Provides a means for clients to specify what EPC data they are interested in
. Provides a standardized format for reporting accumulated, ?¬?ltered EPC data that
is largely independent of where the EPC data originated or how it was processed
. Abstracts the sources of EPC data into a higher level notion of ??????logical reader,??™??™
often synonymous with ??????location,??™??™ hiding from clients the details of exactly what
physical devices were used to gather EPC data relevant to a particular logical
location
The speci?¬?cation includes a formal processing model, an application programming interface
(API) described abstractly via a Uni?¬?ed Modeling Language (UML), and bindings of
the API to a Web Services Interoperability (WS-i) compliant Simple Object Access Protocol
(SOAP) with associated bindings of the key data types to XML schema.
The client of the ALE will be responsible for interpreting and acting on the meaning of
the report (i.e., the ??????business logic??™??™), and may be a traditional ??????enterprise application,??™??™ or
it may be new software designed expressly to carry out an EPC-enabled business process
but which operates at a higher level than the ??????middleware??™??™ that implements the ALE
interface. The ALE interface revolves around client requests and the corresponding reports
that are produced. Requests can either be (1) immediate, in which information is reported
on a one-time basis at the time of the request or (2) recurring, in which information is
reported repeatedly whenever an event is detected or at a speci?¬?ed time interval.
Pages:
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83