DETAILED ACTION
The office action is in response to the amendments received on Jan. 23, 2026 after a non-final office action.
Claims 16-30 are pending in this application, based on the amended claims on Jan. 23, 2026.
Information Disclosure Statement
The information disclosure statements (IDSs) submitted on March 26, 2026, Sept. 15, 2023, and Sept. 6, 2023 has 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 01/23/2026 have been considered for examination. Claims 16-30 are pending in this application, based on the amended claims on Jan. 23, 2026.
With regard to the 101 rejections, Applicant’s arguments filed 01/23/2026 in view of the amendment has been fully considered and is persuasive. Thus, the 101 rejections have been withdrawn.
With regard to the 103 rejections, Applicant’s arguments filed 01/23/2026 (see pages 7-8 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 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 generally teaches a method for transmitting a transport block. (See, e.g., You, Abstract). According to You, a resource allocation table may include information on the number of slots (Z) and number of repetitions (K). (See You, Paragraph [0453]). You discusses that if Z is 1, TBoMS is deactivated. (See You, Paragraph [0307]).
However, You utilizes an explicit "PUSCH Mapping Type" column in its table (see Table 11) and does not teach the specific logic of implicitly determining the transmission procedure (specifically differentiating between a TBoMS procedure and a PUSCH repetition Type A procedure) based specifically on whether the number of slots (N) is greater than 1 versus being 1 or absent, nor does it teach the specific consequence where N is used for TBS determination in the first case and N is set to equal 1 for TBS determination in the second case, within the context of a shared TDRA list configuration as claimed.
Thus, You does not teach or suggest this part of the amended claim 1. (see, pages 7-8 of Remarks).
In response to Applicant’s argument, Examiner respectfully disagrees.
In the argument, Applicant argued that You does not teach or disclose the part of the amended claim 1 in the above. However, Examiner respectfully disagrees.
In the previous Office Action, the previous claim 1 was clearly disclosed by You and Su. Regarding the amended part of the claim 1 mentioned in the above, 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. Thus, the newly added part in the amended claim 1 is clearly disclosed by You.
Therefore, it is clear that the amended claim 16 is disclosed by combination of You and Su and by the same reasoning, the amended claims 21 and 26 is also disclosed by combination of You and Su.
However, since the amended claims 16, 21, and 26 have changed the scope of the previous claims, the new rejection is presented in this instant office action in the below.
Claim Rejections - 35 USC § 112
The following is a quotation of 35 U.S.C. 112(b):
(b) CONCLUSION.—The specification shall conclude with one or more claims particularly pointing out and distinctly claiming the subject matter which the inventor or a joint inventor regards as the invention.
The following is a quotation of 35 U.S.C. 112 (pre-AIA ), second paragraph:
The specification shall conclude with one or more claims particularly pointing out and distinctly claiming the subject matter which the applicant regards as his invention.
Claims 16-19, 21-24, and 26-29 rejected under 35 U.S.C. 112(b) or 35 U.S.C. 112 (pre-AIA ), second paragraph, as being indefinite for failing to particularly point out and distinctly claim the subject matter which the inventor or a joint inventor (or for applications subject to pre-AIA 35 U.S.C. 112, the applicant), regards as the invention. Independent Claims 16, 21, and 26 recites “a number of repetitions (K)” in Line 6 of Claim 16, in Lines 6-7 of Claim 21, and in Line 6 of Claim 26. While, “a number of repetitions (M)” is recited in Line 2 of dependent Claims 17-19, 22-24, and 27-29, respectively. But it is not clear whether K and M indicates the same repetition or not. Further, in Specification, there is no K that indicates a number of repetitions and only M is existed to indicates a number of repetitions. There is insufficient antecedent basis for these limitations in the claim. Thus, Claims 16-19, 21-24, and 26-29 are rejected.
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-30 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 (K), 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.)
However, You does not explicitly teach that encode a message for transmission to a user equipment (UE) that includes the configuration information.
Su teaches that encode a message for transmission to a user equipment (UE) that includes the configuration information (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. Therefore, it is clear that the configuration message such as 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 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 17, combination of You and Su teaches the features defined in the claim 16, -refer to the indicated claim for reference(s).
You further teaches that wherein the entry further includes an indication of a number of repetitions (M) for the TBoMS transmission (You, in Paragraph [0279]-[0281] and in Table 6, K (it is corresponding to M) in Table 6 indicates the number of repetitions for TBoMS transmission as explained in Paragraph [0181]: When one TBoMS transmission is performed through a transmission occasion composed of Z slots and this TBoMS is repeatedly transmitted through K transmission occasions, the Z and K values may be provided by the table above. Z may be the number of symbols used for TBS (Transport Block Size) determination. K may indicate a value of the number of repetitions to be applied to PUSCH transmission.
Therefore, it is clear that the entry of TDRA table or list includes an indication of a number of repetitions (M) (Here, K is corresponding to M) for the TBoMS transmission.)
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 (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.)
However, You does not explicitly teach that encode a message for transmission to a user equipment (UE) that includes the configuration information.
Su teaches that encode a message for transmission to a user equipment (UE) that includes the configuration information (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. Therefore, it is clear that the configuration message such as 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 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 22, 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 the entry further includes an indication of a number of repetitions (M) for the TBoMS transmission (You, in Paragraph [0279]-[0281] and in Table 6, K (it is corresponding to M) in Table 6 indicates the number of repetitions for TBoMS transmission as explained in Paragraph [0181]: When one TBoMS transmission is performed through a transmission occasion composed of Z slots and this TBoMS is repeatedly transmitted through K transmission occasions, the Z and K values may be provided by the table above. Z may be the number of symbols used for TBS (Transport Block Size) determination. K may indicate a value of the number of repetitions to be applied to PUSCH transmission.
Therefore, it is clear that the entry of TDRA table or list includes an indication of a number of repetitions (M) (Here, K is corresponding to M) for the TBoMS transmission.)
Regarding claim 23, combination of You and Su teaches the features defined in the claim 22, -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.)
However, You does not explicitly teach that encode a TBoMS message for transmission based on the configuration information.
Su teaches that encode a TBoMS message for transmission based on the configuration information (Su, in Lines 8-18 in Page 55, teaches that TBoMS transmission determines time domain resource allocation (TDRA) according to PUSCH repetition Type A as defined in 3GPP. The starting symbol S and the number of consecutive symbols L within each slot are calculated for the repetition type A. In the embodiment, a portion of the TB (Transport Block) is carried within each slot, where the entirety of the TB is encoded within each slot. Because only a portion of the TB is carried, the number of symbols L is less than total number of symbols occupied by the TB in all of the slots that the TB is carried in, Nshsymb· Also, because S and L are the same for each slot due to this use of PUSCH repetition type A TDRA, the total number of symbols occupied by the PUSCH is then Nshsymb = K x L. Therefore, it is clear that a TBoMS message is encoded for transmission based on the configuration information.
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 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 27, 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 the entry further includes an indication of a number of repetitions (M) for the TBoMS transmission (You, in Paragraph [0279]-[0281] and in Table 6, K (it is corresponding to M) in Table 6 indicates the number of repetitions for TBoMS transmission as explained in Paragraph [0181]: When one TBoMS transmission is performed through a transmission occasion composed of Z slots and this TBoMS is repeatedly transmitted through K transmission occasions, the Z and K values may be provided by the table above. Z may be the number of symbols used for TBS (Transport Block Size) determination. K may indicate a value of the number of repetitions to be applied to PUSCH transmission.
Therefore, it is clear that the entry of TDRA table or list includes an indication of a number of repetitions (M) (Here, K is corresponding to M) for the TBoMS transmission.)
Regarding claim 28, combination of You and Su teaches the features defined in the claim 27, -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.)
Conclusion
Applicant's amendment necessitated the new ground(s) of rejection presented in this Office action. Accordingly, THIS ACTION IS MADE FINAL. See MPEP § 706.07(a). Applicant is reminded of the extension of time policy as set forth in 37 CFR 1.136(a).
A shortened statutory period for reply to this final action is set to expire THREE MONTHS from the mailing date of this action. In the event a first reply is filed within TWO MONTHS of the mailing date of this final action and the advisory action is not mailed until after the end of the THREE-MONTH shortened statutory period, then the shortened statutory period will expire on the date the advisory action is mailed, and any nonprovisional extension fee (37 CFR 1.17(a)) pursuant to 37 CFR 1.136(a) will be calculated from the mailing date of the advisory action. In no event, however, will the statutory period for reply expire later than SIX MONTHS from the mailing date of this final action.
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
Prosecution Insights