|
Automatic Pairing/Staging |
  
|
Automatic Pairing/Staging
|
Automatic Pairing/Staging |
|
Overview
Automatic Pairing and Automatic Staging are ONLY available for Android devices with camera.
Automatic Pairing/Staging uses a QR code, generated in the destination device group.
The QR code includes pairing information (the device group's identity/location) by default, but it can also contain staging information (ex: If the device group has defined network profiles, that information will also be contained in the QR code). Basically, the QR code will include the pairing information and the staging information that is available at the time it is generated.
Once the device reads the QR code, the required settings are delivered/installed and the device is configured accordingly to establish a connection to the MCL-Mobility Platform account, specifically, to the intended site/device group.
The QR code used in the Automatic mode can have multiple purposes:
•To simply connect the device to a specific device group (ex: establish the initial connection of the device to the MCL-Mobility Platform account).
•To deliver network profiles that will be applied to a device so it uses the correct settings to communicate with the account (ex: to set the wifi network to be used; to provide/configure a different wifi network because the device needs to use another one).
•To move a device onto another compatible device group (ex: the device was included in the "Day Shift" device group and, now, has been assigned to an operator from the night shift and must be moved to the corresponding "Night Shift" device group). See Moving a Device.
The pairing/staging is performed, simultaneously, in the MCL-Mobility Platform and in the devices you want to pair with the account.
Android devices can be paired to a specific device group (compatible with the paired device's manufacturer/model/OS) OR the devices can be paired to the "Unassigned" device group - a default device group that can include all device types and OS but whose devices are automatically disabled.
Pairing devices with the "Unassigned" device group implies they will have to be moved to a compatible device group and have their status enabled, if you want to work with them. Operationally speaking, those devices will only communicate with the account to check if their status has changed.
The steps to pair/stage a device to a specific device group or the "Unassigned" device group are different, so follow the appropriate link:
Automatic Pairing/Staging onto a Device Group
Automatic Pairing/Staging onto the "Unassigned" Device Group
This method is NOT available for Windows Mobile/CE devices - these devices can ONLY use the Manual Pairing or Mass Pairing methods to pair with the MCL-Mobility Platform account/be configured.
See WM/CE File Pairing/Staging
During a Staging process (or when using MCL applications), you may be required to allow the use of the camera, storage, phone, microphone, location, or any other setting according to the application's needs. This is valid ONLY for devices with MCL-Agent v4.10 or above and it is manufacturer/device dependent - certain manufacturers/devices already have these permissions enabled by default.
Permissions can be granted when requested (ex: while running an MCL application, you may get a pop-up window requesting you grant a specific permission) or manually (access the MCL App Desktop menu, select "Permissions" and grant the intended permissions.
Once a permission is granted, it CANNOT be revoked.
Sometimes, when performing a staging, the system might not request a permission, such as the use of the device's camera, although it is necessary to that operation. In those cases, you can access the "Permissions" option of the MCL App Desktop menu and grant the intended permission(s) manually.