Determining a user equipment location within a coverage sub-area of a cell based on the cell identity data
By dividing the coverage area into sub-regions and using cell identity data for location lookup, the problem of inaccurate UE location determination in existing technologies is solved, achieving higher-precision location locking.
Patent Information
- Application Number
- CN202180028134.2
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Priority Date
- 2021-04-16
- Filing Date
- 2021-04-19
- Publication Date
- 2024-11-05
- Estimated Expiration
- 2041-04-19
AI Technical Summary
Existing technologies lack sufficient positioning accuracy when determining the location of user equipment (UE) within a cellular coverage area, especially when considering neighboring cells, resulting in inaccurate location determination.
By using cellular identity data and combining it with a data structure, the coverage area of a cellular cell is divided into multiple coverage sub-areas. The location of the UE is then located in the data structure based on the cellular identity data, and the identity information of the serving cell and neighboring cells is used to achieve more accurate location locking.
It improves the positioning accuracy of the UE within the cellular coverage area, provides a higher granular level of location determination, reduces processing overhead, and can more accurately determine the UE's location when considering neighboring cells.
Smart Images

Figure CN115428538B_ABST
Abstract
Description
[0001] background
[0002] Various aspects of the present disclosure relate to positioning user equipment (UE) within the coverage area of a serving cell. The UE may be a wireless mobile device that provides various functionalities to a user. Some of these functionalities depend on positioning the UE. For example, the UE location may be used to support cell search, intra-frequency handover, or public land mobile network (PLMN) search.
[0003] Different techniques can be used to determine the UE location. Serving sector center and hybrid cell-sector positioning are examples of such techniques. In general, the more accurate the location determination, the higher the quality of service of location-based functionality.
[0004] Brief Overview
[0005] Methods, systems, computer-readable media, and apparatus for determining a UE position within a coverage sub-area of a cell based on cell identity data are presented. In some embodiments, the UE detects one or more cell identities, including a cell identity of a serving cell and possible cell identities of neighboring cells of the serving cell. The one or more cell identities are included in the cell identity data. The cell identity data is used in a search of a data structure that associates each coverage sub-area of the coverage area of the serving cell with a most likely location within each coverage sub-area and with each cell identity. The result of the search indicates that the UE is located at the most likely location within the coverage sub-area of the serving cell.
[0006] An example method for locating a mobile device within a coverage area of a serving cell in communication with the mobile device according to the present disclosure includes: receiving cell identity data, the cell identity data including one or more cell identities; determining a coverage sub-area of the coverage area of the serving cell based on using the cell identity data in a lookup of a data structure, the data structure associating each coverage sub-area of the coverage area with each cell identity, each coverage sub-area of each coverage sub-area being associated in the data structure with the cell identity of the serving cell, and at least one of the coverage sub-areas being further associated in the data structure with the cell identity of a neighbor cell. The method also includes: determining a position of the mobile device, the position being within the coverage sub-area of the coverage area of the serving cell.
[0007] An example method for determining cell coverage based on crowdsourced information received at a cellular entity of a data communications network according to the present disclosure includes obtaining, at the cellular entity, cell identity data and location data for a plurality of locations within a coverage area of a serving cell, wherein the cellular entity includes a mobile device or a computer system, and wherein, for each location, the location data includes a corresponding location, and the cell identity data includes one or more cell identities detected at corresponding locations of one or more mobile devices. The method also includes storing the location data and the cell identity data using the cellular entity. The method also includes associating, by the cellular entity, coverage sub-areas of the coverage area with cell identities based on the cell identity data and the location data using a data structure, wherein: each of the coverage sub-areas is associated with the cell identity of the serving cell in the data structure, and at least one of the coverage sub-areas is further associated with the cell identity of a neighbor cell in the data structure.
[0008] An example mobile device according to the present disclosure, the mobile device for locating the mobile device within a coverage area of a serving cell in communication with the mobile device, the mobile device comprising: a transceiver; a memory; and one or more processing units communicatively coupled to the transceiver and the memory. The one or more processing units are configured to: receive cell identity data via the transceiver, the cell identity data comprising one or more cell identities. The one or more processing units are further configured to: determine a coverage sub-area of the coverage area of the serving cell based on using the cell identity data in a lookup of a data structure, the data structure associating each coverage sub-area of the coverage area with each cell identity, each coverage sub-area of each coverage sub-area being associated with the cell identity of the serving cell in the data structure, and at least one of the coverage sub-areas being further associated with the cell identity of a neighbor cell in the data structure. The one or more processing units are further configured to: determine a location of the mobile device, the location being within the coverage sub-area of the coverage area of the serving cell.
[0009] An example cellular entity of a data communication network according to the present disclosure, the cellular entity for determining cell coverage based on crowdsourced information received at the cellular entity, the cellular entity comprising: a transceiver; a memory; and one or more processing units communicatively coupled to the transceiver and the memory. The one or more processing units are configured to obtain cell identity data and location data for a plurality of locations within a coverage area of a serving cell at the cellular entity, wherein the cellular entity comprises a mobile device or a computer system, and wherein, for each location: the location data comprises a corresponding location, and the cell identity data comprises one or more cell identities detected at the corresponding location of one or more mobile devices. The one or more processing units are further configured to store the location data and the cell identity data using the cellular entity. The one or more processing units are further configured to associate coverage sub-areas of the coverage area with cell identities based on the cell identity data and the location data, wherein each of the coverage sub-areas is associated with the cell identity of the serving cell in the data structure, and at least one of the coverage sub-areas is further associated with the cell identity of a neighbor cell in the data structure.
[0010] An example apparatus for locating a mobile device within a coverage area of a serving cell in communication with the mobile device according to the present disclosure includes: means for receiving cell identity data, the cell identity data including one or more cell identities. The example apparatus further includes: means for determining a coverage sub-area of the coverage area of the serving cell based on using the cell identity data in a lookup of a data structure, the data structure associating each coverage sub-area of the coverage area with each cell identity, each coverage sub-area of each coverage sub-area being associated in the data structure with the cell identity of the serving cell, and at least one of the coverage sub-areas being further associated in the data structure with the cell identity of a neighboring cell. The example apparatus further includes: means for determining a location of the mobile device, the location being within the coverage sub-area of the coverage area of the serving cell. Continued here.
[0011] An example apparatus for determining cell coverage based on crowdsourced information received at a cellular entity of a data communications network according to the present disclosure includes: means for obtaining, at the cellular entity, cell identity data and location data for a plurality of locations within a coverage area of a serving cell, wherein the cellular entity includes a mobile device or a computer system, and wherein, for each location: the location data includes a corresponding location, and the cell identity data includes one or more cell identities detected at corresponding locations of one or more mobile devices. The apparatus further includes: means for storing the location data and the cell identity data using the cellular entity. The apparatus further includes: means for associating, based on the cell identity data and the location data, coverage sub-areas of the coverage area with cell identities, wherein each of the coverage sub-areas is associated with the cell identity of the serving cell in the data structure, and at least one of the coverage sub-areas is further associated with the cell identity of a neighbor cell in the data structure.
[0012] An example non-transitory computer-readable medium according to the present disclosure stores instructions for locating a mobile device within a coverage area of a serving cell in communication with the mobile device. The instructions include: code for receiving cell identity data, the cell identity data including one or more cell identities. The instructions further include: code for determining a coverage sub-area of the coverage area of the serving cell based on using the cell identity data in a lookup of a data structure, the data structure associating each coverage sub-area of the coverage area with each cell identity, each coverage sub-area in each coverage sub-area being associated with the cell identity of the serving cell in the data structure, and at least one of the coverage sub-areas being further associated with the cell identity of a neighbor cell in the data structure. The instructions further include: code for determining a location of the mobile device, the location being within the coverage sub-area of the coverage area of the serving cell.
[0013] An example non-transitory computer-readable medium according to the present disclosure stores code for determining cell coverage based on crowdsourced information received at a cellular entity of a data communications network. The instructions include: code for obtaining, at the cellular entity, cell identity data and location data for a plurality of locations within a coverage area of a serving cell, wherein the cellular entity comprises a mobile device or a computer system, and wherein, for each location: the location data comprises a corresponding location, and the cell identity data comprises one or more cell identities detected at corresponding locations of one or more mobile devices. The instructions further include: code for storing the location data and the cell identity data using the cellular entity. The instructions further include: code for associating, by the cellular entity, coverage sub-areas of the coverage area with respective cell identities based on the cell identity data and the location data using a data structure, wherein: each of the coverage sub-areas is associated with the cell identity of the serving cell in the data structure, and at least one of the coverage sub-areas is further associated with the cell identity of a neighbor cell in the data structure. BRIEF DESCRIPTION OF THE DRAWINGS
[0015] Various aspects of the present disclosure are illustrated by way of examples. In the accompanying drawings, like reference numerals indicate similar elements.
[0016] Figure 1 An example of a communication system including user equipment and multiple cells in accordance with at least one embodiment is illustrated.
[0017] Figure 2 An example of using serving sector technology to locate a UE is illustrated.
[0018] Figure 3 An example of using hybrid cell-sector technology to position a UE is illustrated.
[0019] Figure 4 Illustrated are examples of coverage sub-areas within a coverage area of a cell in accordance with at least one embodiment.
[0020] Figure 5 An example of positioning a UE using an enhanced hybrid cell-sector technique in accordance with at least one embodiment is illustrated.
[0021] Figure 6
[0013] Another example of positioning a UE using an enhanced hybrid cell-sector technique in accordance with at least one embodiment is illustrated.
[0022] Figures 7A-7C
[0013] Yet another example of using enhanced hybrid cell-sector techniques (optionally with beams) to position a UE in accordance with at least one embodiment is illustrated.
[0023] Figure 8
[0013] An example of a process for defining coverage sub-areas within a coverage area of a cell that may be used in positioning a UE according to an enhanced hybrid cell-sector technique is illustrated in accordance with at least one embodiment.
[0024] Fig. 9 An example of a process for sending relevant location data and cell identity data to support definition of coverage sub-areas in accordance with at least one embodiment is illustrated.
[0025] Fig.10 An example of a process for network-based positioning of a UE based on coverage sub-areas in accordance with at least one embodiment is illustrated.
[0026] Fig.11 An example of a process for locating a UE within a coverage area of a serving cell with which the UE is in communication is illustrated in accordance with at least one embodiment.
[0027] Fig.12 An example of a process for UE-based positioning of a UE based on coverage sub-areas in accordance with at least one embodiment is illustrated.
[0028] Fig.13 Another example of a flow for UE-based positioning of a UE based on coverage sub-areas in accordance with at least one embodiment is illustrated.
[0029] Fig.14 Test results demonstrating improvements in positioning a UE based on coverage sub-areas in accordance with at least one embodiment are illustrated.
[0030] Fig.15 is a block diagram of an embodiment of a mobile device that can be used as a mobile device and / or UE, as in the embodiments herein and in connection with Figure 1-13 as described.
[0031] Fig.16 An embodiment of a system is described, which may be described above (e.g., in connection with Figures 1 to 13 ) as described.
[0032] Fig.17 A diagram of a communication system is shown in accordance with at least one embodiment.
[0033] Detailed Description
[0034] Several illustrative embodiments will now be described with reference to the accompanying drawings which form a part hereof. Although specific embodiments are described below in which one or more aspects of the present disclosure may be implemented, other embodiments may be used and various modifications may be made without departing from the scope of the present disclosure or the spirit of the appended claims.
[0035] As used herein, the terms "cell identity" and "cell identity data" may refer to one or more identifiers that may be used to identify and / or distinguish a cell. This may include, for example, a globally unique identifier and / or a locally unique identifier (e.g., a physical cell ID). The cell identity data may also include additional identifiers related to the cell. For example, as described in detail herein, a cell identity in a 5G network may also include a beam index (or other beam identifier). Because the coverage area of a cell may be divided into different beams, this may provide an additional level of granularity when determining the location of a user equipment (UE).
[0036] Embodiments of the present disclosure are particularly directed to determining the position of a UE within a coverage sub-area of a cell based on cell identity data. Generally, a UE may be located within the coverage area of a cell (e.g., the cell is a serving cell and a UE in connected mode resides on the serving cell, or the UE is in idle mode when located in the coverage area). There may be at least one neighbor cell. The coverage area of the serving cell may be divided into coverage sub-areas. At least one coverage sub-area in the coverage sub-area may be associated with a cell identity of a neighbor cell and with a most likely position (e.g., the center of the coverage sub-area or some other position as further described below). The cell ID and most likely position association may be stored in a data structure. Depending on the position of the UE within the coverage area, the UE may detect a neighbor cell and determine its cell identity. By using the cell identity in the search for the data structure, the most likely position within the coverage sub-area may be determined as the position fix of the UE. Therefore, relative to existing UE positioning techniques, the position of the UE may be determined more accurately (e.g., with a higher sub-area resolution) without any significant additional overhead (if any) (e.g., using the cell identity in the data structure search).
[0037] To illustrate, consider an example of a serving cell and two neighbor cells. The coverage area of the serving cell is divided into four coverage sub-areas: a first coverage sub-area that is exclusively associated with the cell identity of the serving cell, a second coverage sub-area that is also associated with the cell identity of the first neighbor cell but not associated with the second neighbor cell, a third coverage sub-area that is also associated with the cell identity of the second neighbor cell but not associated with the first neighbor cell, and a fourth coverage sub-area that is associated with the cell identities of both neighbor cells. Upon detection of the cell identity of only the serving cell, the UE is positioned at the center of the first coverage sub-area. Upon detection of the cell identities of the serving cell and the first neighbor cell, the UE is positioned at the center of the second coverage sub-area. Upon detection of the cell identities of the serving cell and the second neighbor cell, the UE is positioned at the center of the third coverage sub-area. Upon detection of all three cell identities, the UE is positioned at the center of the fourth coverage sub-area.
[0038] For clarity of explanation, various embodiments are described herein in conjunction with a serving cell and one or two neighboring cells. However, the embodiments are not limited thereto and may be applied to any number of cells. For example, there may be one serving cell and no neighboring cells (in which case the coverage sub-area becomes the same as the coverage area of the serving cell). In another illustration, there may be three or more neighboring cells. In general, the greater the number of neighboring cells, the greater the number of coverage sub-areas of the serving cell.
[0039] Figure 1 An example of a communication system 100 including a UE 110 and multiple cells including a serving cell 120 and a neighbor cell 130 is illustrated in accordance with at least one embodiment. The UE 110 may be located within a coverage area 122 of the serving cell 120. The UE 110 may detect a cell identity of the serving cell 120 (in a Figure 1 1 ) and, depending on its location within coverage area 122, detects the cell identity of neighbor cell 130 (in Figure 1 Based on such cell identities, UE 110 may be positioned within a coverage sub-area 124 of coverage area 122.
[0040] In one example, serving cell 120 includes network equipment for providing wireless communications according to a radio access technology (RAT). The network equipment includes, among other things, a set of base stations, each of which may include a directional antenna. The network equipment may be in communication with or include a computer system 140, such as a server or gateway that supports various functionalities of wireless communications.
[0041] The coverage area 122 may correspond to a geographic area covered by the set of base stations, to a sector within the geographic area, or to a timing advance (TA) area within a sector. Generally, the coverage area 122 is associated with the cell identity of the serving cell 120, and the association may be more granular than the level of a sector or TA area, where applicable. In addition, the coverage area 122 may be defined for a specific mobile network operator, frequency channel, or RAT. For example, a set of base stations may cover different frequency channels, each frequency channel having an absolute radio frequency channel number (ARFCN) or an enhanced ARFCN (EARFCN). Each of the frequency channels may have a corresponding coverage area 122.
[0042] As further described in conjunction with the following figures, coverage 122 may be divided into a plurality of coverage sub-areas, among which there is coverage sub-area 124. Each of the coverage sub-areas represents a smaller portion of coverage area 122. Each coverage sub-area is associated with a set of cell identities and a most likely location. The association may be stored in a data structure 142 in the memory of computer system 140. For example, coverage sub-area 124 may be associated with CID1 and CID2, and associated with a specific location fix within coverage sub-area 124. Data structure 142 may optionally include data defining coverage area 122 and other features of the coverage sub-areas (such as geographic boundaries). Of course, when there are multiple coverage areas (e.g., each coverage area is for a specific mobile network operator, frequency channel, or RAT), multiple coverage sub-areas may be defined for each of the coverage areas.
[0043] Similarly, neighbor cell 130 includes network equipment for providing wireless communications within coverage area 132. The network equipment includes, among other things, a set of base stations and may be in communication with computer system 140 or may include or be in communication with another computer system that provides the same functionality as computer system 140. Although not described in detail in the examples of FIG. Figure 1 As illustrated in FIG. 1 , coverage area 132 may also be divided into coverage sub-areas, and this division may be stored in a data structure (similar to data structure 142).
[0044] Computer system 140 stores data structure 142 and responds to lookups including one or more cell identities using location data from data structure 142. Data structure 142 may be stored as a map having multiple layers, or multiple maps with each map corresponding to a layer. Each layer may correspond to a coverage area, such coverage area is divided into corresponding coverage sub-areas, and each of such coverage sub-areas is associated with corresponding one or more cell identities and with a most likely location. Other types of data structures 142 are possible, including, for example, relational databases, tables, strings, etc.
[0045] In one example, the computer system 140 is a location server, which includes a set of processing units, memory, and data service modules (eg, wireless communication interfaces and / or network interfaces), similar to Fig.16 The computer system may be a stand-alone system, may be integrated with components of the network, or may be distributed between stand-alone components and the network. For example, the computer system may be integrated with a base station serving the cell 120, one or more edge servers, a controller (e.g., a software defined controller (SDN)), or a core network, or may be distributed between them. In various embodiments, non-limiting examples of location servers may include a mobile positioning system (MPS), a position determination entity (PDE), a gateway mobile location center (GMLC), and a service mobile location center (SMLC), as well as various other location determination entities.
[0046] In operation, while within coverage area 122, the UE may detect the cell identity (e.g., CID1) of serving cell 120. Depending on its location within coverage area 122 (e.g., as the UE travels closer to coverage area 132), the UE may also detect the cell identity (e.g., CID2) of neighbor cell 130. The detected cell identity / cell identities are included in cell identity data 112 sent from UE 110 to serving cell 120 (e.g., to its base station). Cell identity data 112 may be in the form of a cell identity (CID) measurement report, or an enhanced CID (eCID) measurement report, which contains information about serving cell 120 and optionally a list of neighbor cells that are also heard while camped on serving cell 120. The base station may use the cell identity data 112 to perform a lookup of the data structure 142 to determine a most likely location 128 of the UE 110 within one of the coverage sub-areas of the coverage area 122, and may return the most likely location 128 to the UE 110 as the location data 126. For example, when the cell identity data 112 includes CID1 and CID2, the location data 126 indicates a location fix of the UE 110 within the coverage sub-area 124. As further described below, this location determination may be local to the UE, whereby the UE 110 may store an instance of the data structure 142 in a memory of the UE 110 and may perform a local lookup using the cell identity data 112. Figure 2 An example of using a serving sector technique to locate a UE is illustrated. According to this technique, the cell identity of the serving cell is used to locate the UE, while one or more cell identities detected by the UE for one or more neighbor cells may be ignored in the position determination.
[0047] For the sake of clarity, the coverage area of a cell (serving cell or neighbor cell) is Figure 2 and other figures as having a circular shape. However, the coverage area may have any shape (eg, a triangle or other polygon), and as described herein above, may be defined for a specific mobile network operator, frequency channel, or RAT.
[0048] like Figure 2 As illustrated in FIG. 1 , a first coverage area 210 is defined for a serving cell on which a UE is camped. A second coverage area 220 (shown with vertical lines) and a third coverage area 230 (shown with horizontal lines) are defined for a first neighbor cell and a second neighbor cell, respectively. Each of the coverage areas 210, 220, and 230 is associated with a most likely location (e.g., corresponding to the center of the coverage area and at Figure 1 are associated with the
[0049] While the UE is camped on the serving cell, the UE location is determined to be the most likely location associated with the coverage area 210 of the serving cell (e.g., the center of the coverage area 210, indicated by an asterisk and labeled with element number 240). The determination of the UE location does not change while the UE remains camped on the serving cell, even when the UE reports the cell identity of the first neighbor cell, the cell identity of the second neighbor cell, or the cell identities of both neighbor cells. Accordingly, the serving sector technique may result in a less accurate UE location relative to other positioning techniques described in this disclosure.
[0050] Figure 3 An example of using a hybrid cell-sector technique to locate a UE is illustrated. According to this technique, in addition to the cell identity of the serving cell, one or more cell identities for one or more neighbor cells detected by the UE may also be used to determine the UE position. To avoid repetition and for brevity, the same element numbers are used in the drawings to refer to the same elements.
[0051] According to the hybrid cell-sector technique, the location of the UE is determined as a function of the cell identity detected by the UE, but without taking into account the coverage sub-areas within the coverage area 210 of the serving cell. For example, when the UE is camped on the serving cell and reports the cell identity of a first neighbor cell but does not report the cell identity of a second neighbor cell, the UE's location fix is determined as the most likely location between the center of the coverage area 210 of the serving cell and the coverage area 220 of the first neighbor cell (illustrated by the upper asterisk and marked by element number 310). In contrast, when the cell identity of the second neighbor cell is reported instead, the UE's location fix is determined as the most likely location between the center of the coverage area 210 of the serving cell and the coverage area 230 of the second neighbor cell (illustrated by the lower asterisk 320). When the cell identities of two neighbor cells are reported, the UE's location fix is determined to be the most likely location between the center of the coverage area 210 of the serving cell, the coverage area 220 of the first neighbor cell, and the coverage area 230 of the second neighbor cell (illustrated as the middle asterisk 330 between the upper and lower asterisks).
[0052] Referring back to any of the three explanations above, upon reporting the cell identity of a neighbor cell, the UE location may be determined to be outside the coverage area 210 of the serving cell, despite the fact that the UE is camped on the serving cell and its location is more likely to be within the coverage area 210. Accordingly, the hybrid cell-sector technique may result in a less accurate UE location relative to the positioning techniques described next in this disclosure.
[0053] Figure 4 An example of coverage sub-areas 410, 420, 430, and 440 within the coverage area 210 of a serving cell according to at least one embodiment is illustrated. Definitions of the coverage sub-areas 410, 420, 430, and 440 (e.g., associations with cell identities, most likely locations, and other features such as boundaries) may be stored in a data structure. When a UE is camped on a serving cell, a cell identity-based lookup of the data structure yields a most likely location of the UE within one of the coverage sub-areas 410, 420, 430, and 440, which provides more accurate and more granular results than the above positioning techniques without significantly increasing processing overhead (if any).
[0054] In general, the more the number of neighbor cells, the more the number of coverage sub-areas of the serving cell. The coverage sub-areas do not need to be contiguous and can be overlapping. In the case of overlap, multiple neighbor cells may be observed at the same UE location. In the case of non-overlap, a unique set of coverage sub-areas may be defined based on a unique set of neighbor combinations. Mathematically, the number C of such coverage sub-areas may be up to:
[0055]
[0056] Where N is the number of neighbor cells and M = 1 to N, and these coverage sub-areas do not need to be contiguous.
[0057] Each coverage sub-area may be defined based on the geographic location of the serving cell's base station(s) and the geographic location of the corresponding neighbor cell(s) base stations (e.g., their proximity, possible handover boundaries, and / or relative signal strength within the coverage area). The definitions may divide the coverage area into sub-areas of the same or different sizes and / or shapes based on various geographic locations. Each coverage sub-area may also be associated with one or more cell identities and a most likely location. Over time, based on measurements received from multiple UEs, as further described in the following figures, the definition of the coverage sub-areas (including their boundaries and / or most likely locations) may change, while the association with the cell identities generally remains unchanged.
[0058] like Figure 4, the first coverage sub-area 410 is exclusively associated with the cell identity of the serving cell. The second coverage sub-area 420 is exclusively associated with the cell identities of the serving cell and the first neighbor cell. The third coverage sub-area 430 is exclusively associated with the cell identities of the serving cell and the second neighbor cell. The fourth coverage sub-area 440 is associated with the cell identities of the serving cell and two neighbor cells.
[0059] As such, when the UE reports that it has detected only the cell identity of the serving cell, the UE is located within the first coverage sub-area 410. When the UE reports that it has additionally detected the cell identity of the first neighbor cell but not the cell identity of the second neighbor cell, the UE is located within the second coverage sub-area 420. In contrast, when the UE reports that it has additionally detected the cell identity of the second neighbor cell but not the cell identity of the first neighbor cell, the UE is located within the third coverage sub-area 430. When the UE reports that it has additionally detected the cell identities of both neighbor cells, the UE is located within the fourth coverage sub-area 440. The position fix within each of the coverage sub-areas 410, 420, 430, and 440 may be a most likely position. The most likely position for each of the coverage sub-areas 410, 420, 430, and 440 may initially be defined as the center of such coverage sub-area and may subsequently be refined based on measurements reported from multiple UEs, as further described in conjunction with the following figures.
[0060] Despite Figure 4 Although not illustrated in the figure, each of the coverage areas 220 and 230 may be divided into coverage sub-areas. When the UE camps on the first neighbor cell (e.g., this neighbor cell becomes the serving cell of the UE), the coverage sub-area of the first neighbor cell may be used for positioning the UE. The coverage sub-area of the second neighbor cell may be used similarly.
[0061] Figure 5 An example of using an enhanced hybrid cell-sector technique to locate a UE in accordance with at least one embodiment is illustrated. According to this technique, one or more cell identities detected by a UE may be used to locate the UE within one of the coverage sub-areas, and specifically, at a most likely location within such coverage sub-areas.
[0062] exist Figure 5, only the coverage area 210 of the serving cell and its coverage sub-areas 410, 420, 430, and 440 are shown. In addition, improvements to the definition of the coverage sub-area 420 are shown as circles superimposed on top of the coverage sub-area 420. The improvements may be based on statistical analysis of observed location data 510, where such data 410 may be reported from multiple UEs. Similar improvements may also be defined for the remaining coverage sub-areas 420, 430, and 440, but not in FIG. Figure 5 , and in order to avoid redundancy and for the sake of brevity of explanation, their description will not be repeated herein.
[0063] From each of the reporting UEs, the observed location data 510 may include a cell identity of a serving cell (e.g., CID1) and a cell identity of at least a first neighbor cell (e.g., CID2). The observed location data 510 may also include a cell identity of a second neighbor cell (e.g., CID3), and optionally this cell identity may be filtered out, such as in conjunction with Figures 7A-7C Further described. This observed location data 510 may also include location data of the reporting UE, where the location data may indicate the location of the UE with high accuracy and may be generated by a location sensor of the UE. For example, the location data is Global Positioning System (GPS) data measured by the UE using its GPS sensor. Additionally or alternatively, the location data of the UE may not be reported by the UE and may be determined by the network using some other positioning technology (e.g., multi-angle measurement, multilateration, beacon, etc.).
[0064] Based on the observed location data 510 of the various UEs, a computer system on the network side (e.g., Figure 1 The computer system 140 of the embodiment may perform statistical analysis to determine the set of UEs that detect the serving cell and the neighbor cell and their corresponding positions. The boundary of the coverage sub-area and the most likely position 520 may be improved based on the statistical analysis. For example, the boundary may be set to include the position of a certain percentile (e.g., 99% or some other percentile threshold) of the set of UEs. The most likely position 520 may be defined as the average position of the positions of the UEs within the set of UEs.
[0065] The improvement of the coverage sub-areas may additionally be subject to a number of constraints. A first constraint may limit the boundaries of each coverage sub-area to within the boundaries of coverage area 210. In this way, if a UE is camped on a serving cell and detects a neighbor cell, the UE location may not be determined to be outside of coverage area 210 (e.g., as in conjunction with Figure 3 in the case of the hybrid cell-sector technology described herein).
[0066] The second constraint may limit the most likely location 520 (rather than the boundaries of each coverage sub-area of the first constraint) to be within the coverage area 210, regardless of the boundaries of the improved or original coverage sub-areas 420. Also in this manner, if the UE is camped on a serving cell and detects a neighbor cell, the UE location may not be determined to be outside of the coverage area 210.
[0067] The third constraint may avoid overlap between improved coverage sub-areas. In other words, the coverage sub-areas are non-overlapping, which may avoid inaccurate determinations regarding a UE being within two different coverage sub-areas.
[0068] Figure 6 Another example of using an enhanced hybrid cell-sector technique to locate a UE in accordance with at least one embodiment is illustrated. According to this technique, one or more cell identities detected by the UE may also be used to locate the UE within one of the coverage sub-areas. However, the position fix is not the most likely position within such a coverage sub-area, but rather a weighted position between the possible positions.
[0069] In one example, and referring back to the coverage area 210, the coverage area 210 has a sector center 610 (shown with an asterisk below at the center of the coverage area 210, although it may be located somewhere other than at the center of the coverage area 210). Referring back also to the improved coverage sub-area 420 (at Figure 6 , represented by element 620 and labeled as "covered sub-area"), the covered sub-area 620 has a sector center 630. The sector center 630 is Figure 6 , is shown with an asterisk above and may be the center of the coverage sub-area 620, or, as described herein above, may be an average location of the locations of UEs that reported the cell identity of the first neighbor cell while camped on the serving cell.
[0070] When camped on the serving cell and when the UE reports the cell identity of the first neighbor cell but does not report the cell identity of the second neighbor cell, the UE is determined to be within the coverage sub-area 620. The position fix (e.g., the most likely position 640) of the UE may be determined as a weighted position between the sector center 610 of the serving cell 210 and the sector center 630 of the coverage sub-area 620. In an example, the weights of the sector centers 610 and 630 may be equal. Accordingly, the most likely position 640 is the average position between the two sector centers 610 and 630. In another example, the weight depends on several factors. These factors include any of the following: the size of the coverage sub-area 620 relative to the size of the coverage area 210 (e.g., area, the farthest point from the sector center 630, etc.), or the characteristics (e.g., strength, time delay, etc.) of the signal transmitted from the first neighbor cell and detected by the UE relative to the characteristics (e.g., strength, time delay, etc.) of the signal transmitted from the serving cell and detected by the UE. For example, the larger the size of coverage sub-area 620, the larger the weight of sector center 630 and the smaller the weight of sector center 610, so that most likely position 640 is closer to sector center 630. In another illustration, the smaller the signal strength from the first neighbor cell, the smaller the weight of sector center 630 and the larger the weight of sector center 610, so that most likely position 640 is closer to sector center 610.
[0071] Fig. 7A Another example of positioning a UE using an enhanced hybrid cell-sector technique according to at least one embodiment is illustrated. In this figure, a coverage area 210 of a serving cell is shown. In addition, various coverage sub-areas 710, 720, 730, and 740 of the coverage area 210 are shown as circles superimposed on the coverage area 210 to indicate that these coverage sub-areas have been improved based on measurements reported from various UEs when camped on the serving cell (e.g., corresponding to coverage sub-areas 410, 420, 420, and 440). Each of the coverage sub-areas 710, 720, 730, and 740 has a corresponding most likely position 712, 722, 732, or 742 (shown with asterisks). The definition of the coverage sub-areas 710, 720, 730, and 740 and their most likely positions 712, 722, 732, and 742 can be derived based on the three constraints described above herein. Additionally or alternatively, a fourth constraint can be used. This fourth constraint may filter the UE's measurements based on the detected cell identity.
[0072] In one example, each of the UE reports is location data and a detected cell identity as part of the collected measurement data. The measurement data can be filtered into data sets, where the sets are exclusive and do not include overlapping measurement data. The first set includes location data for UEs that only detect the cell identity of the serving cell (e.g., CID1). This first set is used to define a first coverage sub-area 710 and its most likely location 712. The second set includes location data for UEs that only detect the cell identity of the serving cell (e.g., CID1) and the cell identity of the first neighbor cell (e.g., CID2). This second set is used to define a second coverage sub-area 720 and its most likely location 722. The third set includes location data for UEs that only detect the cell identity of the serving cell (e.g., CID1) and the cell identity of the second neighbor cell (e.g., CID3). This third set is used to define a third coverage sub-area 730 and its most likely location 732. The fourth set includes location data of UEs that detected the cell identity of the serving cell (eg, CID1) and the cell identities of two neighbor cells (eg, CID2 and CID3). This fourth set is used to define a fourth coverage sub-area 740 and its most likely location 742.
[0073] In an example, depending on one or more cell identities detected by the UE, the location of the UE may be any of the most likely locations 712, 722, 732, or 742. For example, when camped on a serving cell and only CID1 and CID2 are detected, the UE is determined to be within the second coverage sub-area 720 and is positioned at the most likely location 722.
[0074] In one example, the location of the UE may be a sector center (eg, Figure 6 ) and any of the most likely positions 712, 722, 732, or 742. For example, when camped on the serving cell and upon detection of only CID1 and CID2, the UE is determined to be within the second coverage sub-area 720 and is positioned at a weighted position between the sector center 610 and the most likely position 722.
[0075] It can be noted that in 5G wireless systems (e.g., as in Fig.17 ), embodiments may further utilize different beams of a cell to provide additional granularity about the UE location. Fig. 7A An example of a configuration is in Figure 7B and 7C Explanation in.
[0076] Figure 7B 750 (which directs wireless signals along different angles). The beams 750 may be generated using an antenna array, and the number and angular width of the beams 750 may vary depending on the desired functionality. (For example, a cell may generate a different number of beams based on different operating modes.) A signal transmitted using any of these beams 750 may be associated with a beam index indicating which beam was used to transmit the signal. Because beams may be identified and associated with different locations within the coverage area of a cell, these locations may be used in conjunction with the techniques provided herein (e.g., in addition to combinations of different cell IDs) to provide additional granularity in positioning a UE.
[0077] Figure 7C Explained Fig. 7A 760 (and the corresponding possible locations, represented by asterisks within each coverage sub-area 760). (To avoid confusion, Figure 7C Only a portion of the coverage sub-area 760 is marked. ) Specifically, Figure 7C Each coverage sub-area 760 illustrated in FIG. 7 represents a coverage sub-area (similar to FIG. 7 ) having a unique combination of cellular identity information (e.g., a combination of CID1, CID2, and / or CID3) in consideration of the beam attachment constraints of the serving cell. Fig. 7A of the covered sub-area).
[0078] It may be noted that, additionally or alternatively, embodiments may utilize beams of neighbor cells. For example, according to some embodiments, the coverage sub-area 760 may be defined based on beams of the serving cell in addition to beams of one or more neighbor cells. Alternatively, for example, the coverage sub-area 760 may be defined based on beams of one or more neighbor cells instead of beams of the serving cell. Different beam combinations of the serving cell may be used depending on desired functionality, beam availability, etc. It can be seen that, in the case of using beams of the serving cell and / or neighbor cells, embodiments herein may be able to provide a high degree of granularity regarding the UE location.
[0079] Figures 8 to 13 An illustrative process related to positioning a mobile device (e.g., UE) based on one or more cellular cell identities according to various embodiments is shown. Some or all of the instructions for performing the operations of the illustrative process may be implemented as a mobile device (e.g., Figure 1 UE 110) or a computer system (e.g., Figure 1The computer system 140 of the network entity and / or the computer readable instructions stored on the non-transitory computer readable medium of the network entity. According to different embodiments, the computer system may be located in the core network (CN) or radio access network (RAN) of the data communication network. (described below) Fig.17 Includes an example CN (5GC 1740) and an example RAN (NG-RAN 1735). As implemented, these instructions represent modules that include circuit systems or codes that can be executed by one or more processors of a mobile device or computer system, where applicable. The use of such instructions configures the mobile device or computer system (where applicable) to perform specific operations described herein. Each circuit system or code combined with the processor represents a means for performing the corresponding operation(s). For example, for performing Figures 8 to 13 The functional means at each operation shown in FIG. 1 may include software and / or hardware components of the mobile device, such as Fig.15 The bus 1505, processing unit(s) 1510, DSP 1520, wireless communication interface 1530, memory 1560 and / or other components of the mobile device 1500 illustrated in FIG. 1 and described in more detail below, and / or may include software and / or hardware components of a computer system that may be incorporated into a base station or network server. These components may include, for example, Fig.16 1605, processing unit(s) 1610, DSP 1620, wireless communication interface 1630, memory 1660, and / or other components of the computer system illustrated in FIG. 1604 and described in more detail below. Although the operations are shown in a particular order, it should be understood that a particular order is not required and that one or more operations may be omitted, skipped, performed in parallel, and / or reordered.
[0080] Figure 8 An example of a process 800 for determining cell coverage based on crowdsourced information received at a cellular entity of a data communications network in accordance with at least one embodiment is illustrated. Among other things, the process 800 provides for defining coverage sub-areas within a coverage area of a cell that can be used in positioning a mobile device (e.g., UE) in accordance with an enhanced hybrid cell sector technique. Figure 8 The means for performing one or more operations illustrated in process 800 may include hardware and / or software components of a mobile device or a server. For example, a single mobile device may be used to obtain location data at multiple locations and generate a data structure based on the location data. Alternatively, a server may receive crowdsourced information including location data from one or more mobile devices at multiple locations. In either case, the components for performing process 800 may include or be similar to Fig.15 and Fig.16Those components explained in , they will be described in more detail below.
[0081] As illustrated, process 800 begins at operation 802 of a mobile device, where functionality includes obtaining cell identity data and location data for a plurality of locations within a coverage area of a serving cell. For each location: (i) the location data includes a corresponding location, and (ii) the cell identity data includes one or more cell identities detected at the corresponding location of one or more mobile devices. As mentioned, this may include a single mobile device capturing a state at a plurality of locations. Additionally or alternatively, one or more mobile devices may determine the data and send it to a server. The location may be generated by a location sensor of the mobile device, such as by a GPS sensor. Additionally or alternatively, the location data may be determined from a computing resource other than the mobile device, such as by utilizing location multi-angle measurement, multilateration, and / or beacons. The mobile device may also obtain and send a cell identity of the serving cell and one or more cell identities corresponding to one or more neighbor cells (if any) detected by the mobile device at the location. Thus, according to some embodiments of process 800, for at least one of the plurality of locations, the cell identity data includes a cell identity of the serving cell and a cell identity of at least one neighbor cell. Depending on the desired functionality, the neighbor cells may include: a cell that is different from the serving cell and may be on the same frequency channel as the serving cell, a cell on a different frequency channel than the serving cell, a cell on a different radio access technology (RAT) using the same frequency channel as the serving cell, or a cell on a different RAT using a different frequency channel than the serving cell, or any combination thereof.
[0082] At operation 804, functionality includes storing the location data and the cell identity data. Specifically, location data and cell identity data may be collected from one or more mobile devices across mobile network operators, frequency channels, RATs, serving cells, and neighbor cells, and the collected data may be stored in a data store, such as a local memory of a device (e.g., a mobile device or a server) collecting the data, or a network-accessible or otherwise remotely accessible storage location.
[0083] At operation 806, the functionality includes associating each coverage sub-area of the coverage area with each cell identity based on the cell identity data and the location data in a data structure. Each coverage sub-area in each coverage sub-area is associated with the cell identity of the serving cell in the data structure, and at least one coverage sub-area in each coverage sub-area is further associated with the cell identity of the neighboring cell in the data structure. For example, for each mobile network operator, frequency channel or RAT, and for each cell acting as a serving cell, the coverage area of the serving cell may be divided into a number of coverage sub-areas. The number depends on the number of neighboring cells of the serving cell. The boundaries of each coverage sub-area may depend on the relative positions of the serving cell and the neighboring cell. In addition, the boundaries may be further improved based on statistical analysis of the location data and the cell identity data stored in the data store. The statistical analysis may optionally use any one or a combination of the four constraints described above.
[0084] At operation 808, the functionality includes defining a most probable position for each coverage sub-area. For example, the most probable position may be set to the center of the coverage sub-area. In another illustration, the most probable position may be set based on position data stored in a data store and associated with the coverage sub-area (e.g., the most probable position is an average of various positions included in the position data and / or may be a weighted position).
[0085] At operation 810, the functionality includes generating a data structure that associates each cell identity with each coverage sub-area and each most likely location. In one example, the data structure may be a mapping comprising multiple layers. Each layer corresponds to a mobile network operator, a frequency channel, and / or a RAT. In one layer, the coverage area of a cell that serves as a serving cell is identified and associated with the cell identity of this cell. In addition, each coverage sub-area of the coverage area and their corresponding most likely locations are identified and associated with the cell identity of the serving cell, and, where applicable, with one or more cell identities corresponding to one or more neighboring cells of the serving cell. As further mentioned herein, beams may be used to provide additional granularity to sub-areas. Accordingly, in some embodiments, the data structure may further associate the coverage sub-area of the coverage area with a beam index of the serving cell, a beam index of a neighboring cell, or both.
[0086] With this in mind, for some embodiments of process 800, the data structure may represent a mapping that (i) divides the coverage area of the serving cell into coverage sub-areas, (ii) maps each coverage sub-area to a set of cell identities, and (iii) indicates the location of the target mobile device as a possible location within the coverage sub-area, wherein the possible location is determined based on location data collected from the one or more mobile devices when the one or more mobile devices are located in the coverage sub-area. According to some embodiments, the mapping may be associated with at least one of: a mobile network operator, a frequency channel, or a radio access technology. Additionally or alternatively, the coverage sub-area associated with the cell identity of the neighbor cell may be further associated with a possible location, wherein the cell identity data includes the cell identity of the neighbor cell, and wherein the location is the possible location.
[0087] According to some embodiments, a coverage area may be associated with a first possible location, wherein a coverage sub-area associated with a cell identity of a neighbor cell may be further associated with a second possible location. In such embodiments, the cell identity data may include a cell identity of a neighbor cell, the location may be within a coverage sub-area associated with the cell identity of the neighbor cell and include a possible location determined based on the first possible location and the second possible location. Additionally or alternatively, the coverage sub-area of the serving cell may include a plurality of unique non-overlapping coverage sub-areas, wherein the data structure associates each of these unique non-overlapping coverage sub-areas with the serving cell and with a set of unique neighbor cells.
[0088] According to some embodiments, the data structure may represent a mapping that (i) divides the coverage area of the serving cell into coverage sub-areas and (ii) constrains the boundaries of each coverage sub-area to be within the boundaries of the coverage area. Alternatively, the data structure may represent a mapping that (i) divides the coverage area of the serving cell into coverage sub-areas and (ii) constrains possible mobile device locations within each coverage sub-area to be within the coverage area. According to some embodiments, process 800 may further include: storing, for each of the plurality of cells, a corresponding data structure that divides the coverage area of the respective cell into coverage sub-areas.
[0089] At operation 812, the functionality includes facilitating positioning of the mobile device based on the data structure. As further described in the following flow chart, this may include the server returning a location fix to the mobile device, or sending a data structure or a portion of a data structure to the mobile device to allow the mobile device to locally determine its location fix.
[0090] Fig. 9An example of a process 900 for sending relevant location data and cell identity data to support definition of a coverage sub-area in accordance with at least one embodiment is illustrated. As illustrated, the process 900 begins at operation 902, where a mobile device generates location data. For example, the mobile device resides on a serving cell and determines its location based on a location sensor of the mobile device.
[0091] At operation 904, the mobile device generates cell identity data. For example, the cell identity data includes a cell identity of a serving cell. In addition, the mobile device may detect neighbor cells based on signals transmitted from neighbor cells. The signal may include a cell identity of a neighbor cell. For each detected neighbor cell (if any), the mobile device includes the corresponding cell identity in the cell identity data.
[0092] At operation 906, the mobile device sends the location data and the cell identity data to the computer system. For example, the mobile device sends the location data and the cell identity data to the base station of the serving cell, and the base station in turn relays the location data and the cell identity data to the computer system. The transmission of the mobile device can follow a push mechanism or a pull mechanism. In a push mechanism, the mobile device can periodically determine its location and detected cell identity, and automatically transmit the resulting location data and cell identity data. In a pull mechanism, the mobile device uses its location data and cell identity data to respond to requests from the computer system. Based on the location data and cell identity data received from the mobile device and similarly data received from other mobile devices, the computer system can, as shown in FIG. Figure 8 The data structure is generated as described in process 800 of .
[0093] At operation 908, the mobile device facilitates positioning of the mobile device based on the data structure. As further described in the following flow chart, the mobile device can send cell identity data of one or more currently detected cell identities and receive a position fix from the computer system. Additionally or alternatively, the mobile device can receive the data structure or a portion of the data structure from the computer system so that the mobile device can locally determine its position fix.
[0094] Fig.10An example of a process 1000 for network-based positioning of a mobile device based on coverage sub-areas in accordance with at least one embodiment is illustrated. As illustrated, the process 1000 begins at operation 1002, where a computer system receives cell identity data from a user equipment. The cell identity data includes a cell identity of a serving cell in which the mobile device resides, and, where applicable, one or more cell identities corresponding to one or more neighbor cells of the serving cell and detected by the mobile device. The cell identity data may be received according to a pull mechanism or a push mechanism. In an example, the cell identity data is received in a CID or eCID measurement report.
[0095] At operation 1004, the computer system determines the location of the user equipment based on a search of the data structure. For example, the search includes cell identity data (or more specifically, one / more cell identities included in the cell identity data). When an entry in the data structure matches the cell identity data, the match indicates a coverage sub-area of the coverage area and a most likely location of the mobile device within the coverage sub-area. The most likely location may be defined in the data structure as a center of the coverage area, an average location based on collected mobile device location data, and / or a weighted location.
[0096] The computer system sends the location to the user equipment at operation 1006. For example, the location is sent as location data.
[0097] Fig.11 An example of a process 1100 for locating a mobile device within a coverage area of a serving cell in communication with a mobile device according to at least one embodiment is illustrated. As illustrated, the process 1100 begins at operation 1102, where the mobile device receives cell identity data. The cell identity data includes one or more cell identities. For example, the one or more cell identities of a cell include a cell identity of a serving cell. Depending on the location of the mobile device within the coverage area, the mobile device can detect one or more neighbor cells of the serving cell, each of which is associated with a cell identity. In this case, the one or more cell identities include a cell identity of each detected neighbor cell. Generally, the mobile device detects the cell identity of a cell (serving cell or neighbor cell) based on a signal sent from a base station of the cell and received by the mobile device. The signal includes the cell identity.
[0098] Means for performing the functionality at operation 1102 may include software and / or hardware components of a mobile device, such as Fig.15The bus 1505, processing unit(s) 1510, DSP 1520, wireless communication interface 1530, memory 1560, and / or other components of the mobile device 1500 are illustrated in FIG. 1 and described in greater detail below.
[0099] At operation 1104, the mobile device determines a coverage sub-area of the coverage area of the serving cell based on using the cell identity data in a lookup of a data structure. The data structure associates each coverage sub-area of the coverage area with each cell identity. Each of the coverage sub-areas is associated with the cell identity of the serving cell in the data structure. As mentioned, each of those coverage sub-areas may also be associated with a beam of the serving cell, a beam of a neighbor cell, or both. At least one of the coverage sub-areas is further associated with the cell identity of the neighbor cell in the data structure. Means for performing the functionality at operation 1104 may include software and / or hardware components of the mobile device, such as Fig.15 The bus 1505, processing unit(s) 1510, DSP 1520, wireless communication interface 1530, memory 1560, and / or other components of the mobile device 1500 are illustrated in FIG. 1 and described in greater detail below.
[0100] At operation 1106, the mobile device determines a location of the mobile device that is within the coverage sub-area of the coverage area of the serving cell. Means for performing the functionality at operation 1106 may include software and / or hardware components of the mobile device, such as Fig.15 The bus 1505, processing unit(s) 1510, DSP 1520, wireless communication interface 1530, memory 1560, and / or other components of the mobile device 1500 are illustrated in FIG. 1 and described in greater detail below.
[0101] In one example, the lookup at block 1104 is performed by a computer system, wherein the mobile device sends cell identity data to the computer system and receives back a location. In this example, the mobile device sends the cell identity data to the computer system, wherein the computer system stores the data structure, and wherein determining the location of the user equipment includes receiving the location from the computer system. This computer system-based location lookup is Fig.12. In another example, the lookup is performed by a mobile device, wherein the mobile device at least sends a cell identity of a serving cell, receives a data structure or a portion of a data structure, performs a lookup, and determines a location. In this example, the mobile device stores the data structure in a memory of the mobile device, and performs a lookup of the data structure from the memory. In a variation of this example, the mobile device sends the cell identity of the serving cell to a computer system, wherein the computer system stores a corresponding data structure that divides the coverage area of the cell into coverage sub-areas for each cell in a plurality of cells. The mobile device receives a data structure corresponding to the serving cell from the computer system based on the cell identity of the serving cell. This mobile device-based location lookup is Fig.13 Further explanation in.
[0102] The mobile device may also be one of the mobile devices that provides location data to generate the data structure. In this case, the mobile device determines, by a location sensor of the user equipment, location data indicating a second location of the user equipment within the coverage area of the serving cell before receiving the cell identity data; receives second cell identity data including the cell identity of the serving cell and the cell identities of the neighboring cells; and sends the location data and the second cell identity data to the computer system, wherein the data structure is generated by the computer system based on the location data and the second cell identity data.
[0103] In one example, the data structure represents a mapping that (i) divides a coverage area of a serving cell into coverage sub-areas, and (ii) maps each coverage sub-area to a set of cell identities, and (iii) indicates a location of a user equipment as a possible location within the coverage sub-area. The possible location is determined based on location data collected from the plurality of user equipment when the plurality of user equipment is located in the coverage sub-area. In addition, the mapping is associated with at least one of: a mobile network operator, a frequency channel, or a radio access technology.
[0104] In an example, the coverage sub-area associated with the cell identity of the neighbor cell is further associated with the possible location.The cell identity data includes the cell identity of the neighbor cell, and wherein the location is the possible location.
[0105] In one example, the coverage area is associated with a first possible location. A coverage sub-area associated with a cell identity of a neighbor cell is further associated with a second possible location. The cell identity data includes a cell identity of the neighbor cell. The location is within the coverage sub-area associated with the cell identity of the neighbor cell and is a possible location determined based on the first possible location and the second possible location.
[0106] In one example, the coverage sub-area of the serving cell includes several unique non-overlapping coverage sub-areas, wherein the data structure associates each of these unique non-overlapping coverage sub-areas with the serving cell and with a unique neighbor cell set. The unique neighbor cell set may but need not include an empty neighbor cell set. For example, these unique non-overlapping coverage sub-areas include: a first coverage sub-area associated with the serving cell and the neighbor cell and a second coverage sub-area associated with the serving cell and not associated with a neighbor cell. In this example, the second coverage sub-area is defined based on first data of a first plurality of user equipments, wherein the third coverage sub-area is defined based on second data of a second plurality of user equipments. The first data includes a first user equipment location and a cell identity of a neighbor cell, wherein the first data does not include a cell identity of another neighbor cell. The second data includes a second user equipment location, a cell identity of a neighbor cell, and a cell identity of the other neighbor cell.
[0107] In an example, the data structure represents a mapping that (i) divides the coverage area of the serving cell into coverage sub-areas and (ii) constrains the boundaries of each coverage sub-area to be within the boundaries of the coverage area.
[0108] In an example, the data structure represents a mapping that (i) divides the coverage area of the serving cell into coverage sub-areas and (ii) constrains possible user equipment locations within each coverage sub-area to be within the coverage area.
[0109] In an example, the data structure represents a mapping that divides the coverage area of the serving cell into coverage sub-areas, and wherein the coverage sub-areas are non-overlapping.
[0110] In one example, the neighbor cell is at least one of: a cell that is different from the serving cell and on the same frequency channel as the serving cell, a cell on a different frequency channel from the serving cell, or a cell on a different RAT using the same frequency channel as the serving cell, or a cell on a different RAT using a different frequency channel from the serving cell.
[0111] Fig.12 An example of a process 1200 for performing mobile device-based positioning of a mobile device based on coverage sub-areas in accordance with at least one embodiment is illustrated. As illustrated, the process 1200 begins at operation 1202, where the mobile device receives cell identity data. The cell identity data includes a cell identity of a serving cell in which the mobile device resides, and, where applicable, one or more cell identities corresponding to one or more neighbor cells of the serving cell and detected by the mobile device. The one or more cell identities may be determined from corresponding signals transmitted by the neighbor cell(s) and received by the mobile device.
[0112] At operation 1204, the mobile device sends the cell identity data to the computer system. The cell identity data may be sent according to a pull mechanism or a push mechanism. In an example, the cell identity data is sent in a CID or eCID measurement report.
[0113] At operation 1206, the mobile device receives its location from the computer system based on a lookup of the data structure by the computer system. Fig.10 Operation 1004 of flow 1000 and using the cell identity data sent at operation 1204. In response to sending the cell identity data, a location may be received as location data.
[0114] Fig.13 Another example of a process 1300 for performing mobile device-based positioning of a mobile device based on coverage sub-areas in accordance with at least one embodiment is illustrated. As illustrated, the process 1300 begins at operation 1302, where the mobile device sends to a computer system a cell identity of a serving cell in which the mobile device resides. Although the mobile device may have detected one or more neighbor cells, the cell identities of such neighbor cells may not be reported to the computer system.
[0115] At operation 1304, the mobile device receives a data structure from the computer system. The data structure is associated with a serving cell, indicates its coverage area and coverage sub-areas, and indicates a most likely location within each of the coverage sub-areas (e.g., indicated as a center, an average location, or a weighted location). In one example, the computer system stores a single data structure for different coverage areas, such as a map (or a layer of a map). Rather than receiving the entire data structure, the computer system determines a portion of the data structure indicating the coverage area of the serving cell (e.g., a segment of the map), and returns this portion to the mobile device, thereby requiring a smaller amount of storage and processing at the mobile device. The mobile device stores the data structure (or a portion thereof) in a memory of the mobile device.
[0116] At operation 1306, the mobile device receives cell identity data. In addition to the cell identity of the serving cell, the cell identity data also includes, where applicable, one or more cell identities corresponding to neighbor cells and detected by the mobile device.
[0117] At operation 1308, the mobile device determines the location of the mobile device based on a lookup of the data structure. Fig.10 Operation 1004 of flow 1000 , but performed by the mobile device based on a data structure (or a portion thereof) stored in a memory of the mobile device and using the cell identity data generated at operation 1306 .
[0118] Fig.14 1400 is illustrated showing test results 1400 demonstrating improvement in positioning of a mobile device based on coverage sub-areas in accordance with at least one embodiment. As illustrated in the figure, the horizontal error improvement is Figure 2 Specifically, the actual position measurement determined by the position sensor and the above combined Figures 2 to 3 and Figures 5 to 7A -7C described technique to determine the position fix is performed and compared to derive the cumulative distribution function (CDF) of the horizontal error in meters and x times. Figure 2 The described technology is labeled "Serving Sector Center (Drive-BSA)". Figure 3 The described technology is labeled "Hybrid Serving Sector Center (Drive-BSA)". Figure 5 The described technique is labeled "Hybrid Neighborhood Sector Center (Drive-BSA)". Figure 6 The described technology is labeled "Hybrid Service and Neighborhood Sector Affinity (Drive-BSA)". Fig. 7A The described technique is labeled "Sector Center of Unique Neighbor Sets (Drive-BSA)". Fig.14 As shown in the measurements plotted in Fig. 7A The described technique is superior to combining Figure 6 The described technique is superior to combining Figure 5 The described technique is superior to combining Figure 3 The described technique is superior to combining Figure 2 Describe the technology.
[0119] Fig.15 is a block diagram of an embodiment of a mobile device 1500 that can be used as a mobile device and / or UE, as in the embodiments herein and in connection with Figures 1 to 13 It should be noted that Fig.15It is intended only to provide a general illustration of the various components of mobile device 1500, any or all of which may be utilized as appropriate. In other words, because mobile devices may vary widely in functionality, they may only include Fig.15 It may be noted that in some instances, the Fig.15 The illustrated components may be localized to a single physical device and / or distributed among various networked devices that may be located at different physical locations.
[0120] The mobile device 1500 is shown as including hardware elements that may be electrically coupled (or may be in communication in other ways as appropriate) via a bus 1505. The hardware elements may include a processing unit(s) 1510, which may include, but is not limited to, one or more general-purpose processors, one or more special-purpose processors (such as digital signal processing (DSP) chips, graphics acceleration processors, application-specific integrated circuits (ASICs), etc.), and / or other processing structures or devices that may be configured to perform one or more of the methods described herein. Fig.15 As shown in , some embodiments may have a separate DSP 1520 depending on the desired functionality. The mobile device 1500 may also include one or more input devices 1570 and one or more output devices 1515, the one or more input devices 1570 may include but are not limited to: one or more touch screens, touch pads, microphones, buttons, dials, switches, etc.; the one or more output devices 1515 may include but are not limited to one or more displays, light emitting diodes (LEDs), speakers, etc.
[0121] The mobile device 1500 may also include a wireless communication interface 1530, which may include but is not limited to a modem, a network card, an infrared communication device, a wireless communication device, and / or a chipset (such as equipment, IEEE802.11 equipment, IEEE 802.15.4 equipment, WiFi equipment, WiMAX TM equipment, cellular communication facilities, etc.), etc., which can enable the mobile device 1500 to be as described herein Figures 1 to 13 The wireless communication interface 1530 may allow data to be communicated with a network, an eNB, an ng-eNB, a gNB, and / or other network components, a computer system, and / or any other electronic device described herein. The communication may be performed via one or more wireless communication antennas 1532 that send and / or receive wireless signals 1534.
[0122] Depending on the desired functionality, the wireless communication interface 1530 may include a separate transceiver to communicate with base stations (e.g., eNBs, ng-eNBs, and / or gNBs) and other terrestrial transceivers (such as wireless devices and access points). The mobile device 1500 may communicate with different data networks, which may include various network types. For example, a wireless wide area network (WWAN) may be a code division multiple access (CDMA) network, a time division multiple access (TDMA) network, a frequency division multiple access (FDMA) network, an orthogonal frequency division multiple access (OFDMA) network, a single carrier frequency division multiple access (SC-FDMA) network, WiMAX (IEEE 802.16), and the like. A CDMA network may implement one or more radio access technologies (RATs), such as cdma2000, wideband CDMA (WCDMA), and the like. Cdma2000 includes IS-95, IS-2000, and / or IS-856 standards. TDMA networks can implement global system for mobile communications (GSM), digital advanced mobile phone system (D-AMPS), or some other RAT. OFDMA networks can use LTE, advanced LTE, new radio (NR), etc. 5G, LTE, advanced LTE, NR, GSM, and WCDMA are described in documents from 3GPP. Cdma2000 is described in documents from an organization named "3rd Generation Partnership Project 2" (3GPP2). 3GPP and 3GPP2 documents are publicly available. Wireless local area network (WLAN) can also be an IEEE 802.11x network, and wireless personal area network (WPAN) can be a Bluetooth network, IEEE 802.15x, or some other type of network. The technology described herein can also be used for any combination of WWAN, WLAN, and / or WPAN.
[0123] The mobile device 1500 may further include sensors 1540. Such sensors may include, but are not limited to, one or more inertial sensors (e.g., accelerometer(s), gyroscope(s), and or other inertial measurement units (IMUs)), cameras(s), magnetometer(s), compasses, altimeter(s), microphone(s), proximity sensor(s), light sensor(s), barometer(s), etc., some of which may be used to supplement and / or facilitate the functionality described herein.
[0124] Embodiments of the mobile device 1500 may also include a GNSS receiver 1580 that is capable of receiving signals 1584 from one or more GNSS satellites (e.g., SV 190) using a GNSS antenna 1582 (which may be combined with antenna(s) 1532 in some implementations). Such positioning may be used to supplement and / or incorporate the techniques described herein. The GNSS receiver 1580 may extract the location of the mobile device 1500 from a GNSS SV (e.g., SV 190) of a GNSS system (such as the Global Positioning System (GPS), Galileo, GLONASS, Compass, the Quasi-Zenith Satellite System (QZSS) over Japan, the Indian Regional Navigation Satellite System (IRNSS) over India, BeiDou over China, etc.) using conventional techniques. In addition, the GNSS receiver 1580 may use various augmentation systems (e.g., satellite-based augmentation systems (SBAS)) that may be associated with or otherwise enabled for use with one or more global and / or regional navigation satellite systems. By way of example and not limitation, SBAS may include augmentation systems that provide integrity information, differential corrections, etc., such as, for example, Wide Area Augmentation System (WAAS), European Geostationary Navigation Overlay Service (EGNOS), Multipurpose Satellite Augmentation System (MSAS), GPS-Assisted Geo-Augmented Navigation, or GPS and Geo-Augmented Navigation System (GAGAN), etc. Thus, as used herein, GNSS may include any combination of one or more global and / or regional navigation satellite systems and / or augmentation systems, and GNSS signals may include GNSS, GNSS-like, and / or other signals associated with such one or more GNSS.
[0125] Mobile device 1500 may further include and / or be in communication with memory 1560. Memory 1560 may include, but is not limited to, local and / or network accessible storage, disk drives, drive arrays, optical storage devices, solid-state storage devices such as random access memory ("RAM") and / or read-only memory ("ROM"), which may be programmable, flash-updatable, etc. Such storage devices may be configured to implement any appropriate data storage, including but not limited to various file systems, database structures, and / or the like.
[0126] The memory 1560 of the mobile device 1500 may also include software elements (not shown), including operating systems, device drivers, executable libraries, and / or other code (such as one or more applications), which may include computer programs provided by various embodiments, and / or may be designed to implement methods provided by other embodiments, and / or configure systems provided by other embodiments, as described herein. By way of example only, one or more of the procedures described with respect to the functionality discussed above may be implemented as code and / or instructions that may be executed by the mobile device 1500 (e.g., using the processing unit(s) 1510). In one aspect, such code and / or instructions may then be used to configure and / or adapt a general purpose computer (or other device) to perform one or more operations according to the described methods.
[0127] Fig.16 An embodiment of system 1600 is illustrated, which can be described above (e.g., in connection with Figures 1 to 13 ) is utilized as described. The components of system 1600 are used to implement a base station. Additionally or alternatively, components of a computer system, such as Figure 1 For example, the system 1600 may perform one or more of the functions of the above-described processes. It should be noted that Fig.16 It is intended only to provide a generalized description of the various components, any or all of which may be utilized as appropriate. In some embodiments, the base station formed by the components of system 1600 may correspond to a gNB, ng-eNB, and / or eNB, as described herein above.
[0128] System 1600 is shown as including hardware elements that may be electrically coupled (or may otherwise be in communication as appropriate) via bus 1605. The hardware elements may include a processing unit 1610, which may include, but is not limited to, one or more general-purpose processors, one or more special-purpose processors (such as DSP chips, graphics acceleration processors, ASICs, etc.), and / or other processing structures or devices. Fig.16 As shown in , some embodiments may have a separate DSP 1620 depending on the desired functionality. According to some embodiments, location determination and / or other determinations based on wireless communications may be provided in the processing unit(s) 1610 and / or the wireless communication interface 1630 (discussed below). The system 1600 may also include one or more input devices, which may include but are not limited to a keyboard, display, mouse, microphone, keys, dials, switches, etc., and one or more output devices, which may include but are not limited to a display, light emitting diodes (LEDs), speakers, etc.
[0129] The system 1600 may also include a wireless communication interface 1630, which may include but is not limited to a modem, a network card, an infrared communication device, a wireless communication device and / or a chipset (such as Devices, IEEE 802.11 devices, IEEE 802.15.4 devices, Wi-Fi devices, WiMAX devices, cellular communication facilities, etc.), etc., which can enable the system 1600 to communicate as described herein. The wireless communication interface 1630 can permit communication (e.g., transmission and reception) of data and signaling to UEs, other base stations (e.g., eNBs, gNBs, and / or ng-eNBs), and / or other network components, computer systems, and / or any other electronic devices described herein. Communication can be performed via one or more wireless communication antennas 1632 that send and / or receive wireless signals 1634.
[0130] The system 1600 may also include a network interface 1680, which may include support for wired communication technologies. The network interface 1680 may include a modem, a network card, a chipset, etc. The network interface 1680 may include one or more input and / or output communication interfaces to permit data to be exchanged with a network, a communication network server, a computer system, and / or any other electronic device described herein.
[0131] In many embodiments, the system 1600 will further include a memory 1660. The memory 1660 may include, but is not limited to, local and / or network accessible storage, disk drives, drive arrays, optical storage devices, solid-state storage devices (such as RAM and / or ROM), which may be programmable, flash-updatable, etc. Such storage devices may be configured to implement any appropriate data storage, including but not limited to various file systems, database structures, and / or the like.
[0132] The memory 1660 of the system 1600 may also include software components ( Fig.161600 (and / or the processing unit(s) 1610 or DSP 1620 within the system 1600). In one aspect, such code and / or instructions may then be used to configure and / or adapt a general purpose computer (or other device) to perform one or more operations according to the described methods.
[0133] Fig.17 A diagram of a communication system 1700 according to at least one embodiment is shown. The communication system 1700 may be configured to determine the location of a UE 1705 by implementing one or more positioning methods using access nodes 1710, 1714, 1716 and / or a location server (LMF 1720). Here, the communication system 1700 includes a UE 1705, and components of a 5G network, including a next generation (NG) radio access network (RAN) (NG-RAN) 1735 and a 5G core network (5GC) 1740. A 5G network may also be referred to as an NR network; NG-RAN 1735 may be referred to as a 5G RAN or NR RAN; and 5GC 1740 may be referred to as an NG core network (NGC). Standardization of NG-RAN and 5GC is being conducted in the Third Generation Partnership Project (3GPP). Accordingly, NG-RAN 1735 and 5GC 1740 may follow current or future standards for 5G support from 3GPP. The communication system 1700 may further utilize information from a satellite vehicle (SV) 1790 of a global navigation satellite system (GNSS) such as GPS, GLONASS, Galileo, or BeiDou, or some other local or regional satellite positioning system (SPS) such as IRNSS, EGNOS, or WAAS. Additional components of the communication system 1700 are described below. The communication system 1700 may include additional or alternative components.
[0134] It should be noted that Fig.17Only a generalized explanation of the various components is provided, any or all of which may be utilized as appropriate, and each component may be repeated or omitted as desired. Specifically, although only one UE 1705 is illustrated, it will be understood that many UEs (e.g., hundreds, thousands, millions, etc.) may utilize the communication system 1700. Similarly, the communication system 1700 may include a larger (or smaller) number of SVs 1790, gNBs 1710, ng-eNBs 1714, WLANs 1716, AMFs 1715, external clients 1730, and / or other components. The illustrated connections connecting the various components in the communication system 1700 include data and signaling connections, which may include additional (intermediate) components, direct or indirect physical and / or wireless connections, and / or additional networks. In addition, the components may be rearranged, combined, separated, replaced, and / or omitted depending on the desired functionality.
[0135] UE 1705 may include and / or be referred to as a device, a mobile device, a wireless device, a mobile terminal, a terminal, a mobile station (MS), a SUPL-enabled terminal (SET), or some other name. In addition, UE 1705 may correspond to a cellular phone, a smart phone, a laptop computer, a tablet device, a PDA, a tracking device, a navigation device, an Internet of Things (IoT) device, or some other portable or removable device. Typically, although not necessarily, UE 1705 may use one or more RATs (such as using GSM, code division multiple access (CDMA), wideband CDMA (WCDMA), LTE, high rate packet data (HRPD), IEEE 802.11 WiFi (also known as Wi-Fi), Bluetooth (BT), Worldwide Interoperability for Microwave Access (WiMAX), 5G New Radio (NR) (e.g., using NG-RAN 1735 and 5GC 1740), etc.) to support wireless communication. UE 1705 may also support wireless communication using WLAN, which may be connected to other networks (e.g., the Internet) using, for example, a digital subscriber line (DSL) or a packet cable. Using one or more of these RATs may allow UE 1705 (via Fig.17 Elements of the 5GC 1740 not shown, or it is possible to communicate with the external client 1730 via the Gateway Mobile Location Center (GMLC) 1725) and / or allow the external client 1730 to receive location information about the UE 1705 (e.g., via the GMLC 1725).
[0136] UE 1705 may include a single entity or may include multiple entities, such as in a personal area network in which a user may employ audio, video, and / or data I / O devices, and / or body sensors and separate wired or wireless modems. The location estimate of UE 1705 may be referred to as a location, location estimate, location fix, fix, position fix, position estimate, or position fix, and may be geographic, thereby providing location coordinates (e.g., latitude and longitude) about UE 1705, which may or may not include an altitude component (e.g., altitude; height above or depth below ground level, floor level, or basement level). Alternatively, the location of UE 1705 may be expressed as a municipal location (e.g., expressed as a postal address or a designation of a point or smaller area in a building (such as a specific room or floor)). The location of UE 1705 may also be expressed as an area or volume (geographically or municipally defined) within which UE 1705 is expected to be located with a certain probability or confidence (e.g., 67%, 95%, etc.). The location of the UE 1705 may further be a relative location, including, for example, a distance and direction or relative X, Y (and Z) coordinates defined relative to some origin at a known location, which may be defined geographically, in municipal form, or with reference to a point, area, or volume indicated on a map, floor plan, or building plan. In the description contained herein, the use of the term location may include any of these variations unless otherwise indicated. When calculating the location of the UE, local x, y, and possibly z coordinates are typically solved, and the local coordinates are then converted to absolute coordinates (e.g., with respect to latitude, longitude, and altitude above or below mean sea level) as needed.
[0137] Fig.17 The base stations (BSs) in the NG-RAN 1735 shown in FIG. 1 include gNRs 1710-1 and 1710-2 (collectively and generally referred to herein as gNBs 1710). The paired gNBs 1710 in the NG-RAN 1735 may be connected to each other—for example, as Fig.17 1705 or indirectly via other gNBs 1710. Access to the 5G network is provided to the UE 1705 via wireless communications between the UE 1705 and one or more gNBs 1710, which may use 5G NR to provide wireless communications access to the 5GC 1740 on behalf of the UE 1705. 5G NR radio access may also be referred to as NR radio access or 5G radio access. Fig.17, it is assumed that the serving gNB for UE 1705 is gNB 1710-1, although other gNBs (e.g., gNB 1710-2) may serve as serving gNBs if UE 1705 moves to another location, or may serve as secondary gNBs to provide additional throughput and bandwidth to UE 1705.
[0138] Fig.17 The base stations (BSs) in the NG-RAN 1735 shown in the figure may also additionally or alternatively include a next generation evolved Node B (also referred to as ng-eNB) 1714. The ng-eNB 1714 may be connected to one or more gNBs 1710 in the NG-RAN 1735—for example, directly or indirectly via other gNBs 1710 and / or other ng-eNBs. The ng-eNB 1714 may provide LTE wireless access and / or evolved LTE (eLTE) wireless access to the UE 1705. Fig.17 Some gNBs 1710 (e.g., gNB 1710-2) and / or ng-eNBs 1714 in the UE 1705 may be configured to function as positioning-only beacons that may transmit signals (e.g., PRS signals) and / or may broadcast assistance data to assist in positioning of the UE 1705, but may not receive signals from the UE 1705 or from other UEs. Fig.17 Only one ng-eNB 1714 is shown in the figure, but some embodiments may include multiple ng-eNB 1714.
[0139] The communication system 1700 may also include one or more WLANs 1716, which may be connected to a non-3GPP interworking function (N3IWF) 1750 in the 5GC 1740. For example, the WLAN 1716 may support IEEE 802.11 WiFi access for the UE 1705 and may include one or more WiFi APs. Here, the N3IWF 1750 may be connected to other elements in the 5GC 1740, such as the AMF 1715. In some embodiments, the WLAN 1716 may support another RAT, such as Bluetooth. The N3IWF 1750 may provide support for secure access by the UE 1705 to other elements in the 5GC 1740 and / or may support interworking of one or more protocols used by the WLAN 1716 and the UE 1705 with one or more protocols used by other elements of the 5GC 1740 (such as the AMF 1715). For example, the N3IWF 1750 may support: establishing an IPsec tunnel with the UE 1705, terminating the IKEv2 / IPsec protocol with the UE 1705, terminating the N2 and N3 interfaces to the 5GC 1740 for the control plane and the user plane, respectively, and relaying uplink and downlink control plane NAS (N1) signaling between the UE 1705 and the AMF 1715. In some other embodiments, the WLAN 1716 may be directly connected to an element in the 5GC 1740 (e.g., the AMF 1715) without passing through the N3IWF 1750 - for example, when the WLAN 1716 is a trusted WLAN for the 5GC 1740. Note that although in Fig.17 Only one WLAN 1716 is shown in FIG. 1 , but some embodiments may include multiple WLANs 1716 .
[0140] As referred to herein, an access node may include any of a variety of network entities that enable communication between a UE 1705 and an AMF 1715. This may include a gNB 1710, an ng-eNB 1714, a WLAN 1716, and / or other types of cellular base stations. However, an access node providing the functionality described herein may additionally or alternatively include a cellular network entity that enables communication with a UE 1705 and an AMF 1715. Fig.17 1714, or WLAN 1716.
[0141] As will be discussed in more detail below, in some embodiments, gNB 1710, ng-eNB 1714, and / or WLAN 1716 (alone or in combination with other modules / elements of communication system 1700) may be configured to, in response to receiving a request for location information for multiple RATs from LMF 1720, perform measurements (e.g., measurements of UE 1705) using one of the multiple RATs and / or obtain measurements performed using one or more of the multiple RATs from UE 1705. As mentioned, although Fig.17 Nodes 1710, 1714, 1716 configured to communicate according to 5G NR, LTE, and Wi-Fi communication protocols are depicted, but nodes configured to communicate according to other communication protocols such as, for example, LTE protocol for UMTS Terrestrial Radio Access Network (E-UTRAN) or Bluetooth protocol for WLAN may also be used. For example, in a 4G Evolved Packet System (EPS) providing LTE wireless access to UE 1705, the RAN may include E-UTRAN, which may include base stations with evolved Node Bs (eNBs) supporting LTE wireless access. The core network for EPS may include an Evolved Packet Core (EPC). EPS may include E-UTRAN plus EPC, where Fig.17 In the example, E-UTRAN corresponds to NG-RAN 1735 and EPC corresponds to 5GC 1740. The methods and techniques described herein for positioning UE 1705 using a common or universal positioning procedure may be applicable to such other networks.
[0142] The gNB 1710 and ng-eNB 1714 may communicate with the AMF 1715, which communicates with the LMF 1720 for positioning functionality. The AMF 1715 may support mobility of the UE 1705, including cell changes and handovers, including handovers from an access node 1710, 1714, or 1716 of a first RAT to an access node 1710, 1714, or 1716 of a second RAT. The AMF 1715 may also be involved in supporting signaling connections to the UE 1705 and possibly supporting data and voice bearers for the UE 1705. LMF 1720 may support positioning of UE 1705 when UE accesses NG-RAN 1735 or WLAN 1716, and may support various positioning procedures / methods, including UE-assisted / UE-based, and / or / network-based procedures / methods, such as Assisted GNSS (A-GNSS), OTDOA, Real-time Kinematics (RTK), Precise Point Positioning (PPP), Differential GNSS (DGNSS), ECID, OTDOA, Angle of Arrival (AOA), Angle of Departure (AOD), WLAN positioning, and / or other positioning procedures. LMF 1720 may also process location service requests for UE 1705 received, for example, from AMF 1715 or from GMLC 1725. LMF 1720 may be connected to AMF 1715 and / or GMLC 1725. LMF 1720 may be referred to by other names, such as Location Manager (LM), Location Function (LF), Commercial LMF (CLMF), or Value-Added LMF (VLMF). In some embodiments, a node / system implementing LMF 1720 may additionally or alternatively implement other types of location support modules, such as E-SMLC. It should be noted that in some embodiments, at least a portion of the positioning functionality (including determining the location of UE 1705) may be performed at UE 1705 (e.g., using signal measurements obtained by UE 1705 for signals transmitted by wireless nodes (such as gNB 1710, ng-eNB 1714 and / or WLAN 1716) and / or assistance data provided to UE 1705 by LMF 1720, for example).
[0143] A Gateway Mobile Location Center (GMLC) 1725 may support location requests for UE 1705 received from external clients 1730 and may forward such location requests to AMF 1715 for forwarding by AMF 1715 to LMF 1720, or may forward the location requests directly to LMF 1720. A location response (e.g., containing a location estimate for UE 1705) from LMF 1720 may similarly be returned to GMLC 1725 directly or via AMF 1715, and GMLC 1725 may then return the location response (e.g., containing the location estimate) to external clients 1730. GMLC 1725 is shown connected to Fig.17 Both the AMF 1715 and the LMF 1720 in the 5GC, but in some implementations only one of these connections may be supported by the 5GC 1740.
[0144] like Fig.17 As further explained in , LMF 1720 may communicate with gNB 1710 and / or with ng-eNB 1714 using NRPPa (which may also be referred to as NPPa), which may be defined in 3GPP Technical Specification (TS) 38.455. NRPPa may be the same as, similar to, or an extension of LTE Positioning Protocol A (LPPa) defined in 3GPP TS 36.455, where NRPPa messages are passed between gNB 1710 and LMF 1720 via AMF 1715, and / or between ng-eNB 1714 and LMF 1720. Fig.17As further explained in , LMF 1720 and UE 1705 may communicate using the LPP protocol, which may be defined in 3GPP TS 36.355. LMF 1720 and UE 1705 may also or instead communicate using the NPP protocol, which may be the same as, similar to, or an extension of the LPP. Here, LPP and / or NPP messages may be passed between UE 1705 and LMF 1720 via AMF 1715 and a serving gNB 1710-1 or serving ng-eNB 1714 for UE 1705. For example, LPP and / or NPP messages may be passed between LMF 1720 and AMF 1715 using a 5G location service application protocol (LCS AP), and may be passed between AMF 1715 and UE 1705 using a 5G non-access stratum (NAS) protocol. The LPP and / or NPP protocols may be used to support positioning of UE 1705 using UE-assisted and / or UE-based positioning methods such as A-GNSS, RTK, OTDOA, and / or ECID. The NRPPa protocol may be used to support positioning of UE 1705 using network-based positioning methods such as ECID (e.g., in conjunction with measurements obtained by gNB 1710 or ng-eNB 1714) and / or may be used by LMF 1720 to obtain location-related information from gNB 1710 and / or ng-eNB 1714, such as parameters defining PRS transmissions from gNB 1710 and / or ng-eNB 1714.
[0145] In the case where UE 1705 accesses WLAN 1716, LMF 1720 may use NRPPa and / or LPP / NPP to obtain the location of UE 1705 in a manner similar to that just described for UE 1705 accessing gNB 1710 or ng-eNB 1714. Thus, NRPPa messages may be passed between WLAN 1716 and LMF 1720 via AMF 1715 and N3IWF 1750 to support network-based positioning of UE 1705 and / or to pass other location information from WLAN 1716 to LMF 1720. Similarly, LPP and / or NPP messages may be passed between UE 1705 and LMF 1720 via AMF 1715, N3IWF 1750, and serving WLAN 1716 of UE 1705 to support UE-assisted or UE-based positioning of UE 1705 through LMF 1720.
[0146] Using UE-assisted positioning methods, UE 1705 may obtain location measurements and send the measurements to a location server (e.g., LMF 1720) to calculate a location estimate for UE 1705. For example, the location measurements may include one or more of: received signal strength indication (RSSI), round-trip signal propagation time (RTT), reference signal time difference (RSTD), reference signal received power (RSRP), and / or reference signal received quality (RSRQ) of an access point (AP) of gNB 1710, ng-eNB 1714, and / or WLAN 1716. The location measurements may additionally or alternatively include measurements of GNSS pseudoranges, code phases, and / or carrier phases of SV 1790. Using UE-based positioning methods, UE 1705 can obtain position measurements (e.g., which can be the same or similar to position measurements of UE-assisted positioning methods) and can calculate the position of UE 1705 (e.g., with the help of assistance data received from a location server (such as LMF 1720) or broadcast by gNB 1710, ng-eNB 1714, or WLAN 1716). Using network-based positioning methods, one or more base stations (e.g., gNB 1710 and / or ng-eNB 1714) or APs (e.g., in WLAN 1716) can obtain position measurements of signals transmitted by UE 1705 (e.g., RSSI, RTT, RSRP, RSRQ, AOA, or arrival time (TOA) measurements) and / or can receive measurements obtained by UE 1705, and can send these measurements to a location server (e.g., LMF 1720) to calculate a position estimate for UE 1705.
[0147] The information provided to LMF 1720 by gNB 1710 and / or ng-eNB 1714 using NRPPa may include timing and configuration information for PRS transmission and location coordinates. LMF 1720 may then provide some or all of this information to UE 1705 as assistance data in LPP and / or NPP messages via NG-RAN 1735 and 5GC 1740.
[0148] The LPP or NPP message sent from the LMF 1720 to the UE 1705 may instruct the UE 1705 to perform any of a variety of operations, depending on the desired functionality. For example, the LPP or NPP message may include instructions for the UE 1705 to obtain measurements for GNSS (or A-GNSS), WLAN, and / or OTDOA (or some other positioning method). In the case of OTDOA, the LPP or NPP message may instruct the UE 1705 to obtain one or more measurements (e.g., RSTD measurements) of PRS signals transmitted within a particular cell supported by a particular gNB 1710 and / or ng-eNB 1714 (or supported by some other type of base station (such as an eNB or Wi-Fi AP)). The RSTD measurement may include the time difference between a signal (e.g., a PRS signal) transmitted or broadcast by one gNB 1710 and a similar signal transmitted by another gNB 1710 arriving at the UE 1705. The UE 1705 may send these measurements back to the LMF 1720 via the serving gNB 1710-117 (or serving ng-eNB 1714) and the AMF 1715 in an LPP or NPP message (e.g., within a 5G NAS message).
[0149] As mentioned, although the communication system 1700 is described with respect to 5G technology, the communication system 1700 may be implemented to support other communication technologies (such as GSM, WCDMA, LTE, etc.) that are used to support and interact with mobile devices (such as UE 1705) (e.g., to implement voice, data, positioning, and other functionality). In some such embodiments, the 5GC 1740 may be configured to control different air interfaces. For example, in some embodiments, both the NG-RAN 1735 and the 5GC 1740 may be replaced by other RANs and other core networks. For example, in the EPS, the NG-RAN 1735 may be replaced by an E-UTRAN including eNBs, and the 5GC 1740 may be replaced by an EPC including a mobility management entity (MME) instead of the AMF 1715, an E-SMLC instead of the LMF 1720, and a GMLC that may be similar to the GMLC 1725. In such EPS, the E-SMLC may use LPPa instead of NRPPa to send and receive location information to and from the eNB in the E-UTRAN, and may use LPP to support positioning of the UE 1705. In these other embodiments, on-demand resource allocation for positioning of the UE 1705 may be supported in a manner similar to that described herein for the 5G network, except that the functions and procedures described herein for the gNB 1710, ng-eNB 1714, AMF 1715, and LMF 1720 may be applied alternatively to other network elements, such as eNB, Wi-Fi AP, MME, and E-SMLC in some cases.
[0150] To support certain positioning methods such as OTDOA and transmissions or PRS or other signals used in locating the UE 1705, the base stations may be synchronized. In a synchronized network, the transmission timing of the gNBs 1710 may be synchronized so that each gNB 1710 has the same transmission timing as every other gNB 1710 to a high level of accuracy (e.g., 50 nanoseconds or less). Alternatively, the gNBs 1710 may be synchronized at the radio frame or subframe level so that each gNB 1710 transmits a radio frame or subframe during the same time duration as every other gNB 1710 (e.g., so that each gNB 1710 begins and ends transmitting a radio frame or subframe almost exactly at the same time as every other gNB 1710), but without necessarily maintaining the same count value or number for the radio frames or subframes. For example, while one gNB 1710 is transmitting a subframe or radio frame with a count value or number zero (which may be the first radio frame or subframe in a periodically repeating sequence of radio frames or subframes), another gNB 1710 may be transmitting a radio frame or subframe with a different number or count value (such as one, ten, one hundred, etc.).
[0151] Synchronization of the transmission timing of the ng-eNB 1714 in the NG-RAN 1735 may be supported in a manner similar to the synchronization of the gNB 1710, but because the ng-eNB 1714 will typically use a different frequency than the gNB 1710 (to avoid interference), the ng-eNB 1714 may not always be synchronized to the gNB 1710. Synchronization of the gNB 1710 and ng-eNB 1714 may be achieved using a GPS receiver or a GNSS receiver in each of the gNB 1710 and ng-eNB 1714 or by other means, such as using the IEEE 1588 Precision Time Protocol.
[0152] Although the present subject matter has been described in detail with respect to specific embodiments thereof, it will be appreciated that changes, variations, and equivalents to such embodiments may be readily made by those skilled in the art upon gaining an understanding of the foregoing. Accordingly, it will be understood that the present disclosure is presented for purposes of illustration and not limitation, and does not exclude the inclusion of such modifications, variations, and / or additions to the present subject matter as will be apparent to one of ordinary skill in the art. In fact, the methods and systems described herein may be embodied in a variety of other forms; furthermore, various omissions, substitutions, and changes may be made to the form of the methods and systems described herein without departing from the spirit of the present disclosure. The appended claims and their equivalents are intended to cover such forms or modifications that fall within the scope and spirit of the present disclosure.
[0153] Unless specifically stated otherwise, it should be understood that discussions throughout this specification utilize terms such as "processing," "computing," "calculating," "determining," and "identifying" to refer to the actions or processes of a computing device (such as one or more computers or similar electronic computing devices) that manipulate or transform data represented as physical electronic or magnetic quantities within a computing platform's memory, registers, or other information storage devices, transmission devices, or display devices.
[0154] The one or more systems discussed herein are not limited to any particular hardware architecture or configuration. A computing device may include any suitable arrangement of components that provide a result conditioned on one or more inputs. Suitable computing devices include multi-purpose computing devices based on microprocessors that access stored software that programs or configures a portable device from a general-purpose computing device to a dedicated computing device that implements one or more embodiments of the subject matter. Any suitable programming, scripting, or other type of language or combination of languages may be used to implement the teachings contained herein in the software to be used by programming or configuring a computing device.
[0155] Embodiments of the methods disclosed herein may be performed in the operation of such computing devices. The order of the blocks presented in the above examples may be changed—for example, the blocks may be reordered, combined, and / or decomposed into sub-blocks. Certain blocks or processes may be performed in parallel.
[0156] Conditional language used herein, such as "may," "might," "could," "can," "e.g.," and the like, unless specifically stated otherwise or otherwise understood in the context of use, is generally intended to convey that certain examples include and other examples do not include certain features, elements, and / or steps. Thus, such conditional language generally does not imply that one or more examples in any way require these features, elements, and / or steps, or that one or more examples must include logic for deciding (with or without author input or prompting) whether these features, elements, and / or steps are included or will be performed in any particular example.
[0157] The terms "include", "comprise", "have", etc. are synonymous and are used inclusively in an open manner, and do not exclude additional elements, features, actions, operations, etc. Moreover, the term "or" is used in an inclusive manner (rather than an exclusive manner), so that, for example, when used to connect the elements of a list, the term "or" represents one, some or all of the elements in the list. "Adapted to" or "configured to" used herein means open and inclusive language, which does not exclude that the device is adapted to or configured to perform additional tasks or steps. In addition, the use of "based on" means openness and inclusiveness, because the process, step, calculation or other action "based on" one or more listed conditions or values can actually be based on additional conditions or values beyond the listed conditions or values. Similarly, the use of "based at least in part" means openness and inclusiveness, because the process, step, calculation or other action "based at least in part" on one or more listed conditions or values can actually be based on additional conditions or values beyond the listed conditions or values. The titles, lists and numbers included herein are only for ease of explanation and are not meant to be limited.
[0158] The various features and processes described above can be used independently of each other, or can be combined in various ways. All possible combinations and sub-combinations are intended to fall within the scope of the present disclosure. In addition, some methods or process blocks can be omitted in some implementations. The methods and processes described herein are not limited to any particular order, and the blocks or states related thereto can be performed in other appropriate orders. For example, the described blocks or states can be performed in an order different from that specifically disclosed, or multiple blocks or states can be combined in a single block or state. Example blocks or states can be performed in serial, parallel or in some other manner. Blocks or states can be added to or removed from the disclosed examples. Similarly, the example systems and components described herein can be configured to be different from those described. For example, compared with the disclosed examples, elements can be added, removed or rearranged.
[0159] In view of this description, various embodiments may include different combinations of features. Various implementation examples are described in the following numbered clauses.
[0160] Item 1: A method for locating a mobile device within a coverage area of a serving cell in communication with the mobile device, the method being implemented by the mobile device and comprising: receiving cell identity data, the cell identity data comprising one or more cell identities; and determining a coverage sub-area of the coverage area of the serving cell based on using the cell identity data in a search of a data structure, the data structure associating each coverage sub-area of the coverage area with each cell identity, each coverage sub-area of each coverage sub-area being associated in the data structure with the cell identity of the serving cell, and at least one of the coverage sub-areas being further associated in the data structure with the cell identity of a neighboring cell; and determining a position of the mobile device, the position being within the coverage sub-area of the coverage area of the serving cell.
[0161] Clause 2: The method of clause 1, further comprising: sending the cell identity data to a computer system, wherein the computer system stores the data structure, and wherein determining the location of the mobile device comprises receiving the location from the computer system.
[0162] Clause 3: The method of any of clauses 1-2, further comprising: storing the data structure in a memory of the mobile device; and performing a lookup of the data structure from the memory.
[0163] Clause 4: The method of clause 1 further comprises: sending the cell identity of the serving cell to a computer system, wherein the computer system stores a corresponding data structure for each cell among a plurality of cells that divides the coverage area of the corresponding cell into coverage sub-areas; and receiving the data structure corresponding to the serving cell from the computer system based on the cell identity of the serving cell.
[0164] Clause 5: The method of any one of clauses 1-4, further comprising: before receiving the cell identity data: determining, by a location sensor of the mobile device, location data indicating a second location of the mobile device within the coverage area of the serving cell; receiving second cell identity data including the cell identity of the serving cell and the cell identity of the neighboring cell; and sending the location data and the second cell identity data to a computer system, wherein the data structure is generated by the computer system based on the location data and the second cell identity data.
[0165] Clause 6: A method as in any of clauses 1-5, wherein: the data structure represents a mapping that (i) divides the coverage area of the serving cell into coverage sub-areas, (ii) maps each of the coverage sub-areas to a set of cell identities, and (iii) indicates the location of the mobile device as a possible location within each of the coverage sub-areas, wherein the possible location for each of the coverage sub-areas is determined based on location data collected from the multiple mobile devices when the multiple mobile devices are located in the corresponding coverage sub-areas.
[0166] Clause 7: The method of any of clauses 1-6, wherein: the mapping is associated with at least one of: a mobile network operator, a frequency channel, or a radio access technology.
[0167] Clause 8: A method as in clause 7, wherein: the coverage sub-area associated with the cell identity of the neighbor cell is further associated with a possible location, wherein the cell identity data includes the cell identity of the neighbor cell, and wherein the location is the possible location.
[0168] Clause 9: The method of any of clauses 1-8, wherein: the data structure further associates a coverage sub-area of the coverage area with a beam index of the serving cell, a beam index of the neighbor cell, or both.
[0169] Clause 10: A method as described in any of clauses 1-9, wherein: the coverage area is associated with a first possible location, wherein a coverage sub-area associated with the cell identity of the neighbor cell is further associated with a second possible location, wherein the cell identity data includes the cell identity of the neighbor cell, and wherein the location is within the coverage sub-area associated with the cell identity of the neighbor cell and includes a possible location determined based on the first possible location and the second possible location.
[0170] Clause 11: A method as in any of clauses 1-10, wherein: the coverage sub-area of the serving cell includes a plurality of unique non-overlapping coverage sub-areas, wherein the data structure associates each of the unique non-overlapping coverage sub-areas with the serving cell and with a set of unique neighbor cells.
[0171] Clause 12: The method of clause 11, wherein: the unique non-overlapping coverage sub-area comprises: a first coverage sub-area associated with the serving cell and the neighbor cell and a second coverage sub-area associated with the serving cell and not associated with the neighbor cell.
[0172] Clause 13: A method as in clause 11, wherein: the second coverage sub-area is defined based on first data of a first plurality of mobile devices, wherein the third coverage sub-area is defined based on second data of a second plurality of mobile devices, wherein the first data includes a first mobile device location and a cell identity of the neighbor cell, wherein the first data excludes a cell identity of another neighbor cell, and wherein the second data includes a second mobile device location, a cell identity of the neighbor cell, and a cell identity of the other neighbor cell.
[0173] Clause 14: A method as in any of clauses 1 or 8-11, wherein: the data structure represents a mapping that (i) divides the coverage area of the serving cell into coverage sub-areas, and (ii) constrains the boundaries of each of the coverage sub-areas to be within the boundaries of the coverage area.
[0174] Clause 15: A method as in any of clauses 1 or 8-11, wherein: the data structure represents a mapping that (i) divides the coverage area of the serving cell into coverage sub-areas, and (ii) constrains possible mobile device locations within each of the coverage sub-areas to be within the coverage area.
[0175] Clause 16: The method of any of clauses 1 or 8-11, wherein: the data structure represents a mapping that divides the coverage area of the serving cell into coverage sub-areas, and wherein the coverage sub-areas are non-overlapping.
[0176] Clause 17: A method as described in any of clauses 1-16, wherein: the neighbor cell includes: a cell that is different from the serving cell and on the same frequency channel as the serving cell, a cell on a frequency channel different from the serving cell, a cell on a different radio access technology (RAT) using the same frequency channel as the serving cell, or a cell on a different RAT using a frequency channel different from the serving cell.
[0177] Clause 18: A method for determining cell coverage based on crowdsourced information received at a cellular entity of a data communications network, the method comprising: obtaining, at the cellular entity, cell identity data and location data for a plurality of locations within a coverage area of a serving cell, wherein the cellular entity comprises a mobile device or a computer system, and wherein, for each location: the location data comprises a corresponding location, and the cell identity data comprises one or more cell identities detected at corresponding locations of one or more mobile devices; storing the location data and the cell identity data using the cellular entity; and associating, by the cellular entity, coverage sub-areas of the coverage area with cell identities based on the cell identity data and the location data using a data structure, wherein: each of the coverage sub-areas is associated with the cell identity of the serving cell in the data structure, and at least one of the coverage sub-areas is further associated with the cell identity of a neighbor cell in the data structure.
[0178] Clause 19: The method of clause 18, further comprising: storing, for each cell of the plurality of cells, a corresponding data structure dividing a coverage area of the respective cell into coverage sub-areas.
[0179] Clause 20: The method of any of clauses 18-19, wherein: for at least one location of the plurality of locations, the cell identity data comprises a cell identity of the serving cell and a cell identity of at least one neighbor cell.
[0180] Clause 21: A method as in any of clauses 18-20, wherein: the data structure represents a mapping that (i) divides the coverage area of the serving cell into coverage sub-areas, (ii) maps each coverage sub-area to a set of cell identities, and (iii) indicates the location of a target mobile device as a possible location within the coverage sub-area, wherein the possible location is determined based on location data collected from the one or more mobile devices when the one or more mobile devices are located in the coverage sub-area.
[0181] Clause 22: The method of clause 21, wherein: the mapping is associated with at least one of: a mobile network operator, a frequency channel, or a radio access technology.
[0182] Clause 23: A method as in any of clauses 18-22, wherein: the coverage sub-area associated with the cell identity of the neighbor cell is further associated with a possible location, wherein the cell identity data includes the cell identity of the neighbor cell, and wherein the location is the possible location.
[0183] Clause 24: A method as in any of clauses 18-22, wherein: the coverage area is associated with a first possible location, wherein a coverage sub-area associated with the cell identity of the neighbor cell is further associated with a second possible location, wherein the cell identity data includes the cell identity of the neighbor cell, and wherein the location is within the coverage sub-area associated with the cell identity of the neighbor cell and includes a possible location determined based on the first possible location and the second possible location.
[0184] Clause 25: A method as in any of clauses 18-22, wherein: the coverage sub-area of the serving cell comprises a plurality of unique non-overlapping coverage sub-areas, wherein the data structure associates each of the unique non-overlapping coverage sub-areas with the serving cell and with a set of unique neighbor cells.
[0185] Clause 26: A method as in any of clauses 18-25, wherein: the data structure represents a mapping that (i) divides the coverage area of the serving cell into coverage sub-areas, and (ii) constrains the boundaries of each coverage sub-area to be within the boundaries of the coverage area.
[0186] Clause 27: A method as in any of clauses 18-25, wherein: the data structure represents a mapping that (i) divides the coverage area of the serving cell into coverage sub-areas, and (ii) constrains possible mobile device locations within each coverage sub-area to be within the coverage area.
[0187] Clause 28: A method as described in any of clauses 18-27, wherein the neighbor cell includes: a cell that is different from the serving cell and on the same frequency channel as the serving cell, a cell on a frequency channel different from the serving cell, a cell on a different radio access technology (RAT) using the same frequency channel as the serving cell, or a cell on a different RAT using a frequency channel different from the serving cell.
[0188] Clause 29: The method of clause 28, wherein: the data structure further associates a coverage sub-area of the coverage area with a beam index of the serving cell, a beam index of the neighbor cell, or both.
[0189] Item 30: A mobile device for locating the mobile device within a coverage area of a serving cell in communication with the mobile device, the mobile device comprising: a transceiver; a memory; and one or more processing units communicatively coupled to the transceiver and the memory, wherein the one or more processing units are configured to: receive cell identity data via the transceiver, the cell identity data comprising one or more cell identities; and determine a coverage sub-area of the coverage area of the serving cell based on using the cell identity data in a search of a data structure, the data structure associating each coverage sub-area of the coverage area with each cell identity, each coverage sub-area of each coverage sub-area being associated in the data structure with the cell identity of the serving cell, and at least one of the coverage sub-areas being further associated in the data structure with the cell identity of a neighboring cell; and determine the position of the mobile device, the position being within the coverage sub-area of the coverage area of the serving cell.
[0190] Clause 31: The mobile device of clause 30, wherein the one or more processing units are further configured to: send the cell identity data to a computer system, wherein the computer system stores the data structure, and wherein determining the location of the mobile device comprises receiving the location from the computer system.
[0191] Clause 32: The mobile device of any of clauses 30-31, wherein the one or more processing units are further configured to: store the data structure in the memory; and perform a lookup of the data structure from the memory.
[0192] Clause 33: A mobile device as in clause 30, wherein the one or more processing units are further configured to: send the cell identity of the serving cell to a computer system, wherein the computer system stores, for each cell in a plurality of cells, a corresponding data structure that divides the coverage area of the corresponding cell into coverage sub-areas; and receive, from the computer system, the data structure corresponding to the serving cell based on the cell identity of the serving cell.
[0193] Clause 34: A mobile device as in any of clauses 30-33, wherein the one or more processing units are further configured to: before receiving the cell identity data: determine location data indicating a second location of the mobile device within the coverage area of the serving cell; receive second cell identity data including the cell identity of the serving cell and the cell identity of the neighbor cell; and send the location data and the second cell identity data to a computer system, wherein the data structure is generated by the computer system based on the location data and the second cell identity data.
[0194] Clause 35: A mobile device as in any of clauses 30-34, wherein the data structure represents a mapping that (i) divides the coverage area of the serving cell into coverage sub-areas, (ii) maps each of the coverage sub-areas to a set of cell identities, and (iii) indicates the location of the mobile device as a possible location within each of the coverage sub-areas, wherein the possible locations for each of the coverage sub-areas are determined based on location data collected from the multiple mobile devices when the multiple mobile devices are located in the corresponding coverage sub-areas.
[0195] Clause 36: The mobile device of any of clauses 30-35, wherein the mapping is associated with at least one of: a mobile network operator, a frequency channel, or a radio access technology.
[0196] Clause 37: The mobile device of clause 36, wherein the coverage sub-area associated with the cell identity of the neighbor cell is further associated with a possible location, wherein the cell identity data includes the cell identity of the neighbor cell, and wherein the location is the possible location.
[0197] Clause 38: The mobile device of any of clauses 30-37, wherein the data structure further associates a coverage sub-area of the coverage area with a beam index of the serving cell, a beam index of the neighbor cell, or both.
[0198] Clause 39: A mobile device as in any of clauses 30-38, wherein the coverage area is associated with a first possible location, wherein a coverage sub-area associated with the cell identity of the neighbor cell is further associated with a second possible location, wherein the cell identity data includes the cell identity of the neighbor cell, and wherein the location is within the coverage sub-area associated with the cell identity of the neighbor cell and includes a possible location determined based on the first possible location and the second possible location.
[0199] Clause 40: A mobile device as in any of clauses 30-39, wherein the coverage sub-area of the serving cell comprises a plurality of unique non-overlapping coverage sub-areas, wherein the data structure associates each of the unique non-overlapping coverage sub-areas with the serving cell and with a set of unique neighbor cells.
[0200] Clause 41: The mobile device of clause 40, wherein the unique non-overlapping coverage sub-area comprises: a first coverage sub-area associated with the serving cell and the neighbor cell and a second coverage sub-area associated with the serving cell and not associated with the neighbor cell.
[0201] Clause 42: A mobile device as in clause 40, wherein the second coverage sub-area is defined based on first data of a first plurality of mobile devices, wherein the third coverage sub-area is defined based on second data of a second plurality of mobile devices, wherein the first data includes a first mobile device location and a cell identity of the neighbor cell, wherein the first data excludes a cell identity of another neighbor cell, and wherein the second data includes a second mobile device location, a cell identity of the neighbor cell, and a cell identity of the other neighbor cell.
[0202] Clause 43: A mobile device as in any of clauses 30 or 37-40, wherein the data structure represents a mapping that (i) divides the coverage area of the serving cell into coverage sub-areas, and (ii) constrains the boundaries of each of the coverage sub-areas to be within the boundaries of the coverage area.
[0203] Clause 44: A mobile device as in any of clauses 30 or 37-40, wherein the data structure represents a mapping that (i) divides the coverage area of the serving cell into coverage sub-areas, and (ii) constrains possible mobile device locations within each of the coverage sub-areas to be within the coverage area.
[0204] Clause 45: The mobile device of any of clauses 30 or 37-40, wherein the data structure represents a mapping that divides the coverage area of the serving cell into coverage sub-areas, and wherein the coverage sub-areas are non-overlapping.
[0205] Clause 46: A mobile device as described in any of clauses 30-45, wherein the neighbor cell includes: a cell that is different from the serving cell and on the same frequency channel as the serving cell, a cell on a frequency channel different from the serving cell, a cell on a different radio access technology (RAT) using the same frequency channel as the serving cell, or a cell on a different RAT using a frequency channel different from the serving cell.
[0206] Clause 47: A cellular entity of a data communication network, the cellular entity being used to determine cellular cell coverage based on crowdsourced information received at the cellular entity, the cellular entity comprising: a transceiver; a memory; and one or more processing units communicatively coupled to the transceiver and the memory, wherein the one or more processing units are configured to: obtain, at the cellular entity, cellular cell identity data and location data for multiple locations within a coverage area of a serving cellular cell, wherein the cellular entity comprises a mobile device or a computer system, and wherein, for each location: the location data comprises a corresponding location, and the cellular cell identity data comprises one or more cellular cell identities detected at corresponding locations of one or more mobile devices; store the location data and the cellular cell identity data using the cellular entity; and associate each coverage sub-area of the coverage area with each cell identity based on the cell identity data and the location data, wherein: each of the coverage sub-areas is associated with the cell identity of the serving cell in the data structure, and at least one of the coverage sub-areas is further associated with the cell identity of a neighbor cell in the data structure.
[0207] Clause 48: The cellular entity of clause 47, wherein the one or more processing units are further configured to: store, for each cell of the plurality of cells, a corresponding data structure dividing a coverage area of the respective cell into coverage sub-areas.
[0208] Clause 49: The cellular entity of any of clauses 47-48, wherein, for at least one location of the plurality of locations, the cell identity data comprises a cell identity of the serving cell and a cell identity of at least one neighbor cell.
[0209] Clause 50: A cellular entity as in any of clauses 47-49, wherein the data structure represents a mapping that (i) divides the coverage area of the serving cell into coverage sub-areas, (ii) maps each coverage sub-area to a set of cell identities, and (iii) indicates a location of a target mobile device as a possible location within the coverage sub-area, wherein the possible location is determined based on location data collected from the one or more mobile devices when the one or more mobile devices are located in the coverage sub-area.
[0210] Clause 51: The cellular entity of clause 50, wherein the mapping is associated with at least one of: a mobile network operator, a frequency channel, or a radio access technology.
[0211] Clause 52: A cellular entity as in any of clauses 47-51, wherein the coverage sub-area associated with the cell identity of the neighbor cell is further associated with a possible location, wherein the cell identity data comprises the cell identity of the neighbor cell, and wherein the location is the possible location.
[0212] Clause 53: A cellular entity as in any of clauses 47-51, wherein the coverage area is associated with a first possible location, wherein a coverage sub-area associated with the cell identity of the neighbor cell is further associated with a second possible location, wherein the cell identity data includes the cell identity of the neighbor cell, and wherein the location is within the coverage sub-area associated with the cell identity of the neighbor cell and includes a possible location determined based on the first possible location and the second possible location.
[0213] Clause 54: A cellular entity as in any of clauses 47-51, wherein the coverage sub-area of the serving cell comprises a plurality of unique non-overlapping coverage sub-areas, wherein the data structure associates each of the unique non-overlapping coverage sub-areas with the serving cell and with a set of unique neighbor cells.
[0214] Clause 55: A cellular entity as in any of clauses 47-54, wherein the data structure represents a mapping that (i) divides the coverage area of the serving cell into coverage sub-areas, and (ii) constrains the boundaries of each coverage sub-area to be within the boundaries of the coverage area.
[0215] Clause 56: A cellular entity as in any of clauses 47-54, wherein the data structure represents a mapping that (i) divides the coverage area of the serving cell into coverage sub-areas, and (ii) constrains possible mobile device locations within each coverage sub-area to be within the coverage area.
[0216] Clause 57: A cellular entity as described in any of clauses 47-56, wherein the neighbor cell includes: a cell that is different from the serving cell and on the same frequency channel as the serving cell, a cell on a frequency channel different from the serving cell, a cell on a different radio access technology (RAT) using the same frequency channel as the serving cell, or a cell on a different RAT using a frequency channel different from the serving cell.
[0217] Clause 58: The cellular entity of any of clauses 47-57, wherein the data structure further associates a coverage sub-area of the coverage area with a beam index of the serving cell, a beam index of the neighbor cell, or both.
[0218] Item 59: An apparatus for locating a mobile device within a coverage area of a serving cell in communication with the mobile device, the apparatus comprising: a device for receiving cell identity data, the cell identity data comprising one or more cell identities; and a device for determining a coverage sub-area of the coverage area of the serving cell based on using the cell identity data in a search of a data structure, the data structure associating each coverage sub-area of the coverage area with each cell identity, each coverage sub-area of each coverage sub-area being associated in the data structure with the cell identity of the serving cell, and at least one of the coverage sub-areas being further associated in the data structure with the cell identity of a neighboring cell; and a device for determining the position of the mobile device, the position being within the coverage sub-area of the coverage area of the serving cell.
[0219] Clause 60: The apparatus of clause 59, further comprising: means for sending the cell identity data to a computer system, wherein the computer system stores the data structure, and wherein determining the location of the mobile device comprises receiving the location from the computer system.
[0220] Clause 61: The apparatus of any of clauses 59-60, further comprising: means for storing the data structure in a memory of the mobile device; and means for performing a lookup of the data structure from the memory.
[0221] Clause 62: The apparatus of clause 59, further comprising: a device for sending a cell identity of the serving cell to a computer system, wherein the computer system stores, for each cell in a plurality of cells, a corresponding data structure that divides the coverage area of the corresponding cell into coverage sub-areas; and a device for receiving, from the computer system, the data structure corresponding to the serving cell based on the cell identity of the serving cell.
[0222] Clause 63: The apparatus as in any of clauses 59-62, further comprising: before receiving the cell identity data: a device for determining location data indicating a second location of the mobile device within the coverage area of the serving cell; a device for receiving second cell identity data including the cell identity of the serving cell and the cell identity of the neighbor cell; and a device for sending the location data and the second cell identity data to a computer system, wherein the data structure is generated by the computer system based on the location data and the second cell identity data.
[0223] Clause 64: An apparatus as in any of clauses 59-63, wherein the data structure represents a mapping that (i) divides the coverage area of the serving cell into coverage sub-areas, (ii) maps each of the coverage sub-areas to a set of cell identities, and (iii) indicates the location of the mobile device as a possible location within each of the coverage sub-areas, wherein the possible locations for each of the coverage sub-areas are determined based on location data collected from the multiple mobile devices when the multiple mobile devices are located in the corresponding coverage sub-areas.
[0224] Clause 65: The apparatus of any of clauses 59-64, wherein the mapping is associated with at least one of: a mobile network operator, a frequency channel, or a radio access technology.
[0225] Clause 66: The apparatus of clause 65, wherein the coverage sub-area associated with the cell identity of the neighbor cell is further associated with a possible location, wherein the cell identity data comprises the cell identity of the neighbor cell, and wherein the location is the possible location.
[0226] Clause 67: The apparatus of any of clauses 59-66, wherein the data structure further associates a coverage sub-area of the coverage area with a beam index of the serving cell, a beam index of the neighbor cell, or both.
[0227] Clause 68: An apparatus as in any of clauses 59-67, wherein the coverage area is associated with a first possible location, wherein a coverage sub-area associated with the cell identity of the neighbor cell is further associated with a second possible location, wherein the cell identity data includes the cell identity of the neighbor cell, and wherein the location is within the coverage sub-area associated with the cell identity of the neighbor cell and includes a possible location determined based on the first possible location and the second possible location.
[0228] Clause 69: The apparatus of any of clauses 59-68, wherein the coverage sub-area of the serving cell comprises a plurality of unique non-overlapping coverage sub-areas, wherein the data structure associates each of the unique non-overlapping coverage sub-areas with the serving cell and with a set of unique neighbor cells.
[0229] Clause 70: The apparatus of clause 69, wherein: the unique non-overlapping coverage sub-area comprises: a first coverage sub-area associated with the serving cell and the neighbor cell and a second coverage sub-area associated with the serving cell and not associated with the neighbor cell.
[0230] Clause 71: An apparatus as in clause 69, wherein the second coverage sub-area is defined based on first data of a first plurality of mobile devices, wherein the third coverage sub-area is defined based on second data of a second plurality of mobile devices, wherein the first data includes a first mobile device location and a cell identity of the neighbor cell, wherein the first data excludes a cell identity of another neighbor cell, and wherein the second data includes a second mobile device location, a cell identity of the neighbor cell, and a cell identity of the other neighbor cell.
[0231] Clause 72: An apparatus as in any of clauses 59 or 66-69, wherein the data structure represents a mapping that (i) divides the coverage area of the serving cell into coverage sub-areas and (ii) constrains the boundaries of each of the coverage sub-areas to be within the boundaries of the coverage area.
[0232] Clause 73: An apparatus as in any of clauses 59 or 66-69, wherein the data structure represents a mapping that (i) divides the coverage area of the serving cell into coverage sub-areas, and (ii) constrains possible mobile device locations within each of the coverage sub-areas to be within the coverage area.
[0233] Clause 74: The apparatus of any of clauses 59 or 66-69, wherein the data structure represents a mapping that divides the coverage area of the serving cell into coverage sub-areas, and wherein the coverage sub-areas are non-overlapping.
[0234] Clause 75: An apparatus as described in any of clauses 59-74, wherein the neighbor cell includes: a cell that is different from the serving cell and on the same frequency channel as the serving cell, a cell on a frequency channel different from the serving cell, a cell on a different radio access technology (RAT) using the same frequency channel as the serving cell, or a cell on a different RAT using a frequency channel different from the serving cell.
[0235] Clause 76: An apparatus for determining cell coverage based on crowdsourced information received at a cellular entity of a data communications network, the apparatus comprising: a device for obtaining, at the cellular entity, cell identity data and location data for a plurality of locations within a coverage area of a serving cell, wherein the cellular entity comprises a mobile device or a computer system, and wherein, for each location: the location data comprises a corresponding location, and the cell identity data comprises one or more cell identities detected at corresponding locations of one or more mobile devices; a device for storing the location data and the cell identity data using the cellular entity; and a device for associating coverage sub-areas of the coverage area with cell identities based on the cell identity data and the location data, wherein: each of the coverage sub-areas is associated with the cell identity of the serving cell in the data structure, and at least one of the coverage sub-areas is further associated with the cell identity of a neighbor cell in the data structure.
[0236] Clause 77: The apparatus of clause 76, further comprising means for storing, for each cell of the plurality of cells, a corresponding data structure dividing the coverage area of the respective cell into coverage sub-areas.
[0237] Clause 78: The apparatus of any of clauses 76-77, wherein, for at least one location of the plurality of locations, the cell identity data comprises a cell identity of the serving cell and a cell identity of at least one neighbor cell.
[0238] Clause 79: An apparatus as in any of clauses 76-78, wherein the data structure represents a mapping that (i) divides the coverage area of the serving cell into coverage sub-areas, (ii) maps each coverage sub-area to a set of cell identities, and (iii) indicates the location of a target mobile device as a possible location within the coverage sub-area, wherein the possible location is determined based on location data collected from the one or more mobile devices when the one or more mobile devices are located in the coverage sub-area.
[0239] Clause 80: The apparatus of clause 79, wherein: the mapping is associated with at least one of: a mobile network operator, a frequency channel, or a radio access technology.
[0240] Clause 81: The apparatus of any of clauses 76-80, wherein the coverage sub-area associated with the cell identity of the neighbor cell is further associated with a possible location, wherein the cell identity data comprises the cell identity of the neighbor cell, and wherein the location is the possible location.
[0241] Clause 82: An apparatus as in any of clauses 76-80, wherein the coverage area is associated with a first possible location, wherein a coverage sub-area associated with the cell identity of the neighbor cell is further associated with a second possible location, wherein the cell identity data includes the cell identity of the neighbor cell, and wherein the location is within the coverage sub-area associated with the cell identity of the neighbor cell and includes a possible location determined based on the first possible location and the second possible location.
[0242] Clause 83: The apparatus of any of clauses 76-80, wherein the coverage sub-area of the serving cell comprises a plurality of unique non-overlapping coverage sub-areas, wherein the data structure associates each of the unique non-overlapping coverage sub-areas with the serving cell and with a set of unique neighbor cells.
[0243] Clause 84: The apparatus of any of clauses 76-83, wherein the data structure represents a mapping that (i) divides the coverage area of the serving cell into coverage sub-areas and (ii) constrains the boundaries of each coverage sub-area to be within the boundaries of the coverage area.
[0244] Clause 85: The apparatus of any of clauses 76-83, wherein the data structure represents a mapping that (i) divides the coverage area of the serving cell into coverage sub-areas, and (ii) constrains possible mobile device locations within each coverage sub-area to be within the coverage area.
[0245] Clause 86: An apparatus as described in any of clauses 76-85, wherein the neighbor cell includes: a cell that is different from the serving cell and on the same frequency channel as the serving cell, a cell on a frequency channel different from the serving cell, a cell on a different radio access technology (RAT) using the same frequency channel as the serving cell, or a cell on a different RAT using a frequency channel different from the serving cell.
[0246] Clause 87: The apparatus of clause 86, wherein: the data structure further associates a coverage sub-area of the coverage area with a beam index of the serving cell, a beam index of the neighbor cell, or both.
[0247] Item 88: A non-transitory computer-readable medium storing instructions for locating a mobile device within a coverage area of a serving cell in communication with the mobile device, the instructions comprising code for: receiving cell identity data, the cell identity data comprising one or more cell identities; and determining a coverage sub-area of the coverage area of the serving cell based on using the cell identity data in a lookup of a data structure, the data structure associating each coverage sub-area of the coverage area with each cell identity, each coverage sub-area of each coverage sub-area being associated in the data structure with the cell identity of the serving cell, and at least one of the coverage sub-areas being further associated in the data structure with a cell identity of a neighbor cell; and determining a position of the mobile device, the position being within the coverage sub-area of the coverage area of the serving cell.
[0248] Clause 89: The non-transitory computer-readable medium of clause 88, wherein the instructions further comprise code for sending the cell identity data to a computer system, wherein the computer system stores the data structure, and wherein determining the location of the mobile device comprises receiving the location from the computer system.
[0249] Clause 90: The non-transitory computer-readable medium of any of clauses 88-89, wherein the instructions further comprise code for: storing the data structure in a memory of the mobile device; and performing a lookup of the data structure from the memory.
[0250] Clause 91: A non-transitory computer-readable medium as in clause 88, wherein the instructions further comprise code for: sending a cell identity of the serving cell to a computer system, wherein the computer system stores, for each cell in a plurality of cells, a corresponding data structure that divides a coverage area of the corresponding cell into coverage sub-areas; and receiving, from the computer system, the data structure corresponding to the serving cell based on the cell identity of the serving cell.
[0251] Clause 92: A non-transitory computer-readable medium as in any of clauses 88-91, wherein the instructions further comprise code for: prior to receiving the cell identity data: determining, by a location sensor of the mobile device, location data indicating a second location of the mobile device within the coverage area of the serving cell; receiving second cell identity data comprising the cell identity of the serving cell and the cell identity of the neighbor cell; and sending the location data and the second cell identity data to a computer system, wherein the data structure is generated by the computer system based on the location data and the second cell identity data.
[0252] Clause 93: A non-transitory computer-readable medium as in any of clauses 88-92, wherein the data structure represents a mapping that (i) divides the coverage area of the serving cell into coverage sub-areas, (ii) maps each of the coverage sub-areas to a set of cell identities, and (iii) indicates the location of the mobile device as a possible location within each of the coverage sub-areas, wherein the possible locations for each of the coverage sub-areas are determined based on location data collected from the multiple mobile devices when the multiple mobile devices are located in the corresponding coverage sub-areas.
[0253] Clause 94: The non-transitory computer-readable medium of any of clauses 88-93, wherein the mapping is associated with at least one of: a mobile network operator, a frequency channel, or a radio access technology.
[0254] Clause 95: The non-transitory computer-readable medium of clause 94, wherein the coverage sub-area associated with the cell identity of the neighbor cell is further associated with a possible location, wherein the cell identity data includes the cell identity of the neighbor cell, and wherein the location is the possible location.
[0255] Clause 96: The non-transitory computer-readable medium of any of clauses 88-95, wherein the data structure further associates a coverage sub-area of the coverage area with a beam index of the serving cell, a beam index of the neighbor cell, or both.
[0256] Clause 97: A non-transitory computer-readable medium as in any of clauses 88-96, wherein the coverage area is associated with a first possible location, wherein a coverage sub-area associated with the cell identity of the neighbor cell is further associated with a second possible location, wherein the cell identity data includes the cell identity of the neighbor cell, and wherein the location is within the coverage sub-area associated with the cell identity of the neighbor cell and includes a possible location determined based on the first possible location and the second possible location.
[0257] Clause 98: A non-transitory computer-readable medium as in any of clauses 88-97, wherein the coverage sub-area of the serving cell comprises a plurality of unique non-overlapping coverage sub-areas, wherein the data structure associates each of the unique non-overlapping coverage sub-areas with the serving cell and with a set of unique neighbor cells.
[0258] Clause 99: The non-transitory computer-readable medium of clause 98, wherein the unique non-overlapping coverage sub-areas include: a first coverage sub-area associated with the serving cell and the neighbor cell and a second coverage sub-area associated with the serving cell and not associated with the neighbor cell.
[0259] Clause 100: A non-transitory computer-readable medium as in clause 98, wherein the second coverage sub-area is defined based on first data of a first plurality of mobile devices, wherein the third coverage sub-area is defined based on second data of a second plurality of mobile devices, wherein the first data includes a first mobile device location and a cell identity of the neighbor cell, wherein the first data excludes a cell identity of another neighbor cell, and wherein the second data includes a second mobile device location, a cell identity of the neighbor cell, and a cell identity of the other neighbor cell.
[0260] Clause 101: A non-transitory computer-readable medium as in any of clauses 88 or 95-98, wherein the data structure represents a mapping that (i) divides the coverage area of the serving cell into coverage sub-areas, and (ii) constrains the boundaries of each of the coverage sub-areas to be within the boundaries of the coverage area.
[0261] Clause 102: A non-transitory computer-readable medium as in any of clauses 88 or 95-98, wherein the data structure represents a mapping that (i) divides the coverage area of the serving cell into coverage sub-areas, and (ii) constrains possible mobile device locations within each of the coverage sub-areas to be within the coverage area.
[0262] Clause 103: The non-transitory computer-readable medium of any of clauses 88 or 95-98, wherein the data structure represents a mapping that divides the coverage area of the serving cell into coverage sub-areas, and wherein the coverage sub-areas are non-overlapping.
[0263] Clause 104: A non-transitory computer-readable medium as in any of clauses 88-103, wherein the neighbor cell comprises: a cell that is different from the serving cell and on the same frequency channel as the serving cell, a cell on a frequency channel different from the serving cell, a cell on a different radio access technology (RAT) using the same frequency channel as the serving cell, or a cell on a different RAT using a different frequency channel from the serving cell.
[0264] Item 105: A non-transitory computer-readable medium for determining cellular cell coverage based on crowdsourced information received at a cellular entity of a data communication network, the non-transitory computer-readable medium comprising: obtaining cellular cell identity data and location data for multiple locations within a coverage area of a serving cellular cell at the cellular entity, wherein the cellular entity comprises a mobile device or a computer system, and wherein, for each location: the location data comprises a corresponding location, and the cellular cell identity data comprises one or more cellular cell identities detected at corresponding locations of one or more mobile devices; storing the location data and the cellular cell identity data using the cellular entity; and associating, by the cellular entity, each coverage sub-area of the coverage area with each cell identity based on the cellular cell identity data and the location data using a data structure, wherein: each of the coverage sub-areas is associated with the cellular cell identity of the serving cellular cell in the data structure, and at least one of the coverage sub-areas is further associated with the cell identity of a neighboring cellular cell in the data structure.
[0265] Clause 106: The non-transitory computer-readable medium of clause 105, wherein the instructions further comprise code for storing, for each cell of the plurality of cells, a corresponding data structure dividing a coverage area of the respective cell into coverage sub-areas.
[0266] Clause 107: The non-transitory computer-readable medium of any of clauses 105-106, wherein, for at least one location of the plurality of locations, the cell identity data comprises a cell identity of the serving cell and a cell identity of at least one neighbor cell.
[0267] Clause 108: A non-transitory computer-readable medium as in any of clauses 105-107, wherein the data structure represents a mapping that (i) divides the coverage area of the serving cell into coverage sub-areas, (ii) maps each coverage sub-area to a set of cell identities, and (iii) indicates a location of a target mobile device as a possible location within the coverage sub-area, wherein the possible location is determined based on location data collected from one or more mobile devices when the one or more mobile devices are located in the coverage sub-area.
[0268] Clause 109: The non-transitory computer-readable medium of clause 108, wherein the mapping is associated with at least one of: a mobile network operator, a frequency channel, or a radio access technology.
[0269] Clause 110: A non-transitory computer-readable medium as in any of clauses 105-109, wherein the coverage sub-area associated with the cell identity of the neighbor cell is further associated with a possible location, wherein the cell identity data includes the cell identity of the neighbor cell, and wherein the location is the possible location.
[0270] Clause 111: A non-transitory computer-readable medium as in any of clauses 105-109, wherein the coverage area is associated with a first possible location, wherein a coverage sub-area associated with the cell identity of the neighbor cell is further associated with a second possible location, wherein the cell identity data includes the cell identity of the neighbor cell, and wherein the location is within the coverage sub-area associated with the cell identity of the neighbor cell and includes a possible location determined based on the first possible location and the second possible location.
[0271] Clause 112: A non-transitory computer-readable medium as in any of clauses 105-109, wherein the coverage sub-area of the serving cell comprises a plurality of unique non-overlapping coverage sub-areas, wherein the data structure associates each of the unique non-overlapping coverage sub-areas with the serving cell and with a set of unique neighbor cells.
[0272] Clause 113: A non-transitory computer-readable medium as in any of clauses 105-112, wherein the data structure represents a mapping that (i) divides the coverage area of the serving cell into coverage sub-areas, and (ii) constrains the boundaries of each coverage sub-area to be within the boundaries of the coverage area.
[0273] Clause 114: A non-transitory computer-readable medium as in any of clauses 105-112, wherein the data structure represents a mapping that (i) divides the coverage area of the serving cell into coverage sub-areas, and (ii) constrains possible mobile device locations within each coverage sub-area to be within the coverage area.
[0274] Clause 115: A non-transitory computer-readable medium as in any of clauses 105-114, wherein the neighbor cell comprises: a cell that is different from the serving cell and on the same frequency channel as the serving cell, a cell on a frequency channel different from the serving cell, a cell on a different radio access technology (RAT) using the same frequency channel as the serving cell, or a cell on a different RAT using a different frequency channel than the serving cell.
[0275] Clause 116: The non-transitory computer-readable medium of clause 115, wherein the data structure further associates a coverage sub-area of the coverage area with a beam index of the serving cell, a beam index of the neighbor cell, or both.
Claims
1. A method for locating a mobile device within the coverage area of a serving cell with which the mobile device is in communication, the method being implemented by the mobile device and include: receiving cell identity data from one or more of a base station associated with the serving cell or a base station associated with a neighbor cell, the cell identity data comprising one or more cell identities; determining a coverage sub-area of the coverage area of the serving cell based on using the cell identity data in a lookup of a data structure, the coverage sub-area being defined at least in part based on geographic or network attributes of the serving cell and the neighbor cells, the data structure associating respective coverage sub-areas of the coverage area with at least the cell identity of the serving cell and the cell identities of the neighbor cells, each of the respective coverage sub-areas being associated in the data structure with the cell identity of the serving cell, and at least one of the respective coverage sub-areas being further associated in the data structure with the cell identity of the neighbor cell, wherein the respective coverage sub-areas of the serving cell include a plurality of unique non-overlapping coverage sub-areas, wherein the data structure associates each of the unique non-overlapping coverage sub-areas with the serving cell and with a set of unique neighbor cells; as well as A location of the mobile device is determined, the location being within the coverage sub-area of the coverage area of the serving cell.
2. The method of claim 1, further comprising: include: The cell identity data is sent to a computer system, wherein the computer system stores the data structure, and wherein determining the location of the mobile device includes receiving the location from the computer system.
3. The method of claim 1, further comprising: include: storing the data structure in a memory of the mobile device; as well as A lookup of the data structure is performed from the memory.
4. The method of claim 3, further comprising: include: sending a cell identity of the serving cell to a computer system, wherein the computer system stores, for each cell of a plurality of cells, a corresponding data structure dividing a coverage area of the corresponding cell into coverage sub-areas; as well as The data structure corresponding to the serving cell is received from the computer system based on a cell identity of the serving cell.
5. The method of claim 1, further comprising: include: Prior to receiving the cell identity data: determining, by a location sensor of the mobile device, location data indicative of a second location of the mobile device within the coverage area of the serving cell; receiving second cell identity data including a cell identity of the serving cell and a cell identity of the neighbor cell; as well as The location data and the second cell identity data are sent to a computer system, wherein the data structure is generated by the computer system based on the location data and the second cell identity data.
6. The method according to claim 1, in, The data structure represents a mapping that (i) divides the coverage area of the serving cell into the coverage sub-areas, (ii) maps each of the coverage sub-areas to a set of cell identities, and (iii) indicates the location of the mobile device as a possible location within each of the coverage sub-areas, wherein the possible location for each of the coverage sub-areas is determined based on location data collected from the plurality of mobile devices when the plurality of mobile devices are located in the corresponding coverage sub-areas.
7. The method according to claim 6, in, The mapping is associated with at least one of: a mobile network operator, a frequency channel, or a radio access technology.
8. The method according to claim 1, in, The coverage sub-area associated with the cell identity of the neighbor cell is further associated with a possible location, wherein the cell identity data comprises the cell identity of the neighbor cell, and wherein the location is the possible location.
9. The method according to claim 1, in, The data structure further associates a coverage sub-area of the coverage area with a beam index of the serving cell, a beam index of the neighbor cell, or both.
10. The method according to claim 1, in, The coverage area is associated with a first possible location, wherein a coverage sub-area associated with the cell identity of the neighbor cell is further associated with a second possible location, wherein the cell identity data includes the cell identity of the neighbor cell, and wherein the location is within the coverage sub-area associated with the cell identity of the neighbor cell and includes a possible location determined based on the first possible location and the second possible location.
11. The method according to claim 1, in, The unique non-overlapping coverage sub-areas include: a first coverage sub-area associated with the serving cell and the neighbor cell, and a second coverage sub-area associated with the serving cell and not associated with a neighbor cell.
12. The method of claim 1, wherein the second coverage sub-area is defined based on first data of a first plurality of mobile devices, wherein the third coverage sub-area is defined based on second data of a second plurality of mobile devices, wherein the first data includes a first mobile device location and a cell identity of the neighbor cell, wherein the first data excludes a cell identity of another neighbor cell, and wherein the second data includes a second mobile device location, a cell identity of the neighbor cell, and a cell identity of the another neighbor cell.
13. The method of claim 1, in, The data structure represents a mapping that (i) divides the coverage area of the serving cell into the coverage sub-areas and (ii) constrains a boundary of each of the coverage sub-areas to be within a boundary of the coverage area.
14. The method of claim 1, in, The data structure represents a mapping that (i) divides the coverage area of the serving cell into the coverage sub-areas and (ii) constrains possible mobile device locations within each of the coverage sub-areas to be within the coverage area.
15. The method of claim 1, in, The data structure represents a mapping that divides the coverage area of the serving cell into the coverage sub-areas, and wherein the coverage sub-areas are non-overlapping.
16. The method of claim 1, in, The neighboring cellular cells include: a cell different from the serving cell and on the same frequency channel as the serving cell, a cell on a different frequency channel than the serving cell, a cell on a different radio access technology (RAT) that uses the same frequency channel as the serving cell, or A cell on a different RAT that uses a different frequency channel than the serving cell.
17. A mobile device, the mobile device being configured to locate the mobile device within a coverage area of a serving cell in communication with the mobile device, the mobile device include: Transceiver; Memory; as well as one or more processing units communicatively coupled to the transceiver and the memory, wherein the one or more processing units are configured to: receiving, via the transceiver, cell identity data from one or more of a base station associated with the serving cell or a base station associated with a neighbor cell, the cell identity data comprising one or more cell identities; determining a coverage sub-area of the coverage area of the serving cell based on using the cell identity data in a lookup of a data structure, the coverage sub-area being defined at least in part based on geographic or network attributes of the serving cell and the neighbor cells, the data structure associating respective coverage sub-areas of the coverage area with at least the cell identity of the serving cell and the cell identities of the neighbor cells, each of the respective coverage sub-areas being associated in the data structure with the cell identity of the serving cell, and at least one of the respective coverage sub-areas being further associated in the data structure with the cell identity of the neighbor cell, wherein the respective coverage sub-areas of the serving cell include a plurality of unique non-overlapping coverage sub-areas, wherein the data structure associates each of the unique non-overlapping coverage sub-areas with the serving cell and with a set of unique neighbor cells; as well as A location of the mobile device is determined, the location being within the coverage sub-area of the coverage area of the serving cell.
18. The mobile device of claim 17, wherein the one or more processing units are further configured to: The cell identity data is sent to a computer system, wherein the computer system stores the data structure, and wherein determining the location of the mobile device includes receiving the location from the computer system.
19. The mobile device of claim 17, wherein the one or more processing units are further configured to: sending a cell identity of the serving cell to a computer system, wherein the computer system stores, for each cell of a plurality of cells, a corresponding data structure dividing a coverage area of the respective cell into coverage sub-areas; and The data structure corresponding to the serving cell is received from the computer system based on a cell identity of the serving cell.
20. The mobile device of claim 17, wherein the one or more processing units are further configured to: Prior to receiving the cell identity data: determining location data indicative of a second location of the mobile device within the coverage area of the serving cell; receiving second cell identity data including a cell identity of the serving cell and a cell identity of the neighbor cell; as well as The location data and the second cell identity data are sent to a computer system, wherein the data structure is generated by the computer system based on the location data and the second cell identity data.
21. The mobile device according to claim 17, in, The data structure represents a mapping that (i) divides the coverage area of the serving cell into the coverage sub-areas, (ii) maps each of the coverage sub-areas to a set of cell identities, and (iii) indicates the location of the mobile device as a possible location within each of the coverage sub-areas, wherein the possible location for each of the coverage sub-areas is determined based on location data collected from the plurality of mobile devices when the plurality of mobile devices are located in the corresponding coverage sub-areas.
22. The mobile device according to claim 17, in, The coverage sub-area associated with the cell identity of the neighbor cell is further associated with a possible location, wherein the cell identity data comprises the cell identity of the neighbor cell, and wherein the location is the possible location.
23. The mobile device according to claim 17, in, The data structure further associates a coverage sub-area of the coverage area with a beam index of the serving cell, a beam index of the neighbor cell, or both.
24. The mobile device according to claim 17, in, The coverage area is associated with a first possible location, wherein a coverage sub-area associated with the cell identity of the neighbor cell is further associated with a second possible location, wherein the cell identity data includes the cell identity of the neighbor cell, and wherein the location is within the coverage sub-area associated with the cell identity of the neighbor cell and includes a possible location determined based on the first possible location and the second possible location.
25. The mobile device of claim 17, in, The unique non-overlapping coverage sub-areas include: a first coverage sub-area associated with the serving cell and the neighbor cell, and a second coverage sub-area associated with the serving cell and not associated with a neighbor cell.
26. A mobile device as described in claim 17, wherein the second coverage sub-area is defined based on first data of a first plurality of mobile devices, and wherein the third coverage sub-area is defined based on second data of a second plurality of mobile devices, wherein the first data includes a first mobile device location and a cell identity of the neighbor cell, wherein the first data excludes a cell identity of another neighbor cell, and wherein the second data includes a second mobile device location, a cell identity of the neighbor cell, and a cell identity of the another neighbor cell.
27. The mobile device of claim 17, in, The data structure represents a mapping that (i) divides the coverage area of the serving cell into the coverage sub-areas and (ii) constrains a boundary of each of the coverage sub-areas to be within a boundary of the coverage area.
28. The mobile device of claim 17, in, The data structure represents a mapping that (i) divides the coverage area of the serving cell into the coverage sub-areas and (ii) constrains possible mobile device locations within each of the coverage sub-areas to be within the coverage area.
29. The mobile device of claim 17, in, The data structure represents a mapping that divides the coverage area of the serving cell into the coverage sub-areas, and wherein the coverage sub-areas are non-overlapping.
30. The mobile device of claim 17, in, The neighboring cellular cells include: a cell different from the serving cell and on the same frequency channel as the serving cell, a cell on a different frequency channel than the serving cell, a cell on a different radio access technology (RAT) that uses the same frequency channel as the serving cell, or A cell on a different RAT that uses a different frequency channel than the serving cell.
31. An apparatus for locating a mobile device within the coverage area of a serving cell with which the mobile device is in communication, the apparatus include: means for receiving cell identity data from one or more of a base station associated with the serving cell or a base station associated with a neighbor cell, the cell identity data comprising one or more cell identities; means for determining a coverage sub-area of the coverage area of the serving cell based on using the cell identity data in a lookup of a data structure, the coverage sub-area being defined at least in part based on geographic or network attributes of the serving cell and the neighbor cells, the data structure associating coverage sub-areas of the coverage area with at least a cell identity of the serving cell and a cell identity of the neighbor cells, each of the coverage sub-areas being associated in the data structure with the cell identity of the serving cell, and at least one of the coverage sub-areas being further associated in the data structure with the cell identity of the neighbor cell, wherein the coverage sub-areas of the serving cell include a plurality of unique non-overlapping coverage sub-areas, wherein the data structure associates each of the unique non-overlapping coverage sub-areas with the serving cell and with a set of unique neighbor cells; as well as Means for determining a location of the mobile device, the location being within the coverage sub-area of the coverage area of the serving cell.
32. The apparatus of claim 31, further comprising: include: Means for sending the cell identity data to a computer system, wherein the computer system stores the data structure, and wherein determining the location of the mobile device comprises receiving the location from the computer system.
33. A non-transitory computer-readable medium storing instructions for locating a mobile device within a coverage area of a serving cell in communication with the mobile device, the instructions comprising code for: receiving cell identity data from one or more of a base station associated with the serving cell or a base station associated with a neighbor cell, the cell identity data comprising one or more cell identities; A coverage sub-area of the coverage area of the serving cell is determined based on using the cell identity data in a lookup of a data structure, the coverage sub-area being defined at least in part based on geographic or network attributes of the serving cell and the neighbor cell, the data structure associating each of the coverage sub-areas of the coverage area with at least the cell identity of the serving cell and the cell identity of the neighbor cell, each of the coverage sub-areas being associated in the data structure with the cell identity of the serving cell, and at least one of the coverage sub-areas being further associated in the data structure with the cell identity of the neighbor cell, wherein The coverage sub-areas of the serving cell include a plurality of unique non-overlapping coverage sub-areas, wherein the data structure associates each of the unique non-overlapping coverage sub-areas with the serving cell and with a unique set of neighbor cells; as well as A location of the mobile device is determined, the location being within the coverage sub-area of the coverage area of the serving cell.
Citation Information
Patent Citations
Location specific search for regional satellite vehicles
CN102057292A
Enhanced cell identification location determination
US10517061B1
Nodes and methods for positioning
US20120178473A1
Enhanced Cell ID Location Method Using Non Uniform Subsectors and Neighboring Cell Centroid
US20140171105A1
