The technical principles of the nfc anti-forgery program and the landing path
RFID Knowledge

The technical principles of the nfc anti-forgery program and the landing path

PublishedShanghai Zejie Smart Technology Co., Ltd.

Core judgement:NFC protection is not so simple as "a chip" but connects the chip identity, dynamic validation, back-office records and field operations. The common approach is based on 13.56 MHz close communication, which should be driven five steps by "label selection key to data design - interface development - pilot validation - batch retroactive".

Point 1: Disassembly the NFC's hypocritical work into four layers.

The NFC labels are usually made up of antennas, chips and sealed materials. When a mobile phone or reading/writing device is near the label, you use 13.56 MHz radio field to power or communicate, and you read the identifying information in the labels. The passive tag does not need batteries, the reading distance is normally within a few centimetres, the specific distance is subject to antenna size, the packaging of material, the reading/writing equipment and the environmental impact on the site.

Consumer scans are only a display of results. The real decision about the level of security is whether the backstage can verify the authenticity of labels, whether they recognize the number of anomalies and whether tag data have dynamical ability to change.

Element 2: Replace "fixed numbering to protect against forgery" with dynamic authentication

Fixed numbers are suitable for basic traceability, not for a single security mission. A more secure approach is to involve labels or readers in a dynamic calculation: the device sends random numbers, the security chip calculates authentication results based on internal keys, and the back-office verification results match. Each random number varies, it is difficult to copy a set of historical data directly through the next validation.

Programme Applications Main limitations
Fixed UID or Serial Number Basic retroactive, batch management, simple information presentation Data are easily photographed, copied or transferred and cannot be independently certified as true
Can write Tab Data Packaging information, date of production, channel information Controls write permissions and keys are required, otherwise there is a risk of tampering
Dynamic password or encryption authentication High-value goods, channel verification, duplicate identification Need security chips, key management and backstage interfaces

Keys cannot be written directly in web code, mobile-end installation packages or normal database fields. The project should have key generation, distribution, rotation, backup and de-licensing, and a distinction between production, testing and operating environments. When it comes to encryption algorithms, the type should be selected according to chip capabilities, communication protocols and compliance requirements, avoiding only " readable " , ignoring key life cycle management.

Element 3: Designing data links by label-equipment-platform

An enforceable chain can be broken down into the following steps:

  1. Initialization of labels:A unique record is created for each chip, with a product code, batch number or internal flow number, recording the time of initialization and the operator.
  2. Security binding:(c) Tie label identity to dynamic authentication parameters, limiting repetition of initialization and unauthorized rewrite.
  3. Read live:Cell phones or special devices acquire label information and submit to the service-end such necessary fields as random numbers, device identification, time and location.
  4. Backstage judgment:Validation of certification results, examination of label status, number of verifications, time interval and regional variations, output of " normal, reviewable, expired, suspected repeater" etc.
  5. Result marks:(c) Maintaining the time of verification, nodes and causes of anomalies to facilitate tracking the movement of a particular product.

The data sheet should contain at least label ID, product ID, batch number, production time, current state, recent time and anomaly count. User displays are not appropriate to directly expose internal flow numbers, key materials and complete channel information. Only the consumer understands the results, and the field required for auditing is kept.

Element 4: Positioning of labels according to product and packaging

Metal, liquids, carbon powder, magnetic materials, and multilayer packaging all affect NFC tag RF performance. Metal packaging generally requires a tag construction suited to metal. For products with high liquid content, retest the spacing between the tag and container. Do not test a bare tag alone. Verify performance with the actual packaging, adhesive, and mounting position.

Field tests can set the following items:

The project acceptance indicator should be clearly written before testing, for example, the number of successful consecutive readings of 1,000 under specified equipment, specified distance and formal packaging conditions, the average response time and the accuracy of abnormal classification. The value here is the project test target and should not be used as a general feature of all labels and devices directly.

Point 5: Linking security and production, storage, and channel processes

The NFC's security value is not only for consumer enquiries. It can be used to record the labeling and boxing relationship at the production chain, the storage chain can be recorded in a warehouse, the inventory and the channel link can assist in judging the movement of goods, and the after-sale chain can check the batch and service records.

In the case of a plant that produces high-value parts, for example, a "chip ID" - product sequence - box number" can be established when a single product is labeled; and a "packer - tray number - export list" can be created when a container is loaded. When a single product is verified, not only does it return to its authenticity state, but also does it check whether it has been released from the bank, is repeatedly bound, or is there an inter-regional verification that does not correspond to the process.

When planning such projects, Shanghai Picket Technologies Ltd. can break demand into label selections, interface protocols, backstage rules and four field tests of work packages, first to validate reading, writing and business processes with small batches, then to decide whether to expand to multi-spectrum packaging. This reduces the problem of mass procurement of labels at the outset, but is not able to read or write in a way that allows for data to be linked.

Element 6: A phased approach to project uplink

Phase I, confirmation of operational boundaries:The need for security is clearly defined as the individual, the packaging or the tray, which determines who is responsible for labelling, who is responsible for checking and which anomalies require manual review.

Phase II, technical samples completed:Preparation of at least two label structures and two types of reading and writing equipment to complete distance, angle, material and environmental tests under formal packaging conditions.

Stage 3: Integrate the Data Interfaces:Defines the interface fields for initialization, authentication, status queries, abnormal reporting and data export, setting privileges and logs for each interface.

Stage 4: Run a Small Pilot:It is recommended that the verification be carried out with a product specification, a production batch and a channel node.

Phase V, Establishment of operational rules:Clear how labels fail, products are returned, packaging is replaced, channels are allocated and unusual reviews are processed. Without operational rules, technical systems can be exposed to chronic data non-updates when they are online.

The NFC's technical focus on authentication and key management is dynamic, with a landing focus on “official packaging tests and operational data binding.” Only the number of labels will be increased without changing the validation logic, and the enhancement of security against forgery will be limited.

When preparing the project, you can draw a flow chart of the product from production to library, from library to validation, and then determine the type of label, authentication method and interface range. Write security levels, read environment, data fields and acceptance indicators into the project document, and then select and expand more easily.