Terminal and wireless communication method

Abstract

A terminal according to one embodiment of the present disclosure includes a reception unit that receives at least one of one downlink control information used for scheduling a plurality of downlink shared channels (PDSCHs) and a plurality of downlink control information used for scheduling a plurality of PDSCHs, and a control unit that controls reception of the plurality of PDSCHs within a certain period based on at least one of quasi co-location corresponding to a first control resource set for the one downlink control information and quasi co-location corresponding to a second control resource set for the plurality of downlink control information.

Description

Technical Field

[0001] This disclosure relates to terminals in next-generation mobile communication systems and wireless communication methods. Background Technology

[0002] In Universal Mobile Telecommunications System (UMTS) networks, Long Term Evolution (LTE) was standardized with the aim of further increasing data rates and reducing latency (Non-Patent Document 1). Furthermore, LTE-Advanced (3GPP Rel. 10-14) was standardized with the aim of further increasing capacity and height from LTE (Third Generation Partnership Project (3GPP) Releases 8 and 9).

[0003] The study also explored subsequent systems to LTE (e.g., also known as the 5th generation mobile communication system (5G), 5G+, New Radio (NR), 3GPPRel.15 and later).

[0004] Existing technical documents

[0005] Non-patent literature

[0006] Non-patent document 1: 3GPP TS 36.300V8.12.0 "Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 (Release 8)", April 2010 Summary of the Invention

[0007] The problem that the invention aims to solve

[0008] Research is underway in future wireless communication systems (such as NR) to enable user terminals (User Equipment) to control transmission and reception processes based on information related to quasi-co-location (QCL).

[0009] In addition, research is underway in NR to consider one or more Transmission / Reception Points (TRPs) (multi-TRPs) using one or more panels (multi-panel) to perform DL transmission (e.g., PDSCH transmission) to the UE.

[0010] However, the previous NR specification did not consider multi-panel / TRP configurations, making it impossible to properly determine the QCL parameters for multi-panel / TRP scenarios. Failure to properly determine the QCL parameters could lead to concerns about reduced system performance, such as decreased throughput.

[0011] Therefore, one of the objectives of this disclosure is to provide a terminal and a wireless communication method for appropriately determining the QCL parameters for a multi-panel / TRP.

[0012] Methods for solving problems

[0013] A terminal according to one aspect of this disclosure is characterized by comprising: a receiving unit for receiving one downlink control information for scheduling multiple downlink shared channels (PDSCHs) and at least one of multiple downlink control information for scheduling multiple PDSCHs; and a control unit for controlling the reception of the multiple PDSCHs during a specific period based on at least one of a quasi-co-addressing corresponding to a first control resource set for the one downlink control information and a quasi-co-addressing corresponding to a second control resource set for the multiple downlink control information.

[0014] Invention Effects

[0015] According to one method of this disclosure, the QCL parameters for multi-panel / TRP can be appropriately determined. Attached Figure Description

[0016] Figure 1 This is a diagram illustrating an example of the QCL concept for the DMRS port of the PDSCH.

[0017] Figures 2A-2D This is a diagram illustrating an example of a multi-TRP scenario.

[0018] Figure 3A as well as Figure 3B This is a diagram illustrating an example of the default QCL for multiple PDSCHs.

[0019] Figure 4 This is a diagram showing an example of the QCL time length corresponding to a single DCI using a CORESET and the QCL time length corresponding to a multi-DCI using a CORESET.

[0020] Figure 5A as well as Figure 5BThis is a diagram illustrating an example of the first approach to QCL design.

[0021] Figure 6 This is a diagram illustrating an example of the second approach to QCL design.

[0022] Figure 7A as well as Figure 7B This diagram illustrates an example of a third-party QCL concept.

[0023] Figure 8 This is a diagram illustrating an example of a fourth approach to QCL design.

[0024] Figure 9 This is a diagram illustrating an example of the schematic structure of a wireless communication system according to one embodiment.

[0025] Figure 10 This is a diagram illustrating an example of the structure of a base station according to one embodiment.

[0026] Figure 11 This is a diagram illustrating an example of the structure of a user terminal according to one embodiment.

[0027] Figure 12 This is a diagram illustrating an example of the hardware structure of a base station and a user terminal according to one embodiment. Detailed Implementation

[0028] (TCI, QCL)

[0029] The following is being studied in NR: Controlling the reception processing (e.g., at least one of receiving, demapping, demodulation, and decoding) and transmission processing (e.g., at least one of transmitting, mapping, precoding, modulation, and encoding) of at least one of the signals and channels (referred to as signals / channels) in the UE based on the Transmission Configuration Indication state (TCI state)

[0030] TCI states can also represent elements of signals / channels applied to the downlink. Similarly, elements of TCI states applied to signals / channels in the uplink can also be represented as spatial relationships.

[0031] TCI status refers to information related to the quasi-co-location (QCL) of a signal / channel, and can also be referred to as spatial reception parameters, spatial relation information, etc. TCI status can also be set by the UE for each channel or each signal.

[0032] QCL refers to an indicator that represents the statistical properties of a signal / channel. For example, if a signal / channel has a QCL relationship with other signals / channels, it can also mean that at least one of the following is the same among these different signals / channels: Doppler shift, Doppler spread, average delay, delay spread, and spatial parameter (e.g., spatial Rxparameter) (with regard to at least one of these being the QCL).

[0033] Additionally, the spatial reception parameters may also correspond to the UE's receive beam (e.g., receive analog beam), and the beam may also be determined based on the spatial QCL. The QCL (or at least one element of the QCL) in this disclosure may also be replaced with sQCL (spatialQCL).

[0034] Regarding QCL, multiple types (QCL types) can also be specified. For example, four different QCL types (ADs) can be set that can be assumed to have the same parameters (or parameter sets), as shown below:

[0035] • QCL Type A (QCL-A): Doppler shift, Doppler spread, average delay, and delay spread;

[0036] • QCL type B (QCL-B): Doppler offset and Doppler extension.

[0037] • QCL Type C (QCL-C): Doppler shift and average time delay;

[0038] • QCL type D (QCL-D): Space reception parameters.

[0039] The UE envisions that a certain control resource set (CORESET), channel, or reference signal has a specific QCL (e.g., QCL type D) relationship with other CORESETs, channels, or reference signals, which can also be referred to as a QCL assumption.

[0040] The UE may also determine at least one of the transmit beam (Tx beam) and receive beam (Rx beam) of the signal / channel based on the TCI state or QCL assumption of the signal / channel.

[0041] For example, the TCI state can also be QCL-related information between the target channel (in other words, the reference signal (RS) used by the channel) and other signals (e.g., other RS). The TCI state can also be set (indicated) by higher-layer signaling, physical-layer signaling, or a combination thereof.

[0042] In this disclosure, for example, higher-level signaling may also be any one or a combination of Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling, broadcast information, etc.

[0043] For example, MAC signaling can also use MAC Control Element (MAC CE) and MAC Protocol Data Unit (PDU). Similarly, broadcast information can be Master Information Block (MIB), System Information Block (SIB), Remaining Minimum System Information (RMSI), or Other System Information (OSI).

[0044] For example, physical layer signaling can also be downlink control information (Downlink Control Information (DCI)).

[0045] For example, the channel whose TCI state or spatial relationship is set (specified) can be at least one of the following: downlink shared channel (Physical Downlink Shared Channel (PDSCH))), downlink control channel (Physical Downlink Control Channel (PDCCH))), uplink shared channel (Physical Uplink Shared Channel (PUSCH))), and uplink control channel (Physical Uplink Control Channel (PUCCH))).

[0046] In addition, for example, the RS that is QCL-related to the channel can be at least one of the following: Synchronization Signal Block (SSB), Channel State Information Reference Signal (CSI-RS), Measurement Reference Signal (Sounding Reference Signal (SRS)), Tracking CSI-RS (also known as Tracking Reference Signal (TRS)), and QCL Detection Reference Signal (also known as QRS).

[0047] An SSB is a block of signals that contains at least one of the following: the Primary Synchronization Signal (PSS), the Secondary Synchronization Signal (SSS), and the Physical Broadcast Channel (PBCH). An SSB can also be referred to as an SS / PBCH block.

[0048] The UE can also receive configuration information (e.g., PDSCH-Config, tci-StatesToAddModList) containing a list of information elements related to TCI states via higher-layer signaling.

[0049] The TCI state information element (RRC's "TCI-state IE") configured via higher-layer signaling may also include a TCI state ID and one or more QCL information ("QCL-Info"). The QCL information may also include at least one of the following: information related to the RS that forms a QCL relationship (RS relationship information) and information indicating the QCL type (QCL type information). The RS relationship information may also include information such as the RS's index (e.g., SSB index, Non-Zero-Power (NZP) CSI-RS resource ID (Identifier)), the index of the cell where the RS resides, and the index of the Bandwidth Part (BWP) where the RS resides.

[0050] In Rel.15NR, as a TCI state of at least one of PDCCH and PDSCH, the UE can be set to both RS for QCL type A and RS for QCL type D, or only RS for QCL type A.

[0051] When the TRS is set to QCL type A RS, the TRS is different from the DeModulation Reference Signal (DMRS) of the PDCCH or PDSCH, and it is assumed that the same TRS is periodically transmitted over a long period of time. The UE can measure the TRS and calculate the average delay, delay spread, etc.

[0052] Since the TCI state of the DMRS of the PDCCH or PDSCH is set, the UE, using the TRS as the RS of QCL type A, can assume that the DMRS of the PDCCH or PDSCH has the same parameters (average delay, delay spread, etc.) as the QCL type A of the TRS. Therefore, the UE can derive the type A parameters (average delay, delay spread, etc.) of the DMRS of the PDCCH or PDSCH from the measurement results of the TRS. When performing channel estimation for at least one of the PDCCH and PDSCH, the UE can use the measurement results of the TRS to perform more accurate channel estimation.

[0053] A UE with a QCL type D RS can use the QCL type D RS to determine the UE receive beam (spatial domain receive filter, UE spatial domain receive filter).

[0054] The RS of QCL type X in TCI state can also mean the RS that has a QCL type X relationship with a certain channel / signal (DMRS), and the RS can also be called the QCL source of QCL type X in TCI state.

[0055] <TCI status for PDCCH>

[0056] Information related to QCL between the PDCCH (or the DMRS antenna port associated with the PDCCH) and a certain RS can also be referred to as the TCI status for the PDCCH, etc.

[0057] The UE can determine the TCI state for a UE-specific PDCCH (CORESET) based on higher-layer signaling. For example, one or more (K) TCI states can also be set for the UE for each CORESET via RRC signaling.

[0058] For each CORESET, the UE can also be activated by one of several TCI states set by RRC signaling via MAC CE. This MAC CE can also be called the UE-specific PDCCH TCI State Indication MAC CE. The UE can also monitor the CORESET based on the activated TCI state corresponding to that CORESET.

[0059] (TCI status for PDSCH)

[0060] Information related to QCL between the PDSCH (or the DMRS antenna port associated with the PDSCH) and a certain DL-RS can also be referred to as the TCI status for the PDSCH, etc.

[0061] The UE can also be notified (set) M (M≥1) TCI states (M QCL information for PDSCH) via higher-layer signaling. In addition, the number M of TCI states set in the UE can also be limited by at least one of the UE capability and QCL type.

[0062] The DCI used for scheduling PDSCH can also include a field to indicate the TCI status used for that PDSCH (e.g., it can also be called a TCI field, TCI status field, etc.). This DCI can also be used to schedule the PDSCH of one cell, and for example, it can also be called DL DCI, DL allocation, DCI format 1_0, DCI format 1_1, etc.

[0063] Whether a TCI field is included in the DCI can also be controlled by information notified to the UE from the base station. This information can also be information indicating whether the TCI field exists (present or absent) within the DCI (e.g., TCI field presence information, TCI presence information within the DCI, higher-layer parameter TCI-PresentInDCI). For example, this information can be set to the UE via higher-layer signaling.

[0064] When more than eight TCI states are set on the UE, a MAC CE can be used to activate (or specify) fewer than eight TCI states. This MAC CE can also be referred to as a UE-specific PDSCH MAC CE (TCIStates Activation / Deactivation for UE-specific PDSCH). The value of the TCI field within the DCI can also represent one of the TCI states activated by the MAC CE.

[0065] If the TCI field, which is set to "enabled" in the CORESET used for scheduling PDSCH (the CORESET used for sending PDCCH for scheduling PDSCH), is present in the UE, the UE may also assume that the TCI field exists in the DCI format 1_1 of the PDCCH sent on that CORESET.

[0066] If the TCI field of the CORESET used for scheduling the PDSCH is not set to have information, or if the PDSCH is scheduled in DCI format 1_0, and the time offset between the reception of the DL DCI (the DCI used for scheduling the PDSCH) and the reception of the PDSCH corresponding to the DCI is greater than a threshold, the UE may also assume that the TCI state or QCL of the PDSCH is the same as the TCI state or QCL of the CORESET used for sending the PDCCH used for scheduling the PDSCH, so as to determine the QCL of the PDSCH antenna port.

[0067] When the TCI field information is set to "enabled", if the TCI field in the DCI within the component carrier (CC) used for scheduling (PDSCH) indicates an activated TCI state within the scheduled CC or DL ​​BWP, and the PDSCH is scheduled in DCI format 1_1, the UE can also use the TCI that conforms to the value of the TCI field in the detected PDCCH with DCI to determine the QCL of the PDSCH antenna port. If the time offset between the reception of the DL DCI (used for scheduling the PDSCH) and the PDSCH corresponding to that DCI (the PDSCH scheduled by that DCI) is greater than or equal to a threshold, the UE can also assume that the DM-RS port of the serving cell's PDSCH and the RS within the TCI state related to the QCL type parameter provided by the indicated TCI state are QCL.

[0068] When a UE is configured with a single-slot PDSCH, the indicated TCI state can also be based on the active TCI state within the slot containing the scheduled PDSCH. When a UE is configured with multiple-slot PDSCHs, the indicated TCI state can be based on the active TCI state within the initial slot containing the scheduled PDSCH, or the UE can expect the indicated TCI state to be the same across the slots containing the scheduled PDSCHs. When a UE is configured with a CORESET associated with a search space set for cross-carrier scheduling, if in the UE, the TCI field presence information is set to "valid" for that CORESET, and at least one of the TCI states configured for the serving cell scheduled through the search space set contains QCL type D, then the UE can also assume that the time offset between the detected PDCCH and the PDSCH corresponding to that PDCCH is greater than or equal to a threshold.

[0069] In RRC connection mode, in both cases where the TCI information (higher-layer parameter TCI-PresentInDCI) within the DCI is set to "enabled" and when the TCI information within the DCI is not set, if the time offset between the reception of the DL DCI (the DCI used for scheduling PDSCH) and the corresponding PDSCH (the PDSCH scheduled by that DCI) is less than a threshold, the UE can also assume that: the DM-RS port of the serving cell's PDSCH is QCL-compliant with the following RS: the RS is related to the QCL parameter used by the PDCCH QCL indication of the CORESET that has the lowest CORESET-ID in the latest (latest) timeslot monitored by the UE and is associated with the monitored search space among more than one CORESET in the active BWP of the serving cell. Figure 1 This RS can also be referred to as the default TCI state of PDSCH or the default QCL assumption of PDSCH.

[0070] The time offset between the reception of a DL DCI and the reception of the corresponding PDSCH can also be referred to as the scheduling offset. In addition, the default QCL or default TCI state can be used not only when the scheduling offset is less than the threshold, but also for DL ​​signals / channels (e.g., PDSCH, A-CSI RS) scheduled by a specific DCI (or PDCCH, CORESET) before the RRC connection.

[0071] In addition, the above threshold can also be referred to as QCL time duration, "timeDurationForQCL", "threshold", "threshold for offset between a DCI indicating a TCI state and a PDSCH scheduled by the DCI", "threshold-Sched-Offset", scheduling offset threshold, scheduling offset threshold, etc.

[0072] The QCL usage time length can be based on UE capabilities, for example, or on delays related to PDCCH decoding and beam switching. The QCL usage time length can also be the minimum time required for the UE to receive PDCCH and apply spatial QCL information received within the DCI used for PDSCH processing. The QCL usage time length can be expressed in symbols per subcarrier interval or in time (e.g., μs). This QCL usage time length information can be reported from the UE to the base station as UE capability information, or it can be set by the base station to the UE using higher-layer signaling.

[0073] For example, the UE can also envision that the DMRS port of the aforementioned PDSCH and the DL-RS based on the TCI state activated for the CORESET corresponding to the aforementioned minimum CORESET-ID are QCLs. For example, the latest time slot can also be the time slot for receiving the DCI used to schedule the aforementioned PDSCH.

[0074] Alternatively, the CORESET-ID can also be an ID set through the RRC information element "ControlResourceSet" (used to identify the CORESET, controlResourceSetId).

[0075] If no CORESET is set for a CC, the default TCI state can also be the active TCI state with the lowest ID that can be applied to the active DLBWP of that CC.

[0076] After Rel.16, when the PDSCH and the PDCCH that schedules it exist in different component carriers (CC) (cross-carrier scheduling), if the delay from PDCCH to PDSCH (PDCCH-to-PDSCH delay) is less than the QCL usage time, or if the TCI state does not exist in the DCI used for scheduling, then the UE can also obtain the QCL assumption for the scheduled PDSCH from the PDSCH in the active BWP that can be applied to the scheduled cell and the active TCI state with the lowest ID.

[0077] (Service (Business Type))

[0078] Envisioning future wireless communication systems (e.g., NR) for: further enhancements to mobile broadband (e.g., enhanced Mobile Broadband (eMBB)), enabling massively simultaneous machine-type communications (e.g., massive Machine-Type Communications (mMTC), Internet of Things (IoT)), and high-reliability and low-latency communications (e.g., ultra-reliable and low-latency communications (URLLC)) are service types (also referred to as types, services, service types, communication types, use cases, etc.). For example, URLLC requires lower latency and higher reliability than eMBB.

[0079] At the physical layer, service types can also be identified based on at least one of the following:

[0080] • Logical channels with different priorities

[0081] • Modulation and Coding Scheme (MCS) Table (MCS Index Table)

[0082] Channel Quality Indication (CQI) Form

[0083] DCI format

[0084] • The wireless network temporary identifier (RNTI) used in the scrambling (mask) of the (additional) Cyclic Redundancy Check (CRC) bits contained in the DCI (DCI format).

[0085] • RRC (Radio Resource Control) parameters

[0086] • Specific RNTIs (e.g., RNTIs used in URLLC, MCS-C-RNTIs, etc.)

[0087] Search Space

[0088] • Specific fields within DCI (e.g., newly added fields or reuse of existing fields)

[0089] Service types can also be associated with communication requirements (such as latency and error rate) and data types (such as voice and data).

[0090] The difference between the requirements of URLLC and eMBB can be that URLLC has lower latency than eMBB, or that URLLC includes reliability requirements.

[0091] (Multiple TRPs)

[0092] In NR, research is underway on using one or more Transmission / Reception Points (TRPs) (multiple TRPs) to perform DL transmissions to the UE via one or more panels (multiple panels). Additionally, research is underway on the UE performing UL transmissions to one or more TRPs.

[0093] Furthermore, multiple TRPs can correspond to the same cell identifier (cell Identifier(ID)) or different cell IDs. This cell ID can be either a physical cell ID or a virtual cell ID.

[0094] Figures 2A-2D This diagram illustrates an example of a multi-TRP scenario. In these examples, it is assumed that each TRP can transmit four different beams, but it is not limited to this.

[0095] Figure 2A This represents a scenario where only one TRP (TRP1 in this example) transmits data to the UE in a multi-TRP configuration (also known as single mode, single TRP, etc.). In this case, TRP1 sends both control signals (PDCCH) and data signals (PDSCH) to the UE.

[0096] Figure 2B This represents an example of a scenario where only one TRP (TRP1 in this example) sends control signals to the UE, and that TRP also sends data signals (also known as single-master mode). The UE receives each PDSCH sent from that TRP based on a single Downlink Control Information (DCI).

[0097] Figure 2CThis represents an example of a scenario where each of the multiple TRPs sends a portion of the control signal to the UE, and the multiple TRPs also send data signals (also known as master-slave mode). It is also possible that portion 1 of the control signal (DCI) is sent in TRP1, and portion 2 of the control signal (DCI) is sent in TRP2. Portion 2 of the control signal can also depend on portion 1. The UE receives each PDSCH sent from the multiple TRP based on these portions of the DCI.

[0098] Figure 2D This illustrates an example of a multi-TRP configuration where each of the multiple TRPs sends a different control signal to the UE, and the multiple TRPs also send data signals (also known as a multi-master mode). It is also possible to send a first control signal (DCI) in TRP1 and a second control signal (DCI) in TRP2. The UE receives each PDSCH sent from the multiple TRPs based on these DCIs.

[0099] When Figure 2B As shown, when a single DCI is used to schedule multiple PDSCHs from multiple TRPs (which can be referred to as multiple PDSCHs), the DCI can be called a single DCI (S-DCI, single PDCCH). Additionally, in situations such as... Figure 2D In such cases, where multiple DCIs are used to schedule multiple PDSCHs from multiple TRPs, these multiple DCIs can also be called multiple DCIs (M-DCI, multiple PDCCH).

[0100] It can also be transmitted from different TRPs, different code words (CWs), and different layers. As a method of multi-TRP transmission, non-coherent joint transmission (NCJT) is being studied.

[0101] In NCJT, for example, TRP1 performs modulation mapping on the first codeword and layer mapping, and uses the first precoding on the first number of layers (e.g., layer 2) to transmit the first PDSCH. Furthermore, TRP2 performs modulation mapping on the second codeword and layer mapping, and uses the second precoding on the second number of layers (e.g., layer 2) to transmit the second PDSCH.

[0102] Furthermore, multiple PDSCHs (multiple PDSCHs) of NCJT can also be defined as partially or completely overlapping in terms of at least one of the time domain and frequency domain. That is, the first PDSCH from the first TRP and the second PDSCH from the second TRP can also overlap in terms of at least one of the time and frequency resources.

[0103] These first and second PDSCHs can also be conceived as not being quasi-co-located (QCL). The reception of multiple PDSCHs can also be replaced by the simultaneous reception of PDSCHs that are not of a certain QCL type (e.g., QCL type D).

[0104] In URLLC for multiple TRPs, support for PDSCH (Transport Block (TB) or Codeword (CW)) repetition across multiple TRPs is being investigated. Schemes supporting repetition across multiple TRPs in the frequency domain, layer (spatial) domain, or time domain (URLLC schemes, such as schemes 1, 2a, 2b, 3, and 4) are being studied. In scheme 1, space division multiplexing (SDM) is used for multiple PDSCHs from multiple TRPs. In schemes 2a and 2b, frequency division multiplexing (FDM) is used for PDSCHs from multiple TRPs. In scheme 2a, the redundancy version (RV) is the same for multiple TRPs. In scheme 2b, the RV can be the same or different for multiple TRPs. In schemes 3 and 4, time division multiplexing (TDM) is used for multiple PDSCHs from multiple TRPs. In scheme 3, multiple PDSCHs from multiple TRPs are transmitted within one time slot. In Scheme 4, multiple PDSCHs from multiple TRPs are transmitted in different time slots.

[0105] In such a multi-TRP scenario, more flexible transmission control can be implemented using channels with good quality.

[0106] NCJTs using multiple TRPs / panels have the potential to use high-rank. To support both ideal and non-ideal backhaul between multiple TRPs, a single DCI (single PDCCH, e.g.) can also be supported. Figure 2B ) and multiple DCI (multiple PDCCH, for example) Figure 2D Both. For both single DCI and multiple DCI, the maximum number of TRPs can be 2.

[0107] For single PDCCH designs (primarily for ideal backhaul), TCI extensions are being investigated. Each TCI code point within the DCI can also correspond to a TCI state of 1 or 2. The TCI field size can also be the same as Rel.15.

[0108] For single PDCCH designs (primarily for ideal backhaul), DMRS extensions are under investigation. The UE can also support the following combinations of layers from two TRPs, as indicated by the antenna port field. For single codeword (CW) and single user (SU), the combination of the layers of TRP1 and TRP2, expressed as "number of layers in TRP1 + number of layers in TRP2," can be any of 1+1, 1+2, 2+1, or 2+2. There is no consensus on supporting combinations of at least one layer from two TRPs, such as 1+3 and 3+1, as indicated by the antenna port field, support for multi-user (MU) scenarios, and support for two CWs. The size of the antenna port field can be the same as Rel.15.

[0109] For multi-PDCCH designs (for both ideal and non-ideal backhaul), the maximum number of CORESETs for each PDCCH configuration (PDCCH-Config) can be increased to 5, depending on the UE capability. The maximum number of CORESETs that can be set to the same TRP can also be less than the number reported by the UE capability. The same TRP can also be set per PDCCH configuration, and if a CORESET is set, the same higher-level index (e.g., CORESET pool index) can be set for each CORESET. The UE capability can also include at least 3 candidate values.

[0110] For multi-PDCCH designs (for both ideal and non-ideal backhaul), the maximum number of resources for at least one of the BD and CCE in each serving cell and each time slot can also be increased based on UE capabilities.

[0111] This study focuses solely on the extension of PDSCH to designs based on multiple PDCCHs.

[0112] The total number of CWs within a scheduled multi-PDSCH can be at most 2. Each PDSCH is scheduled by 1 PDCCH. The total number of multi-input multi-output (MIMO) layers of the scheduled PDSCHs can be at most the number reported by the UE's MIMO capability. There is no consensus on increasing the maximum number of HARQ processes in Rel.16.

[0113] The UE can also support different PDSCH scrambling sequences for multiple PDSCHs. The UE can also support extensions for setting RRC settings for multiple dataScramblingIdentityPDSCHs. Each dataScramblingIdentityPDSCH can also be associated with a higher-level index of each CORESET and applied to PDSCHs scheduled using DCIs detected on CORESETs with the same higher-level index.

[0114] For PDSCH resource allocation, the UE can also support multiple PDSCHs that are at least one of the following: fully overlapped, partially overlapped, or non-overlapped in both the time and frequency domains.

[0115] Regarding rate matching, the LTE cell-specific RS (cell-specific reference signal (CRS)) can also be extended with CRS mode information (lte-CRS-ToMatchAround) to set multiple CRS modes within the serving cell. CRS mode information consists of parameters used to determine the CRS mode, and the UE can perform rate matching around the CRS mode.

[0116] This study focuses on extending PUCCH for designs based on multiple PDCCHs.

[0117] It also supports both combined ACK / NACK (HARQ-ACK) feedback and individual ACK / NACK feedback. RRC signaling can also be used to switch between combined and individual feedback. For combined ACK / NACK feedback, both semi-static HARQ-ACK codebooks and dynamic HARQ-ACK codebooks are supported. For individual ACK / NACK feedback, the higher-level index for each CORESET used to generate separate HARQ-ACK codebooks can be set. It also supports both semi-static and dynamic HARQ-ACK codebooks. It also supports two long PUCCHs with TDM within one time slot, two short PUCCHs and one long PUCCH with TDM within one time slot, and two short PUCCHs with TDM within one time slot.

[0118] (Default QCL for multiple TRPs)

[0119] The serving cell setting for the scheduled PDSCH based on single-DCI multi-TRP / panel transmission using at least one TCI state, including QCL type D, for the single-DCI based multi-TRP / panel transmission, after receiving the activation command for the TCI state used by the UE-specific PDSCH, if the time offset between the PDCCH reception and the corresponding PDSCH is less than the threshold (timeDurationForQCL), the UE can also assume that the DMRS port of the PDSCH follows the QCL parameters indicated by the next default TCI state. The UE can also use the TCI state corresponding to the lowest code point among the two different TCI states activated for the PDSCH as the default TCI state. If all TCI code points are mapped to a single TCI state, the default TCI state can also follow the operation of Rel.15. Using a default TCI state for single-DCI based multi-PDSCH can also be part of the UE capability.

[0120] Figure 3A Figure 3B is a diagram illustrating an example of the default QCL based on a single DCI and multiple PDSCHs. This example is related to... Figure 2B The example shown corresponds to a single PDCCH.

[0121] The UE receives DCI1 and PDSCH1 from panel 1 (or TRP1 or CORESET pool 1). In addition, the UE receives PDSCH2 from panel 2 (or TRP2 or CORESET pool 2).

[0122] DCI1 schedules the reception of PDSCH1 and PDSCH2. The scheduling offset 1 from the reception of DCI1 up to PDSCH1 is less than the scheduling offset threshold. In addition, the scheduling offset 2 from the reception of DCI1 up to PDSCH2 is less than the scheduling offset threshold.

[0123] Figure 3B It shows in Figure 3A The example illustrates the hypothetical correspondence between the TCI field, TCI code point, and TCI state of DCI1. The lowest code point among the TCI code points containing two different TCI states activated for PDSCH is "001". The UE uses the TCI states (TCI state IDs) corresponding to this TCI code point "001" for T0 and T1 as the default QCL for PDSCH1 and PDSCH2, respectively.

[0124] For multi-TRP / panel transmission based on multiple DCI, with a CORESET pool index set, if the time offset between the PDCCH reception and the corresponding PDSCH is less than a threshold, the UE can also assume that the RS associated with the DM-RS port of the PDSCH and the QCL parameter used by the PDCCH of the lowest CORESET index among the CORESETs with the same CORESET pool index set in each latest time slot is the QCL. In each latest time slot, more than one CORESET associated with each of the CORESET pool indices in the active BWP of the serving cell is monitored by the UE. Support for this function is indicated (reported) by the UE capability. If the UE does not support the above feature, it can also reuse the operation of Rel.15 regardless of the CORESET pool index.

[0125] Furthermore, it is envisioned that the default QCL corresponding to multiple DCIs (or CORESETs used by multiple DCIs) and the default QCL corresponding to a single DCI (or CORESETs used by a single DCI) are specified separately (e.g., according to different rules). When CORESETs for single DCIs and multiple DCIs are allocated, how to control the QCL (e.g., the default QCL) applied to the PDSCH reception becomes a problem.

[0126] For example, the UE cannot determine whether the PDSCH can be scheduled until the DCI reception processing (e.g., demodulation or decoding) is completed. Therefore, if the scheduling offset is shorter than a threshold (e.g., QCL usage time length), the UE will save the received signal received through a specific default QCL into a buffer. Then, if the PDSCH is scheduled, the UE will perform demodulation or decoding processing on the resources of the PDSCH scheduled in the received signal saved in the buffer.

[0127] In this scenario, it's also conceivable that the UE could receive PDSCH using only one default QCL (or, a default QCL assumption). Therefore, when a single-DCI CORESET and a multi-DCI CORESET are set for a specific period, the question arises as to which default QCL to apply (see [reference]). Figure 4 ).

[0128] For example, in Figure 4In cases where the time length of the QCL corresponding to a single DCI CORESET (e.g., timeDurationForQCL for COREST of S-DCI) overlaps with the time length of the QCL corresponding to a multi-DCI CORESET (e.g., timeDurationForQCL for COREST of M-DCI), the question arises as to which default QCL assumption should be used for PDSCH reception processing.

[0129] If the default QCL used for receiving PDSCH is not properly determined, spatial diversity gain, high-rank transmission, etc., cannot be properly implemented in the case of using multi-panel / TRP, and there is a concern that the increase in communication throughput will be suppressed.

[0130] Therefore, the inventors of the present invention conceived of controlling the reception of PDSCH during a specific period based on at least one of the QCL (e.g., the default QCL) corresponding to the CORESET used for a single DCI and the QCL (e.g., the default QCL) corresponding to the CORESET used for multiple DCIs.

[0131] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the accompanying drawings. The wireless communication methods of each embodiment can be applied individually or in combination.

[0132] In this disclosure, the panel, uplink (UL) transmitting entity, TRP, spatial relationship, control resource set (CORESET), PDSCH, codeword, base station, antenna port of a signal (e.g., DeModulation Reference Signal (DMRS) port), antenna port group of a signal (e.g., DMRS port group), group for multiplexing (e.g., Code Division Multiplexing (CDM) group, reference signal group, CORESET group), CORESET pool, CW, redundancy version (RV)), and layer (MIMO layer, transmitting layer, spatial layer) can also be interchanged. Furthermore, the panel identifier (ID) and the panel can also be interchanged. In this disclosure, the TRP ID and TRP can also be interchanged.

[0133] In this disclosure, NCJT, NCJT using multiple TRPs, multiple PDSCHs using NCJT, multiple PDSCHs, and multiple PDSCHs from multiple TRPs are interchangeable. Furthermore, multiple PDSCHs can mean multiple PDSCHs with at least a portion (e.g., one symbol) of overlapping time resources, multiple PDSCHs with all (e.g., all symbols) of overlapping time resources, multiple PDSCHs with no overlap in time resources, multiple PDSCHs carrying the same TB or the same CW, or multiple PDSCHs applying different UE beams (spatial domain receive filter, QCL parameters).

[0134] In this disclosure, the default TCI state can also be interchanged with the default QCL, the default QCL concept, etc. Hereinafter, this TCI state or QCL (QCL concept) will be referred to as the default TCI state, but the name is not limited to this.

[0135] Furthermore, the definition of the default TCI state is not limited to this. For example, the default TCI state can be either the TCI state / QCL that is not available for a certain channel / signal (e.g., PDSCH) as specified by the DCI, or the TCI state / QCL that is not specified (or set).

[0136] In this disclosure, cell, CC, carrier, BWP, and band can also be interchanged.

[0137] In this disclosure, index, ID, indicator, and resource ID are interchangeable.

[0138] TCI status, TCI status or QCL designation, QCL designation, QCL parameters, spatial domain receive filter, UE spatial domain receive filter, spatial domain filter, UE receive beam, DL receive beam, DL precoding, DL precoder, DL-RS, QCL parameters followed by the DMRS port, RS of QCL type D in TCI status or QCL designation, and RS of QCL type A in TCI status or QCL designation can also be interchanged. RS of QCL type D, DL-RS associated with QCL type D, DL-RS with QCL type D, source of DL-RS, SSB, and CSI-RS can also be interchanged.

[0139] In this disclosure, the TCI state can also be information related to the receive beam (spatial domain receive filter) indicated (set) to the UE (e.g., DL-RS, QCL type, cell in which DL-RS is transmitted, etc.). The QCL assumption can also be information related to the receive beam (spatial domain receive filter) assumed by the UE based on the transmission or reception of associated signals (e.g., PRACH) (e.g., DL-RS, QCL type, cell in which DL-RS is transmitted, etc.).

[0140] In this disclosure, the latest time slot, the most recent time slot, the latest search space, and the most recent search space may be used interchangeably.

[0141] In this disclosure, DCI format 0_0, DCI without SRI, DCI without spatial relation indication, and DCI without CIF can be interchanged. In this disclosure, DCI format 0_1, DCI with SRI, DCI with spatial relation indication, and DCI with CIF can also be interchanged.

[0142] (First method)

[0143] In the first approach, the case in which at least one of a single DCI and multiple DCI is set to control the reception processing of the PDSCH is described.

[0144] A single DCI can also be referred to as a single DCI or single PDCCH for multi-point TRP (M-TRP). Conversely, a multiple DCI can also be referred to as a multiple DCI or multiple PDCCH for multi-point TRP (M-TRP).

[0145] Setting at least one of single DCI and multiple DCI can also be replaced by setting at least one of monitoring PDCCH (or CORESET) for single DCI and monitoring PDCCH (or CORESET) for multiple DCI. Setting at least one of single DCI and multiple DCI can also be applied for a specific period.

[0146] <Single DCI configuration>

[0147] It is also possible to control the setting so that, during a specific period, a single DCI (or a CORESET for a single DCI) is set while multiple DCIs (or CORESETs for multiple DCIs) are not set (see [reference]). Figure 5A If a UE is configured with a single DCI (or a CORESET for a single DCI), it is not necessary to assume that multiple DCIs (or CORESETs for multiple DCIs) will be configured.

[0148] The settings for a single DCI can also be set to the UE from the network (e.g., base station) via higher-layer signaling. When the scheduling offset is shorter than a specific period (e.g., the QCL time length), the UE can also perform PDSCH reception processing (e.g., demodulation or decoding) based on the default QCL corresponding to the single DCI (or the CORESET used by the single DCI).

[0149] Even when a CORESET for multiple DCIs is set, the UE may not perform reception processing for PDSCHs scheduled by that CORESET (e.g., PDSCHs with a scheduling offset below a certain value). Alternatively, when a CORESET for multiple DCIs is set, the UE may assume that PDSCHs with a scheduling offset below a certain value have not been scheduled.

[0150] Furthermore, all cores set on the UE (or cores instructed to be monitored) can also be set for single DCI use. In this case, the UE can also be configured to use single DCI for all set cores.

[0151] In this way, when a single DCI is set, the UE can also assume the default QCL corresponding to the single DCI (or the CORESET used by the single DCI) and perform PDSCH reception processing, thereby enabling appropriate PDSCH reception.

[0152] <Situation where multiple DCIs are set>

[0153] It is also possible to control the setting so that multiple DCIs (or CORESETs for multiple DCIs) are set while a single DCI (or CORESETs for a single DCI) is not set during a specific period (see [reference]). Figure 5B The UE can also assume that a single DCI (or a single DCI CORESET) is not configured when multiple DCIs (or CORESETs used for multiple DCIs) are configured.

[0154] Multiple DCI settings can also be configured to the UE from the network (e.g., base station) via higher-layer signaling. When the scheduling offset is shorter than a specific period (e.g., QCL usage time length), the UE can also perform PDSCH reception processing (e.g., demodulation or decoding processing) based on the default QCL corresponding to the multiple DCI (or the CORESET used by the multiple DCI).

[0155] Even when the CORESET for a single DCI is set, the UE may not perform reception processing for PDSCHs scheduled by that CORESET (e.g., PDSCHs with a scheduling offset below a certain value). Alternatively, when the CORESET for a single DCI is set, the UE may assume that PDSCHs with a scheduling offset below a certain value have not been scheduled.

[0156] Alternatively, all cores set on the UE (or cores that are instructed to be monitored) can be configured for multi-DCI use. In this case, the UE can also be configured to use all set cores for multi-DCI use.

[0157] In this way, when multiple DCIs are configured, the UE can perform PDSCH reception processing by envisioning the default QCL corresponding to the multiple DCIs (or the CORESET used by the multiple DCIs), thereby enabling appropriate PDSCH reception.

[0158] (Second method)

[0159] In the second approach, a case is described where control is implemented to prevent the reception processing of PDSCH using different default QCLs during a specific period (e.g., a specific time interval).

[0160] The UE may also choose not to perform PDSCH reception processing based on different default QCLs for PDSCH within a specific time interval. Different default QCLs may also include, for example, the default QCL for PDSCH defined in the existing system (e.g., Rel. 15), the default QCL for single DCI (or PDSCH scheduled by single DCI), and the default QCL for multiple DCI (or PDSCH scheduled by multiple DCI).

[0161] Specific time intervals can also be defined using specific time units. These specific time units can be determined by combinations of time slot units, symbol units, or a combination of time slot units and symbol units. For example, a specific time interval can be at least one of the following time intervals A-1 to A-3. Of course, time intervals are not limited to these.

[0162] A-1: The time slot of the CORESET (or CORESET search space) used by the configured single DCI.

[0163] A-2: Symbols within a specific period from the core set (or the search space of the core set) used by a single DCI to the code used by the QCL.

[0164] A-3: Includes one or more time slots from the CORESET (or the CORESET search space) used by a single DCI to the symbol within a specific period set for QCL.

[0165] The specific period set for QCL can be configured to the UE from the base station via higher-layer parameters (e.g., timeDurationForQCL). The specific period set for QCL can also be configured separately for each subcarrier interval.

[0166] Figure 6 This illustrates a scenario where the QCL for a single DCI CORESET is set for the first half of time slots #0 to #1 during a specific period. In this case, since the specific time interval is determined based on time interval A-3, the UE can also determine that the specific time interval traverses time slots #0 to #1 (the first two time slots) and is set accordingly.

[0167] The UE can also control the reception processing to utilize the PDSCH of the QCL for the CORESET used for a single DCI within a specific time interval. In other words, the UE can also control the reception processing to not utilize the PDSCH of a QCL different from the QCL of the CORESET used for a single DCI within a specific time interval.

[0168] Furthermore, this section illustrates a case where PDSCH reception processing is performed according to the QCL concept corresponding to a single DCI (or a CORESET for a single DCI), but it is not limited to this. When performing PDSCH reception processing according to the QCL concept corresponding to multiple DCIs, the single DCI can be replaced with multiple DCIs within specific time intervals in A-1 to A-3 above.

[0169] In this way, the UE can control the PDSCH reception process to not perform PDSCH reception processing based on different default QCLs within a specific time interval, so that PDSCH reception processing can be performed appropriately even when multiple default QCLs are supported.

[0170] (Third method)

[0171] In the third approach, the case where the application of a QCL (or QCL concept) is determined based on specific rules is explained when receiving PDSCHs that utilize different default QCLs during a specific period (e.g., a specific time interval).

[0172] When supporting PDSCH reception processing based on different default QCLs (e.g., the default QCL used for PDSCH) within a specific time interval, the UE can also determine the QCL assumption for that specific time interval based on specific rules. In the case of supporting PDSCH reception processing based on different default QCLs, it can also be replaced by setting multiple CORESETs corresponding to different default QCLs.

[0173] Specific rules can also be set to at least one of the priorities of each QCL (or the default QCL assumption) and the timing of PDCCH monitoring (e.g., the order of monitoring).

[0174] The UE may also determine the QCL to be applied in a specific time interval (or the QCL concept for a specific time interval) based on at least one of the following priorities 1 to 4.

[0175] <Priority 1>

[0176] Alternatively, priorities can be set according to the default QCL defined in the existing system (e.g., Rel.15) > QCL corresponding to a single DCI > QCL corresponding to multiple DCIs. For example, imagine a scenario where monitoring of the CORESET corresponding to a single DCI used with multiple TRPs, monitoring of the CORESET corresponding to multiple DCIs used with multiple TRPs, and monitoring of other CORESETs (e.g., CORESET corresponding to DCIs other than those used with multiple TRPs) are set.

[0177] When a CORESET corresponding to a single DCI and a CORESET corresponding to multiple DCIs are allocated within a specific time interval, PDSCH reception processing can also be performed based on the QCL assumption of the CORESET corresponding to a single DCI (see [reference]). Figure 7A In this way, by setting the priority corresponding to a single DCI to be higher than the priority corresponding to multiple DCIs, the PDSCH reception processing can be prioritized when a PDSCH for a service type requiring low latency (e.g., URLLC) is scheduled by a single DCI.

[0178] <Priority 2>

[0179] Alternatively, priorities can be set according to the default QCL defined in the existing system (e.g., Rel.15) > QCL corresponding to multiple DCIs > QCL corresponding to a single DCI. For example, consider a scenario where monitoring of the CORESET corresponding to a single DCI used for multiple TRPs, monitoring of the CORESET corresponding to multiple DCIs used for multiple TRPs, and monitoring of other CORESETs (e.g., CORESET corresponding to DCIs other than those used for multiple TRPs) are set.

[0180] When a core set corresponding to a single DCI and a core set corresponding to multiple DCIs are allocated within a specific time interval, PDSCH reception processing can also be performed based on the QCL assumption of the core set corresponding to multiple DCIs (see [reference]). Figure 7B When using the default QCL corresponding to multiple DCIs, operations similar to those envisioned for the default QCL in existing systems can be performed. Therefore, by setting the priority corresponding to multiple DCIs higher than that corresponding to a single DCI, backward compatibility can be ensured.

[0181] <Priority 3>

[0182] Alternatively, priorities can be set according to the order of QCL corresponding to the DCI used in multiple TRPs > the default QCL defined in the existing system (e.g., Rel. 15). The priority of the DCI used in multiple TRPs can also be set to QCL corresponding to a single DCI > QCL corresponding to multiple DCIs, or QCL corresponding to multiple DCIs > QCL corresponding to a single DCI. Alternatively, settings that do not consider conflicts or simultaneous monitoring of single DCIs (or their corresponding CORESETs) and multiple DCIs (or their corresponding CORESETs) can be implemented.

[0183] <Priority 4>

[0184] Alternatively, priorities can be set according to the order of QCL corresponding to the DCI used in multiple TRPs > the default QCL defined in the existing system (e.g., Rel. 15). The priority of the DCI used in multiple TRPs can also be set to QCL corresponding to a single DCI > QCL corresponding to multiple DCIs, or QCL corresponding to multiple DCIs > QCL corresponding to a single DCI. Alternatively, settings that do not consider conflicts or simultaneous monitoring of single DCIs (or their corresponding CORESETs) and multiple DCIs (or their corresponding CORESETs) can be implemented.

[0185] The UE can also determine the default QCL to be applied to the PDSCH reception processing based on the order (first / last) of the PDCCH monitoring timing for scheduling the PDSCH, rather than priority 1-4. For example, the UE can also use the default QCL corresponding to the earliest set or configured CORESET for PDSCH reception processing within a specific time interval. Alternatively, the UE can also use the default QCL corresponding to the latest set or configured CORESET for PDSCH reception processing within a specific time interval.

[0186] (Fourth method)

[0187] In the fourth approach, it is explained that when receiving PDSCH using different default QCLs is supported during a specific period (e.g., a specific time interval), control is performed to ensure that PDSCH receiving is performed according to the QCL assumption determined based on specific rules, and PDSCH receiving is not performed according to other QCL assumptions.

[0188] When the UE performs PDSCH reception processing according to a QCL assumption determined based on specific rules, it can also be configured such that the UE is not requested to receive PDSCH based on a different QCL assumption than the determined QCL (see [link to relevant documentation]). Figure 8 A specific rule can be any of the rules shown in the third approach.

[0189] Figure 8 The diagram illustrates a scenario where PDSCH reception processing is performed based on a specific rule and the QCL corresponding to the CORESET used for a single DCI is assumed, and PDSCH reception processing corresponding to other QCLs (QCLs corresponding to the CORESET used for multiple DCIs) is not assumed or performed.

[0190] The situation where PDSCH reception is not requested, based on other QCL assumptions, can also be any of the following.

[0191] • The UE does not assume that the PDSCH corresponding to other QCLs will be scheduled.

[0192] Even if the PDSCH corresponding to other QCLs is scheduled, the UE will not be requested to receive the PDSCH (e.g., decoding or demodulation).

[0193] • If the PDSCH corresponding to other QCLs is scheduled, the UE ignores the scheduling.

[0194] Therefore, even when multiple default QCLs are supported within a specific time interval, PDSCH reception processing can be appropriately performed based on the specific QCL assumption.

[0195] (Modified Example)

[0196] Methods one through four are illustrated using the default QCL used by PDSCH as an example, but are not limited to this. For example, the default QCL used for other signals or channels (e.g., aperiodic CSI-RS (A-CSI-RS)) can also be applied in the same way.

[0197] (Wireless Communication System)

[0198] The structure of a wireless communication system according to one embodiment of this disclosure will now be described. In this wireless communication system, communication is performed using any one or a combination of the wireless communication methods according to the above embodiments of this disclosure.

[0199] Figure 9 This is a diagram illustrating an example of the schematic structure of a wireless communication system according to one embodiment. The wireless communication system 1 may also be a system that uses Long Term Evolution (LTE) or 5th generation mobile communication system New Radio (5G NR) as standardized by the Third Generation Partnership Project (3GPP).

[0200] Furthermore, the wireless communication system 1 can also support dual connectivity between multiple radio access technologies (RATs) (Multi-RAT Dual Connectivity (MR-DC)). MR-DC can also include dual connectivity between LTE (Evolved Universal Terrestrial Radio Access (E-UTRA)) and NR (E-UTRA-NR Dual Connectivity (EN-DC)), dual connectivity between NR and LTE (NR-E-UTRA Dual Connectivity (NE-DC)), etc.

[0201] In EN-DC, the LTE (E-UTRA) base station (eNB) is the master node (MN), and the NR base station (gNB) is the secondary node (SN). In NE-DC, the NR base station (gNB) is the MN, and the LTE (E-UTRA) base station (eNB) is the SN.

[0202] The wireless communication system 1 can also support dual connectivity between multiple base stations within the same RAT (e.g., dual connectivity between base stations (gNB) where both MN and SN are NR (NR-NR Dual Connectivity (NN-DC))).

[0203] The wireless communication system 1 may also include a base station 11 forming a macro cell C1 with a relatively wide coverage area, and a base station 12 (12a-12c) configured within the macro cell C1 and forming a small cell C2 narrower than the macro cell C1. The user terminal 20 may also be located within at least one cell. The configuration and number of each cell and the user terminal 20 are not limited to the arrangement shown in the figure. Hereinafter, without distinguishing between base stations 11 and 12, they will be collectively referred to as base station 10.

[0204] User terminal 20 may also connect to at least one of the plurality of base stations 10. User terminal 20 may also utilize at least one of carrier aggregation (CA) using multiple component carriers (CC) and dual connectivity (DC).

[0205] Each CC can also be included in at least one of the first frequency band (Frequency Range 1 (FR1)) and the second frequency band (Frequency Range 2 (FR2)). Macro cell C1 can also be included in FR1, and small cell C2 can also be included in FR2. For example, FR1 can also be a frequency band below 6 GHz (sub-6 GHz), and FR2 can also be a frequency band above 24 GHz (above-24 GHz). In addition, the frequency bands and definitions of FR1 and FR2 are not limited to these; for example, FR1 can also be equivalent to a frequency band higher than FR2.

[0206] In addition, in each CC, user terminal 20 can also use at least one of Time Division Duplex (TDD) and Frequency Division Duplex (FDD) for communication.

[0207] Multiple base stations 10 can also be connected via wired (e.g., fiber optic, X2 interface, etc., conforming to the Common Public Radio Interface (CPRI)) or wireless (e.g., NR communication). For example, when NR communication between base stations 11 and 12 is used for backhaul, base station 11, which is equivalent to a host station, can also be referred to as an Integrated Access Backhaul (IAB) host, and base station 12, which is equivalent to a relay station, can also be referred to as an IAB node.

[0208] Base station 10 can also be connected to core network 30 via other base stations 10 or directly. Core network 30 may include at least one of Evolved Packet Core (EPC), 5G Core Network (5GCN), Next Generation Core (NGC), etc.

[0209] User terminal 20 can also be a terminal that supports at least one of the following communication methods: LTE, LTE-A, 5G, etc.

[0210] In wireless communication system 1, wireless access methods based on Orthogonal Frequency Division Multiplexing (OFDM) can also be utilized. For example, in at least one of the downlink (DL) and uplink (UL) links, Cyclic Prefix OFDM (CP-OFDM), Discrete Fourier Transform Spread OFDM (DFT-s-OFDM), Orthogonal Frequency Division Multiple Access (OFDMA), and Single Carrier Frequency Division Multiple Access (SC-FDMA) can also be utilized.

[0211] The wireless access method can also be referred to as a waveform. In addition, in the wireless communication system 1, other wireless access methods (e.g., other single-carrier transmission methods, other multi-carrier transmission methods) can also be used for the wireless access methods of UL and DL.

[0212] As a downlink channel, the wireless communication system 1 can also use downlink shared channels (Physical Downlink Shared Channel (PDSCH)), broadcast channels (Physical Broadcast Channel (PBCH)), downlink control channels (Physical Downlink Control Channel (PDCCH)) and so on, which are shared by each user terminal 20.

[0213] In addition, as uplink channels, the wireless communication system 1 may also use uplink shared channels (Physical Uplink Shared Channel (PUSCH)), uplink control channels (Physical Uplink Control Channel (PUCCH)), random access channels (Physical Random Access Channel (PRACH)) and so on, which are shared by each user terminal 20.

[0214] User data, high-level control information, and System Information Blocks (SIBs) are transmitted via the PDSCH. User data and high-level control information can also be transmitted via the PUSCH. Furthermore, the Master Information Block (MIB) can also be transmitted via the PBCH.

[0215] Lower-layer control information can also be transmitted via PDCCH. This lower-layer control information may include, for example, downlink control information (DCI) containing scheduling information from at least one of PDSCH and PUSCH.

[0216] Additionally, the DCI that schedules PDSCH can also be called DL allocation, DL DCI, etc., and the DCI that schedules PUSCH can also be called UL authorization, UL DCI, etc. Furthermore, PDSCH can also be replaced with DL data, and PUSCH can also be replaced with UL data.

[0217] Detection of PDCCHs can also utilize a Control Resource Set (CORESET) and a search space. A CORESET corresponds to the resources used to search for DCIs. The search space corresponds to the search area and search method for PDCCH candidates. A CORESET can also be associated with one or more search spaces. The UE can also monitor CORESETs associated with a specific search space based on search space settings.

[0218] A search space can also correspond to one or more PDCCH candidates with an aggregation level equivalent to one or more aggregation levels. One or more search spaces can also be referred to as a search space set. In addition, the terms "search space", "search space set", "search space setting", "search space set setting", "CORESET", and "CORESET setting" used in this disclosure can be used interchangeably.

[0219] Uplink control information (UCI) containing at least one of the following can also be transmitted via PUCCH: Channel State Information (CSI), Delivery Acknowledgment (e.g., also known as Hybrid Automatic Repeat reQuest (HARQ-ACK), ACK / NACK, etc.), and Scheduling Request (SR). Random access preambles used for establishing a connection with the cell can also be transmitted via PRACH.

[0220] Furthermore, in this disclosure, downlink, uplink, etc., may be represented without being assigned the term "link". Additionally, the term "physical" may be omitted from the beginning of various channels.

[0221] In wireless communication system 1, synchronization signals (SS) and downlink reference signals (DL-RS) can also be transmitted. In wireless communication system 1, as DL-RS, cell-specific reference signals (CRS), channel state information reference signals (CSI-RS), demodulation reference signals (DMRS), positioning reference signals (PRS), and phase tracking reference signals (PTRS) can also be transmitted.

[0222] Synchronization signals can be, for example, at least one of the primary synchronization signal (PSS) and the secondary synchronization signal (SSS). A signal block containing SS (PSS, SSS) and PBCH (and DMRS for PBCH) can also be called an SS / PBCH block, SS block (SSB), etc. Furthermore, SS, SSB, etc., can also be called reference signals.

[0223] Furthermore, in the wireless communication system 1, measurement reference signals (sounding reference signals (SRS)) and demodulation reference signals (DMRS) can also be transmitted as uplink reference signals (UL-RS). Additionally, DMRS can also be referred to as user terminal-specific reference signals (UE-specific reference signals).

[0224] (Base station)

[0225] Figure 10 This diagram illustrates an example of the structure of a base station according to one embodiment. The base station 10 includes a control unit 110, a transmit / receive unit 120, a transmit / receive antenna 130, and a transmission line interface 140. Alternatively, the control unit 110, the transmit / receive unit 120, the transmit / receive antenna 130, and the transmission line interface 140 may each be provided in more than one form.

[0226] Furthermore, while this example primarily illustrates the functional blocks of the characteristic portions of this embodiment, it is also conceivable that the base station 10 may have other functional blocks required for wireless communication. Some of the processing of each unit described below may also be omitted.

[0227] The control unit 110 performs overall control of the base station 10. The control unit 110 can be composed of a controller, control circuit, etc., which are described based on common knowledge in the art to which this disclosure pertains.

[0228] The control unit 110 can also control signal generation and scheduling (e.g., resource allocation, mapping). The control unit 110 can also control transmission, reception, and measurement using the transmit / receive unit 120, transmit / receive antenna 130, and transmission path interface 140. The control unit 110 can also generate data, control information, sequences, etc., to be transmitted as signals and forward them to the transmit / receive unit 120. The control unit 110 can also perform call processing (setting, releasing, etc.) of the communication channel, status management of the base station 10, and management of radio resources.

[0229] The transmitting / receiving unit 120 may also include a baseband unit 121, a radio frequency (RF) unit 122, and a measurement unit 123. The baseband unit 121 may also include a transmitting processing unit 1211 and a receiving processing unit 1212. The transmitting / receiving unit 120 can be composed of transmitters / receivers, RF circuits, baseband circuits, filters, phase shifters, measurement circuits, transmitting / receiving circuits, etc., as described based on common knowledge in the art to which this disclosure pertains.

[0230] The transmitting and receiving unit 120 can also be configured as an integrated transmitting and receiving unit, or it can be composed of a transmitting unit and a receiving unit. The transmitting unit can also be composed of a transmitting processing unit 1211 and an RF unit 122. The receiving unit can also be composed of a receiving processing unit 1212, an RF unit 122, and a measurement unit 123.

[0231] The transmitting and receiving antenna 130 can be constructed from an antenna, such as an array antenna, as described based on common knowledge in the art to which this disclosure pertains.

[0232] The transmitting / receiving unit 120 can also transmit the aforementioned downlink channel, synchronization signal, downlink reference signal, etc. The transmitting / receiving unit 120 can also receive the aforementioned uplink channel, uplink reference signal, etc.

[0233] The transmitting and receiving unit 120 may also use digital beamforming (e.g., precoding), analog beamforming (e.g., phase rotation), etc., to form at least one of the transmitting beam and the receiving beam.

[0234] The transmitting and receiving unit 120 (transmitting processing unit 1211) may, for example, process the data and control information obtained from the control unit 110 through the Packet Data Convergence Protocol (PDCP) layer, the Radio Link Control (RLC) layer (e.g., RLC retransmission control), and the Medium Access Control (MAC) layer (e.g., HARQ retransmission control) to generate a bit string to be transmitted.

[0235] The transmitting and receiving unit 120 (transmitting processing unit 1211) can also perform channel coding (which may include error correction coding), modulation, mapping, filtering, Discrete Fourier Transform (DFT) processing (as needed), Inverse Fast Fourier Transform (IFFT) processing, precoding, digital-to-analog conversion and other transmission processing on the bit string to be transmitted, and output the baseband signal.

[0236] The transmitting and receiving unit 120 (RF unit 122) can also perform modulation, filtering, amplification, etc. of the baseband signal on the wireless frequency band, and transmit the wireless frequency band signal through the transmitting and receiving antenna 130.

[0237] On the other hand, the transmitting and receiving unit 120 (RF unit 122) amplifies, filters, and demodulates the baseband signal received by the transmitting and receiving antenna 130 in the wireless frequency band.

[0238] The transmitting and receiving unit 120 (receiving and processing unit 1212) performs receiving and processing on the acquired baseband signal, including analog-to-digital conversion, Fast Fourier Transform (FFT) processing, Inverse Discrete Fourier Transform (IDFT) processing (as needed), filtering, demapping, demodulation, decoding (which may also include error correction decoding), MAC layer processing, RLC layer processing, and PDCP layer processing, to obtain user data.

[0239] The transmitting / receiving unit 120 (measurement unit 123) can also perform measurements related to the received signal. For example, the measurement unit 123 can also perform radio resource management (RRM) measurements, channel state information (CSI) measurements, etc., based on the received signal. The measurement unit 123 can also measure received power (e.g., Reference Signal Received Power (RSRP)), received quality (e.g., Reference Signal Received Quality (RSRQ), Signal to Interference plus Noise Ratio (SINR), Signal to Noise Ratio (SNR)), signal strength (e.g., Received Signal Strength Indicator (RSSI)), propagation path information (e.g., CSI), etc. The measurement results can also be output to the control unit 110.

[0240] The transmission path interface 140 can also transmit and receive signals (backhaul signaling notification) between devices included in the core network 30 and other base stations 10, and obtain and transmit user data (user plane data), control plane data, etc. for user terminal 20.

[0241] In addition, the transmitting unit and receiving unit of the base station 10 in this disclosure may also be composed of at least one of the transmitting and receiving unit 120, the transmitting and receiving antenna 130 and the transmission path interface 140.

[0242] The transmitting and receiving unit 120 may also transmit one downlink control information used to schedule multiple downlink shared channels (PDSCH), and at least one of multiple downlink control information used to schedule multiple PDSCH.

[0243] The control unit 110 can also control the setting of one of the downlink control information or the first control resource set, and one of the multiple downlink control information or the second control resource set during a specific period.

[0244] (User terminal)

[0245] Figure 11This diagram illustrates an example of the structure of a user terminal according to one embodiment. The user terminal 20 includes a control unit 210, a transmitting / receiving unit 220, and a transmitting / receiving antenna 230. Alternatively, more than one of each of the control unit 210, the transmitting / receiving unit 220, and the transmitting / receiving antenna 230 may be included.

[0246] Furthermore, while this example primarily illustrates the functional blocks of the characteristic portions of this embodiment, it is also conceivable that the user terminal 20 may also have other functional blocks required for wireless communication. Some of the processing of each unit described below may also be omitted.

[0247] The control unit 210 performs overall control of the user terminal 20. The control unit 210 can be composed of a controller, control circuit, etc., which are described based on common knowledge in the technical field to which this disclosure pertains.

[0248] The control unit 210 can also control signal generation, mapping, etc. The control unit 210 can also control transmission, reception, measurement, etc., using the transmission / reception unit 220 and the transmission / reception antenna 230. The control unit 210 can also generate data, control information, sequences, etc., to be transmitted as signals and forward them to the transmission / reception unit 220.

[0249] The transmitting / receiving unit 220 may also include a baseband unit 221, an RF unit 222, and a measurement unit 223. The baseband unit 221 may also include a transmitting processing unit 2211 and a receiving processing unit 2212. The transmitting / receiving unit 220 may be composed of transmitters / receivers, RF circuits, baseband circuits, filters, phase shifters, measurement circuits, transmitting / receiving circuits, etc., as described based on common knowledge in the art to which this disclosure pertains.

[0250] The transmitting and receiving unit 220 can also be configured as a single unit, or it can be composed of a transmitting unit and a receiving unit. The transmitting unit can also be composed of a transmitting processing unit 2211 and an RF unit 222. The receiving unit can also be composed of a receiving processing unit 2212, an RF unit 222, and a measurement unit 223.

[0251] The transmitting and receiving antenna 230 can be constructed from an antenna, such as an array antenna, as described based on common knowledge in the art to which this disclosure pertains.

[0252] The transmitting / receiving unit 220 can also receive the downlink channel, synchronization signal, downlink reference signal, etc., mentioned above. The transmitting / receiving unit 220 can also transmit the uplink channel, uplink reference signal, etc., mentioned above.

[0253] The transmitting and receiving unit 220 may also use digital beamforming (e.g., precoding), analog beamforming (e.g., phase rotation), etc., to form at least one of the transmitting beam and the receiving beam.

[0254] The transmitting and receiving unit 220 (transmitting processing unit 2211) may, for example, perform PDCP layer processing, RLC layer processing (e.g., RLC retransmission control), MAC layer processing (e.g., HARQ retransmission control) on the data and control information obtained from the control unit 210, and generate the bit string to be transmitted.

[0255] The transmitting and receiving unit 220 (transmitting processing unit 2211) can also perform channel coding (which may include error correction coding), modulation, mapping, filtering, DFT processing (as needed), IFFT processing, precoding, digital-to-analog conversion and other transmission processing on the bit string to be transmitted, and output the baseband signal.

[0256] Furthermore, whether or not to apply DFT processing can also be based on the setting of transform precoding. If transform precoding is enabled for a certain channel (e.g., PUSCH), the transmit / receive unit 220 (transmit processing unit 2211) can perform DFT processing as the aforementioned transmission processing in order to transmit the channel using a DFT-s-OFDM waveform; otherwise, it can perform DFT processing without performing DFT processing as the aforementioned transmission processing.

[0257] For baseband signals, the transmitting and receiving unit 220 (RF unit 222) can also perform modulation, filtering, amplification, etc. of the wireless frequency band, and transmit the wireless frequency band signals through the transmitting and receiving antenna 230.

[0258] On the other hand, the transmitting and receiving unit 220 (RF unit 222) can also amplify, filter, demodulate baseband signals, etc., the signals of the wireless frequency band received by the transmitting and receiving antenna 230.

[0259] The transmitting and receiving unit 220 (receiving and processing unit 2212) can also perform receiving and processing on the acquired baseband signal, such as analog-to-digital conversion, FFT processing, IDFT processing (as needed), filtering processing, demapping, demodulation, decoding (which may also include error correction decoding), MAC layer processing, RLC layer processing, and PDCP layer processing, to obtain user data.

[0260] The transmitting / receiving unit 220 (measurement unit 223) can also perform measurements related to the received signal. For example, the measurement unit 223 can also perform RRM measurements, CSI measurements, etc., based on the received signal. The measurement unit 223 can also measure received power (e.g., RSRP), received quality (e.g., RSRQ, SINR, SNR), signal strength (e.g., RSSI), propagation path information (e.g., CSI), etc. The measurement results can also be output to the control unit 210.

[0261] Alternatively, the transmitting and receiving units of the user terminal 20 in this disclosure may also be composed of at least one of the transmitting and receiving unit 220 and the transmitting and receiving antenna 230.

[0262] The transmitting and receiving unit 220 can also receive one downlink control information used to schedule multiple downlink shared channels (PDSCH), and at least one of multiple downlink control information used to schedule multiple PDSCH.

[0263] The control unit 210 can also control the reception of the plurality of PDSCHs during a specific period based on at least one of the quasi-co-address corresponding to a first control resource set for one downlink control information and the quasi-co-address corresponding to a plurality of second control resource sets for multiple downlink control information.

[0264] For example, the control unit 210 can also be conceived as follows: during a specific period, if one of a downlink control information or a first control resource set and multiple downlink control information or a second control resource set is set, the other is not set.

[0265] Alternatively, the control unit 210 can also control the reception of PDSCHs utilizing different quasi-co-addresses during a specific period.

[0266] Alternatively, if different quasi-co-addresses are set within a specific period, the control unit 210 may determine the specific quasi-co-address for PDSCH reception based on at least one of the priority corresponding to each quasi-co-address and the monitoring timing of the downlink control channel corresponding to the PDSCH. In this case, the control unit 210 may also be designed to prevent reception of PDSCHs from being requested to utilize other quasi-co-addresses different from the specific quasi-co-address.

[0267] (Hardware Structure)

[0268] Furthermore, the block diagrams used in the above description of the embodiments represent functional units. These functional blocks (structural units) are implemented through any combination of at least one of hardware and software. Moreover, the implementation method of each functional block is not particularly limited. That is, each functional block can be implemented using a single device that is physically or logically combined, or it can be implemented by directly and / or indirectly (e.g., using wired, wireless, etc.) connecting two or more physically or logically separate devices. Functional blocks can also be implemented by combining software with the aforementioned single device or multiple devices.

[0269] Here, the functions include judgment, decision, determination, calculation, calculation, processing, derivation, investigation, search, confirmation, receiving, sending, output, access, resolution, selection, selection, establishment, comparison, assumption, expectation, consideration, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, and assigning, but are not limited to these. For example, the functional block (structural part) that enables sending can also be called a transmitting unit, transmitter, etc. As mentioned above, the implementation method is not particularly limited for any of them.

[0270] For example, the base station, user terminal, etc. in one embodiment of this disclosure can function as a computer for processing the wireless communication method of this disclosure. Figure 12 This diagram illustrates an example of the hardware structure of a base station and a user terminal according to one embodiment. The base station 10 and the user terminal 20 can physically be configured as a computer device including a processor 1001, a memory 1002, a storage device 1003, a communication device 1004, an input device 1005, an output device 1006, and a bus 1007.

[0271] Furthermore, in this disclosure, terms such as apparatus, circuit, device, section, and unit are interchangeable. The hardware structure of the base station 10 and the user terminal 20 can be configured to include one or more of the apparatuses shown in the figures, or it can be configured without including any of the apparatuses.

[0272] For example, only one processor 1001 is illustrated, but there can be multiple processors. Furthermore, processing can be executed by one processor, or it can be executed simultaneously, sequentially, or by two or more processors using other methods. Additionally, processor 1001 can be implemented using more than one chip.

[0273] The functions of the base station 10 and the user terminal 20 are implemented, for example, by reading specific software (programs) into hardware such as the processor 1001 and the memory 1002, which are then processed by the processor 1001 and controlled to communicate via the communication device 1004, or to control at least one of reading and writing data in the memory 1002 and the storage device 1003.

[0274] The processor 1001 controls the computer as a whole by enabling the operating system to operate. The processor 1001 may be composed of a central processing unit (CPU) that includes interfaces with peripheral devices, control devices, arithmetic devices, registers, etc. For example, at least a part of the control unit 110 (210), the transmit / receive unit 120 (220), etc., described above may also be implemented by the processor 1001.

[0275] Furthermore, the processor 1001 reads programs (program code), software modules, data, etc., from at least one of the storage 1003 and the communication device 1004 into the memory 1002, and performs various processes based on them. As a program, a program is used that causes the computer to perform at least a portion of the operations described in the above embodiments. For example, the control unit 110 (210) can be implemented by a control program stored in the memory 1002 and operated in the processor 1001; similarly, other functional blocks can be implemented.

[0276] The memory 1002 is a computer-readable recording medium, and may be composed of at least one of the following: Read Only Memory (ROM), Erasable Programmable ROM (EPROM), Electrically EPROM (EEPROM), Random Access Memory (RAM), or other suitable storage media. The memory 1002 may also be referred to as a register, cache, main memory (main storage device), etc. The memory 1002 can store executable programs (program code), software modules, etc., for implementing a wireless communication method according to an embodiment of the present disclosure.

[0277] Storage 1003 is a computer-readable recording medium, which may consist of at least one of the following: flexible disk, floppy disk, optical disk (e.g., compact disc ROM (CD-ROM), digital multifunction disk, Blu-ray disc), removable disk, hard disk, smart card, flash memory device (e.g., card, stick, key drive), magnetic stripe, database, server, or other suitable storage media. Storage 1003 may also be referred to as an auxiliary storage device.

[0278] The communication device 1004 is hardware (transmitting and receiving device) used for communication between computers via at least one of a wired network and a wireless network. It is also referred to as a network device, network controller, network interface card (NIC), communication module, etc. The communication device 1004 may be configured to include a high-frequency switch, duplexer, filter, frequency synthesizer, etc., to implement at least one of Frequency Division Duplex (FDD) and Time Division Duplex (TDD). For example, the aforementioned transmit / receive units 120 (220) and 130 (230) may also be implemented by the communication device 1004. The transmit / receive unit 120 (220) may also be physically or logically separated by a transmit unit 120a (220a) and a receive unit 120b (220b).

[0279] Input device 1005 is an input device that receives input from external sources (e.g., keyboard, mouse, microphone, switch, button, sensor, etc.). Output device 1006 is an output device that performs output to external sources (e.g., display, speaker, light-emitting diode (LED) lamp, etc.). Alternatively, input device 1005 and output device 1006 can also be an integrated structure (e.g., touch panel).

[0280] Furthermore, the processor 1001, memory 1002, and other devices are connected via a bus 1007 for information communication. The bus 1007 can be constructed using a single bus or using different buses between devices.

[0281] Furthermore, the base station 10 and the user terminal 20 can be configured with hardware including a microprocessor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a programmable logic device (PLD), and a field-programmable gate array (FPGA), etc., and can also use this hardware to implement part or all of the functional blocks. For example, the processor 1001 can be implemented using at least one of these hardware components.

[0282] (Modified Example)

[0283] Furthermore, the terms used in this disclosure and / or those necessary for understanding this disclosure may be replaced with terms having the same or similar meanings. For example, channel, symbol, and signal (signal or signaling) may be used interchangeably. Additionally, a signal may also be a message. A reference signal may also be abbreviated as RS, and depending on the application standard, may also be referred to as a pilot, pilot signal, etc. Furthermore, a component carrier (CC) may also be referred to as a cell, frequency carrier, carrier frequency, etc.

[0284] A radio frame can also consist of one or more periods (frames) in the time domain. Each of these one or more periods (frames) constituting a radio frame can also be called a subframe. Furthermore, a subframe can also consist of one or more time slots in the time domain. A subframe can be a fixed time length (e.g., 1 ms) independent of a parameter set (numerology).

[0285] Here, the parameter set can also refer to communication parameters applied to at least one of the transmission and reception of a signal or channel. The parameter set can also represent at least one of the following: subcarrier spacing (SCS), bandwidth, symbol length, cyclic prefix length, transmission time interval (TTI), number of symbols per TTI, radio frame structure, specific filtering processing performed by the transmitter and receiver in the frequency domain, and specific windowing processing performed by the transmitter and receiver in the time domain.

[0286] A time slot can also be composed of one or more symbols (Orthogonal Frequency Division Multiplexing (OFDM) symbols, Single Carrier Frequency Division Multiple Access (SC-FDMA) symbols, etc.) in the time domain. Furthermore, a time slot can be a time unit based on a set of parameters.

[0287] A time slot can contain multiple mini-slots. Each mini-slot can consist of one or more symbols in the time domain. Furthermore, a mini-slot can also be called a sub-slot. A mini-slot can also consist of fewer symbols than a time slot. PDSCH (or PUSCH) transmitted in time units longer than a mini-slot can also be called PDSCH (PUSCH) mapping type A. PDSCH (or PUSCH) transmitted using mini-slots can also be called PDSCH (PUSCH) mapping type B.

[0288] Radio frames, subframes, time slots, mini-time slots, and symbols all refer to units of time for transmitting signals. Radio frames, subframes, time slots, mini-time slots, and symbols may also use other corresponding names. Furthermore, the time units for frames, subframes, time slots, mini-time slots, and symbols in this disclosure may be interchanged.

[0289] For example, a single subframe can also be called a TTI, multiple consecutive subframes can also be called a TTI, and a single time slot or a single mini-time slot can also be called a TTI. That is, at least one of a subframe or a TTI can be a subframe (1ms) in existing LTE, a period shorter than 1ms (e.g., 1-13 symbols), or a period longer than 1ms. Furthermore, the unit representing a TTI can also be called a time slot, mini-time slot, etc., instead of a subframe.

[0290] Here, TTI refers, for example, to the smallest unit of time for scheduling in wireless communication. For instance, in an LTE system, the base station schedules the allocation of radio resources (frequency bandwidth, transmit power, etc., available to each user terminal) in units of TTI. However, the definition of TTI is not limited to this.

[0291] TTI can be the transmission time unit for channel-coded data packets (transmission blocks), code blocks, codewords, etc., or it can be a processing unit for scheduling, link adaptation, etc. Furthermore, given a TTI, the actual time interval mapped to a transmission block, code block, codeword, etc. (e.g., the number of symbols) can be shorter than that TTI.

[0292] Furthermore, where one time slot or one mini-time slot is referred to as a TTI, more than one TTI (i.e., more than one time slot or more than one mini-time slot) can be the minimum time unit for scheduling. In addition, the number of time slots (number of mini-time slots) constituting the minimum time unit of the schedule can be controlled.

[0293] A TTI with a duration of 1ms can also be referred to as a normal TTI (TTI in 3GPP Rel.8-12), a normal TTI, a long TTI, a normal subframe, a long subframe, a time slot, etc. A TTI shorter than a normal TTI can also be referred to as a shortened TTI, a short TTI, a partial TTI (partial or fractional TTI), a shortened subframe, a short subframe, a mini time slot, a sub-time slot, a time slot, etc.

[0294] In addition, long TTIs (e.g., normal TTIs, subframes, etc.) can be replaced with TTIs with a duration of more than 1 ms, and short TTIs (e.g., shortened TTIs, etc.) can be replaced with TTIs with a duration of less than long TTIs but more than 1 ms.

[0295] A resource block (RB) is a unit of resource allocation in both the time and frequency domains. In the frequency domain, it can contain one or more consecutive subcarriers. The number of subcarriers contained in an RB can be the same regardless of the parameter set, for example, it can be 12. The number of subcarriers contained in an RB can also be determined based on the parameter set.

[0296] Furthermore, an RB can contain one or more symbols in the time domain, and can also be the length of one time slot, one mini-time slot, one subframe, or one TTI. One TTI and one subframe can also be composed of one or more resource blocks.

[0297] In addition, one or more RBs can also be referred to as Physical Resource Block (PRB), Sub-Carrier Group (SCG), Resource Element Group (REG), PRB pair, RB pair, etc.

[0298] In addition, a resource block can also consist of one or more resource elements (REs). For example, one RE can also be a radio resource area consisting of one subcarrier and one symbol.

[0299] The Bandwidth Part (BWP) (also referred to as partial bandwidth, etc.) can also represent a subset of contiguous common resource blocks (RBs) used for a parameter set within a carrier. Here, common RBs can also be determined by indexing RBs based on a common reference point of that carrier. PRBs can be defined by a BWP or assigned numbers within that BWP.

[0300] A BWP can also include a UL BWP (the BWP used by UL) and a DL BWP (the BWP used by DL). A UE can also be configured with one or more BWPs within a single carrier.

[0301] At least one of the configured BWPs may be active, and the UE may not intend to transmit or receive specific signals / channels outside of the active BWPs. In addition, "cell", "carrier", etc. in this disclosure may be replaced with "BWP".

[0302] Furthermore, the structures of radio frames, subframes, time slots, mini-time slots, and symbols described above are merely examples. For instance, the number of subframes contained in a radio frame, the number of time slots in each subframe or radio frame, the number of mini-time slots contained in a time slot, the number of symbols and RBs contained in a time slot or mini-time slot, the number of subcarriers contained in an RB, and the number of symbols within a TTI, symbol length, and cyclic prefix (CP) length can be varied.

[0303] Furthermore, the information, parameters, etc., described in this disclosure can be represented using absolute values, relative values ​​with respect to a specific value, or other corresponding information. For example, wireless resources can also be indicated by a specific index.

[0304] The names used for parameters, etc., in this disclosure are not limiting names at any point. Furthermore, the formulas, etc., using these parameters may differ from those explicitly disclosed in this disclosure. Various channels (PUCCH, PDCCH, etc.) and information elements can be identified by all appropriate names, and therefore the various names assigned to these various channels and information elements are not limiting names at any point.

[0305] The information, signals, etc., described in this disclosure can be represented using any of a variety of different technologies. For example, data, instructions, commands, information, signals, bits, symbols, and chips mentioned throughout the foregoing description can also be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or photons, or any combination thereof.

[0306] Furthermore, information and signals can be output in at least one of the following directions: from higher level (upper layer) to lower level (lower layer), and from lower layer to higher level. Information and signals can also be input and output via multiple network nodes.

[0307] Input and output information, signals, etc., can be stored in a specific area (e.g., memory) or managed using a management table. Input and output information, signals, etc., can also be overwritten, updated, or added. Output information, signals, etc., can also be deleted. Input information, signals, etc., can also be sent to other devices.

[0308] The notification of information is not limited to the methods / implementations described in this disclosure, and other methods may also be used. For example, the notification of information in this disclosure may be implemented by physical layer signaling (e.g., downlink control information (DCI), uplink control information (UCI), etc.), higher layer signaling (e.g., Radio Resource Control (RRC) signaling, broadcast information (Master Information Block (MIB), System Information Block (SIB), etc.), Medium Access Control (MAC) signaling), other signals, or combinations thereof.

[0309] In addition, physical layer signaling can also be referred to as Layer 1 / Layer 2 (L1 / L2) control information (L1 / L2 control signals), L1 control information (L1 control signals), etc. Furthermore, RRC signaling can also be referred to as RRC messages, for example, RRC Connection Setup messages, RRC Connection Reconfiguration messages, etc. Additionally, MAC signaling can be notified using, for example, MAC Control Element (CE).

[0310] Furthermore, notification of specific information (e.g., a notification that “is X”) is not limited to explicit notification, but can also be implicit (e.g., by not providing that specific information or by providing other information).

[0311] The determination can be made by a value represented by one bit (0 or 1), by a true or false value (Boolean), or by a numerical comparison (e.g., a comparison with a specific value).

[0312] Whether it is called software, firmware, middleware, microcode, hardware description language, or any other name, software should be broadly interpreted as referring to instructions, instruction sets, code, code segments, program code, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, procedures, functions, etc.

[0313] Furthermore, software, instructions, information, etc., can be sent and received via a transmission medium. For example, when software is sent from a website, server, or other remote source using at least one of wired technologies (coaxial cable, optical fiber, twisted pair, and Digital Subscriber Line (DSL) etc.) and wireless technologies (infrared, microwave, etc.), at least one of these wired and wireless technologies is included in the definition of transmission medium.

[0314] The terms “system” and “network” as used in this disclosure are used interchangeably. “Network” may also mean a device contained in a network (e.g., a base station).

[0315] In this disclosure, the terms “precoding”, “precoder”, “weight (precoding weight)”, “quasi-co-location (QCL)”, “transmission configuration indication state (TCI state)”, “spatial relation”, “spatial domain filter”, “transmit power”, “phase rotation”, “antenna port”, “antenna port group”, “layer”, “number of layers”, “rank”, “resource”, “resource set”, “resource group”, “beam”, “beamwidth”, “beam angle”, “antenna”, “antenna element”, “panel”, etc. are used interchangeably.

[0316] In this disclosure, the terms "Base Station (BS)", "wireless base station", "fixed station", "NodeB", "eNB (eNodeB)", "gNB (gNodeB)", "access point", "transmission point (TP)", "reception point (RP)", "transmission / reception point (TRP)", "panel", "cell", "sector", "cell group", "carrier", and "component carrier" are used interchangeably. Base stations are sometimes also referred to as macrocells, small cells, femtocells, picocells, etc.

[0317] A base station can accommodate one or more (e.g., three) cells. When a base station accommodates multiple cells, the overall coverage area of ​​the base station can be divided into multiple smaller areas, and each smaller area can also provide communication services through a base station subsystem (e.g., a small indoor base station (Remote Radio Head (RRH))). Terms such as "cell" or "sector" refer to a portion or all of the coverage area of ​​at least one of the base station and base station subsystem providing communication services within that coverage area.

[0318] In this disclosure, the terms “Mobile Station (MS)”, “user terminal”, “user equipment (UE)”, and “terminal” are used interchangeably.

[0319] Mobile stations are sometimes also referred to as subscriber stations, mobile units, subscriber units, wireless units, remote units, mobile devices, wireless devices, wireless communication devices, remote devices, mobile subscriber stations, access terminals, mobile terminals, wireless terminals, remote terminals, handheld devices, user agents, mobile clients, clients, or some other appropriate terms.

[0320] At least one of the base station and the mobile station can also be referred to as a transmitting device, a receiving device, a wireless communication device, etc. Additionally, at least one of the base station and the mobile station can also be a device mounted on a mobile body, or the mobile body itself. This mobile body can be a vehicle (e.g., a car, an airplane, etc.), an unmanned mobile body (e.g., a drone, an autonomous vehicle, etc.), or a robot (humanized or unmanned). Furthermore, at least one of the base station and the mobile station may also include devices that do not necessarily move during communication operations. For example, at least one of the base station and the mobile station can also be an Internet of Things (IoT) device such as a sensor.

[0321] Furthermore, the base station in this disclosure can be replaced by a user terminal. For example, various methods / implementations of this disclosure can also be applied to structures that replace communication between the base station and the user terminal with communication between multiple user terminals (e.g., also referred to as device-to-device (D2D) or vehicle-to-everything (V2X)). In this case, the user terminal 20 can be configured to have the functions of the base station 10 described above. In addition, terms such as "uplink" and "downlink" can be replaced with terms corresponding to inter-terminal communication (e.g., "side"). For example, uplink channel, downlink channel, etc., can also be replaced with side channel.

[0322] Similarly, the user terminal in this disclosure can also be replaced by a base station. In this case, the base station 10 can be configured to have the functions of the user terminal 20 described above.

[0323] In this disclosure, operations are assumed to be performed by the base station, but sometimes may also be performed by its upper node, depending on the circumstances. In a network containing one or more network nodes that have a base station, various operations performed for communication with a terminal can obviously be performed by the base station, one or more network nodes other than the base station (e.g., consider a Mobility Management Entity (MME) or a Serving Gateway (S-GW), but are not limited thereto), or a combination thereof.

[0324] The various methods / implementations described in this disclosure can be used individually, in combination, or switched during execution. Furthermore, the processing procedures, timing sequences, flowcharts, etc., of the various methods / implementations described in this disclosure can be rearranged as long as they do not contradict each other. For example, regarding the methods described in this disclosure, the elements of various steps are presented in an illustrated order, but the order in which they are presented is not limited.

[0325] The various methods / implementations described in this disclosure can be applied to Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), Future Radio Access (FRA), Radio Access Technology (New-RAT), New Radio (NR), New radio access (NX), Future generation radio access (FX), Global System for Mobile Communications (GSM), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Ultra-Wideband (UWB), Bluetooth (a registered trademark), systems utilizing other appropriate wireless communication methods, and next-generation systems based on them, etc. Furthermore, multiple systems can be used in combination (e.g., a combination of LTE or LTE-A with 5G, etc.).

[0326] As used in this disclosure, the term "based on" does not mean "based on only" unless otherwise expressly stated. In other words, the term "based on" means both "based on only" and "based on at least".

[0327] Any reference to elements using terms such as "first" or "second" as used in this disclosure is not intended to impose a comprehensive limitation on the number or order of these elements. These designations may be used in this disclosure as a convenient method of distinguishing between two or more elements. Therefore, reference to the first and second elements does not imply that only two elements can be used, or that the first element must precede the second element in some form.

[0328] The term "determining" as used in this specification sometimes encompasses a variety of operations. For example, "determining" can be considered as making a "determination" regarding judging, calculating, computing, processing, deriving, investigating, looking up, searching, inquiring (e.g., searching in a table, database, or other data structure), and ascertaining.

[0329] Furthermore, "judgment (decision)" can be viewed as making "judgments (decisions)" on receiving (e.g., receiving information), transmitting (e.g., sending information), inputting, outputting, accessing (e.g., accessing data in memory), etc.

[0330] Furthermore, "judgment (decision)" can be viewed as making "judgments (decisions)" regarding resolving, selecting, choosing, establishing, and comparing. In other words, "judgment (decision)" can be seen as making "judgments (decisions)" regarding certain operations.

[0331] In addition, “judgment (decision)” can also be replaced with “assuming”, “expecting”, or “considering”.

[0332] As used in this disclosure, the terms "connected," "coupled," or any variations thereof mean all direct or indirect connections or combinations between two or more elements, and can include cases where there is one or more intermediate elements between two mutually "connected" or "coupled" elements. The connections or combinations between elements can be physical, logical, or a combination thereof. For example, "connected" can also be replaced with "access."

[0333] In this disclosure, when two or more components are connected, it can be considered that they are "connected" or "combined" with each other using one or more wires, cables, printed electrical connections, etc., and as several non-limiting and non-exhaustive examples, electromagnetic energy with wavelengths in the wireless frequency domain, microwave domain, and optical (both visible and invisible light) domain.

[0334] In this disclosure, the term "A is different from B" can also mean "A and B are not the same." Additionally, the term can also mean "A and B are each different from C." Terms such as "separate" and "combined" can also be interpreted as "different."

[0335] In this disclosure, the terms "include," "including," and variations thereof, like the term "comprising," imply inclusiveness. Furthermore, the term "or," as used in this disclosure, means not a logical XOR.

[0336] In this disclosure, when articles such as a, an, and the from English are added through translation, this disclosure includes cases where the noun following these articles is in the plural form.

[0337] The inventions disclosed herein have been described in detail above. However, it will be apparent to those skilled in the art that the inventions are not limited to the embodiments described herein. The inventions disclosed herein can be implemented as modifications and variations without departing from the spirit and scope of the invention as defined by the claims. Therefore, the description in this disclosure is for illustrative purposes only and does not imply any limitation on the inventions disclosed herein.

Claims

1. A terminal, comprising: The control unit controls the quasi-co-addressing used in the reception of the PDSCH based on downlink control information and whether the offset between the control unit and the corresponding downlink shared channel (PDSCH) is shorter than a specific period; and The receiving unit receives at least one of a downlink control message used in the scheduling of multiple PDSCHs, and multiple downlink control messages used in the scheduling of multiple PDSCHs respectively. The multiple downlink control messages are transmitted through the downlink control channels of the control resource sets corresponding to different control resource pool indices. When multiple control resource sets for downlink control information are set, the control resource set for one downlink control information is not set.

2. The terminal as described in claim 1, wherein, The control resource sets corresponding to the different control resource pool indexes are set within the BWP of the serving cell.

3. A wireless communication method for a terminal, comprising: The steps for controlling the quasi-co-addressing used in the reception of the PDSCH based on downlink control information and whether the offset between the PDSCH and the corresponding downlink shared channel (PDSCH) is shorter than a specific period; and The steps of receiving one downlink control information used in the scheduling of multiple PDSCHs, and at least one of multiple downlink control information used in the scheduling of multiple PDSCHs respectively. The multiple downlink control messages are transmitted through the downlink control channels of the control resource sets corresponding to different control resource pool indices. When multiple control resource sets for downlink control information are set, the control resource set for one downlink control information is not set.

4. A system comprising a terminal and a base station, The terminal has: The control unit controls the quasi-co-addressing used in the reception of the PDSCH based on downlink control information and whether the offset between the control information and the corresponding downlink shared channel (PDSCH) is shorter than a specific period. as well as The receiving unit receives at least one of a downlink control message used in the scheduling of multiple PDSCHs, and multiple downlink control messages used in the scheduling of multiple PDSCHs respectively. The base station has: The transmitting unit transmits the one downlink control information and at least one of the plurality of downlink control information; as well as The control unit controls the quasi-co-addressing used in the PDSCH. The multiple downlink control messages are transmitted through the downlink control channels of the control resource sets corresponding to different control resource pool indices. When multiple control resource sets for downlink control information are set, the control resource set for one downlink control information is not set.

Images