EP3337042B1 - Zellulare handapparatvorrichtung - Google Patents
Zellulare handapparatvorrichtung Download PDFInfo
- Publication number
- EP3337042B1 EP3337042B1 EP16204075.2A EP16204075A EP3337042B1 EP 3337042 B1 EP3337042 B1 EP 3337042B1 EP 16204075 A EP16204075 A EP 16204075A EP 3337042 B1 EP3337042 B1 EP 3337042B1
- Authority
- EP
- European Patent Office
- Prior art keywords
- hardware
- operation mode
- circuit
- hardware circuit
- handset device
- 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
Links
- 230000001413 cellular effect Effects 0.000 title claims description 92
- 238000000034 method Methods 0.000 claims description 66
- 238000012508 change request Methods 0.000 claims description 58
- 230000008859 change Effects 0.000 claims description 23
- 230000008569 process Effects 0.000 claims description 20
- 238000012545 processing Methods 0.000 claims description 13
- 238000010586 diagram Methods 0.000 description 9
- 239000004165 Methyl ester of fatty acids Substances 0.000 description 7
- 238000004891 communication Methods 0.000 description 7
- 238000005516 engineering process Methods 0.000 description 4
- 238000004590 computer program Methods 0.000 description 2
- 230000006870 function Effects 0.000 description 2
- 230000001105 regulatory effect Effects 0.000 description 2
- 230000004044 response Effects 0.000 description 2
- 101000741965 Homo sapiens Inactive tyrosine-protein kinase PRAG1 Proteins 0.000 description 1
- 102100038659 Inactive tyrosine-protein kinase PRAG1 Human genes 0.000 description 1
- 238000013459 approach Methods 0.000 description 1
- 230000010267 cellular communication Effects 0.000 description 1
- 238000012790 confirmation Methods 0.000 description 1
- 230000010485 coping Effects 0.000 description 1
- 230000000977 initiatory effect Effects 0.000 description 1
- 230000007774 longterm Effects 0.000 description 1
- 238000010295 mobile communication Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000001228 spectrum Methods 0.000 description 1
- 230000001052 transient effect Effects 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04B—TRANSMISSION
- H04B1/00—Details of transmission systems, not covered by a single one of groups H04B3/00 - H04B13/00; Details of transmission systems not characterised by the medium used for transmission
- H04B1/005—Details of transmission systems, not covered by a single one of groups H04B3/00 - H04B13/00; Details of transmission systems not characterised by the medium used for transmission adapting radio receivers, transmitters andtransceivers for operation on two or more bands, i.e. frequency ranges
Definitions
- the disclosure relates to a cellular handset device with a configurable hardware circuit for processing a radio signal according to a first hardware capability set, in particular for a global navigation satellite system (GNSS) service, in a first operation mode and for processing a radio signal according to a second hardware capability set, in particular for a metropolitan beacon system (MBS) service, in a second operation mode.
- GNSS global navigation satellite system
- MBS metropolitan beacon system
- the disclosure particularly relates to techniques for reusing modem capabilities for MBS services.
- Terrestrial beacon systems 120 offer a far better performance for indoor positioning, but induce a cost adder.
- cellular functionality needs to be given up.
- costly additional front-end structures 121, 122 for using terrestrial beacon systems 120 must be provided as shown in Fig. 1 .
- Existing network protocols assume that the user equipment (UE) has a certain set of capabilities, and needs to follow network configuration command. Once UE communicated its capabilities and the network configuration command has been communicated to the UE 101, the UE must comply for the duration of the current network registration. As consequences, there is no flexibility in the system to reapply for new set of capabilities assuming those capabilities are dynamically changed. It is most desirable for rare cases such as e911 call to use terrestrial beaconing system.
- Document US 2010/277252 A1 discloses a multi-mode radio frequency front end module.
- Document EP 2 375 803 A1 discloses a multi-mode radio access network controller entity with dynamic re-configuration for supporting at least two different radio access technologies.
- Document US 2015/0133171 A1 discloses a method and system for implementing a dual-mode dual-band GNSS/M-LMS pseudolites receiver.
- GNSS global navigation satellite system
- MBS Metropolitan Beacon System
- a GNSS capability set is a set of hardware functions that supports the global navigation satellite system, i.e. a satellite navigation system with global coverage.
- a satellite navigation system is a system that uses satellites to provide autonomous geo-spatial positioning. It allows small electronic receivers to determine their location to high precision (within a few meters) using time signals transmitted along a line of sight by radio from satellites.
- An MBS capability set is a set of hardware functions that supports navigation by the MBS system.
- Metropolitan Beacon System (MBS) is a precise three dimensional location and timing technology designed to provide services to entire metropolitan areas where GNSS or other satellite location signals are blocked or can't be reliably received.
- the devices and methods described in the following may use hardware that supports the NextNav network.
- the NextNav network uses Metropolitan Beacon System technology to deliver high precision three-dimensional indoor location capabilities across a market area.
- MBS is built on principles similar to GPS transmitting precisely timed signals from a network of wide-area beacons enabling receivers to use trilateration techniques to determine their precise location. This differs significantly from other approaches to indoor and urban location relying on short-range, local-area transmitters.
- MBS is built on principles similar to GPS, transmitting precisely timed signals from a network of wide-area beacons enabling receivers to use trilateration techniques to determine their precise location.
- NextNav operates its MBS network over its spectrum licenses in the 920-928 MHz band.
- E911 is a system used in North America that links emergency callers with the appropriate public resources. In North America, the system tries to automatically associate a location with the origin of the call. This location may be a physical address or other geographic reference information such as X/Y map coordinates. The caller's telephone number is used in numerous manners to track a location that can be used to dispatch police, fire, emergency medical and other response resources.
- E911 exists not only in the US, there are a variety of E911 systems in Europe as well and it is a part of the 3GPP standard in some of its variation. There are multiple E911 methodologies, the special requirements in the US is that the FCC is mandating E911 with location indoor (MBS or similar) and outdoors as well.
- a corresponding device configured to perform the method and vice versa.
- a corresponding device may include a unit to perform the described method step, even if such a unit is not explicitly described or illustrated in the figures.
- the features of the various exemplary aspects described herein may be combined with each other, unless specifically noted otherwise.
- the techniques described herein may be implemented in wireless communication networks, in particular communication networks based on high speed communication standards from the 802.11 family according to the WiFi alliance, e.g. 802.11ad and successor standards.
- the methods are also applicable for mobile communication standards such as LTE, in particular LTE-A and/or OFDM and successor standards such as 5G.
- the methods and devices described below may be implemented in electronic devices such as cellular handsets, mobile or wireless devices (or mobile stations or User Equipments (UE)).
- the described devices may include integrated circuits and/or passives and may be manufactured according to various technologies.
- the circuits may be designed as logic integrated circuits, analog integrated circuits, mixed signal integrated circuits, optical circuits, memory circuits and/or integrated passives.
- Fig. 2 is a schematic diagram illustrating a communication system 200 with a cellular handset device 201 according to the disclosure.
- the cellular handset device 201 includes a configurable hardware circuit 202 and a hardware manager 320 (described in detail below with respect to Fig. 3 ).
- the hardware circuit 202 is configured to process a radio signal 210, 220 according to a first hardware capability set 211 when configured for a first operation mode and according to a second hardware capability set 212 when configured for a second operation mode.
- the radio signal may be a satellite signal 210 received from a satellite of a GNSS system 110 or alternatively a terrestrial radio signal 220 received from a terrestrial beacon system 120 such as an MBS system.
- the hardware manager is configured to change an operation mode of the hardware circuit 202 between the first operation mode and the second operation mode responsive to a hardware capability change request. This hardware capability change request may be initiated from a cellular network or initiated by a higher application layer of the cellular handset device 201.
- Figure 2 illustrates a communication system 200 for changing cellular handset (UE) capability on-the-fly in order to enable terrestrial beacon system features.
- UE cellular handset
- the GNSS system 110 and the MBS system 120 are only exemplary services to illustrate the reconfiguration of the hardware circuit 202. Any other service where different hardware capability sets are required can be implemented by such a mobile device 201 as well.
- the basic principle is to reuse existing receiver resources that share similar characteristics, e.g. terrestrial beaconing system 120 for indoor positioning (such as NextNAV) operating at 915 MHz bandwidth LTE band 8 operating at 920-925MHz.
- the UE will re-configure itself and may be required to notify the network.
- the device needs to apply for reconfiguration via capabilities change request from the cellular network.
- the cellular network will accept or reject it according to its network policy.
- the UE capability request may be initiated by the network (e.g. after e911 services activated). The network in most cases will acknowledge to such request assuming it is designed for it.
- the UE will reuse the existing infrastructure after confirmation from network arrives as long as it requires by the capability (e.g. till the e911 service being served) and reconfigure back to its default capabilities. This may also require to be notified that the device capabilities were restored.
- the cellular handset device 201 described herein supports UE capability reconfiguration, i.e. an RX chain (e.g. as described below with respect to Fig. 3 ) can be reused without duplicating or extending it with another external integrated circuit (IC) 122 as shown in Figure 1 .
- This functionality is mostly appealing in devices that are designed to be used world-wide where a subset of the feature set or partial regulatory requirements apply only to specific regions (e.g. e911 services which are mandatory only in North America).
- the UE will be able to "hijack" certain circuit to be served temporarily and to restore to its original purposes after the service has been served.
- Fig. 3 is a block diagram of a cellular handset device 201 according to the disclosure.
- the cellular handset device 201 includes a configurable hardware circuit 202 and a hardware manager 320.
- the hardware circuit 202 is configured to process a radio signal 312, e.g. a satellite signal 210 of a GNSS system 110 as described above with respect to Fig. 2 or a terrestrial radio signal 220 of a terrestrial beacon system 120 as described above with respect to Fig. 2 , according to a first hardware capability set when configured for a first operation mode and according to a second hardware capability set when configured for a second operation mode.
- the hardware manager 320 is configured to change an operation mode 324 of the hardware circuit 202 between the first operation mode and the second operation mode responsive to a hardware capability change request 322.
- This hardware capability change request 322 may be initiated from a cellular network or initiated by a higher application layer of the cellular handset device 201.
- the hardware circuit 202 includes a reception chain including an antenna circuit 311, a hardware front-end circuit 313, at least one mixer 315 and at least one local oscillator 317 which are configured to support the first hardware capability set when the hardware circuit 202 is configured for the first operation mode and which are configured to support the second hardware capability set when the hardware circuit 202 is configured for the second operation mode.
- the hardware front-end circuit 313 may operate at a first frequency band when the hardware circuit 202 is configured for the first operation mode and may operate at a second frequency band when the hardware circuit 202 is configured for the second operation mode.
- the at least one local oscillator 317 may operate at a first clock frequency when the hardware circuit 202 is configured for the first operation mode and may operate at a second clock frequency when the hardware circuit 202 is configured for the second operation mode.
- the hardware front-end circuit 313 may receive a satellite signal 210 when the hardware circuit 202 is configured for the first operation mode and may receive a terrestrial beacon signal 220 when the hardware circuit 202 is configured for the second operation mode.
- the hardware circuit 202 may include a navigation circuit (not shown in Fig. 3 ) that may process the satellite signal 210 based on a global navigation satellite system functionality when the hardware circuit 202 is configured for the first operation mode and that may process the terrestrial beacon signal 220 based on a terrestrial beacon system functionality when the hardware circuit 202 is configured for the second operation mode.
- a navigation circuit (not shown in Fig. 3 ) that may process the satellite signal 210 based on a global navigation satellite system functionality when the hardware circuit 202 is configured for the first operation mode and that may process the terrestrial beacon signal 220 based on a terrestrial beacon system functionality when the hardware circuit 202 is configured for the second operation mode.
- the terrestrial beacon system functionality may include an in-door call locating functionality, e.g. an emergency call locating functionality such as an e911 service functionality.
- the cellular handset device 201 may include a hardware capability storage for storing the first hardware capability set 211 when the hardware circuit 202 is configured for the second operation mode and for storing the second hardware capability set 212 when the hardware circuit 202 is configured for the first operation mode.
- the hardware manager may retrieve a content of the hardware capability storage responsive to the hardware capability change request 322. I.e. when reconfiguring the hardware circuit 202 from the first hardware capability set 211 to the second hardware capability set 212, this second hardware capability set 212 may be retrieved from the storage. In contrast, when reconfiguring the hardware circuit 202 from the second hardware capability set 212 to the first hardware capability set 211, this first hardware capability set 211 may be retrieved from the storage.
- the hardware manager 320 may receive the hardware capability change request 322 from an upper layer circuit of the cellular handset device 201 or from a cellular network. The hardware manager 320 may forward the hardware capability change request 322 received from the upper layer circuit to the cellular network and change the operation mode of the hardware circuit 202 responsive to an acknowledgement to the hardware capability change request 322 from the cellular network, e.g. as described below with respect to Fig. 4 .
- the hardware circuit 202 may acknowledge a change of its operation mode to the upper layer circuit.
- the hardware manager 320 may reapply the forwarding of the hardware capability change request 322 to the cellular network upon receiving a Non-Acknowledgement to the hardware capability change request 322 from the cellular network until a stopping criterion expires.
- This stopping criterion may include a reception of a predetermined number of Non-Acknowledgements to the reapplied forwarding of the hardware capability change request, e.g. as described below with respect to Fig. 4 .
- the hardware circuit 202 may report the Non-Acknowledgement to the upper layer circuit responsive to the expiration of the stopping criterion, e.g. as described below with respect to Fig. 4 .
- Fig. 4 is a message diagram of a method using UE initiated capability change in a cellular handset device according to the disclosure, e.g. a cellular handset device 201 as described above with respect to Figures 2 and 3 .
- Capability change initiated by UE flow and 2. Capability change initiated by Network flow.
- UE_CAPABILITY_CHANGE_REQ Upon request for UE capability change "UE_CAPABILITY_CHANGE_REQ" 411 by upper layer 410 (e.g. coming from host application), the UE 420 sends "NW_CAPABILITY_CHANGE_REQ” 421 to the cellular network 440.
- NW_CAPABILITY_CHANGE_REQ 421 from UE 420 received the cellular network 440 decides 431 if to allow this capability change. In case it accepts 441 this request 421 it will send "NW_CAPABILITY_CHANGE_ACK” 443 or in case it rejects 442 it will send "NW_CAPABILITY_CHANGE_NACK” 444.
- UE 420 Upon reception of the "NW_CAPABILITY_CHANGE_ACK” 443 UE 420 will send "UE_CAPABILITY_RECONFIG” 422 to UE HW 430 to reconfigure its infrastructure 432 to support the capability (e.g. share RX Chain including LOs, mixers, antenna, frontend).
- the UE HW 430 will report back to upper layer 410 with "UE_CAPABILITY_CHANGE_ACK” 433. For example, it will change the LTE band 8 chain to receive terrestrial beaconing system for navigation on 915 MHz (NextNAV)
- the UE 420 Upon reception of "NW_CAPABILITY_CHANGE_NACK” 444 the UE 420 will wait for a predefined time before reapplying for CAPABILTY change request 412.
- the UE 420 Upon predefined number of retrials of capability change request with NACK response, the UE 420 will report back to the capability requester upper layer 410 with "UE_CAPABILITY_CHANGE_NACK" 434. When services are served, the flow can be repeated by restoring to previous capability.
- the flow above can be altered to support also network initiated capability change.
- the network 440 will send the "UE_CAPABILITY_CHANGE_REQ" 411 to the UE 420.
- the UE 420 shall comply with this request and change its capability to support services temporary.
- the UE 420 will initiate the first flow (Capability change initiated by UE flow) to restore default capabilities.
- Fig. 5 is a schematic diagram illustrating a method 500 for operating a cellular handset device including a hardware circuit according to the disclosure.
- the method 500 may perform the functionality of the cellular handset device 201 described above with respect to Figures 2 and 3 .
- the method 500 includes: processing 501 a radio signal by the hardware circuit according to a first hardware capability set when an operation mode of the hardware circuit is configured for a first operation mode.
- the method 500 further includes: changing 502 the operation mode of the hardware circuit between the first operation mode and a second operation mode responsive to a hardware capability change request.
- the method 500 further includes: processing 503 a radio signal by the hardware circuit according to a second hardware capability set when the operation mode of the hardware circuit is configured for the second operation mode.
- the hardware circuit may include a reception chain, wherein the reception chain comprises an antenna circuit, a hardware front-end circuit, at least one mixer and at least one local oscillator which are configured to support the first hardware capability set when the hardware circuit is configured for the first operation mode and which are configured to support the second hardware capability set when the hardware circuit is configured for the second operation mode.
- the method 500 may further include: operating the hardware front-end circuit at a first frequency band when the hardware circuit is configured for the first operation mode; and operating the hardware front-end circuit at a second frequency band when the hardware circuit is configured for the second operation mode.
- the method 500 may further include: operating the at least one local oscillator at a first clock frequency when the hardware circuit is configured for the first operation mode; and operating the at least one local oscillator at a second clock frequency when the hardware circuit is configured for the second operation mode.
- the method 500 may further include: receiving a satellite signal, by the hardware front-end circuit, when the hardware circuit is configured for the first operation mode; and receiving a terrestrial beacon signal, by the hardware front-end circuit, when the hardware circuit is configured for the second operation mode.
- the method 500 may further include: processing the satellite signal based on a global navigation satellite system functionality when the hardware circuit is configured for the first operation mode; and processing the terrestrial beacon signal based on a terrestrial beacon system functionality when the hardware circuit is configured for the second operation mode.
- the terrestrial beacon system functionality may include an in-door call locating functionality.
- the terrestrial beacon system functionality may include an emergency call locating functionality.
- the emergency call locating functionality may include an e911 service functionality.
- the method 500 may further include: storing the first hardware capability set in a hardware capability storage when the hardware circuit is configured for the second operation mode; and storing the second hardware capability set in the hardware capability storage when the hardware circuit is configured for the first operation mode.
- the method 500 may further include retrieving a content of the hardware capability storage responsive to the hardware capability change request.
- the method 500 may further include receiving the hardware capability change request from an upper layer circuit of the cellular handset device or from a cellular network.
- the method 500 may further include: forwarding the hardware capability change request received from the upper layer circuit to the cellular network; and changing the operation mode of the hardware circuit responsive to an acknowledgement to the hardware capability change request from the cellular network.
- the method 500 may further include acknowledging a change of the operation mode of the hardware circuit to the upper layer circuit.
- the method 500 may further include reapplying the forwarding of the hardware capability change request to the cellular network upon receiving a Non-Acknowledgement to the hardware capability change request from the cellular network until a stopping criterion expires.
- the stopping criterion may include a reception of a predetermined number of Non-Acknowledgements to the reapplied forwarding of the hardware capability change request.
- the method 500 may include reporting the Non-Acknowledgement to the upper layer circuit responsive to the expiration of the stopping criterion.
- DSP Digital Signal Processors
- ASIC application specific integrated circuit
- Embodiments described in this disclosure can be implemented in digital electronic circuitry, or in computer hardware, firmware, software, or in combinations thereof, e.g. in available hardware of mobile devices or in new hardware dedicated for processing the methods described herein.
- the present disclosure also supports a computer program product including computer executable code or computer executable instructions that, when executed, causes at least one computer to execute the performing and computing blocks described herein, in particular the methods described above with respect to Figs. 4 and 5 and the computing blocks described above with respect to Figures 2 and 3 .
- a computer program product may include a non-transient readable storage medium storing program code thereon for use by a processor, the program code comprising instructions for performing the methods or the computing blocks as described above.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Telephone Function (AREA)
- Mobile Radio Communication Systems (AREA)
Claims (13)
- Zellulare Handgerätvorrichtung, die Folgendes umfasst:eine konfigurierbare Hardware-Schaltung (202), die konfiguriert ist, ein empfangenes Satellitensignal (210) gemäß einer ersten Hardware-Fähigkeitsgruppe (211) zu verarbeiten, wenn sie für eine erste Betriebsart konfiguriert ist, und ein empfangenes terrestrisches Baken-Signal (220) gemäß einer zweiten Hardware-Fähigkeitsgruppe (212) zu verarbeiten, wenn sie für eine zweite Betriebsart konfiguriert ist; undeinen Hardware-Manager (320), der konfiguriert ist, eine Betriebsart der konfigurierbaren Hardware-Schaltung (202) zwischen der ersten Betriebsart und der zweiten Betriebsart als Reaktion auf eine Hardware-Fähigkeitsänderungsanforderung (322) zu wechseln,wobei die Hardware-Fähigkeitsänderungsanforderung (322) von einem zellularen Netz ausgelöst wird oder durch eine höhere Anwendungsschicht der zellularen Handgerätvorrichtung ausgelöst wird undwobei die Hardware-Schaltung (202) eine Empfangskette umfasst, wobei die Empfangskette eine Antennenschaltung (311), eine Hardware-Frontend-Schaltung (313), mindestens einen Mischer (315) und mindestens einen Lokaloszillator (317) umfasst, die konfiguriert sind, die erste Hardware-Fähigkeitsgruppe (211) zu unterstützen, wenn die Hardware-Schaltung (202) für die erste Betriebsart konfiguriert ist, und die konfiguriert sind, die zweite Hardware-Fähigkeitsgruppe (212) zu unterstützen, wenn die Hardware-Schaltung (202) für die zweite Betriebsart konfiguriert ist.
- Zellulare Handgerätvorrichtung nach Anspruch 1,
wobei die Hardware-Frontend-Schaltung (313) konfiguriert ist, in einem ersten Frequenzband zu arbeiten, wenn die Hardware-Schaltung (202) für die erste Betriebsart konfiguriert ist, und in einem zweiten Frequenzband zu arbeiten, wenn die Hardware-Schaltung (202) für die zweite Betriebsart konfiguriert ist. - Zellulare Handgerätvorrichtung nach Anspruch 1 oder 2,
wobei der mindestens eine Lokaloszillator (317) konfiguriert ist, bei einer ersten Taktfrequenz zu arbeiten, wenn die Hardware-Schaltung (202) für die erste Betriebsart konfiguriert ist, und bei einer zweiten Taktfrequenz zu arbeiten, wenn die Hardware-Schaltung (202) für die zweite Betriebsart konfiguriert ist. - Zellulare Handgerätvorrichtung nach einem der vorhergehenden Ansprüche,
wobei die Hardware-Frontend-Schaltung (313) konfiguriert ist, das Satellitensignal (210) zu empfangen, wenn die Hardware-Schaltung (202) für die erste Betriebsart konfiguriert ist, und das terrestrische Baken-Signal (220) zu empfangen, wenn die Hardware-Schaltung (202) für die zweite Betriebsart konfiguriert ist. - Zellulare Handgerätvorrichtung nach Anspruch 4,
wobei die Hardware-Schaltung (202) eine Navigationsschaltung umfasst, die konfiguriert ist, das Satellitensignal (210) anhand einer Funktionalität eines globalen Navigationssatellitensystems zu verarbeiten, wenn die Hardware-Schaltung (202) für die erste Betriebsart konfiguriert ist, und das terrestrische Baken-Signal (220) anhand einer Funktionalität eines terrestrischen Baken-Systems zu verarbeiten, wenn die Hardware-Schaltung (202) für die zweite Betriebsart konfiguriert ist. - Zellulare Handgerätvorrichtung nach Anspruch 5,
wobei die Funktionalität des terrestrischen Baken-Systems eine Anrufslokalisierungsfunktionalität im Haus umfasst. - Zellulare Handgerätvorrichtung nach Anspruch 5 oder 6,
wobei die Funktionalität des terrestrischen Baken-Systems eine Notruflokalisierungsfunktionalität umfasst. - Zellulare Handgerätvorrichtung nach Anspruch 7,
wobei die Notruflokalisierungsfunktionalität eine e911-Dienstfunktionalität umfasst. - Zellulare Handgerätvorrichtung nach einem der vorhergehenden Ansprüche, die Folgendes umfasst:
einen Hardwarefähigkeitsspeicher, der konfiguriert ist, die erste Hardware-Fähigkeitsgruppe (211) zu speichern, wenn die Hardware-Schaltung (202) für die zweite Betriebsart konfiguriert ist, und die zweite Hardware-Fähigkeitsgruppe (212) zu speichern, wenn die Hardware-Schaltung (202) für die erste Betriebsart konfiguriert ist. - Zellulare Handgerätvorrichtung nach Anspruch 9,
wobei der Hardware-Manager (320) konfiguriert ist, einen Inhalt des Hardware-Fähigkeitsspeichers als Reaktion auf die Hardware-Fähigkeitsänderungsanforderung (322) zu erfassen. - Zellulare Handgerätvorrichtung nach einem der vorhergehenden Ansprüche,
wobei der Hardware-Manager (320) konfiguriert ist, die Hardware-Fähigkeitsänderungsanforderung (322) von einer Schaltung einer oberen Schicht der zellularen Handgerätvorrichtung oder von einem zellularen Netz zu empfangen. - Verfahren zum Betreiben einer zellularen Handgerätvorrichtung, die eine konfigurierbare Hardware-Schaltung (202) umfasst, wobei das Verfahren Folgendes umfasst:Verarbeiten eines empfangenen Satellitensignals (210) durch die konfigurierbare Hardware-Schaltung (202) gemäß einer ersten Hardware-Fähigkeitsgruppe (211), wenn eine Betriebsart der konfigurierbaren Hardware-Schaltung (202) für eine erste Betriebsart konfiguriert ist;Ändern der Betriebsart der konfigurierbaren Hardware-Schaltung (202) zwischen der ersten Betriebsart und einer zweiten Betriebsart als Reaktion auf eine Hardware-Fähigkeitsänderungsanforderung (322), wobei die Hardware-Fähigkeitsänderungsanforderung (322) von einem zellularen Netz ausgelöst wird oder durch eine höhere Anwendungsschicht der zellularen Handgerätvorrichtung ausgelöst wird; undVerarbeiten eines empfangenen terrestrischen Baken-Signals (220) durch die konfigurierbare Hardware-Schaltung (202) gemäß einer zweiten Hardware-Fähigkeitsgruppe (212), wenn die Betriebsart der konfigurierbaren Hardware-Schaltung (202) für die zweite Betriebsart konfiguriert ist,wobei die Hardware-Schaltung (202) eine Empfangskette umfasst, wobei die Empfangskette eine Antennenschaltung (311), eine Hardware-Frontend-Schaltung (313), mindestens einen Mischer (315) und mindestens einen Lokaloszillator (317) umfasst, die konfiguriert sind, die erste Hardware-Fähigkeitsgruppe (211) zu unterstützen, wenn die Hardware-Schaltung (202) für die erste Betriebsart konfiguriert ist, und die konfiguriert sind, die zweite Hardware-Fähigkeitsgruppe (212) zu unterstützen, wenn die Hardware-Schaltung (202) für die zweite Betriebsart konfiguriert ist.
- Computerlesbares nicht transitorisches Medium, auf dem Computeranweisungen gespeichert sind, die dann, wenn sie durch einen Computer ausgeführt werden, bewirken, dass der Computer das Verfahren nach Anspruch 12, ausführt.
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
EP16204075.2A EP3337042B1 (de) | 2016-12-14 | 2016-12-14 | Zellulare handapparatvorrichtung |
PCT/US2017/062158 WO2018111490A1 (en) | 2016-12-14 | 2017-11-17 | Cellular handset device |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
EP16204075.2A EP3337042B1 (de) | 2016-12-14 | 2016-12-14 | Zellulare handapparatvorrichtung |
Publications (2)
Publication Number | Publication Date |
---|---|
EP3337042A1 EP3337042A1 (de) | 2018-06-20 |
EP3337042B1 true EP3337042B1 (de) | 2020-11-25 |
Family
ID=57629277
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
EP16204075.2A Active EP3337042B1 (de) | 2016-12-14 | 2016-12-14 | Zellulare handapparatvorrichtung |
Country Status (2)
Country | Link |
---|---|
EP (1) | EP3337042B1 (de) |
WO (1) | WO2018111490A1 (de) |
Family Cites Families (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5940438A (en) * | 1997-02-18 | 1999-08-17 | Mitsubishi Electric Information Technology Center America, Inc (Ita) | Universal modem for digital video, audio and data communications |
US7916816B2 (en) * | 2006-05-12 | 2011-03-29 | Broadcom Corporation | Hardware allocation in a multi-channel communication environment |
US7859453B2 (en) * | 2008-06-30 | 2010-12-28 | Qualcomm Incorporated | Multiple radio device having adaptable mode navigation radio |
US8467738B2 (en) * | 2009-05-04 | 2013-06-18 | Rfaxis, Inc. | Multi-mode radio frequency front end module |
US8199051B2 (en) * | 2009-12-18 | 2012-06-12 | Trueposition, Inc. | Satellite positioning receiver and proxy location system |
US9651675B2 (en) * | 2010-02-12 | 2017-05-16 | Avago Technologies General Ip (Singapore) Pte. Ltd. | Estimating frequency of a GNSS enabled device based on time stamps |
ES2375388B1 (es) * | 2010-03-29 | 2013-01-29 | Vodafone España S.A.U | Entidad controladora de red de acceso por radio. |
EP3139193A1 (de) * | 2012-06-05 | 2017-03-08 | NextNav, LLC | Systeme und verfahren zur standortbestimmung einer benutzervorrichtung |
US20150133171A1 (en) * | 2013-11-12 | 2015-05-14 | Blackberry Limited | Method and system for implementing a dual-mode dual-band gnss/m-lms pseudolites receiver |
-
2016
- 2016-12-14 EP EP16204075.2A patent/EP3337042B1/de active Active
-
2017
- 2017-11-17 WO PCT/US2017/062158 patent/WO2018111490A1/en active Application Filing
Non-Patent Citations (1)
Title |
---|
None * |
Also Published As
Publication number | Publication date |
---|---|
EP3337042A1 (de) | 2018-06-20 |
WO2018111490A1 (en) | 2018-06-21 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US11317375B2 (en) | Communication coordination and collision mitigation for multi-subscriber identity module devices | |
EP3913979A1 (de) | Verfahren zur bestimmung des verfolgungsbereichs, endgerät und kernnetzwerkgerät | |
CN109769412B (zh) | 配置频率优先级的方法、终端设备、基站和核心网设备 | |
KR102209453B1 (ko) | 데이터 전송 방법 및 장치 | |
AU2016298524A1 (en) | Sharing an antenna between LTE-U and WLAN | |
US20230025902A1 (en) | Methods and apparatus for measurement gap activation and deactivation for positioning measurements | |
EP4017190B1 (de) | Ressourcenkonfigurationsverfahren und zugangsnetzwerkvorrichtung | |
US8761802B2 (en) | Apparatuses and methods for reporting positioning information of a mobile communications device | |
EP3255941B1 (de) | Verfahren und vorrichtung zur positionierung eines mobilen endgeräts | |
JP2021192519A (ja) | 情報伝送のための方法、端末デバイス及びネットワークデバイス | |
EP3337042B1 (de) | Zellulare handapparatvorrichtung | |
US20230108216A1 (en) | Wireless communication method, terminal device and network device | |
CN114501610B (zh) | 小区同步方法及装置 | |
US8849208B2 (en) | Apparatus, method and radio system | |
EP3461208A1 (de) | Verfahren und vorrichtung zur ressourcenzuweisung | |
US8744518B2 (en) | Mechanism for reducing time away from packet switched operation in a single radio solution | |
CN117941428A (zh) | 用于侧链路定位的方法及设备 | |
US9585121B2 (en) | Method and apparatus for simulcasting within a communication system | |
WO2019003798A1 (ja) | 無線通信装置及び電波干渉の回避方法 | |
JP2003250176A (ja) | 基地局選択方式 | |
WO2023130224A1 (en) | Method for updating system information | |
KR20200120610A (ko) | 통신 방법, 네트워크 디바이스 및 단말기 디바이스 | |
WO2023078402A1 (zh) | 通信方法、装置及计算机可读存储介质 | |
WO2024032235A1 (zh) | 通信方法和通信装置 | |
CN109479184B (zh) | 传输数据的方法、设备和可读存储介质 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
PUAI | Public reference made under article 153(3) epc to a published international application that has entered the european phase |
Free format text: ORIGINAL CODE: 0009012 |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: REQUEST FOR EXAMINATION WAS MADE |
|
17P | Request for examination filed |
Effective date: 20161214 |
|
AK | Designated contracting states |
Kind code of ref document: A1 Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR |
|
AX | Request for extension of the european patent |
Extension state: BA ME |
|
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: 20190412 |
|
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: 20200626 |
|
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: 1339462 Country of ref document: AT Kind code of ref document: T Effective date: 20201215 |
|
REG | Reference to a national code |
Ref country code: DE Ref legal event code: R096 Ref document number: 602016048471 Country of ref document: DE |
|
REG | Reference to a national code |
Ref country code: IE Ref legal event code: FG4D |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: FR Payment date: 20201125 Year of fee payment: 5 Ref country code: GB Payment date: 20201203 Year of fee payment: 5 |
|
REG | Reference to a national code |
Ref country code: NL Ref legal event code: FP |
|
REG | Reference to a national code |
Ref country code: AT Ref legal event code: MK05 Ref document number: 1339462 Country of ref document: AT Kind code of ref document: T Effective date: 20201125 |
|
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: 20201125 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: 20210325 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: 20210225 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: 20210226 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: 20201125 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: SE Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20201125 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: 20201125 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: 20210225 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: 20201125 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: 20201125 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: 20210325 |
|
REG | Reference to a national code |
Ref country code: LT Ref legal event code: MG9D |
|
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: 20201125 |
|
REG | Reference to a national code |
Ref country code: DE Ref legal event code: R081 Ref document number: 602016048471 Country of ref document: DE Owner name: INTEL CORPORATION, SANTA CLARA, US Free format text: FORMER OWNER: INTEL IP CORPORATION, SANTA CLARA, CA, US |
|
REG | Reference to a national code |
Ref country code: NL Ref legal event code: PD Owner name: INTEL CORPORATION; US Free format text: DETAILS ASSIGNMENT: CHANGE OF OWNER(S), ASSIGNMENT; FORMER OWNER NAME: INTEL IP CORPORATION Effective date: 20210623 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
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: 20201125 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: 20201125 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: 20201125 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: 20201125 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: 20201125 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: 20201125 |
|
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: 602016048471 Country of ref document: DE |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: DK Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20201125 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: 20201125 |
|
REG | Reference to a national code |
Ref country code: BE Ref legal event code: MM Effective date: 20201231 |
|
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: 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: 20201125 Ref country code: IE Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20201214 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: 20201125 Ref country code: LU Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20201214 |
|
26N | No opposition filed |
Effective date: 20210826 |
|
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: 20201231 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: 20201125 Ref country code: CH Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20201231 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
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: 20201125 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: IS Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20210325 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: 20201125 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: 20201125 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: 20201125 |
|
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: 20201125 |
|
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: 20201231 |
|
GBPC | Gb: european patent ceased through non-payment of renewal fee |
Effective date: 20211214 |
|
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: 20211214 |
|
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: 20211231 |
|
P01 | Opt-out of the competence of the unified patent court (upc) registered |
Effective date: 20230518 |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: NL Payment date: 20230925 Year of fee payment: 8 |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: DE Payment date: 20230919 Year of fee payment: 8 |