caam.004.001.02
The ATMKeyDownloadResponse message is sent from an acquirer to an ATM in response to an ATMKeyDownloadRequest message, to download of one or several cryptographic keys.
Message Construction
Every ISO20022 message has at the highest level what we call ‘building blocks’. Because the message is constructed as immutable records, the association is by composition. Below you can see the relationship between the message and its constituent building blocks: For comparison, see the ISO20022 official specification
classDiagram
direction LR
%% ATMKeyDownloadResponseV02 recursion level 0 with max 0
ATMKeyDownloadResponseV02 *-- "1..1" Header31 : Header
ATMKeyDownloadResponseV02 *-- "0..1" ContentInformationType10 : ProtectedATMKeyDownloadResponse
ATMKeyDownloadResponseV02 *-- "0..1" ATMKeyDownloadResponse2 : ATMKeyDownloadResponse
ATMKeyDownloadResponseV02 *-- "0..1" ContentInformationType13 : SecurityTrailer
Now, we will zero-in one-by-one on each of these building blocks.
Header building block
Information related to the protocol management on a segment of the path from the ATM to the acquirer. Information related to the protocol management on a segment of the path from the ATM to the acquirer. For comparison, see the ISO20022 official specification
classDiagram
direction tb
%% Header31 recursion level 0 with max 1
class Header31{
ProtocolVersion IsoMax6Text
ExchangeIdentification IsoMax3NumericText
CreationDateTime IsoISODateTime
InitiatingParty IsoMax35Text
RecipientParty IsoMax35Text
ProcessState IsoMax35Text
}
Header31 *-- "1..1" ATMMessageFunction2 : MessageFunction
Header31 *-- "0..0" Traceability4 : Traceability
%% ATMMessageFunction2 recursion level 1 with max 1
class ATMMessageFunction2{
Function MessageFunction11Code
ATMServiceCode IsoMax35Text
HostServiceCode IsoMax35Text
}
%% Traceability4 recursion level 1 with max 1
class Traceability4{
SequenceNumber IsoMax35Text
TraceDateTimeIn IsoISODateTime
TraceDateTimeOut IsoISODateTime
}
Traceability4 *-- "1..1" GenericIdentification77 : RelayIdentification
Header31 members
| Member name | Description | Data Type / Multiplicity |
|---|---|---|
| MessageFunction | Identifies the type of process related to the message. | ATMMessageFunction2 - Required 1..1 |
| ProtocolVersion | Version of the ATM protocol specifications. | IsoMax6Text - Required 1..1 |
| ExchangeIdentification | Unique identification of an exchange occurrence. | IsoMax3NumericText - Required 1..1 |
| CreationDateTime | Date and time at which the message was created. | IsoISODateTime - Required 1..1 |
| InitiatingParty | Unique identification of the partner that has initiated the exchange. | IsoMax35Text - Required 1..1 |
| RecipientParty | Unique identification of the partner that is the recipient of the message exchange. | IsoMax35Text - Optional 0..1 |
| ProcessState | State of the sender of the message inside the process flow. | IsoMax35Text - Optional 0..1 |
| Traceability | Identification of partners involved in exchange from the merchant to the issuer, with the relative timestamp of their exchanges. | Traceability4 - Unknown 0..0 |
ProtectedATMKeyDownloadResponse building block
Encrypted body of the message. General cryptographic message syntax (CMS) containing encrypted data. For comparison, see the ISO20022 official specification
classDiagram
direction tb
%% ContentInformationType10 recursion level 0 with max 1
class ContentInformationType10{
ContentType ContentType2Code
}
ContentInformationType10 *-- "1..1" EnvelopedData4 : EnvelopedData
%% EnvelopedData4 recursion level 1 with max 1
class EnvelopedData4{
Version IsoNumber
}
EnvelopedData4 *-- "1..0" IRecipient4Choice : Recipient
EnvelopedData4 *-- "0..1" EncryptedContent3 : EncryptedContent
ContentInformationType10 members
| Member name | Description | Data Type / Multiplicity |
|---|---|---|
| ContentType | Type of data protection. | ContentType2Code - Required 1..1 |
| EnvelopedData | Data protection by encryption or by a digital envelope, with an encryption key. | EnvelopedData4 - Required 1..1 |
ATMKeyDownloadResponse building block
Information related to the response of an ATM key download from an ATM manager. Information related to the response of an ATM key download from an ATM manager. For comparison, see the ISO20022 official specification
classDiagram
direction tb
%% ATMKeyDownloadResponse2 recursion level 0 with max 1
class ATMKeyDownloadResponse2{
ATMChallenge IsoMax140Binary
}
ATMKeyDownloadResponse2 *-- "1..1" ATMEnvironment7 : Environment
ATMKeyDownloadResponse2 *-- "1..1" ATMSecurityContext2 : ATMSecurityContext
ATMKeyDownloadResponse2 *-- "1..1" SecurityParameters5 : HostSecurityParameters
ATMKeyDownloadResponse2 *-- "0..0" ATMCommand7 : Command
%% ATMEnvironment7 recursion level 1 with max 1
ATMEnvironment7 *-- "0..1" Acquirer7 : Acquirer
ATMEnvironment7 *-- "0..1" Acquirer8 : ATMManager
ATMEnvironment7 *-- "0..1" TerminalHosting1 : HostingEntity
ATMEnvironment7 *-- "1..1" AutomatedTellerMachine3 : ATM
%% ATMSecurityContext2 recursion level 1 with max 1
class ATMSecurityContext2{
CurrentSecurityScheme ATMSecurityScheme1Code
}
ATMSecurityContext2 *-- "0..1" ATMEquipment3 : DeviceProperty
ATMSecurityContext2 *-- "0..1" ATMSecurityConfiguration1 : CurrentConfiguration
%% SecurityParameters5 recursion level 1 with max 1
class SecurityParameters5{
HostChallenge IsoMax140Binary
}
SecurityParameters5 *-- "0..0" CryptographicKey8 : Key
SecurityParameters5 *-- "0..1" ContentInformationType14 : DigitalSignature
%% ATMCommand7 recursion level 1 with max 1
class ATMCommand7{
Type ATMCommand4Code
Urgency TMSContactLevel2Code
DateTime IsoISODateTime
}
ATMCommand7 *-- "0..1" ATMCommandIdentification1 : CommandIdentification
ATMCommand7 *-- "0..1" IATMCommandParameters1Choice : CommandParameters
ATMKeyDownloadResponse2 members
| Member name | Description | Data Type / Multiplicity |
|---|---|---|
| Environment | Environment of the key download. | ATMEnvironment7 - Required 1..1 |
| ATMSecurityContext | Context of the ATM for the key download. | ATMSecurityContext2 - Required 1..1 |
| ATMChallenge | Random value from the ATM provided during a previous exchange. | IsoMax140Binary - Optional 0..1 |
| HostSecurityParameters | Security parameters of the host downloading the key. | SecurityParameters5 - Required 1..1 |
| Command | Maintenance command to perform on the ATM. | ATMCommand7 - Unknown 0..0 |
SecurityTrailer building block
Trailer of the message containing a MAC or a digital signature. General cryptographic message syntax (CMS) containing data. protected by a MAC or a digital signature. For comparison, see the ISO20022 official specification
classDiagram
direction tb
%% ContentInformationType13 recursion level 0 with max 1
class ContentInformationType13{
ContentType ContentType2Code
}
ContentInformationType13 *-- "0..1" AuthenticatedData4 : AuthenticatedData
ContentInformationType13 *-- "0..1" SignedData4 : SignedData
%% AuthenticatedData4 recursion level 1 with max 1
class AuthenticatedData4{
Version IsoNumber
MAC IsoMax140Binary
}
AuthenticatedData4 *-- "1..0" IRecipient4Choice : Recipient
AuthenticatedData4 *-- "1..1" AlgorithmIdentification15 : MACAlgorithm
AuthenticatedData4 *-- "1..1" EncapsulatedContent3 : EncapsulatedContent
%% SignedData4 recursion level 1 with max 1
class SignedData4{
Version IsoNumber
Certificate IsoMax5000Binary
}
SignedData4 *-- "1..0" AlgorithmIdentification16 : DigestAlgorithm
SignedData4 *-- "1..1" EncapsulatedContent3 : EncapsulatedContent
SignedData4 *-- "1..0" Signer3 : Signer
ContentInformationType13 members
| Member name | Description | Data Type / Multiplicity |
|---|---|---|
| ContentType | Type of data protection. | ContentType2Code - Required 1..1 |
| AuthenticatedData | Data protection by a message authentication code (MAC). | AuthenticatedData4 - Optional 0..1 |
| SignedData | Data protected by a digital signatures. | SignedData4 - Optional 0..1 |
Extensibility and generalization considerations
To facilitate generalized design patterns in the system, the ATMKeyDownloadResponseV02 implementation follows a specific implementaiton pattern. First of all, ATMKeyDownloadResponseV02 impleemnts IOuterRecord indicating it is the outermost logical part of the message definition. Like all message wrappers, ATMKeyDownloadResponseV02Document implements IOuterDocument. Because ATMKeyDownloadResponseV02 implements IOuterDocument, it is a suitable template parameter for IOuterDocument, and causes the internal ‘Message’ to be of type ATMKeyDownloadResponseV02.
classDiagram
class IOuterRecord
ATMKeyDownloadResponseV02 --|> IOuterRecord : Implements
ATMKeyDownloadResponseV02Document --|> IOuterDocument~ATMKeyDownloadResponseV02~ : Implements
class IOuterDocument~ATMKeyDownloadResponseV02~ {
ATMKeyDownloadResponseV02 Message
}
Document wrapper for serialization
The only real purpose ATMKeyDownloadResponseV02Document serves is to cause the document to be serialized into the ‘urn:iso:std:iso:20022:tech:xsd:caam.004.001.02’ namespace. Therefore, it will probably be the usual practice to build the message and construct this wrapper at the last minute using ATMKeyDownloadResponseV02.ToDocument() method. The returned ATMKeyDownloadResponseV02Document value will serialize correctly according to ISO 20022 standards.
classDiagram
ATMKeyDownloadResponseV02Document *-- ATMKeyDownloadResponseV02 : Document
Sample of message format
This is an abbreviated version of what the message should look like.
<Document xmlns="urn:iso:std:iso:20022:tech:xsd:caam.004.001.02">
<ATMKeyDwnldRspn>
<Hdr>
<!-- Header inner content -->
</Hdr>
<PrtctdATMKeyDwnldRspn>
<!-- ProtectedATMKeyDownloadResponse inner content -->
</PrtctdATMKeyDwnldRspn>
<ATMKeyDwnldRspn>
<!-- ATMKeyDownloadResponse inner content -->
</ATMKeyDwnldRspn>
<SctyTrlr>
<!-- SecurityTrailer inner content -->
</SctyTrlr>
</ATMKeyDwnldRspn>
</Document>
Data from ISO specification
This is the technical data from the specification document.
<messageDefinition
xmi:id="__AA4sa45EeWRfYPBaeOY8w"
nextVersions="_ya2bYbTzEeeQy4o2AayYHg"
previousVersion="_doLoYItREeST3ocKVc8_qA"
name="ATMKeyDownloadResponseV02"
definition="The ATMKeyDownloadResponse message is sent from an acquirer to an ATM in response to an ATMKeyDownloadRequest message, to download of one or several cryptographic keys."
registrationStatus="Registered"
messageSet="_lVeMdARsEeWTJNHF-ohSqw"
xmlTag="ATMKeyDwnldRspn"
rootElement="Document"
xmlns:xmi="http://www.omg.org/XMI">
<messageBuildingBlock
xmi:id="__AA4s645EeWRfYPBaeOY8w"
name="Header"
definition="Information related to the protocol management on a segment of the path from the ATM to the acquirer."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="1"
xmlTag="Hdr"
complexType="_eMl4Qa1wEeWMg5rOByfExw" />
<messageBuildingBlock
xmi:id="__AA4ta45EeWRfYPBaeOY8w"
name="ProtectedATMKeyDownloadResponse"
definition="Encrypted body of the message."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="0"
xmlTag="PrtctdATMKeyDwnldRspn"
complexType="_UfeMUWizEeS87LmvcA55sg" />
<messageBuildingBlock
xmi:id="__AA4t645EeWRfYPBaeOY8w"
name="ATMKeyDownloadResponse"
definition="Information related to the response of an ATM key download from an ATM manager."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="0"
xmlTag="ATMKeyDwnldRspn"
complexType="_F5BX4a46EeWRfYPBaeOY8w" />
<messageBuildingBlock
xmi:id="__AA4ua45EeWRfYPBaeOY8w"
name="SecurityTrailer"
definition="Trailer of the message containing a MAC or a digital signature."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="0"
xmlTag="SctyTrlr"
complexType="_R_tFoYreEeSvuOJS0mmL0g" />
<messageDefinitionIdentifier
businessArea="caam"
messageFunctionality="004"
flavour="001"
version="02" />
</messageDefinition>
ISO Building Blocks
The following items are used as building blocks to construct this message.