EP3105159B1 - Verfahren zum betrieb einer aufzugsanlage, aufzugsteuerungseinrichtung und mobilfunkgerät zur ausführung des verfahrens sowie system mit einer solchen aufzugsteuerungseinrichtung und einem mobilfunkgerät - Google Patents

Verfahren zum betrieb einer aufzugsanlage, aufzugsteuerungseinrichtung und mobilfunkgerät zur ausführung des verfahrens sowie system mit einer solchen aufzugsteuerungseinrichtung und einem mobilfunkgerät Download PDF

Info

Publication number
EP3105159B1
EP3105159B1 EP15704299.5A EP15704299A EP3105159B1 EP 3105159 B1 EP3105159 B1 EP 3105159B1 EP 15704299 A EP15704299 A EP 15704299A EP 3105159 B1 EP3105159 B1 EP 3105159B1
Authority
EP
European Patent Office
Prior art keywords
elevator
elevator installation
identification code
server
floor
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
EP15704299.5A
Other languages
German (de)
English (en)
French (fr)
Other versions
EP3105159A1 (de
Inventor
Adrian Bünter
Markus GILLI
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Inventio AG
Original Assignee
Inventio AG
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Family has litigation
First worldwide family litigation filed litigation Critical https://patents.darts-ip.com/?family=50073076&utm_source=google_patent&utm_medium=platform_link&utm_campaign=public_patent_search&patent=EP3105159(B1) "Global patent litigation dataset” by Darts-ip is licensed under a Creative Commons Attribution 4.0 International License.
Application filed by Inventio AG filed Critical Inventio AG
Priority to PL15704299T priority Critical patent/PL3105159T3/pl
Publication of EP3105159A1 publication Critical patent/EP3105159A1/de
Application granted granted Critical
Publication of EP3105159B1 publication Critical patent/EP3105159B1/de
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • B—PERFORMING OPERATIONS; TRANSPORTING
    • B66—HOISTING; LIFTING; HAULING
    • B66B—ELEVATORS; ESCALATORS OR MOVING WALKWAYS
    • B66B1/00—Control systems of elevators in general
    • B66B1/34—Details, e.g. call counting devices, data transmission from car to control system, devices giving information to the control system
    • B66B1/46—Adaptations of switches or switchgear
    • B66B1/468—Call registering systems
    • B—PERFORMING OPERATIONS; TRANSPORTING
    • B66—HOISTING; LIFTING; HAULING
    • B66B—ELEVATORS; ESCALATORS OR MOVING WALKWAYS
    • B66B2201/00—Aspects of control systems of elevators
    • B66B2201/40—Details of the change of control mode
    • B66B2201/46—Switches or switchgear
    • B66B2201/4607—Call registering systems
    • B66B2201/4615—Wherein the destination is registered before boarding
    • B—PERFORMING OPERATIONS; TRANSPORTING
    • B66—HOISTING; LIFTING; HAULING
    • B66B—ELEVATORS; ESCALATORS OR MOVING WALKWAYS
    • B66B2201/00—Aspects of control systems of elevators
    • B66B2201/40—Details of the change of control mode
    • B66B2201/46—Switches or switchgear
    • B66B2201/4607—Call registering systems
    • B66B2201/4653—Call registering systems wherein the call is registered using portable devices
    • B—PERFORMING OPERATIONS; TRANSPORTING
    • B66—HOISTING; LIFTING; HAULING
    • B66B—ELEVATORS; ESCALATORS OR MOVING WALKWAYS
    • B66B2201/00—Aspects of control systems of elevators
    • B66B2201/40—Details of the change of control mode
    • B66B2201/46—Switches or switchgear
    • B66B2201/4607—Call registering systems
    • B66B2201/4676—Call registering systems for checking authorization of the passengers

Definitions

  • the invention first and foremost relates to a method for operating an elevator installation. Furthermore, the invention also relates to an elevator control device and a mobile radio device for carrying out the method and to a system having such an elevator control device and such a mobile radio device.
  • the operation of a lift installation by means of a lift control device is known in its basic features per se. If a user wants to travel from one floor (start floor) to another floor (destination floor), he operates on the respective start floor a control panel associated with the control panel and thus causes a so-called floor call, which is processed by the elevator control device. If the elevator car or an elevator car of the elevator installation becomes available or passes through the floor on which the landing call was triggered without any particular restrictions during a current movement operation, the elevator control device causes the elevator car to move to the respective floor and / or to stop the car on the respective floor Floor. When the user enters the elevator car, he selects a destination floor at a control panel in the elevator car and thus triggers a car call at the elevator control device. The elevator car is then moved to the thus specified destination floor. In this case, optionally previously specified other destination floors are approached or the elevator car stops due to a car or floor call in a floor between the current floor and the destination floor.
  • the use of such an identification code is such that the identification code is received by means of a mobile device that a drive request is specified by means of running on the mobile device software drive that the drive request using the floor-specific identification code or possibly using the floor-specific and elevator-specific identification codes in the form of a first travel request telegram is transmitted to a remote, in particular accessible on the Internet server and that the server forwards the drive request in the form of a second travel request telegram to the elevator installation.
  • the mobile device and the software application running on it especially a user interface represented by the software application, act like a conventional control panel of the elevator installation, namely, for example, like a conventional floor control panel.
  • the travel request telegram associated with the drive request associated with the mobile device and the software application running on it is generated by the software application using the floor-specific or floor-specific and elevator-specific identification code. Since the identification code is at least floor-specific, the travel request telegram comprises data relating to the floor on which the user of the mobile radio device will begin the use of the elevator installation.
  • the transmission of the driving desire by the server to the elevator system is carried out, for example, to an elevator control device of the respective elevator installation or to a unit acting as an interface to the elevator control unit.
  • the advantage of the invention is that the mobile device can be used with a software application running on it and intended for carrying out the method instead of the usual control panels of the elevator installation and that additional functions and / or information are available.
  • the user of the mobile device does not need to specify the respective start floor for his drive request, since information about the start floor is already contained in the floor-specific identification code received by a transmission unit. Incorrect entries are prevented in this way.
  • the identification code comprises at least one elevator installation identifier and the elevator installation sends to the remote server an elevator installation data record which comprises elevator installation-specific data, namely at least likewise an elevator installation identifier.
  • the software application of the mobile device sends a respective received identification code or at least the elevator system identifier included therein to the server.
  • the server Upon receipt of the elevator system identifier, the server searches for an elevator system data record with a suitable elevator system identifier. In the case of success, that is, if an elevator installation data record matching the lift system identifier obtained could be determined, the server sends the elevator installation data record to the mobile radio device.
  • the mobile device and the software application running thereupon thus receive the lift-system-specific information encompassed by the elevator installation data set, such as, for example, the number of floors that can be reached by the elevator installation.
  • the elevator system identifier of the identification code By evaluating the elevator system identifier of the identification code before transmitting the elevator system data record to the mobile radio device, it can be ensured that only the elevator-specific data that matches the elevator system in the building in which the user currently has his mobile radio device fit.
  • At least one of the data encompassed by the identification code and / or the elevator installation data record is displayed graphically or in another manner by means of a user interface generated by the software application.
  • the identification code is floor-specific, the user of the mobile device can be informed in a display of the data covered by the identification code, for example, on which floor he is currently located in the respective building.
  • an indication of the floors that can be reached by the elevator installation and / or a display of further information about the respective building can be made.
  • the server receiving the identification code can distinguish data telegrams which comprise the identification code prefix by means of the identification code prefix from other data telegrams.
  • the identification code comprises a message or message authentication code, in particular a message or message authentication code in the form of an encrypted hash message authentication code, it can be ensured that the identification code or a data message containing the identification code was not corrupted on the way to the server, so that misuse is excluded.
  • the above-mentioned object is also achieved with an elevator control device and a mobile radio device which are designed and set up for the execution of the elevator system side or mobile radio device-side part of the method.
  • the invention is preferably implemented in software.
  • FIG. 1 1 schematically shows in simplified form an elevator installation 10 in a building, not shown, having at least one elevator car 14 movable in at least one elevator shaft 12 and an elevator control device 16 provided at a central location of the building.
  • the elevator control device 16 is in a manner known per se for controlling the elevator installation 10 provided.
  • the or each elevator car 14 is movable in a manner known per se in the elevator shaft 12 or in the respective elevator shaft 12 so that different floors 18 of the building can be reached.
  • control panels 20, 22 are usually provided, namely at least one cabin control panel 20, and in each case one control panel on each floor 18 (floor control panel 22).
  • the user of the elevator installation 10 transmits the elevator control device 16 by means of operator actions on a control panel 20, 22 a respective travel request and as soon as the travel request is fulfilled, causes the elevator control device 16 a corresponding movement of the elevator car fourteenth
  • FIG. 2 Repeats for further description of the approach proposed here, individual aspects of the representation in FIG. 1 so they do not need to be described again here.
  • the number of illustrated floors 18 is shown in FIG FIG. 2 opposite to the illustration in FIG. 1 only for the sake of clarity has been reduced.
  • the approach proposed here is not limited to an elevator installation 10 having a certain number of floors 18.
  • the approach proposed here is also applicable to an elevator installation 10 having a plurality of elevator cars 14.
  • the user carries a mobile phone 24 with him.
  • the mobile telephone 24 can be connected in a manner known per se communicatively with a mobile radio network and the Internet 26 and connected when used in the context of the approach proposed here.
  • a connection to an external server 28, for example a server 28 of the manufacturer or the operator of the elevator installation 10, can be established via the Internet 26.
  • the elevator control device 16 or a further device connected to the elevator control device 16 at the location of the elevator installation 10 is itself wired or conduction-free to the Internet 26 and to the server 28 via the Internet 26.
  • the following description is - without renouncing a more general validity - continued on the example of a directly, so without the interposition of another device, via the Internet 26 connected to the server 28 elevator control device 16.
  • the possibility of interposing such a device is nevertheless always to be read in the following. If such a unit is present, it will partly replace the elevator control unit 16 in the method described below In particular, the following options are possible: wireless LAN, WLAN / WiFi, PSTN, 2G, 3G, LTE, GPRS, etc.
  • the elevator control unit 16 After commissioning of the elevator installation 10, after completion of maintenance of the elevator installation 10 or according to additional or alternative predetermined or specifiable rules (once a day, once a month, during faults, when replacing components, etc.), the elevator control unit 16 transmits in a data telegram (hereinafter referred to briefly as a telegram) an elevator installation data record 30 describing the elevator installation 10 to the server 28.
  • the elevator installation data record 30 is stored on the server 28 in a dedicated database (not shown separately) and can be retrieved from the database at the server 28.
  • FIG. 12 shows a possible layout of elevator database record 30 and individual data included in elevator database record 30 according to the approach suggested here.
  • These data include a respective elevator installation 10 uniquely identifying elevator installation identifier 32, which in FIG. 3 symbolically and exemplarily indicated as "200971".
  • the data further encompassed by the elevator installation data record 30 describe the elevator installation 10 with further details.
  • the data includes an indication of the number of floors 18 (number of floors 34), the number of elevator cars 14 (number of lifts 36) and a coded indication of the type of control (control type 38).
  • the control mode 38 encodes whether the respective functionality of the elevator control device 16 is a conventional controller, a group controller, a destination call controller, or a special function controller.
  • Special functions include functions with access control options and additionally or alternatively a disabled version of a travel request or a version that facilitates entry for mothers or users with baby carriages, shopping trolleys, etc. and provides for a longer opening time of the cabin and floor doors.
  • the elevator control device 16 in each case sends an elevator installation data record 30 with an elevator installation identifier 32 to the server 28. Then the respective elevator installation 10 is known on the server 28 side and use of the elevator installation 10 within the framework of the concept proposed here becomes possible.
  • the elevator control device 16 can send in the elevator installation data record 30, together with the elevator installation identifier 32, the above-mentioned further elevator-installation-specific data 34, 36, 38. Alternatively, there is also the possibility that the elevator control device 16 sends this elevator installation-specific data 34, 36, 38 to the server 28 only upon request from the server 28 at the elevator control device 16.
  • the elevator installation 10 includes transmission units 40 (FIG. Fig. 2 ) on each floor 18 or at least those floors 18 on which the approach described here should be usable. On each such floor 18 is at least one transmitting unit 40th
  • the transmission units 40 are not necessarily connected to the elevator control device 16. However, the transmitting units 40 are in each case spatially associated with the elevator installation 10 and, for example, mounted in the vicinity of the storey doors (on the walls or on the floor of the storey).
  • the transmitting units 40 permanently, ie regularly at predetermined or predefinable times, for example every second, in the form of a so-called Broadcast a floor-specific identification code 42. Because the identification code 42 is sent as a broadcast, each located in the transmission range of a transmitting unit 40 mobile device 24, the identification code 42 received.
  • the range of the transmitting units 40 is depending on the requirements in a range of 4-10 meters.
  • a greater range can be provided as long as it is ensured that a sent by a transmitting unit 40 of a first floor 18 identification code 42 received only on this floor 18 and not on another floor 18 can be.
  • the transmitting units 40 transmit the identification code 42 by means of WLAN / WiFi, WPNA, via Bluetooth or ZigBee or by known or future-known methods for the data transmission between devices over a short distance by radio technology.
  • data transmission according to the NFC standard is also conceivable.
  • the transmitting units 40 are conductively or conductively connected to the elevator control device 16, it is possible to use a variable identification code 42 predetermined or at least influenced by the elevator control device 16. In this way, a user on his mobile device 24 in the context of the receipt of an identification code 42 receive additional information about the elevator system 10, for example, the information as to whether a particular elevator is out of service. If the transmitting units 40 are independent of the elevator control device 16, they send a predetermined or predefinable identification code 42, which is adjustable, for example, at each transmitting unit 40, either during programming or for example via so-called DIP switches or the like.
  • FIG. 4 shows a possible layout of the floor-specific identification code 42 and individual according to the approach proposed here of the identification code 42 included data.
  • These data include an identification code prefix 44, an elevator system identifier 46 uniquely identifying the respective elevator installation 10, a floor identifier 48 and an optional message or message authentication code 50 provided to protect the identification code 42 against tampering.
  • the floor identifier 48 includes either the respective floor number or a coded shape of the floor number. With the identification code 42 comprising the floor identifier 48, the identification code 42 is floor-specific. At the in FIG. 4 In the situation shown, the identification code 42 is floor-specific and elevator-specific, since it includes not only the floor identifier 48 but also the elevator installation identifier 46.
  • the respective value of the message authentication code 50 is determined by the transmitting unit 40 according to an algorithm implemented in the transmitting unit 40, for example as an encrypted hash message authentication code (HMAC).
  • HMAC encrypted hash message authentication code
  • the mobile radio device receives an identification code 42 broadcast by the respective transmission unit 40 via broadcast.
  • the mobile device 24 comprises in a manner known per se a transmitting and receiving unit 52, a memory 54 and a processing unit in the form of or in the manner of a microprocessor 56.
  • the transmitting and receiving unit 52 is here - simplified schematically - as a single Function unit shown. In any case, the transmitting and receiving unit 52 is set up to transmit and receive data according to the respective mobile radio standard and to receive data from the transmitting units 40 according to the data transmission method used by them in each case.
  • an actual implementation of such a transmitting and receiving unit 52 may comprise a plurality of functional units, for example a functional unit for transmitting and receiving data according to the respective mobile radio standard and one or more further functional units for transmitting and receiving Bluetooth data, ZigBee data, etc.
  • An identification code 42 received by a transmitting unit 40 is evaluated by a software application 58 loaded into the memory 54 of the mobile radio device 24 in a manner known per se.
  • the software application 58 is, in a known manner, a computer program with program code instructions included therein.
  • the mobile device 24 sends the received identification code 42 via the respective mobile radio network and the Internet 26 to the server 28.
  • the server 28 so a server program running there, checks whether the thus obtained identification code 42 is valid. For this purpose, at least the identification code prefix 44 and the message authentication code 50 are evaluated.
  • the identification code prefix 44 encompassed by the identification code 42 can be chosen largely arbitrarily when programming or configuring the transmitting units 40 and is intended to ensure at least that the server 28 recognizes an identification code 42 that is relevant there as relevant payload data and if necessary also receives it from others at the server 28 User data are distinguishable.
  • the server 28 sends on receipt of a valid identification code 42, the associated elevator-specific information to the respective mobile device 24 back.
  • the server compares the elevator system identifier 46 comprised by the identification code 42 with the elevator system identifier 32 of the elevator system data records 30 stored in its memory. Once a match is found, the data comprised by the respective elevator system data record 30 or the elevator system data record 30 can altogether be referred to as elevator-specific information Mobile device 24 are transmitted.
  • the server 28 thus comprises means for retrievably storing at least one elevator installation data record 30 received from an elevator control device 16 and means for determining an elevator installation data record 30 matching a received identification code 42 and means for transmitting such a suitable elevator system data record 30 to a mobile radio device 24.
  • means for the retrievable Storage of one or more elevator installation data records 30 includes storage in the form of a hardware memory and / or in the form of conventional memory devices (hard disk and the like) as well as software functionality for managing the memory contents and for accessing the memory contents.
  • a software functionality running on the server 28 side is considered, which compares the elevator system identifier 46 with the elevator system identifier 32 of the or each elevator system data record stored on the server 28 side 30 is determined and set up.
  • the server 28 is connected, for example, to the Internet 26 and via the Internet 26 to the mobile radio network in which the mobile radio device 24 can be reached.
  • the server 28 transmits to the mobile radio device 24 the respectively associated elevator system data record 30 originally received by the elevator control device 16.
  • the data actually transmitted to the mobile device 24 may also include additional information and correspondingly go beyond the data of the original elevator system record 30. All of this is intended to be encompassed by the use of the term elevator installation data record 30, insofar as an elevator installation data record 30 transmitted from the server 28 to the mobile radio device 24 is meant to be read.
  • the data transmitted by the server 28 to the mobile radio device 24 in the form of the elevator installation data record 30 can also be filtered on the server 28 side using the floor identifier 48 covered by the identification code 42, for example if an elevator installation 10 with several elevator cars 14 on the one by the Floor identifier 48 designated floor 18 on which the user is currently located, individual elevator cars 14 are not usable.
  • the software application 58 and after receipt of the elevator installation data record 30 from the server 28 it can be displayed on the display (screen) of the mobile radio device 24 on which floor 18 the user is located.
  • Such a display is basically - also under the control of the software application 58 - already possible after receipt of the identification code 42 from one of the transmission units 40. If the display of the floor number on the display of the mobile device 24 is only on the receipt of the elevator installation record 30 from the server 28, the display of the floor number on the display of the mobile device 24 for the user is already a response that successful communication with the elevator system 10 occurred Has.
  • Such an operator action is, for example, a drive request.
  • a travel request for example, from the floor with the number 5 (start floor) to the floor with the number 2 (destination floor) by means of the software application 58
  • a travel request telegram 60 (FIG. 5) automatically generated by the software application 58 (FIG. Fig. 5 . Fig. 6 ; first travel request telegram 60) is sent to the server 28.
  • the representation in FIG. 6 shows that the server 28 in turn sends a corresponding travel request telegram 62 (second travel request telegram 62) to the elevator control device 16 after receiving such a travel request telegram 60.
  • the server 28 is connected, for example, in a manner known per se to the Internet 26, with the mobile telephony device 24 originating travel message 60 initially via the respective mobile radio network in FIG Internet 26 is transmitted and via the Internet 26 reaches the server 28 and wherein the travel request telegram 62 sent by the server 28 reaches the elevator control device 16 via the Internet 26.
  • the illustrations in FIG. 7 and FIG. 8 show in a schematically simplified form a possible layout of such travel request telegrams 60, 62.
  • the sent by the mobile device 24 to the server 28 travel request telegram 60 includes at least one specification of the respective destination floor (destination floor specification 64).
  • a specification of the respective destination floor is basically sufficient here, since the start floor, ie the floor on which the user is located, is already known on the server side from the previous transmission of the identification code.
  • the travel query telegram 62 sent by the server 28 to the elevator control device 16 comprises at least one specification of the respective start floor (start floor specification 66) and the respective destination floor specification 64.
  • the elevator controller 16 at a given time executes the travel thus specified by means of the travel request telegram 62, that is, the travel information.
  • the elevator control device 16 moves the elevator car 14 to the floor 18 on which the user is located and conveys the user to the destination floor after entering the elevator car 14.
  • the elevator control device 16 can execute the travel request in accordance with the travel request telegram 62, it is preferably provided-but fundamentally optional-that the elevator control device 16 automatically generates and sends an acknowledgment telegram (not shown) to the server 28.
  • the server 28 forwards such an acknowledgment telegram to that mobile radio device 24 which has initiated the travel request underlying the travel request telegram 62.
  • the user can be informed via the user interface of the software application 58 of his mobile device 24 that his travel request can now be fulfilled.
  • the data that can be transmitted to mobile device 24 in this way can also go beyond a simple provision message and contain, for example, information with which elevator car 14 the travel request is to be processed, so that the user is informed by means of the user interface of software application 58 which elevator car 14 to use.
  • the data telegrams exchanged between the mobile radio device 24 and the server 28 on the one hand and the server 28 and the elevator control device 16 on the other hand ie in particular the travel request telegrams 60, 62
  • these each comprise an identifier in the manner of the elevator system identifier 32, 46 and / or secured in any other way.
  • floors 18, which require special authorization are not even displayed by the software application 58 of the mobile radio device 24 if, by means of the travel request telegram 60 or in connection with the transmission of the travel request telegram 60, none with a corresponding authorization for single or all floors 18 connected user ID is transmitted.
  • Such a limited display of certain floors 18 by the user interface shown by the software application 58 can be ensured by transmitting correspondingly limited data from the server 28 to the software application 58 of the mobile device 24, for example by the server 28 to the mobile device 24 in a response message (not shown) on the receipt of the travel query telegram 60 a list of the according to the transmitted user ID accessible floors 18 transmitted.
  • Accessible and inaccessible floors 18 as well as possibly an authorization and the like for a not readily accessible floor 18 authorization and the like can be stored on the server 28 in its database and / or the server 28 by the elevator control device 16 with the elevator installation record 30 or in connection with Transmission of the elevator installation data record 30 communicated.
  • the communicative connection between the server 28 and the elevator control device 16 is preferred, but in a fundamentally optional manner, particularly safe remplistal tet.
  • Known encryption and security mechanisms for securing the communication between the server 28 and the elevator control device 16 are considered here, for example SSL, TSL, HTTPS, VPN and the like.
  • the software application 58 allows the use of predefined or predefinable user profiles loaded into the memory 54 of the mobile radio device 24.
  • a user profile may target the request of a wheelchair accessible elevator car 14, the request of a VIP elevator car 14, extended floor and car door opening times, visual and / or audible reproduction of specific media and the like in the elevator car 14, and so on .
  • Due to such a user profile corresponding data, for example as part of the travel request telegram 60 are sent to the server 28 in connection with a travel request by the user by means of the software application 58.
  • the server 28 checks the data thus obtained and forwards it to the elevator control device 16, for example as additional user data in the travel request telegram 62.
  • the software application 58 together with a specification of a travel request, that is, at least the selection of a destination floor, can offer further selection options by means of the user interface, so that the user can specify or parameterize the respective travel request more precisely. This makes it possible, for example, for the user to request a disabled-accessible elevator to fulfill his / her travel request and / or for the user to order the reproduction of a specific audio and / or video sequence for his / her travel request.
  • the user can already make the specification of a travel request before it is physically located in the vicinity of the elevator installation 10. Then the user makes the specification of the respective destination floor, for example, when he is still at his workplace and selects as a destination floor, for example, the floor 18, in which an underground car park is located.
  • the above-described data exchange with the server 28 and the elevator control device 16 takes place, whereby it is recognized by the software application 58 running on the mobile device 24 that already has one Ride request is present and the software application 58 automatically generates a travel request telegram 60 as soon as the identification code 42 has been received by a transmitting unit 40 and thus the data necessary for communication with the server 28 is present.
  • the user can store a generic drive request in the mobile device 24, which is transmitted to the remote server 28 as soon as the mobile device 24 moves into reception range of any, especially previously indefinite, transmission unit 40.
  • the start floor can thus be determined dynamically by the identification code received as the first after activation of the generic drive request.
  • Activation of the generic drive request can also be timed, z. B. every working day at 17.00 clock, and / or locally, for. B. by approaching the GPS position of the elevator location done.
  • FIG. 9 finally shows from left to right snapshots of the user interface shown by the software application 58 on the display of the mobile device 24 when using the mobile device 24 in the context of the approach described here.
  • the illustration at the top left is a possibility for a representation as it takes place when the mobile device 24 is outside the transmission range of at least one transmission unit 40.
  • the software application 58 looks to a certain extent a building in which an elevator installation 10 is located, to which access is possible by means of the software application 58 in the manner described above.
  • the software application 58 has received an identification code 42 from a transmitting unit 40 and, if necessary, also transmitted this to the remote server 28 and received the elevator installation data record 30 from this.
  • a clear text display of a designation of a respective building in this case "Lucerne main station”, can in principle already take place on the basis of the receipt of the identification code 42 from a transmission unit 40.
  • an illustration of the respective floor 18 can already be made, on which the user is located with his mobile radio device 24, here "ground floor”.
  • it is provided that such displays only take place when the software application 58 has received the elevator installation data record 30 from the server 28. It is then ensured that the server 28 has checked the transmitted identification code 42 and that the identification code 42 is a permissible identification code 42.
  • the illustration on the bottom left is a way to design the user interface when selecting the destination floor by the user. Based on such a selection, the software application 58 generates the travel request telegram 60.
  • the illustration at the bottom right shows a possibility for designing the user interface to indicate that the travel request given by the user can now be fulfilled and, in the illustrated example, also includes information regarding the elevator car 14 to be used, here one designated by the letter "B" Elevator car 14.

Landscapes

  • Engineering & Computer Science (AREA)
  • Automation & Control Theory (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Elevator Control (AREA)
  • Indicating And Signalling Devices For Elevators (AREA)
EP15704299.5A 2014-02-13 2015-02-11 Verfahren zum betrieb einer aufzugsanlage, aufzugsteuerungseinrichtung und mobilfunkgerät zur ausführung des verfahrens sowie system mit einer solchen aufzugsteuerungseinrichtung und einem mobilfunkgerät Active EP3105159B1 (de)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PL15704299T PL3105159T3 (pl) 2014-02-13 2015-02-11 Sposób eksploatacji instalacji dźwigowej, urządzenie sterujące dźwigiem oraz urządzenie telefonii komórkowej do realizacji sposobu, jak również system z takim urządzeniem sterującym dźwigiem oraz urządzeniem telefonii komórkowej

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
EP14155095 2014-02-13
PCT/EP2015/052853 WO2015121294A1 (de) 2014-02-13 2015-02-11 Verfahren zum betrieb einer aufzugsanlage, aufzugsteuerungseinrichtung und mobilfunkgerät zur ausführung des verfahrens sowie system mit einer solchen aufzugsteuerungseinrichtung und einem mobilfunkgerät

Publications (2)

Publication Number Publication Date
EP3105159A1 EP3105159A1 (de) 2016-12-21
EP3105159B1 true EP3105159B1 (de) 2018-05-09

Family

ID=50073076

Family Applications (1)

Application Number Title Priority Date Filing Date
EP15704299.5A Active EP3105159B1 (de) 2014-02-13 2015-02-11 Verfahren zum betrieb einer aufzugsanlage, aufzugsteuerungseinrichtung und mobilfunkgerät zur ausführung des verfahrens sowie system mit einer solchen aufzugsteuerungseinrichtung und einem mobilfunkgerät

Country Status (11)

Country Link
US (1) US10836604B2 (ru)
EP (1) EP3105159B1 (ru)
CN (1) CN105980285B (ru)
AU (1) AU2015217692C1 (ru)
BR (1) BR112016018293B1 (ru)
CA (1) CA2939142C (ru)
ES (1) ES2673273T3 (ru)
HK (1) HK1223901A1 (ru)
PL (1) PL3105159T3 (ru)
PT (1) PT3105159T (ru)
WO (1) WO2015121294A1 (ru)

Families Citing this family (31)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
BR112016018293B1 (pt) 2014-02-13 2023-03-21 Inventio Ag Processo para a operação de um equipamento de elevador, dispositivo de controle de elevador e sistema com um dispositivo de controle de elevador
WO2016089932A1 (en) * 2014-12-02 2016-06-09 Otis Elevator Company Method and system for indoor wayfinding based on elevator information
WO2017079675A1 (en) * 2015-11-06 2017-05-11 Otis Elevator Company Locating elevator systems
CN108473281B (zh) 2015-12-22 2021-08-06 奥的斯电梯公司 使用用户装置的电梯服务请求
AU2016277598A1 (en) * 2015-12-22 2017-07-06 Otis Elevator Company User-customized elevator floor selection
TW201724000A (zh) * 2015-12-29 2017-07-01 鴻海精密工業股份有限公司 電梯自動導引輔助系統及引導方法
US10087046B2 (en) * 2016-10-12 2018-10-02 Otis Elevator Company Intelligent building system for altering elevator operation based upon passenger identification
US20180118511A1 (en) * 2016-10-28 2018-05-03 Otis Elevator Company Elevator service request using user device
US10486938B2 (en) 2016-10-28 2019-11-26 Otis Elevator Company Elevator service request using user device
US10597254B2 (en) 2017-03-30 2020-03-24 Otis Elevator Company Automated conveyance system maintenance
US10647544B2 (en) * 2017-06-05 2020-05-12 Otis Elevator Company Elevator notifications on mobile device associated with user identification device
DE102017213405A1 (de) * 2017-08-02 2019-02-07 Franz Xaver Meiller Fahrzeug- Und Maschinenfabrik - Gmbh & Co Kg Aufzugsystem
US11095502B2 (en) * 2017-11-03 2021-08-17 Otis Elevator Company Adhoc protocol for commissioning connected devices in the field
US10875742B2 (en) 2017-11-09 2020-12-29 Otis Elevator Company Elevator service request using user device with filtered destination floor selection
CN109867176B (zh) * 2017-12-05 2023-02-21 奥的斯电梯公司 楼层信息的自动获取
CN110182660B (zh) * 2018-02-23 2022-03-25 东芝电梯株式会社 电梯系统
US11040849B2 (en) * 2018-02-28 2021-06-22 Otis Elevator Company Method for blocking and filtering false automatic elevator calls
CN110228733B (zh) 2018-03-06 2022-08-09 奥的斯电梯公司 电梯服务请求的授权管理和授权请求
US10988345B2 (en) 2018-03-20 2021-04-27 Otis Elevator Company Direct real-time travel indications for multi-segment trip
CN110407043B (zh) * 2018-04-26 2023-01-13 奥的斯电梯公司 用于电梯服务请求的通信
CN110467070B (zh) * 2018-05-11 2023-10-10 奥的斯电梯公司 基于社交媒体应用组件的电梯服务请求
CN111039115A (zh) 2018-10-15 2020-04-21 奥的斯电梯公司 用于监控电梯通信模块故障的方法、系统以及电梯
CN111071873A (zh) * 2018-10-22 2020-04-28 奥的斯电梯公司 基于与电梯大厅的接近度对远程电梯呼叫服务设定优先级的系统和方法
CN111091644B (zh) 2018-10-24 2022-12-13 奥的斯电梯公司 电梯服务请求的授权管理和授权请求
US11472666B2 (en) * 2019-04-05 2022-10-18 Otis Elevator Company Elevator maintenance app matching mechanics position with faults detected
US12049382B2 (en) * 2019-04-11 2024-07-30 Otis Elevator Company Management of elevator service
TWI839507B (zh) * 2019-05-07 2024-04-21 瑞士商伊文修股份有限公司 用於記錄並處理現有電梯設備的電梯資料之方法
CN112027836A (zh) * 2019-06-04 2020-12-04 奥的斯电梯公司 电梯轿厢的位置信息的获取
CN115667111A (zh) 2020-05-18 2023-01-31 因温特奥股份公司 用于操作电梯系统的方法和用于操作电梯装置的系统
CN112456262A (zh) * 2020-10-22 2021-03-09 日立楼宇技术（广州）有限公司 一种自动召梯方法、系统、设备及存储介质
CN115159283B (zh) * 2022-07-14 2024-02-06 大连奥远电子股份有限公司 一种楼宇垂直电梯等梯信息管理系统

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2006000618A2 (en) 2004-06-28 2006-01-05 Kone Corporation Elevator arrangement
US20060144644A1 (en) 2004-04-07 2006-07-06 Yuji Chiba Elevator call registration system
US20070131487A1 (en) 2004-06-28 2007-06-14 Kone Corporation Elevator arrangement
WO2014116182A1 (en) 2013-01-25 2014-07-31 Hitachi Elevator Asia Pte Ltd System, device and method for controlling lift access and computer-readable medium storing computer-readable program for lift access

Family Cites Families (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
ATE232503T1 (de) * 1997-05-22 2003-02-15 Inventio Ag Eingabegerät und verfahren zur akustischen befehlseingabe für eine aufzugsanlage
JP2003531792A (ja) * 2000-05-01 2003-10-28 インベンテイオ・アクテイエンゲゼルシヤフト エレベータの制御方法
EP1749775A1 (de) 2005-07-28 2007-02-07 Inventio Ag Verfahren zum Transport eines Benutzers mit einem Transportmittel, insbesondere mit einem Aufzug
EP2011102B1 (en) * 2006-04-21 2011-10-12 Tac AB Product, device and system for controlling physical properties
US7823700B2 (en) * 2007-07-20 2010-11-02 International Business Machines Corporation User identification enabled elevator control method and system
US8646579B2 (en) * 2008-04-29 2014-02-11 Inventio Ag Circuit board coupling elevator call control to signal bus
EP2208701A1 (de) * 2009-01-16 2010-07-21 Inventio Ag Verfahren zur Steuerung einer Aufzugsanlage
CN202602625U (zh) * 2012-05-16 2012-12-12 上海宇诺电气技术有限公司 智能无线呼叫系统
BR112016018293B1 (pt) 2014-02-13 2023-03-21 Inventio Ag Processo para a operação de um equipamento de elevador, dispositivo de controle de elevador e sistema com um dispositivo de controle de elevador

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20060144644A1 (en) 2004-04-07 2006-07-06 Yuji Chiba Elevator call registration system
WO2006000618A2 (en) 2004-06-28 2006-01-05 Kone Corporation Elevator arrangement
US20070131487A1 (en) 2004-06-28 2007-06-14 Kone Corporation Elevator arrangement
WO2014116182A1 (en) 2013-01-25 2014-07-31 Hitachi Elevator Asia Pte Ltd System, device and method for controlling lift access and computer-readable medium storing computer-readable program for lift access

Also Published As

Publication number Publication date
WO2015121294A1 (de) 2015-08-20
PL3105159T3 (pl) 2018-10-31
EP3105159A1 (de) 2016-12-21
CA2939142C (en) 2019-01-08
US20160376124A1 (en) 2016-12-29
AU2015217692C1 (en) 2018-01-25
AU2015217692A1 (en) 2016-09-01
HK1223901A1 (zh) 2017-08-11
BR112016018293A2 (ru) 2017-08-08
CN105980285A (zh) 2016-09-28
BR112016018293B1 (pt) 2023-03-21
CN105980285B (zh) 2017-12-05
AU2015217692B2 (en) 2017-10-12
PT3105159T (pt) 2018-08-10
US10836604B2 (en) 2020-11-17
ES2673273T3 (es) 2018-06-21
CA2939142A1 (en) 2015-08-20

Similar Documents

Publication Publication Date Title
EP3105159B1 (de) Verfahren zum betrieb einer aufzugsanlage, aufzugsteuerungseinrichtung und mobilfunkgerät zur ausführung des verfahrens sowie system mit einer solchen aufzugsteuerungseinrichtung und einem mobilfunkgerät
EP3307666B1 (de) Aufzugsystem mit prädiktiver ruferzeugung
EP3542350B1 (de) Zugangskontrollsystem mit automatischer statusaktualisierung
DE102015013318B4 (de) Verfahren zur Entfernung eines Kraftfahrzeugs von einer Zielfläche, Kommunikationssystem und Kraftfahrzeug
EP3365211B1 (de) Verfahren und vorrichtung zum verringern eines kollisionsrisikos einer kollision eines kraftfahrzeugs mit einem objekt
EP3212554B1 (de) System und verfahren zur wahrung der privatsphäre von personen in aufzugssystemen
EP3212487B1 (de) Verfahren und vorrichtung zum betreiben eines fahrzeugs
EP2691940B1 (de) Verwaltung von zugriffsrechten auf betriebs- und/oder steuerungsdaten von gebäuden oder gebäudekomplexen
DE102018211776A1 (de) Aufzugsteuerungs- und überwachungssystem
WO2015018741A1 (de) Kommunikationsverfahren für eine aufzugsanlage
DE102013213379A1 (de) Vorrichtung und Verfahren zur Unterstützung eines Fahrers beim Ein- und Ausparken seines Fahrzeugs in einer Parkeinrichtung
DE112018003983T5 (de) Türantrieb
EP2912856B1 (de) System und verfahren zur datenschutzkonformen erfassung und weiterleitung von telemetriedaten
DE102014224101A1 (de) Verfahren und Vorrichtung zum Betreiben eines Parkplatzes
DE112017007632B4 (de) Aufzugsbetrieb-steuervorrichtung, aufzugsbetrieb-steuerverfahren und aufzugsbetrieb-steuerprogamm
EP3634897B1 (de) Aufzugssystem mit besucherbetriebsmodus
WO2016083027A1 (de) Verfahren zum überwachen eines parkplatzes
DE102018202481B3 (de) Verfahren zur Bereitstellung eines Kraftfahrzeugs für eine Servicedienstleistung und Dienstleistungsumgebung
EP3015412A1 (de) Bedienung eines aufzugs mittels touchscreen
EP3680205A1 (de) System zum transport eines benutzers mit einem aufzug zu einem ziel, nachrüstsatz und verfahren
EP3902759B1 (de) Verfahren und vorrichtung zum kommissionieren einer personentransportanlage
EP3798171B1 (de) Steuerung für eine aufzugsanlage
DE102017205211A1 (de) Verfahren zum Betrieb eines automatisierten Kraftfahrzeugs und Kraftfahrzeug
EP3947235A1 (de) Automatisiert gesteuerte türanordnung als stockwerktür einer aufzuganlage
DE102019004718A1 (de) Verfahren zur Handhabung einer Notfallsituation

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: REQUEST FOR EXAMINATION WAS MADE

17P Request for examination filed

Effective date: 20160810

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

AX Request for extension of the european patent

Extension state: BA ME

DAX Request for extension of the european patent (deleted)
GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: GRANT OF PATENT IS INTENDED

INTG Intention to grant announced

Effective date: 20171130

GRAS Grant fee paid

Free format text: ORIGINAL CODE: EPIDOSNIGR3

GRAA (expected) grant

Free format text: ORIGINAL CODE: 0009210

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE PATENT HAS BEEN GRANTED

AK Designated contracting states

Kind code of ref document: B1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

REG Reference to a national code

Ref country code: GB

Ref legal event code: FG4D

Free format text: NOT ENGLISH

REG Reference to a national code

Ref country code: CH

Ref legal event code: EP

Ref country code: AT

Ref legal event code: REF

Ref document number: 997414

Country of ref document: AT

Kind code of ref document: T

Effective date: 20180515

REG Reference to a national code

Ref country code: DE

Ref legal event code: R096

Ref document number: 502015004192

Country of ref document: DE

Ref country code: IE

Ref legal event code: FG4D

Free format text: LANGUAGE OF EP DOCUMENT: GERMAN

REG Reference to a national code

Ref country code: ES

Ref legal event code: FG2A

Ref document number: 2673273

Country of ref document: ES

Kind code of ref document: T3

Effective date: 20180621

REG Reference to a national code

Ref country code: NL

Ref legal event code: FP

REG Reference to a national code

Ref country code: PT

Ref legal event code: SC4A

Ref document number: 3105159

Country of ref document: PT

Date of ref document: 20180810

Kind code of ref document: T

Free format text: AVAILABILITY OF NATIONAL TRANSLATION

Effective date: 20180802

REG Reference to a national code

Ref country code: SE

Ref legal event code: TRGR

REG Reference to a national code

Ref country code: LT

Ref legal event code: MG4D

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: NO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180809

Ref country code: BG

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180809

Ref country code: LT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180509

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: LV

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180509

Ref country code: HR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180509

Ref country code: RS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180509

Ref country code: GR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180810

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: DK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180509

Ref country code: EE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180509

Ref country code: RO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180509

Ref country code: CZ

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180509

Ref country code: SK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180509

REG Reference to a national code

Ref country code: DE

Ref legal event code: R026

Ref document number: 502015004192

Country of ref document: DE

PLBI Opposition filed

Free format text: ORIGINAL CODE: 0009260

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SM

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180509

PLAX Notice of opposition and request to file observation + time limit sent

Free format text: ORIGINAL CODE: EPIDOSNOBS2

26 Opposition filed

Opponent name: OTIS ELEVATOR COMPANY

Effective date: 20190208

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: IT

Payment date: 20181220

Year of fee payment: 10

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180509

PLBB Reply of patent proprietor to notice(s) of opposition received

Free format text: ORIGINAL CODE: EPIDOSNOBS3

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MC

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180509

REG Reference to a national code

Ref country code: IE

Ref legal event code: MM4A

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: AL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180509

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: IE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20190211

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180509

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: LU

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20200211

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: CY

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180509

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: IS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180909

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: HU

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT; INVALID AB INITIO

Effective date: 20150211

PLCK Communication despatched that opposition was rejected

Free format text: ORIGINAL CODE: EPIDOSNREJ1

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: FI

Payment date: 20220216

Year of fee payment: 8

Ref country code: AT

Payment date: 20220216

Year of fee payment: 8

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: SE

Payment date: 20220218

Year of fee payment: 8

Ref country code: PT

Payment date: 20220128

Year of fee payment: 8

Ref country code: PL

Payment date: 20220131

Year of fee payment: 8

Ref country code: NL

Payment date: 20220224

Year of fee payment: 8

Ref country code: BE

Payment date: 20220224

Year of fee payment: 8

APBM Appeal reference recorded

Free format text: ORIGINAL CODE: EPIDOSNREFNO

APBP Date of receipt of notice of appeal recorded

Free format text: ORIGINAL CODE: EPIDOSNNOA2O

APAH Appeal reference modified

Free format text: ORIGINAL CODE: EPIDOSCREFNO

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180509

APBQ Date of receipt of statement of grounds of appeal recorded

Free format text: ORIGINAL CODE: EPIDOSNNOA3O

RAP4 Party data changed (patent owner data changed or rights of a patent transferred)

Owner name: INVENTIO AG

P01 Opt-out of the competence of the unified patent court (upc) registered

Effective date: 20230520

APAH Appeal reference modified

Free format text: ORIGINAL CODE: EPIDOSCREFNO

REG Reference to a national code

Ref country code: SE

Ref legal event code: EUG

REG Reference to a national code

Ref country code: NL

Ref legal event code: MM

Effective date: 20230301

REG Reference to a national code

Ref country code: AT

Ref legal event code: MM01

Ref document number: 997414

Country of ref document: AT

Kind code of ref document: T

Effective date: 20230211

REG Reference to a national code

Ref country code: BE

Ref legal event code: MM

Effective date: 20230228

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20230212

Ref country code: PT

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20230811

Ref country code: FI

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20230211

Ref country code: AT

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20230211

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: NL

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20230301

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: BE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20230228

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: ES

Payment date: 20240307

Year of fee payment: 10

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: DE

Payment date: 20240228

Year of fee payment: 10

Ref country code: GB

Payment date: 20240220

Year of fee payment: 10

Ref country code: CH

Payment date: 20240301

Year of fee payment: 10

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: TR

Payment date: 20240130

Year of fee payment: 10

Ref country code: IT

Payment date: 20240222

Year of fee payment: 10

Ref country code: FR

Payment date: 20240226

Year of fee payment: 10

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: PL

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20230211

APBU Appeal procedure closed

Free format text: ORIGINAL CODE: EPIDOSNNOA9O

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: PL

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20230211

APAN Information on closure of appeal procedure modified

Free format text: ORIGINAL CODE: EPIDOSCNOA9O