Method and apparatus for codebook group based operation with multi-physical downlink shared channel scheduling

Abstract

A method for a user equipment (UE) is provided. The method includes obtaining a downlink control information (DCI) configured for multiple physical downlink shared channel (PDSCH) scheduling, determining whether codebook group (CBG) based operation is enabled for the scheduled PDSCHs based on a number of PDSCHs scheduled by the DCI, and determining a format of the DCI based on the number of PDSCHs scheduled by the DCI.

Description

Technical Field

[0001] This application relates generally to wireless communication systems, and more specifically to methods and apparatus for codebook group (CBG)-based operations using multi-physical downlink shared channel (PDSCH) scheduling. 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, 3rd Generation Partnership Project (3GPP) Long Term Evolution (LTE); 5th Generation (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).

[0003] The NR specification defines operation at frequencies up to 52.6 GHz, where all physical layer channels, signals, procedures, and protocols are designed to be optimized for use at 52.6 GHz. Recently, spectrum above 52.6 GHz (e.g., 52.6 GHz to 71 GHz) has been developed, and research on supporting NR in such frequency schemes continues. Among these, further discussion is needed on whether and how to utilize multi-PDSCH scheduling to support CBG-based operation. Summary of the Invention

[0004] According to an aspect of this disclosure, a method for a user equipment (UE) is provided, the method comprising: acquiring downlink control information (DCI) configured for multiple physical downlink shared channel (PDSCH) scheduling; determining whether to enable codebook group-based (CBG) operation for the scheduled PDSCHs based on the number of PDSCHs scheduled by the DCI; and determining the format of the DCI based on the number of PDSCHs scheduled by the DCI.

[0005] According to an aspect of this disclosure, a method for a user equipment (UE) is provided, the method comprising: acquiring downlink control information (DCI), wherein the DCI includes a time domain resource allocation (TDRA) field, and the value of the TDRA field provides a row index to an allocation table containing rows each having one or more start and length indication values ​​(SLIV); determining a subcodebook association of Hybrid Automatic Repeat Request (HARQ) Acknowledgment (HARQ-ACK) information bits based on the acquired DCI; and generating HARQ-ACK information bits based on the associated HARQ-ACK subcodebook.

[0006] According to an aspect of this disclosure, a method for a base station is provided, the method comprising: configuring downlink control information (DCI) for user equipment (UE) for scheduling multiple physical downlink shared channels (PDSCH), wherein a time domain resource allocation (TDRA) field of the DCI indicates the number of PDSCHs scheduled; and providing the DCI so that the UE determines, based on the TDRA field of the DCI, whether to enable codebook group (CBG) based operation.

[0007] According to an aspect of this disclosure, a method for a base station is provided, the method comprising: generating downlink control information (DCI), wherein the format of the DCI includes a time-domain resource allocation (TDRA) field, and the value of the TDRA field provides a row index to an allocation table containing rows each having one or more start and length indication values ​​(SLIV); and transmitting the DCI for a user equipment (UE) to determine a subcodebook association of Hybrid Automatic Repeat Request (HARQ) Acknowledgment (HARQ-ACK) information bit feedback.

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

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

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

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

[0012] 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

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

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

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

[0016] Figure 3A and Figure 3B An exemplary procedure is shown for the UE to interpret DCI and determine CBG-based operations.

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

[0018] Figure 5 A schematic diagram of HARQ-ACK padding for associating two HARQ-ACK subcodebooks is shown according to some implementation schemes.

[0019] Figure 6 Examples of C-DAI and T-DAI settings based on two HARQ-ACK subcodebook associations and three HARQ-ACK subcodebook associations are shown according to some implementation schemes.

[0020] Figure 7A and Figure 7B A schematic diagram is shown of the DCI Format 1_0 extension to support more than two subcodebooks for CA.

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

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

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

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

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

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

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

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

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

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

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

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

[0033] Figure 1 A 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.

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

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

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

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

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

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

[0040] like Figure 2 As shown, the method 200 for a UE may include the following steps: S202, obtaining downlink control information (DCI) configured for multi-physical downlink shared channel (PDSCH) scheduling; S204, determining whether to enable codebook group-based (CBG) operation based on the number of PDSCHs scheduled by the DCI; and S206, determining the format of the DCI based on the number of PDSCHs scheduled by the DCI.

[0041] At step S202, a single DCI format 1_1 can be used to enable or disable multi-PDSCH scheduling based on CBG operations. The UE can obtain the DCI from the base station (e.g., gNB).

[0042] In some implementations, method 200 may further include a step of interpreting the format of the DCI after acquiring the DCI in S202. In this step, the UE may determine the number C of scheduled PDSCHs, which is indicated by the Time Domain Resource Allocation (TDRA) field in the acquired DCI. For example, the number C of scheduled PDSCHs may be 2, 4, or 8, meaning that two, four, or eight PDSCHs are actually scheduled.

[0043] In some implementations, at step S204, determining whether to enable CBG-based operations based on DCI may include: comparing the number C of scheduled PDSCHs with a threshold M. PDSCH,c The comparison is made based on the threshold, which represents the maximum number of PDSCHs that can be enabled for CBG-based operations for the serving cell; and if the number of scheduled PDSCHs C is greater than the threshold M. PDSCH,c If so, then CBG-based operations will be disabled.

[0044] In some implementations, at step S206, the number C of scheduled PDSCHs is greater than a threshold M. PDSCH,c In cases where the format determination may include: the absence of a CBG Transmission Indicator (CBGTI) field in the DCI; and determining the bit width of each of the New Data Indicator (NDI) field and the Redundancy Version (RV) field in the DCI.

[0045] In some implementations, the bit width of each of the NDI and RV fields can be determined by the maximum number of schedulable PDSCHs for the serving cell based on the TDRA field of the DCI, and each bit of the NDI and RV fields corresponds to one of the scheduled PDSCHs.

[0046] The above processes in steps S204 and S206 can correspond to the following case 1.

[0047] Case 1: If C > M PDSCH,c This will confirm that CBG-based operations are disabled.

[0048] The bit size can be determined for the NDI field (2, 3, 4, 5, 6, 7, or 8 bits), and the bit size can also be determined for the RV field (2, 3, 4, 5, 6, 7, or 8 bits). This determination can be based on the maximum number S of schedulable PDSCHs across all entries in the TDRA. c (For example, S) c It can be eight, meaning the maximum number of SLIVs is 8. Each bit of the NDI field and each bit of the RV field can correspond to a scheduled PDSCH. The bit size of the CBGTI field can be considered zero, i.e., 0 bits.

[0049] For example, if the number of PDSCHs scheduled, C, is 4 (i.e., indicating that the actual number of PDSCHs scheduled is 4), and the threshold M... PDSCH,c If the value is 2 (i.e., the maximum number of PDSCHs indicating that CBG-based operations are enabled for the serving cell is 2), then CBG-based operations are disabled because C > M. PDSCH,c In S cWhen the value is 8, the 8-bit size can be determined for the NDI field, and the 8-bit size can also be determined for the RV field. The 0-bit size can be determined for the CBGTI field.

[0050] See below for reference Figure 3A Further explanation of Case 1.

[0051] In some implementations, at step S204, determining whether to enable CBG-based operations based on DCI may include: comparing the number C of scheduled PDSCHs with a threshold M. PDSCH,c The comparison is made using the threshold, which represents the maximum number of PDSCHs that can be enabled for CBG-based operations on the serving cell; if the number of scheduled PDSCHs C is equal to or less than the threshold M... PDSCH If so, then CBG-based operations will be enabled.

[0052] In some implementations, at step S206, the number C of scheduled PDSCHs is equal to or less than the threshold M. PDSCH In this case, determining the format of the DCI includes: the presence of a CBG Transmission Indicator (CBGTI) field in the DCI; and determining the bit width of each of the NDI field, RV field, and CBGTI in the DCI.

[0053] In some implementations, the bit width of the NDI field is equal to the threshold M. PDSCH,c The value; the bit width of the RV field is equal to the threshold M. PDSCH,c The value is multiplied by a predetermined coefficient K, which takes the value of 1 or 2; and the bit size of the CBGTI field is equal to the threshold M. PDSCH,c The value multiplied by the maximum number N of CBG per transport block c And each bit of the NDI field and each K bits of the RV field correspond to one of the scheduled PDSCHs with CBG-based operation enabled, and the CBGTI field includes subfields each corresponding to one of the scheduled PDSCHs with CBG-based operation enabled.

[0054] The above processes in steps S204 and S206 can correspond to the following case 2.

[0055] Case 2: If C <= M PDSCH,c This will confirm that CBG-based operations are disabled.

[0056] For example, if the number of PDSCHs scheduled, C, is 2 (i.e., indicating that the actual number of PDSCHs scheduled is 2), and the threshold M... PDSCH,cIf the value is also 2 (i.e., the maximum number of PDSCHs indicating that CBG-based operations are enabled for the serving cell is 2), then CBG-based operations are enabled because C <= M. PDSCH,c .

[0057] In this case, the bit size of the NDI field can be determined as M. PDSCH,c Bits, and the bit size of the RV field can be determined as M. PDSCH,c *K bits. In some designs, K = 1 or 2. The bit size of the CBGTI field can be determined as M. PDSCH *Nc bits (N c N represents the maximum number of CBGs per transport block. c ).

[0058] For example, if the threshold M PDSCH,c If the value is 2 and the coefficient K is set to 2, then the NDI field has a bit size of 2 bits, and the RV field has a bit size of 4 bits. Each bit of the NDI field and every K bits of the RV field (2 bits in this example) can correspond to a scheduled PDSCH with CBG-based operations. If, for example, the maximum number N of CBGs per transport block... c If the value is 4 (i.e., at most four CBGs are configured for each transport block), then the bit size of the CBGTI field is 8 bits. Here, the CBGTI field may include two subfields (i.e., each subfield is 4 bits), and each subfield may correspond to a scheduled PDSCH with CBG-based operation enabled.

[0059] See below for reference Figure 3B Further explanation of case 2.

[0060] In some implementations, in case 2, the NDI field, RV field, and CBGTI field are concatenated to each other, and when CBG-based operations are disabled, a zero-padding operation is applied to the concatenated fields to align their sizes.

[0061] In the above process, the threshold M can be determined in various ways. PDSCH,c This threshold indicates the maximum number of PDSCHs that enable CBG-based operations for the serving cell.

[0062] In some implementation schemes, M PDSCH,c Provided on a per-component carrier (CC) basis via Radio Resource Control (RRC) signaling. For example, for serving cell 'c', M PDSCH,c =2.

[0063] In some implementations, the UE can assign a threshold M PDSCH,cAssume the value is 1. In RRC, no threshold M is provided for serving cells that have enabled CBG-based operations. PDSCH,c In this case, UE can assume M PDSCH,c =1.

[0064] In other words, the condition for the existence of CBG-related DCI fields (i.e., CBGTI fields) is that there are at most M... PDSCH,c Scheduled by DCI format 1_1. This explains case 1 (where four PDSCHs are scheduled, with a threshold M greater than 2). PDSCH,c The size of bit 0 in the CBGTI field and case 2 (where two PDSCHs are scheduled, and their values ​​do not exceed the threshold M of 2). PDSCH,c The 8-bit size of the CBGTI field in ().

[0065] In some implementations, the threshold M PDSCH,c It is based on the maximum number S of SLIVs that can be indicated by the TDRA field of the DCI. c Divide by the maximum number N of CBG per transport block c It's confirmed.

[0066] According to this disclosure, the concatenated fields <“NDI”, “RV”, “CBGTI”> in DCI format 1_1 can be conditionally reused for the “CBGTI” field based on the number of dynamically scheduled PDSCHs to minimize downlink (DL) signaling overhead.

[0067] Figure 3A and 3B An exemplary procedure is shown for the UE to interpret DCI and determine CBG-based operations.

[0068] For ease of explanation Figure 3A and Figure 3B Make the following assumptions:

[0069] Maximum number of SLIVs in the TDRA field: S c =8;

[0070] - Maximum number of CBGs per transport block: N c =4;

[0071] - A threshold M indicating the maximum number of PDSCHs that enable CBG-based operations. PDSCH,c Therefore, it was determined to be:

[0072] When CBG-based operations are enabled, K=2 for the RV field.

[0073] like Figure 3AAs shown, the UE can decode DCI 311 and determine that four PDSCHs 310 have been scheduled (i.e., the number of scheduled PDSCHs C is 4) by decoding the TDRA field 312. Based on the above threshold M... PDSCH,c Assuming the value is 2, we can determine that C > M. PDSCH,c This means disabling CBG-based operations, and therefore applying case 1 above.

[0074] Therefore, the UE can determine the format of DCI 311 based on the determination of Case 1. Specifically, the CBGTI field is absent, i.e., it has a bit size of 0 bits. The NDI field 313 has a bit size of 8 bits, and the RV field 314 also has a bit size of 8 bits (i.e., the maximum number of SLIVs in the TDRA field: S). c =8).

[0075] like Figure 3B As shown, the UE can decode DCI 321 and determine that two PDSCHs 320 have been scheduled (i.e., the number of scheduled PDSCHs C is 2) by decoding the TDRA field 322. Based on the above threshold M... PDSCH,c Assuming the value is 2, we can determine that C <= M. PDSCH,c This means enabling CBG-based operations and therefore applying situation 2 above.

[0076] Therefore, the UE can determine the format of DCI 321 based on the determination of case 2. The NDI field 323 has a bit size of 2 bits (i.e., M...). PDSCH,c 4 bits (2 bits); RV field 324 has a bit size of 4 bits (i.e., M PDSCH,c *K bits (2*2 bits)); and the CBGTI field 325 has an 8-bit size (i.e., M). PDSCH *Nc bits (2*4 bits); CBGTI field 325 may include two sub-CBGTI fields 325-1 and 325-2, each sub-CBGTI field having a bit size of 4 bits. In this case, each bit of NDI field 323 and each 2 bits of RV field (K=2) may correspond to a scheduled PDSCH with CBG-based operation enabled. Each of sub-CBGTI fields 325-1 and 325-2 may correspond to a scheduled PDSCH with CBG-based operation enabled.

[0077] In addition, zero-padding can be applied to the concatenated NDI, RV, and CBGTI fields to align the aggregated payload size. For example... Figure 3A and Figure 3B As shown, the zero-padding field 326 with two zero-padding bits is used in case 2 ( Figure 3B ), to compare the bit size of DCI with case 1 ( Figure 3A The bit size alignment of the DCI.

[0078] According to this disclosure, the concatenated NDI field, RV field and CBGTI field can minimize DL signaling overhead.

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

[0080] like Figure 4 As shown, the method 400 for a UE may include the following steps: S402, acquiring downlink control information (DCI), wherein the DCI includes a time domain resource allocation (TDRA) field, and the value of the TDRA field provides a row index to an allocation table containing rows each having one or more start and length indication values ​​(SLIV); S404, determining a subcodebook association of Hybrid Automatic Repeat Request (HARQ) Acknowledgment (HARQ-ACK) information bits based on the acquired DCI; and S406, generating HARQ-ACK information bits based on the associated HARQ-ACK subcodebook.

[0081] At step S404, the subcodebook association for HARQ-ACK can be determined by various methods, including the following.

[0082] Method 1: Two subcodebooks for HARQ-ACK

[0083] In some implementations, determining the subcodebook association for the HARQ-ACK information bits involves generating a first subcodebook that includes the HARQ-ACK bits for one of the following DCIs:

[0084] -DCI is used to schedule PDSCH on a CC that is not configured with codebook group (CBG) based operations but has a TDRA table configured, where each of these rows in the TDRA table has a single SLIV;

[0085] -DCI is used to schedule PDSCH on a CC that is not configured with CBG-based operations but has a TDRA table configured, where at least one of these rows in the TDRA table has multiple SLIVs, and DCI schedules a single PDSCH.

[0086] -DCI is used for semi-persistent scheduling (SPS) physical downlink shared channel (PDSCH) release; and

[0087] -DCI is used for secondary cell (SCell) hibernation indication in the absence of scheduling PDSCH.

[0088] In some implementations, determining the subcodebook association for the HARQ-ACK information bits includes generating a second subcodebook that includes the HARQ-ACK bits for one of the following DCIs:

[0089] -DCI is used to schedule PDSCHs on a CC with a TDRA table configured, where at least one row in the TDRA table has multiple SLIVs, and DCI schedules multiple PDSCHs; and

[0090] -DCI is used to schedule PDSCH on a CC that is configured with CBG-based operations and has a TDRA table configured, where at least one row in the TDRA table has multiple SLIVs, or each row has a single SLIV.

[0091] Method 1 described above can be summarized in Table 1 below.

[0092] Table 1: Association between two HARQ-ACK subcodebooks for enabling CBG-based multi-PDSCH scheduling .

[0093]

[0094]

[0095] In some implementations, at step S406, generating HARQ-ACK feedback bits for the second subcodebook based on subcodebook association may further include generating HARQ-ACK bits for CBG if CBG operation is enabled; and generating HARQ-ACK bits for transport blocks in PDSCH if CBG operation is disabled.

[0096] In other words, the UE can generate a HARQ-ACK bit for each CBG when CBG-based operation is enabled, and can generate a HARQ-ACK bit for each TB when CBG-based operation is disabled.

[0097] In some implementations, the step of generating HARQ-ACK bits for the second subcodebook may further include: generating padding HARQ-ACK bits for the second subcodebook. The step of generating padding HARQ-ACK bits for the second subcodebook may include the following sub-steps:

[0098] i) Determine the first parameter for filling the HARQ-ACK bits in Where S max =max{S c And N max =max{M PDSCH,c *N c}where S cIndicates the maximum number of SLIVs for a serving cell configured with multiple PDSCH scheduling operations; N c This represents the maximum number of CBGs per transport block for a serving cell configured with CBG operations; and M PDSCH,c This indicates a threshold, which is defined as the maximum number of PDSCHs that enable CBG-based operations for the serving cell.

[0099] ii) Determine the second parameter K for filling the HARQ-ACK bits. C K C When CBG operation is enabled, this represents the actual number of CBGs scheduled; and when multi-PDSCH scheduling is configured for the serving cell and CBG operation is disabled, this represents the actual number of PDSCHs scheduled.

[0100] iii) The last The bits are determined to be the padding HARQ-ACK bits.

[0101] In step i), for each multi-PDSCH schedule or CBG-based PDSCH associated with the second HARQ-ACK subcodebook, the UE can generate the first parameter as follows: Where S max =max{S c And N max =max{M PDSCH,c *N c The above has described reference S. c N c and M PDSCH,c Each representation of . For example, if S c N c and M PDSCH,c If the values ​​are 8, 3, and 2 respectively, then the UE can be determined. It is 8.

[0102] In step ii), the UE can determine the second parameter K based on the following rules. C If CBG-based operations are enabled, then K C This indicates the actual number of CBGs scheduled; and if CBG-based operations are disabled in the case of multi-PDSCH scheduling, then K... C This represents the actual number of PDSCHs scheduled. For example, based on practical applications, K... C It can be 4, 6, or 8, etc.

[0103] In step iii), the UE can then... Each bit is determined to be used to fill the HARQ-ACK bits. For example, if the first parameter The value is 8, and the second parameter K C If the value is 6, then the last two bits will be used to fill the HARQ-ACK bits.

[0104] In this case, the UE will generate a corresponding value for filling the HARQ-ACK bit.

[0105] In some implementations, generating padding HARQ-ACK bits for the second subcodebook may further include: generating a negative acknowledgment (NACK) for each of these padding HARQ-ACK bits; or generating the first one... One bit is used as padding HARQ-ACK bits for retransmission.

[0106] In other words, there are two options available for generating corresponding values ​​for filling the HARQ-ACK bits:

[0107] Option 1: UE can generate a final... The NACK value for each bit in the bits.

[0108] Option 2: The UE can retransmit the oldest generated file. One HARQ-ACK bit.

[0109] The following is for reference. Figure 5 Further explanation of the above-described HARQ-ACK padding used in Method 1 will be provided.

[0110] According to this disclosure, the creation of the HARQ-ACK subcodebook enables CBG-based operation for multi-PDSCH scheduling with minimized DL / UL signaling overhead.

[0111] Figure 5 A schematic diagram of HARQ-ACK padding for associating two HARQ-ACK subcodebooks is shown according to some implementation schemes.

[0112] For ease of explanation Figure 5 Make the following assumptions:

[0113] - Enable CBG-based operations, and the actual number of CBGs scheduled is 6 (K). c =6); and

[0114] - N c =3, and M PDSCH,c =2.

[0115] like Figure 5As shown, based on the above assumptions, two PDSCHs, 510-1 and 510-2, are scheduled, and each of PDSCHs 510-1 and 510-2 corresponds to three CBGs 512. As described above, when CBG-based operation is enabled, the UE can generate HARQ-ACK bits for each CBG. Figure 5 An example is shown where HARQ-ACK bits are generated as “ACK, NACK, NACK, NACK, ACK, ACK” for six CBG 512s.

[0116] Furthermore, based on the first parameter mentioned above Second parameter K c Assuming 6, the UE can use the last 2 bits (i.e., the last...) (10 bits) are determined as the padding HARQ-ACK bits. Therefore, the padding HARQ-ACK bits can be generated based on one of the above options 1 and 2.

[0117] For option 1, generate two "NACK, NACK" bits for each of the two padding HARQ-ACK bits 513. For option 2, retransmit the first "ACK, NACK" bits 515 as two padding HARQ-ACK bits 514.

[0118] Method 2: Three subcodebooks for HARQ-ACK

[0119] In some implementations, determining the subcodebook association of HARQ-ACK may include generating a first subcodebook for the component carrier (CC). This step may be the same as the step in Method 1.

[0120] In some implementations, determining the subcodebook association for the HARQ-ACK information bits also includes generating a second subcodebook that includes the HARQ-ACK bits for one of the following DCIs:

[0121] -DCI is used to schedule PDSCH on a CC that is not configured with CBG-based operations but has a TDRA table configured, where at least one row in the TDRA table has multiple SLIVs, and DCI schedules multiple PDSCH; and

[0122] -DCI is used to schedule PDSCHs on a CC configured with CBG-based operations and a TDRA table, where at least one row has multiple SLIVs and the number of PDSCHs scheduled by DCI is greater than a threshold M. PDSCH,c This threshold is defined as the maximum number of PDSCHs that enable CBG-based operations.

[0123] In some implementations, determining the subcodebook association for the HARQ-ACK information bits also includes generating a third subcodebook that includes the HARQ-ACK bits for one of the following DCIs:

[0124] -DCI is used to schedule PDSCH on a CC configured with CBG-based operations and a TDRA table configured, where each row in the TDRA table has a single SLIV; and

[0125] -DCI is used to schedule PDSCHs on a CC configured with CBG-based operations and a TDRA table, where at least one row in the TDRA table has multiple SLIVs, and the number of PDSCHs scheduled by DCI is equal to or less than a threshold M. PDSCH,c This threshold is defined as the maximum number of PDSCHs that enable CBG-based operations.

[0126] Method 2 described above can be summarized in Table 2 below.

[0127] Table 2: Association of three HARQ-ACK subcodebooks for enabling CBG-based multi-PDSCH scheduling .

[0128]

[0129] In some implementations, at step S406, generating HARQ-ACK feedback bits based on subcodebook association includes determining the number of HARQ-ACK bits for the first, second, and third subcodebooks. This determination may include determining the number of HARQ-ACK bits for each of the first, second, and third subcodebooks. This step may include the following sub-steps:

[0130] a) Determine the first size of the first subcodebook as... in K represents the value of the total downlink assignment indicator (T-DAI) used for the first subcodebook, and K is 2 if the UE is configured to receive two transport blocks in at least one configured downlink (DL) bandwidth portion (BWP), otherwise it is 1;

[0131] b) Determine the second size of the second subcodebook as... Let S represent the value of T-DAI used in the second subcodebook, and S c This indicates the maximum number of SLIVs configured for a serving cell with multiple PDSCH scheduling; and

[0132] c) Determine the third size of the third subcodebook as in M represents the value of T-DAI in the third subcodebook;PDSCH,c This represents a threshold, indicating the maximum number of PDSCHs that enable CBG-based operations for the serving cell; and N c This indicates the maximum number of CBGs per transport block for a serving cell where CBG operation is enabled.

[0133] In some implementations, at step S406, generating HARQ-ACK feedback information bits based on subcodebook association may further include: sequentially concatenating the HARQ-ACK bits of the first subcodebook, the second subcodebook, and the third subcodebook based on the subcodebook index; and transmitting the concatenated HARQ-ACK bits through the Physical Uplink Control Channel (PUCCH) or the Physical Uplink Shared Channel (PUSCH).

[0134] In some implementations, the Counter Downlink Assignment Indicator (C-DAI) and the Total Downlink Assignment Indicator (T-DAI) are counted independently within their respective subcodebooks. In other words, the values ​​of C-DAI and T-DAI are not applicable to different DCIs across different HARQ-ACK subcodebooks. Further details will be discussed in [the following section / section / etc.]. Figure 6 More details are shown below.

[0135] In addition to methods 1 and 2, it is also possible that the UE may not expect to enable multiple PDSCH scheduling and CBG-based operations for CC simultaneously within the same PUCCH group.

[0136] Figure 6 Examples of C-DAI and T-DAI settings based on two HARQ-ACK subcodebook associations and three HARQ-ACK subcodebook associations are shown according to some implementation schemes.

[0137] like Figure 6 The diagram illustrates an example of carrier aggregation (CA) for eight CCs. For CC0 and CC1 on FR1, a single PDSCH is scheduled with CBG-based operations disabled. For CC2 and CC3 on FR1, a single PDSCH is scheduled with CBG-based operations enabled. For example, assuming URLLC is enabled on these two CCs from a system perspective, CBG is expected to improve resource efficiency. For CC4 and CC5, multiple PDSCH scheduling is configured with CBG-based operations enabled. For CC6 and CC7, multiple PDSCH scheduling is configured with CBG-based operations disabled.

[0138] In addition, for ease of explanation Figure 6 Make the following assumptions:

[0139] - Maximum number of SLIVs for CC configuration: S c =8;

[0140] - Maximum number of CBGs per transport block: N c =4; and

[0141] -M PDSCH,c =1 (for method 2)

[0142] As from Figure 6 It is evident that the values ​​of C-DAI and T-DAI are not applicable to different DCIs across different HARQ-ACK subcodebooks. For example, the values ​​of C-DAI and T-DAI are recounted for the second subcodebook and for the third subcodebook.

[0143] Based on the above assumptions, the size of the corresponding subcodebook can be calculated, as shown in Table 3 below:

[0144] Table 3: Size of the corresponding subcodebooks for Method 1 and Method 2 .

[0145]

[0146]

[0147] As shown in Table 3, the HARQ-ACK codebook size based on Method 2 is smaller than that of Method 1, which can provide additional benefits for reducing overhead.

[0148] Furthermore, for the association of three HARQ-ACK subcodebooks used to implement individual subcodebooks, various solutions regarding the DAI in the DCI associated with DCI format 0_1 ​​can be considered.

[0149] In some implementations, the UE may obtain a DCI associated with DCI format 0_1, wherein the DCI format includes one or two 2-bit extension fields to indicate the T-DAI value of a third subcodebook, wherein the 2-bit extension field is added to a second DAI field within the T-DAI field.

[0150] Figure 7A and Figure 7B A schematic diagram is shown of the DCI Format 1_0 extension to support more than two subcodebooks for CA.

[0151] like Figure 7A As shown, a 2-bit extension field 712 for the third subcodebook is added to the existing field 711 in the T-DAI field 710. This implementation will cover the following cases: 1) a dynamic HARQ-ACK codebook with two HARQ-ACK subcodebooks; 2) an enhanced dynamic HARQ-ACK codebook with two HARQ-ACK subcodebooks and without UL-TotalDAI-Included configured.

[0152] like Figure 7B As shown, a 2-bit extension field 722-1 for the third subcodebook is added to the existing field 721-1, and a 2-bit extension field 722-2 for the third subcodebook is added to the existing field 721-2. This implementation will involve the following case: 3) an enhanced dynamic HARQ-ACK codebook with two HARQ-ACK subcodebooks and UL-TotalDAI-Included=true.

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

[0154] like Figure 8 As shown, the method 800 for a base station may include the following steps: S802, generating downlink control information (DCI) for user equipment (UE) for scheduling multiple physical downlink shared channels (PDSCH), wherein the time domain resource allocation (TDRA) field of the DCI indicates the number of PDSCHs scheduled; and S804, transmitting the DCI so that the UE can determine whether to enable codebook group-based (CBG) operation based on the TDRA field of the DCI.

[0155] In some implementations, method 800 further includes: configuring a threshold M PDSCH,c This threshold indicates the maximum number of PDSCHs that enable CBG-based operations for the serving cell; and the threshold M is provided via Radio Resource Control (RRC) signaling. PDSCH,c To provide UE with DCI-based TDRA field and threshold M PDSCH,c Determine whether to enable CBG-based operations.

[0156] Reference made by the UE regarding whether to enable CBG-based operations and regarding the format of DCI. Figure 2 , Figure 3A and Figure 3B The description has been provided, and therefore the details will not be repeated here.

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

[0158] like Figure 9 As shown, base station 910 can generate 901DCI for UE 920 for multi-PDSCH scheduling, wherein the time domain resource allocation (TDRA) field of DCI indicates the number of PDSCHs scheduled, and can transmit 902DCI to UE 920.

[0159] When acquiring the DCI, UE 920 can determine 903 whether CBG-based operation is enabled based on the TDRA field of the DCI, and can determine 904 the format of the DCI based on this determination.

[0160] 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 described herein is used to implement this.

[0161] like Figure 10 As shown, the method 1000 for a base station may include the following steps: S1002, generating downlink control information (DCI), wherein the format of the DCI includes a time domain resource allocation (TDRA) field, and the value of the TDRA field provides a row index to an allocation table containing rows each having one or more start and length indication values ​​(SLIV); and S1004 transmitting the DCI for a user equipment (UE) to determine a subcodebook association of Hybrid Automatic Repeat Request (HARQ) Acknowledgment (HARQ-ACK) information bit feedback.

[0162] In some implementations, subcodebook associations may include two HARQ-ACK subcodebook associations (Method 1) and three HARQ-ACK subcodebook associations (Method 2) as described above. Detailed information on both methods has been referenced. Figures 4 to 7B A detailed description has been provided, and therefore the details will not be repeated here.

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

[0164] like Figure 11 As shown, base station 1110 can generate 1101 DCI, wherein the format of DCI includes a TDRA field, which includes a table containing rows, each with one or more SLIVs, and DCI can be transmitted 1102 to UE 1120.

[0165] When acquiring the DCI, UE 1120 can determine the subcodebook association 1103 for HARQ-ACK based on the DCI. Subsequently, UE 1120 can provide HARQ-ACK feedback 1104 to base station 1110 based on the subcodebook association for HARQ-ACK.

[0166] 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 a UE as described above.

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

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

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

[0170] According to another 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.

[0171] According to this disclosure, CBG-based operation for multi-PDSCH scheduling can be implemented with minimized DL / UL signaling overhead.

[0172] 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 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) (at least 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).

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

[0174] Baseband circuitry 1204 may include circuitry such as, but not limited to, one or more single-core or multi-core processors. Baseband circuitry 1204 may include one or more baseband processors or control logic components to process baseband signals received from the receive signal path of RF circuitry 1220 and to generate baseband signals for the transmit signal path of RF circuitry 1220. Baseband circuitry 1204 may interact with application circuitry 1202 to generate and process baseband signals and control the operation of RF circuitry 1220. For example, in some embodiments, baseband circuitry 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.

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

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

[0177] 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 circuit 1220 may further include synthesizer circuit 1228 for synthesizing frequencies used by mixer circuit 1222 in the received signal path and / or transmitted signal path. In some embodiments, mixer circuit 1222 in the received signal path may be configured to down-convert the RF signal received from FEM circuit 1230 based on the synthesized frequency provided by synthesizer circuit 1228. Amplifier circuit 1224 may be configured to amplify the down-converted signal, and filter circuit 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 circuit 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 circuit 1222 in the received signal path may include a passive mixer, but the scope of the embodiments is not limited in this respect.

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

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

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

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

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

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

[0184] 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 circuitry 1204 or the application circuitry 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 circuitry 1202.

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

[0186] 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 may be used with quadrature generator and frequency divider circuitry to generate multiple signals having multiple different phases relative to each other at that 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.

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

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

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

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

[0191] In some implementations, PMC 1234 can 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 can be powered down for short intervals, thereby saving power.

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

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

[0194] The processors of application circuit 1202 and baseband circuit 1204 are elements that can be used to execute one or more instances of a 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 a Radio Resource Control (RRC) layer, which will be described in further detail below. As mentioned herein, layer 2 may include a Media Access Control (MAC) layer, a Radio Link Control (RLC) layer, and a 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.

[0195] Figure 13 An exemplary interface 1300 of a baseband circuit according to some embodiments is shown. As described 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.

[0196] The baseband circuit 1204 may further include: one or more interfaces for communicatively coupling to other circuits / devices, such as a memory interface 1304 (e.g., an interface for sending / receiving data to / from a memory external to the baseband circuit 1204); and an application circuit interface 1306 (e.g., for sending / receiving data to / from a memory external to the baseband circuit 1204); Figure 12 Application circuit 1202 (interface for sending / receiving data); RF circuit interface 1308 (e.g., for sending / receiving data to / from...). Figure 12 The RF circuit 1220 is an interface for transmitting / receiving data; the wireless hardware connection interface 1310 (e.g., for transmitting / receiving data to / from near field communication (NFC) components, Components (e.g.) (low power consumption) 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).

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

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

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

[0200] 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, etc. Components (e.g.) (low power consumption) Components and other communication components.

[0201] Instructions 1424 may include software, programs, applications, applets, or other executable code for causing at least one processor in processor 1412 to perform any or more of the methods discussed herein. Instructions 1424 may reside wholly or partially within 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. Therefore, the memory of processor 1412, memory / storage device 1418, peripheral device 1406, and database 1408 are examples of computer-readable and machine-readable media.

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

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

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

[0205] 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 it can 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, instrument cluster mobility 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.

[0206] In some implementations, any of the UEs in UE 1501 can be IoT UEs, which may include a network access layer designed to utilize low-power IoT applications with short-lived UE connections. IoT UEs may use technologies such as M2M or MTC to exchange data with MTC servers or devices 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. IoT UEs may execute background applications (e.g., keeping track of activity messages, status updates, etc.) to facilitate connectivity within the IoT network.

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

[0208] In this example, connections 1503 and 1504 are shown as air interfaces for communication coupling and can be consistent 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 alternatively 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.

[0209] 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 Wireless Fibre. 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.

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

[0211] In some implementations, all or part of RAN node 1511 can 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 can 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 head units 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. 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.

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

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

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

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

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

[0217] 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 media 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. Media / carrier sensing operations can be performed according to the Listen-After-Speak (LBT) protocol.

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

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

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

[0221] 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 (called "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.

[0222] 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 can also inform UE 1501 about the transmission format, resource allocation, and HARQ information related to the uplink shared channel. Typically, downlink scheduling (assignment 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 sent on the PDCCH used for (e.g., assigned to) each UE in UE 1501.

[0223] 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 for rate matching using a sub-block interleaver. 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.

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

[0225] 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. Xn interfaces are 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 UE1501 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 transmission 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.

[0226] 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 (optionally implemented 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.

[0227] Generally, application server 1530 can be a component that provides IP bearer resources for 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.).

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

[0229] 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 (S1-U) interface 1514, which carries traffic data between RAN node 1511 and S-GW; and S1-MME interface 1515, which is the signaling interface between RAN node 1511 and MME.

[0230] Additional Examples

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

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

[0233] Example 1 is a method for use with a user equipment (UE), the method comprising: acquiring downlink control information (DCI) configured for multi-physical downlink shared channel (PDSCH) scheduling; determining whether to enable codebook group (CBG) based on the number of PDSCHs scheduled by the DCI; and determining the format of the DCI based on the number of PDSCHs scheduled by the DCI.

[0234] Example 2 is the method according to Example 1, the method further comprising: interpreting the format of the DCI after acquiring the DCI, wherein interpreting the DCI format includes: determining the number C of scheduled PDSCHs, the number of scheduled PDSCHs being indicated by the Time Domain Resource Allocation (TDRA) field in the acquired DCI.

[0235] Example 3 is based on the method described in Example 2, wherein determining whether to enable the CBG-based operation based on the DCI includes: setting the number C of scheduled PDSCHs against a threshold M. PDSCH,c The comparison is made based on the threshold, which represents the maximum number of PDSCHs for which the CBG-based operation is enabled for the serving cell; and if the number of scheduled PDSCHs C is greater than the threshold M. PDSCH,c If so, then the CBG-based operation will be disabled.

[0236] Example 4 is based on the method described in Example 3, wherein the number of scheduled PDSCHs C is greater than the threshold M. PDSCH,c Determining the format of the DCI in the following circumstances includes: the absence of a CBG Transmission Indicator (CBGTI) field in the DCI; and determining the bit width of each of the New Data Indicator (NDI) field and the Redundancy Version (RV) field in the DCI.

[0237] Example 5 is the method according to Example 4, wherein the bit width of each of the NDI field and the RV field is determined based on the maximum number of schedulable PDSCHs for the serving cell of the TDRA field of the DCI, and wherein each bit of the NDI field and the RV field corresponds to one of the scheduled PDSCHs.

[0238] Example 6 is the method according to Example 2, wherein determining whether to enable the CBG-based operation based on the DCI includes: setting the number C of scheduled PDSCHs against a threshold M. PDSCH,c The comparison is made using the threshold, which represents the maximum number of PDSCHs for which the CBG-based operation is enabled for the serving cell; if the number of scheduled PDSCHs C is equal to or less than the threshold M... PDSCH If so, then the CBG-based operation will be enabled.

[0239] Example 7 is the method according to Example 6, wherein the number C of scheduled PDSCHs is equal to or less than the threshold M. PDSCH In the case of the presence of a CBG Transmission Indicator (CBGTI) field in the DCI, the format of the DCI is determined by: the presence of a CBG Transmission Indicator (CBGTI) field in the DCI; and the bit width of each of the NDI field, RV field, and CBGTI in the DCI.

[0240] Example 8 is the method according to Example 7, wherein the bit width of the NDI field is equal to the threshold M. PDSCH,c The value; the bit width of the RV field is equal to the threshold M. PDSCH,c The value is multiplied by a predetermined coefficient K, which takes the value of 1 or 2; and the bit size of the CBGTI field is equal to the threshold M. PDSCH,c The value multiplied by the maximum number N of these CBGs per transport block. c And each bit of the NDI field and each K bits of the RV field correspond to one of the scheduled PDSCHs with CBG-based operation enabled, and the CBGTI field includes subfields each corresponding to one of the scheduled PDSCHs with CBG-based operation enabled.

[0241] Example 9 is the method according to Example 8, wherein the NDI field, the RV field, and the CBGTI field are concatenated to each other, and when CBG-based operations are disabled, a zero-padding operation is applied to the concatenated fields to align their sizes.

[0242] Example 10 is the method according to any one of Examples 3-9, wherein the threshold M PDSCH,c Provided via Radio Resource Control (RRC) signaling on a per-component carrier (CC) basis.

[0243] Example 11 is the method according to any one of Examples 3-9, wherein the UE sets the threshold M PDSCH,c Let the value be 1.

[0244] Example 12 is the method according to any one of Examples 3-9, wherein the threshold M PDSCH,c It is based on the maximum number S of SLIVs that can be indicated by the TDRA field of the DCI. c Divide by the maximum number N of these CBGs per transport block c It's confirmed.

[0245] Example 13 is a method for a User Equipment (UE), the method comprising: acquiring downlink control information (DCI), wherein the DCI includes a Time Domain Resource Allocation (TDRA) field and the value of the TDRA field provides a row index to an allocation table containing rows each having one or more start and length indication values ​​(SLIV); determining a subcodebook association of Hybrid Automatic Repeat Request (HARQ) Acknowledgment (HARQ-ACK) information bits based on the acquired DCI; and generating HARQ-ACK information bits based on the associated HARQ-ACK subcodebook.

[0246] Example 14 is the method according to Example 13, wherein determining the subcodebook association of these HARQ-ACK information bits includes generating a first subcodebook including HARQ-ACK bits for one of the following DCIs: a DCI for scheduling PDSCH on a CC without configured codebook group (CBG) operation and configured with a TDRA table, each row in the TDRA table having a single SLIV; a DCI for scheduling PDSCH on a CC without configured CBG operation and configured with a TDRA table, at least one row in the TDRA table having multiple SLIVs, and the DCI scheduling a single PDSCH; a DCI for semi-persistent scheduling (SPS) physical downlink shared channel (PDSCH) release; and a DCI for secondary cell (SCell) sleep indication in the absence of scheduled PDSCH.

[0247] Example 15 is the method according to Example 14, wherein determining the subcodebook association of the HARQ-ACK information bit includes generating a second subcodebook including the HARQ-ACK bit for one of the following DCIs: a DCI for scheduling PDSCH on a CC configured with the TDRA table, wherein at least one row in the TDRA table has multiple SLIVs, and the DCI schedules multiple PDSCHs; and a DCI for scheduling PDSCH on a CC configured with CBG-based operations and configured with the TDRA table, wherein at least one row in the TDRA table has multiple SLIVs, or each of the rows has a single SLIV.

[0248] Example 16 is the method according to Example 15, wherein generating HARQ-ACK feedback bits for the second subcodebook based on the subcodebook association further includes: generating HARQ-ACK bits for the CBG if the CBG operation is enabled; and generating HARQ-ACK bits for the transport blocks in the PDSCH if the CBG operation is disabled.

[0249] Example 17 is the method according to Example 16, wherein generating the HARQ-ACK bit for the second subcodebook further includes: generating padding HARQ-ACK bits for the second subcodebook, the generation including: determining the first parameter of these padding HARQ-ACK bits. in Where S max =max{S c And N max =max{M PDSCH,c *N c}, and where S cThis indicates the maximum number of SLIVs configured for a serving cell with multiple PDSCH scheduling operations; N c This indicates the maximum number of these CBGs per transport block for the serving cell configured with this CBG operation; and M PDSCH,c The threshold is defined as the maximum number of PDSCHs that enable CBG-based operations for the serving cell; the second parameter K is used to determine these HARQ-ACK bits. C K C When the CBG operation is enabled, this represents the actual number of CBGs scheduled; and when the multi-PDSCH scheduling is configured for the serving cell and the CBG operation is disabled, this represents the actual number of PDSCHs scheduled; and the last... These bits are determined to be the padding HARQ-ACK bits.

[0250] Example 18 is the method according to Example 17, wherein generating padding HARQ-ACK bits for the second subcodebook further includes: generating a negative acknowledgment (NACK) for each of the padding HARQ-ACK bits; or taking the first... These bits are used as padding HARQ-ACK bits for retransmission.

[0251] Example 19 is the method according to Example 14, wherein determining the subcodebook association of these HARQ-ACK information bits further includes generating a second subcodebook including HARQ-ACK bits for one of the following DCIs: a DCI for scheduling PDSCHs on a CC that is not configured with the CBG-based operation and has the TDRA table configured, wherein at least one row in the TDRA table has multiple SLIVs, and the DCI schedules multiple PDSCHs; and a DCI for scheduling PDSCHs on a CC that is configured with the CBG-based operation and has the TDRA table configured, wherein at least one row has multiple SLIVs, and the number of PDSCHs scheduled by the DCI is greater than a threshold M. PDSCH,c The threshold is defined as the maximum number of these PDSCHs that enable the CBG-based operation.

[0252] Example 20 is based on the method of Example 19, wherein determining the subcodebook association of these HARQ-ACK information bits further includes generating a third subcodebook including HARQ-ACK bits for one of the following DCIs: a DCI for scheduling PDSCHs on a CC configured with CBG-based operations and a TDRA table, each row in the TDRA table having a single SLIV; and a DCI for scheduling PDSCHs on a CC configured with CBG-based operations and the TDRA table, at least one row in the TDRA table having multiple SLIVs, and the number of PDSCHs scheduled by the DCI being equal to or less than the threshold M. PDSCH,c The threshold is defined as the maximum number of these PDSCHs that enable the CBG-based operation.

[0253] Example 21 is the method according to Example 20, wherein generating these HARQ-ACK feedback information bits based on the sub-codebook association includes determining the number of these HARQ-ACK bits for the first sub-codebook, the second sub-codebook, and the third sub-codebook, the determination including: determining a first size of the first sub-codebook as... in This represents the value of the Total Downlink Assignment Indicator (T-DAI) used for the first subcodebook, and K is 2 if the UE is configured to receive two transport blocks in at least one configured downlink (DL) bandwidth portion (BWP), and 1 otherwise; the second size of the second subcodebook is determined as follows. Where S max =max{S c},in This represents the value of T-DAI used in the second subcodebook, and S c This indicates the maximum number of these SLIVs configured for a serving cell with multiple PDSCH scheduling; and the third size of this third subcodebook is determined as... in This represents the value of T-DAI in the third subcodebook; M PDSCH,c This represents a threshold, indicating the maximum number of PDSCHs for which CBG-based operations are enabled for the serving cell; and N c This indicates the maximum number of these CBGs per transport block for the serving cell where this CBG operation is enabled.

[0254] Example 22 is the method according to Example 21, wherein generating these HARQ-ACK feedback bits based on the subcodebook further includes: sequentially concatenating the HARQ-ACK bits of the first subcodebook, the second subcodebook, and the third subcodebook based on the index of the subcodebook; and transmitting the concatenated HARQ-ACK bits through the Physical Uplink Control Channel (PUCCH) or the Physical Uplink Shared Channel (PUSCH).

[0255] Example 23 is the method according to any one of Examples 14 to 22, wherein the counter downlink assignment indicator (C-DAI) and the total downlink assignment indicator (T-DAI) are counted independently within the respective subcodebook.

[0256] Example 24 is the method according to Example 22, the method further comprising: obtaining a DCI associated with DCI format 0_1, wherein the format of the DCI includes one or two 2-bit extension fields to indicate the T-DAI value of the third subcodebook, wherein the 2-bit extension field is added to a second DAI field within the T-DAI field.

[0257] Example 25 is a method for a base station, the method comprising: generating downlink control information (DCI) for a user equipment (UE) for scheduling multiple physical downlink shared channels (PDSCH), wherein a time domain resource allocation (TDRA) field of the DCI indicates the number of PDSCHs scheduled; and providing the DCI so that the UE determines, based on the TDRA field of the DCI, whether to enable codebook group (CBG) based operation.

[0258] Example 26 is the method according to Example 25, the method further comprising: configuring a threshold M PDSCH,c This threshold indicates the maximum number of PDSCHs for which CBG-based operation is enabled for the serving cell; and this threshold M is provided via Radio Resource Control (RRC) signaling. PDSCH,c So that the UE can use the TDRA field of the DCI and the threshold M to... PDSCH,c Determine whether to enable this CBG-based operation.

[0259] Example 27 is a method for a base station, the method comprising: generating downlink control information (DCI), wherein the format of the DCI includes a time-domain resource allocation (TDRA) field, and the value of the TDRA field provides a row index to an allocation table containing rows each having one or more start and length indication values ​​(SLIV); and transmitting the DCI for a user equipment (UE) to determine a subcodebook association of Hybrid Automatic Repeat Request (HARQ) Acknowledgment (HARQ-ACK) information bit feedback.

[0260] Example 28 is the method according to Example 27, further comprising: obtaining a first HARQ-ACK subcodebook from the UE, wherein the first HARQ-ACK subcodebook is generated for the following DCIs: the DCI is used to schedule PDSCH on a CC that is not configured with codebook group (CBG) based operations and is configured with a TDRA table, each of the rows in the TDRA table having a single SLIV; the DCI is used to schedule PDSCH on a CC that is not configured with CBG based operations and is configured with the TDRA table, at least one of the rows in the TDRA table having multiple SLIVs, and the DCI scheduling a single PDSCH; the DCI is used for semi-persistent scheduling (SPS) physical downlink shared channel (PDSCH) release; and the DCI is used for secondary cell (SCell) sleep indication in the absence of scheduled PDSCH.

[0261] Example 29 is the method according to Example 28, the method further comprising: obtaining a second HARQ-ACK subcodebook from the UE, wherein the second HARQ-ACK subcodebook is generated for one of the following DCIs: the DCI is used to schedule PDSCH on a CC configured with the TDRA table, at least one row in the TDRA table having multiple SLIVs, and the DCI schedules multiple PDSCHs; and the DCI is used to schedule PDSCH on a CC configured with CBG-based operation and configured with the TDRA table, at least one row in the TDRA table having multiple SLIVs, or each row having a single SLIV.

[0262] Example 30 is the method according to Example 28, further comprising: obtaining a second HARQ-ACK subcodebook from the UE, wherein the second HARQ-ACK subcodebook is generated for one of the following DCIs: a DCI for scheduling PDSCHs on a CC that is not configured with the CBG-based operation and has the TDRA table configured, wherein at least one row in the TDRA table has multiple SLIVs, and the DCI schedules multiple PDSCHs; and a DCI for scheduling PDSCHs on a CC that is configured with the CBG-based operation and has the TDRA table configured, wherein at least one row in the TDRA table has multiple SLIVs, and the number of PDSCHs scheduled by the DCI is greater than a threshold M. PDSCH,c The threshold is defined as the maximum number of these PDSCHs that enable the CBG-based operation.

[0263] Example 31 is the method according to Example 30, further comprising: obtaining a third HARQ-ACK subcodebook from the UE, wherein the third HARQ-ACK subcodebook is generated for one of the following DCIs: a DCI for scheduling PDSCHs on a CC configured with CBG-based operation and configured with the TDRA table, each of the rows in the TDRA table having a single SLIV; and a DCI for a CC configured with the CBG operation and configured with the TDRA table, at least one of the rows in the TDRA table having multiple SLIVs, and the number of PDSCHs scheduled by the DCI being equal to or less than the threshold M. PDSCH,c The threshold is defined as the maximum number of these PDSCHs that enable the CBG-based operation.

[0264] Example 32 is the method according to Example 31, the method further comprising: receiving from the UE the HARQ-ACK bits of the first HARQ-ACK subcodebook, the second HARQ-ACK subcodebook and the third HARQ-ACK subcodebook concatenated in sequence based on the index of the subcodebook.

[0265] Example 33 is a method of any one of Examples 28 to 32, wherein the counter downlink assignment indicator (C-DAI) and the total downlink assignment indicator (T-DAI) are counted independently within the corresponding subcodebook.

[0266] Example 34 is the method according to Example 32, the method further comprising: providing a DCI for the UE to schedule PUSCH, wherein the number of concatenated HARQ-ACKs and the number of PDSCHs scheduled by the DCI subcodebook are multiples of the number of PDSCHs scheduled by the DCI, wherein the DCI includes one or two 2-bit T-DAI fields to indicate the size of the third subcodebook.

[0267] 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-24.

[0268] 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 25-34.

[0269] Example 37 is a computer-readable medium having a computer program stored thereon, which, when executed by one or more processors, causes a device to perform the method according to any one of claims 1-34.

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

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

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

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

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

[0275] 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 the invention. It should be noted that many alternative ways exist to implement both the processes and apparatus described herein. Therefore, embodiments of the invention 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 user equipment (UE), comprising: receiving circuitry to obtain a downlink control information (DCI), wherein the DCI includes a time domain resource allocation (TDRA) field, and a value of the TDRA field provides a row index to an allocation table containing rows, where each row has one or more start and length indicator values (SLIVs); and control circuitry coupled with the receiving circuitry to: determine a sub-codebook association of hybrid automatic repeat request (HARQ) acknowledgement (HARQ-ACK) information bits based on the obtained DCI; and generate the HARQ-ACK information bits based on the sub-codebook association, where, to determine the sub-codebook association of the HARQ-ACK information bits, the control circuitry generates a first sub-codebook to include HARQ-ACK bits for: a DCI scheduling a PDSCH on a component carrier (CC) not configured with codebook group (CBG) based operation and configured with a TDRA table, where each of the rows in the TDRA table has a single SLIV; a DCI scheduling a PDSCH on a CC not configured with CBG based operation and configured with a TDRA table, where at least one of the rows in the TDRA table has multiple SLIVs, and a single PDSCH is scheduled by the DCI; a DCI for a semi-persistent scheduling (SPS) physical downlink shared channel (PDSCH) release; or a DCI for a secondary cell (SCell) dormancy indication without a scheduled PDSCH.

2. The UE of claim 1, wherein, To determine the sub-codebook association of the HARQ-ACK information bits, the control circuitry generates a second sub-codebook to include HARQ-ACK bits for: a DCI scheduling a PDSCH on a CC configured with the TDRA table, where at least one of the rows in the TDRA table has multiple SLIVs, and multiple PDSCHs are scheduled by the DCI; or a DCI scheduling a PDSCH on a CC configured with CBG based operation and configured with the TDRA table, where at least one of the rows in the TDRA table has multiple SLIVs or each of the rows has a single SLIV.

3. The UE of claim 2, wherein, To generate the second sub-codebook to include the HARQ-ACK bits, the control circuitry is further to: generate HARQ-ACK bits for CBGs if the CBG operation is enabled; and generate HARQ-ACK bits for transport blocks in PDSCHs if the CBG operation is disabled.

4. The UE of claim 3, wherein the control circuitry is to generate padded HARQ-ACK bits for the second sub-codebook by: determining a first parameter to fill HARQ-ACK bits wherein = wherein and and wherein S c represents a maximum number of SLIVs configured for a serving cell configured with multiple PDSCH scheduling operations; N c represents a maximum number of CBGs per transport block for the serving cell configured with the CBG operation; and M PDSCH,c represents a threshold defined as a maximum number of PDSCHs for which CBG-based operation is enabled for the serving cell; determining a second parameter of the padding HARQ-ACK bits K C wherein K C denotes the number of actually scheduled CBGs in case the CBG operation is enabled and the number of actually scheduled PDSCHs in case multi-PDSCH scheduling is configured for the serving cell and the CBG operation is disabled; and The last bit is determined as the padding HARQ-ACK bit.

5. The UE of claim 4, wherein, To generate padded HARQ-ACK bits for the second sub-codebook, the control circuitry is further to: generate a negative acknowledgement (NACK) for each of the padded HARQ-ACK bits; or generate a NACK for each of the padded HARQ-ACK bits. The first bits are repeated as the padding HARQ-ACK bits.

6. The UE of claim 1, wherein, To determine the sub-codebook association of the HARQ-ACK information bits, the control circuit is further to generate a second sub-codebook to include HARQ-ACK bits for: DCI scheduling PDSCH on a CC not configured with the CBG-based operation and configured with the TDRA table, at least one of the rows in the TDRA table has multiple SLIVs, and multiple PDSCHs are scheduled by the DCI; or A DCI for scheduling a PDSCH on a CC configured with CBG-based operation and configured with the TDRA table, at least one row of the TDRA table has multiple SLIVs, and the number of the PDSCH transmissions is greater than a threshold M PDSCH,c , the threshold M PDSCH,c defined as the maximum number of the PDSCHs enabled with the CBG-based operation.

7. The UE of claim 6, wherein, To determine the sub-codebook association of the HARQ-ACK information bits, the control circuit is further to generate a third sub-codebook to include HARQ-ACK bits for: DCI scheduling PDSCH on a CC configured with CBG-based operation and configured with a TDRA table, each of the rows in the TDRA table has a single SLIV; or DCI for scheduling PDSCH on a CC configured with CBG-based operation and configured with the TDRA table, at least one of the rows in the TDRA table has multiple SLIVs, and the number of the PDSCH transmissions is equal to or less than the threshold M PDSCH,c .

8. The UE of claim 7, wherein, To determine the sub-codebook association of the HARQ-ACK information bits, the control circuit determines the number of HARQ-ACK bits of the first, second, and third sub-codebooks by: a first size of the first sub-codebook is determined as , wherein represents a value of a total downlink assignment indicator (T-DAI) for the first sub-codebook, and K is taken as 2 in case the UE is configured to receive two transport blocks in at least one configured downlink (DL) bandwidth part (BWP), and is taken as 1 otherwise. determining a second size of the second sub-codebook as wherein wherein denotes a value for the T-DAI of the second sub-codebook, and S c denotes a maximum number of the SLIVs configured for a serving cell configured with multi-PDSCH scheduling; and determining a third size of the third sub-codebook as wherein denotes a value of the T-DAI of the third sub-codebook; M PDSCH,c denotes a threshold value indicating a maximum number of PDSCHs for a serving cell for which the CBG-based operation is enabled; and N c denotes a maximum number of CBGs per transport block for the serving cell for which the CBG operation is enabled.

9. The UE of claim 8, wherein, To determine the sub-codebook association of the HARQ-ACK information bits, the control circuit is further to: concatenate the HARQ-ACK bits of the first, second, and third sub-codebooks in order based on an index of the sub-codebooks; and transmit the concatenated HARQ-ACK bits over a physical uplink control channel (PUCCH) or a physical uplink shared channel (PUSCH).

10. The UE of any one of claims 1-9, wherein a counter downlink assignment indicator (C-DAI) and a total downlink assignment indicator (T-DAI) are counted independently within the respective sub-codebooks.

11. The UE of claim 9, wherein the DCI is associated with a DCI format 0 1, wherein a format of the DCI includes one or two 2-bit extension fields to indicate the T-DAI value of the third sub-codebook, wherein the 2-bit extension fields are added to a second DAI field within the T-DAI field.

12. A method for wireless communication performed by one or more processors of a base station, the method comprising: generating downlink control information (DCI), wherein a format of the DCI includes a time domain resource allocation (TDRA) field, and a value of the TDRA field provides row indices for an allocation table containing rows, wherein individual rows have one or more starting and length indication values (SLIVs); and transmitting the DCI for a user equipment (UE) to determine a sub-codebook association of hybrid automatic repeat request (HARQ) acknowledgement (HARQ-ACK) information bits feedback, wherein the method further comprises obtaining a first HARQ-ACK sub-codebook from the UE, wherein the first HARQ-ACK sub-codebook is generated for one or more of the following DCIs: A DCI for scheduling PDSCH on a CC not configured with codebook group (CBG) based operation and configured with a TDRA table in which each of the rows has a single SLIV; A DCI for scheduling PDSCH on a CC not configured with CBG based operation and configured with a TDRA table in which at least one of the rows has multiple SLIVs, and a single PDSCH is scheduled by the DCI; A DCI for semi-persistent scheduling (SPS) physical downlink shared channel (PDSCH) release; and A DCI for secondary cell (SCell) dormancy indication without a scheduled PDSCH.

13. The method of claim 12, further comprising: A second HARQ-ACK sub-codebook is obtained from the UE, wherein the second HARQ-ACK sub-codebook is generated for: A DCI for scheduling PDSCH on a CC configured with the TDRA table in which at least one of the rows has multiple SLIVs, and multiple PDSCHs are scheduled by the DCI; Or A DCI for scheduling PDSCH on a CC configured with CBG based operation and configured with the TDRA table in which at least one of the rows has multiple SLIVs, or each of the rows has a single SLIV.

14. The method of claim 12, further comprising: A second HARQ-ACK sub-codebook is obtained from the UE, wherein the second HARQ-ACK sub-codebook is generated for: A DCI for scheduling PDSCH on a CC not configured with the CBG based operation and configured with the TDRA table in which at least one of the rows has multiple SLIVs, and multiple PDSCHs are scheduled by the DCI; Or DCI for scheduling PDSCH on a CC configured with CBG-based operation and configured with the TDRA table, at least one of the rows in the TDRA table has multiple SLIVs, and the number of PDSCH transmissions is greater than a threshold M PDSCH,c , the threshold M PDSCH,c defined as the maximum number of PDSCHs enabled with the CBG-based operation.

15. The method of claim 14, further comprising: A third HARQ-ACK sub-codebook is obtained from the UE, wherein the third HARQ-ACK sub-codebook is generated for: A DCI for scheduling PDSCH on a CC configured with CBG based operation and configured with the TDRA table in which each of the rows has a single SLIV; and DCI for a CC configured with the CBG operation and configured with the TDRA table, at least one of the rows in the TDRA table has multiple SLIVs, and the number of PDSCH transmissions is equal to or less than the threshold M PDSCH,c , the threshold M PDSCH,c defined as the maximum number of PDSCHs enabled with the CBG-based operation.

16. The method of claim 15, further comprising: The HARQ-ACK bits of the first HARQ-ACK sub-codebook, the HARQ-ACK bits of the second HARQ-ACK sub-codebook, and the HARQ-ACK bits of the third HARQ-ACK sub-codebook are received from the UE in a sequential concatenation based on the sub-codebook index.

17. The method of any one of claims 12-16, wherein a counter downlink assignment indicator (C-DAI) and a total downlink assignment indicator (T-DAI) are counted independently within the respective sub-codebook.

18. The method of claim 16, wherein the DCI includes one or two 2-bit T-DAI fields to indicate the size of the third HARQ-ACK sub-codebook.

Images