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

More documents

Recommendations

Info

495 496 497 498 499 500 501 502 503 504 505 506 507 508 509 510 511 512 513 514 515 516 517 518 519 520 521 522 523 524 525 526 527 528 529 530 531 532 533 534 or through more dynamic discovery mechanisms. The method for establishing and maintaining configuration of this kind is outside the scope of this specification. To summarize, the definition of ALE relies upon several related concepts: • A logical reader is a name that an ALE client uses to refer to one or more, raw EPC data event sources (“Readers”). In terms of the formal model of Section 3, an event cycle aggregates read cycle data from all of the Readers that are associated with the set of logical readers the ALE client specifies in its request. • A Reader is a raw EPC data event source. A Reader provides EPC data to an ALE implementation in a series of read cycles, each containing a list of EPCs. A Reader may map into physical devices in a variety of ways, including: • A Reader may map directly to a single physical device; e.g., a one-antenna RFID reader, a bar code scanner, or a multi-antenna RFID reader where data from all antennas is always combined. • Several Readers may map to the same physical device; e.g., a multi-antenna RFID reader where each antenna is treated as an independent source (in which case there would be a separate Reader for each antenna). • A Reader may map to more than one physical device; e.g., several RFID devices are used to triangulate location information to create synthesized read cycles for virtual “Readers” associated with different spatial zones. 8 ALE API This section defines normatively the programmatic interface to ALE. The external interface is defined by the ALE class (Section 8.1). This interface makes use of a number of complex data types that are documented in the sections following Section 8.1. Implementations may expose the ALE interface via a wire protocol, or via a direct API in which clients call directly into code that implements ALE. This section of the document does not define the concrete wire protocol or programming language-specific API, but instead defines only the abstract syntax. Section 11 of the document specifies the required binding of the API to a WS-i compliant SOAP protocol. Section 10 specifies the standard way in which the two major data types in this API, the Event Cycle Specification and the Event Cycle Report, are rendered in XML. Implementations may provide additional bindings of the API, including bindings to particular programming languages, and of the data types. The general interaction model is that there are one or more clients that make method calls to the ALE interface defined in Section 8.1. Each method call is a request, which causes the ALE implementation to take some action and return results. Thus, methods of the ALE interface are synchronous. The ALE interface also provides a way for clients to subscribe to events that are delivered asynchronously. This is done through methods that take a notificationURI as an argument. Such methods return immediately, but subsequently the ALE implementation may asynchronously deliver information to the consumer denoted by the Copyright © 2005, 2004 EPCglobal Inc, All Rights Reserved. Page 16 of 71
535 536 537 538 539 540 541 542 543 544 545 546 547 548 549 550 551 552 553 554 notificationURI. Different ALE implementations MAY provide a variety of available notification means (e.g., JMS, MQ-Series, TIBCO, e-mail, SOAP, etc.); this is intended to be a point of extensibility. Section 9 specifies notification means that are standardized, and specifies the conformance requirement (MAY, SHOULD, SHALL) for each. In the sections below, the API is described using UML class diagram notation, like so: dataMember1 : Type1 dataMember2 : Type2 --- method1(ArgName:ArgType, ArgName:ArgType, …) : ReturnType method2(ArgName:ArgType, ArgName:ArgType, …) : ReturnType Within the UML descriptions, the notation identifies a place where implementations SHALL provide for extensibility through the addition of new data members and/or methods. Extensibility mechanisms SHALL provide for both proprietary extensions by vendors of ALE-compliant products, and for extensions defined by EPCglobal through future versions of this specification or through new specifications. In the case of the standard XML bindings for ECSpec and ECReports, the extension points are implemented within the XML schema following the methodology described in Section 10.1. In the case of the standard SOAP binding for the ALE interface, the extension point is implemented simply by adding new operations to the WSDL. Copyright © 2005, 2004 EPCglobal Inc, All Rights Reserved. Page 17 of 71
Page 1 and 2: 1 2 3 The Application Level Events
Page 3 and 4: 52 53 54 55 56 57 58 59 60 61 62 63
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: 465 466 467 468 469 470 471 472 473
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?