hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
5b2fbb7f9f34ec451504359adb0cbf12 | 104 097 | 5.1 Structure | The hybrid cable is typically composed of optical fibre elements and current carrying elements, strength member (possible), filler (possible), yarn (possible) tape (possible), ripcord (possible), sheath, etc. The hybrid cable should meet the requirements of the application and operating environment. Typical FTTR (IFDN) hybrid cables include the round-type, bow-type, and flat-type. Sectional views of typical structures are shown in Figures 5.1 to 5.3. Figure 5.1: Bow-type Hybrid cable Figure 5.2: Flat-type Hybrid cable ETSI ETSI TR 104 097 V1.1.1 (2025-10) 13 Figure 5.3: Round-type Hybrid cable |
5b2fbb7f9f34ec451504359adb0cbf12 | 104 097 | 5.2 Optical fibre elements | The optical fibre elements can be composed of one or more optical fibres, tight or semi-tight buffered fibres, fibre ribbons, buffer tubes, or other optical core structures, or independent optical fibre cables (such as loose tube cable). The optical fibre elements should be in accordance with the following: a) For ease of identification, all the optical fibre and optical fibre elements should be identified by colour coding, ring marking, printing or any other ways as agreed between the customer and the supplier. If the primary coated fibres are coloured for identification, the coloured coating needs to be readily identifiable throughout the lifetime of the cable. b) The material of the optical elements' sheath or loose tube could be polyethylene, polypropylene, Polybutylene Terephthalate (PBT), Low Smoke Zero Halogen (LSZH) material, polyvinyl chloride or other materials suitable to the application. 5.3 Current carrying elements The design of the conductor cross-sections needs to be in according with the rated voltage, transmission distance and consumed power of the powered device. Current carrying elements could be copper or other conductive material. The conductor needs to be continuous without joints through the length of the hybrid cable. 5.4 Strength member Strength members should be made of aramid yarn or other material, and be placed in a suitable position according to the structure of the hybrid cable. 5.5 Outer sheath Polyethylene, polypropylene, PVC, polyurethane, flame retardant low smoke polyolefin and other suitable materials can be used. |
5b2fbb7f9f34ec451504359adb0cbf12 | 104 097 | 5.3 Optical transmission performance | Optical transmission performance for cabled optical fibre elements need to conform to Table 5.1. Table 5.1: Optical transmission performance for cabled optical fibre elements Parameter Test procedure Requirements/Remarks Attenuation coefficient at 1 550 nm IEC 60793-1-40 [i.17] ≤0,30 dB/km for B-652.D ≤0,30 dB/km for B-657 Attenuation coefficient at 1 300 nm IEC 60793-1-40 [i.17] ≤1,5 dB/km for A1-OM1 to A1-OM5 ETSI ETSI TR 104 097 V1.1.1 (2025-10) 14 |
5b2fbb7f9f34ec451504359adb0cbf12 | 104 097 | 5.4 Electrical performance | Electrical performance for current carrying elements need to conform to Table 5.2. Table 5.2: Electrical performance for current carrying elements No Test Severity Requirement 1 Conductor DC resistance IEC 60228 [i.1], Annex A Test equipment: A current source in conjunction with a voltmeter Sample length under test: Not less than 1 m The measured value needs to be recalculated to the standard temperature of 20 ºC and needs to conform to relevant specification 2 Dielectric withstand voltage IEC 63294-2021 [i.45], clause 5.3 1,5 KV (AC)，1 min No breakdown of the insulation 3 Insulation resistance IEC 63294-2021 [i.45], clause 5.4 Test in ambient temperature 20 °C and higher temperature 70 °C or according to relevant detail specifications. 80 V DC to 500 V DC The measured value needs to conform to relevant specification 5.5 Mechanical performance The mechanical tests will affect all the elements of the cable to some degree. The cable should be tested as a whole, rather than discrete elements. Tests on single mode fibre cables should be carried out at 1 550 nm. Multimode fibre cables should be tested at 1 300 nm. Measurements at other wavelengths or wavelength range may be agreed upon between the customer and the supplier. Mechanical performance tests should conform to Table 5.3. Table 5.3: Mechanical performance tests No. Test Severity Criteria 1 Tensile performance IEC 60794-1-101 [i.18] Length of the cable under tension: ≥ 50 m Diameter of test pulleys: ≥ 20 D (D is diameter of finished cable). Long-term tensile load (TL): 80 N for cables with strength member (e.g. Aramid yarn), 60 N for cables without strength member Short-term tensile load (TM): 150 N for cables with strength member (e.g. Aramid yarn), 120 N for cables without strength member Duration: 10 min for long term tensile force,1 min for short term tensile force Rate of tension increase: 100 mm/min O (see note 3), E (see note 4), V The axial fibre strain should be less than 60 % of the fibre proof strain while the cable is under short-term tensile load While the cable is under the long-term tensile load, the axial fibre strain should be less than 20 % of fibre proof test, for fibre proof tested to ≤ 1 % strain (e.g. 0,69 GPa, 0,2 % absolute strain) See note 1. 2 Crush IEC 60794-1-21 [i.21], Method E3A Not less than 3 pieces of the sample, each separated 500 mm The load needs to be applied on the wider side of the cable Long-term load: 1,1 KN Short-term load: 2,2 KN Duration: 10 min for long term load, 1 min for short term load O (see note 5), E, V 3 Impact IEC 60794-1-104 [i.19] Impact energy: 1 J or agreed between customer and supplier 3 impact points, impact one time per point, every point spaced not less than 500 mm apart Radius of striking surface:12,5 mm O, E, V (see note 6) ETSI ETSI TR 104 097 V1.1.1 (2025-10) 15 No. Test Severity Criteria 4 Repeated bending IEC 60794-1-21 [i.21], Method E6 Mass of the weight tensile load: Adequate to assure specimen uniform contact with the mandrel Bending radius: 20 D (D is diameter of round cable or the short axis length of bow-type and flat-type cable) Number of cycles: 25 O, E, V 5 Torsion IEC 60794-1-21 [i.21], Method E7 Tension load: Adequate to assure the specimen to be straight Length under test: 1 m Rotating angle (see note 6) : ±180° Number of cycles: 10 O, E, V 6 Bend IEC 60794-1-111:2023 [i.20] Diameter of mandrel: 20 D (D is diameter of finished cable) Number of cycles: 10 Number of turns: 6 Test temperature: Ambient (unless specifically requested otherwise) O, E, V NOTE 1: For fibres proof tested at levels above 1 % strain, the safe long-term load will not scale linearly with proof strain, so a lower percentage of the proof stain is applicable. NOTE 2: • 'O' means no change in attenuation as defined in IEC 60794-1-21 [i.21] after the test. • 'E' means dielectric withstand voltage needs to conform to Table 5.2 after the test. • 'V' means visual examination, no damage to the sheath or to the cable elements. NOTE 3: The change in attenuation during the test needs to be no more than 0,1 dB at 1 550 nm. NOTE 4: The maximum increase in attenuation during the test with a long-term force needs to be specified in the product specification. NOTE 5: The imprint of the striking surface on the sheath is not considered a mechanical damage. NOTE 6: If the specified twist angle applied to the cable results in a high torsional torque that is not suitable for the cable type, then the rotating angle should be lowered as specified by the manufacturer. |
5b2fbb7f9f34ec451504359adb0cbf12 | 104 097 | 5.6 Environmental performance | Environmental performance tests should conform to Table 5.4. Table 5.4: Environmental performance tests No. Test Test Method Severity Criteria 1 Temperature cycling IEC 60794-1-201 [i.22] Length under test: finished cable length, not less than 1 000 m - 10 °C~60°C Duration at extreme temperatures: 8 h Rate of temperature changing: 1°C/min Number of cycles: 2 Attenuation measurements should be taken at 1 550 nm for single-mode fibre and 1 300 nm for multimode fibre after the test. During the test, change in attenuation should be no more than 0,4 dB/km at 1 550 nm. The dielectric withstand voltage should comply with Table 5.2. Under visual examination without magnification no damage to the sheath or to the cable elements. ETSI ETSI TR 104 097 V1.1.1 (2025-10) 16 No. Test Test Method Severity Criteria 2 Flame test Flame propagation IEC 60332-1-2 [i.2] or other methods agreed between customer and supplier Pass the IEC 60332-1-2 [i.2] single cable vertical flame propagation test. The distance between the lower edge of the top support and the onset of charring is greater than 50 mm. The distance from the lower edge of the top support to the lower onset of charring is less than 540 mm. Emission of smoke (for cables with LSZH material) IEC 61034-2 [i.24] Transmittance ≥ 60 % Emission of corrosive gases (for cables with LSZH material) IEC 60754-2 [i.16] Acidity PH ≥ 4,3, Conductivity ≤ 10 μ S/mm |
5b2fbb7f9f34ec451504359adb0cbf12 | 104 097 | 6 Hybrid Connector | |
5b2fbb7f9f34ec451504359adb0cbf12 | 104 097 | 6.1 Structure | A Hybrid connector in the IFDN Hybrid Cabling System is a miniaturized plug-in connector that consists of a single-core plug and an adapter, with optical and electrical connection characteristics. It is used to transmit signals and remotely supply power to low-power terminals such as WLAN devices and cameras. At present, single mode hybrid connectors are mainly used in IFDN Hybrid Cabling System, and the most widely used hybrid connectors include type XC hybrid connector and type SC hybrid connector in IFDN scenarios. The dimensions should be measured according to IEC 60512-1-2 [i.4]. The plug interface of type XC hybrid connector is shown in Figure 6.1, and the dimensions should comply with Table 6.1. Figure 6.2 and Figure 6.3 show the interface for type XC hybrid connector adapters mounted on printed circuit boards and connection adapters respectively. The dimensions should comply with Table 6.2. The plug interface of type SC hybrid connector is shown in Figure 6.4, and the dimensions should comply with Table 6.3. Figure 6.5 and Figure 6.6 show the interface for type SC hybrid connector adapters mounted on printed circuit boards and connection adapters respectively. The dimensions should comply with Table 6.4. Other optical interface dimensions and requirements should comply with IEC 60874-14-5 [i.23]. ETSI ETSI TR 104 097 V1.1.1 (2025-10) 17 Figure 6.1: Interface for type XC hybrid plug connector Table 6.1: Dimensions of type XC hybrid plug connector interface Reference Unit Minimum Maximum Notes A mm 2,4985 2,4995 _ B mm 5,95 6,15 _ C mm 6,25 6,45 _ Da mm 11,3 11,6 _ E mm 0,6 0,8 _ F mm 1,45 1,65 _ G mm 1,2 1,4 Radius H mm 2 2,2 Radius I mm 0,6 0,8 _ J mm 0,9 1,2 _ L mm 5,95 6,05 _ M mm 6,15 6,25 _ N mm 3,6 3,7 _ O mm 2,6 2,7 _ P mm 2,05 2,25 _ Q ° 5 8 _ NOTE: Dimension D is based on the plug connector end face when unmated. The ferrule is moved in the direction of the contact face by the central axial pressure, so the dimension D is variable. ETSI ETSI TR 104 097 V1.1.1 (2025-10) 18 Figure 6.2: Interface for type XC hybrid connector adapters mounted on printed circuit boards Figure 6.3: Interface for type XC hybrid connection adapters ETSI ETSI TR 104 097 V1.1.1 (2025-10) 19 Table 6.2: Dimensions of type XC hybrid connector adapters and connection adapters Reference Unit Minimum Maximum A mm See note See note AI mm 2,7 2,8 B mm 2,3 2,5 C mm 3,1 3,3 D ° 38 45 E ° 35 48 F mm 2,8 3,2 G mm 1,2 1,5 H mm 11 11,2 I mm 3,6 3,8 J mm 2,6 2,7 K mm 6,5 6,7 L mm 2,35 2,45 M mm 6,1 6,2 N mm 3,8 4,2 NOTE: See table 6 in IEC 61754-4:2022 [i.43]. Figure 6.4: Type SC hybrid plug connector interface Table 6.3: Dimensions of type SC hybrid plug connector interface Reference Unit Minimum Maximum Notes W mm 7,29 7,39 Height dimension of the contact area after the installation of electric contacts X mm - 2 Electric contact frontend relative to the mechanical datum plane Y mm 6,55 - Electric contact backend relative to the mechanical datum plane YB mm 0,8 - Width of the electric contact YD mm 4,2 4,3 Center distance between two electric contacts Z mm 1,3 - Width of the through hole NOTE: Other interface dimensions and requirements should comply with the requirements of IEC 61754-4 [i.43]. ETSI ETSI TR 104 097 V1.1.1 (2025-10) 20 Figure 6.5: Interface for type SC hybrid adapters mounted on printed circuit boards Figure 6.6: Interface for type SC hybrid connector adapters Table 6.4: Dimensions of type SC hybrid adapters Reference Unit Minimum Maximum Notes E mm 4,2 4,3 Center distance between two electric contacts F mm 0,8 1,2 Width of the electric contact W mm 12,4 - Contact area frontend relative to the mechanical datum plane X mm - 10,6 Contact area backend relative to the mechanical datum plane Y mm 3,3 3,4 Height dimension of the contact area plane relative to the optical datum axis YA ° 10 15 Bending angle 6.2 Optical Transmission performance Optical transmission performance for Hybrid connectors should conform to Table 6.5. ETSI ETSI TR 104 097 V1.1.1 (2025-10) 21 Table 6.5: Optical transmission performance of hybrid connectors Test Requirement Attenuation (with reference connector) IEC 61300-3-4 [i.38] ≤ 0,50 dB Return loss (with reference connector) IEC 61300-3-6 [i.39] ≥ 50 dB for XC/UPC hybrid connector and SC/UPC hybrid connector ≥ 60 dB for SC/APC hybrid connector Attenuation of random mated connector IEC 61300-3-34 [i.41] for single fibre connector Attenuation grades Attenuation at 1 310 nm, 1 550 nm and 1 625 nm Grade A Not specified Grade B ≤ 0,12 dB mean， ≤ 0,25 dB max. for ≥ 97 % of the connections Grade C ≤ 0,25 dB mean， ≤ 0,50 dB max. for ≥ 97 % of the connections Grade D ≤ 0,50 dB mean， ≤ 1,0 dB max. for ≥ 97 % of the connections Random mated return loss: IEC 61300-3-34 [i.41] Return loss grades Return loss at 1 310 nm, 1 550 nm and 1 625 nm Grade 1 ≥ 60 dB (mated) and ≥ 55 dB (unmated) Grade 2 ≥ 45 dB Grade 3 ≥ 35 dB Grade 4 ≥ 26 dB Active monitoring of changes in attenuation and in return loss (multiple path) IEC 61300-3-3 [i.37] Change in attenuation during test: δ ≤ 0,2 dB at 1 310 nm and 1 550 nm and δ ≤ 0,3 at 1 625 nm for pigtails (1 connection) δ ≤ 0,5 dB at 1 310 nm, δ ≤ 0,6 dB at 1 550 nm and δ ≤ 0,8 dB at 1 625 nm for patch cords (= 2 connections) Change in attenuation after test: δ ≤ 0,2 dB at 1 310 nm, 1 550 nm and 1 625 nm for pigtails (1 connection) δ ≤ 0,4 dB at 1 310 nm, 1 550 nm and 1 625 nm for patch cords (= 2 connections) Transient loss: IEC 61300-3-28 [i.40] Change in attenuation during test: δ ≤ 0,5 dB at 1 550 nm per connection δ ≤ 1,0 dB at 1 625 nm per connection Change in attenuation after test: δ ≤ 0,2 dB at 1 550 nm and 1 625 nm per connection |
5b2fbb7f9f34ec451504359adb0cbf12 | 104 097 | 6.3 Electrical performance | Electrical performance for Hybrid connectors needs to conform to Table 6.6. Table 6.6: Electrical performance of hybrid connectors Test Requirement Insulation resistance IEC 60512-3-1 [i.7] ≥ 500 MΩ Voltage proof IEC 60512-4-1 [i.8] Between contacts r.m.s. withstand voltage DC 1 000 V Between contacts and housing DC 1 500 V Contact resistance IEC 60512-2-1 [i.5] Initial: ≤ 30 mΩ after test: rise in relation to initial values 20 mΩ max Active monitoring duration of discontinuities during test IEC 60512-2-5 [i.6] ≤ 1 μs 6.4 Mechanical performance Mechanical performance for Hybrid connectors needs to conform to Table 6.7. ETSI ETSI TR 104 097 V1.1.1 (2025-10) 22 Table 6.7: Mechanical performance of hybrid connectors No. Test Severity Requirement 1 Insertion and withdrawal force IEC 60512-13-2 [i.15] (For SC hybrid connector) Total insertion force: ≤ 30 N Total withdrawal force: ≤ 30 N 2 Fibre/cable retention IEC 61300-2-4 [i.27] Load: 50 N for 60 s O (see note 2), V 3 Tensile strength of coupling mechanism IEC 61300-2-6 [i.29] Load: 40 N for 60 s O (see note 2), V 4 Flexing of the strain relief of fibre optic devices IEC 61300-2-44 [i.36] Load: 2 N cables Cycle: ±90° Number of cycles: 50 O (see note 2), V 5 Torsion IEC 61300-2-5 [i.28] Load: 10 N 25 cycles，±180° Fibre/cable clamping distance: 25 cm ± 5 cm O (see note 2), V 6 Mating durability IEC 61300-2-2 [i.26] 200 cycles No less than 3 s between engagements O (see note 2), V NOTE 1: • 'O 'includes change of attenuation and return loss after the test. • 'E' represents change of contact resistance after the test. • 'V' represents visual examination according to IEC 60512-1-1 [i.3]. NOTE 2: Active monitoring change of attenuation during test, after the load has reached its maximum level and been stable. NOTE 3: Active monitoring duration of discontinuities during test, after the load has reached its maximum level and been stable. NOTE 4: Active monitoring of transient loss during test. |
5b2fbb7f9f34ec451504359adb0cbf12 | 104 097 | 6.5 Environmental performance | Environmental performance for Hybrid connectors needs to conform to Table 6.8. Table 6.8: Environmental performance of hybrid connectors No. Test Severity Criteria 1 Cold IEC 60512-11-10 [i.13] Temperature: -10 °C Duration: 96 h O, E, V 2 Dry heat - High temperature endurance IEC 60512-11-9 [i.12] Temperature: +60 °C Duration: 96 h O, E, V 3 Change of temperature IEC 60512-11-4 [i.11] Temperature: -10 °C to +60 °C Duration: 60 min at extremes Rate of temperature change: 1 °C/min 5 cycles O (see note 2), E, V 4 Damp heat (steady state) IEC 60512-11-12 [i.14] Temperature: +40 °C Humidity: 93 % RH Duration: 96 h O, E, V 5 Salt mist IEC 61300-2-26 [i.35] Salt solution 5 % NaCl (pH: between 6,5 and 7,2) Temperature: 35 °C Duration: 48 h O, E, V 6 Vibration (sinusoidal) IEC 60512-6-4 [i.10] Frequency range: 10 Hz to 55 Hz Number of sweeps: 15 sweeps, (10 - 55 - 10) Hz per axis Rate of frequency change: 1 octave/min Number of axes: 3 mutually perpendicular axes Amplitude: 0,75 mm O c , E b , V 7 Shock IEC 60512-6-3 [i.9] Wave form: half sine Duration: 11 ms Acceleration: 150 m/s2 Axes: 3 mutually perpendicular axes Number of shocks: 3 shocks per axis and per direction of axis, 18 shocks in total O c , E b , V NOTE 1: • 'O' includes change of attenuation and return loss measurements after the test; • 'E' includes Insulation resistance, voltage proof and change of contact resistance after the test; ETSI ETSI TR 104 097 V1.1.1 (2025-10) 23 No. Test Severity Criteria • 'V' represents visual examination according to IEC 60512-1-1 [i.3]. NOTE 2: Active monitoring change of attenuation during test. |
5b2fbb7f9f34ec451504359adb0cbf12 | 104 097 | 7 ADU | |
5b2fbb7f9f34ec451504359adb0cbf12 | 104 097 | 7.1 Structure | The structure of the ADU usually consist of the active electrical port (for power supply), optical input port (receive optical signals from the upper level), hybrid output port (transmit optical signal and electrical power together with the connected SFU), and the optional cascading optical port (transmit optical signals to the next-level ADU). The optical port and the hybrid port are connected with type SC or XC hybrid connectors. According to the demand of application scenarios, 1:4, 1:8, and 1:16 ADU can be used in even splitting networks while 1:5 and 1:9 ADU can be used in uneven splitting networks. Typically, the ADU for uneven splitting networks contains a cascading optical port where the next level ADU can be connected, but the ADU for even splitting network only contains hybrid output port without a cascading optical port. |
5b2fbb7f9f34ec451504359adb0cbf12 | 104 097 | 7.2 Operating Environment | ADU for indoor cabling system should be able to operate at following environment, according to IEC 61753-1 [i.42] category OP (Outdoor protected environment): • Operating temperature： -25 ℃ ～ + 70 ℃ • Relative Humidity：5 % ～ 95 %； • Atmospheric pressure：86 kPa ～ 106 kPa. |
5b2fbb7f9f34ec451504359adb0cbf12 | 104 097 | 7.3 Optical Transmission Performance | Optical transmission performance for ADU is advised to conform to Table 7.1. Table 7.1: Optical Transmission performance of ADU Item Splitter Ratio 1:5 1:9 1:4 1:8 1:16 Wavelength 1 310 nm and 1 550 nm Insertion Loss Cascading optical port：≤ 11 dB Hybrid output port： ≤ 11 dB Cascading optical port：≤ 2,4 dB Hybrid output port： ≤ 16,3 dB ≤ 8,2 dB ≤ 11,1 dB ≤ 14,1dB Return Loss ≥ 50 dB |
5b2fbb7f9f34ec451504359adb0cbf12 | 104 097 | 7.4 Electrical Performance | 7.4.1 Input power The ADU operates properly with an input voltage of 45 V ~ 57 V with DC power supply. ETSI ETSI TR 104 097 V1.1.1 (2025-10) 24 7.4.2 Output power The ADU output power should comply with the following requirements according to IEEE 802.3af [i.48], IEEE 802.3at [i.49], or IEEE 802.3bt [i.50] standard: • Output voltage should be 44 V ~ 57 V DC. • The maximum output power should depend on the number of output ports and the power consumption of SFU. • Rated current of each output port should not be less than 0,25 A, and the rated power should not be less than 14 W. Table 7.2: Output power performance of ADU Level Rated power（P） POE (IEEE 802.3af [i.48]) P ≤ 15,4 W POE+ (IEEE 802.3at [i.49]) P ≤ 30 W POE++ (IEEE 802.3bt [i.50]) P ≤ 90 W 7.5 Power source protection ADU should support the following power source protection performance: • ADU should have indicator lamp to display the working status of each port. • ADU should support under voltage protection function: When the input voltage is less than the voltage threshold value, ADU should turn off the output power. When the input voltage is back to the operating value, ADU should resume the working state automatically. • ADU should support over voltage protection functions: When the input voltage is greater than the voltage threshold value, ADU should turn off the output power. When the input voltage is back to the operating value, ADU should resume the working state automatically. • Each output port of ADU should have individual short-circuit current protection and over current protection: When the ADU detects short-circuit or over current, on one of the output ports, it should turn off the power supply on this single output port. Other ports should maintain power supply. After troubleshooting, the affected output port should resume the working state automatically. • The ADU should be equipped with a total power protection function, such that when the total power consumption of the connected SFUs exceeds the product's maximum power capacity, the system will power off lower-priority ports based on their pre-configured port priorities, ensuring that higher-priority ports and their connected SFUs continue to operate normally. |
5b2fbb7f9f34ec451504359adb0cbf12 | 104 097 | 7.6 Electrical performance | Electrical performance for ADU need to conform to Table 7.3. Table 7.3: Electrical performance for current carrying elements No Test Severity Requirement 1 Temperature Rise Test IEC 62368-1 [i.44] Ambient temperature: 40 °C ≤ 30 °C 2 Insulation resistance IEC 62368-1 [i.44] Between contacts r.m.s. withstand voltage：500 V DC Duration: 60 s ≥ 500 MΩ Between contacts and housing： 500 V DC Duration: 60 s ETSI ETSI TR 104 097 V1.1.1 (2025-10) 25 |
5b2fbb7f9f34ec451504359adb0cbf12 | 104 097 | 7.7 Mechanical performance | Mechanical performance for ADU should conform to Table 7.4. Table 7.4: Mechanical performance for ADU No Test Severity Requirement 1 Shock IEC 61300-2-9 [i.30] • ≤ 0,125 kg: 5 000 m/s2 • 0,125 kg < Mass of the sample ≤ 0,225 kg: 2 000 m/s2 • 0,225 kg < Mass of the sample ≤ 1 kg: 500 m/s2 Waveforms: Half sine waveform Duration time: 1 ms Direction: Three vertical directions Times: Twice per direction, total 12 times No mechanical damage to the appearance. Such as deformation, cracks and slackness. The optical fibre needs not to be broken, pulled out, faulty at the end or damage of the sealing. Insertion loss variation before and after test needs to be no more than 0,5 dB, and other optical performances need to conform to Table 7.1 after the test. After the test, electrical performance of ADU needs to conform to Table 7.3 when powered on. 2 Vibration (sinusoidal) IEC 61300-2-1 [i.25] Frequency: 10 - 55 Hz Frequency scanning speed: 45 times per minute Vibration amplitude: 0,75 mm Duration: 0 min for X, Y and Z direction |
5b2fbb7f9f34ec451504359adb0cbf12 | 104 097 | 7.8 Environmental performance | Environmental performance for ADU needs to conform to Table 7.5. Table 7.5: Environmental performance for ADU No Test Severity Requirement 1 Dry heat-High temperature IEC 61300-2-18 [i.32] 85 °C (±2 °C)，duration: 96 h No corrosion for the metal parts. No mechanical damages on the appearances, such as deformation, cracks and slackness. The optical fibre needs not to be broken, pulled out, faulty at the end or damage of the sealing. Insertion loss variation before and after test should not be no more than 0,5 dB, and other optical performances should conform to Table 7.1 after the test. After the test, electrical performance of ADU should conform to Table 7.3 when power on. 2 Cold IEC 61300-2-17 [i.31] -40 °C (±2 °C)，duration: 96 h 3 Damp heat (steady state) IEC 61300-2-19 [i.33] 85 °C (±2 °C) 85 %（±5 %）RH， duration time: 96 h 4 Salt mist IEC 61300-2-26 [i.35] Salt solution 5 % NaCl (pH: between 6,5 and 7,2) Temperature: 35 °C Duration: 96 h 5 Temperature Cycling IEC 61300-2-22 [i.34] -40 ℃ ~ 85 °C 8 h for one-time cycle, hold highest and lowest temperature for 1 h, all cycling time is 21. 7.9 Electromagnetic Compatibility (EMC） ADU should support basic Electromagnetic Compatibility (EMC) function including Radiated Emission (RE), Conducted Emission (CE), Electro-Static Discharge (ESD), RF electromagnetic field (RS), Injected Currents (CS), Voltage Dips, Electrical surge, and Electrical fast transient/burst immunity. ADU should comply with the minimum EMC requirements applicable to its intended usage scenarios according to EN 55032 [i.53] and EN 55035 [i.54]. |
5b2fbb7f9f34ec451504359adb0cbf12 | 104 097 | 7.10 Fire safety performance | For the shell made of plastic materials, the V0 requirements should comply with UL 94 [i.52]. Fire safety tests are conducted to confirm whether the product poses fire hazards or equipment burnout risks under abnormal conditions such as abnormally high voltage or water dripping. Fire safety performance for ADU should conform to Table 7.6. ETSI ETSI TR 104 097 V1.1.1 (2025-10) 26 Table 7.6: Fire safety performance for ADU No Test Severity Requirement 1 Water leakage test The following tests are conducted on the ADU's power input port, output port, heat dissipation vents, and other openings susceptible to foreign object intrusion: 1. Connect the ADU to the main power, with all output ports connected to the SFUs via hybrid cables, ensuring the equipment operates under normal working conditions; 2. Using a syringe, slowly drip 3 ml of liquid (test separately with pure water, tap water, 5 % saline solution, and saturated saline solution) into accessible openings. Continuously monitor each location for 10 minutes to observe whether the SFU powers down, or exhibits visible flames, of a melting of the shell, etc. If such phenomena occur, halt testing; if not, proceed to the next step; 3. Drip 1 - 3 drops of liquid onto the test area, continue observation for another 10 minutes. Check again for a SFU power down or visible flames, melting of the shell, etc. If such phenomena occur, halt testing; if not, proceed to the next step; 4. Repeat Step 3 until a total testing duration of 40 minutes is completed. No flame out of the shell; The shell does not melt; The product shell does not exhibit carbonization. 2 Abnormal high voltage test for external power adapter Test Procedures: 1. Connect the ADU and external power adapter to a step-up transformer, with an initial voltage of 230 V. All output ports are connected to SFUs via hybrid cables, ensuring the equipment operates under normal working conditions; 2. Adjust the step-up transformer to gradually increase the input voltage from 230 V to 253 V (the upper limit of mains power voltage fluctuations). Check whether the ADU continues to function properly. 3. At 253 V, simulate poor wiring in the household distribution box (live wire not securely connected). Repeatedly reconnect at a frequency of 1 time/second. Observe the external power adapter for shell melting, shell carbonization, or flames emitting from the shell. 4. Further adjust the step-up transformer to gradually increase the input voltage to 438 V (simulating incorrect connection to three- phase power). Power on and run the device. Check whether the ADU continues to function properly. 5. At 438 V, repeat the test described in Step 3 to observe shell melting, shell carbonization, or flames emitting from the shell under poor wiring conditions. Termination Conditions: The test stops if: 1. The housing temperature stabilizes without further increases, and no abnormalities like shell melting occur. 2. Abnormal phenomena such as shell melting, shell carbonization, or flames are observed. ETSI ETSI TR 104 097 V1.1.1 (2025-10) 27 |
5b2fbb7f9f34ec451504359adb0cbf12 | 104 097 | 8 Deployment | |
5b2fbb7f9f34ec451504359adb0cbf12 | 104 097 | 8.1 General | The IFDN hybrid cabling system is with the features including fully pre-connected, optical and electrical ports integrated, plug and play, quick deployment and reliable connection. Before cabling, the following tools need to be prepared: optical power meter, voltage detection meter, and other auxiliary materials for construction and testing. The cable routing personnel needs to attend training and follow operating regulations, especially the safety regulations. |
5b2fbb7f9f34ec451504359adb0cbf12 | 104 097 | 8.2 Details to be noted | It is advisable to pay attention to the following items when routing cables: • Before routing a cable, mark the labels at both ends for easy management and maintenance. • When routing the branch cable, protect the cable and do not pull the cable with excessive force to avoid damaging the cable. Do not wind, twist, or step on the cable. • Protect the connectors of branch hybrid cables against collision. • Ensure that the cables are routed neatly and do not affect the unused space to facilitate capacity expansion and maintenance. • In practice, cables can be routed in the direction from the ADU to the MFU or from the MFU to the ADU based on the site environment to ensure that optical cables are easy to coil. • When routing and securing cables, straighten the cables every 5 m. The bending radius of cables should be no less than 24 mm. • Strong-current and weak-current cables are advised to be routed separately and far away from heat sources. If there are mice, PVC pipes should be used to protect the cables, and rodent-proof measurements should be taken in the surrounding environment. • When passing through concealed pipes, pay attention to the old cables or network cables in the pipes which have taken too much space, and avoid excessive pulling force during wiring in case the connectors could be pulled off. • Before threading the tube, try to remove sharp and hard objects in the tube to avoid friction and cracking of the cable sheath. Besides, the environment inside the tube should be clean and dry in case of the corrosion damage to the cables. • When threading the pipe, stress the cable rather than the connector. • Keep the cable laid out in a good ventilation and heat dissipation environment rather than placing the remaining length of the coil directly near the heat source during deployment. |
5b2fbb7f9f34ec451504359adb0cbf12 | 104 097 | 8.3 Acceptance items | |
5b2fbb7f9f34ec451504359adb0cbf12 | 104 097 | 8.3.1 Electrical performance acceptance | During the cable routing, the ADU need not work and affect the remote power supply. The following method can be used to verify the issue: 1) Route the cables, and connect the other end of the hybrid connector to the voltage detection meter as described in Figure 8.1. 2) Turn on the ADU to check if the light of normal work status is on. ETSI ETSI TR 104 097 V1.1.1 (2025-10) 28 3) Test the voltage between the positive and negative PIN poles to verify if it is within the normal voltage ranges. Figure 8.1: Schematic diagram of the electrical performance acceptance test 8.3.2 Optical power acceptance During the cable routing, the cable might be broken or severely bent. As a result, the optical power loss is severe and the insertion loss increases. The following method can be used to verify the issue: a) Route the cables, and connect an Adapter, a patch cord and an optical power meter as described in Figure 8.2. b) Measure and record the optical power of the ADU and hybrid cable. c) Check if the optical power can meet the receiving sensitivity index of SFU. Figure 8.2: Schematic diagram of the Optical power acceptance test ETSI ETSI TR 104 097 V1.1.1 (2025-10) 29 Annex A: Biobliography • IEC 61076-3-127: "Connectors for Electrical and Electronic Equipment - Product Requirements - Part 3-127: Rectangular connectors - Detail specification for hybrid connectors with 2-pole 2,0 A max, 60 V DC electric portion for power supply and type XC fibre optic portion for data transmission". • IEC 61076-3: "Connectors for Electrical and Electronic Equipment - Product Requirements - Part 3-123 Rectangular connectors - Detail specification for hybrid connectors with 2-pole 2,0 A max, 60 V DC electric portion for power supply and type SC fibre optic portion for data transmission, with push-pull locking". ETSI ETSI TR 104 097 V1.1.1 (2025-10) 30 History Version Date Status V1.1.1 October 2025 Publication |
9612427cf1aa38840a14974b2ee90b89 | 104 027 | 1 Scope | The present document presents an analysis of the user expectations, with respect to the study of data driven technologies (Artificial Intelligence (AI), deep learning, Machine Learning (ML)) to present the definition and concept of the User Information System (UIS), that enables Smart Customized Services (SCS) from both user and provider side. These services aim to provide personalization, adaptability, and intelligent decision support within the digital ecosystem. NOTE: The UIS and SCS are designed to serve a broad spectrum of users. Their objective is to empower and protect all citizens. By integrating smart and assistive technologies, the system seeks to enhance participation in public, social, and economic activities, while also offering advanced users more autonomy and self-management capabilities. |
9612427cf1aa38840a14974b2ee90b89 | 104 027 | 2 References | |
9612427cf1aa38840a14974b2ee90b89 | 104 027 | 2.1 Normative references | Normative references are not applicable in the present document. |
9612427cf1aa38840a14974b2ee90b89 | 104 027 | 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 this 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] ETSI TR 103 438: "User Group; User centric approach in Digital Ecosystem". [i.2] ETSI EG 203 602: "User Group; User Centric Approach: Guidance for users; Best practices to interact in the Digital Ecosystem". [i.3] ETSI TR 103 603: "User Group; User Centric Approach; Guidance for providers and standardization makers". [i.4] ETSI TR 103 604: "User Group; User centric approach; Qualification of the interaction with the digital ecosystem". [i.5] Directive (EU) 2019/882 of the European Parliament and of the Council of 17 April 2019 on the accessibility requirements for products and services (Text with EEA relevance). [i.6] EN 301 549 (V3.2.1) (2021-03): "Accessibility requirements for ICT products and services". [i.7] ISO 9241-210:2019: "Ergonomics of human-system interaction; Part 210: Human-centred design for interactive systems", Edition 2; 2019. [i.8] Interaction Design Foundation: "Design for All". [i.9] Centre for Excellence in Universal Design: "The 7 Principles". [i.10] ETSI EG 202 116 (V1.2.2) (2009-03): "Human Factors (HF); Guidelines for ICT products and services; "Design for All"". [i.11] ETSI TS 102 747 (V1.1.1) (2009-12): "Human Factors (HF); Personalization and User Profile Management; Architectural Framework". ETSI ETSI TR 104 027 V1.1.1 (2025-10) 7 [i.12] ETSI ES 202 746 (V1.1.1) (2010-02): "Human Factors (HF); Personalization and User Profile Management; User Profile Preferences and Information". [i.13] University of East London: "Exploring the Ethical Implications of AI-Powered Personalization in Digital Marketing". [i.14] EU TAi Guidelines. [i.15] ETSI TR 104 221: "Securing Artificial Intelligence (SAI); Problem Statement". [i.16] ETSI TS 104 224: "Securing Artificial Intelligence (SAI); Explicability and transparency of AI processing". [i.17] ETSI TS 104 102: "Cyber Security (CYBER); Encrypted Traffic Integration (ETI); ZT-Kipling methodology". [i.18] ETSI TR 103 477: "eHEALTH; Standardization use cases for eHealth". [i.19] Assist-IoT project report D3.2: "Use Cases Manual & Requirements and Business Analysis - Initial". [i.20] Regulation (EU) 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.21] The EU project i-Tour. [i.22] Lazarotto, B.: "The right to data portability: A holistic analysis of GDPR, DMA and the Data Act". [i.23] ETSI EN 303 760 (V1.1.1) (2024-10): "SmartM2M; SAREF Guidelines for IoT Semantic Interoperability; Develop, apply and evolve Smart Applications ontologies". [i.24] ETSI TR 103 875-2: "User Centric approach in Digital Ecosystem; The Smart Interface; Part 2: Smart Identity: A Proof of Concept". [i.25] ETSI TR 103 437: "USER; Quality of ICT services; New QoS approach in a digital ecosystem". [i.26] OMG UML®: "OMG® Unified Modeling Language®", Version 2.5.1. [i.27] 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.28] 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.29] ETSI EN 319 401: "Electronic Signatures and Trust Infrastructures (ESI); General Policy Requirements for Trust Service Providers". [i.30] Brandt Dainow: "Digital Alienation as the Foundation of Online Privacy Concerns". [i.31] 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.32] ETSI TS 103 486: "CYBER; Identity Management and Discovery for IoT". [i.33] ISO/IEC 7498-1: "Information technology -- Open Systems Interconnection - Basic Reference Model: The Basic Model". [i.34] Foureaux, Simon & Daum, Thomas (2025): ""But don't think it is a game": Agricultural videogames and "good farming"". Journal of Rural Studies. 117. 10.1016/j.jrurstud.2025.103686. [i.35] ETSI Directives. ETSI ETSI TR 104 027 V1.1.1 (2025-10) 8 [i.36] Regulation (EU) 2024/2847 of the European Parliament and of the Council of 23 October 2024 on horizontal cybersecurity requirements for products with digital elements and amending Regulations (EU) No 168/2013 and (EU) 2019/1020 and Directive (EU) 2020/1828 (Cyber Resilience Act). [i.37] 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 (directive SRI 2). [i.38] Sasan Rostambeik, Noemi Simoni, Antoine Boutignon: "Userware: A framework for next generation personalized services", Computer Communications, Volume 30, Issue 3, 2007, Pages 619-629, ISSN 0140-3664. [i.39] "OGC City Geography Markup Language (CityGML); Part 1: Conceptual Model Standard". [i.40] "OGC City Geography Markup Language (CityGML); Part 2: GML Encoding Standard". [i.41] The EU project iLocate. [i.42] The EU project Assist-IoT. [i.43] Waze. [i.44] Regulation (EU) 2022/1925 of the European Parliament and of the Council of 14 September 2022 on contestable and fair markets in the digital sector and amending Directives (EU) 2019/1937 and (EU) 2020/1828 (EU Digital Markets Act (DMA)). [i.45] ETSI TS 102 165-2: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Methods and protocols; Part 2: Protocol Framework Definition; Security Counter Measures". NOTE: An update is in preparation to a CYBER document at the time of preparation of the present document. |
9612427cf1aa38840a14974b2ee90b89 | 104 027 | 3 Definition of terms, symbols and abbreviations | |
9612427cf1aa38840a14974b2ee90b89 | 104 027 | 3.1 Terms | For the purposes of the present document, the following terms apply: Architecture Communication Information Function Organization (ACIFO) model: framework for interpreting and analysing complex systems whole through the five dimensions that characterize it artificial intelligence: ability of a system to handle representations, both explicit and implicit, and procedures to perform tasks that would be considered intelligent if performed by a human avatar: representation of the user in digital form digital ecosystem: network of interconnected digital technologies, platforms, and services that interact with each other to create value for businesses and consumers and facilitate access to digital technology for everyone machine learning: branch of artificial intelligence concerned with algorithms that learn how to perform tasks by analysing data, rather than explicitly programmed reinforcement learning: form of machine learning where a policy defining how to act is learned by agents through experience to maximize their reward; and agents gain experience by interacting in an environment through state transitions semi-supervised learning: form of machine learning where the data set is partially labelled. In this case, even the unlabelled data can be used to improve the quality of the model supervised learning: form of machine learning where all the training data is labelled and the model can be trained to predict the output based on a new set of inputs ETSI ETSI TR 104 027 V1.1.1 (2025-10) 9 unsupervised learning: form of machine learning where the data set is unlabelled, and the model looks for structure in the data, including grouping and clustering User Platform as a Service (UPaaS): userware developed according to the "aas" model |
9612427cf1aa38840a14974b2ee90b89 | 104 027 | 3.2 Symbols | Void. |
9612427cf1aa38840a14974b2ee90b89 | 104 027 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: aaS as a Service ACIFO Architecture Communication Information Function Organization AI Artificial Intelligence API Application Programming Interface AR Augmented Reality DaaS Device as a Service DAC Discretionary Access Control DMA Digital Market Act DTP Data Transfer Project E2E End-to-End eIDAS electronic IDentification, Authentication and trust Services EUDI EU Digital Identity Wallet GDPR General Data Protection Regulation GIS Geographic Information Systems HMI Human Machine Interface IaC Infrastructure as Code ICT Information & Communications Technology IoT Internet of Things MAC Mandatory Access Control ML Machine Learning NaaS Network as a Service ODA Open Distributed Architecture OSH Occupational Safety and Health PaaS Platform as a Service PPE Personal Protective Equipment QoE Quality of Experience QoS Quality of Service SaaS Software as a Service SAREF Smart Applications REFerence ontology SCS Smart Customized Service SOA Service-Oriented Architecture SUMA Smart Urban Mobility Assistant UDR User Digital Representation UIS User Information System UML Unified Modelling Language UPaaS User Platform as a Service ETSI ETSI TR 104 027 V1.1.1 (2025-10) 10 |
9612427cf1aa38840a14974b2ee90b89 | 104 027 | 4 Smart Customized Services for UIS | |
9612427cf1aa38840a14974b2ee90b89 | 104 027 | 4.1 Identification of the problem to be solved | Users of digital services have historically had limited ability to control the use of personal data by digital services and how a service shares that data with other services, nor is there usually fine-grained control of what is given in terms of personal data, rather there is often a "share all" approach to how data is released. Whilst users are protected by a number of legislative instruments (see clause 6 and Annex D, for a broad summary of these instruments), the control is often passed to the service provider and the user is often not directly involved in the way in which their data is used or how a service is composed from component services. Whilst there are a number of technical means to restrict the personal data given to a service, e.g. by selective disclosure as outlined for eIDAS [i.27], [i.28] and the EU Digital Identity Wallet (EUDI) in ETSI TR 119 476 [i.31], or by application of specific permutations of a user profile following the approach of ETSI TS 103 486 [i.32], there are wider implications and requirements that are considered in the present document that seek to empower the user's control of personal data. NOTE 1: In the eIDAS2 regulation [i.28] it is stated in Recital 59 that "Selective disclosure is a concept empowering the owner of data to disclose only certain parts of a larger data set, in order for the receiving entity to obtain only such information as is necessary for the provision of a service requested by a user. The European Digital Identity Wallet should technically enable the selective disclosure of attributes to relying parties. It should be technically possible for the user to selectively disclose attributes, including from multiple, distinct electronic attestations, and to combine and present them seamlessly to relying parties. This feature should become a basic design feature of European Digital Identity Wallets, thereby reinforcing convenience and the protection of personal data, including data minimization". Addressing only the user's data and its selective disclosure is not sufficient, rather the services that are offered to, or built by the user, also have to be cognizant of the problems that users face in having assurances of the protection of personal data, including data minimization whilst maximizing the conveniences of the digital ecosystem. To this end the present document expands the idea of user by considering the user as an information system (the User Information System (UIS)) in the context of Smart Customized Services (SCS). In this respect it is noted that the concept of user centric design is well established in many industries and describes an approach wherein products and services are explicitly developed around the user. This does not imply bespoke design and manufacture, rather it allows the user to choose aspects of the way the service is presented and accessed, particularly in the ICT domain by personalization of user interfaces. By allowing for greater control of how data is used and how services are constructed using the UIS/SCS model the user is afforded control of, and maintenance of, their personal autonomy. The userware (see [i.38]) is then a means of allowing the user to explicitly control their autonomy within the provision of services. The role and purpose of SCS is to place the user at the centre of their own digital ecosystem as the UIS (i.e. allows users to have control of their autonomy), being a virtual representation of the user's preferences as an information element and active entity. The UIS in SCS is therefore a persistent digital object in the service domain, representing an intelligent agent of the user (i.e. as an AI-enabled avatar acting as the user). SCS and UIS together extend and develop prior concepts of users being represented as information elements in order to allow users to maintain control over their data and more generally their own information system in the way that they present themselves to services and more generally online. In order to support SCS/UIS a number of system pre-requisites have to be met. The primary pre-requisite is that service components are considered as always available and are able to semantically and contextually identify themselves. It is also expected that service components exhibit the following characteristics (these are expanded upon in clause 7 of the present document): • Statelessness: Each service should be able to process requests without retaining any request-specific or contextual information. Operations should function independently of prior invocations. • Autonomy: Services should execute their functionalities independently of each other. • Loose Coupling: Connections between services should be flexible rather than rigid and not require functional dependency on any other service. • Cohesive: Services should be logically coherent and self-contained (see also autonomy). ETSI ETSI TR 104 027 V1.1.1 (2025-10) 11 • Abstract: The internal service logic should remain abstracted from external environments (i.e. independent of). NOTE 2: The term user in the present document is not intended to only refer to a human user but may include a service using other services. NOTE 3: Services can have multiple characteristics, they may be information services or interactive services, and if a composition of services results in a new service then it is the composition that is referred to as the service. In addition to the technical pre-requisites identified above there is an attestation in the present document that there is a consumer demand for more control of services (demand chain), and a matching willingness on the part of providers to meet that demand (supply chain). The smart component is identified as an AI element and applies intelligence to ensure that services are configured and personalized only where the required data from UIS is appropriately acquired and curated (see ETSI TR 104 221 [i.15] for a wider examination of the role of data in machine learning). The UIS model and its realization in the management of services with SCS expands the models from each of ETSI TS 102 747 [i.11] and ETSI ES 202 746 [i.12] to have a persistent user profile able to interact with multiple services. This is shown in Figure 1 as a Venn diagram where SCS lies at the intersection of these 3 technological design paradigms: • User centric design: - Addressing Quality of Experience (QoE) aligned to Quality of Service (QoS). • Societal digitization: - Addresses the increasingly important role of digital devices and their use to connect to services for business, entertainment and governance representing a digital ecosystem. • Automation: - This includes the evolution of smart systems and the application of AI in various forms. Figure 1: Intersection of domains that identifies the role of SCS User centric design Automation Societal digitisation UIS/SCS ETSI ETSI TR 104 027 V1.1.1 (2025-10) 12 Whilst one outcome of loosely controlled release of personal data is that of digital alienation, it is also clear that current best practices such as for the EUDI [i.31] are not often as widely implemented as would be required to give the same quality of experience across all user interactions with the digital world with regards to the use of personal data that would mitigate threats such as those of digital alienation [i.30]. |
9612427cf1aa38840a14974b2ee90b89 | 104 027 | 4.2 Application of the ACIFO model in SCS | The Venn diagram of Figure 1 is expanded first into the model given below in Figure 2 which illustrates the role of elements of each domain on SCS. In the context of Smart Customized Services (SCS), personalization is not limited to the adaptation of content or functionality to an individual. Analysis, through the ACIFO model, shows that it also results from organizational choices regarding data processing and governance, which dynamically adapt to the evolving user context and preferences. The layering that results is: Serviceware where the Platform as a service providers exist; Networkware that provides the necessary connectivity; and Userware where user-centric services exist (see Figure 2). Figure 2: User Centric Approach: Personalization SCS can be further developed using the 5-dimensions of Architecture, Communication, Information, Function, Organization (ACIFO) in the ACIFO model described in ETSI TR 103 438 [i.1], ETSI EG 203 602 [i.2], ETSI TR 103 603 [i.3], ETSI TR 103 604 [i.4]) examined in detail for the UIS/SCS environment in clause 7. In particular recommendations for application in a service centric environment are addressed in clause 7.1, and recommendations for application in a user centric environment (e.g. userware) are addressed in clause 7.2 of the present document: • Architectural Model: defines the global structure, including semantics and is optimized for the stated objectives. • Communication (Relational) Model: defines the exchange protocols, including HMIs (User) and APIs (provider) exchange and management protocols over three planes: (1) Management (Monitoring), (2) Control, and (3) Usage. • Information Model: defines the different Profiles (User, device, service). The information covers the whole ecosystem (equipment, network, applications, services, HMIs, User, etc.) from the offer to the resource's availability for Users, Providers and any other partners. It is a knowledge data base representing the whole ecosystem. EXAMPLE 1: In the present document the information model is the UIS, which includes all of the user preferences and contextual knowledge. • Functional Model: defines services and service composition. The functionalities (the process) to compose any service based on "micro-service". ETSI ETSI TR 104 027 V1.1.1 (2025-10) 13 EXAMPLE 2: In the present document the functional model requires that functions are available using the "as a Service" model. • Organization Model: defines the role of any actor and which actor is responsible of each action. ("Who is doing what?" in terms of responsibility for processing and data governance). The particular use of ACIFO in the present documented is augmented by application of the ZT-Kipling criteria from ETSI TS 104 102 [i.17] which gathers knowledge of every interaction of the user (as UIS) with the system components (via the SCS) by requiring answers to the following questions on each use: What?, Why?, When?, How?, Where?, and Who? Whilst the application of [i.17] primarily impacts the Communication and Information elements of the ACIFO model, the consequence is that each of the other elements of the ACIFO model (i.e. the Architectural, Functional and Organizational elements) have to be designed in such a way that the ZT-Kipling criteria can be fulfilled. NOTE: The ACIFO approach does not infer a specific order of addressing the dimensions but for the purposes of the present document are presented in the order of the acronym. |
9612427cf1aa38840a14974b2ee90b89 | 104 027 | 5 Use cases for User Information Systems | 5.1 Introduction to use cases for UIC and their service composition The present document adopts the model given in ETSI TR 103 477 [i.18] where it is stated that use cases are developed to examine problem statements that are a concise description of issues that need to be solved in the context of the use case. The purpose of the use case is to clearly describe: • What the problem is. • Who has that problem i.e. who will benefit when it is solved. • What are the consequences of the problem. • What a possible solution would be, this sets the expectations and the scope of the solution (is it a new process, an application, etc.). In the context of standardization the problem is multi-fold but is primarily concerned with determination of interoperability. This may be at the application level where syntactic and semantic coherence is critical, or at any of the layers of the OSI stack (see ISO/IEC 7498-1 [i.33]). For communications interoperability the main concerns are to give assurance of connectivity, of routing (i.e. the ability of devices to connect in order to provide reliable transport of information from source to sink), and of mutuality of transfer rates (i.e. to ensure that data produced at a given rate can be consumed at the same rate). The purpose of the use cases given in the present document are to identify common requirements of UIS and SCS. The uses cases identify multiple functions to build relatively complex systems, although it is recognized that such systems (e.g. the urban mobility use case) are extensions of how users typically interact with the transport systems of their local environment, the potential of UIS/SCS to accelerate interventions and to act "in the loop" is identified by the use cases that follow. The use cases are presented to show how they impact different forms of user (in the form of actors in the use cases), and what information is required from and between actors to enable the use cases. It is noted that for most use cases there is a rational decomposition into multiple use cases. Each use case identifies the actors in the use case, the principal interactions and the expected output in terms of the role of UIS and SCS. The use cases are drawn using the conventions of the Unified Modelling Language (UML) [i.26]. NOTE: The UIS/SCS is modelled as an UML Class for the present document but may be modelled in other ways. The generalized use case model of UIS/SCS is given in Figure 3 where each actor manages their preference set as UIS, and creates SCSs which combine the data from the UIS of the actors with the microservices available. ETSI ETSI TR 104 027 V1.1.1 (2025-10) 14 Figure 3: Generalized use case model of UIS/SCS The services used in SCS via the Compose Service use-case are micro-services that have the characteristics outlined in clause 4.1 above. In all cases it is assumed that the user controls which elements of the UIS are released, and that critically, the UIS has a means of selective disclosure available natively. |
9612427cf1aa38840a14974b2ee90b89 | 104 027 | 5.2 Urban mobility use case (Smart Urban Mobility Assistant) | Taking the general model suggested in clause 5.1 above the following outlines the role of SUMA. • What is the problem that SUMA seeks to solve in the UIS/SCS context? - Existing methods of determining an optimized personal travel plan are deficient in addressing in-depth the personal preferences and context of the user. SUMA seeks to optimize the selection and integration of travel modes for each individual, in terms of time, cost, or environmental impact. It considers user preferences and the context: schedules, weather, traffic disruptions, etc. Thus SUMA facilitates user-optimized and personalized multi-modal urban travel (i.e. by the most effective mix of foot, bus, metro, car, or bike) whether for work, leisure, shopping, health, school, social relations, etc. • Who has that problem i.e. who will benefit when it is solved. - The primary affected user is the person travelling. In addition having more knowledge of the real travel requirements and the preferences and contexts in which travel solutions are required may be of benefit to providers of travel solutions in optimizing their service composition and delivery. • What are the consequences of the problem? - The primary consequence at the heart of SUMA is in data collection and processing. The following data is collected and processed: Personal data: (taken from the UIS and augmented on request of the service). As not all personal data of the user is required the user consents to selective disclosure of only part of the UIS dataset (e.g. the user's calendar or diary, health information (where such data has a consequential impact on routing and accessibility (e.g. permanent or temporary disability), subscriptions to specific service providers in the context of SUMA). Transport offer data: transport offer including prices and timetables. Cartographic data (GIS): Geographic Information to enable route visualization and route calculation. ETSI ETSI TR 104 027 V1.1.1 (2025-10) 15 Contextual and environmental data: weather, air pollution, connectivity… - In addition to the data collection consequences of SUMA the following specific functionalities are embedded: Route calculation: the route calculation finds and proposes a path depending on the availability of the transport offer, the user's preferences, and the environment (e.g. the user may set preferences for any of the fastest or shortest or least expensive routing taking into account the current context (i.e. things that impact the plan such as congestion, industrial action and so forth)). Notifications and alerts: departure notification, guidance notification, recommendations, subscription renewal. guidance: information regarding direction to take step by step. Recommendations on the way: possibility of partnership with businesses or services present on the route and able to meet needs of the user identified in the agenda for example. Subscription management: bus, metro, parking, self-service bike or vehicle… Statement: finance, health, environment: a reporting in term of expense, health, impact environment. • What a possible solution would be? - The wider deployment of user centric "as a service" components in the transport domain. The user preferences for SUMA are taken from the UIS and SUMA as a whole represents an instantiation of the SCS model. Figure 4: SUMA data and functional architecture ETSI ETSI TR 104 027 V1.1.1 (2025-10) 16 A specific example within the SUMA use case is given below. EXAMPLE: The user has arranged a visit involving a flight from London's Heathrow airport, to Nice in order to attend a working meeting of an ETSI Technical Body. The public knowledge of this enables significant contextual information to be gathered, e.g. the meeting schedule, the airline schedule. In addition SUMA is aware of the starting point of the visit (the user's home), the user's preference for travel mode, and so forth. SUMA can then identify travel options at each point of the intended journey, suggest options for guard time (e.g. to change train platforms, or travel modes). SUMA can also ask for additional information, such as how much luggage the user is taking (that may assist in determining if public transport is viable for the pre- and post-flight travel). From the available information SUMA recommends that the user is taken to a local London Underground station by a family member (SUMA has access to the shared family calendar and can request verification that this is reasonable) to take a combination of tube lines to Terminal 5 (from knowledge of which airline is being used SUMA can determine which airport terminal to use). During the journey SUMA identifies a potential problem with the initially planned route and recommends a change of route and advises on the change in expected time of arrival, alongside the impact of remaining with the initially planned route. In this case the initially planned route is not viable so the user accepts SUMA's recommendation. At all times SUMA monitors the overall travel progress, and if required can give feedback to friends and family - in this case to keep the user informed that the family member is safely home again after the drop off, and to also inform that same family member whenever a major phase of the journey is complete. NOTE 1: The EU project i-Tour [i.21] addressed many of the core topics of the urban mobility use case as personalized multi-modal route planning and is summarized in Annex B. NOTE 2: The i-Tour project [i.21] contains descriptions of a number of other, closely related, use cases. NOTE 3: The use of Augmented Reality (AR) to assist in visualization of routing instructions in an urban environment, based on the wide availability of CityGML [i.39], [i.40] modelling of the built environment can be found in EU project i-Locate ([i.41]) and a summary can be found in Annex C. |
9612427cf1aa38840a14974b2ee90b89 | 104 027 | 5.3 Agriculture | Taking the general model suggested in clause 5.1 above the following outlines the role of UIS/SCS applied to an instance of an agricultural problem. • What is the problem that UIS/SCS seeks to solve in the agricultural context? - Agriculture faces significant challenges, including climate change, resource depletion, water scarcity, and a rising global demand for food. To address these issues, the digitalized farm leverages real-time, data-driven decision-making to optimize crop yields, reduce risks associated with diseases and climatic hazards, support farmers in making precise and personalized decisions tailored to their specific conditions, and enable effective market integration to anticipate demand and plan harvests accordingly. • Who has that problem? i.e. who will benefit when it is solved. - Farmer: Responsible for the daily use of the system, monitoring crop progress, checking alerts and recommendations, and implementing suggested actions. The farmer remains the final decision-maker and adjusts interventions according to their goals and constraints. - Logistics provider (in both supply chain and demand chains): Manages the supply chain for inputs (seeds, fertilizers, equipment) and the delivery of harvested crops to markets that are determined in advance by giving assurance of demand to encourage supply. ETSI ETSI TR 104 027 V1.1.1 (2025-10) 17 • What are the consequences of the problem? - Smart Customized Services (SCS) can dynamically compose and orchestrate features tailored to the specific needs of a user and their operational context. In agriculture, they enable solutions to be customized according to the specific characteristics of each farm, the farmer's preferences, and local environmental constraints. In order to operate successfully the following are added to the system: Connected sensors: Continuously measure environmental and agronomic parameters (temperature, humidity, pH, light, nutrients). AI engine: Analyses data, detects risks and opportunities, and generates forecasts. Digital farm (Digital Twin): Virtual representation of the farm, integrating static and dynamic data. Smart interface: Allows the farmer to visualize information, receive alerts, and interact with the system through the userware. Service Component Provider: Supplies services that can be composed either by the Agronomist Expert or by the Farmer. Agronomist expert (E2E specialized service provider): responsible for validating and optimizing AI models. It assesses prediction accuracy, adjusts algorithms if necessary, and ensures that recommendations provided to the farmer are reliable, relevant, and tailored to the context. - At present personalization (AI model & service composition) is carried out by the agronomist expert. Applying UIS/SCS will give the farmer more autonomy, allowing them to perform this service composition themselves by directly accessing the service provider's APIs. • What a possible solution would be? - The digitalized farm implements a continuous cycle of data collection, analysis, and action to assist the farmer in the daily management of crops or livestock. Data from sensors is aggregated in the digital farm and analysed by an AI engine, which translates the results into targeted recommendations that the farmer can apply immediately. The actions taken, along with their observed effects, are then fed back into the Digital Twin, allowing future forecasts to be refined and recommendations to be continuously adapted to real field conditions: Anomaly detection and identification of environmental trends. Image analysis to assess tomato ripeness. Automated diagnosis of leaf and fruit diseases. Yield prediction based on historical and real-time data. Visualization of results via interactive dashboards and visual indicators. Agronomic recommendations for irrigation, harvesting, and plant protection treatments. Issuance of intelligent alerts and notifications for optimal responsiveness. - In addition the UIS/SCS centred solution would be able to add the following: Preference management (UIS) The farmer sets preferences in the UIS, such as humidity thresholds, yield objectives, and alert frequency. The farmer selects the corresponding IoT devices. Data collection & Analysis Sensors continuously monitor temperature, humidity, soil pH, light intensity, and nutrient levels. The collected data is securely transmitted to the Digital Farm (via secure APIs), where it is analysed and processed to produce valuable and useful insight. ETSI ETSI TR 104 027 V1.1.1 (2025-10) 18 Analysis and detection (SCS + Serviceware) The SCS orchestrate the available micro-services (humidity analysis, weather analysis, tomato maturity detection). The specialized service provider validates the AI models and provides advanced analyses, such as early disease detection and irrigation optimization. Agronomic recommendations The SCS translates the results into concrete recommendations—for example, irrigate more in the northern zone and plan the optimal harvest in five days. These recommendations are sent to the farmer via the intelligent interface. Yield prediction By combining historical and current data, the SCS estimates the total volume of tomatoes to be harvested. Feedback and continuous learning On the planned day, the farmer harvests the tomatoes. Yield and health data are fed back into the Digital Twin and SCS to improve the accuracy of future forecasts. Figure 5: An example of UIS/SCS applied to tomato cultivation In analysing the agriculture use case as above the role of personalization and autonomy identifies that in the current scenario, personalization (AI model & service composition) is carried out by the expert. To give the farmer more autonomy, they should be allowed to perform this service composition themselves by directly accessing the service provider's APIs and the text above relating to the consequences of the problem). ETSI ETSI TR 104 027 V1.1.1 (2025-10) 19 |
9612427cf1aa38840a14974b2ee90b89 | 104 027 | 5.4 Health | ETSI TR 103 477 [i.18] identifies use cases and actors for each of diagnostic and therapeutic interventions. The present document extends the characterizations from [i.18] with many of the actors being present as persistent AI entities in the health system. Thus applying the use case purpose identified in [i.18] to the UIS/SCS enabled eHealth environment identifies the following: • What the problem is. - The data relating to the health of an individual is not in the control of the individual and may not be readily available during triage, diagnosis, treatment and recovery. Without significant personal data used in a diagnosis the diagnosis and subsequent treatments may be invalid. Personalized healthcare is rare and often expensive even if the core data can be obtained at low cost (both financially and in terms of convenience). Without reasonable control of how data is shared the benefit of ICT enabled healthcare may not be realized. • Who has that problem i.e. who will benefit when it is solved. - The healthcare support to a patient needs often deep and wide knowledge of a patient in order to make an accurate diagnosis. Whilst short term triage may fix an obvious problem it is not a full diagnosis. Thus whilst fixing the effect of a fall is good, it would be better to have access to health records that may identify an underlying problem that led to the fall. - The primary beneficiary is the patient but a wider community of beneficiaries include the healthcare providers, and society in general. Early access to health related data and its analysis may lead to early prevention of health and wellness issues. • What are the consequences of the problem. - Increased digitization of health records with wider, controlled, access rules applied to assure user control as far as is possible. • What a possible solution would be, this sets the expectations and the scope of the solution (is it a new process, an application, etc.). - In eHealth for much of the time the patient is represented by their health record which for the present document is considered as the root of the UIS, with the various diagnostic and therapeutic interventions acting as the SCS. Figure 6: Electronic health record ETSI ETSI TR 104 027 V1.1.1 (2025-10) 20 5.5 Assurance of Health and Safety in an IoT enabled construction environment NOTE 1: This use case has been derived from information contributed by the ASSIST-IoT project in their deliverable D3.2 [i.19]. NOTE 2: A summary of the ASSIST-IoT project [i.42] is given in Annex A of the present document. Using the same schema outlines in clause 5.1 above the following is declared for this use case. • What the problem is. - Within any building construction site, a large number of people with various levels of training and experience, from several subcontracted companies, are required to interact with each other, operate equipment or interface with heavy machinery. - It is necessary that all construction workers wear appropriate Personal Protective Equipment (PPE). The relevant PPE is risk assessed and is unlikely to be the same for all workers on a site. Verifying the correct use of PPE at each point in a site is difficult if the verification is dependent on only human verifiers, and may not be practical if the appropriate PPE for a remote work area is different from the PPE required at the inspection point. - All access points are securely locked and the construction workers and plant have been registered with the main contractor. Smart devices and wearables are paired together in order to monitor the construction worker's status, e.g. wearing all PPE or operating construction plant. • Who has that problem i.e. who will benefit when it is solved. - The actors and their primary interactions are shown in Figure 7 and Figure 8 below. Figure 7: Illustration of occupation safety and health monitoring ETSI ETSI TR 104 027 V1.1.1 (2025-10) 21 Figure 8: Illustration of safe navigation instructions • What are the consequences of the problem. - The first responders are promptly notified about the occurrence, nature and location of an emergency and rescue the construction worker who is in danger. - The UIS/SCS platform needs in this instance to geo-aware and to have knowledge of the applicable Occupational Safety and Health (OSH) regulation. • What a possible solution would be, this sets the expectations and the scope of the solution (is it a new process, an application, etc.). - Collecting reliable and relevant information in order to generate intelligent insights for the protection of all individuals present at any worksite within a large construction site can demonstrate the viability of UIS/SCS in gathering personal, industrial and contextual data to ensure that the user and any liable party is protected from inappropriate use of Personal Protective Equipment (PPE). 6 Regulatory and other constraints that may apply to UIS/SCS |
9612427cf1aa38840a14974b2ee90b89 | 104 027 | 6.1 Data governance | In giving user control, where the user is disassociated from the service by their persistent entity, their User Digital Representation (UDR), in the network, the user has to have assurance that the data gathered, exchanged and processed on their behalf is trustworthy. There are many discussions of trust, and models of trust, that may apply to SCS. The concept of trust can be addressed by the application of methods such as those described in ETSI TS 104 102 [i.17] where based on the answers to a set of questions (who, what, where, when, why, how) knowledge is acquired of the entity that is to be trusted, and based on the answers and local policy a decision to trust or not can be made. The definition of trust as "confidence in the integrity of an entity for reliance on that entity to fulfil specific responsibilities" and for the purpose of the present document this definition requires that each element in the SCS chain, and the services they provide has to be able to generate sufficient proofs or evidence to give assurance of that trust. In some instances trust can be delegated to a third party as in the models used in eIDAS [i.27], [i.28] for Trusted Service Providers (see [i.29]). In all instances for SCS the primary requirement is to be able to satisfy the policy set by the user for the assignment of responsibility to a remote agent. In order to build up the necessary context to give assurances of the trustworthiness of elements of SCS/UIS the requirements for transparency of explicability of AI processing defined in ETSI TS 104 224 [i.16] and by the application of the core questions from the ZT-Kipling method (ETSI TS 104 102 [i.17]) to the data and service. An example of the application of these approaches is given in Annex E. ETSI ETSI TR 104 027 V1.1.1 (2025-10) 22 |
9612427cf1aa38840a14974b2ee90b89 | 104 027 | 6.2 Privacy and data protection | The UIS/SCS has to conform to societal expectations of privacy protection and to also conform to any legal restrictions. To achieve this some security capabilities are required (shown in more detail in clause 7.2 below), and it is expected that the overall system conforms to expectations of the GDPR [i.20] or equivalent national or regional legislation outside of the EU. A further consideration of UIS/SCS is that it is assumed that there are multiple services and therefore the data subject is likely to be represented by a proxy (see also considerations for accessibility in clause 6.5. A wider concern of applying existing data protection legislative frameworks to the UIS/SCS case is that consent may become unclear and therefore the UIS/SCS governance model has to accommodate the UIS/SCS acting somewhat independently of the user. EXAMPLE: In the SUMA use case whilst a query may be anonymized for any particular phase of a journey, an observer, which may be the UIS/SCS itself, may be able to single out the user even if the UIS itself is a protected element of the system. Article 20 of GDPR [i.20] in particular for the UIS/SCS context suggests a framework for the practice of the right to data portability, that data subjects have the right to receive data in a structured, commonly used and machine-readable format. It is not intended that the user should just receive an overview or summary of their data. The goal of portability is to be able to reuse personal data immediately (or later) by integrating it onto another platform or service. The following general characteristics for machine readable data should therefore be applied to all UIS/SCS data and to the use of data in associated services: • Reliability • Authenticity • Integrity • Usability The consequence of applying these characteristics is that, in addition to the appropriate semantic and contextual labelling (see clause 6.4 below), some attention is paid to data provenance. Contrary to ad hoc downloads, APIs can enable continuous real-time data portability and thus the smooth interoperability of the different actors, their technologies and services. In addition, data holders can implement several restrictions via APIs to better control the use of their data, including by enabling access based on the identity of API users, and the scale and scope of the data used. Also, a dedicated API may reduce the perceived necessity of 'data scraping' which requires users to grant third parties access to their online account to extract the data from the online interface and, in some cases, to execute transactions on the customer's behalf. Such activities may violate data holders' terms of use or the IPRs of third parties. Data portability regimes that take advantage of APIs may in this way increase the security of, and trust underpinning, data transfers while minimizing the risk of copyright violations. An example implementation of this data portability implementation is the Data Transfer Project (DTP) which is an open-source initiative which features data portability between multiple online platforms. [i.22] It provides a platform that allows individuals to move their online data between different platforms, without the need of downloading and re- uploading data. The ecosystem is achieved by extracting different files through various available APIs released by online platforms and translating such codes so that they are compatible with other platforms. Further analysis of the impact of privacy regulations on UIS/SCS is given in Annex D of the present document. |
9612427cf1aa38840a14974b2ee90b89 | 104 027 | 6.3 Security | In regulatory terms there are a large number of instruments in place that serve to lower the risk to users of actions they take online. These include the Cyber Resilience Act [i.36], the Network Information Security Directive [i.37] and many of the other legislative instruments that address privacy and the content of data have an implicit, sometime explicit, set of security requirements. An analysis of the regulatory impact of security on UIS/SCS is given in Annex D. ETSI ETSI TR 104 027 V1.1.1 (2025-10) 23 |
9612427cf1aa38840a14974b2ee90b89 | 104 027 | 6.4 Data semantics and ontology | The process of data portability, and of data interoperability, can be enabled by assuring that data is described semantically and to which a context can be attached, This requires that data has been structured to add meaning to it. In common practice an ontology is used to explicitly define the concepts and relationships within a domain, allowing machines to understand the data's semantic structure and to enable them to perform complex operations on it. EXAMPLE: The Smart Applications REFerence ontology (SAREF) framework of ontologies for IoT that enables different parties to interoperate with each other at the semantic level [i.23] The common concept of SAREF is that all existing data models/protocols can be incorporated into an ontology (i.e. a common vocabulary). This captures the meaning of a concept (i.e. semantics) rather than the specific data format in which the concept is encoded for data exchange at the underlying communication layer. For this to work manufacturers and service providers should enable their data to be portable as it enables interoperability. |
9612427cf1aa38840a14974b2ee90b89 | 104 027 | 6.5 Accessibility | Any implementation of UIS/SCS should comply with the European Accessibility Act [i.5], a legal instrument that aims to improve the functioning of the internal market for accessible products and services by removing barriers created by divergent rules in Member States. A detailed review of the impact of [i.15] and related legislation on UIS/SCS is given in Annex D. The present clause highlights those actions applicable to UIS/SCS. The SCS should conform to EN 301 549 [i.6], which can be applied to ICT-based products and services. Also applicable to the SCS is ISO 9241-210 [i.7], which provides requirements and recommendations for human-centred design principles and activities throughout the life cycle of computer-based interactive systems. It is intended to be used by those managing design processes and is concerned with ways in which both hardware and software components of interactive systems can enhance human-system interaction. There are existing standards which provide for user profiles including: • ETSI EG 202 116 [i.10] gives guidance to ICT product and service designers on Human Factors issues, good Human Factors design practices, and relevant international and national standards. The guidelines are intended to encourage a "Design for All" approach to making products and services accessible to as many people as possible, including elderly people and persons with disabilities, without the need for adaptation or specialized design. • ETSI TS 102 747 [i.11] defines an architectural framework supporting the personalization and user profile management concepts. • ETSI ES 202 746 [i.12] specifies a set of user profile preferences and information settings for deployment in ICT services and devices for use by ICT users and suppliers. The concept of a user profile usually refers to a set of preferences, information and rules that are used by a device or service to deliver a customized version of capabilities to the user. In practice, most devices and services contain profiles specific to that product and unrelated to any other. This requires that, on change of service or device, the user has to re-educate themselves in how to personalize their services or devices and re-enter their information and preferences. This often results in variable success rates and user satisfaction. |
9612427cf1aa38840a14974b2ee90b89 | 104 027 | 6.6 Ethics Considerations | With SCS enabling highly personalized experiences for consumers the advent of AI-driven personalization presents opportunities to improve user engagement and experience. However, this gives rise to concerns and issues about the ethical use of AI, potential risks and hazards, and the need for suitable safeguards to protect the rights and well-being of consumers, although AI has a vast amount of promise (for example see [i.13]), the codification of such protection is addressed in the seven key requirements provided by the European Commission concerning the adoption of trustworthy artificial intelligence solutions (see the EU TAi Guidelines [i.14]). Table 1 below considers the alignment of each category with such requirements. Whilst it is reasonable to suggest that any developer has to ensure that their product does not give rise to an ethical dilemma it is not reasonable to define ethical constraints in a standards environment. However in ETSI the wider requirements of [i.14] are addressed in the work programme of TC SAI [i.34]. ETSI ETSI TR 104 027 V1.1.1 (2025-10) 24 NOTE: In ETSI a general decision has been made not to define any standards for ethics as ethical behaviours are not codifiable, rather many of the consequences of ethics are addressed in ensuring accessibility (see clause 6.5 above), and in ETSI's codes of conduct for members that are available in ETSI Directives [i.35]. Table 1: Concerns and Solutions in AI-Powered Personalization Category from [i.14] Main Contribution Significance Recommendations Privacy and Data Security (Requirement #3) Emphasizes the importance of protecting individuals' personal information when using AI for personalization. It addresses the risks of data breaches and unauthorized access, advocating for robust data protection measures and compliance with privacy regulations like GDPR. Ensures that consumers' privacy rights are respected and their personal data is secure, fostering trust and preventing misuse. Data Minimization Anonymization and Encryption Regular Audits Incident Response Plan Federated Learning Algorithmic Bias (Requirement #5) Highlights the potential for AI algorithms to perpetuate or amplify existing biases in the training data, leading to discriminatory outcomes. There are frameworks for identifying and mitigating these biases to ensure fair treatment of all consumer groups. Promotes fairness and equality by preventing biased recommendations and exclusionary targeting, which can have adverse societal impacts. Bias Detection Frameworks Human-in-the-loop Transparency Reports Bias Mitigation Techniques Diverse Training Data Federated Learning for Bias Reduction Consumer Manipulation (Requirements #1, #3) Examines the ethical concerns related to the potential manipulation of consumers through hyper-personalization. It is about how AI-driven personalization can exploit behavioural data and psychological insights to influence consumer behaviour. Protects consumers' autonomy and agency by ensuring that personalized practices do not unduly influence or manipulate their decisions. Ethical Design Principles for example informed consent User Feedback Mechanisms Behavioural Data Safeguards Transparency in Personalization for example using explain ability tools. Ethics Training for developers Social Repercussions (Requirement #6) Explores the broader societal impacts of AI-powered personalization. It emphasizes the need for supportive policies and programs to mitigate these risks. Addresses the long-term societal implications of AI technologies. Community Engagement Sustainability Initiatives Ethical AI Certifications Transparency and Accountability (Requirements #2, #5) Stresses the importance of transparency in AI systems to understand how decisions are made and to identify potential biases and errors. It calls for accountability mechanisms to assess the ethical implications of AI driven personalization. Enhances trust and accountability by making AI decision-making processes more transparent, allowing for better oversight by users, policymakers, and regulators. Explainable / Explicable AI Audit Trails Regulatory Compliance Third-Party Audits User Education for example explain how AI systems impact them ETSI ETSI TR 104 027 V1.1.1 (2025-10) 25 7 Recommendations for further specification of ACIFO in SCS |
9612427cf1aa38840a14974b2ee90b89 | 104 027 | 7.1 General requirements for the Digital Ecosystem | |
9612427cf1aa38840a14974b2ee90b89 | 104 027 | 7.1.1 Overview and introduction | The digital ecosystem (see Figure 9), is given as a digital representation of "reality", independent of applications, and is built on the following characteristics: • Core paradigms: - "softwarization/programmability" (software-defined infrastructure, APIs, IaC); - the "as-a-service" operating model (platform thinking with DaaS/NaaS/PaaS/SaaS); and - pervasive "virtualization" across E2E continuum. • Autonomy by design (AI + IoT). - The combination of AI and IoT shifts the ecosystem from merely automated to autonomous: systems that sense, decide and act. • Capability-driven governance (e.g. ODA). - Use a capability framework to describe what the organization should do to achieve desired outcomes. Implication for the userware: the userware could be engineered as an autonomous, context-aware layer that orchestrates services on the user's behalf. Figure 9: Generic Architectural Components of a digital ecosystem The application of the fundamental questions of the ZT-Kipling method (ETSI TS 104 102 [i.17]) to the ACIFO dimensions are explained below. ETSI ETSI TR 104 027 V1.1.1 (2025-10) 26 Table 2: Application of ETSI TS 104 102 [i.17] in ACIFO Dimensions ACIFO Dimension ZT-Kipling questions (from [i.17]) What Why How Where Who When Architecture clause 7.1.2 What is the Overall Structure? Why is this architecture designed this way? How is the overall architecture structured? Where does the ecosystem operate and its components reside? Who are the key actors involved in the ecosystem? When does the architecture's life-cycle occur? Communication clause 7.1.3 What is the communication type? What is the intent or purpose of the communication? How are communicati on protocols and patterns implemented ? Where do communications flow? Who selects and manages the communication protocols? When are communication protocols and parameters designed, implemented, and managed? Information clause 7.1.4 What is the data? Why is that data (in particular) chosen? How is the data used? Where is the data? (logically and geographically)? Who owns and is liable for the data ? When is that data meant to be available? Function clause 7.1.5 What services and capabilities does the ecosystem provide? Why is this function considered value added? How are the services build and deliver ? Where is the function activated? Who activates, controls and manages every function? When is the function activated? Organization clause 7.1.6 What are administrative domains regulating the digital ecosystem? Why this organization? How do entities collaborate within this organization? Where are the organizational entities of the ecosystem located? Who does what (roles and responsibility)? When does the organizational structure evolve? |
9612427cf1aa38840a14974b2ee90b89 | 104 027 | 7.1.2 The architectural dimension | The architectural dimension defines the overall structure designed to achieve predefined objectives. This structure is characterized by specific properties, and compliance with the architecture implies adherence to these properties, making any architecture inherently semantic. The overall system architecture integrates both its logical components (i.e. software) and its physical infrastructure (i.e. Equipment, Topology) following the "as a service" model. The digital ecosystem relies on components that provide: • Transparency of Access: Users should be able to interact with local or remote components seamlessly and uniformly across the architecture. • Transparency of Location: Users should not be required to be aware of the physical or logical placement of components within the architecture. • Transparency of Concurrency: Components can be simultaneously shared or invoked by multiple users. • Transparency of Scalability: The system can be expanded or reduced without disrupting user experience. • Transparency of Faults: Users remain unaware of error-handling processes, with the system ensuring consistent service quality. This approach to the architecture design inherently implies a distributed architecture in terms of both processing and data management. • The logical architectural blocks of a digital ecosystem are organized into two primary views: - The User View; and - The Provider View. ETSI ETSI TR 104 027 V1.1.1 (2025-10) 27 • The User View represents all components that directly interact with the end-user. This includes: - Userware, UIS, IoT, Smart Interface, and their supporting components. • The Provider View includes the components that deliver services and manage data on the backend: - Serviceware, Infoware, AI. This approach to the architecture domain optimizes the structure and aligns to the strategic and business goals of the deployment (e.g. Green Computing, QoS-based, Privacy-based). This is then achieved by further adoption of an Open Distributed Architecture (ODA) to achieve goals of openness and distribution that in turn encompass the intended goals of transparency identified above. The digital ecosystem's architecture is oriented toward a "user-centric" model, that pre-supposes that the services are always available irrespective of the format of the user's device and of the user's location. To achieve this, the architecture is expected to be able to transparently handle complexity, ensuring at minimum transparency in terms of access, location, concurrency, scalability, and fault tolerance. Addressing the ZT-Kipling criteria [i.17] in more detail reveals the following for the architectural dimension: • Where identifies a number of administrative domains for various forms of service provider: Platform as a Service (PaaS), Network as a Service (NaaS), Device as a Service (DaaS), Software as a Service (SaaS), User Platform as a Service (UPaaS), with the internal and external qualifier that conforms to the main actor. There is no strict limitation to the nature of the architecture within the digital ecosystem, thus each of dew, edge, fog, cloud are equally valid. • Who considers the actors, stakeholders, and owners related to the digital ecosystem and is primarily defined in the logical view and the business context , as it deals with roles, responsibilities, and interactions. • When can be understood in three key architectural contexts: - "Think" is the most strategic view of time, that acknowledges that Architecture is not static, rather it evolves and as a consequence requires anticipation and planning to enable that change and adapt in the future. - "Build" describes the timing related to how the ecosystem is built, deployed, and maintained. - "Run" describes the temporal constraints and behaviours of the ecosystem while it is running and is a fundamental part of the logical and physical views. |
9612427cf1aa38840a14974b2ee90b89 | 104 027 | 7.1.3 The communication dimension | The UIS/SCS is expected to be a persistent object in the system and to interact with the "conventional" APIs that represent any component service's configuration and personalization entity with the added consideration that the UIS adopts a common exchange protocol (i.e. there is an expectation that each component service's configuration and personalization entity is accessed by a common service level protocol (e.g. HTTP/S using JSON (self-defining) data structures). The communication defines the different communication protocols and interactions of the service components. The UIS/SCS is expected to be a persistent object in the system and to interact with the "conventional" APIs that represent any component service's configuration and personalization entity with the added consideration that the UIS adopts a common exchange protocol (i.e. there is an expectation that each component service's configuration and personalization entity is accessed by a common service level protocol (e.g. HTTP/S using JSON (self-defining) data structures). In the context of Smart Customized Services (SCS), personalization is not limited to the adaptation of content or functionality to an individual. Analysis, through the ACIFO model, shows that it also results from organizational choices regarding data processing and governance, which dynamically adapt to the evolving user context and preferences. ETSI ETSI TR 104 027 V1.1.1 (2025-10) 28 The communication dimension defines how information is exchanged between the architectural blocks of the digital ecosystem. It establishes the protocols and models that govern all interactions, ensuring a clear and purposeful flow of data across the system. The application of ZT-Kipling [i.17] considers this in more detail below: • What is the communication type that allows determination of the communication protocols in the different layers of the ISO model in relation to the different architectural blocks of the ecosystem. This can be further characterized: - "Conventional" or Open API. - Open API/AI should facilitate a zero-contact approach (no human intervention, everything is automated). - A protocol which facilitates the composition of services and fosters a dynamic and collaborative ecosystem. • Why allows for the determination of the purpose or reason for the connection/communication link. It clarifies the semantic meaning of the interaction and nature of process as either an interactive or an automated process: - Is it a Command (telling a service to do something); or - a Query (asking for information); or - an Event (notifying that something has happened). • How allows determination of the concrete methods and technologies used to implement the communication patterns and seeks to explain how the protocols are selected and configured to satisfy the system's technological constraints and architectural drivers. • Where addresses the concern regarding direction and scope of communications flows. It therefore identifies the communication between every architectural block, ensuring that transmission and reception occur end-to-end (i.e. at both endpoints). • Who helps to identify the person, team or AI agent that selects communications flow based on the available topologies and the requirements of the application. And who manages them? Internal and external network administrators. • When is then understood in three key architectural contexts Think, Build and Run, in accordance with the architectural blocks. The communication parameters management are particularly crucial during the "Run" phase. |
9612427cf1aa38840a14974b2ee90b89 | 104 027 | 7.1.4 The Informational Dimension: | At the foundation lies data, which serves as the informational backbone of personalization. This dimension integrates: • Smart Identity: Complete representation of users, i.e. their potential profile where their preferences are found, behaviour patterns and knowledge. • External Data: Environmental conditions, service-related metadata, domain-specific datasets, and AI-enriched information. Data in this context is complete, contextualized, and enriched through AI-driven inference and domain expertise. It defines the scope of personalization possibilities and dictates how services can be adapted to the user. This knowledge base (UIS) becomes reactive through the "active profile", i.e. following the "context awareness" which encompasses a rich set of contextual factors, including temporal information (time, day of the week), spatial data (location, environment), device characteristics (smartphone, wearable, computer), social interactions (alone, with friends, in a meeting) and ambient environmental conditions (weather, traffic, noise level). This ubiquitous awareness is the main factor enabling the provision of relevant, fast and non-intrusive proactive services that fit perfectly into the user's life. ETSI ETSI TR 104 027 V1.1.1 (2025-10) 29 The Information Dimension provides a complete blueprint for all data within the digital ecosystem independent of applications. This includes defining the types and value of information managed by the system, clarifying why it is collected to generate insights, enable services, and drive business decisions. It also establishes clear frameworks for data's entire lifecycle, from when it is created, to how it is secured and managed, and where it resides. Ultimately, this dimension assigns accountability by identifying who owns the data and is responsible for its integrity, ensuring information remains a trusted and valuable asset: • What: It is the digital representation of reality, independent of applications. The data in a digital ecosystem refers to the collection of discrete or continuous values that convey information. All entities in the digital ecosystem are represented as an intelligent data object. • Why: Data is chosen based on its relevance to a specific purpose or research question. It should have sufficient be capable of answering the posed questions. Ultimately, data is chosen to create value, provide insights, and drive business decisions. • How: Data is used in a multitude of ways, from basic input for computational processes to a source of insights for advanced analytics. In a broader sense, data is the foundation for creating information, knowledge, and intelligence, enabling tasks like machine learning, predictive analytics, and process automation. • Who: Data ownership is a formal role that establishes accountability and liability for data integrity and management. • Where: Data is stored both logically and geographically. Logically, it can be organized in a hierarchy from bits and fields up to files and databases. Cloud providers allow for data to be stored across different geographical regions and availability zones and exposed via APIs (Data portability). • When: Data is available based on its storage lifecycle, which can be either ephemeral or persistent. |
9612427cf1aa38840a14974b2ee90b89 | 104 027 | 7.1.5 The functional Dimension | To ensure a seamless and coherent user experience, the functional dimension relies on SCS. The application is constructed following an as-a-Service composition model (see ETSI TR 103 437 [i.25], page 13), enabling service components to be independently added, removed, or composed without compromising the global service architecture. This model ensures customization, flexibility in service composition, adaptability of offered services, and on-the-fly deployment. Essential properties for this model are: • Statelessness: Each service consistently processes requests without retaining any request-specific or contextual information. Operations should function independently of prior invocations. • Autonomy: Services should execute their functionalities independently, without requiring interaction with other services or human intervention, effectively serving as "black boxes". • Loose Coupling: Connections between services should be flexible rather than rigid, eliminating functional dependencies and allowing for adaptable service compositions. Users can thus dynamically modify service combinations to suit their specific requirements. • Cohesion: Services are logically coherent and self-contained, delivering meaningful and consistent functionality recognized by potential users. Internally, each service's logic is cohesive and self-sufficient. • Abstraction: Beyond basic service descriptions in catalogues and SLAs, internal service logic should remain abstracted from external environments. For software engineering, the properties of reuse and mutualization are expected to be present: • Reuse: Facilitates the development of new services by leveraging generic interfaces (usage, control, management), promoting efficient software engineering practices. • Mutualization: Services should support multi-tenancy, allowing simultaneous access by multiple users, thereby reinforcing the loose coupling principle fundamental to Service-Oriented Architecture (SOA). ETSI ETSI TR 104 027 V1.1.1 (2025-10) 30 To enable effective SCS management, the properties of exposition, auto-control, and ubiquity are essential: • Exposition: Involves cohesive service descriptions and registration in service catalogues, detailing functional and non-functional aspects, including inherent QoS, thereby enabling third-party actors to select or assemble services based on specific competencies and profiles. • Auto-control: Services should autonomously monitor and control their behaviours, particularly non-functional aspects, using autonomic management approaches, thereby quickly identifying and managing component-level issues. • Ubiquity: Defined as functional equivalence across multiple service components, ubiquity groups similar services providing identical functionalities and QoS, irrespective of underlying implementation details. This facilitates scalability, enhanced availability, redundancy, and quality of service management. Services can be offered by various providers located anywhere, including integration within IoT gateways. Users compose or link these services to build applications tailored to their needs. With the rapid increase of IoT services, complexity grows correspondingly, necessitating stringent control, particularly in critical applications. Effective application composition and structuring require controlled service components, with end-to-end QoS management. Transparency regarding failures (a micro-service property) is assured through comprehensive QoS monitoring, allowing faulty components to be seamlessly replaced by equivalent community components. Each service component is conceived as a self-contained and reusable building block, comparable to a "packaged business capability." The fundamental principle of SCS is that complex, value-added user experiences are not pre-built, but dynamically composed by combining services in innovative ways. This composable nature allows the system to be "personalized" and to adapt its functionality to the user's specific context in real time. Indeed, intelligent personalized service marks a fundamental departure from traditional reactive service delivery models. It is conceptualized not as a static application, but as a dynamic and intelligent composition, designed to anticipate and proactively respond to user needs. SCS is designed to go beyond the traditional request-response cycle. Based on the "active profile," it actively offers services and makes suggestions based on a deep understanding of the user's predicted intentions and the current context. This involves implementing systems capable of "predictive assistance" and anticipating user needs before they are explicitly expressed. NOTE: SCS integrates existing services to the UIS as the proxy of the user and the SCS entity may build new services from existing system capabilities that are orchestrated by the user's profile and preferences represented by the UIS. The Functional View defines the core capabilities and services the ecosystem provides. It focuses on the processing logic and specific actions the system performs to fulfil its purpose, ultimately providing a clear understanding of the tangible value delivered to users and other systems. Applying the ZT-Kipling criteria [i.17] in more detail to the functional dimension reveals the following: • What: The "What" is the service map, which represents the digital ecosystem's processing capabilities. • Why: In a collaboration context, each provider offers specific aaS components (value-added), knowing that all the core services are reusable. • How: Built with as-a-Service properties and exposed via APIs. Service delivery (all-inclusive) is a composition of services. DevOps practices or low-code platforms (within an agile approach) can accelerate service creation. • Where: In a virtualized context, activation is location-agnostic. • Who: Based on responsibilities and organization, there could either be: One Provider, or a collaboration of Providers or the user (see clause 7.2). • When: It defines the workflows and triggers that initiate a function, a scheduled event, or a system event. Functions are executed by Userware on user-side devices, by IoT devices on the network's edge, and by the provider's Serviceware within their data centres. This distribution allows for optimization based on factors like latency, scalability, and data proximity, reflecting the shared nature of execution in the digital ecosystem. ETSI ETSI TR 104 027 V1.1.1 (2025-10) 31 |
9612427cf1aa38840a14974b2ee90b89 | 104 027 | 7.1.6 The Organizational Dimension | The organizational dimension determines data responsibility, where, and how data is processed and stored, spanning the dew, edge, fog, and cloud continuums. The key elements of this process are: • Data Governance: Establishing control mechanisms to manage data integrity, access rights, and retention. • Security and Privacy: Ensuring user data security, trust boundaries, and user consent policies (see clause 6). • Strategic Resource Positioning: Determining the optimal processing location based on defined governance. Applying the XT-Kipling criteria [i.17] assists in defining the role of any actor and clarifying which actor is responsible for which action: • What: This describes the interconnected set of digital assets and services that form the ecosystem based on the strategy. Ways of working and governance: Identify the roles and responsibilities of each architectural block and all other entities within the digital ecosystem. Personalization (UIS/SCS) is the responsibility of serviceware or userware [i.38]. • How: How the entities collaborate within the Digital Ecosystem. • Where: The location of the architectural organizational entities: "Where are entities (SCS) and enabling platforms located?". This defines the distribution of entities for all actors, including users and providers. • Who: "Who is accountable and who enables delivery?" This identifies all the entities participating in the ecosystem. architectural blocks, Engineering leadership, platform leads, security/compliance, and community leads for standards and skills. Personalization could be achieved by serviceware or userware [i.38]. • When: "When is each of planning, monitoring, and auditing done?". • Why: The organization model is chosen for effective management and to ensure that all stakeholders are considered. It answers the question "Why this organizational model matters ?" by providing the strategic rationale (personalization UIS/SCS). This model is designed to align strategy to execution, improve throughput and reliability, and scale delivery with predictable quality and controlled risk. |
9612427cf1aa38840a14974b2ee90b89 | 104 027 | 7.2 UIS/SCS requirements User side (userware) | |
9612427cf1aa38840a14974b2ee90b89 | 104 027 | 7.2.1 Userware Interactions with the ecosystem components | To outline and highlight indicative requirements of UIS/SCS on the user-side within a digital ecosystem, the organizational model should define "who does what", according to the user's chosen autonomy level (see "the cursor" [i.25]). The userware and its interface should make simple and explainable controls, exposing what actions are taken on the user's behalf while honouring consent and preferences. It should also ensure data control and sharing: users retain their data, grant purpose-bound access to providers at their discretion, and can review or revoke that access at any time. This is essential because today's users carry an ubiquitous network (smartwatch, smartphones, tablets, etc.) nearly invisible yet requiring coordination and management, which the userware provides. Finally, the model specifies collaborative service composition with providers clear roles, interfaces, and responsibilities so user policies and preferences are respected end-to-end. To fulfil this role and this type of collaboration, all the services necessary for the user could be in the userware (see Table 3) with the properties of autonomy, simplicity, security and reliability. ETSI ETSI TR 104 027 V1.1.1 (2025-10) 32 Table 3:UIS/SCS Requirement in Userware Ecosystem Components from the Userware perspective UIS General Requirement SCS General Requirement UIS (Smart identity) • Provide the creation, control and management of potential profiles ([i.24], clause 4.3). • Ensure data distribution and sharing with proper control and management. • Enable secure integration of profiles into service workflows. • Ensure interoperability of user identity across services. • Enable clear visualization through the smart interface. IoT Sensors (M2M, environmental, wearables) • Guarantee transparent data collection (in real time) with user configuration. • Ensure data is transmitted to the user profile. • Ensure Sensor Management (synchronize, Configuration, encryption, trust environment, etc.). • Enable secure transmission to provider. • Ensure service reliability from heterogeneous sensor inputs. Userware (smart interface, service management) • Ease of Use: Provides data (knowledge) to the smart interface to enable an intuitive user experience. • Provide seamless service discovery, and execution. • Provide simple composition of services. Autonomy Based AI: • Enable user to configure how AI process data. • Provide different levels of autonomy over Data. • Enable selection of AI functionalities. • Allow local handling of preferences and composition of services. • Adapt services dynamically to user's context. Security: Ensure the properties of availability, integrity, and confidentiality. • Enable protection of personal data in services( Encryption, anonymization, fuzzification, etc.). Reliability: Enable the properties of QoS, robustness, fault tolerance. • Enable redundancy, pertinence. Networkware (4G/5G, edge, VPN) • Ensure the properties of availability, integrity, and confidentiality. • Ensure availability of data for continuous connectivity. • Ensure availability and continuity of connectivity for user operations. • Guarantee secure and reliable communication between distributed services. • Enable Quality of Service (QoS) monitoring. Serviceware (PaaS, SaaS) • Allow users to filter or control access to personal data. • Ensure timely and understandable feedback on actions taken. • Ensure reliable service execution and orchestration. • Provide secure and context-aware services. Infoware (knowledge base, ontologies) • Guarantee privacy parameters. • Guarantee compliance with data governance and retention policies. • Support knowledge-driven orchestration for personalized services. • Ensure semantic interoperability across services. ETSI ETSI TR 104 027 V1.1.1 (2025-10) 33 Ecosystem Components from the Userware perspective UIS General Requirement SCS General Requirement AI (ML/DL, GenAI, Agentic AI) • Allow user control over how AI-based recommendations are applied. • Ensure transparency about AI model use. • Guarantee ethical, explainable, and reliable AI-driven decision-making. • Continuously improve services using feedback loops. • Integrate AI/ML models into workflows while protecting user data. • Ensure fairness, privacy, and accountability in AI operations. |
9612427cf1aa38840a14974b2ee90b89 | 104 027 | 7.2.2 User Centric Vision | According to user-centric vision, a connected ecosystem is designed to deliver seamless digital services through multiple interacting layers (Figure 10). Figure 10: User vision of integrated ecosystem Service providers offer digital services supported by an underlying network layer that ensures reliable connectivity. Access networks bridge users to these services, while the user layer enables personalization, real-time adaptation, and a smooth experience. ETSI ETSI TR 104 027 V1.1.1 (2025-10) 34 Annex A: Assist-IoT project overview NOTE: The description that follows is sourced from the Assist-IoT website [i.42] with additional editing to map aspects of the project to the requirements of UIS/SCS as outlined in the main body of the present document. The ASSIST-IoT project addresses research for the design, implementation and validation of an open, decentralized reference architecture, associated enablers, services and tools, to assist human-centric applications in multiple verticals. ASSIST-IoT will design, implement and validate, in a realistic, measurable, and replicable way, a unified innovative multi-plane (semi-)autonomous decentralized edge-cloud reference architecture, supplemented by cross-cutting digital enablers. The architecture will support continuous integration and long-term sustainability of domain-agnostic, interoperable, capable, intelligent, distributed, scalable, secure and trustworthy IoT ecosystems. ETSI ETSI TR 104 027 V1.1.1 (2025-10) 35 Annex B: i-Tour project overview The i-Tour project of 2008/9 through to 2012 was predicated on the increasing success of navigation technologies, and the expected increase in the diffusion and acceptance of transportation services based on localization technologies. Widespread diffusion of novel info-mobility services promoting multi-modal transport were anticipated to have a profound impact on citizen's lives across EU, in terms of: 1) Safety, as 40 000+ people die on Europe roads each year with a cost for the European economy of approx. 200 B€ p.a. 2) Efficiency, as congestion costs an estimated in 1 % of EU total GDP or 100 B€ p.a. 3) Environmental sustainability, as transport accounts for 30 % of total energy consumption in the EU, with the vast majority being consumed by road transport. At the time when i-Tour was proposed most of the relevant initiatives in multi-modal transport routing, whilst supporting routing through public transport networks, did not (could not) support personalization, in terms of user travel preferences, nor could they provide support of real-time information, nor did they promote an open approach based on common standards. Ideal route optimization has to take into account a complex set of conditions far beyond parameters such as travel times to include factors such as costs, preferred transport means, number of modality changes, pollution minimization, real-time public transport load (e.g. number of passengers currently on a given train), weather conditions (e.g. to suggest walking only in dry conditions). Further optimization at the travel information level has to take into account not only the current conditions but also the effects that the users of the system, as a community, infer on the traffic conditions themselves through new demand management strategies that account for the level of acceptance of the guiding system and adjust the overall system conditions accordingly. The i-Tour project addressed the demand chain aspects identifying a need to support and promote sustainable and environmental-friendly travel preferences as essential. On the supply chain side the i-Tour project identified requirements to create ICT tools based on innovative strategies to promote clean transport based on rewarding mechanisms that can encourage sustainable travel choices. In addition the project identified that current (i.e. the year 2009 or so) data acquisition and distribution strategies, based on centralized authorities, needed to evolve towards distributed federated infrastructures whereby, through open architectures, providers can expose their services and benefit from those available within the infrastructure. A large part of the i-Tour project thus addressed recommender systems as an early AI like approach to sharing experiences of the transport system (i.e. pre-dating more recent examples such as Waze [i.43]), and considered reward schemes to encourage use by consumers, and involvement of providers. The i-Tour concept, although pre-dating UIS/SCS shares many of the characteristics: • User as both consumer and provider of data. • Recommender systems and other collaborative tools to share knowledge and experience. • Micro-services composed into user services on demand. • Strong support of open standards. ETSI ETSI TR 104 027 V1.1.1 (2025-10) 36 Figure B.1: Initial concept of i-Tour approach to the SUMA use case ETSI ETSI TR 104 027 V1.1.1 (2025-10) 37 Annex C: i-locate project overview The role of the i-locate project was to take advantage of the opportunities provided by increasingly accurate indoor localization technologies, for instance based on RFID (active or passive) or Wi-Fi®, to expand the scope of GIS to include indoor spaces (i.e. "indoor GIS"). The development of asset location and tracking technologies for integrated indoor and outdoor scenarios (the latter being typically GNSS-based, including Galileo), was seen as having the potential to be a key driver for innovation and business activities in several fields including -among others- logistics, facility management and retail. Improving location and tracking in the public health domain can bring to significant advantages in terms of improved quality of services and lower risks. A notable example of this can be found in Italy, where location of pharmaceutical products through labels, from production to sales at pharmacy, has allowed higher security and control well above average (0,1 % risk in Italy against 1 % in Europe and 6 - 7 % globally). Modern hospitals and health care centres in fact are extremely complex systems of systems where efficient and accurate asset tracking and management is vital. The leading principles of today's integrated quality management procedures, predicate that each facet of a product or service provided is subject to continuous analysis and assessment. Ensuring open data access to asset information can be very beneficial to improve quality of services and reduce costs. It should be noted that, due to the sensitive nature of some of the data (e.g. personal health records) the open data nature of critical information only has to be limited to the boundaries of the health care systems. ETSI ETSI TR 104 027 V1.1.1 (2025-10) 38 Annex D: Detail of regulatory factors to be considered in UIC/SCS D.1 Privacy aspects D.1.1 General overview The UIS/SCS has to conform to societal expectations of privacy protection and to also conform to any legal restrictions. To achieve this some security capabilities are required (shown in more detail in clause D.2 below), and it is expected that the overall system conforms to expectations of the GDPR [i.21] or equivalent national or regional legislation outside of the EU. The UIS/SCS system has to be clear about the use of data particularly if the AI/ML model at the heart of UIS/SCS modifies the relative weighting of data elements. It is also shown that there are consequences of data export of anonymized data that may result in de-anonymized data if multiple datasets can be used by an AI/ML system to isolate characteristics of the data subject and to single out the data subject. A further consideration of UIS/SCS is that it is assumed that there are multiple services and therefore the data subject is likely to be represented by a proxy (see also considerations for accessibility). A wider concern of applying existing data protection legislative frameworks to the UIS/SCS case is that consent may become unclear and therefore the UIS/SCS governance model has to accommodate the UIS/SCS acting somewhat independently of the user. EXAMPLE: In the SUMA use case whilst a query may be anonymized for any particular phase of a journey, an observer, which may be the UIS/SCS itself, may be able to single out the user even if the UIS itself is a protected element of the system. D.1.2 Identification of Data Controller The data controller in UIS/SCS is notionally the user as UIS/SCS acting for the user composes a service from micro-service elements, but the end user is not a formally recognized data controller in the meaning of GDPR. In UIS/SCS the data controller acts on behalf of the data subject. NOTE 1: For SCS the user to data controller relationship is different from the conventional view as the user, through their representation as an AI-enabled proxy, is intended to be the lead determinant of data usage. NOTE 2: There are aspects of liability for data misuse that apply to the data controller role and it is likely that entities offering micro-service components will have to address how they act in the context of UIS/SCS when subject to the legal requirements of GDPR. D.1.3 Identification of Data Processor The data processer acts on data as allowed by the data controller and the data policies of the data subject and is represented in UIS/SCS as the "as a service" entities that enable the user's service. D.1.4 Identification of affected user (data subject) The data subject is the entity on whose behalf the UIS/SCS acts. ETSI ETSI TR 104 027 V1.1.1 (2025-10) 39 D.1.5 Other privacy impacting aspects Article 20 of GDPR [i.21], the "Rights to portability", gives the data subject (i.e. the affected user) the right to obtain and transfer their data to a different service, and the data controller should facilitate this transfer. This overlaps with Article 6(9) of the EU Digital Market Act (DMA) [i.44] and introduces a new data portability right which stipulates that gatekeepers have to provide end users and authorized third parties with "effective portability of data provided by the end-user of generated through the activity of the end user". NOTE: Gatekeepers in the DMA are defined as having a significant impact on the internal market, providing a core platform service that is an important gateway for business users to reach end users, and enjoying an entrenched and durable position in its operations, or it is foreseeable that it will enjoy such a position in the near future. While it does not adopt the term "right to data portability" the Data Act [i.18] instead, introduces a horizontal cross- sectoral data access right to consumers and businesses that encompasses "data generated by the use of the product or related services". This suggests that any AI manipulated data, or any augmented data is within its scope. It emphasizes the complementarity of this with the right to data portability in GDPR, including the right to receive personal data and to port data to other controllers. With regards to the scope of data covered, there is an overlap and some synchronism between the three Regulations: the GDPR regulates the processing of personal data, and the DMA and the Data Act include the processing of personal data and non-personal data by gatekeepers and IoT product manufacturers and services, respectively. Figure D.1: GDPR, DMA and Data Act process personal and non-personal data Focusing only on the right to data portability of personal data, the synchronized overlaps between the Regulations are modified. The GDPR has the smallest scope of the three Regulations since it is restricted to personal data that has been provided to a controller under the basis of consent or contract, whereas the DMA and the Data Act govern the processing of personal data independently of the lawful basis for processing, being cross-sectoral regulations that encompass different technologies, especially the Data Act, that has a broad scope of IoT technologies. Under the three Regulations, the GDPR covers all categories of personal data processors, and so has the broadest scope of the three. The DMA's scope is restricted to stakeholders who qualify as gatekeepers under the Act, and the Data Act's scope is restricted to IoT manufacturers and suppliers of related services, except for SMEs. ETSI ETSI TR 104 027 V1.1.1 (2025-10) 40 Figure D.2: Stakeholders affected by the different rights to data portability in the GDPR, DMA and Data Act Within this multi-layered right to data portability, individual users potentially have more control over their data-both personal and non-personal-in the context of a multi-sectoral setting. This overlap is essential for UIS to function. Though at present there are a series of series of technical and legal interpretation-based obstacles that block its full implementation. D.2 Security In assessing the security requirement for SCS/UIS there are a small set of principles to be adhered to: • Minimize the attack surface. • Impose a principle of least privilege to allow the use of any asset. • Impose a principle of least persistence for the use of any asset. The general security provisions that apply to both privacy protection, and data protection, are those of least privilege and least persistence. In both cases the role of data minimization is critical. A number of approaches to this exist, and many require the detailed process of a privacy and data impact assessment exercise. This essentially requires that the technical design, and policy design, of a system determines the answer to a number of questions prior to, and in the execution of, a system. NOTE 1: The principle of least privilege is one that has a very long history predating the ICT domain and embraces a number of concepts. The first of these is that an asset is of value and that things of value should not be shared to those not needing to have it, this then as a second concept introduces the idea that it is possible to determine who has the right to access, and this then extends to identifying the things that can be done with an asset and applying restricted rights to each of them. As an example, in the ICT domain a privilege may be one of read, edit, delete, or copy and a user may be granted one or more of these privileges. In summary least privilege access to a protected asset is to only allow those rights or privileges that are essential to perform the required task. In most access control systems that adopt least privilege the default is to deny (i.e. the least privilege is no privilege). NOTE 2: Similarly to least privilege the concept of least persistence has a very long history that predates the ICT era. The concept of least persistence is that access to an asset is not granted forever, rather that access is granted for only sufficient time to perform the requested action. Least persistence is seen in most network systems where a resource is limited and shared (e.g. radio bandwidth, network capacity). Least persistence then ties into resource management as well as to security by taking steps to ensure that a resource is not hogged by any user. ETSI ETSI TR 104 027 V1.1.1 (2025-10) 41 In addition to the general principles of least persistence and least privilege the right to access data is further addressed by access control, for which a general model is given in clause 6 of ETSI TS 102 165-2 [i.45] addressing the technical means of achieving access control and the models of access control. In this there are two (2) primary models that are considered: • Mandatory Access Control (MAC) - access to, and use of, the thing to which access is granted is wholly determined by the thing's owner. • Discretionary Access Control (DAC) - the use of the thing to which access has been granted is at the discretion of the user and not addressed by the thing's owner. In the UIS/SCS environment it should be assumed that the UIS base model is not changed without the knowledge and consent of the actual user it belongs to. Thus the relationship between the UIS and the services it enables through SCS is more likely to be of the MAC form than the DAC form in order to limit the release of personal data outside the controlled boundary. NOTE 3: In some use cases, for example the Health use case given in clause 5.4, there are aspects of data held in the system that intersect with the core of UIS/SCS but are not persistent to the user view of UIS/SCS. In such cases access control requires a large degree of contextual awareness in order to ensure a service can be offered, particularly if withholding that service places the user at risk. D.3 Data semantics and ontology The process of data portability, and of data interoperability, can be enabled by assuring that data is described semantically and to which a context can be attached, This requires that data has been structured to add meaning to it. In common practice an ontology is used to explicitly define the concepts and relationships within a domain, allowing machines to understand the data's semantic structure and to enable them to perform complex operations on it. EXAMPLE: The Smart Applications REFerence ontology (SAREF) framework of ontologies for IoT that enables different parties to interoperate with each other at the semantic level [i.23] The common concept of SAREF is that all existing data models/protocols can be incorporated into an ontology (i.e. a common vocabulary). This captures the meaning of a concept (i.e. semantics) rather than the specific data format in which the concept is encoded for data exchange at the underlying communication layer. For this to work manufacturers and service providers should enable their data to be portable as it enables interoperability. D.4 Data portability Article 20 of GDPR [i.20] suggests a framework for the practice of the right to data portability, that data subjects have the right to receive data in a structured, commonly used and machine-readable format. Two transfer options are offered: • Transfer of the data directly to the data subject; and - The user receives their data and is free to do what they want with it (c.f. discretionary access control (see clause D.2 above)). • Transfer of the data from one controller to another. - The other service (that the user requested be sent the data) receives the data and can use it within their product. The data controller has to make available to the user all the data that the user has provided either with their consent or through a contract and has to also include all the data resulting from their activity, in a machine-readable format, for example, a JSON, or RDF file. This is often done as ad-hoc downloads. ETSI ETSI TR 104 027 V1.1.1 (2025-10) 42 It is not intended that the user should just receive an overview or summary of their data. The goal of portability is to be able to reuse personal data immediately (or later) by integrating it onto another platform or service. So, for example, formats like PDF or XLSX files are not machine-readable data files, and they do not allow the transfer of the data to another platform or service as the file does not allow the user to reuse this data and is therefore in violation of their data portability rights. NOTE: There is a distinction here between machine processable and machine readable, the latter requiring the data to have sufficient direct semantic and contextual labelling to assure correct processing. The following general characteristics for machine readable data should be applied to all UIS/SCS data and to the use of data in associated services: • Reliability • Authenticity • Integrity • Usability The consequence of applying these characteristics is that, in addition to the appropriate semantic and contextual labelling, some attention is paid to data provenance (see also clause D.3 above). For UIS real-time (continuous) data transfers between data holders should enable interoperability between the user-chosen digital services. This can be enabled by Application Programming Interface (APIs) which enable service providers to make their digital resources (e.g. data and software) available over the Internet [i.20]. Contrary to ad hoc downloads, APIs can enable continuous real-time data portability and thus the smooth interoperability of the different actors, their technologies and services. In addition, data holders can implement several restrictions via APIs to better control the use of their data, including by enabling access based on the identity of API users, and the scale and scope of the data used. Also, a dedicated API may reduce the perceived necessity of 'data scraping' which requires users to grant third parties access to their online account to extract the data from the online interface and, in some cases, to execute transactions on the customer's behalf. Such activities may violate data holders' terms of use or the IPRs of third parties. Data portability regimes that take advantage of APIs may in this way increase the security of, and trust underpinning, data transfers while minimizing the risk of copyright violations. An example implementation of this data portability implementation is the Data Transfer Project (DTP) which is an open-source initiative which features data portability between multiple online platforms [i.22]. It provides a platform that allows individuals to move their online data between different platforms, without the need of downloading and re-uploading data. The ecosystem is achieved by extracting different files through various available APIs released by online platforms and translating such codes so that they are compatible with other platforms. D.5 Accessibility aspects Any implementation of UIS/SCS should comply with the European Accessibility Act [i.5], a legal instrument that aims to improve the functioning of the internal market for accessible products and services by removing barriers created by divergent rules in Member States. These covered products and services include: • computers and operating systems • ATMs, ticketing and check-in machines • smartphones • TV equipment related to digital television services • telephony services and related equipment • access to audio-visual media services such as television broadcasts and related consumer equipment • services related to air, bus, rail and waterborne passenger transport ETSI ETSI TR 104 027 V1.1.1 (2025-10) 43 • banking services • e-books • e-commerce The SCS will include many of these products and services. The SCS should conform to EN 301 549 [i.6], which can be applied to ICT-based products and services. This includes software (web pages, mobile applications, desktop applications, etc.), hardware (smartphones, personal computers, information kiosks, etc.), and any combination of hardware and software. To that end, the requirements of the standard are self-scoping. This means they consist of two parts; the first part is a precondition for the second part, which holds the actual requirement. If a product or service meets the precondition, then the product or service has to conform to the second part of the requirement. Also, applicable to the SCS is ISO 9241-210:2019 [i.7], which provides requirements and recommendations for human-centred design principles and activities throughout the life cycle of computer-based interactive systems. It is intended to be used by those managing design processes and is concerned with ways in which both hardware and software components of interactive systems can enhance human-system interaction. It should also be noted that a designer can go beyond the requirements in EN 301 549 [i.6], these are design for all [i.8] and universal design principles [i.9]. This includes design principles such as: • Provide the same means of use for all users: identical whenever possible; equivalent when not. • Avoid segregating or stigmatizing any users. • Provisions for privacy, security, and safety should be equally available to all users. • Provide choice in methods of use. • Eliminate unnecessary complexity. • Provide compatibility with a variety of techniques or devices used by people with sensory limitations. Design for all and universal design principles do go beyond what is required from current accessibility legalisation. They are ideal recommendations but not a requirement. Though they should be considered for the SCS for example if the user is colour blind, they should ideally need to only set one device or service to account for their colour blindness and any linked devices or services should copy or be able to access and use this setting. There are existing standards which provide for user profiles including: • ETSI EG 202 116 [i.10]. It gives guidance to ICT product and service designers on Human Factors issues, good Human Factors design practices, and relevant international and national standards. The guidelines are intended to encourage a "Design for All" approach to making products and services accessible to as many people as possible, including elderly people and persons with disabilities, without the need for adaptation or specialized design. • ETSI TS 102 747 [i.11]. The document defines an architectural framework supporting the personalization and user profile management concepts. • ETSI ES 202 746 [i.12]. It specifies a set of user profile preferences and information settings for deployment in ICT services and devices for use by ICT users and suppliers. The concept of a user profile usually refers to a set of preferences, information and rules that are used by a device or service to deliver a customized version of capabilities to the user. In practice, most devices and services contain profiles specific to that product and unrelated to any other. This requires that, on change of service or device, the user has to re-educate themselves in how to personalize their services or devices and re-enter their information and preferences. This often results in variable success rates and user satisfaction. ETSI ETSI TR 104 027 V1.1.1 (2025-10) 44 There will be several user characteristics and preferences that will apply independently of any particular product (e.g. a user's preferred language or their need for enlarged text). A key objective is that users should not be required to provide this information more times than is necessary. Users move from one situation to another throughout the day (e.g. at home, driving, working). In each of these situations, users may have different needs for how they would like their ICT resources arranged. Generally, products provide the user with ways of tailoring their preferences to these different situations. Users should be able to specify their context-dependent needs in ways that require the minimum need to understand the individual products. ETSI ETSI TR 104 027 V1.1.1 (2025-10) 45 Annex E: Example of Application of ACIFO model to tomato cultivation (user side ) E.1 Overview To illustrate how UIS/SCS works in practice, the example of smart tomato cultivation (clause 5.3), seen entirely from the user side is considered. The farmer is surrounded by sensors that continuously monitor the environment - temperature, humidity, pH, light, even images of the crops. All of this information flows into the UIS. Here, the data is not just raw numbers but visualized and explained through service components and the interface, in a way the farmer can understand and act upon. The important point is that the farmer stays in control if he so desires. When an anomaly is detected, experts and AI models can step in to provide deeper analysis and recommendations, but the system always makes it clear what is happening and why. The farmer decides whether to follow a recommendation or adjusts it to their preferences, and provides feedback. Figure E.1: Smart Tomato Cultivation (User Side) E.2 Functions and features E.2.1 Real-time environmental (Sensors → UIS) It is important to note that the "SCS agriculture management" is in the Userware. It contains: • Continuous comparison service for the incoming sensor data with predefined thresholds (e.g. for pH, humidity, or light levels). ETSI ETSI TR 104 027 V1.1.1 (2025-10) 46 • Synthesis and centralization service of all growth-related information for the tomatoes. • Visualization service across the smart interface. • Visual monitoring service of the crops by the cameras. E.2.2 Anomaly detection (Userware) The Userware constantly compares the incoming data with predefined thresholds (e.g. optimal humidity range, light exposure levels) and learned patterns. When irregularities are detected (e.g. early signs of water stress, unusual pH variation), the anomaly is flagged. E.2.3 Expert validation and AI model selection (Agronomy Expert) The anomaly report is sent to the Agronomy Expert, who evaluates the context and determines whether it requires advanced analysis. The expert selects the most appropriate AI model and configures its parameters. E.2.4 AI-based anomaly analysis (AI Engine) The AI Engine processes the anomaly data using the selected model. E.2.5 Corrective recommendations (Userware + Expert support) The processed results are returned to the Userware and validated by the Agronomy Expert. The system generates precise, actionable recommendations for the farmer (e.g. "Increase watering in Zone A by 10 % over the next 3 days"). E.2.6 Farmer decision-making and feedback (Farmer → Userware) The farmer receives real-time alerts and a dashboard with anomaly insights. He consults recommendations, takes corrective actions, and then provides feedback (yield, treatment success, crop health status). This feedback is integrated into the system to continuously improve anomaly detection accuracy and model performance. ETSI ETSI TR 104 027 V1.1.1 (2025-10) 47 Annex F: Bibliography • Exposito-Rosso, S., Cao, F.-X., et al.: "Research Report GDPR Data Portability: The Forgotten Right". • Reimsbach-Kounatze, C., Molnar, A.: "The impact of data portability on user empowerment, innovation, and competition", Going Digital Toolkit Note, No. 25, 2024. • "Data Transfer Project Overview and Fundamentals". • ETSI TR 103 875-1: "User Centric Approach in Digital Ecosystem; The Smart Interface; Part 1: Smart Identity: user digital clone". • ETSI TC SAI Work programme. NOTE: Visible at https://www.etsi.org/technologies/artificial-intelligence and https://portal.etsi.org/tb.aspx?tbid=913&SubTB=913#/. ETSI ETSI TR 104 027 V1.1.1 (2025-10) 48 History Document history V1.1.1 October 2025 Publication |
1a68fbff3dc809a5ccbe03dc51589d05 | 119 602 | 1 Scope | The present document defines a data model for lists of trusted entities, as well as bindings of such lists in various syntaxes allowing relying parties to establish and process lists of trusted entities. NOTE: The data model for a list of trusted entities aims to be an abstract generalization of the existing specifications of trusted lists provided in ETSI TS 119 612 [1]. The present document applies to any community aiming to establish a way to represent approval statuses of trusted entities as they are defined in the present document. The present document specifically applies to European Union lists of providers of person identity data, wallet providers, providers of wallet relying party access certificates, and public sector bodies issuing electronic attestations of attributes, through the specifications of specific profiles defined in Annexes. |
1a68fbff3dc809a5ccbe03dc51589d05 | 119 602 | 2 References | |
1a68fbff3dc809a5ccbe03dc51589d05 | 119 602 | 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 are not found to be publicly available in the expected location might be found in the ETSI docbox. NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee their long-term validity. The following referenced documents are necessary for the application of the present document. [1] ETSI TS 119 612 (V2.4.1): "Electronic Signatures and Trust Infrastructures (ESI); Trusted Lists". [2] ISO 3166-1:2020: "Codes for the representation of names of countries and their subdivisions — Part 1: Country codes". [3] ETSI TS 119 182-1 (V1.2.1): "Electronic Signatures and Trust Infrastructures (ESI); JAdES digital signatures; Part 1: Building blocks and JAdES baseline signatures". [4] ETSI EN 319 132-1 (V1.3.1): "Electronic Signatures and Trust Infrastructures (ESI); XAdES digital signatures; Part 1: Building blocks and XAdES baseline signatures". [5] ISO/IEC 10646:2020: "Information technology — Universal coded character set (UCS)". [6] ISO/IEC 6429:1992: "Information technology — Control functions for coded character sets". [7] ISO/IEC 2022:1994: "Information technology — Character code structure and extension techniques". [8] ISO 8601:2019 (parts 1 and 2): "Date and time — Representations for information interchange". [9] IETF RFC 3986: "Uniform Resource Identifier (URI): Generic Syntax". [10] IETF RFC 4514: "Lightweight Directory Access Protocol (LDAP): String Representation of Distinguished Names". [11] IETF RFC 5646: "Tags for Identifying Languages". [12] Recommendation ITU-T X.509: "Information technology - Open Systems Interconnection - The Directory: Public-key and attribute certificate frameworks". [13] IETF RFC 2368: "The mailto URL scheme". ETSI ETSI TS 119 602 V1.1.1 (2025-11) 9 [14] IETF RFC 3966: "The tel URI for Telephone Numbers". [15] ETSI EN 319 412-1 (V1.6.1): "Electronic Signatures and Trust Infrastructures (ESI); Certificate Profiles; Part 1: Overview and common data structures". |
1a68fbff3dc809a5ccbe03dc51589d05 | 119 602 | 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 this 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) 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. [i.2] Commission Implementing Regulation (EU) 2024/2980 of 28 November 2024 laying down rules for the application of Regulation (EU) No 910/2014 of the European Parliament and of the Council as regards notifications to the Commission concerning the European. [i.3] Commission Implementing Regulation (EU) 2025/1569 of 29 July 2025 laying down rules for the application of Regulation (EU) No 910/2014 of the European Parliament and of the Council as regards qualified electronic attestations of attributes and electronic attestations of attributes provided by or on behalf of a public sector body responsible for an authentic source. [i.4] W3C® Technical Report #20 Revision 7: "Unicode in XML and other Markup Languages". [i.5] The Unicode® Standard. [i.6] ETSI TR 119 001 (V1.2.1): "Electronic Signatures and Infrastructures (ESI); The framework for standardization of signatures; Definitions and abbreviations". |
1a68fbff3dc809a5ccbe03dc51589d05 | 119 602 | 3 Definition of terms, symbols and abbreviations | |
1a68fbff3dc809a5ccbe03dc51589d05 | 119 602 | 3.1 Terms | For the purposes of the present document, the terms given in ETSI TR 119 001 [i.6] and the following apply: list of trusted entity scheme operator: body that is responsible for the operation and/or management of the approval scheme under which the corresponding LoTE is published provider of person identity data: As defined in Regulation (EU) No 910/2014 [i.1]. provider of relying party access certificate: As defined in Regulation (EU) No 910/2014 [i.1]. provider of relying party registration certificate: As defined in Regulation (EU) No 910/2014 [i.1]. trusted entity: entity that is recognized as trustworthy within a given approval scheme for a specific scope or purpose wallet provider: As defined in Regulation (EU) No 910/2014 [i.1]. |
1a68fbff3dc809a5ccbe03dc51589d05 | 119 602 | 3.2 Symbols | Void. ETSI ETSI TS 119 602 V1.1.1 (2025-11) 10 |
1a68fbff3dc809a5ccbe03dc51589d05 | 119 602 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: CC Country Code EU European Union HTTP HyperText Transfer Protocol LoTE List of Trusted Entities LoTESO List of Trusted Entities Scheme Operator MS Member State PID Person Identity Data Pub-EAA Electronic Attestation of Attribute issued by a public sector body TE Trusted Entity URI Uniform Resource Identifier WRPAC Wallet Relying Party Access Certificate WRPRC Wallet Relying Party Registration Certificate XML eXtensible Markup Language |
1a68fbff3dc809a5ccbe03dc51589d05 | 119 602 | 4 General concepts | |
1a68fbff3dc809a5ccbe03dc51589d05 | 119 602 | 4.1 List of Trusted Entities (LoTE) | List of Trusted Entities are intended to convey trust in a set of entities that are providing services within a given approval scheme. They take the form of a list of entities that have been granted a particular status under the given approval scheme. They represent the outcome of a process of approval, whereby the listed entities are assessed as being trustworthy for the services they provide and granted a particular status corresponding to this level of trustworthiness. How those entities are assessed, and which process is undertaken to grant the entities this particular status enabling them to be listed in a list of trusted entities is outside of the scope of the present document but is integral part of the approval scheme that is described in the list of trusted entities. |
1a68fbff3dc809a5ccbe03dc51589d05 | 119 602 | 4.2 Approval scheme | An approval scheme is any organized process of supervision, monitoring, approval or such practices that are intended to apply oversight with the objective of ensuring adherence to specific criteria in order to maintain confidence in the services under the scope of the scheme. |
1a68fbff3dc809a5ccbe03dc51589d05 | 119 602 | 4.3 Trusted entities | A trusted entity is an entity that is recognized as trustworthy within a given approval scheme for a specific scope or purpose. Trusted entities can be legal or natural entities, or objects. |
1a68fbff3dc809a5ccbe03dc51589d05 | 119 602 | 4.4 Trusted entity services | Entities that are listed in a list of trusted entities are entities that are recognized as being trustworthy within the LoTE scheme for a specific scope. The scope for which this recognition is granted is materialized in the LoTE through "trusted entity service" entries, which are associated to a specific type identifier when applicable, this type identifier then giving the precise scope of the recognition. Trusted entity services can be electronic trust services or other commercial or non-commercial services, but are not limited to it and are a representation of the scope for which the recognition is granted to the listed trusted entities. ETSI ETSI TS 119 602 V1.1.1 (2025-11) 11 |
1a68fbff3dc809a5ccbe03dc51589d05 | 119 602 | 4.5 List of Trusted Entities Scheme Operator | The scheme operator of a List of Trusted Entities (LoTESO) is the body that is responsible for the operation and/or management of the approval scheme under which the corresponding LoTE is published. In particular, the LoTESO is the body responsible for establishing, maintaining and publishing the LoTE. LoTESO can be any kind of bodies, such as governmental bodies, industry or private bodies, etc. |
1a68fbff3dc809a5ccbe03dc51589d05 | 119 602 | 4.6 Syntax bindings | A Syntax binding is an instantiation of the LoTE data model into a given syntax such as XML, JSON, CBOR, etc. The present document provides such XML and JSON bindings in Annex A. There may be several different bindings in the same syntax. EXAMPLE: Different bindings can be defined, for instance, for an implicit scheme information compared to an explicit scheme information. |
1a68fbff3dc809a5ccbe03dc51589d05 | 119 602 | 4.7 LoTE profiles | An LoTE profile is set of scheme-defined constrains on the elements of a LoTE. Such constrains can take the form of additional requirements regarding the values of the elements of a LoTE, or the absence or presence of those elements (e.g. making the presence of an element mandatory or forbidden when it is optional under the present general data model). EXAMPLE: The presence of the ServiceStatus component is optional, however a specific LoTE profile can require that this component is present in all case. NOTE: Additional requirement means, in particular, that when the presence of some components is optional under the requirements laid down in clause 6, specific profiles can condition, forbid, or require their presence. LoTE profile cannot however make the presence of a mandatory component optional or conditioned. |
1a68fbff3dc809a5ccbe03dc51589d05 | 119 602 | 5 Overall structure of lists of trusted entities | The logical model of a list of trusted entities is shown in Figure 1. It has the following logical component parts. There shall be only one occurrence of the first two and last components (i.e. 1., 2. and 6.). The other components may be replicated as illustrated in Figure 1: 1) A list of trusted entities tag (Tag): This tag facilitates the identification of the list of trusted entities during electronic searches. The contents of the tag are specified in clause 6.2. 2) Information on the list of trusted entities and its issuing scheme (Scheme information): The list commences with key information about the list itself and the nature of the scheme which has determined the information found in, and through, the list. This LoTE and scheme information is specified in clause 6.3 and it includes: - A list of trusted entities format version identifier. - A list of trusted entities sequence (or release) number. - A list of trusted entities type information. - A list of trusted entities scheme operator information (e.g. name, address, contact information of the body in charge of establishing, publishing securely and maintaining the list of trusted entities). ETSI ETSI TS 119 602 V1.1.1 (2025-11) 12 - Information about the underlying approval scheme(s) to which the list of trusted entities is associated, including but not limited to: the country in which it applies; information on or reference to the location where information on the approval scheme(s) can be found (scheme model, rules, criteria, applicable community, type, etc.); period of retention of (historical) information. - List of trusted entities policy and/or legal notice, liabilities, responsibilities. - List of trusted entities issue date and time and next planned update. 3) Unambiguous identification information about every trusted entity recognized in the scheme (TE information): It is a sequence of fields holding unambiguous identification information about every listed TE under the scheme. The contents of the TE information fields are specified in clause 6.5 and include: - The TE organization name as used in formal legal registrations. - The TE address and contact information. - Additional information on the TE either included directly or by reference to a location from where such information can be downloaded. 4) For each of the listed TEs, the details of their specific trusted entity services (Service information) whose current status is recorded within the LoTE, either implicitly or explicitly through the presence of a service status identifier, are provided as a sequence of fields holding unambiguous identification of a listed trusted entity service provided by the TE. The contents of the service information field are specified in clause 6.6 and it includes the following for each trusted entity service from a listed TE: - An identifier of the type of service, when applicable. - (Trade) name of this service. - An unambiguous unique identifier of the service. - An identifier of the current status of the service, when applicable. - The current status starting date and time. - Additional information on the service (directly included or included by reference to a location from which information can be downloaded): service definition information provided by the scheme operator, access information with regards to the service, service definition information provided by the TE and service information extensions. 5) (Service approval history) When applicable, for each listed trusted entity service, information on the status history is available in the service approval history information or a sequence of such information. The contents of the history information fields are specified in clause 6.7. 6) (Digital signature) The LoTE is a digitally signed list for authentication purposes. The contents of the digital signature field are specified in clause 6.8. The number of TEs, of services per TE, and of history sections per service is unbounded. The structure of the LoTE is further described in the following clauses by each component part and its fields. ETSI ETSI TS 119 602 V1.1.1 (2025-11) 13 Tag LoTE tag (clause 6.2) Signed LoTE Scheme information LoTE version identifier (clause 6.3.1) LoTE sequence number (clause 6.3.2) LoTE type (clause 6.3.3) Scheme operator name (clause 6.3.4) Scheme operator address (clause 6.3.5) Scheme name (clause 6.3.6) Scheme information URI (clause 6.3.7) Status determination approach (clause 6.3.8) Scheme type/community/rules (clause 6.3.9) Scheme territory (clause 6.3.10) LoTE policy/legal notice (clause 6.3.11) Historical information period (clause 6.3.12) Pointers to other LoTEs (clause 6.3.13) List issue date and time (clause 6.3.14) Next update (clause 6.3.15) Distribution points (clause 6.3.16) Scheme extensions (clause 6.3.17) List of Trusted Entities TE 1 informa- tion TE name (clause 6.5.1) TE trade name (clause 6.5.2) TE address (clause 6.5.3) TE information URI (clause 6.5.4) TE information extensions (clause 6.5.5) List of services Service information (clause 6.6) Service type identifier (clause 6.6.1) Service name (clause 6.6.2) Service digital identity (clause 6.6.3) Service current status (clause 6.6.4) Current status starting date and time (clause 6.6.5) Scheme service definition URI (clause 6.6.6) Service supply points (clause 6.6.7) TE service definition URI (clause 6.6.8) Service information extensions (clause 6.6.9) Service approval history History information (clause 6.7) Service type identifier (clause 6.6.1) Service name (clause 6.6.2) Service digital identity (clause 6.6.3) Service previous status (clause 6.6.4) Previous status starting date and time (clause 6.6.5) Service information extensions (clause 6.6.9) TE 1 Service 1 History 2 Idem for TE 1 Service 1 History 2 (prior to history 1) TE 1 Service 2 Idem for TE 1 Service 2 (as applicable) TE 1 Service 2 History 1 Idem for TE 1 Service 2 History 1 TE 2 Informa- tion Idem for TE 2 (as applicable) Idem for TE 2 Service 1 Idem for TE 2 Service 1 History 1 Digital Signature Digital signature (clause 6.8) Figure 1: Logical model of a list of trusted entities ETSI ETSI TS 119 602 V1.1.1 (2025-11) 14 |
1a68fbff3dc809a5ccbe03dc51589d05 | 119 602 | 6 List of trusted entities components | |
1a68fbff3dc809a5ccbe03dc51589d05 | 119 602 | 6.1 General principles for lists of trusted entities | |
1a68fbff3dc809a5ccbe03dc51589d05 | 119 602 | 6.1.1 Formats of list of trusted entities | The present document provides bindings in XML and JSON for list of trusted entities in Annex A, which may be used for issuing list of trusted entities. Additional bindings may be provided in subsequent versions of the present document. |
1a68fbff3dc809a5ccbe03dc51589d05 | 119 602 | 6.1.2 Use of Uniform Resource Identifiers | In the definitions of LoTE fields given in the present document, many use uniform resource identifiers (URIs) to indicate the meaning of the field concerned. Within these definitions a "common name" may be used to broadly and simply describe the specific values or meanings of the field. These common names are linked to their declaration in Annex H, which formally states all specific URIs used in the present document, with their meanings. Some fields allow to use different URIs, which have the same purpose, to be registered and described by the scheme operator or another entity and recognized by the intended user community. Such URIs may be registered with ETSI. Information on URI registration can be found in Annex H. Where fields are defined as being of or using the type URI, implementers shall use general syntax as specified by IETF RFC 3986 [9]. |
1a68fbff3dc809a5ccbe03dc51589d05 | 119 602 | 6.1.3 Date-time indication | All fields carrying date-time values shall comply with the following rules: 1) the date-time values shall be a character string formatted according to ISO 8601 [8]; and 2) the date-time value shall be expressed as Coordinated Universal Time (UTC): its value shall contain year with four digits, month, day, hour, minute, second (without decimal fraction) and the UTC designator "Z". The time scale shall be based on the second. |
1a68fbff3dc809a5ccbe03dc51589d05 | 119 602 | 6.1.4 Language support | Lists of trusted entities shall be issued supporting at least the UK English language, using the 'en' language code as specified in IETF RFC 5646 [11] and Annex G. Lists of trusted entities may also be issued supporting multiple (national) languages. For all the fields where support of multiple language is applicable, the field format specifications refer to the use of multilingual character string or pointer to which the following general rules shall apply: 1) A multilingual character string shall be a character string as defined in ISO/IEC 10646 [5] encoded in UTF-8. Each multilingual character string shall consist of two parts: a tag, conformant to IETF RFC 5646 [11] and in lower case, that identifies the language in which the string is expressed, and the text in that language. The same content may be represented in multiple languages by a sequence of multilingual character strings. 2) A multilingual pointer shall be a URI that identifies a resource expressed in a particular language. Each multilingual pointer shall consist of two parts: a tag, conformant to IETF RFC 5646 [11], that identifies the language in which the content pointed-to by the URI is expressed, and the URI expressed as a character string with the syntax specified by IETF RFC 3986 [9], identifying a resource expressed in the given language. The same content may be represented in multiple languages by a sequence of multilingual pointers. ETSI ETSI TS 119 602 V1.1.1 (2025-11) 15 Whenever the native terms cannot be represented using the Latin alphabet, as defined in ISO/IEC 10646 [5], one issue of the term in the native language plus one issue with a transliteration to the Latin alphabet shall be used. Implementers should also comply with the UNICODE Standard [i.5]. Further detailed requirements regarding multilingual implementation are specified in normative Annex G. |
1a68fbff3dc809a5ccbe03dc51589d05 | 119 602 | 6.1.5 Value of Country Code fields | All fields carrying Country Codes values, denoted by "CC", shall be in capital letters and in accordance with either: a) ISO 3166-1 [2] Alpha 2 codes with the following exceptions: 1) the Country Code for United Kingdom shall be "UK"; 2) the Country Code for Greece shall be "EL"; 3) when the scope of the field is the European Union and/or the European Commission the code "EU" shall be used; or b) commonly used extensions with regional scope (e.g. AP for Asia Pacific, ASIA); or c) another identifier recognized for identifying multi-state grouping and that does not conflict with a), or b). |
1a68fbff3dc809a5ccbe03dc51589d05 | 119 602 | 6.2 List of trusted entities tag | Description: The LoTE is tagged to facilitate its identification during electronic searches. Format: The LoTETag component shall be a character string which indicates that the data structure is a LoTE. This shall be the character representation of the LoTE Tag URI. Semantics: This value of this string shall be a unique value enabling a web-searching tool to establish during a WWW-wide search for LoTEs that a resource it has located is indeed a LoTE. Only the characters required to fully represent the URI shall be present. |
1a68fbff3dc809a5ccbe03dc51589d05 | 119 602 | 6.3 List and scheme information | |
1a68fbff3dc809a5ccbe03dc51589d05 | 119 602 | 6.3.0 General | Description: This ListAndSchemeInformation component provides information on the list of trusted entities and its issuing scheme. Information about the scheme within which the LoTE is issued may be provided either implicitly or explicitly. NOTE: Scheme information can be implicitly known when, for instance, it is provided through another means, or the context of the transactions itself within which the LoTE is consumed assumes a specific scheme known by all parties, the information on which can be retrieved by all parties out of band. In case the scheme information is implicit, the LoTE need not contain this component. In case the scheme information is explicit the LoTE shall contain this component. ETSI ETSI TS 119 602 V1.1.1 (2025-11) 16 In case the LoTE does not contain this component, information about the list itself shall be provided within the list directly through the presence of the LoTEVersionIdentifier, the LoTESequenceNumber, the SchemeOperatorName, the ListIssueDateTime, and the NextUpdate elements. In case the LoTE does not contain this component, information about the history retention of the listed trusted entities and services may be provided in the list directly through the presence of the HistoricalInformationPeriod element. Format: The ListAndSchemeInformation component shall contain sub-components providing information about the LoTE: • The LoTEVersionIdentifier element. (see clause 6.3.1). • The LoTESequenceNumber element (see clause 6.3.2). • The ListIssueDateTime element (see clause 6.3.14). • The NextUpdate element (see clause 6.3.15). The ListAndSchemeInformation component may optionally contain the below sub-components providing additional information about the LoTE: • The LoTEType element (see clause 6.3.3). • The DistributionPoints element (see clause 6.3.16). The ListAndSchemeInformation component shall contain the below sub-components providing information about the LoTE scheme: • The SchemeOperatorName element (see clause 6.3.4). The ListAndSchemeInformation component may optionally contain the below sub-components providing additional information about the LoTE scheme: • The SchemeOperatorAddress element (see clause 6.3.5). • The SchemeName element (see clause 6.3.6). • The SchemeInformationURI element (see clause 6.3.7). • The StatusDeterminationApproach element (see clause 6.3.8). • The SchemeTypeCommunityRules element (see clause 6.3.9). • The SchemeTerritory element (see clause 6.3.10). • The PolicyOrLegalNotice element (see clause 6.3.11). • The HistoricalInformationPeriod element (see clause 6.3.12). • The PointerToOtherLoTE component (see clause 6.3.13). • The SchemeExtensions element (see clause 6.3.17). Semantics: In case the scheme information is implicit, this component shall contain at least the LoTEVersionIdentifier, the LoTESequenceNumber, the SchemeOperatorName, the ListIssueDateTime, and the NextUpdate elements. ETSI ETSI TS 119 602 V1.1.1 (2025-11) 17 In case the scheme information is explicit this component shall contain, in addition, LoTEType, the SchemeInformationURI, the StatusDeterminationApproach, the SchemeTypeCommunityRules, the SchemeTerritory, and the PolicyOrLegalNotice elements. Table 1 summarizes the above requirements, where "M" means that an element shall be present, "O" means that an element may be present, and "/" means that an element shall not be present. Table 1: Implicit and explicit scheme information Element Presence Implicit scheme information Explicit Scheme information LoTEVersionIdentifier M M LoTESequenceNumber M M LoTEType O M SchemeOperatorName M M SchemeOperatorAddress O M SchemeName / M SchemeInformationURI / M StatusDeterminationApproach / M SchemeTypeCommunityRules / M SchemeTerritory O M PolicyOrLegalNotice / M HistoricalInformationPeriod O O PointerToOtherLoTE O O ListIssueDateTime M M NextUpdate M M DistributionPoints O O SchemeExtensions O O |
1a68fbff3dc809a5ccbe03dc51589d05 | 119 602 | 6.3.1 LoTE version identifier | Description: The LoTEVersionIdentifier component specifies the version of the LoTE format for a specific syntax binding. Format: The LoTEVersionIdentifier component shall contain an integer. Semantics: The value of this integer shall be incremented only when the rules for parsing the LoTE in a specific syntax change, e.g. through addition/removal of a field or a change to the values or meaning of an existing field. Revisions to the specification of a specific syntax binding which do not change the parsing rules of the LoTE may be made without revision to this field. NOTE: The present document does not impose a specific value for the content of this component. It is up to each syntax binding and profile specifications to handle the changes to this component. |
1a68fbff3dc809a5ccbe03dc51589d05 | 119 602 | 6.3.2 LoTE sequence number | Description: The LoTESequenceNumber component specifies the sequence number of the LoTE. ETSI ETSI TS 119 602 V1.1.1 (2025-11) 18 Format: The LoTESequenceNumber component shall contain an integer. Semantics: At the first release of the LoTE, the value of the sequence number shall be 1. The value shall be incremented at each subsequent release of the LoTE and shall not, under any circumstance, be re-cycled to "1" or to any value lower than the one of the LoTE currently in force. |
1a68fbff3dc809a5ccbe03dc51589d05 | 119 602 | 6.3.3 LoTE type | Description: The LoTEType component specifies the type of the list of trusted entities. It permits a parser to determine the form of any following field to expect according to a specific syntax binding and profile. Format: The LoTEType component shall contain an indicator expressed as a URI. Semantics: Each LoTE profile owner shall ensure that the LoTE type URI is unique for the profile it manages. A list of registered LoTE type is provided in Annex H. |
1a68fbff3dc809a5ccbe03dc51589d05 | 119 602 | 6.3.4 Scheme operator name | Description: The SchemeOperatorName component specifies the name of the entity in charge of establishing, publishing, signing and maintaining the list of trusted entities. Format: The SchemeOperatorName component shall contain a sequence of multilingual character strings (see clause 6.1.4). Semantics: The name of the scheme operator shall be the formal name under which the associated legal entity or mandated entity (e.g. for governmental administrative agencies) associated with the legal entity in charge of establishing, publishing and maintaining the list of trusted entities operates. It shall be the name used in formal legal registration or authorization and to which any formal communication should be addressed. |
1a68fbff3dc809a5ccbe03dc51589d05 | 119 602 | 6.3.5 Scheme operator address | |
1a68fbff3dc809a5ccbe03dc51589d05 | 119 602 | 6.3.5.0 General | Description: The SchemeOperatorAddress component specifies the address of the legal entity or mandated organization identified in the 'Scheme operator name' component (clause 6.3.4) for both postal and electronic communications. Format: This component shall contain: 1) the PostalAddresses element specified in clause 6.3.5.1; and 2) the ElectronicAddress element specified in clause 6.3.5.2. ETSI ETSI TS 119 602 V1.1.1 (2025-11) 19 |
1a68fbff3dc809a5ccbe03dc51589d05 | 119 602 | 6.3.5.1 Scheme operator postal address | Description: The PostalAddresses component specifies the postal address of the legal entity identified in clause 6.3.4, with the provision for the inclusion of the address in multiple languages. Format: This component shall contain sequence(s) of multilingual PostalAddress components (see clause 6.1.4). The PostalAddress component shall contain the following elements: • The StreetAddress element, which shall be a string. • The Country element, which shall be a two-character code in accordance with clause 6.1.5 (a). The PostalAddress component may optionally contain the following elements: • The Locality element, which shall be a string. • The StateOrProvince element, which shall be a string. • The PostalCode element, which shall be a string. Semantics: This shall be a postal address at which the scheme operator provides a help line service which is operated through conventional (physical) mail and which is processed as would be expected by normal business services. Users (subscribers, relying parties) should use this address as the contact point for enquiries, complaints, etc. to the scheme operator. |
1a68fbff3dc809a5ccbe03dc51589d05 | 119 602 | 6.3.5.2 Scheme operator electronic address | Description: The ElectronicAddress component specifies the email address, the web-site URI and optional telephone number of the legal entity identified in clause 6.3.4 for electronic communications. Format: The ElectronicAddress component shall contain a sequence of multilingual character strings (see clause 6.1.4). Semantics: This component shall be used to provide: • mandatorily, an e-mail address as a URI, in the form specified by IETF RFC 3986 [9], with the URI scheme defined in IETF RFC 2368 [13]; • mandatorily, a web-site as a URI, in the form specified by IETF RFC 3986 [9]; • optionally, a telephone number as a URI, in the form specified by IETF RFC 3986 [9], with the "tel" URI scheme defined in IETF RFC 3966 [14]. The e-mail address, and the telephone number when present, shall be an address, and respectively a phone number when present, at which the scheme operator provides a help line service which addresses LoTE-related matters and which are processed as would be expected by normal business services. As regards a web-site URI, this shall lead to a capability whereby the user may communicate with a help line service which addresses LoTE-related matters and which is processed as would be expected by normal business services. ETSI ETSI TS 119 602 V1.1.1 (2025-11) 20 |
1a68fbff3dc809a5ccbe03dc51589d05 | 119 602 | 6.3.6 Scheme name | Description: The SchemeName component specifies the name under which the scheme operates. Format: This component shall contain a sequence of multilingual character strings (see clause 6.1.4), defined as follows: • The English version shall be a character string structured as follows: - CC:EN_name_value; where: - 'CC' is the code used in the 'Scheme territory' element (clause 6.3.10); - ':' is used as the separator; - 'EN_name_value' is the name of the scheme. • Any national language version shall be a character string structured as follows: - CC:name_value; where: - 'CC' is the code used in the 'Scheme territory' element (clause 6.3.10); - ':' is used as the separator; - 'name_value' is the national language official translation of the above EN_name_value. Semantics: The name of the scheme shall be the name which is used in formal references to the scheme in question, shall be unique and shall not be used by any other scheme operated by the same entity. |
1a68fbff3dc809a5ccbe03dc51589d05 | 119 602 | 6.3.7 Scheme information URI | Description: The SchemeInformationURI component specifies the URI(s) where users (relying parties) can obtain scheme- specific information. Format: This component shall be a sequence of multilingual pointers (see clause 6.1.4). Semantics: This component may contain be zero or more URIs leading to archived versions of the list. The referenced multilingual pointer URI(s), not leading to archived versions of the list, shall provide a path to information describing appropriate information about the scheme, including: • scope and context of the list of trusted entities; • general description and detailed information about underlying (approval) scheme; • information about the process and procedures followed: - by the LoTESO, or the body from which it depends or by which it is mandated, being in charge to approve the trusted entities for being listed in the list of trusted entities; and - by the trusted entities for being approved for being listed in the list of trusted entities; ETSI ETSI TS 119 602 V1.1.1 (2025-11) 21 • information about the criteria against which the trusted entities are approved; • information about the criteria and rules used to select assessors and defining how trusted entities are assessed by them; • where separate bodies provide separate aspects of supervision, accreditation and scheme operation, the separate responsibilities and any liabilities of each body; and • other contact and general information that may apply to the scheme operation. |
1a68fbff3dc809a5ccbe03dc51589d05 | 119 602 | 6.3.8 Status determination approach | Description: The StatusDeterminationApproach component specifies the identifier of the status determination approach. Format: The StatusDeterminationApproach component shall contain an indicator expressed as a URI. |
1a68fbff3dc809a5ccbe03dc51589d05 | 119 602 | 6.3.9 Scheme type/community/rules | Description: The SchemeTypeCommunityRules component specifies the URI(s) where users (relying parties) can obtain scheme type/community/rules information against which the trusted entities and the trusted entity services included in the list are approved and assessed, and from which the type of scheme or community may be determined. Format: The SchemeTypeCommunityRules component shall contain a sequence of multilingual pointers (see clause 6.1.4). Semantics: The referenced URI(s) shall identify: • the specific policy/rules against which services included in the list are approved and assessed, and from which the type of scheme or community may be determined; and • the description about how to use and interpret the content of the list of trusted entities. Where more than one URI is provided, each shall be a complete subset of the policy defined by its predecessor (e.g. a supra-national policy might be overarching; separate nations part of this supra-national entity may have their own implementations as part of this supra-national high-level policy). When LoTESOs participate to a wider scheme for issuing lists of trusted entities which share common rules and which point towards a descriptive text that applies to the LoTE of each LoTESO, a URI common to all LoTESO shall be used: • denoting participation of the list of trusted entities (identified via the "LoTE type" (see clause 6.3.3) and "Scheme name" (clause 6.3.6)) in a wider scheme of lists of trusted entities (i.e. a LoTE listing pointers to all members publishing and maintaining a list of trusted entities); • identifying a resource from where users can obtain policy/rules against which services included in the lists are assessed; • identifying a resource from where users can obtain description about how to use and interpret the content of the lists of trusted entities. These usage rules shall be common to all lists of trusted entities being part of the wider scheme of schemes whatever the type of listed services. ETSI ETSI TS 119 602 V1.1.1 (2025-11) 22 |
1a68fbff3dc809a5ccbe03dc51589d05 | 119 602 | 6.3.10 Scheme territory | Description: The SchemeTerritory component specifies the country or territory in which the scheme is established and applies. Format: The SchemeTerritory component shall contain a character string in accordance with clause 6.1.5. |
1a68fbff3dc809a5ccbe03dc51589d05 | 119 602 | 6.3.11 LoTE policy/legal notice | Description: The PolicyOrLegalNotice component specifies the scheme's policy or provides a notice concerning the legal status of the scheme or legal requirements met by the scheme for the jurisdiction in which the scheme is established and/or any constraints and conditions under which the LoTE is maintained and published. Format: The PolicyOrLegalNotice component shall contain either: • a sequence of LoTEPolicy elements which shall be multilingual pointers (see clause 6.1.4) for specific use as a pointer to the policy or notice; or • a sequence of LoTELegalNotice elements which shall be multilingual character strings (see clause 6.1.4) providing the actual text of any such policy or notice, in as many languages as necessary. Semantics: Any referenced text shall provide information describing the policy under which the Scheme Operator operates or any relevant legal notices with which users of the LoTE should be aware. |
1a68fbff3dc809a5ccbe03dc51589d05 | 119 602 | 6.3.12 Historical information period | Description: The HistoricalInformationPeriod component specifies the duration over which historical information in the LoTE is maintained once it has been included. Format: This component shall contain an integer. Semantics: When the value of this integer is set to '65535', this signifies that historical information provided in the list of trusted entities shall never be removed. When this component is absent, this signifies that historical information provided in the list of trusted entities shall not be kept. See also the requirements bearing on the presence of the ServiceStatus component (clause 6.6.4). |
1a68fbff3dc809a5ccbe03dc51589d05 | 119 602 | 6.3.13 Pointers to other LoTEs | Description: The PointersToOtherLoTE component references any relevant list of trusted entities or any relevant list of lists of trusted entities. ETSI ETSI TS 119 602 V1.1.1 (2025-11) 23 Format: The PointersToOtherLoTE component shall contain a sequence of one or more OtherLoTEPointer elements, each OtherLoTEPointer element giving: a) a LoTELocation element containing the URI of the machine processable format of another LoTE; b) one or more ServiceDigitalIdentity element, all representing the issuer of the LoTE pointed to, formatted as specified in clause 6.6.3; and c) additional information as a set of LoTE Qualifiers: LoTE Type, as defined in clause 6.3.3; Scheme operator name, as defined in clause 6.3.4; optionally the Scheme type/community/rules, as defined in clause 6.3.9; Scheme territory, as defined in clause 6.3.10; and Mime type. Semantics: More than one digital identity may be used to help the management of the pointed-to list signing process (e.g. in case of expiration/substitution of pointed-to list signing keys or more than a single signing key is allowed to sign this list). One of such digital identities shall allow successful authentication of the pointed-to list before its use. |
1a68fbff3dc809a5ccbe03dc51589d05 | 119 602 | 6.3.14 List issue date and time | Description: The ListIssueDateTime component specifies the date and time on which the list of trusted entities was issued. Format: The ListIssueDateTime component shall contain a date-time value (see clause 6.1.3). Semantics: The ListIssueDateTime value shall be the Coordinated Universal Time (UTC) at which the LoTE was issued. |
1a68fbff3dc809a5ccbe03dc51589d05 | 119 602 | 6.3.15 Next update | Description: The NextUpdate component specifies the date and time by which, at the latest, an update of the LoTE will be made available by the scheme operator or be null to indicate a closed LoTE. Format: The NextUpdate component shall contain a date-time value (see clause 6.1.3). Semantics: The NextUpdate value shall be the Coordinated Universal Time (UTC) by which, at the latest, an update of the LoTE shall be issued. The scheme operator shall issue and publish an update of the LoTE before that Next Update date and time whenever the underlying approval scheme will require so, in particular when changes occur to trusted entity or service related information (e.g. its status). In the event of no interim status changes to any trusted entity or service covered by the scheme, the LoTE shall be re-issued by the time of expiration of the last LoTE issued. LoTE with a Next update occurring in the past shall be discarded as expired as a measure to reduce the risk of a substitution by an attacker with an old LoTE. Applications shall consider, in the event they implement some caching mechanism, that other LoTEs could be issued and published before 'Next update' date and time. LoTE profiles should specify the maximum allowed difference between the 'Next update' date and time and the 'List issue date and time'. ETSI ETSI TS 119 602 V1.1.1 (2025-11) 24 If a scheme ceases operations or halts publication of its LoTE, a final version shall be published with all services' status shown as "expired" (see Service current status) and this field set null. |
1a68fbff3dc809a5ccbe03dc51589d05 | 119 602 | 6.3.16 Distribution points | Description: When used, the DistributionPoints component specifies locations where the current LoTE is published and where updates to the current LoTE can be found. Format: The DistributionPoints component shall contain a non-empty sequence of URIs. Semantics: Dereferencing the given URI will always deliver the latest update of this LoTE. If multiple distribution points are specified, they all shall provide identical copies of the current LoTE or its updated version. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.