Beam failure recovery for single-dci based m-trp urlcc transmission

Abstract

Apparatuses and systems are provided for providing multiple structures to enable flexibility in multiple multi-transmission and reception point ultra-reliable low latency communication (M-TRP URLLC) operations and to reduce measurement effort and power consumption from a transceiver device, such as a UE. The technology disclosed herein features a transceiver device including a transceiver and circuitry. The transceiver receives signals from multiple transmission and reception points (M-TRPs) in a network on at least a physical downlink shared channel (PDSCH). The circuitry performs beam failure recovery (BFR) by evaluating beam failure detection (BFD) and candidate new beam detection (CBD) for signals from a first one of the M-TRPs. The signals from the first one of the M-TRPs include signals received on a physical downlink control channel (PDCCH), and the circuitry determines to skip evaluation of one or both of the BFD and CBD for one or more additional ones of the M-TRPs in response to one or more conditions.

Description

Technical Field

[0001] The present invention generally relates to communication devices, and more specifically to beam fault recovery mechanisms for such communication devices. Background Technology

[0002] Communication devices are ubiquitous in today's world in the form of telephones, tablets, computers, cameras, digital audio / video players, wearable devices, game consoles, telehealth / telemedicine devices, and vehicles that provide communication capabilities, as well as various combinations thereof. Communication can include exchanging data via, for example, cellular systems, wireless local area network (LAN) systems, satellite systems, and various combinations thereof.

[0003] As communications advance to higher generations (e.g., 5G New Radio (5G NR)), many applications (e.g., Augmented Reality / Virtual Reality (AR / VR), eHealth, eSecurity, and mission-critical applications) require Ultra-Reliable Low-Latency Communication (URLLC). URLLC places stringent requirements on capabilities such as throughput, latency, and availability, and is envisioned as one of the driving forces for future vertical applications such as wireless control of industrial manufacturing or production processes, telemedicine surgery, distribution automation in smart grids, and transportation security. Furthermore, 5G NR includes multiple transmit and receive points (M-TRPs) to improve reliability, coverage, and capacity performance through flexible deployment scenarios. For example, to support the exponential growth of mobile data traffic in 5G and to enhance coverage, User Equipment (UE) (i.e., communication devices) is expected to access a network comprised of M-TRPs (e.g., macro cells, small cells, pico cells, femto cells, remote radio heads, and relay nodes).

[0004] During operation, the UE can access signals from one of the M-TRPs. The UE determines that a signal from one of the M-TRPs has been lost through a beam failure detection (BFD) procedure. The UE then attempts to restore communication—a process that includes new beam identification (NBI), also known as candidate new beam detection (CBD). While both BFD and CBD are critical UE procedures for maintaining ultra-reliability and low latency in URLLC communication, recovery after a beam failure, including both BFD and CBD procedures, requires measurement of workload and power consumption.

[0005] Therefore, there is a need for communication devices and systems that conserve power during recovery from beam failure without compromising reliability in URLLC communication. Furthermore, other desirable features and characteristics will become apparent from the following detailed description and appended claims, taken in conjunction with the accompanying drawings and background information. Summary of the Invention

[0006] A non-limiting and exemplary embodiment helps to provide multiple architectures to enable the flexibility of multi-transmit and receive point ultra-reliable low-latency communication (M-TRP URLLC) operation and reduce measurement work and power consumption from transceiver devices such as UEs.

[0007] In embodiments, the technology disclosed herein is characterized by a transceiver apparatus comprising a transceiver and a circuit system. The transceiver receives signals from multiple transmit and receive points (M-TRPs) in the network, at least on the Physical Downlink Shared Channel (PDSCH). The circuit system performs beam fault recovery (BFR) by evaluating beam fault detection (BFD) and candidate new beam detection (CBD) for signals from at least a first M-TRP. The signals from the first M-TRP include signals received on the Physical Downlink Control Channel (PDCCH), and the circuit system determines, in response to one or more operating conditions, to skip (or execute) one or both of BFD and CBD.

[0008] It should be noted that general or specific embodiments may be implemented as systems, methods, integrated circuits, computer programs, storage media or any alternative combination thereof.

[0009] Other benefits and advantages of the disclosed embodiments will become apparent from the specification and drawings. Benefits and / or advantages can be obtained individually from the various embodiments and features in the specification and drawings, without the need to provide all of these embodiments and features to obtain one or more of such benefits and / or advantages. Attached Figure Description

[0010] In the following description, exemplary embodiments will be described in more detail with reference to the accompanying drawings.

[0011] Figure 1 An exemplary architecture of a 3GPP NR system is shown;

[0012] Figure 2 This is a schematic diagram illustrating the functional division of NG-RAN and 5GC;

[0013] Figure 3 It is a sequence diagram of the Radio Resource Control (RRC) connection establishment / reconfiguration process;

[0014] Figure 4 This is a schematic diagram illustrating the use cases of enhanced mobile broadband (eMBB), massive machine-type communications (mMTC), and ultra-reliable low-latency communications (URLLC);

[0015] Figure 5 This is a block diagram showing an exemplary 5G system architecture for non-roaming scenarios;

[0016] Figure 6 This is a diagram of an ultra-reliable low-latency communication (URLLC) system based on multiple transmitter and receiver points (M-TRP) with single downlink control information (DCI);

[0017] Figure 7 This is a diagram of a typical beam fault recovery (BFR) process;

[0018] Figure 8 This is a diagram illustrating a user equipment (UE) simultaneously receiving the Physical Downlink Shared Channel (PDSCH) from both the first TRP and the second TRP.

[0019] Figure 9 This is a diagram illustrating the duration of the operation time used for beam fault detection (BFD) and candidate new beam detection (CBD) during the BFR process;

[0020] Figure 10 It is a diagram of the first BFR process according to this disclosure;

[0021] as well as Figure 11 This is a diagram of the second BFR process according to this disclosure.

[0022] Skilled technicians will understand that the components in the diagram are shown for simplicity and clarity and are not necessarily drawn to scale. Detailed Implementation

[0023] The following detailed embodiments are merely exemplary in nature and are not intended to limit the exemplary embodiments or their application and use. Furthermore, they are not intended to be construed as being bound by any theories presented in the foregoing background or the following detailed embodiments. The purpose of this disclosure is to present exemplary embodiments of communication devices and systems that save power during recovery from beam failure without compromising reliability in Ultra-Reliable Low-Latency Communication (URLLC) communication, thereby reducing measurement work and power consumption during beam failure recovery (BFR) while maintaining URLLC.

[0024] 5G NR System Architecture and Protocol Stack

[0025] The 3rd Generation Partnership Project (3GPP) has been working on the next version of 5G cellular technology, including developing new radio access technology (NR) that operates in a frequency range up to 100 GHz. The first version of the 5G standard was completed at the end of 2017, which allowed for continued trials and commercial deployments of smartphones compliant with the 5G NR standard.

[0026] refer to Figure 1The overall system architecture assumes a Next Generation Radio Access Network (NG-RAN) 102 including gNB 104, providing UEs with NG-Radio Access User Plane (SDAP / PDCP / RLC / MAC / PHY) and Radio Resource Control (RRC) protocol termination. gNBs 104 interconnect with each other via Xn interface 106. gNBs also connect to Next Generation Core (NGC) 108 via Next Generation (NG) interfaces, more specifically via NG-C interface 112a to Access and Mobility Management Functions (AMF) 110 (e.g., specific core entities performing AMF), and via NG-U interface 112b to User Plane Functions (UPF) 110 (e.g., specific core entities performing UPF). The NG-RAN architecture 100 in... Figure 1 As shown in (see, for example, 3GPP TS38.300 v15.6.0, Section 4).

[0027] The user plane protocol stack for NR (see, for example, 3GPP TS 38.300, Section 4.4.1) includes the Packet Data Convergence Protocol (PDCP) (see Section 6.4 of TS 38.300), Radio Link Control (RLC) (see Section 6.3 of TS 38.300), and the MAC (Media Access Control, see Section 6.2 of TS 38.300) sublayer, terminating at the gNB on the network side. Furthermore, a new Access Layer (AS) sublayer (Service Data Adaptation Protocol (SDAP)) is introduced above PDCP (see, for example, Sub-clause 6.5 of 3GPP TS 38.300). A control plane protocol stack is also defined for NR (see, for example, TS 38.300, Section 4.4.2). An overview of Layer 2 functions is given in Sub-clause 6 of TS 38.300. The functions of the PDCP, RLC, and MAC sublayers are listed in Sections 6.4, 6.3, and 6.2 of TS 38.300, respectively. The functions of the RRC layer are listed in Subclause 7 of TS 38.300.

[0028] For example, the media access control layer handles logical channel multiplexing and scheduling and scheduling-related functions, including handling different sets of parameters (numerology).

[0029] The Physical Layer (PHY) is responsible for tasks such as decoding, PHY HARQ processing, modulation, multi-antenna processing, and mapping signals to appropriate physical time-frequency resources. It also handles the mapping from transport channels to physical channels. The Physical Layer provides services to the MAC Layer in the form of transport channels. A physical channel corresponds to a set of time-frequency resources used for transmission on a specific transport channel, and each transport channel is mapped to a corresponding physical channel. For example, physical channels are the Physical Random Access Channel (PRACH), Physical Uplink Shared Channel (PUSCH), and Physical Uplink Control Channel (PUCCH) for uplink, and the Physical Downlink Shared Channel (PDSCH), Physical Downlink Control Channel (PDCCH), and Physical Broadcast Channel (PBCH) for downlink.

[0030] Use cases / deployment scenarios for NR can include enhanced mobile broadband (eMBB), ultra-reliable low-latency communication (URLLC), and massive machine-type communication (mMTC), each with different requirements in terms of data rate, latency, and coverage. For example, eMBB is expected to support peak data rates (20Gbps for downlink and 10Gbps for uplink) and user experience data rates that are orders of magnitude higher than those offered by IMT-Advanced. On the other hand, in the case of URLLC, ultra-low latency (0.5ms user plane latency for both UL and DL) and high reliability (1-10 times latency within 1ms) are crucial. -5 This places more stringent requirements on mMTC. Finally, mMTC may preferably require a high connection density (1,000,000 devices / km in urban environments). 2 ), wide coverage in harsh environments, and extremely long-life batteries (15 years) for low-cost devices.

[0031] Therefore, a set of OFDM parameters suitable for one use case (e.g., subcarrier spacing, OFDM symbol duration, cyclic prefix (CP) duration, number of symbols per scheduling interval) may not be suitable for another use case. For example, low-latency services may preferably require shorter symbol durations (and therefore larger subcarrier spacings) and / or fewer symbols per scheduling interval (aka TTI) compared to mMTC services. Furthermore, deployment scenarios with large channel delay spreads may preferably require longer CP durations than scenarios with short delay spreads. Subcarrier spacing should be optimized accordingly to maintain similar CP overhead. NR can support more than one value for subcarrier spacing. Accordingly, subcarrier spacings of 15kHz, 30kHz, 60kHz… are currently being considered. Symbol duration T u The subcarrier spacing Δf is determined by the formula Δf = 1 / T. uDirectly related. In a manner similar to that in LTE systems, the term "resource element" can be used to refer to the smallest resource unit consisting of a subcarrier of one OFDM / SC-FDMA symbol length.

[0032] In the new 5G-NR radio system, for each parameter set and carrier, resource grids for subcarriers and OFDM symbols are defined for both uplink and downlink. Each element in the resource grid is called a resource element and is identified based on its frequency index in the frequency domain and its symbol position in the time domain (see 3GPP TS 38.211 v15.6.0).

[0033] 5G NR Function Division between NG-RAN and 5GC

[0034] (Control signal)

[0035] In this disclosure, the downlink control signals (information) related to this disclosure may be signals (information) transmitted through the physical layer PDCCH, or signals (information) transmitted through the RRC or higher-layer MAC control elements (CE). Downlink control signals may be predefined signals (information).

[0036] The uplink control signals (information) related to this disclosure may be signals (information) transmitted via the physical layer PUCCH, or signals (information) transmitted via RRC or higher-layer MAC CE. Furthermore, the uplink control signals may be predefined signals (information). Uplink control signals may be replaced by uplink control information (UCI), first-level sidelink control information (SCI), or second-level SCI.

[0037] (Base station)

[0038] In this disclosure, a base station can be, for example, a Transmitter Receiver Point (TRP), a clusterhead, an access point, a Remote Radio Header (RRH), an eNodeB (eNB), a gNodeB (gNB), a base station (BS), a Base Transceiver Station (BTS), a base unit, or a gateway. Furthermore, in sidelink communication, a terminal can be used instead of a base station. A base station can be a relay device that relays communication between higher nodes and terminals. A base station can also be a roadside unit.

[0039] (Uplink / Downlink / Sidelink)

[0040] This disclosure can be applied to any of the uplink, downlink, and sidelink.

[0041] This disclosure can be applied to, for example, uplink channels (such as PUSCH, PUCCH, and PRACH), downlink channels (such as PDSCH, PDCCH, and PBCH), and sidelink channels (such as Physical Sidelink Shared Channel (PSSCH), Physical Sidelink Control Channel (PSCCH), and Physical Sidelink Broadcast Channel (PSBCH)).

[0042] PDCCH, PDSCH, PUSCH, and PUCCH are examples of downlink control channel, downlink data channel, uplink data channel, and uplink control channel, respectively. PSCCH and PSSCH are examples of sidelink control channel and sidelink data channel, respectively. PBCH and PSBCH are examples of broadcast channel, and PRACH is an example of random access channel.

[0043] (Data channel / Control channel)

[0044] This disclosure can be applied to any data channel and control channel. The channels in this disclosure can be replaced with data channels including PDSCH, PUSCH, and PSSCH and / or control channels including PDCCH, PUCCH, PBCH, PSCCH, and PSBCH.

[0045] (Reference signal)

[0046] In this disclosure, a reference signal is a signal known to both the base station and the mobile station, and each reference signal may be referred to as a reference signal (RS), or sometimes as a pilot signal. A reference signal may be any of the following: DMRS, Channel State Information-Reference Signal (CSI-RS), Tracking Reference Signal (TRS), Phase Tracking Reference Signal (PTRS), Cell-Specific Reference Signal (CRS), and Sounding Reference Signal (SRS).

[0047] (Time interval)

[0048] In this disclosure, a time resource unit is not limited to one or a combination of time slots and symbols, and can be a time resource unit such as a frame, superframe, subframe, time slot, time slot sub-time slot, micro-time slot, or a time resource unit such as a symbol, orthogonal frequency division multiplexing (OFDM) symbol, single-carrier frequency division multiplexing access (SC-FDMA) symbol, or other time resource units. The number of symbols contained in a time slot is not limited to any of the number of symbols exemplified in the above (one or more) embodiments, and can also be other number of symbols.

[0049] (frequency band)

[0050] This disclosure can be applied to either licensed or unlicensed frequency bands.

[0051] (communication)

[0052] This disclosure can be applied to any of the following: communication between a base station and a terminal (Uu-link communication), communication between terminals (sidelink communication), and vehicle-to-everything (V2X) communication. The channels in this disclosure can be replaced with PSCCH, PSSCH, Physical Sidelink Feedback Channel (PSFCH), PSBCH, PDCCH, PUCCH, PDSCH, PUSCH, and PBCH.

[0053] Furthermore, this disclosure can be applied to any type of terrestrial network or non-terrestrial network (NTN: non-terrestrial network) that uses satellites or high-altitude pseudo-satellites (HAPS). Additionally, this disclosure can be applied to networks with large cell sizes and terrestrial networks with large delays compared to symbol lengths or slot lengths, such as ultra-wideband transmission networks.

[0054] (Antenna port)

[0055] An antenna port refers to a logical antenna (antenna array) formed by one or more physical antennas. That is, an antenna port does not necessarily refer to a single physical antenna; sometimes it refers to an array of antennas, such as multiple antennas. For example, there is no limit to the number of physical antennas forming an antenna port; rather, the antenna port is defined as the smallest unit through which a terminal can transmit a reference signal. An antenna port can also be defined as the smallest unit used for multiplying a precoded vector weight.

[0056] Figure 2 This describes the functional division between NG-RAN 200 and 5GC 250. The logical node of NG-RAN is gNB or ng-eNB 210. 5GC 250 has logical nodes AMF 260, UPF 270 and SMF 280.

[0057] Specifically, gNB and ng-eNB 210 hosting provides the following main functions:

[0058] - Functions of radio resource management 212, such as radio bearer control 214, radio access control 218, connection mobility control 216, and dynamic allocation of resources to the UE in both uplink and downlink (scheduling) 222.

[0059] - Data IP header compression, encryption, and integrity protection;

[0060] - When the route to the AMF cannot be determined based on the information provided by the UE, the AMF is selected at the UE attachment point;

[0061] - Route user plane data to one or more UPFs;

[0062] - Routing control plane information to the AMF;

[0063] - Connection establishment and release;

[0064] - Scheduling and transmission of paging messages;

[0065] - Scheduling and transmission of system broadcast information (originating from AMF or OAM);

[0066] - Mobility and scheduling measurement and measurement reporting configuration 220;

[0067] - Transport-level packet marking in the uplink;

[0068] - Session management;

[0069] - Support for network slicing;

[0070] - Mapping to data radio bearers and QoS flow management;

[0071] - Support for UEs in RRC_INACTIVE state;

[0072] - NAS message distribution functionality;

[0073] - Shared radio access network;

[0074] - Dual connectivity; and

[0075] - The close interaction between NR and E-UTRA.

[0076] Access and Mobility Management Functions (AMF) 260 manages the following key functions:

[0077] - Non-Access Stratum (NAS) signaling terminated;

[0078] - NAS signaling security 262;

[0079] - Access Layer (AS) security controls;

[0080] - Inter-node signaling for core network (CN) nodes used for mobility between 3GPP access networks;

[0081] - Idle mode UE reachability (including paging retransmission control and execution) 264;

[0082] - Registration area management;

[0083] - Support for intra-system and inter-system mobility;

[0084] - Access authentication;

[0085] - Access authorization, including roaming permission verification;

[0086] - Mobility management controls (subscriptions and policies);

[0087] - Support for network slicing; and

[0088] - Session Management Function (SMF) selection.

[0089] In addition, the User Plane Function (UPF) hosts the following main functions:

[0090] - Anchor points for mobility within / between RATs (where applicable) 272;

[0091] - External PDU session point 274 interconnected with the data network;

[0092] - Packet routing and forwarding;

[0093] - User plane portion and grouping checks for policy rule enforcement;

[0094] - Business volume usage report;

[0095] - An uplink classifier used to support routing traffic flows to the data network;

[0096] - A branch point used to support multi-destination PDU sessions;

[0097] - QoS processing in the user plane, such as packet filtering, gating, and UL / DL rate execution;

[0098] - Uplink traffic verification (SDF to QoS flow mapping); and

[0099] - Downlink packet buffering and downlink data notification triggering.

[0100] Finally, the Session Management Function (SMF) 280 hosts the following main functions:

[0101] - Session Management 284;

[0102] - UE IP address allocation and management 282;

[0103] - Selection and control of the UP function;

[0104] - Configure traffic redirection in User Plane Function (UPF) to route traffic to the correct destination;

[0105] - The control section for QoS and policy enforcement; and

[0106] - Downlink data notification.

[0107] RRC connection establishment and reconfiguration process

[0108] Figure 3 Some interactions between UE310, gNB 320, and AMF 330 (5GC entity) are shown in the context of the UE transitioning from RRC_IDLE to RRC_CONNECTED for the NAS part (see TS 38.300 v15.6.0).

[0109] Radio Resource Control (RRC) is a higher-level signaling (protocol) used for UE and gNB configuration. Specifically, this transition involves the AMF 330 preparing UE context data (including, for example, PDU session context, security keys, UE radio capabilities, and UE security capabilities) and sending it to the gNB 320 along with an Initial Context Setup Request 340. The gNB 320 then activates AS security with the UE 310, which is performed by the gNB sending a Security Mode Command message 342 to the UE, and the UE 310 responding with a Security Mode Complete message 344 to the gNB 320. Subsequently, gNB 320 performs reconfiguration to establish Signaling Radio Bearer 2 (SRB2) and (one or more) Data Radio Bearers (DRBs) by sending an RRC Reconfiguration message 346 to UE 310 and receiving an RRC Reconfiguration Complete message 348 from UE 310 in response. For signaling-only connections, since SRB2 and DRBs are not established, the steps related to RRC reconfiguration are skipped. Finally, gNB 320 notifies AMF 330 of the establishment process completion with an Initial Context Establishment Response (INITIAL CONTEXT SETUPRESPONSE) 350.

[0110] Therefore, this disclosure provides an entity of a 5th generation core (5GC) (e.g., AMF, SMF, etc.) including a control circuitry system and a transmitter. The control circuitry system establishes a next-generation (NG) connection with the gNodeB, and the transmitter sends an initial context establishment message to the gNodeB via the NG connection to establish a signaling radio bearer between the gNodeB and the user equipment (UE). Specifically, the gNodeB sends radio resource control (RRC) signaling containing resource allocation configuration information elements to the UE via the signaling radio bearer. The UE then performs uplink transmission or downlink reception based on the resource allocation configuration.

[0111] Use cases of IMT in 2020 and beyond

[0112] Figure 4 This section describes some use cases for 5G NR. Within the 3rd Generation Partnership Project New Radio (3GPP NR), three use cases already envisioned for IMT-2020 to support a wide variety of services and applications are being considered. Phase 1 specifications for Enhanced Mobile Broadband (eMBB) 410 have been completed. In addition to further expanding eMBB 410 support, current and future work will involve the standardization of Ultra Reliable Low Latency Communication (URLLC) 430 and Massive Machine-Type Communication 450. Figure 4 This section illustrates some examples of envisioned use cases for IMT in 2020 and beyond (see, for example, ITU-R M.2083). Figure 2 ).

[0113] URLLC use case 430 has stringent requirements for capabilities such as throughput, latency, and availability, and has been envisioned as one of the drivers for future vertical applications such as wireless control of industrial manufacturing or production processes, telemedicine surgery, distribution automation in smart grids, and transportation security. Ultra-reliability of URLLC 430 is supported by identifying technologies that meet the requirements set by TR 38.913. For NR URLLC in Release 15, key requirements include a target user plane latency of 0.5 ms for both the UL (uplink) and DL (downlink) channels. For a single packet transmission, the general URLLC 430 requirement is a BLER (Block Error Rate) of 1E-5 for a 32-byte packet size with a user plane latency of 1 ms.

[0114] From a physical layer perspective, reliability can be improved in several ways. Current approaches to reliability enhancement include defining a separate CQI table for URLLC 430, a more compact downlink control information (DCI) format, and PDCCH repetition. However, as NR becomes more stable and evolves (to meet the critical requirements of NR URLLC), the scope may expand to achieve ultra-reliability. Specific use cases for NR URLLC in Release 15 include augmented reality / virtual reality (AR / VR), eHealth, eSafety, and mission-critical applications.

[0115] Furthermore, the technical enhancements targeted by NR URLLC 430 aim to improve latency and reliability. Technical enhancements for latency improvement include configurable parameter sets, non-slot-based scheduling with flexible mapping, unlicensed (configured license) uplinks, slot-level repetition of data channels, and downlink preemption. Preemption means that a transmission for which resources have been allocated is stopped, and the allocated resources are used for another transmission that is requested later but has lower latency / higher priority requirements. Thus, an already licensed transmission is preempted by a later transmission. Preemption applies regardless of service type. For example, a transmission of service type A (URLLC) can be preempted by a transmission of service type B (such as eMBB). Technical enhancements for reliability improvement include a dedicated CQI / MCS table for the target BLER of 1E-5.

[0116] The use cases for mMTC (massive machine-type communications) 450 are characterized by a very large number of connected devices typically transmitting relatively small amounts of non-latency-sensitive data. This necessitates low device cost and very long battery life. From an NR perspective, utilizing a very narrow bandwidth is a possible solution for achieving energy savings and extending battery life from a UE perspective.

[0117] As mentioned above, a broader range of reliability is expected for NR. A key requirement in all cases (particularly necessary for URLLC 430 and mMTC 450) is high or ultra-high reliability. Several mechanisms can be considered to improve reliability from both radio and network perspectives. Generally, there are several key potential areas that can help improve reliability. These areas include compact control channel information, data / control channel repetition, and diversity in the frequency, time, and / or spatial domains. These areas generally apply to reliability regardless of the specific communication scenario.

[0118] For the NR URLLC 430, further use cases with more stringent requirements have been identified, such as factory automation, transportation, and power distribution. Depending on the use case, the more stringent requirement is higher reliability (up to 10). -6 (Level), higher availability, packet size up to 256 bytes, time synchronization in the order of a few microseconds (μs) (where this value can be one or a few microseconds depending on the frequency range), and short latency in the order of about 0.5 to 1 millisecond (ms) (especially 0.5 millisecond target user plane latency).

[0119] In addition, several technical enhancements from a physical layer perspective have been identified for NR URLLC 430. These include Physical Downlink Control Channel (PDCCH) enhancements related to Compact DCI, PDCCH repetition, and increased PDCCH monitoring. Furthermore, Uplink Control Information (UCI) enhancements are associated with enhanced Hybrid Automatic Repeat Request (HARQ) and CSI feedback. Additionally, PUSCH enhancements related to microslot-level hopping and retransmission / repetition enhancements have been identified. The term "microslot" refers to a Transmission Time Interval (TTI) comprising fewer symbols than a slot (a slot consisting of fourteen symbols).

[0120] QoS control

[0121] The 5G QoS (Quality of Service) model is based on QoS flows and supports both QoS flows requiring a guaranteed flow bit rate (GBRQoS flows) and QoS flows not requiring a guaranteed flow bit rate (non-GBR QoS flows). Therefore, at the NAS level, QoS flows represent the finest granularity of QoS differentiation within a PDU session. QoS flows are identified within a PDU session by their QoS Flow ID (QFI), which is carried in the encapsulation header via the NG-U interface.

[0122] For each UE, 5GC establishes one or more PDU sessions. For each UE, NG-RAN establishes at least one data radio bearer (DRB) along with the PDU session. Additional DRBs for one or more QoS flows of that PDU session can then be configured (depending on when NG-RAN does so), for example, as referenced above. Figure 3 As shown, NG-RAN maps packets belonging to different PDU sessions to different DRBs. The NAS-level packet filters in the UE and 5GC associate UL and DL packets with QoS flows, while the AS-level mapping rules in the UE and NG-RAN associate UL and DL QoS flows with DRBs.

[0123] Figure 5 The 5G NR non-roaming reference architecture is described (see TS 23.501 v16.1.0, Section 4.23). Application Function (AF) 500 (e.g., managed) Figure 4The external application server (exemplarily described in the 5G service example) interacts with the 3GPP core network to provide services, such as supporting application impacts on traffic routing, access network exposure function (NEF) 505, or interacting with the policy framework for policy control (see Policy Control Function, PCF), such as QoS control. Based on operator deployment, application functions 500 deemed trusted by the operator may be allowed to interact directly with the relevant network functions. Application functions 500 that the operator does not allow to directly access network functions may interact with the relevant network functions via NEF 505 using the external exposure framework.

[0124] Figure 5 Further functional units of the 5G architecture are illustrated, namely Network Slice Selection Function (NSSF) 510, Network Repository Function (NRF) 515, Unified Data Management (UDM) 520, Authentication Server Function (AUSF) 525, Access and Mobility Management Function (AMF) 530, Session Management Function (SMF) 535, and Data Network (DN) 540, such as operator services, internet access, or third-party services. All or part of the core network functions and application services can be deployed in and run in a cloud computing environment.

[0125] Therefore, this disclosure provides an application server (e.g., AF 500 of a 5G architecture) including a transmitter and a control circuitry system. The transmitter sends a request to at least one of the functions of the 5GC (e.g., NEF 505, AMF 530, SMF 535, PCF545, UPF 550, etc.) containing a QoS requirement of at least one of URLLC, eMMB, and mMTC services to establish a PDU session including radio bearers between the gNodeB and the UE according to the QoS requirements. The control circuitry system uses the established PDU session to perform services.

[0126] Figure 6 A diagram illustrates a multi-transmitter and receiver point (M-TRP) ultra-reliable low-latency communication (URLLC) network 600 based on a single downlink control information (DCI). M-TRP transmissions are used to overcome congestion effects and improve the performance of a cell-edge UE 602. In a single-DCI-based M-TRP URLLC transmission, network 600 schedules PDSCH transmissions 610, 612 from multiple TRPs (i.e., TRP 1 620 and TRP 2 622), wherein PDSCH 610, 612 from different TRPs 620, 622 are transmitted at different layers (i.e., layer 1 630 and layer 2 632).

[0127] To facilitate further selection of one or more schemes in RAN1#96bis, the schemes for multi-TRP-based URLLCs scheduled by at least a single DCI are illustrated by the following schemes for reference frequency division multiplexing (FDM) schemes 2, 2a and 2b, and reference time division multiplexing (TDM) schemes 3 and 4.

[0128] Option 2 (FDM): n (n ≤ N) within a single time slot f There are 1 TCI states with non-overlapping frequency resource allocations. Each non-overlapping frequency resource allocation is associated with one TCI state, and the same single / multiple DMRS ports are associated with all non-overlapping frequency resource allocations.

[0129] Scheme 2a (FDM): A single codeword with one RV is used for the complete resource allocation. From the UE's perspective, a common RB mapping (such as the codeword-to-layer mapping in version 15) is applied to the complete resource allocation.

[0130] Scheme 2b (FDM): A single codeword with one RV is used for each non-overlapping frequency resource allocation. The RV corresponding to each non-overlapping frequency resource allocation can be the same or different. It is possible to discuss applying different MCS / modulation orders for different non-overlapping frequency resource allocations.

[0131] We can also discuss the details of the FDM 2a / 2b frequency resource allocation mechanism regarding allocation granularity and time-domain allocation.

[0132] Scheme 3 (TDM): n (n ≤ Nt1) TCI states within a single timeslot, with non-overlapping time resource allocation. Each transmission opportunity in the TB has one TCI and one RV, with time granularity at the micro-timeslot level. All (one or more) transmission opportunities within a timeslot use a common MCS with the same single or multiple DMRS ports. RV / TCI states can be the same or different between transmission opportunities. FFS channel estimation interpolation is performed across micro-timeslots with the same TCI index.

[0133] Scheme 4 (TDM): n (n ≤ Nt²) TCI states with K (n <= K) distinct time slots. Each transmission opportunity in the TB has one TCI and one RV. All (one or more) transmission opportunities across the K time slots use a common MCS with the same single or multiple DMRS ports. The RV / TCI states can be the same or different between transmission opportunities. FFS channel estimation interpolation is performed across time slots with the same TCI index.

[0134] Please note that URLLC schemes based on M-TRP / panel should be compared in terms of improved reliability, efficiency, and specification impact, and the number of layers supported by each TRP can be discussed.

[0135] For FDM, Schemes 2a and 2b set the number of Transport Configuration Indicator (TCI) states to 2, which, according to Scheme 2a, supports a maximum of two transport layers. For TDM, Schemes 3 and 4 also set the number of TCI states to 2. Resource allocation in the time domain supports scheduling the same number of consecutive symbols for each transmission opportunity. For Scheme 3, all transmission opportunities are implemented through the network (NW) in a single time slot, without FFS for downlink / uplink (DL / UL) handover within the time slot and without dropping.

[0136] Depending on the number of configured TCI states, the UE can receive PDSCH from up to two TRPs. Figure 7 This is a diagram of a general beam fault recovery (BFR) procedure 700, which includes four main steps. The first step is beam fault detection (BFD) 702. A list of reference signals (RS) is provided to the UE by the fault detection resources used for detecting beam faults, or, if the fault detection resources do not provide RS, the UE performs BFD 702 based on the TCI state used for PDCCH / PDSCH reception (see Section 6 of TS 38.213 and Section 8.5 of TS 38.133).

[0137] The next step is New Beam Identification (NBI) 704 (also known as Candidate New Beam Detection (CBD)). A list of CBD RSs is provided to the UE from the CandidateBeamRSList.

[0138] Steps 702 and 704 occur within UE 705. Once the new beam is identified, UE 705 sends a Beam Fault Recovery Request (BFRQ) 706 to the associated gNB 710. In response, gNB 710 sends a Beam Fault Recovery Response (BFRR) 708, and the BFR procedure 700 is completed.

[0139] like Figure 6 As shown, UE 602 receives PDSCH 610 and 612 from both TRP#1 620 and TRP#2 622, with the TRP that sends PDCCH 640 via higher-layer signaling being named TRP#1 620. Figure 8The diagram 800 shows a user equipment (UE) simultaneously receiving Physical Downlink Shared Channel (PDSCH) 610 and 612 from a first TRP (TRP#1) 620 and a second TRP (TRP#2) 622, respectively. The UE 602 receives PDSCH 610 and 612 simultaneously from TRP#1 620 and TRP#2 622 for the duration of the operation time (T_state02) 802, according to the two TCI states 810 indicated in TCI code point 820.

[0140] Figure 9 This is illustrated in Figure 900, showing the duration of the operation time used for Beam Failure Detection (BFD) 910 and Candidate New Beam Detection (CBD) 920 during the BFR process. When the duration 802 of the operation time is not greater than the required BFD evaluation time 910 and / or CBD evaluation time 920, the UE uses measurement operations and power consumption to evaluate the BFD and / or CBD associated with TRP#2 without improving performance. The UE requires the BFD evaluation time 910 (T_evaluate_BFD) and the CBD evaluation time 920 (T_evaluate_CBD), which are defined in Section 8.5.3 of 38.133 and Section 5.17 of 38.321, respectively.

[0141] According to this embodiment, the UE includes a circuitry system that receives signals from the M-TRP and performs BFRs from two or more M-TRPs by: (a) evaluating BFD and CBD for signals from at least the first TRP using the Physical Downlink Control Channel (PDCCH), and (b) skipping the evaluation of one or both of the BFD and CBD in response to one or more operating conditions. In this way, the UE reduces measurement workload and power consumption. Furthermore, the reduction in measurement workload and power consumption for the UE in the network enables flexibility in M-TRP URLLC.

[0142] To evaluate BFD for two or more M-TRPs, multiple sets of BFD reference signals (BFD-RS) can be explicitly or implicitly configured to the UE, where each set is configured for each of the multiple TRPs, i.e., one BFD-RS set per TRP. Explicitly, the BFD-RS set for each TRP can be configured as a set of periodic channel state information reference signals (CSI-RS) or synchronization signal blocks (SSBs). Implicitly, the BFD-RS set for each TRP can be implicitly configured as the quasi-cooperative positioning (QCL) reference signal for the corresponding CORESET of that TRP based on its own TCI state. Similarly, to evaluate CBD for two or more M-TRPs, multiple sets of CBD reference signals (CBD-RS) (or NBI reference signals (NBI-RS)) can be explicitly or implicitly configured for each TRP. It should be understood that these independent configurations of the BFD-RS set and / or the CBD-RS set for each TRP are applicable in all current embodiments.

[0143] By configuring an independent set of BFD-RS for each TRP, a beam fault recovery process for that specific TRP can be triggered if the set of BFD-RS from one of multiple TRPs is identified as faulty (i.e., a beam from one of multiple TRPs is identified as faulty). This can be considered partial or TRP-specific beam fault recovery. Compared to use case scenarios where the beam fault recovery process is triggered only when all sets of BFD-RS configured for all TRPs are identified as faulty (or all beams from all TRPs are identified as faulty), reducing overall beam fault recovery latency and improving multi-TRP / panel transmission efficiency is beneficial.

[0144] In addition, several other BFR parameters can be configured based on the TRP level. For example, suppose there are two operating TRPs (e.g., TRP#1 and TRP#2). Therefore, two sets of thresholds such as the BFD threshold (Q_out) and CBD threshold (Q_in), two sets of timers such as the BFD timer and BFR timer, and two sets of beam fault instance (BFI) counters and their corresponding maximum number of BFI indications (BFIIs) can be configured independently for TRP#1 and TRP#2 respectively.

[0145] Figure 10 This is a diagram of the first BFR process according to this disclosure. The first BFR process queues the duration of the operation time, such as... Figure 9 As shown. Additionally, TRP#1 620 is one of the M-TRPs that sends PDCCH 640 via higher-layer signaling.

[0146] Initially, the UE receives configuration parameter 1002 from higher-layer signaling from M-TRP (i.e., on PDCCH 640 from TRP#1 620), which includes at least an indication of the appropriate duration of the operation time (e.g., T_state02802) pointing to TRP#2 622. The appropriate duration of the operation time can be a static value of the network (e.g., T_state02 can be limited based on the duration of the operation time in TRP#1 620 plus an offset), or it can be dynamically determined by the network based on actual environmental conditions or network configuration. An example of dynamically calculating the appropriate duration of the operation time using at least DCI, MAC CE, or RRC signaling is shown in Equation 1:

[0147] T_state02 = Duration of operation time of TRP#1 – PDCCH transmission duration – offset (1)

[0148] If present, the offset can be the activation time or delay of TRP#2.

[0149] In addition, contrary to the description above, there may be another possibility: T_state02 may be configured as the operation time or the duration of the window, in which both TCI states are activated, or both TRP#1 and TRP#2 are activated.

[0150] Next, the UE performs beam fault detection and recovery of TRP#1 by performing BFD procedure 1004 and CBD procedure 1006 for TRP#1, as specified in version 15 / 16.

[0151] Specifically, in procedure 1004, the UE continuously monitors the BFD-RS set configured for TRP#1 to detect beam faults. Specifically, a beam fault indicator (BFI) can be identified when the link-level quality of all corresponding BFD-RS resources exceeds a threshold (Q_out, defined as the level at which downlink radio links cannot be reliably received, corresponding to a block error rate outage (BLER_out) in the assumed PDCCH transmission) for a certain time instance. The Physical Layer (PHY) provides the BFI indication to the Medium Access Control (MAC) layer. The BFD procedure 1004 in the MAC is indicated by a counter and timer that calculate the number of BFIIs. The timer is restarted each time a BFII is received, and the counter is reset if the timer expires. On the other hand, after detecting N_max (beamFailureInstanceMaxCount) consecutive BFIIs, the UE can declare a beam fault in TRP#1. Subsequently, procedure 1006 for CBD of TRP#1 is triggered. The UE monitors the link-level quality of a set of CBD-RS (e.g., a set of CSI-RS or SSBs) to re-establish connections. The UE measures the L1 reference signal received power (L1-RSRP) on the reference signals of multiple CBD-RS. When the measured value of L1-RSRP exceeds a predetermined value, a new beam can be identified.

[0152] The UE can skip or perform one or more evaluations of BFD and / or CBD based on the value of T_state02. If the UE determines that T_state02 is less than or equal to the time taken to evaluate BFD for TRP#2 (e.g., T_evaluate_BFD 910), Figure 9 If the UE determines that T_state02 is greater than T_evaluate_BFD, then the UE performs BFD for TRP#2 (1012). The UE then compares the duration of T_state02 with T_evaluate_CBD (920) to determine if T_state02 is less than T_evaluate_CBD (1014). If the UE determines that T_state02 is less than or equal to the time for evaluating CBD for TRP#2 (e.g., T_evaluate_CBD (920)), then the UE skips CBD (1016). If the UE determines that T_state02 is greater than T_evaluate_BFD, then the UE performs CBD (1018) for TRP#2.

[0153] When performing BFD for TRP#2, similar to TRP#1, the UE needs to detect N. maxA series of BFIIs are then performed, and it can then declare a beam fault based on the BFD-RS set of TRP#2. Subsequently, the 1018 CBD evaluation is triggered, and the UE measures link-level quality, such as the L1 reference signal received power (L1-RSRP) on the reference signal for the CBD-RS set of TRP#2. In this way, the 1012 BFD procedure of TRP#2 in the MAC layer, indicated by timers and counters, is configured independently compared to the case of TRP#1. In step 1020, during BFRQ (step 706, Figure 7 If one or more beam faults are identified for TRP#1 and / or TRP#2, the UE declares a beam fault event. For TRP#2, if the CBD is skipped, no action or no new beam information is reported due to the default behavior of no action. The UE reports the beam fault content, which includes: (a) beam fault (BF) information for TRP#1 and / or TRP#2, (b) new beam information for TRP#1 (if present), and (c) new beam information, no action, or no new beam information (if present) due to no action for TRP#2. The UE then receives BFRR 1024 from the network providing the corresponding beams from TRP#1 and / or TRP#2.

[0154] The BFRQ generated in step 1022 may include beam fault information for each faulty TRP, such as the beam fault index, TRP index, or configuration index of the corresponding TRP. The BFRQ sent in step 1022 may also include report content for TRP#1 and / or TRP#2, and is reported to the network at least via Uplink Control Information (UCI) messages, Medium Access Control Element (MAC CE) messages, or Radio Resource Control (RRC) messages.

[0155] In this way, if the UE detects a beam fault in any of the multiple TRPs (taking TRP#2 as an example), the UE can send a BFRQ to the active TRP#1. This BFRQ includes beam fault information for the faulty TRP and new beam information. The active TRP#1 can then transmit the BFRQ to the faulty TRP#2 via backhaul, as it has the latest and available uplink resources to carry the BFRQ. In other words, the BFRQ procedure for M-TRP operation should be transmitted via a link with good channel conditions. If the backhaul is ideal, i.e., assuming the backhaul delay meets the requirements or is close to zero, the BFR procedure will work well. If the backhaul is not ideal or there is no new beam information for the faulty TRP#2 reported by the UE, the active TRP#1 can decide to instruct the UE to switch from multi-TRP operation mode to single-TRP operation mode. This occurs when the backhaul delay is not suitable for the delay requirements of the BFR procedure configured by the BFR timer, or when the UE may be unable to reach the faulty TRP#2 due to complete blocking. The TRP that sends PDCCH at a higher level can be configured based on the RRC configuration. For example, assuming there are two TRPs in operation (TRP A and TRP B), with the first RRC configuration, TRP A can send PDCCH and thus becomes the primary TRP or TRP #1, while TRP B is TRP #2. Alternatively, with the second RRC configuration, TRP B can send PDCCH, in which case TRP B becomes the primary TRP or TRP #1, while TRP A is TRP #2. In this way, the flexibility of M-TRP URLLC operation is achieved.

[0156] Furthermore, multiple TRPs can operate within a carrier aggregation (CA) framework using higher-level parameters. Specifically, TRP A can operate as a primary cell (PCell) or a primary TRP, while TRP B can operate as a secondary cell (SCell) or a secondary TRP. In this way, the BFR procedure proposed in this embodiment or version 16 BFR with some enhancements can be used.

[0157] Furthermore, up to two separate scheduling request (SR) configurations, including individual PUCCH resources (i.e., one or more SR-PUCCH resources), can be assigned to send BFRQs for two TRPs, TRP#1 and TRP#2. When a common SR-PUCCH resource is assigned to both TRP#1 and TRP#2, if either TRP fails, the UE can send a BFRQ for the failed TRP to the working TRP based on that common SR-PUCCH resource. When there are two separately assigned SR-PUCCH#1 and SR-PUCCH#2 resources for TRP#1 and TRP#2 respectively, if TRP#2 fails, the UE can send a BFRQ message for TRP#2 to the working TRP#1 based on one of the assigned SR-PUCCH#1 and SR-PUCCH#2 resources. For more than two TRPs, the multiple TRPs can be divided into multiple groups, where each group can be assigned SR-PUCCH resources for sending BFRQ messages. For example, there are two sets of TRPs, where the first set includes the primary TRP (or TRP #1) and the second set includes the remaining TRPs (or secondary TRPs). Therefore, SR-PUCCH #1 and SR-PUCCH #2 resources can be assigned to the first and second sets respectively. However, as mentioned above, there can be a shared SR-PUCCH resource assigned to both sets for sending BFRQ information. This can depend on pre-configured rules in the network implementation or specification.

[0158] like Figure 8 As indicated in the diagram, the UE simultaneously receives independent PDSCH 610 from TRP#1 and independent PDSCH 612 from TRP#2 during the duration of T_state02. Figure 11 This is a diagram illustrating the second BFR process according to this disclosure. Initially, network configuration parameter 1102 is used to send PDSCH from up to two TRPs (e.g., TRP#1 and TRP#2). Figure 10 As shown, the UE will always execute both BFD and CBD for TRP#1. To help the UE save power, the network determines whether the UE should execute one or both of BFD and CBD for TRP#2 and sends an explicit instruction to the UE.

[0159] The network determines whether the UE should perform one or both of the BFD and CBD for TRP#2 by first determining whether T_state02 is less than or equal to T_evaluate_BFD. If T_state02 is greater than T_evaluate_BFD, the network sets parameter BFDTRP2 to enabled, indicating that the UE will perform normal BFD / BFR for TRP#2. If T_state02 is less than or equal to T_evaluate_BFD, the network sets parameter BFDTRP2 to disabled, indicating that the UE will not perform either BFD or CBD for TRP#2.

[0160] The network then determines whether T_state02 is less than or equal to T_evaluate_CBD. If T_state02 is greater than T_evaluate_CBD, the network sets the parameter CBDTRP2 to enabled (1112), instructing the UE to perform normal CBD for TRP#2. If T_state02 is less than or equal to T_evaluate_CBD, the network sets the parameter CBDTRP2 to disabled (1114), instructing the UE not to perform CBD for TRP#2 (1110).

[0161] The decision criteria for steps 1104 and 1110 depend on the gNB implementation and other criteria may be used. The network then sends parameters BFDTRP2 and CBDTRP2, and the UE receives parameters BFDTRP2 and CBDTRP2 in step 1116. The values ​​of BFDTRP2 and CBDTRP2 can be configured and updated using at least DCI, MAC CE, or RRC signaling.

[0162] Alternatively, BFD and / or CBD parameters can be implicitly configured to the UE by interpreting one or more indications used to configure the sets of BFD-RS and / or NBI-RS. Here, for example, it is assumed that two sets of BFD-RS and two sets of CBD-RS are configured for TRP#1 and TRP#2. The UE implicitly understands that it needs to perform BFD and CBD evaluations for both TRP#1 and TRP#2.

[0163] Next, similar to BFD procedure 1004 and CBD procedure 1006, the UE performs beam fault detection and recovery for TPR#1 by executing BFD 1118 for TRP#1 and CBD 1120 for TRP#1, as specified in version 15 / 16. The UE performs beam fault detection and recovery for TPR#2 in response to the values ​​of BFDTRP2 1122 and CBDTRP2 1124. In step 1122, if the value of BFDTRP2 is "disabled", the BFD action for TRP#2 is not performed; otherwise, the BFD for TRP#2 is performed. In step 1124, if the value of CBDTRP2 is "disabled", the CBD action for TRP#2 is not performed; otherwise, the CBD for TRP#2 is performed.

[0164] During BFRQ 1126, if one or more beam faults are identified for TRP#1 and / or TRP#2, the UE declares a BF event. The UE reports BF content, which includes BF information for TRP#1 and / or TRP#2, new beam information for TRP#1 (if present) and / or new beam information for TRP#2, no action or no new beam information due to no action (if present). Finally, in step 1128, the network generates and sends a BFRR, which includes the corresponding beam information from TRP#1 and / or TRP#2.

[0165] In this way, the network reduces the number of reference signals (RS) used by the UE because no BFD and / or CBD RS are configured and because T_state02 is not sent to the UE. Furthermore, the UE reduces measurement workload and power consumption.

[0166] because Figure 11 The operation involves determining a network explicit indication for a TRP. Based on certain conditions of the described network explicit indication, this can be extended to more than two TRPs (such as BFDTRP (disabled / enabled) and / or CBDTRP (disabled / enabled)). Each TRP can be determined independently and sent to the UE for use with the corresponding TRP. Alternatively, a common BFDTRP value (i.e., disabled or enabled) and / or a common CBDTRP value (i.e., disabled or enabled) can be indicated for all TRPs respectively.

[0167] According to this disclosure, another operational condition that allows the UE to reduce measurement workload and power consumption is to define a new timer value (i.e., the active duration of the operation time, T_state02) for each individual TRP. The new timer is configured to the UE. In this way, the TRP is activated to communicate with the UE via MAC CE activated through the TCI state, and deactivated when the UE receives the TCI state to deactivate the MAC CE or when the timer expires. The timer value is indicated to the UE using at least DCI (for each TCI state), MAC CE, or RRC signaling.

[0168] Since BFD and CBD are always performed for TRP#1, the timer value for TRP#1 is configured as a symbolic value, such as infinity, so there is no timer-based deactivation. For TRP#2, the timer value (T_state02) is configured as a finite value (i.e., TRP#2 is activated on demand). Because the timer value is finite, the evaluation of BFD / CBD for TRP#2 can be skipped as follows: if T_state02 ≤ T_evaluate_BFD, the UE skips BFD and CBD; and if T_state02 > T_evaluate_BFD and T_state02 ≤ T_evaluate_CBD, the UE performs BFD and skips CBD.

[0169] If a beam fault in TRP#2 is identified, a beam fault in TRP#2 is reported, and since the default behavior is no action, no action or new beam information is reported. This further enhances the flexibility of M-TRP URLLC operation and reduces measurement workload and power consumption from the UE. Furthermore, explicit deactivation of TRP#2 (i.e., TCI state deactivation MACCE) is not necessary, as it occurs in response to timer expiration.

[0170] The network is enabled to support N max A TRP transmission utilizing a single DCI, where N max This is a (pre)configured value in the network specification. For advanced solutions, based on N... UE The flexible value skips the evaluation of BFD and CBD, where N UE N is the maximum number of TRPs that a UE can associate with. UE The value is indicated by at least DCI, MAC CE, or RRC signaling.

[0171] If N max > N UE Then skip targeting (N) max - N UE The evaluation of BFD and CBD in TRP. UEThe list of values ​​can be selected using configured rules, such as a list of TRPs with the strongest RSRP, ascending / descending indexes, or other rules. Because N UE The setting value depends on the UE's capabilities, therefore N UE The value is flexible, which enables flexibility in M-TRP URLLC operation and reduces measurement work and power consumption from the UE.

[0172] For another advanced solution, based on N min The (pre)fixed value skips the evaluation of BFD and CBD, where N min This is the number of TRPs that the UE needs to evaluate. If N max > N min Then skip targeting (N) max - N min The evaluation of BFD and CBD in TRP. min The list can be selected using (pre)configured rules, such as a list of TRPs with the strongest RSRP, ascending / descending indexes, or other rules. This setting N min The value-based approach provides consistency across the entire network. Furthermore, it reduces the BFD measurement workload for the UE, as it only needs to be applied to N. min A TPR assessment of BFD and CBD.

[0173] It should be noted that, although Figure 10 and Figure 11 The flowcharts and accompanying discussions, along with the timer configuration, address the two-TRP scenario. However, the proposed methods are directly applicable to the N-TRP scenario, namely T_stateN, BFDTPRN, and CBDTRPN, to support N TRP URLLC transmissions utilizing a single DCI. The value of N can be (pre)configured or flexibly indicated by at least the use of DCI, MAC CE, or RRC signaling, depending on the UE's capabilities.

[0174] Furthermore, while the discussion here focuses on single-DCI-based M-TRP transmission scenarios, the methods discussed can be adapted to multi-DCI-based M-TRP transmission scenarios with some modifications. Specifically, the evaluation of BFD and / or CBD for each individual TRP can be skipped based on certain conditions, either one or a combination of the following: (a) the operating time duration of each individual TRP, (b) explicit network indication, (c) timer configuration (activation duration of each individual TRP), (d) UE capability, and (e) the minimum number of TRPs.

[0175] Therefore, it can be seen that the exemplary embodiments provide a variety of structures to achieve flexibility in M-TRP URLLC operation and reduce measurement work and power consumption from the UE.

[0176] This disclosure can be implemented through software, hardware, or a combination of software and hardware. Each functional block used in the description of each of the above embodiments can be implemented, in part or in whole, through a large-scale integration (LSI) such as an integrated circuit, and each process described in each embodiment can be controlled, in part or in whole, by the same LSI or a combination of LSIs. An LSI can be formed as a standalone integrated circuit chip, or it can be formed as a chip to include some or all of the functional blocks. An LSI may include data inputs and outputs coupled thereto. An LSI may be referred to as an integrated circuit (IC), system LSI, super LSI, or extremely large LSI, depending on its degree of integration. However, the technology for implementing an integrated circuit is not limited to LSIs and can be implemented using dedicated circuitry, general-purpose processors, or special-purpose processors. Furthermore, a field-programmable gate array (FPGA) that can be programmed after the LSI is manufactured, or a reconfigurable processor in which the connection and arrangement of circuit cells disposed within the LSI can be reconfigured, can be used. This disclosure can be implemented as digital or analog processing. If future integrated circuit technology replaces LSIs due to advancements in semiconductor technology or other derivative technologies, functional blocks can be integrated using future integrated circuit technologies. Biotechnology can also be applied.

[0177] This disclosure can be implemented by any kind of communication-functional device, apparatus, or system referred to as a communication apparatus. A communication apparatus may include a transceiver and a processing / control circuitry system. A transceiver may include and / or act as both a receiver and a transmitter. A transceiver acting as both a transmitter and a receiver may include a radio frequency (RF) module (which includes amplifiers, RF modulators / demodulators, etc.) and one or more amplifiers, RF modulators / demodulators, etc., and one or more antennas. The processing / control circuitry system may include a power management circuitry system, which may include a dedicated circuitry system, a processor, and instructions for power management control as firmware or stored in memory coupled to the processor.

[0178] Some non-limiting examples of such communication devices include telephones (e.g., cellular phones, smartphones), tablets, personal computers (PCs) (e.g., laptops, desktops, netbooks), cameras (e.g., digital cameras / camcorders), digital players (e.g., digital audio / video players), wearable devices (e.g., wearable cameras, smartwatches, tracking devices), game consoles, digital book readers, remote care / telemedicine (remote health and medical) devices, and vehicles that provide communication capabilities (e.g., cars, airplanes, ships) and various combinations thereof.

[0179] Communication devices are not limited to portable or mobile devices, and may also include any type of non-portable or fixed device, equipment, or system, such as smart home devices (e.g., appliances, lighting, smart meters, control panels), vending machines, and any other "things" in a "Internet of Things (IoT)" network. Communication may include exchanging data via, for example, cellular systems, wireless LAN systems, satellite systems, and various combinations thereof.

[0180] The communication device may include a device such as a controller or sensor coupled to a communication device that performs the communication functions described in this disclosure. For example, the communication device may include a controller or sensor that generates control signals or data signals used by the communication device performing the communication functions of the communication device.

[0181] The communication device may also include infrastructure such as base stations, access points, and any other device, equipment, or system that communicates with or controls the device, such as the device in the non-limiting examples provided herein.

[0182] While exemplary embodiments have been presented in the foregoing detailed descriptions of the invention, it should be understood that numerous variations exist. It should also be understood that the exemplary embodiments are merely examples and are not intended to limit the scope, applicability, operation, or configuration of this disclosure in any way. Rather, the foregoing detailed descriptions will provide those skilled in the art with a convenient roadmap for implementing the exemplary embodiments, and it should be understood that various changes can be made to the functionality and arrangement of the network and / or UE transceiver apparatus described in the exemplary embodiments without departing from the scope of this disclosure as set forth in the appended claims.

[0183] 1. A transceiver device, comprising:

[0184] A transceiver that receives signals from multiple transmit and receive points (M-TRPs) in the network, at least on the Physical Downlink Shared Channel (PDSCH); and

[0185] A circuit system that performs beam fault recovery (BFR) by evaluating beam fault detection (BFD) and candidate new beam detection (CBD) for signals from a first M-TRP in the M-TRP, wherein the signals from the first M-TRP include signals received on the physical downlink control channel (PDCCH), and wherein the circuit system determines, in response to one or more conditions, to skip the evaluation of one or both of BFD and CBD for one or more additional M-TRPs in the M-TRP.

[0186] 2. The transceiver device according to Clause 1, wherein the one or more conditions include the duration of the operation time of the one or more additional M-TRPs in the M-TRP, determined by the duration of the operation time of the circuit system in response to the operation time for performing BFR for signals from the one or more additional M-TRPs in the M-TRPs.

[0187] 3. The transceiver apparatus according to Clause 2, wherein the duration of the operation time of the one or more additional M-TRPs in the M-TRP is indicated from one of the M-TRPs by using at least one of a Downlink Control Information (DCI) message, a Medium Access Control Layer Control Element (MAC CE) message, or a Radio Resource Control (RRC) message.

[0188] 4. The transceiver device according to Clause 2, wherein the one or more conditions include the duration of the operation time of the one or more additional M-TRPs in the M-TRP determined in response to the duration and offset value of the operation time of the first M-TRP performing the BFR.

[0189] 5. The transceiver device according to Clause 4, wherein the one or more conditions include the duration of the operating time of the one or more additional M-TRPs in the M-TRP, which is further determined by the circuit system in response to the PDCCH transmission time.

[0190] 6. The transceiver according to any one of clauses 2 to 5, wherein the circuitry skips the evaluation of both BFD and CBD for the one or more additional M-TRPs in the M-TRP in response to the duration of the operation time not being greater than the evaluation time of BFD.

[0191] 7. The transceiver device according to any one of clauses 2 to 5, wherein the circuit system skips the CBD evaluation and performs the BFD evaluation for the one or more additional M-TRPs in the M-TRP in response to the duration of the operation time being greater than the evaluation time of BFD and not greater than the evaluation time of CBD.

[0192] 8. The transceiver apparatus according to any one of the preceding clauses, wherein the transceiver declares a beam failure event and sends a beam failure recovery request (BFRQ) to one or more M-TRPs in the M-TRPs, and wherein the BFRQ identifies one or more beam failure (BF) events and reports content including BF information and CBD information to one or more M-TRPs in the M-TRPs, wherein for each M-TRP, the BF information includes a beam failure index, a TRP index, or a configuration index, and the CBD information includes the corresponding new beam information when the new beam information exists and includes default information when the new beam information does not exist.

[0193] 9. The transceiver apparatus according to any one of the preceding clauses, wherein the circuitry declares a beam failure event and generates a report of a beam failure for one or more of the M-TRPs, and wherein the transceiver transmits the report to the network via at least one of an uplink control information (UCI) message, a medium access control layer control element (MAC CE) message, or a radio resource control (RRC) message.

[0194] 10. The transceiver apparatus according to Clause 9, wherein the report content generated by the circuit system includes beam fault information and CBD information for one or more of the additional M-TRPs in the M-TRP when identified, the CBD information including the new beam information when new beam information exists for the first M-TRP in the M-TRP and including default information when no new beam information exists for the one or more additional M-TRPs in the M-TRP.

[0195] 11. The transceiver device according to any one of the preceding clauses, wherein the one or more conditions further include the duration of the operating time of each individual TRP in the M-TRP.

[0196] 12. The transceiver device according to Clause 1, wherein the one or more conditions include information received by the transceiver device.

[0197] 13. The transceiver apparatus according to Clause 12, wherein the information is indicated by using at least one of a downlink control information (DCI) message, a medium access control layer control element (MAC CE) message, or a radio resource control (RRC) message.

[0198] 14. The transceiver device according to Clause 12 or Clause 13, wherein the information includes BFD parameters and / or CBD parameters corresponding to one or more of the additional M-TRPs in the M-TRP, and wherein the circuitry skips BFD evaluation in response to the BFD parameters corresponding to the one or more M-TRPs in the M-TRP and / or skips CBD evaluation in response to the CBD parameters corresponding to the one or more additional M-TRPs in the M-TRP.

[0199] 15. The transceiver according to Clause 14, wherein the one or more conditions include not receiving reference signals for BFD and / or CBD for the one or more additional M-TRPs in the additional M-TRPs in the M-TRP, but receiving BFD parameters and / or CBD parameters.

[0200] 16. The transceiver device according to Clause 14 or Clause 15, wherein either or both of the BFD parameter and the CBD parameter are indicated independently for each of the M-TRPs.

[0201] 17. The transceiver device according to Clause 14 or Clause 15, wherein either or both of the BFD parameter and the CBD parameter are common to all M-TRPs in the M-TRP.

[0202] 18. The transceiver device according to Clause 12 or Clause 13, wherein the information includes a timer value corresponding to one of the one or more additional M-TRPs in the M-TRP, and wherein the circuitry responds to the timer value corresponding to the one of the M-TRPs to skip the evaluation of BFD and / or CBD for the one of the one or more additional M-TRPs in the M-TRP.

[0203] 19. The transceiver device according to Clause 18, wherein the timer value includes a finite value, and wherein the transceiver device is deactivated when the timer expires.

[0204] 20. A transceiver device according to Clause 12 or Clause 13, wherein the information includes a value corresponding to the maximum number of TRPs that the transceiver device is capable of associating with, and wherein the circuitry, in response to the value corresponding to the maximum number of TRPs that the transceiver device is capable of associating with, skips the evaluation of BFD and / or CBD for one or more of the M-TRPs.

[0205] 21. The system according to Clause 12 or Clause 13, wherein the information includes a value corresponding to the number of TRPs that need to be evaluated by the transceiver, and wherein the circuit system, in response to the value corresponding to the number of TRPs that need to be evaluated by the transceiver, skips the evaluation of BFD and / or CBD for one or more of the M-TRPs.

[0206] 22. The transceiver apparatus according to Clause 20 or Clause 21, wherein the list of M-TRPs evaluated by the transceiver apparatus is selected by configuration rules, such as a list of M-TRPs with the strongest RSRP, an ascending / descending index, or depending on the implementation of the transceiver apparatus.

[0207] 23. The transceiver device according to any one of the preceding clauses, wherein the circuitry is configured according to the radio resource control (RRC) of the network to identify the first M-TRP in the M-TRP in response to a signal received on the PDCCH.

[0208] 24. The transceiver apparatus according to any one of the preceding clauses, wherein the transceiver simultaneously receives PDSCH from two or more M-TRPs, wherein the PDSCH received from each of the two or more M-TRPs is received at a different layer.

[0209] 25. The transceiver according to any one of the preceding clauses, wherein the transceiver receives signals including M-TRP transmissions based on a single DCI.

[0210] 26. The transceiver according to any one of clauses 1 to 24, wherein the transceiver receives signals including M-TRP transmissions based on multiple DCI.

[0211] 27. A system comprising:

[0212] A network comprising multiple transmit and receive points (M-TRPs) for transmitting and receiving signals; and

[0213] Transceiver device, the transceiver device comprising:

[0214] A transceiver that receives signals from one or more of the M-TRPs; and

[0215] A circuit system that performs beam fault recovery (BFR) by evaluating beam fault detection (BFD) and candidate new beam detection (CBD) for signals from a first M-TRP in the M-TRP, wherein the network generates one or more values ​​for performing BFD and CBD for one or more M-TRPs in the M-TRP and sends the one or more values ​​to the transceiver, and wherein the circuit system skips the evaluation of one or both of BFD and CBD for one or more additional M-TRPs in the M-TRP in response to one of the one or more values ​​corresponding to the one or more additional M-TRPs in the M-TRP.

[0216] 28. The system according to Clause 27, wherein the one or more values ​​corresponding to the one or more M-TRPs in the M-TRP can be indicated by using at least one of a Downlink Control Information (DCI) message, a Medium Access Control Layer Control Element (MAC CE) message, or a Radio Resource Control (RRC) message.

[0217] 29. The system according to Clause 27 or Clause 28, wherein the network responds to a network implementation to generate the one or more values ​​to perform BFD and CBD for the one or more M-TRPs in the M-TRP.

[0218] 30. The system apparatus according to any one of Clauses 27 to 29, wherein the transceiver receives signals from the one or more M-TRPs as a single DCI-based M-TRP transmission.

[0219] 31. The system apparatus according to any one of Clauses 27 to 29, wherein the transceiver receives signals from the one or more M-TRPs as a multi-DCI-based M-TRP transmission.

[0220] 32. The system according to Clause 31, wherein the one or more values ​​include information of each individual TRP received by the transceiver of the transceiver or the duration of the operation time of each individual TRP.

Claims

1. A transceiver device, comprising: A transceiver that receives a first set of beam failure detection (BFD) reference signal configurations, a second set of BFD reference signal configurations, a first set of candidate new beam detection (CBD) reference signal configurations, and a second set of CBD reference signal configurations. as well as The circuit performs a first BFD associated with a first transmit / receive point (TRP) based on a first set of BFD reference signals, performs a second BFD associated with a second TRP based on a second set of BFD reference signals, and performs at least one of the following: a first CBD associated with a first TRP based on a first set of CBD reference signals, or a second CBD associated with a second TRP based on a second set of CBD reference signals.

2. The transceiver device according to claim 1, wherein, The first set of BFD reference signal configurations, the second set of BFD reference signal configurations, the first set of CBD reference signal configurations, and the second set of CBD reference signal configurations are indicated by a Medium Access Control (MAC) element (CE) or Radio Resource Control (RRC) signaling.

3. The transceiver device according to claim 1, wherein, The first set of BFD reference signal configurations and the second set of BFD reference signal configurations, and / or the first set of CBD reference signal configurations and the second set of CBD reference signal configurations, include the configuration of Channel State Information (CSI) reference signals and / or the configuration of Synchronization Signal Blocks (SSBs).

4. The transceiver device according to claim 1, wherein, The transceiver reports content to the base station, the content including at least one result of the first BFD and at least one result of the second BFD.

5. The transceiver device according to claim 1, wherein, Whether to execute the first BFD of the first set configured based on the BFD reference signal and the second BFD of the second set configured based on the BFD reference signal is determined by the transmission configuration indication (TCI) status of the downlink control information (DCI).

6. The transceiver device according to claim 1, wherein, The transceiver reports content to the base station, the content including a result of the first BFD related to a first set of BFD reference signal configurations or a result of the second BFD related to a second set of BFD reference signal configurations, and a result of the first CBD related to a first set of CBD reference signal configurations or a result of the second CBD related to a second set of CBD reference signal configurations.

7. A communication method executed by a communication device, comprising: A first set of BFD reference signal configurations for receive beam failure detection, a second set of BFD reference signal configurations, a first set of CBD reference signal configurations for candidate new beam detection, and a second set of CBD reference signal configurations. as well as A first BFD associated with a first transmit / receive point (TRP) is executed based on a first set of BFD reference signals, a second BFD associated with a second TRP is executed based on a second set of BFD reference signals, and a first CBD is executed based on a first set of CBD reference signals or a second CBD is executed based on a second set of CBD reference signals.

8. The communication method according to claim 7, wherein, The first set of BFD reference signal configurations, the second set of BFD reference signal configurations, the first set of CBD reference signal configurations, and the second set of CBD reference signal configurations are indicated by a Medium Access Control (MAC) element (CE) or Radio Resource Control (RRC) signaling.

9. The communication method according to claim 7, wherein, The first set of BFD reference signal configurations and the second set of BFD reference signal configurations, and / or the first set of CBD reference signal configurations and the second set of CBD reference signal configurations, include the configuration of Channel State Information (CSI) reference signals and / or the configuration of Synchronization Signal Blocks (SSBs).

10. The communication method according to claim 7, further comprising: The content to be sent includes at least one result of the first BFD and at least one result of the second BFD.

11. The communication method according to claim 7, further comprising: The Transmission Configuration Indicator (TCI) state based on the Downlink Control Information (DCI) determines whether to execute the first BFD based on a first set of BFD reference signal configurations and the second BFD based on a second set of BFD reference signal configurations.

12. The communication method according to claim 7, comprising: The content being transmitted includes a result of a first BFD associated with a first set of BFD reference signal configurations or a result of a second BFD associated with a second set of BFD reference signal configurations, and a result of a first CBD associated with a first set of CBD reference signal configurations or a result of a second CBD associated with a second set of CBD reference signal configurations.

Images