GB/T 37075-2018 English PDF

Standard ID	USD	BUY PDF	Lead-Days	Standard Title (Description)	Status
GB/T 37075-2018	RFQ	ASK	3 days	Electronic product code -- Information services	Valid

Similar standards

GB/T 38662.2   GB/T 39852   GB/T 38660   GB/T 35419   GB/T 45309   

Basic data

Standard ID: GB/T 37075-2018 (GB/T37075-2018)
Description (Translated English): Electronic product code -- Information services
Sector / Industry: National Standard (Recommended)
Classification of Chinese Standard: A24
Classification of International Standard: 35.040
Word Count Estimation: 146,135
Date of Issue: 2018-12-28
Date of Implementation: 2019-07-01
Regulation (derived from): National Standard Announcement No. 17 of 2018
Issuing agency(ies): State Administration for Market Regulation, China National Standardization Administration

GB/T 37075-2018: Electronic product code -- Information services

---This is a DRAFT version for illustration, not a final translation. Full copy of true-PDF in English version (including equations, symbols, images, flow-chart, tables, and figures etc.) will be manually/carefully translated upon your order.
Electronic product code--Information services ICS 35.040 A24 National Standards of People's Republic of China Electronic code information service Published on.2018-12-28 2019-07-01 implementation State market supervision and administration China National Standardization Administration issued

Content

Foreword III Introduction IV 1 Scope 1 2 Normative references 1 3 Terms and Definitions 1 4 Abbreviations 2 5 EPCIS standard framework 3 5.1 Overview of the EPCIS Standard 3 5.2 Hierarchical structure of the EPCIS standard 3 5.3 Extension mechanism of the EPCIS standard 5 6 abstract data model layer 5 6.1 Event data and master data 5 6.2 Type of vocabulary 6 6.3 Extension mechanism 6 6.4 identifier representation 7 6.5 Grading Vocabulary 7 7 data definition layer 7 7.1 General rules for defining data definition layer modules 7 7.2 Core Event Type Module Overview 8 7.3 Basic components of the core event type model 10 7.4 Event 16 of the Core Event Type Module 8 Service Layer Interface Technical Requirements 23 8.1 Service Layer Interface Technical Overview 23 8.2 Core Acquisition Operation Module 24 8.3 Core Query Operation Module 25 9 XML definition of the data definition module 32 9.1 Scalable Mechanism 32 9.2 Standard Business Document Title 34 9.3 EPCglobal Infrastructure 35 9.4 Location Field Additional Information 35 9.5 Core Event Type Architecture 35 9.6 Master Data Architecture 35 10 core acquisition operation module binding 36 10.1 Overview of Binding of Core Acquisition Operation Modules 36 10.2 Message Queue Binding 36 10.3 HTTP Binding 37 11 Core Query Operation Module Binding 37 11.1 All bindings of the core query operation module 37 11.2 XML Schema of the Core Query Operations Module 38 11.3 Querying the SOAP/HTTP Binding of the Control Interface 39 11.4 Querying the AS2 Binding of the Control Interface 39 11.5 Querying the Callback Interface Binding 41 Appendix A (informative) Relationship between EPCIS and GS1 system architecture 44 Appendix B (informative) Principles and modular features of the EPCIS standard 50 Appendix C (informative) Supplementary description of the abstract data model layer 51 Appendix D (Normative) UML Form Class Diagram Representation 55 Appendix E (Normative Appendix) Semantics of Data Definition Layer Events 57 Appendix F (informative appendix) Quantity event 62 Appendix G (informative) Supplementary description of the basic component modules of the core event type model 63 Appendix H (informative) Supplementary notes to the events of the core event type module 68 Appendix I (Normative) Method, parameters and fields for the service layer interface 70 Appendix J (Normative) XML Binding for Data Definition Modules 87 Appendix K (informative) XML example of core event data and master data 107 Appendix L (Normative) The XML Schema of the Core Query Operations Module 115 Appendix M (informative) GS1AS2 Guide 139 Reference 141

Foreword

This standard was drafted in accordance with the rules given in GB/T 1.1-2009. This standard refers to the International Article Numbering Association (GS1) "Article Electronic Code Information Service Specification Version 1.1" [EPCInformation Services (EPCIS) Version 1.1Specification] compiled. This standard is proposed and managed by the National Logistics Information Management Standardization Technical Committee (SAC/TC267). This standard was drafted. China Article Numbering Center, National Radio Frequency Product Quality Supervision and Inspection Center, Shenzhen Standard Technology Research Institute, North Beijing Jiaotong University, Fudan University, Imagine IOT (Beijing) Technology Development Co., Ltd. The main drafters of this standard. Luo Yan, Ruo Ruozhen, Li Zhimin, Hu Min, Wang Long, Dong Teng, Zhao Chen, Du Han, Zheng Yi, Xiao Wenkang, Yang Zilong, Hou Hanping, Wang Junyu, Zhang Qiuxia, Yi Xiaoshan, Liu Yi.

Introduction

There is no change in the technical content of this standard and the Electronic Code Information Service (EPCIS) version 1.1 of the article. The goal of EPCIS is to make different Use programs to create and share visibility event data between the enterprise and the enterprise. The ultimate goal of this sharing is to make the user relevant. A shared view of physical or digital objects in a business environment. In the relevant standards of EPCIS, "Object" generally refers to the physical reality identified by the class level identifier or the item level identifier. Body, and these physical entities involve the actual operational steps of one or more organizations' overall business processes. These physical entities include trade items Project (entity products), logistics units, recyclable assets, fixed assets, physical documents, etc. “Object” can also refer to digital products, also by class level It is not identified by the logo or the item level identifier, and also involves similar business process steps as described above. These digital products include digital trade Easy projects (music downloads, e-books, etc.), electronic documents (electronic coupons, etc.). The "object" in this standard is used to refer to a physics An entity or digitized product, identified by a class-level identifier or a item-level identifier, is the subject of a business process. EPCIS Data consists of "visibility events", where each "visibility event" is a record of one or more objects completing a particular business process. The original idea of the EPCIS standard was to strengthen the cooperation between trading partners by sharing the details of physical entities or digital products. Work. The name EPCIS reflects the efforts made in the initial stages of the development of electronic coding of goods. However, it should be noted that EPCIS Electronic code and RFID data carriers are not required, and even EPCIS version 1.1 does not require item-level identification (item electronics) The encoding was originally identified only for instance-level objects when it was designed). The EPCIS standard applies to the collection and sharing of visibility event data. Shape, the expression of the name EPC is only a historical existence. EPCIS provides an open, standard interface that allows for seamless integration of well-defined services across and within the enterprise. Standard interfaces defined in the EPCIS standard can use the defined set of service operations and related data standards to collect and query visibility Pieces of data, combined with security mechanisms to meet the needs of users. In most cases, this will involve one or more visibility event data. A permanent database, although no permanent database is required, the elements of the service method can be used for direct sharing between applications. Regardless of the existence of a permanent database, the EPCIS standard specifies only standard shared data interfaces between applications. Sets visibility event data, also used for data access. It does not specify how the service works and how the database itself is implemented. In addition to regulations In addition to the data required for standard EPCIS acquisition operations, this standard does not define how EPCIS services acquire/calculate the required data. Interoperability requires a standardized interface, but the implementation of the interface allows for the implementation of technology and implementation standards between enterprises or entities competition. Electronic code information service

1 Scope

This standard specifies the abstract data model layer, data definition layer, and service layer interface of the electronic coded information service of the item, and specifies the data. Define the XML syntax description of the module, core acquisition operation module, and query operation module. This standard applies to the use of the EPCIS standard to enable different applications to create and share visibility between and within the enterprise. Data, which in turn enables users to obtain a common view of physical or digital objects in the relevant business environment.

2 Normative references

The following documents are indispensable for the application of this document. For dated references, only the dated version applies to this article. Pieces. For undated references, the latest edition (including all amendments) applies to this document. GB/T 12905 barcode terminology GB/T 17295 International Trade Unit of Measure Code ISO 8601 data element and exchange format information exchange date and time representation (Dataelementsandinterchange formats-Informationinterchange-Representationofdatesandtimes) GS1 Core Business Vocabulary Version 1.2 [GS1CoreBusinessVocabulary(CBV), version1.2] GS1 Article Electronic Coded Label Data Standard Version 1.9 (GS1EPCTagDataStandard, version 1.9) GS1 article electronic coding information service version 1.0 (GS1EPCInformationServices, version1.0) GS1 technical documentation EDIINTAS1 and AS2 transmission communication guide (GS1TechnicalDocumentEDIINTAS1and AS2TransportCommunicationsGuidelines, Issue1, February.2006) RFC2246 Transport Layer Security Protocol (TheTLSProtocol, Version 1.0) RFC2396 Uniform Resource Identifier (URI). Generic Syntax [UniformResourceIdentifiers(URI). GenericSyn- Tax] RFC2616 Hypertext Transfer Protocol HTTP/1.1 (HypertextTransferProtocol-HTTP/1.1) HTTP over HTTPC2818 TLS (HTTPOverTLS) RFC3268 Advanced Encryption Standard (AES) Cipher Suite for Transport Layer Security (TLS) [AdvancedEncryption Standard (AES)CipersuitesforTransportLayerSecurity(TLS)] RFC4130 MIME-based secure peer-to-peer service data exchange using HTTP, Applicability Statement 2 (AS2) [MIME- BasedSecurePeer-to-PeerBusinessDataInterchangeUsingHTTP, ApplicabilityStatement2(AS2)]

3 Terms and definitions

GB/T 12905, GB/T 17295 and GS1 Core Business Vocabulary Version 1.2 (CBV1.2) and the following terms and definitions apply Used in this document. 3.1 Electronic code of goods electronicproductcode; EPC An identification scheme that broadly identifies physical objects (such as traded goods, assets, and locations) through RFID tags and other means. Note. Standardized EPC data consists of an EPC (or EPC identifier) and optional filter values, where EPC is used to uniquely identify one or a class For individual objects, the filter values are chosen when it is judged that EPC tags need to be read efficiently and efficiently. ......

Image     

Tips & Frequently Asked Questions:

Question 1: How long will the true-PDF of GB/T 37075-2018_English be delivered?

Answer: Upon your order, we will start to translate GB/T 37075-2018_English as soon as possible, and keep you informed of the progress. The lead time is typically 1 ~ 3 working days. The lengthier the document the longer the lead time.

Question 2: Can I share the purchased PDF of GB/T 37075-2018_English with my colleagues?

Answer: Yes. The purchased PDF of GB/T 37075-2018_English will be deemed to be sold to your employer/organization who actually pays for it, including your colleagues and your employer's intranet.

Question 3: Does the price include tax/VAT?

Answer: Yes. Our tax invoice, downloaded/delivered in 9 seconds, includes all tax/VAT and complies with 100+ countries' tax regulations (tax exempted in 100+ countries) -- See Avoidance of Double Taxation Agreements (DTAs): List of DTAs signed between Singapore and 100+ countries

Question 4: Do you accept my currency other than USD?

Answer: Yes. If you need your currency to be printed on the invoice, please write an email to Sales@ChineseStandard.net. In 2 working-hours, we will create a special link for you to pay in any currencies. Otherwise, follow the normal steps: Add to Cart -- Checkout -- Select your currency to pay.