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 .
Response to Arguments
Applicant’s arguments with respect to claims 1-30 have been considered but are moot because the new ground of rejection does not rely on any reference applied in the prior rejection of record for any teaching or matter specifically challenged in the argument.
Claim Rejections - 35 USC § 103
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.
Claims 1 are rejected under 35 U.S.C. 103 as being unpatentable over
Rudolf (US 2023/0276438) in view of Park (US 2022/0167404).
Regarding claim 1, Rudolf describes a user equipment (UE) for wireless communication, comprising: one or more memories; and one or more processors, coupled to the memory (fig. 3, UE 116 comprising processor 340 coupled to memory 360), configured to:
receive information scheduling a physical uplink shared channel (PUSCH) transmission at least partially in a sub-band full duplex (SBFD) resource in connection with a random access channel procedure (para. 59, UE receiving an UL DCI format from eNB scheduling its uplink PUSCH transmission in full duplex operation using an UL subband (SBFD), para. 142, perform as part of random access using a random access channel, para. 71 & 74).
Rudolf describes:
transmit the PUSCH transmission on time and frequency (time-frequency) resources, and are associated with a sub-band configuration of the SBFD resource (title & para. 142, SBFD operation is done on the PUSCH transmission, where PUSCH’s UL signaling done in time unit and a frequency unit (bandwidth) (para. 58), but fail to further
explicitly describe:
PUSCH transmission using resources that are derived from a sub-band configuration of the SBFD resource.
Park also describes transceiving (duplex) data in subands (para. 6), ie. SBFD, further describing:
PUSCH transmission using resources that are derived from a sub-band configuration of the SBFD resource (para. 251, frequency resource allocation for PUSCH [transmission] according to the subband configuration for transceiving (duplex) data in subands (para. 6), ie. SBFD).
It would have been obvious to one with ordinary skill in the art before the effective date of the claimed invention to specify that the PUSCH transmission on time and frequency resources in Rudolf be derived form sub-band configuration of the SBFD resource as in Park.
The motivation for combining the teachings is that this efficiently multiplexing of radio resource unit with different assorted requirements for data rates, latency, reliability, coverage, etc. (Park, para. 4).
Regarding claim 2, Rudolf and Park combined describe:
wherein the sub-band configuration indicates one or more uplink sub-bands and one or more downlink sub-bands of the SBFD resource (Rudolf, para. 142, SBFD = full duplex (bidirectional) using UL subband + DL subband).
Regarding claim 8, Rudolf and Park combined describe:
wherein the sub-band configuration indicates an uplink sub-band of the SBFD resource, and wherein the one or more processors, to transmit the PUSCH transmission on time-frequency resources that are associated with the sub-band configuration of the SBFD resource (Rudolf, para. 141, UL frequency sub-band and DL frequency subbands in same time resources (lopped together as time-frequency resources), defining SBFD, subband full-duplex, para. 142), are configured to transmit the PUSCH transmission using a starting resource block that is based at least in part on the uplink sub-band and indicated frequency resources of the PUSCH (Rudolf, para. 128-130, PUSCH transmission using a RB.sub.start equation that is based on UL BWP (UL subband) and [frequency] resource assignment for MsgA PUSCH).
Regarding claim 9, Rudolf and Park combined describe:
wherein the starting resource block is referenced to a lowest resource block, in frequency, of the uplink sub-band (Rudolf, para. 127-130, for either intra- or inter-slot frequency hopping, the starting RB defines a starting [lowest] frequency unit for the UL (para. 58) as part of the subband full duplex (SBFD), fig. 7 & para. 141-142).
Regarding claim 11, Rudolf and Park combined describe:
wherein the starting resource block is a first starting resource block for a first hop of the PUSCH transmission, and wherein the one or more processors, to transmit the PUSCH transmission on the time-frequency resources, are configured to transmit a second hop of the PUSCH transmission, wherein a second starting resource block for the second hop is based at least in part on the starting resource block, a frequency offset, and an uplink sub-band size of the SBFD resource (Rudolf para. 127-128, equation RB.sub.start when i=0 is for first hop, and when i=1 is for second hop, equation is based on RB.sub.start (starting resource block, RB.sub.offset (frequency offset), and N.sup.size&sub.BWP (uplink sub-band size of the transmission using SBFD resource (para. 142). The PUSCH’s UL transmission is done in time unit and a frequency unit (bandwidth) (para. 58)).
Regarding claim 12, Rudolf and Park combined describe:
the second starting resource block is based at least in part on a modulo operation on a sum of the starting resource block and the frequency offset, wherein a modulus of the modulo operation is the uplink sub-band size (Rudolf para. 127, I=1 is the second hop, equating to (based on) ( RB.sub.start + RB.sub.offset (frequency offset) ) mod N.sup.size+sub.BWP).
Regarding claim 13, Rudolf and Park combined describe:
wherein the one or more processors are further configured to receiving, prior to the information, configuration information indicating a plurality of time-domain resource allocation (TDRA) parameters, wherein the one or more processors, to transmit the PUSCH transmission on the time-frequency resources, are configured to transmit the PUSCH transmission in accordance with a start and length indicator value indicated by a particular TDRA parameter, of the plurality of TDRA parameters, based at least in part on the PUSCH transmission occurring on the SBFD resource (Rudolf para. 180-181, 184, 194-195, 198, etc. & also abstract, TDRA parameter(s) as part of configuration comprising start and size/length, are provided to the UE before its PUSCH transmission in SBFD [resource(s)], para. 143 & fig. 7).
Regarding claim 14, Rudolf and Park combined describe:
wherein the one or more processors are further configured to receive, prior to the information, configuration information indicating a time-domain resource allocation (TDRA) parameter, wherein the one or more processors, to transmit the PUSCH transmission on the time-frequency resources, are configured to transmit the PUSCH transmission in accordance with a start and length indicator value indicated by the TDRA parameter, wherein the start and length indicator value is for SBFD resources (Rudolf para. 180-181, 184, 194-195, 198, etc. & also abstract, TDRA parameter(s) as part of configuration comprising start and size/length, are provided to the UE before its PUSCH transmission in SBFD [resource(s)], para. 143 & fig. 7).
Regarding claim 15, Rudolf and Park combined describe:
wherein the one or more processors, to transmit the PUSCH transmission on time-frequency resources that are associated with the sub-band configuration of the SBFD resource, are configured to transmit the PUSCH transmission in accordance with a default time-domain resource allocation (TDRA) parameter that is specific to SBFD resources (Rudolf para. 175, TDRA parameter(s) may be part of the default TDRA table provided to the UE for its PUSCH transmission in SBFD [resource(s)], para. 143 & fig. 7).
Regarding claim 16, Rudolf and Park combined describe:
wherein the one or more processors, to transmit the PUSCH transmission on the time-frequency resources, are configured to transmit the PUSCH transmission on the time-frequency resources based at least in part on the time-frequency resources being available resources for the PUSCH transmission, wherein the time-frequency resources are available resources based at least in part on the sub-band configuration of the SBFD resource (Rudolf para. 180-181, etc. & also abstract, TDRA parameter as configuration are provided to the UE before its PUSCH transmission in SBFD [resources], para. 143 & fig. 7. The PUSCH’s UL transmission is done in the designated time unit and a frequency unit (available resources)) (para. 58).
Regarding claim 17, Rudolf and Park combined describe:
wherein the time-frequency resources are available resources based at least in part on the time-frequency resources not overlapping with a downlink symbol that does not include a configured uplink sub-band according to the sub-band configuration (Rudolf para. 121, for PUSCH (UL) transmission, a slot is not counted in the number of NK slots [for use] if at least one of the symbols indicated by the indexed row of the used resource allocation table in the slot overlaps with a DL symbol), and based at least in part on the time-frequency resources not including a synchronization signal block (SSB) resource (Rudolf para. 194, resource carrying SSBs is unavailable for other time-frequency resource use).
Regarding claim 18, Rudolf and Park combined describe:
wherein the PUSCH transmission comprises at least one of a random access channel message 3 transmission (Rudolf para. 87, using [RACH] MSG3 as transmission for PUSCH).
Claims 19-26 are apparatus (network node) claims reciting exact mirroring features of apparatus (UE) claims 1, 3, 8, 11, 13-16 respectively. Hence, they are rejected/objected to using the same rationale.
Claims 27-28 are method claims reciting same features as apparatus claims 1 and 3. Hence, they are rejected/objected to under the same rationale.
Claims 29-30 are method claims reciting same features as apparatus claims 19 and 20. Hence, they are rejected under the same rationale.
Allowable Subject Matter
Claims 3-7 and 10 are objected to as being dependent upon a rejected base claim, but would be allowable if rewritten in independent form including all of the limitations of the base claim and any intervening claims.
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 WARNER WONG whose telephone number is (571)272-8197. The examiner can normally be reached M-F 7am - 3:30pm.
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, Ian Moore can be reached at 571-272-3085. 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.
WARNER WONG
Primary Examiner
Art Unit 2469
/WARNER WONG/Primary Examiner, Art Unit 2469