|
|
This use case responds to the need to comply with what is regulated in Instruction 18 / V-132 of the DGT and in [RD 159/2021, of March 16, which regulates aid services on public roads ] (https://www.boe.es/boe/dias/2021/03/17/pdfs/BOE-A-2021-4194.pdf), in which the new V-16 signal devices , to send a message to the DGT3.0 platform. Therefore, the communication between the cloud of the manufacturer of these devices and the DGT3.0 platform is detailed.
|
|
|
|
|
|
Likewise, companies that are interested in consuming this information may do so with the following [documentation] (https://gitlab.cs.cmobility30.es/dgt3.0_eng/caso-de-uso-4).
|
|
|
|
|
|
|
|
|
All requests made to the API must be sent to the
|
|
|
following URL (base URL):
|
|
|
|
... | ... | @@ -38,7 +35,7 @@ To carry out the API operations, it is necessary to obtain a session token that |
|
|
|
|
|
The BOE indicates that "The protocol will include a response UDP packet (acknowledgment of receipt) by the
|
|
|
telephone operator, which the manufacturer may use for the purpose of controlling the arrival of the
|
|
|
packet, since the UDP protocol does not have this feature.” This came out in some meetings with the Operators. From the platform, what we will do is publish the messages through the outbox.
|
|
|
packet, since the UDP protocol does not have this feature.” This came out in some meetings with the Operators. From the platform, what we will do is publish the messages.
|
|
|
|
|
|
**Clarify the meaning of the three frame types (“Frame Type” field) of protocol A and resolve inconsistencies between the BOE and the Wiki for frame type 0 (“Incident Start” or “Battery Report”?) .**
|
|
|
|
... | ... | |