正修科技大學 EPCglobal 標準簡介

EPCglobalGS1

2010 GS1 TW

Shawn Chen: Royal Roads University, Canada Master of Business Administration California Polytechnic State University Pomona International Business and Marketing : - : Digitimes

:MCP, MCSE, MCSD MCDBA ,CCNA, Foundation Certificate in EPC Architecture Framework

2010 GS1 TW

EPCgloabl Foundation Certificate in EPC Architecture Framework

2010 GS1 TW

2010 GS1 TW

GS1EAN197710828GS1 Taiwan198547119000200211UCCEAN2005GS1

2010 GS1 TW

GS1

2010 GS1 TW

EPCglobal1999MITAuto-ID (Auto-ID Center) (Electronic Product Code, EPC)20031031EANUCCEPCglobal Inc.Auto-ID LabsEPCglobalEPCAuto-ID Labs

2010 GS1 TW

EPCglobal()EPCglobalEPCEPCglobal(The Internet of Things)EPCglobal NetworkEPCglobal NetworkEPCglobalEPC

2010 GS1 TW

EPCglobal

2010 GS1 TW

What is the EPCglobal Architecture Framework?IDreadercomputerstelemetryEPC - electronic product codeONS - Object Naming ServicedataIDtelemetryEPC Information ServicesStandard dataRFIDtagStandard airprotocolStandard softwareInterfacesStandard querylanguageStandard networkarchitecture

2010 GS1 TW

What is the EPCglobal Architecture Framework?GOAL:

VISIBILITY IN THE SUPPLY CHAINEPCglobal Architecture Framework

2010 GS1 TW

EPCglobal Standards support 3 activitiesShared Service InteractionsEPCglobal Core Servicesand otherShared ServicesCompanyA Exchange of Physical objectswith EPCsExchange of data about EPCs1010101010101Company B

2010 GS1 TW

Identify The EPC Tag Data Specifications IdentifyShared Service InteractionsEPCglobal Core Servicesand otherShared ServicesCompanyA Exchange of Physical objectswith EPCsExchange of data about EPCs1010101010101Company B

2010 GS1 TW

The overall structure of an EPCurn:epc:id:sgtin:0037000.112345.400IANA prefix for names

Names for EPCs

EPC pure identity

SGTIN identifier type

Company Prefix

Item Reference & Indicator Digit

Serial NumberTogether, these are the GTIN

2010 GS1 TW

The EPCglobal Coding Schemes

Identity TypeTag EncodingsRelated GS1 KeyGID (General Identifier)GID-96SGTIN (Serialized Global Trade Item Number)SGTIN-96 SGTIN-198GTIN (with added serial #)SSCC (Serial Shipping Container Code)SSCC-96SSCCSGLN (Serialized Global Location Item Number)SGLN-96 SGLN-195GLN (with additional serial #)GRAI (Global Returnable Asset Identifier)GRAI-96 GRAI-170GRAIGIAI (Global Individual Asset Identifier)GIAI-96 GIAI-202GIAIDoD (Department of Defense )DoD-96

2010 GS1 TW

The Representation of EPCurn:epc:id:sgtin:0037000.112345.400Text Representation in Information Systems

2010 GS1 TW

Tag Data Translation001100000111010000100101011110111111010001100010010111111000000000000000000000000000000000000010 (Binary)Tag Data Translatorurn:epc:id:sgtin: 0614141.100743.2Tag Data Translation Schema

2010 GS1 TW

The Representation of EPCurn:epc:id:sgtin:0037000.112345.400001100000111010000100101011110111111010001100010010111111000000000000000000000000000000110010000urn:epc:id:sgtin:0037000.112345.400001100000001010000010110100101010100010000001100000011100100000000000000000000000000000110010000

sgtin:Header8 bits00110000Filter Value3 bits000Partition3 bits1010037000Company Prefix20-40 bits00001001010111101111112345Item Reference24-4 bits11011011011011001400Serial Number38 bits000000000000000000000000000000110010000

2010 GS1 TW

http://www.gs1-germany.de/internet/content/e6/e156/e158/e1354/Tag Data Translation (TDT) Demo

2010 GS1 TW

Identify & Capture The Tag Air Interface IdentifyShared Service InteractionsEPCglobal Core Servicesand otherShared ServicesCompanyA Exchange of Physical objectswith EPCsExchange of data about EPCs1010101010101Company B

2010 GS1 TW

Aim of the Tag Air Interface

2010 GS1 TW

UHF Class-1 Gen2 Uses

2010 GS1 TW

Worldwide UHF Gen2 OperationEuropeUSImpinj Propeller Tag Frequency ResponseJapan

2010 GS1 TW

RFID: NCC - 4.8UHFRadio Frequency IdentificationRFID922-928MHz10.5

2010 GS1 TW

How do I select the operating frequency?

2010 GS1 TW

Tag Air Interfaces

2010 GS1 TW

EPCglobal Tag Class Definitions Class 1Class 2Class 3Class 4IdentityEncryptionRead/writeuser memoryPowersource SensorsTransmitter Active communications

2010 GS1 TW

?RFIDTAG IDEPCRFIDTAG IDRFIDEPCglobal NetworkEPCGen2 Tags CHIPGen2 Tags CHIP

2010 GS1 TW

Capture The Reader Interface CaptureShared Service InteractionsEPCglobal Core Servicesand otherShared ServicesCompanyA Exchange of Physical objectswith EPCsExchange of data about EPCs1010101010101Company B

2010 GS1 TW

The Reader Interface ReadermoduleHostSpecifications of the interactions = Reader Interface

2010 GS1 TW

Reader Protocol

2010 GS1 TW

Reader ProtocolRFIDtriggerfilter

2010 GS1 TW

Low-Level Reader Protocol (LLRP)

2010 GS1 TW

LLRP RFIDLLRPRFIDLLRPEPCglobal C1G2

2010 GS1 TW

Capture The Reader Management Interface CaptureShared Service InteractionsEPCglobal Core Servicesand otherShared ServicesCompanyA Exchange of Physical objectswith EPCsExchange of data about EPCs1010101010101Company B

2010 GS1 TW

Reader ManagementRFIDRFIDRFIDRFID/RFID/

2010 GS1 TW

The Discovery, Configuration, and Initialization (DCI)

2010 GS1 TW

DCI (Step 2)(Step 2)Client(Step 4)(Step 2)Client(Step 3)

2010 GS1 TW

Capture The filtering & Collection (ALE) Interface CaptureShared Service InteractionsEPCglobal Core Servicesand otherShared ServicesCompanyA Exchange of Physical objectswith EPCsExchange of data about EPCs1010101010101Company B

2010 GS1 TW

ALEReaderCycleEventCycleLogical Readeror locationRequestRequestApplicationsApplicationsDatabasesReturn to requestoror specified recipientReportsFiltersGrouping

2010 GS1 TW

Logical Reader

2010 GS1 TW

Read and Event CyclesFiltersGrouping

2010 GS1 TW

Request from the ALE ClientRequestALE ClientApplicationReport(XML Schema)Specify theEvent Cycle Spec(ECSpec)

2010 GS1 TW

An example of read and event cyclesRead Cycle 2Read Cycle 3EPC1EPC2EPC3EPC1EPC2EPC4EPC1EPC5Read Cycle 1App 1 Event Cycle 1ADD ReportEPC1EPC2EPC3EPC4EPC5Read Cycle 5Read Cycle 6EPC3EPC4EPC3EPC5Read Cycle 4ReportEPC5EPC3EPC5Read Cycle 7EPC3EPC5App 2 Event Cycle 1App 3 Event Cycle 1App 2 Event Cycle 1NEW ReportEPC4EPC2DEL ReportEPC4EPC5

2010 GS1 TW

Returning the reportsRead Cycle 2Read Cycle 3EPC1EPC2EPC3EPC1EPC2EPC4EPC1EPC5Read Cycle 1App 1 Event Cycle 1ADD ReportEPC1EPC2EPC3EPC4EPC5EPC2ApplicationsApplicationsDatabasesReturn to requestoror specified recipient

2010 GS1 TW

What should the middleware do?Middleware should include 7 core capabilities:

Reader and device management ()Allows users to configure, deploy & issue commands to readers through common interface.

Data management () Ensures captured data is intelligently filtered & routed to appropriate destinations

Application integration ()You need messaging, routing & connectivity features to reliably integrate RFID data into existing systems (e.g. ERP, WMS or CRM)

Partner integration ()You need B2B integration features (e.g. partner profile management & communication protocols) to efficiently integrate with partners data over EDI or web-based systems

2010 GS1 TW

What should the middleware do? Process management ()Allows orchestrating RFID related end-to-end processes. E.g. link receiving process to inventory & POS processso system automatically reorders more products without human intervention when inventory is too low

Packaged RFID content (RFID)You dont have to start developing RFID applications (e.g. shipping or asset tracking) from scratch .

Architecture scalability ()Allows system to balance processing load across multiple servers & reroute data automatically if a server fails.

2010 GS1 TW

-1. WAL-Mart

2010 GS1 TW

Capture & Exchange EPCIS CaptureShared Service InteractionsEPCglobal Core Servicesand otherShared ServicesCompanyA Exchange of Physical objectswith EPCsExchange of data about EPCs1010101010101Company B

2010 GS1 TW

EPCISReadersFiltering & CollectionEPCIS Capture AppEPCIS RepositoryEPCIS Capture InterfaceEPCIS Query InterfaceALE InterfaceReader ProtocolInternal ApplicationsExternal ApplicationsInterfaceHardware / SoftwareEPCIS

2010 GS1 TW

What is EPCIS?InterfaceHardware / SoftwareEPCIS Capture App

2010 GS1 TW

EPCIS layersAbstract Data Model LayerEvent DataMaster Data

Data Definition LayerEPCISObject EventAggregation EventQuantity EventTransaction Event

Services LayerEPCISCapture InterfaceQuery Interface Capture InterfaceEPC EventQuery InterfaceEPCIS

BindingsEPCIS

2010 GS1 TW

EPCIS layers

2010 GS1 TW

WHYbizStep (e.g., packing)EPCIS Events at supply chain read points

2010 GS1 TW

Four Core EPCIS Event TypesObject EventsObservation of EPCsSGTINs are moved into storageAggregation EventsPhysical association of EPCs with parent EPCSGTINs are picked and assigned an SSCCQuantity EventsInventory of an object class (item reference)a total of ___ of GTIN 56789 are currently in storage Transaction EventsLink one or more EPCs to a business transactionSGTINs corresponding to DESADV 4711 are shipped

2010 GS1 TW

EPCIS Data Specifications Event DataEPC

Master DataEvent Data

2010 GS1 TW

EPCIS . . .is not an application, but rather a GS1/EPCglobal Standarddefines interfaces for the capture and query of datacan be integrated into ERP / tracking & tracing applicationsaugments rather than supplants traditional EDIdoes not require RFIDcan be used with GS1 bar-coded objectsClearing up some misconceptions on EPCIS

2010 GS1 TW

Interface Functionality of EPCglobal Standards EPCIS Capture Interface

2010 GS1 TW

EPCIS Capture InterfaceEPCIS Capture InterfaceEPCIS RepositoryEPCIS Capturing ApplicationEPCIS Capture Interface . . .defines operations by which core events are transmitted from an EPCIS Capturing Application to another EPCIS servicethe structure of EPCIS core events is defined in XSD-format

2010 GS1 TW

What?When?Where?

Why?Example: Aggregation Event

2009-10-23T12:27:11Z 2009-10-23T12:27:11Z +01:00 urn:epc:id:sscc:4001356.5900000817 urn:epc:id:sgtin:4026800.10421.101 urn:epc:id:sgtin:4026800.10421.102 ADD urn:epcglobal:cbv:bizstep:commissioning urn:epcglobal:cbv:disp:core:active urn:epc:id:sgln:4012345.01020.0 urn:epc:id:sgln:4012345.00020.0

2010 GS1 TW

storagecommssioningshippingEventEventEventEventEPCIS RepositoryEPCIS Capture of supply chain eventsproduction

2010 GS1 TW

Interface Functionality of EPCglobal Standards EPCIS Query Interface

2010 GS1 TW

EPCIS Query and Control InterfaceEPCIS Query InterfaceEPCIS Callback InterfaceEPCIS RepositoryEPCIS Query Interface . . .provides query responses directly (poll) or periodically (subscribe)provides for predefined, parameterised queriesSimpleEventQuery list of EPCIS Eventsperiodic transmission of query results by means ofdefined time plan (QuerySchedule)trigger (specifies an event which triggers a query response)

2010 GS1 TW

EPCIS query of supply chain eventsQuery&ResponseQuery&ResponseQuery&ResponseQuery&ResponseEPCIS Repositorypharmacy

2010 GS1 TW

ManufacturerbReceive TotePack Bottles into CasePick & Pack into ToteDistributorRetailer

Agg. Event5 Jun 12:50EPC X, YPlant 2 WarehousePackIn transit

Object Event3 Jun 10:15EPC XPlant 2 Pack AreaCommissionActive

Object Event8 Jun 15:20EPC X, YNYC Dock AreaReceiveSellable

Object Event10 Jun 11:35EPC XNYC Ship Area PickSellable

Object Event15 Jun 16:10EPC XStore #23 BackReceiveSellableEPCIS Event data Example

ObjectEventDateEPCsBusiness LocationBusiness StepDisposition

2010 GS1 TW

http://www.fosstrak.org/epcis/demo.htmlEPCIS Demo

2010 GS1 TW

Exchange Object Name Service (ONS)ExchangeShared Service InteractionsEPCglobal Core Servicesand otherShared ServicesCompanyA Exchange of Physical objectswith EPCsExchange of data about EPCs1010101010101Company B

2010 GS1 TW

How does ONS works? ONSEPCEPCEPCIS

2010 GS1 TW

The object name service (ONS)EPCIS Interface

ManufacturerDistributorRetailerObject Name Service (ONS)EPCIS Interface

EPCIS Interface

Query ONS with hostname based on EPC ClassFind authoritative source of information

2010 GS1 TW

The object name service (ONS) hierarchy

2010 GS1 TW

Querying ONS Convert into URI

00110000 001101000000001001000010001000 0000011101100010000100000000000000000011111110011000110010

urn:epc:id:sgtin:0037000030241104197000370000302411041970urn:epc:id:sgtin:..

2010 GS1 TW

The resolver converts the URI form into a domain name

00370000302411041970urn:epc:id:sgtin:..0037000030241sgtin.id..Querying ONS Convert into Domain Name.onsepc.com

2010 GS1 TW

Querying ONS DNS Lookup 0037000030241sgtin.id.onsepc.com..

2010 GS1 TW

http://www.apple.com/ipodphoto Querying ONS - Example of product-specific web page

0

0

u

EPC+html

!^.*$!http://www.apple.com/ipodphoto!

.

2010 GS1 TW

The role of the Local ONS

2010 GS1 TW

Exchange Discovery ServicesExchangeShared Service InteractionsEPCglobal Core Servicesand otherShared ServicesCompanyA Exchange of Physical objectswith EPCsExchange of data about EPCs1010101010101Company B

2010 GS1 TW

Discovery Services

2010 GS1 TW

Discovery Services is not ONSWho is manufacturing this watch?ONSDSIs this particular watch authentic?Not possible as ONS does not point to info on serialised EPCs

2010 GS1 TW

EPCIS Interface

ManufacturerDistributorRetailerObject Name Service (ONS)EPCIS Interface

EPCIS Interface

Point to source of informationDS QueryAuthenticate, check for authorizationDiscovery ServicesAuthenticate, check for authorizationFind multiple information providersInfo for individual EPCs+ policies to access itEPCIS + ONS + Discovery Service = VisibilityONS Query

2010 GS1 TW

Exchange Drug PedigreeExchangeShared Service InteractionsEPCglobal Core Servicesand otherShared ServicesCompanyA Exchange of Physical objectswith EPCsExchange of data about EPCs1010101010101Company B

2010 GS1 TW

Concept of e-Pedigree

2010 GS1 TW

Creation of an e-Pedigree/ProcessingShippedReceivedShippedReceived

2010 GS1 TW

- 1. EPCRFID Healthcare- Underpinning patient safety2. EPCRFID Healthcare-

2010 GS1 TW

Exchange Certificate ProfileExchangeShared Service InteractionsEPCglobal Core Servicesand otherShared ServicesCompanyA Exchange of Physical objectswith EPCsExchange of data about EPCs1010101010101Company B

2010 GS1 TW

EPCglobal Standards Summary

2010 GS1 TW

EPC Network vs. InternetInternet EPC NetworkComputers ComputersObject Objects()//InternetRFID Tag()EPC NetworkMAC AddressMAC AddressTags TIDTIDIP AddressInternetEPC EPC NetworkHUB/InternetRFID ReaderEPC NetworkReaderWWW ServerEPC ISSearch EngineInternetEPC DSEPCEPCISISDNSURLIPEPC ONSEPCISDSURL12345678

Foundation Certificate in EPC architecture framework

2010 GS1 TW

EPC/RFID : Foundation Certificate in EPC Architecture Framework: EPCglobal Foundation Certificate in EPC Architecture FrameworkEPCglobal Taiwan , EPC/RFID,

2010 GS1 TW

60402.570()

2010 GS1 TW

2010EPCEPC Global TaiwanEPC Global

*! T: 02-23939145 ext. 507 E: [email protected]

*The EPCglobal Standards support 3 broad activities within the EPCglobal Architecture Framework that are:1) Identify individual products, cases, loads, assets, etc, so that they can be tracked individually2) Capture data about the movement of physical assets, creating visibility3) Exchange data with IT applications and trading partners, to turn visibility into information and action

The EPC Tag Data Specifications defines the overall structure of the Electronic Product Code (EPC).It also defines the EPCglobal coding schemes, most of these schemes being derived from GS1 identifiersFinally the specifications also define the binary representations for use on RFID tags and the URN strings for use within information systems

A fundamental principle of the EPCglobal Network Architecture is the assignment of a unique identifier for physical objects, loads, locations, assets, and other entities whose use is to be tracked. This unique identity is the Electronic Product Code or EPC that has a capacity for over 274 billion serial numbers per item class on a 96-bit tagIn order to facilitate the use of the EPCglobal Network by all industry sectors, the EPC Tag Data Specifications provide a flexible framework that supports multiple coding schemes. This flexible framework enables each sector to incorporate its existing standards-based numberingsystem into its EPCs.In information systems, an EPC is a Uniform Resource Identifier or URI that is in text format. A URI identifier might specify the location of a resource (a URL) or its name (a URN) independent of location. Using a structured URN notation makes it easier to specify patterns e.g. for filtering IDs of the same product type or from the same manufacturer. Such ID patterns are used in both the ALE and EPCIS specifications. Structured URNs are also used as s starting point for making an ONS query.

Tag Data Translation Schema and Interface are provided by EPCglobal Inc. for translating between the EPC encodings defined by the Tag Data Specifications.This ensures that components of the end-users infrastructure may automatically become aware of new EPC formats as they are definedThere are several Tag Air Interfaces that have been defined for use within the EPCglobal Network and several under development.The UHF Class 1 Gen 2 Tag Air Interface is a ratified EPCglobal standard and also a ratified ISO standard while the three others Tag Air interfaces were published by the Auto-ID Center prior to the creation of EPCglobal.

The Tag Air Interface indicates:How to communicate a command to a tag from an RFID ReaderHow to communicate a response from a tag to the RFID Reader that issued the command.How to provide means for a reader to singulate individual tags when more than one is within range of the RFID Reader. And finally How to provide means for readers and tags to minimize interference with each other.

Gen2 tags are far more than mere bar-code replacementsUHF Class 1 Gen 2 has several uses such asIndentifying the tags in an inventoryReading user memory for additional item informationWriting travel history and destination into a baggage tagStoring an in-service date into a tag and locking itDisabling or killing a tag before the consumer checks out

Early 2008, the UHF spectrum was available in more than 55 countries with around 15 additional countries in the approval process.This broad availability of the UHF spectrum ensures the same tags operate worldwide

As we have learned, the operating frequency will directly impact the performance of the RFID system.Therefore, the main factors that you should consider when selecting your operating frequency are your application requirements and the operating conditions. The read range requirements for your application will give you a very good idea as to which frequency you should select for your system.Most application types such as warehouse management have a common set of requirements and are therefore associated with specific frequencies. You should finally also factor under which conditions your system will operate as higher frequencies are more subject to interferences and problems with materials such as liquids or metals.

*EPCglobal continues to develop additional tag air interfaces so as to fulfil additional needs.Tag Air interfaces under development include:The UHF Class-2 Gen2 that is based on the existing Class-1 Gen2 and adds an extended Tag ID, an extended user memory, data protection, and authenticated access controlThe HF Class-1 Gen2 that is a Class-1 specification using the 13.56 Mega Hertz frequency tailored for identifying itemsThe UHF Class-3 Gen2 that is a UHF specification for sensor and battery tags built upon existing Class-1 and Class-2 Gen2 and finally the UHF Class-4 Gen2 that is a UHF specification for active tags

*The Auto-ID Center at the Massachusetts Institute of Technology (MIT) has defined an RFID Class Structure to provide a framework for the discussion and development of RFID tag functionality. From this structure, EPCglobal Inc. has developed Tag Class Definitions describing the functionalities of the tags in each of the 4 classes that are:Class 1 tags are passive tags having basic functionalities as they generally only contain an EPC to identify the product and a Tag ID to identify the tag.They also have embedded a function that renders a tag permanently non-responsive Optionally, they can have user memory, a password-protected access control and the possibility to decommission or re-commission the Tag, Class 2 tags are passive Tags too with additional features above and beyond those of Class-1 Tags that are an extended Tag ID, an Extended user memory and an Authenticated access control.Class 3 tags are semi-passive tags having a power source that may supply power to the Tag and/or to its sensors. Class 3 tags can have sensors with optional data logging. Class 4 tags are active Tags having access to a transmitter so that they typically can initiate communications with a reader or with another Tag. Protocols may limit this ability by requiring a reader to initiate or enable Tag communications. Class-4 Tags shall not interfere with the communications protocols used by Class-1/2/3 Tags.

A Reader Interface provides the means for software on the host system to control aspects of RFID Reader operation, including the capabilities implied by features of the Tag Air Interfaces. All EPCglobal Reader Interface standards are designed to provide complete access to all capabilities of the UHF Class 1 Gen 2 Tag Air Interface, including reading, writing, locking, and killing tags. There are different Reader Interface standards that are the Reader Protocol (RP) and the Low-Level Reader Protocol (LLRP) that provides greater control to clients over the use of the Radio Frequency channel and protocol-specific tag features such as Gen2 inventory sessions. All Reader Interfaces abstracts away specific reader brand and model used

*To operate efficiently, a reader needs a reader interface that specifies the interactions between a device capable of reading/writing tags and application software as to control the aspects of RFID Reader operation. EPCglobal has developed Reader Interface standards that are the Reader Protocol and the Low-Level Reader ProtocolAll EPCglobal standards are designed to provide complete access to all capabilities of the UHF Class 1 Gen 2 Tag Air Interface, including reading, writing, locking, and killing tags.

*The Reader Protocol is an EPCglobal standard that specifies the interaction between a device capable of reading and possibly writing tags namely the tag reader and an application software or host. A goal of the Reader Protocol is to insulate the Host from knowing the details of how the Reader and tags interact.The Reader Protocol defines 3 different layers that are the Reader layer, the Messaging Layer and the Transport Layer*The Low Level Reader Protocol or LLRP specifies an interface between RFID Readers and Clients. The interface protocol is called low-level because it provides control of RFID air protocol operation timing and access to air protocol command parameters. It also recognizes that coupling control to the physical layers of an RFID infrastructure may be useful for the purpose of mitigating RFID interference. Unlike other automated data collection systems such as bar code, an RFID system is essentially a wireless infrastructure. LLRP was designed to provide direct control over the wireless aspects of an RFID reader.

The Reader Management Interface defines the standards for monitoring operation of readers such as querying readers for their identity or their number of antennas.It also provides means to monitor the operational status of the reader such as the number of tags read, the status of the communication channels or any potential operational problem of the reader.*An effort is underway to develop a standard that specifies a new device, called an Access Controller. An Access Controller performs several Discovery, Configuration and initialization functions or DCI. These functions include the initial configuration requirements that an RFID Reader or Client must satisfy, in order for DCI operations to be successful. The purpose of the protocol specified in this proposed standard is to identify how the Reader discovers one or more Clients, the Client discovers one or more Readers, and for the Reader to obtain configuration information, download firmware, and initialize operations to allow other Reader Operation protocols to operate. The Application Level Events or ALE Interface coordinates the activities of one or more RFID Readers that occupy the same physical space and which therefore have the possibility of radio-frequency interference. It also raises the level of abstraction of the raw tag reads from the readers to one suitable for application business logic.Reducing the volume of raw tag reads and transforming the read data into streams of events suitable for application logic can be done for example by:* Filtering the raw data as to eliminate all but EPCs for a specific object classAggregating the raw data over time interval as to eliminate duplicate readsCounting the number of EPCs rather than the EPC valuesPerforming differential analysis as to report which EPCs have been added or removed within a time interval instead of reporting all EPCs reads.

In this topic, we will look in detail at the different aspects of the ALE that is the interface through which clients may interact with filtered, consolidated EPC data and related data from a variety of sources. Filtering and grouping the data received from the readers are key roles of the ALE interface as otherwise the client application would be overwhelmed by useless data. One or more individual readers might be clustered together to form a 'logical reader'. Logical readers are defined at a more abstract level, to allow for changing physical readers without disturbing the applications and to combine data from multiple physical readers. Some logical readers may correspond to physical locations monitored by readers, such as a particular shelf or dock door and in this sense, the logical reader is providing the 'Where' information.

A read cycle is the smallest unit of interaction with a reader that is a single atomic event containing a set of EPCsThe frequency of the read cycles is under control of the readers or the reader management, it is not controlled by the client applicationsThe output of the read cycle is the input to the event filtering and grouping layer

An Event Cycle is an interval of time during which Tags are read. At the conclusion of an event cycle, a report, containing information read from the Tags and based on the ALE clients request, is sent to the ALE client. At the other end, the an ALE client application interacts with the ALE interface by making a request in which an Event Cycle Spec or ECSpec is specified. In the ECSpec request, a client application can specify whether they wish to receive:the objects that are currently present at the reader OR the differential set consisting of the objects that have arrived or departed since the previous Event Cycle. The client application can also specify a number of filtering operations to be performed on the event data. For example, the client can use EPC patterns (as defined in Tag Data Standards) to request only data for a particular product line (SKU) or from a particular manufacturer. The client can also specify grouping operations, so that all objects of the same pattern (e.g. having the same SKU) are grouped together The reports are in a standardized format that is XML schema The client application can make a one-off poll to ALE - or it can set up a subscription for filtered data, to obtain all future events that match the filtering criteria.

- and the results can be sent either back to the client that specified the ECSpec - or to another recipient, specified via a URI. Event cycles can collect reader cycles from more than one reader.As several ALE client applications can perform simultaneously several request, the same tag data are shared by all active events cycles that request data from a given reader.The tags read during the cycle event are filtered and grouped based on the ECSpec provided by the ALE Client application as to generate a report.

At the conclusion of an event cycle, a report, containing information read from the Tags and based on the ALE clients request, is sent back to the ALE client that had specified the ECSpecThe report can also be sent to another recipient, specified via a URI.

Typically, your middleware should include 7 core capabilities that are:Reader and device management as to allow the users to configure, deploy and issue commands to the readers through a common interface.Data management as to ensure the captured data is intelligently filtered and routed to the appropriate destinationsApplication integration as you need these messaging, routing and connectivity features to reliably integrate the RFID data into your existing systems such as your ERP, WMS or CRM systemsPartner integration as you need B2B integration features such as partner profile management and communication protocols to efficiently integrate with your partners data over EDI or web-based systems

*Process management as to allow you to orchestrate RFID related end-to-end processes. As an example you might want to link your receiving process to your inventory and to your point-of-sale process so that the system automatically reorders more products without human intervention when the inventory is too lowPackaged RFID content as you dont want to start from scratch developing your RFID applications such as shipping or asset tracking.Architecture scalability as you want your system to balance the processing load across your multiple servers and reroute the data automatically if a server fails*The EPC Information Services or EPCIS is composed of 3 ratified standards that are:The EPCIS Capture Interface The EPCIS Data Specification and The EPCIS Query InterfaceIt is important to note that EPCIS is a supplement to, not a replacement for, existing enterprise information systemsIn this topic, you will understand the different layers of EPCIS and comprehend the difference between event and master data. You will learn in detail how event data is stored in the EPCIS repository and how this data can be captured and queried via EPCIS interfaces.The EPC Information Services is an EPCglobal standard that enables disparate applications to leverage EPC data via EPC-related data sharing, both within and across enterprises. EPCIS is a supplement to, and not a replacement for, existing enterprise information systems.EPCIS is composed of:A data model for defining events that can occur during the life of an uniquely identified objectAnd interfaces for the capture and query of events

*Within the EPCIS Data Specifications, the different layers are:The Abstract Data Model Layer specifies the kinds of data that is handled by EPCIS. This consists of Event Data and Master Data. The Data Definition Layer specifies what data is exchanged through EPCIS, for which type of event and also provides an XML schema bindingThe Service Layer defines the query and capture interfaces through which EPCIS clients interact. Bindings for the these interfaces are provided to web services (through WSDL files) and to AS2.

The EPCIS Data Specification lays out a general organisation for master data and transactional event data. It defines specific event types, master data vocabularies, and master data attributes that are used within a particular industry. Event types record the activity happening in real world and answers the questions what, where, when and whyMaster Data provides descriptions of locations, products, etc as well as context for the eventsMaster Data is expected to be shared via GSDN or other means

Mglichkeiten einer Integration des RFID-Tags in EAN128-Transportetikett - Hinweis auf EPCMglichkeiten einer Integration des RFID-Tags in EAN128-Transportetikett - Hinweis auf EPCWo?Wie viele?Woher?Wohin?

Es geht also um Informationen, die erfasst, gespeichert und ausgetauscht werden mssen. Was bietet das EPCglobal Netzwerk?Mglichkeiten einer Integration des RFID-Tags in EAN128-Transportetikett - Hinweis auf EPCMglichkeiten einer Integration des RFID-Tags in EAN128-Transportetikett - Hinweis auf EPCIn this example, we are following the transfer of bottles from the manufacturer to the retailer via the distributor.Each step of this transfer is an event with its associated captured data.By accessing this event data, partners in the supply chain can retrieve the business information they are looking for.As an example, the manufacturer can calculate how much time it took for the bottle to reach the retailer by comparing his shipping date with the retailer receiving dateThe Object Name Service (ONS) is a lookup service that takes an EPC as input, and produces as output the address or URL of an EPCIS service designated by the EPC Manager of the EPC in question. Although the ONS does not enable finding other parties in the supply chain, it proves very useful for finding which EPC Manager, generally a manufacturer, manages the EPC that is searched for. ONS is a distributed application composed of a root ONS and local ONSs as it would not be practical to implement ONS as one gigantic directory.

ONS works as follows. When an EPCglobal Subscriber wishes to locate an EPCIS service, it first consults the Root ONS service controlled by EPCglobal. The Root ONS service identifies the Local ONS service of the EPC Manager organization for that EPC. The EPCglobal Subscriber then completes the lookup by consulting the Local ONS service, which provides the pointer to the EPCIS service in question. The Object Naming Service or ONS is a global service operating in a similar way as the yellow pages.Companies can search these yellow pages for EPCs and retrieve the URLs pointing to the sources where authoritative information on the searched objects may be found. In general, the main source of information on the object is the manufacturer EPCIS but the URLs can point to other sources such as websites or Internet resources..ONS is implemented in a hierarchical design, which depends on the EPC identifier being structured. This allows the ONS root to resolve the company code such as the GS1 Company Prefix, while individual companies can operate their own 'second-tier' ONS to resolve particular product lines within their organization.Note that ONS can point to various types of services including EPCIS, product-specific web pages, general web services. An ONS record could also point to a relevant Discovery Service for an object class - although there might be other mechanisms for finding the address of a Discovery Service.The binary string is converted to the URI format of the EPCThe resolver converts the URI form into a domain name byRemoving the urn:epc: prefixRemoving the serial number field that is the rightmost period character and all characters to the right of it.Replacing each colon character with a period character Inverting the order of the remaining period-delimited fields Appending .onsepc.com.

A DNS lookup is performed to obtain the type 35 records these are NAPTR records for this address

For example, you could select EPC+html to find a web page about a specific product

The local ONS is simply the local DNS.ONS records are simply DNS records of a particular type that is type 35 or NAPTR records and for addresses within a specific domain that is onsepc.comA local ONS can cache DNS records so that local applications can use the records from the local cache instead of having to query the ONS root each time.The local ONS may contain the records that resolve for individual product classes within a company.

Discovery Services are standards under development that will provide the means to discover EPCIS data even when that data is under the control of other parties with whom no prior business relationship exists..Obviously, to obtain the searched EPCIS data, the requesting partner has to be authorised to access it as each company keeps its own data, and chooses when and with whom to share.When trading partners know each other, they can simply provide access to their EPCIS as EPCIS standards provide means for point-to-point connexions. In that case, you have to know where the other EPCIS servers are which is challenging if three or more parties are involved as we will see in an example.

Discovery Services will provide a mechanism to find the addresses of multiple providers of information collected during the lifecycle of a particular EPC The sequence of custodians as an object moves through its unique supply chain is a subset of the addresses spanning the whole product lifecycle from beginning-of-life (design, manufacturer) to end-of-life (recycling, remanufacture).

As we have learned previously, ONS queries are performed on EPC classes only, not on individual serialised EPCs.Unlike ONS, Discovery Services will hold different 'link' information for EPCs of the same class but with different serial numbers.Such serial-level data is commercially sensitive because it can be mined to reveal information about volumes and flows of goods.Security is therefore particularly important and challenging for Discovery Services. Discovery Services will need to provide for:Client authentication and secure communication linksEnforcement of access control policies that determine which users/roles are allowed to see which 'link' informationAnd the Ability to be audited.

In this example, we will see how Discovery Services are going one step further than the ONS.Anyone can anonymously query ONS with a hostname based on an EPC Class.Upon receipt of the query, ONS will point to the authoritative source of information that is generally the manufacturer of the queried object.Each information provider can dynamically post records and events to a Discovery Service to say that they hold information for individual EPCs. They can also set policies to control access to this 'link' info.Authenticated authorized clients can query a Discovery Service about a fully serialized EPC to find 'link' info.

In an attempt to help ensure only authentic pharmaceutical products are distributed through the supply chain, some regulatory agencies, have implemented or are considering provisions requiring a pedigree for drug products. Drug Pedigree Messaging is a data exchange interface intended to standardize the exchange of electronic pedigree documents. A pedigree is a certified record that contains information about each distribution of a prescription drug such as product information, transaction information, distributor information, recipient information, and signatures. *The authentication of entities (subscribers, services, physical devices) operating within the EPCglobal network serves as the foundation of any security function incorporated into the network. The EPCglobal architecture allows the use of a variety of authentication technologies across its defined interfaces. It is expected, however, that the X.509 authentication framework will be widely employed within the EPCglobal network. To this end, the EPCglobal produced the EPCglobal X.509 Certificate profile that provides a minimum level of cryptographic security and defines and standardizes identification parameters for users, services, servers and devices. *