terminal
Patent Information
- Application Number
- JP2024206443
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2024-11-27
- Publication Date
- 2025-02-26
Smart Images

Figure 2025027040000001_ABST
Abstract
Description
[Technical field]
[0001] The present disclosure relates to a terminal that performs wireless communication, and in particular to a terminal that performs wireless communication using a component carrier. [Background technology]
[0002] The 3rd Generation Partnership Project (3GPP) has developed specifications for the 5th generation mobile communication system (5G, also known as New Radio (NR) or Next Generation (NG)), and is also developing specifications for the next generation, known as Beyond 5G, 5G Evolution, or 6G.
[0003] 3GPP Release 15 and Release 16 (NR) specify operation in multiple frequency ranges, specifically bands including FR1 (410 MHz to 7.125 GHz) and FR2 (24.25 GHz to 52.6 GHz).
[0004] In addition, NR that supports frequencies above 52.6 GHz and up to 71 GHz is also being studied (Non-Patent Document 1). Furthermore, Beyond 5G, 5G Evolution, and 6G (Release-18 and later) aim to support frequency bands above 71 GHz. [Prior art documents] [Non-patent literature]
[0005] [Non-Patent Document 1] "New WID on Extending current NR operation to 71 GHz", RP-193229, 3GPP TSG RAN Meeting #86, 3GPP, December 2019 Summary of the Invention
[0006] As described above, in the second frequency range (e.g., 52.6 GHz or higher) which is higher than the first frequency range (e.g., 52.6 GHz or lower), from the viewpoints of power amplifier efficiency, high phase noise, etc., it is necessary to suppress degradation in reliability of uplink control information (UCI) transmitted via a physical uplink control channel (PUCCH) or a physical uplink shared channel (PUSCH).
[0007] Therefore, the following disclosure has been made in consideration of the above circumstances, and aims to provide a terminal that can suppress a decrease in the reliability of UCI.
[0008] An aspect of the present disclosure is a terminal including a communication unit that performs data communication with a network via a second component carrier different from a first component carrier, wherein the communication unit transmits uplink control information related to the second component carrier to the network using the first component carrier, or, when a predetermined condition is satisfied, transmits uplink control information related to at least one of the first component carrier and the second component carrier to the network by simultaneously transmitting a predetermined physical uplink channel in the second component carrier, or, after discarding transmission of the predetermined physical uplink channel, transmits the uplink control information related to the second component carrier using the second component carrier, or, when a predetermined condition is satisfied, multiplexes the uplink control information related to the second component carrier into a predetermined physical uplink channel and transmits it to the network. [Brief description of the drawings]
[0009] [Figure 1] FIG. 1 is a diagram showing an overall schematic configuration of a wireless communication system 10. As shown in FIG. [Diagram 2]FIG. 2 is a diagram showing frequency ranges used in the wireless communication system 10. As shown in FIG. [Diagram 3] FIG. 3 is a diagram showing an example of the configuration of a radio frame, a subframe, and a slot used in the radio communication system 10. As shown in FIG. [Figure 4] FIG. 4 is a functional block diagram of UE 200. [Diagram 5] FIG. 5 is a diagram showing the first operation example. [Figure 6] FIG. 6 is a diagram illustrating a second operation example. [Figure 7] FIG. 7 is a diagram illustrating an operation example 3. In FIG. [Figure 8] FIG. 8 is a diagram illustrating the fourth operation example. [Figure 9] FIG. 9 is a diagram illustrating a fifth operation example. [Figure 10] FIG. 10 is a diagram illustrating an operation example 6. In FIG. [Figure 11] FIG. 11 is a diagram illustrating the seventh operation example. [Figure 12] FIG. 12 is a diagram for explaining the first modification. [Figure 13] FIG. 13 is a diagram illustrating an example of a hardware configuration of the UE 200. As shown in FIG. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0010] Hereinafter, an embodiment will be described with reference to the drawings. Note that the same or similar reference numerals are used to designate the same functions or configurations, and the description thereof will be omitted as appropriate.
[0011] [Embodiment] (1) Overall configuration of wireless communication system 1 is a schematic diagram of an overall configuration of a wireless communication system 10 according to the present embodiment. The wireless communication system 10 is a wireless communication system conforming to 5G New Radio (NR), and includes a Next Generation-Radio Access Network 20 (hereinafter, NG-RAN 20) and a terminal 200 (hereinafter, UE 200).
[0012] The wireless communication system 10 may be a wireless communication system conforming to a standard called Beyond 5G, 5G Evolution, or 6G.
[0013] The NG-RAN 20 includes a radio base station 100A (hereinafter, gNB 100A) and a radio base station 100B (hereinafter, gNB 100B). Note that the specific configuration of the wireless communication system 10, including the number of gNBs and UEs, is not limited to the example shown in FIG.
[0014] The NG-RAN 20 actually includes a plurality of NG-RAN nodes, specifically, gNBs (or ng-eNBs), and is connected to a 5G-compliant core network (5GC, not shown). The NG-RAN 20 and the 5GC may be simply referred to as a "network."
[0015] The gNB100 and gNB100B are radio base stations conforming to 5G, and perform radio communication conforming to 5G with the UE 200. The gNB100, gNB100B, and UE 200 are capable of supporting Massive MIMO (Multiple-Input Multiple-Output), which generates a more directional beam BM by controlling radio signals transmitted from multiple antenna elements, Carrier Aggregation (CA), which uses a bundle of multiple component carriers (CC), and Dual Connectivity (DC), which simultaneously communicates between the UE and each of two NG-RAN Nodes.
[0016] The wireless communication system 10 also supports a plurality of frequency ranges (FR).
[0017] 2, the wireless communication system 10 supports FR1 and FR2. The frequency bands of each FR are as follows.
[0018] FR1: 410MHz~7.125GHz FR2: 24.25GHz~52.6GHz FR1 may use a Sub-Carrier Spacing (SCS) of 15, 30 or 60 kHz and a bandwidth (BW) of 5 to 100 MHz. FR2 is a higher frequency than FR1, and may use an SCS of 60 or 120 kHz (240 kHz may be included) and a bandwidth (BW) of 50 to 400 MHz.
[0019] The SCS may be interpreted as a numerology, which is defined in 3GPP TS38.300 and corresponds to one subcarrier interval in the frequency domain.
[0020] Furthermore, the wireless communication system 10 also supports a frequency band higher than the FR2 frequency band. Specifically, the wireless communication system 10 supports a frequency band exceeding 52.6 GHz up to 114.25 GHz. For convenience, such a high frequency band may be referred to as "FR2x."
[0021] To solve this problem, when using a band above 52.6 GHz, Cyclic Prefix-Orthogonal Frequency Division Multiplexing (CP-OFDM) / Discrete Fourier Transform - Spread (DFT-S-OFDM) with a larger Sub-Carrier Spacing (SCS) may be applied.
[0022] FIG. 3 shows an example of the configuration of radio frames, subframes, and slots used in the radio communication system 10. In FIG.
[0023] As shown in Fig. 3, one slot is composed of 14 symbols, and the larger (wider) the SCS is, the shorter the symbol period (and slot period) is. The SCS is not limited to the interval (frequency) shown in Fig. 3. For example, 480 kHz, 960 kHz, etc. may be used.
[0024] Also, the number of symbols constituting one slot does not necessarily have to be 14 (for example, 28 or 56 symbols). Furthermore, the number of slots per subframe may differ depending on the SCS.
[0025] 3 may be called a time domain, a symbol period, a symbol time, etc. The frequency direction may be called a frequency domain, a resource block, a subcarrier, a BWP (Bandwidth part), etc.
[0026] (2) Functional block configuration of wireless communication system Next, a description will be given of a functional block configuration of the wireless communication system 10. Specifically, a functional block configuration of the UE 200 will be described.
[0027] Fig. 4 is a functional block diagram of the UE 200. As shown in Fig. 4, the UE 200 includes a radio signal transmitting / receiving unit 210, an amplifier unit 220, a modulation / demodulation unit 230, a control signal / reference signal processing unit 240, an encoding / decoding unit 250, a data transmitting / receiving unit 260, and a control unit 270.
[0028] The radio signal transmission / reception unit 210 transmits and receives radio signals conforming to NR. The radio signal transmission / reception unit 210 supports Massive MIMO, CA that uses a bundle of multiple CCs, and DC that simultaneously communicates between a UE and each of two NG-RAN nodes.
[0029] The amplifier unit 220 is configured by a PA (Power Amplifier) / LNA (Low Noise Amplifier) etc. The amplifier unit 220 amplifies the signal output from the modem unit 230 to a predetermined power level. The amplifier unit 220 also amplifies the RF signal output from the wireless signal transmitting / receiving unit 210.
[0030] The modem unit 230 performs data modulation / demodulation, transmission power setting, resource block allocation, etc. for each predetermined communication destination (gNB100 or another gNB). The modem unit 230 may apply Cyclic Prefix-Orthogonal Frequency Division Multiplexing (CP-OFDM) / Discrete Fourier Transform - Spread (DFT-S-OFDM). Furthermore, DFT-S-OFDM may be used not only for uplink (UL) but also for downlink (DL).
[0031] The control signal / reference signal processor 240 executes processing related to various control signals transmitted and received by the UE 200, and processing related to various reference signals transmitted and received by the UE 200.
[0032] Specifically, the control signal / reference signal processor 240 receives various control signals, for example, radio resource control layer (RRC) control signals, transmitted from the gNB 100 via a predetermined control channel. In addition, the control signal / reference signal processor 240 transmits various control signals to the gNB 100 via a predetermined control channel.
[0033] The control signal / reference signal processor 240 executes processing using reference signals (RS) such as a Demodulation Reference Signal (DMRS) and a Phase Tracking Reference Signal (PTRS).
[0034] DMRS is a known reference signal (pilot signal) between a base station and a terminal for estimating a fading channel used for data demodulation. PTRS is a terminal-specific reference signal for estimating phase noise, which is an issue in high frequency bands.
[0035] In addition to the DMRS and PTRS, the reference signals may include a Channel State Information-Reference Signal (CSI-RS), a Sounding Reference Signal (SRS), and a Positioning Reference Signal (PRS) for position information.
[0036] The channels include a control channel and a data channel. The control channels include a PDCCH (Physical Downlink Control Channel), a PUCCH (Physical Uplink Control Channel), a RACH (Random Access Channel), Downlink Control Information (DCI) including a Random Access Radio Network Temporary Identifier (RA-RNTI), and a Physical Broadcast Channel (PBCH).
[0037] The data channel includes a physical downlink shared channel (PDSCH) and a physical uplink shared channel (PUSCH), etc. Data means data transmitted via the data channel. The data channel may be read as a shared channel.
[0038] In an embodiment, the control signal / reference signal processing unit 240 constitutes a communication unit that performs data communication with a network (e.g., NG-RAN 20) via a second component carrier (hereinafter, second CC) different from a first component carrier (hereinafter, first CC).
[0039] The control signal / reference signal processor 240 uses the first CC or the second CC to transmit uplink control information (UCI) related to the second CC to the network.
[0040] Specifically, control signal / reference signal processor 240 may transmit UCI related to the second CC using the first CC (operation example 1, described later).
[0041] When a specified condition is satisfied, the control signal / reference signal processing unit 240 may transmit UCI relating to at least one of the first CC and the second CC to the network by simultaneous transmission of specified physical uplink channels in the first CC and the second CC (operation examples 2 and 5 described below).
[0042] When a predetermined condition is satisfied, the control signal / reference signal processor 240 discards the transmission of a predetermined physical uplink channel. At this time, the control signal / reference signal processor 240 may transmit UCI related to at least one of the first CC and the second CC by using at least one of the first CC and the second CC (operation examples 3 and 6 described later).
[0043] When a predetermined condition is satisfied, the control signal and reference signal processor 240 may multiplex UCI related to at least one of the first CC and the second CC onto a predetermined physical uplink channel and transmit the UCI to the network (operation examples 4 and 7 described below).
[0044] The predetermined condition may include a first predetermined condition in which a PUCCH in the first CC collides with a PUCCH in the second CC. The predetermined condition may include a second predetermined condition in which a PUCCH in at least one of the first CC and the second CC collides with a PUSCH in the second CC. Note that the collision in the present disclosure may be two or more channels being included in the same time unit, for example, two or more channels being indicated to be transmitted in the same slot.
[0045] Here, in operation examples 4 and 7 described below, when a third predetermined condition is satisfied, the control signal and reference signal processor 240 may multiplex the UCI related to the second CC onto a predetermined physical uplink channel and transmit the same to the network.
[0046] The third predetermined condition may include a condition that the UCI for the first CC is independently decodable from the UCI for the second CC.
[0047] The third predetermined condition may include a condition that the codebook of UCI for the second CC is generated separately from the codebook of UCI for the first CC.
[0048] In the following, the first CC will be described as a CC belonging to a first frequency range (e.g., 52.6 GHz or less), and the second CC will be described as a CC belonging to a second frequency range (e.g., 52.6 GHz or more) that is higher than the first frequency range (e.g., 52.6 GHz or less).
[0049] Furthermore, the parameters related to the first frequency range are distinguished as “non-above” and the parameters related to the second frequency range are distinguished as “above.” For example, a first CC belonging to the first frequency range is called a non-above CC, and a second CC belonging to the second frequency range is called an above CC.
[0050] The UCI includes at least a response confirmation (HARQ-ACK) corresponding to data (for example, one TB). The UCI may include a Scheduling Request (SR) requesting resource scheduling, and may include Channel State Information (CSI) representing the channel state. In the following, the HARQ-ACK will be mainly described.
[0051] The encoding / decoding unit 250 performs data division / concatenation and channel coding / decoding, etc. for each predetermined communication destination (gNB100 or another gNB).
[0052] Specifically, the encoding / decoding unit 250 divides the data output from the data transmitting / receiving unit 260 into pieces of a predetermined size, performs channel coding on the divided data, and decodes the data output from the modem unit 230 and concatenates the decoded data.
[0053] The data transmission / reception unit 260 transmits and receives Protocol Data Units (PDUs) and Service Data Units (SDUs). Specifically, the data transmission / reception unit 260 performs assembly / disassembly of PDUs / SDUs in multiple layers (such as a Medium Access Control layer (MAC), a Radio Link Control layer (RLC), and a Packet Data Convergence Protocol layer (PDCP)). In addition, the data transmission / reception unit 260 performs data error correction and retransmission control based on a hybrid automatic repeat request (Hybrid ARQ).
[0054] The control unit 270 controls each functional block constituting the UE 200. In particular, in this embodiment, the control unit 270 controls communication of the non-above CC and the above CC.
[0055] (3) Example of operation (3.1) Example 1 In the operation example 1, the UE 200 transmits UCI related to the above CC using the non-above CC. That is, the operation example 1 is an operation example in which the UE 200 transmits HARQ-ACK related to the above CC using the non-above CC. Here, a case is illustrated in which the UE 200 receives data via a PDSCH mapped to the above CC and transmits HARQ-ACK corresponding to the received data.
[0056] As shown in Fig. 5, in step S10, the UE 200 receives an RRC message from the NG-RAN 20. The RRC message includes a resource configuration used for transmitting the HARQ-ACK. In the first operation example, the resource configuration may include a PUCCH-Config used in the non-above CC, or may include a PUSCH-Config used in the non-above CC.
[0057] In step S11, the UE 200 receives DCI from the NG-RAN 20 via a PDCCH that is mapped to the non-above CC and one or more CCs included in the above CC.
[0058] In step S12, the UE 200 receives data from the NG-RAN 20 via a PDSCH mapped to the above CC.
[0059] In step S13, UE 200 transmits a HARQ-ACK for the above CC to NG-RAN 20 via a non-above CC. The HARQ-ACK for the above CC may be transmitted via a PUCCH mapped to the non-above CC, or may be transmitted via a PUSCH mapped to the non-above CC.
[0060] In such a case, a special cell (SpCell) may not be configured for the above CC. The SpCell may be a primary cell (PCell) belonging to a master cell group (MCG), a primary secondary cell (PSCell) belonging to a secondary cell group (SCG), or a PCell other than these.
[0061] Alternatively, even if a Special Cell (SpCell) is configured for an above CC, the PUCCH may be configured as a non-above CC, not as an above CC.
[0062] Alternatively, a secondary cell (SCell) supporting PUCCH may not be configured for the above CC. That is, PUCCH may be configured for a non-above CC, not for an above CC.
[0063] (3.2) Example 2 In the operation example 2, when a predetermined condition is satisfied, the UE 200 transmits UCI related to the above CC to the network by simultaneously transmitting a predetermined physical uplink channel in the non-above CC and the above CC. The predetermined physical uplink channel is a PUCCH in the non-above CC and the above CC. The UCI related to the above CC may be included in the PUCCH in the above CC. That is, the operation example 2 is an operation example in which a PUCCH is transmitted using the above CC. For example, the PUCCH may include a HARQ-ACK related to the above CC. Here, a case is illustrated in which the UE 200 receives data via a PDSCH mapped to the non-above CC and the above CC, and transmits a HARQ-ACK corresponding to the received data.
[0064] However, multiplexing of HARQ-ACK for above CC and HARQ-ACK for non-above CC is not allowed. For example, when PUCCH in above CC and PUCCH in non-above CC collide at least in the time domain, UCI included in PUCCH in above CC and UCI included in PUCCH in non-above CC may not be multiplexed in the same channel. In this case, simultaneous transmission of PUCCH in above CC and PUCCH in non-above CC may be allowed.
[0065] 6, in step S20, the UE 200 receives an RRC message from the NG-RAN 20. The RRC message includes a resource configuration used for transmitting the HARQ-ACK. In the second operation example, the resource configuration includes PUCCH-Config used in the non-above CC and the above CC.
[0066] In step S21, the UE 200 receives DCI from the NG-RAN 20 via a PDCCH that is mapped to the non-above CC and one or more CCs included in the above CC.
[0067] In step S22, the UE 200 receives data from the NG-RAN 20 via a PDSCH mapped to the non-above CC and the above CC.
[0068] In step S23A, UE 200 transmits a HARQ-ACK for the above CC to NG-RAN 20 via a PUCCH mapped to the above CC. In step S23B, UE 200 transmits a HARQ-ACK for the non-above CC to NG-RAN 20 via a PUCCH or PUSCH mapped to the non-above CC.
[0069] Here, steps S23A and S23B are scheduled by the DCI received in step S21. In other words, simultaneous transmission of a HARQ-ACK for an above CC and a HARQ-ACK for a non-above CC is permitted.
[0070] (3.3) Example 3 In the operation example 3, when a predetermined condition is satisfied, the UE 200 discards the transmission of a predetermined physical uplink channel, and then transmits UCI related to the above CC using the above CC. The predetermined physical uplink channel is a PUCCH in a non-above CC. However, the transmission of the PUCCH in the non-above CC may be discarded without being discarded. That is, the operation example 3 is an operation example in which a PUCCH is transmitted using an above CC, or a PUCCH transmission using an above CC is discarded. For example, the PUCCH may include a HARQ-ACK related to the above CC. Here, a case is illustrated in which the UE 200 receives data via a PDSCH mapped to a non-above CC and an above CC, and transmits a HARQ-ACK corresponding to the received data. However, multiplexing of the HARQ-ACK related to the above CC and the HARQ-ACK related to the non-above CC is not permitted. For example, when a PUCCH in an above CC and a PUCCH in a non-above CC collide at least in the time domain, the UCI included in the PUCCH in the above CC and the UCI included in the PUCCH in the non-above CC may not be multiplexed in the same channel. In this case, only one of the PUCCH in the above CC and the PUCCH in the non-above CC may be transmitted.
[0071] 7, in step S30, the UE 200 receives an RRC message from the NG-RAN 20. Since step S30 is similar to step S20 described above, details of step S30 will be omitted.
[0072] In step S31, the UE 200 receives DCI from the NG-RAN 20 via a PDCCH that is mapped to one or more CCs included in the non-above CCs and the above CCs.
[0073] In step S32, the UE 200 receives data from the NG-RAN 20 via a PDSCH mapped to the non-above CC and the above CC.
[0074] In step S33, UE 200 transmits either the HARQ-ACK for the above CC or the HARQ-ACK for the non-above CC to NG-RAN 20. In other words, UE 200 discards the other of the HARQ-ACK for the above CC or the HARQ-ACK for the non-above CC. The HARQ-ACK for the above CC is transmitted via a PUCCH mapped to the above CC. The HARQ-ACK for the non-above CC may be transmitted via a PUCCH or a PUSCH mapped to the non-above CC.
[0075] (3.4) Example 4 In the operation example 4, when a first predetermined condition that a PUCCH in a non-above CC and a PUCCH in an above CC collide is satisfied, the UE 200 multiplexes the UCI related to the above CC into a predetermined physical uplink channel and transmits the UCI to the network. The predetermined physical uplink channel may be a PUCCH in an above CC or a PUCCH in a non-above CC. That is, the operation example 4 is an operation example in which a HARQ-ACK related to an above CC is transmitted using a non-above CC or an above CC. Here, a case is illustrated in which the UE 200 receives data via a PDSCH mapped to a non-above CC and an above CC, and transmits a HARQ-ACK corresponding to the received data. Furthermore, multiplexing of a HARQ-ACK related to an above CC and a HARQ-ACK related to a non-above CC is permitted. For example, when a PUCCH in an above CC and a PUCCH in a non-above CC collide at least in the time domain, the UCI included in the PUCCH in the above CC and the UCI included in the PUCCH in the non-above CC may be multiplexed into the same PUCCH.
[0076] 8, in step S40, the UE 200 receives an RRC message from the NG-RAN 20. The RRC message includes a resource configuration used for transmitting the HARQ-ACK. In the fourth operation example, the resource configuration includes a PUCCH-Config used in the above CC.
[0077] In step S41, the UE 200 receives DCI from the NG-RAN 20 via a PDCCH that is mapped to one or more CCs included in the non-above CCs and the above CCs.
[0078] In step S42, the UE 200 receives data from the NG-RAN 20 via a PDSCH mapped to the non-above CC and the above CC.
[0079] In step S43, UE 200 multiplexes the HARQ-ACK for the non-above CC and the above CC onto the PUCCH, and transmits the multiplexed HARQ-ACK to NG-RAN 20 via the PUCCH mapped to the non-above CC or the above CC.
[0080] In the operation example 4, at least one of the following parameters may be specified independently of the HARQ-ACK for the above CC. That is, the UCI for the above CC is decodable independently of the UCI for the non-above CC (an example in which the third predetermined condition is satisfied).
[0081] Parameter A: payload size of HARQ-ACK for non-above Parameter B: PUCCH resource set or resource Parameter C: coding rate of HARQ-ACK for non-above Parameter D: RE (Resource Element) to which the HARQ-ACK for non-above is mapped Parameter E: Number of PRBs (Physical Resource Blocks) used in PUCCH For example, the multiplexed HARQ-ACK resources are mapped to a PUCCH belonging to a non-above CC or an above CC in the following procedure.
[0082] The payload size (parameter A) of the HARQ-ACK for non-above is N bits. The payload size of the HARQ-ACK for above is M bits. The payload size of the HARQ-ACK for above is assumed to be M2 bits. M2 bits is a value that can be calculated by a method agreed upon between the UE 200 and the NG-RAN 20. For example, M2 bits may be assumed based on a Downlink Assignment Index (DAI) for above. The above-mentioned parameters B, C, and D are determined based on N+M2 bits.
[0083] Under this background, N bits of HARQ-ACK for non-above are mapped to some REs of PUCCH, and M bits of HARQ-ACK for above are mapped to the remaining REs of PUCCH.
[0084] Alternatively, the N bits of HARQ-ACK for non-above may be mapped to all REs of PUCCH, and may be overwritten (punctured) by the M bits of HARQ-ACK for above in some REs of PUCCH. The coding rate for non-above may be a value not exceeding a predetermined threshold. The RE to be overwritten may be preferentially selected as an RE to which at least one of SR and CSI for non-above is mapped. Conversely, the M bits of HARQ-ACK for above may be mapped to all REs of PUCCH, and may be overwritten (punctured) by the N bits of HARQ-ACK for non-above in some REs of PUCCH.
[0085] In the fourth operational example, a codebook for HARQ-ACK for above CC may be generated separately from a codebook for HARQ-ACK for non-above CC (an example in which the third predetermined condition is satisfied). This allows multiplexing of HARQ-ACK for above CC and HARQ-ACK for non-above CC. In such a case, the DAI for PDSCH for above CC may be defined and calculated separately from the DAI for PDSCH for non-above CC. Only a (semi-)static HARQ-ACK codebook may be supported for HARQ-ACK for above CC. In such a case, the (semi-)static HARQ-ACK codebook may not be applied to HARQ-ACK for non-above CC.
[0086] (3.5) Example 5 In the operation example 5, when a predetermined condition is satisfied, the UE 200 transmits UCI related to at least one of the non-above CC and the above CC to the network by simultaneously transmitting a predetermined physical uplink channel in the non-above CC and / or the above CC. The predetermined physical uplink channel is a PUCCH in the non-above CC or the above CC and a PUSCH in the above CC. The UCI related to at least one of the non-above CC and the above CC may be included in the PUCCH in the non-above CC or the above CC. That is, the operation example 5 is an operation example in which at least one of the above CC and the HARQ-ACK related to the non-above is transmitted by using the non-above CC or the above CC. Here, a case is illustrated in which UE 200 receives data via PDSCHs mapped to non-above CCs and above CCs and transmits HARQ-ACKs corresponding to the received data, but it may be applied to a case in which data is received via PDSCHs mapped to either non-above CCs or above CCs. However, it is not permitted to multiplex HARQ-ACKs related to at least one of above CCs and non-above onto PUSCHs in above CCs. For example, when PUCCHs in non-above CCs and PUSCHs in above CCs collide at least in the time domain, UCIs included in PUCCHs in non-above CCs may not be multiplexed onto PUSCHs in above CCs. At this time, simultaneous transmission of PUCCHs in non-above CCs and PUSCHs in above CCs may be permitted. PUCCHs in non-above CCs may be replaced with PUCCHs in above CCs.
[0087] As shown in Fig. 9, in step S50, the UE 200 receives an RRC message from the NG-RAN 20. The RRC message includes a resource configuration used for transmitting the HARQ-ACK. In the operation example 5, the resource configuration includes a PUSCH-Config used in the above CC. The resource configuration includes a PUCCH-Config or a PUSCH-Config used in the non-above CC.
[0088] In step S51, the UE 200 receives DCI from the NG-RAN 20 via a PDCCH that is mapped to one or more CCs included in the non-above CCs and the above CCs.
[0089] In step S52, the UE 200 receives data from the NG-RAN 20 via a PDSCH mapped to the non-above CC and the above CC.
[0090] In step S53A, UE 200 transmits HARQ-ACKs for the non-above CC and above CC to NG-RAN 20 via a PUCCH mapped to the non-above CC or above CC. In step S53B, UE 200 transmits HARQ-ACKs for the non-above CC and above CC to NG-RAN 20 via a PUSCH mapped to the above CC.
[0091] Here, steps S53A and S53B are scheduled by the DCI received in step S51. In other words, simultaneous transmission of a PUCCH in a non-above CC or an above CC and a PUSCH in an above CC is permitted.
[0092] (3.6) Example 6 In the sixth operation example, when a predetermined condition is satisfied, the UE 200 transmits UCI related to at least one of the non-above CC and the above CC using the non-above CC or the above CC after discarding the transmission of the predetermined physical uplink channel. The predetermined physical uplink channel is a PUCCH in the non-above CC or the above CC. However, the transmission of the PUCCH in the non-above CC or the above CC may not be discarded, and the transmission of the PUSCH in the above CC may be discarded. That is, the sixth operation example is an operation example in which at least one of the HARQ-ACK related to the above CC and the non-above is transmitted using the non-above CC or the above CC, or the transmission of the PUCCH in the non-above CC or the above CC is discarded. Here, a case is illustrated in which UE 200 receives data via PDSCHs mapped to non-above CCs and above CCs and transmits HARQ-ACKs corresponding to the received data, but it may also be applied to a case in which data is received via PDSCHs mapped to either non-above CCs or above CCs. However, it is not permitted to multiplex HARQ-ACKs related to at least one of above CCs and non-above onto PUSCHs in above CCs. For example, when PUCCHs in non-above CCs and PUSCHs in above CCs collide at least in the time domain, UCIs included in PUCCHs in non-above CCs may not be multiplexed onto PUSCHs in above CCs. In this case, only one of PUCCHs in non-above CCs and PUSCHs in above CCs may be transmitted. PUCCHs in non-above CCs may be replaced with PUCCHs in above CCs.
[0093] 10, in step S60, the UE 200 receives an RRC message from the NG-RAN 20. Since step S60 is similar to step S50 described above, details of step S60 will be omitted.
[0094] In step S61, the UE 200 receives DCI from the NG-RAN 20 via a PDCCH that is mapped to one or more CCs included in the non-above CCs and the above CCs.
[0095] In step S62, the UE 200 receives data from the NG-RAN 20 via a PDSCH mapped to the non-above CC and the above CC.
[0096] In step S63, UE 200 transmits either the PUCCH including the HARQ-ACK for the non-above CC and the above CC or the PUSCH in the above CC to NG-RAN 20. In other words, UE 200 discards the other of the PUCCH including the HARQ-ACK for the above CC and the HARQ-ACK for the non-above CC and the PUSCH in the above CC.
[0097] (3.7) Example 7 In the seventh operation example, when a second predetermined condition is satisfied in which a PUCCH in at least one of the non-above CC and the above CC and a PUSCH in the above CC collide with each other, the UE 200 multiplexes UCI related to at least one of the non-above CC and the above CC into a predetermined physical uplink channel and transmits the UCI to the network. The predetermined physical uplink channel is a PUSCH in the above CC. That is, the seventh operation example is an operation example in which the UE 200 transmits HARQ-ACK related to the non-above CC or the above CC using the above CC. Here, a case is illustrated in which the UE 200 receives data via a PDSCH mapped to the non-above CC and the above CC, and transmits a HARQ-ACK corresponding to the received data, but the present invention may also be applied to a case in which the UE 200 receives data via a PDSCH mapped to either the non-above CC or the above CC. Furthermore, at least one of a HARQ-ACK for an above CC and a HARQ-ACK for a non-above CC is permitted to be multiplexed onto a PUSCH in an above CC.
[0098] 11, in step S70, the UE 200 receives an RRC message from the NG-RAN 20. The RRC message includes a resource configuration used for transmitting the HARQ-ACK. In the seventh operation example, the resource configuration includes a PUSCH-Config used in the above CC.
[0099] In step S71, the UE 200 receives DCI from the NG-RAN 20 via a PDCCH that is mapped to one or more CCs included in the non-above CCs and the above CCs.
[0100] In step S72, the UE 200 receives data from the NG-RAN 20 via a PDSCH mapped to the non-above CC and the above CC.
[0101] In step S73, when the UE 200 multiplexes the HARQ-ACKs for the non-above CCs and the above CCs onto the PUCCH, the UE 200 detects that the HARQ-ACKs collide with the PUSCH mapped to the above CCs in the time domain. In this case, the UE 200 multiplexes the HARQ-ACK onto the PUSCH and transmits the multiplexed HARQ-ACK to the NG-RAN 20 via the PUSCH.
[0102] In the seventh operation example, at least one of the following parameters is specified independently of the HARQ-ACK for the above CC. That is, at least one of the UCI and the UL-SCH for the non-above CC is decodable independently of the UCI for the above CC (an example in which the third predetermined condition is satisfied).
[0103] Parameter F: coding rate of at least one of HARQ-ACK and UL-SCH for non-above Parameter G: RE (Resource Element) to which at least one of HARQ-ACK and UL-SCH related to non-above is mapped For example, the multiplexed HARQ-ACK resources are mapped to the PUSCH belonging to the above CC in the following procedure.
[0104] The payload size (parameter F) of at least one of the HARQ-ACK and UL-SCH for non-above is N' bits. The payload size of the HARQ-ACK for above is M bits. The payload size of the HARQ-ACK for above is assumed to be M2 bits. M2 bits is a value that can be calculated by a method agreed upon between the UE 200 and the NG-RAN 20. For example, M2 bits may be assumed based on a DAI (Downlink Assignment Index) for above. The above-mentioned parameters F and G are determined based on N'+M2 bits.
[0105] Under this background, at least one of N' bits of non-above HARQ-ACK and UL-SCH is mapped to some REs of PUSCH, and M bits of above HARQ-ACK is mapped to the remaining REs of PUSCH.
[0106] Alternatively, at least one of N' bits of non-above HARQ-ACK and UL-SCH may be mapped to at least some REs of PUSCH, and may be overwritten (punctured) by M bits of HARQ-ACK for above in some REs of PUSCH. The coding rate for non-above may be a value not exceeding a predetermined threshold. The RE to be overwritten may be preferentially selected as an RE to which at least one of non-above SR and CSI is mapped. Conversely, N bits of HARQ-ACK for non-above may be mapped to at least some REs of PUSCH, and may be overwritten (punctured) by at least one of N' bits of HARQ-ACK and UL-SCH for above in some REs of PUSCH.
[0107] In the seventh operational example, similarly to the fourth operational example, the codebook of the HARQ-ACK for the above CC may be generated separately from the codebook of the HARQ-ACK for the non-above CC (one example in which the third predetermined condition is satisfied). This allows multiplexing of the HARQ-ACK for the above CC and the HARQ-ACK for the non-above CC. In such a case, the DAI of the PDSCH for the above CC may be defined and calculated separately from the DAI of the PDSCH for the non-above CC. Only a (semi-)static HARQ-ACK codebook may be supported for the HARQ-ACK for the above CC. In such a case, the (semi-)static HARQ-ACK codebook may not be applied to the HARQ-ACK for the non-above CC.
[0108] (4) Actions and Effects In the embodiment, the UE 200 transmits the HARQ-ACK for the above CC to the network by using the non-above CC. With this configuration, it is possible to suppress a decrease in the reliability of the HARQ-ACK for the above CC.
[0109] In the embodiment, the UE 200 executes the predetermined transmission shown in the operation example 2 to the operation example 7 when a predetermined condition is satisfied. For example, as described in the operation examples 2 and 5, when simultaneous transmission of the predetermined physical uplink channel in the non-above CC and the above CC is permitted, the UE 200 transmits the HARQ-ACK related to the above CC by the simultaneous transmission of the predetermined physical uplink channel. Alternatively, as described in the operation examples 3 and 6, when simultaneous transmission of the physical uplink channel in the non-above CC and the above CC is not permitted, the UE 200 discards the transmission of the predetermined physical uplink channel. At this time, the UE 200 transmits the HARQ-ACK related to at least one of the non-above CC and the above CC by using the non-above CC or the above CC. Alternatively, in the operation example 7, when a predetermined condition is satisfied, the UE 200 multiplexes the UCI related to at least one of the non-above CC and the above CC into the predetermined physical uplink channel and transmits the UCI to the network. According to such a configuration, it is possible to suppress a decrease in reliability of HARQ-ACK for non-above CCs and above CCs.
[0110] Furthermore, a third predetermined condition under which multiplexing is permitted is defined. With this configuration, it is possible to suppress a decrease in reliability of HARQ-ACK related to non-above CCs.
[0111] As described above, by suppressing degradation in reliability of HARQ-ACK for non-above CCs and above CCs, it is possible to suppress error rates of ACK to NACK errors, NACK to ACK errors, DTX to ACK errors, etc. to a desired error rate or lower.
[0112] [Change Example 1] Modification 1 of the embodiment will be described below, with differences from the embodiment being described below.
[0113] Specifically, the UE 200 transmits an information element indicating whether or not it has the capability to execute at least one of the above-mentioned operation examples 1 to 7 to the network (NG-RAN 20). Specifically, as shown in Fig. 12, in step S80, the UE 200 transmits (reports) to the NG-RAN 20 a UE capability including an information element indicating whether or not it has the capability to execute at least one of the operation examples 1 to 7. For example, the UE 200 may transmit a UE capability including an information element indicating whether or not it has the function to execute the simultaneous transmission described in the operation example 2 or operation example 5.
[0114] Although not particularly limited, the UE 200 may execute step S80 when an RRC connection is established with the NG-RAN 20. In other words, step S80 may be executed before the processes shown in Figs. 5 to 11.
[0115] [Change Example 2] The second modification of the embodiment will be described below, with differences from the embodiment being described below.
[0116] In Modification 2, a PUCCH Config related to above CC will be described. The PUCCH Config is set by higher layer parameters. The PUCCH Config may be an information element included in an RRC message.
[0117] First, the PUCCH Config for the above CC may be the same as the PUCCH Config for the non-above CC, in other words, the PUCCH Config may be shared between the above CC and the non-above CC.
[0118] Secondly, the PUCCH Config for the above CC may be set separately from the PUCCH Config for the non-above CC. In a case where multiplexing of HARQ-ACK for non-above CC and above CC is permitted (for example, the above-mentioned operation example 4 or operation example 7), the PUCCH Config for the non-above CC (or the PUCCH Config for the above CC) may be applied. Alternatively, the PUCCH Config specified by the most recent DCI used for multiplexing of HARQ-ACK may be used.
[0119] Thirdly, the PUCCH Config for above CC is configured for HARQ-ACK, but does not need to be configured for SR and CSI (Periodic CSI, Semi-persistent CSI, Aperiodic CSI).
[0120] [Change Example 3] The third modification of the embodiment will be described below, focusing on the differences from the embodiment.
[0121] In modification example 3, a case where HARQ-ACK for non-above CC and above CC is multiplexed, or HARQ-ACK for at least one of non-above CC and above CC is multiplexed onto a PUSCH in an above CC (for example, operation example 4 or operation example 7 described above) is further described.
[0122] In such a case, DCI for scheduling a PDSCH or a PUSCH mapped to a non-above CC may include the following information elements.
[0123] For example, the DCI may include an information element (e.g., 1-bit information) indicating whether or not the HARQ-ACK for the above CC is multiplexed. The DCI may include an information element (e.g., X-bit information) indicating the number of bits of the HARQ-ACK for the above CC. Such an information element may be an information element indicating the total resources specified by the most recent DAI for the above CC.
[0124] If the above-mentioned information element is included in the DCI, multiplexing of HARQ-ACK for non-above CC and above CC may be applied. That is, the third predetermined condition may include that the above-mentioned information element is included in the DCI. On the other hand, if the above-mentioned information element is not included in the DCI, multiplexing of HARQ-ACK for non-above CC and above CC may not be applied.
[0125] [Other embodiments] The present invention has been described above in accordance with the embodiments, but the present invention is not limited to these descriptions, and it will be obvious to those skilled in the art that various modifications and improvements are possible.
[0126] In the above embodiment, the case where the first CC is a non-above CC and the second CC is an above CC is exemplified. However, the embodiment is not limited to this. For example, the first CC may be a CC other than the specific CC, and the second CC may be the specific CC. The specific CC may be a CC to which the transmission of HARQ-ACK is not set. In addition, the first frequency range to which the first CC belongs is not limited to 52.6 GHz or less, and the second frequency range to which the second CC belongs is not limited to 52.6 GHz or more.
[0127] In the above-described embodiment, HARQ-ACK has been described as an example of UCI. However, the embodiment is not limited to this. HAQR-ACK may be read as UCI. The above-described operation example 1 to operation example 7 may be applied for each UCI type. For example, operation example 1 may be applied to HAQR-ACK, and an operation example selected from operation examples 2 to 7 may be applied to SR and CSI.
[0128] In the above-described embodiment, the PUCCH may be interpreted as the control information transmitted via the PUCCH. For example, the transmission of the PUCCH may be interpreted as the transmission of the UCI or the transmission of the HARQ-ACK.
[0129] The block diagram (FIG. 4) used in the description of the above-mentioned embodiment shows functional blocks. These functional blocks (components) are realized by any combination of at least one of hardware and software. Furthermore, the method of realizing each functional block is not particularly limited. That is, each functional block may be realized by using one device that is physically or logically combined, or may be realized by using two or more devices that are physically or logically separated and directly or indirectly connected (for example, by wire, wirelessly, etc.). The functional block may be realized by combining the one device or the multiple devices with software.
[0130] Functions include, but are not limited to, judgment, determination, judgment, calculation, computation, processing, derivation, investigation, search, confirmation, reception, transmission, output, access, resolution, selection, selection, establishment, comparison, assumption, expectation, consideration, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, and assignment. For example, a functional block (component) that performs the function of transmission is called a transmitting unit or a transmitter. As described above, there is no particular limitation on the method of realization of each of these.
[0131] Furthermore, the above-mentioned UE 200 (the device) may function as a computer that performs processing of the wireless communication method of the present disclosure. Fig. 13 is a diagram showing an example of a hardware configuration of the device. As shown in Fig. 13, the device may be configured as a computer device including a processor 1001, a memory 1002, a storage 1003, a communication device 1004, an input device 1005, an output device 1006, and a bus 1007.
[0132] In the following description, the term "apparatus" may be interpreted as a circuit, a device, a unit, etc. The hardware configuration of the apparatus may be configured to include one or more of the apparatuses shown in the drawings, or may be configured to exclude some of the apparatuses.
[0133] Each functional block of the device (see FIG. 4) is realized by any hardware element of the computer device, or a combination of the hardware elements.
[0134] In addition, each function in the device is realized by loading a specific software (program) onto hardware such as the processor 1001, memory 1002, etc., so that the processor 1001 performs calculations, controls communication by the communication device 1004, and controls at least one of reading and writing of data in the memory 1002 and storage 1003.
[0135] The processor 1001 controls the entire computer by running, for example, an operating system, and may be configured by a central processing unit (CPU) including an interface with peripheral devices, a control unit, an arithmetic unit, a register, and the like.
[0136] Furthermore, the processor 1001 reads out programs (program codes), software modules, data, etc. from at least one of the storage 1003 and the communication device 1004 into the memory 1002, and executes various processes according to these. As the programs, programs that cause a computer to execute at least a part of the operations described in the above-mentioned embodiments are used. Furthermore, the above-mentioned various processes may be executed by one processor 1001, or may be executed simultaneously or sequentially by two or more processors 1001. The processor 1001 may be implemented by one or more chips. The programs may be transmitted from a network via a telecommunications line.
[0137] The memory 1002 is a computer-readable recording medium, and may be configured by at least one of, for example, a Read Only Memory (ROM), an Erasable Programmable ROM (EPROM), an Electrically Erasable Programmable ROM (EEPROM), a Random Access Memory (RAM), etc. The memory 1002 may also be called a register, a cache, a main memory (primary storage device), etc. The memory 1002 can store a program (program code), a software module, etc., capable of executing a method according to an embodiment of the present disclosure.
[0138] Storage 1003 is a computer-readable recording medium, and may be composed of at least one of, for example, an optical disk such as a Compact Disc ROM (CD-ROM), a hard disk drive, a flexible disk, a magneto-optical disk (e.g., a compact disk, a digital versatile disk, a Blu-ray (registered trademark) disk), a smart card, a flash memory (e.g., a card, a stick, a key drive), a floppy (registered trademark) disk, a magnetic strip, and the like. Storage 1003 may be referred to as an auxiliary storage device. The above-mentioned recording medium may be, for example, a database, a server, or other suitable medium including at least one of memory 1002 and storage 1003.
[0139] The communication device 1004 is hardware (transmission / reception device) for performing communication between computers via at least one of a wired network and a wireless network, and is also called, for example, a network device, a network controller, a network card, or a communication module.
[0140] The communication device 1004 may be configured to include a high-frequency switch, a duplexer, a filter, a frequency synthesizer, and the like to realize, for example, at least one of Frequency Division Duplex (FDD) and Time Division Duplex (TDD).
[0141] The input device 1005 is an input device (e.g., a keyboard, a mouse, a microphone, a switch, a button, a sensor, etc.) that accepts input from the outside. The output device 1006 is an output device (e.g., a display, a speaker, an LED lamp, etc.) that performs output to the outside. The input device 1005 and the output device 1006 may be integrated into one device (e.g., a touch panel).
[0142] In addition, each device such as the processor 1001 and the memory 1002 is connected by a bus 1007 for communicating information. The bus 1007 may be configured using a single bus, or may be configured using different buses between each device.
[0143] Furthermore, the device may be configured to include hardware such as a microprocessor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a programmable logic device (PLD), a field programmable gate array (FPGA), etc., and some or all of the functional blocks may be realized by the hardware. For example, the processor 1001 may be implemented using at least one of these pieces of hardware.
[0144] Furthermore, the notification of information is not limited to the aspects / embodiments described in the present disclosure, and may be performed using other methods. For example, the notification of information may be performed by physical layer signaling (e.g., Downlink Control Information (DCI), Uplink Control Information (UCI)), higher layer signaling (e.g., RRC signaling, Medium Access Control (MAC) signaling, broadcast information (Master Information Block (MIB), System Information Block (SIB)), other signals, or a combination of these. Furthermore, the RRC signaling may be called an RRC message, and may be, for example, an RRC Connection Setup message, an RRC Connection Reconfiguration message, or the like.
[0145] Each aspect / embodiment described in the present disclosure may be applied to at least one of a system using Long Term Evolution (LTE), LTE-Advanced (LTE-A), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), Future Radio Access (FRA), New Radio (NR), W-CDMA (registered trademark), GSM (registered trademark), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20, Ultra-WideBand (UWB), Bluetooth (registered trademark), other suitable systems, and next-generation systems extended based on these. In addition, a combination of multiple systems (e.g., a combination of at least one of LTE and LTE-A and 5G, etc.) may be applied.
[0146] The order of the steps, sequences, flow charts, etc. of each aspect / embodiment described in this disclosure may be changed unless inconsistent. For example, the methods described in this disclosure present elements of various steps using an example order, and are not limited to the particular order presented.
[0147] In the present disclosure, a specific operation performed by a base station may be performed by its upper node in some cases. In a network consisting of one or more network nodes having a base station, it is clear that various operations performed for communication with a terminal may be performed by at least one of the base station and other network nodes other than the base station (e.g., MME or S-GW, etc., but are not limited to these). Although the above example illustrates a case in which there is one other network node other than the base station, it may also be a combination of multiple other network nodes (e.g., MME and S-GW).
[0148] Information, signals (information, etc.) may be output from a higher layer (or a lower layer) to a lower layer (or a higher layer), and may be input and output via multiple network nodes.
[0149] The input / output information may be stored in a specific location (e.g., memory) or may be managed using a management table. The input / output information may be overwritten, updated, or appended. The output information may be deleted. The input information may be transmitted to another device.
[0150] The determination may be based on a value represented by a single bit (0 or 1), a Boolean value (true or false), or a numerical comparison (e.g., comparison with a predetermined value).
[0151] Each aspect / embodiment described in this disclosure may be used alone, in combination, or switched according to execution. In addition, notification of specific information (e.g., notification that "X is the case") is not limited to being done explicitly, but may be done implicitly (e.g., not notifying the specific information).
[0152] Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.
[0153] Additionally, software, instructions, information, etc. may be transmitted or received over a transmission medium. For example, if the software is transmitted from a website, server, or other remote source using wired technologies (such as coaxial cable, fiber optic cable, twisted pair, Digital Subscriber Line (DSL)), and / or wireless technologies (such as infrared, microwave, etc.), then these wired and / or wireless technologies are included within the definition of transmission media.
[0154] The information, signals, etc. described in this disclosure may be represented using any of a variety of different technologies. For example, the data, instructions, commands, information, signals, bits, symbols, chips, etc. that may be referred to throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or magnetic particles, optical fields or photons, or any combination thereof.
[0155] In addition, the terms described in this disclosure and the terms necessary for understanding this disclosure may be replaced with terms having the same or similar meanings. For example, at least one of a channel and a symbol may be a signal (signaling). Also, a signal may be a message. Also, a component carrier (CC) may be called a carrier frequency, a cell, a frequency carrier, etc.
[0156] As used in this disclosure, the terms "system" and "network" are used interchangeably.
[0157] In addition, the information, parameters, etc. described in the present disclosure may be represented using absolute values, may be represented using relative values from a predetermined value, or may be represented using other corresponding information. For example, a radio resource may be indicated by an index.
[0158] The names used for the above-mentioned parameters are not limiting in any way. Furthermore, the formulas using these parameters may differ from those explicitly disclosed in this disclosure. The various channels (e.g., PUCCH, PDCCH, etc.) and information elements may be identified by any suitable names, and therefore the various names assigned to these various channels and information elements are not limiting in any way.
[0159] In this disclosure, terms such as "base station (BS)", "radio base station", "fixed station", "NodeB", "eNodeB (eNB)", "gNodeB (gNB)", "access point", "transmission point", "reception point", "transmission / reception point", "cell", "sector", "cell group", "carrier", "component carrier", etc. may be used interchangeably. A base station may also be referred to by terms such as a macro cell, a small cell, a femto cell, a pico cell, etc.
[0160] A base station can accommodate one or more (e.g., three) cells (also called sectors). When a base station accommodates multiple cells, the entire coverage area of the base station can be divided into multiple smaller areas, and each smaller area can also be provided with communication services by a base station subsystem (e.g., a small indoor base station (Remote Radio Head: RRH)).
[0161] The term "cell" or "sector" refers to part or all of the coverage area of a base station and / or a base station subsystem that provides communication services within that coverage.
[0162] In this disclosure, the terms "Mobile Station (MS)", "user terminal", "User Equipment (UE)", "terminal", etc. may be used interchangeably.
[0163] A mobile station may also be referred to by those skilled in the art as a subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, or some other suitable terminology.
[0164] At least one of the base station and the mobile station may be called a transmitting device, a receiving device, a communication device, etc. At least one of the base station and the mobile station may be a device mounted on a moving body, the moving body itself, etc. The moving body may be a vehicle (e.g., a car, an airplane, etc.), an unmanned moving body (e.g., a drone, an autonomous vehicle, etc.), or a robot (manned or unmanned). At least one of the base station and the mobile station may include a device that does not necessarily move during communication operation. For example, at least one of the base station and the mobile station may be an Internet of Things (IoT) device such as a sensor.
[0165] Furthermore, a base station in the present disclosure may be read as a mobile station (user terminal, the same applies below). For example, each aspect / embodiment of the present disclosure may be applied to a configuration in which communication between a base station and a mobile station is replaced with communication between multiple mobile stations (which may be called, for example, Device-to-Device (D2D) or Vehicle-to-Everything (V2X)). In this case, the mobile station may be configured to have the functions of a base station. Furthermore, terms such as "uplink" and "downlink" may be read as terms corresponding to communication between terminals (for example, "side"). For example, an uplink channel, a downlink channel, etc. may be read as a side channel.
[0166] Similarly, a mobile station in the present disclosure may be interpreted as a base station, in which case the base station may have the functions of a mobile station.
[0167] A radio frame may be composed of one or more frames in the time domain, each of which may be called a subframe.
[0168] A subframe may further be composed of one or more slots in the time domain. A subframe may have a fixed time length (e.g., 1 ms) that is independent of numerology.
[0169] Numerology may be a communication parameter that applies to the transmission and / or reception of a signal or channel, and may indicate, for example, at least one of a SubCarrier Spacing (SCS), a bandwidth, a symbol length, a Cyclic Prefix length, a Transmission Time Interval (TTI), a number of symbols per TTI, a radio frame structure, a particular filtering operation that a transceiver performs in the frequency domain, a particular windowing operation that a transceiver performs in the time domain, etc.
[0170] A slot may consist of one or more symbols in the time domain (such as Orthogonal Frequency Division Multiplexing (OFDM) symbols, Single Carrier Frequency Division Multiple Access (SC-FDMA) symbols, etc.) A slot may be a time unit based on numerology.
[0171] A slot may include multiple minislots. Each minislot may be composed of one or multiple symbols in the time domain. A minislot may also be called a subslot. A minislot may be composed of fewer symbols than a slot. A PDSCH (or PUSCH) transmitted in a time unit larger than a minislot may be called PDSCH (or PUSCH) mapping type A. A PDSCH (or PUSCH) transmitted using a minislot may be called PDSCH (or PUSCH) mapping type B.
[0172] A radio frame, a subframe, a slot, a minislot, and a symbol each represent a time unit for transmitting a signal. The radio frame, the subframe, the slot, the minislot, and the symbol may each be referred to by a different name.
[0173] For example, one subframe may be called a transmission time interval (TTI), multiple consecutive subframes may be called a TTI, or one slot or one minislot may be called a TTI. That is, at least one of the subframe and the TTI may be a subframe (1 ms) in the existing LTE, a period shorter than 1 ms (for example, 1-13 symbols), or a period longer than 1 ms. Note that the unit expressing the TTI may be called a slot, minislot, etc., instead of a subframe.
[0174] Here, TTI refers to, for example, the minimum time unit for scheduling in wireless communication. For example, in an LTE system, a base station performs scheduling to allocate radio resources (such as frequency bandwidth and transmission power that can be used by each user terminal) to each user terminal in TTI units. Note that the definition of TTI is not limited to this.
[0175] The TTI may be a transmission time unit for a channel-encoded data packet (transport block), a code block, a code word, etc., or may be a processing unit for scheduling, link adaptation, etc. When a TTI is given, the time interval (e.g., the number of symbols) in which a transport block, a code block, a code word, etc. are actually mapped may be shorter than the TTI.
[0176] In addition, when one slot or one minislot is called TTI, one or more TTIs (i.e., one or more slots or one or more minislots) may be the minimum time unit of scheduling. Also, the number of slots (minislots) constituting the minimum time unit of scheduling may be controlled.
[0177] A TTI having a time length of 1 ms may be called a normal TTI (TTI in LTE Rel. 8-12), a normal TTI, a long TTI, a normal subframe, a normal subframe, a long subframe, a slot, etc. A TTI shorter than a normal TTI may be called a shortened TTI, a short TTI, a partial or fractional TTI, a shortened subframe, a short subframe, a minislot, a subslot, a slot, etc.
[0178] In addition, a long TTI (e.g., a normal TTI, a subframe, etc.) may be interpreted as a TTI having a time length exceeding 1 ms, and a short TTI (e.g., a shortened TTI, etc.) may be interpreted as a TTI having a TTI length shorter than the TTI length of a long TTI and equal to or greater than 1 ms.
[0179] A resource block (RB) is a resource allocation unit in the time domain and the frequency domain, and may include one or more consecutive subcarriers in the frequency domain. The number of subcarriers included in an RB may be the same regardless of the numerology, for example, 12. The number of subcarriers included in an RB may be determined based on the numerology.
[0180] In addition, the time domain of the RB may include one or more symbols and may be one slot, one minislot, one subframe, or one TTI in length. Each of one TTI, one subframe, etc. may be composed of one or more resource blocks.
[0181] One or more RBs may be called a physical resource block (PRB), a sub-carrier group (SCG), a resource element group (REG), a PRB pair, an RB pair, or the like.
[0182] Furthermore, a resource block may be composed of one or more resource elements (REs). For example, one RE may be a radio resource region of one subcarrier and one symbol.
[0183] A Bandwidth Part (BWP), which may also be referred to as a fractional bandwidth, may represent a subset of contiguous common resource blocks (RBs) for a numerology on a carrier, where the common RBs may be identified by the index of the RBs relative to a common reference point of the carrier. PRBs may be defined in a BWP and numbered within the BWP.
[0184] The BWP may include a BWP for UL (UL BWP) and a BWP for DL (DL BWP). One or more BWPs may be configured for a UE within one carrier.
[0185] At least one of the configured BWPs may be active, and the UE may not expect to transmit or receive a given signal / channel outside the active BWP. Note that the terms "cell", "carrier", etc. in this disclosure may be replaced with "BWP".
[0186] The above-mentioned structures of radio frames, subframes, slots, minislots, symbols, etc. are merely examples. For example, the number of subframes included in a radio frame, the number of slots per subframe or radio frame, the number of minislots included in a slot, the number of symbols and RBs included in a slot or minislot, the number of subcarriers included in an RB, the number of symbols in a TTI, the symbol length, the cyclic prefix (CP) length, etc. may be changed in various ways.
[0187] The terms "connected," "coupled," or any variation thereof, refer to any direct or indirect connection or coupling between two or more elements, and may include the presence of one or more intermediate elements between two elements that are "connected" or "coupled" to each other. The coupling or connection between elements may be physical, logical, or a combination thereof. For example, "connected" may be read as "access." As used in this disclosure, two elements may be considered to be "connected" or "coupled" to each other using at least one of one or more wires, cables, and printed electrical connections, as well as electromagnetic energy having wavelengths in the radio frequency range, microwave range, and optical (both visible and invisible) range, as some non-limiting and non-exhaustive examples. The reference signal may also be abbreviated as Reference Signal (RS), and may be called a pilot depending on the applicable standard.
[0188] As used in this disclosure, the phrase "based on" does not mean "based only on," unless expressly stated otherwise. In other words, the phrase "based on" means both "based only on" and "based at least on."
[0189] The "means" in the configuration of each of the above devices may be replaced with "part," "circuit," "device," etc.
[0190] Any reference to an element using a designation such as "first," "second," etc., used in this disclosure does not generally limit the quantity or order of those elements. These designations may be used in this disclosure as a convenient method of distinguishing between two or more elements. Thus, a reference to a first and a second element does not imply that only two elements may be employed therein or that the first element must precede the second element in some way.
[0191] When the terms "include," "including," and variations thereof are used in this disclosure, these terms are intended to be inclusive, similar to the term "comprising." Further, when used in this disclosure, the term "or" is not intended to be an exclusive or.
[0192] In this disclosure, where articles have been added due to translation, such as a, an, and the in English, the disclosure may include that the nouns following these articles are in the plural form.
[0193] As used in this disclosure, the terms "determining" and "determining" may encompass a wide variety of actions. "Determining" and "determining" may include, for example, judging, calculating, computing, processing, deriving, investigating, looking up, search, inquiry (e.g., searching in a table, database, or other data structure), ascertaining, and the like. "Determining" and "determining" may also include receiving (e.g., receiving information), transmitting (e.g., sending information), input, output, accessing (e.g., accessing data in a memory), and the like. In addition, "judgment" and "decision" can include considering resolving, selecting, choosing, establishing, comparing, etc., to be a "judgment" or "decision." In other words, "judgment" and "decision" can include considering some action to be a "judgment" or "decision." In addition, "judgment" can be interpreted as "assuming," "expecting," "considering," etc.
[0194] In the present disclosure, the term "A and B are different" may mean "A and B are different from each other." The term may also mean "A and B are each different from C." Terms such as "separate" and "coupled" may also be interpreted in the same way as "different."
[0195] Although the present disclosure has been described in detail above, it is clear to those skilled in the art that the present disclosure is not limited to the embodiments described in the present disclosure. The present disclosure can be implemented in modified and altered forms without departing from the spirit and scope of the present disclosure as defined by the claims. Therefore, the description of the present disclosure is intended to be illustrative and does not have any limiting meaning on the present disclosure. [Explanation of symbols]
[0196] 10. Wireless communication systems 20 NG-RAN 100 gNB 200UE 210 Radio signal transmitter / receiver 220 Amplifier section 230 Modulation and demodulation section 240 Control signal / reference signal processing unit 250 Encoding / Decoding Unit 260 Data transmission and reception unit 270 Control Unit 1001 Processor 1002 Memory 1003 Storage 1004 Communication equipment 1005 Input Device 1006 Output device 1007 Bus
Claims
1. a communication unit that performs data communication with a network via a second component carrier different from the first component carrier; the first component carrier is a component carrier belonging to a first frequency range; the second component carrier is a component carrier belonging to a second frequency range higher than the first frequency range, when a physical uplink control channel of at least one of the first component carrier and the second component carrier and a physical uplink shared channel of the second component carrier collide with each other, the communication unit multiplexes uplink control information related to at least one of the first component carrier and the second component carrier onto the physical uplink shared channel and transmits the uplink control information to the network. Terminal.
2. When a predetermined condition is satisfied, the communication unit multiplexes uplink control information related to at least one of the first component carrier and the second component carrier onto the physical uplink shared channel. The terminal according to claim 1.
3. the predetermined condition is at least one of: uplink control information regarding the first component carrier is decodable independently of uplink control information regarding the second component carrier; and a codebook of the uplink control information regarding the second component carrier is generated separately from a codebook of the uplink control information regarding the first component carrier. The terminal according to claim 2.
4. The second frequency range is 52.6 GHz or higher. The terminal according to claim 1.
Citation Information
Patent Citations
Uplink transmission method and corresponding equipment
US20190103943A1
User terminal and wireless base station
WO2019220595A1