DETAILED ACTION
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 .
Priority
Acknowledgment is made of applicant’s claim for foreign priority under 35 U.S.C. 119 (a)-(d).
Double Patenting
The nonstatutory double patenting rejection is based on a judicially created doctrine grounded in public policy (a policy reflected in the statute) so as to prevent the unjustified or improper timewise extension of the “right to exclude” granted by a patent and to prevent possible harassment by multiple assignees. A nonstatutory double patenting rejection is appropriate where the conflicting claims are not identical, but at least one examined application claim is not patentably distinct from the reference claim(s) because the examined application claim is either anticipated by, or would have been obvious over, the reference claim(s). See, e.g., In re Berg, 140 F.3d 1428, 46 USPQ2d 1226 (Fed. Cir. 1998); In re Goodman, 11 F.3d 1046, 29 USPQ2d 2010 (Fed. Cir. 1993); In re Longi, 759 F.2d 887, 225 USPQ 645 (Fed. Cir. 1985); In re Van Ornum, 686 F.2d 937, 214 USPQ 761 (CCPA 1982); In re Vogel, 422 F.2d 438, 164 USPQ 619 (CCPA 1970); In re Thorington, 418 F.2d 528, 163 USPQ 644 (CCPA 1969).
A timely filed terminal disclaimer in compliance with 37 CFR 1.321(c) or 1.321(d) may be used to overcome an actual or provisional rejection based on nonstatutory double patenting provided the reference application or patent either is shown to be commonly owned with the examined application, or claims an invention made as a result of activities undertaken within the scope of a joint research agreement. See MPEP § 717.02 for applications subject to examination under the first inventor to file provisions of the AIA as explained in MPEP § 2159. See MPEP § 2146 et seq. for applications not subject to examination under the first inventor to file provisions of the AIA . A terminal disclaimer must be signed in compliance with 37 CFR 1.321(b).
The filing of a terminal disclaimer by itself is not a complete reply to a nonstatutory double patenting (NSDP) rejection. A complete reply requires that the terminal disclaimer be accompanied by a reply requesting reconsideration of the prior Office action. Even where the NSDP rejection is provisional the reply must be complete. See MPEP § 804, subsection I.B.1. For a reply to a non-final Office action, see 37 CFR 1.111(a). For a reply to final Office action, see 37 CFR 1.113(c). A request for reconsideration while not provided for in 37 CFR 1.113(c) may be filed after final for consideration. See MPEP §§ 706.07(e) and 714.13.
The USPTO Internet website contains terminal disclaimer forms which may be used. Please visit www.uspto.gov/patent/patents-forms. The actual filing date of the application in which the form is filed determines what form (e.g., PTO/SB/25, PTO/SB/26, PTO/AIA /25, or PTO/AIA /26) should be used. A web-based eTerminal Disclaimer may be filled out completely online using web-screens. An eTerminal Disclaimer that meets all requirements is auto-processed and approved immediately upon submission. For more information about eTerminal Disclaimers, refer to www.uspto.gov/patents/apply/applying-online/eterminal-disclaimer.
Claims 1-15 are rejected on the ground of nonstatutory double patenting as being unpatentable over claims 1-14 of U.S. Patent No. 11,539,407. Although the claims at issue are not identical, they are not patentably distinct from each other because the broader application claim is generic to all that is recited in claims 1-14 of U.S. Patent No. 11,539,407. That is, claims 1-15 are anticipated by claims 1-14 of the patent shown as bold type in the table below. Dependent claims 2-11 and 14 (not shown in the table) are rejected being anticipated by claims 1-11 of the patent.
Claims 1-15 are rejected on the ground of nonstatutory double patenting as being unpatentable over claims 1-14 of U.S. Patent No. 12,057,903. The instant application recites “noncodebook” while the patent recites “Codebook (CB)” (please see the table below). However, the SRS configuration is for codebook and non-codebook in the Patent (Col 4, L38-Col 5, L15). Therefore, it is obvious to one of ordinary skill in the art before the effective filling date of the claimed invention to apply the non-codebook in the patent. By doing so, employing SRS configuration and indication in a network system. Dependent claims 2-11 and 14 (not shown in the table) are rejected being obviousness over claims 2-13 of the patent.
Instant Application
U.S. Patent No. 11,539,407
U.S. Patent No. 12,057,903
Claim 1. A method performed by a user equipment (UE), the method comprising:
receiving a configuration from a network node via a higher layer, the configuration comprising at least two sounding reference signal (SRS) resource sets, wherein each SRS resource set comprises at least one SRS resource, and wherein the higher layer configuration of the SRS comprises a parameter usage and a value of the parameter is set to nonCodebook;
receiving a scheduling of at least one physical uplink shared channel (PUSCH) transmission from the network node via a downlink control information (DCI), wherein at least two SRS resources are indicated via a sounding reference signal resource indicator (SRI) field of the DCI, and wherein each SRS resource is associated with a different SRS resource set;
mapping a given SRI bit field of the SRI field to the SRS resources indicated from associated SRS resource sets; and
transmitting a PUSCH using antenna ports associated with the indicated SRS resources.
Claim 12. A network node comprising a processor and a memory, the memory containing instructions executable by the processor whereby the network node is configured to:
configure at least two sounding reference signal (SRS) resource sets for a user equipment via a higher layer, wherein each SRS resource set comprises at least one SRS resource, and wherein the higher layer configuration of the SRS comprises a parameter usage and the value of the parameter is set to nonCodebook;
schedule at least one physical uplink shared channel (PUSCH) transmission for the user equipment via a downlink control information (DCI), wherein at least two SRS resources are indicated via a sounding reference signal resource indicator (SRI) field of the DCI, wherein each SRS resource is associated with a different SRS resource set;
map a given SRI bit field of the SRI field to the SRS resources indicated from associated SRS resource sets; and
receive from the user equipment a PUSCH that is transmitted using antenna ports associated with the indicated SRS resources.
Claim 13. A user equipment (UE) comprising a processor and a memory, the memory containing instructions executable by the processor whereby the UE is configured to:
receive a configuration from a network node via a higher layer, the configuration comprising at least two sounding reference signal (SRS) resource sets, wherein each SRS resource set comprises at least one SRS resource, and wherein the higher layer configuration of the SRS comprises a parameter usage and a value of the parameter is set to nonCodebook;
receive a scheduling of at least one physical uplink shared channel (PUSCH) transmission from the network node via a downlink control information (DCI), wherein at least two SRS resources are indicated via a sounding reference signal resource indicator (SRI) field of the DCI, wherein each SRS resource is associated with a different SRS resource set;
map a given SRI bit field of the SRI field to the SRS resources indicated from associated SRS resource sets; and
transmit a PUSCH using the antenna ports associated with the indicated SRS resources.
Claim 15. A method performed by a network node, the method comprising:
configuring at least two sounding reference signal (SRS) resource sets for a user equipment via a higher layer, wherein each SRS resource set comprises at least one SRS resource, and wherein the higher layer configuration of the SRS comprises a parameter usage and a value of the parameter is set to nonCodebook;
scheduling at least one physical uplink shared channel (PUSCH) transmission for the user equipment via a downlink control information (DCI), wherein at least two SRS resources are indicated via a sounding reference signal resource indicator (SRI) field of the DCI, and wherein each SRS resource is associated with a different SRS resource set;
mapping a given SRI bit field of the SRI field to the SRS resources indicated from associated SRS resource sets; and
receiving from the user equipment a PUSCH that is transmitted using antenna ports associated with the indicated SRS resources.
Claim 1. A method performed by a network node, the method comprising:
configuring at least two sounding reference signal (SRS) resource sets for a user equipment via a higher layer, wherein each SRS resource set comprises at least one SRS resource, and wherein the higher layer configuration of the SRS comprises a parameter usage and the value of the parameter is set to nonCodebook or Codebook;
scheduling at least one physical uplink shared channel (PUSCH) transmission for said user equipment via a downlink control information (DCI) wherein at least two SRS resources are indicated via a sounding reference signal resource indicator (SRI) field of the DCI, wherein each SRS resource is associated with a different SRS resource set;
mapping a given SRI bit field of the SRI field to the SRS resources indicated from associated SRS resource sets; and
receiving from the user equipment a PUSCH that is transmitted using antenna ports associated with the indicated SRS resources, wherein, in the case when the usage is set to codebook, the DCI indicates as many transmitted precoding matrix index (TPMI) values as the number of SRS resources indicated via the SRI field of the DCI in which a first TPMI value indicates the precoder for the antenna ports corresponding to a first SRS resource and a second TPMI value indicates the precoder for the antenna ports corresponding to a second SRS resource and so on, and - wherein, in the case when the usage is set to nonCodebook, each SRS resource in the SRS resource set configuration is configured with only one port, and wherein each SRS port has a one-to-one mapping with a demodulation reference signal (DMRS) port and thereby, a transmission layer associated with said PUSCH.
Claim 12. A network node comprising a processor and a memory, said memory containing instructions executable by said processor whereby said network node is operative to:
configure at least two sounding reference signal (SRS) resource sets for a user equipment via a higher layer, wherein each SRS resource set comprises at least one SRS resource, and wherein the higher layer configuration of the SRS comprises a parameter usage and the value of the parameter is set to nonCodebook or Codebook;
schedule at least one physical uplink shared channel (PUSCH) transmission for said user equipment via a downlink control information (DCI) wherein at least two SRS resources are indicated via a sounding reference signal resource indicator (SRI) field of the DCI, wherein each SRS resource is associated with a different SRS resource set;
map a given SRI bit field of the SRI field to the SRS resources indicated from associated SRS resource sets; and
receive from the user equipment a PUSCH that is transmitted using antenna ports associated with the indicated SRS resources,
wherein, in the case when the usage is set to codebook, the DCI indicates as many transmitted precoding matrix index (TPMI) values as the number of SRS resources indicated via the SRI field of the DCI in which a first TPMI value indicates the precoder for the antenna ports corresponding to a first SRS resource and a second TPMI value indicates the precoder for the antenna ports corresponding to a second SRS resource and so on, and
wherein, in the case when the usage is set to nonCodebook, each SRS resource in the SRS resource set configuration is configured with only one port, and wherein each SRS port has a one-to-one mapping with a demodulation reference signal (DMRS) port and thereby, a transmission layer associated with said PUSCH.
Claim 13. A user equipment (UE) comprising a processor and a memory, said memory containing instructions executable by said processor whereby said UE is operative to be configured by a network node, the network node comprising a processor and a memory, said memory containing instructions executable by said processor whereby said network node is operative to:
configure at least two sounding reference signal (SRS) resource sets for the user equipment via a higher layer, wherein each SRS resource set comprises at least one SRS resource, and wherein the higher layer configuration of the SRS comprises a parameter usage and the value of the parameter is set to nonCodebook or Codebook;
schedule at least one physical uplink shared channel (PUSCH) transmission for said user equipment via a downlink control information (DCI) wherein at least two SRS resources are indicated via a sounding reference signal resource indicator (SRI) field of the DCI, wherein each SRS resource is associated with a different SRS resource set;
map a given SRI bit field of the SRI field to the SRS resources indicated from associated SRS resource sets; and
receive from the user equipment a PUSCH that is transmitted using antenna ports associated with the indicated SRS resources,
wherein, in the case when the usage is set to codebook, the DCI indicates as many transmitted precoding matrix index(TPMI) values as the number of SRS resources indicated via the SRI field of the DCI in which a first TPMI value indicates the precoder for the antenna ports corresponding to a first SRS resource and a second TPMI value indicates the precoder for the antenna ports corresponding to a second SRS resource and so on, and
wherein, in the case when the usage is set to nonCodebook, each SRS resource in the SRS resource set configuration is configured with only one port, and wherein each SRS port has a one-to-one mapping with a demodulation reference signal (DMRS) port and thereby, a transmission layer associated with said PUSCH.
Claim 14. A method performed by a user equipment (UE), the method comprising:
receiving a configuration from a network node, the configuration comprising:
configuring at least two sounding reference signal (SRS) resource sets for the user equipment via a higher layer, wherein each SRS resource set comprises at least one SRS resource, and wherein the higher layer configuration of the SRS comprises a parameter usage and the value of the parameter is set to nonCodebook or Codebook;
scheduling at least one physical uplink shared channel (PUSCH) transmission for said user equipment via a downlink control information (DCI) wherein at least two SRS resources are indicated via a sounding reference signal resource indicator (SRI) field of the DCI, wherein each SRS resource is associated with a different SRS resource set;
mapping a given SRI bit field of the SRI field to the SRS resources indicated from associated SRS resource sets;
receiving from the user equipment a PUSCH that is transmitted using antenna ports associated with the indicated SRS resources;
wherein, in the case when the usage is set to codebook, the DCI indicates as many transmitted precoding matrix index(TPMI) values as the number of SRS resources indicated via the SRI field of the DCI in which a first TPMI value indicates the precoder for the antenna ports corresponding to a first SRS resource and a second TPMI value indicates the precoder for the antenna ports corresponding to a second SRS resource and so on; and wherein, in the case when the usage is set to nonCodebook, each SRS resource in the SRS resource set configuration is configured with only one port, and wherein each SRS port has a one-to-one mapping with a demodulation reference signal (DMRS) port and thereby, a transmission layer associated with said PUSCH; and operating according to said received configuration.
Claim 1. A method performed by a user equipment (UE), the method comprising:
receiving a configuration from a network node via a higher layer, the configuration comprising at least two sounding reference signal (SRS) resource sets wherein each SRS resource set comprises at least one SRS resource, and wherein the higher layer configuration of the SRS comprises a parameter usage and the value of the parameter is set to Codebook (CB);
receiving a scheduling of at least one physical uplink shared channel (PUSCH) transmission from the network node via a downlink control information (DCI) wherein at least two SRS resources are indicated via a sounding reference signal resource indicator (SRI) field of the DCI, wherein each SRS resource is associated with a different SRS resource set;
mapping a given SRI bit field of the SRI field to the SRS resources indicated from associated SRS resource sets; and
transmitting a PUSCH using antenna ports associated with the indicated SRS resources.
Claim 12. A network node comprising a processor and a memory, the memory containing instructions executable by the processor whereby the network node is configured to:
configure at least two sounding reference signal (SRS) resource sets for a user equipment (UE) via a higher layer, wherein each SRS resource set comprises at least one SRS resource, and wherein the higher layer configuration of the SRS comprises a parameter usage and the value of the parameter is set to Codebook (CB);
schedule at least one physical uplink shared channel (PUSCH) transmission for said user equipment via a downlink control information (DCI) wherein at least two SRS resources are indicated via a sounding reference signal resource indicator (SRI) field of the DCI, wherein each SRS resource is associated with a different SRS resource set;
map a given SRI bit field of the SRI field to the SRS resources indicated from associated SRS resource sets; and
receive from the user equipment a PUSCH that is transmitted using antenna ports associated with the indicated SRS resources.
Claim 13. A user equipment (UE) comprising a processor and a memory, said memory containing instructions executable by said processor whereby said UE is configured to:
receive a configuration from a network node via a higher layer, the configuration comprising at least two sounding reference signal (SRS) resource sets wherein each SRS resource set comprises at least one SRS resource, and wherein the higher layer configuration of the SRS comprises a parameter usage and the value of the parameter is set to Codebook (CB);
receive a scheduling of at least one physical uplink shared channel (PUSCH) transmission from the network node via a downlink control information (DCI) wherein at least two SRS resources are indicated via a sounding reference signal resource indicator (SRI) field of the DCI, wherein each SRS resource is associated with a different SRS resource set;
map a given SRI bit field of the SRI field to the SRS resources indicated from associated SRS resource sets; and
transmit a PUSCH using the antenna ports associated with the indicated SRS resources.
Claim 14. A method performed by a network node, the method comprising:
configuring at least two sounding reference signal (SRS) resource sets for a user equipment (UE) via a higher layer, wherein each SRS resource set comprises at least one SRS resource, and wherein the higher layer configuration of the SRS comprises a parameter usage and the value of the parameter is set to Codebook (CB),
scheduling at least one physical uplink shared channel (PUSCH) transmission for said user equipment via a downlink control information (DCI) wherein at least two SRS resources are indicated via a sounding reference signal resource indicator (SRI) field of the DCI, wherein each SRS resource is associated with a different SRS resource set;
mapping a given SRI bit field of the SRI field to the SRS resources indicated from associated SRS resource sets; and
receiving from the user equipment a PUSCH that is
transmitted using antenna ports associated with the indicated SRS resources.
Conclusion
The prior art made of record and not relied upon is considered pertinent to applicant's disclosure. US 2020/0322187 He et al disclose SRS transmission. US 2022/0224567 Zhang et al disclose controlling SRS.
Any inquiry concerning this communication or earlier communications from the examiner should be directed to Eva Y Puente whose telephone number is 571-272-3049. The examiner can normally be reached on M-F, 7:30 AM to 5:00 PM.
If attempts to reach the examiner by telephone are unsuccessful, the examiner’s supervisor, Chieh Fan can be reached on 571-272-3042. The fax phone number for the organization where this application or proceeding is assigned is 571-273-8300. Information regarding the status of an application may be obtained from the Patent Application Information Retrieval (PAIR) system. Status information for published applications may be obtained from either Private PAIR or Public PAIR. Status information for unpublished applications is available through Private PAIR only. For more information about the PAIR system, see http://pair-direct.uspto.gov. Should you have questions on access to the Private PAIR system, contact the Electronic Business Center (EBC) at 866-217-9197 (toll-free). October 9, 2025
/EVA Y PUENTE/ Primary Examiner, Art Unit 2632