{"id":440527,"date":"2024-10-20T08:15:35","date_gmt":"2024-10-20T08:15:35","guid":{"rendered":"https:\/\/pdfstandards.shop\/product\/uncategorized\/bsi-23-30476568-dc-2023\/"},"modified":"2024-10-26T15:26:19","modified_gmt":"2024-10-26T15:26:19","slug":"bsi-23-30476568-dc-2023","status":"publish","type":"product","link":"https:\/\/pdfstandards.shop\/product\/publishers\/bsi\/bsi-23-30476568-dc-2023\/","title":{"rendered":"BSI 23\/30476568 DC 2023"},"content":{"rendered":"
PDF Pages<\/th>\n | PDF Title<\/th>\n<\/tr>\n | ||||||
---|---|---|---|---|---|---|---|
6<\/td>\n | European foreword (to be replaced with IEC IS foreword) <\/td>\n<\/tr>\n | ||||||
7<\/td>\n | Introduction <\/td>\n<\/tr>\n | ||||||
8<\/td>\n | 1 Scope 2 Normative references 3 Terms and definitions <\/td>\n<\/tr>\n | ||||||
12<\/td>\n | 4 SPINE-IoT Protocol 4.1 General Figure 1 \u2014 Overview of transport protocols within EN 50631-4-1 <\/td>\n<\/tr>\n | ||||||
13<\/td>\n | 4.2 Architecture overview 4.2.1 Introduction <\/td>\n<\/tr>\n | ||||||
14<\/td>\n | 4.2.2 API versioning Table 1 \u2014 Properties of \u201capi\u201d information 4.3 Device model 4.3.1 General <\/td>\n<\/tr>\n | ||||||
15<\/td>\n | Figure 2 \u2014 Primary device model 4.3.2 Device Table 2 \u2014 Properties of \u201cdevice\u201d information 4.3.3 Entity <\/td>\n<\/tr>\n | ||||||
16<\/td>\n | Table 3 \u2014 Properties of \u201centity\u201d information 4.3.4 Feature <\/td>\n<\/tr>\n | ||||||
17<\/td>\n | Table 4 \u2014 Properties of \u201cfeature\u201d information of a single featureObjType instance <\/td>\n<\/tr>\n | ||||||
18<\/td>\n | Table 5 \u2014 Supported featureType-featureObjType combinations 4.4 Use Case model 4.4.1 General Figure 3 \u2014 Use Case instance examples <\/td>\n<\/tr>\n | ||||||
19<\/td>\n | 4.4.2 Use Case information and instances Figure 4 \u2014 Announcement of potential Use Case instance <\/td>\n<\/tr>\n | ||||||
20<\/td>\n | Figure 5 \u2014 Potential Use Case with real instance Table 6 \u2014 Properties of \u201cUse Case\u201d information <\/td>\n<\/tr>\n | ||||||
21<\/td>\n | 4.4.3 Use Case interface 4.5 Binding 4.5.1 General <\/td>\n<\/tr>\n | ||||||
22<\/td>\n | 4.5.2 Binding information and instances Table 7 \u2014 Request body for POST \/bindings Table 8 \u2014 Properties of bindingRequestFeatures <\/td>\n<\/tr>\n | ||||||
23<\/td>\n | Table 9 \u2014 Properties of bindingRequestUsecaseInterfaces <\/td>\n<\/tr>\n | ||||||
24<\/td>\n | Table 10 \u2014 Response body upon accepted binding request Table 11 \u2014 Renew all bindings Table 12 \u2014 Renew a single bindingId Table 13 \u2014 Request body for the deletion of one or all bindings 4.6 Subscription 4.6.1 General 4.6.2 Subscription management <\/td>\n<\/tr>\n | ||||||
25<\/td>\n | Table 14 \u2014 Request body for POST \/subscriptions <\/td>\n<\/tr>\n | ||||||
27<\/td>\n | Table 15 \u2014 Response body upon accepted subscription request Table 16 \u2014 Renew all subscriptions Table 17 \u2014 Renew a single subscriptionId Table 18 \u2014 Request body for the deletion of one or all subscriptions 4.6.3 Callbacks <\/td>\n<\/tr>\n | ||||||
28<\/td>\n | Table 19 \u2014 Properties of a \u201cdevice change description\u201d callback Table 20 \u2014 Properties of an \u201centity change description\u201d callback <\/td>\n<\/tr>\n | ||||||
29<\/td>\n | Table 21 \u2014 Properties of a \u201cfeature change description\u201d callback Table 22 \u2014 Properties of a \u201cUse Case information change description\u201d callback 4.7 Requesting feature changes 4.7.1 General <\/td>\n<\/tr>\n | ||||||
30<\/td>\n | 4.7.2 Requesting changes information and instances Table 23 \u2014 Properties of a \u201cfeature\u201d change request Table 24 \u2014 Properties of type featureModifyCreateReplace <\/td>\n<\/tr>\n | ||||||
31<\/td>\n | Table 25 \u2014 Properties of type featureModifyDelete Table 26 \u2014 Properties of type featureModifyPatchUnset <\/td>\n<\/tr>\n | ||||||
32<\/td>\n | 5 SPINE Protocol 5.1 General 5.2 Architecture overview 5.2.1 General rules <\/td>\n<\/tr>\n | ||||||
33<\/td>\n | 5.2.2 Common data types 5.2.2.1 General 5.2.2.2 ElementTagType 5.2.2.3 LabelType 5.2.2.4 DescriptionType 5.2.2.5 SpecificationVersionType 5.2.2.6 EnumExtendType <\/td>\n<\/tr>\n | ||||||
34<\/td>\n | 5.2.2.7 RoleType 5.2.2.8 FeatureGroupType 5.2.2.9 DeviceTypeType 5.2.2.10 DeviceTypeEnumType 5.2.2.11 EntityTypeType 5.2.2.12 EntityTypeEnumType 5.2.2.13 FeatureTypeType 5.2.2.14 FeatureTypeEnumType 5.2.2.15 FunctionType 5.2.2.16 FunctionEnumType 5.2.2.17 PossibleOperationsClassifierType <\/td>\n<\/tr>\n | ||||||
35<\/td>\n | 5.2.2.18 PossibleOperationsReadType 5.2.2.19 PossibleOperationsWriteType 5.2.2.20 PossibleOperationsType Figure 6 \u2014 PossibleOperationsType 5.2.2.21 MaxResponseDelayType 5.2.2.22 AbsoluteOrRelativeTimeType 5.2.2.23 AddressDeviceType 5.2.2.24 AddressEntityType 5.2.2.25 AddressFeatureType 5.2.2.26 DeviceAddressType <\/td>\n<\/tr>\n | ||||||
36<\/td>\n | Figure 7 \u2014 DeviceAddressType 5.2.2.27 EntityAddressType Figure 8 \u2014 EntityAddressType 5.2.2.28 FeatureAddressType Figure 9 \u2014 FeatureAddressType <\/td>\n<\/tr>\n | ||||||
37<\/td>\n | 5.2.3 Address level details <\/td>\n<\/tr>\n | ||||||
38<\/td>\n | 5.3 SPINE Datagram 5.3.1 Introduction 5.3.1.1 General information <\/td>\n<\/tr>\n | ||||||
39<\/td>\n | Figure 10 \u2014 SPINE datagram 5.3.1.2 Structure Table 27 \u2014 Structure of the SPINE datagram 5.3.2 Header 5.3.2.1 General information <\/td>\n<\/tr>\n | ||||||
40<\/td>\n | Figure 11 \u2014 SPINE header 5.3.2.2 Address information 5.3.2.2.1 addressSource and addressDestination <\/td>\n<\/tr>\n | ||||||
41<\/td>\n | 5.3.2.2.2 addressOriginator 5.3.2.3 Message counter 5.3.2.3.1 General 5.3.2.3.2 msgCounter <\/td>\n<\/tr>\n | ||||||
42<\/td>\n | 5.3.2.3.3 msgCounterReference 5.3.2.4 Message classifiers Table 28 \u2014 cmdClassifier values and kind of messages for a message \u201cM\u201d and the scope of related acknowledgement messages <\/td>\n<\/tr>\n | ||||||
43<\/td>\n | 5.3.2.5 Acknowledgement concept 5.3.2.5.1 Acknowledgement request <\/td>\n<\/tr>\n | ||||||
44<\/td>\n | 5.3.2.5.2 Acknowledgement message 5.3.2.5.3 Delayed application response <\/td>\n<\/tr>\n | ||||||
45<\/td>\n | 5.3.2.6 Time information in \u201ctimestamp\u201d 5.3.2.7 Structure <\/td>\n<\/tr>\n | ||||||
46<\/td>\n | Table 29 \u2014 Structure of the SPINE header <\/td>\n<\/tr>\n | ||||||
47<\/td>\n | 5.3.3 Payload 5.3.3.1 General information Figure 12 \u2014 SPINE payload 5.3.3.2 Elements and usage <\/td>\n<\/tr>\n | ||||||
48<\/td>\n | Table 30 \u2014 Elements of the SPINE payload <\/td>\n<\/tr>\n | ||||||
49<\/td>\n | 5.3.3.3 Ownership <\/td>\n<\/tr>\n | ||||||
50<\/td>\n | 5.3.3.4 Restricted function exchange with cmdOptions 5.3.3.4.1 Overview <\/td>\n<\/tr>\n | ||||||
51<\/td>\n | Table 31 \u2014 Example table (template): This template is used in the subsequent sections for specific cmdOptions combinations. In this template, each \u201c…\u201d is just a placeholder <\/td>\n<\/tr>\n | ||||||
52<\/td>\n | 5.3.3.4.2 \u201cwrite\u201d cmdOptions combinations Table 32 \u2014 Considered cmdOptions combinations for classifier \u201cwrite\u201d <\/td>\n<\/tr>\n | ||||||
53<\/td>\n | 5.3.3.4.3 \u201cnotify\u201d cmdOptions combinations Table 33 \u2014 Considered cmdOptions combinations for classifier \u201cnotify\u201d <\/td>\n<\/tr>\n | ||||||
54<\/td>\n | 5.3.3.4.4 \u201cread\u201d cmdOptions combinations Table 34 \u2014 Considered cmdOptions combinations for classifier \u201cread\u201d <\/td>\n<\/tr>\n | ||||||
55<\/td>\n | 5.3.3.4.5 \u201creply\u201d cmdOptions combinations Table 35 \u2014 Considered cmdOptions combinations for classifier \u201creply\u201d 5.3.3.4.6 identifiers – Implicit list item selection 5.3.3.4.6.1 General <\/td>\n<\/tr>\n | ||||||
56<\/td>\n | 5.3.3.4.6.2 Identifier hierarchy and completeness of list identifiers 5.3.3.4.7 \u2013 Explicit list item selection 5.3.3.4.7.1 General 5.3.3.4.7.2 Common rules and description <\/td>\n<\/tr>\n | ||||||
58<\/td>\n | 5.3.3.4.7.3 Selectors with address elements Table 36 \u2014 Address path examples <\/td>\n<\/tr>\n | ||||||
59<\/td>\n | Figure 13 \u2014 Example of selectors part (extract) with entity address part 5.3.3.4.8 – Selection of \u201celements\u201d <\/td>\n<\/tr>\n | ||||||
60<\/td>\n | 5.3.3.4.9 Minimum restricted function exchange support 5.4 Communication modes 5.4.1 General Figure 14 \u2014 Communication modes of SPINE devices A, B and C. The circle in device B symbolises the \u201cmessage forwarding\u201d task of device B. 5.4.2 Simple communication mode <\/td>\n<\/tr>\n | ||||||
61<\/td>\n | 5.4.3 Enhanced communication mode 5.5 Functional commissioning 5.5.1 General <\/td>\n<\/tr>\n | ||||||
62<\/td>\n | 5.5.2 Detailed discovery 5.5.2.1 General Figure 15 \u2014 Discovery example Figure 16 \u2014 Hierarchy types. Entities can contain child-entities; \u201centityAddress\u201d contains all \u201centity\u201d parts starting from the respective root entity. <\/td>\n<\/tr>\n | ||||||
63<\/td>\n | Figure 17 \u2014 Function Discovery Example over Feature Description 5.5.2.2 Basic definitions and rules 5.5.2.2.1 General <\/td>\n<\/tr>\n | ||||||
64<\/td>\n | 5.5.2.2.2 Rules for devices 5.5.2.2.3 Rules for entities <\/td>\n<\/tr>\n | ||||||
65<\/td>\n | 5.5.2.2.4 Rules for features 5.5.2.2.5 Rules for specific element usage 5.5.2.2.5.1 General 5.5.2.2.5.2 Usage of element \u201cdeviceAddress. device\u201d 5.5.2.2.5.3 Usage of element networkManagementResponsibleAddress 5.5.2.2.5.4 Usage of element networkFeatureSet <\/td>\n<\/tr>\n | ||||||
66<\/td>\n | 5.5.2.2.5.5 Usage of element minimumTrustLevel 5.5.2.2.5.6 Usage of element possibleOperations <\/td>\n<\/tr>\n | ||||||
67<\/td>\n | 5.5.2.3 Detailed discovery \u201call at once\u201d Figure 18 \u2014 nodeManagementDetailedDiscoveryData function overview, part 1 Figure 19 \u2014 nodeManagementDetailedDiscoveryData function overview, part 2: deviceInformation.description <\/td>\n<\/tr>\n | ||||||
68<\/td>\n | Figure 20 \u2014 nodeManagementDetailedDiscoveryData function overview, part 3: entityInformation.description <\/td>\n<\/tr>\n | ||||||
69<\/td>\n | Figure 21 \u2014 nodeManagementDetailedDiscoveryData function overview, part 4: featureInformation.description Table 37 \u2014 Notify\/response list of entities and their corresponding features with nodeManagementDetailedDiscoveryData <\/td>\n<\/tr>\n | ||||||
74<\/td>\n | 5.5.2.4 Partial Detailed Discovery <\/td>\n<\/tr>\n | ||||||
75<\/td>\n | Table 38: nodeManagementDetailedDiscoveryDataSelectors 5.5.2.5 Using detailed discovery for automatisms (informative) <\/td>\n<\/tr>\n | ||||||
76<\/td>\n | 5.5.2.6 Changes during runtime 5.5.3 Destination list 5.5.3.1 Introduction <\/td>\n<\/tr>\n | ||||||
77<\/td>\n | 5.5.3.2 Architecture requirements 5.5.3.3 Rules 5.5.3.3.1 Rules for devices <\/td>\n<\/tr>\n | ||||||
78<\/td>\n | 5.5.3.3.2 Rules for specific element usage 5.5.3.3.2.1 Usage of element deviceAddress. device 5.5.3.3.2.2 Usage of element networkFeatureSet 5.5.3.4 Exchanging DestinationList 5.5.3.4.1 Requesting DestinationList Figure 22 \u2014 nodeManagementDestinationListData function overview, part 1 Figure 23 \u2014 nodeManagementDestinationListData function overview, part 2 <\/td>\n<\/tr>\n | ||||||
79<\/td>\n | Table 39 \u2014 Notify\/response of DestinationList information with nodeManagementDestinationListData 5.5.3.4.2 Notification of DestinationList 5.5.4 Binding 5.5.4.1 General <\/td>\n<\/tr>\n | ||||||
80<\/td>\n | 5.5.4.2 Basic definitions and rules <\/td>\n<\/tr>\n | ||||||
81<\/td>\n | 5.5.4.3 Create Binding Figure 24 \u2014 Binding request Figure 25 \u2014 nodeManagementBindingRequestCall function overview Table 40 \u2014 Binding request with nodeManagementBindingRequestCall <\/td>\n<\/tr>\n | ||||||
82<\/td>\n | 5.5.4.4 Reading binding-information <\/td>\n<\/tr>\n | ||||||
83<\/td>\n | Figure 26 \u2014 nodeManagementBindingData function overview <\/td>\n<\/tr>\n | ||||||
84<\/td>\n | Table 41 \u2014 nodeManagementBindingData holds list of binding entries 5.5.4.5 Release of a binding <\/td>\n<\/tr>\n | ||||||
85<\/td>\n | Figure 27 \u2014 nodeManagementBindingDeleteCall function overview <\/td>\n<\/tr>\n | ||||||
86<\/td>\n | Table 42 \u2014 Remove Binding with nodeManagementBindingDeleteCall <\/td>\n<\/tr>\n | ||||||
87<\/td>\n | 5.5.4.6 Renew lost binding 5.5.4.7 Considerations on broken bindings (informative) <\/td>\n<\/tr>\n | ||||||
88<\/td>\n | 5.5.5 Subscription 5.5.5.1 Basic definitions and rules <\/td>\n<\/tr>\n | ||||||
89<\/td>\n | 5.5.5.2 Create Subscription Figure 28 \u2014 Subscription request <\/td>\n<\/tr>\n | ||||||
90<\/td>\n | Figure 29 \u2014 nodeManagementSubscriptionRequestCall function overview Table 43 \u2014 Subscription request with nodeManagementSubscriptionRequestCall <\/td>\n<\/tr>\n | ||||||
91<\/td>\n | 5.5.5.3 Reading subscription information Figure 30 \u2014 nodeManagementSubscriptionData function overview <\/td>\n<\/tr>\n | ||||||
92<\/td>\n | Table 44 \u2014 nodeManagementSubscriptionData holds list of subscription entries <\/td>\n<\/tr>\n | ||||||
93<\/td>\n | 5.5.5.4 Release of a subscription <\/td>\n<\/tr>\n | ||||||
94<\/td>\n | Figure 31 \u2014 nodeManagementSubscriptionDeleteCall function overview <\/td>\n<\/tr>\n | ||||||
95<\/td>\n | Table 45 \u2014 Remove subscription with nodeManagementSubscriptionDeleteCall 5.5.5.5 Renewal of subscription <\/td>\n<\/tr>\n | ||||||
96<\/td>\n | 5.5.5.6 Considerations on broken subscriptions (informative) 5.5.6 Use Case discovery 5.5.6.1 Basic definitions and rules 5.5.6.2 Use Case Discovery \u201call at once\u201d <\/td>\n<\/tr>\n | ||||||
97<\/td>\n | Figure 32 \u2014 nodeManagementUseCaseData function Table 46 \u2014 nodeManagementUseCaseData <\/td>\n<\/tr>\n | ||||||
98<\/td>\n | 5.5.6.3 Partial Use Case Discovery <\/td>\n<\/tr>\n | ||||||
99<\/td>\n | 5.5.6.4 Changes during runtime 6 SHIP 6.1 General 6.2 Architecture overview 6.2.1 General Figure 33 \u2014 Physical Connections in the Overall System <\/td>\n<\/tr>\n | ||||||
100<\/td>\n | Figure 34 \u2014 SHIP Stack Overview 6.2.2 General Considerations on Closing Communication Channels 6.2.3 SHIP Node Parameters Table 47 \u2014 SHIP Parameters Default Values <\/td>\n<\/tr>\n | ||||||
101<\/td>\n | 6.3 Registration 6.3.1 General <\/td>\n<\/tr>\n | ||||||
103<\/td>\n | 6.3.2 Successful Registration 6.3.3 Registration details and recommendations (informative) <\/td>\n<\/tr>\n | ||||||
104<\/td>\n | 6.4 Reconnection 6.4.1 General 6.4.2 Reconnection details in case of changed key material (informative) <\/td>\n<\/tr>\n | ||||||
105<\/td>\n | 6.5 Discovery 6.5.1 General 6.5.2 Service Instance 6.5.3 Service Name 6.5.4 Multicast DNS Name 6.5.4.1 General 6.5.4.2 Default Records <\/td>\n<\/tr>\n | ||||||
106<\/td>\n | 6.5.4.3 TXT Record Table 48 \u2014 Mandatory Parameters in the TXT Record Table 49 \u2014 Optional Parameters in the TXT Record <\/td>\n<\/tr>\n | ||||||
107<\/td>\n | 6.5.5 Recommendations for re-discovery 6.6 TCP 6.6.1 General 6.6.2 Limited Connection Capabilities <\/td>\n<\/tr>\n | ||||||
108<\/td>\n | 6.6.3 Online Detection 6.6.4 TCP Connection Establishment <\/td>\n<\/tr>\n | ||||||
109<\/td>\n | 6.6.5 Retransmission Timeout 6.7 TLS 6.7.1 General <\/td>\n<\/tr>\n | ||||||
110<\/td>\n | Figure 35 \u2014 Full TLS 1.2 Handshake with mutual authentication 6.7.2 Cipher Suites 6.7.3 Maximum Fragment Length <\/td>\n<\/tr>\n | ||||||
111<\/td>\n | 6.7.4 TLS Compression 6.7.4.1 General 6.7.4.2 Server Name Indication 6.7.5 Renegotiation 6.7.6 Session Resumption Figure 36 \u2014 Quick TLS Handshake with Session Resumption <\/td>\n<\/tr>\n | ||||||
112<\/td>\n | 6.7.7 TLS extension for ECC 6.7.8 TLS Probing <\/td>\n<\/tr>\n | ||||||
113<\/td>\n | 6.8 WebSocket 6.8.1 General 6.8.2 TLS Dependencies 6.8.3 Opening Handshake 6.8.4 Data Framing <\/td>\n<\/tr>\n | ||||||
114<\/td>\n | 6.8.5 Connection Keepalive 6.9 Message Representation Using JSON Text Format 6.9.1 Introduction 6.9.2 Definitions <\/td>\n<\/tr>\n | ||||||
115<\/td>\n | 6.9.3 Examples For Each Type 6.9.4 XML to JSON Transformation 6.9.4.1 Scope 6.9.4.2 XSD Types <\/td>\n<\/tr>\n | ||||||
116<\/td>\n | Table 50 \u2014 Mapping from the XSD Types to JSON Types 6.9.4.3 Element Occurrences 6.9.4.4 Simple Types Table 51 \u2014 Transformation of a simple type 6.9.4.5 Complex Types <\/td>\n<\/tr>\n | ||||||
117<\/td>\n | Table 52 \u2014 Mapping from the XSD compositors to JSON Types 6.9.4.6 Rules <\/td>\n<\/tr>\n | ||||||
118<\/td>\n | 6.9.4.7 Example Transformations Table 53 \u2014 Examples for XML and JSON representations <\/td>\n<\/tr>\n | ||||||
120<\/td>\n | Table 54 \u2014 Example transformation of several combined XSD item types <\/td>\n<\/tr>\n | ||||||
122<\/td>\n | 6.9.5 JSON to XML Transformation 6.9.5.1 Scope 6.9.5.2 Rules 6.9.5.3 Example Transformation Table 55 \u2014 Example for JSON to XML transformation 6.10 Key Management 6.10.1 General <\/td>\n<\/tr>\n | ||||||
123<\/td>\n | 6.10.2 Certificates 6.10.2.1 SHIP Node Certificates <\/td>\n<\/tr>\n | ||||||
124<\/td>\n | 6.10.2.2 Web Server Based SHIP Node Certificates 6.10.2.3 Certificate updates 6.10.2.3.1 General 6.10.2.3.2 Overview <\/td>\n<\/tr>\n | ||||||
125<\/td>\n | 6.10.2.3.3 Transmitting certificate updates <\/td>\n<\/tr>\n | ||||||
126<\/td>\n | 6.10.2.3.4 Receiving certificate updates 6.10.2.3.5 Recognizing certificate updates <\/td>\n<\/tr>\n | ||||||
127<\/td>\n | 6.10.2.3.6 Effects for verification modes 6.10.3 SHIP Node Specific Public Key 6.10.3.1 General 6.10.3.2 Public Key Presentation <\/td>\n<\/tr>\n | ||||||
128<\/td>\n | 6.10.3.3 Public Key Storage <\/td>\n<\/tr>\n | ||||||
129<\/td>\n | 6.10.3.4 Optional Storage 6.10.3.5 Prevent Double Connections with SKI Comparison 6.10.4 Verification Procedure 6.10.4.1 General <\/td>\n<\/tr>\n | ||||||
130<\/td>\n | 6.10.4.2 Public Key Verification Modes 6.10.4.3 Auto Accept <\/td>\n<\/tr>\n | ||||||
131<\/td>\n | 6.10.4.4 Auto Accept with PIN 6.10.4.5 User Verification 6.10.4.5.1 General <\/td>\n<\/tr>\n | ||||||
132<\/td>\n | 6.10.4.5.2 Manufacturer Specific Commissioning 6.10.4.5.3 User Input 6.10.4.5.4 SHIP Commissioning <\/td>\n<\/tr>\n | ||||||
134<\/td>\n | 6.10.4.6 Trust Level <\/td>\n<\/tr>\n | ||||||
135<\/td>\n | Table 56 \u2014 Trust Levels 6.10.5 Symmetric Key <\/td>\n<\/tr>\n | ||||||
136<\/td>\n | 6.10.6 SHIP Node PIN Figure 37 \u2014 Easy Mutual Authentication with QR-codes and Smart Phone <\/td>\n<\/tr>\n | ||||||
137<\/td>\n | 6.10.7 SHIP Commissioning Tool <\/td>\n<\/tr>\n | ||||||
139<\/td>\n | 6.10.8 QR Code <\/td>\n<\/tr>\n | ||||||
141<\/td>\n | Figure 38 \u2014 QR Code Model 2, \u201clow\u201d ECC level, 0,33 mm\/Module, with SKI and PIN Figure 39 \u2014 QR Code Model 2, \u201clow\u201d ECC level, 0,33 mm\/module, with all values <\/td>\n<\/tr>\n | ||||||
142<\/td>\n | Figure 40 \u2014 QR Code Model 2, \u201clow\u201d ECC level, 0,33 mm\/module, with brainpoolP256r1 SKI and brainpoolP384r1 SKI 6.11 SHIP Data Exchange 6.11.1 Introduction 6.11.2 Terms in the context of SHIP Data Exchange <\/td>\n<\/tr>\n | ||||||
144<\/td>\n | 6.11.3 Protocol Architecture \/ Hierarchy 6.11.3.1 Overview Figure 41 \u2014 Protocol Architecture and Hierarchy <\/td>\n<\/tr>\n | ||||||
145<\/td>\n | 6.11.3.2 SHIP Message Exchange (SME), SME User 6.11.3.3 SHIP Transport 6.11.4 SHIP Message Exchange 6.11.4.1 Basic Definitions and Responsibilities <\/td>\n<\/tr>\n | ||||||
146<\/td>\n | 6.11.4.2 Basic Message Structure Table 57 \u2014 MessageType Values 6.11.4.3 Connection Mode Initialisation (CMI) <\/td>\n<\/tr>\n | ||||||
148<\/td>\n | Figure 42 \u2014 CMI Message Sequence Example 6.11.4.4 Connection Data Preparation 6.11.4.4.1 General <\/td>\n<\/tr>\n | ||||||
149<\/td>\n | 6.11.4.4.2 Connection State \u201cHello\u201d 6.11.4.4.2.1 Basic Definitions Table 58 \u2014 Structure of SmeHelloValue of SME \u201chello\u201d Message 6.11.4.4.2.2 Process Overview <\/td>\n<\/tr>\n | ||||||
150<\/td>\n | 6.11.4.4.2.3 Process Details <\/td>\n<\/tr>\n | ||||||
155<\/td>\n | Figure 43 \u2014 Connection State \u201cHello\u201d Sequence Example Without Prolongation Request: \u201cA\u201d and \u201cB\u201d already trust each other; \u201cB\u201d is slower\/delayed. <\/td>\n<\/tr>\n | ||||||
156<\/td>\n | Figure 44 \u2014 Connection State \u201cHello\u201d Sequence Example With Prolongation Request. <\/td>\n<\/tr>\n | ||||||
157<\/td>\n | 6.11.4.4.3 Connection State \u201cProtocol handshake\u201d 6.11.4.4.3.1 Basic Definitions Table 59 \u2014Structure of SmeProtocolHandshakeValue of SME \u201cProtocol Handshake\u201d Message <\/td>\n<\/tr>\n | ||||||
158<\/td>\n | Table 60 \u2014 Structure of SmeProtocolHandshakeErrorValue of SME \u201cProtocol Handshake Error\u201d Message 6.11.4.4.3.2 Compatibility Aspects 6.11.4.4.3.3 Protocol Handshake Process <\/td>\n<\/tr>\n | ||||||
161<\/td>\n | Table 61 \u2014 Values of Sub-element \u201cerror\u201d of messageProtocolHandshakeError Figure 45 \u2014 Connection State \u201cProtocol Handshake\u201d Message Sequence Example <\/td>\n<\/tr>\n | ||||||
162<\/td>\n | 6.11.4.4.4 Connection State \u201cPIN Verification\u201d 6.11.4.4.4.1 Introduction (Informative) 6.11.4.4.4.2 Basic Definitions Table 62 \u2014 Structure of SmeConnectionPinStateValue of SME \u201cPin state\u201d message <\/td>\n<\/tr>\n | ||||||
163<\/td>\n | Table 63 \u2014 Structure of SmeConnectionPinInputValue of SME \u201cPin input\u201d message Table 64 \u2014 Structure of SmeConnectionPinErrorValue of SME \u201cPin error\u201d message 6.11.4.4.4.3 Basic Rules 6.11.4.4.4.4 Protection Against Brute Force Attempts <\/td>\n<\/tr>\n | ||||||
164<\/td>\n | 6.11.4.4.4.5 Process Details PIN Requirement \u2014 Communicated PIN States <\/td>\n<\/tr>\n | ||||||
165<\/td>\n | Process States <\/td>\n<\/tr>\n | ||||||
169<\/td>\n | Table 65 \u2014 Values of Sub-element \u201cerror\u201d of connectionPinError <\/td>\n<\/tr>\n | ||||||
170<\/td>\n | Figure 46 \u2014 Connection State \u201cPIN verification\u201d Message Sequence Example (Begin) 6.11.4.5 Connection Data Exchange 6.11.4.5.1 General Rules <\/td>\n<\/tr>\n | ||||||
171<\/td>\n | 6.11.4.5.2 Message \u201cdata\u201d 6.11.4.5.2.1 Purpose and Structure Table 66 \u2014 Structure of MessageValue of \u201cdata\u201d Message <\/td>\n<\/tr>\n | ||||||
172<\/td>\n | 6.11.4.5.2.2 Extensibility Rules 6.11.4.5.2.3 Element \u201cheader\u201d 6.11.4.5.2.4 Element \u201cprotocolId\u201d 6.11.4.5.2.5 Element \u201cpayload\u201d <\/td>\n<\/tr>\n | ||||||
173<\/td>\n | 6.11.4.5.2.6 Element \u201cextension\u201d 6.11.4.6 Access Methods Identification 6.11.4.6.1 Introduction 6.11.4.6.2 Basic Definitions 6.11.4.6.2.1 General <\/td>\n<\/tr>\n | ||||||
174<\/td>\n | Table 67 \u2014 Structure of SmeConnectionAccessMethodsRequestValue of SME \u201cAccess methods request\u201d message Table 68 \u2014 Structure of SmeConnectionAccessMethodsValue of SME \u201cAccess methods\u201d message <\/td>\n<\/tr>\n | ||||||
175<\/td>\n | 6.11.4.6.2.2 Process Details 6.11.4.6.2.3 Recommendations 6.11.4.7 Key material exchange 6.11.4.7.1 Introduction <\/td>\n<\/tr>\n | ||||||
176<\/td>\n | 6.11.4.7.2 SME \u201ccommissioning request\u201d Message Table 69 \u2014 Structure of SmeConnectionCommissioningRequestValue of SME \u201ccommissioning request\u201d message 6.11.4.7.3 SME \u201ccommissioning response\u201d Message Table 70 \u2014 Structure of SmeConnectionCommissioningResponseValue of SME \u201ccommissioning response\u201d message 6.11.4.7.4 SME \u201ckey material request\u201d Message <\/td>\n<\/tr>\n | ||||||
177<\/td>\n | Table 71 \u2014 Structure of SmeConnectionKeyMaterialRequestValue of SME \u201ckey material request\u201d message 6.11.4.7.5 SME \u201ckey material\u201d Message Table 72 \u2014 Structure of SmeConnectionKeyMaterialValue of SME \u201ckey material\u201d message <\/td>\n<\/tr>\n | ||||||
178<\/td>\n | 6.11.4.7.6 SME \u201ckey material response\u201d Message <\/td>\n<\/tr>\n | ||||||
179<\/td>\n | Table 73 \u2014 Structure of SmeConnectionKeyMaterialResponseValue of SME \u201ckey material response\u201d message 6.11.4.7.7 SME \u201ckey material delete\u201d Message Table 74 \u2014 Structure of SmeConnectionKeyMaterialDeleteValue of SME \u201ckey material delete\u201d message <\/td>\n<\/tr>\n | ||||||
180<\/td>\n | 6.11.4.7.8 SME \u201ckey material delete response\u201d Message Table 75 \u2014 Structure of SmeConnectionKeyMaterialDeleteResponseValue of SME \u201ckey material delete response\u201d message <\/td>\n<\/tr>\n | ||||||
181<\/td>\n | 6.11.4.7.9 SME \u201ckey material state\u201d message Table 76 \u2014 Structure of SmeConnectionKeyMaterialStateValue of SME \u201ckey material state\u201d message 6.11.4.7.10 SME \u201ckey material state response\u201d message <\/td>\n<\/tr>\n | ||||||
182<\/td>\n | Table 77 \u2014 Structure of SmeConnectionKeyMaterialStateResponseValue of SME \u201ckey material state response\u201d message 6.11.4.7.11 SME \u201ckey material state request\u201d message <\/td>\n<\/tr>\n | ||||||
183<\/td>\n | Table 78 \u2014 Structure of SmeConnectionKeyMaterialStateRequestValue of SME \u201ckey material state request\u201d message 6.11.4.8 Connection Termination 6.11.4.8.1 Basic Definitions 6.11.4.8.1.1 General Table 79 \u2014 Structure of SmeCloseValue of SME \u201cclose\u201d Message <\/td>\n<\/tr>\n | ||||||
184<\/td>\n | 6.11.4.8.1.2 Process Overview 6.11.4.8.1.3 Process Details <\/td>\n<\/tr>\n | ||||||
185<\/td>\n | 6.12 Well-known protocolId <\/td>\n<\/tr>\n | ||||||
186<\/td>\n | Annex A (normative) SHIP XSD <\/td>\n<\/tr>\n | ||||||
193<\/td>\n | Bibliography <\/td>\n<\/tr>\n<\/table>\n","protected":false},"excerpt":{"rendered":" BS EN IEC 63510-4-1. Household appliances network and grid connectivity – Part 4-1. Communication Protocol Specific Aspects: SPINE, SPINE-IoT and SHIP (fast track)<\/b><\/p>\n |