Terminal, wireless communication method, base station and system

Abstract

A terminal according to one aspect of the present disclosure comprises: a reception unit that receives setting information relating to a single frequency network (SFN) physical downlink shared channel (PDSCH); and a control unit that, on the basis of a condition relating to an offset from the reception of downlink control information (DCI) for scheduling the SFN PDSCH to the reception of the SFN PDSCH, whether or not a transmission configuration indication (TCI) field is included in the DCI, and the setting information, determines a TCI state to be applied to the SFN PDSCH. According to one aspect of the present disclosure, operation relating to a TCI state / default TCI state can be appropriately controlled.

Description

[Technical Field]

[0001] The present disclosure relates to a terminal and a wireless communication method in a next-generation mobile communication system. 、 base station and systems Regarding. [Background technology]

[0002] In Universal Mobile Telecommunications System (UMTS) networks, Long Term Evolution (LTE) was specified with the aim of achieving higher data rates and lower latency (Non-Patent Document 1). Also, LTE-Advanced (3GPP Rel. 10-14) was specified with the aim of achieving higher capacity and more advanced features than LTE (Third Generation Partnership Project (3GPP) Release (Rel.) 8, 9).

[0003] Successor systems to LTE (e.g., 5th generation mobile communication system (5G), 5G+ (plus), 6th generation mobile communication system (6G), New Radio (NR), 3GPP Rel. 15 or later) are also being considered. [Prior art documents] [Non-patent literature]

[0004] [Non-Patent Document 1] 3GPP TS 36.300 V8.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 [Problem to be solved by the invention]

[0005] In future wireless communication systems (e.g., NR), it is being considered to set the reception method of the physical downlink control channel (PDCCH) and the physical downlink shared channel (PDSCH) for the control resource set (CORESET) for higher reliability / high-speed movement.

[0006] However, there are cases where the application of the TCI state / default TCI state is not fully considered in the terminal (user equipment (UE)). In such cases, there is a risk of degradation of communication quality and throughput.

[0007] Therefore, the present disclosure provides a terminal and a wireless communication method that appropriately control operations related to the TCI state / default TCI state. 、 base station and systems One of the aims is to provide [Means for solving the problem]

[0008] A terminal according to one embodiment of the present disclosure performs scheduling using downlink control information (DCI) without a transmission configuration indication (TCI) field. of Support Toss R indicates that A transmitter reporting UE capabilities and configuration information for the single frequency network (SFN) Physical Downlink Shared Channel (PDSCH) and at least one of configuration information regarding the SFN physical downlink control channel (PDCCH) a receiving unit for receiving the Received The aforementioned Regarding SFN PDSCH SFN PDSCH is set according to the setting information, No. 1 Schedule PDSCH No. 1 From receiving DCI No. 1 The offset to the reception of the PDSCH is greater than or equal to a certain threshold, If the transmitter reports the UE capability indicating that it supports scheduling by DCI without the TCI field, The aforementioned No. 1 The DCI includes the TCI field. figure , Applying the SFN PDSCH based on predetermined conditions The aforementioned No. 1 TCI state of the control resource set associated with the DCI Judge a control unit for cutting off the and when the SFN PDSCH is configured according to received configuration information related to the SFN PDSCH, an offset from reception of a second DCI scheduling a second PDSCH to reception of the second PDSCH is equal to or greater than the specific threshold, and an SFN PDCCH is not configured without receiving configuration information related to the SFN PDCCH, the control unit reports the UE capability indicating that it supports scheduling by a DCI without the TCI field, and when it does not support UE capability related to a single transmission / reception point (TRP) and dynamic switching of the SFN PDSCH, it expects the TCI field to be included in the second DCI. do. [Effects of the Invention]

[0009] According to one aspect of the present disclosure, operations related to the TCI state / default TCI state can be appropriately controlled. [Brief explanation of the drawings]

[0010] [Figure 1] 1A and 1B are diagrams illustrating an example of communication between a mobile unit and a transmission point (eg, RRH). [Figure 2] 2A to 2C are diagrams illustrating an example of schemes 0 to 2 for SFN. [Figure 3] 3A and 3B show an example of Scheme 1. [Figure 4] 4A to 4C are diagrams illustrating an example of a NW pre-compensation scheme. [Figure 5] FIG. 5 is a diagram relating to the configuration of SFN PDCCH / PDSCH. [Figure 6] FIG. 6 is a diagram illustrating an example of application of the TCI state according to embodiment 1-1. [Figure 7] FIG. 7 is a diagram illustrating an example of application of the TCI state according to embodiment 1-2. [Figure 8] FIG. 8 is a diagram illustrating an example of application of the TCI state according to embodiment 2-0 / 2-1. [Figure 9] FIG. 9 is a diagram illustrating an example of application of the TCI state according to embodiment 2-2. [Figure 10] FIG. 10 is a diagram illustrating an example of a schematic configuration of a wireless communication system according to an embodiment. [Figure 11] FIG. 11 is a diagram illustrating an example of the configuration of a base station according to an embodiment. [Figure 12] FIG. 12 is a diagram illustrating an example of the configuration of a user terminal according to an embodiment. [Figure 13] FIG. 13 is a diagram illustrating an example of the hardware configuration of a base station and a user terminal according to an embodiment. [Figure 14] FIG. 14 is a diagram illustrating an example of a vehicle according to an embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0011] (TCI, spatial relations, QCL) In NR, it is being considered to control the reception processing (e.g., at least one of reception, demapping, demodulation, and decoding) and transmission processing (e.g., at least one of transmission, mapping, precoding, modulation, and encoding) in the UE of at least one of a signal and a channel (referred to as signal / channel) based on the transmission configuration indication state (TCI state).

[0012] The TCI state may represent that which is applied to a downlink signal / channel, and the equivalent of the TCI state which is applied to an uplink signal / channel may be expressed as a spatial relation.

[0013] The TCI state is information about the quasi-co-location (QCL) of signals / channels, and may also be called spatial reception parameters, spatial relation information, etc. The TCI state may be configured in the UE for each channel or signal.

[0014] A QCL is an index that indicates the statistical properties of a signal / channel. For example, if a signal / channel has a QCL relationship with another signal / channel, it may mean that it can be assumed that at least one of the Doppler shift, Doppler spread, average delay, delay spread, and spatial parameter (e.g., spatial Rx parameter) is the same between these different signals / channels (i.e., they are QCLs with respect to at least one of these).

[0015] The spatial reception parameters may correspond to a reception beam (e.g., a reception analog beam) of the UE, and the beam may be determined based on a spatial QCL. A QCL (or at least one element of a QCL) in the present disclosure may be replaced with an sQCL (spatial QCL).

[0016] A plurality of types (QCL types) of QCLs may be defined. For example, four QCL types A and B may be provided, each having different parameters (or parameter sets) that can be assumed to be the same. The parameters (which may be referred to as QCL parameters) are listed below: QCL Type A (QCL-A): Doppler shift, Doppler spread, mean delay and delay spread, QCL Type B (QCL-B): Doppler shift and Doppler spread, QCL Type C (QCL-C): Doppler shift and mean delay, · QCL Type D (QCL-D): Spatial reception parameters.

[0017] The assumption by a UE that a Control Resource Set (CORESET), channel, or reference signal has a specific QCL (e.g., QCL type D) relationship with another CORESET, channel, or reference signal may be referred to as a QCL assumption.

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

[0019] The TCI state may be, for example, information about the QCL between the target channel (in other words, the Reference Signal (RS) for the channel) and another signal (e.g., another RS). The TCI state may be set (indicated) by higher layer signaling, physical layer signaling, or a combination thereof.

[0020] The physical layer signaling may be, for example, Downlink Control Information (DCI).

[0021] The channel for which the TCI state or spatial relationship is set (specified) may be, for example, at least one of a downlink shared channel (Physical Downlink Shared Channel (PDSCH)), a downlink control channel (Physical Downlink Control Channel (PDCCH)), an uplink shared channel (Physical Uplink Shared Channel (PUSCH)), and an uplink control channel (Physical Uplink Control Channel (PUCCH)).

[0022] Furthermore, the RS that has a QCL relationship with the channel may be, for example, at least one of a Synchronization Signal Block (SSB), a Channel State Information Reference Signal (CSI-RS), a Sounding Reference Signal (SRS), a CSI-RS for tracking (also called a Tracking Reference Signal (TRS)), and a QCL detection reference signal (also called a QRS).

[0023] An SSB is a signal block that includes at least one of a Primary Synchronization Signal (PSS), a Secondary Synchronization Signal (SSS), and a Physical Broadcast Channel (PBCH). An SSB may also be referred to as an SS / PBCH block.

[0024] An RS of QCL type X in a TCI state may refer to an RS that has a relationship of QCL type X with (the DMRS of) a certain channel / signal, and this RS may be called a QCL source of QCL type X in the TCI state.

[0025] (Default TCI State / Default Spatial Relationship / Default PL-RS) In Rel. 16, a PDSCH may be scheduled in a DCI with a TCI field. The TCI state for the PDSCH is indicated by the TCI field. The TCI field in DCI format 1-1 is 3 bits long, and the TCI field in DCI format 1-2 is a maximum of 3 bits long.

[0026] In RRC connected mode, if the TCI information element in the first DCI (higher layer parameter tci-PresentInDCI) is set to "enabled" for a CORESET that schedules a PDSCH, the UE assumes that the TCI field is present in DCI format 1_1 of the PDCCH transmitted in that CORESET.

[0027] Furthermore, if the TCI information element in the second DCI (higher layer parameter tci-PresentInDCI-1-2) for the CORESET that schedules the PDSCH is configured in the UE, the UE assumes that a TCI field with the DCI field size indicated in the TCI information element in the second DCI is present in DCI format 1_2 of the PDSCH transmitted in that CORESET.

[0028] Also, in Rel. 16, a PDSCH may be scheduled with a DCI that does not have a TCI field. The DCI format of the DCI may be DCI format 1_0 or DCI format 1_1 / 1_2 in the case where the TCI information element in the DCI (the higher layer parameter tci-PresentInDCI or tci-PresentInDCI-1-2) is not configured (enabled). When a PDSCH is scheduled with a DCI that does not have a TCI field, if the time offset between the reception of the DL DCI (the DCI that schedules the PDSCH (the scheduling DCI)) and the corresponding PDSCH (the PDSCH scheduled by the DCI) is equal to or greater than a threshold (timeDurationForQCL), the UE assumes that the TCI state or QCL assumption for the PDSCH is the same as the TCI state or QCL assumption (default TCI state) of the CORESET (e.g., the scheduling DCI).

[0029] In RRC connected mode, when the TCI information elements in DCI (higher layer parameters tci-PresentInDCI and tci-PresentInDCI-1-2) are set to "enabled" and when the TCI information elements in DCI are not set, if the time offset between the reception of a DL DCI (a DCI that schedules a PDSCH) and the corresponding PDSCH (a PDSCH scheduled by that DCI) is less than a threshold (timeDurationForQCL) (applicability condition, first condition), in the case of non-cross-carrier scheduling, the TCI state of the PDSCH (default TCI state) may be the TCI state of the lowest CORESET ID in the latest slot in the active DL BWP of that CC (of the specific UL signal). Otherwise, the TCI state of the PDSCH (default TCI state) may be the TCI state of the lowest TCI state ID of the PDSCH in the active DL BWP of the scheduled CC.

[0030] In Rel.15, separate MAC CEs are required for the activation / deactivation of PUCCH spatial relations and for the activation / deactivation of SRS spatial relations. The PUSCH spatial relations follow the SRS spatial relations.

[0031] In Rel. 16, at least one of the MAC CE for PUCCH spatial-related activation / deactivation and the MAC CE for SRS spatial-related activation / deactivation may not be used.

[0032] If neither the spatial relationship nor the PL-RS for the PUCCH is configured in FR2 (applicable condition, second condition), the default assumptions of the spatial relationship and the PL-RS for the PUCCH (default spatial relationship and default PL-RS) are applied. If neither the spatial relationship nor the PL-RS for the SRS (SRS resource for the SRS or SRS resource corresponding to the SRI in DCI format 0_1 ​​that schedules the PUSCH) is configured in FR2 (applicable condition, second condition), the default assumptions of the spatial relationship and the PL-RS for the PUSCH and SRS scheduled by DCI format 0_1 ​​(default spatial relationship and default PL-RS) are applied.

[0033] If a CORESET is configured in an active DL BWP on the CC (conditions apply), the default spatial relationship and default PL-RS may be the TCI state or QCL assumption of the CORESET with the lowest CORESET ID in the active DL BWP. If a CORESET is not configured in an active DL BWP on the CC, the default spatial relationship and default PL-RS may be the active TCI state with the lowest PDSCH ID in the active DL BWP.

[0034] In Rel.15, the spatial relationship of PUSCH scheduled by DCI format 0_0 follows the spatial relationship of the PUCCH resource with the lowest PUCCH resource ID among the active spatial relationships of PUCCH on the same CC. The network needs to update the PUCCH spatial relationships on all SCells even if no PUCCH is transmitted on the SCell.

[0035] In Rel.16, PUCCH configuration is not required for a PUSCH scheduled by DCI format 0_0. If there is no active PUCCH spatial relationship or no PUCCH resource on the active UL BWP in the CC for a PUSCH scheduled by DCI format 0_0 (applicable condition, second condition), the default spatial relationship and default PL-RS are applied to the PUSCH.

[0036] The application conditions for the default spatial relationship / default PL-RS for SRS may include setting a default beam path loss enable information element for SRS (upper layer parameter enableDefaultBeamPlForSRS) to valid. The application conditions for the default spatial relationship / default PL-RS for PUCCH may include setting a default beam path loss enable information element for PUCCH (upper layer parameter enableDefaultBeamPlForPUCCH) to valid. The application conditions for the default spatial relationship / default PL-RS for PUSCH scheduled by DCI format 0_0 may include setting a default beam path loss enable information element for PUSCH scheduled by DCI format 0_0 (upper layer parameter enableDefaultBeamPlForPUSCH0_0) to valid.

[0037] In Rel. 16, if an RRC parameter (a parameter for enabling the default beam PL for PUCCH (enableDefaultBeamPL-ForPUCCH), a parameter for enabling the default beam PL for PUSCH (enableDefaultBeamPL-ForPUSCH0_0), or a parameter for enabling the default beam PL for SRS (enableDefaultBeamPL-ForSRS)) is configured for a UE and a spatial relationship or PL-RS is not configured, the UE applies the default spatial relationship / PL-RS.

[0038] This threshold may also be called time duration for QCL, "timeDurationForQCL", "Threshold", "Threshold for offset between a DCI indicating a TCI state and a PDSCH scheduled by the DCI", "Threshold-Sched-Offset", "beamSwitchTiming", schedule offset threshold, scheduling offset threshold, etc. This threshold may be reported by the UE as UE capability (per subcarrier spacing).

[0039] If the offset between the reception of a DL DCI and its corresponding PDSCH is less than the threshold timeDurationForQCL, and at least one TCI state configured for the serving cell of the scheduled PDSCH includes "QCL Type D," and the UE is configured with the two default TCI enable information element (enableTwoDefaultTCIStates-r16), and at least one TCI codepoint (the codepoint of the TCI field in the DL DCI) indicates two TCI states, the UE assumes that the PDSCH or DM RS port of the PDSCH transmission occasion of the serving cell is quasi-colocated with the RS for the QCL parameters associated with the two TCI states corresponding to the lowest codepoints among the TCI codepoints containing two different TCI states (two default QCL assumption decision rule). The two default TCI enable information element indicates that Rel. 16 operation of the two default TCI states for the PDSCH is enabled when at least one TCI codepoint maps to two TCI states.

[0040] As the default TCI state of PDSCH in Rel.15 / 16, the default TCI state for a single TRP, the default TCI state for multiple TRPs based on multiple DCIs, and the default TCI state for multiple TRPs based on a single DCI are specified.

[0041] As default TCI states for aperiodic CSI-RS (A(aperiodic)-CSI-RS) in Rel.15 / 16, the default TCI state for a single TRP, the default TCI state for multi-TRP based on multi-DCI, and the default TCI state for multi-TRP based on a single DCI are specified.

[0042] In Rel.15 / 16, the default spatial relationship and default PL-RS for each of PUSCH / PUCCH / SRS are specified.

[0043] (Multi-TRP) In NR, one or more Transmission / Reception Points (TRPs) (multi-TRPs (MTRPs)) are considered to perform DL transmission to a UE using one or more panels (multi-panels). Also, it is considered that a UE performs UL transmission to one or more TRPs using one or more panels.

[0044] Note that multiple TRPs may correspond to the same cell identifier (ID), or different cell IDs. The cell ID may be a physical cell ID or a virtual cell ID.

[0045] Multi-TRPs (e.g., TRPs #1 and #2) may be connected by ideal / non-ideal backhauls to exchange information, data, etc. Each TRP of the multi-TRP may transmit a different code word (CW) and a different layer. Non-Coherent Joint Transmission (NCJT) may be used as a form of multi-TRP transmission.

[0046] In the NCJT, for example, TRP#1 performs modulation mapping and layer mapping on a first codeword to transmit a first PDSCH using a first number of layers (e.g., two layers) with a first precoding, and TRP#2 performs modulation mapping and layer mapping on a second codeword to transmit a second number of layers (e.g., two layers) with a second precoding.

[0047] Note that multiple PDSCHs (multi-PDSCHs) that are non-coherent may be defined as partially or completely overlapping in at least one of the time and frequency domains, i.e., a first PDSCH from a first TRP and a second PDSCH from a second TRP may overlap in at least one of the time and frequency resources.

[0048] The first PDSCH and the second PDSCH may be assumed to be not quasi-co-located (Quasi-Co-Location (QCL)). Reception of multiple PDSCHs may be interpreted as simultaneous reception of PDSCHs that are not of a certain QCL type (e.g., QCL type D).

[0049] Multiple PDSCHs from multiple TRPs (which may also be referred to as multiple PDSCHs) may be scheduled using one DCI (single DCI, single PDCCH) (single-master mode, single-DCI based multi-TRP). Multiple PDSCHs from multiple TRPs may also be scheduled using multiple DCIs (multiple DCI, multiple PDCCHs) (multi-master mode, multi-DCI based multi-TRP).

[0050] In Ultra-Reliable and Low Latency Communications (URLLC) for multiple TRPs, it is considered that PDSCH (transport block (TB) or codeword (CW)) repetition across multiple TRPs is supported. Repetition schemes (URLLC schemes, reliability enhancement schemes, e.g., schemes 1a, 2a, 2b, 3, and 4) across multiple TRPs in the frequency domain, layer (spatial) domain, or time domain are considered to be supported. In scheme 1a, multiple PDSCHs from multiple TRPs are space division multiplexed (SDM). In schemes 2a and 2b, PDSCHs from multiple TRPs are frequency division multiplexed (FDM). In scheme 2a, the redundancy version (RV) is the same for multiple TRPs. In scheme 2b, the RVs for multiple TRPs may be the same or different. In schemes 3 and 4, multiple PDSCHs from multiple TRPs are time division multiplexed (TDM). In scheme 3, multiple PDSCHs from multiple TRPs are transmitted in one slot. In scheme 4, multiple PDSCHs from multiple TRPs are transmitted in different slots.

[0051] Such a multi-TRP scenario allows for more flexible transmission control using good quality channels.

[0052] To support intra-cell (having the same cell ID) and inter-cell (having different cell IDs) multi-TRP transmission based on multiple PDCCHs, in the RRC configuration information for linking multiple pairs of PDCCHs and PDSCHs with multiple TRPs, one control resource set (CORESET) in the PDCCH configuration information (PDCCH-Config) may correspond to one TRP.

[0053] If at least one of the following conditions 1 and 2 is satisfied, the UE may determine that the transmission is a multi-TRP transmission based on the multi-DCI transmission. In this case, the TRP may be replaced with a CORESET pool index. [Condition 1] A CORESET pool index of 1 is set. [Condition 2] Two different values ​​of the CORESET pool index (for example, 0 and 1) are set.

[0054] If the following condition is met, the UE may determine that the state is multi-TRP based on a single DCI, in which case the two TRPs may be interpreted as two TCI states indicated by the MAC CE / DCI. [conditions] "Enhanced TCI States Activation / Deactivation for UE-specific PDSCH MAC CE" is used to indicate one or two TCI states for one codepoint of the TCI field in the DCI.

[0055] The DCI for common beam instruction may be a UE-specific DCI format (e.g., DL DCI format (e.g., 1_1, 1_2), UL DCI format (e.g., 0_1, 0_2)), or may be a UE-group common DCI format.

[0056] (Multi-TRP PDCCH) For the reliability of multi-TRP PDCCH based on non-single frequency network (SFN), the following studies 1 to 3 are considered. [Consideration 1] Coding / rate matching is based on one repetition, and the same coded bits are repeated in other repetitions. [Consideration 2] Each repetition has the same number of control channel elements (CCEs), the same coded bits, and corresponds to the same DCI payload. Consideration 3: Two or more PDCCH candidates are explicitly linked to each other. The UE knows the link before decoding.

[0057] The following options for PDCCH repetition are considered: 1-2, 1-3, 2, 3.

[0058] [Options 1-2] Two sets of PDCCH candidates (within a given search space (SS) set) are associated with two TCI states of CORESET, respectively, where the same CORESET, the same SS set, and PDCCH repetitions in different monitoring occasions are used.

[0059] [Options 1-3] Two sets of PDCCH candidates are associated with two SS sets, respectively. Both SS sets are associated with a CORESET, and each SS set is associated with only one TCI state of that CORESET. Here, the same CORESET and two SS sets are used.

[0060] [Option 2] One SS set is associated with two different CORESETs.

[0061] [Option 3] Two SS sets are associated with two CORESETs respectively.

[0062] In this way, two PDCCH candidates in two SS sets for PDCCH repetition are supported, and it is considered that the two SS sets are explicitly linked.

[0063] (SFN PDCCH) For PDCCH / CORESET specified in Rel. 15, one TCI state without CORESETPoolIndex (which may also be called TRP information (TRP Info)) is set to one CORESET.

[0064] Regarding the enhancement of PDCCH / CORESET specified in Rel. 16, in multi-TRP based on multi-DCI, a CORESET pool index is set for each CORESET.

[0065] In Rel. 17 and later, the following enhancements 1 and 2 for PDCCH / CORESET are being considered.

[0066] In the case where multiple antennas (small antennas, transmitting / receiving points) with the same cell ID form a single frequency network (SFN), up to two TCI states can be set / activated for one CORESET by higher layer signaling (RRC signaling / MAC CE) (Enhancement 1). SFN contributes to at least one of improving the operation and reliability of HST (high speed train).

[0067] Furthermore, in repeated transmission of PDCCH (which may simply be called "repetition"), two PDCCH candidates in two search space sets are linked, and each search space set is associated with a corresponding CORESET (Enhancement 2). The two search space sets may be associated with the same or different CORESETs. For one CORESET, one (maximum one) TCI state can be configured / activated by higher layer signaling (RRC signaling / MAC CE).

[0068] If two search space sets are associated with different CORESETs with different TCI states, this may mean a multi-TRP repeat transmission. If two search space sets are associated with the same CORESET (CORESET with the same TCI state), this may mean a single-TRP repeat transmission.

[0069] (HST) In LTE, placement in HST (high-speed train) tunnels is difficult. Large antennas transmit both inside and outside the tunnel. For example, the transmit power of a large antenna is approximately 1 to 5 W. For handover purposes, it is important for the UE to transmit outside the tunnel before entering it. For example, the transmit power of a small antenna is approximately 250 mW. Multiple small antennas (transmitting and receiving points) with the same cell ID and a distance of 300 m form a single frequency network (SFN). All small antennas within the SFN transmit the same signal at the same time on the same PRB. It is assumed that the terminal transmits and receives signals to a single base station. In reality, multiple transmitting and receiving points transmit the same DL signal. When moving at high speed, transmitting and receiving points several kilometers apart form a single cell. Handover occurs when crossing cells. This reduces the frequency of handovers.

[0070] In NR, it is assumed that a beam transmitted from a transmission point (e.g., RRH) will be used to communicate with a terminal (hereinafter also referred to as UE) included in a moving object (HST (high speed train)) such as a fast-moving train. Existing systems (e.g., Rel. 15) support transmitting a unidirectional beam from the RRH to communicate with a moving object (see Figure 1A).

[0071] FIG. 1A shows a case where RRHs are installed along the movement path (or movement direction, traveling direction, or travel path) of a moving object, and a beam is formed from each RRH in the traveling direction of the moving object. An RRH that forms a beam in one direction may be called a unidirectional RRH. In the example shown in FIG. 1A, the moving object receives a negative Doppler shift (-fD) from each RRH.

[0072] Here, we show a case where a beam is formed in the direction of travel of the moving body, but this is not limited to this, and a beam may be formed in the opposite direction to the direction of travel, or a beam may be formed in any direction regardless of the direction of travel of the moving body.

[0073] In Rel. 16 and later, it is expected that multiple beams (e.g., two or more) will be transmitted from the RRH. For example, it is expected that beams will be formed in both the direction of travel of the moving object and the opposite direction (see Figure 1B).

[0074] 1B shows a case where RRHs are installed along the movement path of a mobile object, and beams are formed from each RRH in both the direction of travel of the mobile object and the direction opposite to the direction of travel. An RRH that forms beams in multiple directions (for example, two directions) may be called a bidirectional RRH.

[0075] In HST, the UE communicates as if it were a single TRP. In base station implementations, it is possible to transmit from multiple TRPs (same cell ID).

[0076] In the example of Figure 1B, when two remote radio heads (RRH#1 and RRH#2) use SFN, the mobile station switches from a signal that has undergone a negative Doppler shift to a signal that has undergone a positive Doppler shift, which increases power, midway between the two remote radio heads. In this case, the maximum Doppler shift change range that requires correction is from -fD to +fD, which is twice as large as that in the case of a unidirectional remote radio head.

[0077] Here, as HST schemes, the following schemes 0 to 2 (HST scheme 0 to HST scheme 2) will be compared.

[0078] In scheme 0 of FIG. 2A, a tracking reference signal (TRS), a DMRS, and a PDSCH are commonly transmitted (using the same time and frequency resources) to two TRPs (RRHs) (normal SFN, transparent SFN, HST-SFN).

[0079] In scheme 0, the UE receives DL channels / signals equivalent to a single TRP, so there is one TCI state for the PDSCH.

[0080] Rel.16 specifies RRC parameters for distinguishing between transmissions using a single TRP and transmissions using SFN. When a UE reports corresponding UE capability information, the UE may distinguish between reception of a DL channel / signal using a single TRP and reception of a PDSCH assuming SFN based on the RRC parameters. On the other hand, the UE may perform transmission and reception using SFN assuming a single TRP.

[0081] In scheme 1 of Figure 2B, TRSs are transmitted TRP-specifically (using different time / frequency resources depending on the TRP). In this example, TRS1 is transmitted from TRP#1 and TRS2 is transmitted from TRP#2.

[0082] In Scheme 1, there are two TCI states for PDSCH since the UE receives DL channels / signals from each TRP using TRS from each TRP.

[0083] In this disclosure, SFN scheme 1 (SFN scheme 1) may also be referred to as SFN scheme A.

[0084] In scheme 2 of FIG. 2C, a TRS and a DMRS are transmitted individually for each TRP. In this example, TRS1 and DMRS1 are transmitted from TRP#1, and TRS2 and DMRS2 are transmitted from TRP#2. Compared to scheme 0, schemes 1 and 2 can suppress sudden changes in Doppler shift and appropriately estimate / guarantee the Doppler shift. Because the DMRS in scheme 2 is higher than that in scheme 1, the maximum throughput of scheme 2 is lower than that of scheme 1.

[0085] In scheme 0, the UE switches between single TRP and SFN based on higher layer signaling (RRC information elements / MAC CE).

[0086] The UE may switch between Scheme 1 / Scheme 2 / NW pre-compensation schemes based on higher layer signaling (RRC information element / MAC CE).

[0087] In Scheme 1, two TRS resources are set for the HST's forward direction and its reverse direction, respectively.

[0088] In the example of Figure 3A, the TRPs (TRP#0, #2, ...) transmitting DL signals in the direction opposite to the HST transmit the first TRS (TRS arriving before the HST) in the same time and frequency resource (SFN). The TRPs (TRP#1, #3, ...) transmitting DL signals in the direction of travel of the HST transmit the second TRS (TRS arriving after the HST) in the same time and frequency resource (SFN). The first TRS and second TRS may be transmitted / received using different frequency resources.

[0089] In the example of FIG. 3B, TRS1-1 to 1-4 are transmitted as the first TRS, and TRS2-1 to 2-4 are transmitted as the second TRS.

[0090] Considering beam operation, the first TRS is transmitted using 64 beams and 64 time resources, and the second TRS is transmitted using 64 beams and 64 time resources. The beam of the first TRS and the beam of the second TRS are considered to be equal (QCL Type D RSs are equal). By multiplexing the first TRS and the second TRS into the same time resource but different frequency resource, resource utilization efficiency can be improved.

[0091] In the example of Fig. 4A, RRHs #0-#7 are arranged along the movement path of the HST. RRHs #0-#3 and RRHs #4-#7 are connected to baseband units (BBUs) #0 and #1, respectively. Each RRH is a bidirectional RRH, and forms beams in both the direction of travel of the movement path and the opposite direction using each transmission / reception point (TRP).

[0092] In the received signal of the example of Figure 4B (single TRP (SFN) / scheme 1), when the UE receives a signal / channel (a beam in the direction of travel of the HST, a beam from behind the UE) transmitted from TRP#2n-1 (n is an integer greater than or equal to 0), a negative Doppler shift (-fD in this example) occurs. Also, when the UE receives a signal / channel (a beam in the direction opposite to the direction of travel of the HST, a beam from in front of the UE) transmitted from TRP#2n (n is an integer greater than or equal to 0), a positive Doppler shift (+fD in this example) occurs.

[0093] In Rel. 17 and later, it is being considered to perform Doppler compensation (also called Doppler compensation, pre-Doppler compensation, network (NW) pre-compensation scheme (NW pre-compensation scheme, HST NW pre-compensation scheme, TRP based pre-compensation scheme)) when transmitting downlink (DL) signals / channels from a TRP to a UE in an HST. By performing Doppler compensation in advance when transmitting DL signals / channels to a UE, the TRP can reduce the effect of Doppler shift when the UE receives the DL signals / channels.

[0094] In this disclosure, the NW pre-compensation scheme may be a combination of Scheme 1 and Doppler shift pre-compensation by the base station. In this disclosure, the NW pre-compensation, TRP-based pre-compensation scheme may be referred to as SFN Scheme B.

[0095] In the NW pre-compensation scheme, the TRPs that form beams in the direction of travel of the moving path and the TRPs that form beams in the opposite direction of travel of the moving path perform Doppler compensation before transmitting DL signals / channels to UEs within the HST. In this example, TRP#2n-1 performs positive Doppler compensation, and TRP#2n performs negative Doppler compensation to reduce the effect of Doppler shift when the UE receives the signal / channel (Figure 4C).

[0096] Note that in the situation of FIG. 4C, there may be two TCI states for the PDSCH since the UE receives DL channels / signals from each TRP using the TRS from each TRP.

[0097] Furthermore, in Rel. 17 and later, dynamic switching between single TRP and SFN using the TCI field (TCI state field) is being considered. For example, one or two TCI states are configured / indicated at each TCI code point (code point of the TCI field, DCI code point) using the RRC information element / MAC CE (e.g., Enhanced TCI States Activation / Deactivation for UE-specific PDSCH MAC CE) / DCI (TCI field). The UE may determine to receive a PDSCH with a single TRP when one TCI state is configured / indicated. Also, the UE may determine to receive a PDSCH with a multi-TRP and SFN when two TCI states are configured / indicated.

[0098] (analysis) Both the above-mentioned SFN scheme A and SFN scheme B are considered to be applied to the PDSCH and PDCCH.

[0099] SFN scheme A may be used primarily for HST / URLLC use cases, and SFN scheme B may be used primarily for HST use cases.

[0100] For PDSCH / PDCCH using SFN, the following assumptions 1 to 3 are possible: Assumption 1: SFN PDCCH schedules SFN PDSCH. Assumption 2: A single TRP PDCCH schedules an SFN PDSCH. Assumption 3: SFN PDCCH schedules a single TRP PDSCH.

[0101] Assumptions 1 and 2 above may be used primarily for the HST / URLLC use case. Assumption 3 above may be used primarily for SFN scheme A for the URLLC use case.

[0102] In Rel. 17 and later, the operation regarding the default QCL / TCI state for the SFN PDCCH / PDSCH configuration for the UE is being considered (see FIG. 5).

[0103] In the example shown in Fig. 5, "SFN PDCCH+SFN PDSCH" indicates a case where an SFN PDCCH and an SFN PDSCH are configured. In the example shown in Fig. 5, "S-TRP PDCCH+SFN PDSCH" indicates a case where an SFN PDCCH is not configured, but an SFN PDSCH is configured. In the example shown in Fig. 5, "SFN PDCCH+S-TRP PDSCH" indicates a case where an SFN PDCCH is configured, but an SFN PDSCH is not configured.

[0104] For example, if an SFN PDCCH and an SFN PDSCH are configured and the scheduling offset (the offset from the reception of DCI (e.g., DCI format 1_0 / 1_1 / 1_2) to the reception of PDSCH) is smaller than a threshold (e.g., "timeDurationForQCL"), and an RRC parameter (two default TCI enable information element (enableTwoDefaultTCI-States)) is configured, the UE will use the TCI state corresponding to the lowest TCI code point among the two active TCI states for PDSCH (TCI code points indicating two TCI states) (i.e., the TCI state is determined in the same way as scheme 1a for PDSCH specified in Rel. 16).

[0105] Furthermore, for example, when an SFN PDCCH is not configured (a single TRP PDCCH is configured), an SFN PDSCH is configured, and the scheduling offset is smaller than a threshold (e.g., "timeDurationForQCL"), and an RRC parameter (two default TCI enable information element (enableTwoDefaultTCI-States)) is configured, the UE is considered to use the TCI state corresponding to the lowest TCI code point of the two active TCI states for the PDSCH.

[0106] Also, for example, when SFN PDCCH and SFN PDSCH are not configured (single TRP PDCCH and PDSCH are configured), and the scheduling offset is smaller than a threshold (for example, "timeDurationForQCL"), and the CORESET with the lowest CORESET ID in the latest slot (monitoring slot) has two TCI states, it is considered that the UE uses the first TCI state of the two TCI states to receive the PDSCH. In this case, a configuration in which the TCI field is not included in the DCI may be supported.

[0107] Furthermore, for example, when an SFN PDCCH and an SFN PDSCH are configured, the scheduling offset is equal to or greater than a threshold (e.g., "timeDurationForQCL"), and the DCI that schedules the PDSCH (e.g., DCI format 1_0 / 1_1 / 1_2) does not include a TCI state field (TCI field), and the scheduling CORESET (CORESET that schedules the PDSCH) has two TCI states, it is being considered that the UE will use both of the two TCI states to receive the PDSCH. Furthermore, for example, when an SFN PDCCH and an SFN PDSCH are configured, and the scheduling offset is equal to or greater than a threshold (for example, "timeDurationForQCL"), and the DCI (for example, DCI format 1_0 / 1_1 / 1_2) that schedules the PDSCH does not include a TCI state field (TCI field), and the scheduling CORESET does not have two TCI states (has one TCI state), the UE may use the one TCI state to receive the PDSCH. In these cases, a configuration in which the DCI does not include a TCI field may be supported.

[0108] Furthermore, for example, when an SFN PDCCH and an SFN PDSCH are not configured (a single TRP PDCCH and a PDSCH are configured), and the scheduling offset is equal to or greater than a threshold (for example, "timeDurationForQCL"), and the DCI that schedules the PDSCH (for example, DCI format 1_0 / 1_1 / 1_2) does not include a TCI state field (TCI field), and the scheduling CORESET (CORESET that schedules the PDSCH) has two TCI states, it is considered that the UE uses the first TCI state of the two TCI states to receive the PDSCH. In this case, a configuration in which the DCI does not include a TCI field may be supported.

[0109] However, there has been insufficient consideration of a method for determining the TCI state when, for example, an SFN PDCCH is not configured (a single TRP PDCCH is configured), an SFN PDSCH is configured, the scheduling offset is equal to or greater than a threshold (e.g., "timeDurationForQCL"), and the DCI that schedules the PDSCH (e.g., DCI format 1_0 / 1_1 / 1_2) does not include a TCI state field (TCI field).

[0110] Furthermore, there has been insufficient consideration of a method for determining the TCI state when, for example, an SFN PDCCH is not configured (a single TRP PDCCH is configured), an SFN PDSCH is configured, the scheduling offset is equal to or greater than a threshold (e.g., "timeDurationForQCL"), and the DCI (e.g., DCI format 1_0 / 1_1 / 1_2) that schedules the PDSCH does not include a TCI state field (TCI field).

[0111] Furthermore, for example, when an SFN PDCCH and an SFN PDSCH are configured and the offset from the reception of the scheduling offset to the reception of the PDSCH is smaller than a threshold (e.g., "timeDurationForQCL"), and an RRC parameter (two default TCI enable information element (enableTwoDefaultTCI-States)) is not configured, there has been insufficient consideration regarding the method for determining the TCI state.

[0112] Furthermore, for example, there has been insufficient consideration of the method for determining the TCI state when an SFN PDCCH is not configured (a single TRP PDCCH is configured), an SFN PDSCH is configured, and the offset from the reception of the scheduling offset to the reception of the PDSCH is smaller than a threshold (e.g., "timeDurationForQCL"), and an RRC parameter (two default TCI enable information element (enableTwoDefaultTCI-States)) is not configured.

[0113] If these considerations are not sufficient, the TCI state cannot be judged / determined / applied appropriately, which may result in a decrease in communication quality and throughput.

[0114] Therefore, the present inventors have conceived a method for appropriately controlling operations relating to the TCI state / default TCI state.

[0115] Hereinafter, embodiments according to the present disclosure will be described in detail with reference to the drawings. Wireless communication methods according to the embodiments may be applied independently or in combination.

[0116] In the present disclosure, "A / B" and "at least one of A and B" may be interpreted interchangeably. Also, in the present disclosure, "A / B / C" may mean "at least one of A, B, and C."

[0117] In the present disclosure, terms such as activate, deactivate, indicate (or indicate), select, configure, update, and determine may be read interchangeably. In the present disclosure, terms such as support, control, controllable, operate, and operate may be read interchangeably.

[0118] In the present disclosure, Radio Resource Control (RRC), RRC signaling, RRC parameters, RRC messages, higher layer parameters, information elements (IEs), configurations, etc. may be interchangeable. In the present disclosure, Medium Access Control (MAC) control elements (CEs), update commands, activation / deactivation commands, etc. may be interchangeable.

[0119] In the present disclosure, higher layer signaling may be, for example, any one of Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling, broadcast information, and the like, or a combination thereof.

[0120] In the present disclosure, MAC signaling may use, for example, a MAC Control Element (MAC CE), a MAC Protocol Data Unit (PDU), etc. Broadcast information may be, for example, a Master Information Block (MIB), a System Information Block (SIB), Remaining Minimum System Information (RMSI), Other System Information (OSI), etc.

[0121] In the present disclosure, physical layer signaling may be, for example, Downlink Control Information (DCI), Uplink Control Information (UCI), and the like.

[0122] In this disclosure, the terms index, identifier (ID), indicator, resource ID, etc. may be interchangeable. In this disclosure, the terms sequence, list, set, group, cluster, subset, etc. may be interchangeable.

[0123] In this disclosure, the terms panel, UE panel, panel group, beam, beam group, precoder, Uplink (UL) transmitting entity, Transmission / Reception Point (TRP), base station, Spatial Relation Information (SRI), spatial relation, SRS Resource Indicator (SRI), Control Resource Set (CORESET), Physical Downlink Shared Channel (PDSCH), Codeword (CW), Transport Block (TB), Reference Signal (RS), antenna port (e.g., Demodulation Reference Signal (DMRS) port), antenna port group (e.g., DMRS port group), group (e.g., spatial relation group, Code Division Multiplexing (CDM) group, reference signal group, CORESET group, Physical Uplink Control The terms PUCCH group, PUCCH resource group, resource (e.g., reference signal resource, SRS resource), resource set (e.g., reference signal resource set), CORESET pool, downlink Transmission Configuration Indication state (TCI state) (DL TCI state), uplink TCI state (UL TCI state), unified TCI state, common TCI state, Quasi-Co-Location (QCL), QCL assumption, etc. may be read as interchangeable.

[0124] Furthermore, the spatial relationship information identifier (ID) (TCI state ID) and spatial relationship information (TCI state) may be interchangeable. "Spatial relationship information" may be interchangeable with "set of spatial relationship information," "one or more pieces of spatial relationship information," etc. The TCI state and TCI may be interchangeable with each other.

[0125] The panel may be associated with at least one of a group index of an SSB / CSI-RS group, a group index of a group-based beam report, and a group index of an SSB / CSI-RS group for group-based beam reporting.

[0126] Furthermore, a panel identifier (ID) and a panel may be interchangeable. That is, a TRP ID and a TRP, a CORESET group ID and a CORESET group, etc. may be interchangeable.

[0127] In the present disclosure, the terms TRP, transmission point, panel, DMRS port group, CORESET pool, and one of two TCI states associated with one code point in a TCI field may be read interchangeably.

[0128] In this disclosure, a single PDCCH (DCI) may be assumed to be supported when multiple TRPs utilize an ideal backhaul. Multiple PDCCHs (DCIs) may be assumed to be supported when multiple TRPs utilize a non-ideal backhaul.

[0129] The ideal backhaul may be called DMRS port group type 1, reference signal associated group type 1, antenna port group type 1, CORESET pool type 1, etc. The non-ideal backhaul may be called DMRS port group type 2, reference signal associated group type 2, antenna port group type 2, CORESET pool type 2, etc. The names are not limited to these.

[0130] In this disclosure, the terms "single TRP," "single TRP system," "single TRP transmission," and "single PDSCH" may be interchangeable. In this disclosure, the terms "multiple TRP," "multiple TRP system," "multiple TRP transmission," and "multiple PDSCH" may be interchangeable. In this disclosure, the terms "single DCI," "single PDCCH," "multiple TRP based on a single DCI," and "activating two TCI states on at least one TCI codepoint" may be interchangeable.

[0131] In the present disclosure, single TRP, channel using single TRP, channel using one TCI state / spatial relationship, no multi-TRP enabled by RRC / DCI, no multiple TCI states / spatial relationships enabled by RRC / DCI, no CORESETPoolIndex value of 1 set for any CORESET, and no codepoint in the TCI field mapped to two TCI states may be read interchangeably.

[0132] In the present disclosure, "multi-TRP," "channel using multi-TRP," "channel using multiple TCI states / spatial relationships," "multi-TRP being enabled by RRC / DCI," "multiple TCI states / spatial relationships being enabled by RRC / DCI," and "at least one of multi-TRP based on a single DCI" and "multi-TRP based on multiple DCI" may be interchangeable. In the present disclosure, "multi-TRP based on multiple DCI," and "setting a CORESET pool index (CORESETPoolIndex) value of 1 for the CORESET" may be interchangeable. In the present disclosure, "multi-TRP based on a single DCI," and "at least one code point in the TCI field is mapped to two TCI states" may be interchangeable.

[0133] In the present disclosure, TRP#1 (first TRP) may correspond to CORESET pool index = 0 or may correspond to the first of two TCI states corresponding to one code point in the TCI field. TRP#2 (second TRP) TRP#1 (first TRP) may correspond to CORESET pool index = 1 or may correspond to the second of two TCI states corresponding to one code point in the TCI field.

[0134] In the present disclosure, single DCI (sDCI), single PDCCH, multi-TRP system based on single DCI, sDCI-based MTRP, and activation of two TCI states on at least one TCI codepoint may be read interchangeably.

[0135] In the present disclosure, multi-DCI (mDCI), multi-PDCCH, multi-TRP system based on multi-DCI, mDCI-based MTRP, and setting two CORESET pool indices or CORESET pool index=1 (or a value greater than or equal to 1) may be read interchangeably.

[0136] The QCLs of the present disclosure may be interchangeably referred to as any QCL type (e.g., QCL types A / B / C / D).

[0137] In the present disclosure, expressions such as "TCI state A is the same QCL type A / D as TCI state B," "TCI state A is the same as TCI state B," "TCI state A is QCL type A / D with TCI state B," and "TCI state A is in a QCL type A / D relationship with TCI state B" may be interpreted interchangeably.

[0138] In the present disclosure, the terms CSI-RS, NZP-CSI-RS, periodic (P)-CSI-RS, P-TRS, semi-persistent (SP)-CSI-RS, aperiodic (A)-CSI-RS, TRS, tracking CSI-RS, CSI-RS having TRS information (higher layer parameter trs-Info), NZP CSI-RS resource in an NZP CSI-RS resource set having TRS information, NZP-CSI-RS resource in an NZP-CSI-RS resource set consisting of multiple NZP-CSI-RS resources of the same antenna port, and TRS resource may be interchangeable. In the present disclosure, the terms CSI-RS resource, CSI-RS resource set, CSI-RS resource group, and information element (IE) may be interchangeable.

[0139] In the present disclosure, the code point of the DCI field 'Transmission Configuration Indication', the TCI code point, the DCI code point, and the code point of the TCI field may be read interchangeably.

[0140] In the present disclosure, a DCI that does not include a TCI field may refer to DCI format 1_0. Also, in the present disclosure, a DCI that does not include a TCI field may refer to DCI format 1_1 / 1_2 when a specific upper layer parameter (e.g., a parameter indicating the presence of TCI (e.g., tci-PresentInDCI)) is set / enabled.

[0141] In the present disclosure, the terms "single TRP" and "SFN" may be interchangeable. In the present disclosure, the terms "HST", "HST scheme", "high speed mobility scheme", "scheme 1", "scheme 2", "NW pre-compensation scheme", "HST scheme 1", "HST scheme 2", and "HST NW pre-compensation scheme" may be interchangeable.

[0142] In the present disclosure, a PDSCH / PDCCH using a single TRP may be interchangeably referred to as a PDSCH / PDCCH based on a single TRP, a single TRP PDSCH / PDCCH, and a non-SFN PDSCH / PDCCH. Also, in the present disclosure, a PDSCH / PDCCH using SFN may be interchangeably referred to as a PDSCH / PDCCH using SFN in multi-hop transmission, a PDSCH / PDCCH based on SFN, and an SFN PDSCH / PDCCH.

[0143] In the present disclosure, receiving DL signals (PDSCH / PDCCH) using SFN may mean receiving the same data (PDSCH) / control information (PDCCH) from multiple transmission / reception points using the same time / frequency resources, and / or receiving DL signals using SFN may mean receiving the same data / control information using the same time / frequency resources and / or multiple TCI states / space-domain filters / beams / QCLs.

[0144] In the present disclosure, the terms HST-SFN scheme, SFN scheme after Rel. 17, new SFN scheme, new HST-SFN scheme, HST-SFN scenario after Rel. 17, HST-SFN scheme for HST-SFN scenario, SFN scheme for HST-SFN scenario, Scheme 1, Doppler pre-compensation scheme, Scheme 1 (HST Scheme 1), and at least one of Doppler pre-compensation scheme may be interchangeable. In the present disclosure, the terms Doppler pre-compensation scheme, base station pre-compensation scheme, TRP pre-compensation scheme, pre-Doppler compensation scheme, Doppler pre-compensation scheme, NW pre-compensation scheme, HST NW pre-compensation scheme, TRP pre-compensation scheme, and TRP-based pre-compensation scheme may be interchangeable. In the present disclosure, the terms pre-compensation scheme, reduction scheme, improvement scheme, and correction scheme may be interchangeable.

[0145] In the present disclosure, a PDCCH / search space (SS) / CORESET with linkage, a linked PDCCH / SS / CORESET, and a PDCCH / SS / CORESET pair may be interchangeable. In the present disclosure, a PDCCH / SS / CORESET without linkage, an unlinked PDCCH / SS / CORESET, and a single PDCCH / SS / CORESET may be interchangeable.

[0146] In the present disclosure, two linked CORESETs for PDCCH repetition, and two CORESETs respectively associated with two linked SS sets may be read interchangeably.

[0147] In the present disclosure, SFN-PDCCH repetition, PDCCH repetition, two linked PDCCHs, and one DCI being received across the two linked search spaces (SS) / CORESETs may be read interchangeably.

[0148] In the present disclosure, PDCCH repetition, SFN-PDCCH repetition, PDCCH repetition for higher reliability, and two linked PDCCHs may be read interchangeably.

[0149] In the present disclosure, the terms PDCCH reception method, PDCCH repetition, SFN-PDCCH repetition, HST-SFN, and HST-SFN scheme may be read interchangeably.

[0150] In the present disclosure, the PDSCH reception method, the single DCI-based multi-TRP, and the HST-SFN scheme may be read interchangeably.

[0151] In the present disclosure, the single DCI-based multi-TRP repetition may be an NCJT for an enhanced mobile broadband (eMBB) service (low priority, priority 0) or a repetition of a URLLC service (high priority, priority 1) for an ultra-reliable and low latency communications service.

[0152] In the present disclosure, received DL channel / signal, DL channel / signal, DL reception, received signal, received channel, etc. may be interchangeable. Also, in the present disclosure, UL channel / signal, transmission of UL channel / signal, and UL transmission may be interchangeable. Also, in the present disclosure, signal and channel may be interchangeable. In the present disclosure, buffering and buffer may be interchangeable.

[0153] In the present disclosure, the first TCI state may mean at least one of the first TCI state and the TCI state with a small (or large) TCI state ID. Also, the second TCI state may mean at least one of the second TCI state and the TCI state with a large (or small) TCI state ID. In the present disclosure, the first TCI state and the second TCI state may be interpreted as interchangeable.

[0154] In each embodiment of the present disclosure, two (default) TCI states are described as the main example, but the number is not limited to two, and each embodiment can be appropriately applied to a number of (default) TCI states greater than two.

[0155] (Wireless communication method) The UE may be configured with respect to (the use of) the SFN PDCCH / PDSCH using higher layer signaling (RRC signaling). The UE may receive parameters related to the configuration of the SFN PDCCH (configuration information, for example, sfnSchemePdcch). The UE may receive parameters related to the configuration of the SFN PDSCH (configuration information, for example, sfnSchemePdsch).

[0156] If the UE is not configured with a parameter related to the configuration of the SFN PDCCH (e.g., sfnSchemePdcch), the UE may determine that a PDCCH using a single TRP is used.If the UE is not configured with a parameter related to the configuration of the SFN PDCCH (e.g., sfnSchemePdcch), the UE may determine that a PDCCH using a single TRP is configured.

[0157] If the UE is not configured with parameters related to the configuration of the SFN PDSCH (e.g., sfnSchemePdsch), the UE may determine that a PDSCH using a single TRP is used. If the UE is not configured with parameters related to the configuration of the SFN PDSCH (e.g., sfnSchemePdsch), the UE may determine that a PDSCH using a single TRP is configured.

[0158] The UE may support scheduling of PDSCH with DCI that does not include a TCI field.

[0159] The UE may determine / judge the TCI state to apply to the SFN PDSCH based on at least one of parameters related to the configuration of the SFN PDSCH, parameters related to the configuration of the SFN PDCCH, conditions related to the scheduling offset, and whether or not the scheduling DCI includes a TCI field.

[0160] First Embodiment The SFN PDCCH may not be configured for the UE. The RRC parameters related to the SFN PDCCH (for example, sfnSchemePdcch) may not be configured / notified for the UE.

[0161] An SFN PDSCH may be configured for the UE. RRC parameters related to the SFN PDSCH (e.g., sfnSchemePdsch) may be configured / notified to the UE.

[0162] The UE may receive DCI that schedules reception of the PDSCH (scheduling DCI, for example, DCI format 1_1 / 1_2).

[0163] <<Embodiment 1-1>> If the (applicable) time offset (scheduling offset) between the reception of a scheduling DCI and the reception of a PDSCH corresponding to that DCI is equal to or greater than a certain threshold (e.g., "timeDurationForQCL"), the case where the DCI scheduling the PDSCH does not include a TCI field may be supported. In this case, the UE may support scheduling using a DCI without a TCI field.

[0164] If the (applicable) time offset (scheduling offset) between the reception of a scheduling DCI and the reception of the PDSCH corresponding to that DCI is greater than or equal to a certain threshold (e.g., "timeDurationForQCL"), the UE may apply the TCI state of the scheduling CORESET to the reception of the PDSCH (see Figure 6).

[0165] If two active TCI states correspond to a scheduling CORESET, the UE may apply the two TCI states (QCL assumptions) of that scheduling offset for receiving the PDSCH.

[0166] If one active TCI state corresponds to a scheduling CORESET, the UE may apply one TCI state of that scheduling offset for receiving the PDSCH.

[0167] UE capability, which is defined as whether or not scheduling using DCI without a TCI field is supported, may be specified.

[0168] If the UE does not support the UE capability (does not support scheduling using DCI without a TCI field), the UE may assume / expect that the TCI field is included in the scheduling DCI (e.g., DCI format 1_1 / 1_2).

[0169] If the UE supports the UE capability and does not support a specific UE capability (e.g., UE capability for dynamic switching of single TRP and SFN), the UE may assume / expect that the TCI field is included in the scheduling DCI (e.g., DCI format 1_1 / 1_2).

[0170] Embodiment 1-2 If the (applicable) time offset (scheduling offset) between the reception of a scheduling DCI and the reception of a PDSCH corresponding to that DCI is equal to or greater than a specific threshold (e.g., "timeDurationForQCL") and the scheduling DCI does not include a TCI field (hereinafter referred to as case 1-2), the UE may assume / judge to apply a specific TCI state as the TCI state of the PDSCH (SFN PDSCH) (see Figure 7).

[0171] For example, in the above case 1-2, if at least one TCI codepoint (activated by the MAC CE) corresponds to two TCI states, the UE may assume that the DM-RS ports of the PDSCH (or PDSCH transmission occasions) of a serving cell are quasi-colocated with the RS(s) with respect to the QCL parameter(s) associated with the TCI states corresponding to the lowest codepoint among the TCI codepoints containing (corresponding to) two different TCI states.

[0172] Also, for example, in the above case 1-2, and when a specific higher layer parameter (e.g., enableTwoDefaultTCI-States) is configured for the UE, if at least one TCI codepoint (activated in the MAC CE) corresponds to two TCI states, the UE may assume that the DMRS port of the PDSCH (or PDSCH transmission opportunity) of the serving cell is in a QCL relationship with the RS for the QCL parameter associated with the TCI state corresponding to the lowest codepoint among the TCI codepoints that include (correspond to) two different TCI states.

[0173] Also, for example, in the above case 1-2, and a specific upper layer parameter (e.g., enableTwoDefaultTCI-States) is not set for the UE, the UE may determine / decide the TCI state of the PDSCH according to at least one method described in the above embodiment 1-1.

[0174] Also, for example, in the above case 1-2, and a specific upper layer parameter (e.g., enableTwoDefaultTCI-States) is not set for the UE, the UE may determine / decide to use the TCI state of the CORESET with the lowest CORESET ID in the latest slot (monitoring slot) for receiving the PDSCH.

[0175] According to the first and second embodiments, one or two TCI states (default TCI states) of a PDSCH (SFN PDSCN) can be derived / determined without using a TCI field, thereby reducing DCI overhead.

[0176] According to the first embodiment described above, even when an SFN PDCCH is not configured and an SFN PDSCH is configured, the TCI state / default TCI state can be appropriately determined / judged / applied.

[0177] <Second embodiment> An SFN PDSCH may be configured for the UE. RRC parameters related to the SFN PDSCH (e.g., sfnSchemePdsch) may be configured / notified to the UE.

[0178] The SFN PDCCH may not be configured for the UE. The RRC parameters related to the SFN PDCCH (for example, sfnSchemePdcch) may not be configured / notified for the UE.

[0179] An SFN PDCCH may be configured for the UE. RRC parameters related to the SFN PDCCH (for example, sfnSchemePdcch) may be configured / notified to the UE.

[0180] <<Embodiment 2-0>> If the (applicable) time offset (scheduling offset) between the reception of a scheduling DCI (e.g., DCI format 1_0 / 1_1 / 1_2) and the reception of a PDSCH corresponding to that DCI is smaller than a certain threshold (e.g., "timeDurationForQCL") and a certain higher layer parameter (e.g., enableTwoDefaultTCI-States) is configured for the UE, the UE may apply the TCI state corresponding to a certain TCI codepoint among the two active TCI states for the PDSCH (among the TCI codepoints indicating two TCI states) to the reception of the PDSCH (SFN PDSCH) (see Figure 8).

[0181] The specific TCI code point may be, for example, the lowest TCI code point among the TCI code points indicating two TCI states.

[0182] At this time, the UE may assume / expect the scheduling DCI to include a TCI field.

[0183] <<Embodiment 2-1>> If the (applicable) time offset (scheduling offset) between the reception of a scheduling DCI (e.g., DCI format 1_0 / 1_1 / 1_2) and the reception of a PDSCH corresponding to that DCI is smaller than a certain threshold (e.g., "timeDurationForQCL"), the case where the DCI scheduling the PDSCH does not include a TCI field may be supported. In this case, the UE may support scheduling using a DCI without a TCI field.

[0184] In this case, the UE may apply the TCI state corresponding to a specific TCI codepoint among the two active TCI states for the PDSCH (among the TCI codepoints indicating the two TCI states) to receive the PDSCH (SFN PDSCH) (see FIG. 8).

[0185] The specific TCI code point may be, for example, the lowest TCI code point among the TCI code points indicating two TCI states.

[0186] UE capability, which is defined as whether or not scheduling using DCI without a TCI field is supported, may be specified.

[0187] If the UE does not support the UE capability (does not support scheduling using DCI without a TCI field), the UE may assume / expect that the TCI field is included in the scheduling DCI (e.g., DCI format 1_0 / 1_1 / 1_2).

[0188] If the UE supports the UE capability and does not support a specific UE capability (e.g., UE capability for dynamic switching of single TRP and SFN), the UE may assume / expect that the TCI field is included in the scheduling DCI (e.g., DCI format 1_0 / 1_1 / 1_2).

[0189] <<Embodiment 2-2>> If the (applicable) time offset (scheduling offset) between the reception of a scheduling DCI (e.g., DCI format 1_0 / 1_1 / 1_2) and the reception of a PDSCH corresponding to that DCI is smaller than a specific threshold (e.g., "timeDurationForQCL") and a specific higher layer parameter (e.g., enableTwoDefaultTCI-States) is not configured for the UE (condition 2-2-1), at least one of the cases where the DCI scheduling the PDSCH does not include a TCI field and the DCI includes a TCI field may be supported. In this case, the UE may support at least one of scheduling using a DCI without a TCI field and scheduling using a DCI with a TCI field.

[0190] If the (applicable) time offset (scheduling offset) between the reception of a scheduling DCI (e.g., DCI format 1_0 / 1_1 / 1_2) and the reception of a PDSCH corresponding to that DCI is smaller than a certain threshold (e.g., "timeDurationForQCL") and all of the TCI states corresponding to the activated TCI codepoints correspond to one TCI state (condition 2-2-2), then at least one of the cases where the DCI scheduling the PDSCH does not include a TCI field and the DCI includes a TCI field may be supported. In this case, the UE may support at least one of scheduling using a DCI without a TCI field and scheduling using a DCI with a TCI field.

[0191] In conditions 2-2-1 / 2-2-2, the UE may apply a specific TCI state as the TCI state of the PDSCH (SFN PDSCH) (see FIG. 9).

[0192] For example, the specific TCI state may be the TCI state of the CORESET with the lowest CORESET ID in the latest slot (monitoring slot).

[0193] If the CORESET has multiple (two) TCI states, the UE may determine that the multiple TCI states apply.

[0194] If the CORESET has one TCI state, the UE may determine that one TCI state should be applied.

[0195] According to embodiment 2-1 / 2-2, one or two TCI states (default TCI states) of a PDSCH (SFN PDSCN) can be derived / determined without using a TCI field, thereby reducing DCI overhead.

[0196] According to the second embodiment described above, it is possible to appropriately determine / judge / apply the TCI state / default TCI state for the SFN PDSCH.

[0197] <Third embodiment> For transmission and reception using a single DCI-based multi-TRP, the PDSCH may be scheduled in a first DCI format (e.g., DCI format 1_1 / 1_2).

[0198] As shown in Fig. 5, in the operation related to the SFN PDCCH / PDSCH, the PDSCH may be scheduled in a second DCI format (e.g., DCI format 1_0 / 1_1 / 1_2). The second DCI format (e.g., DCI format 1_0 / 1_1 / 1_2) may be defined as the DCI format for scheduling the SFN PDSCH.

[0199] When an RRC parameter (eg, sfnSchemePdsch) related to the SFN PDSCH is configured / notified to the UE, the PDSCH (SFN PDSCH) may be scheduled in the second DCI format (eg, DCI format 1_0 / 1_1 / 1_2).

[0200] According to the third embodiment described above, it is possible to distinguish between a DCI format for scheduling a PDSCH that uses a single DCI-based multi-TRP and a DCI format for scheduling an SFN PDSCH, thereby clarifying the operation of the UE / base station.

[0201] (wireless communication system) The configuration of a wireless communication system according to an embodiment of the present disclosure will be described below. In this wireless communication system, communication is performed using any one of the wireless communication methods according to the above embodiments of the present disclosure or a combination thereof.

[0202] 10 is a diagram illustrating an example of a schematic configuration of a wireless communication system according to an embodiment. The wireless communication system 1 may be a system that realizes communication using Long Term Evolution (LTE) or 5th generation mobile communication system New Radio (5G NR) specified by the Third Generation Partnership Project (3GPP).

[0203] The wireless communication system 1 may also support dual connectivity between multiple Radio Access Technologies (RATs) (Multi-RAT Dual Connectivity (MR-DC)). MR-DC may 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.

[0204] 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.

[0205] The wireless communication system 1 may support dual connectivity between multiple base stations within the same RAT (for example, dual connectivity in which both the MN and the SN are NR base stations (gNBs) (NR-NR Dual Connectivity (NN-DC))).

[0206] The wireless communication system 1 may include a base station 11 that forms a macrocell C1 with a relatively wide coverage, and base stations 12 (12a-12c) that are located within the macrocell C1 and form small cells C2 that are smaller than the macrocell C1. A user terminal 20 may be located within at least one of the cells. The locations and numbers of the cells and user terminals 20 are not limited to the embodiment shown in the figure. Hereinafter, when there is no need to distinguish between the base stations 11 and 12, they will be collectively referred to as base station 10.

[0207] The user terminal 20 may be connected to at least one of the multiple base stations 10. The user terminal 20 may utilize at least one of carrier aggregation (CA) using multiple component carriers (CC) and dual connectivity (DC).

[0208] Each CC may be included in at least one of a first frequency band (Frequency Range 1 (FR1)) and a second frequency band (Frequency Range 2 (FR2)). The macro cell C1 may be included in FR1, and the small cell C2 may be included in FR2. For example, FR1 may be a frequency band of 6 GHz or less (sub-6 GHz), and FR2 may be a frequency band above 24 GHz (above-24 GHz). Note that the frequency bands and definitions of FR1 and FR2 are not limited to these, and for example, FR1 may be a frequency band higher than FR2.

[0209] Furthermore, the user terminal 20 may perform communication using at least one of Time Division Duplex (TDD) and Frequency Division Duplex (FDD) in each CC.

[0210] The multiple base stations 10 may be connected by wire (for example, optical fiber conforming to the Common Public Radio Interface (CPRI), an X2 interface, or the like) or wirelessly (for example, NR communication). For example, when NR communication is used as a backhaul between the base stations 11 and 12, the base station 11 corresponding to the upper station may be called an Integrated Access Backhaul (IAB) donor, and the base station 12 corresponding to the relay station (relay) may be called an IAB node.

[0211] The base station 10 may be connected to the core network 30 directly or via another base station 10. The core network 30 may include, for example, at least one of an Evolved Packet Core (EPC), a 5G Core Network (5GCN), a Next Generation Core (NGC), and the like.

[0212] The user terminal 20 may be a terminal compatible with at least one of communication methods such as LTE, LTE-A, and 5G.

[0213] An Orthogonal Frequency Division Multiplexing (OFDM)-based radio access scheme may be used in the radio communication system 1. For example, Cyclic Prefix OFDM (CP-OFDM), Discrete Fourier Transform Spread OFDM (DFT-s-OFDM), Orthogonal Frequency Division Multiple Access (OFDMA), Single Carrier Frequency Division Multiple Access (SC-FDMA), or the like may be used in at least one of the downlink (DL) and uplink (UL).

[0214] The radio access scheme may also be called a waveform. Note that in the wireless communication system 1, other radio access schemes (for example, other single-carrier transmission schemes, other multi-carrier transmission schemes) may be used as the UL and DL radio access schemes.

[0215] In the wireless communication system 1, a downlink shared channel (Physical Downlink Shared Channel (PDSCH)) shared by each user terminal 20, a broadcast channel (Physical Broadcast Channel (PBCH)), a downlink control channel (Physical Downlink Control Channel (PDCCH)), etc. may be used as the downlink channel.

[0216] Furthermore, in the wireless communication system 1, an uplink shared channel (Physical Uplink Shared Channel (PUSCH)) shared by each user terminal 20, an uplink control channel (Physical Uplink Control Channel (PUCCH)), a random access channel (Physical Random Access Channel (PRACH)), etc. may be used as an uplink channel.

[0217] The PDSCH transmits user data, higher layer control information, System Information Block (SIB), etc. The PUSCH may transmit user data, higher layer control information, etc. Furthermore, the PBCH may transmit Master Information Block (MIB).

[0218] Lower layer control information may be transmitted by the PDCCH. The lower layer control information may include, for example, Downlink Control Information (DCI) including scheduling information for at least one of the PDSCH and the PUSCH.

[0219] Note that the DCI for scheduling the PDSCH may be referred to as a DL assignment, a DL DCI, etc., and the DCI for scheduling the PUSCH may be referred to as an UL grant, a UL DCI, etc. Note that the PDSCH may be interpreted as DL data, and the PUSCH may be interpreted as UL data.

[0220] A control resource set (CORESET) and a search space may be used to detect the PDCCH. The CORESET corresponds to resources to search for DCI. The search space corresponds to a search region and a search method for PDCCH candidates. One CORESET may be associated with one or more search spaces. The UE may monitor a CORESET associated with a certain search space based on the search space configuration.

[0221] One search space may correspond to PDCCH candidates corresponding to one or more aggregation levels. One or more search spaces may be called a search space set. Note that the terms "search space," "search space set," "search space setting," "search space set setting," "CORESET," "CORESET setting," etc. in the present disclosure may be read interchangeably.

[0222] The PUCCH may transmit uplink control information (UCI) including at least one of channel state information (CSI), acknowledgement information (which may be called, for example, Hybrid Automatic Repeat reQuest ACKnowledgement (HARQ-ACK), ACK / NACK, etc.), and scheduling request (SR). The PRACH may transmit a random access preamble for establishing a connection with a cell.

[0223] In the present disclosure, downlink, uplink, etc. may be expressed without adding "link." Also, various channels may be expressed without adding "Physical" to the beginning.

[0224] In the wireless communication system 1, a synchronization signal (SS), a downlink reference signal (DL-RS), etc. may be transmitted. In the wireless communication system 1, a cell-specific reference signal (CRS), a channel state information reference signal (CSI-RS), a demodulation reference signal (DMRS), a positioning reference signal (PRS), a phase tracking reference signal (PTRS), etc. may be transmitted as DL-RS.

[0225] The synchronization signal may be, for example, at least one of a Primary Synchronization Signal (PSS) and a Secondary Synchronization Signal (SSS). A signal block including the SS (PSS, SSS) and the PBCH (and DMRS for the PBCH) may be referred to as an SS / PBCH block, an SS Block (SSB), or the like. Note that the SS, SSB, and the like may also be referred to as reference signals.

[0226] Furthermore, in the wireless communication system 1, a sounding reference signal (SRS), a demodulation reference signal (DMRS), etc. may be transmitted as an uplink reference signal (UL-RS). Note that the DMRS may also be called a user equipment-specific reference signal (UE-specific reference signal).

[0227] (base station) 11 is a diagram showing an example of the configuration of a base station according to an embodiment. The base station 10 includes a control unit 110, a transceiver unit 120, a transceiver antenna 130, and a transmission line interface 140. Note that the base station may include one or more of each of the control unit 110, the transceiver unit 120, the transceiver antenna 130, and the transmission line interface 140.

[0228] In this example, the functional blocks of the characteristic parts of the present embodiment are mainly shown, and it may be assumed that the base station 10 also has other functional blocks necessary for wireless communication. Some of the processing of each unit described below may be omitted.

[0229] The control unit 110 performs overall control of the base station 10. The control unit 110 can be configured from a controller, a control circuit, and the like that are explained based on common understanding in the technical field to which the present disclosure relates.

[0230] The control unit 110 may control signal generation, scheduling (e.g., resource allocation, mapping), etc. The control unit 110 may control transmission and reception using the transceiver unit 120, the transceiver antenna 130, and the transmission path interface 140, measurement, etc. The control unit 110 may generate data to be transmitted as signals, control information, sequences, etc., and transfer them to the transceiver unit 120. The control unit 110 may perform call processing (setting up, releasing, etc.) of communication channels, status management of the base station 10, management of radio resources, etc.

[0231] The transceiver unit 120 may include a baseband unit 121, a radio frequency (RF) unit 122, and a measurement unit 123. The baseband unit 121 may include a transmission processing unit 1211 and a reception processing unit 1212. The transceiver unit 120 may be configured with a transmitter / receiver, an RF circuit, a baseband circuit, a filter, a phase shifter, a measurement circuit, a transceiver circuit, etc., which are described based on common understanding in the technical field related to the present disclosure.

[0232] The transmitting / receiving unit 120 may be configured as an integrated transmitting / receiving unit, or may be composed of a transmitting unit and a receiving unit. The transmitting unit may be composed of a transmission processing unit 1211 and an RF unit 122. The receiving unit may be composed of a reception processing unit 1212, an RF unit 122, and a measurement unit 123.

[0233] The transmitting and receiving antenna 130 can be configured from an antenna described based on common understanding in the technical field to which the present disclosure pertains, such as an array antenna.

[0234] The transceiver 120 may transmit the above-mentioned downlink channel, synchronization signal, downlink reference signal, etc. The transceiver 120 may receive the above-mentioned uplink channel, uplink reference signal, etc.

[0235] The transceiver 120 may form at least one of a transmission beam and a reception beam using digital beamforming (for example, precoding), analog beamforming (for example, phase rotation), or the like.

[0236] The transceiver 120 (transmission processing unit 1211) may perform Packet Data Convergence Protocol (PDCP) layer processing, Radio Link Control (RLC) layer processing (e.g., RLC retransmission control), Medium Access Control (MAC) layer processing (e.g., HARQ retransmission control), etc. on data, control information, etc. obtained from the control unit 110, and generate a bit string to be transmitted.

[0237] The transceiver 120 (transmission processor 1211) may perform transmission processing such as channel coding (which may include error correction coding), modulation, mapping, filtering, Discrete Fourier Transform (DFT) processing (if necessary), Inverse Fast Fourier Transform (IFFT) processing, precoding, and digital-to-analog conversion on the bit string to be transmitted, and output a baseband signal.

[0238] The transmitting / receiving unit 120 (RF unit 122) may perform modulation to a radio frequency band, filtering, amplification, etc. on the baseband signal, and transmit the radio frequency band signal via the transmitting / receiving antenna .

[0239] On the other hand, the transmitting / receiving unit 120 (RF unit 122) may perform amplification, filtering, demodulation to a baseband signal, etc. on the radio frequency band signal received by the transmitting / receiving antenna .

[0240] The transceiver 120 (reception processing unit 1212) may apply reception processing such as analog-to-digital conversion, Fast Fourier Transform (FFT) processing, Inverse Discrete Fourier Transform (IDFT) processing (if necessary), filtering, demapping, demodulation, decoding (which may include error correction decoding), MAC layer processing, RLC layer processing, and PDCP layer processing to the acquired baseband signal, thereby acquiring user data, etc.

[0241] The transceiver 120 (measurement unit 123) may perform measurements on the received signal. For example, the measurement unit 123 may perform Radio Resource Management (RRM) measurements, Channel State Information (CSI) measurements, etc. based on the received signal. The measurement unit 123 may 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 may be output to the control unit 110.

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

[0243] The transmitting section and receiving section of the base station 10 in the present disclosure may be configured by at least one of the transmitting / receiving section 120, the transmitting / receiving antenna 130, and the transmission path interface 140.

[0244] The transceiver 120 may transmit configuration information (e.g., sfnSchemePdsch) related to a single frequency network (SFN) physical downlink shared channel (PDSCH). The controller 110 may determine a TCI state to apply to the SFN PDSCH based on a condition related to an offset (scheduling offset) from reception of downlink control information (DCI) that schedules the SFN PDSCH to reception of the SFN PDSCH, whether or not the DCI includes a transmission configuration indication (TCI) field, and the configuration information (first to third embodiments).

[0245] (user terminal) 12 is a diagram showing an example of the configuration of a user terminal according to one embodiment. The user terminal 20 includes a control unit 210, a transceiver unit 220, and a transceiver antenna 230. Note that the user terminal 20 may include one or more of each of the control unit 210, the transceiver unit 220, and the transceiver antenna 230.

[0246] Note that this example mainly shows functional blocks of the characteristic parts of the present embodiment, and it may be assumed that the user terminal 20 also has other functional blocks necessary for wireless communication. Some of the processing of each unit described below may be omitted.

[0247] The control unit 210 performs overall control of the user terminal 20. The control unit 210 can be configured from a controller, a control circuit, and the like that are explained based on common understanding in the technical field to which the present disclosure relates.

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

[0249] The transceiver unit 220 may include a baseband unit 221, an RF unit 222, and a measurement unit 223. The baseband unit 221 may include a transmission processing unit 2211 and a reception processing unit 2212. The transceiver unit 220 may be configured from a transmitter / receiver, an RF circuit, a baseband circuit, a filter, a phase shifter, a measurement circuit, a transceiver circuit, etc., which are described based on common understanding in the technical field related to the present disclosure.

[0250] The transmitting / receiving unit 220 may be configured as an integrated transmitting / receiving unit, or may be composed of a transmitting unit and a receiving unit. The transmitting unit may be composed of a transmission processing unit 2211 and an RF unit 222. The receiving unit may be composed of a reception processing unit 2212, an RF unit 222, and a measurement unit 223.

[0251] The transmitting / receiving antenna 230 can be configured as an antenna described based on common understanding in the technical field to which the present disclosure pertains, such as an array antenna.

[0252] The transceiver 220 may receive the above-mentioned downlink channel, synchronization signal, downlink reference signal, etc. The transceiver 220 may transmit the above-mentioned uplink channel, uplink reference signal, etc.

[0253] The transceiver 220 may form at least one of a transmission beam and a reception beam using digital beamforming (for example, precoding), analog beamforming (for example, phase rotation), or the like.

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

[0255] The transceiver 220 (transmission processor 2211) may perform transmission processing such as channel coding (which may include error correction coding), modulation, mapping, filtering, DFT processing (if necessary), IFFT processing, precoding, and digital-to-analog conversion on the bit string to be transmitted, and output a baseband signal.

[0256] Whether or not to apply DFT processing may be based on the setting of transform precoding. When transform precoding is enabled for a certain channel (e.g., PUSCH), the transceiver unit 220 (transmission processing unit 2211) may perform DFT processing as the transmission processing to transmit the channel using a DFT-s-OFDM waveform, and when transform precoding is not enabled, the transceiver unit 220 may not perform DFT processing as the transmission processing.

[0257] The transmitting / receiving unit 220 (RF unit 222) may perform modulation to a radio frequency band, filtering, amplification, etc. on the baseband signal, and transmit the radio frequency band signal via the transmitting / receiving antenna 230.

[0258] On the other hand, the transmitting / receiving unit 220 (RF unit 222) may perform amplification, filtering, demodulation to a baseband signal, etc. on the radio frequency band signal received by the transmitting / receiving antenna 230.

[0259] The transceiver 220 (reception processing unit 2212) may apply reception processing such as analog-to-digital conversion, FFT processing, IDFT processing (if necessary), filtering, demapping, demodulation, decoding (which may include error correction decoding), MAC layer processing, RLC layer processing, and PDCP layer processing to the acquired baseband signal to acquire user data, etc.

[0260] The transceiver 220 (measurement unit 223) may perform measurements on the received signal. For example, the measurement unit 223 may perform RRM measurement, CSI measurement, etc. based on the received signal. The measurement unit 223 may 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 may be output to the control unit 210.

[0261] The transmitting section and receiving section of the user terminal 20 in the present disclosure may be configured by at least one of the transmitting / receiving section 220 and the transmitting / receiving antenna 230.

[0262] The transceiver 220 may receive configuration information (e.g., sfnSchemePdsch) related to a single frequency network (SFN) physical downlink shared channel (PDSCH). The controller 210 may determine a TCI state to apply to the SFN PDSCH based on a condition related to an offset (scheduling offset) from reception of downlink control information (DCI) that schedules the SFN PDSCH to reception of the SFN PDSCH, whether or not the DCI includes a transmission configuration indication (TCI) field, and the configuration information (first to third embodiments).

[0263] If the offset is greater than a certain threshold (e.g., "timeDurationForQCL") and the DCI does not include the TCI field, the control unit 210 may apply the TCI state of the control resource set associated with the DCI to the SFN PDSCH (first embodiment).

[0264] If the offset is greater than a specific threshold (e.g., "timeDurationForQCL") and the DCI does not include the TCI field, and if at least one TCI code point of the activated TCI state corresponds to two TCI states, the control unit 210 may determine that the demodulation reference signal port of the PDSCH is in a QCL relationship with a reference signal related to a quasi-collocation (QCL) parameter associated with the TCI state corresponding to the lowest code point among the TCI code points corresponding to two different TCI states (first embodiment).

[0265] If the offset is less than or equal to a specific threshold (e.g., "timeDurationForQCL") and a specific higher layer parameter (e.g., enableTwoDefaultTCI-States) is not set, the control unit 210 may apply the TCI state of the control resource set with the lowest control resource set ID in the latest slot to the SFN PDSCH (second embodiment).

[0266] (Hardware configuration) The block diagrams used to explain the above embodiments show functional blocks. These functional blocks (components) are realized by any combination of at least one of hardware and software. Furthermore, the method for realizing each functional block is not particularly limited. That is, each functional block may be realized using a single device that is physically or logically coupled, or may be realized using two or more physically or logically separated devices that are directly or indirectly connected (for example, using wires, wirelessly, etc.) and these multiple devices. The functional block may also be realized by combining the single device or multiple devices with software.

[0267] Here, the functions include, but are not limited to, judgment, determination, judgment, calculation, computation, processing, derivation, investigation, search, confirmation, reception, transmission, output, access, resolution, selection, election, establishment, comparison, assumption, expectation, deeming, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, and assignment. For example, a functional block (component) that performs transmission may be called a transmitting unit, transmitter, etc. As mentioned above, the implementation method of each is not particularly limited.

[0268] For example, a base station, a user terminal, etc. according to an embodiment of the present disclosure may function as a computer that performs processing of the wireless communication method of the present disclosure. Fig. 13 is a diagram illustrating an example of the hardware configuration of a base station and a user terminal according to an embodiment. The above-described base station 10 and user terminal 20 may be physically configured as a computer device including a processor 1001, a memory 1002, a storage 1003, a communication device 1004, an input device 1005, an output device 1006, a bus 1007, etc.

[0269] In this disclosure, terms such as apparatus, circuit, device, section, unit, etc. may be read interchangeably. The hardware configurations of the base station 10 and the user terminal 20 may be configured to include one or more of the devices shown in the drawings, or may be configured to exclude some of the devices.

[0270] For example, although only one processor 1001 is shown, there may be multiple processors. Furthermore, processing may be performed by one processor, or processing may be performed by two or more processors simultaneously, serially, or in other ways. Furthermore, processor 1001 may be implemented by one or more chips.

[0271] Each function in the base station 10 and the user terminal 20 is realized, for example, by loading predetermined software (programs) onto hardware such as a processor 1001 and a memory 1002, causing the processor 1001 to perform calculations, control communication via the communication device 1004, and control at least one of reading and writing data in the memory 1002 and the storage 1003.

[0272] The processor 1001, for example, runs an operating system to control the entire computer. The processor 1001 may be configured as a central processing unit (CPU) including an interface with peripheral devices, a control device, an arithmetic unit, a register, etc. For example, at least a part of the above-mentioned control unit 110 (210), transmission / reception unit 120 (220), etc. may be realized by the processor 1001.

[0273] The processor 1001 also reads programs (program codes), software modules, data, etc. from at least one of the storage 1003 and the communication device 1004 into the memory 1002, and executes various processes in accordance with these. The programs used are those that cause a computer to execute at least some of the operations described in the above-described embodiments. For example, the control unit 110 (210) may be realized by a control program stored in the memory 1002 and running on the processor 1001, and the other functional blocks may be realized in a similar manner.

[0274] The memory 1002 is a computer-readable recording medium and may be configured by at least one of, for example, a read-only memory (ROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), a random access memory (RAM), or other suitable storage medium. The memory 1002 may also be referred to as a register, a cache, a main memory, or the like. The memory 1002 may store executable programs (program codes), software modules, and the like for implementing a wireless communication method according to an embodiment of the present disclosure.

[0275] Storage 1003 is a computer-readable recording medium and may be constituted by at least one of, for example, a flexible disk, a floppy disk, a magneto-optical disk (e.g., a compact disc (e.g., a Compact Disc ROM (CD-ROM)), a digital versatile disc, a Blu-ray disc), a removable disk, a hard disk drive, a smart card, a flash memory device (e.g., a card, stick, key drive), a magnetic stripe, a database, a server, or other suitable storage medium. Storage 1003 may also be referred to as a secondary storage device.

[0276] The communication device 1004 is hardware (transmission / reception device) for communicating between computers via at least one of a wired network and a wireless network, and is also referred to as, for example, a network device, a network controller, a network card, or a communication module. The communication device 1004 may be configured to include a high-frequency switch, a duplexer, a filter, a frequency synthesizer, etc. to realize at least one of frequency division duplex (FDD) and time division duplex (TDD). For example, the above-mentioned transmission / reception unit 120 (220), transmission / reception antenna 130 (230), etc. may be realized by the communication device 1004. The transmission / reception unit 120 (220) may be implemented as a transmission unit 120a (220a) and a reception unit 120b (220b) that are physically or logically separated.

[0277] The input device 1005 is an input device (for example, a keyboard, a mouse, a microphone, a switch, a button, a sensor, etc.) that receives input from the outside. The output device 1006 is an output device (for example, a display, a speaker, a light emitting diode (LED) lamp, etc.) that outputs to the outside. The input device 1005 and the output device 1006 may be integrated into one device (for example, a touch panel).

[0278] Furthermore, each device, such as the processor 1001 and the memory 1002, is connected by a bus 1007 for communicating information. The bus 1007 may be configured using a single bus, or may be configured using different buses between each device.

[0279] Furthermore, the base station 10 and the user terminal 20 may be configured to include hardware such as a microprocessor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a programmable logic device (PLD), or a field programmable gate array (FPGA), and some or all of the functional blocks may be realized using such hardware. For example, the processor 1001 may be implemented using at least one of these pieces of hardware.

[0280] (Variation) Note that terms explained in the present disclosure and terms necessary for understanding the present disclosure may be replaced with terms having the same or similar meanings. For example, a channel, a symbol, and a signal (signal or signaling) may be interchangeable. A signal may also be a message. A reference signal may be abbreviated as RS, and may also be called a pilot, pilot signal, etc. depending on the applicable standard. A component carrier (CC) may also be called a cell, frequency carrier, carrier frequency, etc.

[0281] A radio frame may be composed of one or more periods (frames) in the time domain. Each of the one or more periods (frames) constituting a radio frame may be called a subframe. Furthermore, a subframe may be composed of one or more slots in the time domain. A subframe may have a fixed time length (e.g., 1 ms) that is independent of numerology.

[0282] Here, the numerology may be a communication parameter applied to at least one of transmission and reception of a signal or channel, and may indicate at least one of, for example, a subcarrier spacing (SCS), a bandwidth, a symbol length, a cyclic prefix length, a transmission time interval (TTI), the number of symbols per TTI, a radio frame structure, a specific filtering process performed by a transceiver in the frequency domain, and a specific windowing process performed by a transceiver in the time domain.

[0283] A slot may be composed of one or more symbols in the time domain (such as an Orthogonal Frequency Division Multiplexing (OFDM) symbol or a Single Carrier Frequency Division Multiple Access (SC-FDMA) symbol), and may be a time unit based on numerology.

[0284] A slot may include multiple minislots. Each minislot may consist of one or multiple symbols in the time domain. A minislot may also be called a subslot. A minislot may consist of fewer symbols than a slot. A PDSCH (or PUSCH) transmitted in a time unit larger than a minislot may be called PDSCH (PUSCH) mapping type A. A PDSCH (or PUSCH) transmitted using a minislot may be called PDSCH (PUSCH) mapping type B.

[0285] A radio frame, a subframe, a slot, a minislot, and a symbol all represent time units for transmitting signals. The radio frame, the subframe, the slot, the minislot, and the symbol may be referred to by other names corresponding to the radio frame, the subframe, the slot, the minislot, and the symbol. Note that the time units such as a frame, a subframe, a slot, a minislot, and a symbol in the present disclosure may be interchangeable.

[0286] For example, one subframe may be referred to as a TTI, or multiple consecutive subframes may be referred to as a TTI, or one slot or one minislot may be referred to as a TTI. That is, at least one of a subframe and a TTI may be a subframe (1 ms) in existing LTE, a period shorter than 1 ms (for example, 1-13 symbols), or a period longer than 1 ms. Note that the unit representing the TTI may be called a slot, minislot, etc., instead of a subframe.

[0287] Here, TTI refers to, for example, the smallest time unit for scheduling in wireless communication. For example, in an LTE system, a base station performs scheduling to allocate radio resources (such as frequency bandwidth and transmission power that can be used by each user terminal) to each user terminal in TTI units. However, the definition of TTI is not limited to this.

[0288] The TTI may be a transmission time unit for a channel-encoded data packet (transport block), a code block, a code word, etc., or may be a processing unit for scheduling, link adaptation, etc. When a TTI is given, the time interval (e.g., the number of symbols) to which a transport block, a code block, a code word, etc. is actually mapped may be shorter than the TTI.

[0289] When one slot or one minislot is called a TTI, one or more TTIs (i.e., one or more slots or one or more minislots) may be the minimum time unit for scheduling. Also, the number of slots (minislots) constituting the minimum time unit for scheduling may be controlled.

[0290] A TTI having a time length of 1 ms may be called a regular TTI (TTI in 3GPP Rel. 8-12), normal TTI, long TTI, regular subframe, normal subframe, long subframe, slot, etc. A TTI shorter than a regular TTI may be called a shortened TTI, short TTI, partial or fractional TTI, shortened subframe, short subframe, minislot, subslot, slot, etc.

[0291] In addition, a long TTI (e.g., a normal TTI, a subframe, etc.) may be interpreted as a TTI having a time length of more than 1 ms, and a short TTI (e.g., a shortened TTI, etc.) may be interpreted as a TTI having a TTI length shorter than the TTI length of a long TTI and equal to or greater than 1 ms.

[0292] A resource block (RB) is a resource allocation unit in the time domain and the frequency domain, and may include one or more consecutive subcarriers in the frequency domain. The number of subcarriers included in an RB may be the same regardless of numerology, for example, 12. The number of subcarriers included in an RB may also be determined based on numerology.

[0293] In addition, an RB may include one or more symbols in the time domain and may have a length of one slot, one minislot, one subframe, or one TTI. One TTI, one subframe, etc. may each be composed of one or more resource blocks.

[0294] Note that one or more RBs may also be called a physical resource block (PRB), a sub-carrier group (SCG), a resource element group (REG), a PRB pair, an RB pair, etc.

[0295] Furthermore, a resource block may be composed of one or more resource elements (REs). For example, one RE may be a radio resource region of one subcarrier and one symbol.

[0296] A Bandwidth Part (BWP), which may also be referred to as a fractional bandwidth, may represent a subset of contiguous common resource blocks (RBs) for a given numerology on a given carrier, where the common RBs may be identified by their index relative to a common reference point of the carrier. PRBs may be defined in a given BWP and numbered within that BWP.

[0297] The BWP may include an UL BWP (a BWP for UL) and a DL BWP (a BWP for DL). One or more BWPs may be configured for a UE within one carrier.

[0298] At least one of the configured BWPs may be active, and the UE may not expect to transmit or receive a given signal / channel outside the active BWP. Note that the terms "cell," "carrier," etc. in this disclosure may be read as "BWP."

[0299] The above-described structures of radio frames, subframes, slots, minislots, symbols, etc. are merely examples. For example, the number of subframes included in a radio frame, the number of slots per subframe or radio frame, the number of minislots included in a slot, the number of symbols and RBs included in a slot or minislot, the number of subcarriers included in an RB, the number of symbols in a TTI, the symbol length, the cyclic prefix (CP) length, etc. may be changed in various ways.

[0300] Furthermore, the information, parameters, etc. described in the present disclosure may be expressed using absolute values, may be expressed using relative values ​​from a predetermined value, or may be expressed using other corresponding information. For example, a radio resource may be indicated by a predetermined index.

[0301] The names used for parameters and the like in this disclosure are not intended to be limiting in any way. Furthermore, the mathematical expressions and the like using these parameters may differ from those explicitly disclosed in this disclosure. The various channels (PUCCH, PDCCH, etc.) and information elements may be identified by any suitable names, and therefore the various names assigned to these various channels and information elements are not intended to be limiting in any way.

[0302] The information, signals, etc. described in this disclosure may be represented using any of a variety of different technologies. For example, data, instructions, commands, information, signals, bits, symbols, chips, etc. that may be referred to throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or magnetic particles, optical fields or photons, or any combination thereof.

[0303] Furthermore, information, signals, etc. may be output from a higher layer to a lower layer and / or from a lower layer to a higher layer. Information, signals, etc. may be input / output via multiple network nodes.

[0304] Input and output information, signals, etc. may be stored in a specific location (for example, memory) or may be managed using a management table. Input and output information, signals, etc. may be overwritten, updated, or added. Output information, signals, etc. may be deleted. Input information, signals, etc. may be transmitted to another device.

[0305] Notification of information is not limited to the aspects / embodiments described in the present disclosure, and may be performed using other methods. For example, notification of information in the present disclosure may be performed by physical layer signaling (e.g., Downlink Control Information (DCI) and Uplink Control Information (UCI)), higher layer signaling (e.g., Radio Resource Control (RRC) signaling, broadcast information (Master Information Block (MIB) and System Information Block (SIB)), Medium Access Control (MAC) signaling), other signals, or a combination thereof.

[0306] Note that the physical layer signaling may be called Layer 1 / Layer 2 (L1 / L2) control information (L1 / L2 control signal), L1 control information (L1 control signal), etc. Furthermore, the RRC signaling may be called an RRC message, such as an RRC connection setup message or an RRC connection reconfiguration message. Furthermore, the MAC signaling may be notified using, for example, a MAC Control Element (CE).

[0307] Furthermore, notification of specified information (e.g., notification that "it is X") is not limited to explicit notification, but may be made implicitly (e.g., by not notifying the specified information or by notifying other information).

[0308] The determination may be made by a value represented by one bit (0 or 1), by a Boolean value represented by true or false, or by a comparison of numerical values ​​(e.g., comparison with a predetermined value).

[0309] Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.

[0310] Software, instructions, information, etc. may also be transmitted or received over a transmission medium. For example, if software is transmitted from a website, server, or other remote source using wired technologies (such as coaxial cable, fiber optic cable, twisted pair, Digital Subscriber Line (DSL)), and / or wireless technologies (such as infrared, microwave), then these wired and / or wireless technologies are included within the definition of transmission media.

[0311] As used in this disclosure, the terms "system" and "network" may be used interchangeably. A "network" may refer to devices included in the network (e.g., base stations).

[0312] In the present disclosure, terms such as "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," "beam width," "beam angle," "antenna," "antenna element," "panel," etc. may be used interchangeably.

[0313] In this disclosure, terms such as "base station (BS)," "radio 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," "component carrier," etc. may be used interchangeably. Base stations may also be referred to by terms such as macrocell, small cell, femtocell, picocell, etc.

[0314] 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 be provided with communication service by a base station subsystem (e.g., a small indoor base station (Remote Radio Head (RRH))). The term "cell" or "sector" refers to a part or the entire coverage area of ​​a base station and / or base station subsystem that provides communication service within this coverage.

[0315] In this disclosure, the terms "Mobile Station (MS)," "user terminal," "User Equipment (UE)," "terminal," etc. may be used interchangeably.

[0316] A mobile station may also be referred to as a subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, or some other suitable terminology.

[0317] At least one of the base station and the mobile station may be called a transmitting device, a receiving device, a wireless communication device, etc. Note that at least one of the base station and the mobile station may be a device mounted on a moving object, the moving object itself, etc.

[0318] The mobile body is a movable object that can move at any speed and naturally includes cases where the mobile body is stationary. Examples of the mobile body include, but are not limited to, vehicles, transport vehicles, automobiles, motorcycles, bicycles, connected cars, excavators, bulldozers, wheel loaders, dump trucks, forklifts, trains, buses, handcars, rickshaws, ships and other watercraft, airplanes, rockets, satellites, drones, multicopters, quadcopters, balloons, and objects mounted thereon. The mobile body may also be a mobile body that moves autonomously based on an operation command.

[0319] The mobile object may be a vehicle (e.g., a car, an airplane, etc.), an unmanned mobile object (e.g., a drone, an autonomous vehicle, etc.), or a robot (manned or unmanned). Note that 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 may be an Internet of Things (IoT) device such as a sensor.

[0320] 14 is a diagram showing an example of a vehicle according to an embodiment. Vehicle 40 includes a drive unit 41, a steering unit 42, an accelerator pedal 43, a brake pedal 44, a shift lever 45, left and right front wheels 46, left and right rear wheels 47, axles 48, an electronic control unit 49, various sensors (including a current sensor 50, an RPM sensor 51, an air pressure sensor 52, a vehicle speed sensor 53, an acceleration sensor 54, an accelerator pedal sensor 55, a brake pedal sensor 56, a shift lever sensor 57, and an object detection sensor 58), an information service unit 59, and a communication module 60.

[0321] The drive unit 41 is configured with at least one of an engine, a motor, and a hybrid of an engine and a motor, for example. The steering unit 42 includes at least a steering wheel (also called a handle) and is configured to steer at least one of the front wheels 46 and the rear wheels 47 based on the operation of the steering wheel operated by the user.

[0322] The electronic control unit 49 is composed of a microprocessor 61, memory (ROM, RAM) 62, and a communication port (e.g., an input / output (IO) port) 63. Signals are input to the electronic control unit 49 from various sensors 50-58 provided in the vehicle. The electronic control unit 49 may also be called an Electronic Control Unit (ECU).

[0323] The signals from the various sensors 50-58 include a current signal from a current sensor 50 that senses the current of the motor, a rotation speed signal of the front wheels 46 / rear wheels 47 obtained by a rotation speed sensor 51, an air pressure signal of the front wheels 46 / rear wheels 47 obtained by an air pressure sensor 52, a vehicle speed signal obtained by a vehicle speed sensor 53, an acceleration signal obtained by an acceleration sensor 54, a depression amount signal of the accelerator pedal 43 obtained by an accelerator pedal sensor 55, a depression amount signal of the brake pedal 44 obtained by a brake pedal sensor 56, an operation signal of the shift lever 45 obtained by a shift lever sensor 57, and a detection signal for detecting obstacles, vehicles, pedestrians, etc. obtained by an object detection sensor 58.

[0324] The information service unit 59 is composed of various devices, such as a car navigation system, an audio system, speakers, a display, a television, and a radio, for providing (outputting) various information such as driving information, traffic information, and entertainment information, and one or more ECUs for controlling these devices. The information service unit 59 uses information acquired from external devices via the communication module 60 or the like to provide various information / services (for example, multimedia information / multimedia services) to the occupants of the vehicle 40.

[0325] The information service unit 59 may include input devices (e.g., keyboards, mice, microphones, switches, buttons, sensors, touch panels, etc.) that accept input from the outside, and may also include output devices (e.g., displays, speakers, LED lamps, touch panels, etc.) that output to the outside.

[0326] The driving assistance system unit 64 is configured with various devices that provide functions for preventing accidents and reducing the driver's driving burden, such as millimeter-wave radar, Light Detection and Ranging (LiDAR), cameras, positioning locators (e.g., Global Navigation Satellite System (GNSS)), map information (e.g., High Definition (HD) maps, Autonomous Vehicle (AV) maps), gyro systems (e.g., Inertial Measurement Units (IMUs), Inertial Navigation Systems (INSs)), Artificial Intelligence (AI) chips, and AI processors, as well as one or more ECUs that control these devices. The driving assistance system unit 64 also transmits and receives various information via the communication module 60 to realize driving assistance functions or autonomous driving functions.

[0327] The communication module 60 can communicate with the microprocessor 61 and components of the vehicle 40 via the communication port 63. For example, the communication module 60 transmits and receives data (information) via the communication port 63 to and from the drive unit 41, steering unit 42, accelerator pedal 43, brake pedal 44, shift lever 45, left and right front wheels 46, left and right rear wheels 47, axles 48, the microprocessor 61 and memory (ROM, RAM) 62 in the electronic control unit 49, and the various sensors 50-58, which are provided in the vehicle 40.

[0328] The communication module 60 is a communication device that can be controlled by the microprocessor 61 of the electronic control unit 49 and can communicate with an external device. For example, it transmits and receives various information to and from the external device via wireless communication. The communication module 60 may be located either inside or outside the electronic control unit 49. The external device may be, for example, the above-mentioned base station 10 or user terminal 20. Furthermore, the communication module 60 may be, for example, at least one of the above-mentioned base station 10 and user terminal 20 (or may function as at least one of the base station 10 and user terminal 20).

[0329] The communication module 60 may transmit at least one of signals from the above-mentioned various sensors 50-58 input to the electronic control unit 49, information obtained based on the signals, and information based on input from the outside (user) obtained via the information service unit 59 to an external device via wireless communication. The electronic control unit 49, the various sensors 50-58, the information service unit 59, etc. may be referred to as input units that accept input. For example, the PUSCH transmitted by the communication module 60 may include information based on the above-mentioned input.

[0330] The communication module 60 receives various information (traffic information, traffic signal information, vehicle distance information, etc.) transmitted from external devices and displays it on an information service unit 59 provided in the vehicle. The information service unit 59 may also be called an output unit that outputs information (for example, outputs information to a device such as a display or speaker based on the PDSCH received by the communication module 60 (or data / information decoded from the PDSCH)).

[0331] Furthermore, the communication module 60 stores various information received from external devices in a memory 62 that can be used by the microprocessor 61. Based on the information stored in the memory 62, the microprocessor 61 may control the drive unit 41, steering unit 42, accelerator pedal 43, brake pedal 44, shift lever 45, left and right front wheels 46, left and right rear wheels 47, axles 48, various sensors 50-58, and the like provided in the vehicle 40.

[0332] Furthermore, a base station in the present disclosure may be read as a user terminal. For example, the aspects / embodiments of the present disclosure may be applied to a configuration in which communication between a base station and a user terminal is replaced with communication between multiple user terminals (which may be called, for example, Device-to-Device (D2D) or Vehicle-to-Everything (V2X)). In this case, the user terminal 20 may be configured to have the functions of the base station 10 described above. Furthermore, terms such as "uplink" and "downlink" may be read as terms corresponding to terminal-to-terminal communication (for example, "sidelink"). For example, terms such as uplink channel and downlink channel may be read as sidelink channel.

[0333] Similarly, the user terminal in the present disclosure may be read as a base station, in which case the base station 10 may be configured to have the functions of the user terminal 20 described above.

[0334] In the present disclosure, an operation described as being performed by a base station may be performed by its upper node in some cases. It is apparent that in a network including one or more network nodes having a base station, various operations performed for communication with a terminal may be performed by the base station, one or more network nodes other than the base station (such as, but not limited to, a Mobility Management Entity (MME) and a Serving-Gateway (S-GW)), or a combination thereof.

[0335] Each aspect / embodiment described in this disclosure may be used alone, in combination, or switched depending on the implementation. Furthermore, the order of the processing procedures, sequences, flowcharts, etc. of each aspect / embodiment described in this disclosure may be changed unless inconsistent. For example, the methods described in this disclosure present elements of various steps using an example order, and are not limited to the specific order presented.

[0336] Each aspect / embodiment described in the present disclosure may be a technology other than Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 6th generation mobile communication system (6G), xth generation mobile communication system (xG (x is, for example, an integer or decimal number)), Future Radio Access (FRA), New-Radio Access Technology (RAT), New Radio (NR), New radio access (NX), Future generation radio access (FX), Global System for Mobile communications (GSM (registered trademark)), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE The present invention may be applied to systems that use 802.20, Ultra-WideBand (UWB), Bluetooth (registered trademark), or other appropriate wireless communication methods, or to next-generation systems that are expanded, modified, created, or defined based on these. It may also be applied to a combination of multiple systems (e.g., a combination of LTE or LTE-A and 5G).

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

[0338] As used in this disclosure, any reference to an element using a designation such as "first," "second," etc. does not generally limit the quantity or order of those elements. These designations may be used in this disclosure as a convenient method of distinguishing between two or more elements. Thus, a reference to a first and a second element does not imply that only two elements may be employed or that the first element must in some way precede the second element.

[0339] The term "determining," as used in this disclosure, may encompass a wide variety of actions. For example, "determining" may be considered to be judging, calculating, computing, processing, deriving, investigating, looking up, search, inquiry (e.g., looking up in a table, database, or another data structure), ascertaining, etc.

[0340] Additionally, "determining" may be considered to be "determining" receiving (e.g., receiving information), transmitting (e.g., sending information), input, output, accessing (e.g., accessing data in memory), etc.

[0341] Also, "decision" may be considered to be "deciding" resolving, selecting, choosing, establishing, comparing, etc. In other words, "decision" may be considered to be "deciding" on some action.

[0342] Furthermore, "judgment (decision)" may be interpreted as "assuming," "expecting," "considering," or the like.

[0343] As used in this disclosure, the terms "connected," "coupled," or any variation thereof, refer to any direct or indirect connection or coupling between two or more elements, and may include the presence of one or more intermediate elements between two elements that are "connected" or "coupled" to each other. The coupling or connection between elements may be physical, logical, or a combination thereof. For example, "connected" may be read as "access."

[0344] In this disclosure, when two elements are connected, they may be considered to be "connected" or "coupled" to one another using one or more wires, cables, printed electrical connections, etc., as well as using electromagnetic energy having wavelengths in the radio frequency range, microwave range, light (both visible and invisible) range, etc., as some non-limiting and non-exhaustive examples.

[0345] In the present disclosure, the term "A and B are different" may mean "A and B are different from each other." The term may also mean "A and B are each different from C." Terms such as "separate" and "coupled" may also be interpreted in the same way as "different."

[0346] When used in this disclosure, the terms "include," "including," and variations thereof are intended to be inclusive, similar to the term "comprising." Furthermore, when used in this disclosure, the term "or" is not intended to be an exclusive or.

[0347] In this disclosure, where articles are added by translation, such as a, an, and the in English, the disclosure may include that the nouns following these articles are in the plural form.

[0348] Although the invention according to the present disclosure has been described in detail above, it is clear to those skilled in the art that the invention according to the present disclosure is not limited to the embodiments described in the present disclosure. The invention according to the present disclosure can be implemented in modified and altered forms without departing from the spirit and scope of the invention as defined by the description of the claims. Therefore, the description of the present disclosure is intended to be illustrative and explanatory and does not impose any limiting meaning on the invention according to the present disclosure.

Claims

1. a transmitter for reporting UE capabilities indicating support for scheduling via downlink control information (DCI) without a transmission configuration indication (TCI) field; a receiving unit that receives at least one of configuration information related to a single frequency network (SFN) physical downlink shared channel (PDSCH) and configuration information related to a single frequency network (SFN) physical downlink control channel (PDCCH); a control unit that determines a TCI state of a control resource set associated with the first DCI to be applied to the SFN PDSCH based on a predetermined condition, when an SFN PDSCH is configured according to the received configuration information for the SFN PDSCH, an offset from reception of a first DCI scheduling a first PDSCH to reception of the first PDSCH is equal to or greater than a specific threshold, and the transmitter unit reports the UE capability indicating support for scheduling by a DCI without a TCI field, the first DCI does not include the TCI field, The control unit, when the SFN PDSCH is configured according to the received configuration information for the SFN PDSCH, an offset from reception of a second DCI scheduling a second PDSCH to reception of the second PDSCH is equal to or greater than the specific threshold, and an SFN PDCCH is not configured without receiving configuration information for the SFN PDCCH, reports the UE capability indicating that the UE supports scheduling using a DCI without the TCI field, and when the UE does not support a single transmission / reception point (TRP) and UE capability for dynamic switching of the SFN PDSCH, expects the TCI field to be included in the second DCI.

2. The terminal according to claim 1 , wherein the DCI is in DCI format 1_1 or 1_2.

3. reporting a UE capability indicating that the UE supports scheduling via downlink control information (DCI) without a transmission configuration indication (TCI) field; receiving at least one of configuration information related to a single frequency network (SFN) physical downlink shared channel (PDSCH) and configuration information related to a single frequency network (SFN) physical downlink control channel (PDCCH); When an SFN PDSCH is configured according to the received configuration information for the SFN PDSCH, an offset from reception of a first DCI scheduling a first PDSCH to reception of the first PDSCH is equal to or greater than a specific threshold, and the UE reports a capability indicating that scheduling by a DCI without a TCI field is supported, the first DCI does not include the TCI field, and a TCI state of a control resource set associated with the first DCI to be applied to the SFN PDSCH is determined based on a predetermined condition; and when the SFN PDSCH is configured according to received configuration information for the SFN PDSCH, an offset from reception of a second DCI scheduling a second PDSCH to reception of the second PDSCH is equal to or greater than the specific threshold, and when the SFN PDCCH is not configured without receiving configuration information for the SFN PDCCH, reporting the UE capability indicating that scheduling by DCI without the TCI field is supported, and when the UE does not support UE capability for single transmission / reception point (TRP) and dynamic switching of the SFN PDSCH, expecting the TCI field to be included in the second DCI.

4. a receiver for receiving a UE capability indicating support for scheduling via downlink control information (DCI) without a transmission configuration indication (TCI) field; a transmitter that transmits at least one of configuration information related to a single frequency network (SFN) physical downlink shared channel (PDSCH) and configuration information related to a single frequency network (SFN) physical downlink control channel (PDCCH); a control unit that determines, based on a predetermined condition, a TCI state of a control resource set associated with the first DCI to be applied to the SFN PDSCH when the first DCI does not include the TCI field and the first DCI is applied to the SFN PDSCH if an SFN PDSCH is configured according to the transmitted configuration information for the SFN PDSCH, an offset from reception of a first DCI scheduling a first PDSCH to reception of the first PDSCH is equal to or greater than a specific threshold, and the receiving unit receives the UE capability indicating support for scheduling by a DCI without a TCI field; a base station, wherein the SFN PDSCH is configured according to the transmitted configuration information for the SFN PDSCH, an offset from reception of a second DCI scheduling a second PDSCH to reception of the second PDSCH is equal to or greater than the specific threshold, and an SFN PDCCH is not configured without transmitting configuration information for the SFN PDCCH, the receiving unit receives the UE capability indicating that scheduling by DCI without the TCI field is supported, and if a terminal does not support a single transmission / reception point (TRP) and UE capability for dynamic switching of the SFN PDSCH, the second DCI includes the TCI field.

5. A system having a terminal and a base station, a transmitter for reporting UE capability indicating that the terminal supports scheduling by downlink control information (DCI) without a transmission configuration indication (TCI) field; a receiving unit that receives at least one of configuration information related to a single frequency network (SFN) physical downlink shared channel (PDSCH) and configuration information related to a single frequency network (SFN) physical downlink control channel (PDCCH); a control unit that determines a TCI state of a control resource set associated with the first DCI to be applied to the SFN PDSCH based on a predetermined condition, when an SFN PDSCH is configured according to the received configuration information for the SFN PDSCH, an offset from reception of a first DCI scheduling a first PDSCH to reception of the first PDSCH is equal to or greater than a specific threshold, and the transmitter unit reports the UE capability indicating support for scheduling by a DCI without a TCI field, the first DCI does not include the TCI field, the control unit, when the SFN PDSCH is configured according to received configuration information regarding the SFN PDSCH, an offset from reception of a second DCI scheduling a second PDSCH to reception of the second PDSCH is equal to or greater than the specific threshold, and an SFN PDCCH is not configured without receiving configuration information regarding the SFN PDCCH, expects the TCI field to be included in the second DCI if the transmitter reports the UE capability indicating that it supports scheduling using a DCI without the TCI field and does not support UE capability regarding a single transmission / reception point (TRP) and dynamic switching of the SFN PDSCH; a receiver for receiving the UE capability indicating that the base station supports scheduling by DCI without the TCI field; A transmitter that transmits at least one of configuration information regarding the SFN PDSCH and configuration information regarding the SFN PDCCH; and a control unit that determines the TCI state of the control resource set to be applied to the SFN PDSCH based on the predetermined condition, when the SFN PDSCH is configured according to the transmitted configuration information for the SFN PDSCH, the offset from reception of the first DCI to reception of the first PDSCH is equal to or greater than the specific threshold, and the receiving unit receives the UE capability indicating that scheduling by DCI without the TCI field is supported, and the first DCI does not include the TCI field.

Images