DETAILED ACTION
This communication is in response to the claims filed on 08/12/2026.
Application No: 18/708,764
The present application, filed on or after March 16, 2013, is being examined under the first inventor to file provisions of the AIA .
Notice of Pre-AIA or AIA Status
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 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.
Response to Arguments
Applicants’ arguments filed on 08/12/2026 have been fully considered but they are moot in view of the amended claim(s). Applicant has amended all independent claims that has changed the scope of the invention. Hence new ground of rejection(s) applied.
Claim Rejections - 35 USC § 103
The following is a quotation of 35 U. S. C. 103 which forms the basis for all obviousness rejections set forth in this Office action:
A patent for a claimed invention may not be obtained, notwithstanding that the claimed invention is not identically disclosed as set forth in section 102 of this title, 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 set forth in Graham v. John Deere Co., 383 U. S. 1, 148 USPQ 459 (1966), that are applied 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.
Claims 1-10 and 14-23 and 27-30 are rejected under 35 U. S. C. 103 as being unpatentable over KUMAR et al. (US 20200145977 A1) in view of RenBin et al. (US 20220150866 A1).
Regarding claim 1, KUMAR teaches a method for wireless communications ([0003], e.g. FIG. 8 shows a procedure (i.e. a method) which may be used to support UE based position methods using PRS signals formed along specific azimuth and elevation angles across multiple PRS occasions. [0103] the UE 105 may be configured to measure the TOA of the PRS of each specified beam ID for each base station gNB 110-1, 110-2, 110-3, ng-eNB 114 and report the TOA data to the base station. A network node (e.g., gNB 110-1, AMF 154, LMF 152) may be configured to determine a minimum TOA for each cell across different beam IDs),
by a first network entity ( [0110] e.g. Fig. 8 (AMF, 154), At stage 5, the LMF 152 may generate assistance data (AD) that includes scheduling information for the Elevation/Azimuth PRS beamforming across multiple PRS occasions, e.g., using the capabilities provided by the UE 105 at stage 2 (i.e. by a first network entity LMF/AMF)), comprising:
transmitting, to a second network entity, a request for a location report of a user equipment (UE) ([0112], Fig. 8 (gNB, 110-1), e.g. At stage 7, the LMF 152 sends a Request Location Information message to the UE 105 to request location information. The message may include, e.g., the type of location measurements, the desired accuracy, response time, etc. (i.e. transmitting, to a second network entity, gNB / RAN, a request for a location report)), and
receiving, from the second network entity, the location report including height information of the UE ([0113], Fig 8, (gNB, Step 8), e.g. At stage 8, the gNB 110-1 transmits the PRS Elevation/Azimuth beams across multiple PRS occasions. The UE 105 also performs the requested measurements of the PRS Elevation/Azimuth beams across multiple PRS occasions using the AD from stage 6. [0114] At stage 9, the UE 105 provides the location information to the LMF 152. The location information may include, for example, the location measurement for each PRS occasion or differential location measurements (i.e. gNB receives location information provided by the UE via LMF)).
KUMAR teaches Techniques for determining a location of a mobile device, includes determining, on the mobile device, beam identification information for one or more radio beams, transmitting, with the mobile device, the beam identification information to a network node, receiving, at the mobile device, positioning reference signal beam information for one or more positioning reference signals. KUMAR differs from the claimed invention in not specifically and clearly describing wherein
a request for the second network entity to provide a location report of a user equipment (UE); and receiving the location report in response to the request.
However, in the analogous field of endeavor, RenBin teaches wherein
a request for the second network entity to provide a location report of a user equipment (UE) ([0027] An embodiment of the present application provides a positioning method, which is applied to an LMF entity and includes: [0035] sending a positioning capability request message to the terminal (i.e. a request for the second network entity to provide a location report ) when detecting that the terminal is in a Radio Resource Control-CONNECTED (RRC) state); and
receiving the location report in response to the request ([0036] receiving a positioning capability provision message containing a positioning capability supported by the terminal sent by the terminal. [0102] On the basis of the foregoing embodiments and in an embodiment of the present application, after determining the location information of the terminal, the method further includes: [0103], Fig. 5, sending a positioning information provision message containing the location information of the terminal to the LMF entity (i.e. positioning capability request message triggers the mobile device to respond with a position information message (e.g. a position information report, see fig. 5, step 5011. [0104] The UE-based DL-TDOA positioning function of the terminal can be triggered by itself, that is, the terminal actively reports the location information of the terminal determined by itself to the LMF entity. At this time, the terminal can send a positioning information provision message to the LMF entity, and this message carries the location information of the terminal determined by itself according to each RSTD and the beam direction of each beam reference signal) ).
The motivation to combine reference of RenBin within the method of KUMAR before the effective filing date of the invention is that the combined method provides that the new positioning method, a device, a system, a terminal, an LMF entity, and a medium, used to solve the problem of low positioning accuracy of UE-based TDOA. Further, The transmission beam directions of the SSBs are generally different. Similarly, the beam directions of downlink positioning reference signals used to support the UE positioning are also diverse. However, if the UE is unable to search for a downlink positioning reference signal that supports the accurate positioning based on only the measured value RSTD, the antenna position of the cell and other information, the positioning accuracy of the UE-based DL-TDOA is reduced. The Embodiments of the present application provide a positioning method, device, system, terminal, LMF entity and medium, to solve the problem of low positioning accuracy of the UE-based DL-TDOA (See RenBin [ Abstract, 0005]).
Regarding claim 2, KUMAR in view of RenBin teaches all the limitations of claim 1. KUMAR further teaches wherein the second network entity comprises an access network entity ([0060], e.g. The non-roaming communication system 100 comprises a UE 105 and components of a Fifth Generation (5G) network comprising a Next Generation Radio Access Network (NG-RAN) 112, which includes base stations (BSs) sometimes referred to as New Radio (NR) NodeBs or gNBs 110-1, 110-2, 110-3, and a 5G Core Network (5GC) 150 that is in communication with an external client 130 (i.e. second network entity comprises an access network entity gNB/ RAN)), and
wherein the request for the location report is transmitted when the UE is in a connection management (CM) connected state ([0064], e.g. The UE 105 may enter a connected state with a wireless communication network that may include the NG-RAN 112. [0101] The UE 105 may also report the number of simultaneous beams that the UE 105 is capable of supporting across bands/frequency layers. [0101] In an example, intra-frequency measurements may be carried out simultaneously across different cells. The use of multiple simultaneous beams across bands/frequency layer enables the UE 105 to perform multiple PRS measurements simultaneously and thereby reducing the response time (i.e. the UE is in a connected state and transmits measurement report)).
Regarding claim 3, KUMAR in view of RenBin teaches all the limitations of claim 2. KUMAR further teaches wherein the control plane function comprises an access and mobility management function (AMF) ([0172], e.g. Referring to FIG. 18, a diagram illustrating an example of a hardware implementation of an LMF 1800, such as LMF 152 in FIGS. 1B-1C is shown. The LMF 1800 may be, e.g., part of a wireless network such as a 5G Core network (5GC). The LMF 1800 includes, e.g., hardware components such as an external interface 1802, which may be a wired or wireless interface capable of connecting to a GMLC, such as GMLC 155, … and AMF 154 (i.e. LMF connects other network entity via an interface, which is a part of a control plane)).
Regarding claim 4, KUMAR in view of RenBin teaches all the limitations of claim 1. KUMAR further teaches wherein the second network entity comprises a radio access network (RAN) identifiable by a cell identifier (ID) ([0069], Fig. 1B (AMF, RAN), e.g. As an example, NG-RAN 112 may include one or more next generation eNBs (ng-eNBs) 114 which provide LTE wireless access to UE 105 and may connect to entities in 5GC 150 such as AMF 154 (i.e. second network entity comprises RAN cell ID)).
Regarding claim 5, KUMAR in view of RenBin teaches all the limitations of claim 4. KUMAR further teaches wherein the location report further includes the cell ID of the RAN ([0071], Fig. 1B, e.g. The LMF 152 may support positioning of the UE 105 when UE 105 accesses the NG-RAN 112 and may support position procedures/methods such as Assisted GNSS (A-GNSS), Observed Time Difference of Arrival (OTDOA), Real Time Kinematics (RTK), Precise Point Positioning (PPP), Differential GNSS (DGNSS), Enhanced Cell ID (ECID), angle of arrival (AOA), angle of departure (AOD), WLAN positioning, and/or other position methods. [0057] In general, system 100 may comprise multiple cells indicated by 145-k (0≤k≤N.sub.cells, where N.sub.cells is the number of cells) with additional networks 115 (i.e. the location report further includes the cell ID)).
Regarding claim 6, KUMAR in view of RenBin teaches all the limitations of claim 1. KUMAR further teaches wherein the height information of the UE comprises a value for identifying a height of the UE from a list of height intervals ([0067], e.g. An estimate of a location of the UE 105 may be referred to as a location, location estimate, location fix, fix, position, position estimate or position fix, and may be geographic, thus providing location coordinates for the UE 105 (e.g., latitude and longitude) which may include an altitude component (e.g., height above sea level, height above or depth below ground level, floor level or basement level). Alternatively, a location of the UE 105 may be expressed as a civic location (e.g., as a postal address or the designation of some point or small area in a building such as a particular room or floor (i.e. a value for identifying a height of the UE from a list of height intervals).
Regarding claim 7, KUMAR in view of RenBin teaches all the limitations of claim 6. KUMAR further teaches wherein further comprising: receiving an update of the height information when a change of the second network entity occurs ([0051], e.g. Moreover, the PRS schedule may be based on the respective capabilities of multiple UEs that are requesting location estimation. The PRS from multiple base stations, e.g., gNBs, may be scheduled with changing elevation angle in successive occasions. Similarly, another PRS schedule may be used to vary the azimuth of the PRS beam along narrow elevation (i.e. update of the height information when a change of the second network entity occurs)).
Regarding claim 8, KUMAR in view of RenBin teaches all the limitations of claim 6. KUMAR further teaches wherein further comprising: receiving an update of the height information when the height of the UE in the list of height intervals has changed ([0057], e.g. For simplicity, only one UE 105 and location server 152 are shown in FIG. 1A. The elevation (θ) of the UE 105 is illustrated as changing from a first position to a second position indicated with dotted lines. The position of the UE 105, including azimuth and elevation, may be determined using PRS transmissions from the base stations gNBs 110-1, 110-2, 110-3 along specific azimuth and elevation angles (i.e. update of the height information when the height of the UE in the list of height intervals has change)).
Regarding claim 9, KUMAR in view of RenBin teaches all the limitations of claim 1. KUMAR further teaches wherein the height information of the UE comprises a three-dimensional area of interest defined by an index of an area and an index of a height interval ([0067] e.g. An estimate of a location of the UE 105 may be referred to as a location, location estimate, location fix, fix, position, position estimate or position fix, and may be geographic, thus providing location coordinates for the UE 105 (e.g., latitude and longitude) which may include an altitude component (e.g., height above sea level, height above or depth below ground level, floor level or basement level) (i.e. x, y, z axis, three-dimensional area of interest defined by an index)).
Regarding claim 10, KUMAR in view of RenBin teaches all the limitations of claim 1. KUMAR further teaches wherein the index of the area corresponds to a cell identifier of the second network entity ([0099], e.g. The UE 105 may have travelled along a path 105a and may have been in communication with the second base station gNB 110-2 via a third beam 704c. The UE 105 may send a provide capabilities message including the SSB index of the serving cell and the neighbor cells measured and/or observed in the past. For example, the cell IDs and beam IDs associated with the first beam 702a (i.e., current serving cell), and third beam 704c (i.e., a previous serving cell) (i.e. index of the area corresponds to a current and neigh outing cell identifier)).
Regarding claim 14, KUMAR teaches a method for wireless communications ([0003], e.g. FIG. 8 shows a procedure (i.e. a method) which may be used to support UE based position methods using PRS signals formed along specific azimuth and elevation angles across multiple PRS occasions. [0103] the UE 105 may be configured to measure the TOA of the PRS of each specified beam ID for each base station gNB 110-1, 110-2, 110-3, ng-eNB 114 and report the TOA data to the base station. A network node (e.g., gNB 110-1, AMF 154, LMF 152) may be configured to determine a minimum TOA for each cell across different beam IDs),
by a second network entity [0003], e.g. A network node (e.g., gNB 110-1, AMF 154, LMF 152) may be configured to determine a minimum TOA for each cell across different beam IDs (i.e. s second network entity, gNB)), comprising:
receiving, from a first network entity ( [0110] e.g. Fig. 8 (AMF, 154), At stage 5, the LMF 152 may generate assistance data (AD) that includes scheduling information for the Elevation/Azimuth PRS beamforming across multiple PRS occasions, e.g., using the capabilities provided by the UE 105 at stage 2 (i.e. receiving from a first network entity LMF/AMF)),
a request for a location report of a user equipment (UE); and transmitting, to the first network entity, the location report including height information of the UE ([0113], Fig 8, (gNB, Step 8), e.g. At stage 8, the gNB 110-1 transmits the PRS Elevation/Azimuth beams across multiple PRS occasions. The UE 105 also performs the requested measurements of the PRS Elevation/Azimuth beams across multiple PRS occasions using the AD from stage 6. [0114] At stage 9, the UE 105 provides the location information to the LMF 152. The location information may include, for example, the location measurement for each PRS occasion or differential location measurements (i.e. gNB receives location information provided by the UE and transmitted via LMF)).
KUMAR teaches Techniques for determining a location of a mobile device, includes determining, on the mobile device, beam identification information for one or more radio beams, transmitting, with the mobile device, the beam identification information to a network node, receiving, at the mobile device, positioning reference signal beam information for one or more positioning reference signals. KUMAR differs from the claimed invention in not specifically and clearly describing wherein
a request for the second network entity to provide a location report of a user equipment (UE); and transmitting the location report in response to the request.
However, in the analogous field of endeavor, RenBin teaches wherein
a request for the second network entity to provide a location report of a user equipment (UE) ([0027] An embodiment of the present application provides a positioning method, which is applied to an LMF entity and includes: [0035] sending a positioning capability request message to the terminal (i.e. a request for the second network entity to provide a location report ) when detecting that the terminal is in a Radio Resource Control-CONNECTED (RRC) state); and
transmitting the location report in response to the request ([0036] receiving a positioning capability provision message containing a positioning capability supported by the terminal sent by the terminal. [0102] On the basis of the foregoing embodiments and in an embodiment of the present application, after determining the location information of the terminal, the method further includes: [0103], Fig. 5, sending a positioning information provision message containing the location information of the terminal to the LMF entity (i.e. positioning capability request message triggers the mobile device to respond with a position information message (e.g. a position information report, see fig. 5, step 5011. [0104] The UE-based DL-TDOA positioning function of the terminal can be triggered by itself, that is, the terminal actively reports the location information of the terminal determined by itself to the LMF entity. At this time, the terminal can send a positioning information provision message to the LMF entity, and this message carries the location information of the terminal determined by itself according to each RSTD and the beam direction of each beam reference signal) ).
The motivation to combine reference of RenBin within the method of KUMAR before the effective filing date of the invention is that the combined method provides that the new positioning method, a device, a system, a terminal, an LMF entity, and a medium, used to solve the problem of low positioning accuracy of UE-based TDOA. Further, The transmission beam directions of the SSBs are generally different. Similarly, the beam directions of downlink positioning reference signals used to support the UE positioning are also diverse. However, if the UE is unable to search for a downlink positioning reference signal that supports the accurate positioning based on only the measured value RSTD, the antenna position of the cell and other information, the positioning accuracy of the UE-based DL-TDOA is reduced. The Embodiments of the present application provide a positioning method, device, system, terminal, LMF entity and medium, to solve the problem of low positioning accuracy of the UE-based DL-TDOA (See RenBin [ Abstract, 0005]).
Regarding claim 15, KUMAR in view of RenBin teaches all the limitations of claim 14. KUMAR further teaches wherein the first network entity comprises a core network entity having a control plane function ([0172], e.g. Referring to FIG. 18, a diagram illustrating an example of a hardware implementation of an LMF 1800, such as LMF 152 in FIGS. 1B-1C is shown. The LMF 1800 may be, e.g., part of a wireless network such as a 5G Core network (5GC). The LMF 1800 includes, e.g., hardware components such as an external interface 1802, which may be a wired or wireless interface capable of connecting to a GMLC, such as GMLC 155, … and AMF 154 (i.e. LMF connects other network entity via an interface, which is a part of a control plane)),
wherein the second network entity comprises an access network entity ([0060], e.g. The non-roaming communication system 100 comprises a UE 105 and components of a Fifth Generation (5G) network comprising a Next Generation Radio Access Network (NG-RAN) 112, which includes base stations (BSs) sometimes referred to as New Radio (NR) NodeBs or gNBs 110-1, 110-2, 110-3, and a 5G Core Network (5GC) 150 that is in communication with an external client 130 (i.e. second network entity comprises an access network entity gNB/ RAN)), and
wherein the request for the location report is transmitted when the UE is in a connection management (CM) connected state ([0064], e.g. The UE 105 may enter a connected state with a wireless communication network that may include the NG-RAN 112. [0101] The UE 105 may also report the number of simultaneous beams that the UE 105 is capable of supporting across bands/frequency layers. [0101] In an example, intra-frequency measurements may be carried out simultaneously across different cells. The use of multiple simultaneous beams across bands/frequency layer enables the UE 105 to perform multiple PRS measurements simultaneously and thereby reducing the response time (i.e. the UE is in a connected state and transmits measurement report)).
Regarding claim 16, KUMAR in view of RenBin teaches all the limitations of claim 15. KUMAR further teaches wherein the control plane function comprises an access and mobility management function (AMF) ([0172], e.g. Referring to FIG. 18, a diagram illustrating an example of a hardware implementation of an LMF 1800, such as LMF 152 in FIGS. 1B-1C is shown. The LMF 1800 may be, e.g., part of a wireless network such as a 5G Core network (5GC). The LMF 1800 includes, e.g., hardware components such as an external interface 1802, which may be a wired or wireless interface capable of connecting to a GMLC, such as GMLC 155, … and AMF 154 (i.e. LMF connects other network entity via an interface, which is a part of a control plane)).
Regarding claim 17, KUMAR in view of RenBin teaches all the limitations of claim 14. KUMAR further teaches wherein the second network entity comprises a radio access network (RAN) identifiable by a cell identifier (ID) ([0069], Fig. 1B (AMF, RAN), e.g. As an example, NG-RAN 112 may include one or more next generation eNBs (ng-eNBs) 114 which provide LTE wireless access to UE 105 and may connect to entities in 5GC 150 such as AMF 154 (i.e. second network entity comprises RAN cell ID)).
Regarding claim 18, KUMAR in view of RenBin teaches all the limitations of claim 17. KUMAR further teaches wherein the location report further includes the cell ID of the RAN ([0071], Fig. 1B, e.g. The LMF 152 may support positioning of the UE 105 when UE 105 accesses the NG-RAN 112 and may support position procedures/methods such as Assisted GNSS (A-GNSS), Observed Time Difference of Arrival (OTDOA), Real Time Kinematics (RTK), Precise Point Positioning (PPP), Differential GNSS (DGNSS), Enhanced Cell ID (ECID), angle of arrival (AOA), angle of departure (AOD), WLAN positioning, and/or other position methods. [0057] In general, system 100 may comprise multiple cells indicated by 145-k (0≤k≤N.sub.cells, where N.sub.cells is the number of cells) with additional networks 115 (i.e. the location report further includes the cell ID)).
Regarding claim 19, KUMAR in view of RenBin teaches all the limitations of claim 14. KUMAR further teaches wherein the height information of the UE comprises a value for identifying a height of the UE from a list of height intervals ([0067], e.g. An estimate of a location of the UE 105 may be referred to as a location, location estimate, location fix, fix, position, position estimate or position fix, and may be geographic, thus providing location coordinates for the UE 105 (e.g., latitude and longitude) which may include an altitude component (e.g., height above sea level, height above or depth below ground level, floor level or basement level). Alternatively, a location of the UE 105 may be expressed as a civic location (e.g., as a postal address or the designation of some point or small area in a building such as a particular room or floor (i.e. a value for identifying a height of the UE from a list of height intervals).
Regarding claim 20, KUMAR in view of RenBin teaches all the limitations of claim 19. KUMAR further teaches wherein further comprising: transmitting an update of the height information when a change of the second network entity occurs ([0051], e.g. Moreover, the PRS schedule may be based on the respective capabilities of multiple UEs that are requesting location estimation. The PRS from multiple base stations, e.g., gNBs, may be scheduled with changing elevation angle in successive occasions. Similarly, another PRS schedule may be used to vary the azimuth of the PRS beam along narrow elevation (i.e. update of the height information when a change of the second network entity occurs)).
Regarding claim 21, KUMAR in view of RenBin teaches all the limitations of claim 19. KUMAR further teaches wherein further comprising: transmitting an update of the height information when the height of the UE in the list of height intervals has changed ([0057], e.g. For simplicity, only one UE 105 and location server 152 are shown in FIG. 1A. The elevation (θ) of the UE 105 is illustrated as changing from a first position to a second position indicated with dotted lines. The position of the UE 105, including azimuth and elevation, may be determined using PRS transmissions from the base stations gNBs 110-1, 110-2, 110-3 along specific azimuth and elevation angles (i.e. update of the height information when the height of the UE in the list of height intervals has change)).
Regarding claim 22, KUMAR in view of RenBin teaches all the limitations of claim 14. KUMAR further teaches wherein the height information of the UE comprises a three-dimensional area of interest defined by an index of an area and an index of a height interval ([0067] e.g. An estimate of a location of the UE 105 may be referred to as a location, location estimate, location fix, fix, position, position estimate or position fix, and may be geographic, thus providing location coordinates for the UE 105 (e.g., latitude and longitude) which may include an altitude component (e.g., height above sea level, height above or depth below ground level, floor level or basement level) (i.e. x, y, z axis, three-dimensional area of interest defined by an index)).
Regarding claim 23, KUMAR in view of RenBin teaches all the limitations of claim 22. KUMAR further teaches wherein the index of the area corresponds to a cell identifier of the second network entity ([0099], e.g. The UE 105 may have travelled along a path 105a and may have been in communication with the second base station gNB 110-2 via a third beam 704c. The UE 105 may send a provide capabilities message including the SSB index of the serving cell and the neighbor cells measured and/or observed in the past. For example, the cell IDs and beam IDs associated with the first beam 702a (i.e., current serving cell), and third beam 704c (i.e., a previous serving cell) (i.e. index of the area corresponds to a current and neigh outing cell identifier)).
Regarding claim 27, KUMAR teaches a first network entity ( [0110] e.g. Fig. 8 (AMF, 154), At stage 5, the LMF 152 may generate assistance data (AD) that includes scheduling information for the Elevation/Azimuth PRS beamforming across multiple PRS occasions, e.g., using the capabilities provided by the UE 105 at stage 2 (i.e. by a first network entity LMF/AMF)), comprising:
at least one memory; and one or more processors coupled to at least one memory, the one or more processors ([0172], e.g. The LMF 1800 includes, e.g., hardware components such as an external interface 1802, which may be a wired or wireless interface capable of connecting to a GMLC, such as GMLC 155, VGMLC 155V or HGMLC 155H, and AMF 154. The LMF 1800 includes one or more processors 1804 and memory 1810, which may be coupled together with bus 1806. The memory 1810 may contain executable code or software instructions that when executed by the one or more processors 1804 cause the one or more processors 1804 to operate as a special purpose computer programmed to perform the procedures), being configured to:
transmit, to a second network entity, a request for a location report of a user equipment (UE) ([0112], Fig. 8 (gNB, 110-1), e.g. At stage 7, the LMF 152 sends a Request Location Information message to the UE 105 to request location information. The message may include, e.g., the type of location measurements, the desired accuracy, response time, etc. (i.e. transmitting, to a second network entity, gNB / RAN, a request for a location report)), and
receive, from the second network entity, the location report including height information of the UE ([0113], Fig 8, (gNB, Step 8), e.g. At stage 8, the gNB 110-1 transmits the PRS Elevation/Azimuth beams across multiple PRS occasions. The UE 105 also performs the requested measurements of the PRS Elevation/Azimuth beams across multiple PRS occasions using the AD from stage 6. [0114] At stage 9, the UE 105 provides the location information to the LMF 152. The location information may include, for example, the location measurement for each PRS occasion or differential location measurements (i.e. gNB receives location information provided by the UE via LMF)).
KUMAR teaches Techniques for determining a location of a mobile device, includes determining, on the mobile device, beam identification information for one or more radio beams, transmitting, with the mobile device, the beam identification information to a network node, receiving, at the mobile device, positioning reference signal beam information for one or more positioning reference signals. KUMAR differs from the claimed invention in not specifically and clearly describing wherein
a request for the second network entity to provide a location report of a user equipment (UE); and receive the location report in response to the request.
However, in the analogous field of endeavor, RenBin teaches wherein
a request for the second network entity to provide a location report of a user equipment (UE) ([0027] An embodiment of the present application provides a positioning method, which is applied to an LMF entity and includes: [0035] sending a positioning capability request message to the terminal (i.e. a request for the second network entity to provide a location report ) when detecting that the terminal is in a Radio Resource Control-CONNECTED (RRC) state); and
receive the location report in response to the request ([0036] receiving a positioning capability provision message containing a positioning capability supported by the terminal sent by the terminal. [0102] On the basis of the foregoing embodiments and in an embodiment of the present application, after determining the location information of the terminal, the method further includes: [0103], Fig. 5, sending a positioning information provision message containing the location information of the terminal to the LMF entity (i.e. positioning capability request message triggers the mobile device to respond with a position information message (e.g. a position information report, see fig. 5, step 5011. [0104] The UE-based DL-TDOA positioning function of the terminal can be triggered by itself, that is, the terminal actively reports the location information of the terminal determined by itself to the LMF entity. At this time, the terminal can send a positioning information provision message to the LMF entity, and this message carries the location information of the terminal determined by itself according to each RSTD and the beam direction of each beam reference signal) ).
The motivation to combine reference of RenBin within the method of KUMAR before the effective filing date of the invention is that the combined method provides that the new positioning method, a device, a system, a terminal, an LMF entity, and a medium, used to solve the problem of low positioning accuracy of UE-based TDOA. Further, The transmission beam directions of the SSBs are generally different. Similarly, the beam directions of downlink positioning reference signals used to support the UE positioning are also diverse. However, if the UE is unable to search for a downlink positioning reference signal that supports the accurate positioning based on only the measured value RSTD, the antenna position of the cell and other information, the positioning accuracy of the UE-based DL-TDOA is reduced. The Embodiments of the present application provide a positioning method, device, system, terminal, LMF entity and medium, to solve the problem of low positioning accuracy of the UE-based DL-TDOA (See RenBin [ Abstract, 0005]).
Regarding claim 28, KUMAR in view of RenBin teaches all the limitations of claim 27. KUMAR further teaches wherein the first network entity comprises a core network entity having a control plane function ([0172], e.g. Referring to FIG. 18, a diagram illustrating an example of a hardware implementation of an LMF 1800, such as LMF 152 in FIGS. 1B-1C is shown. The LMF 1800 may be, e.g., part of a wireless network such as a 5G Core network (5GC). The LMF 1800 includes, e.g., hardware components such as an external interface 1802, which may be a wired or wireless interface capable of connecting to a GMLC, such as GMLC 155, … and AMF 154 (i.e. LMF connects other network entity via an interface, which is a part of a control plane)),
wherein the second network entity comprises an access network entity ([0060], e.g. The non-roaming communication system 100 comprises a UE 105 and components of a Fifth Generation (5G) network comprising a Next Generation Radio Access Network (NG-RAN) 112, which includes base stations (BSs) sometimes referred to as New Radio (NR) NodeBs or gNBs 110-1, 110-2, 110-3, and a 5G Core Network (5GC) 150 that is in communication with an external client 130 (i.e. second network entity comprises an access network entity gNB/ RAN)), and
wherein the request for the location report is transmitted when the UE is in a connection management (CM) connected state ([0064], e.g. The UE 105 may enter a connected state with a wireless communication network that may include the NG-RAN 112. [0101] The UE 105 may also report the number of simultaneous beams that the UE 105 is capable of supporting across bands/frequency layers. [0101] In an example, intra-frequency measurements may be carried out simultaneously across different cells. The use of multiple simultaneous beams across bands/frequency layer enables the UE 105 to perform multiple PRS measurements simultaneously and thereby reducing the response time (i.e. the UE is in a connected state and transmits measurement report)).
Regarding claim 29, KUMAR in view of RenBin teaches all the limitations of claim 28. KUMAR further teaches wherein the control plane function comprises an access and mobility management function (AMF) ([0172], e.g. Referring to FIG. 18, a diagram illustrating an example of a hardware implementation of an LMF 1800, such as LMF 152 in FIGS. 1B-1C is shown. The LMF 1800 may be, e.g., part of a wireless network such as a 5G Core network (5GC). The LMF 1800 includes, e.g., hardware components such as an external interface 1802, which may be a wired or wireless interface capable of connecting to a GMLC, such as GMLC 155, … and AMF 154 (i.e. LMF connects other network entity via an interface, which is a part of a control plane)).
Regarding claim 30, KUMAR teaches a second network entity [0112], Fig. 8 (gNB, 110-1), e.g. At stage 7, the LMF 152 sends a Request Location Information message to the UE 105 to request location information. The message may include, e.g., the type of location measurements, the desired accuracy, response time, etc. (i.e. transmitting, to a second network entity, gNB / RAN, a request for a location report)), comprising:
at least one memory; and one or more processors coupled to at least one memory, the one or more processors ([0172], e.g. The LMF 1800 includes, e.g., hardware components such as an external interface 1802, which may be a wired or wireless interface capable of connecting to a GMLC, such as GMLC 155, VGMLC 155V or HGMLC 155H, and AMF 154. The LMF 1800 includes one or more processors 1804 and memory 1810, which may be coupled together with bus 1806. The memory 1810 may contain executable code or software instructions that when executed by the one or more processors 1804 cause the one or more processors 1804 to operate as a special purpose computer programmed to perform the procedures), being configured to:
receive, from a first network entity ( [0110] e.g. Fig. 8 (AMF, 154), At stage 5, the LMF 152 may generate assistance data (AD) that includes scheduling information for the Elevation/Azimuth PRS beamforming across multiple PRS occasions, e.g., using the capabilities provided by the UE 105 at stage 2 (i.e. receiving from a first network entity LMF/AMF)),
a request for a location report of a user equipment (UE); and transmit, to the first network entity, the location report including height information of the UE ([0113], Fig 8, (gNB, Step 8), e.g. At stage 8, the gNB 110-1 transmits the PRS Elevation/Azimuth beams across multiple PRS occasions. The UE 105 also performs the requested measurements of the PRS Elevation/Azimuth beams across multiple PRS occasions using the AD from stage 6. [0114] At stage 9, the UE 105 provides the location information to the LMF 152. The location information may include, for example, the location measurement for each PRS occasion or differential location measurements (i.e. gNB receives location information provided by the UE and transmitted via LMF)).
KUMAR teaches Techniques for determining a location of a mobile device, includes determining, on the mobile device, beam identification information for one or more radio beams, transmitting, with the mobile device, the beam identification information to a network node, receiving, at the mobile device, positioning reference signal beam information for one or more positioning reference signals. KUMAR differs from the claimed invention in not specifically and clearly describing wherein
a request for the second network entity to provide a location report of a user equipment (UE); and receiving the location report in response to the request.
However, in the analogous field of endeavor, RenBin teaches wherein
a request for the second network entity to provide a location report of a user equipment (UE) ([0027] An embodiment of the present application provides a positioning method, which is applied to an LMF entity and includes: [0035] sending a positioning capability request message to the terminal (i.e. a request for the second network entity to provide a location report ) when detecting that the terminal is in a Radio Resource Control-CONNECTED (RRC) state); and
transmit the location report in response to the request ([0036] receiving a positioning capability provision message containing a positioning capability supported by the terminal sent by the terminal. [0102] On the basis of the foregoing embodiments and in an embodiment of the present application, after determining the location information of the terminal, the method further includes: [0103], Fig. 5, sending a positioning information provision message containing the location information of the terminal to the LMF entity (i.e. positioning capability request message triggers the mobile device to respond with a position information message (e.g. a position information report, see fig. 5, step 5011. [0104] The UE-based DL-TDOA positioning function of the terminal can be triggered by itself, that is, the terminal actively reports the location information of the terminal determined by itself to the LMF entity. At this time, the terminal can send a positioning information provision message to the LMF entity, and this message carries the location information of the terminal determined by itself according to each RSTD and the beam direction of each beam reference signal) ).
The motivation to combine reference of RenBin within the method of KUMAR before the effective filing date of the invention is that the combined method provides that the new positioning method, a device, a system, a terminal, an LMF entity, and a medium, used to solve the problem of low positioning accuracy of UE-based TDOA. Further, The transmission beam directions of the SSBs are generally different. Similarly, the beam directions of downlink positioning reference signals used to support the UE positioning are also diverse. However, if the UE is unable to search for a downlink positioning reference signal that supports the accurate positioning based on only the measured value RSTD, the antenna position of the cell and other information, the positioning accuracy of the UE-based DL-TDOA is reduced. The Embodiments of the present application provide a positioning method, device, system, terminal, LMF entity and medium, to solve the problem of low positioning accuracy of the UE-based DL-TDOA (See RenBin [ Abstract, 0005]).
Claim Rejections - 35 USC § 103
The following is a quotation of 35 U. S. C. 103 which forms the basis for all obviousness rejections set forth in this Office action:
A patent for a claimed invention may not be obtained, notwithstanding that the claimed invention is not identically disclosed as set forth in section 102 of this title, 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 set forth in Graham v. John Deere Co., 383 U. S. 1, 148 USPQ 459 (1966), that are applied 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.
Claims 11-12 and 24-25 are rejected under 35 U. S. C. 103 as being unpatentable over KUMAR et al. (US 20200145977 A1) in view of RenBin et al. (US 20220150866 A1), and further in view of Kim et al. (US 20190254105 A1).
Regarding claim 11, KUMAR in view of RenBin teaches all the limitations of claim 1.
KUMAR in view of RenBin differs from the claimed invention in not specifically and clearly teaching wherein the height information of the UE is associated with one or more event types.
However, in the same field of endeavor, Kim teaches that wherein
the height information of the UE is associated with one or more event types ([0102], e.g. Regard to altitude/horizontal or vertical speed of the UE in the previous PCell/serving cell, the logging period for location information can be set based on period (periodic based) or event (event based). In periodic based, the period may be decided by UE (i.e. every 100 ms), or the period may be decided by network (i.e. every 100 ms). In event based, the UE may log the location information when entering and exiting point of the cell (i.e. height information of the UE is associated with an event types)).
The motivation to combine reference of Kim and RenBin within the method of KUMAR before the effective filing date of the invention is that the new method provides that in the aerial environments, speed of the aerial vehicles may be usually faster than the terrestrial UEs on the ground and the number of detected neighbor cells may be mostly larger than the terrestrial UEs cases. Because of these points, only the legacy mobility history reporting is not enough to support mobility scenarios of the aerial vehicles. According, a method performed by an aerial user equipment (UE) in a wireless communication system is provided. The method may comprise: leaving radio resource control (RRC) connected state; logging altitude information of the aerial UE when a specific condition is satisfied; and transmitting the altitude information when the aerial UE enters RRC connected state (See Kim [0006, 0007]).
Regarding claim 12, KUMAR in view of RenBin and further in view of Kim teaches all the limitations of claim 11.
Kim further teaches wherein the one or more event types indicate a change of height in an area of interest above or below a preconfigured threshold ([0103], e.g. Regard to rough location information, this information may be set by one or more threshold information (e.g. altitude below threshold or above threshold) which is optionally provided by network. The network may provide the threshold(s) via RRC dedicated signalling message (i.e. rough area event types indicate a change of height in an area of interest above or below a threshold)).
The motivation to combine reference of Kim and RenBin within the method of KUMAR before the effective filing date of the invention is that the new method provides that in the aerial environments, speed of the aerial vehicles may be usually faster than the terrestrial UEs on the ground and the number of detected neighbor cells may be mostly larger than the terrestrial UEs cases. Because of these points, only the legacy mobility history reporting is not enough to support mobility scenarios of the aerial vehicles. According, a method performed by an aerial user equipment (UE) in a wireless communication system is provided. The method may comprise: leaving radio resource control (RRC) connected state; logging altitude information of the aerial UE when a specific condition is satisfied; and transmitting the altitude information when the aerial UE enters RRC connected state (See Kim [0006, 0007]).
Regarding claim 24, KUMAR in view of RenBin teaches all the limitations of claim 14.
KUMAR in view of RenBin differs from the claimed invention in not specifically and clearly teaching wherein the height information of the UE is associated with one or more event types.
However, in the same field of endeavor, Kim teaches that wherein
the height information of the UE is associated with one or more event types ([0102], e.g. Regard to altitude/horizontal or vertical speed of the UE in the previous PCell/serving cell, the logging period for location information can be set based on period (periodic based) or event (event based). In periodic based, the period may be decided by UE (i.e. every 100 ms), or the period may be decided by network (i.e. every 100 ms). In event based, the UE may log the location information when entering and exiting point of the cell (i.e. height information of the UE is associated with an event types)).
The motivation to combine reference of Kim and RenBin within the method of KUMAR before the effective filing date of the invention is that the new method provides that in the aerial environments, speed of the aerial vehicles may be usually faster than the terrestrial UEs on the ground and the number of detected neighbor cells may be mostly larger than the terrestrial UEs cases. Because of these points, only the legacy mobility history reporting is not enough to support mobility scenarios of the aerial vehicles. According, a method performed by an aerial user equipment (UE) in a wireless communication system is provided. The method may comprise: leaving radio resource control (RRC) connected state; logging altitude information of the aerial UE when a specific condition is satisfied; and transmitting the altitude information when the aerial UE enters RRC connected state (See Kim [0006, 0007]).
Regarding claim 25, KUMAR in view of RenBin and further in view of Kim teaches all the limitations of claim 24.
Kim further teaches wherein the one or more event types indicate a change of height in an area of interest above or below a preconfigured threshold ([0103], e.g. Regard to rough location information, this information may be set by one or more threshold information (e.g. altitude below threshold or above threshold) which is optionally provided by network. The network may provide the threshold(s) via RRC dedicated signalling message (i.e. rough area event types indicate a change of height in an area of interest above or below a threshold)).
The motivation to combine reference of Kim and RenBin within the method of KUMAR before the effective filing date of the invention is that the new method provides that in the aerial environments, speed of the aerial vehicles may be usually faster than the terrestrial UEs on the ground and the number of detected neighbor cells may be mostly larger than the terrestrial UEs cases. Because of these points, only the legacy mobility history reporting is not enough to support mobility scenarios of the aerial vehicles. According, a method performed by an aerial user equipment (UE) in a wireless communication system is provided. The method may comprise: leaving radio resource control (RRC) connected state; logging altitude information of the aerial UE when a specific condition is satisfied; and transmitting the altitude information when the aerial UE enters RRC connected state (See Kim [0006, 0007]).
Allowable Subject Matter
Claims 13 and 26 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; and amending claim(s) to overcome any objection(s) and /or rejection(s) set forth in this Office action.
Conclusion
Applicant's amendment necessitated the new ground(s) of rejection presented in this Office action. Accordingly, THIS ACTION IS MADE FINAL. See MPEP § 706.07(a). Applicant is reminded of the extension of time policy as set forth in 37 CFR 1.136(a).
A shortened statutory period for reply to this final action is set to expire THREE MONTHS from the mailing date of this action. In the event a first reply is filed within TWO MONTHS of the mailing date of this final action and the advisory action is not mailed until after the end of the THREE-MONTH shortened statutory period, then the shortened statutory period will expire on the date the advisory action is mailed, and any extension fee pursuant to 37 CFR 1.136(a) will be calculated from the mailing date of the advisory action. In no event, however, will the statutory period for reply expire later than SIX MONTHS from the mailing date of this final action.
Any inquiry concerning this communication or earlier communications from the examiner should be directed to Mahendra Patel whose telephone number is (571) 270-7499. The examiner can normally be reached on 9:30 AM to 5:30 PM (EST) .
Examiner interviews are available via telephone, in-person, and video conferencing using a USPTO supplied web-based collaboration tool. To schedule an interview, Applicant is encouraged to use the USPTO Automated Interview Request (AIR) at http://www.uspto.gov/interviewpractice.
If attempts to reach the examiner by telephone are unsuccessful, the examiner’s supervisor, Anthony Addy can be reached on (571) 272-7795(571) 272-7795. The fax phone number for the organization where this application or proceeding is assigned is 571-273-8300.
Information regarding the status of an application may be obtained from the Patent Application Information Retrieval (PAIR) system. Status information for published applications may be obtained from either Private PAIR or Public PAIR. Status information for unpublished applications is available through Private PAIR only. For more information about the PAIR system, see http://pair-direct.uspto.gov. Should you have questions on access to the Private PAIR system, contact the Electronic Business Center (EBC) at 866-217-9197 (toll-free) ? If you would like assistance from a USPTO customer Service Representative or access to the automated information system, call 800-786-9199 (IN USA OR CANADA) or 571-272-1000.
/MAHENDRA R PATEL/ Primary Examiner, Art Unit 2645
Prosecution Insights