Method and apparatus for real-time network monitoring and location updating of user equipment

Abstract

In a method for real-time network monitoring and location updating, a Unmanned Aerial System Application Enabler (UAE) server receives a location report from a Location Management (LM) server. The location report indicates location information of a User Equipment (UE). The UAE server receives a first network event notification associated with the UE from a Network Resource Management (NRM) server. The first network event notification indicates the connection status of the UE to the network. In response to detecting a reconnection status of the UE, the UAE server receives a second network event notification from the NRM server. The second network event notification indicates that the UE has reconnected to the network. Additionally, the UAE server records (i) the second network event notification, (ii) the identity of the UAE server, and (iii) the most recently updated location information of the UE from the LM server.

Description

[0001] Cross - Reference to Related Applications

[0002] This application claims the priority benefit of U.S. Patent Application No. 17 / 746,777, filed on May 17, 2022, entitled "METHOD AND APPARATUS FOR REAL TIME UAV CONNECTION MONITORING AND LOCATION REPORTING", which claims the priority benefit of U.S. Provisional Application No. 63 / 190,676, filed on May 19, 2021, entitled "Method and Apparatus for Real Time UAV Connection Monitoring and Location Reporting". The entire disclosure of the prior applications is incorporated herein by reference. Technical Field

[0003] The present disclosure relates to communication of unmanned aerial vehicles (UAVs). Background Art

[0004] The background art description provided herein is for the purpose of generally presenting the context of the present disclosure. To the extent of the work described in this background art section, the work of the presently named inventors and aspects that may not otherwise be defined as prior art at the time of filing are neither expressly nor implicitly admitted as prior art against the present disclosure.

[0005] An unmanned aerial vehicle (UAV) or unmanned aircraft may include an aircraft with no human pilot, crew, or passengers on board. A UAV is a component of an unmanned aircraft system (UAS). The UAS may also include a ground controller and a system for communicating with the UAV. Communication systems are being developed to support the connectivity requirements of unmanned aircraft systems. Summary of the Invention

[0006] Aspects of the present disclosure provide methods and apparatuses for real - time network connection status monitoring and location reporting for an unmanned aircraft system (UAS), for example, under a 3rd Generation Partnership Project (3GPP) network. In some examples, an apparatus for real - time network connection status monitoring and location reporting includes a receiving circuit system and a processing circuit system.

[0007] According to one aspect of the present disclosure, a method for real-time network monitoring and location updating for a user equipment (UE) in a Service Enablement Architecture Layer (SEAL) architecture is provided. In this method, a Unmanned Aerial System Application Enabler (UAE) server may receive a location report from a Location Management (LM) server in the SEAL architecture. The location report may indicate the location information of the UE. The UAE server may receive a first network event notification associated with the UE from a Network Resource Management (NRM) server in the SEAL architecture. The first network event notification may indicate the connection status of the UE with the network. In response to detecting the reconnection status of the UE, the UAE server may receive a second network event notification from the NRM server, wherein the second network event notification may indicate that the UE has reconnected to the network. The UAE server may record (i) the second network event notification, (ii) the identity of the UAE server, and (iii) the most recently updated location information of the UE from the LM server.

[0008] According to another aspect of the present disclosure, a device is provided. The device includes processing circuitry. The processing circuitry may be configured to perform any of the methods mentioned above.

[0009] Aspects of the present disclosure also provide a non-transitory computer-readable medium storing instructions that, when executed by a computer, cause the computer to perform any of the methods mentioned above.

[0010] A method and apparatus for real-time network monitoring and location updating for a user equipment (UE) in a Service Enablement Architecture Layer (SEAL) architecture according to an embodiment of the present application, wherein a Unmanned Aerial System Application Enabler (UAE) server receives a location report from a Location Management (LM) server in the SEAL architecture, the location report indicating the location information of the UE; the UAE server receives a first network event notification associated with the UE from a Network Resource Management (NRM) server in the SEAL architecture, the first network event notification indicating the connection status of the UE with the network; in response to detecting the reconnection status of the UE, the UAE server receives a second network event notification from the NRM server, the second network event notification indicating that the UE has reconnected to the network; and the UAE server records (i) the second network event notification, (ii) the identity of the UAE server, and (iii) the most recently updated location information of the UE from the LM server. In this way, more accurate location updates of the user equipment can be obtained. BRIEF DESCRIPTION OF THE DRAWINGS

[0011] Additional features, properties, and various advantages of the disclosed subject matter will become more apparent from the following detailed description and the accompanying drawings, in which:

[0012] Figure 1 is a schematic diagram of an unmanned aerial system (100) according to an embodiment.

[0013] Figure 2 is a networking function model (200) for a Service Enabler Architecture Layer (SEAL) according to an embodiment.

[0014] Figure 3 illustrates a process (300) for real-time unmanned aerial vehicle (UAV) network connection status monitoring and position updating according to an embodiment.

[0015] Figure 4 illustrates a flowchart of a process for real-time network connection status monitoring and / or position updating according to some embodiments of the present disclosure.

[0016] Figure 5 is a schematic diagram of a computer system according to an embodiment. DETAILED DESCRIPTION

[0017] Referring Figure 1 , an unmanned aerial system (UAS) (100) may include an unmanned aerial vehicle (UAV) (101) and a controller (102). The controller (102) may use a data link (103) to transmit control commands from the controller (102) to the UAV (101). The controller (102) may include at least one communication circuit configured to provide communication via a Very High Frequency (VHF) and / or Ultra-high Frequency (UHF) and / or other wireless technologies capable of analog and / or digital radio communication over the data link (103). The controller (102) may control the power level of the propulsion unit (114) of the UAV (101), such as one or more motors, and / or the engine and / or the control surfaces (not depicted) of a model aircraft. More abstract commands similar to those of a helicopter and / or an aircraft, such as pitch, yaw, and roll, may also be used. An experienced pilot may operate the UAV (101) using basic controls without relying on advanced on-board processing of control signals inside the UAV (101). The UAV (101) may be in the form of a helicopter and / or any other aircraft.

[0018] Advances in airborne electronics design allow certain tasks to be transferred from a human operator (or user) 113 to the UAV (101) itself. Many UAVs, such as UAV (101), can include sensors (104) coupled to an on-board control circuitry (105) for sensing the attitude and acceleration of the UAV (101). The on-board control circuitry (105) can be a computer system having a scaled-down user interface and / or no user interface. In addition to control inputs from the controller (102) received from the data link (103), the information obtained by the sensors (104) enables the UAV (101) to remain stable unless a positive control input is obtained from the controller (102).

[0019] The UAV (101) can include a receiver (106) for one of the Global Navigation Satellite Systems (GNSS), such as the Global Positioning System (GPS) operated by the United States. Figure 1 A single satellite (108) that can provide a communication signal (107) is shown to represent the GNSS. However, the receiver (106) of the UAV (101) can receive communications from a GNSS including three or more and typically four or more line-of-sight satellites to triangulate the position of the UAV (101) in space. A GNSS receiver, such as receiver (106), can determine the position and time of the UAV (101) in space with appropriate accuracy. In the UAV (101), in many cases, enhanced GNSS can be performed by additional sensors (e.g., ultrasonic and / or lidar sensors) of the UAV (101) on the most critical vertical (e.g., Z) axis to enable a soft landing (not depicted). The UAV (101) including GNSS capabilities can provide the user with "fly back to home position" and "automatic landing" functions. Thus, the UAV (101) can fly to a position defined as the home position under a simple command from the controller (102) (e.g., a single button press) or in the event of a loss of the data link (103) from the controller or other meaningful control input timeout.

[0020] The UAV (101) may also include one or more imaging devices (109). In some cases, the UAV (101) may include an imaging device mounted on a gimbal as one of the imaging devices (109). The imaging device mounted on the gimbal may be used to record pictures and / or videos of sufficient quality for use by a user (113) of the UAV (101), for example, recorded at high-definition television resolution. The UAV (101) may include other imaging devices (110) for covering some or all of the axes of movement. Onboard signal processing based on the signals of the other imaging devices (110) may be used to prevent the UAV (101) from colliding with stationary or moving objects.

[0021] In some cases, the UAV (101) may include a "main" imaging device as one of the imaging devices (109). The signal of the "main" imaging device may be transmitted in real time via a data link (111) to a human user (e.g., user (113)) and displayed on a display device (112) included in, attached to, and / or separate from the controller (102). The data link (111) may be the same as or different from the data link (103). Thus, the UAV (101) may successfully fly out of the sight of a human pilot using a technique known as "First Person View" (FPV).

[0022] Due to technological developments, UAVs such as the UAV (101) have become rather easy to fly, which in turn has made them popular not only among professional UAV pilots and committed and wealthy hobbyists, but also among the general public. Thus, compared to a few thousand model helicopters sold, if that many, around 15 years ago, millions of UAVs are now sold each year. At the same time, on average, the requirements for the knowledge, proficiency, and level of engagement of the user community have decreased.

[0023] The Service Enablement Architecture Layer (SEAL) may support vertical applications (e.g., UAV and Vehicle to Everything (V2X)). The SEAL functional entities on the user equipment (UE) and the server may be grouped into a SEAL client and a SEAL server, respectively. SEAL may include a set of common services (e.g., group management, location management) and reference points. SEAL may provide its services to the Vertical Application Layer (VAL). VAL may include VAL clients (e.g., UAVs) and VAL servers.

[0024] Figure 2An exemplary networking functional model (200) for a Service Enablement Architecture Layer (SEAL) is shown. The model (200) can be used for network resource management and includes a Vertical Application Layer (VAL) (206) and a SEAL (207) on a 3GPP wireless network such as a 3GPP network system (213) to support vertical applications (e.g., UAV applications and Vehicle-to-Everything (V2X) applications). The model (200) is shown as a functional architecture including general application plane entities and signaling plane entities. A set of general services of the model (200) (e.g., group management, configuration management, location management) can be shared across vertical applications.

[0025] As Figure 2 shown, the VAL (206) can include a VAL client (201) and a VAL server (203). The SEAL (207) can include a SEAL client (202) and a SEAL server (204). The VAL client (201) and the SEAL client (202) can be communicatively coupled to each other to form a user equipment (212). Figure 2 The SEAL functional architecture shown can consider general capabilities to support mission-critical and other vertical applications.

[0026] Referring Figure 2 , the VAL client (201) can communicate with the VAL server (203) via a VAL-UU (205) reference point. The VAL-UU (205) can support both unicast transmission mode and multicast transmission mode.

[0027] The SEAL functional entities on the user equipment (212) and the server can be grouped into a SEAL client (202) and a SEAL server (204) respectively. The SEAL (207) can include a set of general services (e.g., group management, location management) and reference points. The SEAL (207) can provide services to the VAL (206).

[0028] The SEAL client (202) can communicate with the SEAL server (204) via a SEAL-UU (209) reference point. The SEAL-UU (209) can support both unicast transmission mode and multicast transmission mode. The SEAL client (202) can provide service enablement layer support functions to the VAL client (201) via a SEAL-C reference point (208). The VAL server (203) can communicate with the SEAL server (204) via a SEAL-S (211) reference point. The SEAL server (204) can communicate with an underlying 3GPP network system such as a 3GPP network system (213) using a corresponding 3GPP interface (e.g., 210) specified by the 3GPP network system.

[0029] For each SEAL service in the corresponding networking function model, a specific SEAL client (202) and SEAL server (204) can be set up, along with its specific SEAL-UU (209) reference point and specific network interface (210) in the 3GPP network system (213).

[0030] The VAL client (201) can provide client-side functions corresponding to vertical applications (e.g., UAV, V2X client). The VAL client (201) can support interaction with the SEAL client (202).

[0031] The VAL server (203) can provide server-side functions corresponding to vertical applications (e.g., UAV, V2X application server).

[0032] The SEAL client (202) can provide client-side functions corresponding to specific SEAL services such as location management, group management, configuration management, identity management, key management, and network resource management. The SEAL client can support interaction with the VAL client (201). The SEAL client can also support interaction between two UEs with corresponding SEAL clients. For example, the first SEAL client (e.g., SEAL client (202)) of the first UE (e.g., UE (212)) can interact with the second SEAL client (not shown) of the second UE (not shown).

[0033] The SEAL server (204) can provide server-side functions corresponding to specific SEAL services such as location management, group management, configuration management, identity management, key management, and network resource management. The SEAL server (204) can support interaction with the VAL server (203).

[0034] This disclosure includes exemplary information flows and data points configured as follows: enabling real-time network status reporting and location updates for UAS operations under a 3GPP network using the SEAL architecture.

[0035] Figure 2 and Figure 3 shows the network resource and location management of the SEAL architecture.

[0036] Figure 3 The shown Network Resource Management (NRM) server (304) can be a SEAL functional entity that provides management of 3GPP system network resources (e.g., unicast, multicast) to support the SEAL functions of the VAL application (or VAL client) (201). For example, VAL applications can include UAV and V2X.

[0037] Interactions related to the network resource management function between the NRM client and the NRM server (304) can be supported through the NRM-UU reference point. The NRM client can act as Figure 2 the SEAL client (202) in Figure 2 and the NRM-UU can act as

[0038] the SEAL-UU (209) in Figure 3 Interactions related to the network resource management function between the VAL server (203) and the network resource management server (304) can be supported through the NRM-S reference point. The NRM-S reference point can act as the SEAL-S reference point (211). In some embodiments, Figure 3 the UAE (Unmanned Aerial System Application Enabler) server (303) in Figure 2 can act as Figure 3 the VAL server (203) in Figure 2 and the NRM server (304) in

[0039] can act as Figure 2 the SEAL server (204) in

[0040] Similarly, SEAL location management can provide UAS location information. For example, a Location Management (LM) client (301) can interact with an LM server (302) and provide location data to the UAE server (303). The LM client (301) can act as the SEAL client (202), and the LM server (302) can act as the SEAL server (204). Interactions related to the location management function between the LM server (302) and the LM client (301) can be supported through the LM-S reference point, where the LM-S reference point can act as Figure 2 the SEAL-S reference point (211) in

[0040] To obtain network and location information, the UAE server (303) can subscribe to a connection monitoring service for both the UAV and / or the UAV client from the NRM server (304) and also subscribe to the location information of the UAV from the LM server (302). In some embodiments, the UAE server (303) can subscribe to a monitoring event Application Programming Interface (API) for connection monitoring for both the UAV and / or the UAV client through the NRM server (304).

[0041] An exemplary process for a VAL server to subscribe to an NRM server may include the following steps: (i) The VAL server (e.g., UAE server (303)) sends a monitoring event subscription request to the NRM server (e.g., NRM server (304)) to request the NRM server to monitor events related to the VAL UE (e.g., UAV) according to the subscription request, and may include information related to the events that the VAL server is interested in; (ii) The NRM server may check whether the VAL server is authorized to initiate the monitoring event subscription request, and if the VAL server is authorized, the NRM server may respond with a monitoring event subscription response message to indicate the successful subscription status to the VAL server together with the subscription information. The NRM server may use the VAL service ID to export event-specific information in the 3GPP core network service based on the local configuration (e.g., analyze the QoS (Quality of Service, QoS) requirements in the event subscription). The NRM server maps the VAL group ID (if received) to an external group ID known to the 3GPP core network; (iii) Based on the event information of interest in the subscription request message (if applicable), the NRM server may subscribe to UE monitoring events (e.g., LOSS_OF_CONNECTIVITY, COMMUNICATION_FAILURE, etc.) for a set of UEs (VAL UEs) in the subscription request; and (iv) Based on the event information of interest in the subscription request message (if applicable), the NRM server may subscribe to UE analysis events (e.g., ABNORMAL_BEHAVIOUR, etc.) for a set of UEs (VAL UEs) in the subscription request.

[0042] In some embodiments, the UAE server (303) may subscribe to the location information and location deviation monitoring events of the UAV from the LM server (302).

[0043] An exemplary process for subscribing to location information of an LM server (302) may include the following steps: (i) The VAL server sends a location information subscription request to the location management server to subscribe to the location information of one or more VAL users and / or VAL UEs. The request may include an indication for supplementary location information; (ii) The location management server may check whether the VAL server is authorized to initiate a location information subscription request. In addition, the location management server may initiate a location report configuration using the location management client of the UE for immediate reporting; (iii) The location management server may optionally subscribe to the UE location information from the 3GPP core network for the UE. If the indication for supplementary location information is included in step 1, the UE location information is obtained from the 3GPP core network; (iv) The location management server determines the UE location information of the UE received in steps 3 and 4; and (v) The location management server replies with a location information subscription response indicating the subscription status, and if immediate reporting is requested, replies with the location information of the VAL UE.

[0044] When the UAE server subscribes to connection monitoring, location information, and location deviation monitoring events as mentioned above, the UAE server (303) may receive a location report from the LM server (302), as shown in step (S305) of Figure 3 The location report may provide the location information of the UE. The UAE server (303) may record the current location report timestamp. In some embodiments, the UAE server (303) may receive a location report and / or a location deviation monitoring event notification from the LM server (302). In some embodiments, the UAE server (303) may record the current location report timestamp. In an example, the current location report timestamp may indicate the time when the location report is received by the UAE server (303), the time when the location report is sent from the LM server (302), or the time when the location report of the UE is generated. In another example, the current location report timestamp may indicate the time when the location information of the UE is captured.

[0045] An exemplary process for event-triggered location information notification may include the following steps: (i) The location management server receives the latest location information of the UE according to the location reporting process; (ii) The location management server may optionally receive the location information of the UE from the 3GPP core network. If the subscription includes an indication for supplementary location information, obtain the UE location information from the 3GPP core network; (iii) Based on configurations such as subscriptions, periodic location information timers, trigger the location management server to report the latest user location information to the VAL server (e.g., UAE server (303)). The location management server determines the location information of the UE received in steps 1 and 2, including supplementary location information (if indicated); (iv) The location management server sends a location information report including the latest location information of one or more VAL users and / or VAL UEs to the VAL server or to a previously configured location management client; and (v) The VAL server may also share the location information with a group or another VAL user and / or VAL UE.

[0046] An exemplary process for monitoring location deviation may include the following steps: (i) The VAL server (e.g., UAE server (303)) sends a monitoring location subscription request to the LM server; (ii) The LM server (e.g., LM server 302)) processes the area of interest information in the request and then subscribes to UE location monitoring with appropriate parameter mapping. Based on this subscription, the LM server periodically receives VAL UE location information from the 3GPP core network; (iii) The LM server periodically obtains VAL UE location information; (iv) After successful subscription according to steps 2 and 3, the LM server sends a monitoring location subscription response to indicate that the LM server accepts the request from the VAL server and will monitor the location of the VAL UE to verify whether the VAL UE is within the area of interest; (v) If the location information received from the location management client and the core network does not match, the LM server may consider the VAL UE to be outside its specified area of interest and may notify the VAL server ("notify mismatched location" message); (vi) If the current location of the VAL UE from the location management client and the core network matches and is not within the area of interest in the monitoring location subscription request message received from the VAL server, the LM considers the VAL UE to be outside its specified area of interest and may notify the VAL server in a "notify does not exist" message that the current location of the VALUE is outside the area of interest and the VAL UE ID; and (vii) When the current location of the VAL UE is within the area of interest, the LMS (Location Management Server, LMS) may periodically notify the VAL server ("notify exists" message) according to the "Notify_Interval" value in the "monitoring location subscription request" message to indicate to the VAL server that the VAL UE is within the area of interest along with the current location information of the VAL UE.

[0047] The exemplary data points shown in Table 1 may be provided by the LM server to the client requesting location management and / or the VAL server to report location information.

[0048] Table 1: Location Information Report

[0049]

[0050]

[0051] In some embodiments, the current location report timestamp may be in one of several different time formats, such as ISO (International Organization for Standardization, ISO) 8610 (e.g., yyyy - MMM - ddTHH:MM:SS), RFC (Request For Comments, RFC) 1123 (e.g., Monday, DD Mon YYYY HH:MM:SS timezone), Coordinated Universal Time (UTC (Universal Time Coordinated, UTC): yyyy - mn - ddTHH:MM:SS), etc.

[0052] At step (S306), the UAE server (303) may receive a network event notification from the NRM server (304). The event may be related to the loss of reachability of a UE (e.g., a UAV or UAV - C). For example, a network event notification of "Loss_of_connectivity_notification" may be received by the UAE server (303), which indicates the loss of connection of the UE to the 3GPP network. Thus, the UAE server (303) may use the current timestamp to record such an event. The timestamp may indicate the time when the UE is unreachable. The timestamp may also indicate when the network event notification is received by the UAE server (303) or when it is sent from the NRM server (304).

[0053] In some embodiments, the UAE server (303) may receive a monitoring event notification (or network event notification) from the NRM server (304). For example, the process for the NRM server (e.g., the NRM server (304)) to notify the VAL server (e.g., the UAE server (303)) of VAL UE - related events may include the following steps: (i) If applicable, the NRM server receives a monitoring event notification related to the VAL UE from the 3GPP core network; (ii) If applicable, the NRM server receives an analysis event notification related to the VAL UE from the 3GPP core network; and (iii) The NRM server notifies the VAL server of the event related to the VAL UE in the notification monitoring event message. If multiple events are to be notified, the NRM server may aggregate the notifications and send them to the VAL server.

[0054] At step (S307), when the UE re - connection state is detected, the NRM server (304) may send a notification to the UAE server (303). The notification may indicate that the UE has re - connected to the network, such as the 3GPP network (213).

[0055] At step (S308), the UAE server (303) can record such an event using the current timestamp plus the latest known location information and timestamp. Thus, the UAE server (303) can record a notification from the NRM server (304) indicating that the UE has reconnected to the network and the timestamp associated with the notification. The timestamp can indicate the time when the notification was received or sent. The timestamp can also indicate when the UE reconnected to the network. Similarly, the UAE server can record the most recently updated location information of the UE from the LM server (302) and the associated timestamp. The timestamp associated with the most recently updated location information can indicate one or more of the following: the time when the most recently updated location information was generated; the time when the most recently updated location information was sent by the LM server (302); and the time when the most recently updated location information was received by the UAE server (303).

[0056] In some embodiments, the UAE server (303) can record the notification of the UE's reconnection and the associated timestamp, as well as the most recently known location information of the UE and the associated timestamp. The LM server can provide one or more data points, such as one or more of the data points shown in Table 2, to the VAL server (e.g., the UAE server) or the location management client.

[0057] Table 2: Location Information Notification

[0058]

[0059] In some embodiments, as shown at step (308), the UAE server (303) can also trigger a location update when the UAE server (303) receives a notification of the UE's reconnection. For example, the UAE server (303) can trigger a location update. Thus, the LM server (302) can request UE location information by sending a location information request to the LM client (301). Notify and request the VAL user or VAL UE for permission to share their location. The LM client (e.g., 301) responds to the location management server with a report containing location information. In addition, the LM server (302) can send a location report of the UE to the UAE server (303) to provide real-time location information of the UE.

[0060] In some embodiments, the UAE server (303) can record the data points shown in Table 3. For example, the data points can be recorded in step (308) Figure 3 of.

[0061] Table 3: Data Points from Real-Time Network Monitoring and Location Updates

[0062]

[0063] As shown in Table 3, the network event information can be included in a notification from the NRM server (304) indicating the loss of connection of the UE. The network event information can also be included in a notification from the NRM server (304) for indicating the reconnection of the UE. The UAE server ID can be the identifier (or identity) of the UAE server (303) that provides real-time network connection status monitoring and location updates. The location information can indicate the updated location information received from the LM server (302). The updated location information can include the most recently updated location information. For example, the most recently updated location information can be the most recently updated location information obtained from the LM server before the UE disconnects from the network. The most recently updated location information can also be the most recently updated location information obtained from the LM server after the UE reconnects to the network.

[0064] Figure 4 A process (400) for real-time network monitoring and location updates is shown. As Figure 4 shown, the process (400) can start from step (S401) and proceed to step (S410), where a location report can be received by a first server, for example, from a second server. The location report can be received by the Unmanned Aerial System Application Enablement (UAE) server from the Location Management (LM) server of the SEAL architecture. The location report can indicate the location information of the UE.

[0065] At step (S420), a first network event notification associated with the UE can be received by the UAE server from the Network Resource Management (NRM) server in the SEAL architecture. The first network event notification can indicate the connection status of the UE with the network.

[0066] At step (S430), in response to detecting the reconnection status of the UE, a second network event notification can be received by the UAE server from the NRM server, where the second network event notification can indicate that the UE has reconnected to the network.

[0067] At step (S440), the UAE server can record: (i) the second network event notification; (ii) the identity of the UAE server; and (iii) the most recently updated location information of the UE from the LM server.

[0068] In some embodiments, in response to receiving a location report from the LM server, the UAE server can record a timestamp associated with the location report, where the timestamp can indicate the time when the location report was received.

[0069] In process (400), in response to a first network event notification indicating a connection loss event of a UE, the event and a timestamp associated with the event may be recorded by a UAE server, where the timestamp may indicate the time when the event occurred.

[0070] In process (400), a timestamp of a second network event notification may be recorded by a UAE server, where the timestamp may indicate the time when the UE reconnects to the network.

[0071] In some embodiments, a timestamp of the most recently updated location information may be recorded by a UAE server. The timestamp may indicate the time when the most recently updated location information of the UE is received.

[0072] In process (400), a UAE server may trigger a location update between an LM server and an LM client.

[0073] In some embodiments, triggering the location update may cause the LM server to send a location information request to the LM client. In response to the location information request, the LM client may send a location information report to the LM server. The location information report may indicate the most recently updated location information.

[0074] In some embodiments, a UAE server may (i) subscribe to real-time network monitoring from an NRM server and (ii) subscribe to location updates from an LM server.

[0075] Aspects of the unmanned aerial system communication described above may be implemented in a controller and a UAV as computer software using computer-readable instructions and physically stored in one or more computer-readable media such as one or more non-transitory computer-readable storage media. For example, Figure 5 A computer system 600 suitable for implementing certain embodiments of the disclosed subject matter is shown.

[0076] The computer software may be encoded using any suitable machine code or computer language, which may be subject to mechanisms such as assembly, compilation, linking, or the like to create code including instructions that may be directly executed by a processing circuit system such as a computer central processing unit (CPU), a graphics processing unit (GPU), etc., or executed through interpretation, microcode execution, etc.

[0077] The instructions may be executed on various types of computers or their components - including, for example, personal computers, tablet computers, servers, smart phones, gaming devices, Internet of Things devices, etc.

[0078] Figure 5 The components shown for the computer system (600) are exemplary in nature and are not intended to imply any limitation on the scope of use or functionality of computer software for implementing embodiments of the present disclosure. The configuration of the components should not be construed as having any dependencies or requirements related to any one or combination of the components shown in the exemplary embodiments of the computer system (600).

[0079] The computer system (600) may include certain human-machine interface input devices. Such human-machine interface input devices may respond to inputs by one or more human users through, for example, tactile inputs (such as keystrokes, swipes, data glove movements), audio inputs (such as speech, taps), visual inputs (such as gestures), and olfactory inputs (not depicted). The human-machine interface devices may also be used to capture certain media that are not necessarily directly related to conscious human input, such as audio (such as speech, music, ambient sounds), images (such as scanned images, photographic images obtained from a still-image camera device), and video (such as two-dimensional video, three-dimensional video including stereoscopic video).

[0080] The input human-machine interface devices may include one or more of the following (only one of each is depicted): keyboard (601), mouse (602), touchpad (603), touchscreen (610), data glove (not shown), joystick (605), microphone (606), scanner (607), camera device (608).

[0081] The computer system (600) may also include certain human-machine interface output devices. Such human-machine interface output devices may stimulate the senses of one or more human users through, for example, tactile outputs, sounds, lights, and smells / tastes. Such human-machine interface output devices may include: tactile output devices (such as tactile feedback through the touchscreen (610), data glove (not shown), or joystick (605), but there may also be tactile feedback devices that do not function as input devices), audio output devices (such as speakers (609), headphones (not depicted)), visual output devices (such as screens (610), including CRT (Cathode Ray Tube) screens, LCD (Liquid Crystal Display) screens, plasma screens, OLED (Organic Light Emitting Diode) screens, each screen having or not having touchscreen input capabilities, each screen having or not having tactile feedback capabilities, some of which may be capable of outputting two-dimensional visual outputs or more than three-dimensional outputs through means such as stereoscopic graphics output; virtual reality glasses (not depicted), holographic displays, and smell boxes (not depicted)), and printers (not depicted).

[0082] The computer system (600) may also include human-accessible storage devices and their associated media such as optical media, including CD / DVD ROM (Read Only Memory) / RW (Read / Write Memory) (620) having a CD (Compact Disc) / DVD (Digital Video Disk) or similar medium (621), a thumb drive (622), a removable hard disk drive or solid state drive (623), conventional magnetic media such as tapes and floppy disks (not depicted), devices based on dedicated ROM / ASIC (Application Specific Integrated Circuit) / PLD (Programmable Logic Device) such as a security dongle (not depicted), etc.

[0083] Those skilled in the art should also understand that the term "computer-readable medium" used in connection with the presently disclosed subject matter does not include a transmission medium, a carrier wave, or other transient signals.

[0084] The computer system (600) may also include an interface (654) to one or more communication networks (655). The network may be, for example, a wireless network, a wired network, an optical network. The network may also be a local area network, a wide area network, a metropolitan area network, a vehicular and industrial network, a real-time network, a delay-tolerant network, etc. Examples of networks include: local area networks such as Ethernet, wireless LAN (Local Area Network, LAN); cellular networks including GSM (Global System for Mobile Communications, GSM), 3G (Third Generation, 3G), 4G (Fourth Generation, 4G), 5G (Fifth Generation, 5G), LTE (Long-Term Evolution, LTE), etc.; TV wired networks or wireless wide-area digital networks including cable TV (Television, TV), satellite TV, and terrestrial broadcast TV; vehicular and industrial networks including CAN bus (Controller Area Network Bus, CAN Bus), etc. Some networks typically require an external network interface adapter attached to certain general-purpose data ports or peripheral buses (649) (such as, for example, the USB port of the computer system (600)); others are typically integrated into the core of the computer system (600) by attaching to the system bus as described below (for example, integrated into a PC computer system through an Ethernet interface or integrated into a smart phone computer system through a cellular network interface). Using any of these networks, the computer system (600) can communicate with other entities. Such communication can be one-way, receive-only (such as broadcast TV), send-only one-way (such as CAN bus to certain CANbus devices), or two-way, such as two-way communication to other computer systems using a local digital network or a wide-area digital network. Certain protocols and protocol stacks can be used on each of these networks and network interfaces as described above.

[0085] The above-mentioned human-machine interface device, human-accessible storage device, and network interface may be attached to the core (640) of the computer system (600).

[0086] The core (640) may include one or more central processing units (CPUs) (641), a graphics processing unit (GPU) (642), a dedicated programmable processing unit in the form of a field programmable gate area (FPGA) (643), a hardware accelerator (644) for certain tasks, a graphics adapter (650), etc. These devices, together with a read-only memory (ROM) (645), a random access memory (646), an internal mass storage device such as an internal non-user-accessible hard disk drive, a solid-state drive (SSD), etc. (647), may be connected via a system bus (648). In some computer systems, the system bus (648) may be accessed in the form of one or more physical plugs to enable expansion via additional CPUs, GPUs, etc. Peripheral devices may be attached directly or via a peripheral bus (649) to the system bus (648) of the core. In an example, a screen (610) may be connected to the graphics adapter (650). The architecture of the peripheral bus includes PCI (Peripheral Component Interconnect / Interface), USB (Universal Serial Bus), etc.

[0087] The CPU (641), GPU (642), FPGA (643), and accelerator (644) may execute certain instructions, which, in combination, may constitute the above-mentioned computer code. The computer code may be stored in the ROM (645) or a random access memory (RAM) (646). Transitional data may also be stored in the RAM (646), while permanent data may be stored in, for example, the internal mass storage device (647). Fast storage and retrieval of any memory device in the memory devices may be achieved by using a cache memory, which may be closely associated with one or more CPUs (641), GPUs (642), mass storage devices (647), ROM (645), RAM (646), etc.

[0088] Computer-readable media may have computer code for performing various computer-implemented operations. The media and the computer code may be media and computer code specially designed and constructed for the purposes of this disclosure, or the media and the computer code may be of the type well known and available to those skilled in the field of computer software.

[0089] By way of example and not limitation, a computer system (600) having an architecture and in particular a core (640) can provide functionality as a result of a processor (including a CPU, GPU, FPGA, accelerator, etc.) executing software embodied in one or more tangible computer-readable media. Such computer-readable media can be media associated with a user-accessible mass storage device as introduced above, as well as certain non-transitory storage devices of the core (640) such as an on-core mass storage device (647) or ROM (645). The software implementing various embodiments of the present disclosure can be stored in such devices and executed by the core (640). Depending on specific needs, the computer-readable media can include one or more memory devices or chips. The software can cause the core (640) and in particular the processors therein (including a CPU, GPU, FPGA, etc.) to perform specific processes or specific portions of specific processes described herein, including defining data structures stored in RAM (646) and modifying such data structures according to processes defined by the software. Additionally or alternatively, the computer system can provide functionality as a result of logic implemented hardwired or otherwise in circuitry (e.g., an accelerator (644)), which can operate in place of or in conjunction with the software to perform specific processes or specific portions of specific processes described herein. In appropriate cases, references to software can include logic, and references to logic can also include software. In appropriate cases, references to computer-readable media can include circuitry (e.g., an integrated circuit (IC)) storing software for execution, circuitry implementing logic for execution, or both of the above. The present disclosure encompasses any suitable combination of hardware and software.

[0090] Although the present disclosure has described several exemplary embodiments, there are variations, permutations, and various alternative equivalents that fall within the scope of the present disclosure. Accordingly, it will be understood that those skilled in the art will be able to design various systems and methods that, although not explicitly shown or described herein, embody the principles of the present disclosure and are thus within the spirit and scope of the present disclosure.

Claims

1. A method for real-time network monitoring and location updating for a user equipment (UE) in a service enabling architecture layer (SEAL) architecture, characterized in that, The method includes: receiving, by a Unmanned Aerial System Application Enabler (UAE) server, a location report from a Location Management (LM) server in the SEAL architecture, the location report indicating location information of the UE; receiving, by the UAE server, a first network event notification associated with the UE from a Network Resource Management (NRM) server in the SEAL architecture, the first network event notification indicating a connection state of the UE with the network; in response to detecting a reconnection state of the UE, receiving, by the UAE server, a second network event notification from the NRM server, the second network event notification indicating that the UE has reconnected to the network; and recording, by the UAE server, (i) the second network event notification, (ii) an identity of the UAE server, and (iii) the most recently updated location information of the UE from the LM server.

2. The method according to claim 1, characterized in that, Further included is: recording, by the UAE server, a timestamp associated with the location report in response to receiving the location report from the LM server, the timestamp indicating one of: a time at which the location report is received by the UAE server, a time at which the location report is issued by the LM server, and a time at which the location report is generated by the LM server.

3. The method according to claim 1, characterized in that Further included is: recording, by the UAE server, the connection loss event and a timestamp associated with the connection loss event in response to the first network event notification indicating a connection loss event of the UE, the timestamp indicating a time at which the connection loss event occurred.

4. The method according to claim 1, wherein Further included is: recording, by the UAE server, a timestamp of the second network event notification, the timestamp indicating a time at which the UE has reconnected to the network.

5. The method according to claim 1, wherein Further included is: recording, by the UAE server, a timestamp of the most recently updated location information, the timestamp indicating one of: a time at which the most recently updated location information of the UE is received by the UAE server, a time at which the most recently updated location information of the UE is issued by the LM server, and a time at which the most recently updated location information of the UE is generated.

6. The method according to claim 1, characterized in that Further included is: triggering, by the UAE server, a location update between the LM server and an LM client.

7. The method according to claim 6, wherein the triggering further includes causing the LM server to send a location information request to the LM client, and in response to the location information request, sending, by the LM client, a location information report to the LM server, the location information report indicating the most recently updated location information.

8. The method according to claim 1, wherein the UAE server (i) subscribes to the real-time network monitoring from the NRM server and (ii) subscribes to the location update from the LM server.

9. A device, characterized in that, Included is: processing circuitry configured to perform the method according to any one of claims 1-8.

10. A non-transitory computer-readable storage medium storing instructions, characterized in that, When executed by at least one processor of a Unmanned Aerial System Application Enabler (UAE) server, the instructions cause the at least one processor to perform the method according to any one of claims 1 - 8.

11. A device for real-time network monitoring and location updating for a user equipment (UE) in a service enabling architecture layer (SEAL) architecture, characterized in that, The apparatus comprises: a first receiving module, configured to receive, by a Unmanned Aerial System Application Enabler (UAE) server, a location report from a Location Management (LM) server in the SEAL architecture, the location report indicating location information of the UE; a second receiving module, configured to receive, by the UAE server, a first network event notification associated with the UE from a Network Resource Management (NRM) server in the SEAL architecture, the first network event notification indicating a connection state of the UE with the network; a third receiving module, configured to receive, in response to detecting a reconnection state of the UE, a second network event notification from the NRM server by the UAE server, the second network event notification indicating that the UE reconnects to the network; and a recording module, configured to record, by the UAE server, (i) the second network event notification, (ii) an identity of the UAE server, and (iii) the most recently updated location information of the UE from the LM server.

Images