How eHealth stores speeds and user set speeds (override speeds).

Document ID : KB000023171
Last Modified Date : 14/02/2018
Show Technical Document Details


There are two DCI fields for speeds, but 3 in the database. Which are equivalent, and what do they mean?



There are 2 ways eHealth can get a speed for an element. Through discovery and from a user-set value (called the override speed because a user setting should override the discovered setting).
In DCI, we have speedIn and speedOut, as well as deviceSpeedIn and deviceSpeedOut.

These match up to the database fields thus:

 DCI field      |        DB field
speedIn         =    override_speed
speedOut        =    override_speed1
deviceSpeedIn   =    device_speed
deviceSpeedOut  =    device_speed2

The DB also has a third speed field pair, speed and speed1. These are "meta" values. Where the device_speeds are the discovered speeds of an element and override speeds are those set by the users, the speed/speed1 pair is what value eHealth stores the speed it uses for bandwidth calculations, etc. If the override speed is not set, speed=device_speed and speed1=device_speed1. If the override speed(in, out or both) are set, then the speed/speed1 matches these. This way eHealth does not have to "decide" every calculate which speed to use, it simply stored in a third pair. If it is found that this is not the case, please contact CA Technologies Support for further assistance.