DETAILED ACTION
The office action is in response to the amendments received on Aug. 3, 2026 after a final office action.
The RCE was received on Sept 2, 2026.
Claims 16, 18-21, 23-26, and 28-33 are pending in this application.
Information Disclosure Statement
The information disclosure statements (IDSs) submitted on Sept. 2, 2026, March 26, 2026, Sept. 15, 2023, and Sept. 6, 2023 have been considered by the examiner.
Notice of Pre-AIA or AIA Status
The present application, filed on or after March 16, 2013, is being examined under the first inventor to file provisions of the AIA .
Response to Arguments
Applicant’s Amendments and Arguments filed 08/03/2026 have been considered for examination. Claims 16, 18-21, 23-26, and 28-33are pending in this application.
With regard to the 112 (b) rejections, Applicant’s arguments filed 08/03/2026 in view of the amendment has been fully considered and is persuasive. Thus, the 112 (b) rejections have been withdrawn.
With regard to the 103 rejections, Applicant’s arguments filed 01/23/2026 (see pages 8-10 of Remarks) in view of the amendments have been fully considered but are not persuasive. Further, Examiner notes that Applicant’s amendments necessitated the new ground(s) of rejection presented in the instant Office Action.
Regarding claims 16, 21, and 26, Applicant argued:
Regarding the part of the amended claim 16, recited as “determine a demodulation reference signal (DMRS) configuration for the transmission, wherein the DMRS configuration comprises front-loaded DMRS symbols transmitted in association with the transmission,” combination of You and Su fails to disclose.
According to You, the TDRA table defines parameters like slot offset and number of repetitions, where setting Z=l deactivates TBoMS. (See paragraph [0307] of You). In other words, the wireless device processes time domain parameters to determine whether to activate TBoMS or use PUSCH repetition Type A, but fails to account for the part mentioned in the above. Further, Su does not remedy the deficiencies of You with respect to at least the feature. Thus, combination of You and Su fails to disclose this feature mentioned in the above.
Regarding new claims 31-33, recited as "wherein the DMRS configuration further comprises additional DMRS symbols transmitted in slots subsequent to a first slot of the number of slots (N) at symbol positions indicated by a DMRS additional position parameter," neither You nor SU teaches this feature.
You is directed to determining time domain parameters from a TDRA table and does not address the positioning of DMRS symbols across the slots of a TBoMS transmission, and Su does not remedy this deficiency. Thus, combination of You and Su fails to disclose the feature in new claims 31-33.
In response to Applicant’s argument, Examiner respectfully disagrees.
In the argument, Applicant argued that combination of You and Su do not teach or disclose the part of the amended claim 16 mentioned in the above. Also, the feature in new dependent claim 31-33 is failed to disclose by combination of You and Su. However, Examiner respectfully disagrees.
Regarding the part of the amended claim 16, recited as “determine a demodulation reference signal (DMRS) configuration … comprises front-loaded DMRS symbols transmitted in association with the transmission,” and newly added claims 31-33, recite as "wherein the DMRS configuration further comprises additional DMRS symbols … at symbol positions indicated by a DMRS additional position parameter," You, in Paragraphs [0402]- [0410] and [0413]-[0426], clearly teaches that the DMRS for PDSCH/PUSCH is composed of a front load DMRS (DMRS mentioned in the amended claim 16) and an additional DMRS (DMRS mentioned in new dependent claims 31-33).
For the configuration of front load DMRS symbols in the amended claim 16, as described in Paragraphs [0404]-[0408], You teaches that the transmission time resource location of the front load DM-RS is determined by various factors: First, it depends on the mapping type of the data channel (PDSCH mapping type/PUSCH mapping type) is type A or type B (slot-based or non-slot based), where the mapping type is set through RRC. Further, in the case of slot-based transmission, the transmission start OFDM symbol position of the front load DMRS is the 3rd or 4th OFDM symbol of the data transmission resource, and an indication of whether the transmission start OFDM symbol position is the third OFDM symbol or the fourth OFDM symbol is transmitted through the PBCH. Rather, the front load DMRS consists of one or two consecutive OFDM symbols, and whether the number of OFDM symbols is one or two is set through RRC. In addition, there are two types (either Type 1 or Type 2) of mapping types in the transmission OFDM symbol resource of the front load DMRS, and the type information to be applied is set to RRC. In the case of type 1, using the technique of F-CDM (CDM in frequency domain), T-CDM (CDM in time domain), and/or FDM, the DMRS symbol length is either 1 or 2, or 4 or 8. For Type 2, using the technique of F-CDM, T-CDM. and/or FDM. the DMRS symbol length is either 1 or 2, or 6 or 12. Namely, based on type of mapping, the front load DMRS symbol length is determined.
Regarding the additional DMRS symbols (described in the claims 31-33), You teaches that in Paragraphs [0409]-[0410], the number of addition DMRSs is determined among 0, 1, 2, 3. The maximum number of additional DMRSs to be transmitted is determined through RRC, and the number of additional DMRSs actually transmitted within each maximum number of DMRSs and the transmission OFDM symbol position are determined according to the length of the OFDM symbol through which data is transmitted. The number of OFDM symbols and the mapping type of each additional DMRS are determined to be the same as the number of OFDM symbols and the mapping type of the front load DMRS. As described in Paragraphs [0411]-[0417], in case of DMRS for PUSCH, as described above, it is divided into a front load DM-RS and an additional DMRS, and the number of additional DMRSs is determined among 0, 1, 2, or 3. The reference point of I (I indicates a symbol index in the time domain) and the position Io of the first DMRS symbol are dependent on the mapping type. For PUSCH mapping type A, if frequency hopping is deactivated, I is defined relative to the beginning of the slot, and if frequency hopping is activated, I is defined based on the start of each hop. Io is provided by the higher layer parameter dmrsTypeA-Position. For PUSCH mapping type B, I is defined for the start of the scheduled PUSCH resource when frequency hopping is deactivated and I is defined for the start of each hop when frequency hopping is activated. Io is 0. Further, the location(s) of the DMRS symbol is given by I and duration Id, where Id is a duration between the first OFDM symbol of a slot and the last OFDM symbol of a scheduled PUSCH resource in a slot for PUSCH mapping type A, or, Id is a duration of a PUSCH resource scheduled for PUSCH mapping type B, respectively, when intra-slot frequency hopping is not used. Further, as described in Paragraphs [0418]-[0419] and Table 8 and 9, when intra-slot frequency hopping is deactivated, a PUSCH DMRS position in a slot is configured by Table 8 for a single symbol DMRS and/or by Table 9 for the dual symbol DMRS. Further, as described in [0420]-[0425], when PUSCH TB (Transport Block) is mapped on multiple slots and symbol resources used for PUSCH TB mapping are different between slots, in each slot, the position and number of DMRS (Including front loaded DMRS and addition DMRS) transmission symbols are determined by UE based on the 'reference position for I' and the 'duration Id’ in each transmission slot. In this case, the position and the number of DMRS transmission symbols are either different for each slot (Method 1) or same for each slot (Method 2). Based on this, the DMRS configuration comprises additional DMRS symbols transmitted in slots subsequent to a first slot of the number of slots (N) at symbol positions indicated by a DMRS additional position parameter in Table 8 or 9.
Thus, by this reasoning, the part of the amended claim 16 and the new dependent claims 31-33 are disclosed by combination of You and Su.
However, since the amended claims 16, 21, and 26 have changed the scope of the previous claims due to the amendment and the new dependent claims 31-33 are added, the new rejection is presented in this instant office action in the below based on this.
Continued Examination Under 37 CFR 1.114
A request for continued examination under 37 CFR 1.114, including the fee set forth in 37 CFR 1.17(e), was filed in this application after final rejection. Since this application is eligible for continued examination under 37 CFR 1.114, and the fee set forth in 37 CFR 1.17(e) has been timely paid, the finality of the previous Office action has been withdrawn pursuant to 37 CFR 1.114. Applicant's submission filed on 09/02/2026 has been entered.
Claim Rejections - 35 USC § 103
The following is a quotation of 35 U.S.C. 103 which forms the basis for all obviousness rejections set forth in this Office action:
A patent for a claimed invention may not be obtained, notwithstanding that the claimed invention is not identically disclosed as set forth in section 102, if the differences between the claimed invention and the prior art are such that the claimed invention as a whole would have been obvious before the effective filing date of the claimed invention to a person having ordinary skill in the art to which the claimed invention pertains. Patentability shall not be negated by the manner in which the invention was made.
Claims 16, 18-21, 23-26, and 28-33 are rejected under U.S.C. 103 as being unpatentable over Hyangsun You and et. al (USPub. No.: US 20230047006 A1, hereinafter “You”) in a view of Ling Su and et. al (Int. Pub. No.: WO 2022154738 A1, hereinafter “Su”).
Regarding claim 16, You teaches an apparatus comprising: memory to store configuration information that includes a shared time domain resource allocation (TDRA) list associated with transport block over multiple slot (TBoMS) processing; and processing circuitry, coupled with the memory, to: retrieve the configuration information from the memory, (You, in Fig. 25 and in Paragraphs [0458]-[0460], teaches that Fig. 25 illustrates the structure of a wireless device such as Base station or UE to transmit/receive wireless signals. The processor of the device may store information obtained from signal processing of the second information/signal in the memory 104. The memory 104 may be connected to the processor 102 and may store various pieces of information related to the operation of the processor 102. The information may include the configuration information to transmit/receive wireless signal. The processor 102 and the memory 104 may be part of a communication modem/circuit/chip designed to implement a radio communication technology (e.g., LTE or NR). Here, one of the configuration information can be the TDRA list or table for TBoMS processing (transmission), as described in Table 6 (TDRA table) and in Paragraphs [0279]-[0281]. Further, the processor 102 may process information in the memory 104 to generate first information/signal and may then transmit a radio signal including the first information/ signal through the transceiver 106. In this process, the processor may retrieve the configuration information such as the parameters on TDRA table (Table 6) to perform TBoMS transmissions described in Paragraph [0281]. Therefore, it is clear that an apparatus (wireless device) may comprise a processing circuitry coupled with a memory where the processor may store or retrieve the configuration information such as TDRA list (table) for TBoMS transmission.) wherein the TDRA list includes an entry having an indication of a scheduling delay (k2) a number of repetitions (M), and a number of slots (N) for a transmission; and (You, in Paragraphs [0279]-[0281] and in Table 6, teaches that Table 6 show the example of TDRA table (lists) for TBoMS transmissions. The table may define slot offset K2 (it can be corresponding to the scheduling delay K2 and it is explained in Paragraph [0157]), start and length indicator SLIV (or direct start symbol S and allocation length L), PUSCH mapping type, the number of repetitions, K (it is corresponding to M in the claim 17 in the below), to be applied to PUSCH transmission, may be defined. Further, the number of slots for one TBoMS transmission, Z (it is corresponding to N) is also defined. Therefore, it is clear that the TDRA list (table) includes an entry having an indication of a scheduling delay (k2) and number of slots (N) for a TBoMS transmission.) determine a transmission procedure based on the entry, wherein if the number of slots (N) is greater than 1, a TBoMS procedure is applied where the number of slots (N) is used for transport block size (TBS) determination, and wherein if the number of slots (N) is 1 or absent, a physical uplink shared channel (PUSCH) repetition Type A procedure is applied where a number of slots used for TBS determination is equal to 1; (You, in Fig. 9, in Table 6, and in Paragraphs [0135], [0279], [0280], [0307], and [0319], teaches that as described in Table 6 and Paragraphs [0279] and [0280], the value of the number of slot, Z (it is corresponding to N in the claim), is indicated through the TDRA field existing in DCI. The TDRA field value m of DCI provides the row index m+1 in the allocation table as shown in Table 6. Values corresponding to a specific row index of the TDRA table are applied for PUSCH transmission of the UE. In the past, values of {PUSCH mapping type, K2, SLIV (Sand L), K} were indicated through the TDRA table/field. Note that when the value of Z corresponding to the row index of the TDRA table does not exist 9if not set), the value of Z is assumed to be 1. You also teaches other indication methods for Z is described in Paragraphs [0282]-[0284]. In Paragraphs [0307] and [0319], You teaches when the Z value, which is the number of slots constituting the TBoMS, is set by the DCI as explained in the above, the UE determines activation/deactivation of the TBoMS by using the Z value. The UE determines that TBoMS transmission is activated when the set value of Z is 2 or more and the value of Z is the number of slots constituting the TBoMS. When the set value of Z is 1 or absent (as mention for the table), it is determined that TBoMS transmission is deactivated and the repetition is applied for PUSCH transmission. Here, since the PUSCH transmission uses a slot-based PUSCH repetition, the PUSCH repletion is used Type A as described in Fig. 9 and in Paragraphs [0135]. The PUSCH Type A repetition is performed with the same PUSCH transmission start symbol position and PUSCH transmission symbol length for each slot. Further, as described in Paragraphs [0007], [0428]-[0430], and [0464] and in Equation 7, TBS (Transport Block Size) is determined based on the number of resource elements (REs) allocated for the first PUSCH (NRE), the NRE is a value obtained by multiplying all of i) a number of the plurality of slots (Z) ii) a smaller one between a predetermined fixed value and a number of resource elements allocated for PUSCH within a physical resource block (NRE) and iii) a number of allocated physical resource blocks for the UE (nPRB). Thus, when Z (corresponding to N) ≥ 2, TBoMS procedure is applied for transmission and when Z = 1 or absent, TBoMS procedure is deactivated for transmission and instead, PUSCH transmission procedure is applied for transmission by using PUSCH type A repetition, where the TBS is determined by using Z.) determine a demodulation reference signal (DMRS) configuration for the transmission, wherein the DMRS configuration comprises front-loaded DMRS symbols transmitted in association with the transmission; and (You, in Paragraphs [0402]- [0408], teaches that the DMRS for PDSCH/PUSCH is composed of a front load DMRS and an additional DMRS. For the configuration of front load DMRS symbols in the amended claim 16, as described in Paragraphs [0404]-[0408], You teaches that the transmission time resource location of the front load DM-RS is determined by various factors: First, it depends on the mapping type of the data channel (PDSCH mapping type/PUSCH mapping type) is type A or type B (slot-based or non-slot based), where the mapping type is set through RRC. Further, in the case of slot-based transmission, the transmission start OFDM symbol position of the front load DMRS is the 3rd or 4th OFDM symbol of the data transmission resource, and an indication of whether the transmission start OFDM symbol position is the third OFDM symbol or the fourth OFDM symbol is transmitted through the PBCH. Rather, the front load DMRS consists of one or two consecutive OFDM symbols, and whether the number of OFDM symbols is one or two is set through RRC. In addition, there are two types (either Type 1 or Type 2) of mapping types in the transmission OFDM symbol resource of the front load DMRS, and the type information to be applied is set to RRC. In the case of type 1, using the technique of F-CDM (CDM in frequency domain), T-CDM (CDM in time domain), and/or FDM, the DMRS symbol length is either 1 or 2, or 4 or 8. For Type 2, using the technique of F-CDM, T-CDM. and/or FDM. the DMRS symbol length is either 1 or 2, or 6 or 12. Namely, based on type of mapping, the front load DMRS symbol length is determined. The configuration of DMRS for transmission include front loaded DMRS and additional DMRS, where the front loaded DMRS is configured based on the type of mapping and further the configuration of additional DMRS will be described for the dependent claims 31-33 in the below.)
However, You does not explicitly teach that encode a message for transmission to a user equipment (UE) that includes the configuration information and the DMRS configuration
Su teaches that encode a message for transmission to a user equipment (UE) that includes the configuration information and the DMRS configuration (Su, in Lines 1-9 in Page 20, teaches that there are three cases for scheduling PUSCH transmission, including UL grant in a DCI (Downlink Control Information), configured grant Type 1 and configured Type 2. They use different ways to indicate parameters in TDRA. A group of parameters indicates the value of K2, SLIV and mapping type at the same time, and groups of parameters compose the TDRA list in the RRC signaling or the default PUSCH TDRA Table. Then, time domain resource assignment in DCI field or timeDomainAllocation in RRC indicates the index of the TDRA list or the row of default PUSCH TDRA Table. In Lines 1-8 in Page 52 and Table 3.5-1 in Page 51, the TDRA table configuration is shown in Table 3.5-1 and one more parameter N (number of slots) can be indicated the number of slots of one TBoMS transmission (as indicated by Z or N in the above). The N can be added to the TDRA table and jointly encoded with TDRA field in DCI. Since DCI is the configuration message for UE to configure the uplink transmission, it is encoded (including TDRA field) and transmitted to the UE. Further, in Page 39, Lines 4-13 and Lines 32-35 and in Page 40, Lines 1-20, the DMRS configuration is made based on the PUSCH mapping type by using the parameters in RRC or DCI (as explained in the above). Therefore, the configuration message such as RRC/DCI (including TDRA lists) is encoded and transmitted to the UE.
It would have been obvious for one of ordinary skill in the art, before the effective filing date of the claimed invention, to combine You and Su to include the technique of encode a message for transmission to a user equipment (UE) that includes the configuration information and the DMRS configuration of Su in the system of You to provide network devices, terminal devices and methods therein, enabling TB (Transport Block) transmission over multiple slots, to improve the performance of a PUSCH transmission. (Su, see Lines 18-19 and Lines 29-30 in Page 1).).
Regarding claim 18, combination of You and Su teaches the features defined in the claim 17, -refer to the indicated claim for reference(s).
You further teaches that wherein N = 1 in the entry to indicate M is to be re- interpreted and applied by the UE for a single-slot physical uplink shared channel (PUSCH) transmission (You, in Fig. 11 and in Paragraphs [0185]-[0186], teaches that one TBoMS transmission is performed through a transmission occasion composed of Z (it is corresponding to N) slot resources, and this TBoMS transmission is repeatedly transmitted through K (it is corresponding to M) transmission occasions, as explained in Fig. 11 and in Paragraph [0185]. As explained in Paragraph [0245], K (the number of repetition, corresponding to M) include K=1 case, namely, no repetition. Further, in Paragraphs [0305]-[0307], TBoMS transmission may be dynamically activated/deactivated (enabling/disabling). When TBoMS transmission is deactivated, conventional PUSCH transmission is performed, and when TBoMS transmission is activated, TBoMS transmission can be performed. TBoMS transmission may be activated/deactivated through an explicit field of DCI. Alternatively, when the Z value (corresponding to N), which is the number of slots constituting the TBoMS, is set by the DCI, the UE may determine activation/deactivation of the TBoMS by using the Z value. The UE may determine that TBoMS transmission is activated when the set value of Z is 2 or more and the value of Z is the number of slots constituting the TBoMS. When the set value of Z is 1, it can be determined that TBoMS transmission is deactivated. As explained in Paragraph [0280], it is implemented that when the value of Z corresponding to the row index of the TDRA table does not exit (if not set) the value of Z may be assumed to be 1. In Paragraph [0319], further explained, if the value of Z is set to 1 or all transmission occasions constituting TBoMS transmission consist of one slot, the UE determines that TBoMS transmission is not applied (deactivated) and repetition is applied for PUSCH transmission. Based on this observation, by setting Z (N)=1, TBoMS can be deactivated and a normal single-slot PUSCH transmission is performed or when Z (N) =1, if K (M) = 1 (no repetition) (it is supported as mentioned earlier) is set, the single-slot PUSCH transmission can be performed or if K >1 and Z =1, the normal repetitions in normal PUSCH transmission can be performed. Therefore, it is clear that N = 1 in the entry to indicate M is to be re- interpreted and applied by the UE for a single-slot physical uplink shared channel (PUSCH) transmission.)
Regarding claim 19, combination of You and Su teaches the features defined in the claim 18, -refer to the indicated claim for reference(s).
You teaches that wherein the entry further includes an indication that M is to be re-interpreted and applied by the UE for a single-slot physical uplink shared channel (PUSCH) transmission with repetitions (You, in Fig. 11 and in Paragraphs [0185]-[0186], teaches that one TBoMS transmission is performed through a transmission occasion composed of Z (it is corresponding to N) slot resources, and this TBoMS transmission is repeatedly transmitted through K (it is corresponding to M) transmission occasions, as explained in Fig. 11 and in Paragraph [0185]. As explained in Paragraph [0245], K (the number of repetition, corresponding to M) include K=1 case, namely, no repetition. Further, in Paragraphs [0305]-[0307], TBoMS transmission may be dynamically activated/deactivated (enabling/disabling). When TBoMS transmission is deactivated, conventional PUSCH transmission is performed, and when TBoMS transmission is activated, TBoMS transmission can be performed. TBoMS transmission may be activated/deactivated through an explicit field of DCI. Alternatively, when the Z value (corresponding to N), which is the number of slots constituting the TBoMS, is set by the DCI, the UE may determine activation/deactivation of the TBoMS by using the Z value. The UE may determine that TBoMS transmission is activated when the set value of Z is 2 or more and the value of Z is the number of slots constituting the TBoMS. When the set value of Z is 1, it can be determined that TBoMS transmission is deactivated. As explained in Paragraph [0280], it is implemented that when the value of Z corresponding to the row index of the TDRA table does not exit (if not set) the value of Z may be assumed to be 1. In Paragraph [0319], further explained, if the value of Z is set to 1 or all transmission occasions constituting TBoMS transmission consist of one slot, the UE determines that TBoMS transmission is not applied (deactivated) and repetition is applied for PUSCH transmission. Based on this observation, by setting Z (N)=1, TBoMS can be deactivated and a normal single-slot PUSCH transmission is performed or when Z (N) =1, if K (M) = 1 (no repetition) (it is supported as mentioned earlier) is set, the single-slot PUSCH transmission can be performed or if K >1 and Z =1, the normal repetitions in normal PUSCH transmission can be performed. Therefore, it is clear that the entry further includes an indication that M is to be re-interpreted and applied by the UE for a single-slot physical uplink shared channel (PUSCH) transmission with repetitions.)
Regarding claim 20, combination of You and Su teaches the features defined in the claim 16, -refer to the indicated claim for reference(s).
You teaches that wherein the entry in the TDRA list includes: an indication of a start and length indicator value (SLIV) for the TBoMS transmission, or an indication of a mapping type for the TBoMS transmission (You, in Table 6 and in Paragraph [0279], teaches that as shown in Table 6, the row indicated in allocation table (TDRA table: it can be considered as the TDRA list) may define slot offset K2 (corresponding to scheduling delay K2), start and length indicator SLIV ( or direct start symbol S and allocation length L), PUSCH mapping type, the number of repetitions (if repetition is in the allocation table) K (corresponding to number of repetition M), to be applied to PUSCH transmission, may be defined. The value of Z may be indicated through the 'Time domain resource assignment (TDRA)' field existing in DCI. The TDRA field value m of DCI provides the row index m+1 in the allocation table. That is, values corresponding to a specific row index of the TDRA table are applied for PUSCH transmission of the UE. In the past, values of {PUSCH mapping type, K2, SLIV (Sand L), K} were indicated through the TDRA table/field. For example, when the UE is scheduled to transmit a transport block and not a CSI report, or when the UE is scheduled to transmit a transport block and CSI report(s) on PUSCH by DCI, the time domain resource assignment field value m of DCI provides the row index m+1 of the allocation table.
Therefore, it is clear that the entry in the TDRA list includes: an indication of a start and length indicator value (SLIV) for the TBoMS transmission, or an indication of a mapping type for the TBoMS transmission.)
Regarding claim 21, You teaches one or more non-transitory computer-readable media storing instructions that, when executed by one or more processors, cause a next-generation NodeB (gNB) to: (You, in Fig. 25 and in Paragraphs [0458]-[0460], teaches that Fig. 25 illustrates the structure of a wireless device such as Base station or UE to transmit/receive wireless signals. The processor of the device may store information obtained from signal processing of the second information/signal in the memory 104. The memory 104 may be connected to the processor 102 and may store various pieces of information related to the operation of the processor 102. The information may include the configuration information to transmit/receive wireless signal. The processor 102 and the memory 104 may be part of a communication modem/circuit/chip designed to implement a radio communication technology (e.g., LTE or NR). Further, the processor 102 may process information in the memory 104 to generate first information/signal and may then transmit a radio signal including the first information/ signal through the transceiver 106. Therefore, it is clear that one or more computer-readable media stores instructions to cause a next-generation NodeB (gNB) to perform the followings mentioned in the below, when executed by one or more processors.) determine configuration information that includes a shared time domain resource allocation (TDRA) list associated with transport block over multiple slot (TBoMS) processing, (You, in Fig. 24 and in Paragraphs [0448]-[0451], teaches that in FIG. 24, the network (base station) provides downlink control information (DCI) for scheduling the first PUSCH to the UE (via PDCCH) (S241). The DCI may be, for example, DCI format 0_l or 0_2. DCI format 0_l is a DCI used for scheduling one or multiple PUSCHs in one cell or indicating a configured grant downlink feedback information (CG-DFI) to the UE, and DCI format 0_2 may be a DCI used for scheduling PUSCH in one cell. The DCI may include a time domain resource assignment (TDRA) field. The TDRA field informs of a specific row of a resource allocation table. For example, when the value of the TDRA field is m, it can be interpreted as indicating the row index m+ 1 of the resource allocation table for a TBoMS transmission (as explained in Table 11 and in Paragraph [0451]). Therefore, it is clear that the base station determines configuration information that includes a shared time domain resource allocation (TDRA) list associated with transport block over multiple slot (TBoMS) processing.) wherein the TDRA list includes an entry having an indication of a scheduling delay (k2), a number of repetitions (M), and a number of slots (N) for a TBoMS transmission; and (You, in Paragraphs [0279]-[0281] and in Table 6, teaches that Table 6 show the example of TDRA table (lists) for TBoMS transmissions. The table may define slot offset K2 (it can be corresponding to the scheduling delay K2 and it is explained in Paragraph [0157]), start and length indicator SLIV (or direct start symbol S and allocation length L), PUSCH mapping type, the number of repetitions, K (it is corresponding to M in the claim 22 in the below), to be applied to PUSCH transmission, may be defined. Further, the number of slots for one TBoMS transmission, Z (it is corresponding to N) is also defined. Therefore, it is clear that the TDRA list (table) includes an entry having an indication of a scheduling delay (k2) and number of slots (N) for a TBoMS transmission.) determine a transmission procedure based on the entry, wherein if the number of slots (N) is greater than 1, a TBoMS procedure is applied where the number of slots (N) is used for transport block size (TBS) determination, and wherein if the number of slots (N) is 1 or absent, a physical uplink shared channel (PUSCH) repetition Type A procedure is applied where a number of slots used for TBS determination is equal to 1; (You, in Fig. 9, in Table 6, and in Paragraphs [0135], [0279], [0280], [0307], and [0319], teaches that as described in Table 6 and Paragraphs [0279] and [0280], the value of the number of slot, Z (it is corresponding to N in the claim), is indicated through the TDRA field existing in DCI. The TDRA field value m of DCI provides the row index m+1 in the allocation table as shown in Table 6. Values corresponding to a specific row index of the TDRA table are applied for PUSCH transmission of the UE. In the past, values of {PUSCH mapping type, K2, SLIV (Sand L), K} were indicated through the TDRA table/field. Note that when the value of Z corresponding to the row index of the TDRA table does not exist 9if not set), the value of Z is assumed to be 1. You also teaches other indication methods for Z is described in Paragraphs [0282]-[0284]. In Paragraphs [0307] and [0319], You teaches when the Z value, which is the number of slots constituting the TBoMS, is set by the DCI as explained in the above, the UE determines activation/deactivation of the TBoMS by using the Z value. The UE determines that TBoMS transmission is activated when the set value of Z is 2 or more and the value of Z is the number of slots constituting the TBoMS. When the set value of Z is 1 or absent (as mention for the table), it is determined that TBoMS transmission is deactivated and the repetition is applied for PUSCH transmission. Here, since the PUSCH transmission uses a slot-based PUSCH repetition, the PUSCH repletion is used Type A as described in Fig. 9 and in Paragraphs [0135]. The PUSCH Type A repetition is performed with the same PUSCH transmission start symbol position and PUSCH transmission symbol length for each slot. Further, as described in Paragraphs [0007], [0428]-[0430], and [0464] and in Equation 7, TBS (Transport Block Size) is determined based on the number of resource elements (REs) allocated for the first PUSCH (NRE), the NRE is a value obtained by multiplying all of i) a number of the plurality of slots (Z) ii) a smaller one between a predetermined fixed value and a number of resource elements allocated for PUSCH within a physical resource block (NRE) and iii) a number of allocated physical resource blocks for the UE (nPRB). Thus, when Z (corresponding to N) ≥ 2, TBoMS procedure is applied for transmission and when Z = 1 or absent, TBoMS procedure is deactivated for transmission and instead, PUSCH transmission procedure is applied for transmission by using PUSCH type A repetition, where the TBS is determined by using Z.) determine a demodulation reference signal (DMRS) configuration for the transmission, wherein the DMRS configuration comprises front-loaded DMRS symbols transmitted in association with the transmission; and (You, in Paragraphs [0402]- [0408], teaches that the DMRS for PDSCH/PUSCH is composed of a front load DMRS and an additional DMRS. For the configuration of front load DMRS symbols in the amended claim 16, as described in Paragraphs [0404]-[0408], You teaches that the transmission time resource location of the front load DM-RS is determined by various factors: First, it depends on the mapping type of the data channel (PDSCH mapping type/PUSCH mapping type) is type A or type B (slot-based or non-slot based), where the mapping type is set through RRC. Further, in the case of slot-based transmission, the transmission start OFDM symbol position of the front load DMRS is the 3rd or 4th OFDM symbol of the data transmission resource, and an indication of whether the transmission start OFDM symbol position is the third OFDM symbol or the fourth OFDM symbol is transmitted through the PBCH. Rather, the front load DMRS consists of one or two consecutive OFDM symbols, and whether the number of OFDM symbols is one or two is set through RRC. In addition, there are two types (either Type 1 or Type 2) of mapping types in the transmission OFDM symbol resource of the front load DMRS, and the type information to be applied is set to RRC. In the case of type 1, using the technique of F-CDM (CDM in frequency domain), T-CDM (CDM in time domain), and/or FDM, the DMRS symbol length is either 1 or 2, or 4 or 8. For Type 2, using the technique of F-CDM, T-CDM. and/or FDM. the DMRS symbol length is either 1 or 2, or 6 or 12. Namely, based on type of mapping, the front load DMRS symbol length is determined. The configuration of DMRS for transmission include front loaded DMRS and additional DMRS, where the front loaded DMRS is configured based on the type of mapping and further the configuration of additional DMRS will be described for the dependent claims 31-33 in the below.)
However, You does not explicitly teach that encode a message for transmission to a user equipment (UE) that includes the configuration information and the DMRS configuration
Su teaches that encode a message for transmission to a user equipment (UE) that includes the configuration information and the DMRS configuration (Su, in Lines 1-9 in Page 20, teaches that there are three cases for scheduling PUSCH transmission, including UL grant in a DCI (Downlink Control Information), configured grant Type 1 and configured Type 2. They use different ways to indicate parameters in TDRA. A group of parameters indicates the value of K2, SLIV and mapping type at the same time, and groups of parameters compose the TDRA list in the RRC signaling or the default PUSCH TDRA Table. Then, time domain resource assignment in DCI field or timeDomainAllocation in RRC indicates the index of the TDRA list or the row of default PUSCH TDRA Table. In Lines 1-8 in Page 52 and Table 3.5-1 in Page 51, the TDRA table configuration is shown in Table 3.5-1 and one more parameter N (number of slots) can be indicated the number of slots of one TBoMS transmission (as indicated by Z or N in the above). The N can be added to the TDRA table and jointly encoded with TDRA field in DCI. Since DCI is the configuration message for UE to configure the uplink transmission, it is encoded (including TDRA field) and transmitted to the UE. Further, in Page 39, Lines 4-13 and Lines 32-35 and in Page 40, Lines 1-20, the DMRS configuration is made based on the PUSCH mapping type by using the parameters in RRC or DCI (as explained in the above). Therefore, the configuration message such as RRC/DCI (including TDRA lists) is encoded and transmitted to the UE.
It would have been obvious for one of ordinary skill in the art, before the effective filing date of the claimed invention, to combine You and Su to include the technique of encode a message for transmission to a user equipment (UE) that includes the configuration information and the DMRS configuration of Su in the system of You to provide network devices, terminal devices and methods therein, enabling TB (Transport Block) transmission over multiple slots, to improve the performance of a PUSCH transmission. (Su, see Lines 18-19 and Lines 29-30 in Page 1).).
Regarding claim 23, combination of You and Su teaches the features defined in the claim 21, -refer to the indicated claim for reference(s).
You further teaches that wherein N = 1 in the entry to indicate M is to be re- interpreted and applied by the UE for a single-slot physical uplink shared channel (PUSCH) transmission (You, in Fig. 11 and in Paragraphs [0185]-[0186], teaches that one TBoMS transmission is performed through a transmission occasion composed of Z (it is corresponding to N) slot resources, and this TBoMS transmission is repeatedly transmitted through K (it is corresponding to M) transmission occasions, as explained in Fig. 11 and in Paragraph [0185]. As explained in Paragraph [0245], K (the number of repetitions, corresponding to M) include K=1 case, namely, no repetition. Further, in Paragraphs [0305]-[0307], TBoMS transmission may be dynamically activated/deactivated (enabling/disabling). When TBoMS transmission is deactivated, conventional PUSCH transmission is performed, and when TBoMS transmission is activated, TBoMS transmission can be performed. TBoMS transmission may be activated/deactivated through an explicit field of DCI. Alternatively, when the Z value (corresponding to N), which is the number of slots constituting the TBoMS, is set by the DCI, the UE may determine activation/deactivation of the TBoMS by using the Z value. The UE may determine that TBoMS transmission is activated when the set value of Z is 2 or more and the value of Z is the number of slots constituting the TBoMS. When the set value of Z is 1, it can be determined that TBoMS transmission is deactivated. As explained in Paragraph [0280], it is implemented that when the value of Z corresponding to the row index of the TDRA table does not exit (if not set) the value of Z may be assumed to be 1. In Paragraph [0319], further explained, if the value of Z is set to 1 or all transmission occasions constituting TBoMS transmission consist of one slot, the UE determines that TBoMS transmission is not applied (deactivated) and repetition is applied for PUSCH transmission. Based on this observation, by setting Z (N)=1, TBoMS can be deactivated and a normal single-slot PUSCH transmission is performed or when Z (N) =1, if K (M) = 1 (no repetition) (it is supported as mentioned earlier) is set, the single-slot PUSCH transmission can be performed or if K >1 and Z =1, the normal repetitions in normal PUSCH transmission can be performed. Therefore, it is clear that N = 1 in the entry to indicate M is to be re- interpreted and applied by the UE for a single-slot physical uplink shared channel (PUSCH) transmission.)
Regarding claim 24, combination of You and Su teaches the features defined in the claim 23, -refer to the indicated claim for reference(s).
You teaches that wherein the entry further includes an indication that M is to be re-interpreted and applied by the UE for a single-slot physical uplink shared channel (PUSCH) transmission with repetitions (You, in Fig. 11 and in Paragraphs [0185]-[0186], teaches that one TBoMS transmission is performed through a transmission occasion composed of Z (it is corresponding to N) slot resources, and this TBoMS transmission is repeatedly transmitted through K (it is corresponding to M) transmission occasions, as explained in Fig. 11 and in Paragraph [0185]. As explained in Paragraph [0245], K (the number of repetition, corresponding to M) include K=1 case, namely, no repetition. Further, in Paragraphs [0305]-[0307], TBoMS transmission may be dynamically activated/deactivated (enabling/disabling). When TBoMS transmission is deactivated, conventional PUSCH transmission is performed, and when TBoMS transmission is activated, TBoMS transmission can be performed. TBoMS transmission may be activated/deactivated through an explicit field of DCI. Alternatively, when the Z value (corresponding to N), which is the number of slots constituting the TBoMS, is set by the DCI, the UE may determine activation/deactivation of the TBoMS by using the Z value. The UE may determine that TBoMS transmission is activated when the set value of Z is 2 or more and the value of Z is the number of slots constituting the TBoMS. When the set value of Z is 1, it can be determined that TBoMS transmission is deactivated. As explained in Paragraph [0280], it is implemented that when the value of Z corresponding to the row index of the TDRA table does not exit (if not set) the value of Z may be assumed to be 1. In Paragraph [0319], further explained, if the value of Z is set to 1 or all transmission occasions constituting TBoMS transmission consist of one slot, the UE determines that TBoMS transmission is not applied (deactivated) and repetition is applied for PUSCH transmission. Based on this observation, by setting Z (N)=1, TBoMS can be deactivated and a normal single-slot PUSCH transmission is performed or when Z (N) =1, if K (M) = 1 (no repetition) (it is supported as mentioned earlier) is set, the single-slot PUSCH transmission can be performed or if K >1 and Z =1, the normal repetitions in normal PUSCH transmission can be performed. Therefore, it is clear that the entry further includes an indication that M is to be re-interpreted and applied by the UE for a single-slot physical uplink shared channel (PUSCH) transmission with repetitions.)
Regarding claim 25, combination of You and Su teaches the features defined in the claim 21, -refer to the indicated claim for reference(s).
You teaches that wherein the entry in the TDRA list includes: an indication of a start and length indicator value (SLIV) for the TBoMS transmission, or an indication of a mapping type for the TBoMS transmission (You, in Table 6 and in Paragraph [0279], teaches that as shown in Table 6, the row indicated in allocation table (TDRA table: it can be considered as the TDRA list) may define slot offset K2 (corresponding to scheduling delay K2), start and length indicator SLIV ( or direct start symbol S and allocation length L), PUSCH mapping type, the number of repetitions (if repetition is in the allocation table) K (corresponding to number of repetition M), to be applied to PUSCH transmission, may be defined. The value of Z may be indicated through the 'Time domain resource assignment (TDRA)' field existing in DCI. The TDRA field value m of DCI provides the row index m+1 in the allocation table. That is, values corresponding to a specific row index of the TDRA table are applied for PUSCH transmission of the UE. In the past, values of {PUSCH mapping type, K2, SLIV (Sand L), K} were indicated through the TDRA table/field. For example, when the UE is scheduled to transmit a transport block and not a CSI report, or when the UE is scheduled to transmit a transport block and CSI report(s) on PUSCH by DCI, the time domain resource assignment field value m of DCI provides the row index m+1 of the allocation table.
Therefore, it is clear that the entry in the TDRA list includes: an indication of a start and length indicator value (SLIV) for the TBoMS transmission, or an indication of a mapping type for the TBoMS transmission.)
Regarding claim 26, You teaches one or more non-transitory computer-readable media storing instructions that, when executed by one or more processors, cause a user equipment (UE) to: (You, in Fig. 25 and in Paragraphs [0458]-[0460], teaches that Fig. 25 illustrates the structure of a wireless device such as Base station or UE to transmit/receive wireless signals. The processor of the device may store information obtained from signal processing of the second information/signal in the memory 104. The memory 104 may be connected to the processor 102 and may store various pieces of information related to the operation of the processor 102. The information may include the configuration information to transmit/receive wireless signal. The processor 102 and the memory 104 may be part of a communication modem/circuit/chip designed to implement a radio communication technology (e.g., LTE or NR). Further, the processor 102 may process information in the memory 104 to generate first information/signal and may then transmit a radio signal including the first information/ signal through the transceiver 106. Therefore, it is clear that one or more computer-readable media stores instructions to cause a UE to perform the followings mentioned in the below, when executed by one or more processors.) receive a message from a next-generation NodeB (gNB) comprising configuration information that includes a shared time domain resource allocation (TDRA) list associated with transport block over multiple slot (TBoMS) processing, (You, in Fig. 24 and in Paragraphs [0448]-[0451], teaches that in FIG. 24, the UE receives from network (base station) downlink control information (DCI) for scheduling the first PUSCH to the UE (via PDCCH) (S241). The DCI may be, for example, DCI format 0_l or 0_2. DCI format 0_l is a DCI used for scheduling one or multiple PUSCHs in one cell or indicating a configured grant downlink feedback information (CG-DFI) to the UE, and DCI format 0_2 may be a DCI used for scheduling PUSCH in one cell. The DCI may include a time domain resource assignment (TDRA) field. The TDRA field informs of a specific row of a resource allocation table. For example, when the value of the TDRA field is m, it can be interpreted as indicating the row index m+ 1 of the resource allocation table for a TBoMS transmission (as explained in Table 11 and in Paragraph [0451]). Therefore, it is clear that the base station UE receives a message from a next-generation NodeB (gNB) comprising configuration information that includes a shared time domain resource allocation (TDRA) list associated with transport block over multiple slot (TBoMS) processing.) wherein the TDRA list includes an entry having an indication of a scheduling delay (k2), a number of repetitions (K), and a number of slots (N) for a TBoMS transmission; and (You, in Paragraphs [0279]-[0281] and in Table 6, teaches that Table 6 show the example of TDRA table (lists) for TBoMS transmissions. The table may define slot offset K2 (it can be corresponding to the scheduling delay K2 and it is explained in Paragraph [0157]), start and length indicator SLIV (or direct start symbol S and allocation length L), PUSCH mapping type, the number of repetitions, K (it is corresponding to M in the claim 22 in the below), to be applied to PUSCH transmission, may be defined. Further, the number of slots for one TBoMS transmission, Z (it is corresponding to N) is also defined. Therefore, it is clear that the TDRA list (table) includes an entry having an indication of a scheduling delay (k2) and number of slots (N) for a TBoMS transmission.) determine a transmission procedure based on the entry, wherein if the number of slots (N) is greater than 1, a TBoMS procedure is applied where the number of slots (N) is used for transport block size (TBS) determination, and wherein if the number of slots (N) is 1 or absent, a physical uplink shared channel (PUSCH) repetition Type A procedure is applied where a number of slots used for TBS determination is equal to 1; (You, in Fig. 9, in Table 6, and in Paragraphs [0135], [0279], [0280], [0307], and [0319], teaches that as described in Table 6 and Paragraphs [0279] and [0280], the value of the number of slot, Z (it is corresponding to N in the claim), is indicated through the TDRA field existing in DCI. The TDRA field value m of DCI provides the row index m+1 in the allocation table as shown in Table 6. Values corresponding to a specific row index of the TDRA table are applied for PUSCH transmission of the UE. In the past, values of {PUSCH mapping type, K2, SLIV (Sand L), K} were indicated through the TDRA table/field. Note that when the value of Z corresponding to the row index of the TDRA table does not exist 9if not set), the value of Z is assumed to be 1. You also teaches other indication methods for Z is described in Paragraphs [0282]-[0284]. In Paragraphs [0307] and [0319], You teaches when the Z value, which is the number of slots constituting the TBoMS, is set by the DCI as explained in the above, the UE determines activation/deactivation of the TBoMS by using the Z value. The UE determines that TBoMS transmission is activated when the set value of Z is 2 or more and the value of Z is the number of slots constituting the TBoMS. When the set value of Z is 1 or absent (as mention for the table), it is determined that TBoMS transmission is deactivated and the repetition is applied for PUSCH transmission. Here, since the PUSCH transmission uses a slot-based PUSCH repetition, the PUSCH repletion is used Type A as described in Fig. 9 and in Paragraphs [0135]. The PUSCH Type A repetition is performed with the same PUSCH transmission start symbol position and PUSCH transmission symbol length for each slot. Further, as described in Paragraphs [0007], [0428]-[0430], and [0464] and in Equation 7, TBS (Transport Block Size) is determined based on the number of resource elements (REs) allocated for the first PUSCH (NRE), the NRE is a value obtained by multiplying all of i) a number of the plurality of slots (Z) ii) a smaller one between a predetermined fixed value and a number of resource elements allocated for PUSCH within a physical resource block (NRE) and iii) a number of allocated physical resource blocks for the UE (nPRB). Thus, when Z (corresponding to N) ≥ 2, TBoMS procedure is applied for transmission and when Z = 1 or absent, TBoMS procedure is deactivated for transmission and instead, PUSCH transmission procedure is applied for transmission by using PUSCH type A repetition, where the TBS is determined by using Z.) determine a demodulation reference signal (DMRS) configuration for the transmission, wherein the DMRS configuration comprises front-loaded DMRS symbols transmitted in association with the transmission; and (You, in Paragraphs [0402]- [0408], teaches that the DMRS for PDSCH/PUSCH is composed of a front load DMRS and an additional DMRS. For the configuration of front load DMRS symbols in the amended claim 16, as described in Paragraphs [0404]-[0408], You teaches that the transmission time resource location of the front load DM-RS is determined by various factors: First, it depends on the mapping type of the data channel (PDSCH mapping type/PUSCH mapping type) is type A or type B (slot-based or non-slot based), where the mapping type is set through RRC. Further, in the case of slot-based transmission, the transmission start OFDM symbol position of the front load DMRS is the 3rd or 4th OFDM symbol of the data transmission resource, and an indication of whether the transmission start OFDM symbol position is the third OFDM symbol or the fourth OFDM symbol is transmitted through the PBCH. Rather, the front load DMRS consists of one or two consecutive OFDM symbols, and whether the number of OFDM symbols is one or two is set through RRC. In addition, there are two types (either Type 1 or Type 2) of mapping types in the transmission OFDM symbol resource of the front load DMRS, and the type information to be applied is set to RRC. In the case of type 1, using the technique of F-CDM (CDM in frequency domain), T-CDM (CDM in time domain), and/or FDM, the DMRS symbol length is either 1 or 2, or 4 or 8. For Type 2, using the technique of F-CDM, T-CDM. and/or FDM. the DMRS symbol length is either 1 or 2, or 6 or 12. Namely, based on type of mapping, the front load DMRS symbol length is determined. The configuration of DMRS for transmission include front loaded DMRS and additional DMRS, where the front loaded DMRS is configured based on the type of mapping and further the configuration of additional DMRS will be described for the dependent claims 31-33 in the below.)
However, You does not explicitly teach that encode a TBoMS message for transmission based on the configuration information and the DMRS configuration
Su teaches that encode a message for transmission to a user equipment (UE) that includes the configuration information and the DMRS configuration (Su, in Lines 1-9 in Page 20, teaches that there are three cases for scheduling PUSCH transmission, including UL grant in a DCI (Downlink Control Information), configured grant Type 1 and configured Type 2. They use different ways to indicate parameters in TDRA. A group of parameters indicates the value of K2, SLIV and mapping type at the same time, and groups of parameters compose the TDRA list in the RRC signaling or the default PUSCH TDRA Table. Then, time domain resource assignment in DCI field or timeDomainAllocation in RRC indicates the index of the TDRA list or the row of default PUSCH TDRA Table. In Lines 1-8 in Page 52 and Table 3.5-1 in Page 51, the TDRA table configuration is shown in Table 3.5-1 and one more parameter N (number of slots) can be indicated the number of slots of one TBoMS transmission (as indicated by Z or N in the above). The N can be added to the TDRA table and jointly encoded with TDRA field in DCI. Since DCI is the configuration message for UE to configure the uplink transmission, it is encoded (including TDRA field) and transmitted to the UE. Further, in Page 39, Lines 4-13 and Lines 32-35 and in Page 40, Lines 1-20, the DMRS configuration is made based on the PUSCH mapping type by using the parameters in RRC or DCI (as explained in the above). Therefore, the configuration message such as RRC/DCI (including TDRA lists) is encoded and transmitted to the UE.
It would have been obvious for one of ordinary skill in the art, before the effective filing date of the claimed invention, to combine You and Su to include the technique of encode a TBoMS message for transmission based on the configuration information and the DMRS configuration of Su in the system of You to provide network devices, terminal devices and methods therein, enabling TB (Transport Block) transmission over multiple slots, to improve the performance of a PUSCH transmission. (Su, see Lines 18-19 and Lines 29-30 in Page 1).).
Regarding claim 28, combination of You and Su teaches the features defined in the claim 26, -refer to the indicated claim for reference(s).
You further teaches that wherein N = 1 in the entry to indicate M is to be re- interpreted and applied by the UE for a single-slot physical uplink shared channel (PUSCH) transmission (You, in Fig. 11 and in Paragraphs [0185]-[0186], teaches that one TBoMS transmission is performed through a transmission occasion composed of Z (it is corresponding to N) slot resources, and this TBoMS transmission is repeatedly transmitted through K (it is corresponding to M) transmission occasions, as explained in Fig. 11 and in Paragraph [0185]. As explained in Paragraph [0245], K (the number of repetitions, corresponding to M) include K=1 case, namely, no repetition. Further, in Paragraphs [0305]-[0307], TBoMS transmission may be dynamically activated/deactivated (enabling/disabling). When TBoMS transmission is deactivated, conventional PUSCH transmission is performed, and when TBoMS transmission is activated, TBoMS transmission can be performed. TBoMS transmission may be activated/deactivated through an explicit field of DCI. Alternatively, when the Z value (corresponding to N), which is the number of slots constituting the TBoMS, is set by the DCI, the UE may determine activation/deactivation of the TBoMS by using the Z value. The UE may determine that TBoMS transmission is activated when the set value of Z is 2 or more and the value of Z is the number of slots constituting the TBoMS. When the set value of Z is 1, it can be determined that TBoMS transmission is deactivated. As explained in Paragraph [0280], it is implemented that when the value of Z corresponding to the row index of the TDRA table does not exit (if not set) the value of Z may be assumed to be 1. In Paragraph [0319], further explained, if the value of Z is set to 1 or all transmission occasions constituting TBoMS transmission consist of one slot, the UE determines that TBoMS transmission is not applied (deactivated) and repetition is applied for PUSCH transmission. Based on this observation, by setting Z (N)=1, TBoMS can be deactivated and a normal single-slot PUSCH transmission is performed or when Z (N) =1, if K (M) = 1 (no repetition) (it is supported as mentioned earlier) is set, the single-slot PUSCH transmission can be performed or if K >1 and Z =1, the normal repetitions in normal PUSCH transmission can be performed. Therefore, it is clear that N = 1 in the entry to indicate M is to be re- interpreted and applied by the UE for a single-slot physical uplink shared channel (PUSCH) transmission.)
Regarding claim 29, combination of You and Su teaches the features defined in the claim 28, -refer to the indicated claim for reference(s).
You teaches that wherein the entry further includes an indication that M is to be re-interpreted and applied by the UE for a single-slot physical uplink shared channel (PUSCH) transmission with repetitions (You, in Fig. 11 and in Paragraphs [0185]-[0186], teaches that one TBoMS transmission is performed through a transmission occasion composed of Z (it is corresponding to N) slot resources, and this TBoMS transmission is repeatedly transmitted through K (it is corresponding to M) transmission occasions, as explained in Fig. 11 and in Paragraph [0185]. As explained in Paragraph [0245], K (the number of repetition, corresponding to M) include K=1 case, namely, no repetition. Further, in Paragraphs [0305]-[0307], TBoMS transmission may be dynamically activated/deactivated (enabling/disabling). When TBoMS transmission is deactivated, conventional PUSCH transmission is performed, and when TBoMS transmission is activated, TBoMS transmission can be performed. TBoMS transmission may be activated/deactivated through an explicit field of DCI. Alternatively, when the Z value (corresponding to N), which is the number of slots constituting the TBoMS, is set by the DCI, the UE may determine activation/deactivation of the TBoMS by using the Z value. The UE may determine that TBoMS transmission is activated when the set value of Z is 2 or more and the value of Z is the number of slots constituting the TBoMS. When the set value of Z is 1, it can be determined that TBoMS transmission is deactivated. As explained in Paragraph [0280], it is implemented that when the value of Z corresponding to the row index of the TDRA table does not exit (if not set) the value of Z may be assumed to be 1. In Paragraph [0319], further explained, if the value of Z is set to 1 or all transmission occasions constituting TBoMS transmission consist of one slot, the UE determines that TBoMS transmission is not applied (deactivated) and repetition is applied for PUSCH transmission. Based on this observation, by setting Z (N)=1, TBoMS can be deactivated and a normal single-slot PUSCH transmission is performed or when Z (N) =1, if K (M) = 1 (no repetition) (it is supported as mentioned earlier) is set, the single-slot PUSCH transmission can be performed or if K >1 and Z =1, the normal repetitions in normal PUSCH transmission can be performed. Therefore, it is clear that the entry further includes an indication that M is to be re-interpreted and applied by the UE for a single-slot physical uplink shared channel (PUSCH) transmission with repetitions.)
Regarding claim 30, combination of You and Su teaches the features defined in the claim 26, -refer to the indicated claim for reference(s).
You teaches that wherein the entry in the TDRA list includes: an indication of a start and length indicator value (SLIV) for the TBoMS transmission, or an indication of a mapping type for the TBoMS transmission (You, in Table 6 and in Paragraph [0279], teaches that as shown in Table 6, the row indicated in allocation table (TDRA table: it can be considered as the TDRA list) may define slot offset K2 (corresponding to scheduling delay K2), start and length indicator SLIV ( or direct start symbol S and allocation length L), PUSCH mapping type, the number of repetitions (if repetition is in the allocation table) K (corresponding to number of repetition M), to be applied to PUSCH transmission, may be defined. The value of Z may be indicated through the 'Time domain resource assignment (TDRA)' field existing in DCI. The TDRA field value m of DCI provides the row index m+1 in the allocation table. That is, values corresponding to a specific row index of the TDRA table are applied for PUSCH transmission of the UE. In the past, values of {PUSCH mapping type, K2, SLIV (Sand L), K} were indicated through the TDRA table/field. For example, when the UE is scheduled to transmit a transport block and not a CSI report, or when the UE is scheduled to transmit a transport block and CSI report(s) on PUSCH by DCI, the time domain resource assignment field value m of DCI provides the row index m+1 of the allocation table.Therefore, it is clear that the entry in the TDRA list includes: an indication of a start and length indicator value (SLIV) for the TBoMS transmission, or an indication of a mapping type for the TBoMS transmission.)
Regarding claim 31, combination of You and Su teaches the features defined in the claim 16, -refer to the indicated claim for reference(s).
You teaches that wherein the DMRS configuration further comprises additional DMRS symbols transmitted in slots subsequent to a first slot of the number of slots (N) at symbol positions indicated by a DMRS additional position parameter (You, in Paragraphs [0409]-[0425], teaches that in Paragraphs [0409]-[0410], the number of addition DMRSs is determined among 0, 1, 2, 3. The maximum number of additional DMRSs to be transmitted is determined through RRC, and the number of additional DMRSs actually transmitted within each maximum number of DMRSs and the transmission OFDM symbol position are determined according to the length of the OFDM symbol through which data is transmitted. The number of OFDM symbols and the mapping type of each additional DMRS are determined to be the same as the number of OFDM symbols and the mapping type of the front load DMRS. As described in Paragraphs [0411]-[0417], in case of DMRS for PUSCH, as described above, it is divided into a front load DM-RS and an additional DMRS, and the number of additional DMRSs is determined among 0, 1, 2, or 3. The reference point of I (I indicates a symbol index in the time domain) and the position Io of the first DMRS symbol are dependent on the mapping type. For PUSCH mapping type A, if frequency hopping is deactivated, I is defined relative to the beginning of the slot, and if frequency hopping is activated, I is defined based on the start of each hop. Io is provided by the higher layer parameter dmrsTypeA-Position. For PUSCH mapping type B, I is defined for the start of the scheduled PUSCH resource when frequency hopping is deactivated and I is defined for the start of each hop when frequency hopping is activated. Io is 0. Further, the location(s) of the DMRS symbol is given by I and duration Id, where Id is a duration between the first OFDM symbol of a slot and the last OFDM symbol of a scheduled PUSCH resource in a slot for PUSCH mapping type A, or, Id is a duration of a PUSCH resource scheduled for PUSCH mapping type B, respectively, when intra-slot frequency hopping is not used. Further, as described in Paragraphs [0418]-[0419] and Table 8 and 9, when intra-slot frequency hopping is deactivated, a PUSCH DMRS position in a slot is configured by Table 8 for a single symbol DMRS and/or by Table 9 for the dual symbol DMRS. Further, as described in [0420]-[0425], when PUSCH TB (Transport Block) is mapped on multiple slots and symbol resources used for PUSCH TB mapping are different between slots, in each slot, the position and number of DMRS (Including front loaded DMRS and addition DMRS) transmission symbols are determined by UE based on the 'reference position for I' and the 'duration Id’ in each transmission slot. In this case, the position and the number of DMRS transmission symbols are either different for each slot (Method 1) or same for each slot (Method 2). Based on this, the DMRS configuration comprises additional DMRS symbols transmitted in slots subsequent to a first slot of the number of slots (N) at symbol positions indicated by a DMRS additional position parameter in Table 8 or 9.)
Regarding claim 32, combination of You and Su teaches the features defined in the claim 21, -refer to the indicated claim for reference(s).
You teaches that wherein the DMRS configuration further comprises additional DMRS symbols transmitted in slots subsequent to a first slot of the number of slots (N) at symbol positions indicated by a DMRS additional position parameter (You, in Paragraphs [0409]-[0425], teaches that in Paragraphs [0409]-[0410], the number of addition DMRSs is determined among 0, 1, 2, 3. The maximum number of additional DMRSs to be transmitted is determined through RRC, and the number of additional DMRSs actually transmitted within each maximum number of DMRSs and the transmission OFDM symbol position are determined according to the length of the OFDM symbol through which data is transmitted. The number of OFDM symbols and the mapping type of each additional DMRS are determined to be the same as the number of OFDM symbols and the mapping type of the front load DMRS. As described in Paragraphs [0411]-[0417], in case of DMRS for PUSCH, as described above, it is divided into a front load DM-RS and an additional DMRS, and the number of additional DMRSs is determined among 0, 1, 2, or 3. The reference point of I (I indicates a symbol index in the time domain) and the position Io of the first DMRS symbol are dependent on the mapping type. For PUSCH mapping type A, if frequency hopping is deactivated, I is defined relative to the beginning of the slot, and if frequency hopping is activated, I is defined based on the start of each hop. Io is provided by the higher layer parameter dmrsTypeA-Position. For PUSCH mapping type B, I is defined for the start of the scheduled PUSCH resource when frequency hopping is deactivated and I is defined for the start of each hop when frequency hopping is activated. Io is 0. Further, the location(s) of the DMRS symbol is given by I and duration Id, where Id is a duration between the first OFDM symbol of a slot and the last OFDM symbol of a scheduled PUSCH resource in a slot for PUSCH mapping type A, or, Id is a duration of a PUSCH resource scheduled for PUSCH mapping type B, respectively, when intra-slot frequency hopping is not used. Further, as described in Paragraphs [0418]-[0419] and Table 8 and 9, when intra-slot frequency hopping is deactivated, a PUSCH DMRS position in a slot is configured by Table 8 for a single symbol DMRS and/or by Table 9 for the dual symbol DMRS. Further, as described in [0420]-[0425], when PUSCH TB (Transport Block) is mapped on multiple slots and symbol resources used for PUSCH TB mapping are different between slots, in each slot, the position and number of DMRS (Including front loaded DMRS and addition DMRS) transmission symbols are determined by UE based on the 'reference position for I' and the 'duration Id’ in each transmission slot. In this case, the position and the number of DMRS transmission symbols are either different for each slot (Method 1) or same for each slot (Method 2). Based on this, the DMRS configuration comprises additional DMRS symbols transmitted in slots subsequent to a first slot of the number of slots (N) at symbol positions indicated by a DMRS additional position parameter in Table 8 or 9.)
Regarding claim 33, combination of You and Su teaches the features defined in the claim 26, -refer to the indicated claim for reference(s).
You teaches that wherein the DMRS configuration further comprises additional DMRS symbols transmitted in slots subsequent to a first slot of the number of slots (N) at symbol positions indicated by a DMRS additional position parameter (You, in Paragraphs [0409]-[0425], teaches that in Paragraphs [0409]-[0410], the number of addition DMRSs is determined among 0, 1, 2, 3. The maximum number of additional DMRSs to be transmitted is determined through RRC, and the number of additional DMRSs actually transmitted within each maximum number of DMRSs and the transmission OFDM symbol position are determined according to the length of the OFDM symbol through which data is transmitted. The number of OFDM symbols and the mapping type of each additional DMRS are determined to be the same as the number of OFDM symbols and the mapping type of the front load DMRS. As described in Paragraphs [0411]-[0417], in case of DMRS for PUSCH, as described above, it is divided into a front load DM-RS and an additional DMRS, and the number of additional DMRSs is determined among 0, 1, 2, or 3. The reference point of I (I indicates a symbol index in the time domain) and the position Io of the first DMRS symbol are dependent on the mapping type. For PUSCH mapping type A, if frequency hopping is deactivated, I is defined relative to the beginning of the slot, and if frequency hopping is activated, I is defined based on the start of each hop. Io is provided by the higher layer parameter dmrsTypeA-Position. For PUSCH mapping type B, I is defined for the start of the scheduled PUSCH resource when frequency hopping is deactivated and I is defined for the start of each hop when frequency hopping is activated. Io is 0. Further, the location(s) of the DMRS symbol is given by I and duration Id, where Id is a duration between the first OFDM symbol of a slot and the last OFDM symbol of a scheduled PUSCH resource in a slot for PUSCH mapping type A, or, Id is a duration of a PUSCH resource scheduled for PUSCH mapping type B, respectively, when intra-slot frequency hopping is not used. Further, as described in Paragraphs [0418]-[0419] and Table 8 and 9, when intra-slot frequency hopping is deactivated, a PUSCH DMRS position in a slot is configured by Table 8 for a single symbol DMRS and/or by Table 9 for the dual symbol DMRS. Further, as described in [0420]-[0425], when PUSCH TB (Transport Block) is mapped on multiple slots and symbol resources used for PUSCH TB mapping are different between slots, in each slot, the position and number of DMRS (Including front loaded DMRS and addition DMRS) transmission symbols are determined by UE based on the 'reference position for I' and the 'duration Id’ in each transmission slot. In this case, the position and the number of DMRS transmission symbols are either different for each slot (Method 1) or same for each slot (Method 2). Based on this, the DMRS configuration comprises additional DMRS symbols transmitted in slots subsequent to a first slot of the number of slots (N) at symbol positions indicated by a DMRS additional position parameter in Table 8 or 9.)
Conclusion
Any inquiry concerning this communication or earlier communications from the examiner should be directed to JAEYOUNG KWAK whose telephone number is (703)756-1768. The examiner can normally be reached Monday-Friday 9 AM -5 PM.
Examiner interviews are available via telephone, in-person, and video conferencing using a USPTO supplied web-based collaboration tool. To schedule an interview, applicant is encouraged to use the USPTO Automated Interview Request (AIR) at http://www.uspto.gov/interviewpractice.
If attempts to reach the examiner by telephone are unsuccessful, the examiner’s supervisor, Kevin Bates can be reached at 571-272-3980. The fax phone number for the organization where this application or proceeding is assigned is 571-273-8300.
Information regarding the status of published or unpublished applications may be obtained from Patent Center. Unpublished application information in Patent Center is available to registered users. To file and manage patent submissions in Patent Center, visit: https://patentcenter.uspto.gov. Visit https://www.uspto.gov/patents/apply/patent-center for more information about Patent Center and https://www.uspto.gov/patents/docx for information about filing in DOCX format. For additional questions, contact the Electronic Business Center (EBC) at 866-217-9197 (toll-free). If you would like assistance from a USPTO Customer Service Representative, call 800-786-9199 (IN USA OR CANADA) or 571-272-1000.
/JAEYOUNG KWAK/Examiner, Art Unit 2472
/KEVIN T BATES/Supervisory Patent Examiner, Art Unit 2472
