Request for and provision of meter readings — LF view
Process flow from the perspective of the LF
Process steps
1 Forwarding of an individual request (outside the periodic meter reading)
NB MSB
This step runs between other market partners and is not relevant for this view.
Check identifiers
- 17004 — Request for values · AS4
4 Notification of failed read-out
MSB NB
This step runs between other market partners and is not relevant for this view.
Check identifiers
- 21028 — Information notification · AS4
Meter reading transmission
LF NBMSCONSZ33Z30Check identifiers
Flow
Message from NB · AS4
Load data for the incoming check
- Read metering location
GET /getMeterLocationBasic - Read market location
GET /getMarketLocationBasic - Read meter
GET /getCounterBasic
- Read metering location
APERAK checks
13002,13008,13009→MSCONS13006,13008,13009→Z33— APERAK check: Is referenced message known ?13008→Z30
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
Decision trees of the other parties involved
| EBD | Name |
|---|---|
| E_3009 | Check request |
Process information
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.
Notes on this page
The source provides no use case profile for this process — objective, precondition and result are not recorded there.
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.
Step sequence reconstructed
For this process, the BNetzA consolidated version carries no sequence diagram. The steps are reconstructed from the BDEW check identifier table: grouped by the designation, ordered by the process step. The method agrees with the consolidated version in 200 of 200 cases that can be cross-checked — the individual line is nevertheless not editorially reviewed. Check it against the rulebook before adopting it into an implementation specification.