SYSTEM AND METHOD FOR CONFIGURING UNMANNED AERIAL VEHICLE (UAV) MULTI-RAT DUAL CONNECTIVITY (MRDC)

Abstract

A system and method for configuring an unmanned aerial vehicle (UAV) multi-RAT dual connectivity (MRDC) is presented. A first wireless communication node may communicate with a second wireless communication node to share one or more configuration containers. The one or more configuration containers may include various information associated with a terminal service, and the one or more configuration containers correspond to different radio access technologies (RATs). The one or more configuration containers include at least one of a long-term evolution (LTE) configuration container or a new radio (NR) configuration container.

Description

[Technical field]

[0001] (Technical field) The present disclosure relates generally to wireless communications, including, but not limited to, systems and methods for configuring Unmanned Aerial Vehicle (UAV) Multi-RAT Dual Connectivity (MRDC). [Background technology]

[0002] (background) The standardization body, the 3rd Generation Partnership Project (3GPP®), is currently defining a new air interface called 5G New Radio (5G NR), as well as the Next Generation Packet Core Network (NG-CN or NGC). 5G NR has three main components: 5G Access Network (5G-AN), 5G Core Network (5GC), and User Equipment (UE). To facilitate the enablement of different data services and requirements, the elements of 5GC, also called network functions, have been simplified, some of them software-based and some hardware-based, so that they can be adapted as needed. Summary of the Invention [Means for solving the problem]

[0003] (overview) Exemplary embodiments disclosed herein are directed to solving problems associated with one or more problems presented in the prior art, as well as providing further features that will become readily apparent by reference to the following detailed description in conjunction with the accompanying drawings. According to various embodiments, exemplary systems, methods, devices, and computer program products are disclosed herein. However, it is understood that these embodiments are presented by way of example and not limitation, and various modifications to the disclosed embodiments may be made while remaining within the scope of the present disclosure, as would be apparent to one skilled in the art upon reading this disclosure.

[0004] At least one aspect relates to a system, method, apparatus, or computer-readable medium: A first wireless communication node (e.g., a master node (MN)) may communicate with a second wireless communication node (e.g., a secondary node (SN)) to share one or more configuration containers. The one or more configuration containers may include various information associated with a terminal service, and the one or more configuration containers correspond to different radio access technologies (RATs). The one or more configuration containers may include at least one of a long-term evolution (LTE) configuration container or a new radio (NR) configuration container.

[0005] In some embodiments, the various information may include at least one of a wireless communication device (e.g., an unmanned aerial vehicle (UAV)) identification configured to identify the wireless communication device, wireless communication device service subscription information configured to notify a wireless communication node that the wireless communication device is eligible to use a wireless communication device service, addresses of one or more reporting receivers from which data for the wireless communication device is to be collected, wireless communication device position information configuring wireless communication device position measurements and reports, height report information associated with the wireless communication device, flight path information associated with the wireless communication device, or measurement information including frequency-related information for the wireless communication device.

[0006] In some embodiments, the first wireless communication node may receive a first message including one or more configuration containers from a core network. The first wireless communication node may send a second message including one or more configuration containers to a wireless communication device (e.g., a UE). The first message may be a first communication message. The second message may be a second communication message.

[0007] In some embodiments, the first wireless communication node may receive a first message including one or more configuration containers from a core network. The first wireless communication node may send a second message including the one or more configuration containers to the second wireless communication node. The first message may be a first communication message. The second message may be a third communication message. The one or more configuration containers may be further sent to the wireless communication device via the first communication message.

[0008] In some embodiments, at least a portion of the various information may be reported by the wireless communication device to the core network via a first wireless communication node, reported to the core network via a second wireless communication node, reported first to the core network via the second wireless communication node and then via the first wireless communication node, or reported to the core network first via the first wireless communication node and then via the second wireless communication node.

[0009] In some embodiments, the first wireless communication node may send a first message to a third wireless communication node (e.g., a target node) requesting that the second wireless communication node be changed to the third wireless communication node. The first message may include one or more configuration containers. The first message may be a third communication message.

[0010] In some embodiments, the first wireless communication node may receive a first message from the second wireless communication node requesting to change the second wireless communication node to a third wireless communication node. The first wireless communication node may send a second message to the third wireless communication node, the second message including one or more configuration containers. The first message and the second message may each be a third communication message.

[0011] In some embodiments, a first wireless communication node (e.g., a source MN) may send a first message to a fourth wireless communication node (e.g., a target MN) indicating a handover from the first wireless communication node to the fourth wireless communication node. The first message may be an Xn Application Protocol (XnAP) message and may include one or more configuration containers. The one or more configuration containers included in the first message may be further sent from the fourth wireless communication node to the second wireless communication node via another third communication message.

[0012] In some embodiments, the first wireless communication node may send a first message to the second wireless communication node requesting to add the second wireless communication node. The first message may be a third communication message and may include one or more configuration containers.

[0013] In some embodiments, the first wireless communication node may send a first message to the second wireless communication node requesting to remove the second wireless communication node. The first wireless communication node may receive a second message from the second wireless communication node, the second message including one or more configuration containers. The first message and the second message may each be a third communication message.

[0014] In some embodiments, the first wireless communication node may receive a first message requesting removal of itself from the second wireless communication node. The first message may be a third communication message and may include one or more configuration containers. In a particular embodiment, the first communication message may be a NG Application Protocol (NGAP) message. The second communication message may be a Radio Resource Control (RRC) message. The second communication message may be an Xn Application Protocol (XnAP) message. [Brief description of the drawings]

[0015] Various exemplary embodiments of the present solution are described in detail below with reference to the following figures or drawings. The drawings are provided for illustrative purposes only and merely depict exemplary embodiments of the present solution to facilitate the reader's understanding of the present solution. Thus, the drawings should not be considered as limiting the breadth, scope, or applicability of the present solution. It should be noted that for clarity and ease of illustration, the drawings are not necessarily drawn to scale.

[0016] [Figure 1] FIG. 1 illustrates an example of a cellular communication network in which the techniques disclosed herein may be implemented, according to one embodiment of the present disclosure.

[0017] [Diagram 2] FIG. 2 illustrates a block diagram of an example base station and a user equipment device according to some embodiments of the disclosure.

[0018] [Diagram 3] FIG. 3 illustrates a sequence diagram for a secondary node (SN) addition procedure according to some embodiments of the present disclosure.

[0019] [Figure 4] FIG. 4 illustrates a sequence diagram for a secondary node (SN) modification procedure according to some embodiments of the present disclosure.

[0020] [Diagram 5] FIG. 5 illustrates a sequence diagram for a secondary node (SN) change procedure according to some embodiments of the present disclosure.

[0021] [Figure 6] FIG. 6 illustrates a sequence diagram for an inter-master node (MN) handover procedure according to some embodiments of the present disclosure.

[0022] [Figure 7]FIG. 7 illustrates a sequence diagram for unmanned aerial vehicle (UAV) configuration via a master node (MN) according to some embodiments of the present disclosure.

[0023] [Figure 8] FIG. 8 illustrates a sequence diagram for unmanned aerial vehicle (UAV) configuration via a secondary node (SN) according to some embodiments of the present disclosure.

[0024] [Figure 9] FIG. 9 illustrates a sequence diagram for unmanned aerial vehicle (UAV) reporting in dual connectivity (DC) according to some embodiments of the present disclosure.

[0025] [Figure 10] FIG. 10 illustrates a sequence diagram for master node (MN) initiated mobility upon secondary node (SN) change according to some embodiments of the present disclosure.

[0026] [Figure 11] FIG. 11 illustrates a sequence diagram for secondary node (SN) initiated mobility upon secondary node (SN) change according to some embodiments of the present disclosure.

[0027] [Figure 12] FIG. 12 illustrates a sequence diagram for inter-master node (MN) handover with / without SN change according to some embodiments of the present disclosure.

[0028] [Figure 13] FIG. 13 illustrates a sequence diagram from a standalone architecture to a dual connectivity architecture according to some embodiments of the present disclosure.

[0029] [Figure 14] FIG. 14 illustrates a sequence diagram from a dual connectivity architecture to a standalone architecture according to some embodiments of the present disclosure.

[0030] [Figure 15] FIG. 15 illustrates a flow diagram for configuring Unmanned Aerial Vehicle (UAV) Multi-RAT Dual Connectivity (MRDC) according to one embodiment of the present disclosure. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0031] (Detailed Description) 1. Mobile communications technology and the environment FIG. 1 illustrates an example wireless communication network and / or system 100 in which techniques disclosed herein may be implemented, according to embodiments of the present disclosure. In the following description, the wireless communication network 100 may be any wireless network, such as a cellular network or a narrowband Internet of Things (NB-IoT) network, and is referred to herein as "network 100." Such an example network 100 includes a base station 102 (hereinafter "BS 102," also referred to as a wireless communication node) and a user equipment device 104 (hereinafter "UE 104," also referred to as a wireless communication device) that can communicate with each other via a communication link 110 (e.g., a wireless communication channel), and a cluster of cells 126, 130, 132, 134, 136, 138, and 140 that overlap a geographic region 101. In FIG. 1, the BS 102 and the UE 104 are contained within the respective geographic boundaries of the cell 126. Each of the other cells 130, 132, 134, 136, 138, and 140 may include at least one base station operating in its assigned bandwidth to provide adequate wireless coverage to its intended users.

[0032] For example, the BS 102 may operate in an assigned channel transmission bandwidth to provide adequate coverage to the UE 104. The BS 102 and the UE 104 may communicate via downlink radio frames 118 and uplink radio frames 124, respectively. Each radio frame 118 / 124 may be further divided into subframes 120 / 127 that may include data symbols 122 / 128. In this disclosure, the BS 102 and the UE 104 are generally described herein as non-limiting examples of "communication nodes" capable of practicing the methods disclosed herein. Such communication nodes may be capable of wireless and / or wired communication in accordance with various embodiments of the present solution.

[0033] 2 illustrates a block diagram of an exemplary wireless communication system 200 for transmitting and receiving wireless communication signals (e.g., OFDM / OFDMA signals) in accordance with some embodiments of the present solution. System 200 may include components and elements configured to support known or conventional operational features that need not be described in detail herein. In an exemplary embodiment, system 200 may be used to communicate (e.g., transmit and receive) data symbols in a wireless communication environment, such as wireless communication environment 100 of FIG. 1, as previously described.

[0034] The system 200 generally includes a base station 202 (hereinafter "BS 202") and a user equipment device 204 (hereinafter "UE 204"). The BS 202 includes a BS (base station) transceiver module 210, a BS antenna 212, a BS processor module 214, a BS memory module 216, and a network communication module 218, each of which is coupled and interconnected with each other as needed via a data communication bus 220. The UE 204 includes a UE (user equipment) transceiver module 230, a UE antenna 232, a UE memory module 234, and a UE processor module 236, each of which is coupled and interconnected with each other as needed via a data communication bus 240. The BS 202 communicates with the UE 204 over a communication channel 250, which may be any wireless channel or other medium suitable for the transmission of data as described herein.

[0035] As will be appreciated by those skilled in the art, system 200 may further include any number of modules other than those shown in FIG. 2. Those skilled in the art will appreciate that the various example blocks, modules, circuits, and processing logic described in connection with the embodiments disclosed herein may be implemented in hardware, computer readable software, firmware, or any practical combination thereof. To clearly illustrate this compatibility and suitability of hardware, firmware, and software, various example components, blocks, modules, circuits, and steps are described generally in terms of their functionality. Whether such functionality is implemented as hardware, firmware, or software may depend on the particular application and design constraints imposed on the overall system. Those familiar with the concepts described herein may implement such functionality in a manner suitable for each particular application, but such implementation decisions should not be construed as limiting the scope of the present disclosure.

[0036] According to some embodiments, the UE transceiver 230 may be referred to herein as an "uplink" transceiver 230 including a radio frequency (RF) transmitter and an RF receiver, each with circuitry coupled to an antenna 232. A duplex switch (not shown) may alternatively couple an uplink transmitter or receiver to an uplink antenna in a time-duplexed manner. Similarly, according to some embodiments, the BS transceiver 210 may be referred to herein as a "downlink" transceiver 210 including an RF transmitter and an RF receiver, each with circuitry coupled to an antenna 212. A downlink duplex switch may alternatively couple a downlink transmitter or receiver to a downlink antenna 212 in a time-duplexed manner. The operation of the two transceiver modules 210 and 230 may be time-coordinated such that the downlink transmitter is coupled to the downlink antenna 212 at the same time that the uplink receiver circuitry is coupled to the uplink antenna 232 for receiving transmissions over the wireless transmission link 250. Conversely, the operation of the two transceivers 210 and 230 may be timed such that the uplink transmitter is coupled to the uplink antenna 232 at the same time that the downlink receiver is coupled to the downlink antenna 212 for receiving transmissions over the wireless transmission link 250. In some embodiments, there is a close time synchronization with a minimum guard time between changes in duplex direction.

[0037] The UE transceiver 230 and the base station transceiver 210 are configured to communicate over a wireless data communication link 250 and cooperate with appropriately configured RF antenna devices 212 / 232 capable of supporting a particular wireless communication protocol and modulation scheme. In some exemplary embodiments, the UE transceiver 210 and the base station transceiver 210 are configured to support industry standards such as Long Term Evolution (LTE) and the emerging 5G standard. However, it will be appreciated that the present disclosure is not necessarily limited to application to a particular standard and associated protocol. Rather, the UE transceiver 230 and the base station transceiver 210 may be configured to support alternative or additional wireless data communication protocols, including future standards or variations thereof.

[0038] According to various embodiments, the BS 202 may be, for example, an evolved Node B (eNB), a serving eNB, a target eNB, a femto station, or a pico station. In some embodiments, the UE 204 may be embodied in various types of user devices, such as a mobile phone, a smartphone, a personal digital assistant (PDA), a tablet, a laptop computer, a wearable computing device, etc. The processor modules 214 and 236 may be implemented or realized using a general purpose processor, a content addressable memory, a digital signal processor, an application specific integrated circuit, a field programmable gate array, any suitable programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. As such, the processor may be realized as a microprocessor, a controller, a microcontroller, a state machine, etc. The processor may also be implemented as a combination of computing devices, such as a combination of a digital signal processor and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a digital signal processor core, or any other such configuration.

[0039] Furthermore, the steps of the methods or algorithms described in connection with the embodiments disclosed herein may be embodied directly in hardware, firmware, software modules executed by the processor modules 214 and 236, respectively, or any practical combination thereof. The memory modules 216 and 234 may be realized as RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, removable disk, CD-ROM, or any other form of storage medium known in the art. In this regard, the memory modules 216 and 234 may be coupled to the processor modules 210 and 230, respectively, such that the processor modules 210 and 230 can read information from and write information to the memory modules 216 and 234, respectively. The memory modules 216 and 234 may also be integrated into the respective processor modules 210 and 230. In some embodiments, the memory modules 216 and 234 may each include a cache memory for storing temporary variables or other intermediate information during execution of instructions executed by the processor modules 210 and 230, respectively. Memory modules 216 and 234 may also each include non-volatile memory for storing instructions executed by processor modules 210 and 230, respectively.

[0040] The network communications module 218 generally represents hardware, software, firmware, processing logic, and / or other components of the base station 202 that enable bidirectional communication between the base station transceiver 210 and other network components and communication nodes configured to communicate with the base station 202. For example, the network communications module 218 may be configured to support Internet or WiMAX traffic. In a typical arrangement, without limitation, the network communications module 218 provides an 802.3 Ethernet interface to enable the base station transceiver 210 to communicate with conventional Ethernet-based computer networks. As such, the network communications module 218 may include a physical interface for connecting to a computer network (e.g., a Mobile Switching Center (MSC)). The terms "configured for," "configured to," and conjugations thereof, as used herein with respect to a specified operation or function, refer to devices, components, circuits, structures, machines, signals, etc. that are physically configured, programmed, formatted, and / or arranged to perform the specified operation or function.

[0041] The Open Systems Interconnection (OSI) model (referred to herein as the "Open Systems Interconnection Model") is a conceptual and logical layout that defines network communications used by open systems (e.g., wireless communication devices, wireless communication nodes) to interconnect and communicate with other systems. The model is divided into seven subcomponents or layers, each of which represents a conceptual collection of services provided to the layers above and below it. The OSI model also defines logical networks and effectively describes computer packet transfers by using different layer protocols. The OSI model is sometimes referred to as the seven-layer OSI model or seven-layer model. In some embodiments, the first layer may be the physical layer. In some embodiments, the second layer may be the medium access control (MAC) layer. In some embodiments, the third layer may be the radio link control (RLC) layer. In some embodiments, the fourth layer may be the packet data convergence protocol (PDCP) layer. In some embodiments, the fifth layer may be the radio resource control (RRC) layer. In some embodiments, the sixth layer may be a non-access layer (NAS) layer or an Internet Protocol (IP) layer, and the seventh layer is another layer.

[0042] In order to enable those skilled in the art to make and use the present solution, various exemplary embodiments of the present solution are described below with reference to the accompanying drawings. As will be apparent to those skilled in the art, after reading this disclosure, various changes or modifications to the examples described herein can be made without departing from the scope of the present solution. Thus, the present solution is not limited to the exemplary embodiments and applications described and illustrated herein. Furthermore, the specific order or hierarchy of steps in the methods disclosed herein is merely an example approach. Based on design preferences, the specific order or hierarchy of steps of the disclosed methods or processes can be rearranged while remaining within the scope of the present solution. Thus, those skilled in the art will understand that the methods and techniques disclosed herein present various steps or operations in a sample order, and that the present solution is not limited to the specific order or hierarchy presented, unless otherwise specified.

[0043] 2. System and method for configuring unmanned aerial vehicle (UAV) multi-RAT dual connectivity (MRDC) Unmanned Aerial Vehicle (UAV) related features may be supported in the Rel-18 New Radio (NR) specification. In some cases, UAV related features may not be supported in NR. By using the procedures introduced in this invention, UAV configuration and reports can be transmitted between a network (NW) and a user equipment (UE) and / or between a master node (MN) and a secondary node (SN).

[0044] 3-6 show call flows for Multi-Radio Access Technology (RAT) Dual Connectivity (MRDC) related procedures (e.g., SN addition, SN modification, and / or SN change). FIG. 3 is a call flow for an SN addition procedure. FIG. 4 is a call flow for an SN modification procedure (initiated by the MN). FIG. 5 is a call flow for an SN change procedure (initiated by the MN). FIG. 6 is a call flow for an inter-MN handover with / without an MN initiated SN change procedure. In some embodiments, the NG Application Protocol (NGAP) messages, Xn Application Protocol (XnAP) messages, and / or Radio Resource Control (RRC) messages may be implemented as any of a variety of other messages.

[0045] Example 1: UAV Configuration Container (for Inter-RAT Mobility) This embodiment explains why the UAV configuration container can be introduced for inter-RAT handover. In case of heterogeneous networks, during UE mobility, inter-system handover (HO) (e.g., HO between gNB and eNB with change of core network (CN) between Access and Mobility Management Function (AMF) and Mobility Management Entity (MME)) and intra-system inter-radio access technology (RAT) (e.g., HO between gNB and ng-eNB, CN may be AMF) handover may be performed. To maximize UAV service continuity, the same UAV-related configuration with different encoding / format for both NR and LTE may be configured for RAN nodes in different containers. The UE can continue to use UAV-related functions even if different RATs are used between RAN nodes during HO. The UAV configuration container may be configured for the UE before or during HO.

[0046] In some embodiments, at least one of the following information may be added to both the NR container and the LTE container: UAV identification (ID), UAV subscription information, address of a reporting receiver, UAV position configuration, height reporting configuration, flight path information configuration, or measurement configuration. The UAV ID may be used / configured to identify the UAV. The UAV subscription information may include a flag used / configured to inform the RAN node that the UE is eligible to use the UAV service. The reporting receiver address may include an IP address or URL for a UAV data collector. Different UAV data types may have the same destination or different destinations. The UAV position configuration may include information regarding UAV position measurement and reporting (e.g., precise requirements for the UAV position), the type of positioning method that may be used, measurement / reporting frequency, and / or completeness requirements. The height reporting configuration may include criteria for when the UE can report its height, measurement / reporting frequency, accuracy of the height measurement, and / or completeness requirements. The flight path information configuration may include UE flight path history or prediction, formula, flight path (e.g., cell ID, RAN node ID, list of coordinates), number of points in the flight path list, timestamp requirement, accuracy requirement, completeness requirement, and / or reporting destination (e.g., IP or URL). The measurement configuration may include UE frequency related measurement information (e.g., cell Reference Signal Received Power (RSRP), Reference Signal Received Quality (RSRQ), Signal to Noise and Interference Ratio (SINR)).

[0047] Example 2: UAV configuration via MN FIG. 7 is the call flow for UAV configuration via MN procedure.

[0048] In step 1, the CN may send an NGAP message to the MN for UAV configuration. At least one of the following information may be contained / included in the NGAP message: UE identification information (e.g., UE ID), UAV identification information (e.g., UAV ID), UAV subscription information, or a UAV configuration container. The UAV subscription information may include a flag used / configured to inform the RAN node that the UE is entitled to use the UAV service. The UAV configuration container may include an LTE configuration container and / or an NR configuration container.

[0049] In step 2, the MN may send a response NGAP message with the ACK information to the CN.

[0050] In step 3, the MN may send the received UAV configuration information to the UE via a Radio Resource Control (RRC) message. At least one of the following information may be included in the RRC message: UE identification information (e.g., UE ID), UAV identification information (e.g., UAV ID), UAV subscription information, or a UAV configuration container. The UAV subscription information may include a flag used / configured to inform the RAN node that the UE is entitled to use the UAV service. The UAV configuration container may include an LTE configuration container and / or an NR configuration container.

[0051] In step 4, the UE may send a response RRC message with the ACK information to the MN.

[0052] In some embodiments, the NGAP message and / or the RRC message may be implemented as any of a variety of other messages.

[0053] Example 3: UAV configuration via SN Figure 8 is a call flow for UAV configuration via SN procedure. In this embodiment, two options are introduced: SN may receive UAV configuration via either MN or CN.

[0054] Alternative 1: MN forwards received UAV configuration to SN.

[0055] In step 1, the CN may send an NGAP message to the MN with UAV configuration information. At least one of the following information may be included in the NGAP message: UE identification information (e.g., UE ID), UAV identification information (e.g., UAV ID), UAV subscription information, or a UAV configuration container. The UAV subscription information may include a flag used / configured to inform the RAN node that the UE is entitled to use the UAV service. The UAV configuration container may include an LTE configuration container and / or an NR configuration container.

[0056] In step 2, the MN may send the received UAV configuration information to the SN via an XnAP message. At least one of the following information may be included in the XnAP message: UE identification information (e.g., UE ID), UAV identification information (e.g., UAV ID), UAV subscription information, or a UAV configuration container. The UAV subscription information may include a flag used / configured to inform the RAN node that the UE is entitled to use the UAV service. The UAV configuration container may include an LTE configuration container and / or an NR configuration container.

[0057] In step 3, the SN may send a response XnAP message with the ACK information to the MN.

[0058] In step 4a, the MN may send a response NGAP message with the ACK information to the CN.

[0059] In step 4b, the reply NGAP message does not have to be sent after the MN receives the reply XnAP message in step 3. The NGAP message may be forwarded from the MN to the CN before or when the XnAP procedures of steps 2 and 3 are performed.

[0060] Alternative 2: CN sends UAV configuration to SN

[0061] In step 1, the CN may send an NGAP message to the SN with UAV configuration information. At least one of the following information may be included in the NGAP message: UE identification information (e.g., UE ID), UAV identification information (e.g., UAV ID), UAV subscription information, or a UAV configuration container. The UAV subscription information may include a flag used / configured to inform the RAN node that the UE is entitled to use the UAV service. The UAV configuration container may include an LTE configuration container and / or an NR configuration container.

[0062] In step 2, the SN may send a response NGAP message to the CN.

[0063] In some embodiments, the NGAP message used in step 1 in different alternatives may be the same or different messages. For any alternative, the UAV configuration may be finally sent to the UE by the following steps:

[0064] In step A, the SN may send an RRC message to the UE. At least one of the following information may be included in the RRC message: UE identification information (e.g., UE ID), UAV identification information (e.g., UAV ID), UAV subscription information, or a UAV configuration container. The UAV subscription information may include a flag used / configured to inform the RAN node that the UE is entitled to use the UAV service. The UAV configuration container may include an LTE configuration container and / or an NR configuration container.

[0065] In step B, the UE may send a response RRC message with the ACK information to the SN.

[0066] Example 4: UAV reporting in dual connectivity (DC) Figure 9 is a call flow for the UAV reporting procedure in dual connectivity (DC). During the reporting procedure, at least one of the following information may be reported: UE identification information (e.g., UE ID), UAV identification information (e.g., UAV ID), UAV report, or collector's address. The UAV report may contain the required UAV information. Details can be found in the previous example of the UAV configuration part. The collector's address can be either an IP address or a URL, depending on which type of address is configured.

[0067] As shown in Figure 9, regardless of how the UE receives the UAV configuration (via the MN or SN), four alternatives may be used for UAV information reporting. The RRC message, XnAP message, and NGAP message shown in Figure 9 may be newly introduced for UAVs or may be enhanced by existing messages. The XnAP message used in steps 2c and 2d may be the same message or different messages.

[0068] Example 5: Mobility in SN changes initiated by MN Figure 10 is a call flow for mobility in SN change procedure initiated by MN. The steps in the dotted box are mandatory for this example. The alternatives are steps that can be used for UAV configuration transfer. The UAV configuration information can be transferred in either the SgNB Addition Request message or the SgNB Reconfiguration Complete message. In some embodiments, it may not be possible for the MN to transfer the UAV configuration information to the target SN via both of these two XnAP messages.

[0069] In step 1, the MN may decide / determine to change the SN. The MN may send an XnAP message (e.g., SgNB Addition Request) to the target SN. At least one of the following information may be included in the XnAP message: UE identification information (e.g., UE ID), UAV identification information (e.g., UAV ID), UAV subscription information, or a UAV configuration container. The UAV subscription information may include a flag used / configured to inform the RAN node that the UE is entitled to use the UAV service. The UAV configuration container may include an LTE configuration container and / or an NR configuration container.

[0070] In step 2, the target SN may send an XnAP message (eg, SgNB Addition Request ACK) to the MN.

[0071] In steps 3 and 4, the MN may send an XnAP SgNB Release Request to the source SN, and the source SN may return an XnAP SgNB Release Request ACK to the MN.

[0072] In steps 5 and 6, the MN may send an RRC RRC reconfiguration to the UE, and the UE may return an RRC RRC reconfiguration ACK to the MN.

[0073] In step 7, the MN may send an XnAP message (e.g., SgNB Reconfiguration Complete) to the target SN. If the UAV configuration is not included in step 1, the UAV configuration may be added to this XnAP message. At least one of the following information may be included in the XnAP message: UE identification information (e.g., UE ID), UAV identification information (e.g., UAV ID), UAV subscription information, or a UAV configuration container. The UAV subscription information may include a flag used / configured to inform the RAN node that the UE is entitled to use the UAV service. The UAV configuration container may include an LTE configuration container and / or an NR configuration container.

[0074] Example 6: Mobility in SN-initiated SN changes Figure 11 is a call flow for mobility in SN initiated SN change procedure. The steps in the dotted box are mandatory for this example. The alternatives are steps that can be used for UAV configuration transfer. The UAV configuration information can be transferred in either the SgNB Addition Request message or the SgNB Reconfiguration Complete message. In some embodiments, it may not be possible for the MN to transfer the UAV configuration information to the target SN via both of these two XnAP messages.

[0075] In step 1, the source SN may decide to trigger an SN change procedure. The source SN may send an XnAP message (eg, SgNB change request) to the MN.

[0076] In step 2, the MN may send an XnAP message (e.g., SgNB Addition Request) to the target SN. At least one of the following information may be included in the XnAP message: UE identification information (e.g., UE ID), UAV identification information (e.g., UAV ID), UAV subscription information, or a UAV configuration container. The UAV subscription information may include a flag used / configured to inform the RAN node that the UE is entitled to use the UAV service. The UAV configuration container may include an LTE configuration container and / or an NR configuration container.

[0077] In step 3, the target SN may send an XnAP message (eg, SgNB Addition Request ACK) to the MN.

[0078] In steps 4 and 5, the MN may send an RRC RRC reconfiguration to the UE, and the UE may return an RRC RRC reconfiguration ACK to the MN.

[0079] In step 6, the MN may send an XnAP message (eg, SgNB Change Confirm) to the source SN.

[0080] In step 7, the MN may send an XnAP message (e.g., SgNB Reconfiguration Complete) to the target SN. If the UAV configuration is not included in step 1, the UAV configuration may be added to the XnAP message. At least one of the following information may be included in the XnAP message: UE identification information (e.g., UE ID), UAV identification information (e.g., UAV ID), UAV subscription information, or a UAV configuration container. The UAV subscription information may include a flag used / configured to inform the RAN node that the UE is entitled to use the UAV service. The UAV configuration container may include an LTE configuration container and / or an NR configuration container.

[0081] Example 7: Inter-MN handover with / without SN change FIG. 12 is a call flow for inter-MN handover with / without SN change mobility.

[0082] For alternative a, the procedures within the dotted box are only for the SN change scenario: if the target MN decides to reuse the old SN, these procedures may not be needed anymore.

[0083] In the case of alternative b, both procedures may be performed in this embodiment. How to send the UAV information to the target SN may have different alternatives.

[0084] In case of inter-MN handover without SN change, (source) SN and (target) SN can be the same node since there is no SN change during handover. In this case, (source) SN == (target) SN == SN. In case of inter-MN handover with SN change, (source) SN and (target) SN can be two different nodes.

[0085] In step 1, the source MN may trigger the handover procedure by sending an XnAP message (e.g., handover request) to the target MN. At least one of the following information may be included in the XnAP message: UE identification information (e.g., UE ID), UAV identification information (e.g., UAV ID), UAV subscription information, or a UAV configuration container. The UAV subscription information may include a flag used / configured to inform the RAN node that the UE is entitled to use the UAV service. The UAV configuration container may include an LTE configuration container and / or an NR configuration container.

[0086] In step 2, the target MN may send an XnAP message (e.g., SgNB Addition Request) to the SN (or target SN). At least one of the following information may be included in the XnAP message: UE identification information (e.g., UE ID), UAV identification information (e.g., UAV ID), UAV subscription information, or a UAV configuration container. The UAV subscription information may include a flag used / configured to inform the RAN node that the UE is entitled to use the UAV service. The UAV configuration container may include an LTE configuration container and / or an NR configuration container.

[0087] In step 3, the SN (or target SN) may send a response XnAP message (eg, SgNB Addition Request ACK) to the target MN.

[0088] In step 4, the target MN may send an XnAP message (eg, handover request ACK) to the source MN.

[0089] In steps 5 and 6 (conditionally), the source MN may send an XnAP SgNB release request to the source SN, and the source SN may return an XnAP SgNB release request ACK to the source MN.

[0090] In step 7, the source MN may send an RRC message (eg, RRC reconfiguration) to the UE.

[0091] In step 8, the UE may initiate a random access procedure for the target MN.

[0092] In step 9, the UE may send an RRC message (eg, an RRC Reconfiguration ACK) to the target MN.

[0093] In step 10 (conditional), the UE may initiate a random access procedure for the target SN.

[0094] In step 11, the target MN may send an XnAP message (e.g., SgNB Reconfiguration Complete) to the SN (or target SN). If the UAV configuration is not included in step 1, the UAV configuration may be added to the XnAP message. At least one of the following information may be included in the XnAP message: UE identification information (e.g., UE ID), UAV identification information (e.g., UAV ID), UAV subscription information, or a UAV configuration container. The UAV subscription information may include a flag used / configured to inform the RAN node that the UE is entitled to use the UAV service. The UAV configuration container may include an LTE configuration container and / or an NR configuration container.

[0095] Example 8: Standalone to Dual Connectivity Architecture Figure 13 is a call flow from standalone architecture to dual connectivity architecture procedures. The steps in the dotted box are mandatory for this example. The alternatives are steps that can be used for UAV configuration transfer. The UAV configuration information can be transferred in either the SgNB Addition Request message or the SgNB Reconfiguration Complete message. In some embodiments, it may not be possible for the MN to transfer the UAV configuration information to the target SN via both of these two XnAP messages.

[0096] In step 1, a serving gNB (e.g., MN in a call flow) may decide to add an SN and switch to dual connectivity (DC). The gNB may send an XnAP message (e.g., SgNB Addition Request) to the SN. At least one of the following UAV configuration information may be included in the XnAP message: UE identification information (e.g., UE ID), UAV identification information (e.g., UAV ID), UAV subscription information, or a UAV configuration container. The UAV subscription information may include a flag used / configured to inform the RAN node that the UE is eligible to use the UAV service. The UAV configuration container may include an LTE configuration container and / or an NR configuration container.

[0097] In step 2, the SN may send a response XnAP message (eg, SgNB Addition Request ACK) to the MN.

[0098] In steps 3 and 4, the gNB (MN) may send an RRC RRC reconfiguration to the UE, and the UE may return an RRC RRC reconfiguration complete to the MN.

[0099] In step 5, the MN may send an XnAP message (e.g., SgNB Reconfiguration Complete) to the SN. If the UAV configuration is not included in step 1, the UAV configuration may be added to the XnAP message. At least one of the following information may be included in the XnAP message: UE identification information (e.g., UE ID), UAV identification information (e.g., UAV ID), UAV subscription information, or a UAV configuration container. The UAV subscription information may include a flag used / configured to inform the RAN node that the UE is entitled to use the UAV service. The UAV configuration container may include an LTE configuration container and / or an NR configuration container.

[0100] Example 9: Dual Connectivity Architecture to Standalone Architecture Figure 14 is a call flow from dual connectivity architecture to standalone connectivity architecture procedures. For MN initiated SN release, the procedures / steps can be 1a=>2a=>3=>4. For SN initiated SN release, the procedures / steps can be 1b=>2b=>3=>4.

[0101] MN initiated SN release

[0102] In step 1a, the MN may decide / determine to release the current SN and switch to a standalone architecture. The MN may send an XnAP message (eg, SgNB Release Request) to the SN.

[0103] In step 2a, the SN may send an XnAP message (e.g., SgNB Release Request ACK) to the MN. The XnAP message may contain at least one of the following information: UE identification information (e.g., UE ID), UAV identification information (e.g., UAV ID), UAV subscription information, or a UAV configuration container. The UAV subscription information may include a flag used / configured to inform the RAN node that the UE is entitled to use the UAV service. The UAV configuration container may include an LTE configuration container and / or an NR configuration container.

[0104] In steps 3 and 4, the MN may send an RRC reconfiguration to the UE, and the UE may return an RRC reconfiguration complete to the MN.

[0105] SN Initiated SN Release

[0106] In step 1b, the SN may decide / determine to release itself. The SN may send an XnAP message (e.g., SgNB Release Request) to the MN. The XnAP message may contain at least one of the following information: UE identity (e.g., UE ID), UAV identity (e.g., UAV ID), UAV subscription information, or a UAV configuration container. The UAV subscription information may include a flag used / configured to inform the RAN node that the UE is entitled to use the UAV service. The UAV configuration container may include an LTE configuration container and / or an NR configuration container.

[0107] In step 2b, the MN may return an XnAP message (eg, SgNB Release Confirm) to the SN.

[0108] In steps 3 and 4, the MN may send an RRC reconfiguration to the UE, and the UE may return an RRC reconfiguration complete to the MN.

[0109] It should be understood that one or more features from the above example embodiments are not limited to a particular example embodiment and can be combined in any manner (e.g., in any priority and / or order, simultaneously or otherwise).

[0110] FIG. 15 illustrates a flow diagram of a method 1500 for configuring Unmanned Aerial Vehicle (UAV) Multi-RAT Dual Connectivity (MRDC). The method 1500 may be implemented using any one or more of the components and devices detailed herein in connection with FIGS. 1-2. In summary, the method 1500 may be performed by a wireless communication node in some embodiments. Depending on the embodiment, additional, fewer, or different operations may be performed in the method 1500. At least one aspect of the operations relates to a system, method, apparatus, or computer-readable medium.

[0111] A first wireless communication node (e.g., a master node (MN)) may communicate with a second wireless communication node (e.g., a secondary node (SN)) to share one or more configuration containers. The one or more configuration containers may include various information associated with a terminal service, and the one or more configuration containers may correspond to different radio access technologies (RATs). The one or more configuration containers may include at least one of a long-term evolution (LTE) configuration container or a new radio (NR) configuration container.

[0112] In some embodiments, the various information may include at least one of a wireless communication device (e.g., an unmanned aerial vehicle (UAV)) identification configured to identify the wireless communication device, wireless communication device service subscription information configured to notify a wireless communication node that the wireless communication device is eligible to use a wireless communication device service, addresses of one or more reporting receivers from which data for the wireless communication device is to be collected, wireless communication device position information configuring wireless communication device position measurements and reports, height report information associated with the wireless communication device, flight path information associated with the wireless communication device, or measurement information including frequency-related information for the wireless communication device.

[0113] In some embodiments, the first wireless communication node may receive a first message including one or more configuration containers from a core network. The first wireless communication node may send a second message including one or more configuration containers to a wireless communication device (e.g., a UE). The first message may be a first communication message. The second message may be a second communication message.

[0114] In some embodiments, the first wireless communication node may receive a first message including one or more configuration containers from a core network. The first wireless communication node may send a second message including the one or more configuration containers to the second wireless communication node. The first message may be a first communication message. The second message may be a third communication message. The one or more configuration containers may be further sent to the wireless communication device via the first communication message.

[0115] In some embodiments, at least a portion of the various information may be reported by the wireless communication device to the core network via a first wireless communication node, reported to the core network via a second wireless communication node, reported first to the core network via the second wireless communication node and then via the first wireless communication node, or reported to the core network first via the first wireless communication node and then via the second wireless communication node.

[0116] In some embodiments, the first wireless communication node may send a first message to a third wireless communication node (e.g., a target node) requesting that the second wireless communication node be changed to the third wireless communication node. The first message may include one or more configuration containers. The first message may be a third communication message.

[0117] In some embodiments, the first wireless communication node may receive a first message from the second wireless communication node requesting to change the second wireless communication node to a third wireless communication node. The first wireless communication node may send a second message to the third wireless communication node, the second message including one or more configuration containers. The first message and the second message may each be a third communication message.

[0118] In some embodiments, a first wireless communication node (e.g., a source MN) may send a first message to a fourth wireless communication node (e.g., a target MN) indicating a handover from the first wireless communication node to the fourth wireless communication node. The first message may be an Xn Application Protocol (XnAP) message and may include one or more configuration containers. The one or more configuration containers included in the first message may be further sent from the fourth wireless communication node to the second wireless communication node via another third communication message.

[0119] In some embodiments, the first wireless communication node may send a first message to the second wireless communication node requesting to add the second wireless communication node. The first message may be a third communication message and may include one or more configuration containers.

[0120] In some embodiments, the first wireless communication node may send a first message to the second wireless communication node requesting to remove the second wireless communication node. The first wireless communication node may receive a second message from the second wireless communication node, the second message including one or more configuration containers. The first message and the second message may each be a third communication message.

[0121] In some embodiments, the first wireless communication node may receive a first message requesting removal of itself from the second wireless communication node. The first message may be a third communication message and may include one or more configuration containers. In a particular embodiment, the first communication message may be a NG Application Protocol (NGAP) message. The second communication message may be a Radio Resource Control (RRC) message. The second communication message may be an Xn Application Protocol (XnAP) message.

[0122] Although various embodiments of the present solution have been described above, it should be understood that they are presented only as examples and not as limitations. Similarly, various figures may depict example architectures or configurations provided to enable those skilled in the art to understand example features and functionality of the present solution. However, as such skilled in the art will appreciate, the solution is not limited to the example architectures or configurations shown, but may be implemented using various alternative architectures and configurations. Furthermore, as those skilled in the art will appreciate, one or more features of one embodiment may be combined with one or more features of another embodiment described herein. Thus, the breadth and scope of the present disclosure should not be limited by any of the exemplary embodiments described above.

[0123] It is also understood that any reference to an element herein using a designation such as "first," "second," etc., does not generally limit the quantity or order of those elements. Rather, these designations may be used herein as a convenient means of distinguishing between two or more elements or instances of an element. Thus, a reference to a first and a second element does not imply that only two elements can be used or that the first element must in any way precede the second element.

[0124] Additionally, as will be appreciated by those skilled in the art, information and signals may be represented using any of a variety of different technologies and techniques. For example, the data, instructions, commands, information, signals, bits and symbols that may be referred to in the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

[0125] As will be appreciated by those skilled in the art, any of the various example logic blocks, modules, processors, means, circuits, methods, and functions described in connection with the aspects disclosed herein may be implemented by electronic hardware (e.g., digital implementations, analog implementations, or a combination of the two), firmware, various forms of programs or design code incorporating instructions (for convenience, referred to herein as "software" or "software modules"), or any combination of these techniques. To clearly illustrate this interchangeability of hardware, firmware, and software, various example components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware, firmware, or software, or a combination of these techniques, depends on the particular application and design constraints imposed on the overall system. Those skilled in the art may implement the described functionality in various ways for each particular application, but such implementation decisions are not intended to depart from the scope of the present disclosure.

[0126] Furthermore, as will be appreciated by those skilled in the art, the various example logic blocks, modules, devices, components, and circuits described herein may be implemented in or executed by an integrated circuit (IC), which may include a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, or any combination thereof. The logic blocks, modules, and circuits may further include an antenna and / or a transceiver for communicating with various components in a network or device. The general purpose processor may be a microprocessor, but alternatively, the processor may be any conventional processor, controller, or state machine. The processor may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in combination with a DSP core, or any other suitable configuration for performing the functions described herein.

[0127] If implemented in software, the functions may be stored as one or more instructions or codes on a computer-readable medium. Thus, the steps of a method or algorithm disclosed herein may be implemented as software stored on a computer-readable medium. Computer-readable media includes both computer storage media and communication media, including any medium that can enable a computer program or code to be transferred from one place to another. A storage medium may be any available medium that can be accessed by a computer. By way of example, and not limitation, such computer-readable media may include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to store desired program code in the form of instructions or data structures and that can be accessed by a computer.

[0128] As used herein, the term "module" refers to software, firmware, hardware, and any combination of these elements for performing the associated functions described herein. Moreover, for purposes of explanation, various modules are described as individual modules. However, as would be apparent to one skilled in the art, two or more modules may be combined to form a single module that performs associated functions according to embodiments of the present solution.

[0129] Furthermore, memory or other storage devices, as well as communication components, may be used in embodiments of the solution. For clarity, it may be appreciated that the above description describes embodiments of the solution with reference to different functional units and processors. However, it will be apparent that any suitable distribution of functionality between different functional units, processing logic elements, or domains may be used without detracting from the solution. For example, functions shown to be performed by separate processing logic elements or controllers may be performed by the same processing logic element or controller. Thus, references to specific functional units do not indicate a strict logical or physical structure or organization, but merely to suitable means for providing the described functionality.

[0130] Various modifications to the embodiments described in this disclosure will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without departing from the scope of the present disclosure. Thus, the present disclosure is not intended to be limited to the embodiments shown herein, but is to be accorded the widest scope consistent with the novel features and principles disclosed herein, as set forth in the following claims.

Claims

1. 1. A wireless communication method, comprising: communicating, by a first wireless communication node, with a second wireless communication node to share one or more configuration containers; 11. A method of wireless communication comprising: one or more configuration containers including various information associated with a terminal service, the one or more configuration containers corresponding to different radio access technologies (RATs).

2. 2. The wireless communication method of claim 1, wherein the one or more configuration containers include at least one of a Long Term Evolution (LTE) configuration container or a New Radio (NR) configuration container.

3. The various information includes: a wireless communication device identification configured to identify the wireless communication device; wireless communication device service subscription information configured to inform the wireless communication node that the wireless communication device is entitled to use a wireless communication device service; the addresses of one or more reporting receivers for which data from the wireless communication device should be collected; wireless communication device location information constituting wireless communication device location measurement and reporting; height reporting information associated with the wireless communication device; flight path information associated with said wireless communication device; or Measurement information including frequency-related information of the wireless communication device The wireless communication method of claim 1 , comprising at least one of:

4. receiving, by the first wireless communication node, from a core network, a first message including the one or more configuration containers; sending, by the first wireless communication node, a second message including the one or more configuration containers to a wireless communication device; Further comprising: The method of claim 1 , wherein the first message is a first communication message and the second message is a second communication message.

5. receiving, by the first wireless communication node, from a core network, a first message including the one or more configuration containers; sending, by the first wireless communication node, a second message including the one or more configuration containers to the second wireless communication node; Further comprising: The method of claim 1 , wherein the first message is a first communication message and the second message is a third communication message.

6. The wireless communication method of claim 5 , wherein the one or more configuration containers are further communicated to the wireless communication device via a second communication message.

7. 2. The wireless communication method according to claim 1, wherein at least a portion of the various information is reported by a wireless communication device to a core network via the first wireless communication node, reported to the core network via the second wireless communication node, reported first to the core network via the second wireless communication node and then to the first wireless communication node, or reported first to the core network via the first wireless communication node and then to the second wireless communication node.

8. sending, by the first wireless communication node, a first message to a third wireless communication node requesting that the second wireless communication node be changed to the third wireless communication node; The method of claim 1 , wherein the first message includes the one or more configuration containers, and the first message is a third communication message.

9. receiving, by the first wireless communication node, from the second wireless communication node, a first message requesting that the second wireless communication node change to a third wireless communication node; sending, by the first wireless communication node, a second message including the one or more configuration containers to the third wireless communication node; Further comprising: The method of claim 1 , wherein the first message and the second message are each a third communication message.

10. sending, by the first wireless communication node, to a fourth wireless communication node, a first message indicating a handover from the first wireless communication node to the fourth wireless communication node; The method of claim 1 , wherein the first message is a third communication message and includes the one or more configuration containers.

11. The wireless communication method of claim 10 , wherein the one or more configuration containers included in the first message are further sent from the fourth wireless communication node to the second wireless communication node via another third communication message.

12. sending, by the first wireless communication node, to the second wireless communication node, a first message requesting that the second wireless communication node be added; The method of claim 1 , wherein the first message is a third communication message and includes the one or more configuration containers.

13. sending, by the first wireless communications node, a first message to the second wireless communications node requesting removal of the second wireless communications node; receiving, by the first wireless communication node, a second message from the second wireless communication node, the second message including the one or more configuration containers; Further comprising: The method of claim 1 , wherein the first message and the second message are each a third communication message.

14. receiving, by the first wireless communication node, from the second wireless communication node, a first message requesting that the second wireless communication node remove itself; The method of claim 1 , wherein the first message is a third communication message and includes the one or more configuration containers.

15. A wireless communication device comprising a processor and a memory, the processor configured to read code from the memory and to implement a method according to any of claims 1 to 14.

16. A computer program product comprising a computer readable program medium code stored thereon, said code, when executed by a processor, causing said processor to implement a method according to any of claims 1 to 14.

Images