EP3105159B2 - 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
EP3105159B2
EP3105159B2 EP15704299.5A EP15704299A EP3105159B2 EP 3105159 B2 EP3105159 B2 EP 3105159B2 EP 15704299 A EP15704299 A EP 15704299A EP 3105159 B2 EP3105159 B2 EP 3105159B2
Authority
EP
European Patent Office
Prior art keywords
elevator system
elevator
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
EP3105159B1 (de
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(B2) "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
Publication of EP3105159B2 publication Critical patent/EP3105159B2/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 primarily relates to a method for operating an elevator system. Furthermore, the invention also relates to an elevator control device and a mobile radio device for carrying out the method and to a system with such an elevator control device and such a mobile radio device.
  • the basic principles of operating an elevator system using an elevator control device are known per se. If a user wants to travel from one floor (starting floor) to another floor (destination floor), he or she operates a control panel assigned to the elevator system on the respective starting floor, thereby initiating a so-called floor call, which is processed by the elevator control device. If the elevator car or an elevator car of the elevator system becomes available or passes the floor on which the floor call was triggered without any particular restrictions during a current movement process, the elevator control device causes the elevator car to move to the respective floor and/or to stop the car on the respective floor. When the user enters the elevator car, he or she selects a destination floor on a control panel in the elevator car, thereby initiating a car call on the elevator control device. The elevator car is then moved to the destination floor specified in this way. If necessary, other previously specified destination floors may be approached or the elevator car may stop on a floor between the current floor and the destination floor due to a car or floor call.
  • such an identification code is used in such a way that the identification code is received by means of a mobile radio device, that a travel request is specified by means of a software application running on the mobile radio device, that the travel request is transmitted using the floor-specific identification code or possibly using the floor-specific and elevator system-specific identification code in the form of a first travel request telegram to a remote server, in particular one that can be reached on the Internet, and that the server forwards the travel request to the elevator system in the form of a second travel request telegram.
  • the mobile device and the software application running on it especially a user interface displayed by means of the software application, function like a conventional control panel of the elevator system, namely, for example, like a conventional floor control panel.
  • the travel request telegram associated with the travel request specified 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 system-specific identification code. Because the identification code is at least floor-specific, the travel request telegram includes data on the floor on which the user of the mobile device will begin using the elevator system.
  • the travel request is transmitted by the server to the elevator system, for example, to an elevator control device of the respective elevator system or to a unit acting as an interface to the elevator control device.
  • the advantage of the invention is that the mobile device with a software application running on it and designed to carry out the method can be used instead of the usual control panels of the elevator system and that additional functions and/or information are available.
  • the user of the mobile device does not need to specify the respective starting floor for his or her desired journey, because information about the starting floor is already contained in the floor-specific identification code received by a transmitting unit. Incorrect entries are prevented in this way.
  • the identification code comprises at least one elevator system identifier and the elevator system sends an elevator system data record to the remote server, which comprises elevator system-specific data, such as an elevator system identifier.
  • the software application of the mobile device sends a received identification code to the server.
  • the server Upon receipt of the elevator system identifier, the server searches for an elevator system data record with a matching elevator system identifier. If successful, i.e. if an elevator system data record matching the received elevator system identifier could be determined, the server sends the elevator system data record to the mobile device.
  • the mobile device and the software application running on it therefore receive the elevator-specific information contained in the elevator data set, such as the number of floors that can be reached with the elevator.
  • the elevator-specific information contained in the elevator data set such as the number of floors that can be reached with the elevator.
  • At least some of the data included in the identification code and/or the elevator system data set are displayed graphically or in some other way using a user interface generated by the software application. Because the identification code is floor-specific, the user of the mobile device can be informed, for example, about which floor he is currently on in the respective building when the data included in the identification code is displayed.
  • the elevator system-specific data in the elevator system data set can be used to display the floors that can be reached with the elevator system and/or to display further information about the respective building.
  • the server receiving the identification code can distinguish data telegrams comprising the identification code prefix from other data telegrams by means of the identification code prefix.
  • the identification code comprises a telegram or message authentication code, in particular a telegram 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 telegram containing the identification code has not been falsified on the way to the server, thus precluding misuse.
  • the above-mentioned object is also achieved with an elevator control device and a mobile radio device, which are intended and set up to carry out the elevator system-side or mobile radio device-side part of the method.
  • the invention is preferably implemented in software.
  • FIG. 1 shows a simplified schematic of an elevator system 10 in a building (not shown) with 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 in the building.
  • the elevator control device 16 is provided in a manner known per se for controlling the elevator system 10.
  • 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.
  • a person referred to here and below as the user, who wants to use an elevator car 14 of the elevator system 10 to get from a starting floor to a destination floor.
  • the user carries a mobile phone 24 with him.
  • the mobile phone 24 can be communicatively connected to a mobile network and the Internet 26 in a manner known per se and is connected when used within the framework of the approach proposed here.
  • a connection to an external server 28, for example a server 28 of the manufacturer or operator of the elevator system 10, can be established via the Internet 26.
  • the elevator control device 16 or another device (not shown) connected to the elevator control device 16 at the location of the elevator system 10 by cable or wirelessly is itself connected by cable or wirelessly to the Internet 26 and to the server 28 via the Internet 26.
  • the following description is continued - without sacrificing further general validity - using the example of an elevator control device 16 connected directly to the server 28 via the Internet 26, i.e. without the interposition of another device.
  • the possibility of interposing such a device is nevertheless always mentioned below. If such a unit is present, it partially replaces the elevator control device 16 in the method described below.
  • the following options in particular come into consideration for wireless or wired connection to the Internet 26: LAN, WLAN/WiFi, PSTN, 2G, 3G, LTE, GPRS, etc.
  • the elevator control device 16 After commissioning of the elevator system 10, after completion of maintenance of the elevator system 10 or according to additional or alternative predetermined or predeterminable rules (once a day, once a month, in the event of malfunctions, when replacing components, etc.), the elevator control device 16 sends an elevator system data record 30 describing the elevator system 10 to the server 28 in a data telegram (hereinafter referred to as a telegram).
  • the elevator system data record 30 is stored on the server 28 in a database provided for this purpose (not shown separately) and can be retrieved from this database on the server 28.
  • the representation in Figure 3 shows a possible layout of the elevator installation data set 30 and individual data included in the elevator installation data set 30 according to the approach proposed here.
  • This data includes an elevator installation identifier 32 that uniquely identifies the respective elevator installation 10, which is stored in Figure 3 symbolically and exemplarily indicated as "200971".
  • the data additionally included in the elevator system data record 30 describe the elevator system 10 with further details.
  • the data includes information about the number of floors 18 (number of floors 34), the number of elevator cabins 14 (number of elevators 36) and a coded statement about the type of control (control type 38).
  • the control type 38 codes, for example, whether the respective functionality of the elevator control device 16 is a conventional control, a group control, a destination call control or a control with special functions.
  • Special functions include functions with access control options and, in addition or as an alternative, a disabled-accessible version of a travel request or a version that makes it easier for mothers or users with pushchairs, shopping trolleys, etc. to board and provides for a longer opening time of the cabin and floor doors.
  • the elevator control device 16 sends an elevator system data record 30 with an elevator system identifier 32 to the server 28.
  • the respective elevator system 10 is then known on the server 28 side and use of the elevator system 10 within the framework of the concept proposed here becomes possible.
  • the elevator control device 16 can send the above-mentioned additional elevator system-specific data 34, 36, 38 together with the elevator system identifier 32 in the elevator system data record 30.
  • the transmitting units 40 are not necessarily connected to the elevator control device 16. However, the transmitting units 40 are always spatially assigned to the elevator system 10 and are installed, for example, near the floor doors (on the walls or on the floor ceiling).
  • the transmitting units 40 continuously transmit a floor-specific identification code 42 in the form of a so-called broadcast, i.e. regularly at predetermined or predeterminable times, for example every second. Because the identification code 42 is transmitted as a broadcast, every mobile device 24 located in the transmission range of a transmitting unit 40 can receive the identification code 42.
  • the range of the transmitting units 40 is in a range of 4-10 meters, depending on the respective requirements. In other building topologies, i.e.
  • a greater range can also be provided, as long as it is guaranteed that an identification code 42 sent by a transmitting unit 40 on a first floor 18 can only be received on this floor 18 and not on another floor 18.
  • the transmitting units 40 send the identification code 42 by means of WLAN/WiFi, WPNA, via Bluetooth or ZigBee or according to known or future methods for data transmission between devices over short distances using radio technology. In principle, data transmission according to the NFC standard is also conceivable.
  • the transmitting units 40 are connected to the elevator control device 16 via a wired or wireless communication link, it is possible to use a variable identification code 42 that is specified or at least influenced by the elevator control device 16. In this way, a user can receive additional information about the elevator system 10 on his mobile device 24 when receiving an identification code 42, for example information about whether a specific elevator is out of service. If the transmitting units 40 are independent of the elevator control device 16, they send a specified or specifiable identification code 42 that can be set for each transmitting unit 40, for example, either as part of 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 data included in the identification code 42 according to the approach proposed here.
  • This data includes an identification code prefix 44, an elevator system identifier 46 that uniquely identifies the respective elevator system 10, a floor identifier 48 and an optional telegram or message authentication code 50 provided to protect the identification code 42 against falsification.
  • the floor identifier 48 comprises either the respective floor number or a coded form of the floor number.
  • the identification code 42 comprises the floor identifier 48
  • the identification code 42 is floor-specific.
  • Figure 4 In the situation shown, the identification code 42 is floor-specific and lift-system-specific, because it includes not only the floor identifier 48 but also the lift system 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 device receives an identification code 42 broadcast by the respective transmitting unit 40.
  • the mobile radio 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 - schematically simplified - as a single functional unit shown.
  • the transmitting and receiving unit 52 is in any case set up to send 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.
  • an actual implementation of such a transmitting and receiving unit 52 can comprise several functional units, for example a functional unit for sending and receiving data according to the respective mobile radio standard and one or more further functional units for sending 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 device 24 in a manner known per se.
  • the software application 58 is, in a manner known per se, a computer program with program code instructions included therein.
  • the mobile device 24 sends the received identification code 42 to the server 28 via the respective mobile network and the Internet 26.
  • the identification code prefix 44 included in the identification code 42 can be selected largely arbitrarily when programming or configuring the transmitting units 40 and should at least ensure that the server 28 recognizes an identification code 42 received there as relevant payload data and that these can be distinguished from other payload data that may also be received by the server 28.
  • the server 28 Upon receipt of a valid identification code 42, the server 28 sends the associated elevator-specific information back to the respective mobile device 24. To do this, the server compares the elevator system identifier 46 included in the identification code 42 with the elevator system identifier 32 of the elevator system data records 30 stored in its memory. As soon as a match is found, the data included in the respective elevator system data record 30 or the elevator system data record 30 as a whole can be transmitted to the mobile device 24 as elevator-specific information.
  • the server 28 thus comprises means for the retrievable storage of at least one elevator installation data record 30 received from an elevator control device 16 as well as means for determining an elevator installation data record 30 matching a received identification code 42 and means for sending such a matching elevator installation data record 30 to a mobile radio device 24.
  • the means for the retrievable storage of one or more elevator installation data records 30 can be a memory in the form of a hardware memory and/or in the form of conventional storage devices (hard disk and the like) as well as a software functionality for managing the memory content and for accessing the memory content.
  • a means for determining an elevator system data record 30 that matches a received identification code 42 is a software functionality running on the server 28 side, which is intended and set up to compare the elevator system identifier 46 included in the identification code 42 with the elevator system identifier 32 of the or each elevator system data record 30 stored on the server 28 side.
  • the server 28 is connected, for example, to the Internet 26 and via the Internet 26 to the mobile network in which the mobile device 24 can be reached.
  • the server 28 transmits the respective associated elevator system data record 30 originally received from the elevator control device 16 to the mobile device 24 in response to a valid identification code 42 received from a mobile device 24.
  • the server 28 transmits the respective associated elevator system data record 30 originally received from the elevator control device 16 to the mobile device 24 in response to a valid identification code 42 received from a mobile device 24.
  • only the still relevant data of the elevator system data record 30, i.e. not the elevator system identifier 32, for example, is transmitted to the mobile device 24.
  • the data actually transmitted to the mobile device 24 can also include additional information and accordingly go beyond the data of the original elevator system data record 30. All of this is to be included in the use of the term elevator system data record 30, insofar as an elevator system data record 30 transmitted from the server 28 to the mobile device 24 is meant, and is to be read accordingly in each case.
  • the data transmitted from the server 28 to the mobile device 24 in the form of the elevator system data record 30 can also be filtered on the server 28 side using the floor identifier 48 included in the identification code 42, for example if, in an elevator system 10 with several elevator cars 14, individual elevator cars 14 cannot be used on the floor 18 identified by the floor identifier 48 on which the user is currently located.
  • the display (screen) of the mobile device 24 can show which floor 18 the user is located on. Such a display is basically possible - also under the control of the software application 58 - after receiving the identification code 42 from one of the transmitting units 40.
  • the display of the floor number on the display of the mobile device 24 only occurs after the elevator system data record 30 has been received from the server 28, the display of the floor number is The user already receives feedback on the display of the mobile device 24 that successful communication with the elevator system 10 has taken place.
  • One such operating action is, for example, a travel request. If the user enters a travel request using the software application 58, for example from floor number 5 (starting floor) to floor number 2 (destination floor), a travel request telegram 60 ( Fig. 5 , Fig. 6 ; first trip request telegram 60) is sent to the server 28.
  • FIG. 6 shows that the server 28, after receiving such a travel request telegram 60, in turn sends a corresponding travel request telegram 62 (second travel request telegram 62) to the elevator control device 16.
  • the server 28 comprises means for receiving and sending such travel request telegrams 60, 62.
  • the server 28 is connected to the Internet 26, for example, in a manner known per se, wherein the travel request telegram 60 originating from the mobile radio device 24 is first transmitted to the Internet 26 via the respective mobile radio network and reaches the server 28 via the Internet 26, and wherein the travel request telegram 62 sent by the server 28 reaches the elevator control device 16 via the Internet 26.
  • the depictions in Figure 7 and Figure 8 show a possible layout of such travel request telegrams 60, 62 in a schematically simplified form.
  • the travel request telegram 60 sent from the mobile device 24 to the server 28 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, because the starting floor, i.e. the floor on which the user is located, is already known on the server 28 side from the previous transmission of the identification code 42.
  • the travel request telegram 62 sent from the server 28 to the elevator control device 16 includes at least one specification of the respective starting floor (starting floor specification 66) and the respective destination floor specification 64.
  • the elevator control device 16 carries out the journey specified in this way by means of the journey request telegram 62, i.e. the elevator control device 16 moves the elevator car 14 to the floor 18 on which the user is located and transports the user to the destination floor after entering the elevator car 14.
  • the elevator control device 16 can execute the journey request in accordance with the journey request telegram 62, it is preferably - but basically optional - provided that the elevator control device 16 automatically generates an acknowledgment telegram (not shown) and sends it to the server 28.
  • the server 28 forwards such an acknowledgment telegram back to the mobile device 24 that triggered the journey request underlying the journey request telegram 62.
  • the user can be informed via the user interface of the software application 58 of his mobile device 24 that his journey request can now be fulfilled.
  • the data that can be transmitted to the mobile device 24 in this way can also go beyond a simple availability message and, for example, include information about which elevator car 14 is to be used to process the travel request, so that the user is shown which elevator car 14 is to be used by means of the user interface of the software application 58.
  • floors 18 that require special authorization are not displayed at all by the software application 58 of the mobile device 24 if no user ID associated with a corresponding authorization for individual or all floors 18 is transmitted by means of the trip request telegram 60 or in connection with the transmission of the trip request telegram 60.
  • Such a limited display of certain floors 18 by the user interface displayed 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 a list of the floors 18 accessible according to the transmitted user ID is transmitted to the mobile radio device 24 in a response telegram (not shown) to the receipt of the travel request telegram 60.
  • Accessible and inaccessible floors 18 and, if applicable, an authorization required for a floor 18 that is not readily accessible and the like can be stored on the server 28 side in its database and/or communicated to the server 28 by the elevator control device 16 with the elevator system data record 30 or in connection with the transmission of the elevator system data record 30.
  • the communicative connection between the server 28 and the elevator control device 16 is preferably, but in a fundamentally optional manner, designed to be particularly secure.
  • Known encryption and security mechanisms for securing the communication between the server 28 and the elevator control device 16 come into consideration here, for example SSL, TSL, HTTPS, VPN and the like.
  • the software application 58 enables the use of predefined or predefinable user profiles loaded into the memory 54 of the mobile device 24.
  • a user profile can, for example, be aimed at the request of a disabled-accessible elevator car 14, the request of a VIP elevator car 14, longer opening times of the floor and car doors, optical and/or acoustic playback of special media and the like in the elevator car 14, etc.
  • corresponding data is sent to the server 28 using the software application 58, for example as part of the travel request telegram 60.
  • the server 28 checks the data thus received 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 can offer further selection options together with a specification of a travel request, i.e. at least the selection of a destination floor, using the user interface, so that the user can specify the respective travel request in more detail or additionally parameterize it. This makes it possible, for example, for the user to request a handicapped-accessible elevator to fulfill their travel request and/or for the user to order the playback of a specific audio and/or video sequence for their travel request.
  • the user can also specify a travel request before he is physically close to the elevator system 10.
  • the user specifies the respective destination floor, for example, when he is still at his workplace and selects floor 18, which has an underground car park, as the destination floor.
  • the software application 58 running on the mobile device 24 recognizing that a travel request has already been received and the software application 58 automatically generating a travel request telegram 60 as soon as the identification code 42 has been received by a transmission unit 40 and the data required for communication with the server 28 is therefore available.
  • the user can store a generic travel request in the mobile device 24, which is transmitted to the remote server 28 as soon as the mobile device 24 comes within reception range of any, in particular previously undetermined, transmitting unit 40.
  • the starting floor can thus be determined dynamically by the first identification code received after activating the generic travel request.
  • the generic travel request can also be activated at a specific time, e.g. every working day at 5 p.m., and/or at a specific location, e.g. by approaching the GPS position of the elevator location.
  • the illustration at the top left is one possible illustration of how it occurs when the mobile radio device 24 is outside the transmission range of at least one transmission unit 40.
  • the software application 58 searches for a building in which there is an elevator system 10, which can be accessed using 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 applicable, has already transmitted this to the remote server 28. and receive the elevator system data record 30 from it.
  • a plain text display of the name of a particular building, here "Lucerne - main station”, can in principle already be made based on the receipt of the identification code 42 from a transmitting unit 40.
  • a display of the respective floor 18 on which the user is located with his mobile device 24 can be made based on the receipt of the identification code 42, here "EG" for ground floor.
  • EG for ground floor.
  • it is provided that such displays only take place when the software application 58 has received the elevator system data record 30 from the server 28. This ensures 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 at the bottom left is one way of designing the user interface when the user selects the destination floor. 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 submitted by the user can now be fulfilled and, in the example shown, also includes information regarding the elevator car 14 to be used, here an elevator car 14 designated by the letter "B".
  • a method for operating an elevator system 10, an elevator control device 16 and a mobile radio device 24 for carrying out the method as well as a system with such an elevator control device 16 and a mobile radio device 24 are specified, wherein operating actions in relation to the elevator system 10 can be carried out by means of the mobile radio device 24 and wherein the mobile radio device 24 initially receives relevant data that enables indirect access to the elevator system 10 in the form of an identification code 42 that is continuously or regularly transmitted by a transmitting unit 40 assigned to the elevator system 10.

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 EP3105159B2 (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 (3)

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

Family

ID=50073076

Family Applications (1)

Application Number Title Priority Date Filing Date
EP15704299.5A Active EP3105159B2 (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 (10)

Country Link
US (1) US10836604B2 (enrdf_load_stackoverflow)
EP (1) EP3105159B2 (enrdf_load_stackoverflow)
CN (1) CN105980285B (enrdf_load_stackoverflow)
AU (1) AU2015217692C1 (enrdf_load_stackoverflow)
BR (1) BR112016018293B1 (enrdf_load_stackoverflow)
CA (1) CA2939142C (enrdf_load_stackoverflow)
ES (1) ES2673273T5 (enrdf_load_stackoverflow)
PL (1) PL3105159T3 (enrdf_load_stackoverflow)
PT (1) PT3105159T (enrdf_load_stackoverflow)
WO (1) WO2015121294A1 (enrdf_load_stackoverflow)

Families Citing this family (32)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10836604B2 (en) 2014-02-13 2020-11-17 Inventio Ag Method and system for operating elevator installation using mobile radio
EP3227218B1 (en) * 2014-12-02 2020-02-05 Otis Elevator Company Method and system for indoor wayfinding based on elevator information
US20170134894A1 (en) * 2015-11-06 2017-05-11 Otis Elevator Company System and method of locating elevator systems compatible with a mobile hall call and car call system
AU2016277598A1 (en) * 2015-12-22 2017-07-06 Otis Elevator Company User-customized elevator floor selection
AU2016377566B2 (en) 2015-12-22 2021-10-28 Otis Elevator Company Elevator service request using user device
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
US10486938B2 (en) * 2016-10-28 2019-11-26 Otis Elevator Company Elevator service request using user device
US20180118511A1 (en) * 2016-10-28 2018-05-03 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 奥的斯电梯公司 基于社交媒体应用组件的电梯服务请求
EP3856671A1 (de) * 2018-09-25 2021-08-04 Inventio AG Verfahren und aufzugsteueranordnung zum steuern eines wartungsmodus einer aufzuganlage
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 奥的斯电梯公司 电梯轿厢的位置信息的获取
AU2021275380B2 (en) 2020-05-18 2024-10-03 Inventio Ag Method for operating an elevator system, and system for operating elevator installation
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
DE59807151D1 (de) * 1997-05-22 2003-03-20 Inventio Ag Eingabegerät und Verfahren zur akustischen Befehlseingabe für eine Aufzugsanlage
AU2001248213B2 (en) 2000-05-01 2006-08-03 Inventio Ag Method for controlling an elevator
EP1749775A1 (de) 2005-07-28 2007-02-07 Inventio Ag Verfahren zum Transport eines Benutzers mit einem Transportmittel, insbesondere mit einem Aufzug
WO2007121911A1 (en) * 2006-04-21 2007-11-01 Tac Ab Product, device, and system for controlling
US7823700B2 (en) * 2007-07-20 2010-11-02 International Business Machines Corporation User identification enabled elevator control method and system
CA2722809C (en) * 2008-04-29 2014-10-21 Inventio Ag Lift installation and call control for use in a lift installation
EP2208701A1 (de) * 2009-01-16 2010-07-21 Inventio Ag Verfahren zur Steuerung einer Aufzugsanlage
CN202602625U (zh) * 2012-05-16 2012-12-12 上海宇诺电气技术有限公司 智能无线呼叫系统
US10836604B2 (en) 2014-02-13 2020-11-17 Inventio Ag Method and system for operating elevator installation using mobile radio

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
AU2015217692C1 (en) 2018-01-25
CA2939142C (en) 2019-01-08
PL3105159T3 (pl) 2018-10-31
AU2015217692B2 (en) 2017-10-12
US20160376124A1 (en) 2016-12-29
CA2939142A1 (en) 2015-08-20
EP3105159B1 (de) 2018-05-09
BR112016018293A2 (enrdf_load_stackoverflow) 2017-08-08
BR112016018293B1 (pt) 2023-03-21
US10836604B2 (en) 2020-11-17
ES2673273T5 (en) 2025-03-14
WO2015121294A1 (de) 2015-08-20
CN105980285A (zh) 2016-09-28
PT3105159T (pt) 2018-08-10
AU2015217692A1 (en) 2016-09-01
HK1223901A1 (zh) 2017-08-11
CN105980285B (zh) 2017-12-05
EP3105159A1 (de) 2016-12-21
ES2673273T3 (es) 2018-06-21

Similar Documents

Publication Publication Date Title
EP3105159B2 (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
EP2691940B1 (de) Verwaltung von zugriffsrechten auf betriebs- und/oder steuerungsdaten von gebäuden oder gebäudekomplexen
EP3307666B1 (de) Aufzugsystem mit prädiktiver ruferzeugung
EP3542350B1 (de) Zugangskontrollsystem mit automatischer statusaktualisierung
DE102018211776A1 (de) Aufzugsteuerungs- und überwachungssystem
WO2016066457A1 (de) System und verfahren zur wahrung der privatsphäre von personen in aufzugssystemen
WO2015018741A1 (de) Kommunikationsverfahren für eine aufzugsanlage
DE112018003983T5 (de) Türantrieb
EP2912856B1 (de) System und verfahren zur datenschutzkonformen erfassung und weiterleitung von telemetriedaten
EP3634897B1 (de) Aufzugssystem mit besucherbetriebsmodus
DE112016001246T5 (de) System und Steuerung für eine Raumzuteilung in Aufzugkabinen
DE102015013318A1 (de) Verfahren zur Entfernung eines Kraftfahrzeugs von einer Zielfläche, Kommunikationssystem, Kraftfahrzeug und Sendevorrichtung
DE102014224101A1 (de) Verfahren und Vorrichtung zum Betreiben eines Parkplatzes
DE102014224106A1 (de) Verfahren zum Überwachen eines Parkplatzes
WO2019121335A1 (de) Zugangskontrollsystem mit funk- und gesichtserkennung
EP3158465B1 (de) Verfahren, vorrichtung und system zum aufbau und zum betrieb eines drahtlosen netzwerks
EP3124418A1 (de) Aufzugssteuerung mit drahtlosem zugangspunkt
EP3680205A1 (de) System zum transport eines benutzers mit einem aufzug zu einem ziel, nachrüstsatz und verfahren
DE102014115999A1 (de) Bedienung eines Aufzugs mittels Touchscreen
DE102015117591A1 (de) Verfahren und System zur Steuerung einer Autoparkvorrichtung
EP3798171A1 (de) Steuerung für eine aufzugsanlage
EP3902759B1 (de) Verfahren und vorrichtung zum kommissionieren einer personentransportanlage
DE102017205211A1 (de) Verfahren zum Betrieb eines automatisierten Kraftfahrzeugs und Kraftfahrzeug
EP3001386B1 (de) System und verfahren zur initialisierung eines bordgeräts
EP4490089A1 (de) Gebäudesystem mit aufzugsanlage für gemischt genutztes gebäude

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

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

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

PUAH Patent maintained in amended form

Free format text: ORIGINAL CODE: 0009272

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

Free format text: STATUS: PATENT MAINTAINED AS AMENDED

27A Patent maintained in amended form

Effective date: 20250115

AK Designated contracting states

Kind code of ref document: B2

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: DE

Ref legal event code: R102

Ref document number: 502015004192

Country of ref document: DE

REG Reference to a national code

Ref country code: ES

Ref legal event code: DC2A

Ref document number: 2673273

Country of ref document: ES

Kind code of ref document: T5

Effective date: 20250314

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

Ref country code: DE

Payment date: 20250226

Year of fee payment: 11

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

Ref country code: ES

Payment date: 20250314

Year of fee payment: 11

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

Ref country code: CH

Payment date: 20250301

Year of fee payment: 11

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

Ref country code: FR

Payment date: 20250224

Year of fee payment: 11

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

Ref country code: IT

Payment date: 20250225

Year of fee payment: 11

Ref country code: GB

Payment date: 20250218

Year of fee payment: 11

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

Ref country code: TR

Payment date: 20250130

Year of fee payment: 11