Please help, I have a question and I need an answer.
You can use our Knowledge Capture app to leverage your team’s collective expertise. With the app, agents can: Search the Help Center without leaving the ticket Insert links to relevant Help...
The electronic key, also known as a mobile identifier, is the container of the U-PROX ID application, and it can be transferred to a reader of our production:
Electronic key (mobile identifier) – must be purchased for further registration in the U-PROX ID application on a smartphone, and registration in the ACS software to provide access via it.

– the logo of the old application (it can contain only 1 key of the same type)

– logo of the new accessory (may have more than one single key)
To register the key in your smartphone from a QR code, it is recommended to be in the 3G/4G(LTE)/5G network of the mobile operator to avoid possible restrictions on access to the licensing server in Wi-Fi networks.
According to the current technology, the key is registered in the “U-PROX ID” application on a smartphone and can be used in compatible systems where U-PROX SL/SE readers are used.
It is not possible to take it back from the smartphone, only to delete it in the application or together with the application, but the key is lost and cannot be re-registered.
The current versions of the U-PROX ID application have the ability to backup/restore (transfer) keys within the same Google or Apple ID account, the corresponding item in the application settings.
It can be used in ACS of our production:
Any identifier is registered in the ACS system by the user/administrator, regardless of the type or method of obtaining the identifier, and the option of issuing it to the client.
Mobile identifiers “U-PROX ID” can be provided for registration in the form of:
“QR codes are a link to a cloud server for uploading/validating mobile identifiers to the U-PROX ID application – one of 2 possible options for obtaining mobile identifiers.
Once mobile IDs are activated on a smartphone, they can be transmitted for reading by our readers via a channel:
Currently, U-PROX ID mobile identifiers are a one-time registration (permanent/network type), i.e., the key issued when deleted from the application is not re-registered.
The current versions of the U-PROX ID application have the ability to backup/restore (transfer) keys within the same Google or Apple ID account, the corresponding item in the application settings.
QR codes are distributed for registration directly to the U-PROX ID application – through the camera or as a file (archive with *.png files), and then the code is entered into the software manually and assigned to the user (again, the current version of the U-PROX software is recommended).
The QR contains all the necessary information that can be manually entered into the program database, depending on the system and software used (format and bit depth of the identifier).
Sample:

If you have U-PROX software version 3.52.1 or higher, you can specify the full 16-character code (HEX), and the program will display it accordingly – as a QR (something similar to the smartphone logo).
For other systems, or for lower versions of U-PROX software, it is enough to specify a 5-byte code (it will look like a regular card), in HEX or DEC format (or its subtype – F.C., “Facility Code”).

Executed on the page – http://mobileidorders.ddns.net/ml_validation
The identifier can be transmitted via Bluetooth (10cm – up to 15m) for Android and iOS smartphones, and NFC (1-8cm) for Android smartphones only.
Actions with the “mobile identifier” key, which is already registered on the smartphone, are similar to actions with ordinary plastic cards in the ACS program.
The mobile identifiers work with BLE-enabled readers manufactured by ITV Ltd. and released in 2018 (except for U-PROX keypad and U-Prox mini 485 models), and the current line of Smart Line readers (marked SL or SE).
Additional information:
When the “U-PROX ID” application is launched and the screen looks like this, this indicates the absence of ANY registered key – “mobile identifier”:



If you already have at least one of the possible keys (offline, network, encrypted) registered on your smartphone, the screen will look like this:


If you tap the “wallet” icon at the bottom right, the menu of registered keys will open, where you will see which types are already available in this smartphone/application:
| Key Personal / Autonomous | autonomous key (blue), free of chargeonly for autonomous use in U-PROX IP550/560 controllers (these controllers are out of production) there can be only one of this type in the application |
| Key Network / Network / Permanent | a regular network key (blue), only one of this type can be paid for in the application |
| Key Encrypted | encrypted network key (red), paid for by a system closed to other mobile keys, is obtained from encrypted QR or encrypted USB reader U-PROX Desktop (the “BLE cipher” field), there can be only one of this type in the application |


The Use by default checkbox indicates which of the available keys will be transmitted in the Lighted Screen mode.
For NFC transmission – the key selected for display on the main screen and application is used.
In the “U-PROX ID” request for “screen flicker” operation – specify which key to use for the customer.



Swipe left/right to select the registered different types of keys available on your smartphone/application.
The main menu will display the registered keys, including the keys that have been registered:
| Key Personal / Autonomous | standalone key, free of chargeonly for standalone use in U-PROX IP550/560 controllers (these controllers are out of production) |
| Key Network / Network / Permanent | regular / network / permanent key, paid |
| Key Encrypted | encrypted network / permanent key, paid for systems that are closed to other mobile identifiers (received from encrypted QR or from an encrypted USB reader U-PROX Desktop (field “Encrypt Mobile ID (BLE)”) |



You can also use U-PROX ID widgets for Android and IOS platforms, and install the widget on Apple Watch:

There is no difference in the logic of operation/registration of a mobile key on Android or iOS.
Actions with the “mobile identifier” key, which is already registered on the smartphone, are similar to actions with ordinary plastic cards in the ACS program.
The “mobile identifier” key, the container of which is the “U-PROX ID” mobile application, can be obtained:
For autonomous systems of U-PROX IP550/IP560 controllers – when using the U-Prox Config mobile application, actions are sent via messengers or e-mail, and autonomous keys are created (see the procedure in the relevant device documentation).
For all other options, keys are paid:
In the USB reader U-PROX Desktop – there are 5 pcs. prepaid,
Get a mobile identifier in the form of QR codes and register it in the application by scanning the code or opening a graphic file of the corresponding code.
Repeated keys from a QR code are NOT registered.
Mobile ID keys are supposed to ensure the uniqueness of the number, and therefore they are essentially a one-time registration – reuse for registration is NOT possible!
If the smartphone with the installed application and registered keys is reset to factory settings, the same is true if the gadget is “flashed”, or the U-PROX ID application is simply deleted, all keys (offline, network, encrypted) are lost. It is NOT possible to re-register them.
However, the current versions of the U-PROX ID app have the ability to backup/restore (transfer) keys within the same Google or Apple ID account, the corresponding item in the app settings.
For older versions of the application, the only way to save the key is to back up all smartphone data using the capabilities provided by the manufacturer of the device and then restore this data.
USB reader U-PROX Desktop – comes with 5 prepaid mobile identifiers, you need to use them:
Create a master card in U-PROX Desktop:
Issue a mobile ID from U-PROX Desktop:
When setting up U-PROX Desktop – we do NOT recommend entering data in the “BLE password” field, otherwise it will issue encrypted mobile keys
The need to enable GPS (Geolocation) is related to the technology used for communication between the smartphone and the reader, namely BLE (Bluetooth low energy, a subset of Bluetooth 4.xx).
This is a requirement of the Android (starting from 6.0) and iOS operating systems and the BLE technology stack, and it is impossible to get around it.
Similar applications from other vendors, such as Nedap and HID, that work with mobile tags also require GPS (Geolocation) to be enabled.
In Android devices, you can use an alternative method of transferring a mobile tag to the reader – via NFC.
We do not use GPS (Geolocation) data in any way, do not store it, and do not process it.