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 § 112
The following is a quotation of 35 U.S.C. 112(b):
(b) CONCLUSION.—The specification shall conclude with one or more claims particularly pointing out and distinctly claiming the subject matter which the inventor or a joint inventor regards as the invention.
The following is a quotation of 35 U.S.C. 112 (pre-AIA ), second paragraph:
The specification shall conclude with one or more claims particularly pointing out and distinctly claiming the subject matter which the applicant regards as his invention.
1. Claim 42 recites the limitation "the mapping" in line 1. There is insufficient antecedent basis for this limitation in the claim.
Double Patenting
The nonstatutory double patenting rejection is based on a judicially created doctrine grounded in public policy (a policy reflected in the statute) so as to prevent the unjustified or improper timewise extension of the “right to exclude” granted by a patent and to prevent possible harassment by multiple assignees. A nonstatutory double patenting rejection is appropriate where the conflicting claims are not identical, but at least one examined application claim is not patentably distinct from the reference claim(s) because the examined application claim is either anticipated by, or would have been obvious over, the reference claim(s). See, e.g., In re Berg, 140 F.3d 1428, 46 USPQ2d 1226 (Fed. Cir. 1998); In re Goodman, 11 F.3d 1046, 29 USPQ2d 2010 (Fed. Cir. 1993); In re Longi, 759 F.2d 887, 225 USPQ 645 (Fed. Cir. 1985); In re Van Ornum, 686 F.2d 937, 214 USPQ 761 (CCPA 1982); In re Vogel, 422 F.2d 438, 164 USPQ 619 (CCPA 1970); In re Thorington, 418 F.2d 528, 163 USPQ 644 (CCPA 1969).
A timely filed terminal disclaimer in compliance with 37 CFR 1.321(c) or 1.321(d) may be used to overcome an actual or provisional rejection based on nonstatutory double patenting provided the reference application or patent either is shown to be commonly owned with the examined application, or claims an invention made as a result of activities undertaken within the scope of a joint research agreement. See MPEP § 717.02 for applications subject to examination under the first inventor to file provisions of the AIA as explained in MPEP § 2159. See MPEP § 2146 et seq. for applications not subject to examination under the first inventor to file provisions of the AIA . A terminal disclaimer must be signed in compliance with 37 CFR 1.321(b).
The filing of a terminal disclaimer by itself is not a complete reply to a nonstatutory double patenting (NSDP) rejection. A complete reply requires that the terminal disclaimer be accompanied by a reply requesting reconsideration of the prior Office action. Even where the NSDP rejection is provisional the reply must be complete. See MPEP § 804, subsection I.B.1. For a reply to a non-final Office action, see 37 CFR 1.111(a). For a reply to final Office action, see 37 CFR 1.113(c). A request for reconsideration while not provided for in 37 CFR 1.113(c) may be filed after final for consideration. See MPEP §§ 706.07(e) and 714.13.
The USPTO Internet website contains terminal disclaimer forms which may be used. Please visit www.uspto.gov/patent/patents-forms. The actual filing date of the application in which the form is filed determines what form (e.g., PTO/SB/25, PTO/SB/26, PTO/AIA /25, or PTO/AIA /26) should be used. A web-based eTerminal Disclaimer may be filled out completely online using web-screens. An eTerminal Disclaimer that meets all requirements is auto-processed and approved immediately upon submission. For more information about eTerminal Disclaimers, refer to www.uspto.gov/patents/apply/applying-online/eterminal-disclaimer.
2. Claims 28-45 are provisionally rejected on the ground of nonstatutory double patenting as being unpatentable over claims 28, 30-32, 34-39, 41-43, and 45 of copending Application No. 19/083,014 (see Claims dated 7/2/2026 for Application 19/083,014). Although the claims at issue are not identical, they are not patentably distinct from each other because of the following reasons.
The Examiner notes U.S. Patent 12,732,947 (e.g., copending application 19/083,014) is not available for viewing yet. The latest claim set for application 19/083,014 dated 7/2/2026 will be used.
Claim 28 of the instant application is anticipated by U.S. Patent 12,732,947 (e.g., copending application 19/083,014 – claims dated 7/2/2026) claim 28. For example, the instant application is a broader version therefore is an obvious variant. Claim 28 of the instant application recites all the elements of claim 28 in U.S. Patent 12,732,947 (e.g., copending application 19/083,014) with the exception of “wherein the position of the terminal device is determined based on synchronization offsets among the plurality of supporting terminal devices; receive, from a network entity, the synchronization offsets among the plurality of supporting terminal devices; and determine the position of the terminal device based on the measurements and the synchronization offsets mapping among the plurality of supporting terminal devices”. Nonetheless, the removal of said limitation from claim 28 of the present application makes the claim a broader version of U.S. Patent 12,732,947 (e.g., copending application 19/083,014). Therefore, since the omission of an element and its function in a combination is an obvious expedient if the remaining elements perform the same functions as before (In re Karlson (CCPA) 136 USPQ 184 (1963), claim 28 of the instant application is not patentably distinct from claim 28 of U.S. Patent 12,732,947 (e.g., copending application 19/083,014)
Claim 37 of the instant application is anticipated by U.S. Patent 12,732,947 (e.g., copending application 19/083,014 – claims dated 7/2/2026) claim 37. For example, the instant application is a broader version therefore is an obvious variant. Claim 37 of the instant application recites all the elements of claim 37 in U.S. Patent 12,732,947 (e.g., copending application 19/083,014) with the exception of “provide, to a location management entity, a synchronization offset between the terminal device and another terminal device, wherein the position of the target terminal device is determined based on provided by the location management entity, synchronization offsets mapping among the plurality of supporting terminal devices”. Nonetheless, the removal of said limitation from claim 37 of the present application makes the claim a broader version of U.S. Patent 12,732,947 (e.g., copending application 19/083,014). Therefore, since the omission of an element and its function in a combination is an obvious expedient if the remaining elements perform the same functions as before (In re Karlson (CCPA) 136 USPQ 184 (1963), claim 37 of the instant application is not patentably distinct from claim 37 of U.S. Patent 12,732,947 (e.g., copending application 19/083,014)
Claim 43 of the instant application is anticipated by U.S. Patent 12,732,947 (e.g., copending application 19/083,014 – claims dated 7/2/2026) claim 43. For example, the instant application is a broader version therefore is an obvious variant. Claim 43 of the instant application recites all the elements of claim 43 in U.S. Patent 12,732,947 (e.g., copending application 19/083,014) with the exception of “acquire synchronization offsets from among the plurality of supporting terminal devices; and provide, to the target terminal device, the synchronization offsets among the plurality of supporting terminal devices, wherein the synchronization offsets among the plurality of supporting terminal devices are used to determine a position of the target terminal device”. Nonetheless, the removal of said limitation from claim 43 of the present application makes the claim a broader version of U.S. Patent 12,732,947 (e.g., copending application 19/083,014). Therefore, since the omission of an element and its function in a combination is an obvious expedient if the remaining elements perform the same functions as before (In re Karlson (CCPA) 136 USPQ 184 (1963), claim 43 of the instant application is not patentably distinct from claim 28 of U.S. Patent 12,732,947 (e.g., copending application 19/083,014).
Claim 29 of the instant application is met by claim 28 of U.S. Patent 12,732,947 (e.g., copending application 19/083,014).
Claims 30-32 of the instant application are met by claims 30-32 of U.S. Patent 12,732,947 (e.g., copending application 19/083,014).
Claim 33 of the instant application is met by claim 28 of U.S. Patent 12,732,947 (e.g., copending application 19/083,014).
Claims 34-36 of the instant application are met by claims 34-36 of U.S. Patent 12,732,947 (e.g., copending application 19/083,014).
Claims 38-42 of the instant application are met by claims 38-42 of U.S. Patent 12,732,947 (e.g., copending application 19/083,014).
Claim 44 of the instant application is met by claim 43 of U.S. Patent 12,732,947 (e.g., copending application 19/083,014).
Claims 45 of the instant application is met by claim 45 of U.S. Patent 12,732,947 (e.g., copending application 19/083,014).
This is a provisional nonstatutory double patenting rejection because the patentably indistinct claims have not in fact been patented.
Claim Rejections - 35 USC § 102
In the event the determination of the status of the application as subject to AIA 35 U.S.C. 102 and 103 (or as subject to pre-AIA 35 U.S.C. 102 and 103) is incorrect, any correction of the statutory basis (i.e., changing from AIA to pre-AIA ) for the rejection will not be considered a new ground of rejection if the prior art relied upon, and the rationale supporting the rejection, would be the same under either status.
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.
3. Claims 28, 30-32, 35, 37-38 and 43 are rejected under 35 U.S.C. 102(a)(2) as being anticipated by Manolakos et al (2025/0159645).
Regarding claim 28. Manolakos teaches a terminal device for communication, comprising at least one processor; and at least one memory including computer program code; wherein the at least one memory and the computer program code are configured to, with the at least one processor, cause the terminal device at least to:
receive, from a plurality of supporting terminal devices, information indicative of corresponding sidelink synchronization sources to which each of the plurality of supporting terminal devices is synchronized (abstract, 0005-0008, 0027 – Sidelink based positioning of a UE … sidelink UEs are selected based on their synchronization references (e.g., source). The network may provide SL positioning assistance (0058-0059). The determining the position of the UE may be done at the network and/or at the UE (0062, 0065-0069, 0071, 0080). The corresponding sidelink synchronization sources may be identified by their Sidelink Synchronization Signal (SLSS) ID(s) which are mapped/associated to gNB/eNB(s) (0081-0083, 0107-0109)); and
obtain, a position of the terminal device, which is based on the indicated information of the corresponding sidelink synchronization sources (abstract, 0005-0008, 0027 – Sidelink based positioning of a UE … sidelink UEs are selected based on their synchronization references (e.g., source). The network may provide SL positioning assistance (0058-0059). The determining the position of the UE may be done at the network and/or at the UE (0062, 0065-0069, 0071, 0080). The corresponding sidelink synchronization sources may be identified by their Sidelink Synchronization Signal (SLSS) ID(s) which are mapped/associated to gNB/eNB(s) (0081-0083, 0107-0109)).
Regarding claim 37. Manolakos teaches a terminal device for
communication, comprising at least one processor; and at least one memory
including computer program code; wherein the at least one memory and the computer program code are configured to, with the at least one processor, cause
the terminal device at least to:
indicate, to a target terminal device of a sidelink synchronization source to
which the terminal device is synchronized (abstract, 0005-0008, 0027 - Sidelink
based positioning of a UE sidelink UEs are selected based on their synchronization references (e.g., source). The network may provide SL positioning assistance (0058-0059). The determining the position of the UE may be done at the network and/or at the UE (0062, 0065-0069, 0071, 0080). The corresponding sidelink synchronization sources may be identified by their Sidelink Synchronization Signal (SLSS) ID(s) which
are mapped/associated to gNB/eNB(s) (0081-0083, 0107-0109)); and
transmit, to the target terminal device, a sidelink position reference signal
to enable a determination of a position of the target terminal device, which is
based on the sidelink position reference signal and the sidelink synchronization
source (abstract, 0005-0008, 0027 - Sidelink based positioning of a UE sidelink UEs are selected based on their synchronization references (e.g., source). The network may provide SL positioning assistance (0058-0059). The determining the position of the UE may be done at the network and/or at the UE (0062, 0065-0069, 0071, 0080). The corresponding sidelink synchronization sources may be identified by their Sidelink Synchronization Signal (SLSS) ID(s) which are mapped/associated to gNB/eNB(s) (0081-0083, 0107-0109)).
Regarding claim 43. Manolakos teaches a location management entity for communication, comprising at least one processor; and at least one memory including computer program code; wherein the at least one memory and the computer program code are configured to, with the at least one processor, cause the terminal device at least two:
receive, from a plurality of supporting terminal devices, information indicative of corresponding sidelink synchronization sources to which each of the plurality of supporting terminal devices is synchronized (abstract, 0005-0008, 0027 – Sidelink based positioning of a UE … sidelink UEs are selected based on their synchronization references (e.g., source). The network may provide SL positioning assistance (0058-0059). The determining the position of the UE may be done at the network and/or at the UE (0062, 0065-0069, 0071, 0080). The corresponding sidelink synchronization sources may be identified by their Sidelink Synchronization Signal (SLSS) ID(s) which are mapped/associated to gNB/eNB(s) (0081-0083, 0107-0109)); and
support positioning determination of a target terminal device using the indicated information (abstract, 0005-0008, 0027 – Sidelink based positioning of a UE … sidelink UEs are selected based on their synchronization references (e.g., source). The network may provide SL positioning assistance (0058-0059). The determining the position of the UE may be done at the network and/or at the UE (0062, 0065-0069, 0071, 0080). The corresponding sidelink synchronization sources may be identified by their Sidelink Synchronization Signal (SLSS) ID(s) which are mapped/associated to gNB/eNB(s) (0081-0083, 0107-0109)).
Regarding claims 30 and 38. Manolakos teaches wherein the receiving of the information is responsive to a request by the terminal device, for the corresponding sidelink synchronization sources to which each of the plurality of supporting terminal devices is synchronized (0092 – the target UE may detect multiple sidelink UEs that are available for sidelink positioning, e.g., in a discover process, 0100 – a discovered synchronization positioning cluster, 0105-0106 – discovery phase, 0134 – discovery message).
Regarding claim 31. Manolakos teaches perform respective measurements, on one or more sidelink position reference signals from the plurality of supporting terminal devices (abstract – perform SL positioning measurements, 0027 – sidelink positioning measurements, 0095 – RSTD measurements from sidelink UEs, 0101 – RSTD for sidelink, 0114 – RSTD for sidelink, 0118-0119 – RSTD based positioning methods, 0124 – perform sidelink positioning methods, such as RSTD based, 0127 – sidelink positioning method, such as RSTD, 0139 – sidelink positioning method, such as RSTD measurements).
Regarding claim 32. Manolakos teaches wherein the measurements are sidelink reference signal time difference (SL RSTD) measurements (abstract – perform SL positioning measurements, 0027 – sidelink positioning measurements, 0095 – RSTD measurements from sidelink UEs, 0101 – RSTD for sidelink, 0114 – RSTD for sidelink, 0118-0119 – RSTD based positioning methods, 0124 – perform sidelink positioning methods, such as RSTD based, 0127 – sidelink positioning method, such as RSTD, 0139 – sidelink positioning method, such as RSTD measurements).
Regarding claim 35. Manolakos teaches wherein the terminal device is further configured to perform one or more of: transmit to a network entity, a measurement report comprising the measurements by the terminal device; or transmit to the network entity, an indication indicative of the corresponding sidelink synchronization sources to which each of the plurality of supporting terminal devices is synchronized (0004, 0065 – 0066).
Claim Rejections - 35 USC § 103
In the event the determination of the status of the application as subject to AIA 35 U.S.C. 102 and 103 (or as subject to pre-AIA 35 U.S.C. 102 and 103) is incorrect, any correction of the statutory basis (i.e., changing from AIA to pre-AIA ) for the rejection will not be considered a new ground of rejection if the prior art relied upon, and the rationale supporting the rejection, would be the same under either status.
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.
4. Claims 29 and 33-34 are rejected under 35 U.S.C. 103 as being unpatentable over Manolakos et al (2025/0159645) in view of Tang et al (2021/0051613) or Dutta et al (2023/0362846).
Regarding claim 29. Manolakos teaches wherein the position of the terminal device is determined based on synchronization (abstract, 0005-0008, 0027 – Sidelink based positioning of a UE … sidelink UEs are selected based on their synchronization references (e.g., source). The network may provide SL positioning assistance (0058-0059). The determining the position of the UE may be done at the network and/or at the UE (0062, 0065-0069, 0071, 0080). The corresponding sidelink synchronization sources may be identified by their Sidelink Synchronization Signal (SLSS) ID(s) which are mapped/associated to gNB/eNB(s) (0081-0083, 0107-0109)).
Manolakos does not teach offsets.
Tang teaches UEs cannot communicate with one another over SL when they are not synchronized. According to some embodiments of the disclosure, the UEs can receive from a Base Station a signaling indicating the timing offset between SL synchronization timings for the UEs and a global navigation satellite system (GNSS). The UEs can then adjust their SL synchronization timings based on the timing offset (0015, 0027-0028).
Dutta teaches the UE receives, from a network entity (e.g., base station, eNB,
NodeB, gNB - 0057, 0090, 0095, 0123-0124, 0126, 0132, 0147-0148, 0151) time offset synchronization regarding one or more synchronization signal resources for ONE
or MORE UEs (0004, 0079, 0151). Accordingly, the UE using the first RAT may account for sidelink synchronization signals of the first RAT and second RAT, and may thereby reduce or eliminate interference, among other advantages.
It would have been obvious for one of ordinary skill in the art before the effective filing date to modify Manolakos to provide sidelink synchronization offsets to the UEs as taught by Tang or Dutta in order to enable the UEs to adjust their sidelink synchronization timings based on timing offsets which enables the UEs to communicate over sidelinks that are synchronized.
Regarding claim 33. Manolakos teaches receive, from a network entity, the synchronization (abstract, 0005-0008, 0027 – Sidelink based positioning of a UE … sidelink UEs are selected based on their synchronization references (e.g., source). The network may provide SL positioning assistance (0058-0059). The determining the position of the UE may be done at the network and/or at the UE (0062, 0065-0069, 0071, 0080). The corresponding sidelink synchronization sources may be identified by their Sidelink Synchronization Signal (SLSS) ID(s) which are mapped/associated to gNB/eNB(s) (0081-0083, 0107-0109)); and
determine the position of the terminal device based on the measurements and the synchronization (abstract, 0005-0008, 0027 – Sidelink based positioning of a UE … sidelink UEs are selected based on their synchronization references (e.g., source). The network may provide SL positioning assistance (0058-0059). The determining the position of the UE may be done at the network and/or at the UE (0062, 0065-0069, 0071, 0080). The corresponding sidelink synchronization sources may be identified by their Sidelink Synchronization Signal (SLSS) ID(s) which are mapped/associated to gNB/eNB(s) (0081-0083, 0107-0109)).
Manolakos does not teach synchronization offsets.
Tang teaches UEs cannot communicate with one another over SL when they are not synchronized. According to some embodiments of the disclosure, the UEs can receive from a Base Station a signaling indicating the timing offset between SL synchronization timings for the UEs and a global navigation satellite system (GNSS). The UEs can then adjust their SL synchronization timings based on the timing offset (0015, 0027-0028).
Dutta teaches the UE receives, from a network entity (e.g., base station, eNB,
NodeB, gNB - 0057, 0090, 0095, 0123-0124, 0126, 0132, 0147-0148, 0151) time offset synchronization regarding one or more synchronization signal resources for ONE
or MORE UEs (0004, 0079, 0151). Accordingly, the UE using the first RAT may account for sidelink synchronization signals of the first RAT and second RAT, and may thereby reduce or eliminate interference, among other advantages.
It would have been obvious for one of ordinary skill in the art before the effective filing date to modify Manolakos to provide sidelink synchronization offsets to the UEs as taught by Tang or Dutta in order to enable the UEs to adjust their sidelink synchronization timings based on timing offsets which enables the UEs to communicate over sidelinks that are synchronized.
Regarding claim 34. Manolakos does not teach wherein the terminal device is further configured to: correct, the measurements using the synchronization offsets among the plurality of supporting terminal devices; and determine the position of the terminal device using the corrected measurements.
Tang teaches UEs cannot communicate with one another over SL when they are not synchronized. According to some embodiments of the disclosure, the UEs can receive from a Base Station a signaling indicating the timing offset between SL synchronization timings for the UEs and a global navigation satellite system (GNSS). The UEs can then adjust (e.g., correct) their SL synchronization timings based on the timing offset (0015, 0027-0028).
Dutta teaches the UE receives, from a network entity (e.g., base station, eNB,
NodeB, gNB - 0057, 0090, 0095, 0123-0124, 0126, 0132, 0147-0148, 0151) time offset synchronization regarding one or more synchronization signal resources for ONE
or MORE UEs (0004, 0079, 0151). Accordingly, the UE using the first RAT may account for sidelink synchronization signals of the first RAT and second RAT, and may thereby reduce or eliminate interference, among other advantages.
It would have been obvious for one of ordinary skill in the art before the effective filing date to modify Manolakos to provide sidelink synchronization offsets to the UEs as taught by Tang or Dutta in order to enable the UEs to adjust (e.g., correct) their sidelink synchronization timings based on timing offsets which enables the UEs to communicate over sidelinks that are synchronized.
5. Claims 36, 40, 44 and 45 are rejected under 35 U.S.C. 103 as being unpatentable over Manolakos in view of Hoang et al (2024/0056997).
Regarding claim 36. Manolakos does not teach wherein one or more of the following is applicable: the measurement report indicates the corresponding sidelink synchronization sources to which each of the plurality of supporting terminal devices is synchronized; or the measurements by the terminal device are corrected by the network entity using the synchronization offsets among the plurality of supporting terminal devices, and the position of the terminal device is determined by the network entity using the corrected measurements.
Hoang teaches using synchronization offsets between UEs and the synchronization offsets may be provided to the network and/or other UEs to provide for more accurate location estimations (0278, 0281, 0288-0289, 0354, 0356-0357, 0359, 0362, 0360 – These procedures may be motivated to help the UE or network to calculate the position of the UE accurately). Each UE may broadcast its error information, zone ID, speed, direction, supported positioning methods (0163, 0172, 0198, 0262).
It would have been obvious for one of ordinary skill in the art before the effective filing date to modify the teaching of Manolakos to incorporate Side Link Synchronization Offsets as taught by Hoang in order to help the UE or network to calculate the position of the UE more accurately.
Regarding claim 40. Manolakos does not teach provide, to a location management entity, a synchronization offset between the terminal device and another terminal device, wherein the synchronization offset is used to determine the position of the target terminal device.
Hoang teaches using synchronization offsets between UEs and the synchronization offsets may be provided to the network and/or other UEs to provide for more accurate location estimations (0278, 0281, 0288 - UE reports synchronization offsets to network, 0289, 0354, 0356-0357, 0359, 0362, 0360 - These procedures may be motivated to help the UE or network to calculate the position of the UE accurately). Each UE may broadcast its error information, zone ID, speed, direction, supported positioning methods (0163, 0172, 0198, 0262).
It would have been obvious for one of ordinary skill in the art before the effective filing date to modify the teaching of Manolakos to incorporate Side Link Synchronization Offsets as taught by Hoang in order to help the UE or network to calculate the position of the UE more accurately.
Regarding claim 44. Manolakos does not teach acquire synchronization offsets among the plurality of supporting terminal devices.
Hoang teaches using synchronization offsets between UEs and the synchronization offsets may be provided to the network and/or other UEs to provide for more accurate location estimations (0278, 0281, 0288-0289, 0354, 0356-0357, 0359, 0362, 0360 – These procedures may be motivated to help the UE or network to calculate the position of the UE accurately). Each UE may broadcast its error information, zone ID, speed, direction, supported positioning methods (0163, 0172, 0198, 0262).
It would have been obvious for one of ordinary skill in the art before the effective filing date to modify the teaching of Manolakos to incorporate Side Link Synchronization Offsets as taught by Hoang in order to help the UE or network to calculate the position of the UE more accurately.
Regarding claim 45. Manolakos does not teach, wherein the location management entity is further configured to perform one or both of: determine a position of the target terminal device based on the synchronization offsets among the plurality of supporting terminal devices; or
provide, to the target terminal device, the synchronization offsets among the plurality of supporting terminal devices, wherein the synchronization offsets among the plurality of supporting terminal devices are used to determine a position of the target terminal device.
Hoang teaches using synchronization offsets between UEs and the synchronization offsets may be provided to the network and/or other UEs to provide for more accurate location estimations (0278, 0281, 0288-0289, 0354, 0356-0357, 0359, 0362, 0360 – These procedures may be motivated to help the UE or network to calculate the position of the UE accurately). Each UE may broadcast its error information, zone ID, speed, direction, supported positioning methods (0163, 0172, 0198, 0262).
It would have been obvious for one of ordinary skill in the art before the effective filing date to modify the teaching of Manolakos to incorporate Side Link Synchronization Offsets as taught by Hoang in order to help the UE or network to calculate the position of the UE more accurately.
6. Claims 39 and 41 are rejected under 35 U.S.C. 103 as being unpatentable over Manolakos in view of Thomas et al (2025/0203572).
Regarding claim 39. Manolakos does not teach transmit to a location management entity, a mapping between the SL synchronization source and a network device serving the terminal device.
Thomas teaches SL positioning (0002) and sends SL report information to the network wherein the report includes RTS offset information between a pair of anchor nodes, which provides time synchronization information between the nodes to enable SL TDOA measurement (0120, Table 5 – SL-PRS-ID-Ref used to uniquely identify a SL-PRS resource and is associated to the reference SL TRP or anchor device, Anchor-device-ID – specifies anchor device ID).
It would have been obvious for one of ordinary skill in the art before the effective filing date to modify Manolakos to report RTD offset in conjunction with anchor device ID information as taught by Thomas which enables the network to correct positioning estimations.
Regarding claim 41. Manolakos does not teach transmit to a location management entity, a mapping between an identifier of the SL synchronization source and a network device serving the terminal device.
Thomas teaches SL positioning (0002) and sends SL report information to the network wherein the report includes RTS offset information between a pair of anchor nodes, which provides time synchronization information between the nodes to enable SL TDOA measurement (0120, Table 5 – SL-PRS-ID-Ref used to uniquely identify a SL-PRS resource and is associated to the reference SL TRP or anchor device, Anchor-device-ID – specifies anchor device ID).
It would have been obvious for one of ordinary skill in the art before the effective filing date to modify Manolakos to report RTD offset in conjunction with anchor device ID information as taught by Thomas which enables the network to correct positioning estimations.
7. Claim 42 is rejected under 35 U.S.C. 103 as being unpatentable over Manolakos in view of Hoang further in view of Thomas et al (2025/0203572).
Regarding claim 42. Manolakos in view of Hoang do not teach wherein the mapping is used to determine by the location management entity the position of the target terminal device.
Thomas teaches SL positioning (0002) and sends SL report information to the network wherein the report includes RTS offset information between a pair of anchor nodes, which provides time synchronization information between the nodes to enable SL TDOA measurement (0120, Table 5 – SL-PRS-ID-Ref used to uniquely identify a SL-PRS resource and is associated to the reference SL TRP or anchor device, Anchor-device-ID – specifies anchor device ID).
It would have been obvious for one of ordinary skill in the art before the effective filing date to modify Manolakos in view of Hoang to report RTD offset in conjunction with anchor device ID information as taught by Thomas which enables the network to correct positioning estimations.
Conclusion
8. The prior art made of record and not relied upon is considered pertinent to applicant's disclosure.
---(2025/0024305) Manolakos et al teaches the UE itself determines and pre-configures the SL coordination group(s) that it will use (0164).
10. Any inquiry concerning this communication or earlier communications from the examiner should be directed to BARRY W TAYLOR whose telephone number is (571)272-7509. The examiner can normally be reached Monday-Thursday: 7-5.
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, Matthew Anderson can be reached at 571-272-4177. 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.
/BARRY W TAYLOR/Primary Examiner, Art Unit 2646
Prosecution Insights