You are on page 1of 6

Interaction of patients with breathing problems through NFC in Ambient Assisted

Living environments
Antonio J. Jara, Pablo López, David Fernández, Benito Úbeda, Miguel A. Zamora, Antonio F. G. Skarmeta
Clinical Technology Lab (CLITech)
Research Institute for Oriented Information and Comunications
Technologies (INTICO)
Computer Sciences Faculty, University of Murcia
Regional Campus of International Excellence "Campus Mare Nostrum"
Murcia, Spain

Abstract— Near Field Communication (NFC) is one of the
technologies, in conjunction with Bluetooth and 6LoWPAN,
which makes feasible the wireless transmission of information
from small objects and sensors to Internet-enabled devices.
This presents a new technological generation, denominated
Internet of Things (IoT), which is able to integrate in Internet
the sensors and objects located surround us. Our research
work is focused on the evaluation of the capabilities from the
mentioned technologies for the integration of a continuous data
transmission model. Specifically, this paper analyzes the
capabilities for transmitting continuous data from NFC. This
presents special considerations and constrains, since it was not
originally designed for this purpose. Specifically, it has been
considered, for this evaluation, a sensor with high
requirements in data transmission, an electrocardiogram
(ECG). Over this sensor is presented an evaluation of the
performance with the native communication model from the
sensor, i.e. sending via NFC all the collected data, concluding
that it is necessary to perform data compression when the
amount of data to send is too large, since this introduces a
delay of 2 bytes for each 127 bytes. Therefore, this work also
presents a solution of pre-processed and data compression to
make feasible the communication with NFC technology.
Keywords. Internet of Things; Near Field Communications;
continuous monitoring; NDEF Push Protocol; performance.
Internet of Things is considered one of the greatest advances
in communications in recent years, since it provides the
foundation for the development of autonomous applications
and services that enable make a more scalable operation and
maintenance. Currently, there are related jobs in areas such
as home automation [3], intelligent transportation systems
[4] and personalized healthcare [5].
Flexibility in conjunction with ubiquity, i.e. global and
mobile access, are the key aspects for the new generation of
data acquisition and monitoring solutions. Some examples of
this new generation of monitoring solutions are the located at
the clinical and Ambient Assisted Living environments.
Flexibility, ubiquity, global access capabilities and
mobility support are the features from the Future Internet.
For that reason, it is considered the extension of Internet with
the mentioned sensors, and devices, in order to exploit these
capabilities from Future Internet and reach what is called
Internet of Things [2].
In addition, the Internet of Things is complemented with
the mobile computing, with the generation of personal
devices, smart phones and the evolution of wireless
communications interfaces such as Bluetooth 2.1, the new
Bluetooth Low Energy (4.0), 6LoWPAN and NFC. They
make possible to extend the Internet to small sensors and
devices, in order to identify and connect all the things,
people and systems located around us.
The sensors integrated in the IoT presents a high
heterogeneity, it is located from sensors which transmit a
discrete value each several hours or even days, to sensors
with high requirements to support continuous data
transmission Within the new generation of technologies
based on Internet of Things (IoT) that provides a mean
through witch obtain a larger amount of data with high
accuracy and context awareness.
Our work is focused on the evaluation and discussion
about the performance of continuous data transmission
founded in different contexts which covers from
hydrological monitoring solutions [1] to assisted living
environments. Particularly, this works is focused in health
environments, but been applicable to others fields. In order
to study the NFC capabilities for the transmission of
continuous data, it has been chosen an ECG sensor, since
ECG presents high communications requirements and
Specifically, this paper presents an analysis of the
performance of communication capabilities offered by NFC,
with the communication protocol defined over NFC Data
Exchange Format (NDEF) and the NDEF Push Protocol
(NPP) to transmit data continuously from an RFID/NFC
reader connected via USB (ACR 122 from ACS [7]) to a
smart phone with NFC supports (Google Nexus S from
Samsung). Finally, future work will be focused on
continuous data transmission over Bluetooth Low Energy
(4.0), the second technology of IoT.
This paper is distributed in the following way. Section 2
describes the capabilities for real-time communication from
NFC technology. Section 3 presents the requirements from
the continuous data transmission model. Section 4 presents
the pre-processing technique to analyze the possible heart
2012 Sixth International Conference on Innovative Mobile and Internet Services in Ubiquitous Computing
978-0-7695-4684-1/12 $26.00 © 2012 IEEE
DOI 10.1109/IMIS.2012.150
issues and compress the trace to require a single NDEF
message. Section 5 shows a real application of this work.
Section 6 presents a comparative and evaluation about send
raw data from ECG or pre-processed. Section 7 makes a
discussion, and Section 8 presents the conclusions of this
solution and closes the paper specifying the future work.
NFC communications stack is composed rom bottom to top
as follows: APDU – LLCP – NPP – NDEF. It is necessary
to use the NPP protocol to send continuous data through
NDEF records as described in the following subsections.
A. APDU protocol
APDU (Application Protocol Data Unit) is the
communication unit between a smart card reader and a
smart card. The structure of the APDU is defined by
ISO/IEC 7816-4. The communication between the external
reader and the phone is transparent to the application itself
using APDU commands. APDU message is composed by
the fields presented in the Table I.
Header Body
CLA INS P1 P2 [Lc field] [Data field] [Le field]

The number of bytes present in the data field of the
command APDU is denoted by Lc. The maximum number
of bytes expected in the data field of the response APDU is
denoted by Le (length of expected data). When the Le field
contains only zeros, the maximum number of available data
bytes is requested. Among all the APDU commands that
exist, the most commonly used to communicate with the
mobile reader are:
- TG_INIT_AS_TARGET: With this command we can
start a client connection to a server hosted on the phone.
- TG_SET_DATA: With this command we can exchange
information with the phone, sending necessary data.
- TG_GET_DATA: With this command we can get the
server’s response and whether the last command sent
was correct.

APDU uses two communication protocols, with T=0, it
can only transmit 256 bytes at most, however with T=1, it
can be used the extension of payload and send up to 2
Specifically, T=0 defines a character-level transmission
protocol (ISO/IEC 7816-3), and T=1 defines a block-level
transmission protocol (ISO/IEC 7816-3).
B. NFC protocol
NFC is a contactless or proximity communication medium,
which is based on magnetic induction. This works on the
13,56Mhz frequency. The theoretical distance of standard
antennas (embedded in cards, tags or readers) is around 10
cm, with a practical working distance of 4 cm. The
bandwidth/speed for data transmission is 106, 212 or 424
Kbits/s depending on the mode of transmission and
hardware capabilities.
NDEF Message
R1 MB=1 … Rr … Rs … Rt ME=1
The communication in a NFC System is composed of
two elements:
- Initiator: This starts the commutation and
controls/manages the data exchange. An example
of initiator is a reader.
- Target: The device that respond to the
requirements of the initiator. An example of target
is a card or a tag.

NFC devices operate in two modes, passive or active.
- Passive mode: In this mode, one device generates
an electromagnetic field (reader), while another
device modulates this field for data transmission
(tag). It is founded on the conventional RFID
technology. NFC technology allows emulating a
HF card in a smart phone, in order to act as a
passive RFID HF card. NFC can also acts as a
reader for HF RFID tags.
- Active mode: In this mode, both devices generate
a magnetic field and modulate the opposite
magnetic field. This mode supports machine to
machine (M2M) communication. NFC operates in
this mode to talk between a reader and a smart
phone, or between two smart phones.

C. NDEF Messages and NDEF Records
NDEF is a lightweight binary message designed to
encapsulate one or more payloads in a single message.
NDEF messages can be nested, and are composed by NDEF
records. See Table II with the format and composition for a
NDEF message.
The minimal NDEF message is a unique NDEF record
with MB and ME flags set to 1, but a NDEF message can
contains various NDEF records. MB and ME mark the start
and end of a NDEF message respectively. Table II shows
the NDEF record format.
An NDEF record is not numbered, the application is
responsible to respect the order of the records. NDEF
records can be chained in order to support longer payloads
(fragmentation), Chunk Flag (CF) marks the fragmented
payload, SR the payload length which is between 0 and 256
bytes, and ID length (IL) indicates that the ID_LENGHT
field is present in the NDEF record header with one byte.
NDEF record has three parameters describing the payload.
Naming, TNF (Type Name Format) provides a context for
the payload, Type length, Type to describe the type of
payload. The value of the TYPE field must follow the
structure and format encoding implicit in the TNF field
value. ID field value is an identifier of URI form (RFC
3986). The referenced URI can be relative or absolute. The
intermediate and final segments must not have ID field.
Finally, it is defined and carried out the payload.
D. NDEF Push Protocol (NPP)
The communication between the ACS ACR 122 USB reader
and the smart phone is based on NPP protocol. NPP is a
protocol built on top of Logical Link Control Protocol
(LLCP) [8]. It is designed to push NDEF messages from one
device to another.
NPP offers a simple one way communication, pushing
NDEF messages from a client to a server. A device that
supports NPP always run an NPP server (listening), and may
also run the NPP client procedure when it has an NDEF
message available to push. Thereby, this allows bi-
directional NDEF exchange between NFC devices.
NDEF record can be until 255 bytes, but it has been
found a limitation with NPP, where it only can be sent 128
bytes of payload length. Therefore, in case that it is required
to send more than 128 bytes, it is required more than one
NDEF message, which means that it needs to reconnect
using Connect APDU from APDU commands [9].
Therefore, such as it is presented in the following sections,
in order to send wave traces from an ECG, it is required
more than 127 bytes per heartbeat (see Fig. I). This
introduces a high latency and an accumulative delay.
MB=1 ME=1 CF=0 SR=1 IL=0 TNF=001=0x01
(NFC Forum well-known types)
TYPE = ‘T’ (Text/plain)
Clinical sensors present native protocols for
communications, which provide from RAW data to sensors
which formatted format following a standard such as Health
Level 7 (HL7) and IEEE 1073 (X73). All of them require to
be pre-processed from their original protocol to NDEF
records, in order to make feasible the data transmission via
NFC. This pre-processing and adaptation tasks allows carry
out complex data analysis for anomalies detection, data
compression and security techniques applications. For
example, it can be included a Cyclic Redundancy Code
(CRC) for integrity, digital summary and signatures for
authentication and encryption for protection [6].
The sensor considered is an electrocardiogram (ECG).
Specifically, the ECG module chosen is the EG 01000 from
Medlab (see Fig. 2). This provides a continuous data
channel through a serial interface. This transmits the wave
trace of the called V2 in cardiology. The original protocol
has a sampling rate of 300 samples/second (Hz), and a high
resolution mode with an accuracy of 150 values per mV.
Thus, let a sampling frequency (e), with a value of 300
Hz, and where | is the bpm. It is required in total for each
pulse of _ bytes, equal to 236 bytes for the case of 76 ppm
following the equation 1. Fig. 1 show how many bytes are
transmitted according to the bpm.

Figure 1. Size of the frame according to the Beats Per Minute (BPM).

(1) 60*e/| = _

In addition, it is important to determine how much time
is required for each byte, in order to calculate the relevant
medical intervals, which are able to be used for a pre-
diagnosis analysis. The time required per byte is determined
following the equation 2.

(2) 1 byte/sec / 300 bytes/sec = 3,3 ms/byte

Data collected from the ECG module presented in Section
III can be transmitted directly, where approximately 250 to
336 bytes are required to transmit every beat. This direct
transmission means a high overload and impact in the
quality of service (delay and latency) and lifetime of the
personal device. For that reason, it is defined an optimized
communication model for NFC, in order to increase the
lifetime of the system and considering the requirements of a
personal system of this kind should reach a duration greater
than hours, even days. The compression model considered
to perform the pre-processed is the YOAPY module [6].
YOAPY has been already used with 6LoWPAN technology
and offer a suitable solution to reduce dramatically the
number of bytes required to transmit for each heartbeat.

Figure 2. Left: Evaluation environment formed by a wearable 3 leads
electrocardiogram. Right: ECG module connected to a voluntary patient.
YOAPY module is based on detect maximums and
minimums values in each wave of the PQRST complex, i.e.:
P maximum, Q minimum, R maximum, S minimum and T
maximum. In addition, it is processed and considered the
more descriptive segments, what permit us transport, and
redraw the PQRST complex. The segments can be
differentiated on the presented and described Fig. 3 of this
section, where the consecutive segments showed in the
bottom of figure are for their reconstruction, and the
intervals showed above the segments corresponds with the
medical interest intervals. This is possible because most of
the points as close to the value “0x7F” corresponding to no
signal and can be omitted.

Figure 3. Trace representation of pre-processed ECG. In the upper left is
presented the reference wave. The points are P: green, Q: yellow, R: Pink,
S: blue, and T: dark blue.
YOAPY format data contains the most significant fields
to represent and for the development of embedded
intelligent systems for the detection of abnormalities. The
data obtained information through YOAPY module defines
the payload for the NDEF message, which is transmitted
through NFC. YOAPY format contains five
maximum/minimum values, six segments, the heart beats
per minute and one byte for describe detected anomalies
founded by a simple analysis about the length of some
segments, this is 13 bytes that are ordered as shown in Table
The meaning of the fields in the table V is:
- The 5 maximum / minimum values describe the
difference between the beginning of the wave and
the maximum / minimum. Ie: max_P value
(maximum P wave) represents the height from the
P wave onset (init_P), to the maximum value of the
P wave. (P-init_P) 137 - 127 = 10.
- The 6 segments indicate the length in bytes of the
segments, from which are obtained the medical
intervals by adding some of these segments and
multiplying its length by byte time. For a better
understanding of the medical interval, check our
previous work located at [10].
- BPM: Represents de beats per minute (ppm).
- Diagnostic Byte: This byte indicates through his
bits some diagnostics.
All values except the TP segment (S_TP) and BPM are
represented by signed integers because their values never
overflow the limit of 127.

The system is composed of two parts with their respective
software. On the one hand, the PC has a Java program that
reads, analyzes, compresses, and encapsulates the received
frames from the ECG module through the serial interface in
a NDEF message. This NDEF message is sent through the
NFC USB reader via the smartcardio library. On the other
hand, an application for Android OS has been developed,
for processing the received frames through NFC and
presents it in a plot. Fig. 2 also presents the wearable ECG
connected to a voluntary patient, and transmitting data
continuously to the PC and Fig. 5 presents a capture of the
smart phone receiving compressed frames, represented in a
plot and showing the potential physical problems of the
heart monitored. In addition, it is available a video for
watching the monitoring system running

The part of the PC corresponds to the data acquisition
phase by a PC, which is focused to be replaced by an
embedded device such as personal device previously
developed and presented in [12], called Movital. For that
reason, it has been also considered the mentioned constrains
for the processing of the ECG wave trace.

Figure 4. ECG Wave reconstruction from Yoapy fields and Gauss
An evaluation has been carried to determine the time and
delay for pushing NDEF messages for a continuous
monitoring from the USB RFID/NFC reader to the smart

DEMO video of the monitoring system:
0 1 2 3 4 5 6 7

Wave trace
of reference
ECG curve
phone. It has been compared between a version of the
solution based on the full wave trace transmission, i.e. the
250-336 bytes per heartbeat from the RAW mode, and the
YOAPY pre-processed mode of sending only 13 bytes per
It has been found that for sending the 250-336 bytes
received in RAW mode from the ECG, it is required to send
from 2 to 3 frames (because NPP is limited to 127 bytes
such as mentioned in Section II) and each of them is a
partition of one complete raw trace.

Figure 5. Google Nexus S receiving data from ECG via NFC.
All comparisons shown below have been made in “T=0”
mode at 106Kb/s (Allowed mode by low cost devices).
Fig. 5 shows a graph where you can see the time it takes to
send frames (always containing the same data) in the
different modes described. 20 samples were taken in order
to obtain an average that approximates better the delivery
time, which will be used below to perform certain
The average for the times for transmissions measured
are 2372,25 ms (2 seconds) for RAW mode, and 22,5 ms
(0,02 seconds) for the solution based on the YOAPY mode.
The high value of delivery time in RAW mode is due to
the need to reconnect the session to send a message NDEF
causing a significant delay by the need to send two packets
to recover the session.

Figure 6. Time comparative between RAW mode transmision and
YOAPY mode transmission.
In conclusion, the RAW mode transmission produces a
delay for real-time and continuous monitoring of vital signs.
Since this requires more than 2 seconds for delivering a
sample which is obtained each less than 1 second (76 bpm,
means a heartbeat each 0,79 seconds). For example, when
the patient is monitored for 1 hour, the sample displayed
corresponds to 40 minutes ago. These calculations it is
obtained by the following formulas (3 and 4):

(3) 3600sec/2,37225sec per frame = 1517.54 frames

(4) 0,79sec per heart beat * 1517.54 = 1198.85 sec

That is, being 2.37225 seconds the average time to send
a complete frame in RAW mode, at 3600 seconds in one
hour, it is sent the number for plotting equal to 1518.
Thereby, 1518 value corresponds to the pulse generated in
the second 1198.85 (minute 19.98), being the heartbeat time
0.79 seconds to 76 bpm. An example of this accumulative
delay is shown below in Fig. 6 and 7.

Figure 7. Delay produced between generated and delivered frame in
RAW mode.

Therefore, the use of RAW mode is not feasible, since it
produces an accumulative delay. However, the use of
YOAPY mode, and its compression to send this information
allows to reach a short delay, around 0,02 seconds, which is
under the threshold of the 0,79 seconds. This delay can be
redeemed by sending 2 or more frames (up to 9 frames) if
necessary in a single NDEF message to update the delay.

Figure 8. Cumulative delay grows with the delivery of each frame when
not using YOAPY compression.

At the same that it was carried out for the pre-processing
time from YOAPY. It has been performed a set of tests,
considering also the analysis for several consecutive PQRST
Analyzing the results for the pre-processed (YOAPY)
time with respect to the transmission time of the frame in
RAW mode is drastically more efficient the YOAPY
YOAPY needs two frames ECG, current and previous,
such as mentioned in the Section IV. Thus, it is spent 15ms
on average in order to initialize a heartbeat, in case of
previous heartbeat (i.e., the program has just started or
erroneous frames for patient movement) and 0.1 ms during
the program because, we have the above pattern of the
Regarding the small delay produced by the pre-
processing module (YOAPY), this will make feasible the
real-time transmission, in addition to the extra analysis for
diagnosis, which can be helpful for caregivers, and nursing
Such as it has been presented in this document. The
evaluation has been carried out via NFC with the NPP
library ( from Android OS. But, it is not
suitable the continuous data transmission, since this presents
a bandwidth requirements over 127 bytes per second, since
this requires around 2 seconds to transfer a complete
heartbeat of approximately 250 bytes. This limitation for
sending the payload attached to the short duration of the
connection with NPP makes NFC not viable for sending
data in large quantities and continuously, compared to other
technologies such as Bluetooth 2.1. However, it can be
interesting to send a few fragments of data asynchronously,
and mainly it is highly intuitive for the interaction with
devices and sensors.
The limitations defined for NFC, are not only located at
the software, else it is also presents in the hardware, since
the low cost devices are not able to the extension of the
payload, i.e. T=1 for transferring by blocks. Thereby,
making it impossible to overcome the barrier of 127 bytes
well as the limitation of speed, making it unfeasible to send
frames long because the contact time would be too large and
uncomfortable, making other technologies are imposed on
NFC for purposes such as ours.
In the future with reduced hardware costs linked to the
advancement of android NPP protocol which offer an
extended version of the NPP service with the T=1 mode
support. At this moment, NPP in smart phones is its early
This work presents the integration of a clinical device with
continuous data transmission requirements in NFC
technology. This has been concluded that the direct
transmission of the collected data from an electrocardiogram
is not feasible, since the delay introduced for the
transmission of multiple NDEF messages, i.e. the time
required for pushing a new NDEF message is excessive.
But, this is suitable when the required frame size is
compressed to fill in a single NDEF record, i.e. less or equal
to 127 bytes because the NPP constrains. For that reason, it
has been also presented a pre-processing module called
YOAPY, which compresses and analyzes the vital signs
making feasible its continuous and real-time transmission
and obtaining a medical diagnosis.
Future work is focused to integrate this work to
Bluetooth Low Energy technology and extend the analysis
of the capabilities for real-time transmission.
This work has been made possible by the means of the
Excellence Researching Group Program (04552/GERM/06)
from Foundation Seneca, FPU program (AP2009-3981) from
Education and Science Spanish Ministry, with funds from
the frames of the IoT6 European Project (STREP) from the
7th Framework Program (Grant 288445).
[1] Cristina Sotomayor Martínez, A. J. Jara, Antonio F. G. Skarmeta:
“Real-Time Monitoring System for Watercourse Improvement and
Flood Forecast”. Lecture Notes in Computer Science. Springer
Verlag. Vol. 6935 pp 311-319. ISSN: 0302-9743, 2011.
[2] L. Atzori, A. Iera, G. Morabito, "The Internet of Things: A survey".
Computer Networks Vol. 54, No. 15, pp. 2787-2805, 2010.
[3] M. A. Zamora, J. Santa, A. F. G. Skarmeta, “Integral and networked
home automation solution towards indoor ambient intelligence,
Pervasive Computing, 2010.
[4] M. Castro, A. J. Jara, A. F. G. Skarmeta, “Extending Terrestrial
Logistics Solutions Using New-age Wireless Communications based
on SunSPOT”, V International Symposium on Ubiquitous Computing
and Ambient Intelligence (UCAmI’11), 2011.
[5] R.S.H. Istepanian, A. J. Jara, A. Sungoor, N. Philips, “Internet of
Things for M-health Applications (IoMT)”, AMA IEEE Medical
Tech. Conference on Individualized Healthcare, Washington, 2010.
[6] A.J. Jara, L. Marin, M. A. Zamora, A. F. G. Skarmeta, “Evaluation of
6LoWPAN Capabilities for Secure Integration of Sensors for
Continuous Vital Monitoring”, V International Symposium on
Ubiquitous Computing and Ambient Intelligence (UCAmI’11), 2011.
[7] ACS ACR122 NFC Reader Specification,, 2011.
[8] NFC Forum, Innovision, “Near Field Communication in the real
world - Turning the NFC promise into profitable, everyday
application”, “Near Field Communication in the real world - Using
the right NFC tag type for the right NFC application”, and “Logical
Link Control Protocol”, 2011.
[9] NXP Forum, PN532 transmission module for contactless
communication at 13.56 MHz used in ACR122, and PN532
Application Note,
2.pdf, 2011.
[10] A.J. Jara, F.J. Blaya, M.A. Zamora, A.Skarmeta, "An ontology and
rule based intelligent information system to detect and predict
myocardial diseases",IEEE Inf. Tech. App. in Biomedicine, ITAB,
[11] R.S.H. Istepanian, AA. Petrosian, “Optimal zonal waveletbased ECG
data compression for a mobile telecardiology system” IEEE Trans.
Infor. Tech. in Biomedicine, Vol.4, no. 3, pp. 200–211, 2000.
[12] A.J. Jara, M.A. Zamora, A. Skarmeta, “An Internet of Things–based
personal device for diabetes therapy management in AAL”, Personal
& Ubiquitous Computing, Vol. 15, no. 4, pp. 431-440, 2011