Partners save 15% on every standard

Valid

GB/T 20965-2025Control network HBES technical specification — Home and building control system (English PDF)

控制网络HBES技术规范住宅和楼宇控制系统

Open the GB/T 20965-2025 preview as PDF

Preview — first pages of GB/T 20965-2025 (full document: 578 pages)

This is a limited preview

Buy now to download the full PDF (578 pages)

Issued by

SAMR; SAC

Level / Type

National · Recommended

Issue date

February 28, 2025

Implementation date

September 1, 2025

Scope

GB/T 20965-2025 is the English-translated version of 控制网络HBES技术规范住宅和楼宇控制系统.

GB/T 20965-2025 is the Chinese national standard covering the bus that ties a building's controls into one network — the HBES reference model, the wiring and bus power, the electromagnetic compatibility and the functional safety of products, the application layer with its group and interface objects, the KNXnet over IP carriage, the power line, twisted pair and radio frequency media, and the management procedures that give a device its individual address and scan the network for it. At 347,000 words, one of the largest documents in the catalogue. Issued on 28 February 2025, it has been in force since 1 September 2025, replacing GB/T 20965-2013.

Document preview — GB/T 20965-2025

National Standard of the People's Republic of China

ICS: 25.040
Classification: N 10
Replacing: GB/T 20965-2013

Issued by: State Administration for Market Regulation; Standardization Administration of the PRC

PrefaceXXI
IntroductionXXII
1 Scope1
2 Normative references1
3 Terms and definitions3
4 Abbreviations1824
5 System24
5.1 Architecture24
5.1.1 Overview24
5.1.2 HBES reference model24
5.1.3 Reference points and functional groups34
5.1.4 Interface standardization of specific reference points36
5.1.5 System Characteristics39
5.2 General technical requirements42
5.2.1 Overview42
5.2.2 Topology, wiring and power supply for devices connected to twisted pair or coaxial media42
5.2.3 Security43
5.2.4 Environmental conditions47
5.2.5 Electromagnetic compatibility requirements for equipment connected to twisted pair or coaxial cable48
5.2.6 Reliability64
5.3 General functional safety requirements for HBES products64
5.3.1 General64
5.3.2 General requirements64
5.3.3 Functional safety requirements66
6 Application Features71
6.1 Application Structure71
6.1.1 Overview71
6.1.2 Application Structure71
6.2 Type 1 HBES User Process72
6.2.1 Overview72
6.2.2 Object Model72
6.2.3 Group Object Server73
6.2.4 Interface Object Server77
7 Dielectric Independent Layer81
7.1 Type 1 HBES application layer81
7.1.1 Overview81
7.1.2 Application layer services81
7.1.3 Application Layer Protocol Data Unit (APDU)82
7.1.4 Application layer services89
7.1.5 Application layer parameters144
7.2 Common parts of transport layer, network layer and data link layer of Class 1 HBES144
7.2.1 Overview144
7.2.2 Requirements for the Media-Independent Data Link Layer144
7.2.3 Network Layer Requirements152
7.2.4 Transport layer requirements161
7.3 KNXnet/IP communication184
7.3.1 Overview184
7.3.2 Requirement185
7.4 HBES Safety250
7.4.1 General Introduction250
7.4.2 Norm255
7.5 Network Services287
7.5.1 General Principles287
7.5.2 Introduction to General Technology of HBES Network Services287
7.5.3 Overview288
7.5.4 HBES Information Model290
7.5.5 HBES Network Interface OBIX301
7.5.6 HBES Gateway OBIX311
7.5.7 Gateway Profile312
8 Medium and medium-related layers315
8.1 Class 1 HBES Power Line315
8.1.1 Overview315
8.1.2 Requirements for Class 1 HBES, Power Line PL110315
8.1.3 Requirements for Class 1 HBES, Power Line PL132334
8.2 Twisted Pair Cables for Class 1 HBES Networks344
8.2.1 Overview344
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 HBESRF397
8.3.1 General397
8.3.2 HBESRF Physical Layer397
8.3.3 Physical Layer 400 of HBESRFMulti403
8.3.4 HBESRF Data Link Layer403
8.3.5 Compatibility between HBESReady and HBESMulti427
9 Management Regulations428
9.1 Overview428
9.2 Network Management Procedures429
9.2.1 General Principles429
9.2.2 NM_IndividualAddress_Read429
9.2.3 NM_IndividualAddress_Write430
9.2.4 NM_SerialNumberDefaultIA_Scan432
9.2.5 NM_IndividualAddress_SerialNumber_Read433
9.2.6 NM_IndividualAddress_SerialNumber_Write434
9.2.7 NM_DomainAddress_Read435
9.2.8 NM_DomainAddress_Write435
9.2.9 NM_DomainAddress_Scan438
9.2.10 NM_Router_Scan438
9.2.11 NM_SubnetworkDevices_Scan439
9.2.12 NM_SubnetworkAddress_Read440
9.2.13 NM_IndividualAddress_Reset440
9.2.14 NM_IndividualAddress_Scan441
9.2.15 NM_IndividualAddress_Check442
9.2.16 NM_IndividualAddress_Check_LocalSubnetwork443
9.2.17 NM_GroupAddress_Check444
9.2.18 NM_FunctionalBlock_Scan445
9.3 Equipment Management Procedures445
9.3.1 General Principles445
9.3.2 General Exception Handling446
9.3.3 DM_Connect446
9.3.4 DM_Disconnect447
9.3.5 DM_Authorize448
9.3.6 DM_SetKey449
9.3.7 DM_Restart450
9.3.8 DM_Delay451
9.3.9 DM_IndividualAddressRead451
9.3.10 DM_IndividualAddressWrite451
9.3.11 DM_DomainAddressRead451
9.3.12 DM_DomainAddressWrite451
9.3.13 DM_ProgMode_Switch452
9.3.14 DM_GroupObject_Link_Read452
9.3.15 DM_GroupObject_Link_Write453
9.3.16 DM_MemWrite454
9.3.17 DM_MemVerify457
9.3.18 DM_MemRead458
9.3.19 DM_UserMemWrite459
9.3.20 DM_UserMemVerify462
9.3.21 DM_UserMemRead463
9.3.22 DM_InterfaceObjectWrite464
9.3.23 DM_InterfaceObjectVerify466
9.3.24 DM_InterfaceObjectRead467
9.3.25 DM_InterfaceObjectScan469
9.3.26 DM_LoadStateMachineWrite470
9.3.27 DM_LoadStateMachineVerify478
9.3.28 DM_LoadStateMachineRead480
9.3.29 DM_RunStateMachineWrite482
9.3.30 DM_RunStateMachineVerify483
9.3.31 DM_RunstateMachineRead485
9.3.32 DM_LCSlaveMemWrite487
9.3.33 DM_LCSlaveMemVerify489
9.3.34 DM_LCSlaveMemRead490
9.3.35 DM_LCExtMemWrite491
9.3.36 DM_LCExtMemVerify492
9.3.37 DM_LCExtMemRead493
9.3.38 DM_LCExtMemOpen494
9.3.39 DM_LCRouteTableStateWrite495
9.3.40 DM_LCRouteTableStateVerify496
9.3.41 DM_LCRouteTableStateRead497
10 Product Conformity Assessment498
10.1 Overview498
10.2 Applicable Standards498
10.2.1 Overview498
10.2.2 Protocol498
10.2.3 Electrical safety498
10.2.4 Electromagnetic Compatibility (EMC)498
10.2.5 Environment498
10.2.6 Functional Safety499
11 Installation Requirements - General Requirements for Category 1 HBES Twisted Pair Cabling499
11.1 Overview499
11.2 Systems and Cabling499
11.3 Wiring Model and General Requirements500
11.3.1 Segment connection, generally requires500
11.3.2 Coexistence of HBES Control Bus, Broadband Multimedia and Mains Power501
11.4 Infrastructure Requirements502
11.4.1 General502
11.4.2 Preliminary Configuration of Installation Space505
11.5 Connector 510 for Category 1 HBES twisted pair cable512
11.6 Cable and installation accessories requirements512
11.6.1 Channel and Link Performance512
11.6.2 TP cable characteristics512
11.6.3 Annex513
11.7 Electrical safety and functional safety514
11.7.1 Electrical safety514
11.7.2 Functional insulation of bus segments515
11.7.3 Functional Safety515
11.8 EMC515
11.9 Grounding and shielding grounding for lightning protection516
11.10 Fire reaction and fire resistance requirements516
11.11 Environmental aspects516
11.12 Management and Documentation516
Appendix A (informative) Example of method for determining safety integrity level517
Appendix B (Informative) Development of Hazard and Essential Functional Safety Requirements519
Appendix C (Informative) Example of a transport layer connection-oriented state machine state diagram526
Appendix D (Informative) Example of binary format of KNX/IP frame536
Appendix E (Informative) Code Table555
Appendix F (Informative) Application of CCM561
Appendix G (Informative) Example - Complete Encoding of HBES Security APDU565
Appendix H (Informative) Certification571
Appendix I (Informative) Wiring Model572
Appendix J (Informative) Preliminary Deployment and Planning Aspects576
Appendix K (informative) Performance of building comfort levels580
Appendix L (informative) Standard connectors for TP type 0 and type 1 of class 1 HBES592
Appendix M (Informative) Cable/Channel and Link Requirements594
References596
Figure 1 Single address6
Figure 2 Group Address8
Figure 3 Overview of HBES reference model25
Figure 4 HBES application process28
Figure 5 HBES device application process structure28
Figure 6 HBES device application process model29
Figure 7 User process link29
Figure 8 Communication resource management31
Figure 9 Communication resource user interface32
Figure 10 Example of device management function using common interface32
Figure 11 Application process management33
Figure 12 User interface of application process resources33
Figure 13 Reference points and functional groups34
Figure 14 Example of multiple reference points facing away from the network medium34
Figure 15 Example of multiple reference points for network media35
Figure 16 Gateways between different network segments35
Figure 17 Reference point hierarchy35
Figure 18 Standard interface position36
Figure 19 Symbols used in Figures 20 to 2236
Figure 20 Single-wire connection37
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 connected37
Figure 23 General interface location38
Figure 24 Process interface location38
Figure 25 HBES interactive application40
Figure 26 Geographical distribution zones in buildings40
Figure 27 Power supply unit 43 of HBES equipment Figure 28 Protective isolation of separately installed HBES equipment46
Figure 29 Protective isolation of adjacently installed HBES equipment46
Figure 30 Validity range of this document49
Figure 31 Testing the mains connection of the power supply unit52
Figure 32 Testing the bus connection of the power supply unit53
Figure 33 Testing the mains connection of bus equipment53
Figure 34 Testing the media interface of the bus device53
Figure 35 Testing the general interface, process interface and input/output connections of the bus device54
Figure 36 Testing the mains connection of the power supply unit54
Figure 37 Power supply unit bus connection test55
Figure 38 Testing the mains connection of the HBES device55
Figure 39 Media interface test of HBES equipment56
Figure 40 Testing the common interface, process interface and input/output connections of the HBES device56
Figure 41 Electrostatic discharge57
Figure 42 Test in an anechoic chamber57
Figure 43 Top view58
Figure 44 Side view 158
Figure 45 Side view 258
Figure 46 Side view 359
Figure 47 Test arrangement for GB/T 17626.6 test59
Figure 48 Example of test arrangement in an anechoic chamber60
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 cables62
Figure 54 Test arrangement for conducted disturbance voltage on mains terminals63
Figure 55 Test arrangement for common mode noise current test on bus cable63
Figure 56 Test arrangement for voltage dips and short interruptions64
Figure 57 Application structure71
Figure 58 Possible information flow72
Figure 59 User process model73
Figure 60 Data structure of group object73
Figure 61 Reading group object value76
Figure 62 Receiving a request to read the value of a group object76
Figure 63 Write group object value77
Figure 64 Receive group object value update77
Figure 65 The structure of the interface object78
Figure 66 Message flow for A_PropertyValue_Read service79
Figure 70 Application layer interaction of remote authentication service82
Figure 71 APDU Example82
Figure 72 ASAP is mapped to TSAP example89
Figure 73 TSAP mapping to ASAP89
Figure 74 Processing requests and responses89
Figure 75 Message flow of A_Group_Value_Read service90
Figure 76 A_GroupValue_Read-PDU Example90
Figure 77 Example of A_GroupValue_Response-PDU with ASAP data length greater than 6 bits91
Figure 78 Example of A_GroupValue_Response-PDU with ASAP data length equal to or less than 6 bits91
Figure 79 Message flow of A_Group_Value_Write service92
Figure 80 Example of A_GroupValue_Write-PDU with ASAP data length greater than 6 bits93
Figure 81 Example of A_GroupValue_Write-PDU with ASAP data length equal to or less than 6 bits93
Figure 82 A_IndividualAddress_Write-PDU Example94
Figure 83 A_IndividualAddress_Read-PDU Example95
Figure 84 A_IndividualAddress_Response-PDU Example95
Figure 85 A_IndividualAddressSerialNumber_Read service message flow97
Figure 86 A_IndividualAddressSerialNumber_Read-PDU Example97
Figure 87 A_IndividualAddressSerialNumber_Response-PDU Example98
Figure 88 A_IndividualAddressSerialNumber_Write-PDU Example100
Figure 89 A_ServiceInformation_Indication_Write-PDU Example101
Figure 90 A_DomainAddress_Write-PDU102
Figure 91 A_DomainAddress_Read-PDU Example103
Figure 92 A_DomainAddress_Response-PDU Example104
Figure 93 A_DomainAddressSelective_Read-PDU Example105
Figure 94 A_NetworkParameter_Read-PDU Example106
Figure 95 A_NetworkParameter_Response-PDU Example107
Figure 96 A_NetworkParameter_Write-PDU Example109
Figure 97 A_PropertyValue_Read-PDU Example110
Figure 98 A_PropertyValue_Response-PDU Example111
Figure 99 A_PropertyValue_Write-PDU Example113
Figure 100 A_PropertyDescription_Read-PDU Example115
Figure 101 A_PropertyDescription_Response-PDU Example115
Figure 102 A_DeviceDescriptor_Read-PDU Example117
Figure 103 A_DeviceDescriptor_Response-PDU Example117
Figure 104 A_Link_Read service message flow119
Figure 105 A_Link_Read-PDU Example119
Figure 106 A_Link_Response-PDU Example119
Figure 107 A_Link_Write service message flow120
Figure 108 A_Link_Write-PDU121
Figure 109 A_ADC_Read-PDU Example122
Figure 110 A_ADC_Response-PDU Example122
Figure 111 A_Memory_Read-PDU Example124
Figure 112 A_Memory_Response-PDU Example124
Figure 113 A_Memory_Write-PDU Example126
Figure 114 A_MemoryBit_Write-PDU129
Figure 115 A_UserMemory_Read-PDU Example131
Figure 116 A_UserMemory_Response-PDU131
Figure 117 A_UserMemory_Write-PDU133
Figure 118 A_UserMemoryBit_Write-PDU Example136
Figure 119 A_UserManufacturerInfo_Read-PDU Example138
Figure 120 A_UserManufacturerInfo_Response-PDU138
Figure 121 A_Restart-PDU Example140
Figure 122 A_Authorize_Request-PDU Example141
Figure 123 A_Authorize_Response-PDU Example141
Figure 124 A_Key_Write-PDU Example143
Figure 125 A_Key_Response-PDU Example143
Figure 126 Data link layer interaction145
Figure 127 Exchange of Figure L_Data service primitives146
Figure 128 Frame_format parameter148
Figure 129 Coding of extended frame format149
Figure 130 Network layer interconnection (not used for bridges or routers)153
Figure 131 Basic functions of a router or bridge153
Figure 132 Example of NPDU format154
Figure 133 Transport layer interaction161
Figure 134 TPDU format example162
Figure 135 Transmission Control Field162
Figure 136 Device type and configuration example184
Figure 137 Binary format of KNXnet/IP frame190
Figure 138 KNXnet/IP header binary format190
Figure 139 KNXnet/IP server endpoint configuration example191
Figure 140 Discovery Procedure192
Figure 141 Establishing data connection194
Figure 142 General connection header194
Figure 143 KNX project with multiple installations197
Figure 144 KNXnet/IP message header198
Figure 149 Supported Service Family DIB205
Figure 150 Manufacturer Data DIB205
Figure 151 Binary format of SEARCH_REQUEST frame206
Figure 152 Binary format of SEARCH_RESPONSE frame207
Figure 153 Binary format of DESCRIPTION_REQUEST frame208
Figure 154 Binary format of DESCRIPTION_RESPONSE frame209
Figure 155 Binary format of CONNECT_REQUEST frame210
Figure 156 Binary format of CONNECT_RESPONSE frame211
Figure 157 Binary format of CONNECTIONSTATE_REQUEST frame212
Figure 158 Binary format of CONNECTIONSTATE_RESPONSE frame213
Figure 159 Binary format of DISCONNECT_REQUEST frame214
Figure 160 Binary format of DISCONNECT_RESPONSE frame214
Figure 161 IP protocol stack215
Figure 162 Address allocation procedure217
Figure 163 IP host protocol address information binary format218
Figure 164 KNXnet/IP device endpoint221
Figure 165 PID_PROJECT_INSTALLATION_ID222
Figure 166 Binary format of KNXnet/IP device management CRI230
Figure 167 Binary format of KNXnet/IP device management CRD230
Figure 168 Binary format of DEVICE_CONFIGURATION_REQUEST frame231
Figure 169 Binary format of DEVICE_CONFIGURATION_ACK frame232
Figure 170 Tunnel connection in KNXnet/IP server and KNX single address235
Figure 171 Tunnel CRI binary format237
Figure 172 Tunnel CRD binary format238
Figure 173 Tunnel connection header binary format238
Figure 174 TUNNELLING_REQUEST frame binary format239
Figure 175 TUNNELING_ACK frame binary format240
Figure 176 KNX group datagram routing242
Figure 177 KNXnet/IP group datagram routing242
Figure 178 Mixed topology (unexpected subnet addressing)243
Figure 179 Hybrid topology (expected subnet address assignment)244
Figure 180 ROUTING_INDICATION frame binary format248
Figure 181 ROUTING_LOST_MESSAGE frame binary format249
Figure 182 Secure communication between a secure two-way transmitter and an authorized two-way receiver251
Figure 183 Secure communication between a secure two-way transmitter and a two-way receiver requiring authorization and confidentiality252
Figure 184 HBES data security location in the stack254
Figure 185 The location of S-AL in the application layer256
Figure 186 Security APDU (taking TP1 as an example)257
Figure 187 B0 format258
Figure 188 Format of the field TPCI/APCISec in B0258
Figure 189 Ctrj format258
Figure 190 Use only authorized security data (taking TP1 as an example)259
Figure 191 Security data with authorization and confidentiality260
Figure 192 Format of encrypted secure APDU262
Figure 193 Security Control Field263
Figure 194 Tool Access263
Figure 195 Serial number format265
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 services271
Figure.199 Application layer interaction of remote confirmation service271
Figure.200 Processing T_Data_Group.ind 273 through S-AL Figure.201 Processing T_Data_Group.req through S-AL274
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 data281
Figure 207 The introduction of roles reduces the number of different permission definitions for each DP282
Figure 208 Example of a point-to-point key table283
Figure 209 General schematic diagram of HBES network service interface288
Figure 210 Overall architecture289
Figure 211 Abstract model290
Figure 212 Metamodel of entities, tags, and tag/value pairs292
Figure 213 Entity, label/value pair and label modeling example292
Figure 214 HBES information model example300
Figure 215 Device read request301
Figure 216 Device object response302
Figure 217 Data point read request302
Figure 218 Response 303 of the data point object Figure 219 Installation Agreement305
Figure 220 Device Agreement305
Figure 221 DPST9.001 Agreement306
Figure 222 Example of function block type agreement306
Figure 223 Example of parameter type agreement307
Figure 224 Example of installation instance307
Figure 225 Example of enumeration object307
Figure 226 HBES network interface object tree308
Figure 227 Read Transaction Processing310
Figure 228 Write transaction processing310
Figure 229 Calling transaction processing311
Figure 230 Gateway Profile314
Figure 231 Structure example of MAU316
Figure 232 Signal Code318
Figure 233 Idealized overlap of 105.6kHz and 115.2kHz318
Figure 234 PL inductive coupling line example319
Figure 235 Typical PL topology example319
Figure 236 Character321
Figure 237 Data message structure321
Figure 238 Confirmation frame structure321
Figure 239 PL110 generation matrix322
Figure 240 Operation of Galois field GF2323
Figure 241 Three-phase system323
Figure 242 Domain address324
Figure 243 Single address324
Figure 244 Group address325
Figure 245 Format 1s, frame field 325 with standard field name abbreviations Figure 246 Format 1s, L_Data_Standard request frame format326
Figure 247 Control field326
Figure 248 Check octet327
Figure 249 Frame field 328 with standard field name abbreviations Figure 250 Format 1e, L_Data_Extended request frame format328
Figure 251 Extended Control Field328
Figure 252 Format 2, short confirmation frame format329
Figure 253 L_Data request frame time frame diagram331
Figure 254 Complete frame encapsulation (data message)336
Figure 255 Primitive Overview336
Figure 256 Frame Field 338 with Standard Field Name Abbreviations Figure 257 L_Data request standard frame format338
Figure 258 Control field338
Figure 259 NPCI field339
Figure 260 Frame field 340 with standard field name abbreviations Figure 261 L_Data_Extended request frame format340
Figure 262 Extended control field340
Figure 263 Data field in a positive acknowledgement frame (ACK)341
Figure 264 Complete confirmation frame encapsulation341
Figure 265 NRZ line coding344
Figure 266 Character format345
Figure 267 Transmitter rising and falling edges346
Figure 268 Repeater maximum switching time348
Figure 269 TP0 power supply specification350
Figure 270 Power supply dynamic internal impedance measurement test configuration351
Figure 271 Falling edge and overcurrent measurement351
Figure 272 TP0 network with distributed power supply352
Figure 273 Voltage/current requirements for a node353
Figure 274 Voltage/current specifications for a complete distributed power supply with 6 to 8 power supply nodes355
Figure 275 Common part of the frame structure356
Figure 276 Control field357
Figure 277 CTRLE field357
Figure 280 EFF field359
Figure 281 Format 2, short confirmation frame format360
Figure 282 Transmission definition363
Figure 283 Format 1s, complete L_Data_Standard request frame format364
Figure 284 Format 1e, complete L_Data_Extended request frame format364
Figure 285 Logical structure of physical layer type TP1366
Figure 286 Mapping to octet 366 of serial character Figure 287 "1" bit structure367
Figure 288 "0" bit structure368
Figure 289 Delayed logical "0"369
Figure 290 Example of two logical "0" overlap369
Figure 291 Transmission method372
Figure 292 Transmitter characteristics example373
Figure 293 Example of TP164 transmitter block diagram373
􀃼 Figure 294 Example of TP1256 transmitter block diagram (Ilimit 0.4A)374
Figure 295 Relationship between frame data and asynchronous signal375
Figure 296 Relationship between digital signal and serial bit stream376
Figure 297 Example of dimmer377
Figure 298 Physical segment380
Figure 299 Physical segment 380 combined to line Figure 300 Combined to the line of the domain381
Figure 301 Network topology382
Figure 302 Control Field385
Figure 303 Frame fields with standard field name abbreviations385
Figure 304 Format 1s, L_Data_Standard frame format386
Figure 305 Check octet386
Figure 306 Frame fields 387 with standard frame field abbreviations Figure 307 Format 1e, L_Data_Extended frame format387
Figure 308 Extended Control Field387
Figure 309 Format 3 --- L_Pol_Data request frame format388
Figure 310 L_Pol_Data response frame structure388
Figure 311 Format 2 --- Short confirmation frame format389
Figure 312 Character timing390
Figure 313 Priority Operation391
Figure 314 Guarantee of fair access392
Figure 315 Data link layer state machine396
Figure 316 Data link layer frame405
Figure 317 The first data block structure405
Figure 318 Structure of the second data block in a standard frame406
Figure 319 Data link layer and network layer flow chart of HBESRFReady repeater410
Figure 320 RF domain address based on RF repeater (basic flow chart)411
Figure 321 Medium access algorithm for fast RF channel412
Figure 322 PRM fast receiver scan sequence414
Figure 323 Scan sequence 415 for PRM fast and slow receivers Figure 324 Scanning sequence of NPRM fast receiver415
Figure 325 Scanning sequence for NPRM fast and slow receivers416
Figure 326 NPRM low speed receiver scanning sequence417
Figure 327 Contents of the post-amble message with Ack end418
Figure 328 General Ack Insertion419
Figure 329 Ack frame format419
Figure 330 Time Slot Filling (R2KO)420
􀃽 Figure 331 Ack algorithm, sender end421
Figure 332 Ack algorithm, processing error421
Figure 333 Ack algorithm, receiver end422
Figure 334 General Repeater Algorithm423
Figure 335 HBESRFReady algorithm424
Figure 336 Fast HBESRFMulti repeater algorithm424
Figure 337 Low-speed repeater algorithm425
Figure 338 Communication between HBESRF1.1 and HBESRF1Muti devices427
Figure 339 Communication between HBESRFReady and HBESRFMuti devices428
Figure 340 Communication between HBESRFMuti devices and HBESRFMuti devices428
Figure 341 Data format455
Figure 342 Topology example499
Figure 343 HBES installation space (IS) principle500
Figure 344 HBES installation space layout501
Figure 345 Example of a general infrastructure for a cabling system in a building505
Figure 346 Park Infrastructure506
Figure 347 Building infrastructure507
Figure 348 Horizontal infrastructure508
Figure 349 Apartment unit and single dwelling infrastructure509
Figure 350 Actual location of the installation space in the room510
Figure 351 Standardized HBES connector511
Figure A.1 Risk reduction. general concepts517 Figure D.1 Binary format of the SEARCH_REQUEST frame. IP example536
Figure D.2 Binary format of the SEARCH_RESPONSE frame. IP example537
Figure D.3 Example of binary format of a KNXnet/IPDESCRIPTION_REQUEST frame540
Figure D.4 Binary format of DESCRIPTION_RESPONSE frame. IP example540
Figure D.5 Example of binary format of KNXnet/IPCONNECT_REQUEST frame544
Figure D.6 Binary format of the CONNECT_RESPONSE frame. IP example545
Figure D.7 Binary format of the CONNECTIONSTATE_REQUEST frame. IP example547
Figure D.8 Binary format of a CONNECTIONSTATE_RESPONSE frame. IP example548
Figure D.9 Binary format of the DISCONNECT_REQUEST frame. IP example548
Figure D.10 Binary format of the DISCONNECT_RESPONSE frame. IP example549
Figure D.11 Binary format of the DEVICE_CONFIGURATION_REQUEST frame. Example550
Figure D.12 Binary format of the DEVICE_CONFIGURATION_ACK frame. Example550
Figure D.13 Binary format of the TUNNELING_REQUEST frame. Example551
Figure D.14 Binary format of the TUNNELING_ACK frame. Example552
Figure D.15 Binary format of the ROUTING_INDICATION frame. Example553
􀃾 Figure D.16 Binary format of the ROUTING_LOST_MESSAGE frame. Example553
Figure F.1 Block diagram of AES-128 with CBC-MAC562
Figure F.2 AES-CTR mode block diagram563
Figure H.1 Authentication Procedure571
Figure I.1 General wiring model573
Figure I.2 Topology --- Case A574
Figure I.3 Topology --- Case B575
Figure J.1 Relationship between building cabling and building comfort performance level577
Figure K.1 Application/device location590
Figure L.1 Existing connectors for HBES and mains593
Table 1 Layer management functions30
Table 2 General management functions31
Table 3 Application Management Entity (AME) Function Example33
Table 4 Connection Type41
Table 5 Applicable standards for HBES equipment44
Table 6 Common methods of providing required insulation for protective isolation45
Table 7 Performance criteria49
Table 8 Media interface50
Table 9 General interface, process interface and input/output50
Table 10 Mains power (220VAC)51
Table 11 Shell51
Table 12 Conducted common mode disturbance limits for control lines, signal lines and DC power lines61
Table 13 Mains terminal disturbance voltage limit61
Table 14 Requirements for avoiding improper operation and possible implementation methods70
Table 15 Group object type74
Table 16 APCI Overview83
Table 20 Use of priority147
Table 21 Connection-oriented state machine actions172
Table 22 Conversion table --- Type 1174
Table 23 Conversion table --- Rationalization type 1176
Table 24 Conversion table --- Type 2179
Table 25 Conversion table --- Type 3181
Table 26 KNXnet/IP service types and IP protocols186
􀃿 XVII Table 27 KNXnet/IP device class187
Table 28 Description Type Code202
Table 29 Connection Type209
Table 30 Generic CONNECT_RESPONSE status code211
Table 31 CONNECTIONSTATE_RESPONSE status code212
Table 32 Host protocol code for IP network218
Table 33 Attribute Identifier221
Table 34 Equipment performance223
Table 35 Equipment performance225
Table 36 Device Status225
Table 37 Routing Performance226
Table 38 KNXnet/IP parameter object attributes227
Table 39 Device Statistics229
Table 40 KNXnet/IP device management service type identifier230
Table 41 Configuration status code232
Table 42 KNXnet/IP service type identifier for tunneling237
Table 43 Establishing tunnel 238 on KNX layer Table 44 Tunnel CONNECT_ACK error code238
Table 45 KNXnet/IP routing service type identifier248
Table 46 Security characteristics of HBES layer254
Table 47 Security Algorithm Identification263
Table 48 System Broadcast Identifier264
Table 49 SBC-flag setting in S-A_Data-PDU264
Table 50 Security whitelist and security blacklist for services284
Table 51 Security middleware list service285
Table 52 Safe intermediate list of data points286
Table 53 Communication Mode for Security Services Received in Broadcast Communication Mode286
Table 54 Core Tags293
Table 55 Relationships between core tags296
Table 56 REST Method312
Table 57 HBES Network Service Selection313
Table 58 General requirements for physical layer PL110315
Table 59 Example of typical cable characteristics317
Table 60 Power supply of MAU317
Table 61 Impedance requirements for MAU319
Table 62 Relationship between error group and error Table322
Table 63 L_Data request priority331
XVIII Table 64 Parameters for Ph-Data service337
Table 65 Ph-Service_Class parameter337
Table 66 Ph-Result value337
Table 67 Electrical data code345
Table 68 Transceiver Characteristics --- Transmit Part346
Table 69 Transceiver Characteristics --- Receiver Part346
Table 70 Mandatory and optional requirements for physical layer services347
Table 71 Ph-Result parameters347
Table 72 TP0 line requirements348
Table 73 General Hardware Requirements349
Table 74 Current consumption requirements349
Table 75 Supply voltage350
Table 76 Requirements for DPS power supply equipment352
Table 77 Complete DPS requirements354
Table 78 Possible cable lengths related to the number of connected DPS devices (for typical cables)355
Table 79 Frame Priority - IFT361
Table 80 Acknowledgement wait time, frame retransmission requirements362
Table 81 Total waiting time, frame retransmission requirements362
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 characters370
Table 86 Unit current of standard equipment371
Table 87 Dynamic requirements of TP164 transmitter372
Table 88 Dynamic requirements of TP1256 transmitter373
Table 89 Receiver Requirements374
Table 90 Bit Encoding Requirements375
Table 91 Requirements for bit decoding unit376
Table 92 TP1 cable requirements377
Table 93 Character encoding requirements390
Table 94 Character decoding requirements390
Table 95 Priority order, in descending order of importance391
Table 96 Compliance Guide397
Table 97 General requirements for the physical layer of HBESRFReady398
Table 98 RFReady message structure398
Table 99 Media Access Time399
Table 100 HBESRFMulti physical layer wireless channel400
Table 104 HBES serial number RF domain address usage403
Table 105 HBESCTRL field value408
Table 106 Media Access Time411
Table 107 Communication Matrix413
Table 108 Sending Matrix417
Table 109 Transmission Matrix426
Table 110 Bidirectional mode definition427
Table 111 Result status after each event470
Table 112 Summary of state machine types and tables471
Table 113 Load management control address summary472
Table 114 Loading status control address478
Table 115 Loading status control address480
Table 116 Run Status Events and Results Run Status482
Table 117 Address 483 of operation status control Table 118 Application and HBES Class Example502
Table 119 Minimum requirements for installation space functionality503
Table 120 Standardized HBES connector511
Table 121 HBES standard cable requirements512
Table 122 Cable distribution in wiring duct513
Table A.1 Example of risk categories for unexpected events518
Table A.2 Explanation of risk categories518
Table B.1 Hazardous events, sub-events leading to hazardous events and necessary risk reduction measures519
Table E.1 General constants555
Table E.2 Service type identifier 555 of the KNXnet/IP core specification Table E.3 Device Management Service Type Identifier556
Table E.4 Tunnel service type identifier556
Table E.5 Routing service type identifier557
Table E.6 Connection type557
Table E.7 Common KNXnet/IP error code558
Table E.8 Generic CONNECT_RESPONSE status code558
Table E.9 CONNECTIONSTATE_RESPONSE status code558
Table E.10 Tunnel CONNECT_ACK error code559
Table E.11 Device Management DEVICE_CONFIGURATION_ACK Status Code559
Table E.12 Description type code559
XX Table E.13 KNX media code559
Table E.14 Host protocol code 560 for IP network Table E.15 Timeout constant560
Table E.16 KNXnet/IP Internet protocol constants560
Table J.1 Networks that may coexist in a cabling concept576
Table K.1 Abbreviations used in Tables K.2 to K.14580
Table K.2 Single-family multi-storey or multi-area villas --- economical and practical type581
Table K.3 Single-family multi-storey or multi-area villas --- general use type581
Table K.4 Single-family multi-storey or multi-area villas --- luxury applicable type582
Table K.5 Apartment---Affordable Type583
Table K.6 Apartment---Public Applicability584
Table K.7 Apartment---Luxury Applicable Type584
Table K.8 Hotel585
Table K.9 Nursing Home586
Table K.10 Store587
Table K.11 Bar-Restaurant587
Table K.12 Office588
Table K.13 Recommended application locations in rooms589
Table K.14 Comfort level (Example 2)590
Table L.1 Standard connectors for TP type 0 and type 1 for class 1 HBES592
Table M.1 General requirements594
Table M.2 Requirements for HBES standard cables594

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

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

GB/T 2423.1

GB/T 2423.2

GB/T 2423.3

GB/T 2423.4

GB/T 2423.5

GB/T 2423.10

GB/T 2423.22

GB/T 4798.3

GB/T 5023.1

GB/T 5023.2

GB/T 7289-2017

GB/T 9387.1

GB/T 16895.3

GB/T 16895.6

GB/T 16895.21-2020

GB/T 16935.1-2023

GB/T 17045-2020

GB/T 17625.2

......
This preview omits tables, figures, formulas and parts of the technical clauses. The complete document — 578 pages — is available in the English PDF.

Referenced standards

Normative references

GB/T 2423.1 · GB/T 2423.2 · GB/T 2423.3 · GB/T 2423.4 · GB/T 2423.5 · GB/T 2423.10 · GB/T 5023.2 · GB/T 7289-2017 · GB/T 9387.1 · GB/T 16895.3 · GB/T 16895.6 · GB/T 16895.21-2020 · GB/T 16935.1-2023 · GB/T 17045-2020 · GB/T 17625.2

How to Buy GB/T 20965-2025

1Add to cart. Click the "Buy GB/T 20965-2025" button on this page. You can add more standards before checkout.
2Checkout. Enter your email and billing details. Payment is processed securely by Stripe (cards, Apple Pay, Google Pay supported).
3Instant delivery (0–9 sec). Delivery is automatic: within seconds of payment you'll receive an email with a secure download link. The link stays valid for 72 hours.
4Invoice included. A tax invoice is attached to the confirmation email. Need a custom invoice? Contact us.