EP3698598B1 - Techniken zum verbindungsaufbau von millimeterwellenleiterbasierten v2x-kommunikationssystemen - Google Patents

Techniken zum verbindungsaufbau von millimeterwellenleiterbasierten v2x-kommunikationssystemen Download PDF

Info

Publication number
EP3698598B1
EP3698598B1 EP18799628.5A EP18799628A EP3698598B1 EP 3698598 B1 EP3698598 B1 EP 3698598B1 EP 18799628 A EP18799628 A EP 18799628A EP 3698598 B1 EP3698598 B1 EP 3698598B1
Authority
EP
European Patent Office
Prior art keywords
rach
resources
communications
initiating
discovery
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
EP18799628.5A
Other languages
English (en)
French (fr)
Other versions
EP3698598A1 (de
Inventor
Zhibin Wu
Sudhir Kumar Baghel
Shailesh Patil
Libin JIANG
Junyi Li
Kapil Gulati
Tien Viet NGUYEN
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 EP3698598A1 publication Critical patent/EP3698598A1/de
Application granted granted Critical
Publication of EP3698598B1 publication Critical patent/EP3698598B1/de
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/08—Non-scheduled access, e.g. ALOHA
    • H04W74/0833—Random access procedures, e.g. with 4-step access
    • H04W74/0841—Random access procedures, e.g. with 4-step access with collision treatment
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/08—Non-scheduled access, e.g. ALOHA
    • H04W74/0833—Random access procedures, e.g. with 4-step access
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04J—MULTIPLEX COMMUNICATION
    • H04J13/00—Code division multiplex systems
    • H04J13/0007—Code type
    • H04J13/0055—ZCZ [zero correlation zone]
    • H04J13/0059—CAZAC [constant-amplitude and zero auto-correlation]
    • H04J13/0062—Zadoff-Chu
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/30—Services specially adapted for particular environments, situations or purposes
    • H04W4/40—Services specially adapted for particular environments, situations or purposes for vehicles, e.g. vehicle-to-pedestrians [V2P]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W64/00—Locating users or terminals or network equipment for network management purposes, e.g. mobility management
    • H04W64/003—Locating users or terminals or network equipment for network management purposes, e.g. mobility management locating network equipment
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/005—Discovery of network devices, e.g. terminals
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W84/00—Network topologies
    • H04W84/18—Self-organising networks, e.g. ad-hoc networks or sensor networks

Definitions

  • aspects of the present disclosure relate generally to wireless communication systems, and more particularly, to techniques for vehicle-to-everything (V2X) communication systems in millimeter wave (mmWave or mmW).
  • V2X vehicle-to-everything
  • Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, and broadcasts.
  • Typical wireless communication systems may employ multiple-access technologies capable of supporting communication with multiple users by sharing available system resources. These multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different wireless devices to communicate on a municipal, national, regional, and even global level.
  • An example telecommunication standard is the 4th Generation (4G), which includes Long Term Evolution (LTE) and/or LTE-Advanced (LTE-A).
  • 4G 4th Generation
  • LTE Long Term Evolution
  • LTE-A LTE-Advanced
  • 5G New Radio
  • NR New Radio
  • V2X communications can be used when a vehicle communicates with one or more entities or devices that may affect the vehicle, and vice versa.
  • V2X communication may incorporate a specific type of communications, such as vehicle-to-vehicle (V2V) communications.
  • V2V vehicle-to-vehicle
  • mmWave communications in a V2X communication system may have different features and requirements compared with V2X communication system may have different features and requirements compared with conventional communication systems.
  • omni-directional links may not be available in mmWave band(s) (e.g., 10 GHz through 100 GHz) because of the path loss. In omni-directional transmissions, the path loss may scale as ⁇ 2 , where ⁇ is the carrier wavelength.
  • mmWave links may be inherently directional, and the range or coverage of mmWave communications may depend on the beam width or directivity of a perspective beam being used. For instance, by using more antenna elements, the beams may be narrower, and may reach further in distance or cover more areas compared with using less antenna elements.
  • connection setup and random access procedure e.g., in a mmWave-based V2X communication system
  • enhance medium access in order to satisfy consumer demand and improve user experience in wireless communications.
  • HUAWEI ET AL "Analysis of RACH Procedural steps", 2017-04-03 , 3GPP Draft discloses RACH transmission in 5G where, different preamble repetition times for different QoS requirements are used, to promote delay sensitive traffic.
  • a method related to connection setup and random access procedure in a wireless communication system e.g., a vehicle-to-everything (V2X) communication system
  • a wireless communication system e.g., a vehicle-to-everything (V2X) communication system
  • V2X vehicle-to-everything
  • an apparatus for wireless communication may include a transceiver, a memory configured to store instructions, and one or more processors communicatively coupled with the transceiver and the memory.
  • the apparatus may include instructions executable by the one or more processors to implement the method of claim 1.
  • a computer-readable medium storing computer code executable by a processor for wireless communications, which is arranged to perform the steps of the method disclosed in claim 1.
  • the one or more aspects comprise the features hereinafter fully described and particularly pointed out in the claims.
  • the following description and the annexed drawings set forth in detail certain illustrative features of the one or more aspects.
  • major design components may include, for example, broadcast design, connection setup procedure, and/or unicast traffic scheduling.
  • the broadcast design may be used for discovery procedure, which may be reused for data traffic.
  • NSA Non Stand-Alone
  • the connection setup procedure may be a critical step to establish a V2X or V2V communication link after the directional discovery step.
  • the interested vehicle e.g., a first user equipment (UE)
  • UE user equipment
  • the discovery may be a one-way discovery, and the target vehicle may not be aware of the exact location of the interested vehicle that initiated the random access. As such, the target vehicle may not know the direction, from which the target vehicle can receive request(s) from the interested vehicle.
  • processors include microprocessors, microcontrollers, digital signal processors (DSPs), field programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gated logic, discrete hardware circuits, and other suitable hardware configured to perform the various functionality described throughout this disclosure.
  • DSPs digital signal processors
  • FPGAs field programmable gate arrays
  • PLDs programmable logic devices
  • state machines gated logic, discrete hardware circuits, and other suitable hardware configured to perform the various functionality described throughout this disclosure.
  • One or more processors in the processing system may execute software.
  • Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.
  • the functions described may be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, the functions may be stored on or encoded as one or more instructions or code on a computer-readable medium.
  • Computer-readable media includes computer storage media. Storage media may be any available media that may be accessed by a computer. By way of example, and not limitation, such computer-readable media may comprise RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that may be used to carry or store desired program code in the form of instructions or data structures and that may be accessed by a computer.
  • Disk and disc includes compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), and floppy disk where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above should also be included within the scope of computer-readable media.
  • the computer-readable media may be non-transitory or include a non-transitory computer-readable storage medium.
  • V2X communication systems for example, a V2V communication system.
  • the various aspects are related to techniques or procedures for connection setup of mmWave-based V2X communications.
  • very high throughput links may be established or utilized between vehicles (e.g., cars) for transporting large amounts of data (e.g., camera feeds). These high throughput links (e.g., continuous video streaming between the vehicles) may demand or use high-data rate mmWave links.
  • the view of a vehicle may be blocked by, for example, another vehicle ahead or behind the vehicle.
  • mmWave designs in the Fifth Generation (5G) New Radio (NR) may not be reused or applied to V2X communications, because, for example, V2X scenarios may need to work in out-of-coverage cases where cells or gNBs may not be involved or available.
  • V2X or V2V communications may be considered as device-to-device (D2D) or ad-hoc communications.
  • discovery may be used as part of the design for D2D communications such as LTE-direct.
  • highspeed vehicle(s) may be difficult to manage with conventional cell handoff procedures. As such, new or improved approaches for connection setup of mmWave-based V2X communications may be desired.
  • two different operation modes may be used in V2X communications.
  • One operation mode is proactive mode.
  • the proactive mode may maintain highly directional links between a vehicle and one or more neighbor vehicles so that data transport may be started promptly, and with high-data rate(s).
  • the proactive mode may be used to keep tracking and to refine beams as the vehicle moves.
  • the proactive mode may be used when there is no active data sessions.
  • a vehicle in proactive mode, may actively use discovery to detect or locate other vehicle(s) in proximity to the vehicle.
  • a vehicle may mainly use unicast communications.
  • the other operation mode, reactive mode may be used in V2X communications.
  • a vehicle may not have associated topology maintained.
  • the vehicle may choose to establish one or more links (e.g., one-time broadcast) and transport using a directional link (e.g., one of the established link(s)).
  • the vehicle may use a link with either a wide beam or a narrow beam.
  • the vehicle may release the link after traffic is stopped.
  • both unicast and broadcast traffic may be utilized.
  • the vehicle may use on-demand discovery to detect location with interests (e.g., sensor interests).
  • an initiating UE may perform handshake(s) with a target UE. For example, the initiating UE may discover or find the target UE from broadcast signals or beams sent from the target UE, and then the initiating UE may try to reach the target UE. In another example, the initiating UE may identify the target UE based on predetermined information (e.g., information or schemes stored at the initiating UE). In an example, after discovery, the initiating UE or an interested node may initiate random access (e.g., via a random access channel (RACH)) to the target UE. In some aspects, one or more directional antennas may be used in V2X communications, for example, for discovery and/or RACH procedure(s).
  • RACH random access channel
  • the target UE may not know where the initiating UE is. As a result, the target UE may not know which direction the target UE should expect to receive a request from the initiating UE.
  • the target UE may announce or transmit some information in the discovery phase, and listen to all directions in turn (e.g., in multiple slots) to check whether there is any RACH message.
  • resource timing between the initiating UE and the target UE may need to be considered. For example, the initiating UE may need to know the time when the target UE receives the connection request sent from the initiating UE.
  • the initiating UE may use a discovery and/or a RACH procedure to obtain or identify information for directional V2X communications.
  • the information may include the property, characteristic and/or identifier of the target UE or vehicle, the directivity of a broadcast or discovery signal, and/or the direction(s) to reach the target UE or vehicle.
  • multiplicity among multiple initiating UEs and the target UE may need to be considered. For example, there may be multiple UEs transmitting from the same direction trying to reach the same target UE. In this case, multiple RACH resource allocations may be applied and the RACH resources may be limited, and interference among the multiple UEs may need to be considered.
  • a respective transmission (TX) identification (ID) may be used for each initiating UE, and may be included in transmitted symbols.
  • the target UE may extract the TX ID to identify a respective initiating UE from multiple initiating UEs that are transmitting from the same direction and/or at the same time.
  • the target UE may be in the proximity of one or more initiating UEs.
  • RACH resource allocations and procedures may be based on or associated with discovery that is discussed above.
  • one or more RACH resource locations may be derived based on the content(s) of a discovery message or signal (e.g., a Discovery Msg) broadcasted by the target UE, with an algorithm known by one or more UEs, or all UEs.
  • many-to-one mapping between discovery resources and RACH resources may be used.
  • one-to-one mapping between RACH resources and RACH response resources may be utilized.
  • the resource mapping is shown in FIG. 5 .
  • the number of discovery resources may be larger than the number of RACH resources, and the number of RACH resources may be equal or larger than the number of RACH response resources.
  • each transmitting (TX) vehicle may use an orthogonal sequence (e.g., a Zadoff-Chu (ZC) sequence used in LTE) and/or different code(s) in transmit symbol(s), and the receiving (RX) vehicle may detect the existence of one or more TX vehicles.
  • the sequence chosen by the TX vehicle may be indexed, and the index may be linked to a different "rendezvous" resource(s) for message-based handshake.
  • further message exchanges may be applied between an initiating UE (or vehicle) and a target UE (or vehicle).
  • beam alignment may be used after initial discovery.
  • the initiating UE and the target UE may exchange position information and/or trajectory estimation.
  • a RACH response may contain a ZC-ID and/or the ID of the initiating UE.
  • the initiating UE and/or the target UE may use a different ZC sequence, and/or the best beam (1, 2, ... M), where M is the number of beam directions to be supported by the UE antenna(s).
  • RACH message(s) may contain one or more additional bits (e.g., in addition to the ZC sequence or preamble) to show the best beam that may be used by the initiating UE to reach the target UE.
  • the initiating UE may support one or more beam-sweeping patterns from the target UE. For example, the target UE may transmit and/or receive beams in 8 different directions in the discovery phase. In an aspect, the initiating UE may detect the target UE in one out of the 8 different directions (e.g., one direction with the maximum signal strength out of the 8 different directions). In some cases, the initiating UE may support up to 12 beam directions, and the best beam perceived by the initiating UE may not be the one of the 8 directions where the target UE is currently listening or monitoring for RACH request(s).
  • the sender (e.g., the initiating UE or the target UE) of the RACH message may be configured to use a comparatively wider beam to increase the chance of the receiver (e.g., the target UE or the initiating UE) to capture the beam, due to the potential mobility between the sender and the receiver (or the initiating UE and target UE).
  • using a wider beam may reduce signal-to-interference and noise ratio (SINR) of the signal at the same distance compared with using a narrower beam.
  • SINR signal-to-interference and noise ratio
  • the sender may be aware that a message or signal itself can be decoded in a low-SINR environment (e.g., containing less information bits in the message or signal), and in some cases, the best beam may still be included in the message, and the receiver may know the perception of a proper narrow beam that the sender wants to use to reach the receiver.
  • a low-SINR environment e.g., containing less information bits in the message or signal
  • the initiating UE and/or the target UE may encode a few bits.
  • the initiating UE and/or the target UE may use and/or transmit a single sequence, or a sequence with a few bits.
  • the sequence may be a ZC sequence, and may not have any data information.
  • absolute orthogonality and information-carrying capability may be considered when performing multi-user detection.
  • the receiver at the initiating UE or the target UE
  • the receiver may decode each of the ZC sequences where the different ZC sequences may be orthogonal.
  • the sender at the initiating UE or the target UE may encode a couple of bits as additional information (e.g., in addition to a ZC sequence) to improve information-carrying capability.
  • FIGs. 1-6 are described in more detail below.
  • a wireless communication system 100 includes at least a UE 12 or UE 14 in communication coverage of at least a UE 20.
  • the UE 12 or UE 14 may be referred to as an initiating UE in a vehicle (or being attached to the vehicle or being associated with the vehicle), and the UE 20 may be referred to as a target UE in another vehicle (or being attached to another vehicle or being associated with the vehicle).
  • the initiating UE 12 or UE 14 may communicate with the target UE 20 directly using beamforming.
  • the initiating UE 12 or UE 14 may communicate with the target UE 20 via device-to-device or ad-hoc communications.
  • multiple initiating UEs including the UE 12 and/or UE 14 may be in communication coverage with one or more target UEs, including the UE 20.
  • the initiating UE 12 or UE 14 may transmit and/or receive wireless communications (e.g., beams for discovery or RACH procedure) to and/or from the target UE 20.
  • the initiating UE 12 or 14 may be actively communicating with the target UE 20, for example, to perform connection setup or RACH procedures.
  • the UE 12, 14, or 20 may also be referred to by those skilled in the art (as well as interchangeably herein) as a vehicle (or inside a vehicle), a mobile station, a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communications device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a terminal, a user agent, a mobile client, a client, or some other suitable terminology.
  • the UE 12, 14, or 20 may be a cellular phone, a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a tablet computer, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a global positioning system (GPS) device, a multimedia device, a video device, a digital audio player (e.g., MP3 player), a camera, a game console, a wearable computing device (e.g., a smart-watch, smart-glasses, a health or fitness tracker, etc.), an appliance, a sensor, a vehicle communication system, a medical device, a vending machine, a device for Internet of Things (IoT), or any other similar functioning device.
  • PDA personal digital assistant
  • WLL wireless local loop
  • GPS global positioning system
  • multimedia device e.g., a digital audio player (e.g., MP3 player), a camera, a game console, a wearable computing device (e.
  • the UE 12, 14, or 20 may include one or more processors 103 and a memory 130 that may operate in combination with a communications management component 40.
  • the communications management component 40 may include a discovery component 42, RACH management component 44, resource mapping component 46, and/or sequence management component 48.
  • the communications management component 40 may be configured to perform one or more connection setup or RACH procedures as discussed herein.
  • the discovery component 42 may be configured to broadcast or receive one or more discovery messages.
  • the RACH management component 44 may be configured to perform RACH resource allocations and related procedures, for example, RACH request or RACH response.
  • the resource mapping component 46 may be configured to map the resources among discovery resources, RACH resources, and RACH response resources.
  • the sequence management component 48 may be configured to determine or identify the sequence(s) being used in the resources.
  • the communications management component 40 may be communicatively coupled with a transceiver 106, which may include a receiver 32 for receiving and processing radio frequency (RF) signals (e.g., broadcast signals, directional beam signals, or RACH signals), and a transmitter 34 for processing and transmitting RF signals (e.g., broadcast signals, directional beam signals, or RACH signals).
  • RF radio frequency
  • the processor 103 may be communicatively coupled with the transceiver 106 and memory 130 via at least one bus 110.
  • the receiver 32 may include hardware, firmware, and/or software code executable by a processor for receiving data, the code comprising instructions and being stored in a memory (e.g., computer-readable medium).
  • the receiver 32 may be, for example, an RF receiver.
  • the receiver 32 may receive signals transmitted by the UE 12, UE 14, and/or UE 20.
  • the receiver 32 may obtain discovery signals and/or measurements of the signals.
  • the receiver 32 may obtain signal measurements, and may be communicatively coupled with the processor(s) 103 and assist the processor(s) 103 to determine signal-to-noise ratio (SNR), Reference Signal Received Power (RSRP), Reference Signal Received Quality (RSRQ), Received Signal Strength Indicator (RSSI), etc.
  • SNR signal-to-noise ratio
  • RSRP Reference Signal Received Power
  • RSRQ Reference Signal Received Quality
  • RSSI Received Signal Strength Indicator
  • the transmitter 34 may include hardware, firmware, and/or software code executable by a processor for transmitting data, the code comprising instructions and being stored in a memory (e.g., computer-readable medium).
  • the transmitter 34 may be, for example, a RF transmitter.
  • the one or more processors 103 may include a modem 108 that uses one or more modem processors.
  • the various functions related to the communications management component 40 may be included in the modem 108 and/or processor(s) 103 and, in an aspect, may be executed by a single processor, while in other aspects, different ones of the functions may be executed by a combination of two or more different processors.
  • the one or more processors 103 may include any one or any combination of a modem processor, or baseband processor, or digital signal processor, or transmit processor, or transceiver processor associated with the transceiver 106.
  • the one or more processors 103 may implement components included in the communications management component 40, including the discovery component 42, RACH management component 44, resource mapping component 46, and/or sequence management component 48.
  • the communications management component 40, discovery component 42, RACH management component 44, resource mapping component 46, and/or sequence management component 48 may include hardware, firmware, and/or software code executable by a processor for performing connection setup, RACH procedures and related operations in V2X or V2V communications.
  • the hardware may include, for example, a hardware accelerator, or specialized processor.
  • the term "component" as used herein may be one of the parts that make up a system, may be hardware, firmware, and/or software, and may be divided into other components.
  • the UE 12 may include an RF front end (not shown) and the transceiver 106 for receiving and transmitting radio transmissions, for example, wireless communications 26.
  • transceiver 106 may transmit or receive one or more signals.
  • the transceiver 106 may measure a received pilot signal in order to determine signal quality (e.g., based on RSRP, RSRQ, or RSSI) and for providing feedback.
  • the transceiver 106 may communicate with the modem 108 to transmit messages generated by the communications management component 40 and to receive messages and forward them to the communications management component 40.
  • the RF front end may be communicatively coupled with one or more antennas 102 and may include one or more low-noise amplifiers (LNAs), one or more switches, one or more power amplifiers (PAs), and one or more filters for transmitting and receiving RF signals (e.g., beam signals).
  • LNAs low-noise amplifiers
  • PAs power amplifiers
  • filters for transmitting and receiving RF signals (e.g., beam signals).
  • the components of the RF front end may be communicatively coupled with the transceiver 106 (e.g., via one or more communication links or buses 110).
  • the transceiver 106 may be communicatively coupled with one or more modems 108 and/or processor 103.
  • the LNA may amplify a received signal at a desired output level.
  • each LNA may have a specified minimum and maximum gain values.
  • the RF front end may use one or more switches to select a particular LNA and a specified gain value based on a desired gain value for a particular application.
  • the RF front end may provide measurements (e.g., Ec/Io) and/or applied gain values to the communications management component 40.
  • the one or more PA(s) may be used by the RF front end to amplify a signal for an RF output at a desired output power level.
  • each PA may have a specified minimum and maximum gain values.
  • the RF front end may use one or more switches to select a particular PA and a specified gain value of the PA based on a desired gain value for a particular application.
  • the one or more filters may be used by the RF front end to filter a received signal to obtain an input RF signal.
  • a respective filter may be used to filter an output from a respective PA to produce an output signal for transmission.
  • each filter may be communicatively coupled with a specific LNA and/or PA.
  • the RF front end may use one or more switches to select a transmit or receive path using a specified filter, LNA, and/or PA, based on a configuration as specified by the transceiver 106 and/or processor 103.
  • the transceiver 106 may be configured to transmit and receive wireless signals through an antenna 102 via the RF front end.
  • the transceiver 106 may be tuned to operate at specified frequencies such that the UE 12 or UE 14 may communicate with, for example, the UE 20.
  • the modem 108 may configure the transceiver 106 to operate at a specified frequency and power level based on the UE configuration of the UE 12, UE 14, and/or UE 20, and communication protocol used by the modem 108.
  • the modem 108 may be a multiband-multimode modem, which may process digital data and communicate with the transceiver 106 such that the digital data is sent and received using the transceiver 106.
  • the modem 108 may be multiband and be configured to support multiple frequency bands for a specific communications protocol.
  • the modem 108 may be multi-mode and be configured to support multiple operating networks and communications protocols.
  • the modem 108 may control one or more components of the UE 12, UE 14, or UE 20 (e.g., RF front end, transceiver 106), to perform connection setup and RACH procedures in V2X or V2V communications, or enable transmission and/or reception of signals based on a specified modem configuration.
  • the modem configuration may be based on the mode of the modem and the frequency band in use.
  • the modem configuration may be based on UE configuration information associated with the UE 12, UE 14, or UE 20.
  • the UE 12, UE 14, or UE 20 may further include memory 130, such as for storing data used herein and/or local versions of applications or the communications management component 40 and/or one or more subcomponents of the communications management component 40 being executed by the processor(s) 103.
  • the memory 130 may include any type of computer-readable medium usable by a computer or processor(s) 103, such as random access memory (RAM), read only memory (ROM), tapes, magnetic discs, optical discs, volatile memory, non-volatile memory, and any combination thereof.
  • the memory 130 may be a computer-readable storage medium that stores one or more computer-executable codes defining communications management component 40 and/or one or more of the subcomponents of the communications management component 40, and/or data associated therewith, when the UE 12, UE 14, or UE 20 is operating the processor(s) 103 to execute the communications management component 40 and/or one or more subcomponents of the communications management component 40.
  • the memory 130 may be a non-transitory computer-readable storage medium.
  • mmWave communications such as the wireless communications 26 in FIG. 1
  • mmWave links may be inherently directional.
  • the range of mmWave communications may depend on the beam widths or directivity.
  • the energy consumption or power budget is related to the beam widths that can be used.
  • path loss between a transmitter and a receiver may not change as a function of frequency, as long as the effective aperture of the transmitting and receiving antennas does not change.
  • the antenna aperture does reduce in proportion to the square of the frequency, and the reduction may be compensated by using higher antenna directivity.
  • the mmWave V2X procedure 300 may start with a timing synchronization, for example, via a Global Navigation Satellite System (GNSS) or a Global Positioning System (GPS). If an upper layer determines there are potential or existing V2X communications (e.g., sensor sharing), UE 12 or UE 14 may use transmission or reception beam-sweeping (or both) to detect neighbor V2X UEs in proximity to the UE 12 or UE 14.
  • GNSS Global Navigation Satellite System
  • GPS Global Positioning System
  • the initiating UE 12 or UE 14 may calculate the RACH resources of the neighbor vehicle for a directional beam, and then send a wide beam with an initial access request (e.g., RACH-like) to the target vehicle (e.g., UE 20). After sending the initial access request, the initiating UE 12 or UE 14 may listen or monitor for a RX beam for a response in a designated time slot.
  • a neighbor vehicle e.g., a target UE, or UE 20
  • the initiating UE 12 or UE 14 may listen or monitor for a RX beam for a response in a designated time slot.
  • the initiating UE 12 or UE 14 may receive a RACH response from the target vehicle, e.g., UE 20, to establish a unicast link with at least a Radio Resource Control (RRC) message over PC5 (a one-to-many communication interface) or sidelink at the physical layer, and update Medium Access Control (MAC) schedule with this new unicast link.
  • RRC Radio Resource Control
  • MAC Medium Access Control
  • the initiating UE 12 or UE 14 may identify master or slave roles for beam tracking or refining, keep link(s) alive, and measure and/or refine the beam for the link(s).
  • the UE 12 and/or UE 14 may conduct or perform transmission or reception based on the MAC schedules.
  • the UE 12 (or UE 14, UE 20) may update MAC schedule accordingly.
  • a UE may allocate or use resources based on a predetermined frame structure.
  • the UE may use a frame structure 400 for resource allocations or usage.
  • the UE may use a 5G frame structure as a basis, for example, with flexible numerology, and/or flexible Transmission Time Intervals (TTIs).
  • TTIs Transmission Time Intervals
  • around 10% of the resources may be shared or used for discovery, RACH procedure, broadcast and slow-loop control, and 90% of the resources may be used for unicast traffic and associated traffic management signaling.
  • resources may be repeated (e.g., in frame cycles) as shown in FIG.
  • a cycle duration may be ten milliseconds to ten seconds (10 ms - 10 s), and may include common control resources and resources dedicated for traffic and/or associate data plane control.
  • the common control resources may include discovery and/or RACH resources, and the resources dedicated for traffic may include unicast traffic and/or broadcast traffic.
  • RACH resource allocation scheme 500 with resource mapping is illustrated.
  • one or more RACH resource locations may be derived (e.g., via arrows 510 and/or 520) based on the content(s) of a discovery message or signal (e.g., a Discovery Msg) broadcasted by the target UE, with an algorithm known by one or more UEs, or all UEs.
  • a discovery message or signal e.g., a Discovery Msg
  • many-to-one mapping between discovery resources and RACH resources may be used.
  • resource mapping component 46 may be configured to map one or more discovery resources in the discovery message to one of the RACH resources.
  • one-to-one mapping between RACH resources and RACH response resources may be utilized.
  • the resource mapping component 46 may be configured to map each of the RACH resources to one of the RACH response resources.
  • the number of discovery resources may be larger than the number of RACH resources, and the number of RACH resources may be equal or larger than the number of RACH response resources.
  • a UE such as UE 12, UE 14, or UE 20 in FIG. 1 , performs one or more aspects of a method 600 for managing connection setup in a wireless communication system (e.g., an mmWave-based V2X communication system).
  • a wireless communication system e.g., an mmWave-based V2X communication system
  • the processors 103, memory 130, modem 108, transceiver 106, communications management component 40, discovery component 42, RACH management component 44, resource mapping component 46, and/or sequence management component 48 may be configured to perform aspects of the method 600.
  • the method 600 includes identifying information for V2X communications.
  • the communications management component 40 e.g., in conjunction with one or more of the processors 103, memory 130, modem 108, and/or transceiver 106, may be configured to identify information for V2X communications.
  • the information includes one or more discovery resources and may further include RACH resources mapping information, the property, characteristic and/or identifier of a target UE, the directivity of a broadcast or discovery signal, and/or the direction(s) to reach the target UE.
  • the information may be received (e.g., via transceiver 106) in a broadcast or discovery message, or predetermined by an initiating UE (e.g., via one or more of the processors 103 at UE 12).
  • the method 600 includes initiating a random access procedure based on the identified information.
  • the communications management component 40, discovery component 42, RACH management component 44 e.g., in conjunction with one or more of the processors 103, memory 130, modem 108, and/or transceiver 106, may be configured to initiate a RACH procedure based on the identified information.
  • the RACH procedure is initiated in response to receiving a discovery message.
  • the method 600 includes identifying one or more RACH resources based on the information.
  • the communications management component 40, discovery component 42, RACH management component 44, resource mapping component 46 e.g., in conjunction with one or more of the processors 103, memory 130, modem 108, and/or transceiver 106, may be configured to identify RACH resources based on the identified information (e.g., in a received discovery message).
  • the resource mapping component 46 may be configured to map discovery resources in the discovery message to the RACH resources.
  • the RACH management component 44 and/or resource mapping component 46 may be configured to identify the location of each RACH resource based on the identified information (e.g., in a received discovery message).
  • the method 600 includes identifying one or more RACH response resources based on the one or more RACH resources.
  • the communications management component 40, RACH management component 44, resource mapping component 46 e.g., in conjunction with one or more of the processors 103, memory 130, modem 108, and/or transceiver 106, may be configured to identify RACH response resources based on the identified RACH resources at block 606.
  • the resource mapping component 46 may be configured to map each of the RACH resources to one of the RACH response resources.
  • the method 600 includes performing directional communications using at least the one or more RACH resources or the one or more RACH response resources.
  • the communications management component 40, sequence management component 48 e.g., in conjunction with one or more of the processors 103, memory 130, modem 108, and/or transceiver 106, may be configured to perform directional communications using the identified RACH resources at block 606 and/or the identified RACH response resources at block 608.
  • the communications management component 40 and/or sequence management component 48 may be configured to receive a RACH response using at least one of the RACH response resources, and the RACH response comprises at least a Zadoff-Chu (ZC) sequence identification (ID) and an initiating UE ID.
  • ZC Zadoff-Chu
  • various aspects may be extended to other communication systems such as High Speed Downlink Packet Access (HSDPA), High Speed Uplink Packet Access (HSUPA), High Speed Packet Access Plus (HSPA+) and TD-CDMA.
  • Various aspects may also be extended to systems employing Long Term Evolution (LTE) (in FDD, TDD, or both modes), LTE-Advanced (LTE-A) (in FDD, TDD, or both modes), CDMA2000, Evolution-Data Optimized (EV-DO), Ultra Mobile Broadband (UMB), IEEE 602.11 (Wi-Fi), IEEE 602.16 (WiMAX), IEEE 602.20, Ultra-Wideband (UWB), Bluetooth, and/or other suitable systems.
  • LTE Long Term Evolution
  • LTE-A LTE-Advanced
  • CDMA2000 Long Term Evolution-Data Optimized
  • UMB Ultra Mobile Broadband
  • IEEE 602.11 Wi-Fi
  • IEEE 602.16 WiMAX
  • IEEE 602.20 Ultra-Wideband
  • Bluetooth

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Power Engineering (AREA)
  • Databases & Information Systems (AREA)
  • Mobile Radio Communication Systems (AREA)

Claims (14)

  1. Ein Verfahren (600) zur drahtlosen Kommunikation, das Folgendes aufweist:
    Identifizieren (602) von Informationen, die eine oder mehrere Entdeckungsquellen für Fahrzeug-zu-Allgemeinem, V2X, Kommunikation aufweisen;
    Initiieren (604) eines Zufallszugriffsverfahrens auf der Grundlage der identifizierten Informationen;
    Identifizierung (606) einer oder mehrerer RACH-Ressourcen (RACH = random access channel) auf der Grundlage der Informationen;
    Identifizieren (608) einer oder mehrerer RACH-Antwortressourcen auf der Grundlage der einen oder mehreren RACH-Ressourcen; und
    Durchführen (610) von direktionaler Kommunikation unter Verwendung mindestens der einen oder mehreren RACH-Ressourcen oder der einen oder mehreren RACH-Antwort-Ressourcen.
  2. Verfahren nach Anspruch 1, wobei das Identifizieren der einen oder mehreren RACH-Ressourcen das Abbilden der einen oder mehreren Entdeckungsressourcen auf die eine oder mehreren RACH-Ressourcen aufweist.
  3. Verfahren nach Anspruch 1,
    wobei die Anzahl der einen oder mehreren Discovery-Ressourcen mindestens zwei beträgt und größer ist als die Anzahl der einen oder mehreren RACH-Ressourcen, und
    wobei die Anzahl der einen oder mehreren RACH-Ressourcen gleich oder größer ist als die Anzahl der einen oder mehreren RACH-Antwortressourcen.
  4. Verfahren nach Anspruch 1, wobei das Identifizieren der einen oder mehreren RACH-Antwortressourcen das Abbilden jeder der einen oder mehreren RACH-Ressourcen auf eine der einen oder mehreren RACH-Antwortressourcen aufweist.
  5. Verfahren nach Anspruch 1, das weiterhin aufweist::
    Identifizieren eines Ortes jeder der einen oder mehreren RACH-Ressourcen auf der Grundlage der identifizierten Informationen.
  6. Verfahren nach Anspruch 1, wobei die identifizierenden Informationen das Identifizieren der Informationen in einer empfangenen Broadcast-Nachricht aufweisen.
  7. Verfahren nach Anspruch 1, wobei die Information durch ein initiierendes Benutzergerät, UE, (UE = User Equipment) vorbestimmt wird.
  8. Verfahren nach Anspruch 1, wobei die eine oder mehreren RACH-Ressourcen mindestens eine RACH-Ressource aufweisen, die von mehreren initiierenden Benutzergeräten, UEs, verwendet wird.
  9. Verfahren nach Anspruch 1, das weiter aufweist:
    Empfangen einer RACH-Antwort unter Verwendung einer der einen oder mehreren RACH-Antwort-Ressourcen, wobei die RACH-Antwort mindestens eine Zadoff-Chu, ZC, Sequenzidentifikation, ID, und eine initiierende UE-ID aufweist.
  10. Verfahren nach Anspruch 1, wobei das Verfahren im Millimeterwellenbereich verwendet wird.
  11. Verfahren nach Anspruch 1, wobei das Durchführen von direktionaler Kommunikation das Kommunizieren zwischen mindestens zwei UEs in einer oder mehreren Richtungen aufweist, wobei eine jeweilige Zadoff-Chu, ZC, Sequenz für jede der einen oder mehreren Richtungen verwendet wird.
  12. Verfahren nach Anspruch 1, wobei das Durchführen von direktionaler Kommunikation Folgendes aufweist:
    Übertragen eines Symbols mit einer Zadoff-Chu, ZC, Sequenz, oder
    das Übertragen eines Symbols mit einer ZC-Sequenz mit einem oder mehreren Bits.
  13. Eine Vorrichtung für drahtlose Kommunikation, die Folgendes aufweist:
    Mittel, die zur Durchführung der Schritte nach einem der Ansprüche 1 bis 12 eingerichtet sind.
  14. Computerlesbares Medium, das Computercode speichert, der von einem oder mehreren Prozessoren für drahtlose Kommunikation ausgeführt werden kann, mit computerausführbarem Code, der so eingerichtet ist, dass er die Schritte nach einem der Ansprüche 1 bis 12 ausführt.
EP18799628.5A 2017-10-19 2018-10-17 Techniken zum verbindungsaufbau von millimeterwellenleiterbasierten v2x-kommunikationssystemen Active EP3698598B1 (de)

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
US201762574600P 2017-10-19 2017-10-19
US16/161,397 US10631343B2 (en) 2017-10-19 2018-10-16 Techniques for connection setup of mmWave-based V2X communication systems
PCT/US2018/056197 WO2019079379A1 (en) 2017-10-19 2018-10-17 CONNECTION ESTABLISHING TECHNIQUES OF V2X MILLIMETER WAVE COMMUNICATION SYSTEMS

Publications (2)

Publication Number Publication Date
EP3698598A1 EP3698598A1 (de) 2020-08-26
EP3698598B1 true EP3698598B1 (de) 2023-12-20

Family

ID=66170775

Family Applications (1)

Application Number Title Priority Date Filing Date
EP18799628.5A Active EP3698598B1 (de) 2017-10-19 2018-10-17 Techniken zum verbindungsaufbau von millimeterwellenleiterbasierten v2x-kommunikationssystemen

Country Status (4)

Country Link
US (2) US10631343B2 (de)
EP (1) EP3698598B1 (de)
CN (1) CN111226492B (de)
WO (1) WO2019079379A1 (de)

Families Citing this family (16)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11786146B1 (en) 2012-09-25 2023-10-17 Micro Mobio Corporation Wireless hub system and method
US11877842B1 (en) * 2012-09-25 2024-01-23 Micro Mobio Corporation Personal cloud with a plurality of modular capabilities
US10631343B2 (en) 2017-10-19 2020-04-21 Qualcomm Incorporated Techniques for connection setup of mmWave-based V2X communication systems
US10531254B2 (en) * 2018-01-31 2020-01-07 Toyota Jidosha Kabushiki Kaisha Millimeter wave vehicle-to-vehicle communication system for data sharing
US10999871B2 (en) 2018-06-08 2021-05-04 Qualcomm Incorporated Random access procedure for CV2X
CN113016218A (zh) * 2019-01-04 2021-06-22 株式会社Ntt都科摩 无线通信方法及设备
US11800579B2 (en) 2019-05-07 2023-10-24 Qualcomm Incorporated Establishment of millimeter wave relay links between user equipments with base station coordination
WO2021019140A1 (fr) * 2019-08-01 2021-02-04 Psa Automobiles Sa Procédé, dispositif et système de communication pour véhicule utilisant des radars
FR3099681B1 (fr) * 2019-08-01 2022-08-05 Psa Automobiles Sa Procédé, dispositif et système de communication pour véhicule utilisant des radars
FR3099679B1 (fr) * 2019-08-01 2021-07-16 Psa Automobiles Sa Procédé, dispositif et système de communication pour véhicule utilisant des radars
US11641675B2 (en) * 2019-09-23 2023-05-02 Qualcomm Incorporated Indication of traffic direction for sidelink
KR102477970B1 (ko) * 2019-10-18 2022-12-14 에이에스티 앤 사이언스, 엘엘씨 네트워크 액세스 관리
US11219027B2 (en) 2020-01-03 2022-01-04 Qualcomm Incorporated Methods for beam management in millimeter wave relays
US11304038B2 (en) * 2020-02-28 2022-04-12 Blu Wireless Technology Limited Wireless communication for vehicle based node
US20220256326A1 (en) * 2021-02-11 2022-08-11 Qualcomm Incorporated Techniques for sidelink discovery between user equipments associated with different discovery models
WO2023186479A1 (en) 2022-03-30 2023-10-05 Sony Group Corporation Unmanned aerial vehicles and methods of operating unmanned aerial vehicles

Family Cites Families (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8295243B2 (en) * 2006-08-21 2012-10-23 Qualcomm Incorporated Method and apparatus for random access in an orthogonal multiple-access communication system
US9661654B2 (en) 2010-01-12 2017-05-23 Samsung Electronics Co., Ltd. Apparatus and method for accessing random access channel in a wireless communication system
US9619246B2 (en) * 2010-03-30 2017-04-11 Hon Hai Precision Industry Co., Ltd. Electronic computing device and reboot method thereof
US20120300714A1 (en) * 2011-05-06 2012-11-29 Samsung Electronics Co., Ltd. Methods and apparatus for random access procedures with carrier aggregation for lte-advanced systems
KR102014794B1 (ko) * 2011-12-20 2019-10-21 엘지전자 주식회사 무선 통신 시스템에서 상향링크 동기 획득 방법 및 장치
US9635652B2 (en) * 2012-03-22 2017-04-25 Zte (Usa) Inc. Optimized transmission of machine type communication data from a mobile device to a wireless network
CN110445591B (zh) * 2012-09-26 2021-12-28 华为技术有限公司 用于在异构通信系统中进行随机接入的系统和方法
WO2015065107A1 (ko) * 2013-10-31 2015-05-07 엘지전자(주) 무선 통신 시스템에서 단말 간 직접 통신을 수행하기 위한 방법 및 장치
JP6384878B2 (ja) * 2014-04-23 2018-09-05 華為技術有限公司Ｈｕａｗｅｉ Ｔｅｃｈｎｏｌｏｇｉｅｓ Ｃｏ．，Ｌｔｄ． ランダムアクセス方法、ランダムアクセス装置、およびユーザ機器
WO2016175631A1 (en) * 2015-04-30 2016-11-03 Lg Electronics Inc. Method and apparatus for configuring random access channel in short tti or contention based uplink transmission in wireless communication system
EP3387867B1 (de) * 2016-01-12 2020-07-08 Sony Corporation Endgerätevorrichtung, infrastrukturausrüstung und verfahren zur ressourcenauswahl und aktualisierung von zugriffsklasseninformationen
US10833796B2 (en) * 2016-05-25 2020-11-10 Lg Electronics Inc. Method and apparatus for competition-based transmitting of uplink data in wireless communication system to which non-orthogonal multiple access scheme is applied
US10631343B2 (en) 2017-10-19 2020-04-21 Qualcomm Incorporated Techniques for connection setup of mmWave-based V2X communication systems

Also Published As

Publication number Publication date
CN111226492A (zh) 2020-06-02
EP3698598A1 (de) 2020-08-26
US11172516B2 (en) 2021-11-09
US20200229245A1 (en) 2020-07-16
US20190124698A1 (en) 2019-04-25
WO2019079379A1 (en) 2019-04-25
US10631343B2 (en) 2020-04-21
CN111226492B (zh) 2023-11-10

Similar Documents

Publication Publication Date Title
EP3698598B1 (de) Techniken zum verbindungsaufbau von millimeterwellenleiterbasierten v2x-kommunikationssystemen
EP3636015B1 (de) Signalisierung von synchronisationsblockmustern
US20200245157A1 (en) Techniques for indicating a preferred beam in wireless communication random access
US20180062801A1 (en) Techniques for wireless communications in coordinated multi-point operation
US11770828B2 (en) Techniques for managing feedback in sidelink communications
US11291006B2 (en) Techniques for configuring active spatial relations in wireless communications
US11503652B2 (en) Apparatus and methods for synchronization signal and random access communications in full duplex
US11778609B2 (en) Techniques for beam sweep based semi-persistent scheduling / configured grant activation
US20220338271A1 (en) Techniques for performing random access in full duplex wireless communications
US20230103927A1 (en) Techniques for managing beams to receive multiple communications
US11996941B2 (en) Techniques for providing dedicated demodulation reference signals for transmission repetitions
US11758549B2 (en) Techniques for handling collision in scheduled wireless communications
CN110710270B (zh) 传递和使用用于sfn型传输的虚拟小区标识
CN114731186A (zh) 无线通信中多分量载波的波束成形技术
US12004177B2 (en) Group common full-duplex (FD) beam
US11716758B2 (en) Receiver assisted transmitter sensing for channel access
US20220046446A1 (en) Channel measurement resources (cmrs) and interferometry interference measurement resources (imrs) from different cells
US20220046611A1 (en) Group common full-duplex (fd) beam

Legal Events

Date Code Title Description
STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: UNKNOWN

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

Free format text: STATUS: THE INTERNATIONAL PUBLICATION HAS BEEN MADE

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

Free format text: ORIGINAL CODE: 0009012

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

Free format text: STATUS: REQUEST FOR EXAMINATION WAS MADE

17P Request for examination filed

Effective date: 20200318

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

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

Free format text: STATUS: EXAMINATION IS IN PROGRESS

17Q First examination report despatched

Effective date: 20211126

RIC1 Information provided on ipc code assigned before grant

Ipc: H04W 84/18 20090101ALN20230515BHEP

Ipc: H04W 8/00 20090101ALN20230515BHEP

Ipc: H04J 13/00 20110101ALI20230515BHEP

Ipc: H04W 4/40 20180101ALI20230515BHEP

Ipc: H04W 74/08 20090101AFI20230515BHEP

RIC1 Information provided on ipc code assigned before grant

Ipc: H04W 84/18 20090101ALN20230522BHEP

Ipc: H04W 8/00 20090101ALN20230522BHEP

Ipc: H04J 13/00 20110101ALI20230522BHEP

Ipc: H04W 4/40 20180101ALI20230522BHEP

Ipc: H04W 74/08 20090101AFI20230522BHEP

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 84/18 20090101ALN20230619BHEP

Ipc: H04W 8/00 20090101ALN20230619BHEP

Ipc: H04J 13/00 20110101ALI20230619BHEP

Ipc: H04W 4/40 20180101ALI20230619BHEP

Ipc: H04W 74/08 20090101AFI20230619BHEP

INTG Intention to grant announced

Effective date: 20230704

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

Owner name: QUALCOMM INCORPORATED

GRAS Grant fee paid

Free format text: ORIGINAL CODE: EPIDOSNIGR3

GRAA (expected) grant

Free format text: ORIGINAL CODE: 0009210

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

Free format text: STATUS: THE PATENT HAS BEEN GRANTED

AK Designated contracting states

Kind code of ref document: B1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

REG Reference to a national code

Ref country code: GB

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: DE

Ref legal event code: R096

Ref document number: 602018062961

Country of ref document: DE

REG Reference to a national code

Ref country code: CH

Ref legal event code: EP

REG Reference to a national code

Ref country code: IE

Ref legal event code: FG4D

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

Ref country code: GR

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

Effective date: 20240321

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

REG Reference to a national code

Ref country code: NL

Ref legal event code: MP

Effective date: 20231220

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

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

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

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

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

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

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

REG Reference to a national code

Ref country code: AT

Ref legal event code: MK05

Ref document number: 1643569

Country of ref document: AT

Kind code of ref document: T

Effective date: 20231220

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

Ref country code: NL

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

Effective date: 20231220