Difference between revisions of "RFID tags"
(→Supported RFID Tags) |
|||
| Line 22: | Line 22: | ||
! Standard!! Tested Tag technologies | ! Standard!! Tested Tag technologies | ||
|- | |- | ||
| − | | | + | | NfcA (RFID standard: ISO-14443A) {{Version/AndroidSince|2.4.2}} || EV1(MFOUL11), NTAG 203(F), NTAG 216, NTAG 210, NTAG 213 |
|- | |- | ||
| NfcB (RFID standard: ISO-14443B) {{Version/AndroidSince|2.4.5}} || - | | NfcB (RFID standard: ISO-14443B) {{Version/AndroidSince|2.4.5}} || - | ||
| Line 30: | Line 30: | ||
|} | |} | ||
| − | [[ | + | |
| − | + | == NFC Scan Result Type == | |
| − | + | Depending on the [[Settings#AR_settings|NFC Scan Result Type]] setting, {{UBIK}} can extract different types of information from a scanned RFID tag: | |
| − | + | ||
| + | {| class="wikitable" | width = "100%" | ||
| + | |- | ||
| + | ! NFC Scan Result Type !! Comment | ||
| + | |- | ||
| + | | Identifier (Hexadecimal) {{Version/AndroidSince|2.4.2}} || Extracts the write-protected identifier of a scanned tag in hexadecimal form. The identifier is given by the manufacturer and can´t be manipulated. | ||
| + | |- | ||
| + | | Content (Hexadecimal) {{Version/AndroidSince|3.0.0}} || Extracts the raw content of a scanned tag in hexadecimal form. Not supported on the Getac Z710. NfcB tags are not supported. | ||
| + | |- | ||
| + | | Content (ASCII) {{Version/AndroidSince|3.0.0}} || Extracts the raw content of a scanned tag in ASCII form. Not supported on the Getac Z710. NfcB tags are not supported. | ||
| + | |- | ||
| + | | Content (NDEF) {{Version/AndroidSince|3.0.0}} || Extracts NDEF messages of type "Text" or "text/plain" from a scanned tag. Not supported on the Getac Z710. | ||
| + | |- | ||
| + | |} | ||
== Configurable start screen RFID button == | == Configurable start screen RFID button == | ||
| Line 128: | Line 141: | ||
[[Category:2.4.0|RFID tags]] | [[Category:2.4.0|RFID tags]] | ||
[[Category:Android|RFID tags]] | [[Category:Android|RFID tags]] | ||
| − | |||
[[Category:Version 2.5|RFID tags]] | [[Category:Version 2.5|RFID tags]] | ||
| + | [[Category:WinX|RFID tags]] | ||
| + | [[Category:Version 3.0|RFID tags]] | ||
Revision as of 12:09, 13 November 2017
Android
In order for the users to find objects more efficiently, UBIK® objects can be marked with values for RFID codes. Whenever a user scans an RFID code, the resulting code value can be used to find all matching objects, namely objects that have the right property.
This feature is available since Version 2.4.2 - Android .
Introduction: RFID & NFC
NFC stands for "Near Field Communication" and is a set of ideas and technologies for data transfer between devices, typically in close distances. Technically, it is based on RFID ("Radio-Frequency Identification"), which describes specific technical solutions.
Amongst the use cases for NFC, there is communication between smartphones and other devices, but also the scanning of RFID tags.
The UBIK® RFID scanning feature specifically is the ability to scan RFID tags in order to identify UBIK® objects.
Supported RFID Tags
There are three types of RFID markers supported by UBIK®:
NFC Scan Result Type
Depending on the NFC Scan Result Type setting, UBIK® can extract different types of information from a scanned RFID tag:
Configurable start screen RFID button
In order to use this feature, a RFID scanning entry point is provided using a configurable start start screen button. The following xml shows an example start screen configuration including RFID scanning entry point:
<Tab caption="Content">
<ContentBrowserButton caption="Content Browser"/>
<RFIDScanButton caption="RFID Scan" />
</Tab>
</StartScreenConfiguration>
Scanning an RFID tag
Once the RFID button in the start screen is clicked, the corresponding RFID scanner starts. The user is then able to scan RFID tags continuously.
Presenting results of a search
Once the ID of the tag is scanned, UBIK® starts searching for objects with the scanned RFID.
- During the search, the list might show a searching text before any objects are found;
- If any objects are found, they will be displayed in a list. The users can then browse to any of the objects for more information by clicking on the objects;
- If no objects are found, the list will show a corresponding text.
Searching Mechanism
UBIK® provides two mechanisms for searching objects: online and offline.
Searching offline
In any case (regardless of the network connection and sync mode), UBIK® always goes through all the objects currently available on the device and find the ones that match the scanned results.
Searching online
When the Internet is avaiable and UBIK® is not running under offline mode, the search result is enhanced by online search. This means any objects that match the scanned results can be found even if they don't yet exist locally.
Technical background
In order for objects to be identifiable through RFID, they have to carry the SYSCLS OBJECTWITHRFIDTAG classification.
The service query used for online searching is SYSCLS RFIDTAGSCANQUERY.
See also
WinX
This feature is available since Version 2.5.4 - WinX.
Supported RFID Tags
There are three types of RFID markers supported by UBIK®:
- NfcA (RFID standard: ISO-14443A)
- NfcB (RFID standard: ISO-14443B)
- NfcV (RFID standard: ISO-15693)
UBIK® WinX scans these tags for a NDEF message. Tags which are not NDEF formatted are not supported by the WinX client.
Scanning an RFID tag
A NFC Scan button is shown in the Global App Bar if the device is capable of scanning NFC tags. Pressing the NFC Scan button enables/disables NFC scanning throughout the whole application. That means once the NFC scanning is activated, one can use the application just as usually while UBIK® scans for NFC tags in the background.
Presenting results of a search
Once a tag is successfully scanned, an object search is executed based on the tag´s NDEF message.
- if no objects are found a message is poping up at the right side of the screen.
- if more than one object is found the results are represented in a dialog along with their matching probability. One can than select one object that should be opened in the content browser.
- if exactly one object is found, this object is directly opened in the content browser.
