Beam Interference Recovery for M-TRP URLLC Transmission Based on a Single DCI

Abstract

A plurality of systems are provided to realize flexibility in M-TRP URLLC operation and to reduce measurement effort and power consumption of transmitting and receiving devices such as UEs. During operation, the transmitting and receiving unit receives signals from multiple transmitting and receiving points (M-TRPs) within the network at least on the PDSCH. During operation, the circuit performs beam fault recovery (BFR) by evaluating beam fault detection (BFD) and new beam candidate detection (CBD) on the signal from the first TRP among the M-TRPs. The signal from the first TRP among the M-TRPs includes the signal received on the PDCCH, and the circuit determines to skip the evaluation of one or both of the BFD and the CBD for one or more additional TRPs among the M-TRPs according to one or more conditions.

Description

Technology Field

[0001] The present invention relates to a communication device, and in particular, to a mechanism for beam interference recovery for such a communication device. Background Technology

[0002] In modern society, communication devices are widely distributed in various forms. Examples include telephones, tablets, computers, cameras, digital audio / video players, wearable devices, game consoles, telehealth and telemedicine devices, transportation vehicles equipped with communication functions, and combinations of the various devices mentioned above. Communication includes data communication by cellular systems, wireless LAN (local area network) systems, communication satellite systems, etc., as well as data communication by combinations thereof.

[0003] As communication generations advance (e.g., 5G NR: 5G new Radio), ultra-reliable and low-latency communications (URLLC) are required for most applications (e.g., Augmented Reality / Virtual Reality (AR), e-health, e-safety, and mission-critical applications). URLLC meets stringent performance requirements regarding throughput, latency, and availability, and is envisioned as one of the key technologies for realizing future vertical applications, such as wireless control of industrial production and manufacturing processes, remote medical surgery, power distribution automation in smart grids, and traffic safety. Furthermore, 5G NR is equipped with multiple transmission and reception points (M-TRP) to improve reliability, coverage, and capacity performance through flexible deployment scenarios. For example, user equipment (UE) (i.e., communication device) is assumed to access a network consisting of M-TRP (e.g., macro cell, small cell, pico cell, femto cell, remote radio head, relay node) in order to respond to the rapid increase in mobile data traffic in 5G and to expand coverage. The problem to be solved

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

[0005] Therefore, there is a need for communication devices and systems that save power without losing the reliability of URLLC communication during recovery from beam interference conditions. In addition, other desirable features and characteristics will become apparent from the following detailed description and appended claims, together with the attached drawings and background. means of solving the problem

[0006] Non-limiting and exemplary embodiments of the present disclosure contribute to providing multiple systems that realize flexibility in the operation of M-TRP URLLC (multiple transmission and reception point ultra-reliable low-latency communication) and reduce measurement effort or power consumption in transmitting and receiving devices such as UEs.

[0007] In one embodiment, the technology disclosed herein features a transceiver having a transceiver and a circuit. The transceiver receives a signal from multiple transmission and reception points (M-TRPs) within a network, at least on a physical downlink shared channel (PDSCH), during operation. The circuit performs beam failure recovery (BFR) by evaluating a beam failure detection (BFD) and a candidate new beam detection (CBD) on a signal from a first TRP among the M-TRPs during operation. The signal from the first TRP among the M-TRPs includes a signal received on a physical downlink control channel (PDCCH), and the circuit determines, based on one or more conditions, to skip the evaluation of one or both of the BFD and the CBD for one or more additional TRPs among the M-TRPs.

[0008] In addition, comprehensive or specific modes thereof may be realized as a system, method, integrated circuit, computer program, or recording medium, or as any combination of a system, device, method, integrated circuit, computer program, and recording medium.

[0009] Additional advantages and effects in one embodiment of the present disclosure become apparent from the specification and drawings. These advantages and / or effects are provided by each of the features described in the several embodiments, specification, and drawings, but not all of them are required to be provided to obtain one or more of the same features. Brief explanation of the drawing

[0010] In the following, exemplary embodiments are described in more detail with reference to the attached drawings. Figure 1 is a figure showing an example of the architecture of a 3GPP NR system. Figure 2 is a schematic diagram showing the functional split between NG-RAN and 5GC. Figure 3 is a sequence diagram for the radio resource control (RRC) connection setup / reset procedure. Figure 4 is a schematic diagram showing usage scenarios for enhanced Mobile Broadband (eMBB), massive Machine Type Communications (mMTC), and Ultra Reliable and Low Latency Communications (URLLC). Figure 5 is a block diagram showing an example of a 5G system architecture for a non-roaming scenario. Figure 6 is a figure showing a multiple transmit / receive point (M-TRP) ultra-reliable low-latency (URLLC) system based on one downlink control information (DCI). Figure 7 is a diagram showing a typical beam failure recovery (BFR) procedure. FIG. 8 is a diagram in which a user terminal (UE: user equipment) receives a PDSCH (physical downlink shared channel) simultaneously from a first TRP and a second TRP. Figure 9 is a figure showing the operating time lengths of beam failure detection (BFD) and candidate new beam detection (CBD) in the BFR procedure. FIG. 10 is a figure showing the first BFR procedure relating to the present disclosure. FIG. 11 is a figure showing the second BFR procedure relating to the present disclosure. A person skilled in the art can understand that the elements in the drawing are shown simply and clearly, and that they are not necessarily drawn to a fixed scale. Specific details for implementing the invention

[0011] The following detailed description is by nature merely illustrative and is not intended to limit exemplary embodiments or the application and use of exemplary embodiments. Furthermore, there is no intention to be restricted by any theory presented in the background or the following detailed description. The present disclosure is intended to provide exemplary embodiments of a communication device and a communication system that save power without losing the reliability of URLLC (ultra-reliable and low-latency communications) communication during recovery from beam interference conditions, thereby enabling the reduction of measurement effort and power consumption during BFR while maintaining ultra-reliable and low-latency communication.

[0012] <5G NR System Architecture and Protocol Stack>

[0013] The 3rd Generation Partnership Project (3GPP) is being introduced in the next release of 5th generation cellular technology (also simply called 5G), which includes the development of New Radio Access (NR) technology operating in a frequency range up to 100 GHz. The first version of the 5G standard was completed at the end of 2017, and the implementation and commercial deployment of smartphones compliant with the 5G NR standard could proceed.

[0014] Referring to FIG. 1, in particular, the overall system architecture envisions an NG-RAN (Next Generation-Radio Access Network) (102) equipped with gNBs (gNodeBs) (104). The gNBs provide the UE-side endpoints of the NG radio access user planes (SDAP / PDCP / RLC / MAC / PHY) and Radio Resource Control (RRC) protocols. The gNBs (104) are connected to each other via Xn interfaces (106). Additionally, the gNB is connected to the Next Generation Core (NGC) (112) via the Next Generation (NG) interface, more specifically to the Access and Mobility Management Function (AMF) (108) (e.g., a specific core entity running the AMF) via the NG-C interface (112a), and to the User Plane Function (UPF) (110) (e.g., a specific core entity running the UPF) via the NG-U interface (112b). The NG-RAN architecture (100) is shown in FIG. 1 (see, for example, Section 4 of 3GPP TS 38.300 v15.6.0).

[0015] The user plane protocol stack of NR (see, for example, Section 4.4.1 of 3GPP TS 38.300) includes the PDCP (Packet Data Convergence Protocol; see Section 6.4 of TS 38.300) sublayer, RLC (Radio Link Control; see Section 6.3 of TS 38.300) sublayer, and MAC (Medium Access Control; see Section 6.2 of TS 38.300) sublayer, which are terminated at the network side in the gNB. In addition, a new access layer (AS: Access Stratum) sublayer (SDAP: Service Data Adaptation Protocol) is introduced above PDCP (see, for example, sub-clause 6.5 of 3GPP TS 38.300). Furthermore, a control plane protocol stack is also defined in NR (see, for example, Section 4.4.2 of TS 38.300). An overview of Layer 2 functions is described in sub-clause 6 of TS 38.300. The functions of the PDCP sublayer, RLC sublayer, and MAC sublayer are described in sections 6.4, 6.3, and 6.2 of TS 38.300, respectively. The functions of the RRC layer are listed in sub-clause 7 of TS 38.300.

[0016] For example, the MAC layer is responsible for scheduling and scheduling-related functions, including the multiplexing of logical channels and the processing of various numerologies.

[0017] The physical layer (PHY) is responsible for, for example, encoding, PHY HARQ processing, modulation, multi-antenna processing, and the placement of signals into appropriate physical time-frequency resources. It also performs the placement of transport channels into 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 the transmission of a specific transport channel, and each transport channel is placed into a corresponding physical channel. For example, physical channels become PRACH (Physical Random Access Channel), PUSCH (Physical Uplink Shared Channel), and PUCCH (Physical Uplink Control Channel) in the uplink, and PDSCH (Physical Downlink Shared Channel), PDCCH (Physical Downlink Control Channel), and PBCH (Physical Broadcast Channel) in the downlink.

[0018] NR use cases and deployment scenarios include eMBB (enhanced Mobile Broadband), URLLC (Ultra-Reliable Low-Latency Communications), and mMTC (massive Machine Type Communication), which have various requirements regarding data rates, latency, and coverage. For example, eMBB requires support for peak data rates (downstream 20Gbps, upstream 10Gbps) and user-experienced data rates approximately three times higher than those provided by IMT-Advanced. On the other hand, URLLC has stricter requirements for ultra-low latency (user plane latency is 0.5ms for both UL and DL) and high reliability (1-10 within 1ms). -5...is becoming excessive. Finally, mMTC preferably requires high connection density (1 million units per square kilometer in urban environments), wide coverage in harsh environments, and ultra-long lifespan batteries (15 years) for low-cost devices.

[0019] Therefore, OFDM numerology suitable for one use case (e.g., subcarrier spacing, OFDM symbol length, traversal prefix (CP) length, number of symbols per scheduling interval) may not be effective for another use case. For example, low-latency services may preferably require a shorter symbol length (and thus a larger subcarrier spacing) and / or fewer symbols per scheduling interval (in other words, TTI) than mMTC services. Additionally, in deployment scenarios with a large channel delay spread, it may preferably require a longer CP length than in scenarios with a small delay spread. To maintain the same CP overhead, the subcarrier spacing needs to be appropriately optimized. NR may support multiple values ​​for subcarrier spacing. Accordingly, subcarrier spacings of 15 kHz, 30 kHz, 60 kHz, ... are currently being considered. Symbol length T u The subcarrier spacing Δf is given by the equation Δf=1 / T u It is directly related by. As with LTE systems, the term "resource element" can be used to denote the smallest resource unit consisting of one subcarrier for the length of one OFDM / SC-FDMA symbol.

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

[0021] <NG-RAN과 5GC의 사이의 기능 분할>

[0022] (Control signal)

[0023] In the present disclosure, the downstream control signal (information) related to the present disclosure may be a signal (information) transmitted from the PDCCH of the physical layer, or a signal (information) transmitted from the MAC CE (Control Element) or RRC of the upper layer. It may also be a signal (information) that is predetermined.

[0024] The uplink control signal (information) related to the present disclosure may be a signal (information) transmitted from the PUCCH of the physical layer, or a signal (information) transmitted from the MAC CE or RRC of the upper layer. It may also be a predefined signal (information). Furthermore, it may be substituted with UCI (uplink control information), 1st stage SCI (sidelink control information), and 2nd stage SCI.

[0025] (Base station)

[0026] In the present disclosure, the base station may be a Transmission Reception Point (TRP), cluster head, access point, Remote Radio Head (RRH), eNodeB (eNB), gNodeB (gNB), Base Station (BS), Base Transceiver Station (BTS), parent machine, gateway, etc. Also, in side link communication, a terminal may be used instead of a base station. It may be a relay device that relays communication between an upper node and a terminal. It may also be a roadside device.

[0027] (Uplink / Downlink / Sidelink)

[0028] The present disclosure may be applied to any one of an uplink, a downlink, or a side link.

[0029] For example, the present disclosure may be applied to the PUSCH, PUCCH, and PRACH of the uplink, the PDSCH, PDCCH, and PBCH of the downlink, and the PSSCH (Physical Sidelink Shared Channel), PSCCH (Physical Sidelink Control Channel), and PSBCH (Physical Sidelink Broadcast Channel) of the sidelink.

[0030] In addition, PDCCH, PDSCH, PUSCH, and PUCCH are examples of a downlink control channel, a downlink data channel, an uplink data channel, and an uplink control channel. PSCCH and PSSCH are examples of a sidelink control channel and a sidelink data channel. PBCH and PSBCH are examples of notification (broadcast) channels, and PRACH is an example of a random access channel.

[0031] (Data Channel / Control Channel)

[0032] The present disclosure may be applied to either a data channel or a control channel. For example, the channels of the present disclosure may be substituted with PDSCH, PUSCH, PSSCH of the data channel and PDCCH, PUCCH, PBCH, PSCCH, PSBCH of the control channel.

[0033] (Reference signal)

[0034] In the present disclosure, the reference signal is a signal already known to both the base station and the mobile station, and may also be referred to as a Reference Signal (RS) or a pilot signal. The reference signal may be any one of DMRS, CSI-RS (Channel State Information-Reference Signal), TRS (Tracking Reference Signal), PTRS (Phase Tracking Reference Signal), CRS (Cell-specific Reference Signal), or SRS (Sounding Reference Signal).

[0035] (Time interval)

[0036] In the present disclosure, the unit of time resource is not limited to one or a combination of slots and symbols, and may be, for example, a frame, super frame, sub frame, slot, time slot sub slot, mini slot, or a symbol, OFDM (Orthogonal Frequency Division Multiplexing) symbol, SC-FDMA (Single Carrier-Frequency Division Multiplexing) symbol, or may be any other unit of time resource. Also, the number of symbols included in one slot is not limited to the number of symbols exemplified in the above-described embodiment, and may be any other number of symbols.

[0037] (Frequency band)

[0038] The present disclosure may be applied to either a license band or an unlicensed band.

[0039] (communication)

[0040] The present disclosure may be applied to any one of communication between a base station and a terminal (Uu link communication), communication between terminals (side link communication), or V2X (Vehicle to Everything) communication. For example, the channels of the present disclosure may be replaced with PSCCH, PSSCH, PSFCH (Physical Sidelink Feedback Channel), PSBCH, PDCCH, PUCCH, PDSCH, PUSCH, and PBCH.

[0041] Furthermore, the present disclosure may be applied to any one of a terrestrial network or a non-terrestrial network (NTN) using a satellite or a High Altitude Pseudo Satellite (HAPS). It may also be applied to terrestrial networks with large transmission delays relative to the symbol length or slot length, such as networks with large cell sizes or ultra-wideband transmission networks.

[0042] (Antenna port)

[0043] An antenna port refers to a logical antenna (antenna group) composed of one or more physical antennas. That is, an antenna port is not necessarily limited to referring to a single physical antenna, and may refer to an array antenna composed of multiple antennas. For example, the number of physical antennas that make up an antenna port is not specified, but is defined as the minimum unit in which a terminal can transmit a reference signal. In addition, an antenna port may be defined as the minimum unit for multiplying the weighting of a precoding vector.

[0044] FIG. 2 illustrates the functional partitioning between NG-RAN (200) and 5GC (250). The NG-RAN logical nodes are gNB or ng-eNB (210). 5GC (250) includes logical nodes of AMF (260), UPF (270), and SMF (280).

[0045] gNB and ng-eNB (210) specifically provide the following major functions.

[0046] Wireless resource management functions (212), such as wireless bearer control (214), wireless admission control (218), connection mobility control (216), and dynamic resource allocation (scheduling) (222) for UEs on both the uplink and downlink.

[0047] · Compression, encryption, and integrity protection of IP headers of data

[0048] · AMF selection upon UE attachment when routing to the AMF cannot be determined from the information provided by the UE

[0049] · Routing user plane data toward UPF

[0050] · Routing of control plane information toward the AMF

[0051] · Establishing and disconnecting the connection

[0052] · Scheduling and transmission of paging messages

[0053] · Scheduling and transmission of system notification information (sent from AMF or OAM)

[0054] ·Settings for measurement and measurement reporting for mobility and scheduling (220)

[0055] · Transport-level packet marking on the uplink

[0056] · Session Management

[0057] · Support for network slicing

[0058] · QoS flow management and deployment of data wireless bearers

[0059] · Support for UEs in RRC_INACTIVE state

[0060] · NAS message delivery function

[0061] · Wireless access network sharing

[0062] · Dual Connectivity

[0063] · Close linkage between NR and E-UTRA

[0064] The access and mobility management function (AMF) (260) provides the following key functions.

[0065] · Termination of Non-Access Stratum (NAS) signaling

[0066] ·Security of NAS signaling (262)

[0067] · Security control of the Access Stratum (AS)

[0068] · Signaling between Core Network (CN) nodes for mobility between 3GPP access networks

[0069] · Reachability of the idle mode UE (including control and execution of paging retransmission) (264)

[0070] · Registered Area Management

[0071] · Support for intra-system and inter-system mobility

[0072] · Access Authentication

[0073] · Access authorization including roaming authorization checks

[0074] · Mobility Management Control (Subscription and Policy)

[0075] · Support for network slicing

[0076] · Select Session Management Function (SMF)

[0077] In addition, the User Plane Function (UPF) provides the following key functions.

[0078] · Anchor point for mobility within / between RATs (if applicable) (272)

[0079] · External PDU session point (274) for interconnection with a data network

[0080] · Packet Routing and Transmission

[0081] · Packet inspection and enforcement of policy rules in the user plane

[0082] · Reporting of traffic usage

[0083] · Uplink classifier that supports the routing of traffic flows to a data network

[0084] · Branch point supporting multi-hom PDU sessions

[0085] · QoS processing for the user plane, such as packet filtering, gating, and UL / DL (uplink / downlink) rate enhancement

[0086] · Uplink traffic validation (placement for SDF's QoS flow)

[0087] · Downlink packet buffering and downlink data notification triggers

[0088] Finally, the session management function (SMF) (280) provides the following key functions.

[0089] · Session management (284)

[0090] · Assignment and management of IP addresses for UEs (282)

[0091] · Selection and control of UPF

[0092] · Configuration of traffic steering in User Plane Functions (UPF) to route traffic to appropriate destinations

[0093] · Enforcement of policy in the control section and QoS

[0094] · Notification of downlink data

[0095] <RRC 접속 설정 및 재설정 수순>

[0096] FIG. 3 illustrates part of the exchange between UE (310), gNB (320), and AMF (330) (5GC entity) when UE transitions from RRC_IDLE to RRC_CONNECTED in the NAS section (see TS 38.300 v15.6.0).

[0097] RRC is a high-layer signaling (protocol) used for configuring the UE and gNB. Specifically, this implementation involves the AMF (330) preparing UE context data (e.g., PDU session context, security key, UE Radio Capability, UE Security Capabilities, etc.) and transmitting it to the gNB (320) along with an Initial Context Config Request (340). Then, the gNB (320) initiates AS security with the UE (310). This operation is performed by the gNB transmitting a Security Mode Command message (342) to the UE, and the UE (310) responding to the gNB (320) with a Security Mode Complete message (344). After that, the gNB (320) transmits an RRC Reconfiguration message (346) to the UE (310), and upon receiving an RRC Reconfiguration Complete (348) from the UE (310) in response, the gNB (320) performs a reconfiguration to set up the Signaling Radio Bearer 2 (SRB 2) and the Data Radio Bearer (DRB). In the case of a signaling-only connection, the SRB 2 and DRB are not set up, so the steps related to RRC reconfiguration are omitted. Finally, the gNB (320) notifies the AMF (330) that the setup procedure is complete with an Initial Context Setup Response (350).

[0098] Accordingly, the present disclosure provides an entity of a fifth-generation core (5GC) (e.g., AMF, SMF, etc.) comprising a control circuit that establishes a next-generation (NG) connection with a gNodeB during operation, and a transmitter that transmits an initial context setting message to the gNodeB via the NG connection during operation so that a signaling radio bearer between the gNodeB and the terminal (UE) is established. Specifically, the gNodeB transmits Radio Resource Control (RRC) signaling, which includes a resource allocation setting information element, to the UE via the signaling radio bearer. Then, the UE performs uplink transmission or downlink reception based on the resource allocation setting.

[0099] IMT Usage Scenarios After 2020

[0100] FIG. 4 illustrates some of the use cases for 5G NR. In the 3rd Generation Partnership Project NR (3GPP NR), three use cases are being considered that are expected to support a wide variety of services and applications by IMT-2020. The specification for the first stage of high-speed high-capacity (eMBB) (410) has been finalized. In addition to further expanding support for eMBB (410), research on the standardization of Ultra-Reliable Low Latency (URLLC) (430) and multiple simultaneous connections (450) is also being conducted now and in the future. FIG. 4 illustrates examples of usage scenarios expected for IMT after 2020 (see, for example, FIG. 2 of ITU-R M.2083).

[0101] The use case (430) of URLLC has strict requirements for performance such as throughput, latency, and availability, and is envisioned as one of the realizations of future vertical applications such as wireless control of industrial production or manufacturing processes, remote medical surgery, power distribution automation of smart grids, and traffic safety. The ultra-high reliability of URLLC (430) is supported by specifying a technology that satisfies the requirements set by TR 38.913. In the case of NR URLLC in Release 15, the main requirement is to aim for a user plane latency of 0.5ms for UL (uplink) and 0.5ms for DL ​​(downlink). The general requirement for URLLC (430) for a single packet transmission is that when the user plane latency is 1ms, the block error rate (BLER) is 1E-5 for a packet size of 32 bytes.

[0102] From the perspective of the physical layer, there are various ways to improve reliability. Currently, to improve reliability, it is considered to define independent CQI tables for URLLC (430), a more compact DCI (downlink control information) format, and the repetition of PDCCH. However, as NR becomes more stable and advanced (regarding the main requirements of NR URLC), the range of methods considered to achieve ultra-high reliability can be expanded. Use cases specific to NR URLLC in Release 15 include augmented reality / virtual reality (AR / VR), e-health, e-safety, and mission-critical applications.

[0103] Additionally, the technical enhancements targeted by the NR URLLC (430) are the improvement of latency and the improvement of reliability. Technical enhancements for improving latency include configurable numerology, non-slot-based scheduling by flexible mapping, grant-free (configured grant) uplink, slot-level repetition of data channels, and downlink pre-emption. Pre-emption means stopping a transmission for which resources have already been allocated and using the resources that have already been allocated for another transmission that requires less latency or higher priority, which is requested later. Thus, transmissions that have already been authorized are replaced by subsequent transmissions. Pre-emption can be applied regardless of the specific service type. For example, a transmission of service type A (URLLC) may be pre-empted by a transmission of service type B (e.g., eMBB). Technical enhancements for improving reliability include a dedicated CQI / MCS table for the target BLER 1E-5.

[0104] The use case of mMTC (multiple simultaneous connections) (450) is typically characterized by a very large number of connection devices transmitting relatively small amounts of data that are not affected by delay. The devices are required to be low-cost and have a very long battery life. From the perspective of NR, using a very narrow bandwidth portion is one way to enable power saving in the UE and a long battery life.

[0105] As described above, the scope of reliability improvement in NR is expected to be wider. One of the important requirements common to all cases, and particularly required for URLLC (430) and mMTC (450), is high reliability or ultra-high reliability. To improve reliability, several mechanisms are considered from the perspective of wireless or network. Generally, there are several important areas that contribute to improving reliability. These areas include compact control channel information, data / control channel repetition, and diversity in the frequency domain, time domain, and space domain. These areas are generally applicable to improving reliability regardless of the specific communication scenario.

[0106] For NR URLLC (430), additional use cases with stricter requirements, such as factory automation, the transportation industry, and power distribution, are specified. The stricter requirements refer to high reliability (up to 10) depending on the use case. -6 Level), high availability, packet size of up to 256 bytes, and time synchronization of up to several microseconds (μs) (depending on the frequency range and short delay of about 0.5 to 1 millisecond (ms) (e.g., a delay of 0.5 ms in the target user plane) can be 1 μs or several μs).

[0107] In addition, in NR URLLC (430), several technical enhancements are identified from the perspective of the physical layer. Among these are the enhancement of the Physical Downlink Control Channel (PDCCH) regarding compact DCI, the repetition of the PDCCH, and increased monitoring of the PDCCH. Also, the enhancement of Uplink Control Information (UCI) is related to the enhancement of the Hybrid Automatic Repeat Request (HARQ) and CSI feedback. Additionally, the enhancement of PUSCH and retransmission / repetition related to mini-slot level hopping is also identified. "Mini-slot" refers to a transmission time interval (TTI) containing fewer symbols than a slot (a slot consisting of 14 symbols).

[0108] <QoS의 제어>

[0109] The 5G Quality of Service (QoS) model is based on QoS flows and supports both QoS flows requiring a guaranteed flow bit rate (GBR QoS flows) and QoS flows not requiring a guaranteed flow bit rate (non-GBR QoS flows). Therefore, at the NAS level, a QoS flow is the smallest granular distinction of QoS within a PDU session. A QoS flow is identified within a PDU session by a QoS flow ID (QFI) returned in the encapsulation header via the NG-U interface.

[0110] For each UE, 5GC establishes one or more PDU sessions. For each UE, NG-RAN establishes at least one data radio bearer (DRB) corresponding to the PDU session, and additional DRBs for the QoS flow of that PDU session may be subsequently configured, for example, as described above with reference to FIG. 3 (when they are configured depends on NG-RAN). NG-RAN places packets belonging to different PDU sessions into different DRBs. While NAS-level packet filters in the UE and 5GC associate UL packets and DL packets with QoS flows, AS-level mapping rules in the UE and NG-RAN associate UL QoS flows and DL QoS flows with DRBs.

[0111] FIG. 5 illustrates a non-roaming reference architecture for 5G NR (see TS 23.501 v16.1.0, Section 4.23). An application function (AF) (500), such as an external application server hosting a 5G service as exemplified in FIG. 4, exchanges with a 3GPP core network to provide the service. Examples include accessing a Network Exposure Function (NEF) (505) to support applications that affect traffic routing, and exchanging with a policy framework for policy control, such as QoS control (see Policy Control Function (PCF)). Based on deployment by an operator, an application function (500) that is considered trusted by the operator may exchange directly with a related network function. Application functions (500) that are not granted direct access to network functions by the operator exchange with the relevant network functions using an open framework to the outside through the NEF (505).

[0112] FIG. 5 illustrates additional functional units of a 5G architecture, namely a Network Slice Selection Function (NSSF) (510), a Network Repository Function (NRF) (515), Unified Data Management (UDM) (520), an Authentication Server Function (AUSF) (525), an Access & Mobility Management Function (AMF) (530), a Session Management Function (SMF) (535), and a Data Network (DN) (540) (services by an operator, internet access, services by a third party, etc.). All or some of the core network functions and application services may be deployed and operated in a cloud computing environment.

[0113] Accordingly, the present disclosure provides an application server (e.g., AF (500) of a 5G architecture) having a transmitter that, in operation, transmits a request including QoS requirements for at least one of URLLC, eMBB, and mMTC services to at least one of the functions of 5GC (e.g., NEF (505), AMF (530), SMF (535), PCF (545), UPF (550), etc.) to establish a PDU session including a wireless bearer between a gNodeB and a UE according to QoS requirements, and a control circuit that, in operation, executes a service using the established PDU session.

[0114] FIG. 6 illustrates an example of a multiple transmit / receive point (M-TRP) ultra-reliable low-latency (URLLC) network (600) based on one downlink control information (DCI). M-TRP transmission is used to withstand interference and improve the performance of the UE (602) at the end of the cell. In M-TRP URLLC transmission based on one DCI, the network (600) schedules PDSCH transmissions (610, 612) from multiple TRPs (i.e., TRP1 (620) and TRP2 (622)), and the PDSCH (610, 612) from different TRPs (620, 622) is transmitted at different layers (i.e., Layer 1 (630) and Layer 2 (632)).

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

[0116] Scheme 2 (FDM): n (n≤N) within a single slot with no overlap in frequency resource allocation f ) TCI states. 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.

[0117] Scheme 2a (FDM): A single codeword for a single RV is used across all resource allocations. From the UE's perspective, a common RB mapping (a codeword for layer mappings such as Rel-15) is applied across all resource allocations.

[0118] Scheme 2b (FDM): One codeword of one RV is used for each of the non-overlapping frequency resource allocations. The RVs corresponding to each of the non-overlapping frequency resource allocations may be the same or different. It is possible to consider applying different MCS / modulation orders to different non-overlapping frequency resource allocations.

[0119] Details of the frequency resource allocation mechanism of FDM 2a / 2b regarding allocation granularity and time domain allocation can also be examined.

[0120] Scheme 3 (TDM): n (n ≤ Nt1) TCI states within a single slot with no overlap in time resource allocation. Each transmission opportunity in a TB has one TCI and one RV at the time granularity of a mini-slot. For all transmission opportunities within the slot, a common MCS containing the same single or multiple DMRS ports is used. The RV / TCI states may be the same or different between transmission opportunities. Channel estimation interpolation (detailed review) is performed across mini-slots of the same TCI index.

[0121] Scheme 4 (TDM): K (n ≤ K) different slots with n (n ≤ Nt2) TCI states. Each transmission opportunity of a TB has one TCI and one RV. For all transmission opportunities across the K slots, a common MCS containing the same single or multiple DMRS ports is used. The RV / TCI states may be the same or different between transmission opportunities. Then, channel estimation interpolation (detailed review) is performed across slots with the same TCI index.

[0122] In addition, M-TRP / panel-based URLLC schemes should be compared in terms of reliability improvement, efficiency, and impact on specifications, and support for the number of layers per TRP may be reviewed.

[0123] In the case of FDM, in schemes 2a and 2b, the number of transmission configuration indication (TCI) states is set to 2 according to scheme 2a, supporting up to 2 transmission layers. In the case of TDM, in schemes 3 and 4, the number of TCI states is also set to 2. Resource allocation in the time domain supports the same number of consecutive symbols scheduled for each transmission opportunity. In the case of scheme 3, due to network (NW) implementation, not all transmission opportunities are dropped and exist in a single slot, and details regarding downlink / uplink (DL / UL) switching within the slot are examined.

[0124] The UE may be configured to receive PDSCH from up to two TRPs, depending on the number of configured TCI states. FIG. 7 illustrates a general beam failure recovery procedure (700) comprising four main steps. The first step is beam failure detection (BFD) (702). The UE is provided with a list of reference signals (RS) for detecting beam failures by failure Detection Resources. Or, if RS is not provided by failure Detection Resources, the UE executes BFD (702) based on the TCI state for receiving PDCCH / PDSCH (see Section 6 of TS 38.213 and Section 8.5 of TS 38.133).

[0125] The next step is new beam identification (NBI) (also known as candidate new beam detection). The UE is provided with a list of CBD RSs via the candidate Beam RS List.

[0126] Steps 702 and 704 are performed on the UE (705). When a new beam is identified, the UE (705) transmits a beam failure recovery request (BFRQ) (706) to the associated gNB (710). In response, the gNB (710) transmits a beam failure recovery response (BFRR) (708), and the BFR procedure (700) is completed.

[0127] As shown in FIG. 6, the UE (602) is configured to receive PDSCH (610, 612) from both TRP#1 (620) and TRP#2 (622), and the TRP configured to transmit PDSCH (640) by upper layer signaling is called TRP#1 (620). FIG. 8 is a figure (800) in which a user terminal (UE) simultaneously receives PDSCH (physical downlink shared channel) (610, 612) from the first TRP (TRP#1) (620) and the second TRP (TRP#2) (622), respectively. The UE (602) is configured to receive PDSCH (610, 612) simultaneously from TRP#1 (620) and TRP#2 (622) during the operation time (T_state02) (802), according to two TCI states (810) appearing at the TCI code point (820).

[0128] FIG. 9 is a figure (900) showing the operating time lengths of beam interference detection (BFD) (910) and new beam candidate detection (CBD) (920) in the BFR procedure. While the UE utilizes measurement effort and power consumption to evaluate the BFD and / or CBD regarding TRP#2, performance is not improved if the operating time length (802) is not longer than the required BFD evaluation time (910) and / or CBD evaluation time (920). The BFD evaluation time (910) (T_evaluate_BFD) and CBD evaluation time (920) (T_evaluate_CBD) required by the UE are defined by Section 8.5.3 of 38.133 and Section 5.17 of 38.321, respectively.

[0129] According to the present embodiment, the UE receives a signal from an M-TRP during operation and has a circuit that performs BFR from two or more M-TRPs by (a) evaluating BFD and CBD on a signal including a PDCCH (physical downlink control channel) from at least one TRP, and (b) skipping the evaluation of one or both of BFD and CBD according to one or more operating conditions. In this way, the UE reduces measurement effort and power consumption. Furthermore, the reduction in measurement effort and power consumption by the UE within the network realizes the flexibility of M-TRP URLLC.

[0130] To evaluate the BFD of two or more M-TRPs, multiple sets of BFD reference signals (BFD-RS) may be explicitly or implicitly set for the UE, and each set is set for each of the multiple TRPs (i.e., a set of BFD-RS for each TRP). In the explicit method, the set of BFD-RS for each TRP may be set as a set of periodic channel state information reference signals (CSI-RS) or synchronization signal blocks (SSB). In the implicit method, the set of BFD-RS for each TRP may be implicitly set as a quasi-co-location (QCL) reference signal of the corresponding CORESET based on its TCI state. Likewise, to evaluate the CBD of two or more M-TRPs, multiple sets of CBD reference signals (CBD-RS) (or NBI reference signals (NBI-RS)) may be explicitly or implicitly set for each TRP. It is understood that such independent setting of sets of BFD-RS and / or sets of CBD-RS for each TRP is applicable throughout all embodiments.

[0131] By establishing an independent BFD-RS set for each TRP, a beam interference recovery procedure for that specific TRP can be triggered when a BFD-RS set from one of the multiple TRPs is identified as having an interference (i.e., when a beam from one of the multiple TRPs is identified as having an interference). This can be understood as partial or TRP-specific beam interference recovery. Compared to use case scenarios where the beam interference recovery procedure is triggered only when all BFD-RS sets configured for all TRPs are identified as having an interference (or when all beams of all TRPs are identified as having an interference), this is beneficial in that it reduces the delay in overall beam interference recovery and improves the transmission efficiency of multiple TRPs / panels.

[0132] In addition, there may be several other BFR parameters that are set based on the TRP level. For example, assume that two TRPs (e.g., TRP#1 and TRP#2) are in operation. Accordingly, two sets of thresholds, such as BFD thresholds (Q_out) and CBD thresholds (Q_in), two sets of timers, such as BFD timers and BFR timers, and two sets of beam failure instance (BFI) counters and the maximum number of corresponding BFI indications (BFII) can be set independently for TRP#1 and TRP#2, respectively.

[0133] FIG. 10 illustrates a first BFR procedure according to the present disclosure. The first BFR procedure queues off the operation time length as shown in FIG. 9. Also, TRP#1 (620) is one of the M-TRPs that transmits PDCCH (640) by upper layer signaling.

[0134] First, the UE receives a configuration parameter (1002) that includes at least a notification (e.g., T_state02 (802)) indicating the appropriate operating time length of TRP#2 (622) from upper layer signaling from M-TRP (i.e., from PDCCH (640) from TRP#1 (620)). The appropriate operating time length may be a static value of the network (e.g., T_state02 can be defined based on the value obtained by adding an offset to the operating time length of TRP#1 (620)), or it may be dynamically determined by the network based on actual environmental conditions or network configuration. An example of dynamically calculating the appropriate operating time using at least DCI, MAC CE, or RRC signaling is shown in Equation (1).

[0135] [Mathematical Formula 1]

[0136] T_state02=TRP#1 operation time length-PDCCH transmit time-offset

[0137] The offset may be the active time or delay (if present) of TRP#2.

[0138] In addition, contrary to the above description, there is a possibility that T_state02 may be set as an operation time length or window during which two TCI states are both activated, or both TRP#1 and TRP#2 are activated.

[0139] Next, the UE performs beam disturbance detection and recovery as specified in Rel-15 / 16 for TRP#1 by performing BFD (1004) and CBD (1006) for TRP#1.

[0140] Specifically, the UE continuously monitors the set of BFD-RS configured for TRP#1 to detect beam interference (1004). If the link level quality of all corresponding BFD-RS resources exceeds a threshold at any point (this BFD threshold Q_out is defined as a level at which the downlink radio link cannot be reliably received and corresponds to the block error rate outage (BLER_out) of virtual PDCCH transmission), a BFI can be identified. The physical layer (PHY) provides a BFI notification to the MAC (Media Access Control) layer. The BFD procedure (1004) in the MAC is indicated by a timer and a counter that counts the number of BFIIs. The timer is restarted whenever a BFII is received, and the counter is reset when the timer expires. Meanwhile, a successive N max When a beam failure instance max count (BFII) is detected, the UE can declare that a beam failure has occurred for TRP#1. Subsequently, the CBD (1006) of TRP#1 is triggered. The UE monitors the link-level quality of the CBD-RS set (e.g., CSI-RS or SSB set) to re-establish connectivity. The UE measures the reference signal received power (L1-RSRP) for the reference signals of the multiple CBD-RSs. If the measured value of L1-RSRP exceeds a predetermined value, a new beam can be identified.

[0141] The UE may skip or execute the evaluation of the 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 for evaluating the BFD of TRP#2 (e.g., T_evaluate_BFD (910) of FIG. 9) (1008), the UE skips both the BFD and the CBD (1010). If the UE determines that T_state02 is greater than T_evaluate_BFD (1008), the UE executes the BFD for TRP#2 (1012). Next, the UE compares the time length of T_state02 with T_evaluate_CBD (920) to determine whether 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 the CBD of TRP#2 (e.g., T_evaluate_CBD (920)) (1014), the UE skips the CBD (1016). If the UE determines that T_state02 is greater than T_evaluate_CBD (1014), the UE executes the CBD for TRP#2 (1018).

[0142] When performing BFD for TRP#2 (1012), the UE is N, just like in TRP#1. maxIt is necessary to detect consecutive BFIIs, and then, based on the BFD-RS set of TRP#2, it may be declared that a beam interference is occurring. Next, an evaluation of the CBD is triggered (1018), and the UE measures the quality of the link level, such as the L1 reference signal received power (L1-RSRP) regarding the reference signal of the CBD-RS set of TRP#2. In this way, the BFD procedure (1012) of TRP#2 in the MAC layer indicated by the timer and counter is set independently compared with TRP#1. In step 1020, the UE declares a beam interference event if a beam interference of TRP#1 and / or TRP#2 is identified between BFRQ (step 706 of FIG. 7). Regarding TRP#2, if the CBD is skipped, no action, or no new beam information is reported as no action as the default behavior. The UE reports beam interference content including (a) beam interference (BF) information for TRP#1 and / or TRP#2, (b) new beam information for TRP#1 (if any), and (c) new beam information for TRP#2, no action, or no new beam information due to no action (if any). Then, the UE receives BFRR from the network providing the corresponding beam from TRP#1 and / or TRP#2 (1022).

[0143] The BFRQ generated in Step 1020 may include beam failure information for each TRP where the failure occurred, such as the beam failure index, TRP index, or configuration index of the corresponding TRP. The BFRQ transmitted in Step 1020 also includes reporting content for TRP#1 and / or TRP#2 and is reported to the network through at least an uplink control information (UCI) message, a medium access control layer control element (MAC CE) message, or a radio resource control (RRC) message.

[0144] In this way, when the UE detects a beam interference of any TRP from multiple TRPs (here, for example, when TRP #2 causes the interference), the UE can transmit a BFRQ containing beam interference information of the TRP that caused the interference and new beam information to the active TRP #1. Then, the active TRP #1 can transmit the BFRQ to the TRP that caused the interference, TRP #2, via a backhaul. This is because the backhaul may have the latest available uplink resources to carry the BFRQ. In other words, the BFRQ procedure of M-TRP operation must be transmitted over a link with good channel conditions. When the backhaul is in the best condition, that is, when the backhaul delay satisfies the requirements or is assumed to be close to zero, the BFR procedure can function properly. If the backhaul is not optimal, or if new beam information for the faulty TRP#2 is not reported by the UE, the active TRP#1 may decide to instruct the UE to switch from multi-TRP operating mode to single-TRP operating mode. This situation occurs when the backhaul delay is not adequate for the delay requirements of the BFR sequence set by the BFR timer, or when there is a possibility that the UE cannot reach the faulty TRP#2 because it is completely blocked. The TRP transmitting the PDCCH at a higher level may be configured based on the RRC settings. For example, assuming that two TRPs (TRP A and TRP B) are operating, in the first RRC setting, TRP A may be configured to transmit the PDCCH, and thus TRP A becomes the primary TRP or TRP#1, and TRP B becomes TRP#2. Also, in the second RRC setting, TRP B may be configured to transmit PDCCH, in which case TRP B becomes the primary TRP or TRP#1, and TRP A becomes TRP#2.In this way, flexibility in M-TRP URLLC operation can be realized.

[0145] Additionally, by means of upper-layer parameters, multiple TRPs can be configured to operate under a carrier aggregation (CA) framework. Specifically, TRP A can be configured to operate as a primary cell (PCell) or primary TRP, and TRP B can be configured to operate as a secondary cell (SCell) or secondary TRP. In this way, either the BFR sequence proposed in this embodiment or a Rel-16 BFR for multiple SCells involving several extensions can be used.

[0146] In addition, up to two separate scheduling request (SR) settings, each containing a separate PUCCH resource (i.e., an SR-PUCCH resource), may be assigned to transmit BFRQs of two TRPs, TRP #1 and TRP #2. If a common SR-PUCCH resource is assigned to both TRPs, and a failure occurs in some TRPs, the UE may transmit the BFRQ of the failed TRP to the active TRP based on this common SR-PUCCH resource. If two separate SR-PUCCH #1 and SR-PUCCH #2 are assigned to TRPs, TRP #1 and TRP #2 respectively, and a failure occurs in TRP #2, the UE may transmit the BFRQ information of TRP #2 to the active TRP #1 based on one of the assigned SR-PUCCH #1 and SR-PUCCH #2 resources. When three or more TRPs are in operation, the multiple TRPs may be grouped into multiple groups, and SR-PUCCH resources for transmitting BFRQ information may be allocated to each group. For example, if there are two TRP groups, and the first group includes the primary TRP (or TRP#1) and the second group includes the remaining TRP (or secondary TRP), the resources for SR-PUCCH#1 and SR-PUCCH#2 may be allocated to the first group and the second group, respectively. However, as described above, there are cases where SR-PUCCH resources common to both groups are allocated to transmit BFRQ information. This may be in accordance with regulations pre-established in the network implementation or specifications.

[0147] As shown in FIG. 8, the UE is configured to simultaneously receive an independent PDSCH (610) from TRP#1 and an independent PDSCH (612) from TRP#2 within the time of T_state02. FIG. 11 illustrates a second BFR procedure relating to the present disclosure. First, the network sets parameters to transmit PDSCHs from up to two TRPs (e.g., TRP#1 and TRP#2) (1102). As shown in FIG. 10, the UE always performs both BFD and CBD for TRP#1. To support the UE in saving power, the network determines whether the UE will perform either BFD or CBD or both for TRP#2 and transmits an explicit notification to the UE.

[0148] The network determines whether the UE will execute either BFD or CBD or both for TRP#2 by first determining whether T_state02 is less than or equal to T_evaluate_BFD (1104). If T_state02 is greater than T_evaluate_BFD (1104), the network sets the parameter BFDTRP2 to enable (1106), indicating that the UE will execute normal BFD / BFR for TRP#2. If T_state02 is less than or equal to T_evaluate_BFD (1104), the network sets the parameter BFDTRP2 to disable (1108), indicating that the UE will not execute either BFD or CBD for TRP#2.

[0149] Next, the network determines whether T_state02 is less than or equal to T_evaluate_CBD (1110). If T_state02 is greater than T_evaluate_CBD (1110), the network sets the parameter CBDTRP2 to enable (1112), indicating that the UE performs normal CBD for TRP#2. If T_state02 is less than or equal to T_evaluate_CBD (1110), the network sets the parameter CBDTRP2 to disable (1114), indicating that the UE does not perform CBD for TRP#2.

[0150] The determination criteria for steps 1104 and 1110 depend on the implementation of the gNB, and other criteria may be used. Then, the network transmits parameters BFDTRP2 and CBDTRP2, and the UE receives them (1116). The values ​​of BFDTRP2 and CBDTRP2 can be set and updated by using at least DCI, MAC CE, or RRC signaling.

[0151] Additionally, parameters of BFD and / or CBD may be implicitly set in the UE by interpreting the notification for setting BFD-RS and / or NBI-RS sets. Here, as an example, it is assumed that two sets of BFD-RS and two sets of CBD-RS are set in TRP#1 and TRP#2. The UE implicitly understands that it is necessary to perform evaluations of BFD and CBD for both TRP#1 and TRP#2.

[0152] Next, in the same manner as the steps for BFD (1004) and CBD (1006), the UE performs beam interference detection and recovery for TRP#1 as defined in Rel-15 / 16 by performing BFD (1118) and CBD (1120) for TRP#1. The UE performs beam interference detection and recovery for TRP#2 according to the value of BFDTRP2 (1122) and the value of CBDTRP2 (1124). In step 1122, if the value of BFDTRP2 is "disabled," the BFD action for TRP#2 is not performed, otherwise, BFD is performed for TRP#2. In step 1124, if the value of CBDTRP2 is "disabled," the CBD action for TRP#2 is not performed, otherwise, CBD is performed for TRP#2.

[0153] The UE declares a BF event if a beam interference of TRP#1 and / or TRP#2 is identified between BFRQs (1126). The UE reports BF content that may include BF information for TRP#1 and / or TRP#2, new beam information for TRP#1 (if any), and / or new beam information for TRP#2, no action, or no new beam information due to no action (if any). Finally, in step 1128, the network generates and transmits a BFRR containing corresponding beam information from TRP#1 and / or TRP#2.

[0154] In this way, the network reduces the number of RS for the UE by not setting the reference signal (RS) of the BFD and / or CBD, and by not transmitting T_state02 to the UE. Additionally, the UE reduces measurement effort and power consumption.

[0155] Since the operation of FIG. 11 includes an explicit notification of the network determined for the TRP, the specific condition based on the aforementioned explicit notification of the network can be extended to three or more TRPs. That is, BFDTRP (disable / enable) and / or CBDTRP (disable / enable) can be determined individually for each TRP and transmitted to the UE for use in the corresponding TRP. Alternatively, a common BFDTRP value (i.e., disable / enable) and / or a common CBDTRP value (i.e., disable / enable) can be notified to each of the TRPs.

[0156] Other operating conditions relating to the present disclosure that enable a reduction in the measurement effort and power consumption of the UE are to define a new timer value (i.e., active operating time length T_state02) for each individual TRP. The new timer is set to the UE. In this way, the TRP is activated for communication with the UE via a TCI state activating MAC CE and is deactivated when the UE receives a TCI state deactivating MAC CE or when the timer expires. The timer value is notified to the UE by using at least DCI (for each TCI state), MAC CE, or RRC signaling.

[0157] Since the BFD and CBD for TRP#1 are always executed, the timer value for TRP#1 is set to a symbolic value such as infinity to prevent timer-based deactivation. For TRP#2, the timer value (T_state02) is set to a finite value (i.e., TRP#2 becomes active on demand). Since the timer value is finite, the evaluation of the BFD / CBD for TRP#2 can be skipped as follows. If T_state02 ≤ T_evaluate_BFD, the UE skips the BFD and CBD; if T_state02 > T_evaluate_BFD and T_state02 ≤ T_evaluate_CBD, the UE executes the BFD and skips the CBD.

[0158] Beam interference in TRP#2 is reported to be identified, and no new beam information is reported due to no action or no action as the default behavior. This enables the realization of additional flexibility in M-TRP URLLC operation and reduces the UE's measurement effort and power consumption. Furthermore, since TRP#2 is deactivated upon timer expiration, explicit deactivation of TRP#2 (i.e., TCI status deactivation MAC CE) is unnecessary.

[0159] The network is N in one DCI. max It has been enabled to support the transmission of several TRPs. N max is a value (pre-configured) in the network specifications. For high-level solutions, the evaluation of BFD and CBD is N, which is the maximum number of TRPs to which the UE can be associated. UE Skips based on the flexible value of. N UE The value of is notified by using at least DCI, MAC CE, or RRC signaling.

[0160] N max >N UE In the case of, (N max -N UEThe evaluation of BFD and CBD of ) TRPs is skipped. N UE The list of values ​​can be selected based on configured rules, such as a list of TRPs with the strongest RSRP, ascending / descending order of index, or other rules. UE Since the setting value depends on UE capability, N UE The value of is flexible, thereby realizing flexibility in M-TRP URLLC operation and reducing the measurement effort and power consumption of the UE.

[0161] In other high-level solutions, the evaluation of BFD and CBD is N min Skips based on the (pre-)fixed value of. N min is the number of TRPs that need to be evaluated by the UE. N max >N min In the case of, (N max -N min The evaluation of BFD and CBD of ) TRPs is skipped. N min The list can be selected by (pre-)configured rules, such as a list of TRPs with the strongest RSRP, ascending / descending order of index, or other rules. min By this method of setting the value of, consistency across the entire network is provided. In addition, N min Since only the BFD and CBD of the TRP need to be evaluated, the effort required to measure BFD in the UE can be reduced.

[0162] In addition, although the flowcharts and descriptions of FIGS. 10 and 11, and the description of the timer settings, discussed scenarios for two TRPs, the method proposed therein is also directly applicable to scenarios for N TRPs (i.e., T_stateN, BFDTPRN, and CBDTRPN to support URLLC transmission of N TRPs using one DCI). Depending on the UE capability, the value of N can be set (in advance) by using at least DCI, MAC CE, or RRC signaling, or can be flexibly notified.

[0163] Additionally, while the description herein focuses on a scenario of M-TRP transmission based on a single DCI, the discussed method is applicable to scenarios of M-TRP transmission based on multiple DCIs with a few modifications. In particular, the evaluation of BFD and / or CBD for each individual TRP may be skipped based on specific conditions based on one or a combination of (a) the operating time length for each individual TRP, (b) explicit notification from the network, (c) timer settings (active time length for each individual TRP), (d) UE capabilities, and (e) the minimum number of TRPs.

[0164] As such, it can be seen that exemplary embodiments provide a plurality of systems to realize flexibility in M-TRP URLLC operation and reduce the measurement effort and power consumption of the UE.

[0165] The present disclosure may be realized by software, hardware, or software that interacts with hardware. Each functional block used in the description of each embodiment described above may be realized partially or wholly by Large Scale Integration (LSI), such as an integrated circuit, and each process described in each embodiment may be controlled partially or wholly by the same LSI or a combination of LSIs. The LSI may be formed individually as a chip, or a single chip may be formed to include some or all of the functional blocks. The LSI may include data input / output coupled thereto. Here, depending on the difference in integration density, the LSI may be referred to as an IC, a system LSI, a super LSI, or an ultra LSI. However, the technology for realizing an integrated circuit is not limited to an LSI and may be realized using a dedicated circuit, a general-purpose processor, or a processor for a specific application. In addition, a Field Programmable Gate Array (FPGA) may be used after manufacturing an LSI or a reconfigurable processor in which the connection and configuration of circuit cells placed inside the LSI are reconfigurable. The present disclosure can be realized as digital processing or analog processing. If future integrated circuit technology is adopted instead of LSI as a result of advancements in semiconductor technology or other derivative technologies, the functional blocks may be integrated using future integrated circuit technology. Biotechnology may also be applied.

[0166] The present disclosure may be realized by any one type of device, device, or system having a communication function, referred to as a communication device. The communication device may have a transceiver and a processing / control circuit. The transceiver may have a receiver and a transmitter, and / or function as such. The transceiver as a transmitter and a receiver may include a Radio Frequency (RF) module comprising an amplifier, an RF modulator / demodulator, etc., and one or more antennas. The processing / control circuit may include a power management circuit that may include a dedicated circuit, a processor, and instructions for power management control as either firmware or instructions stored in memory provided in the processor.

[0167] Non-limiting examples of such communication devices include telephones (e.g., mobile (cell) phones, smartphones), tablets, personal computers (PCs) (e.g., laptops, desktops, netbooks), cameras (e.g., digital still / video cameras), digital players (digital audio / video players), wearable devices (e.g., wearable cameras, smartwatches, tracking devices), game consoles, digital book readers, remote health / remote medical devices, and vehicles providing communication functions (e.g., automobiles, airplanes, ships), and various combinations thereof.

[0168] The communication device is not limited to being portable or movable, and may include any type of device, device, or system that is non-portable or fixed, such as smart home devices (e.g., home appliances, lighting, smart meters, control panels), vending machines, and any other "thing" in a network of the "Internet of Things (IoT)".

[0169] Communication may include exchanging data through, for example, cellular systems, wireless LAN systems, satellite systems, etc., and various combinations thereof. A communication device may include a device such as a controller or a sensor coupled to a communication device that performs the communication functions described in this disclosure. For example, a communication device may include a controller or a sensor that generates a control signal or a data signal used by a communication device that performs the communication functions of the communication device.

[0170] The communication device may also include any other device, device, or system that communicates with or controls infrastructure facilities such as base stations and access points, and devices such as objects in the above non-limiting examples.

[0171] While exemplary embodiments have been presented in the foregoing detailed description of the present invention, it should be understood that a vast number of variations exist. Furthermore, it should be understood that these embodiments are merely illustrative and are not intended to limit the scope, applicability, operation, or configuration of the present disclosure in any way. Rather, the foregoing detailed description provides a useful roadmap to those skilled in the art for realizing the exemplary embodiments, and it will be understood that various modifications can be made to the functions and arrangements of the network and / or UE transceiver devices described in the exemplary embodiments without departing from the spirit of the present disclosure as set forth in the appended claims.

[0172] 1. During operation, a transceiver that receives signals from multiple transmission and reception points (M-TRP) within a network, at least on a physical downlink shared channel (PDSCH), and

[0173] A transmitting and receiving device having a circuit that performs beam failure recovery (BFR) by evaluating beam failure detection (BFD) and candidate new beam detection (CBD) on the signal from the first TRP among the M-TRPs during operation,

[0174] A transmitting and receiving device wherein the signal from the first TRP among the M-TRPs includes a signal received from a PDCCH (physical downlink control channel), and the circuit determines, according to one or more conditions, to skip the evaluation of one or both of the BFD and the CBD for one or more additional TRPs among the M-TRPs.

[0175] 2. The transmitting and receiving device described in claim 1, wherein the above one or more conditions include the operating time length of the one or more additional TRPs among the M-TRPs, which is determined by the circuit according to the operating time length for performing BFR on a signal from the one or more additional TRPs among the M-TRPs.

[0176] 3. A transceiver device as described in claim 2, wherein the operating time length of one or more additional TRPs among the M-TRPs is notified from one of the M-TRPs using at least one of a DCI (downlink control information) message, a MAC CE (medium access control layer control element) message, or a RRC (radio resource control) message.

[0177] 4. The transmitting and receiving device described in claim 2, wherein the above one or more conditions include the operating time length of one or more additional TRPs among the M-TRPs, which is determined according to the operating time length and offset value for the first TRP among the M-TRPs to perform BFR.

[0178] 5. The transmitting and receiving device described in claim 4, wherein one or more of the above conditions include the operating time length of one or more additional TRPs among the M-TRPs, which is determined by the circuit in response to the PDCCH transmission time.

[0179] 6. A transceiver device according to any one of claims 2 to 5, wherein the above circuit skips the evaluation of both the BFD and the CBD of the one or more additional TRPs among the M-TRPs, as the operating time length of the one or more additional TRPs is not longer than the evaluation time of the BFD.

[0180] 7. A transceiver device according to any one of claims 2 to 5, wherein the above circuit skips the evaluation of the CBD of the one or more additional TRPs among the M-TRPs and performs the evaluation of the BFD, depending on the fact that the operating time length of the one or more additional TRPs is longer than the evaluation time of the BFD and is not longer than the evaluation time of the CBD.

[0181] 8. The above-described transceiver declares a beam failure event and transmits a beam failure recovery request (BFRQ) to one or more of the M-TRPs, the BFRQ identifies one or more of the beam failure (BF) events and reports content including BF information and CBD information for one or more of the M-TRPs, wherein for each of the M-TRPs, the BF information includes a beam failure index, a TRP index, or a configuration index, and the CBD information includes corresponding new beam information (if any), and default information if no new beam information exists.

[0182] 9. A transceiver device according to any one of claims 1 to 8, wherein the circuit declares a beam interference event to generate report content of a beam interference for one or more of the M-TRPs, and the transceiver transmits the report content 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.

[0183] 10. The reporting content generated by the circuit comprises beam interference information (if identified) for one or more of the additional TRPs of the M-TRP, and CBD information, wherein the CBD information comprises new beam information of the first TRP among the M-TRPs (if present), and default information if there is no new beam information of the one or more additional TRPs of the M-TRP.

[0184] 11. A transmitting and receiving device according to any one of claims 1 to 10, wherein one or more of the above conditions further include the operating time length of each independent TRP of the M-TRP.

[0185] 12. One or more of the above conditions include information received by the transmitting and receiving device as described in claim 1.

[0186] 13. The transmitting and receiving device described in claim 12, wherein the above information is notified using at least one of a DCI (downlink control information) message, a MAC CE (medium access control layer control element) message, or a RRC (radio resource control) message.

[0187] 14. The above information includes BFD parameters and / or CBD parameters corresponding to one or more of the additional TRPs of the M-TRP, and the circuit skips the evaluation of BFD according to the BFD parameters corresponding to one or more of the additional TRPs of the M-TRP, and / or skips the evaluation of CBD according to the CBD parameters corresponding to one or more of the additional TRPs of the M-TRP, the transmitting and receiving device described in claim 12 or claim 13.

[0188] 15. The transmitting and receiving device described in claim 14, wherein one or more of the above conditions include not receiving a reference signal for BFD and / or CBD for one or more of the additional TRPs of the M-TRP, but instead receiving the BFD parameters and / or the CBD parameters.

[0189] 16. A transmitting and receiving device as described in claim 14 or claim 15, wherein either or both of the above BFD parameters and / or the above CBD parameters are independently notified to each of the above M-TRPs.

[0190] 17. A transmitting and receiving device as described in claim 14 or claim 15, wherein either or both of the above BFD parameters and / or the above CBD parameters are common to all of the above M-TRPs.

[0191] 18. The information comprises a timer value corresponding to one or more additional TRPs of the M-TRP, and the circuit skips the evaluation of the BFD and / or the CBD for one or more additional TRPs of the M-TRP according to the timer value corresponding to one of the M-TRPs. A transceiver device as described in claim 12 or claim 13.

[0192] 19. The timer value includes a finite value, and the transmitting and receiving device described in claim 18 is deactivated when the timer expires.

[0193] 20. The above information includes a value corresponding to the maximum number of TRPs to which the transmitting and receiving device can be associated, and the circuit skips the evaluation of the BFD and / or the CBD for one or more of the M-TRPs according to the value corresponding to the maximum number of TRPs to which the transmitting and receiving device can be associated. This is the transmitting and receiving device described in claim 12 or claim 13.

[0194] 21. The above information includes a value corresponding to the number of TRPs to be evaluated by the transmitting and receiving device, and the circuit skips the evaluation of the BFD and / or the CBD for one or more of the M-TRPs according to the value corresponding to the number of TRPs to be evaluated by the transmitting and receiving device, the transmitting and receiving device as described in claim 12 or claim 13.

[0195] 22. A transceiver described in claim 20 or claim 21, wherein the list of M-TRPs evaluated by the transceiver is selected by a set rule such as a list of TRPs having the strongest RSRP, an ascending / descending order of an index, or by the implementation of the transceiver.

[0196] 23. The above circuit identifies the first TRP among the M-TRPs according to a signal received from the PDCCH according to the RRC setting of the network, a transceiver device as described in any one of claims 1 to 22.

[0197] 24. The above-described transceiver is a transceiver that simultaneously receives a PDSCH from two or more of the M-TRPs, and the PDSCH received from each of the two or more M-TRPs is received at a different layer, the transceiver described in any one of claims 1 to 23.

[0198] 25. The above-described transceiver receives a signal of M-TRP transmission based on a single DCI, a transceiver device as described in any one of claims 1 to 24.

[0199] 26. The above-described transmitting and receiving unit receives a signal of M-TRP transmission based on a plurality of DCIs, a transmitting and receiving device as described in any one of claims 1 to 24.

[0200] 27. A network having multiple transmission and reception points (M-TRP) for transmitting and receiving signals, and

[0201] A system comprising a transmitting and receiving device having a transmitting and receiving unit that receives a signal from one or more of the M-TRPs during operation, and a circuit that performs beam failure recovery (BFR) by performing evaluation of beam failure detection (BFD) and candidate new beam detection (CBD) on the signal from the first TRP among the M-TRPs during operation, wherein the network generates one or more values ​​for performing BFD and CBD for one or more of the M-TRPs and transmits the one or more values ​​to the transmitting and receiving device, and the circuit skips one or both evaluations of the BFD and CBD for the one or more additional TRPs among the M-TRPs according to one of the one or more values ​​corresponding to the one or more additional TRPs among the M-TRPs.

[0202] 28. The system described in claim 27, wherein the one or more values ​​corresponding to one or more of the above M-TRPs can be notified using at least one of a DCI (downlink control information) message, a MAC CE (medium access control layer control element) message, or a RRC (radio resource control) message.

[0203] 29. The system described in claim 27 or claim 28, wherein the network generates one or more values ​​for performing BFD and CBD for one or more of the M-TRPs according to the network implementation.

[0204] 30. The system described in any one of claims 27 to 29, wherein the transceiver receives the signal from one or more of the M-TRPs as an M-TRP transmission based on one DCI.

[0205] 31. The system described in any one of claims 27 to 29, wherein the transceiver receives the signal from one or more of the M-TRPs as an M-TRP transmission based on a plurality of DCIs.

[0206] 32. The system described in claim 31, wherein one or more of the above values ​​include the operating time length of each independent TRP or information of each independent TRP, which is received by the transceiver of the transceiver device.

Claims

Claim 1 A communication device comprising: a transceiver receiving a first set of beam fault detection (BFD) reference signal settings, a second set of BFD reference signal settings, a first set of candidate new beam detection (CBD) reference signal settings, and a second set of CBD reference signal settings; a circuit performing both a first beam fault detection regarding a first transmission / reception point based on the first set of BFD reference signal settings and a candidate new beam detection regarding the first transmission / reception point based on the first set of CBD reference signal settings, and performing at least one of a second beam fault detection regarding a second transmission / reception point based on the second set of BFD reference signal settings and a candidate new beam detection regarding the second transmission / reception point based on the second set of CBD reference signal settings; wherein the transceiver transmits a signal including the result of the first beam fault detection and the result of the second beam fault detection to the first transmission / reception point. Claim 2 In claim 1, the first set of BFD reference signal settings, the second set of BFD reference signal settings, the first set of CBD reference signal settings, and the second set of CBD reference signal settings are communication devices indicated by Medium Access Control Element (MAC CE) or Radio Resource Control (RRC) signaling. Claim 3 A communication device according to claim 1, wherein the first set of BFD reference signal settings and the second set of BFD reference signal settings, and / or the first set of CBD reference signal settings and the second set of CBD reference signal settings are settings of channel state information (CSI) reference signals or settings of synchronization signal blocks. Claim 4 A communication device according to claim 1, wherein whether both the first beam fault detection based on the first set of the BFD reference signal settings and the second beam fault detection based on the second set of the BFD reference signal settings are performed is determined by the transmission configuration indication (TCI) of the downlink control information. Claim 5 A communication device according to claim 1 that transmits a signal to the first transmitting / receiving point, the signal comprising the result of the first beam fault detection related to the first set of the BFD reference signal settings, the result of the second beam fault detection related to the second set of the BFD reference signal settings, the result of the candidate new beam detection related to the first set of the CBD reference signal settings, and the result of the candidate new beam detection related to the second set of the CBD reference signal settings. Claim 6 A communication method comprising: a communication device receiving a first set of beam failure detection (BFD) reference signal settings, a second set of BFD reference signal settings, a first set of candidate new beam detection (CBD) reference signal settings, and a second set of CBD reference signal settings; performing both a first beam failure detection regarding a first transmission / reception point based on the first set of BFD reference signal settings and a candidate new beam detection regarding the first transmission / reception point based on the first set of CBD reference signal settings; performing at least one of a second beam failure detection regarding a second transmission / reception point based on the second set of BFD reference signal settings and a candidate new beam detection regarding the second transmission / reception point based on the second set of CBD reference signal settings; and transmitting a signal including the result of the first beam failure detection and the result of the second beam failure detection to the first transmission / reception point. Claim 7 In claim 6, the first set of BFD reference signal settings, the second set of BFD reference signal settings, the first set of CBD reference signal settings, and the second set of CBD reference signal settings are communication methods indicated by Medium Access Control Element (MAC CE) or Radio Resource Control (RRC) signaling. Claim 8 In claim 6, the first set of BFD reference signal settings and the second set of BFD reference signal settings, and / or the first set of CBD reference signal settings and the second set of CBD reference signal settings are a setting of channel state information (CSI) reference signals or a setting of synchronization signal blocks, in a communication method. Claim 9 A communication method according to claim 6, wherein whether both the first beam fault detection based on the first set of the BFD reference signal settings and the second beam fault detection based on the second set of the BFD reference signal settings are performed is determined by the transmission configuration indication (TCI) of the downlink control information. Claim 10 A communication method according to claim 6, wherein the signal transmitted to a base station comprises the result of the first beam fault detection related to the first set of the BFD reference signal settings, the result of the second beam fault detection related to the second set of the BFD reference signal settings, the result of the candidate new beam detection related to the first set of the CBD reference signal settings, and the result of the candidate new beam detection related to the second set of the CBD reference signal settings. Claim 11 An integrated circuit controlling processing for receiving a first set of beam fault detection (BFD) reference signal settings, a second set of BFD reference signal settings, a first set of candidate new beam detection (CBD) reference signal settings, and a second set of CBD reference signal settings; processing for performing both a first beam fault detection regarding a first transmission / reception point based on the first set of BFD reference signal settings and a candidate new beam detection regarding the first transmission / reception point based on the first set of CBD reference signal settings, and performing at least one of a second beam fault detection regarding a second transmission / reception point based on the second set of BFD reference signal settings and a candidate new beam detection regarding the second transmission / reception point based on the second set of CBD reference signal settings; and processing for transmitting a signal including the result of the first beam fault detection and the result of the second beam fault detection to the first transmission / reception point. Claim 12 delete Claim 13 delete Claim 14 delete Claim 15 delete Claim 16 delete Claim 17 delete Claim 18 delete Claim 19 delete Claim 20 delete Claim 21 delete Claim 22 delete Claim 23 delete Claim 24 delete Claim 25 delete Claim 26 delete Claim 27 delete Claim 28 delete Claim 29 delete Claim 30 delete Claim 31 delete Claim 32 delete

Images