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

More documents

Recommendations

Info

692 693 694 695 696 697 698 699 700 701 702 703 704 705 706 707 708 709 710 711 712 713 714 715 716 717 718 719 720 721 722 723 724 725 726 727 728 729 730 • The duration, when specified, expires. • When the stableSetInterval is specified, no new EPCs are reported by any Reader for the specified interval (i.e., the set of EPCs being accumulated by the event cycle is stable for the specified interval). In this context, “new” is to be interpreted collectively among Readers contributing to this event cycle. For example, suppose a given event cycle is accumulating data from Readers A and B. If Reader A completes a read cycle containing EPC X, then subsequently Reader B completes a different read cycle containing the same EPC X, then the occurrence of EPC X in B’s read cycle is not considered “new” for the purposes of evaluating the stableSetInterval. Note that in the context of the stableSetInterval, the term “stable” only implies that no new EPCs are detected; it does not imply that previously detected EPCs must continue to be detected. That is, only additions, and not deletions, are considered in determining that the EPC set is “stable.” • The stopTrigger, when specified, is received. • The ECSpec transitions to the unrequested state. Note that the first of these conditions to become true terminates the event cycle. For example, if both duration and stableSetInterval are specified, then the event cycle terminates when the duration expires, even if the reader field has not been stable for the stableSetInterval. But if the set of EPCs is stable for stableSetInterval, the event cycle terminates even if the total time is shorter than the specified duration. Note that if the repeatPeriod expires while an event cycle is in progress, it does not terminate the event cycle. The event cycle terminates only when one of the four conditions specified above becomes true. If, by that time, the ECSpec has not transitioned to the unrequested state, then a new event cycle will start immediately, following the second rule for repeatPeriod (because the repeatPeriod has expired, the start condition is immediately fulfilled). If no event cycle termination condition is specified in the ECBoundarySpec – that is, stopTrigger, duration, and stableSetInterval are all unspecified, and there is no vendor extension termination condition specified – then the define and immediate methods SHALL raise an ECSpecValidationException. In all the descriptions above, note that an ECSpec presented via the immediate method means that the ECSpec transitions from unrequested to requested immediately upon calling immediate, and transitions from requested to unrequested immediately after completion of the event cycle. The ECTrigger values startTrigger and stopTrigger, if specified, must conform to URI syntax as defined by [RFC2396], and must be supported by the ALE implementation; otherwise, the define and immediate methods SHALL raise an ECSpecValidationException. Copyright © 2005, 2004 EPCglobal Inc, All Rights Reserved. Page 24 of 71
731 732 733 734 735 736 737 738 739 740 741 742 743 744 745 746 747 748 749 750 751 752 753 754 755 756 757 758 759 760 761 762 8.2.2 ECTime ECTime denotes a span of time measured in physical time units. duration : long unit : ECTimeUnit --- 8.2.3 ECTimeUnit ECTimeUnit is an enumerated type denoting different units of physical time that may be used in an ECBoundarySpec. MS // Milliseconds 8.2.4 ECTrigger ECTrigger denotes a URI that is used to specify a start or stop trigger for an event cycle (see Section 8.2.1 for explanation of start and stop triggers). The interpretation of this URI is determined by the ALE implementation; the kinds and means of triggers supported is intended to be a point of extensibility. 8.2.5 ECReportSpec An ECReportSpec specifies one report to be returned from executing an event cycle. An ECSpec contains a list of one or more ECReportSpec instances. reportName : string reportSet : ECReportSetSpec filter : ECFilterSpec group : ECGroupSpec output : ECReportOutputSpec reportIfEmpty : boolean reportOnlyOnChange : boolean --- The ECReportSetSpec specifies what set of EPCs is considered for reporting: all currently read, additions from the previous event cycle, or deletions from the previous event cycle. The filter parameter (of type ECFilterSpec) specifies how the raw EPCs are filtered before inclusion in the report. If any of the specified filters does not conform to Copyright © 2005, 2004 EPCglobal Inc, All Rights Reserved. Page 25 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: 657 658 659 660 661 662 663 664 665
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

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?