Terminal, base station, and communication method

Abstract

The present invention addresses the problem of appropriately reporting interference between base stations. This terminal comprises: a control circuit that determines, on the basis of information set in a time domain resource allocation table, the setting of a second time resource for which uplink transmission is not performed with respect to a first time resource to which a plurality of pieces of uplink data scheduled by one piece of downlink control information are allocated; and a transmission circuit that transmits the plurality of pieces of uplink data on the basis of the second time resource.

Description

Terminals, base stations, and communication methods

[0001] This disclosure relates to terminals, base stations, and communication methods.

[0002] The 3rd Generation Partnership Project (3GPP) has completed the specification of the physical layer for Release 17 NR (New Radio access technology) as an enhancement to the functionality of 5th Generation mobile communication systems (5G). NR supports enhanced Mobile Broadband (eMBB) and Ultra Reliable and Low Latency Communication (URLLC) to meet requirements such as high speed and large capacity (see, for example, Non-Patent Documents 1-6).

[0003] 3GPP TS 38.211 V18.5.0, "Physical channels and modulation (Release 18)", Jan. 20253GPP TS 38.212 V18.5.0, "Multiplexing and channel coding (Release 18)", Jan. 20253GPP TS 38.213 V18.5.0, "Physical layer procedures for control (Release 18)", Jan. 20253GPP TS 38.214 V18.5.0, "Physical layer procedures for data (Release 18)", Jan. 20253GPP TS 38.215 V18.4.0, "Physical layer measurements (Release 18)", Jan. 20253GPP TS 38.331 V18.4.0, "Radio Resource Control (RRC) protocol specification (Release 18)", Dec. 2024

[0004] However, there is room for consideration regarding the method of reporting interference between base stations.

[0005] Non-limiting embodiments of the present disclosure contribute to providing a terminal, a base station, and a communication method that can appropriately report interference between base stations.

[0006] A terminal according to an embodiment of the present disclosure includes a control circuit that determines a setting of a second time resource in which uplink transmission is not performed for a first time resource to which a plurality of uplink data scheduled by one downlink control information is allocated, based on information set in a time domain resource allocation table, and a transmission circuit that transmits the plurality of uplink data based on the second time resource.

[0007] These general or specific aspects may be implemented in a system, an apparatus, a method, an integrated circuit, a computer program, or a recording medium, or may be implemented in any combination of a system, an apparatus, a method, an integrated circuit, a computer program, and a recording medium.

[0008] According to an embodiment of the present disclosure, interference between base stations can be appropriately reported.

[0009] Further advantages and effects in an embodiment of the present disclosure will be clarified from the specification and the drawings. Such advantages and / or effects are provided by some embodiments and the features described in the specification and the drawings, respectively, but not all of them are necessarily provided in order to obtain one or more of the same features.

[0010] Figures illustrating subband non-overlapping full duplex (SBFD) operation, Dynamic / flexible time division duplex (TDD) operation, Cross-link interference (CLI) between base stations in SBFD operation, Muting resource configuration example in inter-base station CLI measurement, Uplink (UL) resource muting allocation example, Multi-scheduling Physical Uplink Shared Channel (PUSCH) notification example, UL resource muting notification example in Dynamic-Grant PUSCH (DG-PUSCH), UL resource muting notification example in PUSCH repetition Type A, PUSCH repetition Type Figure 3 shows an example of UL resource muting notification in B. Block diagram showing a partial configuration example of a base station. Block diagram showing a partial configuration example of a terminal. Block diagram showing an example of a base station configuration. Block diagram showing an example of a terminal configuration. Sequence diagram showing an example of base station and terminal operation. Figure 3 shows an example of UL resource muting configuration. Figure 4 shows an example of UL resource muting configuration. Figure 5 shows an example of UL resource muting configuration. Figure 6 shows an example of UL resource muting configuration. Figure 7 shows an example of UL resource muting configuration. Figure 8 shows an example of UL resource muting configuration. Figure 9 shows an example of UL resource muting configuration. Figure 10 shows an example of UL resource muting configuration. Figure 11 shows an example of UL resource muting configuration. Figure 12 shows an example of UL resource muting configuration. Figure 13 shows an exemplary architecture of a GPP NR system. Figure 14 shows an exemplary functional partitioning in G O-RAN.

[0011] Embodiments of this disclosure will be described in detail below with reference to the drawings.

[0012] [Regarding subband non-overlapping full duplex (SBFD) and Dynamic / flexible time division duplex (TDD)] Subband non-overlapping full duplex (SBFD) and Dynamic / flexible TDD are discussed in Release 18 and Release 19. Figure 1 shows an example of SBFD, and Figure 2 shows an example of Dynamic / flexible TDD.

[0013] Figure 1(a) shows an example of the operation of a base station (also called a gNB) and terminals (also called UE: User Equipment) (e.g., UE#1 and UE#2) within the same cell in SBFD operation. In SBFD operation, the base station performs SBFD operation, and the terminals perform Half duplex operation.

[0014] Figure 1(b) shows an example of SBFD operation. In Figure 1(b), the vertical axis represents frequency and the horizontal axis represents time. Also in Figure 1(b), "UL" represents uplink transmission and "DL" represents downlink transmission. Additionally, unused resources in each device (e.g., gNB, UE#1, and UE#2) are indicated by dotted lines.

[0015] As shown in Figure 1(b), in SBFD, the frequency resource (frequency band) is divided into multiple subbands (also called bands, RB sets, subbands, or sub-BWPs (Bandwidth parts)), and transmission in different directions is supported on a subband basis. As shown in Figure 1(b), the base station can transmit and receive simultaneously on both the uplink and downlink (e.g., SBFD operation), and the terminal can transmit and receive on either the uplink or downlink in a given time resource (e.g., Half-duplex operation). For example, in the example in Figure 1(b), in the same time resource (e.g., slot or symbol), UE#1 communicates with the base station on the uplink, and UE#2 communicates with the base station on the downlink.

[0016] Figure 2 shows an example of operation for different base stations (e.g., gNB1 and gNB2) and terminals (e.g., UE#1 and UE#2) in Dynamic / flexible TDD operation. In Dynamic / flexible TDD operation, base stations and terminals operate in half-duplex mode, and the transmission direction may differ between different base stations.

[0017] In the example in Figure 2, gNB1 sends a DL to UE#1 and gNB2 receives an UL from UE#2 within the same time resource (for example, the same time slot or symbol).

[0018] [Regarding Inter-Base Station Interference in Dynamic / Flexible TDD Operations] In Dynamic / Flexible TDD operations, various types of interference can occur. For example, cross-link interference (CLI) between terminals (UE-to-UE) and between base stations (gNB-to-gNB) can occur. Inter-terminal CLI and inter-base station CLI significantly degrade reception characteristics, so countermeasures are required.

[0019] In the following, regarding CLI between base stations, the base station that causes interference will be referred to as the "aggressor gNB," and the base station that is affected by the interference will be referred to as the "victim gNB."

[0020] For example, in Dynamic / flexible TDD operation, as shown in Figure 2, different base stations may communicate in different directions at the same time. In this case, the base station performing UL reception (gNB2 in Figure 2) may receive CLI from the base station performing DL transmission (gNB1 in Figure 2), which may degrade the UL reception characteristics of the UL receiving base station.

[0021] One way to avoid such interference is for the victim gNB to measure the CLI between base stations, share the measurement results between base stations (for example, between the aggressor gNB and the victim gNB), and avoid CLI between base stations through scheduling or other means.

[0022] [Inter-base station interference in SBFD operation] Even in SBFD operation, CLI can occur between base stations. For example, in SBFD operation, CLI leakage can occur from the DL subband of the aggressor gNB performing SBFD operation to the UL subband of the victim gNB. One way to avoid such CLI leakage between base stations is to have the victim gNB perform received signal processing that measures CLI leakage between base stations and estimates the interference covariance matrix, thereby avoiding or suppressing CLI leakage between base stations.

[0023] Figure 3 shows an example of base station-to-base station CLI (gNB-to-gNB CLI) in SBFD operation. In Figure 3, gNB1 and gNB2 perform SBFD operation, with gNB1 simultaneously receiving UL from terminal (UE#1) and transmitting DL to terminal (UE#2). Also in Figure 3, gNB2 simultaneously receives UL from terminal (UE#3) and transmits DL to terminal (UE#4). As shown in Figure 3, the base station-to-base station CLI is CLI leakage from gNB1, which transmits DL to UE#2, to gNB2, which receives UL from UE#3. At this time, the base station receiving UL (victim gNB; gNB2 in Figure 3) can receive CLI from the base station transmitting DL (aggressor gNB; gNB1 in Figure 3), which may degrade the UL reception characteristics at the base station receiving UL.

[0024] The victim gNB measures the CLI between base stations to reduce the CLI between base stations.

[0025] [Regarding CLI measurement methods between base stations] This section explains the method for measuring CLI between base stations.

[0026] For example, an aggressor gNB transmits a DL channel or signal for measurement, and a victim gNB receives the DL channel or signal and performs a CLI measurement. In this case, in order for the victim gNB to know (or receive) the configuration of the measurement DL channel or signal of the aggressor gNB, information about the measurement DL channel or signal may be shared between base stations in advance.

[0027] A victim gNB may receive UL channels or signals from terminals belonging to the victim gNB at the same time as receiving and measuring DL channels or signals for measurement. In this case, the measured CLI between base stations will include the UL channel or signal, and the victim gNB may not be able to accurately measure the CLI between base stations.

[0028] One way to improve the measurement accuracy of CLI between base stations is to apply "UL resource muting," which prevents UL communication. For example, a victim gNB sets up UL resource muting (e.g., a muting resource) for a terminal (e.g., a terminal belonging to the victim gNB) on the same resource as at least one of the time resource and frequency resource (hereinafter referred to as time / frequency resource) where the measurement DL channel or signal is located. The terminal belonging to the victim gNB does not transmit UL on the configured muting resource. This allows the victim gNB to measure CLI measurements between base stations using the measurement DL channel or signal, excluding the influence of UL, thereby improving the measurement accuracy of CLI between base stations.

[0029] Figure 4 shows an example of UL resource muting in use. In Figure 4, the aggressor gNB transmits measurement DL channels or signals at symbols #9 and #10. Also, as shown in Figure 4, terminals belonging to the victim gNB are assigned muting resources on the same resources as the measurement resources in the aggressor gNB. Terminals belonging to the victim gNB do not transmit uplink data (e.g., PUSCH: Physical Uplink Shared Channel) on the muting resources at symbols #9 and #10. Also, as shown in Figure 4, the victim gNB receives measurement DL channels or signals on the muting resources and measures the CLI between base stations. This allows the victim gNB to measure the CLI value between base stations, excluding the influence of UL signals from the UE, using the measurement DL channels or signals.

[0030] Figure 5 shows another use case for UL resource muting. In Figure 5, the victim gNB sets up UL resource muting for terminals belonging to the victim gNB. Terminals with UL resource muting set up do not transmit UL channels or signals (e.g., PUSCH) on the muted resource. The victim gNB uses the muted resource to measure CLI leakage from the aggressor gNB. This allows the victim gNB to measure CLI leakage from the aggressor gNB and estimate the interference covariance matrix without interference from terminals belonging to the victim gNB.

[0031] [Muting Resources] Transparent and non-transparent schemes are being considered for muting resources configured in UL resource muting.

[0032] In a transparent scheme, muting resources are implicitly configured by the base station's scheduling. For example, the base station schedules UL resources to terminals while avoiding muting resources. Therefore, terminals are not notified of information regarding muting resources.

[0033] In a non-transparent scheme, the base station notifies the terminal of information about muting resources (e.g., configuration). Based on the notified information, the terminal configures (or identifies) the muting resources and does not assign UL channels or signals to them.

[0034] Release 19 is considering supporting a non-transparent scheme for muting UL resources at the Resource Element (RE) level.

[0035] Figure 6 shows an example of UL resource muting allocation. As shown in Figure 6, the RE level UL muting resource pattern is assumed to be a comb-like arrangement (also called Comb-2) with every two subcarriers in the frequency domain, and a maximum of two symbols in the time domain. Also, as shown in Figure 6, it is assumed that the muting resource pattern does not overlap with the UL channel demodulation reference signal (DMRS) within the same symbol.

[0036] Note that the muting resource settings (e.g., arrangement in the frequency domain and time domain) are not limited to the example shown in Figure 6, and other settings may also be used.

[0037] Furthermore, it is assumed that a power boost of, for example, 3 dB (2x) will be applied to the RE within symbols where muting resources are set (symbols #1 and #9 in the example in Figure 6). It is assumed that the power boost will prevent the PUSCH transmit power from changing between symbols. For example, as shown in Figure 6, in the case of a comb-like arrangement with every two subcarriers in a muted symbol, half of the subcarriers are muted and their transmit power is set to 0. By power boosting the transmit power of the unmuted subcarriers (the remaining half) by 2x, the transmit power becomes the same as that of symbols without muting resources, and the PUSCH transmit power does not change between symbols.

[0038] Furthermore, if the time position setting method for UL resource muting is "Type 1 CG (Configured Grant) PUSCH," the symbol position for UL resource muting is set statically. Also, if the time position setting method for UL resource muting is "Type 2 CG PUSCH" or "DG (Dynamic Grant) PUSCH," the symbol position for UL resource muting is set statically, and it is possible to notify whether UL resource muting is enabled or disabled using the TDRA (Time Domain Resource Allocation) field in DCI (Downlink Control Information).

[0039] Also, in the case of PUSCH repetition Type A in SBFD Configuration 1, UL resource muting is applied to all PUSCHs that are repetitively transmitted. Also, in the case of PUSCH repetition Type B in SBFD Configuration 1, UL resource muting is applied to all PUSCHs that are repetitively transmitted in each slot. Here, in SBFD Configuration 1, UL transmission and DL reception are performed either in SBFD symbols or non-SBFD (non-SBFD) symbols. Also, in SBFD Configuration 2, UL transmission and DL reception can be performed across SBFD symbols and non-SBFD symbols.

[0040] Above, the muting resources have been described.

[0041] However, the notification method of UL resource muting in multi-scheduling PUSCH has not been fully studied.

[0042] In a non-limiting example of the present disclosure, the notification method of UL resource muting in multi-scheduling PUSCH will be described.

[0043] [Notification Method of Multi-Scheduling PUSCH] An example of the notification method of multi-scheduling PUSCH will be described.

[0044] The base station schedules a plurality of PUSCHs by a TDRA field of one DCI, for example, by setting time allocation parameters of each of the plurality of PUSCHs for one index number in the TDRA table. In the TDRA table, "PUSCH mapping type", "K2", "S", and "L", which are time allocation parameters of PUSCH, can be set.

[0045] The PUSCH mapping type can be selected from PUSCH mapping type A or PUSCH mapping type B, and the PUSCH mapping method differs depending on the mapping type. K2 is used to calculate the slot offset from the slot in which the DCI is received to the slot to which the PUSCH is allocated. S and L are parameters indicating the position of the first symbol of the PUSCH and the length of the allocated symbols of the PUSCH.

[0046] Also, for example, it is also possible to manage the time allocation parameters of a plurality of PUSCHs using a plurality of index numbers.

[0047] FIG. 7 shows an example of a notification method for multi-scheduled PUSCH. In the index number 1 (row index 1) of the TDRA table shown in FIG. 7, time allocation parameters (for example, K2, S, L) for the first PUSCH and time allocation parameters (for example, K2, S, L) for the second PUSCH are set. For example, the base station sets information in the TDRA table shown in FIG. 7 (for example, the association between the index number and the time allocation parameters) in the terminal. When the base station schedules a PUSCH and notifies the terminal of the index number '1' by, for example, the TDRA field of the DCI, as shown in the upper diagram of FIG. 7, the terminal allocates and transmits two PUSCHs.

[0048] [Notification Method for UL Resource Muting in Type 2 CG PUSCH and DG PUSCH]An example of the notification method for UL resource muting in Type 2 CG PUSCH and DG PUSCH will be described. The time allocation information for Type 2 CG PUSCH and DG PUSCH may be set by, for example, a TDRA table. The base station schedules the PUSCH by the TDRA field of the DCI.

[0049] Furthermore, information indicating whether UL resource muting is enabled or disabled may be set in the terminal by a TDRA table, for example, along with the time allocation parameters of the PUSCH. For example, as information indicating whether UL resource muting is enabled or disabled, a parameter for UL resource muting (e.g., "Muting symbol") may be defined in the TDRA table, and information indicating whether UL resource muting is enabled or disabled may be set. For example, a value of 0 for the Muting symbol may indicate enabled, and a value of 1 may indicate disabled (and vice versa). The base station dynamically notifies the terminal of the index number of the configured TDRA table by the TDRA field of the DCI. Based on the notified index number of the TDRA table, the terminal determines whether to enable or disable UL resource muting in the PUSCH notified by the base station, and decides whether or not to assign UL resource muting to the scheduled PUSCH.

[0050] Figure 8 shows an example of how UL resource muting is notified in DG PUSCH.

[0051] When the index number of the TDRA table shown in Figure 8 is '1', the PUSCH time allocation parameters (PUSCH mapping type, K2, S, L) and UL resource muting are enabled. When the index number is '2', the PUSCH time allocation parameters (PUSCH mapping type, K2, S, L) and UL resource muting are disabled.

[0052] For example, the base station sets the symbol locations for UL resource muting to symbol #1 (the second symbol in the slot) and symbol #6 (the seventh symbol in the slot), and notifies the terminal of index number '1' via the TDRA field of the DCI. In this case, as shown in the upper diagram of Figure 8, the terminal assigns UL resource muting to symbol #1 and symbol #6 within the scheduled PUSCH (symbols #0 to #9).

[0053] [Notification Method for UL Resource Muting in PUSCH repetition Type A] This section describes an example of how to notify users of UL resource muting in PUSCH repetition Type A.

[0054] In PUSCH repetition Type A, the time allocation parameters for PUSCH are set by the TDRA table. The number of PUSCH repetitions (also known as the repetition factor) is set by the base station.

[0055] Furthermore, information indicating whether UL resource muting is enabled or disabled may be set in the terminal by a TDRA table, for example, along with the time allocation parameters for PUSCH. The base station dynamically notifies the terminal of the index number of the set TDRA table by the TDRA field of the DCI. Based on the notified TDRA table index number, the terminal allocates time for PUSCH and repeatedly transmits the allocated PUSCH. In addition, since the terminal can determine whether to enable or disable UL resource muting based on the UL resource muting information in the TDRA table, it decides whether to assign UL resource muting to all PUSCH that are repeatedly transmitted based on that information.

[0056] Figure 9 shows an example of how UL resource muting is notified in PUSCH repetition Type A. When the index number of the TDRA table shown in Figure 9 is '1', the PUSCH time allocation parameters (PUSCH mapping type, K2, S, L) and UL resource muting are enabled. When the index number is '2', the PUSCH time allocation parameters (PUSCH mapping type, K2, S, L) and UL resource muting are disabled.

[0057] For example, the base station sets the number of repetitions of PUSCH to 4, sets the symbol positions of the UL resource muting to symbol #1 and symbol #6, and notifies the terminal of index number '1' via the TDRA field of the DCI. In this case, as shown in the upper diagram of Figure 9, the terminal assigns PUSCH to the symbols in the slots based on the time allocation parameter and transmits PUSCH four times (using four slots). At this time, the terminal assigns UL resource muting to symbols #1 and #6 (not shown) of all (four) PUSCH messages that are transmitted repeatedly.

[0058] [Notification Method for UL Resource Muting in PUSCH repetition Type B] This section describes an example of how to notify users of UL resource muting in PUSCH repetition Type B.

[0059] In PUSCH repetition Type B, the time allocation parameters for PUSCH are set by the TDRA table. The number of PUSCH repetitions is set by the base station.

[0060] Furthermore, information indicating whether UL resource muting is enabled or disabled may be set in the terminal by a TDRA table, for example, along with the time allocation parameters for PUSCH. The base station dynamically notifies the terminal of the index number of the set TDRA table by the TDRA field of the DCI. Based on the notified index number of the TDRA table, the terminal allocates time for PUSCH and repeatedly transmits the allocated PUSCH. The terminal can also determine whether to enable or disable UL resource muting based on the UL resource muting information in the TDRA table, and therefore decide whether to assign UL resource muting to all PUSCH that are repeatedly transmitted based on this information. In this case, if the symbol of the actual repetition PUSCH and the symbol of UL resource muting overlap, UL resource muting may be applied to the actual repetition PUSCH. In other words, UL resource muting may not be applied to the actual repetition PUSCH.

[0061] Figure 10 shows an example of how UL resource muting is notified in PUSCH repetition Type B. When the index number of the TDRA table shown in Figure 10 is '1', the PUSCH time allocation parameters (PUSCH mapping type, K2, S, L) and UL resource muting are enabled. When the index number is '2', the PUSCH time allocation parameters (PUSCH mapping type, K2, S, L) and UL resource muting are disabled.

[0062] For example, the base station sets the number of repetitions for PUSCH to 4, sets the symbol positions for UL resource muting to symbol #2 (the third symbol in the slot) and symbol #8 (the ninth symbol in the slot), and notifies the terminal of index number '1' via the TDRA field of DCI. In this case, as shown in the upper diagram of Figure 10, the terminal assigns PUSCH based on the time allocation parameter and transmits PUSCH four times. Furthermore, if the assigned symbols of the repeatedly transmitted PUSCH overlap with symbols #1 and #6 of UL resource muting, the terminal assigns UL resource muting to that PUSCH.

[0063] [Overview of the Communication System] A communication system according to one aspect of this disclosure may include, for example, a base station 100 (e.g., gNB) shown in Figures 11 and 13, and a terminal 200 (e.g., UE) shown in Figures 12 and 14. Multiple base stations 100 and terminals 200 may exist in the communication system.

[0064] Figure 11 is a block diagram showing a partial configuration example of a base station 100 according to one aspect of the present disclosure. In the base station 100 shown in Figure 11, the control unit (e.g., corresponding to a control circuit) determines, based on information set in a time-domain resource allocation table (TDRA table), the setting of a second time resource (e.g., a muting resource) that does not perform UL transmission for a first time resource to which a plurality of uplink data (e.g., PUSCH) scheduled by a single downlink control information (e.g., DCI) is allocated. The receiving unit (e.g., corresponding to a receiving circuit) receives the plurality of uplink data based on the second time resource.

[0065] Figure 12 is a block diagram showing a partial configuration example of a terminal 200 according to one aspect of the present disclosure. In the terminal 200 shown in Figure 12, the control unit (corresponding to, for example, a control circuit) determines, based on information set in a time-domain resource allocation table (TDRA table), the setting of a second time resource (e.g., a muting resource) that does not perform UL transmission for a first time resource to which a plurality of uplink data (e.g., PUSCH) scheduled by a single downlink control information (e.g., DCI) is allocated. The transmission unit (corresponding to, for example, a transmission circuit) transmits the plurality of uplink data based on the second time resource.

[0066] [Base Station Configuration] Figure 13 is a block diagram showing an example configuration of a base station 100 according to one aspect of the present disclosure. In Figure 13, the base station 100 includes a receiving unit 101, a demodulation / decoding unit 102, a muting resource setting unit 103, a scheduling unit 104, a control information holding unit 105, a data / control information generation unit 106, an encoding / modulation unit 107, and a transmission unit 108.

[0067] For example, at least one of the demodulation / decoding unit 102, muting resource setting unit 103, scheduling unit 104, control information holding unit 105, data / control information generation unit 106, and encoding / modulation unit 107 may be included in the control unit shown in Figure 11, and the receiving unit 101 may be included in the receiving unit shown in Figure 11.

[0068] The receiving unit 101 performs reception processing on the received signal received via the antenna, for example, such as down-conversion or A / D conversion, and outputs the processed received signal to the demodulation / decoding unit 102.

[0069] The demodulation / decoding unit 102 demodulates and decodes the received signal input from the receiving unit 101, for example, and outputs the decoding result to the scheduling unit 104.

[0070] The muting resource setting unit 103 sets the time allocation information for UL resource muting (for example, information indicating whether UL resource muting is enabled or disabled) in the TDRA table for UL based on control information such as time allocation information for UL (for example, the TDRA table) input from the control information holding unit 105. The muting resource setting unit 103 outputs the information of the TDRA table, including the time allocation information for UL resource muting, to the scheduling unit 104 or the control information holding unit 105.

[0071] The scheduling unit 104 may, for example, perform scheduling for the terminals 200. Based on, for example, the decoding result input from the demodulation / decoding unit 102, the TDRA table including UL resource muting time allocation information input from the muting resource setting unit 103, and the control information input from the control information holding unit 105, the scheduling unit 104 schedules the transmission and reception of each terminal 200 and instructs the data / control information generation unit 106 to generate at least one of the data and control information. The scheduling unit 104 also outputs the scheduling information to the control information holding unit 105.

[0072] The control information holding unit 105 holds control information such as the configuration of UL resource muting (e.g., time allocation information or frequency allocation information) and time allocation information for UL, which are input from the muting resource setting unit 103 and the scheduling unit 104. The control information holding unit 105 may output the held information to each component of the base station 100 (e.g., the muting resource setting unit 103 and the scheduling unit 104) as needed.

[0073] The data and control information generation unit 106 generates at least one of data and control information according to instructions from, for example, the scheduling unit 104, and outputs a signal containing the generated data or control information to the encoding and modulation unit 107. The generated data and control information may include, for example, at least one of upper-layer signaling information and downlink control information.

[0074] The encoding and modulation unit 107 encodes and modulates the signal input from, for example, the data and control information generation unit 106, and outputs the modulated signal to the transmission unit 108.

[0075] The transmitting unit 108 performs transmission processing such as D / A conversion, upconversion, or amplification on the signal input from the encoding / modulation unit 107, and transmits the resulting wireless signal from the antenna to the terminal 200.

[0076] [Terminal Configuration] Figure 14 is a block diagram showing an example configuration of a terminal 200 according to one aspect of the present disclosure. In Figure 14, the terminal 200 includes a receiving unit 201, a demodulation / decoding unit 202, a muting resource allocation unit 203, a transmission control unit 204, a control information holding unit 205, a data / control information generation unit 206, an encoding / modulation unit 207, and a transmission unit 208.

[0077] For example, at least one of the demodulation / decoding unit 202, muting resource allocation unit 203, transmission control unit 204, control information holding unit 205, data / control information generation unit 206, and encoding / modulation unit 207 may be included in the control unit shown in Figure 12, and the transmission unit 208 may be included in the transmission unit shown in Figure 12.

[0078] The receiving unit 201 performs reception processing on the received signal received via the antenna, for example, such as down-conversion or A / D conversion, and outputs the processed received signal to the demodulation / decoding unit 202.

[0079] The demodulation / decoding unit 202 demodulates and decodes the received signal input from the receiving unit 201, for example, and outputs the decoded result to the transmission control unit 204.

[0080] The muting resource allocation unit 203 outputs the muting resource allocation settings to the transmission control unit 204 based on control information, for example, that includes time allocation information for UL resource muting input from the control information holding unit 205 (for example, information indicating whether UL resource muting is enabled or disabled).

[0081] The transmission control unit 204 outputs signaling information included in the decoding result input from the demodulation / decoding unit 202 to the control information holding unit 205. The transmission control unit 204 may also issue a generation instruction to the data / control information generation unit 206 for at least one of data and control information based on, for example, the time allocation information for UL resource muting input from the muting resource allocation unit 203, the control information input from the control information holding unit 205, or the decoding result input from the demodulation / decoding unit 202 (for example, downlink control information).

[0082] The control information holding unit 205 holds control information, including, for example, control information input from the transmission control unit 204 (e.g., signaling information including muting resource configuration information or TDRA table), and outputs the held information to each component (e.g., muting resource allocation unit 203 and transmission control unit 204) as needed.

[0083] The data / control information generation unit 206 generates data or control information, for example, according to instructions from the transmission control unit 204. The data / control information generation unit 206 outputs a signal containing the generated data or control information to the encoding / modulation unit 207.

[0084] The encoding and modulation unit 207 encodes and modulates the signal input from, for example, the data and control information generation unit 206, and outputs the modulated transmission signal to the transmission unit 208.

[0085] The transmitting unit 208 performs transmission processing such as D / A conversion, upconversion, or amplification on the signal input from the encoding / modulation unit 207, and transmits the resulting radio signal from the antenna to the base station 100.

[0086] [Operation of Base Station 100 and Terminal 200] An example of operation of the base station 100 and terminal 200 having the above configuration will be described below.

[0087] Figure 15 is a sequence diagram showing an example of the operation of the base station 100 and the terminal 200.

[0088] In Figure 15, the base station 100 transmits settings (configuration) related to UL transmission (e.g., PUSCH transmission or PUCCH transmission) and UL resource muting to the terminal 200 (S101).

[0089] The base station 100 transmits scheduling information for PUSCH to the terminal 200 (S102).

[0090] The terminal 200 determines whether UL resource muting for PUSCH transmission is enabled based on the configuration from the base station 100 (S103).

[0091] If UL resource muting is enabled (S103: Yes), terminal 200 assigns UL resource muting to the PUSCH transmission (S104) and transmits the PUSCH (S105). On the other hand, if UL resource muting is disabled (S103: No), terminal 200 transmits the PUSCH without assigning UL resource muting (S105).

[0092] [Method for configuring UL resource muting in multi-scheduling PUSCH] Next, an example of a method for configuring UL resource muting in multi-scheduling PUSCH according to a non-limiting embodiment of the present disclosure will be described.

[0093] For example, we will describe the operation of setting and notifying UL resource muting for multi-scheduling PUSCH by the base station 100 (e.g., the muting resource setting unit 103), and the operation of assigning UL resource muting by the terminal 200 (e.g., the muting resource allocation unit 203).

[0094] <Configuration Method 1> In Configuration Method 1, information indicating whether a single UL resource muting is enabled or disabled (hereinafter also referred to as "UL muting information") is set in the TDRA table. For example, UL muting information indicating whether or not a muting resource is applied is set in common for multiple scheduled PUSCHs in the TDRA table.

[0095] For example, whether UL resource muting is enabled or disabled can be set with a single bit (e.g., 1 for Enabled, 0 for Disabled). This information applies commonly to all PUSCH entries in the TDRA table.

[0096] The base station 100 sets up a TDRA table containing information indicating whether a single UL resource muting is enabled or disabled, and time allocation parameters (e.g., K2, S, L) for each of the multiple PUSCHs, and sets up information about the TDRA table on the terminal 200.

[0097] Furthermore, the base station 100 uses the DCI's TDRA field to notify the terminal 200 of one of several TDRA parameters set in the TDRA table (for example, candidate combinations of time allocation parameters and UL muting information) (for example, information regarding the corresponding index number).

[0098] Terminal 200 assigns multiple PUSCHs using time allocation parameters for multiple PUSCHs set in the TDRA table, based on the notified index number of the TDRA table. At this time, terminal 200 decides whether or not to assign UL resource muting to all scheduled PUSCHs based on one UL muting information (e.g., Enabled or Disabled) set in the TDRA table.

[0099] Figure 16 shows an example of UL resource muting settings related to setting method 1.

[0100] In the TDRA table shown in Figure 16, index number '1' contains the time allocation parameters (e.g., K2, S, L) for the first and second PUSCH respectively, and one UL muting information indicating that UL resource muting is enabled for the two PUSCHs. Index number '2' contains the time allocation parameters (e.g., K2, S, L) for the first and second PUSCH respectively, and one UL muting information indicating that UL resource muting is disabled for the two PUSCHs.

[0101] For example, the base station 100 sets the TDRA table shown in Figure 16 on the terminal 200.

[0102] For example, if base station 100 notifies terminal 200 of index number '1' using the DCI's TDRA field, terminal 200 will send two PUSCHs assigning UL resource muting, as shown in the upper diagram of Figure 16.

[0103] In configuration method 1, two patterns (Enabled and Disabled) are set for the assignment of UL resource muting to one setting in the TDRA table of a multi-scheduling PUSCH (for example, one pattern (combination) of time allocation parameters for multiple PUSCHs). For example, in order to flexibly determine the assignment of UL resource muting according to the CLI status between base stations, it is expected that at least two patterns of setting, enabled and disabled for UL resource muting, will be used for one setting in a multi-scheduling PUSCH (setting of the same time allocation parameters).

[0104] In this way, by minimizing the number of candidates for UL resource muting settings, it is possible to minimize the number of bits (bit size) in the DCI's TDRA field by the base station 100, as no more than two index numbers are consumed for a single setting of the multi-scheduling PUSCH. The base station 100 may determine the number of bits in the TDRA field according to the number of indexes in the configured TDRA table.

[0105] <Configuration Method 2> In Configuration Method 2, information indicating whether a single UL resource muting is enabled or disabled (UL muting information) is individually set in the TDRA table for each TDRA parameter of a PUSCH. For example, UL muting information indicating whether or not a muting resource is applied is individually set in the TDRA table for each of the multiple PUSCHs that are scheduled.

[0106] For example, whether UL resource muting is enabled or disabled can be set with a single bit (e.g., 1 for Enabled, 0 for Disabled). This information is applied individually to the corresponding PUSCH among multiple PUSCHs set in the TDRA table.

[0107] The base station 100 sets up a TDRA table containing the TDRA parameters (e.g., K2, S, L) for each of the multiple PUSCHs, and UL muting information indicating whether UL resource muting is enabled or disabled for each PUSCH, and sets up information about the TDRA table on the terminal 200.

[0108] Furthermore, the base station 100 uses the DCI's TDRA field to notify the terminal 200 of one of the multiple TDRA parameters set in the TDRA table (for example, information regarding the corresponding index number).

[0109] Terminal 200 assigns multiple PUSCHs using time allocation parameters for multiple PUSCHs set in the TDRA table, based on the index number of the notified TDRA table. At this time, terminal 200 individually decides whether or not to assign UL resource muting to each scheduled PUSCH, based on one piece of UL muting information set for the TDRA parameter of each PUSCH.

[0110] Figure 17 shows an example of UL resource muting settings related to setting method 2.

[0111] In the TDRA table shown in Figure 17, index number '1' contains the time allocation parameters (e.g., K2, S, L) for the first and second PUSCH respectively, and UL muting information indicating that UL resource muting is enabled for the first and second PUSCH respectively. Index number '2' contains the time allocation parameters for the first and second PUSCH respectively, UL muting information indicating that UL resource muting is enabled for the first PUSCH, and UL muting information indicating that UL resource muting is disabled for the second PUSCH. Index number '3' contains the time allocation parameters for the first and second PUSCH respectively, UL muting information indicating that UL resource muting is disabled for the first PUSCH, and UL muting information indicating that UL resource muting is enabled for the second PUSCH. Furthermore, index number '4' is set to the time allocation parameters for the first and second PUSCH respectively, and UL muting information indicating that UL resource muting corresponding to the first and second PUSCH is disabled.

[0112] For example, the base station 100 sets the TDRA table shown in Figure 17 on the terminal 200.

[0113] For example, if base station 100 notifies terminal 200 of index number '2' using the TDRA field of DCI, terminal 200 will send two PUSCHs, assigning UL resource muting to the first PUSCH and not assigning UL resource muting to the second PUSCH, as shown in the upper diagram of Figure 17.

[0114] In configuration method 2, UL resource muting can be individually enabled or disabled for each PUSCH that is being multi-scheduled, thus improving the flexibility of UL resource muting allocation. For example, if there is a period (segment) in which there is no DL traffic in an adjacent cell, no CLI between base stations will occur in that segment. Therefore, allocating UL resource muting to a PUSCH allocated in that segment would result in wasted resources. In such cases, resource waste can be avoided by individually and flexibly configuring UL resource muting for multiple PUSCHs (e.g., multiple slots) as in configuration method 2.

[0115] <Configuration Method 3> In Configuration Method 3, a "slot pattern (UL muting pattern)" is defined that indicates the allocation pattern of UL resource muting to multiple slots (or multiple PUSCHs), and an index of the slot pattern is set in the TDRA table.

[0116] A slot pattern may be defined, for example, by a standard (spec), or it may be set on the terminal 200 by RRC signaling. A slot pattern may define patterns for assigning UL resource muting (e.g., Enabled or Disabled) to multiple slots (or multiple PUSCHs). For example, a single slot pattern may contain information indicating whether or not UL resource muting (e.g., muting resource) is applied to each of the multiple PUSCHs.

[0117] The base station 100 sets information regarding multiple slot patterns and information regarding a TDRA table in which any of the multiple slot patterns is set on the terminal 200.

[0118] Furthermore, the base station 100 uses the TDRA field of DCI to notify the base station of one of several TDRA parameters set in the TDRA table (for example, information regarding the corresponding index number). The base station 100 also determines whether or not UL resource muting is applied to each PUSCH based on the slot pattern set in the TDRA table.

[0119] Figures 18 and 19 show examples of UL resource muting settings related to setting method 3 (examples of settings for different slot patterns).

[0120] The TDRA tables shown in Figures 18 and 19 contain time allocation parameters for each of the two PUSCHs. Additionally, the two slot patterns (UL muting patterns) contain information indicating whether UL resource muting is enabled or disabled for the two PUSCHs (PUSCH#1 and PUSCH#2).

[0121] The slot patterns shown in Figure 18 can be configured with two combinations (two patterns). In Figure 18, in the first slot pattern (slot pattern 1), both PUSCH#1 and PUSCH#2 are set to Enabled, while in the second slot pattern (slot pattern 2), both PUSCH#1 and PUSCH#2 are set to Disabled. Note that the UL resource muting settings (enabled or disabled) for each of the multiple PUSCHs in a slot pattern are not limited to the example shown in Figure 18, and other combinations are also possible.

[0122] For example, in Figure 18, if base station 100 notifies terminal 200 of index number '2' (slot pattern 2) using the TDRA field of DCI, terminal 200 will not apply UL resource muting to the two PUSCHs, as shown in the upper part of Figure 18.

[0123] Furthermore, the slot patterns shown in Figure 19 have four possible combinations (four patterns). In Figure 19, in the first slot pattern (slot pattern 1), both PUSCH#1 and PUSCH#2 are set to Enabled; in the second slot pattern (slot pattern 2), PUSCH#1 is set to Enabled and PUSCH#2 is set to Disabled; in the third slot pattern (slot pattern 3), PUSCH#1 is set to Disabled and PUSCH#2 is set to Enabled; and in the fourth slot pattern (slot pattern 4), both PUSCH#1 and PUSCH#2 are set to Disabled.

[0124] For example, in Figure 19, if base station 100 notifies terminal 200 of index number '2' (slot pattern 2) using the TDRA field of DCI, terminal 200 applies UL resource muting to the first PUSCH but does not apply UL resource muting to the second PUSCH, as shown in the upper part of Figure 19.

[0125] Figure 20 shows another example of UL resource muting configuration (an example of slot pattern configuration) related to configuration method 3.

[0126] The slot patterns shown in Figure 20 can be configured with two combinations (two patterns). In Figure 20, in the first slot pattern (slot pattern 1), both PUSCH#1 and PUSCH#2 are set to Enabled, while in the second slot pattern (slot pattern 2), both PUSCH#1 and PUSCH#2 are set to Disabled. Note that the UL resource muting settings (enabled or disabled) for each of the multiple PUSCHs in a slot pattern are not limited to the example shown in Figure 20, and other combinations are also possible.

[0127] Furthermore, the TDRA table shown in Figure 20 has time allocation parameters (e.g., K2, S, L) set for each of the four PUSCHs, and one UL resource muting slot pattern is set for every two PUSCH time allocation parameters. For example, in the TDRA table shown in Figure 20, one slot pattern is set in common for the first and second PUSCHs, and one slot pattern is set in common for the third and fourth PUSCHs.

[0128] For example, if base station 100 notifies terminal 200 of '3' using the DCI's TDRA field, terminal 200 will not apply UL resource muting to the first and second pushes, but will apply UL resource muting to the third and fourth pushes, as shown in the upper diagram of Figure 20.

[0129] In configuration method 3, the allocation pattern for UL resource muting to multiple PUSCHs can be notified by setting the slot pattern for UL resource muting, thereby reducing the overhead of the TDRA field. In addition, the flexibility of UL resource muting allocation can be adjusted according to the setting of the UL resource muting slot pattern.

[0130] For example, if it can be determined in advance that the CLI between base stations will not fluctuate significantly between slots, the overhead of the TDRA field can be reduced by setting a slot pattern as shown in Figure 18 (for example, a pattern in which the same content is set for multiple slots). Alternatively, if it can be determined in advance that the CLI between base stations will fluctuate significantly between slots, it becomes possible to flexibly allocate UL resource muting in accordance with the fluctuations in the CLI between base stations by setting a slot pattern as shown in Figure 19 (for example, a pattern in which different content is set for each slot).

[0131] <Configuration Method 4> In Configuration Method 4, a mask parameter or a slot pattern for a single UL resource muting (for example, the slot pattern in Configuration Method 3) is defined.

[0132] The mask parameters and slot patterns may be defined, for example, by a standard (spec), or they may be set on the terminal 200 by RRC signaling.

[0133] For example, in the case of mask parameters, UL resource muting is enabled or disabled for multiple PUSCHs by a bitmap where each bit corresponds to a specific bit (e.g., 0 for disabled, 1 for enabled). For example, the standard may define that UL resource muting is enabled for the first slot among multiple slots to which multiple PUSCHs are assigned, and disabled for the other slots. For example, in the case of a single slot pattern, information can be set indicating whether UL resource muting is enabled or disabled for multiple PUSCHs.

[0134] Thus, in setting method 4, information indicating a single pattern (e.g., mask parameter or slot pattern) that shows whether or not a muting resource is applied to each of the multiple PUSCHs is set. The TDRA table also contains information indicating whether or not this single pattern is applied (e.g., UL muting pattern information).

[0135] The base station 100 sets information on the terminal 200 regarding the TDRA table in which UL muting pattern information indicating whether a mask parameter or a single slot pattern is valid or invalid (or whether it is applicable or not) is set.

[0136] Furthermore, the base station 100 uses the DCI's TDRA field to notify the terminal 200 of one of the multiple TDRA parameters set in the TDRA table (for example, information regarding the corresponding index number). In this case, if a setting to disable a mask parameter or a slot pattern is set in the TDRA parameter, the terminal 200 does not apply UL resource muting to all PUSCHs. On the other hand, if a setting to enable a mask parameter or a slot pattern is set in the TDRA parameter, the terminal 200 applies the UL resource muting pattern set in the terminal 200 or the UL resource muting pattern defined in the standard to all PUSCHs.

[0137] Furthermore, if no mask parameter or slot pattern is set on terminal 200, terminal 200 may apply the UL resource muting settings configured in the TDRA table to all PUSCH (for example, the same operation as setting method 1).

[0138] Figure 21 shows an example of UL resource muting settings related to setting method 4.

[0139] In Figure 21, one slot pattern is configured on terminal 200 in which UL resource muting is enabled for PUSCH#1, PUSCH#2, and PUSCH#4, and UL resource muting is disabled for PUSCH#3.

[0140] Furthermore, the TDRA table shown in Figure 21 contains time allocation parameters for each of the four PUSCHs, as well as UL muting pattern information indicating whether one slot pattern (UL resource muting) is enabled or disabled.

[0141] For example, if base station 100 notifies terminal 200 of '1' using the DCI's TDRA field, terminal 200 applies UL resource muting to the 1st, 2nd, and 4th pushes, as shown in the upper diagram of Figure 21, but does not apply UL resource muting to the 3rd push.

[0142] In configuration method 4, if the base station 100 can pre-identify slots to which it does not need to allocate UL resource muting by using a mask parameter or a single slot pattern, it is possible to flexibly allocate UL resource muting while suppressing an increase in overhead.

[0143] The above explains an example of how to configure UL resource muting in multi-scheduling PUSCH.

[0144] Thus, in this embodiment, the terminal 200 determines the setting of muting resources (e.g., whether or not to apply them) for the slot (time resource) to which a multi-scheduling PUSCH is assigned, based on the information set in the TDRA table (e.g., UL muting information or UL muting pattern information). As a result, the terminal 200 (e.g., victim UE) can set resource allocation for multiple PUSCHs and UL resource muting allocation with a single DCI. This allows the terminal 200 to appropriately set muting resources for multiple PUSCHs (e.g., multiple slots) and measure CLI between base stations, even when a multi-scheduling PUSCH is assigned. Therefore, according to this embodiment, the terminal 200 can appropriately report interference between base stations.

[0145] The embodiments of this disclosure have been described above.

[0146] (Other Embodiments) [SBFD Configuration 1 and SBFD Configuration 2] The above embodiments are applicable to PUSCH repetition Type A, PUSCH repetition Type B, and multi-scheduling PUSCH in SBFD Configuration 1 and SBFD Configuration 2.

[0147] SBFD Configuration 1 restricts UL transmission and DL reception to either SBFD symbols or non-SBFD symbols. For example, in PUSCH transmission under SBFD Configuration 1, assignments spanning both SBFD and non-SBFD symbols are not possible. For example, when scheduling two PUSCHs using multi-scheduling PUSCH, the two PUSCHs will transmit using either SBFD symbols only or non-SBFD symbols only. In the case of SBFD Configuration 1, the TDRA table may contain separate settings (configurations) for SBFD symbols only and non-SBFD symbols only. The above embodiment is applicable to a TDRA table dedicated to SBFD symbols.

[0148] SBFD Configuration 2 does not restrict UL transmission and DL reception to SBFD symbols and non-SBFD symbols. For example, in PUSCH transmission in SBFD Configuration 2, assignments can span both SBFD and non-SBFD symbols. For instance, when scheduling two PUSCHs using multi-scheduling PUSCH, the first PUSCH can be transmitted using SBFD symbols, and the second PUSCH can be transmitted using non-SBFD symbols. In SBFD Configuration 2, PUSCH repetition Type A, PUSCH repetition Type B, and multi-scheduling PUSCH are likely to be scheduled across both non-SBFD and SBFD symbols. Therefore, it is preferable to consider the operation of UL resource muting. Examples of UL resource muting operation are explained below in two cases.

[0149] <Case 1: Cases where there are no restrictions on the operation of UL resource muting> UL resource muting for PUSCH repetition Type A, PUSCH repetition Type B, or multi-scheduling PUSCH in SBFD configuration 2 can be assigned to both SBFD symbols / slots and non-SBFD symbols / slots.

[0150] <Case 2: Cases where restrictions are placed on the operation of UL resource muting> When restrictions are placed on the operation of UL resource muting, the following restrictions may be possible.

[0151] (Option 1) Restrictions by Configuration Type In Option 1, UL resource muting is restricted by the SBFD configuration type (e.g., SBFD Configuration 1 or SBFD Configuration 2). For example, UL resource muting can be configured for UL transmissions in SBFD Configuration 1, but not for UL transmissions in SBFD Configuration 2. In this case, for example, UL resource muting can be configured for PUSCH repetition Type A in SBFD Configuration 1, but not for PUSCH repetition Type A in SBFD Configuration 2.

[0152] (Option 2) Restrictions by Slot / Symbol Type In Option 2, UL resource muting is restricted by slot or symbol type. For example, UL resource muting can be set for SBFD slots / symbols, but not for non-SBFD slots / symbols. In this case, for example, when applying UL resource muting to PUSCH repetition Type A in SBFD configuration 2, UL resource muting will be applied to PUSCH for SBFD slots / symbols, but not to PUSCH for non-SBFD slots / symbols.

[0153] [Determination of UL resource muting allocation by terminal] The UL resource muting setting method described in the above embodiment describes the case in which the base station 100 determines which PUSCH to allocate the UL resource muting to and performs scheduling, but is not limited to this.

[0154] For example, terminal 200 may decide whether to allocate UL resource muting. For instance, if the allocated resources for PUSCH are low, allocating UL resource muting may degrade the performance of PUSCH. Therefore, terminal 200 does not need to allocate UL resource muting if the allocated resources for PUSCH are low (for example, below a threshold).

[0155] Other embodiments have been described above.

[0156] Note that the parameter values ​​used in the above embodiment, such as the number of PUSCHs to be multi-scheduled, the time allocation parameters (K2, S, L), and the number of bits for notification information, are just examples and other values ​​may be used.

[0157] Furthermore, the TDRA table used in the above embodiment is just an example, and the TDRA table described above may include other parameters, or some of the parameters included in the TDRA table described above may be omitted.

[0158] (Supplement) Information indicating whether or not the terminal 200 supports the functions, operations, or processes described in the above-described embodiment may be transmitted (or notified) from the terminal 200 to the base station 100 as, for example, capability information or capability parameters of the terminal 200.

[0159] The capability information may include an information element (IE) that individually indicates whether the terminal 200 supports at least one of the functions, operations, or processes shown in the embodiments described above. Alternatively, the capability information may include an information element that indicates whether the terminal 200 supports any two or more combinations of the functions, operations, or processes shown in the embodiments described above.

[0160] For example, the base station 100 may determine (or decide or assume) which functions, operations, or processes the source terminal 200 supports (or does not support) based on capability information received from the terminal 200. The base station 100 may perform operations, processes, or controls in accordance with the determination result based on the capability information. For example, the base station 100 may control the measurement and reporting settings of the inter-base station CLI based on capability information received from the terminal 200.

[0161] Furthermore, the fact that the terminal 200 does not support some of the functions, operations, or processes shown in the embodiments described above may be interpreted as the terminal 200 having restrictions on such some functions, operations, or processes. For example, information or requests regarding such restrictions may be notified to the base station 100.

[0162] Information regarding the capabilities or limitations of terminal 200 may, for example, be defined in a standard, or it may be implicitly communicated to base station 100 in association with information known at base station 100 or information transmitted to base station 100.

[0163] (Control Signals) In this disclosure, the downlink control signals (or downlink control information) relating to one embodiment of this disclosure may be, for example, signals (or information) transmitted in a Physical Downlink Control Channel (PDCCH) at the physical layer, or signals (or information) transmitted in a Medium Access Control Control Element (MAC CE) or Radio Resource Control (RRC) at a higher layer. Furthermore, the signals (or information) are not limited to being notified by downlink control signals, but may be predetermined in a specification (or standard), or may be pre-configured in base stations and terminals.

[0164] In this disclosure, the uplink control signal (or uplink control information) related to one embodiment of this disclosure may be, for example, a signal (or information) transmitted in the physical layer PUCCH, or a signal (or information) transmitted in the upper layer MAC CE or RRC. Furthermore, the signal (or information) is not limited to being notified by the uplink control signal, but may be predetermined in the specification (or standard), or may be pre-configured in the base station and terminal. In addition, the uplink control signal may be replaced with, for example, uplink control information (UCI), 1st stage sidelink control information (SCI), or 2nd stage SCI.

[0165] (Base Station) In one embodiment of the present disclosure, the base station may be a Transmission Reception Point (TRP), cluster head, access point, Remote Radio Head (RRH), eNodeB (eNB), gNodeB (gNB), Base Station (BS), Base Transceiver Station (BTS), master unit, gateway, etc. Also, in side-link communication, the terminal may assume the role of a base station. Alternatively, instead of a base station, there may be a relay device that relays communication between the upper node and the terminal. There may also be a roadside unit.

[0166] (Uplink / Downlink / Sidelink) An embodiment of the present disclosure may be applied to, for example, an uplink, a downlink, or a sidelink. For example, an embodiment of the present disclosure may be applied to a Physical Uplink Shared Channel (PUSCH), Physical Uplink Control Channel (PUCCH), Physical Random Access Channel (PRACH) of an uplink, a Physical Downlink Shared Channel (PDSCH), PDCCH, Physical Broadcast Channel (PBCH) of a downlink, or a Physical Sidelink Shared Channel (PSSCH), Physical Sidelink Control Channel (PSCCH), Physical Sidelink Broadcast Channel (PSBCH) of a sidelink.

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

[0168] (Data Channel / Control Channel) One embodiment of the present disclosure may be applied to either a data channel or a control channel, for example. For example, the channel in one embodiment of the present disclosure may be replaced with any of the data channels PDSCH, PUSCH, PSSCH, or the control channels PDCCH, PUCCH, PBCH, PSCCH, PSBCH.

[0169] (Reference Signal) In one embodiment of the present disclosure, the reference signal is, for example, a signal known to both the base station and the mobile station, and may be called a Reference Signal (RS) or pilot signal. The reference signal may be any of the following: Demodulation Reference Signal (DMRS), Channel State Information - Reference Signal (CSI-RS), Tracking Reference Signal (TRS), Phase Tracking Reference Signal (PTRS), Cell-specific Reference Signal (CRS), or Sounding Reference Signal (SRS).

[0170] (Time Interval) In one embodiment of the present disclosure, the unit of time resource is not limited to one or a combination of slots and symbols, but may be a time resource unit such as a frame, superframe, subframe, slot, time slot, subslot, minislot, or symbol, Orthogonal Frequency Division Multiplexing (OFDM) symbol, Single Carrier - Frequency Division Multiplexing Access (SC-FDMA) symbol, or any other time resource unit. Furthermore, the number of symbols contained in one slot is not limited to the number of symbols exemplified in the above embodiment, but may be any other number of symbols.

[0171] (Frequency Band) One embodiment of the present disclosure may be applied to either a licensed band or an unlicensed band.

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

[0173] Furthermore, one embodiment of this disclosure may be applied to any of the following: a terrestrial network, a satellite, or a non-terrestrial network (NTN) using a high-altitude pseudo-satellite (HAPS). Also, one embodiment of this disclosure may be applied to terrestrial networks with large cell sizes, ultra-wideband transmission networks, and other networks where transmission delay is large relative to symbol length or slot length.

[0174] (SBFD) In ​​one embodiment of the present disclosure, the operation for uplink, downlink, and sidelink symbols may also be applied to symbols (e.g., SBFD symbols) on which SBFD (Subband non-overlapping full duplex, Subband full duplex) operation or control is performed. In an SBFD symbol, a frequency domain (or frequency resource, frequency band) is divided into multiple frequency domains (e.g., also called subbands, RB sets, subbands, or sub-BWPs (Bandwidth parts)). A terminal transmits and receives in different directions (e.g., downlink or uplink) on a subband basis. In an SBFD symbol, a terminal may transmit and receive in either the uplink or downlink direction only, and not in the other direction. On the other hand, a base station may be able to transmit and receive both uplink and downlink simultaneously. An SBFD symbol may have a smaller frequency domain available for downlink transmission compared to a symbol that transmits and receives only downlink. Similarly, an SBFD symbol may have a smaller frequency domain available for uplink transmission compared to a symbol that transmits and receives only uplink.

[0175] Furthermore, in the SBFD symbol, a terminal may transmit and receive both uplink and downlink simultaneously. In this case, the frequency domain from which the terminal transmits and the frequency domain from which it receives may not be adjacent, and a frequency gap (also called a frequency interval) may be maintained between them.

[0176] Furthermore, sidelink transmission and reception may be included as different transmission and reception directions for each subband unit, which is a divided region.

[0177] (XDD: cross division duplex) In one embodiment of the present disclosure, the operation for uplink, downlink, and sidelink symbols may be applied to symbols (e.g., full duplex symbols) on which full duplex operation or control is performed. In full duplex symbols, both the terminal and the base station can transmit and receive uplink and downlink simultaneously. In full duplex symbols, the terminal and base station may transmit and receive simultaneously in the available frequency domain (or frequency resource, frequency band), or they may transmit and receive simultaneously in some frequency domains (i.e., they may transmit or receive in other frequency domains). In this case, the frequency domain on which the base station or terminal transmits and the frequency domain on which it receives may not be adjacent, and a frequency gap (also called a frequency gap) may be maintained between them. Alternatively, for example, to reduce interference, either the terminal or the base station may transmit and receive simultaneously (i.e., the other may transmit or receive).

[0178] Furthermore, full duplex operation may be applied to operations where the terminal can simultaneously transmit and receive sidelinks. Also, full duplex operation may be applied to operations where the terminal can simultaneously transmit and receive sidelinks and uplinks or downlinks.

[0179] (Antenna Port) In one embodiment of the present disclosure, an antenna port refers to a logical antenna (antenna group) composed of one or more physical antennas. For example, an antenna port does not necessarily refer to a single physical antenna, but may refer to an array antenna composed of multiple antennas. For example, the number of physical antennas that make up an antenna port is not specified, and it may be defined as the smallest unit on which a terminal station can transmit a reference signal. An antenna port may also be defined as the smallest unit on which the weighting of a precoding vector is multiplied.

[0180] <5G NR System Architecture and Protocol Stack> The 5G NR system architecture as a whole assumes an NG-RAN (Next Generation - Radio Access Network) with gNBs. The gNBs provide the UE-side termination for the user plane (SDAP / PDCP / RLC / MAC / PHY) and control plane (RRC) protocols of NG radio access. The gNBs are connected to each other by Xn interfaces. Furthermore, the gNBs are connected to the NGC (Next Generation Core) by Next Generation (NG) interfaces, more specifically to the AMF (Access and Mobility Management Function) (e.g., a specific core entity performing the AMF) by NG-C interfaces, and to the UPF (User Plane Function) (e.g., a specific core entity performing the UPF) by NG-U interfaces. The NG-RAN architecture is shown in Figure 22 (see, for example, 3GPP TS 38.300 v15.6.0, section 4).

[0181] <RRC Connection Setup and Reconfiguration Procedure> This describes the communication between the UE, gNB, and AMF (5GC entity) when the UE transitions from RRC_IDLE to RRC_CONNECTED in the NAS section (see TS 38.300 v15.6.0).

[0182] RRC is a higher-layer signaling (protocol) used for configuring the UE and gNB. The AMF prepares the UE context data (which includes, for example, the PDU session context, security key, UE Radio Capability, UE Security Capabilities, etc.) and sends it to the gNB along with an Initial Context Setup Request. The gNB then activates AS security together with the UE. This is done by the gNB sending a SecurityModeCommand message to the UE, and the UE responding to the gNB with a SecurityModeComplete message. Subsequently, the gNB sends an RRCReconfiguration message to the UE, and upon receiving an RRCReconfigurationComplete from the UE, the gNB reconfigures itself to set up the Signaling Radio Bearer 2 (SRB2) and Data Radio Bearer (DRB). For signaling-only connections, the SRB2 and DRB are not set up, so the RRCReconfiguration step is omitted. Finally, the gNB notifies the AMF that the setup procedure is complete with an Initial Context Setup Response.

[0183] Accordingly, this disclosure provides a 5th Generation Core (5GC) entity (e.g., AMF, SMF, etc.) comprising a control circuit that establishes a Next Generation (NG) connection with gNodeB during operation, and a transmission unit that sends an initial context setup message to gNodeB via the NG connection during operation so that a signaling radio bearer between gNodeB and User Equipment (UE) is set up. Specifically, gNodeB transmits Radio Resource Control (RRC) signaling, including a Resource Allocation Setting Information Element (IE), to the UE via the signaling radio bearer. The UE then transmits on the uplink or receives on the downlink based on the resource allocation setting.

[0184] <QoS Control> The 5G QoS (Quality of Service) model is based on QoS flows and supports both QoS flows where a guaranteed flow bit rate is required (GBR: Guaranteed Bit Rate QoS flows) and QoS flows where a guaranteed flow bit rate is not required (non-GBR QoS flows). Therefore, at the NAS level, a QoS flow is the finest granularity of QoS within a PDU session. QoS flows are identified within a PDU session by a QoS Flow ID (QFI: QoS Flow ID) carried in the encapsulation header via the NG-U interface.

[0185] For each UE, the 5GC establishes one or more PDU sessions. For each UE, the NG-RAN establishes, for example, at least one Data Radio Bearers (DRB) in accordance with the PDU session. Additional DRBs for the QoS flow of that PDU session can be configured later (when this is done is up to the NG-RAN). The NG-RAN maps packets belonging to various PDU sessions to various DRBs. NAS-level packet filters in the UE and 5GC associate UL packets and DL packets with QoS flows, while AS-level mapping rules in the UE and NG-RAN associate UL QoS flows and DL QoS flows with DRBs.

[0186] (Open-RAN) The base station described in each embodiment (for example, a 5G NR base station called a gNB) may consist of three functional modules: a Centralized Unit (CU), a Distributed Unit (DU), and a Radio Unit (RU).

[0187] CU may be referred to as, for example, a central node, aggregation node, central station, aggregation station, or central unit. DU may be referred to as, for example, an O-DU (O-RAN Distributed Unit), a distributed node, a distributed station, or a distributed unit. RU may be referred to as, for example, an O-RU (O-RAN Radio Unit), a radio device, a radio node, a radio station, an antenna unit, or a radio unit.

[0188] The functional division configuration (or functional division point) between CU, DU, and RU has multiple division options defined. The term "functional division point" is sometimes referred to as "split," "option," or "split option."

[0189] Examples of "splitting options" include the following splitting options 1 to 8. The functions of the base station described in each embodiment may be split into CU, DU, and RU functions according to any of the following splitting options 1 to 8. For example, CU, DU, and RU may be functionally split individually, or functional split may occur only between CU and DU, or only between DU and RU. (1) Splitting option 1: Between RRC (radio resource control) and PDCP (2) Splitting option 2: Between PDCP and RLC (High-RLC) (3) Splitting option 3: Between High-RLC and Low-RLC (4) Splitting option 4: Between RLC (Low-RLC) and MAC (High-MAC) (5) Splitting option 5: Between High-MAC and Low-MAC (6) Splitting option 6: Between MAC (Low-MAC) and PHY (High-PHY) (7) Splitting option 7: Between High-PHY and Low-PHY (8) Splitting option 8: Between PHY (Low-PHY) and RF

[0190] The functional division point between the CU and O-DU may be Split Option 2. The section between the CU and O-DU is called the midhaul, and the F1 interface is defined by 3GPP. The section between the O-DU and O-RU is called the fronthaul, and its functional division point may be Split Option 7-2x, which has been adopted as the O-RAN fronthaul specification.

[0191] Figure 23 shows an example of splitting the base station functions of a gNB into CU, O-DU, and O-RU using Split Option 2 and Split Option 7-2x.

[0192] The CU may, for example, include RRC (radio resource control) functionality, SDAP (service data adaptation protocol) functionality, and PDCP (packet data convergence protocol) functionality.

[0193] The O-DU may include, for example, RLC (radio link control) functionality, MAC functionality, and high-level physical layer (HIGH-PHY) functionality. The HIGH-PHY functionality may also include encoding functionality, scrambling functionality, modulation functionality, layer mapping functionality, precoding functionality, and RE (resource element) mapping functionality for downlink (DL) transmission. The HIGH-PHY functionality may also include decoding functionality, descrambling functionality, demodulation functionality, layer demapping functionality, and RE (resource element) demapping functionality for uplink (UL) reception.

[0194] The O-RU may, for example, be equipped with a LOW-PHY function and an RF function. The LOW-PHY function may also be equipped with a beamforming function, an IFFT (Inverse Fast Fourier Transform) + CP (Cyclic Prefix) application function, and a D / A (Digital to Analog) conversion function for downlink transmission. The LOW-PHY function may also be equipped with an A / D (Analog to Digital) conversion function, a CP removal + FFT (Fast Fourier Transform) function, and a beamforming function for uplink reception.

[0195] If the O-DU does not have a precoding function, the O-RU may have a precoding function.

[0196] The O-RU may also be equipped with LBT (listen before talk) functionality. In Split Option 7-2x, eCPRI (Evolved Common Public Radio Interface) is specified as the communication method between the O-DU and O-RU. In Split Option 7-2x, eCPRI transmits and receives not only the sampling sequence of the in-phase (I) and quadrature (Q) components of the OFDM signal in the frequency domain, but also information used for beamforming in the antenna and time synchronization signals.

[0197] The information transmitted by the signals described in each embodiment (PDCCH, PUCCH, PDSCH, PUSCH, MAC CE, RRC, etc.) may be transmitted between the O-DU and O-RU via the eCPRI's User Plane (U-Plan) or Control Plane (C-Plane).

[0198] If the functions described in each embodiment are executed in the O-RU by functional partitioning, the O-DU may control the O-RU by transmitting information for controlling the functions via a control signal (e.g., eCPRI) between the O-DU and the O-RU.

[0199] If the functions described in each embodiment are executed in the O-DU by functional partitioning, the O-RU may receive the result of the execution of the function in the O-DU via a control signal (e.g., eCPRI) and control the O-RU based on the received result.

[0200] The CU, O-DU, and O-RU may be deployed in physically different devices connected by optical fibers or the like, or some or all of their functions may be deployed in the same physical device.

[0201] CU and O-DU may be logical entities implemented as software running on a server such as a cloud, as a virtualized RAN (virtual Radio Access Network: vRAN). Furthermore, some or all of the functions of CU and O-DU may be provided as a service of virtualized network functions (NFV).

[0202] The transceiver does not have to be a wireless transceiver; for example, it may be a network transceiver, an optical transceiver, etc. The wireless resources allocated by the O-DU may be resources for wireless communication between the O-RU and the UE.

[0203] This disclosure can be implemented using software, hardware, or software integrated with hardware.

[0204] Each functional block used in the description of the above embodiments may be implemented partially or entirely as an integrated circuit (LSI), and each process described in the above embodiments may be controlled partially or entirely by a single LSI or a combination of LSIs. An LSI may consist of individual chips, or it may consist of a single chip that includes some or all of the functional blocks. An LSI may have data inputs and outputs. Depending on the degree of integration, LSIs may also be referred to as ICs, system LSIs, super LSIs, or ultra LSIs.

[0205] The integrated circuit implementation method is not limited to LSIs; it may also be implemented using dedicated circuits, general-purpose processors, or dedicated processors. Furthermore, a Field Programmable Gate Array (FPGA) that can be programmed after LSI manufacturing, or a reconfigurable processor that allows for the reconfiguration of the connections and settings of circuit cells within the LSI, may also be used. This disclosure may be implemented as digital or analog processing.

[0206] Furthermore, if advancements in semiconductor technology or other derived technologies lead to the emergence of integrated circuit technologies that can replace LSIs, then naturally, it would be possible to use those technologies to integrate functional blocks. The application of biotechnology, for example, is a possibility.

[0207] This disclosure is applicable to all types of devices, systems, and equipment having communication capabilities (collectively referred to as communication equipment). Communication equipment may include a radio transceiver and a processing / control circuit. The radio transceiver may include a receiver and a transmitter, or both as functions. The radio transceiver (transmitter, receiver) may include an RF (Radio Frequency) module and one or more antennas. The RF module may include an amplifier, an RF modulator / demodulator, or similar. Non-exclusive examples of communication devices include telephones (mobile phones, smartphones, etc.), tablets, personal computers (PCs) (laptops, desktops, notebooks, etc.), cameras (digital still / video cameras, etc.), digital players (digital audio / video players, etc.), wearable devices (wearable cameras, smartwatches, tracking devices, etc.), game consoles, digital book readers, telehealth / telemedicine devices, vehicles or mobile transport with communication capabilities (cars, airplanes, ships, etc.), and combinations of the above-mentioned devices.

[0208] Communication devices are not limited to portable or movable devices, but also include all kinds of non-portable or fixed devices, devices, and systems, such as smart home devices (appliances, lighting fixtures, smart meters or measuring instruments, control panels, etc.), vending machines, and any other "things" that may exist on an IoT (Internet of Things) network.

[0209] Communication includes data communication via cellular systems, wireless LAN systems, and communication satellite systems, as well as data communication using combinations of these.

[0210] Furthermore, the communication device also includes devices such as controllers and sensors that are connected to or linked to a communication device that performs the communication functions described in this disclosure. For example, this includes controllers and sensors that generate control signals and data signals used by the communication device that performs the communication functions of the communication device.

[0211] Furthermore, communication equipment includes infrastructure facilities such as base stations, access points, and any other devices, devices, and systems that communicate with or control the aforementioned non-limited types of equipment.

[0212] A terminal according to one embodiment of the present disclosure comprises a control circuit that determines the setting of a second time resource that does not perform uplink transmission for a first time resource to which a plurality of uplink data scheduled by a single downlink control information is allocated, based on information set in a time domain resource allocation table, and a transmission circuit that transmits the plurality of uplink data based on the second time resource.

[0213] In one embodiment of the present disclosure, the time domain resource allocation table includes information indicating whether or not the second time resource is applied, which is set in common for the plurality of uplink data.

[0214] In one embodiment of the present disclosure, the time domain resource allocation table is configured individually for each of the plurality of uplink data, with information indicating whether or not the second time resource is applicable.

[0215] In one embodiment of the present disclosure, information is set to indicate whether or not the second time resource is applied to each of the plurality of uplink data, and the time domain resource allocation table includes information indicating one of the plurality of patterns.

[0216] In one embodiment of the present disclosure, information is set that indicates a pattern indicating whether or not the second time resource is applied to each of the plurality of uplink data, and the time domain resource allocation table includes information indicating whether or not the pattern is applied.

[0217] A base station according to one embodiment of the present disclosure comprises a control circuit that determines the setting of a second time resource that does not perform uplink transmission for a first time resource to which a plurality of uplink data scheduled by a single downlink control information is allocated, based on information set in a time domain resource allocation table, and a receiving circuit that receives the plurality of uplink data based on the second time resource.

[0218] In a communication method according to one embodiment of the present disclosure, the terminal determines, based on information set in a time domain resource allocation table, the setting of a second time resource that does not perform uplink transmission for a first time resource to which a plurality of uplink data scheduled by a single downlink control information is allocated, and transmits the plurality of uplink data based on the second time resource.

[0219] In a communication method according to one embodiment of the present disclosure, the base station determines, based on information set in a time domain resource allocation table, the setting of a second time resource that does not perform uplink transmission for a first time resource to which a plurality of uplink data scheduled by a single downlink control information is allocated, and receives the plurality of uplink data based on the second time resource.

[0220] All disclosures in the specification, drawings, and abstract contained in the Japanese application No. 2025-017712, filed on February 5, 2025, are incorporated herein by reference.

[0221] One embodiment of this disclosure is useful for wireless communication systems.

[0222] 100 Base station 101, 201 Receiving unit 102, 202 Demodulation / decoding unit 103 Muting resource setting unit 104 Scheduling unit 105, 205 Control information holding unit 106, 206 Data / control information generation unit 107, 207 Encoding / modulation unit 108, 208 Transmitting unit 200 Terminal 203 Muting resource allocation unit 204 Transmitting control unit

Claims

A control circuit determines the setting of a second time resource that does not perform uplink transmission for a first time resource to which multiple uplink data scheduled by a single downlink control information is allocated, based on the information set in the time domain resource allocation table, A transmission circuit that transmits the plurality of uplink data based on the second time resource, A terminal equipped with the following. 　 The time domain resource allocation table includes information indicating whether or not the second time resource is applied, which is set in common for the multiple uplink data. The terminal according to claim 1. 　 The time domain resource allocation table includes information indicating whether or not the second time resource is applied, which is set individually for each of the multiple uplink data. The terminal according to claim 1. 　 Information is set that shows multiple patterns indicating whether or not the second time resource is applied to each of the multiple uplink data, The aforementioned time-domain resource allocation table includes information indicating one of the multiple patterns. The terminal according to claim 1. 　 Information is set that shows one pattern indicating whether or not the second time resource is applied to each of the aforementioned plurality of uplink data, The aforementioned time domain resource allocation table includes information indicating whether or not the aforementioned pattern is applied. The terminal according to claim 1. 　 A control circuit determines the setting of a second time resource that does not perform uplink transmission for a first time resource to which multiple uplink data scheduled by a single downlink control information is allocated, based on the information set in the time domain resource allocation table, A receiving circuit that receives the plurality of uplink data based on the second time resource, A base station equipped with the following. 　 The device is, Based on the information set in the time domain resource allocation table, the setting of a second time resource that does not perform uplink transmission is determined for the first time resource to which multiple uplink data scheduled by one downlink control information are allocated. Based on the second time resource, the plurality of uplink data are transmitted. Communication method. 　 The base station is, Based on the information set in the time domain resource allocation table, the setting of a second time resource that does not perform uplink transmission is determined for the first time resource to which multiple uplink data scheduled by one downlink control information are allocated. Based on the second time resource, the plurality of uplink data are received. Communication method.

Images