MADCAD.com - The Cloud-Based Reference Library

Not a subscriber? Register for a trial account.

Username:
Password:

Incorrect username/password.

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.

Email *
Password *
Confirm *
First Name *
Last Name *
Title
Company Name *
Company Size *
Industry *
Address *
Address 2
City *
State *	Zip *
Country *
Phone *
How did you hear about MADCAD.com? *

⨯To continue with accurate pricing,
please select your company type below:

Large goverment organizations

Large multi-national corporation (more than $5B annual revenue)

None of the above

Your company has a special pricing case for IEEE.
For pricing, please contact us by filling out the form.

Full name*
Email*
Phone
Your selection

⨯We need your input!

Are you a code official in a jurisdiction with less than 300,000 population?

Yes No

This item is only available for the code officials of jurisdictions less then 300K population.

If you do not meet the criteria item will be removed and you will be able to continue shopping other items.

⨯ We need your input!

Your company has a special pricing case for ASME.
Please make sure the information you provide below is accurate.

Company Industry
Number Of Employees
Revenue

Pricing for the ASME publications in the store is for a 1-4 employee company in Construction Industry with revenue under $500,000.
If correct company info does not match what is publicly available info we will suspend the access and contact you for correction.
Please call 1-800-798-9296 if you have any questions.
If your company has more than 5,000 employee or more than 500 mil revenue please email us at info@madcad.com to receive a special quote, use "ASME Quote" on the subject line.

Search book title

Search book content

Clear all filters Advanced Search Basic Search

Download File

eLibrary > IEC 63380-3 Ed. 1.0 b:2025 Standard interface for connecting charging stations to local energy management systems - Part 3 Communication protocol and cybersecurity specific aspects >

IEC 63380-3 Ed. 1.0 b:2025 Standard interface for connecting charging stations to local energy management systems - Part 3 Communication protocol and cybersecurity specific aspects, 2025

Expand All

TOC Search:

IEC 63380-3 Ed. 1.0 b:2025 Standard interface for connecting charging stations to local energy management systems - Part 3 Communication protocol and cybersecurity specific aspects, 2025

English [Go to Page]
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"
Français [Go to Page]
SOMMAIRE
AVANT-PROPOS
INTRODUCTION
1 Domaine d’application
2 Références normatives
3 Termes, définitions et abréviations [Go to Page]
3.1 Termes et définitions
3.2 Abréviations
4 Vue d’ensemble
5 Protocole SPINE [Go to Page]
5.1 Généralités
5.2 Vue d’ensemble de l’architecture [Go to Page]
5.2.1 Règles générales
5.2.2 Types communs de données
5.2.3 Détails du niveau d’adresse
5.3 Datagramme SPINE [Go to Page]
5.3.1 Vue d’ensemble
5.3.2 En-tête
5.3.3 Données utiles
5.4 Modes de communication [Go to Page]
5.4.1 Généralités
5.4.2 Mode de communication simple
5.4.3 Mode de communication amélioré
5.5 Mise en service fonctionnelle [Go to Page]
5.5.1 Généralités
5.5.2 Recherche détaillée
5.5.3 Liste de destination
5.5.4 Liaison
5.5.5 Abonnement
5.5.6 Recherche de cas d’utilisation
6 SHIP [Go to Page]
6.1 Vue d’ensemble de l’architecture [Go to Page]
6.1.1 Généralités
6.1.2 Considérations générales relatives à la fermeture des canaux de communication
6.1.3 Paramètres du nœud SHIP
6.2 Enregistrement des données [Go to Page]
6.2.1 Généralités
6.2.2 Enregistrement réussi
6.2.3 Détails et recommandations d’enregistrement (à titre informatif)
6.3 Reconnexion [Go to Page]
6.3.1 Généralités
6.3.2 Détails de la reconnexion en cas de modification d’un élément de clé (à titre informatif)
6.4 Recherche [Go to Page]
6.4.1 Généralités
6.4.2 Instance de service
6.4.3 Nom de service
6.4.4 Nom du DNS multidiffusion
6.4.5 Recommandations relatives aux nouvelles recherches
6.5 TCP [Go to Page]
6.5.1 Généralités
6.5.2 Capacités de connexion limitées
6.5.3 Détection en ligne
6.5.4 Établissement d’une connexion TCP
6.5.5 Temporisation de retransmission
6.6 TLS [Go to Page]
6.6.1 Généralités
6.6.2 Suites chiffrées
6.6.3 Longueur de fragment maximale
6.6.4 Compression TLS
6.6.5 Renégociation
6.6.6 Reprise de session
6.6.7 Extension TLS pour ECC
6.6.8 Sondage TLS
6.7 WebSocket [Go to Page]
6.7.1 Généralités
6.7.2 Dépendances TLS
6.7.3 Liaison d’ouverture
6.7.4 Trame de données
6.7.5 Connexion persistante
6.8 Représentation des messages au format texte JSON [Go to Page]
6.8.1 Généralités
6.8.2 Définitions
6.8.3 Exemples pour chaque type
6.8.4 Transformation d’un XML en JSON
6.8.5 Transformation d’un JSON en XML
6.9 Gestion des clés [Go to Page]
6.9.1 Généralités
6.9.2 Certificats
6.9.3 Clé publique spécifique au nœud SHIP
6.9.4 Procédure de vérification
6.9.5 Clé symétrique
6.9.6 PIN de nœud SHIP
6.9.7 Outil de mise en service SHIP
6.9.8 QR code
6.10 Échange de données SHIP [Go to Page]
6.10.1 Généralités
6.10.2 Termes dans le cadre de l’échange de données SHIP
6.10.3 Architecture/hiérarchie de protocole
6.10.4 Échange de messages SHIP
6.11 ProtocolId bien connu
7 ECHONET Lite
Bibliographie
Figures [Go to Page]
Figure 1 – Vue d’ensemble des protocoles de communication au sein de l’IEC 63380-3
Figure 2 – PossibleOperationsType
Figure 3 – DeviceAddressType
Figure 4 – EntityAddressType
Figure 5 – FeatureAddressType
Figure 6 – Datagramme SPINE
Figure 7 – Structure d’en-tête SPINE
Figure 8 – Charge utile SPINE
Figure 9 – Exemple de partie (extrait) de sélecteurs avec une partie adresse "entity"
Figure 10 – Modes de communication des dispositifs SPINE A, B et C
Figure 11 – Exemple de recherche
Figure 12 – Types de hiérarchie
Figure 13 – Exemple de recherche de fonction sur une description de caractéristiques
Figure 14 – Vue d’ensemble de la fonction nodeManagementDetailedDiscoveryData, partie 1
Figure 15 – Vue d’ensemble de la fonction nodeManagementDetailedDiscoveryData, partie 2: deviceInformation.description
Figure 16 – Vue d’ensemble de la fonction nodeManagementDetailedDiscoveryData, partie 3: entityInformation.description
Figure 17 – Vue d’ensemble de la fonction nodeManagementDetailedDiscoveryData, partie 4: featureInformation.description
Figure 18 – Vue d’ensemble de la fonction nodeManagementDestinationListData, partie 1
Figure 19 – Vue d’ensemble de la fonction nodeManagementDestinationListData, partie 2
Figure 20 – Demande de liaison
Figure 21 – Vue d’ensemble de la fonction nodeManagementBindingRequestCall
Figure 22 – Vue d’ensemble de la fonction nodeManagementBindingData
Figure 23 – Vue d’ensemble de la fonction nodeManagementBindingDeleteCall
Figure 24 – Demande d’abonnement
Figure 25 – Vue d’ensemble de la fonction nodeManagementSubscriptionRequestCall
Figure 26 – Vue d’ensemble de la fonction nodeManagementSubscriptionData
Figure 27 – Vue d’ensemble de la fonction nodeManagementSubscriptionDeleteCall
Figure 28 – Fonction nodeManagementBindingData
Figure 29 – Connexions physiques dans le système global
Figure 30 – Vue d’ensemble de la pile SHIP
Figure 31 – Liaison TLS 1.2 complète avec authentification mutuelle
Figure 32 – Liaison TLS rapide avec reprise de session
Figure 33 – Authentification mutuelle facile par smartphone et QR Code
Figure 34 – QR Code Modèle 2, niveau de code de correction d’erreur "faible", 0,33 mm/module, avec SKI et code PIN
Figure 35 – QR Code Modèle 2, niveau de code de correction d’erreur "faible", 0,33 mm/module, avec toutes les valeurs
Figure 36 – QR Code Modèle 2, niveau de code de correction d’erreur "faible", 0,33 mm/module, avec SKI brainpoolP256r1 et SKI brainpoolP384r1
Figure 37 – Architecture et hiérarchie de protocole
Figure 38 – Exemple de séquence de messages CMI
Figure 39 – Exemple de séquence "hello" d’état de connexion sans demande de prolongation: "A" et "B" se sont déjà approuvés, "B" est plus lent/retardé
Figure 40 – Exemple de séquence "hello" d’état de connexion avec demande de prolongation
Figure 41 – Exemple de séquence de message d’état de connexion "protocol handshake"
Figure 42 – Exemple de séquence de messages d’état de connexion "PIN verification" (début)
Figure 43 – Format de trame ECHONET Lite
Tableaux [Go to Page]
Tableau 1 – Structure du datagramme SPINE
Tableau 2 – Valeurs et nature des messages cmdClassifier pour un message "M" et domaine d’application des messages d’acquittement associés
Tableau 3 – Structure de l’en-tête SPINE
Tableau 4 – Éléments de la charge utile SPINE
Tableau 5 – Exemple de tableau (modèle)
Tableau 6 – Combinaisons de cmdOptions prises en compte pour le classificateur "write"
Tableau 7 – Combinaisons de cmdOptions prises en compte pour le classificateur "notify"
Tableau 8 – Combinaisons de cmdOptions prises en compte pour le classificateur "read"
Tableau 9 – Combinaisons de cmdOptions prises en compte pour le classificateur "reply"
Tableau 10 – Exemples de chemins d’adresse
Tableau 11 – Liste de notifications/réponses des entités et leurs caractéristiques correspondantes avec nodeManagementDetailedDiscoveryData
Tableau 12 – nodeManagementDetailedDiscoveryDataSelectors
Tableau 13 – Notification/réponse des informations DestinationList avec nodeManagementDestinationListData
Tableau 14 – Demande de liaison avec nodeManagementBindingRequestCall
Tableau 15 – nodeManagementBindingData contient la liste des entrées de liaison
Tableau 16 – Supprimer la liaison avec nodeManagementBindingDeleteCall
Tableau 17 – Demande d’abonnement avec nodeManagementSubscriptionRequestCall
Tableau 18 – nodeManagementSubscriptionData contient la liste des entrées d’abonnement
Tableau 19 – Supprimession de l’abonnement avec nodeManagementSubscriptionDeleteCall
Tableau 20 – nodeManagementUseCaseData
Tableau 21 – Valeurs par défaut des paramètres SHIP
Tableau 22 – Paramètres obligatoires dans l’enregistrement TXT
Tableau 23 – Paramètres facultatifs dans l’enregistrement TXT
Tableau 24 – Correspondance des types XSD avec les types JSON
Tableau 25 – Transformation d’un type simple
Tableau 26 – Correspondance des compositeurs XSD avec les types JSON
Tableau 27 – Exemples de représentations XML et JSON
Tableau 28 – Exemple de transformation de plusieurs types d’éléments XSD combinés
Tableau 29 – Exemple de transformation d’un JSON en XML
Tableau 30 – Niveaux de confiance
Tableau 31 – Valeurs de MessageType
Tableau 32 – Structure de SmeHelloValue du message "hello" SME.
Tableau 33 – Structure de SmeProtocolHandshakeValuedu message "protocol handshake" SME
Tableau 34 – Structure de SmeProtocolHandshakeErrorValue du message "Protocol Handshake Error" SME
Tableau 35 – Valeurs du sous-élément "error" de messageProtocolHandshakeError
Tableau 36 – Structure de SmeConnectionPinStateValue du message "PIN state" SME
Tableau 37 – Structure de SmeConnectionPinInputValue du message "PIN input" SME.
Tableau 38 – Structure de SmeConnectionPinErrorValue du message "PIN error" SME
Tableau 39 – Valeurs du sous-élément "error" de connectionPinError
Tableau 40 – Structure de MessageValue du message "data"
Tableau 41 – Structure de SmeConnectionAccessMethodsRequestValue du message "Access methods request" SME
Tableau 42 – Structure de SmeConnectionAccessMethodsValue du message "Access methods" SME
Tableau 43 – Structure de SmeConnectionCommissioningRequestValue du message "commissioning request" SME
Tableau 44 – Structure de SmeConnectionCommissioningResponseValue du message "commissioning response" SME
Tableau 45 – Structure de SmeConnectionKeyMaterialRequestValue du message "key material request" SME
Tableau 46 – Structure de SmeConnectionKeyMaterialValue du message "key material" SME
Tableau 47 – Structure de SmeConnectionKeyMaterialResponseValue du message "key material response" SME
Tableau 48 – Structure de SmeConnectionKeyMaterialDeleteValue du message "key material delete" SME
Tableau 49 – Structure de SmeConnectionKeyMaterialDeleteResponseValue du message "key material delete response" SME
Tableau 50 – Structure de SmeConnectionKeyMaterialStateValue du message "key material state" SME
Tableau 51 – Structure de SmeConnectionKeyMaterialStateResponseValue du message "key material state response" SME
Tableau 52 – Structure de SmeConnectionKeyMaterialStateRequestValue du message "key material state request" SME
Tableau 53 – Structure de SmeCloseValue du message "close" SME
Tableau 54 – Valeurs connues pour l’élément "protocolId" [Go to Page]

Number Of Employees
Number Of Locations
Academic?
In UK?

MADCAD.com Free Trial

Report To Us

Contact us for a custom quote

⨯To continue with accurate pricing,
please select your company type below:

⨯We need your input!

⨯ We need your input!

⨯ We need your input!

⨯We need your input!

⨯We need your input!

Cart Warning

IEC 63380-3 Ed. 1.0 b:2025 Standard interface for connecting charging stations to local energy management systems - Part 3 Communication protocol and cybersecurity specific aspects, 2025

MADCAD.com Free Trial

Report To Us

Contact us for a custom quote

⨯To continue with accurate pricing, please select your company type below:

⨯We need your input!

⨯ We need your input!

⨯ We need your input!

⨯We need your input!

⨯We need your input!

Cart Warning

IEC 63380-3 Ed. 1.0 b:2025 Standard interface for connecting charging stations to local energy management systems - Part 3 Communication protocol and cybersecurity specific aspects, 2025

⨯To continue with accurate pricing,
please select your company type below: