Communication and storage of aircraft system security information

Abstract

An apparatus, method and system for communicating and storing aircraft system security information is provided. The method begins by sending 602 a request message to an unmanned aircraft system network function, a network publishing function, or a combination thereof. The request message includes an air vehicle identifier, a public subscription identifier, and security policy information. The method also receives 604 a response message from the unmanned aircraft system network function, the network publishing function, or a combination thereof. The response message includes the air vehicle identifier, the public subscription identifier, an air vehicle authentication result, an authorization result, or a combination thereof, and aircraft system security requirement information. The method further stores 606 the aircraft system security requirement information along with the air vehicle identifier, the public subscription identifier, and the air vehicle authentication result.

Description

[Technical Field]

[0001] The subject matter disclosed herein relates generally to wireless communications, and more particularly to communicating and storing aerial system security information. [Background technology]

[0002] In certain wireless communication networks, different network devices may not be aware of when authentication has been completed by another network device in the system, which can waste data transmission and / or time in such networks. Summary of the Invention [Means for solving the problem]

[0003] A method for communicating and storing aircraft system security information is disclosed. Apparatus and systems also perform the functions of the method. One embodiment of the method includes sending a request message from an access and mobility management function to an unmanned aircraft system network function, a network publishing function, or a combination thereof, where the request message includes an air vehicle identifier, a public subscription identifier, and security policy information. In some embodiments, the method includes receiving a response message from the unmanned aircraft system network function, the network publishing function, or a combination thereof, where the response message includes the air vehicle identifier, the public subscription identifier, air vehicle authentication results, authorization results, or a combination thereof, and aircraft system security requirement information. In a particular embodiment, the method includes storing the aircraft system security requirement information along with the air vehicle identifier, the public subscription identifier, and the air vehicle authentication results.

[0004] One apparatus for communicating and storing aircraft system security information includes an access and mobility management function. In some embodiments, the apparatus includes a transmitter that transmits a request message to an unmanned aircraft system network function, a network publishing function, or a combination thereof, the request message including an air vehicle identifier, a public subscription identifier, and security policy information. In various embodiments, the apparatus includes a receiver that receives a response message from the unmanned aircraft system network function, the network publishing function, or a combination thereof, the response message including the air vehicle identifier, the public subscription identifier, air vehicle authentication results, authorization results, or a combination thereof, and aircraft system security requirement information. In particular embodiments, the apparatus includes a processor that stores the aircraft system security requirement information along with the air vehicle identifier, the public subscription identifier, and the air vehicle authentication results.

[0005] Another embodiment of a method for communicating and storing aircraft system security information includes receiving a first request message from an access and mobility management function at an unmanned aircraft system network function, a network publishing function, or a combination thereof, wherein the first request message includes an air vehicle identifier, a public subscription identifier, and security policy information. In some embodiments, the method includes sending a second request message to an unmanned aircraft system service supplier, an unmanned aircraft system traffic management function, or a combination thereof, wherein the second request message includes the air vehicle identifier, the public subscription identifier, and security policy information. In particular embodiments, the method includes receiving a second response message from the unmanned aircraft system service supplier, the unmanned aircraft system traffic management function, or a combination thereof, wherein the second response message includes the air vehicle identifier, the public subscription identifier, the air vehicle authentication result, and aircraft system security requirement information. In various embodiments, the method includes sending a first response message to the access and mobility management function, the first response message including an air vehicle identifier, a public subscription identifier, an air vehicle authentication result, and aircraft system security requirement information. In some embodiments, the method includes storing the aircraft system security requirement information with the air vehicle identifier, the public subscription identifier, and the air vehicle authentication result.

[0006] Another apparatus for communicating and storing aircraft system security information includes an unmanned aircraft system network function, a network publishing function, or a combination thereof. In some embodiments, the apparatus includes a receiver that receives a first request message from an access and mobility management function, the first request message including an air vehicle identifier, a public subscription identifier, and security policy information. In various embodiments, the apparatus includes a transmitter that transmits a second request message to an unmanned aircraft system service supplier, an unmanned aircraft system traffic management function, or a combination thereof, the second request message including the air vehicle identifier, the public subscription identifier, and security policy information. In particular embodiments, the apparatus includes a processor. The receiver receives a second response message from the unmanned aircraft system service supplier, the unmanned aircraft system traffic management function, or a combination thereof, the second response message including an air vehicle identifier, a public subscription identifier, an air vehicle authentication result, and aircraft system security requirement information; the transmitter sends a first response message to the access and mobility management function, the first response message including the air vehicle identifier, the public subscription identifier, the air vehicle authentication result, and the aircraft system security requirement information; and the processor stores the aircraft system security requirement information together with the air vehicle identifier, the public subscription identifier, and the air vehicle authentication result.

[0007] A further embodiment of a method for communicating and storing aircraft system security information includes sending a third request message from a session management function to an unmanned aircraft system network function, a network publishing function, or a combination thereof, where the third request message includes an air vehicle identifier, a public subscription identifier, and a data request indication. In some embodiments, the method includes receiving a third response message from the unmanned aircraft system network function, the network publishing function, or a combination thereof, where the third response message includes the air vehicle identifier, the public subscription identifier, an air vehicle authentication result, and aircraft system security requirement information. In particular embodiments, the method includes determining to establish a protocol data unit session and skipping air vehicle authentication in response to receiving the air vehicle authentication result. In various embodiments, the method includes storing the aircraft system security requirement information together with the air vehicle identifier, the public subscription identifier, the air vehicle authentication result, and the aircraft system security requirement information. In some embodiments, the method includes applying user plane security based on the aircraft system security requirement information.

[0008] A further apparatus for communicating and storing aircraft system security information includes a session management function. In some embodiments, the apparatus includes a transmitter that transmits a third request message to the unmanned aircraft system network function, the network publishing function, or a combination thereof, where the third request message includes an air vehicle identifier, a public subscription identifier, and a data request indication. In various embodiments, the apparatus includes a receiver that receives a third response message from the unmanned aircraft system network function, the network publishing function, or a combination thereof, where the third response message includes the air vehicle identifier, the public subscription identifier, the air vehicle authentication result, and the aircraft system security requirement information. In particular embodiments, the apparatus includes a processor that, in response to receiving the air vehicle authentication result, determines to establish a protocol data unit session, skips air vehicle authentication, stores the aircraft system security requirement information together with the air vehicle identifier, the public subscription identifier, the air vehicle authentication result, and the aircraft system security requirement information, and applies user plane security based on the aircraft system security requirement information.

[0009] Another embodiment of a method for communicating and storing aircraft system security information includes receiving, at an unmanned aircraft system service supplier, an unmanned aircraft system traffic management function, or a combination thereof, a request message from an unmanned aircraft system network function, a network publishing function, or a combination thereof, where the request message includes an air vehicle identifier, a public subscription identifier, and security policy information. In some embodiments, the method includes sending a response message to the unmanned aircraft system network function, the network publishing function, or a combination thereof, where the response message includes the air vehicle identifier, the public subscription identifier, the air vehicle authentication result, and the aircraft system security requirement information. In particular embodiments, the method includes storing the aircraft system security requirement information with the air vehicle identifier, the public subscription identifier, and the air vehicle authentication result.

[0010] Another apparatus for communicating and storing aircraft system security information includes an unmanned aircraft system service supplier, an unmanned aircraft system traffic management function, or a combination thereof. In some embodiments, the apparatus includes a receiver that receives a request message from an unmanned aircraft system network function, a network publishing function, or a combination thereof, the request message including an air vehicle identifier, a public subscription identifier, and security policy information. In various embodiments, the apparatus includes a transmitter that sends a response message to the unmanned aircraft system network function, the network publishing function, or a combination thereof, the response message including the air vehicle identifier, the public subscription identifier, the air vehicle authentication result, and the aircraft system security requirement information. In particular embodiments, the apparatus includes a processor that stores the aircraft system security requirement information with the air vehicle identifier, the public subscription identifier, and the air vehicle authentication result.

[0011] A more particular description of the embodiments briefly described above will be made by reference to specific embodiments that are illustrated in the accompanying drawings. The embodiments will be described and explained with additional specificity and detail through the use of the accompanying drawings, understanding that these drawings illustrate some embodiments only and therefore should not be considered limiting in scope. [Brief explanation of the drawings]

[0012] [Figure 1] FIG. 1 is a schematic block diagram illustrating one embodiment of a wireless communication system for communicating and storing aircraft system security information. [Figure 2] FIG. 1 is a schematic block diagram illustrating one embodiment of an apparatus that may be used to communicate and store aircraft system security information. [Figure 3] FIG. 1 is a schematic block diagram illustrating one embodiment of an apparatus that may be used to communicate and store aircraft system security information. [Figure 4] FIG. 1 is a schematic block diagram illustrating one embodiment of a system for user plane security requirement retrieval from a USS and / or UTM. [Figure 5] FIG. 1 is a schematic block diagram illustrating one embodiment of a system for providing UUAA results and UAS security requirement information to an SMF. [Figure 6] FIG. 2 is a flow chart diagram illustrating one embodiment of a method for communicating and storing aircraft system security information. [Figure 7] FIG. 4 is a flow chart diagram illustrating another embodiment of a method for communicating and storing aircraft system security information. [Figure 8] FIG. 10 is a flow chart diagram illustrating a further embodiment of a method for communicating and storing aircraft system security information. [Figure 9] FIG. 4 is a flow chart diagram illustrating yet another embodiment of a method for communicating and storing aircraft system security information. DETAILED DESCRIPTION OF THE INVENTION

[0013] As will be appreciated by those skilled in the art, aspects of the embodiments may be embodied as a system, apparatus, method, or program product. Accordingly, the embodiments may take the form of an entirely hardware embodiment, an entirely software embodiment (including firmware, resident software, microcode, etc.), or an embodiment combining software and hardware aspects, all of which may be referred to generally herein as a "circuit," "module," or "system." Furthermore, the embodiments may take the form of a program product embodied in one or more computer-readable storage devices that store machine-readable code, computer-readable code, and / or program code, hereinafter referred to as code. The storage devices may be tangible, non-transitory, and / or non-transmittable. The storage devices may not embody signals; in certain embodiments, the storage devices merely use signals to access the code.

[0014] Some of the functional units described herein may be labeled as modules to more fully emphasize their implementation independence. For example, a module may be implemented as a hardware circuit comprising custom very large scale integrated ("VLSI") circuits or gate arrays, off-the-shelf semiconductors such as logic chips, transistors, or other discrete components. A module may also be implemented in a programmable hardware device such as a field programmable gate array, programmable array logic, or programmable logic device.

[0015] Modules may also be implemented in code and / or software for execution by various types of processors. An identified module of code may, for example, include one or more physical or logical blocks of executable code, which may be organized as, for example, an object, a procedure, or a function. Although, the executable files of an identified module need not be physically located together, but may include different instructions stored in different locations that, when logically combined, comprise the module and achieve the stated purpose of the module.

[0016] In practice, a module of code may be a single instruction or many instructions, and may even be distributed across several different code segments, among different programs, and across several memory devices. Similarly, operational data may be identified and depicted herein in modules and may be embodied in any suitable form and organized in any suitable type of data structure. Operational data may be collected as a single data set or distributed across different locations, including across different computer-readable storage devices. When a module or portions of a module are implemented in software, the software portions are stored on one or more computer-readable storage devices.

[0017] Any combination of one or more computer-readable mediums may be utilized. The computer-readable medium may be a computer-readable storage medium. The computer-readable storage medium may be a storage device that stores code. The storage device may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, holographic, micro-mechanical, or semiconductor system, apparatus, or device, or any suitable combination of the above.

[0018] More specific examples (a non-exhaustive list) of storage devices would include an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory ("RAM"), a read-only memory ("ROM"), an erasable programmable read-only memory ("EPROM" or Flash memory), a portable compact disc read-only memory ("CD-ROM"), an optical storage device, a magnetic storage device, or any suitable combination of the above. In the context of this document, a computer-readable storage medium may be any tangible medium that contains or is capable of storing a program for use by or in connection with an instruction execution system, apparatus, or device.

[0019] The code to perform operations for the embodiments may be any number of lines and may be written in any combination of one or more programming languages, including object-oriented programming languages ​​such as Python, Ruby, Java, Smalltalk, or C++, and traditional procedural programming languages ​​such as the "C" programming language, and / or machine languages ​​such as assembly language. The code may run entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer through any type of network, including a local area network ("LAN") or a wide area network ("WAN"), or the connection to the external computer may be made (e.g., through the Internet using an Internet Service Provider).

[0020] References throughout this specification to "one embodiment," "an embodiment," or similar language mean that a particular feature, structure, or characteristic described with respect to an embodiment is included in at least one embodiment. Thus, appearances of the phrases "in one embodiment," "in an embodiment," and similar language throughout this specification all mean "one or more, but not all, embodiments," although they may, but do not necessarily, refer to the same embodiment, unless expressly stated otherwise. The terms "including," "comprising," and "having," and variations thereof, mean "including, but not limited to," unless expressly stated otherwise. An enumerated list of items does not imply that any or all of the items are mutually exclusive unless expressly stated otherwise. The terms "a," "an," and "the" also refer to "one or more," unless expressly stated otherwise.

[0021] Furthermore, the described features, structures, or characteristics of the embodiments may be combined in any suitable manner. In the following description, numerous specific details are provided, such as examples of programming, software modules, user selections, network transactions, database queries, database structures, hardware modules, hardware circuits, hardware chips, etc., to provide a thorough understanding of the embodiments. However, one skilled in the art will recognize that the embodiments may be practiced without one or more of the specific details, or with other methods, components, materials, etc. In other instances, well-known structures, materials, or operations are not shown or described in detail to avoid obscuring aspects of an embodiment.

[0022] Aspects of the embodiments are described below with reference to schematic flowchart illustrations and / or schematic block diagrams of methods, apparatus, systems, and program products according to the embodiments. It will be understood that each block of the schematic flowchart illustrations and / or schematic block diagrams, and combinations of blocks in the schematic flowchart illustrations and / or schematic block diagrams, may be implemented by code. The code may be provided to a processor of a general-purpose computer, special-purpose computer, or other programmable data processing apparatus to produce machine instructions that, when executed by the processor of the computer or other programmable data processing apparatus, produce means for implementing the functions / acts specified in one or more blocks of the schematic flowchart illustrations and / or schematic block diagrams.

[0023] Code capable of instructing a computer, other programmable data processing apparatus, or other device to function in a particular manner may also be stored in a storage device, such that the instructions stored on the storage device produce an article of manufacture including instructions that implement the functions / acts specified in one or more blocks of the schematic flowchart diagrams and / or schematic block diagrams.

[0024] The code may also be loaded onto a computer, other programmable data processing apparatus, or other device to cause the computer, other programmable data processing apparatus, or other device to perform a series of operational steps, creating a computer-implemented process, such that the code running on the computer or other programmable data processing apparatus provides a process for implementing the functions / acts specified in one or more blocks of the flowchart diagrams and / or block diagrams.

[0025] The schematic flowchart diagrams and / or schematic block diagrams in the Figures illustrate the architecture, functionality, and operation of possible implementations of apparatus, systems, methods, and program products according to various embodiments. In this regard, each block in the schematic flowchart diagrams and / or schematic block diagrams may represent a module, segment, or portion of code, which includes one or more executable instructions of code for implementing the specified logical function(s).

[0026] It should also be noted that in some alternative implementations, the functions noted in the blocks may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending on the functionality involved. Other steps and methods may be contemplated that are equivalent in function, logic, or effect to one or more blocks of the illustrated figures, or portions thereof.

[0027] While various arrow and line types may be used in the flowchart diagrams and / or block diagrams, it is understood that these do not limit the scope of the corresponding embodiments. Indeed, some arrows or other connectors may be used to indicate only the logical flow of the illustrated embodiments. For example, arrows may indicate wait or monitoring periods of unspecified duration between enumerated steps of the illustrated embodiments. It should also be noted that each block of the block diagrams and / or flowchart diagrams, and combinations of blocks in the block diagrams and / or flowchart diagrams, may be implemented by a dedicated hardware-based system that performs the specified functions or acts, or a combination of dedicated hardware and code.

[0028] The description of an element in each figure may refer to the element in the preceding figure. Like numbers refer to like elements in all figures, including alternative embodiments of like elements.

[0029] 1 illustrates one embodiment of a wireless communication system 100 for communicating and storing aircraft system security information. In one embodiment, the wireless communication system 100 includes a remote unit 102 and a network unit 104. While a particular number of remote units 102 and network units 104 are illustrated in FIG. 1, those skilled in the art will recognize that any number of remote units 102 and network units 104 may be included in the wireless communication system 100.

[0030] In one embodiment, the remote unit 102 may include a computing device such as a desktop computer, a laptop computer, a personal digital assistant ("PDA"), a tablet computer, a smartphone, a smart television (e.g., a television connected to the Internet), a set-top box, a game console, a security system (including a security camera), a vehicle-mounted computer, a network device (e.g., a router, a switch, a modem), an air vehicle, or a drone. In some embodiments, the remote unit 102 includes a wearable device such as a smart watch, a fitness band, or an optical head-mounted display. Furthermore, the remote unit 102 may be referred to as a subscriber unit, a mobile, a mobile station, a user, a terminal, a mobile terminal, a fixed terminal, a subscriber station, a UE, a user terminal, a device, or by other terms used in the art. The remote unit 102 may communicate directly with one or more of the network units 104 via UL communication signals. In particular embodiments, the remote unit 102 may communicate directly with other remote units 102 via sidelink communication.

[0031] The network units 104 may be distributed across a geographic region. In a particular embodiment, the network units 104 may be an access point, an access terminal, a base, a base station, a location server, a core network ("CN"), a radio network entity, a Node B, an evolved Node B ("eNB"), a 5G Node B ("gNB"), a home Node B, a relay node, a device, a core network, an over-the-air server, a radio access node, an access point ("AP"), a new radio ("NR"), a network entity, an access and mobility management function ("AMF"), a unified data management ("UDM"), a unified data repository ("UDM"). The network unit 104 may also be referred to as and / or may include one or more of: Data Registry ("UDR"), UDM / UDR, Policy Control Function ("PCF"), Radio Access Network ("RAN"), Network Slice Selection Function ("NSSF"), Operations, Administration, and Management ("OAM"), Session Management Function ("SMF"), User Plane Function ("UPF"), Application Function, Authentication Server Function ("AUSF"), Security Anchor Function ("SEAF"), Trusted Non-3GPP Gateway Function ("TNGF"), Unmanned Aircraft System Network Function ("UAS NF"), Network Publication Function ("NEF"), UAS Service Supplier ("USS"), Unmanned Aircraft System Traffic Management ("UTM"), or any other terminology used in the art. The network unit 104 is generally part of a radio access network that includes one or more controllers communicatively coupled to one or more corresponding network units 104. The radio access network is typically communicatively coupled to one or more core networks, which may be coupled to other networks such as the Internet and the public switched telephone network, among other networks. These and other elements of the radio access network and core network are not shown but are generally well known to those skilled in the art.

[0032] In one implementation, the wireless communication system 100 conforms to the NR protocol standardized in the 3rd Generation Partnership Project (“3GPP®”), with the network unit 104 transmitting on the downlink (“DL”) using an OFDM modulation scheme and the remote unit 102 transmitting on the uplink (“UL”) using a single-carrier frequency division multiple access (“SC-FDMA”) scheme or an orthogonal frequency division multiplexing (“OFDM”) scheme. More generally, however, the wireless communication system 100 may implement any other open or proprietary communication protocol, such as WiMAX, Institute of Electrical and Electronics Engineers ("IEEE") 802.11 variants, Global System for Mobile Communications ("GSM"), General Packet Radio Service ("GPRS"), Universal Mobile Telecommunications System ("UMTS"), Long Term Evolution ("LTE") variants, Code Division Multiple Access 2000 ("CDMA2000"), Bluetooth, ZigBee, Sigfox, among others. This disclosure is not limited to any particular wireless communication system architecture or protocol implementation.

[0033] The network unit 104 may serve several remote units 102 within a serving area, e.g., a cell or a cell sector, via a wireless communication link. The network unit 104 transmits DL communication signals to serve the remote units 102 in the time domain, the frequency domain, and / or the spatial domain.

[0034] In various embodiments, the network unit 104 may send a request message to the unmanned aircraft system network function, the network publishing function, or a combination thereof, where the request message includes an air vehicle identifier, a public subscription identifier, and security policy information. In some embodiments, the network unit 104 may receive a response message from the unmanned aircraft system network function, the network publishing function, or a combination thereof, where the response message includes the air vehicle identifier, the public subscription identifier, an air vehicle authentication result, an authorization result, or a combination thereof, and aircraft system security requirement information. In particular embodiments, the network unit 104 may store the aircraft system security requirement information along with the air vehicle identifier, the public subscription identifier, and the air vehicle authentication result. Thus, the network unit 104 may be used to communicate and store aircraft system security information.

[0035] In certain embodiments, the network unit 104 may receive a first request message from an access and mobility management function at an unmanned aircraft system network function, a network publishing function, or a combination thereof, where the first request message includes an air vehicle identifier, a public subscription identifier, and security policy information. In some embodiments, the network unit 104 may send a second request message to an unmanned aircraft system service supplier, an unmanned aircraft system traffic management function, or a combination thereof, where the second request message includes the air vehicle identifier, the public subscription identifier, and security policy information. In certain embodiments, the network unit 104 may receive a second response message from the unmanned aircraft system service supplier, the unmanned aircraft system traffic management function, or a combination thereof, where the second response message includes the air vehicle identifier, the public subscription identifier, the air vehicle authentication result, and aircraft system security requirement information. In various embodiments, the network unit 104 may send a first response message to the access and mobility management function, where the first response message includes the air vehicle identifier, the public subscription identifier, the air vehicle authentication result, and the aircraft system security requirement information. In some embodiments, the network unit 104 may store the aircraft system security requirement information together with the air vehicle identifier, the public subscription identifier, and the air vehicle authentication result. Thus, the network unit 104 may be used to communicate and store the aircraft system security information.

[0036] In some embodiments, the network unit 104 may send a third request message to the unmanned aircraft system network function, the network publishing function, or a combination thereof, where the third request message includes the air vehicle identifier, the public subscription identifier, and the data request indication. In some embodiments, the network unit 104 may receive a third response message from the unmanned aircraft system network function, the network publishing function, or a combination thereof, where the third response message includes the air vehicle identifier, the public subscription identifier, the air vehicle authentication result, and the aircraft system security requirement information. In particular embodiments, the network unit 104 may determine to establish a protocol data unit session and skip the air vehicle authentication in response to receiving the air vehicle authentication result. In various embodiments, the network unit 104 may store the aircraft system security requirement information together with the air vehicle identifier, the public subscription identifier, the air vehicle authentication result, and the aircraft system security requirement information. In some embodiments, the network unit 104 may apply user plane security based on the aircraft system security requirement information. Thus, the network unit 104 may be used to communicate and store aircraft system security information.

[0037] In various embodiments, the network unit 104 may receive a request message from an unmanned aircraft system network function, a network publishing function, or a combination thereof at an unmanned aircraft system service supplier, an unmanned aircraft system traffic management function, or a combination thereof, where the request message includes an air vehicle identifier, a public subscription identifier, and security policy information. In some embodiments, the network unit 104 may send a response message to the unmanned aircraft system network function, the network publishing function, or a combination thereof, where the response message includes the air vehicle identifier, the public subscription identifier, the air vehicle authentication result, and the aircraft system security requirement information. In particular embodiments, the network unit 104 may store the aircraft system security requirement information along with the air vehicle identifier, the public subscription identifier, and the air vehicle authentication result. Thus, the network unit 104 may be used to communicate and store aircraft system security information.

[0038] 2 illustrates one embodiment of an apparatus 200 that may be used to communicate and store aircraft system security information. The apparatus 200 includes one embodiment of the remote unit 102. Furthermore, the remote unit 102 may include a processor 202, a memory 204, an input device 206, a display 208, a transmitter 210, and a receiver 212. In some embodiments, the input device 206 and the display 208 are combined into a single device, such as a touchscreen. In certain embodiments, the remote unit 102 may not include any input device 206 and / or display 208. In various embodiments, the remote unit 102 may include one or more of the processor 202, the memory 204, the transmitter 210, and the receiver 212, and may not include the input device 206 and / or the display 208.

[0039] The processor 202, in one embodiment, may include any known controller capable of executing computer-readable instructions and / or performing logical operations. For example, the processor 202 may be a microcontroller, microprocessor, central processing unit (“CPU”), graphics processing unit (“GPU”), auxiliary processing unit, field programmable gate array (“FPGA”), or similar programmable controller. In some embodiments, the processor 202 executes instructions stored in the memory 204 to implement the methods and routines described herein. The processor 202 is communicatively coupled to the memory 204, the input device 206, the display 208, the transmitter 210, and the receiver 212.

[0040] Memory 204, in one embodiment, is a computer-readable storage medium. In some embodiments, memory 204 includes a volatile computer storage medium. For example, memory 204 may include RAM, including dynamic RAM (“DRAM”), synchronous dynamic RAM (“SDRAM”), and / or static RAM (“SRAM”). In some embodiments, memory 204 includes a non-volatile computer storage medium. For example, memory 204 may include a hard disk drive, flash memory, or any other suitable non-volatile computer storage device. In some embodiments, memory 204 includes both volatile and non-volatile computer storage media. In some embodiments, memory 204 also stores program code and associated data, such as an operating system or other controller algorithms running on remote unit 102.

[0041] Input device 206, in one embodiment, may include any known computer input device, including a touch panel, buttons, a keyboard, a stylus, or a microphone. In some embodiments, input device 206 may be integrated with display 208, for example, as a touch screen or similar touch-sensitive display. In some embodiments, input device 206 includes a touch screen such that text may be entered using a virtual keyboard displayed on the touch screen and / or by handwriting on the touch screen. In some embodiments, input device 206 includes two or more different devices, such as a keyboard and a touch panel.

[0042] Display 208, in one embodiment, may include any known electronically controllable display or display device. Display 208 may be designed to output visual, audible, and / or tactile signals. In some embodiments, display 208 includes an electronic display capable of outputting visual data to a user. For example, display 208 may include, but is not limited to, a liquid crystal display ("LCD"), a light-emitting diode ("LED") display, an organic light-emitting diode ("OLED") display, a projector, or similar display device capable of outputting images, text, or the like to a user. As another non-limiting example, display 208 may include a wearable display, such as a smartwatch, smart glasses, or a head-up display. Furthermore, display 208 may be a component of a smartphone, a personal digital assistant, a television, a tablet computer, a notebook (laptop) computer, a personal computer, a vehicle dashboard, or the like.

[0043] In particular embodiments, display 208 includes one or more speakers for generating sound. For example, display 208 may generate audible alerts or notifications (e.g., beeps or chimes). In some embodiments, display 208 includes one or more haptic devices for generating vibration, movement, or other haptic feedback. In some embodiments, all or a portion of display 208 may be integrated with input device 206. For example, input device 206 and display 208 may form a touchscreen or similar touch-sensitive display. In other embodiments, display 208 may be located near input device 206.

[0044] Although only one transmitter 210 and one receiver 212 are shown, the remote unit 102 may have any suitable number of transmitters 210 and receivers 212. The transmitter 210 and receiver 212 may be any suitable type of transmitter and receiver. In one embodiment, the transmitter 210 and receiver 212 may be part of a transceiver.

[0045] 3 illustrates one embodiment of an apparatus 300 that may be used to communicate and store aircraft system security information. The apparatus 300 includes one embodiment of the network unit 104. Further, the network unit 104 may include a processor 302, a memory 304, an input device 306, a display 308, a transmitter 310, and a receiver 312. As can be appreciated, the processor 302, the memory 304, the input device 306, the display 308, the transmitter 310, and the receiver 312 may be substantially similar to the processor 202, the memory 204, the input device 206, the display 208, the transmitter 210, and the receiver 212 of the remote unit 102, respectively.

[0046] In particular embodiments, transmitter 310 sends a request message to the unmanned aircraft system network function, the network publishing function, or a combination thereof, where the request message includes the air vehicle identifier, the public subscription identifier, and the security policy information. In various embodiments, receiver 312 receives a response message from the unmanned aircraft system network function, the network publishing function, or a combination thereof, where the response message includes the air vehicle identifier, the public subscription identifier, the air vehicle authentication result, the authorization result, or a combination thereof, and the aircraft system security requirement information. In particular embodiments, processor 302 stores the aircraft system security requirement information along with the air vehicle identifier, the public subscription identifier, and the air vehicle authentication result.

[0047] In some embodiments, the receiver 312 receives a first request message from the access and mobility management function, the first request message including the air vehicle identifier, the public subscription identifier, and the security policy information. In various embodiments, the transmitter 310 transmits a second request message to the unmanned aircraft system service supplier, the unmanned aircraft system traffic management function, or a combination thereof, the second request message including the air vehicle identifier, the public subscription identifier, and the security policy information. In particular embodiments, the apparatus includes a processor 302. The receiver 312 receives a second response message from the unmanned aircraft system service supplier, the unmanned aircraft system traffic management function, or a combination thereof, the second response message including the air vehicle identifier, the public subscription identifier, the air vehicle authentication result, and the aircraft system security requirement information; the transmitter 310 sends a first response message to the access and mobility management function, the first response message comprising the air vehicle identifier, the public subscription identifier, the air vehicle authentication result, and the aircraft system security requirement information; and the processor 302 stores the aircraft system security requirement information together with the air vehicle identifier, the public subscription identifier, and the air vehicle authentication result.

[0048] In various embodiments, transmitter 310 sends a third request message to the unmanned aircraft system network function, the network publishing function, or a combination thereof, where the third request message includes the air vehicle identifier, the public subscription identifier, and the data request indication. In various embodiments, receiver 312 receives a third response message from the unmanned aircraft system network function, the network publishing function, or a combination thereof, where the third response message includes the air vehicle identifier, the public subscription identifier, the air vehicle authentication result, and the aircraft system security requirement information. In particular embodiments, processor 302, in response to receiving the air vehicle authentication result, determines to establish a protocol data unit session, skips air vehicle authentication, stores the aircraft system security requirement information together with the air vehicle identifier, the public subscription identifier, the air vehicle authentication result, and the aircraft system security requirement information, and applies user plane security based on the aircraft system security requirement information.

[0049] In particular embodiments, receiver 312 receives a request message from the unmanned aircraft system network function, the network publishing function, or a combination thereof, where the request message includes the air vehicle identifier, the public subscription identifier, and the security policy information. In various embodiments, transmitter 310 sends a response message to the unmanned aircraft system network function, the network publishing function, or a combination thereof, where the response message includes the air vehicle identifier, the public subscription identifier, the air vehicle authentication result, and the aircraft system security requirement information. In particular embodiments, processor 302 stores the aircraft system security requirement information along with the air vehicle identifier, the public subscription identifier, and the air vehicle authentication result.

[0050] In certain embodiments, unmanned aircraft system ("UAS") service supplier ("USS") unmanned aerial vehicle ("UAV") authorization and / or authentication ("UUAA") may be performed on the UAV during its registration with a fifth-generation ("5G") system or during a protocol data unit ("PDU") session establishment and / or modification procedure related to UAS services. If UUAA is performed on the UAV during registration, it may not be required to perform UUAA during a subsequent PDU session establishment procedure. In such embodiments, it may not be clear how a session management function ("SMF") involved in a PDU session establishment procedure would know whether UUAA has been performed on the UAV, thus leading to various problems.

[0051] In some embodiments, the SMF may invoke additional UUAAs for the UAV during the PDU session establishment procedure (e.g., without knowledge of a previous successful UUAA), resulting in delayed UAS session setup and unnecessary overhead (e.g., inefficient resource utilization).

[0052] In various embodiments, the system may coordinate UUAA results and UUAA information (e.g., UAS and / or command and control ("C2") user plane security requirement information) between a 3GPP® Network Function ("NF") (e.g., AMF or UAS NF and / or Network Publishing Function ("NEF")) and an SMF during PDU session establishment and / or modification procedures to enable the SMF to know whether UUAA has already been successfully performed for the UAV during a recent registration procedure.

[0053] In a first embodiment, there may be service-based user plane security enforcement in a 3GPP® 5G system (“5GS”) during UUAA. In a first embodiment, an NF in a 3GPP® system may receive user plane security requirement information from a USS and / or unmanned aircraft system traffic management (“UTM”) following successful UUAA or UAV and / or UAV controller (“UAV-C”) pairing authorization.

[0054] 4 is a schematic block diagram illustrating one embodiment of a system 400 for user plane security requirement retrieval from a USS and / or UTM. System 400 includes a user equipment (“UE”) 402, an AMF 404, an SMF 406, a UAS 408 (e.g., a UAS NF and / or NEF), and a USS 410 (e.g., a USS and / or UTM). It should be noted that each communication in system 400 may include one or more messages.

[0055] In certain embodiments, the UE 402 requests the services of any UAS 408 by transmitting to the AMF 404 (e.g., with its UAV identifier (“ID”)). The AMF 404 determines to trigger UUAA based on local policy and / or the AMF 404 determines to trigger UUAA following a request from the USS 410.

[0056] AMF 404 calls UUAA (412).

[0057] In a first communication 414, the AMF 404 sends an authentication request (e.g., Nnef_Authentication_request) to the UAS 408, including the UAV ID (e.g., a civil aviation administration (“CAA”)-level UAV ID) and an external identifier (e.g., a general public subscription identifier (“GPSI”)). In particular embodiments, the authentication request includes UAS session security information (e.g., security policy information). Note that the UAS session security information may be referred to as a user plane security policy, a UAS security policy, and / or an external UAS security policy. The UAS session security information and / or the UAS security policy may also include policies specific to user plane confidentiality and user plane integrity protection.

[0058] In the second communication 416, the UAS 408 may send an authentication request (e.g., Naf_Authentication_request) including the UAV ID (e.g., CAA-level UAV ID) and an external identifier (e.g., GPSI) to the USS 410. In some embodiments, the authentication request may also include UAS session security information.

[0059] In various embodiments, AMF 404 may set the session security information as "supported" based on any of the following conditions: 1) if the aviation subscription user plane security policy fetched from the UDM is "required"; and / or 2) if the user plane security policy fetched from the UDM is "required."

[0060] In certain embodiments, AMF 404 may set the session security information as "not supported, not preferred, and / or not required" based on any of the following conditions: 1) if there is no aviation subscription, and / or 2) if the user plane security policy fetched from the UDM is "not required and / or not preferred."

[0061] In a third communication 418, the USS 410 may send to the UAS 408 an authentication response (eg, Naf_Authentication_response) that includes an external identifier (eg, GPSI) and an authentication and / or authorization message.

[0062] In an optional fourth communication 420, multiple round-trip messages may be performed as required by the authentication method used by the USS 410. The authentication and / or authentication response message from the USS 410 may include the GPSI and may include an authentication message based on the authentication method used that is forwarded transparently to the UE 402 via a transport message (e.g., a mobility management message).

[0063] In a fifth communication 422, following successful authentication and / or authorization, the USS 410 may send to the UAS 408 an authentication response (e.g., Naf_Authentication_response) including the external identifier (e.g., GPSI), the CAA-level UAV ID, the result, and UAS security requirement information (e.g., which may be user plane security requirement information).

[0064] In some embodiments, the USS 410 sets the UAS security requirements information as "required" based on at least one of the following conditions: 1) if the session security information that the USS 410 received from the UAS 408 in step 416 is "supported," and / or 2) if the USS 410 determines not to apply end-to-end security to the session and / or user plane data. In various embodiments, a cause value may be sent from the USS 410 indicating that end-to-end security is not applicable and / or not supported.

[0065] In certain embodiments, the USS 410 sets the UAS security requirements information as "not required" based on at least one of the following conditions: 1) if the session security information received by the USS 410 from the UAS 408 in step 416 is "not necessary and / or not preferred," 2) if the USS 410 does not receive UAS session security information in step 416, and / or 3) if the USS 410 determines to apply end-to-end security to the session and / or user plane data. In some embodiments, a cause value may be sent from the USS 410 indicating that end-to-end security is applicable and / or supported.

[0066] In some embodiments, if the USS 410 receives the session security information from the UAS 408 as "supported" in step 416, the USS 410 may decide to skip end-to-end security and may set the UAS session security requirements information as "required" and set the cause value as end-to-end security not applicable and / or not supported.

[0067] In various embodiments, if the USS 410 receives the session security information from the UAS 408 in step 416 as "not supported, not preferred, and / or not required," the USS 410 may decide to implement end-to-end security and may set the UAS session security requirements information as "not required" and set the cause value as end-to-end security is applicable and / or supported.

[0068] The UAS 408 may store (424) the received UAS security requirement information (e.g., it may be user plane security requirement information) along with the external identifier (e.g., GPSI), CAA-level UAV ID, and / or the result.

[0069] In a sixth communication 426, the UAS 408 may send an authentication response message to the AMF 404 including UAS security requirement information (e.g., which may be user plane security requirement information) along with an external identifier (e.g., GPSI), a CAA-level UAV ID, and / or a result.

[0070] The AMF 404 may store (428) the received UAS security requirement information (e.g., it may be user plane security requirement information) along with the external identifier (e.g., GPSI), CAA-level UAV ID, and / or the result.

[0071] In a seventh communication 430 and / or an optional eighth communication 432, the AMF 404 may provide the authentication result and CAA-level UAV ID to the UE 402 in a non-access stratum ("NAS") message (e.g., a mobility management message or any UE configuration update message).

[0072] In a second embodiment, there may be UUAA status coordination in 3GPP 5GS. In the second embodiment, UUAA may be performed on a UAV during its registration to the 5G system or during a PDU session establishment and / or modification procedure. If UUAA is performed on a UAV during registration, it is not required to perform UUAA during a subsequent PDU session establishment procedure. In some embodiments, an SMF involved in PDU session establishment may not have a means to know whether UUAA has previously been successfully performed on the corresponding UAV. The second embodiment includes information on how the SMF is notified of a successful UUAA result during a subsequent PDU session establishment procedure if UUAA has previously been successfully performed during registration.

[0073] 5 is a schematic block diagram illustrating one embodiment of a system 500 for providing UUAA results and UAS security requirement information to an SMF. System 500 includes a UE 502, an AMF 504, an SMF 506, a UAS 508 (e.g., a UAS NF and / or NEF), and a USS 510 (e.g., a USS and / or UTM). Note that each communication in system 500 may include one or more messages.

[0074] Figure 5 includes three options for providing the UUAA result and UUAA information (e.g., UAS and / or C2 user plane security requirement information, etc.) to the SMF 506 to enable the SMF to continue the PDU session establishment procedure without an additional UUAA.

[0075] In the first communication 512, a successful UUAA is performed on the UAV during the 5GS registration procedure, and the NF (e.g., AMF 504, UAS 508) in the 3GPP network stores the UUAA result (e.g., along with the UAV ID) and the UAS security requirement information (or user plane security requirement information) either in local storage or in an unstructured data storage function ("UDSF") and / or UDM. Note that the storage of the UAS security requirement information may be the same as that described in the first embodiment. The UAS security requirement information may indicate whether user plane security (or UAS session and / or C2 session security) needs to be applied by 5GS.

[0076] The UAS security requirements information may include the following information: 1) 3GPP® user plane security is indicated as "required" and the cause value may indicate that end-to-end security is not applicable and / or not supported as enforced by USS510; or 2) 3GPP® user plane security is indicated as "not required" and the cause value may indicate that end-to-end security is applicable and / or supported as enforced by USS510.

[0077] The first option includes steps 514, 516, 518, 520, 536, and 538.

[0078] Specifically, in the second communication 514, the UE 502 sends a PDU session establishment request to the AMF 504 in a NAS message that includes a service level device identity (e.g., a CAA-level UAV ID for the UAV) and, optionally, authentication data (e.g., a UUAA aeronautical payload).

[0079] If the AMF 504 finds a UE context with UUAA information, such as a locally stored UUAA result and UAS security requirement information, based on the received CAA-level UAV ID, the AMF 504 decides to provide the UUAA information to the SMF 506 (516). The AMF 504 selects the SMF 506 and sends an Nsmf_PDUSession_CreateSMContext request message to the SMF 506 in a third communication 518, along with the PDU session establishment request, the UUAA result (e.g., with an indication of success), and / or the UAS security requirement information. In a particular embodiment, the AMF 504 may send an Nsmf_PDUSession_UpdateSMContext request message to the SMF 506, which may include the UUAA result (e.g., with an indication of success) and / or the UAS security requirement information.

[0080] Upon receiving the CAA-level UAV ID along with the UUAA result (e.g., with an indication of success) and / or the UAS security requirement information, the SMF 506 determines (520) to continue the PDU session establishment procedure without performing any additional UUAA with the USS 510, since the UUAA result (e.g., with an indication of success) and / or the UAS security requirement information from the registration procedure are available for the SMF 506 to continue the PDU session establishment related to the UAS service.

[0081] In the first option, steps 522 to 534 may be skipped. In an eighth communication 536, the SMF 506 continues the PDU session establishment and / or modification procedure. In a ninth communication 538, if the UUAA result is not provided by the AMF 504, the SMF 506 triggers to perform UUAA with the USS 510 for the PDU session establishment and / or modification procedure.

[0082] The second option includes steps 514, 518, 522, 524, 526, 534, 536, and 538, and thus steps 516, 520, and 528-532 are skipped.

[0083] In the second communication 514, the UE 502 sends a PDU session establishment request to the AMF 504 in a NAS message that includes a service level device identity (e.g., a CAA-level UAV ID for the UAV) and, optionally, authentication data (e.g., a UUAA aeronautical payload).

[0084] In a third communication 518, the AMF 504 selects the SMF 506 and sends an Nsmf_PDUSession_CreateSMContext request message to the SMF 506 with a PDU session establishment request.

[0085] In a fourth communication 522, the SMF 506 determines to check for a CAA-level UAV ID and / or an external identifier (e.g., GPSI) if any UUAA results exist from a recent UUAA. Further, the SMF 506 sends a data request message (e.g., Nnef_Auth_Data Request or Nnef_UUAA_Data Request) to the UAS 508, including the CAA-level UAV ID and / or an external identifier (e.g., GPSI).

[0086] If the UAS 508 finds a UE context that has UUAA information, such as locally stored UUAA results and UAS security requirement information, based on the received CAA-level UAV ID, the UAS 508 decides to provide the UUAA information to the SMF 506 (524).

[0087] In a fifth communication 526, the UAS 508 sends a data response message (e.g., Nnef_Auth_Data Response or Nnef_UUAA_Data Response) to the SMF 506 that includes the CAA-level UAV ID and / or external identifier (e.g., GPSI), the UUAA result (e.g., with an indication of success), and / or UAS security requirements information. In some embodiments, if the UUAA result is not available, the UAS 508 sends a data response message (e.g., Nnef_Auth_Data Response or Nnef_UUAA_Data Response) to the SMF 506 that includes the CAA-level UAV ID and / or external identifier (e.g., GPSI), and / or an indication of data unavailability.

[0088] Upon receiving the CAA-level UAV ID along with the UUAA result (e.g., with an indication of success) and / or the UAS security requirement information, the SMF 506 determines (534) to continue the PDU session establishment procedure without performing any additional UUAA with the USS 510, since the UUAA result (e.g., with an indication of success) and the UAS security requirement information from the registration procedure are available for the SMF 506 to continue the PDU session establishment related to the UAS service.

[0089] In an eighth communication 536, the SMF 506 continues the PDU session establishment and / or modification procedures. In various embodiments, if a UUAA result is not provided, a data unavailable indication may be provided by the UAS 508, which then triggers the SMF 506 in an optional ninth communication 538 to perform UUAA with the USS 510 for the PDU session establishment and / or modification procedures.

[0090] The third option includes steps 514, 518, 528, 530, 532, 534, 536, and 538, and thus steps 516 and 520-526 are skipped.

[0091] In the second communication 514, the UE 502 sends a PDU session establishment request to the AMF 504 in a NAS message that includes a service level device identity (e.g., a CAA-level UAV ID for the UAV) and, optionally, authentication data (e.g., a UUAA aeronautical payload).

[0092] In a third communication 518, the AMF 504 selects the SMF 506 and sends an Nsmf_PDUSession_CreateSMContext request message to the SMF 506 with a PDU session establishment request.

[0093] In a sixth communication 528, the SMF 506 decides to invoke the UUAA and sends an authentication request message (e.g., Nnef_Auth_Request) to the UAS 508, including the CAA-level UAV ID and an external identifier (e.g., GPSI).

[0094] If the UAS 508 finds a UE context that has UUAA information, such as locally stored UUAA results and UAS security requirement information, based on the received CAA-level UAV ID, the UAS 508 decides to provide the UUAA information to the SMF 506 (530).

[0095] In a seventh communication 532, the UAS 508 sends to the SMF 506 an authentication response message (e.g., Nnef_Auth_Response) including the CAA-level UAV ID and / or external identifier (e.g., GPSI), the UUAA result (e.g., with an indication of success), and / or UAS security requirement information.

[0096] Upon receiving the CAA-level UAV ID and / or external identifier (e.g., GPSI) along with the UUAA result (e.g., with an indication of success) and / or UAS security requirement information, the SMF 506 determines (534) to continue the PDU session establishment procedure without performing any additional UUAA with the USS 510, since the UUAA result (e.g., with an indication of success) and / or UAS security requirement information from the registration procedure are available for the SMF 506 to continue the PDU session establishment related to the UAS service.

[0097] In an eighth communication 536, the SMF 506 continues the PDU session establishment and / or modification procedures. In various embodiments, if a UUAA result is not provided, a data unavailable indication may be provided by the UAS 508, which then triggers the SMF 506 in an optional ninth communication 538 to perform UUAA with the USS 510 for the PDU session establishment and / or modification procedures.

[0098] 6 is a flow chart diagram illustrating one embodiment of a method 600 for communicating and storing aircraft system security information. In some embodiments, the method 600 is performed by a device such as the network unit 104. In particular embodiments, the method 600 may be performed by a processor executing program code, such as a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, or an FPGA.

[0099] In various embodiments, method 600 includes sending 602 a request message to an unmanned aircraft system network function, a network publishing function, or a combination thereof, where the request message includes an air vehicle identifier, a public subscription identifier, and security policy information. In some embodiments, method 600 includes receiving 604 a response message from the unmanned aircraft system network function, a network publishing function, or a combination thereof, where the response message includes the air vehicle identifier, the public subscription identifier, air vehicle authentication results, authorization results, or a combination thereof, and aircraft system security requirement information. In certain embodiments, method 600 includes storing 606 the aircraft system security requirement information with the air vehicle identifier, the public subscription identifier, and the air vehicle authentication results.

[0100] In certain embodiments, method 600 further comprises setting the security policy information to supported, enabled, or a combination thereof in response to an air subscription user plane security policy fetched from a management function (i.e., a unified data management function (UDM)) being required, in response to a user plane security policy fetched from a management function (i.e., a unified data management function (UDM)) being required, or a combination thereof.

[0101] In some embodiments, the method 600 further comprises setting the security policy information to not supported, not enabled, not preferred, not required, or a combination thereof in response to there being no aviation subscription available for the air vehicle corresponding to the air vehicle identifier, in response to the user plane security policy fetched from the management function (i.e., the unified data management function (UDM)) being preferred, not required, or a combination thereof.

[0102] In various embodiments, method 600 further comprises, in response to receiving a protocol data unit session establishment request with the air vehicle identifier from the user equipment, providing an air vehicle authentication result and aircraft system security requirement information during the protocol data unit session establishment procedure together with the air vehicle identifier to the session management function.

[0103] 7 is a flow chart diagram illustrating another embodiment of a method 700 for communicating and storing aircraft system security information. In some embodiments, the method 700 is performed by a device such as the network unit 104. In particular embodiments, the method 700 may be performed by a processor executing program code, such as a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, or an FPGA.

[0104] In various embodiments, method 700 includes receiving 702 a first request message from an access and mobility management function, the first request message including an air vehicle identifier, a public subscription identifier, and security policy information. In some embodiments, method 700 includes sending 704 a second request message to an unmanned aircraft system service supplier, an unmanned aircraft system traffic management function, or a combination thereof, the second request message including the air vehicle identifier, the public subscription identifier, and security policy information. In particular embodiments, method 700 includes receiving 706 a second response message from the unmanned aircraft system service supplier, an unmanned aircraft system traffic management function, or a combination thereof, the second response message including the air vehicle identifier, the public subscription identifier, the air vehicle authentication result, and aircraft system security requirement information. In various embodiments, method 700 includes sending 708 a first response message to the access and mobility management function, where the first response message includes the air vehicle identifier, the public subscription identifier, the air vehicle authentication result, and the aircraft system security requirement information. In some embodiments, method 700 includes storing 710 the aircraft system security requirement information with the air vehicle identifier, the public subscription identifier, and the air vehicle authentication result.

[0105] In certain embodiments, method 700 further comprises providing, in response to receiving an authentication request from the session management function, an air vehicle authentication result and aircraft system security requirement information, along with an air vehicle identifier, to the session management function during the protocol data unit session establishment procedure.

[0106] 8 is a flowchart diagram illustrating a further embodiment of a method 800 for communicating and storing aircraft system security information. In some embodiments, the method 800 is performed by an apparatus such as the network unit 104. In particular embodiments, the method 800 may be performed by a processor executing program code, such as a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, or an FPGA.

[0107] In various embodiments, method 800 includes step 802 of sending a third request message to the unmanned aircraft system network function, the network publishing function, or a combination thereof, where the third request message includes an air vehicle identifier, a public subscription identifier, and a data request indication. In some embodiments, method 800 includes step 804 of receiving a third response message from the unmanned aircraft system network function, the network publishing function, or a combination thereof, where the third response message includes the air vehicle identifier, the public subscription identifier, the air vehicle authentication result, and the aircraft system security requirement information. In particular embodiments, method 800 includes step 806 of determining to establish a protocol data unit session and skipping air vehicle authentication in response to receiving the air vehicle authentication result. In various embodiments, method 800 includes step 808 of storing the aircraft system security requirement information with the air vehicle identifier, the public subscription identifier, the air vehicle authentication result, and the aircraft system security requirement information. In some embodiments, the method 800 includes applying 810 user plane security based on the aircraft system security requirement information.

[0108] In certain embodiments, method 800 further comprises receiving a third response message without sending the third request message in response to the unmanned aircraft system network function, the network publishing function, or a combination thereof comprising an access and mobility management function. In some embodiments, method 800 further comprises receiving a third response message in response to the unmanned aircraft system network function, the network publishing function, or a combination thereof comprising an access and mobility management system, wherein the access and mobility management function receives a protocol data unit session establishment request having an air vehicle identifier, and the access and mobility management system has the air vehicle identifier with an air vehicle authentication result and aircraft system security requirement information.

[0109] In various embodiments, the third request message is an authentication data request or an authentication request message. In one embodiment, the third response message is an authentication data response or an authentication response message. In a particular embodiment, the third response message comprises an indication that data is unavailable. In some embodiments, method 800 further comprises determining to invoke air vehicle authentication if an indication that data is unavailable is received or if the air vehicle authentication result and security requirement information are not received from the network function.

[0110] 9 is a flow chart diagram illustrating yet another embodiment of a method 900 for communicating and storing aircraft system security information. In some embodiments, the method 900 is performed by an apparatus such as the network unit 104. In particular embodiments, the method 900 may be performed by a processor executing program code, such as a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, or an FPGA.

[0111] In various embodiments, method 900 includes receiving 902 a request message from an unmanned aircraft system network function, a network publishing function, or a combination thereof at an unmanned aircraft system service supplier, an unmanned aircraft system traffic management function, or a combination thereof, where the request message includes an air vehicle identifier, a public subscription identifier, and security policy information. In some embodiments, method 900 includes sending 904 a response message to the unmanned aircraft system network function, the network publishing function, or a combination thereof, where the response message includes the air vehicle identifier, the public subscription identifier, an air vehicle authentication result, and aircraft system security requirement information. In particular embodiments, method 900 includes storing 906 the aircraft system security requirement information with the air vehicle identifier, the public subscription identifier, and the air vehicle authentication result.

[0112] In certain embodiments, method 900 further comprises setting the aircraft system security requirements information as required based on whether the security policy information received from the unmanned aircraft system network function, the network publishing function, or a combination thereof is supported, enabled, or a combination thereof, whether the unmanned aircraft system service supplier, the unmanned aircraft system traffic management function, or a combination thereof determines not to apply end-to-end security to the session data, the user plane data, or a combination thereof. In some embodiments, method 900 further comprises sending a cause value indicating that end-to-end security is not applicable, not supported, or a combination thereof.

[0113] In various embodiments, method 900 further comprises setting the aircraft system security requirements information as not required based on whether the security policy information received from the unmanned aircraft system network function, the network publishing function, or a combination thereof is not supported, not enabled, not required, not preferred, or a combination thereof, whether the unmanned aircraft system service supplier, the unmanned aircraft system traffic management function, or a combination thereof does not receive the security policy information during air vehicle certification and / or authorization, whether the unmanned aircraft system service supplier, the unmanned aircraft system traffic management function, or a combination thereof determines to apply end-to-end security to the session data, the user plane data, or a combination thereof, or some combination thereof.

[0114] In one embodiment, method 900 further comprises sending a cause value indicating end-to-end security is applicable, supported, or a combination thereof. In a particular embodiment, if the security policy information received from the unmanned aircraft system network function, the network publishing function, or a combination thereof is supported, enabled, or a combination thereof, the unmanned aircraft system service supplier, the unmanned aircraft system traffic management function, or a combination thereof determines to skip end-to-end security, sets the aircraft system security requirements information as required, and sets the cause value as end-to-end security is not applicable, not supported, or a combination thereof.

[0115] In some embodiments, if the security policy information received from the unmanned aircraft system network function, the network publishing function, or a combination thereof is not supported, not enabled, not required, not preferred, or a combination thereof, the unmanned aircraft system service supplier, the unmanned aircraft system traffic management function, or a combination thereof determines to activate end-to-end security, sets the aircraft system security requirements information as not required, and sets the cause value as end-to-end security is applicable, supported, or a combination thereof.

[0116] In one embodiment, a method of access and mobility management function includes sending a request message to an unmanned aircraft system network function, a network publishing function, or a combination thereof, wherein the request message comprises an air vehicle identifier, a public subscription identifier, and security policy information; receiving a response message from the unmanned aircraft system network function, the network publishing function, or a combination thereof, wherein the response message comprises the air vehicle identifier, the public subscription identifier, an air vehicle authentication result, an authorization result, or a combination thereof, and aircraft system security requirement information; and storing the aircraft system security requirement information together with the air vehicle identifier, the public subscription identifier, and the air vehicle authentication result.

[0117] In certain embodiments, the method further comprises setting the security policy information to supported, enabled, or a combination thereof in response to an aviation subscription user plane security policy fetched from a management function (i.e., Unified Data Management Function (UDM)) being required, in response to a user plane security policy fetched from a management function (i.e., Unified Data Management Function (UDM)) being required, or a combination thereof.

[0118] In some embodiments, the method further comprises setting the security policy information to not supported, not enabled, not preferred, not required, or a combination thereof in response to there being no aviation subscription available for the air vehicle corresponding to the air vehicle identifier, in response to the user plane security policy fetched from the management function (i.e., Unified Data Management Function (UDM)) being preferred, not required, or a combination thereof.

[0119] In various embodiments, the method further comprises, in response to receiving a protocol data unit session establishment request with the air vehicle identifier from the user equipment, providing an air vehicle authentication result and aircraft system security requirement information during the protocol data unit session establishment procedure together with the air vehicle identifier to the session management function.

[0120] In one embodiment, an apparatus includes an access and mobility management function. The apparatus further includes: a transmitter that sends a request message to the unmanned aircraft system network function, a network publishing function, or a combination thereof, the request message comprising an air vehicle identifier, a public subscription identifier, and security policy information; a receiver that receives a response message from the unmanned aircraft system network function, the network publishing function, or a combination thereof, the response message comprising the air vehicle identifier, the public subscription identifier, an air vehicle authentication result, an authorization result, or a combination thereof, and aircraft system security requirement information; and a processor that stores the aircraft system security requirement information with the air vehicle identifier, the public subscription identifier, and the air vehicle authentication result.

[0121] In certain embodiments, the processor sets the security policy information to supported, enabled, or a combination thereof in response to an air subscription user plane security policy fetched from a management function (i.e., unified data management function (UDM)) being required, in response to a user plane security policy fetched from a management function being required, or a combination thereof.

[0122] In some embodiments, the processor sets the security policy information to not supported, not enabled, not preferred, not required, or a combination thereof in response to there being no aviation subscription available for the air vehicle corresponding to the air vehicle identifier, in response to the user plane security policy fetched from the management function (i.e., the unified data management function (UDM)) being preferred, not required, or a combination thereof.

[0123] In various embodiments, in response to receiving a protocol data unit session establishment request with an air vehicle identifier from the user equipment, the transmitter transmits the air vehicle authentication results and aircraft system security requirement information during the protocol data unit session establishment procedure along with the air vehicle identifier to the session management function.

[0124] In one embodiment, a method of an unmanned aircraft system network function, a network publication function, or a combination thereof, includes receiving a first request message from an access and mobility management function, the first request message comprising an air vehicle identifier, a public subscription identifier, and security policy information; sending a second request message to an unmanned aircraft system service supplier, an unmanned aircraft system traffic management function, or a combination thereof, the second request message comprising the air vehicle identifier, the public subscription identifier, and security policy information; and sending a second response message to the unmanned aircraft system service supplier, an unmanned aircraft system traffic management function, or a combination thereof. receiving a second response message from an access and mobility management function, an unmanned aircraft system traffic management function, or a combination thereof, wherein the second response message comprises the air vehicle identifier, the public subscription identifier, the air vehicle authentication result, and the aircraft system security requirement information; sending a first response message to the access and mobility management function, wherein the first response message comprises the air vehicle identifier, the public subscription identifier, the air vehicle authentication result, and the aircraft system security requirement information; and storing the aircraft system security requirement information together with the air vehicle identifier, the public subscription identifier, and the air vehicle authentication result.

[0125] In certain embodiments, the method further comprises providing, in response to receiving an authentication request from the session management function, an air vehicle authentication result and aircraft system security requirement information together with the air vehicle identifier to the session management function during the protocol data unit session establishment procedure.

[0126] In one embodiment, an apparatus comprises an unmanned aircraft system network function, a network publishing function, or a combination thereof. The apparatus further comprises: a receiver that receives a first request message from an access and mobility management function, the first request message comprising an air vehicle identifier, a public subscription identifier, and security policy information; a transmitter that sends a second request message to an unmanned aircraft system service supplier, an unmanned aircraft system traffic management function, or a combination thereof, the second request message comprising the air vehicle identifier, the public subscription identifier, and security policy information; and a processor, wherein the receiver sends a second response message to the unmanned aircraft system service supplier, the unmanned aircraft system traffic management function, or a combination thereof. and a transmitter receives a first response message from the access and mobility management function, the first response message comprising the air vehicle identifier, the public subscription identifier, the air vehicle authentication result, and the aircraft system security requirement information from the human-aircraft system traffic management function, or a combination thereof, the second response message comprising the air vehicle identifier, the public subscription identifier, the air vehicle authentication result, and the aircraft system security requirement information, and the processor stores the aircraft system security requirement information together with the air vehicle identifier, the public subscription identifier, and the air vehicle authentication result.

[0127] In certain embodiments, the transmitter, in response to receiving an authentication request from the session management function, transmits the air vehicle authentication result and the aircraft system security requirement information along with the air vehicle identifier during the protocol data unit session establishment procedure to the session management function.

[0128] In one embodiment, the session management function method includes sending a third request message to the unmanned aircraft system network function, the network publishing function, or a combination thereof, wherein the third request message comprises an air vehicle identifier, a public subscription identifier, and a data request indication; receiving a third response message from the unmanned aircraft system network function, the network publishing function, or a combination thereof, wherein the third response message comprises the air vehicle identifier, the public subscription identifier, the air vehicle authentication result, and aircraft system security requirement information; in response to receiving the air vehicle authentication result, determining to establish a protocol data unit session and skipping air vehicle authentication; storing the aircraft system security requirement information together with the air vehicle identifier, the public subscription identifier, the air vehicle authentication result, and the aircraft system security requirement information; and applying user plane security based on the aircraft system security requirement information.

[0129] In certain embodiments, the method further includes receiving a third response message without sending a third request message in response to the unmanned aircraft system network capability, the network publishing capability, or a combination thereof comprising the access and mobility management capability.

[0130] In some embodiments, the method further comprises receiving a third response message in response to the unmanned aircraft system network function, the network publishing function, or a combination thereof comprising an access and mobility management system, wherein the access and mobility management function receives a protocol data unit session establishment request having an air vehicle identifier, and the access and mobility management system has the air vehicle identifier with an air vehicle authentication result and the aircraft system security requirement information.

[0131] In various embodiments, the third request message is an authentication data request or an authentication request message.

[0132] In one embodiment, the third response message is an authentication data response or an authentication response message.

[0133] In certain embodiments, the third response message comprises an indication that data is not available.

[0134] In some embodiments, the method further comprises determining to invoke air vehicle authentication if an indication of data unavailability is received or if air vehicle authentication results and security requirement information are not received from the network function.

[0135] In one embodiment, the apparatus includes a session management function. The apparatus further includes: a transmitter that sends a third request message to the unmanned aircraft system network function, a network publishing function, or a combination thereof, the third request message comprising an air vehicle identifier, a public subscription identifier, and a data request indication; a receiver that receives a third response message from the unmanned aircraft system network function, the network publishing function, or a combination thereof, the third response message comprising the air vehicle identifier, the public subscription identifier, the air vehicle authentication result, and aircraft system security requirement information; and a processor that, in response to receiving the air vehicle authentication result, determines to establish a protocol data unit session and skips air vehicle authentication, stores the aircraft system security requirement information together with the air vehicle identifier, the public subscription identifier, the air vehicle authentication result, and the aircraft system security requirement information, and applies user plane security based on the aircraft system security requirement information.

[0136] In certain embodiments, the receiver receives a third response message without sending a third request message in response to the unmanned aircraft system network capability, the network publication capability, or a combination thereof comprising the access and mobility management capability.

[0137] In some embodiments, the receiver receives a third response message in response to the unmanned aircraft system network function, the network publishing function, or a combination thereof comprising an access and mobility management system, the access and mobility management function receiving a protocol data unit session establishment request having an air vehicle identifier, the access and mobility management system having the air vehicle identifier with an air vehicle authentication result and the aircraft system security requirement information.

[0138] In various embodiments, the third request message is an authentication data request or an authentication request message.

[0139] In one embodiment, the third response message is an authentication data response or an authentication response message.

[0140] In certain embodiments, the third response message comprises an indication that data is not available.

[0141] In some embodiments, the processor determines to invoke air vehicle authentication if an indication of data unavailability is received or if air vehicle authentication results and security requirement information are not received from the network function.

[0142] In one embodiment, a method of an unmanned aircraft system service supplier, an unmanned aircraft system traffic management function, or a combination thereof, includes receiving a request message from an unmanned aircraft system network function, a network publishing function, or a combination thereof, wherein the request message comprises an air vehicle identifier, a public subscription identifier, and security policy information; sending a response message to the unmanned aircraft system network function, the network publishing function, or a combination thereof, wherein the response message comprises the air vehicle identifier, the public subscription identifier, an air vehicle authentication result, and aircraft system security requirement information; and storing the aircraft system security requirement information together with the air vehicle identifier, the public subscription identifier, and the air vehicle authentication result.

[0143] In certain embodiments, the method further comprises setting the aircraft system security requirements information as required based on whether the security policy information received from the unmanned aircraft system network function, the network publishing function, or a combination thereof is supported, enabled, or a combination thereof, whether the unmanned aircraft system service supplier, the unmanned aircraft system traffic management function, or a combination thereof determines not to apply end-to-end security to the session data, the user plane data, or a combination thereof.

[0144] In some embodiments, the method further comprises sending a cause value indicating that end-to-end security is not applicable, not supported, or a combination thereof.

[0145] In various embodiments, the method further comprises setting the aircraft system security requirements information as not required based on whether the security policy information received from the unmanned aircraft system network function, the network publishing function, or a combination thereof is not supported, not enabled, not required, not preferred, or a combination thereof, whether the unmanned aircraft system service supplier, the unmanned aircraft system traffic management function, or a combination thereof does not receive the security policy information during air vehicle certification and / or authorization, whether the unmanned aircraft system service supplier, the unmanned aircraft system traffic management function, or a combination thereof determines to apply end-to-end security to the session data, the user plane data, or a combination thereof, or some combination thereof.

[0146] In one embodiment, the method further comprises sending a cause value indicating that end-to-end security is applicable, supported, or a combination thereof.

[0147] In certain embodiments, if the security policy information received from the unmanned aircraft system network function, the network publishing function, or a combination thereof is supported, enabled, or a combination thereof, the unmanned aircraft system service supplier, the unmanned aircraft system traffic management function, or a combination thereof determines to skip end-to-end security, sets the aircraft system security requirements information as required, and sets the cause value as end-to-end security is not applicable, not supported, or a combination thereof.

[0148] In some embodiments, if the security policy information received from the unmanned aircraft system network function, the network publishing function, or a combination thereof is not supported, not enabled, not required, not preferred, or a combination thereof, the unmanned aircraft system service supplier, the unmanned aircraft system traffic management function, or a combination thereof determines to activate end-to-end security, sets the aircraft system security requirements information as not required, and sets the cause value as end-to-end security is applicable, supported, or a combination thereof.

[0149] In one embodiment, the apparatus comprises an unmanned aircraft system service supplier, an unmanned aircraft system traffic management function, or a combination thereof. The apparatus further comprises: a receiver that receives a request message from the unmanned aircraft system network function, the network publishing function, or a combination thereof, the request message comprising an air vehicle identifier, a public subscription identifier, and security policy information; a transmitter that sends a response message to the unmanned aircraft system network function, the network publishing function, or a combination thereof, the response message comprising the air vehicle identifier, the public subscription identifier, the air vehicle authentication result, and aircraft system security requirement information; and a processor that stores the aircraft system security requirement information with the air vehicle identifier, the public subscription identifier, and the air vehicle authentication result.

[0150] In certain embodiments, the processor sets the aircraft system security requirements information as required based on whether the security policy information received from the unmanned aircraft system network function, the network publishing function, or a combination thereof is supported, enabled, or a combination thereof, whether the unmanned aircraft system service supplier, the unmanned aircraft system traffic management function, or a combination thereof determines not to apply end-to-end security to the session data, the user plane data, or a combination thereof.

[0151] In some embodiments, the transmitter transmits a cause value indicating that end-to-end security is not applicable, not supported, or a combination thereof.

[0152] In various embodiments, the processor sets the aircraft system security requirement information as not required based on whether the security policy information received from the unmanned aircraft system network function, the network publishing function, or a combination thereof is not supported, not enabled, not required, not preferred, or a combination thereof, whether the unmanned aircraft system service supplier, the unmanned aircraft system traffic management function, or a combination thereof does not receive the security policy information during air vehicle certification and / or authorization, whether the unmanned aircraft system service supplier, the unmanned aircraft system traffic management function, or a combination thereof determines to apply end-to-end security to session data, user plane data, or a combination thereof, or some combination thereof.

[0153] In one embodiment, the transmitter transmits a cause value indicating that end-to-end security is applicable, supported, or a combination thereof.

[0154] In certain embodiments, if the security policy information received from the unmanned aircraft system network function, the network publishing function, or a combination thereof is supported, enabled, or a combination thereof, the unmanned aircraft system service supplier, the unmanned aircraft system traffic management function, or a combination thereof determines to skip end-to-end security, sets the aircraft system security requirements information as required, and sets the cause value as end-to-end security is not applicable, not supported, or a combination thereof.

[0155] In some embodiments, if the security policy information received from the unmanned aircraft system network function, the network publishing function, or a combination thereof is not supported, not enabled, not required, not preferred, or a combination thereof, the unmanned aircraft system service supplier, the unmanned aircraft system traffic management function, or a combination thereof determines to activate end-to-end security, sets the aircraft system security requirements information as not required, and sets the cause value as end-to-end security is applicable, supported, or a combination thereof.

[0156] The embodiments may be embodied in other specific forms. The described embodiments are to be considered in all respects only as illustrative and not restrictive. The scope of the invention is therefore indicated by the appended claims rather than by the foregoing description. All changes that come within the meaning and range of equivalency of the claims are intended to be embraced within their scope. [Explanation of symbols]

[0157] 100 Wireless Communication System 102 Remote Unit 104 Network Unit 200 equipment 202 processors 204 memory 206 Input Devices 208 Display 210 Transmitter 212 receiver 300 equipment 302 processor 304 memory 306 Input Devices 308 Display 310 Transmitter 312 Receiver 400 System 402 User Equipment, UE 404 AMF 406 SMF 408 UAS 410 USS 414 First Communication 416 Second Communication 418 Third Communication 420 Fourth Communication 422 Fifth Communication 426 Sixth Communication 430 Seventh Communication 432 Eighth Communication 500 Systems 502UE 504 AMF 506 SMF 508 UAS 510 USS 512 First Communication 514 Second Communication 518 Third Communication 522 Fourth Communication 526 Fifth Communication 528 Sixth Communication 532 Seventh Communication 536 Eighth Communication 538 Ninth Communication 600 ways 700 methods 800 ways 900 ways

Claims

1. 1. A device with access and mobility management functionality, comprising:

1. A transmitter that transmits a request message to an unmanned aircraft system network function, a network publishing function, or a combination thereof, the request message comprising: an air vehicle identifier; a public subscription identifier; and Security policy information and a transmitter comprising: a receiver for receiving a response message from the unmanned aircraft system network function, the network publishing function, or a combination thereof, the response message comprising: the air vehicle identifier; and the publicly available subscription identifier; and Air vehicle certification results, permit results, or a combination thereof; Aircraft system security requirements information and a receiver comprising: a processor that stores the aircraft system security requirement information together with the air vehicle identifier, the public subscription identifier, and the air vehicle authentication result; The apparatus further comprises:

2. 10. The apparatus of claim 1, wherein the processor sets the security policy information to supported, enabled, or a combination thereof in response to an air subscription user plane security policy fetched from a management function being needed, in response to a user plane security policy fetched from the management function being needed, or a combination thereof.

3. 10. The apparatus of claim 1, wherein the processor sets the security policy information to not supported, not enabled, not preferred, not required, or a combination thereof in response to no aviation subscription being available for the air vehicle corresponding to the air vehicle identifier, in response to a user plane security policy fetched from a management function being preferred, not required, or a combination thereof.

4. 4. The apparatus of claim 1, 2, or 3, wherein the transmitter, in response to receiving a protocol data unit session establishment request having the air vehicle identifier from a user equipment, transmits the air vehicle authentication result during a protocol data unit session establishment procedure and the aircraft system security requirement information together with the air vehicle identifier to a session management function.

5. 1. An apparatus having unmanned aerial system networking capabilities, network publishing capabilities, or a combination thereof, comprising:

1. A receiver for receiving a first request message from an access and mobility management function, the first request message comprising: an air vehicle identifier; a public subscription identifier; and Security policy information and a receiver comprising: a transmitter that transmits a second request message to an unmanned aircraft system service supplier, an unmanned aircraft system traffic management function, or a combination thereof, the second request message comprising: the air vehicle identifier; and the publicly available subscription identifier; and The security policy information; a transmitter comprising: Processor and Furthermore, The receiver receives a second response message from the unmanned aircraft system service supplier, the unmanned aircraft system traffic management function, or a combination thereof, the second response message comprising: the air vehicle identifier; and the publicly available subscription identifier; and Air vehicle certification results and Aircraft system security requirements information and Equipped with The transmitter sends a first response message to the access and mobility management function, the first response message comprising: the air vehicle identifier; and the publicly available subscription identifier; and the air vehicle authentication result; said aircraft system security requirement information; Equipped with The apparatus, wherein the processor stores the aircraft system security requirement information along with the air vehicle identifier, the public subscription identifier, and the air vehicle authentication result.

6. 6. The apparatus of claim 5, wherein the transmitter, in response to receiving an authentication request from a session management function, transmits the air vehicle authentication result and the aircraft system security requirement information along with the air vehicle identifier to the session management function during a protocol data unit session establishment procedure.

7. 1. A method of session management functionality, comprising: sending a third request message to an unmanned aircraft system network function, a network publishing function, or a combination thereof, wherein the third request message comprises: an air vehicle identifier; a public subscription identifier; and Data request instructions and and receiving a third response message from the unmanned aircraft system network function, the network publishing function, or the combination thereof, the third response message comprising: the air vehicle identifier; and the publicly available subscription identifier; and Air vehicle certification results and Aircraft system security requirements information and and In response to receiving the air vehicle authentication result, determining to establish a protocol data unit session and skipping air vehicle authentication; storing the aircraft system security requirement information together with the air vehicle identifier, the public subscription identifier, the air vehicle authentication result, and the aircraft system security requirement information; applying user plane security based on the aircraft system security requirement information; A method comprising:

8. 8. The method of claim 7, further comprising receiving the third response message without sending the third request message in response to the unmanned aircraft system network capability, the network publishing capability, or the combination thereof comprising an access and mobility management capability.

9. 8. The method of claim 7, further comprising: receiving the third response message in response to the unmanned aircraft system network function, the network publishing function, or the combination thereof comprising an access and mobility management system, wherein the access and mobility management function receives a protocol data unit session establishment request having the air vehicle identifier, and the access and mobility management system has the air vehicle identifier with the air vehicle authentication result and the aircraft system security requirement information.

10. 10. The method of claim 7, 8 or 9, wherein the third request message is an authentication data request or an authentication request message.

11. The method according to any one of claims 7 to 10, wherein the third response message is an authentication data response or an authentication response message.

12. 12. The method of claim 7, wherein the third response message comprises an indication that data is unavailable.

13. 13. The method of any one of claims 7 to 12, further comprising the step of deciding to invoke air vehicle authentication if an indication of data unavailability is received or if air vehicle authentication results and security requirement information are not received from the network function.

14. 1. A method for an unmanned aircraft system service supplier, an unmanned aircraft system traffic management function, or a combination thereof, comprising: receiving a request message from an unmanned aircraft system network function, a network publishing function, or a combination thereof, the request message comprising: an air vehicle identifier; a public subscription identifier; and Security policy information and and sending a response message to the unmanned aircraft system network function, the network publishing function, or the combination thereof, wherein the response message comprises: the air vehicle identifier; and the publicly available subscription identifier; and Air vehicle certification results and Aircraft system security requirements information and and storing the aircraft system security requirement information together with the air vehicle identifier, the public subscription identifier, and the air vehicle authentication result; A method comprising:

15. whether the security policy information received from the unmanned aircraft system network capability, the network publishing capability, or the combination thereof is supported, enabled, or a combination thereof; Whether the unmanned aircraft system service supplier, unmanned aircraft system traffic management function, or a combination thereof, determines not to apply end-to-end security to session data, user plane data, or a combination thereof; or combinations of these 15. The method of claim 14, further comprising setting the aircraft system security requirement information as required based on:

16. 16. The method of claim 15, further comprising sending a cause value indicating that end-to-end security is not applicable, not supported, or a combination thereof.

17. whether the security policy information received from the unmanned aircraft system network capability, the network publishing capability, or the combination thereof is not supported, not enabled, not required, not preferred, or a combination thereof; whether the unmanned aircraft system service supplier, the unmanned aircraft system traffic management function, or a combination thereof, does not receive security policy information during air vehicle certification and / or authorization; whether the unmanned aircraft system service supplier, the unmanned aircraft system traffic management function, or a combination thereof, determines to apply end-to-end security to session data, user plane data, or a combination thereof; or Some combination of them 15. The method of claim 14, further comprising setting the aircraft system security requirement information as not required based on:

18. 20. The method of claim 17, further comprising sending a cause value indicating that end-to-end security is applicable, supported, or a combination thereof.

19. 19. The method of any one of claims 14 to 18, wherein if the security policy information received from the unmanned aircraft system network function, the network publishing function, or the combination thereof is supported, enabled, or a combination thereof, an unmanned aircraft system service supplier, an unmanned aircraft system traffic management function, or a combination thereof determines to skip end-to-end security, sets the aircraft system security requirements information as required, and sets a cause value as end-to-end security is not applicable, not supported, or a combination thereof.

20. 20. The method of any one of claims 14 to 19, wherein if the security policy information received from the unmanned aircraft system network function, the network publishing function, or the combination thereof is not supported, not enabled, not required, not preferred, or a combination thereof, an unmanned aircraft system service supplier, an unmanned aircraft system traffic management function, or a combination thereof determines to activate end-to-end security, sets the aircraft system security requirements information as not required, and sets a cause value as end-to-end security is applicable, supported, or a combination thereof.

Images