• Renew the Ticket. When pay and display ma-
chines are used, if the ticket expires drivers must
go back to the machine, buy a new ticket and leave
it in the car. Thisis a very inconvenientprocedure,
specially if the driver is far fromthe parkingplace.
In the context of a smart city we assume that a
number of RFID readers are deployed so as to iden-
tify vehicles and control their payment status. Thus,
in addition to the previously stated problems,we iden-
tify some attacks against the privacy of the users that
can take place and should be avoided:
• Attacks from the Infrastructure. Some of the cur-
rent parking systems use contactless technology,
but in most cases users use an ID. If vehicles are
identified with a single ID (e.g. the licence plate,
or the like), the infrastructure can obtain a record
of the locations that a given driver visits and can
obtain extra-information that might endanger the
privacy of drivers, namely their habits, their place
of residence, their place of work, etc.
• Attacks from External Attackers. If RFID tech-
nology is used inappropriately, external attackers
could obtain the identification of the vehicle and
clone it so as to avoid payment by stealing the
identity of legitimate users.
In our case study we consider all these problems
related to both the payment and identification of the
vehicles. We do not consider the problem of find-
ing a parking place because it has been widely stud-
ied and several solutions already exist (Lee et al.,
2008). Thus, to address the aforementioned problems
we need to design a procedure (or a set of protocols)
that guaranties the following properties.
• Anonymity. Payments should be anonymous so as
to avoid the identification of the user by the infras-
tructure and avoid undesired profiling.
• Remote payment. Payments might be done re-
motely, this is, without the need for change and
without the need for going back to the vehicle or
the parking meter.
• Transparent Multi-area Parking. If users have
paid for a given parking time and they change the
location of their vehicle, they should be allowed
to use the remaining time that they have (if any)
in the new parking place.
• Untraceability. External attackers and the infras-
tructure should not be able to distinguish two dif-
ferent payments from the same user. Thus, they
cannot infer the habits or the places frequently
visited by users.
3 PROTOCOL
In this section we describe our protocol, which uses
off-the-shelf privacy enhancing technologies to ad-
dress the problems identified in the previous section.
We assume that users/drivers have an RFID card and
a mobile phone that can communicate with this card.
First, we describe the procedure to anonymously pay
by means of e-cash. Then we describe how to use our
protocol within the context of a smart city.
3.1 Anonymous Payment
With the aim to break the link between the identity of
the user and the payment he/she makes, we propose
the use of anonymous e-cash. To obtain e-cash and
proceed with the payment, users operate as follows:
1. Get e-cash. A user U
1
gets e-cash (electronic
cash) from a bank. To do so, one can use a lot
of existing protocols, for example the system pro-
posed in the patent (Simon, 1995), in which a user
asks to the bank for a given amount of money in
the form of electronic cash. To do that, the user
sends a request for some quantity of e-cash to the
bank, and the bank sends back to the user the e-
cash with the requested value. In this procedure
the bank signs the money so as to guaranty its va-
lidity. By using this procedure, double spending
is averted by the bank.
2. Pay for the Service. When U
1
parks a vehicle
in a public parking area that requires payment,
he uses the previously obtained e-cash to pay the
service by using a mobile phone (cf. Figure 1).
To proceed, the user sends an activation message
to the RFID tag located in the vehicle
1
. When
the tag receives the activation message it gener-
ates a pseudonym using a one-way hash function
h(ID
1
||r), where ID
1
is the private identifier of the
tag, r is a random number generated by the tag,
and (||) is the concatenation operator. Then, the
tag sends the pseudonym back to the driver, who
will use it to make the payment.
3. Verify the Payment. Once the service provider
receivesthe payment, it contacts the bank to check
the validity of the e-cash. If the e-cash received
is valid the bank sends the money to the parking
service provider (cf. Figure 2).
4. Determine and Store Expiration Time. The
parking service provider converts the e-cash re-
1
This communication can be performed in a variety of
ways, but the use of NFC is becoming popular and might be
the standard in the near future.
PrivacyinSmartCities-ACaseStudyofSmartPublicParking
57