Communication device, base station, communication method, and integrated circuit

Abstract

The present invention appropriately performs uplink signal transmission. In the present invention, a terminal comprises: a control circuit that, when the transmission timing of uplink control information and the transmission timing of an uplink data signal to which an orthogonal code is applied overlap, controls the transmission of the uplink data signal in time resources in at least part of a section to which the orthogonal code is applied; and a transmission circuit that, in accordance with the control of the transmission of the uplink data signal, transmits the uplink control information and the uplink data signal.

Description

Communication device, base station, communication method, and integrated circuit

[0001] The present disclosure relates to a communication device, a base station, a communication method, and an integrated circuit.

[0002] New Radio access technology (NR) for 5G has been specified by 3GPP, and specifications up to Release 18 (Rel.18) of NR have been published.

[0003] 3GPP, TR 38.821, V16.1.0 “Solutions for NR to support non-terrestrial networks (NTN) (Release 16)”3GPP, TS 38.214, V18.1.0 “NR; Physical layer procedures for data (Release 18)”

[0004] However, there is room for further consideration regarding the method of transmitting the upstream signal.

[0005] Non-limiting embodiments of the present disclosure contribute to providing a communication device, a base station, a communication method, and an integrated circuit that can appropriately transmit an uplink signal.

[0006] A terminal according to one embodiment of the present disclosure includes a control circuit that controls, when the transmission timing of uplink control information overlaps with the transmission timing of an uplink data signal to which an orthogonal code is applied, the transmission of the uplink data signal in at least a portion of the time resources of the section to which the orthogonal code is applied, and a transmission circuit that transmits the uplink control information and the uplink data signal in accordance with the control of the transmission of the uplink data 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] According to an embodiment of the present disclosure, uplink signals can be transmitted appropriately.

[0009] Further advantages and benefits of an embodiment of the present disclosure will become apparent from the specification and drawings. Such advantages and / or benefits may be provided by some of the 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] 1. Block diagram showing an example of the configuration of a portion of a terminal. 2. Block diagram showing an example of the configuration of a portion of a base station. 3. Block diagram showing an example of the configuration of a terminal. 4. Block diagram showing an example of the configuration of a base station. 5. Diagram showing an example of a transmission method for PUSCH (Physical Uplink Shared Channel). 6. Diagram showing an example of a transmission method for PUSCH. 7. Diagram showing an example of a transmission method for PUSCH. 8. Diagram showing an example of a transmission method for PUSCH. 9. Diagram showing an example of a transmission method for PUSCH. 10. Diagram showing an example of a transmission method for PUSCH. 11. Diagram showing an example of a transmission method for PUSCH. 12. Diagram showing an example of a transmission method for PUSCH. 13. Diagram showing an example of a transmission method for PUSCH. 14. Diagram showing an example of a transmission method for PUSCH. 15. Diagram showing an example of a transmission method for PUSCH.

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

[0012] <Regarding Non-Terrestrial Networks (NTNs)> NR Rel. 15 is specified as a radio access technology for terrestrial networks. On the other hand, NR is being considered for extension to non-terrestrial networks (NTNs), such as communications using satellites or high-altitude platform stations (HAPSs) (see, for example, Non-Patent Document 1).

[0013] In the case of communications via satellite, the distance between the satellite and the terminal (also called user equipment (UE)) is long, which means that propagation attenuation is likely to be large. To achieve a sufficiently high reception quality at the satellite, it is expected that the terminal will use a method such as repeatedly transmitting multiple pieces of data (e.g., repetition transmission).

[0014] In an NTN environment, satellite coverage areas (e.g., one or more cells) for terminals located on the ground, in the sky, such as aircraft or drones, or at sea are formed by beams from the satellite (also called satellite beams). The size of a single beam on the Earth's surface can be, for example, 50 to 1,000 km in diameter. For this reason, NTNs are expected to accommodate a large number of terminals.

[0015] Therefore, for example, for the Physical Uplink Shared Channel (PUSCH) used for uplink data transmission, studies are being conducted to increase the number of terminals that can be accommodated by multiplying repeatedly transmitted data by orthogonal codes (e.g., orthogonal cover codes (OCCs)) that differ between terminals and multiplexing the data onto the same time-frequency resources.

[0016] Three methods of applying OCC are under consideration: (1) "Inter-slot OCC," (2) "Inter-symbol OCC," and (3) "Intra-symbol OCC."

[0017] In inter-slot OCC, PUSCHs between terminals are made orthogonal in units of multiple slots by multiplying by OCC when repetition is performed in units of slots.

[0018] Inter-symbol OCC makes PUSCHs between terminals orthogonal in units of multiple symbols by multiplying by OCC when repetition is performed between OFDM (Orthogonal Frequency Division Multiplexing) symbols.

[0019] Intra-symbol OCC, the modulation symbols before DFT spreading are replicated in the DFT (Discrete Fourier Transform)-S (spread)-OFDM signal generation process and multiplied by OCC, thereby orthogonalizing the PUSCHs between terminals in units of multiple modulation symbols.

[0020] In NR, HARQ-ACK information, SR (Scheduling Request) information, or CSI (Channel State Information) feedback information is called uplink control information (UCI) and is transmitted on an uplink control channel (e.g., PUCCH (Physical Uplink Control Channel)). For example, when the transmission timing of the PUSCH and the transmission timing of the UCI collide (or overlap), the PUSCH data and the UCI are multiplexed and transmitted in the PUSCH. Furthermore, when the PUSCH is transmitted in a repetitive manner, the UCI is multiplexed with the data and transmitted in the first slot of multiple slots in which the PUSCH is transmitted in a repetitive manner.

[0021] In the case of inter-slot OCC, if UCI is transmitted (multiplexed) in the first slot of multiple slots to which OCC is applied, the transmission data in the first slot and the subsequent slots in the multiple slots to which OCC is applied are different, which may cause orthogonality to be lost. Thus, there is room for consideration regarding operation when PUSCH and UCI collide when OCC is applied.

[0022] In a non-limiting embodiment of the present disclosure, a method for suppressing a loss of orthogonality between terminals transmitting a PUSCH to which OCC is applied and suppressing degradation of reception performance when a PUSCH and UCI collide when OCC is applied will be described. For example, in a non-limiting embodiment of the present disclosure, when a UCI transmission timing and a PUSCH transmission timing to which OCC is applied collide, a terminal does not transmit a PUSCH in all or some slots in an OCC-applied interval. This makes it possible to reduce a loss of orthogonality between terminals due to OCC when transmitting UCI.

[0023] [Overview of Communication System] A communication system according to an embodiment of the present disclosure includes a terminal 100 and a base station 200.

[0024] Fig. 1 is a block diagram showing a partial configuration example of a terminal 100. In the terminal 100 shown in Fig. 1, a control unit (e.g., corresponding to a control circuit) controls transmission of an uplink data signal in at least some time resources (e.g., slots) of a section to which an orthogonal code (e.g., OCC) is applied when the transmission timing of uplink control information (e.g., UCI) overlaps with the transmission timing of an uplink data signal (e.g., PUSCH) to which an orthogonal code (e.g., OCC) is applied. A communication unit (e.g., corresponding to a transmission circuit) transmits the uplink control information and the uplink data signal in accordance with the control of the transmission of the uplink data signal.

[0025] 2 is a block diagram showing a partial configuration example of a base station 200. In the base station 200 shown in FIG. 2, when the transmission timing of uplink control information (e.g., UCI) overlaps with the transmission timing of an uplink data signal (e.g., PUSCH) to which an orthogonal code (e.g., OCC) is applied, a control unit (e.g., corresponding to a control circuit) performs reception control of the uplink data signal, assuming transmission of the uplink data signal in at least some time resources (e.g., slots) of the section to which the orthogonal code is applied (OCC section). A communication unit (e.g., corresponding to a receiving circuit) receives the uplink control information and the uplink data signal in accordance with the reception control.

[0026] (Embodiment 1) In this embodiment, when a collision occurs between UCI transmission timing and PUSCH transmission timing to which OCC is applied, terminal 100 stops (for example, drops or postpones) PUSCH transmission at least in slots following the collision slot within an OCC interval (a time interval to which one OCC sequence is applied).

[0027] 3 is a block diagram showing an example of the configuration of terminal 100 according to embodiment 1. Terminal 100 has radio receiving section 101, data reception processing section 102, control section 103, data transmission processing section 104, and radio transmitting section 105.

[0028] At least one of the data reception processing unit 102, the control unit 103, and the data transmission processing unit 104 shown in Fig. 3 may be included in the control unit shown in Fig. 1. Also, at least one of the wireless reception unit 101 and the wireless transmission unit 105 shown in Fig. 3 may be included in the communication unit shown in Fig. 1.

[0029] The radio receiving section 101 performs analog receiving processing and digital receiving processing such as down-conversion, A / D conversion, and filtering on a signal received from the base station 200 via an antenna, and outputs the processed signal to the data receiving processing section 102 .

[0030] The data reception processing unit 102 demodulates and decodes downlink signals such as SSB (Synchronization Signal (SS) / Physical Broadcast Channel (PBCH) Block), downlink control channels (e.g., PDCCH: Physical Downlink Control Channel), and downlink shared channels (e.g., PDSCH: Physical Downlink Shared Channel) output from the radio reception unit 101.

[0031] The SSB includes, for example, a synchronization signal and broadcast information to the entire cell.

[0032] The PDSCH may include, in addition to user data, broadcast information such as system information, RRC (Radio Resource Control) control information, MAC CE (Medium Access Control Control Element) control information, RACH (Random Access Channel) responses (e.g., Msg2), TA (Timing Advance) commands, and the like. Furthermore, the data reception processing unit 102 performs reception processing of RRC control information (e.g., an RRC Reconfiguration message, etc.), and outputs the RRC control information to the control unit 103. The RRC control information may include, for example, information regarding the number of slots, or information regarding DMRS bundling. The information regarding the number of slots may be, for example, at least one of the number of slots to be transmitted in repetition, the number of repetitions, and the number of slots to which one TB (Transport Block) is mapped (e.g., the number of slots to be transmitted in TBoMS (Transport Block processing over Multiple Slots)). Furthermore, the information regarding DMRS bundling may include, for example, information regarding TDW (Time Domain Window). Furthermore, the information may be included in MAC CE or Msg.2 transmitted in the PDSCH. The system information may also include information related to time / frequency synchronization such as satellite ephemeris, common TA parameters, Epoch time, etc. The data reception processing unit 102 may output this control information included in the PDSCH to the control unit 103.

[0033] The PDCCH includes, for example, resource allocation information for the PDSCH, resource allocation information for the PUSCH, and resource allocation information for the PUCCH used for HARQ-ACK transmission for the PDSCH.

[0034] Furthermore, the PDSCH or PDCCH may include, for example, information regarding an OCC sequence length, an OCC sequence, or a port of a demodulation reference signal (e.g., a DMRS port). Furthermore, the PDSCH or PDCCH may include, for example, information regarding the transmission timing of UCI. The UCI may include, for example, HARQ-ACK, SR, and CSI feedback.

[0035] The control unit 103 may acquire location information of the terminal 100 from a Global Navigation Satellite System (GNSS) or the like. The control unit 103 may also calculate the orbit and position of a satellite based on information such as satellite ephemeris and epoch time input from the data reception processing unit 102. The control unit 103 may calculate a timing adjustment value (TA value) using a round-trip delay time between the terminal 100 and the satellite calculated from the location information, a round-trip delay time between the satellite and the base station calculated from common TA parameters, and information on a TA command notified from the base station 200, and output the TA value to the wireless transmission unit 105.

[0036] The control unit 103 may calculate the Doppler shift based on the satellite orbit information and the terminal position information of the terminal 100 and output it to the radio transmission unit 105 .

[0037] Here, in a time interval (OCC interval) in which multiplication by a certain OCC sequence is applied, it may be desirable to maintain continuity of phase and amplitude (or power) in order to maintain orthogonality of the OCC-applied signal. For this reason, the control unit 103 may adjust the transmission timing or frequency at timings other than the time interval in which multiplication by a certain OCC sequence is applied.

[0038] Control unit 103 outputs information related to the OCC, information related to the number of slots, and information related to the OCC sequence number or DMRS port input from data reception processing unit 102 to data transmission processing unit 104. Control unit 103 also outputs information related to the time / frequency resources for PUSCH transmission notified from base station 200 (input from data reception processing unit 102 to control unit 103) to data transmission processing unit 104.

[0039] In addition, the control unit 103 may output information on OCC-related capabilities (UE capability), such as the corresponding OCC sequence length, or on capabilities related to UCI multiplexing to the data transmission processing unit 104 (transmitting this as UE capability via an RRC message), taking into consideration, for example, the supported functions or performance of the data transmission processing unit 104 and the radio transmission unit 105 of the terminal 100.

[0040] Furthermore, the control unit 103 generates UCI and outputs it to the data transmission processing unit 104 at a timing based on information about the UCI transmission timing notified from the base station 200 .

[0041] The data transmission processing unit 104 may perform coding such as LDPC (Low Density Parity Check) on the transmission data, modulation such as QPSK and 16QAM (Quadrature Amplitude Modulation), DFT-s-OFDM modulation processing, and mapping to time / frequency resources based on information about the PUSCH resource, OCC sequence length, OCC sequence number information, or slot number information input from the control unit 103. Furthermore, the data transmission processing unit 104 may perform data repetition and OCC multiplication based on information about the OCC and information about the slot number. Furthermore, the data transmission processing unit 104 may multiplex UCI and data and transmit the PUSCH at the UCI transmission timing.

[0042] However, if the UCI transmission timing and the PUSCH transmission timing to which OCC is applied overlap (or collide), the data transmission processing unit 104 does not transmit the PUSCH in one or more slots within the OCC interval (for example, determines to stop transmission). Note that an example of the operation when the UCI transmission timing and the PUSCH transmission timing to which OCC is applied overlap will be described later.

[0043] Furthermore, the data transmission processing unit 104 may generate a DMRS based on information relating to the antenna port or DMRS port input from the control unit 103 and output the DMRS to the radio transmission unit 105 .

[0044] The radio transmitting unit 105 performs analog transmission processing and digital transmission processing such as D / A conversion, filtering, up-conversion, and amplification on the signal input from the data transmission processing unit 104, and transmits the radio signal from an antenna. The radio transmitting unit 105 may perform either or both of timing adjustment and frequency correction based on timing information (e.g., TA information) and a frequency correction value input from the control unit 103.

[0045] 4 is a block diagram showing an example of the configuration of base station 200 according to this embodiment. Base station 200 has radio receiving section 201, data reception processing section 202, control section 203, data transmission processing section 204, and radio transmitting section 205.

[0046] At least one of the data reception processing unit 202, the control unit 203, and the data transmission processing unit 204 shown in Fig. 4 may be included in the control unit shown in Fig. 2. Also, at least one of the wireless reception unit 201 and the wireless transmission unit 205 shown in Fig. 4 may be included in the communication unit shown in Fig. 2.

[0047] The radio receiving section 201 performs analog and digital receiving processes such as down-conversion, A / D conversion, and filtering on the signal received from the terminal 100 via the antenna, and outputs the processed signal to the data receiving processing section 202 .

[0048] The data reception processing unit 202 performs channel estimation and demodulation / decoding processing on uplink signals such as the PUSCH, PUCCH, and PRACH input from the radio receiving unit 201 to obtain a received data sequence. When receiving a PUSCH to which OCC is applied, the data reception processing unit 202 may perform despreading processing (e.g., adding signals multiplied by the complex conjugate or reciprocal of the OCC sequence) in accordance with the OCC sequence or OCC sequence number set by the control unit 203. When the despreading interval of one OCC sequence spans multiple slots, the data reception processing unit 202 may perform joint channel estimation using DMRSs of multiple slots.

[0049] Furthermore, the data reception processing unit 202 may assume that UCI is multiplexed onto the PUSCH at the UCI transmission timing of each terminal 100. In this case, the data reception processing unit 202 obtains a received data sequence and UCI after reception processing. Furthermore, for example, when the UCI transmission timing overlaps with the PUSCH transmission timing to which OCC is applied, the data reception processing unit 202 may assume that the PUSCH will be dropped and receive the UCI on the PUCCH. For example, the data reception processing unit 202 may perform reception control assuming an operation (such as stopping PUSCH transmission) when UCI and PUSCH collide in the terminal 100. Note that an example of reception processing of the PUSCH and UCI when OCC is applied will be described later.

[0050] Furthermore, the data reception processing unit 202 outputs the RRC message and MAC CE data included in the PUSCH to the control unit 203. The RRC message may include, for example, information on terminal capabilities related to OCC or terminal capabilities related to UCI multiplexing when OCC is applied.

[0051] The control unit 203 generates system information (broadcast information) such as a master information block (MIB) and a system information block (SIB), and control information such as terminal-specific control information (RRC message). The system information may include, for the NTN, information such as satellite ephemeris information, common TA parameters used for terminal TA, and epoch time. The RRC message may also include, for example, information related to OCC, such as an OCC sequence length or an OCC number, information related to the number of slots to be transmitted in repetition or the number of slots for TBoMS, information related to DMRS bundling, and information related to UCI transmission timing.

[0052] The control unit 203 generates downlink control information (DCI) or a PDCCH associated with PDSCH transmission. The DCI may include, for example, information related to PDSCH retransmission control, such as a new data indicator (NDI) and a redundancy version (RV), information related to the modulation and coding scheme (MCS) of the PDSCH and the PUSCH, resource allocation information for the PDSCH and the PUSCH, resource allocation information for the PUCCH used for HARQ-ACK transmission for the PDSCH, or information related to the transmission timing of the UCI. The DCI may also include, for example, information related to the OCC, such as an OCC sequence length and an OCC sequence number, or information related to the antenna port or DMRS port used for transmitting the PUSCH and the PUCCH.

[0053] The control unit 203 outputs, for example, this control information to the data transmission processing unit 204, and also outputs setting values ​​based on the control information (e.g., PUSCH and PUCCH resources, OCC sequence length, OCC sequence number, number of TBoMS slots, number of repetitions, TDW of DMRS bundling, etc.) to the data reception processing unit 202.

[0054] The data transmission processing unit 204 performs coding such as LDPC on the transmission data and control information input from the control unit 203 , performs modulation such as QPSK and 16QAM, and outputs the result to the radio transmission unit 205 .

[0055] The radio transmitting section 205 performs transmission processing such as D / A conversion, filtering, up-conversion, and amplification on the signal input from the data transmission processing section 204, and transmits the radio signal from the antenna.

[0056] [Example of Operation of Terminal and Base Station] Hereinafter, an example of operation of terminal 100 and base station 200 when the UCI transmission timing and the transmission timing of a PUSCH to which OCC is applied overlap (or collide) will be described.

[0057] The state in which the transmission timings of the UCI and the PUSCH overlap (or collide) may be, for example, a state in which the slot or symbol for transmitting the UCI and the slot or symbol for transmitting the PUSCH are the same or partially overlap, or a state in which the PUCCH for transmitting the UCI and the PUSCH at least partially overlap. Here, the frequencies (also referred to as carriers or cells) for UCI transmission and PUSCH transmission may be the same or different.

[0058] In the following description, the OCC interval may be the time period of the PUSCH in which one OCC sequence is multiplied, or may be in slot units or symbol units.

[0059] In this embodiment, when the transmission timing of the UCI and the PUSCH collide, the terminal 100 determines not to transmit (for example, drop) the PUSCH. In this case, the terminal 100 may transmit the UCI using, for example, the PUCCH (or the PUSCH).

[0060] The operation of terminal 100 to not transmit the PUSCH may be varied depending on, for example, the relationship between the OCC period of the PUSCH to which OCC is applied and the UCI transmission timing.

[0061] For example, as shown in FIG. 5 , when the UCI transmission timing is the first slot of the OCC interval of the PUSCH, terminal 100 determines not to transmit (e.g., drop) the PUSCH in all slots of the OCC interval of the PUSCH. For example, terminal 100 does not transmit the PUSCH in all slots multiplied by one OCC sequence (OCC sequence length 4 in FIG. 5 ). Also, for example, as shown in FIG. 5 , when the number of repetitions (8 repetitions in FIG. 5 ) is greater than the OCC sequence length (OCC sequence length 4 in FIG. 5 ), the OCC sequence is multiplied by the PUSCH in each of multiple OCC intervals. That is, multiple OCC intervals may exist within the time interval in which the PUSCH is transmitted with repetitions. In this case, as shown in FIG. 5 , terminal 100 may transmit the PUSCH in the OCC interval next to the OCC interval in which the PUSCH was not transmitted due to collision with UCI transmission. That is, as shown in FIG. 5, terminal 100 may transmit the PUSCH in an OCC interval in which UCI transmission and PUSCH transmission do not collide, among a plurality of OCC intervals in which the PUSCH is transmitted in a repetitive manner.

[0062] Also, for example, as shown in FIG. 6 , if the UCI transmission timing is a slot other than the first slot of the OCC interval of the PUSCH (the third slot in FIG. 6 ), terminal 100 determines not to transmit (e.g., drop) the PUSCH in slots (the third and fourth slots in FIG. 6 ) following the slot that overlaps (collides with) the UCI transmission timing within the OCC interval of the PUSCH. Also, as shown in FIG. 6 , if there are multiple OCC intervals (two intervals in FIG. 6 ) in the time interval in which the PUSCH is transmitted with repetition (eight slots in FIG. 6 ), terminal 100 may transmit the PUSCH in the OCC interval next to the OCC interval of the PUSCH that was not transmitted due to collision with the UCI transmission. That is, as shown in FIG. 6 , terminal 100 may transmit the PUSCH in an OCC interval in which UCI transmission and PUSCH transmission do not collide, among multiple OCC intervals in which the PUSCH is transmitted with repetition.

[0063] As shown in FIGS. 5 and 6 , terminal 100 determines to drop the PUSCH in slots in the OCC period after the slot in which the UCI transmission timing and the PUSCH transmission timing to which OCC is applied overlap (for example, the first slot in FIG. 5 , the third slot in FIG. 6 ).

[0064] Alternatively, terminal 100 may determine to drop the PUSCH in multiple (e.g., all) slots included in an OCC interval in which the UCI transmission timing and the PUSCH transmission timing overlap. For example, as shown in FIG. 7 , if the UCI transmission timing is a slot other than the first slot of the OCC interval of the PUSCH (the third slot in FIG. 7 ) and terminal 100 identifies (knows) the UCI transmission timing before the OCC interval of the PUSCH, terminal 100 determines not to transmit (e.g., drop) the PUSCH in all slots of the OCC interval of the PUSCH. For example, terminal 100 does not transmit all PUSCHs multiplied by one OCC sequence (OCC sequence length 4 in FIG. 7 ).

[0065] For example, when the transmission timing of UCI (e.g., HARQ-ACK) is indicated by a PDCCH a predetermined slot before the OCC interval, or when UCI (e.g., CSI report) is transmitted periodically, terminal 100 can identify a collision between the UCI transmission timing and the PUSCH transmission timing before PUSCH transmission (e.g., at a timing before the OCC interval). Therefore, when the UCI transmission timing and the PUSCH transmission timing collide at any timing in a certain OCC interval, terminal 100 may determine not to transmit (drop) the PUSCH in all slots in the OCC interval of the PUSCH. Generally, when a PDCCH indicating the transmission timing of UCI such as HARQ-ACK is received at a timing before a PDCCH indicating PUSCH allocation, terminal 100 can determine the UCI transmission timing when transmitting the PUSCH.

[0066] 7 , terminal 100 may transmit the PUSCH in an OCC interval in which UCI transmission and PUSCH transmission do not collide, among multiple OCC intervals in which the PUSCH is transmitted with repetition. Note that if multiple OCC intervals exist in the time interval in which the PUSCH is transmitted with repetition, terminal 100 may perform control so as not to transmit the PUSCH in any of the OCC intervals.

[0067] As described above, in this embodiment, when the UCI transmission timing overlaps with the transmission timing of a PUSCH to which OCC is applied, terminal 100 controls the transmission (e.g., dropping) of the PUSCH in at least some slots of the OCC interval (e.g., all slots or slots after the slot where the overlap occurs).

[0068] As a result, when UCI transmission and PUSCH transmission to which OCC is applied collide, terminal 100 transmits UCI while not transmitting a PUSCH that may collide with UCI, thereby reducing interference between PUSCHs between terminals. Furthermore, for example, terminal 100 does not transmit a PUSCH in one OCC interval that collide with UCI transmission, but transmits a PUSCH in an OCC interval that does not collide with UCI transmission, thereby suppressing deterioration of PUSCH reception quality (for example, SNR (Signal to Noise Ratio)).

[0069] When terminal 100 transmits UCI without transmitting PUSCH, it may perform repetition and OCC multiplication on the PUCCH (or PUSCH) used for UCI transmission over the OCC interval of the PUSCH, thereby improving the reception quality (e.g., SNR, etc.) of the UCI.

[0070] (Embodiment 2) In this embodiment, when the UCI transmission timing and the transmission timing of a PUSCH to which OCC is applied overlap (or collide), terminal 100 transmits a PUSCH in which UCI and data are multiplexed, in a slot within an OCC interval (e.g., an interval to which one OCC sequence is applied) that overlaps with the UCI transmission.

[0071] The configurations of the terminal 100 and the base station 200 are the same as those in embodiment 1. The operations of the data transmission processing unit 104 of the terminal 100 and the data reception processing unit 202 of the base station 200 are different from those in embodiment 1.

[0072] In terminal 100, data transmission processing unit 104 multiplexes UCI and data in a PUSCH of one or more slots in an OCC interval at the UCI transmission timing and transmits the PUSCH. Note that an example of a transmission operation when the UCI transmission timing and the PUSCH transmission timing to which OCC is applied overlap will be described later.

[0073] In the base station 200, when the UCI transmission timing overlaps with the PUSCH transmission timing to which OCC is applied, the data reception processing unit 202 obtains the received data sequence multiplexed onto the PUSCH and the UCI. For example, the data reception processing unit 202 controls the reception of the PUSCH and the UCI when OCC is applied, in accordance with the operation when the UCI and the PUSCH collide, which will be described later (for example, assuming the operation of the terminal 100).

[0074] [Operational Example of Terminal and Base Station] An operational example of terminal 100 and base station 200 when the UCI transmission timing and the PUSCH transmission timing to which OCC is applied overlap (or collide) will be described below. Note that the state in which the UCI and PUSCH transmission timings overlap (or collide) and the definition of the OCC interval may be the same as in the first embodiment.

[0075] In this embodiment, when the transmission timing of UCI and PUSCH collide, terminal 100 multiplexes UCI and data in the PUSCH of one or more slots in the OCC interval, depending on the timing of the collision, and transmits the PUSCH.

[0076] A case where UCI transmission collides with the first slot of the OCC interval of PUSCH transmission will be described.

[0077] When UCI transmission collides with the first slot of the OCC interval of PUSCH transmission, terminal 100 multiplexes UCI and data in all slots of the colliding OCC interval and transmits the PUSCH. Because UCI and data are multiplied by OCC in all slots of the OCC interval (for example, because common processing is performed on all slots in the OCC interval), orthogonality between terminals can be maintained.

[0078] For example, Figures 8, 9, and 10 show an example of operation when the number of repetitions is 8 and the OCC sequence length is 4. In the examples of Figures 8, 9, and 10, two OCC periods are included in the time period in which the PUSCH is transmitted with repetitions.

[0079] 8 shows an example in which UCI and PUSCH collide in the first slot (e.g., the first slot of repetition) in the first OCC interval of two OCC intervals included in a time interval in which PUSCH is transmitted with repetition. In this case, as shown in FIG. 8, terminal 100 multiplexes UCI with data and transmits PUSCH in all slots (four slots) of the first OCC interval.

[0080] 9 shows an example in which UCI and PUSCH collide in the first slot (e.g., the fifth slot of the repetition) in the latter of two OCC intervals included in a time interval in which PUSCH is transmitted with repetition. In this case, as shown in FIG. 9, terminal 100 multiplexes UCI with data and transmits PUSCH in all slots (four slots) of the latter OCC interval.

[0081] As shown in FIGS. 8 and 9, terminal 100 may determine multiplexing of UCI and data in multiple (for example, all) slots included in an OCC interval in which the UCI transmission timing and the PUSCH transmission timing overlap.

[0082] Furthermore, as shown in FIG. 10 , when UCI and PUSCH collide in the first slot (e.g., the first slot of repetition) in the first OCC interval of two OCC intervals included in a time interval in which PUSCH is transmitted with repetition, terminal 100 may multiplex UCI with data in multiple slots in which PUSCH is transmitted with repetition (across two OCC intervals) and transmit PUSCH. In the example of FIG. 10 , UCI is transmitted in all slots in the repetition interval. That is, terminal 100 may determine multiplexing of UCI and data in multiple OCC intervals in which PUSCH is transmitted with repetition, including an OCC interval in which the UCI transmission timing and the PUSCH transmission timing overlap.

[0083] 8, 9, and 10, UCI and data are multiplied by the OCC and transmitted at least in all slots within an OCC interval where UCI and PUSCH collide. This allows the configurations of transmission signals (e.g., UCI and data) in multiple slots to be similar in the OCC interval, thereby maintaining orthogonality between terminals. Furthermore, in this embodiment, more resources are used for UCI transmission than in embodiment 1, which enables improvement in the reception quality of UCI (e.g., SNR, etc.). Furthermore, for example, as shown in FIG. 10, when UCI is transmitted across multiple OCC intervals including an OCC interval where UCI and PUSCH collide, more resources are used for UCI transmission, which enables further improvement in the reception quality of UCI.

[0084] Next, an example of operation when UCI transmission collides with a slot other than the first slot (for example, an intermediate slot) of the OCC interval of PUSCH transmission will be described.

[0085] <Operation Example 1> In operation example 1, when the UCI transmission timing collides with a slot other than the first slot in the OCC interval of the PUSCH, terminal 100 determines not to transmit (e.g., drop) the PUSCH in all slots in the OCC interval of the PUSCH (e.g., see FIG. 7 ) or in slots following the colliding slot (e.g., see FIG. 6 ), as in embodiment 1, and transmits UCI using the PUCCH or the like.

[0086] This makes it possible to prevent the loss of orthogonality between terminals multiplexed by OCC.

[0087] <Operation Example 2> In operation example 2, as shown in Fig. 11 , when the UCI transmission timing collides with a slot other than the first slot of the OCC interval of the PUSCH (the third slot in Fig. 11 ), terminal 100 transmits a PUSCH in which UCI and data are multiplexed in slots (the third and fourth slots in Fig. 11 ) after the slot that overlaps (collides with) the UCI transmission timing, within the OCC interval of the PUSCH. That is, terminal 100 determines to multiplex UCI and data in slots after the slot where the UCI transmission timing and PUSCH transmission timing overlap, within the OCC interval.

[0088] Although UCI transmission may cause interference to terminal 100 multiplexed by OCC, terminal 100 can transmit UCI in all slots after the slot in which UCI and PUSCH collide, and can suppress degradation of reception characteristics due to loss of orthogonality between terminals multiplexed by OCC.

[0089] <Operation Example 3> In operation example 3, as shown in Fig. 12 , when the UCI transmission timing collides with a slot other than the first slot of the OCC interval of the PUSCH (the third slot in Fig. 12 ), terminal 100 does not transmit UCI in the OCC interval that collides with the UCI transmission timing (the first OCC interval in Fig. 12 ), but transmits PUSCH in which UCI and data are multiplexed in all slots in the OCC interval next to the OCC interval that collides with the UCI transmission timing (the first OCC interval in Fig. 12 ). In other words, terminal 100 determines to multiplex UCI and data in multiple slots included in an OCC interval after the OCC interval in which the UCI transmission timing and the PUSCH transmission timing overlap.

[0090] Alternatively, for example, if the UCI transmission timing is known to terminal 100 at the start of PUSCH transmission, terminal 100 may transmit a PUSCH in which UCI and data are multiplexed in all slots of the corresponding OCC interval. Generally, if a PDCCH that notifies the transmission timing of UCI such as HARQ-ACK is received at a timing earlier than a PDCCH that notifies PUSCH allocation, terminal 100 can ascertain the UCI transmission timing at the time of PUSCH transmission.

[0091] This allows terminal 100 to transmit UCI while suppressing degradation of reception characteristics due to loss of orthogonality between terminals multiplexed by OCC.

[0092] An example of the operation of the terminal 100 and the base station 200 has been described above.

[0093] As described above, in this embodiment, when the UCI transmission timing overlaps with the transmission timing of a PUSCH to which OCC is applied, terminal 100 controls the transmission of the PUSCH (e.g., multiplexing of UCI and data) in at least some slots of the OCC interval (e.g., all slots or slots after the slot where the overlap occurs).

[0094] As a result, terminal 100 can transmit UCI while reducing interference between UCC and PUSCH during despreading of OCC, thereby suppressing degradation of reception performance. Also, orthogonality between terminals multiplexed by OCC can be maintained.

[0095] (Embodiment 3) In this embodiment, when UCI and data are multiplexed in a PUSCH to which OCC is applied, terminal 100 maps UCI to punctured data resources (e.g., REs (Resource Elements)) and transmits the PUSCH. Furthermore, terminal 100 may transmit, in slots within an OCC interval in which UCI is not transmitted, a PUSCH in which resources (OFDM symbols or REs) on which UCI may be multiplexed in slots in which UCI is transmitted are punctured.

[0096] The configurations of the terminal 100 and the base station 200 are the same as those in the second embodiment. The operations of the data transmission processing unit 104 of the terminal 100 and the data reception processing unit 202 of the base station 200 are different from those in the first embodiment.

[0097] In the terminal 100, the data transmission processing unit 104 punctures data resources (e.g., REs) and maps UCI when multiplexing UCI and data in a PUSCH of one or more slots in an OCC interval at UCI transmission timing. Furthermore, the data transmission processing unit 104 punctures resources (e.g., OFDM symbols or REs) on which UCI may be multiplexed in slots in the OCC interval in which UCI is not transmitted, or resources (e.g., OFDM symbols or REs) on which UCI is multiplexed in other slots, and transmits the PUSCH. An example of a transmission operation when the UCI transmission timing and the PUSCH transmission timing to which OCC is applied overlap will be described later.

[0098] In base station 200, when the UCI transmission timing overlaps with the PUSCH transmission timing to which OCC is applied, data reception processing section 202 obtains the received data sequence and UCI multiplexed on the PUSCH. For example, data reception processing section 202 controls reception of the PUSCH and UCI when OCC is applied, taking into account data resources to be punctured for UCI transmission (e.g., assuming the operation of terminal 100).

[0099] [Example of Operation of Terminal and Base Station] Hereinafter, an example of a method for multiplexing UCI and data in a PUSCH to which OCC is applied will be described.

[0100] Methods of multiplexing UCI and data in a PUSCH include a method of mapping UCI to PUSCH resources (REs) and then mapping data to the remaining REs by rate matching, and a method of mapping data to REs and then mapping UCI to a predetermined RE by puncturing.

[0101] The rate matching method is suitable for cases where the resources used for UCI transmission are deterministic (e.g., periodic CSI feedback or HARQ-ACK feedback of 3 or more bits over multiple slots), and provides good data decoding performance because it allows certain data to be transmitted without puncturing (thinning out).

[0102] The method using puncturing is suitable for cases where the resources used by UCI transmission are uncertain (for example, HARQ-ACK feedback of 2 bits or less in a single slot), and when UCI is not present, only data can be embedded in the PUSCH resource for transmission. On the other hand, when UCI is present, certain data is punctured and not transmitted, which may result in degradation of decoding performance.

[0103] 13 shows examples of methods for mapping UCI and data to a PUSCH using rate matching and puncturing. As shown in FIG. 13, when UCI is not multiplexed with data, consecutive data symbols with indexes 0 to 20 are mapped. Also, as shown in FIG. 13, when UCI and data are multiplexed, consecutive data symbols with indexes 0 to 17 are mapped in the method using rate matching, and data symbols with indexes 9 to 11 are not mapped (transmitted) in the method using puncturing.

[0104] In the present embodiment, terminal 100 multiplexes UCI and data by puncturing data in a PUSCH to which OCC is applied.

[0105] As a result, for example, the indexes of the data symbols transmitted are the same between slots in which UCI is not multiplexed and slots in which UCI is multiplexed. For example, as shown in Fig. 13, the sequence of data symbols with indexes 0 to 8 and 12 to 20 in the method of multiplexing UCI by data puncturing matches the sequence of data symbols with indexes 0 to 8 and 12 to 20 in the case in which UCI is not multiplexed.

[0106] Therefore, when the base station 200 performs OCC despreading on reception, it is possible to despread the same data, thereby suppressing degradation of reception performance due to UCI multiplexing and maintaining orthogonality between terminals multiplexed by OCC.

[0107] As a result, even when the UCI transmission timing and the PUSCH transmission timing to which OCC is applied overlap, terminal 100 can transmit UCI while suppressing degradation in reception performance during despreading of OCC, and can also maintain orthogonality between terminals multiplexed by OCC.

[0108] Furthermore, for example, in slots other than the slot in which UCI is transmitted within the OCC interval, terminal 100 may puncture data (e.g., may not transmit anything) in resources (OFDM symbols or REs) to which UCI may be mapped in the slot in which UCI is transmitted or resources corresponding to resources to which UCI is mapped in the slot in which UCI is transmitted.

[0109] As an example, Figure 14 shows an operation example in which the repetition number is 8 and the OCC sequence length is 4. As shown in Figure 14, the slot in which the UCI is transmitted may be the first slot of the OCC interval, or may be a slot other than the first slot of the OCC interval (not shown). As shown in Figure 14, in the OCC interval in which the UCI and the PUSCH are multiplexed, in the slot in which the UCI is transmitted (the first slot), the UCI is mapped to a certain resource by puncturing. Also, as shown in Figure 14, in the OCC interval in which the UCI and the PUSCH are multiplexed, in slots in which the UCI is not transmitted (e.g., the second to fourth slots), data of the same resource (resource position within the slot) as the resource to which the UCI is mapped in the slot in which the UCI is transmitted is punctured.

[0110] As shown in FIG. 14 , when UCI is mapped to a resource (e.g., RE) in a certain slot (e.g., the first slot) in the OCC interval, terminal 100 punctures data in another slot (e.g., the second slot) in the OCC interval that is mapped to an RE corresponding to the resource (RE) to which UCI is mapped in the first slot.

[0111] As a result, in all slots within the OCC section, data is not mapped to resources to which UCI is mapped in a certain slot, so that interference due to UCI does not occur when despreading OCC, and degradation of reception performance can be suppressed.

[0112] Furthermore, terminal 100 may puncture data mapped to resources (e.g., REs) to which UCI may be mapped, in multiple slots included in the OCC interval. For example, as shown in FIG. 15 , terminal 100 may puncture data of resources (OFDM symbols or REs) to which UCI may be mapped, even when UCI transmission is not performed. In the example of FIG. 15 , when UCI transmission is not performed, data mapped to resources to which UCI may be mapped is punctured in each slot in two OCC intervals included in the repetition interval. For example, information on resources to be punctured or information on slots to be punctured may be notified to terminal 100 by base station 200. Terminal 100 may perform puncturing in accordance with the information notified from base station 200.

[0113] In addition, in the above example, a case where UCI and data are multiplexed and transmitted in one slot within the OCC section has been described, but this is not limited to this, and UCI and data may be multiplexed and transmitted in multiple slots.

[0114] Furthermore, terminal 100 may multiplex UCI and data by rate matching data in a PUSCH to which OCC is not applied, and may multiplex UCI and data by puncturing data in a PUSCH to which OCC is applied.

[0115] In this manner, in the present embodiment, when the UCI transmission timing and the transmission timing of a PUSCH to which OCC is applied overlap, terminal 100 controls the transmission of the PUSCH (for example, puncturing) in each slot of the OCC section.

[0116] As a result, terminal 100 can transmit UCI while reducing interference between UCI and PUSCH during despreading of OCC, thereby suppressing degradation of reception performance. Also, orthogonality between terminals multiplexed by OCC can be maintained.

[0117] The above describes each embodiment.

[0118] It should be noted that any combination of Embodiments 1 to 3 may be used. For example, when terminal 100 or base station 200 does not support multiplexing of UCI and data in a PUSCH to which OCC is applied, the method of Embodiment 1 may be applied, and when terminal 100 or base station 200 supports multiplexing of UCI and data in a PUSCH to which OCC is applied, the method of Embodiment 2 may be applied. Whether terminal 100 or base station 200 supports multiplexing of UCI and data in a PUSCH to which OCC is applied may be determined, for example, based on information on terminal capability (UE capability) reported from terminal 100 or information such as an SIB broadcast or notified within the cell.

[0119] Furthermore, depending on the conditions of the priority of UCI or PUSCH and the timing of collision, it is possible to switch between the operation of not transmitting PUSCH (PUSCH drop) of Embodiment 1 and the operation of UCI multiplexing of Embodiment 2. For example, depending on the conditions of the priority of UCI or PUSCH and the timing of collision, it is possible to not transmit PUSCH in an OCC interval that collides with UCI (PUSCH drop) as shown in Fig. 5, or to multiplex UCI and PUSCH in an OCC interval that collides with UCI as shown in Fig. 8.

[0120] Furthermore, in the first to third embodiments, the description has been given including cases in which the UCI transmission timing is a slot other than the first (first) slot of the OCC interval, but terminal 100 or base station 200 may handle only cases in which the UCI transmission timing is the first slot of the OCC interval. For example, base station 200 may notify terminal 100 of the UCI transmission timing so that the UCI transmission timing is the first slot of the OCC interval. Furthermore, terminal 100 assumes that the UCI transmission timing is the first slot of the OCC interval, and in cases in which the notified UCI transmission timing is not the first slot of the OCC interval, it does not need to transmit both UCI and PUSCH, and may transmit either one of them.

[0121] Furthermore, in the first to third embodiments, when the UCI transmission timing overlaps with the PUSCH transmission timing to which OCC is applied, the UCI is transmitted by dropping the PUSCH or multiplexing it with data in the PUSCH. However, terminal 100 may drop the UCI transmission and transmit the PUSCH depending on the content (type) or priority of the UCI. For example, when the UCI is low-priority information such as CSI feedback, terminal 100 may drop the UCI and transmit the PUSCH.

[0122] Furthermore, in the first to third embodiments, when the UCI transmission timing overlaps with the PUSCH transmission timing to which OCC is applied, terminal 100 may transmit UCI on the PUCCH without transmitting the PUSCH within the OCC interval, and may transmit the PUSCH that has not been transmitted at another timing after the OCC interval (or slot). That is, when the UCI transmission timing overlaps with the PUSCH transmission timing to which OCC is applied, terminal 100 may postpone (or delay, or shift) the PUSCH transmission. Here, the timing to start transmission of the postponed (or delayed, or shifted) PUSCH may be the slot next to the slot used for PUCCH transmission, or the slot after the OCC interval of the slot used for PUCCH transmission, or may be another timing. When PUSCH transmission is started in the slot next to the slot used for PUCCH transmission, the transmission delay of the PUSCH can be reduced. Furthermore, for example, if PUSCH transmission is started in a slot that is one OCC interval after the slot used for PUCCH transmission, PUSCH can be transmitted in an OCC interval that is aligned with the OCC intervals of other terminals, thereby reducing interference between terminals.

[0123] Furthermore, in one embodiment of the present disclosure, it is possible to reduce the loss of orthogonality (or inter-code interference) between terminals transmitting PUSCHs to which OCC is applied, and also has the effect of reducing inter-slot interference when despreading multiple slots to which OCC is applied in terminal 100, even when multiplexed transmission is not performed between terminals.

[0124] Alternatively, the OCC interval may be a time period of the PUSCH multiplied by one OCC sequence, may be expressed in slot units, or may be expressed in symbol units, or may be referred to as an OCC group.

[0125] Although the OCC application method has been described using an example of a method of multiplying an OCC by multiple slots to be repeated (inter-slot OCC), the unit of applying the OCC is not limited to a slot unit and may be a different time unit. For example, any of the first to third embodiments may be applied to a method of multiplying an OCC by multiple OFDM symbols (inter-symbol OCC).

[0126] Furthermore, DFT-s-OFDM modulation may be performed on the uplink PUSCH, or CP (Cyclic Prefix)-OFDM modulation may be performed, or other modulation methods may be applied.

[0127] Furthermore, OCC sequences include Walsh sequences, DFT sequences, and cyclic shift sequences, and the first to third embodiments can be applied to any of these sequences.

[0128] For example, the sequence described below may be used.

[0129] sequence length n OCC The OCC sequence m is expressed by the following equation (see, for example, TS38.211 V15.10.0 Table 6.3.2.4.1-2):

[0130] However, ψ(m) may be set to a value in the table shown in FIG. OCC When =4, there are four OCC sequences: [1 1 1 1], [1 -1 1 -1], [1 1 -1 -1], and [1 -1 -1 1].

[0131] Although the above description is directed to an example in which an OCC sequence number is used as information for identifying an OCC sequence, the information for identifying an OCC sequence is not limited to this and may be other information. For example, the information for identifying an OCC sequence may be information related to a cyclic shift amount or a value used in sequence generation.

[0132] Furthermore, OCC may be interpreted as an orthogonal code, a spreading code, a spreading sequence, a spreading code, etc. Furthermore, OCC sequence length may be interpreted as a spreading factor, a spreading code length, etc. Furthermore, the code used for multiplexing signals between terminals is not limited to OCC, and other orthogonal codes may be used. Furthermore, the OCC sequence may be a sequence such as a cyclic shift sequence.

[0133] Furthermore, the loss of orthogonality may be interpreted as inter-code interference.

[0134] The transmission unit may be a slot, a frame, or a symbol. When TBoMS is applied, a TBoMS slot, which is a group of multiple slots, may be used as the transmission unit instead of a slot.

[0135] The OCC sequence length may be interpreted as the time interval (OCC application interval) during which multiplication by one OCC sequence is applied.

[0136] An embodiment of the present disclosure can be applied to both mapping type A, which is allocation in slot units, and mapping type B, which is allocation in symbol units. Also, the repetition can be applied to both type A and type B.

[0137] The control information regarding the OCC may include information regarding the OCC application method (inter-slot, inter-symbol, intra-symbol).

[0138] Furthermore, the present disclosure is not limited to the case where OCC is applied to PUSCH, and may also be applied to the case where OCC is applied to DMRS.

[0139] Furthermore, the base station may be read as a network or a RAN (Radio Access Network).

[0140] Furthermore, the above embodiment may be applied to networks other than NTN.

[0141] An embodiment of the present disclosure can be used for different types of satellite communications, such as Low Earth Orbit satellites (LEO), Medium Earth Orbit satellites (MEO), Highly Elliptical Orbit satellites (HEO), or Geostationary Earth Orbit satellites (GEO), which are located at different altitudes above the Earth's surface.

[0142] In each of the above-described embodiments, satellite ephemeris information, which is information related to satellite positions, may be reported by system information or may be stored in advance by the terminal 100. Furthermore, the satellite ephemeris information may be updated when communication is possible. Furthermore, the terminal 100 may identify satellite positions using information other than the satellite ephemeris information.

[0143] In the above-described embodiments, examples have been described in which GNSS such as GPS (for example, position detection using satellite signals) is used, but the present invention is not limited to this. For example, position detection may be performed using a terrestrial cellular base station, a Wi-Fi (registered trademark) signal or a Bluetooth (registered trademark) signal, an acceleration sensor, or a combination of these detection methods. Furthermore, altitude information may be obtained from a barometric pressure sensor, etc.

[0144] In the above-described embodiments, "report" may be read as "notification," and "notification" may be read as "report." "Calculation" may be read as "determination" or "generation."

[0145] Furthermore, in each of the above-described embodiments, the transmission of an uplink signal from a terminal to a base station has been described, but the present invention may also be applied to the transmission of a downlink signal from a base station to a terminal.

[0146] An embodiment of the present disclosure may be applied regardless of the type of satellite, such as GEO, MEO, LEO, or HEO. Furthermore, an embodiment of the present disclosure may be applied to non-terrestrial communications, such as HAPS or drone base stations.

[0147] Although the above-described embodiment has been described using an NTN environment (e.g., a satellite communication environment) as an example, the present disclosure is not limited thereto. The present disclosure may be applied to other communication environments (e.g., a terrestrial cellular environment of at least one of LTE and NR). For example, one embodiment of the present disclosure may be applied to terrestrial communications in an environment where the cell size is large and the propagation delay between the base station 200 and the terminal 100 is longer (e.g., above a threshold).

[0148] In the above-described embodiment, the satellite communication may be in the form of a configuration in which the base station functions are located on a satellite (e.g., a "regenerative satellite"), or a configuration in which the base station functions are located on the ground and a satellite relays communication between the base station and a terminal (e.g., a "transparent satellite"). For example, in one embodiment of the present disclosure, the downlink and the uplink may be links between a terminal and a satellite, or links via a satellite.

[0149] The method of notifying the control information from the base station 200 to the terminal 100 is not limited to the above-mentioned example, and may be notified (or reported, indicated, or set) by at least one of system information such as MIB and SIB, RRC control information, MAC control information, and downlink control information (DCI), or may be pre-set in the terminal 100 or may be pre-defined in a standard.

[0150] The base station may be referred to as a gNodeB or a gNB, and the terminal may be referred to as a UE.

[0151] The time resource units such as symbols and slots may be replaced with system frames, time slots, minislots, frames, subframes, and the like.

[0152] Furthermore, parameters such as the OCC sequence length, the time interval to which OCC is applied (for example, the number of slots), and the number of repetitions are not limited to the above examples, and other values ​​may be used.

[0153] Furthermore, the notation "... section" in the above-described embodiments may be replaced with other notations such as "... circuitry," "... device," "... unit," or "... module."

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

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

[0156] For example, the base station 200 may determine (or decide or assume) the functions, operations, or processes that the terminal 100 that transmitted the capability information supports (or does not support) based on the capability information received from the terminal 100. The base station 200 may perform operations, processes, or controls according to the determination result based on the capability information. For example, the base station 200 may control communications based on the capability information received from the terminal 100.

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

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

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

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

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

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

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

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

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

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

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

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

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

[0170] (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 transmission than symbols that transmit and receive only downlink transmission. Also, SBFD symbols may have a smaller frequency domain available for uplink transmission than symbols that transmit and receive only uplink transmission.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0208] A terminal according to one embodiment of the present disclosure includes a control circuit that controls, when the transmission timing of uplink control information overlaps with the transmission timing of an uplink data signal to which an orthogonal code is applied, the transmission of the uplink data signal in at least a portion of the time resources of the section to which the orthogonal code is applied, and a transmission circuit that transmits the uplink control information and the uplink data signal in accordance with the control of the transmission of the uplink data signal.

[0209] In one embodiment of the present disclosure, the control circuit determines not to transmit the uplink data signal in time resources after the time resource in which the transmission timing of the uplink control information and the transmission timing of the uplink data signal overlap within the period.

[0210] In one embodiment of the present disclosure, the control circuit determines not to transmit the uplink data signal in a plurality of time resources included in the section in which the transmission timing of the uplink control information and the transmission timing of the uplink data signal overlap.

[0211] In one embodiment of the present disclosure, the control circuit determines multiplexing of the uplink data signal and the uplink control information in multiple time resources included in the section in which the transmission timing of the uplink control information and the transmission timing of the uplink data signal overlap.

[0212] In one embodiment of the present disclosure, the control circuit determines multiplexing of the uplink data signal and the uplink control information in multiple sections in which the uplink data signal is repeatedly transmitted, including the section in which the transmission timing of the uplink control information and the transmission timing of the uplink data signal overlap.

[0213] In one embodiment of the present disclosure, the control circuit determines to multiplex the uplink data signal and the uplink control information in a time resource within the section after the time resource in which the transmission timing of the uplink control information and the transmission timing of the uplink data signal overlap.

[0214] In one embodiment of the present disclosure, the control circuit determines multiplexing of the uplink data signal and the uplink control information in multiple time resources included in a section after the section in which the transmission timing of the uplink control information and the transmission timing of the uplink data signal overlap.

[0215] In one embodiment of the present disclosure, when the uplink control information is mapped to a first resource element in a first slot of the interval, the control circuit punctures the uplink data signal that is mapped to a second resource element corresponding to the first resource element in a second slot different from the first slot of the interval.

[0216] In one embodiment of the present disclosure, the control circuit punctures the uplink data signal that is mapped to resource elements to which the uplink control information may be mapped in multiple slots included in the section.

[0217] A base station according to one embodiment of the present disclosure includes a control circuit that, when the transmission timing of uplink control information overlaps with the transmission timing of an uplink data signal to which an orthogonal code is applied, controls the reception of the uplink data signal, assuming that the uplink signal will be transmitted in at least a portion of the time resources of the section to which the orthogonal code is applied, and a receiving circuit that receives the uplink control information and the uplink data signal in accordance with the reception control.

[0218] In a communication method according to one embodiment of the present disclosure, when the transmission timing of uplink control information overlaps with the transmission timing of an uplink data signal to which an orthogonal code is applied, a terminal controls the transmission of the uplink data signal in at least a portion of the time resources of the section to which the orthogonal code is applied, and transmits the uplink control information and the uplink data signal in accordance with the control of the transmission of the uplink data signal.

[0219] In a communication method according to one embodiment of the present disclosure, when the transmission timing of uplink control information overlaps with the transmission timing of an uplink data signal to which an orthogonal code is applied, a base station performs reception control of the uplink data signal, assuming that the uplink data signal will be transmitted in at least a portion of the time resources of the section to which the orthogonal code is applied, and receives the uplink control information and the uplink data signal in accordance with the reception control.

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

[0221] One aspect of the present disclosure is useful in wireless communication systems.

[0222] 100 Terminal 101, 201 Radio receiving unit 102, 202 Data receiving processing unit 103, 203 Control unit 104, 204 Data transmitting processing unit 105, 205 Radio transmitting unit 200 Base station

Claims

1. A communication device comprising: a control circuit that controls the transmission of uplink control information and uplink data signals to which orthogonal codes are applied in at least a portion of the time resources of a section to which the orthogonal codes are applied when the transmission timing of the uplink control information and the uplink data signals overlap; and a transmission circuit that transmits the uplink control information and the uplink data signals in accordance with the control of the transmission of the uplink data signals.

2. The communication device according to claim 1, wherein the control circuit determines not to transmit the uplink data signal in time resources after the time resource in which the transmission timing of the uplink control information and the transmission timing of the uplink data signal overlap within the period.

3. The communication device according to claim 1, wherein the control circuit determines non-transmission of the uplink data signal in a plurality of time resources included in the section in which the transmission timing of the uplink control information and the transmission timing of the uplink data signal overlap.

4. The communication device according to claim 1, wherein the control circuit determines multiplexing of the uplink data signal and the uplink control information in a plurality of time resources included in the section in which the transmission timing of the uplink control information and the transmission timing of the uplink data signal overlap.

5. The communication device according to claim 1, wherein the control circuit determines multiplexing of the uplink data signal and the uplink control information in multiple sections in which the uplink data signal is repeatedly transmitted, including the section in which the transmission timing of the uplink control information and the transmission timing of the uplink data signal overlap.

6. The communication device according to claim 1, wherein the control circuit determines the multiplexing of the uplink data signal and the uplink control information in a time resource after the time resource in which the transmission timing of the uplink control information and the transmission timing of the uplink data signal overlap within the period.

7. The communication device according to claim 1, wherein the control circuit determines multiplexing of the uplink data signal and the uplink control information in a plurality of time resources included in a section subsequent to the section in which the transmission timing of the uplink control information and the transmission timing of the uplink data signal overlap.

8. The communication device according to claim 1, wherein, when the uplink control information is mapped to a first resource element in a first slot of the section, the control circuit punctures the uplink data signal that is mapped to a second resource element corresponding to the first resource element in a second slot different from the first slot of the section.

9. The communication device according to claim 1, wherein the control circuit punctures the uplink data signal that is mapped to resource elements to which the uplink control information may be mapped in a plurality of slots included in the section.

10. A base station comprising: a control circuit that, when the transmission timing of uplink control information overlaps with the transmission timing of an uplink data signal to which an orthogonal code is applied, controls the reception of the uplink data signal, assuming that the uplink signal will be transmitted in at least a portion of the time resources of the section to which the orthogonal code is applied; and a receiving circuit that receives the uplink control information and the uplink data signal in accordance with the receiving control.

11. A communication method in which, when the transmission timing of uplink control information overlaps with the transmission timing of an uplink data signal to which an orthogonal code is applied, a communication device controls the transmission of the uplink data signal in at least a portion of the time resources of the section to which the orthogonal code is applied, and transmits the uplink control information and the uplink data signal in accordance with the control of the transmission of the uplink data signal.

12. A communication method in which, when the transmission timing of uplink control information overlaps with the transmission timing of an uplink data signal to which an orthogonal code is applied, a base station performs reception control of the uplink data signal, assuming that the uplink data signal will be transmitted in at least a portion of the time resources of the section to which the orthogonal code is applied, and receives the uplink control information and the uplink data signal in accordance with the reception control.

13. An integrated circuit that controls the processing of a communication device, the processing including: when the transmission timing of uplink control information overlaps with the transmission timing of an uplink data signal to which an orthogonal code is applied, a process of controlling the transmission of the uplink data signal in at least a portion of the time resources of the section to which the orthogonal code is applied; and a process of transmitting the uplink control information and the uplink data signal in accordance with the control of the transmission of the uplink data signal.

14. An integrated circuit that controls the processing of a base station, the processing including: when the transmission timing of uplink control information overlaps with the transmission timing of an uplink data signal to which an orthogonal code is applied, a process of performing reception control of the uplink data signal, assuming that the uplink data signal will be transmitted in at least a portion of the time resources of the section to which the orthogonal code is applied; and a process of receiving the uplink control information and the uplink data signal in accordance with the reception control.

Images