Transmission of normalized profiles from NB to MSB — MSB view
The MSB always receives the current standardized profiles. If an individual profile changes, only this profile is transmitted to the MSB.
Process flow from the perspective of the MSB
Process steps
Transmission of the standardised profiles
MSB NBCheck identifiers
Flow
Message from NB · AS4
Write endpoint
- Transaction created — Create process data
POST /createProcessData
Creates a new transaction in the backend with the data of the incoming message.
- Transaction created — Create process data
Process information
Wording of the consolidated version, profile ch. 6.8.1, pp. 75–76.
Preconditions
- The NB has changed at least one standardised profile, or
- the list of profile definitions has changed.
Further requirements
The NB transmits the profile with the highest version number for each time period.
First message
NB sends “Transmission of the standardised profiles” (step 1). From here on, it is the turn of the party involved on this page.
Objective
The MSB knows the standardized profiles of the NB.
Other views of the process
The same process through the eyes of the other parties involved: the same steps, each read from their point of view.
- View NB — NB
Notes on this page
The steps are the possible messages of this process, not a sequence — the source lists neither conditions nor alternatives. The small box on the step names the own view on the left: with ← it receives, with → it sends. Collapsed steps run between other market partners.
The connector table lists no write call for these steps. Derived from the process flow: the process begins for the own role with their message, so the transaction is created.
Applies to: 1
For the check identifiers of these steps there is no test case in the test data set; the »Try it out« button of the write interface therefore offers no body.
Applies to: 1