Terminal, wireless communication system, and wireless communication method
Patent Information
- Application Number
- JP2023524050
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Priority Date
- 2021-05-27
- Filing Date
- 2022-03-28
- Publication Date
- 2026-08-27
- Estimated Expiration
- 2042-03-28
Smart Images

Figure 0007912006000001 
Figure 0007912006000002 
Figure 0007912006000003
Abstract
Description
Technical Field
[0004] , , , , , , , , , ,
[0005] ,
[0003]
[0001] The present disclosure relates to a terminal that performs wireless communication, a base station, and a wireless communication method, and particularly to a terminal, a wireless communication system, and a wireless communication method related to multiplexing of uplink control information for an uplink channel.
Background Art
[0002] The 3rd Generation Partnership Project (3GPP) is standardizing the 5th generation mobile communication system (also referred to as 5G, New Radio (NR), or Next Generation (NG)), and is also proceeding with the standardization of the next generation, such as Beyond 5G, 5G Evolution, or 6G.
[0003] In Release 15 of 3GPP, multiplexing of two or more uplink channels (Physical Uplink Control Channel (PUCCH) and Physical Uplink Shared Channel (PUSCH)) transmitted in the same slot is supported.
[0004] Furthermore, in Release 17 of 3GPP, it was agreed to support multiplexing of Uplink Control Information (UCI) with different priorities on PUCCH or PUSCH (for example, Non-Patent Document 1).
Prior Art Documents
Non-Patent Documents
[0005]
Non-Patent Document 1
[0006] Against this backdrop, the inventors, after diligent consideration, focused on cases where UCIs on PUCCH and UCIs on PUCCH may overlap in time, with UCIs having the same or different priorities and UCIs on PUCCH having the same or different priorities. They found it necessary to define conditions for appropriately overlapping UCIs on PUCCH in such cases.
[0007] Therefore, the present invention has been made in view of these circumstances, and aims to provide a terminal, a wireless communication system, and a wireless communication method that can appropriately multiplex UCIs on PUCCH when various UCIs are expected to overlap in time with UCIs on PUCCH. [Means for solving the problem]
[0008] One aspect of the disclosure is a terminal comprising: a transmitting unit that transmits uplink control information via an uplink channel; and a control unit that determines whether or not to support simultaneous transmission of a physical uplink control channel and a physical uplink data channel based on specific conditions.
[0009] One aspect of the disclosure is a wireless communication system comprising a terminal and a base station, wherein the terminal comprises a transmitting unit that transmits uplink control information via an uplink channel, and a control unit that determines whether or not to support simultaneous transmission of a physical uplink control channel and a physical uplink data channel based on specific conditions.
[0010] One aspect of the disclosure is a wireless communication method comprising the steps of: transmitting uplink control information via an uplink channel; and determining whether or not to support simultaneous transmission of a physical uplink control channel and a physical uplink data channel based on specific conditions. [Brief explanation of the drawing]
[0011] [Figure 1] Figure 1 is a schematic diagram of the overall configuration of the wireless communication system 10. [Figure 2] Figure 2 shows the frequency range used in the wireless communication system 10. [Figure 3] Figure 3 shows an example of the configuration of wireless frames, subframes, and slots used in the wireless communication system 10. [Figure 4] Figure 4 is a functional block diagram of the UE200. [Figure 5] Figure 5 is a functional block diagram of the gNB100. [Figure 6] Figure 6 is a diagram used to explain the background. [Figure 7] Figure 7 is a diagram illustrating the first identification method. [Figure 8] Figure 8 is a diagram illustrating the second identification method. [Figure 9] Figure 9 is a diagram illustrating the third identification method. [Figure 10] Figure 10 is a diagram illustrating the third identification method. [Figure 11] Figure 11 shows an example of the hardware configuration of the gNB100 and UE200. [Modes for carrying out the invention]
[0012] The embodiments will be described below with reference to the drawings. Note that identical or similar reference numerals are used to denote the same functions and components, and their descriptions will be omitted as appropriate.
[0013] [Embodiment] (1) Overall schematic configuration of the wireless communication system FIG. 1 is an overall schematic configuration diagram of a wireless communication system 10 according to an embodiment. The wireless communication system 10 is a wireless communication system compliant with 5G New Radio (NR), and includes a Next Generation-Radio Access Network 20 (hereinafter, NG-RAN 20) and a terminal 200 (hereinafter, UE (User Equipment) 200).
[0014] Note that the wireless communication system 10 may also be a wireless communication system compliant with a system called Beyond 5G, 5G Evolution, or 6G.
[0015] 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. 1.
[0016] 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). Note that NG-RAN 20 and 5GC may simply be expressed as "network".
[0017] gNB 100A and gNB 100B are 5G-compliant radio base stations and perform wireless communication with UE 200 according to 5G. gNB 100A, gNB 100B, and UE 200 can support Massive MIMO (Multiple-Input Multiple-Output) that generates a more directional beam BM by controlling wireless signals transmitted from a plurality of antenna elements, carrier aggregation (CA) that bundles and uses a plurality of component carriers (CC), and dual connectivity (DC) that communicates with two or more transport blocks simultaneously between the UE and each of the two NG-RAN Nodes.
[0018] Furthermore, the wireless communication system 10 supports multiple frequency ranges (FR). Figure 2 shows the frequency ranges used in the wireless communication system 10.
[0019] As shown in Figure 2, the wireless communication system 10 corresponds to FR1 and FR2. The frequency bands of each FR are as follows:
[0020] FR1: 410 MHz ~ 7.125 GHz • FR2: 24.25 GHz ~ 52.6 GHz In FR1, a Sub-Carrier Spacing (SCS) of 15, 30, or 60 kHz may be used, and a bandwidth (BW) of 5 to 100 MHz may be used. FR2 is a higher frequency than FR1, and a 60 or 120 kHz (240 kHz may be included) SCS may be used, and a bandwidth (BW) of 50 to 400 MHz may be used.
[0021] Note that SCS may also be interpreted as numerology. Numerology is defined in 3GPP TS38.300 and corresponds to a single subcarrier interval in the frequency domain.
[0022] Furthermore, the wireless communication system 10 also supports higher frequency bands than the FR2 frequency band. Specifically, the wireless communication system 10 supports frequency bands exceeding 52.6 GHz up to 71 GHz or 114.25 GHz. Such high frequency bands may be conveniently referred to as "FR2x".
[0023] To address the problem of increased phase noise in high-frequency bands, when using bandwidths exceeding 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.
[0024] Figure 3 shows an example of the configuration of wireless frames, subframes, and slots used in the wireless communication system 10.
[0025] As shown in Figure 3, one slot consists of 14 symbols, and the larger (wider) the SCS, the shorter the symbol period (and slot period). The SCS is not limited to the interval (frequency) shown in Figure 3. For example, 480 kHz, 960 kHz, etc., may be used.
[0026] Furthermore, the number of symbols constituting one slot does not necessarily have to be 14 (for example, 28 or 56 symbols). In addition, the number of slots per subframe may vary depending on the SCS.
[0027] The time direction (t) shown in Figure 3 may also be called the time domain, symbol period, or symbol time. The frequency direction may also be called the frequency domain, resource block, subcarrier, or bandwidth part (BWP).
[0028] DMRS is a type of reference signal, prepared for various channels. Here, unless otherwise specified, it may refer to the DMRS for the downlink data channel, specifically the PDSCH (Physical Downlink Shared Channel). However, the DMRS for the uplink data channel, specifically the PUSCH (Physical Uplink Shared Channel), may be interpreted as being the same as the DMRS for the PDSCH.
[0029] DMRS can be used for channel estimation in a device, for example, as part of coherent demodulation in the UE200. DMRS may only be present in the resource block (RB) used for PDSCH transmission.
[0030] A DMRS may have multiple mapping types. Specifically, a DMRS may have mapping type A and mapping type B. In mapping type A, the first DMRS is placed on the second or third symbol of the slot. In mapping type A, the DMRS may be mapped relative to the slot boundary, regardless of where in the slot the actual data transmission begins. The reason the first DMRS is placed on the second or third symbol of the slot may be interpreted as being placed after the control resource sets (CORESET).
[0031] In mapping type B, the first DMRS may be placed on the first symbol of the data allocation. That is, the position of the DMRS may be given relative to where the data is located, rather than relative to the slot boundary.
[0032] Furthermore, DMRS may have multiple types. Specifically, DMRS may have Type 1 and Type 2. Type 1 and Type 2 differ in their frequency domain mapping and the maximum number of orthogonal reference signals. Type 1 is a single-symbol DMRS that can output up to four orthogonal signals, while Type 2 is a double-symbol DMRS that can output up to eight orthogonal signals.
[0033] (2) Functional block configuration of the wireless communication system Next, the functional block configuration of the wireless communication system 10 will be described.
[0034] First, we will describe the functional block configuration of the UE200.
[0035] Figure 4 is a functional block diagram of the UE200. As shown in Figure 4, the UE200 comprises a wireless signal transmission / reception 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 transmission / reception unit 260, and a control unit 270.
[0036] The wireless signal transceiver unit 210 transmits and receives wireless signals in accordance with NR. The wireless signal transceiver unit 210 supports Massive MIMO, CA which uses multiple CCs bundled together, and DC which communicates simultaneously between the UE and each of the two NG-RAN Nodes.
[0037] The amplifier section 220 consists of components such as a PA (Power Amplifier) and an LNA (Low Noise Amplifier). The amplifier section 220 amplifies the signal output from the modulation / demodulation section 230 to a predetermined power level. The amplifier section 220 also amplifies the RF signal output from the wireless signal transmission / reception section 210.
[0038] The modulation / demodulation unit 230 performs data modulation / demodulation, transmit power setting, and resource block allocation for each predetermined communication destination (gNB100 or other gNB). The modulation / demodulation 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 the uplink (UL) but also for the downlink (DL).
[0039] The control signal / reference signal processing unit 240 performs processing related to various control signals transmitted and received by the UE200, and processing related to various reference signals transmitted and received by the UE200.
[0040] Specifically, the control signal / reference signal processing unit 240 receives various control signals transmitted from the gNB100 via a predetermined control channel, such as control signals for the radio resource control layer (RRC). The control signal / reference signal processing unit 240 also transmits various control signals to the gNB100 via a predetermined control channel.
[0041] The control signal / reference signal processing unit 240 performs processing using reference signals (RS) such as the Demodulation Reference Signal (DMRS) and the Phase Tracking Reference Signal (PTRS).
[0042] DMRS is a terminal-specific, known reference signal (pilot signal) between the base station and the terminal used to estimate the fading channel used for data demodulation. PTRS is a terminal-specific reference signal intended to estimate phase noise, which is a problem in the high-frequency band.
[0043] In addition to DMRS and PTRS, the reference signals may also include Channel State Information-Reference Signal (CSI-RS), Sounding Reference Signal (SRS), and Positioning Reference Signal (PRS) for location information.
[0044] Furthermore, channels include control channels and data channels. Control channels include PDCCH (Physical Downlink Control Channel), PUCCH (Physical Uplink Control Channel), RACH (Random Access Channel), Downlink Control Information (DCI) including Random Access Radio Network Temporary Identifier (RA-RNTI), and Physical Broadcast Channel (PBCH), among others.
[0045] Furthermore, data channels include PDSCH (Physical Downlink Shared Channel) and PUSCH (Physical Uplink Shared Channel), among others. "Data" refers to data transmitted through a data channel. A data channel can also be interpreted as a shared channel.
[0046] Here, the control signal / reference signal processing unit 240 may receive downlink control information (DCI). The DCI includes fields that store existing fields such as DCI Formats, Carrier indicator (CI), BWP indicator, FDRA (Frequency Domain Resource Assignment), TDRA (Time Domain Resource Assignment), MCS (Modulation and Coding Scheme), HPN (HARQ Process Number), NDI (New Data Indicator), and RV (Redundancy Version).
[0047] The value stored in the DCI Format field is an information element that specifies the DCI format. The value stored in the CI field is an information element that specifies the CC to which the DCI applies. The value stored in the BWP indicator field is an information element that specifies the BWP to which the DCI applies. The BWP that can be specified by the BWP indicator is set by an information element (BandwidthPart-Config) included in the RRC message. The value stored in the FDRA field is an information element that specifies the frequency domain resource to which the DCI applies. The frequency domain resource is identified by the value stored in the FDRA field and an information element (RA Type) included in the RRC message. The value stored in the TDRA field is an information element that specifies the time domain resource to which the DCI applies. The time domain resource is identified by the value stored in the TDRA field and an information element (pdsch-TimeDomainAllocationList, push-TimeDomainAllocationList) included in the RRC message. The time domain resource may also be identified by the value stored in the TDRA field and the default table. The value stored in the MCS field is an information element that specifies the MCS to which the DCI applies. The MCS is identified by the value stored in MCS and the MCS table. The MCS table may be specified by the RRC message or identified by RNTI scrambling. The value stored in the HPN field is an information element that specifies the HARQ Process to which DCI is applied. The value stored in NDI is an information element that determines whether the data to which DCI is applied is initial transmission data. The value stored in the RV field is an information element that specifies the redundancy of the data to which DCI is applied.
[0048] The encoding / decoding unit 250 performs data splitting / concatenation and channel coding / decoding for each predetermined communication destination (gNB100 or other gNB).
[0049] Specifically, the encoding / decoding unit 250 divides the data output from the data transmission / reception unit 260 into predetermined sizes and performs channel coding on the divided data. The encoding / decoding unit 250 also decodes the data output from the modulation / demodulation unit 230 and concatenates the decoded data.
[0050] The data transmission / reception unit 260 performs the transmission and reception of Protocol Data Units (PDUs) and Service Data Units (SDUs). Specifically, the data transmission / reception unit 260 performs assembly / decomposition of PDUs / SDUs at multiple layers (such as the Media Access Control Layer (MAC), Radio Link Control Layer (RLC), and Packet Data Convergence Protocol Layer (PDCP)). In addition, the data transmission / reception unit 260 performs error correction and retransmission control of data based on HARQ (Hybrid Automatic Repeat Request).
[0051] The control unit 270 controls each functional block that constitutes the UE200. In this embodiment, the control unit 270 may control the multiplexing of uplink control information (hereinafter referred to as specific UCI) for the physical uplink control channel (hereinafter referred to as specific PUCCH).
[0052] Here, UCI priorities may be defined as first priority and second priority. First priority is different from second priority. Two types of UCI priorities are given as examples: HP (High Priority) and LP (Low Priority). First priority may be HP and second priority may be LP, or first priority may be LP and second priority may be HP. Three or more types of priorities may be defined as UCI priorities.
[0053] The control unit 270 controls the control signal / reference signal processing unit 240 described above, and the control signal / reference signal processing unit 240 constitutes a transmitting unit that transmits UCIs via the uplink channel (PUCCH or PUSCH). The control signal / reference signal processing unit 240 may also transmit a specific UCI multiplexed with a UCI selected based on a specific method (hereinafter referred to as the target UCI) via the uplink channel (PUCCH or PUSCH). Possible specific methods include a first specific method, a second specific method, and a third specific method, as will be described later. Details of these specific methods will be described later.
[0054] Secondly, the functional block configuration of the gNB100 will be described.
[0055] Figure 5 is a functional block diagram of the gNB100. As shown in Figure 5, the gNB100 has a receiving unit 110, a transmitting unit 120, and a control unit 130.
[0056] The receiver 110 receives various signals from the UE200. The receiver 110 may also receive the UL signal via PUCCH or PUSCH.
[0057] The transmitter 120 transmits various signals to the UE200. The transmitter 120 may also transmit DL signals via PDCCH or PDSCH.
[0058] The control unit 130 controls the gNB100. The control unit 130 assumes that the receiving unit 110 receives a specific UCI (target UCI) multiplexed with a UCI selected based on a specific method via the uplink channel (PUCCH or PUSCH).
[0059] (3) Background The background of the embodiment will be described below. In this embodiment, we focus on the case in which there may be UCIs on PUCCHs with the same priority, UCIs on PUCCHs with different priorities, UCIs on PUSCHs with the same priority, and UCIs on PUSCHs with different priorities that overlap in time with a specific UCI on a specific PUCCH. In the following, UCI may be used synonymously with PUCCH or PUSCH.
[0060] For example, consider the case where various UCIs are transmitted in each CC, as shown in Figure 6. Specifically, in CC#0, the transmission of HP PUCCH#0-1, HP PUCCH#0-2, LP PUCCH#0-3, and LP PUCCH#0-4 is scheduled. In CC#1, the transmission of HP PUCCH#1-1 is scheduled. In CC#2, the transmission of LP PUCCH#2-1 and HP PUCCH#2-2 is scheduled. In CC#3, the transmission of LP PUCCH#3-1 is scheduled.
[0061] In such a case, assuming that the specific PUCCH (specific UCI) is HP PUCCH#0-1, the UCIs that overlap with HP PUCCH#0-1 in time are HP PUCCH#0-2, LP PUCCH#0-3, LP PUCCH#2-1, HP PUCCH#2-2, and LP PUCCH#3-1. On the other hand, assuming that the specific PUCCH (specific UCI) is LP PUCCH#0-3, the UCIs that overlap with LP PUCCH#0-3 in time are HP PUCCH#0-1, LP PUCCH#0-4, HP PUCCH#1-1, HP PUCCH#2-2, and LP PUCCH#3-1.
[0062] Therefore, it is necessary to define various methods (conditions and order) for multiplexing PUCCH. In this embodiment, a first specification method, a second specification method, and a third specification method are defined as methods for multiplexing PUCCH.
[0063] (4) First identification method The first identification method will be described below. The first identification method may include the following two steps.
[0064] The first stage may be a stage in which, when uplink control information on a PUCCH (specific UCI) overlaps in time with first target uplink control information on a physical uplink control channel (PUCCH) (hereinafter referred to as the first target UCI), the first target UCI that overlaps with the specific UCI is selected based on a first specific condition, and the selected first target UCI is overlapped with the specific UCI. The first stage may also be considered a stage in which the temporal overlap between PUCCHs is resolved.
[0065] The first specific condition may also be a condition in which, after selecting a first target UCI on PUCCH that has the same priority as the specific UCI on PUCCH (hereinafter, first target UCI (same priority)), a first target UCI on PUCCH that has a different priority than the specific UCI (hereinafter, first target UCI (different priority)). That is, the specific UCI is duplicated with a first target UCI (same priority) that overlaps with the specific UCI in time, and if there is no first target UCI (same priority) that overlaps with the specific UCI in time, the specific UCI is duplicated with a first target UCI (different priority) that overlaps with the specific UCI in time.
[0066] The second stage may be a stage in which, when a specific UCI on PUCCH overlaps in time with the second target uplink control information (hereinafter referred to as the second target UCI) on the physical uplink sharing channel (PUSCH), a second target UCI that overlaps with the specific UCI is selected based on a second specific condition, and the selected second target UCI is overlapped with the specific UCI. The second stage may also be considered a stage in which the temporal overlap between PUCCH and PUSCH is resolved.
[0067] Firstly, the second specific condition may include the first condition, which applies when it is assumed that the priority of the second target UCI on PUSCH that overlaps temporally with the specific UCI is the same as the priority of the specific UCI. The first condition may include the following conditions:
[0068] The first condition may include condition 1A, which selects a PUSCH of A(Aperiodic)-CSI that overlaps with the resources of a specific PUCCH.
[0069] The first condition may include condition 1B, which selects the PUSCH having the earliest slot(s) based on the first slot(s) of the PUCCH.
[0070] The first condition may include condition 1C, which prioritizes selecting a PUSCH scheduled by DG (Dynamic Grant) (hereinafter referred to as DG PUSCH) over a PUSCH scheduled by CG (Configured Grant) (hereinafter referred to as CG PUSCH).
[0071] The first condition may include condition 1D, which preferentially selects PUSCH of CC serving cells with a smaller CC serving cell index over PUSCH of CC serving cells with a larger CC serving cell index.
[0072] The first condition may include condition 1E, which prioritizes selecting an earlier transmission PUSCH over a slower transmission PUSCH.
[0073] Here, the first condition may be applied in the order of condition 1A → condition 1B → condition 1C → condition 1D → condition 1E.
[0074] Secondly, the second specific condition may include a second condition relating to at least one of the delay and reliability of the specific UCI. The second condition may be, but is not limited to, condition 2A defining a PUSCH that cannot be duplicated with the specific PUCCH from the perspective of the delay of the specific UCI, or condition 2B defining a PUSCH that can be duplicated with the specific PUCCH. The second condition may be condition 2C defining a PUSCH that cannot be duplicated with the specific PUCCH from the perspective of the reliability of the specific UCI, or condition 2D defining a PUSCH that can be duplicated with the specific PUCCH.
[0075] The second condition may apply if it is assumed that the priority of the second target UCI on PUSCH that overlaps with the specific UCI in time is the same as the priority of the specific UCI. The second condition may also apply if it is assumed that the priority of the second target UCI on PUSCH that overlaps with the specific UCI in time is different from the priority of the specific UCI.
[0076] Thirdly, the second specific condition may include a third condition that applies when HP UCI and LP UCI are already multiplexed on a specific PUCCH. The HP+LP priority may be considered a different priority from HP and LP. The third condition may be condition 3A for selecting an HP PUSCH, or condition 3B for selecting an LP PUSCH. The third condition may also be a condition to which the same conditions as the first condition described above apply to all PUSCHs that overlap temporally with the specific PUCCH.
[0077] Fourth, the second specific condition may include a fourth condition that applies when HP UCIs and LP UCIs are already multiplexed on a specific PUCCH. The HP+LP priority may be considered a different priority from HP and LP. The fourth condition may also be a condition in which UCIs (HP+LP UCIs) on a specific PUCCH are multiplexed on the second PUSCH according to their priority. For example, the fourth condition may be a condition in which HP UCIs on a specific PUCCH are multiplexed on an HP PUSCH having the same priority as HP UCIs, and LP UCIs on a specific PUCCH are multiplexed on an LP PUSCH having the same priority as HP UCIs.
[0078] For example, consider the multiplexing method for LP PUSCH, LP PUCCH, HP PUCCH, and HP PUSCH, as shown in Figure 7.
[0079] In the first stage, overlapping LP PUCCH and HP PUCCH are multiplexed. Specifically, HP UCI and LP UCI can be multiplexed into a single PUCCH (in Figure 7, PUCCH(HP+LP UCI)). If there are no other overlapping PUCCHs, the LP PUCCH and HP PUCCH may remain unmultiplexed.
[0080] In the second stage, overlapping PUCCH and PUSCH operations are performed. Specifically, an LP UCI on PUCCH may be multiplexed onto an LP PUSCH (in Figure 7, LP PUSCH(LP UCI)). Similarly, an HP UCI on PUCCH may be multiplexed onto an HP PUSCH (in Figure 7, HP PUSCH(HP UCI)). However, an LP UCI on PUCCH may be multiplexed onto an HP PUSCH, and an HP UCI on PUCCH may be multiplexed onto an LP PUSCH.
[0081] (5)Second identification method The second identification method will be described below. The second identification method may include the following two steps.
[0082] The first stage may be a stage in which, when uplink control information (specific UCI) on a PUCCH having first priority overlaps in time with first target uplink control information on an uplink channel (PUCCH or PUSCH) having first priority, a first target uplink control information (hereinafter, first target UCI) that overlaps with the uplink control information is selected based on a first specific condition, and the selected first target UCI is overlapped with the specific UCI. The first stage may also be considered a stage in which the temporal overlap between uplink channels (PUCCH or PUSCH) of the same priority is resolved.
[0083] The first identification condition may be a condition in which, after selecting a first target UCI on PUCCH that has the same priority as the specific UCI on PUCCH (hereinafter, first target UCI (PUCCH)), a first target UCI on PUSCH that has the same priority as the specific UCI (hereinafter, first target UCI (PUSCH)) is selected. That is, the specific UCI is multiplexed with a first target UCI (PUCCH) that overlaps with the specific UCI in time, and if there is no first target UCI (PUCCH) that overlaps with the specific UCI in time, the specific UCI is multiplexed with a first target UCI (PUSCH) that overlaps with the specific UCI in time. If there are two or more first target UCIs (PUSCH) that overlap with the specific UCI in time, the first identification condition may be the first condition described in the first identification method (i.e., conditions 1A to 1E).
[0084] The second stage may be a stage in which, when a specific UCI on a PUCCH having first priority overlaps in time with second target uplink control information (hereinafter referred to as second target UCI) on an uplink channel (PUCCH or PUSCH) having second priority, a second target UCI that overlaps with the specific UCI is selected based on a second specific condition, and the selected second target UCI is overlapped with the specific UCI. The second stage may also be considered a stage in which temporal overlaps between uplink channels of different priorities (PUCCH or PUSCH) are resolved.
[0085] Firstly, if a specific UCI on a PUCCH with first priority overlaps temporally only with a second target UCI on a PUCCH with second priority (hereinafter referred to as the second target UCI (PUCCH)), the second specific condition may include a condition for overlapping an LP PUCCH with an HP PUCCH, or a condition for overlapping an HP PUCCH with an LP PUCCH.
[0086] Secondly, if a specific UCI on PUCCH with first priority overlaps temporally only with a second target UCI on PUSCH with second priority (hereinafter, second target UCI (PUSCH)), the second conditions described in the first identification method (i.e., conditions 2A to 2D) may be used as the second identification conditions. As described above, the second conditions may include conditions relating to at least one of the delay and reliability of the specific UCI. As the second identification conditions, the third conditions described in the first identification method (i.e., conditions 3A to 3B) may be used for PUSCHs with different priorities than the specific UCI, or the fourth conditions described in the first identification method may be used.
[0087] Thirdly, if a specific UCI on PUCCH with first priority overlaps temporally with both a second target UCI (PUCCH) and a second target UCI (PUSCH), the second identification condition may include a condition that prioritizes the selection of the second target UCI (PUCCH) over the second target UCI (PUSCH). The second identification condition may include a condition that prioritizes the selection of the second target UCI (PUSCH) over the second target UCI (PUCCH). In such cases, if there are two or more second target UCIs (PUSCH) that overlap temporally with the specific UCI, the second identification condition may be one of the second conditions described in the first identification method (i.e., conditions 2A to 2D).
[0088] For example, consider the multiplexing method for LP PUSCH, LP PUCCH, HP PUCCH, and HP PUSCH, as shown in Figure 8.
[0089] In the first stage, multiplexing of uplink channels of the same priority (LP PUCCH / LP PUCCH, LP PUCCH / LP PUSCH, HP PUCCH / HP PUCCH, HP PUCCH / HP PUSCH) is performed. Specifically, in the first stage (1), time-overlapping LP PUCCHs may be multiplexed, and time-overlapping HP PUCCHs may be multiplexed. As a result, a state is achieved where there are no time-overlapping LP PUCCHs and no time-overlapping HP PUCCHs. In the first stage (2), multiplexing of time-overlapping LP PUCCHs and LP PUSCHs is performed, and multiplexing of time-overlapping HP PUCCHs and HP PUSCHs may be performed. Specifically, a PUCCH may be multiplexed with an LP PUSCH (LP PUSCH(LP UCI) in Figure 8). Similarly, an HP PUCCH may be multiplexed with an HP PUSCH (HP PUSCH(HP UCI) in Figure 8).
[0090] In the second stage, multiplexing of uplink channels with different priorities (LP PUCCH / HP PUCCH, LP PUCCH / HP PUSCH, HP PUCCH / LP PUSCH) is performed. Specifically, HP UCI and LP UCI can be multiplexed onto a single PUCCH (in Figure 8, PUCCH(HP+LP UCI)). Furthermore, LP UCI on a PUCCH may be multiplexed onto an HP PUSCH, and HP UCI on a PUCCH may be multiplexed onto an LP PUSCH.
[0091] (6) Third identification method The third identification method will be described below. The third identification method may include the following four steps.
[0092] The first stage may be a stage in which, when uplink control information (specific UCI) on a PUCCH having first priority overlaps temporally with a first target specific UCI (hereinafter, first target UCI (same priority / PUCCH)) on a physical uplink control channel (PUCCH) having first priority, a first target UCI (same priority / PUCCH) that overlaps with the specific UCI is selected based on a first specific condition, and the selected first target UCI (same priority / PUCCH) and the specific UCI are overlapped.
[0093] The first identification condition is the condition for selecting a first target UCI on PUCCH that has the same priority as the specified UCI on PUCCH (hereinafter, the first target UCI (PUCCH)). The first identification condition of the third identification method may be considered to be the same as a part of the first identification condition of the second identification method. In the third identification method, the first stage may be applied in parallel to both LP PUCCH and HP PUCCH.
[0094] The second stage may be a stage in which, when a specific UCI overlaps in time with a second target uplink control information (hereinafter referred to as the second target UCI (same priority / PUSCH)) on a physical uplink sharing channel (PUSCH) having the first priority, a second target UCI (same priority / PUSCH) that overlaps with the specific UCI is selected based on a second specific condition, and the selected second target UCI (same priority / PUSCH) is then overlapped with the specific UCI.
[0095] The second identification condition is the condition for selecting a second target UCI on PUSCH (same priority / PUSCH) that has the same priority as the specified UCI. The second identification condition of the third identification method may be considered to be the same as a part of the first identification condition of the second identification method. However, in the second identification method, the first stage is applied in parallel to both LP PUCCH and HP PUCCH, whereas in the third identification method, the second stage is applied serially to either LP PUCCH or HP PUCCH. If there are two or more second target UCIs (same priority / PUSCH) that overlap in time with the specified UCI, the first condition described in the first identification method (i.e., conditions 1A to 1E) may be used as the second identification condition.
[0096] The third stage may be a stage in which, when a specific UCI overlaps in time with third target uplink control information (hereinafter referred to as third target UCI (different priority / PUCCH)) on a physical uplink control channel (PUCCH) having second priority, a third target UCI (different priority / PUCCH) that overlaps with the specific UCI is selected based on a third specific condition, and the selected third target UCI (different priority / PUCCH) is overlapped with the specific UCI.
[0097] The third specification condition may include a condition for multiplexing LP PUCCH onto HP PUCCH, or a condition for multiplexing HP PUCCH onto LP PUCCH. The third specification condition of the third specification method may be considered to be the same as a part of the second specification condition of the second specification method. However, the third specification method differs from the second specification method in that it defines that PUCCH is preferentially selected over PUSCH as the different-priority uplink channel to which the specified UCI is multiplexed.
[0098] The fourth stage may be a stage in which, when a specific UCI overlaps in time with a fourth target uplink control information (hereinafter referred to as the fourth target UCI (different priority / PUSCH)) on a physical uplink sharing channel (PUSCH) having second priority, a fourth target UCI (different priority / PUSCH) that overlaps with the specific UCI is selected based on the fourth specific condition, and the selected fourth target UCI (different priority / PUSCH) is overlapped with the specific UCI.
[0099] As the fourth specification condition, the second condition described in the first specification method (i.e., conditions 2A to 2D) may be used. The fourth specification condition of the third specification method may be considered to be the same as a part of the second specification condition of the second specification method. However, the third specification method differs from the second specification method in that it defines that PUCCH is preferentially selected over PUSCH as the different-priority uplink channel to which the specified UCI is multiplexed.
[0100] For example, consider the multiplexing methods for LP PUSCH, LP PUCCH, HP PUCCH, and HP PUSCH, as shown in Figures 9 and 10. Below, we will explain the cases in which multiplexing of LP PUCCH with respect to HP PUSCH is not assumed, and the cases in which multiplexing of HP PUCCH with respect to LP PUSCH is not assumed.
[0101] Firstly, we will explain the case where the multiplexing of LP PUCCH against HP PUSCH is not expected, referring to Figure 9.
[0102] In the first stage, multiplexing of PUCCHs of the same priority (LP PUCCH / LP PUCCH, HP PUCCH / HP PUCCH) is performed. Specifically, in the first stage, LP PUCCHs that overlap in time may be multiplexed, and HP PUCCHs that overlap in time may also be multiplexed. As a result, a state is achieved in which there are no LP PUCCHs that overlap in time and no HP PUCCHs that overlap in time.
[0103] In the second stage, multiplexing of PUCCH / PUSCH (HP PUCCH / HP PUSCH) with the same priority is performed on HP PUCCH. Specifically, an HP PUCCH may be multiplexed onto an HP PUSCH that overlaps with an HP PUCCH in time (in Figure 9, HP PUSCH (HP UCI)).
[0104] In the third stage, multiplexing of PUCCHs with different priorities (LP PUCCH / HP PUCCH) is performed. Specifically, HP UCI and LP UCI can be multiplexed into a single PUCCH (in Figure 9, PUCCH(HP+LP UCI)).
[0105] In the fourth stage, multiplexing of PUCCH / PUSCH with different priorities (in this case, LP PUSCH / HP PUCCH) is performed. Specifically, HP UCI may be multiplexed onto LP PUSCH (for example, LP PUSCH(HP UCI)).
[0106] Secondly, we will explain the case where the HP PUCCH is not expected to be redundant with the LP PUSCH, referring to Figure 10.
[0107] In the first stage, multiplexing of PUCCHs of the same priority (LP PUCCH / LP PUCCH, HP PUCCH / HP PUCCH) is performed. Specifically, in the first stage, LP PUCCHs that overlap in time may be multiplexed, and HP PUCCHs that overlap in time may also be multiplexed. As a result, a state is achieved in which there are no LP PUCCHs that overlap in time and no HP PUCCHs that overlap in time.
[0108] In the second stage, multiplexing of PUCCH / PUSCH (in this case, LP PUCCH / LP PUSCH) of the same priority is performed on LP PUCCH. Specifically, an LP PUCCH may be multiplexed onto an LP PUSCH that overlaps in time with an LP PUCCH (in Figure 10, LP PUSCH(LP UCI)).
[0109] In the third stage, multiplexing of PUCCHs with different priorities (LP PUCCH / HP PUCCH) is performed. Specifically, HP UCI and LP UCI can be multiplexed into a single PUCCH (in Figure 10, PUCCH(HP+LP UCI)).
[0110] In the fourth stage, multiplexing of PUCCH / PUSCH with different priorities (in this case, HP PUSCH / LP PUCCH) is performed. Specifically, LP UCI may be multiplexed onto HP PUSCH (for example, HP PUSCH(LP UCI)).
[0111] (7) Action and Effects In this embodiment, when a specific UCI overlaps in time with a UCI on a PUCCH or PUSCH having the same or a different priority, the UE200 multiplexes the specific UCI on the uplink channel based on at least one of the first, second, and third identification methods. With this configuration, when various UCIs are expected to overlap in time with the specific UCI on the specific PUCCH, the method and conditions for multiplexing the specific UCI are defined, so that the specific UCI can be appropriately multiplexed on the uplink channel.
[0112] (8) Example of change 1 The following describes a modified example of the embodiment, Example 1. In Modified Example 1, the control unit 270 is configured to determine whether or not to support simultaneous transmission of the physical uplink control channel (PUCCH) and the physical uplink data channel (PUSCH) based on specific conditions. Whether or not simultaneous transmission of PUCCH and PUSCH is supported (hereinafter, whether or not simultaneous transmission is supported) may be determined based on the following considerations. These considerations may be read as options or specific conditions.
[0113] From perspective 1, the availability of support for simultaneous transmission may be determined based on the physical priority of PUCCH / PUSCH (hereinafter referred to as PHY priority).
[0114] Specifically, simultaneous transmission may be supported without considering the PHY priority of the PUSCH / PUCCH, may be supported for PUSCH / PUCCH having the same PHY priority, may be supported for PUSCH / PUCCH having different PHY priorities, or may be supported for PUSCH / PUCCH having a specific PHY priority.
[0115] For example, simultaneous transmission may be supported for PUSCH and PUCCH having different PHY priorities, and may also be supported for HP PUCCH and LP PUSCH.
[0116] Here, the PHY priority may be defined as follows:
[0117] For example, the PHY priority of a PUSCH may be determined by at least one of the DCI and RRC settings related to the PUSCH (Principle 1). The PHY priority of a PUSCH may be determined by whether or not a UCI is multiplexed on the PUSCH (Principle 2). The PHY priority of a PUSCH may be determined by the priority of the UCI multiplexed on the PUSCH when a UCI is multiplexed on the PUSCH (Principle 3). The PHY priority of a PUSCH may be determined by the type and priority of the UCI multiplexed on the PUSCH when a UCI is multiplexed on the PUSCH (Principle 4). One or more principles selected from Principles 1 to 4 may be determined by the RRC settings or by the wireless communication system 10.
[0118] For example, the PHY priority of PUCCH may be determined based on the priority of the PUCCH-Config of the PUCCH resource used for PUCCH transmission (Principle 1). The PHY priority of PUCCH may be determined based on the priority of the UCI multiplexed into PUCCH (Principle 2). Principle 2 may include the concept of whether the UCI multiplexed into PUCCH has one priority or two priorities. The PHY priority of PUCCH may be determined based on the type and priority of the UCI multiplexed into PUCCH (Principle 3). One or more principles selected from Principles 1 to 3 may be determined by the RRC setting or by the wireless communication system 10.
[0119] From perspective 2, the availability of support for simultaneous transmission may be determined based on the type of UCI.
[0120] Specifically, simultaneous transmissions including PUCCH may be supported if they include a specific UCI having a specific priority, any priority, the same priority, or a different priority, or they may not include a specific UCI having a specific priority, any priority, the same priority, or a different priority.
[0121] Simultaneous transmissions including PUSCH may be supported if they do not include any UCIs, may be supported if they include a specific UCI with any of the following priorities: specific priority, any priority, same priority, or different priority, or may be supported if they do not include a specific UCI with any of the following priorities: specific priority, any priority, same priority, or different priority.
[0122] For example, simultaneous transmission of PUCCH messages containing HP HARQ-ACKs and PUSCH messages without HP HARQ-ACKs may be supported.
[0123] From perspective 3, the availability of support for simultaneous transmission may be determined based on UCI multiplexing.
[0124] Specifically, simultaneous transmissions including PUSCH may be supported if they do not include any UCIs, if UCIs with the same priority (HP or LP) are multiplexed, if UCIs with different priorities are multiplexed, if UCIs with both priorities (HP and LP) are multiplexed, if UCIs with a specific priority are multiplexed, or whether UCIs with one priority or two priorities are multiplexed.
[0125] Simultaneous transmission of PUCCH may be supported when one UCI with a single priority is multiplexed, when a specific priority is multiplexed, when two or more priority UCIs are multiplexed, or regardless of whether one or two priority UCIs are multiplexed.
[0126] For example, simultaneous transmission of a PUCCH with multiplexed UCIs having the same priority as the PUCCH and a PUSCH without multiplexed UCIs having the same priority as the PUCCH may be supported.
[0127] From perspective 4, the availability of support for simultaneous transmission may be determined by the type of CA (Inter-band CA / Intra-band CA).
[0128] Specifically, simultaneous transmission may be supported for PUCCH and PUSCH on Inter-band CA CCs, or for PUCCH and PUSCH on Intra-band CA CCs, or regardless of the type of CA (Inter-band CA / Intra-band CA).
[0129] In perspective 5, the availability of support for simultaneous transmission may be determined by a combination of one or more perspectives selected from perspectives 1 to 4.
[0130] For example, if simultaneous transmission of PUCCH and PUSCH with different priorities is supported, simultaneous transmission of a PUCCH containing a HARQ-ACK with one priority and a PUSCH without a UCI having the same priority as the PUCCH may also be supported.
[0131] (9) Example of change 2 The following describes a modified example of the embodiment, Part 2. The NG-RAN20 (gNB100) may enable and disable simultaneous transmission. Enabling / disabling simultaneous transmission may be done by RRC settings, by DCI, or by MAC CE messages.
[0132] In Option 1, enabling / disabling simultaneous transmission may be defined at the same level as the support status for simultaneous transmission as described in Perspectives 1 to 5 above.
[0133] For example, in cases where the support for simultaneous transmission is determined based on perspective 1, NG-RAN20(gNB100) may enable / disable simultaneous transmission as follows: NG-RAN20(gNB100) may enable simultaneous transmission of PUCCH / PUSCH when PUCCH / PUSCH have different priorities. NG-RAN20(gNB100) may disable simultaneous transmission of PUCCH / PUSCH when PUCCH / PUSCH have the same priority.
[0134] In cases where the support for simultaneous transmission is determined based on perspectives 1 and 2 (for example, in cases where simultaneous transmission of PUCCH / PUSCH is supported when PUCCH has different priorities and PUCCH contains HP HARQ-ACK), NG-RAN20(gNB100) may enable / disable simultaneous transmission as follows: NG-RAN20(gNB100) may enable simultaneous transmission of PUCCH / PUSCH when PUCCH / PUSCH has different priorities and PUCCH contains HP HARQ-ACK. NG-RAN20(gNB100) may disable simultaneous transmission of PUCCH / PUSCH when PUCCH / PUSCH has the same priority and PUCCH does not contain HP HARQ-ACK. NG-RAN20(gNB100) may disable simultaneous transmission of PUCCH / PUSCH if PUCCH / PUSCH have the same priority and PUCCH contains HP HARQ-ACK. NG-RAN20(gNB100) may also disable simultaneous transmission of PUCCH / PUSCH if PUCCH / PUSCH have different priorities and PUCCH does not contain HP HARQ-ACK.
[0135] In Option 2, whether or not to perform simultaneous transmission may be determined at a higher level than the support status for simultaneous transmission as shown in Perspectives 1 to 5 above. A higher level may mean that additional conditions are imposed on the support status. A higher level may also mean that additional conditions are imposed on the enabling / disabling of NG-RAN20 (gNB100).
[0136] Specifically, UE200 may determine whether additional conditions are met when it receives notification or a setting from NG-RAN20 (gNB100) to enable or disable simultaneous transmission. If the additional conditions are met, UE200 will perform simultaneous PUCCH / PUSCH transmission; if the additional conditions are not met, it may choose not to perform simultaneous PUCCH / PUSCH transmission.
[0137] For example, consider a case where the support for simultaneous transmission is determined based on perspective 1. In such a case, NG-RAN20 (gNB100) may enable or disable simultaneous transmission of PUCCH / PUSCH. UE200 may perform simultaneous transmission of PUCCH / PUSCH with different priorities, but may not perform simultaneous transmission of PUCCH / PUSCH with the same priority.
[0138] Let's consider a case where the support for simultaneous transmission is determined based on perspectives 1 and 2 (for example, a case where simultaneous transmission of PUCCH / PUSCH is supported when PUCCH has different priorities and PUCCH contains HP HARQ-ACK). In such a case, NG-RAN20 (gNB100) may enable simultaneous transmission of PUCCH / PUSCH with different priorities and disable simultaneous transmission of PUCCH / PUSCH with the same priority. UE200 may perform simultaneous transmission of PUCCH / PUSCH when PUCCH / PUSCH has different priorities and PUCCH contains HP HARQ-ACK. UE200 does not have to perform simultaneous transmission of PUCCH / PUSCH when PUCCH / PUSCH has different priorities and PUCCH does not contain HP HARQ-ACK. UE200 does not have to perform simultaneous transmission of PUCCH / PUSCH when PUCCH / PUSCH has the same priority.
[0139] (10) Other embodiments Although the present invention has been described above in accordance with the embodiments, it will be obvious to those skilled in the art that the present invention is not limited to these descriptions and that various modifications and improvements are possible.
[0140] Although not specifically mentioned in the disclosure above, which of the above options to apply may be determined by higher-layer parameters, reported by UE 200 capability information (UE Capability), or predetermined by the wireless communication system 10. Furthermore, which of the above options to apply may be determined by higher-layer parameters and UE Capability. The options may include options such as a first identification method, a second identification method, and a third identification method. The options may also include options such as specific conditions used in the first identification method, the second identification method, and the third identification method.
[0141] Here, UE Capability may include the following information elements:
[0142] Firstly, UE Capability may include an information element that defines whether or not it supports the function of multiplexing a specific UCI onto a UCI on PUCCH or PUSCH with the same or different priority levels.
[0143] Secondly, UE Capability may include an information element that defines whether or not it supports the function of multiplexing a specific UCI on a PUCCH of the same or different priority level as the specific UCI, before multiplexing the specific UCI on a PUCCH of the same or different priority level as the specific UCI.
[0144] Thirdly, UE Capability may include an information element that defines whether or not it supports the ability to multiplex a specific UCI on an uplink channel of the same priority as the specific UCI before multiplexing the specific UCI on an uplink channel of a different priority than the specific UCI.
[0145] Fourth, UE Capability may include an information element that defines whether or not it supports features that support perspective 1 regarding PHY priority.
[0146] Fifth, UE Capability may include an information element that defines whether or not it supports the functionality that relates to the type of UCI (Universal User Interface).
[0147] Fifth, UE Capability may include an information element that defines whether or not it supports the functionality that supports UCI's perspective 3 regarding multiples.
[0148] Sixth, UE Capability may include an information element that defines whether or not it supports the functionality that supports perspective 4 regarding the type of CA.
[0149] Although not specifically mentioned in the disclosure above, an uplink channel (PUCCH / PUSCH) that overlaps in time with a specific PUCCH may mean an uplink channel (PUCCH / PUSCH) scheduled in the same time unit (slot or sub-slot) as the specific PUCCH.
[0150] The block diagrams (Figures 4 and 5) used in the description of the embodiments above show functional units. 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 using one device that is physically or logically coupled, or it may be realized using two or more physically or logically separated devices that are directly or indirectly connected (for example, using wired or wireless connections). A functional block may also be realized by combining the above one device or the above multiple devices with software.
[0151] Functions include, but are not limited to, judgment, decision, judgment, calculation, calculation, processing, derivation, investigation, exploration, confirmation, reception, transmission, output, access, resolution, selection, selection, establishment, comparison, assumption, expectation, assumption, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating (mapping), and assigning. For example, a functional block (configuration part) that enables transmission is called a transmitting unit or transmitter. In any case, as mentioned above, the method of implementation is not particularly limited.
[0152] Furthermore, the gNB100 and UE200 (the device) described above may function as a computer that processes the wireless communication method of this disclosure. Figure 11 shows an example of the hardware configuration of the device. As shown in Figure 11, the device may be configured as a computer device including a processor 1001, memory 1002, storage 1003, communication device 1004, input device 1005, output device 1006, and bus 1007.
[0153] In the following explanation, the term "device" can be replaced with "circuit," "device," "unit," etc. The hardware configuration of the device may include one or more of the devices shown in the diagram, or it may be configured to omit some of the devices.
[0154] Each functional block of the device (see Figure 4) is implemented by any hardware element of the computer device, or a combination of such hardware elements.
[0155] Furthermore, each function in the device is realized by loading predetermined software (programs) onto hardware such as the processor 1001 and memory 1002, which allows the processor 1001 to perform calculations, control communication by the communication device 1004, and control at least one of data reading and writing in the memory 1002 and storage 1003.
[0156] The processor 1001 controls the entire computer, for example, by running an operating system. The processor 1001 may consist of a central processing unit (CPU) that includes interfaces with peripheral devices, control units, arithmetic units, registers, and so on.
[0157] Furthermore, the processor 1001 reads programs (program code), 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 accordingly. The program used is one that causes the computer to execute at least a part of the operations described in the above embodiment. Moreover, the above-mentioned various processes may be executed by one processor 1001, or by two or more processors 1001 simultaneously or sequentially. The processor 1001 may be implemented by one or more chips. The program may also be transmitted from a network via a telecommunications line.
[0158] Memory 1002 is a computer-readable recording medium and may consist of at least one of the following: Read Only Memory (ROM), Erasable Programmable ROM (EPROM), Electrically Erasable Programmable ROM (EEPROM), Random Access Memory (RAM), etc. Memory 1002 may also be called a register, cache, main memory, etc. Memory 1002 can store a program (program code), software modules, etc., that can execute a method according to one embodiment of this disclosure.
[0159] Storage 1003 is a computer-readable recording medium and may consist of at least one of the following: an optical disc such as a Compact Disc ROM (CD-ROM), a hard disk drive, a flexible disk, a magneto-optical disk (e.g., a compact disc, a digital multipurpose disc, a Blu-ray® disc), a smart card, flash memory (e.g., a card, a stick, a key drive), a floppy® disk, a magnetic strip, etc. Storage 1003 may also be called an auxiliary storage device. The recording medium described above may also be, for example, a database, server, or other suitable medium including at least one of memory 1002 and storage 1003.
[0160] The communication device 1004 is hardware (transceiver / receiver device) for communicating between computers via at least one of a wired network and a wireless network, and is also called a network device, network controller, network card, communication module, etc.
[0161] The communication device 1004 may be configured to include, for example, a high-frequency switch, a duplexer, a filter, a frequency synthesizer, etc., in order to implement at least one of frequency division duplex (FDD) and time division duplex (TDD).
[0162] The input device 1005 is an input device that accepts input from an external source (e.g., a keyboard, mouse, microphone, switch, button, sensor, etc.). The output device 1006 is an output device that outputs to an external source (e.g., a display, speaker, LED lamp, etc.). The input device 1005 and the output device 1006 may be configured as an integrated unit (e.g., a touch panel).
[0163] Furthermore, 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 different buses may be configured for each device.
[0164] Furthermore, the device may include hardware such as a microprocessor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a programmable logic device (PLD), and a field-programmable gate array (FPGA), and some or all of the functional blocks may be implemented by such hardware. For example, processor 1001 may be implemented using at least one of these hardware components.
[0165] Furthermore, notification of information is not limited to the embodiments / models described herein and may be carried out by other means. For example, notification of information may be carried out by physical layer signaling (e.g., Downlink Control Information (DCI), Uplink Control Information (UCI)), upper layer signaling (e.g., RRC signaling, Medium Access Control (MAC) signaling, broadcast information (Master Information Block (MIB), System Information Block (SIB))), other signals, or combinations thereof. RRC signaling may also be called RRC messages, and may be, for example, RRC Connection Setup messages, RRC Connection Reconfiguration messages, etc.
[0166] Each aspect / embodiment described herein may be applied to at least one of the following: 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®, GSM®, CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi®), IEEE 802.16 (WiMAX®), IEEE 802.20, Ultra-WideBand (UWB), Bluetooth®, and other appropriate systems, as well as next-generation systems extended based thereon. Furthermore, multiple systems may be applied in combination (for example, a combination of at least one of LTE and LTE-A with 5G).
[0167] The processing procedures, sequences, flowcharts, etc., of each aspect / embodiment described herein may be reordered, provided they are consistent with each other. For example, the methods described herein present various step elements in an exemplary order and are not limited to that specific order.
[0168] The specific operations described in this disclosure as being performed by a base station may, in some cases, be performed by its upper node. 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 can be performed by the base station and at least one other network node (for example, an MME or S-GW, but not limited to these). Although the above example illustrates a case where there is one other network node besides the base station, it may also be a combination of multiple other network nodes (for example, an MME and an S-GW).
[0169] Information and signals (such as data) can be output from a higher layer (or lower layer) to a lower layer (or higher layer). Input and output may occur via multiple network nodes.
[0170] The input and output information may be stored in a specific location (e.g., memory) or managed using a management table. The input and output information may be overwritten, updated, or appended to. Output information may be deleted. Input information may be transmitted to other devices.
[0171] The determination may be made by a value represented by 1 bit (0 or 1), by a boolean value (true or false), or by a numerical comparison (for example, a comparison with a predetermined value).
[0172] Each aspect / embodiment described herein may be used individually, in combination, or switched between as needed during implementation. Furthermore, notification of specific information (e.g., notification that "X is") is not limited to explicit notification, but may also be implicit (e.g., by not providing such notification).
[0173] Software should be broadly interpreted to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, procedures, functions, and so on, whether they are called software, firmware, middleware, microcode, hardware description languages, or by any other name.
[0174] Furthermore, software, instructions, information, etc., may be transmitted and received via a transmission medium. For example, if software is transmitted from a website, server, or other remote source using at least one of wired technology (such as coaxial cable, fiber optic cable, twisted pair, or Digital Subscriber Line (DSL)) and wireless technology (such as infrared or microwave), then at least one of these wired and wireless technologies is included in the definition of a transmission medium.
[0175] The information, signals, etc. described in this disclosure may be represented using any of the various 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 voltage, current, electromagnetic waves, magnetic fields or magnetic particles, optical fields or photons, or any combination thereof.
[0176] In addition, terms used in this disclosure and terms necessary for understanding this disclosure may be replaced with terms having the same or similar meanings. For example, at least one of the channel and symbol may be a signal (signaling). Also, a signal may be a message. Furthermore, a component carrier (CC) may be called a carrier frequency, cell, frequency carrier, etc.
[0177] The terms “system” and “network” as used in this disclosure are interchangeable.
[0178] Furthermore, the information, parameters, etc., described in this disclosure may be expressed using absolute values, relative values from a given value, or corresponding other information. For example, wireless resources may be indicated by an index.
[0179] The names used for the parameters described above are not restrictive in any way. Furthermore, the formulas and other expressions using these parameters may differ from those expressly disclosed in this disclosure. Since various channels (e.g., PUCCH, PDCCH, etc.) and information elements can be identified by any suitable name, the various names assigned to these various channels and information elements are not restrictive in any way.
[0180] In this disclosure, terms such as "Base Station (BS)," "wireless base station," "fixed station," "NodeB," "eNodeB (eNB)," "gNodeB (gNB)," "access point," "transmission point," "reception point," "transmission / reception point," "cell," "sector," "cell group," "carrier," and "component carrier" may be used interchangeably. Base stations may also be referred to by terms such as macrocell, small cell, femtocell, and picocell.
[0181] A base station can house one or more (e.g., three) cells (also called sectors). When a base station houses multiple cells, the entire coverage area of the base station can be divided into multiple smaller areas, each of which can also be provided with communication services by a base station subsystem (e.g., a small indoor base station (Remote Radio Head: RRH)).
[0182] The terms "cell" or "sector" refer to a portion or all of the coverage area of at least one of the base stations and base station subsystems that provide communication services in this coverage.
[0183] In this disclosure, terms such as "Mobile Station (MS)," "user terminal," "User Equipment (UE)," and "terminal" may be used interchangeably.
[0184] 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 several other appropriate terms.
[0185] 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 mobile body, the mobile body itself, etc. The mobile body may be a vehicle (e.g., a car, an airplane, etc.), an unmanned mobile 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 be 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.
[0186] Furthermore, the term "base station" in this disclosure may be interpreted as "mobile station" (user terminal, hereinafter the same). For example, each aspect / embodiment of this 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), Vehicle-to-Everything (V2X), etc.). In this case, the mobile station may have the functions that a base station has. Also, terms such as "uplink" and "downlink" may be interpreted as terms corresponding to terminal-to-terminal communication (for example, "side"). For example, uplink channel, downlink channel, etc. may be interpreted as side channel.
[0187] Similarly, the term "mobile station" in this disclosure may be interpreted as "base station." In this case, the base station may be configured to have the functions that a mobile station has.
[0188] A wireless frame may consist of one or more frames in the time domain. Each of these frames in the time domain may be called a subframe.
[0189] A subframe may further consist 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.
[0190] Numerology may be communication parameters applied to at least one of the transmission and reception of a signal or channel. Numerology may include, for example, at least one of the following: subcarrier spacing (SCS), bandwidth, symbol length, cyclic prefix length, transmission time interval (TTI), number of symbols per TTI, radio frame configuration, specific filtering processes performed by the transceiver in the frequency domain, and specific windowing processes performed by the transceiver in the time domain.
[0191] A slot may consist of one or more symbols in the time domain (such as Orthogonal Frequency Division Multiplexing (OFDM) symbols or Single Carrier Frequency Division Multiple Access (SC-FDMA) symbols). A slot may also be a time unit based on neurology.
[0192] A slot may include multiple minislots. Each minislot may consist of one or more symbols in the time domain. Minislots may also be called subslots. Minislots may consist 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.
[0193] Wireless frames, subframes, slots, minislots, and symbols all represent units of time when transmitting a signal. Different names may be used for each of these terms.
[0194] 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. In other words, at least one of a subframe and a TTI may be a subframe (1 ms) in existing LTE, a period shorter than 1 ms (e.g., 1-13 symbols), or a period longer than 1 ms. Note that the unit representing the TTI may be called a slot, minislot, etc., instead of a subframe.
[0195] Here, TTI refers to, for example, the smallest unit of time for scheduling in wireless communication. For example, in an LTE system, the base station schedules each user terminal to allocate wireless resources (such as the frequency bandwidth and transmission power available to each user terminal) in TTI units. However, the definition of TTI is not limited to this.
[0196] TTI may be a transmission time unit for channel-encoded data packets (transport blocks), code blocks, code words, etc., or it may be a processing unit for scheduling, link adaptation, etc. Given a TTI, the actual time interval (e.g., number of symbols) to which the transport block, code block, code word, etc. are mapped may be shorter than the given TTI.
[0197] Furthermore, if one slot or one mini-slot is referred to as TTI, then one or more TTIs (i.e., one or more slots or one or more mini-slots) may constitute the minimum time unit of scheduling. In addition, the number of slots (number of mini-slots) that constitute the minimum time unit of scheduling may be controlled.
[0198] A TTI with a time length of 1ms may also be called a normal TTI, long TTI, normal subframe, long subframe, slot, etc. A TTI shorter than a normal TTI may also be called a shortened TTI, short TTI, partial or fractional TTI, shortened subframe, short subframe, mini slot, sub slot, slot, etc.
[0199] Furthermore, long TTIs (e.g., normal TTIs, subframes, etc.) may be interpreted as TTIs with a time length exceeding 1 ms, and short TTIs (e.g., shortened TTIs, etc.) may be interpreted as TTIs with a TTI length less than that of a long TTI but 1 ms or more.
[0200] A resource block (RB) is a resource allocation unit in the time domain and frequency domain, and in the frequency domain, it may contain one or more consecutive subcarriers. The number of subcarriers in an RB may be the same regardless of the neurology, for example, 12. The number of subcarriers in an RB may be determined based on the neurology.
[0201] Furthermore, the time domain of RB may contain one or more symbols and may be the length of one slot, one minislot, one subframe, or one TTI. One TTI, one subframe, etc., may each consist of one or more resource blocks.
[0202] One or more RBs may also be called Physical RBs (PRBs), Sub-Carrier Groups (SCGs), Resource Element Groups (REGs), PRB pairs, RB pairs, etc.
[0203] Furthermore, a resource block may consist of one or more resource elements (REs). For example, one RE may be a radio resource area comprising one subcarrier and one symbol.
[0204] A Bandwidth Part (BWP), also known as a partial bandwidth, may represent a subset of consecutive common resource blocks (RBs) for a given neurology on a given carrier. Here, the common RBs may be identified by an index of the RBs relative to the carrier's common reference point. PRBs may be defined and numbered within a BWP.
[0205] A BWP may include BWPs for UL (UL BWP) and BWPs for DL (DL BWP). One or more BWPs may be configured within a single carrier for a UE.
[0206] At least one of the configured BWPs may be active, and the UE does not need to assume that it will send or receive a given signal / channel outside of the active BWP. In this disclosure, terms such as "cell" and "carrier" may be read as "BWP".
[0207] The structures described above, such as wireless frames, subframes, slots, minislots, and symbols, are merely illustrative. For example, the number of subframes included in a wireless frame, the number of slots per subframe or wireless 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, and the number of symbols, symbol length, and cyclic prefix (CP) length within a TTI can be varied in various ways.
[0208] The terms “connected,” “coupled,” or any variation thereof, mean 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” with each other. The coupling or connection between elements may be physical, logical, or a combination thereof. For example, “connection” may be reinterpreted as “access.” As used in this disclosure, two elements may be considered to be “connected” or “coupled” with each other using at least one of one or more wires, cables, and printed electrical connections, and, in some non-limiting and non-exclusive examples, electromagnetic energy having wavelengths in the radio frequency domain, microwave domain, and optical (both visible and invisible) domain.
[0209] The reference signal can also be abbreviated as Reference Signal (RS), and may be called a pilot depending on the applicable standard.
[0210] In this disclosure, the phrase "based on" does not mean "based solely on" unless otherwise specified. In other words, the phrase "based on" means both "based solely on" and "based at least on."
[0211] In the configuration of each of the above devices, "means" may be replaced with "part," "circuit," "device," etc.
[0212] Any reference to elements using designations such as “First,” “Second,” etc., as 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 way to distinguish between two or more elements. Accordingly, references to the First and Second elements do not imply that only two elements may be employed therein, or that the First element must precede the Second element in any way.
[0213] Where the terms “include,” “including,” and variations thereof are used in this disclosure, these terms are intended to be inclusive, as is the term “comprising.” Furthermore, the term “or” as used in this disclosure is not intended to mean exclusive OR.
[0214] In this disclosure, if articles are added through translation, such as a, an, and the in English, this disclosure may include the fact that the noun following these articles is plural.
[0215] As used in this disclosure, the terms “determining” and “determining” may encompass a wide variety of actions. “Determining” may include, for example, judging, calculating, computing, processing, deriving, investigating, looking up, searching, inquiry (e.g., searching in a table, database, or other data structure), and ascertaining. “Determining” may also include, for example, receiving (e.g., receiving information), transmitting (e.g., sending information), input, output, and accessing (e.g., accessing data in memory). Furthermore, "judgment" and "decision" can include considering something as having been "judged" or "decided" after resolving, selecting, choosing, establishing, comparing, etc. In other words, "judgment" and "decision" can include considering something as having been "judged" or "decided" after some action. Also, "judgment (decision)" can be reinterpreted as "assuming," "expecting," or "considering."
[0216] In this 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 "combine" may be interpreted similarly to "different."
[0217] Although the present disclosure has been described in detail above, it will be clear to those skilled in the art that the present disclosure is not limited to the embodiments described herein. The present disclosure can be implemented in modified and altered forms without departing from the intent and scope of the present disclosure as defined by the claims. Therefore, the descriptions in the present disclosure are illustrative and not intended to be restrictive in any way. [Explanation of Symbols]
[0218] 10 Wireless communication systems 20 NG-RAN 100 gNB 110 Receiving unit 120 Transmitter 130 Control Unit 200 UE 210 Wireless signal transmission and reception unit 220 Amplifier section 230 Modulation / Demodulation Section 240 Control signal / reference signal processing unit 250 Encoding / Decoding Unit 260 Data transmission / reception unit 270 Control Unit 1001 Processor 1002 memory 1003 Storage 1004 Communication device 1005 Input device 1006 Output device 1007 Bus
Claims
1. A transmitting unit that transmits uplink control information via at least one of a physical uplink control channel or a physical uplink sharing channel, A receiving unit receives a wireless resource control layer message from the network that enables simultaneous transmission of the physical uplink control channel and the physical uplink sharing channel. A terminal comprising: a control unit that enables simultaneous transmission of the physical uplink control channel and the physical uplink sharing channel upon receipt of the wireless resource control layer message when the physical uplink control channel and the physical uplink sharing channel have the same priority.
2. The terminal according to claim 1, wherein the transmitting unit reports to the network whether the terminal supports simultaneous transmission of the physical uplink control channel and the physical uplink sharing channel having the same priority.
3. Equipped with terminals and base stations, The aforementioned terminal is A transmitting unit that transmits uplink control information to the base station via at least one of a physical uplink control channel or a physical uplink sharing channel, A receiving unit receives a wireless resource control layer message from the network that enables simultaneous transmission of the physical uplink control channel and the physical uplink sharing channel. A wireless communication system comprising: a control unit that enables simultaneous transmission of the physical uplink control channel and the physical uplink sharing channel upon reception of the wireless resource control layer message when the physical uplink control channel and the physical uplink sharing channel have the same priority.
4. The steps include transmitting uplink control information via at least one of a physical uplink control channel or a physical uplink sharing channel, The steps include receiving a wireless resource control layer message from the network that enables simultaneous transmission of the physical uplink control channel and the physical uplink sharing channel, A wireless communication method comprising the step of enabling simultaneous transmission of the physical uplink control channel and the physical uplink sharing channel upon reception of the wireless resource control layer message, when the physical uplink control channel and the physical uplink sharing channel have the same priority.
Citation Information
Patent Citations
Communication method and device
CN111756508A
Uplink control information multiplexing on physical uplink shared channels in new radio
US20190349917A1
Base stations, user equipments, and related communication methods
WO2018111948A1
User terminal and radio communication method
WO2018131675A1
Corresponding configuration for simultaneous physical uplink control channel pucch and physical uplink shared channel pusch transmission
WO2019096059A1