Digital data communications for measurement and control - Fieldbus for use in industrial control systems - Part 5: Application Layer Service definition

Please note that this part is also available as part of a special CD-ROM containing IEC 61158-2 (with 2 amendments), IEC 61158-3, IEC 61158-4, IEC 61158-5 and IEC 61158-6 for a price of CHF 459,00

General Information

Status
Published
Publication Date
26-Jan-2000
Technical Committee
Current Stage
DELPUB - Deleted Publication
Start Date
27-May-2003
Completion Date
26-Oct-2025
Ref Project

Relations

Standard
IEC 61158-5:2000 - Digital data communications for measurement and control - Fieldbus for use in industrial control systems - Part 5: Application Layer Service definition Released:1/27/2000 Isbn:2831851394
English language
908 pages
sale 15% off
Preview
sale 15% off
Preview

Standards Content (Sample)


INTERNATIONAL
IEC
STANDARD
61158-5
Second edition
2000-01
Digital data communications for
measurement and control –
Fieldbus for use in industrial control systems –
Part 5:
Application Layer Service definition

Reference number
Numbering
As from 1 January 1997 all IEC publications are issued with a designation in the
60000 series.
Consolidated publications
Consolidated versions of some IEC publications including amendments are

available. For example, edition numbers 1.0, 1.1 and 1.2 refer, respectively, to the
base publication, the base publication incorporating amendment 1 and the base

publication incorporating amendments 1 and 2.

Validity of this publication
The technical content of IEC publications is kept under constant review by the IEC,
thus ensuring that the content reflects current technology.
Information relating to the date of the reconfirmation of the publication is available
in the IEC catalogue.
Information on the subjects under consideration and work in progress undertaken by
the technical committee which has prepared this publication, as well as the list of
publications issued, is to be found at the following IEC sources:
• IEC web site*
• Catalogue of IEC publications
Published yearly with regular updates
(On-line catalogue)*
• IEC Bulletin
Available both at the IEC web site* and as a printed periodical
Terminology, graphical and letter symbols
For general terminology, readers are referred to IEC 60050: International
Electrotechnical Vocabulary (IEV).
For graphical symbols, and letter symbols and signs approved by the IEC for
general use, readers are referred to publications IEC 60027: Letter symbols to be
used in electrical technology, IEC 60417: Graphical symbols for use on equipment.
Index, survey and compilation of the single sheets and IEC 60617: Graphical symbols
for diagrams.
* See web site address on title page.

INTERNATIONAL IEC
STANDARD 61158-5
Second edition
2000-01
Digital data communications for
measurement and control –
Fieldbus for use in industrial control systems –
Part 5:
Application Layer Service definition

© IEC 2000 – Copyright – all rights reserved
No part of this publication may be reproduced or utilized in any form or by any means, electronic or
mechanical, including photocopying and microfilm, without permission in writing from the publisher.
International Electrotechnical Commission 3, rue de Varembé Geneva, Switzerland
Telefax: +41 22 919 0300 e-mail: inmail@iec.ch IEC web site http: //www.iec.ch
Commission Electrotechnique Internationale
PRICE CODE
XH
International Electrotechnical Commission

For price, see current catalogue

– 2 – 61158-5 © IEC:2000(E)
CONTENTS
Page
FOREWORD .9

INTRODUCTION .11

Clause
1 SCOPE.11

2 NORMATIVE REFERENCES .12
3 DEFINITIONS.13
3.1 ISO/IEC 7498-1 terms .13
3.2 ISO/IEC 8822 terms.13
3.3 ISO/IEC 9545 terms.13
3.4 ISO/IEC 8824 terms.13
3.5 Fieldbus Data Link Layer terms .13
3.6 FAL Specific Definitions.14
3.6.1 Access Protection Definition.14
3.6.2 Address Assignment Table Definition .14
3.6.3 Allocate Definition.14
3.6.4 Application Layer Interoperability Definition .14
3.6.5 Application Object Definition .14
3.6.6 Application Process Definition.14
3.6.7 Application Process Identifier Definition.14
3.6.8 Application Process Object Class Definition .15
3.6.9 Application Relationship Definition .15
3.6.10 Application Relationship Application Service Element Definition.15
3.6.11 Application Relationship Endpoint Definition.15
3.6.12 Application Definition.15
3.6.13 Application Objects Definition .15
3.6.14 Attribute Definition.15
3.6.15 Behaviour Definition.15
3.6.16 Bit-no Definition.15
3.6.17 Channel Definition.15
3.6.18 Channel Related Diagnosis Definition.15
3.6.19 Class Definition .15
3.6.20 Class Attributes Definition.16
3.6.21 Class Code Definition.16
3.6.22 Class Specific Service Definition .16
3.6.23 Client Definition.16

3.6.24 Communication Objects Definition.16
3.6.25 Connection Definition.16
3.6.26 Connection ID (CID) Definition.16
3.6.27 Connection Path Definition.16
3.6.28 Connection Point Definition.16
3.6.29 Consume Definition.16
3.6.30 Consumer Definition .16
3.6.31 Consuming Application Definition .16
3.6.32 Configuration Check Definition .17
3.6.33 Configuration Fault Definition.17
3.6.34 Configuration Identifier Definition.17
3.6.35 Control Commands Definition.17
3.6.36 Conveyance Path Definition.17
3.6.37 Cyclic Definition.17
3.6.38 Data Consistency Definition.17

61158-5 © IEC:2000(E) – 3 –
3.6.39 Dedicated AR Definition.17
3.6.40 Default DL-Address Definition.17

3.6.41 Device Definition .17

3.6.42 Device Profile Definition.17

3.6.43 Diagnosis Information Definition .17

3.6.44 Diagnosis Information Collection Definition .17

3.6.45 DP-Master (Class 1) Definition .18

3.6.46 DP-Master (Class 2) Definition .18

3.6.47 DP-Slave Definition.18

3.6.48 Dynamic AR Definition .18
3.6.49 End Node Definition .18
3.6.50 Endpoint Definition.18

3.6.51 Error Definition.18

3.6.52 Error Class Definition.18

3.6.53 Error Code Definition .18
3.6.54 FAL Subnet Definition .18
3.6.55 First-In-First-Out Variable Definition .18
3.6.56 Frame Definition.18
3.6.57 Freeze Definition.18
3.6.58 Group Definition.19
3.6.59 Invocation Definition.19
3.6.60 I/O Data Definition.19
3.6.61 Ident Number Definition .19
3.6.62 Identifier Related Diagnosis Definition.19
3.6.63 Index Definition .19
3.6.64 Instance Definition .19
3.6.65 Instance Attributes Definition .19
3.6.66 Instantiated Definition .19
3.6.67 Lpacket Definition .19
3.6.68 Management Information Definition.19
3.6.69 Manufacturer ID Definition .19
3.6.70 Master Parameter Set Definition.20
3.6.71 Member Definition.20
3.6.72 Message Router Definition.20
3.6.73 Multicast Connection Definition.20
3.6.74 Module Definition .20
3.6.75 Network Definition.20
3.6.76 Object Definition.20
3.6.77 Object Specific Service Definition.20
3.6.78 Originator Definition .20
3.6.79 Peer Definition .20
3.6.80 Point-to-point Connection Definition .20
3.6.81 Pre-defined AR Endpoint Definition .21
3.6.82 Pre-established AR Endpoint Definition.21
3.6.83 Process Data Definition .21
3.6.84 Produce Definition.21

3.6.85 Producer Definition .21
3.6.86 Publisher Definition .21
3.6.87 Publishing Manager Definition .21
3.6.88 Pull Publisher Definition .21
3.6.89 Pull Publishing Manager Definition .21
3.6.90 Push Publisher Definition.21
3.6.91 Push Publishing Manager Definition .21
3.6.92 Pull Subscriber Definition.22
3.6.93 Push Subscriber Definition.22
3.6.94 Real Configuration Definition .22
3.6.95 Resource Definition.22
3.6.96 Route Endpoint .22
3.6.97 Serial Number Definition.22
3.6.98 Server Definition .22
3.6.99 Server Definition .22

– 4 – 61158-5 © IEC:2000(E)
3.6.100 Service Definition .22
3.6.101 Slot Definition.22

3.6.102 Subscriber Definition.22

3.6.103 Sync Definition .22

3.6.104 Target Definition.23

3.6.105 Unconnected Message Manager (UCMM) Definition .23

3.6.106 Unconnected Service Definition.23

3.7 Abbreviations and Symbols .23

3.8 Conventions.24

3.8.1 General Conventions.24

3.8.2 Conventions for Class Definitions .25
3.8.3 Conventions for Service Definitions .26

4 CONCEPTS28
4.1 Architectural relationships.28
4.1.1 Overview .28
4.1.2 Relationship to the Application Layer of the OSI Reference Model .28
4.1.3 Relationships to other fieldbus standards .29
4.2 Fieldbus Application Layer structure.30
4.2.1 Overview .30
4.2.2 Fundamental concepts.30
4.2.3 Fieldbus Application processes.31
4.2.4 Application objects .34
4.2.5 Application entities .36
4.2.6 Fieldbus Application Service Elements .37
4.2.7 Application relationships.40
4.3 Fieldbus Application Layer Naming and Addressing .43
4.3.1 Identifying Objects accessed through the FAL.43
4.3.2 Addressing APs accessed through the FAL.44
4.4 Architecture Summary .44
4.5 FAL Service Procedures and Time Sequence Diagrams .45
4.5.1 FAL Confirmed Service Procedures.45
4.5.2 Confirmed Service Time Sequence Diagram.46
4.5.3 FAL Unconfirmed Service Procedures.47
4.5.4 Unconfirmed Service Time Sequence Diagram.47
4.6 Common FAL attributes.47
4.7 Common FAL Service Parameters.48
4.8 APDU size.50
5 DATA TYPE ASE.51
5.1 Overview.51
5.1.1 Overview Of Basic Types .52
5.1.2 Overview of Constructed Types .52
5.1.3 Specification of User Defined Data Types .53
5.1.4 Transfer of User Data.53
5.2 Formal Definition of Data Type Objects.53

5.2.1 Data Type Class.53
5.3 FAL Defined Data Types.55
5.3.1 Fixed Length Types.55
5.3.2 String Types .69
5.3.3 Structure Types .71
5.4 Data type ASE Service Specification .73
5.5 Summary of data types.73
6 TYPES OF COMMUNICATION MODELS .74
7 COMMUNICATION MODEL TYPE 1 SPECIFICATION .74
7.1 Type 1 Concepts.74
7.2 Type 1 ASEs .74
7.2.1 Object Management ASE.74
7.2.2 Application Process ASE.84

61158-5 © IEC:2000(E) – 5 –
7.2.3 Application Relationship ASE.108
7.2.4 Variable ASE.133

7.2.5 Event ASE.163

7.2.6 Load Region ASE.192

7.2.7 Function Invocation ASE.214

7.3 Type 1 ARs .232

7.3.1 Queued User-triggered Uni-directional (QUU) AR Endpoint Formal Model.232

7.3.2 Queued User-triggered Bi-directional Connection-Oriented (QUB-Co) AR Endpoint

Formal Model .233

7.3.3 Queued User-triggered Bi-directional Connectionless (QUB-CL) AR Endpoint Formal
Model.235
7.3.4 Queued User-triggered Bi-directional with Flow Control (QUB-FC) AR Endpoint Formal

Model.238

7.3.5 Queued User-Triggered Bi-directional with Segmentation(QUB-Seg) AR Endpoint

Formal Model .241
7.3.6 Buffered User-triggered Bi-directional (BUB) AR Endpoint Formal Model.244
7.3.7 Buffered Network-Scheduled Uni-directional (BNU) AR Endpoint Formal Model.247
7.3.8 Buffered Network-scheduled Bi-directional (BNB) AR Endpoint Formal Model.251
7.3.9 Buffered Network-Scheduled And Unscheduled Uni-directional (BNU-Mp) AR Endpoint
Formal Model .254
7.4 Description.254
L.1 Formal Class Definition .257
7.5 Summary of Type 1 FAL Classes.259
7.6 Permitted FAL Type 1 Services by AREP Role .260
8 COMMUNICATION MODEL TYPE 2 SPECIFICATION .262
8.1 Type 2 Concepts.262
8.1.1 General .262
8.1.2 General concepts .262
8.1.3 Relationships between ASE's .263
8.1.4 Naming and Addressing.264
8.1.5 Type 2 Data Types.264
8.2 Type 2 ASEs.269
8.2.1 Type 2 Object Management ASE.269
8.2.2 Connection Manager ASE.317
8.3 Type 2 AR's .328
8.3.1 Overview .328
8.3.2 UCMM AR Formal Model.338
8.3.3 Transport AR Formal Model.340
8.3.4 AR ASE Services .357
8.4 Summary of FAL Type 2 Classes.365
8.5 Permitted FAL Type 2 Services by AR Type .366
9 COMMUNICATION MODEL TYPE 3 SPECIFICATION .367
9.1 Type 3 Concepts.367
9.1.1 User Requirements of the Type 3 DP System .367

9.1.2 Features of Type 3 DP .367
9.1.3 DP Communication Model .368
9.1.4 Dynamical Behaviour of Type 3 DP .379
9.1.5 Type 3 Status Values .380
9.2 Type 3 ASEs.381
9.2.1 Process Data ASE .381
9.2.2 I/O Data ASE.392
9.2.3 Diagnosis ASE .412
9.2.4 Alarm ASE.432
9.2.5 Context ASE.439
9.2.6 Management ASE .472
9.2.7 AR ASE .493
9.3 Type 3 ARs .498
9.3.1 MS0 Application Relationship.498
9.3.2 MS1 Application Relationship.501

– 6 – 61158-5 © IEC:2000(E)
9.3.3 MS2 Application Relationship.502
9.3.4 MM1 Application Relationship .506

9.3.5 MM2 Application Relationship .507

9.4 Summary of Type 3 FAL Classes .598

9.5 Permitted FAL Type 3 Services by AREP Role .599

9.6 Conformance Classes .601

9.7 Application Characteristics .602

9.7.1 Time Behaviour .602

9.7.2 Ident Number.603

10 COMMUNICATION MODEL TYPE 4 SPECIFICATION .603
10.1 Type 4 Concepts .603
10.1.1 Overview .603

10.1.2 Application Entities.603

10.1.3 Gateway and Routing.605
10.1.4 Architecture Summary .606
FAL Service Procedures and Time Sequence Diagrams.607
10.2 Type 4 Variable ASE .609
10.2.1 Overview .609
10.2.2 Variable Model Class Specification.611
10.2.3 Basic Variable Type Specifications.612
10.2.4 Constructed Variable Type Specifications .617
10.2.5 Services .621
10.3 Type 4 Route Endpoint ASE.621
10.3.1 Overview .621
10.3.2 Route Endpoint Model.622
10.3.3 Route Endpoint ASE Service Specification.624
10.4 Type 4 Application Relationship ASE .629
10.4.1 Overview .629
10.4.2 Application Relationship Class Specification .630
10.4.3 Application Relationship ASE Service Specifications .632
11 COMMUNICATION MODEL TYPE 5 SPECIFICATION .636
11.1 Type 5 Concepts .636
11.1.1 Objectives of the Type 5 FAL AE.636
11.1.2 Type 5 Devices .636
11.1.3 Data Type ASE .637
11.1.4 APO ASEs.637
11.1.5 Application Relationships .639
11.1.6 Support for Configuration Management.640
11.2 Type 5 ASEs.640
11.2.1 Simple Virtual Field Device ASE.640
11.2.2 System Management Kernel ASE.647
11.2.3 LAN Redundancy ASE.664
11.3 Type 5 ARs.668
11.3.1 Publisher/Subscriber Type 5 AR Endpoint Formal Model.668

11.3.2 Client / Server AR Endpoint Formal Model .669
11.4 Summary of FAL Type 1 and Type 5 Classes.671
11.5 Permitted FAL Type 1 and Type 5 Services by AREP Role.672
12 COMMUNICATION MODEL TYPE 6 SPECIFICATION .673
13 COMMUNICATION MODEL TYPE 7 SPECIFICATION .673
13.1 Type 7 Concepts .673
13.1.1 AL Type 7 environment.673
13.1.2 Application services .673
13.1.3 Application process.674
13.1.4 Application entity .675
13.1.5 AE model.676
13.1.6 AEI model.677
13.1.7 Application context.679

61158-5 © IEC:2000(E) – 7 –
13.1.8 Coordination of the AEIs .683
13.1.9 Concepts for Sub_MMS.687

13.2 Type 7 ASEs.689

13.2.1 MPS ASE (Periodic/Aeriodic Manufacturing Services).689

13.2.2 Virtual Model of a Device (VMD) ASE .783

13.2.3 Domain ASE .803

13.2.4 Program Invocation (PI) ASE.820

13.2.5 Variable ASE.833

13.2.6 Event ASE.851

13.2.7 Directory ASE.864
13.3 Type 7 ARs.864
13.3.1 Messaging Common Service (MCS) AR ASE .864

14 COMMUNICATION MODEL TYPE 8 SPECIFICATION .885

14.1 Type 8 Concepts .885
14.1.1 Overview .885
14.1.2 Mapping of functional capabilities .885
14.1.3 Fundamental concept restrictions.885
14.1.4 Common FAL Attributes .887
14.2 Type 8 ASEs.887
14.2.1 Overview .887
14.2.2 Object Management ASE .887
14.2.3 Application Process ASE .888
14.2.4 Application Relationship ASE.
...

Questions, Comments and Discussion

Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.

Loading comments...