The Application Level Events (ALE) Specification, Version 1.0 - GS1
The Application Level Events (ALE) Specification, Version 1.0 - GS1
The Application Level Events (ALE) Specification, Version 1.0 - GS1
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
2691<br />
2692<br />
2693<br />
2694<br />
2695<br />
2696<br />
2697<br />
2698<br />
2699<br />
2700<br />
3. Immediate(ECSpec)<br />
4. Operation Errors<br />
5. System Errors<br />
13.2.1 Scenario 1a: Direct Subscription<br />
<strong>The</strong> scenario shown below involves a client application specifying the EPC data it is<br />
interested in collecting. After specifying the ECSpec, it then subscribes to receive the<br />
resulting ECReports. <strong>The</strong> ECSpec shown in this scenario specifies that event cycles<br />
should repeat periodically. <strong>The</strong> ECReportSpec requests reports for additions and<br />
deletions, and reportIfEmpty is set to false. This is a normal scenario involving no<br />
errors.<br />
2701<br />
2702<br />
2703<br />
2704<br />
2705<br />
2706<br />
2707<br />
2708<br />
2709<br />
13.2.1.1 Assumptions<br />
1. All discovery, configuration, and initialization required has already been<br />
performed.<br />
2. <strong>The</strong> <strong>ALE</strong> layer is implemented as a distinct software component.<br />
3. ECSpec boundary condition specified using: repeatPeriod<br />
4. ECFilterSpec includePatterns includes the EPC(s) illustrated in<br />
this scenario<br />
5. Client 1 is the only client of <strong>ALE</strong> and the only subscriber of the ECSpec<br />
Copyright © 2005, 2004 EPCglobal Inc, All Rights Reserved. Page 65 of 71
Change language