In the following, the procedure of use via various customer media is explained. This includes, in particular, communication from and with CCom.
The reservation/fleet management system sends the reservations to CCom up to 7 days before the start of the reservation. The server then tries to send the reservation (immediately) via TCP to the corresponding on-board computer. If SMS fallback is activated via configuration, the message is also sent by SMS if it is not possible to send it via TCP (maximum 30 minutes before the start of the reservation).
At the same time, CCom transmits the reservation to the user’s app as soon as it connects to CCom via the Internet (when the app is started or tapping onto the “refresh” button). If the AppLib is integrated with a host app, a host app command triggers this process. The reservation is transmitted to the app via HTTPS. The “reservation token”, which is forwarded to the on-board computer, is end-to-end encrypted and cannot be decrypted by the app. To display information and identify the reservations through the app, some reservation details (start and end time, reservation ID) are disclosed to the app.
The current location of the vehicle can be transmitted to the server at the end of the previous use and displayed in the user’s app. The user goes to the vehicle. The devices in the vehicles regularly send advertisements via Bluetooth. The corresponding reservation displays “Nearby car” as soon as such advertising is received.
The user then selects the reserved vehicle in the app, after which a connection to the car is established. If messages are available for exchange between app and device (e.g., an encrypted reservation token), they are now transmitted. The user can log in, i.e., unlock the vehicle and drive off (the immobilizer is unlocked).
While driving
- If the vehicles are configured for the “keyless” mode (i.e., car has no key or the key is not monitored with C-Intac), the user can unlock and lock the vehicle while driving via the dedicated buttons in the app.
- In “Key detection” mode, the user is supposed to use the car key only to unlock and lock the vehicle during the trip.
End of journey
- To finish the reservation, the user taps onto «End reservation» button in the app. In “Key detection” mode the car key must be inserted back into the C-Intac key holder in the glove compartment to process this command. In «Keyless» mode (i.e., vehicle has no key or the key is not monitored with C-Intac) this condition is not required.
- In addition to this information and functions, the app can also display a dashboard that contains information about the reservation, e.g., mileage and charge level. This allows the customer to check his driving data via app at any time.
Use with RFID cards/badges
The user goes to the vehicle and logs in with the RFID card by showing the card on the card reader. If access is granted, the vehicle is unlocked and the user can drive. The LED of the device flashes 2x to signal the successful login.
While driving
- If the vehicle is configured for the “key-less” mode (i.e., car has no key or the key is not monitored with C-Intac), the user can lock and unlock the car while driving with the RFID card/badge.
- In “Key detection” mode, the user is supposed to use the car key only to unlock and lock the vehicle during the trip.
End of journey
- To finish the reservation, in “Key detection” mode, the car key must be inserted back into the key holder “C-Intac” in the glove compartment at the end of the journey. This signals the end of the reservation and enables the card reader to allow locking of the vehicle.
- In “Keyless” mode (i.e., vehicle does not have a key or the key is not monitored with C-Intac) this is not required. The reservation is automatically terminated when the next user starts the reservation or, depending on the configuration, when the end time of the reservation has been reached.
Driving data and event transmission
The trip data will be returned to CCom after completion of the reservation. Depending on the system configuration, partial driving data, e.g., at each logout event, or event data, e.g., “ignition on/off”, can be transmitted to the server while driving. In addition, data on vehicle state, vehicle usage information and location information can also be requested at any time.