The Application Level Events (ALE) Specification, Version 1.0 - GS1

More documents

Recommendations

Info

12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 Abstract This document specifies an interface through which clients may obtain filtered, consolidated Electronic Product Code (EPC) data from a variety of sources. The design of this interface recognizes that in most EPC processing systems, there is a level of processing that reduces the volume of data that comes directly from EPC data sources such as RFID readers into coarser “events” of interest to applications. It also recognizes that decoupling these applications from the physical layers of infrastructure offers cost and flexibility advantages to technology providers and end-users alike. The processing done at this layer typically involves: (1) receiving EPCs from one or more data sources such as readers; (2) accumulating data over intervals of time, filtering to eliminate duplicate EPCs and EPCs that are not of interest, and counting and grouping EPCs to reduce the volume of data; and (3) reporting in various forms. The interface described herein, and the functionality it implies, is called “Application Level Events,” or ALE. The role of the ALE interface within the EPCglobal Network Architecture is to provide independence between the infrastructure components that acquire the raw EPC data, the architectural component(s) that filter & count that data, and the applications that use the data. This allows changes in one without requiring changes in the other, offering significant benefits to both the technology provider and the end-user. The ALE interface described in the present specification achieves this independence through three means: • It provides a means for clients to specify, in a high-level, declarative way, what EPC data they are interested in, without dictating an implementation. The interface is designed to give implementations the widest possible latitude in selecting strategies for carrying out client requests; such strategies may be influenced by performance goals, the native abilities of readers which may carry out certain filtering or counting operations at the level of firmware or RF protocol, and so forth. • It provides a standardized format for reporting accumulated, filtered EPC data that is largely independent of where the EPC data originated or how it was processed. • It abstracts the sources of EPC data into a higher-level notion of “logical reader,” often synonymous with “location,” hiding from clients the details of exactly what physical devices were used to gather EPC data relevant to a particular logical location. This allows changes to occur at the physical layer (for example, replacing a 2-port multi-antenna reader at a loading dock door with three “smart antenna” readers) without affecting client applications. Similarly, it abstracts away the finegrained details of how data is gathered (e.g., how many individual tag read attempts were carried out). These features of abstraction are a consequence of the way the data specification and reporting aspects of the interface are designed. The specification includes a formal processing model, an application programming interface (API) described abstractly via UML, and bindings of the API to a WS-i compliant SOAP protocol with associated bindings of the key data types to XML schema. Copyright © 2005, 2004 EPCglobal Inc, All Rights Reserved. Page 2 of 71
52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 Implementors may provide other bindings, as well as extensions, as provided by the framework of the specification. Audience for this document The target audience for this specification includes: • EPC Middleware vendors • Reader vendors • Application developers • System integrators Status of this document This section describes the status of this document at the time of its publication. Other documents may supersede this document. The latest status of this document series is maintained at EPCglobal. See www.epcglobalinc.org for more information. This version of the specification was ratified by the EPCglobal Board of Governors on September 23, 2005. It was reviewed and approved by the EPCglobal Business Steering Committee on 14 February 2005 and by the Technical Steering Committee on 2 February 2005. Comments on this document should be sent to the EPCglobal Software Action Group Filtering and Collection Working Group mailing list sag_fc@epclinklist.epcglobalinc.org. Table of Contents 1 Introduction ..................................................................................................................6 2 Role Within the EPCglobal Network Architecture...................................................... 7 3 Terminology and Typographical Conventions............................................................. 9 4 ALE Formal Model ...................................................................................................... 9 5 Group Reports ............................................................................................................ 13 6 Read Cycle Timing..................................................................................................... 13 7 Logical Reader Names ............................................................................................... 14 8 ALE API..................................................................................................................... 16 8.1 ALE – Main API Class........................................................................................ 18 8.1.1 Error Conditions............................................................................................ 20 8.2 ECSpec ................................................................................................................ 22 Copyright © 2005, 2004 EPCglobal Inc, All Rights Reserved. Page 3 of 71
Page 1: 1 2 3 The Application Level Events
Page 5 and 6: 115 116 117 118 119 120 121 122 123
Page 7 and 8: 171 172 173 174 175 176 177 178 179
Page 9 and 10: 256 257 258 259 260 261 262 263 264
Page 11 and 12: EPC1 EPC2 EPC3 EPC1 EPC2 EPC4 EPC3
Page 13 and 14: 388 389 390 391 392 393 394 395 396
Page 15 and 16: 465 466 467 468 469 470 471 472 473
Page 17 and 18: 535 536 537 538 539 540 541 542 543
Page 19 and 20: 591 592 593 594 595 596 597 Once re
Page 21 and 22: 629 630 Exception Name DuplicateSub
Page 23 and 24: 657 658 659 660 661 662 663 664 665
Page 25 and 26: 731 732 733 734 735 736 737 738 739
Page 27 and 28: 800 801 802 803 804 805 806 807 808
Page 29 and 30: 865 866 867 868 869 870 871 872 873
Page 31 and 32: 903 904 905 906 907 908 909 910 911
Page 33 and 34: 964 965 966 967 968 969 970 971 972
Page 35 and 36: 1007 1008 1009 1010 1011 1012 1013
Page 37 and 38: 1078 1079 1080 1081 1082 1083 1084
Page 39 and 40: 1151 1152 1153 1154 1155 1156 1157
Page 41 and 42: 1232 1233 1234 1235 1236 1237 1238
Page 43 and 44: 1331 1332 1333 1334 1335 1336 1337
Page 45 and 46: 1471 1472 1473 1474 1475 1476 1477
Page 47 and 48: 1611 1612 1613 1614 1615 1616 1617
Page 49 and 50: 1751 1752 1753 1754 1755 1756 1757
Page 51 and 52: 1875 1876 1877 1878 1879 1880 1881
Page 53 and 54:
2015 2016 2017 2018 2019 2020 2021
Page 55 and 56:
2155 2156 2157 2158 2159 2160 2161
Page 57 and 58:
2295 2296 2297 2298 2299 2300 2301
Page 59 and 60:
2435 2436 2437 2438 2439 2440 2441
Page 61 and 62:
2575 2576 2577 2578 2579 2580 2581
Page 63 and 64:
2660 2661 2662 2663 2664 2665 2666
Page 65 and 66:
2691 2692 2693 2694 2695 2696 2697
Page 67 and 68:
2741 2742 2743 2744 2745 2746 2747
Page 69 and 70:
2780 2781 2782 2783 2784 2785 2786
Page 71:
2818 2819 2820 2821 2822 2823 2824
show all

The Application Level Events (ALE) Specification, Version 1.0 - GS1

Create successful ePaper yourself

Delete template?

Save as template?