Information service
33 Telecommunications. Audio and video engineering
New standards
EVS-EN IEC 60728-114:2026
Cable networks for television signals, sound signals and interactive services - Part 114: Optical transmission systems using RFoG technology
Scope:
This part of IEC 60728 describes the system and equipment specification of FTTH/FTTB (fibre to the home/fibre to the building) networks where information is transmitted in both forward and return path directions using RF subcarrier multiplexing technology, and where the return path transmission uses additionally time division multiple access technique imposed by the transmission of the return path signals using a TDMA (e.g. TDMA mode of DOCSIS) protocol.
Such systems are called RF over glass (RFoG) and consist of an RFoG optical network unit (R-ONU), an optical distribution network based on xPON structure, and an RFoG optical return path receiver. This document specifies the basic system parameters and methods of measurement for RFoG systems in order to assess the system performance and its performance limits.
The detailed description of physical layer is out of the scope of this document and it does not include IP transport technologies.
Such systems are called RF over glass (RFoG) and consist of an RFoG optical network unit (R-ONU), an optical distribution network based on xPON structure, and an RFoG optical return path receiver. This document specifies the basic system parameters and methods of measurement for RFoG systems in order to assess the system performance and its performance limits.
The detailed description of physical layer is out of the scope of this document and it does not include IP transport technologies.
Base documents:
IEC 60728-114:2026; EN IEC 60728-114:2026
EVS-EN IEC 62351-8:2026
Power systems management and associated information exchange - Data and communications security - Part 8: Role-based access control for power system management
Scope:
1.1 General
The scope of this part of IEC 62351 is to facilitate role-based access control (RBAC) for power system management. RBAC assigns human users, automated systems, and software applications (collectively called "subjects" in this document) to specified "roles", and restricts their access to only those resources, which the security policies identify as necessary for their roles.
As electric power systems become more automated and cyber security concerns become more prominent, it is becoming increasingly critical to ensure that access to data (read, write, control, etc.) is restricted. As in many aspects of security, RBAC is not just a technology; it is a way of running a business. RBAC is not a new concept; in fact, it is used by many operating systems to control access to system resources. Specifically, RBAC provides an alternative to the all-or nothing super-user model in which all subjects have access to all data, including control commands.
RBAC is a primary method to meet the security principle of least privilege, which states that no subject should be authorized more permissions than necessary for performing that subject’s task. With RBAC, authorization is separated from authentication. RBAC enables an organization to subdivide super-user capabilities and package them into special user accounts' termed roles for assignment to specific individuals according to their associated duties. This subdivision enables security policies to determine who or what systems are permitted access to which data in other systems. RBAC thus provides a means of reallocating system controls as defined by the organization policy. In particular, RBAC can protect sensitive system operations from inadvertent (or deliberate) actions by unauthorized users. Clearly RBAC is not confined to human users though; it applies equally well to automated systems and software applications, i.e., software parts operating independent of user interactions.
The following interactions are in scope:
– local (direct wired) access to the object by a human user, a local and automated computer agent, or a built-in human machine interface (HMI) or panel;
– remote (via dial-up or wireless media) access to the object by a human user;
– remote (via dial-up or wireless media) access to the object by a remote automated computer agent, e.g., another object at another substation, a distributed energy resource at an end user’s facility, or a control centre application.
While this document defines a set of mandatory roles to be supported, the exchange format for defined specific or custom roles is also in scope of this document. This is achieved by defining two different encoding approaches to handle the definition of custom roles, either based on specific permissions or based on constraints to existing permissions. The definition on handling custom based roles was started in IEC 62351-90-1 and taken over into the IEC 62351-8:2020.
Moreover, additionally to the definition of custom roles based on associated permissions, this document also includes options how to assign permissions to objects in a general way.
Referencing documents will provide a mapping to a concrete data model to ensure an interoperability for standard roles used in different data models as well as for custom defined roles. Referencing documents might be standards such as IEC PAS 61850-90-19 or IEC 60870-5-7:2025 or also definitions by an operator.
Out of scope for this document are all topics which are not directly related to the definition of roles and access tokens for local and remote access, especially administrative or organizational tasks, such as:
– definition of usernames and password definitions/policies;
– management of keys and/or key exchange;
– engineering process of roles;
– assignment of roles;
– selection of trusted certification authorities issuing credentials (access tokens);
– defining the tasks of a security officer;
– integrating local policies in RBAC.
NOTE Specifically, the management of certificates is addressed in IEC 62351-9.
Existing standards (see ANSI INCITS 359-2004, IEC 62443 (all parts), and IEEE 802.1X-2020) in process control industry and access control (RFC 2904 and RFC 2905) are not sufficient for addressing specifics of power system automation as none of them specify either the exact role name and associated permissions or the format of the access tokens nor the detailed mechanism by which access tokens are transferred to and authenticated by the target system.
This is addressed in this document by defining the access token format, distribution and verification based on existing technology
Throughout the document security events are defined. These security events are intended to support the error handling and thus to increase system resilience. Implementations need to provide a mechanism for announcing security events.
The information about security events and potential detailed information can only be provided by the entity based on the availability of this information through the underlying platform or utilized components.
It is strongly recommended that the security events defined throughout the document are made available to the operational infrastructure by cyber security events as specified in IEC 62351-14 and/or by monitoring objects as specified in IEC 62351-7. Annex A provides a mapping of the defined events in this document to the notion of IEC 62351-14.
Notices, warnings, errors, and alarms are used to indicate the severity of an event from a security point of view. The following notion from IEC 62351-14 is used:
– A notice refers to a cyber security related activity during the routine use or maintenance of an entity. It does not relate to a cyber security breach or attack or deviation from the normal operating condition of an entity.
– A warning is a deviation from the normal operating condition of an entity but not necessary a cyber-attack.
– An error describes an unforeseen condition, which can indicate unauthorized activity. It might not require immediate action.
– An alarm is an indication of a serious problem, which might indicate unauthorized activity. Action is expected to be taken immediately.
In any case, it is expected that an organization’s security policy determines the final handling of events based on the operational environment. For instance, the assessment of one of more alarms could rise to the level of an incident.
1.2 Published versions of the standard and related namespace names
Table 1 provides a reference between all published editions, amendments or corrigenda of this document and the full name of the namespace.
Table 1 – Published versions and related namespace names [...]
1.3 Identification of the code component
The code components associated with this document are XACML examples in XML files for the definition of custom based roles as well as example LDAP schema as LDIF files as well as the definitions for RBAC access tokens for profile A and B as ASN file and Profile C as JSON file.
The parameters which identify the code components are provided in Table 2: Table 2 – Attributes of the IEC 62351-8 code component [...]
Note that the code components do not provide an own namespace and rather rely on the XACML namespaces defined in the associated W3C specification.
1.4 Code Component distribution
Each Code Component is a ZIP package containing the electronic representation of the Code Component itself, with a file describing the content of the package (IECManifest.xml).
The life cycle of a code component is not restricted to the life cycle of the related publication. The publication life cycle goes through two stages, Version (corresponding to an edition) and Revision (corresponding to an amendment). A third publication stage (Release) allows publication of Code Component in case of urgent fixes of InterOp Tissues, thus without need to publish an amendment.
Consequently, new releases of the Code Component may be released, which supersedes the previous release, and will be distributed through the IEC TC 57 web site at:
https://www.iec.ch/tc57/supportdocuments
The latest version/release of the code component will be found by selecting the file for the code component with the highest value for VersionStateInfo, e.g. IEC_62351-8.ASN1-JSON-XACML-LDIF-Examples.{VersionStateInfo}.full.zip.
The code components associated with this IS are XACML example files for the definition of custom based roles. It is available as a full version only. It is freely accessible on the IEC website for download at https://www.iec.ch/tc57/supportdocuments, but the usage remains under the licensing conditions.
In case of any differences between the downloadable code component and the IEC pdf published content, the downloadable code component is the valid one; it might be subject to updates. See included history files.
The scope of this part of IEC 62351 is to facilitate role-based access control (RBAC) for power system management. RBAC assigns human users, automated systems, and software applications (collectively called "subjects" in this document) to specified "roles", and restricts their access to only those resources, which the security policies identify as necessary for their roles.
As electric power systems become more automated and cyber security concerns become more prominent, it is becoming increasingly critical to ensure that access to data (read, write, control, etc.) is restricted. As in many aspects of security, RBAC is not just a technology; it is a way of running a business. RBAC is not a new concept; in fact, it is used by many operating systems to control access to system resources. Specifically, RBAC provides an alternative to the all-or nothing super-user model in which all subjects have access to all data, including control commands.
RBAC is a primary method to meet the security principle of least privilege, which states that no subject should be authorized more permissions than necessary for performing that subject’s task. With RBAC, authorization is separated from authentication. RBAC enables an organization to subdivide super-user capabilities and package them into special user accounts' termed roles for assignment to specific individuals according to their associated duties. This subdivision enables security policies to determine who or what systems are permitted access to which data in other systems. RBAC thus provides a means of reallocating system controls as defined by the organization policy. In particular, RBAC can protect sensitive system operations from inadvertent (or deliberate) actions by unauthorized users. Clearly RBAC is not confined to human users though; it applies equally well to automated systems and software applications, i.e., software parts operating independent of user interactions.
The following interactions are in scope:
– local (direct wired) access to the object by a human user, a local and automated computer agent, or a built-in human machine interface (HMI) or panel;
– remote (via dial-up or wireless media) access to the object by a human user;
– remote (via dial-up or wireless media) access to the object by a remote automated computer agent, e.g., another object at another substation, a distributed energy resource at an end user’s facility, or a control centre application.
While this document defines a set of mandatory roles to be supported, the exchange format for defined specific or custom roles is also in scope of this document. This is achieved by defining two different encoding approaches to handle the definition of custom roles, either based on specific permissions or based on constraints to existing permissions. The definition on handling custom based roles was started in IEC 62351-90-1 and taken over into the IEC 62351-8:2020.
Moreover, additionally to the definition of custom roles based on associated permissions, this document also includes options how to assign permissions to objects in a general way.
Referencing documents will provide a mapping to a concrete data model to ensure an interoperability for standard roles used in different data models as well as for custom defined roles. Referencing documents might be standards such as IEC PAS 61850-90-19 or IEC 60870-5-7:2025 or also definitions by an operator.
Out of scope for this document are all topics which are not directly related to the definition of roles and access tokens for local and remote access, especially administrative or organizational tasks, such as:
– definition of usernames and password definitions/policies;
– management of keys and/or key exchange;
– engineering process of roles;
– assignment of roles;
– selection of trusted certification authorities issuing credentials (access tokens);
– defining the tasks of a security officer;
– integrating local policies in RBAC.
NOTE Specifically, the management of certificates is addressed in IEC 62351-9.
Existing standards (see ANSI INCITS 359-2004, IEC 62443 (all parts), and IEEE 802.1X-2020) in process control industry and access control (RFC 2904 and RFC 2905) are not sufficient for addressing specifics of power system automation as none of them specify either the exact role name and associated permissions or the format of the access tokens nor the detailed mechanism by which access tokens are transferred to and authenticated by the target system.
This is addressed in this document by defining the access token format, distribution and verification based on existing technology
Throughout the document security events are defined. These security events are intended to support the error handling and thus to increase system resilience. Implementations need to provide a mechanism for announcing security events.
The information about security events and potential detailed information can only be provided by the entity based on the availability of this information through the underlying platform or utilized components.
It is strongly recommended that the security events defined throughout the document are made available to the operational infrastructure by cyber security events as specified in IEC 62351-14 and/or by monitoring objects as specified in IEC 62351-7. Annex A provides a mapping of the defined events in this document to the notion of IEC 62351-14.
Notices, warnings, errors, and alarms are used to indicate the severity of an event from a security point of view. The following notion from IEC 62351-14 is used:
– A notice refers to a cyber security related activity during the routine use or maintenance of an entity. It does not relate to a cyber security breach or attack or deviation from the normal operating condition of an entity.
– A warning is a deviation from the normal operating condition of an entity but not necessary a cyber-attack.
– An error describes an unforeseen condition, which can indicate unauthorized activity. It might not require immediate action.
– An alarm is an indication of a serious problem, which might indicate unauthorized activity. Action is expected to be taken immediately.
In any case, it is expected that an organization’s security policy determines the final handling of events based on the operational environment. For instance, the assessment of one of more alarms could rise to the level of an incident.
1.2 Published versions of the standard and related namespace names
Table 1 provides a reference between all published editions, amendments or corrigenda of this document and the full name of the namespace.
Table 1 – Published versions and related namespace names [...]
1.3 Identification of the code component
The code components associated with this document are XACML examples in XML files for the definition of custom based roles as well as example LDAP schema as LDIF files as well as the definitions for RBAC access tokens for profile A and B as ASN file and Profile C as JSON file.
The parameters which identify the code components are provided in Table 2: Table 2 – Attributes of the IEC 62351-8 code component [...]
Note that the code components do not provide an own namespace and rather rely on the XACML namespaces defined in the associated W3C specification.
1.4 Code Component distribution
Each Code Component is a ZIP package containing the electronic representation of the Code Component itself, with a file describing the content of the package (IECManifest.xml).
The life cycle of a code component is not restricted to the life cycle of the related publication. The publication life cycle goes through two stages, Version (corresponding to an edition) and Revision (corresponding to an amendment). A third publication stage (Release) allows publication of Code Component in case of urgent fixes of InterOp Tissues, thus without need to publish an amendment.
Consequently, new releases of the Code Component may be released, which supersedes the previous release, and will be distributed through the IEC TC 57 web site at:
https://www.iec.ch/tc57/supportdocuments
The latest version/release of the code component will be found by selecting the file for the code component with the highest value for VersionStateInfo, e.g. IEC_62351-8.ASN1-JSON-XACML-LDIF-Examples.{VersionStateInfo}.full.zip.
The code components associated with this IS are XACML example files for the definition of custom based roles. It is available as a full version only. It is freely accessible on the IEC website for download at https://www.iec.ch/tc57/supportdocuments, but the usage remains under the licensing conditions.
In case of any differences between the downloadable code component and the IEC pdf published content, the downloadable code component is the valid one; it might be subject to updates. See included history files.
Base documents:
IEC 62351-8:2026; EN IEC 62351-8:2026
Replaces:
EVS-EN IEC 62351-8:2020
EVS-EN IEC 63478-3:2026
User’s quality of experience on multimedia conferencing services - Part 3: Measurement methods
Scope:
This part of IEC 63478 describes the measurement methods for users’ quality of experience (QoE) parameters on multimedia conferencing services.
Base documents:
IEC 63478-3:2026; EN IEC 63478-3:2026
EVS-EN 300 019-2-3 V3.1.1:2026
Environmental Engineering (EE);
Environmental conditions and environmental tests for telecommunications equipment;
Part 2: Specification of environmental tests;
Sub-part 3: Stationary use at weatherprotected locations
Scope:
The present document specifies test severities and methods for the verification of the required resistibility of equipment according to the relevant environmental class.
The tests in the present document apply to stationary use of equipment at weatherprotected locations covering the environmental conditions stated in ETSI EN 300 019-1-3.
The tests in the present document apply to stationary use of equipment at weatherprotected locations covering the environmental conditions stated in ETSI EN 300 019-1-3.
Base documents:
ETSI EN 300 019-2-3 V3.1.1
IEC TR 60870-1-3:1997/AMD1:2026
Amendment 1 - Telecontrol equipment and systems - Part 1-3: General considerations - Glossary
Scope:
Amendment to IEC TR 60870-1-3:1997
Base documents:
IEC TR 60870-1-3:1997+AMD1:2026 CSV
Telecontrol equipment and systems - Part 1-3: General considerations - Glossary
Scope:
IEC TR 60870-1-3:1997+AMD1:2026 CSV covers terms which are specifically relevant to telecontrol techniques as well as other terms which are necessary for the understanding of telecontrol standards. Is a technical report of type 3.
Base documents:
IEC PAS 61850-90-28:2026
Communication networks and systems for power utility automation - Part 90-28: Specification for subscriber IED to validate received GOOSE and SV messages
Scope:
IEC PAS 61850-90-28:2026, which is a Publicly Available Specification, specifies the expected behavior and associated documentation related to the validation of received GOOSE and SV messages. It considers engineering rules and guidance to ensure that the communication configuration process is well designed for this validation. Conformance statements related to this validation are also considered.
This document considers subscribers claiming conformance to latest editions of the IEC 61850 series in combination with publishers claiming conformance to any previous version and revision of the IEC 61850 series.
This document considers subscribers claiming conformance to latest editions of the IEC 61850 series in combination with publishers claiming conformance to any previous version and revision of the IEC 61850 series.
Base documents:
IEC/IEEE 62704-1:2026
Determining the peak spatial-average specific absorption rate (SAR) in the human body from wireless communications devices, 100 kHz to 10 GHz - Part 1: General requirements for using the finite-difference time-domain (FDTD) method for SAR calculations
Scope:
IEC/IEEE 62704-1:2026 defines the methodology for the application of the finite-difference time domain (FDTD) technique when used for determining the peak spatial-average specific absorption rate (psSAR) in the human body exposed to wireless communication devices with known uncertainty. It defines methods to validate the computational model of the device under test (DUT) and to assess its uncertainty when used in SAR simulations. Moreover, it defines procedures to determine the psSAR in a cubical volume and to verify the correct implementation of the FDTD simulation software. The applicable frequency range is 100 kHz to 10 GHz.
This document does not recommend specific SAR limits; these are found elsewhere, for example, in the guidelines published by the International Commission on Non-Ionizing Radiation Protection (ICNIRP) or in IEEE Std C95.1.
This second edition cancels and replaces the first edition published in 2017. This edition constitutes a technical revision.
This edition includes the following significant technical changes with respect to the previous edition:
a) specification of a SAR averaging algorithm for the calculation of the psSAR from computational results for arbitrarily shaped homogeneous phantoms, which avoids inconsistencies with respect to the algorithm for SAR averaging algorithm specified in IEC/IEEE 62209-1528 for SAR measurement methods;
b) provision of SHA-256 checksums for all supplemental files;
c) addition of brief informative discussion on developmental stages of IEC and IEEE computational modelling standards for SAR evaluations.
This document does not recommend specific SAR limits; these are found elsewhere, for example, in the guidelines published by the International Commission on Non-Ionizing Radiation Protection (ICNIRP) or in IEEE Std C95.1.
This second edition cancels and replaces the first edition published in 2017. This edition constitutes a technical revision.
This edition includes the following significant technical changes with respect to the previous edition:
a) specification of a SAR averaging algorithm for the calculation of the psSAR from computational results for arbitrarily shaped homogeneous phantoms, which avoids inconsistencies with respect to the algorithm for SAR averaging algorithm specified in IEC/IEEE 62209-1528 for SAR measurement methods;
b) provision of SHA-256 checksums for all supplemental files;
c) addition of brief informative discussion on developmental stages of IEC and IEEE computational modelling standards for SAR evaluations.
Base documents:
Replaces:
IEC/IEEE 62704-1:2017
IEC 60794-3-11:2026 CMV
Optical fibre cables - Part 3-11: Outdoor cables - Detailed specification for duct, directly buried, and lashed aerial optical fibre telecommunication cables
Scope:
IEC 60794-3-11:2026 CMV contains both the official standard and its commented version. The commented version provides you with a quick and easy way to compare all the changes between IEC 60794-3-11:2026 edition 3.0 and the previous IEC 60794-3-11:2010 edition 2.0. Furthermore, comments from IEC SC 86A experts are provided to explain the reasons of the most relevant changes, or to clarify any part of the content.
IEC 60794-3-11:2026 sets forth detailed requirements and characteristics specific to this type of optical fibre cables for duct, direct buried, and lashed installation. This document includes functional, mechanical, environmental and optical requirements, recommended features and test methods for assessing the product against the stated requirements. The specified test methods, where applicable, are those referenced in IEC 60794-1-1 and IEC 60794-1-2. The requirements of this document supplement those of the sectional specification IEC 60794‑3 and the family specification IEC 60794-3-10. This edition includes the following significant technical changes with respect to the previous edition:
a) subclause 5.2.2 has been enlarged to include fibre type B-657.B2;
b) this document has been updated to include multimode optical fibres.
IEC 60794-3-11:2026 sets forth detailed requirements and characteristics specific to this type of optical fibre cables for duct, direct buried, and lashed installation. This document includes functional, mechanical, environmental and optical requirements, recommended features and test methods for assessing the product against the stated requirements. The specified test methods, where applicable, are those referenced in IEC 60794-1-1 and IEC 60794-1-2. The requirements of this document supplement those of the sectional specification IEC 60794‑3 and the family specification IEC 60794-3-10. This edition includes the following significant technical changes with respect to the previous edition:
a) subclause 5.2.2 has been enlarged to include fibre type B-657.B2;
b) this document has been updated to include multimode optical fibres.
Base documents:
IEC 61290-3-2:2026
Optical amplifiers - Test methods - Part 3-2: Noise figure parameters - Electrical spectrum analyzer method
Scope:
IEC 61290-3-2:2026 applies to all commercially available optical amplifiers (OAs), including OAs using optically pumped fibres (i.e. optical fibre amplifiers (OFAs) based on either rare-earth doped fibres or on the Raman effect), semiconductor optical amplifiers (SOAs), and planar waveguide optical amplifiers (PWOAs).
This document defines requirements for accurate and reliable measurements of the noise figure parameters of OAs by means of the electrical spectrum analyser (ESA) method. The noise figure parameters of OAs are defined in IEC 61291-1.
This edition includes the following significant technical changes with respect to the previous edition:
a) shortening and clarification of the scope in Clause 1;
b) update of the normative references in Clause 2;
c) deletion of duplicate instructions in 7.2 to measure the time-average input power;
d) deletion of unused symbols in 3.3 and addition of new symbol.
This document defines requirements for accurate and reliable measurements of the noise figure parameters of OAs by means of the electrical spectrum analyser (ESA) method. The noise figure parameters of OAs are defined in IEC 61291-1.
This edition includes the following significant technical changes with respect to the previous edition:
a) shortening and clarification of the scope in Clause 1;
b) update of the normative references in Clause 2;
c) deletion of duplicate instructions in 7.2 to measure the time-average input power;
d) deletion of unused symbols in 3.3 and addition of new symbol.
Base documents:
Replaces:
IEC 61290-3-2:2008
IEC 61754-6:2022/AMD1:2026
Amendment 1 - Fibre optic interconnecting devices and passive components - Fibre optic connector interfaces - Part 6: Type MU connector family
Scope:
Amendment to IEC 61754-6:2022
Base documents:
EVS-EN IEC 60794-1-208:2025/AC:2026
Optical fibre cables - Part 1-208: Generic specification - Basic optical cable test procedures - Environmental test methods - Pneumatic resistance, Method F8
Scope:
Corrigendum to EN IEC 60794-1-208:2025
Base documents:
IEC 60794-1-208:2025/COR1:2025; EN IEC 60794-1-208:2025/AC:2026-10
IEC 61754-6:2022+AMD1:2026 CSV
Fibre optic interconnecting devices and passive components - Fibre optic connector interfaces - Part 6: Type MU connector family
Scope:
IEC 61754-6:2022+AMD1:2026 CSV specifies the standard interface dimensions for type MU family of connectors. This third edition cancels and replaces the second edition published in 2013 and constitutes a technical revision.
This edition includes the following significant technical changes with respect to the previous edition:
- the test method IEC 61300-3-22 for the compression force of the ferrule was added;
- Annex D (informative) with cut out dimension requirements for testing the strength of mounted adaptors was added.
This edition includes the following significant technical changes with respect to the previous edition:
- the test method IEC 61300-3-22 for the compression force of the ferrule was added;
- Annex D (informative) with cut out dimension requirements for testing the strength of mounted adaptors was added.
Base documents:
IEC 60794-3-11:2026
Optical fibre cables - Part 3-11: Outdoor cables – Detailed specification for duct, directly buried, and lashed aerial optical fibre telecommunication cables
Scope:
IEC 60794-3-11:2026 sets forth detailed requirements and characteristics specific to this type of optical fibre cables for duct, direct buried, and lashed installation. This document includes functional, mechanical, environmental and optical requirements, recommended features and test methods for assessing the product against the stated requirements. The specified test methods, where applicable, are those referenced in IEC 60794-1-1 and IEC 60794-1-2. The requirements of this document supplement those of the sectional specification IEC 60794‑3 and the family specification IEC 60794-3-10.
This edition includes the following significant technical changes with respect to the previous edition:
a) subclause 5.2.2 has been enlarged to include fibre type B-657.B2;
b) this document has been updated to include multimode optical fibres.
This edition includes the following significant technical changes with respect to the previous edition:
a) subclause 5.2.2 has been enlarged to include fibre type B-657.B2;
b) this document has been updated to include multimode optical fibres.
Base documents:
Replaces:
IEC 60794-3-11:2010
Replaced standards
IEC/IEEE 62704-1:2017
Determining the peak spatial-average specific absorption rate (SAR) in the human body from wireless communications devices, 30 MHz to 6 GHz - Part 1: General requirements for using the finite difference time-domain (FDTD) method for SAR calculations<br />
Scope:
IEC/IEEE 62704-1:2017(E) defines the methodology for the application of the finite-difference time domain (FDTD) technique when used for determining the peak spatial-average specific absorption rate (SAR) in the human body exposed to wireless communication devices with known uncertainty. It defines methods to validate the numerical model of the device under test (DUT) and to assess its uncertainty when used in SAR simulations. Moreover, it defines procedures to determine the peak spatial-average SAR in a cubical volume and to validate the correct implementation of the FDTD simulation software. The applicable frequency range is 30 MHz to 6 GHz.
This document does not recommend specific SAR limits since these are found elsewhere, for example, in the guidelines published by the International Commission on Non-Ionizing Radiation Protection (ICNIRP) [1] or in IEEE Std C95.1 [3].
This document does not recommend specific SAR limits since these are found elsewhere, for example, in the guidelines published by the International Commission on Non-Ionizing Radiation Protection (ICNIRP) [1] or in IEEE Std C95.1 [3].
Base documents:
Replaced:
IEC/IEEE 62704-1:2026
IEC 61290-3-2:2008
Optical amplifiers - Test methods - Part 3-2: Noise figure parameters - Electrical spectrum analyzer method
Scope:
IEC 61290-3-2:2008 applies to optical fibre amplifiers (OFA) using active fibres, containing rare-earth dopants, presently commercially available. Establishes uniform requirements for accurate and reliable measurements, of the noise figure, as defined in 3.1.17 of IEC 61291-1, by means of the electricial spectrum analyzer (ESA) method. This technical revision includes updates to specifically address all types of optical amplifiers - not just optical fibre amplifiers. This standard should be read in conjunction with IEC 61290-3 and IEC 61291-1.
Base documents:
Replaced:
IEC 61290-3-2:2026
IEC 60794-3-11:2010
Optical fibre cables - Part 3-11: Outdoor cables - Product specification for duct, directly buried, and lashed aerial single-mode optical fibre telecommunication cables
Scope:
IEC 60794-3-11:2010 sets forth technical requirements and characteristics of single-mode optical fibre cables for duct and direct buried installation. This specification includes functional mechanical, environmental and optical requirements, recommended features and test methods for assessing the product against the stated requirements. The requirements of this specification supplement those of IEC 60794-3 and IEC 60794-3-10. The main changes with respect to the previous edition are as follows:
- the title of the specification has been updated to include lashed applications;
- the fibres specification clause (subclause 5.2.2) has been enlarged to include fibres types B6_a.
- the title of the specification has been updated to include lashed applications;
- the fibres specification clause (subclause 5.2.2) has been enlarged to include fibres types B6_a.
Base documents:
Replaced:
IEC 60794-3-11:2026
EVS-EN IEC 62351-8:2020
Power systems management and associated information exchange - Data and communications security - Part 8: Role-based access control for power system management
Scope:
IEC 62351-8: 2020 is to facilitate role-based access control (RBAC) for power system management. RBAC assigns human users, automated systems, and software applications (collectively called "subjects" in this document) to specified "roles", and restricts their access to only those resources, which the security policies identify as necessary for their roles.
As electric power systems become more automated and cyber security concerns become more prominent, it is becoming increasingly critical to ensure that access to data (read, write, control, etc.) is restricted. As in many aspects of security, RBAC is not just a technology; it is a way of running a business. RBAC is not a new concept; in fact, it is used by many operating systems to control access to system resources. Specifically, RBAC provides an alternative to the all-or-nothing super-user model in which all subjects have access to all data, including control commands.
RBAC is a primary method to meet the security principle of least privilege, which states that no subject should be authorized more permissions than necessary for performing that subject’s task. With RBAC, authorization is separated from authentication. RBAC enables an organization to subdivide super-user capabilities and package them into special user accounts termed roles for assignment to specific individuals according to their associated duties. This subdivision enables security policies to determine who or what systems are permitted access to which data in other systems. RBAC provides thus a means of reallocating system controls as defined by the organization policy. In particular, RBAC can protect sensitive system operations from inadvertent (or deliberate) actions by unauthorized users. Clearly RBAC is not confined to human users though; it applies equally well to automated systems and software applications, i.e., software parts operating independent of user interactions.
The following interactions are in scope:
– local (direct wired) access to the object by a human user; by a local and automated computer agent, or built-in HMI or panel;
– remote (via dial-up or wireless media) access to the object by a human user;
– remote (via dial-up or wireless media) access to the object by a remote automated computer agent, e.g. another object at another substation, a distributed energy resource at an end-user’s facility, or a control centre application.
While this document defines a set of mandatory roles to be supported, the exchange format for defined specific or custom roles is also in scope of this document.
Out of scope for this document are all topics which are not directly related to the definition of roles and access tokens for local and remote access, especially administrative or organizational tasks
As electric power systems become more automated and cyber security concerns become more prominent, it is becoming increasingly critical to ensure that access to data (read, write, control, etc.) is restricted. As in many aspects of security, RBAC is not just a technology; it is a way of running a business. RBAC is not a new concept; in fact, it is used by many operating systems to control access to system resources. Specifically, RBAC provides an alternative to the all-or-nothing super-user model in which all subjects have access to all data, including control commands.
RBAC is a primary method to meet the security principle of least privilege, which states that no subject should be authorized more permissions than necessary for performing that subject’s task. With RBAC, authorization is separated from authentication. RBAC enables an organization to subdivide super-user capabilities and package them into special user accounts termed roles for assignment to specific individuals according to their associated duties. This subdivision enables security policies to determine who or what systems are permitted access to which data in other systems. RBAC provides thus a means of reallocating system controls as defined by the organization policy. In particular, RBAC can protect sensitive system operations from inadvertent (or deliberate) actions by unauthorized users. Clearly RBAC is not confined to human users though; it applies equally well to automated systems and software applications, i.e., software parts operating independent of user interactions.
The following interactions are in scope:
– local (direct wired) access to the object by a human user; by a local and automated computer agent, or built-in HMI or panel;
– remote (via dial-up or wireless media) access to the object by a human user;
– remote (via dial-up or wireless media) access to the object by a remote automated computer agent, e.g. another object at another substation, a distributed energy resource at an end-user’s facility, or a control centre application.
While this document defines a set of mandatory roles to be supported, the exchange format for defined specific or custom roles is also in scope of this document.
Out of scope for this document are all topics which are not directly related to the definition of roles and access tokens for local and remote access, especially administrative or organizational tasks
Base documents:
IEC 62351-8:2020; EN IEC 62351-8:2020
Replaced:
EVS-EN IEC 62351-8:2026
Drafts
prEN IEC 63315:2026
Audio/video, information and communication technology equipment - Safety - DC power transfer between ICT equipment ports using ICT wiring and cables at voltages not exceeding 60 V DC
Scope:
This document applies to any equipment intended to supply or receive charging or operating power from external Information and Communication Technology (ICT) interfaces using ICT wiring or cables. It covers requirements for circuits that are designed to transfer DC power through an ICT interface from a power sourcing equipment to a powered device for equipment that uses interfaces at voltage not exceeding 60 V DC and:
– PDs at power exceeding 15 W;
– PSEs outputs at power exceeding 100 W under any of the following conditions: normal operating conditions, abnormal operating conditions or single fault conditions.
NOTE 1 A PSE or PD which utilize an industry standard connector with a non-industry standard ICT power delivery specification (e.g. protocol) is considered still in scope of this document as determined above.
PSEs are out of scope of this document when the output power is limited to 100 W under all of the following conditions: normal operating conditions, abnormal operating conditions and single fault conditions.
Examples of equipment interfaces that are considered to be within the scope of this document:
– PoE;
– USB Type-C®1 with USB Power Delivery (USB PD)
NOTE 2 Any wiring or cable that permits DC power transfer between ICT equipment is considered a communication cable or ICT cable even if communication does not take place on the conductors. For example, a USB cable can be used just to recharge a portable device with a battery.
Non-static power source and static power source are covered in this document.
Unless otherwise stated, this document does not cover:
– power sources with output connectors not associated with a local ICT interface or remote ICT interface;
– power sources with custom connectors that are not interchangeable with common ICT interface connectors;
– non-static power source which can deliver power to multiple PDs through a single port or cable simultaneously;
– power sources with only wireless power transfer;
– power sources which utilize a wireless communication protocol to control the power transfer through a physical cable connection;
– remote feeding telecommunication (RFT) circuits and other specific communication technologies within the scope of IEC 63316[2].
NOTE 3 A custom connector is a connector that is not defined and referenced for use in an industry communication standard.
NOTE 4 Bluetooth®2 is an example of a wireless communication protocol to control the power transfer through a physical cable connection.
Refer to Annex A for examples of common interfaces which are in or out of scope of this document.
This group safety publication is primarily intended to be used as a product safety standard for the products mentioned in the scope, but shall also be used by technical committees in the preparation of standards for products similar to those mentioned in the scope of this standard, in accordance with the principles laid down in IEC Guide 104 and ISO/IEC Guide 51. One of the responsibilities of a technical committee is, wherever applicable, to make use of basic safety publications and/or group safety publications in the preparation of its publications.
________________________________
1 USB Type-C® and USB-C® are registered trademarks of the Universal Serial Bus Implementers Forum (USB-IF). This information is given for the convenience of users of this document and does not constitute an endorsement by IEC of the product named.
2 Bluetooth is the trademark of a product supplied by Bluetooth SIG, Inc. This information is given for the convenience of users of this document and does not constitute an endorsement by IEC of the product named. Equivalent products can be used if they can be shown to lead to the same results.
– PDs at power exceeding 15 W;
– PSEs outputs at power exceeding 100 W under any of the following conditions: normal operating conditions, abnormal operating conditions or single fault conditions.
NOTE 1 A PSE or PD which utilize an industry standard connector with a non-industry standard ICT power delivery specification (e.g. protocol) is considered still in scope of this document as determined above.
PSEs are out of scope of this document when the output power is limited to 100 W under all of the following conditions: normal operating conditions, abnormal operating conditions and single fault conditions.
Examples of equipment interfaces that are considered to be within the scope of this document:
– PoE;
– USB Type-C®1 with USB Power Delivery (USB PD)
NOTE 2 Any wiring or cable that permits DC power transfer between ICT equipment is considered a communication cable or ICT cable even if communication does not take place on the conductors. For example, a USB cable can be used just to recharge a portable device with a battery.
Non-static power source and static power source are covered in this document.
Unless otherwise stated, this document does not cover:
– power sources with output connectors not associated with a local ICT interface or remote ICT interface;
– power sources with custom connectors that are not interchangeable with common ICT interface connectors;
– non-static power source which can deliver power to multiple PDs through a single port or cable simultaneously;
– power sources with only wireless power transfer;
– power sources which utilize a wireless communication protocol to control the power transfer through a physical cable connection;
– remote feeding telecommunication (RFT) circuits and other specific communication technologies within the scope of IEC 63316[2].
NOTE 3 A custom connector is a connector that is not defined and referenced for use in an industry communication standard.
NOTE 4 Bluetooth®2 is an example of a wireless communication protocol to control the power transfer through a physical cable connection.
Refer to Annex A for examples of common interfaces which are in or out of scope of this document.
This group safety publication is primarily intended to be used as a product safety standard for the products mentioned in the scope, but shall also be used by technical committees in the preparation of standards for products similar to those mentioned in the scope of this standard, in accordance with the principles laid down in IEC Guide 104 and ISO/IEC Guide 51. One of the responsibilities of a technical committee is, wherever applicable, to make use of basic safety publications and/or group safety publications in the preparation of its publications.
________________________________
1 USB Type-C® and USB-C® are registered trademarks of the Universal Serial Bus Implementers Forum (USB-IF). This information is given for the convenience of users of this document and does not constitute an endorsement by IEC of the product named.
2 Bluetooth is the trademark of a product supplied by Bluetooth SIG, Inc. This information is given for the convenience of users of this document and does not constitute an endorsement by IEC of the product named. Equivalent products can be used if they can be shown to lead to the same results.
Base documents:
108/870/CDV; prEN IEC 63315:2026
prEN IEC 62361-102:2026
Power systems management and associated information exchange - Interoperability in the long term - Part 102: CIM - IEC 61850 harmonization
Scope:
1.1 General
This part of IEC 62361 outlines a technical approach for achieving effective information exchange between power system installations governed by IEC 61850 and business systems integrated with IEC CIM standard data exchanges, based on a selected specific set of use cases, but also with the goal of creating a framework that will extend successfully to other use cases in the future. This document includes proposals to ‘harmonize’ the two standards by adapting or extending existing information models and/or defining new models, where such changes will enable more effective communication. Both current and future directions of models will be considered. The document aims to take into account existing standards for semantics, services, protocols, system configuration language, and architecture.
This document is intended to be coordinated with IEC 61850 and all affiliated subgroups as well as IEC 61968 and IEC 61970. The first edition of the document was prepared based on Edition 2 of IEC 61850-6 (2009), IEC 61850-7-3 and IEC 61850-7-4:2026. This edition has been updated to match more recent documents including IEC 61850 Edition 2.1. Mapping to other parts of IEC 61850 is incomplete. Mapping has been considered for the CIM classes defined in IEC 61970-301. The mapping to CIM classes defined in IEC 61968-11 and other standards isincomplete.
This document suggests a technical approach by which two of the leading standards for software interoperability that serve the electric utility industry (the Common Information Model, CIM, and the IEC 61850 model) can cooperate in order to enable effective data exchanges between the domains covered by these standards. Both of these standards are maintained by the International Electrotechnical Committee (IEC).
A number of studies and reports have already been produced on the subject of harmonization as listed in the Bibliography.
The work leading to this document has considered how exchanges required by commonly understood use cases might be mapped between the standard models in order to determine the harmonizing changes suggested for the relevant models. The bibliography lists some of the papers, reports or other documents that provided data for this harmonization.
Paragraphs introduced by the word Recommendation are recommendations for revisions to some of the IEC 61850 and IEC 61970 standards. It is anticipated that if these recommendations are accepted, then this document will be revised.
NOTE New recommendations for this edition are numbered R31, R32 etc in order to distinguish them from recommendations in IEC 62361-102:2018.
1.2 Edition 1
For edition 1, the approach adopted was to define a transformation of the data governed by IEC 61850 SCL XSD to data governed by CIM UML. The transformations in this document are defined based on the use cases presented in this document. Only SCL data relevant to these use cases is transformed.
The aim is to allow the development of tools that perform automatic transformation from an SCL instance file into a CIM based instance model that can then be exported using existing standards such as IEC 61970-552: CIMXML Model exchange format.
These transformations will result in CIM-side processes that can distribute the information as needed for configuration of specific CIM applications. It is also presumed that the result of this exchange will be to enable creation of real-time CIM-side clients for IEC 61850 system data.
The heart of the SCL to CIM transformation specification defined in this document is a mapping between the two information models. Wherever this mapping has been judged to be unnecessarily complex, changes have been recommended to the existing information models.
A major objective, however, has been to define a solution that does not change either SCL or CIM UML without a mechanism to supply backward compatibility.
The transformation specification is only for structural modelling. IEC 61970-301 states "CIM entities have no behaviour." IEC 61850-5 states "the behaviour of the functions itself are ... outside the scope of this standard".
1.3 Edition 2
This edition of the document includes additional use cases and extends the logical nodes mapping for several parts from the IEC 61850 series.
This part of IEC 62361 outlines a technical approach for achieving effective information exchange between power system installations governed by IEC 61850 and business systems integrated with IEC CIM standard data exchanges, based on a selected specific set of use cases, but also with the goal of creating a framework that will extend successfully to other use cases in the future. This document includes proposals to ‘harmonize’ the two standards by adapting or extending existing information models and/or defining new models, where such changes will enable more effective communication. Both current and future directions of models will be considered. The document aims to take into account existing standards for semantics, services, protocols, system configuration language, and architecture.
This document is intended to be coordinated with IEC 61850 and all affiliated subgroups as well as IEC 61968 and IEC 61970. The first edition of the document was prepared based on Edition 2 of IEC 61850-6 (2009), IEC 61850-7-3 and IEC 61850-7-4:2026. This edition has been updated to match more recent documents including IEC 61850 Edition 2.1. Mapping to other parts of IEC 61850 is incomplete. Mapping has been considered for the CIM classes defined in IEC 61970-301. The mapping to CIM classes defined in IEC 61968-11 and other standards isincomplete.
This document suggests a technical approach by which two of the leading standards for software interoperability that serve the electric utility industry (the Common Information Model, CIM, and the IEC 61850 model) can cooperate in order to enable effective data exchanges between the domains covered by these standards. Both of these standards are maintained by the International Electrotechnical Committee (IEC).
A number of studies and reports have already been produced on the subject of harmonization as listed in the Bibliography.
The work leading to this document has considered how exchanges required by commonly understood use cases might be mapped between the standard models in order to determine the harmonizing changes suggested for the relevant models. The bibliography lists some of the papers, reports or other documents that provided data for this harmonization.
Paragraphs introduced by the word Recommendation are recommendations for revisions to some of the IEC 61850 and IEC 61970 standards. It is anticipated that if these recommendations are accepted, then this document will be revised.
NOTE New recommendations for this edition are numbered R31, R32 etc in order to distinguish them from recommendations in IEC 62361-102:2018.
1.2 Edition 1
For edition 1, the approach adopted was to define a transformation of the data governed by IEC 61850 SCL XSD to data governed by CIM UML. The transformations in this document are defined based on the use cases presented in this document. Only SCL data relevant to these use cases is transformed.
The aim is to allow the development of tools that perform automatic transformation from an SCL instance file into a CIM based instance model that can then be exported using existing standards such as IEC 61970-552: CIMXML Model exchange format.
These transformations will result in CIM-side processes that can distribute the information as needed for configuration of specific CIM applications. It is also presumed that the result of this exchange will be to enable creation of real-time CIM-side clients for IEC 61850 system data.
The heart of the SCL to CIM transformation specification defined in this document is a mapping between the two information models. Wherever this mapping has been judged to be unnecessarily complex, changes have been recommended to the existing information models.
A major objective, however, has been to define a solution that does not change either SCL or CIM UML without a mechanism to supply backward compatibility.
The transformation specification is only for structural modelling. IEC 61970-301 states "CIM entities have no behaviour." IEC 61850-5 states "the behaviour of the functions itself are ... outside the scope of this standard".
1.3 Edition 2
This edition of the document includes additional use cases and extends the logical nodes mapping for several parts from the IEC 61850 series.
Base documents:
57/2975/CDV; prEN IEC 62361-102:2026
EN 50173-1:2018/prA1:2026
Information technology - Generic cabling systems - Part 1: General requirements
Scope:
Amendment to EN 50173-1:2018
Base documents:
EN 50173-1:2018/prA1:2026
prEN IEC 60794-2-50:2026
Optical fibre cables - Part 2-50: Indoor cables - Family specification for simplex and duplex cables for use in terminated cable assemblies
Scope:
This part of IEC 60794 is a family specification that specifies requirements for indoor simplex and duplex optical fibre cables for use in terminated cable assemblies or as used for termination of passive components.
NOTE The temperature cycling test parameters for the performance categories C and CHD for indoor controlled environment as well as the performance categories OP and OPHD for outdoor protected environment are included in this standard, as the same type of cables are often used for outdoor protected environment as for indoor controlled environment. The performance categories and operating service environments are defined in IEC 61753-1.
NOTE The temperature cycling test parameters for the performance categories C and CHD for indoor controlled environment as well as the performance categories OP and OPHD for outdoor protected environment are included in this standard, as the same type of cables are often used for outdoor protected environment as for indoor controlled environment. The performance categories and operating service environments are defined in IEC 61753-1.
Base documents:
86A/2729/CDV; prEN IEC 60794-2-50:2026
prEN IEC 62149-10:2026
Fibre optic active components and devices - Performance standards - Part 10: Radio-over-fibre (RoF) transceivers for mobile communication applications
Scope:
This part of IEC 62149 defines performance specifications for radio over fibre (RoF) transceivers used in mobile communication applications. The performance standard contains a definition of the product performance requirements together with a series of tests and measurements with clearly defined conditions, severities, and pass/fail criteria. The tests are intended to be run on a "one-off" basis to prove the ability of a product to satisfy the performance requirements.
A product that has been shown to meet all the requirements of this performance standard can be declared to be in compliance with this document.
A product that has been shown to meet all the requirements of this performance standard can be declared to be in compliance with this document.
Base documents:
86C/2037/CDV; prEN IEC 62149-10:2026
prEN IEC 60942:2026
Electroacoustics - Sound calibrators
Scope:
The primary function of a sound calibrator is to generate a sinusoidal sound pressure of specified level and frequency when coupled to specified models of microphone in specified configurations.
This document specifies the performance requirements for three classes of sound calibrator:
class LS (Laboratory Standard), class 1 and class 2. Acceptance limits are smallest for class LS and greatest for class 2 instruments. Class LS sound calibrators are normally used only in the laboratory; class 1 and class 2 sound calibrators are considered as sound calibrators for field use. A class 1 sound calibrator is primarily intended for use with a class 1 sound level meter and a class 2 sound calibrator primarily with a class 2 sound level meter, as specified in IEC 61672-1, and with a personal sound exposure meter, as specified in IEC 61252 [3].
To promote consistency of testing of sound calibrators and ease of use, this document contains normative information on pattern evaluation tests and periodic tests, and informative information on assessments of conformance to specifications of this document.
This document does not include requirements for equivalent free-field or random-incidence sound pressure levels, such as can be used in the overall sensitivity adjustment of a sound level meter.
A sound calibrator can provide other functions, for example, tonebursts. Requirements for these other functions are not included in this document.
This document specifies the performance requirements for three classes of sound calibrator:
class LS (Laboratory Standard), class 1 and class 2. Acceptance limits are smallest for class LS and greatest for class 2 instruments. Class LS sound calibrators are normally used only in the laboratory; class 1 and class 2 sound calibrators are considered as sound calibrators for field use. A class 1 sound calibrator is primarily intended for use with a class 1 sound level meter and a class 2 sound calibrator primarily with a class 2 sound level meter, as specified in IEC 61672-1, and with a personal sound exposure meter, as specified in IEC 61252 [3].
To promote consistency of testing of sound calibrators and ease of use, this document contains normative information on pattern evaluation tests and periodic tests, and informative information on assessments of conformance to specifications of this document.
This document does not include requirements for equivalent free-field or random-incidence sound pressure levels, such as can be used in the overall sensitivity adjustment of a sound level meter.
A sound calibrator can provide other functions, for example, tonebursts. Requirements for these other functions are not included in this document.
Base documents:
29/1244/CDV; prEN IEC 60942:2026
prEN 301 428 V2.1.3
Satellite Earth Stations and Systems (SES);
Very Small Aperture Terminal (VSAT);
Transmit-only, transmit/receive or receive-only satellite earth stations operating in the 11/12/14 GHz frequency bands;
Harmonised Standard for access to radio spectrum
Scope:
The present document specifies technical characteristics and methods of measurements for Very Small Aperture Terminals (VSATs) intended to operate through a geostationary satellite at least 3° away from any other geostationary satellite operating in the same frequency band and covering the same area and which have the following characteristics:
• The VSAT operates in the following bands, or parts thereof, allocated to the Fixed Satellite Service (FSS):
- 10,70 GHz to 11,70 GHz (space-to-Earth);
- 12,50 GHz to 12,75 GHz (space-to-Earth);
- 14,00 GHz to 14,25 GHz (Earth-to-space);
- 14,25 GHz to 14,50 GHz (Earth-to-space);
• The VSAT uses linear polarization.
• The VSAT antenna diameter does not exceed 3,8 m, or equivalent effective area.
• The VSAT is either:
- a transmit only VSAT: designed for transmission only of radio-communications signals in any of the frequency bands (earth-to-space) specified above; or
- a transmit and receive VSAT: designed for transmission and reception of radio-communications signals in any of the frequency bands specified above; or
- a receive only VSAT: designed for reception only of radio-communications signals in any of the frequency bands (space-earth) specified above.
The present document applies to the VSAT with its ancillary equipment and its various terrestrial ports, and when operated within the boundary limits of the operational environmental profile defined for the intended use of the VSAT of the MES.
NOTE: The relationship between the present document and essential requirements of article 3.2 of Directive 2014/53/EU is given in Annex A.
• The VSAT operates in the following bands, or parts thereof, allocated to the Fixed Satellite Service (FSS):
- 10,70 GHz to 11,70 GHz (space-to-Earth);
- 12,50 GHz to 12,75 GHz (space-to-Earth);
- 14,00 GHz to 14,25 GHz (Earth-to-space);
- 14,25 GHz to 14,50 GHz (Earth-to-space);
• The VSAT uses linear polarization.
• The VSAT antenna diameter does not exceed 3,8 m, or equivalent effective area.
• The VSAT is either:
- a transmit only VSAT: designed for transmission only of radio-communications signals in any of the frequency bands (earth-to-space) specified above; or
- a transmit and receive VSAT: designed for transmission and reception of radio-communications signals in any of the frequency bands specified above; or
- a receive only VSAT: designed for reception only of radio-communications signals in any of the frequency bands (space-earth) specified above.
The present document applies to the VSAT with its ancillary equipment and its various terrestrial ports, and when operated within the boundary limits of the operational environmental profile defined for the intended use of the VSAT of the MES.
NOTE: The relationship between the present document and essential requirements of article 3.2 of Directive 2014/53/EU is given in Annex A.
Base documents:
Draft ETSI EN 301 428 V2.1.3
prEN 302 686 V2.1.0
Intelligent Transport Systems (ITS);
Radiocommunications equipment operating in the 63,72 GHz to 65,88 GHz frequency band;
Harmonised Standard for access to radio spectrum
Scope:
The present document applies to cooperative communications using radio transmitters and receivers for Intelligent Transport Systems (ITS). ITS communications may comprise vehicle-to-vehicle, vehicle-to-infrastructure and infrastructure-to-vehicle.
The equipment is comprised of a transmitter and associated encoder and modulator and/or a receiver and associated demodulator and decoder. The types of equipment covered by the present document are as follows:
• OnBoard Equipment (OBE) fitted with an integral or dedicated antenna(s), intended for use in vehicles, e.g. a road or a rail vehicle.
• RoadSide Equipment (RSE) fitted with an antenna socket, integral or dedicated antenna(s), normally used as a fixed station, e.g. a road or rail infrastructure.
These networks operate over a short range with very wideband communications using a variety of directional medium and high gain antennas to enable a high degree of spectrum reuse, and may use a flexible bandwidth scheme under which they normally operate in a wideband mode, and periodically reduce their bandwidth (e.g. for antenna training and other activities).
The technical characteristics of these applications are described in ETSI TR 102 400, where ITS applications in the 63,72 GHz to 65,88 GHz band is described. The present document is also in line with the results of the spectrum compatibility study in the CEPT ECC Report 113.
These radio equipment types are capable of operating in all or any part of the frequency bands given in table 1.
Table 1: Equipment operating frequency bands
Equipment operating frequency bands
Transmit; 63,72 GHz to 65,88 GHz
Receive; 63,72 GHz to 65,88 GHz
NOTE: The relationship between the present document and essential requirements of article 3.2 of Directive 2014/53/EU is given in Annex A.
The equipment is comprised of a transmitter and associated encoder and modulator and/or a receiver and associated demodulator and decoder. The types of equipment covered by the present document are as follows:
• OnBoard Equipment (OBE) fitted with an integral or dedicated antenna(s), intended for use in vehicles, e.g. a road or a rail vehicle.
• RoadSide Equipment (RSE) fitted with an antenna socket, integral or dedicated antenna(s), normally used as a fixed station, e.g. a road or rail infrastructure.
These networks operate over a short range with very wideband communications using a variety of directional medium and high gain antennas to enable a high degree of spectrum reuse, and may use a flexible bandwidth scheme under which they normally operate in a wideband mode, and periodically reduce their bandwidth (e.g. for antenna training and other activities).
The technical characteristics of these applications are described in ETSI TR 102 400, where ITS applications in the 63,72 GHz to 65,88 GHz band is described. The present document is also in line with the results of the spectrum compatibility study in the CEPT ECC Report 113.
These radio equipment types are capable of operating in all or any part of the frequency bands given in table 1.
Table 1: Equipment operating frequency bands
Equipment operating frequency bands
Transmit; 63,72 GHz to 65,88 GHz
Receive; 63,72 GHz to 65,88 GHz
NOTE: The relationship between the present document and essential requirements of article 3.2 of Directive 2014/53/EU is given in Annex A.
Base documents:
Draft ETSI EN 302 686 V2.1.0
prEN 50385:2026
Product standard to demonstrate the compliance of a base station with radiofrequency electromagnetic field exposure limits (110 MHz - 300 GHz), when placed on the market
Scope:
This document is related to human exposure to radiofrequency (RF) electromagnetic fields transmitted by a base station (BS), operating in the frequency range 110 MHz to 300 GHz. It specifies the methods to assess the compliance of exposure from a BS with the general public basic restrictions, directly or indirectly via compliance with reference levels, and the workers’ exposure limit values, directly or indirectly via compliance with action levels, when the BS is placed on the market.
The term “product” is used in the same sense as BS in this document.
The term “product” is used in the same sense as BS in this document.
Base documents:
prEN 50385:2026