ISO IEC 19987-2015 Information technology - EPC Information services - Specification《信息技术 EPC信息服务 规格》.pdf

《ISO IEC 19987-2015 Information technology - EPC Information services - Specification《信息技术 EPC信息服务 规格》.pdf》由会员分享，可在线阅读，更多相关《ISO IEC 19987-2015 Information technology - EPC Information services - Specification《信息技术 EPC信息服务 规格》.pdf（174页珍藏版）》请在麦多课文档分享上搜索。

1、Information technology EPC Information services SpecificationTechnologies de linformation Services dinformation sur les codes de produit lectronique SpcificationINTERNATIONAL STANDARDISO/IEC19987Reference numberISO/IEC 19987:2015(E)First edition2015-09-15 ISO/IEC 2015ii ISO/IEC 2015 All rights reser

2、vedCOPYRIGHT PROTECTED DOCUMENT ISO/IEC 2015, Published in SwitzerlandAll rights reserved. Unless otherwise specinullied, no part of this publication may be reproduced or utilized otherwise in any form or by any means, electronic or mechanical, including photocopying, or posting on the internet or a

3、n intranet, without prior written permission. Permission can be renulluested from either ISO at the address below or ISOnulls member body in the country of the requester.ISO copyright ofnulliceCh. de Blandonnet 8 CP 401CH-1214 Vernier, Geneva, SwitzerlandTel. +41 22 749 01 11Fax +41 22 749 09 47copy

4、rightnulliso.orgwww.iso.orgISO/IEC 19987:2015(E)ISO/IEC 19987:2015(E) ISO/IEC 2015 All rights reserved iiiForeword ISO (the International Organization for Standardization) and IEC (the International Electrotechnical Commission) form the specialized system for worldwide standardization. National bodi

5、es that are members of ISO or IEC participate in the development of International Standards through technical committees established by the respective organization to deal with particular fields of technical activity. ISO and IEC technical committees collaborate in fields of mutual interest. Other i

6、nternational organizations, governmental and nongovernmental, in liaison with ISO and IEC, also take part in the work. In the field of information technology, ISO and IEC have established a joint technical committee, ISO/IEC JTC 1. The procedures used to develop this document and those intended for

7、its further maintenance are described in the ISO/IEC Directives, Part 1. In particular the different approval criteria needed for the different types of document should be noted. This document was drafted in accordance with the editorial rules of the ISO/IEC Directives, Part 2 (see www.iso.org/direc

8、tives). Attention is drawn to the possibility that some of the elements of this document may be the subject of patent rights. ISO and IEC shall not be held responsible for identifying any or all such patent rights. Details of any patent rights identified during the development of the document will b

9、e in the Introduction and/or on the ISO list of patent declarations received (see www.iso.org/patents). Any trade name used in this document is information given for the convenience of users and does not constitute an endorsement. For an explanation on the meaning of ISO specific terms and expressio

10、ns related to conformity assessment, as well as information about ISOs adherence to the WTO principles in the Technical Barriers to Trade (TBT), see the following URL: Foreword Supplementary information. The committee responsible for this document is ISO/IEC JTC 1, Information technology. EPC Inform

11、ation Services (EPCIS)Version 1.1, May-2014 All contents 20072014 GS1 Page 1 of 169GDSN Package Measurement Rules GS1 Standards DocumentVersion 1 13 2 Dec 2013EPC Information Services (EPCIS) Version 1.1 SpecificationGS1 StandardVersion 1.1, May 20141 EPC Information Services (EPCIS)Version 1.1, May

12、-2014 All contents 20072014 GS1 Page 2 of 169 20072014 GS1 AISBLAll rights reserved. GS1 Global OfficeAvenue Louise 326, bte 10B-1050 Brussels, BelgiumDisclaimerGS1 AISBL (GS1) is providing this document as a free service to interested industries. This document was developed through a consensus proc

13、ess of interested parties in developing the Standard. Although efforts have been made to assure that the document is correct, reliable, and technically accurate, GS1 makes NO WARRANTY, EXPRESS OR IMPLIED, THAT THIS DOCUMENT IS CORRECT, WILL NOT REQUIRE MODIFICATION AS EXPERIENCE AND TECHNOLOGY DICTA

14、TE, OR WILL BE SUITABLE FOR ANY PURPOSE OR WORKABLE IN ANY APPLICATION, OR OTHERWISE. Use of this document is with the understanding that GS1 DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY IMPLIED WARRANTY OF NON-INFRINGEMENT OF PATENTS OR COPYRIGHTS, MERCHANTABILITY

15、AND/OR FITNESS FOR A PARTICULAR PURPOSE, THAT THE INFORMATION IS ERROR FREE, NOR SHALL GS1 BE LIABLE FOR DAMAGES OF ANY KIND, INCLUDING DIRECT, INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL OR EXEMPLARY DAMAGES, ARISING OUT OF USE OR THE INABILITY TO USE INFORMATION CONTAINED HEREIN OR FROM ERRORS CO

16、NTAINED HEREIN. ISO/IEC 2015 All rights reservedISO/IEC 19987:2015(E)EPC Information Services (EPCIS)Version 1.1, May-2014 All contents 20072014 GS1 Page 3 of 169Abstract2This document is a GS1 Standard that defines Version 1.1 of EPC Information Services (EPCIS).3The goal of EPCIS is to enable disp

17、arate applications to create and share visibility event data, 4both within and across enterprises. Ultimately, this sharing is aimed at enabling users to gain a 5shared view of physical or digital objects within a relevant business context. 6Status of this document7This section describes the status

18、of this document at the time of its publication. Other8documents may supersede this document. The latest status of this document series is 9maintained at GS1. See www.gs1.org/gsmp for more information. 10This version of the GS1 EPCIS 1.1 Standard is the ratified version and has completed all GSMP 11

19、steps.12Comments on this document should be sent to gsmpgs1.org.13Differences from EPCIS 1.0.1 14EPCIS 1.1 is fully backward compatible with EPCIS 1.0.1. 15EPCIS 1.1 includes these new or enhanced features: 16 Support for class-level identification is added to ObjectEvent, AggregationEvent,17and Tra

20、nsformationEvent through the addition of quantity lists. 18 A new event type, TransformationEvent, provides for the description of events in 19which inputs are consumed and outputs are produced. 20 The “why” dimension of all event types are enhanced so that information about the sources 21and destin

21、ations of business transfers may be included. 22 The “why” dimension of certain event types are enhanced so that item/lot master data may be 23included. 24 The SimpleEventQuery is enhanced to encompass the above changes to event types.25 The introductory material is revised to align with the GS1 Sys

22、tem Architecture.26 The XML extension mechanism is explained more fully. 27 The QuantityEvent is deprecated, as its functionality is fully subsumed by 28ObjectEvent with the addition of quantity lists.2930 ISO/IEC 2015 All rights reservedISO/IEC 19987:2015(E)EPC Information Services (EPCIS)Version 1

23、.1, May-2014 All contents 20072014 GS1 Page 4 of 169Table of Contents311 Introduction.6322 Relationship to the GS1 System Architecture 7332.1 Overview of GS1 Standards . 7342.2 EPCIS in Relation to the “Capture” and “Share” Layers. 8352.3 EPCIS in Relation to Trading Partners . 10362.4 EPCIS in Rela

24、tion to other GS1 System Architecture Components. 12373 EPCIS Specification Principles15384 Terminology and Typographical Conventions16395 EPCIS Specification Framework 16405.1 Layers . 16415.2 Extensibility . 18425.3 Modularity 18436 Abstract Data Model Layer.19446.1 Event Data and Master Data. 194

25、56.2 Vocabulary Kinds 22466.3 Extension Mechanisms . 23476.4 Identifier Representation. 25486.5 Hierarchical Vocabularies . 26497 Data Definition Layer 26507.1 General Rules for Specifying Data Definition Layer Modules. 27517.1.1 Content 27527.1.2 Notation. 28537.1.3 Semantics . 29547.2 Core Event T

26、ypes Module Overview . 29557.3 Core Event Types Module Building Blocks 33567.3.1 Primitive Types 33577.3.2 Action Type . 34587.3.3 The “What” Dimension 34597.3.4 The “Where” Dimension Read Point and Business Location 40607.3.5 The “Why” Dimension . 44617.3.6 Instance/Lot Master Data (ILMD) 47627.4 C

27、ore Event Types Module Events . 48637.4.1 EPCISEvent 48647.4.2 ObjectEvent (subclass of EPCISEvent) 50657.4.3 AggregationEvent (subclass of EPCISEvent). 54667.4.4 QuantityEvent (subclass of EPCISEvent) DEPRECATED 6067 ISO/IEC 2015 All rights reservedISO/IEC 19987:2015(E)EPC Information Services (EPC

28、IS)Version 1.1, May-2014 All contents 20072014 GS1 Page 5 of 1697.4.5 TransactionEvent (subclass of EPCISEvent) . 61687.4.6 TransformationEvent (subclass of EPCISEvent) 67698 Service Layer 71708.1 Core Capture Operations Module . 73718.1.1 Authentication and Authorization 73728.1.2 Capture Service 7

29、3738.2 Core Query Operations Module 75748.2.1 Authentication . 75758.2.2 Authorization . 75768.2.3 Queries for Large Amounts of Data 76778.2.4 Overly Complex Queries. 76788.2.5 Query Framework (EPCIS Query Control Interface) 77798.2.6 Error Conditions 87808.2.7 Predefined Queries for EPCIS 90818.2.8

30、 Query Callback Interface 109829 XML Bindings for Data Definition Modules.109839.1 Extensibility Mechanism 109849.2 Standard Business Document Header 112859.3 EPCglobal Base Schema 114869.4 Additional Information in Location Fields 114879.5 Schema for Core Event Types 115889.6 Core Event Types Examp

31、les (non-normative). 123899.6.1 Example 1 Object Events with Instance-Level Identification . 123909.6.2 Example 2 Object Event with Class-Level Identification 124919.6.3 Example 3 Aggregation Event with Mixed Identification 125929.6.4 Example 4 Transformation Event. 126939.7 Schema for Master Data .

32、 127949.8 Master Data Example (non-normative) 1309510 Bindings for Core Capture Operations Module 1319610.1 Message Queue Binding. 1319710.2 HTTP Binding 1329811 Bindings for Core Query Operations Module .1339911.1 XML Schema for Core Query Operations Module 13310011.2 SOAP/HTTP Binding for the Quer

33、y Control Interface. 14110111.3 AS2 Binding for the Query Control Interface 14810211.4 Bindings for Query Callback Interface 15310311.4.1 General Considerations for all XML-based Bindings 15310411.4.2 HTTP Binding of the Query Callback Interface. 15410511.4.3 HTTPS Binding of the Query Callback Inte

34、rface 15410611.4.4 AS2 Binding of the Query Callback Interface . 15510712 References 1561081109 ISO/IEC 2015 All rights reservedISO/IEC 19987:2015(E)EPC Information Services (EPCIS)Version 1.1, May-2014 All contents 20072014 GS1 Page 6 of 169Introduction110This document is a GS1 Standard that define

35、s Version 1.1 of EPC Information Services (EPCIS).111The goal of EPCIS is to enable disparate applications to create and share visibility event data,112both within and across enterprises. Ultimately, this sharing is aimed at enabling users to gain a 113shared view of physical or digital objects with

36、in a relevant business context. 114“Objects” in the context of EPCIS typically refers to physical objects that are identified either at 115a class or instance level and which are handled in physical handling steps of an overall business 116process involving one or more organizations. Examples of suc

37、h physical objects include trade 117items (products), logistic units, returnable assets, fixed assets, physical documents, etc. “Objects” 118may also refer to digital objects, also identified at either a class or instance level, which 119participate in comparable business process steps. Examples of

38、such digital objects include digital 120trade items (music downloads, electronic books, etc.), digital documents (electronic coupons, 121etc), and so forth. Throughout this document the word “object” is used to denote a physical or 122digital object, identified at a class or instance level, that is

39、the subject of a business process step. 123EPCIS data consist of “visibility events,” each of which is the record of the completion of a 124specific business process step acting upon one or more objects. 125The EPCIS standard was originally conceived as part of a broader effort to enhance collaborat

40、ion 126between trading partners by sharing of detailed information about physical or digital objects. The 127name EPCIS reflects the origins of this effort in the development of the Electronic Product Code 128(EPC). It should be noted, however, that EPCIS does not require the use of Electronic Produ

41、ct 129Codes, nor of Radio-Frequency Identification (RFID) data carriers, and as of EPCIS 1.1 does not 130even require instance-level identification (for which the Electronic Product Code was originally 131designed). The EPCIS standard applies to all situations in which visibility event data is to be

42、 132captured and shared, and the presence of “EPC” within the name is of historical significance 133only. 134EPCIS provides open, standardised interfaces that allow for seamless integration of well-defined 135services in inter-company environments as well as within companies. Standard interfaces are

43、 136defined in the EPCIS standard to enable visibility event data to be captured and queried using a 137defined set of service operations and associated data standards, all combined with appropriate 138security mechanisms that satisfy the needs of user companies. In many or most cases, this will 139

44、involve the use of one or more persistent databases of visibility event data, though elements of 140the Services approach could be used for direct application-to-application sharing without 141persistent databases.142With or without persistent databases, the EPCIS specification specifies only a stan

45、dard data 143sharing interface between applications that capture visibility event data and those that need 144access to it. It does not specify how the service operations or databases themselves should be 145implemented. This includes not defining how the EPCIS services should acquire and/or compute

46、 146the data they need, except to the extent the data is captured using the standard EPCIS capture 147operations. The interfaces are needed for interoperability, while the implementations allow for 148competition among those providing the technology and implementing the standard. 149EPCIS is intende

47、d to be used in conjunction with the GS1 Core Business Vocabulary (CBV) 150standard CBV1.1. The CBV standard provides definitions of data values that may be used to 151populate the data structures defined in the EPCIS standard. The use of the standardized 152vocabulary provided by the CBV standard i

48、s critical to interoperability and critical to provide for 153 ISO/IEC 2015 All rights reservedISO/IEC 19987:2015(E)EPC Information Services (EPCIS)Version 1.1, May-2014 All contents 20072014 GS1 Page 7 of 169querying of data by reducing the variation in how different businesses express common inten

49、t. 154Therefore, applications should use the CBV standard to the greatest extent possible in 155constructing EPCIS data. 1562 Relationship to the GS1 System Architecture157This section is largely quoted from EPCAF and GS1Arch, and shows the relationship of 158EPCIS to other GS1 Standards. 1592.1 Overview of GS1 Standards160GS1 Standards support the information needs of end users interacting with each other in supply 161chains, specifically the information required to supp