Valid

GB/T 38563-2020General technical requirements for anti-counterfeiting traceability verification based on mobile internet (English PDF)

基于移动互联网的防伪溯源验证通用技术条件

Preview PDF

This is a limited preview

Buy now to download the full PDF (15 pages)

Need quotation for your management?

Get a formal quotation for GB/T 38563-2020 in 30 minutes.

Issued by

SAMR; SAC

Level / Type

National · Recommended

Issue date

March 6, 2020

Implementation date

October 1, 2020

Scope

GB/T 38563-2020 is the English-translated version of 基于移动互联网的防伪溯源验证通用技术条件.

GB/T 38563-2020 is the Chinese standard "General technical requirements for anti-counterfeiting traceability verification based on mobile internet".

Its scope clause reads: This standard specifies the verification terminal, verification interface, compliance, interaction, security, performance and verification of anti-counterfeiting traceability verification in the mobile Internet environment.

Anti-counterfeiting verification security level requirements and test methods. This standard applies to anti-counterfeiting traceability verification based on mobile Internet, and also to the test evaluation of anti-counterfeiting traceability verification. Its clauses include terms and definitions; abbreviations; requirements.

Found what you need?

Document preview — GB/T 38563-2020

National Standard of the People's Republic of China

ICS
35.040
Classification
A 90

Issued by: State Administration for Market Regulation; Standardization Administration of the PRC

Contents

  • Foreword
  • 1 Scope
  • 2 Normative references
  • 3 Terms and definitions
  • 4 Abbreviations
  • 5 Requirements
  • 5.1 Verify Terminal
  • 5.2 Verification interface
  • 5.3 Compliance
  • 5.4 Interaction
  • 5.5 Security
  • 5.6 Performance
  • 5.7 Anti-counterfeiting verification security level
  • 6 Test method
  • 6.1 Test conditions
  • 6.2 Verification interface
  • 6.3 Compliance
  • 6.4 Interaction
  • 6.5 Safety inspection
  • 6.6 Performance inspection
  • 6.7 Anti-counterfeiting verification security level
  • Appendix A (informative appendix) Interface docking realization process
  • Appendix B (informative appendix) Verification interface feedback data example
  • Appendix C (informative appendix) Required display content fields and instructions
  • Appendix D (informative appendix) Extended display content fields and description
  • Appendix E (informative appendix) Blockchain implementation requirements

1 Scope

This standard specifies the verification terminal, verification interface, compliance, interaction, security, performance and verification of anti-counterfeiting traceability verification in the mobile Internet environment.

Anti-counterfeiting verification security level requirements and test methods.

This standard applies to anti-counterfeiting traceability verification based on mobile Internet, and also to the test evaluation of anti-counterfeiting traceability verification.

2 Normative references

The following documents are indispensable for the application of this document. For dated reference documents, only the dated version applies to this article

Pieces. For undated references, the latest version (including all amendments) applies to this document.

GB/T 19425-2003 General technical requirements for anti-counterfeiting technology products

GB/T 22258-2008 General technical requirements for anti-counterfeiting labels

GB/T 34062-2017 Anti-counterfeiting traceability coding technical conditions

GB/T 34975-2017 Information security technology mobile smart terminal application software security technical requirements and test evaluation methods

GB/T 37025-2018 Information Security Technology Internet of Things Data Transmission Security Technical Requirements

ISO /IEC 15693-2 identification card, contactless integrated circuit card proximity card, part 2.air interface and initialization

ISO /IEC 24791-5 Radio Frequency Identification (RFID) Software System Infrastructure for Information Technology Project Management Part 5.Device Interface

3 Terms and definitions

The following terms and definitions apply to this document.

3.1 Mobile Internet

Services and services implemented by mobile wireless communication.

3.2 Anti-counterfeiting verification

The process of identifying anti-counterfeiting identification features or anti-counterfeiting traceability codes.

3.3 Anti-counterfeiting verification based on mobile internet

The process of anti-counterfeiting verification through mobile wireless communication using mobile smart terminals.

3.4 Mobile smart terminal

A mobile communication terminal product that is connected to the public mobile communication network, has an operating system, and can be installed and uninstalled by users by themselves.

[GB/T 34975-2017, definition 3.1]

3.5 Verify terminal

A mobile smart terminal for anti-counterfeiting traceability verification.

Note. Including smart phones, notebook computers, tablet computers, mobile data terminals (PDA) and dedicated mobile anti-counterfeiting verification terminals, etc.

3.6 Anti-counterfeiting traceability

Anti-counterfeiting technology or measures are adopted to realize the binding of the subject matter and the identification information one by one, and the traceability with anti-copy, anti-transfer and anti-tampering capabilities.

3.7 Multimedia digital information verification and anti-counterfeiting system

A comprehensive use of coding technology, digital encryption technology, network communication technology, computer technology to identify and verify anti-counterfeiting traceability codes

Information system.

[GB/T 34062-2017, definition 3.1.3]

3.8 Anti-counterfeiting traceability code

Meet the uniqueness and randomness detection requirements, compile according to certain rules and can be used to identify and uniquely identify items (products, tickets, etc.)

Objects, to achieve anti-counterfeiting traceability of numbers and character encoding.

[GB/T 34062-2017, definition 3.1.1]

3.9 QR code

A barcode symbol that represents information in two dimensions.

[GB/T 33993-2017, definition 3.1]

4 Abbreviations

The following abbreviations apply to this document.

5 requirements

5.1 Verify terminal

The verification terminal shall meet the requirements of Table 1.

5.3.3 RFID

RFID encoding and reading should meet the requirements of GB/T 34062-2017 and ISO /IEC 24791-5.

5.4 Interaction

5.4.1 Interactive pages and operations

The interactive page should be concise and easy to operate. If necessary, there should be graphics and text to prompt the operation method of anti-counterfeiting verification.

5.4.2 Verify display content
5.4.2.1 Necessary display content

Including verification results, key product information, third-party public platform public trust supervision information, and complaint links and contact information. Its field and saying

See Appendix C for instructions. The verification results and key product information are as follows according to whether the verification is passed or not.

a) When the verification is passed, the key product information that should be displayed includes the product name, specification parameters, manufacturer, brand, production date and personal information.

Sexual physical characteristics photos;

b) When the verification fails, it should prompt that the product is suspected of counterfeiting and other related information.

5.4.2.2 Extended display content

Including anti-counterfeiting verification technical service provider information, product traceability information, product quality inspection information, further verification methods for product uniqueness,

Operation tips and other display information related to the product. See Appendix D for its fields and descriptions.

5.5 Security

5.5.1 APP

Should meet the requirements of 4.1 in GB/T 34975-2017.

5.5.2 Data Transmission

Data transmission security should comply with GB/T 37025-2018 specifications. The transmission process should use SSL and HTTPS protocol.

The server can use the CA certificate to prevent the middleman from tampering, and the client should verify the CA certificate.

5.5.3 Data carrier
5.5.3.1 Digital

The security of the digital carrier should meet the requirements in GB/T 19425-2003.

5.5.3.2 QR code

The security of the two-dimensional code carrier shall meet the requirements of Chapter 7 of GB/T 34062-2017.

5.5.3.3 RFID

RFID tags and RAS tags should be unique, and each tag should have a unique UID. Password for RFID tag and RAS tag

Should be unique and not reusable. RFID tags and RAS tags should be bound to the goods one by one to meet anti-transfer requirements.

5.5.4 Blockchain

Blockchain technology can be used to store information such as anti-counterfeiting data. See Appendix E for the implementation requirements of blockchain.

d) Picture or video support format. prepare picture formats such as jpg and png for verification, prepare video formats such as MP4, MOV, MKV, etc.

Type for verification.

6.3 Compliance

6.3.1 Digital

The data provided by the review developer shall be tested in accordance with the method specified in 6.8.1 of GB/T 34062-2017.

6.3.2 QR code

The data provided by the review developer shall be inspected in accordance with the method specified in 6.8.3 of GB/T 34062-2017.

6.3.3 RFID

The data provided by the review developer shall be checked for compliance according to the method specified in 6.8.2 of GB/T 34062-2017, and

Compatibility inspection shall be carried out according to the method specified in ISO /IEC 24791-5.

6.4 Interaction

6.4.1 Interactive pages and operations

Review the interactive page provided by the developer and conduct anti-counterfeiting verification.

6.4.2 Verify display content
6.4.2.1 Necessary display content

Refer to Appendix C, review the verification content provided by the developer for verification and time with a stopwatch.

6.4.2.2 Extended display content

Refer to Appendix D to review the verification content provided by the developer for verification.

6.5 Safety inspection

6.5.1 APP

Carry out the inspection according to the method specified in 5.1 of GB/T 34975-2017.

6.5.2 Data Transmission

Carry out the inspection according to the method specified in GB/T 37025-2018.

6.5.3 Data carrier
6.5.3.1 Digital

Carry out the inspection according to the method specified in GB/T 19425-2003.

6.5.3.2 QR code

Carry out the inspection in accordance with the method specified in 7.1 of GB/T 34062-2017.

6.5.3.3 RFID

Carry out the inspection according to the method specified in GB/T 22258-2008.

6.5.4 Blockchain

Refer to Appendix E, use blockchain technology for inspection.

6.6 Performance inspection

6.6.1 Digital

Carry out the inspection according to the method specified in GB/T 19425-2003.

6.6.2 QR code

The inspection shall be carried out in accordance with the method specified in Chapter 7 of GB/T 34062-2017.

6.6.3 RFID

The inspection is carried out in accordance with the method specified in ISO /IEC 15693-2.

6.7 Security level of anti-counterfeiting verification

The inspection is carried out in accordance with the methods specified in GB/T 19425-2003 and GB/T 34062-2017 in 6.3, 6.4, 6.5, and 6.6.

Appendix B (Informative appendix)

Verification interface feedback data example

B.1 Feedback data information

"code".200,

"hash".2432343243243,

"data".{

"codeContent"."Query QR code",

"codeTime"."Query Time",

"codeCount"."Number of queries",

"codeType"."Anti-counterfeiting technology name"

B.2 Description of feedback data information

B.2.1 message return result

The message returned can be accompanied by any other information that can be directly read by consumers.

B.2.2 Code encoding

The encoding of code is as follows.

200.verification passed; (request successful)

201.The verification is complete, the code is true, but it is suspected to be transferred (maybe the production batch number is too long or has been queried in the past), the consumer will follow the detailed information confirm;

202.The anti-counterfeiting code does not exist;

203.The security code is inconsistent with the logo;

204.The anti-counterfeiting mark cannot be verified;

205.The image quality does not meet the requirements;

100.The QR code in the picture is not recognized; please try again;

500.Abnormal (other unknown circumstances);

503.Internal server error (including. server under maintenance);

400.The request parameter is wrong.

B.2.3 hash value

The value of hash is the hash code of the content of the data field (including curly braces, excluding the colon after data). The specific hash algorithm can be determined by the server

Choose by yourself, but it should be stated in the interface document. After receiving the response, the client needs to verify the hash result to ensure the integrity of the data transmission process.

If the verification is wrong, the client should query again.

B.2.4 data data is the verification result information that returns the identification.

Appendix E (Informative appendix)

Blockchain implementation requirements

E.1 Key Features of Blockchain

E.1.1 Distributed peer

Using the peer-to-peer network model, each participating node is networked, and tasks and shared resources are allocated among peer nodes. Between network nodes

Information sharing and exchange can be realized without relying on central nodes. Peer nodes can be providers of resources, services, and content, or

Getter.

E.1.2 Data block chain

The blockchain network verifies, packs and agrees on transaction data that occurs within a certain period of time to form data blocks, which are

Orderly link with the previous block according to cryptographic characteristics.

E.1.3 Unforgeable and tamper-proof

The transaction request to write data to the blockchain needs to be accompanied by the initiator's private key signature, which is broadcasted among the participating nodes of the network along with the transaction request

And verify, realize the transaction request can not be forged and tamper-proof. The block chain data structure further guarantees tamper-proof modification.

E.1.4 Transparent and reliable

The transmission of information and the generation of blocks in the blockchain follow transparent consensus rules; every transaction is sent to

For other nodes, authorized nodes can save historical records related to their permissions to ensure the transparency of data on the chain. Every transaction and district

Block generation can be verified by the consensus mechanism authorized nodes according to the established rules to ensure the credibility of the recorded results.

E.1.5 High reliability

Multiple nodes of the blockchain have complete service capabilities and full data. The abnormal or malicious behavior of some nodes will not affect the overall service.

The availability and continuity of services, as well as the integrity and authenticity of data.

E.2 Storage

The storage function component provides various types of data generated during the operation of the blockchain, such as writing and query functions for ledger, transaction information, etc.

Yes, relevant selections include but are not limited to relational databases, key-value pair databases, file databases, etc.

Storage function components should have the following functions.

a) In a peer-to-peer network, it can be authorized to deploy and use all nodes;

b) It can provide data writing and query services efficiently, safely and stably.

For the data storage scheme that adopts sub-database and sub-table, the storage function components should also include data fragmentation and routing processing capabilities.

E.3 Blockchain network construction

The public key of the system administrator needs to be written in the genesis block.

Configure the relevant parameters of the network, such as block time, maximum block size, consensus mechanism, etc.

E.4 On-chain and query

The anti-counterfeiting verification and related data (or its hash value) to be written into the transaction are assembled, synchronized on the chain, and the block and transaction ID are obtained. transaction

Need to include. write operator, write time, write location.

The transaction may include the characteristic data of the relevant product production and circulation links.

Query according to the block and transaction ID or related characteristics, and obtain the certificate data on the blockchain.

E.5 Blockchain service provider

The blockchain service provider shall obtain the record of the blockchain information service of the relevant national blockchain authority.

Blockchain service providers should comply with the supervision and management measures formulated and issued by the blockchain service regulator.

......
This preview omits tables, figures, formulas and parts of the technical clauses. The complete document — 15 pages — is available in the English PDF.

Similar standards

How to Download GB/T 38563-2020

  1. 1

    Add to cart

    Click "Download PDF" on this page and choose "Buy this standard". You can add more standards before checkout.

  2. 2

    Checkout

    Enter your email and billing details. Payment is processed securely by Stripe (cards or bank transfer). Prefer bank details? Request a quotation (min. order $300).

  3. 3

    Fast delivery

    After payment you'll receive an email confirmation. The English PDF is sent to the same address, usually within minutes and at the latest within 1 business day.

  4. 4

    Invoice included

    A tax invoice is attached to the confirmation email. Need a custom invoice? Contact us.

Related Standards

English PDF
15 pages
Fast delivery
Invoice included
View Cart

Secure payment via Stripe

Payments accepted

VisaMastercardAmerican ExpressApple PayGoogle PayStripe

GB/T 38563-2020

$235.00