joinup.ec.europa.eu · XLS file · Web viewSpecifies the Management Information Base ... which includes traditional manual systems, and ... given in EG 202 387 [3]

Organization Standard Royalty

ETSI RAND/FRAND

ETSI RAND/FRAND

CEN EN 13321-1:2012 RAND/FRAND








ETSI TS 121 101 V10.1.0 (2011-07)

ETSI TS 141 101 V11.2.0 (2016-05)








CEN EN 50090-3-1:1995 RAND/FRAND





CEN RAND/FRAND



CEN RAND/FRAND



CENELEC EN 55022:2010 RAND/FRAND

EN 50090-4-3 2nd edition:2015

EN 50090-5-3 ed. 2:2016

CENELEC EN 55024:2010 RAND/FRAND

IEC IEC 60870-5-2:1992 RAND/FRAND




IEC RAND/FRAND


IEC RAND/FRAND

IEC RAND/FRAND

IEC TR 60870-6-1:1995

IEC 60870-6-501:1995

IEC 60870-6-502:1995

IEC RAND/FRAND

IEC RAND/FRAND

IEC RAND/FRAND

IEC RAND/FRAND

IEC RAND/FRAND

IEC RAND/FRAND

IEC RAND/FRAND

IEC 60870-6-503:2014

IEC 60870-6-601:1994

IEC 60870-6-701:1998

IEC 60870-6-702:2014

IEC 60870-6-802:2014

IEC 61334-4-32:1996

IEC 61334-4-511:2000

IEC RAND/FRAND


IEC IEC 61508-1:2010 RAND/FRAND







IEC 61334-4-512:2001







IEC RAND/FRAND

IEC RAND/FRAND

IEC 61850-7-410:2012+AMD1:2015 CSV Consolidated version :2015

IEC 61850-7-420:2009



CENELEC EN 61968-1:2013 FRAND


CENELEC EN 61968-11 FRAND


IEC IEC TS 61968-2:2011 FRAND

IEC IEC 61968-3:2004 FRAND








IEC FRAND




CENELEC EN 61970-458 FRAND

IEC IEC 61970-501:2006 FRAND

IEC TS 61970-401:2005

CENELEC EN 61970-502-8 FRAND


CENELEC EN 62056-1-0:2015 RAND/FRAND

IEC RAND/FRAND


CENELEC EN 62056-42:2002 RAND/FRAND

IEC RAND/FRAND



IEC TS 62056-8-20:2016

IEC 62056-46:2002+AMD1:2006





IEC IEC 62056-8-6 RAND/FRAND


CENELEC EN 62439:2010 FRAND


IEC FRAND

IEC IEC 62443-2-1:2010 FRAND

IEC FRAND

IEC TS 62443-1-1:2009

IEC TR 62443-2-3:2015

IEC IEC 62443-2-4:2015 FRAND

IEC FRAND

IEC FRAND

IEC IEC 62443-3-3:2013 FRAND

CENELEC FRAND






IEC PAS 62443-3:2008

IEC TR 62443-3-1:2009

CLC/TR 62541-1:2010





CENELEC EN 50491-11:2015 RAND/FRAND

CENELEC DSF/PREN 50491-12 RAND/FRAND

CEN RAND/FRAND

ISO ISO/IEC 27019:2013 RAND/FRAND

ETSI RAND/FRAND

CEN-CLC-ETSI/TR 50572:2011

ETSI EG 202 387 V1.1.1 (2005-04)

ETSI RAND/FRAND

ETSI FRAND

ETSI FRAND

ETSI FRAND

ETSI FRAND

ETSI FRAND

ETSI FRAND

ETSI RAND/FRAND

ETSI EG 202 549 V1.1.1 (2006-12)

ETSI EN 301 502 V10.1.1 (2012-01)

ETSI EN 301 511 V12.1.10 (2016-12)

ETSI EN 301 908 V11.1.1 (2016-07)

ETSI EN 303 204 V2.1.0 (2015-07)

DRAFT ETSI EN 303 204-1 V1.1.0 (2014-06)

DRAFT ETSI EN 303 204-2 V1.1.0 (2014-06)

ETSI ES 202 382 V1.1.1 (2005-04)

ETSI RAND/FRAND

ETSI ETSI ETR 237:1996 RAND/FRAND

ETSI ETSI ETR 332:1996 RAND/FRAND

ETSI RAND/FRAND

ETSI RAND/FRAND

ETSI RAND/FRAND

ETSI FRAND

ETSI ES 202 383 V1.1.1 (2005-04)

ETSI TCR-TR 029:1995

ETSI TR 102 419 V1.1.1 (2005-04)

ETSI TR 102 437 V1.1.1 (2006-10)

ETSI TR 102 572 V1.1.1 (2007-07)

ETSI FRAND

ETSI FRAND

ETSI FRAND

ETSI FRAND

ETSI FRAND

ETSI TR 103 167 V1.1.1 (2011-08)

ETSI TR 185 008 V2.0.0 (2008-02)

ETSI TR 187 002 V3.1.1 (2011-04)

ETSI TR 187 012 V2.1.1 (2009-11)

ETSI TS 100 920 V8.0.1 (2001-06)

ETSI FRAND

ETSI FRAND

ETSI FRAND

ETSI FRAND

ETSI FRAND

ETSI FRAND

ETSI FRAND

ETSI FRAND

ETSI FRAND

ETSI TS 101 456 V1.4.3 (2007-05)

ETSI TS 102 042 V2.4.1 (2013-02)

ETSI TS 102 165-1 V4.2.3 (2011-03)

ETSI TS 102 165-2 V4.2.1 (2007-02)

ETSI TS 102 225 V9.0.0 (2010-04)

ETSI TS 102 226 V12.0.0 (2015-02)

ETSI TS 102 484 V11.0.0 (2012-09)

ETSI TS 102 573 V2.1.1 (2012-04)

ETSI TS 102 689 V1.1.1 (2010-08)

ETSI FRAND

ETSI FRAND

ETSI FRAND

ETSI FRAND

ETSI FRAND

ETSI FRAND

ETSI FRAND

ETSI FRAND

ETSI FRAND

ETSI FRAND

ETSI TS 102 690 V1.1.1 (2011-10)

ETSI TR 102 691 V1.1.1 (2010-05)

ETSI TS 102 921 V1.1.1 (2012-02)

ETSI TR 102 935 V2.1.1 (2012-09)

ETSI TR 102 966 V1.1.1 (2014-02)

ETSI TS 101 584 V2.1.1 (2013-12)

ETSI TS 102 221 V8.2.0 (2009-06)

ETSI TS 102 240 V11.0.0 (2011-07)

ETSI TS 102 241 V9.1.0 (2011-05)

ETSI TS 102 412 V11.1.0 (2011-12)

ETSI FRAND

ETSI FRAND

ETSI FRAND

ETSI FRAND

ETSI FRAND

ETSI FRAND

ETSI FRAND

ETSI FRAND

ETSI FRAND

ETSI FRAND

ETSI TS 102 569 V7.0.0 (2007-07)

ETSI TS 102 671 V9.0.0 (2010-04)

ETSI TS 103 092 V2.1.1 (2013-01)

ETSI TS 103 093 V1.1.1 (2012-05)

ETSI TS 103 104 V1.1.1 (2013-04)

ETSI TS 103 383 V13.0.0 (2015-10)

ETSI TS 122 368 V12.4.0 (2014-10)

ETSI TS 123 401 V11.3.0 (2012-11)

ETSI TS 123 402 V9.3.0 (2010-01)

ETSI TS 123 682 V13.4.0 (2016-03)

ETSI FRAND

ETSI FRAND

ETSI FRAND

ETSI FRAND

ETSI FRAND

ETSI FRAND

ETSI FRAND

ETSI FRAND

ETSI FRAND

ETSI FRAND

ETSI FRAND

ETSI TS 129 368 V12.4.0 (2015-04)

ETSI TS 133 203 V8.8.0 (2010-01)

ETSI TS 133 210 V13.0.0 (2016-01)

ETSI TS 133 234 4 V13.1.0 (2017-01)

ETSI TS 133 310 V10.4.0 (2011-10)

ETSI TS 136 201 V13.2.0 (2016-08)

ETSI TS 136 211 V12.7.0 (2015-10)

ETSI TS 136 212 V12.2.0 (2014-10)

ETSI TS 136 213 V13.2.0 (2016-08)

ETSI TS 136 214 V13.2.0 (2016-08)

ETSI TS 136 216 V12.0.0 (2014-10)

ETSI FRAND

ETSI FRAND

ETSI FRAND

ETSI FRAND








ETSI TS 136 300 V13.2.0 (2016-01)

ETSI TS 187 001 V3.7.1 (2011-03)

ETSI TS 187 003 V1.7.1 (2008-02)

ETSI TS 187 016 V3.1.1 (2010-06)

IEC FRAND




CENELEC FRAND

CENELEC FRAND

CENELEC FRAND

CENELEC FRAND

CENELEC FRAND

IEC SER Series 61850:2016

EN 62325-451-1:2016

EN 62325-451-2:2014

EN 62325-451-3:2014

EN 62325-451-4:2015

EN 62325-451-5:2015

CENELEC FRAND

IEC FRAND

IEC FRAND

IEC IEC 62351:2016 FRAND


IEC FRAND



EN 62325-451-6:2016

IEC TS 62325-503:2014

IEC TS 62325-504:2015

IEC TR 62351-10:2012







IEC FRANDIEC TR 62351-12:2016

IEC FRAND

IEC IEC TR 62357-1:2016 FRAND

IEC FRAND



IEC IEC 62443-3-3:2013 FRAND

ISO ISO 15118-1:2013 FRAND

ISO FRAND

ISO FRAND

ISO ISO/IEC 15118-4 FRAND

IEC TR 62351-13:2016

IEC TR 62357-200:2015

ISO/IEC 15118-2:2014

ISO/IEC 15118-3:2015






ISO RAND/FRANDISO/IEC 16484-1:2010

ISO RAND/FRAND

ISO RAND/FRAND

ISO ISO/IEC 16484-4 RAND/FRAND

ISO/IEC 16484-2:2004

ISO/IEC 16484-3:2005



ISO RAND/FRANDISO/IEC TR 29108:2013

ISO RAND/FRAND


ISO ISO 19142:2010 RAND/FRAND

ISO/IEC TR 27019:2013

ISO ISO 8601:2004 RAND/FRAND

ISO RAND/FRAND





ISO ISO/IEC 7498-1:1994 RAND/FRAND

IEC IEC 61588:2009 RAND/FRAND

ISO/IEC 12139-1:2009

Title

Communication systems for meters - Part 6: Local Bus

Universal Mobile Telecommunications System (UMTS);Technical Specifications and Technical Reports for a UTRAN-based 3GPP system (3GPP TS 21.101 version 10.1.0 Release 10)

Digital cellular telecommunications system (Phase 2+); Technical Specifications and Technical Reports for a GERAN-based 3GPP system

Open Data Communication in Building Automation, Controls and Building Management - Home and Building Electronic Systems

Open Data Communication in Building Automation, Controls and Building Management - Home and Building Electronic Systems

Communication systems for meters and remote reading of meters - Part 1: Data exchange

Communication systems for and remote reading of meters - Part 2: Physical and link layer

Communication systems for and remote reading of meters - Part 3: Dedicated application layer

Communication systems for meters and remote reading of meters - Part 4: Wireless meter readout (Radio meter reading for operation in SRD bands)

Communication systems for meters and remote reading of meters - Part 5: Wireless relaying

Open Data Communication in Building Automation, Controls and Building Management - Building Network Protocol - Part 1: Protocol Stack

Open Data Communication in Building Automation, Controls and Building Management - Control Network Protocol - Part 2: Twisted Pair Communication

Open Data Communication in Building Automation, Controls and Building Management - Control Network Protocol - Part 3: Power Line Channel Specification

Open Data Communication in Building Automation, Controls and Building Management - Control Network Protocol - Part 4: IP Communication

Open Data Communication in Building Automation, Controls and Building Management Implementation Guideline - Control Network Protocol - Part 5: Implementation

Open Data Communication in Building Automation, Controls and Building Management - Control Network Protocol - Part 6: Application elements

Home and Building Electronic Systems (HBES) - Part 1: Standardization structure

Home and Building Electronic Systems (HBES) - Part 3-1: Aspects of application - Introduction to the application structure

Home and Building Electronic Systems (HBES) - Part 3-2: Aspects of application - User process for HBES class 1

Home and Building Electronic Systems (HBES) - Part 3-3: Aspects of applications - HBES Interworking model and common HBES data types

Home and Building Electronic Systems (HBES) - Part 4-1: Media independent layers - Application layer for HBES class 1

Home and Building Electronic Systems (HBES) - Part 4-2: Media independent layers - Transport layer, network layer and general parts of data link layer for HBES class 1

Home and Building Electronic Systems (HBES) - Part 4-3: Media independent layers - Communication over IP (EN 13321-2:2006)

Home and Building Electronic Systems (HBES) - Part 5-1: Media and media dependent layers - Power line for HBES Class 1

Home and Building Electronic Systems (HBES) - Part 5-2: Media and media dependent layers - Network based on HBES, class 1, twisted pair

Home and Building Electronic Systems (HBES) - Part 5-3: Media and media dependent layers - Radio frequency

Home and Building Electronic Systems (HBES) - Part 7-1: System management; Management procedures

EN 50090-8 Home and Building Electronic Systems (HBES) - Part 8: Conformity assessment of products

Information technology equipment - Radio disturbance characteristics - Limits and methods of measurement

Information technology equipment - Immunity characteristics - Limits and methods of measurement

Telecontrol equipment and systems - Part 5: Transmission protocols - Section 2: Link transmission procedures

Telecontrol equipment and systems; part 5: transmission protocols; section 3: general structure of application data

Telecontrol equipment and systems; part 5: transmission protocols; section 4: definition and coding of application information elements

Telecontrol equipment and systems - Part 5: Transmission protocols - Section 5: Basic application functions

Telecontrol equipment and systems - Part 6: Telecontrol protocols compatible with ISO standards and ITU-T recommendations - Section 1: Application context and organization of standards

Telecontrol equipment and systems - Part 6: Telecontrol protocols compatible with ISO standards and ITU-T recommendations - Section 2: Use of basic standards (OSI layers 1-4)

Telecontrol equipment and systems - Part 6: Telecontrol protocols compatible with ISO standards and ITU-T recommendations - Section 501: TASE.1 service definitions

Telecontrol equipment and systems - Part 6: Telecontrol protocols compatible with ISO standards and ITU-T recommendations - Section 502: TASE.1 protocol definitions

Telecontrol equipment and systems - Part 6-503: Telecontrol protocols compatible with ISO Standards and ITU-T Recommendations; TASE.2 services and protocol

Telecontrol equipment and systems - Part 6: Telecontrol protocols compatible with ISO standards and ITU-T recommendations - Section 601: Functional profile for providing the connection-oriented transport service in end system connected via permanent acces to a packet switched data network

Telecontrol equipment and system - Part 6-701: Telecontrol protocols compatible with ISO standards and ITU-T recommendations - Functional profile for providing the TASE.1 application service in end systems

Telecontrol equipment and systems - Part 6-702: Telecontrol protocols compatible with ISO standards and ITU-T recommendations - Functional profile for providing the TASE.2 application service in end systems

Telecontrol equipment and systems - Part 6-802: Telecontrol protocols compatible with ISO Standards and ITU-T Recommendations; TASE.2 Object models

Distribution automation using distribution line carrier systems - Part 4: Data communication protocols - Section 32: Data link layer - Logical link control (LLC)

Distribution automation using distribution line carrier systems - Part 4-511: Data communication protocols; Systems management; CIASE protocol

Distribution automation using distribution line carrier systems - Part 4-512: Data communication protocols; System management using profile 61334-5-1; Management Information Base (MIB)

Distribution automation using distribution line carrier systems - Part 5-1: Lower layer profiles; The spread frequency shift keying (S-FSK) profile

Functional safety of electrical/electronic/programmable electronic safety-related systems - Part 1: General requirements

Functional safety of electrical/electronic/programmable electronic safety-related systems - Part 2: Requirements for electrical/electronic/programmable electronic safety-related systems

Functional safety of electrical/electronic/programmable electronic safety-related systems - Part 3: Software requirements

Functional safety of electrical/electronic/programmable electronic safety-related systems - Part 4: Definitions and abbreviations

Functional safety of electrical/electronic/programmable electronic safety related systems - Part 5: Examples of methods for the determination of safety integrity levels

Functional safety of electrical/electronic/programmable electronic safety-related systems - Part 6: Guidelines on the application of IEC 61508-2 and IEC 61508-3

Functional safety of electrical/electronic/programmable electronic safety-related systems - Part 7: Overview of techniques and measures

Communication networks and systems in substations - Part 3: General requirements

Communication networks and systems for power utility automation - Part 6: Configuration description language for communication in electrical substations related to IEDs

Communication networks and systems for power utility automation - Part 7-1: Basic communication structure - Principles and models

Communication networks and systems for power utility automation - Part 7-2: Basic information and communication structure - Abstract communication service interface (ACSI)

Communication networks and systems for power utility automation - Part 7-3: Basic communication structure - Common data classes

Communication networks and systems for power utility automation - Part 7-4: Basic communication structure - Compatible logical node classes and data object classes

Communication networks and systems for power utility automation - Part 7-410: Basic communication structure - Hydroelectric power plants - Communication for monitoring and control

Communication networks and systems for power utility automation - Part 7-420: Basic communication structure - Distributed energy resources logical nodes

Communication networks and systems for power utility automation - Part 8-1: Specific communication service mapping (SCSM); Mappings to MMS (ISO 9506-1 and ISO 9506-2) and to ISO/IEC 8802-3

Communication networks and systems for power utility automation - Part 9-2: Specific communication service mapping (SCSM) - Sampled values over ISO/IEC 8802-3

Application integration at electric utilities - System interfaces for distribution management - Part 1: Interface architecture and general recommendations

Application integration at electric utilities - System interfaces for distribution management - Part 100: Implementation Profiles

Application integration at electric utilities - System interfaces for distribution management - Part 11: Common information model (CIM) extensions for distribution

Application integration at electric utilities - System interfaces for distribution management - Part 13: CIM RDF Model exchange format for distribution

Application integration at electric utilities - System interfaces for distribution management - Part 2: Glossary

Application integration at electric utilities - System interfaces for distribution management - Part 3: Interface for network operations

Application integration at electric utilities - System interfaces for distribution management - Part 4: Interfaces for records and asset management

Application integration at electric utilities - System interfaces for distribution management - Part 6: Interfaces for maintenance and construction

Application integration at electric utilities - System interfaces for distribution management - Part 8: Interface standard for customer support

Application integration at electric utilities - System interfaces for distribution management - Part 9: Interface for meter reading and control

Energy management system application program interface (EMS-API) - Part 1: Guidelines and general requirements

Energy management system application program interface (EMS-API) - Part 2: Glossary

Energy management system application program interface (EMS-API) - Part 301: Common information model (CIM) base

Energy management system application program interface (EMS-API) - Part 401: Component interface specification (CIS) framework

Energy management system application program interface (EMS-API) - Part 452: CIM model exchange specification

Energy Management System Application Program Interface (EMS-API) - Part 453: Diagram layout profile

Energy management system application program interface (EMS-API) - Part 456: Solved power system state profiles

Energy management system application program interface (EMS-API) - Part 458: Common Information Model (CIM) extension to generation

Energy management system application program interface (EMS-API) - Part 501: Common Information Model Resource Description Framework (CIM RDF) schema

Energy management system application program interface (EMS-API) - Part 502-8: Web services profile for 61970-4 Generic Services

Energy Management System Application Program Interface (EMS-API) - Part 552: CIM XML Model Exchange Format

Electricity metering data exchange - The DLMS/COSEM suite - Part 1-0: Smart metering standardization framework

Data exchange for meter reading, tariff and load control - Part 8-20: RF Mesh Communication Profile

Electricity metering data exchange - The DLMS/COSEM suite - Part 3-1: Use of local area networks on twisted pair with carrier signalling

Electricity metering - Data exchange for meter reading, tariff and load control - Part 42: Physical layer services and procedures for connection-oriented asynchronous data exchange

Electricity metering - Data exchange for meter reading, tariff and load control - Part 46: Data link layer using HDLC protocol

Electricity metering data exchange - The DLMS/COSEM suite - Part 4-7: DLMS/COSEM transport layer for IP networks

Electricity metering data exchange - The DLMS/COSEM suite - Part 5-3: DLMS/COSEM application layer

Electricity metering data exchange - The DLMS/COSEM suite - Part 6-1: Object Identification System (OBIS)

Electricity metering data exchange - The DLMS/COSEM suite - Part 5-3: DLMS/COSEM application layer

Electricity metering data exchange - The DLMS/COSEM suite - Part 7-6: The 3-layer, connection-oriented HDLC based communication profile

Electricity metering data exchange - The DLMS/COSEM suite - Part 8-3: The PLC S-FSK profile for neighbourhood networks

Electricity metering data exchange - The DLMS/COSEM SUITE - Part 8-6: DMT PLC profile for neighbourhood networks

Electricity metering data exchange - The DLMS/COSEM suite - Part 9-7: Communication profile for TCP-UDP/IP networks

Industrial communication networks - High availability automation networks - Part 1: General concepts and calculation methods

Industrial communication networks - High availability automation networks - Part 3: Parallel Redundancy Protocol (PRP) and High availability Seamless Redundancy (HSR)

Industrial communication networks - Network and system security - Part 1-1: Terminology, concepts and models

Industrial communication networks - Network and system security - Part 2-1: Establishing an industrial automation and control system security program

Security for industrial automation and control systems - Part 2-3: Patch management in the IACS environment

OPC unified architecture - Part 1: Overview and concepts

OPC Unified Architecture - Part 10: Programs

OPC unified architecture - Part 2: Security model

OPC Unified Architecture - Part 3: Address space model

OPC Unified architecture - Part 4: Services

OPC Unified Architecture - Part 5: Information model

Security for industrial automation and control systems - Part 2-4: Security program requirements for IACS service providers

Security for industrial process measurement and control - Network and system security

Industrial communication networks - Network and system security - Part 3-1: Security technologies for industrial automation and control systems

Industrial communication networks - Network and system security - Part 3-3: System security requirements and security levels

OPC Unified Architecture - Part 6: Mappings

OPC Unified Architecture - Part 7: Profiles

OPC Unified Architecture - Part 8: Data Access

OPC Unified Architecture - Part 9: Alarms and Conditions

General requirements for home and building electronic systems (HBES) and building automation and control systems (BACS) - Part 11: Smart Metering - Application Specifications - Simple external consumer display-

General requirements for Home and Building Electronic Systems (HBES) and Building Automation and Control Systems (BACS) - Part 12: Smart grid - Application specification - Interface and framework for customer

Functional reference architecture for communications in smart meteringsystems

Information security management guidelines for process control systems used in the energy utility industry on the basis of ISO/IEC 27002

Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Security Design Guide; Method for application of Common Criteria to ETSI deliverables

Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN) - Design Guide - Application of security countermeasures to service capabilities

Global System for Mobile communications (GSM);Harmonized EN for Base Station Equipment covering the essential requirements of article 3.2 of the R&TTE Directive

Global System for Mobile communications (GSM); Mobile Stations (MS) equipment; Harmonised Standard covering the essential requirements of article 3.2 of Directive 2014/53/EU

IMT cellular networks; Harmonised Standard covering the essential requirements of article 3.2 of the Directive 2014/53/EU; Part 1: Introduction and common requirements

Network Based Short Range Devices (SRD); Radio equipment to be used in the 870 MHz to 876 MHz frequency range with power levels ranging up to 500 mW; Harmonised Standard covering the essential requirements of article 3.2 of the Directive 2014/53/EU

Electromagnetic compatibility and Radio spectrum Matters (ERM); Network Based Short Range Devices (SRD); Radio equipment to be used in the 870 MHz to 876 MHz frequency range with power levels ranging up to 500 mW; Part 1:Technical characteristics and test methods

Electromagnetic compatibility and Radio spectrum Matters (ERM); Network Based Short Range Devices (SRD); Radio equipment to be used in the 870 MHz to 876 MHz frequency range with power levels ranging up to 500 mW; Part 2: Harmonized EN covering the essential requirements of article 3.2 of the R&TTE Directive

Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN) - Security Design Guide - Method and proforma for defining Protection Profiles

Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN) - Security Design Guide - Method and proforma for defining Security Targets

Security Techniques Advisory Group (STAG) - Baseline security standards - Features and mechanisms

Security Techniques Advisory Group (STAG) - Security requirements capture

Security Techniques Advisory Group (STAG) - A directory of security features in ETSI standards

Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN) - Security analysis of IPv6 application in telecommunications standards

Electronic Signatures and Infrastructures (ESI) - Guidance on TS 101456 (Policy Requirements for certification authorities issuing qualified certificates)

Best Practices for handling electronic signatures and signed data for digital accounting

Machine to Machine Communications (M2M) - Threat analysis and counter measures to M2M service layer

Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN) - Analysis of security mechanisms for customer networks connected to TISPAN NGN R2

Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN) - TISPAN NGN Security (NGN SEC) - Threat, Vulnerability and Risk Analysis

Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN) - NGN Security - Report and recommendations on compliance to the data retention directive for NGN-R2

Digital cellular telecommunications system (Phase 2+) - Security aspects (GSM 02.09 version 8.0.1 Release 1999)

Electronic Signatures and Infrastructures (ESI) - Policy requirements for certification authorities issuing qualified certificates

Electronic Signatures and Infrastructures (ESI) - Policy requirements for certification authorities issuing public key certificates

Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN) - Methods and protocols - Part 1: Method and proforma for Threat, Risk, Vulnerability Analysis

Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN) - Methods and protocols - Part 2: Protocol Framework Definition - Security Counter Measures

Smart Cards - Secured packet structure for UICC based applications (Release 9)

Smart Cards - Remote APDU structure for UICC based applications

Smart Cards - Secure channel between a UICC and an end-point terminal (Release 11)

Electronic Signatures and Infrastructures (ESI) - Policy requirements for trust service providers signing and/or storing data objects

Machine-to-Machine communications (M2M) - M2M service requirements

Smart Metering Use Cases

Machine-to-Machine communications (M2M) - Functional architecture

Machine-to-Machine communications (M2M) - mIa, dIa and mId interfaces

Machine-to-Machine communications (M2M);. Applicability of M2M architecture to Smart Grid Networks

Machine-to-Machine communications (M2M); Interworking between the M2M Architecture and M2M Area Network technologies

Machine-to-Machine Communications (M2M);. Study on Semantic support for M2M Data

Smart Cards; UICC-Terminal interface; Physical and logical characteristics (Release 8)

Smart Cards; UICC Application Programming Interface and Loader Requirements; Service description (Release 11)

Smart Cards; UICC Application Programming Interface (UICC API) for Java Card ™ (Release 9)

Smart Cards; Smart Card Platform Requirements Stage 1 (Release 11)

Smart Cards; UICC Security Service Module (USSM); Stage 2 (Release 7)

Smart Cards; Machine to Machine UICC; Physical and logical characteristics (Release 9)

Machine-to-Machine communications (M2M); OMA DM compatible Management Objects for ETSI M2M

Machine-to-Machine communications (M2M); BBF TR-069 compatible Management Objects for ETSI M2M

Machine-to-Machine communications (M2M); Interoperability Test Specification for CoAP Binding of ETSI M2M Primitives

Smart Cards; Embedded UICC; Requirements Specification (Release 13)

Digital cellular telecommunications system (Phase 2+) - Universal Mobile Telecommunications System (UMTS) - LTE - Service requirements for Machine-Type Communications (MTC) - Stage 1 (3GPP TS 22.368 version 12.4.0 Release 12)

LTE; General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access (3GPP TS 23.401 version 11.3.0 Release 11)

Universal Mobile Telecommunications System (UMTS) - LTE - Architecture enhancements for non-3GPP accesses (3GPP TS 23.402 version 9.3.0 Release 9)

Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); LTE; Architecture enhancements to facilitate communications with packet data networks and applications (3GPP TS 23.682 version 13.4.0 Release 13)

Universal Mobile Telecommunications System (UMTS); LTE; Tsp interface protocol between the MTC Interworking Function (MTC-IWF) and Service Capability Server (SCS) (3GPP TS 29.368 version 12.4.0 Release 12)

Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; 3G security; Access security for IP-based services (3GPP TS 33.203 version 8.8.0 Release 8)

Digital cellular telecommunications system (Phase 2+) - Universal Mobile Telecommunications System (UMTS) - LTE - 3G security - Network Domain Security (NDS) - IP network layer security (3GPP TS 33.210 version 13.0.0 Release 13)

Universal Mobile Telecommunications System (UMTS) - LTE - 3G security - Wireless Local Area Network (WLAN) interworking security (3GPP TS 33.234 version 13.1.0 Release 13)

Universal Mobile Telecommunications System (UMTS);LTE; Network Domain Security (NDS); Authentication Framework (AF) (3GPP TS 33.310 version 10.4.0 Release 10)

LTE - Evolved Universal Terrestrial Radio Access (E-UTRA) - LTE physical layer - General description (3GPP TS 36.201 version 13.2.0 Release 13)

LTE - Evolved Universal Terrestrial Radio Access (E-UTRA) - Physical channels and modulation (3GPP TS 36.211 version 12.7.0 Release 12)

LTE - Evolved Universal Terrestrial Radio Access (E-UTRA) - Multiplexing and channel coding (3GPP TS 36.212 version 12.2.0 Release 12)

LTE - Evolved Universal Terrestrial Radio Access (E-UTRA) - Physical layer procedures (3GPP TS 36.213 version 13.2.0 Release 13)

LTE - Evolved Universal Terrestrial Radio Access (E-UTRA) - Physical layer - Measurements (3GPP TS 36.214 version 13.2.0 Release 13)

Universal Mobile Telecommunications System (UMTS) - Evolved Universal Terrestrial Radio Access (E-UTRA) - Physical layer for relaying operation (3GPP TS 36.216 version 12.0.0 Release 12)

Function blocks - Part 1: Architecture

Function blocks - Part 2: Software tool requirements

Function blocks - Part 4: Rules for compliance profiles

Batch control - Part 1: Models and terminology

Batch control - Part 4: Batch production records

LTE - Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN) - Overall description - Stage 2 (3GPP TS 36.300 version 13.2.0 Release 13)

Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN) - NGN SECurity (SEC) - Requirements

Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN) - NGN Security - Security Architecture

Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN) - NGN Security - Identity Protection (Protection Profile)

Batch control - Part 2: Data structures and guidelines for languages

Batch control - Part 3: General and site recipe models and representation

Communication networks and systems for power utility automation - ALL PARTS

Framework for energy market communications - Part 301: Common Information Model (CIM) extensions for markets

Framework for energy market communications - Part 351: CIM European market model exchange profile

Framework for energy market communications - Part 450: Profile and context modelling rules

Framework for energy market communications - Part 451-1: Acknowledgement business process and contextual model for CIM European market

Framework for energy market communications - Part 451-3: Transmission capacity allocation business process (explicit or implicit auction) and contextual models for European market

Framework for energy market communications - Part 451-3: Transmission capacity allocation business process (explicit or implicit auction) and contextual models for European market

Framework for energy market communications - Part 451-4: Settlement and reconciliation business process, contextual and assembly models for European market

Framework for energy market communications - Part 451-5: Problem statement and status request business processes, contextual and assembly models for European market

Framework for energy market communications - Part 451-6: Publication of information on market, contextual and assembly models for European style market

Framework for energy market communications - Part 503: Market data exchanges guidelines for the IEC 62325-351 profile

Framework for energy market communications - Part 504: Utilization of web services for electronic data interchanges on the European energy market for electricity

Power systems management and associated information exchange - Data and communications security

Power systems management and associated information exchange - Data and communications security - Part 1: Communication network and system security - Introduction to security issues

Power systems management and associated information exchange - Data and communications security - Part 10: Security architecture guidelines

Power systems management and associated information exchange - Data and communications security - Part 11: Security for XML Files

Power systems management and associated information exchange - Data and communications security - Part 2: Glossary of terms

Power systems management and associated information exchange - Data and communications security - Part 3: Communication network and system security - Profiles including TCP/IP

Power systems management and associated information exchange - Data and communication security - Part 4: Profiles including MMS

Power systems management and associated information exchange - Data and communications security - Part 5: Security for IEC 60870-5 and derivatives

Power systems management and associated information exchange - Data and communication security - Part 6: Security for IEC 61850

Power systems management and associated information exchange - Data and communication security - Part 7: Network and system management (NSM) data object models

Power systems management and associated information exchange - Data and communications security - Part 8: Role-based access control

Power systems management and associated information exchange - Data and communications security - Part 12: Resilience and security recommendations for power systems with distributed energy resources (DER) cyber-physical systems

Power systems management and associated information exchange - Data and communications security - Part 13: Guidelines on security topics to be covered in standards and specifications

Power systems management and associated information exchange - Part 1: Reference architecture

Power systems management and associated information exchange - Part 200: Guidelines for migration from Internet Protocol version 4 (IPv4) to Internet Protocol version 6 (IPv6)

Power systems management and associated information exchange - Interoperability in the long term - Part 100: CIM profiles to XML schema mapping

Power systems management and associated information exchange - Interoperability in the long term - Part 2: End to end quality codes for supervisory control and data acquisition (SCADA)

Industrial communication networks - Network and system security - Part 3-3: System security requirements and security levels

Road vehicles - Vehicle to grid communication interface - Part 1: General information and use-case definition

Road vehicles - Vehicle to grid communication interface - Part 2: Network and application protocol requirements

Road vehicles - Vehicle to grid Communication Interface - Part 3: Physical and data link layer requirements

Road vehicles - Vehicle to grid communication interface - Part 4: Network and application protocol conformance test

Building automation and control systems (BACS)

Road vehicles - Vehicle to grid communication interface - Part 5: Physical layer and data link layer conformance test

Road vehicles - Vehicle to grid communication interface - Part 6: General information and use-case definition for wireless communication

Road vehicles - Vehicle to grid communication interface - Part 7: Network and application protocol requirements for wireless communication

Road vehicles - Vehicle to grid communication interface - Part 8: Physical layer and data link layer requirements for wireless communication

Information technology -- Terminology for the Home Electronic System (HES)



Building automation and control systems -- Part 4: Control applications

Information technology -- Terminology for intelligent homes

Building automation and control systems (BACS) -- Part 5: Data communication protocol

Building automation and control systems (BACS) -- Part 6: Data communication conformance testing

Geographic information - Web Feature Service

Information technology -- Security techniques -- Information security management guidelines based on ISO/IEC 27002 for process control systems specific to the energy utility industry

Information technology -- Security techniques -- Security requirements for cryptographic modules

Data elements and interchange formats - Information interchange - Representation of dates and times

Information technology - Telecommunications and information exchange between systems - Powerline communication (PLC) - High speed PLC medium access control (MAC) and physical layer (PHY) - Part 1: General requirements

Information technology - Security techniques - Information security management systems - Requirements

Information technology - Security techniques - Code of practice for information security management

Information technology -- Security techniques – Sector-specific application of ISO/IEC 27001

Information technology -- Security techniques – Privacy capability assessment model

Information technology - Open Systems Interconnection - Basic reference model: The basic model

Standard for a Precision Clock Synchronization Protocol for Networked Measurement and Control Systems

Abstract

Com

pone

nt

Com

mun

icati

on

Info

rmati

on

Func

tion

Busi

ness

X

X

X

X

X

X

X

X

X

X

The present document identifies the 3GPP system specifications for Release 10. The specifications and reports of 3GPP Release 10 have a major version number 10 (i.e. 10.x.y). The listed Specifications are required to build a system based on UTRAN radio technology. The present document identifies the 3GPP system specifications for Release 11. The specifications and reports of 3GPP Release 11 have a major version number 11 (i.e. 11.x.y). The listed Specifications are required to build a system based on GERAN radio technology.

EN 13321-1 Open data communication in building automation, controls and building management - Home and building electronic system - Part 1: Product and system requirements - This European Standard specifies, as for Home or Building Electronic Systems (HBES) for the domain of Building Automation and Control System Application and Building Management (BACS), common rules for a class of multi-application bus systems where the functions are decentralised and linked through a common communication process. This European Standard sets the basic requirements for products and systems. The requirements may also apply to the distributed functions of any equipment connected in a home or building control system if no specific standard exists for this equipment or system. Due to its reference to the EN 50090 series, this European Standard sets requirements for the BACS area in relation to Architecture and Hardware and Application and Communication of systems based on HBES amongst other areas, and specifies the basic requirements for interoperability (between products and systems). Aspects such as environmental conditions/external influences, electrical safety, EMC, etc. also used to be covered by EN 50090-2-2, which will be superseded by the now available EN 50491 series. The latter European Standards series was jointly developed by CENELEC/TC 205 and CEN/TC 247 and will in the future also include aspects like functional safety in normal use (now contained in the EN 50090-2-3). The EN 50491 series applies, together with the relevant product standard for devices, if applicable.

EN 13321-2 Open Data Communication in Building Automation, Controls and Building Management - Home and Building Electronic Systems - Part 2: KNXnet/IP Communication - This European Standard defines the integration of KNX protocol implementations on top of Internet Protocol (IP) networks, called KNXnet/IP. It describes a standard protocol for KNX devices connected to an IP network, called KNXnet/IP devices. The IP network acts as a fast (compared to KNX transmission speed) backbone in KNX installations. Widespread deployment of data networks using the Internet Protocol (IP) presents an opportunity to expand building control communication beyond the local KNX control bus, providing: - remote configuration; - remote operation (including control and annunciation); - fast interface from LAN to KNX and vice versa; - WAN connection between KNX systems (where an installed KNX system is at least one line). A KNXnet/IP system contains at least these elements: - one EIB line with up to 64 (255) EIB devices; OR one KNX segment (KNX-TP1, KNX-TP0, KNX-RF, KNX-PL110, KNX-PL132); - a KNX-to-IP network connection device (called KNXnet/IP server); and typically additional - software for remote functions residing on e.g. a workstation (may be data base application, BACnet Building Management System, browser, etc.). Figure 1 shows a typical scenario where a KNXnet/IP client (e.g. running ETS) accesses multiple KNX installed systems or KNX subnetworks via an IP network. The KNXnet/IP client may access one or more KNXnet/IP servers at a time. For subnetwork, routing server-to-server communication is possible.

EN 13757-1 Communication systems for meters - Part 1: Data exchange - This European Standard specifies data exchange and communications for meters and remote reading of meters in a generic way. This European Standard establishes a protocol specification for the Application Layer for meters and establishes several protocols for meter communications which may be applied depending on the application being fulfilled. NOTE Electricity meters are not covered by this standard, as the standardization of remote readout of electricity meters is a task for CENELEC.

EN 13757-2 Communication systems for and remote reading of meters - Part 2: Physical and link layer - This European Standard covers the physical and link layer parameters of baseband communication over twisted pair (M Bus) for meter communication systems. It is especially applicable to heat meters, heat cost allocators, water meters and gas meters. NOTE It is usable also for other meters (like electricity meters) and for sensors and actuators. For generic descriptions concerning communication systems for meters and remote reading of meters see EN 13757-1.EN 13757-3 Communication systems for and remote reading of meters - Part 3: Dedicated application layer - This European Standard applies to communication systems for meters and remote reading of meters.EN 13757-4 Communication systems for meters and remote reading of meters - Part 4: Wireless meter readout (Radio meter reading for operation in SRD bands) - This European Standard specifies the requirements of parameters for the physical and the link layer for systems using radio to read remote meters. The primary focus is to use the Short Range Device (SRD) unlicensed telemetry bands. The standard encompasses systems for walk-by, drive-by and fixed installations. As a broad definition, this European Standard can be applied to various application layers.

EN 13757-5 Communication systems for meters - Part 5: Wireless M-Bus relaying - This European Standard specifies the protocols to use when performing relaying in wireless meter readout networks. This European Standard is an extension to wireless meter readout specified in EN 13757-4. It supports the routing of modes P and Q, and simple single-hop repeating of modes S, T, C, F and N. The main use of this standard is to support simple retransmission as well as routed wireless networks for the readout of meters. NOTE Electricity meters are not covered by this standard, as the standardisation of remote readout of electricity meters is a task for IEC/CENELEC.

EN 13757-6 Communication systems for meters - Part 6: Local Bus - This European Standard specifies the physical layer parameters of a local meter readout system (Local Bus) for the communication with and the readout of a single meter or a small cluster of meters via a single battery powered readout device (master) which can be connected temporarily or stationary for the communication directly to a meter (i.e. local readout) or via a fixed wiring or a small bus (i.e. remote readout). For generic descriptions concerning communication systems for meters and remote reading of meters, refer to EN 13757-1.

X

X

X

X

X

X

X

X

X

This specification applies to a communication protocol for networked control systems. The protocol provides peer-to-peer communication for networked control and is suitable for implementing both peer-to-peer and master-slave control strategies. This specification describes services in layers 2 - 7.

This European standard specifies the control network protocol (CNP) free-topology twisted-pair channel and serves as a companion document to CNP, part 1. The channel supports communication at 78.125 kbps between multiple nodes, each of which consists of a transceiver, a protocol processor, an application processor, a power supply, and application electronics. This standard covers the complete physical layer.

This European Standard specifies all the information necessary to facilitate the exchange of data and control information over the power line medium.This European Standard establishes a minimal set of rules for compliance.

This European Standard specifies the transporting of Control Network Protocol (CNP) packets over Internet Protocol (IP) networks using a tunnelling mechanism wherein the CNP packets are encapsulated within the IP packets. It applies to both CNP nodes and CNP routers.

EN 14908-5 Open Data Communication in Building Automation, Controls and Building Management Implementation Guideline - Control Network Protocol - Part 5: Implementation - This specification contains all the information necessary to facilitate the exchange of data and control information in an interoperable fashion using EN 14908-1 and its associated data-transport media specifications. This specification establishes a minimal set of rules for compliance. It does not rule-out extended services to be provided, given that the rules are adhered-to within the system. It is the intention of the standard to permit extended services to coexist and defines the bounds in which those services function, including the format for internal device-documentation of those services. Services outside purvey of this specification so long as they are adherents of the system are permitted but will not necessarily be interoperable with any other devices and shall not be essential for the functioning of the device. Certain aspects of this standard are defined in other documents. These documents are referenced where relevant. In the case where a referenced standard conflicts with this document, this document will prevail.

EN 14908-6 Open Data Communication in Building Automation, Controls and Building Management - Control Network Protocol - Part 6: Application elements - This European Standard provides mechanisms through which various vendors of building automation, control, and building management systems may exchange information in a standardized way. This document provides specifications for the Application Elements of Control Network Protocol packets as follows: - definitions of standardized packet (network-variable) data types; - definitions of device-interface files; - definitions of standardized configuration-property types; - definitions of standardized enumeration types; - definitions of standardized functional profiles; - definition of the standardized method of file transfer between devices. The purpose of this specification is to ensure interoperability between various CNP implementations. This document contains all the information necessary to read and interpret the format of data and control information that is used by EN 14908-5. It also defines the device interface for a device as specified, which is necessary to exchange data between various devices from different manufacturers.EN 50090-1 Home and Building Electronic Systems (HBES) - Part 1: Standardization structure -

The document deals with the standardization of a bus system for Home and Building Electronic Systems (HBES). It introduces to the underlying application structure.

This part of EN 50090 specifies the structure and functioning of servers for the objects which form the interface between the application layer and the application and management.

X

X

X

X

X

X

X

X

X

X

This European Standard gives general guidelines and recommendations to ensure interworking between HBES devices made by different manufacturers.

This part of the EN 50090 specifies the services and protocol of the application layer for usage in Home and Building Electronic Systems. It provides the services and the interface to the user process as defined in EN 50090-3-2.

This part of the EN 50090 specifies the services and protocol in a physical layer independent way for the data link layer and for the network layer and the transport layer for usage in Home and Building Electronic Systems.EN 50090-4-3 ed. 2 Home and Building Electronic Systems (HBES) - Part 4-3: Media independent layers - Communication over IP - This European Standard concentrates on control applications for Home and Building HBES Open Communication System and covers any combination of electronic devices linked via a digital transmission network. Home and Building Electronic System as provided by the HBES Open Communication System is a specialized form of automated, decentralised and distributed process control, dedicated to the needs of home and building applications. This European Standard defines the mandatory and optional requirements for the medium independent communication over IP for HBES products and systems, a multi-application bus system where the functions are decentralised, distributed and linked through a common communication process. This European Standard is used as a product family standard. It is not intended to be used as a stand-alone standard. Other parts from the EN 50090 series may apply.

EN 50090-5-1 Home and Building Electronic Systems (HBES) - Part 5-1: Media and media dependent layers - Power line for HBES Class 1 - This European Standard defines the mandatory and optional requirements for the medium specific physical and data link layer of power line Class 1 in its two variations PL110 and PL132. Data link layer interface and general definitions, which are medium independent, are given in EN 50090 4-1.

EN 50090-5-2 Home and Building Electronic Systems (HBES) - Part 5-2: Media and media dependent layers - Network based on HBES Class 1, Twisted Pair -

EN 50090-5-3 ed. 2 Home and Building Electronic Systems (HBES) - Part 5 - 3: Media and media dependent layers - Radio Frequency for HBES Class 1 - This European Standard defines the mandatory and optional requirements for the medium specific Physical and Data Link Layer of HBES Radio Frequency. Data Link Layer interfaces and general definitions that are medium independent are given in EN 50090 4 1. This European standard defines the requirements for HBES RF Ready and HBES RF Multi devices. HBES RF Ready is a single RF channel system. HBES RF Multi is an RF multichannel evolution of HBES RF Ready system with 2 additional RF channels for fast reaction time products and 2 RF channels for slow reaction time products. HBES RF Multi, specified below provides the following features: - more reliability in Frame transmissions in presence of interferers. - more efficiency when more HBES RF products are installed at the same location. - mixing of permanent and non-permanent receiving products. - mixing of fast and slow reaction time devices. - Listen Before Talk. Fast RF channels are mainly intended to be used with human controlled applications like for example lights, shutters… Slow RF channels are mainly intended to be used with non-permanent receivers for automatic applications like sensors (smoke, temperature, wind, etc.), heating control, etc. Compatibility issues with products in compliance with the former HBES RF specification (HBES RF 1.1) and the new versions are considered in Clause 7 at the end of this document.

EN 50090-7-1 Home and Building Electronic Systems (HBES) - Part 7-1: System management - Management procedures - This european standard establishes general principles for network and device management shared by and independent of the installation mode. The goal is to standardize the interaction, between a management client and a management server, that shall lead to the successful configuration of the devices.

EN 50090-8 Home and Building Electronic Systems (HBES) - Part 8: Conformity assessment of productsCISPR 22:2008 applies to information technology equipment (ITE). Procedures are given for the measurement of the levels of spurious signals generated by the ITE and limits are specified for the frequency range 9 kHz to 400 GHz for both class A and class B equipment. No measurements need be performed at frequencies where no limits are specified. The intention of this publication is to establish uniform requirements for the radio disturbance level of the equipment contained in the scope, to fix limits of disturbance, to describe methods of measurement and to standardize operating conditions and interpretation of results. This sixth edition of CISPR 22 cancels and replaces the fifth edition published in 2005, its Amendment 1 (2005) and Amendment 2 (2006). This edition constitutes a minor revision. NEW! CISPR 22:2008 is also available as IEC Standards+ CISPR 22:2008 which contains the International Standard and its Redline version, showing all changes of the technical content compared to the previous edition.

X

X

X

X

X

X

X

X

X

Defines the immunity test requirements for information technology equipment (ITE, as defined in CISPR 22) in relation to continuous and transient, conducted and radiated disturbances, including electrostatic discharges (ESD). Procedures are defined for the measurement of ITE and limits are specified which are developed for ITE and within the frequency range from 0 Hz to 400GHz.This publication establishes requirements which will provide an adequate level of intrinsic immunity so that the equipment will operate as intended in its environment. The test requirements are specified for each port considered.

It specifies standard link transmission prodecures suitable for data transmission within telecontrol systems. The defined procedures are composed of dialog elements, with each element presented by a transmission frame.

The document applies to telecontrol equipment and systems with coded bit serial data transmission for monitoring and controlling geographically widespread processes. It specifies rules for structuring application data units in transmission frames of telecontrol systems.

The document applies to telecontrol equipment and systems with coded bit serial data transmission for monitoring and controlling geographically widespread processes. It specifies rules for defining information elements and presents a set of information elements, in particular digital and analog process variables, that are frequently used in telecontrol applications.

The document applies to telecontrol equipment and systems with coded bit serial data transmission for monitoring and controlling geographically widespread processes. It defines basic application functions that perform standard procedures for telecontrol systems, i.e. application procedures that reside beyond layer 7 (application layer) of the OSI basic reference model for open communication systems.

The aim of part 6 of the "Telecontrol Equipment and Systems" series is the standardization of Functional Profiles for electric power systems. These FPs are to provide the means for specifying complete, coherent, working systems for end-to-end communication and interworking.

Particular items are given for ISO and ITU-T compatible protocols of telecontrol equipment and systems and the use of standards which are related to layers 1 through 4 of the ISO reference model.

The document defines the services provided by e teleconrol specific application-service-element - the Telecontrol Application Service Element No. 1 (TASE.1) - for exchange of process data in telecontrol systems.

The document specifies the protocol for the services provided by an application-service-element - The Telecontrol Application Service Element No. 1 (TASE.1) - to support the exchange of process data between telecontrol systems.

X

X

X

X

X

X

X

The document specifies a method of exchanging time-critical control center data through wide- and local-area networks using a full ISO compliant protocol stack, by means of the Telecontrol Application Service Element No. 2 (TASE.2). It contains provisions for supporting both centralized and distributed architectures. The standard includes the exchange of real-time data indications, control operations, time series data, scheduling and accounting information, remote program control, and event notification.

The functionale profile for ISO and ITU-T compatible protocols of telecontrol equipment and systems defines the provision for the OSI connection mode transport service between an end system ("Reference End System") which uses a permanent analog or digital circuit to access a packet switched data network (PSDN) and another end system ("Compatible End System") which is accessible, by permanent or switched methods, either directly from the same PSDN, or indirectly through the provided OSI-connection-mode network service.

The document deals with the application profile to be used with the Telecontrol Application Service Element No. 1 (TASE.1). The functional profile defines the provision of the TASE.1 communication services between two Control Center End-systems. It is supported by the transport services implemented in accordance with transport profiles defined for the type of network that interconnect the control center end-systems. Largely based on standards and profiles, it is defined which services and functional units are required to support the services of TASE.1 from the layers 5 to 7.

The document is an application-class profile for the Telecontrol Application Service Element (TASE.2) providing inter-control center communications to control center applications. It refines the application layer protocol to meet interoperability requirements and specifies requirements on the presentation and session layers support for TASE.2.

The document proposes object models from which to define object instances and which represents objects for transfer through wide- and local-area networks by means of a Telecontrol Application Service Element No. 2 (TASE.2).

The document covers the services required of, or by, the DCP Logical Link Control (LLC) sublayer entity at the logical interfaces with the application layer and the MAC sublayer.

Distribution automation using distribution line carrier systems - Part 4-511: Data communication protocols - Systems management - CIASE protocol

X

X

x

x

x x

x

x

x x

x x

This standard provides a selection of DLMS objects gathered together in a so-called Management Information Base (MIB). This selection corresponds to a set of variables that are used for the management of the PLAN (Power Line Automation Network) profile. Specifies the Management Information Base (MIB), which is used for the management of the communication profile defined by the following standards: IEC 61334-5-1, IEC 61334-4-32, IEC 61334-4-42, and IEC 61334-4-41.

Describes the requirements of S-FSK (frequency shift keying modulation) in conjunction with the services provided by the physical layer entity and the MAC sublayer. The transmission medium is assumed to be the distribution network on both MV or LV level. To be used in conjunction with IEC 61334-4-32.IEC 61508-1:2010 covers those aspects to be considered when electrical/electronic/programmable electronic (E/E/PE) systems are used to carry out safety functions. A major objective of this standard is to facilitate the development of product and application sector international standards by the technical committees responsible for the product or application sector. This will allow all the relevant factors, associated with the product or application, to be fully taken into account and thereby meet the specific needs of users of the product and the application sector. A second objective of this standard is to enable the development of E/E/PE safety-related systems where product or application sector international standards do not exist. This second edition cancels and replaces the first edition published in 1998. This edition constitutes a technical revision. It has been subject to a thorough review and incorporates many comments received at the various revision stages. It has the status of a basic safety publication according to IEC Guide 104.

IEC 61508-2:2010 applies to any safety-related system, as defined by IEC 61508-1, that contains at least:- one electrical, electronic or programmable electronic element;- applies to all elements within an E/E/PE safety-related system;- specifies how to refine the E/E/PE system safety requirements specification, developed in accordance with IEC 61508-1, into the E/E/PE system design requirements specification;- specifies the requirements for activities that are to be applied during the design and manufacture of the E/E/PE safety-related systems except software, which is dealt with in IEC 61508-3.These requirements include the application of techniques and measures that:- are graded against the safety integrity level, for the avoidance of, and control of, faults and failures;- specifies the information necessary for carrying out the installation, commissioning and final safety validation of the E/E/PE safety-related system;- provides requirements for the preparation of information and procedures needed by the user for the operation and maintenance of the E/E/PE safety-related systems;- specifies requirements to be met by the organisation carrying out any modification of the E/E/PE safety-related systems.This second edition cancels and replaces the first edition published in 1998. This edition constitutes a technical revision. It has been subject to a thorough review and incorporates many comments received at the various revision stages. It has the status of a basic safety publication according to IEC Guide 104.

IEC 61508-3:2010 applies to any software forming part of a safety-related system or used to develop a safety-related system within the scope of IEC 61508-1 and IEC 61508-2; provides specific requirements applicable to support tools used to develop and configure a safety-related system within the scope of IEC 61508-1 and IEC 61508-2; requires that the software safety functions and software systematic capability are specified; establishes requirements for safety lifecycle phases and activities which shall be applied during the design and development of the safety-related software. These requirements include the application of measures and techniques, which are graded against the required systematic capability, for the avoidance of and control of faults and failures in the software; provides requirements for information relating to the software aspects of system safety validation to be passed to the organisation carrying out the E/E/PE system integration; provides requirements for the preparation of information and procedures concerning software needed by the user for the operation and maintenance of the E/E/PE safety-related system; provides requirements to be met by the organisation carrying out modifications to safety-related software; provides, in conjunction with IEC 61508-1 and IEC 61508-2, requirements for support tools such as development and design tools, language translators, testing and debugging tools, configuration management tools. This second edition cancels and replaces the first edition published in 1998. This edition constitutes a technical revision. It has been subject to a thorough review and incorporates many comments received at the various revision stages. It has the status of a basic safety publication according to IEC Guide 104.

IEC 61508-4:2010 contains the definitions and explanation of terms that are used in parts 1 to 7 of the IEC 61508 series of standards. The definitions are grouped under general headings so that related terms can be understood within the context of each other. However, it should be noted that these headings are not intended to add meaning to the definitions. This second edition cancels and replaces the first edition published in 1998. This edition constitutes a technical revision. It has been subject to a thorough review and incorporates many comments received at the various revision stages. It has the status of a basic safety publication according to IEC Guide 104.

IEC 61508-5:2010 provides information on the underlying concepts of risk and the relationship of risk to safety integrity (see Annex A); a number of methods that will enable the safety integrity levels for the E/E/PE safety-related systems to be determined (see Annexes C, D, E, F and G). The method selected will depend upon the application sector and the specific circumstances under consideration. Annexes C, D, E, F and G illustrate quantitative and qualitative approaches and have been simplified in order to illustrate the underlying principles. These annexes have been included to illustrate the general principles of a number of methods but do not provide a definitive account. Those intending to apply the methods indicated in these annexes should consult the source material referenced. This second edition cancels and replaces the first edition published in 1998. This edition constitutes a technical revision. It has been subject to a thorough review and incorporates many comments received at the various revision stages.

IEC 61508-6:2010 contains information and guidelines on IEC 61508-2 and IEC 61508 3. Annex A gives a brief overview of the requirements of IEC 61508-2 and IEC 61508-3 and sets out the functional steps in their application. Annex B gives an example technique for calculating the probabilities of hardware failure and should be read in conjunction with 7.4.3 and Annex C of IEC 61508-2 and Annex D. Annex C gives a worked example of calculating diagnostic coverage and should be read in conjunction with Annex C of IEC 61508-2. Annex D gives a methodology for quantifying the effect of hardware-related common cause failures on the probability of failure. Annex E gives worked examples of the application of the software safety integrity tables specified in Annex A of IEC 61508-3 for safety integrity levels 2 and 3. This second edition cancels and replaces the first edition published in 1998. This edition constitutes a technical revision. It has been subject to a thorough review and incorporates many comments received at the various revision stages.

IEC 61508-7:2010 contains an overview of various safety techniques and measures relevant to IEC 61508-2 and IEC 61508-3.The references should be considered as basic references to methods and tools or as examples, and may not represent the state of the art. This edition constitutes a technical revision. It has been subject to a thorough review and incorporates many comments received at the various revision stages.

X X

X

X X

X

X

X

X

X

This part of IEC 61850 defines the general requirements, mainly regarding construction, design and environmental conditions for utility communication and automation IEDs and systems in power plant and substation environments.IEC 61850-6:2009(E) specifies a file format for describing communication-related IED (Intelligent Electronic Device) configurations and IED parameters, communication system configurations, switch yard (function) structures, and the relations between them. The main purpose of this format is to exchange IED capability descriptions, and SA system descriptions between IED engineering tools and the system engineering tool(s) of different manufacturers in a compatible way. The main changes with respect to the previous edition are as follows:- functional extensions added based on changes in other Parts of IEC 61850, especially in IEC 61850-7-2 and IEC 61850-7-3;- functional extensions concerning the engineering process, especially for configuration data exchange between system configuration tools, added;- clarifications and corrections.

EC 61850-7-1:2011 introduces the modelling methods, communication principles, and information models that are used in the various parts of the IEC 61850-7 series. The purpose is to provide - from a conceptual point of view - assistance to understand the basic modelling concepts and description methods for:- substation-specific information models for power utility automation systems,- device functions used for power utility automation purposes, and- communication systems to provide interoperability within power utility facilities. Compared to the first edition, this second edition introduces:- the model for statistical and historical statistical data,- the concepts of proxies, gateways, LD hierarchy and LN inputs,- the model for time synchronisation,- the concepts behind different testing facilities,- the extended logging function. It also clarifies certain items.

IEC 61850-7-2:2010(E) applies to the ACSI communication for utility automation. The ACSI provides the following abstract communication service interfaces:- abstract interface describing communications between a client and a remote server;- and abstract interface for fast and reliable system-wide event distribution between an application in one device and many remote applications in different devices (publisher/sub-scriber) and for transmission of sampled measured values (publisher/subscriber).Major technical changes with regard to the previous edition are as follows:- data types not required have been removed,- service tracking for control blocks have been added,- security issues are solved by the IEC 62351 series,- service tracking for control blocks have been added,- the view concept will be according to the new work on role bases access (RBA),- security issues are solved by the IEC 62351 series.

IEC 61850-7-3:2010 is applicable to the description of device models and functions of substations and feeder equipment. It specifies constructed attribute classes and common data classes related to substation applications. In particular, it specifies common data classes for status information, common data classes for measured information, common data classes for control, common data classes for status settings, common data classes for analogue settings and attribute types used in these common data classes. This second edition defines new common data classes used for new standards defining object models for other domains based on IEC 61850 and for the representation of statistical and historical data.

IEC 61850-7-4:2010(E) specifies the information model of devices and functions generally related to common use regarding applications in systems for power utility automation. It also contains the information model of devices and function-related applications in substations. In particular, it specifies the compatible logical node names and data object names for communication between intelligent electronic devices (IED). This includes the relationship between logical nodes and data objects. Major technical changes with regard to the previous edition are as follows:- corrections and clarifications according to technical issues raised by the users' community; extensions for new logical nodes for the power quality domain;- extensions for the model for statistical and historical statistical data;- extensions regarding IEC 61850-90-1;- extensions for new logical nodes for monitoring functions according to IEC 62271;- new logical nodes from IEC 61850-7-410 and IEC 61850-7-420 of general interest.

IEC 61850-7-410:2012+A1:2015 specifies the additional common data classes, logical nodes and data objects required for the use of IEC 61850 in a hydropower plant. The main changes with respect to the previous edition are as follows:- the logical nodes in IEC 61850-7-410:2007 that were not specific to hydropower plants have been transferred to IEC 61850-7-4:2010;- the definitions of logical nodes in this edition of IEC 61850-7-410 have been updated;- most of the modelling examples and background information included in IEC 61850-7-410:2007 have been transferred to IEC/TR 61850-7-510.This new edition of IEC 61850-7-410 includes additional general-purpose logical nodes that were not included in IEC 61850-7-4:2010, but are required in order to represent the complete control and monitoring system of a hydropower plant. This consolidated version consists of the second edition (2012) and its amendment 1 (2015). Therefore, no need to order amendment in addition to this publication.EC 61850-7-420:2009(E) defines IEC 61850 information models to be used in the exchange of information with distributed energy resources (DER), which comprise dispersed generation devices and dispersed storage devices, including reciprocating engines, fuel cells, microturbines, photovoltaics, combined heat and power, and energy storage. Utilizes existing IEC 61850-7-4 logical nodes where possible, but also defines DER-specific logical nodes where needed.

X

X

X

X

X

X

IEC 61850-8-1:2011 specifies a method of exchanging time-critical and non-time-critical data through local-area networks by mapping ACSI to MMS and ISO/IEC 8802-3 frames. Defines a standardized method of using the ISO 9506 services to implement the exchange of data. For those ACSI services defined in IEC 61850-7-2 that are not mapped to MMS, this part defines additional protocols. It describes real utility devices with respect to their external visible data and behaviour using an object oriented approach. The objects are abstract in nature and may be used to a wide variety of applications. The use of this mapping goes far beyond the application in the utility communications. The main changes with respect to the previous edition are listed below:- the support of gigabit Ethernet,- the link layer redundancy,- the extension of the length of the object reference,- the extension of the reason for inclusion type for comprehensive logging,- the mapping of the tracking services,- a second mapping of the objectReference when used in the tracking services, or as linking,- the extension of the AdditionalCause enumeration,- the simulation of GOOSE telegram,- the so-called fixed-length encoded GOOSE,- the removal of the SCL Control Block.

Defines the Specific Communication Service Mapping for the transmission of sampled values according to the abstract specification in IEC 61850-7-2. The mapping is that of the abstract model on a mixed stack using direct access to an ISO/IEC 8802-3 link for the transmission of the samples in combination with IEC 61850-8-1.This publication is of core relevance for Smart Grid.IEC 61968-1:2012 is the first part in a series that, taken as a whole, define interfaces for the major elements of an interface architecture for distribution management. This International Standard identifies and establishes recommendations for standard interfaces based on an Interface Reference Model (IRM). Subsequent clauses of this standard are based on each interface identified in the IRM. This set of standards is limited to the definition of interfaces. They provide for interoperability among different computer systems, platforms, and languages. Methods and technologies used to implement functionality conforming to these interfaces are recommended in IEC 61968-100. This edition includes the following significant technical changes with respect to the previous one: - update of IRM table which has been out of date; - addition of missing Advanced Metering Infrastructure (AMI) related functions; - alignment with newly released IEC documents; - alignment with IEC 61968-100; update of annexes.IEC 61968-100:2013 specifies an implementation profile for the application of the other parts of IEC 61968 using common integration technologies, including JMS and web services. This International Standard also provides guidance with respect to the use of Enterprise Service Bus (ESB) technologies. This provides a means to derive interoperable implementations of IEC 61968-3 to IEC 61968-9. At the same time, this International Standard can be leveraged beyond information exchanges defined by IEC 61968, such as for the integration of market systems or general enterprise integration.IEC 61968-11:2013 specifies the distribution extensions of the common information model (CIM) specified in IEC 61970-301. It defines a standard set of extensions of common information model (CIM), which support message definitions in IEC 61968-3 to IEC 61968-9, IEC 61968-13 and IEC 61968-14. The scope of this standard is the information model that extends the base CIM for the needs of distribution networks, as well as for integration with enterprise-wide information systems typically used within electrical utilities. Major changes with respect to the first edition are summarized below: - Introduction of new classes to support flexible naming of identified objects. - Introduction of new classes to support single line diagrams exchange. - Consolidated transmission and distribution models for lines, transformers, switching, sensing and other auxiliary equipment.IEC 61968-13:2008(E) specifies the format and rules for exchanging modelling information based upon the Common Information Model ('CIM') and related to distribution network data. Allows the exchange of instance data in bulk. Thus, the imported network model data should be sufficient to allow performing network connectivity analysis, including network tracing, outage analysis, load flow calculations, etc. This standard could be used for synchronizing geographical information system databases with remote control system databases.

X X

X X

X X

X X

X X

X X

X

IEC/TS 61968-2:2011(E) identifies and explains terms and abbreviations used in the remaining parts of IEC 61968. This glossary, accompanying the IEC 61968 series, is the second part in the series that, taken as a whole, defines interfaces for the major elements of an interface architecture for distribution management systems (DMS). This second edition contains numerous new terms in support of IEC 61968-9, as well as revisions to terms found in the first edition.This publication is of core relevance for Smart Grid.

Specifies the information content of a set of message types that can be used to support many of the business functions related to network operations. Typical uses of the message types defined in this part include data acquisition by external systems, fault isolation, fault restoration, trouble management, maintenance of the plant, and the commissioning of the plant. This publication is of core relevance for Smart Grid.

This part of IEC 61968 specifies the information content of a set of message types that can be used to support many of the business functions related to records and asset management. Typical uses of the message types defined in this Part of IEC 61968 include network diagram edits and asset inspection. Message types defined in other Parts of IEC 61968 may be relevant to these use cases.

Application integration at electric utilities - System interfaces for distribution management - Part 6: Interfaces for maintenance and construction

IEC 61968-8:2015(E) specifies the information content of a set of message types that can be used to support many of the business functions related to customer support. Typical uses of the message types include service request, customer agreement, and trouble management. The purpose is to define a standard for the integration of customer support (CS), which would include customer service, trouble management and point of sale related components integrated with other systems and business functions within the scope of IEC 61968. The scope of this standard is the exchange of information between a customer support system and other systems within the utility enterprise.

IEC 61968-9:2013 specifies the information content of a set of message types that can be used to support many of the business functions related to meter reading and control. Typical uses of the message types include meter reading, controls, events, customer data synchronization and customer switching. The purpose of IEC 61968-9 is to define a standard for the integration of metering systems (MS), which includes traditional manual systems, and (one or two-way) automated meter reading (AMR) systems, and meter data management (MDM) systems with other enterprise systems and business functions within the scope of IEC 61968. The scope of IEC 61968-9 is the exchange of information between metering systems, MDM systems and other systems within the utility enterprise. This new edition includes the following significant technical changes with respect to the previous edition: - changes to and addition of new profiles to support PAN and UsagePoints; - extensions to support PAN devices generically as EndDevices; - extensions to the MeterReading model and profiles to support richer descriptions of metered quantities and to accommodate coincident readings.

Provides a glossary for the volume of work produced as part of the IEC 61970 series of publications. Supplies terms and abbreviations that are either specific to the series, or that require explanation because of the way that they are used.

X

X

X

X

X

X

Common Information Model (CIM) extension to generation X

X

Provides a glossary for the volume of work produced as part of the IEC 61970 series of publications. Supplies terms and abbreviations that are either specific to the series, or that require explanation because of the way that they are used. This publication is of core relevance for Smart Grid.

IEC 61970-301:2013 defines the Common Information Model (CIM), that is an abstract model representing all the major objects in an electric utility enterprise typically involved in utility operations. By providing a standard way of representing power system resources as object classes and attributes, along with their relationships, the CIM facilitates the integration of Energy Management System (EMS) applications developed independently by different vendors, between entire EMS systems developed independently, or between an EMS system and other systems concerned with different aspects of power system operations, such as generation or distribution management. SCADA is modeled to the extent necessary to support power system simulation and inter-control center communication. The CIM facilitates integration by defining a common language (i.e. semantics) based on the CIM to enable these applications or systems to access public data and exchange information independent of how such information is represented internally. Major changes from the fourth edition include the following: - transformer models have been modified to be consistent for use by distribution and transmission purposes; - a more general and clear naming approach was added and several ambiguous attributes related to naming were dropped; - phase component wires models have been enhanced to describe internal phase specific attributes and connections; - addition of diagram layout models to facilitate the exchange of diagram layout information.

Specifies the framework for the specification of Component Interface Specifications (CIS) for Energy Management System Application Program Interfaces. A CIS specifies the interfaces that a component (or application) should implement to be able to exchange information with other components (or applications) and/or to access publicly available data in a standard way.This publication is of core relevance for Smart Grid.

IEC 61970-452:2015(E) rigorously defines the subset of classes, class attributes, and roles from the CIM necessary to execute state estimation and power flow applications. These requirements are based on prior industry practices for exchanging power system model data for use primarily in planning studies. This standard is intended for two distinct audiences, data producers and data recipients, and may be used from these two perspectives.IEC 61970-453:2014 is a member of the IEC 61970-450 to 499 series that, taken as a whole, defines, at an abstract level, the content and exchange mechanisms used for data transmitted between control centre components. Included in this part of IEC 61970 are the general use cases for exchange of diagram layout data, and guidelines for linking the layout definitions with CIM data. Guidelines for management of schematic definitions through multiple revisions are also included. This new edition includes the following significant technical change with respect to the previous edition: The SVG elements and its data model have been replaced by the Diagram Layout Package, which is now an integral part of the IEC 61970-301 (CIM) model.

IEC 61970-456:2013 defines the subset of classes, class attributes, and roles from the CIM necessary to describe the result of state estimation, power flow and other similar applications that produce a steady-state solution of a power network, under a set of use cases which are included informatively in this standard. This standard is intended for two distinct audiences, data producers and data recipients, and may be read from those two perspectives. From the standpoint of model export software used by a data producer, the standard describes how a producer may describe an instance of a network case in order to make it available to some other program. From the standpoint of a consumer, the standard describes what that importing software must be able to interpret in order to consume solution cases.

Specifies the format and rules for producing a machine readable form of the Common Information Model (CIM) as specified in the IEC 61970-301 standard. Describes a CIM vocabulary to support the data access facility and associated CIM semantics. This publication is of core relevance for Smart Grid.

X

X

X X X

X

X

X

X

X X

X X X

This document describes how the Web services standardized in IEC 62541 OPC Unified Architecture Parts 1 through 10 provide the definition for Data Services according to IEC 61970-40x-series for data defined by IEC 61970 Part 3 CIM in the follow section.

EC 61970-552:2013 specifies a Component Interface Specification (CIS) for Energy Management Systems Application Program Interfaces. This part specifies the format and rules for exchanging modelling information based upon the CIM. It uses the CIM RDF Schema presented in IEC 61970-501 as the meta-model framework for constructing XML documents of power system modelling information. The style of these documents is called CIMXML format. This standard supports a mechanism for software from independent suppliers to produce and consume CIM described modelling information based on a common format.IEC 62056-1-0:2014 provides information on the smart metering use cases and on architectures supported by the IEC 62056 DLMS/COSEM series of standards specifying electricity meter data exchange. It describes the standardization framework including: - the principles on which the standards shall be developed; - the ways the existing standards shall be extended to support new use cases and to accommodate new communication technologies, while maintaining coherency; - the aspects of interoperability and information security. It also provides guidance for selecting the suitable standards for a specific interface within the smart metering system.IEC TS 62056-8-20:2016(E) specifies a DLMS/COSEM communication profile that can be used in a smart metering system in which the Neighbourhood Networks (NN) are mesh networks. This profile may be considered as an adaptation and extension of the UDP/IP communication profile specified in IEC 62056-9-7:2013. It specifies a number of features essential to the efficient operation of a large scale AMI using mesh NNs.

IEC 62056-3-1:2013 describes three profiles for local bus data exchange with stations either energized or not. For non-energized stations, the bus supplies energy for data exchange. Three different profiles are supported: - base profile; - profile with DLMS; - profile with DLMS/COSEM. The three profiles use the same physical layer and they are fully compatible, meaning that devices implementing any of these profiles can be operated on the same bus. The transmission medium is twisted pair using carrier signalling and it is known as the Euridis Bus. This first edition cancels and replaces the first edition of IEC 62056-31, issued in 1999, and constitutes a technical revision. The main technical changes are: - addition of a profile which makes use of the IEC 62056 DLMS/COSEM Application layer and COSEM object model, - review of the data link layer which is split into two parts: a pure Data Link layer; a "Support Manager" entity managing the communication media; - ability to negotiate the communication speed, bringing baud rate up to 9 600 bauds.Specifies the physical layer services and protocols within the Companion Specification for Energy Metering (COSEM) three-layer connection oriented profile for asynchronous data communication.

Specifies the data link layer for connection-oriented, HDLC-based, asynchronous communication profile. This consolidated version consists of the first edition (2002) and its amendment 1 (2006). Therefore, no need to order amendment in addition to this publication. This publication is of high relevance for Smart GridIEC 62056-4-7:2015 specifies a connection-less and a connection oriented transport layer (TL) for DLMS/COSEM communication profiles used on IP networks. These TLs provide OSI-style services to the service user DLMS/COSEM AL. The connection-less TL is based on the Internet Standard User Datagram Protocol (UDP). The connection-oriented TL is based on the Internet Standard Transmission Control Protocol (TCP). This first edition cancels and replaces the IEC 62056-47 published in 2006 and constitutes a technical revision. It includes the following changes: - This standard is applicable now both for IP4 and IPv6 networks; - Latest editions of the IEC 62056 suite are referenced. DLMS/COSEM IANA-registered port numbers added.IEC 620565-3:2013 specifies the DLMS/COSEM application layer in terms of structure, services and protocols for COSEM clients and servers, and defines how to use the DLMS/COSEM application layer in various communication profiles. It defines services for establishing and releasing application associations, and data communication services for accessing the methods and attributes of COSEM interface objects, defined in IEC 62056-6-2, using either logical name (LN) or short name (SN) referencing. This edition cancels and replaces IEC 62056-53 published in 2006. It constitutes a technical revision.

X X

X

X

X

X

X

X X X X X

X X X X X

X X X X X

IEC 62056-6-1:2015 specifies the overall structure of the OBject Identification System (OBIS) and the mapping of all commonly used data items in metering equipment to their identification codes. OBIS provides a unique identifier for all data within the metering equipment, including not only measurement values, but also abstract values used for configuration or obtaining information about the behaviour of the metering equipment. This second edition cancels and replaces the first edition of IEC 62056-6-1, published in 2013. It constitutes a technical revision. The main technical changes with respect to the previous edition are listed in Annex B (informative).

IEC 62056-5-3:2016 is available as IEC 62056-5-3:2016 RLV which contains the International Standard and its Redline version, showing all changes of the technical content compared to the previous edition. IEC 62056-5-3:2016 specifies the DLMS/COSEM application layer in terms of structure, services and protocols for COSEM clients and servers, and defines how to use the DLMS/COSEM application layer in various communication profiles. It defines services for establishing and releasing application associations, and data communication services for accessing the methods and attributes of COSEM interface objects, defined in IEC 62056-6-2:2016, using either logical name (LN) or short name (SN) referencing. This second edition cancels and replaces the first edition of IEC 62056-5-3 published in 2013.IEC 62056-7-6:2013 specifies the DLMS/COSEM 3-layer, connection-oriented HDLC based communication profile.

IEC 62056-8-3:2013 specifies the DLMS/COSEM PLC S-SFK communication profile for neighbourhood networks. It uses standards established by IEC TC 57 in the IEC 61334 series.

Electricity metering data exchange - The DLMS/COSEM SUITE - Part 8-6: DMT PLC profile for neighbourhood networks

This part of IEC 62056 specifies the DLMS/COSEM communication profile for TCP-UDP/IP networks.

IEC 62439-1:2010(E) is applicable to high-availability automation networks based on the ISO/IEC 8802-3 (IEEE 802.3) (Ethernet) technology. It specifies: - the common elements and definitions for other parts of the IEC 62439 series; - the conformance test specification (normative); - a classification scheme for network characteristics (informative); - a methodology for estimating network availability (informative); - the configuration rules, calculation and measurement method for a deterministic recovery time in RSTP. It cancels and replaces IEC 62439 published in 2008 and constitutes a technical revision. It includes the following significant technical changes with respect to IEC 62439 (2008): - adding a calculation method for RSTP (rapid spanning tree protocol, IEEE 802.1Q), - adding two new redundancy protocols: HSR (High-availability Seamless Redundancy) and DRP (Distributed Redundancy Protocol), - moving former Clauses 1 to 4 (introduction, definitions, general aspects) and the Annexes (taxonomy, availability calculation) to IEC 62439-1, which serves now as a base for the other documents, - moving Clause 5 (MRP) to IEC 62439-2 with minor editorial changes, - moving Clause 6 (PRP) was to IEC 62439-3 with minor editorial changes, - moving Clause 7 (CRP) was to IEC 62439-4 with minor editorial changes, and - moving Clause 8 (BRP) was to IEC 62439-5 with minor editorial changes, - adding a method to calculate the maximum recovery time of RSTP in a restricted configuration (ring) to IEC 62439-1 as Clause 8, - adding specifications of the HSR (High-availability Seamless Redundancy) protocol, which shares the principles of PRP to IEC 62439-3 as Clause 5, and - introducing the DRP protocol as IEC 62439-6.

IEC 62439-3:2010(E) is applicable to high-availability automation networks based on the ISO/IEC 8802-3 (IEEE 802.3) (Ethernet) technology. It specifies two redundancy protocols based on the duplication of the LAN, respectively duplication of the transmitted information, designed to provide seamless recovery in case of single failure of an inter-switch link or switch in the network. It cancels and replaces IEC 62439 published in 2008 and constitutes a technical revision. It includes the following significant technical changes with respect to IEC 62439 (2008): -adding a calculation method for RSTP (rapid spanning tree protocol, IEEE 802.1Q), - adding two new redundancy protocols: HSR (High-availability Seamless Redundancy) and DRP (Distributed Redundancy Protocol), - moving former Clauses 1 to 4 (introduction, definitions, general aspects) and the Annexes (taxonomy, availability calculation) to IEC 62439-1, which serves now as a base for the other documents, - moving Clause 5 (MRP) to IEC 62439-2 with minor editorial changes, -

IEC/TS 62443-1-1:2009(E) is a technical specification which defines the terminology, concepts and models for Industrial Automation and Control Systems (IACS) security. It establishes the basis for the remaining standards in the IEC 62443 series.IEC 62443-2-1:2010 defines the elements necessary to establish a cyber security management system (CSMS) for industrial automation and control systems (IACS) and provides guidance on how to develop those elements. This standard uses the broad definition and scope of what constitutes an IACS described in IEC/TS 62443-1-1. The elements of a CSMS described in this standard are mostly policy, procedure, practice and personnel related, describing what shall or should be included in the final CSMS for the organization. This bilingual version (2012-04) corresponds to the monolingual English version, published in 2010-11.

IEC TR 62443-2-3:2015(E) describes requirements for asset owners and industrial automation and control system (IACS) product suppliers that have established and are now maintaining an IACS patch management program. This Technical Report recommends a defined format for the distribution of information about security patches from asset owners to IACS product suppliers, a definition of some of the activities associated with the development of the patch information by IACS product suppliers and deployment and installation of the patches by asset owners. The exchange format and activities are defined for use in security related patches; however, it may also be applicable for non-security related patches or updates.

X X X X X

X X X X X

X X X X X

X X X X X

X

X

X

X

X

X

IEC 62443-2-4:2015 specifies requirements for security capabilities for IACS service providers that they can offer to the asset owner during integration and maintenance activities of an Automation Solution. The contents of the corrigendum of August 2015 have been included in this copy. It establishes a framework for securing information and communication technology aspects of industrial process measurement and control systems including its networks and devices on those networks, during the operational phase of the plant's life cycle. It provides guidance on a plant's operational security requirements and is primarily intended for automation system owners/operators (responsible for ICS operation).

IEC/TR 62443-3-1:2009(E) provides a current assessment of various cybersecurity tools, mitigation counter-measures, and technologies that may effectively apply to the modern electronically based IACSs regulating and monitoring numerous industries and critical infrastructures. It describes several categories of control system-centric cybersecurity technologies, the types of products available in those categories, the pros and cons of using those products in the automated IACS environments, relative to the expected threats and known cyber vulnerabilities, and, most important, the preliminary recommendations and guidance for using these cybersecurity technology products and/or countermeasures.

IEC 62443-3-3:2013(E) provides detailed technical control system requirements (SRs) associated with the seven foundational requirements (FRs) described in IEC 62443-1-1 including defining the requirements for control system capability security levels, SL-C(control system). These requirements would be used by various members of the industrial automation and control system (IACS) community along with the defined zones and conduits for the system under consideration (SuC) while developing the appropriate control system target SL, SL-T(control system), for a specific asset. The contents of the corrigendum of April 2014 have been included in this copy.

IEC/TR 62541-1:2010(E) presents the concepts and overview of the Unified Architecture (OPC UA) specification produced by the OPC Foundation. Reading this report enables the reader to understand the series of IEC 62541 standards. Each of the other parts is briefly explained along with a suggested reading order.

IEC 62541-10:2012 specifies the standard representation of Programs as part of the OPC Unified Architecture and its defined information model. This includes the description of the NodeClasses, standard Properties, Methods and Events and associated behaviour and information for Programs.

IEC/TR 62541-2:2010(E) describes the OPC Unified Architecture (OPC UA) security model. It describes the security threats of the physical, hardware and software environments in which OPC UA is expected to run. It describes how OPC UA relies upon other standards for security. It gives an overview of the security features that are specified in other parts of the OPC UA specification. It references services, mappings, and profiles that are specified normatively in other parts of this series of standards. It is directed to readers who will develop OPC UA client or server applications or implement the OPC UA services layer.

IEC 62541-3:2015 describes the OPC Unified Architecture (OPC UA) AddressSpace and its Objects. It is the OPC UA meta model on which OPC UA information models are based. This second edition cancels and replaces the first edition published in 2010 and constitutes a technical revision. It includes the following changes: - Added rules for subtyping enumerations; - Added Property EnumValues; - Added Property ValueAsText; - Added EventType SystemStatusChangeEventType; - Added Properties MaxArrayLength and MaxStringLength; - Removed the concept of ModelParent; - Added EventType ProgressEventType; - Stated that it is allowed to use TAI in all places where UTC time is used; - Added Property EngineeringUnits; - Added ModellingRules OptionalPlaceholder and MandatoryPlaceholder.

IEC 62541-4:2015 defines the OPC Unified Architecture (OPC UA) Services. The Services described are the collection of abstract Remote Procedure Calls (RPC) that are implemented by OPC UA Servers and called by OPC UA Clients. This second edition cancels and replaces the first edition published in 2011. It constitutes a technical revision. It includes the following changes: - Update for 6.4 Redundancy. - Clarifications for Publish and Reconnect scenarios. - Handling of MonitoredItem changes in short network interruption scenarios. - Update for 6.1.3 Determining if a Certificate is Trusted. - Revised definition of parameters semaphoreFile and isOnline in Service RegisterServer. - Services ModifySubscription and ModifyMonitoredItems.

IEC 62541-5.2015 defines the Information Model of the OPC Unified Architecture. The Information Model describes standardised Nodes of a Server's AddressSpace. These Nodes are standardised types as well as standardised instances used for diagnostics or as entry points to server-specific Nodes. This second edition cancels and replaces the first edition published in 2011 and constitutes a technical revision. This edition includes the following changes: - Defined ProgressEventType; - Defined DataType called BitFieldMaskDataType; - Delete Property SamplingRateCount in ServerDiagnosticSummaryDataType; - Added the Property "EffectiveTransitionTime" to TransitionVariableType; - Introduced VariableType OptionSetType; - Added a new EventType called SystemStatusChangeEventType; - Added properties to ServerCapabilitiesType. Added an object for operation limits. Added type OperationLimitsType containing that information; - Added SecureChannelId to AuditActivateSessionEventType; - Added normative Annex C defining FileType and Methods; - Added a Method GetMonitoredItems on ServerType; - Removed the concept of ModelParent. Added meta data for namespaces in ServerType and created types for managing that. Added representations for ModellingRules OptionalPlaceholder and MandatoryPlaceholder; - Added new types NonTransparentNetworkRedundancyType, NetworkGroupDataType and EndpointUrlListDataType.

X

X

X

X

X X

X X

X X X

IEC 62541-6:2015 specifies the OPC Unified Architecture (OPC UA) mapping between the security model described in IEC TR 62541-2, the abstract service definitions, described in IEC 62541-4, the data structures defined in IEC 62541-5 and the physical network protocols that can be used to implement the OPC UA specification. This second edition cancels and replaces the first edition published in 2011 and constitutes a technical revision. This edition includes the following changes: - A new HTTPS transport has been defined; - Added an additional padding byte to handle asymmetric key sizes larger than 2048 bits. Fixed errors in SOAP action URIs; - Needed a standard way to serialize nodes in an address space. Added the UANodeSet schema defined in Annex F.

IEC 62541-7:2015 describes the OPC Unified Architecture (OPC UA) Profiles. The Profiles in this document are used to segregate features with regard to testing of OPC UA products and the nature of the testing (tool based or lab based). This includes the testing performed by the OPC Foundation provided OPC UA CTT (a self-test tool) and by the OPC Foundation provided Independent certification test labs. It is also defining functionality that can only be tested in an a lab and defining the grouping of functionality that is to be used when testing OPC UA products either in a lab or using automated tools. This second edition cancels and replaces the first edition published in 2012 and constitutes a technical revision. It includes the following changes: - Added a large number of new Facets to cover additional functional areas of OPC UA. Most significantly: - Facets for Historical Access; - Facets for Aggregates; - Facets for HTTPs; - New Security Facets; - New User Token Facet that supports anonymous access; - Best Practice Facets as well as New Security Policy for asymmetric key length > 2048.

IEC 62451-8:2015 is part of the overall OPC Unified Architecture (OPC UA) standard series and defines the information model associated with Data Access (DA). It particularly includes additional VariableTypes and complementary descriptions of the NodeClasses and Attributes needed for Data Access, additional Properties, and other information and behaviour. This second edition cancels and replaces the first edition published in 2011 and constitutes a technical revision. This edition includes the following changes: - Clarified that deadband has to be between 0.0 and 100.0. Violations result in error Bad_DeadbandFilterInvalid; - Added VariableTypes handling ArrayItems and DataTypes supporting this, including complex number types.

IEC 62541-9:2015 specifies the representation of Alarms and Conditions in the OPC Unified Architecture. Included is the Information Model representation of Alarms and Conditions in the OPC UA address space. This second edition cancels and replaces the first edition published in 2012 and constitutes a technical revision. This edition includes the following changes: - added section to describe expect behaviour for A&C servers and the associated information model in the case of redundancy or communication faults; - changed the DialogConditionType to be not abstract since it is expect that instance of this type will exist in the system; - updated ConditionRefresh Method to allow the use of the well know NodeIds associated with the types for the MethodId and ConditionId instead of requiring the call to use only the MethodId and ConditionId that is part of an instance; - Fixed ExclusiveLimitStateMachineType and ShelvedStatemachineType to be sub-types of FinitStateMachineType not StateMachineType.

This European Standard specifies a data model to abstract the metering world towards a simple external consumer display. The data model, as described by means of functional blocks contained in this European Standard, lays down the format of metering data accessible by a simple external consumer display. This data interface would be typically part of the meter communication functions and be accessed by a simple external consumer display via the H1 interface of the CEN/CLC/ETSI TR 50572 between the display and the meter communication functions.The data interface specified in this document may also be accessed by the LNAP or NNAP through the C or M interface, after which the data could be accessed by HBES devices through the H2 and H3 interface.In other words, in this way the same data model can be used both on the H1 as well as the H2 and H3 interface.The document specifies neither the communication mechanisms used on the data interface, nor the applied data privacy and security mechanisms nor the ergonomics of the simple external consumer displays, where national regulations may apply.The document does also not specify the communication protocol used between the meters and the meter communication functions. However, it takes into account the existing European standards like the EN 13757 series (in particular EN 13757-3:2013 and its Annex O) and the EN 62056 series for the definition of the data model.

This standard specifies the data model, to be used above the Application Layer by the interface between the Customer Energy Manager (CEM) and the mappings. The scope of the standard covers: - Technology independent data structure to be used to exchange information over interface II - Compliance of the data structure described in XSDs (XML schema Definitions) - This standard applies for public or privat building / Home, industrial areas are excluded

Identifies a functional reference architecture for communications relevant for smart metering systems and the standards relevant to meeting the technical / data communications requirements of Mandate M/441, in particular to assist the active participation of consumers in the energy markets.

SO/IEC TR 27019:2013 provides guiding principles based on ISO/IEC 27002 for information security management applied to process control systems as used in the energy utility industry. The aim of ISO/IEC TR 27019:2013 is to extend the ISO/IEC 27000 set of standards to the domain of process control systems and automation technology, thus allowing the energy utility industry to implement a standardized information security management system (ISMS) in accordance with ISO/IEC 27001 that extends from the business to the process control level.

The scope of ISO/IEC TR 27019:2013 covers process control systems used by the energy utility industry for controlling and monitoring the generation, transmission, storage and distribution of electric power, gas and heat in combination with the control of supporting processes. This includes in particular the following systems, applications and components:

the overall IT-supported central and distributed process control, monitoring and automation technology as well as IT systems used for their operation, such as programming and parameterization devices; digital controllers and automation components such as control and field devices or PLCs, including digital sensor and actuator elements; all further supporting IT systems used in the process control domain, e.g. for supplementary data visualization tasks and for controlling, monitoring, data archiving and documentation purposes; the overall communications technology used in the process control domain, e.g. networks, telemetry, telecontrol applications and remote control technology; digital metering and measurement devices, e.g. for measuring energy consumption, generation or emission values; digital protection and safety systems, e.g. protection relays or safety PLCs; distributed components of future smart grid environments; all software, firmware and applications installed on above mentioned systems.Outside the scope of ISO/IEC TR 27019:2013 is the conventional or classic control equipment that is non-digital, i.e. purely electro-mechanical or electronic monitoring and process control systems. Furthermore, energy process control systems in private households and other, comparable residential building installations are outside the scope of ISO/IEC TR 27019:2013.Telecommunication systems and components used in the process control environment are also not directly part of the scope of ISO/IEC TR 27019:2013. These are covered by ISO/IEC 27011:2008.

The purpose of the document is to provide developers of security standards with a summary of the requirements of ISO/IEC-15408 in the context of standardization and to give guidance on how formal methods and other engineering techniques can be used to ensure that standards meet, as far as is possible, the requirements of ISO/IEC 15408 and do not prevent an implementation from achieving an appropriate EAL.

X X X

X

X

X

X

X

X X X

The present document gives guidance on the application of security countermeasures to service capabilities. It covers the construction of services from service capabilities and how a security evaluation of a service capability should be performed. The present document examines and gives guidance on the use of the Composition assurance class defined by the Common Criteria working group in order to be able to answer the question: "if components A and B are evaluated as having security ratings X and Y what is the security rating that can be assigned to the combination of A and B?" The present document builds on the guidance to the Common Criteria for Information Technology Security Evaluation given in EG 202 387 [3] with a particular view to assessing the security of the NGN. In the NGN context, where services are not explicitly defined but are made from combining service capabilities, the present document gives guidance on the means to apply effective security to both service capabilities in isolation, and to service capabilities in combination. The guidance reviews the service capability model in clause 4 and examines the requirements for security arising from the service capability requirements defined for NGN-R1 in clause 5. The analysed security requirements are presented in the form of ISO/IEC 15408-2 [17] functional models. Clause 6 presents a review of the Common Criteria Composition assurance class and describes its impact on the ETSI standardization process. Annex A reviews the use of cryptographic techniques in the NGN. A number of assumptions of the design of NGN for security analysis to take place are made on the NGN development process. The assumption in the present document is that the NGN has been developed using top-down decomposition of the specification, using techniques of planned validation of the specification, with careful recording of design decisions and validation results.

The present document is intended to cover the provisions of Directive 1999/5/EC (R&TTE Directive), Article 3.2, which states that "..... radio equipment shall be so constructed that it effectively uses the spectrum allocated to terrestrial/space radio communications and orbital resources so as to avoid harmful interference". In regards to interference to systems operating in adjacent bands guidance for single carrier BTS and multicarrier BTS is provided in ECC Report 146. In addition to the present document, other ENs that specify technical requirements in respect of essential requirements under other parts of article 3 of the R&TTE Directive may apply to equipment within the scope of the present document.

The present document specifies technical characteristics and methods of measurements for the radio equipment GSM mobile station. This radio equipment type is for operation within the Digital cellular telecommunications system in the GSM 900 and/or GSM 1800 frequency bands as shown in table 1, with a channel separation of 200 kHz, utilizing constant envelope modulation and carrying traffic channels according to the Time Division Multiple Access (TDMA) principle. The present document covers the essential requirements of article 3.2 of Directive 2014/53/EU under the conditions identified in annex A. The present document covers the general access requirements for terminal equipment up to and including 3GPP Rel-12. The general access requirements, applied to the terminal equipment, are for one release only. The present document does not cover the GPRS Class A mobiles and the ECSD mobiles. For each test purpose and its corresponding conformance requirement, a reference is given to the test method in ETSI TS 151 010-1. The requirements apply at the air interface, which may be stimulated to perform the tests by additional equipment if necessary.

The present document applies to user equipment, repeaters and base stations for IMT, falling within the scope of one of the other parts of ETSI EN 301 908 [i.8], except for IMT-2000 FDMA/TDMA (DECT). The present document also covers the corresponding ancillary equipment. NOTE 1: ETSI EN 301 908-10 contains in particular requirements for radiated spurious emissions and control and monitoring functions applicable to IMT-2000 FDMA/TDMA (DECT) equipment. The present document includes technical requirements which are common to equipment falling within the scope of several of the other parts. NOTE 2: The other parts of ETSI EN 301 908, which are listed in the foreword of the present document, specify technical requirements in respect of a particular type of IMT equipment. NOTE 3: Recommendations ITU-R M.1457-12 [i.4] and M.2012-1 define the characteristics of the members of the IMT-2000 family and IMT-Advanced respectively by means of references to technical specifications developed by Standards Development organizations. The present document applies to equipment designed to meet any version of the terrestrial specifications referenced in Recommendations ITU-R M.1457-12 and M.2012-1. The present document contains requirements to demonstrate that radio equipment both effectively uses and supports the efficient use of radio spectrum in order to avoid harmful interference.

The present document applies to the following radio equipment types: 1) Network Based SRDs which are SRDs intended to operate in association with other SRDs to form network topologies supporting the intended application. 2) Network Relay Points which are specific Network Based SRDs supporting interconnection of a network of SRDs with an external network or service. The present document covers equipment intended for use in a fixed location, equipment normally fixed in a vehicle and equipment intended to be carried or attached. The present document contains requirements to demonstrate that radio equipment both effectively uses and supports the efficient use of radio spectrum in order to avoid harmful interference.

The present document applies to the following radio equipment types: 1) Network Based SRDs which are SRDs intended to operate in association with other SRDs to form network topologies supporting the intended application. 2) Network Relay Points which are specific fixed Network Based SRDs supporting interconnection of a network of SRDs with an external network or service. The present document covers equipment intended for use in a fixed location, equipment normally fixed in a vehicle and equipment intended to be carried or attached.

The present document applies to the following following radio equipment types: 1) Network Based SRDs which are SRDs intended to operate in association with other SRDs to form network topologies supporting the intended application. 2) Network Relay Points which are specific Network Based SRDs supporting interconnection of a network of SRDs with an external network or service. The present document is intended to cover the provisions of Directive 1999/5/EC (R&TTE Directive), article 3.2, which states that "..... radio equipment shall be so constructed that it effectively uses the spectrum allocated to terrestrial/space radio communications and orbital resources so as to avoid harmful interference". In addition to the present document, other ENs that specify technical requirements in respect of essential requirements under other parts of article 3 of the R&TTE Directive may apply to equipment within the scope of the present document.

The present document provides guidance on the preparation of Protection Profiles (PP) based upon ETSI communication standards. A PP defines an implementation-independent set of security requirements for a category of communications equipment which is subject to evaluation under the Common Criteria (CC) scheme described in the multipart ISO/IEC 15408 [7].The detailed contents of a PP are specified in ISO/IEC 15408-1. The use and applicability of the CC to the ETSI standardization process is described in EG 202 387 and further guidance on the implementation of security-related standards in telecommunications equipment is specified in ES 202 383. Throughout the present document, a worked example of a Protection Profile (PP) for TETRA Direct Mode Operation (DMO) security is used as an illustration. A partially complete PP for TETRA DMO security can be found in annex B. Conformance to the present document is established by successful evaluation to the requirements of ISO/IEC 15408-3.

X X X

X X X

X X X

X X X

X X X

X

X

The present document provides guidance on the preparation of Security Targets (ST) based upon ETSI communication standards. The detailed contents of an ST are specified in ISO/IEC 15408-1. The present document endorses the requirements for STs expressed in ISO/IEC 15408-1 annex C with some specified modifications and additional requirements. A proforma for a Security Target is given in annex A in tabular form to align with the proforma structure defined for Protection Profiles in ES 202 382. The use and applicability of the Common Criteria (CC) to the ETSI standardization process is described in EG 202 387. Conformance to the present document is established by successful evaluation to the requirements of ISO/IEC 15408-3.

This ETSI Technical Report (ETR) lists all security features and mechanisms that the Security Techniques Advisory Group (STAG) has evaluated and which may be used in ETSI standards. However, this ETRmerely presents guidelines for the selection and application of specific security mechanisms in an annex. If more specific advice is needed, references to relevant sources of information are given. Moreover, theETSI STAG experts are ready to assist in case of questions and problems. In many cases, the security mechanisms are not officially standardized themselves, but are registered for use. Many of them are not published because of security considerations, but may be used in specific ETSI-applications.

This ETSI Technical Report (ETR) provides guidance and support for a comprehensive analysis of threats, vulnerabilities, risks and for the compilation of a specific set of security requirements.It is the intention to provide the user of this ETR with a comprehensive understanding and methodology regarding threats, vulnerabilities, risks and security requirements. The security architecture of a particular system is always unique and the threats and security requirements are very specific to that system. The contents of this paper provide guidelines and checklists rather than specifying in too much detail in order to facilitate the application by the user. This ETR should enable TCs to start their security work from scratch, to take advantage of the experience from other TCs Security Experts Groups (SEGs) or to adapt solutions that have already been devised. STCs seeking advice on threat analysis and security requirements capture should ask STAG for support.

Security features have been incorporated in a number of European Telecommunication Standards (ETSs), and are likely to become an increasingly important aspect of ETSI work as digital technology comes more and more into use. This Technical Committee Reference Technical Report (TCR-TR) provides an overview of security features which currently have been integrated, or are in the process of integration, into an ETS. For each of the activities the scope and status of the work is described. Also some potential security activities which are identified or planned as future ETSI activities are listed.This TCR-TR is intended to be a reference document describing the actual status of the security work within ETSI. For each of the activities described, the corresponding classes from the classification given in ITSTC Memorandum M-IT-06 [1] are indicated. In cases where an activity corresponds to more than one class, the most relevant class is listed first.The present document provides an analysis of the security provisions made in IPv6 and outlines how they may be used to support the objectives of the European Commission to support the implementation of PKI solutions and the further deployment of IPv6 and IPsec. The present document provides guidance on interpreting the requirements specified in TS 101 456 (V1.4.1). This guidance is intended for use by bodies that supervise (e.g. as per Directive articles 3.3), approve or accredit CAs (e.g. as per articles 3.2 of Directive 1999/93/EC of the European Parliament and of the Council of 13 December 1999 on a Community framework for electronic signatures), assessors, certification service providers and other interested parties. The present document purpose is to facilitate assessors in evaluating compliance of certification authorities with TS 101 456 and, consequently, to facilitate certification authorities in implementing TS 101 456 requirements.

The present document has the purpose to propose a set of practices applicable to the various security related aspects of signing fiscally relevant documents when issued and storing them for the legally required time. It is based on the results of a survey carried out on what practices are actually in place in the five most populated European Union Member States (France, Germany, Italy, Spain, UK). The present document specifically addresses trust service providers supporting signing and storage services for fiscally relevant documents, regarding business accounting for corporate entities in several European Member States. In particular it is suitable for Value Added Tax (VAT) purposes although it is applicable also to other fiscally relevant documents. The present document does not directly address requirements for accounting for individuals. The practices identified in the present document are independent of the type of document or information being protected. The present document addresses solely the Advanced Electronic Signature based solution. It is recognized that other suitable measures, not employing Advanced Electronic Signatures, and hence are outside the scope of the present document, may be applied to assure the authenticity and integrity of digital accounting documents. It should be noted that the reliability of such alternative measures generally depend on the trustworthiness of the organization and may require independent assessment of the technical and organizational measures applied. Advanced Electronic Signature may be used to augment existing measures to provide even higher security, or to reduce the need for other controls.

X X

X X X

X X

X X X

X X

In the present document, threats against M2M functional architecture, Service layer and interfaces are identified and analysed for impact and for likelihood. The need for countermeasures is determined. The threat analysis considers only the following two types of threat (with the following order of priority): 1) Type 1 threats: threats that are specific to M2M service layer or interfaces for the service layer. 2) Type 2 threats: threats that may not be specific to M2M service layer but which have a significant impact upon M2M functional requirements. The level of risk (i.e. combined likelihood and impact) of identified threats is also evaluated. As a result of that, there is a prioritisation of threats and therefore of countermeasures and security requirements. Concerning countermeasures identified in the present document, the scope includes: • consideration of merits and demerits (i.e. pros and cons) of identified countermeasures; • evaluation of countermeasures to determine: 1) the need for a standardised solution/implementation, 2) availability of existing standardised solutions (e.g. from other SDOs), 3) the need for a new standardised solution (either from another SDO or from ETSI M2M). Additionally: • Threats against, or originating from, any stakeholders may be considered. • Countermeasures which are normal practice in IT systems (e.g. maintenance logs, firewalls) are out of scope. Content in the present document may lead to new requirements in future releases of TS 102 689 and normative text in TS 102 690

The present document present an analysis of the security mechanisms that could be supported in the customer environment (Customer Network Gateway or Customer Devices) with reference to the overall end to end security architecture for the NGN defined by WG7. As examples, these mechanisms can be related to authentication (for connectivity and for services), firewalling and network access/parental control, virus protection, intrusion detection, Anti Spam capabilities. The activity will be performed in close relationship with WG7. The reactions to threats or the protections against threats described in the present document will involve only the CPN, not the external network. The present document presents the results of the Threat Vulnerability Risk Analysis (TVRA) for the NGN. The present document follows the method and proforma for carrying out a TVRA defined in TS 102 165-1 and incorporates material of the NGN threat and risk analysis herein. The present document identifies security-relevant interfaces in the NGN, identifies security-relevant scenarios for use in the NGN, analyses NGN in terms of security threats and risks by performing a security threat and risk analysis, and classifies the identified vulnerabilities and the associated risk presented to the NGN. This threat and risk analysis makes a number of assumptions that are believed to hold for typical deployment scenarios of the NGN.

The present document identifies the impact on the NGN in achieving compliance to the data retention directive. The present document makes a number of recommendations to operators and manufacturers that may be sufficient to ensure compliance, and identifies where future standardisation may be required. The present document applies to TISPAN NGN services as specified by TR 180 001 (for release 1 specific capabilities) and TR 180 002 (for release 2 specific capabilities), and where the NGN user is identified as specified in TS 184 002. The present document is structured in the following way: • NGN analysis with respect to Data Retention: - annex containing an analysis of the existing Directive and the available provisions in the NGN; - annex providing a comparison of terms between Directive and NGN. • Identification of the data that is expected to be retained in the NGN under the DR Directive and a mapping to determine if the data is available in the NGN. The present document does not define the handover domain which is specified in TS 102 657 nor does the document cover any conformance aspects relating to IMS. However where other standards bodies are directly impacted by the DR Directive in the NGN the present document identifies in outline form the affected publications from such SDOs. The present document does not address the application of Data Retention in Customer Premises Networks (CPN) or Next Generation Corporate Networks (NGCN).

Bearer and Teleservices, as respectively defined in GSM 02.02 and GSM 02.03, are the objects which the GSM PLMNoperators offer to their customers. Besides these basic telecommunications services, features which aim at up-gradingthese basic services need also to be offered. Due to the use of radiocommunications in a PLMN, which are of a specialnature compared to classical distribution transmission techniques used in the fixed networks, such a category of featuresis related to security aspects.In a GSM PLMN, both the users and the network operator have to be protected against undesirable intrusion of thirdparties. However, measures should be provided for in order to insure maximum protection of the rights of theindividuals concerns. As a consequence, a security feature is either a supplementary service to Tele or Bearer services, which can be selected by the subscriber, or a network function involved in the provision of one or several telecommunication services. The purpose of the present document is to define the security features which are to be available in a GSM PLMN, together with the associated levels of protection. The present document is only concerned with those security features which aim at the up-grading of the security in a GSM PLMN. In particular, end-to-end security is outside the scope of the present document.The implementation aspects of security features are described in GSM 03.20.

X

X

X X X

X X X

X X

X X

X X

X

X X

The present document specifies policy requirements relating to Certification Authorities (CAs) issuing qualified certificates (termed certification-service-providers issuing qualified certificates in the Directive Directive 1999/93/EC of the European Parliament and of the Council of 13 December 1999 on a Community framework for electronic signatures). It defines policy requirements on the operation and management practices of certification authorities issuing qualified certificates such that subscribers, subjects certified by the CA and relying parties may have confidence in the applicability of the certificate in support of electronic signatures.

The present document specifies policy requirements relating to Certification Authorities (CAs) issuing public key certificates, including Extended Validation Certificates (EVC) and Publicly trusted TLS/SSL certificates (PTC). It defines policy requirements on the operation and management practices of certification authorities issuing and managing certificates such that subscribers, subjects certified by the CA and relying parties may have confidence in the applicability of the certificate in support of cryptographic mechanisms. The policy requirements are defined in terms of six reference certificate policies and a framework from which CAs can produce a certificate policy targeted at a particular service. The first reference policy defines a set of requirements for CAs providing a level of quality the same as that offered by qualified certificates, without being tied to the Electronic Signature Directive (1999/93/EC) and without requiring use of a secure user (signing or decrypting) device. This is labelled the "Normalized" Certificate Policy (NCP). It is anticipated that the NCP may be used as the basis for realizing the quality level set by the Qualified Certificate Policy (as defined in TS 101 456) but without the legal constraints of the Electronic Signature Directive (1999/93/EC). In addition to the NCP quality level, the present document specifies six alternative variants of NCP, the requirements of which may be used where alternative levels of service can be justified through risk analysis.

The present document defines a method for use by ETSI standards developers in undertaking an analysis of the threats, risks and vulnerabilities of a telecommunications system. The method builds from the Common Criteria for security assurance and evaluation defined in ISO/IEC 15408 and specifically targets the means to build a Threat Vulnerability and Risk Analysis (TVRA) to allow its reference by an ETSI specification developed using the guidelines given in EG 202 387 [i.1] and ES 202 382. The TVRA forms part of the documentation set for the Target Of Evaluation as specified in ES 202 382 with its intended audience being a developer of standards based Protection Profiles. The Unified Modelling Language (UML) is used to model relationships within systems for analysis within the TVRA as a semi-formal tool with verification and simulation capabilities deployed during development. The present document provides a database definition for TVRA and provides, in annexes, the application of the TVRA method to a number of NGN subsystems or components. The database definition is appended to the present document as a text file containing Structured Query Language (SQL) database definition commands.

The present document defines by means of an information model and functional entity behavioural model, the security countermeasures for the ICT in general and where examples are shown they are shown with respect to the NGN. Countermeasures are grouped by their key feature, i.e. Authentication, Integrity. The Unified Modelling Language (UML) is used to model the countermeasures as a semi-formal tool with verification and simulation capabilities deployed during development. The countermeasures defined in the present document have been identified from an analysis of the NGN presented in TS 102 165-1 and in TR 187 002 as those most likely to be required for mitigation of risk in the NGN. The deployment of the countermeasures in the NGN is extrapolated from TR 187 002 and defined in this document. The present document is intended for designers of security countermeasures. The specific use of IPsec in ESP mode including IKEv2 and is reviewed in annex B of this document as a specific stage 3 implementation of the stage 1 and stage 2 capabilities. The authentication countermeasures outlined as structural and behavioural patterns in the present document cover the following scenarios: • Source authentication as defined for IPsec ESP. • NASS-IMS bundled authentication including mechanisms for NASS authentication. • Early IMS authentication (by reference to TR 133 978).

The present document specifies the structure of Secured Packets for different transport and security mechanisms. It is applicable to the exchange of secured packets between an entity in a network and an entity in the UICC. Secured Packets contain application messages to which certain mechanisms according to TS 102 224 have been applied. Application messages are commands or data exchanged between an application resident in or behind the network and on the UICC. The Sending/Receiving Entity in the network and the UICC are responsible for applying the security mechanisms to the application messages and thus turning them into Secured Packets.

The present document defines the remote management of the UICC based on any of the secured packet structures specified in ETSI TS 102 225. It specifies the APDU format for remote management. • Furthermore the present document specifies: a set of commands coded according to this APDU structure and used in the remote file management on the UICC. This is based on ETSI TS 102 221.• A set of commands coded according to this APDU structure and used in the remote application management on the UICC. This is based on the GlobalPlatform Card Specifications. The present document specifies the technical implementation of the secure channel requirements specified in TS 102 412. The present document includes the architecture, functional capabilities and characteristics of the Secure Channel protocol and its associated interfaces transported over the UICC interface specified in TS 102 221 and over the UICC USB interface specified in TS 102 600.

The present document specifies policy requirements applicable to Trusted Service Providers (TSP) that electronically sign and/or store data objects on behalf of their customers. These policy requirements may also be complied with by persons that store data objects on their own. The present document aims to address regulatory requirements to produce and reliably keep, even indefinitely, electronic data objects, where applicable also signed. The practices identified in the present document are independent of the type of data object being preserved, although peculiar requirements for fiscally relevant ones are also specified. The present document is directed at policies involving the use of the Advanced Electronic Signatures or Qualified Electronic Signatures. The primary aim of the application of signatures is to assure the integrity and the authenticity of origin of data objects in communication and storage. However, signatures may also be used, where required, to provide content commitment (i.e. non-repudiation). The present document addresses solely the Advanced Electronic Signature based solutions. It is recognized that other suitable measures, not employing Advanced Electronic Signature, and hence that are outside the scope of the present document, may be applied to assure the authenticity and integrity of digital data objects. It should be noted that the reliability of such alternative measures generally depend on the trustworthiness of the organization, on the exhaustiveness of the adopted practices and procedures and may require independent assessment of the technical and organizational measures applied. Advanced Electronic Signatures may be used to augment existing measures to provide even higher security, or to reduce the need for other controls. This fits particularly art. 233 of EU VAT Directive 2006/112/EC as amended by 2010/45/EU. The present document may be used by competent independent bodies as the basis for confirming that an organization is trustworthy in issuing and storing signed electronic data object on behalf of other persons or on its own behalf.

The present document specifies the M2M service requirements aiming at an efficient end-to-end delivery of M2M services. It contains the following clauses: • General requirements - describes communications features necessary for the correct establishment of M2M communications. •Management - specifies requirements related to the management modes (malfunction detection, configuration, accounting, etc.). • Functional requirements for M2M services - describes functionalities-related requirements for M2M (data collection & reporting, remote control operations, etc.). • Security - covers the requirements for M2M device authentication, data integrity, privacy, etc. • Naming, numbering and addressing - provides the requirements relating to naming, numbering and addressing schemes specific to M2M.

X X

X X

X X

X

X

X

X

X

X

X

The present document contains the overall end to end M2M functional architecture, including the identification of the functional entities and the related reference points. The M2M functional architecture is designed to make use of an IP capable underlying network including the IP network service provided by 3GPP, TISPAN and 3GPP2 compliant systems. The use of other IP capable networks is not intentionally excluded. Non IP data services are used in the context of the present document for the purpose of out of band communication. Details of such usage are not depicted in the present document. The present document collects the Use Cases which have been identified for the Smart Metering M2M application. These Use Cases will identify actors and information flows, and will form the basis of future requirements work at TC M2M on Smart Metering. Several parts of the present document have been taken from "Smart Metering Functionality Use Cases" in particular the subclauses "General Use Case Description", "Scenario" and "Information Exchanges" of clause 5.2.The present document contains the stage 3 specification for the mIa, dIa and mId reference points of the M2M architecture as identified in TS 102 690.

The present document highlights the applicability of M2M architecture to smart grid networks. The present document develops the most relevant Smart grids use cases, used to derive high level requirements. In addition it provides a standard gap analysis (applicability of M2M APIs for Smart Grid applications, mechanisms to manage energy for end users, etc), and derives a set of recommendation for the work of ETSI M2M. Finally it shows dependencies and relationships with other works within ETSI TCs and other standards organisations (including the ones covering the energy Layer: NIST, CEN/Cenelec and IEC in particular). The present document collects and evaluates implementation profiles for interworking with M2M Area Network technologies. An implementation profile is defined, for the purpose of the present document, as the description on how the ETSI M2M architecture can be used to achieve interworking. Each implementation profile is evaluated against deployment scenarios and applicable technologies in order to identify the most suitable for the specific conditions.

The present document is motivated by the fact that within the ETSI M2M System semantic information needs to be available on M2M data that is transferred within the M2M system. Through such semantic information M2M data can be discovered by applications that do not have prior knowledge on them. The capability of the ETSI M2M System to enable applications to discover, interpret and use M2M data from different sources is considered essential for creating high-level M2M services and to develop open markets for M2M data.

The present document specifies the interface between the UICC and the terminal. The present document specifies: • the requirements for the physical characteristics of the UICC; • the electrical interface for exchanging APDUs between the UICC and the terminal, based on ISO/IEC 7816-3; • the initial communication establishment and the transport protocols for this interface; • a model which serves as a basis for the logical structure of the UICC APDU interface; • communication commands and procedures for the UICC APDU interface; • application independent files and protocols for the UICC APDU interface. The administrative procedures, initial card management and optional communication interfaces between the UICC and terminal are not within the scope of the present document.

The present document defines the service description of the UICC Application Programming Interface (UICC API) internal to the UICC. Stage one is an overall service description, and does not deal with the implementation details of the API. The present document includes information applicable to network operators, service providers and terminal, UICC, Network Access Application (NAA) providers, switch and database manufacturers. The present document contains the core requirements, which are sufficient to provide a complete service. It is highly desirable however, that technical solutions for a UICC API should be sufficiently flexible to allow for possible enhancements. Additional functionalities not documented in the present document may implement requirements which are considered outside the scope of the present document. This additional functionality may be on a network wide basis, nation-wide basis or particular to a group of users. Such additional functionality shall not compromise conformance to the core requirements of the service. The present document defines the stage two description of the "Application Programming Interface and Loader Requirements" internal to the UICC. This stage two describes the functional capabilities and the information flow for the UICC API implemented on the Java Card™ Platform, 3.0.1 Classic Edition. The present document includes information applicable to network operators, service providers and UICC, server and database manufacturers.

The present document specifies the additional requirements for Release 7 onwards of the TC SCP with respect to earlier releases. The present document covers all the Stage 1 requirements which are not covered by other TC SCP stage 1 documents.

X

X

X

X

X

X

X

X

X

X

The present document describes the stage two specification of the USSM. The USSM is a generic Security Service Module on a UICC, which can be used by applications on the UICC. This document defines the architectural framework for using the USSM, the functional services for applications and how to manage the USSM on an UICC. The architecture is based on the concepts of Global Platform Card Specification and the requirements as defined in TS 102 226. The concept of the USSM is flexible enough to allow additional security objects and operations to be added easily in later versions of the USSM. The present document details the technical specifications for M2M UICCs. Specifically, the present document specifies: • Physical, logical and electrical specifications for additional machine to machine form factors for the M2M UICC. • Environmental specifications of the M2M UICC dedicated to M2M applications for all specified UICC form factors. • Device pairing mechanisms that allow the M2M UICC to verify the terminal with which it is operating. The present document contains OMA DM compatible management objects for three ETSI M2M mgmtObj instances: etsiSclMo M2M-TS 102 690, etsiAreaNwkInfo M2M-TS 102 690 and etsiAreaNwkDeviceInfo M2M-TS 102 690.

The present document contains BBF TR-069 compatible Data Model for ETSI M2M.The present document specifies Interoperability Test Descriptions (TDs) for the CoAP binding as specified in Annex D of TS 102 921. The Test Descriptions cover the CoAP protocol specification where relevant. The purpose of the interoperability testing is to prove that end-to-end functionality between devices such as D' and GSCL or D' and GSCL and NSCL and NA and using CoAP as underlying application layer, is as required by the standard(s) on which those devices are based. The present document defines the use cases and requirements for an embedded UICC. The present document specifies the service requirements for Network Improvements for Machine Type Communications. In particular it will: - identify and specify general requirements for machine type communications; - identify service aspects where network improvements (compared to the current human-to-human oriented services) are needed to cater for the specific nature of machine-type communications; - specify machine type communication requirements for these service aspects where network improvements are needed for machine type communication.

The present document defines the Stage 2 service description for the Evolved 3GPP Packet Switched Domain - also known as the Evolved Packet System (EPS) in this document. The Evolved 3GPP Packet Switched Domain provides IP connectivity using the Evolved Universal Terrestrial Radio Access Network (E-UTRAN). The specification covers both roaming and non-roaming scenarios and covers all aspects, including mobility between E-UTRAN and pre-E-UTRAN 3GPP radio access technologies, policy control and charging, and authentication. The Radio Access Network functionality is documented only to the extent necessary to describe the overall system. TS 36.300 contains the overall description of the Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN). ITU-T Recommendation I.130 describes a three-stage method for characterisation of telecommunication services, and ITU-T Recommendation Q.65 defines Stage 2 of the method. TS 23.402 is a companion specification to this specification.

This document specifies the stage 2 service description for providing IP connectivity using non-3GPP accesses to the Evolved 3GPP Packet Switched domain. In addition, for E-UTRAN and non-3GPP accesses, the specification describes the Evolved 3GPP PS Domain where the protocols between its Core Network elements are IETF-based. ITU-T Recommendation I.130 describes a three-stage method for characterisation of telecommunication services, and ITU-T Recommendation Q.65 defines stage 2 of the method. The specification covers both roaming and non-roaming scenarios and covers all aspects, including mobility between 3GPP and non 3GPP accesses, policy control and charging, and authentication, related to the usage of non-3GPP accesses. TS 23.401 covers architecture aspects common to the Evolved 3GPP Packet Switched domain. The present document specifies architecture enhancements to facilitate communications with packet data networks and applications (e.g. Machine Type Communication (MTC) applications on the (external) network/MTC servers) according to the use cases and service requirements defined in TS 22.368, TS 22.101, and related 3GPP requirements specifications. Both roaming and non-roaming scenarios are covered.

X

X X

X X

X X

X X

X

X

X

X

X

X

The present document provides the stage 3 specification of the Tsp reference point for the present release. The functional requirements and the stage 2 specifications of the Tsp reference point are contained in 3GPP TS 23.682. The Tsp reference point lies between the Service Capability Server (SCS) and the Machine Type Communication Inter Working Function (MTC-IWF).

The scope for this technical specification is to specify the security features and mechanisms for secure access to the IM subsystem (IMS) for the 3G mobile telecommunication system. Since the scope also encompasses the use of these security features and mechanisms for secure access to IMS in the context of fixed broadband networks and 3GPP2 networks, Annex L and Annex S specify how the material in the main body and other normative Annexes of this document apply to the fixed broadband networks and 3GPP2 networks respectively. The IMS supports IP Multimedia applications such as video, audio and multimedia conferences. SIP, Session Initiation Protocol, was chosen as the signalling protocol for creating and terminating Multimedia sessions, cf. RFC 3261. This specification only deals with how the SIP signalling is protected between the subscriber and the IMS, how the subscriber is authenticated and how the subscriber authenticates the IMS.

The present document defines the security architecture for network domain IP based control planes, which shall be applied to NDS/IP-networks (i.e. 3GPP and fixed broadband networks). The scope of network domain control plane security is to cover the control signalling on selected interfaces between network elements of NDS/IP networks.

The document specifies the security architecture; trust model and security requirements for the interworking of the 3GPP System and WLAN Access Networks. This specification is also valid for other IP based Access Networks that support the same security capabilities towards the interworking system as WLAN does.

The scope of this Technical Specification is limited to authentication of network elements, which are using NDS/IP or TLS. In the case of NDS/IP this specification includes both the authentication of Security Gateways (SEG) at the corresponding Za-interfaces and the authentication between NEs and between NEs and SEGs at the Zb-interface. Authentication of end entities (i.e. NEs and SEGs) in the intra-operator domain is considered an internal issue for operators. This is quite much in line with which states that only Za is mandatory and that the security domain operator can decide if the Zb-interface is deployed or not, as the Zb-interface is optional for implementation. Validity of certificates may be restricted to the operator's domain in case of Zb interface or in case of Za-interface between two security domains of the same operator. In the case of TLS this Specification concentrates on authentication of TLS entities across inter-operator links. For example, TLS is specified for inter-operator communications between IMS and non-IMS networks TS 33.203 and on the Zn' interface in GBA TS 33.220. Authentication of TLS entities across intra-operator links is considered an internal issue for operators. However, NDS/AF can easily be adapted to the intra-operator use case since it is just a simplification of the inter-operator case when all TLS NEs and the PKI infrastructure belong to the same operator. Validity of certificates may be restricted to the operator's domain. An Annex contains information on the manual handling of TLS certificates in case automatic enrolment and revocation according to NDS/AF for TLS is not implemented.

The present document describes a general description of the physical layer of the E-UTRA radio interface. The present document also describes the document structure of the 3GPP physical layer specifications, i.e. TS 36.200 series. The TS 36.200 series specifies the Uu and Un points for the 3G LTE mobile system, and defines the minimum level of specifications required for basic connections in terms of mutual connectivity and compatibility.

(3GPP TS 36.211) The present document describes the physical channels for evolved UTRA.

(3GPP TS 36.212) The present document specifies the coding, multiplexing and mapping to physical channels for E-UTRA.

(3GPP TS 36.213) The present document specifies and establishes the characteristics of the physicals layer procedures in the FDD and TDD modes of E-UTRA.

(3GPP TS 36.214) The present document contains the description and definition of the measurements done at the UE and network in order to support operation in idle mode and connected mode.

(3GPP TS 36.216) The present document describes the characteristics of eNB - relay node transmissions.

X

X X

X X

X X X

X

X

X

X

X

X

X

(3GPP TS 36.300) The present document provides an overview and overall description of the E-UTRAN radio interface protocol architecture. Details of the radio interface protocols are specified in companion specifications of the 36 series.

The present document defines the security requirements pertaining to TISPAN NGN Release 3. The present document holds requirements for the various NGN subsystems defined at a stage 1 level. The present document covers security requirements for both the NGN core network, and the NGN access network(s). The main scope of the security requirements for the different subsystems are to identify requirement in the following main areas: •Security Policies. •Authentication, Authorization, Access Control and Accountability. •Identity and Secure Registration. •Communications and Data Security Requirements (including confidentiality, integrity aspects). •Privacy. •Key Management. •NAT/Firewall Interworking. •Availability and DoS protection. •Assurance. •Strength of Security Mechanisms.

This work item aims to define a stage 2, NGN release 3 security architecture. This Work Item shall set forth the specific security architecture for NGN Release 3 using the Release 2 document as a baseline with additions to support the Release 3 functionality as described in the Release 3 definition.

The present document specifies countermeasures to assure that users of the NGN have protection from abuse of identity. This covers authenticity and integrity countermeasures, including use of existing systems, and credential management in support of identity protection. The present document: •identifies the security objectives; •defines the functional requirements (including those from ISO/IEC 15408-2 that apply); •defines the detail requirements for protection of identity in the NGN. In doing so the present document: •defines measures that provide protection of the NGN user identity from malicious traffic analysis; •identifies those measures that allow compliance with the privacy legislation in the regions where the NGN is to be deployed where such legislation is known and public; •identifies in Annex B a number of countermeasures in the form of policies or procedures. The present document follows the recommendations of ES 202 382 and provides an IdM PP Proforma which may be used as a basis for developing a PP for identity protection in an NGN subsystem deployment. The identity protection PP proforma is provided in Annex A.

EC 61499-1:2012 defines a generic architecture and presents guidelines for the use of function blocks in distributed industrial-process measurement and control systems (IPMCSs). This architecture is presented in terms of implementable reference models, textual syntax and graphical representations. The models given in this standard are intended to be generic, domain independent and extensible to the definition and use of function blocks in other standards or for particular applications or application domains. It is intended that specifications written according to the rules given in this standard be concise, implementable, complete, unambiguous, and consistent. This second edition cancels and replaces the first edition published in 2005 an constitutes a technical revision. It includes the significant technical changes with respect to the previous edition related to: Execution control, Temporary variables, Service sequences, the syntax for mapping of FB instances, the Syntax for definition of segment types, the Function block types for interoperation with programmable controllers and the READ/WRITE management commands.

IEC 61499-2:2012 defines requirements for software tools to support the following systems engineering tasks enumerated in IEC 61499-1: - the specification of function block types; - the functional specification of resource types and device types; - the specification, analysis, and validation of distributed IPMCSs; - the configuration, implementation, operation, and maintenance of distributed IPMCSs; - the exchange of information among software tools. This second edition cancels and replaces the first edition published in 2005 and constitutes a technical revision. This edition includes the following significant technical changes with respect to the previous edition: The contents of Annex A have been updated to conform to the technical changes of the second edition of IEC 61499-1. CDATA sections are now allowed for the textual contents of algorithms in Tables A.4 and A.5.

IEC 61499-4:2013 defines rules for the development of compliance profiles, which specify the features of IEC 61499-1 and 61499-2 to be implemented in order to promote the following attributes of IEC 61499-based systems, devices and software tools: - interoperability of devices from multiple suppliers; - portability of software between software tools of multiple suppliers; - and configurability of devices from multiple vendors by software tools of multiple suppliers. This second edition cancels and replaces the first edition published in 2005. It constitutes a technical revision and includes the following significant technical changes: Table B.1 has been updated for consistency with Table 8 of IEC 61499-1:2013.Defines reference models for batch control as used in the process industries and terminology that helps explain the relationships between these models and terms. May not apply to all batch control applications.This part of this standard on batch control defines data models that describe batch control as applied in the process industries, data structures for facilitating communications within and between batch control implementations and language guidelines for representing recipes. Refer to Annex A for an explanation of the UML notation that is used in this part of this standard. Refer to Annex B for a summary of all of the SQL definitions from clause 5.IEC 61512-3:2008 on Batch Control defines a model for general and site recipes; the activities that describe the use of general and site recipes within a company and across companies; a representation of general and site recipes; and a data model of general and site recipes. This first edition cancels and replaces IEC/PAS 61512-3, published in 2004. EC 61512-4:2009 defines a reference model for batch production records containing information about production of batches or elements of batch production. This standard is intended for batch processes.

X

X

X

X

X

X

X

X

X

This pack contains the following:IEC TR 61850-1:2013IEC TS 61850-2:2003IEC 61850-3:2013IEC 61850-4:2011IEC 61850-5:2013IEC 61850-6:2009IEC 61850-7-1:2011IEC 61850-7-2:2010IEC 61850-7-3:2010IEC 61850-7-4:2010IEC 61850-7-410:2012+AMD1:2015 CSVIEC 61850-7-420:2009IEC TR 61850-7-510:2012IEC 61850-8-1:2011IEC 61850-9-2:2011IEC 61850-10:2012IEC TS 61850-80-1:2016IEC TR 61850-80-3:2015IEC TS 61850-80-4:2016IEC TR 61850-90-1:2010IEC TR 61850-90-2:2016IEC TR 61850-90-3:2016IEC TR 61850-90-4:2013IEC TR 61850-90-5:2012IEC TR 61850-90-7:2013IEC TR 61850-90-8:2016IEC TR 61850-90-12:2015IEC/IEEE 61850-9-3:2016

IEC 62325-301:2014 specifies the common information model for energy market communications. The common information model (CIM) is an abstract model that represents all the major objects in an electric utility enterprise typically involved in utility operations and electricity market management. By providing a standard way of representing power system resources as object classes and attributes, along with their relationships, the CIM facilitates the integration of market management system (MMS) applications developed independently by different vendors, between entire MMS systems developed independently, or between an MMS system and other systems concerned with different aspects of market management, such as capacity allocation, day-ahead management, balancing, settlement, etc.IEC 62325-351:2016 specifies a UML package which provides a logical view of the functional aspects of European style market management within an electricity markets. This package is based on the common information model (CIM). The use of the CIM goes far beyond its application in a market management system.

IEC 62325-450:2013 defines how to create a profile from the common information model and the context modelling rules related to this task. This standard is to be applied to the IEC 62325 series. The common information model (CIM) is an abstract model that represents all the major objects in an electric utility enterprise. The CIM IEC 62325-301 caters for the introduction of the objects required for the operation of electricity markets.

IEC 62325-451-1:2017 specifies a UML package for the acknowledgment business process and its associated document contextual model, assembly model and XML schema for use within the European style electricity markets. The relevant aggregate core components (ACCs) defined in IEC 62325-351 have been contextualized into aggregated business information entities (ABIEs) to satisfy the requirements of the European style market acknowledgment business process. The contextualized ABIEs have been assembled into the acknowledgment document contextual model. This new edition includes the following significant technical changes with respect to the previous edition: - addition of an optional attribute ProcessType to the acknowledgement document to ease routing of incoming acknowledgement document instances to the appropriate application; - clarification of the activity diagram for the acknowledgement process; - addition of the list of constraints on datatypes.

IEC 62325-451-2:2014 specifies a UML package for the scheduling business process and its associated document contextual models, assembly models and XML schemas for use within the European style electricity markets. This International Standard is based on the European style market contextual model (IEC 62325-351). The relevant aggregate core components (ACCs) defined in IEC 62325-351 have been contextualised into aggregated business information entities (ABIEs) to satisfy the requirements of the European style market scheduling business process. IEC 62325-451-3:2014 specifies a package for the transmission capacity allocation business process through explicit or implicit auctions and the associated document contextual models, assembly models and XML schema for use within European style markets. This International standard is based on the European style market contextual model (IEC 62325-351). The relevant aggregate core components (ACCs) defined in IEC 62325-351 have been contextualised into aggregated business information entities (ABIEs) to satisfy the requirements of these business processes. The contextualised ABIEs have been assembled into the relevant document contextual models.

IEC 62325-451-4:2014 specifies a package for the settlement and reconciliation business process and the associated document contextual model, assembly model and XML schema for use within European style markets. The relevant aggregate core components (ACCs) defined in IEC 62325-351 have been contextualised into aggregated business information entities (ABIEs) to satisfy the requirements of this business process. The contextualised ABIEs have been assembled into the relevant document contextual models. Related assembly models and XML schema for the exchange of information between market participants are automatically generated from the assembled document contextual models. This International Standard provides a uniform layout for the transmission of aggregated data in order to settle the electricity market.IEC 62325-451-5:2015 is based on the European style market profile (IEC 62325-351) and specifies a package for the problem statement and status request business processes and the associated document contextual models, assembly models and XML schema for use within European style markets. The relevant aggregate core components (ACCs) defined in IEC 62325-351 have been contextualised into aggregated business information entities (ABIEs) to satisfy the requirements of this business process.

X

X

X

X X

X

X X X X

X X X X

IEC 62325-451-6:2016 specifies a UML package for the market information publication business process and its associated document contextual models, assembly models and XML schemas for use within the European style electricity markets. Is based on the European style market contextual model (IEC 62325-351). The relevant aggregate core components defined in IEC 62325-351 have been contextualised into aggregated business information entities to satisfy the requirements of the European style market publication business process.IEC TS 62325-503:2014(E) is a technical specification intended for European electricity markets, and specifies a communication platform which every Transmission System Operator (TSO) in Europe may use to reliably and securely exchange documents for the energy market. Consequently a European market participant (trader, distribution utilities, etc.) could benefit from a single, common, harmonized and secure platform for message exchange with the different TSOs; thus reducing the cost of building different IT platforms to interface with all the parties involved. This also represents an important step in facilitating parties entering into markets other than their national ones. Keyword: deregulation of energy market.

IEC TS 62325-504:2015(E) defines the services needed to support the electronic data interchanges between different actors on the European Energy Market for Electricity (EME) in a fast (near-real-time), and secure way. At the same time, this Technical Specification can also be applied to integration problems outside the scope of IEC 62325-451, such as to the integration of gas market systems or general enterprise integration. Web Services (in WSDL) will be specified for the defined services, applying the Basic Web Service Pattern implementation profile from IEC 61968-100. The services needed to support the electronic data interchange on the European Energy Market for Electricity are:- List Messages;- Get Message;- Put Message. The scope of the IEC 62351 series is information security for power system control operations. The primary objective is to “Undertake the development of standards for security of the communication protocols defined by IEC TC 57, specifically the IEC 60870-5 series, the IEC 60870-6 series, the IEC 61850 series, the IEC 61970 series, and the IEC 61968 series. Undertake the development of standards and/or technical reports on end-to-end security issues.”

Provides an introduction to the remaining parts of the IEC 62351 series, primarily to introduce the reader to various aspects of information security as applied to power system operations. The scope of the IEC 62351 series is information security for power system control operations. Its primary objective is to undertake the development of standards for security of the communication protocols defined by IEC TC 57, specifically the IEC 60870-5 series, the IEC 60870-6 series, the IEC 61850 series, the IEC 61970 series, and the IEC 61968 series. This publication is of core relevance for Smart Grid.

IEC/TR 62351-10:2012(E) targets the description of security architecture guidelines for power systems based on essential security controls, i.e. on security-related components and functions and their interaction. Furthermore, the relation and mapping of these security controls to the general system architecture of power systems is provided as a guideline to support system integrators to securely deploy power generation, transmission, and distribution systems applying available standards.IEC 62351-11:2016 specifies schema, procedures, and algorithms for securing XML documents that are used within the scope of the IEC as well as documents in other domains. This part is intended to be referenced by standards if secure exchanges are required, unless there is an agreement between parties in order to use other recognized secure exchange mechanisms. This part of IEC 62351 utilizes well-known W3C standards for XML document security and provides profiling of these standards and additional extensions. IEC 62351-2:2008 (E) covers the key terms used in the IEC 62351 series, and is not meant to be a definitive list. Most terms used for cyber security are formally defined by other standards organizations, and so are included here with references to where they were originally defined.This publication is of core relevance for Smart Grid.

X X X X

X X X X

X X X X

X X X X

X X X X

X X X X

X X X X

IEC 62351-3:2014 specifies how to provide confidentiality, integrity protection, and message level authentication for SCADA and telecontrol protocols that make use of TCP/IP as a message transport layer when cyber-security is required. Although there are many possible solutions to secure TCP/IP, the particular scope of this part is to provide security between communicating entities at either end of a TCP/IP connection within the end communicating entities. This part of IEC 62351 reflects the security requirements of the IEC power systems management protocols.

Specifies procedures, protocol extensions, and algorithms to facilitate securing ISO 9506 - Manufacturing Message Specification (MMS) based applications. It is intended that this technical specification be referenced as a normative part of other IEC TC 57 standards that have the need for using MMS in a secure manner.This publication is of core relevance for Smart Grid.

IEC/TS 62351-5:2013(E) specifies messages, procedures and algorithms for securing the operation of all protocols based on or derived from IEC 60870-5: Telecontrol equipment and systems - Transmission protocols. This Technical Specification applies to at least those protocols listed in IEC 60870-5-101, 5-102, 5-103, 5-104. This new edition includes the following main changes with respect to the previous edition:- adds the capability to change Update Keys remotely;- adds security statistics to aid in detecting attacks;- adds measures to avoid being forced to change session keys too often;- discards unexpected messages more often as possible attacks;- adds to the list of permitted security algorithms;- adds new rules for calculating challenge sequence numbers.

Specifies messages, procedures, and algorithms for securing the operation of all protocols based on or derived from the standard IEC 61850. Applies to at least those protocols of IEC 61850-8-1, IEC 61850-9-2 and IEC 61850-6. This publication is of core relevance for Smart Grid.

IEC/TS 62351-7:2010(E) defines network and system management (NSM) data object models that are specific to power system operations. These NSM data objects are used to monitor the health of networks and systems, to detect possible security intrusions, and to manage the performance and reliability of the information infrastructure.This publication is of core relevance for Smart Grid.

IEC/TS 62351-8:2011(E) covers the access control of users and automated agents to data objects in power systems by means of role-based access control. The scope of this specification covers everything that is needed for interoperability between systems from different vendors.

IEC TR 62351-12:2016(E) discusses cyber security recommendations and engineering/operational strategies for improving the resilience of power systems with interconnected Distributed Energy Resources (DER) systems. It covers the resilience requirements for the many different stakeholders of these dispersed cyber-physical generation and storage devices, with the goal of enhancing the safety, reliability, power quality, and other operational aspects of power systems, particularly those with high penetrations of DER systems. It addresses the resilience issues for cyber-physical DER systems interconnected with the power grid, building on the concepts and the hierarchical architecture described in the Smart Grid Interoperability Panel (SGIP) draft DRGS Subgroup B White Paper - Categorizing Use Cases in Hierarchical DER Systems.

X X X X

X X X X

X X X X

X

X

X X X X

X

X X

X

Network and application protocol conformance test X

IEC TR 62351-13:2016(E) provides guidelines on what security topics could or should be covered in standards and specifications (IEC or otherwise) that are to be used in the power industry, and the audience is therefore the developers of standards and specifications. These guidelines cannot be prescriptive for every standard, since individual standards and specifications may legitimately have very different focuses, but it should be expected that the combination of such standards and specifications used in any implementation should cover these security topics. These guidelines are therefore to be used as a checklist for the combination of standards and specifications used in implementations of systems.

IEC TR 62357-1:2016(E) provides a clear and comprehensive map of all standards which are contributing to support interactions, in an open and interoperable way, between actors, components and systems in the field of electricity grids from generation to consumers, including transmission and distribution. The document also brings the vision of the path which will be followed by the concerned IEC technical committees and working groups in the coming years, to improve the global efficiency, market relevancy and coverage of this series of standards. This second edition includes the following significant technical changes with respect to the previous edition:- it provides updates and defines layered Reference Architecture to help direct longer term goals and activities, specifically to ensure compatibility of all new standards developed in the IEC by benefitting from lessons learned during development of the current standards and their application to actual utility projects as well as through application of other internationally recognized architecture standards.- It reflects the most recent editions of the IEC standards relating to power systems management and associated information exchange, including the IEC 61850 series and the IEC 61968, IEC 61970 and IEC 62325 Common Information Model (CIM) standards.

IEC TR 62357-200:2015(E) applies to information exchange in power systems including, but not restricted to, substations, control centre, maintenance centre, energy management systems, synchrophasor-based grid stability systems, bulk energy generation, distributed energy generation (renewables), energy storage, load management. It addresses the issues encountered when migrating from Internet Protocol version 4 (IPv4) to Internet Protocol version 6 (IPv6). It describes migration strategies, covering impact on applications, communication stack, network nodes, configuration, address allocation, cyber security and the related management. This Technical Report considers backward compatibility and show concepts as well as necessary migration paths to IPv6 from IPv4 where necessary, for a number of protocols in the IEC 61850 framework.IEC 62361-100:2016 describes a mapping from CIM profiles to W3C XML Schemas, intended to facilitate the exchange of information in the form of XML documents whose semantics are defined by the IEC CIM and whose syntax is defined by a W3C XML schema.IEC 62361-2:2013 documents the quality codes used by existing IEC standards related to supervisory control and data acquisition (SCADA) in the field of power systems management. Meter reading quality coding is not considered to be in the scope of this version of the document. It determines and documents mapping between these standards. Eventual loss of quality information that might occur in mapping is documented. A cohesive and common list of quality codes with semantics is defined. The identified standards to be dealt with in this document are: IEC 60870-5, IEC 60870-6 TASE.2, IEC 61850, IEC 61970, DAIS DA, OPC DA and OPC UA.

IEC 62443-3-3:2013(E) provides detailed technical control system requirements (SRs) associated with the seven foundational requirements (FRs) described in IEC 62443-1-1 including defining the requirements for control system capability security levels, SL-C(control system). These requirements would be used by various members of the industrial automation and control system (IACS) community along with the defined zones and conduits for the system under consideration (SuC) while developing the appropriate control system target SL, SL-T(control system), for a specific asset. The contents of the corrigendum of April 2014 have been included in this copy.

ISO 15118 specifies the communication between Electric Vehicles (EV), including Battery Electric Vehicles and Plug-In Hybrid Electric Vehicles, and the Electric Vehicle Supply Equipment (EVSE). As the communication parts of this generic equipment are the Electric Vehicle Communication Controller (EVCC) and the Supply Equipment Communication Controller (SECC), ISO 15118 describes the communication between these components. Although ISO 15118 is oriented to the charging of electric road vehicles, it is open for other vehicles as well. ISO 15118-1:2013 specifies terms and definitions, general requirements and use cases as the basis for the other parts of ISO 15118. It provides a general overview and a common understanding of aspects influencing the charge process, payment and load levelling. ISO 15118 does not specify the vehicle internal communication between battery and charging equipment and the communication of the SECC to other actors and equipment (beside some dedicated message elements related to the charging). All connections beyond the SECC, and the method of message exchanging are considered to be out of the scope as specific use cases.

SO 15118-2:2014 specifies the communication between battery electric vehicles (BEV) or plug-in hybrid electric vehicles (PHEV) and the Electric Vehicle Supply Equipment. The application layer message set defined in ISO 15118-2:2014 is designed to support the energy transfer from an EVSE to an EV. ISO 15118-1 contains additional use case elements describing the bidirectional energy transfer. The implementation of these use cases requires enhancements of the application layer message set defined herein.The purpose of ISO 15118-2:2014 is to detail the communication between an EV (BEV or a PHEV) and an EVSE. Aspects are specified to detect a vehicle in a communication network and enable an Internet Protocol (IP) based communication between EVCC and SECC.ISO 15118-2:2014 defines messages, data model, XML/EXI based data representation format, usage of V2GTP, TLS, TCP and IPv6. In addition, it describes how data link layer services can be accessed from a layer 3 perspective. The Data Link Layer and Physical Layer functionality is described in ISO 15118-3.

ISO 15118-3:2015 specifies the requirements of the physical and data link layer for a high-level communication, directly between battery electric vehicles (BEV) or plug-in hybrid electric vehicles (PHEV), termed as EV (electric vehicle) [ISO-1], based on a wired communication technology and the fixed electrical charging installation [Electric Vehicle Supply Equipment (EVSE)] used in addition to the basic signalling, as defined in [IEC-1].It covers the overall information exchange between all actors involved in the electrical energy exchange. ISO 15118 (all parts) is applicable for manually connected conductive charging.Only "[IEC-1] modes 3 and 4" EVSEs, with a high-level communication module, are covered by this part of ISO 15118.

Physical layer and data link layer conformance test X

General information and use-case definition for wireless communication X

Network and application protocol requirements for wireless communication X X

Physical layer and data link layer requirements for wireless communication X

X

X

The home electronic system (HES) provides a common method for interfacing equipment with a variety of home control systems (HCS) such as sensors, actuators, appliances, user interfaces, controllers, switches etc. An HCS is a local area network specialized for residential communications, commonly called home automation.

ISO 16484-1:2010 specifies guiding principles for project design and implementation and for the integration of other systems into the building automation and control systems (BACS).ISO 16484-1:2010 specifies the phases required for the BACS project, including: design (determination of project requirements and production of design documents including technical specifications), engineering (detailed function and hardware design), installation (installing and commissioning of the BACS), and completion (handover, acceptance and project finalization).ISO 16484-1:2010 also specifies the requirements for as-built documentation and training. ISO 16484-1:2010 is not applicable to operation and maintenance, nor is it applicable to retro or continuous commissioning, including a commissioning authority.

X

X

X

ISO 16484-2:2004 specifies the requirements for the hardware to perform the tasks within a building automation and control system (BACS). It provides the terms, definitions and abbreviations for the understanding of ISO 16484-2 and ISO 16484-3. ISO 16484-2:2004 relates only to physical items/devices, i.e. devices for management functions, operator stations and other human system interface devices; controllers, automation stations and application specific controllers; field devices and their interfaces; cabling and interconnection of devices; engineering and commissioning tools.ISO 16484-2:2004 shows a generic system model to which all different types of BACS and their interconnections (BACS network) can fit. A graphical concept of the BACS network in terms of LAN topology will be provided in ISO 16484-5.

ISO 16484-3:2005 specifies the requirements for the overall functionality and engineering services to achieve building automation and control systems. It defines terms, which shall be used for specifications and it gives guidelines for the functional documentation of project/application specific systems. It provides a sample template for documentation of plant/application specific functions, called BACS points list.The informative function block examples explain a method to display the referenced functions in system documentation; they do not standardize the method for programming functions and applications.ISO 16484-3:2005 covers requirements and definitions regarding BACS and application software, generic functions for plant/project specific applications and engineering functions for building controls and operations. It provides communication functions for the integration of other dedicated special system processes.ISO 16484-3:2005 defines a method for specifying the procurement specifications containing all essential elements required for the operational functioning of a BACS. The successful installation and operation of a BACS requires that its procurement be based on a complete and accurate functional specification.

Project specification and implementation, Hardware, Functions, Control Applications, Data communication protocol, Data communication conformance testing, Contribution of BACS to energy performance of buildings

X

X

X

ISO 16484-5:2014 defines data communication services and protocols for computer equipment used for monitoring and control of heating, ventilation, air-conditioning and refrigeration (HVAC&R) and other building systems. It defines, in addition, an abstract, object-oriented representation of information communicated between such equipment, thereby facilitating the application and use of digital control technology in buildings.It provides a comprehensive set of messages for conveying encoded binary, analog, and alphanumeric data between devices including, but not limited to, hardware binary input and output values, hardware analog input and output values,software binary and analog values, text string values, schedule information, alarm and event information, files, and control logic.It models each building automation and control computer as a collection of data structures called "objects," the properties of which represent various aspects of the hardware, software, and operation of the device. These objects provide a means of identifying and accessing information without requiring knowledge of the details of the device's internal design or configuration.

ISO 16484-6:2014 defines a standard method for verifying that an implementation of the BACnet protocol provides each capability claimed in its Protocol Implementation Conformance Statement (PICS) in conformance with the BACnet standard.ISO 16484-6:2014 provides a comprehensive set of procedures for verifying the correct implementation of each capability claimed on a BACnet PICS, including support of each claimed BACnet service, either as an initiator, executor, or both, support of each claimed BACnet object-type, including both required properties and each claimed optional property,support of the BACnet network layer protocol,support of each claimed data link option, andsupport of all claimed special functionality.

ISO/IEC/TR 29108:2013(E) specifies the terminology recommended for future use in International Standards and other specifications for intelligent homes. In addition, it provides a collection of terms and definitions as already used and defined in relevant International Standards, Technical Specifications, Technical Reports and Recommendations developed by ISO, IEC, and ITU-T.

X

X

X

ISO/IEC TR 27019:2013 provides guiding principles based on ISO/IEC 27002 for information security management applied to process control systems as used in the energy utility industry. The aim of ISO/IEC TR 27019:2013 is to extend the ISO/IEC 27000 set of standards to the domain of process control systems and automation technology, thus allowing the energy utility industry to implement a standardized information security management system (ISMS) in accordance with ISO/IEC 27001 that extends from the business to the process control level.The scope of ISO/IEC TR 27019:2013 covers process control systems used by the energy utility industry for controlling and monitoring the generation, transmission, storage and distribution of electric power, gas and heat in combination with the control of supporting processes. This includes in particular the following systems, applications and components: the overall IT-supported central and distributed process control, monitoring and automation technology as well as IT systems used for their operation, such as programming and parameterization devices; digital controllers and automation components such as control and field devices or PLCs, including digital sensor and actuator elements; all further supporting IT systems used in the process control domain, e.g. for supplementary data visualization tasks and for controlling, monitoring, data archiving and documentation purposes; the overall communications technology used in the process control domain, e.g. networks, telemetry, telecontrol applications and remote control technology; digital metering and measurement devices, e.g. for measuring energy consumption, generation or emission values; digital protection and safety systems, e.g. protection relays or safety PLCs; distributed components of future smart grid environments; all software, firmware and applications installed on above mentioned systems.Outside the scope of ISO/IEC TR 27019:2013 is the conventional or classic control equipment that is non-digital, i.e. purely electro-mechanical or electronic monitoring and process control systems. Furthermore, energy process control systems in private households and other, comparable residential building installations are outside the scope of ISO/IEC TR 27019:2013.Telecommunication systems and components used in the process control environment are also not directly part of the scope of ISO/IEC TR 27019:2013. These are covered by ISO/IEC 27011:2008.

ISO/IEC 19790:2012 the security requirements for a cryptographic module utilised within a security system protecting sensitive information in computer and telecommunication systems. This International Standard defines four security levels for cryptographic modules to provide for a wide spectrum of data sensitivity (e.g. low value administrative data, million dollar funds transfers, life protecting data, personal identity information, and sensitive information used by government) and a diversity of application environments (e.g. a guarded facility, an office, removable media, and a completely unprotected location). This International Standard specifies four security levels for each of 11 requirement areas with each security level increasing security over the preceding level.ISO/IEC 19790:2012 specifies security requirements specified intended to maintain the security provided by a cryptographic module and compliance to this International Standard is not sufficient to ensure that a particular module is secure or that the security provided by the module is sufficient and acceptable to the owner of the information that is being protected.

This International Standard specifies the behaviour of a service that provides transactions on and access to geographic features in a manner independent of the underlying data store.

X

X

X X

X X

X X

X X

X

This International Standard is applicable whenever representation of dates in the Gregorian calendar, times in the 24-hour timekeeping system, time intervals and recurring time intervals or of the formats of these representations are included in information interchange.

ISO/IEC 12139-1:2009 is a physical and medium access control layer specification with respect to the connectivity for In-home and Access network high speed powerline communication stations.ISO/IEC 12139-1:2009 provides functional requirements and specification of the physical and medium access control layer for high speed powerline communication devices, and does not include specific implementation methods.

SO/IEC 27001:2013 specifies the requirements for establishing, implementing, maintaining and continually improving an information security management system within the context of the organization. It also includes requirements for the assessment and treatment of information security risks tailored to the needs of the organization. The requirements set out in ISO/IEC 27001:2013 are generic and are intended to be applicable to all organizations, regardless of type, size or nature.ISO/IEC 27002:2013 gives guidelines for organizational information security standards and information security management practices including the selection, implementation and management of controls taking into consideration the organization's information security risk environment(s). It is designed to be used by organizations that intend to: select controls within the process of implementing an Information Security Management System based on ISO/IEC 27001; implement commonly accepted information security controls; develop their own information security management guidelines.

ISO/IEC 27009:2016 defines the requirements for the use of ISO/IEC 27001 in any specific sector (field, application area or market sector). It explains how to include requirements additional to those in ISO/IEC 27001, how to refine any of the ISO/IEC 27001 requirements, and how to include controls or control sets in addition to ISO/IEC 27001:2013, Annex A.It ensures that additional or refined requirements are not in conflict with the requirements in ISO/IEC 27001.It is applicable to those involved in producing sector-specific standards that relate to ISO/IEC 27001.

ISO 29190:2015 provides organizations with high-level guidance about how to assess their capability to manage privacy-related processes. In particular, it- specifies steps in assessing processes to determine privacy capability,- specifies a set of levels for privacy capability assessment,- provides guidance on the key process areas against which privacy capability can be assessed,- provides guidance for those implementing process assessment, and- provides guidance on how to integrate the privacy capability assessment into organizations operations.

Cancels and replaces the first edition (1984). The model provides a common basis for the coordination of standards development for the purpose of systems interconnection, while allowing existing standards to be placed into perspective within the overall Reference Model. The model identifies areas for developing or improving standards. It does not intend to serve as an implementation specification.

IEC 61588:2009(E) defines a protocol enabling precise synchronization of clocks in measurement and control systems implemented with technologies such as network communication, local computing, and distributed objects. The protocol is applicable to systems communicating by local area networks supporting multicast messaging including, but not limited to, Ethernet. The protocol enables heterogeneous systems that include clocks of various inherent precision, resolution, and stability to synchronize to a grandmaster clock. The protocol supports system-wide synchronization accuracy in the sub-microsecond range with minimal network and local clock computing resources. The default behavior of the protocol allows simple systems to be installed and operated without requiring the administrative attention of users. The standard includes mappings to User Datagram Protocol (UDP)/Internet Protocol (IP), DeviceNet, and a layer-2 Ethernet implementation. It includes formal mechanisms for message extensions, higher sampling rates, correction for asymmetry, a clock type to reduce error accumulation in large topologies, and specifications on how to incorporate the resulting additional data into the synchronization protocol. This second edition cancels and replaces the first edition published in 2004. It constitutes a technical revision.

Notes LINK Typology

http://www.etsi.org/deliver/etsi_ts/121100_121199/121101/10.01.00_60/ts_121101v100100p.pdfEuropean Standard


https://www.en-standard.eu/csn-en-13321-1-open-data-communication-in-building-automation-controls-and-building-management-home-and-building-electronic-system-part-1-product-and-system-requirements/European Standard

https://www.en-standard.eu/csn-en-13321-2-open-data-communication-in-building-automation-controls-and-building-management-home-and-building-electronic-systems-part-2-knxnet-ip-communication/European Standard

https://www.en-standard.eu/csn-en-13757-1-communication-systems-for-meters-part-1-data-exchange/European Standard

https://www.en-standard.eu/csn-en-13757-2-communication-systems-for-and-remote-reading-of-meters-part-2-physical-and-link-layer/European Standard

https://www.en-standard.eu/csn-en-13757-3-communication-systems-for-and-remote-reading-of-meters-part-3-dedicated-application-layer/European Standard

https://www.en-standard.eu/csn-en-13757-4-communication-systems-for-meters-and-remote-reading-of-meters-part-4-wireless-meter-readout-radio-meter-reading-for-operation-in-srd-bands/European Standard

https://www.en-standard.eu/csn-en-13757-5-communication-systems-for-meters-part-5-wireless-m-bus-relaying/European Standard

https://www.en-standard.eu/csn-en-13757-6-communication-systems-for-meters-part-6-local-bus-2/European Standard

http://www.etsi.org/deliver/etsi_ts/121100_121199/121101/10.01.00_60/ts_121101v100100p.pdf


https://www.en-standard.eu/csn-en-13321-1-open-data-communication-in-building-automation-controls-and-building-management-home-and-building-electronic-system-part-1-product-and-system-requirements/

https://www.en-standard.eu/csn-en-13321-2-open-data-communication-in-building-automation-controls-and-building-management-home-and-building-electronic-systems-part-2-knxnet-ip-communication/

https://www.en-standard.eu/csn-en-13757-1-communication-systems-for-meters-part-1-data-exchange/

https://www.en-standard.eu/csn-en-13757-2-communication-systems-for-and-remote-reading-of-meters-part-2-physical-and-link-layer/

https://www.en-standard.eu/csn-en-13757-3-communication-systems-for-and-remote-reading-of-meters-part-3-dedicated-application-layer/

https://www.en-standard.eu/csn-en-13757-4-communication-systems-for-meters-and-remote-reading-of-meters-part-4-wireless-meter-readout-radio-meter-reading-for-operation-in-srd-bands/

https://www.en-standard.eu/csn-en-13757-5-communication-systems-for-meters-part-5-wireless-m-bus-relaying/

https://www.en-standard.eu/csn-en-13757-6-communication-systems-for-meters-part-6-local-bus-2/

https://www.en-standard.eu/din-en-14908-1-firmenneutrale-datenkommunikation-fur-die-gebaudeautomation-und-gebaudemanagement-gebaude-netzwerk-protokoll-teil-1-datenprotokollschichtenmodell-englische-fassung-en-14908-1-2014/European Standard

Statement in the national foreword of E DIN 14908-2_2012-10: Further parts will describe functions, profiles and conformance testing

https://www.en-standard.eu/din-en-14908-2-open-data-communication-in-building-automation-controls-and-building-management-control-network-protocol-part-2-twisted-pair-communication-english-version-en-14908-2-2014/European Standard

Test circuits for determining transmit amplitude, effective receiver impedance and receiver performance; Tests designed to measure PL transceiver’s immunity to interference at various frequencies, frequency notches in the power line and to impulsive noise such as produced by triaccontrolled dimmers

https://www.en-standard.eu/din-en-14908-3-firmenneutrale-datenkommunikation-fur-die-gebaudeautomation-und-gebaudemanagement-gebaude-netzwerk-protokoll-teil-3-kommunikation-uber-die-stromversorgungsleitungen-englische-fassung-en-14908-3-2014/European Standard

https://www.en-standard.eu/din-en-14908-4-firmenneutrale-datenkommunikation-fur-die-gebaudeautomation-und-gebaudemanagement-gebaude-netzwerk-protokoll-teil-4-kommunikation-mittels-internet-protokoll-ip-englische-fassung-en-14908-4-2014/European Standard

https://www.en-standard.eu/csn-en-14908-5-open-data-communication-in-building-automation-controls-and-building-management-implementation-guideline-control-network-protocol-part-5-implementation/European Standard

https://www.en-standard.eu/csn-en-14908-6-open-data-communication-in-building-automation-controls-and-building-management-control-network-protocol-part-6-application-elements-1/European Standard

https://www.en-standard.eu/csn-en-50090-1-home-and-building-electronic-systems-hbes-part-1-standardization-structure/European Standard

https://www.en-standard.eu/din-en-50090-3-1-elektrische-systemtechnik-fur-heim-und-gebaude-eshg-teil-3-1-anwendungsaspekte-einfuhrung-in-die-anwendungsstruktur-deutsche-fassung-en-50090-3-1-1994/European Standard

https://www.en-standard.eu/din-en-50090-3-2-home-and-building-electronic-systems-hbes-part-3-2-aspects-of-application-user-process-for-hbes-class-1-german-version-en-50090-3-2-2004-text-english/European Standard

https://www.en-standard.eu/din-en-14908-1-firmenneutrale-datenkommunikation-fur-die-gebaudeautomation-und-gebaudemanagement-gebaude-netzwerk-protokoll-teil-1-datenprotokollschichtenmodell-englische-fassung-en-14908-1-2014/

https://www.en-standard.eu/din-en-14908-2-open-data-communication-in-building-automation-controls-and-building-management-control-network-protocol-part-2-twisted-pair-communication-english-version-en-14908-2-2014/

https://www.en-standard.eu/din-en-14908-3-firmenneutrale-datenkommunikation-fur-die-gebaudeautomation-und-gebaudemanagement-gebaude-netzwerk-protokoll-teil-3-kommunikation-uber-die-stromversorgungsleitungen-englische-fassung-en-14908-3-2014/

https://www.en-standard.eu/din-en-14908-4-firmenneutrale-datenkommunikation-fur-die-gebaudeautomation-und-gebaudemanagement-gebaude-netzwerk-protokoll-teil-4-kommunikation-mittels-internet-protokoll-ip-englische-fassung-en-14908-4-2014/

https://www.en-standard.eu/csn-en-14908-5-open-data-communication-in-building-automation-controls-and-building-management-implementation-guideline-control-network-protocol-part-5-implementation/

https://www.en-standard.eu/csn-en-14908-6-open-data-communication-in-building-automation-controls-and-building-management-control-network-protocol-part-6-application-elements-1/

https://www.en-standard.eu/csn-en-50090-1-home-and-building-electronic-systems-hbes-part-1-standardization-structure/

https://www.en-standard.eu/din-en-50090-3-1-elektrische-systemtechnik-fur-heim-und-gebaude-eshg-teil-3-1-anwendungsaspekte-einfuhrung-in-die-anwendungsstruktur-deutsche-fassung-en-50090-3-1-1994/

https://www.en-standard.eu/din-en-50090-3-2-home-and-building-electronic-systems-hbes-part-3-2-aspects-of-application-user-process-for-hbes-class-1-german-version-en-50090-3-2-2004-text-english/

https://www.en-standard.eu/din-en-50090-3-3-home-and-building-electronic-systems-hbes-part-3-3-aspects-of-application-hbes-interworking-model-and-common-hbes-data-types-english-version-en-50090-3-3-2009/European Standard

https://www.en-standard.eu/csn-en-50090-4-1-home-and-building-electronic-systems-hbes-part-4-1-media-independent-layers-application-layer-for-hbes-class-1/European Standard

https://www.en-standard.eu/csn-en-50090-4-2-home-and-building-electronic-systems-hbes-part-4-2-media-independent-layers-transport-layer-network-layer-and-general-parts-of-data-link-layer-for-hbes-class-1/European Standard

https://www.en-standard.eu/csn-en-50090-4-3-ed-2-home-and-building-electronic-systems-hbes-part-4-3-media-independent-layers-communication-over-ip/European Standard

https://www.en-standard.eu/csn-en-50090-5-1-home-and-building-electronic-systems-hbes-part-5-1-media-and-media-dependent-layers-power-line-for-hbes-class-1/European Standard

https://www.en-standard.eu/csn-en-50090-5-2-home-and-building-electronic-systems-hbes-part-5-2-media-and-media-dependent-layers-network-based-on-hbes-class-1-twisted-pair/European Standard

https://www.en-standard.eu/csn-en-50090-5-3-ed-2-home-and-building-electronic-systems-hbes-part-5-3-media-and-media-dependent-layers-radio-frequency-for-hbes-class-1-2/European Standard

https://www.en-standard.eu/csn-en-50090-7-1-home-and-building-electronic-systems-hbes-part-7-1-system-management-management-procedures/European Standard

https://www.en-standard.eu/csn-en-50090-8-home-and-building-electronic-systems-hbes-part-8-conformity-assessment-of-products/European Standard

Measuring methods of the radio-frequency emission (radio disturbance suppression) of information technology equipment (ITE) (Method of measurement of conducted disturbance at mains terminals and telecommunication ports, Method of measurement of radiated disturbance).SGCG Report v1.72 Gap 3 - Com-2

http://www.cenelec.eu/dyn/www/f?p=104%3A110%3A755476764014601%3A%3A%3A%3AFSP_ORG_ID%2CFSP_PROJECT%2CFSP_LANG_ID%3A1258289%2C42105%2C25European Standard

https://www.en-standard.eu/din-en-50090-3-3-home-and-building-electronic-systems-hbes-part-3-3-aspects-of-application-hbes-interworking-model-and-common-hbes-data-types-english-version-en-50090-3-3-2009/

https://www.en-standard.eu/csn-en-50090-4-1-home-and-building-electronic-systems-hbes-part-4-1-media-independent-layers-application-layer-for-hbes-class-1/

https://www.en-standard.eu/csn-en-50090-4-2-home-and-building-electronic-systems-hbes-part-4-2-media-independent-layers-transport-layer-network-layer-and-general-parts-of-data-link-layer-for-hbes-class-1/

https://www.en-standard.eu/csn-en-50090-4-3-ed-2-home-and-building-electronic-systems-hbes-part-4-3-media-independent-layers-communication-over-ip/

https://www.en-standard.eu/csn-en-50090-5-1-home-and-building-electronic-systems-hbes-part-5-1-media-and-media-dependent-layers-power-line-for-hbes-class-1/

https://www.en-standard.eu/csn-en-50090-5-2-home-and-building-electronic-systems-hbes-part-5-2-media-and-media-dependent-layers-network-based-on-hbes-class-1-twisted-pair/

https://www.en-standard.eu/csn-en-50090-5-3-ed-2-home-and-building-electronic-systems-hbes-part-5-3-media-and-media-dependent-layers-radio-frequency-for-hbes-class-1-2/

https://www.en-standard.eu/csn-en-50090-7-1-home-and-building-electronic-systems-hbes-part-7-1-system-management-management-procedures/

https://www.en-standard.eu/csn-en-50090-8-home-and-building-electronic-systems-hbes-part-8-conformity-assessment-of-products/

http://www.cenelec.eu/dyn/www/f?p=104%3A110%3A755476764014601%3A%3A%3A%3AFSP_ORG_ID%2CFSP_PROJECT%2CFSP_LANG_ID%3A1258289%2C42105%2C25

https://webstore.iec.ch/publication/3749






Immunity test requirements in relation to continuous and transient conducted and radiated disturbances, including electrostatic discharges (ESD) for information technology equipment (ITE).

http://www.cenelec.eu/dyn/www/f?p=104%3A110%3A872969967952801%3A%3A%3A%3AFSP_ORG_ID%2CFSP_PROJECT%2CFSP_LANG_ID%3A1258289%2C52850%2C25European Standard

https://webstore.iec.ch/publication/3747 International Standard


International Standard






http://www.cenelec.eu/dyn/www/f?p=104%3A110%3A872969967952801%3A%3A%3A%3AFSP_ORG_ID%2CFSP_PROJECT%2CFSP_LANG_ID%3A1258289%2C52850%2C25













refines the application layer protocol to meet interoperability requirements















Performance tests - White noise BER tests / Narrowband interferer BER tests / Impulsive noise BER tests









EMI immunity https://webstore.iec.ch/publication/6010

by 61850-10 https://webstore.iec.ch/publication/6013

Data used for testing https://webstore.iec.ch/publication/6014



partly by 61850-10 https://webstore.iec.ch/publication/23693






partly by 61850-10SGCG Report v1.72 Gap 8 - Gen-1 / Dis-2



partly by 61850-10SGCG Report v1.72 Gap 10 - Gen-3 / Ind-2 / HB-2





by 61850-10

Withdrawn


https://webstore.iec.ch/publication/20084&preview=1International Standard

https://www.cenelec.eu/dyn/www/f?p=104:110:1208255120866001::::FSP_ORG_ID,FSP_PROJECT,FSP_LANG_ID:1258723,49776,25European Standard




https://webstore.iec.ch/publication/20084&preview=1

https://www.cenelec.eu/dyn/www/f?p=104:110:1208255120866001::::FSP_ORG_ID,FSP_PROJECT,FSP_LANG_ID:1258723,49776,25











SGCG Report v1.72 Gap 9 - Gen-2 / SM-1 / Ind-1 https://www.cenelec.eu/dyn/www/f?p=104:110:1208255120866001::::FSP_ORG_ID,FSP_PROJECT,FSP_LANG_ID:1258723,45030,25European

Standard








DRAFT







European Standard








DRAFT


European Standard


DLMS UA Yellow book -> conformance testingSGCG Report v1.72 Gap 26 - Other-1SGCG Report v1.72 Gap 27 - Other-2















DRAFT


SGCG Report v1.72 Gap 9 - Gen-2 / SM-1 / Ind-1Part 6-2 replaces part 62






Part 1 Chapter 4.2 Conformance tests https://www.cenelec.eu/dyn/www/f?p=104:110:1208255120866001::::FSP_ORG_ID,FSP_PROJECT,FSP_LANG_ID:1257871,54575,25European

Standard




















Certification software OPC Compliance Test is provided to OPC-members for free and ensures compatibility. Suppliers of OPC-servers are able to test their server already during development. The software tests the complete OPC-functionality, simulates malfunction of a client and checks all error codes. Link OPC UA Compliance & Certification: http://www.opcfoundation.org/Default.aspx/Compliance-Certification/Compliance.asp?MID=Compliance

















DRAFT

https://www.iso.org/standard/43759.html





EN 50491-7: Interoperability (between HBES systems)not releasedSGCG Report v1.72 Gap 23 - Ind-3

http://standards.globalspec.com/std/9931626/cenelec-en-50491-11European Standard

http://standards.globalspec.com/std/9871103/dsf-pren-50491-12European Standard

ftp://ftp.cen.eu/cen/Sectors/List/Measurement/Smartmeters/CENCLCETSI_TR50572.pdf

European Standard


Added as ETSI EG 203 387 (listed in FSS) doesn't exist, seems to be typing error.

http://www.etsi.org/deliver/etsi_eg/202300_202399/202387/01.01.01_60/eg_202387v010101p.pdfEuropean Standard





http://standards.globalspec.com/std/9931626/cenelec-en-50491-11

http://standards.globalspec.com/std/9871103/dsf-pren-50491-12

http://www.etsi.org/deliver/etsi_eg/202300_202399/202387/01.01.01_60/eg_202387v010101p.pdf

DRAFT

DRAFT

The document examines and gives guidance on the use of the Composition assurance class in order to be able to answer the question: "if components A and B are evaluated as having security ratings X and Y what is the security rating that can be assigned to the combination of A and B?"6.4.5 Base TOE testing6.4.5.1 Interface testing (ACO_TBT.1)

http://www.etsi.org/deliver/etsi_eg/202500_202599/202549/01.01.01_60/eg_202549v010101p.pdfEuropean Standard

http://www.etsi.org/deliver/etsi_en/301500_301599/301502/10.01.01_20/en_301502v100101c.pdfEuropean Standard

http://www.etsi.org/deliver/etsi_en/301500_301599/301511/12.01.10_20/en_301511v120110a.pdfEuropean Standard

http://www.etsi.org/deliver/etsi_en/301900_301999/30190801/11.01.01_60/en_30190801v110101p.pdfEuropean Standard

http://www.etsi.org/deliver/etsi_en/303200_303299/303204/02.01.00_20/en_303204v020100a.pdf

European Standard



Conformance to the present document is established by successful evaluation to the requirements of ISO/IEC 15408-3

http://www.etsi.org/deliver/etsi_es/202300_202399/202382/01.01.01_60/es_202382v010101p.pdfEuropean Standard

http://www.etsi.org/deliver/etsi_eg/202500_202599/202549/01.01.01_60/eg_202549v010101p.pdf

http://www.etsi.org/deliver/etsi_en/301500_301599/301502/10.01.01_20/en_301502v100101c.pdf


http://www.etsi.org/deliver/etsi_en/301900_301999/30190801/11.01.01_60/en_30190801v110101p.pdf



http://www.etsi.org/deliver/etsi_es/202300_202399/202382/01.01.01_60/es_202382v010101p.pdf

Conformance to the present document is established by successful evaluation to the requirements of ISO/IEC 15408-3

http://www.etsi.org/deliver/etsi_es/202300_202399/202383/01.01.01_60/es_202383v010101p.pdfEuropean Standard

http://www.etsi.org/deliver/etsi_etr/200_299/237/01_60/etr_237e01p.pdfEuropean Standard

http://www.etsi.org/deliver/etsi_etr/300_399/332/01_60/etr_332e01p.pdfEuropean Standard

http://www.etsi.org/WebSite/document/Technologies/ETSI-WP1_Security.pdfEuropean Standard

http://www.etsi.org/deliver/etsi_tr/102400_102499/102419/01.01.01_60/tr_102419v010101p.pdfEuropean Standard



http://www.etsi.org/deliver/etsi_es/202300_202399/202383/01.01.01_60/es_202383v010101p.pdf

http://www.etsi.org/deliver/etsi_etr/200_299/237/01_60/etr_237e01p.pdf

http://www.etsi.org/deliver/etsi_etr/300_399/332/01_60/etr_332e01p.pdf

http://www.etsi.org/WebSite/document/Technologies/ETSI-WP1_Security.pdf

http://www.etsi.org/deliver/etsi_tr/102400_102499/102419/01.01.01_60/tr_102419v010101p.pdf































Integrity Validation (Ival) test

Integrity Validation (Ival) test




































































European Standard


European Standard


European Standard




https://webstore.iec.ch/publication/5531 European Standard













https://www.cenelec.eu/dyn/www/f?p=104:110:1553318199435101::::FSP_PROJECT,FSP_LANG_ID:62470,25European Standard









https://www.cenelec.eu/dyn/www/f?p=104:110:1553318199435101::::FSP_PROJECT,FSP_LANG_ID:62470,25




































DRAFT - NDIS https://www.iso.org/standard/61724.html







https://www.iso.org/standard/55365.html International Standard












DRAFT https://www.iso.org/standard/61725.html
































https://www.iso.org/iso-8601-date-and-time-format.html







9 Compliance and Consistency with this reference model https://www.iso.org/standard/20269.html International

Standard







x x

x x

x

x

x

x

x

x

x

x

Use Case Energy1

Use Case Energy2

N1

Building Energy Management System Use

O1

Smart Grids and Smart Meters

x x

x x

x x

x x

x x

x x

x

x

x

x

x

x

x

x

x

x

x

x

x x

x x

x

x

x

x

x x

x x

x x

x x

x x

x x

x x

x x

x x

x

x x

x x

x x

x x

x x

x x

x x

x x

x x

x x

x x

x x

x x

x x

x x

x x

x

x

x

x

x x

x x

x x

x x

x x

x x

x x

x x

x x

x x

x

x

x

x

x

x

x

x

x

x

x

x

x

x

x

x x

x

x

x

x

x

x

x

x

x

x

x x

x x

x x

x x

x x

x x

x x

x x

x x

x x

x x

x x

x x

x x

x x

x x

x x

x x

x x

x x

x x

x x

x x

x

x

x

x

x

x

x x

x x

x x

x x

x x

x x

x x

x x

x x

x x

x x

x x

x x

x x

x x

x x

x x

x x

x x

x x

x x

x x

x x

x x

x x

x

x x

x x

x

x

x

x

x x

x x

x x

x x

x x

x x

x x

x x

x x

x x

x x

x x

x x

x x

x x

x x

x x

x x

x x

x x

x x

x x

x x

x x

x x

x x

x x

x x

x x

x x

x x

x x

x x

x x

x x

x x

x x

x x

x x

x x

x x

x x

x x

x x

x

x

x

x

x

x

x

x

x

x

x

x

x

x x

x x

x x

x x

x x

x

x

x

x

x

x

x

x

x

x

x

x

x

x

x

x

x

x

x x

x x

x x

x x

x x

x x

x x

x x

x x

Standard

International Standard A standard adopted by an international standardisation bodyEuropean Standard A standard adopted by a European standardisation organisation

Harmonised Standard

National Standard A standard adopted by a national standardisation body

Draft Standard

Technical Specification

ICT Technical Specification

Use Case List

Cloud1

Cloud10

Cloud11

Cloud2

Cloud3

Cloud4

Cloud5

Cloud6

Technical specification, adopted by a recognised standardisation body, for repeated or continuous application, with which compliance is not compulsory

An European standard adopted on the basis of a request made by the Commission for the application of Union harmonisation legislation

European standardisation deliverable

Any other technical specification than a European standard, adopted by a European standardisation organisation for repeated or continuous application and with which compliance is not compulsory;

A document containing the text of the technical specifications concerning a given subject, which is being considered for adoption in accordance with the relevant standards procedure, as that document stands after the preparatory work and as circulated for public comment or scrutiny

A document that prescribes technical requirements to be fulfilled by a product, process, service or system

A technical specification in the field of information and communication technologies

Portability: the Cloud Service Customer needs to (be able to) retrieve all data that is handled by their Cloud Service Provider at the end of their service contract

Service Level Agreement: the Cloud Service Customer needs to (be able to) monitor the delivery of services by their Cloud Service Provider to ensure they are delivering these services at the agreed levels.

Service Level Agreement: the Cloud Service Customer needs to (be able to) ensure they can retrieve all data that is handled by their Cloud Service Provider when the service is terminated, regardless of why this service is terminated

Portability: the Cloud Service Customer needs to (be able to) move its data residing with one Cloud Service Provider to another Cloud Service Provider

Portability: the Cloud Service Customer needs an application they develop on one Cloud Service Provider’s PaaS services to be easily portable to the cloud platforms of other Cloud Service Providers.

Interoperability: seamlessly switching your service between 2 or more Cloud Service Providers when one is experiencing outage/availability issues (i.e. low band width or availability problems).

Privacy and Security: a Cloud Service Customer employing a bring-your-own-device policy needs to (be able to) ensure secure access to systems in the Cloud via these multiple devices

Privacy and Security: the Cloud Service Customer needs to (be able to) ensure security is retained when mixing services provisioned by their own IT department and services provided by Cloud vendors.

Cloud7

Cloud8

Cloud9

eGov1 eProcurement: Integrating ESDP Data ModeleGov2 eProcurement: eESPD Service Open source

eGov3

eGov4

Energy1 Building Energy Management System UseEnergy2 Smart Grids and Smart MetersTransp1 Levy tolls with On-Board Unit based on DSRCTransp2 Levy tolls with On-Board Unit based on GNSSTransp3 Levy tolls based on ANPR

Privacy and Security: the Cloud Service Customer needs to know the Cloud Service Provider is providing sufficient security for protecting personal sensitive information stored and processed by the Provider’s service, and complying to the General Data Protection Regulation

Service Level Agreement: the Cloud Service Customer needs to procure Software As A Service (SaaS) for use by its employees to replace software currently installed on computers

Service Level Agreement: the Cloud Service Customer needs to (be able to) create a hybrid innovation platform whereby they share specific resources with their Cloud Service Provider.

EESSI – Electronic Exchange of social Security Information: retrieve data and information from the network

EESSI – Electronic Exchange of social Security Information: send on the network data and information

Documents

joinup.ec.europa.eu · XLS file · Web viewSpecifies the Management Information Base ... which includes traditional manual systems, and ... given in EG 202 387 [3]