Iso20022

MaintenanceDelegationResponseV03

catm.006.001.03

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
%% MaintenanceDelegationResponseV03 recursion level 0 with max 0
MaintenanceDelegationResponseV03 *-- "1..1" Header29 : Header
MaintenanceDelegationResponseV03 *-- "1..1" MaintenanceDelegationResponse3 : MaintenanceDelegationResponse
MaintenanceDelegationResponseV03 *-- "0..1" ContentInformationType18 : 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
%% Header29 recursion level 0 with max 1
class Header29{
    ProtocolVersion IsoMax6Text
    ExchangeIdentification IsoNumber
    CreationDateTime IsoISODateTime
}
Header29 *-- "1..1" GenericIdentification72 : InitiatingParty
Header29 *-- "0..1" GenericIdentification93 : RecipientParty
%% GenericIdentification72 recursion level 1 with max 1
class GenericIdentification72{
    Identification IsoMax35Text
    Issuer PartyType6Code
    Country IsoMin2Max3AlphaText
    ShortName IsoMax35Text
}
%% GenericIdentification93 recursion level 1 with max 1
class GenericIdentification93{
    Identification IsoMax35Text
    Issuer PartyType6Code
    Country IsoMin2Max3AlphaText
    ShortName IsoMax35Text
}
GenericIdentification93 *-- "0..1" NetworkParameters5 : RemoteAccess

Header29 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. IsoNumber - 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. GenericIdentification93 - 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
%% MaintenanceDelegationResponse3 recursion level 0 with max 1
MaintenanceDelegationResponse3 *-- "1..1" GenericIdentification72 : TMIdentification
MaintenanceDelegationResponse3 *-- "0..1" GenericIdentification72 : MasterTMIdentification
MaintenanceDelegationResponse3 *-- "1..0" MaintenanceDelegation6 : 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
}
%% MaintenanceDelegation6 recursion level 1 with max 1
class MaintenanceDelegation6{
    MaintenanceService DataSetCategory11Code
    Response Response2Code
    ResponseReason IsoMax35Text
    DelegationType TerminalManagementAction3Code
    POISubset IsoMax35Text
    DelegationScopeIdentification IsoMax35Text
    DelegationScopeDefinition IsoMax3000Binary
    DelegationProof IsoMax5000Binary
}
MaintenanceDelegation6 *-- "0..1" ContentInformationType19 : ProtectedDelegationProof
MaintenanceDelegation6 *-- "0..0" MaintenanceIdentificationAssociation1 : POIIdentificationAssociation

MaintenanceDelegationResponse3 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. MaintenanceDelegation6 - Unknown 1..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
%% ContentInformationType18 recursion level 0 with max 1
class ContentInformationType18{
    ContentType ContentType2Code
}
ContentInformationType18 *-- "0..1" AuthenticatedData5 : AuthenticatedData
ContentInformationType18 *-- "0..1" SignedData5 : SignedData
%% AuthenticatedData5 recursion level 1 with max 1
class AuthenticatedData5{
    Version IsoNumber
    MAC IsoMax140Binary
}
AuthenticatedData5 *-- "1..0" IRecipient6Choice : Recipient
AuthenticatedData5 *-- "1..1" AlgorithmIdentification22 : MACAlgorithm
AuthenticatedData5 *-- "1..1" EncapsulatedContent3 : EncapsulatedContent
%% SignedData5 recursion level 1 with max 1
class SignedData5{
    Version IsoNumber
    Certificate IsoMax5000Binary
}
SignedData5 *-- "0..0" AlgorithmIdentification21 : DigestAlgorithm
SignedData5 *-- "0..1" EncapsulatedContent3 : EncapsulatedContent
SignedData5 *-- "0..0" Signer4 : Signer

ContentInformationType18 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). AuthenticatedData5 - Optional 0..1
SignedData Data protected by a digital signatures. SignedData5 - Optional 0..1

Extensibility and generalization considerations

To facilitate generalized design patterns in the system, the MaintenanceDelegationResponseV03 implementation follows a specific implementaiton pattern. First of all, MaintenanceDelegationResponseV03 impleemnts IOuterRecord indicating it is the outermost logical part of the message definition. Like all message wrappers, MaintenanceDelegationResponseV03Document implements IOuterDocument. Because MaintenanceDelegationResponseV03 implements IOuterDocument, it is a suitable template parameter for IOuterDocument, and causes the internal ‘Message’ to be of type MaintenanceDelegationResponseV03.

classDiagram
    class IOuterRecord
    MaintenanceDelegationResponseV03 --|> IOuterRecord : Implements
    MaintenanceDelegationResponseV03Document --|> IOuterDocument~MaintenanceDelegationResponseV03~ : Implements
    class IOuterDocument~MaintenanceDelegationResponseV03~ {
        MaintenanceDelegationResponseV03 Message
     }

Document wrapper for serialization

The only real purpose MaintenanceDelegationResponseV03Document serves is to cause the document to be serialized into the ‘urn:iso:std:iso:20022:tech:xsd:catm.006.001.03’ namespace. Therefore, it will probably be the usual practice to build the message and construct this wrapper at the last minute using MaintenanceDelegationResponseV03.ToDocument() method. The returned MaintenanceDelegationResponseV03Document value will serialize correctly according to ISO 20022 standards.

classDiagram
    MaintenanceDelegationResponseV03Document *-- MaintenanceDelegationResponseV03 : 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.03">
    <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="_alRXYdqEEeearpaEPXv9UA"
  nextVersions="_I07cYQ01EeqUVL7sB4m7NA"
  previousVersion="_FyShYY4HEeWrZqsymMFdfg"
  name="MaintenanceDelegationResponseV03"
  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="_alRXY9qEEeearpaEPXv9UA"
    nextVersions="_I08DcQ01EeqUVL7sB4m7NA"
    previousVersion="_FyShY44HEeWrZqsymMFdfg"
    name="Header"
    definition="Maintenance delegation response message management information."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="Hdr"
    complexType="_RtBnUY4CEeWrZqsymMFdfg" />
  <messageBuildingBlock
    xmi:id="_alRXZdqEEeearpaEPXv9UA"
    nextVersions="_I08Dcw01EeqUVL7sB4m7NA"
    previousVersion="_FyShZY4HEeWrZqsymMFdfg"
    name="MaintenanceDelegationResponse"
    definition="Information related to the request of maintenance delegations."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="MntncDlgtnRspn"
    complexType="_Q75pYdqEEeearpaEPXv9UA" />
  <messageBuildingBlock
    xmi:id="_alRXZ9qEEeearpaEPXv9UA"
    nextVersions="_I08DdQ01EeqUVL7sB4m7NA"
    previousVersion="_FyShZ44HEeWrZqsymMFdfg"
    name="SecurityTrailer"
    definition="Trailer of the message containing a MAC or a digital signature."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="0"
    xmlTag="SctyTrlr"
    complexType="__DJZ4dtZEee9e6xduATmQg" />
  <messageDefinitionIdentifier
    businessArea="catm"
    messageFunctionality="006"
    flavour="001"
    version="03" />
</messageDefinition>

ISO Building Blocks

The following items are used as building blocks to construct this message.