EP2577344B1 - Maintenance d'almanach pour localisation de station mobile - Google Patents

Maintenance d'almanach pour localisation de station mobile Download PDF

Info

Publication number
EP2577344B1
EP2577344B1 EP11722981.5A EP11722981A EP2577344B1 EP 2577344 B1 EP2577344 B1 EP 2577344B1 EP 11722981 A EP11722981 A EP 11722981A EP 2577344 B1 EP2577344 B1 EP 2577344B1
Authority
EP
European Patent Office
Prior art keywords
mobile device
almanac
almanac data
version
date
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
EP11722981.5A
Other languages
German (de)
English (en)
Other versions
EP2577344A2 (fr
Inventor
Grant Alexander Marshall
Mark Leo Moeglein
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 EP2577344A2 publication Critical patent/EP2577344A2/fr
Application granted granted Critical
Publication of EP2577344B1 publication Critical patent/EP2577344B1/fr
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • G—PHYSICS
    • G01—MEASURING; TESTING
    • G01S—RADIO DIRECTION-FINDING; RADIO NAVIGATION; DETERMINING DISTANCE OR VELOCITY BY USE OF RADIO WAVES; LOCATING OR PRESENCE-DETECTING BY USE OF THE REFLECTION OR RERADIATION OF RADIO WAVES; ANALOGOUS ARRANGEMENTS USING OTHER WAVES
    • G01S19/00—Satellite radio beacon positioning systems; Determining position, velocity or attitude using signals transmitted by such systems
    • G01S19/01—Satellite radio beacon positioning systems transmitting time-stamped messages, e.g. GPS [Global Positioning System], GLONASS [Global Orbiting Navigation Satellite System] or GALILEO
    • G01S19/03—Cooperating elements; Interaction or communication between different cooperating elements or between cooperating elements and receivers
    • G01S19/05—Cooperating elements; Interaction or communication between different cooperating elements or between cooperating elements and receivers providing aiding data
    • G—PHYSICS
    • G01—MEASURING; TESTING
    • G01S—RADIO DIRECTION-FINDING; RADIO NAVIGATION; DETERMINING DISTANCE OR VELOCITY BY USE OF RADIO WAVES; LOCATING OR PRESENCE-DETECTING BY USE OF THE REFLECTION OR RERADIATION OF RADIO WAVES; ANALOGOUS ARRANGEMENTS USING OTHER WAVES
    • G01S19/00—Satellite radio beacon positioning systems; Determining position, velocity or attitude using signals transmitted by such systems
    • G01S19/01—Satellite radio beacon positioning systems transmitting time-stamped messages, e.g. GPS [Global Positioning System], GLONASS [Global Orbiting Navigation Satellite System] or GALILEO
    • G01S19/13—Receivers
    • G01S19/24—Acquisition or tracking or demodulation of signals transmitted by the system
    • G01S19/27—Acquisition or tracking or demodulation of signals transmitted by the system creating, predicting or correcting ephemeris or almanac data within the receiver
    • G—PHYSICS
    • G01—MEASURING; TESTING
    • G01S—RADIO DIRECTION-FINDING; RADIO NAVIGATION; DETERMINING DISTANCE OR VELOCITY BY USE OF RADIO WAVES; LOCATING OR PRESENCE-DETECTING BY USE OF THE REFLECTION OR RERADIATION OF RADIO WAVES; ANALOGOUS ARRANGEMENTS USING OTHER WAVES
    • G01S5/00—Position-fixing by co-ordinating two or more direction or position line determinations; Position-fixing by co-ordinating two or more distance determinations
    • G01S5/02—Position-fixing by co-ordinating two or more direction or position line determinations; Position-fixing by co-ordinating two or more distance determinations using radio waves
    • G01S5/0205—Details
    • G01S5/0236—Assistance data, e.g. base station almanac
    • G—PHYSICS
    • G01—MEASURING; TESTING
    • G01S—RADIO DIRECTION-FINDING; RADIO NAVIGATION; DETERMINING DISTANCE OR VELOCITY BY USE OF RADIO WAVES; LOCATING OR PRESENCE-DETECTING BY USE OF THE REFLECTION OR RERADIATION OF RADIO WAVES; ANALOGOUS ARRANGEMENTS USING OTHER WAVES
    • G01S19/00—Satellite radio beacon positioning systems; Determining position, velocity or attitude using signals transmitted by such systems
    • G01S19/01—Satellite radio beacon positioning systems transmitting time-stamped messages, e.g. GPS [Global Positioning System], GLONASS [Global Orbiting Navigation Satellite System] or GALILEO
    • G01S19/13—Receivers
    • G01S19/24—Acquisition or tracking or demodulation of signals transmitted by the system
    • G01S19/25—Acquisition or tracking or demodulation of signals transmitted by the system involving aiding data received from a cooperating element, e.g. assisted GPS
    • G01S19/258—Acquisition or tracking or demodulation of signals transmitted by the system involving aiding data received from a cooperating element, e.g. assisted GPS relating to the satellite constellation, e.g. almanac, ephemeris data, lists of satellites in view

Definitions

  • the presently disclosed embodiments relate generally to systems, methods, apparatuses, and computer readable media for position location of wireless mobile devices, and more particularly to such systems, methods, apparatuses, and computer readable media for managing almanac data for use in position location functions by such devices.
  • location information has been principally generated by satellite positioning systems (SPSs), such as the global positioning system (GPS) using NAVSTAR satellites, the Russian GLONASS system, or the European EUTELSAT system, or a land-based positioning system, such as LORAN-C.
  • SPSs satellite positioning systems
  • GPS global positioning system
  • GLONASS Russian GLONASS
  • European EUTELSAT European EUTELSAT
  • LORAN-C land-based positioning system
  • assistance information has a number of advantages.
  • Current cellular base stations are positioned in relatively close proximity to mobile devices in which they are in communications, as well as to adjacent or nearby other cellular base stations.
  • the use of assistance data improves or extends the capabilities of satellite positioning systems, enabling operation in places previously not possible, since it improves time-to-fix- and sensitivity. Additionally, improved accuracy may be obtained from having more numerous and closely spaced receivers to account for atmospheric and other effects which tend to degrade the accuracy of positioning systems.
  • additional base stations are deployed in the future, even more densely than current systems, they are likely to continue to provide even better resolution.
  • BSA base station almanac data
  • BSA data could be provided, it would not be the most effective or cost efficient technique, because it would be primarily transaction based, requested, for instance, on an ad hoc, or as-needed, basis. That is, each time a mobile device initiated a position location application or service, it would have to request the base station almanac data.
  • BSA needs to be obtained from a location server serving the mobile devices; consequently, mobile devices must contact the server for their almanac information.
  • the location server does not have any way to contact the mobile devices to keep the BSA up-to-date.
  • the server may have downloaded the BSA, for example, two hours ago, the server typically has no memory of that download, and the BSA must be re-downloaded when it is again needed, even if it is the same data that the mobile device already has. This, of course, takes time, bandwidth, and other resources.
  • WO 02/067462 A1 describes GPS assistance message and data issue identifiers for transmission to GPS enabled mobile stations (MS) in cellular communications networks (100).
  • the GPS almanac data issue identifier is transmitted over the cellular communications network, and received by a MS.
  • the MS compares the GPS almanac data issue identifier with any GPS almanac data issue identifier stored previously at the mobile station for the almanac data.
  • the mobile station reads a new almanac assistance message transmitted by the network if the GPS almanac data issue identifier is different than the stored GPS almanac data issue identifier.
  • a network server that has direct access to a source of real time base station almanac data provided by wireless network operators.
  • This server is designed to respond to requests for base station almanac information from mobile devices in the wireless network. Based on the serving cell information provided by mobile devices making base station almanac requests, the server provides at least subsets of base station almanac data to the mobile devices. The subsets may be optimized, depending upon the application, needs, and context of the mobile devices. In doing so, the server keeps track of the data passed to each uniquely identifiable mobile device. At the same time, the server keeps track of changes in the base station almanac data provided by the network operator. By comparing the base station almanac changes to the known data subsets sent to all mobile devices, the server can determine which mobile devices need updated information, in an efficient manner that minimizes utilization of network resources.
  • the present invention discloses methods, remote station apparatus , mobile devices and a computer-readable medium for managing base station almanac data as defined by the appended claims.
  • base station almanac contains position, calibration, and other characteristics of the base stations from which wireless signals originate.
  • a client server system is used to pass this base station almanac information to the mobile devices.
  • the base station almanac information is not static however, but dynamic and constantly changing due to the maintenance and changing requirements of the wireless network through time. Examples of the types of events that result in changes to the BSA include turning off a base station transmitter which removes it from the network, bringing a new base station transmitter into the network, changing a parameter of a base station, or the like.
  • Another event that results in changes to the BSA is moving a particular base station to a new physical location. Therefore the base station almanac data passed to mobile devices may quickly becomes out-of-date. Using the out-of-date information for positioning calculations results in degraded location performance.
  • the systems and techniques described herein place most of the control for providing updated base station almanac information in the network where changes to the base station almanac information are known. This solution places the decision logic of when to update a mobile device's BSA in the network, providing controlled server loading and updates only when they are needed and only to the mobile devices that need them.
  • FIG. 1 An embodiment of an almanac data management system 10 in a mobile network environment 15 is shown in Figure 1 .
  • the mobile network environment 15 includes a region 18 in which various mobile devices, such as the cell phone 20, shown, may roam.
  • a "mobile device,” or simply “mobile” refers to a device such as a cellular or other wireless communication device, personal communication system (PCS) device, personal navigation device (PND), personal information manager (PIM), personal digital assistant (PDA), laptop computer, or other suitable mobile device that is capable of receiving wireless communication, navigation signals, or both.
  • PCS personal communication system
  • PND personal navigation device
  • PIM personal information manager
  • PDA personal digital assistant
  • laptop computer or other suitable mobile device that is capable of receiving wireless communication, navigation signals, or both.
  • mobile device is also intended to include devices that communicate with personal navigation devices (PNDs), such as by short-range wireless, infrared, wireline connection, or other connection, regardless of whether satellite signal reception, assistance data reception, or position-related processing occurs at the device or at the PND.
  • PNDs personal navigation devices
  • mobile device is intended to include all devices, including wireless communication devices, computers, laptop computers, netbooks, smartbooks, or the like, which are capable of communication with a server, such as via the Internet, Wi-Fi, or other network, and regardless of whether satellite signal reception, assistance data reception, 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.”
  • the region 18 includes any number of base stations, four 24, 26, 28, and 30 being shown for illustration, with which a mobile device (cell phone 20) may receive signals from which its position can be determined, in known manner.
  • the cell phone 20 is shown in two-way wireless communication with base station 28, also in known manner.
  • a number of satellites 32, 34, ... may be in view of the region 18, as shown.
  • the satellites 32 and 34 are of the type that broadcast signals from which the position of a receiving station can be determined, also in known manner.
  • the signals may include at least almanac data.
  • Almanac data is data that includes information indicative of a position of the satellite (or other entity) originating the data.
  • each satellite transmits almanac information (from which a position of each of the satellites of the GPS constellation can be determined at a particular time), as well as ephemeris information (which provides more accurate position information for the transmitting satellite).
  • almanac data is not limited to position information; it may also contain, for instance, clock state information and other data associated with the relevant transmitter. It should also be noted that the almanac data may be received, for example, by a receiver (not shown) for transmission to one or more of the base stations 24, 26, 28, or 30, and rebroadcast in its original, corrected, or modified form.
  • the base stations 24, 26, 28, and 30 do not broadcast their own almanac data which might otherwise be used to determine the location of the cell phone 20. That almanac data, in the past, needed to be obtained from the location server.
  • the cell phone 20 is shown in a "visiting" or “roaming" system away from its respective home system.
  • This embodiment is shown for purposes of illustration, as the respective systems could just as easily could have been simply operating in its home system.
  • their communications to their home systems is via a visiting system server 36 associated with, for example, the base station 28.
  • the visiting system server 36 communicates with the home system 40 through at least a home system server 38.
  • the cell phone 20 holds its own almanac data 22, which may or may not be up-to-date.
  • the almanac data 22 may have been previously downloaded from a location server 42, in the home system.
  • the location server 42 keeps track of mobile devices registered with the home system 10.
  • the base station almanac information is not static, but is dynamic and constantly changing through time. The changes may be due, for example, to the maintenance and changing requirements of the wireless network in which the cell phone 20 operates. Since using the out-of-date information for positioning calculations results in degraded location performance, in order for the mobile devices to accurately determine their respective positions, the almanac data needs to be up-to-date.
  • the location server 42 has direct access to a source of real time base station almanac data 43 provided by a wireless network operator 45.
  • the location server 42 includes an almanac memory 44 and an associated version memory 46.
  • the version memory assigns a unique identifier to each version of the almanac data held in the almanac memory 44.
  • almanac data entries data 1, data 2, data 3, data 4, etc.
  • version indicators v1, v2, v3, v4, etc.
  • the location server 42 maintains a mobile device information memory 48 which contains, among other things, the identification of the almanac data version currently held by each mobile device registered with the home system 10.
  • a mobile device designated as MD1 (cell phone 20) is shown having almanac version v2
  • a mobile device designated as MD2 (not shown) is shown having almanac version v3.
  • Both almanac versions v2 and v3 are out-of-date in the embodiment illustrated, since the current, or up-to-date almanac version 52 in the almanac memory 44 is v4.
  • a comparator system 50 compares the current (up-to-date) almanac data version in the version memory 44 with the current (possibly out-of-date) almanac data version of the mobile devices held in mobile device information memory 48. If, in fact, the comparator system 50 determines that the almanac data version of a mobile device is out-of-date, i.e., not matching the up-to-date almanac data version, or a subset thereof, in the almanac memory 44, the up-to-date almanac data version 52, or a subset thereof, is scheduled and pushed to the mobile device.
  • Comparator system 50 may be implemented in a number of ways; e.g., instructions stored in memory may be executed by a processor to access the current almanac data version of one or more mobile devices and to access the almanac data version in the version memory, to execute a comparison operation, and to provide an indicator (such as a "stale version" flag) based on the outcome of the comparison operation.
  • Comparison system 50 can also be implemented as hardware (e.g., hardware gates, etc., that in some embodiments may be integrated on one or more substrates, where the one or more substrates may include functionality for one or more of the modules described herein). Additionally, embodiments incorporating a combination of hardware and/or software and/or firmware may be used.
  • a subset of the the up-to-date almanac data version 52 may be generated, for example, by an almanac data subset generator 54.
  • an almanac data subset may include only the changed almanac data.
  • Another embodiment may include only the changed almanac data of the base stations 24, 26, 28, and 30 in the system in which the mobile device is roaming.
  • Other subsets will be apparent to those skilled in the art. It should also be noted that the subsets themselves can be versioned and handled in the same or similar manner as the almanac data version itself.
  • an indicator such as a "subset downloaded” flag, or the like, may need to be employed to ensure that necessary additional almanac data my need to be additionally downloaded, for example, if the mobile device roams into another visiting system or region.
  • a notification may be sent to the mobile device to be held in a memory, or the like, of the mobile device, and when the mobile device subsequently needs to have position location determinations made, it sends a request to the location server 42 for the up-to-date almanac data 52. This request, of course, need not be in response to a current need, but may be on a scheduled or other basis.
  • the up-to-date almanac data version 52, or subset thereof generated by the subset generator 54 is downloaded, in the embodiment shown, by a downloading system 56.
  • downloading system 56 is configured to generate one or more messages to transmit up-to-date almanac information to cell phone 20. If a subset of the almanac data is generated, it may be necessary, in some embodiments, to save or archive previous almanac versions. In such a situation, downloading system 56 may be configured to generate one or more messages including the generated subset of up-to-date almanac data with at least some additional data.
  • the subset that is downloaded to the cell phone 20 may include the differences of all of the almanac data from all of the previous versions, although typically the download would comprise a full data replacement of the out-of-date mobile data.
  • a scheduler 58 may be provided to initiate the download of the up-to-date almanac data 52 (or a subset thereof) to the mobile devices served.
  • the scheduler 58 may operate to initiate a download upon the occurrence of a predetermined event. For instance, a download may be initiated when a mobile device logs into a mobile network, when a mobile device makes a position location request to an application that uses position location as an input, when a mobile device requests updates, or on a time schedule in conjunction with updates to other mobile devices in the network.
  • the home system server 38 may send a page or notification to those mobile devices which need updates, triggering those devices to make a request to the server.
  • the server responds to those requests providing the appropriate updated subsets and any new subsets required based on the current mobile serving base station.
  • location server 42 may be located outside of the home system 40 and merely called upon, as needed. In any event, however, the status of almanac versions of the various mobile devices is known and updated by the location server 42.
  • modules shown in FIG. 1 can be implemented in software, hardware, firmware, or a combination.
  • data and instructions to perform the acts described above may be stored in memory and executed by one or more processors.
  • Memory can be implemented in one or more modules, and the processor can comprise more than one processing resource.
  • hardware to perform the acts can be at least partially shared among the functional modules described.
  • the mobile device 60 may be a cell phone, such as the cell phone 20, or some other mobile device of the type described herein.
  • the mobile device 60 includes a transmitter 61 and a receiver 62 that may be of the type normally used for radio communications in a cellular network via antenna 63.
  • the signals in the mobile device 60 from the receiver 62 and to the transmitter 61 are controlled by one or more processors 64, also of the type described herein.
  • a location application 65 operates in conjunction with the processor 64 to perform specific location functions and to request location based information, including almanac information, for use in performing the particular location functions that it provides.
  • location application is shown as a part of the mobile device 60, it may alternatively be of the type that does not permanently reside in the mobile device 60.
  • the location application may be of the type that is downloaded for temporary use.
  • the device 60 also includes a notification receiver 66 for receiving a notification 67 from a location server, such as the location server 42 described above, that the almanac data held in almanac memory 68 is not up-to-date.
  • the notification may be, for example, transmitted as a part of a network overhead message, or by other means.
  • the notification may be received without regard to the operation of the location application 65, and may be initiated by the location server 42 completely independently of any operation of the mobile device 60.
  • the fact that a notification 67 has been received is noted in a notification memory 69.
  • location server 42 may transmit a message containing an indication of a current version identifier for almanac information.
  • Notification receiver 66 may access the received message to determine whether it contains a notification related to almanac information (e.g., notification of a new version of almanac information).
  • Notification information e.g., the version number, date, or other identifier of the almanac and/or almanac subset is then stored in notification memory 69.
  • An almanac validity tester 59 is provided for determining whether the almanac data is valid, or up-to-date, based on the notification noted in the notification memory 69. This determination may be made autonomously, based upon the almanac information provided by the network or location server 42.
  • An up-to-date almanac requester 70 is provided for requesting up-to-date almanac data in response to the determination by the almanac validity tester 59 that the almanac data is not valid.
  • the almanac validity tester 59 checks the notification memory 69 to determine whether a notification 67 has been received. If a notification 67 has been received, the up-to-date almanac requester 70 transmits a request back to the location server 42 to send the up-to-date almanac data. In response, the location server 42 transmits, or causes to be transmitted, the up-to-date almanac data to be stored in the almanac memory 68.
  • the up-to-date almanac requester 70 allows the location application 65 to make use of the current almanac data contained in the almanac memory 68. It should be noted that in some embodiments the up-to-date almanac requester 70 may operate on its own schedule, for example, to periodically check the notification memory 69 to determine whether a notification 67 has been received, and to operate in the manner indicated above in response to the notification state.
  • the various functions encircled by the dashed line 71 may be implemented in software, hardware, or combination thereof, as noted above with respect to the modules of FIG. 1 . More particularly, the various illustrative logical blocks, modules, circuits, and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, computer software, or combinations of both. To clearly illustrate this interchangeability of hardware and software, various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality.
  • DSP Digital Signal Processor
  • ASIC Application Specific Integrated Circuit
  • FPGA Field Programmable Gate Array
  • a general purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine.
  • a processor may also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.
  • a WWAN may be a Code Division Multiple Access (CDMA) network, a Time Division Multiple Access (TDMA) network, a Frequency Division Multiple Access (FDMA) network, an Orthogonal Frequency Division Multiple Access (OFDMA) network, a Single-Carrier Frequency Division Multiple Access (SC-FDMA) network, a Long Term Evolution (LTE) network, a WiMAX (IEEE 802.16) network and so on.
  • 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
  • WiMAX IEEE 802.16
  • 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.
  • Box 73 shows maintaining almanac data versions at a fixed location.
  • the fixed location may be, for example, a location associated with a home system 40.
  • the term "fixed location" does not necessarily imply that the almanac data versions is maintained at a location that is not movable or mobile, but that it is at a location not co-located with the mobile devices that are served by the location server 42.
  • Dashed-box 74 illustrates that in some embodiments the almanac information may be or comprise base station almanac data. In some embodiments the almanac data may be or comprise satellite almanac data, as shown in dashed-box 76.
  • Box 78 illustrates assigning unique version identifications to each almanac data version. As mentioned, it may not be necessary in some embodiments to maintain a full history list of all almanac data.
  • the almanac data of current interest is the most current or up-to-date almanac data version.
  • Box 80 illustrates maintaining mobile device almanac data. Typically, this would include maintaining almanac data for a number of mobile devices that are served by the location server 40.
  • Box 82 illustrates determining if the almanac data of the mobile device is current. As mentioned above, this may be done in some embodiments by comparing the current almanac data version in the mobile device with the up-to-date version maintained by the system (dashed-box 86). Alternatively, the fact that the almanac data held by a mobile device is not the current version may be noted whenever the almanac data in the server is updated by setting a flag for all of the mobile devices in the system (dashed-box 84), then updating the almanac data of the mobile devices on a scheduled or other basis.
  • Box 88 illustrates updating the almanac data in the mobile device if a current version of almanac data is later than the version of almanac data in the mobile device.
  • the updating steps 88 or 90 may be accomplished on a scheduled basis, as shown in dashed box 92.
  • a scheduling embodiment is shown in box 94 in which the mobile device is notified that it is not up-to-date. In response to the notification, the mobile device requests the up-to-date almanac data when it needs to have position location determinations made.
  • a software module may reside in Random Access Memory (RAM), flash memory, Read Only Memory (ROM), Electrically Programmable ROM (EPROM), Electrically Erasable Programmable ROM (EEPROM), registers, hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art.
  • An exemplary storage medium is coupled to the processor such the processor can read information from, and write information to, the storage medium. In the alternative, the storage medium may be integral to the processor.
  • the processor and the storage medium may reside in an ASIC.
  • firmware and/or software the methods and steps thereof 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 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, semiconductor storage, or other 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.
  • CD compact disc
  • DVD digital versatile disc
  • floppy disk floppy disk and blu-ray disc where disks usually reproduce data magnetically, while discs reproduce data optically with lasers.
  • computer-readable media also includes combinations of the above.
  • computer-readable media does not refer to propagating signals.
  • FIG. 4 A general example of an implementation 100 that comprises a computer-readable media is shown in Figure 4 , to which reference is now additionally made.
  • the implementation 100 includes a processor 102 that communicates with a memory 104 and a computer readable medium 106 that holds code or instructions for the operation of the computer.
  • the processor 102, memory 104, and computer readable medium 106 are of the type described herein above.
  • An I/O device 108 is provided to enable access to and from the processor 108.
  • the memory 104 and computer readable medium 106 may be implemented with a single unit, rather than discrete units shown.

Landscapes

  • Engineering & Computer Science (AREA)
  • Radar, Positioning & Navigation (AREA)
  • Remote Sensing (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Power Engineering (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Position Fixing By Use Of Radio Waves (AREA)
  • Telephone Function (AREA)
  • Telephonic Communication Services (AREA)

Claims (15)

  1. Dispositif mobile (20, 60) destiné à être utilisé dans un réseau sans fil, le dispositif comprenant :
    un moyen de mémorisation (22) de données d'almanach de station de base, BSA, les données d'almanach étant associées à au moins une station de base terrestre (24, 26, 28, 30) ;
    un moyen de réception (66) d'informations indicatives d'une version de données d'almanach actualisée en provenance d'un serveur de réseau (42), le moyen de réception comprenant un récepteur de notification (66) destiné à recevoir en provenance du serveur de réseau (42) une notification que les données d'almanach mémorisées ne sont pas actualisées, la notification étant lancée par un serveur de localisation indépendamment du fonctionnement du dispositif mobile (60) et étant basée sur une comparaison d'une version de données d'almanach actualisée à une version de données d'almanach du dispositif mobile, les deux versions étant mémorisées dans des mémoires du serveur d'emplacement, et une détermination que la version de données d'almanach du dispositif mobile est obsolète ;
    un moyen de détermination (59) que les données d'almanach mémorisées par le dispositif mobile sont actualisées sur la base de la notification reçue depuis le serveur de réseau (42) ; et
    un moyen de demande (70) de données d'almanach actualisées en réponse à la détermination que les données d'almanach mémorisées par le dispositif mobile ne sont pas actualisées.
  2. Dispositif mobile selon la revendication 1 comprenant en outre un moyen de réception destiné à recevoir les données d'almanach actualisées en provenance du serveur de réseau (42) programmées selon un événement prédéterminé et de préférence dans lequel l'événement prédéterminé est la connexion du dispositif mobile à un réseau mobile, ou la demande par le dispositif mobile d'une demande de localisation de position, ou la demande par le dispositif mobile d'actualisations ou selon un programme temporel conjointement à des actualisations d'autres dispositifs mobiles dans le réseau.
  3. Dispositif mobile selon la revendication 1 dans lequel la détermination que les données d'almanach mémorisées sont ou non actualisées est basée sur la suppression ou l'ajout de la station de base ou d'une autre station de base dans le réseau ou un changement d'emplacement de la ou d'une autre station de base ou un changement d'un paramètre de la station de base et de préférence dans lequel les données BSA comprennent des données de position et d'étalonnage associées à la station de base.
  4. Dispositif mobile selon la revendication 1 dans lequel le moyen de détermination que les données d'almanach mémorisées par ledit dispositif mobile sont ou non actualisées comprend un testeur de validité d'almanach.
  5. Dispositif mobile selon la revendication 2 dans lequel les informations indicatives d'une version d'almanach actualisée comprennent des informations indicatives d'un identifiant de version unique associé à la version d'almanach actualisée et de préférence dans lequel le moyen de détermination que les données d'almanach mémorisées par ledit dispositif mobile sont ou non actualisées comprend un moyen de comparaison d'un identifiant de version associé aux données d'almanach mémorisées par le dispositif mobile à l'identifiant de version associé à la version d'almanach actualisée.
  6. Dispositif mobile selon la revendication 11 dans lequel le récepteur de notification est configuré pour accéder à un message de réseau reçu et de préférence dans lequel le message de réseau est un message de surdébit de réseau.
  7. Appareil de station distante, comprenant :
    un serveur de localisation (42) contenant des données d'almanach de station de base, BSA, actualisées mémorisées dans une mémoire (44) du serveur de localisation et une identification d'une version de données BSA détenue par un dispositif mobile, dans lequel la version d'identification est mémorisée dans une mémoire d'informations de dispositif mobile (48) du serveur d'emplacement, et dans lequel les données d'almanach sont associes à au moins une station de base terrestre (24, 26, 28, 30) ;
    un comparateur (50) destiné à comparer les données d'almanach actualisées mémorisées dans la mémoire (44) à une version de données d'almanach du dispositif mobile mémorisée dans la mémoire d'informations de dispositif mobile (48) et à fournir une notification à transmettre au dispositif mobile (20) sur la base du résultat de la comparaison dans lequel la notification indique que les données d'almanach mémorisées par le dispositif mobile (20) ne sont pas actualisées, la notification étant lancée par un serveur de localisation indépendamment du fonctionnement du dispositif mobile (60) ; et
    un système de téléchargement (56) configuré pour générer des données d'almanach actualisées en réponse à une demande reçue depuis le dispositif mobile, dans lequel la demande est générée en réponse à une détermination dans le dispositif mobile que la version de données d'almanach du dispositif mobile n'est pas actualisée sur la base de la notification fournie par le serveur de localisation.
  8. Appareil de station distante selon la revendication 7 dans lequel le serveur de localisation est configuré pour poser un fanion associé au dispositif mobile quand les données BSA mémorisées dans la mémoire (44) sont modifiées, et pour acquitter le fanion quand l'au moins un sous-ensemble des données BSA changées a été téléchargé dans le dispositif mobile et de préférence dans lequel le serveur de localisation télécharge au moins un sous-ensemble des données BSA mémorisées dans la mémoire (44) dans le dispositif mobile d'une manière programmée si les données BSA mémorisées dans la mémoire (44) sont ultérieures à la version de données BSA détenue par le dispositif mobile.
  9. Appareil de station distante selon la revendication 6 dans lequel le serveur de localisation télécharge au moins un sous-ensemble des données BSA mémorisées dans la mémoire (44) dans le dispositif mobile si les données BSA mémorisées dans la mémoire (44) sont ultérieures à la version de BSA détenue par le dispositif mobile quand le dispositif mobile demande des données d'almanach.
  10. Appareil de station distante selon la revendication 6 dans lequel le serveur de localisation télécharge au moins un sous-ensemble des données BSA mémorisées dans la mémoire (44) dans le dispositif mobile quand une présence du dispositif mobile est détectée dans un réseau si le BSA mémorisé dans la mémoire (44) est ultérieur à la version de BSA détenue par le dispositif mobile.
  11. Procédé de gestion de données d'almanach de station de base depuis un emplacement distant d'un dispositif mobile, comprenant :
    le recouvrement depuis une mémoire (44) d'un serveur de localisation de données d'almanach de station de base, BSA, actualisées et d'une identification d'une version des données BSA, et le recouvrement depuis une mémoire d'informations de dispositif mobile (48) du serveur d'emplacement d'une identification d'une version de données BSA détenue par un dispositif mobile, dans lequel les données d'almanach sont associées à au moins une station de base terrestre (24, 26, 28, 30) ;
    la comparaison des données d'almanach actualisées mémorisées dans la mémoire (44) à une version de données d'almanach du dispositif mobile mémorisée dans une mémoire d'informations de dispositif mobile (48) ;
    la fourniture d'une notification à transmettre au dispositif mobile (20) sur la base du résultat de la comparaison, la notification indiquant que les données d'almanach mémorisées par le dispositif mobile (20) ne sont pas actualisées, la notification étant lancée par un serveur de localisation indépendamment du fonctionnement du dispositif mobile (60) ; et
    la génération de données d'almanach actualisées en réponse à une demande reçue depuis le dispositif mobile (20), dans lequel dans lequel la demande est générée en réponse à une détermination dans le dispositif mobile que la version de données d'almanach du dispositif mobile n'est pas actualisée sur la base de la notification fournie par le serveur de localisation.
  12. Procédé de gestion de données d'almanach selon la revendication 11 dans lequel les données d'almanach comprennent des données de position et d'étalonnage associées à la station de base et de préférence dans lequel l'actualisation comprend la comparaison de l'identifiant de version de la version de données d'almanach détenue par le dispositif mobile à l'identifiant de version de la version courante de données d'almanach.
  13. Procédé de gestion de données d'almanach selon la revendication 11 dans lequel l'actualisation comprend le téléchargement d'au moins un sous-ensemble de la version courante de données d'almanach dans le dispositif mobile d'une manière programmée et de préférence dans lequel l'actualisation comprend le téléchargement d'au moins un sous-ensemble de la version courante de données d'almanach dans le dispositif mobile quand le dispositif mobile demande des données d'almanach.
  14. Procédé de gestion de données d'almanach selon la revendication 11 dans lequel l'actualisation comprend le téléchargement d'au moins un sous-ensemble de la version courante de données d'almanach dans le dispositif mobile quand une présence du dispositif mobile est détectée dans un réseau et de préférence dans lequel l'emplacement fixe est un emplacement de système de rattachement du dispositif mobile.
  15. Support lisible par ordinateur sur lequel sont mémorisées des instructions, comprenant :
    des instructions qui, à leur exécution par un ordinateur d'un appareil selon la revendication 7, exécutent le procédé selon l'une quelconque des revendications 11 à 14.
EP11722981.5A 2010-05-28 2011-05-20 Maintenance d'almanach pour localisation de station mobile Active EP2577344B1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US12/789,926 US9063222B2 (en) 2010-05-28 2010-05-28 Almanac maintenance for mobile station positioning
PCT/US2011/037389 WO2011149781A2 (fr) 2010-05-28 2011-05-20 Maintenance d'almanach pour localisation de station mobile

Publications (2)

Publication Number Publication Date
EP2577344A2 EP2577344A2 (fr) 2013-04-10
EP2577344B1 true EP2577344B1 (fr) 2020-03-11

Family

ID=44121351

Family Applications (1)

Application Number Title Priority Date Filing Date
EP11722981.5A Active EP2577344B1 (fr) 2010-05-28 2011-05-20 Maintenance d'almanach pour localisation de station mobile

Country Status (6)

Country Link
US (1) US9063222B2 (fr)
EP (1) EP2577344B1 (fr)
JP (2) JP5952268B2 (fr)
KR (1) KR101489567B1 (fr)
CN (1) CN102918414B (fr)
WO (1) WO2011149781A2 (fr)

Families Citing this family (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2634593B1 (fr) 2012-03-02 2016-11-09 U-blox AG Positionnement utilisant un modèle local de propagation d'ondes
US9400320B2 (en) 2012-04-04 2016-07-26 Qualcomm Incorporated Methods and apparatus for efficient transport and management of a positioning and timing almanac
US9113432B2 (en) * 2013-03-14 2015-08-18 Qualcomm Incorporated Crowdsourcing based on base station almanac quality
US9197758B2 (en) * 2013-03-22 2015-11-24 Jdsu Uk Limited Method and apparatus for managing call data
US10021737B2 (en) 2013-09-17 2018-07-10 Qualcomm Incorporated Techniques for determining common characteristics of groups of wireless access points
WO2015131398A1 (fr) * 2014-03-07 2015-09-11 华为终端有限公司 Procédé et appareil de partage de données entre des dispositifs de positionnement
EP2940490B1 (fr) 2014-04-30 2024-05-29 U-blox AG Détermination de la dérive d'horloge au moyen de signaux d'opportunité
CN107003384A (zh) * 2014-08-14 2017-08-01 知维科技有限公司 更新定位数据
US9674653B2 (en) * 2015-03-03 2017-06-06 Facebook, Inc. Techniques to manage client location detection
RU2681647C1 (ru) * 2015-08-07 2019-03-12 Телефонактиеболагет Лм Эрикссон (Пабл) Дифференцированное позиционирование
US11191054B2 (en) * 2018-11-02 2021-11-30 Qualcomm Incorporated Method and apparatus for estimating a position of a mobile device using bundled positioning reference signals
CN113452429A (zh) * 2020-03-27 2021-09-28 华为技术有限公司 卫星星历更新的方法和通信装置
CN112198540B (zh) * 2020-09-30 2022-07-15 哈尔滨工程大学 一种基于动态网络基站的多模多频载波相位定位方法

Family Cites Families (21)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPS63280369A (ja) * 1987-05-13 1988-11-17 Mitsubishi Electric Corp オンライン計算機ネットワ−ク装置
JPH06130144A (ja) * 1992-10-15 1994-05-13 Toshiba Corp ナビゲーション装置
EP2110683A1 (fr) 1995-10-09 2009-10-21 Snaptrack, Inc. Procédé pour déterminer la position d'une unité distante
US5841396A (en) * 1996-03-08 1998-11-24 Snaptrack, Inc. GPS receiver utilizing a communication link
US6133871A (en) * 1995-10-09 2000-10-17 Snaptrack, Inc. GPS receiver having power management
KR100663899B1 (ko) * 1996-03-08 2007-05-17 스냅트랙, 인코포레이티드 통신링크를이용한향상된지피에스수신기
US20020068584A1 (en) * 2000-12-05 2002-06-06 Nortel Networks Limited Method and system for transmitting data to a mobile device
US7747257B2 (en) 2001-02-16 2010-06-29 Motorola, Inc. GPS assistance messages in cellular communications networks and methods therefor
US20040263386A1 (en) * 2003-06-26 2004-12-30 King Thomas M. Satellite positioning system receivers and methods
US8483717B2 (en) 2003-06-27 2013-07-09 Qualcomm Incorporated Local area network assisted positioning
US6915210B2 (en) 2003-07-17 2005-07-05 Motorola, Inc. Method of updating GPS almanac data for satellites not in view
US7450064B2 (en) * 2005-03-22 2008-11-11 Qualcomm, Incorporated Methods and systems for deriving seed position of a subscriber station in support of unassisted GPS-type position determination in a wireless communication system
JP2007006081A (ja) 2005-06-23 2007-01-11 Nec System Technologies Ltd 携帯通信端末及びそのプログラム並びにこれを用いるファイル転送方法及びシステム
WO2007082038A1 (fr) 2006-01-10 2007-07-19 Qualcomm Incorporated Système mondial de navigation par satellite
JP2010502133A (ja) 2006-08-24 2010-01-21 クゥアルコム・インコーポレイテッド ローミング中の移動局の測位をサポートするための方法および装置
UA99266C2 (ru) 2006-11-03 2012-08-10 Нокиа Корпорэйшн Идентификация базирующихся на времени эфемерид во вспомогательных данных и сообщениях с требованием вспомогательных данных
US9083745B2 (en) 2007-03-12 2015-07-14 Qualcomm Incorporated Network independent location services
JP2008258833A (ja) 2007-04-03 2008-10-23 Hitachi Kokusai Electric Inc 無線端末
JP2009198391A (ja) 2008-02-22 2009-09-03 Sharp Corp Ｇｐｓ受信機
US8644853B2 (en) 2008-05-12 2014-02-04 Qualcomm Incorporated Providing base station almanac to mobile station
KR20100037179A (ko) 2008-10-01 2010-04-09 엘지전자 주식회사 텔레매틱스 단말기와 지피에스 얼머낵 데이터 갱신 방법

Non-Patent Citations (1)

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

Also Published As

Publication number Publication date
EP2577344A2 (fr) 2013-04-10
KR101489567B1 (ko) 2015-02-03
WO2011149781A3 (fr) 2012-01-19
JP2013534078A (ja) 2013-08-29
JP2015121556A (ja) 2015-07-02
WO2011149781A2 (fr) 2011-12-01
JP6294249B2 (ja) 2018-03-14
JP5952268B2 (ja) 2016-07-13
CN102918414B (zh) 2015-04-15
US20110291885A1 (en) 2011-12-01
US9063222B2 (en) 2015-06-23
KR20130032334A (ko) 2013-04-01
CN102918414A (zh) 2013-02-06

Similar Documents

Publication Publication Date Title
EP2577344B1 (fr) Maintenance d'almanach pour localisation de station mobile
EP2740280B1 (fr) Fourniture d'informations d'almanach d'émetteur sans fil à un dispositif mobile sur la base d'un itinéraire prévu
US9026143B2 (en) Providing base station almanac to mobile station
KR101477363B1 (ko) 스파스 네트워크 알마낙
US9445233B2 (en) Wireless transmitter identity or positioning information partitioning
US9020522B2 (en) Method and system for optimizing uploading of location data for location based services
US20110201360A1 (en) Method and system for physical map-assisted wireless access point locating
EP2440945B1 (fr) Listes de préférences de demande de données d'assistance dans des systèmes globaux de navigation par satellite
US20080252518A1 (en) Method and apparatus for determining location using a hybrid solution
US7860517B1 (en) Mobile device tracking using mobile agent location breadcrumbs
JP2022524624A (ja) Ｇｐｓ支援による協調的なシグナリング支援型のｗｌａｎ ｄｆｓ動作
WO2017214979A1 (fr) Terminal mobile et procédé de positionnement associé
US9014727B2 (en) Method and system for updating obsolete records for reference positions in a reference position database
JP2009250756A (ja) 地図データ更新システム及びナビゲーション装置

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

AK Designated contracting states

Kind code of ref document: A2

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

RIC1 Information provided on ipc code assigned before grant

Ipc: G01S 19/25 20100101ALI20190820BHEP

Ipc: G01S 5/02 20100101AFI20190820BHEP

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

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

Country of ref document: AT

Kind code of ref document: T

Effective date: 20200315

REG Reference to a national code

Ref country code: IE

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: DE

Ref legal event code: R096

Ref document number: 602011065495

Country of ref document: DE

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

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

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

Ref country code: FI

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

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

Ref country code: DE

Payment date: 20200507

Year of fee payment: 10

REG Reference to a national code

Ref country code: NL

Ref legal event code: MP

Effective date: 20200311

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

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

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

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

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

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

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

Ref country code: GB

Payment date: 20200416

Year of fee payment: 10

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

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

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

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

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

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

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

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

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

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

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

REG Reference to a national code

Ref country code: AT

Ref legal event code: MK05

Ref document number: 1243834

Country of ref document: AT

Kind code of ref document: T

Effective date: 20200311

REG Reference to a national code

Ref country code: DE

Ref legal event code: R097

Ref document number: 602011065495

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

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

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

Ref country code: CH

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

Effective date: 20200531

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

Ref country code: LI

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

Effective date: 20200531

Ref country code: IT

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

Ref country code: ES

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

26N No opposition filed

Effective date: 20201214

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

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

REG Reference to a national code

Ref country code: BE

Ref legal event code: MM

Effective date: 20200531

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

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

Ref country code: FR

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

Effective date: 20200531

Ref country code: IE

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

Effective date: 20200520

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

REG Reference to a national code

Ref country code: DE

Ref legal event code: R119

Ref document number: 602011065495

Country of ref document: DE

GBPC Gb: european patent ceased through non-payment of renewal fee

Effective date: 20210520

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

Ref country code: GB

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

Effective date: 20210520

Ref country code: DE

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

Effective date: 20211201

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

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

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

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

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