Prosecution Insights
Last updated: October 26, 2026
Application No. 18/725,278

LOCATION INFORMATION PROVISIONING

Final Rejection §102§103
Filed
Jun 28, 2024
Priority
Jan 10, 2022 — provisional 63/298,070 +1 more
Examiner
WONG, XAVIER S
Art Unit
2415
Tech Center
2400 — Computer Networks
Assignee
Telefonaktiebolaget LM Ericsson
OA Round
2 (Final)
88%
Grant Probability
Favorable
3-4
OA Rounds
5m
Est. Remaining
98%
With Interview

Examiner Intelligence

Grants 88% — above average
88%
Career Allowance Rate
906 granted / 1030 resolved
+30.0% vs TC avg
Moderate +10% lift
Without
With
+10.2%
Interview Lift
resolved cases with interview
Typical timeline
2y 9m
Avg Prosecution
28 currently pending
Career history
1070
Total Applications
across all art units

Statute-Specific Performance

§101
7.9%
-32.1% vs TC avg
§103
54.7%
+14.7% vs TC avg
§102
23.4%
-16.6% vs TC avg
§112
4.7%
-35.3% vs TC avg
Black line = Tech Center average estimate • Based on career data from 1030 resolved cases

Office Action

§102 §103
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 . Information Disclosure Statement The information disclosure statement (IDS) submitted on 26th May 2026 is in compliance with the provisions of 37 CFR 1.97. Accordingly, the information disclosure statement is being considered by the examiner. ========== ========== ========== Claim Rejections - 35 USC § 102 The text of those sections of Title 35, U.S. Code not included in this action can be found in a prior Office action. Claims 1, 2, 4 – 6 ,8 – 9, 11, 15, 17,19, 21, 22 ,24, 26 – 28 and 32 are rejected under 35 U.S.C. 102(a)(2) as being anticipated by Shin et al (US 2021/0352690 A1). Claim 32 (similarly Claim 1). Shin shows a user equipment (UE) for location provisioning (figs. 1 and 21: UE 100; abstract), the UE comprising: processing circuitry (fig. 21: communication circuit) configured to determine to send location information ([0700]: if the UE transmits something such as MSG3 through a PUR, it may be configured to receive a DL grant in a legacy common search space); and a communication interface (fig. 21: transceiver(s)) configured to, as a result of determining to send location information, send the location information to a network node (see above; [0700]: the UE may configure that which legacy common search space the UE should monitor; [0706]: if the feedback DCI has been received in a search space (or search space candidate) of a specific location while the UE is monitoring as much as the corresponding feedback window, it may be configured that other search spaces (or other search space candidates) in the next feedback window do not need to be monitored), wherein sending the location information to the network node comprises: sending the location information using one or more preconfigured uplink resources, PURs ([0706]: the UE may transmit PUR and shall monitor whether feedback DCI is transmitted for a time corresponding to N times the search space period… if the feedback DCI has been received in a search space (or search space candidate) of a specific location while the UE is monitoring as much as the corresponding feedback window, it may be configured that other search spaces (or other search space candidates) in the next feedback window do not need to be monitored), or sending a connection establishment procedure message as part of a connection establishment procedure ([0729]: self-release the corresponding PUR and perform a fallback operation wherein the fallback operation may include attempting to transmit data through an EDT procedure, performing a RACH procedure for entering an RRC connected mode), wherein the connection establishment procedure message comprises the location information ([0729]: it may be configured that data transmission is performed in a PUR at a preset location). Claim 2. Shin shows the method of claim 1, further comprising receiving location reporting configuration information ([0706]: if the base station has set N number of times of the search space period in which feedback DCI can be transmitted as the feedback window), wherein the determination as to whether to send the location information or refrain from sending the location information is based on the location reporting configuration ([0706]: the UE may transmit PUR and shall monitor whether feedback DCI is transmitted for a time corresponding to N times the search space period). Claim 4. Shin shows the method of claim 2, wherein the location reporting configuration information is applicable for an early data transmission, EDT, ([0687]: if the base station can indicate the EDT in the (N)PDCCH order, the UE may be configured to transmit retransmission of the previous PUR through the EDT) or a PUR transmission (see above). Claim 5. Shin shows the method of claim 1, wherein sending the location information comprises sending the connection establishment procedure message ([0683]: if a UE transmits MSG3 or the like through a PUR, then an NPDSCH can be subsequently scheduled, and the UE can receive an RRC connection message such as connection (re-)establishment through the corresponding NPDSCH), and the connection establishment procedure message is a message transmitted in response to receiving a random access response message transmitted by the network node ([0633]: for NPUSCH (re)transmissions corresponding to a random access response grant). Claim 6. Shin shows the method of claim 1, further comprising determining if the user equipment needs to report its location ([0699]: when the UE indicates the PUR release on the (N)PDSCH(s), the UE may report ACK (or NACK) therefor or transmit a response thereto on the (N)PUSCH). Claim 8. Shin shows the method of claim 2, wherein receiving the location reporting configuration information comprises receiving a broadcast system information ([0418]: the UE monitors the NPDCCH UE-specific search space on the same NB-IoT carrier on which NPSS/NSSS/NPBCH are detected), wherein the system information comprises the location reporting configuration information ([0451]: if resource element (k, l’) is used for Narrowband IoT, and 0 otherwise, and fNB-IoT is the frequency location of the carrier of the narrowband IoT PRB minus the frequency location of the center of the LTE signal). Claim 9. Shin shows the method of claim 1, wherein the location information is sent in a UE Information Response message that is an independent PDU that is sent in Msg3 of EDT ([0731]: if PUR configuration is not proceeded in the connected mode (e.g. if the PUR configuration is indicated through EDT), it may be configured to use as it is TX power values used for PUSCH transmission containing MSG3) or in the PUR PUSCH (see above). Claim 11. Shin shows the method of claim 1, further comprising receiving a feedback message from the network node indicating that the location information needs to be resent or that more detailed location information needs to be sent ([0722]: the base station may be configured to give feedback for the corresponding UL data, and the base station may be configured to indicate, to the UE, a location at which the corresponding feedback is given), wherein the feedback message comprises a request for a new location ([0724]: the base station may newly configure a UE-specific PUR to the corresponding UE) or a rejection of the prior location information (n/a). ---------- ---------- ---------- Claim 34 (similarly Claim 15). Shin shows a network node for location provisioning (figs. 1: base station 200; abstract), the network node comprising: processing circuitry (fig. 21: communication circuit) configured to determine location reporting configuration information to be reported to a UE ([0666]: it may be configured such that an ACK/NACK mapping order is determined depending on a UL data transmission time/frequency/code/spatial resource location of a PUR configured by the base station (i.e. a relative location between resources within the PUR or a location of a PRB/base station transmit antenna port resource within absolute time/system BW); [0676]: the base station may indicate to the UE that the UE performs adaptive retransmission through a specific field of DCI indicating ACK/NACK wherein the UE receiving this indication may be configured to perform retransmission of UL data to a location scheduled by the corresponding DCI field); and a communication interface (fig. 21: transceiver(s)) configured to provide location reporting configuration information to the UE ([0722]: the base station may be configured to indicate, to the UE, a location at which the corresponding feedback is given); and receive location information from the UE ([0700]: the UE may configure that which legacy common search space the UE should monitor; [0706]: if the feedback DCI has been received in a search space (or search space candidate) of a specific location while the UE is monitoring as much as the corresponding feedback window, it may be configured that other search spaces (or other search space candidates) in the next feedback window do not need to be monitored), wherein receiving the location information comprises: receiving the location information using one or more preconfigured uplink resources, PURs ([0706]: the UE may transmit PUR and shall monitor whether feedback DCI is transmitted for a time corresponding to N times the search space period… if the feedback DCI has been received in a search space (or search space candidate) of a specific location while the UE is monitoring as much as the corresponding feedback window, it may be configured that other search spaces (or other search space candidates) in the next feedback window do not need to be monitored), or receiving a connection establishment procedure message as part of a connection establishment procedure ([0729]: self-release the corresponding PUR and perform a fallback operation wherein the fallback operation may include attempting to transmit data through an EDT procedure, performing a RACH procedure for entering an RRC connected mode), wherein the connection establishment procedure message comprises the location information ([0729]: it may be configured that data transmission is performed in a PUR at a preset location). Claim 17. Shin shows the method of claim 15, wherein the location reporting configuration information is applicable for EDT ([0687]: if the base station can indicate the EDT in the (N)PDCCH order, the UE may be configured to transmit retransmission of the previous PUR through the EDT) or PUR (see above). Claim 19. Shin shows the method of claim 18, further comprising: receiving a random access preamble transmitted by the UE ([0181]: to indicate a random access response that is a response to transmission of a random access preamble of the UE, a random access-RNTI (RA-RNTI) can be masked to the CRC); after receiving the random access preamble, transmitting to the UE a random access response, RAR (see above); and after transmitting to the UE the RAR, receiving a message responsive to the RAR ([0519]: the UE is preferentially informed in which subframes the SPS is to be transmitted/received via radio resource control (RRC) signaling), wherein the message responsive to the RAR comprises a Radio Resource Control, RRC, connection resume request message that comprises the location information ([0519]: since the UE is allocated only the time resource domain via RRC signaling, even if the UE has received the RRC signaling, the UE does not immediately perform transmission/reception by the SPS, and completes the allocation of time-frequency resources by allocating the frequency resource domain, if necessary). Claim 21. Shin shows the method of claim 15, wherein the location information is received in a UE Information Response message that is an independent PDU that is received in Msg3 of EDT ([0731]: if PUR configuration is not proceeded in the connected mode (e.g. if the PUR configuration is indicated through EDT), it may be configured to use as it is TX power values used for PUSCH transmission containing MSG3) or in the PUR PUSCH (see above). Claim 22. Shin shows the method of claim 15, further comprising sending a feedback message to the UE indicating that the location information needs to be resent or that more detailed location information needs to be sent ([0722]: the base station may be configured to give feedback for the corresponding UL data, and the base station may be configured to indicate, to the UE, a location at which the corresponding feedback is given) wherein the feedback message comprises a request for a new location or a rejection of the prior location information ([0724]: the base station may newly configure a UE-specific PUR to the corresponding UE). Claim 26. Shin shows the method of claim 15, wherein the type of location information is based on the amount of movement since the last report ([0056]: identifying an object in the dark and notifying a driver of the distance and movement of the object, over a thing seen by the driver through a front window). Claim 27. Shin shows the method of claim 25, further comprising determining that the received location information is insufficient or unsatisfactory ([0666]: it may be configured such that an ACK/NACK mapping order is determined depending on a UL data transmission time/frequency/code/spatial resource location of a PUR configured by the base station; [0698]: when it is determined that new resources to be allocated for retransmission by the UE are insufficient or that the reason for the failure to detect data previously received from the PUR is a transmission timing of the UE or that it is determined that there is a problem with the transmit power, the base station may fallback to a legacy operation so that transmission timing and power can be readjusted rather than allocating new uplink resources). Claim 28. Shin shows the method of claim 15, further comprising determining that the UE has not moved ([0145]: the map data may include object identification information for fixed objects – fixed objects do not move). ---------- ---------- ---------- Claim Rejections - 35 USC § 103 The text of those sections of Title 35, U.S. Code not included in this action can be found in a prior Office action. Claims 3, 14 and 16 are rejected under 35 U.S.C. 103 as being unpatentable over Shin et al in view of Kudekar et al (US 2016/0088584 A1). Claim 3. Shin shows the method of claim 2; Shin does not expressly describe wherein the location reporting configuration information comprises an indication of whether to send coarse location information, fine location information, or no location information.Kudekar teaches feature of location reporting configuration information comprising indication of whether to send coarse location or fine location information ([0051]: the determination of whether the location estimate is sufficiently accurate may be based on a predetermined threshold criterion; [0032]: the server can then receive from the first surveyor device a coarse location estimate of the unknown AP based on this coarse signal information… the server can then receive from the second surveyor device a fine location estimate of the unknown AP).It would have been obvious to one of ordinary skill in the art before the effective filing date of the claimed invention to implement the location information indication feature as taught by Kudekar in the reporting configuration information of Shin to give more accurate location estimates. Claim 14. Shin shows the method of claim 1; Shin does not expressly describe wherein determining whether to send location information comprises determining whether to send coarse location information or fine location information.Kudekar teaches feature of location reporting configuration information comprising indication of whether to send coarse location or fine location information ([0051]: the determination of whether the location estimate is sufficiently accurate may be based on a predetermined threshold criterion; [0032]: the server can then receive from the first surveyor device a coarse location estimate of the unknown AP based on this coarse signal information… the server can then receive from the second surveyor device a fine location estimate of the unknown AP).It would have been obvious to one of ordinary skill in the art before the effective filing date of the claimed invention to implement the location information indication feature as taught by Kudekar in the reporting configuration information of Shin to give more accurate location estimates. Claim 16. Shin shows the method of claim 15; Shin does not expressly describe wherein the location reporting configuration information comprises an indication of whether to send coarse location information, fine location information, or no location information.Kudekar teaches feature of location reporting configuration information comprising indication of whether to send coarse location or fine location information ([0051]: the determination of whether the location estimate is sufficiently accurate may be based on a predetermined threshold criterion; [0032]: the server can then receive from the first surveyor device a coarse location estimate of the unknown AP based on this coarse signal information… the server can then receive from the second surveyor device a fine location estimate of the unknown AP).It would have been obvious to one of ordinary skill in the art before the effective filing date of the claimed invention to implement the location information indication feature as taught by Kudekar in the reporting configuration information of Shin to give more accurate location estimates. ========== ========== ========== Response to Arguments Applicant’s arguments filed on 13th August 2026 have been fully considered but they are not persuasive. The applicant disagrees that independent Claim 32, and similarly Claim 1, is being anticipated by prior art of record Shin. The following is an explanation of how Shin maps to the claims: a user equipment (UE) for location provisioning (figs. 1 and 21: UE 100; abstract: the UE receives, from the base station, a preconfigured uplink (UL) resource (PUR) configuration via RRC signalling) → further in paragraph 0134 cites “the map data may include object identification information for fixed objects, such as a wall and a door, and movable objects, such as a flowerpot and a desk… the object identification information may include a name, a type, a distance, a location, etc.” which is clearly location provisioning technique. the UE comprising: processing circuitry (fig. 21: communication circuit) configured to… → (see figure). determine to send location information ([0700]: if the UE transmits something such as MSG3 through a PUR, it may be configured to receive a DL grant in a legacy common search space) → further in paragraphs 0664 to 0666 cite “a value that can be used as different UE information may be configured to use an RNTI value calculated based on a time/frequency/code/spatial resource location of a PUR transmitted by each UE and/or a unique UE ID… if RNTI is generated only with the time/frequency/code/spatial resource location of a PUR, RNTI may all be calculated the same, so UE-specific information such as a unique UE ID may be considered essentially… it may be configured such that an ACK/NACK mapping order is determined depending on a UL data transmission time/frequency/code/spatial resource location of a PUR configured by the base station (i.e. a relative location between resources within the PUR or a location of a PRB/base station transmit antenna port resource within absolute time/system BW)” and paragraph 0672 also cites “the UE receiving this indication may be configured to perform retransmission of UL data to a location scheduled by the corresponding DCI field” which clearly reads on as a “to send” location. and a communication interface (fig. 21: transceiver(s)) configured to… → (see figure). as a result of determining to send location information, send the location information to a network node (see above; [0700]: the UE may configure that which legacy common search space the UE should monitor; [0706]: if the feedback DCI has been received in a search space (or search space candidate) of a specific location while the UE is monitoring as much as the corresponding feedback window, it may be configured that other search spaces (or other search space candidates) in the next feedback window do not need to be monitored) → further in paragraph 0707 cites “in a search space that a UE monitors after transmitting data to the PUR (the corresponding search space may be a channel for scheduling retransmission or HARQ feedback for data transmitted to the PUR or may be configured to the UE for (a-)periodically transmitted channel for TA and/or TPC adjustment), it may be configured that the UE can expect a reference signal (e.g. NRS)… a subframe in which the NRS can be transmitted may be limited to Y subframe after the start of the search space from a location preceding a subframe configured such that the search space is transmitted” which a feedback (e.g. result) is involved of a reference signal (e.g. NRS) then a search space (to send location) is transmitted. wherein sending the location information to the network node comprises: sending the location information using one or more preconfigured uplink resources, PURs ([0706]: the UE may transmit PUR and shall monitor whether feedback DCI is transmitted for a time corresponding to N times the search space period… if the feedback DCI has been received in a search space (or search space candidate) of a specific location while the UE is monitoring as much as the corresponding feedback window, it may be configured that other search spaces (or other search space candidates) in the next feedback window do not need to be monitored) → further paragraph 0700 cites “if the UE transmits something such as MSG3 through a PUR, it may be configured to receive a DL grant in a legacy common search space (e.g. Type 1/2, 1A/2A NPDCCH CSS) that exists after a transmission time point” in which location and PUR parameters are used for MSG3 transmission, therefore, this limitation condition is met. or → only one of multiple conditions, such as the limitation condition above, is required sending a connection establishment procedure message as part of a connection establishment procedure ([0729]: self-release the corresponding PUR and perform a fallback operation wherein the fallback operation may include attempting to transmit data through an EDT procedure, performing a RACH procedure for entering an RRC connected mode) → further in paragraphs 0730 and 0731 cite “it may be configured that a UE that enters an idle mode and wishes to transmit a PUR uses as it is TX power used for (N)PUSCH transmission used in the connected mode immediately before entering the idle mode… if PUR configuration is not proceeded in the connected mode (e.g. if the PUR configuration is indicated through EDT), it may be configured to use as it is TX power values used for PUSCH transmission containing MSG3, and it may be configured to use a value obtained by adding a specific offset to all the corresponding TX power values (or to a specific parameter for calculating the TX power values)” in which the above is adequate to justify a connection establishment procedure message being sent by the UE, and therefore, reads on to the limitation’s condition. wherein the connection establishment procedure message comprises the location information ([0729]: it may be configured that data transmission is performed in a PUR at a preset location) → also in paragraph 0729 cites “the fallback operation may include attempting to transmit data through an EDT procedure, performing a RACH procedure for entering an RRC connected mode, or performing a predefined operation for TA update. If a PUR is shared with other users, after a transmission failure in the PUR at a specific location” which implies that in order to get into “connected mode,” a PUR location information is involved. Although the claims are interpreted in light of the specification, limitations from the specification are not read into the claims. See In re Van Geuns, 988 F.2d 1181, 26 USPQ2d 1057 (Fed. Cir. 1993). ---------- ---------- ---------- Conclusion THIS ACTION IS MADE FINAL. 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 Xavier Szewai Wong whose telephone number is 571.270.1780. The examiner can normally be reached on 11:30 am - 8:30 pm Mon to Fri. 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, Jeffrey Rutkowski can be reached on 571.270.1215. The fax phone 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. /XAVIER S WONG/Primary Examiner, Art Unit 2415 3rd October 2026
Read full office action

Prosecution Timeline

Jun 28, 2024
Application Filed
May 13, 2026
Non-Final Rejection mailed — §102, §103
Aug 13, 2026
Response Filed
Oct 14, 2026
Final Rejection mailed — §102, §103 (current)

Precedent Cases

Applications granted by this same examiner with similar technology

Patent 12756658
METHOD FOR ADVERTISING PROCESSING CAPABILITY OF NETWORK DEVICE, DEVICE, AND SYSTEM
3y 4m to grant Granted Oct 06, 2026
Patent 12756656
IDENTIFYING A LOOP IN AN EXTERNAL NETWORK
2y 12m to grant Granted Oct 06, 2026
Patent 12750300
ACCESSING LOCAL NETWORK DEVICES VIA MESH NETWORK DEVICES
3y 4m to grant Granted Sep 29, 2026
Patent 12745277
TECHNIQUES FOR FULL-DUPLEX OPERATION ON SIDELINK AND DOWNLINK IN WIRELESS COMMUNICATIONS SYSTEMS
3y 1m to grant Granted Sep 22, 2026
Patent 12744730
PACKET FORWARDING METHOD AND SYSTEM, STORAGE MEDIUM, AND ELECTRONIC DEVICE
3y 0m to grant Granted Sep 22, 2026
Study what changed to get past this examiner. Based on 5 most recent grants.

Strategy Recommendation AI-generated — please review before filing

Get a prosecution strategy drawn from examiner precedents, rejection analysis, and claim mapping.
Typically takes 5-10 seconds — AI-generated, attorney review required before filing

Prosecution Projections

3-4
Expected OA Rounds
88%
Grant Probability
98%
With Interview (+10.2%)
2y 9m (~5m remaining)
Median Time to Grant
Moderate
PTA Risk
Based on 1030 resolved cases by this examiner. Grant probability derived from career allowance 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