Classifications

• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W36/00—Hand-off or reselection arrangements
  • H04W36/0005—Control or signalling for completing the hand-off
  • H04W36/0055—Transmission or use of information for re-establishing the radio link
  • H04W36/0066—Transmission or use of information for re-establishing the radio link of control information between different types of networks in order to establish a new radio link in the target network
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W36/00—Hand-off or reselection arrangements
  • H04W36/0005—Control or signalling for completing the hand-off
  • H04W36/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
  • H04W36/0022—Control or signalling for completing the hand-off for data sessions of end-to-end connection for transferring data sessions between adjacent core network technologies
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W36/00—Hand-off or reselection arrangements
  • H04W36/0005—Control or signalling for completing the hand-off
  • H04W36/0055—Transmission or use of information for re-establishing the radio link
  • H04W36/0058—Transmission of hand-off measurement information, e.g. measurement reports
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W36/00—Hand-off or reselection arrangements
  • H04W36/0005—Control or signalling for completing the hand-off
  • H04W36/0055—Transmission or use of information for re-establishing the radio link
  • H04W36/0061—Transmission or use of information for re-establishing the radio link of neighbour cell information
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W36/00—Hand-off or reselection arrangements
  • H04W36/0005—Control or signalling for completing the hand-off
  • H04W36/0055—Transmission or use of information for re-establishing the radio link
  • H04W36/0064—Transmission or use of information for re-establishing the radio link of control information between different access points
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W36/00—Hand-off or reselection arrangements
  • H04W36/24—Reselection being triggered by specific parameters
  • H04W36/32—Reselection being triggered by specific parameters by location or mobility data, e.g. speed data
  • H04W36/322—Reselection being triggered by specific parameters by location or mobility data, e.g. speed data by location data
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W36/00—Hand-off or reselection arrangements
  • H04W36/24—Reselection being triggered by specific parameters
  • H04W36/32—Reselection being triggered by specific parameters by location or mobility data, e.g. speed data
  • H04W36/328—Reselection being triggered by specific parameters by location or mobility data, e.g. speed data by altitude
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
  • H04W88/02—Terminal devices
  • H04W88/06—Terminal devices adapted for operation in multiple networks or having at least two operational modes, e.g. multi-mode terminals
• • B—PERFORMING OPERATIONS; TRANSPORTING
  • B64—AIRCRAFT; AVIATION; COSMONAUTICS
  • B64U—UNMANNED AERIAL VEHICLES [UAV]; EQUIPMENT THEREFOR
  • B64U2201/00—UAVs characterised by their flight controls

Definitions

• the disclosure relates generally to wireless communications, including but not limited to systems and methods for configuring unmanned aerial vehicle (UAV) service in inter-system and intra-system with inter-radio access technology (RAT) .
• UAV unmanned aerial vehicle
• RAT inter-radio access technology
• the standardization organization Third Generation Partnership Project (3GPP) is currently in the process of specifying a new Radio Interface called 5G New Radio (5G NR) as well as a Next Generation Packet Core Network (NG-CN or NGC) .
• the 5G NR will have three main components: a 5G Access Network (5G-AN) , a 5G Core Network (5GC) , and a User Equipment (UE) .
• 5G-AN 5G Access Network
• 5GC 5G Core Network
• UE User Equipment
• the elements of the 5GC also called Network Functions, have been simplified with some of them being software based, and some being hardware based, so that they could be adapted according to need.
• example embodiments disclosed herein are directed to solving the issues relating to one or more of the problems presented in the prior art, as well as providing additional features that will become readily apparent by reference to the following detailed description when taken in conjunction with the accompany drawings.
• example systems, methods, devices and computer program products are disclosed herein. It is understood, however, that these embodiments are presented by way of example and are not limiting, and it will be apparent to those of ordinary skill in the art who read the present disclosure that various modifications to the disclosed embodiments can be made while remaining within the scope of this disclosure.
• a wireless communication node may send a first message requesting a handover from the first wireless communication node to a second wireless communication node.
• the first message may include one or more configuration containers.
• the one or more configuration containers may include various information associated with a terminal service.
• the first wireless communication node and the second wireless communication node may correspond to respectively different Radio Access Technologies (RATs) .
• RATs Radio Access Technologies
• the various information may include at least one of: wireless communication device (e.g., unmanned aerial vehicle (UAV) ) identification configured to identify a wireless communication device; wireless communication device subscription information configured to notify the wireless communication node that the wireless communication device is qualified to use wireless communication device service; one or more report receiver’s addresses to which wireless communication device data is to be collected; wireless communication device location information configuring wireless communication device location measurement and reporting; height reporting information associated with the wireless communication device; flight path information associated with the wireless communication device; or measurement information including frequency-related information of the wireless communication device.
• wireless communication device e.g., unmanned aerial vehicle (UAV) identification configured to identify a wireless communication device
• wireless communication device subscription information configured to notify the wireless communication node that the wireless communication device is qualified to use wireless communication device service
• one or more report receiver’s addresses to which wireless communication device data is to be collected wireless communication device location information configuring wireless communication device location measurement and reporting; height reporting information associated with the wireless communication device; flight path information associated with the wireless communication device; or measurement information including frequency-related information of
• the one or more configuration containers may have included both of a RAT_A configuration container or a RAT_B configuration container.
• the wireless communication node may send the first message to a core network.
• the second wireless communication node may receive a second message from the core network.
• the second message may include the one or more configuration containers.
• the first wireless communication node and the second wireless communication node may belong to a same wireless communication system. In certain embodiments, the first wireless communication node and the second wireless communication node may belong to respectively different wireless communication systems.
• the first wireless communication node can be a RAT_A node
• the second wireless communication node can be a RAT_B node.
• the RAT_A node can be a Next Generation Radio Access Network (NG-RAN) node
• the RAT_B node can be an Evolved UMTS Terrestrial Radio Access Network (E-UTRAN) node.
• the RAT_A node can be an Evolved UMTS Terrestrial Radio Access Network (E-UTRAN) node
• the RAT_B node can be a Next Generation Radio Access Network (NG-RAN) node.
• the one or more configuration containers may have included only one of a RAT_A configuration container or a RAT_B configuration container.
• the first wireless communication node may send the first message to a core network.
• the second wireless communication node may receive a second message from the core network.
• the second message may include the one or more configuration containers.
• the first wireless communication node and the second wireless communication node may belong to a same wireless communication system. In certain embodiments, the first wireless communication node and the second wireless communication node may belong to respectively different wireless communication systems.
• the first wireless communication node can be a RAT_A node
• the second wireless communication node can be a RAT_B node.
• the RAT_A node can be a Next Generation Radio Access Network (NG-RAN) node
• the RAT_B node can be an Evolved UMTS Terrestrial Radio Access Network (E-UTRAN) node.
• the RAT_A node can be an Evolved UMTS Terrestrial Radio Access Network (E-UTRAN) node
• the RAT_B node can be a Next Generation Radio Access Network (NG-RAN) node.
• the first wireless communication node may optionally send a second message including at least some of the various information and an indicator indicating UAV configuration for the RAT associated with the second wireless communication node to a core network.
• the first wireless communication node may optionally receive a third message in response to the second message from the core network.
• the first wireless communication node may send the first message to the second wireless communication node.
• the one or more configuration containers may include at least one of a RAT_A configuration container or a RAT_B configuration container.
• the RAT_A configuration container can be a Long-Term Evolution (LTE) configuration container.
• the RAT_B configuration container can be a New Radio (NR) configuration container.
• FIG. 1 illustrates an example cellular communication network in which techniques disclosed herein may be implemented, in accordance with an embodiment of the present disclosure
• FIG. 2 illustrates a block diagram of an example base station and a user equipment device, in accordance with some embodiments of the present disclosure
• FIG. 3 illustrates a sequence diagram for 5GS to EPS handover for single-registration mode with N26 interface, in accordance with some embodiments of the present disclosure
• FIG. 4 illustrates a sequence diagram for EPS to 5GS handover using N26 interface during preparation phase, in accordance with some embodiments of the present disclosure
• FIG. 5 illustrates an overall architecture for unmanned aerial vehicle (UAV) service, in accordance with some embodiments of the present disclosure
• FIG. 6 illustrates a sequence diagram for intra-AMF/UPF handover, in accordance with some embodiments of the present disclosure
• FIG. 7 illustrates a sequence diagram for intra-system inter-RAT handover, in accordance with some embodiments of the present disclosure
• FIG. 8 illustrates a sequence diagram for intra-system inter-RAT handover, in accordance with some embodiments of the present disclosure
• FIG. 9 illustrates a sequence diagram for intra-system inter-RAT handover, in accordance with some embodiments of the present disclosure.
• FIG. 10 illustrates a sequence diagram for inter-system handover, in accordance with some embodiments of the present disclosure
• FIG. 11 illustrates a sequence diagram for intra-system handover, in accordance with some embodiments of the present disclosure
• FIG. 12 illustrates a sequence diagram for inter-system handover, in accordance with some embodiments of the present disclosure
• FIG. 13 illustrates a sequence diagram for inter-system handover, in accordance with some embodiments of the present disclosure.
• FIG. 14 illustrates a flow diagram for configuring unmanned aerial vehicle (UAV) service in inter-system and intra-system with inter-radio access technology (RAT) , in accordance with an embodiment of the present disclosure.
• UAV unmanned aerial vehicle
• RAT inter-radio access technology
• FIG. 1 illustrates an example wireless communication network, and/or system, 100 in which techniques disclosed herein may be implemented, in accordance with an embodiment of the present disclosure.
• 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 herein referred to as “network 100.
• NB-IoT narrowband Internet of things
• Such an example network 100 includes a base station 102 (hereinafter “BS 102” ; also referred to as wireless communication node) and a user equipment device 104 (hereinafter “UE 104” ; also referred to as 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 overlaying a geographical area 101.
• the BS 102 and UE 104 are contained within a respective geographic boundary of cell 126.
• Each of the other cells 130, 132, 134, 136, 138 and 140 may include at least one base station operating at its allocated bandwidth to provide adequate radio coverage to its intended users.
• the BS 102 may operate at an allocated channel transmission bandwidth to provide adequate coverage to the UE 104.
• the BS 102 and the UE 104 may communicate via a downlink radio frame 118, and an uplink radio frame 124 respectively.
• Each radio frame 118/124 may be further divided into sub-frames 120/127 which may include data symbols 122/128.
• the BS 102 and UE 104 are described herein as non-limiting examples of “communication nodes, ” generally, which can practice the methods disclosed herein. Such communication nodes may be capable of wireless and/or wired communications, in accordance with various embodiments of the present solution.
• FIG. 2 illustrates a block diagram of an example 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.
• the system 200 may include components and elements configured to support known or conventional operating features that need not be described in detail herein.
• system 200 can be used to communicate (e.g., transmit and receive) data symbols in a wireless communication environment such as the wireless communication environment 100 of Figure 1, as described above.
• 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 module being coupled and interconnected with one another as necessary 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 module being coupled and interconnected with one another as necessary via a data communication bus 240.
• the BS 202 communicates with the UE 204 via a communication channel 250, which can be any wireless channel or other medium suitable for transmission of data as described herein.
• system 200 may further include any number of modules other than the modules shown in Figure 2.
• modules other than the modules shown in Figure 2.
• Those skilled in the art will understand that the various illustrative 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 interchangeability and compatibility of hardware, firmware, and software, various illustrative components, blocks, modules, circuits, and steps are described generally in terms of their functionality. Whether such functionality is implemented as hardware, firmware, or software can depend upon the particular application and design constraints imposed on the overall system. Those familiar with the concepts described herein may implement such functionality in a suitable manner for each particular application, but such implementation decisions should not be interpreted as limiting the scope of the present disclosure.
• the UE transceiver 230 may be referred to herein as an "uplink" transceiver 230 that includes a radio frequency (RF) transmitter and a RF receiver each comprising circuitry that is coupled to the antenna 232.
• a duplex switch (not shown) may alternatively couple the uplink transmitter or receiver to the uplink antenna in time duplex fashion.
• the BS transceiver 210 may be referred to herein as a "downlink" transceiver 210 that includes a RF transmitter and a RF receiver each comprising circuity that is coupled to the antenna 212.
• a downlink duplex switch may alternatively couple the downlink transmitter or receiver to the downlink antenna 212 in time duplex fashion.
• the operations of the two transceiver modules 210 and 230 may be coordinated in time such that the uplink receiver circuitry is coupled to the uplink antenna 232 for reception of transmissions over the wireless transmission link 250 at the same time that the downlink transmitter is coupled to the downlink antenna 212. Conversely, the operations of the two transceivers 210 and 230 may be coordinated in time such that the downlink receiver is coupled to the downlink antenna 212 for reception of transmissions over the wireless transmission link 250 at the same time that the uplink transmitter is coupled to the uplink antenna 232. In some embodiments, there is close time synchronization with a minimal guard time between changes in duplex direction.
• the UE transceiver 230 and the base station transceiver 210 are configured to communicate via the wireless data communication link 250, and cooperate with a suitably configured RF antenna arrangement 212/232 that can support a particular wireless communication protocol and modulation scheme.
• the UE transceiver 210 and the base station transceiver 210 are configured to support industry standards such as the Long Term Evolution (LTE) and emerging 5G standards, and the like. It is understood, however, that the present disclosure is not necessarily limited in application to a particular standard and associated protocols. Rather, the UE transceiver 230 and the base station transceiver 210 may be configured to support alternate, or additional, wireless data communication protocols, including future standards or variations thereof.
• LTE Long Term Evolution
• 5G 5G
• the BS 202 may be an evolved node B (eNB) , a serving eNB, a target eNB, a femto station, or a pico station, for example.
• eNB evolved node B
• the UE 204 may be embodied in various types of user devices such as a mobile phone, a smart phone, a personal digital assistant (PDA) , tablet, laptop computer, wearable computing device, etc.
• PDA personal digital assistant
• the processor modules 214 and 236 may be implemented, or realized, with 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.
• a processor may be realized as a microprocessor, a controller, a microcontroller, a state machine, or the like.
• a processor may also be implemented as a combination of computing devices, e.g., a combination of a digital signal processor and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a digital signal processor core, or any other such configuration.
• the steps of a method or algorithm described in connection with the embodiments disclosed herein may be embodied directly in hardware, in firmware, in a software module executed by processor modules 214 and 236, respectively, or in 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, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art.
• memory modules 216 and 234 may be coupled to the processor modules 210 and 230, respectively, such that the processors modules 210 and 230 can read information from, and write information to, memory modules 216 and 234, respectively.
• the memory modules 216 and 234 may also be integrated into their respective processor modules 210 and 230.
• the memory modules 216 and 234 may each include a cache memory for storing temporary variables or other intermediate information during 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 the processor modules 210 and 230, respectively.
• the network communication module 218 generally represents the hardware, software, firmware, processing logic, and/or other components of the base station 202 that enable bi-directional communication between base station transceiver 210 and other network components and communication nodes configured to communication with the base station 202.
• network communication module 218 may be configured to support internet or WiMAX traffic.
• network communication module 218 provides an 802.3 Ethernet interface such that base station transceiver 210 can communicate with a conventional Ethernet based computer network.
• the network communication module 218 may include a physical interface for connection to the computer network (e.g., Mobile Switching Center (MSC) ) .
• MSC Mobile Switching Center
• the Open Systems Interconnection (OSI) Model (referred to herein as, “open system interconnection model” ) is a conceptual and logical layout that defines network communication used by systems (e.g., wireless communication device, wireless communication node) open to interconnection and communication with other systems.
• the model is broken 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 a logical network and effectively describes computer packet transfer by using different layer protocols.
• the OSI Model may also be referred to as the seven-layer OSI Model or the seven-layer model.
• a first layer may be a physical layer.
• a second layer may be a Medium Access Control (MAC) layer.
• MAC Medium Access Control
• a third layer may be a Radio Link Control (RLC) layer.
• a fourth layer may be a Packet Data Convergence Protocol (PDCP) layer.
• PDCP Packet Data Convergence Protocol
• a fifth layer may be a Radio Resource Control (RRC) layer.
• a sixth layer may be a Non Access Stratum (NAS) layer or an Internet Protocol (IP) layer, and the seventh layer being the other layer.
• NAS Non Access Stratum
• IP Internet Protocol
• Unmanned aerial vehicle (UAV) related features may be supported in Rel-18 new radio (NR) specifications. In some cases, the UAV related features may not be supported in NR.
• the network can transmit a UAV configuration between source and target node during handover. Hence, ongoing UAV functions can continue during/after handover in most cases.
• some UAV features have been supported in LTE.
• a method is introduced in this invention to maintain the UAV service continuity during the inter-system (e.g., between NR and LTE) handover and intra-system inter-radio access technology (RAT) (e.g., between gNB and ng-eNB) handover.
• RAT inter-radio access technology
• the UAV service is supported in LTE specification.
• UAV is not supported in Rel-18 NR specifications.
• WID work item description
• companies may prefer to support the UAV features in NR, and to consider LTE mechanism as baseline.
• the inter-system handover procedure (e.g., from 5GC to EPS and/or from EPS to 5GC) is illustrated in FIG. 3.
• XnAP and NGAP can be used for control plane data transmission between gNB and ng-eNB and/or between ng-eNB and access and mobility management function (AMF) /user plane function (UPF) .
• AMF access and mobility management function
• UPF user plane function
• an inter-system handover (e.g., HO between gNB and eNB with changing 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.
• the CN may be AMF) handover may be performed during a UE mobility.
• AMF access and mobility management function
• MME mobility management entity
• RAT intra-system inter-radio access technology
• the CN may be AMF) handover may be performed during a UE mobility.
• a same UAV related configuration with different encoding/format for both NR and LTE may be configured to a RAN node in a different container.
• the UE may keep using a UAV related function no matter different RATs used between RAN nodes during the HO.
• the UAV configuration containers may be configured to the UE before the HO or during the HO.
• At least one of the following information may be added into both NR and LTE containers: a UAV identification (ID) , UAV subscription information, report receiver’s address (es) , a UAV location configuration, a height reporting configuration, a flight path information configuration, or a measurement configuration.
• the UAV ID can be used/configured to identify a UAV.
• the UAV subscription information can include a flag which is used/configured to notify a RAN node that a UE is qualified to use the UAV service.
• the report receiver’s address can include an IP address or URL for the UAV data collector. Different UAV data types may have the same destination or different destinations.
• the UAV location configuration can include information about UAV location measurement and reporting (e.g., an accurate requirement of the UAV location) , what kinds of positioning methods may be used, a measurement/reporting frequency, and/or an integrity requirement.
• the height reporting configuration can include criteria on when the UE may report its height, measurement/reporting frequency, accuracy of the height measurement, and/or integrity requirement.
• the flight path information configuration can include a UE flight path history or prediction, a formula, a flight path (e.g., a list of cell ID, RAN node ID, coordinates) , a number of points in the flight path list, a timestamp requirement, an accuracy requirement, an integrity requirement, and/or a reporting destination (e.g., IP or URL) .
• the measurement configuration can include UE frequency-related measurement information (e.g., reference signal received power (RSRP) , reference signal received quality (RSRQ) , signal-to-noise and interference ratio (SINR) of cells) .
• FIG. 7 is a call flow for inter-system inter-RAT handover (HO) (containers have been configured before HO) .
• a source node here can be either gNB or ng-eNB.
• the source node and target node may belong to different RATs but use a new radio (NR) core network (CN) .
• NR new radio
• CN core network
• a CN may configure both LTE configuration container and NR configuration container to a NG-RAN node (source node) .
• a source node may send a next generation application protocol (NGAP) message (e.g., Handover Required) to a 5G core (5GC) .
• NGAP next generation application protocol
• UE identification information e.g., UE ID
• UAV identification information e.g., UAV ID
• UAV subscription information can include a flag which is used/configured to notify a RAN node that a UE is qualified to use the UAV service.
• the UAV configuration containers may include LTE configuration container (s) and/or NR configuration container (s) .
• the 5GC may send a NGAP message (e.g., Handover Request) to a target node.
• a NGAP message e.g., Handover Request
• At least one of the following information can be contained in the NGAP message: UE identification information (e.g., UE ID) , UAV identification information (e.g., UAV ID) , UAV subscription information, or UAV configuration containers.
• the UAV subscription information can include a flag which is used/configured to notify a RAN node that a UE is qualified to use the UAV service.
• the UAV configuration containers may include LTE configuration container (s) and/or NR configuration container (s) .
• the target node may receive the NGAP message in step 3 and may reply a NGAP message (e.g., Handover Request ACK) to the 5GC.
• a NGAP message e.g., Handover Request ACK
• the 5GC may reply a NGAP message (e.g., Handover Command) to the source node.
• NGAP message e.g., Handover Command
• the source node may send a radio resource control (RRC) message (e.g., Handover Command) to a UE.
• RRC radio resource control
• FIG. 8 is a call flow for intra-system inter-RAT handover (HO) .
• Containers may be configured during HO.
• a source node here can be either gNB or ng-eNB.
• the source node and target node may belong to different RATs, but both of them may connect to a new radio (NR) core network (CN) (e.g., 5GC) .
• NR new radio
• CN core network
• a CN may configure both LTE configuration container and NR configuration container to a NG-RAN node (source node) .
• a source node may send a next generation application protocol (NGAP) message (e.g., Handover Required) to a 5G core (5GC) .
• NGAP next generation application protocol
• UE identification information e.g., UE ID
• UAV identification information e.g., UAV ID
• UAV subscription information e.g., UAV configuration for only one RAT.
• the UAV subscription information can include a flag which is used/configured to notify a RAN node that a UE is qualified to use the UAV service.
• the UAV configuration for only one RAT can be either NR or LTE, which depends on the source node.
• the CN (5GC) may receive the NGAP message and may find/determine that the UAV configuration can be only for one RAT (either NR or LTE, which depends on source node type) . Another type of the UAV configuration may be added into a NGAP message (e.g., Handover Request) .
• the CN (5GC) may send a NGAP message (e.g., Handover Request) to a target node.
• UE identification information e.g., UE ID
• UAV identification information e.g., UAV ID
• UAV subscription information e.g., or UAV configuration containers.
• the UAV subscription information can include a flag which is used/configured to notify a RAN node that a UE is qualified to use the UAV service.
• the UAV configuration containers may include LTE configuration container (s) and/or NR configuration container (s) .
• the target node may receive the NGAP message in step 3 and may reply a NGAP message (e.g., Handover Request ACK) to the CN (5GC) .
• a NGAP message e.g., Handover Request ACK
• the 5GC may reply a NGAP message (e.g., Handover Command) to the source node.
• NGAP message e.g., Handover Command
• FIG. 9 is a call flow for intra-system inter-RAT handover with Xn-based HO.
• a source node may recognize that a target node may not use same RAT with the source node (e.g., the source node is gNB and the target node is ng-eNB, or vice versa) .
• the source node may only have a UAV configuration for its own RAT.
• the source node may send a NGAP message to a 5GC.
• At least one of the following information can be contained 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 for another RAT indicator.
• the UAV subscription information can include a flag which is used/configured to notify a RAN node that a UE is qualified to use the UAV service.
• the UAV configuration for another RAT indicator may include a flag which is used/configured for the source gNB to require the UAV configuration which has same information but different format/encoding for the target node’s RAT.
• the 5GC may receive the source node’s requirement and may send a reply NGAP message to the source node with 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 for another RAT.
• the UAV subscription information can include a flag which is used/configured to notify a RAN node that a UE is qualified to use the UAV service.
• the UAV configuration for another RAT may include a UAV configuration with same information but different format/encoding for the target node’s RAT.
• the above two procedures are optional. They may only be used when the source node does not has the UAV configuration for the target node’s RAT.
• the source node may send an Xn application protocol (XnAP) message (e.g., Handover Request) to a target node.
• XnAP Xn application protocol
• UE identification information e.g., UE ID
• UAV identification information e.g., UAV ID
• UAV subscription information can include a flag which is used/configured to notify a RAN node that a UE is qualified to use the UAV service.
• the UAV configuration containers may include LTE configuration container (s) and/or NR configuration container (s) .
• the target node may reply a XnAP message (e.g. Handover Request ACK) to the source node.
• a XnAP message e.g. Handover Request ACK
• the source node may a RRC message (e.g., Handover command) to a UE.
• RRC message e.g., Handover command
• FIG. 10 is a call flow for inter-system HO.
• Containers have been configured to NG-RAN before a HO.
• the label “CN” used in this implementation example contains both access and mobility management function (AMF) in NR and mobility management entity (MME) in LTE. An interaction performed between AMF and MME for inter-system handover may not be the key point of this implementation example.
• AMF access and mobility management function
• MME mobility management entity
• a CN may configure both LTE UAV container and NR UAV container to a NG-RAN node (e.g., source node) .
• NG-RAN node e.g., source node
• the CN may forward the received information to a target E-UTRAN node via a S1AP message (e.g., Handover Request) .
• S1AP message e.g., Handover Request
• At least one of the following information may be contained in the S1AP message: UE identification information (e.g., UE ID) , UAV identification information (e.g., UAV ID) , UAV subscription information, or UAV configuration containers.
• the UAV subscription information can include a flag which is used/configured to notify a RAN node that a UE is qualified to use the UAV service.
• the UAV configuration containers may include LTE configuration container (s) and/or NR configuration container (s) .
• the target node may send a reply S1AP message (e.g., Handover Request ACK) to the CN.
• a reply S1AP message e.g., Handover Request ACK
• the source node may send a RRC message (e.g., Handover Command) to a UE.
• a RRC message e.g., Handover Command
• FIG. 11 is a call flow for inter-system HO.
• Containers have been configured to NG-RAN before a HO.
• the label “CN” used in this implementation example contains both access and mobility management function (AMF) in NR and mobility management entity (MME) in LTE. An interaction performed between AMF and MME for inter-system handover may not be the key point of this implementation example.
• AMF access and mobility management function
• MME mobility management entity
• a CN may only configure NR UAV configuration to a NG-RAN node.
• a source node may send a NGAP message (e.g., Handover Required) to a CN (e.g., AMF) .
• a NGAP message e.g., Handover Required
• a CN e.g., AMF
• UE identification information e.g., UE ID
• UAV identification information e.g., UAV ID
• UAV subscription information can include a flag which is used/configured to notify a RAN node that a UE is qualified to use the UAV service.
• the UAV configuration for another RAT indicator may include a flag which is used/configured for the source gNB to require the UAV configuration which has same information but different format/encoding for the target node’s RAT.
• the CN may forward the received information to a target E-UTRAN node via a S1AP message (e.g., Handover Request) .
• S1AP message e.g., Handover Request
• At least one of the following information may be contained in the S1AP message: UE identification information (e.g., UE ID) , UAV identification information (e.g., UAV ID) , UAV subscription information, or UAV configuration containers.
• the UAV subscription information can include a flag which is used/configured to notify a RAN node that a UE is qualified to use the UAV service.
• the UAV configuration containers may include LTE configuration container (s) and/or NR configuration container (s) .
• the target node may send a reply S1AP message (e.g., Handover Request ACK) to the CN.
• a reply S1AP message e.g., Handover Request ACK
• the CN may send a NGAP message (e.g., Handover Command) to the source node.
• NGAP message e.g., Handover Command
• the source node may send a RRC message (e.g., Handover Command) to a UE.
• a RRC message e.g., Handover Command
• FIG. 12 is a call flow for inter-system HO.
• Containers are configured to evolved universal terrestrial radio access network (E-UTRAN) node before a HO.
• E-UTRAN evolved universal terrestrial radio access network
• the label “CN” used in this implementation example contains both access and mobility management function (AMF) in NR and mobility management entity (MME) in LTE. An interaction performed between AMF and MME for inter-system handover may not be the key point of this implementation example.
• AMF access and mobility management function
• MME mobility management entity
• a CN may configure both LTE UAV container and NR UAV container to an E-UTRAN node (e.g., source node) .
• E-UTRAN node e.g., source node
• the source E-UTRAN node may trigger an inter-system handover.
• the source E-UTRAN node may send a S1AP message (e.g., Handover Required) to a CN (e.g., MME) .
• a S1AP message e.g., Handover Required
• a CN e.g., MME
• UAV identification information e.g., UAV ID
• UAV subscription information e.g., UAV ID
• UAV subscription information can include a flag which is used/configured to notify a RAN node that a UE is qualified to use the UAV service.
• the UAV configuration containers may include LTE configuration container (s) and/or NR configuration container (s) .
• the CN may forward the received information to a target NG-RAN node via a NGAP message (e.g., Handover Request) .
• a NGAP message e.g., Handover Request
• At least one of the following information may be contained in the NGAP message: UE identification information (e.g., UE ID) , UAV identification information (e.g., UAV ID) , UAV subscription information, or UAV configuration containers.
• the UAV subscription information can include a flag which is used/configured to notify a RAN node that a UE is qualified to use the UAV service.
• the UAV configuration containers may include LTE configuration container (s) and/or NR configuration container (s) .
• the target node may send a reply NGAP message (e.g., Handover Request ACK) to the CN.
• NGAP message e.g., Handover Request ACK
• the CN may send a S1AP message (e.g., Handover Command) to the source node.
• a S1AP message e.g., Handover Command
• the source node may send a RRC message (e.g., Handover Command) to a UE.
• a RRC message e.g., Handover Command
• FIG. 13 is a call flow for inter-system HO.
• Container may be configured to NG-RAN node during a HO.
• the label “CN” used in this implementation example contains both access and mobility management function (AMF) in NR and mobility management entity (MME) in LTE. An interaction performed between AMF and MME for inter-system handover may not be the key point of this implementation example.
• AMF access and mobility management function
• MME mobility management entity
• a CN may only configure NR UAV container to an E-UTRAN node.
• a source node may send a S1AP message (e.g., Handover Required) to a CN (e.g., MME) .
• a S1AP message e.g., Handover Required
• a CN e.g., MME
• At least one of the following information may be contained in the S1AP message: UE identification information (e.g., UE ID) , UAV identification information (e.g., UAV ID) , UAV subscription information, a UAV configuration for another RAT indicator, or a UAV configuration for LTE.
• the UAV subscription information can include a flag which is used/configured to notify a RAN node that a UE is qualified to use the UAV service.
• the UAV configuration for another RAT indicator may include a flag which is used/configured for the source E-UTRAN node to require the UAV configuration which has same information but different format/encoding for the target node’s RAT (e.g., NR UAV configuration container for the target NG-RAN) .
• RAT e.g., NR UAV configuration container for the target NG-RAN
• the CN may forward the received information to the target NG_RAN node via a NGAP message (e.g., Handover Request) .
• a NGAP message e.g., Handover Request
• At least one of the following information may be contained in the NGAP message: UE identification information (e.g., UE ID) , UAV identification information (e.g., UAV ID) , UAV subscription information, or UAV configuration containers.
• the UAV subscription information can include a flag which is used/configured to notify a RAN node that a UE is qualified to use the UAV service.
• the UAV configuration containers may include LTE configuration container (s) and/or NR configuration container (s) .
• the target node may send a reply NGAP message (e.g., Handover Request ACK) to the CN.
• NGAP message e.g., Handover Request ACK
• the CN may send a NGAP message (e.g., Handover Command) to the source node.
• NGAP message e.g., Handover Command
• the source node may send a RRC message (e.g., Handover Command) to a UE.
• a RRC message e.g., Handover Command
• FIG. 14 illustrates a flow diagram of a method 1400 for the first wireless communication node and the second wireless communication node correspond to respectively different Radio Access Technologies (RATs) .
• the method 1400 may be implemented using any one or more of the components and devices detailed herein in conjunction with FIGs. 1–2.
• the method 1400 may be performed by a wireless communication node, in some embodiments. Additional, fewer, or different operations may be performed in the method 1400 depending on the embodiment. At least one aspect of the operations is directed to a system, method, apparatus, or a computer-readable medium.
• a wireless communication node may send a first message requesting a handover from the first wireless communication node (e.g., a gNB or a ng-eNB) to a second wireless communication node.
• the first message may include one or more configuration containers.
• the one or more configuration containers may include various information associated with a terminal service.
• the first wireless communication node and the second wireless communication node may correspond to respectively different Radio Access Technologies (RATs) .
• RATs Radio Access Technologies
• the various information may include at least one of: wireless communication device (e.g., unmanned aerial vehicle (UAV) ) identification configured to identify a wireless communication device; wireless communication device subscription information configured to notify the wireless communication node that the wireless communication device is qualified to use wireless communication device service; one or more report receiver’s addresses to which wireless communication device data is to be collected; wireless communication device location information configuring wireless communication device location measurement and reporting; height reporting information associated with the wireless communication device; flight path information associated with the wireless communication device; or measurement information including frequency-related information of the wireless communication device.
• wireless communication device e.g., unmanned aerial vehicle (UAV) identification configured to identify a wireless communication device
• wireless communication device subscription information configured to notify the wireless communication node that the wireless communication device is qualified to use wireless communication device service
• one or more report receiver’s addresses to which wireless communication device data is to be collected wireless communication device location information configuring wireless communication device location measurement and reporting; height reporting information associated with the wireless communication device; flight path information associated with the wireless communication device; or measurement information including frequency-related information of
• the one or more configuration containers may have included both of a RAT_A configuration container or a RAT_B configuration container.
• the wireless communication node may send the first message to a core network.
• the second wireless communication node may receive a second message from the core network.
• the second message may include the one or more configuration containers.
• the first wireless communication node and the second wireless communication node may belong to a same wireless communication system. In certain embodiments, the first wireless communication node and the second wireless communication node may belong to respectively different wireless communication systems.
• the first wireless communication node can be a RAT_A node
• the second wireless communication node can be a RAT_B node.
• the RAT_A node can be a Next Generation Radio Access Network (NG-RAN) node
• the RAT_B node can be an Evolved UMTS Terrestrial Radio Access Network (E-UTRAN) node.
• the RAT_A node can be an Evolved UMTS Terrestrial Radio Access Network (E-UTRAN) node
• the RAT_B node can be a Next Generation Radio Access Network (NG-RAN) node.
• the one or more configuration containers may have included only one of a RAT_A configuration container or a RAT_B configuration container.
• the first wireless communication node may send the first message to a core network.
• the second wireless communication node may receive a second message from the core network.
• the second message may include the one or more configuration containers.
• the first wireless communication node and the second wireless communication node may belong to a same wireless communication system. In certain embodiments, the first wireless communication node and the second wireless communication node may belong to respectively different wireless communication systems.
• the first wireless communication node can be a RAT_A node
• the second wireless communication node can be a RAT_B node.
• the RAT_A node can be a Next Generation Radio Access Network (NG-RAN) node
• the RAT_B node can be an Evolved UMTS Terrestrial Radio Access Network (E-UTRAN) node.
• the RAT_A node can be an Evolved UMTS Terrestrial Radio Access Network (E-UTRAN) node
• the RAT_B node can be a Next Generation Radio Access Network (NG-RAN) node.
• the first wireless communication node may optionally send a second message including at least some of the various information and an indicator indicating UAV configuration for the RAT associated with the second wireless communication node to a core network.
• the first wireless communication node may optionally receive a third message in response to the second message from the core network.
• the first wireless communication node may send the first message to the second wireless communication node.
• the one or more configuration containers may include at least one of a RAT_A configuration container or a RAT_B configuration container.
• the RAT_A configuration container can be a Long-Term Evolution (LTE) configuration container.
• the RAT_B configuration container can be a New Radio (NR) configuration container.
• any reference to an element herein using a designation such as “first, “ “second, “ and so forth does not generally limit the quantity or order of those elements. Rather, these designations can be used herein as a convenient means of distinguishing between two or more elements or instances of an element. Thus, a reference to first and second elements does not mean that only two elements can be employed, or that the first element must precede the second element in some manner.
• any of the various illustrative logical blocks, modules, processors, means, circuits, methods and functions described in connection with the aspects disclosed herein can be implemented by electronic hardware (e.g., a digital implementation, an analog implementation, or a combination of the two) , firmware, various forms of program or design code incorporating instructions (which can be referred to herein, for convenience, as "software” or a "software module) , or any combination of these techniques.
• firmware e.g., a digital implementation, an analog implementation, or a combination of the two
• firmware various forms of program or design code incorporating instructions
• software or a “software module”
• IC integrated circuit
• DSP digital signal processor
• ASIC application specific integrated circuit
• FPGA field programmable gate array
• the logical blocks, modules, and circuits can further include antennas and/or transceivers to communicate with various components within the network or within the device.
• a general purpose processor can be a microprocessor, but in the alternative, the processor can be any conventional processor, controller, or state machine.
• a processor can also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other suitable configuration to perform the functions described herein.
• Computer-readable media includes both computer storage media and communication media including any medium that can be enabled to transfer a computer program or code from one place to another.
• a storage media can be any available media that can be accessed by a computer.
• such computer-readable media can 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.
• module refers to software, firmware, hardware, and any combination of these elements for performing the associated functions described herein. Additionally, for purpose of discussion, the various modules are described as discrete modules; however, as would be apparent to one of ordinary skill in the art, two or more modules may be combined to form a single module that performs the associated functions according embodiments of the present solution.
• memory or other storage may be employed in embodiments of the present solution.
• memory or other storage may be employed in embodiments of the present solution.
• any suitable distribution of functionality between different functional units, processing logic elements or domains may be used without detracting from the present solution.
• functionality illustrated to be performed by separate processing logic elements, or controllers may be performed by the same processing logic element, or controller.
• references to specific functional units are only references to a suitable means for providing the described functionality, rather than indicative of a strict logical or physical structure or organization.

Landscapes

• Engineering & Computer Science (AREA)
• Computer Networks & Wireless Communication (AREA)
• Signal Processing (AREA)
• Mobile Radio Communication Systems (AREA)

Applications Claiming Priority (1)

Publications (2)

Family

ID=89848426

Family Applications (1)

Country Status (5)

Families Citing this family (1)

Family Cites Families (9)

• 2022
  • 2022-08-05 KR KR1020247020631A patent/KR20240112317A/ko active Pending
  • 2022-08-05 EP EP22953680.0A patent/EP4445653A4/de active Pending
  • 2022-08-05 WO PCT/CN2022/110689 patent/WO2024026876A1/en not_active Ceased
  • 2022-08-05 CN CN202280097006.8A patent/CN119384840A/zh active Pending
• 2024
  • 2024-06-07 US US18/737,501 patent/US20240357435A1/en active Pending

Also Published As

Similar Documents

Legal Events