IV. ARCHITECTURE
In the following we provide details on the system
architecture for the implementation of the NFC use cases.
Because of the diverse nature of the use cases and different
hardware requirements, the architecture focuses on offering
abstract interfaces to facilitate and speed up the development of
the different applications. First, we describe the NFC/RFID
Service Platform which is a device-independent abstraction
layer offering web services to the applications. After that, we
show the overall architecture of the complete system including
different hardware devices and use cases.
A. NFC/RFID Service Platform
The NFC/RFID Service Platform is an abstraction layer
between the NFC devices and the applications, offering a
transparent access to different NFC devices of different
manufacturers with different hardware interfaces via simple
web services. The NFC/RFID Service Platform offers an
abstract, user friendly interface and a convenient notification
service, for example when devices are added or removed.
Currently the following tag types are supported: Mifare
Ultralight, Mifare 1K, ISO14443-A tags (Smart Cards,
DESFire).
Figure 1 illustrates the architecture of the NFC/RFID
service platform. It contains three modules: Web Services,
Messaging and Core. The NFC/RFID Service Platform runs
inside the Microsoft Internet Information Services (IIS). For
the messaging component, we use Active MQ as a languageindependent,
open-source message broker.
The NFC/RFID Core is an internal library implementing
the basic functionality of all NFC devices such as reading from
and writing to tags or peer-to-peer (P2P) functionalities. It
provides a common interface for several kinds of NFC devices
and thus forms an abstraction layer between the different
device interfaces and the web services module.
The notification mechanism of the NFC/RFID Service Platform
is provided by the NFC/RFID Messaging component. This
library uses the Active MQ message broker to broadcast
messages to all registered processes. Via this mechanism,
applications can be notified when devices are detected or
removed, when tags appear or disappear in the field or when a
message from a P2P device has been received. For receiving
notifications of a specific service the client applications need to
register at the Active MQ message broker.
IV. ARCHITECTURE
In the following we provide details on the system
architecture for the implementation of the NFC use cases.
Because of the diverse nature of the use cases and different
hardware requirements, the architecture focuses on offering
abstract interfaces to facilitate and speed up the development of
the different applications. First, we describe the NFC/RFID
Service Platform which is a device-independent abstraction
layer offering web services to the applications. After that, we
show the overall architecture of the complete system including
different hardware devices and use cases.
A. NFC/RFID Service Platform
The NFC/RFID Service Platform is an abstraction layer
between the NFC devices and the applications, offering a
transparent access to different NFC devices of different
manufacturers with different hardware interfaces via simple
web services. The NFC/RFID Service Platform offers an
abstract, user friendly interface and a convenient notification
service, for example when devices are added or removed.
Currently the following tag types are supported: Mifare
Ultralight, Mifare 1K, ISO14443-A tags (Smart Cards,
DESFire).
Figure 1 illustrates the architecture of the NFC/RFID
service platform. It contains three modules: Web Services,
Messaging and Core. The NFC/RFID Service Platform runs
inside the Microsoft Internet Information Services (IIS). For
the messaging component, we use Active MQ as a languageindependent,
open-source message broker.
The NFC/RFID Core is an internal library implementing
the basic functionality of all NFC devices such as reading from
and writing to tags or peer-to-peer (P2P) functionalities. It
provides a common interface for several kinds of NFC devices
and thus forms an abstraction layer between the different
device interfaces and the web services module.
The notification mechanism of the NFC/RFID Service Platform
is provided by the NFC/RFID Messaging component. This
library uses the Active MQ message broker to broadcast
messages to all registered processes. Via this mechanism,
applications can be notified when devices are detected or
removed, when tags appear or disappear in the field or when a
message from a P2P device has been received. For receiving
notifications of a specific service the client applications need to
register at the Active MQ message broker.
การแปล กรุณารอสักครู่..
