{"id":245461,"date":"2024-10-19T16:08:38","date_gmt":"2024-10-19T16:08:38","guid":{"rendered":"https:\/\/pdfstandards.shop\/product\/uncategorized\/bs-en-iec-61158-6-252019\/"},"modified":"2024-10-25T11:08:49","modified_gmt":"2024-10-25T11:08:49","slug":"bs-en-iec-61158-6-252019","status":"publish","type":"product","link":"https:\/\/pdfstandards.shop\/product\/publishers\/bsi\/bs-en-iec-61158-6-252019\/","title":{"rendered":"BS EN IEC 61158-6-25:2019"},"content":{"rendered":"

1.1 General<\/b><\/p>\n

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 \u201cwindow between corresponding application programs.\u201d<\/p>\n

This International Standard provides common elements for basic time-critical and non-timecritical messaging communications between application programs in an automation environment and material specific to Type 25 fieldbus. The term \u201ctime-critical\u201d 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.<\/p>\n

This document defines in an abstract way the externally visible behavior provided by the different Types of the fieldbus Application Layer in terms of:<\/p>\n

    \n
  1. \n

    the abstract syntax defining the application layer protocol data units conveyed between communicating application entities,<\/p>\n<\/li>\n

  2. \n

    the transfer syntax defining the application layer protocol data units conveyed between communicating application entities,<\/p>\n<\/li>\n

  3. \n

    the application context state machine defining the application service behavior visible between communicating application entities; and<\/p>\n<\/li>\n

  4. \n

    the application relationship state machines defining the communication behavior visible between communicating application entities.<\/p>\n<\/li>\n<\/ol>\n

    The purpose of this document is to define the protocol provided to:<\/p>\n

      \n
    1. \n

      define the wire-representation of the service primitives defined in IEC 61158-5-25, and<\/p>\n<\/li>\n

    2. \n

      define the externally visible behavior associated with their transfer.<\/p>\n<\/li>\n<\/ol>\n

      This document specifies the protocol 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).<\/p>\n

      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.<\/p>\n

      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.<\/p>\n

      PDF Catalog<\/h4>\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
      PDF Pages<\/th>\nPDF Title<\/th>\n<\/tr>\n
      2<\/td>\nNational foreword <\/td>\n<\/tr>\n
      5<\/td>\nAnnex ZA(normative)Normative references to international publicationswith their corresponding European publications <\/td>\n<\/tr>\n
      7<\/td>\nCONTENTS <\/td>\n<\/tr>\n
      12<\/td>\nFOREWORD <\/td>\n<\/tr>\n
      14<\/td>\nINTRODUCTION <\/td>\n<\/tr>\n
      15<\/td>\n1 Scope
      1.1 General <\/td>\n<\/tr>\n
      16<\/td>\n1.2 Specification
      1.3 Conformance
      2 Normative references <\/td>\n<\/tr>\n
      17<\/td>\n3 Terms, definitions, symbols, abbreviations and conventions
      3.1 Reference model terms and definitions
      3.1.1 ISO\/IEC 7498-1 terms
      3.1.2 ISO\/IEC 8822 terms
      3.1.3 ISO\/IEC 9545 terms <\/td>\n<\/tr>\n
      18<\/td>\n3.1.4 ISO\/IEC 8824-1 terms
      3.2 Additional Type 25 terms and definitions <\/td>\n<\/tr>\n
      20<\/td>\n3.3 Symbols and abbreviations <\/td>\n<\/tr>\n
      21<\/td>\n3.4 Conventions
      3.4.1 General conventions
      3.4.2 Conventions for class definitions
      3.4.3 Conventions for bit description in octets
      Figures
      Figure 1 \u2013 Bit description in octets <\/td>\n<\/tr>\n
      22<\/td>\n3.4.4 Conventions for state machine descriptions
      Tables
      Table 1 \u2013 State transition descriptions
      Table 2 \u2013 Descriptions of state machine elements
      Table 3 \u2013 Conventions used in state machine <\/td>\n<\/tr>\n
      23<\/td>\n4 FAL syntax description
      4.1 FAL PDU type S abstract syntax
      4.1.1 Basic abstract syntax <\/td>\n<\/tr>\n
      27<\/td>\n4.2 FAL PDU type N abstract syntax
      4.2.1 Basic abstract syntax
      4.2.2 CyclicData-PDU <\/td>\n<\/tr>\n
      28<\/td>\n4.2.3 MulticastData-PDU
      4.2.4 PtoPData-PDU
      4.2.5 Aliveinfo-PDU
      4.2.6 Aliveinfo6-PDU <\/td>\n<\/tr>\n
      29<\/td>\n4.2.7 Inq-PDU
      4.2.8 Ninq-PDU
      4.2.9 Reply-PDU
      4.2.10 RetransEnq-PDU
      4.2.11 RetransConfirm-PDU <\/td>\n<\/tr>\n
      30<\/td>\n4.2.12 RetransNak-PDU
      4.3 Data type assignments for type S
      4.4 Data type assignments for type N <\/td>\n<\/tr>\n
      31<\/td>\n5 FAL transfer syntax
      5.1 Encoding rules
      5.1.1 Unsigned encoding <\/td>\n<\/tr>\n
      32<\/td>\n5.1.2 Octet string encoding
      5.1.3 SEQUENCE encoding
      5.2 FALPDU type S elements encoding
      5.2.1 RCL_header
      Table 4 \u2013 Frame Class
      Table 5 \u2013 DA_STaddress \u2013 DA_STaddress
      Table 6 \u2013 DA_MACaddress <\/td>\n<\/tr>\n
      33<\/td>\n5.2.2 RHE-PDU
      Table 7 \u2013 CMD field format
      Table 8 \u2013 Send Direction <\/td>\n<\/tr>\n
      34<\/td>\nTable 9 \u2013 RHE ReceiveStatus
      Table 10 \u2013 Physical Linkdown <\/td>\n<\/tr>\n
      35<\/td>\n5.2.3 LCC-PDU
      5.2.4 LCA-PDU
      Table 11 \u2013 RHE_pattern 1~4
      Table 12 \u2013 LCC-Kind <\/td>\n<\/tr>\n
      36<\/td>\n5.2.5 LCN-PDU
      Table 13 \u2013 RCL Status <\/td>\n<\/tr>\n
      37<\/td>\n5.2.6 LNA-PDU
      5.2.7 SCR-PDU
      5.2.8 Cyclic_S-PDU <\/td>\n<\/tr>\n
      38<\/td>\n5.2.9 Cyclic_header
      5.2.10 Control-PDU
      5.2.11 RMTCTL-PDU <\/td>\n<\/tr>\n
      39<\/td>\n5.2.12 INFO-PDU <\/td>\n<\/tr>\n
      40<\/td>\n5.3 FALPDU type N elements encoding
      5.3.1 General
      5.3.2 FALAR-N Header
      Figure 2 \u2013 hd_sa
      Table 14 \u2013 hd_h_type <\/td>\n<\/tr>\n
      41<\/td>\nFigure 3 \u2013 hd_da <\/td>\n<\/tr>\n
      42<\/td>\nTable 15 \u2013 Usage of Mgn or Lnn <\/td>\n<\/tr>\n
      44<\/td>\nTable 16 \u2013 Detailed conditions for sequence number check of reception message <\/td>\n<\/tr>\n
      45<\/td>\nFigure 4 \u2013 Valid sequence number for reception message
      Figure 5 \u2013 hd_m_ctl
      Table 17 \u2013 Valid bits of hd_m_ctl <\/td>\n<\/tr>\n
      46<\/td>\nTable 18 \u2013 Specified TCD <\/td>\n<\/tr>\n
      47<\/td>\nTable 19 \u2013 hd_pkind
      Table 20 \u2013 PDU with an effective hd_pseq <\/td>\n<\/tr>\n
      49<\/td>\nFigure 6 \u2013 Valid reception packet sequence number
      Table 21 \u2013 Detailed conditions for sequence number check of reception packet (Multicast communication with retransmission) <\/td>\n<\/tr>\n
      50<\/td>\nTable 22 \u2013 Detailed conditions for packet sequence number check <\/td>\n<\/tr>\n
      51<\/td>\nTable 23 \u2013 Relation between message transmission\/reception
      Table 24 \u2013 hd_mode
      Table 25 \u2013 Message priority level <\/td>\n<\/tr>\n
      52<\/td>\nTable 26 \u2013 Value of \u03b1
      Table 27 \u2013 Example of header information for a UDP message fragmentation
      Table 28 \u2013 Example of header information for a TCP message fragmentation <\/td>\n<\/tr>\n
      53<\/td>\nTable 29 \u2013 inqid_inq_sa value
      Table 30 \u2013 inqid_tr_adr value <\/td>\n<\/tr>\n
      54<\/td>\n5.3.3 CyclicData-PDU
      Table 31 \u2013 inqid_inq_seq value
      Table 32 \u2013 Relationship between inqid_id_seq and inqid_tr_adr <\/td>\n<\/tr>\n
      55<\/td>\n5.3.4 MulticastData-PDU
      5.3.5 PtoP Data-PDU
      5.3.6 Aliveinfo-PDU <\/td>\n<\/tr>\n
      56<\/td>\nTable 33 \u2013 Type of an alive-message
      Table 34 \u2013 Type of an alive-message protocol <\/td>\n<\/tr>\n
      57<\/td>\nTable 35 \u2013 Time of each al_mode
      Table 36 \u2013 Status change of tasks
      Table 37 \u2013 Change of tasks content <\/td>\n<\/tr>\n
      58<\/td>\n5.3.7 Aliveinfo6-PDU <\/td>\n<\/tr>\n
      59<\/td>\n5.3.8 Inq-PDU <\/td>\n<\/tr>\n
      60<\/td>\n5.3.9 Ninq-PDU
      5.3.10 Reply-PDU
      Figure 7 \u2013 Node-list <\/td>\n<\/tr>\n
      61<\/td>\n5.3.11 RetransEnq-PDU
      5.3.12 RetransConfirm-PDU <\/td>\n<\/tr>\n
      62<\/td>\n5.3.13 RetransNak-PDU <\/td>\n<\/tr>\n
      63<\/td>\n6 Structure of the FAL protocol state machine
      7 FAL service protocol machine (FSPM)
      7.1 Overview
      7.2 FSPM type S
      7.2.1 Overview
      Figure 8 \u2013 Relationships between protocol machines <\/td>\n<\/tr>\n
      64<\/td>\n7.2.2 Interface of cyclic communication to FAL users
      Figure 9 \u2013 Structure of FSPM type S <\/td>\n<\/tr>\n
      65<\/td>\nTable 38 \u2013 The threshold of transmission factor
      Table 39 \u2013 Example of the traffic control configuration menu <\/td>\n<\/tr>\n
      66<\/td>\n7.2.3 State machine of FSPM
      Figure 10 \u2013 Shared memory allocation in type S network
      Table 40 \u2013 Cyclic data state table <\/td>\n<\/tr>\n
      67<\/td>\n7.3 FSPM type N
      7.3.1 Overview
      Table 41 \u2013 Acyclic data state table <\/td>\n<\/tr>\n
      68<\/td>\n7.3.2 FSPM
      Figure 11 \u2013 Structure of FSPM type N <\/td>\n<\/tr>\n
      69<\/td>\nTable 42 \u2013 Cyclic data state table
      Table 43 \u2013 Acyclic data state table <\/td>\n<\/tr>\n
      70<\/td>\n8 Application relationship protocol machine (ARPM)
      8.1 ARPM type S
      8.1.1 Overview <\/td>\n<\/tr>\n
      71<\/td>\n8.1.2 Cyclic control
      Figure 12 \u2013 Structure of ARPM type S <\/td>\n<\/tr>\n
      72<\/td>\nFigure 13 \u2013 Sequence of cyclic communication
      Figure 14 \u2013 The primitives for cyclic control <\/td>\n<\/tr>\n
      73<\/td>\nTable 44 \u2013 Cyclic control state table <\/td>\n<\/tr>\n
      74<\/td>\nTable 45 \u2013 Cyclic control functions <\/td>\n<\/tr>\n
      75<\/td>\n8.1.3 Remote control
      Figure 15 \u2013 The primitives for Remote control
      Table 46 \u2013 Cyclic control variables <\/td>\n<\/tr>\n
      76<\/td>\nTable 47 \u2013 Remote control state table <\/td>\n<\/tr>\n
      79<\/td>\nTable 48 \u2013 Remote control functions <\/td>\n<\/tr>\n
      80<\/td>\n8.1.4 RCL communication control
      Figure 16 \u2013 The primitives for RCL communication control
      Table 49 \u2013 Remote control variables <\/td>\n<\/tr>\n
      81<\/td>\nTable 50 \u2013 RCL communication control state table <\/td>\n<\/tr>\n
      82<\/td>\nTable 51 \u2013 RCL communication control functions <\/td>\n<\/tr>\n
      84<\/td>\n8.1.5 RT communication control
      Table 52 \u2013 RCL communication control variables <\/td>\n<\/tr>\n
      85<\/td>\nFigure 17 \u2013 The primitives for RT communication control
      Table 53 \u2013 RT communication control state table <\/td>\n<\/tr>\n
      87<\/td>\nTable 54 \u2013 RT communication control functions
      Table 55 \u2013 RT communication control variables <\/td>\n<\/tr>\n
      88<\/td>\n8.2 ARPM type N
      8.2.1 Overview
      8.2.2 General control
      Figure 18 \u2013 Structure of ARPM type N <\/td>\n<\/tr>\n
      90<\/td>\n8.2.3 Cyclic transmission control
      Figure 19 \u2013 Primitives of Cyclic transmission control <\/td>\n<\/tr>\n
      91<\/td>\nTable 56 \u2013 Cyclic transmission control state table <\/td>\n<\/tr>\n
      93<\/td>\nTable 57 \u2013 Cyclic transmission control functions <\/td>\n<\/tr>\n
      95<\/td>\n8.2.4 Acyclic transmission control
      Table 58 \u2013 Cyclic transmission control variables <\/td>\n<\/tr>\n
      96<\/td>\nFigure 20 \u2013 Primitives of acyclic transmission control
      Table 59 \u2013 Acyclic transmission control state table <\/td>\n<\/tr>\n
      106<\/td>\nTable 60 \u2013 Acyclic transmission control functions <\/td>\n<\/tr>\n
      109<\/td>\nTable 61 \u2013 Acyclic transmission control variables <\/td>\n<\/tr>\n
      110<\/td>\n8.2.5 RT communication control
      Table 62 \u2013 RT communication control state table <\/td>\n<\/tr>\n
      121<\/td>\nTable 63 \u2013 RT communication control functions <\/td>\n<\/tr>\n
      125<\/td>\nTable 64 \u2013 RT communication control variables <\/td>\n<\/tr>\n
      126<\/td>\n9 DLL mapping protocol machine (DMPM)
      9.1 DMPM type S <\/td>\n<\/tr>\n
      127<\/td>\n9.2 DMPM type N
      9.2.1 General
      9.2.2 Communication port in transport layer
      9.2.3 Quality of Service
      Table 65 \u2013 ARPM to DL mapping
      Table 66 \u2013 Assignment policy of communication ports <\/td>\n<\/tr>\n
      128<\/td>\nFigure 21 \u2013 DSCP format
      Figure 22 \u2013 IEEE 802.1Q tag frame format
      Table 67 \u2013 Default DSCP, IEEE 802.1D and IEEE 802.1Q priority mapping <\/td>\n<\/tr>\n
      129<\/td>\nBibliography <\/td>\n<\/tr>\n<\/table>\n","protected":false},"excerpt":{"rendered":"

      Industrial communication networks. Fieldbus specifications – Application layer protocol specification. Type 25 elements<\/b><\/p>\n\n\n\n\n
      Published By<\/td>\nPublication Date<\/td>\nNumber of Pages<\/td>\n<\/tr>\n
      BSI<\/b><\/a><\/td>\n2019<\/td>\n130<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n","protected":false},"featured_media":245465,"template":"","meta":{"rank_math_lock_modified_date":false,"ep_exclude_from_search":false},"product_cat":[385,2641],"product_tag":[],"class_list":{"0":"post-245461","1":"product","2":"type-product","3":"status-publish","4":"has-post-thumbnail","6":"product_cat-25-040-40","7":"product_cat-bsi","9":"first","10":"instock","11":"sold-individually","12":"shipping-taxable","13":"purchasable","14":"product-type-simple"},"_links":{"self":[{"href":"https:\/\/pdfstandards.shop\/wp-json\/wp\/v2\/product\/245461","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/pdfstandards.shop\/wp-json\/wp\/v2\/product"}],"about":[{"href":"https:\/\/pdfstandards.shop\/wp-json\/wp\/v2\/types\/product"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/pdfstandards.shop\/wp-json\/wp\/v2\/media\/245465"}],"wp:attachment":[{"href":"https:\/\/pdfstandards.shop\/wp-json\/wp\/v2\/media?parent=245461"}],"wp:term":[{"taxonomy":"product_cat","embeddable":true,"href":"https:\/\/pdfstandards.shop\/wp-json\/wp\/v2\/product_cat?post=245461"},{"taxonomy":"product_tag","embeddable":true,"href":"https:\/\/pdfstandards.shop\/wp-json\/wp\/v2\/product_tag?post=245461"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}