<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE ep-patent-document PUBLIC "-//EPO//EP PATENT DOCUMENT 1.5//EN" "ep-patent-document-v1-5.dtd">
<ep-patent-document id="EP15172118A1" file="EP15172118NWA1.xml" lang="en" country="EP" doc-number="3107073" kind="A1" date-publ="20161221" status="n" dtd-version="ep-patent-document-v1-5">
<SDOBI lang="en"><B000><eptags><B001EP>ATBECHDEDKESFRGBGRITLILUNLSEMCPTIESILTLVFIROMKCYALTRBGCZEEHUPLSKBAHRIS..MTNORSMESMMA................</B001EP><B005EP>J</B005EP><B007EP>JDIM360 Ver 1.28 (29 Oct 2014) -  1100000/0</B007EP></eptags></B000><B100><B110>3107073</B110><B120><B121>EUROPEAN PATENT APPLICATION</B121></B120><B130>A1</B130><B140><date>20161221</date></B140><B190>EP</B190></B100><B200><B210>15172118.0</B210><B220><date>20150615</date></B220><B250>en</B250><B251EP>en</B251EP><B260>en</B260></B200><B400><B405><date>20161221</date><bnum>201651</bnum></B405><B430><date>20161221</date><bnum>201651</bnum></B430></B400><B500><B510EP><classification-ipcr sequence="1"><text>G07C   9/00        20060101AFI20151126BHEP        </text></classification-ipcr></B510EP><B540><B541>de</B541><B542>ANNULLIERUNG EINES ELEKTRONISCHEN SCHLÜSSELS</B542><B541>en</B541><B542>INVALIDATION OF AN ELECTRONIC KEY</B542><B541>fr</B541><B542>INVALIDATION D'UNE CLÉ ÉLECTRONIQUE</B542></B540><B590><B598>2</B598></B590></B500><B700><B710><B711><snm>Assa Abloy AB</snm><iid>101503024</iid><irf>15162EP</irf><adr><str>P.O. Box 70340</str><city>107 23 Stockholm</city><ctry>SE</ctry></adr></B711></B710><B720><B721><snm>Strömberg, Stefan</snm><adr><str>Sankt Göransgatan 98</str><city>112 45 Stockholm</city><ctry>SE</ctry></adr></B721><B721><snm>Gärde, Johan</snm><adr><str>Sofiebergsvägen 12</str><city>135 53 Tyresö</city><ctry>SE</ctry></adr></B721></B720><B740><B741><snm>Kransell &amp; Wennborg KB</snm><iid>101410948</iid><adr><str>P.O. Box 27834</str><city>115 93 Stockholm</city><ctry>SE</ctry></adr></B741></B740></B700><B800><B840><ctry>AL</ctry><ctry>AT</ctry><ctry>BE</ctry><ctry>BG</ctry><ctry>CH</ctry><ctry>CY</ctry><ctry>CZ</ctry><ctry>DE</ctry><ctry>DK</ctry><ctry>EE</ctry><ctry>ES</ctry><ctry>FI</ctry><ctry>FR</ctry><ctry>GB</ctry><ctry>GR</ctry><ctry>HR</ctry><ctry>HU</ctry><ctry>IE</ctry><ctry>IS</ctry><ctry>IT</ctry><ctry>LI</ctry><ctry>LT</ctry><ctry>LU</ctry><ctry>LV</ctry><ctry>MC</ctry><ctry>MK</ctry><ctry>MT</ctry><ctry>NL</ctry><ctry>NO</ctry><ctry>PL</ctry><ctry>PT</ctry><ctry>RO</ctry><ctry>RS</ctry><ctry>SE</ctry><ctry>SI</ctry><ctry>SK</ctry><ctry>SM</ctry><ctry>TR</ctry></B840><B844EP><B845EP><ctry>BA</ctry></B845EP><B845EP><ctry>ME</ctry></B845EP></B844EP><B848EP><B849EP><ctry>MA</ctry></B849EP></B848EP></B800></SDOBI>
<abstract id="abst" lang="en">
<p id="pa01" num="0001">It is provided a method for invalidating an electronic key for access to a physical space. The method is performed in an invalidation device and comprises the steps of: receiving a central invalidation command from a central server, the central invalidation command comprising an identifier of an electronic key; discovering a presence of the electronic key over short range radio; and transmitting a local invalidation command to the electronic key.
<img id="iaf01" file="imgaf001.tif" wi="126" he="114" img-content="drawing" img-format="tif"/></p>
</abstract>
<description id="desc" lang="en"><!-- EPO <DP n="1"> -->
<heading id="h0001"><b>TECHNICAL FIELD</b></heading>
<p id="p0001" num="0001">The invention relates to a method, an invalidation device, a computer program and a computer program product for invalidating an electronic key, e.g. when the key has been reported lost.</p>
<heading id="h0002"><b>BACKGROUND</b></heading>
<p id="p0002" num="0002">Locks and keys are evolving from the traditional pure mechanical locks. These days, there are wireless interfaces for electronic locks, e.g. by interacting with an electronic key. In some installations, to save power and complexity, the electronic locks are offline without communication ability with a central access control system.</p>
<p id="p0003" num="0003">A major issue is when an electronic key is lost. In such a case, an attacker should be prevented to gain access to closed spaces by using the lost electronic key. When the electronic lock is online, the identity of the electronic key can be added to a black list in the central access control system, and the black list can be sent to the electronic lock. In this way, the electronic lock can block entry for any electronic key on the black list, thus stopping an attacker having found or stolen the lost electronic key.</p>
<p id="p0004" num="0004">However, when the electronic lock is offline, there is no natural way to send a black list to the electronic lock.</p>
<heading id="h0003"><b>SUMMARY</b></heading>
<p id="p0005" num="0005">It is an object to provide a way to invalidate an electronic key which lacks ability to directly communicate with a central server.</p>
<p id="p0006" num="0006">According to a first aspect, it is provided a method for invalidating an electronic key for access to a physical space. The method is performed in an invalidation device and comprises the steps of: receiving a central invalidation command from a central server, the central invalidation command comprising an identifier of an electronic key; discovering a<!-- EPO <DP n="2"> --> presence of the electronic key over short range radio; and transmitting a local invalidation command to the electronic key.</p>
<p id="p0007" num="0007">The method may further comprise the steps of: receiving a local confirmation message from the electronic key, the local confirmation message indicating a successful invalidation; and transmitting a central confirmation message to the central server, the central confirmation message indicating a successful invalidation.</p>
<p id="p0008" num="0008">The central confirmation message may comprise an indicator of a position of the invalidation device.</p>
<p id="p0009" num="0009">The central invalidation command may comprise a main command and an integrity indicator.</p>
<p id="p0010" num="0010">The integrity indicator may be derived using the main command and a private electronic key.</p>
<p id="p0011" num="0011">The step of discovering may comprise discovering the presence of the electronic key using Bluetooth low energy, BLE.</p>
<p id="p0012" num="0012">The step of receiving a central invalidation command may comprise receiving the central invalidation command over a wide area network.</p>
<p id="p0013" num="0013">According to a second aspect, it is provided an invalidation device for invalidating an electronic key for access to a physical space. The invalidation device comprises: a processor; and a memory storing instructions that, when executed by the processor, cause the invalidation device to: receive a central invalidation command from a central server, the central invalidation command comprising an identifier of an electronic key; discover a presence of the electronic key over short range radio; and transmit a local invalidation command to the electronic key.</p>
<p id="p0014" num="0014">The invalidation device may further comprise instructions that, when executed by the processor, cause the invalidation device to: receive a local confirmation message from the electronic key, the local confirmation<!-- EPO <DP n="3"> --> message indicating a successful invalidation; and transmit a central confirmation message to the central server, the central confirmation message indicating a successful invalidation.</p>
<p id="p0015" num="0015">The central confirmation message may comprise an indicator of a position of the invalidation device.</p>
<p id="p0016" num="0016">The central invalidation command may comprise a main command and an integrity indicator.</p>
<p id="p0017" num="0017">The invalidation device may form part of a mobile phone.</p>
<p id="p0018" num="0018">The invalidation device may be a device dedicated to the purpose of invalidating electronic keys.</p>
<p id="p0019" num="0019">According to a third aspect, it is provided a computer program for invalidating an electronic key for access to a physical space. The computer program comprises computer program code which, when run on an invalidation device, causes the invalidation device to: receive a central invalidation command from a central server, the central invalidation command comprising an identifier of an electronic key; discover a presence of the electronic key over short range radio; and transmit a local invalidation command to the electronic key.</p>
<p id="p0020" num="0020">According to a fourth aspect, it is provided a computer program product comprising a computer program according to the third aspect and a computer readable means on which the computer program is stored.</p>
<p id="p0021" num="0021">Generally, all terms used in the claims are to be interpreted according to their ordinary meaning in the technical field, unless explicitly defined otherwise herein. All references to "a/an/the element, apparatus, component, means, step, etc." are to be interpreted openly as referring to at least one instance of the element, apparatus, component, means, step, etc., unless explicitly stated otherwise. The steps of any method disclosed herein do not have to be performed in the exact order disclosed, unless explicitly stated.<!-- EPO <DP n="4"> --></p>
<heading id="h0004"><b>BRIEF DESCRIPTION OF THE DRAWINGS</b></heading>
<p id="p0022" num="0022">The invention is now described, by way of example, with reference to the accompanying drawings, in which:
<ul id="ul0001" list-style="none">
<li><figref idref="f0001">Fig 1</figref> is a schematic diagram showing an environment in which embodiments presented herein can be applied;</li>
<li><figref idref="f0001">Fig 2</figref> is a schematic diagram illustrating a situation where a lost electronic key is invalidated using an invalidation device;</li>
<li><figref idref="f0002">Fig 3</figref> is a sequence diagram illustrating communication for invalidation of an electronic key;</li>
<li><figref idref="f0003">Fig 4</figref> is a flow chart illustrating a method for invalidating an electronic key, performed in the invalidation device of <figref idref="f0001">Figs 2</figref> and <figref idref="f0002">3</figref>;</li>
<li><figref idref="f0003">Fig 5</figref> is a schematic diagram illustrating some components of an invalidation device according to <figref idref="f0001">Figs 2</figref> and <figref idref="f0002">3</figref>;</li>
<li><figref idref="f0003">Fig 6</figref> is a schematic diagram illustrating an invalidation device provided as part of a mobile phone; and</li>
<li><figref idref="f0003">Fig 7</figref> shows one example of a computer program product comprising computer readable means.</li>
</ul></p>
<heading id="h0005"><b>DETAILED DESCRIPTION</b></heading>
<p id="p0023" num="0023">The invention will now be described more fully hereinafter with reference to the accompanying drawings, in which certain embodiments of the invention are shown. This invention may, however, be embodied in many different forms and should not be construed as limited to the embodiments set forth herein; rather, these embodiments are provided by way of example so that this disclosure will be thorough and complete, and will fully convey the scope of the invention to those skilled in the art. Like numbers refer to like elements throughout the description.<!-- EPO <DP n="5"> --></p>
<p id="p0024" num="0024"><figref idref="f0001">Fig 1</figref> is a schematic diagram showing an environment in which embodiments presented herein can be applied. Access to a physical space 16 is restricted by a physical barrier 15 which is selectively unlockable. The physical barrier 15 stands between the restricted physical space 16 and an accessible physical space 14. Note that the accessible physical space 14 can be a restricted physical space in itself, but in relation to this physical barrier 15, the accessible physical space 14 is accessible. The barrier 15 can be a door, gate, hatch, window, drawer, etc. In order to unlock the barrier 15, an access control device 13 is provided. The access control device 13 is connected to a physical lock device 12, which is controllable by the access control device 13 to be set in an unlocked state or locked state. In this embodiment, the access control device 13 is mounted close to the physical lock device 12. The barrier 15 is provided in a surrounding fixed structure, such as a wall or fence.</p>
<p id="p0025" num="0025">The access control device 13 is able to receive and send signals from/to an electronic key 2 over a communication channel 3 which may be a short range wireless interface or a conductive (i.e. galvanic/electric) connection. The electronic key 2 is any suitable device portable by a user and which can be used for authentication over the communication channel 3. The electronic key 2 is typically carried or worn by the user and may be implemented as a physical key, a key fob, wearable device, etc. The short range wireless interface is a radio frequency wireless interface and could e.g. be using Bluetooth, Bluetooth Low Energy (BLE), ZigBee, any of the IEEE 802. 11 standards, any of the IEEE 802.15 standards, wireless USB, etc. Using the communication channel 3, the authenticity of the electronic key 2 can be checked, e.g. using a challenge and response scheme, after which the access control device 13 grants or denies access.</p>
<p id="p0026" num="0026">When access is granted, the access control device 13 sends an unlock signal to the lock device 12, whereby the lock device 12 is set in an unlocked state. In this embodiment, this can e.g. imply a signal over a wire-based communication interface, e.g. using Universal Serial Bus (USB), Ethernet, a serial connection (e.g. RS-485 or RS-232) or even a simple electric connection (e.g. to the lock device 12), or alternatively signal over a wireless<!-- EPO <DP n="6"> --> communication interface. When the lock device 12 is in an unlocked state, the barrier 15 can be opened and when the lock device 12 is in a locked state, the barrier 15 cannot be opened. In this way, access to a closed space 16 is controlled by the access control device 13. It is to be noted that the access control device 13 and/or the lock device 12 can be mounted in the fixed structure 16 by the physical barrier 15 (as shown) or in the physical barrier 15 itself (not shown). Optionally, the lock device 12 and access control device 13 are combined in one unit. In one embodiment, the lock device (optionally combined with the access control device) is in the form of a padlock or any other suitable implementation.</p>
<p id="p0027" num="0027">The access control device 13 can be implemented as an offline device, without the ability to directly communicate with a central server of an access control system. In this way, the access control device 13 is easier to implement and uses less power. This allows the access control device 13 to be powered for a long time using a battery or by the electronic key. Optionally, energy harvesting of mechanical user actions and/or environmental power (solar power, wind, etc.) can be utilised to prolong the life span of the battery or event to allow the battery to be omitted.</p>
<p id="p0028" num="0028"><figref idref="f0001">Fig 2</figref> is a schematic diagram illustrating a situation where an electronic key is invalidated using an invalidation device. A central server 10 of the access control system is responsible for managing keys and locks. The central server 10 can be accessed by an operator to thereby perform management tasks in the access control system.</p>
<p id="p0029" num="0029">There is a first invalidation device 1a and a second invalidation device 1b. Each one of the first and second invalidation devices are described in more detail below, and can e.g. be implemented as part of a mobile phone or as a dedicated invalidation device. The invalidation devices 1a-b can communicate with an electronic key for invalidation, as explained below, and optionally also for other purposes.<!-- EPO <DP n="7"> --></p>
<p id="p0030" num="0030">In this example, a user has lost an electronic key 2' or has had the electronic key 2' stolen. The electronic key 2' then needs to be invalidated to prevent an attacker from gaining access to closed physical spaces, otherwise accessible using the lost electronic key 2'. The central server 10 is made aware of the lost electronic key 2', e.g. by an operator indicating that the electronic key 2' is lost. The central server 10 then sends a central invalidation command to all relevant invalidation devices 1a-b as explained more below.</p>
<p id="p0031" num="0031">The second invalidation device 1b is within range 7 to communicate over a short range radio interface 5 with the lost electronic key 2'. This allows the second invalidation device 1b to communicate with the lost electronic key 2'. In this way, the second invalidation device 1b can send a local invalidation command to the electronic key 2'. The range 7 depends on the type of short range radio which can be used and radio conditions in the vicinity of the electronic key 2'. When communication channel 3 of <figref idref="f0001">Fig 1</figref> is wireless, the short range radio interface 5 may be the same as the communication channel 3. However, when the communication channel 3 of <figref idref="f0001">Fig 1</figref> is based on a conductive connection, the short range radio interface 5 is not the same as the communication channel 3. The short range radio interface 5 may optionally be used for other purposes, e.g. other maintenance purposes for the electronic key 2'.</p>
<p id="p0032" num="0032">It is to be noted that the first invalidation device 1a is outside the range 7 of the lost electronic key 2', whereby it is unable to invalidate the lost electronic key 2'</p>
<p id="p0033" num="0033"><figref idref="f0002">Fig 3</figref> is a sequence diagram illustrating communication for invalidation of an electronic key, e.g. in the environment shown in <figref idref="f0001">Fig 2</figref>. The sequence is performed to perform invalidation of an electronic key. Hereinafter, the electronic key to be invalidated is referred to as a lost electronic key. However, there may be other reasons for invalidating the electronic key, e.g. the electronic key being stolen or that an employee has ended employment and whose electronic key needs to be invalidated.<!-- EPO <DP n="8"> --></p>
<p id="p0034" num="0034">Once the central server 10 is made aware of the lost key, the central server 10 sends a central invalidation command 30 to all relevant invalidation devices 1. This can e.g. be all possible invalidation devices or only invalidation devices in a specific area, e.g. within a specific range from a last known location of the lost electronic key 2'.</p>
<p id="p0035" num="0035">An invalidation device 1 detects the presence 31 of the lost electronic key 2' (e.g. as shown for the second invalidation device 1b of <figref idref="f0001">Fig 2</figref>). The invalidation device 1 detects that the identity of the electronic key 2' matches the identity of the central invalidation command 30 and thus proceeds with an invalidation. It is to be noted that when an electronic key is detected which does not have an identity matching any received central invalidation command, the invalidation device 1 does not proceed with the invalidation.</p>
<p id="p0036" num="0036">Once the match is confirmed between the lost electronic key 2' and the central invalidation command 30, the invalidation device 1 transmits a local invalidation command 32 to the lost electronic key 2'. Upon receipt of the local invalidation command 32, the lost electronic key 2' makes itself invalid. Optionally, the electronic key 2' verifies the integrity of the invalidation command (as explained below) prior to performing its invalidation procedure. Optionally, the electronic key 2' sends a local confirmation message 33 to the invalidation device 1. The invalidation device 1 can then send a central confirmation message 34 to the central server 10.</p>
<p id="p0037" num="0037">In this way, the central server 10 can initiate an invalidation using all relevant invalidation devices and can optionally be informed of when the invalidation has been successful. Using this method, the lost electronic key 2' can be invalidated even though it has no direct communication link with the central server 10.</p>
<p id="p0038" num="0038"><figref idref="f0003">Fig 4</figref> is a flow chart illustrating a method for invalidating an electronic key for access to a physical space. The method is performed in the invalidation device of <figref idref="f0001">Figs 2</figref> and <figref idref="f0002">3</figref>. The method corresponds to the actions of the invalidation device 1 in <figref idref="f0002">Fig 3</figref>.<!-- EPO <DP n="9"> --></p>
<p id="p0039" num="0039">In a <i>receive central invalidation command</i> step 40, a central invalidation command is received from the central server. The central invalidation command comprises an identifier of the electronic key to be invalidated, e.g. of a lost electronic key. The central invalidation command can e.g. be received over a wide area network, such as the Internet.</p>
<p id="p0040" num="0040">Furthermore, the central invalidation command can comprise a main command and an integrity indicator. The integrity can e.g. be derived using the main command and a private electronic key, e.g. using a cryptographic hash function such as SHA-2 (Secure Hash Algorithm 2) or MD-5 (Message Digest algorithm 5).</p>
<p id="p0041" num="0041">In a <i>discover presence</i> step 42, a presence of the electronic key to be invalidated is discovered over short range radio. This can e.g. be performed by discovering the presence of the electronic key using BLE. Any other short range radio technology is equally applicable.</p>
<p id="p0042" num="0042">In a <i>transmit local invalidation command</i> step 44, a local invalidation command is transmitted to the electronic key to be invalidated. The main command and the integrity indicator of the central invalidation command can form part of the local invalidation command. This allows the electronic key to verify the source of the invalidation, i.e. from the central server. In this way, third parties are prevented from invalidating keys.</p>
<p id="p0043" num="0043">Optionally, the content of the central invalidation command 30 and the local invalidation command 32 is the same. For instance, both can contain an invalidation package which can be encrypted and/or signed for the lost electronic key 2', i.e. using an integrity indicator. This allows the lost electronic key 2' to validate authenticity of the local invalidation command. In such a case, the locating device 1 routes the invalidation package to the lost key 2' and does not (or cannot) examine the contents of the invalidation package.<!-- EPO <DP n="10"> --></p>
<p id="p0044" num="0044">In a <i>receive local confirmation message</i> step 46, a local confirmation message is received from the electronic key to be invalidated. The local confirmation message indicates a successful invalidation.</p>
<p id="p0045" num="0045">In a <i>transmit central confirmation message</i> step 48, a central confirmation message is transmitted to the central server. The central confirmation message indicates a successful invalidation. Optionally, the central confirmation message comprises an indicator of a position (e.g. in form of a longitude and a latitude) of the invalidation device, e.g. obtained using GPS (Global Positioning System) or any other suitable positioning technology. Also, the central confirmation message can comprise an estimated distance (e.g. in metres) to the electronic key from the position of the invalidation device. The distance can be estimated using any suitable method. For instance, the distance can be estimated by measuring received signal strength (i.e. using a received signal strength indicator) and comparing this to transmission power. More specifically, an indicator of the transmission power which is used can be transmitted as part of the message. The receiver can then compare the received signal strength with the power used to transmit it and can thus estimate the distance based on the attenuation of the signal. Alternatively, two-way ranging can be used, measuring the time it takes to transmit a signal and receive its response, which gives a distance indication when divided by two multiplied by the speed of light. The position and optional estimated distance simplifies the retrieval of the electronic key to be able to reprogram and reuse the lost electronic key.</p>
<p id="p0046" num="0046"><figref idref="f0003">Fig 5</figref> is a schematic diagram showing some components of the invalidation device of <figref idref="f0001">Figs 2</figref> and <figref idref="f0002">3</figref>. A processor 60 is provided using any combination of one or more of a suitable central processing unit (CPU), multiprocessor, microcontroller, digital signal processor (DSP), application specific integrated circuit etc., capable of executing software instructions 66 stored in a memory 64, which can thus be a computer program product. The processor 60 can be configured to execute the method described with reference to <figref idref="f0003">Fig 4</figref> above.<!-- EPO <DP n="11"> --></p>
<p id="p0047" num="0047">The memory 64 can be any combination of read and write memory (RAM) and read only memory (ROM). The memory 64 also comprises persistent storage, which, for example, can be any single one or combination of magnetic memory, optical memory, solid state memory or even remotely mounted memory.</p>
<p id="p0048" num="0048">A data memory 66 is also provided for reading and/or storing data during execution of software instructions in the processor 60. The data memory 66 can be any combination of read and write memory (RAM) and read only memory (ROM).</p>
<p id="p0049" num="0049">The invalidation device 1 further comprises an I/O interface 67 for communicating with other external entities. Optionally, the I/O interface 67 also includes a user interface.</p>
<p id="p0050" num="0050">Other components of the invalidation device 1 are omitted in order not to obscure the concepts presented herein.</p>
<p id="p0051" num="0051"><figref idref="f0003">Fig 6</figref> is a schematic diagram illustrating an invalidation device 1 provided as part of a mobile phone 4. In such a case, components of the mobile phone 4 can be utilised also by the invalidation device 1.</p>
<p id="p0052" num="0052">In another embodiment, the invalidation device 1 is a device dedicated to the purpose of invalidating electronic keys. In such a case, the dedicated invalidation device 1 can be placed in a location where there is a large chance of discovering a lost electronic key. For instance, the dedicated invalidation device can be placed by the entrance of a building or by a public transport gateway (e.g. underground turnstiles). The dedicated invalidation device 1 does not need to be portable and can thus be connected to a power socket and wireless and/or wire based communication links for communication with the central server. In this way, the dedicated invalidation device 1 can be continuously active.</p>
<p id="p0053" num="0053"><figref idref="f0003">Fig 7</figref> shows one example of a computer program product comprising computer readable means. On this computer readable means a computer<!-- EPO <DP n="12"> --> program 91 can be stored, which computer program can cause a processor to execute a method according to embodiments described herein. In this example, the computer program product is an optical disc, such as a CD (compact disc) or a DVD (digital versatile disc) or a Blu-Ray disc. As explained above, the computer program product could also be embodied in a memory of a device, such as the computer program product 64 of <figref idref="f0003">Fig 5</figref>. While the computer program 91 is here schematically shown as a track on the depicted optical disk, the computer program can be stored in any way which is suitable for the computer program product, such as a removable solid state memory, e.g. a Universal Serial Bus (USB) drive.</p>
<p id="p0054" num="0054">The invention has mainly been described above with reference to a few embodiments. However, as is readily appreciated by a person skilled in the art, other embodiments than the ones disclosed above are equally possible within the scope of the invention, as defined by the appended patent claims.</p>
</description>
<claims id="claims01" lang="en"><!-- EPO <DP n="13"> -->
<claim id="c-en-0001" num="0001">
<claim-text>A method for invalidating an electronic key (2') for access to a physical space (16), the method being performed in an invalidation device (1, 1a, 1b) and comprising the steps of:
<claim-text>receiving (40) a central invalidation command (30) from a central server (10), the central invalidation command (30) comprising an identifier of an electronic key (2');</claim-text>
<claim-text>discovering (42) a presence of the electronic key (2') over short range radio; and</claim-text>
<claim-text>transmitting (44) a local invalidation command (32) to the electronic key.</claim-text></claim-text></claim>
<claim id="c-en-0002" num="0002">
<claim-text>The method according to claim 1, further comprising the steps of:
<claim-text>receiving (46) a local confirmation message (33) from the electronic key (2'), the local confirmation message (33) indicating a successful invalidation; and</claim-text>
<claim-text>transmitting (48) a central confirmation message (34) to the central server, the central confirmation message (34) indicating a successful invalidation.</claim-text></claim-text></claim>
<claim id="c-en-0003" num="0003">
<claim-text>The method according to claim 2, wherein the central confirmation message (34) comprises an indicator of a position of the invalidation device (1, 1a, 1b).</claim-text></claim>
<claim id="c-en-0004" num="0004">
<claim-text>The method according to any one of the preceding claims, wherein the central invalidation command (30) comprises a main command and an integrity indicator.</claim-text></claim>
<claim id="c-en-0005" num="0005">
<claim-text>The method according to claim 4, wherein the integrity indicator is derived using the main command and a private electronic key.</claim-text></claim>
<claim id="c-en-0006" num="0006">
<claim-text>The method according to any one of the preceding claims, wherein the step of discovering (42) comprises discovering the presence of the electronic key (2') using Bluetooth low energy, BLE.<!-- EPO <DP n="14"> --></claim-text></claim>
<claim id="c-en-0007" num="0007">
<claim-text>The method according to any one of the preceding claims, wherein the step of receiving (40) a central invalidation command comprises receiving the central invalidation command over a wide area network.</claim-text></claim>
<claim id="c-en-0008" num="0008">
<claim-text>An invalidation device (1, 1a, 1b) for invalidating an electronic key for access to a physical space (16), the invalidation device (1, 1a, 1b) comprising:
<claim-text>a processor (60); and</claim-text>
<claim-text>a memory (64) storing instructions (66) that, when executed by the processor, cause the invalidation device (1, 1a, 1b) to:
<claim-text>receive a central invalidation command from a central server (10), the central invalidation command (30) comprising an identifier of an electronic key (2');</claim-text>
<claim-text>discover a presence of the electronic key (2') over short range radio; and</claim-text>
<claim-text>transmit a local invalidation command (31) to the electronic key.</claim-text></claim-text></claim-text></claim>
<claim id="c-en-0009" num="0009">
<claim-text>The invalidation device (1, 1a, 1b) according to claim 8, further comprising instructions (66) that, when executed by the processor, cause the invalidation device (1, 1a, 1b) to:
<claim-text>receive a local confirmation message (33) from the electronic key (2'), the local confirmation message (33) indicating a successful invalidation; and</claim-text>
<claim-text>transmit a central confirmation message (34) to the central server, the central confirmation message (34) indicating a successful invalidation.</claim-text></claim-text></claim>
<claim id="c-en-0010" num="0010">
<claim-text>The invalidation device (1, 1a, 1b) according to claim 9, wherein the central confirmation message (34) comprises an indicator of a position of the invalidation device (1, 1a, 1b).</claim-text></claim>
<claim id="c-en-0011" num="0011">
<claim-text>The invalidation device (1, 1a, 1b) according to claim 9 or 10, wherein the central invalidation command (30) comprises a main command and an integrity indicator.</claim-text></claim>
<claim id="c-en-0012" num="0012">
<claim-text>The invalidation device (1, 1a, 1b) according to any one of claims 9 to 11, wherein the invalidation device forms part of a mobile phone.<!-- EPO <DP n="15"> --></claim-text></claim>
<claim id="c-en-0013" num="0013">
<claim-text>The invalidation device (1, 1a, 1b) according to any one of claims 9 to 11, wherein the invalidation device is a device dedicated to the purpose of invalidating electronic keys.</claim-text></claim>
<claim id="c-en-0014" num="0014">
<claim-text>A computer program (90) for invalidating an electronic key for access to a physical space (16), the computer program comprising computer program code which, when run on an invalidation device (1, 1a, 1b), causes the invalidation device (1, 1a, 1b) to:
<claim-text>receive a central invalidation command from a central server (10), the central invalidation command (30) comprising an identifier of an electronic key (2');</claim-text>
<claim-text>discover a presence of the electronic key (2') over short range radio; and</claim-text>
<claim-text>transmit a local invalidation command (31) to the electronic key.</claim-text></claim-text></claim>
<claim id="c-en-0015" num="0015">
<claim-text>A computer program product (91) comprising a computer program according to claim 14 and a computer readable means on which the computer program is stored.</claim-text></claim>
</claims>
<drawings id="draw" lang="en"><!-- EPO <DP n="16"> -->
<figure id="f0001" num="1,2"><img id="if0001" file="imgf0001.tif" wi="136" he="233" img-content="drawing" img-format="tif"/></figure><!-- EPO <DP n="17"> -->
<figure id="f0002" num="3"><img id="if0002" file="imgf0002.tif" wi="165" he="152" img-content="drawing" img-format="tif"/></figure><!-- EPO <DP n="18"> -->
<figure id="f0003" num="4,5,6,7"><img id="if0003" file="imgf0003.tif" wi="165" he="233" img-content="drawing" img-format="tif"/></figure>
</drawings>
<search-report-data id="srep" lang="en" srep-office="EP" date-produced=""><doc-page id="srep0001" file="srep0001.tif" wi="157" he="233" type="tif"/><doc-page id="srep0002" file="srep0002.tif" wi="157" he="233" type="tif"/><doc-page id="srep0003" file="srep0003.tif" wi="155" he="233" type="tif"/></search-report-data><search-report-data date-produced="20151123" id="srepxml" lang="en" srep-office="EP" srep-type="ep-sr" status="n"><!--
 The search report data in XML is provided for the users' convenience only. It might differ from the search report of the PDF document, which contains the officially published data. The EPO disclaims any liability for incorrect or incomplete data in the XML for search reports.
 -->

<srep-info><file-reference-id>15162EP</file-reference-id><application-reference><document-id><country>EP</country><doc-number>15172118.0</doc-number></document-id></application-reference><applicant-name><name>Assa Abloy AB</name></applicant-name><srep-established srep-established="yes"/><srep-invention-title title-approval="yes"/><srep-abstract abs-approval="yes"/><srep-figure-to-publish figinfo="by-applicant"><figure-to-publish><fig-number>2</fig-number></figure-to-publish></srep-figure-to-publish><srep-info-admin><srep-office><addressbook><text>DH</text></addressbook></srep-office><date-search-report-mailed><date>20151201</date></date-search-report-mailed></srep-info-admin></srep-info><srep-for-pub><srep-fields-searched><minimum-documentation><classifications-ipcr><classification-ipcr><text>G07C</text></classification-ipcr></classifications-ipcr></minimum-documentation></srep-fields-searched><srep-citations><citation id="sr-cit0001"><patcit dnum="EP2821970A1" id="sr-pcit0001" url="http://v3.espacenet.com/textdoc?DB=EPODOC&amp;IDX=EP2821970&amp;CY=ep"><document-id><country>EP</country><doc-number>2821970</doc-number><kind>A1</kind><name>ASSA ABLOY AB [SE]</name><date>20150107</date></document-id></patcit><category>X</category><rel-claims>1-15</rel-claims><rel-passage><passage>* figures 1,3 *</passage><passage>* paragraph [0003] *</passage><passage>* paragraph [0026] - paragraph [0031] *</passage><passage>* paragraph [0034] *</passage><passage>* paragraph [0036] *</passage><passage>* paragraph [0045] *</passage><passage>* paragraph [0059] *</passage><passage>* claims 1,2 *</passage></rel-passage></citation><citation id="sr-cit0002"><patcit dnum="EP2207146A2" id="sr-pcit0002" url="http://v3.espacenet.com/textdoc?DB=EPODOC&amp;IDX=EP2207146&amp;CY=ep"><document-id><country>EP</country><doc-number>2207146</doc-number><kind>A2</kind><name>TALLERES ESCORIAZA SA [ES]</name><date>20100714</date></document-id></patcit><category>X</category><rel-claims>1-15</rel-claims><rel-passage><passage>* figure 1 *</passage><passage>* paragraph [0007] *</passage><passage>* paragraph [0023] *</passage><passage>* paragraph [0028] - paragraph [0029] *</passage><passage>* paragraph [0031] - paragraph [0034] *</passage><passage>* paragraph [0039] *</passage></rel-passage></citation><citation id="sr-cit0003"><patcit dnum="EP1564691A2" id="sr-pcit0003" url="http://v3.espacenet.com/textdoc?DB=EPODOC&amp;IDX=EP1564691&amp;CY=ep"><document-id><country>EP</country><doc-number>1564691</doc-number><kind>A2</kind><name>TOKAI RIKA CO LTD [JP]; TOYOTA MOTOR CO LTD [JP]</name><date>20050817</date></document-id></patcit><category>A</category><rel-claims>1,2,8,9,14,15</rel-claims><rel-passage><passage>* figures 1,4 *</passage><passage>* paragraph [0001] *</passage><passage>* paragraph [0014] - paragraph [0015] *</passage><passage>* paragraph [0019] - paragraph [0020] *</passage><passage>* paragraph [0071] - paragraph [0078] *</passage><passage>* paragraph [0083] *</passage><passage>* paragraph [0089] *</passage></rel-passage></citation><citation id="sr-cit0004"><patcit dnum="EP1568834A1" id="sr-pcit0004" url="http://v3.espacenet.com/textdoc?DB=EPODOC&amp;IDX=EP1568834&amp;CY=ep"><document-id><country>EP</country><doc-number>1568834</doc-number><kind>A1</kind><name>TOSHIBA KK [JP]</name><date>20050831</date></document-id></patcit><category>A</category><rel-claims>1,8,14,15</rel-claims><rel-passage><passage>* paragraph [0001] *</passage><passage>* paragraph [0049] - paragraph [0050] *</passage><passage>* paragraph [0059] - paragraph [0061] *</passage></rel-passage></citation><citation id="sr-cit0005"><patcit dnum="US2011140838A1" id="sr-pcit0005" url="http://v3.espacenet.com/textdoc?DB=EPODOC&amp;IDX=US2011140838&amp;CY=ep"><document-id><country>US</country><doc-number>2011140838</doc-number><kind>A1</kind><name>IMEDIO OCANA JUAN [ES]</name><date>20110616</date></document-id></patcit><category>A</category><rel-claims>1,2,8,9,14,15</rel-claims><rel-passage><passage>* figure 2 *</passage><passage>* paragraph [0002] *</passage><passage>* paragraph [0005] *</passage><passage>* paragraph [0010] *</passage><passage>* paragraph [0017] *</passage><passage>* paragraph [0027] - paragraph [0040] *</passage></rel-passage></citation></srep-citations><srep-admin><examiners><primary-examiner><name>Ngandu, William</name></primary-examiner></examiners><srep-office><addressbook><text>The Hague</text></addressbook></srep-office><date-search-completed><date>20151123</date></date-search-completed></srep-admin><!--							The annex lists the patent family members relating to the patent documents cited in the above mentioned European search report.							The members are as contained in the European Patent Office EDP file on							The European Patent Office is in no way liable for these particulars which are merely given for the purpose of information.							For more details about this annex : see Official Journal of the European Patent Office, No 12/82						--><srep-patent-family><patent-family><priority-application><document-id><country>EP</country><doc-number>2821970</doc-number><kind>A1</kind><date>20150107</date></document-id></priority-application><family-member><document-id><country>AU</country><doc-number>2014286214</doc-number><kind>A1</kind><date>20160107</date></document-id></family-member><family-member><document-id><country>CN</country><doc-number>105453142</doc-number><kind>A</kind><date>20160330</date></document-id></family-member><family-member><document-id><country>DK</country><doc-number>2821970</doc-number><kind>T3</kind><date>20160815</date></document-id></family-member><family-member><document-id><country>EP</country><doc-number>2821970</doc-number><kind>A1</kind><date>20150107</date></document-id></family-member><family-member><document-id><country>ES</country><doc-number>2577882</doc-number><kind>T3</kind><date>20160719</date></document-id></family-member><family-member><document-id><country>JP</country><doc-number>2016527779</doc-number><kind>A</kind><date>20160908</date></document-id></family-member><family-member><document-id><country>KR</country><doc-number>20160030928</doc-number><kind>A</kind><date>20160321</date></document-id></family-member><family-member><document-id><country>PL</country><doc-number>2821970</doc-number><kind>T3</kind><date>20161031</date></document-id></family-member><family-member><document-id><country>WO</country><doc-number>2015001009</doc-number><kind>A1</kind><date>20150108</date></document-id></family-member></patent-family><patent-family><priority-application><document-id><country>EP</country><doc-number>2207146</doc-number><kind>A2</kind><date>20100714</date></document-id></priority-application><family-member><document-id><country>AU</country><doc-number>2008306865</doc-number><kind>A1</kind><date>20090409</date></document-id></family-member><family-member><document-id><country>CA</country><doc-number>2711261</doc-number><kind>A1</kind><date>20090409</date></document-id></family-member><family-member><document-id><country>EP</country><doc-number>2207146</doc-number><kind>A2</kind><date>20100714</date></document-id></family-member><family-member><document-id><country>ES</country><doc-number>2323213</doc-number><kind>A1</kind><date>20090708</date></document-id></family-member><family-member><document-id><country>US</country><doc-number>2010223662</doc-number><kind>A1</kind><date>20100902</date></document-id></family-member><family-member><document-id><country>WO</country><doc-number>2009043952</doc-number><kind>A2</kind><date>20090409</date></document-id></family-member></patent-family><patent-family><priority-application><document-id><country>EP</country><doc-number>1564691</doc-number><kind>A2</kind><date>20050817</date></document-id></priority-application><family-member><document-id><country>EP</country><doc-number>1564691</doc-number><kind>A2</kind><date>20050817</date></document-id></family-member><family-member><document-id><country>JP</country><doc-number>4524122</doc-number><kind>B2</kind><date>20100811</date></document-id></family-member><family-member><document-id><country>JP</country><doc-number>2005226390</doc-number><kind>A</kind><date>20050825</date></document-id></family-member><family-member><document-id><country>US</country><doc-number>2005179519</doc-number><kind>A1</kind><date>20050818</date></document-id></family-member></patent-family><patent-family><priority-application><document-id><country>EP</country><doc-number>1568834</doc-number><kind>A1</kind><date>20050831</date></document-id></priority-application><family-member><document-id><country>EP</country><doc-number>1568834</doc-number><kind>A1</kind><date>20050831</date></document-id></family-member><family-member><document-id><country>JP</country><doc-number>2004187096</doc-number><kind>A</kind><date>20040702</date></document-id></family-member><family-member><document-id><country>US</country><doc-number>2006143463</doc-number><kind>A1</kind><date>20060629</date></document-id></family-member><family-member><document-id><country>WO</country><doc-number>2004051034</doc-number><kind>A1</kind><date>20040617</date></document-id></family-member></patent-family><patent-family><priority-application><document-id><country>US</country><doc-number>2011140838</doc-number><kind>A1</kind><date>20110616</date></document-id></priority-application><text>NONE</text></patent-family></srep-patent-family></srep-for-pub></search-report-data>
</ep-patent-document>
