This page addresses the following FAQs:
What does late response mean?
How do I retrieve a late response?
Is it possible to have late responses forwarded?
How to respond to NDLSRequest?
Q: What does “late response” mean?
The RESPER message dialogues SDLN and GDLD are synchronous, i.e. when receiving a request, the Member State’s Local Data Service is to provide a response within the synchronous session. In other words, within about 10 seconds.
However, in RESPER it is allowed to give a ‘late response’, in exceptional cases, where answering the request properly requires extra retrievals.
In the synchronous session, an InProgress response is sent. This is an acknowledgement message indicating that the request has been received but cannot be processed within a synchronous timeframe.
If the regular business response message is available, it is sent asynchronously to EUCARIS and, from there, back to the requesting Member State, asynchronously. Over there, the complete response message is made retrievable and can be retrieved or forwarded.
Q: How do I retrieve a Late Response?
This is done using the MessageRetrievalService. For further information: Message Retrieval Service – EUCARIS.
Q: Is it possible to have late responses forwarded?
Yes, this can be done by configuring async (response) forwarding in EUCARIS, i.e. create an endpoint that refers to an url of a domestic system that picks up the forwarded message. For further information: ** To do, create knowledge base item **
Q: How to respond to NDLSRequest?
If a Member State receives a NDLSRequest in its Local Data Service, an NDLSResponse is to be sent, synchronously. Basically, the NDLS response message is defined to be an acknowledgement, i.e. a response with status ‘OK’ (ResponseStatusCode=4) means that the request has been received successfully (but does not say anything about processing and/or if the status change that is notified, is ‘OK’ in the sense that the responding authority does agree on it).
Only one situation is defined where another response should be given than ‘OK’. If the driving license to which the notification applies, is unknown, i.e. not found in the DL register, then a response with status ‘NotFound’ (ResponseStatusCode =2) should be given.
Besides these status codes, it is possible to respond with status codes:
3 = NotOK
99 = Other
However, the use of these ResponseStatusCode is undefined. Also, the course of action for the notifying Member State, if receiving such ResponseStatusCode, is undefined.
EUCARIS recommends to always respond with status ‘OK’, unless the driving license to which the notification applies, is unknown. In that case, respond with ‘NotFound’.
Member States are free in deciding and designing how to process a NDLSRequest message, i.e. modify the register, automated or semi-automated or manually.
However, please note that the message is sent in a sync session, which means that it is not stored within EUCARIS and cannot be retrieved afterwards. In other words, an NDLSRequest message should either be processed directly, synchronously, or should be stored by the Local Data Service, somewhere in the local environment, for further processing.