Collection communication involves both messaging and data transmission. The messaging part is illustrate below

The details on alams are described under Alarm communication. File list, checksums and salts, follows the same patter as for Get communication. The "get" message is only sent to one pillar.

The data trasmission involved is described under Data transmission protocol. It can be used either in transmission of message parameters or data as a result of a request.

Sequence diagrams

Ckecksums

Evt. Checksumsalgoritme for checksummer

Evt. max antal checksummer i svarbesked

Specifikt for checksummer skal denne information indeholde:

• antal filer
• information per fil (evt. repeterbar)
  • checksum
  • fil id
  • tidspunkt hvor checksum sidst blev beregnet (hvis det ikke er online, kan denne information være vigtig for alarmering)

File lists

Evt. max antal filer i svarbesked

Specifikt for checksummer skal denne information indeholde:

• antal filer
• information per fil (evt. repeterbar)
  • fil id
  • tidspunkt hvor filen sidst blev set (hvis det ikke er online, kan denne information være vigtig for alarmering)

Salts

Evt. ekstra tegn til direkte checksumscheck (Rosenthal NONCE)

Evt. max antal checksummer i svarbesked

Minimums informationer i request beskeder:

Specifikt for checksummer skal denne information indeholde:

...

Get Status - Communication. Communication for getFileIDs can either be via the Get File IDs client or be the same as for the Get File IDs client (See  Get File IDs Communications). Similar for the getChecksums communication, this can either be via the Get Checksums client or be the same as for the Get Checksums client (See Get Checksums Communication).

Each message is only sent to one pillar.