Prosecution Insights
Last updated: April 19, 2026
Application No. 18/447,056

Random Access Method, Terminal Device, and Network Device

Final Rejection §103
Filed
Aug 09, 2023
Examiner
CUNNINGHAM, KEVIN M
Art Unit
2461
Tech Center
2400 — Computer Networks
Assignee
Huawei Technologies Co., Ltd.
OA Round
2 (Final)
72%
Grant Probability
Favorable
3-4
OA Rounds
2y 9m
To Grant
84%
With Interview

Examiner Intelligence

Grants 72% — above average
72%
Career Allow Rate
413 granted / 577 resolved
+13.6% vs TC avg
Moderate +12% lift
Without
With
+12.2%
Interview Lift
resolved cases with interview
Typical timeline
2y 9m
Avg Prosecution
57 currently pending
Career history
634
Total Applications
across all art units

Statute-Specific Performance

§101
2.9%
-37.1% vs TC avg
§103
58.0%
+18.0% vs TC avg
§102
13.3%
-26.7% vs TC avg
§112
21.9%
-18.1% vs TC avg
Black line = Tech Center average estimate • Based on career data from 577 resolved cases

Office Action

§103
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 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-6, 8-13 and 15-19 are rejected under 35 U.S.C. 103 as being unpatentable over Wu (US 2019/0045549, hereinafter Wu, claiming priority date of provisional application 62/540,045, as disclosed in the IDS), in view of YI et al (US 2019/0364602, hereinafter YI, claiming priority date of provisional applications 62/579,085 and 62/576,585, as disclosed in the IDS), in view of Lee et al (US 2021/0144700, hereinafter Lee2, claiming the priority dates of all provisional applications, as disclosed in the IDS), in view of Lee et al (US 2020/0235896, hereinafter Lee, claiming priority date of provisional application 62/561,688 and 62/568,342) and in view of YE (US 2013/0143547, hereinafter YE). Regarding claim 1, Wu discloses a random access method, comprising: performing, by a terminal device, data transmission based on a configuration parameter of a currently activated first bandwidth part (BWP) (UE and BS communicate via first DL BWP and first UL BWP, Para [0019]); determining, by the terminal device, a first random access resource and a second configuration parameter for random access, and wherein a configuration parameter of a second BWP comprises the first random access resource and the second configuration parameter (UE receives RRC message configuring at least a second DL BWP and/or a second UL BWP and comprises first RACH configuration configuring RACH resources for UE to perform RA in second UL BWP, Para [0020], UE determines what RACH resource to use, Para [0036/37]); sending, by the terminal device, a random access request to the network device on the first random access resource (UE transmits first RA preamble in second UL BWP according to RACH resource, Para [0022]); and receiving, by the terminal device, a random access response according to the second configuration parameter (UE receives a RA response in the second DL BWP in response to the first RA preamble, Para [0023/31]. Also see pages 3-4 from provisional application 62/540,045); but does not disclose determining first RA resource when the currently activated first BWP not including a random access resource when a random access procedure is initiated. Yi discloses a UE has separate RACH resources configured for its active BWP but if there is no RACH resource configuration in its active BWP, a UE may go back to the initial BWP for RACH transmission, Para [0129], (e.g. UE3’s UL BWP does not include any PRACH resource, Para [0155]) and UE can tune to PRACH resource outside its currently active BWP, to transmit PRACH then come back to the active BWP, Para [0178]. Also see pages 14 and 15 from provisional application 62/579,085. It would have been obvious to one of ordinary skill in the art before the effective filing date of the invention to utilize the techniques taught by YI in the system of Wu in order to reduce power consumption of the UE, by configuring UE with different bandwidths according to the traffic load of the UE; nor explicitly discloses wherein the configuration parameter of the first BWP comprises at least one of a first resource offset, a first bandwidth, or a first subcarrier spacing and wherein the second configuration parameter comprises at least one of a second resource offset, a second bandwidth, or a second subcarrier spacing. YI discloses multiple UL BWP configurations, Para [0180], BWP consists of a number of consecutive PRBs, Para [0072] and there is a numerology for configured BWPs, Para [0261] (or page 9). Lee2 discloses a resource offset may be configured for each BWP, Para [0007], therefore a first and second resource offset for first and second BWP or see page 30 of provisional application 62/586,142. It would have been obvious to one of ordinary skill in the art before the effective filing date of the invention to utilize the techniques taught by Lee2 in the system of Wu in view of YI in order to determine resources to use for transmitting for every BWP; and does not disclose forcibly stopping, by the terminal device, based on the terminal device receiving indication information for deactivating the first BWP, the random-access procedure. Lee discloses UE receives BWP configuration with deactivation timer, Para [0128] or a deactivation message, Para [0129] and the UE may de-active the active BWP and determine the random access procedure has failed on the active BWP, Para [0130] or see page 23, Section 6 of provisional application 62/568,342. YE discloses the random access procedure may be proactively stopped when the RA procedure fails, Para [0028]. It would have been obvious to one of ordinary skill in the art before the effective filing date of the invention to utilize the techniques taught by Lee and YE in the system of Wu in view of YI and Lee2 in order to using a BWP timer to recover from DCI lost cases and to prevent the UE and network from being misaligned in regards to BWP and to properly coordinate multiple RA procedure and handle RA failures. Regarding claims 2, 9 and 16, Wu discloses the method/device/CRM according to claim 1/8/17, wherein the method further comprises: sending, by the terminal device, a random access message 3 to the network device based on the random access response (UE transmits response message to BS according to UL grant in the RA response, Para [0067]). Regarding claims 3, 10 and 17, Wu discloses the method/device/CRM according to claim 2/9/15, wherein the sending, by the terminal device, the random access message 3 to the network device based on the random access response comprises: parsing, by the terminal device, based on the second configuration parameter, second scheduling information carried in the random access response, wherein the second scheduling information indicates a second resource; and sending, by the terminal device, the random access message 3 to the network device on the second resource (UE receives a RAR from the BS in the second DL BWP and transmits a message to the BS according to the UL grant in the RAR, Para [0065, 67], the UL grant being the scheduling information, UE parses RAR on second BWP to find the UL grant). Regarding claims 4, 11 and 18, Wu discloses the method/device/CRM according to claim 1/8/15, wherein at least one of: the first random access resource and the second configuration parameter are associated with the first BWP; the first random access resource and the second configuration parameter are associated with a second BWP. YI discloses multiple UL BWP configurations, Para [0180], BWP consists of a number of consecutive PRBs, Para [0072] and there is a numerology for configured BWPs, Para [0261] (or page 9), in this case first resource is on the second BWP and second BWP has configuration parameters; the first random access resource is a cell-specific random access resource, and the cell-specific random access resource is associated with the second configuration parameter; or the first random access resource and the second configuration parameter are associated with a cell-defining synchronization signal block (SSB). Regarding claims 5, 12 and 19, Wu discloses the method/device/CRM according to claim 4/11/18, wherein at least one of information about the first random access resource or information about the second configuration parameter is carried in a system broadcast message (SIB is included in the RRC message, Para [0032] that configures the RACH resources). Regarding claims 6 and 13, Wu discloses the method/device according to claim 5/12, wherein the RRC reconfiguration message or the system broadcast message carries a configuration parameter of the second BWP, and wherein the configuration parameter of the second BWP comprises the second configuration parameter. Wu discloses RRC message configures second DL BWP, Para [0020] and YI discloses multiple UL BWP configurations, Para [0180], BWP consists of a number of consecutive PRBs, Para [0072] and there is a numerology for configured BWPs, Para [0261] (or page 9). Regarding claim 8, Wu discloses a device (device, Fig. 2), comprising: a processor and a non-transitory computer-readable storage medium (processing circuitry and storage device, Fig. 2) storing a program to be executed by the processor, the program including instructions for: performing data transmission based on a configuration parameter of a currently activated first bandwidth part (BWP) (UE and BS communicate via first DL BWP and first UL BWP, Para [0019]); determining a first random access resource and a second configuration parameter for random access and wherein a configuration parameter of a second BWP comprises the first random access resource and the second configuration parameter (UE receives RRC message configuring at least a second DL BWP and/or a second UL BWP and comprises first RACH configuration configuring RACH resources for UE to perform RA in second UL BWP, Para [0020], UE determines what RACH resource to use, Para [0036/37]); sending a random access request to the network device on the first random access resource (UE transmits first RA preamble in second UL BWP according to RACH resource, Para [0022]); and receiving a random access response according to the second configuration parameter(UE receives a RA response in the second DL BWP in response to the first RA preamble, Para [0023/31]. Also see pages 3-4 from provisional application 62/540,045); wherein receiving the random access response according to the second configuration parameter comprises: determining first scheduling information according to the second configuration parameter, wherein the first scheduling information indicates a first resource (RRC message configures second DL BWP, Para [0020]); and receiving, by the terminal device on the first resource, the random access response from the network device (UE receives RAR on the second DL BWP, Para [0023]); but does not disclose determining first RA resource when the currently activated first BWP not including a random access resource when a random access procedure is initiated. Yi discloses a UE has separate RACH resources configured for its active BWP but if there is no RACH resource configuration in its active BWP, a UE may go back to the initial BWP for RACH transmission, Para [0129], (e.g. UE3’s UL BWP does not include any PRACH resource, Para [0155]) and UE can tune to PRACH resource outside its currently active BWP, to transmit PRACH then come back to the active BWP, Para [0178]. Also see pages 14 and 15 from provisional application 62/579,085; nor explicitly discloses wherein the configuration parameter of the first BWP comprises at least one of a first resource offset, a first bandwidth, or a first subcarrier spacing and wherein the second configuration parameter comprises at least one of a second resource offset, a second bandwidth, or a second subcarrier spacing. YI discloses multiple UL BWP configurations, Para [0180], BWP consists of a number of consecutive PRBs, Para [0072] and there is a numerology for configured BWPs, Para [0261] (or page 9). Lee2 discloses a resource offset may be configured for each BWP, Para [0007], therefore a first and second resource offset for first and second BWP or see page 30 of provisional application 62/586,142; and does not disclose forcibly stopping, by the terminal device, based on the terminal device receiving indication information for deactivating the first BWP, the random-access procedure. Lee discloses UE receives BWP configuration with deactivation timer, Para [0128] or a deactivation message, Para [0129] and the UE may de-active the active BWP and determine the random access procedure has failed on the active BWP, Para [0130] or see page 23, Section 6 of provisional application 62/568,342. YE discloses the random access procedure may be proactively stopped when the RA procedure fails, Para [0028]. It would have been obvious to one of ordinary skill in the art before the effective filing date of the invention to utilize the techniques taught by Lee and YE in the system of Wu in view of YI and Lee2 in order to using a BWP timer to recover from DCI lost cases and to prevent the UE and network from being misaligned in regards to BWP and to properly coordinate multiple RA procedure and handle RA failures. Regarding claim 15, Wu discloses a non-transitory computer-readable storage medium (computer readable medium, Para [0015]) storing a program to be executed by a processor, the program including instructions for: performing data transmission based on a configuration parameter of a currently activated first bandwidth part (BWP) (UE and BS communicate via first DL BWP and first UL BWP, Para [0019]); determining a first random access resource and a second configuration parameter for random access, and wherein a configuration parameter of a second BWP comprises the first random access resource and the second configuration parameter (UE receives RRC message configuring at least a second DL BWP and/or a second UL BWP and comprises first RACH configuration configuring RACH resources for UE to perform RA in second UL BWP, Para [0020], UE determines what RACH resource to use, Para [0036/37]); sending a random access request to the network device on the first random access resource (UE transmits first RA preamble in second UL BWP according to RACH resource, Para [0022]); and receiving a random access response according to the second configuration parameter (UE receives a RA response in the second DL BWP in response to the first RA preamble, Para [0023/31]. Also see pages 3-4 from provisional application 62/540,045); wherein receiving the random access response according to the second configuration parameter comprises: determining first scheduling information according to the second configuration parameter, wherein the first scheduling information indicates a first resource; (RRC message configures second DL BWP, Para [0020]); and receiving, by the terminal device on the first resource, the random access response from the network device (UE receives RAR on the second DL BWP, Para [0023]); but does not disclose determining first RA resource when the currently activated first BWP not including a random access resource when a random access procedure is initiated. Yi discloses a UE has separate RACH resources configured for its active BWP but if there is no RACH resource configuration in its active BWP, a UE may go back to the initial BWP for RACH transmission, Para [0129], (e.g. UE3’s UL BWP does not include any PRACH resource, Para [0155]) and UE can tune to PRACH resource outside its currently active BWP, to transmit PRACH then come back to the active BWP, Para [0178]. Also see pages 14 and 15 from provisional application 62/579,085; nor explicitly discloses wherein the configuration parameter of the first BWP comprises at least one of a first resource offset, a first bandwidth, or a first subcarrier spacing and wherein the second configuration parameter comprises at least one of a second resource offset, a second bandwidth, or a second subcarrier spacing. YI discloses multiple UL BWP configurations, Para [0180], BWP consists of a number of consecutive PRBs, Para [0072] and there is a numerology for configured BWPs, Para [0261] (or page 9). Lee2 discloses a resource offset may be configured for each BWP, Para [0007], therefore a first and second resource offset for first and second BWP or see page 30 of provisional application 62/586,142; and does not disclose forcibly stopping, by the terminal device, based on the terminal device receiving indication information for deactivating the first BWP, the random-access procedure. Lee discloses UE receives BWP configuration with deactivation timer, Para [0128] or a deactivation message, Para [0129] and the UE may de-active the active BWP and determine the random access procedure has failed on the active BWP, Para [0130] or see page 23, Section 6 of provisional application 62/568,342. YE discloses the random access procedure may be proactively stopped when the RA procedure fails, Para [0028]. It would have been obvious to one of ordinary skill in the art before the effective filing date of the invention to utilize the techniques taught by Lee and YE in the system of Wu in view of YI and Lee2 in order to using a BWP timer to recover from DCI lost cases and to prevent the UE and network from being misaligned in regards to BWP and to properly coordinate multiple RA procedure and handle RA failures. Allowable Subject Matter Claims 20-22 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. Response to Arguments Applicant's arguments filed 1/27/2026 have been fully considered but they are not persuasive. Applicant amends the limitations in the claim and argues the references do not disclose the amended limitations. Applicant argues Lee discloses failure of RA procedure and deactivation of the BWP and Yi discloses failure of RACH procedure during RAR reception. Applicant argues the RA procedure is forcibly stopped based on the terminal device receiving an indication for deactivating the first BWP. In response, Applicant has amended the limitation from dependent claim 7, but removed “or determining by the terminal device the current RA procedure fails”. The prior references disclosed this prior limitation, where in response to the new amendment another prior art reference is being used in the current office action. Further, Applicant highlights the word “forcibly”, in arguments, which does not appear in the original specification. Examiner interprets the limitation as the UE stops the RA procedure based on receiving the indication information for deactivating the first BWP. 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 KEVIN CUNNINGHAM whose telephone number is (571) 272-1765. The examiner can normally be reached Monday through Thursday 7:30-18:00 (EST). If attempts to reach the examiner by telephone are unsuccessful, the examiner’s supervisor, Huy Vu can be reached on (571) 272-3155. The fax number for the organization where this application or proceeding is assigned is 571-273-8300. Information regarding the status of an application may be obtained from the Patent Application Information Retrieval (PAIR) system. Status information for published applications may be obtained from either Private PAIR or Public PAIR. Status information for unpublished applications is available through Private PAIR only. For more information about the PAIR system, see http://pair-direct.uspto.gov. Should you have questions on access to the Private PAIR system, contact the Electronic Business Center (EBC) at 866-217-9197 (toll-free). If you would like assistance from a USPTO Customer Service Representative or access to the automated information system, call 800-786-9199 (IN USA OR CANADA) or 571-272-1000. /KEVIN M CUNNINGHAM/Primary Examiner, Art Unit 2461
Read full office action

Prosecution Timeline

Aug 09, 2023
Application Filed
Nov 02, 2025
Non-Final Rejection — §103
Jan 27, 2026
Response Filed
Apr 03, 2026
Final Rejection — §103 (current)

Precedent Cases

Applications granted by this same examiner with similar technology

Patent 12587411
SYSTEMS AND METHODS FOR ISOLATING NETWORK TRAFFIC OF MULTIPLE USERS ACROSS NETWORKS OF COMPUTING PLATFORMS
2y 5m to grant Granted Mar 24, 2026
Patent 12581535
RESOURCE EXCLUSION
2y 5m to grant Granted Mar 17, 2026
Patent 12574166
METHOD FOR RETRANSMISSION-RELATED OPERATION OF RELAY UE IN WIRELESS COMMUNICATION SYSTEM
2y 5m to grant Granted Mar 10, 2026
Patent 12532325
PDCCH MONITORING METHOD AND APPARATUS, STORAGE MEDIUM, TERMINAL, AND BASE STATION
2y 5m to grant Granted Jan 20, 2026
Patent 12526869
SLEEPING CELL DETECTION IN AN OPEN RADIO ACCESS NETWORK
2y 5m to grant Granted Jan 13, 2026
Study what changed to get past this examiner. Based on 5 most recent grants.

AI Strategy Recommendation

Get an AI-powered prosecution strategy using examiner precedents, rejection analysis, and claim mapping.
Powered by AI — typically takes 5-10 seconds

Prosecution Projections

3-4
Expected OA Rounds
72%
Grant Probability
84%
With Interview (+12.2%)
2y 9m
Median Time to Grant
Moderate
PTA Risk
Based on 577 resolved cases by this examiner. Grant probability derived from career allow rate.

Sign in with your work email

Enter your email to receive a magic link. No password needed.

Personal email addresses (Gmail, Yahoo, etc.) are not accepted.

Free tier: 3 strategy analyses per month