METHOD AND SYSTEM FOR SUPPORTING UAS DAA USING MOBILE NETWORK multicast AND BROADCAST FUNCTIONS
By using DAA network ID and service ID in a cellular network to select appropriate networks and cells, broadcast or multicast service information to the UAS, the short coverage distance and interface requirements of traditional UAS perception and avoidance solutions are solved, and a wider range of applications has been achieved. Acquisition of business information and more efficient UAS perception and avoidance.
Patent Information
- Application Number
- CN202380030027.2
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2022-04-04
- Filing Date
- 2023-03-29
- Publication Date
- 2024-11-12
AI Technical Summary
The traditional PC5-based UAS awareness and avoidance (DAA) solution relies on the UAS to collect the location information of the surrounding UAS by itself. The coverage distance is short and cannot support long-distance flights. It also requires the UAS to support the PC5 interface and lacks a DAA mechanism based on mobile networks.
Through the cellular base station as a ground station, the local UAS service information is broadcast or multicasted to the UAS using a mobile network, providing overall service information within a wider coverage area, using the DAA network ID and service ID to select appropriate networks and cells, and supporting UAS perception and avoidance.
It realizes UAS perception and avoidance on a larger scale, improves UAS's service information acquisition accuracy and coverage, reduces the special interface requirements for UAS devices, and provides a DAA solution based on mobile networks.
Smart Images

Figure CN118947068A_ABST
Abstract
Description
[0001] This application claims the benefit of U.S. Provisional Patent Application No. 63 / 326,980, filed on April 4, 2022, entitled "New Mechanism for Using Mobile Network Multicast and Broadcast Function to Support UAV DAA (detect and avoid)", the disclosure of which is incorporated herein by reference. Technical Field
[0002] The present invention generally relates to methods and systems for uncrewed aerial system (UAS) traffic management, and in particular embodiments, to methods and systems for supporting UAS detect and avoid (DAA) assistance using a mobile network. Background Art
[0003] 3GPP is committed to integrating UAS (such as uncrewed aerial vehicles (UAVs) or drones) into mobile 4G / 5G / 6G network systems. This not only enables UAS to support base station (e.g., gNB) functions for providing mobile access, but also leverages the mobile communication capabilities used by UAS to integrate mobile networks into global UAS service management systems and support various UAS applications. 3GPP SA2 created a new standardized specification (TS23.256) in Release 17 to support UAV identification, tracking, and connectivity. SA2 and RAN2 also have new Release 18 study projects on further enhancing 5G systems for UAV systems. Both study projects include how to use mobile networks to support the goal of detect and avoid (DAA) assistance by providing surrounding service information to cells connected to UAVs and UAV controllers. Summary of the invention
[0004] Technical advantages are generally achieved through embodiments of the present invention, which describe methods and apparatus for supporting UASDAA using mobile network multicast and broadcast capabilities in the present invention.
[0005] For ease of explanation, some embodiments of the present invention are described using UAV as an example. These embodiments can generally be applied using a UAS (which may be a UAV, a UAV controller that controls the UAV, or a combination of the UAV and the UAV controller).
[0006] According to an embodiment, an uncrewed aerial system (UAS) receives a network selection policy from a first network function device of a first network. The network selection policy instructs a second network to provide local UAS service information. The UAS receives uncrewed aerial system traffic management (UTM) support information from a second network function device of a second network. The UAS selects the second network based on the network selection policy and the UTM support information. The UAS is connected to a second network function device of the second network to receive local UAS service information from the second network function device.
[0007] In some embodiments, the first network may be a home network to which the UAS subscribes. The second network may be different from the first network.
[0008] In some embodiments, the second network may be part of a network of base stations or part of a network of cells of base stations.
[0009] In some embodiments, the UTM support information may be broadcast by the second network function device.
[0010] In some embodiments, the local UAS service information may be multicast or broadcast by the second network function device. In some embodiments, the second network function device may be a base station or an Internet protocol (IP)-based function device.
[0011] In some embodiments, the local UAS service information may be unicast by the second network function device.
[0012] In some embodiments, the UTM support information may indicate that the second network function device of the second network supports UTM, where the UTM includes at least one of a UAS identification or a UAS detect and avoid (DAA).
[0013] In some embodiments, the second network function device may be a ground base station. The UAS may be at least one of an uncrewed aerial vehicle (UAV) and a UAV controller that controls the UAV.
[0014] In some embodiments, the network selection policy may include at least one of a candidate network identifier (ID) or a candidate DAA ID. The UTM support information may include a network ID and a DAA network ID of the second network. In some embodiments, the DAA network ID may indicate that the network is used for UTM. The DAA network ID may be different from any one or more network IDs used to provide one or more other different non-UAS services. In some embodiments, the UE may select a second network based on a network ID in the UTM support information that matches the candidate network ID in the network selection policy, and a DAA network ID in the UTM support information that matches the candidate DAA ID in the network selection policy. In some embodiments, the UE may select a second network based on the coverage area where the UAS is located and the candidate coverage area indicated in the UTM support information. In some embodiments, the UAS may provide location information to the second network function device. The second network function device may provide group-customized service information for the member devices that have joined based on information from the member devices that have joined the group, and the group may include a UAS.
[0015] In some embodiments, the network selection policy may also define the selection granularity for each network or each cell of the second network.
[0016] According to an embodiment, a second network function device of a second network sends uncrewed aerial system traffic management (UTM) support information to an uncrewed aerial system (UAS). The UAS receives a network selection policy from a first network function device of a first network, and the network selection policy instructs the second network to provide local UAS traffic information. The UAS selects the second network according to the network selection policy and the UTM support information. The second network function device of the second network is connected to the UAS to send the local UAS traffic information from the second network function device.
[0017] In some embodiments, the first network may be a home network to which the UAS subscribes. The second network may be different from the first network.
[0018] In some embodiments, the second network may be part of a network of base stations or part of a network of cells of base stations.
[0019] In some embodiments, the UTM support information may be broadcast by the second network function device.
[0020] In some embodiments, the local UAS service information may be multicast or broadcast by the second network function device. In some embodiments, the second network function device may be a base station or an Internet protocol (IP)-based function device.
[0021] In some embodiments, the local UAS service information may be unicast by the second network function device.
[0022] In some embodiments, the UTM support information may indicate that the second network function device of the second network supports UTM, where the UTM includes at least one of a UAS identification or a UAS detect and avoid (DAA).
[0023] In some embodiments, the second network function device may be a ground base station. The UAS may be at least one of an uncrewed aerial vehicle (UAV) or a UAV controller that controls the UAV.
[0024] In some embodiments, the network selection policy may include at least one of a candidate network identifier (ID) or a candidate DAA ID. The UTM support information may include a network ID and a DAA network ID of the second network. In some embodiments, the DAA network ID may indicate that the network is used for UTM. The DAA network ID may be different from any one or more network IDs used to provide one or more other different non-UAS services. In some embodiments, the UE may select a second network based on a network ID in the UTM support information that matches the candidate network ID in the network selection policy, and a DAA network ID in the UTM support information that matches the candidate DAA ID in the network selection policy. In some embodiments, the UE may select a second network based on the coverage area where the UAS is located and the candidate coverage area indicated in the UTM support information. In some embodiments, the UAS may provide location information to the second network function device. The second network function device may provide group-customized service information for the member devices that have joined based on information from the member devices that have joined the group, and the group may include a UAS.
[0025] In some embodiments, the network selection policy may also define the selection granularity for each network or each cell of the second network. BRIEF DESCRIPTION OF THE DRAWINGS
[0026] For a more complete understanding of the present invention and its advantages, reference is now made to the following description taken in conjunction with the accompanying drawings, in which:
[0027] Figure 1A An exemplary communication system 100 is shown according to an embodiment;
[0028] Figure 1B shows a UAV-supported mobile network architecture according to an embodiment;
[0029] Figure 2 An exemplary architecture of an embodiment scheme is shown;
[0030] Figure 3A A flow chart illustrating selection of a DAA information broadcast network according to some embodiments;
[0031] Figure 3B A flow chart showing a UE receiving DAA information according to some embodiments is shown;
[0032] Figure 4A A flow chart showing a method performed by a UAS according to some embodiments;
[0033] Figure 4B A flow chart showing a method performed by a base station according to some embodiments;
[0034] Figure 5 An exemplary communication system 500 is shown in accordance with some embodiments;
[0035] Fig. 6A and Figure 6B An exemplary device is shown that can implement the methods and instructions according to the present invention according to some embodiments;
[0036] Figure 7 A block diagram of a computing system that may be used to implement the devices and methods disclosed herein is shown, according to some embodiments.
[0037] Corresponding numerals and symbols in the different figures generally refer to corresponding parts unless otherwise indicated.The figures are drawn to clearly illustrate the relevant aspects of the embodiments and are not necessarily drawn to scale. DETAILED DESCRIPTION
[0038] The making and using of embodiments of the present invention are discussed in detail below. However, it should be understood that the concepts disclosed herein can be embodied in a wide range of specific contexts, and the specific embodiments discussed herein are merely illustrative and are not intended to limit the scope of the claims. Furthermore, it should be understood that various changes, substitutions, and modifications may be made herein without departing from the spirit and scope of the present invention as defined by the appended claims.
[0039] Figure 1AAn exemplary communication system 100 according to an embodiment is shown. The communication system 100 includes an access node 110, which serves user equipment (UE), such as UE 120, having a coverage area 101. In a first operating mode, communications to and from the UE pass through the access node 110 having the coverage area 101. The access node 110 is connected to a backhaul network 115 to connect to the Internet, perform operations and management, etc. In a second operating mode, communications to and from the UE do not pass through the access node 110, but the access node 110 typically allocates resources for the UE to communicate when certain conditions are met. Communications between a pair of UEs 120 may use a sidelink connection (shown as two separate unidirectional connections 125). In Figure 1A In the embodiment, sidelink communication occurs between two UEs operating within the coverage area 101. However, sidelink communication may also generally occur in the following situations: both UEs 120 are outside the coverage area 101; both UEs 120 are inside the coverage area 101; or one UE 120 is inside the coverage area 101 and the other UE 120 is outside the coverage area 101. Communication between a UE and an access node pair occurs over a unidirectional communication link, where the communication link between the UE and the access node is referred to as an uplink 130, and the communication link between the access node and the UE is referred to as a downlink 135.
[0040] Generally, an access node may also be referred to as a Node B, an evolved Node B (eNB), a next generation (NG) Node B (gNB), a master eNB (MeNB), a secondary eNB (SeNB), a master gNB (MgNB), a secondary gNB (SgNB), a network controller, a control node, a base station, an access point, a transmission point (TP), a transmission-reception point (TRP), a cell, a carrier, a macro cell, a femto cell, a pico cell, etc., and a UE may also generally be referred to as a mobile station, a mobile station, a terminal, a user, a station, etc. The access node may provide wireless access according to one or more wireless communication protocols, for example, third generation partnership project (3GPP) long term evolution (LTE), LTE advanced (LTE-A), 5G, 5G LTE, 5G NR, sixth generation (6G) high speed packet access (HSPA), IEEE 802.11 series standards, such as 802.11a / b / g / n / ac / ad / ax / ay / be, etc. Although it is understood that the communication system may employ multiple access nodes capable of communicating with multiple UEs, for simplicity, only one access node and two UEs are shown.
[0041] In Release 17, TS23.256 defines the network architecture and listed functions that allow mobile networks to work with UAS traffic management (UTM) systems to identify and track mobile connected UAVs and manage control and command (C2) communications for UAVs. C2 communications refer to user plane links used to pass messages with command and control information for UAV operations from a UAV controller or UTM to a UAV, or to report telemetry data from a UAV to its UAV controller or UTM. This architecture can also be used for UAA DAA. An exemplary mobile network architecture defined by 3GPP for supporting UAVs is shown in Figure 1. Figure 1BAs shown in Figure 4.2.2-1 of TS 23.256 "Support for uncrewed aerial systems (UAS) attachment, identification and tracking; Phase 2".
[0042] Unlike the traffic management of manned aircraft, which have well-defined and developed DAA mechanisms to prevent collisions between aircraft, UAS such as drones do not have such DAA mechanisms. Global regulators and industry partners are working together to define such mechanisms. Both 3GPP SA2 and RAN have created Release 18 self-adaptive intrusion detection (SID) to study potential 5G-enabled scenarios for drone DAA mechanisms. One of the main potential directions for the scenarios proposed by various companies is to use mobile sidelink (PC5 interface), similar to the vehicle-to-everything (V2X) use case, allowing UAVs to broadcast their location as well as receive location information from nearby UAVs.
[0043] Limitations of Traditional Systems
[0044] The technical problems of the traditional PC5-based UE broadcast solution include the following:
[0045] First, the traditional scheme relies entirely on the UAS to collect the location information of each surrounding UAS. Therefore, the UAS creates its own surrounding traffic picture. Due to coverage / blocking issues, the UAS may not be able to collect the location information of some nearby UAS. In addition, the UAS may not be able to obtain an accurate traffic picture due to its own poor sidelink implementation.
[0046] Second, because PC5 covers a short distance, the UAS can only observe traffic within a limited range, which may not be helpful for long-distance flight plans of the UAS. A larger coverage area (e.g., greater than 10 km in diameter) is required. The coverage area of the sidelink is usually on the order of 1 km to 2 km in diameter.
[0047] Third, traditional solutions may require the mobile element (ME) of the UAS to support the PC5 interface, which is an optional feature of most existing UE implementations.
[0048] For manned aircraft DAA, there is an automatic dependent surveillance-broadcast (ADS-B) system, in which aircraft not only broadcast their own positions, but also receive traffic information on a dedicated spectrum from broadcast ground stations through their ADS-B system. The broadcast traffic information from the ground stations provides near real-time traffic information in the area.
[0049] The existing ADS-B system is a dedicated broadcast system that uses a dedicated spectrum designed for manned aircraft. However, the existing ADS-B system is not suitable for UAS and does not consider the use of mobile networks. Therefore, it is desirable to define a system for UAVs that uses mobile networks. The European Union Aviation Safety Agency (EASA) is defining an ADS-B-like solution for UAVs, in which the PC5 interface is an option.
[0050] Currently, there is no 3GPP-based DAA mechanism for UAVs. One possible feature is to use the existing 4G and 5G multicast / broadcast service (MBS) scheme defined by 3GPP. This feature is application-independent, but no attempt has been made to support UAS. There is no centralized network-based DAA scheme defined in 3GPP for V2X that can be used for UAS.
[0051] Exemplary Embodiments
[0052] The technical solution of this embodiment solves the above-mentioned technical limitations of the traditional system. The present invention provides a technical solution in which a cellular base station can act as a ground station of a UASDAA to broadcast overall business information in a specific location / area to a cellular-connected UAS via a cellular connection. The present invention provides a solution for broadcasting or multicasting UAS business information to one or more mobile (4G, 5G and / or xG) connected UAVs and one or more UAV controllers using a mobile network. A mobile-connected UAV or UAV controller may or may not subscribe to the same mobile operator that operates the broadcast of UAS business information.
[0053] Figure 2An exemplary architecture 200 of the present embodiment is shown. A UAS services provider (UAS servicesupplier, USS) 202 includes a DAA server 204, which can run on one or more network devices. The DAA server 204 can collect local UAS business information for DAA, including DAA information of devices in the coverage area 220 of network A. The DAA server 204 can send DAA information to a UAV controller (e.g., UAV controller 212) in the coverage area 220. The UAV controller 212 can relay the DAA information to one or more UAVs (e.g., UAV 214a) controlled by the UAV controller 212 via C2 communication. The combination of the UAV controller 212, the UAV 214a, or the UAV controller 212 and the UAV 214 can be considered a UAS.
[0054] In addition, the DAA server 204 can send DAA information to the USS network function (NF) / network exposure function (NEF) 206 of network A. The NF / NEF 206 can run on one or more network devices. The USS NF / NEF 206 can forward the DAA information to the multicast-broadcast (MB) user plane function (UPF) 208, which can run on one or more network devices. Then, the MB UPF 208 forwards the DAA information to the base station 210a of network A. The base station 210a can be a dedicated base station for broadcasting / multicasting DAA information to UAVs (e.g., UAVs 214a, 214b, and 214c). Network A can also include one or more other base stations, such as base station 210b, which handle services other than DAA information services. UAVs in the coverage area 220 of network A can subscribe to network A or not. Therefore, network A may or may not be the home network of the UAVs in coverage area 220.
[0055] Network selection strategy for UE receiving UASDAA broadcast / multicast networks
[0056] In order for the UAV to receive DAA information (e.g., local UAS service information for DAA), the UAV needs to identify and access a network that provides the UASDAA broadcast / multicast service. The UAV may use a (stored) network selection policy provided to the UAV's home network. The home network has a subscription for the UAV to identify and access a network that provides the UASDAA broadcast / multicast service.
[0057] Embodiments include using new network and cell selection strategies. The new strategy can be created by the UAV's home network, which has the UAV's communication service subscription. The new network and cell selection strategy is used for the UAV to select a network or cell that provides UAS DAA broadcast / multicast services (e.g., multicast / broadcast local business information for DAA purposes). Multicast / broadcast transmission can be considered as point-to-multipoint (P2M) transmission. Using Rel-17 NR, multicast transmission can become point-to-point (P2P) transmission. The new network and cell selection strategy can be provided to the UAV by the home network, for example, by enhancing the UE policy update process or UE route selection policy (URSP) defined in 3GPP TS23.501 and TS23.502. The UAV can use the provided network and cell selection strategy to select a network (or cell) for DAA purposes.
[0058] In order for the UAV to identify and select the UAS DAA broadcast / multicast network / cell, an embodiment may use one or more new UAV DAA identifiers associated with the selected network / cell. The new identifier may be defined as a DAA network ID or a DAA service ID. The DAA network ID may be used together with an existing network identifier (such as a PLMN ID or NID) as a unique identifier to assist the UE in identifying whether the network or cell broadcasts / multicasts DAA information. For ease of explanation, some embodiments are described that use the DAA network ID to identify the network for broadcasting / multicasting DAA information. These embodiments may also be applicable to situations where a new ID is used to identify a cell for broadcasting / multicasting DAA information.
[0059] In various embodiments, a DAA network ID may be defined as a new type of network ID to indicate that the network identified by the DAA network ID provides UAS service management information. The DAA network ID may be used for the same network, which may have one or more other network IDs to provide one or more other different non-UAS services. For example, operator A has a network in an area (e.g., coverage area 220) with PLMN ID 1. However, if the network broadcasts / multicasts DAA information (e.g., UAV service information), the same network in the area may also be assigned an additional DAA network ID 8. The unique identifier of a network in the area (e.g., coverage area 220) may be a combination of the PLMN ID (1) and the DAA network ID (8).
[0060] In some embodiments, the DAA network ID may be a local ID used in a region or country, or a global ID assigned by a global entity.
[0061] In some embodiments, the service type of the DAA service ID is an ID assigned to identify the DAA service provided by the network. Even in the same network, there can be several DAA service IDs because DAA information can have different levels, such as accuracy level, service area range, service type (e.g., whether the service includes manned aircraft service) or other additional information, such as weather, etc. This service type of the DAA network ID can be further classified into additional levels according to the type of information provided.
[0062] In some embodiments, there may be a common UAS DAA ID, which may be a combination of different types of DAA network IDs and further divided into multiple fields. One example is that the ID may be represented as having three parts. The first part identifies one or more DAA services supported or provided. The second part indicates the DAA network ID. The third part indicates the DAA service type. For example, the DAA ID may be 16 bits. Among them, the first bit may be a DAA capability indicator. The next 8 bits may be allocated to the UAS network ID. The remaining bits may indicate the type of DAA information provided.
[0063] Using the above new DAA ID, a new DAA network selection strategy can be used in the following embodiments.
[0064] In some embodiments, a UAS DAA ID list (e.g., a network DAA ID list and a DAA service ID list) may be added as selection criteria. The UAV may only select one or more networks / one or more cells that broadcast / send those IDs. In one embodiment, the list may be organized in order of selection priority of one or more DAA IDs.
[0065] In some embodiments, selection conditions for UASDAA service information broadcast / multicast capability support may be added, such as whether layer 2 and / or layer 3 MBS capabilities are required. Layer 2-based or layer 3-based MBS capabilities may be mapped to two different MBS delivery mechanisms defined in 3GPP (TS23.247): a separate MBS service delivery method (layer 3-based, IP-based MBS) and a shared MBS service delivery method (layer 2-based, requiring a radio access network (RAN) that supports MBS capabilities).
[0066] In some embodiments, since there may be dedicated cells or base stations (e.g., gNBs) for UASDAA MBS services, the network selection policy may be enhanced to define the selection granularity as per cell per network or a specific network, new selection validity conditions such as coverage area, time of broadcast / multicast information, and the like.
[0067] In some embodiments, a new DAA Group ID list may be used for an industry consortium of which the UAV's home operator is a member, and no subscription may be required to receive uncrewed aerial system traffic management (UTM) traffic information from any network within the group. The UAV may select a network that belongs to the group. The UAV may select a network that broadcasts a DAA Group ID that matches an ID in the DAA Group ID list.
[0068] In some embodiments, the DAA network selection policy may be implemented as part of the over-the-air subscription defined in TS 23.256.
[0069] The above 5GC separate MBS service delivery method may only be applicable to one or more multicast MBS sessions. The 5G core network (5GC) can receive a single copy of the MBS data packet and deliver a separate copy of these MBS data packets to a separate UE (e.g., UAV) through a PDU session for each UE. Therefore, for each such UE, a PDU session may be required to be associated with the multicast session.
[0070] The 5GC shared MBS service delivery method can be applied to broadcast and multicast one or more MBS sessions. The 5GC can receive a single copy of the MBS data packets and pass a single copy of these MBS data packets to the next generation (NG)-RAN node, and then the NG-RAN node passes the data packets to one or more UEs (e.g., UAVs).
[0071] UE detection and selection of UASDAA broadcast networks based on network selection strategy
[0072] The UAV may scan and receive broadcast system information from surrounding networks and use such system information to identify a suitable DAA network according to a stored DAA network selection policy. The broadcast system information may indicate an identifier. Embodiments of the present invention provide a new network system broadcast mechanism that allows a network to broadcast its DAA support information to UAVs within its coverage area.
[0073] In some embodiments, embodiments allow one or more base stations (e.g., one or more gNBs) to be dedicated to broadcasting / multicasting service information in a location / area. One or more base stations may broadcast an indication that the base station is a DAA designated ground station that is broadcasting / multicasting DAA information (e.g., local DAA service information). The indication may be broadcast by one or more base stations via a SIB message.
[0074] In some embodiments, a network (e.g., Figure 2The network A in the UAV may also broadcast a dedicated UAS DAA ID, such as a DAA network ID and / or a DAA service ID. If the UAV detects such an indication during the UAV's network discovery and selection process, and if the network matches the UAV's network selection policy, the UAV may establish a connection to the base station to receive the broadcast DAA information.
[0075] In some embodiments, a designated base station (e.g., eNB / gNB) may also broadcast other DAA information, including the IP address or ID of a DAA server in the cloud. The DAA server is a central database that provides real-time UTM information in the area, such as DAA information. The UAV may forward the network ID or DAA server ID and / or address received from the broadcast / multicast network to its UAV controller via C2 communications, which may also query the DAA information via other interfaces (e.g., the Internet).
[0076] In some embodiments, since the current 3GPP specification supports layer 2 and layer 3 broadcast and / or multicast services, the DAA capability indication information broadcast by the base station may also indicate the type of DAA broadcast / multicast service (layer 2 or layer 3).
[0077] In some embodiments, the base station may also broadcast area of interest information, which defines the coverage area for broadcast / multicast DAA information (eg, local service information).
[0078] Receive UASDAA information
[0079] In the present invention, it may or may not be necessary to subscribe to the UTM service information of the DAA (eg, the DAA information). In some other embodiments, it may be necessary to have the DAA information subscribed.
[0080] DAA information can include traffic information of local UAVs or manned aircraft within a specific area. DAA information can be transmitted from a DAA server in a USS (e.g., DAA server 204 in USS 202) to UAS (UAVs and / or UAV controllers), such as UAV controller 212, UAVs 214a, 214b, and 214c. DAA information can be transmitted through the 3GPP system via a new dedicated DAA information container. DAA information can also be part of a C2 aviation payload container or a UAS payload container, both of which are defined in TS 23.256. The way in which a UAV and its controller receive DAA information may be different.
[0081] If the DAA information is received from the local network via layer 2 broadcast, the UAS can use the following method to receive the DAA information.
[0082] In method 1, the UE (e.g., UAV) may have a subscription to another mobile operator that is not the same operator of the DAA information broadcast network. In order to receive the DAA information, the UAV may be required to have two cellular links (cells), one of which is connected to the network that provides normal data communication for the UAV, and the other link is used (periodically) for the DAA information broadcast network to receive the DAA information.
[0083] In method 2, if the DAA information broadcast network is the same as the network to which the UE (e.g., UAV) subscribes, the UAV may only need to periodically tune one of the UAV's receivers (Rx) to the cell broadcasting the DAA information. The new rules of URSP can be used to divide Rx into different paths.
[0084] In method 3, if the DAA information broadcast network has a roaming relationship with the UE's home mobile network (e.g., UAV), the UAV can roam to the DAA information broadcast network based on the UTM roaming policy provided by the UE's home network, or be directed to the DAA information broadcast network by the home network. The home network can direct the UAV to the DAA information broadcast network based on a trigger from the UTM / USS through the enhanced N33 interface.
[0085] If the DAA information is received from the local network via layer 3 IP layer broadcast / multicast, the UAS can use the following method to receive the DAA information.
[0086] Method 4 may require the UE (e.g., UAV) to subscribe to the DAA MBS service. If the network providing the DAA service (e.g., the DAA information broadcast / multicast network) is the same home network of the UAV, the UAV may perform a service subscription process with the DAA information broadcast / multicast network; otherwise, the UAV may roam to the DAA information broadcast / multicast network to receive the DAA service.
[0087] In method 5, the UE (eg, UAV) remains in the same network to which it is connected. Method 5 may use the DAA server address broadcasted by the DAA information broadcast / multicast network to establish an Internet connection with the DAA server without switching to the DAA information broadcast / multicast network.
[0088] In order for the UAV to receive multicast UTM service information (e.g., DAA information), the UAV may be required to send specific one or more join / keep alive messages to the USS to keep the UAV in the multicast group. The message may include the location, speed, and other service information of the UAV. The USS or DAA server may provide service information customized for the group based on information from members joining the group.
[0089] UASDAA gNB / network discovery and selection based on new network selection strategy
[0090] Figure 3A A method for selecting a DAA information broadcast / multicast network (e.g., Figure 2 300 of a cellular connected UAV 214a having a UAS subscription including a network selection policy. The network selection policy directs the UAV 214a to select a network that supports UTM, including DAA (e.g., providing local UAS service information). The home network 302 of the UAV 214a may provide the network selection policy to the UAV 214a. The network selection policy may include a network ID of a DAA broadcast / multicast network (e.g., Figure 2 The network selection policy may be provided to the UAV via a UE parameter update (UPU) / UE configuration update (UCU) message as part of a network selection policy or URSP update.
[0091] In operation 302, a DAA information broadcast / multicast network (e.g., network A) may assign and configure base station 210a as a DAA ground station to broadcast / multicast DAA information to all UAS in an area (e.g., coverage area 220). Base station 210a may send a system information block (SIB) broadcast message with an indication that the base station supports DAA information broadcast / multicast, a public DAA ID, and / or other DAA capability indicators. In some embodiments, network A may configure only one base station in the network (e.g., base station 210a) to broadcast DAA information. In some embodiments, network A may configure some or all base stations in the network to broadcast DAA information.
[0092] In operation 303, USS 202 may periodically send broadcast / multicast DAA information to network A via USS NF / NEF 206 of network A (303a of operation 303). Then, the DAA information is broadcast / multicast via base station 210a using the defined 3GPP MBS service (303b of operation 303). The DAA information from USS 202 may be transmitted to the UAV via the 3GPP network MBS service in a dedicated DAA information container or as part of the C2 aeronautical payload defined in TS 23.256.
[0093] In operation 304, UAV 214a flies into the coverage area (e.g., coverage area 220) of network A. UAV 214a activates the DAA service and begins searching for any ground station to receive DAA information from.
[0094] In operation 305, the UAV 214a receives broadcast SIBs from one or more nearby networks. The UAV 214a checks each received broadcast SIB to see if the received network ID and public DAAID information matches the UAV's stored network selection policy. Based on the UAV's stored network selection policy, the UAV 214a selects network A and selects base station 210a (or a cell of network A) as the DAA ground station for broadcasting / multicasting DAA information.
[0095] In operation 306, UAV 214a connects to base station 210a to receive DAA information broadcast / multicast by base station 210a of network A.
[0096] UAV receives DAA information
[0097] Figure 3B A flow chart 350 is shown of a UE (eg, UAS or UAV) receiving DAA information from a base station according to some embodiments. In operation 351, the UAV 214a detects the network B (eg, the home network 302) and the base station 210a for DAA service.
[0098] For a UE (eg, UAS or UAV) to receive DAA information, the above-described method 3 or method 4 may be used.
[0099] Method 3 is used for layer 2 broadcasting. In operation 352a, based on the network selection policy for UAV 214a (which is provided and stored in UAV 214a), UAV 214a roams into network A. In operation 353a (corresponding to Figure 3A In operation 303 in , following a defined 3GPP MBS service procedure, the UAV 214a receives DAA information from the base station 210a (via or bypassing the UAV controller 212).
[0100] Method 4 is used for layer 3 broadcast. In operation 352b, the base station 210a provides the DAA server address and the layer 3 broadcast indication in its SIB broadcast information. In operation 353b, the UAV 214a stays in the current network (e.g., the home network 302) to which the UAV 214a is connected. The UAV 214a can establish an Internet connection with the DAA server in the USS 202 via the home network 302 using the DAA server address received from the base station 210a, and receive DAA information (via or bypassing the UAV controller 212).
[0101] The present invention can be applicable to LTE, NR and higher versions.
[0102] The present invention may be combined with existing technologies based on Uu or non-3GPP technologies or existing technologies based on unlicensed frequency bands.
[0103] Figure 4A A flow chart of a method 400 performed by an unmanned aerial system (UAS) (e.g., a UAV, a UAV controller, or a combination of a UAV and a UAV controller) according to some embodiments is shown. The UAS may include computer readable code or instructions executed on one or more processors of the UAS. It will be appreciated by those of ordinary skill in the art that the present invention may decode software for implementing or executing method 400. Method 400 may include more or fewer operations than those shown and described, and may be performed or performed in a different order. Computer readable code or instructions of software executable by one or more processors may be stored in a non-transitory computer readable medium, such as a memory of the UAS.
[0104] In operation 402, the UAS receives a network selection policy from a first network function device of a first network. The network selection policy indicates that a second network provides local UAS service information.
[0105] In operation 404, the UAS receives uncrewed aerial system traffic management (UTM) support information from a second network function device (eg, a base station) of a second network.
[0106] In operation 406, the UAS selects a second network according to the network selection policy and the UTM support information.
[0107] In operation 408, the UAS connects to a second network function device of the second network to receive local UAS service information from the second network function device.
[0108] In some embodiments, the first network may be a home network to which the UAS subscribes. The second network may be different from the first network.
[0109] In some embodiments, the second network may be part of a network of base stations or part of a network of cells of base stations.
[0110] In some embodiments, the UTM support information may be broadcast by the second network function device.
[0111] In some embodiments, the local UAS service information may be multicast or broadcast by the second network function device. In some embodiments, the second network function device may be a base station or an Internet protocol (IP)-based function device.
[0112] In some embodiments, the local UAS service information may be unicast by the second network function device.
[0113] In some embodiments, the UTM support information may indicate that the second network function device of the second network supports UTM, where the UTM includes at least one of a UAS identification or a UAS detect and avoid (DAA).
[0114] In some embodiments, the second network function device may be a ground base station. The UAS may be at least one of an uncrewed aerial vehicle (UAV) or a UAV controller that controls the UAV.
[0115] In some embodiments, the network selection policy may include at least one of a candidate network identifier (ID) or a candidate DAA ID. The UTM support information may include a network ID and a DAA network ID of the second network. In some embodiments, the DAA network ID may indicate that the network is used for UTM. The DAA network ID may be different from one or more network IDs that provide one or more other different non-UAS services. In some embodiments, the UE may select a second network based on a network ID in the UTM support information that matches the candidate network ID in the network selection policy, and a DAA network ID in the UTM support information that matches the candidate DAA ID in the network selection policy. In some embodiments, the UE may select a second network based on the coverage area where the UAS is located and the candidate coverage area indicated in the UTM support information. In some embodiments, the UAS may provide location information to the second network function device. The second network function device may provide group-customized service information for the member devices that have joined based on information from the member devices that have joined the group, and the group may include a UAS.
[0116] In some embodiments, the network selection policy may also define the selection granularity for each network or each cell of the second network.
[0117] Figure 4BA flow chart of a method 450 performed by a second network function device (e.g., base station 212a) of a second network according to some embodiments is shown. The second network function device may include computer readable code or instructions executed on one or more processors of the second network function device. It will be appreciated by those of ordinary skill in the art that the present invention may decode software for implementing or executing method 450. Method 450 may include more or fewer operations than those shown and described, and may be performed or performed in a different order. Computer readable code or instructions of software executable by one or more processors may be stored in a non-transitory computer readable medium, such as a memory of a second network function device.
[0118] In operation 452, a second network function device of a second network sends uncrewed aerial system traffic management (UTM) support information to an uncrewed aerial system (UAS). The UAS receives a network selection policy from a first network function device of a first network, the network selection policy instructing the second network to provide local UAS traffic information. The UAS selects the second network based on the network selection policy and the UTM support information.
[0119] In operation 454, a second network function device of the second network connects with the UAS to transmit local UAS service information from the second network function device.
[0120] In some embodiments, the first network may be a home network to which the UAS subscribes. The second network may be different from the first network.
[0121] In some embodiments, the second network may be part of a network of base stations or part of a network of cells of base stations.
[0122] In some embodiments, the UTM support information may be broadcast by the second network function device.
[0123] In some embodiments, the local UAS service information may be multicast or broadcast by the second network function device. In some embodiments, the second network function device may be a base station or an Internet protocol (IP)-based function device.
[0124] In some embodiments, the local UAS service information may be unicast by the second network function device.
[0125] In some embodiments, the UTM support information may indicate that the second network function device of the second network supports UTM, where the UTM includes at least one of a UAS identification or a UAS detect and avoid (DAA).
[0126] In some embodiments, the second network function device may be a ground base station. The UAS may be at least one of an uncrewed aerial vehicle (UAV) or a UAV controller that controls the UAV.
[0127] In some embodiments, the network selection policy may include at least one of a candidate network identifier (ID) or a candidate DAA ID. The UTM support information may include a network ID and a DAA network ID of the second network. In some embodiments, the DAA network ID indicates that the network is used for UTM. The DAA network ID may be different from any one or more network IDs used to provide one or more other different non-UAS services. In some embodiments, the UE may select a second network based on a network ID in the UTM support information that matches the candidate network ID in the network selection policy, and a DAA network ID in the UTM support information that matches the candidate DAA ID in the network selection policy. In some embodiments, the UE may select a second network based on the coverage area where the UAS is located and the candidate coverage area indicated in the UTM support information. In some embodiments, the UAS may provide location information to the second network function device. The second network function device may provide group-customized service information for the member devices that have joined based on information from the member devices that have joined the group, and the group may include a UAS.
[0128] In some embodiments, the network selection policy may also define the selection granularity for each network or each cell of the second network.
[0129] Figure 5An exemplary communication system 500 is shown. In general, the system 500 enables multiple wireless or wired users to send and receive data and other content. The system 500 can implement one or more channel access methods, such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), single-carrier FDMA (SC-FDMA), or non-orthogonal multiple access (NOMA).
[0130] In this example, the communication system 500 includes electronic devices (ED) 510a to 510c, radio access networks (RAN) 520a and 520b, a core network 530, a public switched telephone network (PSTN) 540, the Internet 550, and other networks 560. Figure 5 A certain number of these components or elements are shown, but any number of these components or elements may be included in system 500 .
[0131] EDs 510a to 510c are used to operate or communicate in the system 500. For example, EDs 510a to 510c are used to transmit or receive through a wireless or wired communication channel. Each ED 510a to 510c represents any suitable end-user device and may include (or may be referred to as): user equipment (UE), wireless transmit or receive unit (WTRU), mobile station, fixed or mobile subscriber unit, cellular phone, personal digital assistant (PDA), smart phone, laptop, computer, touch pad, wireless sensor or consumer electronic device.
[0132] RAN 520a includes a base station 570a, and RAN 520b includes a base station 570b. Each of the base stations 570a and 570b is used to wirelessly connect to one or more EDs of EDs 510a to 510c, so as to access the core network 530, PSTN 540, Internet 550 or other networks 560. For example, the base stations 570a and 570b may include (or be) one or more of several well-known devices, such as a base transceiver station (BTS), Node-B (NodeB), evolved NodeB (evolved NodeB, eNodeB), next generation (next generation NodeB, gNB), home NodeB, home eNodeB, site controller, access point (access point, AP) or wireless router. EDs 510a to 510c are used to connect and communicate with the Internet 550, and can access the core network 530, PSTN 540 or other networks 560.
[0133] exist Figure 5 In the illustrated embodiment, base station 570a forms part of RAN 520a, which may include other base stations, elements or devices. In addition, base station 570b forms part of RAN 520b, which may include other base stations, elements or devices. Each of base stations 570a and 570b is used to send or receive wireless signals within a specific geographic area or region (sometimes referred to as a "cell"). In some embodiments, multiple-input multiple-output (MIMO) technology may be used so that each cell has multiple transceivers.
[0134] Base stations 570a and 570b communicate with one or more of EDs 510a-510c using wireless communication links over one or more air interfaces 590. Air interfaces 590 may use any suitable radio access technology.
[0135] It is contemplated that the system 500 may use multi-channel access functionality, including the schemes described above. In certain embodiments, the base station and ED implement 5G new radio (NR), LTE, LTE-A, or LTE-B. Of course, other multiple access schemes and wireless protocols may also be used.
[0136] RAN 520a and 520b communicate with core network 530 to provide voice, data, applications, voice over internet protocol (VoIP) or other services to ED 510a to 510c. It is understood that RAN 520a and 520b or core network 530 can communicate directly or indirectly with one or more other RANs (not shown). Core network 530 can also be used as a gateway access for other networks (e.g., PSTN 540, Internet 550, and other networks 560). In addition, some or all of ED 510a to ED 510c can include functionality to communicate with different wireless networks through different wireless links using different wireless technologies or protocols. Instead of wireless communication (or in addition to wireless communication), ED can also communicate with a service provider or switch (not shown) and with Internet 550 through a wired communication channel.
[0137] although Figure 5 An example of a communication system is shown, but the Figure 5 For example, communication system 500 may include any number of EDs, base stations, networks, or other components in any suitable configuration.
[0138] Fig. 6A and Figure 6B An exemplary device is shown in which the methods and instructions according to the present invention can be implemented. Specifically, Fig. 6A An exemplary ED 610 is shown, Figure 6B An exemplary base station 670 is shown. These components may be used in system 500 or any other suitable system.
[0139] like Fig. 6A As shown, ED 610 includes at least one processing unit 600. Processing unit 600 implements various processing operations of ED 610. For example, processing unit 600 can perform signal encoding, data processing, power control, input / output processing, or any other function that enables ED 610 to operate in system 1000. Processing unit 600 also implements the methods and instructions described in detail above. Each processing unit 600 includes any suitable processing or computing device for performing one or more operations. For example, each processing unit 600 may include a microprocessor, a microcontroller, a digital signal processor, a field programmable gate array, or an application specific integrated circuit.
[0140] ED 610 also includes at least one transceiver 602. Transceiver 602 is used to modulate data or other content for transmission through at least one antenna or network interface controller (NIC) 604. Transceiver 602 is also used to demodulate data or other content received by at least one antenna 604. Each transceiver 602 includes any suitable structure for generating a signal for wireless or wired transmission or for processing a signal received wirelessly or wired. Each antenna 604 includes any suitable structure for sending or receiving a wireless signal or a wired signal. One or more transceivers 602 can be used for ED 610, and one or more antennas 604 can be used for ED 610. Although transceiver 602 is shown as a single functional unit, transceiver 602 can also be implemented using at least one transmitter and at least one separate receiver.
[0141] ED 610 also includes one or more input / output devices 606 or interfaces (e.g., a wired interface to the Internet 550). Input / output devices 606 facilitate interaction with users or other devices in a network (network communications). Each input / output device 606 includes any suitable structure for providing information to or receiving information from a user, such as a speaker, microphone, keypad, keyboard, display, or touch screen, including network interface communications.
[0142] In addition, the ED 610 includes at least one memory 608. The memory 608 stores instructions and data used, generated, or collected by the ED 610. For example, the memory 608 can store software or firmware instructions executed by one or more processing units 600 and data for reducing or eliminating interference in incoming signals. Each memory 608 includes one or more any suitable volatile or non-volatile storage and retrieval devices. Any suitable type of memory can be used, such as random access memory (RAM), read only memory (ROM), hard disk, optical disk, subscriber identity module (SIM) card, memory stick, secure digital (SD) memory card, etc.
[0143] like Figure 6BAs shown, the base station 670 includes at least one processing unit 650, at least one transceiver 652 (which includes functions for a transmitter and a receiver), one or more antennas 656, at least one memory 658, and one or more input / output devices or interfaces 666. A scheduler as understood by those skilled in the art is coupled to the processing unit 650. The scheduler may be included in the base station 670 or run separately from the base station 670. The processing unit 650 implements various processing operations of the base station 670, such as signal encoding, data processing, power control, input / output processing, or any other function. The processing unit 650 may also support the methods and teachings described in detail above. Each processing unit 650 includes any suitable processing or computing device for performing one or more operations. For example, each processing unit 650 may include a microprocessor, a microcontroller, a digital signal processor, a field programmable gate array, or an application specific integrated circuit.
[0144] Each transceiver 652 includes any suitable structure for generating a signal for wireless or wired transmission to one or more EDs or other devices. Each transceiver 652 also includes any suitable structure for processing a signal received wirelessly or by wire from one or more EDs or other devices. Although shown as a combination of transceivers 652, the transmitter and receiver can be separate components. Each antenna 656 includes any suitable structure for sending or receiving wireless signals or wired signals. Although the common antenna 656 is shown here as coupled to the transceiver 652, one or more antennas 656 can be coupled to one or more transceivers 652 so that a separate antenna 656 can be coupled to the transmitter and receiver (if the transmitter and receiver are equipped as separate components). Each memory 658 includes one or more any suitable volatile or non-volatile storage and retrieval devices. Each input / output device 666 promotes interaction with users or other devices (network communication) in the network. Each input / output device 666 includes any suitable structure for providing information to a user or receiving information from a user, including a network communication interface.
[0145] Figure 7A block diagram of a computing system 700 that can be used to implement the devices and methods disclosed herein according to some embodiments is shown. For example, the computing system can be any entity of a UE, an access network (AN), a mobility management (MM), a session management (SM), a user plane gateway (UPGW), or an access stratum (AS). A specific device may use all of the components shown or only a subset of the components, and the level of integration may vary from device to device. In addition, a device may include multiple instances of a component, such as multiple processing units, processors, memories, transmitters, receivers, etc. The computing system 700 includes a processing unit 702. The processing unit includes a central processing unit (CPU) 714, a memory 708, and may also include a mass storage 704, a video adapter 710, and an I / O interface 712 connected to a bus 720.
[0146] Bus 720 can be one or more of several bus architectures of any type, including a storage bus or storage controller, a peripheral bus, or a video bus. CPU 714 can include any type of electronic data processor. Memory 708 can include any type of non-transient system memory, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous DRAM (SDRAM), read-only memory (ROM) or a combination thereof. In one embodiment, memory 708 can include a ROM used at startup and a DRAM for storing programs and data, which is used when executing a program.
[0147] The mass storage 704 may include any type of non-transitory storage device for storing data, programs, and other information and making the data, programs, and other information accessible via the bus 720. For example, the mass storage 704 may include one or more of a solid-state drive, a hard disk drive, a magnetic disk drive, or an optical disk drive.
[0148] The interface of video adapter 710 and I / O interface 712 can couple external input and output devices to processing unit 702. As shown, examples of input and output devices include a display 718 coupled to video adapter 710 and a mouse, keyboard, or printer 716 coupled to I / O interface 712. Other devices can be coupled to processing unit 702, and more or fewer interface cards can be used. For example, a serial interface such as a universal serial bus (USB) (not shown) can be used to provide an interface for external devices.
[0149] The processing unit 702 also includes one or more network interfaces 706, which may include a wired link (e.g., an Ethernet cable) or a wireless link to an access node or a different network. The network interface 706 enables the processing unit 702 to communicate with a remote unit over a network. For example, the network interface 706 may provide wireless communication via one or more transmitters / transmit antennas and one or more receivers / receive antennas. In one embodiment, the processing unit 702 is coupled to a local area network 722 or a wide area network for data processing and communication with remote devices (e.g., other processing units, the Internet, or a remote storage facility).
[0150] It should be understood that one or more steps of the embodiment method provided herein can be performed by corresponding units or modules. The corresponding units or modules can be hardware, software or a combination thereof. For example, one or more units or modules can be integrated circuits, such as field programmable gate arrays (FPGA) or application-specific integrated circuits (ASIC).
[0151] Although the specification has been described in detail, it should be understood that various changes, substitutions and modifications may be made without departing from the spirit and scope of the invention as defined by the appended claims. Furthermore, the scope of the invention is not intended to be limited to the specific embodiments described herein, and as will be readily appreciated by those of ordinary skill in the art from this disclosure, processes, machines, manufactures, compositions of matter, components, methods or steps (currently existing or to be developed later) may perform substantially the same functions or obtain substantially the same results as the corresponding embodiments described herein. Therefore, the appended claims are intended to include within their scope such processes, machines, manufactures, compositions of matter, components, methods or steps.
Claims
1. A method performed by an unmanned aerial system (UAS), characterized in that: The method comprises: receiving a network selection policy from a first network function device of the first network, wherein the network selection policy instructs the second network to provide local UAS service information; receiving unmanned aerial system service management (UTM) support information from a second network function device of the second network; selecting the second network according to the network selection policy and the UTM support information; Connecting to the second network function device to receive the local UAS service information from the second network function device.
2. The method according to claim 1, characterized in that The first network is a home network subscribed by the UAS, and the second network is different from the first network.
3. The method according to claim 1 or 2, characterized in that: The second network is part of a network of a base station or part of a network of a cell of the base station.
4. The method according to any one of claims 1 to 3, characterized in that The UTM support information is broadcast by the second network function device.
5. The method according to any one of claims 1 to 4, characterized in that The local UAS service information is multicast or broadcast by the second network function device.
6. The method according to claim 5, characterized in that The second network function device is a base station or a function device based on the Internet Protocol (IP).
7. The method according to any one of claims 1 to 6, characterized in that The local UAS service information is unicast by the second network function device.
8. The method according to any one of claims 1 to 7, characterized in that The UTM support information indicates that the second network function device of the second network supports UTM, and the UTM includes at least one of a UAS identification or a UAS sense and avoidance DAA.
9. The method according to any one of claims 1 to 8, characterized in that The second network function device is a ground base station, and the UAS is at least one of an unmanned aerial vehicle (UAV) or a UAV controller that controls the UAV.
10. The method according to any one of claims 1 to 9, characterized in that The network selection policy includes at least one of a candidate network identifier ID or a candidate DAA ID, and the UTM support information includes a network ID and a DAA network ID of the second network.
11. The method according to claim 10, characterized in that The DAA Network ID indicates that the network is used for UTM and is different from the network ID used to provide any other different non-UAS services.
12. The method according to claim 10, characterized in that The options include: The second network is selected based on the network ID in the UTM support information matching the candidate network ID in the network selection policy and the DAA network ID in the UTM support information matching the candidate DAA ID in the network selection policy.
13. The method according to claim 12, characterized in that The selection is based on the coverage area where the UAS is located and the candidate coverage areas indicated in the UTM support information.
14. The method according to claim 12, characterized in that The UAS provides location information to the second network function device, and the second network function device provides service information customized for the group of joined member devices based on information from the joined member devices in the group, the group including the UAS.
15. The method according to any one of claims 1 to 14, characterized in that The network selection strategy also defines a selection granularity for each network or each cell of the second network.
16. A method, characterized in that include: A second network function device of the second network sends unmanned aerial system service management (UTM) support information to an unmanned aerial system (UAS), the UAS receives a network selection policy from a first network function device of the first network, the network selection policy instructs the second network to provide local UAS service information, and the UAS selects the second network according to the network selection policy and the UTM support information; The second network function device of the second network is connected to the UAS to send the local UAS service information from the second network function device.
17. The method according to claim 16, characterized in that The first network is a home network subscribed by the UAS, and the second network is different from the first network.
18. The method according to claim 16 or 17, characterized in that The second network is part of a network of a base station or part of a network of a cell of the base station.
19. The method according to any one of claims 16 to 18, characterized in that The UTM support information is broadcast by the second network function device.
20. The method according to any one of claims 16 to 19, characterized in that The local UAS service information is multicast or broadcast by the second network function device.
21. The method according to claim 20, characterized in that The second network function device is a base station or a function device based on the Internet Protocol (IP).
22. The method according to any one of claims 16 to 21, characterized in that The local UAS service information is unicast by the second network function device.
23. The method according to any one of claims 16 to 22, characterized in that The UTM support information indicates that the second network function device of the second network supports UTM, and the UTM includes at least one of a UAS identification or a UAS sense and avoidance DAA.
24. The method according to any one of claims 16 to 23, characterized in that The second network function device is a ground base station, and the UAS is at least one of an unmanned aerial vehicle (UAV) or a UAV controller that controls the UAV.
25. The method according to any one of claims 16 to 24, characterized in that The network selection policy includes at least one of a candidate network identifier ID or a candidate DAA ID, and the UTM support information includes a network ID and a DAA network ID of the second network.
26. The method according to claim 25, characterized in that The DAA network ID indicates that the network is used for UTM, and the DAA network ID is different from any one or more network IDs used to provide one or more other different non-UAS services.
27. The method according to claim 25, characterized in that The second network is selected based on the network ID in the UTM support information matching the candidate network ID in the network selection policy and the DAA network ID in the UTM support information matching the candidate DAA ID in the network selection policy.
28. The method according to claim 27, characterized in that The second network is selected based on the coverage area where the UAS is located and the candidate coverage area indicated in the UTM support information.
29. The method according to claim 27, characterized in that The UAS provides location information to the second network function device, wherein the second network function device provides service information customized for the group of joined member devices based on information from the joined member devices in the group, the group including the UAS.
30. The method according to any one of claims 16 to 29, characterized in that The network selection strategy also defines a selection granularity for each network or each cell of the second network.
31. An unmanned aerial system (UAS), characterized in that: include: at least one processor; A non-transitory computer-readable storage medium storing a program which, when executed by the at least one processor, causes the UAS to perform the method according to any one of claims 1 to 15.
32. A second network function device, characterized in that: include: at least one processor; A non-transitory computer-readable storage medium storing a program, which, when executed by the at least one processor, causes the second network function device to perform the method according to any one of claims 15 to 30.
