Once a mobile device is connected to the server, the device will continuously send information about itself.
This provides the central system with information on usage of battery, network connections, GPS, etc.
It also allows us to interact with the device using action messages and commands.
1 Device Information
Additional features / Mobile Devices / Reports / Device information
Show all metrics of the device's most recent connection.
This Device Details report contains a link under Device UUID.
1.1 Device Details
"Device Details" provides full device information.
Mobile device identifier, unique for each device.
|Device description||Description of mobile device|
Used to enable or disable a device.
|To wipe||Indicates if device data must be wiped
|Wiped||Indicates if device data has been wiped
Indicator used to force-refresh all information associated with the device (version code, version name, OS name, locale, etc.)
|Pending messages||Pending messages|
|BUTT_RESET_STATISTICS||Reset statistics||Reset number of access and reset number of soap errors|
|BUTT_NEW_MESSAGE||New message||Create a message to the device|
2 Device Commands and Messages
Commands can be sent remotely to a mobile device with the
Axional Mobile application installed.
These commands consist of a set of instructions to be performed by the terminal.
Commands may be sent from:
* SOAP: device-server communication. During any type of communication between device and server, the system checks if the device has pending messages. If so, the messages are sent on to the device.
* SMS Messages: only for phones with SIM cards.
When a device receives a message, it is inserted into the table core_server_messages. A cron service is responsible for periodically checking the table, and for executing the commands sequentially.
This maintenance allows us to keep a record of messages that will be sent to a device.
Messages contain actions which the device must process and execute.
During every ping connection, the device will check for messages. If one exists, the device will save and execute it, and the process will be stored in a table and pulled to the server. This informs the server if the message was or was not correctly processed.