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

More documents

Recommendations

Info

2710 2711 2712 2713 2714 2715 2716 2717 2718 2719 2720 2721 2722 2723 2724 2725 2726 2727 2728 2729 2730 2731 2732 2733 2734 2735 2736 2737 2738 2739 2740 13.2.1.2 Description 1. The client calls the define method of the ALE interface. The ECSpec specifies that the event cycle is to begin using repeatPeriod as the boundary specification and to end using duration as the boundary specification (but 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 step 3. 2. The client calls the subscribe method of the ALE interface, including a URI that identifies the client itself as the destination for the ECReports. At this point the ECSpec is considered “Requested.” Since the start condition is given by repeatPeriod, the ECSpec immediately transitions to the “Active” state. 3. During period1 no new tags (additions) were reported by the Reader, and no deletions were noted, thus no ECReports is generated. 4. In period2, an EPC that does meet the filter conditions specified in the ECSpec is reported to the ALE layer by one of the Readers indicated in the ECSpec. 5. At the end of period2, the requested ECReports is generated and sent to the client. 6. In period3, no EPCs are reported, and no ECReports are generated. 7. In period4 the client calls the unsubscribe method of the ALE interface. As this client is the only subscriber, the ECSpec transitions to the “Unrequested” state, and no further ECReports are generated. 8. Because the ECSpec is Unrequested, the client can undefine the ECSpec without any error. 13.2.2 Scenario 1b: Indirect Subscription The scenario shown below involves a client application specifying the EPC data that is of interest to another observer. After specifying the ECSpec, the client subscribes a third party observer to receive the resulting ECReports. The ECSpec shown in this scenario specifies the event cycle to start and stop using a trigger mechanism. This is a normal scenario involving no errors. Copyright © 2005, 2004 EPCglobal Inc, All Rights Reserved. Page 66 of 71
2741 2742 2743 2744 2745 2746 2747 2748 2749 2750 2751 2752 2753 2754 2755 2756 2757 2758 2759 2760 2761 2762 13.2.2.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 conditions specified using startTrigger, stopTrigger 4. ECFilterSpec includePatterns includes the EPC(s) illustrated in this scenario 13.2.2.2 Description 1. The ALE client calls the define methods of the ALE interface. The ECSpec contains a valid startTrigger and stopTrigger as boundary specifications – though any valid boundary conditions could be specified. The ECReportSpec and ECFilterSpec contained within the ECSpec is defined to include the EPC data sent later in step 4. 2. The ALE client calls the subscribe method of the ALE interface which includes the URI of the intended observer. At this point the ECSpec is considered “Requested.” 3. After the start trigger is received, the ECSpec is considered “Active.” Subsequent EPCs that meet the filter conditions in the ECSpec will be collected by the ALE layer. 4. An EPC that does meet the filter conditions in the ECSpec is reported to the ALE layer. Copyright © 2005, 2004 EPCglobal Inc, All Rights Reserved. Page 67 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: 2691 2692 2693 2694 2695 2696 2697
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

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?