Product Specs

Page 15 of 18

a permanent bond during the specified renting time period. When the renting period

has expired it will not automatically close the E-RL 2 but will not allow the renting

customer to unlock the Bike anymore. The permanent bond with the smartphone is not

transferable to a different smartphone since its using unique session keys exchanged

during the pairing and bonding process.

In case an OTP eKey certificate is requested from the KeySafe cloud the eKey is

returned including a list of OTP commands used to lock and unlock, each of these

OTP commands can only be used once and are transferable and not bound to the

smartphone that initially send the eKey certificate. OTP eKey certificate are mainly but

not exclusively intended for smartphones that do not allow the app to enter the passkey

through an API call to the OS. In the KeySafe-Cloud end node API documentation a

more detailed and thorough explanation of the different eKey types and there working

is given.

1.3 New functionality in eRL 2

The functionality of E-RL 2 has been increased by smart plugin detection, always close

push button functionality making it possible to close the E-RL 2 in all cases including

the case the mobile phone’s battery is dead. Figure 8 is showing the KeySafe API

extensions between the E-RL 1 and E-RL 2.

Figure 8.

The E-RL 2 makes use of the latest KeySafe-Cloud end node API interface giving full

control over the fleet from your own backend software. It’s possible to update the E-

RL 2 from within your mobile App during use without the customer being aware, no

interruptions in operation while updating.