EP4315627A1 - Anzeige von strahlfehlern beim betrieb mit mehreren sendeempfangspunkten - Google Patents

Anzeige von strahlfehlern beim betrieb mit mehreren sendeempfangspunkten

Info

Publication number
EP4315627A1
EP4315627A1 EP22714384.9A EP22714384A EP4315627A1 EP 4315627 A1 EP4315627 A1 EP 4315627A1 EP 22714384 A EP22714384 A EP 22714384A EP 4315627 A1 EP4315627 A1 EP 4315627A1
Authority
EP
European Patent Office
Prior art keywords
beam failure
bfd
value
mac
indication data
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
EP22714384.9A
Other languages
English (en)
French (fr)
Inventor
Timo Koskela
Samuli Heikki TURTINEN
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.)
Nokia Technologies Oy
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
Publication of EP4315627A1 publication Critical patent/EP4315627A1/de
Pending legal-status Critical Current

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W24/00Supervisory, monitoring or testing arrangements
    • H04W24/08Testing, supervising or monitoring using real traffic
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04BTRANSMISSION
    • H04B7/00Radio transmission systems, i.e. using radiation field
    • H04B7/02Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas
    • H04B7/04Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas
    • H04B7/06Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas at the transmitting station
    • H04B7/0686Hybrid systems, i.e. switching and simultaneous transmission
    • H04B7/0695Hybrid systems, i.e. switching and simultaneous transmission using beam selection
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04BTRANSMISSION
    • H04B7/00Radio transmission systems, i.e. using radiation field
    • H04B7/02Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas
    • H04B7/022Site diversity; Macro-diversity
    • H04B7/024Co-operative use of antennas of several sites, e.g. in co-ordinated multipoint or co-operative multiple-input multiple-output [MIMO] systems
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04BTRANSMISSION
    • H04B7/00Radio transmission systems, i.e. using radiation field
    • H04B7/02Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas
    • H04B7/04Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas
    • H04B7/06Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas at the transmitting station
    • H04B7/0686Hybrid systems, i.e. switching and simultaneous transmission
    • H04B7/0695Hybrid systems, i.e. switching and simultaneous transmission using beam selection
    • H04B7/06952Selecting one or more beams from a plurality of beams, e.g. beam training, management or sweeping
    • H04B7/06964Re-selection of one or more beams after beam failure
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00Arrangements affording multiple use of the transmission path
    • H04L5/003Arrangements for allocating sub-channels of the transmission path
    • H04L5/0048Allocation of pilot signals, i.e. of signals known to the receiver
    • H04L5/0051Allocation of pilot signals, i.e. of signals known to the receiver of dedicated pilots, i.e. pilots destined for a single user or terminal
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W24/00Supervisory, monitoring or testing arrangements
    • H04W24/10Scheduling measurement reports ; Arrangements for measurement reports
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W76/00Connection management
    • H04W76/10Connection setup
    • H04W76/15Setup of multiple wireless link connections
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04BTRANSMISSION
    • H04B17/00Monitoring; Testing
    • H04B17/0082Monitoring; Testing using service channels; using auxiliary channels
    • H04B17/0087Monitoring; Testing using service channels; using auxiliary channels using auxiliary channels or channel simulators
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00Arrangements affording multiple use of the transmission path
    • H04L5/003Arrangements for allocating sub-channels of the transmission path
    • H04L5/0048Allocation of pilot signals, i.e. of signals known to the receiver
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00Arrangements affording multiple use of the transmission path
    • H04L5/003Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053Allocation of signaling, i.e. of overhead other than pilot signals

Definitions

  • the following exemplary embodiments relate to wireless communication.
  • Some wireless communication networks are capable of utilizing multiple transmission reception point operation. It is desirable to provide solutions that enhance the overall effectiveness of such capabilities. For example, it may be beneficial to provide solutions that relate to beam failure recovery in multiple transmission reception point operation.
  • an apparatus comprising at least one processor, and at least one memory including computer program code, wherein the at least one memory and the computer program code are configured, with the at least one processor, to cause the apparatus to: detect a beam failure on at least one transmission reception point of a plurality of transmission reception points, the apparatus being configured to communicate with the plurality of transmission reception points; include one or more beam failure indication data into a first medium access control (MAC) control element (CE), wherein the one or more beam failure indication data indicates the beam failure detected on the at least one transmission reception point; wherein the one or more beam failure indication data comprises at least a first bit that comprises a first value and a second value, wherein the first value of the first bit indicates a first transmission reception point at least on which the beam failure is detected; and transmit, to an access point, the first MAC CE comprising the one or more beam failure indication data.
  • MAC medium access control
  • CE medium access control element
  • the second value of the first bit indicates that no beam failure is detected at least on the first transmission reception point.
  • the second value of the first bit indicates a second transmission reception point on which the beam failure is detected.
  • the one or more beam failure indication data further comprises at least a first set of candidate beam information associated with the first transmission reception point and/or a second set of candidate beam information associated with the second transmission reception point.
  • the first set of candidate beam information is included into the first MAC CE before including the second set of candidate beam information into the first MAC CE.
  • the first bit is set to the first value
  • the one or more beam failure indication data further comprises at least a second bit indicating whether the beam failure is detected on the second transmission reception point.
  • the one or more beam failure indication data further indicates whether the beam failure is for a transmission reception point level beam failure or for a cell-level beam failure.
  • the transmission reception point level beam failure or the cell-level beam failure is indicated by a bitmap within the one or more beam failure indication data, wherein a length of the bitmap is determined based at least partly on a number of serving cells for which the beam failure is detected.
  • the apparatus is further caused to: transmit, to the access point, a second medium access control (MAC) control element (CE) indicating a cell-level beam failure.
  • MAC medium access control
  • CE control element
  • an apparatus comprising means for: detecting a beam failure on at least one transmission reception point of a plurality of transmission reception points, the apparatus being configured to communicate with the plurality of transmission reception points; including one or more beam failure indication data into a first medium access control (MAC) control element (CE), wherein the one or more beam failure indication data indicates the beam failure detected on the at least one transmission reception point; wherein the one or more beam failure indication data comprises at least a first bit that comprises a first value and a second value, wherein the first value of the first bit indicates a first transmission reception point at least on which the beam failure is detected; and transmitting, to an access point, the first MAC CE comprising the one or more beam failure indication data.
  • MAC medium access control
  • CE medium access control element
  • a method comprising: detecting, by a terminal device, a beam failure on at least one transmission reception point of a plurality of transmission reception points, the terminal device being configured to communicate with the plurality of transmission reception points; including, by the terminal device, one or more beam failure indication data into a first medium access control (MAC) control element (CE), wherein the one or more beam failure indication data indicates the beam failure detected on the at least one transmission reception point; wherein the one or more beam failure indication data comprises at least a first bit that comprises a first value and a second value, wherein the first value of the first bit indicates a first transmission reception point at least on which the beam failure is detected; and transmitting, by the terminal device, to an access point, the first MAC CE comprising the one or more beam failure indication data.
  • MAC medium access control
  • a computer program comprising instructions for causing an apparatus to perform at least the following: detect a beam failure on at least one transmission reception point of a plurality of transmission reception points, the apparatus being configured to communicate with the plurality of transmission reception points; include one or more beam failure indication data into a first medium access control (MAC) control element (CE), wherein the one or more beam failure indication data indicates the beam failure detected on the at least one transmission reception point; wherein the one or more beam failure indication data comprises at least a first bit that comprises a first value and a second value, wherein the first value of the first bit indicates a first transmission reception point at least on which the beam failure is detected; and transmit, to an access point, the first MAC CE comprising one or more beam failure indication data.
  • MAC medium access control
  • CE medium access control element
  • a computer readable medium comprising program instructions for causing an apparatus to perform at least the following: detect a beam failure on at least one transmission reception point of a plurality of transmission reception points, the apparatus being configured to communicate with the plurality of transmission reception points; include one or more beam failure indication data into a first medium access control (MAC) control element (CE), wherein the one or more beam failure indication data indicates the beam failure detected on the at least one transmission reception point; wherein the one or more beam failure indication data comprises at least a first bit that comprises a first value and a second value, wherein the first value of the first bit indicates a first transmission reception point at least on which the beam failure is detected; and transmit, to an access point, the first MAC CE comprising the one or more beam failure indication data.
  • MAC medium access control
  • CE medium access control element
  • a non-transitory computer readable medium comprising program instructions for causing an apparatus to perform at least the following: detect a beam failure on at least one transmission reception point of a plurality of transmission reception points, the apparatus being configured to communicate with the plurality of transmission reception points; include one or more beam failure indication data into a first medium access control (MAC) control element (CE), wherein the one or more beam failure indication data indicates the beam failure detected on the at least one transmission reception point; wherein the one or more beam failure indication data comprises at least a first bit that comprises a first value and a second value, wherein the first value of the first bit indicates a first transmission reception point at least on which the beam failure is detected; and transmit, to an access point, the first MAC CE comprising the one or more beam failure indication data.
  • MAC medium access control
  • CE medium access control element
  • an apparatus comprising at least one processor, and at least one memory including computer program code, wherein the at least one memory and the computer program code are configured, with the at least one processor, to cause the apparatus to: receive, from a terminal device, a medium access control (MAC) control element (CE) comprising at least a first bit comprising a first value and a second value, wherein the first value of the first bit indicates a beam failure on at least a first transmission reception point.
  • MAC medium access control
  • CE control element
  • an apparatus comprising means for receiving, from a terminal device, a medium access control (MAC) control element (CE) comprising at least a first bit comprising a first value and a second value, wherein the first value of the first bit indicates a beam failure on at least a first transmission reception point.
  • MAC medium access control
  • CE control element
  • a method comprising receiving, from a terminal device, a medium access control (MAC) control element (CE) comprising at least a first bit comprising a first value and a second value, wherein the first value of the first bit indicates a beam failure on at least a first transmission reception point.
  • MAC medium access control
  • CE control element
  • a computer program comprising instructions for causing an apparatus to perform at least the following: receive, from a terminal device, a medium access control (MAC) control element (CE) comprising at least a first bit comprising a first value and a second value, wherein the first value of the first bit indicates a beam failure on at least a first transmission reception point.
  • MAC medium access control
  • CE control element
  • a computer readable medium comprising program instructions for causing an apparatus to perform at least the following: receive, from a terminal device, a medium access control (MAC) control element (CE) comprising at least a first bit comprising a first value and a second value, wherein the first value of the first bit indicates a beam failure on at least a first transmission reception point.
  • MAC medium access control
  • CE control element
  • a non-transitory computer readable medium comprising program instructions for causing an apparatus to perform at least the following: receive, from a terminal device, a medium access control (MAC) control element (CE) comprising at least a first bit comprising a first value and a second value, wherein the first value of the first bit indicates a beam failure on at least a first transmission reception point.
  • MAC medium access control
  • CE control element
  • a system comprising at least a terminal device and an access point.
  • the terminal device is configured to: detect a beam failure on at least one transmission reception point of a plurality of transmission reception points, the terminal device being configured to communicate with the plurality of transmission reception points; include one or more beam failure indication data into a first medium access control (MAC) control element (CE), wherein the one or more beam failure indication data indicates the beam failure detected on the at least one transmission reception point; wherein the one or more beam failure indication data comprises at least a first bit that comprises a first value and a second value, wherein the first value of the first bit indicates a first transmission reception point at least on which the beam failure is detected; and transmit, to the access point, the first MAC CE comprising the one or more beam failure indication data.
  • the access point is configured to: receive, from the terminal device, the MAC CE comprising the one or more beam failure indication data.
  • a system comprising at least a terminal device and an access point.
  • the terminal device comprises means for: detecting a beam failure on at least one transmission reception point of a plurality of transmission reception points, the terminal device being configured to communicate with the plurality of transmission reception points; including one or more beam failure indication data into a first medium access control (MAC) control element (CE), wherein the one or more beam failure indication data indicates the beam failure detected on the at least one transmission reception point; wherein the one or more beam failure indication data comprises at least a first bit that comprises a first value and a second value, wherein the first value of the first bit indicates a first transmission reception point at least on which the beam failure is detected; and transmitting, to the access point, the first MAC CE comprising the one or more beam failure indication data.
  • the access point comprises means for: receiving, from the terminal device, the MAC CE comprising the one or more beam failure indication data.
  • FIGS. 1A and IB illustrate an exemplary embodiment of a cellular communication network
  • FIG. 2 illustrates a beam failure recovery medium access control control element with a single octet bitmap
  • FIG. 3 illustrates a signaling diagram according to another exemplary embodiment
  • FIGS. 4 and 5 illustrate medium access control control elements according to some exemplary embodiments
  • FIGS. 6-9 illustrate flow charts according to some exemplary embodiments
  • FIGS. 10-11 illustrate apparatuses according to some exemplary embodiments.
  • exemplary embodiments will be described using, as an example of an access architecture to which the exemplary embodiments may be applied, a radio access architecture based on long term evolution advanced (LTE Advanced, LTE-A) or new radio (NR, 5G), without restricting the exemplary embodiments to such an architecture, however. It is obvious for a person skilled in the art that the exemplary embodiments may also be applied to other kinds of communications networks having suitable means by adjusting parameters and procedures appropriately.
  • LTE Advanced long term evolution advanced
  • NR new radio
  • UMTS universal mobile telecommunications system
  • UTRAN radio access network
  • LTE long term evolution
  • Wi-Fi wireless local area network
  • WiMAX wireless local area network
  • Bluetooth® personal communications services
  • PCS personal communications services
  • WCDMA wideband code division multiple access
  • UWB ultra-wideband
  • sensor networks mobile ad-hoc networks
  • IMS Internet Protocol multimedia subsystems
  • FIG. 1A depicts examples of simplified system architectures showing some elements and functional entities, all being logical units, whose implementation may differ from what is shown.
  • the connections shown in FIG. 1A are logical connections; the actual physical connections may be different. It is apparent to a person skilled in the art that the system may also comprise other functions and structures than those shown in FIG. 1A.
  • FIG. 1A shows a part of an exemplifying radio access network.
  • FIG. 1A shows user devices 100 and 102 configured to be in a wireless connection on one or more communication channels in a cell with an access node (such as (e/g)NodeB) 104 providing the cell.
  • the physical link from a user device to a (e/g)NodeB may be called uplink or reverse link and the physical link from the (e/g)NodeB to the user device may be called downlink or forward link.
  • (e/g)NodeBs or their functionalities may be implemented by using any node, host, server or access point etc. entity suitable for such a usage.
  • a communication system may comprise more than one (e/g)NodeB, in which case the (e/g)NodeBs may also be configured to communicate with one another over links, wired or wireless, designed for the purpose. These links may be used for signaling purposes.
  • the (e/g) NodeB may be a computing device configured to control the radio resources of communication system it is coupled to.
  • the NodeB may also be referred to as a base station, an access point or any other type of interfacing device including a relay station capable of operating in a wireless environment.
  • the (e/g)NodeB may include or be coupled to transceivers. From the transceivers of the (e/g)NodeB, a connection may be provided to an antenna unit that establishes bi-directional radio links to user devices.
  • the antenna unit may comprise a plurality of antennas or antenna elements.
  • the (e/g) NodeB may further be connected to core network 110 (CN or next generation core NGC).
  • core network 110 CN or next generation core NGC.
  • the counterpart on the CN side may be a serving gateway (S-GW, routing and forwarding user data packets), packet data network gateway (P-GW), for providing connectivity of user devices (UEs) to external packet data networks, or mobile management entity (MME), etc.
  • S-GW serving gateway
  • P-GW packet data network gateway
  • MME mobile management entity
  • the user device also called UE, user equipment, user terminal, terminal device, etc.
  • UE user equipment
  • user terminal terminal device
  • any feature described herein with a user device may be implemented with a corresponding apparatus, such as a relay node.
  • a relay node may be a layer 3 relay (self- backhauling relay) towards the base station.
  • the 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 (mobile phone), smartphone, personal digital assistant (PDA), handset, device using a wireless modem (alarm or measurement device, etc.), laptop and/or touch screen computer, tablet, game console, notebook, and multimedia device.
  • SIM subscriber identification module
  • a user device may also be a nearly exclusive uplink only device, of which an example may be a camera or video camera loading images or video clips to a network.
  • a user device may also be a device having capability to operate in Internet of Things (loT) network which is a scenario in which objects may be provided with the ability to transfer data over a network without requiring human-to-human or human-to-computer interaction.
  • the user device may also utilize cloud.
  • a user device may comprise a small portable device with radio parts (such as a watch, earphones or eyeglasses) and the computation may be carried out in the cloud.
  • the user device (or in some exemplary embodiments a layer 3 relay node) may be configured to perform one or more of user equipment functionalities.
  • the user device may also be called a subscriber unit, mobile station, remote terminal, access terminal, user terminal, terminal device, or user equipment (UE) just to mention but a few names or apparatuses.
  • CPS cyber physical system
  • 1CT devices sensors, actuators, processors microcontrollers, etc.
  • Mobile cyber physical systems in which the physical system in question may have inherent mobility, are a subcategoiy of cyber-physical systems. Examples of mobile physical systems include mobile robotics and electronics transported by humans or animals.
  • apparatuses have been depicted as single entities, different units, processors and/or memory units (not all shown in FIG. 1A) may be implemented.
  • 5G may enable using multiple input - multiple output (M1MO) antennas, many more base stations or nodes than the LTE (a so-called small cell concept), including macro sites operating in co-operation with smaller stations and employing a variety of radio technologies depending on service needs, use cases and/or spectrum available.
  • 5G mobile communications may support a wide range of use cases and related applications including video streaming, augmented reality, different ways of data sharing and various forms of machine type applications (such as (massive) machine-type communications (mMTC), including vehicular safety, different sensors and real-time control.
  • 5G may be expected to have multiple radio interfaces, namely below 6GHz, cmWave and mmWave, and also being integrable with existing legacy radio access technologies, such as the LTE.
  • Integration with the LTE may be implemented, at least in the early phase, as a system, where macro coverage may be provided by the LTE, and 5G radio interface access may come from small cells by aggregation to the LTE.
  • 5G may support both inter-RAT operability (such as LTE-5G) and inter-RI operability (inter-radio interface operability, such as below 6GHz - cmWave, below 6GHz - cmWave - mmWave).
  • inter-RAT operability such as LTE-5G
  • inter-RI operability inter-radio interface operability, such as below 6GHz - cmWave, below 6GHz - cmWave - mmWave.
  • One of the concepts considered to be used in 5G networks may be network slicing in which multiple independent and dedicated virtual sub networks (network instances) may be created within the substantially same infrastructure to run services that have different requirements on latency, reliability, throughput and mobility.
  • the current architecture in LTE networks may be fully distributed in the radio and fully centralized in the core network.
  • the low latency applications and services in 5G may need to bring the content close to the radio which leads to local break out and multi-access edge computing (MEC).
  • 5G may enable analytics and knowledge generation to occur at the source of the data. This approach may need leveraging resources that may not be continuously connected to a network such as laptops, smartphones, tablets and sensors.
  • MEC may provide a distributed computing environment for application and service hosting. It may also have the ability to store and process content in close proximity to cellular subscribers for faster response time.
  • Edge computing may cover a wide range of technologies such as wireless sensor networks, mobile data acquisition, mobile signature analysis, cooperative distributed peer-to-peer ad hoc networking and processing also classifiable as local cloud/fog computing and grid/mesh computing, dew computing, mobile edge computing, cloudlet, distributed data storage and retrieval, autonomic self-healing networks, remote cloud services, augmented and virtual reality, data caching, Internet of Things (massive connectivity and/or latency critical), critical communications (autonomous vehicles, traffic safety, real time analytics, time-critical control, healthcare applications).
  • the communication system may also be able to communicate with other networks, such as a public switched telephone network or the Internet 112, or utilize services provided by them.
  • the communication network may also be able to support the usage of cloud services, for example at least part of core network operations may be carried out as a cloud service (this is depicted in FIG. 1A by “cloud” 114).
  • the communication system may also comprise a central control entity, or a like, providing facilities for networks of different operators to cooperate for example in spectrum sharing.
  • Edge cloud may be brought into radio access network (RAN) by utilizing network function virtualization (NFV) and software defined networking (SDN).
  • RAN radio access network
  • NFV network function virtualization
  • SDN software defined networking
  • Using edge cloud may mean access node operations to be carried out, at least partly, in a server, host or node operationally coupled to a remote radio head or a radio unit (RU), or a base station comprising radio parts. It may also be possible that node operations will be distributed among a plurality of servers, nodes or hosts.
  • Carrying out the RAN real-time functions at the RAN side (in a distributed unit, DU 104) and non-real time functions in a centralized manner (in a centralized unit, CU 108) may be enabled for example by application of cloudRAN architecture.
  • 5G (or new radio, NR) networks may be designed to support multiple hierarchies, where MEC servers may be placed between the core and the base station or nodeB (gNB). It should be appreciated that MEC may be applied in 4G networks as well.
  • 5G may also utilize satellite communication to enhance or complement the coverage of 5G service, for example by providing backhauling.
  • Possible use cases may be providing service continuity for machine-to-machine (M2M) or Internet of Things (IoT) devices or for passengers on board of vehicles, or ensuring service availability for critical communications, and future railway/maritime/aeronautical communications.
  • Satellite communication may utilize geostationary earth orbit (GEO) satellite systems, but also low earth orbit (LEO) satellite systems, in particular mega-constellations (systems in which hundreds of (nano)satellites are deployed).
  • GEO geostationary earth orbit
  • LEO low earth orbit
  • At least one satellite 106 in the mega- constellation may cover several satellite-enabled network entities that create on ground cells.
  • the on-ground cells maybe created through an on-ground relay node 104 or by a gNB located on-ground or in a satellite.
  • the depicted system is only an example of a part of a radio access system and in practice, the system may comprise a plurality of (e/g)NodeBs, the user device may have an access to a plurality of radio cells and the system may also comprise other apparatuses, such as physical layer relay nodes or other network elements, etc. At least one of the (e/g)NodeBs or may be a Home(e/g)nodeB.
  • the (e/g)nodeB or base station may also be split into: a radio unit (RU) comprising a radio transceiver (TRX), i.e. a transmitter (TX) and a receiver (RX); a distributed unit (DU) that may be used for the so-called Layer 1 (LI) processing and real-time Layer 2 (L2) processing; and a centralized unit (CU) or a central unit that may be used for non-real-time L2 and Layer 3 (L3) processing.
  • TRX radio transceiver
  • DU distributed unit
  • L2 real-time Layer 2
  • CU centralized unit
  • L3 Layer 3
  • the CU and DU together may also be referred to as baseband or a baseband unit (BBU).
  • the RU and DU may also be comprised into a radio access point (RAP).
  • Cloud computing platforms may also be used to run the CU or DU.
  • the CU may run in a cloud computing platform (vCU, virtualized CU).
  • vCU virtualized CU
  • vDU virtualized DU
  • there may also be a combination, where the DU may use so-called bare metal solutions, for example application-specific integrated circuit (ASIC) or customer-specific standard product (CSSP) system-on-a-chip (SoC) solutions.
  • ASIC application-specific integrated circuit
  • CSSP customer-specific standard product
  • SoC system-on-a-chip
  • Radio cells may be macro cells (or umbrella cells) which may be large cells having a diameter of up to tens of kilometers, or smaller cells such as micro-, femto- orpicocells.
  • the (e/g)NodeBs of FIG. 1A may provide any kind of these cells.
  • a cellular radio system may be implemented as a multilayer network including several kinds of cells. In multilayer networks, one access node may provide one kind of a cell or cells, and thus a plurality of (e/g)NodeBs may be needed to provide such a network structure.
  • a network which may be able to use “plug-and-play” (e/g)Node Bs may include, in addition to Home (e/g)NodeBs (H(e/g)nodeBs), a home node B gateway, or HNB-GW (not shown in FIG. 1A).
  • HNB-GW HNB Gateway
  • HNB-GW which may be installed within an operator’s network, may aggregate traffic from a large number of HNBs back to a core network.
  • CFRA BFR beam failure recovery
  • CFRA BFR dedicated random access (RA) preamble resources that may correspond to a specific downlink (DL) reference signal (RS), i.e. a new candidate beam.
  • RS downlink reference signal
  • the UE may perform beam failure detection for one or more SCells that has been configured for the beam failure detection. This may be similar to primary cell (PCell) failure detection, wherein for a given SCell configured for the failure detection, the UE determines the respective set of beam failure detection resources, such as a set of qO and/or a beam failure detection reference signal (BFD-RS), in an implicit or explicit manner.
  • the UE may determine the BFD-RS based on the reference signal indicated by the active transmission configuration indicator (TCI) states for the physical downlink control channel (PDCCH).
  • TCI active transmission configuration indicator
  • PDCCH physical downlink control channel
  • the UE may perform beam failure detection according to the reference signal configured by the network.
  • the physical layer i.e.
  • LI determines, based on the downlink reference signal, such as synchronization signal block (SSB) or SS/PBCH (synchronization signal / physical broadcast channel) block or channel state information reference signal (CS1-RS), in a set of qO whether or not to indicate a beam failure instance (BF1) to the higher layer, i.e. the medium access control (MAC) layer, which may also be referred to as L2.
  • SSB synchronization signal block
  • PBCH synchronization signal / physical broadcast channel
  • CS1-RS channel state information reference signal
  • the MAC layer counts, in a BF1 counter, the BF1 indications for a given cell, and when it counts the configured number of BF1 instances indicated by the lower layer for the respective cell (PCell or SCell), it initiates, or triggers, the beam failure recovery.
  • the counter for BF1 indications is supervised by a beam failure detection (BFD) timer. When the UE receives a new BF1 indication, the BFD timer is started and the counter is incremented. If the BFD timer expires, the counter is reset.
  • BFD beam failure detection
  • the UE may indicate the failure and recover the failed cell by transmitting a MAC control element (MAC CE), which may also be referred to as a BFR MAC CE.
  • MAC CE MAC control element
  • BFR MAC CE may refer to BFR MAC CE, or to truncated BFR MAC CE, or a MAC CE used for beam failure recovery.
  • FIG. 2 illustrates an example of a BFR and truncated BFR MAC CE with a single octet bitmap.
  • FIG. 2 is used as an example to describe some of the features and the data structure of a BFR MAC CE that may be utilized in the context of some exemplary embodiments.
  • the BFR MAC CE indicates, to the network, the failed SCell index (C1-C7 bits illustrated in FIG. 2), an indication (AC bit illustrated in FIG. 2) on whether a candidate beam is available, and the index of the candidate beam (candidate RS ID in FIG. 2, if any) in the candidate beam RS list.
  • the candidate beam RS list is a list of candidate beam indices that may be SSB and/or CS1-RS indices. A candidate beam may be determined to be available, if, for example, the quality and/or received signal strength of the candidate beam exceeds a threshold level.
  • the MAC CE that indicates SCell failure and/or recovery information may also be used for PCell recovery by setting the PCell bit (SP bit illustrated in FIG. 2) to indicate the failure.
  • the transmission of the MAC CE may be preceded by a transmission of a dedicated RS signal that may indicate the beam failure event on the SCell.
  • the UE may multiplex the BFR MAC CE in any available uplink (UL) grant.
  • an SpCell may refer to a primary cell of a master cell group or to a primary secondary cell of a secondary cell group. It is further noted that a primary cell (PCell) may refer to a SpCell of a master cell group, and a primary secondary cell (PSCell) may refer to a SpCell of a secondary cell group.
  • PCell primary cell
  • PSCell primary secondary cell
  • BFR MAC CEs may be identified by a MAC subheader with a logical channel identifier (LCID / eLCID).
  • a BFR MAC CE may have a variable size. It may comprise a bitmap in ascending order based on the ServCelllndex and beam failure recovery information, i.e. octets containing candidate beam availability indication (AC bit) for SCells indicated in the bitmap.
  • a single octet bitmap may be used when the highest ServCelllndex of this MAC entity's SCell, for which beam failure is detected, is less than 8. Otherwise, four octets may be used.
  • a single octet bitmap (for example as illustrated in FIG. 2) may be used for example for the following cases:
  • the highest ServCelllndex of this MAC entity's SCell configured with beam failure detection is less than 8;
  • the fields in the BFR MAC CEs may be defined as follows with reference to FIG. 2: - SP: This field may indicate beam failure detection for the SpCell of this MAC entity.
  • the SP field maybe set to 1 to indicate that beam failure is detected for SpCell when BFR MAC CE or truncated BFR MAC CE is to be included into a MAC protocol data unit (PDU) as part of a random access procedure. Otherwise, it is set to 0.
  • PDU MAC protocol data unit
  • This field may indicate beam failure detection and the presence of an octet containing the AC field for the SCell with ServCelllndex i.
  • the Ci field set to 1 indicates that beam failure is detected and the octet containing the AC field is present for the SCell with ServCelllndex i.
  • the Ci field set to 0 indicates that the beam failure is not detected and an octet containing the AC field is not present for the SCell with ServCelllndex i.
  • the octets containing the AC field are present in ascending order based on the ServCelllndex.
  • This field indicates beam failure detection for the SCell with ServCelllndex i.
  • the Ci field set to 1 indicates that beam failure is detected and the octet containing the AC field for the SCell with ServCelllndex i may be present.
  • the Ci field set to 0 indicates that the beam failure is not detected and the octet containing the AC field is not present for the SCell with ServCelllndex i.
  • the octets containing the AC field if present, are included in ascending order based on the ServCelllndex. The number of octets containing the AC field included is maximized, while not exceeding the available grant size.
  • This field may indicate the presence of the Candidate RS ID field in this octet. If at least one of the SSBs with synchronization signal reference signal received power (SS-RSRP) above rsrp-ThresholdBFR amongst the SSBs in candidateBeamRSSCellList, or the CSl-RSs with CS1-RSRP above rsrp-ThresholdBFR amongst the CSl-RSs in candidateBeamRSSCellList is available, the AC field is set to 1; otherwise, it is set to 0. If the AC field is set to 1, the Candidate RS ID field is present. If the AC field set to 0, R bits are present instead.
  • SS-RSRP synchronization signal reference signal received power
  • This field is set to the index of an SSB with SS-RSRP above rsrp-ThresholdBFR amongst the SSBs in candidateBeamRSSCellList, or to the index of a CS1-RS with CS1-RSRP above rsrp-ThresholdBFR amongst the CSl-RSs in candidateBeamRSSCellList.
  • the length of this field is 6 bits.
  • the network may further support utilizing multiple transmission reception points (TRPs). This may be referred to as multiple transmission reception point (mTRP) operation.
  • TRPs transmission reception points
  • mTRP operation may support, for example, two or more TRPs.
  • the UE 100, 102 may receive data via a plurality of TRPs.
  • the different TRPs may be controlled, for example, by the access point 104, such as a gNB.
  • FIG. IB An example of such a system is illustrated in FIG. IB, which may be understood to depict the system of FIG. 1A, but with greater accuracy with respect to the mTRP scenario.
  • the mTRP operation may be implemented in such a manner that, instead of explicitly indicating the TRP identifier (ID), the control resource sets (CORESETs) may be associated to specific TRPs using a CORESETPoollndex parameter [0..1].
  • CORESETs within a PDCCH configuration that have the same poollndex may be assumed by the UE to be configured to be provided from the same (set of) TRP(s). Referring to FIG. IB, two TRPs with CORESETPoollndex 0 and 1 are shown. TRP0, i.e.
  • TRP0 and/or TRP1 may comprise one or more TRPs.
  • mTRP may also be configured for an inter-cell scenario (sometimes referred to as inter-cell mTRP), i.e. the TRPs may be associated with different cells.
  • the UE may be provided a configuration where the CORESETs of CORESETPoollndex/TRP are provided by multiple cells (for example two).
  • the UE may be explicitly configured with CORESETs with more than one (for example two) distinct CORESETPoollndex values that CORESETs, or the CORESETpoollndex is associated with another cell than the current serving cell, for example associating a CORESET/Poolindex with a physical cell identity (PCI).
  • PCI physical cell identity
  • the UE may determine that it is configured with inter-cell mTRP communication, when the downlink reference signal indicated by an activated TCI state for PDCCH or physical downlink shared channel (PDSCH) for a CORESET is associated, or the quasi co-location (QCL) source of the signal is associated with a PCI other than the current serving cell.
  • PDSCH physical downlink shared channel
  • QCL quasi co-location
  • mTRP operation may refer to single downlink control information (S-DCI) or multiple downlink control information (mDCl) operation.
  • S-DCI single downlink control information
  • mDCl multiple downlink control information
  • the CORESETPoollndex value may be used to group CORESETs under separate groups. In other words, when CORESETs share the same group ID or CORESETPoolindex value, they may be considered to be in the same group.
  • S- DC1 operation the different CORESETs are not grouped, i.e. the same CORESETpoolindex value is configured for all the CORESETs.
  • the UE When configured with more than one value of CORESETpoolindex (for example two sets of CORESETs are configured in mDCl operation), the UE may be expected to monitor downlink control information (DC1) transmissions simultaneously from CORESETs associated with different pool index values.
  • DC1 downlink control information
  • the UE 100 may determine that it has experienced a failure on a subset of beams or a failure of a TRP or a failure of BFD-RS set. This may be referred to as partial beam failure or TRP failure.
  • all beams i.e. all the BFD-RSs or all the reference signals in the failure detection set, i.e. in all the sets of qO
  • this may be referred to as full failure or full beam failure or cell-level beam failure.
  • a TRP 1 when referring herein that a TRP 1 has failed, it may refer to the failure of RSs in the BFD-RS set associated with the TRP1.
  • a TRPO when referring herein that a TRPO has failed, it may refer to the failure of RSs in the BFD-RS set associated with the TRPO.
  • the TRP1 failure may refer to the failure of the BFD-RS set associated with the CORESETs under specific CORESETPoollndex value(s) (for example 1).
  • the TRPO failure may refer to the failure of the BFD-RS set associated with the CORESETs under specific CORESETpoollndex value(s) (for example 0).
  • Some exemplary embodiments may be used to provide beam failure detection for mTRP operation by indicating TRP failure with or without a candidate beam, when the UE is configured to indicate cell-level failure, i.e. full failure, or when the UE is configured to indicate failure per TRP.
  • Some exemplary embodiments may utilize signaling techniques, such as MAC CE encoding techniques or rules for various mTRP recovery schemes including, but not limited to: signaling support to indicate failure of all TRPs, signaling support to indicate failure of at least one TRP, and/or signaling support to indicate failure in the cell (failure on all TRPs may be interpreted by the UE as a failure of an entire cell).
  • TRP may refer to the BFD-RS set associated with one or more specific TRPs
  • TRP-specific failure may refer to the failure of a specific qO set.
  • two TRPs i.e. two BFD-RS sets of qO, may be used as an example.
  • some exemplary embodiments may also be applied to more than two TRPs.
  • FIG. 3 illustrates a signaling diagram according to an exemplary embodiment.
  • An access point such as a gNB configures 301 a UE for mTRP beam failure detection.
  • the UE may be configured to detect one or more TRP-specific beam failures and to indicate the one or more TRP-specific beam failures to the base station.
  • the UE may include 303 the beam failure indication data into at least a part of the MAC CE fields for example with the following logic, which may be configured to the UE by the access point in the configuration 301.
  • the UE may include the indication of the beam failure detected on TRPO first by setting a first TRP failure information field indicating the beam failure of TRPO.
  • the indication may be followed by the candidate beam information of TRPO.
  • the candidate beam information may comprise, for example, an AC field and/or candidate RS index.
  • the UE may also include a second set of TRP failure information to the MAC CE. If a second TRP (denoted as TRP1) has failed, the UE may indicate the failed second TRP by setting the second TRP failure information field to indicate the second beam failure. If TRP 1 has not failed, the UE may set the second TRP failure information field to indicate that TRP1 has not failed.
  • the UE may encode the TRP1 beam failure information into the first TRP failure information field.
  • the indication may be followed by the candidate beam information of TRP1.
  • the candidate beam information may comprise, for example, an AC field and/or candidate RS index.
  • the failure information of TRP1 is encoded first in the MAC CE, the second TRP information field may not be encoded. If TRP1 is indicated first, then the MAC CE does not indicate TRPO failure. In other words, the above TRP failure information, or octet, comprising the TRP failure information and/or AC field encoding is performed per serving cell indicated by the bitmap comprising the SpCell ‘P’ bit and Ci fields.
  • the UE After encoding the beam failure indication data to the MAC CE, the UE transmits 304 the MAC CE comprising the encoded beam failure indication data to the access point. The access point may then initiate a beam failure recovery procedure for the UE based on the beam failure indication data comprised in the received MAC CE.
  • the order of the TRPs encoded in the MAC CE is just an example, and the encoding order of the TRPs may also be reversed.
  • TRP1 may also be encoded first before TRPO in the above exemplary embodiment.
  • the TRP# failure may refer to the failure of the BFD-RS set# or BFD-RS set associated with CORESETPoollndex# or any higher layer parameter index# that is used to group the BFD-RS to a specific set of qO.
  • FIG. 4 illustrates a MAC CE according to an exemplary embodiment.
  • beam failure of at least one TRP has been detected for a serving cell (for example SpCell indicated by the ‘P’ bit).
  • the R1 bit indicates whether the failed TRP is TRP0 or TRP1. If the R1 bit is set to 1, this indicates that TRP1 has failed. If the R1 bit is set to 0, this indicates that at least TRP0 has failed.
  • the procedures herein may be applicable to any serving cell (for example SpCell and/or SCell).
  • the candidate beam information (for example AC and/or candidate RS index) is encoded for TRP0, and another field (octet) for TRP1 information follows.
  • the candidate beam information (for example AC and/or candidate RS index) is encoded for TRP1, and no further octet follows, since the TRP0 failure is indicated first if it has occurred.
  • the R1 bit indicates failure of TRP0 (i.e. R1 is set to 0)
  • the R2 bit indicates whether TRP1 has failed. If the R2 bit indicates TRP1 failure, then the candidate beam information (for example AC and/or candidate RS index) in the second field (octet) is encoded for TRP1.
  • the failure of a TRP may be indicated by setting a TRP-specific field in a MAC CE to a specific value.
  • the value of a first bit may be set to ' if a first TRP is in failure, and otherwise the first bit may be set to ⁇ ’ to indicate no failure on the first TRP.
  • the value of a second bit may be set to ' if a second TRP is in failure, and otherwise the second bit may be set to ⁇ ’ to indicate no failure on the second TRP.
  • the value of a third bit may be set to ' if a third TRP is in failure, and otherwise the third bit may be set to ⁇ ’ to indicate no failure on the third TRP.
  • the TRP-specific fields may be listed in ascending or descending order in the MAC CE, and a bit may be set in each field in the TRP information field (for example octet) to indicate the failed or not failed status.
  • the TRP fields may be listed per failed serving cell indicated in the MAC CE.
  • a bitmap may comprise one or more bits or octets that indicate the TRP-specific failure status (failed or not failed) for each of the indicated serving cells in the MAC CE.
  • a serving cell bit may be set to a specific value to indicate failure in a specific serving cell. For example, for each serving cell for which failure is indicated, the TRP-specific failure status may be indicated.
  • FIG. 5 illustrates a MAC CE according to another exemplary embodiment, wherein the MAC CE comprises a bitmap to indicate whether a TRP- specific beam failure or cell-level beam failure has occurred.
  • the serving cell specific T/S field indicates whether the UE indicates TRP-specific failure (T) or serving cell level failure (S).
  • T TRP-specific failure
  • S serving cell level failure
  • the UE may indicate a beam failure of at least one serving cell for example by using the ServCell index bitmap, and the T /S field may be set to indicate TRP-specific beam failure.
  • the T /S field indicates the failure of one of the TRPs, wherein the TRP ID is encoded in the R1 bit of the candidate beam octet, i.e. the first octet comprising Rl, AC, and candidate RS index.
  • the UE may be configured to indicate this when one TRP is in failure.
  • it may indicate the failure of both TRPs with the encoding logic described above with reference to FIG. 3.
  • it may indicate the failure of both TRPs.
  • both candidate beam octets (Rl, AC, first candidate RS index; R2, AC, second candidate RS index) may be encoded per indicated serving cell.
  • a field (for example the T/S field) may be set to indicate TRP-specific beam failure, and both candidate beam octets may be encoded to the MAC CE.
  • a field (for example the T/S field) may be set to indicate cell-level failure (for example both TRPs have failed), and both TRP- specific candidate beam octets may be encoded to the MAC CE.
  • the UE when the UE indicates the beam failure of a (serving) cell, it may set the T/S field to indicate serving cell failure, and the candidate beam information octet (Rl, AC, candidate RS index) maybe encoded for the cell.
  • the UE may omit the TRP-specific candidate beam information for the SpCell, when MAC CE is provided using CBRA.
  • bitmap length to indicate the TRP-specific failure or cell failure may be determined based on the number of serving cells, for which failure is indicated based on the Ci fields and the P field.
  • the UE may initiate a random access procedure for beam failure recovery on the SpCell or other serving cell.
  • the UE may provide a MAC CE indicating SpCell level (or serving cell level) failure (for example instead TRP-specific failure) for a serving cell, where no candidate beams were available to be indicated for the failed TRPs.
  • the BFR MAC CE illustrated in FIG. 2 may be used for indicating the cell-level failure when there are no candidate beams available for both (or all of the) TRPs. This may be an implicit indication by the UE to indicate that it has determined that no candidates are available for the failed TRPs.
  • BFR MAC CE may refer to a truncated BFR MAC CE or to a BFR MAC CE.
  • the UE when it sends a BFR MAC CE, it may indicate to the network that the UE recovers a cell (instead of one or more TRPs).
  • the UE may set a field in a MAC CE (for example the T/S field) to indicate cell-level failure. For example, when indicating the cell-level failure, the UE may omit candidate beam information from the MAC CE for SpCell, when the MAC CE is provided using CBRA. In another example, if there are no candidate beams available for any of the failed TRPs for an SCell (or for a serving cell), then the UE may indicate cell-level failure and omit candidate beam information fields from the MAC CE.
  • a field in a MAC CE for example the T/S field
  • the UE may implicitly indicate the failure of TRPs and that there are no new candidate beam(s) available for the failed TRPs, when the UE indicates a serving cell level failure using a specific field in a MAC CE, or uses a BFR MAC CE or any MAC that is used for beam failure recovery.
  • the new candidate beam for one or more TRPs may be indicated by the selected DL RS (SSB or CS1-RS) for the random access procedure.
  • the UE may be configured for mTRP communication, if, for example more than one CORESETPoollndex values are configured for the UE, or more than one sets of BFD-RS are configured for the UE.
  • UE may initiate beam failure recovery for the failed TRP(s).
  • the UE may encode, or include, in a MAC CE the TRP failure information, or octet, comprising the TRP failure information and/or AC field for both or all of the failed TRPs.
  • the new candidate beam for one or more TRPs may then be further indicated by the selected DL RS (SSB or CS1-RS) for the random access procedure initiated for beam failure recovery.
  • the MAC CE illustrated in FIG. 5 may be applicable for one or more of the following: SpCell, SCell, and/or multiple SCells.
  • the information may be encoded as described above per serving cell that has been indicated for failure.
  • FIG. 6 illustrates a flow chart according to an exemplary embodiment.
  • the functions illustrated in FIG. 6 may be performed by an apparatus such as a UE, or an apparatus comprised in a UE.
  • a beam failure is detected 601 on at least one TRP of a plurality of TRPs, the apparatus being configured to communicate with the plurality of TRPs.
  • One or more beam failure indication data is included 602 into a first MAC CE, wherein the one or more beam failure indication data indicates the beam failure detected on the at least one TRP.
  • the one or more beam failure indication data comprises at least a first bit that comprises a first value and a second value, wherein the first value of the first bit indicates a first TRP of the plurality of TRPS at least on which the beam failure is detected.
  • the second value of the first bit may indicate, for example, a second TRP of the plurality of TRPs on which the beam failure is detected. Alternatively, the second value of the first bit may indicate that no beam failure is detected at least on the first TRP.
  • the first MAC CE comprising the one or more beam failure indication data is transmitted 603 to an access point.
  • FIG. 7 illustrates a flow chart according to another exemplary embodiment.
  • the functions illustrated in FIG. 7 maybe performed by an apparatus such as an access point, or an apparatus comprised in an access point.
  • a MAC CE indicating beam failure on at least one TRP is received 701 from a UE.
  • the MAC CE comprises at least a first bit comprising a first value and a second value, wherein the first value of the bit indicates a beam failure on at least a first TRP.
  • the second value of the first bit may indicate, for example, that the beam failure is on a second TRP of the plurality of TRPs. Alternatively, the second value of the first bit may indicate that no beam failure is detected on the first TRP.
  • FIG. 8 illustrates a flow chart according to another exemplary embodiment.
  • the functions illustrated in FIG. 8 may be performed by an apparatus such as a UE, or an apparatus comprised in a UE.
  • a first set of beam failure indication data indicating at least one TRP on which the beam failure is detected is included 801 into a first MAC CE.
  • a second set of beam failure indication data indicating at least one cell-level beam failure is included 802 to a second MAC CE.
  • the legacy BFR MAC CE such as the BFR MAC CE illustrated in FIG. 2] may be used as the second BFR MAC CE for cell(s) for which full cell-level failure is indicated
  • the new BFR MAC CE for example the BFR MAC CE illustrated in FIG. 4 or FIG. 5
  • the second MAC CE is transmitted 803 to an access point.
  • the first MAC CE is transmitted 804 to the access point.
  • the UE may indicate both the cell-level BFR MAC CE and the TRP-level BFR MAC CE in a single MAC PDU.
  • the cell-level BFR MAC CE may be prioritized over the TRP-level BFR MAC CE.
  • the second BFR MAC CE may be transmitted before the first BFR MAC CE.
  • the (cell-level or TRP-level) BFR MAC CE, in which the SpCell is indicated as failed may be prioritized in case the SpCell has failed.
  • FIG. 9 illustrates a flow chart according to another exemplary embodiment. The functions illustrated in FIG. 9 may be performed by an apparatus such as an access point, or an apparatus comprised in an access point.
  • a second MAC CE is received 901, wherein the second MAC CE comprises a second set of beam failure indication data indicating at least one cell-level beam failure.
  • a first MAC CE is received 902, wherein the first MAC CE comprises a first set of beam failure indication data indicating at least one TRP on which the beam failure is detected.
  • a MAC CE may comprise at least one of:
  • MAC CE is a MAC CE indicating failure of at least one TRP of at least one serving cell
  • a field value/sub-header value, for example LCID, of the legacy BFR MAC CE wherein specific fields of the legacy BFR MAC CE may be encoded when the UE is configured with mTRP beam failure detection and recovery.
  • the mTRP failure detection may be determined based on the configuration of more than one set of qO.
  • a MAC CE may comprise a set of fields per cell and at least one field specific to a TRP, wherein the field may comprise of:
  • RSRP reference signal received power
  • a technical advantage provided by some exemplary embodiments is that they may enable an improved beam failure recovery procedure to cover mTRP operation. Some exemplary embodiments may improve communication efficiency, and enable the UE to recover more efficiently from a beam failure. Furthermore, in some exemplary embodiments, an octet can be omitted from the MAC CE, when at least one but not all TRPs are in failure. In addition, two or more TRPs can be indicated to be in failure.
  • FIG. 10 illustrates an apparatus 1000, which may be an apparatus such as, or comprised in, a terminal device, according to an exemplary embodiment.
  • a terminal device may also be referred to as a UE or user equipment herein.
  • the apparatus 1000 comprises a processor 1010.
  • the processor 1010 interprets computer program instructions and processes data.
  • the processor 1010 may comprise one or more programmable processors.
  • the processor 1010 may comprise programmable hardware with embedded firmware and may, alternatively or additionally, comprise one or more application-specific integrated circuits (ASICs).
  • ASICs application-specific integrated circuits
  • the processor 1010 is coupled to a memory 1020.
  • the processor is configured to read and write data to and from the memory 1020.
  • the memory 1020 may comprise one or more memory units.
  • the memory units may be volatile or non-volatile. It is to be noted that in some exemplary embodiments there may be one or more units of non-volatile memory and one or more units of volatile memory or, alternatively, one or more units of non-volatile memory, or, alternatively, one or more units of volatile memory.
  • Volatile memory may be for example random-access memory (RAM), dynamic random-access memory (DRAM) or synchronous dynamic random-access memory (SDRAM).
  • Non-volatile memory may be for example read-only memory (ROM), programmable read-only memory (PROM), electronically erasable programmable read-only memory (EEPROM), flash memory, optical storage or magnetic storage.
  • ROM read-only memory
  • PROM programmable read-only memory
  • EEPROM electronically erasable programmable read-only memory
  • flash memory optical storage or magnetic storage.
  • memories may be referred to as non-transitory computer readable media.
  • the memory 1020 stores computer readable instructions that are executed by the processor 1010.
  • non-volatile memory stores the computer readable instructions and the processor 1010 executes the instructions using volatile memory for temporary storage of data and/or instructions.
  • the computer readable instructions may have been pre-stored to the memory 1020 or, alternatively or additionally, they may be received, by the apparatus, via an electromagnetic carrier signal and/or may be copied from a physical entity such as a computer program product. Execution of the computer readable instructions causes the apparatus 1000 to perform one or more of the functionalities described above.
  • a “memory” or “computer-readable media” or “computer-readable medium” may be any non-transitory media or medium or means that can contain, store, communicate, propagate or transport the instructions for use by or in connection with an instruction execution system, apparatus, or device, such as a computer.
  • the apparatus 1000 may further comprise, or be connected to, an input unit 1030.
  • the input unit 1030 may comprise one or more interfaces for receiving input.
  • the one or more interfaces may comprise for example one or more temperature, motion and/or orientation sensors, one or more cameras, one or more accelerometers, one or more microphones, one or more buttons and/or one or more touch detection units.
  • the input unit 1030 may comprise an interface to which external devices may connect to.
  • the apparatus 1000 may also comprise an output unit 1040.
  • the output unit may comprise or be connected to one or more displays capable of rendering visual content, such as a light emitting diode (LED) display, a liquid crystal display (LCD) and/or a liquid crystal on silicon (LCoS) display.
  • the output unit 1040 may further comprise one or more audio outputs.
  • the one or more audio outputs may be for example loudspeakers.
  • the apparatus 1000 further comprises a connectivity unit 1050.
  • the connectivity unit 1050 enables wireless connectivity to one or more external devices.
  • the connectivity unit 1050 comprises at least one transmitter and at least one receiver that may be integrated to the apparatus 1000 or that the apparatus 1000 may be connected to.
  • the at least one transmitter comprises at least one transmission antenna, and the at least one receiver comprises at least one receiving antenna.
  • the connectivity unit 1050 may comprise an integrated circuit or a set of integrated circuits that provide the wireless communication capability for the apparatus 1000.
  • the wireless connectivity may be a hardwired application-specific integrated circuit (ASIC).
  • ASIC application-specific integrated circuit
  • the connectivity unit 1050 may comprise one or more components such as a power amplifier, digital front end (DFE), analog-to-digital converter (ADC), digital-to-analog converter (DAC), frequency converter, (de) modulator, and/or encoder/decoder circuitries, controlled by the corresponding controlling units.
  • DFE digital front end
  • ADC analog-to-digital converter
  • DAC digital-to-analog converter
  • frequency converter frequency converter
  • de modulator demodulator
  • encoder/decoder circuitries controlled by the corresponding controlling units.
  • apparatus 1000 may further comprise various components not illustrated in FIG. 10.
  • the various components may be hardware components and/or software components.
  • the apparatus 1100 of FIG. 11 illustrates an exemplary embodiment of an apparatus such as, or comprised in, an access point such as a gNB.
  • the apparatus may comprise, for example, a circuitry or a chipset applicable to an access point to realize some of the described exemplary embodiments.
  • the apparatus 1100 may be an electronic device comprising one or more electronic circuitries.
  • the apparatus 1100 may comprise a communication control circuitry 1110 such as at least one processor, and at least one memory 1120 including a computer program code (software) 1122 wherein the at least one memory and the computer program code (software) 1122 are configured, with the at least one processor, to cause the apparatus 1100 to carry out some of the exemplary embodiments described above.
  • the memory 1120 may be implemented using any suitable data storage technology, such as semiconductor-based memory devices, flash memory, magnetic memory devices and systems, optical memory devices and systems, fixed memory and/or removable memory.
  • the memory may comprise a configuration database for storing configuration data.
  • the configuration database may store a current neighbour cell list, and, in some exemplary embodiments, structures of the frames used in the detected neighbour cells.
  • the apparatus 1100 may further comprise a communication interface 1130 comprising hardware and/or software for realizing communication connectivity according to one or more communication protocols.
  • the communication interface 1130 comprises at least one transmitter (TX) and at least one receiver (RX) that may be integrated to the apparatus 1100 or that the apparatus 1100 may be connected to.
  • the communication interface 1130 provides the apparatus with radio communication capabilities to communicate in the cellular communication system.
  • the communication interface may, for example, provide a radio interface to terminal devices.
  • the apparatus 1100 may further comprise another interface towards a core network such as the network coordinator apparatus and/or to the access nodes of the cellular communication system.
  • the apparatus 1100 may further comprise a scheduler 1140 that is configured to allocate resources.
  • circuitry may refer to one or more or all of the following: a. hardware-only circuit implementations (such as implementations in only analog and/or digital circuitry) and b. combinations of hardware circuits and software, such as (as applicable): i. a combination of analog and/or digital hardware circuit(s) with software/firmware and ii. any portions of hardware processor(s) with software (including digital signal processor(s)), software, and memory(ies) that work together to cause an apparatus, such as a mobile phone, to perform various functions) and c. hardware circuit(s) and or processor(s), such as a microprocessor(s) or a portion of a microprocessor(s), that requires software (for example firmware) for operation, but the software may not be present when it is not needed for operation.
  • hardware circuit(s) and or processor(s) such as a microprocessor(s) or a portion of a microprocessor(s), that requires software (for example firmware) for operation, but the software may not be present when it is not needed
  • circuitry also covers an implementation of merely a hardware circuit or processor (or multiple processors) or portion of a hardware circuit or processor and its (or their) accompanying software and/or firmware.
  • circuitry also covers, for example and if applicable to the particular claim element, a baseband integrated circuit or processor integrated circuit for a mobile device or a similar integrated circuit in server, a cellular network device, or other computing or network device.
  • the techniques and methods described herein may be implemented by various means. For example, these techniques may be implemented in hardware (one or more devices), firmware (one or more devices), software (one or more modules), or combinations thereof.
  • the apparatus(es) of exemplary embodiments may be implemented within one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), graphics processing units (GPUs), processors, controllers, micro-controllers, microprocessors, other electronic units designed to perform the functions described herein, or a combination thereof.
  • ASICs application-specific integrated circuits
  • DSPs digital signal processors
  • DSPDs digital signal processing devices
  • PLDs programmable logic devices
  • FPGAs field programmable gate arrays
  • GPUs graphics processing units
  • processors controllers, micro-controllers, microprocessors, other electronic units designed to perform the functions described herein, or a
  • the implementation can be carried out through modules of at least one chipset (for example procedures, functions, and so on) that perform the functions described herein.
  • the software codes may be stored in a memory unit and executed by processors.
  • the memory unit may be implemented within the processor or externally to the processor. In the latter case, it can be communicatively coupled to the processor via various means, as is known in the art.
  • the components of the systems described herein may be rearranged and/or complemented by additional components in order to facilitate the achievements of the various aspects, etc., described with regard thereto, and they are not limited to the precise configurations set forth in the given figures, as will be appreciated by one skilled in the art.

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Mobile Radio Communication Systems (AREA)
EP22714384.9A 2021-03-26 2022-03-11 Anzeige von strahlfehlern beim betrieb mit mehreren sendeempfangspunkten Pending EP4315627A1 (de)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
FI20215353 2021-03-26
PCT/EP2022/056312 WO2022200078A1 (en) 2021-03-26 2022-03-11 Indicating beam failure in multiple transmission reception point operation

Publications (1)

Publication Number Publication Date
EP4315627A1 true EP4315627A1 (de) 2024-02-07

Family

ID=81325149

Family Applications (1)

Application Number Title Priority Date Filing Date
EP22714384.9A Pending EP4315627A1 (de) 2021-03-26 2022-03-11 Anzeige von strahlfehlern beim betrieb mit mehreren sendeempfangspunkten

Country Status (6)

Country Link
US (1) US20240179548A1 (de)
EP (1) EP4315627A1 (de)
JP (1) JP2024512611A (de)
KR (1) KR20230161496A (de)
CN (1) CN117083810A (de)
WO (1) WO2022200078A1 (de)

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020057665A1 (zh) * 2018-09-21 2020-03-26 中兴通讯股份有限公司 波束失败恢复的处理方法及装置

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020057665A1 (zh) * 2018-09-21 2020-03-26 中兴通讯股份有限公司 波束失败恢复的处理方法及装置
EP3855661A1 (de) * 2018-09-21 2021-07-28 ZTE Corporation Verfahren und vorrichtung zur verarbeitung von strahlfehlern

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
MODERATOR (CATT): "Moderator summary on M-TRP simultaneous transmission with multiple Rx panels (round 0)", vol. RAN WG1, no. E-meeting; 20210125 - 20210205, 5 February 2021 (2021-02-05), XP051977633, Retrieved from the Internet <URL:https://ftp.3gpp.org/tsg_ran/WG1_RL1/TSGR1_104-e/Docs/R1-2101862.zip R1-2101862_FEMIMO_item2c_MTRP_BM_v056_ZTE2_Mod.docx> [retrieved on 20210205] *
See also references of WO2022200078A1 *
VIVO: "Further discussion on MTRP multibeam enhancement", vol. RAN WG1, no. e-Meeting; 20201026 - 20201113, 24 October 2020 (2020-10-24), XP051946456, Retrieved from the Internet <URL:https://ftp.3gpp.org/tsg_ran/WG1_RL1/TSGR1_103-e/Docs/R1-2007647.zip R1-2007647_Further discussion on MTRP multibeam enhancement_final.docx> [retrieved on 20201024] *

Also Published As

Publication number Publication date
CN117083810A (zh) 2023-11-17
US20240179548A1 (en) 2024-05-30
KR20230161496A (ko) 2023-11-27
JP2024512611A (ja) 2024-03-19
WO2022200078A1 (en) 2022-09-29

Similar Documents

Publication Publication Date Title
US20230308974A1 (en) Beam switching controlled by distributed unit
US20230199529A1 (en) M-trp beam failure indication
US20230328617A1 (en) Beam failure reporting
US20240276333A1 (en) Determining handover command transmission based on survival time
US11997504B2 (en) Dynamic spectrum sharing reduced overhead operation
US11627552B1 (en) Offset value for paging early indication
US20240236937A9 (en) Determining random-access resources for group paging
US20240179548A1 (en) Indicating beam failure in multiple transmission reception point operation
US11870585B1 (en) Adapting hybrid automatic repeat requests
US20220311538A1 (en) Allocating radio resources based on user mode
US20240155508A1 (en) Power headroom report
WO2023152377A1 (en) Beam link failure status information
WO2023213551A1 (en) Indicating a transmission configuration indicator state
WO2023174519A1 (en) Cell search
EP4449643A1 (de) Teilweise wiederholung eines physikalischen rundfunkkanals
WO2023274494A1 (en) Determining random-access channel transmission occasions
WO2023078642A1 (en) Indicating system information modification in inter-cell operation
WO2023158419A1 (en) Timing-based control for relaxed measurement
WO2024068131A1 (en) Delayed access to primary cell of secondary cell group
EP4275421A1 (de) Zuweisung von leistungssteuerungsparametern für betrieb mit mehreren sendeempfangspunkten
CN117897993A (zh) 基于特定于装置类型的一个或多个条件而发起小数据传输

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

AK Designated contracting states

Kind code of ref document: A1

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

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

Free format text: STATUS: EXAMINATION IS IN PROGRESS

17Q First examination report despatched

Effective date: 20240521

DAV Request for validation of the european patent (deleted)
DAX Request for extension of the european patent (deleted)