DETAILED ACTION
The office action is in response to the amendments received on Jan. 19, 2026 after RCE non-final office action.
Claims 1, 3, 8, and 10 are pending in this application, based on the amended claims on Jan. 19, 2026.
Information Disclosure Statement
The information disclosure statements (IDSs) submitted on March 7, 2024, March 20, 2023, and Sept. 27, 2022 have been considered by the examiner.
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 Amendments and Arguments filed 1/19/2026 have been considered for examination. Claims 1, 3, 8, and 10 are pending in the instant application.
With regard to the 102/103 rejections, Applicant’s arguments filed 1/19/2026 (see pages 6-9 of Remarks) in view of the amendments have been fully considered and persuasive (see Allowable subject matter). However, the newly amended independent claim 1 is rejected due to contingent limitation in the instant Office Action and accordingly, the dependent claim 3 is rejected, too, due to the independent claim 1.
Allowable Subject Matter
Regarding the amended claim 8, the prior art of record (Guorong LI and et. al (USPub No: US 20240224338 A1, hereinafter “Guorong”) in a view of Dongru LI and et. al. (USPub No: US 20240163730 A1, hereinafter “Dongru”)) does not disclose: “in response to determining that the random access procedure is successfully completed based on reception of a physical downlink control channel (PDCCH) addressed to a cell-radio network temporary identifier (C-RNTI), starting a BWP inactivity timer associated with an active DL BWP, wherein the active DL BWP is not indicated as a dormant BWP; determining whether a default DL BWP is configured upon expiration of the BWP inactivity timer; and in response to determining that the default DL BWP is not configured and that the second initial DL BWP related to the RedCap UE is configured based on the fourth configuration information, switching the active DL BWP to the second initial DL BWP related to the RedCap UE” in the recited context.
Rather, Guorong, in Fig. 1 and 2 and in Paragraphs [0078], [0081]-[0083], [0097], [0130], [0096]-[0103], clearly discloses the previous claims 1 and 3. Thus, Guorong disclose the part of the amended claim 1, based on the previous claims 1 and 3, recited as “A method performed by a reduced capability (RedCap) user equipment (UE) in a wireless communication system, the method comprising: … switching the active UL BWP to the second initial UL BWP related to the RedCap UE.” However, Guororng fails to disclose the rest part of the amended claim 8, mentioned in the above.
Further, the part of the amended claim 8 mentioned in the above is related to the previous claim 5 with the new condition under that the random access procedure is successfully completed. Regarding the previous claim 5, Dongru, in Fig. 2 and in Paragraphs [0135], [0101]-[0107], [0114], [0122]-[0123], [0127], and [0130]-[0131], clearly disclose the condition of the expiration of the BWP inactivity timer with RedCap UE and switching method for the active DL BWP, when the default DL BWP is not configured. However, since the new condition with the completion of a random access procedure is added, Dongru unfortunately fails to disclose the new condition.
Further, based on additional searching, the new prior art, Tun-Huai Shih and et. al. (USPub No: US 20220022276 A1, hereinafter “Shih”) is found. Shih, in Paragraphs [0379]-[0391], teaches the procedure in the part of the amended claim 8 mentioned in the above, except the condition related to RedCap UE. Namely, Shih’s procedure does not cover the RedCap case. Thus, Shih fails to disclose the part of the amended claim 8, too.
Thus, combination of Guorong, Dongru, and Shih fails to disclose the part of the amended claim 8, recited as “in response to determining that the random access procedure is successfully completed … switching the active DL BWP to the second initial DL BWP related to the RedCap UE.”
Therefore, the amended claim 8 is allowable and the dependent claim 10 are also allowable.
Claim Rejections - 35 USC § 102
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)(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.
Claims 1 and 3 are rejected under U.S.C. 102(a)(2) as being anticipated by Guorong Li et. al (USPub No: US 20240224338 A1, hereinafter “Guorong”).
Regarding claim 1, Guorong teaches a method performed by a reduced capability (RedCap) user equipment (UE) in a wireless communication system, the method comprising: receiving, from a base station, first configuration information on a first initial uplink (UL) bandwidth part (BWP) and second configuration information on a second initial UL BWP related to the RedCap UE, third configuration information on a first initial downlink (DL) BWP, and fourth configuration information on a second initial DL BWP related to the RedCap UE; (Guorong, in Paragraphs [0078] teaches that SIB1 or other system information transmitted by the network device (such as a gNB) may include configuration of an initial DL BWP configured for a non-reduced capability terminal equipment (non-Redcap UE) and the configuration of the initial DL BWP separately configured or defined for the Redcap UE. The Redcap UE may ignore the configuration of the initial DL BWP configured for the non-Redcap UE, and take the initial DL BWP configured separately for the Redcap UE as an initial DL BWP of its own or take the configuration of the initial DL BWP configured separately for the Redcap UE as configuration of an initial DL BWP of its own, for example, the initial DL BWP has a BWP-id of 0; or, the Redcap UE may also use both the initial DL BWP configured for the non- Redcap UE and the initial DL BWP separately configured for the Redcap UE as initial DL BWPs of its own. The two initial DL BWPs may be distinguished by using different BWP-ids, for example, the initial DL BWP configured for the non-Redcap UE has a BWP-id of 0, and the initial DL BWP configured separately for the Redcap UE has a BWP-id of 5 or another value (which may be predefined or may be configured by the network device); or, vice versa. The initial downlink BWP is called as the first initial downlink BWP as described in Fig. 1. The separate configuration example is described in Fig. 2 and in Paragraphs [0081]-[0083]. Accordingly, as described in Paragraphs [0097] and [0130], the first initial uplink BWP (the second configuration in the claim) for RedCap UE and the initial uplink BWP (the first configuration in the claim) for non-RedCap UE (normal UE) are separately configured or defined. Based on this observation, the first configuration information on a first initial uplink (UL) bandwidth part (BWP) and second configuration information on a second initial UL BWP related to the RedCap UE can be received from the base station.) identifying that a random access procedure is initiated on a serving cell; determining whether physical random access channel (PRACH) occasions are configured for an active UL BWP; in response to determining that the PRACH occasions are not configured for the active UL BWP and the second initial UL BWP related to the RedCap UE is configured based on the second configuration information, switching the active UL BWP to the second initial UL BWP related to the RedCap UE (Guorong, in Paragraphs [0096]-[0103], teaches that the reduced capability UE receives a signal by using the first initial downlink BWP during or after an initialization procedure of a random access procedure. For example, during the initialization procedure of the random access procedure, it may be that the reduced capability UE receives the signal by using the first initial downlink BWP (considered as the second initial downlink BWP for the claim) when an initial uplink (UL) BWP (initialUplinkBWP) separately configured for the Redcap UE is used, that is, when the reduced capability UE uses a first initial uplink BWP (considered as the second initial uplink BWP for the claim), the first initial uplink BWP being an initial uplink BWP separately configured or defined for the reduced capability UE. For example, if the Redcap UE deems that the initial DL BWP separately configured for the Redcap UE has a BWP-id of 0, there is no need to modify the BWP operation in Sub-section 5.15 of the MAC Specification (will be attached). Namely, the BWP operation defined in Sub-section 5.15 of the MAC Specification is for the normal UE and that is described in Table 2 when ignoring the underline part. For the RedCap UE, the operation for the normal UE is can be used for the RedCap UE with replacing the initial UL BWP and the initial downlink BWP by the first initial UL BWP for the RedCap UE (is considered as the second initial UL BWP) and the first initial downlink BWP, respectively. Further, in Paragraphs [0103], Guorong teaches that after the initialization procedure of the random access procedure, before executing a random access resource selection procedure, the Redcap UE may switch the downlink BWP to the first initial downlink BWP, or adjust the receiving bandwidth to the first initial downlink BWP. Namely, when the RedCap UE is configured, the downlink BWP is switched to the first downlink BWP and the initial uplink BWP is switched to the first initial uplink BWP in Table 2. Based on the above description, Guorong teaches, in Paragraphs [0096]-[0099] and [0103], that from Table 2, the following pseudo code can be configured:
upon initiation of the random access procedure on a Serving Cell, after the selection of carrier for performing Random Access procedure, the MAC entity shall for the selected carrier of this Serving Cell:
Step 1> if PRACH occasions are not configured for the active UL BWP,
Step 2>if non-RedCap UE (normal UE) is configured, switch the active UL BWP to BWP indicated by initialUplinkBWP (the first initial uplink BWP for the claim).
Step 2> if RedCap UE is configured, switch the active UL BWP to BWP indicated by the first initial uplink BWP (the second initial uplink BWP for the claim).
Step 2> if the Serving Cell is an SpCell:
Step 3> if normal UE is configured, switch the active DL BWP to BWP indicated by initialDownlinkBWP (the first initial downlink BWP for the claim or Specfication of Application).
Step 3> if RedCap UE is configured, switch the active DL BWP to BWP indicated by the first downlink BWP (the second initial downlink BWP for the claim or Specfication of Application).
As explained in the above, these steps can be applied for the normal UE and the RedCap UE. It is exactly matched to Paragraphs [0119]-[0129] of Specification of Application. Based on this observation, it is clear that when a random access procedure is initiated on a serving cell, the PRACH occasions are not configured, the second initial UL BWP related to the RedCap UE is configured by the second configuration information, the active UL BWP is switched to the second initial UL BWP related to the RedCap UE.
While Guorong teaches the features of claim 1 as indicated above, Examiner notes that the claim recites “… determining whether a default DL BWP is configured upon expiration of the BWP inactivity timer; …” contains a contingent limitation. The broadest reasonable interpretation of a method (or process) claim having contingent limitations requires only those steps that must be performed and does not include steps that are not required to be performed because the condition(s) precedent are not met. The limitation starting with "…determining whether a default DL BWP is configured upon expiration of the BWP inactivity timer; …" is a contingent limitation. the claim has been interpreted to not require the conditions stated to be met. See MPEP 2111.04 subsection 11.
Regarding claim 3, Guorong teaches the features defined in the claim 1, -refer to the indicated claim for reference(s).
Guorong further teaches further comprising: in response to determining that the PRACH occasions are not configured for the active UL BWP, determining whether the serving cell is a special cell (SpCell); and in response to determining that the PRACH occasions are not configured for the active UL BWP, that the serving cell is the SpCell, and that the second initial DL BWP related to the RedCap UE is configured based on the fourth configuration information, switching the active DL BWP to the second initial DL BWP related to the RedCap UE. (Guorong, in Paragraphs [0096]-[0103], teaches that the reduced capability UE receives a signal by using the first initial downlink BWP during or after an initialization procedure of a random access procedure. For example, during the initialization procedure of the random access procedure, it may be that the reduced capability UE receives the signal by using the first initial downlink BWP (considered as the second initial downlink BWP for the claim) when an initial uplink (UL) BWP (initialUplinkBWP) separately configured for the Redcap UE is used, that is, when the reduced capability UE uses a first initial uplink BWP (considered as the second initial uplink BWP for the claim), the first initial uplink BWP being an initial uplink BWP separately configured or defined for the reduced capability UE. For example, if the Redcap UE deems that the initial DL BWP separately configured for the Redcap UE has a BWP-id of 0, there is no need to modify the BWP operation in Sub-section 5.15 of the MAC Specification (will be attached). Namely, the BWP operation defined in Sub-section 5.15 of the MAC Specification is for the normal UE and that is described in Table 2 when ignoring the underline part. For the RedCap UE, the operation for the normal UE is can be used for the RedCap UE with replacing the initial UL BWP and the initial downlink BWP by the first initial UL BWP for the RedCap UE (is considered as the second initial UL BWP) and the first initial downlink BWP, respectively. Further, in Paragraphs [0103], Guorong teaches that after the initialization procedure of the random access procedure, before executing a random access resource selection procedure, the Redcap UE may switch the downlink BWP to the first initial downlink BWP, or adjust the receiving bandwidth to the first initial downlink BWP. Namely, when the RedCap UE is configured, the downlink BWP is switched to the first downlink BWP and the initial uplink BWP is switched to the first initial uplink BWP in Table 2. Based on the above description, Guorong teaches, in Paragraphs [0096]-[0099] and [0103], that from Table 2, the following pseudo code can be configured:
upon initiation of the random access procedure on a Serving Cell, after the selection of carrier for performing Random Access procedure, the MAC entity shall for the selected carrier of this Serving Cell:
Step 1> if PRACH occasions are not configured for the active UL BWP,
Step 2>if non-RedCap UE (normal UE) is configured, switch the active UL BWP to BWP indicated by initialUplinkBWP (the first initial uplink BWP for the claim).
Step 2> if RedCap UE is configured, switch the active UL BWP to BWP indicated by the first initial uplink BWP (the second initial uplink BWP for the claim).
Step 2> if the Serving Cell is an SpCell:
Step 3> if normal UE is configured, switch the active DL BWP to BWP indicated by initialDownlinkBWP (the first initial downlink BWP for the claim or Specfication of Application).
Step 3> if RedCap UE is configured, switch the active DL BWP to BWP indicated by the first downlink BWP (the second initial downlink BWP for the claim or Specfication of Application).
As explained in the above, these steps can be applied for the normal UE and the RedCap UE. It is exactly matched to Paragraphs [0119]-[0129] of Specification of Application. Based on this observation, it is clear that when a random access procedure is initiated on a serving cell, the PRACH occasions are not configured for the active UL BWP, the serving cell is the SpCell, and the second initial DL BWP related to the RedCap UE is configured by the fourth configuration information, an active DL BWP is switched to the second itnitial DL BWP related to the RedCap UE.)
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 JAEYOUNG KWAK whose telephone number is (703)756-1768. The examiner can normally be reached Monday-Friday 9 AM -5 PM.
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, Kevin Bates can be reached at 571-272-3980. 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.
/JAEYOUNG KWAK/Examiner, Art Unit 2472
/KEVIN T BATES/Supervisory Patent Examiner, Art Unit 2472
Prosecution Insights