System and method for binding information transmission with unmanned autonomous aircraft

Abstract

Aspects of the technical solution may include transmitting, by a first wireless communication entity to a second wireless communication entity, a first message indicating that a first wireless communication device is bound to or unbound from a second wireless communication device; a second message responsive to the first message is received by the first wireless communication entity from the second wireless communication entity.

Description

Technical Field

[0001] The present disclosure relates generally to wireless communications, and more particularly to bound information transmission with unrewed autonomous vehicles (UAVs). Background Art

[0002] Global interest in unmanned aerial vehicle (UAV)-based services has increased dramatically. As governments around the world plan to support urban aerial mobility (UAM) services, 3GPP is expecting traditional 5G NR devices, rather than UAVs, to maintain sufficient data communication quality. Summary of the Invention

[0003] The example arrangements disclosed herein are intended to address issues related to one or more problems encountered in the prior art, as well as to provide additional features that will become apparent by reference to the following detailed description when taken in conjunction with the accompanying drawings. According to various arrangements, example systems, methods, devices, and computer program products are disclosed herein. However, it should be understood that these arrangements are presented by way of example and not limitation, and that various modifications to the disclosed arrangements will be apparent to those skilled in the art having read this disclosure, while remaining within the scope of this disclosure.

[0004] At least one aspect relates to a wireless communication method. The method may include: a first wireless communication entity sending a first message to a second wireless communication entity, wherein the first message indicates binding the first wireless communication device to the second wireless communication device or unbinding the first wireless communication device from the second wireless communication device. The method may also include: the first wireless communication entity receiving a second message from the second wireless communication entity in response to the first message.

[0005] The above-mentioned aspects and other aspects and their embodiments are described in more detail in the drawings, the description and the claims. BRIEF DESCRIPTION OF THE DRAWINGS

[0006] Various example arrangements of the present solution are described in detail below with reference to the following illustrations or drawings. The drawings are provided for illustrative purposes only and depict only example arrangements of the present solution to facilitate the reader's understanding of the present solution. Therefore, the drawings should not be considered limiting of 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.

[0007] Figure 1 An example cellular communication system is shown in accordance with some arrangements.

[0008] Figure 2Shown is a block diagram of an example base station and an example user equipment device according to some arrangements.

[0009] Figure 3 An example network architecture according to the present embodiment is depicted.

[0010] Figure 4 Depicted are example procedures for binding and unbinding a UAV to a UE according to the present embodiment.

[0011] Figure 5 An example binding configuration between a UAV and a UE according to the present embodiment is depicted.

[0012] Figure 6 An example binding configuration between a UAV and a UE according to the present embodiment is depicted.

[0013] Figure 7 An example unbinding configuration between a UAV and a UE according to the present embodiment is depicted.

[0014] Figure 8 Depicted is an example binding information transmission with a UAV according to the present embodiment.

[0015] Figure 9 An example method for transmitting binding information with a UAV according to the present embodiment is described. DETAILED DESCRIPTION

[0016] Various example arrangements of the present solution are described below with reference to the accompanying drawings to enable one of ordinary skill in the art to make and use the present solution. It will be apparent to one of ordinary skill in the art, after reading this disclosure, that various changes or modifications may be made to the examples described herein without departing from the scope of the present solution. Therefore, the present solution is not limited to the example arrangements and applications described and illustrated herein. Furthermore, the specific order or hierarchy of steps in the methods disclosed herein are merely example approaches. Based on design preferences, the specific order or hierarchy of steps of the disclosed methods or processes may be rearranged while remaining within the scope of the present solution. Therefore, it will be understood by one of ordinary skill in the art that the methods and techniques disclosed herein present various steps or actions in a sample order, and unless expressly stated otherwise, the present solution is not limited to the specific order or hierarchy presented.

[0017] Figure 1An example wireless communication system 100 is shown in accordance with an embodiment of the present disclosure, in which the techniques disclosed herein may be implemented. In the following discussion, the wireless communication system 100 may implement any wireless network, such as a cellular network or a narrowband Internet of Things (NB-IoT) network, and is referred to herein as system 100. Such an example system 100 includes a BS 102 and a UE 104, which may 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 covering a geographic area 101. Figure 1 , BS 102 and UE 104 are contained within the respective geographic boundaries of cell 126. Each of the other cells 130, 132, 134, 136, 138, and 140 may include at least one BS operating on its allocated bandwidth to provide adequate radio coverage to its intended users.

[0018] For example, BS 102 can operate on the allocated channel transmission bandwidth to provide sufficient coverage to UE 104. BS 102 and UE 104 can communicate via downlink radio frames 118 and uplink radio frames 124, respectively. Each radio frame 118 / 124 can be further divided into subframes 120 / 127, which can include data symbols 122 / 128. In the present disclosure, BS 102 and UE 104 are described herein as non-limiting examples of "communication nodes," which can generally practice the methods disclosed herein. According to various embodiments of the present solution, such communication nodes can be capable of wireless and / or wired communication.

[0019] In some embodiments, the wireless communication system 100 may support MIMO communication. For example, MIMO is a key technical solution in the New Radio (NR) system. Among other things, MIMO can play a role in both frequency division duplex (FDD) and time division duplex (TDD) systems. MIMO technical solutions can utilize reporting mechanisms such as CSI to support communication. CSI reports can include various types, parts, groups, and fields. The techniques described herein can provide enhancements to various aspects of CSI reporting and reporting processes. For example, a wireless communication device may receive multiple reference signals and configuration parameters from a network via the wireless communication device. The wireless communication device may determine a CSI report based on the multiple reference signals and configuration parameters, wherein the CSI report includes CSI part 1 and CSI part 2. The wireless communication device may report the CSI report to the network. In some cases, the reporting process may include one or more of the following: configuration parameters may be configured to enable two or more CQIs in the CSI report, the reference signal is aperiodic or semi-persistent, and each of the CSI window length, the DD basic unit size, the offset between two CSI reference signal (CSI-RS) resources, and the length of the DD basis vector is greater than or equal to a threshold. Additionally or alternatively, the wireless communication device may send a user equipment (UE) capability report to the network indicating that the wireless communication device supports a certain number of CQI reports, where the number is a positive integer. The wireless communication system may implement a codebook to further support CSI reporting and various other uses.

[0020] Figure 2 A block diagram of an example wireless communication system 200 for transmitting and receiving wireless communication signals (e.g., OFDM / OFDMA signals) according to some embodiments of the present solution is shown. The system 200 may include components and elements configured to support known or conventional operating features that need not be described in detail herein. In one illustrative embodiment, the system 200 may be used to communicate with a wireless communication environment (e.g., a wireless communication environment such as ... Figure 1 The data symbols are communicated (eg, transmitted and received) in the wireless communication environment 100) as described above.

[0021] System 200 generally includes a BS 202 and a UE 204. BS 202 includes a base station (BS) transceiver module 210, a BS antenna 212, a BS processor module 214, a BS memory module 216, and a network communication module 218, each coupled to and interconnected with one another as needed via a data communication bus 220. UE 204 includes a UE transceiver module 230, a UE antenna 232, a UE memory module 234, and a UE processor module 236, each coupled to and interconnected with one another as needed via a data communication bus 240. BS 202 communicates with UE 204 via a communication channel 250, which may be any wireless channel or other medium suitable for data transmission as described herein.

[0022] System 200 may also include Figure 2 Any number of modules other than the modules shown. It will be understood by those skilled in the art that the various illustrative blocks, modules, circuits, and processing logic described in conjunction with the embodiments disclosed herein can be implemented in hardware, computer-readable software, firmware, or any actual combination thereof. In order to clearly illustrate this interchangeability and compatibility of hardware, firmware, and software, various illustrative components, blocks, modules, circuits, and steps are generally described in terms of their functionality. Whether such functionality is implemented as hardware, firmware, or software can depend on the specific application and the design constraints imposed on the entire system. A technician familiar with the concepts described herein can implement such functionality in a manner suitable for each specific application, but such implementation decisions should not be interpreted as limiting the scope of this disclosure.

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

[0024] The UE transceiver 230 and the BS transceiver 210 are configured to communicate via a wireless data communication link 250 and cooperate with an appropriately configured RF antenna arrangement 212 / 232 capable of supporting a specific wireless communication protocol and modulation scheme. In some illustrative embodiments, the UE transceiver 230 and the BS transceiver 210 are configured to support industry standards such as Long Term Evolution (LTE) and emerging 5G and 6G standards. However, it should be understood that the present disclosure is not necessarily limited to specific standards and associated protocols in terms of application. More specifically, the UE transceiver 230 and the BS transceiver 210 can be configured to support alternative or additional wireless data communication protocols, including future standards or variations thereof.

[0025] According to various embodiments, BS202 can be, for example, an evolved Node B (eNB), a serving eNB, a target eNB, a femto station or a micro station. In some embodiments, UE 204 can be various types of user equipment, such as mobile phones, smart phones, personal digital assistants (PDAs), tablet computers, laptop computers, wearable computing devices, etc. Processor modules 214 and 236 can be implemented or implemented 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, and are designed to perform the functions described herein. In this way, the processor can be implemented as a microprocessor, a controller, a microcontroller, a state machine, or the like. The processor can also be implemented as a combination of computing devices, for example, a combination of a digital signal processor and a microprocessor, a plurality of microprocessors, one or more microprocessors combined with a digital signal processor core, or any other such configuration.

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

[0027] The network communication module 218 generally represents the hardware, software, firmware, processing logic and / or other components of BS202, which enable two-way communication between the BS transceiver 210 and other network components and communication nodes configured to communicate with the BS202. For example, the network communication module 218 can be configured to support Internet or WiMAX traffic. In a typical deployment, without limitation, the network communication module 218 provides an 802.3 Ethernet interface so that the BS transceiver 210 can communicate with a computer network based on conventional Ethernet. In this way, the network communication module 218 can include a physical interface for connection to a computer network (e.g., a mobile switching center (MSC)). As used herein with respect to a specified operation or function, the term "configured for...", "configured to..." and its variations refer to a device, component, circuit, structure, machine, signal, etc. that is physically constructed, programmed, formatted and / or arranged to perform a specified operation or function.

[0028] Figure 3 Depicts an example network architecture according to this embodiment. Figure 3 As shown by way of example, the example network architecture 300 may include at least a 5G core 310, NG communication channels 312 and 314, an NG-RAN 320, CU / DU communication channels 352 and 354, and gNB distributed units 360 and 362.

[0029] For example, Figure 3The overall architecture of the control unit / distributed unit (CU / DU) split is shown. As shown in the figure, the 5G core network (5GC or AMF) and NG-RAN nodes are connected via the NG interface. The Xn interface can connect different NG-RAN nodes. The gNB can include a gNB central unit (gNB-CU) and one or more gNB distributed units (gNB-DUs). The gNB-CU and gNB-DU are connected via at least one F1 interface.

[0030] Figure 4 Describes an example process for binding and unbinding a UAV to a UE according to this embodiment. Figure 4 As shown by way of example in FIG, an example process 400 for binding and unbinding a UAV to a UE may include at least a UAV 402, a UE 404, a RAN node 406, an AMF 408, a CN binding determination 410, a binding request message 420, a binding response message 422, configuration by the RAN node 430, a CN unbinding determination 440, an unbinding request message 450, an unbinding response message 452, and configuration by the RAN node 460.

[0031] For example, Figure 4 An example process for binding and unbinding a UAV to a UE is shown. The process may include prerequisites. For example, the UE in this call flow may be a legacy UE type in NR. More specifically, the UE may correspond to a Rel-15 / Rel-16 / Rel-17 UE, or may not correspond to a UAV UE for Rel-18. For example, the specification lacks UAV features.

[0032] For example, by collecting information from both the UE and the UAV, the CN can determine that a particular UE is likely to be accompanying the UAV for a period of time (e.g., the UE is on an aircraft, connected to the UAV by a wire, or inside the UAV as an accessory), and decide to bind the UE to the UAV. Next, for example, the AMF sends a message containing the UAV-UE binding information to the UE's serving RAN node. Next, for example, the RAN node receives the request message and responds with an ACK message. Next, for example, by receiving the binding request message, while the UE remains bound, the RAN node can configure certain UAV-specific features for the UE (e.g., regarding measurements, mobility, etc.) based on the UE's capabilities. For example, after a period of time, the CN may decide to unbind the UAV from the UE (e.g., the UE leaves the UAV). Next, for example, the AMF sends a message containing the unbinding information to the UE's serving RAN node. Next, for example, the RAN node receives the request message and responds with an ACK message to the AMF. Next, for example, the RAN node can reconfigure the UE based on the UE's unbinding state.

[0033] Figure 5 An example binding configuration between a UAV and a UE according to the present embodiment is depicted. Figure 5 As shown by way of example in the figure, an example binding configuration 500 between a UAV and a UE may include at least nodes 510 and 520, a binding communication 530, and a response communication 540. Various aspects of the technical solution relate to a UAV and UE binding configuration. For example, a first node uses an indicator to notify a second node that a UE with a specific UE identifier (UE ID) is to be bound to a UAV with a specific UAV identifier (UAV ID). For example, when the second node receives the information, the second node may treat the UE as a traditional UE with additional UAV features. If the second node is an NG-RAN node, the second node may determine to optimize the UE configuration from the perspective of the UAV. The detailed optimization may depend on the UE capabilities (e.g., in response to a specific version or different versions of the UE) and / or the node capabilities.

[0034] For example, a message sent from a first node to a second node may include at least one of the following. The message may include a UE ID to indicate which UE is to be bound to the UAV. The message may include a UAV ID to indicate which UAV is to be bound to the UE. The message may include a UE-to-UAV binding indicator to indicate that the UE and the UAV are to be bound to each other or have been bound to each other. For example, the first node and the second node may correspond to various entities in a 3GPP network. The above process may be transmitted by using existing processes or newly introduced processes in different fields and is not limited to the examples discussed herein. The above-mentioned patterns may represent various entities in a 3GPP network. The above process may be transmitted by using existing processes or newly introduced processes in different fields.

[0035] Aspects of this technical solution may involve the Next Generation Application Protocol (NGAP). For example, the first node and the second node are the AMF and the NG-RAN node, respectively. For example, if the first node is the AMF, then the second node is the NG-RAN node. For example, if the first node is the NG-RAN node, then the second node is the AMF. For example, the first message and the second message are NGAP messages. For example, if existing procedures are selected for this purpose, one of the following procedures may be used for binding information transmission.

[0036]

[0037] Table 1

[0038] Aspects of this technical solution may involve the Xn Application Protocol (XnAP). For example, the first node and the second node are two NG-RAN nodes. For example, the first message and the second message are XnAP messages. The relationship between the two NG-RAN nodes may be a source node and a target node (in a mobility scenario) or a mobile node and a network node (in a DC scenario). For example, if existing procedures are selected for this purpose, one of the following procedures may be used for binding information transmission:

[0039]

[0040]

[0041] Table 2

[0042] Aspects of this technical solution may involve the F1 Application Protocol (F1AP). For example, if the first node is a gNB-CU, the second node is a gNB-DU. For example, if the first node is a gNB-DU, the second node is a gNB-CU. For example, the first message and the second message are F1AP messages. The UE information may be the existing gNB-CU UE F1AP ID IE and / or gNB-DU UE F1AP ID IE. For example, if existing procedures are selected for this purpose, one of the following procedures may be used for bundling information transmission.

[0043]

[0044] Table 3

[0045] Figure 6 An example binding configuration between a UAV and a UE according to the present embodiment is depicted. Figure 6 As shown by way of example in FIG, an example binding configuration 600 between a UAV and a UE may include at least nodes 610 and 620, a binding communication 630, and a response communication 640. Various aspects relate to a UAV-UE binding configuration with UAV state information. For example, this aspect may be used if the second node does not know the UAV ID prior to the process. The UAV state information is used by the second node to evaluate which UAV is the relevant UAV in the process and which UAV-specific features can be configured for the UE.

[0046] For example, a first node uses an indicator to notify a second node that a UE (marked by UE information) is to be bound to a UAV (with UAV status information). When the second node receives this information, it may treat the UE as a legacy UE with additional UAV features and may determine to optimize the UE configuration from the perspective of the UAV, if the second node is an NG-RAN node. The details of the optimization may depend on the UE capabilities (e.g., UEs of different versions) and / or the capabilities of the nodes involved in the process.

[0047] At least one of the following information may be included in a message sent from a first node to a second node. The message may include UE information for marking which UE can be bound to the UAV. For example, the UE information may be different for different first nodes and second nodes. The message may include UAV status information, which may include UAV status information (e.g., predicted / historical flight path information, UAV altitude information, interference detection information, UAV subscription information, UAV speed information, etc.). The UAV status information can be used by the second node to evaluate which UAV is the relevant UAV in the process, and which UAV specific features can be configured to the UE. The message may include a UE-UAV binding indicator to indicate that the UE and the UAV can be bound to each other. The first node and the second node mentioned above may represent various entities in a 3GPP network. The above process can be transmitted by using existing processes in different fields or newly introduced processes.

[0048] Aspects of this technical solution may involve the NG Application Protocol (NGAP). For example, the first node is an AMF and the second node is an NG-RAN node. For example, the first message and the second message are NGAP messages. For example, the UE information may be defined as an AMF UE NGAP ID IE and a RAN UE NGAP ID IE. For example, if existing procedures are selected for this purpose, one of the following may be used for binding information transmission.

[0049]

[0050]

[0051] Table 4

[0052] Aspects of this technical solution may involve the Xn Application Protocol (XnAP). For example, the first node and the second node are two NG-RAN nodes. For example, the first message and the second message are XnAP messages. For example, the relationship between the two NG-RAN nodes may be a source node and a target node (in a mobility scenario) or a mobile node and a network node (in NR-DC, EN-DC, or NE-DC). The UE information may correspond to an existing NG-RAN node UE XnAP ID IE. For example, if an existing procedure is selected for this purpose, one of the following may be used for binding information transmission.

[0053]

[0054] Table 5

[0055] Aspects of this technical solution may involve the F1 Application Protocol (F1AP). For example, if the first node is a gNB-CU, the second node is a gNB-DU. For example, if the first node is a gNB-DU, the second node is a gNB-CU. For example, the first message and the second message are F1AP messages. For example, the UE information may be an existing gNB-CU UE F1AP ID IE and / or a gNB-DU UE F1AP ID IE. For example, if an existing procedure is selected for this purpose, one of the following procedures may be used for bundling information transmission. If an existing procedure is selected for this purpose, one of the following procedures may be used for bundling information transmission:

[0056] First News Second message UE CONTEXT SETUP REQUEST UE CONTEXT SETUP RESPONSE UE CONTEXT MODIFICATION REQUEST UE CONTEXT MODIFICATION RESPONSE UE CONTEXT MODIFICATION REQUIRED UE CONTEXT MODIFICATION CONFIRM

[0057] Table 6

[0058] Figure 7 An example debinding configuration between a UAV and a UE according to the present embodiment is depicted. Figure 7 As shown by way of example in the accompanying drawings, an example unbinding configuration 700 between a UAV and a UE may include at least nodes 710 and 720, an unbinding communication 730, and a response communication 740. Various aspects of the technical solution may relate to unbinding configurations between the UAV and the UE. For example, prior to the unbinding process, the UE and the UAV may be bound based on the received configuration, as discussed herein. In response to a change in state or conditional satisfaction (e.g., the UE leaves the range of the UAV), the first node may send unbinding information to the second node. For example, the first node uses an indicator to notify the second node that a UE with a specific UE ID is unbound from a UAV with a specific UAV ID. When the second node receives the information, the second node may treat the specific UE as a traditional UE without any UAV features, and may determine whether to modify the current configuration of the UE.

[0059] For example, a message sent from the first node to the second node may include at least one of the following: The message may include a UE ID to indicate which UE is to be bound to the UAV. The message may include a UAV ID to indicate which UAV is to be bound to the UE. The message may include a UE-UAV debinding indicator to indicate that the UE and the UAV are to be debinded. The first node and the second node mentioned above may represent various entities in a 3GPP network.

[0060] Aspects of this technical solution may involve the Next Generation Application Protocol (NGAP). For example, the first node is an AMF and the second node is an NG-RAN node. For example, the first message and the second message are NGAP messages. For example, if existing procedures are selected for this purpose, one of the following may be used for binding information transmission.

[0061] First News Second message HANDOVER REQUEST HANDOVER REQUEST ACKNOWLEDGE UE CONTEXT SUSPEND REQUEST UE CONTEXT SUSPEND RESPONSE UE CONTEXT RESUME REQUEST UE CONTEXT RESUME RESPONSE

[0062] Table 7

[0063] Aspects of this technical solution may involve the Xn Application Protocol (XnAP). For example, the first node and the second node are two NG-RAN nodes. For example, the first message and the second message are XnAP messages. For example, the relationship between the two NG-RAN nodes may be a source node and a target node (in a mobility scenario) or a mobile node and a network node (in NR-DC, EN-DC, or NE-DC). The UE information may correspond to an existing NG-RAN node UE XnAP ID IE. For example, if an existing procedure is selected for this purpose, one of the following may be used for binding information transmission.

[0064]

[0065]

[0066] Table 8

[0067] Aspects of this technical solution may involve the F1 Application Protocol (F1AP). For example, if the first node is a gNB-CU, the second node is a gNB-DU. For example, if the first node is a gNB-DU, the second node is a gNB-CU. For example, the first message and the second message are F1AP messages. For example, if existing procedures are selected for this purpose, one of the following procedures may be used for bundling information transmission.

[0068] First News Second message UE CONTEXT SETUP REQUEST UE CONTEXT SETUP RESPONSE UE CONTEXT MODIFICATION REQUEST UE CONTEXT MODIFICATION RESPONSE UE CONTEXT MODIFICATION REQUIRED UE CONTEXT MODIFICATION CONFIRM

[0069] Table 9

[0070] Figure 8 An example binding information transmission with a UAV according to the present embodiment is depicted. At least UE 104, BS 102, or UAV 402 may perform method 800. At 810, method 800 may include a first wireless communication entity sending a first message to a second wireless communication entity, wherein the first message indicates binding the first wireless communication device to the second wireless communication device or unbinding the first wireless communication device from the second wireless communication device. At 820, method 800 may include a first wireless communication entity receiving a first message from the second wireless communication entity, wherein the first message indicates binding the first wireless communication device to the second wireless communication device or unbinding the first wireless communication device from the second wireless communication device. At 830, method 800 may include a second wireless communication entity sending a second message to the first wireless communication entity in response to the first message. At 840, method 800 may include a second message received by the first wireless communication entity from the second wireless communication entity in response to the first message.

[0071] Figure 9 An example method for transmitting binding information with a UAV according to the present embodiment is described. At least UE 104, BS 102, or UAV 402 may perform method 900. At 910, method 900 may send a first message. At 912, method 900 may be sent by a first wireless communication entity to a second wireless communication entity. At 914, method 900 may send, wherein the first message indicates binding the first wireless communication device to the second wireless communication device. At 916, method 900 may send, wherein the first message indicates unbinding the first wireless communication device from the second wireless communication device. At 920, method 900 may receive a second message in response to the first message. At 922, method 900 may be received by the first wireless communication entity from the second wireless communication entity.

[0072] For example, in a wireless communication method, a first message includes an identifier of a first wireless communication device. The method may include an identifier of a second wireless communication device. The method may include an indicator indicating that the first wireless communication device and the second wireless communication device should be bound to each other.

[0073] For example, in a wireless communication method, the first wireless communication entity is an access and mobility management function (AM) entity, and the second wireless communication entity is a next generation random access network (NG-RAN) node. For example, in the wireless communication method, each of the first message and the second message is a next generation application protocol (NGAP) message. For example, in the wireless communication method, the first wireless communication entity is a first NG-RAN node, and the second wireless communication entity is a second NG-RAN node.

[0074] For example, in the wireless communication method, each of the first message and the second message is an Xn Application Protocol (XnAP) message. For example, in the wireless communication method, the first wireless communication entity is a source node, and the second wireless communication entity is a destination node. For example, in the wireless communication method, the first wireless communication entity is a master node, and the second wireless communication entity is a slave node.

[0075] For example, in a wireless communication method, the first wireless communication entity is a gNodeB control unit (gNB-CU), and the second wireless communication entity is a gNodeB distributed unit (gNB-DU). For example, in the wireless communication method, the first wireless communication entity is a gNodeB distributed unit (gNB-DU), and the second wireless communication entity is a gNodeB control unit (gNB-CU). For example, in the wireless communication method, each of the first message and the second message is an F1 Application Protocol (FIAP) message. For example, in the wireless communication method, the first message includes an identification of the first wireless communication device. The method may include status information of the second wireless communication device. The method may include an indicator indicating that the first wireless communication device and the second wireless communication device should be bound to each other.

[0076] For example, in a wireless communication method, the first wireless communication entity is an access and mobility management function (AMF) entity, and the second wireless communication entity is a next-generation random access network (NG-RAN) node. For example, in the wireless communication method, each of the first message and the second message is a next-generation application protocol (NGAP) message. For example, in the wireless communication method, the first wireless communication entity is a first NG-RAN node, and the second wireless communication entity is a second NG-RAN node. For example, in the wireless communication method, each of the first message and the second message is an Xn application protocol (XAP) message. For example, in the wireless communication method, the first wireless communication entity is a source node, and the second wireless communication entity is a target node. For example, in the wireless communication method, the first wireless communication entity is a master node, and the second wireless communication entity is a slave node.

[0077] For example, in a wireless communication method, the first wireless communication entity is a gNodeB control unit (gNB-CU), and the second wireless communication entity is a gNodeB distributed unit (gNB-DU). For example, in a wireless communication method, the first wireless communication entity is a gNodeB distributed unit (gNB-DU), and the second wireless communication entity is a gNodeB control unit (gNB-CU). For example, the wireless communication method according to claim 19 or 20, wherein each of the first message and the second message is an F1 Application Protocol (FIAP) message. For example, in the wireless communication method, the first message includes an identifier of the first wireless communication device. The method may include an identifier of the second wireless communication device and an indicator indicating that the first wireless communication device and the second wireless communication device should be debound from each other.

[0078] For example, in a wireless communication method, the first wireless communication entity is an access and mobility management function (AMF) entity, and the second wireless communication entity is a next-generation random access network (NG-RAN) node. For example, in the wireless communication method, each of the first message and the second message is a next-generation application protocol (NGAP) message. For example, in the wireless communication method, the first wireless communication entity is a first NG-RAN node, and the second wireless communication entity is a second NG-RAN node. For example, in the wireless communication method, each of the first message and the second message is an Xn application protocol (XnAP) message. For example, in the wireless communication method, the first wireless communication entity is a source node, and the second wireless communication entity is a target node. For example, in the wireless communication method, the first wireless communication entity is a master node, and the second wireless communication entity is a slave node.

[0079] For example, in the wireless communication method, the first wireless communication entity is a gNodeB control unit (sNB-CU), and the second wireless communication entity is a gNodeB distributed unit (gNB-DU). For example, in the wireless communication method, the first wireless communication entity is a gNodeB distributed unit (gNB-DU), and the second wireless communication entity is a gNodeB control unit (gNB-CU). For example, the wireless communication method according to claim 29 or 30, wherein each of the first message and the second message is an F1 Application Protocol (FIAP) message.

[0080] At least one aspect relates to a wireless communication device, which may include at least one processor and memory, wherein the at least one processor is configured to read code from the memory and implement a technical solution. At least one aspect relates to a computer program product, which may include a computer-readable program medium having code stored thereon, the code, when executed by the at least one processor, causing the at least one processor to implement the technical solution.

[0081] Although various arrangements of the present solution have been described above, it should be understood that they are presented by way of example only and not by way of limitation. Similarly, various diagrams may depict example architectures or configurations, which are provided to enable those of ordinary skill in the art to understand the example features and functions of the present solution. However, it will be understood by those skilled in the art that the present solution is not limited to the example architectures or configurations shown, but may be implemented using a variety of alternative architectures and configurations. In addition, as will be understood by those of ordinary skill in the art, one or more features of some arrangements may be combined with one or more features of other arrangements described herein. Therefore, the breadth and scope of the present disclosure should not be limited by any of the illustrative arrangements described above.

[0082] It should also be understood that any reference to an element herein using names such as "first," "second," etc. does not generally limit the quantity or order of those elements. Rather, these names 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 element and a second element does not mean that only two elements are used, or that the first element must precede the second element in some manner.

[0083] Furthermore, it will be understood by those skilled in the art that information and signals may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, and symbols mentioned in the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or magnetic particles, light fields or optical particles, or any combination thereof.

[0084] It will also be understood by those of ordinary skill in the art that any of the various illustrative logical blocks, modules, processors, devices, circuits, methods, and functions described in conjunction with the aspects disclosed herein may be implemented by electronic hardware (e.g., digital implementation, analog implementation, or a combination of both), firmware, various forms of programs or design code incorporating instructions (which, for convenience, may be referred to herein as "software" or "software modules"), or any combination of these technologies. To clearly illustrate this interchangeability of hardware, firmware, and software, various illustrative 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 technologies depends on the specific application and the design constraints imposed on the overall system. A skilled person may implement the described functionality in various ways for each specific application, but such implementation decisions do not result in a departure from the scope of this disclosure.

[0085] In addition, it will be understood by those skilled in the art that the various illustrative logic blocks, modules, devices, components and circuits described herein may be implemented within or performed 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 also include an antenna and / or a transceiver to communicate with various components within a network or within a device. The general-purpose processor may be a microprocessor, but in an alternative, the processor may be any conventional processor, controller or state machine. The processor may also be implemented as a combination of computing devices, for example, a combination of a DSP and a microprocessor, a combination of multiple microprocessors, a combination of one or more microprocessors in conjunction with a DSP core, or a combination of any other suitable configuration to perform the functions described herein.

[0086] 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 the methods or algorithms disclosed herein may be implemented as software stored on a computer-readable medium. Computer-readable media include both computer storage media and communication media, including any medium that enables 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 device, 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.

[0087] In this document, the term "module" as used herein refers to software, firmware, hardware, and any combination of these elements for performing the associated functions described herein. In addition, for the purposes of discussion, various modules are described as separate modules; however, it will be apparent to one of ordinary skill in the art that two or more modules can be combined to form a single module that performs the associated functions according to the arrangement of the present solution.

[0088] In addition, memory or other storage devices and communication components can be used in the arrangement of the present solution. It will be appreciated that, for the sake of clarity, the above description has described the arrangement of the present solution with reference to different functional units and processors. However, it is clear that any suitable functional distribution between different functional units, processing logic elements or domains can be used without departing from the present solution. For example, functionality shown as being performed by a separate processing logic element or controller can be performed by the same processing logic element or controller. Therefore, reference to a particular functional unit is merely a reference to a suitable device for providing the described functionality, rather than indicating a strict logical or physical structure or organization.

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

Claims

1. A wireless communication method, comprising: Sending, by a first wireless communication entity, a first message to a second wireless communication entity, wherein the first message indicates binding the first wireless communication device to the second wireless communication device or unbinding the first wireless communication device from the second wireless communication device; A second message is received by the first wireless communication entity from the second wireless communication entity in response to the first message.

2. The wireless communication method according to claim 1, wherein: The first message includes: an identifier of the first wireless communication device; an identification of the second wireless communication device; and An indicator indicating that the first wireless communication device and the second wireless communication device should be bound to each other.

3. The wireless communication method according to claim 2, wherein: The first wireless communication entity is an Access and Mobility Management Function (AMF) entity, and the second wireless communication entity is a Next Generation Random Access Network (NG-RAN) node.

4. The wireless communication method according to claim 3, wherein: Each of the first message and the second message is a Next Generation Application Protocol (NGAP) message.

5. The wireless communication method according to claim 2, wherein: The first wireless communication entity is a first NG-RAN node, and the second wireless communication entity is a second NG-RAN node. The wireless communication method according to claim 5 , wherein: Each of the first message and the second message is an Xn Application Protocol (XnAP) message.

7. The wireless communication method according to claim 5, wherein: The first wireless communication entity is a source node, and the second wireless communication entity is a target node. The wireless communication method according to claim 5 , wherein: The first wireless communication entity is a master node, and the second wireless communication entity is a slave node.

9. The wireless communication method according to claim 2, wherein: The first wireless communication entity is a gNodeB control unit (gNB-CU), and the second wireless communication entity is a gNodeB distributed unit (gNB-DU).

10. The wireless communication method according to claim 2, wherein: The first wireless communication entity is a gNodeB distributed unit (gNB-DU), and the second wireless communication entity is a gNodeB control unit (gNB-CU).

11. The wireless communication method according to claim 9 or 10, wherein: Each of the first message and the second message is an F1 Application Protocol (F1AP) message.

12. The wireless communication method according to claim 1, wherein: The first message includes: an identifier of the first wireless communication device; Status information of the second wireless communication device; and An indicator indicating that the first wireless communication device and the second wireless communication device should be bound to each other.

13. The wireless communication method according to claim 12, wherein: The first wireless communication entity is an Access and Mobility Management Function (AMF) entity, and the second wireless communication entity is a Next Generation Random Access Network (NG-RAN) node.

14. The wireless communication method according to claim 13, wherein: Each of the first message and the second message is a Next Generation Application Protocol (NGAP) message.

15. The wireless communication method according to claim 12, wherein: The first wireless communication entity is a first NG-RAN node, and the second wireless communication entity is a second NG-RAN node.

16. The wireless communication method according to claim 15, wherein: Each of the first message and the second message is an Xn Application Protocol (XnAP) message.

17. The wireless communication method according to claim 15, wherein: The first wireless communication entity is a source node, and the second wireless communication entity is a target node.

18. The wireless communication method according to claim 15, wherein: The first wireless communication entity is a master node, and the second wireless communication entity is a slave node.

19. The wireless communication method according to claim 12, wherein: The first wireless communication entity is a gNodeB control unit (gNB-CU), and the second wireless communication entity is a gNodeB distributed unit (gNB-DU).

20. The wireless communication method according to claim 12, wherein: The first wireless communication entity is a gNodeB distributed unit (gNB-DU), and the second wireless communication entity is a gNodeB control unit (gNB-CU).

21. The wireless communication method according to claim 19 or 20, wherein: Each of the first message and the second message is an F1 Application Protocol (F1AP) message.

22. The wireless communication method according to claim 1, wherein: The first message includes: an identifier of the first wireless communication device; an identification of the second wireless communication device; and An indicator indicating that the first wireless communication device and the second wireless communication device should be unbound from each other.

23. The wireless communication method according to claim 22, wherein: The first wireless communication entity is an Access and Mobility Management Function (AMF) entity, and the second wireless communication entity is a Next Generation Random Access Network (NG-RAN) node.

24. The wireless communication method according to claim 23, wherein: Each of the first message and the second message is a Next Generation Application Protocol (NGAP) message.

25. The wireless communication method according to claim 22, wherein: The first wireless communication entity is a first NG-RAN node, and the second wireless communication entity is a second NG-RAN node.

26. The wireless communication method according to claim 25, wherein: Each of the first message and the second message is an Xn Application Protocol (XnAP) message.

27. The wireless communication method according to claim 25, wherein: The first wireless communication entity is a source node, and the second wireless communication entity is a target node.

28. The wireless communication method according to claim 25, wherein: The first wireless communication entity is a master node, and the second wireless communication entity is a slave node.

29. The wireless communication method according to claim 22, wherein: The first wireless communication entity is a gNodeB control unit (gNB-CU), and the second wireless communication entity is a gNodeB distributed unit (gNB-DU).

30. The wireless communication method according to claim 22, wherein: The first wireless communication entity is a gNodeB distributed unit (gNB-DU), and the second wireless communication entity is a gNodeB control unit (gNB-CU).

31. The wireless communication method according to claim 29 or 30, wherein: Each of the first message and the second message is an F1 Application Protocol (F1AP) message.

32. A wireless communication device comprising at least one processor and a memory, wherein the at least one processor is configured to read code from the memory and implement the method according to any one of claims 1 to 31.

33. A computer program product comprising a computer readable program medium having code stored thereon, said code, when executed by at least one processor, causing said at least one processor to carry out the method according to any one of claims 1 to 31.

Images