catm.006.001.01
The master terminal manager provides the outcome of a maintenance delegation request to a terminal manager.
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
%% MaintenanceDelegationResponseV01 recursion level 0 with max 0
MaintenanceDelegationResponseV01 *-- "1..1" Header16 : Header
MaintenanceDelegationResponseV01 *-- "1..1" MaintenanceDelegationResponse1 : MaintenanceDelegationResponse
MaintenanceDelegationResponseV01 *-- "1..1" ContentInformationType12 : SecurityTrailer
Now, we will zero-in one-by-one on each of these building blocks.
Header building block
Maintenance delegation response message management information. Set of characteristics related to the reject of a transaction. For comparison, see the ISO20022 official specification
classDiagram
direction tb
%% Header16 recursion level 0 with max 1
class Header16{
ProtocolVersion IsoMax6Text
ExchangeIdentification IsoMax3NumericText
CreationDateTime IsoISODateTime
}
Header16 *-- "1..1" GenericIdentification72 : InitiatingParty
Header16 *-- "0..1" GenericIdentification72 : RecipientParty
%% GenericIdentification72 recursion level 1 with max 1
class GenericIdentification72{
Identification IsoMax35Text
Issuer PartyType6Code
Country IsoMin2Max3AlphaText
ShortName IsoMax35Text
}
%% GenericIdentification72 recursion level 1 with max 1
class GenericIdentification72{
Identification IsoMax35Text
Issuer PartyType6Code
Country IsoMin2Max3AlphaText
ShortName IsoMax35Text
}
Header16 members
| Member name | Description | Data Type / Multiplicity |
|---|---|---|
| ProtocolVersion | Version of the terminal management protocol specifications. | IsoMax6Text - Required 1..1 |
| ExchangeIdentification | Unique identification of an exchange occurrence. | IsoMax3NumericText - Optional 0..1 |
| CreationDateTime | Date and time at which the file or message was created. | IsoISODateTime - Required 1..1 |
| InitiatingParty | Unique identification of the partner that has initiated the exchange. | GenericIdentification72 - Required 1..1 |
| RecipientParty | Unique identification of the partner that is the recipient of the exchange. | GenericIdentification72 - Optional 0..1 |
MaintenanceDelegationResponse building block
Information related to the request of maintenance delegations. Information related to the request of maintenance delegations. For comparison, see the ISO20022 official specification
classDiagram
direction tb
%% MaintenanceDelegationResponse1 recursion level 0 with max 1
MaintenanceDelegationResponse1 *-- "1..1" GenericIdentification72 : TMIdentification
MaintenanceDelegationResponse1 *-- "0..1" GenericIdentification72 : MasterTMIdentification
MaintenanceDelegationResponse1 *-- "1..0" MaintenanceDelegation2 : DelegationResponse
%% GenericIdentification72 recursion level 1 with max 1
class GenericIdentification72{
Identification IsoMax35Text
Issuer PartyType6Code
Country IsoMin2Max3AlphaText
ShortName IsoMax35Text
}
%% GenericIdentification72 recursion level 1 with max 1
class GenericIdentification72{
Identification IsoMax35Text
Issuer PartyType6Code
Country IsoMin2Max3AlphaText
ShortName IsoMax35Text
}
%% MaintenanceDelegation2 recursion level 1 with max 1
class MaintenanceDelegation2{
MaintenanceService DataSetCategory6Code
Response Response2Code
ResponseReason IsoMax35Text
POISubset IsoMax35Text
ParametersSubsetIdentification IsoMax35Text
ParametersSubsetDefinition IsoMax3000Binary
DelegationProof IsoMax5000Binary
}
MaintenanceDelegation2 *-- "0..1" ContentInformationType12 : ProtectedDelegationProof
MaintenanceDelegation2 *-- "0..0" MaintenanceIdentificationAssociation1 : POIIdentificationAssociation
MaintenanceDelegationResponse1 members
| Member name | Description | Data Type / Multiplicity |
|---|---|---|
| TMIdentification | Terminal manager identification. | GenericIdentification72 - Required 1..1 |
| MasterTMIdentification | Master terminal manager identification. | GenericIdentification72 - Optional 0..1 |
| DelegationResponse | Information on the delegation of a maintenance action. | MaintenanceDelegation2 - Unknown 1..0 |
SecurityTrailer building block
Trailer of the message containing a MAC or a digital signature. General cryptographic message syntax (CMS) containing protected data. For comparison, see the ISO20022 official specification
classDiagram
direction tb
%% ContentInformationType12 recursion level 0 with max 1
class ContentInformationType12{
ContentType ContentType2Code
}
ContentInformationType12 *-- "0..1" EnvelopedData4 : EnvelopedData
ContentInformationType12 *-- "0..1" AuthenticatedData4 : AuthenticatedData
ContentInformationType12 *-- "0..1" SignedData4 : SignedData
ContentInformationType12 *-- "0..1" DigestedData4 : DigestedData
%% EnvelopedData4 recursion level 1 with max 1
class EnvelopedData4{
Version IsoNumber
}
EnvelopedData4 *-- "1..0" IRecipient4Choice : Recipient
EnvelopedData4 *-- "0..1" EncryptedContent3 : EncryptedContent
%% 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
%% DigestedData4 recursion level 1 with max 1
class DigestedData4{
Version IsoNumber
Digest IsoMax140Binary
}
DigestedData4 *-- "1..1" AlgorithmIdentification16 : DigestAlgorithm
DigestedData4 *-- "1..1" EncapsulatedContent3 : EncapsulatedContent
ContentInformationType12 members
| Member name | Description | Data Type / Multiplicity |
|---|---|---|
| ContentType | Type of data protection. | ContentType2Code - Required 1..1 |
| EnvelopedData | Data protection by encryption, with a session key. | EnvelopedData4 - Optional 0..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 |
| DigestedData | Data protected by a digest. | DigestedData4 - Optional 0..1 |
Extensibility and generalization considerations
To facilitate generalized design patterns in the system, the MaintenanceDelegationResponseV01 implementation follows a specific implementaiton pattern. First of all, MaintenanceDelegationResponseV01 impleemnts IOuterRecord indicating it is the outermost logical part of the message definition. Like all message wrappers, MaintenanceDelegationResponseV01Document implements IOuterDocument. Because MaintenanceDelegationResponseV01 implements IOuterDocument, it is a suitable template parameter for IOuterDocument, and causes the internal ‘Message’ to be of type MaintenanceDelegationResponseV01.
classDiagram
class IOuterRecord
MaintenanceDelegationResponseV01 --|> IOuterRecord : Implements
MaintenanceDelegationResponseV01Document --|> IOuterDocument~MaintenanceDelegationResponseV01~ : Implements
class IOuterDocument~MaintenanceDelegationResponseV01~ {
MaintenanceDelegationResponseV01 Message
}
Document wrapper for serialization
The only real purpose MaintenanceDelegationResponseV01Document serves is to cause the document to be serialized into the ‘urn:iso:std:iso:20022:tech:xsd:catm.006.001.01’ namespace. Therefore, it will probably be the usual practice to build the message and construct this wrapper at the last minute using MaintenanceDelegationResponseV01.ToDocument() method. The returned MaintenanceDelegationResponseV01Document value will serialize correctly according to ISO 20022 standards.
classDiagram
MaintenanceDelegationResponseV01Document *-- MaintenanceDelegationResponseV01 : 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:catm.006.001.01">
<MntncDlgtnRspn>
<Hdr>
<!-- Header inner content -->
</Hdr>
<MntncDlgtnRspn>
<!-- MaintenanceDelegationResponse inner content -->
</MntncDlgtnRspn>
<SctyTrlr>
<!-- SecurityTrailer inner content -->
</SctyTrlr>
</MntncDlgtnRspn>
</Document>
Data from ISO specification
This is the technical data from the specification document.
<messageDefinition
xmi:id="_2l24gGqEEeS8RZDTbvnB_A"
nextVersions="_FyShYY4HEeWrZqsymMFdfg"
name="MaintenanceDelegationResponseV01"
definition="The master terminal manager provides the outcome of a maintenance delegation request to a terminal manager."
registrationStatus="Registered"
messageSet="_urpIICeJEeOCeO5e7islRQ"
xmlTag="MntncDlgtnRspn"
rootElement="Document"
xmlns:xmi="http://www.omg.org/XMI">
<messageBuildingBlock
xmi:id="_fY2w8GqFEeS8RZDTbvnB_A"
nextVersions="_FyShY44HEeWrZqsymMFdfg"
name="Header"
definition="Maintenance delegation response message management information."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="1"
xmlTag="Hdr"
complexType="_Ns0VYWp3EeSojYXQbRlLzA" />
<messageBuildingBlock
xmi:id="_3RHmkGqFEeS8RZDTbvnB_A"
nextVersions="_FyShZY4HEeWrZqsymMFdfg"
name="MaintenanceDelegationResponse"
definition="Information related to the request of maintenance delegations."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="1"
xmlTag="MntncDlgtnRspn"
complexType="_5IxrwGqFEeS8RZDTbvnB_A" />
<messageBuildingBlock
xmi:id="_sgPd8GqFEeS8RZDTbvnB_A"
nextVersions="_FyShZ44HEeWrZqsymMFdfg"
name="SecurityTrailer"
definition="Trailer of the message containing a MAC or a digital signature."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="1"
xmlTag="SctyTrlr"
complexType="_PwIbYWmPEeS7iYydEtv3Ug" />
<messageDefinitionIdentifier
businessArea="catm"
messageFunctionality="006"
flavour="001"
version="01" />
</messageDefinition>
ISO Building Blocks
The following items are used as building blocks to construct this message.