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
Receipt is acknowledged of certified copies of papers required by 37 CFR 1.55.
Response to Arguments
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 102 (See 102 rejection of claims 1 and 2 below).
Specification
The title of the invention is not descriptive. A new title is required that is clearly indicative of the invention to which the claims are directed.
Claim Rejections - 35 USC § 102
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 the appropriate paragraphs of 35 U.S.C. 102 that form the basis for the rejections under this section made in this Office action:
A person shall be entitled to a patent unless –
(a)(1) the claimed invention was patented, described in a printed publication, or in public use, on sale, or otherwise available to the public before the effective filing date of the claimed invention.
(a)(2) the claimed invention was described in a patent issued under section 151, or in an application for patent published or deemed published under section 122(b), in which the patent or application, as the case may be, names another inventor and was effectively filed before the effective filing date of the claimed invention.
Claim(s) 1-3 is/are rejected under 35 U.S.C. 102 (a)(2) as being anticipated by US 20220095346 A1 (hereinafter Khoshnevisan) (priority document us-provisional-application US 63081147 20200921, hereinafter prov).
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]).),
and 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]).).
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]).),
and 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]).).
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 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