Home Cart Quotation About-Us
www.ChineseStandard.net
SEARCH

GB/T 20965-2025 English PDF

GB/T 20965: Historical versions

Standard IDUSDBUY PDFLead-DaysStandard Title (Description)Status
GB/T 20965-2025RFQ ASK 3 days Control network HBES technical specification - Home and building control system Valid
GB/T 20965-2013RFQ ASK 3 days Control network HBES technical specification -- Home and building control system Valid

Similar standards

GB/T 20438.5   GB/T 20438.4   GB/T 20438.6   GB/T 45510   GB/T 41771.6   

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

Tips & Frequently Asked Questions:

Question 1: How long will the true-PDF of GB/T 20965-2025_English be delivered?

Answer: Upon your order, we will start to translate GB/T 20965-2025_English as soon as possible, and keep you informed of the progress. The lead time is typically 1 ~ 3 working days. The lengthier the document the longer the lead time.

Question 2: Can I share the purchased PDF of GB/T 20965-2025_English with my colleagues?

Answer: Yes. The purchased PDF of GB/T 20965-2025_English will be deemed to be sold to your employer/organization who actually pays for it, including your colleagues and your employer's intranet.

Question 3: Does the price include tax/VAT?

Answer: Yes. Our tax invoice, downloaded/delivered in 9 seconds, includes all tax/VAT and complies with 100+ countries' tax regulations (tax exempted in 100+ countries) -- See Avoidance of Double Taxation Agreements (DTAs): List of DTAs signed between Singapore and 100+ countries

Question 4: Do you accept my currency other than USD?

Answer: Yes. If you need your currency to be printed on the invoice, please write an email to Sales@ChineseStandard.net. In 2 working-hours, we will create a special link for you to pay in any currencies. Otherwise, follow the normal steps: Add to Cart -- Checkout -- Select your currency to pay.

Question 5: Should I purchase the latest version GB/T 20965-2025?

Answer: Yes. Unless special scenarios such as technical constraints or academic study, you should always prioritize to purchase the latest version GB/T 20965-2025 even if the enforcement date is in future. Complying with the latest version means that, by default, it also complies with all the earlier versions, technically.