Description:RESERVATION OF RIGHTS
[0001] A portion of the disclosure of this patent document contains material, which is subject to intellectual property rights such as but are not limited to, copyright, design, trademark, integrated circuit (IC) layout design, and/or trade dress protection, belonging to Jio Platforms Limited (JPL) or its affiliates (hereinafter referred as owner). The owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure, as it appears in the Patent and Trademark Office patent files or records, but otherwise reserves all rights whatsoever. All rights to such intellectual property are fully reserved by the owner.

FIELD OF INVENTION
[0002] The embodiments of the present disclosure generally relate to a field of communication systems, and specifically to a system and a method for sensing and tracking an Unmanned Aerial Vehicle (UAV) in a cellular network and beyond cellular networks.

BACKGROUND OF INVENTION
[0003] Currently available 3rd Generation Partnership Project (3GPP) Unmanned Aerial Vehicle (UAV) location monitoring mechanism assumes that a UAV is equipped with 4G Long Term Evolution (LTE) or 5G New Radio (NR) modems that allow them to function as LTE/5G devices (User Equipment (UE)/Handsets) to support 3GPP location estimation methods. Accordingly, the UAV (acting as the UE) may determine its location and transmit the location information to a UAV controller through an application. However, several issues arise with this approach. In some cases, the UAVs may reach altitudes where the LTE/5G coverage may not be available. Additionally, some of the UAVs may not be equipped with 3GPP UE capabilities, and in such cases, there are no established methods available for a terrestrial cellular network to assist in tracking a trajectory of the UAV.
[0004] In addition, prevalent Integrated Sensing and Communication (ISAC) services encompasses various use cases, which may be broadly classified into two categories: outdoor and indoor. The outdoor use cases pertain to smart transportation, while the indoor use cases relate to smart life. One example of an outdoor use case is perception of road dynamic information. Current methods for detecting traffic congestion suffer from various limitations. Consequently, a perception-assisted traffic condition detection mechanism that uses road dynamic information emerges as a crucial use case for an ISAC technology. FIG. 1 illustrates an exemplary 6G assisted automotive manoeuvring and navigation scheme 100 representing the ISAC technology. The solution provides an extensive deployment coverage without additional costs and has a potential to address most issues related to traffic congestion and traffic safety risk detection in real-time and with high accuracy. However, the state of art in the communication and sensing technology only covers location services and does not integrate sensed data (in all its variations) and location data into a cellular network protocol.
[0005] There is, therefore, a need in the art to provide an improved system and a method to sense and track the UAV by overcoming the deficiencies of the prior art(s).

OBJECTS OF THE INVENTION
[0006] It is an object of the present disclosure to provide a system and a method to sense and track an Unmanned Aerial Vehicle (UAV) in a cellular network and beyond cellular networks.
[0007] It is an object of the present disclosure to provide a system and a method that enables a close integration between a UAV controller or a UAV management entity and a 3GPP network to provide enhanced UAV tracking, collision avoidance, and handover of sensing data for accurate UAV tracking.
[0008] It is an object of the present disclosure to provide a system and a method that uses different architectural elements for integrated communication, sensing and tracking of the UAVs through the 3GPP network.
[0009] It is an object of the present disclosure to provide a system and a method that provides base station coverage adaptation for the UAV on a flight.
[0010] It is an object of the present disclosure to provide a system and a method that enables a proactive sensing handover of base stations for the coverage adaptation of the UAV.
[0011] Yet another object of the present disclosure is to provide a system and a method that enables tracing a flight trajectory of the UAV.

SUMMARY
[0012] In an aspect, the present disclosure relates to a system for sensing and tracking an Unmanned Aerial Vehicle (UAV) in a cellular network and beyond cellular networks. The system may include one or more processors associated with a sensing agent, and a memory operatively coupled to the one or more processors, wherein the memory includes processor-executable instructions, which on execution, cause the one or more processors to register a sensing client with the sensing agent. The sensing client may include a User Application Server (UAS) service Application Programming Interface (API) entity. The one or more processors establish communication between the registered sensing client and the sensing agent. The communication may be established upon the sensing agent registering with at least one of a UAS Service Provider (USP) entity and one or more UAS operator entities. Further, the one or more processors receive, via the sensing agent, a service request from the sensing client to initiate and execute the sensing and tracking of the UAV when trajectory of the UAV falls within a coverage area of the sensing agent.
[0013] In an embodiment, the one or more processors may be configured to initiate communication between the USP entity and the one or more UAS operator entities. The communication may be conducted according to pre-defined rules when the one or more UAS operator entities lie within a core network domain of a cellular operator.
[0014] In an embodiment, the one or more processors may be configured to sense and track the UAV by determining location information from any or a combination of at least one of the UAV, a group of UAVs, one or more stray UAVs that are in proximity to the group of UAVs, and one or more identified UAVs straying from a pre-defined route.
[0015] In an embodiment, to sense and trace a flight trajectory of the UAV, the one or more processors may be configured to receive a service request message to initiate a tracing function. The tracing function may be initiated by the USP entity and the tracing function may include an activated flight trajectory of the UAV on a flight route within a designated airspace. The one or more processors may identify one or more active sensing agents in the trajectory for sensing the UAV. The identified one or more sensing agents may be activated in an order defined by a sensing aggregation entity.
[0016] In an embodiment, to sense the UAV, the one or more processors may be configured to send, via a first sensing agent of the sensing aggregation entity, a reference symbol towards a designated second sensing agent of the sensing aggregation entity. The one or more processors may be configured to receive, via the second sensing agent, a modified reference symbol when the flight trajectory of the UAV lies between the first sensing agent and the second sensing agent. The modified reference symbol may be altered based on speed, size, and direction of the UAV. In addition, the one or more processors may be configured to transmit, via the second sensing agent, the modified reference symbol to at least one of the USP entity and the one or more of UAS operator entities.
[0017] In an embodiment, to enable a coverage adaptation of a base station, the one or more processors may be configured to determine if the UAV has moved from a coverage area of a first base station to a coverage area of a second base station, and activate a power-saving mode for the first base station in response to a positive determination.
[0018] In an embodiment, the first base station may be configured to continuously sense the UAV until the UAV completely moves out of the coverage area of the first base station to the coverage area of the second base station.
[0019] In an embodiment, to perform a proactive sensing handover, the one or more processors may be configured to determine whether a sensing coverage of a current base station monitoring the UAV is weak in comparison to another base station located near the UAV. In response to a positive determination, the proactive sensing handover for the UAV may be activated. The proactive sensing handover may lead to a seamless and a continuous sensing service for the UAV.
[0020] In an embodiment, a sensing aggregation entity may act as a sensing handover anchor between the current base station and the another base station.
[0021] In an embodiment, when the one or more UAS operator entities act as a sensing handover anchor between the current base station and the another base station, the sensing aggregation entity may provide an ordered list of one or more base stations present in the flight route to the one or more UAS operator entities.
[0022] In an aspect, the present disclosure relates to a method for determining a flight trajectory of a UAV in a cellular network and beyond cellular networks. The method may include receiving, by a UAV positioning platform, during an on-route detection of the UAV, one or more inputs from one or more UAV sensors associated with the UAV. The UAV positioning platform may receive sensing information from a base transceiver station (BTS). The method may include determining, by the UAV positioning platform, a position of the UAV in the flight trajectory based on the one or more inputs, and based on the sensing information when the UAV is off-route.
[0023] In an aspect, the present disclosure relates to a method for determining location information of the UAV. The method may include receiving, by a UAV positioning platform, a first set of positioning and sensing parameters from one or more UAV sensors associated with the UAV. The first set of positioning and sensing parameters may be received when a successful connection exists between the UAV positioning platform and the UA. The method may further include receiving, by a telecommunications platform, a second set of positioning and sensing parameters of the UAV. The second set of positioning and sensing parameters are received when the connection between the UAV positioning platform and the UAV is unsuccessful. The method may include receiving, by each of the UAV positioning platform and the telecommunications platform, each of the first set and the second set of the positioning and sensing parameters respectively to determine the location information of the UAV.
[0024] In an embodiment, the method may include maintaining, by a Gateway UAV Location Center (GULC) entity, an interface with a location structure via a Location Services (LCS) client to determine the location information of the UAV, where the LCS client is co-resident with the GULC entity.
[0025] In an embodiment, the method may include maintaining, by the GULC entity, a direct interface with at least one of a Gateway Mobile Location Center (GMLC) and a Location Retrieval Function (LRF) to determine the location information of the UAV.
[0026] In an embodiment, the method may include combining, by a sensing aggregation entity, the received first set and the second set of positioning and sensing parameters from each of the one or more UAV sensors associated with the UAV and the received set of positioning and sensing parameters of the UAV from the telecommunications platform respectively, to predict a UAV status.

BRIEF DESCRIPTION OF DRAWINGS
[0027] The accompanying drawings, which are incorporated herein, and constitute a part of this disclosure, illustrate exemplary embodiments of the disclosed methods and systems which like reference numerals refer to the same parts throughout the different drawings. Components in the drawings are not necessarily to scale, emphasis instead being placed upon clearly illustrating the principles of the present disclosure. Some drawings may indicate the components using block diagrams and may not represent the internal circuitry of each component. It will be appreciated by those skilled in the art that disclosure of such drawings includes the disclosure of electrical components, electronic components, or circuitry commonly used to implement such components.
[0028] FIG. 1 illustrates an exemplary 6th Generation (6G) assisted automotive manoeuvring and navigation representing an integrated communication and sensing technology for a UAV.
[0029] FIG. 2 illustrates an exemplary network architecture of a system for sensing and tracking an Unmanned Aerial Vehicle (UAV) in a cellular network and beyond cellular networks, in accordance with an embodiment of the present disclosure.
[0030] FIG. 3 illustrates an exemplary block diagram of the system, in accordance with an embodiment of the present disclosure.
[0031] FIG. 4 illustrates an exemplary representation of architectural elements of a UAV sensing architecture, in accordance with an embodiment of the present disclosure.
[0032] FIG. 5 illustrates an exemplary representation of UAS application enabler services for sensing and tracking the UAVs through a 3GPP system, in accordance with an embodiment of the present disclosure.
[0033] FIG. 6 illustrates an exemplary UTM architecture representing the 3GPP core comprising User Application Server (UAS) service Application Programming Interfaces (APIs) provided through an API gateway, in accordance with an embodiment of the present disclosure.
[0034] FIG. 7 illustrates the exemplary UTM architecture to facilitate a communication between the UTM and the 3GPP sensing entities, in accordance with an embodiment of the present disclosure.
[0035] FIG. 8 illustrates an exemplary representation of UAS operator entities within a cellular operator core network domain, in accordance with an embodiment of the present disclosure.
[0036] FIG. 9 illustrates an exemplary representation for tracing and sensing a UAV flight trajectory in a 5G assisted network, in accordance with an embodiment of the present disclosure.
[0037] FIG. 10 illustrates an exemplary representation of proactive sensing handover of the UAV between two base stations, in accordance with an embodiment of the present disclosure.
[0038] FIG. 11 illustrates an exemplary sequence flow for flight trajectory tracing of the UAV, in accordance with an embodiment of the present disclosure.
[0039] FIG. 12 illustrates an exemplary representation of a Gateway UAV Location Center (GULC) entity between an existing location architecture and a UAV location tracking center, in accordance with an embodiment of the present disclosure.
[0040] FIG. 13 illustrates an exemplary flow diagram for the UAV sensing, in accordance with an embodiment of the present disclosure.
[0041] FIG. 14 illustrates a sequence flow for determining a flight trajectory of the UAV in the cellular network and beyond the cellular networks, in accordance with an embodiment of the present disclosure.
[0042] FIG. 15 illustrates a sequence flow for collecting a set of positioning and sensing parameters of the UAV to determine a location information of the UAV, in accordance with an embodiment of the present disclosure.
[0043] FIG. 16 illustrates an exemplary computer system in which or with which embodiments of the present disclosure may be utilized in accordance with embodiments of the present disclosure.
[0044] The foregoing shall be more apparent from the following more detailed description of the disclosure.

DETAILED DESCRIPTION
[0045] In the following description, for the purposes of explanation, various specific details are set forth in order to provide a thorough understanding of embodiments of the present disclosure. It will be apparent, however, that embodiments of the present disclosure may be practiced without these specific details. Several features described hereafter can each be used independently of one another or with any combination of other features. An individual feature may not address all of the problems discussed above or might address only some of the problems discussed above. Some of the problems discussed above might not be fully addressed by any of the features described herein.
[0046] The ensuing description provides exemplary embodiments only and is not intended to limit the scope, applicability, or configuration of the disclosure. Rather, the ensuing description of the exemplary embodiments will provide those skilled in the art with an enabling description for implementing an exemplary embodiment. It should be understood that various changes may be made in the function and arrangement of elements without departing from the spirit and scope of the disclosure as set forth.
[0047] Specific details are given in the following description to provide a thorough understanding of the embodiments. However, it will be understood by one of ordinary skill in the art that the embodiments may be practiced without these specific details. For example, circuits, systems, networks, processes, and other components may be shown as components in block diagram form in order not to obscure the embodiments in unnecessary detail. In other instances, well-known circuits, processes, algorithms, structures, and techniques may be shown without unnecessary detail to avoid obscuring the embodiments.
[0048] Also, it is noted that individual embodiments may be described as a process that is depicted as a flowchart, a flow diagram, a data flow diagram, a structure diagram, or a block diagram. Although a flowchart may describe the operations as a sequential process, many of the operations can be performed in parallel or concurrently. In addition, the order of the operations may be re-arranged. A process is terminated when its operations are completed but could have additional steps not included in a figure. A process may correspond to a method, a function, a procedure, a subroutine, a subprogram, etc. When a process corresponds to a function, its termination can correspond to a return of the function to the calling function or the main function.
[0049] The word “exemplary” and/or “demonstrative” is used herein to mean serving as an example, instance, or illustration. For the avoidance of doubt, the subject matter disclosed herein is not limited by such examples. In addition, any aspect or design described herein as “exemplary” and/or “demonstrative” is not necessarily to be construed as preferred or advantageous over other aspects or designs, nor is it meant to preclude equivalent exemplary structures and techniques known to those of ordinary skill in the art. Furthermore, to the extent that the terms “includes,” “has,” “contains,” and other similar words are used in either the detailed description or the claims, such terms are intended to be inclusive in a manner similar to the term “comprising” as an open transition word without precluding any additional or other elements.
[0050] Reference throughout this specification to “one embodiment” or “an embodiment” or “an instance” or “one instance” means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the present disclosure. Thus, the appearances of the phrases “in one embodiment” or “in an embodiment” in various places throughout this specification are not necessarily all referring to the same embodiment. Furthermore, the particular features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.
[0051] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the disclosure. As used herein, the singular forms “a”, “an”, and “the” are intended to include the plural forms as well, unless the context indicates otherwise. It will be further understood that the terms “comprises” and/or “comprising,” when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof. As used herein, the term “and/or” includes any and all combinations of one or more of the associated listed items.
[0052] The advent of Unmanned Aerial Vehicles (UAVs) have led to a substantial progress across multiple industries. To facilitate smooth incorporation of the UAVs into a 3rd Generation Partnership Project (3GPP) system, advanced sophisticated tracking mechanisms have been devised. These mechanisms are designed to be independent of Network Remote ID availability, thereby guaranteeing consistent location and tracking services to UAV Service Suppliers (USS) through the 3GPP systems.
[0053] The implementation of these mechanisms is consistent with capabilities of existing mobile networks for other User Equipment (UE). Notably, UAV tracking is conducted with an explicit consent of the UAV, which provides specific information to the 3GPP system. This information enables the 3GPP system to communicate with the USS thus granting them access to precise location data of the UAV. In this context, the current 3GPP system provides a variety of services that are specifically designed for tracking of the UAV. The services include:
i. Immediate UAV location reporting: Upon receiving a request from the USS, the 3GPP system promptly delivers the UAV’s current location.
ii. Periodic UAV location reporting: In accordance with the USS’s request, the 3GPP system periodically shares the UAV’s location at an interval that is mutually agreed upon by the USS and the 3GPP system.
iii. Monitoring the UAV’s presence within designated areas: The 3GPP system tracks the UAV’s movements within designated areas and provides regular reports to the USS. To enable this, the USS subscribes to event monitoring for a particular UAV by defining an “Area of Interest.” This subscription allows the USS to receive real-time updates on the UAV’s presence within a monitored area. The “Area of Interest” may be mapped to 3GPP-specific regions, such as cells, or may be based on actual locations reported by the 3GPP Gateway Mobile Location Center (GMLC).
iv. UAV Discovery: In this scenario, the USS may request an “Area of interest” from the 3GPP system and, in return, receive a comprehensive list of the UAVs served by the 3GPP system and currently operating within the designated area.
[0054] Further, in some countries enforcement of a revised Aeronautical Law has lifted a ban on “Level 4” flight, which involves remotely piloting unmanned aircraft in inhabited areas without a visual line of sight. This change has led to environmental improvements related to drone use and has spurred an increased research and development in the field of use of drones. However, differing definitions and functional structures related to Unmanned Traffic Management in each country has hindered an establishment of a global common understanding. Consequently, Requirements for Communication Performance (RCP), Navigation Performance (RNP), and Surveillance Performance (RSP) have become more stringent. Also, it is anticipated that enforcement authorities shall mandate multiple tracking mechanisms, or “eyes,” when the UAVs operate in populated areas.
[0055] Typically, on-route flying is critically important for commercial UAVs and their flight paths are meticulously optimized and authorized by UAV service operators, UAV management departments or Uncrewed Aerial System Service Suppliers (USS)/Uncrewed Aerial System Traffic Management entities. The routes for the commercial UAVs are designed to minimize distance, avoid restricted airspace, and maintain a safe distance from obstacles such as buildings, trees, hills, and other commercial UAVs. Although the UAVs are equipped with sensors to stay on their designated flight paths, it is still essential to have an external UAV flight trajectory tracking function due to potential sensor limitations. For example, camera performance of the UAV may be affected by varying lighting conditions, and UAV-mounted radar may experience interference during rainfall or snowfall. In such cases, the UAV may not be able to accurately determine its position, altitude, or speed, and thus cannot reliably follow its intended flight path. While dedicated UAV surveillance equipment and radar systems do exist, their widespread deployment presents significant challenges. Limited availability of suitable locations and the high costs associated with installation and maintenance contribute to these challenges.
[0056] Thus, one of primary objectives for 6G networks is to support a combined communication and sensing radio network architecture. Massive Multiple Input, Multiple Output (MIMO) radios, may be utilized for radio imaging. When a cellular network has massive MIMO radios incorporated, it may be feasible to envision a system that integrates both sensing and communication with the UAVs. However, the current state of art does not provide a unified system that is capable of performing both functions within a single radio/core network architecture. It may be noted that the sensing is not limited to radio imaging but it can also include camera imaging and use of infrared sensors. A key use case of interest is the tracking of the UAVs and addressing of issues such as UAV collision detection and avoidance.
[0057] Current advancements in communications and sensing primarily address location services that do not integrate sensing (in all its variations) with location data within cellular network protocols.
[0058] The disclosed system and method specifically addresses use of various sensing mechanisms within a communication system to enhance a UAV support architecture. The disclosed system and method proposes a tight integration between the UAV controller or a UAV Management entity and the 3GPP network, specifically 3GPP core network entities and location entities. This integration aims to enhance the UAV tracking, enable collision avoidance for the UAV and handover of sensing data to assist in the UAV tracking.
[0059] Various embodiments of the present disclosure will be explained in detail with reference to FIGs. 2-5.
[0060] FIG. 2 illustrates an exemplary network architecture 200 of a system for sensing and tracking the UAV in the cellular network and beyond the cellular networks, in accordance with an embodiment of the present disclosure.
[0061] With respect to FIG. 2, a sensing agent 204 may act as the system 204. The sensing agent 204 may be communicatively connected to a sensing client 202 and a sensing aggregation entity 206. The sensing client 202 may be a UAV traffic management entity (UTM) or a UAV management entity that may connect to and request the 3GPP network for availing sensing services.
[0062] The sensing agent 204 may be interchangeably referred to as a Radio Access Network (RAN) entity 204. The sensing agent 204 may sense an availability of a UAV object. The RAN entity 204 may connect individual devices of a network to other parts of the network through a radio link. The RAN entity 204 may connect user equipment, such as a cell phone, computer or any remotely controlled machine, over a fiber or wireless backhaul connection. A person of ordinary skill in the art will appreciate that the RAN entity 204 may include, but is not limited to, a Global System for Mobile Communications (GSM) radio access network (RAN) (GRAN), a GSM EDGE RAN (GERAN), a Universal Mobile Telecommunications Service (UMTS) RAN (UTRAN), and an Evolved UTRAN (E-UTRAN).
[0063] In an embodiment, the sensing aggregation entity 206 may manage the sensing of multiple UAV objects across multiple RAN entities.
[0064] As may be appreciated, the UAV may be commonly known as a drone or a remotely piloted aircraft (RPA) that operates without any human pilot, crew, or passengers on board.
[0065] A person of ordinary skill in the art will appreciate that the sensing client 202, the sensing agent 204 and the sensing aggregation entity 206 may not be restricted to the mentioned devices and various other devices may be used.
[0066] In an embodiment, for the sensing and tracking of the UAV in the cellular network and beyond the cellular networks the sensing client 202 may be registered with the sensing agent 204. The sensing client 202 may include a User Application Server (UAS) service Application Programming Interface (API) entity. the sensing agent 204 may establish a communication between the registered sensing client 202 and the sensing agent 204. The communication may be established upon the sensing agent 204 registering with at least one of a UAS Service Provider (USP) entity and one or more UAS operator entities. Further, the sensing agent 204 may receive a service request from the sensing client 202 to initiate and execute the sensing and tracking of the UAV when a trajectory of the UAV falls within a coverage area of the sensing agent 204.
[0067] In an embodiment, the sensing agent 204 may initiate a communication between the USP entity and the one or more UAS operator entities. The communication may be conducted according to pre-defined rules when the one or more UAS operator entities lies within a core network domain of a cellular operator.
[0068] In an embodiment, the sensing agent 204 may sense and track the UAV by determining a location information from any or a combination of at least one of the UAV, a group of UAVs, one or more stray UAVs that are in proximity to the group of UAVs, and one or more identified UAVs straying from a pre-defined route.
[0069] In an embodiment, to sense and trace a flight trajectory of the UAV, the sensing agent may receive a service request message to initiate a tracing function. The tracing function may be initiated by the USP entity and the tracing function may include an activated flight trajectory of the UAV on a flight route within a designated airspace. further, the sensing agent 204 may identify one or more active sensing agents in the trajectory for sensing the UAV. The identified one or more sensing agents may be activated in an order defined by a sensing aggregation entity.
[0070] In an embodiment, to sense the UAV a first sensing agent of the sensing aggregation entity may send a reference symbol towards a designated second sensing agent of the sensing aggregation entity. The second sensing agent may receive a modified reference symbol when the flight trajectory of the UAV lies in between the first sensing agent and the second sensing agent. The modified reference symbol may be altered based on speed, size and direction of the UAV. Further, the second sensing agent may transmit the modified reference symbol to at least one of the USP entity and the one or more of UAS operator entities.
[0071] In an embodiment, to enable a coverage adaptation of a base station, the sensing agent 204 may determine if the UAV has moved from a coverage area of a first base station to a coverage area of a second base station. In response to receiving a positive determination, a power-saving mode for the first base station may be activated. The first base station may be configured to continuously sense the UAV until the UAV completely moves out of the coverage area of the first base station to the coverage area of the second base station.
[0072] In an embodiment, to perform a proactive sensing handover, the sensing agent 204 may determine whether a sensing coverage of a current base station monitoring the UAV is weak in comparison to another base station located near the UAV. In response to a positive determination, the proactive sensing handover for the UAV may be activated. The proactive sensing handover may lead to a seamless and a continuous sensing service for the UAV. In an embodiment, the sensing aggregation entity may act as a sensing handover anchor between the current base station and the another base station. In addition, when the one or more UAS operator entities act as a sensing handover anchor between the current base station and the another base station, the sensing aggregation entity may provide an ordered list of one or more base stations present in the flight route to the one or more UAS operator entities.
[0073] In an embodiment, a mechanism for determining a flight trajectory of the UAV in the cellular network and beyond the cellular networks is discussed. A UAV positioning platform may receive during an on-route detection of the UAV one or more inputs from one or more UAV sensors associated with the UAV. This may be done to calculate a position of the UAV in the flight trajectory. Further, the UAV positioning platform may receive sensing information from a base transceiver station (BTS) to calculate the position of the UAV in the flight trajectory when the UAV is off-route.
[0074] In an embodiment, a mechanism for collecting a set of positioning and sensing parameters of the UAV to determine the location information of the UAV is discussed. The method includes receiving by a UAV positioning platform a first set of positioning and sensing parameters from one or more UAV sensors associated with the UAV. The first set of positioning and sensing parameters may be received when a successful connection exists between the UAV positioning platform and the UAV. In addition, a second set of positioning and sensing parameters of the UAV may be received by a telecommunications platform. The second set of positioning and sensing parameters may be received when the connection between the UAV positioning platform and the UAV is unsuccessful. Further, both the UAV positioning platform and the telecommunications platform may receive each their first set and the second set of positioning and sensing parameters respectively, to determine the location information of the UAV.
[0075] In an embodiment, a Gateway UAV Location Center (GULC) entity may maintain an interface with a location structure via a Location Services (LCS) client to determine the location information of the UAV. The LCS client may be a co-resident with the GULC entity. In an embodiment, the GULC entity may maintain a direct interface with at least one of a Gateway Mobile Location Center (GMLC) and a Location Retrieval Function (LRF) to determine the location information of the UAV. Further, a sensing aggregation entity may combine the received first set and the second set of positioning and sensing parameters from each of the one or more UAV sensors associated with the UAV and the received set of positioning and sensing parameters of the UAV from the telecommunications platform respectively, to predict a UAV status.
[0076] Although FIG. 2 shows exemplary components of the network architecture, in other embodiments, the network architecture may include fewer components, different components, differently arranged components, or additional functional components than depicted in FIG. 1. Additionally, or alternatively, one or more components of the network architecture may perform functions described as being performed by one or more other components of the network architecture.
[0077] FIG. 3 illustrates an exemplary block diagram 300 of the system 204, in accordance with an embodiment of the present disclosure. The system 204 may include one or more processors 302. The one or more processors 302 may be implemented as one or more microprocessors, microcomputers, microcontrollers, digital signal processors, central processing units, logic circuitries, and/or any devices that manipulate data based on operational instructions. Among other capabilities, the one or more processors 302 may be configured to fetch and execute computer-readable instructions stored in a memory 304 of the system 204. The memory 304 may store one or more computer-readable instructions or routines, which may be fetched and executed to create or share the data units over a network service. The memory 304 may include any non-transitory storage device including, for example, volatile memory such as Random-Access Memory (RAM), or non-volatile memory such as an Erasable Programmable Read-Only Memory (EPROM), a flash memory, and the like.
[0078] In an embodiment, the system 204 may also include an interface(s) 306. The interface(s) 306 may include a variety of interfaces, for example, a variety of interfaces, for example, interfaces for data input and output devices, referred to as I/O devices, storage devices, and the like. The interface(s) 306 may facilitate communication of the system 204 with various devices coupled to it. The interface(s) 306 may also provide a communication pathway for one or more components of the system 204. Examples of such components include, but are not limited to, processing engine(s) 308 and a database 310.
[0079] In an embodiment, the processing engine(s) 308 may be implemented as a combination of hardware and programming (for example, programmable instructions) to implement one or more functionalities of the processing engine(s) 308. In examples, described herein, such combinations of hardware and programming may be implemented in several different ways. For example, the programming for the processing engine(s) 308 may be processor-executable instructions stored on a non-transitory machine-readable storage medium and the hardware for the one or more processors 302 may include a processing resource, to execute such instructions. In the present examples, the machine-readable storage medium may store instructions that, when executed by the processing resource, implement the processing engine(s) 308. In such examples, the system 204 may comprise the machine-readable storage medium storing the instructions and the processing resource to execute the instructions, or the machine-readable storage medium may be separate but accessible to the system 204 and the processing resource. In other examples, the processing engine(s) 308 may be implemented by an electronic circuitry.
[0080] In an embodiment, the database 310 may comprise data that may be either stored or generated as a result of functionalities implemented by any of the components of the processors 302 or the processing engine(s) 308 or the system 204.
[0081] In an exemplary embodiment, the processing engine(s) 308 may include one or more engines selected from any of a registering engine 312, a communication engine 314, an initiation and execution engine 316, a tracing engine 318, a sensing engine 320 and other units/engines 322. The other units/engines 322 may include, but are not limited to, a monitoring engine, a determination engine, and the like.
[0082] In an embodiment, the one or more processors 302 may, via the registering engine 312 register the sensing client with the sensing agent. The sensing client may include a User Application Server (UAS) service Application Programming Interface (API) entity. The communication engine 314 may establish a communication between the sensing agent and the registered sensing client. The communication may be established when the sensing agent registers with at least one of the UAS Service Provider (USP) entity and the one or more UAS operator entities. Further, the initiation and execution engine 316 may instruct the sensing agent to receive a service request from the sensing client to initiate and execute the sensing and tracking of the UAV when a trajectory of the UAV falls within a coverage area of the sensing agent.
[0083] In an embodiment, the tracing engine 318 may instruct the sensing agent to receive a service request message to initiate the tracing function. The tracing function may be initiated by the USP entity and may include an activated flight trajectory of the UAV on the flight route within the designated airspace. further, the sensing engine 320 may identify one or more active sensing agents in the trajectory for sensing the UAV. The identified one or more sensing agents may be activated in an order defined by the sensing aggregation entity.
[0084] In an embodiment, a first sensing agent of the sensing aggregation entity may send a reference symbol towards a designated second sensing agent of the sensing aggregation entity. Further, the second sensing agent may receive a modified reference symbol when the flight trajectory of the UAV lies in between the first sensing agent and the second sensing agent. The modified reference symbol may be altered based on speed, size and direction of the UAV. The second sensing agent may transmit the modified reference symbol to at least one of the USP entity and the one or more of UAS operator entities.
[0085] In an embodiment, to enable a coverage adaptation of the base station, the sensing agent may determine if the UAV has moved from a coverage area of a first base station to a coverage area of a second base station. Based on a positive determination a power-saving mode for the first base station may be activated.
[0086] In an embodiment, the first base station may be configured to continuously sense the UAV until the UAV completely moves out of the coverage area of the first base station to the coverage area of the second base station. In addition, to perform a proactive sensing handover, the sensing agent may determine whether a sensing coverage of a current base station monitoring the UAV is weak in comparison to another base station located near the UAV. Upon receiving the positive determination, the proactive sensing handover for the UAV may be activated thus providing a seamless and a continuous sensing service for the UAV.
[0087] Although FIG. 3 shows exemplary components of the system 204, in other embodiments, the system 204 may include fewer components, different components, differently arranged components, or additional functional components than depicted in FIG. 3. Additionally, or alternatively, one or more components of the system 204 may perform functions described as being performed by one or more other components of the system 204.
[0088] FIG. 4 illustrates an exemplary representation 400 of elements of a UAV sensing architecture, in accordance with an embodiment of the present disclosure. To develop the UAV sensing architecture, various architectural elements are utilized for integrated communication and sensing of the UAV. The elements may include the sensing client 402, the sensing agent 404, and the sensing aggregation entity 406, that may assist in the tracking of the UAV. The sensing client 402 may request or utilize sensing data of the UAV. The sensing agent 404 may be responsible for detecting the UAV. Further, the sensing aggregation entity 406 may collect and process data from the multiple sensing agents. The sensing client 402, the sensing agent 404, and the sensing aggregation entity 406 may form a foundation for enhancing the UAV sensing architecture thus enabling more effective tracking of an individual UAV or a group of UAVs.
[0089] In an embodiment, a mechanism is disclosed for providing a tight coupled architecture between the UAV controller and 3GPP network entities for specifically addressing an issue of sensing and tracking of the UAVs through the 3GPP system. FIG. 5 illustrates an exemplary representation 500 of UAS application enabler services for sensing and tracking the UAVs through the 3GPP system, in accordance with an embodiment of the present disclosure. In order to track the UAV or the group of UAVs, the UAS application enabler services are described, where a UTM (UAV traffic management entity) or a UAV management entity may request the 3GPP system for the sensing service. The service request may be directed by the UTM to the sensing agent (interchangeably referred to herein as a radio access network (RAN) entity) or to the sensing aggregation entity. Thereafter, the sensing agent or the sensing aggregation entity may manage the sensing across the multiple sensing agents associated with the group of UAVs.
[0090] In an embodiment the UTM may request the service aggregation entity which may reside in any of the 3GPP core network entities to track a specific UAV or a specific group of UAVs. On receiving the request, the sensing aggregation entity may involve the multiple sensing agents (the RAN entities) to execute the tracking function. It is to be noted that the sensing aggregation entity and/or the sensing agents are anchor points for sensing the service request for an entity, for example, the UTM.
[0091] FIG. 6 illustrates an exemplary UTM architecture 600 representing the 3GPP core comprising User Application Server (UAS) service Application Programming Interfaces (APIs) provided through an API gateway, in accordance with an embodiment of the present disclosure. With respect to FIG. 6, the 3GPP core may have the UAS service APIs that are provided through an API gateway. The API gateway and/or an API server may register with a UAS Service Provider (USP) and/or with a UAS operator entity.
[0092] FIG. 7 illustrates an exemplary UTM architecture 700 to facilitate communication between the UTM and the 3GPP sensing entities, in accordance with an embodiment of the present disclosure. With respect to FIG. 7, in order to facilitate communication between the UTM and the 3GPP sensing entities, the 3GPP sensing entities such as the sensing agent and/or the sensing aggregation entity may have to register with the USP and/or one or more UAS operator entities.
[0093] In an embodiment, the UTM may request a RAN entity to track a specific UAV when the UTM is aware that the UAV may be present in a trajectory that falls within a RAN coverage area of the RAN entity. In this case, each RAN entity may act as the sensing agent and the UTM may act as the sensing client.
[0094] FIG. 8 illustrates an exemplary representation 800 of the UAS operator entities within a cellular operator core network domain, in accordance with an embodiment of the present disclosure. With respect to FIG. 8, when the UAS operator entities are present within the cellular operator core network domain, a communication flow between the UAS service provider and the UAS operator entity may be dictated by regulatory bodies. By way of an example, in this case, User Equipment (UE) Mobile Station International Subscriber Directory Numbers (MSISDNs) of a device may be exchanged between an equipment identity register and the one or more UAS operator entities.
[0095] In an embodiment, overall communication flows between the UAS service provider and the UAS operator entity may involve exchanging a possible trajectory or route of the UAV to the sensing agent and/or to the sensing aggregation entity. Once the sensing agent and/or the sensing aggregation entity obtains a service request message along with route information of the UAV or the group of UAVs, the sensing agent and/or the sensing aggregation entity may initiate a tracking process for the UAV.
[0096] It may be appreciated that a sensing/tracking service request message may be aimed at identification of any or a combination of an individual UAV, a group of UAVs, identification of stray UAVs that are not part of the group of UAVs but comes in proximity to the group of UAVs, and identification of one or more UAVs that are straying from a predefined route.
[0097] In an embodiment, a mechanism for exchanging location/latitude/longitude/altitude information from the sensing agent to the sensing aggregation entity and/or the UTM is provided. Further, the UTM may look for continuous or non-continuous sensing information. In addition, the sensing aggregation entity may aggregate data from other sensing agents/RAN entities including satellite data.
[0098] In another embodiment, a mechanism for 5G network-assisted UAV flight trajectory tracing and sensing is disclosed. Following steps outline a series of signaling steps involved in the tracing of the UAV flight trajectory and the sensing of the UAVs with the assistance of 5G/6G networks.
1. The sensing aggregation entity, the UAV API entity, and/or the sensing agents in the 3GPP network architecture may register themselves with the UAS service provider and/or the UAV operator entity.
2. The USP may initiate the tracing function by sending a service request message to one or more of cellular network sensing entities. Sending the service request message may involve activating the UAV flight trajectory tracing function within a designated airspace at a specified time to the 5G/6G network. The tracing function may remain active for a specified time period.
3. Once the sensing aggregation entity receives the service request message with the UAV flight trajectory or a flight route of the UAV, the sensing aggregation entity may identify the sensing agents (i.e. the 5G/6G base stations) in the trajectory. In addition, the sensing agents may be activated for sensing the group of UAVs. It may be noted that the sensing aggregation entity may also identify an order of activation of appropriate sensing agents.
4. Execution of a sensing step may involve two or more sensing agents (e.g., base stations). One or more of a first sensing agent may act as an illuminator by sending a special signal, for example, a reference symbol towards another designated second sensing agent(s) (base station(s)). When the UAV comes between the first sensing agent that is acting as the illuminator and the second sensing agent(s), a signal as received by the sensing agent may get modified based on speed, size, and direction of the UAV. Further, a base station sensed position and motion-related metrics, for example, distance, angle of the UAV, and the like, may be identified within a coverage area of the UAV. The resulting sensed data may be transmitted from the 5G/6G base station (sensing agents) to the USP/UAS operator entity. FIG. 9 illustrates an exemplary representation 900 for tracing and sensing the UAV flight trajectory in a 5G assisted network, in accordance with an embodiment of the present disclosure.
[0099] In an embodiment, a base station coverage adaptation mechanism is discussed. Based on the received sensing and location information of the UAV, it may be determined if the UAV has moved from a coverage area of a first base station to a coverage area of a second base station. If such a transition is observed, the first base station may enter into a power-saving mode. In addition, the second base station may continue to sense the UAV until the UAV moves out of the coverage area of the second base station. It may be appreciated that the 5G sensing processing entity may facilitate determination of entry or exit of the UAV from the coverage area of the base station, thereby enabling the network to accordingly activate or deactivate the sensing in specific base stations.
[00100] In an embodiment a proactive sensing handover mechanism is provided. During the flight of the UAV, the network may trigger a proactive sensing handover when the sensing coverage of the current base station monitoring the UAV weakens or when another base station offers an improved sensing coverage. This ensures seamless and continuous sensing service for the UAV.
[00101] In an embodiment, the sensing aggregation entity may act as a sensing handover anchor between different sensing agents (for example, base stations/sectors of a base station). In yet another embodiment, the UAS operator entity may act as a sensing handover anchor. In a scenario where the UAS operator entity acts as a sensing handover anchor, the sensing aggregation entity may indicate an ordered list of the sensing agents for a given flight path of the UAV to the UAS operator entity. FIG. 10 illustrates an exemplary representation 1000 of the proactive sensing handover of the UAV between the two base stations, in accordance with an embodiment of the present disclosure.
[00102] In an embodiment, a mechanism for tracing the flight trajectory of the UAV is disclosed. The mechanism enables the UAV operator and/or UTM system to trace the flight trajectory of the UAV. In the event of an off-route detection, appropriate actions may be taken by the UAV operator and/or the UTM to steer the UAV back on course. FIG. 11 illustrates an exemplary sequence flow 1100 for the flight trajectory tracing of the UAV, in accordance with an embodiment of the present disclosure. As illustrated, in a sensing and augmentation message flow diagram, a platform may represent a sensing aggregation entity and/or the UAS operator entity. The application may represent the USP. In addition, the platform may also be referred to as the UAV positioning platform and may be used to collect a set of positioning parameters/sensing parameters.
[00103] With respect to FIG. 11, during normal functioning i.e., when a link between the platform and the UAV is undisturbed, the platform may receive inputs from the UAV sensors. Further, based on the received inputs, position of the UAV may be calculated. However, in circumstances when the link between the platform and the UAV is disrupted, the 3GPP platform may be used to determine the UAV tracing by providing relevant sensing information to the platform.
[00104] In an embodiment, received inputs from both the sensor data of the UAV and the 3GPP platform may be combined to provide more accurate information with respect to the location of the UAV.
[00105] FIG. 12 illustrates an exemplary representation 1200 of a Gateway UAV Location Center (GULC) entity between an existing location architecture and a UAV location tracking center, in accordance with an embodiment of the present disclosure. It is known that a sensing operation as against a positioning operation does not facilitate receiving feedback from the UAV. Therefore, functioning of the sensing operation and the positioning operation cannot be combined. To overcome this, the GULC entity is disclosed in FIG. 12. The GULC entity may be implemented between the existing location architecture and the UAV location tracking center and may facilitate UAV sensing. In an embodiment, the GULC entity may interface with an existing location infrastructure via a Location Services (LCS) client. The client may be a co-resident with the GULC entity. Further, the GULC entity may directly interact with a Gateway Mobile Location Center (GMLC)/Location Retrieval Function (LRF).
[00106] FIG. 13 illustrates an exemplary flow diagram 1300 for enabling the UAV sensing, in accordance with an embodiment of the present disclosure. With respect to FIG. 13, to facilitate the UAV sensing of the UAV, the sensing aggregation entity may combine inputs received from multiple UAV sensors associated with a cellular network reported sensing to arrive at a UAV status prediction. Further, data received from the sensors mounted on the UAV, for example, Global Positioning System (GPS), Inertial motion Unit (IMU), gyroscope, camera, and the like may be combined with sensing agent data before sharing with the USP.
[00107] FIG. 14 illustrates a sequence flow 1400 for determining the flight trajectory of the UAV in the cellular network and beyond the cellular networks, in accordance with an embodiment of the present disclosure. With reference to FIG. 14, the method 1400 may include the following steps. At 1402, the UAV positioning platform may receive one or more inputs from the one or more UAV sensors associated with the UAV to calculate the position of the UAV in the flight trajectory. The one or more inputs may be received during an on-route detection of the UAV. When the UAV is off-route, the UAV positioning platform may receive, at 1404, sensing information from the base transceiver station (BTS) to calculate the position of the UAV in the flight trajectory.
[00108] FIG. 15 illustrates a sequence flow 1500 for collecting the set of positioning and sensing parameters of the UAV to determine the location information of the UAV, in accordance with an embodiment of the present disclosure. With reference to FIG. 15, the method 1500 may include the following steps. At 1502, the UAV positioning platform may receive the first set of positioning and sensing parameters from the one or more UAV sensors associated with the UAV. The first set of positioning and sensing parameters may be received when the successful connection exists between the UAV positioning platform and the UAV.
[00109] At 1504, the telecommunications platform may receive the second set of positioning and sensing parameters of the UAV. The second set of positioning and sensing parameters may be received when the connection between the UAV positioning platform and the UAV is unsuccessful. Further, at 1506, each of the UAV positioning platform and the telecommunications platform may receive each of the first set and the second set of the positioning and sensing parameters respectively to determine the location information of the UAV.
[00110] FIG. 16 illustrates an exemplary computer system 1600 in which or with which embodiments of the present disclosure may be utilized in accordance with embodiments of the present disclosure.
[00111] As shown in FIG. 16, the computer system 1600 may include an external storage device 1610, a bus 1620, a main memory 1630, a read-only memory 1640, a mass storage device 1650, a communication port(s) 1660, and a processor 1670. A person skilled in the art will appreciate that the computer system 1600 may include more than one processor 1670 and communication ports 1660. The processor 1670 may include various modules associated with embodiments of the present disclosure. The communication port(s) 1660 may be any of an RS-232 port for use with a modem-based dialup connection, a 10/100 Ethernet port, a Gigabit or 10 Gigabit port using copper or fiber, a serial port, a parallel port, or other existing or future ports. The communication ports(s) 1660 may be chosen depending on a network, such as a Local Area Network (LAN), Wide Area Network (WAN), or any network to which the computer system 1600 connects.
[00112] In an embodiment, the main memory 1630 may be a Random-Access Memory (RAM), or any other dynamic storage device commonly known in the art. The read-only memory 1640 may be any static storage device(s) e.g., but not limited to, a Programmable Read Only Memory (PROM) chip for storing static information e.g., start-up or basic input/output system (BIOS) instructions for the processor 1670. The mass storage device 1650 may be any current or future mass storage solution, which can be used to store information and/or instructions. Exemplary mass storage solutions include, but are not limited to, Parallel Advanced Technology Attachment (PATA) or Serial Advanced Technology Attachment (SATA) hard disk drives or solid-state drives (internal or external, e.g., having Universal Serial Bus (USB) and/or Firewire interfaces).
[00113] In an embodiment, the bus 1620 may communicatively couple the processor(s) 1670 with the other memory, storage, and communication blocks. The bus 1620 may be, e.g., a Peripheral Component Interconnect (PCI)/PCI Extended (PCI-X) bus, Small Computer System Interface (SCSI), USB, or the like, for connecting expansion cards, drives, and other subsystems as well as other buses, such a front side bus (FSB), which connects the processor 1670 to the computer system 1600.
[00114] In another embodiment, operator and administrative interfaces, e.g., a display, keyboard, and cursor control device may also be coupled to the bus 1620 to support direct operator interaction with the computer system 1600. Other operator and administrative interfaces can be provided through network connections connected through the communication port(s) 1660. Components described above are meant only to exemplify various possibilities. In no way should the aforementioned exemplary computer system 1600 limit the scope of the present disclosure.
[00115] While considerable emphasis has been placed herein on the preferred embodiments, it will be appreciated that many embodiments can be made and that many changes can be made in the preferred embodiments without departing from the principles of the disclosure. These and other changes in the preferred embodiments of the disclosure will be apparent to those skilled in the art from the disclosure herein, whereby it is to be distinctly understood that the foregoing descriptive matter is to be implemented merely as illustrative of the disclosure and not as a limitation.

ADVANTAGES OF THE INVENTION
[00116] The present disclosure enables to sense and track an Unmanned Aerial Vehicle (UAV) in a cellular network and beyond cellular networks.
[00117] The present disclosure enables a close integration between a UAV controller or a UAV management entity and a 3GPP network to provide enhanced UAV tracking, collision avoidance, and handover of sensing data for accurate UAV tracking.
[00118] The present disclosure uses different architectural elements for integrated communication, sensing, and tracking of the UAVs through the 3GPP network.
[00119] The present disclosure provides a base station coverage adaptation for the UAV on a flight.
[00120] The present disclosure enables a proactive sensing handover of base stations for the coverage adaptation of the UAV.
[00121] The present disclosure enables tracing the flight trajectory of the UAV.
, Claims:1. A system (204) for sensing and tracking an Unmanned Aerial Vehicle (UAV), the system (204) comprising:
one or more processors (302) associated with a sensing agent (404); and
a memory (304) operatively coupled to the one or more processors (302), wherein the memory (304) comprises processor-executable instructions, which on execution, cause the one or more processors (302) to:
register a sensing client (202) with the sensing agent (404), wherein the sensing client (202) comprises a User Application Server (UAS) service Application Programming Interface (API) entity;
establish communication between the registered sensing client (202) and the sensing agent (404), wherein the communication is established upon the sensing agent (404) registering with at least one of a UAS Service Provider (USP) entity and one or more UAS operator entities; and
receive, via the sensing agent (404), a service request from the sensing client (202) to initiate and execute the sensing and tracking of the UAV when trajectory of the UAV falls within a coverage area of the sensing agent (404).
2. The system (204) as claimed in claim 1, wherein the one or more processors (302) are configured to:
initiate communication between the USP entity and the one or more UAS operator entities, wherein the communication is conducted according to pre-defined rules when the one or more UAS operator entities lie within a core network domain of a cellular operator.
3. The system (204) as claimed in claim 1, wherein the one or more processors (302) are configured to:
sense and track the UAV by determining location information from any or a combination of at least one of: the UAV, a group of UAVs, one or more stray UAVs that are in proximity to the group of UAVs, and one or more identified UAVs straying from a pre-defined route.
4. The system (204) as claimed in claim 1, wherein to sense and track a flight trajectory of the UAV, the one or more processors (302) are configured to:
receive a service request message to initiate a tracing function, wherein the tracing function is initiated by the USP entity, and the tracing function includes an activated flight trajectory of the UAV on a flight route within a designated space; and
identify one or more active sensing agents in the trajectory for sensing the UAV, wherein the identified one or more sensing agents are activated in an order defined by a sensing aggregation entity.
5. The system (204) as claimed in claim 4, wherein to sense the UAV, the one or more processors (302) are configured to:
send, via a first sensing agent of the sensing aggregation entity, a reference symbol towards a designated second sensing agent of the sensing aggregation entity;
receive, via the second sensing agent, a modified reference symbol when the flight trajectory of the UAV lies between the first sensing agent and the second sensing agent, wherein the modified reference symbol is altered based on speed, size, and direction of the UAV; and
transmit, via the second sensing agent, the modified reference symbol to at least one of the USP entity and the one or more of UAS operator entities.
6. The system (204) as claimed in claim 4, wherein to enable a coverage adaptation of a base station, the one or more processors (302) are configured to:
determine if the UAV has moved from a coverage area of a first base station to a coverage area of a second base station; and
activate a power-saving mode for the first base station in response to a positive determination,
wherein the first base station is configured to continuously sense the UAV until the UAV completely moves out of the coverage area of the first base station to the coverage area of the second base station.
7. The system (204) as claimed in claim 4, wherein to perform a proactive sensing handover, the one or more processors (302) are configured to:
determine whether a sensing coverage of a current base station monitoring the UAV is weak in comparison to another base station located near the UAV; and
in response to a positive determination, activate the proactive sensing handover for the UAV.
8. The system (204) as claimed in claim 7, wherein a sensing aggregation entity acts as a sensing handover anchor between the current base station and the another base station.
9. The system (204) as claimed in claim 7, wherein when the one or more UAS operator entities act as a sensing handover anchor between the current base station and the another base station, the sensing aggregation entity provides an ordered list of one or more base stations present in the flight route to the one or more UAS operator entities.
10. A method (1400) for determining a flight trajectory of an Unmanned Aerial Vehicle (UAV), the method (1400) comprising:
receiving, by a UAV positioning platform, during an on-route detection of the UAV, one or more inputs from one or more UAV sensors associated with the UAV to determine a position of the UAV in the flight trajectory; and
receiving, by the UAV positioning platform, sensing information from a base transceiver station (BTS); and
determining, by the UAV positioning platform, a position of the UAV in the flight trajectory based on the one or more inputs, and based on the sensing information when the UAV is off-route.
11. A method (1500) for determining location information of an Unmanned Aerial Vehicle (UAV), the method (1500) comprising:
receiving, by a UAV positioning platform, a first set of positioning and sensing parameters from one or more UAV sensors associated with the UAV, wherein the first set of positioning and sensing parameters are received when a successful connection exists between the UAV positioning platform and the UAV;
receiving, by a telecommunications platform, a second set of positioning and sensing parameters of the UAV, wherein the second set of positioning and sensing parameters are received when the connection between the UAV positioning platform and the UAV is unsuccessful; and
receiving, by each of the UAV positioning platform and the telecommunications platform, each of the first set and the second set of the positioning and sensing parameters, respectively, to determine the location information of the UAV.
12. The method (1500) as claimed in claim 11, wherein the method (1500) comprises:
maintaining, by a Gateway UAV Location Center (GULC) entity, an interface with a location structure via a Location Services (LCS) client to determine the location information of the UAV, wherein the LCS client is co-resident with the GULC entity.
13. The method (1500) as claimed in claim 12, wherein the method (1500) comprises:
maintaining, by the GULC entity, a direct interface with at least one of a Gateway Mobile Location Center (GMLC) and a Location Retrieval Function (LRF) to determine the location information of the UAV.
14. The method (1500) as claimed in claim 11, wherein the method (1500) comprises:
combining, by a sensing aggregation entity, the received first set and the second set of positioning and sensing parameters from each of the one or more UAV sensors associated with the UAV, and the received set of positioning and sensing parameters of the UAV from the telecommunications platform, respectively, to predict a UAV status.