Method by which user equipment performs communication in wireless communication system and apparatus therefor

Abstract

A method by which a UE performs handover, and an apparatus therefor, according to various embodiments, are disclosed. The UE may transmit information about a predicted movement path to a first base station and receive a handover (HO) command targeting a second base station, wherein the HO command may include timing advance (TA) information and uplink resource information for the second base station reserved on the basis of the predicted movement path.

Description

Method for a terminal to perform communication in a wireless communication system and device therefor

[0001] The present invention relates to a method for a terminal to perform handover in a wireless communication system and a device therefor.

[0002] Wireless communication systems are multiple access systems that support communication with multiple users by sharing available system resources (e.g., bandwidth, transmission power, etc.). Examples of multiple access systems include code division multiple access (CDMA), frequency division multiple access (FDMA), time division multiple access (TDMA), orthogonal frequency division multiple access (OFDMA), single carrier frequency division multiple access (SC-FDMA), and multi-carrier frequency division multiple access (MC-FDMA).

[0003] Sidelink (SL) refers to a communication method that establishes a direct link between user equipment (UE), allowing voice or data to be exchanged directly between terminals without going through a base station (BS). SL is being considered as a solution to address the burden on base stations due to rapidly increasing data traffic.

[0004] V2X (vehicle-to-everything) refers to a communication technology that exchanges information with other vehicles, pedestrians, and infrastructure-based objects through wired / wireless communication. V2X can be divided into four types: V2V (vehicle-to-vehicle), V2I (vehicle-to-infrastructure), V2N (vehicle-to-network), and V2P (vehicle-to-pedestrian). V2X communication can be provided through the PC5 interface and / or Uu interface.

[0005] Meanwhile, as more and more communication devices demand greater communication capacity, the need for improved mobile broadband communication compared to existing radio access technology (RAT) is emerging. Accordingly, communication systems that consider services or terminals sensitive to reliability and latency are being discussed. Next-generation wireless access technologies that consider improved mobile broadband communication, massive machine type communication (MTC), and ultra-reliable and low latency communication (URLLC) can be called new radio access technology (RAT) or new radio (NR). NR can also support vehicle-to-everything (V2X) communication.

[0006] Figure 1 is a diagram for comparing and explaining V2X communication based on RAT before NR and V2X communication based on NR.

[0007] In relation to V2X communication, in RATs prior to NR, methods for providing safety services based on V2X messages such as Basic Safety Message (BSM), Cooperative Awareness Message (CAM), and Decentralized Environmental Notification Message (DENM) were mainly discussed. V2X messages may include location information, dynamic information, attribute information, etc. For example, a terminal may transmit a CAM of a periodic message type and / or a DENM of an event triggered message type to another terminal.

[0008] For example, a CAM may include basic vehicle information such as dynamic vehicle status information, such as direction and speed, static vehicle data, such as dimensions, external lighting conditions, and route history. For example, a terminal may broadcast a CAM, and the latency of the CAM may be less than 100 ms. For example, in the event of an emergency, such as a vehicle breakdown or accident, a terminal may generate a DENM and transmit it to other terminals. For example, all vehicles within the transmission range of the terminal may receive the CAM and / or DENM. In this case, the DENM may have a higher priority than the CAM.

[0009] Since then, various V2X scenarios have been proposed in NR in relation to V2X communications. For example, various V2X scenarios may include vehicle platooning, advanced driving, extended sensors, and remote driving.

[0010] For example, based on vehicle platooning, vehicles can dynamically form groups and move together. For example, to perform platoon operations based on vehicle platooning, vehicles in the group can receive periodic data from the lead vehicle. For example, vehicles in the group can use this periodic data to narrow or widen the gap between vehicles.

[0011] For example, based on improved driving, vehicles can become semi-autonomous or fully automated. For example, each vehicle can adjust its trajectories or maneuvers based on data acquired from local sensors of nearby vehicles and / or nearby logical entities. Furthermore, for example, each vehicle can share driving intentions with nearby vehicles.

[0012] For example, based on extended sensors, raw data, processed data, or live video data acquired through local sensors can be exchanged between vehicles, logical entities, pedestrian terminals, and / or V2X application servers. Thus, for example, a vehicle can perceive its environment better than it can perceive using its own sensors.

[0013] For example, based on remote driving, a remote driver or V2X application can operate or control the remote vehicle for people who cannot drive or for remote vehicles located in hazardous environments. For example, in cases where the route is predictable, such as public transportation, cloud computing-based driving can be utilized to operate or control the remote vehicle. Additionally, access to a cloud-based back-end service platform, for example, can be considered for remote driving.

[0014] Meanwhile, a method to specify service requirements for various V2X scenarios, such as vehicle platooning, enhanced driving, expanded sensors, and remote driving, is being discussed in NR-based V2X communication.

[0015] The technical problem to be solved by the present invention is to provide a method for performing a handover procedure more accurately and efficiently.

[0016] The technical challenges are not limited to the technical challenges mentioned above, and other technical challenges not mentioned will be clearly understood by those skilled in the art to which the present invention pertains from the description below.

[0017] A method by a UE (user equipment) according to one aspect includes the steps of transmitting information on a predicted movement path of the UE to a first base station; and receiving a handover (HO) command targeting a second base station; wherein the HO command may include TA (Timing Advance) information and uplink resource information for the second base station reserved based on the predicted movement path.

[0018] Alternatively, the HO command is characterized in that it further includes information about a specific area and a specific time period in which the TA information and the uplink resource information are valid.

[0019] Alternatively, based on the UE operating within the specific time interval being located in the specific area, the UE transmits an initial message for performing a HO procedure to the second base station based on the TA information and the uplink resource information.

[0020] Alternatively, the HO procedure is characterized in that it is performed without performing a RACH (Random Access Channel) procedure for the second base station.

[0021] Alternatively, the initial message is characterized as being an RRCReconfigurationComplete message for completion of the HO procedure.

[0022] Alternatively, the TA information is characterized in that it includes a plurality of candidate TA values ​​corresponding to a plurality of locations.

[0023] Alternatively, the HO command is characterized in that it is determined based on the predicted movement path.

[0024] Alternatively, based on the fact that the HO command includes information about a plurality of candidate target base stations, the HO command is characterized in that it further includes the TA information and the uplink resource information reserved for each of the plurality of candidate target base stations.

[0025] Alternatively, the UE is associated with an Unmanned Aerial Vehicle (UAV), and the predicted movement path is characterized by being a flight path of the UAV.

[0026] According to another aspect, at least one non-transitory computer-readable storage medium having recorded thereon instructions for performing the method described above may be provided.

[0027] According to another aspect, a UE performing the above-described method may be provided.

[0028] According to another aspect, a processing device may be provided for controlling a UE performing the above-described method.

[0029] According to another aspect, a method by a first base station includes the steps of: receiving information on a predicted movement path of a user equipment (UE); and transmitting a handover (HO) command targeting a second base station to the UE; wherein the HO command may include TA (Timing Advance) information and uplink resource information for the second base station reserved based on the predicted movement path.

[0030] According to another aspect, a first base station performing the method described above may be provided.

[0031] According to one embodiment of the present invention, a handover procedure can be performed more accurately and efficiently in a wireless communication system. Alternatively, the performance of a RACH-less HO procedure can be effectively supported for a UE that has provided a predicted movement path.

[0032] The effects that can be obtained in various embodiments are not limited to the effects mentioned above, and other effects not mentioned will be clearly understood by those skilled in the art to which the present invention pertains from the description below.

[0033] The drawings attached to this specification are intended to provide an understanding of the present invention, illustrate various embodiments of the present invention, and together with the description of the specification serve to explain the principles of the present invention.

[0034] Figure 1 is a diagram for comparing and explaining V2X communication based on RAT before NR and V2X communication based on NR.

[0035] Figure 2 shows the structure of the LTE system.

[0036] Figure 3 shows the structure of the NR system.

[0037] Figure 4 shows the structure of a radio frame of NR.

[0038] Figure 5 shows the slot structure of an NR frame.

[0039] FIG. 6 illustrates a communication structure that can be provided in a 6G system according to one embodiment of the present disclosure.

[0040] FIG. 7 illustrates an electromagnetic spectrum according to one embodiment of the present disclosure.

[0041] Figure 8 shows a radio protocol architecture for SL communication.

[0042] Figure 9 shows a terminal performing V2X or SL communication.

[0043] Figure 10 shows resource units for V2X or SL communication.

[0044] FIG. 11 illustrates an example of a BWP according to one embodiment of the present disclosure.

[0045] FIG. 12 illustrates a procedure for a terminal to perform V2X or SL communication according to a resource allocation mode, according to one embodiment of the present disclosure.

[0046] Figure 13 illustrates a procedure for path switching from a direct path to an indirect path.

[0047] Figure 14 schematically illustrates how to switch from a direct route to an indirect route.

[0048] FIG. 15 and FIG. 16 are diagrams for explaining a procedure for U2U relay selection (UE-to-UE Relay Selection) without relay discovery.

[0049] Figure 17 schematically illustrates a flat protocol stack for L2 U2U relay.

[0050] Figures 18 to 22 are drawings for explaining the U2X system.

[0051] Figures 19 to 27 are diagrams illustrating how a UAV performs handover with respect to a satellite gNB.

[0052] Figures 28 to 30 are diagrams for explaining the HO procedure related to a UAV UE moving through the coverage area of ​​gNB (A) to the coverage area of ​​gNB (b).

[0053] Figure 31 is a diagram for explaining how a terminal performs handover (HO).

[0054] Figure 32 is a diagram for explaining a method for a first base station to transmit a handover (HO) command to a UE.

[0055] Figure 33 illustrates a communication system applied to the present invention.

[0056] Figure 34 illustrates a wireless device applicable to the present invention.

[0057] Figure 35 illustrates another example of a wireless device applicable to the present invention. The wireless device may be implemented in various forms depending on the use case / service.

[0058] Figure 36 illustrates a vehicle or autonomous vehicle to which the present invention applies.

[0059] A wireless communication system is a multiple access system that supports communication with multiple users by sharing available system resources (e.g., bandwidth, transmission power, etc.). Examples of multiple access systems include code division multiple access (CDMA), frequency division multiple access (FDMA), time division multiple access (TDMA), orthogonal frequency division multiple access (OFDMA), single carrier frequency division multiple access (SC-FDMA), and multi-carrier frequency division multiple access (MC-FDMA).

[0060] Sidelink refers to a communication method that establishes a direct link between user equipment (UE), allowing voice or data to be exchanged directly between terminals without going through a base station (BS). Sidelink is being considered as a solution to address the burden on base stations due to rapidly increasing data traffic.

[0061] V2X (vehicle-to-everything) refers to a communication technology that exchanges information with other vehicles, pedestrians, and infrastructure-based objects through wired / wireless communication. V2X can be divided into four types: V2V (vehicle-to-vehicle), V2I (vehicle-to-infrastructure), V2N (vehicle-to-network), and V2P (vehicle-to-pedestrian). V2X communication can be provided through the PC5 interface and / or Uu interface.

[0062] Meanwhile, as more and more communication devices demand greater communication capacity, the need for improved mobile broadband communication compared to existing radio access technology (RAT) is emerging. Accordingly, communication systems that consider services or terminals sensitive to reliability and latency are being discussed. Next-generation wireless access technologies that consider improved mobile broadband communication, massive MTC, and URLLC (Ultra-Reliable and Low Latency Communication) can be called new radio access technology (RAT) or new radio (NR). NR can also support V2X (vehicle-to-everything) communication.

[0063] The following technologies can be used in various wireless communication systems, such as CDMA (code division multiple access), FDMA (frequency division multiple access), TDMA (time division multiple access), OFDMA (orthogonal frequency division multiple access), and SC-FDMA (single carrier frequency division multiple access). CDMA can be implemented with wireless technologies such as UTRA (universal terrestrial radio access) or CDMA2000. TDMA can be implemented with wireless technologies such as GSM (global system for mobile communications) / GPRS (general packet radio service) / EDGE (enhanced data rates for GSM evolution). OFDMA can be implemented with wireless technologies such as IEEE (Institute of Electrical and Electronics Engineers) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802-20, and E-UTRA (evolved UTRA). IEEE 802.16m is an evolution of IEEE 802.16e, providing backward compatibility with systems based on IEEE 802.16e. UTRA is part of UMTS (universal mobile telecommunications system). 3GPP (3rd generation partnership project) LTE (long term evolution) is a part of E-UMTS (evolved UMTS) that uses E-UTRA (evolved-UMTS terrestrial radio access), employing OFDMA in the downlink and SC-FDMA in the uplink.LTE-A (advanced) is an evolution of 3GPP LTE.

[0064] 5G NR, the successor to LTE-A, is a new clean-slate mobile communications system featuring high performance, low latency, and high availability. 5G NR can utilize all available spectrum resources, from low-frequency bands below 1 GHz, mid-frequency bands between 1 GHz and 10 GHz, and high-frequency (millimeter wave) bands above 24 GHz.

[0065] For clarity, the description will focus on LTE-A or 5G NR, but the technical ideas of the embodiment(s) are not limited thereto.

[0066] Figure 2 illustrates the architecture of an applicable LTE system. This may be referred to as an Evolved-UMTS Terrestrial Radio Access Network (E-UTRAN) or a Long Term Evolution (LTE) / LTE-A system.

[0067] Referring to FIG. 2, the E-UTRAN includes a base station (20; BS) that provides a control plane and a user plane to a terminal (10). The terminal (10) may be fixed or mobile, and may be referred to by other terms such as a mobile station (MS), a user terminal (UT), a subscriber station (SS), a mobile terminal (MT), a wireless device, etc. The base station (20) refers to a fixed station that communicates with the terminal (10), and may be referred to by other terms such as an evolved-NodeB (eNB), a base transceiver system (BTS), an access point, etc.

[0068] Base stations (20) can be connected to each other via the X2 interface. The base station (20) is connected to an EPC (Evolved Packet Core, 30) via the S1 interface, more specifically, to an MME (Mobility Management Entity) via the S1-MME, and to an S-GW (Serving Gateway) via the S1-U.

[0069] The EPC (30) consists of an MME, an S-GW, and a P-GW (Packet Data Network-Gateway). The MME holds information about terminal access and capabilities, and this information is primarily used for terminal mobility management. The S-GW is a gateway with the E-UTRAN as its endpoint, and the P-GW is a gateway with the PDN as its endpoint.

[0070] The layers of the radio interface protocol between the terminal and the network can be divided into L1 (Layer 1), L2 (Layer 2), and L3 (Layer 3) based on the three lower layers of the Open System Interconnection (OSI) standard model, which is widely known in communication systems. Among these, the physical layer belonging to Layer 1 provides an information transfer service using a physical channel, and the RRC (Radio Resource Control) layer located in Layer 3 controls radio resources between the terminal and the network. To this end, the RRC layer exchanges RRC messages between the terminal and the base station.

[0071] Figure 3 shows the structure of the NR system.

[0072] Referring to FIG. 3, the NG-RAN may include a gNB and / or an eNB that provides user plane and control plane protocol termination to the UE. FIG. 7 illustrates a case where only a gNB is included. The gNB and eNB are connected to each other via an Xn interface. The gNB and eNB are connected to the 5th generation core network (5G Core Network: 5GC) via the NG interface. More specifically, the gNB is connected to the access and mobility management function (AMF) via the NG-C interface, and the gNB is connected to the user plane function (UPF) via the NG-U interface.

[0073] Figure 4 shows the structure of a radio frame of NR.

[0074] Referring to FIG. 4, radio frames can be used for uplink and downlink transmission in NR. A radio frame has a length of 10 ms and can be defined as two 5 ms half-frames (Half-Frames, HF). A half-frame can include five 1 ms sub-frames (Subframes, SF). A sub-frame can be divided into one or more slots, and the number of slots within a sub-frame can be determined by the Subcarrier Spacing (SCS). Each slot can include 12 or 14 OFDM (A) symbols depending on the cyclic prefix (CP).

[0075] When normal CP is used, each slot can contain 14 symbols. When extended CP is used, each slot can contain 12 symbols. Here, the symbols can include OFDM symbols (or CP-OFDM symbols), SC-FDMA (Single Carrier - FDMA) symbols (or DFT-s-OFDM (Discrete Fourier Transform-spread-OFDM) symbols).

[0076] Table 1 below shows the number of symbols per slot ((N)) depending on the SCS setting (u) when normal CP is used. slot symb ), number of slots per frame ((N frame,u slot ) and the number of slots per subframe ((N subframe,u slot ) is an example.

[0077] SCS (15*2 u )N slot symb N frame,u slot N subframe,u slot 15KHz (u=0)1410130KHz (u=1)1420260KHz (u=2)14404120KHz (u=3)14808240KHz (u=4)1416016

[0078] Table 2 illustrates the number of symbols per slot, the number of slots per frame, and the number of slots per subframe according to SCS when extended CP is used.

[0079] SCS (15*2 u )N slot symb N frame,u slot N subframe,u slot 60KHz (u=2)12404

[0080] In an NR system, OFDM(A) numerology (e.g., SCS, CP length, etc.) may be set differently between multiple cells that are merged into a single terminal. Accordingly, the (absolute time) interval of a time resource (e.g., subframe, slot, or TTI) (conveniently referred to as TU (Time Unit)) consisting of the same number of symbols may be set differently between the merged cells.

[0081] In NR, multiple numerologies, or SCSs, can be supported to support various 5G services. For example, a 15 kHz SCS can support wide areas in traditional cellular bands, while a 30 kHz / 60 kHz SCS can support dense urban areas, lower latency, and wider carrier bandwidth. A 60 kHz or higher SCS can support bandwidths greater than 24.25 GHz to overcome phase noise.

[0082] The NR frequency band can be defined by two types of frequency ranges. The two types of frequency ranges can be FR1 and FR2. The numerical values ​​of the frequency ranges can be changed, and for example, the two types of frequency ranges can be as shown in Table 3 below. Among the frequency ranges used in the NR system, FR1 can mean the "sub 6 GHz range", and FR2 can mean the "above 6 GHz range" and can be called millimeter wave (mmW).

[0083] Frequency Range designationCorresponding frequency rangeSubcarrier Spacing (SCS)FR1450MHz - 6000MHz15, 30, 60kHzFR224250MHz - 52600MHz60, 120, 240kHz

[0084] As described above, the numerical value of the frequency range of the NR system can be changed. For example, FR1 may include a band from 410 MHz to 7125 MHz, as shown in Table 4 below. That is, FR1 may include a frequency band above 6 GHz (or 5850, 5900, 5925 MHz, etc.). For example, the frequency band above 6 GHz (or 5850, 5900, 5925 MHz, etc.) included within FR1 may include an unlicensed band. The unlicensed band may be used for various purposes, such as for vehicular communications (e.g., autonomous driving).

[0085] Frequency Range designationCorresponding frequency rangeSubcarrier Spacing (SCS)FR1410MHz - 7125MHz15, 30, 60kHzFR224250MHz - 52600MHz60, 120, 240kHz

[0086] Figure 5 shows the slot structure of an NR frame.

[0087] Referring to Figure 5, a slot includes multiple symbols in the time domain. For example, in the case of a normal CP, one slot may include 14 symbols, but in the case of an extended CP, one slot may include 12 symbols. Alternatively, in the case of a normal CP, one slot may include 7 symbols, but in the case of an extended CP, one slot may include 6 symbols.

[0088] A carrier includes multiple subcarriers in the frequency domain. An RB (Resource Block) can be defined as multiple (e.g., 12) consecutive subcarriers in the frequency domain. A BWP (Bandwidth Part) can be defined as multiple consecutive (P)RBs ((Physical) Resource Blocks) in the frequency domain, and can correspond to one numerology (e.g., SCS, CP length, etc.). A carrier can include up to N (e.g., 5) BWPs. Data communication can be performed through activated BWPs. Each element can be referred to as a Resource Element (RE) in the resource grid, and one complex symbol can be mapped to it.

[0089] Meanwhile, the wireless interface between terminals or between terminals and a network may be composed of an L1 layer, an L2 layer, and an L3 layer. In various embodiments of the present disclosure, the L1 layer may refer to a physical layer. Furthermore, for example, the L2 layer may refer to at least one of a MAC layer, an RLC layer, a PDCP layer, and an SDAP layer. Furthermore, for example, the L3 layer may refer to an RRC layer.

[0090] FIG. 6 illustrates a communication structure that can be provided in a 6G system according to an embodiment of the present disclosure. The embodiment of FIG. 6 can be combined with various embodiments of the present disclosure.

[0091] New network characteristics in 6G may include:

[0092] - Satellite integrated network

[0093] - Connected Intelligence: Unlike previous generations of wireless communication systems, 6G is revolutionary, upgrading the wireless evolution from "connected objects" to "connected intelligence." AI can be applied at every stage of the communication process (or at every signal processing step, as described below).

[0094] - Seamless integration of wireless information and energy transfer

[0095] - Ubiquitous super 3D connectivity: Access to networks and core network functions of drones and very low Earth orbit satellites will create super 3D connectivity in 6G ubiquitous.

[0096] Some general requirements for the new network characteristics of 6G, such as the above, may be as follows:

[0097] - small cell networks

[0098] - Ultra-dense heterogeneous network

[0099] - High-capacity backhaul

[0100] - Radar technology integrated with mobile technology: High-precision localization (or location-based services) through communications is a key feature of 6G wireless communication systems. Therefore, radar systems will be integrated with 6G networks.

[0101] - Softwarization and virtualization

[0102] Below, the core implementation technologies of the 6G system are described.

[0103] - Artificial Intelligence: Incorporating AI into communications can streamline and improve real-time data transmission. AI can use numerous analytics to determine how complex target tasks should be performed. This means AI can increase efficiency and reduce processing delays. Time-consuming tasks such as handovers, network selection, and resource scheduling can be performed instantly using AI. AI can also play a crucial role in machine-to-machine (M2M), machine-to-human, and human-to-machine communications. Furthermore, AI can facilitate rapid communication in brain-computer interfaces (BCIs). AI-based communication systems can be supported by metamaterials, intelligent structures, intelligent networks, intelligent devices, intelligent cognitive radios, self-sustaining wireless networks, and machine learning.

[0104] - THz communication (terahertz communication): Data rates can be increased by increasing the bandwidth. This can be achieved by using sub-THz communication with wide bandwidths and applying advanced massive MIMO technology. THz waves, also known as sub-millimeter waves, typically refer to the frequency range between 0.1 THz and 10 THz, with corresponding wavelengths ranging from 0.03 mm to 3 mm. The 100 GHz to 300 GHz band (sub-THz band) is considered a key part of the THz spectrum for cellular communications. Adding the sub-THz band to the mmWave band will increase the capacity of 6G cellular communications. Among the defined THz bands, 300 GHz to 3 THz lies in the far infrared (IR) frequency band. While part of the optical band, the 300 GHz to 3 THz band lies at the boundary of the optical band, immediately following the RF band. Therefore, this 300 GHz to 3 THz band exhibits similarities to RF.

[0105] Figure 7 illustrates the electromagnetic spectrum according to one embodiment of the present disclosure. The embodiment of Figure 7 can be combined with various embodiments of the present disclosure. Key characteristics of THz communications include (i) a widely available bandwidth to support very high data rates, and (ii) high path loss at high frequencies (highly directional antennas are essential). The narrow beamwidth generated by the highly directional antenna reduces interference. The small wavelength of THz signals allows for a much larger number of antenna elements to be integrated into devices and base stations operating in this band. This enables the use of advanced adaptive array techniques to overcome range limitations.

[0106] - Large-scale MIMO technology

[0107] - Hologram beamforming (HBF)

[0108] - Optical wireless technology

[0109] - Free-space optical transmission backhaul network (FSO backhaul network)

[0110] - Quantum communication

[0111] - Cell-free communication

[0112] - Integration of wireless information and power transmission

[0113] - Integration of wireless communication and sensing

[0114] - Integrated access and backhaul network

[0115] - Big data analysis

[0116] - Reconfigurable intelligent surface

[0117] - metaverse

[0118] - Block chain

[0119] Unmanned aerial vehicles (UAVs): UAVs, or drones, will be a key element in 6G wireless communications. In most cases, high-speed data wireless connectivity can be provided using UAV technology. Base stations (BSs) can be installed on UAVs to provide cellular connectivity. UAVs may offer specific capabilities not found in fixed BS infrastructure, such as easy deployment, robust line-of-sight links, and controlled mobility. During emergencies such as natural disasters, deploying terrestrial communications infrastructure is not economically feasible and sometimes cannot provide services in volatile environments. UAVs can easily handle these situations. UAVs will become a new paradigm in wireless communications. This technology facilitates three fundamental requirements for wireless networks: enhanced mobile broadband (eMBB), URLLC, and mMTC. UAVs can also support various purposes, such as enhancing network connectivity, fire detection, disaster emergency services, security and surveillance, pollution monitoring, parking monitoring, and accident monitoring. Therefore, UAV technology is recognized as one of the most important technologies for 6G communications.

[0120] - Autonomous driving (self-driving): V2X (vehicle to everything), a key element in building autonomous driving infrastructure, can be a technology that allows cars to communicate and share with various elements on the road for autonomous driving, such as vehicle-to-vehicle (V2V) and vehicle-to-infrastructure (V2I) wireless communication. Fast transmission speeds and low-latency technologies are essential to maximize autonomous driving performance and ensure high safety. Furthermore, in the future, autonomous driving will go beyond simply providing warnings or guidance messages to drivers and may require active intervention in vehicle operation and direct control of the vehicle in dangerous situations. To this end, the amount of information that needs to be transmitted and received may become enormous, so 6G is expected to maximize autonomous driving with faster transmission speeds and lower latency than 5G.

[0121] Figure 8 illustrates a radio protocol architecture for SL communication. Specifically, Figure 8 (a) illustrates the user plane protocol stack of NR, and Figure 8 (b) illustrates the control plane protocol stack of NR.

[0122] Below, the SL synchronization signal (Sidelink Synchronization Signal, SLSS) and synchronization information are described.

[0123] SLSS is an SL-specific sequence and may include a Primary Sidelink Synchronization Signal (PSSS) and a Secondary Sidelink Synchronization Signal (SSSS). The PSSS may be referred to as a Sidelink Primary Synchronization Signal (S-PSS), and the SSSS may be referred to as a Sidelink Secondary Synchronization Signal (S-SSS). For example, length-127 M-sequences may be used for the S-PSS, and length-127 Gold sequences may be used for the S-SSS. For example, a terminal may detect an initial signal and acquire synchronization using the S-PSS. For example, a terminal may acquire detailed synchronization and detect a synchronization signal ID using the S-PSS and the S-SSS.

[0124] PSBCH (Physical Sidelink Broadcast Channel) may be a (broadcast) channel that transmits basic (system) information that a terminal must know first before transmitting or receiving an SL signal. For example, the basic information may be information related to SLSS, duplex mode (DM), TDD UL / DL (Time Division Duplex Uplink / Downlink) configuration, resource pool-related information, type of application related to SLSS, subframe offset, broadcast information, etc. For example, in NR V2X, for evaluating PSBCH performance, the payload size of PSBCH may be 56 bits, including a 24-bit CRC.

[0125] S-PSS, S-SSS and PSBCH may be included in a block format supporting periodic transmission (e.g., SL SS (Synchronization Signal) / PSBCH block, hereinafter referred to as S-SSB (Sidelink-Synchronization Signal Block)). The S-SSB may have the same numerology (i.e., SCS and CP length) as the PSCCH (Physical Sidelink Control Channel) / PSSCH (Physical Sidelink Shared Channel) in the carrier, and the transmission bandwidth may be within a (pre-)configured SL BWP (Sidelink BWP). For example, the bandwidth of the S-SSB may be 11 RBs (Resource Blocks). For example, the PSBCH may span 11 RBs. And, the frequency location of the S-SSB may be (pre-)configured. Therefore, the terminal does not need to perform hypothesis detection in the frequency to discover the S-SSB in the carrier.

[0126] Meanwhile, in the NR SL system, multiple numerologies having different SCS and / or CP lengths may be supported. In this case, as the SCS increases, the length of the time resource for a transmitting terminal to transmit an S-SSB may become shorter. Accordingly, the coverage of the S-SSB may decrease. Therefore, in order to ensure the coverage of the S-SSB, the transmitting terminal may transmit one or more S-SSBs to a receiving terminal within one S-SSB transmission period according to the SCS. For example, the number of S-SSBs that the transmitting terminal transmits to the receiving terminal within one S-SSB transmission period may be pre-configured or configured for the transmitting terminal. For example, the S-SSB transmission period may be 160 ms. For example, an S-SSB transmission period of 160 ms may be supported for all SCSs.

[0127] For example, when the SCS is 15 kHz at FR1, the transmitting terminal can transmit one or two S-SSBs to the receiving terminal within one S-SSB transmission period. For example, when the SCS is 30 kHz at FR1, the transmitting terminal can transmit one or two S-SSBs to the receiving terminal within one S-SSB transmission period. For example, when the SCS is 60 kHz at FR1, the transmitting terminal can transmit one, two, or four S-SSBs to the receiving terminal within one S-SSB transmission period.

[0128] For example, when the SCS is 60 kHz at FR2, the transmitting terminal can transmit 1, 2, 4, 8, 16, or 32 S-SSBs to the receiving terminal within one S-SSB transmission period. For example, when the SCS is 120 kHz at FR2, the transmitting terminal can transmit 1, 2, 4, 8, 16, 32, or 64 S-SSBs to the receiving terminal within one S-SSB transmission period.

[0129] Meanwhile, when the SCS is 60 kHz, two types of CP may be supported. In addition, the structure of the S-SSB transmitted by the transmitting terminal to the receiving terminal may be different depending on the CP type. For example, the CP type may be Normal CP (NCP) or Extended CP (ECP). Specifically, for example, when the CP type is NCP, the number of symbols to which the PSBCH is mapped within the S-SSB transmitted by the transmitting terminal may be 9 or 8. On the other hand, for example, when the CP type is ECP, the number of symbols to which the PSBCH is mapped within the S-SSB transmitted by the transmitting terminal may be 7 or 6. For example, the PSBCH may be mapped to the first symbol within the S-SSB transmitted by the transmitting terminal. For example, the receiving terminal receiving the S-SSB may perform an Automatic Gain Control (AGC) operation in the first symbol section of the S-SSB.

[0130] Figure 9 shows a terminal performing V2X or SL communication.

[0131] Referring to FIG. 9, the term "terminal" in V2X or SL communication may primarily refer to a user's terminal. However, if a network device such as a base station transmits and receives signals according to a communication method between terminals, the base station may also be considered a type of terminal. For example, terminal 1 may be a first device (100), and terminal 2 may be a second device (200).

[0132] For example, terminal 1 can select a resource unit corresponding to a specific resource within a resource pool, which represents a set of resources. Then, terminal 1 can transmit an SL signal using the resource unit. For example, terminal 2, which is a receiving terminal, can be configured with a resource pool in which terminal 1 can transmit a signal, and can detect a signal from terminal 1 within the resource pool.

[0133] Here, if terminal 1 is within the connection range of the base station, the base station can inform terminal 1 of the resource pool. On the other hand, if terminal 1 is outside the connection range of the base station, another terminal can inform terminal 1 of the resource pool, or terminal 1 can use a pre-configured resource pool.

[0134] In general, a resource pool can be composed of multiple resource units, and each terminal can select one or multiple resource units to use for its SL signal transmission.

[0135] Figure 10 shows resource units for V2X or SL communication.

[0136] Referring to Figure 10, the entire frequency resources of the resource pool can be divided into NF units, and the entire time resources of the resource pool can be divided into NT units. Therefore, a total of NF * NT resource units can be defined within the resource pool. Figure 10 illustrates an example where the resource pool repeats with a cycle of NT subframes.

[0137] As shown in Figure 10, a single resource unit (e.g., Unit #0) may appear periodically and repeatedly. Alternatively, to achieve diversity effects in the time or frequency dimensions, the index of the physical resource unit to which a single logical resource unit is mapped may change in a predetermined pattern over time. In this resource unit structure, a resource pool may refer to a set of resource units that a terminal wishing to transmit an SL signal can use for transmission.

[0138] Resource pools can be subdivided into several categories. For example, based on the content of the SL signal transmitted from each resource pool, resource pools can be categorized as follows:

[0139] (1) Scheduling Assignment (SA) may be a signal that includes information such as the location of resources used by a transmitting terminal for transmission of an SL data channel, MCS (Modulation and Coding Scheme) or MIMO (Multiple Input Multiple Output) transmission method required for demodulation of other data channels, and TA (Timing Advance). SA may also be transmitted multiplexed with SL data on the same resource unit, in which case the SA resource pool may mean a resource pool in which SA is multiplexed with SL data and transmitted. SA may also be called an SL control channel.

[0140] (2) The SL data channel (Physical Sidelink Shared Channel, PSSCH) may be a resource pool used by a transmitting terminal to transmit user data. If SA is multiplexed and transmitted together with SL data on the same resource unit, only the SL data channel excluding SA information may be transmitted from the resource pool for the SL data channel. In other words, the REs (Resource Elements) that were used to transmit SA information on individual resource units within the SA resource pool may still be used to transmit SL data in the resource pool of the SL data channel. For example, the transmitting terminal may transmit the PSSCH by mapping it to consecutive PRBs.

[0141] (3) A discovery channel may be a resource pool for transmitting terminals to transmit information such as their IDs. Through this, transmitting terminals can enable neighboring terminals to discover them.

[0142] Even if the content of the SL signal described above is the same, different resource pools may be used depending on the transmission and reception properties of the SL signal. For example, even if it is the same SL data channel or discovery message, it may be again divided into different resource pools depending on the transmission timing determination method of the SL signal (for example, whether it is transmitted at the time of reception of a synchronization reference signal or whether it is transmitted by applying a certain timing advance at the time of reception), the resource allocation method (for example, whether the base station designates transmission resources for individual signals to individual transmitting terminals or whether individual transmitting terminals independently select individual signal transmission resources within the resource pool), the signal format (for example, the number of symbols each SL signal occupies in one subframe or the number of subframes used for transmission of one SL signal), the signal strength from the base station, the transmission power strength of the SL terminal, etc.

[0143] FIG. 11 illustrates an example of a BWP according to an embodiment of the present disclosure. The embodiment of FIG. 11 can be combined with various embodiments of the present disclosure. In the embodiment of FIG. 11, it is assumed that there are three BWPs.

[0144] Referring to Figure 11, a common resource block (CRB) may be a carrier resource block numbered from one end of a carrier band to the other. Furthermore, a PRB may be a numbered resource block within each BWP. Point A may indicate a common reference point for the resource block grid.

[0145] The BWP can be set by Point A, an offset from Point A (NstartBWP), and a bandwidth (NsizeBWP). For example, Point A can be an outer reference point of a PRB of a carrier where subcarrier 0 of all numerologies (e.g., all numerologies supported by the network on that carrier) are aligned. For example, the offset can be the PRB spacing between the lowest subcarrier in a given numerology and Point A. For example, the bandwidth can be the number of PRBs in a given numerology.

[0146] SLSS (Sidelink Synchronization Signal) is a SL (sidelink) specific sequence and may include PSSS (Primary Sidelink Synchronization Signal) and SSSS (Secondary Sidelink Synchronization Signal). The PSSS may be referred to as S-PSS (Sidelink Primary Synchronization Signal) and the SSSS may be referred to as S-SSS (Sidelink Secondary Synchronization Signal). For example, length-127 M-sequences may be used for S-PSS and length-127 Gold sequences may be used for S-SSS. For example, a terminal may detect an initial signal (signal detection) and obtain synchronization using S-PSS. For example, the terminal can obtain detailed synchronization using S-PSS and S-SSS and detect a synchronization signal ID.

[0147] PSBCH (Physical Sidelink Broadcast Channel) may be a (broadcast) channel that transmits basic (system) information that a terminal must know first before transmitting or receiving an SL signal. For example, the basic information may be information related to SLSS, duplex mode (DM), TDD UL / DL (Time Division Duplex Uplink / Downlink) configuration, resource pool-related information, type of application related to SLSS, subframe offset, broadcast information, etc. For example, in order to evaluate PSBCH performance, in NR V2X, the payload size of PSBCH may be 56 bits, including a 24-bit CRC (Cyclic Redundancy Check).

[0148] S-PSS, S-SSS and PSBCH may be included in a block format supporting periodic transmission (e.g., SL SS (Synchronization Signal) / PSBCH block, hereinafter referred to as S-SSB (Sidelink-Synchronization Signal Block)). The S-SSB may have the same numerology (i.e., SCS and CP length) as the PSCCH (Physical Sidelink Control Channel) / PSSCH (Physical Sidelink Shared Channel) in the carrier, and the transmission bandwidth may be within a (pre-)configured SL BWP (Sidelink BWP). For example, the bandwidth of the S-SSB may be 11 RBs (Resource Blocks). For example, the PSBCH may span 11 RBs. And, the frequency location of the S-SSB may be (pre-)configured. Therefore, the terminal does not need to perform hypothesis detection in the frequency to discover the S-SSB in the carrier.

[0149] FIG. 12 illustrates a procedure for a terminal to perform V2X or SL communication according to a resource allocation mode, according to an embodiment of the present disclosure. The embodiment of FIG. 12 may be combined with various embodiments of the present disclosure.

[0150] Referring to (a) of FIG. 12, in resource allocation mode 1, the base station may schedule SL resources to be used by the terminal for SL transmission. For example, in step S1200, the base station may transmit information related to SL resources and / or information related to UL resources to the first terminal. For example, the UL resources may include PUCCH resources and / or PUSCH resources. For example, the UL resources may be resources for reporting SL HARQ feedback to the base station.

[0151] For example, a first terminal may receive information related to a dynamic grant (DG) resource and / or information related to a configured grant (CG) resource from a base station. For example, a CG resource may include a CG type 1 resource or a CG type 2 resource. In this specification, a DG resource may be a resource that a base station configures / allocates to the first terminal via downlink control information (DCI). In this specification, a CG resource may be a (periodic) resource that a base station configures / allocates to the first terminal via DCI and / or an RRC message. For example, in the case of a CG type 1 resource, the base station may transmit an RRC message including information related to the CG resource to the first terminal. For example, in the case of a CG type 2 resource, the base station may transmit an RRC message including information related to the CG resource to the first terminal, and the base station may transmit a DCI related to activation or release of the CG resource to the first terminal.

[0152] In step S1510, the first terminal may transmit a PSCCH (e.g., Sidelink Control Information (SCI) or 1st-stage SCI) to the second terminal based on the resource scheduling. In step S1220, the first terminal may transmit a PSSCH (e.g., 2nd-stage SCI, MAC PDU, data, etc.) related to the PSCCH to the second terminal. In step S1230, the first terminal may receive a PSFCH related to the PSCCH / PSSCH from the second terminal. For example, HARQ feedback information (e.g., NACK information or ACK information) may be received from the second terminal via the PSFCH. In step S1240, the first terminal may transmit / report HARQ feedback information to the base station via a PUCCH or a PUSCH. For example, the HARQ feedback information reported to the base station may be information generated by the first terminal based on the HARQ feedback information received from the second terminal. For example, the HARQ feedback information reported to the base station may be information generated by the first terminal based on a rule set in advance. For example, the DCI may be DCI for scheduling SL.

[0153] Referring to (b) of FIG. 12, in resource allocation mode 2, a terminal can determine an SL transmission resource within the SL resources set by the base station / network or within the preset SL resources. For example, the set SL resources or the preset SL resources may be a resource pool. For example, the terminal can autonomously select or schedule resources for SL transmission. For example, the terminal can perform SL communication by selecting a resource within the set resource pool. For example, the terminal can select a resource within a selection window by performing sensing and resource (re)selection procedures. For example, the sensing can be performed on a subchannel basis. For example, in step S1210, a first terminal that has selected a resource within the resource pool can transmit a PSCCH (e.g., Sidelink Control Information (SCI) or 1st-stage SCI) to a second terminal using the resource. In step S1220, the first terminal may transmit a PSSCH (e.g., 2nd-stage SCI, MAC PDU, data, etc.) related to the PSCCH to the second terminal. In step S1230, the first terminal may receive a PSFCH related to the PSCCH / PSSCH from the second terminal.

[0154] Referring to (a) or (b) of FIG. 12, for example, a first terminal may transmit an SCI to a second terminal on a PSCCH. Or, for example, the first terminal may transmit two consecutive SCIs (e.g., 2-stage SCIs) to the second terminal on the PSCCH and / or the PSSCH. In this case, the second terminal may decode the two consecutive SCIs (e.g., 2-stage SCIs) to receive the PSSCH from the first terminal. In this specification, an SCI transmitted on a PSCCH may be referred to as a 1st SCI, a 1st SCI, a 1st-stage SCI, or a 1st-stage SCI format, and an SCI transmitted on a PSSCH may be referred to as a 2nd SCI, a 2nd SCI, a 2nd-stage SCI, or a 2nd-stage SCI format.

[0155] Referring to (a) or (b) of FIG. 12, in step S1530, the first terminal may receive a PSFCH. For example, the first terminal and the second terminal may determine PSFCH resources, and the second terminal may use the PSFCH resources to transmit HARQ feedback to the first terminal.

[0156] Referring to (a) of FIG. 12, in step S1540, the first terminal may transmit SL HARQ feedback to the base station via PUCCH and / or PUSCH.

[0157] Figure 13 is a diagram for explaining the control plane procedure of L2 U2N relay (UE-to-Network Relay).

[0158] The PC5-RRC aspect PC5 unicast link establishment procedure of Rel-16 NR V2X can be reused to establish a secure unicast link for L2 U2N relay (layer 2 UE-to-Network relaying) between the remote UE and the relay UE before the remote UE establishes a Uu RRC connection with the network via the relay UE.

[0159] For both in-coverage and out-of-coverage scenarios, when a remote UE initiates the first RRC message to establish a connection with a gNB, the PC5 L2 configuration for transmissions between the remote UE and the U2N relay UE can be based on the RLC / MAC configuration defined in the standard. The establishment of Uu SRB1 / SRB2 and DRB of the remote UE follows the legacy Uu configuration procedure for the L2 U2N relay.

[0160] A given scenario (TS 38.300) describes the control plane procedures of an L2 U2N relay as follows:

[0161] In step S1300, the remote UE and the relay UE can perform a discovery procedure and establish a PC5-RRC connection in step S1301 based on the existing Rel-16 procedure.

[0162] In step S1302, the remote UE can transmit the first RRC message (i.e., RRCSetupRequest) to establish a connection with the gNB via the relay UE using the default L2 configuration of PC5. The gNB responds to the remote UE with an RRCSetup message (S1303). The RRCSetup delivery to the remote UE uses the default configuration of PC5. If the relay UE is not initiated in RRC_CONNECTED, it must perform its own connection establishment upon receiving the message for the default L2 configuration of PC5.

[0163] In step S1304, the gNB and the relay UE perform a relay channel setup procedure via Uu. Depending on the configuration of the gNB, the relay / remote UE establishes an RLC channel for relaying SRB1 to the remote UE via PC5. This step prepares the relay channel for SRB1.

[0164] In step S1305, a remote UE SRB1 message (e.g., an RRCSetupComplete message) is transmitted to the gNB via the relay UE using the SRB1 relay channel over PC5. The remote UE is then RRC connected over Uu.

[0165] In steps S1306 and S1307, the remote UE and the gNB establish security according to legacy procedures, and the security message is transmitted through the Relay UE.

[0166] In steps S1308 and S1309, the gNB transmits RRCReconfiguration to the remote UE via the relay UE to set up the relay SRB2 / DRB. The remote UE responds by transmitting RRCReconfigurationComplete to the gNB via the relay UE.

[0167] In step S1310, the gNB establishes an additional RLC channel between the gNB and the relay UE for traffic relay. Depending on the configuration of the gNB, the relay / remote UE establishes an additional RLC channel between the remote UE and the relay UE for traffic relay.

[0168] In the above scenario, in addition to the connection setup procedure, for L2 UE-to-Network relay:

[0169] - RRC reconfiguration and RRC disconnection procedures can reuse legacy RRC procedures with message content / configuration design left in the WI phase.

[0170] - The RRC connection re-establishment and RRC connection resumption procedures can be reused as a baseline by considering the connection establishment procedure of the L2 U2N relay above to handle relay-specific parts along with the message content / structure design. The message content / structure can be defined later.

[0171] Unmanned Aerial Vehicle (UAV)-to-everything (U2X)

[0172] Figures 14 to 18 are drawings for explaining the U2X system.

[0173] The key points of the proposed U2X solution in the given scenario (TR 23.700-58) are as follows:

[0174] - U2X can support BRID and Direct DAA by leveraging the V2X mechanism defined in TS 23.287. In this case, both LTE PC5 and NR PC5 defined in TS 23.285 are supported, and RAT selection can be performed based on U2XP.

[0175] - Communication mode: BRID (Broadcasting UAV identification) can use Broadcast communication mode. DAA can use Broadcast communication mode to advertise UAV information. Broadcast via PC5 or unicast via PC5 can be used between two or more UAVs for DAA de-collision. Unicast via Uu via U2X AS may not be supported in the above-mentioned U2X solution. Groupcast mode for NR-based PC5 may not be supported in the above-mentioned U2X solution. When NR PC5 is selected, connectionless groupcast communication can be used for DAA. Meanwhile, application layer managed groupcast may not be considered in this release due to lack of clear requirements.

[0176] - U2X can be supported by a U2X Application Server that interfaces with the operator network via NEF, as in the case of a V2X Application Server.

[0177] Meanwhile, the above given scenario / solution needs to allow for multiple deployment scenarios where a dedicated service set can be defined and the U2X AS and USS providing the UAV are the same or different entities.

[0178] - A U2X policy (U2XP) can be defined to provide configuration parameters to a UE for U2X communication via a PC5 reference point or a Uu reference point. The configuration parameters can be preset in the ME (Mobile Equipment), set in the UICC (universal IC card), pre-set in the ME and set in the UICC, provided / updated by a U2X application server via a policy control function (PCF) and / or a V1 reference point, or provided / updated to the UE by the PCF. Here, the UE needs to consider the U2X policies in the following order of priority: those provided / updated by the PCF, those provided / updated by the U2X application server via the V1 reference point, those configured in the UICC, and those pre-configured in the ME. A de-conflicting policy can be a policy indicating a communication mode for de-conflicting (unicast or broadcast), a communication frequency for de-conflicting, etc.

[0179] - As with V2X, the Tx profile or NR Tx profile can be determined based on the U2XP mapping of the U2X service type.

[0180] - Both UAVs with UICC and UAVs without UICC (i.e. not subscribed to an MNO) can be supported. Here, UAVs without UICC can perform U2X communication only if they are approved as “Not provided in E-UTRA” and “Not provided in NR.”

[0181] - U2X communication parameters of the U2X application server or PCF can be transmitted via the UAV-C UE.

[0182] - In addition to the existing parameters for V2X, PC5 RAT-specific radio parameters (e.g., LTE PC5, NR PC5) may be configured, including geographic area, altitude restrictions, and validity timers. Such additional information / parameters may be required to policy-specifically control PC5 usage based on the specific location of the UAV.

[0183] - The definition of DAA / UAV service types may go beyond the scope of the given scenarios described above.

[0184] - For UAVs with UICC to use PC5-based communications for BRID and DAA, successful UUAA authentication / authorization as defined in TS 23.256 and authorization via U2XP are required. However, the FAA does not require specific authorization for the use of PC5 for BRID or DAA. For UAVs without UICC, the use of PC5-based communications for BRID and DAA can only be authorized via U2XP. Meanwhile, U2X services can be identified by one of the following values ​​specifically defined for aviation applications: ITS Application Identifier (ITS-AID), Provider Service Identifier (PSID), or Application Identifier (AID).

[0185] - As in TS 23.287, security for broadcast U2X communications over the PC5 reference point can be supported in U2X application layer schemes developed in other SDOs.

[0186] Referring to FIG. 14, a non-roaming 5G system architecture for U2X communication via PC5 can be configured as illustrated in FIG. 14. Here, the non-roaming 5G system architecture for U2X communication via PC5 can be applied with the reference point of TS 23.287, and the following differences can be present.

[0187] - U2X1: As a reference point between the UE and the UAV-C and the U2X application of the U2X application server, this reference point may be outside the scope of the above-mentioned scenario.

[0188] - U2X5: As a reference point between U2X applications within the UE, this reference point may / may not be specified in the release of a given scenario.

[0189] - N1: In addition to the relevant functions defined in TS 23.501 for N1, it can also be used to transfer U2X policies and parameters (including service authorization) from AMF to UE for U2X services, and PC5 functions for U2X capabilities and U2X information of UE to AMF.

[0190] - N2: In addition to the relevant functions defined in TS 23.501 for N2, it can also be used to convey U2X policies and parameters (including service authorization) from AMF to NG-RAN for U2X services.

[0191] - The above-described solution can support UAV UEs utilizing Uu connections and UAV UEs that do not utilize Uu connections (i.e., UAV UEs that are either Uu capable or Uu non-capable). UAVs that do not utilize Uu capabilities can use U2X for BRID and DAA and can be configured via U2X1 for transmissions outside the scope of 3GPP. On the other hand, UAV UEs that do not utilize Uu capabilities can be part of the 3GPP ecosystem as they use U2X1 for configuration by U2X application servers and implement PC5 connections as specified by 3GPP.

[0192] A roaming 5G system architecture for U2X communication over PC5 can be configured as illustrated in FIGS. 15 and 16. Specifically, FIG. 15 illustrates a roaming 5G system architecture for U2X communication over PC5 in a local breakout scenario, and FIG. 16 illustrates a roaming 5G system architecture for U2X communication over PC5 in a home routing scenario.

[0193] A 5G system architecture between Public Land Mobile Networks (PLMNs) for U2X communication over PC5 reference points could be as follows.

[0194] - For U2X communication between PLMNs via PC5 reference point, PC5 parameters need to be set in a consistent manner between UEs within a specific area.

[0195] - The architecture for Inter-PLMN PC5 may be similar to that defined in the non-roaming 5G system architecture for U2X communication over PC5 described with reference to FIG. 14.

[0196] AF-based service parameter provisioning for U2X communication can be defined as follows.

[0197] - As defined in TS 23.287, a 5G system may provide NEF services to enable communication between a PLMN's NF and a U2X application server. Specifically, a high level view of AF-based service parameter provisioning for U2X communication may be illustrated in Fig. 17. Service parameters may also be pre-configured in the UAV using methods outside the scope of 3GPP (e.g., when not utilizing Uu functionality).

[0198] In a U2X scenario, the following may be considered:

[0199] - Usage / Usage of U2X for BRID: Message content for BRID can be defined according to regional regulations for BRID (e.g. message sets of ASTM F3411.19 or ASD-STAN prEN 4709-002 P1) and optionally according to regional means in compliance documents.

[0200] - Usage / Usage of U2X for DAA: Message content for DAA is defined by local regulations for DAA and may go beyond the scope of the given scenarios described above.

[0201] The procedures and mechanisms of TS 23.287 can be applied to U2X scenarios. Specifically, the procedure for broadcasting via PC5 for DAA collision resolution can be performed as shown in Fig. 18. Meanwhile, the procedure for broadcasting via PC5 for DAA collision resolution can be assumed that the UAV is provisioned with a U2X policy that includes a DAA collision resolution policy (e.g., unicast or broadcast communication for collision resolution, communication frequency).

[0202] Specifically, the procedure for broadcasting through PC5 for DAA collision resolution according to FIG. 18 can be performed as follows.

[0203] 1. UAV1 may receive a broadcast message from UAV2 that may include an application layer DAA payload (e.g., CAA level UAV ID, USS address of UAV2, speed, heading, position, etc.).

[0204] - Note 1: A USS address (Unmanned aerial system Traffic Management (UTM) Service Supplier address) is not required if UAV-to-UAV conflicts are resolved locally, but may be required if USS coordination of the UAVs involved in the conflict is required.

[0205] 2. UAV1 can transmit the DAA payload to the upper layer. The application layer can detect collisions by comparing the broadcast message received from UAV2 with its own trajectory and position. If UAV1's application layer detects a collision, it can initiate collision avoidance / resolution procedures with UAV2.

[0206] 3. Optionally, UAV1 can notify its USS (UTM Service Supplier) about the detected collision, including the ID of peer UAV 2.

[0207] 4. UAV1 can select a communication mode (broadcast or unicast) for DAA deconfliction based on input received from the application layer and DAA policy. If the broadcast deconfliction method is selected, the following messages can be exchanged between UAVs.

[0208] 5. UAV1 broadcasts a message (e.g., PC5-S message) (e.g., de-collision request message), which is part of the U2X functionality and may include DAA functionality indicating whether the UAV can participate in communication for protocol, DAA de-collision policy (broadcast-based, de-collision message frequency), collision detection warning, ID of other UAVs detected in collision with its CAA level UAV ID, and certain parameters (e.g., de-collision information) (e.g., trajectory correction information to avoid collision). (UAV1 broadcasts a message (eg PC5-S message), eg deconfliction request message and may include DAA capability, which is part of U2X capability and indicates whether the UAV is able to engage in communication for deconflicting protocol, DAA deconflicting policy (broadcast based, deconflicting message frequency), collision detection alert, its CAA-level UAV IDs and the one(s) from other detected conflicting UAV(s), and deconflicting specific parameters (eg trajectory correction information to avoid collision))

[0209] 6. UAV2 may broadcast a message (e.g., a PC5-S message) to provide the agreed-upon DAA deconfliction policy, updated trajectories, and other information (e.g., a message deconfliction status response, a conflict resolution warning, and the CAA-level UAV ID of the participating UAV from the receiving UAV). Subsequent broadcast messages may be exchanged between UAVs at an agreed-upon message frequency until a traffic conflict resolution (e.g., mutual position / trajectory monitoring) is reached.

[0210] The impact on services, entities and interfaces related to the above-described U2X may be as shown in Tables 5 and 6 below.

[0211] 1. UE: In addition to the capabilities defined in TS 23.501, the UE supports the following capabilities:- Reporting U2X capabilities (including DAA capabilities) and PC5 based U2X capabilities to the 5GC via the N1 reference point.- Indicating UE based U2X policy provisioning requests via the UE Policy Container.- Receiving U2X parameters from the 5GC via the N1 reference point.- Executing U2X communication procedures via the PC5 reference point.- Configuring parameters for U2X communication. These parameters can be pre-configured in the UE or provisioned or updated by signaling via the U2X1 reference point of the PCF or the U2X Application Server in the HPLMN, if in coverage. 2. AMF: In addition to the functions defined in TS 23.501, the AMF performs the following functions:- Obtains U2X related subscriber information from the UDM and stores it as part of the UE context data.- Selects a PCF that supports U2X policy / parameter provisioning and reports the PC5 capabilities of U2X to the selected PCF.- Obtains U2X related PC5 QoS information from the PCF and stores it as part of the UE context data.- Provides the communication authorization status of the UE to the NG-RAN for U2X communications over the PC5 reference point.- Provides PC5 QoS parameters related to U2X communications to the NG-RAN. 3. PCF: In addition to the functions defined in TS 23.501, it provisions parameters required for U2X communications to the UE and the AMF, including the functions specified in TS 23.287. 4. UDM: Performs subscriber management functions for U2X communications over the PC5 reference point. 5. U2X Application Server: TS 23.Implements a subset of the V2X AS capabilities defined in TS 23.501:- Includes AF capabilities and can support the following minimum capabilities:- For U2X service parameter provisioning, the U2X AS provides U2X communication parameters via PC5 and Uu reference points to the 5GC and UAV UE (via UAVC if required). 6. UDR: In addition to the capabilities defined in TS 23.501, includes the capability to store U2X service parameters. 7. NRF: In addition to the capabilities defined in TS 23.501, discovers PCFs taking U2X capabilities into account. 8. NEF: Performs U2X service parameter support functionality for the U2X AS.

[0212] U2X Subscription dataNR U2X Services AuthorizationIndicates whether the UE is authorized to use the NR sidelink for U2X services as UAV UE, UAV-C UE, or Authority UE.LTE sidelink (ie PC5) communication for U2X services.LTE UE-PC5-AMBRAMBR of UE's LTE sidelink (ie PC5) communication for U2X services.

[0213] Additionally, the most recent discussions regarding the above-described scenarios are as shown in Table 7 below.

[0214] Measurement reporting: Based on LTE principles, similar events H1 (height of aerial UE becomes higher than a threshold) and H2 (height of aerial UE becomes lower than a threshold) are introduced. Further improvements to NR are a subject of future study (FFS). Research is needed on the scaling of RRM parameters (e.g., which parameters, what is the purpose / benefit of scaling, and how it can be achieved). - Research is needed on how to limit excessive measurements and measurement reporting (FFS). - Research is needed on whether user consent is required for position reporting in CONNECTED state (FFS). - Research is needed on vertical movement of UAV UEs and their accompanying mobility (FFS). - Rel-18 NR supports reporting of altitude, position, and velocity of UAV UEs. The required accuracy and reporting mechanism, and whether further improvements are needed, are a subject of future study. - Flight path planning reporting, like LTE, will be introduced, with position lists (3D position information) and timestamps adopted as the basic contents of flight path reporting. In NR, whether timestamps are mandatory or optional is FFS. Further enhancements are also needed FFS. - Similar functionality (numberofTriggeringCells) is introduced as in LTE. In NR, whether numberoftriggerbeams is required is FFS. Research is needed on how to prevent measurement reports from being transmitted primarily when the reporting entity is reportOnLeave (FFS). - A waypoint is a planned position of a UE along a flight path, described via the existing parameter type LocationCoordinates defined in TS 37.355. - The timestamp provides the UTC time corresponding to the expected time of arrival at the waypoint and is used as a baseline. Granularity is FFS. - There are no requirements on the spatial distribution of waypoints.- The UE indicates that flight path information is available via a RRCReconfigurationComplete, RRCReestablishmentComplete, RRCResumeComplete or RRCSetupComplete message. Flight path reporting is based on the UE information request / response procedure. - The UE indicates to the network that a new flight path is available (whether initial or updated), reusing the normal request / response procedure for flight path reporting. - The UAI message can also be used by the UE to indicate that flight path information is available. - The trigger condition for a flight path update is specified by the FFS. The maximum number of waypoints in the flight path plan is left to the FFS. - When an event H1 or H2 is triggered, the content of the measurement report is configurable by the network (i.e. it can contain altitude, position information and / or RSRP / RSRQ measurements of the UAV UE). Whether the altitude of the UAV UE must be reported mandatory and what parameters / IEs are used for altitude reporting are FFS.- In NR Rel-18 UAV, the combined use of altitude dependent conditions and RSRP / RSRQ / SINR based conditions is supported for measurement reporting triggering. A combination of existing events is used. Altitude based parameter scaling is not supported as part of Rel-18 NR.- The Number of triggering cells mechanism is not applicable to inter-RAT scenarios, i.e. event B1 and B2 triggering.- The Number of triggering cells mechanism is not restricted to FR1 only, i.e. the Number of triggering cells mechanism is applicable to both FR1 and FR2 (depending on network configuration).- The UE shall not ignore or bypass the Number of triggering cells mechanism when it is configured.- The NumberOfTriggeringBeams mechanism is not introduced.- No replacement mechanism for the Number of triggering cells mechanism is introduced. - No additional mechanism based on the changed number of cells is introduced. - No prohibit timer mechanism is introduced for interference control purposes (e.g. Number of triggering cells). - ReportOnLeave is not triggered by cells that were not previously included in the measurement report for Number of triggering cells. - Support for altitude dependent multiple configurations for improved measurements and measurement reporting. The UE applies its configuration (config) according to altitude. The proposed solution aims to avoid RAN4 impact. How this is configured (e.g. different MO configurations or different parameters, etc.) is described in the FFS. Specific parameters and details are in the FFS. - Altitude dependent multiple configurations are supported at parameter / field level (i.e. different fields / values ​​within the same MO), where different values ​​(or ranges of values) of a parameter / field are applied according to altitude or altitude range. - For MO configuration parameters, at least the following items can be configured to have altitude dependent multiple configurations / values ​​for specific altitude zones: SSB-ToMeasure. The method is specified in the FFS. For L1 and L3 measurement behavior of the UE, FFS.- For MR configuration parameters, at least the following can be configured to have altitude-dependent multiple configurations / values ​​for specific altitude regions: Event A4 threshold and numberoftriggeringcells. This can be specified using FFS (e.g., through event combinations).- If altitude-dependent multiple configurations are provided, the UE applies new values ​​when moving to a new altitude (or altitude range) (similar to RRC reconfiguration). Codes, field descriptions, etc., as per existing specifications apply.- If an altitude-specific value is not explicitly configured for a particular altitude, whether to continue using the previous value or to consider the parameter as disabled should be reviewed on a case-by-case basis and can be clarified through code, field descriptions, or procedure text, as needed. Details are provided in the FFS.

[0215] Satellite gNB-related UAV handover

[0216] Figures 19 to 27 are diagrams illustrating how a UAV performs handover with respect to a satellite gNB.

[0217] In the following, it is assumed that the UAV UE must always be in a CONNECTED state. It can be connected to the ground-gNB within the ground-gNB coverage, but when it goes out of the ground-gNB coverage (e.g., in a desert, sea, or mountainous area), the UAV can connect to the ground-gNB via a satellite or maintain the connection via the satellite-gNB.

[0218] Here, connecting to a ground-gNB via a satellite may mean that the satellite gNB acts as a relay, enabling an indirect connection between the UAV UE and the ground-gNB. On the other hand, satellite-gNB may mean that a gNB (or a device that functions as a gNB) is installed on the satellite itself, enabling a direct connection with the UAV UE.

[0219] Previously, connectivity via satellite was discussed in 3GPP through the NTN WI (work item). The following triggering conditions were added for cases where a terrestrial UE performs HO from a terrestrial gNB (A) to another terrestrial gNB (B) via a satellite relay.

[0220] - 이벤트 D1: Distance between UE and a reference locationreferenceLocation1becomes larger than configured thresholddistanceThreshFromReference1and distance between UE and a reference locationreferenceLocation2becomes shorter than configured thresholddistanceThreshFromReference2;

[0221] - 이벤트 D2: Distance between UE and a moving reference location based onmovingReferenceLocationand its corresponding satellite ephemeris and epoch time broadcast inSIB19for the serving cell becomes larger than configured thresholddistanceThreshFromReference1and distance between UE and a moving reference location determined based onreferenceLocation2becomes shorter than configured thresholddistanceThreshFromReference2;

[0222] - 조건 이벤트 D1 (CondEvent D1): Distance between UE and a reference locationreferenceLocation1becomes larger than configured thresholddistanceThreshFromReference1and distance between UE and a reference locationreferenceLocation2of conditional reconfiguration candidate becomes shorter than configured thresholddistanceThreshFromReference2;

[0223] - 조건 이벤트 D2 (CondEvent D2): Distance between UE and a moving reference location determined based onmovingReferenceLocationand its corresponding satellite ephemeris and epoch time broadcast inSIB19for the serving cell becomes larger than configured thresholddistanceThreshFromReference1and distance between UE and a moving reference location determined based onreferenceLocation2of conditional reconfiguration candidate becomes shorter than configured thresholddistanceThreshFromReference2;

[0224] The reason why the location-based triggering condition as above was added in NTN is that since the signal received through the satellite is a signal transmitted from a very long distance, it may be difficult for the UE to measure the change in signal strength and trigger the measurement report at an appropriate time.

[0225] For example, referring to FIG. 19, a UE on the ground may go out of coverage without being aware of the difference in signal changes between receiving a signal at the edge of satellite_A and receiving a signal at the center of satellite_B. In this case, the existing HO triggering method cannot maintain service continuity. Considering this problem, when the UE moves away from a predetermined (or set) reference location (A) by a certain distance and / or moves closer to another predetermined (or set) reference location (B) by a certain distance, a measurement event may be triggered, thereby satisfying service continuity. This location-based measurement triggering operation may be applied to the existing basic HO procedure or the conditional HO procedure.

[0226] In this way, when a UE communicates using a satellite, the role of the satellite can be distinguished into Scenario 1 and Scenario 2 below.

[0227] - Scenario 1: The satellite can simply receive messages transmitted by the ground gNB and transparently transmit them to the ground UE (transparency mode). Alternatively, it can receive messages from the ground UE and transparently transmit them to the ground gNB.

[0228] - Scenario 2: A method in which a satellite directly performs the functions of a communication gNB. For example, a communication unit capable of performing the same (or similar) functions as a gNB is attached to the satellite, which receives messages transmitted by a ground-based gNB, interprets them, generates messages, and transmits the generated messages to a ground-based UE (regenerative mode). Alternatively, a method may be used in which a message is received from a ground-based UE, interprets them, generates messages, and transmits the generated messages to a ground-based gNB.

[0229] 1. Scenario 1

[0230] (1) Case 1-1

[0231] Referring to FIG. 20, a ground UE connected to gNB(A) can perform a HO procedure to gNB(B) via a transparency satellite (Case 1-1).

[0232] - 1. When a measurement report is triggered for a UE connected to a ground-gNB(A), the UE can measure the signal strength of the current serving cell and neighboring cells and report the same to the ground-gNB(A). In this case, the measurement report on the signal strength can be transmitted to the source gNB, ground-gNB(A), via a satellite (or satellite relay).

[0233] - 2. Ground-gNB (A) can determine HO and transmit a message requesting HO to the target ground-gNB (B).

[0234] - 3. Ground-gNB (A) can receive permission or HO request ACK for the HO request from the target ground-gNB (B).

[0235] - 4. Ground-gNB (A) can transmit an RRC message (e.g., RRCReconfiguration message) containing an HO related command (HO command) to the UE.

[0236] - 5. At this time, the ground-gNB (A) may transmit an SN (Sequence Number) status Transfer message to the target ground-gNB (B). Here, the SN status Transfer message may be a message for transmitting an uplink PDCP SN receiver status and a downlink PDCP SN transmitter status for a data radio bearer (DRB).

[0237] - 6. When the UE receives the RRCReconfiguration message, it can perform RACH to the target ground-gNB (B) and complete the HO procedure by transmitting an RRCReconfigurationComplete message to the target ground-gNB (B).

[0238] - 7. The UE is connected to the target ground-gNB (B), and 8. The target ground-gNB (B) can send a UE context release message to the source ground-gNB (A).

[0239] (2) Case 1-2

[0240] Referring to FIG. 21, a ground UE connected to gNB(B) via a Transparency satellite can perform a HO procedure to ground-gNB(A) (Case 1-2).

[0241] - 1. When a measurement report is triggered for a UE connected to the ground-gNB(B) via a transparency satellite, the UE can report the measurement value to the ground-gNB(B) via the transparency satellite.

[0242] - 2. (source) Ground-gNB (B) can decide on HO and transmit a request for HO to the target ground-gNB (A).

[0243] - 3. (source) Ground-gNB (B) can receive a response to the HO request from the target ground-gNB (A).

[0244] - 4. (Source) Ground-gNB(B) can send an RRCReconfiguration message to the UE to command HO via transparency satellite.

[0245] - 5. At this time, the ground-gNB (B) can transmit SN status Transfer to the target ground-gNB (A).

[0246] - 6. The UE can complete HO by transmitting an RRCReconfigurationComplete message to the target ground-gNB(A) after performing the RACH procedure to the target ground-gNB(A) based on the RRCReconfiguration message.

[0247] - 7. The UE is connected to the target ground-gNB (A), and 8. The target ground-gNB (A) can send a UE context release message to the source ground-gNB (A).

[0248] When a UE performs HO operation as in Case 1-1 and / or Case 1-2, the process in which the UE performs measurement reporting via transparency satellite and the (Source) ground-gNB transmits an RRCReconfiguration message related to the measurement reporting to the UE (and / or the UE transmits an RRCReconfigurationComplete message to the target ground-gNB) may take significantly longer than the HO between a typical ground-gNB and the UE. In this case, the reported measurement values ​​may be out-of-date values, which may be disadvantageous in selecting an appropriate target-gNB. Therefore, it may be more appropriate to apply a conditional HO (CHO) scheme to operations related to HO from a ground UE connected to gNB (A) to gNB (B) via transparency satellite. This will be described in detail in Case 1-3 and Case 1-4 below.

[0249] (3) Case 1-3

[0250] Referring to FIG. 22, a ground UE connected to ground-gNB (A) can perform a CHO procedure to ground-gNB (B) via a transparency satellite (Case 1-3).

[0251] - 1. A ground UE connected to a ground-gNB (A) can report a measurement value when a measurement report is triggered. For example, the ground UE can report the measurement value to the ground-gNB (A) via a transparency satellite (or satellite relay).

[0252] - 2. (source) Ground-gNB(A) can determine HO based on the above reported measurement values ​​and transmit a HO request message to candidate target gNB(s).

[0253] - 3. The candidate target gNB(s) that accepted the above HO request can send a response allowing HO to the (source) ground-gNB(A).

[0254] - 4. (source) Ground-gNB(A) can transmit CHO-related configuration to ground UE. For example, ground-gNB(A) can provide CHO-related configuration to ground UE through RRCReconfiguration message.

[0255] - 5. The ground UE can transmit RRCReconfigurationComplete to the ground-gNB (A) when it has received the settings related to CHO.

[0256] - 6. The ground-gNB(A) may provide an Early status transfer message to the candidate target gNB(s). Here, the Early status transfer message may include information about the RLC and PDCP layer states of the ground UE.

[0257] - 7. The ground UE can perform RACH to the target ground-gNB(B) through the transparency satellite and complete HO with the target ground-gNB(B) when the HO condition is satisfied based on the CHO condition according to the above CHO setting.

[0258] - 8. The target ground-gNB (B) can provide a message related to the success of HO with the ground UE to the source ground-gNB (A).

[0259] - 9. The source ground-gNB (A) can provide an SN status transfer message to the target ground-gNB (B).

[0260] - 10. The source ground-gNB (A) can transmit a message related to HO cancellation to the remaining candidate target gNBs except the target ground-gNB (B) among the candidate target gNB (s).

[0261] (4) Case 1-4

[0262] Referring to FIG. 23, a ground UE connected to ground-gNB(B) via a Transparency satellite can perform CHO to ground-gNB(A) (Case 1-4).

[0263] - 1. When a measurement report is triggered, the ground UE performs a measurement report to the (source) ground-gNB (B) via the transparency satellite.

[0264] - 2. (Source) The ground-gNB can determine the CHO and transmit a HO request message to the candidate target ground-gNB(s) selected based on the measurement results.

[0265] - 3. The candidate target ground-gNB(s) can transmit a response to the (source) ground-gNB(B) if the HO is allowed.

[0266] - 4. (source) Ground-gNB(B) can perform CHO-related configuration to the ground UE. For example, (source) Ground-gNB(B) can provide the ground UE with an RRCReconfiguration message including CHO configuration for CHO trigger conditions, etc.

[0267] - 5. The ground UE that received the configuration for CHO can send an RRCReconfigurationComplete message to the (source) ground-gNB (B).

[0268] - 6. Ground-gNB(B) can provide an Early status transfer message to candidate target gNB(s).

[0269] - 7. The ground UE can complete the CHO handover procedure by performing RACH to the target gNB (A) when the set specific HO triggering conditions are satisfied.

[0270] - 8. The target ground-gNB (A) can provide a message related to the success of HO with the ground UE to the source ground-gNB (B).

[0271] - 9. The source ground-gNB (B) can provide an SN status transfer message to the target ground-gNB (A).

[0272] - 10. The source ground-gNB (B) can transmit a message related to HO cancellation to the remaining candidate target gNBs except the target ground-gNB (A) among the candidate target gNB (s).

[0273] The CHO procedure according to Cases 1-3 and / or 1-4 can receive HO-related settings for multiple candidate target ground-gNBs in advance and trigger HO based on measurements taken by the ground UE. This has the advantage over the typical HO procedure in that HO can be determined based on currently measured measurements.

[0274] 2. Scenario 2

[0275] (1) Case 2-1

[0276] Referring to FIG. 24, a ground UE connected to gNB (A) can perform HO to satellite-gNB (B).

[0277] - 1. (source) A ground UE connected to ground-gNB(A) can perform measurement reporting to (source) ground-gNB(A).

[0278] - 2. (source) Ground-gNB (A) can determine HO based on the measurement report value and transmit an HO request message to (target) satellite-gNB (B).

[0279] - 3. The ground-gNB (A) can receive a response message from the satellite-gNB (B) that HO is allowed.

[0280] - 4. Ground-gNB (A) can transmit an RRCReconfiguration message including an HO command to the ground UE.

[0281] - 5. Ground-gNB (A) can transmit an SN status transfer message to satellite-gNB (B).

[0282] - 6. After receiving the RRCReconfiguration message including the HO command, the ground UE can perform HO to the target satellite-gNB (B) and complete the HO procedure by transmitting the RCReconfigurationComplete message to the ground-gNB (A).

[0283] - 7. The UE is connected to the target satellite-gNB (B), and 8. The target satellite-gNB (B) can send a UE context release message to the source ground-gNB (A).

[0284] (1) Case 2-2

[0285] Referring to FIG. 25, a ground UE connected to a satellite-gNB (B) can perform HO to a ground-gNB (A).

[0286] - 1. A ground UE connected to a satellite-gNB(B) can perform a measurement report to the satellite-gNB(B) when a measurement report is triggered.

[0287] - 2. Satellite-gNB (B) can determine HO based on the above measurement report, determine target ground-gNB (A), and transmit an HO request message to target ground-gNB (A).

[0288] - 3. Satellite-gNB (B) can receive a response from Target Ground-gNB (A) that HO is allowed.

[0289] - 4. (source) Satellite-gNB(B) can send an RRCReconfiguration message containing a HO command to the ground UE.

[0290] - 5. (source) Satellite-gNB (B) can transmit an SN status transfer message to Target ground-gNB (A).

[0291] - 6. After receiving the RRCReconfiguration message including the HO command, the ground UE can perform HO to the target ground-gNB (A) and complete the HO procedure by transmitting the RRCReconfigurationComplete message to the satellite-gNB (B).

[0292] - 7. The UE is connected to the target ground-gNB (A), and 8. The target ground-gNB (A) can send a UE context release message to the source satellite-gNB (B).

[0293] In Cases 2-1 and 2-2, as in the HO case of Scenario 1 described above, the time required for transmitting the measured value from the ground UE to the satellite-gNB, for the satellite-gNB to make a HO request to the ground-gNB, and for receiving admission (and / or for transmitting the measured value from the ground UE to the ground-gNB, but for the ground-gNB to request HO to the satellite-gNB, and for receiving admission) may be much longer than in the case of a general HO. In this case, the measured value measured by the ground UE may be an out-of-date value, and determining HO based on this may not be suitable for achieving good performance. Therefore, conditional HO (CHO) may be a more appropriate operation for HO used in satellite communication. This will be described in detail in Cases 2-3 and 2-4 below.

[0294] (3) Case 2-3

[0295] Referring to FIG. 26, a ground UE connected to a ground-gNB (A) can perform a CHO procedure with a satellite-gNB (B).

[0296] - 1. When measurement reporting is triggered, the ground UE can report measurement values ​​to the (source) ground-gNB(A).

[0297] - 2. (source) Ground-gNB(A) can transmit an HO request message to candidate satellite-gNB(s) based on the above measurement report.

[0298] - 3. (source) Ground-gNB(A) can receive admission for HO ( / HO Request ACK) from candidate satellite-gNB(s).

[0299] - 4. The (source) ground-gNB (A) receiving this can transmit an RRCReconfiguration message to the ground UE for CHO-related settings for multiple candidate satellite-gNB (s).

[0300] - 5. The ground UE may send RRCReconfigurationComplete to the (source) ground-gNB(A) when it has received the settings related to CHO.

[0301] - 6. The ground-gNB(A) may provide an Early status transfer message to the candidate target satellite-gNB(s). Here, the Early status transfer message may include information about the RLC and PDCP layer states of the ground UE.

[0302] - 7. The UE can perform HO by selecting one target satellite-gNB among candidate target satellite-gNB(s) and performing RACH procedure when conditional HO (CHO) is triggered based on the set value.

[0303] - 8. The target satellite-gNB (B) can provide a message related to the success of HO with the ground UE to the ground-gNB (A).

[0304] - 9. Ground-gNB (A) can provide an SN status transfer message to the target satellite-gNB (B).

[0305] - 10. Ground-gNB(A) can transmit a message related to HO cancellation to the remaining candidate target satellite-gNB(s) except for target satellite-gNB(B).

[0306] (4) Case 2-4

[0307] Referring to FIG. 27, a ground UE connected to a satellite-gNB (B) can perform a CHO procedure with a ground-gNB (A).

[0308] - 1. When a measurement report is triggered, the ground UE performs a measurement report to the satellite-gNB(B).

[0309] - 2. Satellite-gNB(B) can determine CHO and transmit HO request message to candidate target ground-gNB(s) selected based on measurement results.

[0310] - 3. If the candidate target ground-gNB(s) allows HO, it can transmit a response to it to the satellite-gNB(B).

[0311] - 4. Satellite-gNB(B) can perform CHO-related configuration to ground UE. For example, satellite-gNB(B) can provide RRCReconfiguration message including CHO configuration for CHO trigger conditions, etc. to ground UE.

[0312] - 5. The ground UE that has received the configuration for CHO can send an RRCReconfigurationComplete message to the satellite-gNB(B).

[0313] - 6. Satellite-gNB(B) can provide an Early status transfer message to candidate target ground-gNB(s).

[0314] - 7. When a ground UE satisfies a specific HO triggering condition set, the ground UE performs a RACH procedure to a target ground-gNB(A) selected from among candidate target ground-gNB(s), and completes a CHO procedure with the target ground-gNB(A) through the RACH procedure.

[0315] - 8. The target ground-gNB (A) can provide a message related to the success of HO with the ground UE to the satellite-gNB (B).

[0316] - 9. Satellite-gNB (B) can provide an SN status transfer message to the target ground-gNB (A).

[0317] - 10. Satellite-gNB(B) can transmit a message related to HO cancellation to the remaining candidate target ground-gNB(s) except for target ground-gNB(A).

[0318] Below, a method of applying the above-described HO procedure or CHO procedure by additionally considering the flight path of the UAV UE is described in detail.

[0319] (4) Case 2-4

[0320] Referring to FIG. 27, a ground UE connected to a satellite-gNB (B) can perform a CHO procedure with a ground-gNB (A).

[0321] - 1. When a measurement report is triggered, the ground UE performs a measurement report to the satellite-gNB(B).

[0322] - 2. Satellite-gNB(B) can determine CHO and transmit HO request message to candidate target ground-gNB(s) selected based on measurement results.

[0323] - 3. If the candidate target ground-gNB(s) allows HO, it can transmit a response to it to the satellite-gNB(B).

[0324] - 4. Satellite-gNB(B) can perform CHO-related configuration to ground UE. For example, satellite-gNB(B) can provide RRCReconfiguration message including CHO configuration for CHO trigger conditions, etc. to ground UE.

[0325] - 5. The ground UE that has received the configuration for CHO can send an RRCReconfigurationComplete message to the satellite-gNB(B).

[0326] - 6. Satellite-gNB(B) can provide an Early status transfer message to candidate target ground-gNB(s).

[0327] - 7. When a ground UE satisfies a specific HO triggering condition set, the ground UE performs a RACH procedure to a target ground-gNB(A) selected from among candidate target ground-gNB(s), and completes a CHO procedure with the target ground-gNB(A) through the RACH procedure.

[0328] - 8. The target ground-gNB (A) can provide a message related to the success of HO with the ground UE to the satellite-gNB (B).

[0329] - 9. Satellite-gNB (B) can provide an SN status transfer message to the target ground-gNB (A).

[0330] - 10. Satellite-gNB(B) can transmit a message related to HO cancellation to the remaining candidate target ground-gNB(s) except for target ground-gNB(A).

[0331] For UAV UEs, they are required to report their own flight paths. Flight paths can be reported using timestamps and waypoint information values, and the timestamp granularity used here is 1 second. Flight paths can be updated, and flight path updates can be triggered when the waypoint / timestamp values ​​reported by the UAV UE exceed a threshold set by the network. In addition, if thresholds are set for both waypoints and timestamp values, flight path reporting can be triggered (e.g., flight path reporting for flight path update is triggered) when either value exceeds the threshold.

[0332] Below, we describe in detail how a UAV UE performs cell selection or the process of connecting to a gNB using the UAV's flight path. For example, below, we propose a method for a UAV UE to more easily perform cell selection or HO when the UAV UE moves to a new cell.

[0333] RACH-less connection procedure using the flight path of the UAV UE

[0334] A UAV UE can report its flight path (toward a specific destination) to a base station during flight. It is assumed that the flight path of the UAV UE is known to all gNB(s) along the path or flight path of the UAV UE through the ID (of the specific UAV UE). For example, when the gNB(s) along the path of the UAV UE are in an (RRC) CONNECTED state with the UAV UE, they can recognize which path the UAV UE is trying to travel.

[0335] Additionally, for a UAV UE, it can be assumed that the UAV UE moves through a virtual aerial tunnel. For example, the range in which the UAV can move can be defined through a reference point for indicating the virtual aerial tunnel and a threshold value of a distance for indicating the 3D space of the tunnel.

[0336] In this way, for a UAV UE moving through a virtual aerial tunnel, gNBs may know their coverage (or coverage map) for the virtual aerial tunnel associated with the UAV UE and an appropriate TA (Timing Advance) value to be used at a specific waypoint of the virtual aerial tunnel. For example, the gNB may construct its own coverage map (e.g., generation of a coverage map using a method such as AI / ML) based on measurement reports reported by UAV UEs passing through the virtual aerial tunnel, 3D position information values ​​(within the virtual aerial tunnel), etc. In addition, the gNB may infer an appropriate TA value at a given location based on the TA values ​​(values ​​assigned by the gNB) used / applied to the CONNECTED UAV UEs at a specific location (or a specific waypoint). Alternatively, since it can be assumed that the signal is rarely shaded by buildings, etc. in the case of a UAV UE, the gNB may calculate the TA value to be used using the distance value between the UAV and the gNB.

[0337] Under the above-described assumptions, the following UAV UE operations can be considered. Alternatively, the UAV UE operations described below may also be applied even when the above-described assumptions are not assumed.

[0338] Figures 28 to 30 are diagrams for explaining the HO procedure related to a UAV UE moving through the coverage area of ​​gNB (A) to the coverage area of ​​gNB (b).

[0339] In the following, the UAV UE can move into the coverage area of ​​gNB (A), the Out of Coverage (OoC) area, the coverage area of ​​gNB (b) (case 1), or move from the coverage area of ​​gNB (A) to the coverage area of ​​gNB (b) (case 2). The following describes in detail how the HO procedure is performed in each case.

[0340] (1) Case 1

[0341] Referring to Fig. 28, the UAV UE can move from gNB(A) to gNB(B) along the indicated solid line (Case 1). At this time, the UAV UE can also pass through the OoC (Out of Coverage) area as illustrated in Fig. 28. For example, the UAV UE can pass through the OoC (out-of-coverage) area via gNB(A) and then enter the gNB(B) area.

[0342] At this time, a UVA UE that is in a CONNECTED state to gNB(A) may perform HO (Handover). Here, the HO performed by the UAV UE may be different from the existing HO. For example, in the case of the existing HO, a ground UE belonging to the coverage of gNB(A) may report a measurement value to gNB(A) when a measurement report is triggered. gNB(A) may decide whether to perform HO to gNB(B) based on the reported measurement value. However, a different HO operation may be expected for the UAV UE. For example, even if the UAV UE does not report the signal strength of a cell belonging to gNB(B) as a measurement value, gNB(A) may command the UAV UE to perform HO to gNB(B) based on the UAV's flight path. In this case, the UAV UE may be commanded to perform HO for a cell that the UAV UE did not report from its serving gNB( / cell)(A).

[0343] Also, referring to FIG. 29, when a (Conditional) HO command for a UAV UE is issued, a source gNB (e.g., gNB(A)) may also set a TA value (and / or) an uplink resource for transmitting an RRCReconfigurationComplete message to a target gNB (e.g., gNB(B)) that can be used for uplink synchronization when the HO command is issued to the UAV UE (S291). Here, the TA value and / or the uplink resource may be a value received by the source gNB from the target gNB. In this case, from the target gNB's perspective, the uplink resource may be treated as a resource reserved to be used by the UAV UE after a certain period of time. Since the source gNB knows the flight path of the UAV UE, it can transmit information about the flight path (or predicted movement path) to the target gNB when making a HO request. At this time, information such as 3D location information, movement speed, and direction of the UAV UE may also be transmitted to the target gNB. The target gNB may also know which TA value is appropriate to use when the UAV UE reaches the coverage of the target gNB through the transmitted flight path, 3D location information, and movement speed information. For example, the target gNB may estimate when and at what location the UAV UE will arrive when it reaches the coverage of the target gNB. In this case, the target gNB may transmit to the source gNB a message allowing HO, which includes a TA value and / or uplink resource information that the UAV UE can use when transmitting an initial message (e.g., an RRCReconfigurationComplete message) to the target gNB.Based on this, the message of the source gNB (e.g., an RRC message including a HO command) may further include information about the TA value and / or uplink resources transmitted by the target gNB, and the UAV UE may transmit an initial message (e.g., an RRCReconfiguration or RRCReconfigurationComplete message) to the target gNB without RACH based on the message of the source gNB (S293).

[0344] And / or, the message configuring the UAV UE to transmit an initial message to the target gNB without RACH in the cell coverage belonging to the target gNB may further include information about a location (or range) and / or a time or time interval information (duration) for which the TA value and / or uplink resource configuration is valid. For example, the message (RRCReconfiguration message) including the HO command transmitted by the source gNB may further include information about the TA value, uplink resource, a time interval and a location range for which the TA and uplink resource are valid. In this case, the UAV UE (or the target gNB) may transmit an initial message for connection to the target gNB without RACH in the configured location (range) and / or time or time interval information (duration). For example, the source gNB may predict / determine a time interval and area in which the UAV UE enters the coverage of the target gNB when the UAV UE is predicted to pass through the OoC area based on the flight path, and may determine information about the time interval and location range based thereon.

[0345] When the above-described content is applied to CHO, TA (list) and uplink resources can be set for each candidate target gNB / cell. Similarly, location (or location range) and / or time information (duration) can also be set for each target gNB / cell.

[0346] (2) Case 2

[0347] In case 2, the HO method described in relation to case 1 can be similarly applied even when the UAV UE moves through the cell coverage area of ​​gNB (A) to the cell coverage area of ​​gNB (B) as illustrated in FIG. 30.

[0348] For example, the UAV UE may receive a (Conditional) HO command or an RRC message including the HO command (e.g., an RRCReconfiguration message) in the cell coverage of the gNB (A). The (Conditional) HO command may include a TA value capable of achieving uplink synchronization with the target gNB (B) and information about uplink resources for transmitting an initial message to the target gNB (B). And / or, the HO command or the RRC message including the HO command may further include configuration information about a time range and / or a location range in which the configured TA value can be applied and the uplink resources can be used to transmit the initial message to the target gNB (B). In this case, the UAV UE may transmit an initial connection or an initial message (e.g., an RRCReconfigurationComplete) message to the target gNB without a RACH. For example, the UAV UE may transmit an initial connection to the target gNB or an initial message for initial connection to the target gNB without a RACH procedure based on the TA value and uplink resources when the UAV UE falls within a time interval and / or location (or location range) included in the HO command or an RRC message including the HO command.

[0349] When the source gNB (e.g., gNB(A)) described above receives TA information from the target gNB (e.g., gNB(B)) to be used when the UAV UE transmits an initial message to the target gNB / cell, the transmitted TA information may include at least one TA value per waypoint. For example, the TA information may include different TA values ​​per waypoint, which is to prepare for a case where the position of the UAV UE within the cell of the target gNB cannot be accurately predicted at the time of HO configuration. Even when the TA values ​​are configured differently for each waypoint, the uplink resource (and / or uplink grant) may be configured to be shared for multiple TA values. Even if multiple TA values ​​are configured for each waypoint, the UAV UE selects and uses only one of the configured TA values, so that transmission of the initial connection message is possible even if only one uplink resource is configured.

[0350] Even if the UAV UE performs the RACH-less handover procedure as described above with the target gNB, the handover procedure may not succeed. For example, the UAV UE may not receive an ACK (or RLC ACK) for the RRCReconfigurationComplete message from the target gNB. In this case, the UAV UE may fallback to a general RACH procedure (e.g., 2-step RACH, 4-step RACH) and perform the HO procedure for the target gNB.

[0351] When a UAV UE moves from the cell coverage of gNB(A) (via the OoC area) to the cell coverage of gNB(B), the UAV UE may be in RRC IDLE / INACTIVE state. In this case, the UAV UE may be configured in advance using the flight path information. Here, 'configured in advance' may mean that the configuration is configured when the UAV UE is in a CONNECTED state with the corresponding cell( / gNB). When the UAV UE is in a CONNECTED state with the gNB( / cell), it can be assumed that the gNB( / cell) knows information about the flight path of the UAV UE. In this case, the gNB currently in the CONNECTED state may know which gNB / cell the UAV UE may pass through while passing through the flight path. Therefore, when the UAV UE is in the CONNECTED state, the gNB may inform the UAV UE in advance of information about other gNBs / cells by considering the flight path of the UAV UE. In the case of a typical UE (e.g., a ground UE) in an IDLE / INACTIVE state, even if the UE has been in a CONNECTED state, the gNB in ​​the CONNECTED state cannot know where the UE will move in the future. However, in the case of a UAV UE, the gNB can estimate the time and location of the UAV UE through the flight path of the UAV UE, and thus can perform an operation of notifying the UAV UE in advance of information about the gNB / cell it will pass by in the future.

[0352] For example, when the UAV UE is (briefly) CONNECTED to gNB(A) (or, when the flight path is updated, etc.), the UAV UE may receive information about gNB(B) from gNB(A). The information about gNB(B) received at this time can be used when the UAV UE passes through the cell coverage of gNB(B) in IDLE / INACTIVE state. Specifically, the information that can be informed to the UAV UE may include the following information. For example, it may be information that is helpful in searching for a cell at the corresponding location. Specifically, when the UAV UE enters the cell coverage of gNB(B) in IDLE / INACTIVE state, the UAV UE may be informed in advance of information that is helpful in searching for the cell of gNB(B) from another gNB / cell (for example, when it was in RRC_CONNECTED state in the cell coverage of another (gNB(A)) previously). For example, information that helps in searching for a cell may include a frequency range ( / BWP) available in the corresponding coverage of the gNB(B), a center frequency of the available frequency range ( / BWP), and / or a transmission period of a signal (e.g., SSB / PSS) for synchronization and related information (e.g., SSB search window). In addition, the UAV UE may also be informed in advance (by requesting) through another gNB of the transmission period of the SI (System Information) of the gNB(B) and / or specific SIB information.

[0353] The proposed method described above proposes a RACH less (conditional) HO scheme when moving from an RRC_CONNECTED state to the coverage of another cell / gNB using the flight path of the UAV UE. In addition, when the UAV UE is expected to move from an RRC_IDLE / INACTIVE state to the coverage of another cell / gNB, a method is proposed in which the UAV UE receives information about the expected cell / gNB from another cell / gNB to which the UAV UE was previously CONNECTED. This can be applied by taking advantage of the characteristic of a UAV UE that moves along a preset flight path, unlike a general UE. Alternatively, the proposed method can be similarly applied to a UE whose movement path is preset (or set) even if it is not a UAV UE. In addition, the content of the proposed method described above is not limited to UAV UEs, but can be applied to all UEs using NTN / TN (Non-terrestrial Network / terrestrial Network).

[0354] In this way, the proposed invention can effectively support RACH less HO in case of a UAV UE in a CONNECTED state with a determined path, and can support cell selection in a new cell / gNB more easily (or, faster / with lower power) in case of a UAV UE in an IDLE / INACTIVE state.

[0355] Figure 31 is a diagram for explaining how a terminal performs handover (HO).

[0356] As described above, a UE may be a device associated with a UAV moving in the sky along a flight path toward a preset destination. As described above, the UE may provide information about its flight path in advance to a gNB or base station. During flight, the UE may connect to not only a ground-based gNB but also a satellite-based gNB. Since the UE moves at a relatively high speed along its flight path, frequent handover operations may be performed. Below, a method for a UE associated with a UAV to perform a (conditional) handover (HO) procedure is described in detail, based on the proposals described in FIGS. 16 to 30 .

[0357] Specifically, referring to FIG. 31, the UE may transmit information on a predicted movement path for moving to a specific destination to the first base station (or the first gNB) (S311). The UE may move to the specific destination along the predicted movement path at a height above a certain height, and may perform operations related to the proposed handover while moving to the specific destination. As illustrated in FIG. 28, the predicted movement path of the UE may pass through the OoC state area in the coverage area of ​​the first base station (gNB A) and the coverage area of ​​the second base station (gNB B). Alternatively, as illustrated in FIG. 30, the predicted movement path of the UE may pass through the coverage area of ​​the second base station (gNB B) from the coverage area of ​​the first base station (gNB A).

[0358] Next, the UE can receive a handover (HO) command targeting a second base station from the first base station (S313). Here, the HO command can be transmitted from the first base station even if a measurement report is not triggered for the UE. For example, the first base station can determine a handover for the UE based on the predicted movement path. In other words, the UE can receive an RRC message (e.g., an RRCReconfiguration message) including a HO command indicating a handover for the second base station from the first base station without triggering the measurement report. In this case, the HO command or the RRC message can further include reserved TA information and uplink resource information for the second base station. In addition, the HO command or the RRC message can further include information about a specific time period and / or a specific (geographic) area in which the reserved TA information and the uplink resource information are valid. For example, the HO command or the RRC message may further include information about the specific time period and / or specific area as a validity condition of the TA information and the uplink resource information or as a trigger condition of the HO command.

[0359] Next, the UE can perform a HO procedure for the second base station based on the HO command (S315). At this time, as described above, the UE can perform / complete the HO procedure without a RACH procedure for the second base station based on the TA information and uplink resource information included in the HO command. For example, the UE can complete the handover procedure with the second base station by transmitting an initial message (e.g., an RRCReconfigurationComplete message) for handover (or for performing / completing the HO procedure) to the second base station based on the TA information and uplink resource information.

[0360] Alternatively, as described above, the HO command or the RRC message may further include information about a specific time interval and / or a specific (geographic) area in which the reserved TA information and the uplink resource information are valid. In this case, the UE may perform / complete the HO procedure based on the TA information and uplink resource information included in the HO command (only) when the UE is operating within the specific time interval included in the HO command and is located within the specific area. For example, the UE may perform the HO procedure with the second base station based on the HO command when the UE is operating within the specific time interval and is located within the specific area. For example, even if the UE receives the HO command, it may not immediately perform the HO procedure with the second base station, but may determine whether the conditions of the specific time interval and the specific area are satisfied. The UE may determine / determine that the TA information and uplink resource information included in the HO command are valid when the UE is operating within the specific time interval and its location is located within the specific area, and may perform / complete the HO procedure for the second base station by transmitting an initial message based on the TA information and uplink resource information. Alternatively, the UE may determine that the TA information and uplink resource information included in the HO command are valid when the UE is located within the specific area within the specific time interval, and may perform / complete the HO procedure by transmitting an initial message for the second base station based on the TA information and uplink resource information without performing a RACH procedure. This is because the UE may attempt to perform an unnecessary HO procedure by the HO command within the OoC area as illustrated in FIG. 28.In other words, the HO command may further include information about the specific time interval and the specific area as a validity condition of the TA information and uplink resource information (or a trigger condition of the HO procedure) so that the UE can perform the HO procedure for the second base station only after passing through the OoC area. Alternatively, if the UE enters the coverage of the second base station directly without passing through the OoC area as illustrated in FIG. 30, the HO command may not include information about the specific time interval and the specific area. In this case, the UE can immediately perform the HO procedure for the second base station based on the HO command.

[0361] Figure 32 is a diagram for explaining a method for a first base station to transmit a handover (HO) command to a UE.

[0362] Referring to FIG. 32, the first base station (or the first gNB) may receive information about the predicted movement path of the UE from the UE (S321). Here, the UE may be a UAV UE moving to the specific destination along the predicted movement path from a certain height or higher. As illustrated in FIG. 28, the predicted movement path of the UE may pass through the OoC state area in the coverage area of ​​the first base station (gNB A) and enter the coverage area of ​​the second base station (gNB B). Alternatively, as illustrated in FIG. 30, the predicted movement path of the UE may enter the coverage area of ​​the second base station (gNB B) from the coverage area of ​​the first base station (gNB A).

[0363] Next, the first base station may transmit a request message requesting a handover related to the UE to a second base station having coverage on the predicted movement path based on the predicted movement path (S323). For example, the first base station may transmit a handover request message to the second base station when movement to a second base station, which is another base station, is predicted based on the predicted movement path even without receiving a separate measurement report from the UE. For example, the first base station may predict / determine at what time and at what location the UE will be located based on the virtual aerial tunnel and / or coverage map of the UE described above. Here, the HO request may further include information on the predicted movement path of the UE and / or mobility information of the UE. The predicted movement path of the UE and / or the mobility information of the UE may be information necessary for the second base station to reserve TA information and uplink resources to be applied to the transmission of the initial message by the UE. In other words, the first base station may further include the predicted movement path and mobility information in the HO request to request the second base station to reserve in advance a TA value and uplink resources for the UE to transmit the initial message.

[0364] Next, the first base station can receive a message for HO approval including TA information and uplink resource information from the second base station (S325). For example, the second base station can predict the location of the UE when the UE enters the coverage of the second base station based on information about the predicted movement path of the UE and / or mobility information of the UE, determine an appropriate TA value based on the predicted location of the UE, and reserve / determine uplink resources for the UE to transmit an initial message. The second base station can transmit a message for HO approval including TA information including the determined TA value and uplink resource information for the uplink resources to the first base station.

[0365] Next, the first base station can transmit a handover (HO) command targeting the second base station to the UE (S327). Here, the HO command or the RRC message may further include TA information and uplink resource information transmitted from the second base station. In addition, the HO command or the RRC message may further include information about a specific time period and / or a specific (geographical) area in which the reserved TA information and the uplink resource information are valid. For example, as described above, if (only) it is predicted that the UE will enter the coverage of the second base station after passing through the OoC area based on the predicted movement path, the first base station may transmit a HO command to the UE that further includes information about a specific time period and a specific area as a validity condition of the TA information and uplink resource information or a trigger condition of the HO command. For example, the first base station can predict a time interval and a geographic area in which the UE will pass through the OoC section and enter the coverage of the second base station based on the predicted movement path, and can determine the specific time interval and the specific area based on the predicted time interval and geographic area.

[0366] In this way, the proposed invention can effectively support the performance of a RACH-less HO procedure for the UE by providing the UE with a TA value and uplink resources for a predicted target base station in advance through an HO command based on the predicted movement path of the UE. And / or, the proposed invention can prevent the UE from performing the HO procedure in the OoC region by providing a specific time interval and a specific area as a validity condition of the TA value and uplink resource information based on the predicted movement path through the HO command, thereby minimizing unnecessary power consumption in the UE. And / or, the proposed invention can effectively provide information for searching for a target base station in advance for a UAV UE predicted to be in an IDLE / INACTIVE state by predicting in advance a target base station that will perform the HO procedure based on the predicted movement path.

[0367] Examples of communication systems to which the invention applies

[0368] Although not limited thereto, the various descriptions, functions, procedures, proposals, methods and / or operational flowcharts of the present invention disclosed in this document may be applied to various fields requiring wireless communication / connection (e.g., 5G) between devices.

[0369] Hereinafter, more specific examples will be provided with reference to the drawings. In the drawings / descriptions below, the same drawing reference numerals may represent identical or corresponding hardware blocks, software blocks, or functional blocks, unless otherwise described.

[0370] Figure 33 illustrates a communication system applied to the present invention.

[0371] Referring to FIG. 33, a communication system (1) applied to the present invention includes a wireless device, a base station, and a network. Here, the wireless device refers to a device that performs communication using a wireless access technology (e.g., 5G NR (New RAT), LTE (Long Term Evolution)) and may be referred to as a communication / wireless / 5G device. Although not limited thereto, the wireless device may include a robot (100a), a vehicle (100b-1, 100b-2), an XR (eXtended Reality) device (100c), a hand-held device (100d), a home appliance (100e), an IoT (Internet of Things) device (100f), and an AI device / server (400). For example, the vehicle may include a vehicle equipped with a wireless communication function, an autonomous vehicle, a vehicle capable of performing vehicle-to-vehicle communication, etc. Here, the vehicle may include an Unmanned Aerial Vehicle (UAV) (e.g., a drone). XR devices include AR (Augmented Reality) / VR (Virtual Reality) / MR (Mixed Reality) devices, and can be implemented in the form of HMD (Head-Mounted Device), HUD (Head-Up Display) installed in a vehicle, television, smartphone, computer, wearable device, home appliance, digital signage, vehicle, robot, etc. Mobile devices can include smartphone, smart pad, wearable device (e.g., smart watch, smart glass), computer (e.g., laptop, etc.), etc. Home appliances can include TV, refrigerator, washing machine, etc. IoT devices can include sensors, smart meters, etc. For example, base stations and networks can also be implemented as wireless devices, and a specific wireless device (200a) can act as a base station / network node to other wireless devices.

[0372] Wireless devices (100a to 100f) can be connected to a network (300) via a base station (200). Artificial Intelligence (AI) technology can be applied to the wireless devices (100a to 100f), and the wireless devices (100a to 100f) can be connected to an AI server (400) via the network (300). The network (300) can be configured using a 3G network, a 4G (e.g., LTE) network, a 5G (e.g., NR) network, etc. The wireless devices (100a to 100f) can communicate with each other via the base station (200) / network (300), but can also communicate directly (e.g., sidelink communication) without going through the base station / network. For example, vehicles (100b-1, 100b-2) can communicate directly (e.g., V2V (Vehicle to Vehicle) / V2X (Vehicle to Everything) communication). In addition, IoT devices (e.g., sensors) can communicate directly with other IoT devices (e.g., sensors) or other wireless devices (100a to 100f).

[0373] Wireless communication / connection (150a, 150b, 150c) can be established between wireless devices (100a~100f) / base stations (200), and base stations (200) / base stations (200). Here, wireless communication / connection can be achieved through various wireless access technologies (e.g., 5G NR) such as uplink / downlink communication (150a), sidelink communication (150b) (or D2D communication), and communication between base stations (150c) (e.g., relay, IAB (Integrated Access Backhaul). Through wireless communication / connection (150a, 150b, 150c), wireless devices and base stations / wireless devices, and base stations and base stations can transmit / receive wireless signals to each other. For example, wireless communication / connection (150a, 150b, 150c) can transmit / receive signals through various physical channels. To this end, at least some of various configuration information setting processes for transmitting / receiving wireless signals, various signal processing processes (e.g., channel encoding / decoding, modulation / demodulation, resource mapping / demapping, etc.), and resource allocation processes can be performed based on various proposals of the present invention.

[0374] Examples of wireless devices to which the present invention is applied

[0375] Figure 34 illustrates a wireless device applicable to the present invention.

[0376] Referring to FIG. 34, the first wireless device (100) and the second wireless device (200) can transmit and receive wireless signals via various wireless access technologies (e.g., LTE, NR). Here, {the first wireless device (100), the second wireless device (200)} can correspond to {the wireless device (100x), the base station (200)} and / or {the wireless device (100x), the wireless device (100x)} of FIG. 33.

[0377] A first wireless device (100) includes one or more processors (102) and one or more memories (104), and may further include one or more transceivers (106) and / or one or more antennas (108). The processor (102) controls the memories (104) and / or the transceivers (106), and may be configured to implement the descriptions, functions, procedures, proposals, methods, and / or operational flowcharts disclosed in this document. For example, the processor (102) may process information in the memory (104) to generate first information / signal, and then transmit a wireless signal including the first information / signal via the transceiver (106). In addition, the processor (102) may receive a wireless signal including second information / signal via the transceiver (106), and then store information obtained from signal processing of the second information / signal in the memory (104). The memory (104) may be connected to the processor (102) and may store various information related to the operation of the processor (102). For example, the memory (104) may perform some or all of the processes controlled by the processor (102), or may store software code including commands for performing the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in this document. Here, the processor (102) and the memory (104) may be part of a communication modem / circuit / chipset designed to implement wireless communication technology (e.g., LTE, NR). The transceiver (106) may be connected to the processor (102) and may transmit and / or receive wireless signals via one or more antennas (108). The transceiver (106) may include a transmitter and / or a receiver. The transceiver (106) may be used interchangeably with an RF (Radio Frequency) unit. In the present invention, a wireless device may also mean a communication modem / circuit / chipset.

[0378] Specifically, the first wireless device or terminal (100) may include a processor (102) and a memory (104) connected to a transceiver (106). The memory (104) may include at least one program capable of performing operations related to the embodiments described in FIGS. 19 to 32.

[0379] The processor (102) controls the transceiver (106) to transmit information about the predicted movement path of the UE to the first base station and receive a HO (handover) command targeting the second base station, and the HO command may include TA (Timing Advance) information and uplink resource information for the second base station reserved based on the predicted movement path.

[0380] Alternatively, a processing device may be configured that includes a processor (102) for controlling a terminal and a memory (104). In this case, the processing device may include at least one processor; and at least one memory that is connected to the at least one processor and stores instructions that perform operations when executed by the at least one processor. The operations include transmitting information about a predicted movement path of the UE to a first base station; and receiving a handover (HO) command targeting a second base station, wherein the HO command may include TA (Timing Advance) information and uplink resource information for the second base station that are reserved based on the predicted movement path.

[0381] The second wireless device (200) includes one or more processors (202), one or more memories (204), and may further include one or more transceivers (206) and / or one or more antennas (208). The processor (202) controls the memories (204) and / or the transceivers (206), and may be configured to implement the descriptions, functions, procedures, proposals, methods, and / or operational flowcharts disclosed in this document. For example, the processor (202) may process information in the memory (204) to generate third information / signals, and then transmit a wireless signal including the third information / signals via the transceivers (206). Furthermore, the processor (202) may receive a wireless signal including fourth information / signals via the transceivers (206), and then store information obtained from signal processing of the fourth information / signals in the memory (204). The memory (204) may be connected to the processor (202) and may store various information related to the operation of the processor (202). For example, the memory (204) may perform some or all of the processes controlled by the processor (202), or may store software code including commands for performing the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in this document. Here, the processor (202) and the memory (204) may be part of a communication modem / circuit / chip designed to implement wireless communication technology (e.g., LTE, NR). The transceiver (206) may be connected to the processor (202) and may transmit and / or receive wireless signals via one or more antennas (208). The transceiver (206) may include a transmitter and / or a receiver. The transceiver (206) may be used interchangeably with an RF unit. In the present invention, a wireless device may also mean a communication modem / circuit / chip.

[0382] Specifically, the second wireless device or base station (200) may include a processor (202) and a memory (204) connected to a transceiver or RF transceiver (206). The memory (204) may include at least one program capable of performing operations related to the embodiments described in FIGS. 19 to 32.

[0383] The processor (202) controls the transceiver (206) to receive information about a predicted movement path of the UE, and transmits a HO (handover) command targeting a second base station to the UE, wherein the HO command may include TA (Timing Advance) information and uplink resource information for the second base station reserved based on the predicted movement path.

[0384] Hereinafter, the hardware elements of the wireless device (100, 200) will be described in more detail. Although not limited thereto, one or more protocol layers may be implemented by one or more processors (102, 202). For example, one or more processors (102, 202) may implement one or more layers (e.g., functional layers such as PHY, MAC, RLC, PDCP, RRC, SDAP). One or more processors (102, 202) may generate one or more Protocol Data Units (PDUs) and / or one or more Service Data Units (SDUs) according to the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in this document. One or more processors (102, 202) may generate messages, control information, data, or information according to the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in this document. One or more processors (102, 202) can generate signals (e.g., baseband signals) including PDUs, SDUs, messages, control information, data or information according to the functions, procedures, proposals and / or methods disclosed herein, and provide the signals to one or more transceivers (106, 206). One or more processors (102, 202) can receive signals (e.g., baseband signals) from one or more transceivers (106, 206) and obtain PDUs, SDUs, messages, control information, data or information according to the descriptions, functions, procedures, proposals, methods and / or operational flowcharts disclosed herein.

[0385] One or more processors (102, 202) may be referred to as a controller, a microcontroller, a microprocessor, or a microcomputer. One or more processors (102, 202) may be implemented by hardware, firmware, software, or a combination thereof. For example, one or more Application Specific Integrated Circuits (ASICs), one or more Digital Signal Processors (DSPs), one or more Digital Signal Processing Devices (DSPDs), one or more Programmable Logic Devices (PLDs), or one or more Field Programmable Gate Arrays (FPGAs) may be included in one or more processors (102, 202). The descriptions, functions, procedures, proposals, methods, and / or operational flowcharts disclosed in this document may be implemented using firmware or software, and the firmware or software may be implemented to include modules, procedures, functions, etc. The descriptions, functions, procedures, suggestions, methods and / or operation flowcharts disclosed in this document may be implemented using firmware or software configured to perform one or more processors (102, 202) or stored in one or more memories (104, 204) and executed by one or more processors (102, 202). The descriptions, functions, procedures, suggestions, methods and / or operation flowcharts disclosed in this document may be implemented using firmware or software in the form of codes, instructions and / or sets of instructions.

[0386] One or more memories (104, 204) may be coupled to one or more processors (102, 202) and may store various forms of data, signals, messages, information, programs, codes, instructions, and / or commands. The one or more memories (104, 204) may be configured as ROM, RAM, EPROM, flash memory, hard drives, registers, cache memory, computer-readable storage media, and / or combinations thereof. The one or more memories (104, 204) may be located internally and / or externally to the one or more processors (102, 202). Additionally, the one or more memories (104, 204) may be coupled to the one or more processors (102, 202) via various technologies, such as wired or wireless connections.

[0387] One or more transceivers (106, 206) can transmit user data, control information, wireless signals / channels, etc., as mentioned in the methods and / or flowcharts of this document, to one or more other devices. One or more transceivers (106, 206) can receive user data, control information, wireless signals / channels, etc., as mentioned in the descriptions, functions, procedures, proposals, methods and / or flowcharts of this document, from one or more other devices. For example, one or more transceivers (106, 206) can be connected to one or more processors (102, 202) and can transmit and receive wireless signals. For example, one or more processors (102, 202) can control one or more transceivers (106, 206) to transmit user data, control information, or wireless signals to one or more other devices. Additionally, one or more processors (102, 202) may control one or more transceivers (106, 206) to receive user data, control information, or wireless signals from one or more other devices. Additionally, one or more transceivers (106, 206) may be coupled to one or more antennas (108, 208), and one or more transceivers (106, 206) may be configured to transmit and receive user data, control information, wireless signals / channels, or the like, as referred to in the descriptions, functions, procedures, proposals, methods, and / or operational flowcharts disclosed herein, via one or more antennas (108, 208). In this document, one or more antennas may be multiple physical antennas or multiple logical antennas (e.g., antenna ports). One or more transceivers (106, 206) can convert received user data, control information, wireless signals / channels, etc. from RF band signals to baseband signals in order to process the received user data, control information, wireless signals / channels, etc. using one or more processors (102, 202).One or more transceivers (106, 206) may convert user data, control information, wireless signals / channels, etc. processed by one or more processors (102, 202) from baseband signals to RF band signals. For this purpose, one or more transceivers (106, 206) may include an (analog) oscillator and / or filter.

[0388] Examples of wireless devices to which the present invention is applied

[0389] Figure 35 illustrates another example of a wireless device applicable to the present invention. The wireless device may be implemented in various forms depending on the use case / service (see Figure 33).

[0390] Referring to FIG. 35, the wireless device (100, 200) corresponds to the wireless device (100, 200) of FIG. 34 and may be composed of various elements, components, units, and / or modules. For example, the wireless device (100, 200) may include a communication unit (110), a control unit (120), a memory unit (130), and additional elements (140). The communication unit may include a communication circuit (112) and a transceiver(s) (114). For example, the communication circuit (112) may include one or more processors (102, 202) and / or one or more memories (104, 204) of FIG. 35. For example, the transceiver(s) (114) may include one or more transceivers (106, 206) and / or one or more antennas (108, 208) of FIG. 34. The control unit (120) is electrically connected to the communication unit (110), the memory unit (130), and the additional elements (140) and controls the overall operation of the wireless device. For example, the control unit (120) may control the electrical / mechanical operation of the wireless device based on the program / code / command / information stored in the memory unit (130). In addition, the control unit (120) may transmit information stored in the memory unit (130) to an external device (e.g., another communication device) via a wireless / wired interface through the communication unit (110), or store information received from an external device (e.g., another communication device) via a wireless / wired interface in the memory unit (130).

[0391] The additional element (140) may be configured in various ways depending on the type of the wireless device. For example, the additional element (140) may include at least one of a power unit / battery, an input / output unit (I / O unit), a driving unit, and a computing unit. Although not limited thereto, the wireless device may be implemented in the form of a robot (Fig. 33, 100a), a vehicle (Fig. 33, 100b-1, 100b-2), an XR device (Fig. 33, 100c), a portable device (Fig. 33, 100d), a home appliance (Fig. 33, 100e), an IoT device (Fig. 33, 100f), a digital broadcasting terminal, a hologram device, a public safety device, an MTC device, a medical device, a fintech device (or a financial device), a security device, a climate / environmental device, an AI server / device (Fig. 33, 400), a base station (Fig. 33, 200), a network node, etc. Wireless devices may be mobile or stationary depending on the use / service.

[0392] In FIG. 35, various elements, components, units / parts, and / or modules within the wireless device (100, 200) may be entirely interconnected via a wired interface, or at least some may be wirelessly connected via a communication unit (110). For example, within the wireless device (100, 200), the control unit (120) and the communication unit (110) may be wired, and the control unit (120) and a first unit (e.g., 130, 140) may be wirelessly connected via the communication unit (110). In addition, each element, component, unit / part, and / or module within the wireless device (100, 200) may further include one or more elements. For example, the control unit (120) may be composed of a set of one or more processors. For example, the control unit (120) may be composed of a set of a communication control processor, an application processor, an electronic control unit (ECU), a graphics processing processor, a memory control processor, etc. As another example, the memory unit (130) may be composed of RAM (Random Access Memory), DRAM (Dynamic RAM), ROM (Read Only Memory), flash memory, volatile memory, non-volatile memory, and / or a combination thereof.

[0393] Examples of vehicles or autonomous vehicles to which the present invention is applied

[0394] Figure 36 illustrates a vehicle or autonomous vehicle applicable to the present invention. The vehicle or autonomous vehicle may be implemented as a mobile robot, car, train, manned / unmanned aerial vehicle (AV), ship, etc.

[0395] Referring to FIG. 36, a vehicle or autonomous vehicle (100) may include an antenna unit (108), a communication unit (110), a control unit (120), a driving unit (140a), a power supply unit (140b), a sensor unit (140c), and an autonomous driving unit (140d). The antenna unit (108) may be configured as a part of the communication unit (110). Blocks 110 / 130 / 140a to 140d correspond to blocks 110 / 130 / 140 of FIG. 35, respectively.

[0396] The communication unit (110) can transmit and receive signals (e.g., data, control signals, etc.) with external devices such as other vehicles, base stations (e.g., base stations, road side units, etc.), and servers. The control unit (120) can control elements of the vehicle or autonomous vehicle (100) to perform various operations. The control unit (120) can include an ECU (Electronic Control Unit). The drive unit (140a) can drive the vehicle or autonomous vehicle (100) on the ground. The drive unit (140a) can include an engine, a motor, a power train, wheels, brakes, a steering device, etc. The power supply unit (140b) supplies power to the vehicle or autonomous vehicle (100) and can include a wired / wireless charging circuit, a battery, etc. The sensor unit (140c) can obtain vehicle status, surrounding environment information, user information, etc. The sensor unit (140c) may include an IMU (inertial measurement unit) sensor, a collision sensor, a wheel sensor, a speed sensor, an incline sensor, a weight detection sensor, a heading sensor, a position module, a vehicle forward / backward sensor, a battery sensor, a fuel sensor, a tire sensor, a steering sensor, a temperature sensor, a humidity sensor, an ultrasonic sensor, an illuminance sensor, a pedal position sensor, etc. The autonomous driving unit (140d) may implement a technology for maintaining a driving lane, a technology for automatically controlling speed such as adaptive cruise control, a technology for automatically driving along a set path, a technology for automatically setting a path and driving when a destination is set, etc.

[0397] For example, the communication unit (110) can receive map data, traffic information data, etc. from an external server. The autonomous driving unit (140d) can generate an autonomous driving route and driving plan based on the acquired data. The control unit (120) can control the drive unit (140a) so that the vehicle or autonomous vehicle (100) moves along the autonomous driving route according to the driving plan (e.g., speed / direction control). During autonomous driving, the communication unit (110) can irregularly / periodically acquire the latest traffic information data from an external server and can acquire surrounding traffic information data from surrounding vehicles. In addition, during autonomous driving, the sensor unit (140c) can acquire vehicle status and surrounding environment information. The autonomous driving unit (140d) can update the autonomous driving route and driving plan based on newly acquired data / information. The communication unit (110) can transmit information regarding the vehicle location, autonomous driving route, driving plan, etc. to the external server. External servers can predict traffic information data in advance using AI technology or other technologies based on information collected from vehicles or autonomous vehicles, and provide the predicted traffic information data to the vehicles or autonomous vehicles.

[0398] Here, the wireless communication technology implemented in the wireless device (XXX, YYY) of the present specification may include not only LTE, NR, and 6G, but also Narrowband Internet of Things for low-power communication. At this time, for example, NB-IoT technology may be an example of LPWAN (Low Power Wide Area Network) technology, and may be implemented with standards such as LTE Cat NB1 and / or LTE Cat NB2, and is not limited to the above-described names. Additionally or alternatively, the wireless communication technology implemented in the wireless device (XXX, YYY) of the present specification may perform communication based on LTE-M technology. At this time, for example, LTE-M technology may be an example of LPWAN technology, and may be called by various names such as eMTC (enhanced Machine Type Communication). For example, LTE-M technology can be implemented by at least one of various standards such as 1) LTE CAT 0, 2) LTE Cat M1, 3) LTE Cat M2, 4) LTE non-BL (non-Bandwidth Limited), 5) LTE-MTC, 6) LTE Machine Type Communication, and / or 7) LTE M, and is not limited to the above-described names. Additionally or alternatively, the wireless communication technology implemented in the wireless device (XXX, YYY) of the present specification can include at least one of ZigBee, Bluetooth, and Low Power Wide Area Network (LPWAN) considering low-power communication, and is not limited to the above-described names. For example, ZigBee technology can create PAN (personal area networks) related to small / low-power digital communication based on various standards such as IEEE 802.15.4, and can be called by various names.

[0399] The embodiments described above are combinations of components and features of the present invention in a predetermined form. Each component or feature should be considered optional unless explicitly stated otherwise. Each component or feature may be implemented without being combined with other components or features. Furthermore, it is also possible to form an embodiment of the present invention by combining some components and / or features. The order of operations described in the embodiments of the present invention may be changed. Some components or features of one embodiment may be included in another embodiment or may be replaced with corresponding components or features of another embodiment. It is self-evident that claims that do not have an explicit citation relationship in the patent claims may be combined to form an embodiment or may be incorporated as a new claim through a post-application amendment.

[0400] In this document, embodiments of the present invention have been described primarily focusing on the signal transmission and reception relationship between a terminal and a base station. This transmission and reception relationship is equally / similarly extended to signal transmission and reception between a terminal and a relay or a base station and a relay. Certain operations described as being performed by a base station in this document may, in some cases, be performed by its upper node. That is, it is obvious that various operations performed for communication with a terminal in a network composed of multiple network nodes including a base station may be performed by the base station or other network nodes other than the base station. The base station may be replaced by terms such as fixed station, Node B, eNode B (eNB), and access point. In addition, the terminal may be replaced by terms such as UE (User Equipment), MS (Mobile Station), MSS (Mobile Subscriber Station).

[0401] Embodiments of the present invention may be implemented by various means, for example, hardware, firmware, software, or a combination thereof. In the case of hardware implementation, an embodiment of the present invention may be implemented by one or more ASICs (application specific integrated circuits), DSPs (digital signal processors), DSPDs (digital signal processing devices), PLDs (programmable logic devices), FPGAs (field programmable gate arrays), processors, controllers, microcontrollers, microprocessors, etc.

[0402] When implemented via firmware or software, an embodiment of the present invention may be implemented in the form of modules, procedures, functions, etc. that perform the functions or operations described above. The software code may be stored in a memory unit and executed by a processor. The memory unit may be located within or outside the processor and may exchange data with the processor via various known means.

[0403] It will be apparent to those skilled in the art that the present invention can be embodied in other specific forms without departing from the scope of the invention. Therefore, the above detailed description should not be construed as limiting in any respect, but rather as illustrative. The scope of the present invention should be determined by a reasonable interpretation of the appended claims, and all modifications within the scope of equivalents of the present invention are intended to be included within the scope of the present invention.

[0404] The embodiments of the present invention as described above can be applied to various mobile communication systems.

Claims

1. In the method by UE (user equipment), A step of transmitting information about the predicted movement path of the UE to the first base station; and A step of receiving a HO (handover) command targeting a second base station; A method wherein the HO command includes TA (Timing Advance) information and uplink resource information for the second base station reserved based on the predicted movement path.

2. In paragraph 1, A method, characterized in that the HO command further includes information about a specific area and a specific time period in which the TA information and the uplink resource information are valid.

3. In paragraph 2, A method characterized in that, based on the UE operating within the specific time interval being located in the specific area, the UE transmits an initial message for performing a HO procedure to the second base station based on the TA information and the uplink resource information.

4. In paragraph 3, A method characterized in that the above HO procedure is performed without performing a RACH (Random Access Channel) procedure for the second base station.

5. In paragraph 3, A method, characterized in that the initial message is an RRCReconfigurationComplete message for completion of the HO procedure.

6. In paragraph 1, A method, characterized in that the above TA information includes a plurality of candidate TA values ​​corresponding to a plurality of locations.

7. In paragraph 1, A method, characterized in that the above HO command is determined based on the above predicted movement path.

8. In paragraph 2, A method, characterized in that the HO command further includes the TA information and the uplink resource information reserved for each of the plurality of candidate target base stations, based on the HO command including information about a plurality of candidate target base stations.

9. In paragraph 1, A method, characterized in that the UE is related to an Unmanned Aerial Vehicle (UAV), and the predicted movement path is a flight path of the UAV.

10. In at least one non-transitory computer-readable medium, Contains instructions that perform operations when executed by at least one processor, The above actions are, Transmitting information about the predicted movement path of the UE to the first base station; and Including receiving a HO (handover) command targeting a second base station, At least one non-transitory computer-readable medium recording medium, wherein the HO command includes TA (Timing Advance) information and uplink resource information for the second base station reserved based on the predicted movement path.

11. In UE (user equipment), RF (Radio Frequency) transmitter and receiver; and A processor connected to the RF transceiver, The processor controls the RF transceiver to transmit information about the predicted movement path of the UE to a first base station and receives a HO (handover) command targeting a second base station, The above HO command includes TA (Timing Advance) information and uplink resource information for the second base station reserved based on the predicted movement path, UE.

12. In a processing device that controls UE (user equipment), at least one processor; and At least one memory connected to said at least one processor and storing instructions that perform operations when executed by said at least one processor, The above actions are, Transmitting information about the predicted movement path of the UE to the first base station; and Including receiving a HO (handover) command targeting a second base station, A processing device, wherein the HO command includes TA (Timing Advance) information and uplink resource information for the second base station reserved based on the predicted movement path.

13. In the method by the first base station, A step of receiving information on a predicted movement path of a UE (user equipment); and A step of transmitting a HO (handover) command targeting a second base station to the UE; A method wherein the HO command includes TA (Timing Advance) information and uplink resource information for the second base station reserved based on the predicted movement path.

14. In paragraph 13, A step of transmitting a HO request message including information about the predicted movement path to the second base station: and A method further comprising: receiving a message including the TA information and the uplink resource information determined based on the predicted movement path from the second base station.

15. At the first base station, RF (Radio Frequency) transmitter and receiver; and A processor connected to the RF transceiver, The processor controls the RF transceiver to receive information on a predicted movement path of a UE (user equipment), and transmits a HO (handover) command targeting a second base station to the UE. A first base station, wherein the HO command includes TA (Timing Advance) information and uplink resource information for the second base station reserved based on the predicted movement path.

Images