Method and processing circuitry for wireless communication

Abstract

A method for a user equipment (UE) is provided. The method includes receiving a downlink control information (DCI) indicating a physical uplink control channel (PUCCH) occasion retransmission and performing the retransmission of the PUCCH occasion and a HARQ-ACK codebook associated with the PUCCH occasion based on the received DCI.

Description

Technical Field

[0001] This application relates generally to wireless communication systems, and more specifically to a method and apparatus for retransmission at the timing of Hybrid Automatic Repeat Request (HARQ) Acknowledgment (HARQ-ACK) / Physical Uplink Control Channel (PUCCH). Background Technology

[0002] Wireless mobile communication technologies use various standards and protocols to transmit data between base stations and wireless mobile devices. Wireless communication system standards and protocols may include, but are not limited to, 3GPP Long Term Evolution (LTE); 5G 3GPP New Radio (NR) standards; and technologies beyond 5G. In a 5G wireless RAN, RAN nodes may include 5G nodes, NR nodes, or gNodeBs (gNBs), which communicate with wireless communication equipment (also known as User Equipment (UE)).

[0003] Recent research on HARQ-ACK enhancements has reached a consensus, supporting the retransmission of canceled HARQ-ACKs. Further details are still under discussion to achieve efficient HARQ-ACK CB / PUCCH timing retransmissions. Summary of the Invention

[0004] According to an aspect of this disclosure, a method for a user equipment (UE) is provided, the method comprising: receiving downlink control information (DCI) indicating a physical uplink control channel (PUCCH) timing retransmission; and performing retransmission of the PUCCH timing and a HARQ-ACK codebook associated with the PUCCH timing based on the received DCI.

[0005] According to an aspect of this disclosure, a method for a base station is provided, the method comprising: constructing downlink control information (DCI) for the UE indicating the timing of retransmission of the Physical Uplink Control Channel (PUCCH); and providing the DCI to the UE for triggering the PUCCH timing retransmission.

[0006] According to an aspect of this disclosure, an apparatus for a user equipment (UE) is provided, the apparatus including one or more processors configured to perform the steps of the method described above.

[0007] According to an aspect of this disclosure, an apparatus for a base station is provided, the apparatus comprising: one or more processors configured to perform the steps of the method described above.

[0008] According to an aspect of this disclosure, a computer-readable medium having a computer program stored thereon is provided, which, when executed by one or more processors, causes a device to perform the steps of the method described above.

[0009] According to an aspect of this disclosure, an apparatus for a communication device is provided, the apparatus including means for performing the steps of the method described above.

[0010] According to an aspect of this disclosure, a computer program product includes a computer program that, when executed by one or more processors, causes a device to perform the steps of the method described above. Attached Figure Description

[0011] The features and advantages of this disclosure will become apparent from the following detailed description taken in conjunction with the accompanying drawings, which illustrate the features of this disclosure by way of example.

[0012] Figure 1 It is a block diagram of a system including base stations and user equipment (UE) according to some implementation schemes.

[0013] Figure 2 A flowchart of an exemplary method for a UE according to some implementation schemes is shown.

[0014] Figure 3 An example of an enhanced DCI format 1_2 for PUCCH timing retransmission is shown according to some implementation schemes.

[0015] Figure 4 An exemplary case is shown in which the PUCCH Priority Indicator (PPI) field is used according to some implementation schemes.

[0016] Figure 5 A schematic diagram is shown as an example of an implicit HARQ-ACK CB abandonment operation according to some implementation schemes.

[0017] Figure 6 A schematic diagram showing an example of the C-DAI and T-DAI settings for DCI format 1_2 for type 2 HARQ-ACK CB / PUCCH timing retransmission is provided.

[0018] Figure 7 A schematic diagram showing an example of the C-DAI and T-DAI settings for DCI format 1_2 for type 2 HARQ-ACK CB / PUCCH timing retransmission is provided.

[0019] Figure 8 A schematic diagram is shown as an example of retransmission for Type 1 HARQ-ACK CB / PUCCH timing.

[0020] Figure 9 A schematic diagram of another example of retransmission for Type 1 HARQ-ACK CB / PUCCH timing is shown.

[0021] Figure 10 A flowchart of an exemplary method for a base station according to some implementation schemes is shown.

[0022] Figure 11 A schematic diagram of an exemplary method for communication between a UE and a base station according to some implementation schemes is shown.

[0023] Figure 12 Communication devices (e.g., UEs or base stations) according to some implementation schemes are shown.

[0024] Figure 13 An exemplary interface of a baseband circuit according to some implementation schemes is shown.

[0025] Figure 14 The components are shown according to some implementation schemes.

[0026] Figure 15 The architecture of a wireless network according to some implementation schemes is shown. Detailed Implementation

[0027] In this disclosure, a "base station" may include RAN nodes such as an Evolved Universal Terrestrial Radio Access Network (E-UTRAN) node B (also commonly referred to as an evolved node B, enhanced node B, eNodeB, or eNB) and / or a Radio Network Controller (RNC) and / or a 5G node, New Radio (NR) node, or g node B (gNB), which communicates with wireless communication equipment also referred to as User Equipment (UE). Although some examples may be described with reference to any of E-UTRAN node B, eNB, RNC, and / or gNB, such equipment can be replaced by any type of base station.

[0028] Figure 1 It is a block diagram of a system including base stations and user equipment (UE) according to some implementation schemes. Figure 1 A wireless network 100 according to some embodiments is shown. The wireless network 100 includes a UE 101 and a base station 150 connected via an air interface 190.

[0029] UE 101 and any other UE in the system can be, for example, a laptop computer, smartphone, tablet computer, printer, machine-type device such as a smart meter or dedicated device for healthcare monitoring, remote security monitoring, intelligent transportation systems, or any other wireless device with or without a user interface. Base station 150 can provide UE 101 with network connectivity to a wider network (not shown) via air interface 190 within the base station service area provided by base station 150. In some embodiments, such a wider network can be a wide area network operated by a cellular network provider, or it can be the Internet. Each base station service area associated with base station 150 is supported by an antenna integrated with base station 150. The service area is divided into multiple sectors associated with certain antennas. Such sectors can be physically associated with fixed antennas, or can be assigned to physical areas with tunable antennas or antenna configurations that can be adjusted during beamforming to direct signals to a particular sector. For example, one implementation of base station 150 includes three sectors, each covering a 120-degree area, wherein the antenna array is pointed at each sector to provide 360-degree coverage around base station 150.

[0030] UE 101 includes control circuitry 105 coupled to transmit circuitry 110 and receive circuitry 115. Transmit circuitry 110 and receive circuitry 115 may each be coupled to one or more antennas. Control circuitry 105 may be adapted to perform operations associated with MTC. In some embodiments, control circuitry 105 of UE 101 may perform calculations or initiate measurements associated with air interface 190 to determine the channel quality of an available connection to base station 150. These calculations may be performed in conjunction with control circuitry 155 of base station 150. Transmit circuitry 110 and receive circuitry 115 may be adapted to transmit and receive data, respectively. Control circuitry 105 may be adapted or configured to perform various operations, such as the various UE-related operations described elsewhere in this disclosure. Transmit circuitry 110 may transmit multiple multiplexed uplink physical channels. These multiple uplink physical channels may be multiplexed according to time division multiplexing (TDM) or frequency division multiplexing (FDM). Transmit circuitry 110 may be configured to receive block data from control circuitry 105 for transmission across air interface 190. Similarly, receiving circuitry 115 can receive multiple multiplexed downlink physical channels from air interface 190 and relay these physical channels to control circuitry 105. Uplink and downlink physical channels can be multiplexed according to TDM or FDM. Transmitting circuitry 110 and receiving circuitry 115 can transmit and receive structured control data and content data (e.g., messages, images, video, etc.) within data blocks carried by the physical channels.

[0031] Figure 1A base station 150 according to various embodiments is also shown. The base station 150 circuitry may include control circuitry 155 coupled to transmitting circuitry 160 and receiving circuitry 165. Transmitting circuitry 160 and receiving circuitry 165 may each be coupled to one or more antennas, which may be used for communication via air interface 190.

[0032] Control circuitry 155 can be adapted to perform operations associated with the MTC. Transmitting circuitry 160 and receiving circuitry 165 can be adapted to transmit and receive data respectively within a narrow system bandwidth, which is narrower than the standard bandwidth used for personal communications. In some embodiments, for example, the transmission bandwidth can be set to or close to 1.4 MHz. In other embodiments, other bandwidths can be used. Control circuitry 155 can perform various operations, such as those associated with the base station described elsewhere in this disclosure.

[0033] Within a narrow system bandwidth, the transmitter circuit 160 can transmit multiple multiplexed downlink physical channels. These multiple downlink physical channels can be multiplexed according to TDM or FDM. The transmitter circuit 160 can transmit these multiple multiplexed downlink physical channels in a downlink superframe consisting of multiple downlink subframes.

[0034] Within a narrow system bandwidth, receiver circuit 165 can receive multiple multiplexed uplink physical channels. These multiple uplink physical channels can be multiplexed according to TDM or FDM. Receiver circuit 165 can receive these multiple multiplexed uplink physical channels in an uplink superframe composed of multiple uplink subframes.

[0035] As further described below, control circuits 105 and 155 may be involved in measuring the channel quality of air interface 190. Channel quality may be based, for example, on physical barriers between UE 101 and base station 150, electromagnetic interference from other sources, reflections, or indirect paths between UE 101 and base station 150, or other such signal noise sources. Based on channel quality, multiple retransmissions of data blocks can be scheduled, allowing transmitting circuit 110 to transmit multiple copies of the same data, and receiving circuit 115 to receive multiple copies of the same data.

[0036] The UE and various base stations described in the following implementation schemes can be provided by, for example Figure 1 The UE 101 and base station 150 are implemented as described above.

[0037] Figure 2 A flowchart of an exemplary method for a UE according to some implementation schemes is shown. Figure 2 The method 200 shown can be derived from, for example Figure 1 The UE 101 implementation is described above.

[0038] like Figure 2 As shown, the method 200 for a UE may include the following steps: S202, receiving downlink control information (DCI) indicating a physical uplink control channel (PUCCH) timing retransmission; and performing retransmission of the PUCCH timing and the HARQ-ACK codebook associated with the PUCCH timing based on the received DCI.

[0039] In some implementations, the DCI may include a PUCCH slot indicator (PSI) field, a single hybrid automatic repeat request (HARQ) acknowledgment (HARQ-ACK) request field, and a PUCCH priority indicator (PPI) field.

[0040] PSI field

[0041] For DCI format 1_2, the new field 'PSI' can be added to the existing fields in DCI format 1_2.

[0042] In some implementations, the value of the PSI field is mapped one-to-one to parameters configured by Radio Resource Control (RRC) signaling. K The value of 3.

[0043] parameter K 3 can have at least one value, and the PSI field indicates one of at least one value.

[0044] For example, K Each of at least one of the values ​​in 3 can have an index, and the PSI field can indicate the index as mapped to... K 3.

[0045] The UE can first use a set number of time slots or sub-time slots. K 3. Configure it. K The maximum value of at least one of the values ​​of 3 can be reported as part of the UE capability.

[0046] In some implementations, the bit width of the PSI field can be determined as follows: ,in I Indicates configuration by RRC signaling K The number of at least one value for the 3 parameters.

[0047] As an example, if it is K 3. If a single value is configured, the PSI field will be 0 bits, meaning it does not exist.

[0048] In some implementations, in some designs, multiple PSI fields may be included in the DCI (i.e., DCI format 1_2) to support retransmissions at multiple PUCCH times triggered by the DCI.

[0049] In addition to the one-to-one mapping format of the PSI field described above, alternative formats can also be applied as follows.

[0050] In some implementations, the PSI field can be formed as I Bitmap, in which I express K The number of parameter values, and I Each bit in the bitmap corresponds to K One of the three parameter values.

[0051] Compared to the one-to-one mapping format mentioned above, this bitmap format can support more than one HARQ-ACK / PUCCH timing that can be retransmitted in the PUCCH slot.

[0052] Regarding parameters K The physical meaning of 3 can be further understood from the following aspects.

[0053] In some implementations, at step S204, performing PUCCH timing retransmission based on DCI may include: in the time slot n When the DCI that triggers the PUCCH timing retransmission is detected, among which n Indicates the index of the time slot, in the time slot nK 3. Retransmission of the PUCCH timing indicated by the DCI and the corresponding HARQ-ACK codebook (CB) transmitted on the PUCCH timing, wherein... K 3. As indicated by DCI.

[0054] For example, if the UE detects a DCI in a time slot that is associated with a DCI2_1 format including a single HARQ-ACK request field with a value of "1", the UE can proceed in the time slot or sub-time slot of a separate PUCCH time slot indicated by DCI format 2_1. n- K 3. The HARQ-ACK CB transmitted during the PUCCH timing is retransmitted.

[0055] In some implementations, at step S204, performing PUCCH timing retransmission based on DCI may include: performing PUCCH timing retransmission in the target PUCCH timing, wherein the initial PUCCH timing for PUCCH timing retransmission has a corresponding time interval to the target PUCCH timing. K The time slot interval with a value of 3.

[0056] In other words, parameters K The value of 3 can be limited to the time slot of the retransmitted HARQ-ACK CB / PUCCH timing and the time slot in which the new target PUCCH is scheduled by triggering the DCI format to transmit the retransmitted HARQ-ACK CB in the retransmitted PUCCH timing.

[0057] Single HARQ-ACK Request Field

[0058] In some implementations, the single HARQ-ACK request field can be set to 1 bit and used to trigger a retransmission of the HARQ-ACK CB carried on the retransmitted PUCCH timing indicated by the DCI.

[0059] PPI field

[0060] In some implementations, the PPI field can be set to 1 bit.

[0061] In some implementations, the PPI field can be configured to indicate the priority of the retransmitted PUCCH.

[0062] The PPI field can be used to mitigate potential inaccuracies between the gNB and UE regarding the HARQ-ACK codebook to be retransmitted.

[0063] The PPI field of DCI format 1_2 can be used to indicate the priority value of the retransmitted PUCCH. Using this option, PUCCH retransmissions can be limited to PDCCHs triggered by PDSCHs with the same priority.

[0064] Reference Figure 4 Further details on this matter will be provided.

[0065] In some implementations, instead of using the PPI field, the priority of the retransmitted PUCCH timing can be appended to a predefined location in the retransmitted HARQ-ACK payload, for example, appended to the end of the retransmitted HARQ-ACK CB.

[0066] Figure 3 An enhanced DCI format 1_2 for timing retransmission of the PUCCH is shown according to some implementation schemes.

[0067] like Figure 3 As shown, in addition to the existing field 310 of DCI format 1_2 300, the enhanced DCI format 1_2 300 may also include a PUCCH slot indicator (PSI) field 311, a single HARQ-ACK request field 312, and a PUCCH priority indicator (PPI) field 313.

[0068] Each of the single HARQ-ACK request field 312 and the PPI field 313 may have a bit width of 1 bit. As described above, the bit width 3110 of the PSI field 311 can be determined as follows: ,in I express KThe number of at least one value of 3. For example, if K If 3 has four different values, then the PSI field 311 can have a 2-bit width.

[0069] Figure 4 An exemplary case of using the PPI field is shown according to some implementation schemes.

[0070] like Figure 4 The diagram illustrates an example of the HARQ-ACK CB inaccuracy problem and how it is resolved by introducing a PPI field.

[0071] For easier explanation of the HARQ-ACK CB inaccuracy issue, please refer to [reference needed]. Figure 4 Make specific assumptions.

[0072] Assume that four PDSCHs (i.e., low-priority PDSCHs 410 and 420, and higher-priority PDSCHs 430 and 440 compared to PDSCHs 410 and 420) are scheduled on different component carriers (CCs) of the UE (as shown in CC0 to CC2). Therefore, the gNB expects both PUCCHs 450 and 460 to be transmitted by the UE for the scheduled PDSCHs 410 to 440.

[0073] However, suppose that on the UE side, the PDCCHs scheduling PDSCH 430 and 440 are lost, and therefore the UE cannot transmit PUCCH 460. At the same time, the UE detects the lower priority PDSCHs 410 and 420, and therefore transmits the associated PUCCH 450 that was lost on the gNB side.

[0074] Without the PPI field, the UE could misinterpret it as a time slot. n DCI format 1_2 (via PDCCH470) request for retransmission is made by the UE in the time slot. nK PUCCH 450 transmitted in segment 3. However, gNB can interpret this as the retransmitted HARQ-ACKCB and time slot. nK The PUCCH 460 in section 3 is associated with this. Therefore, a HARQ-ACK CB inaccuracy issue occurs.

[0075] This issue can be resolved by indicating the PUCCH priority by setting the PPI field to '1'. Therefore, the UE will not transmit anything, i.e., DTX. Based on the time slot... nK Based on the detection results of the retransmitted PUCCH 460 in section 3, the gNB knows that PDSCH 430 and 440 were lost on the UE side, and therefore retransmits these PDSCHs in a timely manner.

[0076] Back to Figure 1This provides an implicit HARQ-ACK CB abandonment operation according to this disclosure.

[0077] In some implementations, at step S204, performing PUCCH timing retransmission based on DCI may include: in the time slot n The indication detected in the time slot nK When the PUCCH timing retransmission is triggered in step 3, among which... n Indicates the index of the time slot, discarding slots earlier than the specified time slot. nK HARQ-ACK CB transmitted in time slot 3.

[0078] In other words, if the UE is in a time slot n Received trigger time slot nK In DCI format 2_1, which specifies retransmissions of PUCCH timings with certain priorities, the UE can choose not to retransmit earlier than the time slot. nK HARQ-ACK feedback for PDSCH transmitted in slot 3. In this way, the HARQ-ACK CB buffer can be minimized.

[0079] This aspect will be referenced below. Figure 5 Let me describe it further.

[0080] Figure 5 A schematic diagram is shown as an example of an implicit HARQ-ACK CB abandonment operation according to some implementation schemes.

[0081] As an example, Figure 5 Three CCs are shown: CC0, CC1, and CC2. PDSCH 530 and 540 are positioned in time slots CC0 and CC2, respectively. n-6 Transmission in the middle. Associated HARQ-ACK CB in the time slot. n-4 The data is transmitted on PUCCH 510. Additionally, PDSCH 550 and 560 are scheduled by the gNB to operate on CC2 and CC1 respectively in time slots. n-4 Transmission in the middle. Associated HARQ-ACK CB in the time slot. n-2 It is scheduled via PUCCH 520.

[0082] Assuming time slots n-4 The PUCCH 510 in the middle was successfully decoded on the gNB side, but the decoding failure occurred in the time slot. n-2 PUCCH 520 in this case. The time slot... n In DCI format 1_2, the PSI field can be set to indicate retransmission of PUCCH 520. Therefore, if PUCCH 510 and 520 have the same priority, the UE can discard PUCCH 510. This minimizes the HARQ-ACK CB buffer.

[0083] Back to Figure 1 In some implementations, various methods may be considered for setting the counter downlink allocation indicator (C-DAI) and total downlink allocation indicator (T-DAI) fields in DCI format 1_2 that triggers PUCCH timing retransmission when the type 2 HARQ-ACK CB is configured for the UE.

[0084] In some implementations, the C-DAI and T-DAI fields in the DCI that triggers the PUCCH timing retransmission are continuously accumulated based on the values ​​of the C-DAI and T-DAI fields of the last DCI associated with the retransmitted PUCCH timing.

[0085] This aspect will be referenced below. Figure 6 Let me describe it further.

[0086] Figure 6 A schematic diagram showing an example of C-DAI and T-DAI settings for DCI format 1_2 for type 2 HARQ-ACK CB / PUCCH timing retransmission is provided.

[0087] like Figure 6 As shown, assuming that the DCI is set appropriately during scheduling...<C-DAI, T-DAI> In the case of scheduling seven PDSCHs (e.g.) Figure 6 (The shaded box depicting the C-DAI and T-DAI numbers is shown below) and the associated HARQ-ACK CB is carried by the PUCCH 610. However, on the gNB side, the PUCCH 610 experiences a decoding failure.

[0088] Therefore, gNB is configured in DCI format 1_2 630.<C-DAI, T-DAI> =<8,9> (which counts C-DAI and T-DAI consecutively based on the last DCI format 1_2 640 associated with PUCCH610) to trigger a retransmission of PUCCH 610.

[0089] UE in<C-DAI,T-DAI> When set to <9,9>, <10,10>, <11,12>, and <12,12>, four additional PDSCH repetitions are scheduled. Therefore, a total of 12 HARQ-ACK bits are transmitted via PUCCH 620, including 7 bits for the retransmitted HARQ-ACK CB and 5 bits for the initial HARQ-ACK bit of the newly scheduled PDSCH.

[0090] In some implementations, the C-DAI and T-DAI fields of the DCI that triggers a PUCCH retransmission are reset and counted independently, regardless of the values ​​of the C-DAI and T-DAI fields in the last DCI of the retransmitted PUCCH.

[0091] In some implementations, an additional T-DAI field is added to the DCI that triggers the PUCCH retransmission to indicate the size of the retransmitted HARQ-ACK.

[0092] This is to ensure the reliability of the concatenated HARQ-ACKCB, which includes both the new HARQ-ACK bit and the retransmitted HARQ-ACK CB.

[0093] This aspect will be referenced below. Figure 7 Let me describe it further.

[0094] Figure 7 A schematic diagram of another example of the C-DAI and T-DAI settings for DCI format 1_2 for type 2 HARQ-ACK CB / PUCCH timing retransmission is shown.

[0095] like Figure 7 As shown, similar to Figure 6 Suppose that 7 PDSCHs and 5 PDSCHs are scheduled on three CCs (i.e., CC0, CC1, and CC2). Figure 7 (Indicated by the shaded boxes containing the C-DAI and T-DAI numbers). The associated HARQ-ACK CB is carried by PUCCH710 and PUCCH720 respectively.

[0096] Assume the gNB loses PUCCH 710. In this implementation, DCI format 1_2 730 can be transmitted by the gNB to trigger a retransmission of PUCCH 710, wherein in DCI format 1_2 730...<C-DAI,T-DAI> Perform a reset and recount, regardless of the last DCI format 1_2 740 associated with PUCCH 710.<C-DAI,T-DAI> What is the value of ?

[0097] Back to Figure 1 In some implementations, PUCCH timing retransmission can be associated with Type 1 HARQ-ACK CB. Several methods can be considered for Type 1 HARQ-ACK CB / PUCCH timing retransmission.

[0098] In some implementations, performing a PUCCH timing retransmission at step S204 may include: retransmitting the PUCCH timing retransmission in the time slot based on the set of K1 values ​​configured by RRC. n The HARQ-ACK CB for mid-retransmission is appended to the time slot.n At the end of the associated initial HARQ-ACK CB, where n Indicates the index of the time slot.

[0099] This aspect will be referenced below. Figure 8 Let me describe it further.

[0100] Figure 8 A schematic diagram is shown as an example of retransmission for Type 1 HARQ-ACK CB / PUCCH timing.

[0101] like Figure 8 As shown, by concatenating two HARQ-ACK CBs—one for the initial HARQ-ACK CB (18 bits) in PUCCH 830 and the other for the retransmitted HARQ-ACK CB (18 bits) in PUCCH 810—the size of the Type 1 HARQ-ACK CB used in PUCCH 830 will be doubled (i.e., as shown). Figure 8 As shown, this is increased to 36 bits. Here, as an example, assume three CCs.

[0102] Since the UE may lose DCI format 1_2 820 that triggers the retransmission of HARQ-ACK CB originally scheduled in PUCCH 810, the gNB may need to perform BD twice in PUCCH 830 for HARQ-ACK CB reception, assuming different conditions, i.e., whether DCI format 1_2 820 is detected and not detected at the UE.

[0103] This could lead to time slots. n+3 The size of the HARQ-ACK CB using PUCCH 830 has increased. For example... Figure 8 As shown, with time slots n-4 and n-1 The associated 6 HARQ-ACK bits are copied in the original HARQ-ACK CB and the retransmitted HARQ-ACK CB, resulting in an unnecessary overhead of 6 bits.

[0104] However, this problem can be solved by another implementation scheme as described below, which will refer to Figure 9 As shown.

[0105] In some implementations, performing a PUCCH timing retransmission at step S204 may include: excluding duplicate HARQ-ACK bits present in both the original HARQ-ACK CB and the retransmitted HARQ-ACK CB associated with the same DL slot index; and concatenating the original HARQ-ACK CB with the retransmitted HARQ-ACK CB.

[0106] In other words, in order to avoid such Figure 8 To avoid unnecessary overhead, the UE can eliminate the duplicated HARQ-ACK feedback between the original HARQ-ACK CB and the retransmitted HARQ-ACK CB, and then perform the concatenation operation of the original HARQ-ACK CB and the retransmitted HARQ-ACK CB.

[0107] This aspect will be referenced below. Figure 9 Let me describe it further.

[0108] Figure 9 A schematic diagram of another example of retransmission for Type 1 HARQ-ACK CB / PUCCH timing is shown.

[0109] like Figure 9 As shown, with Figure 8 Compared to the implementation shown, the UE will exclude time slots containing HARQ-ACK bits from both the original HARQ-ACK CB 930 and the retransmitted HARQ-ACK CB 910. n-4 and n-1 DCI format 1_2 920 triggers a retransmission of the HARQ-ACK CB originally scheduled in PUCCH 910.

[0110] Thus, time slots n+3 The concatenation size of the HARQ-ACK CB on the PUCCH is effectively reduced from 36 bits to 30 bits without any loss of HARQ-ACK information.

[0111] In some implementations, performing a PUCCH timing retransmission at step S204 may include transmitting the retransmitted HARQ-ACK CB on the PUCCH timing indicated by the DCI that triggered the PUCCH timing retransmission.

[0112] According to this disclosure, HARQ-ACK CB / PUCCH timed retransmission can efficiently achieve improved reliability performance.

[0113] Figure 10 A flowchart of an exemplary method for a base station according to some implementation schemes is shown. Figure 10 The method 1000 shown can be derived from, for example Figure 1 The base station 150 is used to implement this.

[0114] like Figure 10 As shown, the method 1000 for a base station may include the following steps: S1002, constructing downlink control information (DCI) for a UE that indicates when to retransmit the physical uplink control channel (PUCCH); and providing the DCI to the UE to trigger the retransmission of the PUCCH.

[0115] In some implementations, the DCI may include a PUCCH Slot Indicator (PSI) field, a Single Mixed Automatic Repeat Request (HARQ) Acknowledgment (HARQ-ACK) Request field, and a PUCCH Priority Indicator (PPI) field. (See reference...) Figures 2-4 The details about each field in the field are described, and therefore will not be repeated here.

[0116] In some implementations, PUCCH timing retransmission may be associated with a Type 2 HARQ-ACK CB, and the DCI includes a counter downlink allocation indicator (C-DAI) field and a total downlink allocation indicator (T-DAI) field.

[0117] In this case, in some implementations, at step S1004, providing the DCI for performing PUCCH timing retransmission may include: continuously accumulating the C-DAI field and the T-DAI field in the DCI that triggers the PUCCH timing retransmission based on the values ​​of the C-DAI field and the T-DAI field in the last DCI associated with the retransmitted PUCCH.

[0118] Alternatively, in some embodiments, at step S1004, providing the DCI for performing PUCCH timing retransmission may include: independently resetting and counting the C-DAI and T-DAI fields in the DCI that triggered the PUCCH timing retransmission, regardless of the values ​​of the C-DAI and T-DAI fields in the last DCI of the retransmitted PUCCH. In some embodiments, providing the DCI for performing PUCCH timing retransmission may further include: adding an additional T-DAI field to the DCI that triggered the PUCCH timing retransmission to indicate the size of the retransmitted HARQ-ACK.

[0119] Referenced Figures 6-7 Details about these aspects have been described, and therefore will not be repeated here.

[0120] Figure 11 A schematic diagram of an exemplary method for communication between a UE and a base station according to some implementation schemes is shown.

[0121] like Figure 11 As shown, base station 1110 can construct 1101 a DCI indicating the timing of physical uplink control channel (PUCCH) retransmission for UE, and can provide 1102 DCI for UE 1120 to trigger PUCCH timing retransmission.

[0122] When acquiring the DCI, the UE 1120 can perform retransmission of the 1103 PUCCH timing and the HARQ-ACK codebook associated with the PUCCH timing based on the received DCI.

[0123] According to another aspect of this disclosure, an apparatus for a user equipment (UE) is provided, the apparatus including one or more processors configured to perform the steps of the method for the UE as described above.

[0124] According to another aspect of this disclosure, an apparatus for a base station is provided, the apparatus including one or more processors configured to perform steps of a method for a base station.

[0125] According to another aspect of this disclosure, a computer-readable medium having a computer program stored thereon is provided, which, when executed by one or more processors, causes a device to perform the steps of the method described above.

[0126] According to another aspect of this disclosure, an apparatus for a communication device is provided, the apparatus including components for performing the steps of the method described above.

[0127] According to another aspect of this disclosure, a computer program product includes computer programs that, when executed by one or more processors, cause a device to perform the steps of the method described above.

[0128] According to this disclosure, it is possible to implement CBG-based operations for multi-PDSCH scheduling with minimal DL / UL signaling overhead.

[0129] Figure 12 Communication devices (e.g., UEs or base stations) according to some implementation schemes are shown. Figure 12 Exemplary components of device 1200 according to some embodiments are shown. In some embodiments, device 1200 may include at least application circuitry 1202, baseband circuitry 1204, radio frequency (RF) circuitry (shown as RF circuitry 1220), front-end module (FEM) circuitry (shown as FEM circuitry 1230), one or more antennas 1232, and power management circuitry (PMC) (shown as PMC 1234) coupled together as shown. Components of the illustrated device 1200 may be included in a UE or RAN node. In some embodiments, device 1200 may include fewer components (e.g., the RAN node may not utilize application circuitry 1202, but instead include a processor / controller to process IP data received from the EPC). In some embodiments, device 1200 may include additional components such as memory / storage devices, displays, cameras, sensors, or input / output (I / O) interfaces. In other embodiments, the components described below may be included in more than one device (e.g., the circuitry may be individually included in more than one device for a cloud-RAN (C-RAN) specific implementation).

[0130] Application circuitry 1202 may include one or more application processors. For example, application circuitry 1202 may include circuitry such as, but not limited to, one or more single-core or multi-core processors. The processor may include any combination of general-purpose processors and special-purpose processors (e.g., graphics processors, application processors, etc.). The processor may be coupled to or may include a memory / storage device and may be configured to execute instructions stored in the memory / storage device to enable various applications or operating systems to run on device 1200. In some embodiments, the processor of application circuitry 1202 may process IP data packets received from the EPC.

[0131] Baseband circuit 1204 may include circuitry such as, but not limited to, one or more single-core or multi-core processors. Baseband circuit 1204 may include one or more baseband processors or control logic components to process baseband signals received from the receive signal path of RF circuit 1220 and to generate baseband signals for the transmit signal path of RF circuit 1220. Baseband circuit 1204 may interact with application circuitry 1202 to generate and process baseband signals and control the operation of RF circuit 1220. For example, in some embodiments, baseband circuit 1204 may include a third-generation (3G) baseband processor (3G baseband processor 1206), a fourth-generation (4G) baseband processor (4G baseband processor 1208), a fifth-generation (5G) baseband processor (5G baseband processor 1210), or other existing, under development, or future generations of baseband processors 1212 (e.g., second-generation (2G), sixth-generation (6G), etc.). The baseband circuitry 1204 (e.g., one or more processors in a baseband processor) can handle various radio control functions capable of communicating with one or more radio networks via the RF circuitry 1220. In other embodiments, some or all of the functions of the illustrated baseband processor may be included in modules stored in memory 1218 and may be executed via a central processing unit (CPU 1214). Radio control functions may include, but are not limited to, signal modulation / demodulation, encoding / decoding, RF shifting, etc. In some embodiments, the modulation / demodulation circuitry of the baseband circuitry 1204 may include Fast Fourier Transform (FFT), precoding, or constellation mapping / demapping functions. In some embodiments, the encoding / decoding circuitry of the baseband circuitry 1204 may include convolution, tail-biting convolution, turbo, Viterbi, or low-density parity-check (LDPC) encoder / decoder functions. Implementations of the modulation / demodulation and encoder / decoder functions are not limited to these examples, and other suitable functions may be included in other embodiments.

[0132] In some embodiments, the baseband circuitry 1204 may include a digital signal processor (DSP), such as one or more audio DSPs 1216. The one or more audio DSPs 1216 may include elements for compression / decompression and echo cancellation, and in other embodiments may include other suitable processing elements. In some embodiments, components of the baseband circuitry may be suitably combined in a single chip, a single chipset, or disposed on the same circuit board. In some embodiments, some or all components of the baseband circuitry 1204 and the application circuitry 1202 may be implemented together, for example, on a system-on-a-chip (SoC).

[0133] In some implementations, baseband circuit 1204 can provide communication compatible with one or more radio technologies. For example, in some implementations, baseband circuit 1204 can support communication with the Evolved Universal Terrestrial Radio Access Network (EUTRAN) or other Wireless Metropolitan Area Networks (WMAN), Wireless Local Area Networks (WLAN), or Wireless Personal Area Networks (WPAN). Implementations in which baseband circuit 1204 is configured to support radio communication with more than one wireless protocol may be referred to as multimode baseband circuits.

[0134] RF circuit 1220 can communicate with a wireless network via a non-solid medium using modulated electromagnetic radiation. In various embodiments, RF circuit 1220 may include switches, filters, amplifiers, etc., to facilitate communication with the wireless network. RF circuit 1220 may include a receive signal path, which may include circuitry for down-converting an RF signal received from FEM circuit 1230 and providing a baseband signal to baseband circuit 1204. RF circuit 1220 may also include a transmit signal path, which may include circuitry for up-converting the baseband signal provided by baseband circuit 1204 and providing an RF output signal for transmission to FEM circuit 1230. In some embodiments, the receive signal path of RF circuit 1220 may include mixer circuit 1222, amplifier circuit 1224, and filter circuit 1226. In some embodiments, the transmit signal path of RF circuit 1220 may include filter circuit 1226 and mixer circuit 1222. RF circuitry 1220 may further include synthesizer circuitry 1228 for synthesizing frequencies used by mixer circuitry 1222 in the received signal path and / or transmitted signal path. In some embodiments, mixer circuitry 1222 in the received signal path may be configured to down-convert the RF signal received from FEM circuitry 1230 based on the synthesized frequency provided by synthesizer circuitry 1228. Amplifier circuitry 1224 may be configured to amplify the down-converted signal, and filter circuitry 1226 may be a low-pass filter (LPF) or band-pass filter (BPF) configured to remove unwanted signals from the down-converted signal to generate an output baseband signal. The output baseband signal may be provided to baseband circuitry 1204 for further processing. In some embodiments, although not required, the output baseband signal may be a zero-frequency baseband signal. In some embodiments, mixer circuitry 1222 in the received signal path may include a passive mixer, but the scope of the embodiments is not limited in this respect.

[0135] In some implementations, the mixer circuit 1222 of the transmit signal path can be configured to up-convert the input baseband signal based on the synthesized frequency provided by the synthesizer circuit 1228 to generate an RF output signal for the FEM circuit 1230. The baseband signal can be provided by the baseband circuit 1204 and can be filtered by the filter circuit 1226.

[0136] In some embodiments, the mixer circuit 1222 for the receive signal path and the mixer circuit 1222 for the transmit signal path may include two or more mixers and may be arranged for quadrature downconversion and upconversion, respectively. In some embodiments, the mixer circuit 1222 for the receive signal path and the mixer circuit 1222 for the transmit signal path may include two or more mixers and may be arranged for image rejection (e.g., Hartley image rejection). In some embodiments, the mixer circuit 1222 for the receive signal path and the mixer circuit 1222 may be arranged for direct downconversion and direct upconversion, respectively. In some embodiments, the mixer circuit 1222 for the receive signal path and the mixer circuit 1222 for the transmit signal path may be configured for superheterodyne operation.

[0137] In some embodiments, the output baseband signal and the input baseband signal may be analog baseband signals, although the scope of the embodiments is not limited in this respect. In some alternative embodiments, the output baseband signal and the input baseband signal may be digital baseband signals. In these alternative embodiments, the RF circuit 1220 may include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuitry, and the baseband circuit 1204 may include a digital baseband interface for communicating with the RF circuit 1220.

[0138] In some dual-mode implementations, separate radio IC circuits can be provided to process signals for each spectrum, but the scope of the implementation is not limited in this respect.

[0139] In some implementations, synthesizer circuit 1228 may be a fractional N synthesizer or a fractional N / N+1 synthesizer, but the scope of implementations is not limited in this respect, as other types of frequency synthesizers may also be suitable. For example, synthesizer circuit 1228 may be a Δ-Σ synthesizer, a frequency multiplier, or a synthesizer including a phase-locked loop with a frequency divider.

[0140] Synthesizer circuit 1228 can be configured to synthesize an output frequency based on the frequency input and the divider control input for use by mixer circuit 1222 of RF circuit 1220. In some embodiments, synthesizer circuit 1228 may be a fractional N / N+1 synthesizer.

[0141] In some implementations, the frequency input may be provided by a voltage-controlled oscillator (VCO), although this is not mandatory. The divider control input may be provided by the baseband circuit 1204 or the application circuit 1202 (such as an application processor) according to the desired output frequency. In some implementations, the divider control input (e.g., N) may be determined from a lookup table based on the channel indicated by the application circuit 1202.

[0142] The synthesizer circuit 1228 of the RF circuit 1220 may include a frequency divider, a delay-locked loop (DLL), a multiplexer, and a phase accumulator. In some embodiments, the frequency divider may be a dual-mode divider (DMD), and the phase accumulator may be a digital phase accumulator (DPA). In some embodiments, the DMD may be configured to divide the input signal by N or N+1 (e.g., based on carry) to provide a fractional division ratio. In some example embodiments, the DLL may include a cascaded, tunable delay element, a phase detector, a charge pump, and a set of D-type flip-flops. In these embodiments, the delay elements may be configured to divide the VCO cycle into Nd equal phase groups, where Nd is the number of delay elements in the delay line. Thus, the DLL provides negative feedback to help ensure that the total delay through the delay line is one VCO cycle.

[0143] In some embodiments, the synthesizer circuit 1228 may be configured to generate a carrier frequency as the output frequency, while in other embodiments, the output frequency may be a multiple of the carrier frequency (e.g., twice the carrier frequency, four times the carrier frequency) and used in conjunction with quadrature generator and frequency divider circuitry to generate multiple signals having multiple different phases relative to each other at the carrier frequency. In some embodiments, the output frequency may be the LO frequency (f LO In some implementations, the RF circuit 1220 may include an IQ / polarity converter.

[0144] FEM circuit 1230 may include a receive signal path, which may include circuitry configured to operate on RF signals received from one or more antennas 1232, amplify the received signals, and provide an amplified version of the received signals to RF circuit 1220 for further processing. FEM circuit 1230 may also include a transmit signal path, which may include circuitry configured to amplify transmit signals provided by RF circuit 1220 for transmission by one or more of the one or more antennas 1232. In various embodiments, amplification via the transmit or receive signal path may be performed only in RF circuit 1220, only in FEM circuit 1230, or in both RF circuit 1220 and FEM circuit 1230.

[0145] In some embodiments, FEM circuit 1230 may include a TX / RX switch to switch between transmit and receive mode operation. FEM circuit 1230 may include a receive signal path and a transmit signal path. The receive signal path of FEM circuit 1230 may include an LNA to amplify the received RF signal and provide the amplified received RF signal as an output (e.g., to RF circuit 1220). The transmit signal path of FEM circuit 1230 may include a power amplifier (PA) to amplify the input RF signal (e.g., provided by RF circuit 1220), and one or more filters to generate an RF signal for subsequent transmission (e.g., through one or more antennas in the one or more antennas 1232).

[0146] In some implementations, the PMC 1234 can manage the power supplied to the baseband circuitry 1204. Specifically, the PMC 1234 can control power selection, voltage scaling, battery charging, or DC-DC conversion. The PMC 1234 is typically included when the device 1200 is capable of being battery powered, for example, when the device 1200 is included in an EGE. The PMC 1234 can improve power conversion efficiency while providing the desired implementation size and thermal characteristics.

[0147] Figure 12 PMC 1234 is shown coupled only to baseband circuit 1204. However, in other embodiments, PMC 1234 may additionally or alternatively be coupled to other components, such as, but not limited to, application circuit 1202, RF circuit 1220, or FEM circuit 1230, and perform similar power management operations for these components.

[0148] In some implementations, PMC 1234 may control or otherwise become part of various power-saving mechanisms of device 1200. For example, if device 1200 is in an RRC connected state, and in this state the device is still connected to the RAN node because the device expects to receive communication soon, the device may enter a state called discontinuous receive mode (DRX) after a period of inactivity. During this state, device 1200 may be powered down for short intervals, thereby saving power.

[0149] If there is no data traffic activity during the extended period, device 1200 can transition to the RRC Idle state, in which the device disconnects from the network and does not perform operations such as channel quality feedback or handover. Device 1200 enters a very low power state and performs paging, in which the device periodically wakes up again to listen to the network, and then powers off again. Device 1200 cannot receive data in this state, and in order to receive data, the device must transition back to the RRC Connected state.

[0150] An additional power-saving mode allows the device to be unavailable from the network for periods exceeding the paging interval (ranging from seconds to hours). During this time, the device is completely unconnected to the network and can be completely powered off. Any data sent during this period will incur significant latency, which is assumed to be acceptable.

[0151] The processors of application circuit 1202 and baseband circuit 1204 are elements that can be used to execute one or more instances of the protocol stack. For example, the processor of baseband circuit 1204 can be used alone or in combination to execute layer 3, layer 2, or layer 1 functions, while the processor of application circuit 1202 can utilize data received from these layers (e.g., packet data) and further execute layer 4 functions (e.g., Transport Communication Protocol (TCP) and User Datagram Protocol (UDP) layers). As mentioned herein, layer 3 may include the Radio Resource Control (RRC) layer, which will be described in further detail below. As mentioned herein, layer 2 may include the Media Access Control (MAC) layer, the Radio Link Control (RLC) layer, and the Packet Data Convergence Protocol (PDCP) layer, which will be described in further detail below. As mentioned herein, layer 1 may include the physical (PHY) layer of the UE / RAN node, which will be described in further detail below.

[0152] Figure 13 An exemplary interface 1300 of a baseband circuit according to some embodiments is shown. As discussed above, Figure 12 The baseband circuit 1204 may include a 3G baseband processor 1206, a 4G baseband processor 1208, a 5G baseband processor 1210, other baseband processors 1212, a CPU 1214, and a memory 1218 used by the processors. As shown, each processor may include a memory interface 1302 for sending / receiving data to / from the memory 1218.

[0153] Baseband circuit 1204 may further include: one or more interfaces for communicatively coupling to other circuits / devices, such as memory interface 1304 (e.g., an interface for sending / receiving data to / from a memory external to baseband circuit 1204); application circuit interface 1306 (e.g., for sending / receiving data to / from a memory external to baseband circuit 1204); and application circuit interface 1306 (e.g., for sending / receiving data to / from a memory external to baseband circuit 1204). Figure 12 Application circuit 1202 is an interface for sending / receiving data; RF circuit interface 1308 (e.g., for sending / receiving data to / from...) Figure 12 RF circuit 1220 is an interface for transmitting / receiving data; wireless hardware connection interface 1310 (e.g., for sending / receiving data to / from near field communication (NFC) components, Bluetooth). ® Components (e.g., Bluetooth) ® Low power consumption, Wi-Fi ®Interface for sending / receiving data to / from components and other communication components); and power management interface 1312 (e.g., an interface for sending / receiving power or control signals to / from PMC 1234).

[0154] Figure 14 This is a block diagram illustrating a component 1400, according to some exemplary embodiments, capable of reading instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and capable of executing any or more of the methods discussed herein. Specifically, Figure 14 A schematic representation of hardware resources 1402 is shown, including one or more processors 1412 (or processor cores), one or more memory / storage devices 1418, and one or more communication resources 1420, each of which is communicatively coupled via bus 1422. For implementations utilizing node virtualization (e.g., NFV), an executable hypervisor 1404 provides an execution environment for enabling one or more network slices / subslices to utilize hardware resources 1402.

[0155] Processor 1412 (e.g., a central processing unit (CPU), a reduced instruction set computing (RISC) processor, a complex instruction set computing (CISC) processor, a graphics processing unit (GPU), a digital signal processor (DSP) (such as a baseband processor), an application-specific integrated circuit (ASIC), a radio frequency integrated circuit (RFIC), another processor, or any suitable combination thereof) may include, for example, processor 1414 and processor 1416.

[0156] The memory / storage device 1418 may include main memory, disk storage, or any suitable combination thereof. The memory / storage device 1418 may include, but is not limited to, any type of volatile or non-volatile memory, such as dynamic random access memory (DRAM), static random access memory (SRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, solid-state storage devices, etc.

[0157] Communication resource 1420 may include interconnect or network interface components or other suitable devices for communicating with one or more peripheral devices 1406 or one or more databases 1408 via network 1410. For example, communication resource 1420 may include wired communication components (e.g., for coupling via Universal Serial Bus (USB), cellular communication components, NFC components, Bluetooth, etc. ® Components (e.g., Bluetooth) ® Low power consumption, Wi-Fi ® Components and other communication components.

[0158] Instructions 1424 may include software, programs, applications, applets, or other executable code for causing at least any one of the processors 1412 to perform any or more of the methods discussed herein. Instructions 1424 may reside wholly or partially within at least one of the processor 1412 (e.g., within the processor's cache), memory / storage device 1418, or any suitable combination thereof. Furthermore, any portion of instructions 1424 may be transferred to hardware resource 1402 from any combination of peripheral device 1406 or database 1408. Thus, the memory of processor 1412, memory / storage device 1418, peripheral device 1406, and database 1408 are examples of computer-readable and machine-readable media.

[0159] For one or more embodiments, at least one of the components shown in one or more of the foregoing figures may be configured to perform one or more operations, techniques, processes, and / or methods as described in the Examples section below. For example, the baseband circuitry described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the examples below. As another example, circuitry associated with the UE, base station, network element, etc., described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the examples shown in the Examples section below.

[0160] Figure 15 The architecture of a system 1500 for a network according to some implementations is shown. The following description is provided for an exemplary system 1500 operating in combination with LTE system standards and 5G or NR system standards provided by 3GPP technical specifications. However, the exemplary implementations are not limited in this respect, and the implementations can be applied to other networks that benefit from the principles described herein, such as future 3GPP systems (e.g., sixth generation (6G) systems, etc.).

[0161] like Figure 15 As shown, system 1500 includes UE 1501a and UE 1501b (collectively referred to as "UE 1501"). UE 1501a and / or UE 1501b may correspond to the aforementioned UE.

[0162] In this example, UE 1501 is shown as a smartphone (e.g., a handheld touchscreen mobile computing device that can connect to one or more cellular networks), but may also include any mobile or non-mobile computing device, such as consumer electronics devices, mobile phones, smartphones, feature phones, tablets, wearable computing devices, personal digital assistants (PDAs), pagers, wireless handheld devices, desktop computers, laptops, in-vehicle infotainment (IVI), in-vehicle entertainment (ICE) devices, instrument cluster (IC), head-up display (HUD) devices, onboard diagnostic (OBD) devices, dashtop mobile equipment (DME), mobile data terminal (MDT), electronic engine management system (EEMS), electronic / engine control unit (ECU), electronic / engine control module (ECM), embedded systems, microcontrollers, control modules, engine management system (EMS), connected or “smart” appliances, MTC devices, M2M, IoT devices, etc.

[0163] In some implementations, any of UEs 1501 can be an IoT UE, which may include a network access layer designed to utilize low-power IoT applications with short-lived UE connections. The IoT UE may utilize technologies such as M2M or MTC to exchange data with an MTC server or device via PLMN, ProSe, or D2D communication, sensor networks, or IoT networks. M2M or MTC data exchange may be machine-initiated data exchange. The IoT network describes interconnected IoT UEs, which may include uniquely identifiable embedded computing devices (within the Internet infrastructure) with short-lived connections. The IoT UE may execute background applications (e.g., keeping track of activity messages, status updates, etc.) to facilitate connectivity within the IoT network.

[0164] UE 1501 can be configured to connect to RAN 1510, for example, communicatively coupled. In implementations, RAN 1510 can be an NG RAN or 5G RAN, E-UTRAN, or a legacy RAN such as UTRAN or GERAN. As used herein, the term "NGRAN," etc., can refer to RAN 1510 operating in NR or 5G system 1500, while the term "E-UTRAN," etc., can refer to RAN 1510 operating in LTE or 4G system 1500. UE 1501 utilizes connections (or channels) 1503 and 1504, each connection including a physical communication interface or layer (discussed in further detail below).

[0165] In this example, connections 1503 and 1504 are shown as air interfaces for communication coupling and are compatible with cellular communication protocols such as GSM, CDMA, PTT, POC, UMTS, 3GPP LTE, 5G, NR, and / or any other communication protocols discussed herein. In an implementation, UE 1501 can directly exchange communication data via ProSe interface 1505. ProSe interface 1505 may also be referred to as SL interface 1505 and may include one or more logical channels, including but not limited to PSCCH, PSSCH, PSDCH, and PSBCH.

[0166] UE 1501b is shown configured to access AP 1506 (also referred to as "WLAN Node 1506", "WLAN 1506", "WLAN Terminal 1506", "WT 1506", etc.) via connection 1507. Connection 1507 may include a local wireless connection, such as a connection consistent with any IEEE 802.11 protocol, where AP 1506 will include Wi-Fi. ® Router. In this embodiment, AP 1506 is shown as a core network connected to the Internet but not to a wireless system (described in further detail below). In various implementations, UE 1501b, RAN 1510, and AP 1506 can be configured to utilize LWA operation and / or LWIP operation. LWA operation may involve UE 1501b in RRC CONNECTED being configured by RAN nodes 1511a-b to utilize the radio resources of LTE and WLAN. LWIP operation may involve UE 1501b using WLAN radio resources (e.g., connection 1507) via IPsec protocol tunneling to authenticate and encrypt packets (e.g., IP packets) transmitted through connection 1507. IPsec tunneling may include encapsulating the entire original IP packet and adding a new packet header to protect the original header of the IP packet.

[0167] RAN 1510 may include one or more AN nodes or RAN nodes 1511a and 1511b (collectively referred to as "multiple RAN nodes 1511" or "RAN node 1511") that enable connectivity between 1503 and 1504. As used herein, the terms "access node," "access point," etc., can describe equipment that provides radio baseband functionality for data and / or voice connections between the network and one or more users. These access nodes may be referred to as BS, gNB, RAN node, eNB, NodeB, RSU, TRxP, or TRP, etc., and may include ground stations (e.g., terrestrial access points) or satellite stations that provide coverage within a geographic area (e.g., a cell). As used herein, the terms "NG RAN node," etc., can refer to RAN node 1511 (e.g., gNB) operating in NR or 5G system 1500, while the terms "E-UT RAN node," etc., can refer to RAN node 1511 (e.g., eNB) operating in LTE or 4G system 1500. According to various implementation schemes, RAN node 1511 can be implemented as one or more of dedicated physical devices such as macro cell base stations and / or low-power (LP) base stations for providing smaller coverage areas, smaller user capacity, or higher bandwidth compared to macro cells.

[0168] In some implementations, all or part of RAN node 1511 may be implemented as one or more software entities running on a server computer as part of a virtual network that may be referred to as CRAN and / or Virtual Baseband Unit Pool (vBBUP). In these implementations, CRAN or vBBUP may implement RAN function partitioning, such as PDCP partitioning, where the RRC and PDCP layers are operated by CRAN / vBBUP, while other L2 protocol entities are operated by individual RAN nodes 1511; MAC / PHY partitioning, where the RRC, PDCP, RLC, and MAC layers are operated by CRAN / vBBUP, and the PHY layer is operated by individual RAN nodes 1511; or "lower PHY" partitioning, where the upper portion of the RRC, PDCP, RLC, MAC, and PHY layers is operated by CRAN / vBBUP, while the lower portion of the PHY layer is operated by individual RAN nodes 1511. This virtualization framework allows the idle processor cores of RAN node 1511 to execute other virtualized applications. In some specific implementations, a single RAN node 1511 may represent a virtual network via a separate FI interface (…). Figure 15(Not shown) A separate gNB-DU connected to the gNB-CU. In these specific implementations, the gNB-DU may include one or more remote radio heads or RFEMs, and the gNB-CU may be operated by a server (not shown) located in RAN 1510 or by a server pool in a manner similar to CRAN / vBBUP. In addition or alternatively, one or more RAN nodes in RAN node 1511 may be next-generation eNBs (ng-eNBs), which are RAN nodes that provide E-UTRA user plane and control plane protocol terminals to UE 1501 and are connected to the 5G core (5GC) via the NG interface.

[0169] In a V2X scenario, one or more RAN nodes in RAN node 1511 can be RSUs or act as RSUs. The term "roadside unit" or "RSU" can refer to any traffic infrastructure entity used for V2X communication. An RSU can be implemented in or by a suitable RAN node or a stationary (or relatively stationary) UE, wherein an RSU implemented in or by a UE can be referred to as a "UE-type RSU," an RSU implemented in or by an eNB can be referred to as an "eNB-type RSU," an RSU implemented in or by a gNB can be referred to as a "gNB-type RSU," and so on. In one example, an RSU is a computing device coupled to radio frequency circuitry located on the roadside, which provides connectivity support to a passing vehicle UE 1501 (vUE1501). An RSU may also include internal data storage circuitry for storing intersection map geometry, traffic statistics, media, and applications / software for sensing and controlling ongoing vehicle and pedestrian traffic. The RSU may operate on the 5.9 GHz Direct Near Range Communication (DSRC) band to provide extremely low-latency communication required for high-speed events, such as collision avoidance and traffic warnings. Alternatively, the RSU may operate on the cellular V2X band to provide the aforementioned low-latency communication as well as other cellular communication services. Alternatively, the RSU may operate as a Wi-Fi hotspot (2.4 GHz band) and / or provide connectivity to one or more cellular networks to provide uplink and downlink communication. Some or all of the computing device and the RSU's radio frequency circuitry may be packaged in a weather-resistant package suitable for outdoor installation and may include a network interface controller to provide wired connectivity (e.g., Ethernet) to traffic signal controllers and / or backhaul networks.

[0170] Any of the RAN nodes 1511 can serve as the endpoint of the air interface protocol and can be the first point of contact for UE 1501. In some implementations, any of the RAN nodes 1511 can perform various logical functions of RAN 1510, including but not limited to Radio Network Controller (RNC) functions such as radio bearer management, uplink and downlink dynamic radio resource management and data packet scheduling, and mobility management.

[0171] In the implementation, UE 1501 may be configured to communicate with each other or with any of the RAN nodes 1511 on a multi-carrier communication channel using OFDM communication signals according to various communication technologies, such as, but not limited to, OFDMA communication technology (e.g., for downlink communication) or SC-FDMA communication technology (e.g., for uplink and ProSe or sidelink communication), although the scope of the implementation is not limited in this respect. The OFDM signal may include multiple orthogonal subcarriers.

[0172] In some implementations, the downlink resource grid can be used for downlink transmissions from any node in RAN node 1511 to UE 1501, while uplink transmissions can utilize similar techniques. The grid can be a time-frequency grid, referred to as a resource grid or time-frequency resource grid, which represents the physical resources in the downlink within each time slot. This time-frequency plane representation is common practice for OFDM systems, making radio resource allocation intuitive. Each column and row of the resource grid corresponds to an OFDM symbol and an OFDM subcarrier, respectively. The duration of the resource grid in the time domain corresponds to a time slot in a radio frame. The smallest time-frequency unit in the resource grid is represented as a resource element. Each resource grid comprises multiple resource blocks that describe the mapping of certain physical channels to resource elements. Each resource block comprises a set of resource elements; in the frequency domain, this can represent the minimum amount of resources currently available for allocation. Such resource blocks are used to transmit several different physical downlink channels.

[0173] According to various implementations, UE 1501 and RAN node 1511 transmit data (e.g., transmit and receive data) through licensed media (also referred to as “licensed spectrum” and / or “licensed band”) and unlicensed shared media (also referred to as “unlicensed spectrum” and / or “unlicensed band”). Licensed spectrum may include channels operating in the frequency range of approximately 400 MHz to approximately 3.8 GHz, while unlicensed spectrum may include a 5 GHz band.

[0174] To operate in unlicensed spectrum, UE 1501 and RAN node 1511 can use LAA, eLAA, and / or feLAA mechanisms. In these specific implementations, UE 1501 and RAN node 1511 can perform one or more known medium sensing and / or carrier sensing operations to determine whether one or more channels in the unlicensed spectrum are unavailable or otherwise occupied before transmission in the unlicensed spectrum. Medium / carrier sensing operations can be performed according to the Listen-After-Speak (LBT) protocol.

[0175] LBT is a mechanism that equipment (e.g., UE 1501, RAN node 1511, etc.) uses to sense a medium (e.g., a channel or carrier frequency) and transmit when that medium is sensed to be idle (or when a specific channel in that medium is sensed to be unoccupied). Medium sensing operations may include CCA, which utilizes at least ED to determine the presence of other signals on the channel in order to determine whether the channel is occupied or idle. This LBT mechanism allows cellular / LAA networks to coexist with existing systems in unlicensed spectrum and with other LAA networks. ED may include sensing RF energy in the intended transmission band over a period of time and comparing the sensed RF energy with predefined or configured thresholds.

[0176] Typically, existing systems in the 5GHz band are WLANs based on IEEE 802.11 technology. WLANs employ a contention-based channel access mechanism called CSMA / CA. Here, when a WLAN node (e.g., a mobile station (MS) such as UE 1501, AP 1506, etc.) intends to transmit, the WLAN node can first perform CCA before transmitting. Additionally, in cases where more than one WLAN node senses the channel as idle and transmits simultaneously, a backoff mechanism is used to avoid collisions. This backoff mechanism can be a counter randomly introduced within the CWS, which increases exponentially upon collision and resets to a minimum value upon successful transmission. The LBT mechanism designed for LAA is somewhat similar to WLAN's CSMA / CA. In some specific implementations, the LBT process for DL ​​or UL transmission bursts (including PDSCH or PUSCH transmissions) can have a variable-length LAA contention window between the X and Y ECCA time slots, where X and Y are the minimum and maximum values ​​of the LAA's CWS. In one example, the minimum CWS for LAA transmission can be 9 microseconds (µs); however, the size of the CWS and MCOT (e.g., transmission burst) can be based on government regulatory requirements.

[0177] The LAA mechanism is built upon the CA technology of LTE-Advanced systems. In CA, each aggregated carrier is called a CC. A CC can have a bandwidth of 1.4, 3, 5, 10, 15, or 20 MHz, and a maximum of five CCs can be aggregated, thus the maximum aggregated bandwidth is 100 MHz. In FDD systems, the number of aggregated carriers can differ for DL ​​and UL, where the number of UL CCs is equal to or less than the number of DL component carriers. In some cases, individual CCs can have different bandwidths than the other CCs. In TDD systems, the number of CCs and the bandwidth of each CC are usually the same for DL ​​and UL.

[0178] The CA also includes individual serving cells to provide individual CCs. The coverage of serving cells can differ, for example, because CCs on different frequency bands will experience different path losses. The primary serving cell, or PCell, provides PCCs for both UL and DL and handles activities related to RRC and NAS. Other serving cells are called SCells, and each SCell provides individual SCCs for both UL and DL. SCCs can be added and removed as needed, while changing the PCC may require UE 1501 to undergo a handover. In LAA, eLAA, and feLAA, some or all of the SCells can operate in unlicensed spectrum (referred to as "LAA SCells"), and LAA SCells are assisted by PCells operating in licensed spectrum. When a UE is configured to have more than one LAA SCell, the UE can receive UL grants on the configured LAA SCells, indicating different PUSCH start positions within the same subframe.

[0179] The PDSCH carries user data and higher-layer signaling to UE 1501. Among other information, the PDCCH carries information about the transmission format and resource allocation related to the PDSCH channel. It also informs UE 1501 about the transmission format, resource allocation, and HARQ information related to the uplink shared channel. Typically, downlink scheduling (allocating control and shared channel resource blocks to UE 1501b within the cell) can be performed on any RAN node in RAN node 1511 based on channel quality information fed back from any UE in UE 1501. Downlink resource allocation information can be transmitted on the PDCCH used for (e.g., allocated to) each UE in UE 1501.

[0180] The PDCCH uses Control Channel Elements (CCEs) to transmit control information. Before being mapped to resource elements, the complex-valued symbols of the PDCCH can first be organized into quadruplets, which can then be arranged using a sub-block interleaver for rate matching. One or more of these CCEs can be used to transmit each PDCCH, where each CCE can correspond to six resource element groups (REGs). Each REG includes one resource block within an OFDM symbol. Depending on the size of the downlink control information (DCI) and channel conditions, one or more CCEs can be used to transmit the PDCCH. Different numbers of CCEs (e.g., aggregation levels, L=1, 2, 4, 8, or 16) can be used for PDCCH transmission.

[0181] Some implementations may use the concept of resource allocation for control channel information, which is an extension of the above concept. For example, some implementations may utilize EPDCCH, which uses PDSCH resources for control information transmission. One or more ECCEs may be used to transmit EPDCCH. Similarly, each ECCE may correspond to a set of nine, each consisting of four physical resource elements, called EREG. In some cases, an ECCE may have a different number of EREGs.

[0182] RAN nodes 1511 can be configured to communicate with each other via interface 1512. In implementations where system 1500 is an LTE system (e.g., when CN 1520 is an EPC), interface 1512 can be an X2 interface 1512. The X2 interface can be defined between two or more RAN nodes 1511 connected to EPC 1520 (e.g., two or more eNBs, etc.), and / or between two eNBs connected to EPC 1520. In some specific implementations, the X2 interface may include an X2 user plane interface (X2-U) and an X2 control plane interface (X2-C). X2-U can provide flow control mechanisms for user packets transmitted via the X2 interface and can be used to transmit information about the delivery of user data between eNBs. For example, X2-U can provide specific sequence number information about user data transmitted from MeNB to SeNB; information about the successful in-order delivery of PDCP PDUs from SeNB to UE 1501 for user data; information about PDCP PDUs not delivered to UE 1501; information about the current minimum expected buffer size at SeNB for transmitting user data to the UE; and so on. X2-C can provide in-LTE access mobility functions, including context transfer from source eNB to destination eNB, user plane transmission control, etc.; load management functions; and inter-cell interference coordination functions. In implementations where system 1500 is a 5G or NR system (e.g., when CN 1520 is 5GC), interface 1512 can be Xn interface 1512. The Xn interface is defined between two or more RAN nodes 1511 (e.g., two or more gNBs, etc.) connected to 5GC 1520, between a RAN node 1511 (e.g., gNB) connected to 5GC 1520 and an eNB, and / or between two eNBs connected to 5GC 1520. In some implementations, the Xn interface may include an Xn user plane (Xn-U) interface and an Xn control plane (Xn-C) interface. Xn-U provides non-guaranteed delivery of user plane PDUs and supports / provides data forwarding and flow control functions. Xn-C provides management and error handling functions for managing the functionality of the Xn-C interface; mobility support for UE 1501 in connected modes (e.g., CM-CONNECTED) includes functions for managing UE mobility in connected modes between one or more RAN nodes 1511. Mobility support may include context transfer from the old (source) serving RAN node 1511 to the new (destination) serving RAN node 1511; and control of user plane tunnels between the old (source) serving RAN node 1511 and the new (destination) serving RAN node 1511. The Xn-U protocol stack may include a transport network layer built on top of the Internet Protocol (IP) transport layer, and a GTP-U layer on top of the UDP and / or IP layers for carrying user plane PDUs.The Xn-C protocol stack may include an application layer signaling protocol (referred to as the Xn Application Protocol (Xn-AP)) and a transport network layer built on top of SCTP. SCTP sits on top of the IP layer and provides guaranteed delivery of application layer messages. In the transport IP layer, point-to-point transport is used to deliver signaling PDUs. In other implementations, the Xn-U protocol stack and / or Xn-C protocol stack may be the same as or similar to the user plane and / or control plane protocol stacks shown and described herein.

[0183] RAN 1510 is shown communicatively coupled to the core network—in this embodiment, communicatively coupled to the core network (CN) 1520. CN 1520 may include multiple network elements 1522 configured to provide various data and telecommunications services to customers / subscribers (e.g., users of UE 1501) connected to CN 1520 via RAN 1510. Components of CN 1520 may be implemented in a single physical node or separate physical nodes, including components for reading and executing instructions from machine-readable or computer-readable media (e.g., non-transitory machine-readable storage media). In some embodiments, NFV may be used to virtualize any or all of the aforementioned network node functions via executable instructions stored in one or more computer-readable storage media (described in further detail below). A logical instance of CN 1520 may be referred to as a network slice, and a logical instance of a portion of CN 1520 may be referred to as a network subslice. NFV architectures and infrastructure may be used to virtualize one or more network functions onto physical resources comprising a combination of industry-standard server hardware, storage hardware, or switches (or alternatively, performed by proprietary hardware). In other words, an NFV system can be used to perform a virtual or reconfigurable concrete implementation of one or more EPC components / functions.

[0184] Generally, application server 1530 can be a component that provides IP bearer resources for applications to use with the core network (e.g., UMTS PS domain, LTE PS data service, etc.). Application server 1530 can also be configured to support one or more communication services for UE 1501 via EPC 1520 (e.g., VoIP sessions, PTT sessions, group communication sessions, social networking services, etc.).

[0185] In the implementation, CN 1520 may be a 5GC (referred to as "5GC 1520", etc.), and RAN 1510 may be connected to CN 1520 via NG interface 1513. In the implementation, NG interface 1513 may be divided into two parts: NG User Plane (NG-U) interface 1514, which carries traffic data between RAN node 1511 and UPF; and SI Control Plane (NG-C) interface 1515, which is the signaling interface between RAN node 1511 and AMF.

[0186] In one implementation, CN 1520 may be a 5G CN (referred to as "5GC 1520", etc.), while in other implementations, CN 1520 may be an EPC. When CN 1520 is an EPC (referred to as "EPC 1520", etc.), RAN 1510 may be connected to CN 1520 via SI interface 1513. In another implementation, SI interface 1513 may be divided into two parts: SI user plane (SI-U) interface 1514, which carries traffic data between RAN node 1511 and S-GW; and SI-MME interface 1515, which is the signaling interface between RAN node 1511 and MME.

[0187] Additional Examples

[0188] For one or more embodiments, at least one of the components shown in one or more of the foregoing figures may be configured to perform one or more operations, techniques, processes, and / or methods as described in the Examples section below. For example, the baseband circuitry described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the examples below. As another example, circuitry associated with the UE, base station, network element, etc., described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the examples shown in the Examples section below.

[0189] The following examples relate to other implementation schemes.

[0190] Example 1 is a method for a user equipment (UE), the method comprising: receiving downlink control information (DCI) indicating a retransmission of a physical uplink control channel (PUCCH) timing; and performing a retransmission of the PUCCH timing and a HARQ-ACK codebook associated with the PUCCH timing based on the received DCI.

[0191] Example 2 is the method described in Example 1, wherein the DCI includes a PUCCH slot indicator (PSI) field, a single hybrid automatic repeat request (HARQ) acknowledgment (HARQ-ACK) request field, and a PUCCH priority indicator (PPI) field.

[0192] Example 3 is based on the method described in Example 2, wherein the value of the PSI field is mapped one-to-one to parameters configured by Radio Resource Control (RRC) signaling. K The value of 3.

[0193] Example 4 is based on the method described in Example 3, wherein the bit width of the PSI field is determined to be... ,in I These are configured by RRC signaling. K 3. The number of parameter values.

[0194] Example 5 is the method according to Example 3, wherein multiple PSI fields are included in the DCI to support retransmission at multiple PUCCH times triggered by the DCI.

[0195] Example 6 is the method according to Example 2, wherein the PSI field is formed as follows: I Bitmap, in which I express K The number of 3 parameter values, and the I Each bit in the bitmap corresponds to K One of the three parameter values.

[0196] Example 7 is the method according to any one of Examples 3 to 6, wherein performing the PUCCH timing retransmission based on the DCI includes: in the time slot n When the DCI that triggers the PUCCH timing retransmission is detected, among which n This indicates the index of the time slot, within the time slot. nK 3. Retransmission of the PUCCH timing indicated by the DCI and the corresponding HARQ-ACK codebook (CB) transmitted on that PUCCH timing, wherein K 3. As indicated by the DCI.

[0197] Example 8 is a method according to any one of Examples 3 to 6, wherein performing the PUCCH timing retransmission based on the DCI includes: performing the PUCCH timing retransmission in the target PUCCH timing, wherein the initial PUCCH timing for the PUCCH timing retransmission has a corresponding time interval to the target PUCCH timing. K The time slot interval with a value of 3.

[0198] Example 9 is the method according to Example 2, wherein the single HARQ-ACK request field is set to 1 bit and is used to trigger the retransmission of the HARQ-ACK CB carried at the retransmitted PUCCH timing indicated by the DCI.

[0199] Example 10 is the method according to Example 2, wherein the PPI field is set to 1 bit.

[0200] Example 11 is the method according to Example 2, wherein the PPI field is configured to indicate the priority of the retransmitted PUCCH.

[0201] Example 12 is the method according to Example 1, wherein the priority of the retransmitted PUCCH timing is appended to a predefined position of the retransmitted HARQ-ACK payload.

[0202] Example 13 is the method according to any one of Examples 3 to 6, wherein performing the PUCCH timing retransmission based on the DCI includes: in the time slot n The indication detected in the time slot nK When the PUCCH timing retransmission is triggered in step 3, among which... n Indicates the index of this time slot, discarding slots earlier than this time slot. nK HARQ-ACK CB transmitted in time slot 3.

[0203] Example 14 is the method according to Example 1, wherein the PUCCH timing retransmission is associated with type 2 HARQ-ACKCB, and the DCI includes a counter downlink allocation indicator (C-DAI) field and a total downlink allocation indicator (T-DAI) field.

[0204] Example 15 is the method according to Example 14, wherein the C-DAI field and the T-DAI field in the DCI that triggers the PUCCH timing retransmission are continuously accumulated based on the values ​​of the C-DAI field and the T-DAI field in the last DCI associated with the retransmitted PUCCH timing.

[0205] Example 16 is the method according to Example 14, wherein the C-DAI field and the T-DAI field in the DCI that triggers the PUCCH retransmission are independently reset and counted, regardless of the values ​​of the C-DAI field and the T-DAI field in the last DCI of the retransmitted PUCCH.

[0206] Example 17 is the method according to Example 16, wherein an additional T-DAI field is added to the DCI that triggers the PUCCH retransmission to indicate the size of the retransmitted HARQ-ACK.

[0207] Example 18 is the method according to Example 1, wherein the PUCCH timing retransmission is associated with type 1 HARQ-ACKCB.

[0208] Example 19 is the method according to Example 18, wherein performing the PUCCH timing retransmission includes: according to the set of K1 values ​​configured by RRC, in the time slot n The HARQ-ACK CB for mid-retransmission is appended to this time slot. n At the end of the associated initial HARQ-ACK CB, where n This indicates the index of the time slot.

[0209] Example 20 is the method according to Example 18, wherein performing the PUCCH timing retransmission includes: excluding duplicate HARQ-ACK bits present in both the original HARQ-ACK CB and the retransmitted HARQ-ACK CB associated with the same DL slot index; and concatenating the original HARQ-ACK CB with the retransmitted HARQ-ACK CB.

[0210] Example 21 is the method described in Example 18, wherein performing the PUCCH timing retransmission includes transmitting the retransmitted HARQ-ACK CB on the PUCCH timing indicated by the DCI that triggered the PUCCH timing retransmission.

[0211] Example 22 is a method for a base station, the method comprising: constructing downlink control information (DCI) for the UE indicating when to retransmit the Physical Uplink Control Channel (PUCCH); and providing the DCI for the UE to trigger the PUCCH retransmission.

[0212] Example 23 is the method according to Example 22, wherein the DCI includes a PUCCH slot indicator (PSI) field, a single hybrid automatic repeat request (HARQ) acknowledgment (HARQ-ACK) request field, and a PUCCH priority indicator (PPI) field.

[0213] Example 24 is the method according to Example 23, wherein the value of the PSI field is mapped one-to-one to parameters configured by Radio Resource Control (RRC) signaling. K The value of 3.

[0214] Example 25 is the method according to Example 24, wherein the bit width of the PSI field is determined to be... ,in I These are configured by RRC signaling. K 3. The number of parameter values.

[0215] Example 26 is the method according to Example 24, wherein multiple PSI fields are included in the DCI to support retransmission at multiple PUCCH times triggered by the DCI.

[0216] Example 27 is the method according to Example 23, wherein the PSI field is formed as follows: I Bitmap, in which I express K The number of 3 parameter values, and the I Each bit in the bitmap corresponds to K One of the three parameter values.

[0217] Example 28 is the method according to Example 23, wherein the single HARQ-ACK request field is set to 1 bit and used to trigger the retransmission of the HARQ-ACK CB carried at the retransmitted PUCCH timing indicated by the DCI.

[0218] Example 29 is the method according to Example 23, wherein the PPI field is set to 1 bit.

[0219] Example 30 is the method according to Example 23, wherein the PPI field is configured to indicate the priority of the retransmitted PUCCH.

[0220] Example 31 is the method according to Example 22, wherein the PUCCH timing retransmission is associated with type 2 HARQ-ACKCB, and the DCI includes a counter downlink allocation indicator (C-DAI) field and a total downlink allocation indicator (T-DAI) field.

[0221] Example 32 is the method according to Example 31, wherein the DCI for performing the PUCCH timing retransmission includes: continuously accumulating the C-DAI field and T-DAI field in the DCI that triggers the PUCCH timing retransmission based on the values ​​of the C-DAI field and T-DAI field in the last DCI associated with the retransmitted PUCCH.

[0222] Example 33 is the method according to Example 31, wherein the DCI provided for performing the PUCCH timing retransmission includes: independently resetting and counting the C-DAI field and the T-DAI field in the DCI that triggers the PUCCH timing retransmission, regardless of the values ​​of the C-DAI field and the T-DAI field in the last DCI of the retransmitted PUCCH.

[0223] Example 34 is the method according to Example 33, wherein the DCI for performing the PUCCH timing retransmission further includes: adding an additional T-DAI field to the DCI that triggers the PUCCH timing retransmission to indicate the size of the retransmitted HARQ-ACK.

[0224] Example 35 is an apparatus for a user equipment (UE) comprising: one or more processors configured to perform the method according to any one of Examples 1-21.

[0225] Example 36 is an apparatus for a base station, the apparatus comprising: one or more processors configured to perform the method according to any one of Examples 22-34.

[0226] Example 37 is a computer-readable medium having computer programs stored thereon that, when executed by one or more processors, cause a device to perform the method according to any one of Examples 1-34.

[0227] Example 38 is an apparatus for a communication device, the apparatus including components for performing the method according to any one of Examples 1-34.

[0228] Example 39 is a computer program product comprising computer programs that, when executed by one or more processors, cause a device to perform the method according to any one of Examples 1-34.

[0229] Unless otherwise expressly stated, any of the above embodiments may be combined with any other embodiment (or combination of embodiments). The foregoing description of one or more specific embodiments provides illustration and description, but is not intended to be exhaustive or to limit the scope of the embodiments to the precise forms disclosed. In view of the teachings above, modifications and variations are possible, or modifications and variations may be obtained from the practice of various embodiments.

[0230] It should be recognized that the systems described herein include descriptions of specific implementations. These implementations may be combined into a single system, partially integrated into other systems, divided into multiple systems, or otherwise partitioned or combined. Furthermore, it is conceivable to use parameters / attributes / aspects, etc., of one implementation in another implementation. For clarity, these parameters / attributes / aspects, etc., are described only in one or more implementations, and it should be recognized that unless specifically stated herein, these parameters / attributes / aspects, etc., may be combined with or replace parameters / attributes, etc., of another implementation.

[0231] As is widely recognized, the use of personally identifiable information should comply with privacy policies and practices that are generally accepted to meet or exceed industry or governmental requirements for protecting user privacy. Specifically, personally identifiable information data should be managed and processed to minimize the risk of unintentional or unauthorized access or use, and the nature of authorized use should be clearly explained to users.

[0232] Although the foregoing has been described in considerable detail for clarity, it will be apparent that certain changes and modifications can be made without departing from the principles of this disclosure. It should be noted that there are many alternative ways to implement both the processes and apparatus described herein. Therefore, embodiments of this disclosure should be considered illustrative rather than restrictive, and this specification is not limited to the details given herein but can be modified within the scope of the appended claims and their equivalents.

Claims

1. A processing circuit for wireless communication, the processing circuit being used to: Identify the original HARQ-ACK codebook for the first hybrid automatic repeat request originally scheduled for transmission in the first time slot; Receive downlink control information to trigger a second HARQ-ACK codebook combination in a second time slot that occurs after the first time slot; Physical uplink control channel (PUCCH) transmission is generated by appending the first HARQ-ACK codebook to the second HARQ-ACK codebook; and The PUCCH transmission is transmitted in the second time slot.

2. The processing circuit according to claim 1, wherein the index of the second time slot is: n And the second HARQ-ACK codebook is based on the configuration by Radio Resource Control (RRC). K1 The value is associated with the second time slot.

3. The processing circuit according to claim 1, wherein the first HARQ-ACK codebook is a Type 1 HARQ-ACK codebook.

4. The processing circuit according to claim 1, wherein the processing circuit is further configured to: Exclude duplicate HARQ-ACK bits present in both the second HARQ-ACK codebook and the first HARQ-ACK codebook.

5. The processing circuit according to claim 1, wherein the processing circuit is further configured to: The second HARQ-ACK codebook is concatenated with the first HARQ-ACK codebook.

6. A method for wireless communication, the method comprising: A physical downlink shared channel (PDSCH) transmission is generated, wherein the PDSCH transmission is associated with the original scheduled first hybrid automatic repeat request-acknowledgment (HARQ-ACK) codebook for transmission in the first time slot; Generate downlink control information (DCI) to trigger a second HARQ-ACK codebook in a second time slot occurring after the first time slot; and In the second time slot, a Physical Uplink Control Channel (PUCCH) transmission is received, the PUCCH transmission including the first HARQ-ACK codebook appended to the second HARQ-ACK codebook.

7. The method according to claim 6, wherein the index of the second time slot is n And the second HARQ-ACK codebook is based on the configuration by Radio Resource Control (RRC). K1 The value is associated with the second time slot.

8. The method according to claim 6, wherein the second HARQ-ACK codebook is concatenated with the first HARQ-ACK codebook.

9. A method for wireless communication, the method comprising: Downlink Control Information (DCI) is detected in the first time slot with index n, the DCI indicating the index n. nK The retransmission of the Physical Uplink Control Channel (PUCCH) timing associated with the second time slot of 3, wherein, K 3. Indicated by the DCI or Radio Resource Control (RRC) signaling, wherein the DCI further includes the PUCCH Slot Indicator (PSI) field, the Single HARQ-ACK Request field, and the PUCCH Priority Indicator (PPI) field; Based on the detection of the DCI in the first time slot, identify the hybrid automatic repeat request-acknowledgment (HARQ-ACK) codebook associated with the PUCCH timing; Output the HARQ-ACK codebook for transmission.

10. The method of claim 9, wherein the value of the PSI field is mapped one-to-one to the value of parameter K3 configured by Radio Resource Control (RRC) signaling.

11. The method of claim 10, wherein the bit width of the PSI field is determined as follows: log 2 (I) ,in I This indicates the configuration of the RRC signaling. K 3. The number of parameter values.

12. The method of claim 10, wherein a plurality of the PSI fields are included in the DCI to support multiple PUCCH timing retransmissions triggered by the DCI.

13. The method according to any one of claims 10 to 12, wherein K 3. As indicated by the DCI.

14. The method of claim 9, further comprising: Detect the priority associated with the HARQ-ACK codebook; as well as Based on the detection of the priority, HARQ-ACK feedback for Physical Downlink Shared Channel (PDSCH) transmission in a time slot earlier than the second time slot is abandoned.

15. The method according to any one of claims 10 to 12, further comprising: The HARQ-ACK codebook is transmitted during the target PUCCH timing, and the PUCCH timing corresponds to the target PUCCH timing. K The time slot interval with a value of 3.

16. The method of claim 9, wherein the PSI field is formed as I Bitmap, in which I express K The number of parameter values, and the stated I Each bit in the bitmap corresponds to the K One of the three parameter values.

17. The method of claim 9, wherein the single HARQ-ACK request field is used to trigger the retransmission at the PUCCH timing.

18. The method of claim 9, wherein the PPI field is used to indicate the priority of the HARQ-ACK codebook.

Images