WO2025158656A1 - Terminal, wireless communication method, and base station - Google Patents

Abstract

A terminal according to one aspect of the present disclosure is characterized by including: a reception unit that receives setting information for a Sounding Reference Signal (SRS) which is set for a specific application that is used for management of an uplink (UL) beam to a UL reception point; and a control unit that determines a UL beam for the UL reception point on the basis of a specified rule or a transmitted instruction. According to this one aspect of the present disclosure, UL beam management can be performed appropriately for UL reception points/microBSs.

Description

Terminal, wireless communication method and base station

This disclosure relates to terminals, wireless communication methods, and base stations in next-generation mobile communication systems.

Long Term Evolution (LTE) was specified for Universal Mobile Telecommunications System (UMTS) networks with the aim of achieving even higher data rates and lower latency (Non-Patent Document 1). Furthermore, LTE-Advanced (3GPP Rel. 10-14) was specified with the aim of achieving even greater capacity and sophistication over LTE (Third Generation Partnership Project (3GPP (registered trademark)) Release (Rel.) 8 and 9).

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, etc.) are also being considered.

3GPP TS 36.300 V8.12.0 “Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Univers al　Terrestrial　Radio　Access　Network　(E-UTRAN);　Overall　description;　Stage 2　(Release　8)”, April 2010

In future wireless communication systems, in order to expand uplink (UL) coverage, it is being considered to install UL receiving points in addition to general transmitting and receiving points. Also being considered are high-density UL deployments/Heterogeneous Networks (HetNets) using macro Base Stations (BSs) and micro BSs.

However, it is not clear how UL beam management for UL receiving points/micro BSs should be performed. This could result in inappropriate UL transmission to UL receiving points/micro BSs, resulting in reduced communication throughput.

Therefore, one of the objectives of this disclosure is to provide a terminal, wireless communication method, and base station that can appropriately perform UL beam management for UL receiving points/micro BSs.

A terminal according to one aspect of the present disclosure is characterized by having a receiving unit that receives setting information for a Sounding Reference Signal (SRS) that is set to a specific purpose for use in managing an uplink (UL) beam to an uplink (UL) receiving point, and a control unit that determines a UL beam for the UL receiving point based on a specified rule or transmitted instructions.

According to one aspect of the present disclosure, UL beam management can be properly performed for UL receiving points/micro BSs.

1A is a diagram showing an example of a general arrangement of transmission and reception points, and FIG. 1B is a diagram showing an example of a high-density UL arrangement. Figure 2 shows an example of DL/UL coverage of a Heterogeneous Network (HetNet). FIG. 3 is a diagram showing an example of option 1-2 of the second embodiment. FIG. 4 is a diagram showing examples of options 1-3 of the second embodiment. FIG. 5 is a diagram showing examples of options 1-4 of the second embodiment. FIG. 6 is a diagram illustrating a first example of the SRS resource set indication field of option 1'-1 of the second embodiment. FIG. 7 is a diagram illustrating a second example of the SRS resource set indication field of option 1'-1 of the second embodiment. FIG. 8 is a diagram illustrating an example of a schematic configuration of a wireless communication system according to an embodiment. FIG. 9 is a diagram illustrating an example of the configuration of a base station according to an embodiment. FIG. 10 is a diagram illustrating an example of the configuration of a user terminal according to an embodiment. FIG. 11 is a diagram illustrating an example of the hardware configuration of a base station and a user terminal according to an embodiment. FIG. 12 is a diagram illustrating an example of a vehicle according to an embodiment.

(Control of SRS and PUSCH transmission)
In Rel. 15 NR, a terminal (user terminal, User Equipment (UE)) may receive information (SRS configuration information, for example, parameters in the RRC control element "SRS-Config") used to transmit a measurement reference signal (e.g., a sounding reference signal (SRS)).

Specifically, the UE may receive at least one of information regarding one or more SRS resource sets (SRS resource set information, e.g., the RRC control element "SRS-ResourceSet") and information regarding one or more SRS resources (SRS resource information, e.g., the RRC control element "SRS-Resource").

An SRS resource set may be associated with (or group together) a predetermined number of SRS resources. Each SRS resource may be identified by an SRS Resource Indicator (SRI) or SRS Resource Identifier (ID).

The SRS resource set information may include the SRS resource set ID (SRS-ResourceSetId), a list of SRS resource IDs (SRS-ResourceId) used in the resource set, the SRS resource type, and SRS usage information.

Here, the SRS resource type may indicate either periodic SRS (P-SRS), semi-persistent SRS (SP-SRS), or aperiodic CSI (Aperiodic SRS (A-SRS)). Note that the UE may transmit P-SRS and SP-SRS periodically (or periodically after activation) and transmit A-SRS based on an SRS request in the DCI.

Furthermore, the use (RRC parameter "usage", L1 (Layer-1) parameter "SRS-SetUse") may be, for example, beam management, codebook (CB), non-codebook (NCB), antenna switching, etc. An SRS for codebook or non-codebook use may be used to determine a precoder for codebook-based or non-codebook-based uplink shared channel (Physical Uplink Shared Channel (PUSCH)) transmission based on the SRI.

For example, in the case of codebook-based transmission, the UE may determine the precoder (precoding matrix) for PUSCH transmission based on the SRI, the Transmitted Rank Indicator (TRI), and the Transmitted Precoding Matrix Indicator (TPMI). In the case of non-codebook-based transmission, the UE may determine the precoder for PUSCH transmission based on the SRI.

The SRS resource information may include an SRS resource ID (SRS-ResourceId), the number of SRS ports, the SRS port number, the transmission comb, SRS resource mapping (e.g., time and/or frequency resource position, resource offset, resource period, number of repetitions, number of SRS symbols, SRS bandwidth, etc.), hopping-related information, an SRS resource type, a sequence ID, spatial relationship information of the SRS, etc.

The spatial relationship information of the SRS (e.g., the RRC information element "spatialRelationInfo") may indicate spatial relationship information between a predetermined reference signal and the SRS. The predetermined reference signal may be at least one of a Synchronization Signal/Physical Broadcast Channel (SS/PBCH) block, a Channel State Information Reference Signal (CSI-RS), and an SRS (e.g., another SRS). The SS/PBCH block may be referred to as a Synchronization Signal Block (SSB).

The spatial relationship information for the SRS may include at least one of an SSB index, a CSI-RS resource ID, and an SRS resource ID as an index for the predetermined reference signal.

Note that in the present disclosure, the SSB index, SSB resource ID, and SSB Resource Indicator (SSBRI) may be interchangeable. Also, the CSI-RS index, CSI-RS resource ID, and CSI-RS Resource Indicator (CRI) may be interchangeable. Also, the SRS index, SRS resource ID, and SRI may be interchangeable.

The spatial relationship information of the SRS may include a serving cell index, a BWP index (BWP ID), etc. corresponding to the above-mentioned specified reference signal.

When spatial relationship information regarding an SSB or CSI-RS and an SRS is configured for a certain SRS resource, the UE may transmit the SRS resource using the same spatial domain filter (spatial domain transmit filter) as the spatial domain filter used to receive the SSB or CSI-RS. In this case, the UE may assume that the UE receive beam for the SSB or CSI-RS and the UE transmit beam for the SRS are the same.

When spatial relationship information regarding a certain SRS (target SRS) resource is configured between another SRS (reference SRS) and the SRS (target SRS), the UE may transmit the target SRS resource using the same spatial domain filter (spatial domain transmit filter) as the spatial domain filter (spatial domain transmit filter) used to transmit the reference SRS. In other words, in this case, the UE may assume that the UE transmit beam for the reference SRS and the UE transmit beam for the target SRS are the same.

The UE may determine the spatial relationship of the PUSCH scheduled by a DCI (e.g., DCI format 0_1) based on the value of a predetermined field (e.g., the SRS resource identifier (SRI) field) in the DCI. Specifically, the UE may use spatial relationship information (e.g., the RRC information element "spatialRelationInfo") of the SRS resources determined based on the value of the predetermined field (e.g., the SRI) for PUSCH transmission.

In Rel. 15/16 NR, when codebook-based transmission is used for PUSCH, the UE is configured by RRC with an SRS resource set for the codebook with up to two SRS resources, and one of the up to two SRS resources may be indicated by DCI (a 1-bit SRI field). The transmission beam for PUSCH is specified by the SRI field.

The UE may determine the TPMI and number of layers (transmission rank) for the PUSCH based on the precoding information and number of layers field (hereinafter also referred to as the precoding information field). The UE may select a precoder based on the TPMI, number of layers, etc. from an uplink codebook for the same number of SRS ports as indicated by the upper layer parameter "nrofSRS-Ports" configured for the SRS resource specified by the SRI field.

In Rel. 15/16 NR, when non-codebook-based transmission is used for PUSCH, the UE is configured by RRC with a non-codebook-used SRS resource set having up to four SRS resources, and one or more of the up to four SRS resources may be indicated by DCI (2-bit SRI field).

The UE may determine the number of layers (transmission rank) for the PUSCH based on the SRI field. For example, the UE may determine that the number of SRS resources specified by the SRI field is the same as the number of layers for the PUSCH. The UE may also calculate a precoder for the SRS resources.

If the CSI-RS (which may also be called associated CSI-RS) associated with the SRS resource (or the SRS resource set to which the SRS resource belongs) is configured by a higher layer, the transmission beam for the PUSCH may be calculated based on (measurements of) the configured associated CSI-RS. Otherwise, the transmission beam for the PUSCH may be specified by the SRI.

The UE may be configured to use codebook-based PUSCH transmission or non-codebook-based PUSCH transmission using the higher layer parameter "txConfig," which indicates the transmission scheme. This parameter may indicate the value "codebook" or "non-codebook."

In this disclosure, codebook-based PUSCH (codebook-based PUSCH transmission, codebook-based transmission) may refer to PUSCH when "codebook" is configured as the transmission scheme for the UE. In this disclosure, non-codebook-based PUSCH (non-codebook-based PUSCH transmission, non-codebook-based transmission) may refer to PUSCH when "non-codebook" is configured as the transmission scheme for the UE.

(TCI, spatial relationships, QCL)
In NR, it is 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 the signal and the channel (referred to as the signal/channel) based on the transmission configuration indication state (TCI state).

TCI states may refer to those that apply to downlink signals/channels. The equivalent of TCI states that apply to uplink signals/channels may be expressed as spatial relations.

TCI status 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 status may be set in the UE for each channel or signal.

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 parameters (e.g., spatial Rx parameters) is the same between these different signals/channels (i.e., they have QCL with respect to at least one of these).

Note that the spatial reception parameters may correspond to the reception beam of the UE (e.g., a reception analog beam), and the beam may be identified based on the spatial QCL. In this disclosure, the QCL (or at least one element of the QCL) may be interpreted as sQCL (spatial QCL).

A plurality of types (QCL types) of QCL may be defined. For example, four QCL types A to D 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 as follows:
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.

The UE's assumption 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.

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

The TCI state may be, for example, information regarding the QCL between the target channel (in other words, the reference signal (RS) for that 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 of these.

Note that the channel/signal to which the TCI state is applied may be referred to as the target channel/reference signal (target channel/RS), or simply the target, and the other signal may be referred to as the reference signal (reference RS), source RS, or simply the reference.

The channel for which the TCI state or spatial relationship is set (specified) may be, for example, at least one of the following: 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)).

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 tracking CSI-RS (also called a tracking reference signal (TRS)), a QCL detection reference signal (also called a QRS), a demodulation reference signal (DMRS), etc.

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.

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

(Scenario 1: High-density UL deployment (UL-only TRP))
In Rel. 15 NR, the coverage (reaching distance) of PUSCH, PUCCH, PRACH, PDSCH, PDCCH, and PBCH is uneven. PUSCH coverage is limited, especially at higher frequencies. Future wireless communication systems (e.g., Rel. 18, Rel. 19, or later) are expected to improve at least one of UL coverage and UL throughput.

In order to expand UL coverage, the installation of UL reception points in addition to general transmission and reception points is being considered. Here, we will explain examples of the placement of general transmission and reception points, as well as an example of a placement with UL reception points (high-density UL placement).

Figure 1A shows an example of a typical transmission/reception point arrangement. In Figure 1A, a UE receives a DL signal from a transmission/reception point (TRP) and transmits a UL signal to that TRP. For example, if the UE and TRP are far apart, there may be significant path loss, resulting in a decrease in communication quality.

Figure 1B is a diagram showing an example of a high-density UL deployment. In order to expand UL coverage, it is being considered to provide UL reception points as shown in Figure 1B in addition to DL transmission points as shown in Figure 1A. In Figure 1B, a UE receives DL signals from a DL transmission point (TRP/Central TRP/DL TRP/Macro TRP) corresponding to a macro cell, and transmits UL signals to a UL reception point (e.g., a reception point with smaller path loss/reception power). However, the UE may also be capable of performing UL transmission to a DL transmission point.

By using a high-density UL configuration like that of Figure 1B, it is possible to reduce path loss, improve UL signaling quality, and obtain a higher coding rate, thereby improving both coverage and UL data rates, compared to a general configuration like that of Figure 1A. Furthermore, since the UL receiving point primarily performs reception, it requires fewer functions (such as power amplifiers) and is therefore less costly than a transmission/reception point corresponding to a typical small cell, making deployment management much easier.

(Scenario 2: Decoupling of DL TRP and UL TRP in HetNet)
In the present disclosure, a Heterogeneous Network (HetNet) using a macro Base Station (BS) (DL TRP) and a micro BS (UL TRP) may be applied (see FIG. 2). In a typical HetNet, the transmission power of the macro BS and the micro BS is different. Also, the optimal DL coverage and the optimal UL coverage are different. For example, the DL coverage is determined by the RSRP, and the UL coverage is determined by the path loss (PL).

In the example shown in Figure 2, the UE is included in the optimal DL coverage of the macro BS and the optimal UL coverage of the micro BS. In this case, the UE can receive DL from the macro BS and transmit UL to the micro BS. However, the UE may transmit some reference signals/channels (e.g., SRS with Antenna Switching (AS) usage, used to acquire DL CSI) to the macro BS. Therefore, the UE may require two Timing Advances (TAs) in this scenario. Note that the AS SRS is transmitted to the macro BS because it allows the base station (macro BS) to measure DL CSI (e.g., determine the DL MIMO precoder) based on the SRS reception using channel reciprocity. On the other hand, the Codebook/Non-codebook SRS is transmitted to the micro BS because it is used for PUSCH precoder/beam determination.

In a HetNet, even if a micro BS has DL transmission capability, it can save energy by turning off DL most of the time. In this case, the functionality of the micro BS is similar to that of a UL-only TRP (UL Reception Point).

(SRS whose usage is beam management)
Rel. 15 and later support the use of SRS for beam management, which is independent of DL RSs. However, the spatial relationship/TCI status of the beam management SRS is dependent on the UE implementation. For example, even for the same SRS resource ID within a periodic SRS resource set, the spatial relationship/TCI status may change. This feature can also be used to obtain better beam correspondence with DL-RSs. Therefore, applying conventional beam management to the UL receiving point may result in inappropriate UL beam management.

(analysis)
As mentioned above, in order to expand UL coverage in future wireless communication systems, it is being considered to provide UL receiving points in addition to general transmitting and receiving points. Also, UL high-density deployment/Heterogeneous Network (HetNet) using macro Base Stations (BS) and micro BSs is being considered.

However, it is not clear how UL beam management for UL receiving points/micro BSs should be performed. This could result in inappropriate UL transmission to UL receiving points/micro BSs, resulting in reduced communication throughput.

The inventors therefore came up with a wireless communication method that can properly perform UL beam management for UL receiving points/micro BSs.

Embodiments of the present disclosure will be described in detail below with reference to the drawings. The wireless communication methods according to the embodiments may be applied independently or in combination.

(Various reading changes)
In the present disclosure, a word enclosed in "( )" in a sentence may indicate an explanation of the word immediately preceding it (for example, an explanation of spelling), a paraphrase, a specific example, a supplementary explanation, etc. Also, in the present disclosure, a word enclosed in "[ ]" in a sentence may be interpreted including the word in the meaning of the entire sentence, or may be interpreted excluding the word in the meaning of the entire sentence (ignoring the word in the meaning of the entire sentence). Note that "( )" and "[ ]" may also be used for purposes/meanings other than those mentioned above.

In this disclosure, "A/B" and "at least one of A and B" may be interpreted interchangeably. Also, in this disclosure, "A/B/C" may mean "at least one of A, B, and C."

In this disclosure, terms such as notify, activate, deactivate, indicate (or indicate), select, configure, update, and determine may be read interchangeably. In this disclosure, terms such as support, control, controllable, operate, and operateable may be read interchangeably.

In this disclosure, Radio Resource Control (RRC), RRC parameters, RRC messages, upper layer parameters, fields, information elements (IEs), settings, etc. may be interchangeable. In this disclosure, Medium Access Control control elements (MAC Control Elements (CEs)), update commands, activation/deactivation commands, etc. may be interchangeable.

In the present disclosure, higher layer signaling may be, for example, Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling, broadcast information, other messages (e.g., messages from the core network such as positioning protocol (e.g., NR Positioning Protocol A (NRPPa)/LTE Positioning Protocol (LPP)) messages), or a combination of these.

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.

In the present disclosure, physical layer signaling may be, for example, Downlink Control Information (DCI), Uplink Control Information (UCI), etc.

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 relationship group, Code Division Multiplexing (CDM) group, reference signal group, CORESET group, Physical Uplink Control Channel (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 interchangeably.

The UL reception point may be connected to a TRP (e.g., a base station) or a core network via wired or wireless connections. The UL reception point may be treated as a network (NW) or a base station. The UL reception point may be capable of transmitting downlink (DL) signals (e.g., PL values) and may be applied to base stations that form a macrocell. For example, the UL reception point may not transmit downlink data, but may transmit control signals/channels.

In this disclosure, the terms base station, TRP, UL receiving point, UL TRP, UL only TRP, micro cell, micro BS, and micro TRP may be interchangeable. An UL receiving point primarily performs UL reception. An UL receiving point may perform only UL reception, or may perform UL reception and DL transmission.

In this disclosure, the terms base station, TRP, DL transmission point, DL TRP, DL only TRP, UL/DL TRP, macro cell, macro BS, macro TRP, and central TRP may be interchangeable. A DL transmission point primarily performs DL transmission. A DL transmission point may perform only DL transmission, or may perform UL reception and DL transmission.

In this disclosure, UL high density deployment, distributed TRP mode, separated location mode of transmitting/receiving points, distributed transmitting/receiving mode, separated TRP mode, TRP type 1, TRP type 2, TRP type A, and TRP type B may be read interchangeably.

This disclosure may be based on at least one of single TRP, multi-TRP with multi-DCI, multi-TRP with single DCI, Scenario 1 or Scenario 2 above.

In this disclosure, UL beam management for UL reception points will be mainly described, but the same may also be applied to UL beam management for the micro BS in Figure 2. UL beam management, UL beam sweeping, and UL beam determination/selection may be read interchangeably.

(Wireless communication method)
First Embodiment
The UE may receive configuration information (e.g., SRS-Config) for an SRS configured for a specific usage, used for UL beam management to a UL reception point, from a DL transmission point or a UL reception point. The UE may control SRS transmission to the UL reception point based on the configuration information. The specific usage (new usage) may be a usage different from conventional beam management, CB, NCB, and antenna switching. This allows the gNB/NW to distinguish the SRS for UL beam management to a UL reception point from other usages.

<<Option 1>>
The number of SRS resource sets corresponding to the new application may be set. For example, at least one of the following options may be applied as the number of SRS resource sets:
Option 1-1: Maximum 1.
Option 1-2: Maximum of 2. In this case, different SRS resource sets may correspond to different UE antenna panels.
Option 1-3: 3 or more (e.g., 8).

<<Option 2>>
The number of SRS resources for each SRS resource set corresponding to the new application may be configured. For example, at least one of the following options may be applied as the number of SRS resources for each SRS resource set:
Option 2-1: Maximum 1.
Option 2-2: Maximum two.
Option 2-3: Three or more.

If different SRS resource sets are configured, the limit on the number of SRS resources per set may also be different.

<< Option 3 >>
For the SRS resource/resource set corresponding to the new application, for example, at least one of the following options may be applied:
Option 3-1: The UE may transmit different SRS resources in the same beam in different SRS resource sets. The gNB may perform receive beam sweeping between the different SRS resources. The different SRS resource sets may refer to SRS resource sets transmitted at different periods when a certain SRS resource set is transmitted periodically or semi-persistently.
Option 3-2: The UE may transmit different SRS resources in the same SRS resource set on the same beam, and the gNB may perform receive beam sweeping between the different SRS resources.
Option 3-3: The UE may perform different repeated transmissions of the same SRS resource on the same beam. The gNB may perform receive beam sweeping between different SRS resources.

<< Option 4 >>
The new application may be used in combination with the existing application. For example, at least one of the following options may be applied:
Option 4-1: UL beam management for UL reception points and UL beam management for DL TRPs (application "beam management") may be applied in combination, or a new application may indicate both UL beam management for UL reception points and UL beam management for DL TRPs.
Option 4-2: UL beam management for the UL reception point and CSI for the CB PUSCH (application "codebook") may be applied in combination, or a new application may indicate both UL beam management for the UL reception point and CSI for the CB PUSCH (application "codebook").
Option 4-3: UL beam management for UL reception points and CSI for NCB PUSCH (use "noncodebook") may be applied in combination, or a new use may indicate both UL beam management for UL reception points and CSI for NCB PUSCH (use "noncodebook").
Option 4-4: UL beam management for UL reception points and CSI for DL (application "antenna switching") may be applied in combination, or a new application may indicate both UL beam management for UL reception points and CSI for DL (application "antenna switching").

<< Option 5 >>
The UE may receive a new indication to indicate that the legacy use is for an UL reception point in addition to the legacy use (beam management, CB, NCB, or antenna switching). For example, a flag (e.g., Flag_UL TRP) indicating whether the legacy use is for an UL reception point may be indicated. Alternatively, another parameter (e.g., Timing Advance Group (TAG) ID) that implicitly indicates whether the legacy use is for an UL reception point may be used. This flag/parameter may be indicated per SRS configuration, per SRS resource set, or per SRS resource.

According to the first embodiment, the UE appropriately controls SRS transmission to an UL reception point based on the specific application corresponding to the UL reception point.

Second Embodiment
In addition to UL channel sounding (measurement), the UE may use codebook (CB) SRS transmission (SRS transmission with CB as its purpose) for UL beam management for UL reception points. For example, when a specific purpose "codebook" is configured, the UE may control SRS transmission for UL reception points and perform beam management for the UL reception points. In this case, the total amount of UL resources required for SRS transmission can be reduced.

<<Option 1>>
As the number of SRS resource sets, for example, at least one of the following options may be applied:

Option 1-1: Maximum of 1. In this case, the SRS resource set may be configured to include multiple SRS resources.

Option 1-2: Up to two. In this case, each of the two SRS resource sets may correspond to any one of multiple TRPs or any one of multiple UE panels. At least one of the TRPs may be an UL reception point.

Figure 3 shows an example of option 1-2 of the second embodiment. SRS resource set #0 may correspond to a macro TRP, and SRS resource set #1 may correspond to a UL reception point. SRS resource set #0 may correspond to UL panel 1, and SRS resource set #1 may correspond to UL panel 2.

Options 1-3: Up to three. In this case, each of the three SRS resource sets may correspond to any one of multiple TRPs or any one of multiple UE panels. At least one of the TRPs may be an UL reception point. For example, the three SRS resource sets may correspond to a macro TRP and its corresponding UE panel, another macro TRP and its corresponding UE panel, or an UL reception point and its corresponding UE panel, respectively.

Figure 4 shows examples of options 1-3 of the second embodiment. SRS resource set #0 may correspond to the macro TRP and UL panel 1, SRS resource set #1 may correspond to the macro TRP and UL panel 2, and SRS resource set #2 may correspond to the UL reception point (and UE panel 1 or 2).

Options 1-4: Up to four. In this case, each of the three SRS resource sets may correspond to any one of multiple TRPs or any one of multiple UE panels. At least one of the TRPs may be an UL reception point.

Figure 5 shows examples of options 1-4 of the second embodiment. SRS resource set #0 may correspond to the macro TRP and UL panel 1, SRS resource set #1 may correspond to the macro TRP and UL panel 2, SRS resource set #2 may correspond to the UL reception point and UE panel 1, and SRS resource set #3 may correspond to the UL reception point and UE panel 2.

Options 1-5: Maximum X (e.g., X≧5).
Option 1-5-1: Fixed value (e.g. 5, 6, 8, etc.) Fixed values may be defined.
Option 1-5-2: The number is set by RRC signaling.
Option 1-5-3: The number is indicated by the DL MAC CE/DCI.
Option 1-5-4: A combination of these. For example, the number may be indicated by the DL MAC CE/DCI from a list set by the specifications/RRC signaling.

<<Option 1>>
For the fields of the DCI scheduling the UL, for example, at least one of the following options may be applied:
Option 1'-1: For the SRS resource set indicator field, an existing field may be applied, or new bits (additional bits) corresponding to UL reception points may be applied.
Option 1'-2: An additional field may be applied indicating whether it is a macro TRP or a UL reception point.

Figure 6 shows a first example of the SRS resource set indication field for option 1'-1 of the second embodiment. In the example of Figure 6, four code points using the existing two bits are applied. For example, code point 2 indicates the application of a UL reception point (UL-only TRP).

Figure 7 shows a second example of the SRS resource set indication field for option 1'-1 of the second embodiment. In the example of Figure 7, eight code points using three bits are applied. For example, code points 4 to 7 indicate the application of UL reception points (UL-only TRPs).

<<Option 2>>
Regarding the number of SRS resources per SRS resource set (for UL beam management), for example, at least one of the following options may be applied:
Option 2-1: Maximum 2.
Option 2-2: Maximum 4.
Option 2-3: Maximum 8.
Options 2-4: Max X.
Option 2-4-1: Fixed value (e.g. 9, 10, 12, 14, 16, etc.).
Option 2-4-2: The number is set by RRC signaling.
Option 2-4-3: The number is indicated by the DL MAC CE/DCI.
Option 2-4-4: A combination of these. For example, the number may be indicated by the DL MAC CE/DCI from a list set by the specifications/RRC signaling.

For options 2-3, examples 1 and 2 below may be applied. For options 2-4, example 3 below may be applied.

Example 1: A total of 8 resources are configured. 6 of the 8 resources are used for UL beam management. The remaining 2 resources are used in the same way as Rel. 15 CB PUSCH transmission.

Example 2: A total of 8 resources are configured. 4 of the 8 resources are used for UL beam management. The remaining 4 resources are used for Rel. 16 UL full power MIMO transmit mode 2 functionality.

Example 3: A total of 16 resources are configured. The resources are divided into multiple groups, each corresponding to one TRP and containing four resources. The four resources in each group are used for UL full power MIMO transmission mode 2 function.

<<Option 2'>>
In the DCI field of the UL-scheduled DCI, the bit width of the SRI field may be extended (e.g., to 4 bits), thereby indicating increased SRS resources.

<< Option 3 >>
With respect to one or more SRS resources/SRS resource sets to be configured, for example, at least one of the following options may apply:
Option 3-1: The same RE is set.
Option 3-2: The same/different OFDM symbols are set within a slot.
Option 3-3: Same/different cyclic shifts are set.
Option 3-4: The same/different TCI conditions (QCL assumptions) are set.

Options 3-1 to 3-4 may be applied to some of the configured SRS resources/SRS resource sets (not all configured resources/resource sets), or to all SRS resources/SRS resource sets.

<< Option 4 >>
The UE may determine a beam for each SRS resource for UL beam management to the UL reception point.

According to the second embodiment, beam management corresponding to UL reception points can be performed using the conventional application "codebook," so beam management corresponding to UL reception points can be performed appropriately without changing the application specifications.

Third Embodiment
In addition to UL channel sounding (measurement), the UE may use non-codebook (NCB) SRS transmission (SRS transmission with NCB as its purpose) for UL beam management for UL reception points. For example, when a specific purpose "non-codebook" is configured, the UE may control SRS transmission for UL reception points and perform beam management for the UL reception points. In this case, the total amount of UL resources required for SRS transmission can be reduced.

<<Option 1>>
As the number of SRS resource sets, at least one of the options in option 1 of the second embodiment may be applied.

<<Option 2>>
Regarding the number of SRS resources per SRS resource set (for UL beam management), for example, at least one of the following options may be applied:

Option 2-1: Up to 4 x N. N may correspond to the number of TRPs (total of macro TRPs/DL TRPs, UL reception points/UL TRPs). For example, if one macro TRP and one UL reception point are applied, the number of SRS resources per SRS resource set is, for example, 4 x 2 = 8.

Option 2-2: Up to 4 x N. N may correspond to the number of beams for UL beam sweeping. For example, if 4 ports are used for NCB and 4 beams are used for UL beam sweeping, the number of SRS resources per SRS resource set is 4 x 4 = 16.

The "4" in options 2-1 and 2-2 may refer to the maximum MIMO layer for non-codebook PUSCH transmission by the UE. The "4" in options 2-1 and 2-2 may be replaced with another number (e.g., 8). Furthermore, "N" may refer to the number of resource groups for SRS resource configuration within an SRS resource set. Whether simultaneous transmission is possible for multiple SRS resources, and if so, the maximum number of possible simultaneous transmissions, may be determined for all resources or for each resource group.

<< Option 3 >>
For one or more SRS resources/SRS resource sets to be configured, at least one of the options in option 3 of the second embodiment may be applied.

According to the third embodiment, beam management corresponding to UL reception points can be performed using the conventional application "codebook," so beam management corresponding to UL reception points can be performed appropriately without changing the application specifications.

<Fourth embodiment>
The following describes UL beam management for a UL reception point. Regarding the determination of the UE's beam (UL beam) for a UL reception point, at least one of the following options may be applied: The fourth embodiment may be implemented, for example, when a specific application shown in the first to third embodiments is set.

<<Option 1>>
The determination of the UL beam for the UL reception point may be up to the UE implementation.

<<Option 2>>
The UE may determine the UL beam for the UL reception point based on a specified rule. At least one of the following options may be applied:
Option 2-1: The UL beam for the UL reception point is a different beam than the beam for the macro TRP.
Option 2-2: The UL beam for the UL reception point is a beam pointing in a specific direction.
Option 2-3: The UL beam for the UL reception point is a beam in the opposite direction to the beam for the macro TRP.

In Option 2, rules based on Effective Isotropic Radiated Power (EIRP) may be applied. For example, for UL beams, a beam/TCI state/spatial relationship may be applied that satisfies the spherical coverage requirement but does not satisfy the minimum EIRP requirement.

In option 2, rules based on beam directivity may be applied to the UL beam. For example, a beam/TCI state/spatial relationship that points in a direction 180 degrees different from the direction toward the macro TRP may be applied to the UL beam.

<< Option 3 >>
The UE may determine the UL beam for the UL reception point based on the configuration/instruction sent from the NW. For example, at least one of the following options may be applied:
Option 3-1: The UE may determine the UL beam based on received RRC signaling.
Option 3-2: The UE may determine the UL beam based on the received DL MAC CE.
Option 3-3: The UE may determine the UL beam based on the received DCI.

The UE may receive the configuration of multiple UL beams via RRC signaling, receive a MAC CE/DCI that activates/indicates one of the multiple UL beams, and determine the activated/indicated UL beam as the UL beam for the UL reception point.

The Rel. 17/Rel. 18 unified TCI state framework for UL beams may be applied. The UE may apply the configured/indicated unified TCI state to the beam for the UL reception point.

<< Option 4 >>
As conditions/restrictions set for UL beam management to a UL reception point, at least one of the following options may be applied:

Option 4-1: No followUnifiedTCI-State or spatial relationship is configured for the SRS resources configured for UL beam management to the UL reception point. This option may mean that the SRS beam resulting from beam management at the UL reception point is up to the UE implementation. This option may also be applied when different SRS resources are configured between the conventional SRS and the extended SRS of this disclosure.

Option 4-2: The followUnifiedTCI-State or spatial relationship is configured for the SRS resources configured for UL beam management to the UL reception point. In this case, the configured followUnifiedTCI-State or spatial relationship may be ignored. This option may mean that the SRS beam due to beam management of the UL reception point is up to the UE implementation.

followUnifiedTCI-State may be read as followUnifiedTCI-StateSRS. followUnifiedTCI-State is an RRC parameter, and when set to enabled, the UE may apply the indicated DL-dedicated TCI or joint TCI when receiving PDCCH in the corresponding CORESET.

followUnifiedTCI-StateSRS is an RRC parameter that, when set to enabled, allows the UE to apply the indicated DL-dedicated TCI or joint TCI for the SRS resource set. This parameter may be set for aperiodic SRS for beam management, or for SRS for any time-domain operation such as codebook, non-codebook, and antenna switching.

According to this embodiment, the UE can more easily or more efficiently identify an appropriate beam for the UL reception point.

Fifth Embodiment
The UE may switch on and off UL beam management for the UL reception point, which can suppress a decrease in throughput when, for example, the distance to the UL reception point changes due to the movement of the UE.

<<Aspect 5-1>>
The NW (base station) decides to switch on/off UL beam management for the UL reception point. Then, the UE may receive a configuration/instruction indicating the switch from the NW and perform the switch on/off of UL beam management based on the configuration/instruction. For example, at least one of the following options may be applied:

<<<Option 1>>>
The UE may receive the configuration/indication indicating the switch in at least one of the following ways:
Option 1-1: The UE may receive a configuration/instruction indicating the switch via RRC signaling.
Option 1-2: The UE may receive a configuration/indication indicating the switchover via the DL MAC CE.
Option 1-3: The UE may receive a configuration/instruction indicating the switch via DCI.

<<<Option 2>>>
The settings/instructions sent from the NW to the UE may include at least one of the following:
Option 2-1: Whether to turn on/off UL beam management for the UL receiving point.
Option 2-2: Beam information for UL beam sweeping.

<<<Option 3>>>
The timing/conditions under which the UE switches on/off UL beam management for an UL reception point may be at least one of the following:
Option 3-1: After receiving a setting/instruction from the network (for example, after a predetermined period of time has passed since receiving the setting/instruction).
Option 3-2: After transmitting HARQ ACK in response to receiving a setting/instruction from the network (e.g., after a predetermined period of time after reception).

The specified period for options 3-1 and 3-2 may be defined as a specific number of slots or a specific number of symbols.

As an example of the switching operation, the following example 1 or example 2 may be applied.

<<<Example 1>>>
The use of the new SRS corresponding to the new CB/NCB SRS for UL beam sweeping to the UL reception point in the second embodiment/third embodiment may be applied. For example, the legacy CB, the legacy NCB, the new CB, and the new NCB may be individually configured in the SRS resource set.

In addition to the existing CB and NCB, txConfig may also be configured with at least one of a CB corresponding to a UL reception point (e.g., codebook-RxonlyTRP) and an NCB corresponding to a UL reception point (e.g., nonCodebook-RxonlyTRP).

When a CB corresponding to an UL reception point is configured, the operation of the second embodiment may be performed. When an NCB corresponding to an UL reception point is configured, the operation of the second embodiment may be performed. When a CB is configured, the operation of a conventional CB PUSCH may be performed. When an NCB is configured, the operation of a conventional NCB PUSCH may be performed.

<<<Example 2>>>
The existing CB/NCB settings for SRS may be applied for UL beam sweeping to the UL reception point. For example, when the existing CB/NCB is set, the operation of the second embodiment/third embodiment may be applied.

The legacy CB and NCB for the SRS resource set may be configured separately. In this case, a specific RRC parameter (e.g., withRxOnlyTRP) may be configured to distinguish between operation using and not using the UL reception point. When the specific RRC parameter is configured, the UE may transmit the CB SRS or the NCB SRS, taking into account UL beam sweeping for the UL reception point (e.g., operation of the second/third embodiment). When the specific RRC parameter is not configured, the UE may transmit the conventional CB SRS or the NCB SRS.

The UE may receive a MAC CE/DCI instructing dynamic switching between legacy UL beam management and enhanced UL beam management for the UL reception point, and may perform the dynamic switching. Switching to (applying) legacy UL beam management may mean that UL beam management for the UL reception point is turned off.

When dynamic switching between legacy UL beam management and extended UL beam management for UL reception points (for example, switching based on MAC CE/DCI instructions) is performed, it is necessary to change the SRS resource/resource set or resources used for CB/NCB. For example, conventionally, there are a maximum of two SRS resources for CB, but in the case of beam sweep for UL reception points, it is preferable to be able to set more SRS resources. Therefore, at least one of the following examples 1 to 3 may be applied.

Example 1: When dynamic switching occurs (e.g., when switching to legacy UL beam management), the UE may ignore SRS resources with larger SRS resource IDs and only consider an appropriate number of SRS resources (e.g., two).
Example 2: When dynamic switching is performed (e.g., when switching to UL beam management for a UL reception point), the UE may transmit SRS on all SRS resources configured for the corresponding SRS resource set.
Example 3: When dynamic switching is performed, the UE may transmit SRS on any of the SRS resources configured for the corresponding SRS resource set.

<<Aspect 5-2>>
Switching UL beam management on and off for a UL reception point may be triggered by the UE.

<<<Option 1>>>
At least one of the following options may be applied as a condition for triggering the on/off switching of UL beam management for a UL reception point:
Option 1-1: The UE may perform switching based on the reception result (e.g., RSRP) of the RS (e.g., SSB (SS/PBCH)). For example, the UE may turn on UL beam management for the UL reception point if the RSRP of the SSB/CSI-RS from the DL transmission point is below a threshold. For example, the UE may turn off UL beam management for the UL reception point if the RSRP of the SSB/CSI-RS from the UL reception point is below a threshold.
Option 1-2: The UE may perform switching based on the reception results (e.g., RSRP) of another DL signal/channel (e.g., TRS/CSI-RS).

<<<Option 2>>>
Regarding whether the UE reports to the UL reception point about the activation (on) of UL beam management, at least one of the following options may apply:
Option 2-1: The UE does not report activation/initiation of UL beam management.
Option 2-2: The UE reports the activation/start of UL beam management. This reporting may be performed by at least one of PUSCH transmission, PUCCH transmission, and SRS transmission.
Option 2-3: The UE may request the NW to activate/start UL beam management. The request may include a request for SRS configuration.

To disable (turn off) UL beam management, methods similar to those described in options 2-1 to 2-3 above may be applied.

In the present disclosure, applying legacy operations of CB/NCB SRS transmission (e.g., legacy CB, legacy NCB, legacy UL beam management) may mean that the number of SRS resource sets/number of SRS resources is at least one of the following:
The number of SRS resource sets is up to 1 (Rel. 15) or up to 2 (Rel. 16 and later). The number of SRS resource sets may correspond to the number of UE panels.
The number of SRS resources per SRS resource set is up to 2 (Rel. 15) or up to 4 (Rel. 16 and later, for UEs supporting full power MIMO mode 2) for CB SRS.
The number of SRS resources per SRS resource set is up to 4 (Rel. 15) or up to 8 (Rel. 18 and later, for UEs supporting 8 transmissions (antenna ports)) for NCB SRS.

According to this embodiment, UL beam management for UL reception points can be easily switched on and off in response to changes in UE movement, the communication environment, etc. This makes it possible to suppress a decrease in communication throughput.

<Additional Information>
<<Notification of information to UE>>
In the above-described embodiments, any information may be notified to the UE [from a network (NW) (e.g., a base station (BS)] (in other words, the UE receives any information from the BS) using physical layer signaling (e.g., DCI), higher layer signaling (e.g., RRC signaling, MAC CE), a specific signal/channel (e.g., PDCCH, PDSCH, reference signal), or a combination thereof.

If the above notification is made by a MAC CE, the MAC CE may be identified by including a new Logical Channel ID (LCID) in the MAC subheader that is not specified in existing standards.

If the notification is made by DCI, the notification may be made by a specific field of the DCI, a Radio Network Temporary Identifier (RNTI) used to scramble the Cyclic Redundancy Check (CRC) bits assigned to the DCI, the format of the DCI, etc.

Furthermore, notification of any information to the UE in the above-described embodiments may be performed periodically, semi-persistently, or aperiodically.

<<Notification of information from UE>>
In the above-described embodiments, notification of any information from the UE [to the NW] (in other words, transmission/reporting of any information from the UE to the BS) may be performed using physical layer signaling (e.g., UCI), higher layer signaling (e.g., RRC signaling, MAC CE), specific signals/channels (e.g., PUCCH, PUSCH, PRACH, reference signals), or a combination thereof.

If the above notification is made by a MAC CE, the MAC CE may be identified by including a new LCID in the MAC subheader that is not specified in existing standards.

If the notification is made by UCI, the notification may be transmitted using PUCCH or PUSCH.

Furthermore, any information notification from the UE in the above-described embodiments may be performed periodically, semi-persistently, or aperiodically.

<<Application of each embodiment>>
In a UE/BS, the specific process/operation/control/assumption/information(s) of at least one of the above-described embodiments may be applied (used) when one or more of the following conditions are met:
- Upper layer parameters indicating the specific processing/operation/control/assumption/information are set;
The specific process/action/control/assumption/information is determined based on relevant higher layer parameters;
The specific process/action/control/assumption/information is specified/activated/triggered by MAC CE/DCI/UCI/resource/channel/RS,
Reporting or supporting specific UE capabilities indicating (or relating to) the specific processes/actions/controls/assumptions/information;
The application of the specific process/action/control/assumption/information is determined based on specific conditions.

The specific UE capabilities may indicate at least one of the following:
- Supporting the above specific processes/actions/controls/assumptions/information;
Supporting specific uses of SRS (for beam management for UL transmitting/receiving points);
Supporting scenario 1 (UL dense deployment),
Supporting Scenario 2 (HetNet),
Supporting UL transmissions (SRS/PUSCH/PUCCH/PRACH) to UL reception points;
Number of supported UL reception points/DL transmission points.

Furthermore, the above-mentioned specific UE capabilities may be capabilities that are applied across all frequencies (commonly regardless of frequency), capabilities for each frequency (e.g., one or a combination of cell, band, band combination, BWP, component carrier, etc.), capabilities for each frequency range (e.g., Frequency Range 1 (FR1), FR2, FR3, FR4, FR5, FR2-1, FR2-2), capabilities for each subcarrier spacing (SubCarrier Spacing (SCS)), or capabilities for each Feature Set (FS) or Feature Set Per Component-carrier (FSPC)).

Furthermore, the above-mentioned specific UE capabilities may be capabilities that apply across all duplexing methods (commonly regardless of the duplexing method), or may be capabilities for each duplexing method (e.g., Time Division Duplex (TDD) or Frequency Division Duplex (FDD)).

If the above conditions are not met, the UE/BS may follow the behavior specified in existing 3GPP releases.

(Additional Note)
The following inventions are added to the first to third embodiments of the present disclosure.
[Appendix 1]
A receiving unit that receives configuration information of an SRS that is configured with a specific purpose used for UL beam management to an uplink (UL) receiving point;
a control unit that controls SRS transmission to the UL reception point based on the setting information;
A terminal having:
[Appendix 2]
2. The terminal of claim 1, wherein the specific application is an application other than beam management, codebook, non-codebook, and antenna switching.
[Appendix 3]
The terminal according to claim 1 or 2, wherein the control unit uses codebook SRS transmission for UL beam management for the UL reception point.
[Appendix 4]
The terminal according to any one of Supplementary Note 1 to Supplementary Note 3, wherein the control unit uses non-codebook SRS transmission for UL beam management for the UL reception point.

(Additional Note)
The following inventions are further noted regarding the fourth and fifth embodiments of the present disclosure.
[Appendix 1]
A receiving unit that receives setting information of a Sounding Reference Signal (SRS) having a specific purpose set for use in UL beam management to an uplink (UL) receiving point;
a control unit that determines an UL beam for the UL reception point based on a specified rule or a transmitted instruction;
A terminal having:
[Appendix 2]
The terminal described in Appendix 1, wherein the control unit determines, as the UL beam for the UL receiving point, a beam different from the beam for the macro TRP, a beam heading in a specific direction, or a beam heading in the opposite direction to the beam for the macro TRP.
[Appendix 3]
The receiving unit receives a setting indicating switching on or off of UL beam management for the UL reception point;
The terminal described in Supplementary Note 1 or Supplementary Note 2, wherein the control unit switches the UL beam management on and off based on a setting indicating the switching.
[Appendix 4]
The terminal described in any one of Supplementary Note 1 to Supplementary Note 3, wherein the control unit switches on and off UL beam management for the UL reception point based on the reception result of the reference signal.

(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.

Figure 8 is a diagram showing an example of the schematic configuration of a wireless communication system according to one embodiment. Wireless communication system 1 (which may simply be referred to as system 1) may be a system that achieves communication using Long Term Evolution (LTE) specified by the Third Generation Partnership Project (3GPP), 5th generation mobile communication system New Radio (5G NR), or the like.

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.

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.

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

The wireless communication system 1 may include a base station 11 that forms a macrocell C1 with relatively wide coverage, and base stations 12 (12a-12c) that are located within the macrocell C1 and form a small cell C2 that is smaller than the macrocell C1. A user terminal 20 may be located within at least one of the cells. The location, number, shape, size, etc. of each cell and user terminal 20 are not limited to the configuration shown in the figure. Hereinafter, when base stations 11 and 12 are not to be distinguished, they will be collectively referred to as base station 10.

The wireless communication system 1 may also utilize multi-input multi-output (MIMO). For example, one cell may be formed by one antenna/base station 10, or by multiple antennas/base stations 10. One [virtual] cell (which may be called, for example, a supercell) may be made up of multiple [virtual] cells (which may be called, for example, subcells). A supercell may correspond to a cell with a fixed physical range, and a subcell may correspond to a cell with a quasi-static/dynamically changing physical range. In this case, the wireless communication system 1 may be called a cell-free system.

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

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)). Macrocell C1 may be included in FR1, and small cell C2 may be included in FR2. For example, FR1 may be a frequency band below 6 GHz (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 correspond to a higher frequency band than FR2.

Furthermore, the user terminal 20 may communicate using at least one of time division duplex (TDD) and frequency division duplex (FDD) in each CC.

Multiple base stations 10 may be connected by wire (e.g., optical fiber compliant with the Common Public Radio Interface (CPRI), X2/Xn interface, etc.) or wirelessly (e.g., NR communication). For example, if NR communication is used as a backhaul between base stations 11 and 12, base station 11, which corresponds to the upper station, may be called an Integrated Access Backhaul (IAB) donor, and base station 12, which corresponds to the relay station (relay), may be called an IAB node.

A 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), etc.

The core network 30 may include network functions (Network Functions (NF)) such as, for example, a User Plane Function (UPF), an Access and Mobility management Function (AMF), a Session Management Function (SMF), a Unified Data Management (UDM), an Application Function (AF), a Data Network (DN), a Location Management Function (LMF), and Operation, Administration and Maintenance (Management) (OAM). Note that multiple functions may be provided by a single network node. Communication with an external network (e.g., the Internet) may also be performed via the DN.

The user terminal 20 may be a terminal that supports at least one of the communication methods such as LTE, LTE-A, and 5G.

In the wireless communication system 1, a wireless access method based on Orthogonal Frequency Division Multiplexing (OFDM) may be used. For example, in at least one of the downlink (DL) and uplink (UL), 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), etc. may be used.

The radio access method may also be called a waveform. Note that in the wireless communication system 1, other radio access methods (e.g., other single-carrier transmission methods, other multi-carrier transmission methods) may be used as the UL and DL radio access methods.

In the wireless communication system 1, the downlink channel may be 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)), or the like.

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.

User data, upper layer control information, System Information Block (SIB), etc. are transmitted via PDSCH. User data, upper layer control information, etc. may also be transmitted via PUSCH. Furthermore, Master Information Block (MIB) may also be transmitted via PBCH.

Lower layer control information may be transmitted via 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 PUSCH.

Note that the DCI that schedules the PDSCH may be referred to as a DL assignment or DL DCI, and the DCI that schedules the PUSCH may be referred to as a UL grant or UL DCI. Note that the PDSCH may be interpreted as DL data, and the PUSCH may be interpreted as UL data.

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

One search space may correspond to PDCCH candidates corresponding to one or more aggregation levels. One or more search spaces may be referred to as a search space set. Note that in this disclosure, "search space," "search space set," "search space setting," "search space set setting," "CORESET," "CORESET setting," etc. may be read interchangeably.

The PUCCH may transmit uplink control information (UCI) including at least one of channel state information (CSI), delivery confirmation 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.

Note that in this disclosure, downlink, uplink, etc. may be expressed without adding the word "link." Also, various channels may be expressed without adding "Physical" to the beginning.

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, as the DL-RS, 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.

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 an SS (PSS, SSS) and a PBCH (and a DMRS for the PBCH) may be referred to as an SS/PBCH block, an SS block (SSB), etc. Note that SS, SSB, etc. may also be referred to as a reference signal.

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). DMRS may also be called a user equipment-specific reference signal (UE-specific Reference Signal).

(base station)
9 is a diagram illustrating 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.

Note that this example mainly shows the functional blocks that characterize the present embodiment, 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.

The control unit 110 controls the entire base station 10. The control unit 110 can be composed of a controller, a control circuit, etc., as described based on common understanding in the technical field to which this disclosure pertains.

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

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 composed of 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 to which this disclosure relates.

The transceiver unit 120 may be configured as an integrated transceiver unit, or may be composed of a transmitter unit and a receiver unit. The transmitter unit may be composed of a transmission processing unit 1211 and an RF unit 122. The receiver unit may be composed of a reception processing unit 1212, an RF unit 122, and a measurement unit 123.

The transmitting and receiving antenna 130 can be composed of an antenna described based on common understanding in the technical field to which this disclosure pertains, such as an array antenna.

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

The transceiver unit 120 may form at least one of the transmit beam and the receive beam using digital beamforming (e.g., precoding), analog beamforming (e.g., phase rotation), etc.

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.

The transmitter/receiver unit 120 (transmission processing unit 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.

The transceiver unit 120 (RF unit 122) may perform modulation, filtering, amplification, etc. on the baseband signal to a radio frequency band, and transmit the radio frequency band signal via the transceiver antenna 130.

On the other hand, the transceiver unit 120 (RF unit 122) may perform amplification, filtering, demodulation to a baseband signal, etc. on the radio frequency band signal received by the transceiver antenna 130.

The transceiver unit 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.

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.

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

Note that the transmitter and receiver of the base station 10 in this disclosure may be configured by at least one of the transmitter/receiver 120, the transmitter/receiver antenna 130, and the transmission path interface 140.

The base station 10 may be separated into three elements: a radio unit (RU), a distributed unit (DU), and a central unit (CU). For example, the RU may perform RF processing (digital beamforming, digital-to-analog conversion, analog beamforming, etc.) and lower-level physical layer functions (precoding, IFFT, FFT, etc.). The DU may perform higher-level physical layer functions (encoding to resource element mapping, etc.), MAC layer functions, and RLC layer functions. The CU may perform PDCP layer, Service Data Adaptation Protocol (SDAP) layer, and RRC layer functions.

In the present disclosure, the base station 10 may include a single device that implements all of the functions of the RU, DU, and CU, or may include multiple devices that each implement some of the functions of the RU, DU, and CU and are connected to each other. In the present disclosure, the base station 10 may be interchangeably referred to as the RU/DU/CU.

The transceiver unit 120 may also transmit configuration information for a Sounding Reference Signal (SRS) with a specific purpose set for use in uplink (UL) beam management to an uplink (UL) receiving point.

The control unit 110 may assume that SRS transmission to the UL reception point is controlled based on the setting information. If the base station 10 is an UL reception point, the transceiver unit 120 may receive the SRS.

The control unit 110 may assume that the UL beam for the UL reception point is determined based on a specified rule or a transmitted instruction. If the base station 10 is the UL reception point, the transceiver unit 120 may receive an UL signal using that UL beam.

(user terminal)
10 is a diagram showing an example of the configuration of a user terminal according to an 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.

Note that this example mainly shows the functional blocks that characterize the present embodiment, and the user terminal 20 may also have other functional blocks necessary for wireless communication. Some of the processing of each unit described below may be omitted.

The control unit 210 controls the entire user terminal 20. The control unit 210 can be composed of a controller, control circuit, etc., as described based on common understanding in the technical field to which this disclosure pertains.

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

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 composed of 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 this disclosure.

The transceiver unit 220 may be configured as an integrated transceiver unit, or may be composed of a transmitter unit and a receiver unit. The transmitter unit may be composed of a transmission processing unit 2211 and an RF unit 222. The receiver unit may be composed of a reception processing unit 2212, an RF unit 222, and a measurement unit 223.

The transmitting and receiving antenna 230 can be configured as an antenna described based on common understanding in the technical field to which this disclosure pertains, such as an array antenna.

The transceiver unit 220 may receive the above-mentioned downlink channel, synchronization signal, downlink reference signal, etc. The transceiver unit 220 may also transmit the above-mentioned uplink channel, uplink reference signal, etc.

The transceiver unit 220 may form at least one of the transmit beam and the receive beam using digital beamforming (e.g., precoding), analog beamforming (e.g., phase rotation), etc.

The transceiver unit 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.

The transceiver unit 220 (transmission processing unit 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.

Whether or not to apply DFT processing may be based on the settings for transform precoding. If 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; if not, it may not be necessary to perform DFT processing as the transmission processing.

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

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

The transceiver unit 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.

The transceiver unit 220 (measurement unit 223) may perform measurements on the received signal. For example, the measurement unit 223 may perform RRM measurements, CSI measurements, 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.

The measurement unit 223 may derive channel measurements for CSI calculation based on channel measurement resources. The channel measurement resources may be, for example, non-zero power (NZP) CSI-RS resources. The measurement unit 223 may also derive interference measurements for CSI calculation based on interference measurement resources. The interference measurement resources may be at least one of NZP CSI-RS resources for interference measurement, CSI-Interference Measurement (IM) resources, etc. CSI-IM may also be referred to as CSI-Interference Management (IM) or may be interchangeably read as Zero Power (ZP) CSI-RS. In this disclosure, CSI-RS, NZP CSI-RS, ZP CSI-RS, CSI-IM, CSI-SSB, etc. may be interchangeable.

Note that the transmitter and receiver of the user terminal 20 in this disclosure may be configured by at least one of the transmitter/receiver 220 and the transmitter/receiver antenna 230.

The transceiver unit 220 may also receive configuration information for a Sounding Reference Signal (SRS) with a specific purpose set for use in uplink (UL) beam management to an uplink (UL) receiving point.

The control unit 210 may control SRS transmission to the UL reception point based on the setting information.

The specific application may be an application other than beam management, codebook, non-codebook, and antenna switching.

The control unit 210 may use codebook SRS transmission for UL beam management for the UL reception point.

The control unit 210 may use non-codebook SRS transmission for UL beam management for the UL reception point.

The control unit 210 may determine the UL beam for the UL reception point based on specified rules or transmitted instructions.

The control unit 210 may determine, as the UL beam for the UL reception point, a beam different from the beam for the macro TRP, a beam directed in a specific direction, or a beam directed in the opposite direction to the beam for the macro TRP.

The transceiver unit 220 may receive a setting indicating whether UL beam management for the UL reception point is on or off.

The control unit 210 may switch the UL beam management on and off based on the setting indicating the switch.

The control unit 210 may switch UL beam management for the UL reception point on and off based on the reception result of the reference signal.

(Hardware configuration)
The block diagrams used to explain the above embodiments show functional blocks. These functional blocks (components) are realized by any combination of hardware and/or 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 (e.g., wired, wireless, etc.) and these multiple devices. The functional block may also be realized by combining software with the single device or multiple devices.

Here, 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 functions may be called a transmitting unit, transmitter, etc. As mentioned above, there are no particular limitations on how these functions are implemented.

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

In this disclosure, terms such as apparatus, circuit, device, section, and unit may be used interchangeably. The hardware configuration of the base station 10 and user terminal 20 may be configured to include one or more of the devices shown in the figures, or may be configured to exclude some of the devices.

For example, although only one processor 1001 is shown, there may be multiple processors. Furthermore, processing may be performed by a single processor, or processing may be performed by two or more processors simultaneously, sequentially, or using other techniques. Furthermore, the processor 1001 may be implemented by one or more chips.

The functions of the base station 10 and the user terminal 20 are realized, for example, by loading specific software (programs) onto hardware such as the processor 1001 and memory 1002, causing the processor 1001 to perform calculations, control communications via the communication device 1004, and control at least one of reading and writing data from and to the memory 1002 and storage 1003.

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) that includes an interface with peripheral devices, a control unit, an arithmetic unit, registers, etc. For example, at least a portion of the above-mentioned control unit 110 (210), transceiver unit 120 (220), etc. may be realized by the processor 1001.

In addition, the processor 1001 reads programs (program code), software modules, data, etc. from at least one of the storage 1003 and the communication device 1004 into the memory 1002, and 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 implemented by a control program stored in the memory 1002 and running on the processor 1001, and similar implementations may be used for other functional blocks.

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

Storage 1003 is a computer-readable recording medium and may be composed of at least one of a flexible disk, a floppy disk, a magneto-optical disk (e.g., a compact disc (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, a stick, a key drive), a magnetic stripe, a database, a server, or other suitable storage medium. Storage 1003 may also be referred to as an auxiliary storage device.

The communication device 1004 is hardware (transmitting/receiving device) for communicating between computers via at least one of a wired network and a wireless network, and is also referred to as a network device, network controller, network card, or communication module. The communication device 1004 may be configured to include high-frequency switches, duplexers, filters, frequency synthesizers, etc. to implement at least one of frequency division duplex (FDD) and time division duplex (TDD). For example, the above-mentioned transmitter/receiver unit 120 (220), transmitter/receiver antenna 130 (230), etc. may be implemented by the communication device 1004. The transmitter/receiver unit 120 (220) may be implemented as a transmitter unit 120a (220a) and a receiver unit 120b (220b) that are physically or logically separated.

The input device 1005 is an input device (e.g., a keyboard, mouse, microphone, switch, button, sensor, etc.) that accepts input from the outside. The output device 1006 is an output device (e.g., a display, speaker, Light Emitting Diode (LED) lamp, etc.) that outputs to the outside. Note that the input device 1005 and the output device 1006 may be integrated into one device (e.g., a touch panel).

Furthermore, each device, such as the processor 1001 and 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.

Furthermore, the base station 10 and 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 this hardware. For example, the processor 1001 may be implemented using at least one of these pieces of hardware.

In addition, devices included in the core network 30 (e.g., network nodes that provide NF) may also be realized using the above-mentioned functional block/hardware configuration.

(Modification)
Note that terms described 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.

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.

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

A slot may consist of one or more symbols in the time domain (such as Orthogonal Frequency Division Multiplexing (OFDM) symbols or Single Carrier Frequency Division Multiple Access (SC-FDMA) symbols). A slot may also be a time unit based on numerology.

A slot may include multiple minislots. Each minislot may consist of one or more 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.

Radio frame, subframe, slot, minislot, and symbol all represent time units for transmitting signals. Radio frame, subframe, slot, minislot, and symbol may each be referred to by a different name. Note that the time units used in this disclosure, such as frame, subframe, slot, minislot, and symbol, may be interchangeable.

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. In other words, at least one of a subframe and a TTI may be a subframe (1 ms) as in existing LTE, or may be a period shorter than 1 ms (e.g., 1-13 symbols), or may be a period longer than 1 ms. Note that the unit representing a TTI may be called a slot, minislot, etc. instead of a subframe.

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 the 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.

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

Note that 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 smallest time unit for scheduling. Furthermore, the number of slots (minislots) that make up the smallest time unit for scheduling may be controlled.

A TTI with 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 TTI (partial or fractional TTI), shortened subframe, short subframe, minislot, subslot, slot, etc.

Note that a long TTI (e.g., a normal TTI, 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 of 1 ms or more but less than the TTI length of a long TTI.

A resource block (RB) is a resource allocation unit in the time domain and 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, and may be, for example, 12. The number of subcarriers included in an RB may also be determined based on numerology.

Furthermore, an RB may include one or more symbols in the time domain and may be one slot, one minislot, one subframe, or one TTI in length. One TTI, one subframe, etc. may each be composed of one or more resource blocks.

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

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.

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

BWPs may include UL BWPs (BWPs for UL) and DL BWPs (BWPs for DL). One or more BWPs may be configured for a UE within one carrier.

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 "cell," "carrier," etc. in this disclosure may be read as "BWP."

Note that the structures of the radio frames, subframes, slots, minislots, and symbols described above 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, as well as the number of symbols in a TTI, symbol length, and cyclic prefix (CP) length can be changed in various ways.

Furthermore, the information, parameters, etc. described in this disclosure may be expressed using absolute values, relative values from a predetermined value, or other corresponding information. For example, radio resources may be indicated by a predetermined index.

The names used for parameters and the like in this disclosure are not limiting in any way. Furthermore, the mathematical formulas 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 limiting in any way.

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.

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.

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 to. Output information, signals, etc. may be deleted. Input information, signals, etc. may be sent to another device.

With regard to any information (e.g., variables, constants, parameters) described in this disclosure, even if not specifically stated in the above embodiments, any first device (e.g., UE/base station) may notify any second device (e.g., base station/UE) of information indicating/identifying (or relating to) the value of that information.

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

Note that physical layer signaling may also be referred to as Layer 1/Layer 2 (L1/L2) control information (L1/L2 control signal), L1 control information (L1 control signal), etc. Furthermore, RRC signaling may also be referred to as RRC messages, such as RRC Connection Setup messages or RRC Connection Reconfiguration messages. Furthermore, MAC signaling may also be notified using, for example, MAC Control Elements (CEs).

Furthermore, notification of specified information (e.g., notification that "X is true") is not limited to explicit notification, but may also be done implicitly (e.g., by not notifying the specified information or by notifying other information).

The determination may be made based on a value represented by a single bit (0 or 1), a Boolean value represented as true or false, or a comparison of numerical values (for example, a comparison with a predetermined value).

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.

In addition, software, instructions, information, etc. may be transmitted and received via a transmission medium. For example, if software is transmitted from a website, server, or other remote source using wired technology (such as coaxial cable, fiber optic cable, twisted pair, or Digital Subscriber Line (DSL)) and/or wireless technology (such as infrared or microwave), then the wired and/or wireless technology is included within the definition of transmission medium.

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

In this 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," "layer," "number of layers," "rank," "resource," "resource set," "beam," "beam width," "beam angle," "antenna," "antenna element," "panel," "UE panel," "transmitting entity," "receiving entity," etc. may be used interchangeably.

In the present disclosure, the term "antenna port" may be interchangeably read as an antenna port for any signal/channel (e.g., a demodulation reference signal (DMRS) port). In the present disclosure, the term "resource" may be interchangeably read as a resource for any signal/channel (e.g., a reference signal resource, an SRS resource, etc.). The resource may include time/frequency/code/space/power resources. The spatial domain transmit filter may include at least one of a spatial domain transmission filter and a spatial domain reception filter.

The above groups may include, for example, at least one of a spatial relationship group, a Code Division Multiplexing (CDM) group, a Reference Signal (RS) group, a Control Resource Set (CORESET) group, a PUCCH group, an antenna port group (e.g., a DMRS port group), a layer group, a resource group, a beam group, an antenna group, a panel group, etc.

Furthermore, in this disclosure, beam, SRS Resource Indicator (SRI), CORESET, CORESET pool, PDSCH, PUSCH, codeword (CW), transport block (TB), RS, etc. may be read as interchangeable terms.

Furthermore, in this disclosure, terms such as TCI state, downlink TCI state (DL TCI state), uplink TCI state (UL TCI state), unified TCI state, common TCI state, and joint TCI state may be interpreted interchangeably.

Furthermore, in this disclosure, terms such as "QCL," "QCL assumptions," "QCL relationships," "QCL type information," "QCL properties," "specific QCL type (e.g., Type A, Type D) properties," and "specific QCL types (e.g., Type A, Type D)" may be read interchangeably.

In this disclosure, terms such as index, identifier (ID), indicator, indication, and resource ID may be interchangeable. In this disclosure, terms such as sequence, list, set, group, cluster, and subset may be interchangeable.

Furthermore, the spatial relationship information identifier (ID) (TCI state ID) and spatial relationship information (TCI state) may be interchangeable. "Spatial relationship information (TCI state)" may be interchangeable as "set of spatial relationship information (TCI state)", "one or more pieces of spatial relationship information", etc. TCI state and TCI may be interchangeable. Spatial relationship information and spatial relationship may be interchangeable.

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," and "Component Carrier" may be used interchangeably. Base stations may also be referred to by terms such as macrocell, small cell, femtocell, and picocell.

A base station can accommodate one or more (e.g., three) cells. When a base station accommodates multiple cells, the entire coverage area of the base station can be divided into multiple smaller areas, and each smaller area can also be provided with communication services by a base station subsystem (e.g., a small indoor base station (Remote Radio Head (RRH))). The terms "cell" or "sector" refer to part or all of the coverage area of at least one of the base station and base station subsystems that provide communication services within this coverage area.

In this disclosure, a base station transmitting information to a terminal may be interpreted as the base station instructing the terminal to control/operate based on that information.

In this disclosure, terms such as "Mobile Station (MS)," "user terminal," "User Equipment (UE)," and "terminal" may be used interchangeably.

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.

At least one of the base station and the mobile station may be referred to as a transmitting device, a receiving device, a wireless communication device, etc. In addition, 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.

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

The moving object may be a vehicle (e.g., a car, an airplane, etc.), an unmanned moving object (e.g., a drone, a self-driving car, 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.

FIG. 12 is a diagram showing an example of a vehicle according to one embodiment. The 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, an axle 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.

The drive unit 41 is composed of, for example, at least one of an engine, a motor, or a hybrid of an engine and a motor. 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.

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).

Signals from the various sensors 50-58 include a current signal from a current sensor 50 that senses the motor current, a rotation speed signal for the front wheels 46/rear wheels 47 obtained by a rotation speed sensor 51, an air pressure signal for 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 for the accelerator pedal 43 obtained by an accelerator pedal sensor 55, a depression amount signal for the brake pedal 44 obtained by a brake pedal sensor 56, an operation signal for 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.

The information service unit 59 is composed of various devices, such as a car navigation system, audio system, speakers, displays, televisions, and radios, that provide (output) various information such as driving information, traffic information, and entertainment information, as well as one or more ECUs that control these devices. The information service unit 59 uses information obtained from external devices via the communication module 60, etc., to provide various information/services (e.g., multimedia information/multimedia services) to the occupants of the vehicle 40.

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.

The driving assistance system unit 64 is composed of various devices that provide functions to prevent accidents and reduce 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 Unit (IMU) and Inertial Navigation System (INS)), 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 or autonomous driving functions.

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 between 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, all of which are provided on the vehicle 40.

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 external devices. For example, it sends and receives various information to and from external devices 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 base station 10 or user terminal 20 described above. The communication module 60 may also be, for example, at least one of the base station 10 and user terminal 20 described above (or may function as at least one of the base station 10 and user terminal 20).

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

The communications module 60 receives various information (traffic information, traffic signal information, vehicle-to-vehicle information, etc.) transmitted from external devices and displays it on the information service unit 59 installed 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 communications module 60 (or data/information decoded from the PDSCH)).

Furthermore, the communication module 60 stores various information received from external devices in memory 62 that can be used by the microprocessor 61. Based on the information stored in 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 other components provided on the vehicle 40.

Furthermore, the 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 possessed by the base station 10 described above. Furthermore, terms such as "uplink" and "downlink" may be read as terms corresponding to communication between terminals (for example, "sidelink"). For example, terms such as uplink channel and downlink channel may be read as sidelink channel.

Similarly, the term "user terminal" in this disclosure may be interpreted as "base station." In this case, the base station 10 may be configured to have the functions possessed by the user terminal 20 described above.

In this disclosure, operations described as being performed by a base station may in some cases also be performed by its upper node. In a network including one or more network nodes having base stations, it is clear that various operations performed for communication with terminals 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) or a Serving-Gateway (S-GW)), or a combination thereof.

Each aspect/embodiment described in this disclosure may be used alone, in combination, or switched between depending on the implementation. Furthermore, the processing procedures, sequences, flowcharts, etc. of each aspect/embodiment described in this disclosure may be rearranged as long as they are consistent. For example, the methods described in this disclosure present various step elements in an exemplary order, and are not limited to the specific order presented.

Each aspect/embodiment described in this disclosure may be applied to any of the following mobile communication systems: 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 The present invention may be applied to systems that use 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 802.20, Ultra-WideBand (UWB), Bluetooth (registered trademark), or other appropriate wireless communication methods, as well as next-generation systems that are extended, modified, created, or defined based on these. It may also be applied to a combination of multiple systems (for example, a combination of LTE or LTE-A with 5G).

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."

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.

As used in this disclosure, the term "determining" 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., searching in a table, database, or other data structure), ascertaining, etc.

Furthermore, "determination" 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.

Furthermore, "judgment (decision)" may be considered to mean "judging (deciding)" resolving, selecting, choosing, establishing, comparing, etc. In other words, "judgment (decision)" may be considered to mean "judging (deciding)" some kind of action. In this disclosure, "judgment (decision)" may be read interchangeably with the above-mentioned actions.

Furthermore, in this disclosure, "determine/determining" may be interpreted interchangeably as "assume/assuming," "expect/expecting," "consider/considering," etc. Furthermore, in this disclosure, "does not expect to do..." may be interpreted interchangeably as "assumes not to do...."

In the present disclosure, "expect" may be interchangeably read as "be expected." For example, "expect(s)..." ("..." may be expressed, for example, as a that clause, a to-infinitive, etc.) may be interchangeably read as "be expected..." or "does... (if the above "..." is a to-infinitive, a verb with "to")." "does not expect..." may be interchangeably read as "be not expected..." or "does not... (if the above "..." is a to-infinitive, a verb with "to")." Furthermore, "An apparatus A is not expected..." may be interchangeably read as "apparatus B other than apparatus A does not expect..." from apparatus A (for example, if apparatus A is a UE, apparatus B may be a base station).

The term "maximum transmit power" used in this disclosure may refer to the maximum value of transmit power, the nominal UE maximum transmit power, or the rated UE maximum transmit power.

As used in this disclosure, the terms "connected," "coupled," or any variation thereof, mean 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."

For the purposes of 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.

In this disclosure, the term "A and B are different" may mean "A and B are different from each other." Note that this term may also mean "A and B are each different from C." Terms such as "separate" and "combined" may also be interpreted in the same way as "different."

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

In this disclosure, where articles are added by translation, such as a, an, and the in English, this disclosure may include the noun following these articles being plural.

In this disclosure, terms such as "less than or equal to," "less than," "greater than," "more than," "equal to," etc. may be read interchangeably. Furthermore, in this disclosure, terms meaning "good," "bad," "big," "small," "high," "low," "fast," "slow," "wide," "narrow," etc. may be read interchangeably, not limited to the positive, comparative, and superlative. Furthermore, in this disclosure, terms meaning "good," "bad," "big," "small," "high," "low," "fast," "slow," "wide," "narrow," etc. may be read interchangeably, not limited to the positive, comparative, and superlative, as expressions with the prefix "i-th" (i is any integer) (for example, "highest" may be read interchangeably as "i-th highest").

In this disclosure, the terms "of," "for," "regarding," "related to," "associated with," etc. may be read interchangeably.

In the present disclosure, expressions such as "when A, B," "if A, (then) B," "B upon A," "B in response to A," "B based on A," "B during/while A," "B before A," "B at (the same time as)/on A," "B after A," "B since A," and "B until A" may be interchangeable. Note that A and B may be replaced with other appropriate expressions, such as nouns, gerunds, and regular sentences, depending on the context. The time difference between A and B may be nearly zero (immediately after or immediately before). A time offset may also be applied to the time at which A occurs. For example, "A" may be interpreted interchangeably as "before/after the time offset at which A occurs." The time offset (e.g., one or more symbols/slots) may be predefined or may be determined by the UE based on signaled information.

In the present disclosure, terms such as timing, time, duration, time instance, any time unit (e.g., slot, subslot, symbol, subframe), period, occasion, and resource may be interpreted interchangeably.

The invention according to the present disclosure has been described in detail above, but it will be clear to those skilled in the art that the invention according to the present disclosure is not limited to the embodiments described herein. The description of the present disclosure is for illustrative purposes only and does not pose any limitations on the invention according to the present disclosure.

Claims (6)

A receiving unit that receives setting information of a Sounding Reference Signal (SRS) having a specific purpose set for use in UL beam management to an uplink (UL) receiving point;
a control unit that determines an UL beam for the UL reception point based on a specified rule or a transmitted instruction;
A terminal having: The terminal of claim 1 , wherein the control unit determines a beam different from a beam for a macro TRP, a beam directed in a specific direction, or a beam directed in the opposite direction to the beam for the macro TRP as the UL beam for the UL reception point. The receiving unit receives a setting indicating switching on or off of UL beam management for the UL reception point;
The terminal according to claim 1 , wherein the control unit switches the UL beam management on and off based on a setting indicating the switching. The terminal according to claim 1 , wherein the control unit switches on and off UL beam management for the UL reception point based on a reception result of a reference signal. Receiving configuration information of a Sounding Reference Signal (SRS) having a specific purpose configured for use in uplink (UL) beam management to an uplink (UL) receiving point;
determining an UL beam for the UL reception point based on specified rules or transmitted instructions;
A wireless communication method for a terminal having the above configuration. A transmitter that transmits setting information of a Sounding Reference Signal (SRS) having a specific purpose set for use in UL beam management to an uplink (UL) receiving point;
a control unit that determines an UL beam for the UL reception point based on a specified rule or a transmitted instruction;
A base station having