DETAILED ACTION
The present application, filed on or after March 16, 2013, is being examined under the first inventor to file provisions of the AIA .
The preliminary amendment filed 6/20/2024 was received.
PRIOR ART
The following references are prior art:
1. Appl. No.: 18/135,459 (Tenny) is prior art under 35 U.S.C. 102(a)(2) since it published as US 2023/0254810 A1, names another inventor (Nathan Edward Tenny of MEDIATEK Singapore Pte. Ltd.), and was effectively filed by Jun. 11, 2021 before Dec. 21, 2021 the effective filing dated of the claimed invention.
2. Appl. No.: 18/685,344 (Barbu) is prior art under 35 U.S.C. 102(a)(2) since it published as US 2024/0397467A1, names another inventor (Oana-Elena BARBU of Nokia Technologies Oy), and was effectively filed by Sep. 13, 2021 before Dec. 21, 2021 the effective filing dated of the claimed invention.
CLAIM REJECTIONS — 35 U.S.C. 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:
35 U.S.C. 102 Conditions for patentability; novelty.
(a) NOVELTY; PRIOR ART.—A person shall be entitled to a patent unless—
(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-5, 7, 9, & 16-18
Claims 1-5, 7, 9, and 16-18 are rejected under 35 U.S.C. 102(a)(2) as being anticipated by Tenny (US 2023/0254810 A1) for the reasons given below.
Claim 1
With respect to claim 1, Tenny disclosed:
A first user equipment (UE) for wireless communication, comprising: at least one memory; and at least one processor coupled with the at least one memory ([0025] UE 120 comprises memory 121, a processor 123… Processor 123 processes received baseband signals and invokes different functional modules and circuits to perform features in wireless device 120. Memory 121 stores program instructions and data 122 to control the operations of mobile device… The functional modules, when executed by processors 123 via program instructions 122 contained in memory 121, interwork with each other to allow the network device to perform positioning for the target UE.)
and configured to cause the first UE to: transmit first assistance information to a network, wherein the first assistance information includes UE information associated with at least one second UE ([FIG. 4] Step. 3 Assistance data request. [0024] In accordance with one novel aspect, methods for a distinguished UE, e.g., leader UE 102, to function as a "server UE" for positioning a target UE over sidelink interface are proposed. This allows a reduction in the necessary sidelink signalling to support positioning as well as control of the distribution of information about the various peer UEs. Alternatively, the distinguished UE in the group may have no special role as a leader or coordinator, but supports positioning functions as a server UE, e.g., server UE 103. This distinguished server UE 103 may, for example, have access to information about all the peer UEs in the group, such as the configurations and estimated locations of the peer UEs. [0026] In the proposed positioning operations, there is a need to transport signalling messages for positioning purposes between UEs over the sidelink interface. For instance, UEs must be given configurations of reference signals, instructed to take measurements, provided with assistance data, and so on. [0033] UE1 in FIG. 4 is the UE to be positioned, functioning as a "target device" in the parlance of the LPP specification. UE2 in FIG. 4 includes the basic functionality of a positioning server; specifically, UE2 has the ability to collect configuration information from other peer UEs, compose corresponding assistance data, and distribute the assistance data to a target device (such as UE1). UE2 may have additional positioning server functionality such as the ability to compute a position estimate from measurements. UE3 and UE4 are additional UEs that may, for instance, transmit reference signals that can be measured by UE1 as part of the positioning process. [0034] In steps 1a and 1b of FIG. 4, UE3 and UE4, respectively, inform UE2 of their configurations. The provided information may include, for example, configurations of positioning reference signals, known or estimated locations of UE3 and UE4 themselves, and any other information that needs to be provided to the server and/or the target device for a positioning operation… In step 2, UE2 formulates positioning assistance data based on the information provided by UE3 and UE4; the assistance data may be in a format defined by a protocol, such as LPP, for example. [0035] In step 3, UE1 requests assistance data from UE2. This step may be prompted by a request for a positioning operation at UE1 itself (for example, an application layer operating in UE1 may indicate a need for a location estimate). The Examiner finds that the assistance data request in Tenny reads on the claimed first assistance information; the server UE of Tenny reads on the claimed network; and the peer UEs of Tenny read on the claimed at least one second UE),
and wherein the at least one second UE helps the first UE to acquire its position ([0023] When the group of UEs communicate via a sidelink interface, there is an opportunity to use the sidelink signals to estimate the locations of a to-be-positioned target UE. [0031] UE4 may initiate RTT measurements towards UE1, UE2, and UE3, and use the measured RTTs as estimates of the ranges from UE4 to each of the peer UEs. Based on the known locations of UE1, UE2, and UE3, and the ranges based on the measured RTT1, RTT2, and RTT3, UE4 may then compute (by a process of trilateration, for example) an estimate of its own location. [0033] UE3 and UE4 are additional UEs that may, for instance, transmit reference signals that can be measured by UE1 as part of the positioning process.);
and receive first sidelink (SL) positioning related information from the network ([0032] FIG. 4 shows a message flow for a to-be-positioned target UE to receive assistance data from a server UE to facilitate the measurements on the PCS interface. The assistance data may contain, for example, information on the configuration of reference signals being transmitted by other peer UEs on the PCS interface, the known locations of other peer UEs whose signals the target UE may measure, and so on. [0034] UE2 formulates positioning assistance data based on the information provided by UE3 and UE4; the assistance data may be in a format defined by a protocol, such as LPP, for example. [0035] In step 4, UE2 delivers assistance data to UE1 in response to the request from step 3. The assistance data delivered in step 4 may be identical to, a subset of, or a superset of the assistance data formulated in step 2. The server UE may determine what assistance data should be provided, taking into account any information it has about the environment of UE1, such as a coarse location estimate, measurement reports indicating the radio environment in relation to other UEs, and so on. The delivery of assistance data may be in a format defined by a protocol, such as LPP, for example. The Examiner finds that the assistance data delivery in Tenny reads on the claimed SL positioning related information).
Claim 2
With respect to claim 2, Tenny disclosed:
The first UE of Claim 1 (see rejection above),
wherein the at least one second UE is determined by the first UE, and the UE information includes at least one of: an identification of each of the at least one second UE; a number of the at least one second UE; a status of each of the at least one second UE; serving cell information of each of the at least one second UE; UE capability associated with SL positioning of each of the at least one second UE; or a candidate UE list including an index of each of the at least one second UE ([0028] UEs in a group are presumed to have some capability for positioning based on sidelink signals, e.g., the ability to take measurements of positioning reference signals (PRSs) that may be transmitted on the sidelink. [0031] FIG. 3 shows an example in which UE1, UE2, UE3, and UE4 are in communication via a PC5 interface… UE4 is assumed to know the locations of UE1, UE2, and UE3; this information may be available by various means, such as transmissions from the involved UEs themselves, transmissions from a positioning server that manages location information of the involved UEs, and so on. [0032] FIG. 4 shows a message flow for a to-be-positioned target UE to receive assistance data from a server UE to facilitate the measurements on the PCS interface. The assistance data may contain, for example, information on the configuration of reference signals being transmitted by other peer UEs on the PC5 interface, the known locations of other peer UEs whose signals the target UE may measure, and so on. ).
Claim 3
With respect to claim 3, Tenny disclosed:
The first UE of Claim 1 (see rejection above),
wherein the at least one second UE is determined by the network based on the UE information, and the UE information includes at least one of: a minimum number of second UEs helping the first UE to acquire its position; or a preferred UE type of each of the second UEs helping the first UE to acquire its position ([0024] In accordance with one novel aspect, methods for a distinguished UE, e.g., leader UE 102, to function as "server UE" for positioning a target UE over sidelink interface are proposed. This allows a reduction in the necessary sidelink signalling to support positioning as well as control of the distribution of information about the various peer UEs. Alternatively, the distinguished UE in the group may have no special role as a leader or coordinator, but supports positioning functions as a server UE, e.g., server UE 103. [0029] In addition, some or all of the UEs may have the ability to determine their location by other means than sidelink measurements, such as global navigation satellite system (GNSS) measurements and/or measurements of signals of a cellular network… thus, a UE in the group that cannot determine its own location directly may be able to determine its location relative to other UEs in the group whose locations are known, and thus infer a location estimate for itself. [0030] UE1 and the leader UE have visibility to a GNSS constellation 201, allowing them to use ordinary GNSS techniques to determine their own locations; but UE2's visibility to the GNSS constellation is obstructed, meaning that UE2 must rely on other methods to determine its location. [0034] In steps 1a and 1b of FIG. 4, UE3 and UE4, respectively, inform UE2 of their configurations. The provided information may include, for example, configurations of positioning reference signals, known or estimated locations of UE3 and UE4 themselves, and any other information that needs to be provided to the server and/or the target device for a positioning operation… In step 2, UE2 formulates positioning assistance data based on the information provided by UE3 and UE4. In addition, the Examiner finds that Tenny implicitly disclosed that a minimum number of second UEs helping the first UE to acquire its position is 1, as shown in FIG. 2 of Tenny).
Claim 4
With respect to claim 4, Tenny disclosed:
The first UE of Claim 1 (see rejection above),
wherein the at least one processor is further configured to cause the first UE to transmit the first assistance information to the network in response to at least one of the following conditions: measurement quality for SL positioning meets a threshold; or current SL positioning configuration cannot satisfy quality of service (QoS) requirements ([0029] In addition, some or all of the UEs may have the ability to determine their location by other means than sidelink measurements, such as global navigation satellite system (GNSS) measurements and/or measurements of signals of a cellular network. At any given moment, a particular UE-even if equipped with the ability to determine its own location-may or may not be able to make location measurements, and thus may or may not know its estimated location in practice. For example, a UE that depends on GNSS for positioning may not be able to receive signals from GNSS satellites while the UE is in a tunnel or otherwise has an obstructed view of the sky. Thus, a UE in the group that cannot determine its own location directly may be able to determine its location relative to other UEs in the group whose locations are known, and thus infer a location estimate for itself. [0035] In step 1 of FIG. 5, an event triggers UE1 to perform a positioning operation. The triggering event may be an indication from a user, an indication from an application layer operating in UE1, a message from another UE (for example, from UE2), a message from a cellular network element, and so on.).
Claim 5
With respect to claim 5, Tenny disclosed:
The first UE of Claim 1 (see rejection above),
wherein the first SL positioning related information includes at least one mapping, and wherein each mapping is: a mapping between a SL positioning configuration and a corresponding sidelink destination ID; a mapping between a SL positioning configuration and a corresponding second UE of the at least one second UE; or a mapping between a SL positioning configuration and a corresponding SL positioning capability index ([0032] FIG. 4 shows a message flow for a to-be-positioned target UE to receive assistance data from a server UE to facilitate the measurements on the PCS interface. The assistance data may contain, for example, information on the configuration of reference signals being transmitted by other peer UEs on the PCS interface, the known locations of other peer UEs whose signals the target UE may measure, and so on. [0037] In step 3, UE2 provides assistance data to UE1 (similar to step 4 of FIG. 4)… A static or semi-static configuration of assistance data ( such as through OAM) may be appropriate in case the UEs to be measured are substantially stationary (for example, UE-type RSUs). A dynamic configuration of assistance data (such as through reports from individual UEs) may be appropriate in case the UEs to be measured are mobile (for example, vehicular UEs ). If assistance data are configured through reports from individual UEs, the reports may be in a format defined by a protocol, such as NRPPa, for example. In steps 4a, 4b, and 4c, UE2, UE3, and UE4, respectively, transmit reference signals on a sidelink interface.).
Claim 7
With respect to claim 7, Tenny disclosed:
The first UE of Claim 1 (see rejection above),
wherein a state of the first UE is changed from an in-coverage state to an out-of-coverage state, and the at least one processor is further configured to cause the first UE to perform at least one of the following: keeping using the first SL positioning related information until the first SL positioning related information becomes invalid; acquiring second SL positioning related information in the out-of-coverage state and keeping using the first SL positioning related information in the in-coverage state until the second SL positioning related information is available, wherein the second SL positioning related information is acquired by pre-configuration information; or using default SL positioning related information during a time period from the first SL positioning related information becomes invalid to the second SL positioning related information is available, wherein the default SL positioning related information is pre-defined ([0005] However, a group of UEs communicating via sidelink may be in cellular network coverage, out of cellular network coverage, or in a so-called "partial-coverage" scenario in which some UEs are in network coverage while others are out. Particularly in the out-of-coverage and partial-coverage scenarios, existing methods of positioning based on communication with a server in the cellular network may not be feasible. [0023] FIG. 1 shows an example of a group of UEs with an identified leader UE, e.g., leader UE 102, in a partial-coverage scenario in which some of the UEs of the group are in coverage of a cellular network while others are out of coverage. [0029] At any given moment, a particular UE-even if equipped with the ability to determine its own location-may or may not be able to make location measurements, and thus may or may not know its estimated location in practice. For example, a UE that depends on GNSS for positioning may not be able to receive signals from GNSS satellites while the UE is in a tunnel or otherwise has an obstructed view of the sky. Thus, a UE in the group that cannot determine its own location directly may be able to determine its location relative to other UEs in the group whose locations are known, and thus infer a location estimate for itself. [0036] In step 1 of FIG. 5, an event triggers UE1 to perform a positioning operation. The triggering event may be an indication from a user, an indication from an application layer operating in UE1, a message from another UE (for example, from UE2), a message from a cellular network element, and so on. The triggering event may identify UE2 as an appropriate device to use as a server for the requested positioning operation. The Examiner finds that in Tenny the assistance data would keep being used until another triggering event rendered it invalid, reading on the claimed “keeping using the first SL positioning related information until the first SL positioning related information becomes invalid”).
Claim 9
With respect to claim 9, Tenny disclosed:
The first UE of Claim 1 (see rejection above),
wherein a state of the first UE is changed from an out-of-coverage state to an in-coverage state, and the at least one processor is further configured to cause the first UE to: report third SL positioning related information to the network, wherein the third SL positioning related information comprises at least one of: UE information associated with at least one fourth UE, wherein the at least one fourth UE helps the first UE to acquire its position in the out-of-coverage state; SL positioning configuration associated with each of the at least one fourth UE; third assistance information (([0005] However, a group of UEs communicating via sidelink may be in cellular network coverage, out of cellular network coverage, or in a so-called "partial-coverage" scenario in which some UEs are in network coverage while others are out. Particularly in the out-of-coverage and partial-coverage scenarios, existing methods of positioning based on communication with a server in the cellular network may not be feasible. [0023] FIG. 1 shows an example of a group of UEs with an identified leader UE, e.g., leader UE 102, in a partial-coverage scenario in which some of the UEs of the group are in coverage of a cellular network while others are out of coverage. [0029] At any given moment, a particular UE-even if equipped with the ability to determine its own location-may or may not be able to make location measurements, and thus may or may not know its estimated location in practice. For example, a UE that depends on GNSS for positioning may not be able to receive signals from GNSS satellites while the UE is in a tunnel or otherwise has an obstructed view of the sky. Thus, a UE in the group that cannot determine its own location directly may be able to determine its location relative to other UEs in the group whose locations are known, and thus infer a location estimate for itself. [0036] In step 1 of FIG. 5, an event triggers UE1 to perform a positioning operation. The triggering event may be an indication from a user, an indication from an application layer operating in UE1, a message from another UE (for example, from UE2), a message from a cellular network element, and so on. The triggering event may identify UE2 as an appropriate device to use as a server for the requested positioning operation. [0039] FIG. 6 shows a variation on the positioning procedure of FIG. 5. For example, the positioning operation may be triggered at UE2 rather than at UE1, potentially in response to a request from some external entity ( e.g., a client in a cellular network that requires the location of UE1). In such a case, changes in the message flow are foreseeable. For example, steps 1 and 2 in FIG. 6 may be replaced by the arrival of a request from an external entity at UE2, prompting UE2 to request positioning measurements from UE1; steps 3 to 8 in FIG. 6 are the same as steps 2 to 7 in FIG. 5; and step 9 in FIG. 6 is the delivery of the location estimate to the external entity that requested it).
Claim 16
Claim 16 recites limitations similar to claim 1 and is rejected by similar reasoning.
Claim 17
Claim 17 recites limitations similar to claim 2 and is rejected by similar reasoning.
Claim 18
Claim 18 recites limitations similar to claim 3 and is rejected by similar reasoning.
CLAIMS 12, 13, 19 & 20
Claims 12, 13, 19, and 20 are rejected under 35 U.S.C. 102(a)(2) as being anticipated by Barbu (US 2024/0397467 A1) for the reasons given below.
Claim 12
With respect to claim 12, Barbu disclosed:
A second user equipment (UE) for wireless communication, comprising: at least one memory; and at least one processor coupled with the at least one memory ([0104] FIG. 6 illustrates an example of an apparatus 600 configured to practice one or more example embodiments. The apparatus 600 may comprise at least one processor 602. The at least one processor 602 may comprise, for example, one or more of various processing devices or processor circuitry. [0105] The apparatus 600 may further comprise at least one memory 604. The at least one memory 604 may be configured to store, for example, computer program code or the like. [0107] When the apparatus 600 is configured to implement some functionality, some component and/or components of the apparatus 600, for example, the at least one processor 602 and/or the at least one memory 604, may be configured to implement this functionality. Furthermore, when the at least one processor 602 is configured to implement some functionality, this functionality may be implemented using the program code 606 comprised, for example, in the at least one memory 604. [0108] The functionality described herein may be performed, at least in part, by one or more computer program product components such as software components.)
and configured to cause the second UE to: receive sidelink (SL) positioning configuration information from a first UE ([0061] FIG. 2A illustrates a target user device for a locally assisted positioning procedure according to an example embodiment. [0062] The user devices 202, 204 are herein called as "anchor user devices", and the anchor user device is a user device whose position information is used to determine a position for the target user device 206. An anchor user device may be a user device that has satellite positioning capabilities. [0063] a paging message may be triggered which in tum will make the target user device 206 to initiate a positioning procedure, i.e. a locally assisted positioning procedure. [0069] At 216 the target user device 206 may be configured to send a local positioning aid request (for example, a side-link LPP-LP aid request) indicating a need for a locally assisted positioning procedure to one or more anchor user devices for the locally assisted positioning procedure. The request asks nearby user devices to join the assisted positioning procedure and thus to become anchor user devices for the target user device 206.);
and transmit an indication indicating whether the SL positioning configuration information is rejected or accepted by the second UE ([0077] At 218 and 220, the anchor user devices 204, 202 are configured to review the SL LPP-LP aid request and accept it when possible. In an example embodiment, the anchor user devices 202, 204 may transmit to the target user device 206 a local positioning aid response in response to the local positioning aid request. The local positioning aid response may indicate that the anchor user device 202, 204 has accepted the local positioning aid request. [0078] At 222 the anchor user device 204 may be configured to transmit to the target user device 206 a local positioning aid response, for example, in the form of a SL LPP-LP aid response. The local positioning aid response 222 may comprise at least one of a rejection indication to the local positioning aid request, an acknowledgement to the local positioning aid request, location data associated with the anchor user device 204, and an indication that the location data associated with the anchor user device 204 is to be transmitted to the location management function.).
Claim 13
With respect to claim 13, Tenny disclosed:
The second UE of Claim 12 (see rejection above),
wherein the at least one processor is further configured to cause the second UE to transmit the SL positioning configuration information to the network when the second UE is in-coverage of the network and determines to use the received SL positioning configuration information ([0062] The location management function 102 may refer to an entity that receives measurements and assistance information from a next generation radio access network (NG-RAN) and a mobile device, for example, user equipment (UE). [0077] At 218 and 220, the anchor user devices 204, 202 are configured to review the SL LPP-LP aid request and accept it when possible. In an example embodiment, the anchor user devices 202, 204 may transmit to the target user device 206 a local positioning aid response in response to the local positioning aid request. [0090] In the example illustrated in FIG. 2C, the anchor user device 202 does not know its location. Due to this, at 240 the anchor user device 202 is configured to trigger LPP positioning with a message to the LMF 102, for example, LPP report in response to LPP-LP, to enable the [location management function] LMF to obtain its location, for example, by an NR-based procedure. The purpose of this message is to indicate to the LMF 102 that the anchor user device 202 is a nearby device for the target user device 206.).
Claim 19
Claim 19 recites limitations similar to claim 12 and is rejected by similar reasoning.
Claim 20
Claim 20 recites limitations similar to claim 13 and is rejected by similar reasoning.
CLAIM REJECTIONS — 35 U.S.C. 103
The following is a quotation of 35 U.S.C. 103 which forms the basis for all obviousness rejections set forth in this Office action:
35 U.S.C. 103 Conditions for patentability; non-obvious subject matter.
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 nonobviousness.
CLAIM 6
Claim 6 is rejected under 35 U.S.C. 103 as being unpatentable over Tenny in view of Barbu.
Claim 6
With respect to claim 6, Tenny disclosed:
The first UE of Claim 1 (see rejection above).
Tenny did not explicitly disclose: wherein the at least one processor is further configured to cause the first UE to transmit SL positioning configuration information to a second UE of the at least second UE and receive an indication indicating whether the SL positioning configuration information is rejected or accepted by the second UE, wherein the SL positioning configuration information is generated based on the first SL positioning related information and includes a SL positioning configuration or an index associated with the SL positioning configuration.
With respect to claim 6, Barbu taught:
wherein the at least one processor is further configured to cause the first UE to transmit SL positioning configuration information to a second UE of the at least second UE and receive an indication indicating whether the SL positioning configuration information is rejected or accepted by the second UE, wherein the SL positioning configuration information is generated based on the first SL positioning related information and includes a SL positioning configuration or an index associated with the SL positioning configuration ([0061] FIG. 2A illustrates a target user device for a locally assisted positioning procedure according to an example embodiment. [0062] The user devices 202, 204 are herein called as "anchor user devices", and the anchor user device is a user device whose position information is used to determine a position for the target user device 206. An anchor user device may be a user device that has satellite positioning capabilities. [0063] a paging message may be triggered which in tum will make the target user device 206 to initiate a positioning procedure, i.e. a locally assisted positioning procedure. [0069] At 216 the target user device 206 may be configured to send a local positioning aid request (for example, a side-link LPP-LP aid request) indicating a need for a locally assisted positioning procedure to one or more anchor user devices for the locally assisted positioning procedure. The request asks nearby user devices to join the assisted positioning procedure and thus to become anchor user devices for the target user device 206. [0077] At 218 and 220, the anchor user devices 204, 202 are configured to review the SL LPP-LP aid request and accept it when possible. In an example embodiment, the anchor user devices 202, 204 may transmit to the target user device 206 a local positioning aid response in response to the local positioning aid request. The local positioning aid response may indicate that the anchor user device 202, 204 has accepted the local positioning aid request. [0078] At 222 the anchor user device 204 may be configured to transmit to the target user device 206 a local positioning aid response, for example, in the form of a SL LPP-LP aid response. The local positioning aid response 222 may comprise at least one of a rejection indication to the local positioning aid request, an acknowledgement to the local positioning aid request, location data associated with the anchor user device 204, and an indication that the location data associated with the anchor user device 204 is to be transmitted to the location management function.).
The Examiner finds that 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 the claimed invention pertains to modify Tenny’s server-based positioning operation facilitated by a server UE to include Barbu’s SL local positioning aid request and response, thereby reading on claim 6, with the motivation being to leverage sidelink communications to take advantage of nearby devices to aid on the power impaired user device positioning while ensuring that the anchor/peer device has the capability to assist in positioning (see Barbu [0060]-[0062]). The result would be predictable given that both Tenny and Barbu describe similar positioning systems in which a peer/anchor UE assists in position a target UE.
CLAIM 14
Claim 14 is rejected under 35 U.S.C. 103 as being unpatentable over Barbu.
Claim 14
With respect to claim 14, Barbu taught:
The second UE of Claim 12 (see rejection above),
wherein the at least one processor is further configured to cause the second UE operate in the RRC idle/inactive state and transition to the RRC connected state if needed, and to transmit the SL positioning configuration information to the network when the second UE connects to the network ([FIG. 2C] LPP report in response to LPP-LP 240. [0058] It is preferred that such devices operate as much as possible in an idle/inactive state in order to preserve power levels over long periods of time. [0063] If the target user device 206 is in a radio resource control (RRC) idle/inactive state, a paging message may be triggered which in tum will make the target user device 206 to initiate a positioning procedure. [0069] At 216 the target user device 206 may be configured to send a local positioning aid request (for example, a side-link LPP-LP aid request) indicating a need for a locally assisted positioning procedure to one or more anchor user devices for the locally assisted positioning procedure. [0090] In the example illustrated in FIG. 2C, the anchor user device 202 does not know its location. Due to this, at 240 the anchor user device 202 is configured to trigger LPP positioning with a message to the LMF 102, for example, LPP report in response to LPP-LP, to enable the LMF to obtain its location, for example, by an NR-based procedure. The purpose of this message is to indicate to the LMF 102 that the anchor user device 202 is a nearby device for the target user device 206.).
The Examiner finds that 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 the claimed invention because while Barbu did not explicitly disclose that the second UE transmits the SL positioning configuration “when the second UE connects to the network,” Barbu explicitly teaches and suggests doing so. Specifically, Bardu [0058] suggested that “It is preferred that such devices operate as much as possible in an idle/inactive state in order to preserve power levels over long periods of time.” According to this suggestion, user device of Barbu would be operating in the idle state and would transition to the connect to the network in order to transmit message 240, thereby achieving “the second UE to transmit the SL positioning configuration information to the network when the second UE connects to the network” as recited in claim 14. Use of RRC idle/inactive/connected states is part of the 3GPP standard and is predictable.
OBJECTION TO CLAIMS, ALLOWABLE SUBJECT MATTER
Claims 8, 10, 11, and 15 are objected to as being dependent upon a rejected base claim, but would be allowable if rewritten in independent form including all of the limitations of the base claim and any intervening claims.
PERTINENT PRIOR ART
The prior art made of record and not relied upon is considered pertinent to applicant's disclosure:
1. Appl. No.: 17/995,062 (Gulati) is prior art under 35 U.S.C. 102(a)(2) since it published as US 2023/0125710 A1, names another inventor (Kapil GULATI of QUALCOMM Incorporated), and was effectively filed by May 4, 2020 before Dec. 21, 2021 the effective filing dated of the claimed invention. Gulati [Abstract] disclosed a user equipment (UE) may transmit, to another UE, a positioning request associated with a procedure for determining a position of the UE, wherein the positioning request comprises a first sidelink communication between a first sidelink location management component (S-LMC) of the UE and a second S-LMC of the other UE.
2. Appl. No.: 17/448,660 (Nam) is prior art under 35 U.S.C. 102(a)(2) since it published as US 2023/0092211 A1, names another inventor (Wooseok Nam of Qualcomm Incorporated), and was effectively filed by Sep. 23, 2021 before Dec. 21, 2021 the effective filing dated of the claimed invention. Nam [0087] In aspects, positioning assistance information 374 may include the configuration of the sidelink PRS transmission to be transmitted to target UE 115a from anchor UEs 115b and 115c, and/or configuration of PRS transmissions to be transmitted over the Uu from one or more anchor base stations.
CONCLUSION
Any inquiry concerning this communication or earlier communications from the examiner should be directed to Christopher Davis whose telephone number is 703-756-1832. The examiner can normally be reached Mon-Fri from 11AM to 7PM ET. If attempts to reach the examiner by telephone are unsuccessful, the examiner’s supervisor, Ayaz Sheikh, can be reached at telephone number 571-272-3795. 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 Patent Center. Status information for published applications may be obtained from Patent Center. Status information for unpublished applications is available through Patent Center to authorized users only. Should you have questions about access to the USPTO patent electronic filing system, contact the Electronic Business Center (EBC) at 866-217-9197 (toll-free). Examiner interviews are available via a variety of formats see MPEP § 713.01. To schedule an interview, applicant is encouraged to use the USPTO Automated Interview Request (AIR) Form at https://www.uspto.gov/InterviewPractice.
/Christopher R Davis/
Examiner, Art Unit 2476
Prosecution Insights