Cart (0)
- No items in cart.
Total
$0
There is a technical issue about last added item. You can click "Report to us" button to let us know and we resolve the issue and return back to you or you can continue without last item via click to continue button.
Not a subscriber? Register for a trial account.
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? * |
|
Reset password
Enter your personal account email address to request
a password reset:
a password reset:
Reset password
Enter your account email address to request
a password reset:
a password reset:
Security check
Please login to your authorized staff account to use this feature.
Are you sure you want to empty the cart?
Report To Us
Contact us for a custom quote
⨯To continue with accurate pricing,
please select your company type below:
⨯We need your input!
Are you a code official in a jurisdiction with less than 300,000 population?
⨯ We need your input!
⨯We need your input!
Are you an existing Madcad user?
If so, please login to continue with the free items in your cart.
⨯We need your input!
This bundle includes subscribed items.
Download File
eLibrary >
23/30476568 DC 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) >
Expand All
TOC Search:
23/30476568 DC 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), 2023
- 59_820e_CDV.pdf [Go to Page]
- European foreword (to be replaced with IEC IS foreword)
- Introduction
- 1 Scope
- 2 Normative references
- 3 Terms and definitions
- 4 SPINE-IoT Protocol [Go to Page]
- 4.1 General
- Figure 1 — Overview of transport protocols within EN 50631-4-1 [Go to Page]
- 4.2 Architecture overview [Go to Page]
- 4.2.1 Introduction
- 4.2.2 API versioning
- Table 1 — Properties of “api” information [Go to Page]
- 4.3 Device model [Go to Page]
- 4.3.1 General
- Figure 2 — Primary device model [Go to Page]
- 4.3.2 Device
- Table 2 — Properties of “device” information [Go to Page]
- 4.3.3 Entity
- Table 3 — Properties of “entity” information [Go to Page]
- 4.3.4 Feature
- Table 4 — Properties of “feature” information of a single featureObjType instance
- Table 5 — Supported featureType-featureObjType combinations [Go to Page]
- 4.4 Use Case model [Go to Page]
- 4.4.1 General
- Figure 3 — Use Case instance examples [Go to Page]
- 4.4.2 Use Case information and instances
- Figure 4 — Announcement of potential Use Case instance
- Figure 5 — Potential Use Case with real instance
- Table 6 — Properties of “Use Case” information [Go to Page]
- 4.4.3 Use Case interface
- 4.5 Binding [Go to Page]
- 4.5.1 General
- 4.5.2 Binding information and instances
- Table 7 — Request body for POST /bindings
- Table 8 — Properties of bindingRequestFeatures
- Table 9 — Properties of bindingRequestUsecaseInterfaces
- Table 10 — Response body upon accepted binding request
- Table 11 — Renew all bindings
- Table 12 — Renew a single bindingId
- Table 13 — Request body for the deletion of one or all bindings [Go to Page]
- 4.6 Subscription [Go to Page]
- 4.6.1 General
- 4.6.2 Subscription management
- Table 14 — Request body for POST /subscriptions
- Table 15 — Response body upon accepted subscription request
- Table 16 — Renew all subscriptions
- Table 17 — Renew a single subscriptionId
- Table 18 — Request body for the deletion of one or all subscriptions [Go to Page]
- 4.6.3 Callbacks
- Table 19 — Properties of a “device change description” callback
- Table 20 — Properties of an “entity change description” callback
- Table 21 — Properties of a “feature change description” callback
- Table 22 — Properties of a “Use Case information change description” callback [Go to Page]
- 4.7 Requesting feature changes [Go to Page]
- 4.7.1 General
- 4.7.2 Requesting changes information and instances
- Table 23 — Properties of a “feature” change request
- Table 24 — Properties of type featureModifyCreateReplace
- Table 25 — Properties of type featureModifyDelete
- Table 26 — Properties of type featureModifyPatchUnset
- 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 [Go to Page]
- 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
- 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
- 5.2.2.18 PossibleOperationsReadType
- 5.2.2.19 PossibleOperationsWriteType
- 5.2.2.20 PossibleOperationsType
- Figure 6 — PossibleOperationsType [Go to Page]
- 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
- Figure 7 — DeviceAddressType [Go to Page]
- 5.2.2.27 EntityAddressType
- Figure 8 — EntityAddressType [Go to Page]
- 5.2.2.28 FeatureAddressType
- Figure 9 — FeatureAddressType [Go to Page]
- 5.2.3 Address level details
- 5.3 SPINE Datagram [Go to Page]
- 5.3.1 Introduction [Go to Page]
- 5.3.1.1 General information
- Figure 10 — SPINE datagram [Go to Page]
- 5.3.1.2 Structure
- Table 27 — Structure of the SPINE datagram [Go to Page]
- 5.3.2 Header [Go to Page]
- 5.3.2.1 General information
- Figure 11 — SPINE header [Go to Page]
- 5.3.2.2 Address information [Go to Page]
- 5.3.2.2.1 addressSource and addressDestination
- 5.3.2.2.2 addressOriginator
- 5.3.2.3 Message counter [Go to Page]
- 5.3.2.3.1 General
- 5.3.2.3.2 msgCounter
- 5.3.2.3.3 msgCounterReference
- 5.3.2.4 Message classifiers
- Table 28 — cmdClassifier values and kind of messages for a message “M” and the scope of related acknowledgement messages [Go to Page]
- 5.3.2.5 Acknowledgement concept [Go to Page]
- 5.3.2.5.1 Acknowledgement request
- 5.3.2.5.2 Acknowledgement message
- 5.3.2.5.3 Delayed application response
- 5.3.2.6 Time information in “timestamp”
- 5.3.2.7 Structure
- Table 29 — Structure of the SPINE header [Go to Page]
- 5.3.3 Payload [Go to Page]
- 5.3.3.1 General information
- Figure 12 — SPINE payload [Go to Page]
- 5.3.3.2 Elements and usage
- Table 30 — Elements of the SPINE payload [Go to Page]
- 5.3.3.3 Ownership
- 5.3.3.4 Restricted function exchange with cmdOptions [Go to Page]
- 5.3.3.4.1 Overview
- Table 31 — Example table (template): This template is used in the subsequent sections for specific cmdOptions combinations. In this template, each “...” is just a placeholder [Go to Page]
- 5.3.3.4.2 “write” cmdOptions combinations
- Table 32 — Considered cmdOptions combinations for classifier “write” [Go to Page]
- 5.3.3.4.3 “notify” cmdOptions combinations
- Table 33 — Considered cmdOptions combinations for classifier “notify” [Go to Page]
- 5.3.3.4.4 “read” cmdOptions combinations
- Table 34 — Considered cmdOptions combinations for classifier “read” [Go to Page]
- 5.3.3.4.5 “reply” cmdOptions combinations
- Table 35 — Considered cmdOptions combinations for classifier “reply” [Go to Page]
- 5.3.3.4.6
identifiers - Implicit list item selection [Go to Page] - 5.3.3.4.6.1 General
- 5.3.3.4.6.2 Identifier hierarchy and completeness of list identifiers
- 5.3.3.4.7
– Explicit list item selection [Go to Page] - 5.3.3.4.7.1 General
- 5.3.3.4.7.2 Common rules and description
- 5.3.3.4.7.3 Selectors with address elements
- Table 36 — Address path examples
- Figure 13 — Example of selectors part (extract) with entity address part [Go to Page]
- 5.3.3.4.8
- Selection of “elements” - 5.3.3.4.9 Minimum restricted function exchange support
- 5.4 Communication modes [Go to Page]
- 5.4.1 General
- Figure 14 — Communication modes of SPINE devices A, B and C. The circle in device B symbolises the “message forwarding” task of device B. [Go to Page]
- 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 [Go to Page]
- 5.5.2.1 General
- Figure 15 — Discovery example
- Figure 16 — Hierarchy types. Entities can contain child-entities; “entityAddress” contains all “entity” parts starting from the respective root entity.
- Figure 17 — Function Discovery Example over Feature Description [Go to Page]
- 5.5.2.2 Basic definitions and rules [Go to Page]
- 5.5.2.2.1 General
- 5.5.2.2.2 Rules for devices
- 5.5.2.2.3 Rules for entities
- 5.5.2.2.4 Rules for features
- 5.5.2.2.5 Rules for specific element usage [Go to Page]
- 5.5.2.2.5.1 General
- 5.5.2.2.5.2 Usage of element “deviceAddress. device”
- 5.5.2.2.5.3 Usage of element networkManagementResponsibleAddress
- 5.5.2.2.5.4 Usage of element networkFeatureSet
- 5.5.2.2.5.5 Usage of element minimumTrustLevel
- 5.5.2.2.5.6 Usage of element possibleOperations
- 5.5.2.3 Detailed discovery “all at once”
- Figure 18 — nodeManagementDetailedDiscoveryData function overview, part 1
- Figure 19 — nodeManagementDetailedDiscoveryData function overview, part 2: deviceInformation.description
- Figure 20 — nodeManagementDetailedDiscoveryData function overview, part 3: entityInformation.description
- Figure 21 — nodeManagementDetailedDiscoveryData function overview, part 4: featureInformation.description
- Table 37 — Notify/response list of entities and their corresponding features with nodeManagementDetailedDiscoveryData [Go to Page]
- 5.5.2.4 Partial Detailed Discovery
- Table 38: nodeManagementDetailedDiscoveryDataSelectors [Go to Page]
- 5.5.2.5 Using detailed discovery for automatisms (informative)
- 5.5.2.6 Changes during runtime
- 5.5.3 Destination list [Go to Page]
- 5.5.3.1 Introduction
- 5.5.3.2 Architecture requirements
- 5.5.3.3 Rules [Go to Page]
- 5.5.3.3.1 Rules for devices
- 5.5.3.3.2 Rules for specific element usage [Go to Page]
- 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 [Go to Page]
- 5.5.3.4.1 Requesting DestinationList
- Figure 22 — nodeManagementDestinationListData function overview, part 1
- Figure 23 — nodeManagementDestinationListData function overview, part 2
- Table 39 — Notify/response of DestinationList information with nodeManagementDestinationListData [Go to Page]
- 5.5.3.4.2 Notification of DestinationList
- 5.5.4 Binding [Go to Page]
- 5.5.4.1 General
- 5.5.4.2 Basic definitions and rules
- 5.5.4.3 Create Binding
- Figure 24 — Binding request
- Figure 25 — nodeManagementBindingRequestCall function overview
- Table 40 — Binding request with nodeManagementBindingRequestCall [Go to Page]
- 5.5.4.4 Reading binding-information
- Figure 26 — nodeManagementBindingData function overview
- Table 41 — nodeManagementBindingData holds list of binding entries [Go to Page]
- 5.5.4.5 Release of a binding
- Figure 27 — nodeManagementBindingDeleteCall function overview
- Table 42 — Remove Binding with nodeManagementBindingDeleteCall [Go to Page]
- 5.5.4.6 Renew lost binding
- 5.5.4.7 Considerations on broken bindings (informative)
- 5.5.5 Subscription [Go to Page]
- 5.5.5.1 Basic definitions and rules
- 5.5.5.2 Create Subscription
- Figure 28 — Subscription request
- Figure 29 — nodeManagementSubscriptionRequestCall function overview
- Table 43 — Subscription request with nodeManagementSubscriptionRequestCall [Go to Page]
- 5.5.5.3 Reading subscription information
- Figure 30 — nodeManagementSubscriptionData function overview
- Table 44 — nodeManagementSubscriptionData holds list of subscription entries [Go to Page]
- 5.5.5.4 Release of a subscription
- Figure 31 — nodeManagementSubscriptionDeleteCall function overview
- Table 45 — Remove subscription with nodeManagementSubscriptionDeleteCall [Go to Page]
- 5.5.5.5 Renewal of subscription
- 5.5.5.6 Considerations on broken subscriptions (informative)
- 5.5.6 Use Case discovery [Go to Page]
- 5.5.6.1 Basic definitions and rules
- 5.5.6.2 Use Case Discovery “all at once”
- Figure 32 — nodeManagementUseCaseData function
- Table 46 — nodeManagementUseCaseData [Go to Page]
- 5.5.6.3 Partial Use Case Discovery
- 5.5.6.4 Changes during runtime
- 6 SHIP [Go to Page]
- 6.1 General
- 6.2 Architecture overview [Go to Page]
- 6.2.1 General
- Figure 33 — Physical Connections in the Overall System
- Figure 34 — SHIP Stack Overview [Go to Page]
- 6.2.2 General Considerations on Closing Communication Channels
- 6.2.3 SHIP Node Parameters
- Table 47 — SHIP Parameters Default Values [Go to Page]
- 6.3 Registration [Go to Page]
- 6.3.1 General
- 6.3.2 Successful Registration
- 6.3.3 Registration details and recommendations (informative)
- 6.4 Reconnection [Go to Page]
- 6.4.1 General
- 6.4.2 Reconnection details in case of changed key material (informative)
- 6.5 Discovery [Go to Page]
- 6.5.1 General
- 6.5.2 Service Instance
- 6.5.3 Service Name
- 6.5.4 Multicast DNS Name [Go to Page]
- 6.5.4.1 General
- 6.5.4.2 Default Records
- 6.5.4.3 TXT Record
- Table 48 — Mandatory Parameters in the TXT Record
- Table 49 — Optional Parameters in the TXT Record [Go to Page]
- 6.5.5 Recommendations for re-discovery
- 6.6 TCP [Go to Page]
- 6.6.1 General
- 6.6.2 Limited Connection Capabilities
- 6.6.3 Online Detection
- 6.6.4 TCP Connection Establishment
- 6.6.5 Retransmission Timeout
- 6.7 TLS [Go to Page]
- 6.7.1 General
- Figure 35 — Full TLS 1.2 Handshake with mutual authentication [Go to Page]
- 6.7.2 Cipher Suites
- 6.7.3 Maximum Fragment Length
- 6.7.4 TLS Compression [Go to Page]
- 6.7.4.1 General
- 6.7.4.2 Server Name Indication
- 6.7.5 Renegotiation
- 6.7.6 Session Resumption
- Figure 36 — Quick TLS Handshake with Session Resumption [Go to Page]
- 6.7.7 TLS extension for ECC
- 6.7.8 TLS Probing
- 6.8 WebSocket [Go to Page]
- 6.8.1 General
- 6.8.2 TLS Dependencies
- 6.8.3 Opening Handshake
- 6.8.4 Data Framing
- 6.8.5 Connection Keepalive
- 6.9 Message Representation Using JSON Text Format [Go to Page]
- 6.9.1 Introduction
- 6.9.2 Definitions
- 6.9.3 Examples For Each Type
- 6.9.4 XML to JSON Transformation [Go to Page]
- 6.9.4.1 Scope
- 6.9.4.2 XSD Types
- Table 50 — Mapping from the XSD Types to JSON Types [Go to Page]
- 6.9.4.3 Element Occurrences
- 6.9.4.4 Simple Types
- Table 51 — Transformation of a simple type [Go to Page]
- 6.9.4.5 Complex Types
- Table 52 — Mapping from the XSD compositors to JSON Types [Go to Page]
- 6.9.4.6 Rules
- 6.9.4.7 Example Transformations
- Table 53 — Examples for XML and JSON representations
- Table 54 — Example transformation of several combined XSD item types [Go to Page]
- 6.9.5 JSON to XML Transformation [Go to Page]
- 6.9.5.1 Scope
- 6.9.5.2 Rules
- 6.9.5.3 Example Transformation
- Table 55 — Example for JSON to XML transformation [Go to Page]
- 6.10 Key Management [Go to Page]
- 6.10.1 General
- 6.10.2 Certificates [Go to Page]
- 6.10.2.1 SHIP Node Certificates
- 6.10.2.2 Web Server Based SHIP Node Certificates
- 6.10.2.3 Certificate updates [Go to Page]
- 6.10.2.3.1 General
- 6.10.2.3.2 Overview
- 6.10.2.3.3 Transmitting certificate updates
- 6.10.2.3.4 Receiving certificate updates
- 6.10.2.3.5 Recognizing certificate updates
- 6.10.2.3.6 Effects for verification modes
- 6.10.3 SHIP Node Specific Public Key [Go to Page]
- 6.10.3.1 General
- 6.10.3.2 Public Key Presentation
- 6.10.3.3 Public Key Storage
- 6.10.3.4 Optional Storage
- 6.10.3.5 Prevent Double Connections with SKI Comparison
- 6.10.4 Verification Procedure [Go to Page]
- 6.10.4.1 General
- 6.10.4.2 Public Key Verification Modes
- 6.10.4.3 Auto Accept
- 6.10.4.4 Auto Accept with PIN
- 6.10.4.5 User Verification [Go to Page]
- 6.10.4.5.1 General
- 6.10.4.5.2 Manufacturer Specific Commissioning
- 6.10.4.5.3 User Input
- 6.10.4.5.4 SHIP Commissioning
- 6.10.4.6 Trust Level
- Table 56 — Trust Levels [Go to Page]
- 6.10.5 Symmetric Key
- 6.10.6 SHIP Node PIN
- Figure 37 — Easy Mutual Authentication with QR-codes and Smart Phone [Go to Page]
- 6.10.7 SHIP Commissioning Tool
- 6.10.8 QR Code
- Figure 38 — QR Code Model 2, “low” ECC level, 0,33 mm/Module, with SKI and PIN
- Figure 39 — QR Code Model 2, “low” ECC level, 0,33 mm/module, with all values
- Figure 40 — QR Code Model 2, “low” ECC level, 0,33 mm/module, with brainpoolP256r1 SKI and brainpoolP384r1 SKI [Go to Page]
- 6.11 SHIP Data Exchange [Go to Page]
- 6.11.1 Introduction
- 6.11.2 Terms in the context of SHIP Data Exchange
- 6.11.3 Protocol Architecture / Hierarchy [Go to Page]
- 6.11.3.1 Overview
- Figure 41 — Protocol Architecture and Hierarchy [Go to Page]
- 6.11.3.2 SHIP Message Exchange (SME), SME User
- 6.11.3.3 SHIP Transport
- 6.11.4 SHIP Message Exchange [Go to Page]
- 6.11.4.1 Basic Definitions and Responsibilities
- 6.11.4.2 Basic Message Structure
- Table 57 — MessageType Values [Go to Page]
- 6.11.4.3 Connection Mode Initialisation (CMI)
- Figure 42 — CMI Message Sequence Example [Go to Page]
- 6.11.4.4 Connection Data Preparation [Go to Page]
- 6.11.4.4.1 General
- 6.11.4.4.2 Connection State “Hello” [Go to Page]
- 6.11.4.4.2.1 Basic Definitions
- Table 58 — Structure of SmeHelloValue of SME “hello” Message [Go to Page]
- 6.11.4.4.2.2 Process Overview
- 6.11.4.4.2.3 Process Details
- Figure 43 — Connection State “Hello” Sequence Example Without Prolongation Request: “A” and “B” already trust each other; “B” is slower/delayed.
- Figure 44 — Connection State “Hello” Sequence Example With Prolongation Request. [Go to Page]
- 6.11.4.4.3 Connection State “Protocol handshake” [Go to Page]
- 6.11.4.4.3.1 Basic Definitions
- Table 59 —Structure of SmeProtocolHandshakeValue of SME “Protocol Handshake” Message
- Table 60 — Structure of SmeProtocolHandshakeErrorValue of SME “Protocol Handshake Error” Message [Go to Page]
- 6.11.4.4.3.2 Compatibility Aspects
- 6.11.4.4.3.3 Protocol Handshake Process
- Table 61 — Values of Sub-element “error” of messageProtocolHandshakeError
- Figure 45 — Connection State “Protocol Handshake” Message Sequence Example [Go to Page]
- 6.11.4.4.4 Connection State “PIN Verification” [Go to Page]
- 6.11.4.4.4.1 Introduction (Informative)
- 6.11.4.4.4.2 Basic Definitions
- Table 62 — Structure of SmeConnectionPinStateValue of SME “Pin state” message
- Table 63 — Structure of SmeConnectionPinInputValue of SME “Pin input” message
- Table 64 — Structure of SmeConnectionPinErrorValue of SME “Pin error” message [Go to Page]
- 6.11.4.4.4.3 Basic Rules
- 6.11.4.4.4.4 Protection Against Brute Force Attempts
- 6.11.4.4.4.5 Process Details [Go to Page]
- PIN Requirement — Communicated PIN States
- Process States
- Table 65 — Values of Sub-element “error” of connectionPinError
- Figure 46 — Connection State “PIN verification” Message Sequence Example (Begin) [Go to Page]
- 6.11.4.5 Connection Data Exchange [Go to Page]
- 6.11.4.5.1 General Rules
- 6.11.4.5.2 Message “data” [Go to Page]
- 6.11.4.5.2.1 Purpose and Structure
- Table 66 — Structure of MessageValue of “data” Message [Go to Page]
- 6.11.4.5.2.2 Extensibility Rules
- 6.11.4.5.2.3 Element “header”
- 6.11.4.5.2.4 Element “protocolId”
- 6.11.4.5.2.5 Element “payload”
- 6.11.4.5.2.6 Element “extension”
- 6.11.4.6 Access Methods Identification [Go to Page]
- 6.11.4.6.1 Introduction
- 6.11.4.6.2 Basic Definitions [Go to Page]
- 6.11.4.6.2.1 General
- Table 67 — Structure of SmeConnectionAccessMethodsRequestValue of SME “Access methods request” message
- Table 68 — Structure of SmeConnectionAccessMethodsValue of SME “Access methods” message [Go to Page]
- 6.11.4.6.2.2 Process Details
- 6.11.4.6.2.3 Recommendations
- 6.11.4.7 Key material exchange [Go to Page]
- 6.11.4.7.1 Introduction
- 6.11.4.7.2 SME “commissioning request” Message
- Table 69 — Structure of SmeConnectionCommissioningRequestValue of SME “commissioning request” message [Go to Page]
- 6.11.4.7.3 SME “commissioning response” Message
- Table 70 — Structure of SmeConnectionCommissioningResponseValue of SME “commissioning response” message [Go to Page]
- 6.11.4.7.4 SME “key material request” Message
- Table 71 — Structure of SmeConnectionKeyMaterialRequestValue of SME “key material request” message [Go to Page]
- 6.11.4.7.5 SME “key material” Message
- Table 72 — Structure of SmeConnectionKeyMaterialValue of SME “key material” message [Go to Page]
- 6.11.4.7.6 SME “key material response” Message
- Table 73 — Structure of SmeConnectionKeyMaterialResponseValue of SME “key material response” message [Go to Page]
- 6.11.4.7.7 SME “key material delete” Message
- Table 74 — Structure of SmeConnectionKeyMaterialDeleteValue of SME “key material delete” message [Go to Page]
- 6.11.4.7.8 SME “key material delete response” Message
- Table 75 — Structure of SmeConnectionKeyMaterialDeleteResponseValue of SME “key material delete response” message [Go to Page]
- 6.11.4.7.9 SME “key material state” message
- Table 76 — Structure of SmeConnectionKeyMaterialStateValue of SME “key material state” message [Go to Page]
- 6.11.4.7.10 SME “key material state response” message
- Table 77 — Structure of SmeConnectionKeyMaterialStateResponseValue of SME “key material state response” message [Go to Page]
- 6.11.4.7.11 SME “key material state request” message
- Table 78 — Structure of SmeConnectionKeyMaterialStateRequestValue of SME “key material state request” message [Go to Page]
- 6.11.4.8 Connection Termination [Go to Page]
- 6.11.4.8.1 Basic Definitions [Go to Page]
- 6.11.4.8.1.1 General
- Table 79 — Structure of SmeCloseValue of SME “close” Message [Go to Page]
- 6.11.4.8.1.2 Process Overview
- 6.11.4.8.1.3 Process Details
- 6.12 Well-known protocolId
- Annex A (normative) SHIP XSD
- Bibliography [Go to Page]
Copyright 2025 Compu-tecture, Inc.
All Rights Reserved.
About Us /
Careers /
support@madcad.com /
1.800.798.9296