Real-time Ethernet - Real-time Automation Protocol for Industrial Ethernet (RAPIEnet)

IEC/PAS 62573:2008 specifies the protocol set necessary for RAPIEnet, specifically for the data link layer and the application layer, which is mapped on top of the data link layer, to exploit the services in accordance with the three-layer fieldbus reference model, which is based in part on the OSI Basic Reference Model. Both reference models subdivide the area of standardization for interconnection into a series of layers of manageable size.

General Information

Status
Replaced
Publication Date
11-Mar-2008
Technical Committee
SC 65C - Industrial networks
Drafting Committee
WG 9 - TC 65/SC 65C/WG 9
Current Stage
DELPUB - Deleted Publication
Start Date
05-Aug-2010
Completion Date
14-Feb-2026

Relations

Effective Date
05-Sep-2023
Effective Date
05-Sep-2023
Effective Date
05-Sep-2023
Effective Date
05-Sep-2023

Buy Documents

Technical specification

IEC PAS 62573:2008 - Real-time Ethernet - Real-time Automation Protocol for Industrial Ethernet (RAPIEnet) Released:3/12/2008 Isbn:2831896509

English language (244 pages)
sale 15% off
Preview
sale 15% off
Preview

Get Certified

Connect with accredited certification bodies for this standard

National Aerospace and Defense Contractors Accreditation Program (NADCAP)

Global cooperative program for special process quality in aerospace.

ANAB United States Verified

TL 9000 QuEST Forum

Telecommunications quality management system.

ANAB United States Verified

ANCE

Mexican certification and testing association.

EMA Mexico Verified

Sponsored listings

Frequently Asked Questions

IEC PAS 62573:2008 is a technical specification published by the International Electrotechnical Commission (IEC). Its full title is "Real-time Ethernet - Real-time Automation Protocol for Industrial Ethernet (RAPIEnet)". This standard covers: IEC/PAS 62573:2008 specifies the protocol set necessary for RAPIEnet, specifically for the data link layer and the application layer, which is mapped on top of the data link layer, to exploit the services in accordance with the three-layer fieldbus reference model, which is based in part on the OSI Basic Reference Model. Both reference models subdivide the area of standardization for interconnection into a series of layers of manageable size.

IEC/PAS 62573:2008 specifies the protocol set necessary for RAPIEnet, specifically for the data link layer and the application layer, which is mapped on top of the data link layer, to exploit the services in accordance with the three-layer fieldbus reference model, which is based in part on the OSI Basic Reference Model. Both reference models subdivide the area of standardization for interconnection into a series of layers of manageable size.

IEC PAS 62573:2008 is classified under the following ICS (International Classification for Standards) categories: 25.040.40 - Industrial process measurement and control; 33.040.40 - Data communication networks. The ICS classification helps identify the subject area and facilitates finding related standards.

IEC PAS 62573:2008 has the following relationships with other standards: It is inter standard links to IEC 61158-6-21:2010, IEC 61158-4-21:2010, IEC 61158-5-21:2010, IEC 61158-3-21:2010. Understanding these relationships helps ensure you are using the most current and applicable version of the standard.

IEC PAS 62573:2008 is available in PDF format for immediate download after purchase. The document can be added to your cart and obtained through the secure checkout process. Digital delivery ensures instant access to the complete standard document.

Standards Content (Sample)


IEC/PAS 62573
Edition 1.0 2008-03
PUBLICLY AVAILABLE
SPECIFICATION
PRE-STANDARD
Real-time Ethernet – Real-time Automation Protocol for Industrial Ethernet
(RAPIEnet)
IEC/PAS 62573:2008(E)
All rights reserved. Unless otherwise specified, 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
either IEC or IEC's member National Committee in the country of the requester.
If you have any questions about IEC copyright or have an enquiry about obtaining additional rights to this publication,

please contact the address below or your local IEC member National Committee for further information.

IEC Central Office
3, rue de Varembé
CH-1211 Geneva 20
Switzerland
Email: inmail@iec.ch
Web: www.iec.ch
About the IEC
The International Electrotechnical Commission (IEC) is the leading global organization that prepares and publishes
International Standards for all electrical, electronic and related technologies.

About IEC publications
The technical content of IEC publications is kept under constant review by the IEC. Please make sure that you have the
latest edition, a corrigenda or an amendment might have been published.
ƒ Catalogue of IEC publications: www.iec.ch/searchpub
The IEC on-line Catalogue enables you to search by a variety of criteria (reference number, text, technical committee,…).
It also gives information on projects, withdrawn and replaced publications.
ƒ IEC Just Published: www.iec.ch/online_news/justpub
Stay up to date on all new IEC publications. Just Published details twice a month all new publications released. Available
on-line and also by email.
ƒ Electropedia: www.electropedia.org
The world's leading online dictionary of electronic and electrical terms containing more than 20 000 terms and definitions
in English and French, with equivalent terms in additional languages. Also known as the International Electrotechnical
Vocabulary online.
ƒ Customer Service Centre: www.iec.ch/webstore/custserv
If you wish to give us your feedback on this publication or need further assistance, please visit the Customer Service
Centre FAQ or contact us:
Email: csc@iec.ch
Tel.: +41 22 919 02 11
Fax: +41 22 919 03 00
IEC/PAS 62573
Edition 1.0 2008-03
PUBLICLY AVAILABLE
SPECIFICATION
PRE-STANDARD
Real-time Ethernet – Real-time Automation Protocol for Industrial Ethernet
(RAPIEnet)
INTERNATIONAL
ELECTROTECHNICAL
COMMISSION
PRICE CODE
XH
ICS 25.040.40 33.040.40 ISBN 2-8318-9650-9

– 2 – PAS 62573 © IEC:2008(E)
CONTENTS
FOREWORD.12

INTRODUCTION.13

1 Scope.14

2 Normative references .14

3 Terms, definitions, and abbreviations .15

3.1 IEC 61158 definitions .15
3.2 Definitions from other standards.19
3.3 RAPIEnet terms and definitions .19
3.4 Symbols and abbreviations.19
4 Technology overview.19
4.1 General Information.19
4.2 Operating principles .20
4.2.1 Frame forwarding and receiving control .20
4.2.2 Link status monitoring.21
4.2.3 Error detection.22
4.3 Topology .22
4.4 Device reference model.23
4.4.1 Physical layer .24
4.4.2 Data link layer (DLL).24
4.4.3 Application layer.24
4.5 Data link layer overview .24
4.5.1 Extremely fast network recovery (EFR).24
4.5.2 Plug and play (PnP).25
4.5.3 Network management information base (NMIB) management .25
4.5.4 Automatic network configuration (ANC) .25
4.6 Application layer overview .25
5 Physical layer.26
5.1 Overview .26
5.2 100BASE-TX .27
5.3 100BASE-FX .27

5.4 1000BASE-T .27
5.5 1000BASE-X .27
6 Data link layer service definitions .27
6.1 Introduction .27
6.2 Scope.27
6.2.1 Overview .27
6.2.2 Specifications .28
6.2.3 Conformance.28
6.3 Normative references .28
6.4 Terms, definitions, symbols, abbreviations, and conventions .29
6.4.1 Reference model terms and definitions .29
6.4.2 Service convention terms and definitions.30
6.4.3 Data link service terms and definitions.31
6.4.4 Symbols and abbreviations.34

PAS 62573 © IEC:2008(E) – 3 –
6.4.5 Conventions .35

6.5 Data link service and concept.36

6.5.1 Overview .36

6.5.2 Detailed description of the data service .40

6.5.3 Detailed description of the sporadic data service .42

6.5.4 Detailed description of network control message service .43

6.6 Data link management services .45

6.6.1 General .45

6.6.2 Data link management service (DLMS) facilities .46

6.6.3 Data link management service (DLMS) .46

6.6.4 Overview of interactions .47
6.6.5 Detailed specification of service and interactions.48
6.7 MAC control service .56
6.7.1 General .56
6.7.2 MAC control service .56
6.7.3 Overview of interactions .57
6.7.4 Detailed specification of service and interactions.57
6.8 Ph-control service .59
6.8.1 General .59
6.8.2 Ph-control service.59
6.8.3 Overview of interactions .59
6.8.4 Detailed specification of service and interactions.60
7 Data link layer protocol specification .62
7.1 Introduction .62
7.2 Scope.63
7.2.1 General .63
7.2.2 Specifications .63
7.2.3 Procedures.63
7.2.4 Applicability .63
7.2.5 Conformance.63
7.3 Overview of the data link protocol.63
7.3.1 General .63
7.3.2 Overview of medium access control.64
7.3.3 Service assumed from the physical layer .64
7.3.4 DLL architecture .64

7.3.5 Data type.66
7.3.6 Local parameters and variables .68
7.4 General structure and encoding.83
7.4.1 Overview .83
7.4.2 MAPDU structure and encoding.83
7.4.3 Common MAC frame structure, encoding and elements of procedure .83
7.4.4 Order of bit transmission .93
7.4.5 Invalid DLPDU.94
7.5 DLPDU structure and procedure.94
7.5.1 General .94
7.5.2 Common DLPDU field.94
7.5.3 DL-DATA transfer .95
7.5.4 DL-SPDATA transfer .97
7.5.5 Network control messages.99

– 4 – PAS 62573 © IEC:2008(E)
7.6 DLE elements of procedure .104

7.6.1 Overall structure.104

7.6.2 DL-protocol machine (DLPM).105

7.6.3 DLL management protocol.112

7.7 Constants.135

7.7.1 General .135

7.7.2 Constants .135

7.7.3 Data link layer error codes.136

8 Application layer service definition.137

8.1 Introduction .137
8.2 Scope.137
8.2.1 Overview .137
8.2.2 Specifications .138
8.2.3 Conformance.139
8.3 Normative references .139
8.4 Terms, definitions, symbols, abbreviations, and conventions . 139
8.4.1 ISO/IEC 7498-1 terms .139
8.4.2 ISO/IEC 8822 terms.139
8.4.3 ISO/IEC 9545 terms.139
8.4.4 Fieldbus data link layer terms .140
8.4.5 Fieldbus application layer specific definitions . 140
8.4.6 Abbreviations and symbols .145
8.4.7 Conventions .146
8.5 Concepts.148
8.5.1 Common concepts .148
8.5.2 Type specific concepts .165
8.6 Data type ASE.168
8.6.1 General .168
8.6.2 Formal definition of data type objects .171
8.6.3 FAL defined data types.173
8.6.4 Data type ASE service specification .176
8.7 Communication model specification.176
8.7.1 ASEs .176
8.7.2 ARs .196
8.7.3 Summary of FAL classes .200

8.7.4 Permitted FAL services by AREP role.200
9 Application layer protocol specification .201
9.1 Introduction .201
9.2 Scope.201
9.2.1 General .201
9.2.2 Overview .201
9.2.3 Specifications .202
9.2.4 Conformance.202
9.3 Normative references .202
9.4 Terms, definitions, symbols, abbreviations, and conventions . 202
9.4.1 ISO/IEC 8824 terms.202
9.4.2 ISO/IEC 10731 terms.203
9.4.3 Other terms and definitions.203
9.5 Conventions .204

PAS 62573 © IEC:2008(E) – 5 –
9.5.1 General conventions.204

9.5.2 Convention for the encoding of reserved bits and octets . 204

9.5.3 Conventions for the common coding of specific field octets . 204

9.5.4 Conventions for APDU abstract syntax definitions .205

9.5.5 Conventions for APDU transfer syntax definitions .205

9.5.6 Conventions for AE state machine definitions . 205

9.6 FAL syntax description .206

9.6.1 General .206

9.6.2 FAL-AR PDU abstract syntax.206

9.6.3 Abstract syntax of PDU body .207

9.6.4 Protocol data units (PDUs) for application service elements (ASEs) . 208
9.7 Transfer syntax .212
9.7.1 Overview of encoding .212
9.7.2 APDU header encoding .212
9.7.3 APDU body encoding.213
9.7.4 Encoding of Data types.213
9.8 FAL protocol state machines .218
9.9 AP context state machine .219
9.10 FAL service protocol machine.219
9.10.1 General .219
9.10.2 Common parameters of the primitives. 219
9.10.3 AP ASE protocol machine.219
9.10.4 Service data object ASE protocol machine (SDOM) . 223
9.10.5 Process data object ASE protocol machine (PDOM) . 226
9.11 AR protocol machine .227
9.11.1 General .227
9.11.2 Point-to-point user-triggered confirmed client/server AREP (PTC-AR)
ARPM.228
9.11.3 Multipoint network-scheduled unconfirmed publisher/subscriber
AREP (MSU-AR) ARPM.230
9.11.4 Multipoint user-triggered unconfirmed publisher/subscriber AREP
(MTU-AR) ARPM .232
9.12 DLL mapping protocol machine .235
9.12.1 Primitive definitions .235
9.12.2 DMPM state machine.236
Annex A Data link layer technical description.237

A.1 DL-address collision .237
A.1.1 General .237
A.1.2 Detecting DL-address collision .237
A.1.3 Clearing DL-address collision .239
A.2 Automatic Ring Network Manager (RNM) election procedure.240
A.2.1 General .240
A.2.2 Primary RNM (RNMP) .241
A.2.3 Secondary RNM (RNMS).241
A.3 Path management .241
A.3.1 General .241
A.3.2 Path of line topology network .241
A.3.3 Path of ring topology network .242
A.4 Extremely fast network recovery.243

– 6 – PAS 62573 © IEC:2008(E)
A.4.1 Link fault with neighbouring device.243

A.4.2 Link fault of remote device .244

Figure 1 – Forwarding and receiving Ethernet frames .20

Figure 2 – Forward control of LNM.21

Figure 3 – Forward control of RNM .21

Figure 4 – Link status information .22

Figure 5 – Line topology .23

Figure 6 – Ring topology.23

Figure 7 – OSI basic reference model .24
Figure 8 – Interaction between FAL and DLL .25
Figure 9 – Publisher-subscriber communication model.26
Figure 10 – Client-server communication model.26
Figure 11 – Relationships of DLSAPs, DLSAP-addresses, and group DL-addresses .32
Figure 12 – Full-duplex flow control .37
Figure 13 – Sequence diagram of DL-DATA service.38
Figure 14 – Sequence diagram of DL-SPDATA service .38
Figure 15 – Sequence diagram of NCM service primitive .39
Figure 16 – DL-DATA service .40
Figure 17 – Sequence diagram of Reset, Set-value, Get-value, SAP-allocation, SAP-
deallocation, Get-SAP information and Get-diagnostic information service primitives.48
Figure 18 – Sequence diagram of Event service primitive .48
Figure 19 – Sequence diagram of MAC-reset and MAC-forward-control service
primitive.57
Figure 20 – Sequence diagram of Ph-reset and Ph-get-link-status service primitive.60
Figure 21 – Sequence diagram of Ph-link-status-change service primitive .60
Figure 22 – Interaction of PhS primitives with DLE.64
Figure 23 – Data link layer architecture.65
Figure 24 – Common MAC frame format for RAPIEnet DLPDU .83
Figure 25 – MAC frame format for other protocols.84
Figure 26 – Version and Length field .85
Figure 27 – DST_addr field .86

Figure 28 – SRC_addr field.87
Figure 29 – Frame Control Field .87
Figure 30 – Extension field .89
Figure 31 – DSAP field .89
Figure 32 – Source service access point field .90
Figure 33 – Length of group mask and extension information.90
Figure 34 – Group mask option field .91
Figure 35 – Common DLPDU field .94
Figure 36 – Building a DT DLPDU.95
Figure 37 – DT DLPDU structure .95
Figure 38 – SPDT DLPDU structure .98
Figure 39 – NCM_LA DLPDU structure .99

PAS 62573 © IEC:2008(E) – 7 –
Figure 40 – DLL structure and elements .105

Figure 41 – State transition diagram of the DLPM . 108

Figure 42 – State transition diagram of DLM . 116

Figure 43 – Relationship to the OSI Basic Reference Model .149

Figure 44 – Architectural positioning of the fieldbus application layer.150

Figure 45 – Client/server interactions.152

Figure 46 – Pull model interactions .153

Figure 47 – Push model interactions .154

Figure 48 – APOs services conveyed by the FAL .155
Figure 49 – Application entity structure .157
Figure 50 – FAL management of objects .158
Figure 51 – ASE service conveyance.159
Figure 52 – Defined and established AREPs.161
Figure 53 – FAL architectural components .163
Figure 54 – Interaction between FAL and DLL .166
Figure 56 – Client-server communication model.167
Figure 57 – Object model.167
Figure 58 – ASEs of a RAPIEnet application.168
Figure 59 – Data type class hierarchy example .169
Figure 60 – The AR ASE conveys APDUs between APs.190
Figure 61 – Common structure of specific fields. 204
Figure 62 – APDU overview .212
Figure 63 – Type field .213
Figure 64 – Encoding of time-of-day value .217
Figure 65 – Encoding of time difference value.217
Figure 66 – Primitives exchanged between protocol machines . 218
Figure 67 – State transition diagram of APAM. 221
Figure 68 – State transition diagram of SDOM . 224
Figure 69 – State transition diagram of PDOM . 226
Figure 70 – State transition diagram of PTC-ARPM .229
Figure 71 – State transition diagram of MSU-ARPM.231

Figure 72 – State transition diagram of MTU-ARPM .234
Figure 11 – State transition diagram of DMPM .236
Figure A.1 – RAPIEnet DL-address collision in a ring network.237
Figure A.2 – RAPIEnet DL-address collision in a line network.238
Figure A.3 – DL-address collision detection procedure.239
Figure A.4 – DL-address collision clearing example .239
Figure A.5 – DL-address collision clearing procedure . 240
Figure A.6 – Path management in a line topology .241
Figure A.7 – Path management in a ring network .242
Figure A.8 – Link fault with neighbouring device .244
Figure A.9 – Link fault of remote device .244

– 8 – PAS 62573 © IEC:2008(E)
Table 1 – Destination DL-address.39

Table 2 – Primitives and parameters used in DL-DATA service.40

Table 3 – DL-DATA primitives and parameters.41

Table 4 – Primitives and parameters used in DL-SPDATA service .42

Table 5 – DL-SPDATA primitives and parameters .43

Table 6 – Primitives and parameters used on DL-NCM_SND service .43

Table 7 – DL-NCM_SND primitives and parameters.44

Table 8 – Summary of Network Control Message Type .45

Table 9 – Summary of DL-management primitives and parameters .47
Table 10 – DLM-RESET primitives and parameters.49
Table 11 – DLM-SET_VALUE primitives and parameters .49
Table 12 – DLM-GET_VALUE primitives and parameters.50
Table 13 – DLM-SAP_ALLOC primitives and parameters .51
Table 14 – DLM-SAP_DEALLOC primitives and parameters .52
Table 15 – DLM-GET_SAP_INFO primitives and parameters .53
Table 16 – DLM-GET_DIAG primitives and parameters.53
Table 17 – DLM-EVENT primitives and parameters.55
Table 18 – DLM event identifier .55
Table 19 – DLM-GET_PATH primitives and parameters .56
Table 20 – Summary of MAC control primitives and parameters.57
Table 21 – MAC-RESET primitives and parameters .58
Table 22 – MAC-FW_CTRL primitives and parameters .58
Table 23 – Summary of Ph-control primitives and parameters.60
Table 24 – Ph-RESET primitives and parameters.61
Table 25 – Ph-GET_LINK_STATUS primitives and parameters .61
Table 26 – Ph-LINK_STATUS _CHANGE primitives and parameters .62
Table 27 – DLL components .65
Table 28 – UNSIGNEDn data type .67
Table 29 – INTEGERn data type .67
Table 30 – DLE configuration parameters .69
Table 31 – Queues to support data transfer .69

Table 32 – Variables to support SAP management .70
Table 33 – Variables to support device information management .70
Table 34 – DL-address .71
Table 35 – Device flags .71
Table 36 – DLM state.72
Table 37 – Device unique identification.72
Table 38 – Unique identification of device connected to R-port1 .72
Table 39 – Unique identification of device connected to R-port2 .73
Table 40 – MAC address.73
Table 41 – Port information.74
Table 42 – Protocol version .74
Table 43 – Device type .75

PAS 62573 © IEC:2008(E) – 9 –
Table 44 – Device description.75

Table 45 – Hop count.75

Table 46 – Variables to support managing network information.75

Table 47 – Topology .76

Table 48 – Collision count.76

Table 49 – Device count .76

Table 50 – Topology change count .77

Table 51 – Last topology change time.77

Table 52 – RNMP device UID .77
Table 53 – RNMS device UID .77
Table 54 – LNM device UID for R-port1 .78
Table 55 – LNM device UID for R-port2 .78
Table 56 – Network flags .78
Table 57 – Variables and counter to support managing path information.79
Table 58 – Hop count for R-port1 direction.80
Table 59 – Hop count for R-port2 direction.80
Table 60 – Preferred R-port .80
Table 61 – Destination R-port .81
Table 62 – In net count .82
Table 63 – In net time .82
Table 64 – Out net count .82
Table 65 – Out net time .82
Table 66 – Version and length .85
Table 67 – Destination DL-address .86
Table 68 – Source DL-address.87
Table 69 – Frame control .87
Table 70 – Extension .89
Table 71 – Destination service access point .90
Table 72 – source service access point.90
Table 73 – FCS length, polynomials and constants .91
Table 74 – DT DLPDU parameters.95

Table 75 – Primitives exchanged between DLS-user and DLE to send a DT DLPDU .97
Table 76 – Primitives exchanged between DLS-user and DLEs to receive a DT DLPDU .97
Table 77 – SPDT DLPDU parameters .98
Table 78 – Primitive exchanged between DLS-User and DLEs to send an SPDT DLPDU .98
Table 79 – Primitives exchanged between DLS-user and DLEs to receive an SPDT DLPDU.99
Table 80 – NCM_LA DLPDU parameters.100
Table 81 – NCM_AT DLPDU parameters .
...

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...