WO2022219224A1

WO2022219224A1 - Retrieval of a parked vehicle

Info

Publication number: WO2022219224A1
Application number: PCT/FI2021/050271
Authority: WO
Inventors: Sweeda SHERIN
Original assignee: Kone Corporation
Priority date: 2021-04-14
Filing date: 2021-04-14
Publication date: 2022-10-20

Abstract

According to an example embodiment, there is provided a controller (200, 212, 400) comprising at least one processor (402) and at least one memory (404) including computer program code. The at least one memory (404) and the computer program code configured to, with the at least one processor (402), cause the controller (400) to at least perform: obtaining data (204), the data (204) being associated with a parked vehicle; and transmitting, based on the data (204), a message to enable a retrieval of the parked vehicle.

Description

RETRIEVAL OF A PARKED VEHICLE BACKGROUND

Valet parking is a service in which parking of a vehicle is performed by a valet. When using the valet parking, the user may be given some kind of identifier, for example, a card, with which the user is later able to have the vehicle retrieved when the user is leaving. The valet parking may be available, for example, in hotels, apartments and shopping malls.

When using the valet parking, the waiting time may be long to get the vehicle back from the valet parking.

SUMMARY

According to a first aspect, there is provided an apparatus comprising at least one processor and at least one memory including computer program code. The at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus to at least perform: obtaining data, the data identifying a parked vehicle; and transmitting, based on the data, a message to enable a retrieval of the parked vehicle.

In an implementation form of the first aspect, the at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus to at least perform: receiving location data indicating a location of the retrieved vehicle; and causing display of the location data on a display.

In an implementation form of the first aspect, the at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus to at least perform: transmitting the message to a building management system. In an implementation form of the first aspect, the at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus to at least perform: transmitting the message to a cloud node.

In an implementation form of the first aspect, the at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus to at least perform: transmitting an elevator identifier identifying the elevator car.

In an implementation form of the first aspect, the at least one memory and the computer program code configured to, with the at least one processor, cause the apparatus to at least perform: obtaining a trigger event; and obtaining the data based on the trigger event.

In an implementation form of the first aspect, the trigger event comprises an event associated with at least one of a location, time and acceleration. In an implementation form of the first aspect, obtaining the data comprises obtaining the data from a reader arranged in an elevator car.

In an implementation form of the first aspect, obtaining the data comprises obtaining the data from a reader of the apparatus.

In an implementation form of the first aspect, obtaining the data comprises obtaining the data from the at least one memory. In an implementation form of the first aspect, the data comprises identification information identifying the parked vehicle.

In an implementation form of the first aspect, the apparatus comprises a controller of an elevator system.

In an implementation form of the first aspect, the apparatus comprises a mobile device.

According to a second aspect, there is provided an elevator system comprising an apparatus of the first aspect; and a reader configured to obtain the data.

In an implementation form of the second aspect, the elevator system further comprises a display configured to display location data indicating a location of the retrieved vehicle wherein the display is arranged in the elevator car.

In an implementation form of the second aspect, the reader is arranged in an elevator car.

According to a third aspect, there is provided a cloud node comprising at least one processor and at least one memory including computer program code. The at least one memory and the computer program code are configured to, with the at least one processor, cause the cloud node to at least perform: receiving a message from an apparatus, the message being associated with a parked vehicle; and transmitting, based on the message, a request to a building management system to enable a retrieval of the parked vehicle.

In an implementation form of the third aspect, the at least one memory and the computer program code are configured to, with the at least one processor, cause the cloud node to at least perform: receiving an elevator identifier identifying an elevator car; and transmitting the elevator identifier to the building management system.

In an implementation form of the third aspect, the at least one memory and the computer program code are configured to, with the at least one processor, cause the cloud node to at least perform: receiving location data indicating a location of the retrieved vehicle from the building management system; and transmitting the location data to the apparatus.

In an implementation form of the third aspect, the data comprises identification information identifying the parked vehicle.

According to a fourth aspect, there is provided a method comprising: obtaining, by an apparatus of an elevator system, data, the data identifying a parked vehicle; and transmitting, by the apparatus, based on the data, a message to enable a retrieval of the parked vehicle.

In an implementation form of the fourth aspect, the method further comprises receiving, by the apparatus, location data indicating a location of the retrieved vehicle; and causing, by the apparatus, display of the location data on a display.

In an implementation form of the fourth aspect, the method further comprises transmitting, by the apparatus, the message to a building management system.

In an implementation form of the fourth aspect, the method further comprises transmitting, by the apparatus, the message to a cloud node. In an implementation form of the fourth aspect, the method further comprises transmitting, by the apparatus, an elevator identifier identifying an elevator car.

In an implementation form of the fourth aspect, obtaining the data comprises obtaining the data from the reader arranged in an elevator car.

In an implementation form of the fourth aspect, obtaining the data comprises obtaining the data from the reader of the apparatus.

In an implementation form of the fourth aspect, obtaining the data comprises obtaining the data from the at least one memory.

In an implementation form of the fourth aspect, the data comprises identification information identifying the parked vehicle.

In an implementation form of the fourth aspect, the apparatus comprises a controller of an elevator system.

In an implementation form of the fourth aspect, the apparatus comprises a mobile device.

According to a fifth aspect, there is provided a method comprising: receiving, by a cloud node, identification data from an apparatus, the identification data identifying a parked vehicle; and transmitting, by the cloud node, the identification data to a building management system to enable a retrieval of the parked vehicle.

In an implementation form of the fifth aspect, the method further comprises receiving, by the cloud node, an elevator identifier identifying the elevator car; and transmitting, by the cloud node, the elevator identifier to the building management system.

In an implementation form of the fifth aspect, the method further comprises receiving, by the cloud node, location data indicating a location of the retrieved vehicle from the building management system; and transmitting, by the cloud node, the location data to the apparatus.

According to a sixth aspect, there is provided a computer program comprising instructions which, when the program is executed by the at least one processor of the apparatus of the first aspect, cause the apparatus to carry out the method of the fourth aspect.

According to a seventh aspect, there is provided a computer program comprising instructions which, when the program is executed by the at least one processor of the cloud node of the third aspect, cause the cloud node to carry out the method of the fifth aspect.

According to an eighth aspect, there is provided a computer-readable medium comprising instructions which, when the program is executed by the at least one processor of the apparatus of the first aspect, cause the apparatus to carry out the method of the fourth aspect.

According to a ninth aspect, there is provided a computer-readable medium comprising instructions which, when the program is executed by the at least one processor of the cloud node of the third aspect, cause the cloud node to carry out the method of the fifth aspect. BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are included to provide a further understanding of the invention and constitute a part of this specification, illustrate embodiments of the invention and together with the description help to explain the principles of the invention. In the drawings:

FIG. 1A illustrates a flow chart of a method for enabling retrieval of a parked vehicle according to an example embodiment.

FIG. IB illustrates a flow chart of a method for enabling retrieval of a parked vehicle according to an example embodiment.

FIG. 2A illustrates an elevator system according to an example embodiment.

FIG. 2B illustrates a mobile device based solution according to an example embodiment.

FIG. 3 illustrates a system according to an example embodiment.

FIG. 4A illustrates a block diagram of an apparatus according to an example embodiment.

FIG. 4B illustrates a block diagram of a cloud node according to an example embodiment.

DETAILED DESCRIPTION

FIG. 1A illustrates a flow chart of a method for enabling retrieval of a parked vehicle according to an example embodiment. The method may be performed, for example, by a controller in an elevator system or a mobile device. At 100, the apparatus may obtain data, the data being associated with a parked vehicle. In an example embodiment, the data may comprise identification data that identifies the vehicle. The data may be read, for example, with a reader. The reader may be implemented, for example, using near field communication (NFC) or any other short-range information transmission technique, for example, radio frequency identification (RFID). In another example embodiment, the reader may refer to a camera configured to optically read the identification data. In another example embodiment, the reader may be configured to read a smart card. The identification data may comprise any identifier that uniquely identifies the vehicle. The reader may be part of the apparatus or an external reader connected to the apparatus. In another example embodiment, the data may be obtained from a memory of the apparatus or obtained based on an event performed with the apparatus. In another embodiment, the apparatus may obtain the data from another entity, for example, via a request.

At 102, the apparatus may transmit, based on the data, a message to enable a retrieval of the parked vehicle. The message may be transmitted, for example, to a building management system (BMS) that then arranges, based on the message, a retrieval of the vehicle. In an example embodiment, in addition to the message, the apparatus may transmit an elevator identifier to identify the elevator that the user using. Based in the elevator identifier, the building management system is able to know which elevator the user is using and thus take this into account when retrieving the vehicle. In another example embodiment, the apparatus may transmit the message to a cloud node which then interfaces towards the building management system. In an example embodiment, the message may comprise the identification data.

In an example embodiment, the apparatus may obtain a trigger event, and the data is then obtained based on the trigger event. The trigger event may comprise an event associated with at least one of a location, time and acceleration. For example, if the location of the user of the apparatus reaches a preset location or area, the data may be obtained in response to this. Or, if the user travels in an elevator, an acceleration measured by the apparatus exceeding a preset threshold may act as a trigger event for obtaining the data. Or, if time is used as a trigger, when a preset is reached, it may act as a trigger event for obtaining the data.

In an example embodiment, an application executed in the apparatus may send a message to the user's car or to some other entity. The transmission may be initiated, for example, when the user selects an event "fetch my car" with the application. In response to the message, an application executed by the car or the entity may transmit a request, for example, to a building management to enable a retrieval of the parked vehicle.

In an example embodiment, the application executed in the apparatus may obtain the data in a digital form without using a reader. For example, the data may comprise identification information identifying the parked vehicle, and it may be obtained, for example, from a memory of the mobile device or received by the application in a digital form from an outside entity. The identification data may be part, for example, of a digital card or parking ticket. The transmitted message may then comprise the identification information. FIG. IB illustrates a flow chart of a method for enabling retrieval of a parked vehicle according to an example embodiment. The method may be performed, for example, by a cloud node associated with an elevator system. The term "cloud node" may refer to any node or apparatus that can be reached via a communication network, for example, the internet.

At 104 the cloud node may receive a message from an apparatus, the message being associated with a parked vehicle. In an example embodiment, the message may comprise identification data identifying the parked vehicle.

At 106 the cloud node may transmit, based on the message, a request to a building management system to enable a retrieval of the parked vehicle. In an example embodiment, the request may comprise identification data identifying the parked vehicle.

In an example embodiment, in addition to the message, the cloud node may receive from the apparatus also an elevator identifier identifying the elevator car and transmit the elevator identifier to the building management system. Based on the elevator identifier, the building management system is then able to know which elevator the user is using (i.e. the location of the elevator) and thus take this into account when retrieving the vehicle.

In an example embodiment, the cloud node may further receive location data indicating a location of the retrieved vehicle from the building management system and transmit the location data to the apparatus.

FIG. 2A illustrates an elevator system according to an example embodiment. The elevator system comprises an apparatus 200 and an elevator car 206 connected to the apparatus 200. The apparatus 200 may be an elevator controller or some other controller associated with the elevator system. The elevator car 206 may comprise a reader 202 configured to read identification data 204. The reader 202 may be implemented, for example, using near field communication (NFC) or any other contactless short-range information transmission technique, for example, radio frequency identification (RFID). In another example embodiment, the reader 202 may be configured to read a smart card. The identification data 204 may be stored in a chip or circuitry that can be wirelessly read by the reader 202 or in the smart card read by the reader 202.

A user 208 may have earlier used a valet parking service for the user's vehicle, and received, for example, an identification card or a tag containing the identification data from the valet. In another example embodiment, the user may have parked the car by himself, and obtained the identification card or the tag containing the identification data after the parking. The identification data is associated with the user's vehicle. When the user then enters the elevator car 206 in order to leave the building, the user shows the identification card or a tag to the reader 202 in the elevator in order to enable reading of the identification data 204 stored on the identification card or the tag. In another example embodiment, the reader 202 may comprise an input device configured to obtain the identification data, for example, a numerical or alphanumerical code from the user 208. When the identification data 204 is read or obtained with the reader 202, it provides an indication that the user 208 wishes to have the vehicle retrieved from parking. The apparatus 200 connected to the reader 202 transmits the identification data 204 to a cloud node or to a building management system to enable retrieval of the vehicle. The vehicle may be retrieved closer to the elevator in the parking space. In an example embodiment, there may be a dedicated space for retrieved cars close to the elevator.

FIG. 2B illustrates a mobile device 212 based solution according to an example embodiment. In this embodiment, the mobile device 212 comprises a reader 214. The reader 214 may be implemented, for example, using near field communication (NFC) or any other short-range information transmission technique, for example, radio frequency identification (RFID). In another example embodiment, the reader 214 may refer to a camera configured to optically read the identification data. In another example embodiment, the reader 214 may be configured to read a smart card. The identification data 204 may be stored in a chip or circuitry that can be wirelessly read by the reader 214 or in the smart card read by the reader 214.

A user 208 may have earlier used a valet parking service for the user's vehicle, and received, for example, an identification card or a tag containing the identification data from the valet. The identification data is associated with the user's vehicle. When the user then is about the leave the building, the user may use the reader 214 in order to enable reading of the identification data 204 stored on the identification card or the tag. When the identification data 204 is obtained with the reader 214, it provides an indication that the user 208 wishes to have the vehicle retrieved from parking. The mobile device 212 may transmit the identification data 204 to a cloud node or to a building management system to enable retrieval of the vehicle. In an example embodiment, the mobile device 212 may be configured to transmit also an elevator identifier identifying an elevator car. The elevator identifier may be obtained, for example, from the user 208. The vehicle may be retrieved closer to the elevator in the parking space. In an example embodiment, there may be a dedicated space for retrieved cars close to the elevator.

FIG. 3 illustrates a system according to an example embodiment. The system comprises an apparatus 200, 212, a cloud node 300 and a building management system 302. As already discussed above in relation to FIG. 2A and 2B, the apparatus 200, 212 may transmit the identification data to the cloud node 300 to enable retrieval of the vehicle. In another example embodiment, the apparatus 200, 212 may transmit the identification data directly to the building management system 302. The building management system 302 interfaces with a valet parking service and is able to control the retrieval of the user's vehicle.

FIG. 4A illustrates a block diagram of an apparatus according to an example embodiment. The apparatus 400 may be configured to implement the method discussed earlier in relation to FIG. 1A.

The apparatus 400 comprises one or more processors 402, and one or more memories 404 that comprise computer program code. The apparatus 400 may also include an input/output module (not shown in FIG. 4A), and/or a communication interface 408. Although the apparatus 400 is depicted to include only one processor 402, the apparatus 400 may include more than one processor. In an example embodiment, the memory 404 is capable of storing instructions, such as an operating system and/or various applications. Furthermore, the processor 402 is capable of executing the stored instructions. In an example embodiment, the processor 402 may be embodied as a multi-core processor, a single core processor, or a combination of one or more multi-core processors and one or more single core processors. For example, the processor 402 may be embodied as one or more of various processing devices, such as a coprocessor, a microprocessor, a controller, a digital signal processor (DSP), a processing circuitry with or without an accompanying DSP, or various other processing devices including integrated circuits such as, for example, an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), a microcontroller unit (MCU), a hardware accelerator, a special-purpose computer chip, or the like. In an example embodiment, the processor 402 may be configured to execute hard-coded functionality. In an example embodiment, the processor 402 is embodied as an executor of software instructions, wherein the instructions may specifically configure the processor 402 to perform the algorithms and/or operations described herein when the instructions are executed.

The memory 404 may be embodied as one or more volatile memory devices, one or more non-volatile memory devices, and/or a combination of one or more volatile memory devices and non-volatile memory devices. For example, the memory 404 may be embodied as semiconductor memories (such as mask ROM, PROM (programmable ROM), EPROM (erasable PROM), flash ROM, RAM (random access memory), etc.).

In an embodiment, the at least one memory 404 may store program instructions 406 that, when executed by the at least one processor 402, cause the apparatus 400 to perform the functionality of the various embodiments discussed herein. Further, in an embodiment, at least one of the processor 402 and the memory 404 may constitute means for implementing the discussed functionality .

FIG. 4B illustrates a block diagram of a cloud node 410 according to an example embodiment. The cloud node 410 may be configured to implement the method discussed earlier in relation to FIG. IB.

The cloud node 410 comprises one or more processors 412, and one or more memories 414 that comprise computer program code. The cloud node 410 may also include an input/output module (not shown in FIG. 4B), and/or a communication interface 418. Although the cloud node 410 is depicted to include only one processor 412, the cloud node 410 may include more than one processor. In an example embodiment, the memory 414 is capable of storing instructions, such as an operating system and/or various applications. In an example embodiment, the cloud node 410 may be implemented as a server.

Furthermore, the processor 412 is capable of executing the stored instructions. In an example embodiment, the processor 412 may be embodied as a multi-core processor, a single core processor, or a combination of one or more multi-core processors and one or more single core processors. For example, the processor 412 may be embodied as one or more of various processing devices, such as a coprocessor, a microprocessor, a controller, a digital signal processor (DSP), a processing circuitry with or without an accompanying DSP, or various other processing devices including integrated circuits such as, for example, an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), a microcontroller unit (MCU), a hardware accelerator, a special-purpose computer chip, or the like. In an example embodiment, the processor 412 may be configured to execute hard-coded functionality. In an example embodiment, the processor 412 is embodied as an executor of software instructions, wherein the instructions may specifically configure the processor 412 to perform the algorithms and/or operations described herein when the instructions are executed.

The memory 414 may be embodied as one or more volatile memory devices, one or more non-volatile memory devices, and/or a combination of one or more volatile memory devices and non-volatile memory devices. For example, the memory 414 may be embodied as semiconductor memories (such as mask ROM, PROM (programmable ROM), EPROM (erasable PROM), flash ROM, RAM (random access memory), etc.).

In an embodiment, the at least one memory 404 may store program instructions 416 that, when executed by the at least one processor 412, cause the cloud node 410 to perform the functionality of the various embodiments discussed herein. Further, in an embodiment, at least one of the processor 412 and the memory 414 may constitute means for implementing the discussed functionality .

The illustrated solution may enable a solution which reduces the user's waiting time when leaving from a building having a valet service. When the vehicle's retrieval process is initiated already when the user is in an elevator or even before the user has reached the elevator, the waiting time of the retrieval of the user's vehicle is reduced.

Example embodiments may be implemented in software, hardware, application logic or a combination of software, hardware and application logic. The example embodiments can store information relating to various methods described herein. This information can be stored in one or more memories, such as a hard disk, optical disk, magneto-optical disk, RAM, and the like. One or more databases can store the information used to implement the example embodiments. The databases can be organized using data structures (e.g., records, tables, arrays, fields, graphs, trees, lists, and the like) included in one or more memories or storage devices listed herein. The methods described with respect to the example embodiments can include appropriate data structures for storing data collected and/or generated by the methods of the devices and subsystems of the example embodiments in one or more databases.

The components of the example embodiments may include computer readable medium or memories for holding instructions programmed according to the teachings and for holding data structures, tables, records, and/or other data described herein. In an example embodiment, the application logic, software or an instruction set is maintained on any one of various conventional computer-readable media. In the context of this document, a "computer-readable medium" may be any media or means that can contain, store, communicate, propagate or transport the instructions for use by or in connection with an instruction execution system, apparatus, or device, such as a computer. A computer- readable medium may include a computer-readable storage medium that may be any media or means that can contain or store the instructions for use by or in connection with an instruction execution system, apparatus, or device, such as a computer. A computer readable medium can include any suitable medium that participates in providing instructions to a processor for execution. Such a medium can take many forms, including but not limited to, non-volatile media, volatile media, transmission media, and the like. While there have been shown and described and pointed out fundamental novel features as applied to preferred embodiments thereof, it will be understood that various omissions and substitutions and changes in the form and details of the devices and methods described may be made by those skilled in the art without departing from the spirit of the disclosure. For example, it is expressly intended that all combinations of those elements and/or method steps which perform substantially the same function in substantially the same way to achieve the same results are within the scope of the disclosure. Moreover, it should be recognized that structures and/or elements and/or method steps shown and/or described in connection with any disclosed form or embodiments may be incorporated in any other disclosed or described or suggested form or embodiment as a general matter of design choice. The applicant hereby discloses in isolation each individual feature described herein and any combination of two or more such features, to the extent that such features or combinations are capable of being carried out based on the present specification as a whole, in the light of the common general knowledge of a person skilled in the art, irrespective of whether such features or combinations of features solve any problems disclosed herein, and without limitation to the scope of the claims. The applicant indicates that the disclosed aspects/embodiments may consist of any such individual feature or combination of features. In view of the foregoing description it will be evident to a person skilled in the art that various modifications may be made within the scope of the disclosure.

Claims

1. An apparatus (200, 212, 400) comprising: at least one processor (402); and at least one memory (404) including computer program code; the at least one memory (404) and the computer program code configured to, with the at least one processor (402), cause the apparatus (400) to at least perform: obtaining data (204), the data (204) being associated with a parked vehicle; and transmitting, based on the data (204), a message to enable a retrieval of the parked vehicle. 2. The apparatus (200, 212, 400) of claim 1, wherein the at least one memory (404) and the computer program code configured to, with the at least one processor (402), cause the apparatus (200, 212, 400) to at least perform: receiving location data indicating a location of the retrieved vehicle; and causing display of the location data on a display (210). 3. The apparatus (200, 212, 400) of claim 1 or

2, wherein the at least one memory (404) and the computer program code configured to, with the at least one processor (402), cause the apparatus (200, 212, 400) to at least perform: transmitting the message to a building management system (302).

4. The apparatus (200, 212, 400) of claim 1 or 2, wherein the at least one memory (404) and the computer program code configured to, with the at least one processor (402), cause the apparatus (200, 212, 400) to at least perform: transmitting the message to a cloud node (300).

5. The apparatus (200, 212, 400) of any of claims 1 - 4, wherein the at least one memory (404) and the computer program code configured to, with the at least one processor (402), cause the apparatus (200, 212, 400) to at least perform: transmitting an elevator identifier identifying an elevator car.

6. The apparatus (200, 212, 400) of any of claims 1 - 4, wherein the at least one memory (404) and the computer program code configured to, with the at least one processor (402), cause the apparatus (200, 212, 400) to at least perform: obtaining a trigger event; and obtaining the data based on the trigger event.

7. The apparatus (200, 212, 400) of claims 1 - 6, wherein the trigger event comprises an event associated with at least one of a location, time and acceleration.

8. The apparatus (200, 212, 400) of any of claims 1-7, wherein obtaining the data (204) comprises obtaining the data (204) from the reader (202) arranged in an elevator car.

9. The apparatus (200, 212, 400) of any of claims 1-7, wherein obtaining the data (204) comprises obtaining the data (204) from the reader (214) of the apparatus (200, 212, 400).

10. The apparatus (200, 212, 400) of any of claims 1-7, wherein obtaining the data (204) comprises obtaining the data (204) from the at least one memory (404). 11. The apparatus (200, 212, 400) of any of claims 1 - 10, wherein the data comprises identification information identifying the parked vehicle.

12. The apparatus (200, 212, 400) of any of claims 1 - 11, wherein the apparatus (200, 212, 400) comprises a controller (200) of an elevator system. 13. The apparatus (200, 212, 400) of any of claims 1 - 11, wherein the apparatus (200, 212, 400) comprises a mobile device (212).

14. An elevator system comprising: an apparatus (200, 400) of any of claims 1 -

12; and a reader (202) configured to obtain the data

(204). 15. The elevator system of claim 14, further comprising: a display (210) configured to display location data indicating a location of the retrieved vehicle wherein the display (210) is arranged in the elevator car (206).

16. The elevator system of claim 14 or 15, wherein the reader (202) is arranged in an elevator car (206).

17. A cloud node (300, 410) comprising: at least one processor (412); and at least one memory (414) including computer program code; the at least one memory (414) and the computer program code configured to, with the at least one processor (412), cause the cloud node (300, 410) to at least perform: receiving a message from an apparatus (400), the message being associated with a parked vehicle; and transmitting, based on the message, a request to a building management system (302) to enable a retrieval of the parked vehicle.

18. The cloud node (300, 410) of claim 17, the at least one memory (404) and the computer program code being configured to, with the at least one processor (402), cause the cloud node (300, 410) to at least perform: receiving an elevator identifier identifying an elevator car; and transmitting the elevator identifier to the building management system (302).

19. The cloud node (300, 410) of claim 17 or 18, the at least one memory (404) and the computer program code being configured to, with the at least one processor (402), cause the cloud node (300, 410) to at least perform: receiving location data indicating a location of the retrieved vehicle from the building management system (302); and transmitting the location data to the apparatus

(400).

20. The cloud node (300, 410) of any of claims 17 - 19, wherein the data comprises identification information identifying the parked vehicle.

21. A method comprising: obtaining, by an apparatus (200, 212, 400), data (204), the data (204) being associated with a parked vehicle; and transmitting, by the apparatus (200, 212, 400), based on the data (204), message to enable a retrieval of the parked vehicle.

22. The method of claim 21, further comprising: receiving, by the apparatus (200, 212, 400), location data indicating a location of the retrieved vehicle; and causing, by the apparatus (200, 212, 400), display of the location data on a display (210).

23. The method of claim 21 or 22, further comprising: transmitting, by the apparatus (200, 212, 400), the message to a building management system (302).

24. The method of claim 21 or 22, further comprising: transmitting, by the apparatus (200, 212, 400), the message to a cloud node (300).

25. The method of any of claims 21 - 24, further comprising: transmitting, by the apparatus (200, 212, 400), an elevator identifier identifying an elevator car.

26. The method of any of claims 21 - 25, wherein obtaining the data (204) comprises obtaining the data (204) from the reader (202) arranged in an elevator car.

27. The method of any of claims 21 - 26, wherein obtaining the data (204) comprises obtaining the data (204) from the reader (214) of the apparatus (200, 212, 400).

28. The method of any of claims 21 - 27, wherein obtaining the data (204) comprises obtaining the data (204) from the at least one memory (404).

29. The method of any of claims 21 - 28, wherein the data comprises identification information identifying the parked vehicle.

30. The method of any of claims 21 - 29, wherein the apparatus (200, 212, 400) comprises a controller of an elevator system.

31. The method of any of claims 21 - 29, wherein the apparatus (200, 212, 400) comprises a mobile device (212).

32. A method comprising: receiving, by a cloud node (300), a message from an apparatus (200, 212, 400), the message being associated with a parked vehicle; and transmitting, by the cloud node (300), based on the message a request to a building management system (302) to enable a retrieval of the parked vehicle.

33. The method of claim 32, further comprising: receiving, by the cloud node (300), an elevator identifier identifying the elevator car; and transmitting, by the cloud node (300), the elevator identifier to the building management system (302).

34. The method of claim 32 or 33, further comprising: receiving, by the cloud node (300), location data indicating a location of the retrieved vehicle from the building management system (302); and transmitting, by the cloud node (300), the location data to the apparatus (200, 212, 400). 35. The method of any of claims 32 - 34, wherein the data comprises identification information identifying the parked vehicle.

36. A computer program comprising instructions which, when the program is executed by the at least one processor (402) of the apparatus (200, 212, 400) of claim 1, cause the apparatus (200, 212, 400) to carry out the method of any of claims 21 - 31.

37. A computer program comprising instructions which, when the program is executed by the at least one processor (402) of the cloud node (300, 410) of claim 17, cause the cloud node (300, 410) to carry out the method of any of claims 32 - 35.

38. A computer-readable medium comprising instructions which, when the program is executed by the at least one processor (402) of the apparatus (200, 212, 400) of claim 1, cause to apparatus (400) carry out the method of any of claims 21 - 31.

39. A computer-readable medium comprising instructions which, when the program is executed by the at least one processor (412) of the cloud node (300, 410) of claim 17, cause the cloud node (300, 410) to carry out the method of any of claims 32 - 35.