35.100.70 - Application layer
ICS 35.100.70 Details
Application layer
Anwenderschicht (Application layer)
Couche application
Uporabniški sloj
General Information
e-Library Subscription
Create subscription and get permanent access to documents within 35.100.70 - Application layer
Currently subscription includes documents marked with .We are working on making all documents available within the subscription.
IEC 61158-6-26:2023 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 26 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.
- Standard206 pagesEnglish languagesale 15% off
IEC 61158-6-10:2023 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.
- Standard1179 pagesEnglish languagesale 15% off
IEC 61158-6-24:2023 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.
- Standard145 pagesEnglish languagesale 15% off
IEC 61158-6-23:2023 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.
- Standard309 pagesEnglish languagesale 15% off
IEC 61158-6-4:2023 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.
- Standard41 pagesEnglish languagesale 15% off
IEC 61158-6-2:2023 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.
- Standard289 pagesEnglish languagesale 15% off
IEC 61158-5-4:2023 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.
- Standard71 pagesEnglish languagesale 15% off
IEC 61158-5-10:2023 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.
- Standard762 pagesEnglish languagesale 15% off
IEC 61158-5-2:2023 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.
- Standard240 pagesEnglish languagesale 15% off
IEC 61158-5-26:2023 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 26 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 Type26 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.
- Standard116 pagesEnglish languagesale 15% off
IEC 61158-5-25:2023 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.
- Standard120 pagesEnglish languagesale 15% off
IEC 61158-5-24:2023 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.
- Standard102 pagesEnglish languagesale 15% off
IEC 62055-42:2022, specifies a token generation mechanism and token structure for smart prepayment functionality in markets where IEC 62055-41 compliant systems are not used, and where a different security mechanism is required by project-specific or national requirements. This document specifies token structure, authentication and an anti-replay mechanism, token operating model, and protocol. This document is informed by the STS Association key management services, and by the key management mechanisms used within the DLMS/COSEM security model within IEC 62056‑6‑2. Reference is made to the international STS token standards (IEC 62055-41, IEC 62055-51 and IEC 62055-52) for payment metering systems, and interworking has been considered where appropriate in terms of token carrier ranges in the decimal domain. IEC 62055-41 tokens and those described in this document are not interoperable, however their domains are designed to be mutually exclusive to ensure the two kinds of tokens do not interfere with each other. Metering application processing and functionality, HAN interface commands and attributes, WAN interface commands and attributes are outside the scope of this document; however, reference is made to other standards in this regard. The mechanism for auditing and retrieving data from the meter relating to tariffication, meter readings, profile data and other legal metrology information is outside the scope of this document; however, this is defined as part of any overall metering solution. Such interfaces for retrieving data from a meter may be defined using suitable protocols such as DLMS/COSEM as defined in the IEC 62056 series.
- Standard84 pagesEnglish languagesale 10% offe-Library read for1 day
IEC 61158-6-4:2019 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. The purpose of this document is to define the protocol provided to a) define the wire-representation of the service primitives defined in this document, 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). This third edition includes the following significant technical changes with respect to the previous edition: a) additional user parameters to services; b) additional services to support distributed objects; c) additional secure services.
- Standard43 pagesEnglish languagesale 10% offe-Library read for1 day
IEC 61158-6-26:2019 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. The purpose of this document is to define the protocol provided to a) define the wire-representation of the service primitives defined in this document, 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).
- Standard187 pagesEnglish languagesale 10% offe-Library read for1 day
IEC 61158-6-21:2019 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. The purpose of this document is to define the protocol provided to a) define the wire-representation of the service primitives defined in this document, 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). This second edition includes the following significant technical changes with respect to the previous edition: - added WriteAndRead service; - miscellaneous editorial corrections.
- Standard58 pagesEnglish languagesale 10% offe-Library read for1 day
IEC 61158-6-10:2019 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. The purpose of this document is to define the protocol provided to a) define the wire-representation of the service primitives defined in this document, 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). This fourth edition includes the following significant technical changes with respect to the previous edition: a) integration of system redundancy basic functionality; b) integration of dynamic reconfiguration basic functionality; c) integration of reporting system basic functionality; d) integration of asset management basic functionality; e) integration of media redundancy ring interconnection basic functionality.
- Standard899 pagesEnglish languagesale 10% offe-Library read for1 day
IEC 61158-6-12:2019 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. The purpose of this document is to define the protocol provided to a) define the wire-representation of the service primitives defined in this document, 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). This fourth edition includes the following significant technical changes with respect to the previous edition: - technical corrections; and - editorial improvements for clarification.
- Standard146 pagesEnglish languagesale 10% offe-Library read for1 day
IEC 61158-6-25:2019 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. The purpose of this document is to define the protocol provided to a) define the wire-representation of the service primitives defined in this document, 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).
- Standard127 pagesEnglish languagesale 10% offe-Library read for1 day
IEC 61158-6-19:2019 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. The purpose of this document is to define the protocol provided to a) define the wire-representation of the service primitives defined in this document, 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). This fourth edition includes the following significant technical changes with respect to the previous edition: - improving the hotplug and redundancy features; - improving the phase switching and the error handling; - editorial improvements.
- Standard26 pagesEnglish languagesale 10% offe-Library read for1 day
IEC 61158-6-23:2019 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. The purpose of this document is to define the protocol provided to a) define the wire-representation of the service primitives defined in this document, 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). This second edition includes the following significant technical changes with respect to the previous edition: - addition of the transmission extended mode and related attribute (Clauses 3.2.28, 4.1.9, 4.4, 5.2.9.2, and 5.3); - update of Table 4, Table 5, Table 16 and Table 48.
- Standard228 pagesEnglish languagesale 10% offe-Library read for1 day
IEC 61158-6-3:2019 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. The purpose of this document is to define the protocol provided to a) define the wire-representation of the service primitives defined in this document, 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). This fourth edition includes the following significant technical changes with respect to the previous edition: - corrected substitutions in Table 4; - corrections in 5.3.14; - corrections in 5.5.6; - corrections in 5.17.15; - corrections in 5.17.16.2; - spelling and grammar.
- Standard381 pagesEnglish languagesale 10% offe-Library read for1 day
IEC 61158-6-2:2019 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. The purpose of this document is to define the protocol provided to a) define the wire-representation of the service primitives defined in this document, 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). This fourth edition includes the following significant technical changes with respect to the previous edition: - clarifications of response PDU formats in case of failure in 4.1.5; - clarifications of connection request priority definition and handling in 4.1.6.5 and 4.1.6.6; - clarification of connection remaining path in 4.1.6.12; - extensions of general syntax in 4.1.8.1; - extensions and clarifications of Identity object PDUs in 4.1.8.2; - updates of Assembly object PDUs in 4.1.8.4; - extensions and clarification of Time sync object PDUs in 4.1.8.6; - updates of Parameter object PDUs in 4.1.8.7; - extensions of Connection Manager object PDUs in 4.1.8.8; - clarifications of Connection object PDUs in 4.1.8.9; - extensions and clarifications of message and connection paths in 4.1.9; - updates of object and service class codes in 4.1.10 and error codes in 4.1.11; - updates of data types in 4.2.4, 5.1.3 and 5.2.3; - updates of the encapsulation abstract syntax in 4.3; - updates to the DLL mapping protocol machine 2 in Clause 11; - miscellaneous editorial corrections.
- Standard276 pagesEnglish languagesale 10% offe-Library read for1 day
IEC 62055-42:2022, specifies a token generation mechanism and token structure for smart prepayment functionality in markets where IEC 62055-41 compliant systems are not used, and where a different security mechanism is required by project-specific or national requirements. This document specifies token structure, authentication and an anti-replay mechanism, token operating model, and protocol.
This document is informed by the STS Association key management services, and by the key management mechanisms used within the DLMS/COSEM security model within IEC 62056‑6‑2. Reference is made to the international STS token standards (IEC 62055-41, IEC 62055-51 and IEC 62055-52) for payment metering systems, and interworking has been considered where appropriate in terms of token carrier ranges in the decimal domain. IEC 62055-41 tokens and those described in this document are not interoperable, however their domains are designed to be mutually exclusive to ensure the two kinds of tokens do not interfere with each other.
Metering application processing and functionality, HAN interface commands and attributes, WAN interface commands and attributes are outside the scope of this document; however, reference is made to other standards in this regard.
The mechanism for auditing and retrieving data from the meter relating to tariffication, meter readings, profile data and other legal metrology information is outside the scope of this document; however, this is defined as part of any overall metering solution. Such interfaces for retrieving data from a meter may be defined using suitable protocols such as DLMS/COSEM as defined in the IEC 62056 series.
- Standard163 pagesEnglish and French languagesale 15% off
This document specifies data exchange and communications for meters in a generic way.
This document establishes a protocol specification for the Application Layer for meters and establishes several protocols for meter communications which can be applied depending on the application being fulfilled.
This document also 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.
NOTE Electricity meters are not covered by this document, as the standardization of remote readout of electricity meters is a task for CENELEC/IEC.
- Standard129 pagesEnglish languagesale 10% offe-Library read for1 day
- Draft130 pagesEnglish languagesale 10% offe-Library read for1 day
IEC 61158-5-25:2019 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 ApplicationLayer 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
- Standard74 pagesEnglish languagesale 10% offe-Library read for1 day
IEC 61158-5-26:2019(E) specifies the structure and services of the IEC fieldbus Application Layer, in conformance with the OSI Basic Reference Model (see ISO/IEC 7498-1) and the OSI Application Layer Structure (see 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.
- Standard108 pagesEnglish languagesale 10% offe-Library read for1 day
IEC 61158-5-23:2019 defines 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 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). This second edition cancels and replaces the first edition published in 2014. This edition constitutes a technical revision. This edition includes the following significant technical changes with respect to the previous edition:•addition of an attribute for Master ID (see 3.2.10, 6.4.3, 6.4.4 and 6.4.5)
- Standard97 pagesEnglish languagesale 10% offe-Library read for1 day
IEC 61158-5-4:2019 (E) defines 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 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). This third edition cancels and replaces the second edition published in 2014. This edition constitutes a technical revision. This edition includes the following significant technical changes with respect to the previous edition: a) additional user parameters to services; b) additional services to support distributed objects; c) additional secure services.
- Standard224 pagesEnglish languagesale 10% offe-Library read for1 day
IEC 61158-5-12:2019 defines 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 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). This fourth edition cancels and replaces the third edition published in 2014 and constitutes a technical revision. This edition includes the following significant technical changes with respect to the previous edition: •Technical corrections; and •Editorial improvements for clarification
- Standard120 pagesEnglish languagesale 10% offe-Library read for1 day
IEC 61158-5-19:2019 defines 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 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). This fourth edition cancels and replaces the third edition published in 2014 and constitutes a technical revision. This edition includes the following significant technical changes with respect to the previous edition: •improving the hotplug and redundancy features; •improving the phase switching and the error handling;•editorial improvements
- Standard37 pagesEnglish languagesale 10% offe-Library read for1 day
IEC 61158-5-21:2019 specifies the structure and services of the type 21 IEC fieldbus Application Layer, in conformance with the OSI Basic Reference Model (ISO/IEC 7498) and the OSI Application Layer Structure (ISO/IEC 9545). This second edition cancels and replaces the first edition published in 2010. This edition constitutes a technical revision. This edition includes the following significant technical changes with respect to the previous edition: •added Write and Read service; •miscellaneous editorial corrections.
- Standard83 pagesEnglish languagesale 10% offe-Library read for1 day
IEC 61158-5-4:2019 (E) defines 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 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). This third edition cancels and replaces the second edition published in 2014. This edition constitutes a technical revision. This edition includes the following significant technical changes with respect to the previous edition: a) additional user parameters to services; b) additional services to support distributed objects; c) additional secure services.
- Standard74 pagesEnglish languagesale 10% offe-Library read for1 day
IEC 61158-5-10:2019 (E) defines 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 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). This fourth edition cancels and replaces the third edition published in 2014 and constitutes a technical revision which includes the following significant technical changes with respect to the previous edition: – integration of system redundancy basic functionality; – integration of dynamic reconfiguration basic functionality; – integration of reporting system basic functionality; –-integration of asset management basic functionality; – integration of media redundancy ring interconnection basic functionality.
- Standard634 pagesEnglish languagesale 10% offe-Library read for1 day
This document defines a technology independent model for a set of abstract services that is
located above the application layer of the OSI model, and that is used for exchanging
transaction messages based on the transaction models defined in IEC 62264-5. The model,
which is called the Messaging Service Model (MSM), is intended for interoperability between
manufacturing operations domain applications and applications in other domains.
NOTE It is recognized that other sets of services not defined in accordance with this document are possible for the
exchange of MOM information and are not deemed invalid as a result of this document.
- Standard53 pagesEnglish languagesale 10% offe-Library read for1 day
- Draft53 pagesEnglish languagesale 10% offe-Library read for1 day
This document defines a technology independent model for a set of abstract services that is located above the application layer of the OSI model, and that is used for exchanging transaction messages based on the transaction models defined in IEC 62264-5. The model, which is called the Messaging Service Model (MSM), is intended for interoperability between manufacturing operations domain applications and applications in other domains. NOTE It is recognized that other sets of services not defined in accordance with this document are possible for the exchange of MOM information and are not deemed invalid as a result of this document.
- Standard53 pagesEnglish languagesale 10% offe-Library read for1 day
- Draft53 pagesEnglish languagesale 10% offe-Library read for1 day
This document specifies data exchange and communications for meters in a generic way.
This document establishes a protocol specification for the Application Layer for meters and establishes several protocols for meter communications which can be applied depending on the application being fulfilled.
This document also 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.”
NOTE Electricity meters are not covered by this document, as the standardization of remote readout of electricity meters is a task for CENELEC/IEC.
- Standard129 pagesEnglish languagesale 10% offe-Library read for1 day
- Draft130 pagesEnglish languagesale 10% offe-Library read for1 day
The scope of this Recommendation | International Standard is threefold. This Recommendation | International Standard provides guidance on how to prepare new and old protocols for cryptographic algorithm migration, and defines auxiliary cryptographic algorithms to be used for migration purposes. This Recommendation | International Standard specifies a general wrapper protocol that provides authentication, integrity and confidentiality (encryption) protection for other protocols. This wrapper protocol includes a migration path for cryptographic algorithms allowing for smooth migration to stronger cryptographic algorithms as such requirements evolve. This will allow migration to quantum-safe cryptographic algorithms. Protected protocols can then be developed without taking security and cryptographic algorithms into consideration. This Recommendation | International Standard also includes some protocols to be protected by the wrapper protocol primarily for support of public-key infrastructure (PKI). Other specifications, e.g., Recommendations or International Standards, may also develop protocols designed to be protected by the wrapper protocol.
- Standard84 pagesEnglish languagesale 15% off
This document addresses some of the security requirements in the areas of authentication and other security services through the provision of a set of frameworks upon which full services can be based. Specifically, this Recommendation | International Standard defines frameworks for: ? public-key certificates; and ? attribute certificates. The public-key certificate framework defined in this Recommendation | International Standard specifies the information objects and data types for a public-key infrastructure (PKI), including public-key certificates, certificate revocation lists (CRLs), trust broker and authorization and validation lists (AVLs). The attribute certificate framework specifies the information objects and data types for a privilege management infrastructure (PMI), including attribute certificates, and attribute certificate revocation lists (ACRLs). This Recommendation | International Standard also provides the framework for issuing, managing, using and revoking certificates. An extensibility mechanism is included in the defined formats for both certificate types and for all revocation list schemes. This Recommendation | International Standard also includes a set of extensions, which is expected to be generally useful across a number of applications of PKI and PMI. The schema components (including object classes, attribute types and matching rules) for storing PKI and PMI information in a directory, are included in this Recommendation | International Standard. This Recommendation | International Standard specifies the framework for strong authentication, involving credentials formed using cryptographic techniques. It is not intended to establish this as a general framework for authentication, but it can be of general use for applications which consider these techniques adequate. Authentication (and other security services) can only be provided within the context of a defined security policy. It is a matter for users of an application to define their own security policy.
- Standard224 pagesEnglish languagesale 15% off
- Standard224 pagesEnglish languagesale 15% off
This document defines a number of attribute types and matching rules which may be found useful across a range of applications of the Directory. Attribute types and matching rules fall into three categories, as described below. Some attribute types and matching rules are used by a wide variety of applications or are understood and/or used by the Directory itself. NOTE 1 ? It is recommended that an attribute type or matching rule defined in this Recommendation | International Standard be used, in preference to the generation of a new one, whenever it is appropriate for the application. NOTE 2 ? The attribute and context types definitions by this Recommendation | International Standard have some associated semantics. Such specifications should not be used in situations where these semantics do not apply. Some attribute types and matching rules are internationally standardized, but are application‑specific. These are defined in the standards associated with the application concerned. Any administrative authority can define its own attribute types and matching rules for any purpose. These are not internationally standardized, and are available to others beyond the administrative authority which created them only through bilateral agreement.
- Standard122 pagesEnglish languagesale 15% off
- Standard122 pagesEnglish languagesale 15% off
This document specifies the Directory Access Protocol, the Directory System Protocol, the Directory Information Shadowing Protocol, and the Directory Operational Binding Management Protocol which fulfil the abstract services specified in Rec. ITU-T X.511 | ISO/IEC 9594-3, Rec. ITU-T X.518 | ISO/IEC 9594-4, Rec. ITU‑T X.525 | ISO/IEC 9594-9, and Rec. ITU-T X.501 | ISO/IEC 9594-2.
- Standard83 pagesEnglish languagesale 15% off
- Standard83 pagesEnglish languagesale 15% off
This document defines in an abstract way the externally visible service provided by the Directory. This document does not specify individual implementations or products.
- Standard120 pagesEnglish languagesale 15% off
- Draft120 pagesEnglish languagesale 15% off
This document defines a number of object classes and name forms which may be found useful across a range of applications of the Directory. The definition of an object class involves listing a number of attribute types which are relevant to objects of that class. The definition of a name form involves naming the object class to which it applies and listing the attributes to be used in forming names for objects of that class. These definitions are used by the administrative authority which is responsible for the management of the directory information. Any administrative authority can define its own object classes or subclasses and name forms for any purpose. NOTE 1 ? Those definitions may or may not use the notation specified in Rec. ITU-T X.501 | ISO/IEC 9594-2. NOTE 2 ? It is recommended that an object class defined in this Recommendation | International Standard, or a subclass derived from one, or a name form defined in this Recommendation | International Standard, be used in preference to the generation of a new one, whenever the semantics is appropriate for the application. Administrative authorities may support some or all the selected object classes and name forms, and may also add additional ones. All administrative authorities shall support the object classes which the directory uses for its own purpose (the top, alias and Directory system agent (DSA) object classes).
- Standard30 pagesEnglish languagesale 15% off
- Standard30 pagesEnglish languagesale 15% off
This document provides the directory capabilities required by many application layer standards and telecommunication services. Among the capabilities which it provides are those of "user-friendly naming", whereby objects can be referred to by names which are suitable for citing by human users (though not all objects need have user-friendly names); and "name-to-address mapping" which allows the binding between objects and their locations to be dynamic. The latter capability allows networks, for example, to be "self-configuring" in the sense that addition, removal and the changes of object location do not affect network operation. The Directory is not intended to be a general-purpose database system, although it may be built on such systems. It is assumed, for instance, that, as is typical with communication directories, there is a considerably higher frequency of "queries" than of updates. The rate of updates is expected to be governed by the dynamics of people and organizations, rather than, for example, the dynamics of networks. There is also no need for instantaneous global commitment of updates; transient conditions, where both old and new versions of the same information are available, are quite acceptable. It is a characteristic of the Directory that, except as a consequence of differing access rights or un-propagated updates, the results of directory queries will not be dependent on the identity or location of the inquirer. This characteristic renders the Directory unsuitable for some telecommunication applications, for example some types of routing. For cases where the results are dependent on the identity of the inquirer, access to directory information and updates of the Directory may be denied.
- Standard22 pagesEnglish languagesale 15% off
- Standard22 pagesEnglish languagesale 15% off
This document specifies a shadow service which Directory system agents (DSAs) may use to replicate Directory information. The service allows Directory information to be replicated among DSAs to improve service to Directory users. The shadowed information is updated, using the defined protocol, thereby improving the service provided to users of the Directory.
- Standard38 pagesEnglish languagesale 15% off
- Standard38 pagesEnglish languagesale 15% off
This document specifies the behaviour of DSAs taking part in a distributed directory consisting of multiple Directory systems agents (DSAs) and/or LDAP servers with at least one DSA. The allowed behaviour has been designed to ensure a consistent service given a wide distribution of the DIB across a distributed directory. Only the behaviour of DSAs taking part in a distributed directory is specified. The behaviour of LDAP servers are specified in relevant LDAP specifications. There are no special requirements on an LDAP server beyond those given by the LDAP specifications. The Directory is not intended to be a general purpose database system, although it may be built on such systems. It is assumed that there is a considerably higher frequency of queries than of updates.
- Standard125 pagesEnglish languagesale 15% off
- Draft125 pagesEnglish languagesale 15% off
This document provides a conceptual and terminological framework for the other ITU-T X.500-series Recommendations | parts of ISO/IEC 9594 which define various aspects of the Directory. The functional and administrative authority models define ways in which the Directory can be distributed, both functionally and administratively. Generic Directory System Agent (DSA) and DSA information models and an Operational Framework are also provided to support Directory distribution. The generic Directory Information Models describe the logical structure of the Directory Information Base (DIB) from the perspective of Directory and Administrative Users. In these models, the fact that the Directory is distributed, rather than centralized, is not visible. This Recommendation | International Standard provides a specialization of the generic Directory Information Models to support Directory Schema administration. The other ITU-T Recommendations in the X.500 series | parts of ISO/IEC 9594 make use of the concepts defined in this Recommendation | International Standard to define specializations of the generic information and DSA models to provide specific information, DSA and operational models supporting particular directory capabilities (e.g., Replication): a) the service provided by the Directory is described (in Rec. ITU-T X.511 | ISO/IEC 9594-3) in terms of the concepts of the information framework: this allows the service provided to be somewhat independent of the physical distribution of the DIB; b) the distributed operation of the Directory is specified (in Rec. ITU-T X.518 | ISO/IEC 9594-4) so as to provide that service, and therefore maintain that logical information structure, given that the DIB is in fact highly distributed; c) replication capabilities offered by the component parts of the Directory to improve overall Directory performance are specified (in Rec. ITU-T X.525 | ISO/IEC 9594-9). The security model establishes a framework for the specification of access control mechanisms. It provides a mechanism for identifying the access control scheme in effect in a particular portion of the Directory Information Tree (DIT), and it defines three flexible, specific access control schemes which are suitable for a wide variety of applications and styles of use. The security model also provides a framework for protecting the confidentiality and integrity of directory operations using mechanisms such as encryption and digital signatures. This makes use of the framework for authentication defined in Rec. ITU-T X.509 | ISO/IEC 9594-8 as well as generic upper layers security tools defined in Rec. ITU-T X.830 | ISO/IEC 11586-1. DSA models establish a framework for the specification of the operation of the components of the Directory. Specifically: a) the Directory functional model describes how the Directory is manifested as a set of one or more components, each being a DSA; b) the Directory distribution model describes the principals according to which the DIB entries and entry‑copies may be distributed among DSAs; c) the DSA information model describes the structure of the Directory user and operational information held in a DSA; d) the DSA operational framework describes the means by which the definition of specific forms of cooperation between DSAs to achieve particular objectives (e.g., shadowing) is structured.
- Standard238 pagesEnglish languagesale 15% off
- Standard238 pagesEnglish languagesale 15% off
IEC 62264-6:2020 defines a technology independent model for a set of abstract services that is located above the application layer of the OSI model, and that is used for exchanging transaction messages based on the transaction models defined in IEC 62264-5. The model, which is called the Messaging Service Model (MSM), is intended for interoperability between manufacturing operations domain applications and applications in other domains.
- Standard50 pagesEnglish languagesale 15% off
- Standard96 pagesEnglish and French languagesale 15% off
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 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 International Standard defines in an abstract way the externally visible behavior provided by the Type 10 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-10 and b) 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). 1.2 Specifications The principal objective of this document is to specify the syntax and behavior of the application layer protocol that conveys the application layer services defined in IEC 61158-5-10. A secondary objective is to provide migration paths from previously-existing industrial communications protocols. It is this latter objective which gives rise to the diversity of protocols standardized in IEC 61158-6. 1.3 Conformance This document does not specify individual implementations or products, nor does it constrain the implementations of application layer entities within industrial automation systems. Conformance is achieved through implementation of this application layer protocol specification.
- Standard899 pagesEnglish languagesale 10% offe-Library read for1 day
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 26 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 behavior provided by the Type 26 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-26, and b) define the externally visible behavior associated with their transfer. This document specifies the protocol of the Type 26 fieldbus Application Layer, in conformance with the OSI Basic Reference Model (see ISO/IEC 7498-1) and the OSI Application Layer Structure (see 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.
- Standard187 pagesEnglish languagesale 10% offe-Library read for1 day