EP3573307A1 - Multi-packet-protokoll-header-detektion - Google Patents

Multi-packet-protokoll-header-detektion Download PDF

Info

Publication number
EP3573307A1
EP3573307A1 EP19172633.0A EP19172633A EP3573307A1 EP 3573307 A1 EP3573307 A1 EP 3573307A1 EP 19172633 A EP19172633 A EP 19172633A EP 3573307 A1 EP3573307 A1 EP 3573307A1
Authority
EP
European Patent Office
Prior art keywords
packet
preamble
header
packets
guard
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.)
Granted
Application number
EP19172633.0A
Other languages
English (en)
French (fr)
Other versions
EP3573307B1 (de
Inventor
Michael W. O'brien
Sudarshan Onkar
Joshua J. Nekl
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.)
Analog Devices International ULC
Original Assignee
Analog Devices Global ULC
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 Analog Devices Global ULC filed Critical Analog Devices Global ULC
Publication of EP3573307A1 publication Critical patent/EP3573307A1/de
Application granted granted Critical
Publication of EP3573307B1 publication Critical patent/EP3573307B1/de
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/22—Parsing or analysis of headers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/74—Address processing for routing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/28—Timers or timing mechanisms used in protocols
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W56/00—Synchronisation arrangements
    • H04W56/0055—Synchronisation arrangements determining timing error of reception due to propagation delay
    • H04W56/0065—Synchronisation arrangements determining timing error of reception due to propagation delay using measurement of signal travel time
    • H04W56/007—Open loop measurement
    • H04W56/0075—Open loop measurement based on arrival time vs. expected arrival time
    • H04W56/0085—Open loop measurement based on arrival time vs. expected arrival time detecting a given structure in the signal
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/80—Services using short range communication, e.g. near-field communication [NFC], radio-frequency identification [RFID] or low energy communication

Definitions

  • Embodiments of the present disclosure relate to communications and, in particular, to data communication that involves processing packets.
  • FSK frequency-shift keying
  • GFSK Gaussian frequency-shift keying
  • a receive device can receive an FSK signal that includes packets and process the packets.
  • the FSK signal can be configured as a multi-packet transmission.
  • the packets can each include a preamble, a synchronization header, and a payload. There are technical challenges associated with detecting the synchronization header in certain applications.
  • the communication device comprises a receive signal path and a receiver control circuit in communication with the receive signal path.
  • the receive signal path is configured to provide a receive signal comprising a multi-packet exchange and a guard preamble between successive packets within the multi-packet exchange.
  • the successive packets include a first packet and a second packet following the first packet.
  • the receiver control circuit is configured to trigger a timer associated with detecting a header of the second packet in response to detecting an end of a preamble of the second packet.
  • the receiver control circuit is configured to detect the header of the second packet.
  • the timer can have a timeout threshold that is less than a duration of the preamble and the header of the second packet.
  • the timer can have a timeout threshold that is less than or equal to 125% of a duration of the header of the second packet.
  • the receive signal path can include an analog-to-digital converter and a bit recovery circuit having an input coupled to an output of the analog to digital converter.
  • the bit recovery circuit can generate bits that represent the packets and the guard preamble and to provide the bits to the receiver control circuit.
  • the receive signal path can be configured to receive and process a frequency shift keying signal.
  • the header can be a synchronization header.
  • the packets and the guard preamble can be in accordance with a multi-packet Bluetooth protocol.
  • the communication device can include a digital baseband processor configured to demodulate data bits of the second packet in response to the header of the second packet being detected by the receiver control circuit.
  • the receiver control circuit can include a digital state machine.
  • Another aspect of this disclosure is a method of detecting a header in a multi-packet bit stream with guard preambles between packets.
  • the method includes receiving a bit stream comprising a multi-packet exchange and a guard preamble between successive packets within the multi-packet exchange.
  • the successive packets include a first packet and a second packet following the first packet.
  • the method includes detecting an end of a preamble of the second packet.
  • the method includes triggering a timer in response to the detecting the end of the preamble of the second packet.
  • the method also includes detecting a header of the second packet before the timer reaches a timeout threshold.
  • the method can include setting the timeout threshold to a duration that is less than a duration of the preamble and the header of the second packet.
  • the method can include setting the timeout threshold to a duration that is less than or equal to 125% of a duration of the header of the second packet.
  • the method can include performing automatic frequency correction while the guard preamble is being processed.
  • the method can include demodulating data of the second packet in response to the detecting the header of the second packet.
  • the method can include encountering a failure for the first packet such that the first packet is missed.
  • the receiver system comprises a receive signal path and a receiver control circuit in communication with the receive signal path.
  • the receive signal path is configured to provide a receive signal comprising packets and a guard preamble between successive packets of the packets.
  • the successive packets comprise a first packet and a second packet following the first packet.
  • the receiver control circuit is configured to trigger a timer for detecting a synchronization header of the second packet, wherein a timeout threshold of the timer corresponds to less than a duration of the preamble and the header of the second packet.
  • the receiver control circuit is configured to detect the synchronization header of the second packet.
  • the timeout threshold can have a duration that is less than or equal to 125% of a duration of the header of the second packet.
  • the receive signal path can include a downconverter, an analog-to-digital converter, and a bit recovery circuit having an input coupled to an output of the analog to digital converter.
  • the bit recovery circuit is configured to generate bits that represent the packets and the guard and to provide the bits to the receiver system control circuit.
  • the receiver control circuit can include a digital state machine.
  • the receiver control circuit can include an automatic gain control circuit configured to provide automatic gain control for the receive signal path.
  • the receiver control circuit can include an automatic frequency correction circuit configured to provide automatic frequency correction for the receive signal path.
  • the header can be a synchronization header.
  • the packets and the guard preamble can be in accordance with a multi-packet Bluetooth protocol.
  • Multi-Packet support can be included in various communications protocols, such as Bluetooth Low Energy (BTLE) and BTLE related protocols. Multi-packet protocols can have enhanced data throughput relative to single-packet protocols.
  • BTLE Bluetooth Low Energy
  • Multi-packet protocols can have enhanced data throughput relative to single-packet protocols.
  • a guard-time can be included between adjacent packets, where a link is still transmitting at the link power.
  • a receiver can be powered while the guard preamble is being processed for multi-packet detection protocols.
  • the guard-time can be filled with a guard preamble.
  • This guard-preamble bit stream can include the same pattern of bits as a preamble. For instance, the guard preamble can be a sequence of alternating 0's and 1's.
  • the duration of the guard preamble may be unconstrained in the protocol.
  • the duration of the guard preamble can be variable.
  • the duration of the guard preamble prior to processing a multi-packet transmission, may be unknown to a receiving device arranged to receive and process the multi-packet transmission.
  • the guard preamble can have an indeterminate duration.
  • the indeterminate duration or length can be referred to an undefined length or duration as this length can be unconstrained by a protocol and also unknown to a receiving device prior to processing a multi-packet transmission.
  • the length of different guard preambles can be variable.
  • a receive device can be arranged to process a guard preamble having a variety of different lengths. With unconstrained length guard preambles, different guard preambles can have different durations.
  • a receive device can receive an FSK signal that includes packets and process the packets.
  • the FSK signal can include multiple packets with a guard preamble between successive packets.
  • the guard preamble can have a length that is undefined by a protocol.
  • the packets can each include a preamble and a synchronization header. There are technical challenged associated with detecting the synchronization header when there is a guard preamble of undefined length between successive packets.
  • Figure 1 is a diagram illustrating data of a multi-packet protocol that includes a guard preamble between successive packets.
  • Each packet includes at least a preamble, a synchronization header, and a payload.
  • a first guard preamble Guard Preamble 1 is included between a first packet Packet 1 and a second packet Packet 2. Accordingly, the guard preamble is between successive packets, in which the second packet Packet 2 is the next packet following a first packet Packet 1.
  • the first guard preamble Guard Preamble 1 can have a different length than a second guard preamble Guard Preamble 2 in certain applications. Both of the guard preambles can be a sequence of alternating binary values.
  • the preamble is included to allow time for detecting a signal (e.g., a Gaussian FSK signal), followed by a number of calibrations including, but not limited, to performing automatic gain control (AGC), and performing automatic frequency correction (AFC).
  • AGC automatic gain control
  • AFC automatic frequency correction
  • a synchronization header For a multi-packet protocol, it is generally desirable to detect a synchronization header for each packet and maintain a communication link.
  • the synchronization header is typically included in a packet after the preamble.
  • the synchronization header is known between paired communications devices.
  • a challenge with having an unknown and/or variable guard preamble duration can be setting a synchronization header timeout duration. If the synchronization header timeout duration is set too short, then the synchronization header timeout duration might not extend to the entire duration of the guard-preamble. On the other hand, if the synchronization header timeout duration is set too long, then the recovery time from a false signal detect could result in one or more legitimate packets being missed. False signal detects can be relatively common for BTLE links. It can be desirable to ensure that the recovery from a false signal detect be relatively quick. This can prevent one or more packets from being missed.
  • Figure 2 is a timing diagram associated with detecting a synchronization header in a multi-packet protocol with an undefined guard preamble duration.
  • a worked example for a problematic case caused by a long synchronization header timeout duration is shown in Figure 2 .
  • a synchronization header is not found and demodulation of the payload is not commenced.
  • the synchronization header detection signal SYNC_HEADER FOUND is not asserted in Figure 2 .
  • the example begins with a false signal being detected and a signal detect signal Sig_det being asserted in Event 1. Then AGC and AFC can run while respective enable signals AGC_en and AFC_en are asserted in Event 2. However, AGC and AFC will both likely converge to incorrect values.
  • a hunt can commence looking for the synchronization header SYNC_HEADER of the packet in Event 3 after AGC and AFC have been performed.
  • An actual packet can arrive after the hunt is commenced in Event 4.
  • the synchronization header timeout can expire while the actual packet is being processed in Event 5. This can occur when the synchronization header timeout SYNC_HEADER Timeout Timer reaches a threshold SYNC_HEADER Timeout Threshold.
  • the synchronization header timeout can have a relatively long duration to accommodate a relatively long guard preamble. The length of the synchronization header timeout in this example can cause legitimate packets to be missed.
  • the missing packet can still be present when the synchronization header timeout expires in Event 6 as illustrated in Figure 2 . This can cause the signal detect signal Sig_det to be asserted.
  • the synchronization header timeout timer can continue to run for a relatively long time without detecting a synchronization header in Event 7. This can cause more legitimate packets to be missed.
  • aspects of this disclosure relate to triggering a synchronization header timeout timer in response to detecting an end of a preamble of a packet and detecting a synchronization header of the packet.
  • Raw bits can be monitored in parallel to detect the end of the preamble and to detect the synchronization header.
  • the synchronization header can be hunted. If the synchronization header is found, then a state-machine can proceed to a subsequent phase of the demodulator.
  • a state-machine can look at the demodulated bits. If the demodulated bits are alternating 0's and 1's, then the assumption is that a preamble, which can be a guard preamble or a preamble of a packet, is present.
  • a synchronization header timeout timer can be triggered. This can accommodate the variability of the guard-preamble duration. As such, a synchronization header timeout threshold can be set to be moderately longer than an expected synchronization header duration. Accordingly, the synchronization header timeout threshold need not be excessively long.
  • the technology described herein can be implemented in any suitable communication device arranged to wireless communicate with another communication device. The communication device can receive a radio frequency signal via a antenna and process the received radio frequency signal.
  • the synchronization header timeout timer is associated with detecting a synchronization header of a packet.
  • the synchronization header timeout timer can run until a synchronization header is detected or until a synchronization header timeout threshold is reached.
  • the synchronization header timeout threshold can set an amount of time for which a receiver control circuit hunts for a synchronization header. If the synchronization header is not detected within the synchronization header timeout threshold, the synchronization header is not found.
  • the synchronization header timeout threshold is longer than the duration of the synchronization header.
  • the synchronization header timeout threshold can be shorter than the combined duration of a preamble and a synchronization header of a packet.
  • a packet can include a preamble of 8 microseconds and a synchronization header of 32 microseconds.
  • the synchronization header timeout threshold can be less than 40 microseconds (e.g., 38 microseconds) in accordance with the principles and advantages discussed herein.
  • the synchronization header timeout threshold can have a duration that is less than or equal to 125% of a duration of a synchronization header of a packet.
  • the synchronization header timeout threshold can have a duration that is less than or equal to 120% of a duration of a synchronization header of a packet.
  • the synchronization header timeout threshold can be relatively short in duration while a receiver system processes a multi-packet transmission that includes a guard preamble between successive packets.
  • FIG. 3 is a schematic block diagram of a receiver system 10 according to an embodiment.
  • the receiver system 10 includes an antenna 11, a radio frequency front end (RF FE) 12, a baseband filter 13, an analog-to-digital converter (ADC) 14, a channelization filter 15, a frequency conversion circuit 16, an adjustment circuit 17, a bit recovery circuit 18, and a receiver control circuit 20.
  • the receiver control circuit 20 can include a synchronization header detection circuit 21, a synchronization timer and preamble detection circuit 22, an automatic frequency control circuit 23, and an automatic gain control circuit 24.
  • the receiver control circuit 20 can be a state machine. Some or all of the functionality of the receiver control circuit 20 can be implemented by digital circuitry.
  • the antenna 11 can receive a radio frequency signal from a transmit device.
  • the radio frequency signal can be an FSK signal, such as a GFSK signal.
  • the FSK signal can be in accordance with a Bluetooth protocol, such as BTLE 4 or BLTE 5.
  • the antenna 11 can be implemented external to an integrated circuit that includes the other illustrated circuitry of the receiver.
  • the antenna 11 can be connected to the RF FE 12 by way of an integrated circuit contact.
  • the RF FE 12 can process the radio frequency signal.
  • the RF FE 12 can include a low noise amplifier and one or more filters.
  • the RF FE 12 can downconvert the processed RF signal to baseband.
  • the RF FE 12 can output an in-phase signal (I signal) and a quadrature signal (Q signal) that is 90° out of phase with the I signal
  • I signal in-phase signal
  • Q signal quadrature signal
  • the baseband filter 13 can filter an output signal of the RF FE 12.
  • the ADC 14 can convert an output signal provided by the baseband filter 13 to a digital signal.
  • the channelization filter 15 can filter an output of the ADC 14.
  • the output of the channelization filter 15 is connected to the frequency conversion circuit 16. While only one signal path from the RF FE 12 to the frequency conversion circuit 16 is shown in Figure 3 , an I path and a Q path can be included between the RF FE 12 and the frequency conversion circuit 16.
  • the frequency conversion circuit 16 can perform an arctangent (ATAN) function. This can convert an IQ signal to a phase.
  • the frequency conversion circuit 16 can perform an additional function, such as a differential function, to convert the phase to frequency.
  • the frequency conversion circuit 16 can convert processed I and Q signals to a frequency. Any suitable circuit that convert I and Q signals to a frequency can be implemented by the frequency conversion circuit 16.
  • the adjustment circuit 17 can adjust an output signal from the frequency conversion circuit 16 using a frequency correction signal provided by the automatic frequency correction circuit 23. This can correct for a frequency offset in a FSK signal received by the receiver system 10.
  • the adjustment circuit 17 can be a summer as illustrated.
  • the adjustment circuit 17 can perform any suitable operation (for example, addition, subtraction, the like, or any suitable combination thereof) to adjust an output signal from the frequency conversion circuit 16 based on the frequency correction signal from the automatic frequency correction circuit 23. For instance, the adjustment circuit 17 can subtract a frequency correction value from the output of the frequency conversion circuit 16.
  • the frequency correction signal can be determined while a guard preamble between successive packets is being processed.
  • the frequency correction signal can be set for the duration a packet.
  • a frequency corrected signal provided by the adjustment circuit 17 can be further processed.
  • the frequency corrected signal can be provided to the bit recovery circuit 18 that generates bits corresponding to the FSK signal received by the antenna 11.
  • a bit stream from the bit recovery circuit 18 can be provided to the synchronization header detection circuit 21.
  • the synchronization header detection circuit 21 can search for a synchronization header.
  • the synchronization header can be detected when a pattern in the bit stream matches the synchronization header.
  • the synchronization header can be predefined, for example, by a communications protocol.
  • the bit stream from the bit recovery circuit 18 can also be provided to the synchronization timer and preamble detection circuit 22.
  • the synchronization timer and preamble detection circuit 22 can detect an end of a preamble of a packet.
  • the end of the preamble of the packet can be detected when two bits of the bit stream have the same value following a sequence of alternating 0's and 1's. Accordingly, the end of the preamble can be detected based on one or more bits that follow the preamble in the packet.
  • the one or more bits can be part of a synchronization header. Accordingly, the end of the preamble of the packet can be detected in parallel with the synchronization header detection circuit 21 hunting for the synchronization header.
  • the synchronization header can be detected after the preamble is detected by detecting less than the entire synchronization header (e.g., 1 bit less than the full synchronization header or 2 bits less than the full synchronization header).
  • the preamble can be either 0101...01 or 1010...10.
  • the preamble that is used can depend on the first bit of the synchronization header. If the first bit of the synchronization header is 0, then the preamble can be 0101...01. If the first bit of the synchronization header is 1 then the preamble can be 1010... 10. Accordingly, there can be either a 01 or 10 transition going from the preamble to the synchronization header. As such, the expiration time can be 2 bits less than the full synchronization header and still detect the synchronization header.
  • the synchronization timer and preamble detection circuit 22 can receive an AFC completion signal AFC_done from the AFC circuit 23. In response to AFC being completed and the end of a preamble being detected, the synchronization timer and preamble detection circuit 22 can start the synchronization header timeout timer. The synchronization timer and preamble detection circuit 22 can provide the synchronization timer timeout signal SYNC_HEADER_TIMEOUT to the synchronization header detection circuit 21 to start the synchronization header timer. The synchronization header detection circuit 21 can assert a synchronization header detection signal SYNC_HEADER FOUND in response to detecting the synchronization header of the packet. This can cause a baseband processor to demodulate a payload of the packet.
  • the AFC circuit 23 can detect a frequency based on an instantaneous frequency contained in the guard preamble.
  • the AFC circuit 23 can include a state machine.
  • the AFC circuit 23 can generate frequency correction signal and provide the frequency correction signal to the adjustment circuit 17.
  • the frequency correction signal can be determined while the guard preamble between successive packets is being processed by the receiver system 10.
  • the frequency correction signal can be set for the duration of the packet.
  • the automatic gain control circuit 24 can receive a digital signal from the ADC 14 and adjust a gain of the RF FE 12 based on the digital signal. These operations can be performed while the guard preamble is being processed by the receiver system 10.
  • the automatic gain control circuit 24 can be implemented by a state machine.
  • the automatic gain control circuit 24 can send an automatic gain control completion signal ADG_done to the automatic frequency correction circuit 23.
  • Figure 4 is a timing diagram associated with receiving multiple packets for a functional case in the receiver system 10 of Figure 3 .
  • Figure 4 illustrates timing of signals in the receiver control circuit 20 for receiving 3 packets. This timing diagram illustrates how the receiver system 10 of Figure 3 can process multiple packets with a relatively short synchronization header timer.
  • the first packet Packet 1 is detected. This causes the signal detect signal Sig_det to be asserted.
  • AGC and AFC operations of the automatic frequency control circuit 23 and an automatic gain control circuit 24, respectively, are enabled in the receiver control circuit 20, as indicated by their respective control signals AGC_en and AFC en being asserted.
  • a preamble enable signal within the receiver control circuit 20 is asserted in response to the preamble being detected.
  • the preamble can be detected by detecting an alternating sequence of 1's and 0's of a sufficient length.
  • the preamble enable signal is de-asserted in response to an end of the preamble being detected.
  • the synchronization header timeout timer SOF Timeout Timer is triggered in response the end of the preamble being detected.
  • a Start of Frame flag (SOF) indicates whether a synchronization header has been found.
  • the SOF can correspond to the synchronization header detection signal SYNC HEADER FOUND.
  • the synchronization header is found by the receiver control circuit 20 before the synchronization header timeout timer SOF Timeout Timer reaches the SFO Timeout Threshold. Accordingly, the synchronization header for the first packet Packet 1 is found within the synchronization header timeout time and demodulation of the data of the packet can commence. Demodulation can commence in response to the the synchronization header detection signal SYNC_HEADER FOUND being asserted. The synchronization header detection signal SYNC_HEADER FOUND can be de-asserted at the end of the first packet Packet 1 as shown by the timing diagram of Figure 4 .
  • the signal detection signal Sig_det is asserted while the guard preamble is being processed.
  • AGC and AFC are then enabled by the respective control signals AGC en and AFC_en being asserted.
  • the preamble enable is then asserted while the guard preamble is being processed.
  • the synchronization header time is not asserted until the preamble enable signal is de-asserted.
  • the synchronization header timeout timer SOF Timeout Timer is triggered.
  • the synchronization header is detected for the second packet Packet 2 before the synchronization timer reaches a timeout threshold.
  • the data of the second packet Packet 2 commences in response to the synchronization header being found.
  • the receiver control circuit 20 can process the third packet Packet 3 similarly to the second packet Packet 2.
  • Figure 5 is a timing diagram associated with receiving multiple packets for a failing case in the receiver system 10 of Figure 3 .
  • Figure 5 illustrates timing of signals in the receiver control circuit 20 for receiving 3 packets in which there is a synchronization failure on the first packet.
  • This timing diagram illustrates how the receiver system 10 of Figure 3 can recover relatively quickly from a synchronization error failure and properly detect the next packet.
  • a preamble enable signal is asserted for a relatively short time in Event 51.
  • the synchronization header is not detected by the time that the synchronization header is finished being processed. Accordingly, the first packet Packet 1 will be lost.
  • the synchronization header timer timeout threshold is reached in Event 52. Accordingly, the SOF is not detected, which corresponds to an error scenario. This can cause digital state machines of the receiver control circuit 20 to reset in Event 53.
  • the signal detect signal Sig_det can be asserted again relatively soon in Event 54, as a packet is still being received.
  • AGC and AFC can be triggered again in Event 55.
  • the preamble is then found again in Event 56 while the first packet Packet 1 is being received.
  • the synchronization header timer is started again in Event 57 while the first packet Packet 1 is being received. The timer expires without the synchronization header being detected in Event 58.
  • the signal detect signal Sig_det is asserted again in Event 59 while the first guard preamble Guard Preamble 1 is being processed .
  • the second packet Packet 2 is processed like the second packet of Figure 4 .
  • the third packet Packet 3 is processed in Event 60 like the third packet of Figure 4 . Accordingly, only one packet is lost in the error case where there is a synchronization failure on the first packet in the worked case of Figure 5 .
  • recoverable failure cases include a variety of failure scenarios in a first packet, any type of failure in a second or subsequent packet, false signal detects, and the like. Failure scenarios on the first packet include late signal-detection, AGC errors, AFC measurement and/or correction errors, and the like. For these cases, the first packet will likely be missed, but all subsequent packets can be recoverable. Such recoveries can be similar to the recovery described with reference to Figure 5 . For failures in a second or subsequent packet, the failed packet will likely be lost, but all other packets can be recoverable. Using the technology described herein, a relatively quick decision can be made on whether the signal detect was false and the receiver state machine can speedily prepare and wait for the next signal detect event. This can provide a speedy recovery from false signal detects.
  • FIG. 6 is a schematic diagram of a receive signal chain 30 according to an embodiment.
  • the receive signal chain 30 includes a low noise amplifier (LNA) 32, a down converter 34, and a filtering and data conversion circuit 37.
  • the receive signal chain 30 is in communication with a receiver control circuit 20.
  • LNA low noise amplifier
  • the receive signal chain 30 is in communication with a receiver control circuit 20.
  • the down converter 34 can be a heterodyne down-converter.
  • the illustrated downconverter 34 includes mixers 35, 36A, and 36B.
  • the down converter 34 can frequency translate the output signal from the LNA 32 from a radio frequency signal to quadrature base-band signals.
  • the first down conversion stage of the down converter 34 includes the mixer 35 that can generate an intermediate frequency signal from the radio frequency signal from the LNA 32. Image rejection can be provided via a combination of the band-pass transfer function of the LNA 32, and its input matching circuit.
  • the second down-conversion stage of the down converter 34 includes mixers 36A and 36B that can perform a complex mix that results in quadrature I and Q base band output signals.
  • the I and Q baseband signals can subsequently be filtered and then digitized by the filtering and data conversion circuit 37.
  • Baseband filters 38A and 38B can filter I and Q baseband signals, respectively.
  • the filtered baseband signals can be converted to digital signals RX_I[N:0] and RX_Q[N:0] by the ADCs 39A and 39B, respectively.
  • the ADC output signals can be provided to a digital baseband processor for demodulation.
  • the receiver control circuit 20 can be implemented in accordance with any suitable principles and advantages of the receiver control circuits discussed herein.
  • the receiver control circuit 20 can receive a bit stream BIT STREAM and detect a synchronization header and an end of a preamble in the bit stream BIT STREAM.
  • the receiver control circuit 20 can provide a synchronization header detection signal SYNC_HEADER FOUND that indicates whether a synchronization header of a packet is detected.
  • the ADC output signals can be provided to the receiver control circuit 20.
  • the ADC output signals can be used in AFC.
  • the receiver control circuit 20 can provide and AFC adjustment signal ADF_ADJUST.
  • the receiver control circuit 20 can provide a control signal to the LNA 32 to implement AGC.
  • FIG. 7 is a schematic diagram of a transmit signal chain 40 for generating a radio frequency signal to be received by any suitable receiver discussed herein.
  • the transmit signal chain 40 can have enhanced flexibility in generating a multi-packet transmission with guard preambles between successive packets for communicating with receivers discussed herein.
  • the transmit signal chain 40 can generate a multi-packet transmission in which the guard preamble can have a length that is unknown to a paired receiving device prior to processing the multi-packet transmission.
  • a transceiver device includes the transmit signal chain 40 and a receiver implemented in accordance with any suitable principles and advantages discussed herein.
  • the transmitter takes on the form of a frequency synthesizer with digital control ports allowing instantaneous frequency modulation.
  • Frequency control words can be received from a digital baseband processor.
  • Carrier frequency adjustment and modulation are performed via the frequency synthesizer.
  • Output signal generation and power control can be performed via the power amplifier.
  • the illustrated transmit signal chain 40 includes a digital Gaussian frequency-shift keying (GFSK) modulator 41, a phase-locked loop (PLL) 42, and a power amplifier 49.
  • the PLL 42 is a frequency synthesizer.
  • the PLL 42 includes a voltage-controller oscillator 43, a divider 44, a feedback divider 45, and a phase frequency detector/charge pump/loop filter circuit 46.
  • Carrier frequency adjustment and low frequency modulation can be accomplished using a first control word TX_FM1.
  • a sigma delta modulator 47 can generate the first control word TX_FM1 based on an output of the GFSK modulator 41.
  • the first control word TX_FM1 can dynamically adjust a division ratio in a feedback loop of the PLL 42.
  • the first control word TX_FM1 can adjust a division ratio of the feedback divider 45.
  • the transfer function of the frequency modulation at this injection point can take on a low-pass form, with the bandwidth being defined by the PLL's loop bandwidth.
  • a digital-to-analog converter such as a frequency modulated (FM) DAC 48, can modulate the PLL's carrier frequency via a second control word TX_FM2 to provide for high frequency modulation.
  • the FM DAC 48 can convert the second control word TX_FM2 to an analog signal and apply the analog signal to the voltage-controlled oscillator 43 of the PLL 42.
  • the transfer function of this injection point can take on a high-pass form, with the cut-off determined by the PLL's loop bandwidth.
  • the GFSK modulator 41 can modulate a bit stream, including the associated packet handling, for transmission by the transmit signal chain 40.
  • the GFSK modulator 41 can include a Gaussian filter.
  • the power amplifier 49 can include multiple portions, each converting the PLL's output voltage waveform to a current.
  • the output power of the power amplifier 49 can be set by adjusting the number of active power amplifier portions.
  • An output matching circuit (not illustrated) can be coupled between an output of the power amplifier and an antenna.
  • FIG. 8 is a schematic diagram of a transceiver integrated circuit 80 according to an embodiment. Any of the transmit devices and/or the receive devices discussed herein can be implemented on a transceiver integrated circuit. As illustrated, the transceiver integrated circuit 80 includes a digital baseband processor 81, a synthesizer 82, a crystal oscillator 83, a transmitter 84, a power amplifier 49, a receiver 85, and a low noise amplifier 32.
  • An analog RF FE can include the transmitter 84, the receiver 85, and the synthesizer 82.
  • the transceiver 80 can operate in a half-duplex fashion so that the synthesizer 82 can serve the dual purpose of generating local oscillator signals for both the receiver 85 and the transmitter 84.
  • a receive chain can include the low noise amplifier 32, a receiver 85 that includes a heterodyne down-converter and filtering, and a data conversion stage in the baseband processor 81.
  • a transmitter chain can include a transmitter 84 that includes a frequency agile synthesizer and the power amplifier 49.
  • the transmitter chain of the integrated circuit 80 can include any suitable features of the transmit signal chain 40 of Figure 7 .
  • a receive chain can include a receiver 85 and the low noise amplifier 32.
  • the receiver chain of the integrated circuit 80 can include any suitable features of the receive signal chain 30 of Figure 6 and/or any suitable features of the receiver system 10 of Figure 3 .
  • the receiver 85 can receive a FSK signal that includes a multiple packets with a guard preamble of indeterminate length between successive packets in accordance with any suitable principles and advantages discussed herein.
  • the illustrated crystal oscillator 83 is connected to an off-chip crystal.
  • the radio channel frequency and symbol rate can be derived from an output of the crystal oscillator 83.
  • the digital baseband processor 81 can perform any suitable processing associated with generating signals for the transmitter 84 and/or processing signals provided by the receiver 85.
  • the receiver 85 and/or the digital baseband processor 81 can implement synchronization header detection and/or multi-packet protocol processing in accordance with any suitable principles and advantages discussed herein.
  • the receiver control circuit 20 can be included in the receiver 85 and/or the digital baseband processor 85.
  • the digital baseband processor 81 can provide digital modulation data to the transmitter 84.
  • the digital baseband processor 81 can include any of the modulation circuits discussed herein, such as the digital GFSK modulator 41 of Figure 7 .
  • the digital baseband processor 81 can process baseband data from the receiver 85 to perform a variety of different processing, such as synchronization, and data demodulation.
  • the digital baseband processor 81 can demodulate data bits of a packet in response to the header of the second packet being detected by a receiver control circuit.
  • the digital baseband processor 81 can dynamically provide configuration and/or control data to/from an RF FE that includes the transmitter 84 and the receiver 85.
  • the digital baseband processor 81 can control system timing in the transceiver integrated circuit 80.
  • any of the principles and advantages discussed herein can be applied to other systems, devices, integrated circuits, electronic apparatus, not just to the embodiments described above.
  • the elements and operations of the various embodiments described above can be combined to provide further embodiments.
  • the principles and advantages of the embodiments can be used in connection with any other systems, devices, integrated circuits, apparatus, or methods that could benefit from any of the teachings herein.
  • the technology described herein can be implemented in any suitable wireless communication device configured to receive and process an FSK signal, such as a wireless device configured to receive signals in accordance with the Bluetooth protocol.
  • aspects of this disclosure can be implemented in various electronic devices.
  • the electronic devices can include, but are not limited to, consumer electronic products, parts of electronic products such as integrated circuits, electronic test equipment, wireless communication devices, personal area network communication devices, cellular communications infrastructure such as a base station, vehicular electronics such as automotive electronics, etc. Further, the electronic devices can include unfinished products.
  • the words “comprise,” “comprising,” “include,” “including,” and the like are to generally be construed in an inclusive sense, as opposed to an exclusive or exhaustive sense; that is to say, in the sense of "including, but not limited to.”
  • the word “coupled,” as generally used herein, refers to two or more elements that may be either directly coupled to each other, or coupled by way of one or more intermediate elements.
  • the word “connected,” as generally used herein, refers to two or more elements that may be either directly connected, or connected by way of one or more intermediate elements.
  • conditional language used herein such as, among others, “can,” “could,” “might,” “may,” “e.g.,” “for example,” “such as” and the like, unless specifically stated otherwise or otherwise understood within the context as used, is generally intended to convey that certain embodiments include, while other embodiments do not include, certain features, elements and/or states.
  • conditional language is not generally intended to imply that features, elements and/or states are in any way required for one or more embodiments or that one or more embodiments necessarily include logic for deciding whether these features, elements and/or states are included or are to be performed in any particular embodiment.
  • circuit blocks described herein may be deleted, moved, added, subdivided, combined, and/or modified. Each of these circuit blocks may be implemented in a variety of different ways.
  • the accompanying claims and their equivalents are intended to cover any such forms or modifications as would fall within the scope and spirit of the disclosure.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Circuits Of Receivers In General (AREA)
EP19172633.0A 2018-05-25 2019-05-03 Multi-packet-protokoll-header-detektion Active EP3573307B1 (de)

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
US15/990,193 US10841217B2 (en) 2018-05-25 2018-05-25 Multi-packet protocol header detection

Publications (2)

Publication Number Publication Date
EP3573307A1 true EP3573307A1 (de) 2019-11-27
EP3573307B1 EP3573307B1 (de) 2023-06-28

Family

ID=66647013

Family Applications (1)

Application Number Title Priority Date Filing Date
EP19172633.0A Active EP3573307B1 (de) 2018-05-25 2019-05-03 Multi-packet-protokoll-header-detektion

Country Status (2)

Country Link
US (1) US10841217B2 (de)
EP (1) EP3573307B1 (de)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10841217B2 (en) 2018-05-25 2020-11-17 Analog Devices Global Unlimited Company Multi-packet protocol header detection

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11363529B2 (en) * 2019-07-24 2022-06-14 Silicon Laboratories Inc. Software emulation of parallelized packet detection across channels

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20130083648A1 (en) * 2011-09-30 2013-04-04 Hendricus De Ruijter Receiver with Collision Detection and Method Therefor
US20150131683A1 (en) * 2013-07-24 2015-05-14 Silicon Laboratories Inc. Receiver with signal arrival detection capability

Family Cites Families (15)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6859899B2 (en) 2000-05-15 2005-02-22 Texas Instruments Incorporated Method for data packet acquisition using split preamble
US7577122B1 (en) 2002-06-18 2009-08-18 Richard Douglas Schultz Method for minimizing receive packet processing for a personal computer implementation of a wireless local area network adapter
US8179879B2 (en) * 2006-09-18 2012-05-15 Pmc-Sierra Israel Ltd. Robust ranging method
KR100789921B1 (ko) 2006-11-07 2008-01-02 한국전자통신연구원 Ｏｆｄｍ 시스템에서의 프리엠블 패킷 검출 장치 및 그방법
US8705418B1 (en) 2010-03-03 2014-04-22 Kbc Research Foundation Pvt. Ltd. Methods and systems for detecting a preamble of a data packet in wireless communication systems
CN102625441A (zh) * 2011-03-31 2012-08-01 北京新岸线无线技术有限公司 用于接入无线网络的方法及装置
JP5720058B2 (ja) * 2011-04-25 2015-05-20 株式会社レイトロン Ｍｉｍｏ検出装置
US9608905B1 (en) 2013-07-19 2017-03-28 Marvell International Ltd. Packet preamble and symbol boundary detection
US10218822B2 (en) * 2013-10-25 2019-02-26 Marvell World Trade Ltd. Physical layer frame format for WLAN
US9479288B2 (en) * 2014-06-17 2016-10-25 Freescale Semiconductor, Inc. Techniques for time-domain frame synchronization of packets
US9813931B2 (en) 2014-07-29 2017-11-07 University Of Ottawa Adaptive packet preamble adjustment
US9992087B2 (en) * 2015-05-15 2018-06-05 Sr Technologies, Inc. System and method for long range wireless local area network communications
US9461654B1 (en) * 2015-06-01 2016-10-04 eTopus Technology Inc. Timing recovery for digital receiver with interleaved analog-to-digital converters
US10674459B2 (en) * 2017-03-10 2020-06-02 Analog Devices Global Method of operating a receiver to process a preamble of a data packet, and to a receiver operating in accordance with the method
US10841217B2 (en) 2018-05-25 2020-11-17 Analog Devices Global Unlimited Company Multi-packet protocol header detection

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20130083648A1 (en) * 2011-09-30 2013-04-04 Hendricus De Ruijter Receiver with Collision Detection and Method Therefor
US20150131683A1 (en) * 2013-07-24 2015-05-14 Silicon Laboratories Inc. Receiver with signal arrival detection capability

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10841217B2 (en) 2018-05-25 2020-11-17 Analog Devices Global Unlimited Company Multi-packet protocol header detection

Also Published As

Publication number Publication date
EP3573307B1 (de) 2023-06-28
US10841217B2 (en) 2020-11-17
US20190363981A1 (en) 2019-11-28

Similar Documents

Publication Publication Date Title
CN109586741B (zh) 使用频移键控的通信设备和方法
EP1710967B1 (de) Verfahren sowie System zur Anwendung eines PSK-SYNC-Wortes zur feinen Frequenzabstimmung
EP2975814B1 (de) Chirpsignalprozessor
US7542527B2 (en) Frequency offset correction circuit device
EP1653616B1 (de) Verfahren und System zur Anpassung der Frequenzrückkopplung in digitalen Empfängern
US8583067B2 (en) Apparatus and method for improved wireless communication reliability and performance in process control systems
US10484215B2 (en) Asynchronous transmission for NFC card emulation mode
US20040202133A1 (en) Power detection techniques and discrete gain state selection for wireless networking
US7212797B2 (en) DC removal techniques for wireless networking
EP3573307B1 (de) Multi-packet-protokoll-header-detektion
US20100261434A1 (en) Phase noise correction circuit, transmission device,reception device, radio device, radio communication system, and phase noise correction method
US7684519B2 (en) Method and system for adjusting DC offset slice point in an RF receiver
US7167535B2 (en) Circuit sharing for frequency and phase error correction
US11553431B2 (en) Time slotted scan receiver
US9071417B2 (en) Method and system for packet synchronization
US7532687B2 (en) Dual stage automatic gain control in an ultra wideband receiver
US11632733B2 (en) System, apparatus and method for acquisition of signals in wireless systems with adverse oscillator variations
US7194046B2 (en) Frequency error correction unit and method in a wireless LAN system
US7120206B2 (en) Signal DC offset correction method and device
US10491264B1 (en) Combined demodulator and despreader
Erhardt et al. Receiving GSM broadcast channels with an ultra-low power sub-GHz transceiver
JP2003008474A (ja) スペクトル拡散通信機
US20240214958A1 (en) Methods and devices of processing wireless signals with adaptive frequency shift correction
EP1488586B1 (de) System zur korrektur des frequenzversatzes mit anfänglicher frequenzschätzung und rückführungstracking
JP2023071215A (ja) 復調回路

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

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

Free format text: STATUS: THE APPLICATION HAS BEEN PUBLISHED

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: REQUEST FOR EXAMINATION WAS MADE

17P Request for examination filed

Effective date: 20200427

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

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

RAP1 Party data changed (applicant data changed or rights of an application transferred)

Owner name: ANALOG DEVICES INTERNATIONAL UNLIMITED COMPANY

REG Reference to a national code

Ref country code: DE

Ref legal event code: R079

Ref document number: 602019031569

Country of ref document: DE

Free format text: PREVIOUS MAIN CLASS: H04L0029060000

Ipc: H04L0069280000

GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

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

Free format text: STATUS: GRANT OF PATENT IS INTENDED

RIC1 Information provided on ipc code assigned before grant

Ipc: H04W 56/00 20090101ALI20221121BHEP

Ipc: H04L 69/22 20220101ALI20221121BHEP

Ipc: H04L 69/28 20220101AFI20221121BHEP

INTG Intention to grant announced

Effective date: 20221206

RIN1 Information on inventor provided before grant (corrected)

Inventor name: NEKL, JOSHUA J.

Inventor name: ONKAR, SUDARSHAN

Inventor name: O'BRIEN, MICHAEL W.

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

Ref legal event code: EP

REG Reference to a national code

Ref country code: AT

Ref legal event code: REF

Ref document number: 1583757

Country of ref document: AT

Kind code of ref document: T

Effective date: 20230715

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

Country of ref document: DE

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

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

REG Reference to a national code

Ref country code: NL

Ref legal event code: MP

Effective date: 20230628

REG Reference to a national code

Ref country code: AT

Ref legal event code: MK05

Ref document number: 1583757

Country of ref document: AT

Kind code of ref document: T

Effective date: 20230628

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

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

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

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

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

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

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

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

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

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

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

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

Ref country code: SM

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

Effective date: 20230628

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

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

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

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

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

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

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

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

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

Ref country code: PL

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

Effective date: 20230628

REG Reference to a national code

Ref country code: DE

Ref legal event code: R097

Ref document number: 602019031569

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

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

26N No opposition filed

Effective date: 20240402

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

Ref country code: GB

Payment date: 20240419

Year of fee payment: 6

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

Ref country code: DE

Payment date: 20240418

Year of fee payment: 6

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

Ref country code: SI

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

Effective date: 20230628

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

Ref country code: FR

Payment date: 20240418

Year of fee payment: 6