BS EN IEC 61158-5-28:2023
$215.11
Industrial communication networks. Fieldbus specifications – Application layer service definition – Type 28 elements
Published By | Publication Date | Number of Pages |
BSI | 2023 | 72 |
PDF Catalog
PDF Pages | PDF Title |
---|---|
2 | undefined |
5 | Annex ZA (normative)Normative references to international publicationswith their corresponding European publications |
7 | English CONTENTS |
10 | FOREWORD |
12 | INTRODUCTION |
13 | 1 Scope 1.1 Overview |
14 | 1.2 Specifications 1.3 Conformance 2 Normative references |
15 | 3 Terms, definitions, symbols, abbreviated terms and conventions 3.1 Referenced terms and definitions 3.1.1 ISO/IEC 7498-1 terms 3.1.2 ISO/IEC 8822 terms |
16 | 3.1.3 ISO/IEC 9545 terms 3.1.4 ISO/IEC 8824 terms 3.2 Additional terms and definitions for this IEC 61158-5-28 |
17 | 3.3 Abbreviations and symbols |
18 | 3.4 Conventions 3.4.1 Overview 3.4.2 Conventions for class definitions |
19 | 3.4.3 Conventions for service definitions |
20 | 4 Concepts 5 Data type ASE 5.1 General 5.1.1 Overview |
21 | 5.1.2 Overview of basic types 5.1.3 Overview of fixed-length types Figures Figure 1 – Data type class hierarchy example |
22 | 5.1.4 Overview of constructed types 5.2 AL defined data types 5.2.1 Fixed length types Tables Table 1 – TIMEV type data coding |
23 | Table 2 – TIMEDATE type coding Table 3 – TIMEOFDAY type coding |
24 | 5.2.2 String type Table 4 – TIMEDIFFER type coding Table 5 – VISIBLESTRING type data coding |
25 | 5.2.3 Structure type Figure 2 – BITMAP data type Table 6 – Description of time information structure TIMEINFO_S |
26 | Table 7 – Description of clock option information structure CLOCK_OPTION_INFO_S |
27 | Table 8 – Description of network configuration parameter structure NETWORK_CFG_PARA_S |
28 | Table 9 – Description of MAC mapping table NETWORKID_MAC_MAP_TABLE_S |
29 | Table 10 – Description of IP mapping table structure IP_MAP_TABLE_S |
30 | 6 Type 28 communication model specification 6.1 General |
31 | 6.2 Protocol stack for Type 28 fieldbus Figure 3 – AL in fieldbus protocol stack architecture Figure 4 – Type 28 AL protocol architecture |
32 | 6.3 Data mapping modelling Figure 5 – Data mapping modelling object structure |
33 | Figure 6 – Diagram of mapping data buffers and service data variables |
34 | 6.4 Overview of Type 28 communication model 6.4.1 General 6.4.2 P/S Figure 7 – Diagram of P/S model Table 11 – Service data mapping table parameter list |
35 | 6.4.3 C/S 6.5 AL related management information table 6.5.1 General Figure 8 – P/S model of PUSH mode Figure 9 – P/S model of PULL mode Figure 10 – Diagram of C/S communication model |
36 | 6.5.2 Time management information table Table 12 – Time management information table |
37 | 6.5.3 Network management information table Table 13 – Network management information table |
38 | 6.6 ASEs 6.6.1 Overview Table 14 – Communication models supported by Type 28 AL ASEs Table 15 – Application service interface return value list |
39 | 6.6.2 RT data ASE Table 16 – RT data service interface parameters |
40 | Figure 11 – RT data transmission model |
41 | 6.6.3 nRT data ASE Table 17 – nRT data service interface parameters |
42 | Figure 12 – Diagram of nRT data request response model |
43 | 6.6.4 Time ASE Figure 13 – Diagram of nRT data AP interaction based on C/S communication model Figure 14 – Diagram of nRT data AP interaction based on P/S communication model |
44 | Table 18 – Timing service interface parameters |
45 | Figure 15 – Time synchronization application interaction process |
46 | 6.6.5 Resource ASE Figure 16 – Time query process |
47 | Table 19 – Resource service interface parameters |
48 | 6.6.6 Addressing ASE Figure 17 – Resource AP interaction based on C/S communication model Figure 18 – Resource ASE local service function diagram |
49 | Figure 19 – NETWORKID identification field structure |
50 | Table 20 – Addressing service interface parameters |
51 | Figure 20 – NETWORKID interaction process diagram Figure 21 – Diagram of MAC mapping table service function |
52 | Figure 22 – IP mapping table service function diagram Figure 23 – Type 28 AL data message mapped to IP payload data payload |
53 | 6.6.7 Management ASE Figure 24 – Type 28 AL protocol header and IP protocol header mapping Figure 25 – IP data message is mapped to valid data of Type 28 AL data message |
54 | Table 21 – Management service interface parameters |
56 | Figure 26 – Static configuration initialization process |
57 | Figure 27 – Join the network interaction process |
58 | Figure 28 – Passively exit the network interaction process |
59 | Figure 29 – Actively exit network interaction process Figure 30 – Diagram of diagnostic object mapping |
60 | 6.6.8 Virtualization ASE Figure 31 – Diagram of the logging process |
61 | Figure 32 – A physical bus divided into two virtual bus domain diagrams Table 22 – Virtual service interface parameters |
62 | Figure 33 – Diagram of virtualized AP interaction based on C/S communication model |
63 | 6.7 Application service 6.7.1 Overview 6.7.2 Read service 6.7.3 Write service Figure 34 – Virtualization ASE local implementation diagram Table 23 – Read service parameters |
64 | Table 24 – Write service parameters Table 25 – Application service errcode |
65 | Annex A (informative) Example of service data mapping DTU message Figure A.1 – Data transmission unit message content example |
66 | Annex B (informative) Example of OPC UA data model and Type 28 data model mapping Figure B.1 – OPC UA data model and mapping of Type 28 data model |
67 | Annex C (informative) Example of RTA service processing Figure C.1 – Example of RTA service processing |
68 | Annex D (informative) Type 28 virtualization solution example Figure D.1 – Diagram of Type 28 industrial bus service deployment Figure D.2 – Diagram of networking topology based on the virtualized bus |
69 | Figure D.3 – Virtual network topology based on logical business function RT1 |
70 | Table D.1 – Virtual bus environment node NETWORKID list |
71 | Bibliography |