EP3410787B1 - Niedrigleistungsprotokoll mit niedriger latenz zum datenaustausch - Google Patents

Niedrigleistungsprotokoll mit niedriger latenz zum datenaustausch Download PDF

Info

Publication number
EP3410787B1
EP3410787B1 EP18186076.8A EP18186076A EP3410787B1 EP 3410787 B1 EP3410787 B1 EP 3410787B1 EP 18186076 A EP18186076 A EP 18186076A EP 3410787 B1 EP3410787 B1 EP 3410787B1
Authority
EP
European Patent Office
Prior art keywords
processing
low power
shared memory
power state
data
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
EP18186076.8A
Other languages
English (en)
French (fr)
Other versions
EP3410787A1 (de
Inventor
Andy I-Fong Yu
Honghao Liu
Andrei Tudorancea
Zeeshan Asad Sardar
Lakshmi Narayana Macha
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 EP3410787A1 publication Critical patent/EP3410787A1/de
Application granted granted Critical
Publication of EP3410787B1 publication Critical patent/EP3410787B1/de
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H04W52/02—Power saving arrangements
    • H04W52/0209—Power saving arrangements in terminal devices
    • H04W52/0225—Power saving arrangements in terminal devices using monitoring of external events, e.g. the presence of a signal
    • H04W52/0229—Power saving arrangements in terminal devices using monitoring of external events, e.g. the presence of a signal where the received signal is a wanted signal
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/40—Bus networks
    • H04L12/40006—Architecture of a communication node
    • H04L12/40039—Details regarding the setting of the power status of a node according to activity on the bus
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H04W52/02—Power saving arrangements
    • H04W52/0209—Power saving arrangements in terminal devices
    • H04W52/0251—Power saving arrangements in terminal devices using monitoring of local events, e.g. events related to user activity
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D30/00—Reducing energy consumption in communication networks
    • Y02D30/70—Reducing energy consumption in communication networks in wireless communication networks

Definitions

  • the present disclosure generally relates to wireless communications and, more particularly, to methods of effecting power savings for wireless devices during periodic data exchanges.
  • Wireless communication systems are widely deployed to provide various types of communication content such as voice, data, and so on. These systems may be multiple-access systems capable of supporting communications with multiple users by sharing the available system resources (e.g., bandwidth and transmit power). Examples of such multiple-access systems include Code Division Multiple Access (CDMA) systems, Time Division Multiple Access (TDMA) systems, Frequency Division Multiple Access (FDMA) systems, 3rd Generation Partnership Project (3GPP) Long Term Evolution (LTE) systems and Orthogonal Frequency Division Multiple Access (OFDMA) systems.
  • CDMA Code Division Multiple Access
  • TDMA Time Division Multiple Access
  • FDMA Frequency Division Multiple Access
  • 3GPP 3rd Generation Partnership Project
  • LTE Long Term Evolution
  • OFDMA Orthogonal Frequency Division Multiple Access
  • Devices connected to a wireless communication system may be configured to perform searches for limited service and camp on limited services on an available radio access technology (RAT) to provide for emergency service access. Searching for and camping on limited service may be performed regardless of whether a device is a voice capable or non-voice capable device.
  • RAT radio access technology
  • US 2011/183727 A1 , US 2007/140199 A1 and US 2006/146769 D1 disclose devices comprising two processing entities, whereby the first processing entity provides timing information to the second processing entity to indicate when the next message exchange occurs between the two entities.
  • the two processing entities exchange messages via a shared memory space. Based on the provided timing information, the processing entities exit a low power state in order to process the message exchange and enter the low power state again afterwards.
  • Certain aspects of the present disclosure provide a method for processing data on a processing entity of a device according to independent claim 1.
  • Performing data exchange between data subsystems using a shared memory and a timer may provide for power savings for wireless devices during predictable and/or periodic data exchanges.
  • a CDMA network may implement a radio technology such as Universal Terrestrial Radio Access (UTRA), cdma2000, etc.
  • UTRA includes Wideband CDMA (WCDMA), Time Division Synchronous CDMA (TD-SCDMA), and other variants of CDMA.
  • cdma2000 covers IS-2000, IS-95 and IS-856 standards.
  • a TDMA network may implement a radio technology such as Global System for Mobile Communications (GSM).
  • GSM Global System for Mobile Communications
  • An OFDMA network may implement a radio technology such as Evolved UTRA (E-UTRA), Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM®, etc.
  • E-UTRA Evolved UTRA
  • UMB Ultra Mobile Broadband
  • IEEE 802.11 Wi-Fi
  • WiMAX IEEE 802.16
  • Flash-OFDM® Flash-OFDM®
  • UTRA and E-UTRA are part of Universal Mobile Telecommunication System (UMTS).
  • 3GPP Long Term Evolution (LTE) and LTE-Advanced (LTE-A) in both frequency division duplexing (FDD) and time division duplexing (TDD), are new releases of UMTS that use E-UTRA, which employs OFDMA on the downlink and SC-FDMA on the uplink.
  • LTE Long Term Evolution
  • LTE-A LTE-Advanced
  • FDD frequency division duplexing
  • TDD
  • UTRA, E-UTRA, UMTS, LTE, LTE-A and GSM are described in documents from an organization named "3rd Generation Partnership Project” (3GPP).
  • CDMA 2000 and UMB are described in documents from an organization named “3rd Generation Partnership Project 2" (3GPP2).
  • the techniques described herein may be used for the wireless networks and radio technologies mentioned above as well as other wireless networks and radio technologies. For clarity, certain aspects of the techniques are described below for LTE, and LTE terminology is used in much of the description below. It should be noted that the descriptions are also applicable to other technologies with different terminologies.
  • FIG. 1 shows a wireless communication network 100 in which aspects of the present disclosure may be practiced.
  • user equipments (UEs) 110 may use the techniques described herein to save power while performing predictable and/or periodic operations.
  • wireless communication network 100 includes multiple wireless networks having overlapping coverage.
  • An evolved universal terrestrial radio access network (E-UTRAN) 120 may support LTE and may include a number of evolved Node Bs (eNBs) 122 and other network entities that can support wireless communication for user equipments 110 (UEs). Each eNB 122 may provide communication coverage for a particular geographic area.
  • the term "cell" can refer to a coverage area of an eNB and/or an eNB subsystem serving this coverage area.
  • a serving gateway (S-GW) 124 may communicate with E-UTRAN 120 and may perform various functions such as packet routing and forwarding, mobility anchoring, packet buffering, initiation of network-triggered services, etc.
  • a mobility management entity (MME) 126 may communicate with E-UTRAN 120 and serving gateway 124 and may perform various functions such as mobility management, bearer management, distribution of paging messages, security control, authentication, gateway selection, etc.
  • the network entities in LTE are described in 3GPP TS 36.300, entitled “Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description,” which is publicly available.
  • a radio access network (RAN) 130 may support GSM and may include a number of base stations 132 and other network entities that can support wireless communication for UEs.
  • a mobile switching center (MSC) 134 may communicate with the RAN 130 and may support voice services, provide routing for circuit-switched calls, and perform mobility management for UEs located within the area served by MSC 134.
  • an inter-working function (IWF) 140 may facilitate communication between MME 126 and MSC 134 (e.g., for 1xCSFB).
  • E-UTRAN 120, serving gateway 124, and MME 126 may be part of an LTE network 102.
  • RAN 130 and MSC 134 may be part of a GSM network 104.
  • FIG. 1 shows only some network entities in the LTE network 102 and the GSM network 104.
  • the LTE and GSM networks may also include other network entities that may support various functions and services.
  • any number of wireless networks may be deployed in a given geographic area.
  • Each wireless network may support a particular RAT and may operate on one or more frequencies.
  • a RAT may also be referred to as a radio technology, an air interface, etc.
  • a frequency may also be referred to as a carrier, a frequency channel, etc.
  • Each frequency may support a single RAT in a given geographic area in order to avoid interference between wireless networks of different RATs.
  • a UE 110 may be stationary or mobile and may also be referred to as a mobile station, a terminal, an access terminal, a subscriber unit, a station, etc.
  • UE 110 may be a cellular phone, a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, etc.
  • PDA personal digital assistant
  • WLL wireless local loop
  • UE 110 may search for wireless networks from which it can receive communication services. If more than one wireless network is detected, then a wireless network with the highest priority may be selected to serve UE 110 and may be referred to as the serving network. UE 110 may perform registration with the serving network, if necessary. UE 110 may then operate in a connected mode to actively communicate with the serving network. Alternatively, UE 110 may operate in an idle mode and camp on the serving network if active communication is not required by UE 110.
  • UE 110 may be located within the coverage of cells of multiple frequencies and/or multiple RATs while in the idle mode.
  • UE 110 may select a frequency and a RAT to camp on based on a priority list.
  • This priority list may include a set of frequencies, a RAT associated with each frequency, and a priority of each frequency.
  • the priority list may include three frequencies X, Y and Z. Frequency X may be used for LTE and may have the highest priority, frequency Y may be used for GSM and may have the lowest priority, and frequency Z may also be used for GSM and may have medium priority.
  • the priority list may include any number of frequencies for any set of RATs and may be specific for the UE location.
  • UE 110 may be configured to prefer LTE, when available, by defining the priority list with LTE frequencies at the highest priority and with frequencies for other RATs at lower priorities, e.g., as given by the example above.
  • UE 110 may operate in the idle mode as follows. UE 110 may identify all frequencies/RATs on which it is able to find a "suitable” cell in a normal scenario or an "acceptable” cell in an emergency scenario, where "suitable” and “acceptable” are specified in the LTE standards. UE 110 may then camp on the frequency/RAT with the highest priority among all identified frequencies/RATs. UE 110 may remain camped on this frequency/RAT until either (i) the frequency/RAT is no longer available at a predetermined threshold or (ii) another frequency/RAT with a higher priority reaches this threshold.
  • This operating behavior for UE 110 in the idle mode is described in 3GPP TS 36.304, entitled “Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) procedures in idle mode," which is publicly available.
  • E-UTRA Evolved Universal Terrestrial Radio Access
  • UE User Equipment
  • UE 110 may be able to receive packet-switched (PS) data services from LTE network 102 and may camp on the LTE network while in the idle mode.
  • LTE network 102 may have limited or no support for voice-over-Internet protocol (VoIP), which may often be the case for early deployments of LTE networks. Due to the limited VoIP support, UE 110 may be transferred to another wireless network of another RAT for voice calls. This transfer may be referred to as circuit-switched (CS) fallback.
  • UE 110 may be transferred to a RAT that can support voice service such as 1xRTT, WCDMA, GSM, etc.
  • UE 110 may initially become connected to a wireless network of a source RAT (e.g., LTE) that may not support voice service.
  • the UE may originate a voice call with this wireless network and may be transferred through higher-layer signaling to another wireless network of a target RAT that can support the voice call.
  • the higher-layer signaling to transfer the UE to the target RAT may be for various procedures, e.g., connection release with redirection, PS handover, etc.
  • FIG. 2 shows a block diagram of a design of UE 110, eNB 122, and MME 126 in FIG. 1 .
  • an encoder 212 may receive traffic data and signaling messages to be sent on the uplink. Encoder 212 may process (e.g., format, encode, and interleave) the traffic data and signaling messages.
  • a modulator (Mod) 214 may further process (e.g., symbol map and modulate) the encoded traffic data and signaling messages and provide output samples.
  • a transmitter (TMTR) 222 may condition (e.g., convert to analog, filter, amplify, and frequency upconvert) the output samples and generate an uplink signal, which may be transmitted via an antenna 224 to eNB 122.
  • antenna 224 may receive downlink signals transmitted by eNB 122 and/or other eNBs/base stations.
  • a receiver (RCVR) 226 may condition (e.g., filter, amplify, frequency downconvert, and digitize) the received signal from antenna 224 and provide input samples.
  • a demodulator (Demod) 216 may process (e.g., demodulate) the input samples and provide symbol estimates.
  • a decoder 218 may process (e.g., deinterleave and decode) the symbol estimates and provide decoded data and signaling messages sent to UE 110.
  • Encoder 212, modulator 214, demodulator 216, and decoder 218 may be implemented by a modem processor 210. These units may perform processing in accordance with the RAT (e.g., LTE, 1xRTT, etc.) used by the wireless network with which UE 110 is in communication.
  • the RAT e.g., LTE, 1xRTT, etc.
  • a controller/processor 230 may direct the operation at UE 110. Controller/processor 230 may also perform or direct other processes for the techniques described herein. Controller/processor 230 may also perform or direct the processing by UE 110 in FIG. 3 .
  • Memory 232 may store program codes and data for UE 110. Memory 232 may also store a priority list and configuration information.
  • a transmitter/receiver 238 may support radio communication with UE 110 and other UEs.
  • a controller/processor 240 may perform various functions for communication with the UEs.
  • the uplink signal from UE 110 may be received via an antenna 236, conditioned by receiver 238, and further processed by controller/processor 240 to recover the traffic data and signaling messages sent by UE 110.
  • traffic data and signaling messages may be processed by controller/processor 240 and conditioned by transmitter 238 to generate a downlink signal, which may be transmitted via antenna 236 to UE 110 and other UEs.
  • Controller/processor 240 may also perform or direct other processes for the techniques described herein. Controller/processor 240 may also perform or direct the processing by eNB 122 in FIG. 3 .
  • Memory 242 may store program codes and data for the base station.
  • a communication (Comm) unit 244 may support communication with MME 126 and/or other network entities.
  • a controller/processor 250 may perform various functions to support communication services for UEs.
  • Memory 252 may store program codes and data for MME 126.
  • a communication unit 254 may support communication with other network entities.
  • FIG. 2 shows simplified designs of UE 110, eNB 122, and MME 126.
  • each entity may include any number of transmitters, receivers, processors, controllers, memories, communication units, etc.
  • Other network entities may also be implemented in similar manner.
  • Wireless devices typically can perform data operations that may be predictable and/or periodic, such as Voice over LTE (VoLTE) or Video Telephony over LTE (VTLTE).
  • Operations such as VoLTE or VTLTE may have predetermined packet exchange times that may be used to reduce the number of times an RF device (e.g., a modem) is woken up but keep round-trip delays within reasonable limits.
  • RF device e.g., a modem
  • power savings may be realized using Connected Mode Discontinuous Reception (CDRX), in which a device turns off a radio and places a modem into a low-power state (e.g., sleep state) for different durations depending on, for example, talk, listen, and silence states.
  • CDRX may also entail switching from a 20ms packet exchange to a 40ms packet exchange periodicity to reduce the number of times an RF device is woken up and keep round-trip delays within reasonable limits.
  • synchronizing data exchanges between subsystems may entail synchronizing data exchanges without one subsystem causing another to wake up at the wrong time, which may negate possible power savings. Additionally, power savings may be realized by reducing software layering delays, improving system jitter handling, reducing interrupt frequencies, improving the accuracy of data synchronization, and allowing for seamless switching between different buffering sizes.
  • GPIO general purpose input/output
  • data reception and transmission may be predictable and periodic. These applications include, for example, audio/video transmission, sensors, bus protocols (e.g., high speed inter-chip), or network interface operations (e.g., polling modes). Data may include control or event information as well as user data.
  • bus protocols e.g., high speed inter-chip
  • network interface operations e.g., polling modes.
  • Data may include control or event information as well as user data.
  • IPC inter-process communications
  • aspects of the present disclosure may help to save power by synchronizing timing between processing subsystems and activating subsystems when data is expected to be processed. Power savings may be realized, for example, by allowing processing subsystems to independently schedule when to exit a low power state to check a shared memory space for messages to process. The processing subsystems may be in a low power state for as much time as possible.
  • Dynamic voltage and clock switching may be completely enabled.
  • System clocks need not be maintained at nominal settings to support IPC between subsystems. Further, clock rates need not be increased, for example, to prevent preemption of critical tasks by processing interrupts in an interrupt service routine or interrupt service thread context.
  • aspects of the present disclosure may allow for high IPC performance, regardless of system clock rate changes.
  • Message delivery and reception may be processed using the resources of each processing subsystem independently.
  • Subsystems may be operated using the lowest clock rate possible, even under a combination of critical and non-critical IPCs.
  • Processing priority may be governed by the sender or receiver thread's priority.
  • aspects of the present disclosure may allow for minimal latency and layering overheads, as processing subsystems may directly read data just before the data is needed. For example, round trip delays for GSM voice calls may be reduced by up to 4.615ms due to aligning the processing of data to modulation and demodulation times rather than to the beginning of the closest TDMA frame processing timeline.
  • Message delivery and reception may be highly precise, as work completion may be expected before a specified time.
  • Message delivery and reception may be robust to system jitter as well, as a processing subsystem can be configured to read expired buffers in shared memory spaces while the overall system moves forward in real time.
  • polling-based algorithms may be replaced with time stamp-based algorithms, which may further avoid wasted processing cycles.
  • the server can write, to a data buffer (or series of data buffers) a data unit and a timestamp associated with the data unit.
  • the client-side timer handler periodically wakes the client up to read expired buffers from the transmit buffer.
  • the client can determine the amount of clock skew that must be compensated for during execution. Based on the amount of clock skew, the client can program its own time to cause buffers for the receiver and transmit sides to perform faster or slower.
  • changes in the periodicity at which packets are received and written is captured from the amount of time compensation applied on the client side, and generation of packets can be modified based on the amount of compensation applied on the client side.
  • VFR vocoder frame reference
  • PCM pulse code modulation
  • Hardware designs may eliminate dedicated VFR interrupts and allow for simpler modem-voice hardware (e.g., multiple SIM, multiple active modems) designs. Synchronization of high-resolution time references between processing subsystems may be performed without using interrupts in a steady state. Reducing the use of interrupts may provide support for IPC in both kernel-space and user-space contexts.
  • aspects of the present disclosure may allow for dynamic changes to buffering granularity. For example, in VoLTE operations, switching between 20ms and 40ms modes can be performed seamlessly. The voice subsystem need not be stopped for reconfiguration, which may reduce the frequency and length of audio gaps during VoLTE operations.
  • Polling-based algorithms may be replaced with time stamp-based algorithms, which may further avoid wasted processing cycles.
  • the operations described herein may be fully asynchronous and allow for the emulation of isochronous-like operations.
  • Time synchronization between processing subsystems may provide for accurate audio/video synchronization.
  • FIG. 3 illustrates example operations that may be performed by a first processing entity of a wireless device to implement a low power, low latency protocol for predictable and/or periodic data exchange.
  • operations 300 begin at 302, where the first processing entity provides timing information to a second processing entity indicating when the second processing entity is to next process a message exchange between the first and second processing entities using a shared memory space.
  • the first processing entity takes action to exit a low power state, based on the timing information, to access the shared memory space to process the message exchange.
  • the first processing entity enters the low power state after processing the message exchange.
  • the first processing entity and second processing entity may be configured to independently receive, process, and send messages, and the first and second processing entities may be configured to enter a low power mode independently.
  • the timing information may be provided via a shared memory space.
  • a shared memory space may entail, for example, shared memory or interfaces that act like shared memory (e.g., a low latency interface).
  • Taking action to exit a low power state may comprise programming a timer local to a processing entity.
  • this timer may be configured to cause a processing entity to exit a low power state just before data is scheduled to be processed.
  • Timers local to a processing entity may be standard timers and need not be implemented using specialized hardware.
  • Each processing entity e.g., the first and second processing entities
  • the first processing entity may comprise a modem subsystem and the second processing entity may comprise a voice subsystem.
  • the modem and voice subsystems may adjust the timing information to switch between different rates of packet exchanges between the subsystems.
  • the different rates may correspond to 20ms and 40ms VoLTE packet exchange modes.
  • timing information may be designed to ensure that the voice processing system provides vocoder packets or pulse code modulation (PCM) samples to the shared memory space prior to the first processing entity exiting the low power state, and taking action to exit the low power state may comprise taking action to ensure the first processing entity exits the low power state in time to process the vocoder packets or PCM samples for transmission.
  • PCM pulse code modulation
  • taking action to exit the low power state may comprise taking action to ensure the first processing entity exits the low power state in time to demodulate received signals, and the timing information may be designed to ensure that the voice processing system exits a low power state to process the demodulated received signals.
  • the first and second processing entities may reside on a same integrated circuit, different integrated circuits, or as part of a common processor. In some aspects, the first and second processing entities may be connected via a bus, such as a serial bus.
  • the first processing system may be considered a client system and the second processing system may be considered a server system, as the first processing system may be configured to generate or receive data and provide that data to the second processing system.
  • the first processing system may comprise, for example, a modem or a data provider (e.g., a camera, microphone, etc.), and the corresponding second processing system may comprise, for example, a voice processing system or a playback device, respectively.
  • the roles of the first and second processing systems may be reversed, for example, depending on whether the system, as a whole, is receiving or transmitting data.
  • FIG. 4 is a block diagram of an example system 400 for low power, low latency data exchange.
  • System 400 may operate according to the operations described in FIG. 3 .
  • the system 400 may have a first processing system 402, a second processing system 404, and a shared memory space 406.
  • first processing system 402 may provide timing information to second processing system 404 indicating when second processing system 404 is to next process a message exchange between first processing system 402 and second processing system 404 using shared memory space 406.
  • first processing system 402 may write data to shared memory space 406 just before second processing system 404 reads data from shared memory space 406. After writing data to shared memory space 406, first processing system 402 may enter the low power state.
  • FIG. 5 illustrates a block diagram of an example system 500 for low power, low latency data exchange in the voice data (e.g., VoLTE) context.
  • the first processing system 402 described in FIG. 4 may comprise modem 502, and the second processing system 404 described in FIG. 4 may comprise vocoder system 504.
  • modem 502 may read vocoder packets, PCM samples, and the like from shared memory space 406, modulate the packet, and transmit the modulated packet to another device, and vocoder system 504 may write vocoder packets or PCM samples to shared memory space 406.
  • modem 502 may demodulate received packets and write the demodulated packets to shared memory space 406, and vocoder system 504 may read data from shared memory space 406.
  • aspects of the present disclosure may also be used for low power, low latency data exchange in the video or graphics contexts.
  • sound and video can be captured from capture devices (e.g., a webcam and a microphone) and processed at a first processing system for transmission to a second processing system. While a video telephony call is being performed, capture and processing of data by the first processing system may continue on a regular basis. For example, data exchange may be scheduled every n frames of video, where n is a positive number.
  • the first processing system can generate packets to be used in providing multimedia or entertainment content to a user.
  • multimedia or entertainment content may be exchanged on a frame-by-frame basis.
  • the periodicity of data exchange may be calculated to provide for smooth playback of graphics and sound.
  • the periodicity of data exchange may be calculated based on the format of the data to be exchanged (e.g., video frames encoded at 1080p/24fps may be exchanged with a different periodicity than video frames encoded at 1080p/60fps).
  • FIG. 6 illustrates a message flow diagram 600 illustrating messages that may be exchanged between a first and a second processing entity for low power, low latency data exchange according to aspects of the present disclosure.
  • the first processing subsystem may be a server
  • the second processing subsystem may be a client. Operations utilizing the methods described herein may be broadly described in terms of an initialization stage, steady-state operations stage, and termination stage.
  • a first processing subsystem and second processing subsystem may synchronize clocks and provide buffers for use on the transmit and receive paths.
  • the client system transmits an optional setup message 602 to the server system.
  • a clock associated with the client may be synchronized with a clock associated with the server.
  • the server may transmit a synchronization request message 604 requesting the client to synchronize a clock associated with the client with a clock associated with the server.
  • the client may then transmit a server time request message 606 requesting the server's time and receive the server's time via message 608.
  • the client programs its own clock and timer and transmits a message 610 instructing the server to program the server's timer.
  • the server may autonomously transmit a request 604 to the client to re-synchronize with the server (e.g., rather than waiting for a setup message 602).
  • the client can transmit start command 612 to begin steady-state operations (e.g., the generation of messages written to shared memory by the server system, and the reading of messages stored in shared memory by the client system, as discussed herein).
  • start command 612 e.g., the generation of messages written to shared memory by the server system, and the reading of messages stored in shared memory by the client system, as discussed herein).
  • the client and server systems can enter a low power (sleep) state.
  • the server system may wake up when the server timer expires to generate data and access the shared memory.
  • the server system may write the generated data to shared memory and read any data that a client system may have previously written to the shared memory.
  • the server system can re-enter a low power (sleep) state until the next time the server timer expires.
  • the client system may wake up when the client timer expires (at a time at which the client system may expect data to be present in shared memory) and read the contents of the shared memory.
  • the client system may also generate data to be written to shared memory.
  • the client system may access the shared memory to read data written to shared memory by the server system and, if applicable, write generated data to shared memory.
  • the client system can set the next wakeup time, write the client system's next wakeup time to shared memory, and enter a low power (sleep) state until the client timer reaches the next wakeup time.
  • the server and client devices may be active and draw power when data is to be written to or read from shared memory and inactive when the server and client devices are waiting to write to or read from shared memory, thus lowering power usage.
  • the client and server systems may provide buffers to be used during steady-state operations.
  • the buffers may be first-in, first-out structures, where the earliest packet of data written to a buffer is the first packet removed and read from the buffer.
  • the client can provide the transmit side with one or more empty buffers for the server to store data, and the server can provide one or more buffers on the receive side for data to be processed by the client.
  • buffers On the transmit side, buffers may be provided to support a set transmission period, and additional buffers may be provided to provide additional time for the client to process data before freeing a buffer to receive data from the server.
  • the server may store a timestamp indicating when data is provided to a buffer.
  • the client can mark data with timestamps set in the future and can mark empty buffers to signify that the server should perform, for example, error concealment or silence.
  • the client and server may program their respective local timers to wake up and deliver data just in time before the other subsystem needs to read the buffer. Waking up and delivering data just in time may be supported due to a client programming data exchange timestamps on each buffer and the use of absolute time to program both the client and server timers, which allows for accurate timing and corrections to be performed on each cycle to avoid accumulated time drift.
  • the client for example, a modem
  • the client may supply three buffers for a server (for example, a voice subsystem) to store encoded vocoder packets.
  • Two buffers, each of a 20ms duration, may be used to buffer data for the 40ms vocoder packet exchange period.
  • An optional additional 20ms buffer may be used to provide an additional 20ms for the client to process data before freeing a buffer back to the server for encoding.
  • the client and server can continually read and write to the receive and transmit side buffers, respectively.
  • the client-side timer can cause the client to periodically wake up to read expired transmit side buffers and supply empty buffers to the server.
  • the client-side timer may also cause the client to periodically wake up to write data to the receive side buffers for the server to decode.
  • the server-side timer can cause the server to periodically wake up to write encoded data into the transmit buffers before the buffers expire and may cause the server to read data from the receive side buffers at the expiry to decode received data.
  • the client may be given control to correct timing drift between the network time and device time. Drift may be caused due to the network time and device time being generated from different clock crystals, which may eventually cause the network time and device time to drift.
  • the client may read the capture time from expired transmit-side buffers to detect average clock drift between the client clock and server clock. The client can return the data exchange between the client and server to the original timeline by programming buffer expirations to be earlier or later.
  • the server can detect changes to periodicity and change the data rate to match the amount of time compensation that may be needed to correct for timing drift.
  • the voice subsystem can provide encoded data to a modem in the transmit side buffers, and a modem can provide data to the voice subsystem for decoding in the receive side buffers.
  • the voice subsystem can employ sample slipping and stuffing algorithms over longer durations of time to mask or conceal the effects of time correction to the user.
  • data exchanged between the client and server can include audio, encoded using various codecs, and video frames, which may or may not be encoded.
  • Multimedia playback and recording can include audio and video playback, recording, or transcoding, as well as camera or camcorder recording.
  • Playback may comprise a client subsystem writing encoded data to the receive side buffers, which may decode the encoded data and output the decoded data to one or more output devices.
  • Recording may comprise a client subsystem writing data into the transmission side buffers.
  • Transcoding operations may entail use of both receive side and transmission side buffers. Data to be transcoded may be placed into the receive side buffers, and transcoded data may be read from the transmission side buffers.
  • Sensor data may be recorded from, for example, gyroscopes, global navigation satellite system (e.g., GPS, GLONASS, GALILEO, etc.) devices, magnetic sensors, and the like.
  • Sensor data can be recorded to the transmit side buffers, and a client can read recorded data from the transmit side buffers. The client may read recorded data at any time and may be forced to read recorded data when the transmit side buffers become full.
  • the server can interrupt the client to cause the client to re-sync; after the client re-syncs, interrupt-less steady state operations may proceed.
  • Increased amounts of memory may allow a server to capture more data before the client is interrupted to read and empty a full buffer.
  • Buffering sensor data may allow application processors to read sensor data whenever the application processors desire to instead of being forced to read at certain intervals, which may prevent or delay the execution of system critical tasks.
  • the client can flush out any data remaining in the transmit side and receive side buffers.
  • the client and server devices may subsequently be placed in a low-power mode (e.g., a sleep state) until operations involving the client and server devices are initiated again (e.g., the device is used for a new VoLTE or VTLTE call).
  • 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 software module may reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, 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.
  • the storage medium may be integral to the processor.
  • the processor and the storage medium may reside in an ASIC.
  • the ASIC may reside in a user terminal.
  • the processor and the storage medium may reside as discrete components in a user terminal.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Transceivers (AREA)
  • Telephone Function (AREA)

Claims (15)

  1. Ein Verfahren für Verarbeitung durch eine erste Verarbeitungseinheit (402) einer Einrichtung, das Folgendes aufweist:
    Vorsehen (302) von Timing-Information an eine zweite Verarbeitungseinheit (404), die anzeigt, wann die zweite Verarbeitungseinheit als nächstes einen Nachrichtenaustausch zwischen der ersten und der zweiten Verarbeitungseinheit verarbeiten wird unter Verwendung eines gemeinsam verwendeten Speicherraums (406, 506), wobei die erste Verarbeitungseinheit ein Modemsubsystem (502) aufweist und die zweite Verarbeitungseinheit ein Sprachsubsystem (504) aufweist;
    Ergreifen einer Maßnahme (304), um einen Niedrigleistungszustand zu verlassen, basierend auf der Timing-Information, um auf den gemeinsam verwendeten Speicherraum (406, 506) zuzugreifen, um den Nachrichtenaustausch zu verarbeiten, wobei die Timing-Information ausgelegt ist um sicherzustellen, dass das Sprachsubsystem (504) Vocoderpaket-Samples bzw. -Abtastungen an den gemeinsam verwendeten Speicherraum vorsieht, bevor das Modemsubsystem (502) den Niedrigleistungszustand verlässt, und wobei das Ergreifen einer Maßnahme, um den Niedrigleistungszustand zu verlassen, Ergreifen einer Maßnahme aufweist, um sicherzustellen, dass das Modemsubsystem den Niedrigleistungszustand rechtzeitig verlässt, um die Vocoderpaketabtastungen zu verarbeiten; und
    Eintreten (306) in den Niedrigleistungszustand nach Verarbeiten des Nachrichtenaustauschs.
  2. Verfahren nach Anspruch 1, wobei:
    die Einrichtung eine Drahtloseinrichtung aufweist; und
    die erste (402) und zweite (404) Verarbeitungseinheit konfiguriert sind zum Verarbeiten von Aufgaben in Bezug auf Drahtloskommunikationen.
  3. Verfahren nach Anspruch 1, wobei die erste (402) und zweite (404) Verarbeitungseinheit konfiguriert sind zum Verarbeiten von Aufgaben in Bezug auf Multimediaverarbeitung oder Verarbeiten von Sensordaten.
  4. Verfahren nach Anspruch 1, wobei die Timing-Information über den gemeinsam verwendeten Speicherraum (406, 506) vorgesehen wird.
  5. Verfahren nach Anspruch 1, wobei der gemeinsam verwendete Speicherraum (406, 506) wenigstens eines von einem gemeinsam verwendeten physischen Speicher oder einer Schnittstelle mit geringer Latenz aufweist.
  6. Verfahren nach Anspruch 1, wobei das Ergreifen einer Maßnahme zum Verlassen eines Niedrigleistungszustand das Programmieren eines Timers, der lokal für wenigstens eine von der ersten oder zweiten Verarbeitungseinrichtung ist, aufweist.
  7. Verfahren nach Anspruch 1, das weiter Anpassen der Timing-Information aufweist, um zwischen unterschiedlichen Raten von Paketaustauschvorgängen zwischen dem Modem und Sprachsubsystemen zu wechseln.
  8. Verfahren nach Anspruch 1, wobei die unterschiedlichen Raten Dauern für einen Paketaustausch entsprechen, der für Kommunikationen von Sprache über LTE (LTE = long term evolution) oder Videotelefonie über LTE genutzt wird.
  9. Eine Vorrichtung, die Folgendes aufweist:
    eine erste Verarbeitungseinheit (402), die konfiguriert ist zum:
    Vorsehen von Timing-Information an eine zweite Verarbeitungseinheit (404), die anzeigt, wann die zweite Verarbeitungseinheit als nächstes einen Nachrichtenaustausch zwischen der ersten und zweiten Verarbeitungseinheit verarbeiten wird unter Verwendung eines gemeinsam verwendeten Speicherraums (406, 506), wobei die erste Verarbeitungseinheit ein Modemsubsystem (502) aufweist und die zweite Verarbeitungseinheit ein Sprachsubsystem (504) aufweist;
    Ergreifen einer Maßnahme um einen Niedrigleistungszustand zu verlassen, basierend auf der Timing-Information, um auf den gemeinsam verwendeten Speicherraums (406, 506) zuzugreifen, um den Nachrichtenaustausch zu verarbeiten, wobei die Timing-Information ausgelegt ist um sicherzustellen, dass das Sprachsubsystem (504) Vocoderpaket-Samples bzw. -Abtastungen an den gemeinsam verwendeten Speicherraum vorsieht, bevor das Modemsubsystem den Niedrigleistungszustand verlässt, und wobei das erste Verarbeitungssystems konfiguriert ist zum Ergreifen einer Maßnahme, um den Niedrigleistungszustand zu verlassen durch Ergreifen einer Maßnahme, um sicherzustellen, dass das Modemsubsystem (502) den Niedrigleistungszustand rechtzeitig verlässt, um die Vocoderpaketabtastungen zu verarbeiten; und
    Eintreten in den Niedrigleistungszustand nach Verarbeiten des Nachrichtenaustauschs;
    die zweite Verarbeitungseinheit (404); und
    einen gemeinsam verwendeten Speicher.
  10. Vorrichtung nach Anspruch 9, wobei:
    die Vorrichtung eine Drahtloseinrichtung aufweist; und
    die erste (402) und zweite (404) Verarbeitungseinheit konfiguriert sind zum Verarbeiten von Aufgaben in Bezug auf Drahtloskommunikationen.
  11. Vorrichtung nach Anspruch 9, wobei die Timing-Information über den gemeinsam verwendeten Speicherraum (406, 506) vorgesehen wird.
  12. Vorrichtung nach Anspruch 9, wobei das erste Verarbeitungssystem (402) konfiguriert ist zum Ergreifen einer Maßnahme zum Verlassen des Niedrigleistungszustandes durch Programmieren eines Timers, der lokal für wenigstens eine von der ersten oder zweiten Verarbeitungseinheit ist.
  13. Vorrichtung nach Anspruch 9, wobei die erste Verarbeitungseinheit weiter konfiguriert ist zum Anpassen der Timing-Information um zwischen unterschiedlichen Raten von Paketaustauschvorgängen zwischen dem Modem und Sprachsubsystemen zu wechseln.
  14. Vorrichtung nach Anspruch 9, wobei die unterschiedlichen Raten Dauern für einen Paketaustausch entsprechen, der für Kommunikationen von Sprache über LTE (LTE = long term evolution) oder Videotelefonie über LTE genutzt wird.
  15. Ein computerlesbares Medium, das von einem Computer ausführbaren Code zur Verarbeitung durch eine erste Verarbeitungseinheit (402) einer Einrichtung speichert, der Code aufweist zum Durchführen eines der Verfahren der Ansprüche 1 bis 8.
EP18186076.8A 2014-02-20 2015-02-20 Niedrigleistungsprotokoll mit niedriger latenz zum datenaustausch Active EP3410787B1 (de)

Applications Claiming Priority (5)

Application Number Priority Date Filing Date Title
US201461942512P 2014-02-20 2014-02-20
US201461948074P 2014-03-05 2014-03-05
US14/626,539 US10200951B2 (en) 2014-02-20 2015-02-19 Low power low latency protocol for data exchange
PCT/US2015/016790 WO2015127184A1 (en) 2014-02-20 2015-02-20 Low power low latency protocol for data exchange
EP15708400.5A EP3108703B1 (de) 2014-02-20 2015-02-20 Niedrigleistungsprotokoll mit niedriger latenz zum datenaustausch

Related Parent Applications (2)

Application Number Title Priority Date Filing Date
EP15708400.5A Division-Into EP3108703B1 (de) 2014-02-20 2015-02-20 Niedrigleistungsprotokoll mit niedriger latenz zum datenaustausch
EP15708400.5A Division EP3108703B1 (de) 2014-02-20 2015-02-20 Niedrigleistungsprotokoll mit niedriger latenz zum datenaustausch

Publications (2)

Publication Number Publication Date
EP3410787A1 EP3410787A1 (de) 2018-12-05
EP3410787B1 true EP3410787B1 (de) 2019-11-06

Family

ID=53799357

Family Applications (2)

Application Number Title Priority Date Filing Date
EP15708400.5A Active EP3108703B1 (de) 2014-02-20 2015-02-20 Niedrigleistungsprotokoll mit niedriger latenz zum datenaustausch
EP18186076.8A Active EP3410787B1 (de) 2014-02-20 2015-02-20 Niedrigleistungsprotokoll mit niedriger latenz zum datenaustausch

Family Applications Before (1)

Application Number Title Priority Date Filing Date
EP15708400.5A Active EP3108703B1 (de) 2014-02-20 2015-02-20 Niedrigleistungsprotokoll mit niedriger latenz zum datenaustausch

Country Status (6)

Country Link
US (1) US10200951B2 (de)
EP (2) EP3108703B1 (de)
JP (1) JP6549139B2 (de)
KR (1) KR20160122239A (de)
CN (2) CN110225577A (de)
WO (1) WO2015127184A1 (de)

Families Citing this family (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9357409B2 (en) * 2012-09-21 2016-05-31 Azimuth Systems, Inc. System level emulation of TD-SCDMA wireless networks
CN108028830B (zh) * 2015-09-18 2021-06-08 索尼移动通讯有限公司 无线电终端以及流传输调度装置中执行的方法和终端
CN108476383B (zh) * 2016-07-27 2021-02-05 华为技术有限公司 一种最大打包间隔的协商方法、装置以及存储介质
CN106535307B (zh) * 2016-10-31 2019-10-25 努比亚技术有限公司 一种串口休眠方法及终端
CN106535306B (zh) * 2016-10-31 2019-10-29 努比亚技术有限公司 一种休眠控制方法及终端
CN106572521B (zh) * 2016-10-31 2020-04-10 努比亚技术有限公司 一种串口唤醒方法及终端
US10624033B2 (en) * 2017-07-17 2020-04-14 Qualcomm Incorporated Voice over internet protocol power conservation techniques for wireless systems
KR102539720B1 (ko) 2018-01-09 2023-06-01 주식회사 케이티 VoLTE 단말의 코덱 변경 장치 및 방법
JP6766836B2 (ja) * 2018-03-07 2020-10-14 カシオ計算機株式会社 衛星電波受信装置、電子時計及び電波受信報知制御方法
US20220256623A1 (en) * 2021-02-05 2022-08-11 Parallel Wireless, Inc. GTPC (S11 and S5 Interface) Optimization for EPC Core Nodes

Family Cites Families (24)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6089456A (en) * 1995-06-07 2000-07-18 E-Comm Incorporated Low power telecommunication controller for a host computer server
US7062303B2 (en) 2001-07-05 2006-06-13 Intel Corporation Synchronizing power conservation modes
US6889331B2 (en) * 2001-08-29 2005-05-03 Analog Devices, Inc. Dynamic voltage control method and apparatus
US7898994B2 (en) 2002-02-25 2011-03-01 Hewlett-Packard Development Company, L.P. Power saving in multi-processor device
US7623894B2 (en) * 2003-10-09 2009-11-24 Freescale Semiconductor, Inc. Cellular modem processing
US6973052B2 (en) * 2003-12-19 2005-12-06 Motorola, Inc. Hybrid power save delivery method in a wireless local area network for real time communication
US7623028B2 (en) * 2004-05-27 2009-11-24 Lawrence Kates System and method for high-sensitivity sensor
US20060146769A1 (en) 2004-12-31 2006-07-06 Patel Anil N Method of operating a WLAN mobile station
US7500128B2 (en) 2005-05-11 2009-03-03 Intel Corporation Mobile systems with seamless transition by activating second subsystem to continue operation of application executed by first subsystem as it enters into sleep mode
US8441972B2 (en) * 2005-11-16 2013-05-14 Qualcomm Incorporated WCDMA device and method for discontinuous reception for power saving in idle mode and flexible monitoring of neighboring cells
US8515052B2 (en) * 2007-12-17 2013-08-20 Wai Wu Parallel signal processing system and method
JP2009301500A (ja) * 2008-06-17 2009-12-24 Nec Electronics Corp タスク処理システム及びタスク処理方法
US8141024B2 (en) * 2008-09-04 2012-03-20 Synopsys, Inc. Temporally-assisted resource sharing in electronic systems
CN102065577A (zh) 2009-11-13 2011-05-18 英业达股份有限公司 手持式通信装置及其封包管理方法
JP5499735B2 (ja) * 2010-01-28 2014-05-21 富士通モバイルコミュニケーションズ株式会社 携帯端末
CN101827088B (zh) * 2010-03-15 2013-03-27 北京航空航天大学 基于cpu总线互联的底层通信协议实现方法
JP2011235493A (ja) * 2010-05-07 2011-11-24 Seiko Epson Corp 通信装置
US8706172B2 (en) * 2010-10-26 2014-04-22 Miscrosoft Corporation Energy efficient continuous sensing for communications devices
US8799697B2 (en) 2011-09-26 2014-08-05 Qualcomm Incorporated Operating system synchronization in loosely coupled multiprocessor system and chips
US9107049B2 (en) * 2012-05-11 2015-08-11 D2 Technologies, Inc. Advanced real-time IP communication in a mobile terminal
US8639253B2 (en) * 2012-06-19 2014-01-28 Ecrio, Inc. Real-time communications client architecture
US8923880B2 (en) * 2012-09-28 2014-12-30 Intel Corporation Selective joinder of user equipment with wireless cell
TWI530215B (zh) * 2013-02-05 2016-04-11 蘋果公司 減少連接模式不連續接收之功率消耗
US20150009874A1 (en) * 2013-07-08 2015-01-08 Amazon Technologies, Inc. Techniques for optimizing propagation of multiple types of data

Non-Patent Citations (1)

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

Also Published As

Publication number Publication date
JP6549139B2 (ja) 2019-07-24
CN106031252A (zh) 2016-10-12
US20150237580A1 (en) 2015-08-20
CN110225577A (zh) 2019-09-10
CN106031252B (zh) 2019-05-10
EP3108703A1 (de) 2016-12-28
EP3108703B1 (de) 2018-09-19
KR20160122239A (ko) 2016-10-21
EP3410787A1 (de) 2018-12-05
WO2015127184A1 (en) 2015-08-27
US10200951B2 (en) 2019-02-05
JP2017512408A (ja) 2017-05-18

Similar Documents

Publication Publication Date Title
EP3410787B1 (de) Niedrigleistungsprotokoll mit niedriger latenz zum datenaustausch
US11324069B2 (en) Methods, devices, and systems for discontinuous reception for a shortened transmission time interval and processing time
US9713192B2 (en) Device and method for processing audio data
EP2820896B1 (de) Optimierung von signalisierungslast-overhead und batterieverbrauch für hintergrundanwendungen
US20150103817A1 (en) Global time synchronization server for wireless devices
CN114271021B (zh) 用于确定非连续接收持续定时器的启动状态的方法及设备
US9955422B2 (en) User equipment power optimization
US20100135209A1 (en) Reception cycle control method, radio base station, and mobile station
GB2493713A (en) Discontinuous (DRX/DTX) operation of a wireless device, where uplink frames are sent at the same time as downlink frames are received
JP7431991B2 (ja) 制御チャネルの監視なしのデータ受信
CN118303114A (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: THE APPLICATION HAS BEEN PUBLISHED

AC Divisional application: reference to earlier application

Ref document number: 3108703

Country of ref document: EP

Kind code of ref document: P

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

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

Free format text: STATUS: REQUEST FOR EXAMINATION WAS MADE

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

17P Request for examination filed

Effective date: 20190411

RBV Designated contracting states (corrected)

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

INTG Intention to grant announced

Effective date: 20190522

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

AC Divisional application: reference to earlier application

Ref document number: 3108703

Country of ref document: EP

Kind code of ref document: P

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

Ref country code: AT

Ref legal event code: REF

Ref document number: 1200599

Country of ref document: AT

Kind code of ref document: T

Effective date: 20191115

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

Country of ref document: DE

REG Reference to a national code

Ref country code: NL

Ref legal event code: MP

Effective date: 20191106

REG Reference to a national code

Ref country code: LT

Ref legal event code: MG4D

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

Ref country code: NO

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

Effective date: 20200206

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

REG Reference to a national code

Ref country code: DE

Ref legal event code: R097

Ref document number: 602015041474

Country of ref document: DE

REG Reference to a national code

Ref country code: AT

Ref legal event code: MK05

Ref document number: 1200599

Country of ref document: AT

Kind code of ref document: T

Effective date: 20191106

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

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

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

REG Reference to a national code

Ref country code: CH

Ref legal event code: PL

26N No opposition filed

Effective date: 20200807

REG Reference to a national code

Ref country code: BE

Ref legal event code: MM

Effective date: 20200229

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

Ref country code: MC

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

Effective date: 20191106

Ref country code: LU

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

Effective date: 20200220

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

Ref country code: CH

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

Effective date: 20200229

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

Ref country code: LI

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

Effective date: 20200229

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

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

Ref country code: IE

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

Effective date: 20200220

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

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

Ref country code: FR

Payment date: 20210120

Year of fee payment: 7

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

Ref country code: DE

Payment date: 20210113

Year of fee payment: 7

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

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

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

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

REG Reference to a national code

Ref country code: DE

Ref legal event code: R119

Ref document number: 602015041474

Country of ref document: DE

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

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

Ref country code: DE

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

Effective date: 20220901

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

Ref country code: GB

Payment date: 20240111

Year of fee payment: 10