WO2018202310A1 - Surveillance de liaison radio pour communications multifaisceaux - Google Patents

Surveillance de liaison radio pour communications multifaisceaux Download PDF

Info

Publication number
WO2018202310A1
WO2018202310A1 PCT/EP2017/060744 EP2017060744W WO2018202310A1 WO 2018202310 A1 WO2018202310 A1 WO 2018202310A1 EP 2017060744 W EP2017060744 W EP 2017060744W WO 2018202310 A1 WO2018202310 A1 WO 2018202310A1
Authority
WO
WIPO (PCT)
Prior art keywords
sync
primary beam
secondary beam
primary
synchronization
Prior art date
Application number
PCT/EP2017/060744
Other languages
English (en)
Inventor
Timo Koskela
Esa Mikael Malkamaki
Samuli Heikki TURTINEN
Original Assignee
Nokia Technologies Oy
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 Nokia Technologies Oy filed Critical Nokia Technologies Oy
Priority to PCT/EP2017/060744 priority Critical patent/WO2018202310A1/fr
Publication of WO2018202310A1 publication Critical patent/WO2018202310A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W56/00—Synchronisation arrangements
    • H04W56/001—Synchronization between nodes
    • H04W56/0015—Synchronization between nodes one node acting as a reference for the others
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/20—Arrangements for detecting or preventing errors in the information received using signal quality detector

Definitions

  • This description relates to communications, and in particular, to radio link monitoring test procedures for wireless devices.
  • a communication system may be a facility that enables communication between two or more nodes or devices, such as fixed or mobile communication devices. Signals can be carried on wired or wireless carriers.
  • LTE long-term evolution
  • E-UTRA evolved UMTS Terrestrial Radio Access
  • LTE Long Term Evolution
  • APs base stations or access points
  • eNBs enhanced Node AP
  • UE user equipments
  • LTE has included a number of improvements or developments.
  • a user device or UE may monitor its downlink radio link quality and determine whether it is in out-of-sync (OOS) or in in-sync (IS) status.
  • OOS out-of-sync
  • IS in-sync
  • RLM Radio Link Monitoring
  • RLF radio link failure
  • an apparatus includes at least one processor and at least one memory including computer instructions, when executed by the at least one processor, cause the apparatus to: determine, by a user device, a primary beam and a secondary beam for a multi-beam based communications session; count, by the user device, synchronization conditions for the primary beam using at least a first synchronization counter and synchronization conditions for the secondary beam using at least a second synchronization counter; determine, based on an association of each of the counters with either the primary beam or the secondary beam, a first threshold counter value for the first synchronization counter for the primary beam and a second threshold counter value for the second synchronization counter for the secondary beam; determine a primary beam link status for the primary beam and a secondary beam link status for the secondary beam based on the counting and the threshold counter values; and update a radio link failure (RLF) status for the user device based on at least one of the primary beam link status and the secondary beam link status.
  • RLF radio link failure
  • a computer program product includes a computer-readable storage medium and storing executable code that, when executed by at least one data processing apparatus, is configured to cause the at least one data processing apparatus to perform a method including determining, by a user device, a primary beam and a secondary beam for a multi-beam based communications session; counting, by the user device, synchronization conditions for the primary beam using at least a first synchronization counter and synchronization conditions for the secondary beam using at least a second synchronization counter; determining, based on an association of each of the counters with either the primary beam or the secondary beam, a first threshold counter value for the first synchronization counter for the primary beam and a second threshold counter value for the second synchronization counter for the secondary beam; determining a primary beam link status for the primary beam and a secondary beam link status for the secondary beam based on the counting and the threshold counter values; and updating a radio link failure (RLF) status for the user device based on at least one of the primary beam link status
  • RLF radio link failure
  • FIG. 1 is a block diagram of a wireless network according to an example implementation.
  • FIG. 2 is a diagram illustrating beam sweeping for the transmission of a synchronization signal block according to an example implementation.
  • FIG. 3A is diagram illustrating operation of a user device or other network device according to an example implementation.
  • FIG. 3B is a diagram illustrating operation of a user device according to another example implementation.
  • FIG. 4 is a diagram illustrating a downlink control channel monitoring pattern of resources for primary and secondary beams according to an example implementation.
  • FIG. 5 is a diagram illustrating radio link measurement framework according to an example implementation.
  • FIG. 6 is a flow chart illustrating radio link measurement according to an example implementation.
  • FIG. 7 is a block diagram of a node or wireless station (e.g., network device, base station/access point or mobile station/user device/UE) according to an example implementation.
  • a node or wireless station e.g., network device, base station/access point or mobile station/user device/UE
  • FIG. 1 is a block diagram of a wireless network 130 according to an example implementation.
  • user devices 131 , 132, 133 and 135, which may also be referred to as mobile stations (MSs) or user equipment (UEs) may be connected (and in communication) with a base station (BS) 134, which may also be referred to as an access point (AP), an enhanced Node B (eNB) or a network node.
  • AP access point
  • eNB enhanced Node B
  • At least part of the functionalities of an access point (AP), base station (BS) or (e)Node B (eNB) may be also be carried out by any node, server or host which may be operably coupled to a transceiver, such as a remote radio head.
  • BS (or AP) 134 provides wireless coverage within a cell 136, including to user devices 131 , 132, 133 and 135. Although only four user devices are shown as being connected or attached to BS 134, any number of user devices may be provided. BS 134 is also connected to a core network 150 via a S1 interface 151 . This is merely one simple example of a wireless network, and others may be used.
  • a user device may refer to a portable computing device that includes wireless mobile communication devices operating with or without a subscriber identification module (SIM), including, but not limited to, the following types of devices: a mobile station (MS), a mobile phone, a cell phone, a smartphone, a personal digital assistant (PDA), a handset, a device using a wireless modem (alarm or measurement device, etc.), a laptop and/or touch screen computer, a tablet, a phablet, a game console, a notebook, and a multimedia device, as examples.
  • SIM subscriber identification module
  • MS mobile station
  • PDA personal digital assistant
  • a handset a device using a wireless modem (alarm or measurement device, etc.)
  • a laptop and/or touch screen computer a tablet, a phablet, a game console, a notebook, and a multimedia device, as examples.
  • a user device may also be a nearly exclusive uplink only device, of which an example is a camera or video camera loading images or video clips to
  • loT may refer to an ever-growing group of objects that may have Internet or network connectivity, so that these objects may send information to and receive information from other network devices.
  • MTC machine type communication
  • eMTC enhanced machine type communication
  • LoT Internet of Things
  • loT may refer to an ever-growing group of objects that may have Internet or network connectivity, so that these objects may send information to and receive information from other network devices.
  • many sensor type applications or devices may monitor a physical condition or a status, and may send a report to a server or other network device, e.g., when an event occurs.
  • Machine Type Communications (MTC, or Machine to Machine
  • eMTC may be an example of a narrowband user device, where the eMTC or narrowband user device is limited to transmission or reception within a narrowband.
  • loT and/or narrowband loT devices may also include operation within a narrowband.
  • core network 150 may be referred to as Evolved Packet Core (EPC), which may include a mobility management entity (MME) which may handle or assist with mobility/handover of user devices between BSs, one or more gateways that may forward data and control signals between the BSs and packet data networks or the Internet, and other control functions or blocks.
  • EPC Evolved Packet Core
  • MME mobility management entity
  • gateways may forward data and control signals between the BSs and packet data networks or the Internet, and other control functions or blocks.
  • a layer 1 protocol layer may include a physical layer (PHY) for measuring signals, and/or measuring synchronization conditions, such as detecting in-sync (IS) conditions (e.g., where the user device is synchronized to a transmission via a beam) and/or out-of-sync (OOS) conditions (e.g., where the user device detects that it is not synchronized to a transmission via a beam) for one or more beam links at the PHY protocol layer.
  • IS in-sync
  • OOS out-of-sync
  • a layer 2 protocol layer may include, e.g., a media access control (MAC) layer, and/or a radio link control (RLC) layer, a radio link management (RLM) layer, and/or other protocol layer.
  • a layer 3 layer may include, for example, a radio resource control (RRC) layer, for example.
  • RRC radio resource control
  • the various example implementations may be applied to a wide variety of wireless technologies or wireless networks, such as LTE, LTE-A, 5G, cmWave, and/or mmWave band networks, loT, MTC, eMTC, etc., or any other wireless network or wireless technology.
  • wireless technologies or wireless networks such as LTE, LTE-A, 5G, cmWave, and/or mmWave band networks, loT, MTC, eMTC, etc.
  • These example networks or technologies are provided only as illustrative examples, and the various example implementations may be applied to any wireless technology/wireless network.
  • the various example implementations may be applied to a variety of user devices, such as, for example, user devices, UEs, mobile stations, eMTC user devices, and/or loT or narrowband loT user devices.
  • a connected user device e.g., connected to a serving cell/BS
  • a user device may monitor a downlink radio link quality by measuring a signal-to-noise ratio (SNR) of the cell-specific reference signals received from a serving cell/BS.
  • SNR signal-to-noise ratio
  • the user device may compare the SNR of the downlink radio link to a lower threshold (Q ou t) and/or to an upper threshold (Q in ) for the purpose of monitoring downlink radio link quality of the serving cell/BS.
  • the lower threshold Q ou t may be defined as a level at which the downlink radio link cannot be reliably received and may, for example, correspond to a 10% block error rate (BLER) of a hypothetical PDCCH (physical downlink control channel) transmission.
  • the upper threshold Q, n is defined as the level at which the downlink radio link quality can be significantly more reliably received than at Q ou t and may, for example, correspond to 2% BLER of a hypothetical PDCCH transmission.
  • a user device may frequently or even periodically measure a link quality (e.g., SNR) of a downlink radio link, and then compare the link quality (e.g., SNR) of the downlink radio link to a lower threshold (Q ou t) and/or to an upper threshold (0, ⁇ ) to determine whether it is in out-of-sync (OOS) status or in in-sync (IS) status.
  • a link quality e.g., SNR
  • Q ou t a lower threshold
  • an upper threshold 0, ⁇
  • SNR is used as an example link quality in one or more illustrative example implementations described herein, a variety of different link parameters or link qualities may be used for measuring or determining a downlink radio link quality, e.g., such as received signal strength, reference signal received power, error rate (e.g., block error rate), SNR, or other link quality.
  • a downlink radio link quality e.g., such as received signal strength, reference signal received power, error rate (e.g., block error rate), SNR, or other link quality.
  • a user device may follow when comparing a SNR of the downlink radio link quality (e.g., SNR) to the lower threshold (Q ou t) and/or to the upper threshold (Qm).
  • SNR downlink radio link quality
  • Q ou t the lower threshold
  • Qm the upper threshold
  • the user device may periodically measure SNR of reference signals received from the serving cell/BS.
  • RRC radio resource control
  • the downlink radio link quality e.g., SNR (e.g., over a last period of time period of 200 ms or other time period, which may be shorter in beam based systems that require beamforming) is less than Q ou t
  • a physical (PHY) layer (or layer 1 ) of the user device may send an out-of-sync (OOS) indication to higher layer(s) at the user device.
  • OOS out-of-sync
  • An upper layer (e.g., radio resource control/RRC layer) of the user device may increment an OOS counter each time it receives an OOS indication. If a threshold number (e.g., 1 , 2, 3, 4, ...) of (e.g., consecutive) OOS indications are received by the upper layers of the user device without receiving an in-sync (IS) indication from the PHY (or lower layer) of the user device (e.g., OOS counter reaches a threshold number), then a recovery (e.g., T310) timer is started.
  • a threshold number e.g., 1 , 2, 3, 4, .
  • the OOS timer expires before an IS indication is received from the user device PHY (e.g., before a SNR is measured for the downlink radio link that is greater than Qin), then the UE declares a radio link failure (RLF) for the radio link or connection with the serving cell or serving BS.
  • RLF radio link failure
  • the IS counter is incremented for the user device, and the recovery timer is stopped and OOS counter is reset to zero, which prevents the user device from declaring a RLF.
  • a SNR that is in-between Q in and Q ou t will not cause an OOS to be indicated to upper layers, and such an in-between SNR will not generate an IS that will stop a RLF from being triggered.
  • a recovery timer is started (based on one or more received OOS indications)
  • only an IS indication (based on SNR greater than Qin) will prevent a radio link failure (RLF) for the UE/user device, for example.
  • RLF radio link failure
  • the user device After declaring RLF, the user device is no longer connected, but is now disconnected from the previous serving cell/BS, which may also be referred to as idle state or RRC idle state.
  • the user device may be expected to declare it is in out-of-sync (OOS) status, and then user device may eventually trigger or declare a Radio Link Failure (RLF) for the connection.
  • OOS out-of-sync
  • RLF Radio Link Failure
  • the user device may be expected to declare it comes back to in-sync (IS) status, if the downlink signal quality exceeds another predefined threshold Q, n to avoid unnecessarily triggering RLF.
  • a user device may try to find and then establish a connection to the same or a different cell or BS.
  • the user device may perform cell search and measurement, which may include, for example, a user device monitoring one or more signals, e.g., including searching for, synchronizing to, and estimating the received signal quality from one or more neighbor cells.
  • Measurement may include, e.g., the user device tuning its wireless transceiver
  • synchronization signals e.g., primary synchronization signals and secondary synchronization signals
  • acquiring frequency and symbol synchronization and frame synchronization to the neighbor cell determining a physical cell identity or cell ID of the neighbor cell, and measuring a signal quality (e.g., reference signal received power/RSRP or SNR of reference signals) of signals received from the cell.
  • a signal quality e.g., reference signal received power/RSRP or SNR of reference signals
  • the user device may send a random access (e.g., RACH) preamble to the cell/BS for connection establishment (or re-establishment if it is the same cell as before). Once connected, the user device may resume performing RLM for the serving cell/BS.
  • RACH random access
  • Various example implementations may relate, for example, to 5G (New Radio) radio access systems (or other systems) with support for Massive MIMO (multiple input, multiple output) and which may be optimized for operating in high carrier frequencies such as cmWave frequencies (e.g. from 3 GHz onwards) or mmWave frequencies, as examples, according to an illustrative example implementation.
  • Massive MIMO multiple input, multiple output
  • Those illustrative example systems may be characterized by the need for high antenna gain to compensate for increased pathloss and by the need for high capacity and high spectral efficiency to respond to ever increasing wireless traffic.
  • the increased attenuation at higher carrier frequencies may, for example, be compensated by introducing massive (multielement) antenna arrays and correspondingly antenna gain via beamforming at the access point (AP) / base station (BS) and/or user device.
  • the spectral efficiency may typically improve with the number spatial streams the system can support and thus with the number of antenna ports at the BS.
  • spatial multiplexing may include a transmission technique in MIMO wireless communication to transmit independent and separately encoded data signals, so-called streams, from each of the multiple transmit antennas.
  • M-MIMO massive multiple input multiple output
  • a large number of antenna elements may typically be used at a transmitter and/or receiver (e.g., at a base station/access point or other network node).
  • M-MIMO may typically have more spatial links/layers and provides more spatial degrees of freedom.
  • a MIMO or M-MIMO transmitter can generate relatively narrow beams with good spatial separation.
  • such a transmitter can achieve greater beamforming gain, reduce the spatial interference range and obtain greater multiple user spatial multiplexing gain.
  • a MIMO or M-MIMO system may typically have better performance in terms of data rate and link reliability compared with other systems.
  • transceiver architectures may be used for 5G radio access systems: digital, analogue or so-called hybrid, which utilizes a hybrid of digital baseband processing (such as MIMO Multiple Input Multiple Output and /or digital precoding).
  • digital baseband processing such as MIMO Multiple Input Multiple Output and /or digital precoding.
  • beamforming may be used for providing cell coverage.
  • the aforementioned transceiver architectures allows for implementing beam forming in future or 5G radio systems depending on the cost and complexity limitations.
  • systems deployed to lower frequencies (-sub 6 GHz) may be implemented by using fully digital architecture, and the higher frequencies where the number of antenna elements required for cell coverage may range from tens to hundreds may be implemented by using hybrid-architecture, or even fully analogue architecture.
  • FIG. 2 is a diagram illustrating beam sweeping for the transmission of a synchronization signal block according to an example implementation. Different sets of beams are shown for different times, e.g., for different transmit/receive points (TRPs). Only a subset of beams may be active at a time. Thus, a different SSB may be transmitted using a different set of beams.
  • TRPs transmit/receive points
  • a so-called beam sweeping (sweeping subframe or synchronization signal-burst (SS-burst)) may be used to provide coverage for signaling, such as common control channel signaling, with beam forming.
  • Sweeping sub frame/SS-burst may include SS- blocks blocks (SSB) where a single SS block (transmitted by a BS/AP) covers a specific area of the cell with a set of active (transmit) beams.
  • SSB SS- blocks blocks
  • a total number of beams required to cover required cell area is typically much larger than the number of concurrent active beams the BS/AP is able to form. Therefore, for example, BSs/APs may sweep through the cell coverage area in time domain by activating different sets of beams on each SSB.
  • beam sweeping may be performed to generate or activate each of a plurality of sets of beams in the time domain in order to transmit signals across a cell. For example, only one beam may be active, or a set of beams (e.g., 3 beams, 4 beams, 6 beams, or some other number of beams) may be active at a time due to cost and/or complexity.
  • a set of beams e.g., 3 beams, 4 beams, 6 beams, or some other number of beams
  • Various control signals such as synchronization signals (SSs), New Radio synchronization signals (NR-SSs), beam-specific reference signals (RSs), Physical broadcast channel (PBCH), PBCH demodulation reference signals (PBCH-DMRS), Channel State Information Reference Signals (CSI-RS), Beam specific CSI-RS, cell specific CSI-RS, UE specific CSI- RS, DMRS, PBCH DMRS, Mobility Reference Signals (MRS) etc., may be transmitted by BS 134 for typically only one set of beams or for one SS block at a time.
  • SSs synchronization signals
  • NR-SSs New Radio synchronization signals
  • RSs beam-specific reference signals
  • PBCH Physical broadcast channel
  • PBCH-DMRS PBCH demodulation reference signals
  • CSI-RS Channel State Information Reference Signals
  • Beam specific CSI-RS Beam specific CSI-RS
  • cell specific CSI-RS cell specific CSI-RS
  • UE specific CSI- RS DMRS
  • SS may comprise of Primary SS (PSS), Secondary SS (SSS) and additional SS such TSS/ESS (Tertiary Synchronization Signal, Extended Synchronization Signal). While the PSS and SSS may encode a cell identity (such as PCI, physical cell ID) the additional SS may encode the SS-block identifier.
  • PSS and SSS may encode a cell identity (such as PCI, physical cell ID)
  • the additional SS may encode the SS-block identifier.
  • one set of beams or SS block (SSB1 ) that may be used by the BS 134 may include, for example, beam 1 , beam 2, and beam 3, as an illustrative example. Other sets of beams or SS blocks may also be provided by BS 134.
  • BS 134 may sweep across each beam or across each set of beams or SS block, for example.
  • SS block 1 may include a synchronization signal transmitted at the same time on each of beam 1 , beam 2 and beam 3, for example. Synchronization signals may be transmitted for other SS blocks as the BS 134 sweeps around. Alternatively, the BS may transmit control signals, such as a synchronization signal on only one beam at a time. Additionally, SS block may include beam specific reference signals enabling UE to distinguish and measure different beams in a specific SS block In one example the different signals of an SS block may transmitted in different manner: SS/PBCH or other signals may be transmitted using all the beams of an SS block while beam specific signals are transmitted using individual beams. The previously mentioned signals may also be used for radio link monitoring, determining the beam specific IS/OOS conditions.
  • Using these signals may be implicit e.g., if UE is configured with a beam for PDCCH reception based on the reported measurements on beam specific CSI-RS it may assume direct correspondence between the resource used for radio link monitoring.
  • network may configure UE to explicitly monitor specific reference signals to determine beam IS/OOS condition.
  • a user device 132 may measure each of a plurality of beams and determine a best or preferred downlink (DL) transmit beam/SS block that was applied by the BS 134.
  • the user device may measure a signal strength (e.g., RSRP), amplitude or other signal characteristic for each of the beam or non- beam -specific signals (e.g., reference signals, synchronization signals (e.g. SS), or other control signals), and then may determine the best DL transmit beam or alternatively best SS block.
  • the user device 132 may send a beam report to the BS 134 to indicate a best or preferred beam, or a best or preferred set of beams or the SS-block, for example.
  • the BS 134 may then use such identified preferred beam(s) to transmit to the user device 132 (transmit downlink data or control, or both).
  • the best transmit beam may be referred to as a primary beam or primary PDCCH beams
  • the next best transmit beam may be referred to as a secondary beam or secondary PDCCH beam, e.g., which may be used by the user device for multi-beam communications.
  • the user device may also apply a downlink receive beam to receive signals transmitted from a BS/AP, and different receive beams may be applied to receive signals transmitted via different DL transmit beams.
  • a layer 1 protocol layer may include a physical layer (PHY) for measuring signals, and/or measuring synchronization conditions, such as detecting in-sync (IS) conditions (e.g., where the user device is synchronized to a transmission via a beam) and/or out-of-sync (OOS) conditions (e.g., where the user device detects that it is not synchronized to a transmission via a beam) for one or more beam links at the PHY protocol layer.
  • a layer 2 protocol layer may include, e.g., a media access control (MAC) layer, and/or a radio link control (RLC) layer, and/or other protocol layer.
  • a layer 3 layer may include, for example, a radio resource control (RRC) layer, for example.
  • RRC radio resource control
  • FIG. 3A is diagram illustrating operation of a user device or other network device according to an example implementation.
  • a user device may monitor (e.g., receive and measure) signal qualities (e.g., RSRP, SNR or SINR) of signals (e.g., beam-specific reference signals) for a plurality of beams.
  • signal qualities e.g., RSRP, SNR or SINR
  • a set of best beams may be selected by the user device, e.g., those beams having the best RSRP/SNR/SINR, as determined by the UE, for example.
  • a best beam may be selected as a primary beam, and one or more next best beams may be selected as a secondary beam(s).
  • L1 of the user device may detect each of a plurality of beams, and may determine any (or one or more) synchronization conditions (e.g., in-sync (IS) condition and/or out-of-sync (OOS) condition) for each beam of a plurality of beams.
  • IS in-sync
  • OOS out-of-sync
  • a set of K detected beams are shown as being measured, and then one or more beam-specific (or beam-level) synchronization conditions, e.g., ( beam or PDCCH beam- specific IS condition and/or OOS condition) may be reported by L1 to L2 of the user device.
  • L2 of the user device may perform beam level (or beam-specific) failure detection and/or recovery.
  • a beam link failure detected by L2 may be a beam link status that is out-of-sync (OOS).
  • L2 may use or may include synchronization counters to count synchronization conditions reported by L1 . Counters may be provided for each beam, or for at least a primary beam and one or more secondary beams. For example, beam #1 may be selected as a primary beam, and beam #2 may be selected as a secondary beam.
  • an IS counter and an OOS counter may be provided and used for each of at least beam #1 (e.g., the primary beam) and beam #2 (e.g., the secondary beam in this example).
  • L2 may implement or include an IS counter 316 for beam #1 to count a number of consecutive in-sync conditions (e.g., reported by L1 ) for beam #1 , and an OOS counter 318 for beam #1 to count a number of consecutive out-of-sync (OOS) conditions (e.g., reported by L1 ) for beam #1 .
  • OOS out-of-sync
  • L2 may also implement or include an IS counter and an OOS counter for beam #2 (e.g., the secondary beam in this example).
  • L2 of the user device may also include or implement a threshold counter value for each of the synchronization counters. L2 may determine (e.g., as a beam link status of either IS or OOS/beam link failure) e.g., when a synchronization counter reaches or is equal to is respective threshold counter value. For example, an NO threshold counter value may be used for the OOS counter (e.g., 318) for the primary beam, and an N1 threshold counter value may be used for the IS counter for the primary beam.
  • a set of N0/N1 threshold counter values may be used for each of a plurality of beams, such as for each of a primary beam and a secondary beam.
  • a set of threshold counter values 320 may be used for a primary beam
  • a set of threshold counter values 322 may be used for a secondary beam.
  • These threshold counter values may be independent and/or different, and/or may be assigned by the network or BS, or may be determined by the user device (e.g., based on a PDCCH monitoring pattern for resources for primary and secondary beams, or using other technique). Other threshold counter values may be used for other counters.
  • L2 OOS counter 318 for beam #1 may count OOS conditions detected by L1 for the primary beam (beam #1 in this example).
  • L2 may determine a primary beam link status of OOS when the OOS counter 318 for the primary beam reaches or becomes equal to the NO threshold counter value, for example.
  • a L2 OOS counter (not shown) for beam #2 may count OOS conditions detected by L1 for the secondary beam (beam #2 in this example).
  • L2 of the user device may determine a secondary beam link status of OOS when the OOS counter for the secondary beam reaches or becomes equal to the NO threshold counter value for the secondary beam, for example.
  • a beam link status of IS may also be determined by L2 when a number of IS conditions for a beam detected by L1 reaches or is equal to its respective threshold counter value.
  • the counter may only count consecutive IS/OOS indications or they can count a number of IS/OOS indications in a time window of N milliseconds, for example.
  • This time window may also be a moving window, such as, for example, M indications during the last N milliseconds.
  • a beam recovery timer may be provided or used by L2 for each of a plurality of beams (e.g., for the primary beam and each secondary beam(s)).
  • a beam recovery timer 319 may be used for the primary beam.
  • OOS counter 318 reaches or is equal to NO threshold counter value (e.g., meaning a number of consecutive OOS indications from L1 is equal to NO threshold counter value)
  • the beam recovery timer 319, for the primary beam may be started or initiated.
  • the L2 determines a primary beam link status of OOS (beam link failure for that beam).
  • a primary beam link status of OOS beam link failure for that beam.
  • no recovery timer is used and the beam failure is determined based only on the counted number of OOS indications (consecutive/time window).
  • the specific value of conditions (IS or OOS conditions) for a beam is counted, the beam is considered to be in failure (or, in other words, the beam link status is OOS or beam failure/beam link failure).
  • This beam failure/beam link failure may trigger beam recovery actions (e.g., where a new PDCCH beam is obtained, or the UE switches to an alternative PDCCH beam).
  • beam recovery When beam recovery is triggered, it may also trigger an indication of cell level OOS condition to RRC/L3.
  • L2 may report to L3 a cell level synchronization (or link) status, e.g., as either IS or OOS, based on beam link status for one or more beams, such as based on the primary beam link status and/or the secondary beam link status.
  • L2 may report to L3 (e.g., RRC) at 324, a cell level synchronization (or cell level link) condition (or indication) of OOS if a threshold number (e.g., two, or even all) of the beams have a beam link status of OOS (beam failure).
  • L3 e.g., RRC
  • a threshold number e.g., two, or even all
  • implementations may be used to trigger or cause sending a cell level synchronization (or link) status or condition (e.g., OOS or IS).
  • a cell level synchronization (or link) status or condition e.g., OOS or IS.
  • OOS cell level synchronization
  • an OOS cell level status or condition may be reported or signaled by L2 to L3 when either: 1 ) only the primary beam link status is OOS (out-of-sync), which is a beam link failure for the primary beam; 2) . or both the primary beam link status and the secondary beam link status are OOS (out-of-sync), which means that both the primary beam and the secondary beam have failed (beam failure, as determined by L2).
  • L3 of the user device may perform cell level (as opposed to beam level) radio link failure detection and/or recovery.
  • L3 may receive, e.g., from L2, a cell level synchronization (or link) status (or condition or indication), such as a cell level IS or OOS status or indication.
  • L3 may include one or more timers, such as a T310 cell level (or RRC) radio link recovery timer 334.
  • One or more cell level timer values may be provided as well, including one or more timer values for the cell level radio link recovery timer 334.
  • the cell level radio link recovery timer may be started by L3 if a cell level threshold number of (e.g., consecutive) cell level OOS indications have been received by L3.
  • the user device may, for example, declare a (cell level) radio link failure (RLF) for the user device.
  • RLF radio link failure
  • L3 may receive, e.g., from L2, a beam link status for one or more beams, such as for a primary beam and/or a secondary beam(s), and may perform cell level radio link failure detection and/or recovery based on beam link status for primary and secondary beams. Additional example features, by way of illustrative examples, will now be described.
  • a cell may be covered using multiple narrow beams (narrow compared with the sector beams). Radio link monitoring may be performed based on beams configured for PDCCH (physical downlink control channel) reception:
  • PDCCH physical downlink control channel
  • PDCCH beams may be explicitly configured/indicated to UE by network or BS using MAC CE/DCI (downlink control information) (or RRC message);
  • MAC CE/DCI downlink control information
  • UE performs radio link monitoring based on the beam specific reference signals:
  • non-cell specific reference signals e.g.
  • o NW may configure UE/user device to perform RLM (radio link measurement) on reference signal, e.g., such as one or more of CSI- RS/DMRS/PBCH-DMRS/MRS/BRS/SSblock/SSS signals;
  • RLM radio link measurement
  • o RLM (radio link measurement) signals may be present in SS-block
  • RRC may operate at cell level (e.g., L3); and L2 may handle beam level IS/OOS indications reported by L1 to determine whether to initiate beam recovery (or beam switch).
  • Beam level IS/OOS indications may be based on PDCCH beams or beams corresponding to PDCCH.
  • IS/OOS indication(s) may be based on the measurements on CSI-RS resource(s) corresponding the PDCCH beam or beams.
  • Cell level IS/OOS determinations can be determined, e.g., based on rules such as if all (or alternatively for both primary and secondary) PDCCH beams (beam link status) are OOS then L2 indicates cell level OOS status for all beams. Otherwise cell (radio link for cell) would be IS as there are still one or more PDCCH beams available that can be received by the UE (at least one PDCCH beam that is IS (in-sync), and thus, can be received by UE).
  • L2/L1 may attempt to recover a link or beam link (e.g., obtain new PDCCH beams, such as by reporting new/detected beams to the network BS) before cell level RLF is declared by L3.
  • a cell level radio link recovery timer 334 (T310), e.g., always if UE initiates beam recovery, or if even one PDCCH beam (beam link status) is OOS, or when all beams are considered out of sync, or when a threshold number of beams are OOS.
  • a beam failure for a beam is declared before the beam recovery is triggered or the beam is considered to be in OOS condition (beam link status of OOS, e.g., requiring a specific number OOS indications received/determined by L1 ).
  • Network/BS may configure PDCCH beam specific IS/OOS threshold counters values (e.g., NW/BS may indicate N1 b eam# and N0beam# threshold counter values for each beam). For example, for N beams, there will be N sets of
  • parameters/threshold counter values UE has been configured with A/-PDCCH beams, there are N sets of parameters, one set of parameters/threshold counter values for each beam. Also, for example, when L2 receives NO consecutive OOS indications for a beam from L1 , this beam is considered to have a beam link status of out-of-sync (OOS) or in "beam failure" (beam link status for this beam is OOS/beam link failure).
  • OOS out-of-sync
  • the illustrated example shown in FIG. 3A is merely one illustrative example implementation. In other example implementations, all or some of the functions shown at (or performed by) layer 1 and layer 2 may be performed by only one layer, e.g., either layer 1 or layer 2, for example.
  • the beam specific counters (shown in FIG. 3A as being provided at L2) may be at L1 , and L1 may indicate to L3 the cell level IS/OOS indications.
  • the L1 may provide beam link status (IS/OOS) to L3 for various beams, and L3 determines cell level status (IS/OOS) of radio link based on the received beam link status for e.g., primary beam and secondary beam.
  • the example implementation illustrated in FIG. 3A is merely one illustrative example, and uses, by way of example, functions performed by each of the three layers, including at layer 1 (L1 ) (e.g., detecting and reporting synchronization (e.g., IS/OOS) conditions to L2), layer 2 (L2) (e.g., beam level radio link management/ beam level failure and detection/recovery) and layer 3 (L3) (cell level radio link management/cell level radio link failure detection/recovery).
  • L1 detecting and reporting synchronization
  • L2 e.g., beam level radio link management/ beam level failure and detection/recovery
  • L3 cell level radio link management/cell level radio link failure detection/recovery
  • FIG. 3A includes a three layer, e.g., L1 ->L2->L3, structure or operation.
  • FIG. 3B illustrates another example implementation.
  • FIG. 3B is a diagram illustrating operation of a user device according to another example implementation.
  • a structure or operation (of at least some functions or operation) may use a two layer structure or operation, L1 ->L3, e.g., in which the L1 functions and (at least some of the ) L2 functions from the example of FIG. 3A are performed or provided by layer 1 (L1 ) in FIG. 3B.
  • L3 may be the same as L3 in FIG. 3A.
  • 3B may perform: detecting synchronization (e.g., IS/OOS) conditions, and beam level radio link management/ beam level failure and detection/recovery, and then reporting cell level synchronization status or conditions (cell level IS or OOS) to L3, e.g., without assistance of L2.
  • L2 beam level RLM
  • IS/OOS indications for each beam may be handled/processed (e.g., to determine when a beam link has failed) at L1
  • cell level IS/OOS status or conditions may be sent directly from L1 to L3 in such example
  • FIG. 4 is a diagram illustrating a downlink control channel (e.g., PDCCH) monitoring pattern of resources for primary and secondary beams according to an example implementation.
  • a user device 132 may apply receive beam A when the BS/cell applies a primary beam for transmission, and apply a receive beam B when the BS/cell applies secondary beam for transmission, for example.
  • the downlink control channel monitoring pattern identifies resources (e.g., slots) for receiving signals via the primary beam (P slots) and the secondary beam (S slots).
  • resources e.g., slots
  • the user device 132 would monitor or receive signals via five P (primary beam) slots (by applying receive beam A), then monitor or receive signals via one S (secondary beam) slot (by applying receive beam B), and then repeating.
  • the user device monitors the signals received during the P slots via the primary transmit (TX) beam by applying the DL receive beam A, and monitors the signals received during the S slots via the secondary TX beam by applying receive beam B.
  • FIG. 4 illustrates a monitoring pattern for primary and secondary beams.
  • Primary and secondary beams to be used for DL transmission via slots A and B may be signalled by NW/BS to UE via DCI (downlink control information).
  • UE may have different beams to monitor, but can monitor PDCCH over 1 beam at a time; NW may signal UE receive (RX) beam A (for UE reception of PDCCH), and UE RX beam B. These might be 2 best beams for the UE, as reported by UE. Or UE may determine its two best beams to be used as beams A and B (e.g., to be applied by UE when BS transmits via primary and secondary beams, respectively). Alternatively UE may be able to receive using multiple beams simultaneously and network may transmit PDCCH using multiple DL beams simultaneously.
  • NW may signal UE receive (RX) beam A (for UE reception of PDCCH), and UE RX beam B. These might be 2 best beams for the UE, as reported by UE.
  • UE may determine its two best beams to be used as beams A and B (e.g., to be applied by UE when BS transmits via primary and secondary beams, respectively).
  • UE may be able to receive using
  • PDCCH would be transmitted with so called composite beam: UE would receive PDCCH via multiple beam links simultaneously, e.g., using a set of receive beams (A and B) simultaneously. Also, in this case, UE may monitor the PDCCH (and network may transmit) on primary and secondary set of receive beams. From radio link perspective, as long as one of the used beams of the composite PDCCH beam is in IS condition (or is not considered to be in failure), the composite beam is considered to be in IS condition.
  • L1 can determine composite beam IS/OOS condition(s) in similar manner from the corresponding beam specific reference signals such as CSI-RS.
  • the illustrated model is one implementation option.
  • the beam specific counters may be at L1 and L1 indicates to L3 the cell level IS/OOS condition and/or beam link status.
  • the L1 provides beam link status (IS/OOS) to L3 that determines cell level condition/status of radio link.
  • the network or BS may configure (e.g., BS may send control information indicating) a downlink control channel (e.g., PDCCH) monitoring pattern, which may allow the user device/UE to monitor PDCCH on multiple network (NW) beams with specific pattern (A beam/B beam), with A receive beam being applied by UE as a receive beam during P slots (for primary DL transmit beam), and B receive beam being applied by UE as a receive beam during S slots (for secondary DL transmit beam).
  • NW network
  • a receive beam or B receive beam is active (applied by UE as receive beam).
  • NW/BS are synchronized to the pattern.
  • the network/BS has configured 2 beams for PDCCH reception for UE in two distinctive receive directions (A receive beam, and B receive beam are in different directions, for example).
  • PDCCH monitoring patter for X time units (e.g., 5 slots), the UE monitors PDCCH using beam A, and for Y time units (e.g., 1 slot) the UE monitors PDCCH using beam B (during S slots).
  • Network/BS knows the UE beam alignment based on the pattern.
  • the Primary/Secondary PDCCH DL transmit beams are defined and associated with time slots P and S, respectively (and associated with receive beams A and B, respectively).
  • Beam specific counters or timers may be handled differently depending on the beam type (e.g., primary or secondary beam) of the PDCCH beam.
  • primary and secondary PDCCH beams may be handled differently.
  • primary and secondary beams (DL control channel transmit beams) may be beams assigned by the network or BS to UE; NW/BS has primary and secondary DL PDCCH transmit beams that are assigned to UE, and used by the BS to transmit PDCCH to the UE; and the UE has determined its (e.g., two) best beams it should use, such as an A beam and B beam to receive PDCCH via primary (P) slot and secondary (S) slots, respectively (FIG. 4).
  • P primary
  • S secondary
  • NW/BS may provide the downlink control channel monitoring pattern of resources for PDCCH for primary(P) slot/resource and secondary (S) slot/resource; NW determined the primary and secondary DL TX beams to be used, e.g., based on beam reports from UE. UE also determines its beams A and B to use for DL receive beams based on beam
  • threshold counter values NO, N1 for primary and secondary beams may be based on either PDCCH monitoring pattern of resources, or explicitly signalled by BS to UE. Based on the association of Primary and Secondary PDCCH beams, the beam specific counters may be configured with the counter values as follows, by way of illustrative example:
  • the threshold counter (maximum) values may be based on the PDCCH monitoring pattern (e.g., based on how many P slots or S slots are in a specific window, or based on a ratio of P slots and S slots to total number of slots in a window, or based on a ratio of P slots to S slots);
  • a threshold counter value for a beam may be inversely proportional to a number of slots for the beam within a window, as indicated by the monitoring pattern, which means that typically a primary beam (having more slots, e.g., as P slots, FIG.
  • a counter threshold value for the primary beam 1 or 2
  • a threshold counter value for the secondary beam 3
  • the user device may tolerate fewer OOS indications for the primary beam before reaching the counter threshold and declaring an OOS (failed) beam link status (e.g., because resources for such beam may be transmitted or provided more frequently).
  • the user device may tolerate more OOS indications for such secondary or backup beam (e.g., a higher number of OOS indications from L1 , based on higher threshold counter value, are required or permitted before an OOS/failed beam link status is declared for that beam).
  • a slot may here mean, e.g., a PDCCH symbol, a slot of a subframe, a subframe, or a radio frame, or any time based configuration or resource, such as one monitoring slot can be X milliseconds or expressed in multiples of a symbol, multiples of a subframe, etc.
  • the network or BS may send signalling, or explicitly indicate (e.g., via RRC configuration or MAC CE/control element, downlink control information), that identifies threshold counter values for each of the primary and secondary PDCCH beams. Also, in both cases, if a new beam is configured as a PDCCH beam for the UE (as either the primary beam or secondary beam), the UE may then typically reset the counters, for example. Alternatively, the counter may not be reset but the new beam (or the corresponding reference signal) is used to evaluate the IS/OOS condition.
  • the threshold counter value for a beam-specific counters for one of the beams may be adjusted (or a different threshold counter value may be used) based on a status (e.g., IS/OOS) of another beam, based on detecting or receiving one or more IS/OOS conditions from L1 , or based on how many OOS indications have been received by L2 from L1 for another beam.
  • a status e.g., IS/OOS
  • a threshold counter value for a secondary beam may be decreased (e.g., to cause a quicker change to OOS/failed beam link status for the secondary beam) if a predetermined number (Xprimaryoos) which is less than the threshold counter value for the primary beam) of OOS indications have been received by L2 from L1 for the primary beam.
  • the user device may now be less tolerant (e.g., based on a decreasing of threshold counter value for secondary beam) of OOS indications for the secondary beam if a predetermined number (Xprimaryoos) of OOS indications for the primary beam have already been detected by L1 and signalled to L2.
  • L2 may decrease threshold counter value for the secondary beam.
  • this predetermined number (Xprimaryoos ) may be less than the associated threshold counter value for the primary beam.
  • a threshold counter value is set to 5 OOS indications for the primary beam, then, for example, a predetermined value of 2 OOS indications for the primary beam may be used to trigger or cause L2 to decrease the threshold counter value for the secondary beam.
  • This approach may also be reversed or switched, e.g., that is where receipt by L2 of one or more (or a predetermined number of) OOS indications for the secondary beam may be used to adjust (e.g., decrease) the threshold counter value for the primary beam.
  • L1 indicates Xprimaryoos consecutive (or in a window) OOS for the primary PDCCH beam it requires only Ysecondaryoos (the new or adjusted threshold for secondary beam) consecutive OOS indications for the secondary PDCCH beam to be considered in beam failure or OOS beam link status.
  • Ysecondaryoos the new or adjusted threshold for secondary beam
  • the user device may lower the threshold counter value for secondary, as noted above, which may increase the speed or likelihood of a RLF at a cell level.
  • These conditions may reset if new beam is configured as primary or secondary, in case primary or secondary beam is considered to be again in IS condition.
  • Values for X P nmar y oos and Ysecondaryoos may, for example, be configured by network via DCI/MAC/RRC signalling in different combinations so that RRC provides one set of values which can be modified by MAC/DCI or MAC/DCI may point to different set of values that are RRC configured.
  • the secondary value applies for rest of the PDCCH beams or derived by the ratio of P and S slots.
  • threshold counter values for these multiple secondary beams may be similarly adjusted or decreased in the same manner as described above for 1 secondary beam.
  • different timer values for the cell level radio link recovery timer may be used (or the timer value may be adjusted) based on different or various beam link status (e.g., IS beam link status, or OOS beam link status), or receipt or detection of one or more beam conditions (e.g., IS or OOS conditions detected by L1 ) of the primary beam and/or the secondary beam, for example.
  • beam link status e.g., IS beam link status, or OOS beam link status
  • a cell level synchronization (or link) status or condition of OOS may be reported by L2 to L3, along with the new or updated timer value that the L3 should use for the cell level radio link recovery timer.
  • the new timer value may simply be reported by L2 to L3 with a command to start the timer, for example. L3 may then, for example, start or initiate the recovery timer using the new or updated timer value.
  • Multiple timer values may be configured for RRC cell level recovery timer (e.g., T310 values).
  • One timer value out of multiple timer values may be used, such as one of: T1_a (long timer), T1_b (medium timer, shorter than the long timer), and T1_c (short timer, shorter than medium timer).
  • these possible timer values may be used for the cell level (RRC) recovery timer depending on the situation, e.g., depending on beam link status of the primary or secondary beams, or depending on whether 1 (or a predetermined number) of OOS conditions have been detected by L1 for a beam, etc. For example, as one or more beams degrade, such as, e.g., as one or more beam links fail, or beam link status is
  • a shorter timer value for the cell or RRC recovery timer may be used, e.g., to allow a quicker or less tolerant triggering of RLF for the radio link at L3.
  • L2 indicates to higher layer (RRC or L3) to start either T1_a, T1_b or T1_c based on following conditions, by way of illustrative example: :
  • Long timer (T1_a) may be initiated when L2 detects (e.g., a predetermined number of) OOS condition(s) on primary PDCCH beam only (or alternatively when L2 declares the primary beam link as OOS/failed);
  • Medium timer (T1_b, shorter than T1_a) may be initiated when L2 detects OOS conditions (e.g., a predetermined of OOS conditions detected by L1 ) on both primary and secondary PDCCH beams (or alternatively when L2 declares both the primary beam link and the secondary beam link as OOS/failed), and at least one alternative beams are detected in the cell with signal level above threshold_1 ; and
  • OOS conditions e.g., a predetermined of OOS conditions detected by L1
  • Short timer (T1_c, shorter than T1_b) may be initiated when L2 detects OOS conditions on both primary and secondary PDCCH beams (or alternatively when primary and secondary beam links have been declared OOS/failed), and no alternative beams are detected in the cell with signal level above threshold_1 .
  • the timer at L3 could be advanced (so that it would expire sooner) or L2 could indicate Expire to L3 which would lead to RLF directly/immediately.
  • L2 can be determined by L2 based on lower layer (L1 ) beam specific synchronization (IS or OOS) indications.
  • L1 lower layer
  • IS or OOS beam specific synchronization
  • L2 may indicate to higher layers (e.g., RRC or L3) potentially initiate recovery related actions (such as start recovery timer T310) depending on which beam indicated a beam link problem (OOS).
  • OOS beam link problem
  • FIG. 5 is a diagram illustrating radio link measurement framework according to an example implementation.
  • FIG. 5 illustrates an example RLM framework with beam level IS/OOS and cell level IS/OOS with L1 /L2/L3 inter action.
  • Alternative implementations can consider e.g. having cell level IS/OOS indication logic implemented at L1 (L1 handles IS/OOS per beam and determines what to indicate to L3) or yet in another alternative L1 indicates beam IS/OOS) to RRC/L3 directly and RRC runs the cell level logic based on beam specific indications.
  • beams are received or monitored at L1 .
  • L2 performs L2 RLM functions
  • L3/RRC layer performs cell level radio link failure detection and recovery.
  • OOS condition 512 for beam #1 causes beam #1 to have a beam link status 514 of OOS.
  • OOS condition 516 for beam #0 causes beam #0 to have a beam link status 518 of OOS.
  • this causes L2, for example, at 520, to send a cell level OOS indication to L3/RRC and thereby cause cell level recovery timer to start.
  • IS condition 522 for beam #1 causes beam #1 to have a beam link status 524 of IS, which then causes L2 RLM, at 526, to send a cell level IS indication to L3/RRC and thereby stop the cell level recovery timer, for example.
  • FIG. 6 is a flow chart illustrating radio link measurement according to an example implementation.
  • Operation 610 includes determining, by a user device, a primary beam and a secondary beam for a multi-beam based communications session.
  • Operation 620 includes counting, by the user device, synchronization conditions for the primary beam using at least a first synchronization counter and synchronization conditions for the secondary beam using at least a second synchronization counter.
  • Operation 630 includes determining, based on an association of each of the counters with either the primary beam or the secondary beam, a first threshold counter value for the first synchronization counter for the primary beam and a second threshold counter value for the second synchronization counter for the secondary beam.
  • Operation 640 includes determining a primary beam link status for the primary beam and a secondary beam link status for the secondary beam based on the counting and the threshold counter values.
  • operation 650 includes updating a radio link failure (RLF) status for the user device based on at least one of the primary beam link status and the secondary beam link status.
  • RLF radio link failure
  • Example 2 The method of example 1 ,wherein the updating comprises:
  • Example 3 The method of any of examples 1 -2, wherein the determining a primary beam and a secondary beam comprises: monitoring, by a user device operating in a multi-beam based communication session, signal qualities for a plurality of beams;
  • Example 4 The method of any of examples 1 -3, wherein the counting comprises at least one of the following: counting in-sync (IS) conditions of the primary beam using a first in-sync counter; counting out-of-sync (OOS) conditions of the primary beam using a first out-of-sync counter; counting in-sync conditions of the secondary beam using a second in-sync counter; and counting out-of-sync conditions of the secondary beam using a second out-of-sync counter.
  • IS in-sync
  • OOS out-of-sync
  • Example 5 The method of any of examples 1 -4, wherein the determining a first threshold counter value for the first synchronization counter for the primary beam and a second threshold counter value for the second synchronization counter for the secondary beam comprises: receiving, by the user device, information indicating a downlink control channel monitoring pattern of resources for the primary beam and the secondary beam; and determining, by the user device based on the downlink control channel monitoring pattern of resources for primary beam and the secondary beam, the first threshold counter value for the first synchronization counter for the primary beam and the second threshold counter value for the second synchronization counter for the secondary beam.
  • Example 6 The method of any of examples 1 -5, wherein the determining a first threshold counter value for the first synchronization counter for the primary beam and a second threshold counter value for the second synchronization counter for the secondary beam comprises: receiving, by the user device, information indicating the first threshold counter value for the first synchronization counter for the primary beam and the second threshold counter value for the second synchronization counter for the secondary beam.
  • Example 7 The method of any of examples 1 -6, wherein the counting comprises: counting out-of-sync (OOS) conditions of the primary beam using a first out-of- sync counter; and counting out-of-sync conditions of the secondary beam using a second out- of-sync counter; wherein the determining a primary beam link status for the primary beam and a secondary beam link status for the secondary beam comprises: determining the primary beam link status is out-of-sync if a number of consecutive out-of-sync conditions of the primary beam is equal to the first threshold counter value; and determining the secondary beam link status is out-of-sync if a number of consecutive out-of-sync conditions of the secondary beam is equal to the second threshold counter value.
  • OOS out-of-sync
  • Example 8 The method of any of examples 1 -7, wherein the determining a primary beam link status for the primary beam and a secondary beam link status for the secondary beam based on the counting and the threshold counter values comprises:
  • Example 9 The method of any of examples 1 -8, further comprising:
  • Example 10 The method of any of examples 1 -9, wherein the adjusting comprises decreasing the second threshold counter value or using a lower second threshold counter value to cause the secondary beam link status to change to out-of-sync based on a lower number of consecutive out-of-sync conditions counted for the secondary beam.
  • Example 1 1 The method of any of examples 1 -10, and further comprising: selecting one of a plurality of timer values for a cell level radio link recovery timer depending upon a number of synchronization conditions counted for at least one of the primary beam and the secondary beam.
  • Example 12 The method of any of examples 1 -1 1 , and further comprising: selecting one of a plurality of timer values for a cell level radio link recovery timer depending upon a number of out-of-sync conditions counted for at least one of the primary beam and the secondary beam.
  • Example 13 The method of any of examples 1 -12, and further comprising: selecting one of a plurality of timer values for a cell level radio link recovery timer depending upon the primary beam link status and the secondary beam link status.
  • Example 14 The method of any of examples 1 -13, wherein the selecting comprises: selecting a first timer value for the radio link recovery timer if the primary beam link status is out-of-sync and the secondary beam link status is in-sync; selecting a second timer value, less than the first timer value, for the radio link recovery timer if the primary beam link status is out-of-sync and the secondary beam link status is out-of-sync.
  • Example 15 The method of any of examples 1 -14, wherein the selecting comprises: selecting a first timer value for the radio link recovery timer if the primary beam link status is out-of-sync and the secondary beam link status is in-synch; selecting a second timer value, less than the first timer value, for the radio link recovery timer if the primary beam link status is out-of-sync and the secondary beam link status is out-of-sync and one or more alternative beams have been detected with a signal quality greater than a signal threshold; and selecting a third timer value, less than the second timer value, for the radio link recovery timer if the primary beam link status is out-of-sync and the secondary beam link status is out- of-sync and no alternative beams have been detected with a signal quality greater than a signal threshold.
  • Example 16 An apparatus comprising at least one processor and at least one memory including computer instructions, when executed by the at least one processor, cause the apparatus to perform a method of any of examples 1 -15.
  • Example 17 An apparatus comprising means for performing the method of any of examples 1 -15.
  • FIG. 7 is a block diagram of a wireless station (e.g., AP or user device) 800 according to an example implementation.
  • the wireless station 800 may include, for example, one or two RF (radio frequency) or wireless transceivers 802A, 802B, where each wireless transceiver includes a transmitter to transmit signals and a receiver to receive signals.
  • the wireless station also includes a processor or control unit/entity (controller) 804 to execute instructions or software and control transmission and receptions of signals, and a memory 806 to store data and/or instructions.
  • Processor 804 may also make decisions or determinations, generate frames, packets or messages for transmission, decode received frames or messages for further processing, and other tasks or functions described herein.
  • Processor 804 which may be a baseband processor, for example, may generate messages, packets, frames or other signals for transmission via wireless transceiver 802 (802A or 802B).
  • Processor 804 may control transmission of signals or messages over a wireless network, and may control the reception of signals or messages, etc., via a wireless network (e.g., after being down-converted by wireless transceiver 802, for example).
  • Processor 804 may be programmable and capable of executing software or other instructions stored in memory or on other computer media to perform the various tasks and functions described above, such as one or more of the tasks or methods described above.
  • Processor 804 may be (or may include), for example, hardware, programmable logic, a programmable processor that executes software or firmware, and/or any combination of these.
  • processor 804 and transceiver 802 together may be considered as a wireless transmitter/receiver system, for example.
  • a controller (or processor) 808 may execute software and instructions, and may provide overall control for the station 800, and may provide control for other systems not shown in FIG. 7, such as controlling input/output devices (e.g., display, keypad), and/or may execute software for one or more applications that may be provided on wireless station 800, such as, for example, an email program, audio/video applications, a word processor, a Voice over IP application, or other application or software.
  • a storage medium may be provided that includes stored
  • RF or wireless transceiver(s) 802A/802B may receive signals or data and/or transmit or send signals or data.
  • Processor 804 (and possibly transceivers 802A/802B) may control the RF or wireless transceiver 802A or 802B to receive, send, broadcast or transmit signals or data.
  • the embodiments are not, however, restricted to the system that is given as an example, but a person skilled in the art may apply the solution to other communication systems.
  • Another example of a suitable communications system is the 5G concept. It is assumed that network architecture in 5G will be quite similar to that of the LTE-advanced. 5G is likely to use multiple input - multiple output (MIMO) antennas, many more base stations or nodes than the LTE (a so-called small cell concept), including macro sites operating in cooperation with smaller stations and perhaps also employing a variety of radio technologies for better coverage and enhanced data rates.
  • MIMO multiple input - multiple output
  • NFV network functions virtualization
  • a virtualized network function may comprise one or more virtual machines running computer program codes using standard or general type servers instead of customized hardware. Cloud computing or data storage may also be utilized.
  • radio communications this may mean node operations may be carried out, at least partly, in a server, host or node operationally coupled to a remote radio head. It is also possible that node operations will be distributed among a plurality of servers, nodes or hosts. It should also be understood that the distribution of labour between core network operations and base station operations may differ from that of the LTE or even be nonexistent.
  • Implementations of the various techniques described herein may be implemented in digital electronic circuitry, or in computer hardware, firmware, software, or in combinations of them. Implementations may implemented as a computer program product, i.e., a computer program tangibly embodied in an information carrier, e.g., in a
  • a machine-readable storage device or in a propagated signal for execution by, or to control the operation of, a data processing apparatus, e.g., a programmable processor, a computer, or multiple computers. Implementations may also be provided on a computer readable medium or computer readable storage medium, which may be a non-transitory medium.
  • Implementations of the various techniques may also include implementations provided via transitory signals or media, and/or programs and/or software implementations that are downloadable via the Internet or other network(s), either wired networks and/or wireless networks.
  • implementations may be provided via machine type communications (MTC), and also via an Internet of Things (IOT).
  • MTC machine type communications
  • IOT Internet of Things
  • the computer program may be in source code form, object code form, or in some intermediate form, and it may be stored in some sort of carrier, distribution medium, or computer readable medium, which may be any entity or device capable of carrying the program.
  • carrier include a record medium, computer memory, read-only memory, photoelectrical and/or electrical carrier signal, telecommunications signal, and software distribution package, for example.
  • the computer program may be executed in a single electronic digital computer or it may be distributed amongst a number of computers.
  • implementations of the various techniques described herein may use a cyber-physical system (CPS) (a system of collaborating computational elements controlling physical entities).
  • CPS may enable the implementation and exploitation of massive amounts of interconnected ICT devices (sensors, actuators, processors microcontrollers, etc embedded in physical objects at different locations.
  • ICT devices sensors, actuators, processors microcontrollers, etc.
  • Mobile cyber physical systems in which the physical system in question has inherent mobility, are a subcategory of cyber-physical systems. Examples of mobile physical systems include mobile robotics and electronics transported by humans or animals. The rise in popularity of smartphones has increased interest in the area of mobile cyber-physical systems. Therefore, various implementations of techniques described herein may be provided via one or more of these technologies.
  • a computer program such as the computer program(s) described above, can be written in any form of programming language, including compiled or interpreted languages, and can be deployed in any form, including as a stand-alone program or as a module, component, subroutine, or other unit or part of it suitable for use in a computing environment.
  • a computer program can be deployed to be executed on one computer or on multiple computers at one site or distributed across multiple sites and interconnected by a
  • Method steps may be performed by one or more programmable processors executing a computer program or computer program portions to perform functions by operating on input data and generating output. Method steps also may be performed by, and an apparatus may be implemented as, special purpose logic circuitry, e.g., an FPGA (field programmable gate array) or an ASIC (application-specific integrated circuit).
  • FPGA field programmable gate array
  • ASIC application-specific integrated circuit
  • processors suitable for the execution of a computer program include, by way of example, both general and special purpose microprocessors, and any one or more processors of any kind of digital computer, chip or chipset.
  • a processor will receive instructions and data from a read-only memory or a random access memory or both.
  • Elements of a computer may include at least one processor for executing instructions and one or more memory devices for storing instructions and data.
  • a computer also may include, or be operatively coupled to receive data from or transfer data to, or both, one or more mass storage devices for storing data, e.g., magnetic, magneto-optical disks, or optical disks.
  • Information carriers suitable for embodying computer program instructions and data include all forms of non-volatile memory, including by way of example semiconductor memory devices, e.g., EPROM, EEPROM, and flash memory devices; magnetic disks, e.g., internal hard disks or removable disks; magneto-optical disks; and CD-ROM and DVD-ROM disks.
  • semiconductor memory devices e.g., EPROM, EEPROM, and flash memory devices
  • magnetic disks e.g., internal hard disks or removable disks
  • magneto-optical disks e.g., CD-ROM and DVD-ROM disks.
  • the processor and the memory may be supplemented by, or incorporated in, special purpose logic circuitry.
  • implementations may be implemented on a computer having a display device, e.g., a cathode ray tube (CRT) or liquid crystal display (LCD) monitor, for displaying information to the user and a user interface, such as a keyboard and a pointing device, e.g., a mouse or a trackball, by which the user can provide input to the computer.
  • a display device e.g., a cathode ray tube (CRT) or liquid crystal display (LCD) monitor
  • a user interface such as a keyboard and a pointing device, e.g., a mouse or a trackball
  • Other kinds of devices can be used to provide for interaction with a user as well; for example, feedback provided to the user can be any form of sensory feedback, e.g., visual feedback, auditory feedback, or tactile feedback; and input from the user can be received in any form, including acoustic, speech, or tactile input.
  • Implementations may be implemented in a computing system that includes a back-end component, e.g., as a data server, or that includes a middleware component, e.g., an application server, or that includes a front-end component, e.g., a client computer having a graphical user interface or a Web browser through which a user can interact with an implementation, or any combination of such back-end, middleware, or front-end components.
  • Components may be interconnected by any form or medium of digital data communication, e.g., a communication network. Examples of communication networks include a local area network (LAN) and a wide area network (WAN), e.g., the Internet.
  • LAN local area network
  • WAN wide area network

Landscapes

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

Abstract

L'invention concerne une technique comprenant les étapes suivantes : détermination d'un faisceau primaire et d'un faisceau secondaire par un dispositif utilisateur ; comptage des conditions de synchronisation pour le faisceau primaire au moyen d'au moins un premier compteur de synchronisation et des conditions de synchronisation pour le faisceau secondaire au moyen d'au moins un second compteur de synchronisation ; détermination, sur la base d'une association de chacun des compteurs avec soit le faisceau primaire soit le faisceau secondaire, d'une première valeur seuil du premier compteur de synchronisation pour le faisceau primaire et d'une seconde valeur seuil du second compteur de synchronisation pour le faisceau secondaire ; détermination d'un état de liaison de faisceau pour le faisceau primaire et d'un état de liaison pour le faisceau secondaire sur la base du comptage et des valeurs seuils des compteurs ; et mise à jour d'un état de défaillance de la liaison radio (RLF) pour le dispositif utilisateur sur la base d'au moins l'état de liaison du faisceau primaire et/ou l'état de liaison du faisceau secondaire.
PCT/EP2017/060744 2017-05-05 2017-05-05 Surveillance de liaison radio pour communications multifaisceaux WO2018202310A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/EP2017/060744 WO2018202310A1 (fr) 2017-05-05 2017-05-05 Surveillance de liaison radio pour communications multifaisceaux

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/EP2017/060744 WO2018202310A1 (fr) 2017-05-05 2017-05-05 Surveillance de liaison radio pour communications multifaisceaux

Publications (1)

Publication Number Publication Date
WO2018202310A1 true WO2018202310A1 (fr) 2018-11-08

Family

ID=58671672

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/EP2017/060744 WO2018202310A1 (fr) 2017-05-05 2017-05-05 Surveillance de liaison radio pour communications multifaisceaux

Country Status (1)

Country Link
WO (1) WO2018202310A1 (fr)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020097813A1 (fr) * 2018-11-14 2020-05-22 华为技术有限公司 Procédé, appareil, et système de mesure de mobilité
WO2023011285A1 (fr) * 2021-08-02 2023-02-09 索尼集团公司 Dispositif et procédé de communication sans fil et support de stockage
US11716132B2 (en) 2020-09-11 2023-08-01 Asustek Computer Inc. Method and apparatus for beam failure detection regarding multiple transmission/reception points in a wireless communication system

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2921024A1 (fr) * 2012-11-13 2015-09-23 Telefonaktiebolaget L M Ericsson (publ) Procédé pour modifier des valeurs de paramètres pour extension longue portée et noeud correspondant

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2921024A1 (fr) * 2012-11-13 2015-09-23 Telefonaktiebolaget L M Ericsson (publ) Procédé pour modifier des valeurs de paramètres pour extension longue portée et noeud correspondant

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
HUAWEI ET AL: "Initial RLM consideration for NR", vol. RAN WG4, no. Spokane, USA; 20170403 - 20170407, 3 April 2017 (2017-04-03), XP051246833, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/Meetings_3GPP_SYNC/RAN4/Docs/> [retrieved on 20170403] *
NOKIA ET AL: "Beam Recovery in NR", vol. RAN WG1, no. Spokane, WA, USA; 20170403 - 20170407, 2 April 2017 (2017-04-02), XP051244070, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/Meetings_3GPP_SYNC/RAN1/Docs/> [retrieved on 20170402] *
QUALCOMM INCORPORATED: "Considerations of RLM and RLF in NR", vol. RAN WG2, no. Spokane, USA; 20170403 - 20170407, 3 April 2017 (2017-04-03), XP051245402, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/Meetings_3GPP_SYNC/RAN2/Docs/> [retrieved on 20170403] *

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020097813A1 (fr) * 2018-11-14 2020-05-22 华为技术有限公司 Procédé, appareil, et système de mesure de mobilité
CN111713131A (zh) * 2018-11-14 2020-09-25 华为技术有限公司 一种移动性测量的方法、装置和系统
US11716132B2 (en) 2020-09-11 2023-08-01 Asustek Computer Inc. Method and apparatus for beam failure detection regarding multiple transmission/reception points in a wireless communication system
WO2023011285A1 (fr) * 2021-08-02 2023-02-09 索尼集团公司 Dispositif et procédé de communication sans fil et support de stockage

Similar Documents

Publication Publication Date Title
CN110366827B (zh) 用于周期性波束故障测量的系统和方法
US20220279341A1 (en) Radio resource control procedures for machine learning
US10966271B2 (en) Connection setup recovery for wireless networks
EP3721658A1 (fr) Surveillance de liens avec auto-raccordement pour réseaux sans fil
US20180049080A1 (en) Network controlled sharing of measurement gaps for intra and inter frequency measurements for wireless networks
US10979159B2 (en) Radio link monitoring test procedures for wireless devices
US20210345211A1 (en) Timing advance for rach-less backhaul handover
WO2021254590A1 (fr) Commande de relâchement de mesures de surveillance de liaison radioélectrique
CN114008935B (zh) 触发针对侧行链路通信的资源分配配置切换
EP3751900A1 (fr) Sélection d&#39;une cellule cible pour un transfert sur la base d&#39;une mesure de réponse d&#39;impulsion de canal
US20230247672A1 (en) Random access report in mixed network types
US11895542B2 (en) Reducing handover interruption with two transmitters and receivers
US20230403591A1 (en) Group based beam reporting
WO2018202310A1 (fr) Surveillance de liaison radio pour communications multifaisceaux
WO2021063487A1 (fr) Détection améliorée de défaillance de liaison radio pour réseaux sans fil
EP3949564A1 (fr) Procédé de correction de temps de départ dans une différence observée de temps de positionnement d&#39;arrivée
WO2018077416A1 (fr) Transmission proactive d&#39;informations de système pour réduire le temps d&#39;interruption après une défaillance de liaison radio pour des réseaux sans fil
US20220232440A1 (en) Configuration of carriers for non-mobility related purposes
US20230239752A1 (en) Logging information related to multiple-event conditional handover execution for wireless networks
US11743830B2 (en) Panel activation at a user equipment
EP4190013A2 (fr) Ajustements de synchronisation de rapport de mesure
WO2018224545A1 (fr) Utilisation de mesures de transfert pour des réseaux sans fil sur la base d&#39;une condition de blocage de signal
US20230199590A1 (en) Variable time-to-trigger value for transmission of measurement report for wireless networks
US20230088234A1 (en) Data collection enhancements for multicast broadcast services
WO2022204706A1 (fr) Techniques de production de rapports de mesures pour des communications avec formation de faisceaux

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 17721672

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 17721672

Country of ref document: EP

Kind code of ref document: A1