S-ALL-04 Support for Multiple End Clients failed - CACTUS client expecting MMR values in MUP/{id} GET requests

[joecrowley-synergy]

There is an issue where a MUP check is being performed and no mmrs are being returned by our utility server. According to the 2030.5 WADL, the GET method is optional on a mup resource, and with this the mup model states a relation of mmrs being 0..* so not sure how this should be represented in a GET response.

[joecrowley-synergy]

Later investigations show from section 10.11.3 part c of AS5385:2023 states that the behaviour of our server is the expected and the assumption made by CACTUS is false i.e. collections are to be provided in a response. The suggested fix I have come up with is to perform a series of GETs on the underlying Usage Point resource tree to make determinations that Meter Readings have been created correctly and exist, for later use in checks etc.

I have implemented a simplistic bypass of this by appending the POSTed mmrs to the internal resource tree of the CACTUS client context, and altered MUP checks to exclude certain checks. A more robust solution would be prudent.