Runtime view
New participant joins Block Management
-
A new client joins an existing block management service, that already contains active blocks
-
The new client must call BMS for an update
-
Block Management checks by the source application token (unique identifier for the application) the current state and returns a seperated list of block identifiers
-
section 1: blocks that must be added - Block Management knows if the client already knows about the Block
-
section 2: blocks that must be released - this should be empty because the participant is new and shouldn’t get blocks which should be deleted
-
-
Block Management Agent calls for each block the "Get Block"-Scenario
Subscribed participant went offline and after a while online again
-
The Client already contains active blocks of Block Management
-
The Client went offline and after a while online again. During the downtime, Block Management released and added some blocks
-
The Client must call Block Management for an update
-
Block Management knows the source application token of the Client and its current state. Block Management returns a seperated list of block identifiers
-
Section 1: Blocks that must be added - Block Management knows if the client already knows about the Block
-
Section 2: Blocks that must be released - Block Management knows if the client already has the information about the released Block
-
-
Block Management Agent removes Blocks from the "Blocks to Release"-list in the Application
-
Block Management Agent calls for each block the "Get Block"-Scenario
