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

More documents

Recommendations

Info

2763 2764 2765 2766 2767 2768 2769 2770 2771 2772 2773 5. The stop trigger is received. The ECSpec transitions to the “Requested” state. 6. The ECReports is generated and sent asynchronously to the observer. 13.2.3 Scenario 2, 3: Poll, Immediate The scenario shown illustrates an ALE client using the poll method of the ALE interface to synchronously obtain the EPC data it is interested in collecting. The ECSpec shown in this scenario specifies the event cycle boundary to be a duration of time. Later in the scenario the ALE client uses the immediate method of the ALE interface, again synchronously obtaining EPC data. The combination of poll and immediate is not required, and only serves to illustrate a possibility. This is a normal scenario involving no errors. 2774 2775 2776 2777 2778 2779 13.2.3.1 Assumptions 1. All discovery, configuration, and initialization required has already been performed. 2. The ALE layer is implemented as a distinct software component. 3. ECSpec boundary condition is specified as duration. Copyright © 2005, 2004 EPCglobal Inc, All Rights Reserved. Page 68 of 71
2780 2781 2782 2783 2784 2785 2786 2787 2788 2789 2790 2791 2792 2793 2794 2795 2796 2797 2798 2799 2800 2801 2802 2803 2804 2805 2806 2807 2808 2809 2810 2811 2812 2813 4. ECFilterSpec includePatterns includes the EPC(s) illustrated in this scenario. 13.2.3.2 Description 1. The ALE client calls the define method of the ALE interface. The ECSpec contains a valid duration as the boundary specification – though any valid boundary conditions could be specified. The ECReportSpec and ECFilterSpec contained within the ECSpec are defined to include the EPC data sent later in steps 3 and 4. At this point the ECSpec is considered “Unrequested.” 2. The ALE client calls the poll method of the ALE interface, naming the ECSpec previously defined in Step 1. At this point the ECSpec is transitioned to the “Active” state, and the event cycle begins for the duration specified in the ECSpec. During the duration of the event cycle the ALE client is blocked waiting for a response to the poll method. 3. An EPC which meets the filter conditions of the ECSpec is received during the event cycle. At the end of the event cycle, the ECReports is generated and returned to the ALE client as the response to the poll method. At this point the ECSpec transitions to the “Unrequested” state. 4. An EPC that meets the filter conditions of the ECSpec is reported to the ALE layer, but since there is no “Active” ECSpec, this EPC will not be reported. 5. The ALE client invokes the poll method of the ALE interface a second time. This is similar to the process described above in Steps 2 and 3, but since no EPC is received, no EPC data is returned in the ECReports. 6. Later, the ALE client calls the immediate method of the ALE interface. This is very similar to the use of poll, except that when the client calls immediate it provides the ECSpec as part of the method call, as opposed to referring to a previously defined ECSpec. Since a new ECSpec is provided with the immediate method, it can contain any valid combination of parameters and report options. 14 Glossary (non-normative) This section provides a non-normative summary of terms used within this specification. For normative definitions of these terms, please consult the relevant sections of the document. Term Section Meaning ALE (Application Level Events) Interface 1 Software interface through which ALE Clients may obtain filtered, consolidated EPC data from a variety of sources. Copyright © 2005, 2004 EPCglobal Inc, All Rights Reserved. Page 69 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 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: 2741 2742 2743 2744 2745 2746 2747
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?