Summary of The EPCglobal Architecture Framework

1. Introduction. EPCglobal architecture framework is a collection of interrelated hardware, software, and data standard (EPCglobal Standards), together with shared network services that operated by EPCglobal, its delegates, and others (EPC Network Services). EPCglobal architectural defines an interfaces for those element for collaborating each other (e.g UHF Class 1 Gen 2, etc). While a the design of hardware and software component that implement EPCglobal standardsare propietary to the solution providers and end user that create such element (e.g RFID tag). Whereas a special case of components that implement EPCglobal standard are shared network services that operated and developed by EPCglobal itself (or the delegates organization or by third parties). This components are refered to as EPC Network Services and provide services to all end users (e.g Object Naming Service (ONS)) 2. Architecture Framework Overview

Fig. 1 Architecture Framework Overview

Architecture Framework Activities EPC Physical Object Exchange Exchange of physiscal objects with EPC (the physical object is trade good, and the exchange activity is shipping, receivinf, etc) EPCglobal define EPC physical object exchange standard, designed to ensure that when one end user deliver a physical object to another end user, the later will be able to determine the EPC of the physical object and interpret it properly. EPC Data Exchange By EPC Data Exchange the subscriberes is get a benefit from the EPCglobal Network by exchange data with each other EPC Infrastructure Subscriber carries out operations within its four walls that create EPC(s) for new objects, follow its movement, and gather a valuable information. The EPCglobal Architecture Framework defines interface standards for the major infrastructure components required to gather and record EPC data, thus allowing end users to build their internal systems using interoperable components. Architecture Framework Standards The following table summarizes all standards in terms of the three activities above. Notes for the Status column of the table bellow: Ratified indicates a ratified EPCglobal standard. In development indicates a standard whose development has been chartered and is underway within the EPCglobal standards development process Prior to the launch of EPCglobal in November 2003, the former Auto-ID Center published two UHF Tag Air Interface specifications, referred to herein as UHF 0 Gen 1 and UHF Class 1 Gen 1. These specifications, which are not EPCglobal standards, are superseded by the UHF Class 1 Gen 2 Tag Air Interface which was ratified byEPCglobal in December 2004. Prior to the launch of EPCglobal in November 2003, the former Auto-ID Center also published an HF Tag Air Interface specification referred to herein as HF Class 1 Gen 1. This specification, which is not an EPCglobal standard, will be superseded by the HF Class 1 Tag Air Interface.

Table 1. Architecture Framework Standard In the table above, the EPCIS Data Standard 315 is shown as spanning the categories of infrastructure standard and data exchange standard. Likewise, the EPC Tag Data Standard is shown spanning the categories of object exchange standard and infrastructure standard, though in fact it also spans the data exchange category.

3. Goal for the EPCglobal Architecture Framework The Role of Standards To facilitate the exchange of information and physical objects between trading partners by providing a mechanism on how the exchange activiti will be carried out. To foster the existence of a competitive marketplace for system components To encourage innovation (i.e just define interface, not implementation) Global Standards EPCglobal standards are developed for global use to ensure that the standard will work everywherein the world. Open System Open standard through the EPCglobal Standards Development Process or another standards organization Free and open rights to implement EPCglobal Standard Platform Independence Implemented on heterogeneous software and hardware (.e the structure and semantics of data in an abstract sense is specified separately from the concrete details of data access services and bindings to particular interface protocols) Specified using a neutral technology (e.g. XML, SOAP, etc) Scalability and Extensibility Designed to scale to meet the needs of each End-User, to a global implementation across many companies and many continents. Data Ownership Collecting information from a single company or across multiple companies and making it available to those authorized parties. A fundamental principle is that each End User that captures data owns that data, and has full control over what other parties have access to that data. Security Designed to promote a secure environment Privacy Designed to accommodate the needs of both individual and corporations

Industry Architectures and Standards Designed to work with complement existing industry-wide architecture and standards

Open, Community Process Designed to yield standards that are relevant and beneficial to end users

4. Underlying Technical Principles Unique dentity to physical objects, loads, locations, assets, and other entities whose use is to be tracked. The name assigned to one entity is different than the name assigned to another entity EPC characteristics Uniqueness / Serialization Universality : EPC(s) comprise a single space of identifiers that can be used to identify any entity, regardless of what kind of entity it is. Compatibility : EPC identifiers are designed to be fit with existing naming systems Federation of several naming structure (GS1 SSCC, GS1 GRAI) instead of single naming structure. This allows existing naming structures to be incorporated into the EPC system. Extensibility, this makes the additional naming structures may be incorporated into the EPC system without invalidating existing EPC(s) or the GS1 system. Representation independence : binary realization, URI realization Decentralized assignment : Done through a hierarchical scheme (Registration authority issuing agency EPC Manager), so that 463 independent organizations can assign new EPC(s) without the possibility of collision Structure : Not purely random strings, but rather have a certain amount of internal structure in the form from of designated fields. The structure is essential to the scalability of look up service. Light Weight : Just enough structure and information to accomplish the goal. Use of the Electronic Product Code. The EPC is a universal identifier that provides a unique identity for any physical object. The EPC is designed to be unique across all physical objects in the world, over all time, and across all categories of physical objects

Decentralized Implementation EPCglobal is a single global network, but logically centralized functions are distributed Assignment of EPC codes, ONS lookup service

Layering of Data Standard Verticalization Data exchange that are intended to serve the needs of many different industries Layers A framework layer : apply equally to all industries Vertical data : particular industries group EPC Tag Data Specification Header bit / specific coding schemes of industry EPCIS Data Specification Abstract data model / specific event types, mast data attributes used within a particular industry. Layering of Software Spesification Does not rely on specific implementation technology (Web service, XML, AS2, EDI) Layered approach : abstract content of data (service) is defined neutral description language (e.g UML) Extensibility Recognizes the fact that change is inevitable Extensions Supports to backward compatibility and forward compatibility Supports to non-standard extensions by multiple groups without possibility of conflict or collision.

5. Architecture Foundations Electronic Product Code Underlying the principle of unique identity Plays a central part in every role and interface EPC Manager Subscriber who has been granted rights to use a portion of the EPC namespace Responsibilities : Allocate a new EPC (commission), Associates EPC with a physical object (entity) Maintain the Object Name Services records EPC Manager Number A single number that issues the EPC Manager Allows any system to instantly identify the EPC Manager associated with a given EPC (distinct field) Embedding of Existing Codes EPC Tag Data Specification are based on existing industry coding scheme GS1 family : SGTIN, SSCC, SGLN, GRAI, GIAI Class Level Data versus Instance Level Data A product class : EPC Manager Number and Object Class ID A product : EPC Manager Number, Object Class ID, Serial Number EPC Information Services (EPCIS) The primary vehicle for data exchange activity between EPCglobal subsricbers. Static Data : static data is unchangeable over the life cycle of a physical object Class-level static data This data is same for all object of given object class

Instance-level static data Differ from one instance to the next within given object class. Example : data of manufacture, lot number, expiration data, etc.

Transactional data : transactional data is continuously grows and changes. Instance Observations Record events that occur in the life of one or more specific EPC(s)

Consist of : time, location, one or more EPC(s), and business process step. Example : EPC X was shipped at 12:30pm March 15th 2004 from Acme Distribution Center.

Quantity Observations. Record events concerned with measuring the quantity of objects within a particular object class. Consist of : time, location, object class, quantity, and business process step. Example : There were 4.100 instances of object class C observed at 2.00am January 16th 2003 in RetailMart Store #23. Business Transaction Observations Record an association between one or more EPC(s) and a business transaction. Consist of : time, one or more EPC(s) and a business transaction. Example : The pallet with EPC X was shipped in fulfillment of Acme Corp purchase order #23 at 2:20pm. 6. Roles and Interfaces (General Consideration Architecture Framework vs. System Architecture Architecture Framework Only define interfaces (interoperable, wide marketplace of vendor-provided) Avoid specification of components (flexibility in designing system architecture) System Architecture Implemented by end user, and have a particular hardware/software components In line with the preferences an goals of end users. Cross-Enterprise vs. Intra-Enterprise Cross-Enterprise Data exchange between enterprises (EPC Object Exchange, EPC Data Exchange) Intra-Enterprise Not affect parties outside the subscribes's own four wall (EPC Infrastructure)

7. Data Flow Relationships Cross-Enterprise Data Exchange Interaction EPCIS Accessing Application Exactly where to find the information (two-party supply chain) A
Known B

Exactly where to find the information (three-party supply chain) A

Can reach B

B
Kn ow nB

The use of Object Naming Service (ONS)

ONS
Lo ca

Qu er y

tio n of B

Can reach B

The use of EPCIS Discovery Service (case of multiple party supply chain)
EPCIS Discovery Service
tE
L oca tion of E

B D

Known E Known E E Not Known E

Qu e ry a bou

rea Can

ch E

E F

Two EPCglobal Standards govers this interaction EPCIS Query Interface : define how data is requested and delivered EPCIS Data Specification : define the format and meaning of data.

Subscriber Authentication Authenticate the identity of the pPartner EPCglobal Subscriber Belong to EPCglobal Core Services

 Object Exchange Interaction Read the tag using RFID readers Two EPCglobal Standards govern this interaction Tag protocol : define how data is carried through a radio signal EPC Tag Data Specification : define the format and meaning of data

ONS Interactions Input EPC, output URL A

Implemented as a hierarchy of lookup services

Local ONS

Local ONS

Local ONS

Figure 2. Data Flow Diagram for Cross-Enterprise Relationship

 Number Assignment EPCglobal's service of issuing unique EPC Manager Numbers to each EPC Manager Insure uniqueness. Intra-Enterprise Roles and Interfaces Readers Make multiple observations of RFID tags

Reader Protocol Interface. Define the control and delivery of raw tag reads Reader : Filtering & Collection role

Filtering & Collection Filters and collections raw tag reads (filtering, aggregating, grouping, and perform differential analysis) Filtering & Collection (ALE) Interface. Define control and delivery of filtered and collected tag read data Filtering and collection (EPCIS Capturing Application)

EPCIS Capturing Application Supervise the operation of the lower EPC element Provide business context (check for exceptional condition)

EPCIS Capture Interface. EPCIS data is delivered to enterprise-level roles Roles : EPCIS Repositories, EPCIS Accessing Application, data exchange with partners EPCIS Accessing Application Carry out overall enterprise business processes (i.e warehouse management, shipping and receiving, etc) EPCIS Repository Record EPCIS-level events generated by EPCIS Capture Application Make available for later query by EPCIS Accessing Application

Figure 3. Data Flow Diagram for Intra-Enterprise Relationship. Interfaces Insulation Each Interface insulate the higher level from lower level References Responsibilities and collaborations Reader Management Interface (Interface) Query the configuration of an RFID Reader Monitor the operational status of an RFID Reader Acces RFID Reader management functions

Reader Management (Role) Monitor the operational status of one and more RFID Readers

Manages the configuration of one and more RFID Readers Carries other RFID reader management functions

Tag Data Translation Schema (Core Service) How to translate between EPC Encodings

Tag Data Translation Interface (Interface) Roles that define how to translate between EPC encodings

Figure 4. Role Interface References