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 .
Information Disclosure Statement
The information disclosure statement submitted on 05/06/2025, have been considered by the examiner and made of record in the application file.
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)(1) the claimed invention was patented, described in a printed publication, or in public use, on sale, or otherwise available to the public before the effective filing date of the claimed invention.
(a)(2) the claimed invention was described in a patent issued under section 151, or in an application for patent published or deemed published under section 122(b), in which the patent or application, as the case may be, names another inventor and was effectively filed before the effective filing date of the claimed invention.
Claims 1-4, 6, 9-14, 16, 19-23, 25 and 28-30 are rejected under U.S.C. 102(a)(1) as being anticipated by 3GPP (3GPP TSG-RAN2#123 R2-2308908, hereinafter 3GPP).
Consider Claim 1, 3GPP discloses a first network device for wireless communications, the first network device comprising:
at least one memory; and (1. Introduction Line 3-5, Specify reporting signaling and procedures to facilitate support of SL positioning in all coverage scenarios and for PC5-only and joint PC5-Uu scenarios [RAN2, RAN3]: Specify the protocol and procedures for SL positioning between UEs and LMF).
at least one processor coupled to the at least one memory and configured to: (1. Introduction Line 3-5, Specify reporting signaling and procedures to facilitate support of SL positioning in all coverage scenarios and for PC5-only and joint PC5-Uu scenarios [RAN2, RAN3]: Specify the protocol and procedures for SL positioning between UEs and LMF( uses a processor and contains memory)).
receive, from a plurality of second network devices, respective anchor selection criteria for each second network device of the plurality of second network devices; (Section 2.2 observation 1, if the Anchor UE’s location is too unstable or temporarily unavailable, then the role of the Anchor UE may change. In such case the Anchor UE should not announce itself (anymore) as a “Located UE” but may still announce itself as a “Reference UE”. The role may possibly even change during a sidelink positioning procedure, and hence a mechanism to indicate a role change may be needed).
determine, based on the respective anchor selection criteria for each second network device of the plurality of second network devices, a network device from the plurality of second network devices as an anchor device for determining a position of the first network device; and (section 2.2 observation 2, RAN2 should define criteria or allow the network to configure criteria by which it can be determined whether or not the Anchor UE’s location is sufficiently stable and/or sufficiently accurate to be used for SL positioning. Such criteria can be used by Anchor UE to decide whether or not it should announce itself as a ““Located UE” or as a “SL Reference UE’ (as per the SA2 definitions), rather than leaving this only to implementation).
determine the position of the first network device based on the anchor device. (Section 2.3, an Anchor UE can indicate its role to be a Located UE during discovery, this may not provide sufficient information for the Target UE or SL Positioning Server UE to determine whether or not it can rely on the location of the Anchor UE to be sufficiently accurate and stable solely based on this role indication during discovery. RAN2 to agree that the UE role information is indicated first in the discovery SLPP metafield, and any other field(if any) indicated parameter(s) essential to the indicated UE role).
Consider Claim 2, 3GPP discloses the first network device of claim 1, wherein the respective anchor selection criteria for each second network device of the plurality of second network devices comprises at least one of a respective type of user equipment (UE) of each second network device, one or more sources for a respective position of each second network device, an age of the respective position for each second network device, a validity duration for the respective position of each second network device, an accuracy duration for the respective position for each second network device, or assistance data validity for the respective position for each second network device. (Section 2.2, accuracy of Anchor UE’s absolute location is stable and sufficiently accurate may often not hold in practice. Whereas legacy base stations typically have a fixed position, an Anchor UE is likely to be mobile. This leads to several issues that need to be resolved, the Anchor UE may move quite fast or shake too much, leading to an unstable location. the anchor UE is mobile, then measurements of its absolute location will age. If out-of-date or ‘stale’ anchor UE absolute locations are used to calculate a target UE location, the result will be inaccurate).
Consider Claim 3, 3GPP discloses the first network device of claim 2, wherein the respective anchor selection criteria for each second network device of the plurality of second network devices further comprises at least one of the respective position of each second network device or a source diversity for the respective position for each second network device. (Section 2.2 observation 2, RAN2 should define criteria or allow the network to configure criteria by which it can be determined whether or not the Anchor UE’s location is sufficiently stable and/or sufficiently accurate to be used for SL positioning. Such criteria can be used by Anchor UE to decide whether or not it should announce itself as a ““Located UE” or as a “SL Reference UE’ (as per the SA2 definitions), rather than leaving this only to implementation).
Consider Claim 4, 3GPP discloses the first network device of claim 2, wherein the one or more sources for the respective position of each second network device includes at least one of one or more Global Navigation Satellite System (GNSS) sources, one or more geodetic survey sources, one or more sidelink (SL) signal sources, one or more wireless network (Uu) signal sources, one or more Uu positioning sources, or one or more WiFi positioning sources. (Section 2.2, no requirements exist on how accurate the location of an Anchor UE needs to be. In particular, if the Anchor UE does not support GNSS and depends on Uu based positioning, the Anchor UE’s location and hence also the calculated location of the Target UE may deviate quite a bit from its actual location. This may lead to undesired side effects given that various sidelink positioning use case require accurate location estimations).
Consider Claim 6, 3GPP discloses the first network device of claim 2, wherein the respective type of UE is a stationary UE or a mobile UE. (Section 2.2 observation 2, an Anchor UE’s role of being Located UE is not fixed and may change over time (possibly even during a sidelink positioning procedure). Whether or not the Anchor UE is stationary or moving, which may be determined by means of a set of thresholds).
Consider Claim 9, 3GPP discloses the first network device of claim 1, wherein, to determine the position of the first network device based on the anchor device, the at least one processor is configured to:
receive, by the first network device from the anchor device, one or more sidelink (SL) signals; and (section 2.3 proposal 3, an Anchor UE may move around, the timing of obtaining the position of the Anchor UE during the procedure can impact the position calculation of a Target UE. Hence, RAN2 should also define mechanisms to compensate for the time difference between obtaining/determining the location of an Anchor UE and performing the SL positioning measurements and calculations).
determine, by the first network device, the position of the first network device based on measurements of the one or more SL signals. (Section 2.3 proposal 3, possible mechanisms include scheduling Ranging/Sidelink positioning and the positioning of the Anchor UE(s) at the same time or providing a validity time for which the Anchor UE’s location is expected to remain valid).
Consider Claim 10, 3GPP discloses the first network device of claim 1, wherein the at least one processor is configured to receive the respective anchor selection criteria via sidelink position protocol (SLPP) signaling. (Section 2.3, the purpose of such auxiliary information would be to allow the Target UE to make a first-pass down-selection of Anchor UEs that do not meet the necessary positioning requirements.it may be necessary to poll the Anchor to retain an up-to-date understanding of the Anchor’s status. Alternatively, we propose to add to SLPP/RSPP the ability to notify or express to the Target UE or LMF or SL positioning server UE about a change to this status).
Consider Claim 11, 3GPP discloses a method for wireless communications at a first network device, the method comprising:
receiving, by the first network device from a plurality of second network devices, respective anchor selection criteria for each second network device of the plurality of second network devices; (Section 2.2 observation 1, if the Anchor UE’s location is too unstable or temporarily unavailable, then the role of the Anchor UE may change. In such case the Anchor UE should not announce itself (anymore) as a “Located UE” but may still announce itself as a “Reference UE”. The role may possibly even change during a sidelink positioning procedure, and hence a mechanism to indicate a role change may be needed).
determining, by the first network device based on the respective anchor selection criteria for each second network device of the plurality of second network devices, a network device from the plurality of second network devices as an anchor device for determining a position of the first network device; and (section 2.2 observation 2, RAN2 should define criteria or allow the network to configure criteria by which it can be determined whether or not the Anchor UE’s location is sufficiently stable and/or sufficiently accurate to be used for SL positioning. Such criteria can be used by Anchor UE to decide whether or not it should announce itself as a ““Located UE” or as a “SL Reference UE’ (as per the SA2 definitions), rather than leaving this only to implementation).
determining the position of the first network device based on the anchor device. (Section 2.3, an Anchor UE can indicate its role to be a Located UE during discovery, this may not provide sufficient information for the Target UE or SL Positioning Server UE to determine whether or not it can rely on the location of the Anchor UE to be sufficiently accurate and stable solely based on this role indication during discovery. RAN2 to agree that the UE role information is indicated first in the discovery SLPP metafield, and any other field(if any) indicated parameter(s) essential to the indicated UE role).
Consider Claim 12, 3GPP discloses the method of claim 11, wherein the respective anchor selection criteria for each second network device of the plurality of second network devices comprises at least one of a respective type of user equipment (UE) of each second network device, one or more sources for a respective position of each second network device, an age of the respective position for each second network device, a validity duration for the respective position of each second network device, an accuracy duration for the respective position for each second network device, or assistance data validity for the respective position for each second network device. (Section 2.2, accuracy of Anchor UE’s absolute location is stable and sufficiently accurate may often not hold in practice. Whereas legacy base stations typically have a fixed position, an Anchor UE is likely to be mobile. This leads to several issues that need to be resolved, the Anchor UE may move quite fast or shake too much, leading to an unstable location. the anchor UE is mobile, then measurements of its absolute location will age. If out-of-date or ‘stale’ anchor UE absolute locations are used to calculate a target UE location, the result will be inaccurate).
Consider Claim 13, 3GPP discloses the method of claim 12, wherein the respective anchor selection criteria for each second network device of the plurality of second network devices further comprises at least one of the respective position of each second network device or a source diversity for the respective position for each second network device. (Section 2.2 observation 2, RAN2 should define criteria or allow the network to configure criteria by which it can be determined whether or not the Anchor UE’s location is sufficiently stable and/or sufficiently accurate to be used for SL positioning. Such criteria can be used by Anchor UE to decide whether or not it should announce itself as a ““Located UE” or as a “SL Reference UE’ (as per the SA2 definitions), rather than leaving this only to implementation).
Consider Claim 14, 3GPP discloses the method of claim 12, wherein the one or more sources for the respective position of each second network device includes at least one of one or more Global Navigation Satellite System (GNSS) sources, one or more geodetic survey sources, one or more sidelink (SL) signal sources, one or more wireless network (Uu) signal sources, one or more Uu positioning sources, or one or more WiFi positioning sources. (Section 2.2, no requirements exist on how accurate the location of an Anchor UE needs to be. In particular, if the Anchor UE does not support GNSS and depends on Uu based positioning, the Anchor UE’s location and hence also the calculated location of the Target UE may deviate quite a bit from its actual location. This may lead to undesired side effects given that various sidelink positioning use case require accurate location estimations).
Consider Claim 16, 3GPP discloses the method of claim 12, wherein the respective type of UE is a stationary UE or a mobile UE. (Section 2.2 observation 2, an Anchor UE’s role of being Located UE is not fixed and may change over time (possibly even during a sidelink positioning procedure). Whether or not the Anchor UE is stationary or moving, which may be determined by means of a set of thresholds).
Consider Claim 19, 3GPP discloses the method of claim 11, wherein determining the position of the first network device based on the anchor device comprises:
receiving, by the first network device from the anchor device, one or more sidelink (SL) signals; and (section 2.3 proposal 3, an Anchor UE may move around, the timing of obtaining the position of the Anchor UE during the procedure can impact the position calculation of a Target UE. Hence, RAN2 should also define mechanisms to compensate for the time difference between obtaining/determining the location of an Anchor UE and performing the SL positioning measurements and calculations).
determining, by the first network device, the position of the first network device based on measurements of the one or more SL signals. (Section 2.3 proposal 3Possible mechanisms include scheduling Ranging/Sidelink positioning and the positioning of the Anchor UE(s) at the same time or providing a validity time for which the Anchor UE’s location is expected to remain valid).
Consider Claim 20, 3GPP discloses the method of claim 11, wherein the respective anchor selection criteria is received via sidelink position protocol (SLPP) signaling. (Section 2.3, the purpose of such auxiliary information would be to allow the Target UE to make a first-pass down-selection of Anchor UEs that do not meet the necessary positioning requirements.it may be necessary to poll the Anchor to retain an up-to-date understanding of the Anchor’s status. Alternatively, we propose to add to SLPP/RSPP the ability to notify or express to the Target UE or LMF or SL positioning server UE about a change to this status).
Consider Claim 21, 3GPP discloses a first network device for wireless communications, the first network device comprising:
at least one memory; and (1. Introduction Line 3-5, Specify reporting signaling and procedures to facilitate support of SL positioning in all coverage scenarios and for PC5-only and joint PC5-Uu scenarios [RAN2, RAN3]: Specify the protocol and procedures for SL positioning between UEs and LMF(contains memory)).
at least one processor coupled to the at least one memory and configured to: (1. Introduction Line 3-5, Specify reporting signaling and procedures to facilitate support of SL positioning in all coverage scenarios and for PC5-only and joint PC5-Uu scenarios [RAN2, RAN3]: Specify the protocol and procedures for SL positioning between UEs and LMF( uses a processor and contains memory)).
determine anchor selection criteria for the first network device, wherein the anchor selection criteria for the first network device comprises at least one of a type of user equipment (UE) of the first network device, one or more sources for a position of the first network device, an age of the position for the first network device, a validity duration for the position of the first network device, an accuracy duration for the position of the first network device, or assistance data validity for the position of the first network device; and (Section 2.2, accuracy of Anchor UE’s absolute location is stable and sufficiently accurate may often not hold in practice. Whereas legacy base stations typically have a fixed position, an Anchor UE is likely to be mobile. This leads to several issues that need to be resolved, the Anchor UE may move quite fast or shake too much, leading to an unstable location. the anchor UE is mobile, then measurements of its absolute location will age. If out-of-date or ‘stale’ anchor UE absolute locations are used to calculate a target UE location, the result will be inaccurate).
output the anchor selection criteria for transmission to a second network device. . (Section 2.2 observation 2, RAN2 should define criteria or allow the network to configure criteria by which it can be determined whether or not the Anchor UE’s location is sufficiently stable and/or sufficiently accurate to be used for SL positioning. Such criteria can be used by Anchor UE to decide whether or not it should announce itself as a ““Located UE” or as a “SL Reference UE’ (as per the SA2 definitions)).
Consider Claim 22, 3GPP discloses the first network device of claim 21, wherein the anchor selection criteria for the first network device further comprises at least one of the respective position of the first network device or a source diversity for the position of the first network device. (Section 2.2, accuracy of Anchor UE’s absolute location is stable and sufficiently accurate may often not hold in practice. Whereas legacy base stations typically have a fixed position, an Anchor UE is likely to be mobile. This leads to several issues that need to be resolved, the Anchor UE may move quite fast or shake too much, leading to an unstable location. the anchor UE is mobile, then measurements of its absolute location will age. If out-of-date or ‘stale’ anchor UE absolute locations are used to calculate a target UE location, the result will be inaccurate).
Consider Claim 23, 3GPP discloses the first network device of claim 21, wherein the one or more sources for the position of the first network device includes at least one of one or more Global Navigation Satellite System (GNSS) sources, one or more geodetic survey sources, one or more sidelink (SL) signal sources, one or more wireless network (Uu) signal sources, one or more Uu positioning sources, or one or more WiFi positioning sources. (Section 2.2, no requirements exist on how accurate the location of an Anchor UE needs to be. In particular, if the Anchor UE does not support GNSS and depends on Uu based positioning, the Anchor UE’s location and hence also the calculated location of the Target UE may deviate quite a bit from its actual location. This may lead to undesired side effects given that various sidelink positioning use case require accurate location estimations).
Consider Claim 25, 3GPP discloses the first network device of claim 21, wherein the type of UE is a stationary UE or a mobile UE. (Section 2.2 observation 2, an Anchor UE’s role of being Located UE is not fixed and may change over time (possibly even during a sidelink positioning procedure). Whether or not the Anchor UE is stationary or moving, which may be determined by means of a set of thresholds).
Consider Claim 28, 3GPP discloses the first network device of claim 21, wherein the at least one processor is configured to output the anchor selection criteria for transmission via sidelink position protocol (SLPP) signaling. (Section 2.3, the purpose of such auxiliary information would be to allow the Target UE to make a first-pass down-selection of Anchor UEs that do not meet the necessary positioning requirements.it may be necessary to poll the Anchor to retain an up-to-date understanding of the Anchor’s status. Alternatively, we propose to add to SLPP/RSPP the ability to notify or express to the Target UE or LMF or SL positioning server UE about a change to this status).
Consider Claim 29, 3GPP discloses a method for wireless communications at a first network device, the method comprising:
determining anchor selection criteria for the first network device, wherein the anchor selection criteria for the first network device comprises at least one of a type of user equipment (UE) of the first network device, one or more sources for a position of the first network device, an age of the position for the first network device, a validity duration for the position of the first network device, an accuracy duration for the position of the first network device, or assistance data validity for the position of the first network device; and (Section 2.2, accuracy of Anchor UE’s absolute location is stable and sufficiently accurate may often not hold in practice. Whereas legacy base stations typically have a fixed position, an Anchor UE is likely to be mobile. This leads to several issues that need to be resolved, the Anchor UE may move quite fast or shake too much, leading to an unstable location. the anchor UE is mobile, then measurements of its absolute location will age. If out-of-date or ‘stale’ anchor UE absolute locations are used to calculate a target UE location, the result will be inaccurate).
transmitting the anchor selection criteria to a second network device. (Section 2.2 observation 2, RAN2 should define criteria or allow the network to configure criteria by which it can be determined whether or not the Anchor UE’s location is sufficiently stable and/or sufficiently accurate to be used for SL positioning. Such criteria can be used by Anchor UE to decide whether or not it should announce itself as a ““Located UE” or as a “SL Reference UE’ (as per the SA2 definitions)).
Consider Claim 30, 3GPP discloses the method of claim 29, wherein the anchor selection criteria for the first network device further comprises at least one of the respective position of the first network device or a source diversity for the position of the first network device. (Section 2.2, accuracy of Anchor UE’s absolute location is stable and sufficiently accurate may often not hold in practice. Whereas legacy base stations typically have a fixed position, an Anchor UE is likely to be mobile. This leads to several issues that need to be resolved, the Anchor UE may move quite fast or shake too much, leading to an unstable location. the anchor UE is mobile, then measurements of its absolute location will age. If out-of-date or ‘stale’ anchor UE absolute locations are used to calculate a target UE location, the result will be inaccurate).
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.
The factual inquiries for establishing a background for determining obviousness under 35 U.S.C. 103 are summarized as follows:
1. Determining the scope and contents of the prior art.
2. Ascertaining the differences between the prior art and the claims at issue.
3. Resolving the level of ordinary skill in the pertinent art.
4. Considering objective evidence present in the application indicating obviousness or non-obviousness.
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.
Claims 5, 7-8, 15, 17-18, 24 and 26-27 are rejected under the U.S.C. 103 as being unpatentable over 3GPP (3GPP TSG-RAN2#123 R2-2308908, hereinafter 3GPP) in view of WU et al. (US 20230061043 A1, hereinafter WU).
Consider Claim 5, 3GPP discloses the claim invention but he fails to teach the first network device of claim 4, wherein each GNSS source of the one or more GNSS sources is one of a Global Positioning System (GPS) satellite, a Global Navigation Satellite System (GLONASS) satellite, a Galileo satellite, a BeiDou Navigation Satellite System (BDS) satellite, a Quazi-Zenith Satellite System (QZSS) satellite, or a Navigation with Indian Constellation (NavIC) satellite.
However, WU teaches (paragraph 0189, GNSS systems include, but are not limited to, the US-based Global Positioning System (GPS), the Russia-based Global Navigation Satellite System (GLONASS), the China-based BeiDou Navigation Satellite System (BDS), and the Europe-based Galileo GNSS).
Consider Claim 7, 3GPP discloses the claim invention but he fails to teach The first network device of claim 6, wherein the stationary UE is a roadside unit (RSU).
However, WU teaches (paragraph 0159, the anchor device category associated with each of the plurality of sidelink positioning anchor devices includes at least one of a stationary road side unit (RSU) category, a vehicle on-board unit (OBU) category, and a pedestrian UE category).
Consider Claim 8, 3GPP discloses the claim invention but he fails to teach the first network device of claim 6, wherein the mobile UE is a vehicle or a mobile phone.
However, WU teaches (paragraph 0054, a UE may be any wireless communication device (e.g., a mobile phone, router, tablet computer, laptop computer, tracking device. A UE may be mobile or may (e.g., at certain times) be stationary, and may communicate with a radio access network (RAN)).
Consider Claim 15, 3GPP discloses the method of claim 14, wherein each GNSS source of the one or more GNSS sources is one of a Global Positioning System (GPS) satellite, a Global Navigation Satellite System (GLONASS) satellite, a Galileo satellite, a BeiDou Navigation Satellite System (BDS) satellite, a Quazi-Zenith Satellite System (QZSS) satellite, or a Navigation with Indian Constellation (NavIC) satellite.
However, WU teaches (paragraph 0189, GNSS systems include, but are not limited to, the US-based Global Positioning System (GPS), the Russia-based Global Navigation Satellite System (GLONASS), the China-based BeiDou Navigation Satellite System (BDS), and the Europe-based Galileo GNSS).
Consider Claim 17, 3GPP discloses the claim invention but he fails to teach the method of claim 16, wherein the stationary UE is a roadside unit (RSU).
However, WU teaches (paragraph 0159, the anchor device category associated with each of the plurality of sidelink positioning anchor devices includes at least one of a stationary road side unit (RSU) category, a vehicle on-board unit (OBU) category, and a pedestrian UE category).
Consider Claim 18, 3GPP discloses the claim invention but he fails to teach the method of claim 16, wherein the mobile UE is a vehicle or a mobile phone.
However, WU teaches (paragraph 0054, a UE may be any wireless communication device (e.g., a mobile phone, router, tablet computer, laptop computer, tracking device. A UE may be mobile or may (e.g., at certain times) be stationary, and may communicate with a radio access network (RAN)).
Consider Claim 24, 3GPP discloses the claim invention but he fails to teach the first network device of claim 23, wherein each GNSS source of the one or more GNSS sources is one of a Global Positioning System (GPS) satellite, a Global Navigation Satellite System (GLONASS) satellite, a Galileo satellite, a BeiDou Navigation Satellite System (BDS) satellite, a Quazi-Zenith Satellite System (QZSS) satellite, or a Navigation with Indian Constellation (NavIC) satellite.
However, WU teaches (paragraph 0189, GNSS systems include, but are not limited to, the US-based Global Positioning System (GPS), the Russia-based Global Navigation Satellite System (GLONASS), the China-based BeiDou Navigation Satellite System (BDS), and the Europe-based Galileo GNSS).
Consider Claim 26, 3GPP discloses the claim invention but he fails to teach the first network device of claim 25, wherein the stationary UE is a roadside unit (RSU).
However, WU teaches (paragraph 0159, the anchor device category associated with each of the plurality of sidelink positioning anchor devices includes at least one of a stationary road side unit (RSU) category, a vehicle on-board unit (OBU) category, and a pedestrian UE category).
Consider Claim 27, 3GPP discloses the first network device of claim 25, wherein the mobile UE is a vehicle or a mobile phone.
However, WU teaches (paragraph 0054, a UE may be any wireless communication device (e.g., a mobile phone, router, tablet computer, laptop computer, tracking device. A UE may be mobile or may (e.g., at certain times) be stationary, and may communicate with a radio access network (RAN)).
Therefore, it would have been obvious before the effective filing date of the claimed invention to a person having ordinary skill in the art to which said subject matter pertains, to modify Claims 5, 7-8, 15, 17-18, 24 and 26-27 by incorporating the 3GPP TSG-RAN2#123 R2-2308908 discussion “On the selection of Anchor UEs for Sidelink Positioning Source” for use in anchor UE selection to include the wireless communication device associated with one or more sidelink positioning anchor devices from the plurality of sidelink positioning anchor devices(i.e. GPS, GNSS, RSU & SLPP). The motivation to do so would be to develop an expanded and improved NR positioning specify reporting signaling and procedures to facilitate support of sidelink (SL) positioning in all coverage scenarios. While increasing wireless communications systems that are deployed to provide various telecommunication services, including telephony, video, data, messaging, broadcasts, among others. Wireless communications systems have developed through various generations for performing sidelink (SL) positioning anchor user equipment (UE) selection criteria.
Conclusion
Any inquiry concerning this communication or earlier communications from the examiner should be directed to MICHELE CAMILLE DOUGLAS whose telephone number is (571)270-0458. The examiner can normally be reached Monday - Friday 6:30 am - 5:00 pm.
Examiner interviews are available via telephone, in-person, and video conferencing using a USPTO supplied web-based collaboration tool. To schedule an interview, applicant is encouraged to use the USPTO Automated Interview Request (AIR) at http://www.uspto.gov/interviewpractice.
If attempts to reach the examiner by telephone are unsuccessful, the examiner’s supervisor, 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.
/MICHELE C DOUGLAS/Examiner, Art Unit 2646
/MATTHEW D. ANDERSON/Supervisory Patent Examiner, Art Unit 2646