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 .
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.
Claim(s) 1 and 3-4 is/are rejected under 35 U.S.C. 103 as being unpatentable over Takeda [US 2022/0216972] in view of Yi [US 2020/0337029].
As claims 1 and 3, Takeda discloses a method by a user equipment (UE), comprising: receiving, from a base station, a first radio resource control (RRC) parameter, the first RRC parameter corresponding to a configuration of a specific search space (SS) set [Par. 0024-0027, 0030-0031, 0048-0049 disclose UE receives, from base station, a RRC parameter “searchspace” which indicates USS set information], the first RRC parameter including both a second RRC parameter and a third RRC parameter [Par. 0027 discloses the first parameter “USS searchspace” includes second parameter “USS Set # 1 has searchspace id = 1” and third parameter “USS Set # 3 has search space id = 3”, Par. 0027, 0030-0031, 0048-0049, IE (8) discloses USS set information], the second RRC parameter indicating a first pair of Downlink Control Information (DCI) formats to be monitored in a UE-specific search space (USS) set [Par. 0030-0031 discloses USS set # 1 for monitoring DCI formats 0_0, 1_0, First pair, Par. 0027, IE (8) discloses USS set information, DCI formats 0_0, 1_0, First pair], the third RRC parameter indicating a second pair of DCI formats to be monitored in a USS set [Par. 0031, 0048-0049 discloses USS set # 3 for monitoring DCI formats, Second pair, Par. 0027, IE (8) discloses USS set information, DCI formats 0_2, 1_2, Second pair], and the second RRC parameter being different from the third RRC parameter [Fig 2, 4 and 8-9 discloses the second parameter “searchspaceid = 1” which indicates first pair is different from third parameter “searchspaceid = 3” which indicates second pair wherein first pair 0_0, 1_0 is different from second pair 0_2, 1_2], wherein the first pair of DCI formats indicated by a fourth RRC parameter to be monitored in a common search space (CSS) set [Par. 0028 discloses CSS “four parameter” for monitoring DCI formats 0_0, 1_0, First pair, Par. 0027-0028, IE (7) discloses CSS set information, DCI formats 0_0, 1_0], the second pair of DCI formats not indicated by the fourth RRC parameter to be monitored in a CSS set [Par. 0028 discloses “four parameter” DCI formats 0_2 and 1_2 not configured for monitoring in CSS], and each of the first pair of DCI formats and the second pair of DCI formats includes a DCI format for scheduling of physical downlink shared channel (PDSCH) and a DCI format for scheduling of physical uplink shared channel (PUSCH) [Par. 0032, 0041-0042, 0048-0049 discloses DCI formats 0_0, 1_0 “first pair” for PDSCH and PUSCH and 0_2, 1_2 “second pair” for PDSCH and PUSCH]; the first pair of DCI formats is DCI format 0 0 and DCI format 1_0 [Par. 0032, 0041-0042 discloses DCI formats 0_0, 1_0 “first pair”], and the second pair of DCI formats is DCI format 0_2 and DCI format 1_2 [Par. 0032, 0041-0042 discloses DCI formats 0_2, 1_2 “second pair”]. However, Takeda fails to fully disclose the first parameter which includes second parameter and third parameter and the first RRC parameter, the second RRC parameter, and the third parameter correspond to a same search space ID. In the same field of endeavor, Yi discloses first parameter which includes second parameter and third parameter the first RRC parameter, the second RRC parameter, and the third parameter correspond to a same search space ID [Par. 0346 discloses SS #1 “search space ID” which includes the first RRC parameter, the second RRC parameter, and the third parameter and first parameter “search space ID” which includes second parameter “source” and third parameter “target”, Fig 27 discloses SS2 “search space ID # 2 “first parameter” which includes USS for 0_2, 1_2 and 0_0, 1_0].
Since, a method and system for using bits to indicate first and second value etc… are well known and expected in the art. Therefore, it would have been obvious to one of ordinary skill in the art before the effective filing date of claimed invention to apply a method and system comprising a search space ID for the first, second and third parameter as disclosed by Yi into the teaching of Taketa. The motivation would have been to increase the capacity of monitoring the control channel.
As claim 4, Takeda discloses a base station, comprising: transmitting, by transmission circuit, to a user equipment (UE), a first radio resource control (RRC) parameter, the first RRC parameter corresponding to a configuration of a specific search space (SS) set [Par. 0024-0027, 0030-0031, 0048-0049 disclose UE receives, from base station, a RRC parameter which indicates USS search space set], the first RRC parameter including both of a second RRC parameter and a third RRC parameter [Par. 0027 discloses the first parameter “USS searchspace” includes second parameter “USS Set # 1 has searchspace id = 1” and third parameter “USS Set # 3 has search space id = 3”, Par. 0027, 0030-0031, 0048-0049, IE (8) discloses USS set information] the second RRC parameter indicating a first pair of Downlink Control Information (DCI) formats to be monitored in a UE-specific search space (USS) set [Par. 0030-0031 discloses USS set # 1 for monitoring DCI formats 0_0, 1_0, first pair, Par. 0027, IE (8) discloses USS set information, DCI formats 0_1, 1_0, first pair], the third RRC parameter indicating a second pair of DCI formats to be monitored in a USS set [Par. 0030-0031, 0048-0049 discloses USS set # 3 for monitoring DCI formats 0_2, 1_2, Second pair, Par. 0027, 0048-0049, IE (8) discloses USS set information, DCI formats 0_2, 1_2, Second pair] and the second RRC parameter being different from the third RRC parameter [Fig 2, 4 and 8-9 discloses the second parameter “searchspaceid = 1” which indicates first pair is different from third parameter “searchspaceid = 3” which indicates second pair wherein first pair is different from second pair], wherein the first pair of DCI formats indicated by a fourth RRC parameter to be monitored in a common search space (CSS) set [Par. 0028 discloses CSS “four parameter” for monitoring DCI formats 0_0, 1_0, First pair], the second pair of DCI formats not indicated by the fourth RRC parameter to be monitored in a CSS set [Par. 0028 discloses CSS “four parameter” DCI formats 0_1 and 1_0, first pair and DCI formats 0_2, 1_2, Second pair not configured for monitoring in CSS], and each of the first pair of DCI formats and the second pair of DCI formats includes a DCI format for scheduling of physical downlink shared channel (PDSCH) and a DCI format for scheduling of physical uplink shared channel (PUSCH) [Par. 0032, 0048-0049 discloses DCI formats 0_0, 1_0 “first pair” for PDSCH and PUSCH and DCI formats 0_2, 1_2, “second pair” for PDSCH and PUSCH]; the first pair of DCI formats is DCI format 0 0 and DCI format 1 0 [Par. 0032, 0041-0042 discloses DCI formats 0_0, 1_0 “first pair”], and the second pair of DCI formats is DCI format 0_2 and DCI format 1_2 [Par. 0032, 0041-0042 discloses DCI formats 0_2, 1_2 “second pair”]. However, Takeda fails to fully disclose the first parameter which includes second parameter and third parameter and the first RRC parameter, the second RRC parameter, and the third parameter correspond to a same search space ID. In the same field of endeavor, Chatterjee discloses first parameter which includes second parameter and third parameter [Par. 0055, 0227, 0228-0229, 0266, 0278, 0281 discloses a field with two bits to indicate second parameter and third parameter for DCI formats 0_0, 1_0 “first pair = first bit = 1, for USS” and 0_2, 1_2 “second pair = second bit = 1, for USS” and for CSS “ first bit = 1 for first pair and second bit = 0 for second pair, zero for not configured]. However, Takeda fails to fully disclose the first parameter which includes second parameter and third parameter and the first RRC parameter, the second RRC parameter, and the third parameter correspond to a same search space ID. In the same field of endeavor, Yi discloses first parameter which includes second parameter and third parameter the first RRC parameter, the second RRC parameter, and the third parameter correspond to a same search space ID [Par. 0346 discloses SS #1 “search space ID” which includes the first RRC parameter, the second RRC parameter, and the third parameter and first parameter “search space ID” which includes second parameter “source” and third parameter “target”, Fig 27 discloses SS2 “search space ID # 2 “first parameter” which includes USS for 0_2, 1_2 and 0_0, 1_0].
Since, a method and system for using bits to indicate first and second value etc… are well known and expected in the art. Therefore, it would have been obvious to one of ordinary skill in the art before the effective filing date of claimed invention to apply a method and system comprising a search space ID for the first, second and third parameter as disclosed by Yi into the teaching of Taketa. The motivation would have been to increase the capacity of monitoring the control channel.
Claim(s) 1 and 3-4 is/are rejected under 35 U.S.C. 103 as being unpatentable over Takeda [US 2022/0216972] in view of Chatterjee [US 2019/0274032] and Yi [US 2020/0337029].
As claims 1 and 3, Takeda discloses a method by a user equipment (UE), comprising: receiving, from a base station, a first radio resource control (RRC) parameter, the first RRC parameter corresponding to a configuration of a specific search space (SS) set [Par. 0024-0027, 0030-0031, 0048-0049 disclose UE receives, from base station, a RRC parameter “searchspace” which indicates USS set information], the first RRC parameter including both a second RRC parameter and a third RRC parameter [Par. 0027 discloses the first parameter “USS searchspace” includes second parameter “USS Set # 1 has searchspace id = 1” and third parameter “USS Set # 3 has search space id = 3”, Par. 0027, 0030-0031, 0048-0049, IE (8) discloses USS set information], the second RRC parameter indicating a first pair of Downlink Control Information (DCI) formats to be monitored in a UE-specific search space (USS) set [Par. 0030-0031 discloses USS set # 1 for monitoring DCI formats 0_0, 1_0, First pair, Par. 0027, IE (8) discloses USS set information, DCI formats 0_0, 1_0, First pair], the third RRC parameter indicating a second pair of DCI formats to be monitored in a USS set [Par. 0031, 0048-0049 discloses USS set # 3 for monitoring DCI formats, Second pair, Par. 0027, IE (8) discloses USS set information, DCI formats 0_2, 1_2, Second pair], and the second RRC parameter being different from the third RRC parameter [Fig 2, 4 and 8-9 discloses the second parameter “searchspaceid = 1” which indicates first pair is different from third parameter “searchspaceid = 3” which indicates second pair wherein first pair 0_0, 1_0 is different from second pair 0_2, 1_2], wherein the first pair of DCI formats indicated by a fourth RRC parameter to be monitored in a common search space (CSS) set [Par. 0028 discloses CSS “four parameter” for monitoring DCI formats 0_0, 1_0, First pair, Par. 0027-0028, IE (7) discloses CSS set information, DCI formats 0_0, 1_0], the second pair of DCI formats not indicated by the fourth RRC parameter to be monitored in a CSS set [Par. 0028 discloses “four parameter” DCI formats 0_2 and 1_2 not configured for monitoring in CSS], and each of the first pair of DCI formats and the second pair of DCI formats includes a DCI format for scheduling of physical downlink shared channel (PDSCH) and a DCI format for scheduling of physical uplink shared channel (PUSCH) [Par. 0032, 0041-0042, 0048-0049 discloses DCI formats 0_0, 1_0 “first pair” for PDSCH and PUSCH and 0_2, 1_2 “second pair” for PDSCH and PUSCH]; the first pair of DCI formats is DCI format 0 0 and DCI format 1_0 [Par. 0032, 0041-0042 discloses DCI formats 0_0, 1_0 “first pair”], and the second pair of DCI formats is DCI format 0_2 and DCI format 1_2 [Par. 0032, 0041-0042 discloses DCI formats 0_2, 1_2 “second pair”]. However, Takeda fails to fully disclose the first parameter which includes second parameter and third parameter and the first RRC parameter, the second RRC parameter, and the third parameter correspond to a same search space ID. In the same field of endeavor, Chatterjee discloses first parameter which includes second parameter and third parameter [Par. 0055, 0227, 0228-0229, 0266, 0278, 0281 discloses a field with two bits to indicate second parameter and third parameter for DCI formats 0_0, 1_0 “first pair = first bit = 1, for USS” and 0_2, 1_2 “second pair = second bit = 1, for USS” and for CSS “ first bit = 1 for first pair and second bit = 0 for second pair, zero for not configured]. However, Takeda and Chatterjee fail to fully disclose the first RRC parameter, the second RRC parameter, and the third parameter correspond to a same search space ID. In the same field of endeavor, Yi discloses the first RRC parameter, the second RRC parameter, and the third parameter correspond to a same search space ID [Par. 0346 discloses SS #1 “search space ID” which includes the first RRC parameter, the second RRC parameter, and the third parameter, Fig 27 discloses SS2 “search space ID # 2 “first parameter” which includes USS for 0_2, 1_2 and 0_0, 1_0].
Since, a method and system for using bits to indicate first and second value etc… are well known and expected in the art. Therefore, it would have been obvious to one of ordinary skill in the art before the effective filing date of claimed invention to apply a method and system comprising a search space ID for the first, second and third parameter as disclosed by Yi into the teaching of Chatterjee comprising bitmap for indicating the DCI format the UE into the teaching of Taketa. The motivation would have been to increase the capacity of monitoring the control channel.
As claim 4, Takeda discloses a base station, comprising: transmitting, by transmission circuit, to a user equipment (UE), a first radio resource control (RRC) parameter, the first RRC parameter corresponding to a configuration of a specific search space (SS) set [Par. 0024-0027, 0030-0031, 0048-0049 disclose UE receives, from base station, a RRC parameter which indicates USS search space set], the first RRC parameter including both of a second RRC parameter and a third RRC parameter [Par. 0027 discloses the first parameter “USS searchspace” includes second parameter “USS Set # 1 has searchspace id = 1” and third parameter “USS Set # 3 has search space id = 3”, Par. 0027, 0030-0031, 0048-0049, IE (8) discloses USS set information] the second RRC parameter indicating a first pair of Downlink Control Information (DCI) formats to be monitored in a UE-specific search space (USS) set [Par. 0030-0031 discloses USS set # 1 for monitoring DCI formats 0_0, 1_0, first pair, Par. 0027, IE (8) discloses USS set information, DCI formats 0_1, 1_0, first pair], the third RRC parameter indicating a second pair of DCI formats to be monitored in a USS set [Par. 0030-0031, 0048-0049 discloses USS set # 3 for monitoring DCI formats 0_2, 1_2, Second pair, Par. 0027, 0048-0049, IE (8) discloses USS set information, DCI formats 0_2, 1_2, Second pair] and the second RRC parameter being different from the third RRC parameter [Fig 2, 4 and 8-9 discloses the second parameter “searchspaceid = 1” which indicates first pair is different from third parameter “searchspaceid = 3” which indicates second pair wherein first pair is different from second pair], wherein the first pair of DCI formats indicated by a fourth RRC parameter to be monitored in a common search space (CSS) set [Par. 0028 discloses CSS “four parameter” for monitoring DCI formats 0_0, 1_0, First pair], the second pair of DCI formats not indicated by the fourth RRC parameter to be monitored in a CSS set [Par. 0028 discloses CSS “four parameter” DCI formats 0_1 and 1_0, first pair and DCI formats 0_2, 1_2, Second pair not configured for monitoring in CSS], and each of the first pair of DCI formats and the second pair of DCI formats includes a DCI format for scheduling of physical downlink shared channel (PDSCH) and a DCI format for scheduling of physical uplink shared channel (PUSCH) [Par. 0032, 0048-0049 discloses DCI formats 0_0, 1_0 “first pair” for PDSCH and PUSCH and DCI formats 0_2, 1_2, “second pair” for PDSCH and PUSCH]; the first pair of DCI formats is DCI format 0 0 and DCI format 1 0 [Par. 0032, 0041-0042 discloses DCI formats 0_0, 1_0 “first pair”], and the second pair of DCI formats is DCI format 0_2 and DCI format 1_2 [Par. 0032, 0041-0042 discloses DCI formats 0_2, 1_2 “second pair”]. However, Takeda fails to fully disclose the first parameter which includes second parameter and third parameter and the first RRC parameter, the second RRC parameter, and the third parameter correspond to a same search space ID. In the same field of endeavor, Chatterjee discloses first parameter which includes second parameter and third parameter [Par. 0055, 0227, 0228-0229, 0266, 0278, 0281 discloses a field with two bits to indicate second parameter and third parameter for DCI formats 0_0, 1_0 “first pair = first bit = 1, for USS” and 0_2, 1_2 “second pair = second bit = 1, for USS” and for CSS “ first bit = 1 for first pair and second bit = 0 for second pair, zero for not configured]. However, Takeda and Chatterjee fail to fully disclose the first RRC parameter, the second RRC parameter, and the third parameter correspond to a same search space ID. In the same field of endeavor, Yi discloses the first RRC parameter, the second RRC parameter, and the third parameter correspond to a same search space ID [Par. 0346 discloses SS #1 “search space ID” which includes the first RRC parameter, the second RRC parameter, and the third parameter, Fig 27 discloses SS2 “search space ID # 2 “first parameter” which includes USS for 0-2, 1_2 and 0_0, 1_0].
Since, a method and system for using bits to indicate first and second value etc… are well known and expected in the art. Therefore, it would have been obvious to one of ordinary skill in the art before the effective filing date of claimed invention to apply a method and system comprising a search space ID for the first, second and third parameter as disclosed by Yi into the teaching of Chatterjee comprising bitmap for indicating the DCI format the UE into the teaching of Taketa. The motivation would have been to increase the capacity of monitoring the control channel.
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 STEVEN HIEU D NGUYEN whose telephone number is (571)272-3159. The examiner can normally be reached 9-5.
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, Edan Orgad can be reached on 571-272-7884. 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.
/STEVEN HIEU D NGUYEN/Primary Examiner, Art Unit 2414