Already a subscriber? 
MADCAD.com Free Trial
Sign up for a 3 day free trial to explore the MADCAD.com interface, PLUS access the
2009 International Building Code to see how it all works.
If you like to setup a quick demo, let us know at support@madcad.com
or +1 800.798.9296 and we will be happy to schedule a webinar for you.
Security check
Please login to your personal account to use this feature.
Please login to your authorized staff account to use this feature.
Are you sure you want to empty the cart?
IEC 63380-3 Ed. 1.0 en:2025 Standard interface for connecting charging stations to local energy management systems - Part 3 Communication protocol and cybersecurity specific aspects, 2025
- CONTENTS
- FOREWORD
- INTRODUCTION
- 1 Scope
- 2 Normative references
- 3 Terms, definitions, and abbreviated terms [Go to Page]
- 3.1 Terms and definitions
- 3.2 Abbreviated terms
- 4 Overview
- 5 SPINE protocol [Go to Page]
- 5.1 General
- 5.2 Architecture overview [Go to Page]
- 5.2.1 General rules
- 5.2.2 Common data types
- 5.2.3 Address level details
- 5.3 SPINE datagram [Go to Page]
- 5.3.1 Overview
- 5.3.2 Header
- 5.3.3 Payload
- 5.4 Communication modes [Go to Page]
- 5.4.1 General
- 5.4.2 Simple communication mode
- 5.4.3 Enhanced communication mode
- 5.5 Functional commissioning [Go to Page]
- 5.5.1 General
- 5.5.2 Detailed discovery
- 5.5.3 Destination list
- 5.5.4 Binding
- 5.5.5 Subscription
- 5.5.6 Use case discovery
- 6 SHIP [Go to Page]
- 6.1 Architecture overview [Go to Page]
- 6.1.1 General
- 6.1.2 General considerations on closing communication channels
- 6.1.3 SHIP node parameters
- 6.2 Registration [Go to Page]
- 6.2.1 General
- 6.2.2 Successful registration
- 6.2.3 Registration details and recommendations (informative)
- 6.3 Reconnection [Go to Page]
- 6.3.1 General
- 6.3.2 Reconnection details in case of changed key material (informative)
- 6.4 Discovery [Go to Page]
- 6.4.1 General
- 6.4.2 Service instance
- 6.4.3 Service name
- 6.4.4 Multicast DNS name
- 6.4.5 Recommendations for re-discovery
- 6.5 TCP [Go to Page]
- 6.5.1 General
- 6.5.2 Limited connection capabilities
- 6.5.3 Online detection
- 6.5.4 TCP connection establishment
- 6.5.5 Retransmission timeout
- 6.6 TLS [Go to Page]
- 6.6.1 General
- 6.6.2 Cipher suites
- 6.6.3 Maximum fragment length
- 6.6.4 TLS compression
- 6.6.5 Renegotiation
- 6.6.6 Session resumption
- 6.6.7 TLS extension for ECC
- 6.6.8 TLS probing
- 6.7 WebSocket [Go to Page]
- 6.7.1 General
- 6.7.2 TLS dependencies
- 6.7.3 Opening handshake
- 6.7.4 Data framing
- 6.7.5 Keep-alive connection
- 6.8 Message representation using JSON text format [Go to Page]
- 6.8.1 General
- 6.8.2 Definitions
- 6.8.3 Examples for each type
- 6.8.4 XML to JSON transformation
- 6.8.5 JSON to XML transformation
- 6.9 Key management [Go to Page]
- 6.9.1 General
- 6.9.2 Certificates
- 6.9.3 SHIP node specific public key
- 6.9.4 Verification procedure
- 6.9.5 Symmetric key
- 6.9.6 SHIP node PIN
- 6.9.7 SHIP commissioning tool
- 6.9.8 QR code
- 6.10 SHIP data exchange [Go to Page]
- 6.10.1 General
- 6.10.2 Terms in the context of SHIP data exchange
- 6.10.3 Protocol architecture/hierarchy
- 6.10.4 SHIP message exchange
- 6.11 Well-known protocolId
- 7 ECHONET Lite
- Annex A (normative) SHIP XSD
- Bibliography
- Figures [Go to Page]
- Figure 1 – Overview of communication protocols within IEC 63380-3
- Figure 2 – PossibleOperationsType
- Figure 3 – DeviceAddressType
- Figure 4 – EntityAddressType
- Figure 5 – FeatureAddressType
- Figure 6 – SPINE datagram
- Figure 7 – SPINE header
- Figure 8 – SPINE payload
- Figure 9 – Example of selectors part (extract) with entity address part
- Figure 10 – Communication modes of SPINE devices A, B and C
- Figure 11 – Discovery example
- Figure 12 – Hierarchy types
- Figure 13 – Function Discovery Example over Feature Description
- Figure 14 – nodeManagementDetailedDiscoveryData function overview, part 1
- Figure 15 – nodeManagementDetailedDiscoveryData function overview,part 2: deviceInformation.description
- Figure 16 – nodeManagementDetailedDiscoveryData function overview,part 3: entityInformation.description
- Figure 17 – nodeManagementDetailedDiscoveryData function overview,part 4: featureInformation.description
- Figure 18 – nodeManagementDestinationListData function overview, part 1
- Figure 19 – nodeManagementDestinationListData function overview, part 2
- Figure 20 – Binding request
- Figure 21 – nodeManagementBindingRequestCall function overview
- Figure 22 – nodeManagementBindingData function overview
- Figure 23 – nodeManagementBindingDeleteCall function overview
- Figure 24 – Subscription request
- Figure 25 – nodeManagementSubscriptionRequestCall function overview
- Figure 26 – nodeManagementSubscriptionData function overview
- Figure 27 – nodeManagementSubscriptionDeleteCall function overview
- Figure 28 – nodeManagementUseCaseData function
- Figure 29 – Physical connections in the overall system
- Figure 30 – SHIP stack overview
- Figure 31 – Full TLS 1.2 handshake with mutual authentication
- Figure 32 – Quick TLS Handshake with Session Resumption
- Figure 33 – Easy mutual authentication with QR codes and smart phone
- Figure 34 – QR code model 2, "low" error correction code level, 0,33 mm/module, with SKI and PIN
- Figure 35 – QR code model 2, "low" error correction code level, 0,33 mm/module, with all values
- Figure 36 – QR code model 2, "low" error correction code level, 0,33 mm/module, with brainpoolP256r1 SKI and brainpoolP384r1 SKI
- Figure 37 – Protocol architecture and hierarchy
- Figure 38 – CMI Message sequence example
- Figure 39 – Connection state "hello" sequence example without prolongation request: "A" and "B" already trust each other; "B" is slower/delayed
- Figure 40 – Connection state "hello" sequence example with prolongation request
- Figure 41 – Connection State "Protocol Handshake" message sequence example
- Figure 42 – Connection state "PIN verification" message sequence example (begin)
- Figure 43 – ECHONET Lite frame format
- Tables [Go to Page]
- Table 1 – Structure of the SPINE datagram
- Table 2 – cmdClassifier values and kind of messages for a message "M" and scope of related acknowledgement messages
- Table 3 – Structure of the SPINE header
- Table 4 – Elements of the SPINE payload
- Table 5 – Example table (template)
- Table 6 – Considered cmdOptions combinations for classifier "write"
- Table 7 – Considered cmdOptions combinations for classifier "notify"
- Table 8 – Considered cmdOptions combinations for classifier "read"
- Table 9 – Considered cmdOptions combinations for classifier "reply"
- Table 10 – Address path examples
- Table 11 – Notify/response list of entities and their corresponding features with nodeManagementDetailedDiscoveryData
- Table 12 – nodeManagementDetailedDiscoveryDataSelectors
- Table 13 – Notify/response of DestinationList information with nodeManagementDestinationListData
- Table 14 – Binding request with nodeManagementBindingRequestCall
- Table 15 – nodeManagementBindingData holds list of binding entries
- Table 16 – Remove binding with nodeManagementBindingDeleteCall
- Table 17 – Subscription request with nodeManagementSubscriptionRequestCall
- Table 18 – nodeManagementSubscriptionData holds list of subscription entries
- Table 19 – Remove subscription with nodeManagementSubscriptionDeleteCall
- Table 20 – nodeManagementUseCaseData
- Table 21 – SHIP parameters default values
- Table 22 – Mandatory parameters in the TXT record
- Table 23 – Optional parameters in the TXT record
- Table 24 – Mapping from the XSD types to JSON types
- Table 25 – Transformation of a simple type
- Table 26 – Mapping from the XSD compositors to JSON types
- Table 27 – Examples for XML and JSON representations
- Table 28 – Example transformation of several combined XSD item types
- Table 29 – Example for JSON to XML transformation
- Table 30 – Trust levels
- Table 31 – MessageType values
- Table 32 – Structure of SmeHelloValue of SME "hello" message
- Table 33 – Structure of SmeProtocolHandshakeValue of SME "Protocol Handshake" message
- Table 34 – Structure of SmeProtocolHandshakeErrorValue of SME "Protocol Handshake Error" message
- Table 35 – Values of Sub-element "error" of messageProtocolHandshakeError
- Table 36 – Structure of SmeConnectionPinStateValue of SME "PIN state" message
- Table 37 – Structure of SmeConnectionPinInputValue of SME "pin input" message
- Table 38 – Structure of SmeConnectionPinErrorValue of SME "Pin error" message
- Table 39 – Values of Sub-element "error" of connectionPinError
- Table 40 – Structure of MessageValue of "data" message
- Table 41 – Structure of SmeConnectionAccessMethodsRequestValue of SME "Access methods request" message
- Table 42 – Structure of SmeConnectionAccessMethodsValue of SME "Access methods" message
- Table 43 – Structure of SmeConnectionCommissioningRequestValue of SME "commissioning request" message
- Table 44 – Structure of SmeConnectionCommissioningResponseValue of SME "commissioning response" message
- Table 45 – Structure of SmeConnectionKeyMaterialRequestValue of SME "key material request" message
- Table 46 – Structure of SmeConnectionKeyMaterialValue of SME "key material" message
- Table 47 – Structure of SmeConnectionKeyMaterialResponseValue of SME "key material response" message
- Table 48 – Structure of SmeConnectionKeyMaterialDeleteValue of SME "key material delete" message
- Table 49 – Structure of SmeConnectionKeyMaterialDeleteResponseValue of SME "key material delete response" message
- Table 50 – Structure of SmeConnectionKeyMaterialStateValue of SME "key material state" message
- Table 51 – Structure of SmeConnectionKeyMaterialStateResponseValue of SME "key material state response" message
- Table 52 – Structure of SmeConnectionKeyMaterialStateRequestValue of SME "key material state request" message
- Table 53 – Structure of SmeCloseValue of SME "close" message
- Table 54 – Well-known values for the element "protocolId" [Go to Page]
