Prosecution Insights
Last updated: April 19, 2026
Application No. 18/317,509

SYSTEMS AND METHODS FOR PROVIDING TIMING ADVANCE (TA) VALUES

Non-Final OA §103
Filed
May 15, 2023
Examiner
KAO, JUTAI
Art Unit
2473
Tech Center
2400 — Computer Networks
Assignee
Huawei Technologies Co., Ltd.
OA Round
3 (Non-Final)
80%
Grant Probability
Favorable
3-4
OA Rounds
3y 3m
To Grant
98%
With Interview

Examiner Intelligence

Grants 80% — above average
80%
Career Allow Rate
531 granted / 664 resolved
+22.0% vs TC avg
Strong +18% interview lift
Without
With
+17.6%
Interview Lift
resolved cases with interview
Typical timeline
3y 3m
Avg Prosecution
34 currently pending
Career history
698
Total Applications
across all art units

Statute-Specific Performance

§101
4.1%
-35.9% vs TC avg
§103
58.1%
+18.1% vs TC avg
§102
18.5%
-21.5% vs TC avg
§112
13.1%
-26.9% vs TC avg
Black line = Tech Center average estimate • Based on career data from 664 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 . Continued Examination Under 37 CFR 1.114 A request for continued examination under 37 CFR 1.114, including the fee set forth in 37 CFR 1.17(e), was filed in this application after final rejection. Since this application is eligible for continued examination under 37 CFR 1.114, and the fee set forth in 37 CFR 1.17(e) has been timely paid, the finality of the previous Office action has been withdrawn pursuant to 37 CFR 1.114. Applicant's submission filed on 03/18/2026 has been entered. Response to Arguments Applicant’s arguments with respect to claim(s) 1, 3-5, 7, 8, 10-12, 14-18, 20 and 26-31 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. 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. Claim(s) 1, 3-5, 8, 10-12, 26, 28 and 30 is/are rejected under 35 U.S.C. 103 as being unpatentable over Lin (US 2024/0306187) in views of Wu (US 2021/0153263) and Wang (US 2021/0345381). Lin discloses the following features. Regarding claim 1, a method performed by an apparatus (see UE shown in Fig. 1 and Fig. 2), the method comprising: receiving physical layer control signaling, the physical layer control signaling carrying a group message for a group of apparatuses including the apparatus, the group message indicating a time-frequency resource for a data channel (see “physical downlink control channel (PDCCH) used to schedule msg2's physical downlink shared channel (PDSCH)…DCI“, recited in paragraph [0072], which shows that a PDCCH that carries a DCI being a physical control channel that is used to schedule the msg2; or see paragraph [0084], which recites “in 2-step RA procedure…PDSCH scheduled by PDCCH” for a two-step RACH procedure, wherein the PDSCH for msgB is scheduled by the PDCCH; that is the UE receives the message on the PDCCH that schedules the resource on the PDSCH, a data channel, for receiving the msg2/msgB; and see Fig. 3, wherein the DCI being transmitted in step 306 including an identifier determined in step 304, which “may be an identifier which can be used by a group of terminal devices to detect a PDCCH with the DCI format” recited in paragraph [0096]); decoding the group message to obtain message in the data channel on the time-frequency resource (see step 504 in Fig. 5, wherein the terminal obtains information regarding a scheduled downlink shared channel from the DCI). Regarding claim 3, wherein the physical layer control signaling includes a CRC scrambled using the group ID (see “The identifier comprises at least one of a common identifier or a specific identifier. The method further comprises transmitting information regarding a scheduled downlink shared channel with the format of DCI with the CRC scrambled by the identifier on a downlink control channel to at least one terminal device” recited in paragraph [0007]). Regarding claim 8, an apparatus (see UE shown in Fig. 1 and Fig. 2) comprising: a memory (see memory 722 in Fig. 7) to store processor-executable instructions; a processor (see processor 721 in Fig. 7) to execute the processor executable instructions to cause the processor to: receive physical layer control signaling, the physical layer control signaling carrying a group message for a group of apparatuses including the apparatus, the group message indicating a time-frequency resource for a data channel (see “physical downlink control channel (PDCCH) used to schedule msg2's physical downlink shared channel (PDSCH)…DCI“, recited in paragraph [0072], which shows that a PDCCH that carries a DCI being a physical control channel that is used to schedule the msg2; or see paragraph [0084], which recites “in 2-step RA procedure…PDSCH scheduled by PDCCH” for a two-step RACH procedure, wherein the PDSCH for msgB is scheduled by the PDCCH; that is the UE receives the message on the PDCCH that schedules the resource on the PDSCH, a data channel, for receiving the msg2/msgB; and see Fig. 3, wherein the DCI being transmitted in step 306 including an identifier determined in step 304, which “may be an identifier which can be used by a group of terminal devices to detect a PDCCH with the DCI format” recited in paragraph [0096]); decode the group message to obtain message in the data channel on the time-frequency resource (see step 504 in Fig. 5, wherein the terminal obtains information regarding a scheduled downlink shared channel from the DCI). Regarding claim 10, wherein the physical layer control signaling includes a CRC scrambled using the group ID (see “The identifier comprises at least one of a common identifier or a specific identifier. The method further comprises transmitting information regarding a scheduled downlink shared channel with the format of DCI with the CRC scrambled by the identifier on a downlink control channel to at least one terminal device” recited in paragraph [0007]). Regarding claim 15, a method performed by a device (see base station shown in Figs. 1-2), the method comprising: transmitting physical layer control signaling, the physical layer control signaling carrying a group message for the group of apparatuses, the group message indicating a time-frequency resource for a data channel, wherein a message is carried in the data channel on the time-frequency resource; and transmitting the TA message in the data channel on the time-frequency resource (see “physical downlink control channel (PDCCH) used to schedule msg2's physical downlink shared channel (PDSCH)…DCI“, recited in paragraph [0072], which shows that a PDCCH that carries a DCI being a physical control channel that is used to schedule the msg2; or see paragraph [0084], which recites “in 2-step RA procedure…PDSCH scheduled by PDCCH” for a two-step RACH procedure, wherein the PDSCH for msgB is scheduled by the PDCCH; that is the UE receives the message on the PDCCH that schedules the resource on the PDSCH, a data channel, for receiving the msg2/msgB; and see Fig. 3, wherein the DCI being transmitted in step 306 including an identifier determined in step 304, which “may be an identifier which can be used by a group of terminal devices to detect a PDCCH with the DCI format” recited in paragraph [0096]). Lin does not disclose the following features: regarding claims 1 and 8, wherein a TA message is carried in the data channel on the time-frequency resource; wherein the TA message is carried in the data channel; wherein the TA message includes a plurality of IDs, wherein each ID corresponding to a respective apparatus in the group of apparatuses, wherein included in the TA message for each ID is at least a TA value specific to the respective apparatus; and the TA message includes additional information relating to timing advance or synchronization; and obtaining, from the TA message, both (1) the TA value corresponding to the apparatus using the ID in the TA message that corresponds to the apparatus, and (2) the additional information relating to timing advance or synchronization; regarding claim 4, 11 and 17, wherein the group message further indicates a common TA value for the group of apparatuses; regarding claims 5, 12 and 18, wherein the TA value corresponding to the apparatus is an updated TA value for an adjustment to the common value; regarding claim 15, determining at least one TA value for at least one apparatus in a group of apparatuses; wherein a TA message is carried in the data channel; and transmitting the TA message in the data channel, wherein the TA message includes a plurality of IDs, wherein each ID corresponding to a respective apparatus in the group of apparatuses, wherein included in the TA message for each ID is at least a TA value specific to the respective apparatus; and the TA message includes additional information relating to timing advance or synchronization; regarding claims 26, 28 and 30, wherein the additional information comprises an indication of one or more of: a timing reference point, a beam direction, an orientation configuration, a subcarrier spacing, and/or a carrier frequency band Wu discloses the following features. Regarding claims 1 and 8, wherein a TA message is carried in the data channel on the time-frequency resource (see step S102 in Fig. 1, wherein the terminal receives a message 2 including target configuration information as shown in paragraph [0048] and see “the target configuration information may include at least one of the following: multiple preamble identities, multiple timing advances, multiple pieces of uplink resource allocation information used to indicate a transmission resource for a feedback message of Msg2, multiple terminal device identities, multiple contention resolution identities, and multiple pieces of wireless connection configuration information” recited in paragraph [0049]; and see “a network side transmits a random access response message Msg2 based on content of Msg1 by using a downlink data channel (for example, a PDSCH)” recited in paragraph [0046]); obtain the TA message in the data channel (see step S102 in Fig. 1, wherein the terminal receives a message 2 including target configuration information including timing advance information as shown in paragraph [0048]-[0049]; and see “a network side transmits a random access response message Msg2 based on content of Msg1 by using a downlink data channel (for example, a PDSCH)” recited in paragraph [0046]), wherein the TA message includes a plurality of IDs, (see “see “the target configuration information may include at least one of the following: multiple preamble identities, multiple timing advances, multiple pieces of uplink resource allocation information used to indicate a transmission resource for a feedback message of Msg2, multiple terminal device identities, multiple contention resolution identities, and multiple pieces of wireless connection configuration information” recited in paragraph [0049]), and wherein the TA message includes additional information relating to timing advance or synchronization (see “the target configuration information may include at least one of the following: multiple preamble identities, multiple timing advances, multiple pieces of uplink resource allocation information used to indicate a transmission resource for a feedback message of Msg2, multiple terminal device identities, multiple contention resolution identities, and multiple pieces of wireless connection configuration information” recited in paragraph [0049], wherein at least the preamble identity is related to the timing advance/synchronization as the preamble transmission in msg1/msgA results in the transmission of the msg2/msgB that includes the timing advance); and obtaining, from the TA message, both (1) the TA value corresponding to the apparatus using the ID in the TA message that corresponds to the apparatus, and (2) the additional information relating to timing advance or synchronization (see TA values and additional information as shown in paragraph [0049] and see “the terminal device 11 may obtain, based on the association relationship, configuration information that is associated with the target association parameter of the terminal device 11 from the target configuration information” recited in paragraph [0050], wherein the apparatus obtains the values corresponding information corresponding to the apparatus). Regarding claim 15, determining at least one TA value for at least one apparatus in a group of apparatuses (see step S102 in Fig. 1, wherein the terminal receives a message 2 including target configuration information as shown in paragraph [0048] and see “the target configuration information may include at least one of the following: multiple preamble identities, multiple timing advances, multiple pieces of uplink resource allocation information used to indicate a transmission resource for a feedback message of Msg2, multiple terminal device identities, multiple contention resolution identities, and multiple pieces of wireless connection configuration information” recited in paragraph [0049], wherein the base station must determine the TA value in order to transmit the TA value to the terminal); wherein a TA message is carried in the data channel and transmitting the TA message in the data channel (see “a network side transmits a random access response message Msg2 based on content of Msg1 by using a downlink data channel (for example, a PDSCH)” recited in paragraph [0046]). Wang discloses the following features. Regarding claims 1, 8 and 15, wherein each ID corresponding to a respective apparatus in the group of apparatuses, wherein included in the TA message for each ID is at least a TA value specific to the respective apparatus (see “the aggregated-command message includes a table of user equipment identities (UEIDs) for the UEs in the UECS and respective timing advance values for those UEs” recited in paragraph [0072]). Regarding claims 4, 11 and 17, wherein the group message further indicates a common TA value for the group of apparatuses (see “In an alternative, the aggregated-command message values can be sent as a timing advance value for the coordinating UE” recited in paragraph [0072], or alternatively, see “a command setting (e.g., a transmit power control setting or a timing advance setting) may be the same for (common to) all the UEs in the UECS” recited in paragraph [0074]). Regarding claims 5, 12 and 18, wherein the TA value corresponding to the apparatus is an updated TA value for an adjustment to the common value (see “In an alternative, the aggregated-command message values can be sent as a timing advance value for the coordinating UE and difference (delta) timing advance values for the other UEs from the timing advance value for the coordinating UE” recited in paragraph [0072]). Regarding claims 26, 28 and 30, wherein the additional information comprises an indication of one or more of: a timing reference point (see “In an alternative, the aggregated-command message values can be sent as a timing advance value for the coordinating UE and difference (delta) timing advance values for the other UEs from the timing advance value for the coordinating UE” recited in paragraph [0072], wherein the timing advance value for the coordinating UE can be considered as a timing reference point), a beam direction, an orientation configuration, a subcarrier spacing, and/or a carrier frequency band It would have been obvious to one of ordinary skill in the art at the effective filing date of the current application to modify the system of Lin using features, as taught by Wu and Wang, in order to reduce transmission overhead by aggregating configuration information and commands transmitted for a plurality of UEs (see paragraph [0049] of Wu and paragraph [0015] of Wang). Claim(s) 7 and 14 is/are rejected under 35 U.S.C. 103 as being unpatentable over Lin, Wu and Wang as applied to claims 1 and 8 above, and further in view of Yang (US 2021/0345281). Lin, Wu and Wang disclose the features as shown above. Lin does not disclose the following features: regarding claims 7 and 14, transmitting information with a time offset that is based on the TA value for the apparatus. Yang discloses the following features. Regarding claims 7 and 14, transmitting information with a time offset that is based on the TA value for the apparatus (see “If the TA signaling includes the relative value of the TA, the UE adds the relative value to the current TA value and uses the sum for the uplink signal transmission” recited in paragraph [0047]). It would have been obvious to one of ordinary skill in the art at the effective filing date of the current application to modify the system of Lin, Wu and Wang using features, as taught by Yang, in order to reduce signaling overhead (see paragraph [0004] and [0047] of Yang). Claim(s) 20 is/are rejected under 35 U.S.C. 103 as being unpatentable over Lin, Wu and Wang as applied to claim 15 above, and further in view of Cirik (US 12,003,988). Lin, Wu and Wang disclose the features as shown above. Lin does not disclose the following features: regarding claim 20, wherein the group message is transmitted during a wake-up duration of the at least one apparatus when the at least one apparatus is in a power saving state. Cirik discloses the following features. Regarding claim 20, wherein the group message is transmitted during a wake-up duration of the at least one apparatus when the at least one apparatus is in a power saving state (see Fig. 16A, wherein the UE monitors the PDCCH during the DRX On duration; Zhou as applied to claim 15 above, receives the group message in a DCI transmitted on the PDCCH). It would have been obvious to one of ordinary skill in the art at the effective filing date of the current application to modify the system of Lin, Wu and Wang using features, as taught by Cirik, in order to save power consumption (see column 36, lines 26-41 of Cirik). Claim(s) 27, 29 and 31 is/are rejected under 35 U.S.C. 103 as being unpatentable over Lin, Wu and Wang as applied to claim 15 above, and further in view of Luo (US 2020/0112890). Lin, Wu and Wang disclose the features as shown above. Lin does not disclose the following features: regarding claims 27, 29 and 31, transmitting a capability report upon initial entry into a network, wherein the capability report indicates, for the apparatus, at least one of: support for group TA adjustment, one or more frequency bands of operation, a beam capability, and/or ability to transmit a dedicated uplink synchronization signal. Luo discloses the following features. Regarding claims 27, 29 and 31, transmitting a capability report upon initial entry into a network (see “during an initial registration process of the UE with the network including the BS” recited in paragraph [0054]), wherein the capability report indicates, for the apparatus, at least one of: support for group TA adjustment, one or more frequency bands of operation, a beam capability (see “a UE may report a beam correspondence capability to a BS” recited in paragraph [0054]), and/or ability to transmit a dedicated uplink synchronization signal. It would have been obvious to one of ordinary skill in the art at the effective filing date of the current application to modify the system of Lin, Wu and Wang using features, as taught by Luo, in order to report the UE’s beam correspondence capability to a base station (see paragraph [0054] of Luo). Conclusion Any inquiry concerning this communication or earlier communications from the examiner should be directed to JUTAI KAO whose telephone number is (571)272-9719. The examiner can normally be reached Monday-Friday 8:00-17:00 EST. 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, Kwang Yao can be reached at (571)272-3182. 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. /JUTAI KAO/ Primary Examiner, Art Unit 2473
Read full office action

Prosecution Timeline

May 15, 2023
Application Filed
Jun 10, 2025
Non-Final Rejection — §103
Sep 04, 2025
Response Filed
Dec 12, 2025
Final Rejection — §103
Mar 16, 2026
Request for Continued Examination
Mar 25, 2026
Response after Non-Final Action
Mar 30, 2026
Non-Final Rejection — §103 (current)

Precedent Cases

Applications granted by this same examiner with similar technology

Patent 12598566
IAB Timing Delta MAC CE Enhancement for Case #6 Timing Support
2y 5m to grant Granted Apr 07, 2026
Patent 12574971
PRIORITY HANDLING FOR A RANDOM ACCESS MESSAGE THAT INCLUDES A PREAMBLE AND A PAYLOAD
2y 5m to grant Granted Mar 10, 2026
Patent 12556434
UPLINK SOUNDING REFERENCE SIGNAL (SRS) TRANSMISSION IN CARRIER AGGREGATION SYSTEM
2y 5m to grant Granted Feb 17, 2026
Patent 12557056
METHOD FOR TIMING SYNCHRONIZATION, TERMINAL DEVICE, AND NETWORK DEVICE
2y 5m to grant Granted Feb 17, 2026
Patent 12550185
CONFLICT AVOIDANCE BETWEEN RANDOM ACCESS MESSAGES AND OTHER TRANSMISSIONS
2y 5m to grant Granted Feb 10, 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
80%
Grant Probability
98%
With Interview (+17.6%)
3y 3m
Median Time to Grant
High
PTA Risk
Based on 664 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