Device Configuration Hierarchy

The Device Configuration hierarchy attributes are primarily used to track the Badge and Communicator mobile client configuration telemetry. The device configuration telemetry is tracked at the transactional level. Each Badge transaction records the exact operating system​, device,​ and ​mobile​ configuration. Therefore, the historical upgrade or modification of the device configuration is recorded. To see the latest device configuration for a user, sort descending on the Timestamp attribute. 

For MicroStrategy transactions, the unique Device​ configuration is tracked. The ​Device Type​ and ​Device Category​ are always defined as a static value, but the Device is populated with the IP of the client that the MicroStrategy transaction occurred from. 

lu_device

The ​Device​ stores the unique ID and name/IP of the client device with which a users performs an action. For Usher iOS clients, the device_desc is the name registered on the mobile device. For Usher Android clients, the device_desc is the name of the model. For MicroStrategy clients, the name is the IP address from the client. 

The Device ID is always unique for both Usher and MicroStrategy client actions. For Usher, the ID is generated by Usher Server. For MicroStrategy, the ID is auto-generated by Platform Analytics ETL. 

Column	Description	Data-Type
device_id	The auto-generated ID of the Usher device or MicroStrategy Session Source IP address.	bigint(20)
device_desc	The description of the Device. The description can vary depending on the source (Badge iOS, Badge Android, or MicroStrategy Session Source).	varchar(255)
device_type_id	The corresponding Device Type ID for the Device.	bigint(20)

lu_device_type

The Device Type records make and/or model of the phone, tablet, or computer used to perform a Badge action. All MicroStrategy actions are assigned a static Device Type of Personal Computer. 

Column	Description	Data-Type
device_type_id	The auto-generated numeric ID of the Device Type.	bigint(20)
device_type_desc	The descriptive make and/or model of the phone or tablet. All MicroStrategy actions are assigned a static Device Type of Personal Computer. For example,  iPhone Google Pixel  LG-D820	varchar(255)
device_category_id	The corresponding Device Category ID.	int(11)

lu_device_category

The Device Category records the grouping of device types. All MicroStrategy actions are assigned a static Device Category of Personal Machine. 

Column	Description	Data-Type
device_category_id	The fixed numeric ID of the Device Category.	int(11)
device_category_desc	The fixed description of the Device Category. The elements include: Android iPhone iPad Tablet Personal Computer Not Applicable	varchar(255)

lu_os

The ​OS ​is used to record the exact operating system which is on the Badge app or Communicator app used in an Identity transaction. The ​OS​ is tracked at the transactional level, therefore, each Identityaction will record the unique OS version and OS Category. 

MicroStrategy transactions do not record the client OS information and are mapped to a default Not Applicable. 

Column	Description	Data-Type
os_id	The auto-generated ID of the OS.	bigint(20)
os_desc	The description of the OS installed on the Usher Client. For example,  Android 8.1.0 iOS 11.2.5	varchar(255)
os_category_id	The corresponding OS Category ID.	int(11)

lu_os_category

The OS Category ​is used to record the type of operating system which is running on the Badge app mobile client. The ​OS​ is tracked at the transactional level, therefore, each Badge action will record the unique OS version and OS Category. 

MicroStrategy transactions do not record the client OS information and are mapped to a default Not Applicable. 

Column	Description	Data-Type
os_category_id	The fixed numeric id of the OS Category.	int(11)
os_category_desc	The descriptive form of the OS Category. The OS Category includes: Android iOS OS x Not Applicable	varchar(255)

lu_mobile_app

The ​Mobile App ​records the exact Mobile App version on the Badge users’ device during a transaction. The ​Mobile App​ is tracked at the transactional level, therefore, each Badge action will record the unique app version. 

MicroStrategy transactions do not record the Mobile App information and are mapped to a default Unknown. 

Column	Description	Data-Type
mobile_app_id	The auto-generated numeric ID for the Mobile App.	bigint(20)
mobile_app_desc	The Mobile App version installed on the Badge users’ device. The Mobile App version will change as the user upgrades the app version. An example of Mobile App includes: Badge/10.10.101 Communicator/10.10.002 Not Applicable	varchar(50)
mobile_app_category_id	The corresponding Mobile App Category ID.	tinyint(4)

lu_mobile_app_category

The ​Mobile App Category ​is used to record the type of Mobile App which is running on the users mobile client. The ​Mobile App​ is tracked at the transactional level, therefore, each Badge action will record the unique Mobile App version. 

MicroStrategy transactions do not record the Mobile App information and are mapped to a default ‘Unknown’. 

Column	Description	Data-Type
mobile_app_category_id	The fixed numeric ID for the Mobile Category	tinyint(4)
mobile_app_category_desc	The descriptive form of the Mobile App Category. The Mobile App Category includes: Badge Door Reader Communicator WatchKit Not Applicable	varchar(255)