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 .
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 5/6/2026 has been entered.
Priority
Receipt is acknowledged of certified copies of papers required by 37 CFR 1.55.
Response to Arguments
Applicant’s amendments with respect to the specification have been fully considered. The objection of the specification has been withdrawn.
Applicant’s arguments with respect to claim(s) 1-3 have been fully considered, a new ground for rejection has been made in view of amendment. Claims 1-3 are rejected under 35 U.S.C 103 (See 103 rejection of claims 1 and 2 below).
Claim Rejections - 35 USC § 103
In the event the determination of the status of the application as subject to AIA 35 U.S.C. 102 and 103 (or as subject to pre-AIA 35 U.S.C. 102 and 103) is incorrect, any correction of the statutory basis (i.e., changing from AIA to pre-AIA ) for the rejection will not be considered a new ground of rejection if the prior art relied upon, and the rationale supporting the rejection, would be the same under either status.
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.
The factual inquiries for establishing a background for determining obviousness under 35 U.S.C. 103 are summarized as follows:
1. Determining the scope and contents of the prior art.
2. Ascertaining the differences between the prior art and the claims at issue.
3. Resolving the level of ordinary skill in the pertinent art.
4. Considering objective evidence present in the application indicating obviousness or nonobviousness.
This application currently names joint inventors. In considering patentability of the claims the examiner presumes that the subject matter of the various claims was commonly owned as of the effective filing date of the claimed invention(s) absent any evidence to the contrary. Applicant is advised of the obligation under 37 CFR 1.56 to point out the inventor and effective filing dates of each claim that was not commonly owned as of the effective filing date of the later invention in order for the examiner to consider the applicability of 35 U.S.C. 102(b)(2)(C) for any potential 35 U.S.C. 102(a)(2) prior art against the later invention.
Claim(s) 1-3 is/are rejected under 35 U.S.C. 103 as being unpatentable over US 20220095346 A1 (hereinafter Khoshnevisan) (priority document us-provisional-application US 63081147 20200921, hereinafter prov), in view of US 20210297191 A1 (hereinafter Takeda).
Regarding claim 1, Khoshnevisan teaches A terminal apparatus comprising (Khoshnevisan Fig. 1;
[0026] The wireless communications system includes base stations 102, UEs 104 (prov Fig. 1, [0023]).
[0028] The base stations 102 may wirelessly communicate with the UEs 104 (prov [0025]).
Fig. 9 apparatus 902; [0082] The apparatus 902 may be a UE (prov Fig. 8, [0069]).):
reception circuitry configured to receive a physical downlink control channel (PDCCH) to which
a downlink control information (DCI) format is mapped (Khoshnevisan
Fig. 9, reception component 930; [0083] The reception component 830 is configured to receive a PUCCH resource configuration associated with a PUCCH resource (prov [0070]).[0078] the UE may receive DCI scheduling the PUCCH transmission. The DCI indicates the PUCCH resource associated with the PUCCH resource configuration (prov [0067]).
[0047] The physical downlink control channel (PDCCH) carries DCI. A UE is configured to monitor PDCCH candidates in a PDCCH search space (e.g., common search space, UE-specific search space) during PDCCH monitoring occasions on the CORESET, where the PDCCH candidates have different DCI formats and different aggregation levels (prov [0041]).
); and
transmission circuitry configured to transmit a physical uplink control channel (PUCCH) corresponding to a PUCCH resource indicated based on the DCI format (Khoshnevisan Fig. 9, transmission component 934; [0078] the UE may receive DCI scheduling the PUCCH transmission. The DCI indicates the PUCCH resource associated with the PUCCH resource configuration (prov Fig. 8; [0067]).
[0070] the UE 602 transmits a PUCCH 608 in the PUCCH resource based on the at least one of the PUCCH resource repetition configuration 406a or the PUCCH resource inter-slot frequency hopping configuration 406b configured in the PUCCH resource configuration (prov [0062]).),
Wherein: a first higher layer parameter is configured for a PUCCH format corresponding to the PUCCH (Khoshnevisan Fig. 4; [0059] FIG. 4 is a diagram 400 illustrating PUCCH formats 402, a PUCCH format configuration IE 404, and a PUCCH resource IE 406 (prov Fig. 4, [0052]).
[0061] PUCCH repetition in different slots may be supported for PUCCH formats 1, 3, and 4. A number of PUCCH repetitions is RRC configured for a given PUCCH format through the field nrofSlots (2, 4, or 8 slots) within the PUCCH format configuration IE 404. The format field nrofSlots may be referred to as a PUCCH format repetition configuration 404a. As the PUCCH format configuration IE 404 configures a format with the same PUCCH format repetition configuration 404a, all PUCCH resources with that format will have the same PUCCH format repetition configuration 404a (i.e., the same number of PUCCH repetitions) (prov [0054]).),
in a case that a second higher layer parameter is configured for the PUCCH resource, a number of repetitions of the PUCCH is a value of the second higher layer parameter (Khoshnevisan
[0064] a number of PUCCH repetitions and/or inter-slot (or inter-repetition) frequency hopping can be RRC configured per PUCCH resource configuration (e.g., instead of per PUCCH format, or overriding the configuration per PUCCH format). For example, the PUCCH resource IE 406 may provide a PUCCH resource configuration associated with a PUCCH resource. The PUCCH resource configuration for the PUCCH resource may indicate a PUCCH resource repetition configuration 406a through, for example, the field nrofSlots (indicated in bold), and/or a PUCCH resource inter-slot frequency hopping configuration 406b through, for example, the field interslotFrequencyHopping (indicated in bold). Both the PUCCH resource repetition configuration 406a and the PUCCH resource inter-slot frequency hopping configuration 406b are specifically for the PUCCH resource and are independent of PUCCH formats (prov [0057]).
[0072]while the PUCCH resource repetition configuration 406a and the PUCCH resource inter-slot frequency hopping configuration 406b are configured semi-statically through RRC signaling, multiple different PUCCH resource IEs may define different PUCCH resources with different configurations of the PUCCH repetition/PUCCH inter-slot frequency hopping, and the UE 602 may be configured with PUCCH repetition/PUCCH inter-slot frequency hopping dynamically through a received DCI 606 that indicates the PUCCH resource (prov [0064]).)
and the first higher layer parameter is ignored (Khoshnevisan [0067] With respect to conflict resolution of a legacy RRC configuration through the PUCCH format configuration IE 404 versus the RRC configuration through the PUCCH resource IE 406, if the number of PUCCH repetitions/PUCCH inter-slot frequency hopping (enabled or disabled) is configured for a PUCCH format, a UE may determine whether to use the PUCCH format repetition configuration 404a or the PUCCH resource repetition configuration 406a. If a PUCCH resource that is configured with that PUCCH format is configured, via RRC, or activated, via MAC-CE, with a different number of PUCCH repetitions or a different configuration of PUCCH inter-slot frequency hopping, the UE may override the PUCCH format repetition configuration 404a with the PUCCH resource repetition configuration 406a (prov [0060]).).
in a case that the second higher layer parameter is not configured, the number of repetitions of the PUCCH is a value of the first higher layer parameter (Khoshnevisan [0067] If a PUCCH resource that is configured with that PUCCH format is not configured or activated with a number of PUCCH repetitions or a configuration of PUCCH inter-slot frequency hopping, in a first configuration, the RRC configuration of the PUCCH format may be assumed (for PUCCH repetition and/or PUCCH inter-slot frequency hopping) when PUCCH is transmitted using the PUCCH resource (prov [0060]).),
the value of the second higher layer parameter is indicated based on the DCI format (Khoshnevisan [0064] a number of PUCCH repetitions and/or inter-slot (or inter-repetition) frequency hopping can be RRC configured per PUCCH resource configuration (e.g., instead of per PUCCH format, or overriding the configuration per PUCCH format). For example, the PUCCH resource IE 406 may provide a PUCCH resource configuration associated with a PUCCH resource. The PUCCH resource configuration for the PUCCH resource may indicate a PUCCH resource repetition configuration 406a through, for example, the field nrofSlots (indicated in bold), and/or a PUCCH resource inter-slot frequency hopping configuration 406b through, for example, the field interslotFrequencyHopping (indicated in bold). Both the PUCCH resource repetition configuration 406a and the PUCCH resource inter-slot frequency hopping configuration 406b are specifically for the PUCCH resource and are independent of PUCCH formats (prov [0057]).
[0065] DCI may include a PRI field that indicates a PUCCH resource with a number of PUCCH repetitions. Accordingly, dynamic indication of the number of PUCCH repetitions may be achieved by dynamic indication of a PUCCH resource (prov [0058]).),
the value of the first higher layer parameter is any of 2, 4, and 8 (Khoshnevisan Fig. 4; [0059] FIG. 4 is a diagram 400 illustrating PUCCH formats 402, a PUCCH format configuration IE 404, and a PUCCH resource IE 406 (prov Fig. 4, [0052])
[0061] PUCCH repetition in different slots may be supported for PUCCH formats 1, 3, and 4. A number of PUCCH repetitions is RRC configured for a given PUCCH format through the field nrofSlots (2, 4, or 8 slots) within the PUCCH format configuration IE 404. (prov [0054])),
the value of the second higher layer parameter is any of 1, 2, 4, and 8 (Khoshnevisan Fig. 4; [0059] FIG. 4 is a diagram 400 illustrating PUCCH formats 402, a PUCCH format configuration IE 404, and a PUCCH resource IE 406 (prov Fig. 4, [0052])
[0064] the PUCCH resource IE 406 may provide a PUCCH resource configuration associated with a PUCCH resource. The PUCCH resource configuration for the PUCCH resource may indicate a PUCCH resource repetition configuration 406a through, for example, the field nrofSlots (indicated in bold). (prov [0057])
As shown in Fig. 4, PUCCH resource repetition configuration 406a, nrofSlots can have values 2, 4 and 8.),
Although Khoshnevisan teaches in a case that the number of repetitions of the PUCCH, having a value of N, is greater than 1, the transmission circuitry repeats the PUCCH transmission in N slots (Khoshnevisan [0064] the PUCCH resource IE 406 may provide a PUCCH resource configuration associated with a PUCCH resource. The PUCCH resource configuration for the PUCCH resource may indicate a PUCCH resource repetition configuration 406a through, for example, the field nrofSlots (indicated in bold). (prov [0057])
[0070] A UE 602 receives, from a base station 604, a PUCCH resource configuration 406 (in a PUCCH resource IE) associated with a PUCCH resource. The PUCCH resource configuration 406 indicates at least one of a PUCCH resource repetition configuration (e.g., 406a). the UE 602 transmits a PUCCH 608 in the PUCCH resource based on the at least one of the PUCCH resource repetition configuration 406a (prov [0062]).), Khoshnevisan does not explicitly teach and the N slots are not continuous.
Takeda in the same or similar field of endeavor teaches and the N slots are not continuous (Takeda [0063] The UE may repeat the UCI, which is transmitted by PUCCH in the first slot of the number of repetitions, even in the remaining slots of the number of repetitions. The number of symbols for PUCCH and the starting symbol may be the same in each slot to which the repetition is applied. Note that the PUCCH repetition may be performed in continuous slots or in non-continuous slots.).
By modifying Khoshnevisan’s teachings of in a case that the number of repetitions of the PUCCH, having a value of N, is greater than 1, the transmission circuitry repeats the PUCCH transmission in N slots with Takeda’s teachings of and the N slots are not continuous, the modification results in
in a case that the number of repetitions of the PUCCH, having a value of N, is greater than 1, the transmission circuitry repeats the PUCCH transmission in N slots, and the N slots are not continuous.
It would have been prima facie obvious to one of ordinary skill in the art before the effective
filing date of the claimed invention to have modified Khoshnevisan with Takeda’s above teachings. The motivation is appropriately transmitting the UCI when the PUCCH repetition is used (Takeda [0011]).
Claim 3 recites similar limitations of claim 1, is thus rejected under similar rational.
Regarding claim 2, Khoshnevisan teaches A base station apparatus comprising (Khoshnevisan
Fig. 1; [0026] The wireless communications system includes base stations 102, UEs 104 (prov Fig. 1, [0023]). [0028] The base stations 102 may wirelessly communicate with the UEs 104 (prov [0025]).):
transmission circuitry configured to transmit a physical downlink control channel (PDCCH) to
which a downlink control information (DCI) format is mapped
(Khoshnevisan Fig. 3, TX processor 316; [0050] FIG. 3 is a block diagram of a base station 310 in communication with a UE 350 in an access network (prov Fig. 3, [0044]).
[0078] the UE may receive DCI scheduling the PUCCH transmission. The DCI indicates the PUCCH resource associated with the PUCCH resource configuration (prov [0067]).
[0047] The physical downlink control channel (PDCCH) carries DCI. A UE is configured to monitor PDCCH candidates in a PDCCH search space (e.g., common search space, UE-specific search space) during PDCCH monitoring occasions on the CORESET, where the PDCCH candidates have different DCI formats and different aggregation levels (prov [0041]).); and
reception circuitry configured to receive a physical uplink control channel (PUCCH)
corresponding to a PUCCH resource indicated based on the DCI format (Khoshnevisan Fig. 3, RX processor 370; [0078] the UE may receive DCI scheduling the PUCCH transmission. The DCI indicates the PUCCH resource associated with the PUCCH resource configuration (prov Fig. 3; [0067]).
[0070] the UE 602 transmits a PUCCH 608 in the PUCCH resource based on the at least one of the PUCCH resource repetition configuration 406a or the PUCCH resource inter-slot frequency hopping configuration 406b configured in the PUCCH resource configuration (prov [0062]).),
wherein: a first higher layer parameter is configured for a PUCCH format corresponding to the PUCCH (Khoshnevisan Fig. 4; [0059] FIG. 4 is a diagram 400 illustrating PUCCH formats 402, a PUCCH format configuration IE 404, and a PUCCH resource IE 406 (prov Fig. 4, [0052]).
[0061] PUCCH repetition in different slots may be supported for PUCCH formats 1, 3, and 4. A number of PUCCH repetitions is RRC configured for a given PUCCH format through the field nrofSlots (2, 4, or 8 slots) within the PUCCH format configuration IE 404. The format field nrofSlots may be referred to as a PUCCH format repetition configuration 404a. As the PUCCH format configuration IE 404 configures a format with the same PUCCH format repetition configuration 404a, all PUCCH resources with that format will have the same PUCCH format repetition configuration 404a (i.e., the same number of PUCCH repetitions) (prov [0054]).),
in a case that a second higher layer parameter is configured for the PUCCH resource, a number of repetitions of the PUCCH is a value of the second higher layer parameter (Khoshnevisan
[0064] a number of PUCCH repetitions and/or inter-slot (or inter-repetition) frequency hopping can be RRC configured per PUCCH resource configuration (e.g., instead of per PUCCH format, or overriding the configuration per PUCCH format). For example, the PUCCH resource IE 406 may provide a PUCCH resource configuration associated with a PUCCH resource. The PUCCH resource configuration for the PUCCH resource may indicate a PUCCH resource repetition configuration 406a through, for example, the field nrofSlots (indicated in bold), and/or a PUCCH resource inter-slot frequency hopping configuration 406b through, for example, the field interslotFrequencyHopping (indicated in bold). Both the PUCCH resource repetition configuration 406a and the PUCCH resource inter-slot frequency hopping configuration 406b are specifically for the PUCCH resource and are independent of PUCCH formats (prov [0057]).
[0072]while the PUCCH resource repetition configuration 406a and the PUCCH resource inter-slot frequency hopping configuration 406b are configured semi-statically through RRC signaling, multiple different PUCCH resource IEs may define different PUCCH resources with different configurations of the PUCCH repetition/PUCCH inter-slot frequency hopping, and the UE 602 may be configured with PUCCH repetition/PUCCH inter-slot frequency hopping dynamically through a received DCI 606 that indicates the PUCCH resource (prov [0064]).)
and the first higher layer parameter is ignored (Khoshnevisan [0067] With respect to conflict resolution of a legacy RRC configuration through the PUCCH format configuration IE 404 versus the RRC configuration through the PUCCH resource IE 406, if the number of PUCCH repetitions/PUCCH inter-slot frequency hopping (enabled or disabled) is configured for a PUCCH format, a UE may determine whether to use the PUCCH format repetition configuration 404a or the PUCCH resource repetition configuration 406a. If a PUCCH resource that is configured with that PUCCH format is configured, via RRC, or activated, via MAC-CE, with a different number of PUCCH repetitions or a different configuration of PUCCH inter-slot frequency hopping, the UE may override the PUCCH format repetition configuration 404a with the PUCCH resource repetition configuration 406a (prov [0060]).),
in a case that the second higher layer parameter is not configured, the number of repetitions of the PUCCH is a value of the first higher layer parameter (Khoshnevisan [0067] If a PUCCH resource that is configured with that PUCCH format is not configured or activated with a number of PUCCH repetitions or a configuration of PUCCH inter-slot frequency hopping, in a first configuration, the RRC configuration of the PUCCH format may be assumed (for PUCCH repetition and/or PUCCH inter-slot frequency hopping) when PUCCH is transmitted using the PUCCH resource (prov [0060]).),
the value of the second higher layer parameter is indicated based on the DCI format (Khoshnevisan [0064] a number of PUCCH repetitions and/or inter-slot (or inter-repetition) frequency hopping can be RRC configured per PUCCH resource configuration (e.g., instead of per PUCCH format, or overriding the configuration per PUCCH format). For example, the PUCCH resource IE 406 may provide a PUCCH resource configuration associated with a PUCCH resource. The PUCCH resource configuration for the PUCCH resource may indicate a PUCCH resource repetition configuration 406a through, for example, the field nrofSlots (indicated in bold), and/or a PUCCH resource inter-slot frequency hopping configuration 406b through, for example, the field interslotFrequencyHopping (indicated in bold). Both the PUCCH resource repetition configuration 406a and the PUCCH resource inter-slot frequency hopping configuration 406b are specifically for the PUCCH resource and are independent of PUCCH formats (prov [0057]).
[0065] DCI may include a PRI field that indicates a PUCCH resource with a number of PUCCH repetitions. Accordingly, dynamic indication of the number of PUCCH repetitions may be achieved by dynamic indication of a PUCCH resource (prov [0058]).),
the value of the first higher layer parameter is any of 2, 4, and 8 (Khoshnevisan Fig. 4; [0059] FIG. 4 is a diagram 400 illustrating PUCCH formats 402, a PUCCH format configuration IE 404, and a PUCCH resource IE 406 (prov Fig. 4, [0052])
[0061] PUCCH repetition in different slots may be supported for PUCCH formats 1, 3, and 4. A number of PUCCH repetitions is RRC configured for a given PUCCH format through the field nrofSlots (2, 4, or 8 slots) within the PUCCH format configuration IE 404. (prov [0054])),
the value of the second higher layer parameter is any of 1, 2, 4, and 8 (Khoshnevisan Fig. 4; [0059] FIG. 4 is a diagram 400 illustrating PUCCH formats 402, a PUCCH format configuration IE 404, and a PUCCH resource IE 406 (prov Fig. 4, [0052])
[0064] the PUCCH resource IE 406 may provide a PUCCH resource configuration associated with a PUCCH resource. The PUCCH resource configuration for the PUCCH resource may indicate a PUCCH resource repetition configuration 406a through, for example, the field nrofSlots (indicated in bold). (prov [0057])
As shown in Fig. 4, PUCCH resource repetition configuration 406a, nrofSlots can have values 2, 4 and 8.),
Although Khoshnevisan teaches in a case that the number of repetitions of the PUCCH, having a value of N, is greater than 1, the transmission circuitry repeats the PUCCH transmission in N slots (Khoshnevisan [0064] the PUCCH resource IE 406 may provide a PUCCH resource configuration associated with a PUCCH resource. The PUCCH resource configuration for the PUCCH resource may indicate a PUCCH resource repetition configuration 406a through, for example, the field nrofSlots (indicated in bold). (prov [0057])
[0070] A UE 602 receives, from a base station 604, a PUCCH resource configuration 406 (in a PUCCH resource IE) associated with a PUCCH resource. The PUCCH resource configuration 406 indicates at least one of a PUCCH resource repetition configuration (e.g., 406a). the UE 602 transmits a PUCCH 608 in the PUCCH resource based on the at least one of the PUCCH resource repetition configuration 406a (prov [0062]).), Khoshnevisan does not explicitly teach and the N slots are not continuous.
Takeda in the same or similar field of endeavor teaches and the N slots are not continuous (Takeda [0063] The UE may repeat the UCI, which is transmitted by PUCCH in the first slot of the number of repetitions, even in the remaining slots of the number of repetitions. The number of symbols for PUCCH and the starting symbol may be the same in each slot to which the repetition is applied. Note that the PUCCH repetition may be performed in continuous slots or in non-continuous slots.).
By modifying Khoshnevisan’s teachings of in a case that the number of repetitions of the PUCCH, having a value of N, is greater than 1, the transmission circuitry repeats the PUCCH transmission in N slots with Takeda’s teachings of and the N slots are not continuous, the modification results in
in a case that the number of repetitions of the PUCCH, having a value of N, is greater than 1, the transmission circuitry repeats the PUCCH transmission in N slots, and the N slots are not continuous.
It would have been prima facie obvious to one of ordinary skill in the art before the effective
filing date of the claimed invention to have modified Khoshnevisan with Takeda’s above teachings. The motivation is appropriately transmitting the UCI when the PUCCH repetition is used (Takeda [0011]).
Conclusion
Any inquiry concerning this communication or earlier communications from the examiner should be directed to David Z Sun whose telephone number is (571)270-0750. The examiner can normally be reached Monday-Friday 0800am-0500pm.
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, Moo Jeong can be reached at 571-272-9617. 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.
/D.Z.S./Examiner, Art Unit 2418
/Moo Jeong/Supervisory Patent Examiner, Art Unit 2418
Prosecution Insights