Terminal, wireless communication system, and wireless communication method
The system effectively multiplexes UCIs with different priorities by determining PUCCH resources based on downlink control information association, enhancing communication efficiency by ensuring high-priority UCI transmission.
Patent Information
- Application Number
- JP2023520597
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Filing Date
- 2021-05-10
- Publication Date
- 2025-10-22
- Estimated Expiration
- 2041-05-10
AI Technical Summary
Existing wireless communication systems face challenges in appropriately determining PUCCH resources when multiplexing two or more UCIs with different priorities, leading to inefficiencies in resource allocation and transmission.
A terminal and wireless communication system that multiplex first and second uplink control information onto an uplink control channel, with a control unit determining resources based on the association of first downlink control information with the first uplink control information, allowing for dynamic and semi-static resource allocation.
This approach enables appropriate determination of PUCCH resources, ensuring efficient transmission of high-priority UCI while accommodating low-priority UCI, thereby optimizing communication performance.
Smart Images

Figure 0007758733000004 
Figure 0007758733000005 
Figure 0007758733000006
Abstract
Description
[Technical Field]
[0001] The present disclosure relates to a terminal, a wireless communication system, and a wireless communication method that perform wireless communication, and more particularly to a terminal, a wireless communication system, and a wireless communication method that are related to multiplexing uplink control information onto an uplink channel. [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 supports simultaneous transmission of two or more uplink channels (a physical uplink control channel (PUCCH) and a physical uplink shared channel (PUSCH)) transmitted in the same slot.
[0004] Furthermore, in Release 17 of 3GPP, it was agreed to support the operation of multiplexing UCI (Uplink Control Information) having different priorities onto a PUCCH (for example, Non-Patent Document 1). [Prior art documents] [Non-patent literature]
[0005] [Non-Patent Document 1] "Enhanced Industrial Internet of Things (IoT) and ultra-reliable and low latency communication", RP-201310, 3GPP TSG RAN Meeting #86e, 3GPP, July 2020 Summary of the Invention
[0006] Under such circumstances, the inventors have conducted extensive research and found that it is necessary to appropriately determine PUCCH resources when two or more UCIs are multiplexed onto a PUCCH.
[0007] Therefore, the present invention has been made in view of the above circumstances, and has an object to provide a terminal, a radio communication system, and a radio communication method that are capable of multiplexing two or more UCIs into appropriate PUCCH resources.
[0008] The present disclosure provides a terminal including: a control unit capable of multiplexing first uplink control information of a first priority and second uplink control information of a second priority onto an uplink control channel; and a communication unit that transmits an uplink signal via the uplink control channel, wherein the control unit determines resources of the uplink control channel based on whether first downlink control information is associated with the first uplink control information.
[0009] The present disclosure provides a wireless communication system including a terminal and a base station, wherein the terminal includes a control unit capable of multiplexing first uplink control information of a first priority and second uplink control information of a second priority onto an uplink control channel, and a communication unit that transmits an uplink signal via the uplink control channel, and the control unit determines resources for the uplink control channel based on whether first downlink control information is associated with the first uplink control information.
[0010] The present disclosure provides a wireless communication method, comprising: a step of multiplexing first uplink control information of a first priority and second uplink control information of a second priority onto an uplink control channel; a step of transmitting an uplink signal via the uplink control channel; and a step of determining resources for the uplink control channel based on whether first downlink control information is associated with the first uplink control information. [Brief explanation of the drawings]
[0011] [Figure 1] FIG. 1 is a diagram showing the overall schematic configuration of a wireless communication system 10. As shown in FIG. [Figure 2] FIG. 2 is a diagram showing frequency ranges used in the wireless communication system 10. As shown in FIG. [Figure 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 the UE 200. [Figure 5] Figure 5 is a functional block diagram of gNB100. [Figure 6] FIG. 6 is a diagram illustrating rate matching. [Figure 7] FIG. 7 is a diagram illustrating rate matching. [Figure 8] FIG. 8 is a diagram illustrating rate matching. [Figure 9] FIG. 9 is a diagram for explaining the first operation example. [Figure 10] FIG. 10 is a diagram for explaining the operation example 2-1. [Figure 11] FIG. 11 is a diagram for explaining the operation example 2-2. [Figure 12] FIG. 12 is a diagram for explaining the operation example 2-3. [Figure 13] FIG. 13 is a diagram showing an example of the hardware configuration of gNB100 and UE200. DETAILED DESCRIPTION OF THE INVENTION
[0012] Hereinafter, embodiments 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 descriptions thereof will be omitted as appropriate.
[0013] [Embodiment] (1) Overall configuration of the wireless communication system 1 is a schematic diagram of an overall configuration of a wireless communication system 10 according to an 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).
[0014] The wireless communication system 10 may be a wireless communication system conforming to a system called Beyond 5G, 5G Evolution, or 6G.
[0015] The NG-RAN 20 includes a radio base station 100A (hereinafter, gNB100A) and a radio base station 100B (hereinafter, gNB100B). Note that the specific configuration of the radio communication system 10, including the number of gNBs and UEs, is not limited to the example shown in FIG. 1.
[0016] 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."
[0017] The gNB100A and gNB100B are radio base stations conforming to 5G, and perform 5G radio communication with the UE 200. The gNB100A, 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 aggregates and uses multiple component carriers (CCs), and Dual Connectivity (DC), which simultaneously communicates on two or more transport blocks between the UE and each of two NG-RAN nodes.
[0018] The wireless communication system 10 also supports a plurality of frequency ranges (FR).
[0019] 2, the wireless communication system 10 supports FR1 and FR2. The frequency bands of each FR are as follows:
[0020] FR1: 410 MHz to 7.125 GHz FR2: 24.25 GHz~52.6 GHz 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 (including 240 kHz) and a bandwidth (BW) of 50 to 400 MHz.
[0021] Note that SCS may be interpreted as numerology, which is defined in 3GPP TS38.300 and corresponds to one subcarrier spacing in the frequency domain.
[0022] Furthermore, the wireless communication system 10 also supports frequency bands higher than the FR2 frequency band. Specifically, the wireless communication system 10 supports frequency bands above 52.6 GHz up to 71 GHz or 114.25 GHz. For convenience, such high frequency bands may be referred to as "FR2x."
[0023] To solve the problem of increased phase noise in high frequency bands, when using bands above 52.6 GHz, Cyclic Prefix-Orthogonal Frequency Division Multiplexing (CP-OFDM) / Discrete Fourier Transform - Spread (DFT-S-OFDM) with larger Sub-Carrier Spacing (SCS) may be applied.
[0024] FIG. 3 shows an example of the configuration of a radio frame, a subframe, and a slot used in the radio communication system 10. In FIG.
[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] 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.
[0027] The time direction (t) shown in Fig. 3 may be called a time domain, a symbol period, or a symbol time, etc. The frequency direction may be called a frequency domain, a resource block, a subcarrier, a bandwidth part (BWP), etc.
[0028] DMRS is a type of reference signal and is prepared for various channels. Here, unless otherwise specified, it may refer to a downlink data channel, specifically, a DMRS for a PDSCH (Physical Downlink Shared Channel). However, a DMRS for an uplink data channel, specifically, a PUSCH (Physical Uplink Shared Channel), may be interpreted as being the same as a DMRS for a PDSCH.
[0029] The DMRS may be used for channel estimation at the device, for example, as part of coherent demodulation at the UE 200. The DMRS may only be present in resource blocks (RBs) used for PDSCH transmission.
[0030] A DMRS may have multiple mapping types. Specifically, a DMRS has mapping type A and mapping type B. In mapping type A, the first DMRS is placed in the second or third symbol of a slot. In mapping type A, the DMRS may be mapped based on the slot boundary, regardless of where in the slot actual data transmission starts. The reason why the first DMRS is placed in the second or third symbol of a slot may be interpreted as being to place the first DMRS after a control resource set (CORESET).
[0031] In mapping type B, the first DMRS may be placed in the first symbol of the data allocation, i.e., the position of the DMRS may be given relative to where the data is placed, rather than relative to the slot boundary.
[0032] Furthermore, DMRS may have multiple types. Specifically, DMRS has Type 1 and Type 2. Type 1 and Type 2 differ in 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 wireless communication system Next, the functional block configuration of the wireless communication system 10 will be described.
[0034] First, the functional block configuration of the UE 200 will be described.
[0035] Fig. 4 is a functional block diagram of UE 200. As shown in Fig. 4, UE 200 includes radio signal transmitting / receiving unit 210, amplifier unit 220, modem unit 230, control signal / reference signal processing unit 240, encoding / decoding unit 250, data transmitting / receiving unit 260, and control unit 270.
[0036] The radio signal transmitting / receiving unit 210 transmits and receives radio signals conforming to NR. The radio signal transmitting / receiving unit 210 supports Massive MIMO, CA that uses a bundle of multiple CCs, and DC that simultaneously communicates between a UE and two NG-RAN nodes.
[0037] 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 modulation / demodulation unit 230 to a predetermined power level. The amplifier unit 220 also amplifies the RF signal output from the radio signal transmission / reception unit 210.
[0038] The modem unit 230 performs data modulation / demodulation, transmission power setting, resource block allocation, etc. for each predetermined communication destination (gNB 100 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 the uplink (UL) but also for the downlink (DL).
[0039] The control signal / reference signal processor 240 performs 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 .
[0040] Specifically, the control signal / reference signal processor 240 receives various control signals, for example, control signals of a radio resource control layer (RRC), transmitted via a predetermined control channel from the gNB 100. The control signal / reference signal processor 240 also transmits various control signals to the gNB 100 via a predetermined control channel.
[0041] The control signal / reference signal processor 240 performs processing using reference signals (RS) such as a Demodulation Reference Signal (DMRS) and a Phase Tracking Reference Signal (PTRS).
[0042] DMRS is a reference signal (pilot signal) known between the base station and the terminal for estimating the 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.
[0043] 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.
[0044] The channels include control channels and data channels, such as 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).
[0045] Furthermore, the data channel includes a PDSCH (Physical Downlink Shared Channel) and a PUSCH (Physical Uplink Shared Channel). Data refers to data transmitted via the data channel. The data channel may be interpreted as a shared channel.
[0046] Here, the control signal and reference signal processor 240 may receive downlink control information (DCI). The DCI includes existing fields for storing DCI Formats, Carrier indicator (CI), BWP indicator, Frequency Domain Resource Allocation (FDRA), Time Domain Resource Allocation (TDRA), Modulation and Coding Scheme (MCS), HARQ Process Number (HPN), New Data Indicator (NDI), Redundancy Version (RV), etc.
[0047] The value stored in the DCI Format field is an information element that specifies the format of the DCI. 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 information elements (pdsch-TimeDomainAllocationList, pusch-TimeDomainAllocationList) included in the RRC message. The time domain resource may be identified by the value stored in the TDRA field and a 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 the MCS and an MCS table. The MCS table may be specified by an RRC message or may be determined by RNTI scrambling. The value stored in the HPN field is an information element that specifies the HARQ process to which the DCI is applied. The value stored in the NDI field is an information element for specifying whether the data to which the 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 the DCI is applied.
[0048] In the embodiment, the control signal and reference signal processing unit 240 constitutes a communication unit that transmits an uplink signal via an uplink control channel (PUCCH).
[0049] The encoding / decoding unit 250 performs data division / concatenation and channel coding / decoding for each predetermined communication destination (gNB100 or another gNB).
[0050] 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, decodes the data output from the modem unit 230, and concatenates the decoded data.
[0051] The data transmitter / receiver 260 transmits and receives Protocol Data Units (PDUs) and Service Data Units (SDUs). Specifically, the data transmitter / receiver 260 assembles and disassembles 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)). The data transmitter / receiver 260 also performs data error correction and retransmission control based on HARQ (Hybrid Automatic Repeat Request).
[0052] The control unit 270 controls each functional block constituting the UE 200. In the embodiment, the control unit 270 constitutes a control unit that can multiplex first uplink control information (first UCI) of a first priority and second uplink control information (second UCI) of a second priority onto an uplink control channel (PUCCH).
[0053] Here, a first priority and a second priority may be assumed as the priority of a UCI. The first priority may be different from the second priority. For example, two types of UCI priority, HP (High Priority) and LP (Low Priority), are exemplified. For example, the first priority may be HP and the second priority may be LP. The first UCI may be referred to as an HP UCI, and the second UCI may be referred to as an LP UCI. However, three or more types of priority may be defined as the priority of a UCI.
[0054] Under this assumption, the control unit 270 determines the resource of the uplink control channel (PUCCH) based on whether or not the first downlink control information (first DCI) is associated with the first UCI (HP UCI).
[0055] "The first DCI is associated with the HP UCI" means that, when it is assumed that the HP UCI is not multiplexed with the LP UCI, the HP UCI is transmitted using a resource specified by the first DCI from among resources that can be specified by the first DCI. For example, the resource that can be specified by the first DCI may be a PUCCH resource that is set for the HP UCI by an information element (e.g., PUCCH-ResourceSet(s)) included in an RRC message (e.g., PUCCH-Config).
[0056] "The first DCI is not associated with the HP UCI" means that, when it is assumed that the HP UCI is not multiplexed with the LP UCI, the HP UCI is transmitted using a resource configured as a resource other than the resource that can be specified by the first DCI. For example, the resource configured as a resource other than the resource that can be specified by the first DCI may be a PUCCH resource configured for the HP UCI by an information element (e.g., SPS (Semi-Persistent Scheduling)-PUCCH-AN-List) included in an RRC message (e.g., PUCCH-Config).
[0057] The UCI may include an acknowledgement (HARQ-ACK) for one or more TBs, a scheduling request (SR) for requesting resource scheduling, and channel state information (CSI) for indicating the channel state.
[0058] The control unit 270 controls the control signal / reference signal processing unit 240 described above, and the control signal / reference signal processing unit 240 may constitute a communication unit that transmits an uplink signal via a PUSCH multiplexed with UCI.
[0059] Secondly, we will explain the functional block configuration of gNB100.
[0060] Fig. 5 is a functional block diagram of the gNB 100. As shown in Fig. 5, the gNB 100 includes a receiving unit 110, a transmitting unit 120, and a control unit 130.
[0061] The receiving unit 110 receives various signals from the UE 200. The receiving unit 110 may receive an UL signal via a PUCCH or a PUSCH.
[0062] The transmitter 120 transmits various signals to the UE 200. The transmitter 120 may transmit a DL signal via a PDCCH or a PDSCH. In the embodiment, the transmitter 120 configures a communication unit that transmits to the UE 200 an information element that explicitly or implicitly indicates at least one of enabling and disabling of multiplexing of a UCI of a second priority onto a PUSCH of a first priority.
[0063] The control unit 130 controls the gNB 100. The control unit 130 may assume that the resource of the uplink control channel (PUCCH) is determined based on whether or not the first downlink control information (first DCI) is associated with the first UCI (HP UCI).
[0064] (3) Rate Matching Rate matching will be described below. Specifically, rate matching of UCI in the case where UCI is multiplexed onto UL SCH will be described. Here, HARQ-ACK, CSI Part 1, and CSI Part 2 will be exemplified as UCI. Note that HARQ-ACK, CSI-Part 1, and CSI-Part 2 are executed separately.
[0065] As shown in FIG. 6, a bit sequence of "C00, C01, ..." is obtained by applying channel coding to a HARQ-ACK having a bit sequence of "X0, X1, ...". Rate matching is applied to such a bit sequence. The bit sequence after rate matching (E UCI ) is E UCI =N L ×Q' ACK ×Q m It may be represented by:
[0066] N L is the number of PUSCH transmission layers. Q m is the modulation condition of PUSCH. For example, Q' ACK is expressed by the following formula (TS38.212 V16.3.0 §6.3.2.4.1.1 “HARQ-ACK”).
[0067]
number
[0068] In addition, Q' ACK is the minimum value of the item (left side) defined by the coefficient (β) and the item (right side) defined by the scaling factor (α). Therefore, it should be noted that the RE (Resource Element) used for transmitting HARQ-ACK may be limited by the scaling factor (α).
[0069] As shown in FIG. 7, a bit sequence of "C00, C01, ..." is obtained by applying channel coding to CSI Part 1 having a bit sequence of "Y0, Y1, ...". Rate matching is applied to such a bit sequence. The bit sequence after rate matching (E UCI ) is E UCI =N L ×Q' CSI-part1 ×Q m It may be represented by:
[0070] N Lis the number of PUSCH transmission layers. Q m is the modulation condition of PUSCH. For example, Q' CSI-part1 is expressed by the following formula (TS38.212 V16.3.0 §6.3.2.4.1.2 “CSI part 1”).
[0071]
number
[0072] In addition, Q' ACK is the minimum value of the item (left side) defined by the coefficient (β) and the item (right side) defined by the scaling factor (α). Therefore, it should be noted that the RE (Resource Element) used for transmitting CSI Part 1 may be limited by the scaling factor (α).
[0073] As shown in FIG. 8, a bit sequence of "C00, C01, ..." is obtained by applying channel coding to CSI Part 2 having a bit sequence of "Z0, Z1, ...". Rate matching is applied to such a bit sequence. The bit sequence after rate matching (E UCI ) is E UCI =N L ×Q' CSI-part2 ×Q m It may be represented by:
[0074] N L is the number of PUSCH transmission layers. Q m is the modulation condition of PUSCH. For example, Q' CSI-part2 is expressed by the following formula (TS38.212 V16.3.0 §6.3.2.4.1.3 “CSI part 2”).
[0075]
number
[0076] In addition, Q'ACK is the minimum value of the item (left side) defined by the coefficient (β) and the item (right side) defined by the scaling factor (α). Therefore, it should be noted that the RE (Resource Element) used for transmitting CSI Part 2 may be limited by the scaling factor (α).
[0077] (4) Example of operation An example of the operation of the embodiment will be described below. A method for determining a PUCCH resource (hereinafter referred to as a PUCCH resource) when an HP UCI and an LP UCI can be multiplexed on a PUCCH will be described below. As described above, the UE 200 determines the PUCCH resource based on whether the first DCI is associated with the HP UCI. Details of the method for determining the PUCCH resource are as follows.
[0078] (4.1) Example 1 The following describes Operation Example 1. In Operation Example 1, a case where the first DCI is associated with the HP UCI will be described.
[0079] As shown in Fig. 9, when the first DCI is associated with the HP UCI, the UE 200 determines a PUCCH resource (hereinafter referred to as a Multiplexed PUCCH resource) for multiplexing the HP UCI and the LP UCI from among resources that can be specified by the first DCI. The resources that can be specified by the first DCI are PUCCH resources set for the HP UCI by an information element (PUCCH-ResourceSet(s)) included in an RRC message (e.g., PUCCH-Config). The first DCI includes an information element (hereinafter referred to as a PUCCH Resource Indicator) that specifies a PUCCH resource from among the PUCCH resources set by the PUCCH-ResourceSet(s).
[0080] FIG. 9 illustrates a case in which the PUCCH resource identified by ID#2 included in PUCCH-ResourceSet#2 is determined as the multiplexed PUCCH resource.
[0081] Here, the Multiplexed PUCCH resource may be determined based on the following options.
[0082] For example, the multiplexed PUCCH resource may be determined based on the PUCCH resource indicator. The following options are available as a method for identifying the PUCCH resource indicator.
[0083] In option 1, the PUCCH Resource Indicator specifying the Multiplexed PUCCH resource may be the PUCCH Resource Indicator included in the nearest first DCI among the first DCIs associated with the HP UCI.
[0084] In option 2, the PUCCH Resource Indicator specifying the Multiplexed PUCCH resource may be the PUCCH Resource Indicator included in the nearest DCI among the first DCI associated with the HP UCI and the second DCI associated with the LP UCI when the second DCI associated with the LP UCI is notified.
[0085] In option 3, when a DCI enabling multiplexing of an HP UCI and an LP UCI is defined, the PUCCH Resource Indicator specifying the Multiplexed PUCCH resource may be a PUCCH Resource Indicator included in the DCI enabling multiplexing of an HP UCI and an LP UCI.
[0086] In Option 4, the PUCCH Resource Indicator specifying the multiplexed PUCCH resource may be determined based on higher layer configuration. The higher layer configuration may include RRC configuration configured by an RRC message or may be configuration using a MAC CE message.
[0087] In option 5, the PUCCH resource indicator that specifies the multiplexed PUCCH resource may be predetermined in the wireless communication system 10. For example, it may be defined that "0" is used as the PUCCH resource indicator.
[0088] Alternatively, the multiplexed PUCCH resource may be determined based on a specific condition. The specific condition may be a condition for selecting a PUCCH resource with the smallest delay from among the PUCCH-ResourceSet(s) configured for the HP UCI. The specific condition may be a condition for selecting a PUCCH resource with the lowest target code rate from among the PUCCH-ResourceSet(s) configured for the HP UCI.
[0089] (4.2) Example 2 The following describes Operation Example 2. In Operation Example 2, a case where the first DCI is not associated with the HP UCI will be described. As Operation Example 2, any one of the operation examples shown below may be adopted.
[0090] (4.2.1) Example 2-1 As shown in Fig. 10, UE 200 determines a PUCCH resource (multiplexed PUCCH resource) on which the HP UCI and the LP UCI are multiplexed from resources configured as resources other than those that can be specified by the first DCI. The resources configured as resources other than those that can be specified by the first DCI are resources that are not dynamically specified by the first DCI and may be statically or semi-persistently configured resources. For example, the resources configured as resources other than those that can be specified by the first DCI may be PUCCH resources configured for the HP UCI by an information element (e.g., SPS-PUCCH-AN-List) included in an RRC message (e.g., PUCCH-Config).
[0091] FIG. 10 illustrates a case where the PUCCH resource identified by ID#2 included in the SPS-PUCCH-AN-List is determined as the multiplexed PUCCH resource.
[0092] (4.2.2) Example 2-2 As shown in Fig. 11, when a second DCI is associated with an LP UCI, UE 200 determines a PUCCH resource (multiplexed PUCCH resource) for multiplexing the HP UCI and the LP UCI from among resources that can be specified by the second DCI. The resources that can be specified by the second DCI are PUCCH resources set for the LP UCI by an information element (PUCCH-ResourceSet(s)) included in an RRC message (e.g., PUCCH-Config). The second DCI includes an information element (PUCCH Resource Indicator) that specifies a PUCCH resource from among the PUCCH resources set by the PUCCH-ResourceSet(s).
[0093] FIG. 11 illustrates a case in which the PUCCH resource identified by ID#2 included in PUCCH-ResourceSet#2 is determined as the multiplexed PUCCH resource.
[0094] Here, the Multiplexed PUCCH resource may be determined based on the following options.
[0095] For example, the multiplexed PUCCH resource may be determined based on the PUCCH resource indicator. The following options are available as a method for identifying the PUCCH resource indicator.
[0096] In option 1, the PUCCH Resource Indicator specifying the Multiplexed PUCCH resource may be the PUCCH Resource Indicator included in the nearest second DCI among the second DCIs associated with the LP UCI.
[0097] In option 2, when a DCI enabling multiplexing of an HP UCI and an LP UCI is defined, the PUCCH Resource Indicator specifying the Multiplexed PUCCH resource may be a PUCCH Resource Indicator included in the DCI enabling multiplexing of an HP UCI and an LP UCI.
[0098] In Option 3, the PUCCH Resource Indicator specifying the multiplexed PUCCH resource may be determined based on higher layer configuration. The higher layer configuration may include RRC configuration configured by an RRC message or may be configuration using a MAC CE message.
[0099] In option 4, the PUCCH resource indicator that specifies the multiplexed PUCCH resource may be predetermined in the wireless communication system 10. For example, it may be defined that "0" is used as the PUCCH resource indicator.
[0100] Alternatively, the multiplexed PUCCH resource may be determined based on a specific condition. The specific condition may be a condition for selecting a PUCCH resource with the smallest delay from among the PUCCH-ResourceSet(s) configured for the LP UCI. The specific condition may be a condition for selecting a PUCCH resource with the lowest target code rate from among the PUCCH-ResourceSet(s) configured for the LP UCI.
[0101] (4.2.3) Example 2-3 As shown in Fig. 12, UE 200 drops the LP UCI. That is, UE 200 transmits only the HP UCI without multiplexing the HP UCI with the LP UCI. Here, UE 200 may determine a PUCCH resource to be used for transmitting the HP UCI from among PUCCH resources configured for the HP UCI by an information element (e.g., SPS-PUCCH-AN-List) included in an RRC message (e.g., PUCCH-Config).
[0102] (5) Actions and Effects In the embodiment, the UE 200 determines a PUCCH resource (Multiplexed PUCCH resource) based on whether the first DCI is associated with the HP UCI. According to such a configuration, when a case is assumed in which two or more UCIs are multiplexed in the PUCCH, the method for determining the Multiplexed PUCCH resource is clarified, and therefore, the Multiplexed PUCCH resource can be appropriately determined.
[0103] For example, as described in the first operation example, when the first DCI is associated with the HP UCI, the UE 200 may determine a PUCCH resource (multiplexed PUCCH resource) for multiplexing the HP UCI and the LP UCI from among resources that can be specified by the first DCI. With this configuration, a PUCCH resource that can be dynamically specified is determined as a multiplexed PUCCH resource, so that it is possible to use a PUCCH resource that appropriately reflects the status of the NG RAN 20.
[0104] Alternatively, as described in operation example 2-1, when the first DCI is not associated with the HP UCI, UE 200 may determine a PUCCH resource (multiplexed PUCCH resource) for multiplexing the HP UCI and the LP UCI from among resources that are semi-statically set as PUCCH resources for the HP UCI. With this configuration, since the PUCCH resource for the HP UCI is used, when a case in which the HP UCI and the LP UCI are multiplexed is assumed, it is possible to appropriately transmit at least the HP UCI.
[0105] Alternatively, as described in operation example 2-2, when the first DCI is not associated with the HP UCI and the second DCI is associated with the LP UCI, the UE 200 may determine a PUCCH resource (multiplexed PUCCH resource) for multiplexing the HP UCI and the LP UCI from among resources that can be specified by the second DCI. With this configuration, a PUCCH resource that can be dynamically specified is determined as a multiplexed PUCCH resource, making it possible to use PUCCH resources that appropriately reflect the status of the NG RAN 20.
[0106] (6) Appendix Although not particularly limited, the effective payload size of the HP UCI and the LP UCI may be determined by the coding rate, which may be determined by the following options:
[0107] (6.1) Option 1 In the following, we will explain Option 1. In Option 1, we will explain a specific parameter (omega_LP_HP) that applies to either the LP UCI or the HP UCI. Here, it applies to the omega_LP_HP for the LP UCI.
[0108] The coding rate of the HP UCI (HP_UCI_coding_rate) may be a coding rate applied to the HP UCI or a coding rate applied to the HP (High Priority) PUCCH resource. These coding rates are coding rates before being multiplied by omega_LP_HP, and may be coding rates (original coding rates) used when UCIs with different priorities are not multiplexed.
[0109] The LP UCI coding rate (LP_UCI_coding_rate) may be the coding rate obtained by multiplying HP_UCI_coding_rate by omega_LP_HP.
[0110] (6.2) Option 2 In the following, we will explain Option 2. Option 2 explains a specific parameter (omega_LP_HP) that applies to either the LP UCI or the HP UCI. Here, omega_LP_HP applies to the HP UCI.
[0111] The HP UCI co-de-rate (HP_UCI_coding_rate) may be the coding rate obtained by dividing the LP_UCI_coding_rate by omega_LP_HP. In other words, the HP_UCI_coding_rate may be the coding rate obtained by multiplying the LP_UCI_coding_rate by the reciprocal of omega_LP_HP.
[0112] The coding rate of the LP UCI (LP_UCI_coding_rate) may be a coding rate applied to the LP UCI or a coding rate applied to the LP (Low Priority) PUCCH resource. These coding rates are coding rates before being multiplied by omega_LP_HP, and may be coding rates (original coding rates) used when UCIs with different priorities are not multiplexed.
[0113] (6.3) Option 3 Option 3 will be described below. Option 3 describes a specific parameter (omega_LP_HP) that is applied to either the LP UCI or the HP UCI. Here, Option 3 describes a case where the PUCCH format is one of PUCCH Format 2, PUCCH Format 3, and PUCCH Format 4. Option 3 describes a case where the LP_UCI_coding_rate can be changed without changing the HP_UCI_coding_rate.
[0114] The coding rate of the HP UCI (HP_UCI_coding_rate) may be the coding rate applied to the HP UCI or the coding rate applied to the HP (High Priority) PUCCH resource. These coding rates are coding rates before being multiplied by omega_LP_HP and may be referred to as original coding rates.
[0115] The LP UCI coding rate (LP_UCI_coding_rate) may be expressed as LP_UCI_coding_rate=min(omega_LP_HP*HP_UCI_coding_rate, Upper_bound_LP_UCI_coding_rate).
[0116] Upper_bound_LP_UCI_coding_rate represents the upper limit of the co-rate of the LP UCI, and is calculated based on the total number of REs (Resource Elements) of the PUCCH resource on which the LP_UCI is multiplexed, the HP_UCI_coding_rate, the HP UCI payload, and the LP UCI payload. The LP UCI payload may be a payload without bundling or partial dropping of LP UCI bits, or may be a payload with bundling or partial dropping of LP UCI bits.
[0117] (6.4) Option 4 The following describes Option 4. Option 4 describes a specific parameter (omega_LP_HP) that applies to either the LP UCI or the HP UCI. Here, the case where the PUCCH format is one of PUCCH Format 2, PUCCH Format 3, and PUCCH Format 4 is described. Option 4 describes the case where both the LP_UCI_coding_rate and the HP_UCI_coding_rate can be changed.
[0118] The HP UCI co-de-rate (HP_UCI_coding_rate) and the LP UCI coding rate (LP_UCI_coding_rate) may be calculated based on the total number of REs of the PUCCH resource in which the LP UCI and the HP UCI are multiplexed, the HP UCI payload, and the LP UCI payload. The LP UCI payload may be a payload in which LP UCI bit bundling or partial dropping is not performed, or may be a payload in which LP UCI bit bundling or partial dropping is performed.
[0119] However, a constraint may be imposed that the LP_UCI_coding_rate is a coding rate obtained by multiplying the HP_UCI_coding_rate by omega_LP_HP.
[0120] (6.5) Option 5 Option 5 will be explained below. Option 5 explains the case where specific parameters (omega_LP) applied to LP UCI and specific parameters (omega_HP) applied to HP UCI are defined separately. Option 5 illustrates the case where omega_LP is not provided and omega_HP is provided.
[0121] The coding rate of the HP UCI (HP_UCI_coding_rate) may be a coding rate obtained by multiplying the original coding rate by omega_HP. The original coding rate may be the coding rate applied to the HP UCI or the coding rate applied to the HP PUCCH resource.
[0122] The LP UCI coding rate (LP_UCI_coding_rate) may be expressed as LP_UCI_coding_rate=min(HP_UCI_coding_rate, original coding rate), where the original coding rate may be the coding rate applied to the LP UCI or may be the coding rate applied to the LP PUCCH resource.
[0123] (6.6) Option 6 Option 6 will be explained below. Option 6 explains the case where specific parameters (omega_LP) applied to LP UCI and specific parameters (omega_HP) applied to HP UCI are defined separately. Option 5 illustrates the case where omega_LP is provided without omega_HP being provided.
[0124] The HP UCI coding rate (HP_UCI_coding_rate) may be the coding rate applied to the HP UCI or the coding rate applied to the HP PUCCH resource. These coding rates may be referred to as original coding rates.
[0125] The coding rate of the LP UCI (LP_UCI_coding_rate) may be a coding rate obtained by multiplying the original coding rate by omega_LP. The original coding rate may be the coding rate applied to the LP UCI or may be the coding rate applied to the LP PUCCH resource.
[0126] However, a constraint may be imposed that the LP_UCI_coding_rate does not become larger than the HP_UCI_coding_rate.
[0127] (6.7) Option 7 Option 7 will be explained below. Option 7 explains the case where specific parameters (omega_LP) applied to LP UCI and specific parameters (omega_HP) applied to HP UCI are defined separately. Option 7 illustrates the case where both omega_LP and omega_HP are provided.
[0128] The coding rate of the HP UCI (HP_UCI_coding_rate) may be a coding rate obtained by multiplying the original coding rate by omega_HP. The original coding rate may be the coding rate applied to the HP UCI or the coding rate applied to the HP PUCCH resource.
[0129] The coding rate of the LP UCI (LP_UCI_coding_rate) may be a coding rate obtained by multiplying the original coding rate by omega_LP. The original coding rate may be the coding rate applied to the LP UCI or may be the coding rate applied to the LP PUCCH resource.
[0130] However, a constraint may be imposed that the LP_UCI_coding_rate does not become larger than the HP_UCI_coding_rate.
[0131] (6.8) Option 8 Option 8 will be described below. Option 8 describes a case where specific parameters (omega_LP) applied to LP UCI and specific parameters (omega_HP) applied to HP UCI are defined separately. Here, a case where the PUCCH format is one of PUCCH Format 2, PUCCH Format 3, and PUCCH Format 4 will be described. Option 8 illustrates an example where omega_LP is not provided and omega_HP is provided.
[0132] The coding rate of the HP UCI (HP_UCI_coding_rate) may be a coding rate obtained by multiplying the original coding rate by omega_HP. The original coding rate may be the coding rate applied to the HP UCI or the coding rate applied to the HP PUCCH resource.
[0133] The LP UCI coding rate (LP_UCI_coding_rate) may be expressed as LP_UCI_coding_rate=min(Upper_bound_LP_UCI_coding_rate, HP_UCI_coding_rate, original coding rate).
[0134] Upper_bound_LP_UCI_coding_rate represents the upper limit of the co-rate of the LP UCI and is calculated based on the total number of REs (Resource Elements) of the PUCCH resource onto which the LP_UCI is multiplexed, the HP_UCI_coding_rate, the HP UCI payload, and the LP UCI payload. The LP UCI payload may be a payload without bundling or partial dropping of LP UCI bits, or may be a payload with bundling or partial dropping of LP UCI bits. The original coding rate may be the coding rate applied to the LP UCI or the coding rate applied to the LP PUCCH resource.
[0135] (6.9) Option 9 Option 9 will be described below. Option 9 describes a case where specific parameters (omega_LP) applied to LP UCI and specific parameters (omega_HP) applied to HP UCI are defined separately. Here, a case where the PUCCH format is one of PUCCH Format 2, PUCCH Format 3, and PUCCH Format 4 will be described. Option 9 illustrates an example where omega_LP is provided without omega_HP being provided.
[0136] The HP UCI coding rate (HP_UCI_coding_rate) may be the coding rate applied to the HP UCI or the coding rate applied to the HP PUCCH resource. These coding rates may be referred to as original coding rates.
[0137] The LP UCI coding rate (LP_UCI_coding_rate) may be expressed as LP_UCI_coding_rate=min(Upper_bound_LP_UCI_coding_rate, omega_LP*original coding rate).
[0138] Upper_bound_LP_UCI_coding_rate represents the upper limit of the co-rate of the LP UCI and is calculated based on the total number of REs (Resource Elements) of the PUCCH resource onto which the LP_UCI is multiplexed, the HP_UCI_coding_rate, the HP UCI payload, and the LP UCI payload. The LP UCI payload may be a payload without bundling or partial dropping of LP UCI bits, or may be a payload with bundling or partial dropping of LP UCI bits. The original coding rate may be the coding rate applied to the LP UCI or the coding rate applied to the LP PUCCH resource.
[0139] However, a constraint may be imposed that the LP_UCI_coding_rate does not become larger than the HP_UCI_coding_rate.
[0140] (6.10) Option 10 Option 10 will be described below. Option 10 will explain the case where specific parameters (omega_LP) applied to LP UCI and specific parameters (omega_HP) applied to HP UCI are defined separately. Here, the case where the PUCCH format is one of PUCCH Format 2, PUCCH Format 3, and PUCCH Format 4 will be explained. Option 10 will exemplify the case where both omega_LP and omega_HP are provided.
[0141] The coding rate of the HP UCI (HP_UCI_coding_rate) may be a coding rate obtained by multiplying the original coding rate by omega_HP. The original coding rate may be the coding rate applied to the HP UCI or the coding rate applied to the HP PUCCH resource.
[0142] The LP UCI coding rate (LP_UCI_coding_rate) may be expressed as LP_UCI_coding_rate=min(Upper_bound_LP_UCI_coding_rate, omega_LP*original coding rate).
[0143] Upper_bound_LP_UCI_coding_rate represents the upper limit of the co-rate of the LP UCI and is calculated based on the total number of REs (Resource Elements) of the PUCCH resource onto which the LP_UCI is multiplexed, the HP_UCI_coding_rate, the HP UCI payload, and the LP UCI payload. The LP UCI payload may be a payload without bundling or partial dropping of LP UCI bits, or may be a payload with bundling or partial dropping of LP UCI bits. The original coding rate may be the coding rate applied to the LP UCI or the coding rate applied to the LP PUCCH resource.
[0144] However, a constraint may be imposed that the LP_UCI_coding_rate does not become larger than the HP_UCI_coding_rate.
[0145] (7) Other embodiments The present invention has been described above in accordance with the embodiments, but 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.
[0146] Although not specifically mentioned in the above disclosure, which of the above-described options (e.g., Operation Example 1, Operation Example 2, and each option included in these operation examples) to apply may be set by higher layer parameters, may be reported by capability information (UE Capability) of UE 200, or may be predetermined in wireless communication system 10. Furthermore, which of the above-described options to apply may be determined by higher layer parameters and UE Capability.
[0147] Here, the UE Capability may include the following information elements. Specifically, the UE Capability may include an information element indicating whether the UE 200 supports multiplexing of an HP UCI and an LP UCI. The UE Capability may include an information element indicating whether the UE 200 supports multiplexing of an HP UCI and an LP UCI associated with a first DCI (for example, Operation Example 1). The UE Capability may include an information element indicating whether the UE 200 supports multiplexing of an HP UCI not associated with the first DCI and an LP UCI not associated with the second DCI (for example, Operation Example 2-1). The UE Capability may include an information element indicating whether the UE 200 supports multiplexing of an HP UCI not associated with the first DCI and an LP UCI associated with the second DCI (for example, Operation Example 2-2). The UE Capability may include an information element indicating whether the UE 200 supports multiplexing of the HP UCI and the LP UCI using a PUCCH resource set for the HP UCI by an information element (e.g., PUCCH-ResourceSet(s)) included in an RRC message (e.g., PUCCH-Config). The UE Capability may include an information element indicating whether the UE 200 supports multiplexing of the HP UCI and the LP UCI using a PUCCH resource set for the HP UCI by an information element (e.g., SPS-PUCCH-AN-List) included in an RRC message (e.g., PUCCH-Config).
[0148] In the above disclosure, a case where the first priority and the second priority are different is exemplified. However, the above disclosure is not limited to this. The above disclosure may also be applied to a case where the first priority and the second priority are the same.
[0149] In the above disclosure, a case where the first priority is HP and the second priority is LP is exemplified. However, the above disclosure is not limited to this. The above disclosure may be applied to a case where the first priority is LP and the second priority is HP.
[0150] The block diagrams (FIGS. 4 and 5) used in the description of the above-described embodiments show 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 using a single device that is physically or logically coupled, or may be realized using two or more physically or logically separated devices that are connected directly or indirectly (for example, by wire, wirelessly, etc.) and these multiple devices. The functional block may be realized by combining the single device or the multiple devices with software.
[0151] Functions include, but are not limited to, judgment, determination, judgment, calculation, computation, processing, derivation, investigation, search, confirmation, reception, transmission, output, access, resolution, selection, election, establishment, comparison, assumption, expectation, regard, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, and assignment. For example, a functional block (component) that performs transmission is called a transmitting unit or transmitter. As mentioned above, there are no particular limitations on how each is implemented.
[0152] Furthermore, the above-described gNB100 and UE200 (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 the 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, a bus 1007, etc.
[0153] In the following description, the term "apparatus" can 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.
[0154] 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.
[0155] In addition, each function of the device is realized by loading specified software (programs) onto hardware such as processor 1001 and memory 1002, causing processor 1001 to perform calculations, control communication via communication device 1004, and control at least one of reading and writing data in memory 1002 and storage 1003.
[0156] The processor 1001 controls the entire computer by running, for example, an operating system, and may be configured as a central processing unit (CPU) including an interface with peripheral devices, a control unit, an arithmetic unit, a register, and the like.
[0157] The processor 1001 also reads 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 in accordance with these. The programs used are those that cause a computer to execute at least some of the operations described in the above-mentioned embodiments. Furthermore, the various processes described above 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.
[0158] The memory 1002 is a computer-readable recording medium and may be configured by, for example, at least one of 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., that can execute a method according to an embodiment of the present disclosure.
[0159] Storage 1003 is a computer-readable recording medium, and may be, for example, at least one of 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 disc), a smart card, a flash memory (e.g., a card, a stick, a key drive), a floppy disk, a magnetic strip, etc. Storage 1003 may also be referred to as an auxiliary storage device. The above-mentioned recording medium may be, for example, a database, a server, or other appropriate medium including at least one of memory 1002 and storage 1003.
[0160] The communication device 1004 is hardware (transmission / reception device) for communicating 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.
[0161] The communication device 1004 may be configured to include a high-frequency switch, a duplexer, a filter, a frequency synthesizer, etc. to realize, for example, at least one of Frequency Division Duplex (FDD) and Time Division Duplex (TDD).
[0162] The input device 1005 is an input device (for example, a keyboard, a mouse, a microphone, a switch, a button, a sensor, etc.) that receives input from the outside. The output device 1006 is an output device (for example, a display, a speaker, an LED lamp, etc.) that outputs to the outside. The input device 1005 and the output device 1006 may be integrated into one device (for example, a touch panel).
[0163] Furthermore, each device such as the processor 1001 and the memory 1002 is connected to 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.
[0164] 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), or a field programmable gate array (FPGA), 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.
[0165] 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 thereof. Furthermore, the RRC signaling may be referred to as an RRC message, and may be, for example, an RRC Connection Setup message, an RRC Connection Reconfiguration message, or the like.
[0166] 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, a 4th generation mobile communication system (4G), a 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), or other suitable system, and a next-generation system extended based on these. Furthermore, a combination of multiple systems (e.g., a combination of at least one of LTE and LTE-A and 5G) may also be applied.
[0167] The order of the procedures, sequences, flowcharts, etc. of each aspect / embodiment described in this disclosure may be changed unless it is consistent. 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.
[0168] In the present disclosure, a specific operation described as being 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 another network node other than the base station (for example, but not limited to, an MME or an S-GW). Although the above example illustrates a case where there is one other network node other than the base station, a combination of multiple other network nodes (for example, an MME and an S-GW) may also be used.
[0169] Information and 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.
[0170] The input and output information may be stored in a specific location (for example, memory) or may be managed using a management table. The input and output information may be overwritten, updated, or added. The output information may be deleted. The input information may be sent to another device.
[0171] The determination may be made based on a value represented by one bit (0 or 1), a Boolean value (true or false), or a numerical comparison (e.g., comparison with a predetermined value).
[0172] Each aspect / embodiment described in this disclosure may be used alone, in combination, or switched depending on the implementation. Furthermore, notification of predetermined information (e.g., notification that "X is true") is not limited to being done explicitly, but may be done implicitly (e.g., by not notifying the predetermined information).
[0173] 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.
[0174] Software, instructions, information, etc. may also be transmitted or received over a transmission medium. For example, if 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), then these wired and / or wireless technologies are included within the definition of transmission media.
[0175] The information, signals, etc. described in this disclosure may be represented using any of a variety of different technologies. For example, 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.
[0176] Note that terms explained 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 a channel and a symbol may be a signal (signaling). Furthermore, a signal may be a message. Furthermore, a component carrier (CC) may be called a carrier frequency, a cell, a frequency carrier, etc.
[0177] As used in this disclosure, the terms "system" and "network" are used interchangeably.
[0178] Furthermore, the information, parameters, etc. described in the present disclosure may be expressed using absolute values, may be expressed using relative values from a predetermined value, or may be expressed using other corresponding information. For example, a radio resource may be indicated by an index.
[0179] The names used for the above-described parameters are not intended to be limiting in any way. Furthermore, the mathematical expressions 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 intended to be limiting in any way.
[0180] 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," 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 accommodate one or more (e.g., three) cells (also called sectors). When a base station accommodates multiple cells, the overall coverage area of the base station can be divided into multiple smaller areas, and each smaller area can be provided with communication service by a base station subsystem (e.g., a small indoor base station (Remote Radio Head: RRH)).
[0182] The terms "cell" or "sector" refer to part or all of the coverage area of a base station and / or base station subsystem that provides communication services within that coverage area.
[0183] In this disclosure, the terms "Mobile Station (MS)," "user terminal," "User Equipment (UE)," "terminal," etc. 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 some other suitable terminology.
[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 also include devices that do not necessarily move during communication operations. 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, a base station in the present disclosure may be read as a mobile station (user terminal, the same applies hereinafter). For example, the aspects / embodiments 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, terms such as uplink channel and downlink channel may be read as side channel.
[0187] 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.
[0188] A radio frame may be made up of one or more frames in the time domain, each of which may be called a subframe.
[0189] A subframe may further be composed of one or more slots in the time domain, and may have a fixed time length (e.g., 1 ms) that is independent of numerology.
[0190] Numerology may be a communication parameter applied to at least one of transmission and reception of a signal or channel, such as subcarrier spacing (SCS), bandwidth, symbol length, cyclic prefix length, transmission time interval (TTI), number of symbols per TTI, radio frame structure, specific filtering operations performed by a transceiver in the frequency domain, and specific windowing operations performed by a transceiver in the time domain.
[0191] A slot may consist of one or more symbols in the time domain (such as an Orthogonal Frequency Division Multiplexing (OFDM) symbol or a Single Carrier Frequency Division Multiple Access (SC-FDMA) symbol). A slot may be a time unit based on numerology.
[0192] A slot may include multiple minislots. Each minislot may consist of one or multiple symbols in the time domain. A minislot may also be called a subslot. A minislot 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] The radio frame, subframe, slot, minislot, and symbol all represent time units for transmitting signals, and may be referred to by other names corresponding to the radio frame, subframe, slot, minislot, and symbol.
[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. That is, at least one of the subframe and the 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 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. However, the definition of TTI is not limited to this.
[0196] 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) to which a transport block, a code block, a code word, etc. is actually mapped may be shorter than the TTI.
[0197] When one slot or one minislot is called a TTI, one or more TTIs (i.e., one or more slots or one or more minislots) may be the minimum time unit for scheduling. Also, the number of slots (minislots) constituting the minimum time unit for scheduling may be controlled.
[0198] A TTI having a time length of 1 ms may be called a regular TTI (TTI in LTE Rel. 8-12), normal TTI, long TTI, regular subframe, normal subframe, long subframe, slot, etc. A TTI shorter than a regular TTI may be called a shortened TTI, short TTI, partial or fractional TTI, shortened subframe, short subframe, minislot, subslot, slot, etc.
[0199] In addition, a long TTI (e.g., a normal TTI, a subframe, etc.) may be interpreted as a TTI having a time length of more than 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.
[0200] A resource block (RB) is a resource allocation unit in the time domain and 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 numerology, for example, 12. The number of subcarriers included in an RB may also be determined based on numerology.
[0201] The time domain of an RB may include one or more symbols and may have a length of one slot, one minislot, one subframe, or one TTI. One TTI, one subframe, etc. may each be composed of one or more resource blocks.
[0202] Note that one or more RBs may also 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.
[0203] 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.
[0204] 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 given numerology on a given carrier, where the common RBs may be identified by their index relative to a common reference point of the carrier. PRBs may be defined in a given BWP and numbered within that BWP.
[0205] 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.
[0206] 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 read as "BWP."
[0207] The above-described 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.
[0208] 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 one or more wires, cables, and / or 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.
[0209] The reference signal may also be abbreviated as Reference Signal (RS), and may also be called a pilot depending on the applicable standard.
[0210] 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."
[0211] The "means" in the configuration of each of the above devices may be replaced with "part," "circuit," "device," etc.
[0212] As used in this disclosure, any reference to an element using a designation such as "first," "second," etc. 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.
[0213] When used in this disclosure, the terms "include," "including," and variations thereof are intended to be inclusive, similar to the term "comprising." Furthermore, when used in this disclosure, the term "or" is not intended to be an exclusive or.
[0214] In this disclosure, where articles are added by translation, such as a, an, and the in English, the disclosure may include that the nouns following these articles are in the plural form.
[0215] 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, searching, inquiring (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 memory), and the like. Furthermore, "judgment" and "decision" can include regarding resolving, selecting, choosing, establishing, comparing, etc. as having been "judged" or "decided." In other words, "judgment" and "decision" can include regarding some action as having been "judged" or "decided." Furthermore, "judgment (decision)" can be interpreted as "assuming," "expecting," "considering," etc.
[0216] 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."
[0217] 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 herein. 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]
[0218] 10. Wireless communication systems 20 NG-RAN 100 gNB 110 Receiving unit 120 Transmitter 130 Control Unit 200 UE 210 Radio signal transmitter / receiver 220 Amplifier section 230 Modulation and Demodulation Unit 240 Control signal / reference signal processing section 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 control unit that multiplexes first uplink control information of a first priority and second uplink control information of a second priority; a communication unit that transmits the first uplink control information and the second uplink control information via a same uplink control channel, The control unit determining resources of the same uplink control channel based on a most recent first downlink control information among a plurality of first downlink control information associated with the first uplink control information; when there is no first downlink control information associated with the first uplink control information, determining a resource for the same uplink control channel from among resources set as resources different from resources that may be specified by the first downlink control information; The terminal, wherein the resource set as the different resource is a resource set for the first priority by an SPS-PUCCH-AN-List included in an RRC message.
2. 2. The terminal according to claim 1, wherein the controller determines, from among resources in a resource set associated with the first uplink control information, a resource identified by an identifier included in the most recent first downlink control information as a resource for the same uplink control channel.
3. A terminal and a base station are provided, The terminal a control unit that multiplexes first uplink control information of a first priority and second uplink control information of a second priority; a communication unit that transmits the first uplink control information and the second uplink control information via a same uplink control channel, The control unit determining resources of the same uplink control channel based on a most recent first downlink control information among a plurality of first downlink control information associated with the first uplink control information; when there is no first downlink control information associated with the first uplink control information, determining a resource for the same uplink control channel from among resources set as resources different from resources that may be specified by the first downlink control information; A wireless communication system, wherein the resource set as the different resource is a resource set for the first priority by an SPS-PUCCH-AN-List included in an RRC message.
4. multiplexing first uplink control information of a first priority and second uplink control information of a second priority; transmitting the first uplink control information and the second uplink control information via a same uplink control channel; determining resources of the same uplink control channel based on a most recent first downlink control information among a plurality of first downlink control information associated with the first uplink control information; determining, when first downlink control information associated with the first uplink control information does not exist, a resource for the same uplink control channel from among resources set as resources different from resources that may be specified by the first downlink control information; A wireless communication method, wherein the resource set as the different resource is a resource set for the first priority by an SPS-PUCCH-AN-List included in an RRC message.