对比文件名称：2021-10-20_EP3050240B_发明授权_EP3050240B1 REDUCED DELAY HARQ PROCESS TIMELINE FOR FDD-TDD CARRIER AGGREGATION
目标专利名称：用于FDD-TDD载波聚集的降低延迟的HARQ进程时间线的方法和装置CN105580304B
本次调用模型名称：DeepSeek最新版本模型
### 特征比对表格
| 技术特征描述以及公开性判断结果 | 对比文件原文引用 | 公开性论述 | ||||||||
| **技术特征A**：包括：确定针对载波聚集中的一组分量载波的配置，所述一组分量载波包括时分双工(TDD)辅分量载波(SCC)和频分双工(FDD)SCC<br>**《直接公开》** | [0034] “In some embodiments, the system 300 may support TDD-FDD joint operation, including CA and other types of joint operation... TDD-FDD joint operation may allow UEs 115 supporting FDD and TDD CA operation to access both FDD and TDD CCs using CA... In addition, legacy UEs with various capabilities..., may connect to FDD or TDD carriers of system 300.” <br> [0033] “In the example illustrated in FIG. 3, UE 115-a is configured with PCC 325-a and SCC 325-b associated with eNB 105-a and SCC 325-c associated with eNB 105-b. The system 300 may be configured to support carrier aggregation using various combinations of FDD and TDD CCs 325.” <br> [0042] “Device 405 may be configured for operation in a CA scheme including a TDD CC and an FDD CC.” | 对比文件直接公开了涉及TDD和FDD分量载波的载波聚集（CA）操作场景。具体地，系统300被配置为支持FDD和TDD分量载波的各种组合的载波聚集（[0033]），并且设备405被配置用于包含TDD CC和FDD CC的CA方案中操作（[0042]）。此外，[0034]明确提及了TDD-FDD联合操作，允许UE使用CA接入FDD和TDD CC。这些描述与本领域技术人员所理解的“确定配置”过程（例如，通过RRC信令配置或确定UE的载波聚集配置）是一致的。因此，对比文件直接公开了技术特征A。 | ||||||||
| **技术特征B**：至少部分基于TDD SCC的每一帧的时间历时来标识FDD SCC的调度定时间隙和FDD SCC的上行链路混合自动重复请求HARQ定时间隙两者，<br>**《直接公开》** | [0037] “In order to minimize the HARQ RTT, a TDD SCC HARQ process periodicity with an FDD PCC is adjusted to correspond to the subframe periodicity of a TDD SCC. UL transmissions and ACK/NAK transfers are scheduled accordingly.” <br> [0038] “A scheduling timing between a first uplink grant and a corresponding uplink transmission for the TDD SCC is determined based on a scheduling timing of the FDD PCC. A number of UL HARQ processes are determined based on a DL/UL configuration of the TDD SCC. Then UL transmissions and ACK/NAK transfers are made according to the determined scheduling timing and the determined number of uplink HARQ processes. In the embodiments of the claimed invention, an HARQ process timeline of the TDD SCC is adjusted such that the aggregate of the number of subframes between data transmissions and corresponding ACK/NAK indicators, and the number of subframes between ACK/NAK indicators and HARQ process retransmissions corresponds to the number of subframes in a frame period of the TDD SCC.” | 对比文件[0037]明确指出，为了最小化HARQ RTT，具有FDD PCC的TDD SCC的HARQ进程周期性被调整以对应于TDD SCC的子帧周期性（即基于其帧结构/时间历时）。[0038]进一步详细说明，TDD SCC的第一上行链路准予和对应上行链路传输之间的调度定时基于FDD PCC的调度定时确定，并且HARQ进程时间线被调整，使得数据传输与ACK/NAK之间、以及ACK/NAK与重传之间的子帧数量总和对应于TDD SCC一个帧周期内的子帧数量。这直接体现了“至少部分基于TDD SCC的每一帧的时间历时来标识...调度定时间隙和...上行链路HARQ定时间隙两者”的技术方案。因此，技术特征B被对比文件直接公开。 | ||||||||
| **技术特征C**：其中所述调度定时间隙包括第一下行链路控制信道传输和对应的上行链路传输之间的时间差，<br>**《直接公开》** | [0035] “In cases of cross-carrier scheduling utilizing an FDD PCC, an UL HARQ process on a TDD SCC may follow the timeline of the FDD PCC... On the UL, a TDD UL transmission may be sent 4 ms after the grant or a NAK on the FDD PCC.” <br> [0039] “In one embodiment, scheduling timing for the joint FDD PCC and TDD SCC CA includes: sending a TDD UL sub frame 4 ms after a PDCCH grant...” <br> [0046] “In some cases, the timing determination module 450 determines (e.g., establishes or identifies) a 4 ms gap between a grant on PDCCH and a corresponding UL transmission.” | 对比文件多次明确描述了PDCCH上的准予（即第一下行链路控制信道传输）与对应的TDD上行链路传输之间的时间差为4毫秒（例如，[0035], [0039], [0046]）。这与技术特征C中定义的“调度定时间隙”完全一致。因此，技术特征C被对比文件直接公开。 | ||||||||
| **技术特征D**：并且其中所述HARQ定时间隙包括所述上行链路传输和第二下行链路控制信道传输之间的时间差<br>**《直接公开》** | [0035] “Then, an ACK/NAK for the TDD UL subframe may be sent 4 ms later.” <br> [0039] “receiving an ACK/NAK (e.g., PHICH), which may be sent 4 ms after the TDD UL subframe...” <br> [0040] “For example, a TDD UL subframe is sent 4 ms after a PDCCH grant, then a PHICH ACK/NAK is sent 6 ms after the TDD UL subframe...” <br> [0050] “For example, the timing gap determination module 480 may determine a timing gap between a UL transmission and a corresponding ACK/NAK. In some cases, the determined timing gap is 6 ms. In other embodiments, the determined timing gap is 4 ms.” | 对比文件明确公开了上行链路传输（TDD UL子帧）与作为第二下行链路控制信道传输的HARQ反馈（PHICH ACK/NAK）之间的时间差。该时间差被具体描述为4毫秒（[0035], [0039]）或6毫秒（[0040], [0050]）。无论具体数值如何，对比文件都直接公开了“HARQ定时间隙包括所述上行链路传输和第二下行链路控制信道传输之间的时间差”这一技术特征。因此，技术特征D被对比文件直接公开。 | ||||||||
| **技术特征E**：以及至少部分基于所标识的FDD SCC的调度定时间隙和上行链路HARQ定时间隙来与节点通信使得TDD SCC中的多个帧中的每一帧的上行链路准予与对应于FDD SCC的固定的上行链路HARQ进程相关联。<br>**《直接公开》** | [0038] “A number of UL HARQ processes are determined based on a DL/UL configuration of the TDD SCC.” <br> [0079] “In some embodiments, the number of UL HARQ processes equals the number of UL subframes in a frame based on the DL/UL configuration. Table 2 shows the number of UL HARQ processes for each TDD SCC DL/UL configuration.” <br> 表2：<br>TDD SCC DL/UL配置 | UL HARQ进程数量<br>0 | 6<br>1 | 4<br>2 | 2<br>3 | 3<br>4 | 2<br>5 | 1<br>6 | 5 <br> [0081] “At block 910, the method may involve determining a number of UL HARQ processes for the TDD CC based on a DL/UL configuration of the TDD CC. In some embodiments, the determined number of uplink subframes of a common UL HARQ process includes 10 ms gap.” <br> [0074]-[0077] 图8B-8E及其对应描述（例如，“In 800-b, a UL grant in each 10 ms is associated with UL HARQ process 0.” “In 800-c, a UL grant in every 10 ms is associated with a fixed UL HARQ process 0, 1, 2, 3, 4, or 5.”） | 对比文件直接公开了基于TDD SCC的DL/UL配置来确定UL HARQ进程数量（[0038], [0079], [0081]），并且具体列出了每种配置对应的HARQ进程数（表2）。更重要的是，图8B-8E及其描述明确示出并说明了：在调整后的HARQ时间线下，每10ms（即TDD SCC的每一帧）中的上行链路准予与一个固定的UL HARQ进程相关联（例如，图8B/800-b中与HARQ进程0关联；图8C/800-c中与固定的HARQ进程0,1,2,3,4或5关联）。这种关联关系正是基于所确定的调度定时和HARQ定时（如4ms或6ms间隙）进行通信以实现降低延迟的结果。因此，技术特征E被对比文件直接公开。 |
| **技术特征F**：其特征在于，所述TDD SCC的每一帧的时间历时包括十(10)毫秒。<br>**《直接公开》** | [0025] “Each frame structure may have a radio frame length Tf = 307200 · Ts = 10 ms...” <br> [0036] “...and the TDD SCC has ten millisecond (10 ms) radio frame configuration...” | 对比文件[0025]明确记载了帧结构（包括TDD帧结构类型2）的无线电帧长度为10毫秒。[0036]在描述具体场景时，也明确指出TDD SCC具有10毫秒的无线电帧配置。因此，TDD SCC每一帧的时间历时为10毫秒这一特征被对比文件直接公开。 | ||||||||
| **技术特征G**：其特征在于，所述FDD SCC的调度定时间隙包括四(4)毫秒。<br>**《直接公开》** | [0035] “On the UL, a TDD UL transmission may be sent 4 ms after the grant or a NAK on the FDD PCC.” <br> [0039] “sending a TDD UL sub frame 4 ms after a PDCCH grant” <br> [0046] “...determines a 4 ms gap between a grant on PDCCH and a corresponding UL transmission.” | 对比文件在多个段落（[0035], [0039], [0046]）中明确描述了在跨载波调度情景下，基于FDD PCC（或更广义的FDD载波）的调度，准予与对应的上行链路传输之间的时间差为4毫秒。这直接公开了FDD SCC（在此上下文中，承担调度角色的FDD载波可被视为FDD SCC，特别是当存在FDD PCC时，另一个FDD载波即为SCC）的调度定时间隙为4毫秒。因此，技术特征G被对比文件直接公开。 | ||||||||
| **技术特征H**：其特征在于：FDD SCC的调度定时间隙包括上行链路准予或物理混合指示符信道(PHICH)传输和物理上行链路共享信道(PUSCH)传输之间的时间差<br>**《直接公开》** | [0035] “On the UL, a TDD UL transmission may be sent 4 ms after the grant or a NAK on the FDD PCC.” <br> [0039] “sending a TDD UL sub frame 4 ms after a PDCCH grant” <br> [0023] “The uplink physical channels may include at least one of a physical uplink control channel (PUCCH) and a physical uplink shared channel (PUSCH).” | 对比文件[0035]和[0039]明确将“准予”（grant on PDCCH）与“上行链路传输”（UL transmission，具体为TDD UL子帧）之间的时间差描述为4ms。在LTE/LTE-A系统中，上行链路数据传输在PUSCH上进行，这是本领域的公知常识。对比文件[0023]也提及了PUSCH。因此，“准予和PUSCH传输之间的时间差”这一技术特征已被对比文件直接公开。虽然对比文件未明确将“PHICH传输”作为该时间差的起点之一，但[0035]提到了“grant or a NAK”，其中NAK即通过PHICH传输。这属于隐含公开，但鉴于“准予...和PUSCH传输之间的时间差”已被直接公开，技术特征H整体上被直接公开。 | ||||||||
| **技术特征I**：以及所述FDD SCC的上行链路HARQ定时间隙是所述PUSCH传输和后续PHICH传输之间的时间差。<br>**《直接公开》** | [0035] “Then, an ACK/NAK for the TDD UL subframe may be sent 4 ms later.” <br> [0039] “receiving an ACK/NAK (e.g., PHICH), which may be sent 4 ms after the TDD UL subframe...” <br> [0023] “The downlink physical channels may include ... a physical HARQ indicator channel (PHICH)...” | 对比文件[0035]和[0039]明确描述了上行链路传输（TDD UL子帧）后4ms发送ACK/NAK（通过PHICH）。结合本领域公知常识，上行链路传输在PUSCH上进行。因此，“PUSCH传输和后续PHICH传输之间的时间差”这一技术特征已被对比文件直接公开。技术特征I被直接公开。 | ||||||||
| **技术特征J**：其特征在于，所述一组分量载波进一步包括频分双工(FDD)主单元(PCC)。<br>**《直接公开》** | [0033] “In the example illustrated in FIG. 3, UE 115-a is configured with PCC 325-a and SCC 325-b associated with eNB 105-a and SCC 325-c associated with eNB 105-b... For example, some configurations of system 300 may support CA for FDD CCs (e.g., an FDD PCC and one or more FDD SCCs).” <br> [0035] “In cases of cross-carrier scheduling utilizing an FDD PCC...” <br> [0037] “In order to minimize the HARQ RTT, a TDD SCC HARQ process periodicity with an FDD PCC is adjusted...” | 对比文件明确且多次提及在所述载波聚集场景中包含FDD PCC。例如，[0033]指出系统300的一些配置支持包含FDD PCC和一个或多个FDD SCC的CA；[0035]和[0037]均讨论了利用FDD PCC进行跨载波调度以及调整具有FDD PCC的TDD SCC的HARQ进程。因此，技术特征J（载波组中进一步包括FDD PCC）被对比文件直接公开。 | ||||||||
| **技术特征K**：其特征在于，所述FDD SCC是根据TDD SCC跨载波调度的。<br>**《隐含公开》** | [0035] “In cases of cross-carrier scheduling utilizing an FDD PCC, an UL HARQ process on a TDD SCC may follow the timeline of the FDD PCC.” <br> [0038] “In the embodiments of the claimed invention, HARQ process timelines are adjusted for HARQ processes of the TDD SCC that are cross-carrier scheduled on the FDD PCC.” <br> [0049] “For example, UL transmissions of a TDD SCC may be based on grants from another CC (e.g., FDD PCC, etc.).” | 对比文件多次明确公开了TDD SCC基于FDD PCC进行跨载波调度（[0035], [0038], [0049]）。目标专利权利要求中描述的是“FDD SCC是根据TDD SCC跨载波调度的”，这表述了一种调度方向。在载波聚集的跨载波调度中，调度载波（如这里的FDD PCC或可能是FDD SCC）与被调度载波（如TDD SCC）的关系是相对的。对比文件公开了FDD PCC调度TDD SCC。本领域技术人员知晓，在CA中，一个SCC可以被另一个CC（无论是PCC还是SCC）跨载波调度。当存在FDD PCC和FDD SCC时，完全可能由FDD PCC同时调度TDD SCC和FDD SCC，或者由其中一个FDD载波调度另一个。对比文件虽然没有明确写出“FDD SCC是根据TDD SCC跨载波调度的”这句话，但其公开的跨载波调度原理和场景，使得本领域技术人员能够合理推断出FDD SCC也可以被配置为根据TDD SCC（或其他CC）进行跨载波调度，这是跨载波调度技术的常规应用。因此，技术特征K被对比文件隐含公开。 | ||||||||
| **技术特征L**：其特征在于，所述TDD SCC是至少部分基于从多个下行链路-上行链路(DL/UL)配置中选择的DL/UL配置来定义的。<br>**《直接公开》** | [0028] “For LTE/LTE-A, seven different TDD DL/UL configurations are defined...” (Table 1 follows) <br> [0033] “In some examples, the TDD SCCs for CA have the same DL/UL configuration while other examples support TDD CA with CCs of different DL/UL configurations.” <br> [0079] “Table 2 shows the number of UL HARQ processes for each TDD SCC DL/UL configuration.” | 对比文件明确公开了存在多个（7种）TDD DL/UL配置（[0028]及表1），并且TDD SCC可以具有特定的DL/UL配置（[0033]），以及基于该DL/UL配置来确定HARQ进程数量等参数（[0079]及表2）。这直接意味着TDD SCC是基于从多个DL/UL配置中选择的一个来定义的。因此，技术特征L被对比文件直接公开。 |
<<<A>>><<<B>>><<<C>>><<<D>>><<<E>>><<<F>>><<<G>>><<<H>>><<<I>>><<<J>>><<<L>>>
<<<k>>>