GB/T 20965: Evolution and historical versions
| Standard ID | Contents [version] | USD | STEP2 | [PDF] delivered in | Standard Title (Description) | Status | PDF |
| GB/T 20965-2025 | English | RFQ |
ASK
|
3 days [Need to translate]
|
Control network HBES technical specification - Home and building control system
| Valid |
GB/T 20965-2025
|
| GB/T 20965-2013 | English | RFQ |
ASK
|
3 days [Need to translate]
|
Control network HBES technical specification -- Home and building control system
| Valid |
GB/T 20965-2013
|
PDF similar to GB/T 20965-2025
Basic data | Standard ID | GB/T 20965-2025 (GB/T20965-2025) | | Description (Translated English) | Control network HBES technical specification - Home and building control system | | Sector / Industry | National Standard (Recommended) | | Classification of Chinese Standard | N10 | | Classification of International Standard | 25.040 | | Word Count Estimation | 622,668 | | Date of Issue | 2025-02-28 | | Date of Implementation | 2025-09-01 | | Issuing agency(ies) | State Administration for Market Regulation, China National Standardization Administration | GB/T 20965-2025: Control network HBES technical specification - Home and building control system---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.
GB/T 20965-2025 English version. Control network HBES technical specification - Home and building control system
ICS 25.040
CCSN10
National Standard of the People's Republic of China
Replace GB/T 20965-2013
HBES Technical Specifications for Residential and Control Networks
Building Control Systems
Home and building control system
Released on 2025-02-28
2025-09-01 Implementation
State Administration for Market Regulation
The National Standardization Administration issued
Table of Contents
Preface XXI
Introduction XXII
1 Scope 1
2 Normative references 1
3 Terms and definitions 3
4 Abbreviations18
5 System 24
5.1 Architecture 24
5.1.1 Overview 24
5.1.2 HBES reference model 24
5.1.3 Reference points and functional groups 34
5.1.4 Interface standardization of specific reference points 36
5.1.5 System Characteristics 39
5.2 General technical requirements 42
5.2.1 Overview 42
5.2.2 Topology, wiring and power supply for devices connected to twisted pair or coaxial media 42
5.2.3 Security 43
5.2.4 Environmental conditions 47
5.2.5 Electromagnetic compatibility requirements for equipment connected to twisted pair or coaxial cable 48
5.2.6 Reliability 64
5.3 General functional safety requirements for HBES products 64
5.3.1 General 64
5.3.2 General requirements 64
5.3.3 Functional safety requirements 66
6 Application Features 71
6.1 Application Structure 71
6.1.1 Overview 71
6.1.2 Application Structure 71
6.2 Type 1 HBES User Process 72
6.2.1 Overview 72
6.2.2 Object Model 72
6.2.3 Group Object Server 73
6.2.4 Interface Object Server 77
7 Dielectric Independent Layer 81
7.1 Type 1 HBES application layer 81
7.1.1 Overview 81
7.1.2 Application layer services 81
7.1.3 Application Layer Protocol Data Unit (APDU) 82
7.1.4 Application layer services 89
7.1.5 Application layer parameters 144
7.2 Common parts of transport layer, network layer and data link layer of Class 1 HBES 144
7.2.1 Overview 144
7.2.2 Requirements for the Media-Independent Data Link Layer 144
7.2.3 Network Layer Requirements 152
7.2.4 Transport layer requirements 161
7.3 KNXnet/IP communication 184
7.3.1 Overview 184
7.3.2 Requirement 185
7.4 HBES Safety 250
7.4.1 General Introduction 250
7.4.2 Norm 255
7.5 Network Services 287
7.5.1 General Principles 287
7.5.2 Introduction to General Technology of HBES Network Services 287
7.5.3 Overview 288
7.5.4 HBES Information Model 290
7.5.5 HBES Network Interface OBIX 301
7.5.6 HBES Gateway OBIX 311
7.5.7 Gateway Profile 312
8 Medium and medium-related layers 315
8.1 Class 1 HBES Power Line 315
8.1.1 Overview 315
8.1.2 Requirements for Class 1 HBES, Power Line PL110 315
8.1.3 Requirements for Class 1 HBES, Power Line PL132 334
8.2 Twisted Pair Cables for Class 1 HBES Networks 344
8.2.1 Overview 344
8.2.2 Requirements for Class 1 HBES, Twisted Pair Type 0 (TP0) 344
8.2.3 Requirements for Class 1 HBES, Twisted Pair Type 1 (TP164 and TP1256) 365
8.3 HBESRF 397
8.3.1 General 397
8.3.2 HBESRF Physical Layer 397
8.3.3 Physical Layer 400 of HBESRFMulti
8.3.4 HBESRF Data Link Layer 403
8.3.5 Compatibility between HBESReady and HBESMulti 427
9 Management Regulations 428
9.1 Overview 428
9.2 Network Management Procedures 429
9.2.1 General Principles 429
9.2.2 NM_IndividualAddress_Read 429
9.2.3 NM_IndividualAddress_Write 430
9.2.4 NM_SerialNumberDefaultIA_Scan 432
9.2.5 NM_IndividualAddress_SerialNumber_Read 433
9.2.6 NM_IndividualAddress_SerialNumber_Write 434
9.2.7 NM_DomainAddress_Read 435
9.2.8 NM_DomainAddress_Write 435
9.2.9 NM_DomainAddress_Scan 438
9.2.10 NM_Router_Scan 438
9.2.11 NM_SubnetworkDevices_Scan 439
9.2.12 NM_SubnetworkAddress_Read 440
9.2.13 NM_IndividualAddress_Reset 440
9.2.14 NM_IndividualAddress_Scan 441
9.2.15 NM_IndividualAddress_Check 442
9.2.16 NM_IndividualAddress_Check_LocalSubnetwork 443
9.2.17 NM_GroupAddress_Check 444
9.2.18 NM_FunctionalBlock_Scan 445
9.3 Equipment Management Procedures 445
9.3.1 General Principles 445
9.3.2 General Exception Handling 446
9.3.3 DM_Connect 446
9.3.4 DM_Disconnect 447
9.3.5 DM_Authorize 448
9.3.6 DM_SetKey 449
9.3.7 DM_Restart 450
9.3.8 DM_Delay 451
9.3.9 DM_IndividualAddressRead 451
9.3.10 DM_IndividualAddressWrite 451
9.3.11 DM_DomainAddressRead 451
9.3.12 DM_DomainAddressWrite 451
9.3.13 DM_ProgMode_Switch 452
9.3.14 DM_GroupObject_Link_Read 452
9.3.15 DM_GroupObject_Link_Write 453
9.3.16 DM_MemWrite 454
9.3.17 DM_MemVerify 457
9.3.18 DM_MemRead 458
9.3.19 DM_UserMemWrite 459
9.3.20 DM_UserMemVerify 462
9.3.21 DM_UserMemRead 463
9.3.22 DM_InterfaceObjectWrite 464
9.3.23 DM_InterfaceObjectVerify 466
9.3.24 DM_InterfaceObjectRead 467
9.3.25 DM_InterfaceObjectScan 469
9.3.26 DM_LoadStateMachineWrite 470
9.3.27 DM_LoadStateMachineVerify 478
9.3.28 DM_LoadStateMachineRead 480
9.3.29 DM_RunStateMachineWrite 482
9.3.30 DM_RunStateMachineVerify 483
9.3.31 DM_RunstateMachineRead 485
9.3.32 DM_LCSlaveMemWrite 487
9.3.33 DM_LCSlaveMemVerify 489
9.3.34 DM_LCSlaveMemRead 490
9.3.35 DM_LCExtMemWrite 491
9.3.36 DM_LCExtMemVerify 492
9.3.37 DM_LCExtMemRead 493
9.3.38 DM_LCExtMemOpen 494
9.3.39 DM_LCRouteTableStateWrite 495
9.3.40 DM_LCRouteTableStateVerify 496
9.3.41 DM_LCRouteTableStateRead 497
10 Product Conformity Assessment 498
10.1 Overview 498
10.2 Applicable Standards 498
10.2.1 Overview 498
10.2.2 Protocol 498
10.2.3 Electrical safety 498
10.2.4 Electromagnetic Compatibility (EMC) 498
10.2.5 Environment 498
10.2.6 Functional Safety 499
11 Installation Requirements - General Requirements for Category 1 HBES Twisted Pair Cabling 499
11.1 Overview 499
11.2 Systems and Cabling 499
11.3 Wiring Model and General Requirements 500
11.3.1 Segment connection, generally requires 500
11.3.2 Coexistence of HBES Control Bus, Broadband Multimedia and Mains Power 501
11.4 Infrastructure Requirements 502
11.4.1 General 502
11.4.2 Preliminary Configuration of Installation Space 505
11.5 Connector 510 for Category 1 HBES twisted pair cable
11.6 Cable and installation accessories requirements 512
11.6.1 Channel and Link Performance 512
11.6.2 TP cable characteristics 512
11.6.3 Annex 513
11.7 Electrical safety and functional safety 514
11.7.1 Electrical safety 514
11.7.2 Functional insulation of bus segments 515
11.7.3 Functional Safety 515
11.8 EMC 515
11.9 Grounding and shielding grounding for lightning protection 516
11.10 Fire reaction and fire resistance requirements 516
11.11 Environmental aspects 516
11.12 Management and Documentation 516
Appendix A (informative) Example of method for determining safety integrity level 517
Appendix B (Informative) Development of Hazard and Essential Functional Safety Requirements 519
Appendix C (Informative) Example of a transport layer connection-oriented state machine state diagram 526
Appendix D (Informative) Example of binary format of KNX/IP frame 536
Appendix E (Informative) Code Table 555
Appendix F (Informative) Application of CCM 561
Appendix G (Informative) Example - Complete Encoding of HBES Security APDU 565
Appendix H (Informative) Certification 571
Appendix I (Informative) Wiring Model 572
Appendix J (Informative) Preliminary Deployment and Planning Aspects 576
Appendix K (informative) Performance of building comfort levels 580
Appendix L (informative) Standard connectors for TP type 0 and type 1 of class 1 HBES 592
Appendix M (Informative) Cable/Channel and Link Requirements 594
References 596
Figure 1 Single address 6
Figure 2 Group Address 8
Figure 3 Overview of HBES reference model 25
Figure 4 HBES application process 28
Figure 5 HBES device application process structure 28
Figure 6 HBES device application process model 29
Figure 7 User process link 29
Figure 8 Communication resource management 31
Figure 9 Communication resource user interface 32
Figure 10 Example of device management function using common interface 32
Figure 11 Application process management 33
Figure 12 User interface of application process resources 33
Figure 13 Reference points and functional groups 34
Figure 14 Example of multiple reference points facing away from the network medium 34
Figure 15 Example of multiple reference points for network media 35
Figure 16 Gateways between different network segments 35
Figure 17 Reference point hierarchy 35
Figure 18 Standard interface position 36
Figure 19 Symbols used in Figures 20 to 22 36
Figure 20 Single-wire connection 37
Figure 21 Two-wire connection without interruption of bus when device is not connected (recommended solution) 37
Figure 22 Two-wire connection with bus interruption when device is not connected 37
Figure 23 General interface location 38
Figure 24 Process interface location 38
Figure 25 HBES interactive application 40
Figure 26 Geographical distribution zones in buildings 40
Figure 27 Power supply unit 43 of HBES equipment
Figure 28 Protective isolation of separately installed HBES equipment 46
Figure 29 Protective isolation of adjacently installed HBES equipment 46
Figure 30 Validity range of this document 49
Figure 31 Testing the mains connection of the power supply unit 52
Figure 32 Testing the bus connection of the power supply unit 53
Figure 33 Testing the mains connection of bus equipment 53
Figure 34 Testing the media interface of the bus device 53
Figure 35 Testing the general interface, process interface and input/output connections of the bus device 54
Figure 36 Testing the mains connection of the power supply unit 54
Figure 37 Power supply unit bus connection test 55
Figure 38 Testing the mains connection of the HBES device 55
Figure 39 Media interface test of HBES equipment 56
Figure 40 Testing the common interface, process interface and input/output connections of the HBES device 56
Figure 41 Electrostatic discharge 57
Figure 42 Test in an anechoic chamber 57
Figure 43 Top view 58
Figure 44 Side view 1 58
Figure 45 Side view 2 58
Figure 46 Side view 3 59
Figure 47 Test arrangement for GB/T 17626.6 test 59
Figure 48 Example of test arrangement in an anechoic chamber 60
Figure 49 Side view 1 (example) 60
Figure 50 Side view 2 (example) 60
Figure 51 Side view 3 (example) 61
Figure 52 Side view 4 (example) 61
Figure 53 Test arrangement for conducted disturbance voltage on bus cables 62
Figure 54 Test arrangement for conducted disturbance voltage on mains terminals 63
Figure 55 Test arrangement for common mode noise current test on bus cable 63
Figure 56 Test arrangement for voltage dips and short interruptions 64
Figure 57 Application structure 71
Figure 58 Possible information flow 72
Figure 59 User process model 73
Figure 60 Data structure of group object 73
Figure 61 Reading group object value 76
Figure 62 Receiving a request to read the value of a group object 76
Figure 63 Write group object value 77
Figure 64 Receive group object value update 77
Figure 65 The structure of the interface object 78
Figure 66 Message flow for A_PropertyValue_Read service 79
Figure 67 Message flow 80 for A_PropertyValue_Write service
Figure 68 Message flow 80 for A_PropertyDescription_Read service
Figure 69 Application layer interaction for non-remote authentication services 82
Figure 70 Application layer interaction of remote authentication service 82
Figure 71 APDU Example 82
Figure 72 ASAP is mapped to TSAP example 89
Figure 73 TSAP mapping to ASAP 89
Figure 74 Processing requests and responses 89
Figure 75 Message flow of A_Group_Value_Read service 90
Figure 76 A_GroupValue_Read-PDU Example 90
Figure 77 Example of A_GroupValue_Response-PDU with ASAP data length greater than 6 bits 91
Figure 78 Example of A_GroupValue_Response-PDU with ASAP data length equal to or less than 6 bits 91
Figure 79 Message flow of A_Group_Value_Write service 92
Figure 80 Example of A_GroupValue_Write-PDU with ASAP data length greater than 6 bits 93
Figure 81 Example of A_GroupValue_Write-PDU with ASAP data length equal to or less than 6 bits 93
Figure 82 A_IndividualAddress_Write-PDU Example 94
Figure 83 A_IndividualAddress_Read-PDU Example 95
Figure 84 A_IndividualAddress_Response-PDU Example 95
Figure 85 A_IndividualAddressSerialNumber_Read service message flow 97
Figure 86 A_IndividualAddressSerialNumber_Read-PDU Example 97
Figure 87 A_IndividualAddressSerialNumber_Response-PDU Example 98
Figure 88 A_IndividualAddressSerialNumber_Write-PDU Example 100
Figure 89 A_ServiceInformation_Indication_Write-PDU Example 101
Figure 90 A_DomainAddress_Write-PDU 102
Figure 91 A_DomainAddress_Read-PDU Example 103
Figure 92 A_DomainAddress_Response-PDU Example 104
Figure 93 A_DomainAddressSelective_Read-PDU Example 105
Figure 94 A_NetworkParameter_Read-PDU Example 106
Figure 95 A_NetworkParameter_Response-PDU Example 107
Figure 96 A_NetworkParameter_Write-PDU Example 109
Figure 97 A_PropertyValue_Read-PDU Example 110
Figure 98 A_PropertyValue_Response-PDU Example 111
Figure 99 A_PropertyValue_Write-PDU Example 113
Figure 100 A_PropertyDescription_Read-PDU Example 115
Figure 101 A_PropertyDescription_Response-PDU Example 115
Figure 102 A_DeviceDescriptor_Read-PDU Example 117
Figure 103 A_DeviceDescriptor_Response-PDU Example 117
Figure 104 A_Link_Read service message flow 119
Figure 105 A_Link_Read-PDU Example 119
Figure 106 A_Link_Response-PDU Example 119
Figure 107 A_Link_Write service message flow 120
Figure 108 A_Link_Write-PDU 121
Figure 109 A_ADC_Read-PDU Example 122
Figure 110 A_ADC_Response-PDU Example 122
Figure 111 A_Memory_Read-PDU Example 124
Figure 112 A_Memory_Response-PDU Example 124
Figure 113 A_Memory_Write-PDU Example 126
Figure 114 A_MemoryBit_Write-PDU 129
Figure 115 A_UserMemory_Read-PDU Example 131
Figure 116 A_UserMemory_Response-PDU 131
Figure 117 A_UserMemory_Write-PDU 133
Figure 118 A_UserMemoryBit_Write-PDU Example 136
Figure 119 A_UserManufacturerInfo_Read-PDU Example 138
Figure 120 A_UserManufacturerInfo_Response-PDU 138
Figure 121 A_Restart-PDU Example 140
Figure 122 A_Authorize_Request-PDU Example 141
Figure 123 A_Authorize_Response-PDU Example 141
Figure 124 A_Key_Write-PDU Example 143
Figure 125 A_Key_Response-PDU Example 143
Figure 126 Data link layer interaction 145
Figure 127 Exchange of Figure L_Data service primitives 146
Figure 128 Frame_format parameter 148
Figure 129 Coding of extended frame format 149
Figure 130 Network layer interconnection (not used for bridges or routers) 153
Figure 131 Basic functions of a router or bridge 153
Figure 132 Example of NPDU format 154
Figure 133 Transport layer interaction 161
Figure 134 TPDU format example 162
Figure 135 Transmission Control Field 162
Figure 136 Device type and configuration example 184
Figure 137 Binary format of KNXnet/IP frame 190
Figure 138 KNXnet/IP header binary format 190
Figure 139 KNXnet/IP server endpoint configuration example 191
Figure 140 Discovery Procedure 192
Figure 141 Establishing data connection 194
Figure 142 General connection header 194
Figure 143 KNX project with multiple installations 197
Figure 144 KNXnet/IP message header 198
Figure 145 Binary format of HPAI structure.200
Figure 146 Binary format of CRI structure.201
Figure 147 Binary format of CRD structure.201
Figure 148 Binary format describing structure 202
Figure 149 Supported Service Family DIB 205
Figure 150 Manufacturer Data DIB 205
Figure 151 Binary format of SEARCH_REQUEST frame 206
Figure 152 Binary format of SEARCH_RESPONSE frame 207
Figure 153 Binary format of DESCRIPTION_REQUEST frame 208
Figure 154 Binary format of DESCRIPTION_RESPONSE frame 209
Figure 155 Binary format of CONNECT_REQUEST frame 210
Figure 156 Binary format of CONNECT_RESPONSE frame 211
Figure 157 Binary format of CONNECTIONSTATE_REQUEST frame 212
Figure 158 Binary format of CONNECTIONSTATE_RESPONSE frame 213
Figure 159 Binary format of DISCONNECT_REQUEST frame 214
Figure 160 Binary format of DISCONNECT_RESPONSE frame 214
Figure 161 IP protocol stack 215
Figure 162 Address allocation procedure 217
Figure 163 IP host protocol address information binary format 218
Figure 164 KNXnet/IP device endpoint 221
Figure 165 PID_PROJECT_INSTALLATION_ID 222
Figure 166 Binary format of KNXnet/IP device management CRI 230
Figure 167 Binary format of KNXnet/IP device management CRD 230
Figure 168 Binary format of DEVICE_CONFIGURATION_REQUEST frame 231
Figure 169 Binary format of DEVICE_CONFIGURATION_ACK frame 232
Figure 170 Tunnel connection in KNXnet/IP server and KNX single address 235
Figure 171 Tunnel CRI binary format 237
Figure 172 Tunnel CRD binary format 238
Figure 173 Tunnel connection header binary format 238
Figure 174 TUNNELLING_REQUEST frame binary format 239
Figure 175 TUNNELING_ACK frame binary format 240
Figure 176 KNX group datagram routing 242
Figure 177 KNXnet/IP group datagram routing 242
Figure 178 Mixed topology (unexpected subnet addressing) 243
Figure 179 Hybrid topology (expected subnet address assignment) 244
Figure 180 ROUTING_INDICATION frame binary format 248
Figure 181 ROUTING_LOST_MESSAGE frame binary format 249
Figure 182 Secure communication between a secure two-way transmitter and an authorized two-way receiver 251
Figure 183 Secure communication between a secure two-way transmitter and a two-way receiver requiring authorization and confidentiality 252
Figure 184 HBES data security location in the stack 254
Figure 185 The location of S-AL in the application layer 256
Figure 186 Security APDU (taking TP1 as an example) 257
Figure 187 B0 format 258
Figure 188 Format of the field TPCI/APCISec in B0 258
Figure 189 Ctrj format 258
Figure 190 Use only authorized security data (taking TP1 as an example) 259
Figure 191 Security data with authorization and confidentiality 260
Figure 192 Format of encrypted secure APDU 262
Figure 193 Security Control Field 263
Figure 194 Tool Access 263
Figure 195 Serial number format 265
Figure 196 S-A_Sync_Req-PDUs format (e.g. SCF setup with tool key and SBC) 266
Figure 197 S-A_Sync_Res-PDU format (e.g. SCF setup with tool key and SBC) 268
Figure 198 Application layer interaction of non-remotely confirmed services 271
Figure.199 Application layer interaction of remote confirmation service 271
Figure.200 Processing T_Data_Group.ind 273 through S-AL
Figure.201 Processing T_Data_Group.req through S-AL 274
Figure 202 Processing T_Data_Tag_Group.ind 275 through S-AL
Figure 203 S-AL processes T_Data_Tag_Group.req 276 via S-AL
Figure 204 Processing T_Data_Individual.ind/.con and T_Data_Connected.ind/.con via S-AL 277
Figure 205 Processing T_Data_Individual.req and T_Data_Connected.req via S-AL (Informative) 278
Figure 206 Many links with different licenses resulting in a large amount of definition data 281
Figure 207 The introduction of roles reduces the number of different permission definitions for each DP 282
Figure 208 Example of a point-to-point key table 283
Figure 209 General schematic diagram of HBES network service interface 288
Figure 210 Overall architecture 289
Figure 211 Abstract model 290
Figure 212 Metamodel of entities, tags, and tag/value pairs 292
Figure 213 Entity, label/value pair and label modeling example 292
Figure 214 HBES information model example 300
Figure 215 Device read request 301
Figure 216 Device object response 302
Figure 217 Data point read request 302
Figure 218 Response 303 of the data point object
Figure 219 Installation Agreement 305
Figure 220 Device Agreement 305
Figure 221 DPST9.001 Agreement 306
Figure 222 Example of function block type agreement 306
Figure 223 Example of parameter type agreement 307
Figure 224 Example of installation instance 307
Figure 225 Example of enumeration object 307
Figure 226 HBES network interface object tree 308
Figure 227 Read Transaction Processing 310
Figure 228 Write transaction processing 310
Figure 229 Calling transaction processing 311
Figure 230 Gateway Profile 314
Figure 231 Structure example of MAU 316
Figure 232 Signal Code 318
Figure 233 Idealized overlap of 105.6kHz and 115.2kHz 318
Figure 234 PL inductive coupling line example 319
Figure 235 Typical PL topology example 319
Figure 236 Character 321
Figure 237 Data message structure 321
Figure 238 Confirmation frame structure 321
Figure 239 PL110 generation matrix 322
Figure 240 Operation of Galois field GF2 323
Figure 241 Three-phase system 323
Figure 242 Domain address 324
Figure 243 Single address 324
Figure 244 Group address 325
Figure 245 Format 1s, frame field 325 with standard field name abbreviations
Figure 246 Format 1s, L_Data_Standard request frame format 326
Figure 247 Control field 326
Figure 248 Check octet 327
Figure 249 Frame field 328 with standard field name abbreviations
Figure 250 Format 1e, L_Data_Extended request frame format 328
Figure 251 Extended Control Field 328
Figure 252 Format 2, short confirmation frame format 329
Figure 253 L_Data request frame time frame diagram 331
Figure 254 Complete frame encapsulation (data message) 336
Figure 255 Primitive Overview 336
Figure 256 Frame Field 338 with Standard Field Name Abbreviations
Figure 257 L_Data request standard frame format 338
Figure 258 Control field 338
Figure 259 NPCI field 339
Figure 260 Frame field 340 with standard field name abbreviations
Figure 261 L_Data_Extended request frame format 340
Figure 262 Extended control field 340
Figure 263 Data field in a positive acknowledgement frame (ACK) 341
Figure 264 Complete confirmation frame encapsulation 341
Figure 265 NRZ line coding 344
Figure 266 Character format 345
Figure 267 Transmitter rising and falling edges 346
Figure 268 Repeater maximum switching time 348
Figure 269 TP0 power supply specification 350
Figure 270 Power supply dynamic internal impedance measurement test configuration 351
Figure 271 Falling edge and overcurrent measurement 351
Figure 272 TP0 network with distributed power supply 352
Figure 273 Voltage/current requirements for a node 353
Figure 274 Voltage/current specifications for a complete distributed power supply with 6 to 8 power supply nodes 355
Figure 275 Common part of the frame structure 356
Figure 276 Control field 357
Figure 277 CTRLE field 357
Figure 278 Format 1s, L_Data_Standard frame format 358 with standard field name abbreviations
Figure 279 Format 1e, L_Data_Extended frame format with standard field name abbreviations 358
Figure 280 EFF field 359
Figure 281 Format 2, short confirmation frame format 360
Figure 282 Transmission definition 363
Figure 283 Format 1s, complete L_Data_Standard request frame format 364
Figure 284 Format 1e, complete L_Data_Extended request frame format 364
Figure 285 Logical structure of physical layer type TP1 366
Figure 286 Mapping to octet 366 of serial character
Figure 287 "1" bit structure 367
Figure 288 "0" bit structure 368
Figure 289 Delayed logical "0" 369
Figure 290 Example of two logical "0" overlap 369
Figure 291 Transmission method 372
Figure 292 Transmitter characteristics example 373
Figure 293 Example of TP164 transmitter block diagram 373
Figure 294 Example of TP1256 transmitter block diagram (Ilimit 0.4A) 374
Figure 295 Relationship between frame data and asynchronous signal 375
Figure 296 Relationship between digital signal and serial bit stream 376
Figure 297 Example of dimmer 377
Figure 298 Physical segment 380
Figure 299 Physical segment 380 combined to line
Figure 300 Combined to the line of the domain 381
Figure 301 Network topology 382
Figure 302 Control Field 385
Figure 303 Frame fields with standard field name abbreviations 385
Figure 304 Format 1s, L_Data_Standard frame format 386
Figure 305 Check octet 386
Figure 306 Frame fields 387 with standard frame field abbreviations
Figure 307 Format 1e, L_Data_Extended frame format 387
Figure 308 Extended Control Field 387
Figure 309 Format 3 --- L_Pol_Data request frame format 388
Figure 310 L_Pol_Data response frame structure 388
Figure 311 Format 2 --- Short confirmation frame format 389
Figure 312 Character timing 390
Figure 313 Priority Operation 391
Figure 314 Guarantee of fair access 392
Figure 315 Data link layer state machine 396
Figure 316 Data link layer frame 405
Figure 317 The first data block structure 405
Figure 318 Structure of the second data block in a standard frame 406
Figure 319 Data link layer and network layer flow chart of HBESRFReady repeater 410
Figure 320 RF domain address based on RF repeater (basic flow chart) 411
Figure 321 Medium access algorithm for fast RF channel 412
Figure 322 PRM fast receiver scan sequence 414
Figure 323 Scan sequence 415 for PRM fast and slow receivers
Figure 324 Scanning sequence of NPRM fast receiver 415
Figure 325 Scanning sequence for NPRM fast and slow receivers 416
Figure 326 NPRM low speed receiver scanning sequence 417
Figure 327 Contents of the post-amble message with Ack end 418
Figure 328 General Ack Insertion 419
Figure 329 Ack frame format 419
Figure 330 Time Slot Filling (R2KO) 420
Figure 331 Ack algorithm, sender end 421
Figure 332 Ack algorithm, processing error 421
Figure 333 Ack algorithm, receiver end 422
Figure 334 General Repeater Algorithm 423
Figure 335 HBESRFReady algorithm 424
Figure 336 Fast HBESRFMulti repeater algorithm 424
Figure 337 Low-speed repeater algorithm 425
Figure 338 Communication between HBESRF1.1 and HBESRF1Muti devices 427
Figure 339 Communication between HBESRFReady and HBESRFMuti devices 428
Figure 340 Communication between HBESRFMuti devices and HBESRFMuti devices 428
Figure 341 Data format 455
Figure 342 Topology example 499
Figure 343 HBES installation space (IS) principle 500
Figure 344 HBES installation space layout 501
Figure 345 Example of a general infrastructure for a cabling system in a building 505
Figure 346 Park Infrastructure 506
Figure 347 Building infrastructure 507
Figure 348 Horizontal infrastructure 508
Figure 349 Apartment unit and single dwelling infrastructure 509
Figure 350 Actual location of the installation space in the room 510
Figure 351 Standardized HBES connector 511
Figure A.1 Risk reduction. general concepts517
Figure D.1 Binary format of the SEARCH_REQUEST frame. IP example 536
Figure D.2 Binary format of the SEARCH_RESPONSE frame. IP example 537
Figure D.3 Example of binary format of a KNXnet/IPDESCRIPTION_REQUEST frame 540
Figure D.4 Binary format of DESCRIPTION_RESPONSE frame. IP example 540
Figure D.5 Example of binary format of KNXnet/IPCONNECT_REQUEST frame 544
Figure D.6 Binary format of the CONNECT_RESPONSE frame. IP example 545
Figure D.7 Binary format of the CONNECTIONSTATE_REQUEST frame. IP example 547
Figure D.8 Binary format of a CONNECTIONSTATE_RESPONSE frame. IP example 548
Figure D.9 Binary format of the DISCONNECT_REQUEST frame. IP example 548
Figure D.10 Binary format of the DISCONNECT_RESPONSE frame. IP example 549
Figure D.11 Binary format of the DEVICE_CONFIGURATION_REQUEST frame. Example 550
Figure D.12 Binary format of the DEVICE_CONFIGURATION_ACK frame. Example 550
Figure D.13 Binary format of the TUNNELING_REQUEST frame. Example 551
Figure D.14 Binary format of the TUNNELING_ACK frame. Example 552
Figure D.15 Binary format of the ROUTING_INDICATION frame. Example 553
Figure D.16 Binary format of the ROUTING_LOST_MESSAGE frame. Example 553
Figure F.1 Block diagram of AES-128 with CBC-MAC 562
Figure F.2 AES-CTR mode block diagram 563
Figure H.1 Authentication Procedure 571
Figure I.1 General wiring model 573
Figure I.2 Topology --- Case A 574
Figure I.3 Topology --- Case B 575
Figure J.1 Relationship between building cabling and building comfort performance level 577
Figure K.1 Application/device location 590
Figure L.1 Existing connectors for HBES and mains 593
Table 1 Layer management functions 30
Table 2 General management functions 31
Table 3 Application Management Entity (AME) Function Example 33
Table 4 Connection Type 41
Table 5 Applicable standards for HBES equipment 44
Table 6 Common methods of providing required insulation for protective isolation 45
Table 7 Performance criteria 49
Table 8 Media interface 50
Table 9 General interface, process interface and input/output 50
Table 10 Mains power (220VAC) 51
Table 11 Shell 51
Table 12 Conducted common mode disturbance limits for control lines, signal lines and DC power lines 61
Table 13 Mains terminal disturbance voltage limit 61
Table 14 Requirements for avoiding improper operation and possible implementation methods 70
Table 15 Group object type 74
Table 16 APCI Overview 83
Table 17 Function table 128 of A_MemoryBit_Write service
Table 18 Function table 135 of A_UserMemoryBit_Write service
Table 19 Key and access level association table 142
Table 20 Use of priority 147
Table 21 Connection-oriented state machine actions 172
Table 22 Conversion table --- Type 1 174
Table 23 Conversion table --- Rationalization type 1 176
Table 24 Conversion table --- Type 2 179
Table 25 Conversion table --- Type 3 181
Table 26 KNXnet/IP service types and IP protocols 186
ⅩⅦ
Table 27 KNXnet/IP device class 187
Table 28 Description Type Code 202
Table 29 Connection Type 209
Table 30 Generic CONNECT_RESPONSE status code 211
Table 31 CONNECTIONSTATE_RESPONSE status code 212
Table 32 Host protocol code for IP network 218
Table 33 Attribute Identifier 221
Table 34 Equipment performance 223
Table 35 Equipment performance 225
Table 36 Device Status 225
Table 37 Routing Performance 226
Table 38 KNXnet/IP parameter object attributes 227
Table 39 Device Statistics 229
Table 40 KNXnet/IP device management service type identifier 230
Table 41 Configuration status code 232
Table 42 KNXnet/IP service type identifier for tunneling 237
Table 43 Establishing tunnel 238 on KNX layer
Table 44 Tunnel CONNECT_ACK error code 238
Table 45 KNXnet/IP routing service type identifier 248
Table 46 Security characteristics of HBES layer 254
Table 47 Security Algorithm Identification 263
Table 48 System Broadcast Identifier 264
Table 49 SBC-flag setting in S-A_Data-PDU 264
Table 50 Security whitelist and security blacklist for services 284
Table 51 Security middleware list service 285
Table 52 Safe intermediate list of data points 286
Table 53 Communication Mode for Security Services Received in Broadcast Communication Mode 286
Table 54 Core Tags 293
Table 55 Relationships between core tags 296
Table 56 REST Method 312
Table 57 HBES Network Service Selection 313
Table 58 General requirements for physical layer PL110 315
Table 59 Example of typical cable characteristics 317
Table 60 Power supply of MAU 317
Table 61 Impedance requirements for MAU 319
Table 62 Relationship between error group and error Table 322
Table 63 L_Data request priority 331
ⅩⅧ
Table 64 Parameters for Ph-Data service 337
Table 65 Ph-Service_Class parameter 337
Table 66 Ph-Result value 337
Table 67 Electrical data code 345
Table 68 Transceiver Characteristics --- Transmit Part 346
Table 69 Transceiver Characteristics --- Receiver Part 346
Table 70 Mandatory and optional requirements for physical layer services 347
Table 71 Ph-Result parameters 347
Table 72 TP0 line requirements 348
Table 73 General Hardware Requirements 349
Table 74 Current consumption requirements 349
Table 75 Supply voltage 350
Table 76 Requirements for DPS power supply equipment 352
Table 77 Complete DPS requirements 354
Table 78 Possible cable lengths related to the number of connected DPS devices (for typical cables) 355
Table 79 Frame Priority - IFT 361
Table 80 Acknowledgement wait time, frame retransmission requirements 362
Table 81 Total waiting time, frame retransmission requirements 362
Table 82 System parameters 365 for physical layer types TP1-64 and TP1-256
Table 83 Analog and digital signals of logic "1" 367
Table 84 Analog and digital signals for logic "0" 368
Table 85 Restrictions on characters 370
Table 86 Unit current of standard equipment 371
Table 87 Dynamic requirements of TP164 transmitter 372
Table 88 Dynamic requirements of TP1256 transmitter 373
Table 89 Receiver Requirements 374
Table 90 Bit Encoding Requirements 375
Table 91 Requirements for bit decoding unit 376
Table 92 TP1 cable requirements 377
Table 93 Character encoding requirements 390
Table 94 Character decoding requirements 390
Table 95 Priority order, in descending order of importance 391
Table 96 Compliance Guide 397
Table 97 General requirements for the physical layer of HBESRFReady 398
Table 98 RFReady message structure 398
Table 99 Media Access Time 399
Table 100 HBESRFMulti physical layer wireless channel 400
ⅩⅨ
Table 101 HBESRF channel definition 401 for RF channels F1, F2 and F3
Table 102 HBESRF channel definition 402 for RF channels S1 and S2
Table 103 HBESRFMulti message structure 403
Table 104 HBES serial number RF domain address usage 403
Table 105 HBESCTRL field value 408
Table 106 Media Access Time 411
Table 107 Communication Matrix 413
Table 108 Sending Matrix 417
Table 109 Transmission Matrix 426
Table 110 Bidirectional mode definition 427
Table 111 Result status after each event 470
Table 112 Summary of state machine types and tables 471
Table 113 Load management control address summary 472
Table 114 Loading status control address 478
Table 115 Loading status control address 480
Table 116 Run Status Events and Results Run Status 482
Table 117 Address 483 of operation status control
Table 118 Application and HBES Class Example 502
Table 119 Minimum requirements for installation space functionality 503
Table 120 Standardized HBES connector 511
Table 121 HBES standard cable requirements 512
Table 122 Cable distribution in wiring duct 513
Table A.1 Example of risk categories for unexpected events 518
Table A.2 Explanation of risk categories 518
Table B.1 Hazardous events, sub-events leading to hazardous events and necessary risk reduction measures 519
Table E.1 General constants 555
Table E.2 Service type identifier 555 of the KNXnet/IP core specification
Table E.3 Device Management Service Type Identifier 556
Table E.4 Tunnel service type identifier 556
Table E.5 Routing service type identifier 557
Table E.6 Connection type 557
Table E.7 Common KNXnet/IP error code 558
Table E.8 Generic CONNECT_RESPONSE status code 558
Table E.9 CONNECTIONSTATE_RESPONSE status code 558
Table E.10 Tunnel CONNECT_ACK error code 559
Table E.11 Device Management DEVICE_CONFIGURATION_ACK Status Code 559
Table E.12 Description type code 559
ⅩⅩ
Table E.13 KNX media code 559
Table E.14 Host protocol code 560 for IP network
Table E.15 Timeout constant 560
Table E.16 KNXnet/IP Internet protocol constants 560
Table J.1 Networks that may coexist in a cabling concept 576
Table K.1 Abbreviations used in Tables K.2 to K.14 580
Table K.2 Single-family multi-storey or multi-area villas --- economical and practical type 581
Table K.3 Single-family multi-storey or multi-area villas --- general use type 581
Table K.4 Single-family multi-storey or multi-area villas --- luxury applicable type 582
Table K.5 Apartment---Affordable Type 583
Table K.6 Apartment---Public Applicability 584
Table K.7 Apartment---Luxury Applicable Type 584
Table K.8 Hotel 585
Table K.9 Nursing Home 586
Table K.10 Store 587
Table K.11 Bar-Restaurant 587
Table K.12 Office 588
Table K.13 Recommended application locations in rooms 589
Table K.14 Comfort level (Example 2) 590
Table L.1 Standard connectors for TP type 0 and type 1 for class 1 HBES 592
Table M.1 General requirements 594
Table M.2 Requirements for HBES standard cables 594
ⅩⅩⅠ
Foreword
This document is in accordance with the provisions of GB/T 1.1-2020 "Guidelines for standardization work Part 1.Structure and drafting rules for standardization documents"
Drafting.
This document replaces GB/T 20965-2013 "Control Network HBES Technical Specification Residential and Building Control Systems" and
Compared with GB/T 20965-2013, in addition to structural adjustments and editorial changes, the main technical changes are as follows.
--- Added "HBES safety" (see Section 7.4);
--- Added "Network Services" (see Section 7.5);
--- Added "HBESRF" (see Section 8.3).
Please note that some of the contents of this document may involve patents. The issuing organization of this document does not assume the responsibility for identifying patents.
This document was jointly issued by the National Technical Committee for Standardization of Industrial Process Measurement, Control and Automation (SAC/TC124) and the National Technical Committee for Intelligent Buildings and Residential Buildings (SAC/TC124).
It is jointly under the Technical Committee on Digital Standardization of Residential Areas (SAC/TC426).
This document was drafted by. Mechanical Industry Instrumentation Comprehensive Technical and Economic Research Institute, Beijing Instrumentation Technology Development Co., Ltd., Haige
Electrical Management (Shanghai) Co., Ltd., Guangzhou Vision Intelligent Co., Ltd., Guangzhou Hedong Technology Co., Ltd., Beijing Haian Ruihang Technology Co., Ltd.
Co., Ltd., Zhuhai Huaxun Intelligent Control Technology Co., Ltd., Siemens (China) Co., Ltd., Komanli (Guangdong) Electric Co., Ltd., Nanjing Tiansuo
Automation Control Systems Co., Ltd., Taichuang Technology Co., Ltd.
The main drafters of this document are. Wang Linkun, Zheng Qiuping, Wang Jun, Wang Zhou, Du Jialin, Zhu Xiangjun, He Hairong, Gao Wei, Wu Yuanfu, Ye Minli,
Hu Jingqun, Lu Jin, Fang Ming, Shen Pu, Yu Zhipeng, and Song Xiaoming.
The previous versions of this document and the documents it replaces are as follows.
---Published as GB /Z 20965-2007 in.2007;
---First revised in.2013 to GB/T 20965-2013;
---This is the second revision.
ⅩⅩⅡ
Introduction
The technical content specified in this document is also called KNX technology, which originated in Europe and is mainly used in the field of residential and building control.
A distributed bus control technology.
Note 1.KNX technology is derived from three bus control technologies used in homes and buildings, namely EIB, Batibus and EHS.
tionBus, European installation bus) is its technical main body.
Note 2.The technical content specified in this document is part of KNX technology. Other technical contents, such as application description, communication rules and interoperability regulations, are not included in this document.
Etc., refer to the relevant technical documents of the KNX Association.
Note 3.HBES is the name used by KNX technology during the standardization process. KNX is used uniformly in the market and technology promotion process.
This document describes a distributed bus system based on event control, which mainly consists of the following parts.
---System overview.
It mainly describes three aspects. system architecture, general technical requirements and product functional safety requirements.
Characteristics and architecture; defines residential and building electronic systems based on safety extra low voltage (SELV) and protective extra low voltage (PELV)
General technical requirements for HBES, including cabling and topology, electrical and functional safety, environmental conditions and failure and specific HBES installations
Behavior under regulatory circumstances; specifies general functional safety requirements for HBES products and systems.
---Application characteristics.
The application structure and the first type of HBES user process are mainly described. The basic concept of user process related to the application is given;
The structure and function of the server side, which is used to form the interface objects and their data structures between the application layer and the application and management; define the application
The data structure of the application interface layer and each application interface layer object is defined, and its functions are specified.
---Media independent layer.
This paper mainly describes the common parts of the application layer, transport layer, network layer and data link layer of Class 1 HBES based on twisted pair and power line.
The KNX protocol is integrated on the Internet Protocol (IP), namely KNXnet/IP.
The common part of HBES application layer, transport layer, network layer and data link layer specifies the application layer, physical layer and data link layer in the process of HBES use.
The services and protocols of the data link layer, network layer and transport layer, as well as the services and interfaces provided to the user process; KNXnet/IP specification
The HBES security protocol specifies the standard protocol used by KNX devices connected to the IP network; the HBES security protocol specifies the HBES data security protocol; web
Service defines the network interface protocol specification.
---Medium dependent layer.
This paper mainly describes the Class 1 HBES power line and the twisted pair based on the Class 1 HBES network. It specifies two types of Class 1 power lines.
PL110 and PL132 provide the necessary and optional requirements for the media-specific physical layer and data link layer; specify the two-pair cable of Category 1 HBES
The HBESRF specifies the mandatory and optional requirements for the media-specific physical layer and data link layer of different types of TP0 and TP1;
Protocol specifications.
---System management.
The basic principles of network management and device management are given, and the interaction between management clients and management servers is standardized to achieve device configuration.
Specifies the communication requirements between the management client and the management server.
---Product conformity assessment.
It defines the criteria and standards for functional compliance testing and evaluation of HBES products and specifies the general compliance evaluation of communication protocols.
The standard for HBES product and/or system conformity assessment is given in the standard.
---Installation requirements.
It specifies the installation requirements of HBES; provides general rules for HBES design, engineering and wiring system installation; specifies the
The rules for parallel laying of HBES1 category wiring and other networks.
HBES Technical Specifications for Residential and Control Networks
Building Control Systems
1 Scope
This document establishes the concept of an event-based distributed bus system (Home and Building Electronic System, HBES)
The overall structure of HBES was established, and the management procedures for HBES were formulated, which stipulated the requirements for the medium-independent layer and the medium-dependent layer, product compliance testing and evaluation.
Criteria and standards for assessment and installation requirements.
This document applies to the design, manufacture, integration, installation and maintenance of automation control systems and products, especially to residential and building control systems.
System field.
2 Normative references
The contents of the following documents constitute essential clauses of this document through normative references in this document.
For referenced documents without a date, only the version corresponding to that date applies to this document; for referenced documents without a date, the latest version (including all amendments) applies to
This document.
GB/T 2423.1 Environmental testing for electric and electronic products Part 2.Test methods Test A. Low temperature
GB/T 2423.2 Environmental testing for electric and electronic products Part 2.Test methods Test B. High temperature
GB/T 2423.3 Environmental testing Part 2.Test method Test Cab. Steady state damp heat test
GB/T 2423.4 Environmental testing for electric and electronic products Part 2.Test method Test Db. Cyclic damp heat (12h 12h cycle)
GB/T 2423.5 Environmental testing Part 2.Test method Test Ea and guidance. Impact
GB/T 2423.10 Environmental testing Part 2.Test methods Test Fc. Vibration (sinusoidal)
GB/T 2423.22 Environmental testing Part 2.Test method Test N. Temperature change
GB/T 4798.3 Classification of environmental conditions Classification of environmental parameter groups and their severity classification Part 3.Climate-protected locations
Fixed use
GB/T 5023.1 Polyvinyl chloride insulated cables with rated voltage up to and including 450/750V Part 1.General requirements
GB/T 5023.2 Thermoplastic insulated cables with rated voltage up to and including 450/750V Part 2.Test methods
GB/T 7289-2017 Reference conditions for reliability failure rate of electrical components and stress model for failure rate conversion
GB/T 9387.1 Information technology Open Systems Interconnection Basic Reference Model Part 1.Basic Model
GB/T 16895.3 Low voltage electrical installations Part 5-54.Selection and installation of electrical equipment Grounding arrangements and protective conductors
GB/T 16895.6 Low voltage electrical installations Part 5-52.Selection and installation of wiring systems for electrical equipment
GB/T 16895.21-2020 Low voltage electrical installations Part 4-41.Safety protection Protection against electric shock
GB/T 16935.1-2023 Insulation coordination for equipment in low-voltage power supply systems Part 1.Principles, requirements and tests
GB/T 17045-2020 Common parts for electric shock protection devices and equipment
GB/T 17625.2 Electromagnetic compatibility limits for equipment with a rated current of ≤16A per phase and unconditionally connected to the public low-voltage power supply
Limitation of voltage changes, voltage fluctuations and flickers generated in the system
|