35.110 - Networking
ICS 35.110 Details
Networking
Netzwerke
Réseaux
Omreževanje
General Information
e-Library Subscription
Create subscription and get permanent access to documents within 35.110 - Networking
Currently subscription includes documents marked with .We are working on making all documents available within the subscription.
- Standard80 pagesEnglish languagesale 15% off
IEC 61158-4-4:2023 specifies
- procedures for the timely transfer of data and control information from one data-link user entity to a peer user entity, and among the data-link entities forming the distributed data-link service provider;
- the structure of the fieldbus DLPDUs used for the transfer of data and control information by the protocol of this document, and their representation as physical interface data units.
- Standard49 pagesEnglish languagesale 10% offe-Library read for1 day
This standard specifies generic cabling for homes. A home can contain one or more buildings or can be within a building that contains more than one home.
It covers balanced cabling, optical fibre cabling, and coaxial cabling.
This standard specifies generic cabling for two groups of applications:
- Information and Communications Technologies (ICT);
- Broadcast and Communications Technologies (BCT).
This standard specifies directly or via reference to EN 50173 1 the:
- structure and minimum configuration for generic cabling within homes;
- interfaces at the telecommunications outlet (TO) and broadcast outlet (BO);
- performance requirements for cabling links and channels;
- implementation requirements and options;
- performance requirements for cabling components;
- conformance requirements and verification procedures.
This standard has taken into account requirements specified in application standards listed in EN 50173 1.
Safety and electromagnetic compatibility (EMC) requirements are outside the scope of this standard and are covered by other standards and regulations. However, information given in this standard can be of assistance in meeting these standards and regulations.
- Amendment3 pagesEnglish languagesale 10% offe-Library read for1 day
- Amendment43 pagesEnglish languagesale 10% offe-Library read for1 day
IEC 61139-3:2023 specifies a wireless single-drop digital communication interface (SDCI wireless).
This is an extension to the single-drop digital communication interface (SDCI) technology that is specified in IEC 61131-9.
This document specifies the wireless communication services and protocol (physical layer, data link layer and application layer in accordance with the ISO/OSI reference model) for W‑Masters and W‑Devices.
NOTE This document does not cover the integration into higher level systems such as fieldbuses.
- Standard368 pagesEnglish languagesale 10% offe-Library read for1 day
This part of IEC 62453 provides information for integrating the CIP™ technology into the FDT interface specification (IEC 62453-2). Communication Profile Family 2 (commonly known as CIP™1) defines communication profiles based on IEC 61158-2 Type 2, IEC 61158-3-2, IEC 61158-4-2, IEC 61158-5-2, IEC 61158-6-2, and IEC 62026-3. The basic profiles CP 2/1 (ControlNet™2), CP 2/2 (EtherNet/IP™3), and CP 2/3 (DeviceNet™1) are defined in IEC 61784-1 and IEC 61784-2. An additional communication profile (CompoNet™1), also based on CIP™, is defined in IEC 62026-7.
This part of IEC 62453 specifies communication and other services.
This specification neither contains the FDT specification nor modifies it.
- Standard39 pagesEnglish languagesale 10% offe-Library read for1 day
This part of IEC 62056 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. The ID codes defined in this document are used
for the identification of:
• logical names of the various instances of the ICs, or objects, as defined in
IEC 62056‑6‑2:2023;
• data transmitted through communication lines;
• data displayed on the metering equipment, see Clause A.2 in Annex A.
This document applies to all types of metering equipment, such as fully integrated meters,
modular meters, tariff attachments, data concentrators, etc.
To cover metering equipment measuring energy types other than electricity, combined metering
equipment measuring more than one type of energy or metering equipment with several physical
measurement channels, the concepts of medium and channels are introduced. This allows
meter data originating from different sources to be identified. While this document fully defines
the structure of the identification system for other media, the mapping of non-electrical energy
related data items to ID codes is completed separately.
NOTE EN 13757-1:2014 defines identifiers for metering equipment other than electricity: heat cost allocators,
thermal energy, gas, cold water and hot water.
- Standard46 pagesEnglish languagesale 10% offe-Library read for1 day
- Standard46 pagesEnglish languagesale 10% offe-Library read for1 day
This part of IEC 62056 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. The ID codes defined in this document are used for the identification of: - logical names of the various instances of the ICs, or objects, as defined in IEC 62056-6-2:2021; - data transmitted through communication lines; - data displayed on the metering equipment, see Clause A.2. This document applies to all types of metering equipment, such as fully integrated meters, modular meters, tariff attachments, data concentrators, etc. To cover metering equipment measuring energy types other than electricity, combined metering equipment measuring more than one type of energy or metering equipment with several physical measurement channels, the concepts of medium and channels are introduced. This allows meter data originating from different sources to be identified. While this document fully defines the structure of the identification system for other media, the mapping of non-electrical energy related data items to ID codes is completed separately. NOTE EN 13757-1:2014 defines identifiers for metering equipment other than electricity: heat cost allocators, thermal energy, gas, cold water and hot water.
- Standard46 pagesEnglish languagesale 10% offe-Library read for1 day
- Standard46 pagesEnglish languagesale 10% offe-Library read for1 day
IEC 61158-2:2023 is one of a series produced to facilitate the interconnection of automation system components. It is related to other standards in the set as defined by the "three-layer" fieldbus reference model described in IEC 61158‑1.
- Standard546 pagesEnglish languagesale 10% offe-Library read for1 day
Communication Profile Family 2 (commonly known as CIPTM1) defines communication profiles based on IEC 61158-2 Type 2, IEC 61158-3-2, IEC 61158-4-2, IEC 61158-5-2, IEC 61158-6-2, and IEC 62026-3. The basic profiles CP 2/1 (ControlNetTM2), CP 2/2 (EtherNet/IPTM3), and CP 2/3 (DeviceNetTM1) are defined in IEC 61784-1 and IEC 61784-2. An additional communication profile (CompoNetTM1), also based on CIPTM, is defined in [15]. This part of IEC 62453 provides information for integrating the CIPTM technology into the FDT interface specification (IEC 62453-2). This part of IEC 62453 specifies communication and other services. This specification neither contains the FDT specification nor modifies it.
- Standard39 pagesEnglish languagesale 10% offe-Library read for1 day
IEC 62056-6-1:2023 is available as IEC 62056-6-1:2023 RLV which contains the International Standard and its Redline version, showing all changes of the technical content compared to the previous edition.IEC 62056-6-1:2023 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. The ID codes defined in this document are used for the identification of:
- logical names of the various instances of the ICs, or objects, as defined in IEC 62056‑6‑2:2023;
- data transmitted through communication lines;
- data displayed on the metering equipment, see Clause A.2 in Annex A.
This document applies to all types of metering equipment, such as fully integrated meters, modular meters, tariff attachments, data concentrators, etc.
To cover metering equipment measuring energy types other than electricity, combined metering equipment measuring more than one type of energy or metering equipment with several physical measurement channels, the concepts of medium and channels are introduced. This allows meter data originating from different sources to be identified. While this document fully defines the structure of the identification system for other media, the mapping of non-electrical energy related data items to ID codes is completed separately
This fourth edition cancels and replaces the third edition of IEC 62056-6-1, published in 2017. This edition constitutes a technical revision. The main technical changes with respect to the previous edition are listed in Annex B (informative).
- Standard133 pagesEnglish languagesale 15% off
- Standard87 pagesEnglish and French languagesale 15% off
This part of IEC 62056 specifies a model of a meter as it is seen through its communication interface(s). Generic building blocks are defined using object-oriented methods, in the form of interface classes to model meters from simple up to very complex functionality.
Annexes A to F (informative) provide additional information related to some interface classes.
- Standard533 pagesEnglish languagesale 10% offe-Library read for1 day
This part of IEC 62056 specifies the DLMS®/COSEM application layer in terms of structure, services and protocols for DLMS®/COSEM clients and servers, and defines rules to specify the DLMS®/COSEM 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:2021 using either logical name (LN) or short name (SN) referencing.
Annex A (normative) defines how to use the COSEM application layer in various communication profiles. It specifies how various communication profiles can be constructed for exchanging data with metering equipment using the COSEM interface model, and what are the necessary elements to specify in each communication profile. The actual, media-specific communication profiles are specified in separate parts of the IEC 62056 series.
Annex B (normative) specifies the SMS short wrapper.
Annex C (normative) specifies the gateway protocol.
Annex D, Annex E and Annex F (informative) include encoding examples for APDUs.
Annex G (normative) provides NSA Suite B elliptic curves and domain parameters.
Annex H (informative) provides an example of an End entity signature certificate using P-256 signed with P-256.
Annex I (normative) specifies the use of key agreement schemes in DLMS®/COSEM.
Annex J (informative) provides examples of exchanging protected xDLMS APDUs between a third party and a server.
Annex K (informative) lists the main technical changes in this edition of the standard.
- Standard380 pagesEnglish languagesale 10% offe-Library read for1 day
IEC 62056-8-12:2023 describes the use of DLMS®/COSEM for Low-Power Wide Area Networks (LPWANs). It specifies how the COSEM data model and the DLMS®/COSEM application layer can be used over various LPWAN technologies using an adaptation layer based on IETF RFC 8724, and in particular over LoRaWAN.
This profile is intended to be used with LPWANs as defined in IETF RFC 8724, in particular LoRaWAN. Low-Power Wide Area Networks (LPWANs) are wireless technologies with characteristics such as large coverage areas, low bandwidth, possibly very small packet and application-layer data sizes, and long battery life operation. This document does not provide functionality to manage the lower layers of the LPWANs.
This part of the DLMS®/COSEM suite specifies the communication profile for Low-Power Wide Area Networks (LPWANs).
The DLMS®/COSEM LPWAN communication profiles use connection-less transport layer based on the Internet Standard User Datagram Protocol (UDP) and Internet Protocol (IPv6).
The adaptation layer is based on IETF RFC 8724 which provides both a header compression/decompression mechanism and an optional fragmentation/reassembly mechanism. SCHC compression is based on static context with small context identifier to represent full IPv6/UDP/COSEM wrapper headers. If required, SCHC fragmentation is used to support IPv6 MTU over the LPWAN technologies.
This document follows the rules defined in IEC 62056-5-3:2023, Annex A, and in IEC 62056-1-0, and IEC TS 62056-1-1:2016 for its structure. See also Annex A for examples
- Standard34 pagesEnglish languagesale 10% offe-Library read for1 day
IEC 62453-302:2023 is available as IEC 62453-302:2023 RLV which contains the International Standard and its Redline version, showing all changes of the technical content compared to the previous edition.
IEC 62453-302:2023 provides information for integrating the CIP™ technology into the FDT interface specification (IEC 62453‑2). Communication Profile Family 2 (commonly known as CIP™[1]) defines communication profiles based on IEC 61158-2 Type 2, IEC 61158-3-2, IEC 61158-4-2, IEC 61158-5-2, IEC 61158-6-2, and IEC 62026-3. The basic profiles CP 2/1 (ControlNet™[2]), CP 2/2 (EtherNet/IP™[3]), and CP 2/3 (DeviceNet™1) are defined in IEC 61784‑1 and IEC 61784‑2. An additional communication profile (CompoNet™1), also based on CIP™, is defined in IEC 62026-7. This part of IEC 62453 specifies communication and other services. This specification neither contains the FDT specification nor modifies it.
[1] CIP™ (Common Industrial Protocol), DeviceNet™ and CompoNet™ are trade names of Open DeviceNet Vendor Association, Inc (ODVA). This information is given for the convenience of users of this document and does not constitute an endorsement by IEC of the trade name holder or any of its products. Compliance to this standard does not require use of the trade names CIP™, DeviceNet™ or CompoNet™. Use of the trade names CIP™, DeviceNet™ or CompoNet™ requires permission of Open DeviceNet Vendor Association, Inc.
[2] ControlNet™ is a trade name of ControlNet International, Ltd. This information is given for the convenience of users of this document and does not constitute an endorsement by IEC of the trademark holder or any of its products. Compliance to this profile does not require use of the trade name ControlNet™. Use of the trade name ControlNet™ requires permission of ControlNet International, Ltd.
[3] EtherNet/IP™ is a trade name of ControlNet International, Ltd. and Open DeviceNet Vendor Association, Inc. This information is given for the convenience of users of this document and does not constitute an endorsement by IEC of the trademark holder or any of its products. Compliance to this profile does not require use of the trade name EtherNet/IP™. Use of the trade name EtherNet/IP™ requires permission of either ControlNet International, Ltd. or Open DeviceNet Vendor Association, Inc.
- Standard109 pagesEnglish languagesale 15% off
- Standard73 pagesEnglish and French languagesale 15% off
This part of IEC 62056 specifies a model of a meter as it is seen through its communication interface(s). Generic building blocks are defined using object-oriented methods, in the form of interface classes to model meters from simple up to very complex functionality. Annexes A to F (informative) provide additional information related to some interface classes.
- Standard533 pagesEnglish languagesale 10% offe-Library read for1 day
IEC 62056-8-12:2023 describes the use of DLMS®/COSEM for Low-Power Wide Area Networks (LPWANs). It specifies how the COSEM data model and the DLMS®/COSEM application layer can be used over various LPWAN technologies using an adaptation layer based on IETF RFC 8724, and in particular over LoRaWAN. This profile is intended to be used with LPWANs as defined in IETF RFC 8724, in particular LoRaWAN. Low-Power Wide Area Networks (LPWANs) are wireless technologies with characteristics such as large coverage areas, low bandwidth, possibly very small packet and application-layer data sizes, and long battery life operation. This document does not provide functionality to manage the lower layers of the LPWANs. This part of the DLMS®/COSEM suite specifies the communication profile for Low-Power Wide Area Networks (LPWANs). The DLMS®/COSEM LPWAN communication profiles use connection-less transport layer based on the Internet Standard User Datagram Protocol (UDP) and Internet Protocol (IPv6). The adaptation layer is based on IETF RFC 8724 which provides both a header compression/decompression mechanism and an optional fragmentation/reassembly mechanism. SCHC compression is based on static context with small context identifier to represent full IPv6/UDP/COSEM wrapper headers. If required, SCHC fragmentation is used to support IPv6 MTU over the LPWAN technologies. This document follows the rules defined in IEC 62056-5-3:2023, Annex A, and in IEC 62056-1-0, and IEC TS 62056-1-1:2016 for its structure. See also Annex A for examples
- Standard34 pagesEnglish languagesale 10% offe-Library read for1 day
This part of IEC 62056 specifies the DLMS®/COSEM application layer in terms of structure, services and protocols for DLMS®/COSEM clients and servers, and defines rules to specify the DLMS®/COSEM 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:2021 using either logical name (LN) or short name (SN) referencing. Annex A (normative) defines how to use the COSEM application layer in various communication profiles. It specifies how various communication profiles can be constructed for exchanging data with metering equipment using the COSEM interface model, and what are the necessary elements to specify in each communication profile. The actual, media-specific communication profiles are specified in separate parts of the IEC 62056 series. Annex B (normative) specifies the SMS short wrapper. Annex C (normative) specifies the gateway protocol. Annex D, Annex E and Annex F (informative) include encoding examples for APDUs. Annex G (normative) provides NSA Suite B elliptic curves and domain parameters. Annex H (informative) provides an example of an End entity signature certificate using P-256 signed with P-256. Annex I (normative) specifies the use of key agreement schemes in DLMS®/COSEM. Annex J (informative) provides examples of exchanging protected xDLMS APDUs between a third party and a server. Annex K (informative) lists the main technical changes in this edition of the standard.
- Standard380 pagesEnglish languagesale 10% offe-Library read for1 day
This document specifies the optical fibre access network cabling within multi-subscriber premises termed the premises distribution access network (PDAN). The premises may comprise single or multiple buildings.
The cabling specified is intended to be pre-installed, in readiness for subsequent connection of the multi-subscriber premises to an access providers infrastructure to support deployment of optical broadband networks.
This document does not specify either the access network cabling external to the premises or the cabling within the subscriber space for onward distribution of services beyond the customer premises equipment.
This document specifies:
a) the structure and configuration of the optical fibre cabling;
b) cabling performance requirements;
c) implementation options.
Safety practices in relation to optical power hazard are specified in EN 60825-2. Optical powers higher than the hazard levels specified in EN 60825-2 are not considered in this document.
Safety (electrical safety, fire, etc.) and electromagnetic compatibility (EMC) requirements are outside the scope of this document and are covered by other standards and regulations. However, information given in this document may be of assistance in meeting these standards and regulations.
- Standard42 pagesEnglish languagesale 10% offe-Library read for1 day
This document specifies the optical fibre access network cabling within single- and multi-subscriber premises termed the premises distribution access network (PDAN). The premises can comprise single or multiple buildings. The cabling specified is intended to be pre-installed, in readiness for subsequent connection of the multi-subscriber premises to an access providers infrastructure to support deployment of optical broadband networks. This document does not specify either the access network cabling external to the premises or the cabling within the subscriber space for onward distribution of services beyond the customer premises equipment. This document specifies: a) the structure and configuration of the optical fibre cabling; b) cabling performance requirements; c) implementation options. Annex A contains information on network segments not covered by this document. Safety practices in relation to optical power hazard are specified in EN 60825-2. Optical powers higher than the hazard levels specified in EN 60825-2 are not considered in this document. Safety (electrical safety, fire, etc.) and electromagnetic compatibility (EMC) requirements are outside the scope of this document and are covered by other standards and regulations. However, information given in this document can be of assistance in meeting these standards and regulations.
- Standard42 pagesEnglish languagesale 10% offe-Library read for1 day
The fieldbus application layer (FAL) provides user programs with a means to access the fieldbus communication environment. In this respect, the FAL can be viewed as a "window between corresponding application programs."
This part of IEC 61158 provides common elements for basic time-critical and non-time-critical messaging communications between application programs in an automation environment and material specific to Type 2 fieldbus. The term "time-critical" is used to represent the presence of a time-window, within which one or more specified actions are required to be completed with some defined level of certainty. Failure to complete specified actions within the time window risks failure of the applications requesting the actions, with attendant risk to equipment, plant and possibly human life.
This International Standard defines in an abstract way the externally visible service provided by the Type 2 fieldbus application layer in terms of:
a) an abstract model for defining application resources (objects) capable of being manipulated by users via the use of the FAL service,
b) the primitive actions and events of the service;
c) the parameters associated with each primitive action and event, and the form which they take; and
d) the interrelationship between these actions and events, and their valid sequences.
The purpose of this document is to define the services provided to:
a) the FAL user at the boundary between the user and the application layer of the fieldbus reference model, and
b) Systems Management at the boundary between the application layer and Systems Management of the fieldbus reference model.
This document specifies the structure and services of the Type 2 fieldbus application layer, in conformance with the OSI Basic Reference Model (ISO/IEC 7498-1) and the OSI application layer structure (ISO/IEC 9545).
FAL services and protocols are provided by FAL application-entities (AE) contained within the application processes. The FAL AE is composed of a set of object-oriented application service elements (ASEs) and a layer management entity (LME) that manages the AE. The ASEs provide communication services that operate on a set of related application process object (APO) classes. One of the FAL ASEs is a management ASE that provides a common set of services for the management of the instances of FAL classes.
Although these services specify, from the perspective of applications, how request and responses are issued and delivered, they do not include a specification of what the requesting and responding applications are to do with them. That is, the behavioral aspects of the applications are not specified; only a definition of what requests and responses they can send/receive is specified. This permits greater flexibility to the 318 FAL users in standardizing such object behavior. In addition to these services, some supporting services are also defined in this document to provide access to the FAL to control certain aspects of its operation.
- Standard120 pagesEnglish languagesale 10% offe-Library read for1 day
The Fieldbus Application Layer (FAL) provides user programs with a means to access the
fieldbus communication environment. In this respect, the FAL can be viewed as a "window
between corresponding application programs".
This part of IEC 61158 provides common elements for basic time-critical and non-time-critical
messaging communications between application programs in an automation environment and
material specific to Type 23 fieldbus. The term "time-critical" is used to represent the
presence of a time-window, within which one or more specified actions are required to be
completed with some defined level of certainty. Failure to complete specified actions within
the time window risks failure of the applications requesting the actions, with attendant risk to
equipment, plant and possibly human life.
This document defines in an abstract way the externally visible service provided by the
different Types of the fieldbus Application Layer in terms of
a) an abstract model for defining application resources (objects) capable of being
manipulated by users via the use of the FAL service,
b) the primitive actions and events of the service;
c) the parameters associated with each primitive action and event, and the form that they
take; and
d) the interrelationship between these actions and events, and their valid sequences.
The purpose of this document is to define the services provided to
a) the FAL user at the boundary between the user and the Application Layer of the Fieldbus
Reference Model, and
b) Systems Management at the boundary between the Application Layer and Systems
Management of the Fieldbus Reference Model.
This document specifies the structure and services of the IEC Fieldbus Application Layer, in
conformance with the OSI Basic Reference Model (ISO/IEC 7498-1) and the OSI Application
Layer Structure (ISO/IEC 9545).
FAL services and protocols are provided by FAL application-entities (AE) contained within the
application processes. The FAL AE is composed of a set of object-oriented Application
Service Elements (ASEs) and a Layer Management Entity (LME) that manages the AE. The
ASEs provide communication services that operate on a set of related application process
object (APO) classes. One of the FAL ASEs is a management ASE that provides a common
set of services for the management of the instances of FAL classes.
Although these services specify, from the perspective of applications, how request and
responses are issued and delivered, they do not include a specification of what the requesting
and responding applications are to do with them. That is, the behavioral aspects of the
applications are not specified; only a definition of what requests and responses they can
send/receive is specified. This permits greater flexibility to the FAL users in standardizing
such object behavior. In addition to these services, some supporting services are also defined
in this document to provide access to the FAL to control certain aspects of its operation.
- Standard123 pagesEnglish languagesale 10% offe-Library read for1 day
This part of IEC 61158 provides common elements for basic time-critical messaging
communications between devices in an automation environment. The term "time-critical" is used
to represent the presence of a time-window, within which one or more specified actions are
required to be completed with some defined level of certainty. Failure to complete specified
actions within the time-window risks failure of the applications requesting the actions, with
attendant risk to equipment, plant and possibly human life.
This document defines in an abstract way the externally visible service provided by the Type
24 fieldbus data-link layer in terms of
• the primitive actions and events of the service;
• the interrelationship between these actions and events, and their valid sequences;
• the parameters associated with each primitive action and event, and the form which they
take.
The purpose of this document is to define the services provided to
• the Type 24 fieldbus application layer at the boundary between the application and data-link
layers of the fieldbus reference model;
• systems management at the boundary between the data-link layer and systems
management of the fieldbus reference model.
- Standard43 pagesEnglish languagesale 10% offe-Library read for1 day
The Fieldbus Application Layer (FAL) provides user programs with a means to access the
fieldbus communication environment. In this respect, the FAL can be viewed as a “window
between corresponding application programs”.
This part of IEC 61158 provides common elements for basic time-critical and non-time-critical
messaging communications between application programs in an automation environment and
material specific to Type 10 fieldbus. The term “time-critical” is used to represent the presence
of a time window, within which one or more specified actions are required to be completed with
a defined level of certainty. Failure to complete specified actions within the time window risks
failure of the applications requesting the actions, with attendant risk to equipment, plant and
possibly human life.
This document defines in an abstract way the externally visible behavior provided by the
Type 10 fieldbus application layer in terms of:
• the abstract syntax defining the application layer protocol data units conveyed between
communicating application entities,
• the transfer syntax defining the application layer protocol data units conveyed between
communicating application entities,
• the application context state machine defining the application service behavior visible
between communicating application entities, and
• the application relationship state machines defining the communication behavior visible
between communicating application entities.
The purpose of this document is to define the protocol provided to:
• define the wire-representation of the service primitives defined in IEC 61158-5-10 and
• define the externally visible behavior associated with their transfer.
This document specifies the protocol of the Type 10 fieldbus application layer, in conformance
with the OSI Basic Reference Model (ISO/IEC 7498-1) and the OSI Application Layer Structure
(ISO/IEC 9545).
- Standard1185 pagesEnglish languagesale 10% offe-Library read for1 day
The fieldbus application layer (FAL) provides user programs with a means to access the fieldbus
communication environment. In this respect, the FAL can be viewed as a “window between
corresponding application programs.”
This part of IEC 61158 provides common elements for basic time-critical and non-time-critical
messaging communications between application programs in an automation environment and
material specific to Type 4 fieldbus. The term “time-critical” is used to represent the presence
of a time-window, within which one or more specified actions are required to be completed with
some defined level of certainty. Failure to complete specified actions within the time window
risks failure of the applications requesting the actions, with attendant risk to equipment, plant
and possibly human life.
This document specifies interactions between remote applications and defines the externally
visible behavior provided by the Type 4 fieldbus application layer in terms of
• the formal abstract syntax defining the application layer protocol data units conveyed
between communicating application entities;
• the transfer syntax defining encoding rules that are applied to the application layer protocol
data units;
• the application context state machine defining the application service behavior visible
between communicating application entities;
• the application relationship state machines defining the communication behavior visible
between communicating application entities.
The purpose of this document is to define the protocol provided to
• define the wire-representation of the service primitives defined in IEC 61158-5-4, and
• define the externally visible behavior associated with their transfer.
This document specifies the protocol of the Type 4 fieldbus application layer, in conformance
with the OSI Basic Reference Model (ISO/IEC 7498-1) and the OSI application layer structure
(ISO/IEC 9545).
- Standard44 pagesEnglish languagesale 10% offe-Library read for1 day
This part of IEC 61158 provides common elements for basic time-critical messaging
communications between devices in an automation environment. The term "time-critical" is used
to represent the presence of a time-window, within which one or more specified actions are
required to be completed with some defined level of certainty. Failure to complete specified
actions within the time window risks failure of the applications requesting the actions, with
attendant risk to equipment, plant and possibly human life.
This document defines in an abstract way the externally visible service provided by the Type 2
fieldbus data-link layer in terms of:
• the primitive actions and events of the service;
• the parameters associated with each primitive action and event, and the form which they
take; and
• the interrelationship between these actions and events, and their valid sequences.
The purpose of this document is to define the services provided to:
• the Type 2 fieldbus application layer at the boundary between the application and data-link
layers of the fieldbus reference model;
• systems management at the boundary between the data-link layer and systems
management of the fieldbus reference model.
Type 2 DL-service provides both a connected and a connectionless subset of those services
specified in ISO/IEC 8886.
- Standard51 pagesEnglish languagesale 10% offe-Library read for1 day
The Fieldbus Application Layer (FAL) provides user programs with a means to access the fieldbus communication environment. In this respect, the FAL can be viewed as a "window between corresponding application programs."
This part of IEC 61158 provides common elements for basic time-critical and non-time-critical messaging communications between application programs in an automation environment and material specific to Type 2 fieldbus. The term "time-critical" is used to represent the presence of a time-window, within which one or more specified actions are required to be completed with some defined level of certainty. Failure to complete specified actions within the time window risks failure of the applications requesting the actions, with attendant risk to equipment, plant and possibly human life.
This International Standard specifies interactions between remote applications and defines the externally visible behavior provided by the Type 2 fieldbus application layer in terms of
a) the formal abstract syntax defining the application layer protocol data units conveyed between communicating application entities;
b) the transfer syntax defining encoding rules that are applied to the application layer protocol data units;
c) the application context state machine defining the application service behavior visible between communicating application entities;
d) the application relationship state machines defining the communication behavior visible between communicating application entities.
The purpose of this document is to define the protocol provided to
a) define the wire-representation of the service primitives defined in IEC 61158-5-2, and
b) define the externally visible behavior associated with their transfer.
This document specifies the protocol of the Type 2 fieldbus application layer, in conformance with the OSI Basic Reference Model (ISO/IEC 7498-1) and the OSI application layer structure (ISO/IEC 9545).
- Standard210 pagesEnglish languagesale 10% offe-Library read for1 day
The fieldbus application layer (FAL) provides user programs with a means to access the fieldbus communication environment. In this respect, the FAL can be viewed as a "window between corresponding application programs."
This part of IEC 61158 provides common elements for basic time-critical and non-time-critical messaging communications between application programs in an automation environment and material specific to Type 27 fieldbus. The term "time-critical" is used to represent the presence of a time-window, within which one or more specified actions are required to be completed with some defined level of certainty. Failure to complete specified actions within the time window risks failure of the applications requesting the actions, with attendant risk to equipment, plant and possibly human life.
This International Standard defines in an abstract way the externally visible service provided by the different Types of fieldbus Application Layer in terms of
a) an abstract model for defining application resources (objects) capable of being manipulated by users via the use of the FAL service,
b) the primitive actions and events of the service,
c) the parameters associated with each primitive action and event, and the form which they take, and
d) the interrelationship between these actions and events, and their valid sequences.
The purpose of this International Standard is to define the services provided to
a) the FAL user at the boundary between the user and the Application Layer of the Fieldbus Reference Model, and
b) Systems Management at the boundary between the Application Layer and Systems Management of the Fieldbus Reference Model.
This International Standard specifies the structure and services of the IEC fieldbus Application Layer, in conformance with the OSI Basic Reference Model (ISO/IEC 7498-1) and the OSI Application Layer Structure (ISO/IEC 9545).
FAL services and protocols are provided by FAL application-entities (AE) contained within the application processes. The FAL AE is composed of a set of object-oriented Application Service Elements (ASEs) and a Layer Management Entity (LME) that manages the AE. The ASEs provide communication services that operate on a set of related application process object (APO) classes. One of the FAL ASEs is a management ASE that provides a common set of services for the management of the instances of FAL classes.
Although these services specify, from the perspective of applications, how request and responses are issued and delivered, they do not include a specification of what the requesting and responding applications are to do with them. That is, the behavioral aspects of the applications are not specified; only a definition of what requests and responses they can send/receive is specified. This permits greater flexibility to the 289 FAL users in standardizing such object behavior. In addition to these services, some supporting services are also defined in this International Standard to provide access to the FAL to control certain aspects of its operation.
- Standard222 pagesEnglish languagesale 10% offe-Library read for1 day
IEC 61158-4-21:2023 describes:
procedures for the timely transfer of data and control information from one data link user entity to a peer user entity, and among the data link entities forming the distributed data link service provider;
procedures for giving communication opportunities based on ISO/IEC/IEEE 8802‑3 MAC, with provisions for nodes to be added or removed during normal operation;
structure of the fieldbus data link protocol data units (DLPDUs) used for the transfer of data and control information by the protocol of this document, and their representation as physical interface data units.
- Standard112 pagesEnglish languagesale 10% offe-Library read for1 day
The fieldbus application layer (FAL) provides user programs with a means to access the fieldbus
communication environment. In this respect, the FAL can be viewed as a "window between
corresponding application programs."
This document provides common elements for basic time-critical and non-time-critical
messaging communications between application programs in an automation environment and
material specific to Type 24 fieldbus. The term "time-critical" is used to represent the presence
of a time-window, within which one or more specified actions are required to be completed with
some defined level of certainty. Failure to complete specified actions within the time window
risks failure of the applications requesting the actions, with attendant risk to equipment, plant
and possibly human life.
This document defines in an abstract way the externally visible service provided by the different
Types of fieldbus Application Layer in terms of
• an abstract model for defining application resources (objects) capable of being manipulated
by users via the use of the FAL service,
• the primitive actions and events of the service,
• the parameters associated with each primitive action and event, and the form which they
take, and
• the interrelationship between these actions and events, and their valid sequences.
The purpose of this International Standard is to define the services provided to
• the FAL user at the boundary between the user and the Application Layer of the Fieldbus
Reference Model, and
• Systems Management at the boundary between the Application Layer and Systems
Management of the Fieldbus Reference Model.
This document specifies the structure and services of the IEC fieldbus Application Layer, in
conformance with the OSI Basic Reference Model (ISO/IEC 7498-1) and the OSI Application
Layer Structure (ISO/IEC 9545).
FAL services and protocols are provided by FAL application-entities (AE) contained within the
application processes. The FAL AE is composed of a set of object-oriented Application Service
Elements (ASEs) and a Layer Management Entity (LME) that manages the AE. The ASEs
provide communication services that operate on a set of related application process object
(APO) classes. One of the FAL ASEs is a management ASE that provides a common set of
services for the management of the instances of FAL classes.
Although these services specify, from the perspective of applications, how request and
responses are issued and delivered, they do not include a specification of what the requesting
and responding applications are to do with them. That is, the behavioral aspects of the
applications are not specified; only a definition of what requests and responses they can
send/receive is specified. This permits greater flexibility to the FAL users in standardizing such
object behavior. In addition to these services, some supporting services are also defined in this
document to provide access to the FAL to control certain aspects of its operation.
- Standard105 pagesEnglish languagesale 10% offe-Library read for1 day
IEC 61158-3-4:2023 provides common elements for basic time-critical messaging communications between devices in an automation environment. The term "time-critical" is used to represent the presence of a time-window, within which one or more specified actions are required to be completed with some defined level of certainty. Failure to complete specified actions within the time window risks failure of the applications requesting the actions, with attendant risk to equipment, plant and possibly human life.
This document defines in an abstract way the externally visible services provided by the Type 4 fieldbus data-link layer in terms of
the primitive actions and events of the services;
the parameters associated with each primitive action and event, and the form which they take; and
the interrelationship between these actions and events, and their valid sequences.
The purpose of this document is to define the services provided to
the Type 4 fieldbus application layer at the boundary between the application and data-link layers of the fieldbus reference model;
systems management at the boundary between the data-link layer and systems management of the fieldbus reference model.
- Standard29 pagesEnglish languagesale 10% offe-Library read for1 day
This part of IEC 61158 describes basic packet communication services and models in an
automation control industrial field environment. The Type 28 data-link layer provides time-
critical and non-time-critical communication services. Time-critical refers to the requirement to
complete specified functions between devices in a defined time window in an industrial field
environment. Failure to complete specified functions within the time window can lead to failure
or harm in industrial production.
This document defines in an abstract way the externally visible service provided by the Type
28 fieldbus data-link layer in terms of
a) function description;
b) primitive actions and events with primitive sequence diagram;
c) the form of externally service interface and related parameters.
The purpose of this document is to define the services provided to:
• the Type 28 fieldbus application layer at the boundary between the application and data-link
layers of the fieldbus reference model;
• systems management at the boundary between the data-link layer and systems
management of the fieldbus reference model.
Type 28 DL-service provides both a connected and a connectionless subset of those services
provided by OSI data-link protocols as specified in ISO/IEC 8886.
- Standard60 pagesEnglish languagesale 10% offe-Library read for1 day
The fieldbus application layer (FAL) provides user programs with a means to access the fieldbus
communication environment. In this respect, the FAL can be viewed as a "window between
corresponding application programs."
This part of IEC 61158 provides common elements for basic time-critical and non-time-critical
messaging communications between application programs in an automation environment and
material specific to Type 2 fieldbus. The term "time-critical" is used to represent the presence
of a time-window, within which one or more specified actions are required to be completed with
some defined level of certainty. Failure to complete specified actions within the time window
risks failure of the applications requesting the actions, with attendant risk to equipment, plant
and possibly human life.
This document defines in an abstract way the externally visible service provided by the Type 2
fieldbus application layer in terms of:
• an abstract model for defining application resources (objects) capable of being manipulated
by users via the use of the FAL service;
• the primitive actions and events of the service;
• the parameters associated with each primitive action and event, and the form which they
take; and
• the interrelationship between these actions and events, and their valid sequences.
The purpose of this document is to define the services provided to:
• the FAL user at the boundary between the user and the application layer of the fieldbus
reference model; and
• Systems Management at the boundary between the application layer and Systems
Management of the fieldbus reference model.
This document specifies the structure and services of the Type 2 fieldbus application layer, in
conformance with the OSI Basic Reference Model (ISO/IEC 7498-1) and the OSI application
layer structure (ISO/IEC 9545).
FAL services and protocols are provided by FAL application-entities (AE) contained within the
application processes. The FAL AE is composed of a set of object-oriented application service
elements (ASEs) and a layer management entity (LME) that manages the AE. The ASEs provide
communication services that operate on a set of related application process object (APO)
classes. One of the FAL ASEs is a management ASE that provides a common set of services
for the management of the instances of FAL classes.
Although these services specify, from the perspective of applications, how request and
responses are issued and delivered, they do not include a specification of what the requesting
and responding applications are to do with them. That is, the behavioral aspects of the
applications are not specified; only a definition of what requests and responses they can
send/receive is specified. This permits greater flexibility to the FAL users in standardizing such
object behavior. In addition to these services, some supporting services are also defined in this
document to provide access to the FAL to control certain aspects of its operation.
- Standard244 pagesEnglish languagesale 10% offe-Library read for1 day
The fieldbus application layer (FAL) provides user programs with a means to access the fieldbus
communication environment. In this respect, the FAL can be viewed as a “window between
corresponding application programs".
This part of IEC 61158 provides common elements for basic time-critical and non-time-critical
messaging communications between application programs in an automation environment and
material specific to Type 10 fieldbus. The term "time-critical" is used to represent the presence
of a time-window, within which one or more specified actions are required to be completed with
some defined level of certainty. Failure to complete specified actions within the time window
risks failure of the applications requesting the actions, with attendant risk to equipment, plant
and possibly human life.
This document defines in an abstract way the externally visible service provided by the Type 10
fieldbus application layer in terms of:
• an abstract model for defining application resources (objects) capable of being manipulated
by users via the use of the FAL service,
• the primitive actions and events of the service;
• the parameters associated with each primitive action and event, and the form which they
take; and
• the interrelationship between these actions and events, and their valid sequences.
The purpose of this document is to define the services provided to:
• the FAL user at the boundary between the user and the application layer of the fieldbus
reference model, and
• Systems Management at the boundary between the application layer and Systems
Management of the fieldbus reference model.
This document specifies the structure and services of the Type 10 fieldbus application layer, in
conformance with the OSI Basic Reference Model (ISO/IEC 7498-1) and the OSI application
layer structure (ISO/IEC 9545).
FAL services and protocols are provided by FAL application-entities (AE) contained within the
application processes. The FAL AE is composed of a set of object-oriented application service
elements (ASEs) and a layer management entity (LME) that manages the AE. The ASEs provide
communication services that operate on a set of related application process object (APO)
classes. One of the FAL ASEs is a management ASE that provides a common set of services
for the management of the instances of FAL classes.
Although these services specify, from the perspective of applications, how request and
responses are issued and delivered, they do not include a specification of what the requesting
and responding applications are to do with them. That is, the behavioral aspects of the
applications are not specified; only a definition of what requests and responses they can
send/receive is specified. This permits greater flexibility to the FAL users in standardizing such
object behavior. In addition to these services, some supporting services are also defined in this
document to provide access to the FAL to control certain aspects of its operation.
- Standard767 pagesEnglish languagesale 10% offe-Library read for1 day
IEC 61158-1:2023 specifies the generic concept of fieldbuses. This document also presents an overview and guidance for the IEC 61158 eries by:
explaining the structure and content of the IEC 61158 series;
relating the structure of the IEC 61158 series to the ISO/IEC 7498-1 OSI Basic Reference Model;
showing the logical structure of the IEC 61784 series;
showing how to use parts of the IEC 61158 series in combination with the IEC 61784 series;
providing explanations of some aspects of the IEC 61158 series that are common to the type specific parts of the IEC 61158‑5 series including the application layer service description concepts and the generic fieldbus data types.
- Standard79 pagesEnglish languagesale 10% offe-Library read for1 day
The fieldbus application layer (FAL) provides user programs with a means to access the fieldbus
communication environment. In this respect, the FAL can be viewed as a "window between
corresponding application programs".
This part of IEC 61158 provides common elements for basic time-critical and non-time-critical
messaging communications between application programs in an automation environment and
material specific to Type 4 fieldbus. The term "time-critical" is used to represent the presence
of a time-window, within which one or more specified actions are required to be completed with
some defined level of certainty. Failure to complete specified actions within the time window
risks failure of the applications requesting the actions, with attendant risk to equipment, plant
and possibly human life.
This document defines in an abstract way the externally visible service provided by the Type 4
fieldbus application layer in terms of:
• an abstract model for defining application resources (objects) capable of being manipulated
by users via the use of the FAL service;
• the primitive actions and events of the service;
• the parameters associated with each primitive action and event, and the form which they
take; and
• the interrelationship between these actions and events, and their valid sequences.
The purpose of this document is to define the services provided to:
• the FAL user at the boundary between the user and the application layer of the fieldbus
reference model, and
• Systems Management at the boundary between the application layer and Systems
Management of the fieldbus reference model.
This document specifies the structure and services of the Type 4 fieldbus application layer, in
conformance with the OSI Basic Reference Model (ISO/IEC 7498-1) and the OSI application
layer structure (ISO/IEC 9545).
FAL services and protocols are provided by FAL application-entities (AE) contained within the
application processes. The FAL AE is composed of a set of object-oriented application service
elements (ASEs) and a layer management entity (LME) that manages the AE. The ASEs provide
communication services that operate on a set of related application process object (APO)
classes. One of the FAL ASEs is a management ASE that provides a common set of services
for the management of the instances of FAL classes.
Although these services specify, from the perspective of applications, how request and
responses are issued and delivered, they do not include a specification of what the requesting
and responding applications are to do with them. That is, the behavioral aspects of the
applications are not specified; only a definition of what requests and responses they can
send/receive is specified. This permits greater flexibility to the FAL users in standardizing such
object behavior. In addition to these services, some supporting services are also defined in this
document to provide access to the FAL to control certain aspects of its operation.
- Standard74 pagesEnglish languagesale 10% offe-Library read for1 day
IEC 61158-4-2:2023 is one of a series produced to facilitate the interconnection of automation system components. It is related to other standards in the set as defined by the "three-layer" fieldbus reference model described in IEC 61158‑1.
The data-link protocol provides the data-link service by making use of the services available from the physical layer. The primary aim of this document is to provide a set of rules for communication expressed in terms of the procedures to be carried out by peer data-link entities (DLEs) at the time of communication. These rules for communication are intended to provide a sound basis for development in order to serve a variety of purposes:
- as a guide for implementers and designers;
- for use in the testing and procurement of equipment;
- as part of an agreement for the admittance of systems into the open systems environment;
- as a refinement to the understanding of time-critical communications within OSI.
- Standard405 pagesEnglish languagesale 10% offe-Library read for1 day
IEC 61158-4-24:2023 provides
procedures for the timely transfer of data and control information from one data-link user entity to a peer user entity, and among the data-link entities forming the distributed datalink service provider;
procedures for giving communications opportunities to all participating DL-entities (DLEs), sequentially and in a cyclic manner for deterministic and synchronized transfer at cyclic intervals up to 64 ms;
procedures for giving communication opportunities available for time-critical data transmission together with non-time-critical data transmission without prejudice to the time-critical data transmission;
procedures for giving cyclic and acyclic communication opportunities for time-critical data transmission with prioritized access;
procedures for giving communication opportunities based on ISO/IEC/IEEE 8802‑3 medium access control, with provisions for nodes to be added or removed during normal operation;
the structure of the fieldbus DLPDUs used for the transfer of data and control information by the protocol of this document, and their representation as physical interface data units.
- Standard138 pagesEnglish languagesale 10% offe-Library read for1 day
The Fieldbus Application Layer (FAL) provides user programs with a means to access the
fieldbus communication environment. In this respect, the FAL can be viewed as a "window
between corresponding application programs".
This part of IEC 61158 provides common elements for basic time-critical and non-time-critical
messaging communications between application programs in an automation environment and
material specific to Type 24 fieldbus. The term "time-critical" is used to represent the presence
of a time-window, within which one or more specified actions are required to be completed with
some defined level of certainty. Failure to complete specified actions within the time window
risks failure of the applications requesting the actions, with attendant risk to equipment, plant
and possibly human life.
This document defines in an abstract way the externally visible behavior provided by the Type
24 fieldbus application layer in terms of
• the abstract syntax defining the application layer protocol data units conveyed between
communicating application entities,
• the transfer syntax defining the application layer protocol data units conveyed between
communicating application entities,
• the application context state machines defining the application service behavior visibly
between communicating application entities, and
• the application relationship state machines defining the communication behavior visibly
between communicating application entities.
The purpose of this document is to define the protocol provided to
• define the representation-on-wire of the service primitives defined in IEC 61158-5-24, and
• define the externally visible behavior associated with their transfer.
This document specifies the protocol of the Type 24 fieldbus application layer, in conformance
with the OSI Basic Reference Model (ISO/IEC 7498-1) and the OSI Application Layer Structure
(ISO/IEC 9545)
- Standard148 pagesEnglish languagesale 10% offe-Library read for1 day
The fieldbus application layer (FAL) provides user programs with a means to access the fieldbus
communication environment. In this respect, the FAL can be viewed as a "window between
corresponding application programs."
This part of IEC 61158 provides common elements for basic time-critical and non-time-critical
messaging communications between application programs in an automation environment and
material specific to Type 27 fieldbus. The term "time-critical" is used to represent the presence
of a time-window, within which one or more specified actions are required to be completed with
some defined level of certainty. Failure to complete specified actions within the time window
risks failure of the applications requesting the actions, with attendant risk to equipment, plant
and possibly human life.
This document defines in an abstract way the externally visible service provided by the different
Types of fieldbus Application Layer in terms of
• an abstract model for defining application resources (objects) capable of being manipulated
by users via the use of the FAL service,
• the primitive actions and events of the service,
• the parameters associated with each primitive action and event, and the form which they
take, and
• the interrelationship between these actions and events, and their valid sequences.
The purpose of this document is to define the services provided to
• the FAL user at the boundary between the user and the Application Layer of the Fieldbus
Reference Model, and
• Systems Management at the boundary between the Application Layer and Systems
Management of the Fieldbus Reference Model.
This document specifies the structure and services of the IEC fieldbus Application Layer, in
conformance with the OSI Basic Reference Model (ISO/IEC 7498-1) and the OSI Application
Layer Structure (ISO/IEC 9545).
FAL services and protocols are provided by FAL application-entities (AE) contained within the
application processes. The FAL AE is composed of a set of object-oriented Application Service
Elements (ASEs) and a Layer Management Entity (LME) that manages the AE. The ASEs
provide communication services that operate on a set of related application process object
(APO) classes. One of the FAL ASEs is a management ASE that provides a common set of
services for the management of the instances of FAL classes.
Although these services specify, from the perspective of applications, how request and
responses are issued and delivered, they do not include a specification of what the requesting
and responding applications are to do with them. That is, the behavioral aspects of the
applications are not specified; only a definition of what requests and responses they can
send/receive is specified. This permits greater flexibility to the FAL users in standardizing such
object behavior. In addition to these services, some supporting services are also defined in this
document to provide access to the FAL to control certain aspects of its operation.
- Standard143 pagesEnglish languagesale 10% offe-Library read for1 day
This document of IEC 61158 describes basic packet communication services and models in an automation control industrial field environment. The Type 28 data-link layer provides time critical and non-time-critical communication services. Time-critical refers to the requirement to complete specified functions between devices in a defined time window in an industrial field environment. Failure to complete specified functions within the time window may lead to failure or harm in industrial production.
This document defines in an abstract way the externally visible service provided by the Type 28 fieldbus data-link layer in terms of
a) function description;
b) primitive actions and events with primitive sequence diagram;
c) the form of externally service interface and related parameters.
The purpose of this document is to define the services provided to:
- the Type 28 fieldbus application layer at the boundary between the application and data link layers of the fieldbus reference model;
- systems management at the boundary between the data-link layer and systems management of the fieldbus reference model.
Type 28 DL-service provides both a connected and a connectionless subset of those services provided by OSI data-link protocols as specified in ISO/IEC 8886.
- Standard56 pagesEnglish languagesale 10% offe-Library read for1 day
The Fieldbus Application Layer (FAL) provides user programs with a means to access the
fieldbus communication environment. In this respect, the FAL can be viewed as a "window
between corresponding application programs."
This part of IEC 61158 provides common elements for basic time-critical and non-time-critical
messaging communications between application programs in an automation environment and
material specific to Type 2 fieldbus. The term "time-critical" is used to represent the presence
of a time-window, within which one or more specified actions are required to be completed with
some defined level of certainty. Failure to complete specified actions within the time window
risks failure of the applications requesting the actions, with attendant risk to equipment, plant
and possibly human life.
This document specifies interactions between remote applications and defines the externally
visible behavior provided by the Type 2 fieldbus application layer in terms of
• the formal abstract syntax defining the application layer protocol data units conveyed
between communicating application entities;
• the transfer syntax defining encoding rules that are applied to the application layer protocol
data units;
• the application context state machine defining the application service behavior visible
between communicating application entities;
• the application relationship state machines defining the communication behavior visible
between communicating application entities.
The purpose of this document is to define the protocol provided to
• define the wire-representation of the service primitives defined in IEC 61158-5-2, and
• define the externally visible behavior associated with their transfer.
This document specifies the protocol of the Type 2 fieldbus application layer, in conformance
with the OSI Basic Reference Model (ISO/IEC 7498-1) and the OSI application layer structure
(ISO/IEC 9545)
- Standard293 pagesEnglish languagesale 10% offe-Library read for1 day
The fieldbus Application Layer (FAL) provides user programs with a means to access the
fieldbus communication environment. In this respect, the FAL can be considered as a window
between corresponding application programs.
This part of IEC 61158 provides common elements for basic time-critical and non-time-critical
messaging communications between application programs in an automation environment and
material specific to Type 28 fieldbus. The term "time-critical" is used to represent the presence
of a time-window, in which one or more specified actions are required to be completed with
some defined level of certainty.
This document defines in an abstract way the externally visible service provided by the different
Types of the fieldbus Application Layer in terms of
• an abstract model for defining application resources (objects) capable of being manipulated
by users via the use of the FAL service,
• the primitive actions and events of the service,
• the parameters associated with each primitive action and event, and the form which they
take, and
• the interrelationship between these actions and events, and their valid sequences.
The purpose of this document is to define the services provided to
• the FAL user at the boundary between the user and the Application Layer of the Fieldbus
Reference Model, and
• Systems Management at the boundary between the Application Layer and Systems
Management of the Fieldbus Reference Model.
This document specifies the structure and services of the IEC fieldbus Application Layer, in
conformance with the OSI Basic Reference Model (ISO/IEC 7498-1) and the OSI Application
Layer Structure (ISO/IEC 9545).
FAL services and protocols are provided by FAL application-entities (AE) contained within the
application processes. The FAL AE is composed of a set of object-oriented Application Service
Elements (ASEs) and a Layer Management Entity (LME) that manages the AE. The ASEs
provide communication services that operate on a set of related application process object
(APO) classes. One of the FAL ASEs is a management ASE that provides a common set of
services for the management of the instances of FAL classes.
Although these services specify, from the perspective of applications, how to request and
response are issued and delivered, they do not include a specification of what the requesting
and responding applications are to do with them. That is, the behavioural aspects of the
applications are not specified; only a definition of what requests and responses they can
send/receive is specified. This permits greater flexibility to the FAL users in standardizing such
object behaviour. In addition to these services, some supporting services are also defined in
this document to provide access to the FAL to control certain aspects of its operation.
- Standard70 pagesEnglish languagesale 10% offe-Library read for1 day
- Corrigendum12 pagesEnglish languagesale 10% offe-Library read for1 day
The Fieldbus Application Layer (FAL) provides user programs with a means to access the
fieldbus communication environment. In this respect, the FAL can be considered as a window
between corresponding application programs.
This part of IEC 61158 provides common elements for basic time-critical and non-time-critical
messaging communications between application programs in an automation environment and
material specific to Type 28 fieldbus. The term "time-critical" is used to represent the presence
of a time-window, within which one or more specified actions are required to be completed with
some defined level of certainty. Failure to complete specified actions within the time window
can cause failure of the applications requesting the actions, with attendant risk to equipment,
plant and possibly human life.
This document defines in an abstract way the externally visible behavior provided by the
Type 28 of the fieldbus Application Layer in terms of:
• the abstract syntax defining the application layer protocol data units conveyed between
communicating application entities,
• the transfer syntax defining the application layer protocol data units conveyed between
communicating application entities,
• the application context state machine defining the application service behavior visible
between communicating application entities; and
• the application relationship state machines defining the communication behavior visible
between communicating application entities.
The purpose of this document is to define the protocol provided to:
• the wire-representation of the service primitives defined in IEC 61158-5-28, and
• the externally visible behavior associated with their transfer.
This document specifies the protocol of the Type 28 IEC fieldbus application layer, in
conformance with the OSI Basic Reference Model (ISO/IEC 7498) and the OSI Application
Layer Structure (ISO/IEC 9545).
- Standard28 pagesEnglish languagesale 10% offe-Library read for1 day
- Corrigendum5 pagesEnglish languagesale 10% offe-Library read for1 day
The Fieldbus Application Layer (FAL) provides user programs with a means to access the
fieldbus communication environment. In this respect, the FAL can be viewed as a "window
between corresponding application programs".
This part of IEC 61158 provides common elements for basic time-critical and non-time-critical
messaging communications between application programs in an automation environment and
material specific to Type 23 fieldbus. The term "time-critical" is used to represent the
presence of a time-window, within which one or more specified actions are required to be
completed with some defined level of certainty. Failure to complete specified actions within
the time window risks failure of the applications requesting the actions, with attendant risk to
equipment, plant and possibly human life.
This document defines in an abstract way the externally visible behavior provided by the
different Types of the fieldbus Application Layer in terms of:
a) the abstract syntax defining the application layer protocol data units conveyed between
communicating application entities,
b) the transfer syntax defining the application layer protocol data units conveyed between
communicating application entities,
c) the application context state machine defining the application service behavior visible
between communicating application entities; and
d) the application relationship state machines defining the communication behavior visible
between communicating application entities.
The purpose of this document is to define the protocol provided to:
a) define the wire-representation of the service primitives defined in IEC 61158-5-23, and
b) define the externally visible behavior associated with their transfer.
This document specifies the protocol of the IEC fieldbus Application Layer, in conformance
with the OSI Basic Reference Model (ISO/IEC 7498) and the OSI Application Layer Structure
(ISO/IEC 9545).
FAL services and protocols are provided by FAL application-entities (AE) contained within the
application processes. The FAL AE is composed of a set of object-oriented Application
Service Elements (ASEs) and a Layer Management Entity (LME) that manages the AE. The
ASEs provide communication services that operate on a set of related application process
object (APO) classes. One of the FAL ASEs is a management ASE that provides a common
set of services for the management of the instances of FAL classes.
Although these services specify, from the perspective of applications, how request and
responses are issued and delivered, they do not include a specification of what the requesting
and responding applications are to do with them. That is, the behavioral aspects of the
applications are not specified; only a definition of what requests and responses they can
send/receive is specified. This permits greater flexibility to the FAL users in standardizing
such object behavior. In addition to these services, some supporting services are also defined
in this document to provide access to the FAL to control certain aspects of its operation.
- Standard312 pagesEnglish languagesale 10% offe-Library read for1 day
IEC 62056-5-3:2023 specifies the DLMS®/COSEM application layer in terms of structure, services and protocols for DLMS®/COSEM clients and servers, and defines rules to specify the DLMS®/COSEM 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:2021 using either logical name (LN) or short name (SN) referencing.
Annex A (normative) defines how to use the COSEM application layer in various communication profiles. It specifies how various communication profiles can be constructed for exchanging data with metering equipment using the COSEM interface model, and what are the necessary elements to specify in each communication profile. The actual, media-specific communication profiles are specified in separate parts of the IEC 62056 series.
Annex B (normative) specifies the SMS short wrapper.
Annex C (normative) specifies the gateway protocol.
Annex D, Annex E and Annex F (informative) include encoding examples for APDUs.
Annex G (normative) provides NSA Suite B elliptic curves and domain parameters.
Annex H (informative) provides an example of an End entity signature certificate using P-256 signed with P-256.
Annex I (normative) specifies the use of key agreement schemes in DLMS®/COSEM.
Annex J (informative) provides examples of exchanging protected xDLMS APDUs between a third party and a server.
This fourth edition cancels and replaces the third edition published in 2017. This edition constitutes a technical revision.
The significant technical changes with respect to the previous edition are listed in Annex K (Informative).
- Standard765 pagesEnglish and French languagesale 15% off
IEC 62056-6-2:2023 specifies a model of a meter as it is seen through its communication interface(s). Generic building blocks are defined using object-oriented methods, in the form of interface classes to model meters from simple up to very complex functionality.
Annexes A to F (informative) provide additional information related to some interface classes
This fourth edition cancels and replaces the third edition of IEC 62056-6-2 published in 2017. It constitutes a technical revision. The significant technical changes with respect to the previous edition are listed in Annex F (Informative).
- Standard1067 pagesEnglish and French languagesale 15% off
IEC 62056-8-12:2023 describes the use of DLMS®/COSEM for Low-Power Wide Area Networks (LPWANs). It specifies how the COSEM data model and the DLMS®/COSEM application layer can be used over various LPWAN technologies using an adaptation layer based on IETF RFC 8724, and in particular over LoRaWAN.
This profile is intended to be used with LPWANs as defined in IETF RFC 8724, in particular LoRaWAN. Low-Power Wide Area Networks (LPWANs) are wireless technologies with characteristics such as large coverage areas, low bandwidth, possibly very small packet and application-layer data sizes, and long battery life operation. This document does not provide functionality to manage the lower layers of the LPWANs.
This part of the DLMS®/COSEM suite specifies the communication profile for Low-Power Wide Area Networks (LPWANs).
The DLMS®/COSEM LPWAN communication profiles use connection-less transport layer based on the Internet Standard User Datagram Protocol (UDP) and Internet Protocol (IPv6).
The adaptation layer is based on IETF RFC 8724 which provides both a header compression/decompression mechanism and an optional fragmentation/reassembly mechanism. SCHC compression is based on static context with small context identifier to represent full IPv6/UDP/COSEM wrapper headers. If required, SCHC fragmentation is used to support IPv6 MTU over the LPWAN technologies.
This document follows the rules defined in IEC 62056-5-3:2023, Annex A, and in IEC 62056-1-0, and IEC TS 62056-1-1:2016 for its structure. See also Annex A for examples
- Standard61 pagesEnglish and French languagesale 15% off
This document provides a maturity model addressing the environmental impact (energy management and environmental sustainability) of the facilities, infrastructures and the information and communication technology (ICT) equipment accommodated by the data centre.
- Technical specification65 pagesEnglish languagesale 10% offe-Library read for1 day