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

More documents

Recommendations

Info

2633 2634 2635 2636 2637 2638 2639 2640 2641 2642 2643 2644 2645 2646 2647 2648 2649 2650 2651 2652 2653 2654 2655 2656 2657 2658 2659 checkout clerk brought into the store that inadvertently happen to be read), something in the architecture needs to make sure such Items are not read or filter them out. Prevention might be achievable with proper portal design and the ability for the checkout clerk to override errant reads. Alternatively, the ALE implementation could filter errant reads via access to a list of Items (down to the serial number) that are qualified for sale in that store (this could be hundreds of thousands to millions of items), or the POS application itself could do it. With the list options, the requesting application would be responsible for maintaining the list. 4. For retail front door theft detection, applications will request the full EPC of any Item that passes through the security point portal and that has not be marked as sold by the store and perhaps that meet certain theft detection criteria established by the store, such as item value. Like the retail checkout use case, the assumption is that the ALE implementation will have access to a list of store Items (to the serial number level) that have not been sold and that meet the stores theft alert conditions. The requesting application will be responsible for maintaining the list, and will decide what action, if any, should be taken based on variables such as the value and quantity of Items reported. 5. For retail shelf theft detection, applications will request the number of Items that were removed from the shelf since the last read cycle, totaled by Item GTIN across all serial numbers. Object types other than Item should be filtered out. 6. For warehouse management, a relatively complex range of operations and thus requirements will exist. For illustration at this stage, one of the requirements is that the application will request the EPC of the slot location into which a forklift operator has placed a Pallet of products. Object types other than “slot” should be filtered out of the reading. The table below summarizes the ALE API settings used in each of these use cases. Use Case Event Cycle Boundaries 1 (ship/rcpt) Triggered by pallet entering and leaving portal Result Set R 2a (retail OOS) Periodic Additions & Deletions Report Settings Filter F(R) Complete Pallet & Case Item Report Type Group cardinality, G = pallet/case GTIN Group cardinality, G = item GTIN 2b (retail OOS) Periodic Complete Item Group cardinality, G = item GTIN 3 (retail ckout) Single Complete Item Membership (EPC) Copyright © 2005, 2004 EPCglobal Inc, All Rights Reserved. Page 62 of 71
2660 2661 2662 2663 2664 2665 2666 2667 2668 2669 2670 2671 2672 Use Case Event Cycle Boundaries 4 (door theft) Triggered by object(s) entering and leaving portal Result Set R Complete None Report Settings Filter F(R) Report Type Membership (EPC) 5 (shelf theft) Periodic Deletions Item Group cardinality, G = item GTIN 6 (forklift) Single Complete Slot Membership (EPC) 13 ALE Scenarios (non-normative) This section provides a non-normative illustration of the API-level interactions between the ALE interface and the ALE client and other actors. 13.1 ALE Context The ALE layer exists in a context including RFID readers, Users (administrative) and Client applications as shown below. Initially the administrators are responsible for installing and configuring the RFID environment. Once the environment is configured, EPC data (tag reads) are sent from the Readers to the ALE layer. In some cases the ALE layer may be implemented on the Reader or elsewhere, but in these scenarios we assume that the ALE layer is implemented as a distinct software component and is configured to support more than one Reader. Copyright © 2005, 2004 EPCglobal Inc, All Rights Reserved. Page 63 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: 2575 2576 2577 2578 2579 2580 2581
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

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

Delete template?

Save as template?