Physical Web for Smart Campus Management

Giorgio Delzanno, Giovanna Guerrini, Maurizio Leotta and Marina Ribaudo

Dipartimento di Informatica, Bioingegneria, Robotica e Ingegneria dei Sistemi (DIBRIS),

Università di Genova, Italy

Keywords:

Internet of Things, Physical Web, Beacon Technology, Indoor Location, Database Security.

Abstract:

Physical Web enables smartphone users to interact with physical objects and locations through the use of

beacon technology. Beacons are small devices placed on physical objects or at speciﬁc places that can be

detected by users’ smartphones when within a range of up to some tens of meters. In this way, users can receive

notiﬁcations on their handset or associate their presence with a speciﬁc place, enabling indoor localization. In

this paper, we present the design and the prototype development of a platform for Smart Campus management

based on the Physical Web metaphor. This beacon-enabled platform provides services for the registration and

analysis of student attendance and for the scheduling of lectures, classrooms allocation, and event notiﬁcations

(e.g., notify students when teachers are in their ofﬁce). The software prototype has been implemented using

state-of-the-practice technologies such as Node.js, Android, and MySQL and has been preliminary tested in

real setting in the context of the Computer Science Bachelor degree at the University of Genova obtaining

encouraging results.

1 INTRODUCTION

The Google’s Physical Web project

– center stage at

the Google IO developer conference in 2016 – was

conceived to enable smartphone users to interact with

physical objects and locations through the use of the

beacon technology. Beacons (Statler, 2016)

are low

cost radio transmitters that typically transmit a unique

ID on a regular interval, e.g., 100-1000ms, in a range

of approximatively 30 meters. Bluetooth-enabled de-

vices can detect a beacon and receive its correspon-

ding identiﬁer, following the so-called lighthouse me-

taphor. Smartphone applications can use such ID to

signal their physical presence in the beacon vicinity

to a remote server and the limited transmission range

of these transmitters provides precise users localiza-

tion.

The typical application domain of Physical Web

is that of proximity marketing (Jeon et al., 2018). In

this context beacons are located nearby speciﬁc pro-

ducts and smartphone applications, enabled to detect

beacons, redirect the user towards Web sites with de-

tails on the products, brand, coupons, special offers,

https://google.github.io/physical-web/

Google Physical Web architecture has been supported

with physical devices such as Estimote beacons and client

API’s.

etc. Beacons have been applied in other domains like

indoor localization (Huh and Seo, 2017; Zhu et al.,

2012; Kaulich et al., 2017; Mackey and Spachos,

2017; He et al., 2017), crowdsensing in public trans-

portation (Kang, 2017; Cianciulli et al., 2017), tou-

rism (Sato et al., 2017), usage of public spaces (Ng

et al., 2017; Purta and Striegel, 2017), support for el-

der people (Kashimoto et al., 2017), and so on. One

of the main issues precluding a wider adoption of the

Physical Web was the need to install native apps on

each user’s smartphone but, more recently, this limita-

tion has been circumvented thanks to client APIs and

by using browsers as delivery channel and show up

notiﬁcation, e.g. in the Android Notiﬁcations Mana-

ger

Our application of the Physical Web eco-system

is aimed at providing an automated support for the

management of typical Academic Campus services.

As an example, lecture attendance is often a relevant

factor inﬂuencing the performance of academic stu-

dents (especially bachelor). Intermediate tests are of-

ten used as a way to encourage students to actively

attend lectures and take exams. For instance, in the

Computer Science bachelor of the University of Ge-

nova, students are encouraged to sustain intermediate

https://developer.android.com/reference/android/app/

NotiﬁcationManager

Delzanno, G., Guerrini, G., Leotta, M. and Ribaudo, M.

Physical Web for Smart Campus Management.

DOI: 10.5220/0006959102770284

In Proceedings of the 14th International Conference on Web Information Systems and Technologies (WEBIST 2018), pages 277-284

ISBN: 978-989-758-324-7

277

tests during the courses. The goal here is to allow stu-

dents to split an entire exam into smaller parts thanks

to intermediate tests accessible only to students who

attend at least 75% of the lectures. Of course, inter-

mediate tests are not mandatory and those students

that, for any reason, cannot attend the lectures can

take the entire exam at the end of the semester.

In this paper, we present DidUp a software plat-

form providing (physical) Web services and mobile

applications for the registration and analysis of lec-

ture/meeting attendance, for the scheduling of lectu-

res, for classrooms allocation, and for events notiﬁ-

cation. The main novelty of our Physical Web appli-

cation comes from the use of beacons. Indeed, diffe-

rently from scenarios like proximity marketing orien-

ted to a single-user experience, in the DidUp eco-

system beacons are used to detect, in almost real-time,

the presence of a possible large number of students in

a lecture room. When attendance is mandatory for

taking exams such a system can improve the lecture

workﬂow by removing the need of collecting signa-

tures, writing codes/passwords on the blackboard for

students detections, etc. Furthermore, the same archi-

tecture can be applied in every scenario that requires

a veriﬁed list of attendees, for example in the case of

meetings in which it is mandatory to generate on-the-

ﬂy reports.

A prototype of the DidUp system has been deve-

loped using the Node.js

server-side technology and

Android for dedicated mobile app interfaces. The in-

ternal structure of Node.js allows, as required in Di-

dUp, to handle a large number of connections in a

short period of time (Düüna, 2016). Furthermore, An-

droid OS provides natively support for beacons, for

secure network connectivity, and for protecting device

resources. In our system, private data are exposed to

the server only after obtaining permissions from the

users. The system has been tested in real setting in

the context in two courses of the Computer Science

Bachelor degree with more than 120 students over-

all. In this paper, we present the DidUp system requi-

rements, design principles, implementation choices,

and a preliminary user experience evaluation of the

DidUp system.

Organization

The paper is organized as follows. In Section 2

and 3 we discuss the system requirements of the Di-

dUp platform and its infrastructure, respectively. In

Section 4 we brieﬂy present the data model which

constitutes the back-end of the components of the

platform architecture, described in Section 5. In

https://nodejs.org/

Section 6 we report the related work, while in Section

7 we discuss some results of a preliminary evaluation

and address future research directions.

2 SYSTEM AND

INFRASTRUCTURE

REQUIREMENTS

The DidUp platform is based on a combination of har-

dware and software solutions that must be deployed

in physical spaces like lecture and meeting rooms in

an academic campus. The infrastructure and system

requirements can be summarized as follows.

1. The system should provide precise indoor locali-

zation of users via their smartphones. The requi-

red precision must be in the order of a few meters

(i.e., to cover a lecture room).

2. Registration of student attendance must be done

in real-time. The DidUp server must be reachable

from every lecture room.

3. Classrooms must be viewed as geofences. Only

students inside a classroom should be able to re-

gister their attendance at the lecture taking place

in there.

4. The DidUp server must be available during ofﬁce

hours.

5. The app and Web user interfaces must be acces-

sible to non expert users and must provide an on-

line help menu.

6. The system should be resistant to server failures,

e.g., by using multiple server instances on diffe-

rent machines.

7. Logged data must be stored persistently in a data

storage system. Data storage must be accessible

to the DidUp application and administrators, only.

8. Users must be informed that the server makes use

of localization data.

9. Users must give their permission for releasing

data stored in the device (IMEI).

10. Data stored in the DidUp server should not be re-

leased to third parties.

11. Students (and staff members) must be uniquely

identiﬁed via ofﬁcial credentials such as the ma-

triculation (staff) number assigned by the central

administration.

12. Students and staff devices must be identiﬁed uni-

quely using IMEIs. Every student (staff member)

must associate a unique device (IMEI) to the cor-

responding personal identiﬁer.

WEBIST 2018 - 14th International Conference on Web Information Systems and Technologies

278

Figure 1: DidUp System Architecture.

13. Data exchanged with the users must be encrypted

and sent on secure channels.

14. To limit the budget, hardware and software infra-

structures must be composed by low cost devices,

standard networking services provided in acade-

mic environments (e.g. server on virtual machi-

nes), open-source software and development fra-

meworks for server-side and mobile applications.

To meet all the above requirements, we need to satisfy

constraints at the physical (infrastructure and har-

dware), communication (networking), and software

level (platform), as discussed in the following secti-

ons.

3 PHYSICAL AND HARDWARE

ARCHITECTURE

The DidUp Physical Web system is based on the com-

bination of beacons and wi-ﬁ network technology.

Our operative scenario is a typical example of an Aca-

demic Campus (see Figure 1) and we assume that

each classroom is equipped with at least one beacon

conﬁgured with a unique identiﬁer consisting of three

subﬁelds called UUID, MajorID, and MinorID.

In our experimental setup we adopted Estimote

beacons

. For lecture rooms for at most 180 students,

as illustrated in Figure 2, a ﬁx beacon turned out to

be sufﬁcient to detect all enabled smartphones. As an

alternative to the use of hardware devices, it would

http://www.estimote.com/Beacons

also be possible to use smartphone apps that simu-

late beacons and that could be activated by the in-

structor at the beginning of the lecture. We also as-

sume that teacher ofﬁces are equipped with beacons

to inform students of their presence in the building

and their ofﬁce-hour updates. Finally, we assume that

each room provides wi-ﬁ access to students, e.g., via

Eduroam

access points. A (Web) server must be in-

stalled either on an external cloud provider or on a

local server. In both cases it must be reachable from

the local network, i.e., the ﬁrewall conﬁguration must

provide access to the Web APIs needed by the DidUp

smartphone and Web applications.

4 CONCEPTUAL MODEL OF

THE DATA

In this section we describe the data model adopted in

the system. We ﬁrst illustrate some key ideas with

the help of an example involving, for simplicity, only

lessons attendance of students.

Assume that Alice Smith is enrolled in the ﬁrst

year of a Computer Science Bachelor degree. Alice

has student ID 3471890 and the association between

her identiﬁer and the IMEI of her smartphone (and of

other two students) is shown in Table 1.

The semester lecture schedule has two slots per

day, namely 9-11 and 11-13 AM. We assume that the

study plan of the ﬁrst semester is given as shown in

Table 2.

https://www.eduroam.org/

Physical Web for Smart Campus Management

279

Figure 2: Lecture rooms planimetry (beacons were placed near the teacher’s desks).

Table 1: Association between student ID and IMEI.

Matricula IMEI

3471890 980000832471652

3471891 990000551621881

3471895 990000144425624

Table 2: Semester Lecture Plan.

9-11 11-13

Mon CS1 (room 1) CS2 (room 1)

Tue CS3 (room 1) Lab1 (room 2)

Wed CS1 (room 1) Lab1 (room 2)

Thu CS3 (room 1) Lab2 (room 2)

Fri CS2 (room 1) Lab2 (room 2)

Table 3: Association between rooms and beacons.

Physical space beaconID

room 1 101

room 2 102

The association between beacons identiﬁers and

rooms is shown in Table 3. We now come to the re-

quirements needed by the registration protocol. At-

tendance registration for Alice Smith is enabled twice

every day and synchronized in accordance to the data

in Table 2 and Table 3.

Timing is based on the server time in order to

avoid manipulation of timestamps sent with user re-

quests. As an example, in the 9-11 Monday slot the

app installed on Alice smartphone scans the BLE net-

work for beacon signal 101. If detected, it opens a

connection with the DidUp server and, via the app

user interface (a button), it provides the user a bridge

to register attendance at the current CS1 lecture. In

the 11-13 slot the same app starts searching for sig-

nal 102. Registration is disabled for the rest of the

day and enabled again on Tuesday in the 9-11 slot for

signal 101, this time associated to a lecture of course

CS3, and so on.

Based on the above considerations, the data model

of DidUp consists of the conceptual schema in Figure

3 (note that for the sake of readability, we show a sim-

pliﬁed version of the ER schema including, for each

table, only the most relevant information and focusing

on the part of DidUp monitoring the students lecture

attendance).

The USERS table contains data of students (and

staff members) and associations with passwords (sto-

red in hash form) and IMEIs. The COURSES table

contains code, title, and year. CREDENTIALS associ-

ates login and password for accessing course data.

LECTURES speciﬁes records for each lecture (date,

start, end). ATTENDANCES contains logs of individual

lecture attendance (date and hours). LECTURE_ROOMS

reports the name and size of each room available for

the lecture and it size. BEACONS lists all the available

beacons and associates each of them with a room.

5 SOFTWARE PLATFORM

ARCHITECTURE

The DidUp software platform consists of an app with

different views depending from the current user (e.g.,

WEBIST 2018 - 14th International Conference on Web Information Systems and Technologies

280

Figure 3: Conceptual Model of the Data (simpliﬁed fragment: teachers related part is not reported).

students, teacher, administrator), a Web application,

and a persistency server as described in the next secti-

ons.

DidUp and Persistency Server

The DidUp server provides secure APIs (secure TCP)

for accepting user requests and for sending notiﬁcati-

ons. Persistent data are stored in a MySQL server da-

tabase accessible only from the server. For the model

of persistent data see the fragment shown in Figure 3.

Web Application

The Web application allows staff members to create

and modify user proﬁles, visualize historical data and

statistics for both classrooms and individual students.

Although responsive, this functionality must be vie-

wed as an access point designed for a traditional (non

mobile) browser.

Middleware

The middleware underlying the DidUp platform has

been implemented combining different technologies.

The server has been implemented using the Node.js

IoT framework, an efﬁcient server-side development

framework based on JavaScript and on the npm

eco-

system. Node.js provides very efﬁcient packages for

handling secure TCP connections, Web servers, and

https://www.npmjs.com/

applications. Node.js server-side libraries are opti-

mized for network intensive applications even when

executed on single host or cluster.

Indeed, Node.js allows to handle a large number

of connections in a short period of time reducing po-

tential risks of denial of service (this is very useful

in our context since DidUp has to handle hundreds of

requests in a few minutes). This property is due to

the internal structure of the Node.js event-driven en-

gine. Requests are not handled using multiple threads

as in the Apache server model since the Node.js en-

gine is based on an event loop that executes callbacks

sequentially. Callbacks are picked from multiple pri-

orities FIFO queues. Furthermore, thread pool imple-

mented using the C++ libuv

concurrency library sup-

ports the execution of asynchronous callbacks. Dif-

ferently from server architectures based on multiple

threads, in Node.js the response to connection reque-

sts requires few system resources since they basically

require the emission of events whose synchronous ef-

fect is that of enqueuing callback invocations in the

I/O queue. This choice mitigates the risk of classical

denial of service attacks based on a high number of

simultaneous requests that could congest the server

by exhausting system resources (Düüna, 2016) (e.g.

creation of new threads to scale up the server).

DidUp App

The DidUp prototypes of the mobile applications

have been developed in the Android OS. Android OS

https://github.com/libuv/libuv

Physical Web for Smart Campus Management

281

Figure 4: Student App: Mockup.

provides native support for beacons (e.g. using OS

notiﬁcation management or beacon SDKs like Esti-

mote SDK). It also provides secure network connecti-

ons and access control policy management that pro-

tects private data. Private data are exposed to the ser-

ver only after obtaining permissions from the owner.

The authentication mechanism built on top of asso-

ciations between user and device identiﬁer relies on

secure network connections (secure TCP sockets) be-

tween the smartphone application and the DidUp ser-

ver. A smartphone app, conﬁgured to detect beacons

using libraries like the Estimote SDK

, is provided in

two different versions: students and teachers.

The student app provides sign-up, sign-in, and

sign-out and a wide range of functionalities. Figure

4 illustrates mock-ups of the app: home activity (at-

tendance is indicated via the pen icon), and the ca-

lendar activity (with different colors to indicate lec-

tures and other events). The sign-up service associ-

ates the smartphone IMEI to the unique student en-

rollment number and to his contact details. After the

ﬁrst user registration, sign-in is automatically enabled

whenever the app is activated by the user. Indeed, the

server can retrieve the IMEI of the smartphone from

the initial connection request issued by the app. Thus,

the silent authentication stage is based on the asso-

ciation between the user identiﬁer and the registered

IMEI. Upon authentication, students can register their

attendance to a given lecture in a given time-slot. The

lectures schedule of each student is indeed synchroni-

zed, server-side, with the lectures and rooms alloca-

tions plan, for each enrollment year. Thanks to this

synchronization, attendance is enabled only in speci-

https://estimote.com/

ﬁc time-slots and in physical spaces. In addition the

app provides user interfaces for visualizing the histo-

rical data stored in the DidUp persistence server (pro-

ﬁle, attendance log) and interfaces to visualize, via a

calendar widget, lecture plans (according to the corre-

sponding study plan), seminars, and other events re-

gistered by staff members.

Using protocols similar to those adopted for the

student view, the teacher app provides a user interface

for visualizing statistics on students attendance, lec-

tures and events calendar. The aggregated number of

presences provides indications for each course trend:

it is indeed possible to understand if the number of

students attending at the beginning of the course de-

creases signiﬁcantly or remains stable during the se-

mester. It is also possible to check if there are days

or time-slots with a signiﬁcant decrease in attendance

and consequently try to implement strategies to avoid

such drop out. The app also provides a control widget

for the notiﬁcation of presence in ofﬁce-hours. Staff

members can create, modify, and delete events that

will be notiﬁed to users and visualized in their calen-

dar view. Furthermore, they can access the room allo-

cation service that is moderated by a dedicated admi-

nistrator.

6 RELATED WORK

In this section we discuss other examples of beacon-

enabled applications and compare them with our pro-

ject proposal. In general bluetooth-based beacons

make mobile devices aware of the surrounding envi-

ronment (Gast, 2014; Statler, 2016; Jeon et al., 2018).

WEBIST 2018 - 14th International Conference on Web Information Systems and Technologies

282

This technology enables a wide spectrum of applica-

tions such as cell-based localization enabled by intel-

ligent placement or proximity-aware systems for the

interaction with nearby objects. As an example, (Ito

et al., 2015) presents a tour and navigation system ba-

sed on proximity detection. The system provides the

tourists time table of nearby bus stop and distance to

nearby subway stations. (Ng et al., 2017) describes an

interactive system for art galleries, which outperfor-

med the conventional QR code’s engagement conver-

sion rate and time. Estimote has implemented a BLE-

beacon based system in a museum to provide detailed

information about an artwork to nearby users (Ander-

son, 2017). The system employs a pull mechanism,

where the information is provided on request. The

work in (Kang, 2017) is based instead on an infra-

structure based on around 1000 beacon nodes across

Hong Kong for push promotion and location adverti-

sing. Apple has implemented proximity based servi-

ces such as AirDrop to allow iOS devices to connect

to other devices in their vicinity. (Thomson, 2014)

describes applications of iBeacons on a car for auto-

matic transaction at toll booths, parking meters, gas

station and more. BLE beacons have been mainly

used to detect ﬁne-grained location and movement to

better identify the activity of the users with help of

gesture detection technology of smart wearable devi-

ces. Knowing the user’s micro-location helps to nar-

row down the list of possible gestures/actions users

may take. Other applications to indoor localization

can be found in (Huh and Seo, 2017; Zhu et al., 2012;

Kaulich et al., 2017; Mackey and Spachos, 2017; He

et al., 2017). (Kashimoto et al., 2017) presents a

system that collects data of elder people. The sy-

stem is based on wearable BLE beacon tags equipped

with accelerometer. BLE beacon signals scanned by

pre-deployed ﬁxed scanners helps to identify micro-

location of the user. Data coming from the accele-

rometer helps to identify the type of activities of the

subjects under monitoring. Beacons are often used in

combination with mobile crowd sensing technology.

The main goal of these works is to replace expen-

sive sensors on vehicles and street infrastructures with

mobile crowd-sourcing that still enable safe driving

experiences and awareness of car accidents and traf-

ﬁc information. (Cianciulli et al., 2017) described a

distributed infrastructure for measuring trafﬁc conge-

stion, road conditions, parking availability, outages of

public works and for real-time transit tracking. Ex-

amples of mobile crowd sensing applied to transpor-

tation can be found e.g. in (Chen et al., 2012; Sato

et al., 2017). Beacons as technology support for im-

proving the usage of physical spaces is discussed in

(Purta and Striegel, 2017). Although the system ar-

chitecture layer of our systems has common features

with the above mentioned beacon-enabled solutions,

we believe that our work has at least two main no-

velties: a new application domain and a novel com-

bination of beacon and mobile device technology via

Node.js.

7 CONCLUSIONS AND FUTURE

WORK

The DidUp system is currently in alpha testing in

some of the undergraduate courses of the Bachelor

in Computer Science at the University of Genova. In

particular, it has been adopted in the Computer Archi-

tecture and Database courses (respectively ﬁrst and

second year of the bachelor). Subscription was on

voluntary basis since, as an alternative modality, stu-

dents could still certify their presence to lectures by

signing attendance sheets. As a result of this pre-

liminary evaluation the service has been subscribed

by 25% of the students. This is also due to the fact

that part of the students refused to install the smartp-

hone application mainly for privacy issues. We plan

to improve the system, e.g., by providing a cross-

platform Web-app and integrating other functionali-

ties for improving the user experience and incentivate

the adoption of the Physical Web app for attendance

registration. We plan to extensively test the system in

the academic year 2018/19 and to improve its quality

by employing end-to-end automated testing solutions

(Leotta et al., 2018b) and runtime veriﬁcation techni-

ques (Leotta et al., 2018a). Moreover, we plan to furt-

her extend our prototype to include also iOS devices

in order to cover, virtually, the 100% of the students

(note that no changes are required to the Node.js ser-

ver). We also plan to improve data exploitation and

integration with student/course data provided by our

University. The resulting IoT framework is currently

under evaluation as a possible physical infrastructure

for access control based on a new speciﬁcation lan-

guage for location- and time-based RBAC policies

(Delzanno and Guerrini, 2018) that can be automati-

cally compiled into a set of permission rules that can

be checked dynamically with an extension of the Di-

dUp system.

There are many other interesting directions rela-

ted to emerging beacon technologies like battery-free

beacons (Wiliot, 2018), video estimote (Estimote,

2018), etc. In particular battery-free beacons could

open new opportunities related to physical identiﬁca-

tion and authentication of users (e.g. attach beacons

to badges, etc). Interactions with video estimote is

also very promising since it can transfer personaliza-

Physical Web for Smart Campus Management

283

tion through user proﬁling, a typical feature of Web

Applications, to the Physical Web. For example, a

student wearing a passive beacon could receive per-

sonalized multimedia notiﬁcations in proximity of an

information screen.

ACKNOWLEDGMENTS

The authors would like to thank Claudio Orlando for

the prototype implementation of DidUp and Steve

Statler for interesting discussion on beacons techno-

logy.

REFERENCES

Anderson, J. (2017). The icon of modern art

puts estimote beacons on display. Available:

https://blog.estimote.com/post/157200820650/the-

icon-of-modern-art-puts-estimote-beacons-on.

Chen, X., Santos-Neto, E., and Ripeanu, M. (2012). Crowd-

sourcing for on-street smart parking. In Proceedings

of the 2nd ACM International Symposium on Design

and Analysis of Intelligent Vehicular Networks and

Applications, DIVANet 2012, pages 1–8, New York,

NY, USA. ACM.

Cianciulli, D., Canfora, G., and Zimeo, E. (2017). Beacon-

based context-aware architecture for crowd sensing

public transportation scheduling and user habits. Pro-

cedia Computer Science, 109:1110 – 1115.

Delzanno, G. and Guerrini, G. (2018). An IoT framework

for context-aware role based access control. In Proc.

of the 26th Italian Symp. on Advanced Database Sys-

tems, SEBD 2018.

Düüna, K. (2016). Secure Your Node.js Web Application:

Keep Attackers Out and Users Happy. The Pragmatic

Bookshelf.

Estimote (2018). https://estimote.com.

Gast, M. (2014). Building applications with IBeacon: prox-

imity and location services with bluetooth low energy.

O’Reilly.

He, W., Ho, P. H., and Tapolcai, J. (2017). Beacon deploy-

ment for unambiguous positioning. IEEE Internet of

Things Journal, 4(5):1370–1379.

Huh, J.-H. and Seo, K. (2017). An indoor location-based

control system using bluetooth beacons for IoT sys-

tems. Sensors, 17(12):2917.

Ito, A., Hatano, H., Fujii, M., Sato, M., Watanabe, Y., Hira-

matsu, Y., Sato, F., and Sasaki, A. (2015). A trial of

navigation system using ble beacon for sightseeing in

traditional area of Nikko. In Proceedings of IEEE In-

ternational Conference on Vehicular Electronics and

Safety, ICVES 2015, pages 170–175.

Jeon, K. E., She, J., Soonsawad, P., and Ng, P. C. (2018).

BLE beacons for internet of things applications: Sur-

vey, challenges, and opportunities. IEEE Internet of

Things Journal, 5(2):811–828.

Kang, S. C. (2017). Apple daily launches in-

app, beacon-based targeting. Available:

http://www.campaignasia.com/article/apple-daily-

launches-in-app-beacon-based-targeting/441080.

Kashimoto, Y., Morita, T., Fujimoto, M., Arakawa, Y.,

Suwa, H., and Yasumoto, K. (2017). Sensing acti-

vities and locations of senior citizens toward automa-

tic daycare report generation. In Proceedings of 31st

IEEE International Conference on Advanced Informa-

tion Networking and Applications, AINA 2017, pages

174–181.

Kaulich, T., Heine, T., and Kirsch, A. (2017). Indoor loca-

lisation with beacons for a user-friendly mobile tour

guide. KI - Künstliche Intelligenz - German Journal

on Artiﬁcial Intelligence, 31(3):239–248.

Leotta, M., Ancona, D., Franceschini, L., Olianas, D., Ri-

baudo, M., and Ricca, F. (2018a). Towards a runtime

veriﬁcation approach for Internet of Things systems.

In Proceedings of 2nd International Workshop on En-

gineering the Web of Things (EnWoT 2018), LNCS.

Springer.

Leotta, M., Clerissi, D., Olianas, D., Ricca, F., Ancona,

D., Delzanno, G., Franceschini, L., and Ribaudo, M.

(2018b). An acceptance testing approach for Internet

of Things systems. IET Software.

Mackey, A. and Spachos, P. (2017). Performance evaluation

of beacons for indoor localization in smart buildings.

In Proceedings of the 5th IEEE Global Conference on

Signal and Information Processing, GlobalSIP 2017,

pages 823–827.

Ng, P. C., She, J., and Park, S. (2017). Notify-and-interact:

A beacon-smartphone interaction for user engagement

in galleries. In Proceedings of IEEE International

Conference on Multimedia and Expo, ICME 2017, pa-

ges 1069–1074.

Purta, R. and Striegel, A. (2017). Estimating dining hall

usage using bluetooth low energy beacons. In Pro-

ceedings of the 2017 ACM International Joint Con-

ference on Pervasive and Ubiquitous Computing and

Proceedings of the 2017 ACM International Sympo-

sium on Wearable Computers, UbiComp 2017, pages

518–523.

Sato, G., Hirakawa, G., and Shibata, Y. (2017). Push typed

tourist information system based on beacon and au-

gumented reality technologies. In Proceedings of the

31st IEEE International Conference on Advanced In-

formation Networking and Applications, AINA 2017,

pages 298–303.

Statler, S. (2016). Beacon Technologies: The Hitchhiker’s

Guide to the Beacosystem. Apress.

Thomson, D. (2014). ibeacon auto: Your car is a beacon.

Available: http://beekn.net/2014/02/ibeacon-auto/.

Wiliot (2018). https://www.wiliot.com.

Zhu, J., Zeng, K., Kim, K. H., and Mohapatra, P. (2012).

Improving crowd-sourced Wi-Fi localization systems

using Bluetooth beacons. In Proc. of the 9th Annual

IEEE Communications Society Conference on Sensor,

Mesh and Ad Hoc Communications and Networks, pa-

ges 290–298.

WEBIST 2018 - 14th International Conference on Web Information Systems and Technologies

284