CTNF 18/722,436 CTNF 88695 DETAILED ACTION Notice of Pre-AIA or AIA Status 07-03-aia AIA 15-10-aia 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 07-06 AIA 15-10-15 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. 07-20-aia AIA 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. 07-20-02-aia AIA 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. 07-21-aia AIA Claim (s) 10, 11 and 12 are rejected under 35 U.S.C. 103 as being unpatentable over Hwang et al (US 20240107533) in view of Liu et al (EP 3860257) . As to claims 10 and 12 Hwang disclose a terminal apparatus and a communicational method for the terminal apparatus comprising (Hwang UE of Fig.5, Fig.13, 106 of Fig.20): a receiver configured to receive a first system information block (SIB), receive a second SIB, receive downlink control information (DCI) with a cyclic redundancy check (CRC) scrambled with a first radio network temporary identifier (RNTI) ( Hwang ¶0088 - The PDCCH delivers DCI …The DCI includes a cyclic redundancy check (CRC). The CRC is masked with various identifiers (IDs) (e.g. a radio network temporary identifier (RNTI)) according to an owner or usage of the PDCCH… If the PDCCH is for system information (e.g., a system information block (SIB)), the CRC is masked by a system information RNTI (SI-RNTI). When the PDCCH is for an RAR, the CRC is masked by a random access-RNTI (RA-RNTI) , and receive a physical downlink shared channel (PDSCH) scheduled on a first time resource ( Hwang s502 of Fig.5 ¶0090- 3 rd sentence - a PDSCH carrying system information block 1 (SIB1) may be scheduled by a specific PDCCH, and CORESET #0 may be used to transmit the specific PDCCH .); and a controller configured to determine the first time resource by using a first value indicated by a first field included in the DCI and a PDSCH time domain resource allocation configuration indicating mapping between the first value and the first time resource ( Hwang ¶0209 - determining a PDSCH scheduling scheme according to a P-RNTI value used for paging transmission/reception in a PO. In the proposed method, the configuration and interpretation of PDSCH scheduling information (e.g., DCI field for scheduling a PDSCH scheduled by DCI) included in the corresponding DCI may be determined according to a P-RNTI value applied to DCI (e.g., DCI format 1_0) transmitted and received in the PO for the purpose of paging. Characteristically, for example, a method of determining the configuration and interpretation of (at least) time domain resource assignment (TDRA) field among DCI fields for scheduling of a PDSCH according to a value of a P-RNTI applied to DCI (e.g., DCI format 1_0) scrambled with a P-RNTI may be proposed. The DCI field for PDSCH scheduling to be determined according to a P-RNTI value may include other DCI fields, ¶0210-¶0212, Table.5; ¶0242- Each entry of each TDRA table may indicate a combination of {slot offset, start symbol, and length} for the corresponding PDSCH time resource . ¶0353- 1 st sentence ); Hwang however is silent wherein in a case that a first parameter list is provided in the first SIB, the first parameter list is applied as the PDSCH time domain resource allocation configuration; and in a case that the first parameter list is not provided in the first SIB, and a second parameter list is provided in the second SIB, the second parameter list is applied as the PDSCH time domain resource allocation configuration; and in a case that the first parameter list is not provided in the first SIB, and the second parameter list is not provided in the second SIB, a default table is applied as the PDSCH time domain resource allocation configuration- first and second parameter lists corresponding to pdsch- TimeDomainAllocationLis ts . However in an analogous art Liu remedies these deficiencies: ( Liu ¶0022- when a physical downlink shared channel (PDSCH) time domain resource allocation table is configured for a PDSCH, the configured PDSCH time domain resource allocation table is preferably used for resource allocation, that is, when a PDSCH is configured with a pdsch- TimeDomainAllocationList , the pdsch- TimeDomainAllocationList is used as the PDSCH time domain resource allocation table. ¶0076 - When the pdsch-ConfigCommon information element of the SIB1 does not contain the pdsch- TimeDomainAllocationList (namely, the PDSCH time domain resource allocation table is not configured), if the SearchSpaceId corresponding to the searchSpaceOtherSystemlnformation field in the PDCCH-ConfigCommon information element of the SIB 1 is configured as SearchSpaceZero, then the applied PDSCH time domain resource allocation table is determined according to the multiplexing pattern between the SSB and the CORESET. That is, if the multiplexing pattern is pattern1, the default PDSCH time domain resource allocation table A (Default A) is adopted; if the multiplexing pattern is pattern2, the default PDSCH time domain resource allocation table B (Default B) is adopted ; and if the multiplexing pattern is pattern3, the default PDSCH time domain resource allocation table C (Default C) is adopted. ). Therefore, it would have been obvious to one of ordinary skills in the art before the effective filing date of the invention to modify the teachings of Hwang with that of Liu for the purpose of choosing the correct TDRA table for interpreting control fields mapped to PDSCH timing. As to claim 11 Hwang discloses a base station apparatus comprising ( Hwang, BS of Fig. 5, Network of Fig. 13, 206 of Fig. 20 ): a transmitter configured to transmit a first system information block (SIB), receive a second SIB, transmit downlink control information (DCI) with a cyclic redundancy check (CRC) scrambled with a first radio network temporary identifier (RNTI) ( Hwang ¶0088 - The PDCCH delivers DCI …The DCI includes a cyclic redundancy check (CRC). The CRC is masked with various identifiers (IDs) (e.g. a radio network temporary identifier (RNTI)) according to an owner or usage of the PDCCH… If the PDCCH is for system information (e.g., a system information block (SIB)), the CRC is masked by a system information RNTI (SI-RNTI). When the PDCCH is for an RAR, the CRC is masked by a random access-RNTI (RA-RNTI) , and receive a physical downlink shared channel (PDSCH) scheduled on a first time resource ( Hwang s502 of Fig.5 ¶0090- 3 rd sentence - a PDSCH carrying system information block 1 (SIB1) may be scheduled by a specific PDCCH, and CORESET #0 may be used to transmit the specific PDCCH .);, and transmit a physical downlink shared channel (PDSCH) scheduled on a first time resource( Hwang s502 of Fig.5 ¶0090- 3 rd sentence - a PDSCH carrying system information block 1 (SIB1) may be scheduled by a specific PDCCH, and CORESET #0 may be used to transmit the specific PDCCH .); and a controller configured to determine the first time resource by using a first value indicated by a first field included in the DCI and a PDSCH time domain resource allocation configuration indicating mapping between the first value and the first time resource( Hwang ¶0209 - determining a PDSCH scheduling scheme according to a P-RNTI value used for paging transmission/reception in a PO. In the proposed method, the configuration and interpretation of PDSCH scheduling information (e.g., DCI field for scheduling a PDSCH scheduled by DCI) included in the corresponding DCI may be determined according to a P-RNTI value applied to DCI (e.g., DCI format 1_0) transmitted and received in the PO for the purpose of paging. Characteristically, for example, a method of determining the configuration and interpretation of (at least) time domain resource assignment (TDRA) field among DCI fields for scheduling of a PDSCH according to a value of a P-RNTI applied to DCI (e.g., DCI format 1_0) scrambled with a P-RNTI may be proposed. The DCI field for PDSCH scheduling to be determined according to a P-RNTI value may include other DCI fields, ¶0210-¶0212, Table.5; ¶0242- Each entry of each TDRA table may indicate a combination of {slot offset, start symbol, and length} for the corresponding PDSCH time resource . ); Hwang however is silent wherein in a case that a first parameter list is provided in the first SIB, the first parameter list is applied as the PDSCH time domain resource allocation configuration; in a case that the first parameter list is not provided in the first SIB, and a second parameter list is provided in the second SIB, the second parameter list is applied as the PDSCH time domain resource allocation configuration; and in a case that the first parameter list is not provided in the first SIB, and the second parameter list is not provided in the second SIB, a default table is applied as the PDSCH time domain resource allocation configuration. However in an analogous art Liu remedies these deficiencies: ( Liu ¶0022- when a physical downlink shared channel (PDSCH) time domain resource allocation table is configured for a PDSCH, the configured PDSCH time domain resource allocation table is preferably used for resource allocation, that is, when a PDSCH is configured with a pdsch- TimeDomainAllocationList , the pdsch- TimeDomainAllocationList is used as the PDSCH time domain resource allocation table. ¶0076 - When the pdsch-ConfigCommon information element of the SIB1 does not contain the pdsch- TimeDomainAllocationList (namely, the PDSCH time domain resource allocation table is not configured), if the SearchSpaceId corresponding to the searchSpaceOtherSystemlnformation field in the PDCCH-ConfigCommon information element of the SIB 1 is configured as SearchSpaceZero, then the applied PDSCH time domain resource allocation table is determined according to the multiplexing pattern between the SSB and the CORESET. That is, if the multiplexing pattern is pattern1, the default PDSCH time domain resource allocation table A (Default A) is adopted; if the multiplexing pattern is pattern2, the default PDSCH time domain resource allocation table B (Default B) is adopted ; and if the multiplexing pattern is pattern3, the default PDSCH time domain resource allocation table C (Default C) is adopted. ). Therefore, it would have been obvious to one of ordinary skills in the art before the effective filing date of the invention to modify the teachings of Hwang with that of Liu for the purpose of choosing the correct TDRA table for interpreting control fields mapped to PDSCH timing . Conclusion 07-96 AIA The prior art made of record and not relied upon is considered pertinent to applicant's disclosure. Jiang et al – Data Scheduling Method and Apparatus, and Data Sending Method and Apparatus- US 20240260036, ¶0063,¶0077,¶0095. Bae et al - Method for Monitoring Uplink Cancelation Instructions, User Equipment, Apparatus, Computer-Readable Storage Medium, Method for Transmitting Uplink Cancelation Instructions And Base Station- US 20240073887, ¶0148. Lin et al – Method to Indicate Time Domain Resource Allocation for Physical download Shared Channel Before RRC Connection- WO 2019166991, pg. 23, lines 1-30. Any inquiry concerning this communication or earlier communications from the examiner should be directed to DERRICK V ROSE whose telephone number is (571)270-7460. The examiner can normally be reached 9am- 6pm. 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, YEMANE MESFIN can be reached at 571-272-3927. 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. /DERRICK V ROSE/Primary Examiner, Art Unit 2462 Application/Control Number: 18/722,436 Page 2 Art Unit: 2462 Application/Control Number: 18/722,436 Page 3 Art Unit: 2462 Application/Control Number: 18/722,436 Page 4 Art Unit: 2462 Application/Control Number: 18/722,436 Page 5 Art Unit: 2462 Application/Control Number: 18/722,436 Page 6 Art Unit: 2462 Application/Control Number: 18/722,436 Page 7 Art Unit: 2462 Application/Control Number: 18/722,436 Page 8 Art Unit: 2462
Prosecution Insights