Terminal, base station, transmission method, and reception method

Abstract

This terminal comprises: a control circuit that determines a resource for transmitting an uplink control signal, taking into account an uplink muting resource; and a transmission unit that transmits the uplink control signal on the basis of the determination.

Description

Terminal, base station, transmission method and reception method

[0001] The present disclosure relates to a terminal, a base station, a transmission method, and a reception method.

[0002] In recent years, the expansion and diversification of wireless services has led to the dramatic development of the Internet of Things (IoT). Mobile communications are now being used not only in smartphones and other information terminals, but also in a wide range of applications, including automobiles, homes, home appliances, and industrial equipment. To support this diversification, significant improvements in the performance and functionality of mobile communication systems are required, addressing various requirements, such as increasing the number of connected devices and achieving low latency, in addition to increasing system capacity. Fifth-generation mobile communication systems (5G) boast high capacity, ultra-high speed (eMBB: enhanced Mobile BroadBand), massive machine-type communication (mMTC: massive machine-type communication), and ultra-reliable and low-latency communication (URLLC: ultra-reliable and low-latency communication). By leveraging these features, 5G will provide flexible wireless communications to meet a wide variety of needs.

[0003] The international standardization organization 3GPP (3rd Generation Partnership Project) is currently working on the specification of New Radio (NR) as one of the 5G wireless interfaces. The basic functions of eMBB and URLLC were specified in Release 15, and from Release 16 onwards, URLLC has been extended to include industrial IoT, V2X (Vehicle-to-Everything), and non-terrestrial networks (NTN: Non-Terrestrial Networks) including satellites. The extended 3GPP specifications from Release 18 onwards have been called 5G-Advanced (see, for example, Non-Patent Documents 1-4).

[0004] 3GPP TS 38.211 V18.3.0, "Physical channels and modulation (Release 18) ", Jun. 20243GPP TS 38.212 V18.3.0, "Multiplexing and channel coding (Release 18)", Jun. 20243GPP TS 38.213 V18.3.0, "Physical layer procedure for control (Release 18)", Jun. 20243GPP TS 38.214 V18.3.0, "Physical layer procedures for data (Release 18)", Jun. 20243GPP RAN1#117 Chairman's note, May 2024

[0005] Subband non-overlapping full duplex (SBFD) and dynamic / flexible time division duplex (TDD) are discussed in Release 18. Figures 1A and 1B show examples of SBFD, and Figure 2 shows an example of dynamic / flexible TDD.

[0006] Figure 1A shows an example of the operation of a base station (also called gNB) and a terminal (also called User Equipment (UE)) in the same cell in SBFD operation. In SBFD operation, the base station performs SBFD operation (full duplex operation), while the terminal performs half duplex operation.

[0007] Figure 1B shows an example of SBFD operation. The vertical axis represents frequency and the horizontal axis represents time. UL represents uplink transmission, DL represents downlink transmission, and unused resources are shown in white. Frequency resources are divided into multiple subbands, and each subband supports transmission in different directions. A base station can transmit and receive on both the uplink and downlink simultaneously, while a terminal can only transmit and receive on either the uplink or downlink in a given time resource (e.g., UE#1 can communicate with the base station on the uplink and UE#2 on the downlink at the same time).

[0008] Figure 2 shows an example of the operation of different base stations and terminals in dynamic / flexible TDD operation. In dynamic / flexible TDD operation, base stations and terminals operate in half-duplex mode, and different base stations may have different transmission directions. In the example in Figure 2, base station 1 (gNB1) is transmitting downlink to the terminal and base station 2 (gNB2) is receiving uplink from the terminal at the same time.

[0009] However, there is room for further study on the method of determining UCI resources when UCI is multiplexed onto PUSCH transmission to which uplink resource muting is applied.

[0010] A non-limiting example of the present disclosure determines a UCI resource when UCI is multiplexed onto a PUSCH transmission to which uplink resource muting is applied.

[0011] A terminal according to one embodiment of the present disclosure includes a control circuit that determines a resource for transmitting an uplink control signal in consideration of an uplink muting resource, and a transmitter that transmits the uplink control signal based on the determination.

[0012] These comprehensive or specific aspects may be realized as a system, an apparatus, a method, an integrated circuit, a computer program, or a recording medium, or may be realized as any combination of a system, an apparatus, a method, an integrated circuit, a computer program, and a recording medium.

[0013] According to an embodiment of the present disclosure, resource configuration can be performed appropriately, and in particular, SBFD symbol configuration can be performed appropriately.

[0014] Further advantages and benefits of one embodiment of the present disclosure will become apparent from the specification and drawings. Such advantages and / or benefits may be provided by some embodiments and features described in the specification and drawings, respectively, but not necessarily all of them may be provided to obtain one or more identical features.

[0015] Example of operation of a base station and terminal within the same cell in SBFD operation Example of SBFD operation Example of operation of different base stations and terminals in Dynamic / flexible TDD operation Example of CLI between base stations Example of how to use uplink muting resources Example of muting resource pattern Example of transmitting UCI by multiplexing it onto PUSCH Example of using the existing UCI resource determination method without considering uplink resource muting Block diagram showing an example of the configuration of part of a base station Block diagram showing an example of the configuration of part of a terminal When uplink muting resources are not configured When uplink muting resources are configured When uplink muting resources are not configured When uplink muting resources are configured When uplink muting resources are not configured When uplink muting resources are configured When uplink muting resources are not configured When uplink muting resources are configured Sequence diagram Block diagram showing an example of the detailed configuration of part of a base station Block diagram showing an example of the detailed configuration of part of a terminal NG-RAN architecture Example of functional division of gNB base station functions into CU, O-DU, and O-RU using Split Option 2 and Split Option 7-2x

[0016] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the drawings.

[0017] [Dynamic / flexible TDD operation] Dynamic / flexible TDD operation can cause various types of interference, such as cross-link interference (CLI) between terminals and between base stations. CLI between terminals and base stations significantly degrades reception characteristics, so countermeasures are needed.

[0018] Figure 3 shows an example of CLI between base stations. For example, dynamic / flexible TD operation may involve communications in different directions at the same time, as shown in Figure 3. At this time, the base station receiving the uplink (victim gNB in ​​Figure 3) may receive CLI from the base station transmitting the downlink (aggressor gNB in ​​Figure 3), potentially degrading the uplink reception characteristics. Here, the interfering base station is also called the aggressor gNB, and the interfered base station is also called the victim gNB. The victim gNB measures CLI between base stations to avoid CLI between base stations. The measurement results are shared between base stations (aggressor gNB and victim gNB), and CLI between base stations can be avoided by scheduling, etc.

[0019] In addition, CLI between base stations can occur even in the case of SBFD operation. For example, in SBFD operation, leakage interference (CLI leakage) can occur from the downlink subband of the aggressor gNB operating in SBFD to the uplink subband of the victim. In this case, the victim gNB measures CLI leakage between base stations and estimates the interference covariance matrix to avoid CLI leakage between base stations and perform received signal processing to suppress interference.

[0020] [CLI Measurement Method] This section explains the CLI measurement method between base stations. The aggressor gNB transmits a downlink channel or signal for measurement, and the victim gNB receives and measures that downlink channel or signal. At this time, the victim gNB needs to know the configuration of the aggressor gNB's downlink channel or signal for measurement, so it shares information about the downlink channel or signal for measurement in advance. While receiving and measuring the downlink channel or signal for measurement, the victim gNB may also receive an uplink channel or signal from a terminal belonging to the victim gNB. As a result, the CLI measurement between base stations includes the uplink channel or signal, which may result in an inaccurate measurement of the CLI between base stations.

[0021] Uplink muting resources are considered for accurate inter-base station CLI measurements and covariance matrix estimation. The victim gNB configures uplink muting resources for terminals (terminals belonging to the victim gNB) on the same time and frequency resources as the measurement downlink channel or signal, and the terminals belonging to the victim gNB do not transmit on the configured resources. This allows the victim gNB to accurately measure inter-base station CLI measurements excluding the influence from the uplink.

[0022] Figure 4 shows an example of how uplink muting resources are used. The aggressor gNB transmits a measurement downlink channel or signal (mesh resource) using symbols #9 and #10. A terminal belonging to the victim gNB is assigned a muting resource on the same resource (resource indicated by a vertical line) and does not transmit a PUSCH (Physical Uplink Shared Channel). The victim gNB receives the measurement downlink channel or signal on this muting resource, allowing it to measure the CLI value between base stations without the influence of the uplink.

[0023] [Muting Resource] Regarding uplink muting resources, transparent and non-transparent methods are under consideration.

[0024] In the transparent method, muting resources are implicitly configured by the base station scheduling, i.e., the base station schedules uplink resources for the terminal, avoiding resources to be muted (the terminal is not notified of information about the muting resources).

[0025] On the other hand, in the non-transparent method, information (e.g., configuration) of muting resources is notified from the base station to the terminal, and the terminal does not allocate an uplink channel or signal to the notified muting resources.

[0026] In Release 19, support for a non-transparent method of muting uplink resources at the resource element (RE) level is being considered (see, for example, Non-Patent Document 5).

[0027] Figure 5 shows an example of a muting resource pattern. The uplink muting resource pattern at the RE level is assumed to have a comb-like arrangement (Comb-2) with every two subcarriers in the frequency domain, and a maximum of two symbols in the time domain, as shown in Figure 5. Furthermore, it is assumed that the uplink muting resource pattern for a terminal does not overlap with an uplink channel demodulation reference signal (DMRS: Demodulation Reference Signal) or a phase noise estimation reference signal (PTRS: Phase Tracking Reference Signal) within the same symbol.

[0028] Furthermore, it is assumed that power boosting is applied to REs in symbols with uplink muting resources, and that the PUSCH transmission power does not change between symbols. For example, in the case of a comb-like arrangement in which every two subcarriers are arranged, half of the subcarriers are muted and have a transmission power of 0. Therefore, if the transmission power of the non-muted subcarriers (the remaining half) is doubled, the transmission power will be the same as that of a symbol without a muting resource, and therefore the PUSCH transmission power will not change between symbols.

[0029] [Resource Allocation] In NR, a terminal transmits and receives data in accordance with resource allocation indicated by a layer 1 control signal (Downlink Control Information: DCI) on a downlink control channel (Physical Downlink Control Channel: PDCCH) from a base station or a layer 3 Radio Resource Control (RRC).

[0030] The terminal uses an uplink control channel (PUCCH: Physical Uplink Control Channel) to feed back a response signal (ACK / NACK: Acknowledgement / Negative Acknowledgement or HARQ-ACK: Hybrid Automatic Repeat Request) indicating whether decoding of a downlink data channel (PDSCH: Physical Downlink Shared Channel) has been successful. The terminal can also transmit downlink channel state information (CSI: Channel State Information) to the base station using the PUCCH in addition to the ACK / NACK.

[0031] These ACK / NACK and CSI are also called uplink control information (UCI). When transmitting an ACK / NACK for a PDSCH allocated by DCI, the terminal transmits a PUCCH according to the resource allocation indicated by the DCI from the base station. The control information included in the DCI may include information about the PUCCH resource, and may include information about the timing of transmitting the PUCCH after how many slots after the slot in which the PDSCH is received (K1 or PDSCH-to-HARQ_feedback timing indication).

[0032] The terminal transmits an uplink data channel (PUSCH) in accordance with a resource allocation (Grant) instructed by the terminal in the DCI or RRC on the PDCCH from the base station. The control information included in the DCI or RRC may include information about the time domain resource for transmitting the PUSCH. For example, the information about the time domain resource may include information (K2) about the timing of transmitting the PUSCH after how many slots after the slot in which the PDCCH is received, the position of the first symbol of the PUSCH within the slot, and information about the number of symbols to transmit the PUSCH.

[0033] In uplink transmissions by a terminal, the transmission resources for the PUCCH and the PUSCH may overlap in time. In this case, in NR, the terminal can multiplex UCI and uplink data onto the PUSCH for transmission (see, for example, Non-Patent Documents 2-3).

[0034] When UCI (for example, ACK / NACK) is multiplexed into PUSCH for transmission, the amount of resources (the number of REs) allocated to UCI in PUSCH can be calculated by the following formula (for example, see Non-Patent Document 2). where: Furthermore, may be Also, may be.

[0035] In addition, the set of REs in the first OFDM (Orthogonal Frequency Division Multiplexing) symbol to which data can be assigned on the PUSCH is defined as Let the set of REs in the l-th OFDM symbol to which UCI can be assigned on the PUSCH be Then, in a symbol in which no DMRS is transmitted before the symbol in which the first DMRS is transmitted in the PUSCH, and for symbols that do not transmit DMRS, where, does not include at least REs used for DMRS and PT-RS.

[0036] The UCI is allocated the amount of resources (number of REs) allocated to UCI on the PUSCH according to the frequency-first-time-second rule from the set of REs to which UCI can be allocated. The frequency domain allocation is also mapped to distributed REs within the bandwidth (subcarriers) allocated to the PUSCH.

[0037] Fig. 6 shows an example in which UCI is multiplexed onto a PUSCH for transmission. Fig. 6 shows an example in which the PUSCH bandwidth (number of subcarriers) is 12 subcarriers and the amount of resources (number of REs) allocated to UCI is 15. If the first symbol number is #0, then symbol #1 has 12 REs to which UCI can be allocated, and UCI is mapped to all REs. Symbol #2 has 12 REs to which UCI can be allocated, but the number of UCI resources to be allocated is the remainder after allocation in symbol #1, i.e., 15 - 12 = 3, and UCI is mapped to distributed REs.

[0038] As mentioned above, Release 19 is considering supporting a non-transparent method of muting uplink resources at the RE level. In this case, it is assumed that UCI may be multiplexed on a PUSCH transmission to which uplink resource muting is applied. However, since the existing UCI resource determination method for PUSCH (e.g., calculation of the amount of UCI resources (number of REs) for PUSCH and resource mapping) does not take uplink muting resources into consideration, there is room for further study on the UCI resource determination method when UCI is multiplexed on a PUSCH transmission to which uplink resource muting is applied.

[0039] Fig. 7 shows an example of a case where an existing UCI resource determination method is used without considering uplink resource muting. When an uplink resource muting resource pattern overlaps with a UCI resource, for example, if the UCI resource overlapping with the uplink resource muting pattern is overwritten with the uplink resource muting pattern, the amount of resources (the number of REs) used for UCI transmission decreases, which may result in degradation of UCI transmission performance. In the example shown in Fig. 7, a collision occurs between the UCI resource and the uplink resource muting pattern for nine resources, so the amount of UCI resources (the number of REs) is six.

[0040] An object of the present disclosure is to provide a terminal device, a base station device, a communication method, and a control method that can appropriately determine the resource of UCI to be multiplexed onto PUSCH when the transmission resources for PUCCH transmission and PUSCH transmission overlap in time and an uplink muting resource is set on the PUSCH transmission resource.

[0041] Specifically, the UCI resource to be multiplexed onto the PUSCH is determined in consideration of the uplink muting resource. The determination of the UCI resource may include calculating the amount of UCI resources (the number of modulation symbols or the number of REs) and / or determining a method for mapping UCI onto the PUSCH.

[0042] This embodiment will be described in detail below.

[0043] [Overview of Communication System] A communication system according to an aspect of the present disclosure includes, for example, at least one base station and at least one terminal.

[0044] FIG. 8 is a block diagram showing a configuration example of a portion of a base station 800 according to an embodiment of the present disclosure, and FIG. 9 is a block diagram showing a configuration example of a portion of a terminal 900 according to an embodiment of the present disclosure.

[0045] In the base station 800 shown in Fig. 8, a communication unit (e.g., corresponding to a receiving unit) receives an uplink control signal. A control unit (e.g., corresponding to a control circuit) determines a resource for receiving the uplink control signal in consideration of an uplink muting resource.

[0046] In the terminal 900 shown in Fig. 9, a communication unit (e.g., a transmitter) transmits the uplink control signal using resources determined by a control unit. The control unit (e.g., a control circuit) determines resources for transmitting the uplink control signal in consideration of uplink muting resources.

[0047] [Embodiment 1] In this embodiment, the amount of UCI resources (the number of modulation symbols or the number of REs) on the PUSCH is calculated without taking into account uplink muting resources. This is intended to make the coding rate of UCI the same regardless of the presence or absence of uplink muting resources by making the amount of UCI resources (the number of modulation symbols or the number of REs) on the PUSCH the same regardless of the presence or absence of uplink muting resources. However, when calculating the upper limit of the amount of resources to be allocated to UCI in the PUSCH, the uplink muting resources are taken into account.

[0048] On the other hand, for the UCI mapping method of mapping UCI onto PUSCH, a set of REs to which UCI can be allocated is determined taking into consideration uplink muting resources. Specifically, REs used in uplink muting resources are not included in the set of REs to which UCI can be allocated. In other words, the amount of UCI resources calculated using REs other than those used in uplink muting resources is allocated.

[0049] 10A and 10B show examples in which this embodiment is applied, where Fig. 10A shows a case in which no uplink muting resources are configured, and Fig. 10B shows a case in which uplink muting resources are configured.

[0050] 10B shows an example in which uplink muting resources are set to symbol #1 and symbol #2 when the first symbol number is #0. Also shown is an example in which the PUSCH bandwidth (number of subcarriers) is 12 subcarriers and the amount of resources (number of REs) allocated to UCI is 15. When the first symbol number is #0, the number of REs to which UCI can be allocated for symbol #1 and symbol #2 is 6, which is 12 subcarriers minus the number of REs set as uplink muting resources, and UCI is mapped to all REs except for the uplink muting resources. For symbol #3, the number of REs to which UCI can be allocated is 12, but the number of UCI resources to be allocated is the remainder after allocation for symbol #1 and symbol #2, i.e., 15-12=3, and UCI is mapped to distributed REs.

[0051] According to the present embodiment, the coding rate of UCI can be made the same regardless of whether or not there is an uplink muting resource, and therefore degradation of UCI transmission performance can be avoided.

[0052] The terminal may be notified of information about uplink muting resources (which may also be referred to as a muting resource pattern or a muting resource configuration) using RRC signaling, MAC (Medium Access Control) signaling, DCI, or a combination thereof. The information about uplink muting resources may include, for example, the number of muting symbols in a slot, the position of the muting symbols in a slot, a comb number, etc. as a muting resource pattern. Information about the periodicity and offset of the muting resource pattern may also be included. A configuration ID may also be included, and parameters such as the muting resource pattern and the periodicity may be identified by the configuration ID.

[0053] When the transmission resources for PUCCH transmission and PUSCH transmission overlap in time, the terminal multiplexes UCI (ACK / NACK and CSI) that was to be transmitted on the PUCCH onto the PUSCH and transmits the multiplexed UCI.

[0054] <Method of Determining the Amount of UCI Resources> In a slot in which the transmission resources of the PUCCH and the PUSCH overlap in time, the amount of UCI resources to be allocated to the PUSCH, for example, the number of REs or the number of modulation symbols, may be calculated as follows. where: Furthermore, may be Also, may be.

[0055] Also, and is the number of subcarriers used for uplink resource muting in the l-th OFDM symbol.

[0056] In the present embodiment, as described above, the uplink muting resource is not taken into consideration when calculating the amount of UCI resources (the number of modulation symbols or the number of REs), i.e., in the first term of the min function in equation (2) (i.e., the first term is the same as equation (1)). However, when calculating the upper limit of the amount of resources to be allocated to UCI in the PUSCH (i.e., the second term of the min function in equation (2)), the uplink muting resource is taken into consideration.

[0057] <UCI mapping method> of is defined as the set of REs available for data transmission in an OFDM symbol, where does not include the number of subcarriers used for DMRS, PTRS, and uplink resource muting. of In the OFDM symbols before the first DMRS symbol in the PUSCH, the set of REs available for UCI transmission is defined as and for symbols that do not transmit DMRS, is.

[0058] In this embodiment, as described above, a set of REs to which UCIs can be allocated is determined in consideration of uplink muting resources.

[0059] The UCI is allocated the amount of resources (number of REs) allocated to UCI on the PUSCH according to the frequency-first-time-second rule from the set of REs to which UCI can be allocated. The frequency domain allocation is also mapped to distributed REs within the bandwidth (subcarriers) allocated to the PUSCH.

[0060] [Embodiment 2] In this embodiment, uplink muting resources are taken into consideration when calculating the amount of UCI resources (the number of modulation symbols or the number of REs) on the PUSCH. Specifically, the number of REs available for UCI transmission is calculated by subtracting the number of REs used for uplink resource muting.

[0061] This is because the amount of UCI resources (the number of modulation symbols or the number of REs) on the PUSCH may be reduced due to the presence of uplink muting resources. Therefore, in this embodiment, the coding rate of UCI is adjusted using a parameter that controls the coding rate of UCI in order to avoid or reduce the impact of a reduction in the amount of UCI resources on the PUSCH.

[0062] Furthermore, for a UCI mapping method for mapping UCI onto a PUSCH, a set of REs to which UCI can be allocated is determined taking into consideration uplink muting resources. Specifically, REs used in uplink muting resources are not included in the set of REs to which UCI can be allocated.

[0063] According to the present embodiment, it is possible to avoid or mitigate the influence of a change in the coding rate of UCI depending on the presence or absence of uplink muting resources, thereby preventing degradation of UCI transmission performance. Furthermore, by subtracting the number of REs used for uplink resource muting when calculating the number of REs available for UCI transmission, it is possible to easily match the coding rate of the data signal on the PUSCH (calculated taking into account the number of REs used for uplink resource muting).

[0064] The terminal may be notified of information about uplink muting resources (which may also be referred to as a muting resource pattern or a muting resource configuration) using RRC signaling, MAC signaling, DCI, or a combination thereof. The information about uplink muting resources may include, for example, the number of muting symbols in a slot, the position of the muting symbols in a slot, a comb number, etc. as a muting resource pattern. Information about the periodicity and offset of the muting resource pattern may also be included. A configuration ID may also be included, and parameters such as the muting resource pattern and the periodicity may be identified by the configuration ID.

[0065] When the transmission resources for PUCCH transmission and PUSCH transmission overlap in time, the terminal multiplexes UCI (ACK / NACK and CSI) that was to be transmitted on the PUCCH onto the PUSCH and transmits the multiplexed UCI.

[0066] <Method of Determining the Amount of UCI Resources> In a slot in which the transmission resources of the PUCCH and the PUSCH overlap in time, the amount of UCI resources to be allocated to the PUSCH, for example, the number of REs or the number of modulation symbols, may be calculated as follows. where: Furthermore, may be Also, may be.

[0067] In the present embodiment, as described above, the uplink muting resource is taken into consideration when calculating the amount of UCI resources (the number of modulation symbols or the number of REs), i.e., in the first term of the min function in equation (3).Furthermore, the uplink muting resource is also taken into consideration when calculating the upper limit of the amount of resources to be allocated to UCI in the PUSCH (i.e., the second term of the min function in equation (3)).

[0068] <UCI mapping method> of, is defined as the set of REs available for data transmission in an OFDM symbol, where does not include the number of subcarriers used for DMRS, PTRS and uplink resource muting. of, In the OFDM symbols before the first DMRS symbol in the PUSCH, the set of REs available for UCI transmission is defined as and for symbols that do not transmit DMRS, is.

[0069] In this embodiment, as described above, a set of REs to which UCIs can be allocated is determined in consideration of uplink muting resources.

[0070] The UCI is allocated the amount of resources (number of REs) allocated to UCI on the PUSCH according to the frequency-first-time-second rule from the set of REs to which UCI can be allocated. The frequency domain allocation is also mapped to distributed REs within the bandwidth (subcarriers) allocated to the PUSCH.

[0071] <Parameters that control the coding rate of UCI> Parameters that control the coding rate of UCI may be set to one value semi-statically by RRC, or multiple values ​​(for example, 2 or 4) may be set by RRC, and one of the multiple values ​​set by RRC may be notified by DCI. In this embodiment, the uplink muting resource is taken into consideration in calculating the UCI resource amount (the number of modulation symbols or the number of REs). By adjusting the number of REs allocated to UCI, the number of REs allocated to UCI is controlled to be the same as that in embodiment 1. Therefore, the same examples as in Figs. 10A and 10B can be used.

[0072] (Option 1) In this embodiment, for example, a parameter for controlling the coding rate of the existing UCI is used. The coding rate of UCI when uplink muting resources are present may be controlled using Option 1. For example, two values ​​may be set by RRC, and one value may be implicitly signaled depending on whether uplink muting resources are present. Alternatively, for example, four values ​​may be set by RRC, and a set having two values ​​may be implicitly signaled depending on whether uplink muting resources are present, and one value may be explicitly signaled by DCI from among them. Option 1 can reduce the impact of standard changes and can suppress an increase in overhead required for setting parameters that control the coding rate of UCI.

[0073] (Option 2) In this embodiment, a parameter for controlling the coding rate of different UCIs is set depending on the presence or absence of uplink muting resources. In other words, if no uplink muting resources are configured, the existing parameters and when uplink muting resources are configured, the existing parameters is different from may be set. and For Option 2, one value may be semi-statically set by RRC, or multiple values ​​(e.g., 2 or 4) may be set by RRC, and one of the multiple values ​​set by RRC may be notified by DCI. Option 2 allows flexible setting of the UCI coding rate depending on the presence or absence of uplink muting resources.

[0074] (Option 3) In this embodiment, the existing parameter for controlling the coding rate of UCI is set depending on the presence or absence of uplink muting resources. and multiplied by a scaling factor In other words, if no uplink muting resources are configured, the existing parameters and when uplink muting resources are configured, the existing parameters multiplied by a scaling factor may be set. The scaling factor may be set to one value semi-statically by the RRC, or may be set to multiple values ​​(e.g., 2 or 4) by the RRC, and one of the multiple values ​​set by the RRC may be notified by the DCI. The UCI coding rate may be set quasi-statically by RRC, or different coefficients may be set depending on the number of symbols in the muting resource. Option 3 allows flexible setting of the UCI coding rate depending on whether or not there is an uplink muting resource.

[0075] [Embodiment 3] In this embodiment, the amount of UCI resources (the number of modulation symbols or the number of REs) on the PUSCH is calculated without taking into account uplink muting resources. On the other hand, the amount of UCI resources (the number of modulation symbols or the number of REs) finally allocated on the PUSCH may vary depending on the number of REs used for UL resource muting.

[0076] Specifically, in this embodiment, it is assumed that power boosting is applied to REs in a symbol with an uplink muting resource, and the total transmission power is intended to be the same regardless of the presence or absence of an uplink muting resource, and the amount of UCI resources finally allocated to PUSCH is determined. However, when calculating the upper limit of the amount of resources allocated to UCI in PUSCH, the uplink muting resource is taken into consideration.

[0077] On the other hand, for the UCI mapping method of mapping UCI onto the PUSCH, the set of REs to which UCI can be allocated is determined taking into account uplink muting resources. Specifically, REs used in uplink muting resources are not included in the set of REs to which UCI can be allocated.

[0078] 11A and 11B show examples when this embodiment is applied. Fig. 11A shows a case where no uplink muting resource is configured, while Fig. 11B shows a case where an uplink muting resource is configured. When the first symbol number is #0, this example shows an uplink muting resource being configured to symbol #1 and symbol #2. This example also shows a case where the PUSCH bandwidth (number of subcarriers) is 12 subcarriers, and the amount of resources (number of REs) allocated to the calculated UCI is 18.

[0079] Assuming that the first symbol number is #0 and that a 2x power boost is applied to REs in symbols #1 and #2, where uplink muting resources are configured, mapping to one RE in symbols #1 and #2 corresponds to mapping to two REs. In symbol #1, the number of REs to which UCI can be assigned is 6, which is 12 subcarriers minus the number of REs configured for uplink muting resources, and UCI is mapped to all REs except for the uplink muting resources. Here, the UCI resources mapped to symbol #1 correspond to 6 x 2 = 12 REs. In symbol #2, UCI is mapped to 3 REs, which correspond to the remaining 6 REs, and UCI is also mapped to distributed REs.

[0080] According to this embodiment, the total UCI transmission power can be made the same regardless of the presence or absence of uplink muting resources, thereby preventing degradation of UCI transmission performance. Furthermore, by determining the amount of UCI resources ultimately allocated to the PUSCH in consideration of the application of power boost, it is possible to suppress an increase in the amount of resources allocated to UCI, and thus suppress degradation of PUSCH data transmission performance.

[0081] The terminal may be notified of information about uplink muting resources (which may also be referred to as a muting resource pattern or a muting resource configuration) using RRC signaling, MAC signaling, DCI, or a combination thereof. The information about uplink muting resources may include, for example, the number of muting symbols in a slot, the position of the muting symbols in a slot, a comb number, etc. as a muting resource pattern. Information about the periodicity and offset of the muting resource pattern may also be included. A configuration ID may also be included, and parameters such as the muting resource pattern and the periodicity may be identified by the configuration ID.

[0082] When the transmission resources for PUCCH transmission and PUSCH transmission overlap in time, the terminal multiplexes UCI (ACK / NACK and CSI) that was to be transmitted on the PUCCH onto the PUSCH and transmits the multiplexed UCI.

[0083] <Method of Determining the Amount of UCI Resources> In a slot in which the transmission resources of the PUCCH and the PUSCH overlap in time, the amount of UCI resources to be allocated to the PUSCH, for example, the number of REs or the number of modulation symbols, may be calculated as follows. where: Furthermore, may be Also, Also, and is the number of subcarriers used for uplink resource muting in the l-th OFDM symbol.

[0084] In the present embodiment, as described above, the uplink muting resource is not taken into consideration when calculating the amount of UCI resources (the number of modulation symbols or the number of REs), i.e., in the first term of the min function in equation (2). However, when calculating the upper limit of the amount of resources to be allocated to UCI in the PUSCH (i.e., the second term of the min function in equation (2)), the uplink muting resource is taken into consideration.

[0085] <UCI mapping method> of is defined as the set of REs available for data transmission in an OFDM symbol, where does not include the number of subcarriers used for DMRS, PTRS, and uplink resource muting. of In the OFDM symbols before the first DMRS symbol in the PUSCH, the set of REs available for UCI transmission is defined as and for symbols that do not transmit DMRS, is.

[0086] In this embodiment, as described above, a set of REs to which UCIs can be allocated is determined in consideration of uplink muting resources.

[0087] The UCI is allocated the amount of resources (number of REs) allocated to the UCI described above according to the frequency-first-time-second rule from a set of REs to which the UCI can be allocated on the PUSCH. Furthermore, the frequency domain allocation is mapped to REs distributed over the bandwidth (between subcarriers) allocated to the PUSCH. In this embodiment, in an OFDM symbol including an uplink resource muting resource, the amount of allocated resources when UCI is allocated to one RE is converted to two REs in consideration of power boosting. The conversion ratio may be determined based on the ratio of power boosting.

[0088] [Modification of the Third Embodiment] In the third embodiment, the parameter for controlling the coding rate of UCI is The RRC may set one value semi-statically, or multiple values ​​(e.g., 2 or 4) may be set by the RRC, and one of the multiple values ​​set by the RRC may be notified by the DCI.

[0089] (Option 1) In this modification, for example, the parameter controlling the coding rate of the existing UCI is The coding rate of UCI when uplink muting resources are present may be controlled using Option 1. For example, two values ​​may be set by RRC, and one value may be implicitly notified depending on whether uplink muting resources are present. Alternatively, for example, four values ​​may be set by RRC, and a set having two values ​​may be implicitly notified depending on whether uplink muting resources are present, and one value may be explicitly notified by DCI from among them. Option 1 can reduce the impact of standard changes and can suppress an increase in overhead required for setting parameters that control the coding rate of UCI.

[0090] (Option 2) In this modification, a parameter for controlling the coding rate of different UCIs is used depending on the presence or absence of uplink muting resources. In other words, if no uplink muting resources are configured, the existing parameters and when uplink muting resources are configured, the existing parameters is different from may be set. and For Option 2, one value may be semi-statically set by RRC, or multiple values ​​(e.g., 2 or 4) may be set by RRC, and one of the multiple values ​​set by RRC may be notified by DCI. Option 2 allows flexible setting of the UCI coding rate depending on the presence or absence of uplink muting resources.

[0091] (Option 3) In this modification, the parameter that controls the coding rate of the existing UCI is changed depending on the presence or absence of uplink muting resources. and multiplied by a scaling factor In other words, if no uplink muting resources are configured, the existing parameters and when uplink muting resources are configured, the existing parameters multiplied by a scaling factor may be set. may be set to one value semi-statically by RRC, or multiple values ​​(e.g., 2 or 4) may be set by RRC, and one of the multiple values ​​set by RRC may be notified by DCI. Also, scaling coefficient a may be set to one value semi-statically by RRC, or different coefficients may be set depending on the number of symbols of the muting resource. Option 3 enables flexible setting of the UCI coding rate depending on the presence or absence of an uplink muting resource.

[0092] According to this modification, the total transmission power and coding rate of UCI can be adjusted depending on the presence or absence of uplink muting resources.

[0093] Fourth Embodiment In this embodiment, uplink muting resources are taken into consideration when calculating the amount of UCI resources (the number of modulation symbols or the number of REs) on the PUSCH. Specifically, when calculating the number of REs available for UCI transmission, a value obtained by multiplying the number of REs used for uplink resource muting by an adjustment coefficient is subtracted.

[0094] This is intended to reduce the amount of UCI resources (the number of modulation symbols or the number of REs) on the PUSCH in consideration of the effect of power boost due to the presence of uplink muting resources.

[0095] Furthermore, for a UCI mapping method for mapping UCI onto a PUSCH, a set of REs to which UCI can be allocated is determined taking into consideration uplink muting resources. Specifically, REs used in uplink muting resources are not included in the set of REs to which UCI can be allocated.

[0096] According to the present embodiment, the amount of UCI resources (the number of modulation symbols or the number of REs) on the PUSCH can be calculated taking into account the application of power boosting, thereby making it possible to suppress degradation of UCI transmission performance and degradation of PUSCH data transmission performance.

[0097] The terminal may be notified of information about uplink muting resources (which may also be referred to as a muting resource pattern or a muting resource configuration) using RRC signaling, MAC signaling, DCI, or a combination thereof. The information about uplink muting resources may include, for example, the number of muting symbols in a slot, the position of the muting symbols in a slot, a comb number, etc. as a muting resource pattern. Information about the periodicity and offset of the muting resource pattern may also be included. A configuration ID may also be included, and parameters such as the muting resource pattern and the periodicity may be identified by the configuration ID.

[0098] When the transmission resources for PUCCH transmission and PUSCH transmission overlap in time, the terminal multiplexes UCI (ACK / NACK and CSI) that was to be transmitted on the PUCCH onto the PUSCH and transmits the multiplexed UCI.

[0099] <Method of Determining the Amount of UCI Resources> In a slot in which the transmission resources of the PUCCH and the PUSCH overlap in time, the amount of UCI resources to be allocated to the PUSCH, for example, the number of REs or the number of modulation symbols, may be calculated as follows. where: Furthermore, may be Also, may be.

[0100] In the present embodiment, as described above, the uplink muting resource is taken into consideration when calculating the amount of UCI resources (the number of modulation symbols or the number of REs), i.e., in the first term of the min function in equation (3).Furthermore, the uplink muting resource is also taken into consideration when calculating the upper limit of the amount of resources to be allocated to UCI in the PUSCH (i.e., the second term of the min function in equation (3)).

[0101] <UCI mapping method> of is defined as the set of REs available for data transmission in an OFDM symbol, where does not include the number of subcarriers used for DMRS, PTRS, and uplink resource muting. of is defined as the set of REs available for UCI transmission in an OFDM symbol.

[0102] In a symbol in which DMRS is not transmitted before the first DMRS symbol in the PUSCH, and for symbols that do not transmit DMRS, is.

[0103] In this embodiment, as described above, a set of REs to which UCIs can be allocated is determined in consideration of uplink muting resources.

[0104] The UCI is allocated the amount of resources (number of REs) allocated to UCI on the PUSCH according to the frequency-first-time-second rule from the set of REs to which UCI can be allocated. The frequency domain allocation is also mapped to distributed REs within the bandwidth (subcarriers) allocated to the PUSCH.

[0105] [Modification] In each of the above-described embodiments, figures and formulas are used to illustrate an example in which ACK / NACK is multiplexed as UCI and UCI is multiplexed in a PUSCH that transmits an UL-SCH. Each of the above-described embodiments can also be applied to UCI other than ACK / NACK, such as CSI Part 1 or CSI Part 2.

[0106] Furthermore, the above-described embodiments can also be applied to UCI in a PUSCH that does not transmit a UL-SCH.

[0107] For example, in Section 6.3.2.4.1.1 of Non-Patent Document 2, The number of REs that can be used to transmit UCI for the calculation of The above-described embodiments can be applied to the calculation of .

[0108] For example, when multiplexing CSI Part 1, the following is true: The number of REs that can be used to transmit UCI for the calculation of The above-described embodiments can be applied to the calculation of .

[0109] For example, when multiplexing CSI Part 2, the following is true: The number of REs that can be used to transmit UCI for the calculation of The above-described embodiments can be applied to the calculation of .

[0110] Also, for example, when multiplexing CG-UCI (Configured Grant-UCI), the following is true: The number of REs that can be used to transmit UCI for the calculation of The above-described embodiments can be applied to the calculation of .

[0111] Also, for example, when multiplexing ACK / NACK and CG-UCI, the following is performed: The number of REs that can be used to transmit UCI for the calculation of The above-described embodiments can be applied to the calculation of .

[0112] [Another embodiment 1] In the uplink, in addition to Dynamic grant transmission in which a terminal transmits a PUSCH in accordance with a Grant, which is data allocation information indicated by DCI transmitted on a PDCCH from a base station, the terminal supports Configured grant transmission in which the terminal transmits a PUSCH on pre-specified resources without a Grant by DCI.

[0113] Among the above-described embodiments, the applicable embodiment, modified example, or option may differ depending on whether dynamic grant transmission or configured grant transmission is used. Furthermore, the parameter for controlling the coding rate of UCI (β in each embodiment or γ in embodiment 4) may be set differently depending on whether dynamic grant transmission is used or configured grant transmission is used.

[0114] According to this embodiment, it is possible to apply an appropriate UCI resource determination method to each of Dynamic grant transmission and Configured grant transmission.

[0115] [Another Embodiment 2] Figures 12A and 12B show an example in which this embodiment is applied. Figure 12A shows a case in which no uplink muting resources are configured, and Figure 12B shows a case in which uplink muting resources are configured. As shown in Figure 12B, when the number of REs assigned to UCI is half or less of the total number of REs in a symbol, there is a possibility that UCI resources, uplink muting resources, and data are multiplexed in one OFDM symbol. In Figure 12B, three types of resources, namely, UCI resources, uplink muting resources, and data (PUSCH), are multiplexed in symbol #2. When many types are multiplexed, taking into account the multiplexing of UCI resources and the power boost provided by uplink muting resources, the control of data rate matching adjustment and data coding rate adjustment may become complicated.

[0116] Therefore, if the amount of resources (the number of REs) in one symbol to which UCI is mapped is less than half of the total number of REs in the symbol, the REs set as uplink muting resources do not need to be muted, i.e., the REs set as uplink muting resources may be regarded as REs available for transmitting data or UCI.

[0117] 13A and 13B are examples of UCI mapping in this embodiment. Fig. 13A shows a case where no uplink muting resource is configured, and Fig. 13B shows a case where an uplink muting resource is configured. Fig. 13B shows an example where uplink muting resources are configured for symbol #1 and symbol #2, but the amount of UCI resources for symbol #2 is less than half of the total number of REs, so the REs configured as the uplink muting resources are not muted.

[0118] According to this embodiment, it is possible to simplify the control relating to UCI resource determination, the rate matching adjustment of data, and the control of the coding rate adjustment of data.

[0119] [Sequence Diagram] Fig. 14 is a sequence diagram according to the present disclosure. The base station transmits settings related to PUSCH transmission, PUCCH transmission, and uplink muting resources to the terminal (step S1401).

[0120] The base station transmits PUSCH scheduling information to the terminal (step S1402).

[0121] The base station transmits PDSCH scheduling information and PUCCH resource notification to the terminal (step S1403).

[0122] The terminal determines whether the transmission resources for the PUCCH transmission and the PUSCH transmission overlap in time (step S1404).

[0123] If the transmission resources overlap (step S1404, Yes), the terminal determines the UCI resource to be multiplexed on the PUSCH (step S1405) and transmits the PUSCH (step S1406).

[0124] If the transmission resources do not overlap (step S1404, No), the terminal transmits the PUSCH and the PUCCH (step S1407).

[0125] After step S1406 or S1407, the process returns to step S1402, where the base station transmits PUSCH scheduling information to the terminal. Returning to step S1401, the base station may transmit configurations regarding PUSCH transmission, PUCCH transmission, and uplink muting resources to the terminal.

[0126] 15 is a block diagram showing a detailed example configuration of a part of a base station 800 according to one aspect of the present disclosure.

[0127] The base station 800 includes a receiving unit 1501, an extracting unit 1502, a demodulating unit 1503, a decoding unit 1504, a control unit 1505, a downlink control information generating unit 1506, a higher control signal generating unit 1507, an encoding unit 1508, a modulating unit 1509, a signal allocating unit 1510, and a transmitting unit 1511. At least one of the extracting unit 1502, the demodulating unit 1503, the decoding unit 1504, the control unit 1505, the downlink control information generating unit 1506, the higher control signal generating unit 1507, the encoding unit 1508, the modulating unit 1509, and the signal allocating unit 1510 may be configured as a control circuit 1512. The receiving unit 1501 may be configured as a receiving circuit, and the transmitting unit 1511 may be configured as a transmitting circuit. At least one of the receiving unit 1501 and the transmitting unit 1511 may be configured as a transmitting / receiving unit.

[0128] The receiving unit 1501 performs RF (Radio Frequency) processing such as down-conversion or A / D conversion on an uplink transmission signal transmitted from the terminal 900 and received via an antenna. In addition, in the case of OFDM transmission, the receiving unit 1501 applies FFT to the received signal to obtain a frequency domain signal, and outputs the frequency domain signal to the extracting unit 1502.

[0129] Based on information received from control section 1505 , extraction section 1502 extracts the radio resource portion on which PUSCH or PUCCH is transmitted from the received signal input from receiving section 1501 , and outputs them to demodulation section 1503 .

[0130] The demodulation section 1503 demodulates the PUSCH or PUCCH based on the information received from the control section 1505 and outputs the demodulation result to the decoding section 1504 .

[0131] The decoding unit 1504 performs error correction decoding on the PUSCH or PUCCH using information received from the control unit 1505 and the demodulation result obtained from the demodulation unit 1503, and obtains a decoded received bit sequence. The received bit sequence may be a UCI or UL data signal.

[0132] The control unit 1505 determines PUCCH resources for the terminal to transmit an uplink data signal (e.g., PUCCH) and outputs the determined information to the downlink control information generation unit 1506 or the higher control signal generation unit 1507. The control unit 1505 determines the coding / modulation scheme and radio resource allocation for the terminal to transmit the uplink data signal. The control unit 1505 outputs the determined information to the downlink control information generation unit 1506, extraction unit 1502, demodulation unit 1503, and decoding unit 1504.

[0133] The control unit 1505 determines whether the PUCCH resource for transmitting UCI and the radio resource for transmitting uplink data overlap in time, and if they overlap in time, determines the amount of UCI resources on the PUSCH using the method described above and outputs it to the extraction unit 1502, the demodulation unit 1503, and the decoding unit 1504.

[0134] In addition, the control unit 1505 determines the coding and modulation scheme and radio resource allocation for the downlink signal for transmitting the downlink data signal, the higher control signal, and the downlink control information, and outputs the determined information to the coding unit 1508, the modulation unit 1509, and the signal allocation unit 1510.

[0135] The control unit 1505 determines information related to PDSCH reception, information related to PUSCH transmission, and information related to PUCCH transmission for the terminal, and outputs the determined information to the downlink control information generation unit 1506 or the higher control signal generation unit 1507. The information related to PDSCH reception and information related to PUSCH transmission may include, for example, information related to a TDRA (Time Domain Resource Allocation) table and information related to frequency resources. Furthermore, the information related to PUCCH transmission may include information related to a PUCCH resource set and information related to K1.

[0136] The control unit 1505 outputs the coding and modulation scheme for the data signal and the higher control signal and radio resource allocation information to the downlink control information generation unit 1506. The control unit 1505 determines the configuration of the muting resource (for example, the allocation pattern of the muting resource) and outputs the determined information to the higher control signal generation unit 1507.

[0137] The downlink control information generating section 1506 generates a DCI bit string using the control information input from the control section 1505, and outputs the generated DCI bit string to the encoding section 1508. Note that the control information may be transmitted to multiple terminals.

[0138] The upper control signal generating section 1507 uses the control information input from the control section 1505 to generate an upper layer control signal bit string and outputs it to the encoding section 1508 .

[0139] The encoding unit 1508 encodes the downlink data, the bit string obtained from the higher control signal generating unit 1507, or the DCI bit string input from the downlink control information generating unit 1506 based on the encoding method input from the control unit 1505, and outputs the encoded bit string to the modulation unit 1509.

[0140] The modulation section 1509 modulates the coded bit string received from the coding section 1508 based on the modulation method input from the control section 1505 and outputs the modulated bit string to the signal allocation section 1510 .

[0141] The signal allocation unit 1510 maps the downlink data signal or control signal input as a symbol sequence from the modulation unit 1509 to the radio resources instructed by the control unit 1505. The signal allocation unit 1510 also inputs the mapped signal to the transmission unit 1511.

[0142] The transmitter 1511 performs transmission waveform generation such as OFDM on the signal output from the signal allocation unit 1510. In the case of OFDM transmission using a CP (Cyclic Prefix), the CP is added after applying IFFT. The transmitter 1511 performs RF processing such as D / A conversion and up-conversion, and transmits the radio signal to the terminal 900 via an antenna.

[0143] [Configuration of Terminal] The configuration of the terminal will be described. Fig. 16 is a block diagram showing a detailed configuration example of a portion of a terminal 900 according to one aspect of the present disclosure. The terminal 900 includes a receiving unit 1601, an extracting unit 1602, a demodulating unit 1603, a decoding unit 1604, a control unit 1605, an encoding unit 1606, a modulating unit 1607, a signal allocating unit 1608, and a transmitting unit 1609. At least one of the extracting unit 1602, the demodulating unit 1603, the decoding unit 1604, the control unit 1605, the encoding unit 1606, the modulating unit 1607, and the signal allocating unit 1608 may be configured as a control circuit 1610. The receiving unit 1601 may be configured as a receiving circuit, and the transmitting unit 1609 may be configured as a transmitting circuit. At least one of the receiving unit 1601 and the transmitting unit 1609 may be configured as a transceiver unit.

[0144] Receiving section 1601 receives a data signal or a downlink control signal transmitted from base station 800 via an antenna, performs RF processing such as down-conversion or A / D conversion on the radio received signal, and outputs the result to extraction section 1602. When receiving an OFDM signal, receiving section 1601 also performs FFT processing on the received signal, converts the received signal into the frequency domain, and outputs the result to extraction section 1602.

[0145] The extracting unit 1602 extracts a radio resource portion including a downlink control signal from the received signal received from the receiving unit 1601, using information related to the radio resource of the control signal input from the control unit 1605, and outputs the extracted radio resource portion to the demodulating unit 1603. The extracting unit 1602 also extracts a radio resource portion including a data signal, using information related to the radio resource of the data signal input from the control unit 1605, and outputs the extracted radio resource portion to the demodulating unit 1603.

[0146] The demodulation section 1603 demodulates the PDCCH or PDSCH based on the information received from the control section 1605 and outputs the demodulation result to the decoding section 1604 .

[0147] The decoder 1604 performs error correction decoding of the PDCCH or PDSCH using the information received from the controller 1605 and the demodulation result obtained from the demodulator 1603, and obtains downlink reception data, upper layer control information, or downlink control information. The obtained upper layer control information and downlink control information are output to the controller 1605. The decoder may also generate an ACK / NACK signal from the decoding result of the downlink reception data.

[0148] The control unit 1605 specifies radio resources for PDSCH reception, PUSCH transmission, PUCCH transmission, and uplink resource muting from radio resource allocation information obtained from the higher layer control signal and downlink control information. The control unit 1605 also outputs the determined information to the signal allocation unit 1608, the extraction unit 1602, and the demodulation unit 1603.

[0149] The control unit 1605 determines whether the PUCCH resource for transmitting the PUCCH and the radio resource for transmitting the uplink data overlap in time, and if they overlap in time, identifies the UCI resource on the PUSCH using the method described above and outputs it to the encoding unit 1606, the modulation unit 1607, and the signal allocation unit 1608.

[0150] The encoding unit 1606 encodes the UCI or the uplink data signal based on the information input from the control unit 1605 and outputs the encoded bit string to the modulation unit 1607 .

[0151] The modulation section 1607 modulates the coded bit sequence received from the coding section 1606 based on the modulation scheme input from the control section 1505 to generate a modulated symbol sequence, and outputs it to the signal allocation section 1608 .

[0152] The signal allocating unit 1608 maps the signal input from the modulating unit 1607 to radio resources instructed by the control unit 1605. The signal allocating unit 1608 also inputs the mapped signal to the transmitting unit 1609. When generating a single-carrier waveform, a DFT unit may be added after the modulating unit 1607 or before the signal allocating unit 1608.

[0153] The transmitting unit 1609 generates a transmission signal waveform such as OFDM for the signal input from the signal allocating unit 1608. In the case of OFDM transmission using CP, a CP is added after IFFT.

[0154] Furthermore, the transmitting section 1609 performs RF processing such as D / A conversion and up-conversion on the transmission signal, and transmits the radio signal to the base station 800 via an antenna.

[0155] (Supplementary Note) Information indicating whether the terminal 900 supports the functions, operations, or processes described in each of the above-described embodiments and each supplementary note may be transmitted (or notified) from the terminal 900 to the base station 800, for example, as capability information or capability parameters of the terminal 900.

[0156] The capability information may include an information element (IE) that individually indicates whether or not the terminal 900 supports at least one of the functions, operations, or processes described in the above-described embodiments, modifications, and supplements. Alternatively, the capability information may include an information element that indicates whether or not the terminal 900 supports a combination of any two or more of the functions, operations, or processes described in the above-described embodiments, modifications, and supplements.

[0157] For example, the base station 800 may determine (or decide or assume) functions, operations, or processes that the terminal 900 that transmitted the capability information supports (or does not support) based on the capability information received from the terminal 900. The base station 800 may perform operations, processes, or controls according to the determination result based on the capability information. For example, the base station 800 may control processing related to uplink control signals based on the capability information received from the terminal 900.

[0158] Note that the fact that terminal 900 does not support some of the functions, operations, or processes described in the above-described embodiments, modifications, and supplementary notes may be interpreted as meaning that such some of the functions, operations, or processes are restricted in terminal 900. For example, information or a request regarding such restrictions may be notified to base station 800.

[0159] Information regarding the capabilities or limitations of terminal 900 may, for example, be defined in a standard, or may be implicitly notified to base station 800 in association with information known at base station 800 or information transmitted to base station 800.

[0160] (Control Signal) In the present disclosure, a downlink control signal (or downlink control information) related to an embodiment of the present disclosure may be, for example, a signal (or information) transmitted in a Physical Downlink Control Channel (PDCCH) of a physical layer, or a signal (or information) transmitted in a Medium Access Control Control Element (MAC CE) or Radio Resource Control (RRC) of a higher layer. Furthermore, the signal (or information) is not limited to being notified by a downlink control signal, but may be predefined in a specification (or standard) or preconfigured in a base station and a terminal.

[0161] In the present disclosure, an uplink control signal (or uplink control information) related to an embodiment of the present disclosure may be, for example, a signal (or information) transmitted in a PUCCH of a physical layer, or a signal (or information) transmitted in a MAC CE or RRC of a higher layer. Furthermore, the signal (or information) is not limited to being notified by an uplink control signal, but may be predefined in a specification (or standard) or preconfigured in a base station and a terminal. Furthermore, the uplink control signal may be replaced with, for example, uplink control information (UCI), 1st stage sidelink control information (SCI), or 2nd stage SCI.

[0162] (Base Station) In an embodiment of the present disclosure, the base station may be a Transmission Reception Point (TRP), a cluster head, an access point, a Remote Radio Head (RRH), an eNodeB (eNB), a gNodeB (gNB), a Base Station (BS), a Base Transceiver Station (BTS), a parent device, a gateway, or the like. In sidelink communication, a terminal may play the role of a base station. Instead of a base station, a relay device that relays communication between an upper node and a terminal may be used. Alternatively, a roadside unit may be used.

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

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

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

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

[0167] (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, for example, a time resource unit such as a frame, a superframe, a subframe, a slot, a time slot, a subslot, a minislot, a symbol, an Orthogonal Frequency Division Multiplexing (OFDM) symbol, a Single Carrier-Frequency Division Multiplexing Access (SC-FDMA) symbol, or another time resource unit. Furthermore, the number of symbols included in one slot is not limited to the number of symbols exemplified in the above-mentioned embodiment, and may be another number of symbols.

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

[0169] (Communication) An 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 an 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.

[0170] An embodiment of the present disclosure may be applied to a terrestrial network, a non-terrestrial network (NTN) using a satellite or a high altitude pseudo satellite (HAPS), or a terrestrial network in which transmission delay is large compared to the symbol length or slot length, such as a network with a large cell size or an ultra-wideband transmission network.

[0171] (SBFD) In ​​one embodiment of the present disclosure, operations on uplink, downlink, and sidelink symbols may be applied to symbols (e.g., SBFD symbols) on which SBFD (Subband Non-Overlapping Full Duplex, Subband Full Duplex) operations or controls are performed. In SBFD symbols, a frequency domain (or frequency resource, frequency band) is divided into multiple frequency domains (e.g., subbands, RB sets, subbands, or sub-BWPs (Bandwidth Parts)). A terminal transmits and receives in different directions (e.g., downlink or uplink) in units of subbands, which are the divided domains. In SBFD symbols, a terminal may transmit and receive in one direction, either uplink or downlink, but not in the other direction. On the other hand, a base station may be capable of transmitting and receiving on both the uplink and downlink simultaneously. SBFD symbols may have a smaller frequency domain available for downlink use than symbols that transmit and receive only downlink use. Also, SBFD symbols may have a smaller frequency domain available for uplink use than symbols that transmit and receive only uplink use.

[0172] In addition, in the SBFD symbol, a terminal may transmit and receive uplink and downlink simultaneously. In this case, the frequency domain in which the terminal transmits and the frequency domain in which the terminal receives may not be adjacent, but may be separated by a frequency interval (also called a frequency gap).

[0173] In addition, different transmission and reception directions in subband units, which are divided areas, may include transmission and reception of side links.

[0174] (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) where full duplex operation or control is performed. In a full duplex symbol, both the terminal and the base station can simultaneously transmit and receive on the uplink and downlink. In a full duplex symbol, the terminal and the base station may simultaneously transmit and receive in an available frequency region (or frequency resource, frequency band), or may simultaneously transmit and receive in a partial frequency region (i.e., transmission or reception may be performed in other frequency regions). In this case, the frequency region in which the base station or terminal transmits and receives may not be adjacent, but may have a frequency interval (also called a frequency gap). Furthermore, for the purpose of, for example, reducing interference, either the terminal or the base station may simultaneously transmit and receive (i.e., the other may transmit or receive).

[0175] In addition, full duplex operation may be applied to an operation in which a terminal can simultaneously transmit and receive sidelinks, or to an operation in which a terminal can simultaneously transmit and receive sidelinks and uplinks or downlinks.

[0176] (Antenna Port) In one embodiment of the present disclosure, an antenna port refers to a logical antenna (antenna group) consisting 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 consisting of multiple antennas. For example, the number of physical antennas that an antenna port is composed of is not specified, and the antenna port may be specified as the smallest unit by which a terminal station can transmit a reference signal. Furthermore, an antenna port may also be specified as the smallest unit by which a weighting of a precoding vector is multiplied.

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

[0178] <RRC connection setup and reconfiguration procedure> This shows the NAS part of the interaction between the UE, gNB, and AMF (5GC entity) when the UE transitions from RRC_IDLE to RRC_CONNECTED (see TS 38.300 v15.6.0).

[0179] RRC is a higher layer signaling protocol used to configure the UE and gNB. The AMF prepares UE context data (including, for example, PDU session context, security keys, UE radio capabilities, 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 with a SecurityModeComplete message to the gNB. The gNB then sends an RRCReconfiguration message to the UE, and upon receiving an RRCReconfigurationComplete from the UE, the gNB performs reconfiguration to set up Signaling Radio Bearer 2 (SRB2) and Data Radio Bearer (DRB). For signaling-only connections, the steps related to RRCReconfiguration are omitted because SRB2 and DRB are not set up. Finally, the gNB notifies the AMF that the setup procedure is complete with an INITIAL CONTEXT SETUP RESPONSE.

[0180] Therefore, the present disclosure provides a 5th Generation Core (5GC) entity (e.g., AMF, SMF, etc.) that includes: a control circuit that, upon operation, establishes a Next Generation (NG) connection with a gNodeB; and a transmitter that, upon operation, transmits an initial context setup message to the gNodeB via the NG connection so that a signaling radio bearer between the gNodeB and a user equipment (UE) is set up. Specifically, the gNodeB transmits Radio Resource Control (RRC) signaling, including a resource allocation configuration information element (IE), to the UE via the signaling radio bearer. The UE then transmits in uplink or receives in downlink based on the resource allocation configuration.

[0181] <QoS Control> The 5G Quality of Service (QoS) model is based on QoS flows and supports both QoS flows that require a guaranteed flow bit rate (Guaranteed Bit Rate QoS flows (GBR)) and QoS flows that do not require a guaranteed flow bit rate (non-GBR QoS flows). Thus, at the NAS level, a QoS flow is the finest granularity of QoS classification in a PDU session. A QoS flow is identified within a PDU session by a QoS Flow ID (QFI) carried in an encapsulation header over the NG-U interface.

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

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

[0184] A CU may be referred to as a centralized node, aggregation node, central station, aggregation station, or centralized unit. A DU may be referred to as an O-RAN Distributed Unit (O-DU), distributed node, distributed station, or distributed unit. An RU may be referred to as an O-RAN Radio Unit (O-RU), radio equipment, radio node, radio station, antenna unit, or radio unit.

[0185] There are several split options for the functional split configuration (or functional split point) between CU, DU, and RU. The term "functional split point" is sometimes referred to as "split," "option," or "split option."

[0186] Examples of "division options" include the following division options 1 to 8. The functions of the base station described in each embodiment may be divided into a CU, a DU, and an RU by any of the following division options 1 to 8. For example, the CU, DU, and RU may be functionally divided, or the functions may be divided only between the CU and DU or only between the DU and RU. (1) Segmentation option 1: Between RRC (radio resource control) and PDCP (2) Segmentation option 2: Between PDCP and RLC (High-RLC) (3) Segmentation option 3: Between High-RLC and Low-RLC (4) Segmentation option 4: Between RLC (Low-RLC) and MAC (High-MAC) (5) Segmentation option 5: Between High-MAC and Low-MAC (6) Segmentation option 6: Between MAC (Low-MAC) and PHY (High-PHY) (7) Segmentation option 7: Between High-PHY and Low-PHY (8) Segmentation option 8: Between PHY (Low-PHY) and RF

[0187] The functional split point between the CU and O-DU may be split option 2. The section between the CU and O-DU is called midhaul, and the F1 interface is specified by 3GPP. The section between the O-DU and O-RU is called fronthaul, and the functional split point may be split option 7-2x, which is adopted as the O-RAN fronthaul specification.

[0188] Figure 18 shows an example of functional division of the gNB base station functions into CU, O-DU, and O-RU using Split Option 2 and Split Option 7-2x.

[0189] The CU may have, for example, a radio resource control (RRC) function, a service data adaptation protocol (SDAP) function, and a packet data convergence protocol (PDCP) function.

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

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

[0192] In addition, if the O-DU does not have a precoding function, the O-RU may have a precoding function.

[0193] The O-RU may have a function related to LBT (listen before talk). The evolving common public radio interface (eCPRI) is specified as the communication method between the O-DU and the O-RU in Split Option 7-2x. In Split Option 7-2x, eCPRI transmits and receives sampling sequences of the in-phase (I) and quadrature (Q) components of the OFDM signal in the frequency domain, as well as information used for beamforming in the antenna and time synchronization signals.

[0194] 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 the O-RU via the eCPRI User Plane (U-Plane) or Control Plane (C-Plane).

[0195] When the functions described in each embodiment are performed in the O-RU by functional division, 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.

[0196] When the functions described in each embodiment are performed in the O-DU by functional division, the O-RU may receive the results of the functions performed in the O-DU via a control signal (e.g., eCPRI) and control the O-RU based on the received results.

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

[0198] The CU and O-DU may be logical entities implemented as software running on a server in the cloud or the like as a virtualized RAN (virtual Radio Access Network: vRAN). Also, some or all of the functions of the CU and O-DU may be provided as a virtualized network function (Network Functions Virtualization: NFV) service.

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

[0200] The present disclosure can be realized in software, hardware, or software in conjunction with hardware.

[0201] Each functional block used in the description of the above embodiments may be partially or entirely realized as an LSI, which is an integrated circuit, and each process described in the above embodiments may be partially or entirely controlled by a single LSI or a combination of LSIs. The LSI may be composed of individual chips, or may be composed of a single chip that includes some or all of the functional blocks. The LSI may have data input and output. Depending on the degree of integration, the LSI may also be called an IC, system LSI, super LSI, or ultra LSI.

[0202] The integrated circuit method is not limited to LSI, and may be realized by a dedicated circuit, a general-purpose processor, or a dedicated processor. Also, a field programmable gate array (FPGA) that can be programmed after LSI manufacturing, or a reconfigurable processor that can reconfigure the connections and settings of circuit cells within the LSI, may be used. The present disclosure may be realized as digital processing or analog processing.

[0203] Furthermore, if an integrated circuit technology that can replace LSI emerges due to advances in semiconductor technology or other derivative technologies, it is natural that such technology may be used to integrate functional blocks. The application of biotechnology, etc. is also a possibility.

[0204] The present disclosure may be implemented in any type of apparatus, device, or system (collectively referred to as a communications apparatus) that has a communications function. The communications apparatus may include a radio transceiver and processing / control circuitry. The radio transceiver may include a receiver and a transmitter, or both functions. The radio transceiver (transmitter and receiver) may include a radio frequency (RF) module and one or more antennas. The RF module may include an amplifier, an RF modulator / demodulator, or the like. Non-limiting examples of communication devices include telephones (e.g., cell phones, smartphones), tablets, personal computers (PCs) (e.g., laptops, desktops, notebooks), cameras (e.g., digital still / video cameras), digital players (e.g., digital audio / video players), wearable devices (e.g., wearable cameras, smartwatches, tracking devices), game consoles, digital book readers, telehealth / telemedicine devices, communication-enabled vehicles or mobile transportation (e.g., cars, airplanes, ships), and combinations of the above devices.

[0205] The communication devices are not limited to portable or mobile devices, but also include any kind of non-portable or fixed equipment, devices, and systems, such as smart home devices (such as home appliances, lighting equipment, smart meters or measuring devices, control panels, etc.), vending machines, and any other "things" that may exist on an IoT (Internet of Things) network.

[0206] Communications include data communications via cellular systems, wireless LAN systems, communication satellite systems, and the like, as well as data communications via combinations of these.

[0207] A communications apparatus also includes devices such as controllers and sensors connected or coupled to a communications device that performs the communications functions described in this disclosure, such as controllers and sensors that generate control and data signals used by the communications device to perform the communications functions of the communications apparatus.

[0208] The communication apparatus also includes infrastructure facilities, such as base stations, access points, and any other apparatus, device, or system that communicates with or controls the various apparatuses listed above, but are not limited to these.

[0209] (1) A terminal according to one embodiment of the present disclosure includes a control circuit that determines resources for transmitting an uplink control signal in consideration of uplink muting resources, and a transmitting unit that transmits the uplink control signal using the determined resources.

[0210] (2) In a terminal according to one embodiment of the present disclosure, in the terminal of (1), the control circuit calculates the resource amount of the uplink control signal to be equal to or less than an upper limit without taking into account the uplink muting resources, and determines the set of resource elements of the uplink control signal taking into account the uplink muting resources.

[0211] (3) In a terminal according to one embodiment of the present disclosure, in the terminal of (2), the control circuit determines the set of resource elements as a set of resources other than the uplink muting resources.

[0212] (4) In a terminal according to one embodiment of the present disclosure, in the terminal of (1), the control circuit calculates the resource amount of the uplink control signal, not more than an upper limit, taking into account the uplink muting resources, and determines the set of resource elements of the uplink control signal taking into account the uplink muting resources.

[0213] (5) In a terminal according to one embodiment of the present disclosure, in the terminal of (4), the control circuit calculates the amount of resources by adjusting a parameter that controls the coding rate of the uplink control signal.

[0214] (6) In a terminal according to one embodiment of the present disclosure, in the terminal of (2), the control circuit determines the set of resource elements taking power boosting into consideration.

[0215] (7) In a terminal according to an embodiment of the present disclosure, in the terminal of (4), the control circuit calculates the amount of resources taking into account an adjustment coefficient.

[0216] (8) In a terminal according to one embodiment of the present disclosure, in the terminal of (1), the control circuit determines resources for each of Dynamic grant transmission and Configured grant transmission of the PUSCH.

[0217] (9) In a terminal according to one embodiment of the present disclosure, in the terminal of (1), the control circuit does not mute the resources assigned to the uplink muting resource when the number of resources assigned to the uplink control signal is less than or equal to half the number of resources in a symbol.

[0218] (10) A base station according to one embodiment of the present disclosure includes a control circuit that determines a resource for receiving an uplink control signal in consideration of an uplink muting resource, and a receiving unit that receives the uplink control signal based on the determination.

[0219] (11) A transmission method according to one embodiment of the present disclosure determines a resource for transmitting an uplink control signal in consideration of an uplink muting resource, and transmits the uplink control signal based on the determination.

[0220] (12) A receiving method according to one embodiment of the present disclosure determines a resource for receiving an uplink control signal in consideration of an uplink muting resource, and receives the uplink control signal based on the determination.

[0221] The disclosures of the specification, drawings and abstract contained in Japanese Patent Application No. 2024-132047, filed on August 8, 2024, are incorporated herein by reference in their entirety.

[0222] One embodiment of the present disclosure is useful in wireless communication systems.

[0223] 800 Base Station 900 Terminal 1501, 1601 Receiving section 1502, 1602 Extracting section 1503, 1603 Demodulating section 1504, 1604 Decoding section 1505, 1605 Control section 1506 Downlink control information generating section 1507 Upper control signal generating section 1508, 1606 Encoding section 1509, 1607 Modulating section 1510, 1608 Signal allocating section 1511, 1609 Transmitting section 1512, 1610 Control circuit

Claims

1. A terminal comprising: a control circuit that determines resources for transmitting an uplink control signal in consideration of uplink muting resources; and a transmission unit that transmits the uplink control signal using the determined resources.

2. The terminal according to claim 1, wherein the control circuit calculates the amount of resources for the uplink control signal to be equal to or less than an upper limit without taking the uplink muting resources into consideration, and determines the set of resource elements for the uplink control signal while taking the uplink muting resources into consideration.

3. The terminal according to claim 2, wherein the control circuit determines the set of resource elements as a set of resources other than the uplink muting resources.

4. The terminal according to claim 1, wherein the control circuit calculates the amount of resources for the uplink control signal, not more than an upper limit, taking into account the uplink muting resources, and determines a set of resource elements for the uplink control signal taking into account the uplink muting resources.

5. The terminal according to claim 4, wherein the control circuit calculates the amount of resources by adjusting a parameter that controls a coding rate of the uplink control signal.

6. The terminal according to claim 2, wherein the control circuit determines the set of resource elements taking power boosting into consideration.

7. The terminal according to claim 4, wherein the control circuit calculates the amount of resources taking into account an adjustment coefficient.

8. The terminal according to claim 1, wherein the control circuit determines resources for each of Dynamic grant transmission and Configured grant transmission of the PUSCH.

9. The terminal according to claim 1, wherein the control circuit does not mute the resources allocated to the uplink muting resources when the number of resources allocated to the uplink control signal is equal to or less than half the number of resources in a symbol.

10. A base station comprising: a receiver that receives an uplink control signal; and a control circuit that determines a resource for receiving the uplink control signal in consideration of an uplink muting resource.

11. A transmission method comprising: determining a resource for transmitting an uplink control signal in consideration of an uplink muting resource; and transmitting the uplink control signal using the determined resource.

12. A receiving method comprising: receiving an uplink control signal; and determining a resource for receiving the uplink control signal in consideration of an uplink muting resource.

Images