EP2776900B1 - Sensor api framework for cloud based applications - Google Patents

Sensor api framework for cloud based applications Download PDF

Info

Publication number
EP2776900B1
EP2776900B1 EP12787227.3A EP12787227A EP2776900B1 EP 2776900 B1 EP2776900 B1 EP 2776900B1 EP 12787227 A EP12787227 A EP 12787227A EP 2776900 B1 EP2776900 B1 EP 2776900B1
Authority
EP
European Patent Office
Prior art keywords
sensor
sensor data
request
mobile device
core processor
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
EP12787227.3A
Other languages
German (de)
English (en)
French (fr)
Other versions
EP2776900A1 (en
Inventor
Piyush Sharma
Ashwin Swaminathan
Christopher Brunner
Murali R. Chari
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.)
Qualcomm Inc
Original Assignee
Qualcomm Inc
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
Application filed by Qualcomm Inc filed Critical Qualcomm Inc
Publication of EP2776900A1 publication Critical patent/EP2776900A1/en
Application granted granted Critical
Publication of EP2776900B1 publication Critical patent/EP2776900B1/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F1/00—Details not covered by groups G06F3/00 - G06F13/00 and G06F21/00
    • G06F1/26—Power supply means, e.g. regulation thereof
    • G06F1/32—Means for saving power
    • G06F1/3203—Power management, i.e. event-based initiation of a power-saving mode
    • G06F1/3234—Power saving characterised by the action undertaken
    • G06F1/3293—Power saving characterised by the action undertaken by switching to a less power-consuming processor, e.g. sub-CPU
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/54—Interprogram communication
    • G06F9/541—Interprogram communication via adapters, e.g. between incompatible applications
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H04W52/02—Power saving arrangements
    • H04W52/0209—Power saving arrangements in terminal devices
    • H04W52/0261—Power saving arrangements in terminal devices managing power supply demand, e.g. depending on battery level
    • H04W52/0274—Power saving arrangements in terminal devices managing power supply demand, e.g. depending on battery level by switching on or off the equipment or parts thereof
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M2250/00—Details of telephonic subscriber devices
    • H04M2250/12—Details of telephonic subscriber devices including a sensor for measuring a physical value, e.g. temperature or motion
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H04W52/02—Power saving arrangements
    • H04W52/0209—Power saving arrangements in terminal devices
    • H04W52/0261—Power saving arrangements in terminal devices managing power supply demand, e.g. depending on battery level
    • H04W52/0287—Power saving arrangements in terminal devices managing power supply demand, e.g. depending on battery level changing the clock frequency of a controller in the equipment
    • H04W52/0293—Power saving arrangements in terminal devices managing power supply demand, e.g. depending on battery level changing the clock frequency of a controller in the equipment having a sub-controller with a low clock frequency switching on and off a main controller with a high clock frequency
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D30/00—Reducing energy consumption in communication networks
    • Y02D30/70—Reducing energy consumption in communication networks in wireless communication networks

Definitions

  • This disclosure relates generally to apparatus and methods for wireless communications, and more particularly to providing sensor data from a mobile device to multiple web-based applications.
  • client applications that require sensor data from a mobile device have a corresponding client application executing on the mobile device. Some of these client applications run on the mobile device continuously. With the wide variety of sensors being integrated into mobile devices and growing interest in the community to leverage sensor data in innovative ways, such client applications on the mobile device are increasing in popularity and use. These multiple client applications come from different sources, communicate with different servers, and may each consume large amounts of power and processing cycles from the mobile device. Unless these multiple client applications are from a common vendor, they are as a whole uncoordinated with each other and query the sensors randomly and redundantly. A sensor may be interrupted with overlapping requests when a single coordinated response would have sufficed.
  • a platform should exist that reduces a number of client applications running on a mobile device, coordinate sensor requests, minimize or eliminate code development on the mobile device platform, and/or reduce power consumption in providing sensor data to server applications.
  • US patent application US 2010/302028 describes managing the power consumption of one or more sensors utilized within a mobile device.
  • US patent application US 2008/263196 describes using a tolerance level provided by the application developer to control the execution of the application instructions at multiple devices with varying resources, and using an involvement level provided by the sensor or computing device owner for the purpose of automatically adapting the execution of application code at multiple devices to suit the individual owner's willingness to share resources, and the capabilities of resources available with that owner.
  • Multiple applications interface with a tasking server.
  • a mobile device client receives requests for sensor data from the tasking server, processes the requests, receives the sensor data from a sensor in the mobile device and replies to the requests with a response comprising the sensor data.
  • a mobile device and a method running on a mobile device for providing a common API (application programming interface) that couples sensor data from one or more sensors to multiple server applications via a low duty cycle processor thereby offloading a high power consuming application processor.
  • API application programming interface
  • a mobile device for providing a common API (application programming interface), the mobile device comprising: a modem coupled to a wireless antenna; a client application processor coupled to the modem, the client application processor, consuming a first level of power over a duration; a sensor core processor coupled to the modem and comprising the common API, wherein the sensor core processor comprises a sensor core client and a sensor driver coupled to the sensor core client, wherein the sensor core processor consumes a second level of power over the duration, and wherein the second level is lower than the first level of power; a sensor coupled to communicate with the sensor driver of the sensor core processor.
  • a common API application programming interface
  • a method in a mobile device for providing a common API comprising: receiving, from a first web-based server application, a first request for sensor data using the common API; receiving, from a second web-based server application unrelated to the first web-based server application, a second request for sensor data using the common API; processing the first request and the second request for sensor data on a sensor core processor and bypassing a client application processor; receiving, at the sensor core processor, sensor data from a sensor; replying to the first request with a first response comprising the sensor data; and replying to the second request for sensor data with a second response, separate from the first request, comprising the sensor data.
  • a common API application programming interface
  • a mobile device for providing a common API (application programming interface) 170, the mobile device comprising: means for receiving, from a first web-based server application, a first request for sensor data using the common API; means for receiving, from a second web-based server application unrelated to the first web-based server application, a second request for sensor data using the common API; means for processing the first request and the second request for sensor data on a sensor core processor and bypassing a client application processor; means for receiving, at the sensor core processor, sensor data from a sensor; means for replying to the first request with a first response comprising the sensor data; and means for replying to the second request for sensor data with a second response, separate from the first request, comprising the sensor data.
  • a common API application programming interface
  • a device comprising a processor and a memory wherein the memory includes software instructions for: receiving, from a first web-based server application, a first request for sensor data using a common API; receiving, from a second web-based server application unrelated to the first web-based server application, a second request for sensor data using the common API; processing the first request and the second request for sensor data on a sensor core processor and bypassing a client application processor; receiving, at the sensor core processor, sensor data from a sensor; replying to the first request with a first response comprising the sensor data; and replying to the second request for sensor data with a second response, separate from the first request, comprising the sensor data.
  • a non-transient computer-readable storage medium including program code stored thereon, comprising program code for: receiving, from a first web-based server application, a first request for sensor data using a common API; receiving, from a second web-based server application unrelated to the first web-based server application, a second request for sensor data using the common API; processing the first request and the second request for sensor data on a sensor core processor and bypassing a client application processor; receiving, at the sensor core processor, sensor data from a sensor; replying to the first request with a first response comprising the sensor data; and replying to the second request for sensor data with a second response, separate from the first request, comprising the sensor data.
  • a mobile device described herein may be implemented in conjunction with various wireless communication networks such as a wireless wide area network (WWAN), a wireless local area network (WLAN), a wireless personal area network (WPAN), and so on.
  • WWAN wireless wide area network
  • WLAN wireless local area network
  • WPAN wireless personal area network
  • CDMA Code Division Multiple Access
  • TDMA Time Division Multiple Access
  • FDMA Frequency Division Multiple Access
  • OFDMA Orthogonal Frequency Division Multiple Access
  • SC-FDMA Single-Carrier Frequency Division Multiple Access
  • LTE Long Term Evolution
  • a CDMA network may implement one or more radio access technologies (RATs) such as cdma2000, Wideband-CDMA (W-CDMA), and so on.
  • Cdma2000 includes IS-95, IS-2000, and IS-856 standards.
  • a TDMA network may implement Global System for Mobile Communications (GSM), Digital Advanced Mobile Phone System (D-AMPS), or some other RAT.
  • GSM and W-CDMA are described in documents from a consortium named "3rd Generation Partnership Project" (3GPP).
  • Cdma2000 is described in documents from a consortium named "3rd Generation Partnership Project 2" (3GPP2).
  • 3GPP and 3GPP2 documents are publicly available.
  • a WLAN may be an IEEE 802.11x network
  • a WPAN may be a Bluetooth network, an IEEE 802.15x, or some other type of network.
  • the techniques may also be implemented in conjunction with any combination of WWAN, WLAN and/or WPAN.
  • a satellite positioning system typically includes a system of transmitters positioned to enable entities to determine their location on or above the Earth based, at least in part, on signals received from the transmitters.
  • Such a transmitter typically transmits a signal marked with a repeating pseudo-random noise (PN) code of a set number of chips and may be located on ground based control stations, user equipment and/or space vehicles. In a particular example, such transmitters may be located on Earth orbiting satellite vehicles (SVs).
  • PN pseudo-random noise
  • a SV in a constellation of Global Navigation Satellite System such as Global Positioning System (GPS), Galileo, GLONASS or Compass may transmit a signal marked with a PN code that is distinguishable from PN codes transmitted by other SVs in the constellation (e.g., using different PN codes for each satellite as in GPS or using the same code on different frequencies as in GLONASS).
  • GNSS Global Navigation Satellite System
  • GPS Global Positioning System
  • GLONASS Global Positioning System
  • Compass may transmit a signal marked with a PN code that is distinguishable from PN codes transmitted by other SVs in the constellation (e.g., using different PN codes for each satellite as in GPS or using the same code on different frequencies as in GLONASS).
  • GNSS Global Navigation Satellite System
  • GPS Global Positioning System
  • GLONASS Global Positioning System
  • Compass may transmit a signal marked with a PN code that is distinguishable from PN codes transmitted by other SVs in the constellation (e.g., using different
  • the techniques provided herein may be applied to or otherwise enabled for use in various regional systems, such as, e.g., Quasi-Zenith Satellite System (QZSS) over Japan, Indian Regional Navigational Satellite System (IRNSS) over India, Beidou over China, etc., and/or various augmentation systems (e.g., an Satellite Based Augmentation System (SBAS)) that may be associated with or otherwise enabled for use with one or more global and/or regional navigation satellite systems.
  • QZSS Quasi-Zenith Satellite System
  • IRNSS Indian Regional Navigational Satellite System
  • SBAS Satellite Based Augmentation System
  • an SBAS may include an augmentation system(s) that provides integrity information, differential corrections, etc., such as, e.g., Wide Area Augmentation System (WAAS), European Geostationary Navigation Overlay Service (EGNOS), Multi-functional Satellite Augmentation System (MSAS), GPS Aided Geo Augmented Navigation or GPS and Geo Augmented Navigation system (GAGAN), and/or the like.
  • WAAS Wide Area Augmentation System
  • GNOS European Geostationary Navigation Overlay Service
  • MSAS Multi-functional Satellite Augmentation System
  • GPS Aided Geo Augmented Navigation or GPS and Geo Augmented Navigation system (GAGAN), and/or the like such as, e.g., a Global Navigation Satellite Navigation System (GNOS), and/or the like.
  • SPS may include any combination of one or more global and/or regional navigation satellite systems and/or augmentation systems, and SPS signals may include SPS, SPS-like, and/or other signals associated with such one or more SPS.
  • a mobile device 100 sometimes referred to as a mobile station (MS) or user equipment (UE), such as a cellular phone, mobile phone or other wireless communication device, personal communication system (PCS) device, personal navigation device (PND), Personal Information Manager (PIM), Personal Digital Assistant (PDA), laptop or other suitable mobile device which is capable of receiving wireless communication and/or navigation signals.
  • MS mobile station
  • UE user equipment
  • PCS personal communication system
  • PND personal navigation device
  • PIM Personal Information Manager
  • PDA Personal Digital Assistant
  • laptop laptop or other suitable mobile device which is capable of receiving wireless communication and/or navigation signals.
  • the term "mobile station” is also intended to include devices which communicate with a personal navigation device (PND), such as by short-range wireless, infrared, wireline connection, or other connection - regardless of whether satellite signal reception, assistance data reception, and/or position-related processing occurs at the device or at the PND.
  • PND personal navigation device
  • mobile station is intended to include all devices, including wireless communication devices, computers, laptops, etc. which are capable of communication with a server, such as via the internet, WiFi, or other network, and regardless of whether satellite signal reception, assistance data reception, and/or position-related processing occurs at the device, at a server, or at another device associated with the network. Any operable combination of the above are also considered a mobile device 100.
  • a cloud 300 which may be the public internet or a private internet, may be accessed through a wireless base station or access point having an internet gateway.
  • a base station provides internet access through its data services offerings.
  • an access point provides internet access via a WiFi signal.
  • a framework exposing an API (application programming interface) to web-based server applications 200 on the internet or in the cloud 300 is presented.
  • the API allows server applications 200 to retrieve sensor data from a mobile device 100 via a low-power sensor core processor on the mobile device 100. This API eliminates effort and cost associated with developing and promoting a new mobile device client application.
  • the API framework includes APIs that web-based application may use to fetch sensor data from one or more particular sensors on the mobile device 100.
  • the mobile device 100 may receive an instruction via the API to trigger actions based on a certain condition (such as a threshold-based triggering, time-based triggering or a computation-based triggering).
  • the web-based application may set up future triggers by having the mobile device 100 execute a customized script via the API.
  • a web-based application may register (possibly requiring explicit permissions from the user) for either requesting immediate or periodic sensor data or may set up a future trigger for sensor data.
  • FIG. 1 shows components of a known system including cloud-based applications and dedicated client applications 130 (e.g., 131, 132, 133) running on a client application processor 120 of a mobile device 100.
  • the cloud-based applications are web-based remote server applications 200 (e.g., 201, 202, 203) running in the cloud 300.
  • the client applications 130 communicate sensor data to the server applications 200 via a client application processor 120.
  • a mobile device 100 must continuously execute separate client applications 130 (e.g., client B application 132) for the server applications 200.
  • Client applications 130 follows a vendor proprietary protocol 171 and consumes power while waiting for a request for sensor data from server applications 200. Because server applications 200 are unrelated to the other server applications 200, requests for sensor data are not coordinated.
  • FIG. 2 shows components of a mobile device 100 that provides sensor data via a client application processor 120.
  • a mobile device 100 processes sensor data requests via dedicated client applications 130 (e.g., 131, 132, 133) running on a client application processor 120.
  • Dedicated client applications 130 e.g., 131, 132, 133 are required for the server applications 200 (e.g., 201, 202, 203).
  • client A application 131 and client B application 132 execute on a client application processor 120 and wait for a request from server A application 201 and server B application 202, respectively.
  • a client application receives a request, it sends the request to a sensor core processor 140, which in turns polls or interrupts a particular sensor 160 or set of sensors (e.g., a global positioning satellite (GPS) receiver 161, an accelerometer 162, a gyroscope 163, a magnetometer 164, a temperature sensor 165, a pressure sensor 166, a proximity sensor 167 and/or an ambient light sensor (ALS 168) and the like).
  • the particular sensor 160 or set of sensors may also include a microphone and/or a camera.
  • the client application responds to the original request with the sensor data. Therefore, the client application processor 120 is consuming power running various client applications 130 while it is waiting for new requests from its particular server application 200 and while it is waiting for sensor data.
  • FIG. 3 shows components of a mobile device 100 that provides sensor data using a sensor core processor 140 and bypassing a client application processor 120, in accordance with the present invention.
  • the mobile device 100 operates with a common API 170 at the interface between the sensor core processor 140 and the server applications 200, which bypasses the client application processor 120.
  • the sensor core processor 140 operates in a low power mode.
  • the sensor core processor 140 may operate at a lower clock rate and/or have longer hibernation periods than the client application processor 120 or run on a lower grade processor. In this manner, the client application processor 120 is consuming a first level of power over a duration and the sensor core processor 140 is consuming a second level of power over the duration, where the second level of power is lower than the first level of power.
  • the sensor core processor 140 executes a sensor core client 141 using the common API to communicate with various server applications 200.
  • the sensor core client 141 acts as a means to receive requests for sensor data and a means for replying to the requests, each using a common API.
  • the sensor core processor 140 also executes sensor drivers 150.
  • the sensor drivers 150 may include a GPS driver 151, which acts as a means to communicate with the GPS receiver 161.
  • the sensor drivers 150 may include an accelerometer driver 152, which acts as a means to communicate with the accelerometer 162.
  • the sensor drivers 150 may include a gyroscope driver 153, which acts as a means to communicate with the gyroscope 163.
  • the sensor drivers 150 may include a magnetometer driver 154, which acts as a means to communicate with the magnetometer 164.
  • the sensor drivers 150 may include a driver for each separate sensor, which acts as a means for receiving the sensor data from a sensor.
  • the sensor drivers 150 are tailored to communicate with a specific hardware implementation of the
  • the sensor core processor 140 waits for requests from the server applications 200, which uses a common API request and is sent via the modem 110.
  • the modem 110 is coupled to an air interface via a wireless antenna 111.
  • the server applications 200 may push the request to the mobile device 100.
  • the sensor core processor 140 may be less responsive than the client application processor 120, however, the sensor data reception at server applications 200 is often not time critical. Other client applications 130 requiring an immediate response may still be executed on the client application processor 120 but will not reduce power consumption as will client applications 130 running on the sensor core processor 140.
  • the sensor core processor 140 may execute lower computationally intensive applications while more computationally intensive applications are executed on the client application processor 120. This configuration enables trigger calculations and sensor data uploads to be done on the low power processor while leaving the power intensive application processor in a sleep mode.
  • FIG. 4 shows an API framework, in accordance with the present invention.
  • the API framework includes an application layer 10, a high level operating system (HLOS 20), and a low level operating system (LLOS 30).
  • HLOS 20 high level operating system
  • LLOS 30 low level operating system
  • Server-based applications communicate with the top of API framework at the application layer 10. Sensors communicate with the API framework from below at the LLOS 30.
  • the entire API framework runs on the low-power sensor core processor, such as sensor core processor 140, in the mobile device 100.
  • a unified application runs at the application layer 10 and acts as a client by returning sensor data as requested by multiple uncoordinated, unassociated and unrelated cloud or web-based server applications 200.
  • Sensor drivers on the mobile device 100 reside below the application layer 10 and HLOS 20 and are under control of the LLOS 30.
  • a mobile device 100 includes sensor drivers 150 that are coupled to the LLOS 30.
  • the sensor drivers 150 is partially or completely part of the LLOS 30.
  • FIG. 5 shows components of a system including server applications 200 (e.g., 201, 202, 203) running in the cloud 300 and a dedicated sensor core client 141 running on a sensor core processor 140 of a mobile device 100.
  • the system communicates sensor data via separate sensor drivers 150 running on the sensor core processor 140.
  • the sensor core client 141 may act as a means for processing requests for sensor data.
  • the sensor core client 141 may coordinate overlapping or conflicting sensor data requests such that two separate requests for sensor data invoice a single call to sensor drivers 150.
  • a sensor 160 is not interrupted with overlapping requests when a single coordinated response suffices.
  • the sensor core processor 140 receives requests from the modem 110 (shown in FIGS. 3 and 4 ) from separate and unrelated server applications 200 but with a common API 170. These requests may wait until the sensor core processor 140 cycles between an inactive period of a duty cycle (a sleep mode) to an active period of the duty cycle (an operational mode). A complete duty cycle includes one inactive period and one adjoining active period. Often, a duty-cycle operational mode that favors a sleep mode over an operational mode is a low-power duty-cycle mode. The sensor core processor 140 saves power by operating in a low-power duty-cycle mode.
  • the sensor core client 141 uses the sensor drivers 150 to receive the sensor data from the sensors 160 and reports the sensor data back to the requesting server applications 200 via the common API 170. In this manner, the mobile device 100 provides the sensor data using the sensor core processor 140 and bypassing a client application processor 120.
  • FIG. 6 illustrates various API messages, in accordance with the present invention.
  • Common API messages include both requests for sensor information and responses containing sensor data.
  • a sensor data request contains a request for sensor data and an indication or address of where that data should be returned.
  • sensor data request 301 is a simple request for sensor data from a particular sensor and contains a return IP address.
  • sensor data request 302 is a request for sensor data from a variable sensor and contains a return IP address. Attached to sensor data request 302 is an indication of the type of sensor data 303.
  • the type of sensor data 303 may indicate data from an accelerometer.
  • sensor data request 304 is a request for sensor data from multiple sensors and contains a return IP address.
  • Attached to sensor data request 304 is an indication of a first type of sensor data 305 and a second type of sensor data 306.
  • sensor data request 307 is a request for sensor data at a future time and contains a return IP address.
  • Attached to sensor data request 307 is a schedule 308.
  • the schedule 308 may indicate that the sensor data is requested periodically and/or starting at a particular time.
  • the unified client application may send a sensor data response.
  • sensor data response 310 corresponds to sensor data request 301, 302 or 307.
  • Sensor data response 310 contains the indicated IP address as a destination address.
  • Attached to sensor data response 310 is the raw sensor data 311.
  • sensor data response 312 corresponds to sensor data request 304.
  • Sensor data response 312 contains the indicated IP address as a destination address. Attached to sensor data response 312 are the raw sensor data 313 from a first type of sensor and the raw sensor data 314 from a second type of sensor.
  • the sensor data request includes instructions indicating a triggering calculation or triggering event.
  • a triggering calculation may or may not be met.
  • a trigger instructs the mobile device 100 to send data from one or more of its sensors as sensor data if one or more sensor measurements or sensor data from the same sensor and/or different sensors trigger a certain condition.
  • the mobile device 100 sends a sensor data response message including data from a first sensor (e.g., the GPS sensor showing a border has been crossed) based on data from a second sensor (e.g., the temperature sensor indicating a temperature passing lower than a certain amount).
  • the triggering event may be location based. For example, when the GPS sensor shows a mobile device 100 is entering or exiting a certain boundary, the mobile device 100 may report its temperature.
  • the mobile device 100 may send measurements from multiple sensors based on a sensor triggering a certain criteria.
  • the mobile device 100 may send measurements from a sensor based on a combination of measurements from multiple sensors triggering a certain criteria.
  • the triggers may be a range or a certain value and may include a hysteresis to reduce duplicative reporting.
  • the mobile device 100 sends the GPS data based on when the temperature sensor shows temperature is outside a range for a certain about of time, the humidity sensor indicates humidity is greater that a certain value and the accelerometer 162 shows acceleration is below a set threshold.
  • the mobile device 100 may send data from multiple or all sensors based on criteria begin met by multiple sensors. For example, the mobile device 100 may determine certain sensors indicate an emergency is occurring with a patient from biomedical sensors and then may report the emergency in the form of data from the biomedical sensors and the GPS sensor in a sensor data response message. Furthermore, some sensors may be included within the mobile device 100 itself while other sensors may be included in a personal area network (PAN) apart from but in communication with the mobile device 100.
  • PAN personal area network
  • a triggering calculation is triggered by one or more sensors.
  • a triggering calculation may also be triggered by or conditioned on a timer or absolute time.
  • a sensor may report its data after conditions are met and a certain amount of time has passed from a previous event, such as a previous reporting.
  • a mobile device 100 may periodically check (e.g., every 30 minutes) if certain sensor conditions are met and if so, report sensor data.
  • a mobile device 100 may check according to a schedule (e.g., every day at 8 AM, noon and 5 PM) whether certain sensor conditions are met and if so, report sensor data.
  • FIG. 7 shows a flow diagram 400, in accordance with the present invention.
  • the method is executed in a mobile device 100 and provides a common API 170 to multiple server applications 200.
  • a mobile device 100 receives, from a first web-based application (e.g., server application 201), a first request for sensor data using the common API 170.
  • the mobile device 100 receives, from a second web-based application (e.g., server B application 202) unrelated to the first web-based application, a second request for sensor data also uses the common API 170.
  • a first web-based application e.g., server application 201
  • a second web-based application e.g., server B application 202
  • the mobile device 100 processes the first request and the second request for sensor data on a sensor core processor 140 using a sensor core client 141 and bypasses a client application processor 120.
  • the mobile device 100 receives, at the sensor core processor, sensor data from a sensor.
  • the mobile device 100 replies to the first request with a first response comprising the sensor data and bypasses the client application processor 120.
  • the mobile device 100 replies to the second request for sensor data with a second response.
  • the second response is separate from the first request and comprises the sensor data and also bypasses the client application processor 120. Step 450 and step 460 may occur independently, sequentially or overlapping from one another.
  • the methodologies described herein may be implemented by various means depending upon the application. For example, these methodologies may be implemented in hardware, firmware instructions, software instructions, or any combination thereof.
  • the processing units may be implemented within one or more application specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), processors, controllers, micro-controllers, microprocessors, electronic devices, other electronic units designed to perform the functions described herein, or a combination thereof.
  • ASICs application specific integrated circuits
  • DSPs digital signal processors
  • DSPDs digital signal processing devices
  • PLDs programmable logic devices
  • FPGAs field programmable gate arrays
  • processors controllers, micro-controllers, microprocessors, electronic devices, other electronic units designed to perform the functions described herein, or a combination thereof.
  • the methodologies may be implemented with modules (e.g., procedures, functions, and so on) that perform the functions described herein.
  • Any machine-readable medium tangibly embodying instructions may be used in implementing the methodologies described herein.
  • software codes may be stored in a non-transient computer-readable storage medium, such as memory, and executed by a processor unit.
  • Memory may be implemented within the processor unit or external to the processor unit.
  • memory refers to any type of long term, short term, volatile, nonvolatile, or other memory and is not to be limited to any particular type of memory or number of memories, or type of media upon which memory is stored.
  • the functions may be stored as one or more instructions or code on a computer-readable medium. Examples include computer-readable media encoded with a data structure and computer-readable media encoded with a computer program. Computer-readable media includes physical computer storage media. A storage medium may be any available medium that can be accessed by a computer.
  • such computer-readable media can comprise RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to store desired program code in the form of instructions or data structures and that can be accessed by a computer; disk and disc, as used herein, includes compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk and blu-ray disc where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above should also be included within the scope of computer-readable media.
  • a communication apparatus may include a transceiver having signals indicative of instructions and data.
  • the instructions and data are configured to cause one or more processors to implement the functions outlined in the claims. That is, the communication apparatus includes transmission media with signals indicative of information to perform disclosed functions. At a first time, the transmission media included in the communication apparatus may include a first portion of the information to perform the disclosed functions, while at a second time the transmission media included in the communication apparatus may include a second portion of the information to perform the disclosed functions.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Software Systems (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Telephone Function (AREA)
  • Telephonic Communication Services (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Power Sources (AREA)
  • Transceivers (AREA)
EP12787227.3A 2011-11-09 2012-10-19 Sensor api framework for cloud based applications Active EP2776900B1 (en)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US13/292,578 US10248184B2 (en) 2011-11-09 2011-11-09 Sensor API framework for cloud based applications
PCT/US2012/061142 WO2013070420A1 (en) 2011-11-09 2012-10-19 Sensor api framework for cloud based applications

Publications (2)

Publication Number Publication Date
EP2776900A1 EP2776900A1 (en) 2014-09-17
EP2776900B1 true EP2776900B1 (en) 2019-09-04

Family

ID=47178914

Family Applications (1)

Application Number Title Priority Date Filing Date
EP12787227.3A Active EP2776900B1 (en) 2011-11-09 2012-10-19 Sensor api framework for cloud based applications

Country Status (8)

Country Link
US (1) US10248184B2 (zh)
EP (1) EP2776900B1 (zh)
JP (1) JP6165156B2 (zh)
KR (1) KR101683352B1 (zh)
CN (1) CN103946769B (zh)
ES (1) ES2759620T3 (zh)
HU (1) HUE046106T2 (zh)
WO (1) WO2013070420A1 (zh)

Families Citing this family (20)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CA2861215C (en) * 2012-09-12 2015-09-08 Omron Corporation Data flow control order generating apparatus and sensor managing apparatus
AU2013321782A1 (en) * 2012-09-27 2015-04-16 Omron Corporation Device management apparatus and device search method
CN104102749B (zh) * 2013-04-11 2019-04-23 华为技术有限公司 终端设备
US9313740B2 (en) 2013-06-14 2016-04-12 Sony Corporation Power efficient sensor accessory management through sensor subsystem
US10362112B2 (en) * 2014-03-06 2019-07-23 Verizon Patent And Licensing Inc. Application environment for lighting sensory networks
US10416750B2 (en) 2014-09-26 2019-09-17 Qualcomm Incorporated Algorithm engine for ultra low-power processing of sensor data
WO2016154785A1 (zh) * 2015-03-27 2016-10-06 华为技术有限公司 一种云平台、运行应用的方法及接入网单元
KR102525295B1 (ko) * 2016-01-06 2023-04-25 삼성전자주식회사 데이터 관리 방법 및 장치
US10009708B2 (en) 2016-03-09 2018-06-26 Tata Consultancy Services Limited System and method for mobile sensing data processing
CN109792617B (zh) 2016-07-13 2021-02-23 华为技术有限公司 用于部署在平台上的应用程序的应用程序弹性系统及其方法
US20190079787A1 (en) * 2016-11-14 2019-03-14 Google Llc Systems and methods for providing interactive streaming media
CN106713648B (zh) * 2016-12-30 2019-07-26 Oppo广东移动通信有限公司 一种通信方法及移动终端
CN106791152B (zh) * 2016-12-30 2019-08-27 Oppo广东移动通信有限公司 一种通信方法及移动终端
EP3396549A1 (de) * 2017-04-28 2018-10-31 dSPACE digital signal processing and control engineering GmbH Adapter für die verbindung eines eingebetteten systems mit einem bedienrechner und verfahren zum anpassen eines adapters
US10796501B2 (en) * 2017-06-19 2020-10-06 Qualcomm Incorporated Interactive sharing of vehicle sensor information
US10789093B2 (en) * 2019-02-05 2020-09-29 Citrix Systems, Inc. Extension of mobile device sensor capabilities into an application
US11818210B2 (en) * 2019-10-07 2023-11-14 Advanced Measurement Technology, Inc. Systems and methods of direct data storage for measurement instrumentation
CN111366791A (zh) * 2020-03-03 2020-07-03 上海闻泰信息技术有限公司 电磁波吸收比值的检测方法、装置及电子设备
KR102531765B1 (ko) 2020-12-07 2023-05-11 인하대학교 산학협력단 Put 오브젝트 처리속도 상향을 위한 하이브리드 오브젝트 스토리지 시스템 및 그 동작 방법
US12010517B1 (en) * 2021-05-10 2024-06-11 Zimperium, Inc. Dynamic detection for mobile device security

Family Cites Families (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20060036833A (ko) 2004-10-26 2006-05-02 엘지전자 주식회사 표준 메모리 카드 타입의 생체 정보 측정 장치와 그서비스 방법
CN102740323B (zh) * 2006-09-26 2015-09-30 高通股份有限公司 基于无线装置的传感器网络
US7925900B2 (en) 2007-01-26 2011-04-12 Microsoft Corporation I/O co-processor coupled hybrid computing device
US8185599B2 (en) * 2007-04-18 2012-05-22 Microsoft Corporation Programming techniques for distributed multi-party networks
US8467300B2 (en) 2007-10-18 2013-06-18 Telefonaktiebolaget Lm Ericsson (Publ) Methods and arrangements in a mobile telecommunications network
US20090125918A1 (en) * 2007-11-13 2009-05-14 Microsoft Corporation Shared sensing system interfaces
KR100959774B1 (ko) 2008-06-05 2010-05-27 (주)엔텔스 센싱 정보 처리 장치, 방법 및 그 방법을 실행하는프로그램이 기록된 기록매체
US8405505B2 (en) 2009-05-26 2013-03-26 Qualcomm Incorporated Power management of sensors within a mobile device
US9086875B2 (en) 2009-06-05 2015-07-21 Qualcomm Incorporated Controlling power consumption of a mobile device based on gesture recognition
US8521848B2 (en) * 2011-06-28 2013-08-27 Microsoft Corporation Device sensor and actuation for web pages

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
None *

Also Published As

Publication number Publication date
US20130117769A1 (en) 2013-05-09
WO2013070420A1 (en) 2013-05-16
JP2015507774A (ja) 2015-03-12
KR101683352B1 (ko) 2016-12-06
HUE046106T2 (hu) 2020-01-28
CN103946769B (zh) 2017-02-15
CN103946769A (zh) 2014-07-23
ES2759620T3 (es) 2020-05-11
EP2776900A1 (en) 2014-09-17
JP6165156B2 (ja) 2017-07-19
KR20140090193A (ko) 2014-07-16
US10248184B2 (en) 2019-04-02

Similar Documents

Publication Publication Date Title
EP2776900B1 (en) Sensor api framework for cloud based applications
US9749794B2 (en) Scalability and reliability of hardware geo-fencing with failover support
EP3017321B1 (en) Methods and apparatuses for use in providing location parameters to mobile applications
US9615208B2 (en) Dynamically controlling the presentation of a graphic feature based on location information
US9128180B2 (en) Efficient power usage in position tracking operations
US9596670B2 (en) Location assisted service capability monitoring
EP2769561B1 (en) Method and/or apparatus for geofence management
US8310394B2 (en) Apparatus, method, manufacture, and system for sensing substitution for location-based applications
JP6055826B2 (ja) 端末機器を位置決めするための方法及び装置
US9736781B2 (en) Determining points of interest within a geofence
KR20120052260A (ko) 예측성 배경에 기초한 푸시된 컨텐츠 전달의 구성
US9788275B2 (en) Method for reducing current consumption and electronic device thereof
JP5672384B2 (ja) 進行中のロケーションセッション中のロケーション関連データの転送および修正
US9103901B2 (en) Position determination methodology selection
JP2021069122A (ja) 動的に生成された地理データを用いた位置追跡のためのシステムおよび方法
US20170367066A1 (en) Terrestrial transceiver-based positioning data download for semi-connected devices

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

17P Request for examination filed

Effective date: 20140403

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

DAX Request for extension of the european patent (deleted)
STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: EXAMINATION IS IN PROGRESS

17Q First examination report despatched

Effective date: 20170731

REG Reference to a national code

Ref country code: DE

Ref legal event code: R079

Ref document number: 602012063671

Country of ref document: DE

Free format text: PREVIOUS MAIN CLASS: G06F0001320000

Ipc: G06F0001329300

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

RIC1 Information provided on ipc code assigned before grant

Ipc: H04W 52/02 20090101ALI20190401BHEP

Ipc: G06F 9/54 20060101ALI20190401BHEP

Ipc: H04L 29/08 20060101ALI20190401BHEP

Ipc: G06F 1/3293 20190101AFI20190401BHEP

INTG Intention to grant announced

Effective date: 20190429

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

REG Reference to a national code

Ref country code: CH

Ref legal event code: EP

REG Reference to a national code

Ref country code: AT

Ref legal event code: REF

Ref document number: 1176264

Country of ref document: AT

Kind code of ref document: T

Effective date: 20190915

REG Reference to a national code

Ref country code: DE

Ref legal event code: R096

Ref document number: 602012063671

Country of ref document: DE

REG Reference to a national code

Ref country code: IE

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: NL

Ref legal event code: FP

REG Reference to a national code

Ref country code: LT

Ref legal event code: MG4D

REG Reference to a national code

Ref country code: HU

Ref legal event code: AG4A

Ref document number: E046106

Country of ref document: HU

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

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

Ref country code: SE

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

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

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

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

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

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

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

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

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

REG Reference to a national code

Ref country code: AT

Ref legal event code: MK05

Ref document number: 1176264

Country of ref document: AT

Kind code of ref document: T

Effective date: 20190904

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

Ref country code: AT

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

Ref country code: PT

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

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

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

Ref country code: PL

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

REG Reference to a national code

Ref country code: ES

Ref legal event code: FG2A

Ref document number: 2759620

Country of ref document: ES

Kind code of ref document: T3

Effective date: 20200511

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

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

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

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

REG Reference to a national code

Ref country code: CH

Ref legal event code: PL

REG Reference to a national code

Ref country code: DE

Ref legal event code: R097

Ref document number: 602012063671

Country of ref document: DE

PLBE No opposition filed within time limit

Free format text: ORIGINAL CODE: 0009261

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

Free format text: STATUS: NO OPPOSITION FILED WITHIN TIME LIMIT

PG2D Information on lapse in contracting state deleted

Ref country code: IS

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

Ref country code: LI

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

Effective date: 20191031

Ref country code: LU

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

Effective date: 20191019

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

Ref country code: CH

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

Effective date: 20191031

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

26N No opposition filed

Effective date: 20200605

REG Reference to a national code

Ref country code: BE

Ref legal event code: MM

Effective date: 20191031

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

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

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

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

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

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

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

Ref country code: NL

Payment date: 20210920

Year of fee payment: 10

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

Ref country code: TR

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

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

REG Reference to a national code

Ref country code: NL

Ref legal event code: MM

Effective date: 20221101

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

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

Ref country code: ES

Payment date: 20231108

Year of fee payment: 12

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

Ref country code: IT

Payment date: 20231012

Year of fee payment: 12

Ref country code: HU

Payment date: 20231004

Year of fee payment: 12

Ref country code: DE

Payment date: 20230915

Year of fee payment: 12

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

Ref country code: FI

Payment date: 20240926

Year of fee payment: 13

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

Ref country code: GB

Payment date: 20240912

Year of fee payment: 13

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

Ref country code: FR

Payment date: 20240913

Year of fee payment: 13