Method for supporting non-transmission area of unmanned aerial vehicle

Abstract

In one embodiment, a network device includes a processor including an access and mobility management function (AMF) configured to: receive a non-transmission area (NTZ) request, the NTZ request indicating one or more NTZs within a network; starting a WTRU position procedure, wherein the WTRU tracking procedure tracks the location of a target WTRU; determining whether the target WTRU is within the indicated NTZ and a connected mode (e.g., connected mode, idle mode) of the WTRU; transmitting a PDU session deactivation request to the network based on determining that the target WTRU is within the indicated NTZ and a connected mode of the WTRU; transmitting an NTZ implementation notification (the NTZ implementation notification) to the target WTRU; and transmitting the NTZ implementation request (the NTZ implementation request) to the network.

Description

[0001] Cross-reference to related applications This application claims the benefit of U.S. Provisional Application No. 63 / 531,888, filed August 10, 2023, the entire contents of which are incorporated herein by reference. Background Technology

[0002] In addition to the technical requirements for MFCN bands and for spectrum compatibility purposes, certain spectrum operation constraints can be defined. This can be accomplished using no-transmission zones, which can be defined at the national level as geographical areas where radio transmit / receive units (WTRUs) (such as aerospace WTRUs (e.g., UAVs)) are not permitted to operate in a particular frequency band. Additional OOB (Out-of-Band) transmission restrictions specific to aerospace WTRUs can be defined, for example, to avoid interference with other services in some other frequency bands (e.g., to protect MetSat in the 1675-1710 MHz range). These requirements may apply to aerospace WTRUs, depending on their operating frequency band, such as those operating in a specific frequency band and / or a specific channel. In some cases, the operation of aerospace WTRUs also requires corresponding cross-border harmonization agreements.

[0003] A no-transmission zone can be defined as a geographical area in which, for spectrum compatibility purposes, aerospace WTRUs are not permitted to transmit within a given Coordinated MFCN band or a portion thereof. For spectrum compatibility purposes, one or more studies may define a no-transmission zone for aerospace WTRUs operating in the relevant band. A mechanism may be used to ensure that aerospace WTRUs comply with the no-transmission zone. Summary of the Invention

[0004] A network device may include a processor that includes Access and Mobility Management (AMF) functions. The processor may be configured to receive a Non-Transport Zone (NTZ) request. The NTZ request may indicate NTZ information and / or identifiers for one or more NTZs within the network. The NTZ information may include: a geographic area associated with the NTZ, one or more frequency bands, and / or a time period. The NTZ may be a geographic area in which a WTRU is not permitted to transmit via one or more frequency bands. The processor may be configured to initiate a WTRU location procedure. The WTRU location procedure tracks the location of a target WTRU. The WTRU may be an Unmanned Aerial Vehicle (UAV).

[0005] The processor may be configured to: determine whether the target WTRU is within an indicated NTZ. The processor may be configured to: determine whether the target WTRU is in a connected mode (e.g., connected mode) when it is in the geographic area of ​​the NTZ. The processor may be configured to: transmit an NTZ implementation notification based on the determination that the target WTRU is within the indicated NTZ.

[0006] The processor may be configured to: transmit a PDU session deactivation request to the network based on determining that the target WTRU is within an indicated NTZ (e.g., and also based on the WTRU being in a connected mode). The processor may be configured to: transmit an NTZ implementation notification to the target WTRU. The NTZ implementation notification may include an indication that command and control (C2) communication with only the target WTRU is permitted. The processor may be configured to: transmit the NTZ implementation notification to the target WTRU based on determining that the target WTRU is within an indicated NTZ and when the WTRU is in a specific connected mode (e.g., connected mode, idle mode). The NTZ implementation notification may include any combination of indications of one or more NTZs, frequency bands, and / or time periods.

[0007] The processor may be further configured to transmit an NTZ implementation request to the network based on determining that the target WTRU is within an indicated NTZ (e.g., and, in some instances, also based on the WTRU's connection mode (e.g., connected mode)). The NTZ implementation request may include: an identifier of the WTRU (e.g., a target UAV ID), the one or more NTZs, an indication of the associated frequency band, and / or the time period. The processor may be configured to receive the NTZ implementation request from the network. The NTZ implementation request may include modification or cancellation of the NTZ information. In some examples, the processor may be configured to transmit an NTZ implementation notification to a WTRU that is not within an indicated NTZ. The NTZ implementation notification may include an indication of the one or more NTZs.

[0008] The processor may be further configured to: determine whether the target WTRU is within an indicated NTZ and in an idle mode. The processor may be further configured to: based on the determination that the target WTRU is within an indicated NTZ and in an idle mode, transmit an NTZ implementation notification to the target WTRU, the NTZ implementation notification including an indication of one or more NTZs, frequency bands, and time periods. The processor may be further configured to: based on the determination that the target WTRU is within an indicated NTZ and in an idle mode, receive a service request from the target WTRU. The processor may be further configured to: based on the determination that the target WTRU is within an indicated NTZ and in an idle mode, transmit a service rejection message to the target WTRU.

[0009] The Target Wireless Transmitter / Receiver Unit (WTRU) may include a processor. The processor may be configured to receive a Non-Transmission Zone (NTZ) enforcement notification from the network device. The NTZ enforcement notification may include an indication of one or more NTZs, the frequency band, and / or the time period. The processor may be further configured to determine whether the WTRU is within the indicated NTZ. The processor may be further configured to release an RRC connection with the network based on the WTRU being under NTZ control. The processor may be further configured to transmit a service request to the network device based on determining that the WTRU is in an idle mode. The processor may be further configured to receive a service rejection message based on whether the WTRU is within the indicated NTZ. The processor may be further configured to generate an alarm related to the NTZ. The processor may be further configured to transmit the NTZ indication to the controller of the WTRU. Attached Figure Description

[0010] Figure 1A This is a system diagram illustrating an exemplary communication system that can implement one or more of the disclosed embodiments.

[0011] Figure 1B The illustration is based on an embodiment and can be used Figure 1A The diagram shows a system diagram of an exemplary wireless transmit / receive unit (WTRU) used within a communication system.

[0012] Figure 1C The illustration is based on an embodiment and can be used Figure 1A The diagram shows an exemplary radio access network (RAN) and an exemplary core network (CN) used within a communication system.

[0013] Figure 1D The illustration is based on an embodiment and can be used Figure 1AThe diagram shows a further exemplary RAN and a further exemplary CN used within the communication system.

[0014] Figure 2 This is a process diagram illustrating an exemplary implementation of the non-transmission zone (NTZ) in a 5G network. Detailed Implementation

[0015] Figure 1A This is a diagram illustrating an exemplary communication system 100 that can implement one or more of the disclosed embodiments. The communication system 100 may be a multiple access system that provides content, such as voice, data, video, messaging, broadcasting, etc., to multiple wireless users. The communication system 100 enables multiple wireless users to access such content by sharing system resources, including wireless bandwidth. For example, the communication system 100 may employ 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), Zero Tail Unique Word DFT Spread Spectrum OFDM (ZT UW DTS-s OFDM), Unique Word OFDM (UW-OFDM), Resource Block Filtered OFDM, Filter Library Set Multicarrier (FBMC), etc.

[0016] like Figure 1AAs shown, the communication system 100 may include wireless transmit / receive units (WTRUs) 102a, 102b, 102c, 102d, RAN 104 / 113, CN 106 / 115, public switched telephone network (PSTN) 108, Internet 110, and other networks 112. However, it will be appreciated that the disclosed embodiments contemplate any number of WTRUs, base stations, networks, and / or network elements. Each of the WTRUs 102a, 102b, 102c, and 102d may be any type of device configured to operate and / or communicate in a wireless environment. As an example, WTRUs 102a, 102b, 102c, and 102d (any of which may be referred to as a “station” and / or “STA”) may be configured to transmit and / or receive wireless signals and may include user equipment (UE), mobile stations, fixed or mobile subscriber units, subscription-based units, pagers, cellular phones, personal digital assistants (PDAs), smartphones, laptops, netbooks, personal computers, wireless sensors, hotspots or Mi-Fi devices, Internet of Things (IoT) devices, watches or other wearable devices, head-mounted displays (HMDs), vehicles, drones, medical devices and applications (e.g., remote surgery), industrial devices and applications (e.g., robots and / or other wireless devices operating in industrial and / or automated processing chain scenarios), consumer electronics devices, devices operating on commercial and / or industrial wireless networks, etc. Any WTRU in WTRUs 102a, 102b, 102c, and 102d may be interchangeably referred to as a WTRU.

[0017] The communication system 100 may also include base station 114a and / or base station 114b. Each of the base stations 114a and 114b may be any type of device configured to wirelessly interface with at least one of the WTRUs 102a, 102b, 102c, and 102d to facilitate access to one or more communication networks (such as CN 106 / 115, the Internet 110, and / or other networks 112). As an example, base stations 114a and 114b may be base transceivers (BTS), Node-B, eNode B, home Node B, home eNode B, gNB, NR Node B, field controllers, access points (APs), wireless routers, etc. Although base stations 114a and 114b are depicted as single elements, it will be understood that base stations 114a and 114b may include any number of interconnected base stations and / or network elements.

[0018] Base station 114a may be part of RAN 104 / 113, which may also include other base stations and / or network elements (not shown), such as base station controllers (BSCs), radio network controllers (RNCs), relay nodes, etc. Base station 114a and / or base station 114b may be configured to transmit and / or receive radio signals on one or more carrier frequencies, which may be referred to as cells (not shown). These frequencies may be in licensed spectrum, unlicensed spectrum, or a combination of licensed and unlicensed spectrum. A cell may provide coverage of a specific geographic area, which may be relatively fixed or may change over time. A cell may be further divided into cell sectors. For example, the cell associated with base station 114a may be divided into three sectors. Therefore, in one embodiment, base station 114a may include three transceivers, i.e., one transceiver for each sector of the cell. In embodiments, base station 114a may employ multiple-input multiple-output (MIMO) technology and may utilize multiple transceivers for each sector of the cell. For example, beamforming can be used to transmit and / or receive signals in a desired spatial direction.

[0019] Through air interface 116, base stations 114a and 114b can communicate with one or more WTRUs among WTRUs 102a, 102b, 102c, and 102d. Air interface 116 can be any suitable wireless communication link (e.g., radio frequency (RF), microwave, centimeter wave, micrometer wave, infrared (IR), ultraviolet (UV), visible light, etc.). Air interface 116 can be established using any suitable radio access technology (RAT).

[0020] More specifically, as described above, the communication system 100 can be a multiple access system and can employ one or more channel access schemes, such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, etc. For example, base stations 114a and WTRUs 102a, 102b, and 102c in RAN 104 / 113 can implement radio technologies such as Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA), which can use Wideband CDMA (WCDMA) to establish air interfaces 115 / 116 / 117. WCDMA may include communication protocols such as High-Speed ​​Packet Access (HSPA) and / or Evolved HSPA (HSPA+). HSPA may include High-Speed ​​Downlink (DL) Packet Access (HSDPA) and / or High-Speed ​​UL Packet Access (HSUPA).

[0021] In the embodiment, base station 114a and WTRUs 102a, 102b, 102c can implement radio technologies such as evolved UMTS terrestrial radio access (E-UTRA), which can use Long Term Evolution (LTE) and / or LTE-Advanced (LTE-A) and / or LTE-Advanced Pro (LTE-A Pro) to establish air interface 116.

[0022] In the embodiment, base station 114a and WTRUs 102a, 102b, 102c can implement radio technologies such as NR radio access, which can use New Radio (NR) to establish air interface 116.

[0023] In the embodiments, base station 114a and WTRUs 102a, 102b, and 102c can implement multiple radio access technologies. For example, using a dual connectivity (DC) principle, base station 114a and WTRUs 102a, 102b, and 102c can implement both LTE radio access and NR radio access. Therefore, the air interface utilized by WTRUs 102a, 102b, and 102c can be characterized by multiple types of radio access technologies and / or transmissions sent to / from multiple types of base stations (e.g., eNBs and gNBs).

[0024] In other embodiments, base station 114a and WTRUs 102a, 102b, 102c may implement radio technologies such as IEEE 802.11 (i.e., WiFi), IEEE 802.16 (i.e., WiMAX), CDMA2000, CDMA2000 1X, CDMA2000 EV-DO, transitional standard 2000 (IS-2000), transitional standard 95 (IS-95), transitional standard 856 (IS-856), Global System for Mobile Communications (GSM), Enhanced Data Rate GSM Evolution (EDGE), GSMEDGE (GERAN), etc.

[0025] Figure 1ABase station 114b can be, for example, a wireless router, a home Node B, a home eNode B, or an access point, and can utilize any suitable RAT to facilitate wireless connectivity in a local area, such as commercial locations, homes, vehicles, campuses, industrial facilities, air corridors (e.g., used by drones), roads, etc. In one embodiment, base station 114b and WTRUs 102c, 102d can implement radio technologies (such as IEEE 802.11) to establish a wireless local area network (WLAN). In another embodiment, base station 114b and WTRUs 102c, 102d can implement radio technologies (such as IEEE 802.15) to establish a wireless personal area network (WPAN). In yet another embodiment, base station 114b and WTRUs 102c, 102d can utilize cellular-based RATs (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, LTE-A Pro, NR, etc.) to establish picocells or femtocells. Figure 1A As shown, base station 114b may have a direct connection to the Internet 110. Therefore, base station 114b may not require access to the Internet 110 via CN 106 / 115.

[0026] RAN 104 / 113 can communicate with CN 106 / 115, which can be any type of network configured to provide voice, data, application, and / or Voice over Internet Protocol (VoIP) services to one or more WTRUs of WTRUs 102a, 102b, 102c, and 102d. Data may have varying Quality of Service (QoS) requirements, such as different throughput requirements, latency requirements, fault tolerance requirements, reliability requirements, data throughput requirements, mobility requirements, etc. CN 106 / 115 can provide call control, billing services, mobile location-based services, prepaid telephony, internet connectivity, video distribution, etc., and / or perform advanced security functions such as user authentication. Although not explicitly stated... Figure 1A As shown, but as will be understood, RAN 104 / 113 and / or CN 106 / 115 can communicate directly or indirectly with other RANs that use the same RAT as or a different RAT than RAN 104 / 113. For example, in addition to connecting to RAN 104 / 113, which may utilize NR radio technology, CN 106 / 115 can also communicate with another RAN (not shown) that uses GSM, UMTS, CDMA 2000, WiMAX, E-UTRA, or WiFi radio technology.

[0027] CN 106 / 115 can also serve as a gateway for WTRU 102a, 102b, 102c, 102d to access PSTN 108, the Internet 110, and / or other networks 112. PSTN 108 may include a circuit-switched telephone network providing Common Old-Style Telephone Service (POTS). The Internet 110 may include a globally interconnected computer network and equipment system using common communication protocols such as Transmission Control Protocol (TCP), User Datagram Protocol (UDP), and / or Internet Protocol (IP) from the TCP / IP Internet Protocol suite. Network 112 may include wired and / or wireless communication networks owned and / or operated by other service providers. For example, network 112 may include another CN connected to one or more RANs, which may use the same RAT as RAN 104 / 113 or a different RAT.

[0028] Some or all of the WTRUs 102a, 102b, 102c, and 102d in communication system 100 may include multi-mode capability (e.g., WTRUs 102a, 102b, 102c, and 102d may include multiple transceivers for communicating with different wireless networks on different wireless links). For example, Figure 1A The WTRU 102c shown can be configured to communicate with base station 114a, which can employ cellular-based radio technology, and with base station 114b, which can employ IEEE 802 radio technology.

[0029] Figure 1B This is a system diagram illustrating an exemplary WTRU 102. (Example:) Figure 1B As shown, WTRU 102 may include a processor 118, a transceiver 120, a transmit / receive element 122, a speaker / microphone 124, a keypad 126, a display / touchpad 128, non-removable memory 130, removable memory 132, a power supply 134, a Global Positioning System (GPS) chipset 136, and / or other peripheral devices 138, etc. It will be appreciated that WTRU 102 may include any sub-combination of the foregoing elements while remaining consistent with the embodiments.

[0030] Processor 118 may be a general-purpose processor, a special-purpose processor, a conventional processor, a digital signal processor (DSP), multiple microprocessors, one or more microprocessors associated with a DSP core, a controller, a microcontroller, an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) circuit, any other type of integrated circuit (IC), a state machine, etc. Processor 118 may perform signal decoding, data processing, power control, input / output processing, and / or any other functions that enable WTRU 102 to operate in a wireless environment. Processor 118 may be coupled to transceiver 120, and transceiver 120 may be coupled to transmit / receive element 122. Although... Figure 1B While the processor 118 and transceiver 120 are depicted as separate components, it will be understood that the processor 118 and transceiver 120 may be integrated together in an electronic package or chip.

[0031] Transmitting / receiving element 122 may be configured to transmit signals to or receive signals from a base station (e.g., base station 114a) via air interface 116. For example, in one embodiment, transmitting / receiving element 122 may be an antenna configured to transmit and / or receive RF signals. In embodiments, for example, transmitting / receiving element 122 may be a transmitter / detector configured to transmit and / or receive IR, UV, or visible light signals. In another embodiment, transmitting / receiving element 122 may be configured to transmit and / or receive both RF and optical signals. It will be appreciated that transmitting / receiving element 122 may be configured to transmit and / or receive any combination of wireless signals.

[0032] Although the transmitting / receiving element 122 is in Figure 1B While depicted as a single element, WTRU 102 may include any number of transmit / receive elements 122. More specifically, WTRU 102 may employ MIMO technology. Thus, in one embodiment, WTRU 102 may include two or more transmit / receive elements 122 (e.g., multiple antennas) for transmitting and receiving wireless signals via air interface 116.

[0033] Transceiver 120 can be configured to modulate signals to be transmitted by transmitting / receiving element 122 and demodulate signals received by transmitting / receiving element 122. As described above, WTRU 102 may have multi-mode capability. Therefore, transceiver 120 may include multiple transceivers to enable WTRU 102 to communicate via various RATs (such as, for example, NR and IEEE 802.11).

[0034] The processor 118 of WTRU 102 can be coupled to a speaker / microphone 124, a keypad 126, and / or a display / touchpad 128 (e.g., a liquid crystal display (LCD) unit or an organic light-emitting diode (OLED) display unit), and can receive user input data from the speaker / microphone 124, keypad 126, and / or display / touchpad 128. The processor 118 can also output user data to the speaker / microphone 124, keypad 126, and / or display / touchpad 128. Additionally, the processor 118 can access information from any type of suitable memory (such as non-removable memory 130 and / or removable memory 132) and store data in said memory. Non-removable memory 130 may include random access memory (RAM), read-only memory (ROM), a hard disk, or any other type of memory storage device. Removable memory 132 may include a subscriber identity module (SIM) card, a memory stick, a secure digital storage (SD) card, etc. In other embodiments, the processor 118 may access information from memory that is not physically located on the WTRU 102 (such as on a server or home computer (not shown)) and store the data in the memory.

[0035] The processor 118 may receive power from the power supply 134 and may be configured to distribute and / or control power to other components in the WTRU 102. The power supply 134 may be any suitable device for powering the WTRU 102. For example, the power supply 134 may include one or more dry cell battery packs (e.g., nickel-cadmium (NiCd), nickel-zinc (NiZn), nickel metal hydride (NiMH), lithium-ion (Li-ion), etc.), solar cells, fuel cells, etc.

[0036] The processor 118 may also be coupled to a GPS chipset 136, which may be configured to provide location information (e.g., longitude and latitude) about the current location of the WTRU 102. In addition to or alternative to information from the GPS chipset 136, the WTRU 102 may receive location information via air interface 116 from base stations (e.g., base stations 114a, 114b) and / or determine its location based on the timing of signals received from two or more nearby base stations. It will be appreciated that the WTRU 102 may acquire location information using any suitable location determination method while remaining consistent with the embodiments.

[0037] The processor 118 may be further coupled to other peripheral devices 138, which may include one or more software and / or hardware modules providing additional features, functions, and / or wired or wireless connectivity. For example, peripheral devices 138 may include accelerometers, electronic compasses, satellite transceivers, digital cameras (for photos and / or videos), Universal Serial Bus (USB) ports, vibration devices, television transceivers, hands-free headsets, Bluetooth® modules, frequency modulation (FM) radio units, digital music players, media players, video game player modules, internet browsers, virtual reality and / or augmented reality (VR / AR) devices, activity trackers, etc. Peripheral devices 138 may include one or more sensors, which may be one or more of the following: gyroscopes, accelerometers, Hall effect sensors, magnetometers, orientation sensors, proximity sensors, temperature sensors, time sensors, geolocation sensors, altimeters, light sensors, touch sensors, magnetometers, barometers, gesture sensors, biometric sensors, and / or humidity sensors.

[0038] WTRU 102 may include a full-duplex radio for which transmission and reception of some or all of the signals (e.g., associated with a specific subframe of both UL (e.g., for transmission) and downlink (e.g., for reception)) may be concurrent and / or simultaneous. The full-duplex radio may include an interference management unit 139 to reduce and / or substantially eliminate self-interference via hardware (e.g., a choke) or via signal processing (e.g., a separate processor (not shown) or via processor 118). In an embodiment, WTRU 102 may include a half-duplex radio for which transmission and reception of some or all of the signals (e.g., associated with a specific subframe of either UL (e.g., for transmission) or downlink (e.g., for reception)) may occur.

[0039] Figure 1C This is a system diagram illustrating RAN 104 and CN 106 according to an embodiment. As described above, RAN 104 may employ E-UTRA radio technology to communicate with WTRUs 102a, 102b, and 102c via air interface 116. RAN 104 may also communicate with CN 106.

[0040] RAN 104 may include eNode-Bs 160a, 160b, and 160c, but it will be understood that RAN 104 may include any number of eNode-Bs while remaining consistent with the embodiments. Each eNode-B 160a, 160b, and 160c may include one or more transceivers for communicating with WTRUs 102a, 102b, and 102c via air interface 116. In one embodiment, eNode-Bs 160a, 160b, and 160c may implement MIMO technology. Therefore, eNode-B 160a may, for example, use multiple antennas to transmit radio signals to and / or receive radio signals from WTRU 102a.

[0041] Each of the eNode-B 160a, 160b, and 160c can be associated with a specific cell (not shown) and can be configured to handle radio resource management decisions, handover decisions, and scheduling of users in the UL and / or DL, etc. Figure 1C As shown, eNode-B 160a, 160b, and 160c can communicate with each other via the X2 interface.

[0042] Figure 1C CN 106 shown may include a Mobility Management Entity (MME) 162, a Serving Gateway (SGW) 164, and a Packet Data Network (PDN) Gateway (or PGW) 166. Although each of the preceding elements is depicted as part of CN 106, it will be understood that any of these elements may be owned and / or operated by an entity other than a CN operator.

[0043] The MME 162 can be connected to each of the eNode-Bs 162a, 162b, and 162c in RAN 104 via the S1 interface and can be used as a control node. For example, the MME 162 can be responsible for authenticating users of WTRUs 102a, 102b, and 102c, activating / deactivating bearers, selecting a specific serving gateway during the initial attachment of WTRUs 102a, 102b, and 102c, etc. The MME 162 can provide control plane functions for handover between RAN 104 and other RANs (not shown) employing other radio technologies such as GSM and / or WCDMA.

[0044] The SGW 164 can be connected to each of the eNode Bs 160a, 160b, and 160c in RAN 104 via the S1 interface. The SGW 164 can typically route and forward user data packets to / from WTRUs 102a, 102b, and 102c. The SGW 164 can perform other functions such as anchoring the user plane during inter-eNode B handover, triggering paging when DL data is available for WTRUs 102a, 102b, and 102c, and managing and storing the context of WTRUs 102a, 102b, and 102c.

[0045] SGW 164 can be connected to PGW 166, which provides WTRU 102a, 102b, 102c with access to packet-switched networks (such as the Internet 110) to facilitate communication between WTRU 102a, 102b, 102c and IP-enabled devices.

[0046] CN 106 can facilitate communication with other networks. For example, CN 106 can provide WTRUs 102a, 102b, and 102c with access to a circuit-switched network (such as PSTN 108) to facilitate communication between WTRUs 102a, 102b, and 102c and traditional landline communication equipment. For example, CN 106 may include an IP gateway (e.g., an IP Multimedia Subsystem (IMS) server), or can communicate with said IP gateway, which serves as an interface between CN 106 and PSTN 108. Additionally, CN 106 can provide WTRUs 102a, 102b, and 102c with access to other networks 112, which may include other wired and / or wireless networks owned and / or operated by other service providers.

[0047] Although WTRU is Figure 1A-1D While described as a wireless terminal, it is envisioned that, in some representative embodiments, such a terminal may (e.g., temporarily or permanently) use a wired communication interface with a communication network.

[0048] In a representative embodiment, the other network 112 may be a WLAN.

[0049] A WLAN in an Infrastructure Basic Services Set (BSS) mode may have an Access Point (AP) for the BSS and one or more Stations (STAs) associated with the AP. The AP may access a Distribution System (DS) or another type of wired / wireless network, or have an interface with a Distribution System (DS) or another type of wired / wireless network that carries traffic into and / or out of the BSS. Traffic originating outside the BSS destined for a STA can be delivered to the AP via the AP. Traffic originating from a STA destined for a destination outside the BSS can be sent to the AP for delivery to the appropriate destination. Traffic between STAs within the BSS can be transmitted via the AP, for example, where a source STA can send traffic to the AP and the AP can deliver the traffic to the destination STA. Traffic between STAs within the BSS may be considered and / or referred to as peer-to-peer traffic. With Direct Link Establishment (DLS), peer-to-peer traffic can be transmitted between source and destination STAs (e.g., directly between source and destination STAs). In some representative embodiments, the DLS may use 802.11e DLS or 802.11z Tunneled DLS (TDLS). WLANs using Standalone BSS (IBSS) mode may not have access points (APs), and STAs within the IBSS or using the IBSS (e.g., all STAs within a STA) can communicate directly with each other. IBSS communication mode may sometimes be referred to herein as "ad-hoc" communication mode.

[0050] When using 802.11ac infrastructure operating mode or a similar operating mode, the AP can transmit beacons on a fixed channel, such as a primary channel. The primary channel can be of fixed width (e.g., a bandwidth of 20 MHz) or dynamically set via signaling. The primary channel can be the operating channel of the BSS and can be used by the STA to establish a connection with the AP. In some representative embodiments, such as in an 802.11 system, carrier-sense multiple access (CSMA / CA) with collision avoidance can be implemented. For CSMA / CA, each STA (including the AP) can sense the primary channel. If the primary channel is sensed / detected and / or determined to be busy by a particular STA, that particular STA can back off. In a given BSS, one STA (e.g., only one station) can transmit at any given time.

[0051] For example, a high-throughput (HT) STA can communicate using a 40 MHz wide channel by combining a primary 20 MHz channel with adjacent or non-adjacent 20 MHz channels.

[0052] Very High Throughput (VHT) STAs can support channels with widths of 20 MHz, 40 MHz, 80 MHz, and / or 160 MHz. 40 MHz and / or 80 MHz channels can be formed by combining adjacent 20 MHz channels. A 160 MHz channel can be formed by combining eight adjacent 20 MHz channels, or by combining two non-adjacent 80 MHz channels (this can be referred to as an 80+80 configuration). For the 80+80 configuration, after channel coding, data is passed through a segment resolver, which divides the data into two streams. Inverse Fast Fourier Transform (IFFT) processing and time-domain processing can be performed separately on each stream. The streams can be mapped onto two 80 MHz channels, and the data can be transmitted by the transmitting STA. At the receiver of the receiving STA, the above operations for the 80+80 configuration can be reversed, and the combined data can be sent to the Media Access Control (MAC).

[0053] Sub-1 GHz operating modes are supported by 802.11af and 802.11ah. In 802.11af and 802.11ah, the channel operating bandwidth and carrier are reduced compared to those used in 802.11n and 802.11ac. 802.11af supports 5 MHz, 10 MHz, and 20 MHz bandwidths in the TV white space (TVWS) spectrum, and 802.11ah supports 1 MHz, 2 MHz, 4 MHz, 8 MHz, and 16 MHz bandwidths using non-TVWS spectrum. According to a representative embodiment, 802.11ah may support instrument-type control / machine-type communication, such as MTC devices in macro coverage areas. MTC devices may have certain capabilities, such as limited capabilities, including support (e.g., only support) certain and / or limited bandwidths. MTC devices may include batteries with a battery life exceeding a threshold (e.g., to maintain a very long battery life).

[0054] WLAN systems that support multiple channels and channel bandwidths (such as 802.11n, 802.11ac, 802.11af, and 802.11ah) include channels that can be designated as primary channels. The primary channel may have a bandwidth equal to the maximum common operating bandwidth supported by all STAs in the BSS. The bandwidth of the primary channel may be set and / or limited by the STA that supports the minimum bandwidth operating mode among all STAs operating in the BSS. In the example of 802.11ah, for STAs that support (e.g., only support) the 1MHz mode (e.g., MTC type devices), the primary channel may still be 1 MHz wide, even if the AP and other STAs in the BSS support 2 MHz, 4 MHz, 8 MHz, 16 MHz, and / or other channel bandwidth operating modes. Carrier sensing and / or Network Assignment Vector (NAV) settings may depend on the status of the primary channel. If, for example, the primary channel is busy due to a STA (that only supports the 1 MHz operating mode) transmitting to the AP, the entire available band may be considered busy even if most of the band remains idle and may be available.

[0055] In the United States, the available frequency bands for 802.11ah are from 902 MHz to 928 MHz. In South Korea, the available frequency bands are from 917.5 MHz to 923.5 MHz. In Japan, the available frequency bands are from 916.5 MHz to 927.5 MHz. Depending on the country code, the total bandwidth available for 802.11ah is 6 MHz to 26 MHz.

[0056] Figure 1D This is a system diagram illustrating RAN 113 and CN 115 according to an embodiment. As described above, RAN 113 may employ NR radio technology to communicate with WTRUs 102a, 102b, and 102c via air interface 116. RAN 113 may also communicate with CN 115.

[0057] RAN 113 may include gNBs 180a, 180b, and 180c, but it will be understood that RAN 113 may include any number of gNBs while remaining consistent with the embodiments. gNBs 180a, 180b, and 180c may each include one or more transceivers for communicating with WTRUs 102a, 102b, and 102c via air interface 116. In one embodiment, gNBs 180a, 180b, and 180c may implement MIMO technology. For example, gNBs 180a and 180b may utilize beamforming to transmit signals to and / or receive signals from gNBs 180a, 180b, and 180c. Therefore, gNB 180a may, for example, use multiple antennas to transmit radio signals to and / or receive radio signals from WTRU 102a. In embodiments, gNBs 180a, 180b, and 180c can implement carrier aggregation technology. For example, gNB 180a can transmit multiple component carriers to WTRU 102a (not shown). A subset of these component carriers may be on unlicensed spectrum, while the remaining component carriers may be on licensed spectrum. In embodiments, gNBs 180a, 180b, and 180c can implement Coordinated Multipoint (CoMP) technology. For example, WTRU 102a can receive coordinated transmissions from gNBs 180a and 180b (and / or gNB 180c).

[0058] Using transmissions associated with scalable digital theory, WTRU 102a, 102b, and 102c can communicate with gNB 180a, 180b, and 180c. For example, OFDM symbol spacing and / or OFDM subcarrier spacing can vary for different transmissions, different cells, and / or different portions of the radio transmission spectrum. Using various or scalable length subframes or transmission time intervals (TTIs) (e.g., containing a varying number of OFDM symbols and / or an absolute time of continuously varying length), WTRU 102a, 102b, and 102c can communicate with gNB 180a, 180b, and 180c.

[0059] gNBs 180a, 180b, and 180c can be configured to communicate with WTRUs 102a, 102b, and 102c in standalone and / or non-standalone configurations. In standalone configuration, WTRUs 102a, 102b, and 102c can communicate with gNBs 180a, 180b, and 180c without also accessing other RANs (e.g., eNode-Bs 160a, 160b, and 160c). In standalone configuration, WTRUs 102a, 102b, and 102c can utilize one or more gNBs from gNBs 180a, 180b, and 180c as mobility anchors. In standalone configuration, using signals in unlicensed frequency bands, WTRUs 102a, 102b, and 102c can communicate with gNBs 180a, 180b, and 180c. In a non-standalone configuration, WTRUs 102a, 102b, and 102c can communicate with / connect to gNBs 180a, 180b, and 180c, while also communicating with / connecting to another RAN, such as eNode-Bs 160a, 160b, and 160c. For example, WTRUs 102a, 102b, and 102c can implement DC principles to communicate substantially simultaneously with one or more gNBs 180a, 180b, and 180c and one or more eNode-Bs 160a, 160b, and 160c. In a non-standalone configuration, eNode-B 160a, 160b, and 160c can be used as mobility anchors for WTRU 102a, 102b, and 102c, and gNB 180a, 180b, and 180c can provide additional coverage and / or throughput for servicing WTRU 102a, 102b, and 102c.

[0060] Each gNB in ​​gNBs 180a, 180b, and 180c can be associated with a specific cell (not shown) and can be configured to handle radio resource management decisions, handover decisions, user scheduling in UL and / or DL, network slicing support, dual connectivity, interoperability between NR and E-UTRA, routing of user plane data to User Plane Functions (UPFs) 184a and 184b, routing of control plane information to Access and Mobility Management Functions (AMFs) 182a and 182b, etc. Figure 1D As shown, gNB180a, 180b, and 180c can communicate with each other via the Xn interface.

[0061] Figure 1DThe CN 115 shown may include at least one AMF 182a, 182b, at least one UPF 184a, 184b, at least one Session Management Function (SMF) 183a, 183b, and possibly a Data Network (DN) 185a, 185b. Although each of the foregoing elements is depicted as part of the CN 115, it will be understood that any of these elements may be owned and / or operated by an entity other than a CN operator.

[0062] AMF 182a and 182b can be connected to one or more gNBs (gNBs) 180a, 180b, and 180c in RAN 113 via the N2 interface and can be used as control nodes. For example, AMF 182a and 182b can be responsible for authenticating users of WTRU 102a, 102b, and 102c, supporting network slices (e.g., handling different PDU sessions with different requirements), selecting specific SMF 183a and 183b, managing registration areas, terminating NAS signaling, mobility management, etc. Network slices can be used by AMF 182a and 182b to customize CN support for WTRU 102a, 102b, and 102c based on the type of services utilized by WTRU 102a, 102b, and 102c. For example, different network slices can be established for different use cases, such as services relying on Ultra Reliable Low Latency (URLLC) access, services relying on Enhanced Massive Mobile Broadband (eMBB) access, and services for Machine Type Communication (MTC) access. AMF 162 can provide control plane functions for switching between RAN 113 and other RANs (not shown) that employ other radio technologies, such as LTE, LTE-A, LTE-A Pro, and / or non-3GPP access technologies such as WiFi.

[0063] SMF 183a and 183b can be connected to AMF 182a and 182b in CN 115 via the N11 interface. SMF 183a and 183b can also be connected to UPF 184a and 184b in CN 115 via the N4 interface. SMF 183a and 183b can select and control UPF 184a and 184b, and configure the routing of services through UPF 184a and 184b. SMF 183a and 183b can perform other functions, such as managing and allocating WTRU IP addresses, managing PDU sessions, controlling policy enforcement and QoS, and providing downlink data notifications. PDU session types can be IP-based, non-IP-based, or Ethernet-based.

[0064] UPF 184a and 184b can be connected via the N3 interface to one or more gNBs (gNBs) 180a, 180b, and 180c in RAN 113. This provides WTRU 102a, 102b, and 102c with access to packet-switched networks (such as the Internet 110) to facilitate communication between WTRU 102a, 102b, 102c and IP-enabled devices. UPF 184 and 184b can perform other functions such as routing and forwarding packets, enforcing user plane policies, supporting multi-homed PDU sessions, handling user plane QoS, buffering downlink packets, and providing mobility anchoring.

[0065] CN 115 can facilitate communication with other networks. For example, CN 115 may include an IP gateway (e.g., an IP Multimedia Subsystem (IMS) server), or may communicate with said IP gateway, which serves as an interface between CN 115 and PSTN 108. Additionally, CN 115 may provide WTRUs 102a, 102b, and 102c with access to other networks 112, which may include other wired and / or wireless networks owned and / or operated by other service providers. In one embodiment, WTRUs 102a, 102b, and 102c can be connected to DNs 185a and 185b via UPFs 184a and 184b, through their N3 interfaces and the N6 interface between UPFs 184a and 184b and local data networks (DNs) 185a and 185b.

[0066] Considering Figure 1A-1D and Figure 1A-1D The corresponding descriptions herein regarding WTRU 102a-d, base station 114a-b, eNode-B 160a-c, MME 162, SGW 164, PGW 166, gNB 180a-c, AMF 182a-ab, UPF 184a-b, SMF183a-b, DN 185a-b, and / or one or more other devices described herein, and the functions described herein, one or more of the functions described herein, may be performed by one or more emulation devices (not shown). An emulation device may be one or more devices configured to emulate one or more of the functions described herein. For example, an emulation device may be used to test other devices and / or simulate network and / or WTRU functions.

[0067] The simulation device may be designed to perform one or more tests on other devices in a laboratory environment and / or in a carrier network environment. For example, while being fully or partially implemented and / or deployed as part of a wired and / or wireless communication network, the one or more simulation devices may perform one or more or all of the functions to test other devices within the communication network. While being temporarily implemented / deployed as part of a wired and / or wireless communication network, the one or more simulation devices may perform one or more or all of the functions. The simulation device may be directly coupled to another device for testing purposes and / or may use over-the-air wireless communication to perform the tests.

[0068] While not implemented / deployed as part of a wired and / or wireless communication network, the one or more emulation devices may perform the one or more functions (including all functions). For example, the emulation devices may be utilized in test scenarios in test laboratories and / or non-deployed (e.g., test) wired and / or wireless communication networks to perform testing of one or more components. The one or more emulation devices may be test rigs. Wireless communication via direct RF coupling and / or through an RF circuit system (e.g., the RF circuit system may include one or more antennas) may be used by the emulation devices to transmit and / or receive data.

[0069] Any description of the WTRU described herein is equally applicable to the UAV (or vice versa). For example, the WTRU may be configured to perform any process or procedure described herein as performed by the UAV (or vice versa).

[0070] A no-transmission zone (NTZ) defined for a single UAV or a group of UAVs can cause problems within a wireless network. NTZ implementation cannot rely solely on the UAV itself. The Radio Access Network (RAN) ensures that UL transmission resources are correctly scheduled for the target UAV; for example, to comply with NTZ requirements, the UAV is provided with RRC configuration. Many details exist regarding how the wireless network is involved in implementing NTZ.

[0071] Such details may include how the wireless network ensures that the NTZ is correctly implemented in the UAV and / or how the wireless network ensures that the UAV does not transmit within the designated NTZ. For UAVs under NTZ control, Uu communication can be securely controlled because the network schedules UL transmission resources. Uncooperative UAVs may perform (one or more) radio transmissions in frequency bands that are not permitted (e.g., for side link communication). A mechanism may be provided to monitor illegal transmissions within the NTZ.

[0072] Such details could further include how the wireless network monitors unauthorized transmissions from non-cooperative UAVs within the NTZ and / or what countermeasures can be taken. Another question might be: how to maintain necessary critical communications (e.g., C2 communications) for the security and safety of UAVs within the NTZ.

[0073] NTZ can be implemented in a wireless network. The core network (e.g., the Unmanned Aircraft System (UAS) Network Function (UAS NF) in a 5G core network) can receive requests from the UAS Service Provider (USS) / Unmanned Aircraft System Traffic Management (UTM) to implement one or more NTZs.

[0074] The request may include identifiers of one or more UAVs (e.g., a General Public Subscription Identifier (GPSI) or a Civil Aviation Administration (CAA) level UAV ID), and the designated NTZ may be applied to the one or more UAVs. The request may also be applied to one or more (e.g., all) UAVs controlled by the USS / UTM without specifying the affected UAV identifiers. The UAS NF can identify one or more (e.g., all) corresponding UAVs belonging to the USS / UTM that issued the request.

[0075] The request may include NTZ information. NTZ information may include a defined NTZ or a list of defined NTZs. NTZs may be defined by geographic coordinates or civil codes. For example, in some cases, an NTZ may be a geographic area where the WTRU is not permitted to transmit via one or more frequency bands.

[0076] For one or more NTZs, NTZ information may include frequency bands or spectrums where UAVs are not permitted to transmit. When UAVs are (e.g., not permitted to transmit on any frequency at all), no specific frequency band can be specified.

[0077] For one or more NTZs, the NTZ information may include the time period during which the NTZ can be applied. If no time period is specified, the NTZ should be considered to be implemented immediately until it is canceled or updated.

[0078] For one or more NTZs, NTZ information may include the type of communication exempted in the NTZ (e.g., C2 communication, direct C2 communication, short-range side link communication).

[0079] Upon receiving an NTZ implementation request, the UAS NF can perform one or more actions. For example, if no specific UAV identifier is specified in the request, the UAS NF can identify one or more (e.g., all) corresponding UAVs belonging to the USS / UTM that issued the request.

[0080] UAS NF can store the content of the NTZ implementation request in the context of the affected UAV.

[0081] For example, with the assistance of other NFs or based on pre-defined information, the UAS NF can locate the area (e.g., cell, tracking area, etc.) in the wireless network that corresponds to the NTZ defined in the request.

[0082] UAS NF can initiate a UAV tracking procedure to monitor whether a UAV has entered the designated NTZ.

[0083] The UAS NF can locate the Service Access and Mobility Management Function (AMF) of the affected UAV and forward the NTZ enforcement request to the Service AMF. The UAS NF can forward the request to the Service AMF immediately after receiving the request from the USS / UTM, or it can forward the request to the Service AMF after the UAS NF has detected that the affected UAV has entered the NTZ.

[0084] Upon receiving an NTZ implementation request from a UAV, the Service AMF may perform one or more actions. The NTZ implementation request may include the identifier of one or more UAVs (e.g., a General Public Subscription Identifier (GPSI) or a Civil Aviation Administration (CAA) level UAVID), and the designated NTZ may be applied to said one or more UAVs. The NTZ implementation request may also be applied to one or more (e.g., all) UAVs controlled by the USS / UTM without specifying the affected UAV identifier. The AMF may identify one or more (e.g., all) corresponding UAVs belonging to the USS / UTM that issued the request. Furthermore, the NTZ implementation request may include NTZ information, such as that described herein.

[0085] The AMF service can initiate a WTRU location procedure to obtain the current location of the UAV and determine whether the UAV is within the NTZ. As long as the UAV is under NTZ control, the AMF can maintain monitoring of the WTRU location. For example, based on a request to implement NTZ, the AMF can determine the WTRU's location. Based on the determined WTRU location, the AMF can determine that the WTRU is near the NTZ. If the WTRU is determined to be near the NTZ, the AMF can send a message to the WTRU including at least a portion of NTZ information and / or an indication that the WTRU is under NTZ control.

[0086] When the UAV is in the NTZ and in connected mode, the serving AMF can instruct the SMF to disable or suspend one, several, or all PDU sessions of the WTRU. For example, if the NTZ request indicates that the UAV is not allowed to transmit on any frequency and C2 communication (e.g., C2 communication only) is exempted, the AMF can disable one or more (e.g., all) PDU sessions other than those for C2 communication. If the PDU sessions for C2 communication are also disabled, the AMF can trigger the UAV's procedures to switch C2 communication to direct C2 communication, i.e., C2 communication via PC5.

[0087] When the UAV is in the NTZ and in connected mode, the serving AMF can notify the serving RAN that the UAV is under NTZ control. The AMF can also notify the RAN of frequency bands where the UAV is not permitted to transmit (or where there is no transmission on any frequency). The RAN should avoid scheduling UL transmissions on those frequency bands. If the UAV is not permitted to transmit on any frequency band, the RAN can release the RRC connection and notify the WTRU that the connection has been released due to NTZ control.

[0088] When the UAV is in NTZ and in connected mode, the serving AMF can instruct the SMF to buffer downlink data that may cause the UAV to respond using UL transmission.

[0089] When the UAV is in the NTZ and in idle mode, the AMF may notify the UAV (e.g., via NAS signaling) that the UAV is in the NTZ. For example, the AMF may send a message to the UAV that includes at least a portion of the NTZ information and / or includes an indication that the WTRU is under NTZ control. The AMF may notify the UAV (e.g., via NAS signaling) that communication is restricted due to NTZ control. For example, the AMF may notify the UAV that C2 communication (e.g., C2 communication only) is permitted. Alternatively, if C2 communication is not exempted, the UAV may switch to a direct C2 communication method. The AMF may also notify the UAV of the NTZ area and the duration of the NTZ, so that the UAV can retry communication when it is outside the NTZ. The UAV may also forward NTZ information to its controller.

[0090] When the UAV is in the NTZ and in idle mode, the AMF can reject a full service request or registration request from the UAV. The AMF can also reject the activation of some PDU sessions from the "List of PDU Sessions to be Activated" in the service request. For example, if the NTZ enforcement request indicates that C2 communication (e.g., C2 communication only) can be exempted from NTZ control, then one or more (e.g., all) PDU sessions other than the PDU sessions for C2 communication can be rejected.

[0091] If the UAV is not in an NTZ, the AMF can notify the UAV about potential NTZs (e.g., neighboring or in the UAV's trajectory) via NAS signaling, so if authorized by the USS / UTM, the UAV application can manipulate the UAV to avoid NTZs. The UAV can also forward NTZ information to its controller.

[0092] If a UAV performs a handover and switches to a new serving RAN, the source RAN that has received the NTZ implementation request can pass the NTZ implementation information to the target RAN that can continue to implement NTZ. When a UAV changes its serving AMF due to mobility, the old serving AMF that has received the NTZ implementation request can pass the NTZ implementation information to the new serving AMF that can continue to implement NTZ.

[0093] Figure 2 This is a process diagram illustrating an exemplary call flow 200 for implementing a non-transport zone (NTZ) in a 5G network.

[0094] In step 1, the UAS NF can receive NTZ implementation notifications from the USS / UTM. The NTZ implementation notification message may include one or more target UAV IDs, one or more NTZs, and one or more frequency bands and / or time periods associated with the NTZ. The NTZ implementation notification message may include identifiers of one or more UAVs (e.g., General Public Subscription Identifier (GPSI) or Civil Aviation Authority (CAA) level UAV IDs), and the designated NTZ can be applied to said one or more UAVs.

[0095] For example, as described above, an NTZ implementation notification message may include NTZ information. NTZ information may include a defined NTZ or a list of defined NTZs. NTZs may be defined by geographic coordinates or civil codes. For example, in some examples, an NTZ may be a geographic area where WTRUs are not permitted to transmit via one or more frequency bands. For one or more NTZs, NTZ information may include frequency bands or spectrum where UAVs are not permitted to transmit. When UAVs (e.g., not at all) are not permitted to transmit on any frequency, no specific frequency band may be specified. For one or more NTZs, NTZ information may include the time period during which the NTZ can be applied. If no time period is specified, it may be considered that the NTZ should be implemented immediately until it is canceled or updated. For one or more NTZs, NTZ information may include the types of communication exempted in the NTZ (e.g., C2 communication, direct C2 communication, short-range sidelink communication).

[0096] In step 2, the UAS NF can initiate a UAV tracking procedure to monitor whether a UAV has entered one or more NTZs as defined in the NTZ implementation notification.

[0097] In step 3, the UAS NF may send (e.g., forward) an NTZ enforcement request to the AMF. The UAS NF may determine that the AMF is the serving AMF of the affected UAV. After receiving the request from the USS / UTM, the UAS NF may immediately forward the request to the serving AMF. After the UAS NF has detected that the affected UAV has entered one or more NTZs, the UAS NF may forward the request to the serving AMF.

[0098] In step 4, the AMF can initiate a WTRU location procedure. The service AMF can initiate a WTRU location procedure to obtain the current location of the UAV and / or determine whether the UAV is within one or more NTZs. As long as the UAV is under NTZ control, the AMF can continue to monitor the WTRU location.

[0099] In step 5, the AMF can determine whether the target UAV is within one or more NTZs. As described herein, if the WTRU is determined to be near an NTZ, the AMF can send a message to the WTRU, wherein the first message may include at least a portion of NTZ information and / or an indication that the WTRU is under NTZ control.

[0100] In 6a, if the UAV is within the NTZ and in connected mode, the serving AMF can transmit a PDU session deactivation request to the SMF / UPF. The request may include deactivation of one, several, or all PDU sessions of the target WTRU.

[0101] In 7a, when the UAV is within the NTZ and in connected mode, the AMF can transmit an NTZ implementation notification with an indication of the NTZ to the UAV. The NTZ implementation notification can indicate any combination of NTZ information, such as one or more NTZs, frequency bands, and / or time periods.

[0102] In 8a, when the UAV is within the NTZ and in connected mode, the AMF can transmit an NTZ implementation request to the RAN. The NTZ implementation request may indicate the target UAV ID, one or more NTZs, frequency band, and / or time period.

[0103] In 9a, when the UAV is within the NTZ and in connected mode, the RAN can release the RRC connection and notify the WTRU that the connection has been released due to NTZ control.

[0104] In 6b, if a UAV is within an NTZ and in idle mode, the AMF can transmit an NTZ implementation notification to the UAV within the one or more NTZs. The NTZ implementation notification can indicate one or more NTZs, frequency bands, and / or time periods.

[0105] In 7b, when the UAV is within the NTZ and in idle mode, the AMF can receive service requests from the UAV. In 8b, when the UAV is within the NTZ and in idle mode, the AMF can transmit service rejection messages due to NTZ control.

[0106] NTZ control can be modified or deactivated for one or more reasons. The USS / UTM can initiate modification or cancellation of a previous NTZ implementation request. The modification may indicate a new NTZ area and / or a new prohibited frequency band. Therefore, the UAS NF and the Serving AMF can take one or more actions to modify the implementation.

[0107] If NTZ control is cancelled, the UAS NF and Serving AMF can notify the RAN and / or WTRU that they are no longer under NTZ control. The UAS NF or Serving AMF can detect that the UAV is outside the NTZ or that the NTZ period has elapsed. As a result, the UAS NF or Serving AMF can send NTZ deactivation information to the RAN or WTRU, which can stop NTZ implementation.

[0108] UAVs controlled by the NTZ and subject to communication constraints may take one or more actions. For communications not scheduled by the RAN (e.g., communications via PC5 links), the UAV may select spectrum for communications not constrained by the NTZ unless the PC5-based communication is exempted from NTZ implementation. For communications that may require high bandwidth and could suffer QoS degradation due to constrained frequency bands, the UAV may delay the communication until it is no longer constrained by the NTZ. The UAV may attempt to find alternative communication paths (such as non-3GPP connections (e.g., Wi-Fi connections, satellite connections, etc.)) to avoid communication constraints. Under USS / UTM authorization, the UAV may attempt to maneuver out of the NTZ area to avoid communication constraints.

[0109] When a UAV is under NTZ control, the core network can monitor illegal data activity on certain PDU sessions (assuming the CN has not yet disabled these PDU sessions) and / or trigger alarms upon detecting illegal data activity. Upon receiving an NTZ enforcement request and determining that the target UAV is under NTZ control (e.g., within the NTZ area), the serving AMF can notify the SMF that the UAV is under NTZ control and / or that a PDU session should be constrained. The SMF can invoke the UPF service to monitor data activity on those constrained PDU sessions. If data packets are received on those constrained PDU sessions, the UPF can send an illegal data transmission event report to the SMF.

[0110] Event reports may include information such as the PDU session ID on which illegal data transmission was detected, the timestamp of the detected illegal data transmission, and / or the size of the received illegal data packets.

[0111] SMF can include additional information (such as DNN related to PDU sessions) in the event report and can forward the event report to AMF. AMF can forward the event report to USS / UTM (e.g., via UAS NF / NEF).

[0112] The CN can instruct the serving RAN to monitor unauthorized radio transmissions via the air interface. Radio transmissions via the Uu interface are scheduled by the RAN, and thus, the spectrum used is securely controlled. Air interface monitoring primarily targets other types of radio transmissions (e.g., communications via PC5 / side link), for which non-cooperative UAVs may select spectrum that might not be permitted in the NTZ.

[0113] Multiple specific NTZ surveillance devices (NTZ-SDs) (capable of receiving UAV broadcast or unicast transmissions on the target spectrum (e.g., supporting PC5-based reception)) can be deployed in the NTZ and connected to the RAN. When a UAV is under NTZ control and there is a request (e.g., a USS request) to monitor the UAV for illegal transmissions, the Serving AMF can instruct the Serving RAN to activate surveillance. The request may include the target UAV identifier (e.g., CAA-level UAV ID), area, surveillance time period, etc.

[0114] The serving RAN can locate one or more NTZ-SDs in the target NTZ and instruct them to monitor any transmissions from the target UAV. The NTZ-SDs report any detected illegal radio transmissions to the RAN, including the detected UAV identifier, the type of communication (e.g., broadcast or unicast), the timestamp of the detected radio transmission, etc. The RAN can forward the report back to the CN, and the CN can forward the report to the USS.

Claims

1. A first network node, comprising: The processor is configured as follows: Receive a request for implementing non-transfer area NTZ, wherein the request indicates NTZ information, and wherein the request includes an identifier of one or more WTRUs to which the NTZ is applied; Based on the request for implementing the NTZ, the location of the Wireless Transmit / Receive Unit (WTRU) is determined; Based on the determined location of the WTRU, it is determined that the WTRU is located near the NTZ; as well as When the WTRU is determined to be near the NTZ, a first message is sent to the WTRU, wherein the first message includes at least a portion of the NTZ information and an indication that the WTRU is under NTZ control.

2. The first network node according to claim 1, wherein the NTZ information includes: Indications for geographical regions, one or more frequency bands, or time periods.

3. The first network node according to claim 1 or 2, wherein the processor is configured to: A second message is sent to the second network node, wherein the second message indicates that one or more Protocol Data Unit (PDU) sessions of the WTRU should be deactivated.

4. The first network node according to claim 1 or 2, wherein the processor is configured to: A second message is sent to a second network node, wherein the second message indicates that command-and-control C2 communication with the WTRU via the first network node or the second network node is permitted.

5. The first network node according to any one of claims 1 to 4, wherein the processor is configured to: If the WTRU is determined not to be near the NTZ, a third message is sent to the WTRU, wherein the third message notifies the WTRU about the NTZ.

6. The first network node according to any one of claims 1 to 5, wherein the NTZ is a geographic area in which the WTRU is not permitted to transmit via one or more frequency bands.

7. The first network node according to any one of claims 1 to 6, wherein the processor is configured to: Receive a second request for implementing the non-transfer zone NTZ, wherein the second request modifies or cancels the NTZ information.

8. The first network node according to any one of claims 1 to 7, wherein the WTRU is an unmanned aerial vehicle (UAV).

9. A method performed by a first network node, the method comprising: Receive a request for implementing non-transfer area NTZ, wherein the request indicates NTZ information, and wherein the request includes an identifier of one or more WTRUs to which the NTZ is applied; Based on the request for implementing the NTZ, the location of the Wireless Transmit / Receive Unit (WTRU) is determined; Based on the determined location of the WTRU, it is determined that the WTRU is located near the NTZ; as well as When the WTRU is determined to be near the NTZ, a first message is sent to the WTRU, wherein the first message includes at least a portion of the NTZ information and an indication that the WTRU is under NTZ control.

10. The method of claim 9, wherein the NTZ information includes: Indications for geographical regions, one or more frequency bands, or time periods.

11. The method according to claim 9 or 10, further comprising: A second message is sent to the second network node, wherein the second message indicates that one or more Protocol Data Unit (PDU) sessions of the WTRU should be deactivated.

12. The method according to claim 9 or 10, further comprising: A second message is sent to a second network node, wherein the second message indicates that command-and-control C2 communication with the WTRU via the first network node or the second network node is permitted.

13. The method according to any one of claims 9 to 12, further comprising: If the WTRU is determined not to be near the NTZ, a third message is sent to the WTRU, wherein the third message notifies the WTRU about the NTZ.

14. The method according to any one of claims 9 to 13, wherein the NTZ is a geographic area in which the WTRU is not permitted to transmit via one or more frequency bands.

15. The method according to any one of claims 9 to 14, further comprising: Receive a second request for implementing the NTZ, wherein the second request modifies or cancels the NTZ information.

16. The method according to any one of claims 9 to 15, wherein the WTRU is an unmanned aerial vehicle (UAV).

17. A wireless transmit / receive unit (WTRU), comprising: The processor is configured as follows: Receive messages from network nodes, wherein the messages include information related to the non-transfer zone NTZ and an indication that the WTRU is under NTZ control; Determine whether the WTRU is under NTZ control; and Based on the fact that the WTRU is under NTZ control, the RRC connection with the network node is released.

18. The WTRU of claim 17, wherein the information related to the NTZ includes: The NTZ can be an indication of its geographical area, an indication of one or more frequency bands associated with the NTZ, or an indication of a time period associated with the NTZ.

19. The WTRU of claim 17 or 18, wherein the processor is configured to: Based on the fact that the WTRU is in idle mode, a service request message is sent to the network node; and Based on the fact that the WTRU is controlled by NTZ, it receives a service rejection message from the network node.

20. The WTRU according to any one of claims 17, 18, or 19, wherein the processor is configured to: Generate an alarm related to the NTZ or send an indication of the NTZ to the controller of the WTRU.

Images