Terminal, base station, transmission method, and reception method

Abstract

This terminal is provided with: a control circuit that controls the transmission of an uplink signal on the basis of temporal positions of a resource of the uplink signal and an uplink muting resource; and a transmission unit that transmits the uplink signal.

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: registered trademark) is 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] There is room for further study on the method of transmitting uplink signals when uplink resource muting is applied.

[0006] A terminal according to one embodiment of the present disclosure includes a control circuit that controls transmission of the uplink signal based on an uplink signal resource and a time position of the uplink muting resource, and a transmitting unit that transmits the uplink signal.

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

[0008] A non-limiting embodiment of the present disclosure determines a method for transmitting an uplink signal when uplink resource muting is applied. According to an embodiment of the present disclosure, resource configuration can be performed appropriately.

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

[0010] Example of operation between a base station and a terminal in the same cell during SBFD operation Example of SBFD operation Example of operation between different base stations and a terminal during 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 PUSCH repetition Type B where K2=1, the position of the first PUSCH symbol in the slot is symbol #0, the number of symbols to transmit PUSCH is 7, and the repetition count is 4 Example of when the nominal PUSCH repetition interval crosses a slot boundary (number of symbols to transmit PUSCH is 4, the repetition count is 2) Example of when contention with uplink and downlink patterns occurs during the nominal PUSCH repetition interval (number of symbols to transmit PUSCH is 7, the repetition count is 4) Example of when contention with uplink muting resources occurs during the nominal PUSCH repetition interval Block diagram showing an example configuration of part of a base station Block diagram showing an example configuration of part of a terminal Actual PUSCH with overlap Example of dropping a repetition Example of not muting an RE set in an uplink muting resource Example of not muting an RE set in an uplink muting resource in a symbol overlapping with DMRS or PT-RS When the amount of PUSCH resources allocated to actual PUSCH repetitions excluding uplink muting resources is equal to or greater than a threshold When the amount of PUSCH resources allocated to actual PUSCH repetitions excluding uplink muting resources is less than a threshold Sequence diagram for PUSCH repetition Type B Sequence diagram for TBoMS Block diagram showing a detailed example configuration of part of a base station Block diagram showing a detailed example configuration of part of a terminal NG-RAN architecture Example of functional division of NB base station functions into CU, O-DU, and O-RU using Split Option 2 and Split Option 7-2x

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

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

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

[0014] 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).

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

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

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

[0018] 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 also 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.

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

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

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

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

[0023] 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).

[0024] On the other hand, in the non-transparent method, the base station notifies the terminal of information (e.g., configuration) of muting resources, and the terminal does not allocate uplink channels or signals to the notified muting resources.

[0025] 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).

[0026] Figure 5 shows an example of a muting resource pattern. The RE-level uplink muting resource pattern is assumed to have a comb-like arrangement (Comb-2) with every other subcarrier in the frequency domain, as shown in Figure 5, and a maximum of two symbols per slot in the time domain. Furthermore, the terminal is assumed to ensure that the uplink muting resource pattern does not overlap with an uplink channel demodulation reference signal (DMRS) or a phase noise estimation reference signal (PTRS) within the same symbol. Furthermore, power boosting is assumed to be applied to REs within a symbol containing uplink muting resources, and the PUSCH transmission power is assumed to remain constant between symbols. For example, in the case of a comb-like arrangement with every other subcarrier, muting is performed on half the subcarriers. Therefore, doubling the transmission power of the non-muted subcarriers (the remaining half) results in the same transmission power as that of a symbol without a muting resource, resulting in no change in the PUSCH transmission power between symbols.

[0027] [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).

[0028] A 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 the success or failure of decoding of a downlink data channel (PDSCH: Physical Downlink Shared Channel). The terminal can also transmit downlink channel state information (CSI: Channel State Information) in addition to the ACK / NACK to the base station using the PUCCH. The ACK / NACK and CSI are also referred to as uplink control information (UCI). When transmitting an ACK / NACK for a PDSCH allocated by DCI, the terminal transmits the PUCCH in accordance with the resource allocation indicated by the DCI from the base station. The control information included in the DCI can include information regarding PUCCH resources and information regarding 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).

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

[0030] In the NR uplink, a method is specified for repeatedly transmitting one or more PUSCHs within one slot for PUSCH (see, for example, Non-Patent Document 4). The base station notifies the terminal of the time domain resource allocation for the first (initial) PUSCH transmission (e.g., K2, the PUSCH first symbol position within the slot, and the number of symbols to transmit the PUSCH) and the number of repetitions. For the second and subsequent PUSCH transmissions, the time domain resource allocation is allocated to symbols consecutive to and the same number of symbols as the previous PUSCH transmission. Hereinafter, this repetition method will be referred to as PUSCH repetition Type B.

[0031] FIG. 6 shows an example of PUSCH repetition Type B where K2=1, the PUSCH first symbol position in the slot is symbol #0, the number of symbols transmitting the PUSCH is 7, and the number of repetitions is 4.

[0032] Data transmitted on the PUSCH is stored in a circular buffer. In the NR uplink, a method for transmitting the PUSCH using multiple slots is specified in which a transport block size (TBS) is calculated based on the number of resources RE available for the PUSCH in multiple slots, and a bit sequence in which consecutive bits are selected from the circular buffer is mapped across multiple slots for transmission (see, for example, Non-Patent Documents 2 and 4). Hereinafter, this method will be referred to as TBoMS (TB processing over Multiple Slots).

[0033] 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 uplink muting resources are configured on PUSCH transmissions generated by PUSCH repetition Type B or TBoMS. However, the existing PUSCH repetition Type B and TBoMS may have the following problems.

[0034] <PUSCH repetition Type B> In PUSCH repetition Type B, when one PUSCH transmission (nominal PUSCH repetition: nominally assigned PUSCH repetition transmission) interval straddles a slot boundary, the single PUSCH transmission is divided (reconfigured) into multiple PUSCH transmissions (actual PUSCH repetition: actually transmitted PUSCH repetition transmissions) and transmitted. Also, when a conflict with an uplink / downlink pattern occurs in the nominal PUSCH repetition interval (i.e., when the nominal PUSCH repetition overlaps with a symbol that cannot be used in the uplink), the nominal PUSCH repetition interval is reconfigured (divided) into one or multiple PUSCH transmissions (actual PUSCH repetitions) and transmitted.

[0035] Fig. 7 shows an example of a case where a PUSCH transmission (nominal PUSCH repetition) interval crosses a slot boundary (the number of symbols for transmitting the PUSCH is 4, and the number of repetitions is 2). Fig. 8 shows an example of a case where contention with an uplink / downlink pattern occurs in a nominal PUSCH repetition interval (the number of symbols for transmitting the PUSCH is 7, and the number of repetitions is 4).

[0036] In PUSCH repetition Type B, an RE or a symbol set as an uplink muting resource may be included in an actual PUSCH repetition resource. Fig. 9 shows an example of a case where contention with an uplink muting resource occurs in a nominal PUSCH repetition period.

[0037] At this time, in the resource allocation for the nominal PUSCH repetition, even if the uplink muting resource pattern does not overlap with the DMRS in the same symbol, in the actual PUSCH repetition, depending on the slot format, the uplink muting resource pattern may overlap with the DMRS in the same symbol.For example, in Figure 9, the 3rd nominal PUSCH repetition does not overlap with the DMRS, but the 3rd actual PUSCH repetition overlaps with the DMRS.

[0038] Furthermore, when an uplink muting resource pattern is configured, the number of REs available for PUSCH data transmission is reduced. Therefore, when the Actual PUSCH repetition, which has a small number of symbols, includes an RE or symbol configured as an uplink muting resource, the coding rate of the PUSCH increases, which may degrade the transmission quality of the PUSCH.

[0039] Therefore, there is room for further study on the method of transmitting PUSCH repetition Type B when uplink muting resources are applied.

[0040] <TBoMS> Data transmitted via PUSCH is stored in a Circular Buffer. In TBoMS, the bit read start position in the Circular Buffer for each slot changes for each slot.

[0041] In TBoMS, the bit read start position on the Circular Buffer for each slot In the first slot of the multiple slots allocated to TBoMS, is the read position corresponding to the notified RV index value (see, for example, Table 5.4.2.1-2 in Non-Patent Document 2). On the other hand, in the multiple slots allocated to TBoMS other than the first slot, where is the bit read start position on the Circular Buffer in the previous slot, H is the number of coding bits available for TB transmission in the previous slot, τ is the number of filler bits skipped in the previous slot (if filler bits exist), is the circular buffer size. Here, the number of coding bits H available for TB transmission in the previous slot is calculated assuming that uplink control information (UCI) is not multiplexed, regardless of whether UCI is multiplexed or not.

[0042] Furthermore, in TBoMS, PUSCH resource allocation is the same for multiple slots allocated to TBoMS. That is, the number H of coding bits available for TB transmission in the previous slot described above can be considered to be the same for multiple slots allocated to TBoMS. Therefore, in determining the bit read start position on the Circular Buffer in the existing TBoMS, if the terminal obtains the amount of resources allocated to PUSCH transmission in the first slot of multiple slots allocated to TBoMS, it is possible to start rate matching processing in subsequent slots regardless of the number of coding bits read in slots previous to that slot.

[0043] However, when an uplink muting resource pattern is configured, among the multiple slots allocated to TBoMS, there may be slots in which an uplink muting resource exists and slots in which an uplink muting resource does not exist. If there is an uplink muting resource among the multiple slots allocated to TBoMS, the number of transmittable bits decreases due to the presence of the uplink muting resource, so the read start bit position on the Circular Buffer when reading out coded bits may differ depending on whether or not the uplink muting resource exists in the previous slot. In this case, the read start bit position of each slot on the Circular Buffer depends on the result of the rate matching process in the previous slot (i.e., the read start bit position of the Circular Buffer in the next slot differs depending on whether or not the uplink muting resource exists in the previous slot). Therefore, the rate matching process for a slot cannot be started until the number of coded bits read in a slot prior to the slot to which rate matching is applied has been obtained. Therefore, there is a risk of an increase in processing delay.

[0044] Furthermore, when uplink muting resources are configured using, for example, a Group-common DCI, the read start bit position on the Circular Buffer when reading coded bits not only depends on the DCI that assigns the corresponding TBoMS, but also on the DCI that configures the uplink muting resources.If these DCI misdetections occur, a discrepancy occurs in the read start bit position on the Circular Buffer when reading coded bits between the base station and the terminal, which may result in a significant degradation of decoding performance or complicate the decoding process at the base station, such as by having the base station perform blind decoding taking into account DCI misdetection.

[0045] 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 prevent degradation in PUSCH quality and processing efficiency when an uplink muting resource is configured on a PUSCH transmission resource for transmitting PUSCH repetition Type B or TBoMS.

[0046] Specifically, in PUSCH repetition Type B, the uplink transmission method is controlled depending on whether or not the actual PUSCH repetition includes an uplink muting resource, or depending on the amount or ratio of the uplink muting resource included in the PUSCH resource allocated to the actual PUSCH repetition.

[0047] In addition, in TBoMS, the read start bit position on the Circular Buffer when reading coded bits from multiple slots allocated to TBoMS is determined based on the number of coded bits calculated based on the reference resource amount that is independent of the presence or absence of uplink muting resources, thereby avoiding complexity in the terminal or processing.

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

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

[0050] FIG. 10 is a block diagram showing a partial configuration example of a base station 1000 according to an embodiment of the present disclosure, and FIG. 11 is a block diagram showing a partial configuration example of a terminal 1100 according to an embodiment of the present disclosure.

[0051] 10 , a communication unit (e.g., corresponding to a receiving unit) receives an uplink signal, and a control unit (e.g., corresponding to a control circuit) controls transmission of the uplink signal based on a resource of the uplink signal and a time position of an uplink muting resource.

[0052] 11 , a communication unit (e.g., a transmitter) transmits the uplink signal using resources determined by a control unit, and a control unit (e.g., a control circuit) controls transmission of the uplink signal based on the resources of the uplink signal and the time positions of the uplink muting resources.

[0053] [Embodiment 1] This embodiment describes processing in a case where, in PUSCH repetition Type B, in resource allocation for nominal PUSCH repetition, the uplink muting resource pattern does not overlap with DMRS or PTRS in the same symbol, but in actual PUSCH repetition, the uplink muting resource pattern overlaps with DMRS or PTRS in the same symbol.

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

[0055] The base station notifies the terminal of the time domain resource allocation for the first (initial) PUSCH transmission (for example, K2, the PUSCH first symbol position within a slot, and the number of symbols to transmit the PUSCH) and the number of repetitions. For the time domain resource allocation for the second and subsequent PUSCH transmissions, symbols consecutive to and the same number of symbols as those in the previous PUSCH transmission are allocated.

[0056] In PUSCH repetition Type B, when one PUSCH transmission (nominal PUSCH repetition) interval spans a slot boundary, the single PUSCH transmission is divided into multiple PUSCH transmissions (actual PUSCH repetitions) for transmission. Also, when a conflict with an uplink / downlink pattern occurs in the nominal PUSCH repetition interval (i.e., when the nominal PUSCH repetition overlaps with a symbol that cannot be used for uplink), the nominal PUSCH repetition interval is divided into one or multiple PUSCH transmissions (actual PUSCH repetitions) for transmission.

[0057] <Option 1> If an uplink muting resource pattern overlaps with a DMRS or PTRS of an actual PUSCH repetition within the same symbol, the terminal drops the actual PUSCH repetition where the overlap occurs. Fig. 12 is an example of Option 1 in this embodiment.

[0058] According to the present embodiment, by muting the DMRS or PTRS, it is possible to stop the transmission of the actual PUSCH repetition whose transmission is disabled, and therefore the base station can measure the CLI using the uplink muting resource while reducing uplink interference. Also, the terminal can avoid an increase in power consumption by stopping the transmission of the actual PUSCH repetition whose transmission is disabled.

[0059] <Option 2> If the uplink muting resource pattern overlaps with the DMRS or PT-RS of the actual PUSCH repetition within the same symbol, the UE does not mute the RE configured as the uplink muting resource, i.e., the UE may regard the RE configured as the uplink muting resource as an RE available for transmitting data, DMRS, PTRS, or UCI.

[0060] FIG. 13 is an example of Option 2 in this embodiment.

[0061] According to this embodiment, the actual PUSCH repetition can be transmitted regardless of the presence or absence of an uplink muting resource, and therefore, performance degradation of the PUSCH repetition can be suppressed.

[0062] [Embodiment 2] This embodiment describes processing in a case where, in PUSCH repetition Type B, resource allocation for nominal PUSCH repetition involves an uplink muting resource pattern that does not overlap with DMRS or PTRS within the same symbol, but in actual PUSCH repetition, some resources of the uplink muting resource pattern overlap with DMRS or PTRS within the same symbol.

[0063] 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 (Radio Resource Control) 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 periodicity may be identified by the configuration ID.

[0064] The base station notifies the terminal of the time domain resource allocation for the first (initial) PUSCH transmission (for example, K2, the PUSCH first symbol position within a slot, and the number of symbols to transmit the PUSCH) and the number of repetitions. For the second and subsequent PUSCH transmissions, the time domain resource allocation allocates consecutive symbols and the same number of symbols as in the previous PUSCH transmission.

[0065] In PUSCH repetition Type B, if one PUSCH transmission (nominal PUSCH repetition) interval spans a slot boundary, the PUSCH transmission is divided into multiple PUSCH transmissions (actual PUSCH repetitions) for transmission. Also, if a conflict with an uplink / downlink pattern occurs in the nominal PUSCH repetition interval (i.e., if the nominal PUSCH repetition overlaps with a symbol that cannot be used in the uplink), the nominal PUSCH repetition interval is divided into one or multiple PUSCH transmissions (actual PUSCH repetitions) for transmission.

[0066] When the uplink muting resource pattern overlaps with the DMRS or PT-RS of the actual PUSCH repetition within the same symbol, the terminal does not mute the REs set as uplink muting resources in the symbols overlapping with the DMRS or PT-RS. That is, the REs set as uplink muting resources may be regarded as REs available for transmitting data, DMRS, PTRS, or UCI. Meanwhile, in the PUSCH resources allocated to the actual PUSCH repetition, in symbols not overlapping with the DMRS or PT-RS, the terminal transmits the actual PUSCH repetition while muting the REs set as uplink muting resources.

[0067] FIG. 14 shows an example of this embodiment.

[0068] According to this embodiment, the actual PUSCH repetition can be transmitted regardless of the presence or absence of an uplink muting resource, thereby suppressing performance degradation of the PUSCH repetition. Also, the base station can measure the CLI using an uplink muting resource of a symbol that does not overlap with the DMRS or PT-RS of the actual PUSCH repetition.

[0069] [Embodiment 3] This embodiment describes processing when an uplink muting resource pattern is included in PUSCH resources allocated to actual PUSCH repetition in PUSCH repetition Type B. However, it is assumed that the uplink muting resource pattern does not overlap with DMRS or PTRS within the same symbol.

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

[0071] The base station notifies the terminal of the time domain resource allocation for the first (initial) PUSCH transmission (for example, K2, the PUSCH first symbol position within a slot, and the number of symbols to transmit the PUSCH) and the number of repetitions. For the time domain resource allocation for the second and subsequent PUSCH transmissions, symbols consecutive to and the same number of symbols as those in the previous PUSCH transmission are allocated.

[0072] In PUSCH repetition Type B, when one PUSCH transmission (nominal PUSCH repetition) interval spans a slot boundary, the single PUSCH transmission is divided into multiple PUSCH transmissions (actual PUSCH repetitions) for transmission. Also, when a conflict with an uplink / downlink pattern occurs in the nominal PUSCH repetition interval (i.e., when the nominal PUSCH repetition overlaps with a symbol that cannot be used in the uplink), the nominal PUSCH repetition interval is divided into one or multiple PUSCH transmissions (actual PUSCH repetitions) for transmission.

[0073] The terminal may calculate the amount of PUSCH resources allocated to the actual PUSCH repetition excluding the uplink muting resource, and may determine whether to transmit the actual PUSCH repetition while muting the RE set as the uplink muting resource, drop the actual PUSCH repetition, or not mute the RE set as the uplink muting resource based on the threshold value of the amount of PUSCH resources. Note that information about the threshold value may be notified using RRC signaling, MAC signaling, DCI, or a combination thereof.

[0074] For example, if the amount of PUSCH resources allocated to the actual PUSCH repetition excluding the uplink muting resources is equal to or greater than a threshold, the terminal may transmit the actual PUSCH repetition while muting the REs set as the uplink muting resources, and if the amount of PUSCH resources allocated to the actual PUSCH repetition excluding the uplink muting resources is less than a threshold, the terminal may drop the actual PUSCH repetition.

[0075] Furthermore, for example, when the amount of PUSCH resources allocated to the actual PUSCH repetition excluding the uplink muting resources is equal to or greater than a threshold, the terminal may transmit the actual PUSCH repetition while muting the REs set as the uplink muting resources, and when the amount of PUSCH resources allocated to the actual PUSCH repetition excluding the uplink muting resources is less than a threshold, the terminal may not mute the REs set as the uplink muting resources.

[0076] 15 is an example of this embodiment. For example, when the number of PUSCH symbols allocated to actual PUSCH repetitions excluding uplink muting resources is used as a threshold and the threshold is 1, FIG. 15A shows a case where the amount of PUSCH resources allocated to actual PUSCH repetitions excluding uplink muting resources is equal to or greater than the threshold (when actual PUSCH repetitions are transmitted while muting), and FIG. 15B shows a case where the amount of PUSCH resources allocated to actual PUSCH repetitions excluding uplink muting resources is less than the threshold (when muting is not performed). When actual PUSCH repetitions are transmitted while muting, for example, in symbols allocated to uplink muting resources, half of the REs of the symbols are muted and actual PUSCH repetitions are transmitted in the remaining half of the REs. Therefore, when the number of symbols is the threshold, the threshold does not need to be an integer. Furthermore, the threshold for the amount of PUSCH resources may be the number of REs, and when the number of REs is the threshold, the threshold may be an integer.

[0077] The threshold for determining whether to transmit the actual PUSCH repetition while muting the RE set in the uplink muting resource, to drop the actual PUSCH repetition, or not to mute the RE set in the uplink muting resource is not limited to the amount of PUSCH resources allocated to the actual PUSCH repetition excluding the uplink muting resource. For example, the threshold may be compared with the amount of uplink muting resources on the PUSCH resources allocated to the actual PUSCH repetition, the ratio between the amount of PUSCH resources allocated to the actual PUSCH repetition and the amount of uplink muting resources, or the coding rate of the PUSCH calculated using the amount of PUSCH resources allocated to the actual PUSCH repetition excluding the uplink muting resource.

[0078] A plurality of parameters may be taken into consideration. For example, when at least one parameter is equal to or greater than a threshold, when all parameters are equal to or greater than a threshold, or when a predetermined number of parameters are equal to or greater than a threshold, the actual PUSCH repetition may be transmitted while muting the REs configured as uplink muting resources, and when all parameters are less than the threshold, when at least one parameter is less than the threshold, or when a predetermined number of parameters are less than the threshold, the REs configured as uplink muting resources may not be muted.

[0079] For example, when the transmission frequency is equal to or greater than a first threshold, the actual PUSCH repetition may be transmitted while muting, when the transmission frequency is less than the first threshold and equal to or greater than a second threshold, the actual PUSCH repetition may not be muted, and when the transmission frequency is less than the second threshold, the actual PUSCH repetition may be dropped.

[0080] According to this embodiment, it is possible to determine whether to transmit the actual PUSCH repetition in consideration of the amount of uplink muting resources on the resources allocated to the actual PUSCH repetition. Therefore, it is possible for the base station to measure the CLI using the uplink muting resources while suppressing performance degradation of the PUSCH repetition and reducing uplink interference.

[0081] [Variation of Second Embodiment] In the second embodiment, when an uplink muting resource pattern overlaps with a DMRS or PT-RS of an actual PUSCH repetition within the same symbol, the REs set as uplink muting resources in the symbols overlapping with the DMRS or PT-RS are not muted. On the other hand, in the PUSCH resources allocated to the actual PUSCH repetition, in symbols not overlapping with the DMRS or PT-RS, the actual PUSCH repetition is transmitted while muting the REs set as uplink muting resources.

[0082] Also in the second embodiment, the threshold value in the third embodiment may be used to determine whether to transmit the actual PUSCH repetition while muting the RE set in the uplink muting resource, to drop the actual PUSCH repetition, or not to mute the RE set in the uplink muting resource.

[0083] [Fourth Embodiment] In this embodiment, a process will be described for the case where, in TBoMS, an uplink muting resource pattern is included in the PUSCH resources in a plurality of slots allocated to TBoMS, resulting in overlapping.

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

[0085] In TBoMS, the same time resource allocation is applied across multiple consecutive slots. The base station notifies the terminal of the time resource allocation within the slot and the number of slots. Here, the number of slots may be a value counted based on consecutive slots or may be a value counted based on uplink slots available for PUSCH transmission.

[0086] In TBoMS, the TBS may be calculated by the following method. The TBS is determined by multiplying the TBS calculated from the amount of resources allocated to PUSCH transmission in the first slot, for example, the number of symbols or the number of resource elements, by a scaling factor greater than 1. For example, the amount of resources (number of resource elements) N_RE allocated to PUSCH transmission in the first slot may be calculated by the following method. for example teeth, where: For example, the number of OFDM symbols allocated to PUSCH transmission in the first slot may be notified to the terminal using information on the symbol length of Time Domain Resource Allocation (TDRA). TB size is the amount of resources allocated to PUSCH transmission in the first slot mentioned above. It may be calculated by the following formula using: where: Note that a scaling factor greater than 1 may be the number of slots allocated to TBoMS. Furthermore, regardless of whether an uplink muting resource is included in the resources allocated to PUSCH transmission in the first slot, TBS may be calculated based on the amount of resources assuming that no uplink muting resource is included.

[0087] In this embodiment, the terminal determines the read start position on the Circular Buffer in each slot of TBoMS as follows: Bit read start position on the Circular Buffer in each slot in TBoMS is the read position corresponding to the notified RV index value in the first slot of multiple slots allocated to TBoMS (see, for example, Table 5.4.2.1-2 in Non-Patent Document 2).

[0088] On the other hand, among the multiple slots allocated to TBoMS, except for the first slot, where, is the bit read start position on the Circular Buffer in the previous slot, H is the number of coding bits available for TB transmission in the previous slot, τ is the number of filler bits skipped in the previous slot (if filler bits exist), is the circular buffer size. Here, the number of coding bits H available for TB transmission in the previous slot is calculated assuming that UCI multiplexing is not performed, regardless of whether UCI is multiplexed or not.

[0089] In this embodiment, of is defined as the set of REs available for data transmission in an OFDM symbol, where does not include subcarriers used for DMRS and PTRS, but does include subcarriers used for uplink muting resources. In TBoMS, the bit read start position in the Circular Buffer is read, and after interleaving and modulation are performed, the data symbols are mapped to a set of REs that can be assigned to data transmission on the PUSCH according to the frequency-first-time-second rule. Then, REs that overlap with uplink muting resources are punctured.

[0090] According to this embodiment, the uplink muting resources are included in the set of REs available for data transmission, and data symbols are mapped to the uplink muting resources. By applying puncturing to the uplink muting resources, the rate matching process is independent of the presence or absence of uplink muting resources. Therefore, the read start bit position on the Circular Buffer when reading coded bits from multiple slots allocated to TBoMS can be determined based on the number of coded bits calculated based on the amount of resources that is independent of the presence or absence of uplink muting resources.

[0091] Fifth Embodiment In this embodiment, a process will be described for the case where, in TBoMS, an uplink muting resource pattern is included in the PUSCH resources in a plurality of slots allocated to TBoMS, resulting in overlapping.

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

[0093] In TBoMS, the same time resource allocation is applied across multiple consecutive slots. The base station notifies the terminal of the time resource allocation within the slot and the number of slots. Here, the number of slots may be a value counted based on consecutive slots or may be a value counted based on uplink slots available for PUSCH transmission.

[0094] In TBoMS, TBS may be calculated using the following method.

[0095] The amount of resources allocated to PUSCH transmission in the first slot, for example, the TBS calculated from the number of symbols or the number of resource elements, is multiplied by a scaling factor greater than 1 to determine the TBS. For example, the amount of resources allocated to PUSCH transmission in the first slot (number of resource elements) may be calculated in the following way: for example, may be calculated by the following formula: where: For example, the number of OFDM symbols allocated to PUSCH transmission in the first slot may be notified to the terminal using information related to the symbol length of time domain resource allocation (TDRA). is.

[0096] TB size is the amount of resources allocated to PUSCH transmission in the first slot mentioned above. It may be calculated by the following formula using where: Note that the scaling factor greater than 1 may be the number of slots allocated to TBoMS.

[0097] Furthermore, regardless of whether or not an uplink muting resource is included in the resources allocated to PUSCH transmission in the first slot, the TBS may be calculated based on the amount of resources that assumes that no uplink muting resource is included.

[0098] In this embodiment, the terminal determines the read start position on the Circular Buffer for each slot of TBoMS as follows.

[0099] In TboMS, the bit read start position on the Circular Buffer for each slot In the first slot of the multiple slots allocated to TBoMS, is the read position corresponding to the notified RV index value (see, for example, Table 5.4.2.1-2 in Non-Patent Document 2). On the other hand, in the multiple slots allocated to TBoMS other than the first slot, where, is the bit read start position on the Circular Buffer in the previous slot, H is the number of coding bits available for TB transmission in the previous slot, τ is the number of filler bits skipped in the previous slot (if filler bits exist), is the circular buffer size. Here, the number of coding bits H available for TB transmission in the previous slot is calculated assuming that UCI multiplexing is not performed, regardless of whether UCI is multiplexed or not.

[0100] In this embodiment, of is defined as the set of REs available for data transmission in an OFDM symbol, where does not include subcarriers used for DMRS and PTRS, but does include subcarriers used for uplink muting resources. In TBoMS, the bit read start position in the Circular Buffer is read, and after interleaving and modulation, the data symbols are mapped to a set of REs that can be assigned to data transmission on the PUSCH in a frequency-first-time-second manner.

[0101] That is, in this embodiment, when TBoMS is applied, REs configured as uplink muting resources are not muted, and therefore, REs configured as uplink muting resources may be regarded as REs available for transmitting data, DMRS, PTRS, or UCI.

[0102] Note that this embodiment may be implemented by disabling the configuration of uplink muting resources when TBoMS is configured for a terminal or when the terminal transmits PUSCH using TBoMS.

[0103] According to this embodiment, since no uplink muting resource is used in TBoMS, the read start bit position on the Circular Buffer when reading coded bits from multiple slots allocated to TBoMS can be determined based on the number of coded bits calculated based on the amount of resources that is independent of the presence or absence of uplink muting resources.Furthermore, since TBoMS can be transmitted regardless of the presence or absence of uplink muting resources, it is possible to suppress performance degradation of PUSCH TBoMS.

[0104] Sixth Embodiment In this embodiment, a process will be described for the case where, in TBoMS, an uplink muting resource pattern is included in the PUSCH resources in a plurality of slots allocated to TBoMS, resulting in overlapping.

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

[0106] In TBoMS, the same time resource allocation is applied across multiple consecutive slots. The base station notifies the terminal of the time resource allocation within the slot and the number of slots. Here, the number of slots may be a value counted based on consecutive slots or may be a value counted based on uplink slots available for PUSCH transmission.

[0107] In TBoMS, TBS may be calculated using the following method.

[0108] The amount of resources allocated to PUSCH transmission in the first slot, for example, the TBS calculated from the number of symbols or the number of resource elements, is multiplied by a scaling factor greater than 1 to determine the TBS. For example, the amount of resources allocated to PUSCH transmission in the first slot (number of resource elements) may be calculated in the following way: for example, may be calculated by the following formula: where: For example, the number of OFDM symbols allocated to PUSCH transmission in the first slot may be notified to the terminal using information related to the symbol length of time domain resource allocation (TDRA). is.

[0109] TB size is the amount of resources allocated to PUSCH transmission in the first slot mentioned above. It may be calculated by the following formula using where: Note that the scaling factor greater than 1 may be the number of slots allocated to TBoMS.

[0110] Furthermore, regardless of whether or not an uplink muting resource is included in the resources allocated to PUSCH transmission in the first slot, the TBS may be calculated based on the amount of resources that assumes that no uplink muting resource is included.

[0111] In this embodiment, the terminal determines the read start position on the Circular Buffer for each slot of TBoMS as follows.

[0112] In TboMS, the bit read start position on the Circular Buffer for each slot In the first slot of the multiple slots allocated to TBoMS, is the read position corresponding to the notified RV index value (see, for example, Table 5.4.2.1-2 in Non-Patent Document 2). On the other hand, in the multiple slots allocated to TBoMS other than the first slot, where, is the bit read start position on the Circular Buffer in the previous slot, H is the number of coding bits available for TB transmission in the previous slot, τ is the number of filler bits skipped in the previous slot (if filler bits exist), is the circular buffer size. Here, the number of coding bits H available for TB transmission in the previous slot is calculated assuming that UCI multiplexing is not performed, regardless of whether UCI is multiplexed or not.

[0113] In this embodiment, of is defined as the set of REs available for data transmission in an OFDM symbol, where does not include subcarriers used for DMRS, PTRS, and uplink muting resources. In TBoMS, the bit read start position on the Circular Buffer is read, and after interleaving and modulation, the data symbols are mapped to a set of REs that can be assigned to data transmission on the PUSCH in a frequency-first-time-second manner.

[0114] Furthermore, in this embodiment, among the slots allocated to TBoMS, the uplink muting resource setting is valid only in the first slot, and the uplink muting resource setting is invalid in slots other than the first slot. In other words, REs set as uplink muting resources are not muted in slots other than the first slot. This means that there are no subcarriers used for the uplink muting resources described above in slots other than the first slot.

[0115] According to this embodiment, among the multiple slots allocated to TBoMS, the read start bit position on the Circular Buffer when reading coded bits can be determined based on the number of coded bits calculated based on the reference resource amount that is independent of the presence or absence of uplink muting resources, except for the first slot. Furthermore, in slots other than the first slot, TBoMS can be transmitted regardless of the presence or absence of uplink muting resources, so that performance degradation of PUSCH TBoMS can be suppressed. Furthermore, the first slot can be used to measure CLI between base stations.

[0116] Seventh Embodiment In this embodiment, a process will be described for the case where, in TBoMS, an uplink muting resource pattern is included in the PUSCH resources in a plurality of slots allocated to TBoMS, resulting in overlapping.

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

[0118] In TBoMS, the same time resource allocation is applied across multiple consecutive slots. The base station notifies the terminal of the time resource allocation within the slot and the number of slots. Here, the number of slots may be a value counted based on consecutive slots or may be a value counted based on uplink slots available for PUSCH transmission.

[0119] In TBoMS, TBS may be calculated using the following method.

[0120] The amount of resources allocated to PUSCH transmission in the first slot, for example, the TBS calculated from the number of symbols or the number of resource elements, is multiplied by a scaling factor greater than 1 to determine the TBS. For example, the amount of resources allocated to PUSCH transmission in the first slot (number of resource elements) may be calculated in the following way: for example, may be calculated by the following formula: where: For example, the number of OFDM symbols allocated to PUSCH transmission in the first slot may be notified to the terminal using information on the symbol length of Time Domain Resource Allocation (TDRA). is.

[0121] TB size is the amount of resources allocated to PUSCH transmission in the first slot mentioned above. It may be calculated by the following formula using where: Note that the scaling factor greater than 1 may be the number of slots allocated to TBoMS.

[0122] Furthermore, regardless of whether or not an uplink muting resource is included in the resources allocated to PUSCH transmission in the first slot, the TBS may be calculated based on the amount of resources that assumes that no uplink muting resource is included.

[0123] In this embodiment, the terminal determines the read start position on the Circular Buffer for each slot of TBoMS as follows.

[0124] In TboMS, the bit read start position on the Circular Buffer for each slot In the first slot of the multiple slots allocated to TBoMS, is the read position corresponding to the notified RV index value (see, for example, Table 5.4.2.1-2 in Non-Patent Document 2). On the other hand, in the multiple slots allocated to TBoMS other than the first slot, where, is the bit read start position on the Circular Buffer in the previous slot, H is the number of coding bits available for TB transmission in the previous slot, τ is the number of filler bits skipped in the previous slot (if filler bits exist), is the circular buffer size. Here, the number H of coding bits available for TB transmission in the previous slot is calculated assuming that UCI multiplexing is not performed, regardless of whether UCI is multiplexed or not. Also, the number H of coding bits available for TB transmission in the previous slot is calculated assuming that uplink resource muting is not performed, regardless of whether uplink muting resources are available.

[0125] In this embodiment, of is defined as the set of REs available for data transmission in an OFDM symbol, where does not include subcarriers used for DMRS, PTRS, and uplink muting resources. In TBoMS, data symbols are read from the bit read start position in the Circular Buffer, interleaved, and modulated, and then mapped to a set of REs that can be assigned to data transmission on the PUSCH in a frequency-first-time-second manner (i.e., mapping is performed taking into account uplink muting resources).

[0126] According to this embodiment, the read start bit position on the circular buffer when reading coded bits from multiple slots allocated to TBoMS can be determined based on the number of coded bits calculated based on the reference resource amount that is independent of the presence or absence of uplink muting resources.In addition, CLI between base stations can be measured in TBoMS as well.

[0127] [Sequence Diagram] FIG. 16 is a sequence diagram relating to PUSCH repetition Type B.

[0128] The base station transmits settings related to PUSCH transmission and uplink muting resources to the terminal (step S1601).

[0129] The base station transmits scheduling information of PUSCH repetition Type B to the terminal (step S1602).

[0130] The terminal determines the actual PUSCH repetition resource (step S1603).

[0131] The terminal determines whether the Actual PUSCH repetition resources include an uplink muting resource (step S1604).

[0132] If the actual PUSCH repetition resources include uplink muting resources (step S1604, Yes), the terminal determines whether to transmit the actual PUSCH repetition resources or whether to apply uplink muting resources (step S1605), and transmits PUSCH repetition Type B in accordance with the determination made in step S1605 (the modified resources determined in step S1603) (step S1606).

[0133] If the Actual PUSCH repetition resources do not include an uplink muting resource (step S1604, No), the terminal transmits PUSCH repetition Type B in accordance with the resources determined in step S1603 (step S1607).

[0134] 17 is a sequence diagram relating to TBoMS. The base station transmits settings relating to PUSCH transmission and uplink muting resources to the terminal (step S1701).

[0135] The base station transmits TBoMS scheduling information to the terminal (step S1702).

[0136] The terminal determines the TBoMS resource (step S1703).

[0137] The terminal determines whether the TBoMS resources include an uplink muting resource (step S1704).

[0138] If the TBoMS resources include uplink muting resources (step S1704, Yes), the terminal determines the transmission method of the TBoMS resources or whether or not to apply the uplink muting resources (step S1705), and transmits the TBoMS according to the determination made in step S1705 (the modified resource determined in step S1703) (step S1706).

[0139] If the TBoMS resources do not include an uplink muting resource (step S1704, No), the terminal transmits the TBoMS in accordance with the resource determined in step S1603 (step S1707).

[0140] 18 is a block diagram showing a detailed example configuration of a part of a base station 1000 according to one aspect of the present disclosure.

[0141] The base station 1000 includes a receiving unit 1801, an extracting unit 1802, a demodulating unit 1803, a decoding unit 1804, a control unit 1805, a downlink control information generating unit 1806, a higher control signal generating unit 1807, an encoding unit 1808, a modulating unit 1809, a signal allocating unit 1810, and a transmitting unit 1811. At least one of the extracting unit 1802, the demodulating unit 1803, the decoding unit 1804, the control unit 1805, the downlink control information generating unit 1806, the higher control signal generating unit 1807, the encoding unit 1808, the modulating unit 1809, and the signal allocating unit 1810 may be configured as a control circuit 1812. The receiving unit 1801 may be configured as a receiving circuit, and the transmitting unit 1811 may be configured as a transmitting circuit.

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

[0143] Based on information received from the control unit 1805 , the extraction unit 1802 extracts the radio resource portion on which the PUSCH is transmitted from the received signal input from the receiving unit 1801 , and outputs them to the demodulation unit 1803 .

[0144] The demodulation section 1803 demodulates the PUSCH based on information received from the control section 1805 and outputs the demodulation result to the decoding section 1804 .

[0145] The decoding unit 1804 performs error correction decoding on the PUSCH using information received from the control unit 1805 and the demodulation result obtained from the demodulation unit 1803, and obtains a decoded received bit string. The received bit string may be a UL data signal.

[0146] The control unit 1805 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 1806 or the higher control signal generation unit 1807. The control unit 1805 determines the coding / modulation scheme and radio resource allocation for the terminal to transmit the uplink data signal. The control unit 1805 outputs the determined information to the downlink control information generation unit 1806, extraction unit 1802, demodulation unit 1803, and decoding unit 1804.

[0147] The control unit 1805 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 1802, the demodulation unit 1803, and the decoding unit 1804.

[0148] In addition, the control unit 1805 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 1808, the modulation unit 1809, and the signal allocation unit 1810.

[0149] The control unit 1805 determines information related to PDSCH reception and information related to PUSCH transmission for the terminal, and outputs the determined information to the downlink control information generation unit 1806 or the higher control signal generation unit 1807. 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.

[0150] The control unit 1805 outputs coding and modulation methods for data signals and higher-level control signals and radio resource allocation information to the downlink control information generation unit 1806. The control unit 1805 determines the configuration of muting resources (e.g., allocation patterns of muting resources) and outputs the determined information to the higher-level control signal generation unit 1807.

[0151] The downlink control information generating section 1806 generates a DCI bit string using the control information input from the control section 1805, and outputs the generated DCI bit string to the encoding section 1808. Note that the control information may be transmitted to multiple terminals.

[0152] The higher-level control signal generating section 1807 generates a higher-level layer control signal bit string using the control information input from the control section 1805 , and outputs the generated higher-level layer control signal bit string to the encoding section 1808 .

[0153] The encoding unit 1808 encodes the downlink data, the bit string obtained from the higher control signal generating unit 1807, or the DCI bit string input from the downlink control information generating unit 1806 based on the encoding method input from the control unit 1805, and outputs the encoded bit string to the modulation unit 1809.

[0154] The modulation unit 1809 modulates the coded bit string received from the coding unit 1808 based on the modulation method input from the control unit 1805 and outputs the modulated bit string to the signal allocation unit 1810 .

[0155] The signal allocation unit 1810 maps the downlink data signal or control signal input as a symbol sequence from the modulation unit 1809 to the radio resources instructed by the control unit 1805. The signal allocation unit 1810 also inputs the mapped signal to the transmission unit 1811.

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

[0157] [Configuration of Terminal] The configuration of the terminal will be described. Fig. 19 is a block diagram showing a detailed configuration example of a portion of a terminal 1100 according to one aspect of the present disclosure. The terminal 1100 includes a receiving unit 1901, an extracting unit 1902, a demodulating unit 1903, a decoding unit 1904, a control unit 1905, an encoding unit 1906, a modulating unit 1907, a signal allocating unit 1908, and a transmitting unit 1909. At least one of the extracting unit 1902, the demodulating unit 1903, the decoding unit 1904, the control unit 1905, the encoding unit 1906, the modulating unit 1907, and the signal allocating unit 1908 may be configured as a control circuit 1910. The receiving unit 1901 may be configured as a receiving circuit, and the transmitting unit 1909 may be configured as a transmitting circuit.

[0158] The receiving unit 1901 receives a data signal or a downlink control signal transmitted from the base station 1000 via an antenna, performs RF processing such as down-conversion or A / D conversion on the radio received signal to obtain a baseband signal, and outputs the baseband signal to the extracting unit 1902. When receiving an OFDM signal, the receiving unit 1901 also performs FFT processing on the received signal, converts the received signal into the frequency domain, and outputs the signal to the extracting unit 1902.

[0159] Extraction section 1902 extracts a radio resource portion including a downlink control signal from the received signal received from receiving section 1901, using information related to the radio resource of the control signal input from control section 1905, and outputs the extracted radio resource portion to demodulation section 1903. Extraction section 1902 also extracts a radio resource portion including a data signal, using information related to the radio resource of the data signal input from control section 1905, and outputs the extracted radio resource portion to demodulation section 1903.

[0160] The demodulation section 1903 demodulates the PDCCH or PDSCH based on information received from the control section 1905 and outputs the demodulation result to the decoding section 1904 .

[0161] The decoder 1904 performs error correction decoding of the PDCCH or PDSCH using the information received from the controller 1905 and the demodulation result obtained from the demodulator 1903, 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 1905. The decoder may also generate an ACK / NACK signal from the decoding result of the downlink reception data.

[0162] The control unit 1905 specifies radio resources for PDSCH reception, PUSCH transmission, and uplink muting resources from radio resource allocation information obtained from the higher layer control signal and downlink control information. The control unit 1905 also outputs the determined information to the signal allocation unit 1908, the extraction unit 1902, and the demodulation unit 1903.

[0163] The control unit 1905 determines whether the radio resources for transmitting uplink data include an uplink muting resource, and if so, identifies the radio resource on the PUSCH and outputs the identified radio resource to the encoding unit 1906, the modulation unit 1907, and the signal allocation unit 1908.

[0164] The encoding unit 1906 encodes the uplink data signal based on the information input from the control unit 1905 and outputs the encoded bit string to the modulation unit 1907 .

[0165] The modulation unit 1907 modulates the coded bit sequence received from the coding unit 1906 based on the modulation scheme input from the control unit 1905 to generate a modulated symbol sequence, and outputs it to the signal allocation unit 1908 .

[0166] The signal allocation unit 1908 maps the signal input from the modulation unit 1907 to radio resources instructed by the control unit 1905. Furthermore, the signal allocation unit 1908 inputs the mapped signal to the transmission unit 1909. Note that when generating a single-carrier waveform, a DFT unit may be added after the modulation unit 1907 or before the signal allocation unit 1908.

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

[0168] The transmitter 1909 also performs RF processing such as D / A conversion and up-conversion on the transmission signal, and transmits the radio signal to the base station 1000 via an antenna.

[0169] (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 1100 to the base station 1000, for example, as capability information or capability parameters of the terminal 1100.

[0170] The capability information may include an information element (IE) that individually indicates whether or not the terminal 1100 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 1100 supports a combination of any two or more of the functions, operations, or processes described in the above-described embodiments, modifications, and supplements.

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

[0172] Note that the fact that terminal 1100 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 1100. For example, information or a request regarding such restrictions may be notified to base station 1000.

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

[0174] (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.

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

[0176] (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.

[0177] (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.

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

[0179] (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.

[0180] (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).

[0181] (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.

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

[0183] (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), Vehicle to Everything (V2X) communication, or communication between an Ambient IoT Reader and an Ambient IoT Device. 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, PRDCH (Physical Reader-to-Device Channel), PDRCH (Physical Device-to-Reader Channel), PDCCH, PUCCH, PDSCH, PUSCH, or PBCH. For example, the control information in an embodiment of the present disclosure may be replaced with any of DCI, UCI, SCI (Sidelink Control Information), R2D Control Information, and D2R Control Information. For example, the terminal and base station in an embodiment of the present disclosure may be replaced with an Ambient IoT Device or an Ambient IoT Reader. The Ambient IoT Device may be a wireless communication device with a backscattering function or a transmission / reception bandwidth of several resource blocks or less. The Ambient IoT Reader may be a wireless communication device with a communication function with the Ambient IoT Device. The Ambient IoT Device may also be called an Ambient IoT terminal, IoT terminal, LPWA terminal, or tag.

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

[0185] (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.

[0186] 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).

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

[0188] (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).

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

[0190] (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.

[0191] <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 the Next Generation Core (NGC) via a Next Generation (NG) interface, more specifically to the Access and Mobility Management Function (AMF) (e.g., a specific core entity that performs AMF) via an NG-C interface, and to the 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 20 (see, for example, 3GPP TS 38.300 v15.6.0, section 4).

[0192] <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).

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

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

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

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

[0197] (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).

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

[0199] 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."

[0200] 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 each 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

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

[0202] Figure 21 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.

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

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

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

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

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

[0208] 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).

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0223] (1) A terminal according to one embodiment of the present disclosure includes a control circuit that controls transmission of the uplink signal based on a resource of the uplink signal and the time position of the uplink muting resource, and a transmitting unit that transmits the uplink signal.

[0224] (2) In a terminal according to an embodiment of the present disclosure, in the terminal of (1), the uplink signal is a signal that transmits PUSCH repetition Type B.

[0225] (3) In a terminal according to an embodiment of the present disclosure, in the terminal of (2), the control circuit controls transmission of the uplink signal based on at least one of: an amount of PUSCH resources allocated to an actual PUSCH repetition excluding the uplink muting resources; an amount of the uplink muting resources on the PUSCH resources allocated to the actual PUSCH repetition; a ratio between the amount of PUSCH resources allocated to the actual PUSCH repetition and the amount of uplink muting resources; and a coding rate of a PUSCH calculated using the amount of PUSCH resources allocated to the actual PUSCH repetition excluding the uplink muting resources.

[0226] (4) In a terminal according to one embodiment of the present disclosure, in the terminal of (2), when the uplink muting resource overlaps with a DMRS or PTRS resource of an actual PUSCH repetition within the same symbol, the control circuit drops the actual PUSCH repetition where the overlap occurs.

[0227] (5) In a terminal according to one embodiment of the present disclosure, in the terminal of (2), the control circuit does not mute the resource set as the uplink muting resource when the uplink muting resource overlaps with a DMRS or PTRS resource of an actual PUSCH repetition within the same symbol.

[0228] (6) In a terminal according to one embodiment of the present disclosure, in the terminal of (2), when the uplink muting resource overlaps with a DMRS or PTRS resource of an actual PUSCH repetition within the same symbol, the control circuit drops the resource of the actual PUSCH repetition where the overlap occurs and transmits the resource of the actual PUSCH repetition where no overlap occurs.

[0229] (7) In a terminal according to an embodiment of the present disclosure, in the terminal of (2), when the uplink muting resource overlaps with a DMRS or PTRS resource of an actual PUSCH repetition within the same symbol, and when an amount of PUSCH resources allocated to the actual PUSCH repetition excluding the uplink muting resource is less than a threshold, the control circuit drops the actual PUSCH repetition.

[0230] (8) In a terminal according to one embodiment of the present disclosure, in the terminal of (1), the uplink signal is a signal that transmits Transport Block processing over Multiple Slots (TBoMS).

[0231] (9) In a terminal according to an embodiment of the present disclosure, in the terminal of (8), the control circuit punctures the TBoMS resources that overlap with the uplink muting resources.

[0232] (10) In a terminal according to an embodiment of the present disclosure, in the terminal of (8), the control circuit does not puncture the TBoMS resources that overlap with the uplink muting resources.

[0233] (11) In a terminal according to one embodiment of the present disclosure, in the terminal of (8), the control circuit punctures the TBoMS resource of the first slot that overlaps with the uplink muting resource, and does not puncture the TBoMS resource other than the first slot.

[0234] (12) In a terminal according to one embodiment of the present disclosure, in the terminal of (8), the control circuit assumes that the uplink resource muting is not performed, calculates the read start position on the Circular Buffer in which the uplink signal is stored for each slot of the TBoMS, and performs mapping taking into account the uplink muting resource.

[0235] (13) A base station according to one embodiment of the present disclosure includes a control circuit that controls reception of an uplink signal based on a resource of the uplink signal and a time position of the uplink muting resource, and a transmitting unit that receives the uplink signal.

[0236] (14) A transmission method according to one embodiment of the present disclosure controls transmission of an uplink signal based on a resource of the uplink signal and a time position of an uplink muting resource, and transmits the uplink signal.

[0237] (15) A receiving method according to one embodiment of the present disclosure controls reception of an uplink signal based on a resource of the uplink signal and a time position of an uplink muting resource, and receives the uplink signal.

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

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

[0240] 1000 Base Station 1100 Terminal 1801, 1901 Receiving section 1802, 1902 Extracting section 1803, 1903 Demodulating section 1804, 1904 Decoding section 1805, 1905 Control section 1806 Downlink control information generating section 1807 Upper control signal generating section 1808, 1906 Encoding section 1809, 1907 Modulating section 1810, 1908 Signal allocating section 1811, 1909 Transmitting section 1812, 1910 Control circuit

Claims

1. A terminal comprising: a control circuit that controls transmission of an uplink signal based on a resource of the uplink signal and a time position of an uplink muting resource; and a transmission unit that transmits the uplink signal.

2. The terminal according to claim 1, wherein the uplink signal is a signal that transmits a PUSCH repetition Type B.

3. The terminal according to claim 2, wherein the control circuit controls transmission of the uplink signal based on at least one of: an amount of PUSCH resources allocated to an actual PUSCH repetition excluding the uplink muting resources; an amount of the uplink muting resources on the PUSCH resources allocated to the actual PUSCH repetition; a ratio between the amount of PUSCH resources allocated to the actual PUSCH repetition and the amount of uplink muting resources; and a coding rate of a PUSCH calculated using the amount of PUSCH resources allocated to the actual PUSCH repetition excluding the uplink muting resources.

4. The terminal according to claim 2, wherein, when the uplink muting resource overlaps with a DMRS or PTRS resource of an actual PUSCH repetition within the same symbol, the control circuit drops the actual PUSCH repetition in which the overlap occurs.

5. The terminal according to claim 2, wherein the control circuit does not mute the resource set as the uplink muting resource when the uplink muting resource overlaps with a DMRS or PTRS resource of an actual PUSCH repetition within the same symbol.

6. The terminal according to claim 2, wherein, when the uplink muting resource overlaps with a DMRS or PTRS resource of an actual PUSCH repetition within the same symbol, the control circuit drops the resource of the actual PUSCH repetition where the overlap occurs and transmits the resource of the actual PUSCH repetition where no overlap occurs.

7. The terminal according to claim 2, wherein when the uplink muting resource overlaps with a DMRS or PTRS resource of an actual PUSCH repetition within the same symbol, the control circuit drops the actual PUSCH repetition if an amount of PUSCH resources allocated to the actual PUSCH repetition excluding the uplink muting resource is less than a threshold.

8. The terminal according to claim 1, wherein the uplink signal is a signal that transmits Transport Block Processing over Multiple Slots (TBoMS).

9. The terminal of claim 8, wherein the control circuitry punctures resources of the TBoMS that overlap with the uplink muting resources.

10. The terminal of claim 8, wherein the control circuitry does not puncture resources of the TBoMS that overlap with the uplink muting resources.

11. The terminal according to claim 8, wherein the control circuit punctures the TBoMS resource in the first slot that overlaps with the uplink muting resource, and does not puncture the TBoMS resource in slots other than the first slot.

12. The terminal according to claim 8, wherein the control circuit calculates a read start position on a circular buffer in which the uplink signal is stored for each slot of the TBoMS, assuming that the uplink resource muting is not performed, and performs mapping taking the uplink muting resource into consideration.

13. A base station comprising: a control circuit that controls reception of an uplink signal based on a resource of the uplink signal and a time position of an uplink muting resource; and a transmitter that receives the uplink signal.

14. A transmission method, comprising: controlling transmission of an uplink signal based on a resource of the uplink signal and a time position of an uplink muting resource; and transmitting the uplink signal.

15. A receiving method, comprising: controlling reception of an uplink signal based on a resource of the uplink signal and a time position of an uplink muting resource; and receiving the uplink signal.

Images