WO2019018908A1 - System for reading, logging and providing data on and parameters of the driving of a motor vehicle added to an electronic point logging system - Google Patents

Abstract

A system for reading, logging and providing data on and parameters of the driving of a motor vehicle added to an electronic point logging system, which is particularly but not exclusively intended for use in connection with haulage and public-transport vehicles, which permits the use of tachographs normally used to produce a log, on a "Chart Disc", of driving parameters that include: vehicle speed, distance covered (kilometres travelled) and period of time of movement and stops, having, therefore, a standard external device (DEP) (1) positioned in the interior of the vehicle and interconnected via wireless communication (2) to a DDD file (3) coupled to a tachograph (4), the latter housed in a secure location in the interior of the same vehicle; there are, furthermore, other devices interconnected to the DEP (1) and to the DDD file (3), such as GPS (5), the configuration terminal (6), monitoring and control terminals (7) and driver (8) and inspection (9) apps, all connected to a mobile telephone network (10), the internet (11) and the cloud, in addition to backend servers (12).

Description

 "SYSTEM FOR READING, REGISTERING AND AVAILABILIZING DATA AND DRIVING PARAMETERS OF AN AUTOMOTIVE VEHICLE ADDED TO THE ELECTRONIC POINT REGISTRATION SYSTEM" FIELD OF APPLICATION

 This invention describes a new system for reading, recording and making available the data and parameters for driving a motor vehicle, particularly, but not exclusively intended for use in relation to cargo vehicles and transport vehicles. which allows the use of chronographs normally used to record in a "Disc Diagram" driving parameters that include: vehicle speed, distance traveled (mileage) and times of movement and stops.

GOALS

 This patent application proposes a system for reading, recording and making available the data and driving parameters of a motor vehicle, which simplifies and makes more efficient the administration of fleets of vehicles with respect to the way of driving by the drivers, reducing traffic accidents caused by excesses in the transportation of schoolchildren, passengers, cargoes in general, and dangerous cargoes in terms of working hours and observance of speed limits.

STATE OF THE TECHNIQUE

The chronographs and the diagram discs, respectively, recording and media equipment, in which are recorded parameters of driving of a self-propelled vehicle (cargo or passenger transport) are known and integrate the state of the art related to this application of Invention Patent, , which parameters include vehicle speed, distance traveled (mileage) and times of movement and stops.

 The parameters listed above are obtained directly from the vehicle equipped with the chronograph by means of specific sensors and recorded instantaneously on a disk diagram, which medium is inserted in the recording chrono and on which the recording needles of said chronograph take place.

 The paper diaphragm disk, widely used as standard equipment for chrono-graphic equipment installed in passenger and cargo transport vehicles, has the purpose of automatically and instantaneously recording the speed and distance traveled by the vehicle in relation to time, as well as data concerning the driver of the vehicle such as: driver, route and driving and rest times.

 As reference of the state of the art may be cited document MU7101093-9, filed 23/05/1991, which deals with "DISCHARGE IN DIAGRAM FOR TACHOGRAPH", which describes innovation in a disk diagram in which a microcapsulated material is proposed (special paper) free from any layers of paint and dust, which may appear more pronounced when in contact with air.

 Another document belonging to the state of the art and related to the subject matter addressed by this patent application is MU72002114-0, filed February 11, 1992 and which deals with "INTRODUCTION INTO A TACHOGRAPH DISK" and which describes an innovation in disk diagram that is made up of blocks of paper.

EP-0550080 filed on 10/19/1992 and dealing with a "METHOD AND DEVICE FOR THE AUTOMATIC TREATMENT OF RECORDED DATA ON A TACHOGRAPH GRAPHIC" is also a further state-of-the-art document. Another document also pertinent to the case is patent GB2075681, filed May 03, 1980 and dealing with "DATA HANDLING SYSTEM", employed to enable manipulation of data recorded in a disk diagram.

 The state of the art relating to the present application also includes WO9308543, filed on 10/16/1991 and dealing with "METHOD AND APPARATUS FOR READING GRAPHICS GRAPHICS", in which the information on the diagram disk is scanned to produce, from representative of the data recorded in a table and send to a computer for processing information.

 DE4206139, filed February 28, 1992, which deals with "METHOD OF INTERPRETATION OF CHRONOTACOGRAPHIC DIAGRAMS", which provides for the scanning of the image and the profile of the recording line, which is drawn in a digital image using an algorithm of search.

 The state of the art pertinent to the present patent application further contemplates the patent application BR 10 2013 015772-4, filed on 06/21/2013 and entitled "DIGITAL DIAGRAM DISK AND ITS OPERATING SYSTEM". Said patent application was developed by the Applicant in order to provide an alternative to the conventional paper-produced disks.

Said Digital Diagram Disk discussed in the previous document BR 10 2013 015772-4 discloses a digital diagram disk and its operating system, characterized in that it comprises, dispersed in its constituent material or on one of its surfaces, a configuration of plates and electronic circuits interconnected in a peculiar way, providing embedded technology so that the trace on the disk, particularly the chronograph information from the driving of the vehicle, said information captured and converted into a digital signal by the disk itself, these digital data being stored directly on the disk and transmitted to external devices via wireless communication protocols.

 In more advanced studies, the applicant, in order to further provide benefits to vehicle drivers in general and other professionals involved in the industry and trade of chronograph and related equipment, is in this case intended to implement the object of the above-cited patent application , this application, registered in the name of this same applicant, and that, being a constant observer and researcher of these equipment, he noted the need to add to the set, the electronic point registration functionality to the Cronotacógrafo equipment, aiming its homologation and regulation by public bodies based on existing norms and guidelines because of the difficulty in controlling the working conditions of the professional driver, the legislation that teaches about the exercise of the driver's profession, extended the rights of this professional category, while at the same time extending obligations to their employer s, shippers, logistics companies and supervisory bodies, among which are duties to supervise the working day and the time of direction of the professional driver.

The supervision of the driving time of professional drivers has been hampered by the inexistence of an effective control system, since it occurs only through the use of records in ballots, which makes the work of the traffic agent unproductive and inefficient, in relation the purpose of supervision, which is to provide the traffic Safety.

BRIEF DESCRIPTION OF THE INVENTION

 In this way, the Applicant has developed this "SYSTEM FOR THE READING, REGISTRATION AND AVAILABILITY OF DATA AND DRIVING PARAMETERS OF AN AUTOMOTIVE VEHICLE ADDED TO THE ELECTRONIC POINT REGISTRATION SYSTEM", which should provide substantial benefits to professional drivers, as well as provide protection and safety, not only to these drivers, but also to employers, shippers and even logistics companies, thus forming an effective and productive protection and control system for the purpose for which it is intended.

 The "Diagram Digital Diagram - DDD", now proposed, is an equipment that adds to the chronographer an electronic point registration system, an innovative and multifunctional product that associates digital intelligence and attends the private and public area, executing activities control registration of activities and identification through biometric authentication, while promoting the traceability, integrity and security of the information guaranteed by means of digital signature and access control, and also allowing the inspection by means of smartphones ( Traffic agents, PRF and INMETRO).

 Another feature is the possibility of sending and storing information in the cloud and also allows the geographical location of activities through GPS.

 The DDD now proposed has a format compatible with the Disk Paper Diagram, already widely known in the art, enabling installation without any necessary adaptation, in any Cronotachograph equipment.

The use of the chronographer to obtain an electronic point record promotes greater effectiveness in the control of drivers, logistics companies, passenger transport, dangerous cargoes and others, facilitating inspection and establishing a consistent proof of the work done by the drivers, facilitating the inspections carried out by the Ministry of Labor and Social Security and also in the labor, civil and criminal procedural instructions, if necessary.

 Another aspect of relevance is that the proposed DDD project is sustainable. Its conception is totally digital, eliminating the printing of the current disks paper diagrams, being this, an evolution, as much in the ecological aspect, as of the availability of data, since besides allowing to access the data in a application of smartphone, one has the possibility of replicating them to servers in the cloud, thus ensuring the redundancy of information with the same reliability of the data stored internally on the disk by means of the digital signature.

 BRIEF DESCRIPTION OF THE DRAWINGS

 The subject matter of this invention will be fully clear in its technical aspects from the detailed description which will be made on the basis of the following figures, in which:

 Figure 1 shows a diagram of the proposed solution set for the system for reading, recording and making available data and driving parameters of a self-propelled vehicle added to an electronic point registration system.

Figure 2 shows the schematic drawing of the disc digital diagram - DDD proposed here. Figure 3 shows a schematic front view of the standard external device-DEP employed in association with the disk digital diagram proposed herein.

 Figure 4 shows a schematic of the device's cryptographic certificates, which sets up permanent information such as the unique identifier, the model, and the serial number.

 Figure 5 shows the connection authorization diagram between devices.

 Figure 6 shows the signature flow, verification, and execution of configuration commands.

 Figure 7 shows the file signing process of the disk digital diagram - DDD presented here.

 Figure 8 shows the signature verification process.

 Figure 9 shows the front view of the main screen of the inspection application.

 Figure 10 shows the front view of the inspection application activities.

 Figure 11 shows the front view of the graphics of the inspection application.

 Figure 12 shows the front view of a selected point of the inspection application.

 Figure 13 shows the schematic drawing of the proposed standard external device, DEP 1.

DETAILED DESCRIPTION OF THE INVENTION

In accordance with the above figures, the present invention entitled "SYSTEM FOR READING, REGISTERING AND AVAILABILIZING DATA AND DRIVING PARAMETERS OF AN AUTOMOTIVE VEHICLE ADDED TO THE ELECTRONIC POINT REGISTRATION SYSTEM" has a standard external device - DEP 1, positioned in the interior of the vehicle, being in direct contact with the driver, in addition to being interconnected via wireless communication 2 to a DDD 3 coupled to a chronograph 4, as shown in figure 1, this is housed in a secure location inside the same vehicle.

 The system DEP 1 and DDD 3 have interconnection with other systems such as GPS 5, configuration terminal 6, monitoring and control terminals 7 and driver 8 and inspection 9 applications, all connected to a telephone network mobile 10, internet 11 and cloud, in addition to Backend 12 servers, as shown in the diagram in figure 1.

 The standard external device DEP 1 presents functional graph as shown in figure 13, being constituted by a processor 108 equipped with flash memory 109, RAM 110 and a microcontroller 111, said processor 108 also having a SIM Card 112 and a Micro SD Card 113.

 The system as a whole is powered by a battery 114 and particularly the processor 108 has a serial interface 115, connected to a power center 116 where a charger 117 is positioned for the battery 114, in addition to a buck 118 and a boost 119 which provide the operating voltages of the system, depending on whether the system is powered by the external power unit 116 or the internal battery 114, where buck 118 and boost 119 are part of the system's macro power management block, which manages the different system operating voltages and charge the battery.

Interconnected to the processor 108 of the standard external device DEP 1, two interfaces 120 and 121 are provided, one internal 120 and one external 121, where the internal interface 120 has a transmitter and receiver circuit 122 of the DDD 3, a transmitter and receiver circuit 123 of the GPS 5, and a transmitter and receiver circuit 124 of the internet 11.

 On the other hand, the external interface 121 has in turn a user display 125, navigation selection keys 126, a buzzer 127 and a biometric data reader 128, which can configure the digital reading, the palm of the hand, retinal scan or other possible means of biometry.

 DDD 3 presents the same physical format as the paper diagram disk, thus being easily coupled to the chronograph 4 in exactly the same way as a conventional disk pattern, however, having a very diverse information capture structure.

 The processor 3A provided in the DDD system 3 and DEP 1, via its battery 3B, powers the wireless communication module 3C, the non-volatile type 3D memory, the cryptographic hardware 3E, the clock movement sensor 3F and the 3G sensors of the 3H needles, as shown in figure 2.

 When the 3H needles of the chronotegraph 4 come into contact with the 3G sensors of the DDD 3, data are produced which are processed to form the speed and displacement information of the vehicle in relation to the time, which is provided by an internal clock of the Real Time type Clock 3F.

 This information is then stored in the internal memory of DDD 3 in the form of sequential files, signed by the private key of the device's internal cryptographic 3E processor, thereby ensuring the integrity and legitimacy of the information.

The registration of the information concerning the driver of the vehicle is carried out with the aid of DEP 1, which has an interface for selecting the activity of the driver 13, which must be confirmed with the positive reading of the capture biometric 15 of the same, as it is possible to observe in figure 3.

 The device 1 sends via wireless communication 2 to the digital diagram disk DDD 3, the driver activity record 13, which in turn stores it in the log file, also signed by the cryptographic processor 3E to guarantee the integrity and legitimacy of information.

 A location record, obtained by a GPS 5 processor installed on the Standard External Device - DEP 1, is also sent and stored in the internal memory of the disk 3 in a similar manner and guarantees the location of the driver at the time of recording the activity 13.

 By means of logs of the procedures for installation, configuration, connection, opening and closing of the chronograph 4, among others, it is possible to audit the operation of the Digital Diagram Disk - DDD 3. Such procedures assure its integrity and help to identify fraudulent actions, since the records stored in the memory of device 1 can not be deleted or changed.

 For the surveillance process, a smartphone with an application 8 and 9 developed for this purpose is used.

 Inspection agents can access and inspect any digital disk 3 diagram that will provide information of the last 24 hours of direction.

 With the combination of these equipments, the time and subjectivity of the inspection of the traffic laws and the working day of the professional drivers is drastically reduced.

The DEP 1 also has connection to the mobile telephone network 10. The files generated by DDD 3 are constantly sent to the company's Backend 12 servers, thus guaranteeing the redundancy of the data stored in DDD 3 also in the cloud. This functionality allows real-time management of vehicles with positioning and speed of travel, in addition to the driver's information and current activity, except for the limitations of connection availability.

 An overview of the architecture of the DDD 3 solution can be seen through the diagram shown in Figure 1 and the detail of each device in the section that addresses the essential and functional requirements of the DDD solution 3.

 When purchasing equipment 1, it is necessary to attach the DDD to the chronograph 4, attach the DEP 1 to the vehicle cabin and register with the Backend 12 Servers of the solution, creating a user account and associating it with the equipment 1 purchased, the data of the vehicle , owner data and possible DDD 3 user drivers on that vehicle.

 In order to derive the requirements of the DDD 3 solution, the elements it provides for the exercise of the driver's license have been mapped and consolidated, particularly on the supervision of the driver's driving time, on the minimum technical requirements of the instantaneous and unchanging speed and time, and electronic time record, in addition to the standards dealing with the requirements of the chronograph 4 and the disk diagram 3 which establish the minimum conditions that satisfy the instantaneous and unalterable speed and time recording instruments and the parameters that establish the requirements to be met by the Electronic Point Recorder.

Thus, the essential elements of the cited standards and regulations are specific requirements directly correlated to the material or technology used for the Paper Diagram Disk as demarcated print areas for speed recording or manual filling by the inspector and driver or pertinent to the statically installed clock model in the companies, however, that guarantee the correct recording of the information, ensuring its fidelity, authenticity and credibility and providing the inspection bodies with precise conditions for the exercise of the inspection and analysis of accidents.

 Functional requirements describe the services that the DDD 3 solution must provide, respond to specific inputs, and behave in certain situations in order to faithfully record the data generated by the chronograph 4 and the driver's activity markings.

 Thus, DDD 3 shall record, simultaneously, unalterably and instantaneously, the speed and distance traveled by the vehicle as a function of the elapsed time, at a frequency of 1 register per second.

 The DDD 3 shall record the non-operation of the chronograph's clock 4 in the interval of at least 40 minutes.

 The DDD 3 solution must provide, at any time, when required, the data monitored by the chronograph 4.

 The DDD 3 solution must have a non-analog DDT 3 RTC display, containing hour, minute, and second.

 The DDD 3 solution should allow synchronization of the RTC using a GPS 5.

 The DDD 3 solution should record the occurrence of an inspection, identifying the inspector, the location and the date and time of the inspection act.

The DDD solution 3 shall allow the driver to record the current activity by confirming the biometric reading 15 of his fingerprint, containing the driver's identification, activity, time and place of registration. The DDD 3 solution should record the location at the time of registration of a driver activity.

 The DDD 3 solution must present the data referring to the last 24 hours of operation of the chronograph 4, totalizing the time of direction and the time of non-activity per driver, crossing the activities with the vehicle movement register.

 The DDD 3 solution must have a data storage medium necessary for its operation, containing the owner's data, such as name, document type, document, vehicle nameplate and mileage at the time of installation, in addition to the driver's data, , unique identifier, name, document type, and document.

 DDD 3 must have at least one year of energy autonomy.

 The DEP 1 must present to the driver, condition indicators of the battery 3B of the DDD 3 and condition of the battery of the DEP 1, that is, the status of the connection with the DDD, status of the connection to the mobile telephone network 10 and the status of the reception of the GPS signal 5 and further, the DEP 1 must have an interface for charging the internal battery.

 The non-functional requirements mainly describe the criteria for information security in order to allow the integrity of the programs embedded in the DDD solution 3, the authenticity and traceability of the relevant records, the influence of the user interfaces and communication between the solution devices DDD 3, secure data transmission and the hierarchy of embedded programs.

DDD 3 permanently records relevant operations or events, generating records of activity log operations 13, storing the unique driver identifier, activity identifier, time stamp, and coordinates GPS 5 and also records the owner's setup operations.

 Referenced DDD 3 also records the internal RTC tuning operations, storing the RTC data before and after the setting, the timestamp chronograph 4 event opening, the timestamp event DDD 3, and the connection between DDD 3 and any authorized device, containing the unique identifier of the device and a time stamp.

 DDD 3 stores data, with data retention capability recorded for at least 10 (ten) years, and provides the internal attributes such as the unique identifier, public key, and version of embedded applications.

 0 DEP 1 provides the internal attributes, such as the unique identifier, the version of the embedded applications, and the unique identifier of the DDD to which it is configured to connect.

 0 DEP 1, when connected to DDD 3, provides the unique identifier, public key and version of the embedded applications.

 DDD 3 must digitally sign the files stored in internal memory.

 The cryptographic keys for the digital signature of the DDD 3 files must be generated internally by dedicated 3E cryptographic hardware.

 The algorithm for digital signature, its respective level of security and the size of the generated key must be among those recommended by the competent authorities.

 DDD 3 has data access control mechanisms and intrusion protection for all interfaces.

DDD 3 is an electronic device designed to record and make available the data monitored by the chronograph 4, adding electronic point registration functionality.

 Analog to paper disk paper, it has been developed to be compatible with existing chronograph equipment, without the need for any adapter or auxiliary equipment.

 The data generated by the cronot plot 4 is captured by means of 3G sensors contained in DDD 3, at a frequency of 1 register per second. Processed, these data are timestamped and are safely stored by digital signature 14 in the non-volatile 3D memory of device 3, as well as the activity register commands 13, or point register, received by a wireless communication interface 2 , which are then attached to an internal RTC timestamp of DDD 3, signed by embedded cryptographic processor 3E, and stored in internal nonvolatile 3D memory.

 Clock movement of timer 4 is constantly monitored and, if no movement occurs within 40 minutes, DDD 3 generates a log record reporting the problem.

 The availability of the data stored by DDD 3 is ensured by 3C wireless communication modules that can be accessed by both a smartphone, Inspection Application 9, and the Standard External Device - DEP 1.

 Access to wireless interface 2 of DDD 3 is protected by a secure authorization protocol that allows, after correct identification, that the device connected to DDD 3 has restricted and selective access to the services, according to the type of authorization.

The services available in DDD 3 are listed in the table below: SERVICES DESCRIPTION AVAILABILITY

 PROVIDE THE CURRENT SPEED INFORMED BY THE CHRONOTECHNOLOGIST AND THE REQUIREMENT DISTANCE PERCURED SINCE THE MEASURE AUTHORIZATION. PREVIOUS.

 PROVIDES ACCESS TO THE SIGNED FILES CONTAINING THE RECORDS OF SPEED AND DISPLACEMENT DATA IN RELATION REQUIRES THE TIME GENERATED BY THE AUTHORIZATION. CHRONOTACOGRAPHER. EVERY FILE

 STORE 30 MINUTES OF INFORMATION.

 PROVE ACCESS TO LOG FILES WITH REQUIRED ACTIVITY RECORDS AUTHORIZATION.

INSERTED BY THE DRIVER,

 VEHICLE LOCATION, RECORDS

 OPENING AND CLOSING OF THE CHRONOTECHNOLOGIST, SYNCHRONIZATION OF

 RTC, OF CONNECTION WITH ANOTHER DEVICE

 SPEED AND EXTERNAL, AMONG OTHERS.

 DISTANCE

PROVIDE INFORMATION ABOUT INSTANT STATUS DDD OPERATION LIKE: BATTERY,

 DATA FILE REQUIRES MEMORY, OPEN CHRONOTECHOGRAPH OR

 OF AUTHORIZATION.

 CLOSED, MOVEMENT SENSOR

 CHRONOGRAPH WATCH AND VERSION OF FIRMWARE.

 LOGS DATA FILE PROVIDES ACCESS TO INTERNAL DDD RTC. NO AUTHORIZATION STATUS REQUIRED. DATE AND TIME PROVIDE ACCESS TO THE CERTIFICATE CONTAINING REQUIRED PUBLIC KEY TO THE PUBLIC CODE OF THE DDD. AUTHORIZATION. IDENTIFIER

PROVIDES ACCESS TO THE SINGLE IDENTIFIER OF THE UNIQUE REQUIREMENT OF DDD DDD. AUTHORIZATION. DDD MODEL SERIAL NUMBER REQUIRES

PROVIDES ACCESS TO THE DDD MODEL.

 OWNER AUTHORIZATION. SEND TOKEN PROVIDES ACCESS TO THE DDD SERIAL NUMBER. NO CHALLENGE IS AUTHORIZED.

LOG REGISTRATION

PROVIDES ACCESS TO CONFIGURATION DATA REQUIRES DDD OWNER WITH AUTHORIZATION SYNCHRONIZATION.

 VEHICLE INFORMATION.

 RTC

ENTRY INTERFACE FOR WRITING DOES NOT REQUIRE A TOKEN OF AUTHORIZATION. AUTHORIZATION.

PROVIDES READ AND WRITTEN ACCESS WHICH DOES NOT REQUIRE A CHALLENGE TO THE AUTHENTICATION PROTOCOL. AUTHORIZATION.

WRITE INTERFACE FOR REGISTRATION OF REQUER LOGS IN DDD HOW: REGISTRY OF ACTIVITY AUTHORIZATION WITH IDENTIFICATION OF THE DRIVER DEVICE AND REGISTRATION OF EXTERNAL LOCATION OF THE DDD SOLUTION. GPS DEP.

 WRITING INSTRUCTION INTERFACE

INTERACTION REQUIRES CONFIGURATION SENT BY SERVER AUTHORIZATION. BACKEND OF THE DDD SOLUTION.

 REQUIRED

PROVE INTERFACE SO THAT IT MAY BE AUTHORIZED TO SYNCHRONIZE THE DDD RTC BY THE GPS DEP. DEVICE. EXTERNAL

DDD SOLUTION. The DDD 3 is built on a printed circuit board with the dimensions of a traditional chronotegrapher's disk, adding 3A processors, 3D memory, 3F and 3G sensors, 3B battery and other electronic components required for its operation.

 0 DEP 1 is an auxiliary equipment, installed in the vehicle panel, which allows the driver to select and record an activity in DDD 3 before the correct reading 15 of the fingerprint of the same. An embedded GPS 5 signal receiver correlates the record of an activity to the location of the vehicle.

 The communication between the disk 3 and the external device is effected wirelessly by means of a wireless communication connection 2, following a secure authentication protocol.

 The data generated in DDD 3 is periodically sent to the DEP 1, which, by means of a connection to the mobile telephone network 10, synchronizes them with Backend Servers 12, whereby also configuration instructions are received, which are passed on to DDD 3 or interpreted locally if addressed to it. The packet of messages sent to the Backend Server 12 is signed by DEP 1 with the private key PVK_0, thus ensuring a source trace of the messages and the configuration commands are signed by the private key PVK_1, which make them authentic and reliable before the receiver.

 Since DEP 1 is constantly connected to DDD 3 to which it has been linked, it is necessary, in the case of an inspection, to select the inspection option in DEP 1.

When invoked this option DEP 1 sends the current location to the DDD 3 log file and then disconnects from DDD 3 so that Inspector 9 Application can connect and take the necessary approach. This situation reverts automatically in 10 minutes, or when reconnection is instructed by DEP 1.

 The DEP 1 also has the responsibility of keeping the internal clock 3F of the DDD 2 synchronized with the GPS 5 so that the difference between the two does not exceed 30 seconds. If an adjustment is necessary, the DEP 1 sends a time synchronization command to the DDD 3, which in turn adjusts the internal RTC and records a log of the occurred event containing the time before and after the adjustment.

 DEP 1 is internally composed of electronic modules 15 with readability 14 of the driver's fingerprint, connection to mobile telephone network 10, reception of GPS 5 signal, cryptographic hardware 3E, BLE 3C and processing unit 3A.

 Externally it has a communication interface with the driver by means of an LCD screen 16 and indicative lights 17 of operating status, allowing the interaction by means of navigation buttons BT, confirmation and cancellation of operations, besides the reading 15 of the fingerprint of the driver .

 In order for DDD devices to be in use, they undergo a pre-boot process (Figure 4), which is responsible for configuring some information that will be permanently stored in non-volatile memory, such as: the identifier model and serial number.

As shown in Figure 4, for DDD 3 and DEP 1 to be able to be used, they undergo a process responsible for configuring some information, which process starts 18 through the terminal configuration, from the serial connection 19 which demands a physical plug 20 provided in the DDD 3 and / or DEP 1 equipment, thus initiating the configuration 21. First, the system generates 22 public PU and private PR keys internally, more particularly in the cryptographic processor 3E PVK_0 and PBK_0, externalizing PBK_0 and the device identification number, only at the end of the server signing process.

 Following the configuration, the public key 24 and the device identifier 24 are sent to the server 12.

 Next, the public PUI and private PR1 public keys PVK_1 and PBK_1 are generated, generating 28 certificate X509 CERT_1 signed with PVK_CA.

 The identification of the device 26, generation 27 of the external public and private keys PUK and PR1 PVK_1 and PBK_1, and the certificate 28 X509 CERT_1 signed with generated PVK_CA, are recorded in the Data Center database 29.

 Subsequently, the certificate 30 is generated CERT_0 with PVK_1 and 31 x509 signed CERT_0 and signed CERT_1 and CERT_CA, then stored 32, ending this configuration process 33 or being saved 34 in the equipment.

 As mentioned above, the unique identifier of a device of the DDD solution 3 is the serial number obtained from the embedded cryptographic processor 3E, which has the uniqueness assurance stated in the hardware manufacturer's technical specification. The model and serial number are generated in the manufacturing process of the equipment.

 This process is also responsible for loading the firmware and initializing the internal and external cryptographic keys of the DDD 3 solution devices.

The generation of the pair of internal keys (used in the process of signing and verifying the authenticity and integrity of the files generated and stored internally in the devices) of the devices (PKV_0 PBK_0) is delegated to the cryptographic processor 3E, which uses algorithm of elliptic curve (ECC) encryption to generate them.

 By inherent characteristic of cryptographic processors 3E, only the public key is externalized, the private key being internally stored and restricted and exclusive access to the cryptographic processor 3E itself, according to figure 4.

 A pair of external keys (used in the process of signing and verifying authenticity and integrity of commands sent to devices) are also generated for the devices (PKV_1, PBK_1) using ECC encryption algorithms.

 Based on the public key PBK_0 and the unique identification of the device, a certificate is generated that is signed by the external private key of the same one, PVK_1, which in turn is signed by the root private key of the DDD 3 solution, PVK_CA, resulting in the following string of certificates that are stored in the device's permanent memory:

 CERT_CA 35 DDD Root Root Certificate 3.

 CERT_1 36 External device certificate.

 CERT_0 37 Internal device certificate.

 The pre-boot data is permanently written to the 3D non-volatile internal memory of the DDD device 3, which generates a log record containing a time stamp of when the process was completed. This data is also saved on the Backend Server 12 of DDD 3 solution along with the unique identifier, make, model, pair of foreign keys (PVK_1, PBK_1), and the internal certificate (CERT_0) of the device.

Figure 5 illustrates the connection between devices and is protected through an authentication protocol, using signed certificates that differs devices from the DDD 3 (Digital Diagram Disk) and DEP 1 (Standard External Device) solution between the such as smartphones with utility or surveillance applications, restricting authorization depending on the device type.

 When an External Device needs to establish a connection with DDD 3 or DEP 1 for the first time, it must request to Backend Server 12 a token, which is CERT_0 37 certificate from the requesting External Device signed by the private key PVK_1 of DDD 3 or DEP 1 target.

 To request a token to the Backend server 12, the external device at the beginning of the process 38 must select a target and identify it 40, that target may be authorized 41 or not.

 If allowed 42, a authorization token 43 CERT_035 signed by the target PVK_1 will be generated, and then the information "validates the token" 44 arises and the information "valid?" 45 so that said token 43 is validated 46 or not 47.

 If it is not allowed 48, in the identification of the device 49 and in the identification of the target 50, a new permission is checked 51 and, after the "authorized?" Information appears. 52 if allowed 53, the authorization of the token 43 is generated, however, if not 54, the process shows the expression "unauthorized" 55 is finalized 56.

 If the token 43 is validated 45, a challenge 57 is generated, then the expression "sign the challenge with PVK_0" 58 is displayed, after which 59 is signed with PVK_0 and, after signed 59 and validated 60, the expression "valid? " 61 which releases the authorization resources 63 and the process is terminated 56.

Otherwise, if the token 43 is not validated 46, the connection between the devices will not be established and the process will be terminated 56. As mentioned above, when attempting to establish a connection with DDD 3 or DEP 1 for the first time, a token 43, which is the CERT_0 35 certificate of the requesting External Device signed by the private key PVK_1 of the DDD 3 or DEP 1 target.

 This means that a unique credential will be created to be used specifically between the two devices involved in the authorization request process, being invalid for use in the connection between any other devices as shown in figure 5.

 This token 43 is then sent to DDD 3 or DEP 1 target, which in turn validates it using its CERT_1 certificate, which was configured at pre-initialization (Figure 4).

 If token 43 is valid, target DDD 3 or DEP 1 sends a random (bytes) challenge 57 to the requesting External Device, which must prove that it owns the token 43 sent by signing challenge 58 with its private key PVK_0. If the challenge is successfully completed, DDD 3 or DEP 1 releases the use of its resources according to the type of authorization granted according to each type:

 - Standard External Device: authorization used for communication between devices that allows the token holder 43 read and write access to the target's resources. Valid for 20 years.

 - Smartphone: used to authorize auxiliary applications to consume real-time target data without written permission. Valid for 30 days.

 - Supervisor: authorization used for supervisors (PRF, Inmetro and others), through the Inspection Application, to send commands to close and read files stored in the target. Valid for one day.

The diagram in figure 5 demonstrates the flow of authorization and authentication between the devices. To configure both DDD 3 and DEP 1, as shown in Figure 6, configuration instruction packets are sent by the DDD 3 Solution's Backend Server 12 to them. These commands are protected by the digital signature made by the PVK_1 external private key of the respective device.

 When a command is received, DDD 3 or DEP 1 validates it by verifying the signature with the public key PUI PBK_1 of CERT_1 36 that was inserted in DDD 3 equipment in the pre-boot of it. This process ensures that only authentic commands are executed on DDD 3 or DEP 1.

 6, through the Backend server 12, the configuration process 65 is started by creating a configuration command 66 which generates an instruction 67, said command to sign with PVK_1 68, then of signature 69, the command is received 70 by DDD 3 or by DEP 1, validating signature 71 with PBK_1.

 The expression "valid?" If the command is effectively validated, the instruction is executed 74, otherwise, at a negative 75, the instruction is invalid 76. In either case, execution is logged in the Logs file and communicates the result to the server which files the result, completing process 79.

 The flow of emission, verification and execution of instructions can be seen in the diagram of figure 6.

 The only configuration command DDD 3 receives is to update the owner's data. DEP 1 receives commands to update the list of available drivers and data synchronization parameters with the Backend Server 12.

The credibility of the DDD solution is to provide authentic and up-to-date data with irrefutable origin assurance. To achieve these objectives, the solution was developed using digital signature technology recommended by international bodies for digital signature of electronic documents in a dedicated 3E cryptographic hardware, which guarantees the non-violability of the private key that is stored internally in the cryptographic device itself 3E.

 In more detail, the DDD file signature process 3, shown in Figure 7, is initiated by inserting data files 81, which are stored by DDD 3, passing through a function 82 which generates a secure cryptographic summary , where the signature 84 of the summary using the ECDSA algorithm, generating a cryptographic summary 85 to add 86, then the signature to the data file, and after signed 87, the process is terminated 88. The diagram in figure 7 shows the process of signing the files.

 Integrity, authenticity and non-repudiation are guaranteed by digital signature verification using the public key (PBK_0) contained in the CERT_0 certificate belonging to the data originator. The diagram in Figure 8 illustrates this validation.

 Figure 8 shows the start 89 of the digital signature validation process with the signed data 90, the data signature 91 being subsequently separated, generating, on the one hand, the data 92 subsequently generating the summary function 93 through the SHA-256 algorithm and on the other, the cryptographic summary 94 by PVK_0.

 The abstract function, using the SHA-256 algorithm, establishes the abstract 95, at the same time as the cryptographic abstract 94 by PVK_0, decrypts 96 the abstract using ECDSA with the key PBK_0, generating new abstract 97.

The system compares the abstracts obtained 95 and 97 and verifies its identity 98. If it is positive 99, the data 100 becomes valid and the process is ended 101, whereas, if it is negative 102, the data is invalid 103 and the process is terminated 101.

 The CERT_0 35 certificate of a device can be consulted at any time via the device's own Bluetooth interface 2 or even on the company's data servers by means of a unique validated request against the chain of certificates that sign it in the pre-initialization of the equipment, as shown in figure 4.

 Visual inspection of the data generated by the chronograph 4 is done using an application installed on an Android smartphone. The inspector, after authenticating in the application through valid credentials, is able to establish a connection with any DDD 3 that is in inspection mode with a supervisor authorization, according to the connection of the devices.

 When connected to DDD 3, the road and log files of the last 24 hours are transferred to the Inspector Application 102, where validation and processing of the received data occurs. Information relating to the owner 104 of the DDD 3 is also collected which is displayed in the main screen 105 of the application 102, as shown in figure 9.

 The processed data is then presented in a line graph 106, which correlates the velocity with respect to time, allowing the visualization of the activity 107 recorded in relation to the speed and time of the vehicle, highlighting the active, inactive and unregistered ranges 108, as 10 is shown.

Also displayed are totalizers of activity and inactivity time 109, and a bar chart, to enable the visualization of the time intervals of each recorded activity, allowing the inspector to check compliance with the laws established in relation to the activities practiced by the driver, as shown in figure 12.

 The application allows the interaction of the monitoring user by selecting points in the graph, crossing the speed and time information, and displaying the distance from the selected point until the moment the supervision occurs among other details of the event selected as activity responsible driver, as shown in figure 11.

 If there is more than one driver with activities registered in the last 24 hours, it is possible to individually view the data recorded by the chronograph 4 for each driver, accompanied by cadastral data such as full name and driver's license number.

 All information displayed in the Inspection Application can be exported to an image that is saved on the smartphone of the inspector. This image can then be attached in the notice of infraction as document evidencing some irregularity, such as speeding or non-compliance with the laws of time of direction and mandatory stop.

 The DDD 3 solution unequivocally unifies the main instruments used to enforce the laws, norms and resolutions regarding the working hours of professional drivers and respect the speed limits established for the driven vehicle, adding to the chronograph the functionality of electronic point record.

Utilizing world-renowned security technologies, the DDD 3 solution stores the data collected by the chronograph 4 and the driver's activities in a digital manner ensuring reliability, traceability and integrity of the information exempting from the inspecting agent any doubts as to the correct interpretation of paper chart discs and on-board control card which in the DDD 3 solution are easily interpreted through a smartphone application.

 With the possibility of synchronizing the information for servers in the cloud, the DDD solution allows the monitoring and displacement of the vehicles remotely, besides serving as a source of redundancy of the data stored in DDD 3.

 The synchrony established between existing norms and guidelines, which deal with the control of the working day and rest of the professional drivers, and the guiding requirements for the design of the DDD 3 solution only project an adequacy in the existing regulations for the technological accommodation of the proposed solution .

 The adoption of the DDD 3 solution will contribute to the immediate modernization of the control systems, which are now totally dependent on the lagging disc technology, a paper diagram, present in the great majority of the fleet circulating in Brazil, which, despite the efforts, can not curb the abuse of long working hours that victimize both people and the public and private coffers, to a homogenic level, indifferent to the average age of the fleet, economically sustainable and digitally compatible with developed nations.

 Although the invention is detailed, it is important to understand that it does not limit its application to the details and steps described herein. The invention is capable of other embodiments and is practiced or performed in a variety of ways. It should be understood that the terminology employed herein is for the purpose of description and not limitation.

Claims

 1. "SYSTEM FOR READING, REGISTERING AND AVAILABILIZING DATA AND DRIVING PARAMETERS OF AN AUTOMOTIVE VEHICLE ADDED TO THE ELECTRONIC POINT RECORDING SYSTEM", which uses a DDD (3), used in a chronograph (4) for recording purposes parameters obtained by the needles (3H) of said chronograph (4); the DDD (3) having a processing unit (3A) and memory (3D), characterized in that the system has a standard external device DEP (1), positioned inside the vehicle, interconnected via wireless communication (2) to a DDD (3) coupled to a chronograph (4); in addition, other devices are interconnected to the DEP 1 and the DDD 3, such as GPS 5, the configuration terminal 6, monitoring and control terminals 7 and the driver's applications 8 ) and inspection (9), all connected to a mobile telephone network (10), the internet (11) and the cloud, in addition to the Backend servers (12). 2. A system for reading, registering and arranging data and driving parameters of an automotive vehicle added to an electronic point register system according to claim 1, characterized in that the standard external device DEP (1) is constituted by a processor 108 having flash memory 109, RAM 110 and a microcontroller 111, said processor 108 further including a SIM Card 112 and a Micro SD Card 113, processor 108), which is fed by a battery (114) and has, in turn, a serial interface (115) connected to a power center (116) where a battery charger (114) is positioned (114), in addition to a buck 118 and a boost 119; interconnected to the processor 108 of the standard external device DEP 1 are provided two interfaces 120 and 121, one internal 120 and one external 121 where the internal interface 120 has a circuit transmitter and the receiver (122) of the DDD (3), a GPS transmitter and receiver circuit (123) and an internet transmitter and receiver circuit (124); the external interface 121 in turn has a display 125, navigation selection keys 126, bell 127 and biometric data reader 128.  3. A system for reading, registering and arranging data and driving parameters of an automotive vehicle added to an electronic point register system according to claim 1, characterized in that the processor (3A) provided in the DDD (3) and DEP (1) via battery (3B), to power the wireless communication module (3C), the memory (3D), being non-volatile, the cryptographic hardware (3E), the clock movement sensor 3F) and the needles (3G) sensors (3H).  4. "SYSTEM OF READING, REGISTRATION AND AVAILABILITY OF DATA AND CONTROL PARAMETERS OF AN AUTOMOTIVE VEHICLE ADJUSTED TO THE ELECTRONIC POINT RECORDING SYSTEM, according to claims 1 and 3, characterized in that the needles (3H) of the chronotachograph (4) generate velocity and displacement data of the vehicle in (3F) of the DDD (3), this information being stored in the internal memory of the DDD (3) in form sequential files, signed by the cryptographic processor's private key (3E) inside the device. 5. A system for reading, registering and providing data and driving parameters of an automotive vehicle added to an electronic point recording system according to claims 1 and 2, characterized in that the information of the driver of the vehicle is recorded performed by the standard external device - DEP (1), whose interface (13) is confirmed by the positive reading of the biometric capture (15).  A system for reading, registering and providing data and driving parameters of an automotive vehicle added to an electronic point register system according to claim 1, characterized in that the standard external device DEP (1) (3), the register of the driver's activity (13), which in turn stores it in the log file, signed by the cryptographic processor (3E), by means of wireless communication (2), to the digital diagram disk DDD to send a location record obtained by a GPS processor (5) installed on the Standard External Device - DEP (1).  7. A system for reading, registering and providing data and driving parameters of an automotive vehicle added to an electronic point register system according to claim 1, characterized in that the logs of the installation, configuration, connection, opening and closing of the chronograph (4), among others, to be audited.  8. "READING, REGISTRATION AND AVAILABILITY SYSTEM OF DATA AND CONTROL PARAMETERS OF AN AUTOMOTIVE VEHICLE ADDED TO THE ELECTRONIC POINT REGISTRATION SYSTEM, according to claims 1 and 7, characterized in that the monitoring process uses a smartphone with an application (8) and (9).  9. A system for reading, registering and arranging data and driving parameters of an automotive vehicle added to an electronic point registration system according to claims 1, 2, 5 and 6, characterized in that the DEP (1) to have connection with the mobile telephone network (10). 10. SYSTEM FOR READING, REGISTERING AND AVAILABILITY OF DATA AND DRIVING PARAMETERS OF AN AUTOMOTIVE VEHICLE ADDED TO THE ELECTRONIC POINT RECORDING SYSTEM, from according to claims 1, 3 and 4, characterized in that the files generated by the DDD (3) are sent to the Backend Servers (12).  11. "SYSTEM FOR READING, REGISTERING AND AVAILABILIZING DATA AND DRIVER PARAMETERS OF AN AUTOMOTIVE VEHICLE The electronic point register system according to claims 1, 3 and 4, characterized in that the DDD (3) simultaneously and unalterably and simultaneously records the speed and distance traveled by the vehicle as a function of time frequency of one record per second.  12. A system for reading, registering and arranging data and driving parameters of an automotive vehicle added to an electronic point register system according to claims 1, 3 and 4, characterized in that the DDD (3) registers the time of the chronograph (4) in the interval of at least 40 minutes.  13. A system for reading, registering and arranging data and driving parameters of an automotive vehicle added to an electronic point registration system according to claims 1, 3, 4 and 12, characterized in that the solution DDD (3) ) provide, when required, the data monitored by the chronographer (4).  14. "SYSTEM FOR THE READING, REGISTRATION AND AVAILABILITY OF DATA AND DRIVER PARAMETERS OF AN AUTOMOTIVE VEHICLE The electronic point register system according to claims 1, 3, 4, 12 and 13, characterized in that the DEP (1) has a non-analogue display of the RTC of said DDD (3), containing hour , minute and second.  15. "SYSTEM OF READING, REGISTRATION AND AVAILABILITY OF DATA AND PARAMETERS FOR THE DRIVING OF AN AUTOMOTIVE VEHICLE ADJUSTED TO THE ELECTRONIC POINT RECORDING SYSTEM, according to claims 1, 3, 4, 12, 13 and 14, characterized by the fact that the driver registers the current activity by means of the confirmation of the biometric reading (15) in the DDD (3), containing the driver's identification, activity, time and place of registration.  16. "SYSTEM OF READING, REGISTRATION AND AVAILABILITY OF DATA AND DRIVING PARAMETERS OF AN AUTOMOTIVE VEHICLE ADJUSTED TO THE ELECTRONIC POINT REGISTRATION SYSTEM "according to claim 1 and 2, characterized in that the DEP (1) shows the battery condition indicators (3B) of the DDD (3) and condition of the DEP battery (1), the status of the connection to the mobile telephone network (10) and the reception status of the GPS signal (5).  17. A system for reading, registering and arranging data and driving parameters of an automotive vehicle added to an electronic point register system according to claims 1, 3, 4, 12, 13, 14, 15, 16 , characterized in that the DDD (3) permanently records the relevant operations or events, generating records of activity logging operations (13), storing the unique identifier of the driver, activity identifier, time stamp and GPS coordinates (5) Recording the internal RTC adjustment operations, storing the RTC data before and after the adjustment, the timestamp chronograph (4) opening event, the event of energizing the DDD (3) with timestamp and the connection event established between DDD (3) and any authorized device containing the unique identifier of the device and a time stamp.  18. "SYSTEM OF READING, REGISTRATION AND AVAILABILITY OF DATA AND CONTROL PARAMETERS OF AN AUTOMOTIVE VEHICLE ADDED TO THE ELECTRONIC POINT RECORDING SYSTEM, according to claims 1, 3, 4, 12, 13, 14, 15, 16 and 17, characterized in that the cryptographic keys of the DDD (3) files are generated internally by dedicated cryptographic (3E) hardware.  19. "SYSTEM FOR THE READING, REGISTRATION AND AVAILABILITY OF DATA AND DRIVING PARAMETERS OF AN AUTOMOTIVE VEHICLE The method according to claim 1, 3, 4, 12, 13, 14, 15, 16, 17 and 18, characterized in that the DDD (P) has access control mechanisms for the data and commands and protection against intrusion on all interfaces.  20. A system for reading, registering and providing data and driving parameters of an automotive vehicle added to an electronic point registration system according to claims 1, 3, 4, 12, 13, 14, 15, 16 , 17, 18 and 19, characterized in that the data generated in the chronograph (4) is captured by means of (3G) sensors contained in the DDD (3), at a frequency of one register per second, receiving a time stamp and stored by means (14) in the non-volatile memory (3) of the device (3), as well as the activity register commands (13), or point register, received by a wireless communication interface (2), which are then (3), signed by the embedded cryptographic processor (3E) and stored in internal non-volatile (3D) memory. 21. A system for reading, registering and providing data and driving parameters of an automotive vehicle added to an electronic point registration system according to claims 1, 3, 4, 12, 13, 14, 15, 16 , 17, 18, 19 and 20, characterized in that the clock movement of the chronograph (4) is constantly monitored and, if no movement occurs within a period of 40 minutes, the DDD (3) generates a log recording informing the problem . 22. A system for reading, registering and providing data and driving parameters of an automotive vehicle added to an electronic point register system according to claims 1 and 2, characterized in that the data stored by the DDD (3) are accessed through wireless communication modules (3C) via smartphone, with the Inspection Application (9) or the Standard External Device - DEP (1).  23. "SYSTEM FOR THE READING, REGISTRATION AND AVAILABILITY OF DATA AND DRIVER PARAMETERS OF AN AUTOMOTIVE VEHICLE (1) is internally composed of electronic modules (15) with biometric driver readability (14), connection to the electronic network mobile telephone (10), GPS signal reception (5), cryptographic hardware (3E), BLE (3C) and processing unit (3A).  24. A system for reading, registering and arranging data and driving parameters of an automotive vehicle added to an electronic point registration system according to claims 1, 2 and 3, characterized in that the assembly (1) has an interface of communication with the driver by means of a display (16), indicative lights (17) and navigation buttons (BT), confirmation and cancellation of operations.  25. "SYSTEM OF READING, REGISTRATION AND AVAILABILITY OF DATA AND CONTROL PARAMETERS OF AN AUTOMOTIVE VEHICLE ADJUSTED TO THE ELECTRONIC POINT RECORDING SYSTEM, according to claims 1, 2 and 3, characterized in that the road and log files of the last 24 hours when connected to the DDD (3) transferred to the Inspector Application (102), where validation and processing of the received data occurs and also to the owner 104 of the DDD 3 which are displayed in the main screen 105 of the application 102.  26. A system for reading, registering and arranging data and driving parameters of an automotive vehicle added to an electronic point register system according to claims 1, 2 and 3, characterized in that all information displayed in the Application Inspection are exported to an image that is saved on the inspector's smartphone, and is subsequently attached to the notice of infraction as a document evidencing some irregularity, such as speeding or non-compliance with driving time and mandatory stop laws.  27. A system for reading, registering and providing data and driving parameters of an automotive vehicle added to an electronic point recording system according to claims 1, 2 and 3, characterized in that the biometric data reader (128 ) of the external interface (121) of the standard external device DEP (1) is configured by digital.