BLUETOOTH LOW ENERGY E-RL 2 LOCK PRODUCT SPECIFICATION Draft Version 1.00 1/03/2019 AXA Bike Security EnergieStraat 2 3903 AV Veenendaal Netherlands http://www.axabikesecurity.
Page 2 of 18 Disclaimer The information contained in this document is believed to be correct and complete. However, AXA Stenman Nederland B.V. (“AXA”) does not give any representations or warranties, expressed or implied, as to the accuracy or completeness of such information or as to its suitability (for products) and shall have no liability whatsoever for the consequences of use of such information.
Page 3 of 18 FCC/SED Regulatory notices Modification statement AXA Stenman Nederland B.V. has not approved any changes or modifications to this device by the user. Any changes or modifications could void the user's authority to operate the equipment. AXA Stenman Nederland B.V. n'approuve aucune modification apportée à l'appareil par l'utilisateur, quelle quén soit la nature. Tout changement ou modification peuvent annuler le droit d'utilisation de l'appareil par l'utilisateur.
Page 4 of 18 Table of Contents 1. INTRODUCTION .............................................................................................................................. 5 1.1 QUICK OVERVIEW OF BLUETOOTH LE ..................................................................... 5 1.1.1 Application Perspective................................................................................... 5 1.1.2 Services...................................................................................................
Page 5 of 18 1. Introduction The Bluetooth Low Energy Wireless E-RL 2 lock can be controlled directly through standard Bluetooth LE communication without the need for a proprietary communication stack. Bluetooth Low Energy sometimes referred to as Bluetooth LE or Bluetooth 5 is a new technology completely different and not compatible with Classic Bluetooth that has been around since 2001.
Page 6 of 18 Central vs. Peripheral: The peripheral device has valuable information to share with central devices. The central device treats the received data to fulfill specific tasks. Figure 1. Figure 1 is giving an overview of the different roles, so what is the difference between a client and a server? First let me remind you that a client and a server is not interchangeable with master/slave. Figure 2.
Page 7 of 18 Exiting this particular sleeping state the E-RL 2 needs to be woken-up by a simple button press on the side of the lock to start it advertising again during a set period. The smartphone app will now be able to detect the advertising packets and act accordingly depending on the relationship with the E-RL 2. Figure 3. In real-life situations smartphones (Central) will be surrounded by peripherals broadcasting (Advertising) their presents, see Figure 3.
Page 8 of 18 the role of “Slave”. “Master” devices will initiate commands and requests to “Slave” devices which will respond. One of the first task of a Bluetooth LE application, such as on a smartphone app, is to discover other Bluetooth LE devices that it can connect to. 1.1.2 Services Once a device has been discovered the next task is to figure out what services are offered by the device.
Page 9 of 18 You can easily see that it is possible for a device to be a GATT server and a GATT client at the same time. While it is most common for the slave (peripheral) device to be the GATT server only and the master (central) device to be the GATT client, this is not required. The GATT functionality of a device is logically separate from the master/slave role.
Page 10 of 18 Some other related attributes are read-only (such as a Characteristic User Description attribute), some control the behavior of the characteristic (such as the Client Characteristic Configuration attribute which is used to enable notify or indicate operations). Every attribute has a UUID. These may be either 16 bits (e.g. “0x180A“) or 128 bits (e.g. “00001530-1212-EFDE-1523-785FEABCD123 “). All 16-bit UUIDs are defined by the Bluetooth SIG and are known as adopted UUIDs.
Page 11 of 18 A central is a device that initiates connections to peripherals. As such, it becomes a master when connected. Just like a peripheral, a central needs to have both a transmitter and a receiver. We explained before that since the E-RL 2 has adopted the role of peripheral device the smartphone will need to accept the role of central in this system.
Page 12 of 18 be exchanged using the bonding procedure, but that does not mean they are bonded if the keys are not stored and used the next time. If a device is bonded with another device, like a heart rate monitor and a smartphone, they can encrypt the connection without exchanging any sensitive security information.
Page 13 of 18 Figure 6. The Bluetooth low energy channels differ from classic channels because of the relaxed modulation index. This means that the radio energy for each channel is spread wider; therefore, to prevent interference between adjacent Bluetooth low-energy channels, they are separated by 2MHz, instead of the classic 1MHz. In the Link Layer, these channels are divided into two types: advertising channels and data channels.
Page 14 of 18 When in a data connection, an adaptive frequency-hopping algorithm is used. Adaptive frequency hopping makes it possible for a given packet to be remapped from a known bad channel to a known good channel so that the interference from other devices is reduced. To do this, a channel map of good and bad channels is kept in both devices.
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.
Page 16 of 18 2. E-RL 2 Profiles The E-RL profile is offering the following 5 Standardised and non-standard services: The Standardised Service, which consists of: o Generic Access Service. (Mandatory for all BLE devices) o Generic Attribute Service. (Mandatory for all BLE devices) o Device Information Service. The Non-standard Service, which consists of: o KeySafe Cloud Service. o Device Firmware Update Service.
Page 17 of 18 together with the software and firmware revision strings during the device firmware update process. 2.2 KeySafe Cloud Service The device specific E-RL 2 KeySafe Cloud Service is a non-standard Bluetooth service that exposes an interface for the operation and control of the E-RL 2. In the KeySafeCloud end node API documentation a more detailed and thorough explanation of the operation of this vital service is given. 2.
Page 18 of 18 3. Electrical Characteristics Absolute Maximum Electrical Ratings(†) Characteristic Ambient temperature under bias Ambient temperature during operation Supply Voltage Vdd pin with respect to Vss (Idle) Supply Voltage Vdd pin with respect to Vss (Running) Supply Voltage Vdd pin with respect to Vss (Stall) Supply Current Vdd pin Peak (10s) Supply Current Vdd pin @ 3V (Stall) ESD protection on all pins (HBM; MM) -25°C to +85°C -20°C to +55°C 3.7V 3.7V 3.
