Methods and apparatus for supporting multiple USS for uncrewed aerial vehicle in a wireless communication system

Abstract

The disclosure relates to a fifth generation (5G) or sixth generation (6G) communication system for supporting higher data rates. The present invention relates to supporting multiple USS for UAV (301). A method for supporting multiple USS for UAV includes determining current location of the UAV. Further, the method includes retrieving the USS address from the plurality of USS address which serves different geographical area based on the current location of the UAV. Further, the method includes transmitting the USS address with the current location of the UAV to the network apparatus during UUAA-SM or UUAA-MM procedure.

Description

METHODS AND APPARATUS FOR SUPPORTING MULTIPLE USS FOR UNCREWED AERIAL VEHICLE IN A WIRELESS COMMUNICATION SYSTEM

[0001] This application is based on and derives the benefit of Indian Provisional Application 202441013120 filed on 23rd February 2024, the contents of which are incorporated herein by reference. The proposed embodiments relate to a telecommunication network. More particularly, the present disclosure relates to supporting multiple UAS Service Supplier (USS) for Uncrewed Aerial Vehicle (UAV).

[0002] 5G mobile communication technologies define broad frequency bands such that high transmission rates and new services are possible, and can be implemented not only in “Sub 6GHz” bands such as 3.5GHz, but also in “Above 6GHz” bands referred to as mmWave including 28GHz and 39GHz. In addition, it has been considered to implement 6G mobile communication technologies (referred to as Beyond 5G systems) in terahertz bands (for example, 95GHz to 3THz bands) in order to accomplish transmission rates fifty times faster than 5G mobile communication technologies and ultra-low latencies one-tenth of 5G mobile communication technologies.

[0003] At the beginning of the development of 5G mobile communication technologies, in order to support services and to satisfy performance requirements in connection with enhanced Mobile BroadBand (eMBB), Ultra Reliable Low Latency Communications (URLLC), and massive Machine-Type Communications (mMTC), there has been ongoing standardization regarding beamforming and massive MIMO for mitigating radio-wave path loss and increasing radio-wave transmission distances in mmWave, supporting numerologies (for example, operating multiple subcarrier spacings) for efficiently utilizing mmWave resources and dynamic operation of slot formats, initial access technologies for supporting multi-beam transmission and broadbands, definition and operation of BWP (BandWidth Part), new channel coding methods such as a LDPC (Low Density Parity Check) code for large amount of data transmission and a polar code for highly reliable transmission of control information, L2 pre-processing, and network slicing for providing a dedicated network specialized to a specific service.

[0004] Currently, there are ongoing discussions regarding improvement and performance enhancement of initial 5G mobile communication technologies in view of services to be supported by 5G mobile communication technologies, and there has been physical layer standardization regarding technologies such as V2X (Vehicle-to-everything) for aiding driving determination by autonomous vehicles based on information regarding positions and states of vehicles transmitted by the vehicles and for enhancing user convenience, NR-U (New Radio Unlicensed) aimed at system operations conforming to various regulation-related requirements in unlicensed bands, NR UE Power Saving, Non-Terrestrial Network (NTN) which is UE-satellite direct communication for providing coverage in an area in which communication with terrestrial networks is unavailable, and positioning.

[0005] Moreover, there has been ongoing standardization in air interface architecture / protocol regarding technologies such as Industrial Internet of Things (IIoT) for supporting new services through interworking and convergence with other industries, IAB (Integrated Access and Backhaul) for providing a node for network service area expansion by supporting a wireless backhaul link and an access link in an integrated manner, mobility enhancement including conditional handover and DAPS (Dual Active Protocol Stack) handover, and two-step random access for simplifying random access procedures (2-step RACH for NR). There also has been ongoing standardization in system architecture / service regarding a 5G baseline architecture (for example, service based architecture or service based interface) for combining Network Functions Virtualization (NFV) and Software-Defined Networking (SDN) technologies, and Mobile Edge Computing (MEC) for receiving services based on UE positions.

[0006] As 5G mobile communication systems are commercialized, connected devices that have been exponentially increasing will be connected to communication networks, and it is accordingly expected that enhanced functions and performances of 5G mobile communication systems and integrated operations of connected devices will be necessary. To this end, new research is scheduled in connection with eXtended Reality (XR) for efficiently supporting AR (Augmented Reality), VR (Virtual Reality), MR (Mixed Reality) and the like, 5G performance improvement and complexity reduction by utilizing Artificial Intelligence (AI) and Machine Learning (ML), AI service support, metaverse service support, and drone communication.

[0007] Furthermore, such development of 5G mobile communication systems will serve as a basis for developing not only new waveforms for providing coverage in terahertz bands of 6G mobile communication technologies, multi-antenna transmission technologies such as Full Dimensional MIMO (FD-MIMO), array antennas and large-scale antennas, metamaterial-based lenses and antennas for improving coverage of terahertz band signals, high-dimensional space multiplexing technology using OAM (Orbital Angular Momentum), and RIS (Reconfigurable Intelligent Surface), but also full-duplex technology for increasing frequency efficiency of 6G mobile communication technologies and improving system networks, AI-based communication technology for implementing system optimization by utilizing satellites and AI (Artificial Intelligence) from the design stage and internalizing end-to-end AI support functions, and next-generation distributed computing technology for implementing services at levels of complexity exceeding the limit of UE operation capability by utilizing ultra-high-performance communication and computing resources.

[0008] The present disclosure relates to wireless communication systems and, more specifically, the present disclosure relates to support multiple USS for UAV.

[0009] The principal object of the embodiments herein is to support multiple USS for UAV

[0010] Yet another object of the invention is to support UAS connectivity, identification and tracking in 3GPP.

[0011] Yet another object of the invention is to provide a service to UAV when served by multiple USS.

[0012] In an aspect, the objectives are achieved by providing a method for supporting multiple USS for UAV. The method includes determining, by a UAV, a current location of the UAV. Further, the method includes retrieving, by the UAV, USS address from the plurality of USS address which serves different geographical area based on the current location of the UAV. The geographical area is identified by one of a geolocation identifier (ID), a cell ID, or a Tracking Area (TA). Further, the method includes transmitting, by the UAV, the USS address which serves the current location of the UAV to a network apparatus during a USS UAV Authorization / Authentication Session Management (UUAA-SM) or USS UAV Authorization / Authentication Mobility Management (UUAA-MM) procedure.

[0013] In an embodiment, the UAV retrieves the USS address from one of a pre-configured information or from the USS through the network apparatus during a UUAA-MM or UUAA-SM procedure.

[0014] In an embodiment, the method includes updating, by the UAV, the pre-configured information with the received USS address which serves thegeographical area from the USS through the network apparatus.

[0015] In an embodiment, the network apparatus is one of an Access and Mobility Management Function (AMF), Session Management Function (SMF), and SMF+PDN Gateway Control Plane (PGW-C).

[0016] In another aspect, the objectives are achieved by providing a method for supporting multiple USS for Uncrewed Aerial Vehicle. The method includes receiving, by a UASNF, at least one of a USS address and current location of the UAV from at least one of the UAV or network apparatus during UUAA-MM or UUAA-SM procedure. Further, the method includes determining, by the UASNF, whether the at least one USS address which serves the geographical area matches with the current location of the UAV. Further, the method includes transmitting, by the UASNF, the current location of the UAV to the USS for providing the service to the UAV, when the at least one USS address which serves geographical area matches with the current location of the UAV. Also, the method includes retrieving, by the UANSF, the USS address from the plurality of USS address which serves geographical area based on the received current location of the UAV from the network apparatus, when the at least one USS address which serves the geographical area does not match with the current location of the UAV or when the USS address is not received.

[0017] In an embodiment, the UASNF retrieves the at least one USS address from one of a pre-configured information or from USS through the network apparatus.

[0018] In an embodiment, the method includes receiving, by the UASNF, a subscription request message from a USS to subscribe with plurality of USS to provide service. The subscription request message includes geographical area associated with the plurality of USS. Further, the method includes determining, by the UASNF, current location of the UAV. Further, the method includes providing, by the UASNF, service through notification to a corresponding USS based on the current location of the UAV.

[0019] In yet another aspect, the objectives are achieved by providing a UAV for supporting multiple USS. The UAV includes a processor and a mobility management controller communicatively coupled with the processor. The mobility management controller determines the current location of the UAV. Further, the mobility management controller retrieves the USS address from the plurality of USS address which serves differentgeographical area based on the current location of the UAV. The geographical area is identified by at least one of a geolocation ID, a cell ID, or a Tracking Area. Further, the mobility management controller transmits the USS address associated with the current location of the UAV to the network apparatus during the UUAA-SM or UUAA-MM procedure.

[0020] In yet another aspect, the objectives are achieved by providing a UASNF for supporting multiple USS for UAV. The UASNF includes a processor and a mobility management controller communicatively coupled with the processor. The mobility management controller receives the USS address and current location of the UAV from the UAV through network apparatus during UUAA-MM or UUAA-SM procedure. Further, the mobility management controller determines whether the at least one USS address which serves geographical area matches with the current location of the UAV. Further, the mobility management controller transmits the current location of the UAV to the USS for providing the service to the UAV, when the at least one USS address associated with the corresponding geographical area matches with the current location of the UAV. Also, the mobility management controller retrieves the USS address from the plurality of USS address which serves different geographical area based on the received current location of the UAV from the network apparatus, when the at least one USS address associated with the corresponding geographical area does not match with the current location of the UAV or when the USS address is not received.

[0021] These and other aspects of the embodiments herein will be better appreciated and understood when considered in conjunction with the following description and the accompanying drawings. It should be understood, however, that the following descriptions, while indicating preferred embodiments and numerous specific details thereof, are given by way of illustration and not of limitation. Many changes and modifications can be made within the scope of the embodiments herein.

[0022] In an embodiment, a method performed by an unscrewed aerial vehicle (UAV) in a communication system, the method comprising: identifying whether first information of an address of at least one unscrewed aerial system (UAS) service supplier (USS) and second information of at least one geographical area which the at least one USS serves is configured; and in case that the first information and the second information is configured, based on a current location of the UAV, transmitting, to a UAS network function (UASNF) entity, the address of the at least one USS corresponding to the at least one geographical area; wherein a correct USS is discovered among the at least one USS based on the current location of the UAV.

[0023] In an embodiment, a method performed by an unscrewed aerial vehicle (UAV) service supplier (USS) network function (UASNF) entity in a communication system, the method comprising: based on a current location of the UAV, receiving, from the UAV, an address of at least one USS corresponding to at least one geographical area; identifying whether the address of the at least one USS is configured; and in case that the address of the at least one USS is configured, based on the current location of the UAV, discovering a correct USS among the at least one USS, wherein the UAV is configured with first information of the address of at least one USS and second information of the at least one geographical area which the at least one USS serves is configured.

[0024] In an embodiment, an unscrewed aerial vehicle (UAV) in a communication system, the UAV comprising: a transceiver; and at least one processor connected to the transceiver, wherein the at least one processor is configured to: identify whether first information of an address of at least one unscrewed aerial system (UAS) service supplier (USS) and second information of at least one geographical area which the at least one USS serves is configured, and in case that the first information and the second information is configured, based on a current location of the UAV, transmit, to a UAS network function (UASNF) entity, the address of the at least one USS corresponding to the at least one geographical area, wherein a correct USS is discovered among the at least one USS based on the current location of the UAV.

[0025] In an embodiment, an unscrewed aerial vehicle (UAV) service supplier (USS) network function (UASNF) entity in a communication system, the method comprising: a transceiver; and at least one processor connected to the transceiver, wherein the at least one processor is configured to: based on a current location of the UAV, receive, from the UAV, an address of at least one USS corresponding to at least one geographical area, identify whether the address of the at least one USS is configured, and in case that the address of the at least one USS is configured, based on the current location of the UAV, discover a correct USS among the at least one USS, wherein the UAV is configured with first information of the address of at least one USS and second information of the at least one geographical area which the at least one USS serves is configured.

[0026] According to an embodiment of the disclosure, a wireless communication can be performed efficiently. Especially, a handle handling temporary capability restriction and removal associated with the UE can be performed efficiently.

[0027] These and other features, aspects, and advantages of the present embodiments are illustrated in the accompanying drawings, throughout which like reference letters indicate corresponding parts in the various figures. The embodiments herein will be better understood from the following description with reference to the drawings, in which:

[0028] Fig. 1 is a sequence diagram that illustrates a UUAA-MM procedure, according to embodiments disclosed herein.

[0029] Fig. 2 is a sequence diagram that illustrates a UUAA-SM procedure during PDU establishment, according to embodiments disclosed herein.

[0030] Fig. 3 is a block diagram of UAV for supporting multiple USS, according to embodiments disclosed herein.

[0031] Fig. 4 is a block diagram of UASNF for supporting multiple USS for UAV, according to embodiments disclosed herein.

[0032] Fig. 5 is a flow diagram that illustrates a method for supporting multiple USS by UAV, according to embodiments disclosed herein.

[0033] Fig. 6 is a flow diagram that illustrates a method for supporting multiple USS for UAV by UASNF, according to embodiments disclosed herein.

[0034] Fig. 7 is a sequence diagram that illustrates a supporting multiple USS for UAV based on pre-configuration at UAV, according to embodiments disclosed herein.

[0035] Fig. 8 is a sequence diagram that illustrates a supporting multiple USS for UAV based on pre-configuration at UASNF, according to embodiments disclosed herein.

[0036] Fig. 9 is a sequence diagram that illustrates a scenario of USS subscribing with UASNF on behalf of other USS, according to embodiments disclosed herein.

[0037] 3GPP has defined solutions for UAV to get authenticated and authorized by a USS as part of USS UAV Authorization / Authentication Mobility (UUAA-MM) procedure during registration or USS UAV Authorization / Authentication Session Management (UUAA-SM) during PDU session / PDN connection and then avail aerial services.

[0038] However, it was always assumed that there will be only one USS in the deployment. But there are some use cases where it has been observed that to serve the UAV better, on a flight path, there can be multiple USS in the deployment.

[0039] To address this requirement of multiple USS support, 3GPP has started a study in Rel 19.

[0040] Thus, it is desired to address the above-mentioned disadvantages, issues, or other shortcomings, or at least provide a useful alternative.

[0041] It may be noted that, to the extent possible, like reference numerals have been used to represent like elements in the drawing. Furthermore, those of ordinary skill in the art will appreciate that elements in the drawing are illustrated for simplicity and may not necessarily have been drawn to scale. For example, the dimensions of some of the elements in the drawing may be exaggerated relative to other elements to improve the understanding of aspects of the invention. Further, the elements may have been represented in the drawing by conventional symbols, and the drawings may show only those specific details that are pertinent to understanding the embodiments of the invention so as not to obscure the drawing with details that will be readily apparent to those of ordinary skill in the art having the benefit of the description herein.

[0042] As is traditional in the field, embodiments are described and illustrated in terms of blocks that carry out a described function or functions. These blocks, which are referred to herein as managers, units, modules, hardware components, or the like, are physically implemented by analog and / or digital circuits such as logic gates, integrated circuits, microprocessors, microcontrollers, memory circuits, passive electronic components, active electronic components, optical components, hardwired circuits, and the like, and may optionally be driven by firmware and software. The circuits, for example, may be embodied in one or more semiconductor chips or on substrate supports such as printed circuit boards and the like. The circuits constituting a block may be implemented by dedicated hardware or by a processor (e.g., one or more programmed microprocessors and associated circuitry) or by a combination of dedicated hardware to perform some functions of the block and a processor to perform other functions of the block. Each block of the embodiments may be physically separated into two or more interacting and discrete blocks without departing from the scope of the proposed method. Likewise, the blocks of the embodiments may be physically combined into more complex blocks without departing from the scope of the proposed method.

[0043] Referring now to the drawings, and more particularly to Fig. 1 through Fig. 9 where similar reference characters denote corresponding features consistently throughout the figures, there are shown preferred embodiments.

[0044] Fig. 1 is a sequence diagram that illustrates a UUAA-MM procedure, according to embodiments disclosed herein.

[0045] At step S1, for a UE (101) that requires UUAA or when triggered by re-authentication by USS (107), an Access and Mobility management Function (AMF) (103) triggers a UUAA-MM procedure. If the UE (101) does not have an aerial subscription in the UE subscription data retrieved from the UDM, the AMF (103) shall not trigger the UUAA-MM procedure.

[0046] At step S2, the AMF (103) invokes Nnef-Authentication-AuthenticateAuthorize message to UASNF (105). For initial authentication, the General Public Subscription Identifier (GPSI) and the Capability Authorization Authority (CAA)-Level UAV ID and may include USS address (e.g. FQDN), UUAA Aviation Payload if it was provided by the UE (101). For re-authentication triggered by AMF (103), this may not include the CAA-Level UAV ID. UASNF (105) resolves the USS address based on CAA-Level UAV ID or considers the pre-configured USS addresses per serving area based on the current location of the UAV or uses the provided USS address. In addition, the AMF (103) can also include the User Location Information (e.g. Cell ID). The UASNF (105) should store the serving AMF ID. The AMF (103) identifies the UASNF (105) / NEF based on local configuration or by Network Function (NF) discovery procedure using Data Network Name (DNN) / Single Network Slice Selection Assistance Information (S-NSSAI) and / or UE provided identity e.g. USS address. The AMF (103) also provides a Notification Endpoint to the UASNF (105) or NEF, so that UASNF (105) / NEF can include this Notification Endpoint together with UUAA updated parameters, as shown in clause　5.2.4. By providing the Notification Endpoint, the AMF (103) is implicitly subscribed to be notified of re-authentication, update authorization data or revocation of UAV from UAS NF / NEF, if the UUAA result is successful in step　5.

[0047] At step S3, the UASNF (105) sends Naf-AuthenticationAuthenticateAuthorize Request message, shall include the GPSI and CAA-Level UAV ID and optionally UAV location obtained from AMF (103) in step 2 e.g. to support geo-caging functionality. UASNF (105) / NEF can translate the Cell ID received as UAV location from AMF (103) in step 2 into a corresponding geographic area and / or may further obtain the UE location information using Location Service Procedures as defined in TS　23.273　[8]. The UASNF (105) / NEF also provides a Notification Endpoint to the USS (107), so that USS (107) can include this Notification Endpoint together with UUAA updated parameters, as shown in clause　5.2.4. By providing the Notification Endpoint, the UASNF (105) / NEF is implicitly subscribed to be notified of re-authentication, update authorization data or revocation of UAV from USS, if the UUAA result is successful in step　5.

[0048] At step S4, multiple round-trip messages as required by the authentication method used by USS (107). Naf_Authentication_AuthenticateAuthorize Response messages from USS (107) shall include GPSI and shall include an authentication message based on authentication method used that is forwarded transparently to UE (101) over NAS MM transport messages. The authentication message in step　4d may contain UUAA Aviation Payload required by the USS (107) if it was not provided by the UE (101) before.

[0049] At step S5, the USS (107) sends Naf-Authentication-AuthenticateAuthorize Response message that includes, GPSI, a UUAA result (success / failure) for the UAV and the UASNF (105), can include an authorized / new CAA-Level UAV ID for the UAV and a UUAA Authorization Payload to the UAV (e.g. security info to be used to secure communications with USS) and a final authentication message (e.g. indicating success or failure and if the UUAA is for re-authentication, indicating whether the UAS service related network resource can be released in case of UUAA failure) based on authentication method used that is forwarded transparently to UE over NAS MM transport messages. The USS (107) can send in the Naf_Authentication_AuthenticateAuthorize Response message the information about relevant USSs (i.e. a list of USS addresses, information about geographical area each of the USSs serve). The USS (107) includes that information also inside the UUAA Authorization Payload for the UAV consumption.

[0050] At step S6, the UASNF (105) sends Nnef-Authentication-AuthenticateAuthorize Response message to AMF (103), and forwards information received from USS (107) in step　5. If UUAA for re-authentication failed and UASNF (105) / NEF received indication that the UAS service related network resource can be released in step 5, the UASNF (105) / NEF includes an indication that the PDU sessions associated with the "DNN(s) subject to aerial services" can be released.

[0051] At step S7a, if UUAA-MM succeeded and UASNF (105) / NEF has not subscribed to AMF (103) for the Mobility Event Exposure before, UASNF (105) / NEF subscribes to AMF (103) for the mobility event notification by sending Namf_EventExposure_Subscribe request with the mobility events as described in TS　23.502　[3], Table 5.2.2.3.1-1 with Event ID = Reachability Filter.

[0052] At step 7b, from UASNF (105) / NEF to AMF (103), if UUAA-MM failed and UASNF (105) / NEF has subscribed to AMF (103) for the Mobility Event Exposure earlier, UASNF (105) / NEF unsubscribes to AMF (103) for the mobility event notification by sending Namf_EventExposure_Unsubscribe request with Subscription Correlation ID.

[0053] At step S8a, from AMF (103) to UASNF (105) / NEF, the AMF (103) acknowledges the subscription request from 7a by sending Namf_EventExposure_Subscribe response with Subscription Correlation ID.

[0054] At step S8b, from the AMF (103) acknowledges the un-subscription request from 7b by sending Namf_EventExposure_Unsubscribe response to UASNF (105) / NEF.

[0055] At step 9, the AMF (103) transmits the NAS MM transport message forwarding authentication message from USS including authentication / authorization result (success / failure) and the UUAA Authorization Payload to UE (101).

[0056] At step S10, when UUAA-MM succeeded, the AMF (103) triggers a UE Configuration Update procedure to deliver to the UAV authorization information from USS (107), as described in clause　5.2.2.1.

[0057] At step S11, if UUAA-MM fails during a Re-authentication and Re-authorization and there are PDU session(s) established using UAS services and the USS (107) has indicated that the network resources can be released, AMF (103) can trigger these PDU Sessions release. The AMF (103) identifies the relevant PDU session(s) for UAS services based on the DNN / S-NSSAI value of the PDU session.

[0058] Fig. 2 is a sequence diagram that illustrates a UUAA-SM procedure during PDU establishment, according to embodiments disclosed herein.

[0059] At step S0, the UAV (101) includes the Service Level Device Identity (e.g. the CAA-Level UAV ID of the UVA) and can include the Authentication Server Address (i.e. the USS address or the USS address for the corresponding geographical area based on the UAV current location) and optionally Authentication Data (i.e. the UUAA Aviation Payload) in the PDU Session Establishment request. Further, the SMF (111) determines that it needs to invoke UASNF / NEF (105) service operation for UUAA Authentication / Authorization of the PDU session establishment request based on that the provided DNN / S-NSSAI combination is dedicated for aerial services (have aerial service indicator set) and that the Service Level Device Identity (CAA-Level-UAV ID) is included in the request. If the provided APN / DNN is dedicated for aerial services but Service Level Device Identity (CAA-Level UAV ID) is not provided, the SMF (111) shall reject the establishment of the PDU Session. The SMF (111) identifies the UASNF / NEF (105) based on local configuration or by NF discovery procedure using DNN / S-NSSAI and / or UE (101) provided identity e.g. USS address.

[0060] At step S1, the SMF (111) invokes Nnef-Authentication-AuthenticateAuthorize service operation to UASNF / NEF (105), including the Service Level Device Identity (that contains the CAA-Level UAV ID of the UAV), DNN, S-NSSAI, and can include the Authentication Server Address (i.e. the USS address) and the UUAA Aviation Payload if it was provided by the UE (101), GPSI, optionally UAV location, PEI if available, and the UE IP Address if available. The UAV location is the User Location Information provided by the AMF (103) (e.g. Cell ID). The UASNF / NEF (105) selects a USS (107) based on either the Service Level Device Identity (i.e. CAA-Level UAV ID of the UAV) or the pre-configured USS addresses per serving area based on the current location of the UAV (101) or the Authentication Server address (i.e. USS address) as described in clause　4.4.2. The SMF (111) also provides a Notification Endpoint to the UASNF / NEF (105), so that UASNF / NEF (105) can include this Notification Endpoint together with UUAA updated parameters, as shown in clause　5.2.4. By providing the Notification Endpoint, the SMF (111) is implicitly subscribed to be notified of re-authentication, update authorization data or revocation of UAV (101) from UASNF / NEF (105), if the UUAA result is successful in step　4.

[0061] At step S2, the Naf-Authentication-AuthenticateAuthorize service operation that is received from the SMF (111) is forwarded from UASNF / NEF (105) to USS (107). The UASNF (105) can translate the Cell ID received as part of UAV location in the Nnef-Authentication-AuthenticateAuthorize request at step　1 into a corresponding geographic area and / or may further obtain the UE location information using Location Service Procedures as defined in TS　23.273　[8] and include them in the Naf-Authentication-AuthenticateAuthorize message towards the USS (107) e.g. to support geo-caging functionality. The UASNF / NEF (105) also provides a Notification Endpoint to the USS (107), so that USS (107) can include this Notification Endpoint together with UUAA updated parameters, as shown in clause　5.2.4. By providing the Notification Endpoint, the UASNF / NEF (105) is implicitly subscribed to be notified of re-authentication, update authorization data or revocation of UAV (101) from USS (107), if the UUAA result is successful.

[0062] At step S3, multiple round-trip messages as required by the authentication method used by USS (107). This step　is performed if the Naf-Authentication-AuthenticateAuthorize response messages from USS (107) in step　3a does not contain a UUAA result (SUCCESS / FAILURE). Naf-Authentication-AuthenticateAuthorize response messages from USS (107) shall include GPSI and shall include an authentication message based on authentication method used that is forwarded transparently to UE (101) over NAS MM transport messages. The authentication message in step3e may contain UUAA Aviation Payload required by the USS (107) if it was not provided by the UE (101) before.

[0063] At step S4, the USS (107) sends Naf-Authentication-AuthenticateAuthorize response message to UASNF / NEF (105). The USS (107) sends Naf-Authentication-AuthenticateAuthorize response to the UASNF / NEF (105) with the Authentication / Authorization result containing the UUAA result (SUCCESS / FAILURE) for the UASNF (105) and indication whether the UAS service related network resource can be released in the case of UUAA failure for re-authentication or re-authorization, optionally a Service Level Device Identity containing the authorized CAA-Level UAV ID, requested policy information and the UUAA Authorization Payload. The requested policy information from USS (107) can contain a DN Authorization Profile Index and / or a DN authorized Session AMBR. The USS (107) can include a new CAA-Level UAV ID as authorized CAA-Level UAV ID. The USS (107) can send in the Naf-Authentication-AuthenticateAuthorize response the information about relevant USS (107) (i.e., a list of USS addresses and information about a geographical area each of the USSes serve); the USS (107) includes that information also inside the UUAA Authorization Payload for the UAV consumption.

[0064] At step S5, the UASNF / NEF (105) confirms the successful Authentication / Authorization of the PDU Session. The UASNF / NEF (105) stores the UUAA result together with the GPSI. UASNF / NEF (105) forwards the Authentication / Authorization result, a Service Level Device Identity containing the authorized CAA-Level UAV ID and the Authorization Data (i.e. the UUAA Authorization Payload), if received from the USS (107), to the SMF (111).

[0065] At step S6, if the authentication / authorization is successful, the USS (107) shall subscribe to the PDU Session Status Event. This step　can be executed in parallel to step　4. The UASNF / NEF (105) determines the DNN, S-NSSAI to subscribe to the PDU Session Status Event notification as specified in clause　5.2.3.1.

[0066] At step S7, the PDU Session establishment is continued and completed. Further, if the SMF (111) receives the DN Authorization Profile Index from the UASNF / NEF (105), it sends the DN Authorization Profile Index to retrieve the PDU Session related policy information (described in clause　6.4 of TS　23.503　[9]) and the PCC rule(s) (described in clause　6.3 of TS　23.503　[9]) from the PCF. If the SMF (111) receives the DN authorized Session AMBR in from the UASNF / NEF (105), it sends the DN authorized Session AMBR within the Session AMBR to the PCF to retrieve the authorized Session AMBR (described in clause　6.4 of TS　23.503　[9]). The SMF (111) transfers the Authentication / Authorization result, the Service Level Device Identity containing the authorized CAA-Level UAV ID and the Authorization Data (i.e. the UUAA Authorization Payload) to the UAV (101) if received from the UASNF (105). If the authentication / authorization result is a failure, the SMF (111) rejects the PDU session establishment with a proper cause value.

[0067] At step S8, if the USS (107) is subscribed to the PDU Session Status Event the SMF (111) will, detect when the PDU Session is established, and send the PDU Session Establishment event report to the UASNF / NEF (105) by means of Nsmf-EventExposure-Notify message, including GPSI and the UE IP Address. Then, the UASNF / NEF (105) forwards the event message to the USS (107). If UUAA-SM fails during a Re-authentication and Re-authorization and the USS (107) has indicated that the network resources can be released, SMF (111) may trigger PDU Session release for UAS services with a proper cause value.

[0068] Fig. 3 is the block diagram of UAV for supporting multiple USS, according to embodiments disclosed herein. The UAV (301) is an aircraft that carries no human pilots or passengers. For example, the UAV can be a drone and the like. The UAVs (301) is at least one of a fully or partially autonomous that are more controlled remotely by a human pilot. The UAV (301) includes a processor (303), a memory (305), an I / O interface (307), and a mobility management controller (309). Furthermore, the processor (303) of the UAV (301) communicates with the memory (305), the I / O interface (307), and the mobility management controller (309). The processor (303) is configured to execute instructions stored in the memory (305) and to perform various processes. The processor (303) can include one or a plurality of processors, can be a general-purpose processor such as a central processing unit (CPU), an application processor (AP), or the like, a graphics-only processing unit such as a graphics processing unit (GPU), a visual processing unit (VPU), and / or an Artificial Intelligence (AI) dedicated processor such as a neural processing unit (NPU).

[0069] Furthermore, the memory (305) of the UAV (301) includes storage locations that can be addressed through the processor (303). The memory (305) is not limited to volatile or non-volatile memory and can include one or more computer-readable storage media. Non-volatile storage elements such as magnetic hard disks, optical discs, floppy discs, flash memories, EPROM, or EEPROM memories can also be included in the memory (305). Further, the memory (305) of the UAV (301) can store various information received from UASNF and USS. The UAV (301) can store several pieces of information such as plurality of USS address associated with corresponding geographical area (hereinafter geographical area is interchangeably used as service area), current location of the UAV and the like.

[0070] The I / O interface (307) transmits information between the memory (305) and external peripheral devices, which are input-output devices associated with the UAV (301). The I / O interface (307) receives various information from the UASNF and USS. This interface is used to maintain seamless communication between the UAV (301) and external devices, ensuring that data is transmitted and received. Additionally, the I / O interface (307) facilitates the integration of the UAV (301) with other network components for supporting multiple USS for the UAV.

[0071] The mobility management controller (309) communicates with the I / O interface (307) and the memory (305) for supporting multiple USS for the UAV (301). The mobility management controller (309) is an innovative hardware that is realized through the physical implementation of both analog and digital circuits, including logic gates, integrated circuits, microprocessors, microcontrollers, memory circuits, passive and active electronic components, as well as optical components.

[0072] The mobility management controller (309) determines the current location of the UAV (301). Further, the mobility management controller (309) retrieves the USS address from the plurality of USS address which serves different geographical area based on the current location of the UAV (301). Particularly, each USS address serves a specific geographical area. In an embodiment each USS is associated with a corresponding geographical area. The service area is identified by one of the geolocation identifiers, a cell ID, or a Tracking Area. Further, the mobility management controller (309) transmits the USS address associated with the current location of the UAV (301) to the network apparatus during a UUAA-SM or UUAA-MM procedure. The network apparatus can be, but not limited to AMF, SMF and SMF+PGW-C.

[0073] In an embodiment, the mobility management controller (309) retrieves the USS address from one of the pre-configured information or from USS through the network apparatus during a UUAA-MM or UUAA-SM procedure.

[0074] In an embodiment, the mobility management controller (309) updates the pre-configured information with the received USS address associated with the corresponding service area from the USS through the network apparatus.

[0075] Fig. 4 is the block diagram of UASNF for supporting multiple USS for UAV, according to embodiments disclosed herein.

[0076] The UASNF (401) is a support of aerial functionality related to UAV identification, authentication / authorization and tracking to support remote identification. The UASNF (401) includes a processor (403), a memory (405), an I / O interface (407), and a mobility management controller (409). Furthermore, the processor (403) of the UASNF (401) communicates with the memory (405), the I / O interface (407), and the mobility management controller (409). The processor (403) is configured to execute instructions stored in the memory (405) and to perform various processes. The processor (403) can include one or a plurality of processors, can be a general-purpose processor such as a central processing unit (CPU), an application processor (AP), or the like, a graphics-only processing unit such as a graphics processing unit (GPU), a visual processing unit (VPU), and / or an Artificial Intelligence (AI) dedicated processor such as a neural processing unit (NPU).

[0077] Furthermore, the memory (405) of the UAV (401) includes storage locations that can be addressed through the processor (403). The memory (405) is not limited to volatile or non-volatile memory and can include one or more computer-readable storage media. Non-volatile storage elements such as magnetic hard disks, optical discs, floppy discs, flash memories, EPROM, or EEPROM memories can also be included in the memory (405). Further, the memory (405) of the UASNF (401) can store various information received from the UAV (301) and USS. The UASNF (401) can store several pieces of information such as the USS address associated with the current location of the UAV (301) and the current location of the UAV (301) and the like.

[0078] The I / O interface (407) transmits information between the memory (405) and external peripheral devices, which are input-output devices associated with the UASNF (401). The I / O interface (407) receives various information from the UAV (301) and USS. This interface is used to maintain seamless communication between the UASNF (401) and external devices, ensuring that data is transmitted and received. Additionally, the I / O interface (407) facilitates the integration of the UASNF (401) with other network components for supporting multiple USS for the UAV (301).

[0079] The mobility management controller (409) communicates with the I / O interface (407) and the memory (405) for supporting multiple USS for the UAV (301). The mobility management controller (409) is an innovative hardware that is realized through the physical implementation of both analog and digital circuits, including logic gates, integrated circuits, microprocessors, microcontrollers, memory circuits, passive and active electronic components, as well as optical components.

[0080] The mobility management controller (409) receives the USS address and current location of the UAV (301) from at least one of the UAV (301) or the network apparatus during UUAA-MM or UUAA-SM procedure. Further, the mobility management controller (409) determines whether the USS address associated with the corresponding service area matches with the current location of the UAV (301). Further, the mobility management controller (409) transmits the current location of the UAV (301) to the USS for providing the service to the UAV (301), when the USS address associated with the corresponding service area matches with the current location of the UAV (301). Further, the mobility management controller (409) retrieves the USS address from the plurality of USS address associated with the corresponding service area based on the received current location of the UAV (301) from the network apparatus, when the at least one USS address associated with the corresponding service area does not match with the current location of the UAV (301) or when the USS address is not received.

[0081] In an embodiment, the mobility management controller (409) retrieves the at least one USS address from one of the pre-configured information or from the USS.

[0082] In an embodiment, mobility management controller (409) receives the subscription request message from the USS to subscribe with plurality of USS to provide service. The subscription request message includes service area associated with the plurality of USS. Further, the mobility management controller (409) determines the current location of the UAV (301). Further, the mobility management controller (409) provides the service to a corresponding USS based on the current location of the UAV (301).

[0083] Fig. 5 is the flow diagram that illustrates a method for supporting multiple USS by UAV, according to embodiments disclosed herein.

[0084] At block 501, the method includes determining the current location of the UAV (301).

[0085] At block 503, the method includes retrieving the USS address from the plurality of USS address associated with the corresponding service area based on the current location of the UAV (301). The service area is identified by one of the geolocation ID, the cell ID, or the TA.

[0086] At block 505, the method includes transmitting the USS address associated with the current location of the UAV (301) to the network apparatus during the UUAA-SM or UUAA-MM procedure.

[0087] Fig. 6 is the flow diagram that illustrates the method for supporting multiple USS for UAV by UASNF, according to embodiments disclosed herein.

[0088] At block 601, the method includes receiving the USS address associated with the current location of the UAV (301) and current location of UAV (301) from at least one of the UAV (301) or the network apparatus during UUAA-MM or UUAA-SM procedure.

[0089] At block 603, the method includes determining whether the USS address associated with the corresponding service area matches with the current location of the UAV (301).

[0090] At block 605, the method includes transmitting the current location of the UAV (301) to the USS for providing the service to the UAV (301), when the at least one USS address associated with the corresponding service area matches with the current location of the UAV (301).

[0091] At block 607, the method includes retrieving the USS address from the plurality of USS address associated with the corresponding service area based on the received current location of the UAV (301) from the network apparatus, when the USS address associated with the corresponding service area does not match with the current location of the UAV (301) or when the USS address is not received. The UASNF (401) retrieves the at least one USS address from one of the pre-configured information or from the USS.

[0092] In an embodiment, for multiple USS support, 3GPP has started a study in Rel 19. This study is shown below:

[0093] TR 23.700-59:

[0094] The study (i.e., T KI#1, “Enhancement of NEF services to support service exposure and interactions between MNOs and UTM functions”,) focuses on the scenario of multiple USS serving different geographical areas corresponding to the UAV flight path.

[0095] Unlike the conventional system and methods, the proposed method provides an efficient service to UAV (301) when served by multiple USS. Wherein the UAV (301) while registering with the network, as part of the UUAA-MM procedure, optionally provides the USS address to AMF or UUAA-SM procedure to SMF / SMF+PGW-C during PDU session establishment or PDN connection and then AMF or SMF / SMF+PGW-C was sending the USS address to UASNF / NEF (401). UASNF (401) / Network Exposure Function (NEF) was using this USS address received from AMF or SMF / SMF+PGW-C to discover the USS. As now there can be multiple USSs that serve different geographic areas, hence it is proposed that UAV (301) should be pre-configured with USS address along with the corresponding service area in the form of geolocation ID / cell ID / TAs, etc which the USS serves.

[0096] It is also proposed that the UAV (301) use the location information (where the UAV is present) to retrieve the corresponding USS address and send the same USS address in the UUAA-MM or UUAA-SM procedure.

[0097] In an embodiment, the UASNF (401) is configured with the USS addresses along with service area information that that USS serves. When UASNF (401) does not receive the USS address from AMF or SMF / SMF+PGW-C then it shall use the stored configuration of the USS address to fetch based on the UAV location which it receives from AMF or SMF / SMF+PGW-C. In this way, UASNF (401) can discover the correct USS address that serves the area where the UAV is actually located.

[0098] In another embodiment, if the USS address is not received by UASNF (401), nor the UASNF (401) have the information of USS address per location then it is proposed that using the existing logic of USS serving one UAV identified by CAA-Level-ID, a USS is discovered. The UASNF (401) provides the location of the UAV (301) to USS. After the USS identifies that the UAV (301) is in a different location which needs to be served by a different USS, sends the correct address (target USS address) to UASNF (401). In this case, the UASNF (401) will send to the correct USS address received from the first (source) and continue the UUAA-MM or UUAA-SM procedure with this new / target USS. After the successful UUAA-MM or UUAA-SM procedure, the serving USS address along with other USS address and the corresponding location these USS serves is sent to UAV (301). Whenever there is an update to the USSs serving different location happens, then the serving USS can invoke the UUAA re-authentication procedure to provide these updated USS address along with location details of which these USS serves to UAV (301).

[0099] The USS while subscribing with UASNF (401), can subscribe on behalf of other USSs as well by providing the corresponding locations which these USSs serve. It is proposed that UASNF (401) can subscribe to the location of UAV (301) and based on the location or whenever it receives updated location information from AMF / SMF / SMF+PGW-C or any other NF, it can notify the corresponding USS serving that location (service area). In this way, each USS need not to subscribe.

[0100] Fig. 7 is a sequence diagram that illustrates a supporting multiple USS for UAV based on pre-configuration at UAV, according to embodiments disclosed herein.

[0101] At step S1, the UAV (301) is pre-configured with plurality of USS address associated with the corresponding service area or have received from the network apparatus (701) during UUAA-MM or UUAA-SM procedure. The service area is identified by the geolocation ID, the cell ID, the Tracking Area and the like. The UAV (301) stores the received plurality of USS address associated with corresponding service area. Further, the UAV (301) can retrieve the USS address that is serving the UAV (301) based on the current location of the UAV (301). The UAV (301) maps the current location and the corresponding service area for which the USS is serving.

[0102] Further, at step S2, the UAV (301) when registering with the network, as part of UUAA-MM procedure, provides the USS address to AMF (701). In an embodiment, the UAV (301) as a part of UUAA-SM procedure, sends the USS address to SMF / SMF+PGW-C (701) during PDU session establishment or PDN connection. The USS address provided to the AMF or SMF / SMF+PGW-C (701) is associated with the current location of the UAV (301).

[0103] Further, at step S3, the AMF or the SMF / SMF+PGW-C (701) forwards the USS address associated with the current location of the UAV (301) to the UASNF (401). In an embodiment, the AMF or the SMF / SMF+PGW-C (701) sends the USS address associated with the current location of the UAV (301) to NEF.

[0104] Further, at step S4, the UASNF (401) discovers the USS1 (703) based on the received USS address associated with current location of the UAV (301), among the multiple USS that serves different geographic area. Upon discovering, the UASNF (401) sends the current location of the UAV (301) to the USS1 (703).

[0105] At step S5, the UUAA-MM or the UUAA-SM is finished followed by registration or a PDU session / PDU connection so that all the USS addresses and the corresponding area that USS serves is updated to the UAV (301).

[0106] Fig. 8 is the sequence diagram that illustrates the supporting multiple USS for UAV based on pre-configuration at UASNF, according to embodiments disclosed herein.

[0107] At step S1, the UASNF (401) is configured with plurality of USS address associated with corresponding service area that the USS serves.

[0108] Further, at step S2 the UAV (301) triggers registration to the AMF (701) (UUAA-MM) or the PDU session / PDN connection SMF / SMF+PGW-C (701) (UUAA-SM).

[0109] Further, at step S3, AMF or SMF / SMF+PGW-C (701) sends the current location of the UAV (301) to the UASNF (401).

[0110] At step S4, when UASNF (401) does not receive the USS address from AMF or SMF / SMF+PGW-C (701) then it uses the stored configuration of the USS address to fetch based on the UAV location which it receives from AMF or SMF / SMF+PGW-C (701). Upon discovering, the UASNF (401) sends the UAV location to the USS1 (703).

[0111] At step S5, the UUAA-MM or the UUAA-SM is finished followed by the registration or the PDU session / PDU connection. So that all the USS addresses and corresponding areas that the USS serves is updated to the UAV (301).

[0112] Fig. 9 is the sequence diagram that illustrates the scenario of USS subscribing with UASNF on behalf of other USS, according to embodiments disclosed herein.

[0113] At step S1, the UAV (301) triggers registration to the AMF (701) (UUAA-MM) or the PDU session / PDN connection SMF / SMF+PGW-C (701) (UUAA-SM).

[0114] At step S2, the AMF / SMF / SMF+PGW-C (701) provides the UAV location to the UASNF (401) (i.e., Area2).

[0115] At step S3, the USS1 (703) is discovered by the UASNF (401) based on the existing info of the USS1 (703) that is serving the UAV1. Further, the UASNF (401) sends the Area 2 as the location.

[0116] At step S4, the USS1 (703) finds that in Area2, the USS2 (705) serves the UAV (301).

[0117] At step S5, the USS1 (703) responds with the USS2 address to the UASNF (401).

[0118] At step S6, the UASNF (401) sends to the USS2 (705) along with the UAV location Area2;

[0119] At step S7, the UUAA-MM or the UUAA-SM is finished followed by the registration or the PDU session / PDU connection. So that all the USS addresses and corresponding areas that the USS serves are updated to the UAV (301).

[0120] The foregoing description of the specific embodiments will fully reveal the general nature of the embodiments herein such that others can readily modify and / or adapt such specific embodiments for various applications without departing from the generic concept. Therefore, such adaptations and modifications are intended to be comprehended within the meaning and range of equivalents of the disclosed embodiments. It is to be understood that the phraseology or terminology employed herein is for the purpose of description and not of limitation. Thus, while the embodiments herein have been described in terms of preferred embodiments, those skilled in the art will recognize that the embodiments herein can be practiced with modifications within the scope of the embodiments as described herein.

Claims

1.A method performed by an unscrewed aerial vehicle (UAV) in a communication system, the method comprising:identifying whether first information of an address of at least one unscrewed aerial system (UAS) service supplier (USS) and second information of at least one geographical area which the at least one USS serves is configured; andin case that the first information and the second information is configured, based on a current location of the UAV, transmitting, to a UAS network function (UASNF) entity, the address of the at least one USS corresponding to the at least one geographical area;wherein a correct USS is discovered among the at least one USS based on the current location of the UAV.2.The method of claim 1,wherein the UASNF entity is configured with the address of the at least one USS, andwherein each of the at least one USS serves a different geographical area.3.The method of claim 1, further comprising:based on the current location of the UAV, transmitting, to a network entity function (NEF) entity, the address of the at least one USS,wherein the geographical area is associated with a flight path of the UAV.4.The method of claim 1,wherein the correct USS is discovered during at least one of an USS UAV authorization authentication (UUAA) procedure, an UUAA mobility management (MM) procedure, a protocol data unit (PDU) session establishment procedure, or a packet data network (PDN) connection procedure.5.A method performed by an unscrewed aerial vehicle (UAV) service supplier (USS) network function (UASNF) entity in a communication system, the method comprising:based on a current location of the UAV, receiving, from the UAV, an address of at least one USS corresponding to at least one geographical area;identifying whether the address of the at least one USS is configured; andin case that the address of the at least one USS is configured, based on the current location of the UAV, discovering a correct USS among the at least one USS,wherein the UAV is configured with first information of the address of at least one USS and second information of the at least one geographical area which the at least one USS serves is configured.6.The method of claim 5,wherein each of the at least one USS serves a different geographical area.7.The method of claim 5, wherein the geographical area is associated with a flight path of the UAV.8.The method of claim 5,wherein the correct USS is discovered during at least one of an USS UAV authorization authentication (UUAA) procedure, an UUAA mobility management (MM) procedure, a protocol data unit (PDU) session establishment procedure, or a packet data network (PDN) connection procedure.9.An unscrewed aerial vehicle (UAV) in a communication system, the UAV comprising:a transceiver; andat least one processor connected to the transceiver, wherein the at least one processor is configured to: identify whether first information of an address of at least one unscrewed aerial system (UAS) service supplier (USS) and second information of at least one geographical area which the at least one USS serves is configured, andin case that the first information and the second information is configured, based on a current location of the UAV, transmit, to a UAS network function (UASNF) entity, the address of the at least one USS corresponding to the at least one geographical area,wherein a correct USS is discovered among the at least one USS based on the current location of the UAV.10.The UAV of claim 9,wherein the UASNF entity is configured with the address of the at least one USS, andwherein each of the at least one USS serves a different geographical area.11.The UAV of claim 9, wherein the at least one processor is further configured to:based on the current location of the UAV, transmit, to a network entity function (NEF) entity, the address of the at least one USS,wherein the geographical area is associated with a flight path of the UAV.12.The UAV of claim 9,wherein the correct USS is discovered during at least one of an USS UAV authorization authentication (UUAA) procedure, an UUAA mobility management (MM) procedure, a protocol data unit (PDU) session establishment procedure, or a packet data network (PDN) connection procedure.13.An unscrewed aerial vehicle (UAV) service supplier (USS) network function (UASNF) entity in a communication system, the method comprising:a transceiver; andat least one processor connected to the transceiver, wherein the at least one processor is configured to:based on a current location of the UAV, receive, from the UAV, an address of at least one USS corresponding to at least one geographical area,identify whether the address of the at least one USS is configured, andin case that the address of the at least one USS is configured, based on the current location of the UAV, discover a correct USS among the at least one USS,wherein the UAV is configured with first information of the address of at least one USS and second information of the at least one geographical area which the at least one USS serves is configured.14.The UASNF entity of claim 13,wherein each of the at least one USS serves a different geographical area, andwherein the geographical area is associated with a flight path of the UAV.15.The UASNF entity of claim 13,wherein the correct USS is discovered during at least one of an USS UAV authorization authentication (UUAA) procedure, an UUAA mobility management (MM) procedure, a protocol data unit (PDU) session establishment procedure, or a packet data network (PDN) connection procedure.

Images