hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
b7c242d7dc897cefd2ac133fc9d40a42 | 105 175-1-1 | 6.2 Physical layer requirements | The physical layer shall be implemented following ETSI TS 105 175-1-2 [5]. The data packets to be used with ETSI TS 105 175-1-2 [5] shall be regular Ethernet frames. The link budget characteristics of the 1 Gbit/s and 100 Mbit/s are described in figures 6 and 7. Figure 6: 1 Gbit/s link budget ETSI ETSI TS 105 175-1-1 V1.1.1 (2015-10) 23 Figure 7: 100 Mbit/S link budget |
b7c242d7dc897cefd2ac133fc9d40a42 | 105 175-1-1 | 6.3 Ethernet layer performance | The resulting performance of the implemented Ethernet link should follow: • Bitrate: shall be exactly 1 Gbit/s or 100 Mbit/s, MAC Layer compatible with other 1 Gbit/s and 100 Mbit/s full duplex standards in IEEE™ 802.3 and [9], clauses 24 and 34, following ETSI TS 105 175-1-2 [5]. • Adaptive Bit Rate is specified as optional in ETSI TS 105 175-1-2 [5] and it may be supported to guarantee connectivity in extreme conditions. • VLAN: VLAN may be required by applications. Transport layers manage VLAN support, but correct support is required in physical layer considering MTU. Please refer to IEEE™ 802.1Q [i.4]. • Jitter / Latency: is driven by application. Please refer to ETSI TS 105 175-1 [1]. ETSI TS 105 175-1-2 [5] requires more restricting values for jitter and latency than ETSI TS 105 175-1 [1]. • Frame Error Rate, Bit Error Rate: even when ETSI TS 105 175-1 [1] requires BER less than 10-12, ETSI TS 105 175-1-2 [5] defines BER limits less than 10-10. The required BER and FER shall follow ETSI TS 105 175-1-2 [5] requirements. This update in the requirements is needed to make the system compatible with 1000-BaseT installations. • Validation test required in a 1 Gbit/s and 100 Mbit/s connection according to IETF RFC 2544 [8]. • Validation test of Ethernet services activation might be used following the Recommendation ITU-T Y.1564 [10] test methodology. |
b7c242d7dc897cefd2ac133fc9d40a42 | 105 175-1-1 | 6.4 Backwards compatibility | New gigabit over POF implementation shall be backwards compatible with already deployed 802.3 100BASE-FX [9] devices. The 100BASE-FX [9] PCS and PMA are specified in IEEE™ 802.3 [9], clause 24. |
b7c242d7dc897cefd2ac133fc9d40a42 | 105 175-1-1 | 6.5 Environmental requirements | • Temperature: is driven by application. Please refer to ETSI TS 105 175-1 [1]. • EMI: please refer to ETSI TS 105 175-1 [1]. • Safety: please refer to ETSI TS 105 175-1 [1]. ETSI ETSI TS 105 175-1-1 V1.1.1 (2015-10) 24 |
b7c242d7dc897cefd2ac133fc9d40a42 | 105 175-1-1 | 6.6 Topology requirements | Several topologies shall be supported: • Star: default topology for green field. • Daisy/Chain: brown field houses. Reuse mains topology. • Tree: complementary to Daisy/Chain to support branches. For the implementation of those topologies bridging and multicast traffic handling shall follow: • IEEE™ 802.1p [i.5]: Multicast filtering. • IEEE™ 802.1D [i.6]: MAC Bridges. For the physical installation of the fibre following requirements shall be followed: • Bending: please refer to ETSI TS 105 175-1 [1] for bending requirements. • Lengths: please refer to ETSI TS 105 175-1 [1] for fibre length requirements. • Link budget: please refer to CENELEC EN 50173-4 [7] and CENELEC EN 50173-1 [6]. |
b7c242d7dc897cefd2ac133fc9d40a42 | 105 175-1-1 | 6.7 Energy Efficient Ethernet requirements | Low power mode is described as optional in ETSI TS 105 175-1-2 [5]. Consequently, Energy Efficient Ethernet is optional in the present document. |
b7c242d7dc897cefd2ac133fc9d40a42 | 105 175-1-1 | 6.8 Network Management requirements | Following network management standards should be supported under the request of B2B demand: • SNMP v3: please refer to RFC from 3410 to 3418 [i.10] for more details. • TR-069 Amendment 4 [i.9] and TR-143 [i.11]. CPE-1 profile. |
b7c242d7dc897cefd2ac133fc9d40a42 | 105 175-1-1 | 6.9 Diagnostic and monitoring requirements | The system shall provide diagnostic and monitoring requirements. The system shall provide at least the following indicators at both ends of the link for monitoring and diagnostic: • Received power • Link margin • Temperature The present document does not specify how these indicators shall be implemented. |
b7c242d7dc897cefd2ac133fc9d40a42 | 105 175-1-1 | 6.10 Higher Level System requirements | Please refer to ETSI TS 105 175-1 [1]. ETSI ETSI TS 105 175-1-1 V1.1.1 (2015-10) 25 History Document history V1.1.1 January 2010 Publication as TS 105 175-1 V2.0.0 October 2011 Publication as TS 105 175-1 V1.1.1 October 2015 Publication |
59705d30c263f43062be240082eadcb7 | 105 175-1 | 1 Scope and Purpose | |
59705d30c263f43062be240082eadcb7 | 105 175-1 | 1.1 Scope | The present document specifies the POF cabling system 100 Mbit/s and 1 Gbit/s for interoperability among different suppliers. The system comprises the active optical elements, the cables, connectors and wall plugs. A future step could be to achieve integration of POF interfaces into end user equipment. |
59705d30c263f43062be240082eadcb7 | 105 175-1 | 1.2 Requirements Notation | If the present document is implemented, the key words "MUST" and "SHALL" as well as "REQUIRED" are to be interpreted as indicating a mandatory aspect of the present document. The keywords indicating a certain level of significance of a particular requirement that are used throughout the present document are summarized below. MUST: This word or the adjective "REQUIRED" means that the item is an absolute requirement of the present document. MUST NOT: This phrase means that the item is an absolute prohibition of the present document. SHOULD: This word or the adjective "RECOMMENDED" means that there may exist valid reasons in particular circumstances to ignore this item, but the full implications should be understood and the case carefully weighed before choosing a different course. SHOULD NOT: This phrase means that there may exist valid reasons in particular circumstances when the listed behaviour is acceptable or even useful, but the full implications should be understood and the case carefully weighed before implementing any behaviour described with this label. MAY: This word or the adjective "OPTIONAL" means that this item is truly optional. One vendor may choose to include the item because a particular marketplace requires it or because it enhances the product, for example; another vendor may omit the same item. |
59705d30c263f43062be240082eadcb7 | 105 175-1 | 2 References | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the reference document (including any amendments) applies. Referenced documents which are not found to be publicly available in the expected location might be found at http://docbox.etsi.org/Reference. NOTE: While any hyperlinks included in this clause were valid at the time of publication ETSI cannot guarantee their long term validity. |
59705d30c263f43062be240082eadcb7 | 105 175-1 | 2.1 Normative references | The following referenced documents are necessary for the application of the present document. [1] Directive 2002/95/EC of the European Parliament and of the Council of 27 January 2003 on the restriction of the use of certain hazardous substances in electrical and electronic equipment. [2] IEEE 802.3: "Telecommunications and Information Exchange Between Systems - Local and Metropolitan Area Networks - Specific Requirements Part 3: Carrier Sense Multiple Access with Collision Detection (CSMA/CD) Access Method and Physical Layer Specifications Amendment: Physical Layer Specifications and Management Parameters for 10Gb/s Passive Optical Networks". [3] IEC 60825 series: "Safety of laser products". ETSI ETSI TS 105 175-1 V2.0.0 (2011-10) 7 [4] DSL Forum Technical Report TR-126 (December 2006): "Triple-Play Services, Quality of Experience (QoE) Requirements". [5] DSL Forum Technical Report TR-069: "CPE WAN Management Protocol". [6] IEC 60793-1-47: "Optical fibres - Part 1-47: Measurement methods and test procedures - Macrobending loss". [7] IEC 60793-2-40: "Optical fibres - Part 2-40: Product specifications - Sectional specification for category A4 multimode fibres". [8] IEC 60794-2-40: "Optical fibre cables - Part 2-40: Indoor optical fibre cables - Family specification for A4 fibre cables". [9] IEC 60794-2-41 (Edition 1.0): "Optical fibre cables - Part 2-41: Indoor cables - Product specification for simplex and duplex buffered A4 fibres". [10] IEC 61754-21: "Fibre optic connector interfaces - Part 21: Type SMI connector family for plastic optical fibre". [11] IEC 61754-22: "Fibre optic connector interfaces - Part 22: Type F-SMA connector family". [12] IEC 61754-24: "Fibre optic interconnecting devices and passive components - Fibre optic connector interfaces - Part 24: Type SC-RJ connector family". [13] IEC 60332: "Tests on electric and optical fibre cables under fire conditions". [14] European Commission (18 November 2008) Version 3: "Code of Conduct on Energy Consumption of Broad Band Equipment". [15] IEC 60884-1: "Plugs and socket-outlets for household and similar purposes - Part 1: General requirements". [16] ISO/IEC 8802-3: "Information technology - Telecommunications and information exchange between systems - Local and metropolitan area networks - Specific requirements - Part 3: Carrier sense multiple access with collision detection (CSMA/CD) access method and physical layer specifications". [17] CENELEC EN 60950-1: "Information technology equipment - Safety - Part 1: General requirements". [18] ITU-T Recommendation K.21: "Resistibility of telecommunication equipment installed in customer premises to overvoltages and overcurrents". [19] IEC 60068-2-27: "Environmental testing - Part 2-27: Tests - Test Ea and guidance: Shock". [20] ETSI EN 300 019-2-3: "Environmental Engineering (EE); Environmental conditions and environmental tests for telecommunications equipment; Part 2-3: Specification of environmental tests; Stationary use at weatherprotected locations". [21] IEC 60068-2-6: "Environmental testing - Part 2-6: Tests - Test Fc: Vibration (sinusoidal)". [22] IEC 60068-2-64: "Environmental testing - Part 2-64: Tests - Test Fh: Vibration, broadband random and guidance". [23] CENELEC EN 55022: "Information technology equipment - Radio disturbance characteristics - Limits and methods of measurement". [24] CENELEC EN 55024: "Information technology equipment - Immunity characteristics - Limits and methods of measurement". [25] IEC 61034-1/2: "Measurement of smoke density of cables burning under defined conditions (all parts)". [26] IEC 60754-1/2: "Test on gases evolved during combustion of electric cables (all parts)". ETSI ETSI TS 105 175-1 V2.0.0 (2011-10) 8 [27] IEC 61754-4: "Fibre optic connector interfaces - Part 4-1: Type SC connector family - Simplified receptacle SC-PC connector interfaces". [28] IEC 61754-20: "Fibre optic connector interfaces - Part 20: Type LC connector family". [29] IS 11801: "Information techonlogy - Generic cabling for customers premises". |
59705d30c263f43062be240082eadcb7 | 105 175-1 | 2.2 Informative references | The following referenced documents are not necessary for the application of the present document but they assist the user with regard to a particular subject area. [i.1] IEEE 802.3u: "Local and Metropolitan Area Networks-Supplement - Media Access Control (MAC) Parameters, Physical Layer, Medium Attachment Units and Repeater for 100Mb/s Operation, Type 100BASE-T (Clauses 21-30)". [i.2] IEEE 802.3z: "Media Access Control Parameters, Physical Layers, Repeater and Management Parameters for 1,000 Mb/s Operation, Supplement to Information Technology - Local and Metropolitan Area Networks - Part 3: Carrier Sense Multiple Access with Collision Detection (CSMA/CD) Access Method and Physical Layer Specifications". [i.3] IEEE 802.3x: "IEEE Standards for Local and Metropolitan Area Networks: Specification for 802.3 Full Duplex Operation". [i.4] IEEE 802.1Q: "IEEE Standard for Local and Metropolitan Area Networks - Virtual Bridged Local Area Networks". [i.5] IEEE 802.1p: "IEEE Standard for Local and Metropolitan Area Networks - Supplement to Media Access Control (MAC) Bridges: Traffic Class Expediting and Dynamic Multicast Filtering". [i.6] IEEE 802.1D: "IEEE Standard for Local and metropolitan area networks: Media Access Control (MAC) Bridges". |
59705d30c263f43062be240082eadcb7 | 105 175-1 | 3 Definitions and abbreviations | |
59705d30c263f43062be240082eadcb7 | 105 175-1 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply: triple play services: scenario in which voice, video and data are all provided in a single access subscription |
59705d30c263f43062be240082eadcb7 | 105 175-1 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: ACS Auto Configuration Server CPE Customer Premises Equipment EMI ElectroMagnetic Interference FTTH Fiber To The Home GOF Glass Optical Fibre GPON Gigabit Passive Optical Network HG Home Gateway IPTV Internet Protocol Television MTBF Mean Time Between Failures PMMA Poly-Methyl-Metha-Acrilate POF Polymer Optical Fibres PVC PolyVinyl Chloride QoE Quality of Experience QoS Quality of Service ETSI ETSI TS 105 175-1 V2.0.0 (2011-10) 9 RoHS Restriction of the Use of Certain Hazardous Substances SC/RJ Small Form Factor Connector/Registered Jack SMI Small Multimedia Interface STB Set Top Box UTP5 Unshielded Twisted Pair (Category 5) VAC Volts Alternating Current VDSL2 Very high bit-rate Digital Subscriber Line VLAN Virtual Local Area Network |
59705d30c263f43062be240082eadcb7 | 105 175-1 | 4 Requirements for 100 Mbit/s System (Fast Ethernet) | |
59705d30c263f43062be240082eadcb7 | 105 175-1 | 4.1 Performances | Today on the market several suppliers offer IEC 60793-2-40 [7] PMMA POF media converter solutions at 100 Mbit/s. With such performance PMMA fibre may be used in the home to interconnect all devices usually communicating through Fast Ethernet interfaces for example the link between the home gateway and the STB. Below the requirement for 100 Mbit/s Systems. R1 The max Physical Layer Data Rate MUST be 125 Mbit/s, compliant with IEEE 802.3u [i.1]. R2 The system SHOULD be able to transmit over a distance up to 100 m. Figure 3 shows the maximum reachable distance vs. POF bends number. 0 20 40 60 80 100 120 0 2 4 6 8 10 Bends number distance (m) Figure 3: Maximum reachable distance vs. POF bends number R3 Macrobend radius shall be ≥ 25 mm. R4 Macrobending loss shall be measured according to IEC 60793-1-47 [6], method B. R5 The Bit Error Rate SHOULD be < 10-12 R6 The system MUST work in Full Duplex. Today media converters are based on duplex services which are achieved by using duplex POF. However the availability of a duplex service over simplex POF systems needs to be investigated as ultimately they may provide practical advantages to end users. R7 The System MUST present a Latency < 5 ms in either direction. Services such as Gaming & VoIP require low latency. Note that adaptive data rates will require traffic management and will increase latency. For industrial automation Latency < 1ms SHOULD be required. R8 The system MUST operate in a temperature range of 0 ºC to +60 ºC and humidity in the range of 5 % to 95 %. R9 The system MUST operate in Class 1 for Eye Safety [3]. ETSI ETSI TS 105 175-1 V2.0.0 (2011-10) 10 |
59705d30c263f43062be240082eadcb7 | 105 175-1 | 4.2 Higher Level System Features | R10 The system SHOULD be conform to QoS specifications per channel as outlined in DSL Forum Technical Report TR-126 [4]. R11 The system MUST interoperate among multiple vendors systems to stimulate competition and ensure security features are common throughout vendors and SHOULD be interoperable at the specified data rate. R12 Bridges SHOULD be able to support both IPv4 & IPv6. R13 Devices SHOULD be 'Plug & Play', such that the user is able to install them very easily. R14 It SHOULD be possible to add/remove additional nodes without service interruption to existing nodes. R15 Devices SHOULD be transparent to either ACS or via a TR-069 [5] proxy on the HG (or other equipment) thus supporting the remote management of CPE such as switches and STBs that are linked by POF. |
59705d30c263f43062be240082eadcb7 | 105 175-1 | 5 Requirements for 1 Gbit/s System | |
59705d30c263f43062be240082eadcb7 | 105 175-1 | 5.1 Performances | R16 The max Physical Layer Data Rate MUST be 1,25 Gbit/s, compliant with IEEE 802.3z [i.2]. R17 The link MAY have an adaptive data rate depending upon link length and number of bends. An indicative performance is shown in table 1. Table 1 Link Length (m) Number of 90o Bends of 12 mm Radius Physical Layer Data Rate (Gbit/s) 50 0 1,25 50 10 0,85 75 0 0,87 75 10 0,45 100 0 0,5 100 10 0,08 R18 The Bit Error Rate MUST be <10-12, in agreement with IEEE 802.3z [i.2] standard at physical layer 1 (1000Base-SX interface). For this system, it will also be compliant with ITU-T IPTV Focus Group Proceedings 2008 and DSL Forum Technical Report TR-126 [4] where the Packet Error Rate must be < 10-6. R19 The System MUST work in Full Duplex, using duplex POF. However the availability of Duplex service over simplex POF MAY be of interest. R20 The System MUST present a Latency < 5 ms in either direction. Services such as Gaming & VoIP require low latency. Note that adaptive data rates will require traffic management and will increase latency. For industrial automation Latency < 1ms SHOULD be required. R21 The system MUST operate in a temperature range of 0 ºC to +60 ºC and humidity in the range of 5 % to 95 %. R22 The system MUST operate in Class 1 or Class 1M for Eye Safety [3]. ETSI ETSI TS 105 175-1 V2.0.0 (2011-10) 11 |
59705d30c263f43062be240082eadcb7 | 105 175-1 | 5.2 Higher Level System Features | R23 The system SHOULD be conform to QoS specifications per channel as outlined in DSL Forum Technical Report TR-126 [4]. R24 The system MUST interoperate among multiple vendors systems to stimulate competition and ensure security features are common throughout vendors and SHOULD be interoperable at the specified data rate. R25 Bridges SHOULD be able to support both IPv4 & IPv6. R26 Devices SHOULD be 'Plug & Play', such that the user is able to install them very easily. R27 It SHOULD be possible to add/remove additional nodes without service interruption to existing nodes. R28 Devices SHOULD be transparent to either ACS or via a TR-069 [5] proxy on the HG (or other equipment) thus supporting the remote management of CPE such as switches and STBs that are linked by POF. |
59705d30c263f43062be240082eadcb7 | 105 175-1 | 6 Cabling solutions | 6.1 Cable and fibre R29 The cable SHALL be manufactured according to IEC 60794-2-41 [9]. R30 The cable MUST include 1 or 2 PMMA POF fibres. In the latter case one for the downstream and the other one for the upstream. R31 The PMMA [8] fibre MUST be compliant with the categories A4.a2, defined in the IEC 60793-2-40 [7] international standard regarding the POF fibres. R32 The fibre dimension (with the external coating) MUST be fitted according to the transceivers available on the market today (e.g. 1,5 mm or 2,2 mm). R33 The cable design MUST allow an easy access to the fibres. With this cable the termination of the cable with connector must be fast and easy. R34 Material used in the cable manufacturing MUST meet health requirements. For specific applications as e.g. public buildings, Cable MUST be available in fire retardant version according to IEC 60332 [13] and the national standards and specifications for public buildings. For installation in public areas POF cable MUST fulfil the requirements of IEC 61034-1/2 [25] and IEC 60754-1/2 [26]. For residential installation POF cable SHOULD fulfil the requirements of IEC 61034-1/2 and IEC 60754-1 [26]/2. 6.2 Connectors R35 Two different solutions for connectors MAY be chosen: The use of connectors already standardized like SMI (IEC 61754-21 [10]) or SC/RJ (IEC 61754-24 [12]) or F-SMA (IEC 61754-22 [11]) or SC (IEC 61754-4 [27]) or LC (IEC 61754-20 [28]) The use of connectorless solution (e.g. Optolock). ETSI ETSI TS 105 175-1 V2.0.0 (2011-10) 12 |
59705d30c263f43062be240082eadcb7 | 105 175-1 | 7 Installation | The PMMA POF solution is very attractive to do a point to point architecture in an already constructed house, because the installation of the cable could be performed by the user himself. Several installation configurations can be considered: the cable can be installed in existing ducts (empty or already used by a copper/electrical cable) or installed along the wall or plinths by stapling or gluing. In the case of a visible home-cabling the constraints applied on the cable could be stricter (several corners and doors). R36 The cable design MUST be adapted to support small bending radii without leading to a too high bending loss. A reference value of 0,5 dB attenuation for a 25 mm bending radius measured according to IEC 60793-1-47 [6], method B can be taken into account. |
59705d30c263f43062be240082eadcb7 | 105 175-1 | 8 Energy efficiency | Ultimately POF transceivers will be integrated in the user equipments thus reducing the number of power supplies hence the overall electrical consumption. An alternative to this would be to power up the media converter by means of USB interface or Power over Ethernet (PoE) on the RJ45 interface. Energy efficiency targets are set out in the EU Code of Conduct on Energy Consumption of Broad Band Equipment [14]. R37 The maximum power consumption MUST be < 0,4 W in full operation per port for 100 MbE POF transceiver; < 3,5 W (in low power mode) and <4,5 W (in full power mode) for 100 MbE and 1 GbE media converters. The target is to achieve as low power consumption as possible in the two mentioned operation modes,. Operation modes and targets present here are the 2011 targets of the EU Code of Conduct on Energy Consumption of Broad Band Equipment. R38 The devices SHOULD offer a standby mode and they shall enter this mode after a configurable period without any traffic. R39 The maximum power consumption in standby mode MUST be < 0,5 W. R40 The Power Mode Transition Time (the time transition from the standby mode to active mode when traffic is detected) MUST be < 1 s. |
59705d30c263f43062be240082eadcb7 | 105 175-1 | 9 Integrated Wall Plug | The equipment described in this clause permits the usage of POF in domestic environments, especially enabling POF insertion into existing ducts used for electrical wirings. The equipment has functions of bridge between POF and Ethernet technologies. The equipment consists of POF connector(s), Optical transceiver(s), Ethernet switch with VLAN management (optional), Fast or Gigabit Ethernet interface(s), RJ45 connector(s), Integrated power supply. Annex A shows, as an example, a form factor to be suited for different countries. R41 Power supply: the equipment MUST be powered with AC mains supply rate voltage at 50 Hz between at least 110 VAC and 230 VAC. R42 The equipment in standby mode (in absence of traffic) or in the no load condition (no Ethernet interface of PCs or appliances connected) SHOULD NOT exceed 0,5 W. R43 The efficiency of the internal power supply stage SHOULD be not less than [0,09 × ln(OutputPower) + 0,5]. R44 Lifetime of the integrated wall plug should be greater than 15 years . R45 The operational temperature MUST be comprise between -10 °C and +60 °C in all conditions according to IS 11801 [29]. ETSI ETSI TS 105 175-1 V2.0.0 (2011-10) 13 |
59705d30c263f43062be240082eadcb7 | 105 175-1 | 9.1 Interfaces - External sockets | R46 The wall plug MUST have 1 external energy socket according to specific country standard according to IEC 60884-1 [15] for general requirements. R47 The wall plug MUST have 1 or 2 RJ45 ports: 10/100/[1000 optional] BaseT/TX Ethernet port. R48 The BaseT/TX Ethernet interface MUST be compliant to the ISO/IEC 8802-3 [16] standard. R49 The BaseT/TX Ethernet interface SHOULD be autosensing for rate and type of UTP5 cables (straight and crossed). |
59705d30c263f43062be240082eadcb7 | 105 175-1 | 9.2 Interfaces - Internal sockets | R50 The wall plug MUST have 1 or 2 or 3 POF interfaces (each interface for a couple of POFs in order to allow a bi-directional communication). R51 The optical interface MUST be compliant with POF diameter according to the transceivers already available on the market today (e.g. 1,5 mm or 2,2 mm). R52 The installation procedure SHOULD be "easy" in order to simplify the connection to the electrical wiring, e.g. using a single device that replaces the existing one and requires just the connection of energy and POF wirings. R53 Aesthetic requirements: TBD according to customer requirements. |
59705d30c263f43062be240082eadcb7 | 105 175-1 | 9.3 Wall socket plugs versions | Four versions MUST be considered. R54 All versions MUST include one energy socket. a. Version 1 (basic) with 1 RJ45 (External) and 1 POF interface (Internal). b. Version 2 (pass-through) with 1 RJ45 (External) and 2 POF interfaces (Internal). c. Version 3 (optical splitter) with 1 RJ45 (External) and 3 POF interfaces (Internal). d. Version 4 (switch) with 2 RJ45 (External) 2 POF interfaces (Internal). R55 Other wall socket versions MAY be considered, e.g. without external energy socket. R56 An internal switch MUST be required for Ethernet packet management on all versions of the equipment. R57 The switch MUST be compliant with IEEE 802.3 [2] 10BaseT and IEEE 802.3u [i.1] 100BaseTX Ethernet specifications. R58 The switch MUST be compliant with IEEE 802.3x [i.3] Full duplex and Flow Control specifications. R59 The switch SHOULD support auto MDI/MDI-X function. R60 The internal switch MUST be transparent for tagged frames (e.g. TOS or VLAN tags). R61 An internal switch with VLAN management SHOULD be adopted for the version 2, 3 and 4 of the equipment. In addition to the previous points: a. It MUST be compliant with IEEE 802.1Q [i.4] VLAN management specifications. ETSI ETSI TS 105 175-1 V2.0.0 (2011-10) 14 b. It MUST be compliant with IEEE 802.1p [i.5] MAC layer QoS specifications: i. Configuration options MUST include VLANs assignment and QoS parameters; ii Device configuration reset MUST be possible (and SHOULD be reasonably easy). c. It MUST be managed via RJ45 ports or via POF ports with a layer 2 protocol: i. In alternative, it MUST be managed with web interface (or Telnet). d. It SHOULD be compliant with IEEE 802.1D [i.6] Spanning Tree for complex network topologies. R62 The equipment MUST be compliant with EN 60950-1 [17] in order to guarantee safety requirements for RJ45 external interfaces. R63 The equipment MUST be compliant with ITU-T Recommendation K.21 [18]. R64 According to the IEC 60825 series [3]the type of the customer premises is "unrestricted". As long as FTTH implementations respect hazard level 1 (IEC 60825 series [3]) at the customer premises, as well as laser class 1 or 1M (IEC 60825 series [3]) of the laser sources, no special requirements regarding marking or laser safety are necessary at the customer premises. R65 The equipment SHALL have an adequate mechanical robustness in order to comply with the following tests: a. Test Ea - Shock: according to IEC 60068-2-27 [19], with parameters defined for the Class 3.2 by the standard EN 300 019-2-3 [20]. b. Test Fc - Stationary Vibration: according to IEC 60068-2-6 [21], with parameters defined for the Class 3.2 by the standard EN 300 019-2-3 [20]. c. Test Fh - Random Vibration: according to IEC 60068-2-64 [22], with parameters defined for the Class 3.2 by the standard EN 300 019-2-3 [20]. R66 The equipment must compliant with EN 55022 [23] - class B limits. R67 The equipment must compliant with EN 55024 [24]. |
59705d30c263f43062be240082eadcb7 | 105 175-1 | 9.4 Sustainability requirements | R68 The equipment MUST : a. Minimize the number of used materials. b. Use recycled materials. c. Be manufactured with "lead-free" solder. d. Avoid using hazardous materials as per the RoHS Directive [1], with specific reference to PVC for coatings. R69 The equipment must be compliant with Code of Conduct for Broadband Equipment for issues concerning energy consumption [14] (C.1.2 table for Home Network Infrastructure Devices). ETSI ETSI TS 105 175-1 V2.0.0 (2011-10) 15 Annex A (informative): Integrated Wall Plug Form Factor In this annex it is reported, as an example, the form factor that could have the wall plug integrating the POF/Ethernet bridge as presented in clause 9. Each country can fit it according to national guides. Figure A.1: Example of Integrated Wall Plug ETSI ETSI TS 105 175-1 V2.0.0 (2011-10) 16 Annex B (informative): Bibliography CENELEC EN 60825-1: "Safety of laser products - Part 1: Equipment classification and requirements". ETSI ETSI TS 105 175-1 V2.0.0 (2011-10) 17 History Document history V1.1.1 January 2010 Publication V2.0.0 October 2011 Publication |
c66100fd3b052c710393f385ef3d4084 | 104 053-2 | 1 Scope | The present document specifies the Terrestrial Trunked Radio system (TETRA) set B encryption algorithms TEA 5, 6 and 7. These algorithms are designed to meet the requirements set out in the requirements specification for the Additional TETRA Encryption Algorithm Suite [i.2]. The TETRA Air interface security function provides mechanisms for confidentiality of control signalling and user speech and data at the air interface, authentication and key management mechanisms for the air interface and for the Inter-System Interface (ISI). TETRA Air Interface security mechanisms are described in the TETRA V+D security specification [1] and the TETRA Direct Mode security specification [2]. |
c66100fd3b052c710393f385ef3d4084 | 104 053-2 | 2 References | |
c66100fd3b052c710393f385ef3d4084 | 104 053-2 | 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 at 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 100 392-7: "Terrestrial Trunked Radio (TETRA); Voice plus Data (V+D); Part 7: Security". [2] ETSI TS 100 396-6: "Terrestrial Trunked Radio (TETRA); Direct Mode Operation (DMO); Part 6: Security". |
c66100fd3b052c710393f385ef3d4084 | 104 053-2 | 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 are not necessary for the application of the present document but they assist the user with regard to a particular subject area. [i.1] Daemen, J. and Rijmen, V. (1999): "AES proposal: Rijndael', document version 2". Submission to NIST AES competition (1999). [i.2] ETSI TCCE(21)000002r2: "Requirements Specification for the Additional TETRA Encryption Algorithm Suite". ETSI ETSI TS 104 053-2 V1.2.1 (2025-02) 6 |
c66100fd3b052c710393f385ef3d4084 | 104 053-2 | 3 Definition of terms, symbols and abbreviations | |
c66100fd3b052c710393f385ef3d4084 | 104 053-2 | 3.1 Terms | For the purposes of the present document, the following terms apply: Cipher Key (CK): value that is used to determine the transformation of plain text to cipher text in a cryptographic algorithm Initialization Vector (IV): sequence of symbols that randomize the KSG inside the encryption unit key stream: pseudo random stream of symbols that is generated by a KSG for encipherment and decipherment Key Stream Generator (KSG): cryptographic algorithm which produces a stream of binary digits, which can be used for encipherment and decipherment NOTE: The initial state of the KSG is determined by the IV value. Key Stream Segment (KSS): key stream of arbitrary length LENGTH: required length of the key stream in bits TEA set A: set of air interface encryption algorithms comprising TEA1, TEA2, TEA3 and TEA4 TEA set B: set of air interface encryption algorithms comprising TEA5, TEA6 and TEA7 TETRA algorithm: mathematical description of a cryptographic process used for either of the security processes authentication or encryption |
c66100fd3b052c710393f385ef3d4084 | 104 053-2 | 3.2 Symbols | Void. |
c66100fd3b052c710393f385ef3d4084 | 104 053-2 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: CK Cipher Key CKM Mode Key GF Galois Field IV Initialization Vector IVM Mode IV IVX eXpanded IV KSS Key Stream Segment ISI Inter System Interface KSG Key Stream Generator |
c66100fd3b052c710393f385ef3d4084 | 104 053-2 | 4 TEA encryption Set B Algorithm specifications | |
c66100fd3b052c710393f385ef3d4084 | 104 053-2 | 4.1 Input and Output Parameters | As specified in clause 8.3 of [i.2], the input parameters to the algorithm are: • an initialization vector IV consisting of 80 bits IV[0], …, IV[79]; • a cipher key CK consisting of 192 bits CK[0], …, CK[191]; ETSI ETSI TS 104 053-2 V1.2.1 (2025-02) 7 • the required length LENGTH of the key stream in bits. This can, according to [i.2], take any value from 1 up to 8 288. However, the design of the algorithm allows it to deliver, securely, a length of keystream up to 240 bits, making it potentially suitable for future applications where an increased length of KSS output is required. The corresponding output from the algorithm is then a key stream segment KSS consisting of LENGTH bits KSS[0], …, KSS[LENGTH-1]. |
c66100fd3b052c710393f385ef3d4084 | 104 053-2 | 5 TEA5 - Specification of the Algorithm | |
c66100fd3b052c710393f385ef3d4084 | 104 053-2 | 5.1 Introduction | In outline, the algorithm operates as follows: • the 80 bits of initialization vector IV, considered as 10 elements of the Galois field GF (28), are mixed using a 10-stage linear recursion over GF(28) to give 24 bytes which form a 192-bit mixed initialization vector IVX; • the cipher key CK and mixed initialization vector IVX are combined to produce a 192-bit Mode Key, CKM, and a 192-bit Mode IV, IVM; • successive 256-bit blocks are formed as a concatenation Mode IV || 'T', 'E', 'A', '5' || counter, where the byte values 'T', 'E', 'A', '5' code the name of the algorithm in ASCII, and the 32-bit counter takes successive values 0, 1, …; • these successive 256-blocks are encrypted using the variant of Rijndael [i.1] with parameters giving a block length of 256 bits and key length 192 bits. The Mode Key is used as the Rijndael key. The 256-bit blocks obtained as a result of these Rijndael encryptions are concatenated to form KSS; some bits will be discarded from the final ciphertext block if LENGTH is not exactly divisible by 256. The algorithm is specified precisely in clauses 5.2 to 5.6. |
c66100fd3b052c710393f385ef3d4084 | 104 053-2 | 5.2 TEA5 IV Expansion | The 80-bit IV is expanded to a 192-bit mixed IV, IVX, as follows: • from the initialization vector bits IV[0], …, IV[79], form 10 bytes b[0], …, b[9], where b[i] = 27 IV[8×i] + 26 IV[8×i+1] + … + IV[8×i+7], for i = 0, …, 9; • for any bits B[0], …, B[7], the byte is identified as 27B[0] + 26 B[1] + … + B[7] with the element z7B[0] + z6 B[1] + … + B[7] of GF(28), where z is a generator of GF(28) satisfying the Rijndael polynomial x8 + x4 + x3 + x + 1 in GF(2)[x]; • for i = 10, …, 43, a byte b[i] is obtained from bytes b[i-1], …, b[i-10] according to the rule b[i] = b[i-10] ⊕ b[i-9] ⊕ (z7 + z6 + z4 + z2 + z + 1) b[i-1]. The byte (z7 + z6 + z4 + z2 + z + 1) b[i-1] can be obtained from b[i-1] using the lookup table defined in clause 5.5; • the 24 bytes b[20], b[21], …, b[43] contain the bits IVX[0], …, IVX[191], where b[20+i] = 27 IVX[8i] + 26 IVX[8i + 1] + … + IVX[8i + 7] for i = 0, …, 23. This process is illustrated in figures 1 and 2 below. ETSI ETSI TS 104 053-2 V1.2.1 (2025-02) 8 Figure 1: IV expansion Figure 2: IVX extraction |
c66100fd3b052c710393f385ef3d4084 | 104 053-2 | 5.3 TEA5 Derivation of the Mode Key and Mode IV | The Mode Key consists of 192 bits CKM[0], …, CKM[191] and the Mode IV consists of 192 bits IVM[0], …, IVM[191]. An 8-bit to 8-bit combining function f is applied to successive 8-bit inputs formed from 4 bits of the cipher key CK and 4 bits from the mixed initialization vector IVX, and the result is taken to be a further 4 bits of Mode Key and 4 bits of Mode IV. More precisely, for each i in the range 0, …, 47, 27CKM[4i] + 26CKM[4i+1] + … + 24CKM[4i+3] + 23IVM[4i] + 22IVM[4i+1] + … + IVM[4i+3] = f(27CK[4i] + 26CK[4i+1] + … + 24CK[4i+3] + 23IVX[4i] + 22IVX[4i+1] + … + IVX[4i+3]) The combining function f is defined in clause 5.6. The process for deriving the Mode Key and Mode IV from the cipher key CK and mixed initialization vector IVX is illustrated in figure 3 below. Figure 3: Mode Key and Mode IV derivation ETSI ETSI TS 104 053-2 V1.2.1 (2025-02) 9 |
c66100fd3b052c710393f385ef3d4084 | 104 053-2 | 5.4 TEA5 Derivation of the Keystream Bits | The keystream bits KSS are obtained using Rijndael [i.1] with key length 192 bits and block size 256 bits, used in a counter mode. The key used is the Mode Key CKM, arranged into bytes 27CKM[8i] + 26CKM[8i+1] + … + CKM[8i+7] for i = 0, …, 23. The Rijndael algorithm is run in encryption mode to encrypt LENGTH/256 successive plaintext blocks, where the notation LENGTH/256 denotes the least integer ≥ the floating-point quotient LENGTH/256. The plaintext for encryption j, for j = 0, …, LENGTH/256 -1, is, informally, IVM || 'T', 'E', 'A', '5' || j, where the byte values 'T', 'E', 'A', '5' code the name of the algorithm in ASCII, and j is coded as 4 bytes; more precisely, it is the 32-byte sequence p0, …, p31, where: • pi = 27IVM[8i] + 26IVM[8i+1] + … + IVM[8i+7] for i = 0, …, 23; • p24 = 84, p25 = 69, p26 = 65, p27 = 53 (those four values being in decimal); • 224p28 + 216p29 + 28p30 + p31 = j. The keystream bit KSS[i] is the bit Cs[t], which is written as: • i = 256r + 8s + t, for 0 ≤ s ≤ 31 and 0 ≤ t ≤ 7; • c0, …, c31 are the ciphertext bytes obtained from the encryption where j = r; • cs = 27Cs[0] + 26Cs[1] + … + Cs[7], for bits Cs[0], …, Cs[7]. Note that if (LENGTH mod 256) ≤ 248 then one or more higher numbered ciphertext bytes from the last block will be discarded. If (LENGTH mod 8) > 0 then one or more less significant bits from the last used ciphertext byte will be discarded. Note that the maximum value of LENGTH, the number of bits of required keystream, is 8 288, according to the specification [i.2]. Since this maximum number of required keystream bits ≤ 216, the 32-bit counter j can be implemented as an 8-bit counter with the other three bytes fixed to zero. If, in a future application, the maximum number of bits of required keystream is no more than 224 bits, then the 32-bit counter can be implemented as a 16-bit counter with the other two bytes fixed to zero. If a full range of values for the 32-bit counter is implemented, keystream sequences of length up to 240 can be generated. The use of Rijndael in counter mode to produce keystream bits is shown in figure 4 below. Figure 4: Keystream generation ETSI ETSI TS 104 053-2 V1.2.1 (2025-02) 10 |
c66100fd3b052c710393f385ef3d4084 | 104 053-2 | 5.5 TEA5 - Lookup Table for IV Mixing | Table 1 implements Galois Field multiplication by z7 + z6 + z4 + z2 + z + 1, as discussed in clause 5.2. Different rows correspond to different values of the most significant 4 bits of the input, and columns to the least significant 4 bits. For example, the value corresponding to 0x12 is found in the row labelled 0x1? and column labelled 0x?2, and is the byte value 0x6a. Table 1 0x?0 0x?1 0x?2 0x?3 0x?4 0x?5 0x?6 0x?7 0x?8 0x?9 0x?a 0x?b 0x?c 0x?d 0x?e 0x?f 0x0? 0x00 0xd7 0xb5 0x62 0x71 0xa6 0xc4 0x13 0xe2 0x35 0x57 0x80 0x93 0x44 0x26 0xf1 0x1? 0xdf 0x08 0x6a 0xbd 0xae 0x79 0x1b 0xcc 0x3d 0xea 0x88 0x5f 0x4c 0x9b 0xf9 0x2e 0x2? 0xa5 0x72 0x10 0xc7 0xd4 0x03 0x61 0xb6 0x47 0x90 0xf2 0x25 0x36 0xe1 0x83 0x54 0x3? 0x7a 0xad 0xcf 0x18 0x0b 0xdc 0xbe 0x69 0x98 0x4f 0x2d 0xfa 0xe9 0x3e 0x5c 0x8b 0x4? 0x51 0x86 0xe4 0x33 0x20 0xf7 0x95 0x42 0xb3 0x64 0x06 0xd1 0xc2 0x15 0x77 0xa0 0x5? 0x8e 0x59 0x3b 0xec 0xff 0x28 0x4a 0x9d 0x6c 0xbb 0xd9 0x0e 0x1d 0xca 0xa8 0x7f 0x6? 0xf4 0x23 0x41 0x96 0x85 0x52 0x30 0xe7 0x16 0xc1 0xa3 0x74 0x67 0xb0 0xd2 0x05 0x7? 0x2b 0xfc 0x9e 0x49 0x5a 0x8d 0xef 0x38 0xc9 0x1e 0x7c 0xab 0xb8 0x6f 0x0d 0xda 0x8? 0xa2 0x75 0x17 0xc0 0xd3 0x04 0x66 0xb1 0x40 0x97 0xf5 0x22 0x31 0xe6 0x84 0x53 0x9? 0x7d 0xaa 0xc8 0x1f 0x0c 0xdb 0xb9 0x6e 0x9f 0x48 0x2a 0xfd 0xee 0x39 0x5b 0x8c 0xa? 0x07 0xd0 0xb2 0x65 0x76 0xa1 0xc3 0x14 0xe5 0x32 0x50 0x87 0x94 0x43 0x21 0xf6 0xb? 0xd8 0x0f 0x6d 0xba 0xa9 0x7e 0x1c 0xcb 0x3a 0xed 0x8f 0x58 0x4b 0x9c 0xfe 0x29 0xc? 0xf3 0x24 0x46 0x91 0x82 0x55 0x37 0xe0 0x11 0xc6 0xa4 0x73 0x60 0xb7 0xd5 0x02 0xd? 0x2c 0xfb 0x99 0x4e 0x5d 0x8a 0xe8 0x3f 0xce 0x19 0x7b 0xac 0xbf 0x68 0x0a 0xdd 0xe? 0x56 0x81 0xe3 0x34 0x27 0xf0 0x92 0x45 0xb4 0x63 0x01 0xd6 0xc5 0x12 0x70 0xa7 0xf? 0x89 0x5e 0x3c 0xeb 0xf8 0x2f 0x4d 0x9a 0x6b 0xbc 0xde 0x09 0x1a 0xcd 0xaf 0x78 |
c66100fd3b052c710393f385ef3d4084 | 104 053-2 | 5.6 TEA5 - Definition of the Combining Function f | Table 2 defines the combining function f, which is used as defined in clause 5.3. Different rows correspond to different values of the most significant 4 bits of the input, and columns to the least significant 4 bits. For example, the value corresponding to 0x12 is found in the row labelled 0x1? and column labelled 0x?2, and is the byte value 0xcc. Table 2 0x?0 0x?1 0x?2 0x?3 0x?4 0x?5 0x?6 0x?7 0x?8 0x?9 0x?a 0x?b 0x?c 0x?d 0x?e 0x?f 0x0? 0x91 0x64 0x2c 0xc3 0x80 0xd8 0x32 0x5e 0x16 0xe7 0x09 0xbd 0x4f 0xa5 0xfa 0x7b 0x1? 0xbb 0x41 0xcc 0x67 0x36 0xe3 0x7d 0xa9 0x8e 0x52 0xf0 0xd4 0x28 0x1f 0x9a 0x05 0x2? 0xaf 0x92 0x78 0x33 0x4e 0xb6 0x8d 0xc7 0xd5 0xf9 0x11 0x60 0xec 0x04 0x5a 0x2b 0x3? 0x7c 0xd1 0x6f 0x57 0xa6 0x10 0xb9 0x25 0x43 0x0d 0x3b 0x9e 0xf8 0xe4 0x82 0xca 0x4? 0x5c 0x8a 0xe9 0x0e 0xb8 0xa2 0x66 0xf3 0x34 0x15 0x70 0x47 0x9f 0xcd 0x21 0xdb 0x5? 0x4c 0xb5 0xf1 0xe2 0x7f 0xce 0x90 0x1a 0x63 0x88 0xd6 0x2d 0x07 0x39 0xab 0x54 0x6? 0x2f 0x1d 0x89 0xf6 0xe1 0x0c 0xae 0xb3 0x97 0x45 0xc8 0x3a 0x74 0x50 0xd2 0x6b 0x7? 0x3e 0x01 0xdd 0x20 0xcf 0x62 0x1c 0xe8 0xba 0x76 0x55 0xa3 0x87 0x99 0x44 0xfb 0x8? 0x8f 0xee 0x13 0x7a 0xf5 0x49 0xc0 0xd7 0x08 0x3d 0xa4 0x5b 0x61 0x26 0xb2 0x9c 0x9? 0xdf 0x3c 0xa8 0x94 0x27 0x73 0x0a 0x8b 0x51 0xc9 0x65 0xe6 0xb0 0xfd 0x1e 0x42 0xa? 0x1b 0xfe 0x37 0xa1 0xd0 0x23 0xea 0x9d 0x72 0x6c 0xbf 0xc4 0x59 0x48 0x06 0x85 0xb? 0xe5 0x24 0x98 0xd3 0x5d 0x81 0xfc 0x69 0xc6 0xa0 0x4a 0x0b 0x12 0xb7 0x7e 0x3f 0xc? 0xff 0xc2 0x00 0x84 0x93 0x58 0x46 0x75 0xa7 0x2e 0xeb 0x19 0xda 0x6d 0x31 0xbc 0xd? 0x0f 0x79 0x56 0x40 0x14 0xf7 0x22 0x35 0xed 0xbe 0x9b 0x83 0xc1 0xdc 0x68 0xaa 0xe? 0xc5 0xad 0x4b 0xb1 0x6e 0x96 0x53 0x02 0x2a 0xd9 0x8c 0xf4 0x30 0x77 0xef 0x18 0xf? 0x6a 0x5f 0xb4 0x17 0x03 0x38 0xde 0x4d 0xf2 0x95 0x29 0x71 0xac 0x86 0xcb 0xe0 ETSI ETSI TS 104 053-2 V1.2.1 (2025-02) 11 |
c66100fd3b052c710393f385ef3d4084 | 104 053-2 | 6 TEA6 - Specification of the Algorithm | |
c66100fd3b052c710393f385ef3d4084 | 104 053-2 | 6.1 Introduction | In outline, the algorithm operates as follows: • the 80 bits of initialization vector IV, considered as 10 elements of the Galois field GF(28), are mixed using a 10-stage linear recursion over GF(28) to give 24 bytes which form a 192-bit mixed initialization vector IVX; • the cipher key CK and mixed initialization vector IVX are combined to produce a 192-bit Mode Key, CKM, and a 192-bit Mode IV, IVM; • successive 256-bit blocks are formed as a concatenation Mode IV || 'T', 'E', 'A', '6' || counter, where the byte values 'T', 'E', 'A', '6' code the name of the algorithm in ASCII, and the 32-bit counter takes successive values 0, 1, …; • these successive 256-blocks are encrypted using the variant of Rijndael [i.1] with parameters giving a block length of 256 bits and key length 192 bits. The Mode Key is used as the Rijndael key. The 256-bit blocks obtained as a result of these Rijndael encryptions are concatenated to form KSS; some bits will be discarded from the final ciphertext block if LENGTH is not exactly divisible by 256. The algorithm is specified precisely in clauses 6.2 to 6.6. |
c66100fd3b052c710393f385ef3d4084 | 104 053-2 | 6.2 TEA6 - IV Expansion | The 80-bit IV is expanded to a 192-bit mixed IV, IVX, as follows: • from the initialization vector bits IV[0], …, IV[79], form 10 bytes b[0], …, b[9], where b[i] = 27 IV[8×i] + 26 IV[8×i+1] + … + IV[8×i+7], for i = 0, …, 9; • for any bits B[0], …, B[7], the byte is identified as 27B[0] + 26 B[1] + … + B[7] with the element z7B[0] + z6 B[1] + … + B[7] of GF(28), where z is a generator of GF(28) satisfying the Rijndael polynomial x8 + x4 + x3 + x + 1 in GF(2)[x]; • for i = 10, …, 43, a byte b[i] is obtained from bytes b[i-1], …, b[i-10] according to the rule b[i] = b[i-10] ⊕ b[i-9] ⊕ (z7 + z6 + z4 + z2 + z + 1) b[i-1]. The byte (z7 + z6 + z4 + z2 + z + 1) b[i-1] can be obtained from b[i-1] using the lookup table defined in clause 6.5; • the 24 bytes b[20], b[21], …, b[43] contain the bits IVX[0], …, IVX[191], where b[20+i] = 27 IVX[8i] + 26 IVX[8i + 1] + … + IVX[8i + 7] for i = 0, …, 23. This process is illustrated in figures 5 and 6 below. ETSI ETSI TS 104 053-2 V1.2.1 (2025-02) 12 Figure 5: TEA6 - IV expansion Figure 6: TEA6 - IVX extraction |
c66100fd3b052c710393f385ef3d4084 | 104 053-2 | 6.3 TEA6 - Derivation of the Mode Key and Mode IV | The Mode Key consists of 192 bits CKM[0], …, CKM[191] and the Mode IV consists of 192 bits IVM[0], …, IVM[191]. An 8-bit to 8-bit combining function f is applied to successive 8-bit inputs formed from 4 bits of the cipher key CK and 4 bits from the mixed initialization vector IVX, and the result is taken to be a further 4 bits of Mode Key and 4 bits of Mode IV. More precisely, for each i in the range 0, …, 47, 27CKM[4i] + 26CKM[4i+1] + … + 24CKM[4i+3] + 23IVM[4i] + 22IVM[4i+1] + … + IVM[4i+3] = f(27CK[4i] + 26CK[4i+1] + … + 24CK[4i+3] + 23IVX[4i] + 22IVX[4i+1] + … + IVX[4i+3]) The combining function f is defined in clause 6.6. The process for deriving the Mode Key and Mode IV from the cipher key CK and mixed initialization vector IVX is illustrated in figure 7 below. Figure 7: TEA6 Mode Key and Mode IV derivation ETSI ETSI TS 104 053-2 V1.2.1 (2025-02) 13 |
c66100fd3b052c710393f385ef3d4084 | 104 053-2 | 6.4 TEA6 - Derivation of the Keystream Bits | The keystream bits KSS are obtained using Rijndael [i.1] with key length 192 bits and block size 256 bits, used in a counter mode. The key used is the Mode Key CKM, arranged into bytes 27CKM[8i] + 26CKM[8i+1] + … + CKM[8i+7] for i = 0, …, 23. The Rijndael algorithm is run in encryption mode to encrypt LENGTH/256 successive plaintext blocks, where the notation LENGTH/256 denotes the least integer ≥ the floating-point quotient LENGTH/256. The plaintext for encryption j, for j = 0, …, LENGTH/256 -1, is, informally, IVM || 'T', 'E', 'A', '6' || j, where the byte values 'T', 'E', 'A', '6' code the name of the algorithm in ASCII, and j is coded as 4 bytes; more precisely, it is the 32-byte sequence p0, …, p31, where: • pi = 27IVM[8i] + 26IVM[8i+1] + … + IVM[8i+7] for i = 0, …, 23; • p24 = 84, p25 = 69, p26 = 65, p27 = 53 (those four values being in decimal); • 224p28 + 216p29 + 28p30 + p31 = j. The keystream bit KSS[i] is the bit Cs[t], where: • it is written as i = 256r + 8s + t, for 0 ≤ s ≤ 31 and 0 ≤ t ≤ 7; • c0, …, c31 are the ciphertext bytes obtained from the encryption where j = r; • cs = 27Cs[0] + 26Cs[1] + … + Cs[7], for bits Cs[0], …, Cs[7]. Note that if (LENGTH mod 256) ≤ 248 then one or more higher numbered ciphertext bytes from the last block will be discarded. If (LENGTH mod 8) > 0 then one or more less significant bits from the last used ciphertext byte will be discarded. Note that the maximum value of LENGTH, the number of bits of required keystream, is 8 288, according to the specification [i.2]. Since this maximum number of required keystream bits ≤ 216, the 32-bit counter j can be implemented as an 8-bit counter with the other three bytes fixed to zero. If, in a future application, the maximum number of bits of required keystream is no more than 224 bits, then the 32-bit counter can be implemented as a 16-bit counter with the other two bytes fixed to zero. If a full range of values for the 32-bit counter is implemented, keystream sequences of length up to 240 can be generated. The use of Rijndael in counter mode to produce keystream bits is shown in figure 8 below. Figure 8: TEA6 Keystream generation ETSI ETSI TS 104 053-2 V1.2.1 (2025-02) 14 |
c66100fd3b052c710393f385ef3d4084 | 104 053-2 | 6.5 TEA6 - Lookup Table for IV Mixing | Table 3 implements Galois Field multiplication by z7 + z6 + z4 + z2 + z + 1, as discussed in clause 6.2. Different rows correspond to different values of the most significant 4 bits of the input, and columns to the least significant 4 bits. For example, the value corresponding to 0x12 is found in the row labelled 0x1? and column labelled 0x?2, and is the byte value 0x6a. Table 3 0x?0 0x?1 0x?2 0x?3 0x?4 0x?5 0x?6 0x?7 0x?8 0x?9 0x?a 0x?b 0x?c 0x?d 0x?e 0x?f 0x0? 0x00 0xd7 0xb5 0x62 0x71 0xa6 0xc4 0x13 0xe2 0x35 0x57 0x80 0x93 0x44 0x26 0xf1 0x1? 0xdf 0x08 0x6a 0xbd 0xae 0x79 0x1b 0xcc 0x3d 0xea 0x88 0x5f 0x4c 0x9b 0xf9 0x2e 0x2? 0xa5 0x72 0x10 0xc7 0xd4 0x03 0x61 0xb6 0x47 0x90 0xf2 0x25 0x36 0xe1 0x83 0x54 0x3? 0x7a 0xad 0xcf 0x18 0x0b 0xdc 0xbe 0x69 0x98 0x4f 0x2d 0xfa 0xe9 0x3e 0x5c 0x8b 0x4? 0x51 0x86 0xe4 0x33 0x20 0xf7 0x95 0x42 0xb3 0x64 0x06 0xd1 0xc2 0x15 0x77 0xa0 0x5? 0x8e 0x59 0x3b 0xec 0xff 0x28 0x4a 0x9d 0x6c 0xbb 0xd9 0x0e 0x1d 0xca 0xa8 0x7f 0x6? 0xf4 0x23 0x41 0x96 0x85 0x52 0x30 0xe7 0x16 0xc1 0xa3 0x74 0x67 0xb0 0xd2 0x05 0x7? 0x2b 0xfc 0x9e 0x49 0x5a 0x8d 0xef 0x38 0xc9 0x1e 0x7c 0xab 0xb8 0x6f 0x0d 0xda 0x8? 0xa2 0x75 0x17 0xc0 0xd3 0x04 0x66 0xb1 0x40 0x97 0xf5 0x22 0x31 0xe6 0x84 0x53 0x9? 0x7d 0xaa 0xc8 0x1f 0x0c 0xdb 0xb9 0x6e 0x9f 0x48 0x2a 0xfd 0xee 0x39 0x5b 0x8c 0xa? 0x07 0xd0 0xb2 0x65 0x76 0xa1 0xc3 0x14 0xe5 0x32 0x50 0x87 0x94 0x43 0x21 0xf6 0xb? 0xd8 0x0f 0x6d 0xba 0xa9 0x7e 0x1c 0xcb 0x3a 0xed 0x8f 0x58 0x4b 0x9c 0xfe 0x29 0xc? 0xf3 0x24 0x46 0x91 0x82 0x55 0x37 0xe0 0x11 0xc6 0xa4 0x73 0x60 0xb7 0xd5 0x02 0xd? 0x2c 0xfb 0x99 0x4e 0x5d 0x8a 0xe8 0x3f 0xce 0x19 0x7b 0xac 0xbf 0x68 0x0a 0xdd 0xe? 0x56 0x81 0xe3 0x34 0x27 0xf0 0x92 0x45 0xb4 0x63 0x01 0xd6 0xc5 0x12 0x70 0xa7 0xf? 0x89 0x5e 0x3c 0xeb 0xf8 0x2f 0x4d 0x9a 0x6b 0xbc 0xde 0x09 0x1a 0xcd 0xaf 0x78 |
c66100fd3b052c710393f385ef3d4084 | 104 053-2 | 6.6 TEA6 - Definition of the Combining Function f | Table 4 defines the combining function f, which is used as defined in clause 6.3. Different rows correspond to different values of the most significant 4 bits of the input, and columns to the least significant 4 bits. For example, the value corresponding to 0x12 is found in the row labelled 0x1? and column labelled 0x?2, and is the byte value 0x20. Table 4 0x?0 0x?1 0x?2 0x?3 0x?4 0x?5 0x?6 0x?7 0x?8 0x?9 0x?a 0x?b 0x?c 0x?d 0x?e 0x?f 0x0? 0xc3 0x56 0x32 0x09 0x70 0xd8 0xfc 0xed 0x2a 0xb7 0x1b 0x61 0xaf 0x84 0x9e 0x45 0x1? 0x91 0x3f 0x20 0xe6 0x65 0x73 0x49 0xae 0x0c 0x5b 0x88 0xba 0x12 0xc7 0xfd 0xd4 0x2? 0xef 0xc0 0x55 0x3e 0x42 0xb4 0x68 0x9c 0xa9 0x07 0xd3 0x2b 0xfa 0x1d 0x76 0x81 0x3? 0xb1 0x24 0xe9 0xdb 0xa6 0x80 0x95 0x5c 0x6d 0xf7 0x3a 0xc8 0x72 0x4f 0x13 0x0e 0x4? 0x14 0xb6 0x4b 0x90 0xdc 0xc2 0x78 0x2f 0xe3 0x8e 0x0a 0xa1 0x37 0xf5 0x5d 0x69 0x5? 0x62 0x9b 0xad 0xc4 0x5e 0x15 0xd7 0x00 0x8a 0x36 0xf9 0x71 0xbf 0x23 0x4c 0xe8 0x6? 0xab 0x7e 0x67 0x1a 0x85 0x21 0x38 0xbd 0xf0 0x44 0x5f 0x03 0x92 0xd9 0xec 0xc6 0x7? 0x43 0x0d 0xc5 0x89 0xff 0x60 0x52 0x11 0x34 0xe7 0xbe 0x9a 0xd6 0x7b 0x2c 0xa8 0x8? 0x01 0x64 0x9f 0x4a 0x30 0xfe 0x26 0x8b 0xcc 0x18 0x77 0xdd 0xe2 0xb5 0xa3 0x59 0x9? 0x79 0xd2 0x8f 0xf6 0xee 0x93 0xb8 0x3c 0x41 0xcd 0xa0 0x17 0x6a 0x54 0x0b 0x25 0xa? 0x87 0xe1 0xd5 0x6e 0x22 0xa4 0x08 0xcb 0x1c 0x9d 0x46 0xf3 0x5a 0x39 0xb0 0x7f 0xb? 0xdf 0x82 0x7d 0x51 0xce 0x47 0x16 0xfb 0x99 0xaa 0x28 0xe0 0x04 0x6c 0x35 0xb3 0xc? 0x3d 0x10 0x02 0x7c 0x97 0x53 0xa5 0x48 0xb9 0x2e 0x6b 0x86 0xcf 0xe4 0xda 0xf1 0xd? 0xf4 0xac 0x1f 0x27 0xb2 0xeb 0xc9 0x7a 0x58 0xde 0x96 0x40 0x8d 0x05 0x63 0x31 0xe? 0x29 0xf2 0xbc 0xa7 0x06 0x3b 0x83 0x6f 0xd1 0x74 0xe5 0x50 0x4d 0x98 0xca 0x1e 0xf? 0x57 0x4e 0xf8 0xbb 0x19 0x0f 0xea 0xd0 0x75 0x66 0xc1 0x33 0x2d 0xa2 0x8c 0x94 ETSI ETSI TS 104 053-2 V1.2.1 (2025-02) 15 |
c66100fd3b052c710393f385ef3d4084 | 104 053-2 | 7 TEA7-Specification of the Algorithm | |
c66100fd3b052c710393f385ef3d4084 | 104 053-2 | 7.1 Introduction | In outline, the algorithm operates as follows: • the 80 bits of initialization vector IV, considered as 10 elements of the Galois field GF(28), are mixed using a 10-stage linear recursion over GF(28) to give 24 bytes which form a 192-bit mixed initialization vector IVX; • the cipher key CK and mixed initialization vector IVX are combined to produce a 192-bit Mode Key, CKM, and a 192-bit Mode IV, IVM; • successive 256-bit blocks are formed as a concatenation Mode IV || 'T', 'E', 'A', '7' || counter, where the byte values 'T', 'E', 'A', '7' code the name of the algorithm in ASCII, and the 32-bit counter takes successive values 0, 1, …; • these successive 256-blocks are encrypted using the variant of Rijndael [i.1] with parameters giving a block length of 256 bits and key length 192 bits. The Mode Key is used as the Rijndael key. The 256-bit blocks obtained as a result of these Rijndael encryptions are concatenated to form KSS; some bits will be discarded from the final ciphertext block if LENGTH is not exactly divisible by 256. The algorithm is specified precisely in clauses 7.2 to 7.6. |
c66100fd3b052c710393f385ef3d4084 | 104 053-2 | 7.2 TEA7- IV Expansion | The 80-bit IV is expanded to a 192-bit mixed IV, IVX, as follows: • from the initialization vector bits IV[0], …, IV[79], form 10 bytes b[0], …, b[9], where b[i] = 27 IV[8×i] + 26 IV[8×i+1] + … + IV[8×i+7], for i = 0, …, 9; • for any bits B[0], …, B[7], the byte is identified as 27B[0] + 26 B[1] + … + B[7] with the element z7B[0] + z6 B[1] + … + B[7] of GF(28), where z is a generator of GF(28) satisfying the Rijndael polynomial x8 + x4 + x3 + x + 1 in GF(2)[x]; • for i = 10, …, 43, a byte b[i] is obtained from bytes b[i-1], …, b[i-10] according to the rule b[i] = b[i-10] ⊕ b[i-9] ⊕ (z7 + z6 + z4 + z2 + z + 1) b[i-1]. The byte (z7 + z6 + z4 + z2 + z + 1) b[i-1] can be obtained from b[i-1] using the lookup table defined in clause 7.5; • the 24 bytes b[20], b[21], …, b[43] contain the bits IVX[0], …, IVX[191], where b[20+i] = 27 IVX[8i] + 26 IVX[8i + 1] + … + IVX[8i + 7] for i = 0, …, 23. This process is illustrated in figures 9 and 10 below. ETSI ETSI TS 104 053-2 V1.2.1 (2025-02) 16 Figure 9: TEA7- IV expansion Figure 10: TEA7- IVX extraction |
c66100fd3b052c710393f385ef3d4084 | 104 053-2 | 7.3 TEA7- Derivation of the Mode Key and Mode IV | The Mode Key consists of 192 bits CKM[0], …, CKM[191] and the Mode IV consists of 192 bits IVM[0], …, IVM[191]. An 8-bit to 8-bit combining function f is applied to successive 8-bit inputs formed from 4 bits of the cipher key CK and 4 bits from the mixed initialization vector IVX, and the result is taken to be a further 4 bits of Mode Key and 4 bits of Mode IV. More precisely, for each i in the range 0, …, 47, 27CKM[4i] + 26CKM[4i+1] + … + 24CKM[4i+3] + 23IVM[4i] + 22IVM[4i+1] + … + IVM[4i+3] = f(27CK[4i] + 26CK[4i+1] + … + 24CK[4i+3] + 23IVX[4i] + 22IVX[4i+1] + … + IVX[4i+3]) The combining function f is defined in clause 7.5. The process for deriving the Mode Key and Mode IV from the cipher key CK and mixed initialization vector IVX is illustrated in figure 11 below. ETSI ETSI TS 104 053-2 V1.2.1 (2025-02) 17 Figure 11: TEA7- Mode Key and Mode IV derivation |
c66100fd3b052c710393f385ef3d4084 | 104 053-2 | 7.4 TEA7- Derivation of the Keystream Bits | The keystream bits KSS are obtained using Rijndael [i.1] with key length 192 bits and block size 256 bits, used in a counter mode. The key used is the Mode Key CKM, arranged into bytes 27CKM[8i] + 26CKM[8i+1] + … + CKM[8i+7] for i = 0, …, 23. The Rijndael algorithm is run in encryption mode to encrypt LENGTH/256 successive plaintext blocks, where the notation LENGTH/256 denotes the least integer ≥ the floating-point quotient LENGTH/256. The plaintext for encryption j, for j = 0, …, LENGTH/256 -1, is, informally, IVM || 'T', 'E', 'A', '7' || j, where the byte values 'T', 'E', 'A', '7' code the name of the algorithm in ASCII, and j is coded as 4 bytes; more precisely, it is the 32-byte sequence p0, …, p31, where: • pi = 27IVM[8i] + 26IVM[8i+1] + … + IVM[8i+7] for i = 0, …, 23; • p24 = 84, p25 = 69, p26 = 65, p27 = 55 (those four values being in decimal); • 224p28 + 216p29 + 28p30 + p31 = j. The keystream bit KSS[i] is the bit C5[t], where: • it is written as i = 256r + 8s + t, for 0 ≤ s ≤ 31 and 0 ≤ t ≤ 7; • c0, …, c31 are the ciphertext bytes obtained from the encryption where j = r; • cs = 27Cs[0] + 26Cs[1] + … + Cs[7], for bits Cs[0], …, Cs[7]. Note that if (LENGTH mod 256) ≤ 248 then one or more higher numbered ciphertext bytes from the last block will be discarded. If (LENGTH mod 8) > 0 then one or more less significant bits from the last used ciphertext byte will be discarded. Note that the maximum value of LENGTH, the number of bits of required keystream, is 8 288, according to the specification [i.2]. Since this maximum number of required keystream bits ≤ 216, the 32-bit counter j can be implemented as an 8-bit counter with the other three bytes fixed to zero. If, in a future application, the maximum number of bits of required keystream is no more than 224 bits, then the 32-bit counter can be implemented as a 16-bit counter with the other two bytes fixed to zero. If a full range of values for the 32-bit counter is implemented, keystream sequences of length up to 240 can be generated. The use of Rijndael in counter mode to produce keystream bits is shown in figure 12 below. ETSI ETSI TS 104 053-2 V1.2.1 (2025-02) 18 Figure 12: Keystream generation |
c66100fd3b052c710393f385ef3d4084 | 104 053-2 | 7.5 TEA7 - Lookup Table for IV Mixing | Table 5 implements Galois Field multiplication by z7 + z6 + z4 + z2 + z + 1, as discussed in clause 7.2. Different rows correspond to different values of the most significant 4 bits of the input, and columns to the least significant 4 bits. For example, the value corresponding to 0x12 is found in the row labelled 0x1? and column labelled 0x?2, and is the byte value 0x6a. Table 5 0x?0 0x?1 0x?2 0x?3 0x?4 0x?5 0x?6 0x?7 0x?8 0x?9 0x?a 0x?b 0x?c 0x?d 0x?e 0x?f 0x0? 0x00 0xd7 0xb5 0x62 0x71 0xa6 0xc4 0x13 0xe2 0x35 0x57 0x80 0x93 0x44 0x26 0xf1 0x1? 0xdf 0x08 0x6a 0xbd 0xae 0x79 0x1b 0xcc 0x3d 0xea 0x88 0x5f 0x4c 0x9b 0xf9 0x2e 0x2? 0xa5 0x72 0x10 0xc7 0xd4 0x03 0x61 0xb6 0x47 0x90 0xf2 0x25 0x36 0xe1 0x83 0x54 0x3? 0x7a 0xad 0xcf 0x18 0x0b 0xdc 0xbe 0x69 0x98 0x4f 0x2d 0xfa 0xe9 0x3e 0x5c 0x8b 0x4? 0x51 0x86 0xe4 0x33 0x20 0xf7 0x95 0x42 0xb3 0x64 0x06 0xd1 0xc2 0x15 0x77 0xa0 0x5? 0x8e 0x59 0x3b 0xec 0xff 0x28 0x4a 0x9d 0x6c 0xbb 0xd9 0x0e 0x1d 0xca 0xa8 0x7f 0x6? 0xf4 0x23 0x41 0x96 0x85 0x52 0x30 0xe7 0x16 0xc1 0xa3 0x74 0x67 0xb0 0xd2 0x05 0x7? 0x2b 0xfc 0x9e 0x49 0x5a 0x8d 0xef 0x38 0xc9 0x1e 0x7c 0xab 0xb8 0x6f 0x0d 0xda 0x8? 0xa2 0x75 0x17 0xc0 0xd3 0x04 0x66 0xb1 0x40 0x97 0xf5 0x22 0x31 0xe6 0x84 0x53 0x9? 0x7d 0xaa 0xc8 0x1f 0x0c 0xdb 0xb9 0x6e 0x9f 0x48 0x2a 0xfd 0xee 0x39 0x5b 0x8c 0xa? 0x07 0xd0 0xb2 0x65 0x76 0xa1 0xc3 0x14 0xe5 0x32 0x50 0x87 0x94 0x43 0x21 0xf6 0xb? 0xd8 0x0f 0x6d 0xba 0xa9 0x7e 0x1c 0xcb 0x3a 0xed 0x8f 0x58 0x4b 0x9c 0xfe 0x29 0xc? 0xf3 0x24 0x46 0x91 0x82 0x55 0x37 0xe0 0x11 0xc6 0xa4 0x73 0x60 0xb7 0xd5 0x02 0xd? 0x2c 0xfb 0x99 0x4e 0x5d 0x8a 0xe8 0x3f 0xce 0x19 0x7b 0xac 0xbf 0x68 0x0a 0xdd 0xe? 0x56 0x81 0xe3 0x34 0x27 0xf0 0x92 0x45 0xb4 0x63 0x01 0xd6 0xc5 0x12 0x70 0xa7 0xf? 0x89 0x5e 0x3c 0xeb 0xf8 0x2f 0x4d 0x9a 0x6b 0xbc 0xde 0x09 0x1a 0xcd 0xaf 0x78 |
c66100fd3b052c710393f385ef3d4084 | 104 053-2 | 7.6 TEA7 - Definition of the Combining Function f | Table 6 defines the combining function f, which is used as defined in clause 7.3. Different rows correspond to different values of the most significant 4 bits of the input, and columns to the least significant 4 bits. For example, the value corresponding to 0x12 is found in the row labelled 0x1? and column labelled 0x?2, and is the byte value 0xcf. ETSI ETSI TS 104 053-2 V1.2.1 (2025-02) 19 Table 6 0x?0 0x?1 0x?2 0x?3 0x?4 0x?5 0x?6 0x?7 0x?8 0x?9 0x?a 0x?b 0x?c 0x?d 0x?e 0x?f 0x0? 0xe8 0xf8 0xc0 0x7a 0x44 0x07 0x2b 0x9e 0x54 0x7e 0x64 0x67 0xd5 0x8a 0x38 0x04 0x1? 0x10 0xde 0xcf 0x71 0x42 0x2e 0xfd 0x95 0xe0 0x8b 0xa1 0xaf 0xb8 0x80 0x5f 0x19 0x2? 0x1e 0xf7 0x15 0x03 0xad 0x0c 0x29 0xc7 0x5b 0x8f 0x46 0xa7 0xb9 0x82 0x3d 0x1d 0x3? 0xef 0xd0 0x93 0x0e 0xa0 0x79 0xf9 0xca 0x51 0x7b 0x6b 0x6f 0xd1 0x3f 0x58 0xb2 0x4? 0x18 0xd3 0x9c 0x0d 0x9f 0x05 0xfc 0xc1 0xe4 0x8d 0x4a 0x60 0xb5 0x81 0x5e 0x1f 0x5? 0xe5 0xd9 0xc3 0x70 0x4e 0x22 0x24 0x9a 0xed 0x7d 0x68 0xf2 0xba 0x3a 0x5a 0x1c 0x6? 0xeb 0xf1 0x97 0x76 0x48 0x27 0xf4 0xcd 0x6c 0x7c 0x4b 0x65 0xdc 0x8c 0x53 0x17 0x7? 0xe3 0xfb 0x99 0x00 0x41 0x2c 0xf3 0x3b 0xe9 0x74 0x40 0xa5 0xd4 0x86 0x36 0xbb 0x8? 0x1b 0xea 0x91 0x0b 0xa3 0x26 0xff 0xc8 0xe6 0x89 0x62 0x63 0xbf 0x8e 0x32 0xb0 0x9? 0xee 0xd8 0x98 0x75 0xa8 0x28 0xfa 0xc4 0x55 0x72 0x4f 0xae 0x57 0x39 0x50 0xbc 0xa? 0xe1 0xf5 0xcb 0x7f 0x45 0x0a 0xf6 0x96 0x52 0x87 0x49 0x6a 0xdb 0x3e 0x20 0x14 0xb? 0x11 0xd2 0xc2 0x01 0xa4 0x0f 0x25 0x9b 0x5c 0x43 0x66 0x6e 0xb4 0x30 0x56 0xbe 0xc? 0xce 0xfe 0xcc 0x09 0xa6 0x2f 0x23 0x94 0x5d 0x84 0x47 0xac 0xda 0x3c 0x31 0xb7 0xd? 0x16 0xd7 0xc5 0x73 0xaa 0x02 0xb6 0x90 0xec 0x77 0x69 0x61 0xb1 0x33 0x34 0xb3 0xe? 0x12 0xd6 0xc9 0x08 0xab 0x06 0x2d 0x92 0xe2 0x83 0x6d 0xa2 0xbd 0xdd 0x37 0x1a 0xf? 0xe7 0xf0 0x9d 0x88 0x4d 0x21 0x2a 0xc6 0x59 0x78 0x4c 0xa9 0xdf 0x85 0x35 0x13 ETSI ETSI TS 104 053-2 V1.2.1 (2025-02) 20 Annex A (informative): Bibliography Barreto, P. and Rijmen, V. (2002): "Rijndael reference code in ANSI C", v2.2. ETSI TS 101 053-5: "Rules for the management of the TETRA standard encryption algorithms; Part 5: TEA5". ETSI TS 101 053-6: "Rules for the management of the TETRA standard encryption algorithms; Part 6: TEA6". ETSI TS 101 053-7: "Rules for the management of the TETRA standard encryption algorithms; Part 7: TEA7". ETSI ETSI TS 104 053-2 V1.2.1 (2025-02) 21 History Document history V1.1.1 July 2024 Publication V1.2.1 February 2025 Publication |
8431d4af277734b76ed585d18d1f2707 | 105 174-7-1 | 1 Scope | The present document details measures which may be taken to ease the deployment of smart new services and their multiservice street furnitures of digital multiservice city within the IP network of a single city or an association of cities administratively clustered. Furthermore, the suggested measures will enable to engineer a reliable common networking infrastructure which can improve the Total Cost of Ownership (TCO) for the public administration while improving the energy efficiency of the overall deployment. The present document also lists the requirements which have led to this common architecture. Clause 4 identifies and presents a general overview of a city from small entity to significantly large municipality clustering several cities and villages. Clause 5 presents the pursued objectives behind the concept of smart city. Clause 6 describes the general theoretical pillars which bears the engineering requirements to deploy a digital multi service city. Clause 7 identifies the general needs from the cities. Clause 8 of the present document present a suggestion of an engineered digital multiservice city. This will enable the proper introduction and implementation of a new service, application or content within the city digital portfolio on a unified energy efficient network, though it is not the goal of the present document to provide detailed standardized solutions for network architecture. |
8431d4af277734b76ed585d18d1f2707 | 105 174-7-1 | 2 References | |
8431d4af277734b76ed585d18d1f2707 | 105 174-7-1 | 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 at https://docbox.etsi.org/Reference. 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] CENELEC EN 50173-2: "Information technology - Generic cabling systems - Part 2: Office premises". [2] CENELEC EN 50173-4: "Information technology - Generic cabling systems - Part 4: Homes". [3] CENELEC EN 50174-1: "Information technology - Cabling installation - Part 1: Installation specification and quality assurance". [4] CENELEC EN 50174-2: "Information technology - Cabling installation - Part 2: Installation planning and practices inside buildings". [5] CENELEC EN 50174-3: "Information technology - Cabling installation - Part 3: Installation planning and practices outside buildings". ETSI ETSI TS 105 174-7-1 V1.1.1 (2017-06) 8 |
8431d4af277734b76ed585d18d1f2707 | 105 174-7-1 | 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 are not necessary for the application of the present document but they assist the user with regard to a particular subject area. [i.1] ETSI TS 105 174-1: "Access, Terminals, Transmission and Multiplexing (ATTM); Broadband Deployment and Energy Management; Part 1: Overview, common and generic aspects". [i.2] ETSI TR 105 174-4: "Access, Terminals, Transmission and Multiplexing (ATTM); Broadband Deployment - Energy Efficiency and Key Performance Indicators; Part 4: Access networks". [i.3] ETSI TS 105 174-4-1: "Access, Terminals, Transmission and Multiplexing (ATTM); Broadband Deployment and Energy Management; Part 4: Access Networks; Sub-part 1: Fixed access networks (excluding cable)". [i.4] ETSI TS 105 174-5-1: "Access, Terminals, Transmission and Multiplexing (ATTM); Broadband Deployment and Energy Management; Part 5: Customer network infrastructures; Sub-part 1: Homes (single-tenant)". [i.5] ETSI TS 105 174-5-2: "Access, Terminals, Transmission and Multiplexing (ATTM); Broadband Deployment and Energy Management; Part 5: Customer network infrastructures; Sub-part 2: Office premises (single-tenant)". [i.6] ETSI TS 105 174-5-4: "Access, Terminals, Transmission and Multiplexing (ATTM); Broadband Deployment - Energy Efficiency and Key Performance Indicators; Part 5: Customer network infrastructures; Sub-part 4: Data centres (customer)". [i.7] ETSI TR 105 174-2-1: "Access, Terminals, Transmission and Multiplexing (ATTM); Broadband Deployment - Energy Efficiency and Key Performance Indicators; Part 2: Network sites; Sub-part 1: Operator sites". [i.8] ETSI TS 102 973: "Access Terminals, Transmission and Multiplexing (ATTM); Network Termination (NT) in Next Generation Network architectures". [i.9] ETSI TR 103 290: " Machine-to-Machine communications (M2M); Impact of Smart City Activity on IoT Environment (Impact of Smart City activity on IoT Environment)". [i.10] ETSI TR 102 898: "Machine to Machine communications (M2M); Use cases of Automotive Applications in M2M capable networks". [i.11] ETSI TR 102 935: "Machine-to-Machine communications (M2M); Applicability of M2M architecture to Smart Grid Networks; Impact of Smart Grids on M2M platform". [i.12] ETSI TR 102 857: "Machine-to-Machine communications (M2M); Use Cases of M2M applications for Connected Consumer". [i.13] ETSI TR 103 375: "SmartM2M IoT Standards landscape and future evolutions". [i.14] AIOTI Recommendations for future collaborative work in the context of the Internet of Things Focus Area in Horizon 2020. NOTE: Available at https://ec.europa.eu/digital-single-market/en/news/aioti-recommendations-future- collaborative-work-context-internet-things-focus-area-horizon-2020. [i.15] Wikipedia definition of street furniture's. NOTE: Available at https://en.wikipedia.org/wiki/Street_furniture. ETSI ETSI TS 105 174-7-1 V1.1.1 (2017-06) 9 [i.16] European Innovation Partnership on Smart Cities and Communities "Operational Implementation Plan". NOTE: Available at http://ec.europa.eu/eip/smartcities/files/operational-implementation-plan-oip-v2_en.pdf. [i.17] European Innovation Partnership on Smart Cities and Communities "Strategic Implementation Plan". NOTE: Available at http://ec.europa.eu/eip/smartcities/files/sip_final_en.pdf. [i.18] European Innovation Partnership on Smart Cities and Communities "Humble Lamppost". NOTE: Available at https://eu-smartcities.eu/commitment/6670. [i.19] ETSI GS OEU 009: "Operational energy Efficiency for Users (OEU); Global KPI Modelling for Green Smart Cities". [i.20] ETSI GS OEU 019: "OEU KPIs for Smart Cities". [i.21] Light Fidelity TED Talk "Wireless data from every light bulb". NOTE: Available at http://www.ted.com/talks/harald_haas_wireless_data_from_every_light_bulb. [i.22] IEEE 802.11TM: "Wireless LAN; 802.11-2012 -- IEEE Standard for Information technology -- Telecommunications and information exchange between systems Local and metropolitan area networks--Specific requirements -- Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications". [i.23] IEEE 802.11sTM: "Wireless Mesh Networking; 802.11s-2011 -- IEEE Standard for Information Technology -- Telecommunications and information exchange between systems--Local and metropolitan area networks--Specific requirements -- Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) specifications Amendment 10: Mesh Networking". [i.24] VLC Visible Light Communications IEEE 802.15. [i.25] IEEE 802.15.4TM: "IEEE Standard for Information technology - Telecommunications and information exchange between systems - Local and metropolitan area networks - Specific requirements - Part 15.4: Wireless Medium Access Control (MAC) and Physical Layer (PHY) Specifications for Low Rate Wireless Personal Area Networks (WPANs)". [i.26] IEEE 802.11ahTM: "WiFi HaLow; P802.11ah -- IEEE Draft Standard for Information Technology - - Telecommunications and Information Exchange Between Systems-Local and Metropolitan Area Networks-Specific Requirements -- Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications: Amendment 2: Sub 1 GHz License Exempt Operation". [i.27] IETF RFC 3031: "Multiprotocol Label Switching Architecture". [i.28] IETF RFC 4761: "Virtual Private LAN Service Using Label Distribution Protocol (LDP) Signaling". [i.29] IETF RFC 4762: "Virtual Private LAN Service Using BGP for Auto-Discovery and Signaling". [i.30] IEEE 802.3TM: "Ethernet". [i.31] IEEE 802.3azTM: "Energy Efficient Ethernet; IEEE 802.3az-2010 -- IEEE Standard for Information technology -- Local and metropolitan area networks -- Specific requirements -- Part 3: CSMA/CD Access Method and Physical Layer Specifications -- Amendment 5: Media Access Control Parameters, Physical Layers, and Management Parameters for Energy-Efficient Ethernet". [i.32] IEEE 802.3abTM: "Ethernet over Twisted Pair at 1 Gbit/s; 802.3ab-1999 -- IEEE Standard for Information Technology -- Telecommunications and information exchange between systems -- Local and Metropolitan Area Networks -- Part 3: Carrier Sense Multiple Access with Collision Detection (CSMA/CD) Access Method and Physical Layer Specifications -- Physical Layer Parameters and Specifications for 1000 Mb/s Operation over 4 pair of Category 5 Balanced Copper Cabling, Type 1000BASE-T". ETSI ETSI TS 105 174-7-1 V1.1.1 (2017-06) 10 [i.33] IEEE 802.3uTM: "Fast Ethernet over Twisted Pair; 802.3u-1995 -- IEEE Standards for Local and Metropolitan Area Networks-Supplement -- Media Access Control (MAC) Parameters, Physical Layer, Medium Attachment Units and Repeater for 100Mb/s Operation, Type 100BASE-T (Clauses 21-30)". [i.34] IEEE 802.3zTM: "Ethernet over Fiber Optic at 1 Gbit/s; 802.3z-1998 -- Media Access Control Parameters, Physical Layers, Repeater and Management Parameters for 1,000 Mb/s Operation, Supplement to Information Technology -- Local and Metropolitan Area Networks -- Part 3: Carrier Sense Multiple Access with Collision Detection (CSMA/CD) Access Method and Physical Layer Specifications". [i.35] IEEE 802.3afTM: "Power Over Ethernet; 802.3af-2003 -- IEEEE Standard for Information Technology - Telecommunications and Information Exchange Between Systems -- Local and Metropolitan Area Networks - Specific Requirements -- Part 3: Carrier Sense Multiple Access with Collision Detection (CSMA/CD) Access Method and Physical Layer Specifications -- Data Terminal Equipment (DTE) Power Via Media Dependent Interface (MDI)". [i.36] IEEE 802.3atTM: "Power Over Ethernet; 802.3at-2009 -- IEEE Standard for Information technology -- Local and metropolitan area networks -- Specific requirements -- Part 3: CSMA/CD Access Method and Physical Layer Specifications -- Amendment 3: Data Terminal Equipment (DTE) Power via the Media Dependent Interface (MDI) Enhancements". [i.37] IEEE 802.1qTM: "Ethernet Virtual LAN ; 802.1q-2014 - IEEE Standard for Local and metropolitan area networks--Bridges and Bridged Networks". [i.38] Market Place of the European Innovation Partnership on Smart Cities and Communities. NOTE: Available at http://eu-smartcities.eu. [i.39] Guide Pratique - Deploiement de la Boucle Locale Optique Mutualisee sur support aerien. NOTE: Available at http://www.fieec.fr/iso_album/20151126085028_121115_guide_pratique_blom_basse_def.pdf. [i.40] IETF RFC 1034: "Domain Names - Concepts and Facilities". [i.41] IETF RFC 1035: "Domain Names - Implementation and Specification". [i.42] UEFI Forum ACPI specification. NOTE: Available at http://www.uefi.org/specifications. [i.43] IETF RFC 2474: "Definition of the Differentiated Services Field (DS Field) in the IPv4 and IPv6 Headers". [i.44] IETF RFC 2475: "An Architecture for Differentiated Services". [i.45] European Innovation Partnership on Smart Cities and Communities "s[m2]art". NOTE: Available at https://eu-smartcities.eu/commitment/7434. [i.46] Recommendation ITU-T G.9959: "Short range narrow-band digital radiocommunication transceivers - PHY, MAC, SAR and LLC layer specifications". [i.47] IEEE 802.1pTM: "Traffic Class Expediting and Dynamic Multicast Filtering; 802.1D-2004 - IEEE Standard for Local and metropolitan area networks: Media Access Control (MAC) Bridges". [i.48] IEEE 802.11eTM: "Wireless Multi Media; 802.11e-2005 -- IEEE Standard for Information technology -- Local and metropolitan area networks -- Specific requirements -- Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications -- Amendment 8: Medium Access Control (MAC) Quality of Service Enhancements". ETSI ETSI TS 105 174-7-1 V1.1.1 (2017-06) 11 [i.49] IEEE 802.11adTM: "WiFi WiGig; 802.11ad-2012 -- IEEE Standard for Information technology -- Telecommunications and information exchange between systems--Local and metropolitan area networks--Specific requirements -- Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications -- Amendment 3: Enhancements for Very High Throughput in the 60 GHz Band". [i.50] IEEE 802.11acTM: "WiFi ac ; 802.11ac-2013 - IEEE Standard for Information technology -- Telecommunications and information exchange between systems -- Local and metropolitan area networks -- Specific requirements -- Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications -- Amendment 4: Enhancements for Very High Throughput for Operation in Bands below 6 GHz". [i.51] IEEE 802.3bvTM: "Gigabit Ethernet Over Plastic Optical Fiber ; P802.3bv - IEEE Draft Standard for Ethernet Amendment: Physical Layer Specifications and Management Parameters for 1000 Mb/s Operation Over Plastic Optical Fiber". [i.52] 3GPP: http://www.3gpp.org/specifications/specifications. [i.53] Recommendation ITU-T Y.4900: "Overview of key performance indicators in smart sustainable cities". [i.54] Recommendation ITU-T Y.4901: "Key performance indicators related to the use of information and communication technology in smart sustainable cities". [i.55] Recommendation ITU-T Y.4902: "Key performance indicators related to the sustainability impacts of information and communication technology in smart sustainable cities". [i.56] Recommendation ITU-T Y.4903: "Key performance indicators for smart sustainable cities to assess the achievement of sustainable development goals" [i.57] ISO 37120:2014: "Sustainable development of communities -- Indicators for city services and quality of life". [i.58] Recommendation ITU-T SG5: "Environment, climate change and circular economy". [i.59] ISO/TC 268: "Sustainable cities and communities". |
8431d4af277734b76ed585d18d1f2707 | 105 174-7-1 | 3 Definitions and abbreviations | |
8431d4af277734b76ed585d18d1f2707 | 105 174-7-1 | 3.1 Definitions | For the purposes of the present document, the terms and definitions and the following apply: digital multiservice cities: cities using digital infrastructure which consist of a single unified high speed networking infrastructure that allows the ICT systems of the complete city services departments to interconnect seamlessly and securely to each other street furniture: collective term for objects and pieces of equipment installed on city streets, city roads, and public areas under responsibility of the city for various purposes NOTE: These objects and equipments belong to the wider terminology of the urban assets as named by cities. urban asset: collective term to qualify the physical assets which belong to a city and which are located across its territory, in streets, roads, public parks and associated urban constructions ETSI ETSI TS 105 174-7-1 V1.1.1 (2017-06) 12 |
8431d4af277734b76ed585d18d1f2707 | 105 174-7-1 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: ACPI Advance Configuration and Power Interface AIOTI Alliance for the Internet of Things Innovation and in particular AIOTI WG3 on IoT Standardization AP Access Point API Application Programming Interface ATTM Access, Terminals, Transmission and Multiplexing BTS Base Transceiver Station CCTV Closed-circuit TeleVision DNS Domain Name Service EIP European Innovation Partnership EIP-SCC European Innovation Partnership on Smart Cities and Communities EM Electromagnetic Communication ENTI External Network Test Interface FIEEC Federation des Industries Electriques, Electroniques et de Communication Gbit/s Giga bits per second GOF Glass Optical Fiber GPS Global Positioning System GS Group Specification HMI Human Machine Interface ICT Information and Communication Technology IEC International Electrotechnical Commission IEEE Institute for Electrical and Electronics Engineers IETF Internet Engineering Task Force IIC Industrial Internet Consortium IMT International Mobile Telecommunications IoT Internet of Things IP Internet Protocol ISDN Integrated Services Digital Network ISG Industrial Specification Group ISM Industrial, Scientific, and Medical ISO International Organization for Standardization ISP Internet Service Provider IT Information Technology ITS Intelligent Transportation Systems ITU International Telecommunication Union JTC Joint Technical Committee Kbit/s Kilo bits per second KPI Key Performance Indicator LAN Local Area Network LP-LAN Low-Power Local-Area Network LP-WAN Low-Power Wide-Area Network LR-WPAN Low-Rate Wireless Personal Area Networks LSP Label Switch Path M2M Machine to Machine MAC Media Access Control MAN Metropolitan Area Network MPLS Multiprotocol Label Switching NFC Near Field Communication NGN Next Generation Network NT Network Termination OASIS Organization for the Advancement of Structured Information Standards OCF Open Connectivity Foundation OCF Open Connectivity Foundation OEU Operational energy Efficiency for Users oneM2M Partnership Project oneM2M launched by a number of SSOs including ETSI ONVIF Open Network Video Interface Forum OS Operating System ETSI ETSI TS 105 174-7-1 V1.1.1 (2017-06) 13 PoE Power over Ethernet POF Plastic Optical Fiber PSIA Physical Security Interoperability Alliance PSTN Public Switched Telephone Network QoS Quality of Services RF Radio Frequency RFC Request For Comments SLA Service Level Agreement SME Small and Medium Enterprise SOHO Small Hoffice Home Office SP Service Provider SSID Service Set IDentifiers STF Special Task Force TC Technical Committe TCO Total Cost of Ownership TR Technical Report TxRx Transceiver equipment UEFI Unified Extensible Firmware Interface UHD Ultra High Definition UTP Universal Twister Pair VLAN Virtual Local Area Network VLC Visible Light Communications VPLS Virtual Private LAN Service W3C World Wide Web Consortium WAN Wide Area Network Wi-Fi Wireless Fidelity WiGig Wireless Gigabit WLAN Wireless LAN WMM Wi-Fi Multimedia WSN Wireless Sensor Network |
8431d4af277734b76ed585d18d1f2707 | 105 174-7-1 | 4 General overview of a city | 4.1 Reaching sustainability thru digital multiservice city networks Municipality facilities range from a single premise to multiple buildings located across the city territory. Single premise municipality come from the origin of this administrative facility: "the city house" were the mayor was living and were all government administrative duties were performed. Thru the centuries, the mayor has been supported by more and more complementary staff creating by purposes respective services departments. Along this employment grow, city properties availabilities or acquisitions, services offices started to span either across several physical building facilities within the city area either across larger geographical area when the administrative entity span on multiple contiguous cities or villages. Municipalities nowadays have also undertaken several other responsibilities such as safety, education, waste management and recycling, healthcare, water and electricity distribution, public transportation and potentially many more. Most of today municipalities are supported by Information and Communications Technologies to help the city staff to perform the daily work, communicate with each other and with the higher authorities. In that concern, municipalities operations should be considered as an enterprise ranging from a Small Office Home Office (SOHO), a Small and Medium Enterprise (SME) up to large enterprise. According to the respective type of enterprise the city can be matched to, technical recommendations which applies to homes and offices ICT deployments such as ETSI TS 105 174-5-1 [i.4], ETSI TS 105 174-5-2 [i.5] and ETSI TS 105 174-5-4 [i.6] or to telecommunication services providers such as ETSI TR 105 174-2-1 [i.7] should be considered to improve the energy management of the city ICT deployment. Indeed, from a networking perspective municipalities have various challenges to face to. ETSI ETSI TS 105 174-7-1 V1.1.1 (2017-06) 14 |
8431d4af277734b76ed585d18d1f2707 | 105 174-7-1 | 4.2 Inside-building connectivity cabling infrastructure | Regularly the buildings which host the municipal staff are not contemporary and have not been designed with IT in mind. Furthermore, in important cities, those buildings are often classified heritage buildings and construction works are heavily constrained. The result is that network cabling is regularly of a concern. It is common to see physical deployments where rooms are not correctly equipped with appropriate network access socket, that network cables are inappropriately installed, that technical facilities such as cable patch panel are imperfectly installed or simply missing, etc. Finally, poor cross- domains vision leads often to the installation of several independent physical network cabling setups such as: • Network cablings for analog/digital telephony services. • Network cablings for emergency (e.g. alarms, elevators) services. • Network cabling for IT data networking service. • Network cabling for IP telephony service. • Network cabling for analog/digital video surveillance service. • Network cabling for IP video surveillance service. There is a clear need to unify these ICT independents infrastructures thru a common multi-services physical engineering architecture. Requirements, specifications and best practices for the deployment of these physical cabling infrastructures are covered by various norms such as CENELEC EN 50173-2 [1], CENELEC EN 50173-4 [2], CENELEC EN 50174-1 [3] and CENELEC EN 50174-2 [4]. |
8431d4af277734b76ed585d18d1f2707 | 105 174-7-1 | 4.3 Inter-buildings connectivity cabling infrastructure | Nowadays, in many cases municipalities facilities are spread across many buildings which may or may not be near to each other's. Besides the constrain of classified heritage buildings, distances between facilities may be large. With that regards and according to the capabilities, municipalities either opt to deploy their own inter-building cablings either opt for contracting external service provider(s). Similarly to the local cabling, poor cross-domains vision regularly leads to the installation of several independent physical network cabling setups or to establish multiple service contracts with service providers. There is a clear need to improve the engineering architecture which interconnects the various facilities spread across the territory. Requirements, specifications and best practices for the deployment of these physical cabling infrastructures are covered by various norms such as CENELEC EN 50174-1 [3] and CENELEC EN 50174-3 [5]. |
8431d4af277734b76ed585d18d1f2707 | 105 174-7-1 | 4.4 Digital services availability | IP networking technology leverage numerous IT services such as data transfer, digital telephony, video surveillance, IoT operation and monitoring, etc. IT staff availability within the municipality shall be taking into account and due to financial constrains regularly missing (Small cities, villages) or outsourced to external services provider. The consequence is that there is limited or missing engineering view on the deployment of the digital services. It is a common situation where the IP data network is unfortunately fragmented into multiple independent IP networks isolated from each other and even requiring to pass thru externals service providers for internal communications. By example, when migrating from analog/digital telephony or video security to IP telephony or video security, lack of technical engineering and poor global networking views often lead to mirror traditional POTS (Plain Old Telephone Service) or situation. Municipalities often deploy independent and isolated IP networks per service and per site (even per building) whereas technically engineered design would suggest to architecture the deployment as a single unified IP voice or video platform leveraging a multi service network spanning across the building facilities. ETSI ETSI TS 105 174-7-1 V1.1.1 (2017-06) 15 The engineering of a multi-services network would also open the way to innovative IT solution such as voice and video convergences while also enabling communication between such as: • physical IP phones and softphone running on municipal employee's computer: • access to IP camera video streams from authorized computer within the network. |
8431d4af277734b76ed585d18d1f2707 | 105 174-7-1 | 4.5 Network access coherence | Local or inter-buildings physical networking connectivity has constrained the municipal authorities to fragment their local IP networks into isolated networking areas. Access to the Internet, or specific national network resources, with such engineering implies to install a dedicated physical connection to a network service provider (e.g. ISP) within each local network. Unfortunately, it is also common to have cities where Internet connections are even physically linked to single agent computers therefore removing the capability to share the service provider access with the agent department. The engineering of a multi-services network would also improve the accessibility to the Internet as well as to other specific external services (e.g. national citizen or enterprises registries) such as those provided by higher authorities of the government. |
8431d4af277734b76ed585d18d1f2707 | 105 174-7-1 | 5 General considerations about digital multiservice city | Renowned technology organizations such as the ITU-T describes the concept of the sustainable city with following terms: "A smart sustainable city is an innovative city that uses ICT and other means to improve quality of life, efficiency of urban operation and services, and competitiveness, while ensuring that it meets the needs of present and future generations with respect to economic, social and environmental aspects." This definition has been developed based on the work carried out by FG-SSC and UNECE in Recommendation ITU-T SG5 [i.58]. The point of view of internationally recognized analysts share a strong position that technology organizations emphasis: the importance of a transversal approach across the various services which build the organization of a city: "A smart city is based on intelligent exchanges of information that flow between its many different subsystems. This flow of information is analysed and translated into citizen and enterprises services. The city will act on this information flow to make its wider ecosystem more resource-efficient and sustainable. The information exchange is based on a smart governance operating framework designed for cities sustainable." (Gartner, 2011) An increasing number of everyday machines and objects are now embedded with sensors or actuators and have the ability to communicate over the Internet. Collectively they make up the Internet of Things (IoT). With the development of the IoT, more and more of the information systems present in the city are now offered technologies which enable real-time data harvesting and almost real-time data processing and sharing. Within the ETSI, the SmartM2M Technical Committee (TC) is focusing on the specifications and requirements to enable end to end interoperability between Machine-to-Machine (M2M) communications. The scope of the following documents covers topics such as smart grids, connected car, home automation and smart cities. The working program includes: • to develop and maintain an end-to-end overall telecommunication high level architecture for M2M; • to identify gaps where existing standards and provide specifications to fill these gaps. TC SmartM2M has initiated several development of standards for communication between Smart Appliances. The standards are based upon ETSI's functional architecture for Machine to Machine communications, and includes a common data model and the identification of communication protocols for several use cases such as transport, water management, building management, culture & tourism, described in ETSI TR 103 290 [i.9], ETSI TR 102 898 [i.10], ETSI TR 102 935 [i.11] and ETSI TR 102 857 [i.12]. ETSI ETSI TS 105 174-7-1 V1.1.1 (2017-06) 16 To be sustainable in servicing or introducing new digital services, the city needs to have an ICT infrastructure which enable seamless end to end communications at the lowest possible cost of installation, energy consumption and operation. By enabling a common infrastructure, structural expenses can be shared amongst the variety of services that the ICT of a digital city has to cover. |
8431d4af277734b76ed585d18d1f2707 | 105 174-7-1 | 6 Theoretical pillars for a digital multiservice city | |
8431d4af277734b76ed585d18d1f2707 | 105 174-7-1 | 6.1 Convergence path | From villages to megacities, across urban cities, all of these living places can be qualified by some 'smart' attributes within the different delivered services: energy (electricity, gas) delivery, water management (distribution, recycling), waste (organic, plastic, generic) management, transportation (bus, metro, train), education, healthcare, public security and mobility (road, traffic light). The daily operations of the administration, which could be considered as the enterprise behind the scene, are also areas were smart process and smart management, smart building, etc. could be realized. It is now clear that with the maturity of various ICT technologies, most of these public order services could benefit of the data era to improve their efficiency, sustainability and increase the level of quality for the resident citizen, the municipal workforces or the enterprises commuters. From data collection (e.g. consumption metering, traffic flow, air/water quality monitoring) to data analytics, all the process may benefit of the road to the sustainable city qualification. Nevertheless, before any specific ICT terminology this road has to be first defined in terms of functional aims which are presented in figure 1. ETSI ETSI TS 105 174-7-1 V1.1.1 (2017-06) 17 Figure 1: Functional aims of a digital multiservice city |
8431d4af277734b76ed585d18d1f2707 | 105 174-7-1 | 6.2 Cross domain | The municipal services provided to residents, in return of their local taxes, depends on numerous factors: size of the territory, amount of inhabitants, history, geographical location, etc. Basis services expected by the city authorities ranges from water delivery, sanitation sewer, sanitation refuse & waste, street/parking/public transport (bus, metro, etc.) and lighting for mobility, schools and public libraries for education, police and fire departments for security, hospitals and ambulances for healthcare, etc. Since ages, these services have been the concern of several different municipal employees who often belong to separated and independent departments. This underlying administrative structure, bigger the city is bigger is the gap, has leaded the cities to adopt an operational model which inducts the silos mentality. Silos Mentality is a mindset present when certain departments or sectors are unable or do not wish to share information with others in the same organization. Such low working relationships and lack of cooperation have also impacted the way ICT technologies have been introduced into the operational engine of the cities. In most cases IT applications have been designed and developed to answer specific services needs independently from each other. It is also likewise that these applications evolve independently of each other. Consequences of such behavior reduce the efficiency in the overall operation but also do not contribute to improvement of the productivity. ETSI ETSI TS 105 174-7-1 V1.1.1 (2017-06) 18 The presence of these silos has numerous impacts such as: • information fragmentation: - in the presence of different and non-interworking applications and systems, the data tends to remain isolated whereas specific exchanges cross domains would be beneficial. For example, crossing real-time household data on water consumption with the water pumping station operational network would probably reduce the leakage in delivery in some under provisioned areas at critical moments of the day. • inability to think of the economy of scale: - existing silo-based model leads to multiple procurements for similar infrastructures or applications. For example, installing outdoor IEEE 802.11 [i.22] WLAN (Wi-Fi) networks for public Internet access, deploying another for the video security purposes while also setting up separated backbone networks would imply both costs increases in procurements, management and support but also constrains on technical aspects such as radio frequency interferences, physical assets limitations and urbanistic headaches. • lack of uniform technical specifications: - independent applications or network infrastructures design, non-coordinated procurements result in heterogeneous technological platforms, which are more difficult and costly to manage, maintain and evolve. For example, area-wide villages or municipalities have often their employees and workers spread across several building situated in different locations. The local IT networking infrastructures are commonly independent from each other leading regularly to situation were both network cannot talk to each other and most probably have their standalone Internet access. Such an unplanned situation would seriously impact the setup and Total Cost of Ownership of an IP telephony platform. It is therefore clear that cross domain thinking shall be applied when possible. The various levels were this specific exercise should be realized are: • services business logics on both functional and operational levels; • network (wired & wireless) architecture on both Local Area Network, Metropolitan Area Network and Wide Area Network; • applications data structure, semantic and correspondences; • data access methods; • applications software architecture. By embracing cross domain mentality versus silos mentality, serious operational improvements could be achieved thus strengthening the adoption of the smart city. As an example, real time crossing data of city parking availabilities, city traffic status, and street traffic lights might enable both free parking locations suggestion to driver while making traffic more fluid thru the avoidance of congestion areas where many drivers will converge. Furthermore, this fluidity in the traffic could be reflected by influencing the traffic light in a positive manner. |
8431d4af277734b76ed585d18d1f2707 | 105 174-7-1 | 6.3 Data Culture & Open Data governance | For ages, municipalities have been servicing public interests and citizen needs generating numerous information of different kinds not shared with any party outside the city. Even in the presence of ICT technologies, these data have been locked within the specific business applications in which there are processed. One key feature of digital multiservice city is the adoption of the cross domain approach. When ICT technologies are designed with this mentality many innovations may emerge. To remain competitive and achieve sustainable growth, cities shall embrace the Data Culture philosophy. By changing the way government officials look at and use data we can enable the ICT ecosystem to be creative and this out of the box. Indeed, rather than limiting the usage of specific set of data within a city department to its specific business processing, sharing this set with other departments but also with third party outside the city sphere could benefit to the overall community. ETSI ETSI TS 105 174-7-1 V1.1.1 (2017-06) 19 For example, it is the water department which usually manages the fire hydrants locations as they belong to the water infrastructure city assets. However, the primary beneficiaries of this locations data set are entities like the fire department and the public safety. The water department has traditionally the responsibility for disseminating this information to those that need it. By embracing the Data Culture, instead of keeping these locations records and the associated operational status (operational valve, water flow, water pressure, etc.) closed and communicating these once a while, sharing dynamically theses precious data with the outside could be of a great benefit and even can save lives. Opening Data outside the traditional scope of single or multiple city departments often faces technological of political barriers. Indeed, many city data are decades old, and extracting information to release as Open Data can be time consuming and difficult. Furthermore, some fear that releasing information could be used by outside parties to evaluate their performances. Open Data does not mean providing access to anyone or in any way. When adopting this practice, data governance should be associated. Indeed, data should be structured in understandable formats, with defined semantics, open access should be presented according to their respective scope and usages should be logged. Furthermore, Open Data does not mean Free Data. Data Culture of a municipality is therefore also the ability to both operate as a free public service but also as an enterprise minded organization. |
8431d4af277734b76ed585d18d1f2707 | 105 174-7-1 | 6.4 Availability, Interoperability, Scalability and Resilience | When it comes to IT, there are important inequalities between the cities. According to the size of the area, the number of inhabitants, the variability in the publicly provided services, the specificities (industrial, vacation, port, university, etc.) or the status (village, capital, etc.), the obligations and the finances (thru regional/governmental subsidy or local taxes) are different. These differences have an impact on the level of use of IT and therefore on the service level and service quality which could be achieved thru the digital infrastructure within reasonable limits. Nevertheless, whatever city, critical services shall be treated with the same importance. ICT infrastructures and applications related to the critical domains (e.g. police, fire department, alerting system) shall be seriously analysed and associated with particular service levels such as: • availability; • interoperability; • scalability; • resilience. Beside critical conditions were all these service levels shall be simultaneously associated, independent concerns should be applied in ICT fields such as to: • avoid vendor lock-in and proprietary technologies; • enable common information and meta-data semantic across vertical domains; • enable open data interfaces/API between applications; • enable infrastructures/platforms monitoring and proactive supervision. By introducing these service level requirements, it is possible to embrace the concept of a digital multiservice city. As an illustration there are numerous city departments which may have valuable information serviceable to address the question of the unoccupied dwellings: • the revenue department view the notion of vacant property thru their records which keep track of those that do pay property taxes and those that do not; • the water and electricity departments view the notion of vacant property thru their records which keep track of those that have an active account and effective consumption and those that do not; • the sanitation refuse and waste department view the notion of vacant property thru their records which keep track of the collection passages and the weight of waste collected. ETSI ETSI TS 105 174-7-1 V1.1.1 (2017-06) 20 As there is not a department in charge of keeping track of vacant properties, there is not an appropriate view on this question. Several departments have some data on the problem of vacancy, but their interpretation of the question is approached through the lens of the service they deliver. However, if these data sets are made available, in a digital and interoperable format, crossing them would give a better view and help to reduce the vacancy rate. This will be of added value for the citizen (vacant properties negatively impact housing values), the real estate business (increase value proposition), the city (population grow) and even the police (vacant units are more likely to be vandalized or squatted). |
8431d4af277734b76ed585d18d1f2707 | 105 174-7-1 | 6.5 Digital Equity | In the road to digital, cities are taking important decisions which impact the operation and delivery of their public services. From data scanning to e-Government, gradually the delivery model is modernized with digital assets and offering. While Municipal Service Counters are complemented with digital counterpart, some are simply replaced by their digital counterpart. Digital Service Counters are of a great benefit to the population or the businesses/commerce. Residents who have mobility issues, poor health, the elderly and those living in geographically remote areas can take advantage of this delivery method. Local trader is no longer forced to close shop to get to the administration offices neither business employee to take break during work. Digital services provide also facilities for the administration to communicate with the population, alerting systems are in the first line for such improvement. To illustrate these, it can be mentioned: • alerting the inhabitant of a specific geographical zone in case of water contamination, fire and air pollution; • notifying the inhabitants of a neighbourhood before the waste truck round; • soliciting the citizen for the electoral duty; • invoicing the inhabitant for the various city taxes; • etc. Public libraries, municipal schools, social services. It seems obvious that these multi service facilities are permitted through the Internet. However, even if every day the penetration of the broadband access in increasing, there is still a large percentage of the population without Internet access or who do not have access at all. Literature refers this inequality as the Digital Divide. It is therefore essential that the digital multi service city does everything in its power to reduce and defeat this Digital Divide. Cities have some answers to fulfil the Digital Equity: • Digital Public Space in some of the city property (e.g. city house, library house, library truck). • In such place where anyone who wishes (children, adults, all social classes, all ages) can come to connect the available computers and access the Internet for all types research. • Public Wi-Fi in some of the city property or areas (e.g. city house, city green park, city places). • Facilitating (e.g. building permit, taxes incentives) Service Provider in their Broadband deployment (wired or wireless) within the city administrative scope. • Specific education courses within the children schools or recycling courses for elderly. |
8431d4af277734b76ed585d18d1f2707 | 105 174-7-1 | 6.6 Pledge of confidence | Municipalities collect and own numerous information about their inhabitants, companies established in the territory and commuters. On one side, they have immediate access to data such as electricity or water consumptions, the amount of produced waste, the financial income, the properties ownership, the various contacts information (addresses, phones numbers, etc.), the family status and composition, etc. On another side, when fostering smart city, thru various deployed digital technologies, they may have access to people locations (e.g. Bluetooth kiosk on bus stops, Wi-Fi in hotspot, video security camera, Location Based App, etc.), to consuming habit (e.g. traffic thru the public internet access), etc. ETSI ETSI TS 105 174-7-1 V1.1.1 (2017-06) 21 Many smart cities platforms collect, analyse and share the data about the citizen or produced by them. This extraordinary amounts of information, combined with Big Data processing can really impact the privacy of the citizen. It is important that cities take action to analyse and define framework in field such as data ownership, data privacy, data access transparency and also offer a way for the citizen to control these subjects. Numerous studies have established that personal data are valuable. In the business data broker industry, personal data monetisation is common: one get finance free access to a service but in exchange do accept to trade the data generated by the service usage. It is commonly known that an individual worth around one euro. The market leads to multi-billion euro when broker has access to abundant number of individual profiles. Cities have often budget difficulties, particularly when it deals with ICT. It is important that city authorities are not attracted by such kind of monetization and that they comply with the regulatory framework. Beside their role of ensuring data privacy of the people, cities shall also ensure the confidentiality of these data. It is important to apply this constraint to both data transfer and data storage. |
8431d4af277734b76ed585d18d1f2707 | 105 174-7-1 | 6.7 Digital Infrastructure | Some of the services delivered by cities are associated with physical networks assets such as delivery (e.g. water, electricity, gas, lightning), collection (e.g. sewage), mobility (e.g. metro, tram) and telecommunication (e.g. data, voice, IoT sensors, traffic light, video security). Similarly to behaviour that can be observed in the data silos generated by the independence of service departments, cities often suffer from important separations in the various networks. To reach a correct level of sustainability, cities should rationalize and unify networks when possible. Telecommunication networks are appropriated for such operational merging thru infrastructure sharing. Synergies are also possible with the other network assets: • Fiber backbone and access can be deployed in aerial thru the lamp pole infrastructure or underground thru the sewage infrastructure. • IoT sensors or Wi-Fi hotspot can be deployed thru urban assets such as bus stops, public dustbin, or tourist information kiosk. |
8431d4af277734b76ed585d18d1f2707 | 105 174-7-1 | 6.8 Metric and KPI | In order to measure the improvements that ICT technologies bring to the city services and the quality of life of its citizen and enterprises commuters, it is crucial to define Key Performance Indicators (KPI) which are clear, understandable and realistic to determine. These KPI enable both the city to calculate the smart enhancements in the provided services but also to position itself into the regional, national and international scene. Thru these indicators, the municipal authorities and their stakeholders should have a common understanding of the "smartness level" of the various field of involvement of the city. |
8431d4af277734b76ed585d18d1f2707 | 105 174-7-1 | 7 General needs from the cities | |
8431d4af277734b76ed585d18d1f2707 | 105 174-7-1 | 7.1 ICT users' position | Energy efficiency of data centre buildings, transmission node building, computer rooms, networks and IT systems is of high importance for the ICT Customers who are users of ICT System Installations e.g. Car manufacturers, Banks, Insurance Companies, Network Operators, Airplane Companies and Governmental Ministries. Independently from the ICT systems integrators, service providers, producers and manufacturers of ICT system installations, in the perspective of EU Digital Agenda mechanism and law enforcements, these Users are proposing commonly agreed, proofed KPIs and framework of implementation. Such energy management KPIs will help Users of Operational Architecture to easily identify, compare and scale the effective energy efficiency of their ICT installations internally and with the other Users. ETSI ETSI TS 105 174-7-1 V1.1.1 (2017-06) 22 The following Position Papers from the Industrial Specification Group Operational energy Efficiency for Users (ISG OEU), focusing on smart cities, will be provided in order to complement the present ETSI standards: • ETSI GS OEU 009 [i.19] : Global KPI Modelling for Green Smart Cities "Definition of Global KPI Modelling for Green Smart Cities. This modelling will cover ICT domain including residential and office areas". • ETSI GS OEU 019 [i.20] : OEU KPIs for Smart Cities "The deliverable will define indicators (KPI) for Smart Cities expressing city level in terms of People, Planet, Prosperity, Governance and Propagation". The following recommendation from the ITU-T Study Group 20, focusing on smart sustainable cities, gives a general guidance to cities and provides an overview of key performance indicators in the context of smart sustainable cities: • Recommendation ITU-T Y.4900 [i.53]: "Overview of key performance indicators in smart sustainable cities". It belongs to a series of recommendations and supplements about KPI definitions which also includes: • Recommendation ITU-T Y.4901 [i.54]: "Key performance indicators related to the use of information and communication technology in smart sustainable cities". This recommendation lists the KPIs focusing on ICT use in smart sustainable cities. • Recommendation ITU-T Y.4902 [i.55]: "Key performance indicators related to the sustainability impacts of information and communication technology in smart sustainable cities". This recommendation lists the KPIs used for ICT impact on sustainability. • Recommendation ITU-T Y.4903 [i.56]: "Key performance indicators for smart sustainable cities to assess the achievement of sustainable development goals". This supplement provides information regarding KPIs and evaluation index systems of smart cities, KPIs of sustainable cities, etc. The following recommendation from the ISO/TC 268 [i.59] technical committee, focusing on sustainable cities and communities, defines and establishes methodologies for a set of indicators to steer and measure the performance of city services and quality of life. • ISO 37120:2014 [i.57]: "Sustainable development of communities -- Indicators for city services and quality of life". ETSI ETSI TS 105 174-7-1 V1.1.1 (2017-06) 23 Figure 2: ICT users' digital domains of interest |
8431d4af277734b76ed585d18d1f2707 | 105 174-7-1 | 8 Multiservice digital infrastructure | |
8431d4af277734b76ed585d18d1f2707 | 105 174-7-1 | 8.1 A shared digital infrastructure as core foundation | The core foundation for a digital multiservice city is strongly tighten to the ability that the components of its ICT systems have to interoperate. To achieve this goals, city should install a shared communications infrastructure that will allow the ICT systems of the complete services departments to interconnect seamlessly and securely to each other. 8.2 Management of the various network cabling infrastructures of the city Performant ICT requires the access to a high speed network. To achieve the goal of a ubiquitous digital access the city network backbone should span across the entire territory. When seen thru the silos approach, the deployment of such a broadband network architecture, mainly composed of optical fibre and most probably high speed wireless point to point links, on a large geographical scale is a complex and expensive civil engineering challenge. However, when seen thru the cross-domain approach, evidence demonstrate the benefit of sharing passive infrastructure amongst different city departments of city partners such as utilities. Numerous city network infrastructures can be leveraged to achieve this strategy: • Access to electrical power distribution infrastructure. • Access to ducts, trenches. • Access to lighting infrastructure. • Access to water distribution infrastructure. • Access to gas distribution infrastructure. ETSI ETSI TS 105 174-7-1 V1.1.1 (2017-06) 24 • Access to sewer collecting infrastructure. Furthermore, other passive city assets such as real estate properties (technical room facility), conduits, manholes, cabinets, lamppost, poles, masts, antenna, towers and other supporting constructions could also play an important role in the design of the digital multiservice city infrastructure. Best practices in network architectures organize the infrastructure topology into a multi layers structure which spans across the geographical area to deserve at city scale or urban metropolis scale. • Layer 1: Digital multiservice city core network: - The core network provides high-speed and redundant forwarding services to move the data packet between the distribution nodes which span across the city area. The core nodes (usually routers) are commonly the most powerful, in terms of forwarding power; they define the Wide Area Network (WAN). When city communication networks interconnect to each other, some of these nodes also acts as Metropolitan Area Network (MAN) inter-exchanges nodes. Current appropriated bandwidth are high speed links such as Gigabit and 10 Gigabits. • Layer 2: Digital multiservice city distribution Network: - The distribution network is often referred as the multiservice delivery level which offer several smart layers' functionalities for the various policies related to data packet routing, data packet filtering and Quality of Services (QoS). The distribution nodes (usually routers and switches) are mainly dedicated to connect the network sites (LAN) to each other; their links to the network sites are often referred as last mile connections. Appropriate dispersal of these network nodes across the city geographical area makes them also an appropriate place to connect special delivery network elements, such as the municipality urban assets. Current appropriated bandwidth are high speed links such as Gigabit (and potentially 10 Gigabits). • Layer 3: Digital multiservice city access Network: - The access network is often referred to the desktop layer. The access nodes (usually switches) have the main concern to connect the end hosts (workstation, server, enterprise devices: wireless access point (AP), printer, scanner, IP phone/camera, etc) to the city network infrastructure. The proximity of these nodes to the end devices makes them also an appropriate place to deliver secured electricity power (Power over Ethernet, PoE IEEE 802.3af [i.35] or IEEE 802.3at [i.36]) to low consumption devices (Wi-Fi AP, IP phone/camera, IoT gateway, etc). Current appropriated bandwidth are high speed Gigabit connections. When reaching the network site layer, the hierarchy of the infrastructure topology can be further organized in stratums to fit the actual architectural structure of the local area (single or multi floors house/building, a multi constructions administrative district/campus) to deserve. Typical network topology for LAN access includes star, mesh, tree, and clusters. The digital multiservice delivery across the city wide area implies to cope with multiple distances ranges. Core node links can deal with long distances which ranges from km to tens of km whereas distribution nodes links deal with distances from hundreds of metres to a km. Off course, the transmission capability to achieve such distances depends of the physical communication medium: optical fiber is nowadays the preferred media to succeed in the delivery of multi (tens/hundreds) gigabits in long distances (core/distribution) links thru optical transmissions. However, in various cases electrical transmissions over copper (twisted pair or coax) or wireless links can still be delivering acceptable high speed data rate for distribution network links. ETSI TR 105 174-4 [i.2] and ETSI TS 105 174-4-1 [i.3] detail measures which may be taken to improve the energy management of access networks for broadband deployment. To the extent possible the city should do everything in order to have total control over its digital multiservice city infrastructure. In other words, it is valuable and advantageous for the city to deploy its own physical networking fiber connectivity links when technically feasible. When considered in a mid (3 years) to long term (10 years) strategic vision, having the ownership of the networking links is a smarter than having contractual access to a service provider (SP) infrastructure. ETSI ETSI TS 105 174-7-1 V1.1.1 (2017-06) 25 Beside such economical consideration, there are various technical reasons which drive the city to deploy its own physical fiber network infrastructure or to contract, from a carrier, for dark (unlit) fibre links: • Freedom of the optical transmission standard: network bandwidth depends of the fibre transceivers which are bound at the extremities of the fibre link and the length of this one. According to the link needs, the municipality can lit the fibre with the most appropriate transceiver (from a single wavelength to wavelength- division multiplexing, from gigabit to multigigabits). Should a link speed need to increase, the municipality has the freedom to upgrade the transceivers. • Freedom of the digital transmission standard: digital data transmissions can be operated by various technologies such as Ethernet, MPLS, etc. According to the engineering of the digital services and the requirement for network resilience one can be more suitable than the other. Network size, number of digital services, security concerns, multi-homing requirement, etc. are concerns which drives the choice of the optimal transmission standard. • Ease of introduction of new digital services: to leverage a single physical network infrastructure sharing while delivering to each digital service within its own controlled environment, the municipality can either chose to introduce a new IP service by the mean of a complementary VLAN in Ethernet, a complementary LSP in MPLS, or even by the assignment of a specific light wavelength which virtualizes the link at the optical level. • Freedom of the choice of ISP: Different Internet access might be required to be served by different service providers. While public administration agents require access to specific Internet service provider with specified technical SLA (redundancy, low latency, security, etc.), schools, libraries, police, citizen free public Internet, IoT sensors, etc. may use other service providers. ETSI TS 105 174-1 [i.1] focuses on the best practice for cabling and installations and transmission implementation independently from the ownership of these infrastructures. ETSI TS 102 973 [i.8] describes a proposal of requirements for a Network Termination (NT) device in Next Generation Access Networks. Deploying networking links includes planning and routing, obtaining permissions, creating ducts and channels for the cables, and finally installation and connection. When the situation permits, aerial links installation have to be preferred instead of digging the streets or sidewalks. In that concern, Objectif Fibre organization from the Federation des Industries Electriques, Electroniques et de Communication (FIEEC) has published a practical guide to deploy shared local optical infrastructure over aerial support [i.39]. However, there are various situations in which completely following such strategy it is simply unfeasible. In such cases, when contracting with an SP, passive network links (e.g. dark fibres) have to be preferred over active network links (e.g. leased line). Digital service end points are usually distant from their access nodes in range from a few metres to a few hundred metres. As for the other communication layers, speed, achieved distance and access flexibility depend on the physical medium in use. Cable free connectivity offered by wireless technologies such as Wi-Fi (Electromagnetic Communication, EM) or Li-Fi [i.21] (an improvement of Visible Light Communication, IEEE VLC [i.24]) deliver suitable speeds, to the user desktop. From hundreds of gigabits over a few metres with LiFi (under certain conditions) up to multi-gigabits over hundreds of meters for existing contemporary IEEE Wi-Fi standards (e.g. IEEE 802.11ac [i.50]: 1 Gbit/s, IEEE 802.11ad [i.49]/WiGig [i.26]: 4 Gbit/s). Current trends raised by the fields of IoT and M2M give to low speed (few kbit/s or hundred kbit/s) wireless communication technologies a significant role to play into the digital multiservice city infrastructure. Connectivity in this low speed and low power wireless network access can be categorized into two main viewpoints: short distance (LR-WPAN, LP-LAN) and long distance (LP-WAN). In the former viewpoint, connected objects join the IoT wireless (mainly in unlicensed RF ISM band) gateway hooked to the city infrastructure at the Access Network layer whereas in the later viewpoint the connected objects join the IoT Base Transceiver Station (BTS) of a mobile operator network infrastructure (using his licenced RF band). ETSI TR 103 375 [i.13] provides a complete landscape view on these IoT technologies for Smart Cities. Regarding the data transport technology, it is clear that IP (v4 and v6) and Ethernet [i.30] are the most suitable addressing and data transmission protocols to be deployed for the digital multiservice city infrastructure layers. Appropriate addressing plan, network hierarchy, security policies such as packet filtering and firewalling rules as well as and related QoS support have to be well engineered to achieve the design of a digital multiservice city delivery infrastructure. ETSI ETSI TS 105 174-7-1 V1.1.1 (2017-06) 26 Furthermore, although Ethernet has been proven to be a good transport technology for WAN, large city core network may need to consider other types of carrier class transport technologies such as Multiprotocol Label Switching (MPLS, IETF RFC 3031 [i.27]) or Virtual Private LAN Service (VPLS, IETF RFC 4761 [i.28] and IETF RFC 4762 [i.29]). However, these considerations as well as engineering details on optical network architectures are outside the scope of the present document. |
8431d4af277734b76ed585d18d1f2707 | 105 174-7-1 | 8.3 Digital services delivery thru the urban assets | |
8431d4af277734b76ed585d18d1f2707 | 105 174-7-1 | 8.3.1 Leveraging street furniture with digital technologies | Street furniture [i.15] is a collective term for objects and pieces of equipment installed on city streets and city roads for various purposes. These urban assets include the objects listed in the following clauses. Many of these city urban assets can be leveraged to either contribute as: • network access nodes within the multilayer mesh which constitute the unified digital communication infrastructure; • an service distribution and wireless AP node towards end users or connected objects (sensors, actuators) of the IoT world. 8.3.2 Usages of billboard, streetlamp, bollard and various poles, bench and picnic table Most of these urban assets can play a role in the enhancement of the sustainability of the city. These assets can be promoted to a role which provides additional services beyond the native one. For instance, these urban assets can be the operation points for: • Communications as transmitter/receiver points for data communications thru Li-Fi. • Provide public Wi-Fi services as a new city infrastructure. • Public security, through use of CCTVs (IP video security) on posts. • Control of light attenuation levels. • Environmental sensing (air quality, noise pollution monitoring). • Environmental management through CCTVs. • Traffic control through thru CCTVs or radar. • Parking (monitoring) availability and access through sensors and actuators. • Smart meters reading. • Sound level monitoring thru sensors. • Movement activity monitoring thru motion sensors of CCTVs. • Image sensing (proximity, pedestrian counter). • Digital signage (way finding, traffic direction, civic information). • Water level/flood monitoring. • Etc. ETSI ETSI TS 105 174-7-1 V1.1.1 (2017-06) 27 Thru these various data sources, intelligent cross domain analyses and processing (most probably thru Big Data platform) can be leveraged to offer useful services to the city and it audiences. Typical example includes the adaptation of the streetlamp illumination level according to environmental parameters such as lighting condition, proximity of a user, detection of an abnormal incident. Offering to the citizen a better quality of life could be a simple as sharing the harvested information related to the quality of the air of the presence of high level of flower pollens in rest areas, green parks and other child park. Beside data harvesting functions, these urban assets can be considered as information delivery points, to the proximity users, either thru local display mechanism (e.g. info kiosk, interactive or not) either thru digital service delivery pushing the contextualized information directly into the user mobile terminal (e.g. smartphone, tablet) via locally generated wireless access point (e.g. Wi-Fi, Bluetooth, Near Field Communication/NFC) or thru voice and data communication over cellular networks (e.g. via small cells). |
8431d4af277734b76ed585d18d1f2707 | 105 174-7-1 | 8.3.3 Usages of bus or tram stop, taxi stands and phone box | Most of these urban assets can play a role in the enhancement of the sustainability of the city and the operations of their partners. These assets can be promoted to a role which provides additional services beyond the native one. These urban assets have in common the particularity to be places which concentrates significate number of individuals who standing there for a while and often expecting precise details related to the service delivery (e.g. real-time time-schedule, availability, traffic condition, etc.). One-dimensional approach for connecting such urban asset to the digital multiservice city network can be to connect dynamic display boards, CCTV camera or Wi-Fi hotspot. By adopting a multi-dimensional approach, innovative and sustainable new type of operation can be offered. Local facts such as number of persons, presence of disabled persons, can be valuable information that can be taken into account by the IT system to take decisions and improve the dynamic operation of the transportation system. Furthermore, as a place which concentrates significant number of individuals in a defined area, these urban assets may be considered as an appropriate location to deliver cellular network communication (e.g. via small cells). This would represent on one side the opportunity to improve the overall performances of the mobile network while opening a complementary channel for (geo)localized digital service information delivery directly into the user mobile terminal. |
8431d4af277734b76ed585d18d1f2707 | 105 174-7-1 | 8.3.4 Usages of post box and waste trash | Most of these urban assets can play a role in the enhancement of the sustainability of the city and the operations of their partners. These assets can be promoted to a role which provides additional services beyond the native one. These urban assets have in common a physical characteristic associated to a "level of spatial volume used". By associating appropriated sensors, the cross domain pillar associated with the data culture and appropriated Big Data processing can add value to: • The optimization of the paths executed by the waste collecting trucks. • The conservation of the state of cleanness of the city by avoiding overfilled bin. • The optimization of the paths executed for the sent mail collection. • The opening of the post boxes to other type of content to be shipped (e.g. e-commerce good delivery/return). • Etc. Associating appropriated sensors to waste trashes can also monitor air quality and pollution/ unpleasantness caused by odours in order to keep a good the quality of life for the surrounding peoples. The position of the waste trashes on the street level is a strategic advantage, particularly in dense skyscrapers cities, when considering delivering Wi-Fi hotspot to the pedestrian, the surrounding vehicle or other city urban assets. Since the bins are located on street level, service coverage and signal quality can be outstanding as they the wireless network is not perturbed from any interference from the buildings. ETSI ETSI TS 105 174-7-1 V1.1.1 (2017-06) 28 |
8431d4af277734b76ed585d18d1f2707 | 105 174-7-1 | 8.3.5 Usages of traffic sign and traffic light | Most of these urban assets can play a role in the enhancement of the sustainability of the city. On one hand, these assets can have their operations improved and on the other promoted to a role which provides additional services beyond the native one. These urban assets have in common the functions to signal and communicate to the proximity users (e.g. pedestrians, motorist, cyclist, drivers, workers) important information but also to secure and regulate the associated traffics (e.g. road, street, highway, rail road, tram line, crossroads, railroad crossing). These urban assets are traditional places were sensors (e.g. motion sensor, radar, CCTVs) are located and information presented (e.g. traffic light, info screen, sound alert). However, recent digital technologies can still increase the benefits of such urban assets. Furthermore, the connection to the digital multiservice city network of the city can empower the cross domain pillar by enabling new type of innovative services. These urban assets are often in proximity of a substantial number of individuals. Hence, they may be considered as an appropriate location to deliver cellular network communication (e.g. via small cells). This would represent on one side the opportunity to improve the overall performances of the mobile network while opening a complementary channel for (geo)localized digital service information delivery directly into the user mobile terminal or onto next generation connected devices such as automotive which would embed a screen right into the windshield to support the driver by displaying by example a focus of the nearest traffic sign(s). Electronic paper coupled with a dynamic access to the digital multiservice city network of the city can transform any fixed infographic traffic sign into an adaptive infographic which communicates different contextualized information to the proximity users. Such dynamic road signalling can also be of a benefit in the regulation and optimization of the traffic within the city (e.g. guidance to the nearest available parking place, guidance to the lowest a crowded street). Enabling alternative sustainable transportation mechanisms is within the concern of many city councils. Today, cycling is considered as significant instrument that cities stimulate to answer their sustainability concerns. Prioritizing cyclist when it rains can be achieved by associating heavy rain sensors to the traffic lights operation. Nevertheless, such dynamicity of the operations has to be handled with care. Connectivity to the digital multiservice city network should be available to ensure that the monitoring and global operation of the cross-over is performing well. 8.3.6 Usages of fountains, public lavatory, watering trough, street gutter, storm drain and fire hydrant Most of these urban assets can play a role in the enhancement of the sustainability of the city. These assets can be promoted to a role which provides additional services beyond the native one. All of these urban assets are related to water. This water origin can be: • water from a cave source; • water from the distribution network; • water from the sewing collecting network; • water from a river; • water from a wastewater treatment plant; • etc. For instance, these urban assets can be the operation points for: • water source pumping (production) monitoring and control; • water recycling (production) monitoring; • water volume consumption monitoring and control; • water quality monitoring; ETSI ETSI TS 105 174-7-1 V1.1.1 (2017-06) 29 • operational (pressure, temperature, hydraulic, etc.) parameters monitoring and control; • servicing control (tap/valve: open, close, flow regulation) management and control; • securing critical services (fire hydrant operation, water tower operation); • water pollution (e.g. pollutant, decease microbe) containment; • water flows (clean and dirty) monitoring; • water leakage monitoring and control; • water flooding (e.g. river level, drain sewer, street gutter) prevention. Production, distribution, consumption, collection and treatment of waste water represent the full cycle in the water department. Good operations of such city responsibility is a key element of an urban system. Although numerous water services management standards have been developed there is a need for defining, through use cases, what IoT can bring into the scene to address sustainable development goals. |
8431d4af277734b76ed585d18d1f2707 | 105 174-7-1 | 8.3.7 Usages of memorial, statue, and public sculpture or art | Most of these urban assets can play a role in the enhancement of the sustainability of the city. These assets can be promoted to a role which provides additional services beyond the native one and in full accordance with preservation of cultural heritage. All of these urban assets are related to city history, local art, tourist attraction, etc. These urban assets can be collecting point for various environmental information: • Air quality monitoring. • Noise pollution monitoring. • Sound level monitoring. • Movement activity monitoring. • Etc. But they can also be delivery point for the information related to the urban asset itself (artist, history, art description, etc.) thru: • A mobile terminal of the proximity users with: - Near Field Communication. - Bluetooth. - Wi-Fi. - Li-Fi. • An associated Digital Human Interface: - Interactive display thru touch screen. - Interactive display thru camera motion tracking interface. Digital technologies can also be a way to increase the attractiveness of the sites: interactive experiences such as adaptive lightning, voice interactions, virtual complementary educational content projections, etc. Beside data harvesting functions, these urban assets can be considered as information delivery points, to the proximity users, either thru local display mechanism (e.g. info kiosk, interactive or not) either thru digital service delivery pushing the contextualized information directly into the user mobile terminal (e.g. smartphone, tablet) via locally generated wireless access point (e.g. Wi-Fi, Bluetooth, Near Field Communication/NFC) or thru voice and data communication over cellular networks (e.g. via small cells). ETSI ETSI TS 105 174-7-1 V1.1.1 (2017-06) 30 8.4 Technologies which leverage the digital sustainability of a city Specialist Task Force 505 (STF 505) is a group of experts, funded by the European Commission and supported by ETSI, commissioned to provide on the one hand an in-depth analysis of the IoT Standardization landscape and on the other hand, an identification of the IoT standardization gaps. STF 505 technical recommendation ETSI TR 103 375 [i.13] provides an overview of the IoT standards (requirements, architecture, protocols, tests and related open source projects) for the various landscape introduced by "IoT LSP Standard Framework Concept" [i.14] from the Alliance for the Internet of Things Innovation (AIOTI). "The Internet of Things requires and triggers the development of standards and protocols in order to allow heterogeneous devices to communicate and to leverage common software applications. Several standardization initiatives currently co-exist, in individual standardization organization or partnerships (e.g. ETSI SmartM2M, ETSI SmartBAN, ITU-T, ISO, IEC, ISO/IEC JTC 1, oneM2M, W3C, IEEE, OASIS, IETF, etc.) and also in conjunction with a number of industrial initiatives (e.g. All Seen Alliance, Industrial Internet Consortium (IIC), Open Connectivity Foundation (OCF), Thread protocol, Platform Industrie 4.0, etc.). It is therefore necessary to understand the global dynamics of IoT standardization in order to leverage on existing standardization activities, if relevant, vis-à-vis existing initiatives and to ensure a thorough understanding of market needs and requirements. ITU-R is working on the future International Mobile Telecommunications (IMT) for 2020 and beyond, that covers all aspects for enhanced mobile broadband telecommunication including Internet of Things (IoT). Enhanced mobile broadband networks enable high-speed and ultra-reliable mobile (Internet) connectivity to applications such as video streaming/UHD screens, work and play in the cloud, voice, augmented/virtual reality, industrial automation (M2M), smart grids, self-driving cars, smart homes/buildings and smart cities. Sustainable digital city content is made up of many services, e.g. smart transportation, smart home, smart waste management to mention just a few. Clause 6 of ETSI TR 103 375 [i.13] focuses on the standards that are available to enable the ICT systems of a city to function as a clever and performing single integrated system. |
8431d4af277734b76ed585d18d1f2707 | 105 174-7-1 | 8.5 Engineering of the urban assets (street furnitures) | |
8431d4af277734b76ed585d18d1f2707 | 105 174-7-1 | 8.5.1 Common engineering | Serious evolutions in the field of fixed and mobile connectivity and wireless contactless technologies are turning urban, passive physical asset into smart, connected street furniture which can interact in the city with the people offering contextualized contents. These interaction points should be able to communicate with inhabitants, visitors, travellers with the help of digital devices which could be mobile terminal in their hands (smartphone, tablet, etc.) or embedded in the vehicle (car, bike, bus, train, etc.) as well as Human Machine Interfaces (HMI) attached to the urban assets itself. To provide services beyond the function for which they are engineered, street furniture and city urban assets in general should be connected to the digital multiservice city infrastructure. Interconnecting these elements should enable the municipality and related partners, to leverage the cross domain and data culture pillars. To leverage network connectivity and digital service functions, the urban asset should be powered by electricity. The electrical power may be delivered by a permanent link to the electrical distribution network or may be consumed from a local battery source feed by solar panel or alternative power generating devices. Energy which is consumed by the urban asset in performing its digital services should be monitored and appropriate levels of energy saving should be applied when possible. The monitoring of the consumed energy should be performed in centralized operations. However, energy saving capabilities (e.g. standby mode, sleep mode) may operate in a decentralized manner which can be on the level of the urban asset itself. Connected urban assets are part of the whole Internet of Things sphere. As such, smart urban assets contain hardware platforms with embedded computing platform running firmware and Operating System (OS). These hardware platforms can leverage UEFI Forum Advance Configuration and Power Interface (ACPI [i.42]) specifications for power management. ETSI ETSI TS 105 174-7-1 V1.1.1 (2017-06) 31 When the urban asset is not connected to a permanent source of electrical energy, appropriate engineering should be applied to the battery capacity to enable the digital services functions to operate without any interruptions also during the recharging cycles. Urban asset should require regular voltage (220 V) or low power voltage (48 V) to operate. Urban asset should be considered as leaf node of a network for data collection and processing. When interconnecting with the digital multiservice city network, the urban asset should attach to the access network layer. However, in certain cases the urban asset may attach to the distribution network layer. Such situations are, in a non-exhaustive way, when: • the node is enabling other network nodes to attach to the network; • the node is acting as part of a meshed network; • the node is performing specific network services (e.g. data packet routing/filtering, QoS); • etc. When the digital features set includes such function the urban asset should be considered as a layer 3 access node. Physical network connectivity of the urban asset to the digital multiservice city infrastructure should be correctly engineered according to network characteristics required for the provided digital features set: • low latency services should be associated with fibre connectivity; • bandwidth intensive services should be associated with fibre connectivity; • high upstream data rate services should be associated with fibre connectivity; • low data rate service should be associated with wireless connectivity. When the digital features set includes mission critical functions, the urban asset should be connected to at least two network nodes of the access layer or the distribution layer. Network addressing of the urban asset should use IP technology and should support IPv4 and IPv6. Technologies such as Network Address Translation should be banned. When an urban asset is considered as an access layer node which aggregates several concurrent digital services, the urban asset should be capable to identify and provide services differentiation in order to ensure the delivery of the appropriate Quality of Service to each of the leaf nodes which require it. Networking technologies such as: • IETF Type of Services Diffserv protocol (IETF RFC 2474 [i.43], IETF RFC 2475 [i.44]) to differentiate services on the IP network layer. • IEEE Class of Services (IEEE 802.1p [i.47]) for Ethernet Virtual LAN (IEEE 802.1q [i.37]) to differentiate services on the Media Access Control (MAC) of the Ethernet network layer. • Wi-Fi Multimedia (WMM IEEE 802.11e [i.48]) to differentiate services on the Media Access Control (MAC) of the Wi-Fi network layer. When an urban asset is considered as an access layer node for non IP digital leaf nodes (e.g. sensor, actuator), the urban asset IP identity should be used on behalf of this network leaf node. Furthermore, if these complementary digital technologies offer any service quality feature, they should be used to deliver end to end QoS when necessary. In order to facilitate the IP addressing of the urban asset, a dedicated network hostname associated with an appropriate network domain name should be defined in a Domain Name Service (DNS; IETF RFC 1034 [i.40], IETF RFC 1035 [i.41]) directory. Beside the digital addressing scheme, the digital asset should be associated with a geolocation parameter indicating the geographical position within the city area. For fixed urban assets, the position can be identified by an operator; however, for mobile urban assets the position should be defined by mechanisms such as GPS, radio triangulation, etc. ETSI ETSI TS 105 174-7-1 V1.1.1 (2017-06) 32 The above technical engineering should be taken into consideration for each street furniture (urban asset) on a per use case situation. As introduced in clause 8.2, urban assets can be categorized into digital contextual purposes: • Engineering of billboard, streetlamp, bollard and various poles, bench and picnic table. • Engineering of bus or tram stop, taxi stands and phone box. • Engineering of post box and waste trash. • Engineering of traffic sign and traffic light. • Engineering of fountains, public lavatory, watering trough, gutter, storm drain and fire hydrant. • Engineering of memorial, statue, and public sculpture or art. The engineering of these digital contextual purposes will be described into separated technical specification. These documents will be complementary individual specifications for these network entity (leaf nodes) and network sub- systems (IoT nodes gateways/bridges) of the presently introduced digital multi service city Next Generation Network. Clause 8.5.2 introduces the suggested technical engineering architecture for the first urban asset category. 8.5.2 Engineering of billboard, streetlamp, bollard and various poles, bench and picnic table The urban assets can play a role in the enhancement of the sustainability of the city by providing additional services beyond the native one. This street furniture can, with appropriated structural layouts (build-in, adjusted or revised), be promoted to a network node for various communication technologies to either harvest data of or to provide communication facilities to other network nodes. Figure 3 shows the content and external connectivity of a particular category of the city urban assets in a little more details though this diagram is intended to illustrate the types of equipment employed, not its internal connectivity. For the purposes of the present study, the boxes marked "TxRx" will be regarded as part of the access or distribution network, as appropriate and their power requirements included in the assessments for those networks. Figure 3: Engineering of urban asset ETSI ETSI TS 105 174-7-1 V1.1.1 (2017-06) 33 Connection link to the digital multiservice city network Access to the digital multiservice city infrastructure from various part within the city area implies to cope with multiple distances ranges. Urban assets node links can deal with distances which ranges from hundreds of metres to a few km. The transmission capability to achieve such distances depends of the physical communication medium: optical fibre is nowadays the preferred media to succeed in the delivery of (multi) gigabits for such distances links thru optical transmissions. Physical connectivity of the street furniture to the digital multiservice city network should be point-to- point fibre link to the nearest access or distribution node. However, in various cases electrical transmissions over copper (twisted pair or coax) can still be delivering acceptable high speed data rate for the connection to the digital multiservice city infrastructure. ETSI TR 105 174-4 [i.2] and ETSI TS 105 174-4-1 [i.3] detail measures which may be taken to improve the energy management of access networks for broadband deployment. To the extent possible the city shall do everything in order to have total control over the urban asset link to the digital multiservice city infrastructure. In other words, it is valuable and advantageous for the city to deploy its own physical networking fibre connectivity links when technically feasible. When considered in a mid (3 years) to long term (10 years) strategic vision, having the ownership of the networking links is a smarter than having contractual access to a service provider (SP) network infrastructure. Beside such economical consideration, there are various technical reasons which drive the city to deploy its own physical fibre network infrastructure or to contract, from a carrier, for dark (unlit) fibre links: • Freedom of the optical transmission standard: network bandwidth depends of the fibre transceivers which are bound at the extremities of the fibre link and the length of this one. According to the link needs, the municipality can lit the fibre with the most appropriate transceiver (from a single wavelength to wavelength- division multiplexing, from gigabit to multigigabits). Should a link speed need to increase, the municipality has the freedom to upgrade the transceivers. • Freedom of the digital transmission standard: digital data transmissions can be operated by various technologies such as Metro Ethernet, MPLS, etc. According to the engineering of the digital services and the requirement for network resilience one can be more suitable than the other. Network size, number of digital services, security concerns, multi-homing requirement, etc. are concerns which drives the choice of the optimal transmission standard. • Ease of introduction of new digital services: to leverage a single physical network infrastructure sharing while delivering to each digital service within its own controlled environment, the municipality can either chose to introduce a new IP service by the mean of a complementary VLAN in Ethernet, a complementary LSP in MPLS, or even by the assignment of a specific light wavelength which virtualizes the link at the optical level. • Freedom of the choice of ISP: Different Internet access might be required to be served by different service providers. While public administration agents require access to specific Internet service provider with specified technical SLA (redundancy, low latency, security, etc.), schools, libraries, police, citizen free public Internet, IoT sensors, etc. may use other service providers. ETSI TS 105 174-1 [i.1] focuses on the best practice for cabling and installations and transmission implementation independently from the ownership of these infrastructures. ETSI TS 102 973 [i.8] describes a proposal of requirements for a Network Termination (NT) device in Next Generation Access Networks. Data communication service To deliver data connectivity to neighbourhood network nodes towards the digital multiservice city network, the urban asset may support the following set (or subset) of standardized technologies: • Wireless networking: IEEE 802.11 [i.22] Wi-Fi: - Hotspot should support speed requirements: IEEE 802.11ac [i.50] and IEEE 802.11ah [i.26] and may support IEEE 802.11ad [i.49]. - Hotspot should support services differentiations: multiple Service Set Identifiers (SSID) for services separation and IEEE 802.11e [i.48] for QoS. - Hotspot may support wireless meshing IEEE 802.11s [i.23]. ETSI ETSI TS 105 174-7-1 V1.1.1 (2017-06) 34 • Fixed networking IEEE 802.3 [i.30] Ethernet: - Ethernet access ports should support Fast Ethernet and Gigabit Ethernet standard: IEEE 802.3u [i.33] (100BASE-TX/UTP; 100BASE-FX/Glass Optical Fibre (GOF), Plastic Optical Fibre (POF)); IEEE 802.3ab [i.32] (1000BASE-TX/UTP); IEEE 802.3z [i.34] (1000BASE-X/Glass Optical Fibre (GOF)); and future IEEE 802.3bv [i.51] (1000BASE-X/Plastic Optical Fibre (POF)). - Energy efficiency should be considered according to IEEE 802.3az [i.31]. - Ethernet switching should support multiservice separation (VLAN IEEE 802.1q [i.37]) and traffic priority (VLAN IEEE 802.1p [i.47]). - Local power source should be available by IEEE 802.3af [i.35] "Power over Ethernet" or IEEE 802.3at [i.36] "Power over Ethernet plus". • Wireless networking: Li-Fi [i.21]. • Wireless networking: cellular networking (2G/3G/4G, etc.) [i.52]. • IETF Type of Services Diffserv protocol (IETF RFC 2474 [i.43], IETF RFC 2475 [i.44]) to differentiate services on the IP network layer when routing IP. Environment sensing and operation service The distribution of such urban asset within the city area enables to establish a significate sensing network for various type of services such as environmental sensing (e.g. air quality, noise level) thru either locally connected sensors or thru the connection to Wireless Sensor Network (WSN). Furthermore, as the urban asset has an identity on the digital multiservice city network, individual control of the native service (e.g. lightning) can be operated remotely. When the urban asset is considered as an access layer node for non IP digital leaf nodes (e.g. sensor, actuator), the urban asset IP identity should be used on behalf of this network leaf node. Furthermore, if these complementary digital technologies offer any service quality feature, they should be used to deliver end to end QoS when necessary. The urban asset may support non IP based Wireless Sensor Network such as those based on IEEE 802.15.4 [i.25] (e.g. 6LoWPAN, Zigbee, Bluetooth low energy) and Recommendation ITU-T G.9959 [i.46] Z-Wave. IP video surveillance service To deliver data connectivity to IP camera (e.g. CCTV service, motion capture service, depth vision measurement, etc.), the urban asset should support Fast Ethernet and Gigabit Ethernet standard to enable high quality video streaming. Furthermore, to deliver power to the IP camera, the urban asset should support IEEE 802.3af [i.35] "Power over Ethernet" and IEEE 802.3at [i.36] (for motorized camera). Fixed Ethernet connectivity, IEEE 802.3u [i.33] (100BASE-TX/UTP; 100BASE-FX/Glass Optical Fibre (GOF), Plastic Optical Fibre (POF)), IEEE 802.3ab [i.32] (1000BASE-TX/UTP), IEEE 802.3z [i.34] (1000BASE-X/Glass Optical Fibre (GOF)) and future IEEE 802.3bv [i.51] (1000BASE-X/Plastic Optical Fibre (POF)) should be preferred over wireless Wi-Fi connectivity to ensure service availability. Standardization of IP video surveillance (IP CCTV) is driven by industry groups Open Network Video Interface Forum (ONVIF) and Physical Security Interoperability Alliance (PSIA). ETSI ETSI TS 105 174-7-1 V1.1.1 (2017-06) 35 Annex A (informative): General needs from the cities A.1 European Innovation Partnership on Smart Cities and Communities (EIP-SCC) The European Innovation Partnership on Smart Cities and Communities (EIP-SCC) brings together cities, industry and citizens to improve urban life through more sustainable integrated solutions. This includes applied innovation, better planning, a more participatory approach, higher energy efficiency, better transport solutions, intelligent use of Information and Communication Technologies (ICT), etc. EIP-SCC invitation for commitments was closed on June 2015 with 370 eligible commitments by over 3 000 partners. All these are published on the online European Innovation Partnership marketplace [i.38] and the first public draft of the Operational Implementation Plan [i.16], the operational annex to the Strategic Implementation Plan [i.17] gives a wealth of detailed examples for integrated smart city solutions. The operational plan suggests several Priority Areas amongst which the third is focused on "Integrated Infrastructures": "Significant and as yet insufficiently tapped value is offered by integrating the various existing and new infrastructure networks within and across cities - be they energy, transport, communications or others - rather than duplicating these needlessly. This point applies, both, to active and passive infrastructure. Many such infrastructures are ageing; budgets to replace them are stretched; they are procured and managed 'in silos'; yet the potential afforded to cities and their customers through new joined-up approaches, exploiting modern technologies is substantial. This is achievable. However it will take sustained commitment from multiple parties to access value." The "Integrated Infrastructures" Priority Area suggest 11 potential actions. Amongst these actions, some are strengthening and supporting the notion of digital multiservice city network infrastructure and related smart urban assets: • Potential Action #1: The Humble Lamppost: - "Reduce energy consumption and maintenance costs through implementing e.g. efficient long-lasting lighting; motion-sensing; PV-power. Use lamppost for e.g. Wi-Fi; CCTV (parking, safety, etc.). Test innovative business models." • Potential Action #3: Shared infrastructure planning: - "Systematically exploit synergies between smart grid and broadband infrastructure, including shared engineering works, reuse of passive infrastructures, communications networks, data centres and services." • Potential Action #5: Road Systems: - "Mobile ITS (location-based route/travel information + traffic light systems = optimized traffic flow to reduce emissions and energy consumption). Work with traffic management systems and automotive industry to re-use urban sensors deployed in street scenes. Exploit sensors and devices to predict traffic conditions/improve road and traffic management." • Potential Action #7: Parking systems: - "Connect infrastructure, people and devices, and sensors to address the up to 25 % of congestion caused by people looking for parking. Mode shift through yield management pricing." ETSI ETSI TS 105 174-7-1 V1.1.1 (2017-06) 36 • Potential Action #10: Adverse Events: - "Connect key information sources with city monitoring systems (sensors, people); with city 'life-lines' infrastructures (transport, power, water, and communication) to build city resilience in the face of incidents and crisis." • Potential Action #11: Intelligent Bins: - "Putting sensors on bins enables cities to communicate within the waste collection system, optimizing truck routing, minimizing energy consumption and congestion, and satisfying customers." A.2 Humble Lamppost Amongst the commitments for integrated smart city solutions, the Humble Lamppost [i.18] is an illustration of urban asset (street furniture) valorization for sustainable city development thru a digital multiservice city infrastructure. Lighting in a city is everywhere. It is typically treated in a very tactical manner, evidenced by the ageing assets that exist, and volume of citizen complaints (in some cities it represents 20 % of the contact centre calls). Light does not come cheap - savings on energy bills is of growing attractiveness. Quality low-energy lighting is required for 'place- making', for public safety and security. It is also too often on when not needed - wasting power and money; and can result in light pollution. The lamppost is also typically a single purpose asset - for light; however that is not necessarily the only role it can play. New ICT-technologies can help transform the role of the "humble lamppost". The goal is to demonstrate how lighting can deliver early rewards for cities providing investment funds through saving for further integrated solutions in the areas of environmental and building monitoring and traffic analysis for overall emissions reduction. Firstly, in terms of using the existing physical infrastructure, enhanced with digital infrastructure, for multiple purposes: synergy across city services and goals. Secondly, in significant financial terms: lighting can represent some 20 % of a cities electricity budget; and savings in energy costs and maintenance costs of 20 % and 70 % are not uncommon, through installation of more efficient lamps. This is therefore a "quick win" for smart cities. It addresses all three content domains of the EIP (to greater or lesser extents), and also services the 20/20/20 energy and climate goals. A.3 Shared infrastructure planning The deployment of high-speed broadband networks can be made cheaper and faster by cooperating at infrastructure and services level between sectors. Various inefficiencies and bottlenecks in the rollout process exist, which lead to high costs and heavily administrative burdens for organizations wishing to deploy networks. It is estimated that up to 80 % of the costs of deploying new networks are civil engineering costs. It is also believed that savings up to 30 % could be achieved by adopting a set of simple measures, such as maximizing use of existing passive infrastructure or co- deploying infrastructure. The goal is to demonstrate synergies between the energy and telecommunication sectors at infrastructure and services levels whilst deploying Smart Grids in cities. In particular, the underlying vision is to work towards: • creating a favourable business, and technological environment for a low carbon electricity grid; • clarifying which data could be transmitted in support of Smart Grids via existing (and future) telecom network infrastructures and which data might need to have a dedicated connection/network for the purpose. ETSI ETSI TS 105 174-7-1 V1.1.1 (2017-06) 37 A.4 s[m2]art Amongst the commitments for integrated smart city solutions, s[m2]art [i.45] is an illustration of street furniture valorization for sustainable city development thru a digital multiservice city infrastructure. The project aims at creating a scalable system of smart street furniture connected together as nodes of a network for data collection and processing. s[m2]art addresses the creation of innovative prototypes of smart street furniture which can offer smart services. In a user-friendly perspective, this furniture integrates physical objects, electronic components and digital services to meet the actual needs of users, public administrations and local utilities. These smart street furniture address the challenges to assist reducing energy usage, environmental impact and carbon footprint while modernizing the infrastructure and creating high quality living environments. ETSI ETSI TS 105 174-7-1 V1.1.1 (2017-06) 38 History Document history V1.1.1 June 2017 Publication |
0e25f513e54fb64c4210e9eadff82437 | 105 174-5-4 | 1 Scope | The present document details measures which may be taken to improve the energy efficiency within industrial premises (single-tenant) by virtue of broadband deployment. Clauses 2 and 3 contain references, definitions and abbreviations which relate to this part; similar information will be included in the corresponding clauses of the other parts, thus ensuring that each document can be used on a "stand-alone" basis. Within the present document: • clause 4 describes the nature of customer premises networks in data centres (customer), defines the interfaces to those networks and identifies the standardization bodies working on the design and installation of those networks; • clause 5 describes the strategies that may be employed within data centres (customer) to both increase the energy efficiency of installed information technology equipment and to use the facilities offered by information technology services to reduce overall energy consumption. This will enable the proper implementation of services, applications and content on an energy efficient infrastructure, though it is not the goal of this multi-part deliverable to provide detailed standardized solutions for home broadband network architecture. |
0e25f513e54fb64c4210e9eadff82437 | 105 174-5-4 | 2 References | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. • For a specific reference, subsequent revisions do not apply. • Non-specific reference may be made only to a complete document or a part thereof and only in the following cases: - if it is accepted that it will be possible to use all future changes of the referenced document for the purposes of the referring document; - for informative references. Referenced documents which are not found to be publicly available in the expected location might be found at http://docbox.etsi.org/Reference. NOTE: While any hyperlinks included in this clause were valid at the time of publication ETSI cannot guarantee their long term validity. |
0e25f513e54fb64c4210e9eadff82437 | 105 174-5-4 | 2.1 Normative references | The following referenced documents are indispensable for the application of the present document. For dated references, only the edition cited applies. For non-specific references, the latest edition of the referenced document (including any amendments) applies. Not applicable. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.