Device positioning for multi-sim user equipment

Abstract

A network element estimates a position of a user equipment served by a first network and a second network. At the network element, at least one memory and computer program code are configured to, with at least one processor, cause the network element to determine first position measurement information for the user equipment in the first network, obtain position assistance data associated with the second network, the position assistance data comprising at least second position measurement information for the user equipment in the second network, obtain frequency offset information and time offset information for transmissions in the first network and transmissions in the second network, and estimate the position of the user equipment based on the first position measurement information, the second position measurement information, the frequency offset information, and the time offset information.

Description

Technical Field

[0001] One or more example embodiments relate to wireless communication networks. Background Technology

[0002] Fifth-generation (5G) wireless communication networks are the next generation of mobile communication networks. The 3rd Generation Partnership Project (3GPP) is currently developing standards for 5G communication networks. These standards are known as the 3GPP New Radio (NR) standards. Summary of the Invention

[0003] The scope of protection sought by the various example embodiments is defined by the independent claims. Exemplary embodiments and / or features (if any) described in this specification that are not within the scope of the independent claims are to be interpreted as examples that help to understand the various embodiments.

[0004] According to one or more example embodiments, location information from at least two different networks is used to estimate the location of a user equipment (UE).

[0005] At least one example embodiment provides a network element for estimating the location of a user equipment served by a first network and a second network. The network element includes at least one processor and at least one memory, including computer program code. The at least one memory and the computer program code are configured, together with the at least one processor, to cause the network element to: determine first location measurement information for the user equipment in the first network; obtain location-aided data associated with the second network, the location-aided data including at least second location measurement information for the user equipment in the second network; obtain frequency offset information and time offset information for transmissions in the first network and the second network; and estimate the location of the user equipment based on the first location measurement information, the second location measurement information, the frequency offset information, and the time offset information.

[0006] According to one or more example embodiments, the network element can be a location management function for a first network.

[0007] Location-aided data includes the location of at least one base station in the second network, and at least one memory and computer program code configured with at least one processor to enable the network element to estimate the location of the user equipment based on first location measurement information, second location measurement information, frequency offset information, time offset information, and the location of at least one base station in the second network.

[0008] The first and second location measurement information may include uplink time difference of arrival (UL-TDOA) information or uplink round-trip time (UL-RTT) information.

[0009] At least one memory and computer program code may be configured with at least one processor to enable the network element to receive capability and connectivity reports from the user equipment, the capability and connectivity reports including (i) an indication of the user equipment as a user equipment with multi-user identification module capability and (ii) a network identifier for a second network.

[0010] At least one memory and computer program code can be configured, along with at least one processor, to enable the network element to obtain location-aided data from a location management function for a second network.

[0011] At least one memory and computer program code can be configured, along with at least one processor, to cause the network element to send a cross-network positioning request to a positioning management function for a second network. The cross-network positioning request requests the positioning management function for the second network to configure the user equipment to generate second location measurement information.

[0012] Cross-network location requests can include the time it takes to perform a location process in order to obtain second location measurement information.

[0013] At least one example embodiment provides a method for estimating the location of a user equipment served by a first network and a second network, the method comprising: determining first location measurement information for the user equipment in the first network; obtaining location auxiliary data associated with the second network, the location auxiliary data including at least second location measurement information for the user equipment in the second network; obtaining frequency offset information and time offset information for transmissions in the first network and transmissions in the second network; and estimating the location of the user equipment based on the first location measurement information, the second location measurement information, the frequency offset information, and the time offset information.

[0014] At least one other example embodiment provides a non-transitory computer-readable storage medium storing computer-readable instructions that, when executed by at least one processor at a network element, cause the network element to perform a method for estimating the location of a user equipment served by a first network and a second network. The method includes: determining first location measurement information for the user equipment in the first network; obtaining location auxiliary data associated with the second network, the location auxiliary data including at least second location measurement information for the user equipment in the second network; obtaining frequency offset information and time offset information for transmissions in the first network and transmissions in the second network; and estimating the location of the user equipment based on the first location measurement information, the second location measurement information, the frequency offset information, and the time offset information.

[0015] Location assistance data may include the location of at least one base station in the second network, and the location of the user equipment may be estimated based on the first location measurement information, the second location measurement information, the frequency offset information, the time offset information, and the location of at least one base station in the second network.

[0016] The first and second location measurement information includes uplink time difference of arrival (UL-TDOA) information or uplink round-trip time (UL-RTT) information.

[0017] The method may further include: receiving a capability and connectivity report from the user equipment, the capability and connectivity report including (i) an indication that the user equipment is a user equipment with multi-user identification module capability and (ii) a network identifier for a second network.

[0018] The method may also include obtaining location-aided data from location management functions used for a second network.

[0019] The method may further include sending a cross-network positioning request to a positioning management function for a second network, the cross-network positioning request requesting the positioning management function for the second network to configure the user equipment to generate second location measurement information.

[0020] Cross-network location requests can include the time it takes to perform a location process in order to obtain second location measurement information.

[0021] At least one other example embodiment provides a network element for estimating the location of a user equipment served by a first network and a second network. The network element includes: a unit for determining first location measurement information for the user equipment in the first network; a unit for obtaining location auxiliary data associated with the second network, the location auxiliary data including at least second location measurement information for the user equipment in the second network; a unit for obtaining frequency offset information and time offset information for transmissions in the first network and the second network; and a unit for estimating the location of the user equipment based on the first location measurement information, the second location measurement information, the frequency offset information, and the time offset information.

[0022] At least one other example embodiment provides a network element for estimating the location of a user equipment (UE) served by a first network and a second network. The network element includes at least one processor and at least one memory, including computer program code. The at least one memory and the computer program code are configured, together with the at least one processor, to cause the network element to: generate first enhanced cell identification information for the UE in the first network, obtain second enhanced cell identification information for the UE in the second network, and estimate the location of the UE based on the first enhanced cell identification information and the second enhanced cell identification information.

[0023] At least one memory and computer program code are configured, together with at least one processor, to enable the network element to estimate the location of the user equipment by combining first enhanced cell identification information and second enhanced cell identification information.

[0024] At least one memory and computer program code are configured, together with at least one processor, to enable the network element to obtain second enhanced cell identification information from a location management function for a second network.

[0025] At least one other example embodiment provides a method for estimating the location of a user equipment served by a first network and a second network, the method comprising: generating first enhanced cell identification information for the user equipment in the first network; obtaining second enhanced cell identification information for the user equipment in the second network; and estimating the location of the user equipment based on the first enhanced cell identification information and the second enhanced cell identification information.

[0026] At least one other example embodiment provides a network element for estimating the location of a user equipment served by a first network and a second network, the network element comprising: a unit for generating first enhanced cell identification information for the user equipment in the first network; a unit for obtaining second enhanced cell identification information for the user equipment in the second network; and a unit for estimating the location of the user equipment based on the first enhanced cell identification information and the second enhanced cell identification information.

[0027] At least one other example embodiment provides a non-transitory computer-readable storage medium storing computer-readable instructions that, when executed by at least one processor at a network element, cause the network element to perform a method for estimating the location of a user equipment served by a first network and a second network, the method comprising: generating first enhanced cell identification information for the user equipment in the first network; obtaining second enhanced cell identification information for the user equipment in the second network; and estimating the location of the user equipment based on the first enhanced cell identification information and the second enhanced cell identification information.

[0028] At least one other example embodiment provides a user equipment (UE) communicating with a first serving base station in a first network and a second serving base station in a second network. The UE includes at least one processor and at least one memory, including computer program code. The at least one memory and the computer program code are configured, together with the at least one processor, to cause the UE to: send a first capability and connectivity report to the first network, the first capability and connectivity report indicating (i) multi-user identification module (MIMB) capabilities for the UE and (ii) a network identifier for the second network; send a second capability and connectivity report to the second network, the second capability and connectivity report indicating (i) multi-user identification module (MIMB) capabilities for the UE and (ii) the network identifier for the first network; and report time offset information and frequency offset information to the first network for estimating the location of the UE, the time offset information indicating the time offset between transmissions in the first network and transmissions in the second network, and the frequency offset information indicating the frequency offset between transmissions in the first network and transmissions in the second network.

[0029] At least one memory and computer program code are configured, together with at least one processor, to enable the user equipment to: send a first capability and connectivity report to a first location management function for a first network, and to send a second capability and connectivity report to a second location management function for a second network.

[0030] At least one other example embodiment provides a method for operating a user equipment (UE) communicating with a first serving base station in a first network and a second serving base station in a second network, the method comprising: sending a first capability and connectivity report to the first network, the first capability and connectivity report indicating (i) multi-user identification module (MIMB) capabilities for the UE and (ii) a network identifier for the second network; sending a second capability and connectivity report to the second network, the second capability and connectivity report indicating (i) the UE's MIMB capabilities and (ii) the network identifier of the first network; and reporting time offset information and frequency offset information to the first network for estimating the location of the UE, the time offset information indicating a time offset between transmissions in the first network and transmissions in the second network, and the frequency offset information indicating a frequency offset between transmissions in the first network and transmissions in the second network.

[0031] At least one other example embodiment provides a non-transitory computer-readable storage medium storing computer-readable instructions that, when executed by at least one processor at a user equipment, cause the user equipment to perform a method of operating the user equipment to communicate with a first serving base station in a first network and a second serving base station in a second network. The method includes: sending a first capability and connectivity report to the first network, the first capability and connectivity report indicating (i) multi-user identification module capabilities for the user equipment and (ii) a network identifier for the second network; sending a second capability and connectivity report to the second network, the second capability and connectivity report indicating (i) multi-user identification module capabilities for the user equipment and (ii) the network identifier of the first network; and reporting time offset information and frequency offset information to the first network for estimating the location of the user equipment, the time offset information indicating a time offset between transmissions in the first network and transmissions in the second network, and the frequency offset information indicating a frequency offset between transmissions in the first network and transmissions in the second network.

[0032] At least one other example embodiment provides a user equipment (UE) communicating with a first serving base station in a first network and a second serving base station in a second network. The UE includes: a unit for sending a first capability and connectivity report to the first network, the first capability and connectivity report indicating (i) multi-user identification module (MIMB) capabilities for the UE and (ii) a network identifier for the second network; a unit for sending a second capability and connectivity report to the second network, the second capability and connectivity report indicating (i) multi-user identification module (MIMB) capabilities for the UE and (ii) a network identifier for the first network; and a unit for reporting time offset information and frequency offset information to the first network for estimating the location of the UE, the time offset information indicating the time offset between transmissions in the first network and transmissions in the second network, and the frequency offset information indicating the frequency offset between transmissions in the first network and transmissions in the second network. Attached Figure Description

[0033] The exemplary embodiments will become more fully understood from the detailed description and accompanying drawings given below, wherein similar elements are indicated by similar reference numerals, which are given by way of illustration only and therefore do not limit this disclosure.

[0034] Figure 1 A simplified diagram is shown to illustrate a portion of the 3GPP New Radio (NR) access deployment used to explain an example embodiment;

[0035] Figure 2 A signal flow diagram of a method according to an example embodiment is shown;

[0036] Figure 3 A signal flow diagram of another method according to an example embodiment is shown;

[0037] Figure 4 A signal flow diagram of another method according to an example embodiment is shown;

[0038] Figure 5 A block diagram of an example embodiment of a network element is shown.

[0039] It should be noted that these figures are intended to illustrate general features of the methods, structures, and / or materials used in some exemplary embodiments and to supplement the written description provided below. However, these figures are not drawn to scale and may not accurately reflect the precise structural or performance characteristics of any given embodiment, and should not be construed as defining or limiting the range of values ​​or characteristics contained in the exemplary embodiments. The use of similar or identical reference numerals in the various figures is intended to indicate the presence of similar or identical elements or features. Detailed Implementation

[0040] Various exemplary embodiments will now be described more fully with reference to the accompanying drawings, some of which illustrate exemplary embodiments.

[0041] This document discloses detailed illustrative embodiments. However, the specific structural and functional details disclosed herein are merely representative for the purpose of describing exemplary embodiments. Exemplary embodiments may be embodied in various alternative forms and should not be construed as being limited to the embodiments set forth herein.

[0042] It should be understood that there is no intention to limit the exemplary embodiments to the specific forms disclosed. Rather, the exemplary embodiments will cover all modifications, equivalents, and alternatives falling within the scope of this disclosure. Throughout the description of the drawings, the same numbers refer to the same elements.

[0043] While one or more example embodiments may be described from the perspective of a radio access network (RAN) or radio network element (e.g., gNB), user equipment (UE), etc., it should be understood that one or more example embodiments discussed herein may be executed by one or more processors (or processing circuitry) at an applicable device. For example, according to one or more exemplary embodiments, at least one memory may include or store computer program code, and the at least one memory and computer program code may be configured to use at least one processor to cause the radio network element (or user equipment) to perform the operations discussed herein.

[0044] As discussed in this article, the terms “one or more” and “at least one” are used interchangeably.

[0045] As discussed in this article, a gNB may also be referred to as a base station, access point, enhanced NodeB (eNodeB), or more generally, radio access network element, radio network element, or network node. A UE may also be referred to as a mobile station in this article and may include mobile phones, cellular phones, smartphones, handheld devices, personal digital assistants (PDAs), tablets, laptops, phablets, etc.

[0046] It should be understood that multiple example embodiments may be used in combination.

[0047] Multi-SIM devices can support multiple simultaneous or concurrent network connections (e.g., 3GPP networks) and multiple International Mobile Equipment Identity (IMEIs), each associated with a specific SIM. Therefore, multi-SIM devices can be served simultaneously or concurrently by different networks. The MSIM device manages device-side connectivity without network involvement. To this end, the MSIM device selects which service can be used with which SIM. Each SIM can support different types of subscriptions and quality of service.

[0048] Multi-UE SIM (multi-USIM) devices are becoming increasingly popular in various countries. In multi-USIM devices, users can have both personal and enterprise subscriptions on a single device, or two personal subscriptions for different services (e.g., a personal subscription and a "family" plan). However, without any support from 3GPP specifications, current support for multi-USIM within devices is handled in an implementation-specific manner, leading to various implementations and UE behaviors. From a performance perspective, standardized support for such UEs could be beneficial, as network functions could be based on more predictable behavior at the UE level.

[0049] UEs registered to more than one network, such as multi-USIM UEs, must be able to receive paging from more than one network. Depending on the UE's capabilities (e.g., receive (Rx) and transmit (Tx) capabilities), this may result in the UE being preoccupied with listening for paging from one network while paging from other networks may also be transmitted. Furthermore, while one network is attempting to page the UE, the UE can actively communicate with another network. If the UE switches between communication from a first network to a different second network, there may be situations where the UE is no longer able to receive data from the first network. This situation can negatively impact performance (e.g., if pages are sent but not received correctly, or if the UE is scheduled to communicate within a network that it cannot).

[0050] Regarding location services, 3GPP implemented the 3GPP NR Release 16 (Rel-16) work project for native location support in 3GPP NR. As a result of this work, the following location solutions were specified for 3GPP NR Rel-16:

[0051] Downlink Time Difference of Arrival (DL-TDOA)

[0052] • Uplink Time Difference of Arrival (UL-TDOA)

[0053] Downlink AoD (DL-AoD)

[0054] • Uplink Angle of Arrival (UL-AoA)

[0055] • Multi-cell round-trip time (multi-RTT)

[0056] Furthermore, this work involves specifying solutions to achieve both RAT-dependent (for FR1 and FR2) and RAT-independent NR positioning technologies. A new Positioning Reference Signal (PRS) is introduced on the downlink (DL). A new Detection Reference Signal (SRS) (SRS-P) is introduced on the uplink (UL) for positioning. Rel-16 also introduces UE-based positioning for downlink technologies (e.g., DL-TDOA), which allows the UE to perform positioning measurements and location estimation locally. In UE-based mode, the gNB's location is transmitted to the UE for use in the location estimation process.

[0057] In 3GPP NR Release 17 (Rel-17), further positioning work is expected to be carried out, with the main objective of studying enhancements and solutions that support relatively high accuracy (horizontal and vertical), relatively low latency, network efficiency (e.g., scalability, reference signal (RS) overhead, etc.) and device efficiency (e.g., power consumption, complexity, etc.) for commercial use cases, including general commercial use cases, especially Internet of Things (IoT) use cases.

[0058] Regarding emergency radio services, the Federal Communications Commission (FCC)'s Enhanced 911 (E911) rule seeks to improve the effectiveness and reliability of radio 911 services by providing 911 dispatchers with additional information about radio 911 calls. The FCC's E911 rule applies to all radio licensees, Broadband Personal Communications Service (PCS) licensees, and Certain Private Mobile Radio (SMR) licensees.

[0059] The U.S. Federal Communications Commission has divided the wireless E911 project into Phase 1 and Phase 2.

[0060] In the first phase, the FCC requires operators to provide the local public safety answering point (PSAP) with the phone number of the person who initiated the wireless 911 call and the location of the cell site or base station that sent the call within six months of a valid request being made.

[0061] In the second phase, the FCC requires wireless operators to begin providing more precise information to the PSAP (Powered Service Assisted Platform) within six months of a valid request, specifically the caller's latitude and longitude. This information must meet FCC accuracy standards, typically within a range of 50 to 300 meters, depending on the type of technology used. E911 deployment requires the development of new technologies and upgrades to local 911 PSAPs, as well as coordination among public safety agencies, wireless operators, technology vendors, equipment manufacturers, and local cable operators.

[0062] Currently, positioning in 3GPP NR networks relies on AoA and TDOA or RTT, each of which requires at least three or four visible gNBs to triangulate the UE's location. RTT is calculated by combining the UE receive-transmit (Rx-Tx) time difference measured by the UE and the gNB receive-transmit time difference measured by the gNB.

[0063] In non-line-of-sight (non-LoS) environments, more gNBs are needed to provide accurate positioning estimates. However, in rural areas and indoors (where there is no Global Navigation Satellite System (GNSS) connection), the availability of three or more gNBs can be difficult to achieve. Furthermore, even when three or more base stations are visible, sufficient accuracy may be difficult to obtain, especially in non-LoS scenarios.

[0064] One or more example embodiments provide mechanisms for improving the location accuracy of a UE in a 3GPP NR network. For example, one or more example embodiments provide mechanisms for estimating the location of a UE when fewer than three or four gNBs are visible in a single network. One or more example embodiments also provide mechanisms for improving the location accuracy of a UE under non-LoS conditions.

[0065] More specifically, for example, one or more example embodiments present a set of procedures to enable uplink or network-based positioning using gNBs from multiple networks, thereby obtaining a larger number of gNBs for triangulating the location of the UE. The example embodiments primarily focus on uplink or network-based positioning methods; however, the example embodiments should not be limited to the example embodiments discussed herein.

[0066] By employing one or more example embodiments, the network can utilize more visible gNBs (otherwise unavailable) and / or may further increase the number of gNBs to obtain a more accurate location estimate for the UE. The positioning techniques applied in the example embodiments may include UL-TDOA, multiple RTT, and / or enhanced positioning techniques based on cell ID (E-CID). However, the example embodiments should not be limited to these examples. Rather, the example embodiments can be applied to any positioning technique involving uplink transmissions.

[0067] Figure 1 A simplified diagram is shown to illustrate a portion of the 3GPP NR access deployment for a more detailed explanation of the example embodiment. Figure 1 The diagrams shown also include some embedded signaling to help explain the example embodiment. (Refer to later...) Figure 2 and Figure 3 Let's discuss this embedded signaling.

[0068] refer to Figure 1The 3GPP NR radio access deployment includes separate networks X and Y. Network X (also known as the first network X) includes gNB 102X and gNB 104X, which provide cellular resources for UEs (e.g., UE 106) within the first geographic coverage area. Network Y (also known as the second network Y) includes gNB 102Y and gNB 104Y, which provide cellular resources for UEs (e.g., UE 106) within the second geographic coverage area. The first and second geographic coverage areas may overlap. Furthermore, networks X and Y may employ the same or different radio access technologies and / or be deployed by the same or different network providers.

[0069] Although not shown, Figure 1 Each gNB in ​​a fifth-generation (5G) cell can have transmit and receive points (TRPs), where each TRP can be, for example, a remote radio head (RRH) or a remote radio unit (RRU), and includes at least, for example, a radio frequency (RF) antenna (or multiple antennas) or antenna panel, and a radio transceiver for transmitting and receiving data within a geographic area. In some cases, baseband processing can be divided between the TRPs and gNBs in a 5G cell. Alternatively, baseband processing can be performed at the gNB. Figure 1 In the example shown, the gNB is configured to communicate with the UE via one or more transmit (Tx) / receive (Rx) beam pairs. The gNB also communicates with the core network, referred to as the New Core in 3GPP NR, and includes Location Management Functions (LMF) 100X and LMF 100Y for Network X and Network Y, respectively. According to one or more example embodiments, LMF 100X and LMF 100Y communicate bidirectionally with each other, as well as with their respective RAN elements (e.g., the gNB) and the UE within their respective networks.

[0070] According to one or more example embodiments, LMF 100X and LMF 100Y can communicate using an extension to the Long Term Evolution (LTE) Positioning Protocol (LPP), which allows LMF 100X and LMF 100 to exchange messages using UE 106 as a relay. In another example embodiment, LMF 100X and LMF 100Y can communicate using IP layer signaling between LMFs. Although the example embodiments discussed herein relate to extensions to LPP and IP layer signaling, these example embodiments should not be limited to these examples. Detailed discussion is omitted because the details of LPP and IP layer signaling are generally known.

[0071] In addition to the specific functions discussed in this article, the LMF is a network entity that supports the following functions: location determination for the UE, obtaining downlink location measurements or location estimates from the UE, obtaining uplink location measurements from the radio access network (RAN, such as NG RAN), and obtaining non-UE-associated auxiliary data from the RAN.

[0072] exist Figure 1 In the access deployment shown, gNB 102X is the serving gNB for UE 106 in network X, while gNB 104X is the neighboring gNB in ​​network X. Similarly, gNB 102Y is the serving gNB for UE 106 in network Y, while gNB 104Y is the neighboring gNB in ​​network Y. LMF 100X is for location management functions in network X, and LMF 100Y is for location management functions in network Y. As mentioned above, each of LMF 100X and LMF 100Y resides in the core network.

[0073] Despite Figure 1 Only two networks are shown, but the example embodiment should not be limited to this example. Furthermore, although each network is shown as including only two gNBs for simplicity, the example embodiment should not be limited to this example. Rather, it is well known that a RAN can have any number of gNBs deployed across geographical regions.

[0074] UE 106 is a multi-USIMUE configured to communicate via multiple networks (in this case, networks X and Y). Although in Figure 1 Only a single UE 106 is shown, but networks X and Y can each provide communication services to a relatively large number of UEs within their respective geographical coverage areas. For clarity of the illustrative embodiment, communication services (including sending and receiving radio signals) between the LMF, gNB, and UE will be discussed. However, it should be understood that signals can be transmitted between the UE and one or more TRPs (not shown).

[0075] As described above, one or more example embodiments present a set of procedures to enable uplink or network-based positioning using gNBs from multiple networks, thereby obtaining a larger number of gNBs for triangulating the location of the UE. The example embodiments primarily focus on uplink or network-based positioning methods; however, the example embodiments should not be limited to those discussed herein.

[0076] Although not explicitly shown in the figure, location determination, according to one or more example embodiments, can be triggered by one or more location determination triggering events. According to one or more example embodiments, triggering events may include E911 service requests, network-initiated events, events initiated by user applications at the UE, etc. Location determination can also be performed periodically.

[0077] Figure 2 A signal flow diagram of a method for multi-SIM uplink positioning using UL-TDOA according to an example embodiment is shown. For illustrative purposes, reference will be made to... Figure 1 Let's discuss the access deployment shown. Figure 2 The example embodiments shown are shown. However, the example embodiments should not be limited to this example.

[0078] refer to Figure 2 At 202, UE 106 reports to LMF 100X that UE 106 has multiple USIM capabilities and is connected to network Y. In at least one example embodiment, UE 106 can indicate the connection to network Y by reporting the network identifier (ID) of network Y to LMF 100X. Also at 202, UE 106 can report to LMF 100X the positioning methods supported by network Y (e.g., TDOA, RTT, E-CID, etc.). In at least some cases, the report from UE 106 at 202 may be referred to herein as a (first) capability and connectivity report. UE 106 can send this capability and connectivity report using, for example, LPP signaling between UE 106 and LMF 100X in network X.

[0079] At step 224, UE 106 reports to LMF 100Y that UE 106 has multiple USIM capabilities and is connected to network X. In at least one example embodiment, UE 106 can indicate the connection to network X by reporting the network ID of network X to LMF 100Y. UE 106 can also report to LMF 100Y the positioning method supported by network X (e.g., UL-TDOA, UL-RTT, E-CID, etc.). In at least some cases, the report from UE 106 at step 224 may be referred to herein as a (second) capability and connectivity report. UE 106 can send this capability and connectivity report using, for example, LPP signaling between UE 106 and LMF 100Y in network Y. Steps 202 and 224 can occur in parallel, simultaneously, or serially.

[0080] As a result of 202, network X knows that UE 106 is connected to network Y and knows the network ID of network Y. As a result of 224, network Y knows that UE 106 is connected to network X and knows the network ID of network X.

[0081] Although not in Figure 2 As shown in the text, but Figure 1As shown, in at least some example embodiments, LMF 100X and LMF 100Y can exchange capability information to determine the location method supported by each corresponding network (e.g., in response to receiving LPP signaling that reports the network ID of another network) if the information is not reported by UE 106 at 202 or 224.

[0082] Still referencing Figure 2 Regarding network X, in response to the first capability and connectivity report from UE 106, at 204, LMF100X sends a location request to serving gNB 102X. This location request requests connectivity to UE 106 via serving gNB 102X, and requests the location of UE 106 via serving gNB 102X using UL-TDOA.

[0083] In 206, the serving gNB 102X configures UE 106 for uplink sounding reference signal (SRS) transmission in network X. In one example, the serving gNB 102X configures and / or allocates uplink SRS sequences, as well as time and frequency (physical) resources for uplink SRS transmission of UE 106, to the serving gNB 102 and the neighboring gNB 104X.

[0084] At 208, the serving gNB 102X configures the neighboring gNB 104X to receive uplink SRS transmissions from UE 106. In one example, the serving gNB 102X configures and / or allocates uplink SRS sequences and time and frequency (physical) resources for uplink SRS transmissions to UE 106 at the neighboring gNB 104X, enabling the neighboring gNB 104X to receive uplink SRS transmissions from UE 106. The configuration of the neighboring gNB 104X corresponds to the configuration of UE 106.

[0085] At 210, LMF 100X requests LMF 100Y to configure UE 106 for performing a location procedure (e.g., UL-TDOA, UL-RTT, E-CID, etc.) in network Y. According to at least one example embodiment, the request from LMF 100X may include the time at which the location procedure occurs (e.g., such that the time when the uplink SRS transmission from UE 106 in network Y is sent is relatively close to the time when the uplink SRS transmission is sent to UE 106 in network X). The request may also include the UE ID and location method (e.g., UL-TDOA, UL-RTT, E-CID, etc.) for UE 106. In this example, the location method is UL-TDOA. The request from LMF 100X to LMF 100Y may be referred to herein as a cross-network location request.

[0086] In at least one example embodiment, LMF 100X can send a cross-network location request to LMF 100Y using the LPP extensions discussed above, IP layer signaling between LMFs, etc. However, the exemplary embodiments should not be limited to this example.

[0087] In 212, UE 106 transmits uplink SRS transmissions by sending uplink SRS sequences configured on allocated physical resources (e.g., frequency and time resources) to serving gNB 102X and neighboring gNB 104X in network X.

[0088] At 214, in response to an uplink SRS transmission from UE 106, the serving gNB 102X provides UL-TDOA information to LMF 100X. This UL-TDOA information may include the arrival time (e.g., reception timestamp) observed or measured by UE 106 for the uplink SRS transmission at both the serving gNB 102X and the neighboring gNB 104X (reporting to the serving gNB 102X).

[0089] Redirecting to network Y, in response to a cross-network location request from LMF 100X (at 210), at 226, LMF 100Y sends a location request to serving gNB 102Y in network Y. This location request requests a connection to UE 106 via serving gNB 102Y, and requests the location of UE 106 using UL-TDOA via serving gNB 102Y.

[0090] According to at least one example embodiment, a location request from LMF 100Y may be the same as or substantially the same as a location request from LMF 100 discussed above with respect to 204.

[0091] In 228, serving gNB 102Y configures UE 106 for uplink SRS transmission in network Y. In one example, serving gNB 102Y configures and / or allocates uplink SRS sequences and time and frequency (physical) resources for uplink SRS transmission of UE 106 to serving gNB 102 and neighboring gNB 104Y in network Y.

[0092] At 230, serving gNB 102Y configures neighboring gNB 104Y to receive uplink SRS transmissions from UE 106 in network Y. In one example, serving gNB 102Y configures and / or allocates uplink SRS sequences and time and frequency (physical) resources for uplink SRS transmissions from UE 106 at neighboring gNB 104Y, enabling neighboring gNB 104Y to receive uplink SRS transmissions from UE 106 in network Y. The configuration of neighboring gNB 104Y corresponds to the configuration of UE 106 at 228.

[0093] In 232, UE 106 transmits uplink SRS transmissions in network Y by sending uplink SRS sequences configured on allocated physical resources (e.g., frequency and time resources) to serving gNB 102Y and neighboring gNB 104Y.

[0094] At 234, in response to an uplink SRS transmission from UE 106, serving gNB 102Y provides UL-TDOA information to LMF 100Y. This UL-TDOA information may include the arrival time (e.g., reception timestamp) observed or measured by UE 106 for the uplink SRS transmission at serving gNB 102Y and neighboring gNB 104Y (reporting to serving gNB 102Y).

[0095] As described above, the cross-network location request at location 210 includes the time when the location process occurs in network Y, such that the uplink SRS transmission from UE 106 in network Y is relatively close in time to the time when a similar uplink SRS transmission occurs in network X. Therefore, Figure 2 212 and 232 in the equation can occur simultaneously or substantially simultaneously.

[0096] Returning to network X, at 216, UE 106 provides time and frequency offset information to LMF 100X. The time and frequency offset information may include the time offset used for SRS transmission in network X (at 212) and network Y (at 232), as well as the frequency offset between network X and network Y. In at least one example embodiment, the time and frequency offsets between network X and network Y can be estimated based on downlink reference symbol / signal transmissions from serving gNB 102X and neighboring gNB 104X in network X, and from serving gNB 102Y and neighboring gNB 104Y in network Y. UE 106 can calculate the time and frequency offsets between network X and network Y in any suitable manner. UE 106 can report the frequency offset (delta) and time offset information to LMF 100X using LPP signaling.

[0097] At 220, LMF 100Y sends location assistance data for UE 106 in network Y to LMF 100X. According to one or more example embodiments, the location assistance data may include the locations of gNB 102Y and neighboring gNB 104Y in network Y and UL-TDOA information provided at 234.

[0098] At 222, LMF 100X jointly estimates the location of UE 106 based on UL-TDOA information from network X, UL-TDOA information from network Y, and frequency and time offset information provided by UE 106 at 216.

[0099] According to one or more example embodiments, UL-TDOA uses Time of Arrival (ToA) measurements (receive timestamp and receive frequency) and the location of the gNB to estimate the UE's location. In at least one example embodiment, the LMF 100X uses measurements from network X and network Y to increase the number of ToA measurements to calculate the location of UE 106. If used directly by the LMF 100X, the measurements from network Y may contain errors. To compensate for this error, the LMF 100X uses time and frequency offset information from UE 106 to adjust the ToA measurements from network X and network Y to have the same reference, so that these measurements can be used for joint location estimation.

[0100] More specifically, for example, in 222, LMF 100X can compensate for the offset between the ToA measurements (time and frequency) in the corresponding network X and network Y by subtracting the time and frequency offsets from the ToA measurements in network X or network Y. The ToA measurements can then be combined, and the combined measurements are used to estimate the location of UE 106 according to a known UL-TDOA calculation method that takes into account the locations of gNB 102X, gNB 102Y, gNB 104X, and gNB 104Y when determining the location of UE 106. In one example, the combination of measurements can be a weighted average.

[0101] According to at least one example embodiment, if the UL-TDOA information from each of networks X and Y includes measurements from at least three gNBs, then the LMF 100X can estimate the location of UE 106 in each network separately and combine the location estimates to generate a joint estimate of the location of UE 106. In this example, the combination may be the average of the estimated locations of UE 106 in each network.

[0102] Figure 3 A signal flow diagram of a method for multi-SIM uplink positioning using UL-RTT according to an example embodiment is shown. For illustrative purposes, reference will be made to... Figure 1Let's discuss the access deployment shown. Figure 3 The example embodiment shown is shown. However, the exemplary embodiment should not be limited to this example. Figure 3 In, with Figure 2 The same operations are identified by the same reference numerals.

[0103] refer to Figure 3 In step 202, UE 106 reports to LMF 100X that UE 106 has multi-USIM capability and is connected to network Y, a step consistent with the above regarding... Figure 2 The same or substantially the same methods are used to implement (first capability and connection report).

[0104] At 224, UE 106 reports to LMF 100Y that UE 106 has multi-USIM capability and is connected to network X, a step consistent with the above regarding... Figure 2 The same or substantially the same methods discussed are used to implement (secondary capabilities and connection reports).

[0105] As a result of 202, network X knows that UE 106 is connected to network Y and knows the network ID of network Y. As a result of 224, network Y knows that UE 106 is connected to network X and knows the network ID of network X.

[0106] Despite Figure 3 Not shown in the image, but... Figure 1 As shown, in at least some example embodiments, LMF 100X and LMF 100Y can exchange capability information so that if in Figure 3 At position 202 or 224, this information was not reported by UE 106, which determines the location method supported by each corresponding network (e.g., in response to receiving an LPP signaling that reports the network ID of another network).

[0107] Still referencing Figure 3 Regarding network X, in response to the first capability and connectivity report from UE 106, at 304, LMF100X sends a location request to serving gNB 102X. This location request requests connectivity to UE 106 via serving gNB 102X, and requests the location of UE 106 using UL-RTT. In at least one example embodiment, the UL-RTT location request may be similar to the one described above regarding network X, except that the location request uses UL-RTT to request the location of UE 106. Figure 2 The UL-TDOA location request under discussion.

[0108] In 306, the serving gNB 102X configures UE 106 for UL-RTT reception and transmission. More specifically, for example, the serving gNB 102X configures and / or allocates uplink SRS sequences, downlink PRS sequences, and physical (e.g., time and frequency) resources for uplink SRS transmission and downlink PRS reception, and the UE 106 reports the time offset (delta) for uplink SRS transmission and downlink PRS reception to the serving gNB 102X and the neighboring gNB 104X.

[0109] At 308, the serving gNB 102X configures its neighboring gNB 104X to send a downlink PRS to UE 106 and receive an uplink SRS from UE 106. More specifically, for example, the serving gNB 102X configures and / or allocates uplink SRS sequences and physical (e.g., time and frequency) resources to its neighboring gNB 104X for sending reference signals to and receiving reference signals from UE 106.

[0110] At 310, LMF 100X requests LMF 100Y to configure UE 106 for a positioning procedure in network Y (e.g., UL-RTT). According to at least one example embodiment, the request from LMF 100X may include the timing of the positioning procedure (e.g., such that the reference signal transmission in network Y is relatively close in time to the timing of the reference signal transmission in network X). The request may also include the UE ID and positioning method (e.g., UL-RTT) for UE 106. In this example, the positioning request method is UL-RTT. Figure 2 Similarly, a request sent from LMF 100X to LMF 100Y can be referred to here as a cross-network location request.

[0111] In at least one example embodiment, LMF 100X can send a cross-network location request to LMF 100Y using the LPP extensions discussed above, IP layer signaling between LMFs, etc. However, the exemplary embodiments should not be limited to this example.

[0112] In 312, the serving gNB 102X and the neighboring gNB 104X use the configured / allocated resources to send downlink PRS to UE 106.

[0113] In 212, UE 106 transmits uplink SRS transmissions by sending uplink SRS sequences configured on allocated physical resources (e.g., frequency and time resources) to serving gNB 102X and neighboring gNB 104X in network X.

[0114] At 314, the serving gNB 102X reports UL-RTT data to the LMF 100X. The UL-RTT data may include SRS information (e.g., SRS sequence and transmit and receive times (Tx-Rx time)) for uplink and downlink reference signals (e.g., uplink SRS and downlink PRS) from UE 106 and to UE 106.

[0115] Redirecting to network Y, in response to the cross-network location request from LMF 100X (at 310), at 326, LMF 100Y sends a location request to serving gNB 102Y in network Y. This location request requests a connection to UE 106 via serving gNB 102Y, and requests the location of UE 106 using UL-RTT from serving gNB 102Y. The location request may be the same as the location request discussed above with respect to 304, but here it pertains to network Y.

[0116] In 328, the serving gNB 102Y configures UE 106 for UL-RTT reception and transmission in network Y. More specifically, for example, the serving gNB 102Y configures and / or allocates uplink SRS sequences, downlink PRS sequences, and physical (e.g., time and frequency) resources for uplink SRS transmission and downlink PRS reception, and the UE 106 reports the time offset (delta) for uplink SRS transmission and downlink PRS reception to the serving gNB 102Y and neighboring gNB 104Y.

[0117] At 330, the serving gNB 102Y configures its neighbor gNB 104Y to send a downlink PRS to UE 106 in network Y and to receive an uplink SRS from UE 106. More specifically, for example, the serving gNB 102Y configures and / or allocates uplink SRS sequences to its neighbor gNB 104Y, as well as physical (e.g., time and frequency) resources for sending and receiving reference signals to and from UE 106 in network Y.

[0118] In 332, serving gNB 102Y and neighboring gNB 104Y use the resources configured / allocated in network Y to send downlink PRS to UE106.

[0119] In 232, UE 106 transmits uplink SRS transmissions by sending uplink SRS sequences configured on allocated physical resources (e.g., frequency and time resources) to serving gNB 102Y and neighboring gNB 104Y in network Y.

[0120] The cross-network location request at 310 includes the timing of the location process in network Y, such that the uplink SRS transmission from UE 106 in network Y is relatively close in time to the timing of a similar uplink SRS transmission in network X. Therefore, as Figure 2 , Figure 3 212 and 232 in the equation can occur simultaneously or substantially simultaneously.

[0121] In 334, service gNB 102Y reports UL-RTT data to LMF 100Y, in conjunction with the above regarding... Figure 3 The same or substantially the same approach discussed in section 314, but here concerning network Y. UL-RTT information may include SRS information (e.g., SRS sequence, transmit and receive times (Tx-Rx time)) for reference signals from UE 106.

[0122] At 320, LMF 100Y sends location assistance data for UE 106 in network Y to LMF 100X. This location assistance data may include the UL-RTT data for UE 106 provided at 334, as well as the locations of gNB 102Y and gNB 104Y in network Y.

[0123] In 322, LMF 100X jointly estimates the location of UE 106 based on location assistance data from LMF 100Y and UL-RTT data for UE 106 in Network X.

[0124] In at least one example embodiment, the LMF 100X utilizes UL-RTT data (e.g., RTT measurements) from network X and network Y to increase the number of measurements in order to calculate the location of UE 106 using the UL-RTT calculation method. Unlike UL-TDOA, in this example embodiment, time and frequency measurements in the network do not necessarily need to be compensated, since each RTT measurement represents the distance from the UE to the gNB. Nevertheless, the LMF 100X can compensate for errors between measurements if needed and / or necessary.

[0125] More specifically, for example, in 322, LMF 100X can combine RTT measurements from network X and network Y and use the combined measurements to estimate the location of UE 106 according to a known UL-RTT method that takes into account the locations of gNB 102X, gNB102Y, gNB 104X, and gNB 104Y. In one example, the combination of measurements could be a weighted average.

[0126] According to at least one example embodiment, if the UL-RTT data from each of Network X and Network Y includes RTT measurements from at least three gNBs, then LMF 100X can individually estimate the location of UE 106 in each network and combine the location estimates to generate a joint estimate of the location of UE 106. In this example, the combination may be the average of the estimated locations of UE 106 in each network.

[0127] Figure 4 A signal flow diagram of a method for multi-SIM uplink positioning using E-CID according to an example embodiment is shown. For illustrative purposes, reference will be made to... Figure 1 Let's discuss the access deployment shown. Figure 4 The example embodiments shown are shown. However, the example embodiments should not be limited to this example.

[0128] refer to Figure 4 In step 202, UE 106 reports to LMF 100X that UE 106 has multi-USIM capability and is connected to network Y, a step consistent with the above regarding... Figure 2 and Figure 3 The same or substantially the same methods are used to implement (first capability and connection report).

[0129] At 224, UE 106 reports to LMF 100Y that UE 106 has multi-USIM capability and is connected to network X, in order to communicate with the above regarding... Figure 2 and Figure 3 The same or substantially the same methods discussed are used to implement (secondary capabilities and connection reports).

[0130] As a result of 202, network X knows that UE 106 is connected to network Y and knows the network ID of network Y. As a result of 224, network Y knows that UE 106 is connected to network X and knows the network ID of network X.

[0131] and Figure 2 and Figure 3 Similar to the example embodiments shown, in at least some example embodiments, LMF 100X and LMF100Y can exchange capability information so that if in Figure 4 At positions 202 or 224, this information was not reported by UE 106, which determines the location method supported by each corresponding network (e.g., in response to receiving an LPP signaling that reports the network ID of another network).

[0132] In a 404 error, LMF 100X sends an E-CID location request to LMF 100Y. This E-CID location request asks LMF Y to obtain the E-CID location of UE 106 in network Y, and then sends the E-CID location of UE 106 in network Y to LMF 100X. In one example, LMF 100X can send the E-CID location request via LPP extensions, via IP layer signaling, etc.

[0133] In response to a location request from LMF 100X, at 406, LMF 100Y sends the E-CID location of UE 106 in network Y to LMF 100X.

[0134] At 408, LMF 100X estimates the location of UE 106 based on the E-CID location at LMF 100X and the E-CID location from LMF 100Y. According to at least one example embodiment, LMF 100X can jointly estimate the location of UE 106 by combining the E-CID locations from LMF 100X and the E-CID locations from LMF 100Y according to a weighted average. Although weighted averaging is discussed herein, the example embodiment should not be limited to this example.

[0135] Although this document discusses example embodiments with respect to SRS and PRS, these example embodiments should not be limited to them. Rather, the example embodiments may utilize any reference signal (RS) used for positioning.

[0136] Figure 5 It shows Figure 1 The example embodiment of the network element shown is illustrated. The network element can be used as... Figure 1 The LMF 100X, LMF 100Y, gNB 102X, gNB 102Y, gNB 104X, gNB 104Y and / or UE 106 are shown. However, for the sake of brevity, LMF 100X will be used as the reference in the description. Figure 5 .

[0137] As shown in the figure, the network element includes: a memory 540; a processor 520 connected to the memory 540; various interfaces 560 connected to the processor 520; and one or more (e.g., multiple) antennas or antenna panels 565 connected to the various interfaces 560. The various interfaces 560 and antennas 565 can constitute a transceiver for transmitting / receiving data from / to other network elements (e.g., UE 106, gNB 102X, gNB 102Y, gNB 104X, gNB 104Y, LMF 100Y, etc.) via one or more radio beams. It should be understood that, depending on the implementation of the network element, the network element may include more than Figure 5The components shown are far more numerous than those shown. However, it is not necessary to show all of these generally conventional components in order to disclose illustrative example embodiments.

[0138] Memory 540 may be a computer-readable storage medium, which typically includes random access memory (RAM), read-only memory (ROM), and / or permanent mass storage devices such as disk drives. Memory 540 also stores the operating system and any other routines / modules / applications for providing functionality of network elements (e.g., LMF, gNB, UE functionality, methods according to example embodiments, etc.) to be executed by processor 520. These software components may also be loaded into memory 540 from a separate computer-readable storage medium using a drive mechanism (not shown). Such a separate computer-readable storage medium may include a disk, magnetic tape, DVD / CD-ROM drive, memory card, or other similar computer-readable storage media (not shown). In some example embodiments, software components may be loaded into memory 540 via one of various interfaces 560 instead of via a computer-readable storage medium.

[0139] Processor 520 can be configured to execute instructions of a computer program by performing arithmetic, logical, and input / output operations of the system. Instructions can be provided to processor 520 by memory 540.

[0140] Various interfaces 560 may include components that interface the processor 520 with the antenna 565, or other input / output components. It should be understood that the various interfaces 560 and programs stored in the memory 540 to describe the specific functions of the network element will vary depending on the implementation of the network element.

[0141] Interface 560 may also include one or more user input devices (e.g., keyboard, keypad, mouse, etc.) and user output devices (e.g., display, speaker, etc.).

[0142] Although the terms first, second, etc., may be used herein to describe various elements, these elements should not be limited by these terms. These terms are used only to distinguish one element from another. For example, a first element may be referred to as a second element, and similarly, a second element may be referred to as a first element, without departing from the scope of this disclosure. As used herein, the term "and / or" includes any and all combinations of one or more of the associated listed items.

[0143] When an element is described as "connected" or "coupled" to another element, it can be directly connected or coupled to the other element, or there may be an intermediate element. Conversely, when an element is described as "directly connected" or "directly coupled" to another element, there is no intermediate element. Other words used to describe the relationship between elements should be interpreted in a similar way (e.g., "between" and "directly between", "adjacent to" and "directly adjacent to", etc.).

[0144] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting. As used herein, the singular forms “a,” “an,” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises,” “comprising,” “includes,” and / or “including” as used herein specify the presence of the stated features, integrals, steps, operations, elements, and / or components, but do not exclude the presence or addition of one or more other features, integrals, steps, operations, elements, components, and / or groups thereof.

[0145] It should also be noted that in some alternative implementations, the indicated functions / actions may not occur in the order shown in the diagram. For example, depending on the functions / actions involved, two diagrams shown consecutively may actually be executed substantially simultaneously or sometimes in reverse order.

[0146] Specific details are set forth in the following description to provide a thorough understanding of the exemplary embodiments. However, those skilled in the art will understand that the exemplary embodiments can be practiced without these specific details. For example, a system may be illustrated as a block diagram to avoid obscuring the exemplary embodiments due to unnecessary detail. In other instances, well-known processes, structures, and techniques may be shown without unnecessary detail to avoid obscuring the exemplary embodiments.

[0147] As discussed herein, illustrative embodiments will be described with reference to the actions and symbolic representations of operations (e.g., in the form of flowcharts, diagrams, data flow graphs, structural diagrams, block diagrams, etc.). These operations can be implemented as program modules, or functional processes including routines, programs, objects, components, data structures, etc., that perform specific tasks or implement specific abstract data types, and can be implemented using existing hardware such as existing user equipment, base stations, evolved Node Bs (eNBs), remote radio heads (RRHs), 5G base stations (gNBs), femtocells, network controllers, computers, etc. Such existing hardware can be processing or control circuitry systems, such as, but not limited to, one or more processors, one or more central processing units (CPUs), one or more controllers, one or more arithmetic logic units (ALUs), one or more digital signal processors (DSPs), one or more microcomputers, one or more field-programmable gate arrays (FPGAs), one or more system-on-a-chip (SoCs), one or more programmable logic units (PLUs), one or more microprocessors, one or more application-specific integrated circuits (ASICs), or any one or more other devices capable of responding to and executing instructions in a defined manner.

[0148] Although flowcharts can describe operations as a sequential process, many operations can be executed in parallel, concurrently, or simultaneously. Furthermore, the order of operations can be rearranged. A process can terminate when its operations are completed, but it can also have other steps not included in the diagram. A process can correspond to a method, function, procedure, subroutine, subroutine, etc. When a process corresponds to a function, its termination can correspond to the function returning from its calling function or the main function.

[0149] As disclosed herein, the terms "storage medium," "computer-readable storage medium," or "non-transitory computer-readable storage medium" can refer to one or more devices for storing data, including read-only memory (ROM), random access memory (RAM), magnetic RAM, core memory, disk storage media, optical storage media, flash memory devices, and / or other tangible machine-readable media for storing information. The term "computer-readable medium" can include, but is not limited to, portable or fixed storage devices, optical storage devices, and a variety of other media capable of storing, containing, or carrying instructions and / or data.

[0150] Furthermore, the example embodiments can be implemented using hardware, software, firmware, middleware, microcode, hardware description languages, or any combination thereof. When implemented in software, firmware, middleware, or microcode, program code or code segments for performing the necessary tasks can be stored in a machine or computer-readable medium, such as a computer-readable storage medium. When implemented in software, one or more processors will perform the necessary tasks. For example, as described above, according to one or more example embodiments, at least one memory may include or store computer program code, and at least one memory and computer program code can be configured, together with at least one processor, to cause a network element or network device to perform the necessary tasks. Furthermore, the processor, memory, and example algorithms encoded as computer program code serve as components for providing or causing the execution of the operations discussed herein.

[0151] A code segment of computer program code can represent any combination of procedures, functions, subroutines, programs, routines, subroutines, modules, software packages, classes, or instructions, data structures, or program statements. A code segment can be coupled to another code segment or hardware circuit by passing and / or receiving information, data, arguments, parameters, or memory contents. Information, arguments, parameters, data, etc., can be passed, forwarded, or transmitted via any suitable technology, including memory sharing, message passing, token passing, network transmission, etc.

[0152] As used herein, the terms “including” and / or “having” are defined as comprising (i.e., open language). As used herein, the term “coupling” is defined as a connection, but not necessarily direct or mechanical. Terms derived from “indicating” (e.g., “indicates” and “indication”) are intended to encompass all the various techniques that can be used to transmit or reference indicated objects / information. Some (but not all) examples of techniques that can be used to transmit or reference indicated objects / information include the transmission of indicated objects / information, the transmission of identifiers of indicated objects / information, the transmission of information used to generate indicated objects / information, the transmission of a part or portion of indicated objects / information, the transmission of some derivative of indicated objects / information, and the transmission of some symbol representing indicated objects / information.

[0153] According to the example embodiments, user equipment, base stations, eNBs, RRHs, gNBs, femtocells, network controllers, computers, etc., can be (or include) hardware, firmware, hardware-executed software, or any combination thereof. Such hardware may include processing or control circuitry systems, such as, but not limited to, one or more processors, one or more CPUs, one or more controllers, one or more ALUs, one or more DSPs, one or more microcomputers, one or more FPGAs, one or more SoCs, one or more PLUs, one or more microprocessors, one or more ASICs, or any other device capable of responding to and executing instructions in a defined manner.

[0154] The benefits, other advantages, and solutions to problems have been described above with respect to specific embodiments of this disclosure. However, the benefits, advantages, and solutions to problems, as well as any element(s) that may cause or lead to such benefits, advantages, or solutions, or cause such benefits, advantages, or solutions to become more apparent, shall not be construed as key, essential, or essential features or elements of any or all claims.

Claims

1. A network element for estimating the location of user equipment served by a first network and a second network, the network element comprising: At least one processor; as well as At least one memory, including computer program code, said at least one memory and said computer program code are configured to enable the network element to: Determine first location measurement information for the user equipment in the first network; Obtain location assistance data associated with the second network, the location assistance data including at least second location measurement information for the user equipment in the second network; Obtain frequency offset information and time offset information for transmission in the first network and transmission in the second network; Based on the first location measurement information, the second location measurement information, the frequency offset information, and the time offset information, the location of the user equipment is estimated. The first location measurement information includes first uplink time difference of arrival (UL-TDOA) information or first uplink round-trip time (UL-RTT) information. The first UL-TDOA information includes a first observed or measured arrival time for a first UL-TDOA transmission from the user equipment to at least two base stations in the first network. The first UL-RTT information includes a first transmission time for a first RTT downlink transmission from the first network to the user equipment and a first reception time for a first RTT uplink transmission from the user equipment to the first network. The second location measurement information includes second uplink time difference of arrival (UL-TDOA) information or second uplink round-trip time (UL-RTT) information. The second UL-TDOA information includes a second observed or measured arrival time for second UL-TDOA transmission from the user equipment to at least two base stations in the second network. The second UL-RTT information includes a second transmission time for second RTT downlink transmission from the second network to the user equipment and a second reception time for second RTT uplink transmission from the user equipment to the second network. as well as The user equipment receives a capability and connectivity report, which includes (i) an indication that the user equipment is a user equipment with a multi-user identification module capability and (ii) a network identifier for the second network.

2. The network element according to claim 1, wherein the network element is a positioning management function for the first network.

3. The network element according to any one of claims 1-2, wherein The location assistance data includes the location of at least one base station in the second network, and The at least one memory and the computer program code are configured, together with the at least one processor, to enable the network element to estimate the location of the user equipment based on the first location measurement information, the second location measurement information, the frequency offset information, the time offset information, and the location of at least one base station in the second network.

4. The network element according to any one of claims 1-2, wherein the first location measurement information and the second location measurement information include uplink time difference of arrival (UL-TDOA) information or uplink round-trip time (UL-RTT) information.

5. The network element according to any one of claims 1-2, wherein the at least one memory and the computer program code are configured with the at least one processor to enable the network element to obtain the location assistance data from a location management function for the second network.

6. The network element according to any one of claims 1-2, wherein the at least one memory and the computer program code are configured, together with the at least one processor, to cause the network element to send a cross-network positioning request to a positioning management function for the second network, the cross-network positioning request requesting the positioning management function for the second network to configure the user equipment to generate the second location measurement information.

7. The network element according to claim 6, wherein the cross-network positioning request includes the time for performing the positioning process to obtain the second location measurement information.

8. A method for estimating the location of a user equipment served by a first network and a second network, the method comprising: Determine first location measurement information for the user equipment in the first network; Obtain location assistance data associated with the second network, the location assistance data including at least second location measurement information for user equipment in the second network; Obtain frequency offset information and time offset information for transmission in the first network and transmission in the second network; Based on the first location measurement information, the second location measurement information, the frequency offset information, and the time offset information, the location of the user equipment is estimated. The first location measurement information includes first uplink time difference of arrival (UL-TDOA) information or first uplink round-trip time (UL-RTT) information. The first UL-TDOA information includes a first observed or measured arrival time for a first UL-TDOA transmission from the user equipment to at least two base stations in the first network. The first UL-RTT information includes a first transmission time for a first RTT downlink transmission from the first network to the user equipment and a first reception time for a first RTT uplink transmission from the user equipment to the first network. The second location measurement information includes second uplink time difference of arrival (UL-TDOA) information or second uplink round-trip time (UL-RTT) information. The second UL-TDOA information includes a second observed or measured arrival time for second UL-TDOA transmission from the user equipment to at least two base stations in the second network. The second UL-RTT information includes a second transmission time for second RTT downlink transmission from the second network to the user equipment and a second reception time for second RTT uplink transmission from the user equipment to the second network. as well as The user equipment receives a capability and connectivity report, which includes (i) an indication that the user equipment is a user equipment with a multi-user identification module capability and (ii) a network identifier for the second network.

9. The method of claim 8, wherein The location assistance data includes the location of at least one base station in the second network, and The estimation is based on the first location measurement information, the second location measurement information, the frequency offset information, the time offset information, and the location of at least one base station in the second network to estimate the location of the user equipment.

10. The method according to claim 8 or 9, wherein the first location measurement information and the second location measurement information include uplink time difference of arrival (UL-TDOA) information or uplink round-trip time (UL-RTT) information.

11. The method according to claim 8 or 9, further comprising: The location assistance data is obtained from the location management function used for the second network.

12. The method according to claim 8 or 9, further comprising: A cross-network location request is sent to the location management function for the second network, the cross-network location request requesting the location management function for the second network to configure the user equipment to generate the second location measurement information.

13. The method of claim 12, wherein the cross-network location request includes the time for performing the location process to obtain the second location measurement information.

14. A user equipment communicating with a first serving base station in a first network and a second serving base station in a second network, the user equipment comprising: At least one processor; as well as At least one memory, including computer program code, said at least one memory and said computer program code being configured to enable the user equipment in conjunction with said at least one processor: Send a first capability and connectivity report to the first network, the first capability and connectivity report indicating (i) a multi-user identification module capability for the user equipment and (ii) a network identifier for the second network, the multi-user identification module capability for the user equipment indicating that the user equipment is configured to be served by both the first network and the second network, and the network identifier for the second network indicating that the user equipment is connected to the second network; Send a second capability and connectivity report to the second network, the second capability and connectivity report indicating (i) the multi-user identification module capability of the user equipment and (ii) the network identifier of the first network, the network identifier of the first network indicating that the user equipment is connected to the first network; as well as The system reports time offset information and frequency offset information to the first network for estimating the location of the user equipment. The time offset information indicates the time offset between transmissions in the first network and transmissions in the second network, and the frequency offset information indicates the frequency offset between transmissions in the first network and transmissions in the second network.

15. The user equipment of claim 14, wherein the at least one memory and the computer program code are configured to enable the user equipment with the at least one processor. Send the first capability and connectivity report to the first location management function used in the first network, and Send the second capability and connectivity report to the second location management function used for the second network.

Images