| Standard ID | Contents [version] | USD | STEP2 | [PDF] delivered in | Standard Title (Description) | Status | PDF |
| GB/Z 26157.4-2010 | English | RFQ |
ASK
|
3 days [Need to translate]
|
Digital data communication for measurement and control -- Fieldbus for use in industrial control systems -- Type 2: ControlNet and EtherNet/IP specification -- Part 4: Network and transport layer
| Valid |
GB/Z 26157.4-2010
|
PDF similar to GBZ26157.4-2010
Basic data | Standard ID | GB/Z 26157.4-2010 (GB/Z26157.4-2010) | | Description (Translated English) | Digital data communication for measurement and control -- Fieldbus for use in industrial control systems -- Type 2: ControlNet and EtherNet/IP specification -- Part 4: Network and transport layer | | Sector / Industry | National Standard | | Classification of Chinese Standard | N10 | | Classification of International Standard | 25.040 | | Word Count Estimation | 153,153 | | Date of Issue | 2011-01-14 | | Date of Implementation | 2011-06-01 | | Quoted Standard | ISO/IEC 8802-4-1990; GB/T 15629.3-1995; GB/Z 26157.9-2010 | | Adopted Standard | IEC 61158-2003, MOD | | Regulation (derived from) | ?National Standard Approval Announcement 2011 No.2 | | Issuing agency(ies) | Ministry of Health of the People's Republic of China | | Summary | This standard specifies the requirements identified in the control network node in the network and transport layers. The technical guidance document applies to determine the control network and transport layer network layer corresponds to comply with GB/T 9387 's seven- layer ISO model 3 and 4. Figure 1 shows the location of the network and transport layer in the OSI model. | GBZ26157.4-2010: Digital data communication for measurement and control -- Fieldbus for use in industrial control systems -- Type 2: ControlNet and EtherNet/IP specification -- Part 4: Network and transport layer
---This is a DRAFT version for illustration, not a final translation. Full copy of true-PDF in English version (including equations, symbols, images, flow-chart, tables, and figures etc.) will be manually/carefully translated upon your order.
Digital data communication for measurement and control. Fieldbus for use in industrial control systems. Type 2. ControlNet and EtherNet/IP specification. Part 4. Network and transport layer
ICS 25.040
N10
People's Republic of China national standardization of technical guidance documents
Measure and control digital data communications
Industrial control system with fieldbus
Type 2.ControlNet and EtherNet/IP specifications
Part 4. Network layer and transport layer
Fieldbus for use in industrial control systems-
Part 4.Networkandtransportlayer
(IEC 61158.2003 TYPE 2, MOD)
2011-01-14.2011-06-01 implementation
General Administration of Quality Supervision, Inspection and Quarantine of People's Republic of China
China National Standardization Administration released
Directory
Introduction Ⅶ
Introduction Ⅷ
1 Scope 1
2 Unconnected Message Manager (UCMM) 1
2.1 Overview 1
2.2 external interface 2
2.3 PDU format 3
2.4 UCMM client 4
2.5 UCMM server 5
2.6 Examples (informative) 9
2.7 Holder UCMM 11
3 Message Routing (MR) Object 11
3.1 Overview 11
3.2 Path 11
3.3 External Interface (SDU) 17
3.4 Packet Router Header (PDU) 17
4 Connection Manager (CM) object 18
4.1 Service Data Unit (SDU) 18
4.2 Parameter 22
4.3 Connection Manager Service (PDU) 28
4.4 Error Code 37
5 Transfer connection 44
5.1 Transmission Meaning 44
5.2 Tools for Discussion of Transmission Services (Informative) 44
5.3 Transferring Connected Components 45
5.4 Create Transfer Connection 48
5.5 Binding producers and consumers to network connections 48
5.6 Transmission Type 50
6 transmission class 53
6.1 Category 53
6.2 Class 0 (Nul or Base) 53
6.3 class 1 (repeat detection) 56
Category 2 (Confirmation)
6.5 Category 3 (Confirmed-Certified) 69
6.6 Class 4 to Class 6 Common Elements 79
6.7 class 4 (not blocked) 83
6.8 Category 5 (non-blocking, segmented) 92
Class 6 (multicast, segment) 104
6.10 Retry timer 119
7 Application Connection 121
7.1 Connection 121
7.2 Production Trigger, Transport Class, and RPI 121
7.3 Polling 122
8 TCP/IP package 122
8.1 Introduction (informative) 122
8.2 CIPPDU on TCP/IP 123
8.3 Connection Manager 124
8.4 Class 0 and Class 1 connection data 127
8.5 IP Multicast Range and Address Allocation 128
8.6 Packaging Agreement 129
8.7 Command Descriptions 132
Session Management 137
8.9 Common Packet Formats 138
9 TCP/IP on the ControlNet physical layer
9.1 IPLpackets (Fixed Label 0x85) 140
9.2 Ethernet Lpackets (Fixed Label 0x89) 140
9.3 Examples of TCP/IP on ControlNet 141
Figure 1 and the ISO /OSI model of the relationship 1
Figure 2 client state transition Figure 4
Figure 3 high-end server state transition Figure 6
Figure 4 low-end UCMM server state transition Figure 8
Figure 5 UCMM flow chart with one unfinished message 9
FIG. 6 is a flowchart of a UCMM having a plurality of unfinished messages simultaneously. FIG
Figure 7 Segment type 12
Figure 8 Port 12
Figure 9 network connection parameters 23
Figure 10 Priority/Duration 25
Figure 11 Connection establishment timeout 26
Figure 12 Communication model in the transmission service up and down relationship 44
Figure 13 Application to Application Data Transfer Figure 44
Figure 14 Data Flow of a Link Producer Figure 45
Figure 15 State Transition Diagram (StateTransDiagramDiagram-STD) 45
Figure 16 Link Consumer Data Flow Figure 46
Figure 17 Link Consumer Status Transition Figure 47
Figure 18 Trigger 47
Figure 19 T-PDU Buffer 48
Figure 20 Binding of a transport instance to a producer and consumer of a transport connection without an opposite-direction data path 49
Figure 21 Binding of a Transport Instance to Producers and Consumers of a Transport Connection with an Opposite Data Path 49
Fig. 22 Binds the transmission instance to the producer and consumer of the multicast connection 50 when the transmission connection has no reverse data path
Fig. 23 Binding of transmission instances to producers and consumers of multicast connections 50 when the transmission connection has an opposite direction data path
Figure 24 Data flow using class 0 and server class 0 with client transfer Figure 54
Figure 25 Sequence diagram of data transfer with transport class 0 54
Figure 26 Class 0 Customer Status Transition Figure 55
Figure 27 Class 0 Server State Transition Figure 56
Figure 28 Data Flow with Class 1 and Server Transport Class 1 Using Client Transfer Figure 57
Figure 29 Data Transfer Sequence with Client Transport Class 1 and Server Transport Class 1 Figure 57
Figure 30 Class 1 Customer State Transition Diagram (STD) 58
Figure 31 Class 1 Server State Transition Diagram (STD)
Figure 32 Data Flow Using Class 2 for Customer Delivery and Class 2 for Server Transmission Figure 63
Figure 33 Data Transfer with Client Transfer Class 2 and Server Transfer Class 2 and No Data Returned Figure 63
Figure 34 Data Transfer Sequence with Customer Transfer Class 2 and Server Transfer Class 2 with Return Data Figure 64
Figure 35 Class 2 Customer State Transition Diagram (STD) 65
Figure 36 Class 2 Server STD 67
Figure 37 Data Flow for Class 3 and Server 3 Transmission with Customer
Figure 38 Data Transfer Sequence with Client Transfer Class 3 and Server Transfer Class 3 and No Data Returned Figure 71
Figure 39 Using Client Transfer Class 3 and Server Transfer Class 3 with Data Transfer Sequence When Returning Data Figure 72
Figure 40 Class 3 Customer State Transition Diagram (STD) 73
Figure 41 Class 3 Server State Transition Diagram (STD) 76
Figure 42 Streams for Transport Class 4 and Class 5 Figure 79
Figure 43 Transport class 4 and class 5 basic structure 80
Figure 44 Class 6 basic structure 81
Figure 45 General state transition from class 4 to class 6 Figure 82
Figure 46 Sequence diagram of message exchange with transport class 4 Figure 84
Figure 47 Sequence of Overwritten Messages Written to Each Other Figure 85
Figure 48 Sequence of packet exchanges queued by transmission class 4 Figure 86
Figure 49 Sequence to Retry with Transfer Class 4 Figure 87
Figure 50 Sequence of free traffic with transport class 4 Figure 88
Figure 51 Class 4 Transmitter STD 89
Figure 52 Class 4 receiver STD 91
Figure 53 Three-Segment Sequence Using Transmit Class 5 Figure 94
Figure 54 Using retransmission class 5 with retry segment sequence Figure 95
Figure 55 Two-Segment Sequence Using Transport Class 5 Figure 96
Figure 56 Message Sequence with Abort of Transmission Class 5 Figure 96
Figure 57 Class 5 Transmitter STD 97
Figure 58 Class 5 receiver STD 100
Figure 59 Transport class 6 data flow Figure 104
Figure 60 Sequence diagram of message exchange when class 6 is transmitted
Figure 61 Retry Sequence with Transfer Class 6 106
Figure 62 Sequence of free traffic with class 6 transmission 107
Figure 63 asks to overwrite the sequence diagram 108 written with Nul
Figure 64 Sequence of responses covering overwrite ACK with nul written Figure 108
Figure 65 uses a three-segment sequence of transmission class 6 Figure 109
Figure 66 shows a reordered segmentation sequence diagram of transmission class 6 110
Figure 67 shows a two-segment sequence diagram of transmission class 6 110
Figure 68 Message Sequence with Abort of Transmission Class 6 Figure 111
Figure 69 Class 6 Customer STD 112
Figure 70 Class 6 Server STD 115
Figure 71 Retry timer 120
Figure 72 Retry timer state transition diagram 120
Figure 73 ControlNet and ISO /OSI model of the corresponding 123
Figure 74 Connection ID with avatar ID
Figure 75 Pseudo-random connection ID 126
Figure 76 Encapsulation packet 130
Table 1 UCMM Command Code 3
Table 2 UCMM Client Status Event Matrix 4
Table 3 High-end UCMM server status event matrix 6
Table 4 Low-end UCMM server status event matrix 8
Table 5 UCMM Affairs 10
Table 6 Examples of possible port segments 13
Table 7 Logical Segment 13
Table 8 Network segment 15
Table 9 Time-out multiplication factor 24
Table 10 Time slice unit 25
Table 11 Connection ID Selection 27
Table 12 Connection Manager Class-Specific Services 29
Table 13 unconnected_reply successful connection format 34
Table 14 Unconnected_reply format on failure 35
Table 15 Connection Manager service request error code 37
Table 16 State Event Matrix (StateEventMatrix-SEM)
Table 17 Status Event Matrix (SEM) 47
Table 18 Notice 48
Table 19 Transmission class
Table 20 Class 0 Customer Status Event Matrix 55
Table 21 Class 0 Server Status Event Matrix 56
Table 22 Class 1 Customer Status Event Matrix (SEM) 59
Table 23 Class 1 Server Status Event Matrix (SEM) 60
Table 24 Class 2 Customer Status Event Matrix (SEM) 65
Table 25 Class 2 Server SEM 68
Table 26 Class 3 Customers SEM 74
Table 27 Class 3 Server Status Event Matrix (SEM) 76
Table 28 Transmit and write events in class 4 and class 5 79
Table 29 Class 4 to Class 6 header format 81
Table 30 General state event matrices of class 4 to class 6 82
Table 31 Class 4 Transmitter SEM 89
Table 32 Class 4 Receiver SEM 91
Table 33 Class 5 Transmitter SEM 98
Table 34 Class 5 Receiver Status Event Matrix (SEM) 101
Table 35 Class 6 Customer SEM 112
Table 36 Class 6 Server SEM 116
Table 37 Retry timer SEM 120
Table 38 Production Triggering, Transport Classes, and RPI How to Determine When Data Is Generated 122
Table 39 TCP/IP Link Address Example 125
Table 40 UDP data format for class 0 and class 1 127
Table 41 Encapsulates header 130
Table 42 Encapsulates the command code 130
Table 43 Encapsulation status code 131
Table 44 Optional Flags
Table 45 Nop Package Header 132
Table 46 RegisterSession Header 132
Table 47 RegisterSession data section 133
Table 48 Option Flags
Table 49 RegisterSession Answer 133
Table 50 RegisterSession Response, Data Section 133
Table 51 UnRegisterSession Header 134
Table 52 ListServices Header 134
Table 53 ListServices Answer 134
Table 54 ListServices Data Section
Table 55 Service Type Codes 135
Table 56 Communication Performance Indicators 135
Table 57 SendRRData Header 135
Table 58 SendRRData Data Section 136
Table 59 SendRRData Response 136
Table 60 SendUnitData Header 136
Table 61 SendUnitData data section 137
Table 62 General Packet Formats
Table 63 Address and Data Item Structure 138
Table 64 Address Type ID 138
Table 65 Data Type ID 139
Table 66 Null Value Address Type 139
Table 67 Connection Address Type 139
Table 68 Sequence Address Type 139
Table 69 UCMM data types 140
Table 70 Connection Data Types 140
Table 71 Sockaddrinfo Item 140
Foreword
IEC 61158.2003 "Fieldbus for the Measurement and Control of Digital Data Communications Industrial Control Systems" includes 10 fieldbus
Types of.
--- Type 1.IEC technical report;
--- Type 2.ControlNet and Ethernet/IP;
--- Type 3.PROFIBUS;
--- Type 4.P-Net;
--- Type 5.FFHSE;
--- Type 6.SwiftNet;
--- Type 7.WorldFIP;
--- Type 8.Interbus;
--- Type 9.FFAL;
--- Type 10.PROFINET.
The standardization of the guidance of technical documents to amend the use of IEC 61158.2003 "Measurement and Control Digital Data Communications Industrial Control System
Fieldbus Type 2. ControlNet and EtherNet/IP Specification Part 4. Network and Transport Layers. "
IEC 61158 series of standards will be 10 kinds of fieldbus technology mixed together to write, not easy to domestic engineering and technology
Off personnel on a variety of bus technology reading and understanding of the National Industrial Process Measurement and Control Standardization Technical Committee in the use of international standards
On time, only used in the country has a wide range of applications 2.ControlNet and EtherNet/IP specification of the relevant technical content, and
According to the habits of technology developers will be divided into 10 parts to prepare. In technical content and international standards no difference, for the convenience of me
National users, in the text of the structure of the layout of the appropriate adjustments, and according to GB/T 1.1 requirements for the preparation.
GB /Z 26157 "Measurement and Control Digital Data Communication Fieldbus Type for Industrial Control Systems 2.ControlNet and Ether-
Net/IP specification "is divided into the following 10 sections.
GB /Z 26157.1 General Description;
GB /Z 26157.2 physical layer and media;
GB /Z 26157.3 data link layer;
GB /Z 26157.4 network layer and transport layer;
GB /Z 26157.5 Data Management;
GB /Z 26157.6 object model;
GB /Z 26157.7 equipment rules;
GB /Z 26157.8 electronic data sheet;
GB /Z 26157.9 station management;
GB /Z 26157.10 object library.
This guidance document is Part 4.
This guidance document is proposed by China Machinery Industry Federation.
This Guidance Document is governed by the National Technical Committee for Measurement and Control of Industrial Processes (SAC/TC124).
The drafting of the guidance of technical documents. Machinery Industry Instrumentation Technology and Economy Institute, Tsinghua University, Southwest University, Beijing Iron and Steel
Design and Research Institute, China Instrument Association, China Mechatronics Technology Association, Shanghai Automation Instrumentation Co., Ltd., Shanghai Engineering
Automation Instrumentation Institute, Shanghai Electric Institute of Science (Group) Co., Ltd., Rockwell Automation Research (Shanghai) Co., Ltd.
The main drafters of this technical document are Zheng Xu, Mei Ke, Chen Kai Tai, Wang Jinbiao, Peng Yu, Liu Feng, Bao Weihua, Xia Dehai, Dong Jingchen,
Ruan Yu Dong, Li Baihuang, Wang Chunxi, Wang Yumin.
Introduction
The task of the network and transport layer is to establish and maintain the connection. You can compare a connection to a telephone line. Phone system root when calling is required
According to your dial select the path and set the path of each switching station. This virtual channel remains open as the call continues
Realize data or voice transmission. In a telephone system, a call can go through several different types of links and the format of the data
Different links change, but the same appearance appears before the conversant and the receiving caller. One end of the voice immediately output the other end
the sound of.
A connected message has previously agreed on resources and parameters for the source, destination, and all intermediate delivery points. These resources are associated with
The only identifier related, does not need to be included in each message, only need to identify the connection ID in the message can indicate the relevant parameters,
This leads to a marked improvement in the efficiency of the message.
Unconnected messages provide a way to communicate with a target object that was previously un-agreed resources, so messages should carry all the details of the target ID
Emotions, internal data description, details of source ID if needed. No message is used to establish the connection.
The standard and this part of the connection established by the agreement and unconnected together referred to as Control and Information Protocol (CIP).
Measure and control digital data communications
Industrial control system with fieldbus
Type 2.ControlNet and EtherNet/IP specifications
Part 4. Network layer and transport layer
1 Scope
This guidance document defines the network and transport layer requirements for a node on a defined control network.
The guidance and technical documents applicable to determine the network and transmission control layer corresponds to GB/T 9387 in accordance with the seven ISO model
Type 3 and 4. Figure 1 shows the location of the network and transport layer within the OSI model.
Note Most of the terms and models for the network and transport layers come from ISO /IEC 8802-4.1990 or GB/T 15629.3-1995. The type of data used
Part 5 data management instructions.
Figure 1 and the ISO /OSI model of the relationship
2 Not connected message manager (UCMM)
2.1 Overview
UCMM shall provide unconnected request/response packet service, this service is only used to support multiple unfinished packet processing a single chain
road. The number of pending unprocessed messages is implementation-specific. All nodes should have UCMM and support at least one incomplete
|