Geofencing for satellite communications in the absence of a terrestrial network
Geofencing using region and restriction status files represented by geopolygons allows UE to adapt to satellite service restrictions in areas without terrestrial networks, ensuring efficient and adaptive communication.
Patent Information
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2024-03-01
- Publication Date
- 2026-03-25
AI Technical Summary
Obtaining the latest restriction status of satellite-related services for user equipment (UE) in areas without terrestrial networks is difficult, limiting the use of satellite-based communication in many regions.
A method for geofencing using region and restriction status files, represented by geopolygons, which are updated and managed by a server to provide real-time service restriction information to UE, enabling it to determine and adapt to service availability.
Enables UE to obtain and adapt to the latest satellite service restrictions even in areas without ground networks, optimizing GNSS duty cycles and ensuring appropriate communication measures are taken.
Smart Images

Figure 2026509802000001_ABST
Abstract
Description
Technical Field
[0001] <0**********6>(Cross - Reference to Related Applications)
[0001] This application claims the benefit of U.S. Provisional Patent Application No. 63 / 489,514, filed Mar. 10, 2023, entitled "GEOFENCING FOR SATELLITE COMMUNICATION IN THE ABSENCE OF TERRESTRIAL NETWORKS", and claims the benefit of U.S. Patent Application No. 18 / 311,878, filed May 3, 2023, entitled "GEOFENCING FOR SATELLITE COMMUNICATION IN THE ABSENCE OF TERRESTRIAL NETWORKS", both of which are assigned to the assignee of this application and are hereby incorporated by reference in their entirety.
Background Art
[0002] 1. Field of Disclosure
[0002] This disclosure relates generally to the field of wireless communication and, more specifically, to enabling user equipment (UE) (e.g., a mobile device) to communicate using satellite - based communication.
[0003] 2. Description of Related Art
[0003] Satellite - based communication has been extended to non - specialized devices such as standard UEs (e.g., mobile devices) since it only enabled satellite phones with specialized antennas for satellite - based communication. Although widely used, satellite - based communication is still restricted in over 80 countries. Obtaining the latest restricted status of one or more satellite - related services for a UE with respect to the area where the UE is located can be difficult when there is no terrestrial network at all. <00000**********8>
Summary of the Invention
[0004] <**********22>
[0004] A method for an exemplary geofencing method relating to satellite communications, performed by a UE, comprising obtaining a first region file containing a plurality of regions, each of which is represented by one or more geopolygons, each of which corresponds to its own unique region identifier, and each of which corresponds to a first set of region identifiers. The method also comprises obtaining a first restriction status file containing restriction status information relating to each of which is which, with respect to each of which is which, the first restriction status file indicates the restriction status of one or more satellite-related services for a UE in a region represented by one or more geopolygons. The method further comprises receiving a second restriction status file from a server, containing a second set of region identifiers and corresponding restriction status information, determining the difference between the first set of region identifiers and the second set of region identifiers, and updating the first region file, the first restriction status file, or both, based on the difference.
[0005]
[0005] A method, performed by a server, that exemplifies geofencing for satellite communications, comprising obtaining a first region file containing a plurality of regions, each of which is represented by one or more geopolygons, each of which corresponds to its own unique region identifier, and the plurality of regions corresponding to a first set of region identifiers. The method also comprises obtaining a first restriction status file containing restriction status information for each of which is which, the first restriction status file indicates, with respect to each of which is which, the restriction status of one or more satellite-related services for a UE in a region represented by one or more geopolygons. The method further comprises receiving a request for restriction status information for one or more of which are which from a target UE, and, in response to receiving the request, sending the first restriction status file to the target UE.
[0006]
[0006] A method for exemplary geofencing relating to satellite communications performed by a UE, comprising obtaining a region file containing a plurality of regions, each of which is represented by one or more geopolygons, and each of which corresponds to its respective unique region identifier. The method also comprises obtaining a restriction status file containing restriction status information for each of which regions, the restriction status file indicating the restriction status of one or more satellite-related services for the UE in the region represented by one or more geopolygons with respect to each of which regions. The method further comprises determining a location estimate for the UE and the uncertainty associated with the location estimate, determining the corresponding geopolygon among one or more geopolygons in the region file corresponding to the location estimate based on the location estimate and the uncertainty associated with the location estimate, and obtaining restriction status information for the corresponding geopolygon based on the restriction status file.
[0007]
[0007] A representative method of cloud-based geofencing relating to satellite communications, performed by a server, comprising obtaining a region file containing a plurality of regions, each of which is represented by one or more geopolygons, and each of which corresponds to its respective unique region identifier. The method also comprises obtaining a restriction status file containing restriction status information for each of the plurality of regions, wherein the restriction status file indicates, with respect to each of the plurality of regions, the restriction status status of one or more satellite-related services for a UE in a region represented by one or more geopolygons. The method further comprises obtaining a location estimate of the target UE and a unique identifier of the target UE, determining a unique region identifier corresponding to the location estimate of the UE according to the region file, and determining a restriction status, including satellite-related service parameters applicable to the target UE, based on the unique region identifier and the unique identifier of the target UE, according to the restriction status file.
[0008]
[0008] An exemplary UE for geofencing relating to satellite communications comprises a transceiver, memory, and one or more processors communicatively coupled to the transceiver and memory. The one or more processors are configured to obtain a first region file containing a plurality of regions, each of which regions is represented by one or more geopolygons, each of which regions corresponds to its own unique region identifier, and the plurality of regions corresponds to a first set of region identifiers. The one or more processors are also configured to obtain a first restriction status file containing restriction status information relating to each of which regions, the first restriction status file indicating the restriction status of one or more satellite-related services for the UE in the region represented by one or more geopolygons relating to each of which regions. One or more processors are further configured to receive from the server a second set of area identifiers and a second restriction status file containing corresponding restriction status information, determine the difference between the first set of area identifiers and the second set of area identifiers, and update the first area file, the first restriction status file, or both based on the difference.
[0009]
[0009] An exemplary server for geofencing relating to satellite communications comprises a transceiver, memory, and one or more processors communicatively coupled to the transceiver and memory. One or more processors are configured to obtain a first region file containing a plurality of regions, each of which is represented by one or more geopolygons, each of which corresponds to its own unique region identifier, and each of which corresponds to a first set of region identifiers. One or more processors are also configured to obtain a first restriction status file containing restriction status information relating to each of which is which, for each of which is which, the first restriction status file indicates the restriction status of one or more satellite-related services for a UE in a region represented by one or more geopolygons. One or more processors are further configured to receive a request for restriction status information relating to one or more of which is which from a target UE, and, upon receiving the request, to send the first restriction status file to the target UE.
[0010]
[0010] An exemplary UE for geofencing relating to satellite communications comprises a transceiver, memory, and one or more processors communicatively coupled to the transceiver and memory. The one or more processors are configured to obtain a region file containing a plurality of regions, each of which is represented by one or more geopolygons, and each of which corresponds to a unique region identifier. The one or more processors are also configured to obtain a restriction status file containing restriction status information relating to each of which regions, the restriction status file indicating the restriction status of one or more satellite-related services for the UE in the region represented by one or more geopolygons with respect to each of which regions. The one or more processors are further configured to determine a location estimate of the UE and the uncertainty associated with the location estimate, determine the corresponding geopolygon among the one or more geopolygons in the region file corresponding to the location estimate based on the location estimate and the uncertainty associated with the location estimate, and obtain restriction status information for the corresponding geopolygon based on the restriction status file.
[0011]
[0011] An exemplary server for cloud-based geofencing relating to satellite communications comprises a transceiver, memory, and one or more processors communicatively coupled to the transceiver and memory. One or more processors are configured to retrieve a region file containing multiple regions, each of which is represented by one or more geopolygons, and each of which corresponds to a unique region identifier. One or more processors are also configured to retrieve a restriction status file containing restriction status information relating to each of which regions, the restriction status file indicating the restriction status of one or more satellite-related services for each of which regions, to a UE in a region represented by one or more geopolygons. One or more processors are further configured to obtain a location estimate of the target UE and a unique identifier for the target UE, determine a unique region identifier corresponding to the location estimate of the UE according to a region file, and determine a restriction status, including satellite-related service parameters applicable to the target UE, based on the unique region identifier and the unique identifier for the target UE, according to a restriction status file.
[0012]
[0012] This summary is not intended to identify any major or essential features of the claimed subject matter, nor is it intended to be used independently to determine the scope of the claimed subject matter. The subject matter should be understood by referring to appropriate parts of the entire specification of this disclosure, any or all of the drawings, and each claim. The above summary, along with other features and examples, is described in more detail below in the text of the specification, the claims, and the accompanying drawings. [Brief explanation of the drawing]
[0013] [Figure 1]
[0013] This is a diagram of a satellite-based communication system according to one embodiment. [Figure 2]
[0014] An exemplary architecture of a system for providing geofencing support data in satellite-based communications to a UE, according to one embodiment, is shown. [Figure 3AB]
[0015] This is a diagram of exemplary geopolygons representing different regions in geofencing according to one embodiment. [Figure 3C]
[0016] An exemplary region file is shown, in which multiple geopolygons are represented using the GeoJSON format according to one embodiment. [Figure 4]
[0017] This flowchart illustrates how geofencing area files can be updated from a server for satellite-based communications, according to several embodiments. [Figure 5]
[0018] This flowchart illustrates how geofencing restriction status files can be updated from a server for satellite-based communications, according to several embodiments. [Figure 6]
[0019] This flowchart illustrates how geofencing can be performed by a UE for satellite-based communications in several embodiments. [Figure 7]
[0020] This is a flowchart of a method for updating geofencing in satellite-based communications, performed by a UE, according to several embodiments. [Figure 8]
[0021] This is a flowchart of a method for updating geofencing in satellite-based communications, performed by a server, according to several embodiments. [Figure 9]
[0022] This is a flowchart of a method for using geofencing in satellite-based communications, performed by a UE, according to several embodiments. [Figure 10]
[0023] A block diagram of one embodiment of a UE that can be used in an embodiment as described in this specification. [Figure 11]
[0024] A block diagram of one embodiment of a computer system that can be used in an embodiment as described in this specification. [Figure 12]
[0025] A flowchart showing how cloud-based geofencing can be performed by a server for satellite-based communication according to some embodiments. [Figure 13]
[0026] A flowchart of a method for using cloud-based geofencing in satellite-based communication, performed by a server according to some embodiments.
[0014]
[0027] According to certain exemplary implementations, like reference numerals in the various drawings indicate like elements. Further, multiple instances of an element may sometimes be indicated by following the first digit of that element with a letter or a hyphen and a second digit. For example, multiple instances of element 110 may be indicated as 110-1, 110-2, 110-3, etc., or 110a, 110b, 110c, etc. When referring to such an element using only the first digit, it is understood to be any instance of that element (e.g., in the foregoing example, element 110 refers to elements 110-1, 110-2, and 110-3, or elements 110a, 110b, and 110c).
Embodiments for Carrying Out the Invention
[0015]
[0028] The following description focuses on a specific implementation for the purpose of illustrating inventive aspects of various embodiments. However, it will be readily apparent to those skilled in the art that the teachings herein can be applied in numerous different ways. The implementations described include the IEEE 802.15.4 standard for ultra-wideband (UWB), the IEEE 802.11 standard (including those identified as Wi-Fi® technology), the Bluetooth® standard, code division multiple access (CDMA), frequency division multiple access (FDMA), time division multiple access (TDMA), Global System for Mobile communications (GSM), General Packet Radio Service (GPRS), Enhanced Data GSM Environment (EDGE), Terrestrial Trunked Radio (TETRA), Wideband-CDMA (W-CDMA), Evolution Data Optimized (EV-DO), 1xEV-DO, and EV-DO Rev. A, EV-DO Rev B, High Rate Packet Data (HRPD), High Speed Packet Access (HSPA), High Speed Downlink Packet Access (HSDPA), High Speed Uplink Packet Access (HSUPA), Evolved High Speed Packet AccessIt can be implemented in any device, system, or network capable of transmitting and receiving radio frequency (RF) signals in accordance with any communication standard, such as Access (HSPA+), Long Term Evolution (LTE), or Advanced Mobile Phone System (AMPS), or other known signals used for communication within wireless networks, cellular networks, or Internet of Things (IoT) networks, such as systems utilizing 3G, 4G, 5G, 6G technologies, or further implementations thereof.
[0016]
[0029] As used herein, “RF signal” includes electromagnetic waves that transmit information through the space between a transmitter (or transmitting device) and a receiver (or receiving device). As used herein, a transmitter may transmit a single “RF signal” or a plurality of “RF signals” to a receiver. However, due to the propagation characteristics of RF signals through multiple channels or paths, a receiver may receive a plurality of “RF signals” corresponding to each transmitted RF signal.
[0017]
[0030] In addition, unless otherwise specified, references to “reference signals,” “positioning reference signals,” and “positioning reference signals” may be used to refer to signals used for positioning user equipment (UEs) in 5G new radio (NR) networks. As will be described in more detail herein, such signals may include any of various signal types, but are not necessarily limited to positioning reference signals (PRS) as defined in the relevant wireless standards.
[0018]
[0031] Furthermore, unless otherwise specified, the term “positioning” as used herein may include absolute location determination, relative location determination, distance measurement, or a combination thereof. Such positioning may include, and / or be based on, timing measurements, angle measurements, phase measurements, or power measurements, or a combination thereof (including RF sensing measurements), for the purpose of location identification services or sensing services.
[0019]
[0032] Various aspects relate to the field of wireless communications in general. Some aspects, more specifically, relate to geofencing in satellite-based communications.
[0020]
[0033] When performing geofencing in satellite-based communications, obtaining the latest restriction status of one or more satellite-related services to the UE in the area where the UE is located (e.g., whether satellite-based communications are permitted, whether satellite-based communications or positioning are affected, or any combination thereof) can be difficult if no ground network exists. In some embodiments, a server can be used to obtain and / or update the UE's geofencing area file and / or restriction status file(s).
[0021]
[0034] When performing geofencing, each region in the region file can be represented by one or more geopolygons. Each region may correspond to its own unique region identifier (e.g., region details for the corresponding one or more geopolygons, and a hash of the region file's version indicator). The restriction status file may contain restriction status information for each region, indicating the restriction status of one or more satellite-related services for the UEs within the region represented by one or more geopolygons. For example, restrictions may include whether satellite communications are permitted by the provider, whether satellite communications are affected, the level of service (e.g., whether only emergency communications are permitted, or whether person-to-person messaging is also permitted), the transmit power level, the amount of data that can be used, which satellite constellations are available, or any combination thereof. When using geofencing, the UE can determine its location estimate, determine the uncertainty associated with the location estimate, determine the corresponding geopolygon among one or more geopolygons corresponding to the location estimate based on the location estimate and the uncertainty associated with the location estimate, and obtain restriction status information for the corresponding area represented by the geopolygon based on the restriction status file.
[0022]
[0035] Certain aspects of the subject matter described herein can be implemented to achieve one or more of the following potential benefits. In some embodiments, by periodically updating geofencing area files and / or restriction status files stored within the UE (e.g., at different frequencies), the described technique may enable the UE to obtain the most up-to-date restriction status for one or more satellite-related services to the area where the UE is located. In some embodiments, the UE can determine its proximity (e.g., determined based on the UE's speed and direction of travel) to one or more neighboring areas with service restrictions. In some embodiments, the UE's GNSS duty cycle can be optimized based on its proximity to areas of interest specified in the area files. For example, if the UE is far from an area of interest, the GNSS function may be activated less frequently.
[0023]
[0036] Therefore, when a UE roams into an area where one or more satellite-related services are restricted, in the absence of a ground network (for example, hiking or traveling in a remote area, or traveling in airplane mode), the UE can still take appropriate measures depending on the current restriction status of one or more satellite-related services in that area (for example, using signals from unaffected / unbanned bands, notifying the user of the restrictions).
[0024]
[0037] Figure 1 shows a satellite-based communications system 100 in which satellites 110 move along a path within an orbital plane 130 and orbit the Earth 120. For simplicity, this figure has been greatly simplified. In actual embodiments, the satellite-based communications system 100 may include dozens of satellites 110 with many orbital planes 130. For example, the Iridium® communications system has 66 satellites, with 11 satellites in each of the six orbital planes. To facilitate the optimization of communications efficiency, the satellites 110 in such a satellite-based communications system 100 are typically arranged at equal intervals such that the spacing 140 between all satellites 110 within the orbital plane 130 is approximately the same.
[0025]
[0038] Satellite-based communication systems, such as those shown in Figure 1, generally operate in low Earth orbit (LEO), where the satellite altitude is below 2,000 km. However, some satellite-based communication systems can operate in medium Earth orbit (MEO) (with an altitude of approximately 10,000–20,000 kara) or geostationary Earth orbit (GEO) (with an altitude of approximately 35,786 km).
[0026]
[0039] Figure 2 shows an exemplary architecture 200 of a system for providing geofencing support data to UE205 in satellite-based communications, according to one embodiment. Satellite 210 may correspond to satellite 110 in Figure 1. Arrows represent communication links, which may include one or more intervening devices, networks, etc. (not shown). As with other figures, Figure 2 is provided as a non-limiting embodiment, and alternative embodiments may include additional or alternative components for providing support data to UE205.
[0027]
[0040] In exemplary architecture 200, geofencing can be performed using a server 220 connected to a satellite 210. In this case, the server 220 may include a computer server hosted in the cloud by a service for providing support data for geofencing in satellite-based communications. This service may be provided, for example, by a satellite-based communications operator, a mobile phone operator, etc., and communication between the server 220 and the UE 205 may be relayed over one or more wired and / or wireless networks, including the internet, a wireless cellular network, etc. In some embodiments, the UE 205 may also receive support data directly from the satellite 210.
[0028]
[0041] As disclosed in detail below, the server 220 and / or satellite 210 may provide geofencing information (e.g., region files (one or more) and restriction status files) to the UE 205, thereby enabling the UE 205 to obtain the latest restriction status of one or more satellite-related services for one or more regions, and to take appropriate action accordingly (e.g., using signals from unaffected / unbanned bands, notifying users of restrictions).
[0029]
[0042] As described above, geofencing for satellite-based communications allows a UE to obtain the latest restriction status of one or more satellite-related services for a given area when roaming in areas where services are restricted, and even when there is no ground network available (e.g., hiking or traveling in a remote area, or moving in airplane mode). The UE can take appropriate measures (e.g., using signals from unaffected / unbanned bands, notifying the user of the restrictions). For example, the UE can obtain (e.g., download or update) the relevant geofencing support data (e.g., area files (one or more) and / or restriction status files) in advance (e.g., from areas where there are no restrictions on satellite-based communications, from areas where ground network connectivity is available, and / or by pre-programming), and perform geofencing when roaming in areas where one or more of the satellite-related services are restricted. The UE can then use relevant geofencing support data to determine the restrictions and, accordingly, take appropriate measures (e.g., using signals from unaffected / unbanned bands, and / or notifying the user of the restrictions).
[0030]
[0043] In some embodiments, the associated geofencing support data may include one or more region files representing different features or regions of a target, and / or a restriction status file showing restriction status information for each of the different regions of a target. For example, in a region file (typically several kilobytes in size), different regions may be represented by one or more geopolygons, in which case each region of the different regions is indexed by its own unique identifier.
[0031]
[0044] In some embodiments, a restriction status file (e.g., typically a few bytes in size per feature) can be included within the supporting data provided for each feature of interest. When updating the restriction status file, the server can identify a list of areas of interest (e.g., corresponding to a subset of areas in an area file) along with the relevant restriction status and any relevant details (e.g., whether satellite-based communications are permitted, which constellations and bandwidths are available, and / or whether communications or positioning are affected by spoofing / jamming). In some embodiments, the restriction status file can be updated at a faster rate than the area file.
[0032]
[0045] Figures 3A and 3B are illustrative diagrams of geopolygons representing different regions in geofencing according to one embodiment. As shown in Figure 3A, Italy is represented using three polygons 310 with a resolution of 110m. In some embodiments, other resolutions can also be used. For example, as shown in Figure 3B, with a resolution of 50m, ten geopolygons 320 (only some of the ten geopolygons 320 are labeled for ease of illustration) are used to represent Italy. When higher resolutions are used (e.g., geopolygons with vertices that are more closely spaced apart from one another), more map detail of the region (e.g., a more accurate representation of the shape and size of the region, a smaller region) can be shown. The boundaries of the region represented by the geopolygons can also be defined more accurately and in more detail. For example, when representing small islands or overlapping regions (e.g., regions within a region, such as Vatican City within Rome, one or more regions), geopolygons with finer resolutions can be used.
[0033]
[0046] In some embodiments, geopolygons with different resolutions can be used within the region file to achieve the desired performance. For example, a large region (e.g., a peninsula) can be represented by a geopolygon with a resolution of 110m, while a small region (e.g., islands and / or overlapping regions) can be represented by a geopolygon with a resolution of 50m. Note that geopolygons with other resolutions can also be used for the desired performance.
[0034]
[0047] In some embodiments, geopolygons in a region file can be represented using various standardized formats (e.g., GeoJSON, shapefile, KML, well-known text (WKT)). As a non-limiting embodiment, Figure 3C shows an exemplary region file 330 in which multiple geopolygons within the region file 330 are represented using the GeoJSON format according to one embodiment.
[0035]
[0048] As shown in Figure 3C, in some embodiments, the region file 330 may have multiple "Features" 342 within a "FeatureCollection" 341, where each "Feature" 342 represents a region of interest having one or more geopolygons. The region file 330 may also include a characteristics section 345 that provides information associated with the multiple geopolygons contained within the region file 330. For example, the characteristics section 345 may include a readable name 350 (e.g., the name of the region being represented), a geopolygon boundary uncertainty 355 (e.g., the resolution for each geopolygon expressed in meters), and a unique ID 360 (e.g., region details for the corresponding one or more geopolygons, and a hash of the region file's version indicator). In some embodiments, the region file 330 also includes geographical details of each geopolygon, for example, the vertex coordinates 365 (e.g., longitude and latitude) of each geopolygon among the multiple geopolygons contained within the region file 330, or a hierarchical index of the tiles that make up each geopolygon among the multiple geopolygons contained within the region file 330.
[0036]
[0049] In some embodiments, the region file 330 may include a header. The header may include the version number of the region file 330, a timestamp of the most recent update, a file signature, a content summary, high-level characteristics applicable to all included geopolygons, or any combination thereof. In some embodiments, each region in the region file 330 may correspond to a region identifier. For example, the region identifier may be a hash of the map version number and geopolygon details (e.g., the coordinates of one or more geopolygons used to represent the region, the region's characteristics). Thus, the region identifier may be unique for the corresponding region. Consequently, multiple regions within the region file 330 may correspond to a set of region identifiers.
[0037]
[0050] In some embodiments, the region file 330 may also include a set of region identifiers and associated characteristics (e.g., features such as whether satellite communications are permitted, whether satellite-based communications or positioning are affected, or any combination thereof). In some embodiments, the region file 330 can be feature-independent. For example, different characteristics may require different regions to be restricted.
[0038]
[0051] In some embodiments, the region file 330 can be retrieved from a server if the UE is in a region where there are no restrictions on satellite-based communications, and / or can be retrieved from a region where ground network connectivity exists. Additionally or alternatively, the region file 330 can also be pre-programmed within the UE (e.g., the region file 330 is loaded into the UE at the factory). In some embodiments, as will be discussed in detail below, the region file 330 stored within the UE can be periodically updated by a server (e.g., every few weeks or months). Alternatively or additionally, the region file 330 can be updated when one or more new geopolygons are added to the region file 330, or when the boundaries of one or more geopolygons in the region file 330 are adjusted. In some embodiments, when transmitted (e.g., to retrieve and / or update the region file 330), the region file 330 can be converted to an extensible binary format using, for example, binary encoding for geographical data.
[0039]
[0052] Figure 4 is a flowchart illustrating how geofencing area files can be updated from a server for satellite-based communications in several embodiments. In some embodiments, the update process 400 can be performed between a server 410 (e.g., server 220 in Figure 2) and a UE 420 (e.g., UE 205 in Figure 2).
[0040]
[0053] Starting from arrow 425, device-specific information of the UE420 (e.g., which feature(single or multiple) information is required by the UE420 and / or a version indicator of the region file stored within the UE420) can be sent from the UE420 to the server 410. In some embodiments, the device-specific information of the UE420 may include a device capability report, such as supported constellations and / or signal bandwidth. In some embodiments, as described above, the UE420 may be preloaded with a first region file. The version indicator of the first region file may indicate the version number of the first region file and / or the timestamp of the last modification of the first region file.
[0041]
[0054] At arrow 435, in response to the determination that the first area file is different from the second area file stored on the server (e.g., the latest version of the area file), the second area file can be sent from server 410 to UE420. In some embodiments, the determination can be made based on comparing the version indicator of the first area file with the version indicator of the second area file. If the version indicator of the first area file is different from the version indicator of the second area file, the first area file and the second area file can be considered different area files.
[0042]
[0055] In some embodiments, a notification 427 for the second region file can be sent from the server 410 to the UE 420 before the second region file is sent. Upon receiving the notification, the UE 420 can initiate the update process (for example, by initiating the download of the second region file) by sending a request 429 for the second region file.
[0043]
[0056] In block 440, UE420 can perform authentication of the second area file received from server 410. In some embodiments, authentication can be performed based on a file signature contained within the second area file (e.g., the file header or any portion agreed upon by both server 410 and UE420).
[0044]
[0057] In some embodiments, after authenticating the second region file, the UE420 can compute a unique region identifier for each region provided in the second region file in order to obtain a unique region identifier. For example, the UE420 can compute a unique region identifier as a hash of selected common information from the header of the second region file (e.g., map version) and information specific to each region within the different regions contained in the second region file (e.g., one or more geopolygons used to represent the region, the geometric representation of each geopolygon among the one or more geopolygons, and associated properties).
[0045]
[0058] Figure 5 is a flowchart illustrating how geofencing restriction status files can be updated from a server or satellite for satellite-based communications, according to several embodiments. In some embodiments, the update process 500 can be performed between a server 510 (e.g., server 220 in Figure 2 and / or server 410 in Figure 4) and a UE 520 (e.g., UE205 in Figure 2 and / or UE420 in Figure 4).
[0046]
[0059] Starting from arrow 525, UE520 can check the restriction status file(s) in server 510. For example, UE520 can send a request to server 510 to check the restriction status file(s) in server 510. In some embodiments, a capability report indicating the satellite-related services supported by UE520 may also be included in the request.
[0047]
[0060] At arrow 535, server 510 may, upon request, provide a restriction file to UE520. In some embodiments, the restriction status file may include a list of unique region identifiers and restriction status information for each unique region identifier (e.g., restriction status information for regions corresponding to unique geopolygon identifiers represented by one or more geopolygons). Thus, the restriction status file may indicate the restriction status of one or more satellite-related services for UE520 in regions represented by one or more geopolygons for each different region corresponding to the list of unique region identifiers. In some embodiments, the restriction status file may be determined based on capability reports. For example, the restriction file may indicate information about satellite-related services supported by UE520 and the regions in question (e.g., a set of region identifiers corresponding to one or more regions indicated in the request).
[0048]
[0061] In block 540, UE520 can determine whether the information in UE520's first restriction status file is incomplete. For example, the first restriction file and the corresponding first region file can be preloaded and stored in UE520. The first restriction status file may contain restriction status information relating to a first list of unique region identifiers corresponding to a first set of multiple regions contained in the first region file. UE520 can compare the first list of unique region identifiers with the list of unique region identifiers contained in the restriction file received from server 510. If a difference is determined between the first list of unique geopolygon identifiers and the second list of unique geopolygon identifiers contained in the restriction status file received from server 510 (for example, if the second list of unique geopolygon identifiers is a subset of the unique geopolygon identifiers in the first list of unique geopolygon identifiers, or if one or more unique geopolygon identifiers in the second list of unique geopolygon identifiers are missing in the first list of unique geopolygon identifiers), then the information in UE520's first restriction file and / or area file may need to be updated.
[0049]
[0062] At arrow 545, in response to the determination that information in the first restriction file and / or region file needs updating, UE520 may send a request for missing information to server 510. For example, a missing / different unique region identifier in the first list of unique region identifiers may indicate that information about a new region is missing, or that information about available regions in the first list of unique region identifiers has been corrected, or that a region has been removed from the region in question. UE520 may request information about the missing region from server 510.
[0050]
[0063] At arrow 555, server 510 can provide requested information to UE 520. For example, the information may include the map version, geographical details of the area, and corresponding restriction status information associated with the area represented by one or more geopolygons.
[0051]
[0064] In block 560, UE520 may update or replace the first restriction status file according to the requested information received from server 510. For example, if in block 540 it is determined that a second list of unique geopolygon identifiers is a subset of the unique geopolygon identifiers in the first list of unique geopolygon identifiers, this may indicate that the satellite communication service restriction in the areas corresponding to the missing identifiers in the second set of unique geopolygon identifiers has been lifted. Therefore, UE520 may update the first area file and / or the first restriction status file by deleting the area details (e.g., geometric arrangement, characteristics) of the areas corresponding to those missing unique geopolygon identifiers in the second set of unique geopolygon identifiers from the first area file and / or the first restriction status file.
[0052]
[0065] In addition or alternatively, if block 540 determines that a second list of unique geopolygon identifiers includes one or more identifiers that are not part of the first set of unique geopolygon identifiers, this may indicate that data for the region corresponding to the new identifier is missing in the first region file and / or first restriction status file (e.g., one or more satellite communication service restrictions have been added to the region, and / or the region's boundaries have been redrawn or represented by different geopolygons). UE 520 may optionally request missing region data for the new identifier, as indicated by arrows 545 and 555, and replace the previous region data with the requested information. After updating the region file and / or restriction status file (e.g., obtaining the latest version of the region file and / or restriction status file), even if there is no ground network (e.g., hiking or traveling in a remote area, or moving in airplane mode), when roaming to a different region, UE can use the latest restriction status information for the target region based on the updated region file and restriction status file.
[0053]
[0066] Figure 6 is a flowchart illustrating how geofencing may be performed by a UE for satellite-based communications in several embodiments. In some embodiments, geofencing 600 can be performed by a UE (e.g., UE205 in Figure 2, UE420 in Figure 4, and / or UE520 in Figure 5).
[0054]
[0067] In some embodiments, before initiating geofencing 600, the UE may obtain the latest versions of the region files and / or restrict status files by receiving the region files and restrict status files from the server (e.g., updating the region files and / or restrict status files as shown in Figures 4 and / or 5), or by retrieving the region files and restrict status files from local storage / memory (e.g., preloading the latest versions of the region files and / or restrict status files).
[0055]
[0068] In some embodiments, geofencing 600 may begin in block 610, in which the target activity (e.g., satellite-based communications-related activity such as satellite messaging and / or Global Navigation Satellite System (GNSS) positioning) may be attempted by the UE.
[0056]
[0069] In block 620, the UE's position estimate and the uncertainty associated with the position estimate can be determined. In some embodiments, if a ground network is not available (e.g., when traveling in aircraft mode), the UE can use GNSS signals to determine its position estimate.
[0057]
[0070] In block 630, it is possible to determine one geopolygon from among multiple geopolygons contained in the region file that corresponds to the location estimate. In some embodiments, a list of candidate geopolygons associated with the location estimate (e.g., a subset of geopolygons that are close to the location estimate, taking into account the uncertainty associated with the location estimate) can be determined based on applying a supervised learning algorithm to the multiple geopolygons (e.g., applying a decision tree to the multiple geopolygons). The UE can then check the locations / points within each geopolygon in the subset of geopolygons (e.g., runpoints within each geopolygon in the subset of geopolygons).
[0058]
[0071] In block 640, you can obtain restriction status information for the corresponding geopolygon. For example, you can obtain restriction status information for the target activity based on the relevant restriction status file.
[0059]
[0072] In block 650, appropriate measures(s) may be taken based on the restriction status information. In some embodiments, appropriate measures(s) may include notifying the user of satellite messaging restrictions, removing GNSS bands affected by jamming or spoofing, etc.
[0060]
[0073] Figure 7 is a flowchart of a method 700 for updating geofencing in satellite-based communications, performed by a UE, according to several embodiments. In some embodiments, the UE may correspond to UE205 in Figure 2, UE420 in Figure 4, and / or UE520 in Figure 5. The means / structures that perform the functions shown in one or more of the blocks shown in Figure 7 may be performed by hardware and / or software components of the UE, as described herein. Exemplary components of the UE are shown in Figure 10, which are described in more detail below.
[0061]
[0074] In block 710, the function includes obtaining a first region file containing multiple regions, each of which is represented by one or more geopolygons, each of which corresponds to its own unique region identifier, and the multiple regions correspond to a first set of region identifiers. As described above, each region identifier may include the geometric arrangement and characteristics of the multiple geopolygons used to represent the region, as well as a hash of the map version indicator of the first region file.
[0062]
[0075] In some embodiments, multiple geopolygons within a first region file may correspond to different resolutions. When a higher resolution (e.g., geopolygons with vertices closer together) is used, more map detail of the region (e.g., a more accurate representation of the region's shape and size) can be shown. The boundaries of the region represented by the geopolygons can also be defined more accurately and in more detail. For example, when representing small islands or overlapping regions (e.g., regions within a region, such as Vatican City within Rome), geopolygons with finer resolutions can be used.
[0063]
[0076] In some embodiments, the geopolygons of the first region file can be represented using various standardized formats (e.g., GeoJSON, shapefile, KML, WKT). In some embodiments, the first region file may include a header containing the version number of the first region file, a timestamp of the last modification, a file signature, a content summary, high-level characteristics applicable to all geopolygons contained therein, or any combination thereof.
[0064]
[0077] In some embodiments, as described above, the first region file can be received from a server or retrieved from local storage / memory. For example, the first region file can be received from a server if the UE is in an area without restrictions in satellite-based communications and an area where ground network connectivity exists. Additionally or alternatively, the first region file can also be pre-programmed within the UE. In some embodiments, when transmitted (for example, to retrieve and / or update the first region file), the first region file can be converted to an extensible binary format using, for example, binary encoding for geographical data.
[0065]
[0078] Means for performing the functions in block 710 may include, as shown in Figure 10, the bus 1005, one or more processors 1010, a wireless communication interface 1030, memory 1060, and / or other components of the UE 1000.
[0066]
[0079] In block 720, the function includes obtaining a first restriction status file containing restriction status information for each of a plurality of regions, the first restriction status file showing the restriction status of one or more satellite-related services for a UE within the region represented by one or more geopolygons, for each of the plurality of regions.
[0067]
[0080] In some embodiments, as described above, the first restriction status file can be received from a server or retrieved from local storage / memory. For example, the first restriction status file can be received from a server when the UE is in an area without restrictions in satellite-based communications and an area where ground network connectivity exists. Additionally or alternatively, the first restriction status can also be pre-programmed within the UE.
[0068]
[0081] In some embodiments, the restriction status information may include information about different characteristics corresponding to whether satellite-based communications or positioning are permitted, whether satellite-based communications or positioning are affected, or any combination thereof.
[0069]
[0082] Means for performing the functions in block 720 may include, as shown in Figure 10, bus 1005, processor(s) 1010, wireless communication interface 1030, memory 1060, and / or other components of UE 1000.
[0070]
[0083] In block 730, the function includes receiving a second restriction status file from the server, which contains a second set of area identifiers and the corresponding restriction status.
[0071]
[0084] In some embodiments, before receiving the second limit status, method 700 may also include sending a request for a second limit status to the server, which indicates a version indicator of the first area file. In some embodiments, the request may indicate a capability report, which indicates satellite-related services supported by the UE. In some embodiments, the second limit status file may be determined based on the capability report (for example, customized to include limit status information regarding satellite-related services supported by the UE).
[0072]
[0085] In some embodiments, Method 700 may include sending a version indicator of a first area file to a server. Based on the version indicator of the first area file, the determination that the first area file is different from the second area file (for example, the version indicator of the first area file is different from the version indicator of the second area file) is made, and the second area file is received from the server. In some embodiments, Method 700 may also include authenticating the second area file received from the server (for example, based on a file signature contained in the header of the second area file).
[0073]
[0086] Means for performing the functions in block 730 may include, as shown in Figure 10, bus 1005, processor(s) 1010, wireless communication interface 1030, memory 1060, and / or other components of UE 1000.
[0074]
[0087] In block 740, the function includes determining the differences between a first set of region identifiers and a second set of region identifiers. For example, the UE can determine if the information in the first region file is incomplete. In some embodiments, the UE can compare a first list of unique region identifiers with a list of unique region identifiers contained in a second restriction file received from the server. If one or more region identifiers in the list of unique region identifiers contained in the second restriction file are missing from / different from the first list of unique region identifiers, then the information in the UE's first restriction file and region file may be incomplete.
[0075]
[0088] Means for performing the functions in block 740 may include, as shown in Figure 10, bus 1005, processor(s) 1010, wireless communication interface 1030, memory 1060, and / or other components of UE 1000.
[0076]
[0089] In block 750, the functionality includes updating the first region file, the first limit status file, or both, based on differences. For example, in response to a decision that information in the first limit file needs updating, the UE may, as described above, send a request to the server for corrected information regarding the missing information or regions available in the first list of unique region identifiers. For example, a missing / different unique region identifier in the first list of unique region identifiers may indicate that information about a region represented by one or more geopolygons is missing or corrected. The UE may request information from the server regarding the missing regions.
[0077]
[0090] Means for performing the functions in block 750 may include, as shown in Figure 10, a bus 1005, a processor(s) 1010, a wireless communication interface 1030, a memory 1060, and / or other components of the UE 1000.
[0078]
[0091] In some embodiments, method 700 may also include updating the first area file and / or the first limit status file based on the second area file and / or missing information received from the server.
[0079]
[0092] Figure 8 is a flowchart of a method for updating geofencing in satellite-based communications, performed by a server, according to several embodiments. In some embodiments, the server may correspond to Server 220 in Figure 2 and / or Server 410 in Figure 4. The means / structures that perform the functions shown in one or more of the blocks shown in Figure 8 may be performed by hardware and / or software components of a computer system, as described herein. Illustrative components of a computer system are shown in Figure 11, which are described in more detail below.
[0080]
[0093] In block 810, the function includes obtaining a first region file containing multiple regions, each of which is represented by one or more geopolygons, each of which corresponds to its own unique region identifier, and the multiple regions correspond to a first set of region identifiers.
[0081]
[0094] As described above, each region identifier may include the geopolygon details of the corresponding region and a hash of the version indicator of the first region file. The geopolygon details may include the geometric arrangement of each geopolygon within the region (e.g., the longitude and latitude of the vertices) along with region-specific characteristics.
[0082]
[0095] In some embodiments, multiple geopolygons within a first region file may correspond to different resolutions. When a higher resolution (e.g., geopolygons with vertices closer together) is used, more map detail of the region (e.g., a more accurate representation of the region's shape and size) can be shown. The boundaries of the region represented by the geopolygons can also be defined more accurately and in more detail. For example, when representing small islands or overlapping regions (e.g., regions within a region, such as Vatican City within Rome), geopolygons with finer resolutions can be used.
[0083]
[0096] In some embodiments, the geopolygons of the first region file can be represented using various standardized formats (e.g., GeoJSON, shapefile, KML, WKT). In some embodiments, the first region file may include a header containing the version number of the first region file, a timestamp of the last modification, a file signature, a content summary, high-level characteristics applicable to all geopolygons contained therein, or any combination thereof.
[0084]
[0097] In some embodiments, when transmitted (for example, to retrieve and / or update the first region file), the first region file can be converted to an extensible binary format using, for example, binary encoding for geographical data.
[0085]
[0098] Means for performing the functions in block 810 may include, as shown in Figure 11, a bus 1105, a processor(s) 1110, a communication subsystem 1130, a memory 1135, and / or other components of the computer system 1100.
[0086]
[0099] In block 820, the function includes obtaining a first restriction status file containing restriction status information for each of a plurality of regions, the first restriction status file showing the restriction status of one or more satellite-related services for a UE in the region represented by one or more geopolygons for each of the plurality of regions.
[0087]
[0100] In some embodiments, the restriction status information may include information about different characteristics corresponding to whether satellite-based communications or positioning are permitted, whether satellite-based communications or positioning are affected, or any combination thereof.
[0088]
[0101] Means for performing the functions in block 820 may include, as shown in Figure 11, a bus 1105, a processor(s) 1110, a communication subsystem 1130, a memory 1135, and / or other components of the computer system 1100.
[0089]
[0102] In block 830, the function includes receiving a request for restriction status information from the target UE regarding one or more of a plurality of regions. In some embodiments, the request may include a capability report indicating the satellite-related services supported by the target UE, and the first restriction status file may be determined based on the capability report (for example, customized to include restriction status information regarding the satellite-related services supported by the target UE).
[0090]
[0103] Means for performing the functions in block 830 may include, as shown in Figure 11, a bus 1105, a processor(s) 1110, a communication subsystem 1130, a memory 1135, and / or other components of the computer system 1100.
[0091]
[0104] In block 840, the function includes sending a first restriction status file to the target UE in response to receiving a request. For example, the target UE can determine if the information in a second restriction file stored within the target UE is incomplete. In some embodiments, the target UE can compare a first list of unique region identifiers with a list of unique region identifiers contained in a second restriction file. If one or more region identifiers in the list of unique region identifiers contained in the first restriction file are missing / different from the second list of unique region identifiers, the information in the target UE's second first restriction file may be incomplete. In response to a determination that at least one region identifier from the first set of region identifiers is not available in the second set of region identifiers in the second restriction status file stored within the target UE, the server sends geopolygon restriction status information corresponding to at least one geopolygon identifier to the target UE. For example, in response to a determination that the information in the second restriction file is incomplete, the server can receive a request for missing information from the target UE.
[0092]
[0105] Means for performing the functions in block 850 may include, as shown in Figure 11, a bus 1105, a processor(s) 1110, a communication subsystem 1030, a memory 1135, and / or other components of the computer system 1100.
[0093]
[0106] Figure 9 is a flowchart of a method for using geofencing in satellite-based communications, performed by a UE, according to several embodiments. In some embodiments, the UE may correspond to UE205 in Figure 2, UE420 in Figure 4, and / or UE520 in Figure 5. The means / structures that perform the functions shown in one or more of the blocks shown in Figure 9 may be performed by hardware and / or software components of the UE, as described herein. Exemplary components of the UE are shown in Figure 10, which are described in more detail below.
[0094]
[0107] In block 910, the function includes obtaining a region file containing multiple regions, each of which is represented by one or more geopolyons, each of which corresponds to its own unique region identifier, and the multiple regions correspond to a first set of region identifiers.
[0095]
[0108] Means for performing the functions in block 910 may include, as shown in Figure 10, bus 1005, processor(s) 1010, wireless communication interface 1030, memory 1060, and / or other components of UE 1000.
[0096]
[0109] In block 920, the function includes obtaining a restriction status file containing restriction status information for each of a plurality of regions, the first restriction status file showing the restriction status of one or more satellite-related services for a UE in the region represented by one or more geopolygons, for each of the plurality of regions.
[0097]
[0110] Means for performing the functions in block 920 may include, as shown in Figure 10, bus 1005, processor(s) 1010, wireless communication interface 1030, memory 1060, and / or other components of UE 1000.
[0098]
[0111] In block 930, the function includes determining a location estimate for the UE and the uncertainty associated with the location estimate. In some embodiments, if a ground network is not available (for example, hiking or traveling in a remote area, or moving in airplane mode), the UE can use GNSS signals to determine its location estimate.
[0099]
[0112] Means for performing the functions in block 930 may include, as shown in Figure 10, bus 1005, processor(s) 1010, wireless communication interface 1030, memory 1060, and / or other components of UE 1000.
[0100]
[0113] In block 940, the function includes determining the corresponding geopolygon among multiple geopolygons in the region file that corresponds to the location estimate, based on the location estimate and the uncertainty associated with the location estimate.
[0101]
[0114] In some embodiments, a list of candidate geopolyons associated with a location estimate (e.g., a subset of geopolyons close to the location estimate, taking into account the uncertainty associated with the location estimate) can be determined by applying a supervised learning algorithm to multiple geopolyons (e.g., using a decision tree for multiple geopolyons). The UE can then check the locations / points within each geopolyon in the subset of geopolyons (e.g., runpoints within each geopolyon in the subset of geopolyons).
[0102]
[0115] Means for performing the functions in block 940 may include, as shown in Figure 10, bus 1005, processor(s) 1010, wireless communication interface 1030, memory 1060, and / or other components of UE 1000.
[0103]
[0116] In block 950, the function includes retrieving restriction status information for the corresponding geopolygon based on the restriction status file. For example, restriction status information for the target activity can be retrieved based on the relevant restriction status file.
[0104]
[0117] Means for performing the functions in block 950 may include, as shown in Figure 10, bus 1005, processor(s) 1010, wireless communication interface 1030, memory 1060, and / or other components of UE 1000.
[0105]
[0118] In some embodiments, method 900 may also include taking appropriate measures(s) based on restriction status information. In some embodiments, appropriate measures(s) may include notifying the user of satellite messaging restrictions, removing GNSS bands affected by jamming or spoofing, etc.
[0106]
[0119] Figure 10 is a block diagram of one embodiment of UE1000 that may be used as described herein (for example, in relation to the figures above). In some embodiments, for example, UE1000 may include, for example, a mobile (e.g., portable) device (e.g., a tablet, laptop, vehicle, etc.). Note that Figure 10 is intended only to provide a generalized example of various components, and any or all of those components may be used as needed.
[0107]
[0120] UE1000 is shown as comprising hardware elements that can be electrically coupled (or, if necessary, communicate) via bus 1005. The hardware elements may include, but are not limited to, one or more general-purpose processors (e.g., application processors), one or more dedicated processors (such as digital signal processor (DSP) chips, graphics acceleration processors, application-specific integrated circuits (ASICs)), and / or other processing structures or means, and may include a processor(s) 1010. The processor(s) 1010 may include one or more processing units that can be housed in a single integrated circuit (IC) or multiple Ic. As shown in Figure 10, some embodiments may have a separate DSP 1020 depending on the desired functionality. Location determination and / or other determinations based on wireless communication may be provided in the processor(s) 1010 and / or the wireless communication interface 1030 (discussed below). The UE1000 may also include, but is not limited to, one or more input devices 1070, which may include one or more keyboards, touchscreens, touchpads, microphones, buttons, dials, switches, etc., and one or more output devices 1015, which may include, but is not limited to, one or more displays (e.g., touchscreens), light-emitting diodes (LEDs), speakers, etc.
[0108]
[0121] The UE1000 may also include, but is not limited to, a wireless communication interface 1030 which may include a modem, network card, infrared communication device, wireless communication device, and / or chipset (such as a Bluetooth® device, IEEE 802.11 device, IEEE 802.15.4 device, Wi-Fi device, WiMAX device, WAN device, and / or various cellular devices), which may enable the UE1000 to communicate with other devices as described in the embodiments above. The wireless communication interface 1030 may enable data and signaling to be communicated (e.g., transmitted and received) with base stations of the network via, for example, eNBs, gNBs, ng-eNBs, access points, various base stations and / or other access node types, and / or other network components, computer systems, and / or any other electronic devices that are communicably coupled to base stations. Communication can be performed via one or more wireless communication antennas 1032 that send and / or receive wireless signals 1034. According to some embodiments, the wireless communication antennas 1032 may include a plurality of individual antennas, an antenna array, or any combination thereof. The antennas 1032 may be capable of sending and receiving wireless signals using beams (e.g., a Tx beam and an Rx beam). Beamforming can be performed using digital and / or analog circuits, respectively, and using digital and / or analog circuits, and using digital and / or analog beamforming techniques. The wireless communication interface 1030 may include such circuits.
[0109]
[0122] Depending on the desired functionality, the wireless communication interface 1030 may comprise separate receivers and transmitters, or any combination of transceivers, transmitters, and / or receivers, for communication with base stations (e.g., ng-eNB and gNB) and other terrestrial transceivers such as wireless devices and access points. The UE 1000 can communicate with various data networks, which may include a variety of network types. For example, one such network type may include a wireless wide area network (WWAN), which could 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, a WiMAX (IEEE 802.16) network, and so on. CDMA networks can implement one or more radio access technologies (RATs), such as CDMA2000®, wideband code division multiple access (WCDMA), etc. CDMA2000® includes the IS-95 standard, IS-2000 standard, and / or IS-856 standard. TDMA networks can implement Pan-European Digital Mobile Telephone System (GSM), digital advanced mobile phone system (D-AMPS), or any other RAT. OFDMA networks can adopt Long-Term Evolution (LTE), LTE Advanced, 5G New Radio (NR), etc. 5G NR, LTE, LTE Advanced, GSM, and WCDMA are part of the 3rd Generation Partnership Project (3 rdThis is explained in a document by the Generation Partnership Project (3GPP). CDMA2000 (registered trademark) is described in the "Third Generation Partnership Project 2" (3GPP). rd This is described in a document by a consortium called Generation Partnership Project 2 (3GPP2). 3GPP and 3GPP2 documents are publicly available. A wireless local area network (WLAN) can also be an IEEE 802.11x network, and a wireless personal area network (WPAN) can be a Bluetooth network, IEEE 802.15x, or any other type of network. The technologies described herein can also be used with respect to any combination of WWAN, WLAN, and / or WPAN.
[0110]
[0123] The UE1000 may further include one or more sensors 1040. The sensors 1040 may include, but are not limited to, one or more inertial sensors and / or other sensors (e.g., one or more accelerometers, one or more gyroscopes, one or more cameras, one or more magnetometers, one or more altimeters, one or more microphones, one or more proximity sensors, one or more optical sensors, one or more barometers, etc.), some of which can be used to acquire position-related measurements and / or other information.
[0111]
[0124] Embodiments of UE1000 may further include a sensing unit 1050. The sensing unit 1050 may include hardware and / or software components capable of transmitting and / or receiving RF signals (e.g., RS) to detect one or more targets in the manner described herein. The sensing unit 1050 may include a standalone component connected to bus 1005, as shown in the figures, or it may be incorporated within another component (e.g., wireless display interface 1030). Furthermore, the sensing unit 1050 may be communicatively coupled to antenna 1032, which may be shared with wireless communication interface 1030. Additionally or alternatively, the sensing unit 1050 may have its own antenna (not shown). In some embodiments, the sensing unit 1050 may be communicatively coupled to a plurality of antennas or antenna arrays capable of transmitting and / or receiving RF signals via a directional beam.
[0112]
[0125] Embodiments of the UE1000 may also include a GNSS receiver 1080 capable of receiving signals 1084 from one or more Global Navigation Satellite System (GNSS) satellites using an antenna 1082 (which may be the same as antenna 1032). Positioning based on GNSS signal measurement can be utilized to complement and / or incorporate the techniques described herein. The GNSS receiver 1080 can use conventional techniques to extract the position of the UE1000 from GNSS satellites of GNSS systems such as the Global Positioning System (GPS), Galileo, GLONASS, the Quasi-Zenith Satellite System (QZSS) over Japan, the IRNSS over India, and the BeiDou Navigation Satellite System (BDS) over China. Furthermore, the GNSS receiver 1080 can be used with a variety of augmentation systems (e.g., Satellite Based Augmentation Systems, SBAS) that can be associated with, or enable use with, one or more global navigation satellite systems and / or regional navigation satellite systems, such as the Wide Area Augmentation System (WAAS), the European Geostationary Navigation Overlay Service (EGNOS), the Multi-functional Satellite Augmentation System (MSAS), and the Geo Augmented Navigation system (GAGAN).
[0113]
[0126] Although the GNSS receiver 1080 is shown as a separate component in Figure 10, it should be noted that embodiments are not limited thereto. As used herein, the term “GNSS receiver” may include hardware and / or software components configured to acquire GNSS measurements (measurements from GNSS satellites). Therefore, in some embodiments, the GNSS receiver may include a measurement engine, which is run (as software) by one or more processors, such as processor(s) 1010, DSP 1020, and / or a processor in the wireless communication interface 1030 (e.g., in a modem). The GNSS receiver may also optionally include a positioning engine, which may use GNSS measurements from the measurement engine to determine the position of the GNSS receiver, using methods such as an Extended Kalman Filter (EFK), Weighted Least Squares (WLS), or particle filter. The positioning engine can also be run by one or more processors, such as processor(s) 1010 or DSP1020.
[0114]
[0127] The UE1000 may further include and / or communicate with memory 1060. Memory 1060 may include, but is not limited to, local storage and / or network-accessible storage, disk drives, drive arrays, optical memory devices, 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 suitable data store, including, but is not limited to, various file systems, database structures, etc.
[0115]
[0128] Memory 1060 of the UE1000 may also contain software elements (not shown in Figure 10), including other code such as an operating system, device drivers, executable libraries, and / or one or more application programs, which may include computer programs provided by various embodiments as described herein and / or may be designed to implement methods provided by other embodiments and / or to constitute a system provided by other embodiments. Just as an example, one or more steps described with respect to the methods (one or more) discussed above may be implemented as code and / or instructions in memory 1060 that can be executed by the UE1000 (and / or a processor (one or more) 1010 or DSP 1020 within the UE1000). In some embodiments, such code and / or instructions can then be used to configure and / or adapt a general-purpose computer (or other device) to perform one or more operations according to the methods described.
[0116]
[0129] Figure 11 is a block diagram of one embodiment of a computer system 1100 that can be used whole or in part to provide the functionality of one or more components and / or devices as described in the embodiments herein, including a server (e.g., a sensing server / SMF, a location server / LMF, etc.) that communicates with one or more base stations and / or one or more sensing nodes to coordinate RF sensing as described in the embodiments herein. This computer system may include, for example, a computer server, a personal computer, a personal electronic device, etc. Note that Figure 11 is intended only to provide a generalized example of various components, and any or all of those components can be used as needed. Therefore, Figure 11 broadly illustrates how individual system elements can be implemented in a relatively isolated or relatively more integrated manner. Furthermore, note that the components shown in Figure 11 can be localized into a single device and / or distributed among various networked devices that can be located in geographically different locations.
[0117]
[0130] The computer system 1100 is shown to include hardware elements that can be electrically coupled (or communicate as needed) via a bus 1105. The hardware elements may include, but are not limited to, one or more general-purpose processors, one or more dedicated processors (such as digital signal processing chips, graphics acceleration processors), and / or other processing structures that can be configured to perform one or more of the methods described herein. The computer system 1100 may also include, but are not limited to, one or more input devices 1115 that may include a mouse, keyboard, camera, microphone, etc., and one or more output devices 1120 that may include a display device, printer, etc.
[0118]
[0131] The computer system 1100 may further include (and / or communicate with) one or more non-temporary storage devices 1125, which may include, but are not limited to, local storage and / or network-accessible storage, and / or, but are not limited to, solid-state storage devices such as disk drives, drive arrays, optical storage devices, 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 suitable data store, including, but are not limited to, various file systems, database structures, etc. Such data stores may include one or more databases and / or other data structures used to store and manage messages and / or other information that will be sent to one or more devices via a hub, as described herein.
[0119]
[0132] The computer system 1100 may also include a communications subsystem 1130, which may include wireless communications technology managed and controlled by a wireless communications interface 1133, as well as wired communications technology (such as Ethernet, coaxial communications, and universal serial bus (USB)). The wireless communications interface 1133 may include one or more wireless transceivers capable of transmitting and receiving wireless signals 1155 (e.g., signals according to 5G NR or LTE) via one or more wireless antennas 1150. Thus, the communications subsystem 1130 may include modems, network cards (wireless or wired), infrared communications devices, wireless communications devices, and / or chipsets, etc., which may enable the computer system 1100 to communicate with any device on any of the communications networks described herein, including user equipment (UEs), base stations and / or other transmission reception points (TRPs), and / or any other electronic devices described herein. Therefore, the communication subsystem 1130 can be used to receive and transmit data, as described in the embodiments of this specification.
[0120]
[0133] In many embodiments, the computer system 1100 further includes working memory 1135, which may include RAM or ROM devices as described above. Software elements shown as residing in the working memory 1135 may include other code such as an operating system 1140, device drivers, executable libraries, and / or one or more applications 1145, which may include computer programs provided by various embodiments as described herein and / or may be designed to implement methods provided by other embodiments and / or to constitute a system provided by other embodiments. Just as an example, one or more procedures described with respect to the methods (one or more) discussed above can be implemented as code and / or instructions executable by a computer (and / or a processor in the computer), and in one embodiment, such code and / or instructions can then be used to configure and / or adapt a general-purpose computer (or other device) to perform one or more operations according to the methods described.
[0121]
[0134] These instructions and / or sets of code may be stored on a non-temporary computer-readable storage medium, such as the storage device(s) 1125 described above. In some cases, the storage medium may be incorporated into a computer system, such as computer system 1100. In other embodiments, the storage medium may be separate from the computer system (e.g., a removable medium such as an optical disc) and / or provided in an installation package, so that the storage medium can be used to program, configure, and / or adapt a general-purpose computer using the instructions / code stored on it. These instructions may take the form of executable code that can be executed by computer system 1100, and / or take the form of source code and / or installable code, which, when compiled and / or installed on computer system 1100 (e.g., using one of various commonly available compilers, installation programs, compression / decompression utilities, etc.), take the form of executable code.
[0122]
[0135] In some embodiments, geofencing can also be performed in a cloud-based manner. For example, if a UE attempts a target activity (e.g., satellite messaging), the restriction status applicable to the UE may be determined by a server based on satellite-related service parameters determined based on the UE's location (e.g., a location estimate determined by the UE along with the associated uncertainties) and the UE's unique identifier (e.g., International Mobile Equipment Identity (IMEI)). In some embodiments, the satellite-related service parameters may include a restriction applicable time window (e.g., the time period during which the restriction should be enforced), a unique identifier for the device to which the restriction applies, the applicable restriction, or any combination thereof. As described above, in some embodiments, the applicable restriction may include whether satellite communications are permitted or have transmission power level limits, whether satellite-based positioning is permitted or affected by intentional or unintentional interference, the level of service permitted (e.g., whether only emergency communications are permitted, or whether person-to-person messaging is also permitted), or any combination thereof.
[0123]
[0136] For example, Figure 12 is a flowchart illustrating how cloud-based geofencing may be performed by a server for satellite-based communications according to several embodiments. In some embodiments, cloud-based geofencing 1200 can be performed by a server (e.g., server 220 in Figure 2, server 410 in Figure 4, and / or server 510 in Figure 5).
[0124]
[0137] In some embodiments, before initiating cloud-based geofencing 1200, the server may obtain the latest versions of the area file and / or the restriction status file, including satellite-related service parameters, through an application programming interface (API) exposed to a trusted entity (e.g., a government agency). The server may also obtain the location estimate and uncertainty of the location estimate, as well as the unique identifier of the UE, from the UE. In some embodiments, the location estimate, uncertainty, and unique identifier of the UE may be received along with the data to be transmitted by the UE through a satellite associated with the UE (e.g., a satellite receiving packets from the UE).
[0125]
[0138] In some embodiments, cloud-based geofencing 1200 can begin in block 1210, where a unique region identifier corresponding to the UE's location estimate can be determined according to a region file. For example, a list of candidate geopolygons associated with the location estimate (e.g., a subset of geopolygons close to the location estimate, taking into account the uncertainty associated with the location estimate) can be determined based on applying a supervised learning algorithm to multiple geopolygons (e.g., applying a decision tree to multiple geopolygons). The server can then check the locations / points within each geopolygon in the subset of geopolygons (e.g., runpoints within each geopolygon in the subset of geopolygons) to determine which region encompasses the UE's location estimate. The unique identifier of the determined region can then be used to determine the restriction status applicable to the UE.
[0126]
[0139] In block 1220, the restriction status, including satellite-related service parameters applicable to the UE, can be determined based on a unique domain identifier and a unique identifier for the UE. For example, the applicable restriction status, including satellite-related service parameters, can be determined based on the restriction status information corresponding to the unique domain identifier in the restriction status file, and the satellite-related service parameters applicable to the UE can be determined according to the unique identifier for the UE.
[0127]
[0140] In some embodiments, in block 1225, the server can directly apply the restriction status applicable to the UE to the UE. For example, data transmitted by the UE may be routed according to the applicable restriction status.
[0128]
[0141] As an addition or alternative, in block 1230, the server may notify the UE of applicable restriction statuses, in which case the UE can enforce those applicable restriction statuses. For example, the server may notify the UE of applicable restriction statuses such as transmit power level limits (e.g., the maximum power level allowed for transmission) and satellites available to the UE, and the UE can enforce those restrictions when it attempts to reconnect.
[0129]
[0142] Figure 13 is a flowchart of a method for using cloud-based geofencing in satellite-based communications, performed by a server, according to several embodiments. In some embodiments, the server may correspond to server 220 in Figure 2, server 410 in Figure 4, and / or the server discussed with respect to Figure 12. The means / structures that perform the functions shown in one or more of the blocks shown in Figure 13 may be performed by hardware and / or software components of a computer system, as described herein. Illustrative components of a computer system are shown in Figure 11, and these components are described above.
[0130]
[0143] In block 1310, the function includes obtaining a region file containing multiple regions, each of which is represented by one or more geopolyons, each of which corresponds to its own unique region identifier, and the multiple regions correspond to a first set of region identifiers.
[0131]
[0144] Means for performing the functions in block 1310 may include, as shown in Figure 11, a bus 1105, a processor(s) 1110, a communication subsystem 1030, a memory 1135, and / or other components of the computer system 1100.
[0132]
[0145] In block 1320, the function includes obtaining a restriction status file containing restriction status information for each of a plurality of regions, the first restriction status file showing the restriction status of one or more satellite-related services for a UE in the region represented by one or more geopolygons, for each of the plurality of regions.
[0133]
[0146] Means for performing the functions in block 1320 may include, as shown in Figure 11, a bus 1105, a processor(s) 1110, a communication subsystem 1030, a memory 1135, and / or other components of the computer system 1100.
[0134]
[0147] In block 1330, the function includes obtaining the location estimate of the target UE and a unique identifier for the target UE. As described above, the server can also obtain the location estimate of the target UE, the uncertainty of the location estimate, and a unique identifier from the target UE. In some embodiments, the location estimate, the uncertainty of the location estimate, and the unique identifier can be received along with data to be transmitted by the target UE through a satellite associated with the target UE.
[0135]
[0148] Means for performing the functions in block 1330 may include, as shown in Figure 11, a bus 1105, a processor(s) 1110, a communication subsystem 1030, a memory 1135, and / or other components of the computer system 1100.
[0136]
[0149] In block 1340, the function includes determining a unique region identifier corresponding to the UE's location estimate. For example, a list of candidate geopolyons associated with the location estimate (e.g., a subset of geopolyons close to the location estimate, taking into account the uncertainty associated with the location estimate) can be determined based on applying a supervised learning algorithm to multiple geopolyons (e.g., applying a decision tree to multiple geopolyons). The server can then check the locations / points within each geopolyon in the subset of geopolyons (e.g., runpoints within each geopolyon in the subset of geopolyons) to determine which region encompasses the UE's location estimate. The unique identifier of the determined region can then be used to determine the restriction status applicable to the UE.
[0137]
[0150] Means for performing the functions in block 1330 may include, as shown in Figure 11, a bus 1105, a processor(s) 1110, a communication subsystem 1030, a memory 1135, and / or other components of the computer system 1100.
[0138]
[0151] In block 1350, the function includes determining a restriction status, including satellite-related service parameters applicable to the target UE, based on a unique area identifier and a unique identifier for the target UE, according to a restriction status file. In some embodiments, the satellite-related service parameters may include a restriction applicable time window (e.g., the time period during which the restriction should be enforced), a unique identifier relating to the device to which the restriction applies (e.g., IMEI), the applicable restriction, or any combination thereof. As described above, in some embodiments, the applicable restriction may include whether satellite communications are permitted, a transmit power level restriction, whether satellite-based positioning is permitted, the level of services permitted (e.g., whether only emergency communications are permitted, or whether person-to-person messaging is also permitted), or any combination thereof.
[0139]
[0152] Means for performing the functions in block 1340 may include, as shown in Figure 11, a bus 1105, a processor(s) 1110, a communication subsystem 1030, a memory 1135, and / or other components of the computer system 1100.
[0140]
[0153] As described above, in some embodiments, after determining the applicable restriction status for the target UE, the server can directly apply the applicable restriction status to the target UE. For example, data transmitted by the target UE may be routed according to the applicable restriction status.
[0141]
[0154] As an addition or alternative, the server may notify the target UE of applicable restriction statuses, in which case the target UE can enforce those restrictions. For example, the server may notify the target UE of applicable restriction statuses, such as transmit power level limits (e.g., the maximum power level allowed for transmits) and the satellites available to the target UE, and the target UE can enforce those restrictions when it attempts to reconnect.
[0142]
[0155] Those skilled in the art will see that significant modifications can be made according to specific requirements. For example, customized hardware can also be used, and / or certain elements can be implemented in hardware, software (including portable software such as applets), or both. Furthermore, connections to other computing devices, such as network input / output devices, can be employed.
[0143]
[0156] Referring to the attached diagram, components that may include memory may also include non-temporary machine-readable media. The terms “machine-readable media” and “computer-readable media,” as used herein, refer to any storage medium involved in providing data that operates a machine in a particular manner. In the embodiments provided above, various machine-readable media may be involved in providing instructions / code to a processor and / or other device(s) for execution. Additionally or alternatively, machine-readable media may also be used to store and / or carry such instructions / code. In many implementations, computer-readable media are physical and / or tangible storage media. Such media can take many forms, including, but not limited to, non-volatile and volatile media. Common forms of computer-readable media include, for example, magnetic media and / or optical media, any other physical media having a pattern of holes, RAM, programmable ROM (PROM), erasable PROM (EPROM), FLASH-EPROM, any other memory chip or cartridge, or any other media from which a computer can read instructions and / or code.
[0144]
[0157] The methods, systems, and devices discussed herein are examples. Various embodiments may omit, substitute, or add various procedures or components as needed. For example, features described in relation to a particular embodiment may be combined in various other embodiments. Different aspects and elements of embodiments may be combined in the same way. Various components of the figures provided herein can be embodied in hardware and / or software. Furthermore, since technology is evolving, many of these elements are examples and do not limit the scope of this disclosure to their specific examples.
[0145]
[0158] It has been found that, primarily due to common usage, it is sometimes convenient to refer to such signals as bits, information, values, elements, symbols, characters, variables, terms, numbers, numerical values, etc. However, it should be understood that all of these terms, or similar terms, should be associated with appropriate physical quantities and are merely labels for convenience. Unless otherwise specified, as is evident from the above discussion, discussions throughout this specification using terms such as “process,” “calculate,” “calculate,” “determine,” “verify,” “identify,” “relevant,” “measure,” and “execute” will be understood to refer to actions or processes of specific devices, such as dedicated computers or similar dedicated electronic computing devices. Therefore, in the context of this specification, dedicated computers or similar dedicated electronic computing devices can manipulate or transform signals, typically represented as physical electronic, electric, or magnetic quantities, within their memory, registers, or other information storage devices, transmitting devices, or display devices.
[0146]
[0159] The terms “and” and “or,” as used herein, may have a variety of meanings, which are also expected to depend at least in part on the context in which such terms are used. Typically, when “or,” used to relate a list such as A, B, or C, is intended to mean A, B, and C in an inclusive sense, as well as A, B, or C in an exclusive sense. Furthermore, the term “one or more,” as used herein, may be used to describe any feature, structure, or characteristic in the singular, or to describe any combination of features, structures, or characteristics. However, it should be noted that these are merely illustrative examples, and the claimed subject matter is not limited to these examples. Furthermore, when the term “at least one of” is used to relate a list such as A, B, or C, it may be interpreted to mean any combination of A, B, and / or C, such as A, AB, AA, AAB, AABBCCC, etc.
[0147]
[0160] While several embodiments have been described, various modifications, alternative configurations, and equivalents can be used without departing from the scope of this disclosure. For example, the elements described above are merely components of a larger system, and other rules may take precedence over or modify the application of various embodiments. Furthermore, several steps can be taken before, during, or after considering the elements described above. Therefore, the above description does not limit the scope of this disclosure.
[0148]
[0161] In light of this description, embodiments may include combinations of different features. Examples of implementations are described in the following numbered clauses.
[0149] A method for performing exemplary geofencing relating to satellite communications, as performed by a UE, comprising obtaining a first domain file containing a plurality of domains, each of which is represented by one or more geopolygons, each of which corresponds to its own unique domain identifier, and each of which corresponds to a first set of domain identifiers. The method also comprises obtaining a first restriction status file containing restriction status information relating to each of which domains, wherein the first restriction status file indicates, with respect to each of which domains, the restriction status of one or more satellite-related services for a UE in a domain represented by one or more geopolygons. The method further comprises receiving a second restriction status file from a server, containing a second set of domain identifiers and corresponding restriction status information, determining the difference between the first set of domain identifiers and the second set of domain identifiers, and updating the first domain file, the first restriction status file, or both, based on the difference.
[0150] Clause 2. The method of Clause 1 further includes sending a request for a second limit status file to the server before receiving the second limit status file, the request indicating a version indicator for the first limit file.
[0151] Clause 3. Either method of Clause 1 or 2, further comprising sending a version indicator of the first area file to the server, receiving the second area file from the server in accordance with the determination, based on the version indicator of the first area file, that the first area file is different from the second area file, and authenticating the second area file received from the server.
[0152] Clause 4. Each region identifier in the second set of region identifiers includes the region details of the corresponding one or more geopolygons and a hash of the version indicator of the second region file, in any way from Clauses 1 to 3.
[0153] Clause 5. The region details of one or more corresponding geopolygons include the geometric arrangement and characteristics of the one or more corresponding geopolygons representing the region, in any way from Clauses 1 to 4.
[0154] Clause 6. Obtaining the first region file further includes any method of Clauses 1 to 5, wherein obtaining the first region file further includes receiving the first region file from the server or retrieving the first region file from local memory.
[0155] Clause 7. One or more geopolyons correspond to different resolutions in any of the manner described in Clauses 1 through 6.
[0156] Clause 8. Restriction status information includes information about different features, and the different features correspond to whether satellite-based communications are permitted or affected by the provider, whether satellite-based positioning is affected, or any combination thereof, in any way of Clauses 1 through 7.
[0157] Clause 9. Further including sending a capability report to the server indicating the satellite-related services supported by the UE, and a second limit status file determined based on the capability report, in any way of Clauses 1-8.
[0158] Clause 10. The header of the first region file includes data indicating the version indicator of the first region file, the timestamp of the most recent update of the first region file, the file signature of the first region file, a summary of the content provided within the first region file, characteristics applicable to one or more geopolygons, or any combination thereof, in any way of any of Clauses 1 to 9.
[0159] Clause 11. The second area file is transmitted in an extensible binary format, using any of the methods described in Clauses 1 through 10.
[0160] Clause 12. A method, performed by a server, that exemplifies geofencing relating to satellite communications, comprising obtaining a first domain file containing a plurality of domains, each of which domains is represented by one or more geopolygons, each of which domains corresponds to its own unique domain identifier, and the plurality of domains corresponds to a first set of domain identifiers. The method also comprises obtaining a first restriction status file containing restriction status information relating to each of the plurality of domains, wherein the first restriction status file indicates, with respect to each of the plurality of domains, the restriction status of one or more satellite-related services for a UE in a domain represented by one or more geopolygons. The method further comprises receiving a request for restriction status information relating to one or more of the plurality of domains from a target UE, and, in response to receiving the request, transmitting the first restriction status file to the target UE.
[0161] The method of Clause 12, further comprising receiving a version indicator of a second area file stored within the UE from the UE, and transmitting the first area file to the UE in response to a determination, made based on the version indicator of the second area file, that the first area file is different from the second area file.
[0162] Clause 14. Each region identifier in the first set of region identifiers includes the region details of one or more geopolygons and a hash of the version indicator of the first region file, in either way of Clause 12 or 13.
[0163] Clause 15. The region details of one or more corresponding geopolygons include the geometric arrangement and characteristics of the one or more corresponding geopolygons representing the region, in any way from Clauses 12 to 14.
[0164] Clause 16. One or more geopolyons correspond to different resolutions in any of the manner described in Clauses 12-15.
[0165] Clause 17. Restriction status information includes information about different features, and the different features correspond to whether satellite-based communications are permitted or affected by the provider, whether satellite-based positioning is affected, or any combination thereof, in any way of Clauses 12-16.
[0166] Clause 18. Further including receiving a capability report from the UE indicating the satellite-related services supported by the UE, the first limitation status file is determined based on the capability report, in any way of Clauses 12-17.
[0167] Clause 19. The header of the first region file includes data indicating the version indicator of the first region file, the timestamp of the most recent update of the first region file, the file signature of the first region file, a summary of the content provided within the first region file, characteristics applicable to one or more geopolygons, or any combination thereof, in any way described in Clauses 12 to 18.
[0168] Clause 20. The first area file is transmitted in an extensible binary format, using any of the methods described in Clauses 12-19.
[0169] Clause 21. An exemplary method of geofencing relating to satellite communications, performed by a UE, comprising obtaining a region file containing a plurality of regions, each of which is represented by one or more geopolygons, and each of which corresponds to its respective unique region identifier. The method also comprises obtaining a restriction status file containing restriction status information for each of which regions, the restriction status file indicating, with respect to each of which regions, the restriction status file indicating the restriction status of one or more satellite-related services for the UE in the region represented by one or more geopolygons. The method further comprises determining a location estimate for the UE and the uncertainty associated with the location estimate, determining the corresponding geopolygon among the one or more geopolygons in the region file corresponding to the location estimate based on the location estimate and the uncertainty associated with the location estimate, and obtaining restriction status information for the corresponding geopolygon based on the restriction status file.
[0170] The method of Clause 21, further comprising determining the corresponding geopolygon, by identifying a subset of geopolygons that correspond to a location estimate based on applying a supervised learning algorithm to one or more geopolygons, and determining the corresponding geopolygon by checking the location within each geopolygon of the subset geopolygon.
[0171] Clause 23. A method for exemplary cloud-based geofencing relating to satellite communications, performed by a server, comprising obtaining a region file containing a plurality of regions, each of which is represented by one or more geopolygons, and each of which corresponds to its respective unique region identifier. The method also comprises obtaining a restriction status file containing restriction status information for each of the plurality of regions, wherein the restriction status file indicates, with respect to each of the plurality of regions, the restriction status status of one or more satellite-related services for a UE in a region represented by one or more geopolygons. The method further comprises obtaining a location estimate for the target UE and a unique identifier for the target UE; determining a unique region identifier corresponding to the location estimate for the UE according to the region file; and determining a restriction status, including satellite-related service parameters applicable to the target UE, based on the unique region identifier and the unique identifier for the target UE, according to the restriction status file.
[0172] Clause 24. The method of Clause 23, wherein satellite-related service parameters include a limited applicable time window, a unique identifier relating to the device to which the limit applies, applicable limits, or any combination thereof.
[0173] Clause 25. Any applicable restrictions include, in any way, those of Clause 23 or 24, whether satellite communications are permitted by the provider, transmission power level restrictions, whether satellite-based positioning is permitted or affected, the level of service permitted, or any combination thereof.
[0174] Clause 26. Any method of Clauses 23-25, further including applying the applicable restriction status to the target UE.
[0175] Clause 27. Any method of Clauses 23-26, further including notifying the target UE of the applicable restriction status.
[0176] Clause 28. An exemplary UE for geofencing relating to satellite communications comprises a transceiver, memory, and one or more processors communicatively coupled to the transceiver and memory. The one or more processors are configured to obtain a first region file containing a plurality of regions, each of which regions is represented by one or more geopolygons, each of which regions corresponds to its own unique region identifier, and the plurality of regions corresponds to a first set of region identifiers. The one or more processors are also configured to obtain a first restriction status file containing restriction status information relating to each of which regions, the first restriction status file indicating the restriction status of one or more satellite-related services for the UE in the region represented by one or more geopolygons relating to each of which regions. One or more processors are further configured to receive from the server a second set of area identifiers and a second restriction status file containing corresponding restriction status information, determine the difference between the first set of area identifiers and the second set of area identifiers, and update the first area file, the first restriction status file, or both based on the difference.
[0177] Clause 29. One or more processors are further configured to send a request for a second limit status file to the server before receiving the second limit status file, the UE of Clause 28, the request indicating a version indicator of the first limit file.
[0178] Clause 30. One or more processors are further configured to send a version indicator of a first region file to a server, receive a second region file from the server in response to a determination, made based on the version indicator of the first region file, that the first region file is different from the second region file, and authenticate the second region file received from the server, as per any UE of Clause 28 or 29.
[0179] Clause 31. Any UE from Clauses 28-30, where each region identifier in the second set of region identifiers includes the region details of the corresponding one or more geopolygons and a hash of the version indicator of the second region file.
[0180] Clause 32. The region details of one or more corresponding geopolygons include the geometric arrangement and characteristics of the one or more corresponding geopolygons representing the region, as specified in any of Clauses 28-31.
[0181] Clause 33. Any UE from Clauses 28-32, where obtaining the first region file further includes receiving the first region file from a server or retrieving the first region file from local memory.
[0182] Clause 34. One or more processors are further configured to receive the first region file from a server or retrieve the first region file from local memory, in order to obtain the first region file, as specified in any of Clauses 28-33.
[0183] Clause 35. Any UE under Clauses 28-34 whose restriction status information includes information about different features, where the different features correspond to whether satellite-based communications are permitted or affected by the provider, whether satellite-based positioning is affected, or any combination thereof.
[0184] Clause 36. One or more processors are further configured to send capability reports to a server indicating the satellite-related services supported by the UE, and a second limit status file is determined based on the capability reports, for any UE under any of Clauses 28-35.
[0185] Clause 37. Any UE from Clauses 28 to 36 whose header of the first region file includes data indicating the version indicator of the first region file, the timestamp of the most recent update of the first region file, the file signature of the first region file, a summary of the content provided within the first region file, characteristics applicable to one or more geopolygons, or any combination thereof.
[0186] Clause 38. Any UE under Clauses 28-37 where the second area file is transmitted in an extensible binary format.
[0187] Clause 39. An exemplary server for geofencing relating to satellite communications comprises a transceiver, memory, and one or more processors communicatively coupled to the transceiver and memory. One or more processors are configured to obtain a first region file containing a plurality of regions, each of which is represented by one or more geopolygons, each of which corresponds to its own unique region identifier, and each of which corresponds to a first set of region identifiers. One or more processors are also configured to obtain a first restriction status file containing restriction status information relating to each of which regions, the first restriction status file indicating the restriction status of one or more satellite-related services for each of which regions, to a UE in a region represented by one or more geopolygons. One or more processors are further configured to receive a request for restriction status information relating to one or more of which regions from a target UE, and, in response to receiving the request, transmit the first restriction status file to the target UE.
[0188] Clause 40. A server of Clause 39, further configured to receive a version indicator of a second area file stored in the UE from the UE, and to transmit the first area file to the UE in response to a determination, made based on the version indicator of the second area file, that the first area file is different from the second area file.
[0189] Clause 41. Each region identifier in the first set of region identifiers includes the region details of the corresponding one or more geopolygons and a hash of the version indicator of the first region file, on either server of Clause 39 or 40.
[0190] Clause 42. The region details of one or more corresponding geopolygons include the geometric arrangement and characteristics of the one or more corresponding geopolygons representing the region, as defined in any of the servers under Clauses 39 to 41.
[0191] Clause 43. One or more geopolyons correspond to any of the servers specified in Clauses 39-42, with different resolutions.
[0192] Clause 44. Any server under Clauses 39-43 whose restriction status information includes information about different features, where the different features correspond to whether satellite-based communications are permitted or affected by the provider, whether satellite-based positioning is affected, or any combination thereof.
[0193] Clause 45. One or more processors are further configured to receive capability reports from the UE indicating satellite-related services supported by the UE, and a first limit status file is determined based on the capability reports, on any of the servers in Clauses 39-44.
[0194] Clause 46. Any server under Clauses 39-45 whose header of the first region file contains data indicating the version indicator of the first region file, the timestamp of the most recent update of the first region file, the file signature of the first region file, a summary of the content provided within the first region file, characteristics applicable to one or more geopolygons, or any combination thereof.
[0195] Clause 47. Any server specified in Clauses 39-46, where the first area file is transmitted in an extensible binary format.
[0196] Clause 48. An exemplary UE for geofencing relating to satellite communications comprises a transceiver, memory, and one or more processors communicatively coupled to the transceiver and memory. The one or more processors are configured to obtain a region file containing a plurality of regions, each of which is represented by one or more geopolygons, and each of which corresponds to a unique region identifier. The one or more processors are also configured to obtain a restriction status file containing restriction status information relating to each of which regions, the restriction status file indicating the restriction status of one or more satellite-related services for the UE in the region represented by one or more geopolygons with respect to each of which regions. The one or more processors are further configured to determine a location estimate of the UE and the uncertainty associated with the location estimate, determine the corresponding geopolygon among the one or more geopolygons in the region file corresponding to the location estimate based on the location estimate and the uncertainty associated with the location estimate, and obtain restriction status information for the corresponding geopolygon based on the restriction status file.
[0197] Clause 49. The UE of Clause 48 is further configured to determine the corresponding geopolygon by having one or more processors identify a subset of geopolygons that correspond to a location estimate based on applying a supervised learning algorithm to one or more geopolygons, and by checking the location within each geopolygon of the subset geopolygons.
[0198] Clause 50. An exemplary server for cloud-based geofencing relating to satellite communications comprises a transceiver, memory, and one or more processors communicatively coupled to the transceiver and memory. One or more processors are configured to obtain a region file containing a plurality of regions, each of which is represented by one or more geopolygons, and each of which corresponds to a unique region identifier. One or more processors are also configured to obtain a restriction status file containing restriction status information relating to each of which regions, the restriction status file indicating the restriction status of one or more satellite-related services for each of which regions, in the region represented by one or more geopolygons. One or more processors are further configured to obtain a location estimate of the target UE and a unique identifier of the target UE, determine the unique region identifier corresponding to the location estimate of the UE according to the region file, and determine the restriction status, including satellite-related service parameters applicable to the target UE, based on the unique region identifier and the unique identifier of the target UE, according to the restriction status file.
[0199] Clause 51. The server under Clause 50, whose satellite-related service parameters include a limited applicable time window, a unique identifier relating to the device to which the limit applies, applicable limits, or any combination thereof.
[0200] Clause 52. Any server under Clause 50 or 51, where applicable restrictions include whether satellite communications are permitted by the provider, transmit power level restrictions, whether satellite-based positioning is permitted or affected, the level of service permitted, or any combination thereof.
[0201] Clause 53. Any server under Clauses 50-52, in which one or more processors are further configured to apply applicable restriction statuses to the target UE.
[0202] Clause 54. Any of the servers under Clauses 50-53, in which one or more processors are further configured to notify the target UE of applicable restriction statuses.
Claims
1. A geofencing method relating to satellite communications, performed by user equipment (UE), Obtaining a first region file containing multiple regions, each of which is represented by one or more geopolyons, each of which corresponds to a unique region identifier, and each of which corresponds to a first set of region identifiers; Obtaining a first restriction status file, which includes restriction status information for each of the plurality of regions, wherein the first restriction status file indicates the restriction status of one or more satellite-related services for the UE in the region represented by one or more geopolygons, with respect to each of the plurality of regions; The server receives a second restriction status file containing a second set of area identifiers and corresponding restriction status information. To determine the difference between the first set of region identifiers and the second set of region identifiers, A method comprising updating the first area file, the first restriction status file, or both, based on the aforementioned difference.
2. The process further includes sending a request for the second restriction status file to the server before receiving the second restriction status file, wherein the request indicates a version indicator for the first area file. The method according to claim 1.
3. Sending the version indicator of the first area file to the server, In response to the determination, made based on the version indicator of the first area file, that the first area file is different from the second area file, the server receives the second area file. Authenticating the second area file received from the server, The method according to claim 1, further comprising:
4. The method according to claim 3, wherein each region identifier in the second set of region identifiers includes a region detail of one or more geopolygons and a hash of the version indicator of the second region file.
5. The method according to claim 4, wherein the region detail of the corresponding one or more geopolygons includes the geometric arrangement and characteristics of the corresponding one or more geopolygons representing the region.
6. Obtaining the aforementioned first area file is Receiving the first area file from the server, or The method according to claim 1, further comprising retrieving the first region file from local memory.
7. The method according to claim 1, wherein the one or more geopolyons correspond to different resolutions.
8. The aforementioned restriction status information includes information about different characteristics, and the aforementioned different characteristics are Whether satellite-based communications are permitted or affected by the provider, Satellite-based positioning is affected, or The method according to claim 1, corresponding to any combination thereof.
9. The process further includes transmitting a capability report to the server indicating the satellite-related services supported by the UE, wherein the second limitation status file is determined based on the capability report. The method according to claim 1.
10. The header of the first area file is, Version indicator of the first area file, The timestamp of the most recent update of the first area file, The file signature of the first area file, Summary of the content provided in the first domain file, Characteristics applicable to one or more of the aforementioned geopolyons, The method according to claim 1, comprising data showing any combination thereof.
11. The method according to claim 3, wherein the second area file is transmitted in an extensible binary format.
12. A geofencing method relating to satellite communications, which is performed by a server, Obtaining a first region file containing multiple regions, each of which is represented by one or more geopolyons, each of which corresponds to a unique region identifier, and each of which corresponds to a first set of region identifiers; Obtaining a first restriction status file, which includes restriction status information for each of the plurality of regions, wherein the first restriction status file indicates the restriction status of one or more satellite-related services for user equipment (UE) in the region represented by one or more geopolygons, with respect to each of the plurality of regions; Receiving a request for restriction status information regarding one or more of the aforementioned regions from the target UE, A method comprising sending the first restriction status file to the target UE in response to receiving the aforementioned request.
13. The UE receives a version indicator for a second area file stored within the UE, In response to the determination, made based on the version indicator of the second region file, that the first region file is different from the second region file, the UE is sent the first region file. The method according to claim 12, further comprising:
14. The method according to claim 12, wherein each region identifier in the first set of region identifiers includes a region detail of the corresponding one or more geopolygons and a hash of the version indicator of the first region file.
15. The method according to claim 14, wherein the region detail of the corresponding one or more geopolygons includes the geometric arrangement and characteristics of the corresponding one or more geopolygons representing the region.
16. The method according to claim 12, wherein the one or more geopolyons correspond to different resolutions.
17. The aforementioned restriction status information includes information about different characteristics, and the aforementioned different characteristics are Whether satellite-based communications are permitted or affected by the provider, Satellite-based positioning is affected, or The method according to claim 12, corresponding to any combination thereof.
18. The first limitation status file is determined based on the capability report, and the UE further includes receiving a capability report from the UE indicating the satellite-related services supported by the UE. The method according to claim 12.
19. The header of the first area file is, Version indicator of the first area file, The timestamp of the most recent update of the first area file, The file signature of the first area file, Summary of the content provided in the first domain file, Characteristics applicable to one or more of the aforementioned geopolyons, The method according to claim 12, comprising data showing any combination thereof.
20. The method according to claim 12, wherein the first area file is transmitted in an extensible binary format.
21. User equipment (UE) for geofencing related to satellite communications, Transceiver and, Memory and The transceiver and the memory are communicatively coupled to one or more processors, and the one or more processors Obtain a first region file containing multiple regions, each of which is represented by one or more geopolyons, each of which corresponds to its own unique region identifier, and each of which corresponds to a first set of region identifiers. A first restriction status file is obtained, which includes restriction status information for each of the plurality of regions, wherein the first restriction status file indicates the restriction status of one or more satellite-related services for the UE in the region represented by one or more geopolygons, with respect to each of the plurality of regions. The server receives a second restriction status file containing a second set of area identifiers and corresponding restriction status information. Determine the difference between the first set of region identifiers and the second set of region identifiers. A UE configured to update the first area file, the first restriction status file, or both, based on the aforementioned difference.
22. The aforementioned one or more processors The UE according to claim 21, further configured to send a request for the second restriction status file to the server before receiving the second restriction status file, wherein the request indicates a version indicator of the first area file.
23. The aforementioned one or more processors The version indicator of the first area file is sent to the server. Based on the version indicator of the first area file, in accordance with the determination that the first area file is different from the second area file, the server receives the second area file. The UE according to claim 21, further configured to authenticate the second area file received from the server.
24. The UE according to claim 23, wherein each region identifier in the second set of region identifiers includes a region detail of one or more geopolygons and a hash of the version indicator of the second region file.
25. The UE according to claim 24, wherein the region detail of the corresponding one or more geopolygons includes the geometric arrangement and characteristics of the corresponding one or more geopolygons representing the region.
26. In order to obtain the first region file, one or more processors, The server receives the first area file, or The UE according to claim 21, further configured to retrieve the first region file from local memory.
27. A server for geofencing related to satellite communications, Transceiver and, Memory and The transceiver and the memory are communicatively coupled to one or more processors, and the one or more processors Obtain a first region file containing multiple regions, each of which is represented by one or more geopolyons, each of which corresponds to its own unique region identifier, and each of which corresponds to a first set of region identifiers. A first restriction status file is obtained, which includes restriction status information for each of the plurality of regions, wherein the first restriction status file indicates the restriction status of one or more satellite-related services for user equipment (UE) in the region represented by one or more geopolygons, with respect to each of the plurality of regions. The target UE receives a request for restriction status information regarding one or more of the aforementioned regions. A server configured to send the first restriction status file to the target UE in response to receiving the aforementioned request.
28. The aforementioned one or more processors The UE receives a version indicator for a second area file stored within the UE. The server according to claim 27, further configured to transmit the first area file to the UE in response to a determination, made based on the version indicator of the second area file, that the first area file is different from the second area file.
29. The server according to claim 27, wherein each region identifier in the first set of region identifiers includes the region details of the corresponding one or more geopolygons and a hash of the version indicator of the first region file.
30. The server according to claim 29, wherein the region detail of the corresponding one or more geopolygons includes the geometric arrangement and characteristics of the corresponding one or more geopolygons representing the region.