Method and apparatus for flight path information in a wireless communication system

Abstract

A method and apparatus for flight path information in a wireless communication system is provided. A wireless device acquires information related to at least one specific zone in which the wireless device is not allowed to perform transmission. A wireless device identifies a flight path of the wireless device; and transmitting the information related to the flight path. The information related to the flight path includes information related to whether the flight path passes the at least one specific zone.

Description

METHOD AND APPARATUS FOR FLIGHT PATH INFORMATION IN A WIRELESS COMMUNICATION SYSTEM

[0001] The present disclosure relates to a method and apparatus for flight path information in a wireless communication system.

[0002] 3rd generation partnership project (3GPP) long-term evolution (LTE) is a technology for enabling high-speed packet communications. Many schemes have been proposed for the LTE objective including those that aim to reduce user and provider costs, improve service quality, and expand and improve coverage and system capacity. The 3GPP LTE requires reduced cost per bit, increased service availability, flexible use of a frequency band, a simple structure, an open interface, and adequate power consumption of a terminal as an upper-level requirement.

[0003] Work has started in international telecommunication union (ITU) and 3GPP to develop requirements and specifications for new radio (NR) systems. 3GPP has to identify and develop the technology components needed for successfully standardizing the new RAT timely satisfying both the urgent market needs, and the more long-term requirements set forth by the ITU radio communication sector (ITU-R) international mobile telecommunications (IMT)-2020 process. Further, the NR should be able to use any spectrum band ranging at least up to 100 GHz that may be made available for wireless communications even in a more distant future.

[0004] The NR targets a single technical framework addressing all usage scenarios, requirements and deployment scenarios including enhanced mobile broadband (eMBB), massive machine-type-communications (mMTC), ultra-reliable and low latency communications (URLLC), etc. The NR shall be inherently forward compatible.

[0005] As per the Electronic Communications Committee (ECC) requirement, with the harmonized technical conditions for mobile / fixed communication networks (MFCN) bands and for spectrum compatibility purpose, there is some spectrum operational restrictions. This can be done using "no-transmit zones (NTZ)", which is defined at a geographical area where aerial UE are not allowed to operate in a certain frequency band. This restriction can be applied to LTE and 5G NR in the following MFCN harmonised bands: 703-733 MHz, 832-862 MHz, 880-915 MHz, 1710-1785 MHz, 1920-1980 MHz, 2500-2570 MHz and 2570-2620 MHz.

[0006] In order to decide on appropriate mobility configuration, and to provide early resource reservation in cells suitable for a handover, the network can utilize the flight path information received from UE. UE can indicate that a flight path is available or updated, and it can send that information with up to 20 waypoints in the flight path information.

[0007] If the network knows the no-transmit zones, it can configure the UE with the suitable configuration, e.g., removal NTZ frequency related configuration when the UE enters NTZ area and re-configuration of NTZ frequency related when the UE leaves NTZ area. However, it is difficult to properly configure the UE without accurate entry and exit information for NTZ zones. In particular, when entering the NTZ area, if the network does not release the operation related to the NTZ frequency, the UE may transmit control / user data through the NTZ frequency in the NTZ area, thereby violating the ECC requirement.

[0008] Therefore, studies for flight path information in a wireless communication system are required.

[0009] In an aspect, a method performed by a wireless device in a wireless communication system is provided. The method comprises: acquiring information related to at least one specific zone in which the wireless device is not allowed to perform transmission; identifying a flight path of the wireless device; and transmitting the information related to the flight path, wherein the information related to the flight path includes information related to whether the flight path passes the at least one specific zone.

[0010] In another aspect, an apparatus for implementing the above method is provided.

[0011] The present disclosure can have various advantageous effects.

[0012] According to some embodiments of the present disclosure, a wireless device could efficiently provide flight path information related to the NTZ in a wireless communication system.

[0013] For example, by including additional information with location / time related to the specific area in the flight path information, the network can proactively configure the UE with appropriate configuration considering the characteristic of the specific area. In particular, when the UE is planned to go into a no-transmit zone, the network can disallow mobility related to the NTZ frequency in advance. The network can utilize the additional information in T1 / D1 condition configuration as well.

[0014] In other words, the wireless device can include information related to whether the flight path passes through the NTZ in the flight path information. Therefore, the network can efficiently configure the wireless device.

[0015] According to some embodiments of the present disclosure, the wireless communication system could provide an efficient solution for flight path information about entering and exiting a specific area.

[0016] Advantageous effects which can be obtained through specific embodiments of the present disclosure are not limited to the advantageous effects listed above. For example, there may be a variety of technical effects that a person having ordinary skill in the related art can understand and / or derive from the present disclosure. Accordingly, the specific effects of the present disclosure are not limited to those explicitly described herein, but may include various effects that may be understood or derived from the technical features of the present disclosure.

[0017] FIG. 1 shows an example of a communication system to which implementations of the present disclosure is applied.

[0018] FIG. 2 shows an example of wireless devices to which implementations of the present disclosure is applied.

[0019] FIG. 3 shows an example of a wireless device to which implementations of the present disclosure is applied.

[0020] FIG. 4 shows another example of wireless devices to which implementations of the present disclosure is applied.

[0021] FIG. 5 shows an example of UE to which implementations of the present disclosure is applied.

[0022] FIGS. 6 and 7 show an example of protocol stacks in a 3GPP based wireless communication system to which implementations of the present disclosure is applied.

[0023] FIG. 8 shows a frame structure in a 3GPP based wireless communication system to which implementations of the present disclosure is applied.

[0024] FIG. 9 shows a data flow example in the 3GPP NR system to which implementations of the present disclosure is applied.

[0025] FIG. 10 shows an example of measurement reporting.

[0026] FIG. 11 shows an example of Location measurement indication

[0027] FIG. 12 shows an example of RRC reconfiguration, successful.

[0028] FIG. 13 shows an example of UE information procedure.

[0029] FIG. 14 shows an example of a method for flight path information in a wireless communication system.

[0030] FIG. 15 shows an example of a method related to flight path information about entering and exiting a specific area.

[0031] FIG. 16 shows an example of a method related to flight path information including information about entering and exiting a specific area.

[0032] The following techniques, apparatuses, and systems may be applied to a variety of wireless multiple access systems. Examples of the multiple access systems include a code division multiple access (CDMA) system, a frequency division multiple access (FDMA) system, a time division multiple access (TDMA) system, an orthogonal frequency division multiple access (OFDMA) system, a single carrier frequency division multiple access (SC-FDMA) system, and a multicarrier frequency division multiple access (MC-FDMA) system. CDMA may be embodied through radio technology such as universal terrestrial radio access (UTRA) or CDMA2000. TDMA may be embodied through radio technology such as global system for mobile communications (GSM), general packet radio service (GPRS), or enhanced data rates for GSM evolution (EDGE). OFDMA may be embodied through radio technology such as institute of electrical and electronics engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, or evolved UTRA (E-UTRA). UTRA is a part of a universal mobile telecommunications system (UMTS). 3rd generation partnership project (3GPP) long term evolution (LTE) is a part of evolved UMTS (E-UMTS) using E-UTRA. 3GPP LTE employs OFDMA in DL and SC-FDMA in UL. LTE-advanced (LTE-A) is an evolved version of 3GPP LTE.

[0033] For convenience of description, implementations of the present disclosure are mainly described in regards to a 3GPP based wireless communication system. However, the technical features of the present disclosure are not limited thereto. For example, although the following detailed description is given based on a mobile communication system corresponding to a 3GPP based wireless communication system, aspects of the present disclosure that are not limited to 3GPP based wireless communication system are applicable to other mobile communication systems.

[0034] For terms and technologies which are not specifically described among the terms of and technologies employed in the present disclosure, the wireless communication standard documents published before the present disclosure may be referenced.

[0035] In the present disclosure, "A or B" may mean "only A", "only B", or "both A and B". In other words, "A or B" in the present disclosure may be interpreted as "A and / or B". For example, "A, B or C" in the present disclosure may mean "only A", "only B", "only C", or "any combination of A, B and C".

[0036] In the present disclosure, slash ( / ) or comma (,) may mean "and / or". For example, "A / B" may mean "A and / or B". Accordingly, "A / B" may mean "only A", "only B", or "both A and B". For example, "A, B, C" may mean "A, B or C".

[0037] In the present disclosure, "at least one of A and B" may mean "only A", "only B" or "both A and B". In addition, the expression "at least one of A or B" or "at least one of A and / or B" in the present disclosure may be interpreted as same as "at least one of A and B".

[0038] In addition, in the present disclosure, "at least one of A, B and C" may mean "only A", "only B", "only C", or "any combination of A, B and C". In addition, "at least one of A, B or C" or "at least one of A, B and / or C" may mean "at least one of A, B and C".

[0039] Also, parentheses used in the present disclosure may mean "for example". In detail, when it is shown as "control information (PDCCH)", "PDCCH" may be proposed as an example of "control information". In other words, "control information" in the present disclosure is not limited to "PDCCH", and "PDCCH" may be proposed as an example of "control information". In addition, even when shown as "control information (i.e., PDCCH)", "PDCCH" may be proposed as an example of "control information".

[0040] Technical features that are separately described in one drawing in the present disclosure may be implemented separately or simultaneously.

[0041] Although not limited thereto, various descriptions, functions, procedures, suggestions, methods and / or operational flowcharts of the present disclosure disclosed herein can be applied to various fields requiring wireless communication and / or connection (e.g., 5G) between devices.

[0042] Hereinafter, the present disclosure will be described in more detail with reference to drawings. The same reference numerals in the following drawings and / or descriptions may refer to the same and / or corresponding hardware blocks, software blocks, and / or functional blocks unless otherwise indicated.

[0043] FIG. 1 shows an example of a communication system to which implementations of the present disclosure is applied.

[0044] The 5G usage scenarios shown in FIG. 1 are only exemplary, and the technical features of the present disclosure can be applied to other 5G usage scenarios which are not shown in FIG. 1.

[0045] Three main requirement categories for 5G include (1) a category of enhanced mobile broadband (eMBB), (2) a category of massive machine type communication (mMTC), and (3) a category of ultra-reliable and low latency communications (URLLC).

[0046] Partial use cases may require a plurality of categories for optimization and other use cases may focus only upon one key performance indicator (KPI). 5G supports such various use cases using a flexible and reliable method.

[0047] eMBB far surpasses basic mobile Internet access and covers abundant bidirectional work and media and entertainment applications in cloud and augmented reality. Data is one of 5G core motive forces and, in a 5G era, a dedicated voice service may not be provided for the first time. In 5G, it is expected that voice will be simply processed as an application program using data connection provided by a communication system. Main causes for increased traffic volume are due to an increase in the size of content and an increase in the number of applications requiring high data transmission rate. A streaming service (of audio and video), conversational video, and mobile Internet access will be more widely used as more devices are connected to the Internet. These many application programs require connectivity of an always turned-on state in order to push real-time information and alarm for users. Cloud storage and applications are rapidly increasing in a mobile communication platform and may be applied to both work and entertainment. The cloud storage is a special use case which accelerates growth of uplink data transmission rate. 5G is also used for remote work of cloud. When a tactile interface is used, 5G demands much lower end-to-end latency to maintain user good experience. Entertainment, for example, cloud gaming and video streaming, is another core element which increases demand for mobile broadband capability. Entertainment is essential for a smartphone and a tablet in any place including high mobility environments such as a train, a vehicle, and an airplane. Other use cases are augmented reality for entertainment and information search. In this case, the augmented reality requires very low latency and instantaneous data volume.

[0048] In addition, one of the most expected 5G use cases relates a function capable of smoothly connecting embedded sensors in all fields, i.e., mMTC. It is expected that the number of potential Internet-of-things (IoT) devices will reach 204 hundred million up to the year of 2020. An industrial IoT is one of categories of performing a main role enabling a smart city, asset tracking, smart utility, agriculture, and security infrastructure through 5G.

[0049] URLLC includes a new service that will change industry through remote control of main infrastructure and an ultra-reliable / available low-latency link such as a self-driving vehicle. A level of reliability and latency is essential to control a smart grid, automatize industry, achieve robotics, and control and adjust a drone.

[0050] 5G is a means of providing streaming evaluated as a few hundred megabits per second to gigabits per second and may complement fiber-to-the-home (FTTH) and cable-based broadband (or DOCSIS). Such fast speed is needed to deliver TV in resolution of 4K or more (6K, 8K, and more), as well as virtual reality and augmented reality. Virtual reality (VR) and augmented reality (AR) applications include almost immersive sports games. A specific application program may require a special network configuration. For example, for VR games, gaming companies need to incorporate a core server into an edge network server of a network operator in order to minimize latency.

[0051] Automotive is expected to be a new important motivated force in 5G together with many use cases for mobile communication for vehicles. For example, entertainment for passengers requires high simultaneous capacity and mobile broadband with high mobility. This is because future users continue to expect connection of high quality regardless of their locations and speeds. Another use case of an automotive field is an AR dashboard. The AR dashboard causes a driver to identify an object in the dark in addition to an object seen from a front window and displays a distance from the object and a movement of the object by overlapping information talking to the driver. In the future, a wireless module enables communication between vehicles, information exchange between a vehicle and supporting infrastructure, and information exchange between a vehicle and other connected devices (e.g., devices accompanied by a pedestrian). A safety system guides alternative courses of a behavior so that a driver may drive more safely drive, thereby lowering the danger of an accident. The next stage will be a remotely controlled or self-driven vehicle. This requires very high reliability and very fast communication between different self-driven vehicles and between a vehicle and infrastructure. In the future, a self-driven vehicle will perform all driving activities and a driver will focus only upon abnormal traffic that the vehicle cannot identify. Technical requirements of a self-driven vehicle demand ultra-low latency and ultra-high reliability so that traffic safety is increased to a level that cannot be achieved by human being.

[0052] A smart city and a smart home / building mentioned as a smart society will be embedded in a high-density wireless sensor network. A distributed network of an intelligent sensor will identify conditions for costs and energy-efficient maintenance of a city or a home. Similar configurations may be performed for respective households. All of temperature sensors, window and heating controllers, burglar alarms, and home appliances are wirelessly connected. Many of these sensors are typically low in data transmission rate, power, and cost. However, real-time HD video may be demanded by a specific type of device to perform monitoring.

[0053] Consumption and distribution of energy including heat or gas is distributed at a higher level so that automated control of the distribution sensor network is demanded. The smart grid collects information and connects the sensors to each other using digital information and communication technology so as to act according to the collected information. Since this information may include behaviors of a supply company and a consumer, the smart grid may improve distribution of fuels such as electricity by a method having efficiency, reliability, economic feasibility, production sustainability, and automation. The smart grid may also be regarded as another sensor network having low latency.

[0054] Mission critical application (e.g., e-health) is one of 5G use scenarios. A health part contains many application programs capable of enjoying benefit of mobile communication. A communication system may support remote treatment that provides clinical treatment in a faraway place. Remote treatment may aid in reducing a barrier against distance and improve access to medical services that cannot be continuously available in a faraway rural area. Remote treatment is also used to perform important treatment and save lives in an emergency situation. The wireless sensor network based on mobile communication may provide remote monitoring and sensors for parameters such as heart rate and blood pressure.

[0055] Wireless and mobile communication gradually becomes important in the field of an industrial application. Wiring is high in installation and maintenance cost. Therefore, a possibility of replacing a cable with reconstructible wireless links is an attractive opportunity in many industrial fields. However, in order to achieve this replacement, it is necessary for wireless connection to be established with latency, reliability, and capacity similar to those of the cable and management of wireless connection needs to be simplified. Low latency and a very low error probability are new requirements when connection to 5G is needed.

[0056] Logistics and freight tracking are important use cases for mobile communication that enables inventory and package tracking anywhere using a location-based information system. The use cases of logistics and freight typically demand low data rate but require location information with a wide range and reliability.

[0057] Referring to FIG. 1, the communication system 1 includes wireless devices 100a to 100f, base stations (BSs) 200, and a network 300. Although FIG. 1 illustrates a 5G network as an example of the network of the communication system 1, the implementations of the present disclosure are not limited to the 5G system, and can be applied to the future communication system beyond the 5G system.

[0058] The BSs 200 and the network 300 may be implemented as wireless devices and a specific wireless device may operate as a BS / network node with respect to other wireless devices.

[0059] The wireless devices 100a to 100f represent devices performing communication using radio access technology (RAT) (e.g., 5G new RAT (NR)) or LTE) and may be referred to as communication / radio / 5G devices. The wireless devices 100a to 100f may include, without being limited to, a robot 100a, vehicles 100b-1 and 100b-2, an extended reality (XR) device 100c, a hand-held device 100d, a home appliance 100e, an IoT device 100f, and an artificial intelligence (AI) device / server 400. For example, the vehicles may include a vehicle having a wireless communication function, an autonomous driving vehicle, and a vehicle capable of performing communication between vehicles. The vehicles may include an unmanned aerial vehicle (UAV) (e.g., a drone). The XR device may include an AR / VR / Mixed Reality (MR) device and may be implemented in the form of a head-mounted device (HMD), a head-up display (HUD) mounted in a vehicle, a television, a smartphone, a computer, a wearable device, a home appliance device, a digital signage, a vehicle, a robot, etc. The hand-held device may include a smartphone, a smartpad, a wearable device (e.g., a smartwatch or a smartglasses), and a computer (e.g., a notebook). The home appliance may include a TV, a refrigerator, and a washing machine. The IoT device may include a sensor and a smartmeter.

[0060] In the present disclosure, the wireless devices 100a to 100f may be called user equipments (UEs). A UE may include, for example, a cellular phone, a smartphone, a laptop computer, a digital broadcast terminal, a personal digital assistant (PDA), a portable multimedia player (PMP), a navigation system, a slate personal computer (PC), a tablet PC, an ultrabook, a vehicle, a vehicle having an autonomous traveling function, a connected car, an UAV, an AI module, a robot, an AR device, a VR device, an MR device, a hologram device, a public safety device, an MTC device, an IoT device, a medical device, a FinTech device (or a financial device), a security device, a weather / environment device, a device related to a 5G service, or a device related to a fourth industrial revolution field.

[0061] The UAV may be, for example, an aircraft aviated by a wireless control signal without a human being onboard.

[0062] The VR device may include, for example, a device for implementing an object or a background of the virtual world. The AR device may include, for example, a device implemented by connecting an object or a background of the virtual world to an object or a background of the real world. The MR device may include, for example, a device implemented by merging an object or a background of the virtual world into an object or a background of the real world. The hologram device may include, for example, a device for implementing a stereoscopic image of 360 degrees by recording and reproducing stereoscopic information, using an interference phenomenon of light generated when two laser lights called holography meet.

[0063] The public safety device may include, for example, an image relay device or an image device that is wearable on the body of a user.

[0064] The MTC device and the IoT device may be, for example, devices that do not require direct human intervention or manipulation. For example, the MTC device and the IoT device may include smartmeters, vending machines, thermometers, smartbulbs, door locks, or various sensors.

[0065] The medical device may be, for example, a device used for the purpose of diagnosing, treating, relieving, curing, or preventing disease. For example, the medical device may be a device used for the purpose of diagnosing, treating, relieving, or correcting injury or impairment. For example, the medical device may be a device used for the purpose of inspecting, replacing, or modifying a structure or a function. For example, the medical device may be a device used for the purpose of adjusting pregnancy. For example, the medical device may include a device for treatment, a device for operation, a device for (in vitro) diagnosis, a hearing aid, or a device for procedure.

[0066] The security device may be, for example, a device installed to prevent a danger that may arise and to maintain safety. For example, the security device may be a camera, a closed-circuit TV (CCTV), a recorder, or a black box.

[0067] The FinTech device may be, for example, a device capable of providing a financial service such as mobile payment. For example, the FinTech device may include a payment device or a point of sales (POS) system.

[0068] The weather / environment device may include, for example, a device for monitoring or predicting a weather / environment.

[0069] The wireless devices 100a to 100f may be connected to the network 300 via the BSs 200. An AI technology may be applied to the wireless devices 100a to 100f and the wireless devices 100a to 100f may be connected to the AI server 400 via the network 300. The network 300 may be configured using a 3G network, a 4G (e.g., LTE) network, a 5G (e.g., NR) network, and a beyond-5G network. Although the wireless devices 100a to 100f may communicate with each other through the BSs 200 / network 300, the wireless devices 100a to 100f may perform direct communication (e.g., sidelink communication) with each other without passing through the BSs 200 / network 300. For example, the vehicles 100b-1 and 100b-2 may perform direct communication (e.g., vehicle-to-vehicle (V2V) / vehicle-to-everything (V2X) communication). The IoT device (e.g., a sensor) may perform direct communication with other IoT devices (e.g., sensors) or other wireless devices 100a to 100f.

[0070] Wireless communication / connections 150a, 150b and 150c may be established between the wireless devices 100a to 100f and / or between wireless device 100a to 100f and BS 200 and / or between BSs 200. Herein, the wireless communication / connections may be established through various RATs (e.g., 5G NR) such as uplink / downlink communication 150a, sidelink communication (or device-to-device (D2D) communication) 150b, inter-base station communication 150c (e.g., relay, integrated access and backhaul (IAB)), etc. The wireless devices 100a to 100f and the BSs 200 / the wireless devices 100a to 100f may transmit / receive radio signals to / from each other through the wireless communication / connections 150a, 150b and 150c. For example, the wireless communication / connections 150a, 150b and 150c may transmit / receive signals through various physical channels. To this end, at least a part of various configuration information configuring processes, various signal processing processes (e.g., channel encoding / decoding, modulation / demodulation, and resource mapping / de-mapping), and resource allocating processes, for transmitting / receiving radio signals, may be performed based on the various proposals of the present disclosure.

[0071] Here, the radio communication technologies implemented in the wireless devices in the present disclosure may include narrowband internet-of-things (NB-IoT) technology for low-power communication as well as LTE, NR and 6G. For example, NB-IoT technology may be an example of low power wide area network (LPWAN) technology, may be implemented in specifications such as LTE Cat NB1 and / or LTE Cat NB2, and may not be limited to the above-mentioned names. Additionally and / or alternatively, the radio communication technologies implemented in the wireless devices in the present disclosure may communicate based on LTE-M technology. For example, LTE-M technology may be an example of LPWAN technology and be called by various names such as enhanced machine type communication (eMTC). For example, LTE-M technology may be implemented in at least one of the various specifications, such as 1) LTE Cat 0, 2) LTE Cat M1, 3) LTE Cat M2, 4) LTE non-bandwidth limited (non-BL), 5) LTE-MTC, 6) LTE Machine Type Communication, and / or 7) LTE M, and may not be limited to the above-mentioned names. Additionally and / or alternatively, the radio communication technologies implemented in the wireless devices in the present disclosure may include at least one of ZigBee, Bluetooth, and / or LPWAN which take into account low-power communication, and may not be limited to the above-mentioned names. For example, ZigBee technology may generate personal area networks (PANs) associated with small / low-power digital communication based on various specifications such as IEEE 802.15.4 and may be called various names.

[0072] FIG. 2 shows an example of wireless devices to which implementations of the present disclosure is applied.

[0073] Referring to FIG. 2, a first wireless device 100 and a second wireless device 200 may transmit / receive radio signals to / from an external device through a variety of RATs (e.g., LTE and NR). In FIG. 2, {the first wireless device 100 and the second wireless device 200} may correspond to at least one of {the wireless device 100a to 100f and the BS 200}, {the wireless device 100a to 100f and the wireless device 100a to 100f} and / or {the BS 200 and the BS 200} of FIG. 1.

[0074] The first wireless device 100 may include one or more processors 102 and one or more memories 104 and additionally further include one or more transceivers 106 and / or one or more antennas 108. The processor(s) 102 may control the memory(s) 104 and / or the transceiver(s) 106 and may be configured to implement the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts described in the present disclosure. For example, the processor(s) 102 may process information within the memory(s) 104 to generate first information / signals and then transmit radio signals including the first information / signals through the transceiver(s) 106. The processor(s) 102 may receive radio signals including second information / signals through the transceiver(s) 106 and then store information obtained by processing the second information / signals in the memory(s) 104. The memory(s) 104 may be connected to the processor(s) 102 and may store a variety of information related to operations of the processor(s) 102. For example, the memory(s) 104 may store software code including commands for performing a part or the entirety of processes controlled by the processor(s) 102 or for performing the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts described in the present disclosure. Herein, the processor(s) 102 and the memory(s) 104 may be a part of a communication modem / circuit / chip designed to implement RAT (e.g., LTE or NR). The transceiver(s) 106 may be connected to the processor(s) 102 and transmit and / or receive radio signals through one or more antennas 108. Each of the transceiver(s) 106 may include a transmitter and / or a receiver. The transceiver(s) 106 may be interchangeably used with radio frequency (RF) unit(s). In the present disclosure, the first wireless device 100 may represent a communication modem / circuit / chip.

[0075] The second wireless device 200 may include one or more processors 202 and one or more memories 204 and additionally further include one or more transceivers 206 and / or one or more antennas 208. The processor(s) 202 may control the memory(s) 204 and / or the transceiver(s) 206 and may be configured to implement the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts described in the present disclosure. For example, the processor(s) 202 may process information within the memory(s) 204 to generate third information / signals and then transmit radio signals including the third information / signals through the transceiver(s) 206. The processor(s) 202 may receive radio signals including fourth information / signals through the transceiver(s) 106 and then store information obtained by processing the fourth information / signals in the memory(s) 204. The memory(s) 204 may be connected to the processor(s) 202 and may store a variety of information related to operations of the processor(s) 202. For example, the memory(s) 204 may store software code including commands for performing a part or the entirety of processes controlled by the processor(s) 202 or for performing the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts described in the present disclosure. Herein, the processor(s) 202 and the memory(s) 204 may be a part of a communication modem / circuit / chip designed to implement RAT (e.g., LTE or NR). The transceiver(s) 206 may be connected to the processor(s) 202 and transmit and / or receive radio signals through one or more antennas 208. Each of the transceiver(s) 206 may include a transmitter and / or a receiver. The transceiver(s) 206 may be interchangeably used with RF unit(s). In the present disclosure, the second wireless device 200 may represent a communication modem / circuit / chip.

[0076] Hereinafter, hardware elements of the wireless devices 100 and 200 will be described more specifically. One or more protocol layers may be implemented by, without being limited to, one or more processors 102 and 202. For example, the one or more processors 102 and 202 may implement one or more layers (e.g., functional layers such as physical (PHY) layer, media access control (MAC) layer, radio link control (RLC) layer, packet data convergence protocol (PDCP) layer, radio resource control (RRC) layer, and service data adaptation protocol (SDAP) layer). The one or more processors 102 and 202 may generate one or more protocol data units (PDUs) and / or one or more service data unit (SDUs) according to the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed in the present disclosure. The one or more processors 102 and 202 may generate messages, control information, data, or information according to the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed in the present disclosure. The one or more processors 102 and 202 may generate signals (e.g., baseband signals) including PDUs, SDUs, messages, control information, data, or information according to the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed in the present disclosure and provide the generated signals to the one or more transceivers 106 and 206. The one or more processors 102 and 202 may receive the signals (e.g., baseband signals) from the one or more transceivers 106 and 206 and acquire the PDUs, SDUs, messages, control information, data, or information according to the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed in the present disclosure.

[0077] The one or more processors 102 and 202 may be referred to as controllers, microcontrollers, microprocessors, or microcomputers. The one or more processors 102 and 202 may be implemented by hardware, firmware, software, or a combination thereof. As an 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 the one or more processors 102 and 202. descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed in the present disclosure may be implemented using firmware or software and the firmware or software may be configured to include the modules, procedures, or functions. Firmware or software configured to perform the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed in the present disclosure may be included in the one or more processors 102 and 202 or stored in the one or more memories 104 and 204 so as to be driven by the one or more processors 102 and 202. The descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed in the present disclosure may be implemented using firmware or software in the form of code, commands, and / or a set of commands.

[0078] The one or more memories 104 and 204 may be connected to the one or more processors 102 and 202 and store various types of data, signals, messages, information, programs, code, instructions, and / or commands. The one or more memories 104 and 204 may be configured by read-only memories (ROMs), random access memories (RAMs), electrically erasable programmable read-only memories (EPROMs), flash memories, hard drives, registers, cash memories, computer-readable storage media, and / or combinations thereof. The one or more memories 104 and 204 may be located at the interior and / or exterior of the one or more processors 102 and 202. The one or more memories 104 and 204 may be connected to the one or more processors 102 and 202 through various technologies such as wired or wireless connection.

[0079] The one or more transceivers 106 and 206 may transmit user data, control information, and / or radio signals / channels, mentioned in the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed in the present disclosure, to one or more other devices. The one or more transceivers 106 and 206 may receive user data, control information, and / or radio signals / channels, mentioned in the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed in the present disclosure, from one or more other devices. For example, the one or more transceivers 106 and 206 may be connected to the one or more processors 102 and 202 and transmit and receive radio signals. For example, the one or more processors 102 and 202 may perform control so that the one or more transceivers 106 and 206 may transmit user data, control information, or radio signals to one or more other devices. The one or more processors 102 and 202 may perform control so that the one or more transceivers 106 and 206 may receive user data, control information, or radio signals from one or more other devices.

[0080] The one or more transceivers 106 and 206 may be connected to the one or more antennas 108 and 208 and the one or more transceivers 106 and 206 may be configured to transmit and receive user data, control information, and / or radio signals / channels, mentioned in the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed in the present disclosure, through the one or more antennas 108 and 208. In the present disclosure, the one or more antennas may be a plurality of physical antennas or a plurality of logical antennas (e.g., antenna ports).

[0081] The one or more transceivers 106 and 206 may convert received radio signals / channels, etc., from RF band signals into baseband signals in order to process received user data, control information, radio signals / channels, etc., using the one or more processors 102 and 202. The one or more transceivers 106 and 206 may convert the user data, control information, radio signals / channels, etc., processed using the one or more processors 102 and 202 from the base band signals into the RF band signals. To this end, the one or more transceivers 106 and 206 may include (analog) oscillators and / or filters. For example, the transceivers 106 and 206 can up-convert OFDM baseband signals to a carrier frequency by their (analog) oscillators and / or filters under the control of the processors 102 and 202 and transmit the up-converted OFDM signals at the carrier frequency. The transceivers 106 and 206 may receive OFDM signals at a carrier frequency and down-convert the OFDM signals into OFDM baseband signals by their (analog) oscillators and / or filters under the control of the transceivers 102 and 202.

[0082] In the implementations of the present disclosure, a UE may operate as a transmitting device in uplink (UL) and as a receiving device in downlink (DL). In the implementations of the present disclosure, a BS may operate as a receiving device in UL and as a transmitting device in DL. Hereinafter, for convenience of description, it is mainly assumed that the first wireless device 100 acts as the UE, and the second wireless device 200 acts as the BS. For example, the processor(s) 102 connected to, mounted on or launched in the first wireless device 100 may be configured to perform the UE behavior according to an implementation of the present disclosure or control the transceiver(s) 106 to perform the UE behavior according to an implementation of the present disclosure. The processor(s) 202 connected to, mounted on or launched in the second wireless device 200 may be configured to perform the BS behavior according to an implementation of the present disclosure or control the transceiver(s) 206 to perform the BS behavior according to an implementation of the present disclosure.

[0083] In the present disclosure, a BS is also referred to as a node B (NB), an eNode B (eNB), or a gNB.

[0084] FIG. 3 shows an example of a wireless device to which implementations of the present disclosure is applied.

[0085] The wireless device may be implemented in various forms according to a use-case / service (refer to FIG. 1).

[0086] Referring to FIG. 3, wireless devices 100 and 200 may correspond to the wireless devices 100 and 200 of FIG. 2 and may be configured by various elements, components, units / portions, and / or modules. For example, each of the wireless devices 100 and 200 may include a communication unit 110, a control unit 120, a memory unit 130, and additional components 140. The communication unit 110 may include a communication circuit 112 and transceiver(s) 114. For example, the communication circuit 112 may include the one or more processors 102 and 202 of FIG. 2 and / or the one or more memories 104 and 204 of FIG. 2. For example, the transceiver(s) 114 may include the one or more transceivers 106 and 206 of FIG. 2 and / or the one or more antennas 108 and 208 of FIG. 2. The control unit 120 is electrically connected to the communication unit 110, the memory 130, and the additional components 140 and controls overall operation of each of the wireless devices 100 and 200. For example, the control unit 120 may control an electric / mechanical operation of each of the wireless devices 100 and 200 based on programs / code / commands / information stored in the memory unit 130. The control unit 120 may transmit the information stored in the memory unit 130 to the exterior (e.g., other communication devices) via the communication unit 110 through a wireless / wired interface or store, in the memory unit 130, information received through the wireless / wired interface from the exterior (e.g., other communication devices) via the communication unit 110.

[0087] The additional components 140 may be variously configured according to types of the wireless devices 100 and 200. For example, the additional components 140 may include at least one of a power unit / battery, input / output (I / O) unit (e.g., audio I / O port, video I / O port), a driving unit, and a computing unit. The wireless devices 100 and 200 may be implemented in the form of, without being limited to, the robot (100a of FIG. 1), the vehicles (100b-1 and 100b-2 of FIG. 1), the XR device (100c of FIG. 1), the hand-held device (100d of FIG. 1), the home appliance (100e of FIG. 1), the IoT device (100f of FIG. 1), a digital broadcast terminal, a hologram device, a public safety device, an MTC device, a medicine device, a FinTech device (or a finance device), a security device, a climate / environment device, the AI server / device (400 of FIG. 1), the BSs (200 of FIG. 1), a network node, etc. The wireless devices 100 and 200 may be used in a mobile or fixed place according to a use-example / service.

[0088] In FIG. 3, the entirety of the various elements, components, units / portions, and / or modules in the wireless devices 100 and 200 may be connected to each other through a wired interface or at least a part thereof may be wirelessly connected through the communication unit 110. For example, in each of the wireless devices 100 and 200, the control unit 120 and the communication unit 110 may be connected by wire and the control unit 120 and first units (e.g., 130 and 140) may be wirelessly connected through the communication unit 110. Each element, component, unit / portion, and / or module within the wireless devices 100 and 200 may further include one or more elements. For example, the control unit 120 may be configured by a set of one or more processors. As an example, the control unit 120 may be configured by a set of a communication control processor, an application processor (AP), an electronic control unit (ECU), a graphical processing unit, and a memory control processor. As another example, the memory 130 may be configured by a RAM, a DRAM, a ROM, a flash memory, a volatile memory, a non-volatile memory, and / or a combination thereof.

[0089] FIG. 4 shows another example of wireless devices to which implementations of the present disclosure is applied.

[0090] Referring to FIG. 4, wireless devices 100 and 200 may correspond to the wireless devices 100 and 200 of FIG. 2 and may be configured by various elements, components, units / portions, and / or modules.

[0091] The first wireless device 100 may include at least one transceiver, such as a transceiver 106, and at least one processing chip, such as a processing chip 101. The processing chip 101 may include at least one processor, such a processor 102, and at least one memory, such as a memory 104. The memory 104 may be operably connectable to the processor 102. The memory 104 may store various types of information and / or instructions. The memory 104 may store a software code 105 which implements instructions that, when executed by the processor 102, perform the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed in the present disclosure. For example, the software code 105 may implement instructions that, when executed by the processor 102, perform the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed in the present disclosure. For example, the software code 105 may control the processor 102 to perform one or more protocols. For example, the software code 105 may control the processor 102 may perform one or more layers of the radio interface protocol.

[0092] The second wireless device 200 may include at least one transceiver, such as a transceiver 206, and at least one processing chip, such as a processing chip 201. The processing chip 201 may include at least one processor, such a processor 202, and at least one memory, such as a memory 204. The memory 204 may be operably connectable to the processor 202. The memory 204 may store various types of information and / or instructions. The memory 204 may store a software code 205 which implements instructions that, when executed by the processor 202, perform the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed in the present disclosure. For example, the software code 205 may implement instructions that, when executed by the processor 202, perform the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed in the present disclosure. For example, the software code 205 may control the processor 202 to perform one or more protocols. For example, the software code 205 may control the processor 202 may perform one or more layers of the radio interface protocol.

[0093] FIG. 5 shows an example of UE to which implementations of the present disclosure is applied.

[0094] Referring to FIG. 5, a UE 100 may correspond to the first wireless device 100 of FIG. 2 and / or the first wireless device 100 of FIG. 4.

[0095] A UE 100 includes a processor 102, a memory 104, a transceiver 106, one or more antennas 108, a power management module 110, a battery 1112, a display 114, a keypad 116, a subscriber identification module (SIM) card 118, a speaker 120, and a microphone 122.

[0096] The processor 102 may be configured to implement the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed in the present disclosure. The processor 102 may be configured to control one or more other components of the UE 100 to implement the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed in the present disclosure. Layers of the radio interface protocol may be implemented in the processor 102. The processor 102 may include ASIC, other chipset, logic circuit and / or data processing device. The processor 102 may be an application processor. The processor 102 may include at least one of a digital signal processor (DSP), a central processing unit (CPU), a graphics processing unit (GPU), a modem (modulator and demodulator). An example of the processor 102 may be found in SNAPDRAGONTMseries of processors made by Qualcomm®, EXYNOSTMseries of processors made by Samsung®, A series of processors made by Apple®, HELIOTMseries of processors made by MediaTek®, ATOMTMseries of processors made by Intel®or a corresponding next generation processor.

[0097] The memory 104 is operatively coupled with the processor 102 and stores a variety of information to operate the processor 102. The memory 104 may include ROM, RAM, flash memory, memory card, storage medium and / or other storage device. When the embodiments are implemented in software, the techniques described herein can be implemented with modules (e.g., procedures, functions, etc.) that perform the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed in the present disclosure. The modules can be stored in the memory 104 and executed by the processor 102. The memory 104 can be implemented within the processor 102 or external to the processor 102 in which case those can be communicatively coupled to the processor 102 via various means as is known in the art.

[0098] The transceiver 106 is operatively coupled with the processor 102, and transmits and / or receives a radio signal. The transceiver 106 includes a transmitter and a receiver. The transceiver 106 may include baseband circuitry to process radio frequency signals. The transceiver 106 controls the one or more antennas 108 to transmit and / or receive a radio signal.

[0099] The power management module 110 manages power for the processor 102 and / or the transceiver 106. The battery 112 supplies power to the power management module 110.

[0100] The display 114 outputs results processed by the processor 102. The keypad 116 receives inputs to be used by the processor 102. The keypad 16 may be shown on the display 114.

[0101] The SIM card 118 is an　integrated circuit　that is intended to　securely store the　international mobile subscriber identity　(IMSI) number and its related　key, which are used to identify and authenticate subscribers on　mobile telephony　devices (such as　mobile phones　and　computers). It is also possible to store contact information on many SIM cards.

[0102] The speaker 120 outputs sound-related results processed by the processor 102. The microphone 122 receives sound-related inputs to be used by the processor 102.

[0103] FIGS. 6 and 7 show an example of protocol stacks in a 3GPP based wireless communication system to which implementations of the present disclosure is applied.

[0104] In particular, FIG. 6 illustrates an example of a radio interface user plane protocol stack between a UE and a BS and FIG. 7 illustrates an example of a radio interface control plane protocol stack between a UE and a BS. The control plane refers to a path through which control messages used to manage call by a UE and a network are transported. The user plane refers to a path through which data generated in an application layer, for example, voice data or Internet packet data are transported. Referring to FIG. 6, the user plane protocol stack may be divided into Layer 1 (i.e., a PHY layer) and Layer 2. Referring to FIG. 7, the control plane protocol stack may be divided into Layer 1 (i.e., a PHY layer), Layer 2, Layer 3 (e.g., an RRC layer), and a non-access stratum (NAS) layer. Layer 1, Layer 2 and Layer 3 are referred to as an access stratum (AS).

[0105] In the 3GPP LTE system, the Layer 2 is split into the following sublayers: MAC, RLC, and PDCP. In the 3GPP NR system, the Layer 2 is split into the following sublayers: MAC, RLC, PDCP and SDAP. The PHY layer offers to the MAC sublayer transport channels, the MAC sublayer offers to the RLC sublayer logical channels, the RLC sublayer offers to the PDCP sublayer RLC channels, the PDCP sublayer offers to the SDAP sublayer radio bearers. The SDAP sublayer offers to 5G core network quality of service (QoS) flows.

[0106] In the 3GPP NR system, the main services and functions of the MAC sublayer include: mapping between logical channels and transport channels; multiplexing / de-multiplexing of MAC SDUs belonging to one or different logical channels into / from transport blocks (TB) delivered to / from the physical layer on transport channels; scheduling information reporting; error correction through hybrid automatic repeat request (HARQ) (one HARQ entity per cell in case of carrier aggregation (CA)); priority handling between UEs by means of dynamic scheduling; priority handling between logical channels of one UE by means of logical channel prioritization; padding. A single MAC entity may support multiple numerologies, transmission timings and cells. Mapping restrictions in logical channel prioritization control which numerology(ies), cell(s), and transmission timing(s) a logical channel can use.

[0107] Different kinds of data transfer services are offered by MAC. To accommodate different kinds of data transfer services, multiple types of logical channels are defined, i.e., each supporting transfer of a particular type of information. Each logical channel type is defined by what type of information is transferred. Logical channels are classified into two groups: control channels and traffic channels. Control channels are used for the transfer of control plane information only, and traffic channels are used for the transfer of user plane information only. Broadcast control channel (BCCH) is a downlink logical channel for broadcasting system control information, paging control channel (PCCH) is a downlink logical channel that transfers paging information, system information change notifications and indications of ongoing public warning service (PWS) broadcasts, common control channel (CCCH) is a logical channel for transmitting control information between UEs and network and used for UEs having no RRC connection with the network, and dedicated control channel (DCCH) is a point-to-point bi-directional logical channel that transmits dedicated control information between a UE and the network and used by UEs having an RRC connection. Dedicated traffic channel (DTCH) is a point-to-point logical channel, dedicated to one UE, for the transfer of user information. A DTCH can exist in both uplink and downlink. In downlink, the following connections between logical channels and transport channels exist: BCCH can be mapped to broadcast channel (BCH); BCCH can be mapped to downlink shared channel (DL-SCH); PCCH can be mapped to paging channel (PCH); CCCH can be mapped to DL-SCH; DCCH can be mapped to DL-SCH; and DTCH can be mapped to DL-SCH. In uplink, the following connections between logical channels and transport channels exist: CCCH can be mapped to uplink shared channel (UL-SCH); DCCH can be mapped to UL-SCH; and DTCH can be mapped to UL-SCH.

[0108] The RLC sublayer supports three transmission modes: transparent mode (TM), unacknowledged mode (UM), and acknowledged node (AM). The RLC configuration is per logical channel with no dependency on numerologies and / or transmission durations. In the 3GPP NR system, the main services and functions of the RLC sublayer depend on the transmission mode and include: transfer of upper layer PDUs; sequence numbering independent of the one in PDCP (UM and AM); error correction through ARQ (AM only); segmentation (AM and UM) and re-segmentation (AM only) of RLC SDUs; reassembly of SDU (AM and UM); duplicate detection (AM only); RLC SDU discard (AM and UM); RLC re-establishment; protocol error detection (AM only).

[0109] In the 3GPP NR system, the main services and functions of the PDCP sublayer for the user plane include: sequence numbering; header compression and decompression using robust header compression (ROHC); transfer of user data; reordering and duplicate detection; in-order delivery; PDCP PDU routing (in case of split bearers); retransmission of PDCP SDUs; ciphering, deciphering and integrity protection; PDCP SDU discard; PDCP re-establishment and data recovery for RLC AM; PDCP status reporting for RLC AM; duplication of PDCP PDUs and duplicate discard indication to lower layers. The main services and functions of the PDCP sublayer for the control plane include: sequence numbering; ciphering, deciphering and integrity protection; transfer of control plane data; reordering and duplicate detection; in-order delivery; duplication of PDCP PDUs and duplicate discard indication to lower layers.

[0110] In the 3GPP NR system, the main services and functions of SDAP include: mapping between a QoS flow and a data radio bearer; marking QoS flow ID (QFI) in both DL and UL packets. A single protocol entity of SDAP is configured for each individual PDU session.

[0111] In the 3GPP NR system, the main services and functions of the RRC sublayer include: broadcast of system information related to AS and NAS; paging initiated by 5GC or NG-RAN; establishment, maintenance and release of an RRC connection between the UE and NG-RAN; security functions including key management; establishment, configuration, maintenance and release of signaling radio bearers (SRBs) and data radio bearers (DRBs); mobility functions (including: handover and context transfer, UE cell selection and reselection and control of cell selection and reselection, inter-RAT mobility); QoS management functions; UE measurement reporting and control of the reporting; detection of and recovery from radio link failure; NAS message transfer to / from NAS from / to UE.

[0112] FIG. 8 shows a frame structure in a 3GPP based wireless communication system to which implementations of the present disclosure is applied.

[0113] The frame structure shown in FIG. 8 is purely exemplary and the number of subframes, the number of slots, and / or the number of symbols in a frame may be variously changed. In the 3GPP based wireless communication system, OFDM numerologies (e.g., subcarrier spacing (SCS), transmission time interval (TTI) duration) may be differently configured between a plurality of cells aggregated for one UE. For example, if a UE is configured with different SCSs for cells aggregated for the cell, an (absolute time) duration of a time resource (e.g., a subframe, a slot, or a TTI) including the same number of symbols may be different among the aggregated cells. Herein, symbols may include OFDM symbols (or CP-OFDM symbols), SC-FDMA symbols (or discrete Fourier transform-spread-OFDM (DFT-s-OFDM) symbols).

[0114] Referring to FIG. 8, downlink and uplink transmissions are organized into frames. Each frame has Tf= 10ms duration. Each frame is divided into two half-frames, where each of the half-frames has 5ms duration. Each half-frame consists of 5 subframes, where the duration Tsfper subframe is 1ms. Each subframe is divided into slots and the number of slots in a subframe depends on a subcarrier spacing. Each slot includes 14 or 12 OFDM symbols based on a cyclic prefix (CP). In a normal CP, each slot includes 14 OFDM symbols and, in an extended CP, each slot includes 12 OFDM symbols. The numerology is based on exponentially scalable subcarrier spacing △f = 2u*15 kHz.

[0115] Table 1 shows the number of OFDM symbols per slot Nslotsymb, the number of slots per frameNframe,uslot, and the number of slots per subframe Nsubframe,uslotfor the normal CP, according to the subcarrier spacing △f = 2u*15 kHz.

[0116] uNslotsymbNframe,uslotNsubframe,uslot01410111420221440431480841416016

[0117] Table 2 shows the number of OFDM symbols per slot Nslotsymb, the number of slots per frameNframe,uslot, and the number of slots per subframe Nsubframe,uslotfor the extended CP, according to the subcarrier spacing △f = 2u*15 kHz.

[0118] uNslotsymbNframe,uslotNsubframe,uslot212404

[0119] A slot includes plural symbols (e.g., 14 or 12 symbols) in the time domain. For each numerology (e.g., subcarrier spacing) and carrier, a resource grid ofNsize,ugrid,x*NRBscsubcarriers andNsubframe,usymbOFDM symbols is defined, starting at common resource block (CRB)Nstart,ugridindicated by higher-layer signaling (e.g., RRC signaling), whereNsize,ugrid,xis the number of resource blocks (RBs) in the resource grid and the subscript x is DL for downlink and UL for uplink.NRBscis the number of subcarriers per RB. In the 3GPP based wireless communication system,NRBscis 12 generally. There is one resource grid for a given antenna portp, subcarrier spacing configurationu, and transmission direction (DL or UL). The carrier bandwidthNsize,ugridfor subcarrier spacing configurationuis given by the higher-layer parameter (e.g., RRC parameter). Each element in the resource grid for the antenna portpand the subcarrier spacing configurationuis referred to as a resource element (RE) and one complex symbol may be mapped to each RE. Each RE in the resource grid is uniquely identified by an indexkin the frequency domain and an indexlrepresenting a symbol location relative to a reference point in the time domain. In the 3GPP based wireless communication system, an RB is defined by 12 consecutive subcarriers in the frequency domain.

[0120] In the 3GPP NR system, RBs are classified into CRBs and physical resource blocks (PRBs). CRBs are numbered from 0 and upwards in the frequency domain for subcarrier spacing configurationu. The center of subcarrier 0 of CRB 0 for subcarrier spacing configurationucoincides with 'point A' which serves as a common reference point for resource block grids. In the 3GPP NR system, PRBs are defined within a bandwidth part (BWP) and numbered from 0 toNsizeBWP,i-1, where i is the number of the bandwidth part. The relation between the physical resource block nPRBin the bandwidth part i and the common resource block nCRBis as follows: nPRB= nCRB+NsizeBWP,i, whereNsizeBWP,iis the common resource block where bandwidth part starts relative to CRB 0. The BWP includes a plurality of consecutive RBs. A carrier may include a maximum of N (e.g., 5) BWPs. A UE may be configured with one or more BWPs on a given component carrier. Only one BWP among BWPs configured to the UE can active at a time. The active BWP defines the UE's operating bandwidth within the cell's operating bandwidth.

[0121] The NR frequency band may be defined as two types of frequency range, i.e., FR1 and FR2. The numerical value of the frequency range may be changed. For example, the frequency ranges of the two types (FR1 and FR2) may be as shown in Table 3 below. For ease of explanation, in the frequency ranges used in the NR system, FR1 may mean "sub 6 GHz range", FR2 may mean "above 6 GHz range," and may be referred to as millimeter wave (mmW).

[0122] Frequency Range designationCorresponding frequency rangeSubcarrier SpacingFR1450MHz - 6000MHz15, 30, 60kHzFR224250MHz - 52600MHz60, 120, 240kHz

[0123] As mentioned above, the numerical value of the frequency range of the NR system may be changed. For example, FR1 may include a frequency band of 410MHz to 7125MHz as shown in Table 4 below. That is, FR1 may include a frequency band of 6GHz (or 5850, 5900, 5925 MHz, etc.) or more. For example, a frequency band of 6 GHz (or 5850, 5900, 5925 MHz, etc.) or more included in FR1 may include an unlicensed band. Unlicensed bands may be used for a variety of purposes, for example for communication for vehicles (e.g., autonomous driving).

[0124] Frequency Range designationCorresponding frequency rangeSubcarrier SpacingFR1410MHz - 7125MHz15, 30, 60kHzFR224250MHz - 52600MHz60, 120, 240kHz

[0125] In the present disclosure, the term "cell" may refer to a geographic area to which one or more nodes provide a communication system, or refer to radio resources. A "cell" as a geographic area may be understood as coverage within which a node can provide service using a carrier and a "cell" as radio resources (e.g., time-frequency resources) is associated with bandwidth which is a frequency range configured by the carrier. The "cell" associated with the radio resources is defined by a combination of downlink resources and uplink resources, for example, a combination of a DL component carrier (CC) and a UL CC. The cell may be configured by downlink resources only, or may be configured by downlink resources and uplink resources. Since DL coverage, which is a range within which the node is capable of transmitting a valid signal, and UL coverage, which is a range within which the node is capable of receiving the valid signal from the UE, depends upon a carrier carrying the signal, the coverage of the node may be associated with coverage of the "cell" of radio resources used by the node. Accordingly, the term "cell" may be used to represent service coverage of the node sometimes, radio resources at other times, or a range that signals using the radio resources can reach with valid strength at other times.

[0126] In CA, two or more CCs are aggregated. A UE may simultaneously receive or transmit on one or multiple CCs depending on its capabilities. CA is supported for both contiguous and non-contiguous CCs. When CA is configured, the UE only has one RRC connection with the network. At RRC connection establishment / re-establishment / handover, one serving cell provides the NAS mobility information, and at RRC connection re-establishment / handover, one serving cell provides the security input. This cell is referred to as the primary cell (PCell). The PCell is a cell, operating on the primary frequency, in which the UE either performs the initial connection establishment procedure or initiates the connection re-establishment procedure. Depending on UE capabilities, secondary cells (SCells) can be configured to form together with the PCell a set of serving cells. An SCell is a cell providing additional radio resources on top of special cell (SpCell). The configured set of serving cells for a UE therefore always consists of one PCell and one or more SCells. For dual connectivity (DC) operation, the term SpCell refers to the PCell of the master cell group (MCG) or the primary SCell (PSCell) of the secondary cell group (SCG). An SpCell supports PUCCH transmission and contention-based random access, and is always activated. The MCG is a group of serving cells associated with a master node, comprised of the SpCell (PCell) and optionally one or more SCells. The SCG is the subset of serving cells associated with a secondary node, comprised of the PSCell and zero or more SCells, for a UE configured with DC. For a UE in RRC_CONNECTED not configured with CA / DC, there is only one serving cell comprised of the PCell. For a UE in RRC_CONNECTED configured with CA / DC, the term "serving cells" is used to denote the set of cells comprised of the SpCell(s) and all SCells. In DC, two MAC entities are configured in a UE: one for the MCG and one for the SCG.

[0127] FIG. 9 shows a data flow example in the 3GPP NR system to which implementations of the present disclosure is applied.

[0128] Referring to FIG. 9, "RB" denotes a radio bearer, and "H" denotes a header. Radio bearers are categorized into two groups: DRBs for user plane data and SRBs for control plane data. The MAC PDU is transmitted / received using radio resources through the PHY layer to / from an external device. The MAC PDU arrives to the PHY layer in the form of a transport block.

[0129] In the PHY layer, the uplink transport channels UL-SCH and RACH are mapped to their physical channels PUSCH and PRACH, respectively, and the downlink transport channels DL-SCH, BCH and PCH are mapped to PDSCH, PBCH and PDSCH, respectively. In the PHY layer, uplink control information (UCI) is mapped to PUCCH, and downlink control information (DCI) is mapped to PDCCH. A MAC PDU related to UL-SCH is transmitted by a UE via a PUSCH based on an UL grant, and a MAC PDU related to DL-SCH is transmitted by a BS via a PDSCH based on a DL assignment.

[0130] Hereinafter, technical features related to measurements are described. Section 5.5 of 3GPP TS 38.331 v17.5.0 may be referred.

[0131] The network may configure an RRC_CONNECTED UE to perform measurements. The network may configure the UE to report them in accordance with the measurement configuration or perform conditional reconfiguration evaluation in accordance with the conditional reconfiguration. The measurement configuration is provided by means of dedicated signalling i.e. using theRRCReconfigurationorRRCResume.

[0132] The network may configure the UE to perform the following types of measurements:

[0133] - NR measurements;

[0134] - Inter-RAT measurements of E-UTRA frequencies;

[0135] - Inter-RAT measurements of UTRA-FDD frequencies;

[0136] - NR sidelink measurements of L2 U2N Relay UEs.

[0137] The network may configure the UE to report the following measurement information based on SS / PBCH block(s):

[0138] - Measurement results per SS / PBCH block;

[0139] - Measurement results per cell based on SS / PBCH block(s);

[0140] - SS / PBCH block(s) indexes.

[0141] The network may configure the UE to report the following measurement information based on CSI-RS resources:

[0142] - Measurement results per CSI-RS resource;

[0143] - Measurement results per cell based on CSI-RS resource(s);

[0144] - CSI-RS resource measurement identifiers.

[0145] The network may configure the UE to perform the following types of measurements for NR sidelink and V2X sidelink:

[0146] - CBR measurements.

[0147] The network may configure the UE to report the following CLI measurement information based on SRS resources:

[0148] - Measurement results per SRS resource;

[0149] - SRS resource(s) indexes.

[0150] The network may configure the UE to report the following CLI measurement information based on CLI-RSSI resources:

[0151] - Measurement results per CLI-RSSI resource;

[0152] - CLI-RSSI resource(s) indexes.

[0153] The network may configure the UE to report the following Rx-Tx time difference measurement information based on CSI-RS for tracking or PRS:

[0154] - UE Rx-Tx time difference measurement result.

[0155] The measurement configuration includes the following parameters:

[0156] 1.Measurement objects:A list of objects on which the UE shall perform the measurements.

[0157] - For intra-frequency and inter-frequency measurements a measurement object indicates the frequency / time location and subcarrier spacing of reference signals to be measured. Associated with this measurement object, the network may configure a list of cell specific offsets, a list of 'exclude-listed' cells and a list of 'allow-listed' cells. Exclude-listed cells are not applicable in event evaluation or measurement reporting. Allow-listed cells are the only ones applicable in event evaluation or measurement reporting.

[0158] - ThemeasObjectIdof the MO which corresponds to each serving cell is indicated byservingCellMOwithin the serving cell configuration.

[0159] - For inter-RAT E-UTRA measurements a measurement object is a single E-UTRA carrier frequency. Associated with this E-UTRA carrier frequency, the network can configure a list of cell specific offsets and a list of 'exclude-listed' cells. Exclude-listed cells are not applicable in event evaluation or measurement reporting.

[0160] - For inter-RAT UTRA-FDD measurements a measurement object is a set of cells on a single UTRA-FDD carrier frequency.

[0161] - For NR sidelink measurements of L2 U2N Relay UEs, a measurement object is a single NR sidelink frequency to be measured.

[0162] - For CBR measurement of NR sidelink communication, a measurement object is a set of transmission resource pool(s) on a single carrier frequency for NR sidelink communication.

[0163] - For CBR measurement of NR sidelink discovery, a measurement object is a set of discovery dedicated resource pool(s) or transmission resource pool(s) also used for NR sidelink discovery on a single carrier frequency for NR sidelink discovery.

[0164] - For CLI measurements a measurement object indicates the frequency / time location of SRS resources and / or CLI-RSSI resources, and subcarrier spacing of SRS resources to be measured.

[0165] 2.Reporting configurations:A list of reporting configurations where there can be one or multiple reporting configurations per measurement object. Each measurement reporting configuration consists of the following:

[0166] - Reporting criterion: The criterion that triggers the UE to send a measurement report. This can either be periodical or a single event description.

[0167] - RS type: The RS that the UE uses for beam and cell measurement results (SS / PBCH block or CSI-RS).

[0168] - Reporting format: The quantities per cell and per beam that the UE includes in the measurement report (e.g. RSRP) and other associated information such as the maximum number of cells and the maximum number beams per cell to report.

[0169] In case of conditional reconfiguration, each configuration consists of the following:

[0170] - Execution criteria: The criteria the UE uses for conditional reconfiguration execution.

[0171] - RS type: The RS that the UE uses for obtaining beam and cell measurement results (SS / PBCH block-based or CSI-RS-based), used for evaluating conditional reconfiguration execution condition.

[0172] 3.Measurement identities:For measurement reporting, a list of measurement identities where each measurement identity links one measurement object with one reporting configuration. By configuring multiple measurement identities, it is possible to link more than one measurement object to the same reporting configuration, as well as to link more than one reporting configuration to the same measurement object. The measurement identity is also included in the measurement report that triggered the reporting, serving as a reference to the network. For conditional reconfiguration triggering, one measurement identity links to exactly one conditional reconfiguration trigger configuration. And up to 2 measurement identities can be linked to one conditional reconfiguration execution condition.

[0173] 4.Quantity configurations:The quantity configuration defines the measurement filtering configuration used for all event evaluation and related reporting, and for periodical reporting of that measurement. For NR measurements, the network may configure up to 2 quantity configurations with a reference in the NR measurement object to the configuration that is to be used. In each configuration, different filter coefficients can be configured for different measurement quantities, for different RS types, and for measurements per cell and per beam.

[0174] 5.Measurement gaps:Periods that the UE may use to perform measurements.

[0175] A UE in RRC_CONNECTED maintains a measurement object list, a reporting configuration list, and a measurement identities list according to signalling and procedures in this specification. The measurement object list possibly includes NR measurement object(s), CLI measurement object(s), inter-RAT objects, and L2 U2N Relay objects. Similarly, the reporting configuration list includes NR, inter-RAT, and L2 U2N Relay reporting configurations. Any measurement object can be linked to any reporting configuration of the same RAT type. Some reporting configurations may not be linked to a measurement object. Likewise, some measurement objects may not be linked to a reporting configuration.

[0176] The measurement procedures distinguish the following types of cells:

[0177] 1. The NR serving cell(s) - these are the SpCell and one or more SCells.

[0178] 2. Listed cells - these are cells listed within the measurement object(s).

[0179] 3. Detected cells - these are cells that are not listed within the measurement object(s) but are detected by the UE on the SSB frequency(ies) and subcarrier spacing(s) indicated by the measurement object(s).

[0180] For NR measurement object(s), the UE measures and reports on the serving cell(s) / serving Relay UE (for L2 U2N Remote UE), listed cells and / or detected cells. For inter-RAT measurements object(s) of E-UTRA, the UE measures and reports on listed cells and detected cells and, for RSSI and channel occupancy measurements, the UE measures and reports on the configured resources on the indicated frequency. For inter-RAT measurements object(s) of UTRA-FDD, the UE measures and reports on listed cells. For CLI measurement object(s), the UE measures and reports on configured measurement resources (i.e. SRS resources and / or CLI-RSSI resources). For L2 U2N Relay object(s), the UE measures and reports on the serving NR cell(s), as well as the discovered L2 U2N Relay UEs.

[0181] Whenever the procedural specification, other than contained in clause 5.5.2, refers to a field it concerns a field included in theVarMeasConfigunless explicitly stated otherwise i.e. only the measurement configuration procedure covers the direct UE action related to the receivedmeasConfig.

[0182] In NR-DC, the UE may receive two independentmeasConfig:

[0183] - ameasConfig, associated with MCG, that is included in theRRCReconfigurationmessage received via SRB1; and

[0184] - ameasConfig, associated with SCG, that is included in theRRCReconfigurationmessage received via SRB3, or, alternatively, included within aRRCReconfigurationmessage embedded in aRRCReconfigurationmessage received via SRB1.

[0185] In this case, the UE maintains two independentVarMeasConfigandVarMeasReportList, one associated with eachmeasConfig, and independently performs all the procedures for eachmeasConfigand the associatedVarMeasConfigandVarMeasReportList, unless explicitly stated otherwise.

[0186] The configurations related to CBR measurements are only included in themeasConfigassociated with MCG.

[0187] The configurations related to Rx-Tx time difference measurement are only included in themeasConfigassociated with MCG.

[0188] Measurement configuration

[0189] The network applies the procedure as follows:

[0190] - to ensure that, whenever the UE has ameasConfigassociated with a CG, it includes ameasObjectfor the SpCell and for each NR SCell of the CG to be measured;

[0191] - to configure at most one measurement identity across all CGs using a reporting configuration with thereportTypeset toreportCGI;

[0192] - to configure at most one measurement identity per the node hosting PDCP entity using a reporting configuration with theul-DelayValueConfig;

[0193] - to configure at most one measurement identity per the node hosting PDCP entity using a reporting configuration with theul-ExcessDelayConfig;

[0194] -to ensure that, in themeasConfigassociated with a CG:

[0195] - for all SSB based measurements there is at most one measurement object with the samessbFrequency;

[0196] -ansmtc1included in any measurement object with the samessbFrequencyhas the same value and that ansmtc2included in any measurement object with the samessbFrequencyhas the same value and that ansmtc3listincluded in any measurement object with the samessbFrequencyhas the same value and that ansmtc4listincluded in any measurement object with the samessbFrequencyhas the same value;

[0197] - to ensure that all measurement objects configured in this specification with the samessbFrequencyhave the samessbSubcarrierSpacing;

[0198] - to ensure that, if a measurement object associated with the MCG has the samessbFrequencyas a measurement object associated with the SCG:

[0199] - for thatssbFrequency, the measurement window according to thesmtc1configured by the MCG includes the measurement window according to thesmtc1configured by the SCG, or vice-versa, with an accuracy of the maximum receive timing difference.

[0200] - if both measurement objects are used for RSSI measurements, bits inmeasurementSlotsin both objects corresponding to the same slot are set to the same value. Also, theendSymbolis the same in both objects.

[0201] - to ensure that, if a measurement object has the samessbFrequencyas a measurement object:

[0202] - for thatssbFrequency, the measurement window according to thesmtcincludes the measurement window according to thesmtc1, or vice-versa, with an accuracy of the maximum receive timing difference.

[0203] - if both measurement objects are used for RSSI measurements, bits inmeasurementSlotsin both objects corresponding to the same slot are set to the same value. Also, theendSymbolis the same in both objects.

[0204] - when the UE is in NE-DC, NR-DC, or NR standalone, to configure at most one measurement identity across all CGs using a reporting configuration with thereportTypeset toreportSFTD;

[0205] For CSI-RS resources, the network applies the procedure as follows:

[0206] - to ensure that all CSI-RS resources configured in each measurement object have the same center frequency, (startPRB+floor(nrofPRBs / 2))

[0207] - to ensure that the total number of CSI-RS resources configured in each measurement object does not exceed the maximum number.

[0208] The UE shall:

[0209] 1> if the receivedmeasConfigincludes themeasObjectToRemoveList:

[0210] 2> perform the measurement object removal procedure;

[0211] 1> if the receivedmeasConfigincludes themeasObjectToAddModList:

[0212] 2> perform the measurement object addition / modification procedure as specified in 5.5.2.5;

[0213] 1> if the receivedmeasConfigincludes thereportConfigToRemoveList:

[0214] 2> perform the reporting configuration removal procedure;

[0215] 1> if the receivedmeasConfigincludes thereportConfigToAddModList:

[0216] 2> perform the reporting configuration addition / modification procedure;

[0217] 1> if the receivedmeasConfigincludes thequantityConfig:

[0218] 2> perform the quantity configuration procedure;

[0219] 1> if the receivedmeasConfigincludes themeasIdToRemoveList:

[0220] 2> perform the measurement identity removal procedure;

[0221] 1> if the receivedmeasConfigincludes themeasIdToAddModList:

[0222] 2> perform the measurement identity addition / modification procedure;

[0223] 1> if the receivedmeasConfigincludes themeasGapConfig:

[0224] 2> perform the measurement gap configuration procedure;

[0225] 1> if the receivedmeasConfigincludes themeasGapSharingConfig:

[0226] 2> perform the measurement gap sharing configuration procedure;

[0227] 1> if the receivedmeasConfigincludes thes-MeasureConfig:

[0228] 2> ifs-MeasureConfigis set tossb-RSRP, set parameterssb-RSRPofs-MeasureConfigwithinVarMeasConfigto the threshold value of the RSRP indicated by the received value ofs-MeasureConfigwhich is derived;

[0229] 2> else, set parametercsi-RSRPofs-MeasureConfigwithinVarMeasConfigto the threshold value of the RSRP indicated by the received value ofs-MeasureConfigwhich is derived.

[0230] Performing measurements

[0231] An RRC_CONNECTED UE shall derive cell measurement results by measuring one or multiple beams associated per cell as configured by the network. For all cell measurement results, except for RSSI, and CLI measurement results in RRC_CONNECTED, the UE applies the layer 3 filtering, before using the measured results for evaluation of reporting criteria, measurement reporting or the criteria to trigger conditional reconfiguration execution. For cell measurements, the network can configure RSRP, RSRQ, SINR, RSCP or EcN0 as trigger quantity. For CLI measurements, the network can configure SRS-RSRP or CLI-RSSI as trigger quantity. For cell and beam measurements, reporting quantities can be any combination of quantities (i.e. only RSRP; only RSRQ; only SINR; RSRP and RSRQ; RSRP and SINR; RSRQ and SINR; RSRP, RSRQ and SINR; only RSCP; only EcN0; RSCP and EcN0), irrespective of the trigger quantity, and for CLI measurements, reporting quantities can be either SRS-RSRP or CLI-RSSI. For conditional reconfiguration execution, the network can configure up to 2 quantities, both using same RS type. The UE does not apply the layer 3 filtering to derive the CBR measurements. The UE does not apply the layer 3 filtering to derive the Rx-Tx time difference measurements.

[0232] The network may also configure the UE to report measurement information per beam (which can either be measurement results per beam with respective beam identifier(s) or only beam identifier(s)). If beam measurement information is configured to be included in measurement reports, the UE applies the layer 3 beam filtering. On the other hand, the exact L1 filtering of beam measurements used to derive cell measurement results is implementation dependent.

[0233] Hereinafter events for triggering measurements reports are described.

[0234] Event A1 (Serving becomes better than threshold)

[0235] Event A2 (Serving becomes worse than threshold)

[0236] Event A3 (Neighbour becomes offset better than SpCell)

[0237] Event A4 (Neighbour becomes better than threshold)

[0238] Event A5 (SpCell becomes worse than threshold1 and neighbour becomes better than threshold2)

[0239] Event A6 (Neighbour becomes offset better than SCell)

[0240] Event B1 (Inter RAT neighbour becomes better than threshold)

[0241] Event B2 (PCell becomes worse than threshold1 and inter RAT neighbour becomes better than threshold2)

[0242] Event I1 (Interference becomes higher than threshold)

[0243] Event C1 (The NR sidelink channel busy ratio is above a threshold)

[0244] Event C2 (The NR sidelink channel busy ratio is below a threshold)

[0245] Event D1 (Distance between UE and referenceLocation1 is above threshold1 and distance between UE and referenceLocation2 is below threshold2)

[0246] CondEvent T1 (Time measured at UE is within a duration from threshold)

[0247] Event X1 (Serving L2 U2N Relay UE becomes worse than threshold1 and NR Cell becomes better than threshold2)

[0248] Event X2 (Serving L2 U2N Relay UE becomes worse than threshold)

[0249] Event Y1 (PCell becomes worse than threshold1 and candidate L2 U2N Relay UE becomes better than threshold2)

[0250] Event Y2 (Candidate L2 U2N Relay UE becomes better than threshold)

[0251] Event H1 (The Aerial UE height is above a threshold)

[0252] Event H2 (The Aerial UE height is below a threshold)

[0253] FIG. 10 shows an example of measurement reporting.

[0254] The purpose of this procedure is to transfer measurement results from the UE to the network. The UE shall initiate this procedure only after successful AS security activation.

[0255] FIG. 11 shows an example of Location measurement indication

[0256] The purpose of this procedure is to indicate to the network that the UE is going to start / stop location related measurements towards E-UTRA or NR (eutra-RSTD, nr-RSTD, nr-UE-RxTxTimeDiff, nr-PRS-RSRP) which require measurement gaps or start / stop detection of subframe and slot timing towards E-UTRA (eutra-FineTimingDetection) which requires measurement gaps. UE shall initiate this procedure only after successful AS security activation.

[0257] Hereinafter, technical features related to RRC reconfiguration are described. Section 5.3.5 of 3GPP TS 38.331 v17.5.0 may be referred.

[0258] FIG. 12 shows an example of RRC reconfiguration, successful.

[0259] The purpose of this procedure is to modify an RRC connection, e.g. to establish / modify / release RBs / BH RLC channels / Uu Relay RLC channels / PC5 Relay RLC channels, to perform reconfiguration with sync, to setup / modify / release measurements, to add / modify / release SCells and cell groups, to add / modify / release conditional handover configuration, to add / modify / release conditional PSCell change or conditional PSCell addition configuration. As part of the procedure, NAS dedicated information may be transferred from the Network to the UE.

[0260] RRC reconfiguration to perform reconfiguration with sync includes, but is not limited to, the following cases:

[0261] - reconfiguration with sync and security key refresh, involving RA to the PCell / PSCell, MAC reset, refresh of security and re-establishment of RLC and PDCP triggered by explicit indicators;

[0262] - reconfiguration with sync but without security key refresh, involving RA to the PCell / PSCell, MAC reset and RLC re-establishment and PDCP data recovery (for AM DRB or AM MRB) triggered by explicit indicators.

[0263] - reconfiguration with sync for DAPS and security key refresh, involving RA to the target PCell, establishment of target MAC, and

[0264] - for non-DAPS bearer: refresh of security and re-establishment of RLC and PDCP triggered by explicit indicators;

[0265] - for DAPS bearer: establishment of RLC for the target PCell, refresh of security and reconfiguration of PDCP to add the ciphering function, the integrity protection function and ROHC function of the target PCell;

[0266] - for SRB: refresh of security and establishment of RLC and PDCP for the target PCell;

[0267] - reconfiguration with sync for DAPS but without security key refresh, involving RA to the target PCell, establishment of target MAC, and

[0268] - for non-DAPS bearer: RLC re-establishment and PDCP data recovery (for AM DRB or AM MRB) triggered by explicit indicators.

[0269] - for DAPS bearer: establishment of RLC for target PCell, reconfiguration of PDCP to add the ciphering function, the integrity protection function and ROHC function of the target PCell;

[0270] - for SRB: establishment of RLC and PDCP for the target PCell.

[0271] - reconfiguration with sync for direct-to-indirect path switch, not involving RA at target side, involving re-establishment of PDCP / PDCP data recovery (for AM DRB) triggered by explicit indicators.

[0272] In (NG)EN-DC and NR-DC, SRB3 can be used for measurement configuration and reporting, for UE assistance (re-)configuration and reporting for power savings, for IP address (re-)configuration and reporting for IAB-nodes, to (re-)configure MAC, RLC, BAP, physical layer and RLF timers and constants of the SCG configuration, and to reconfigure PDCP for DRBs associated with the S-KgNBor SRB3, and to reconfigure SDAP for DRBs associated with S-KgNBin NGEN-DC and NR-DC, and to add / modify / release conditional PSCell change configuration, provided that the (re-)configuration does not require any MN involvement, and to transmit RRC messages between the MN and the UE during fast MCG link recovery. In (NG)EN-DC and NR-DC, onlymeasConfig,radioBearerConfig,conditionalReconfiguration,bap-Config,iab-IP-AddressConfigurationList,otherConfigand / orsecondaryCellGroupare included inRRCReconfigurationreceived via SRB3, except whenRRCReconfigurationis received withinDLInformationTransferMRDC.

[0273] Hereinafter, technical features related to LTE UAV and flight path information are described. Section 5.3.3.4 of 3GPP TS 36.331 v17.5.0 may be referred.

[0274] Reception of theRRCConnectionSetupby the UE

[0275] Prior to this, lower layer signalling is used to allocate a C-RNTI.

[0276] The UE shall:

[0277] 1> set the content ofRRCConnectionSetupCompletemessage as follows:

[0278] 2> if theRRCConnectionSetupis received in response to anRRCConnectionResumeRequest:

[0279] 3> if upper layers provide an S-TMSI:

[0280] 4> set thes-TMSIto the value received from upper layers;

[0281] 3> else if upper layers provide a 5G-S-TMSI:

[0282] 4> if the UE is a NB-IoT UE:

[0283] 5> set theng-5G-S-TMSIto the value received from upper layers;

[0284] 4> else:

[0285] 5> set theng-5G-S-TMSI-Bitstong-5G-S-TMSIwith the value received from upper layers;

[0286] 2> if the UE is connected to EPC:

[0287] 3> except for NB-IoT:

[0288] 4> include themobilityStateand set it to the mobility state of the UE just prior to entering RRC_CONNECTED state;

[0289] 4> if the UE has flight path information available:

[0290] 5> includeflightPathInfoAvailable;

[0291] 3> for NB-IoT:

[0292] 4> if the UE has radio link failure information available inVarRLF-Report-NBand if the RPLMN is included inplmn-IdentityListstored inVarRLF-Report-NB:

[0293] 5> includerlf-InfoAvailable;

[0294] 4> if the UE has ANR measurements information available inVarANR-MeasReport-NBand if the RPLMN is included inplmn-IdentityListstored inVarANR-MeasReport-NB:

[0295] 5> includeanr-InfoAvailable;

[0296] Reception of theRRCConnectionResumeby theUE

[0297] The UE shall:

[0298] 1> set the content ofRRCConnectionResumeCompletemessage as follows:

[0299] 2> set theselectedPLMN-Identityto the PLMN selected by upper layers from the PLMN(s) included in theplmn-IdentityListinSystemInformationBlockType1;

[0300] 2> set thededicatedInfoNASto include the information received from upper layers;

[0301] 2> except for NB-IoT:

[0302] 3> if resuming an RRC connection from a suspended RRC connection:

[0303] 4> if the UE has radio link failure or handover failure information available inVarRLF-Reportand if the RPLMN is included inplmn-IdentityListstored inVarRLF-Report:

[0304] 5> includerlf-InfoAvailable;

[0305] 4> if the UE has MBSFN logged measurements available for E-UTRA and if the RPLMN is included inplmn-IdentityListstored inVarLogMeasReport:

[0306] 5> includelogMeasAvailableMBSFN;

[0307] 4> else if the UE has logged measurements available for E-UTRA and if the RPLMN is included inplmn-IdentityListstored inVarLogMeasReport:

[0308] 5> includelogMeasAvailable;

[0309] 5> if Bluetooth measurement results are included in the logged measurements the UE has available:

[0310] 6> includelogMeasAvailableBT;

[0311] 5> if WLAN measurement results are included in the logged measurements the UE has available:

[0312] 6> includelogMeasAvailableWLAN;

[0313] 4> if the UE has connection establishment failure information available inVarConnEstFailReportand if the RPLMN is equal toplmn-Identitystored inVarConnEstFailReport:

[0314] 5> includeconnEstFailInfoAvailable;

[0315] 4> include themobilityStateand set it to the mobility state (as specified in TS 36.304 [4]) of the UE just prior to entering RRC_CONNECTED state;

[0316] 4> if the UE has flight path information available:

[0317] 5> includeflightPathInfoAvailable;

[0318] 3> if the UE supports storage of mobility history information and the UE has mobility history information available inVarMobilityHistoryReport:

[0319] 4> includemobilityHistoryAvail;

[0320] 3> if theidleModeMeasurementReqis included in theRRCConnectionResumemessage:

[0321] 4> if the UE has idle / inactive measurement information concerning cells other than the PCell available inVarMeasIdleReport:

[0322] 5> set themeasResultListIdle-r16in theRRCConnectionResumeCompletemessage to the value ofmeasReportIdle-r15in theVarMeasIdleReport;

[0323] 5> set themeasResultListExtIdlein theRRCConnectionResumeCompletemessage to the value ofmeasReportIdle-r16in theVarMeasIdleReport, if available;

[0324] 5> set themeasResultListIdleNRin theRRCConnectionResumeCompletemessage to the value ofmeasReportIdleNRin theVarMeasIdleReport, if available;

[0325] 5> discard theVarMeasIdleReportupon successful delivery of theRRCConnectionResumeCompletemessage is confirmed by lower layers;

[0326] 3> else:

[0327] 4> if the SIB2 containsidleModeMeasurementsand the UE has E-UTRA idle / inactive measurement information concerning cells other than the PCell available inVarMeasIdleReport; or

[0328] 4> if the SIB2 containsidleModeMeasurementsNRand the UE has NR idle / inactive measurement information available inVarMeasIdleReport:

[0329] 5> include theidleMeasAvailable;

[0330] 3> if theRRCConnectionResumemessage includesnr-SecondaryCellGroupConfig:

[0331] 4> includescg-ConfigResponseNR;

[0332] 2> for NB-IoT:

[0333] 3> if the UE supports serving cell idle mode measurements reporting andservingCellMeasInfois present inSystemInformationBlockType2-NB:

[0334] 4> set themeasResultServCellto include the measurements of the serving cell;

[0335] - The UE includes the latest results of the serving cell measurements as used for cell selection / reselection evaluation, which are performed in accordance with the performance requirements.

[0336] 3> if the UE is connected to EPC:

[0337] 4> if the UE has radio link failure information available inVarRLF-Report-NBand if the RPLMN is included inplmn-IdentityListstored inVarRLF-Report-NB:

[0338] 5> includerlf-InfoAvailable;

[0339] 4> if the UE has ANR measurements information available inVarANR-MeasReport-NBand if the RPLMN is included inplmn-IdentityListstored inVarANR-MeasReport-NB:

[0340] 5> includeanr-InfoAvailable;

[0341] 2> if the UE is connected to NTN:

[0342] 3> includegnss-validityDurationin accordance with the remaining time of the GNSS validity duration;

[0343] 1> if the UE is configured to operate in EN-DC as result of this procedure, forwardupperLayerIndicationto upper layers as if the UE has received this field from SIB2, otherwise indicate to upper layers the absence of this field;

[0344] 1> submit theRRCConnectionResumeCompletemessage to lower layers for transmission;

[0345] 1> for NB-IoT:

[0346] 2> if the UE supports connected mode measurements andconnMeasConfigis present inSystemInformationBlockType3-NB:

[0347] 3> perform measurements.

[0348] 1> the procedure ends.

[0349] Reception of anRRCConnectionReconfigurationincluding themobilityControlInfoby theUE(handover)

[0350] If theRRCConnectionReconfigurationmessage includes themobilityControlInfoand theUE is able to comply with the configuration included in this message, the UE shall:

[0351] 1> set the content ofRRCConnectionReconfigurationCompletemessage as follows:

[0352] 2> if the UE has radio link failure or handover failure information available inVarRLF-Reportand if the RPLMN is included inplmn-IdentityListstored inVarRLF-Report:

[0353] 3> includerlf-InfoAvailable;

[0354] 2> if the UE has MBSFN logged measurements available for E-UTRA and if the RPLMN is included inplmn-IdentityListstored inVarLogMeasReportand if T330 is not running:

[0355] 3> includelogMeasAvailableMBSFN;

[0356] 2> else if the UE has logged measurements available for E-UTRA and if the RPLMN is included inplmn-IdentityListstored inVarLogMeasReport:

[0357] 3> include thelogMeasAvailable;

[0358] 3> if Bluetooth measurement results are included in the logged measurements the UE has available:

[0359] 4> includelogMeasAvailableBT;

[0360] 3> if WLAN measurement results are included in the logged measurements the UE has available:

[0361] 4> includelogMeasAvailableWLAN;

[0362] 2> if the UE has connection establishment failure information available inVarConnEstFailReportand if the RPLMN is equal toplmn-Identitystored inVarConnEstFailReport:

[0363] 3> includeconnEstFailInfoAvailable;

[0364] 2> if theRRCConnectionReconfigurationmessage includesperCC-GapIndicationRequest:

[0365] 3> includeperCC-GapIndicationListandnumFreqEffective;

[0366] 2> if the frequencies are configured for reduced measurement performance:

[0367] 3> includenumFreqEffectiveReduced;

[0368] 2> if the UE has flight path information available:

[0369] 3> includeflightPathInfoAvailable;

[0370] 2> if the receivedRRCConnectionReconfigurationmessage includednr-SecondaryCellGroupConfig:

[0371] 3> includescg-ConfigResponseNR;

[0372] 2> if the UE is connected to NTN:

[0373] 3> includegnss-validityDurationin accordance with the remaining time of the GNSS validity duration;

[0374] 1> submit theRRCConnectionReconfigurationCompletemessage to lower layers for transmission;

[0375] 1> if MAC successfully completes the random access procedure; or

[0376] 1> if MAC indicates the successful reception of a PDCCH transmission addressed to C-RNTI and ifrach-Skipis configured:

[0377] 2> stop timer T304;

[0378] 2> ifdaps-HOis configured for any DRB:

[0379] 3> stop timer T310 for the source PCell, if running;

[0380] 3> for each DAPS bearer trigger UL data switching;

[0381] 2> releaserach-Skip;

[0382] 2> apply the parts of the CQI reporting configuration, the scheduling request configuration and the sounding RS configuration that do not require the UE to know the SFN of the target PCell, if any;

[0383] 2> apply the parts of the measurement and the radio resource configuration that require the UE to know the SFN of the target PCell (e.g. measurement gaps, periodic CQI reporting, scheduling request configuration, sounding RS configuration), if any, upon acquiring the SFN of the target PCell;

[0384] - Whenever the UE shall setup or reconfigure a configuration in accordance with a field that is received it applies the new configuration, except for the cases addressed by the above statements.

[0385] 2> if the UE is configured to provide IDC indications:

[0386] 3> if the UE has initiated the transmission of anInDeviceCoexIndicationmessage during the last 1 second preceding reception of theRRCConnectionReconfigurationmessage includingmobilityControlInfo; or

[0387] 3> if theRRCConnectionReconfigurationmessage is applied due to a conditional reconfiguration execution and the UE has initiated transmission of anInDeviceCoexIndicationmessage since it was configured to do so in accordance with 5.6.9.2:

[0388] 4> initiate transmission of theInDeviceCoexIndicationmessage in accordance with 5.6.9.3;

[0389] 2> if the UE is configured to provide power preference indications, overheating assistance information, SPS assistance information, delay budget report or maximum bandwidth preference indications:

[0390] 3> if the UE has initiated the transmission of aUEAssistanceInformationmessage during the last 1 second preceding reception of theRRCConnectionReconfigurationmessage includingmobilityControlInfo; or

[0391] 3> if theRRCConnectionReconfigurationmessage is applied due to a conditional reconfiguration execution, and the UE has initiated transmission of aUEAssistanceInformationmessage for the corresponding cell group since it was configured to do so:

[0392] 4> initiate transmission of theUEAssistanceInformationmessage;

[0393] Reception of theRRCConnectionReestablishmentby theUE

[0394] Prior to this, lower layer signalling is used to allocate a C-RNTI.

[0395] The UE shall:

[0396] 1> stop timer T301;

[0397] 1> consider the current cell to be the PCell;

[0398] 1> except for a NB-IoT UE for which AS security has not been activated:

[0399] 2> if SRB1 was configured with NR PDCP and the UE is connected to EPC:

[0400] 3> for SRB1, release the NR PDCP entity and establish an E-UTRA PDCP entity with the current (MCG) security configuration;

[0401] The UE applies the LTE ciphering and integrity protection algorithms that are equivalent to the previously configured NR security algorithms.

[0402] 2> else:

[0403] 3> for SRB1, re-establish the PDCP entity;

[0404] 2> re-establish RLC for SRB1;

[0405] 2> perform the radio resource configuration procedure in accordance with the receivedradioResourceConfigDedicated;

[0406] 2> resume SRB1;

[0407] E-UTRAN should not transmit any message on SRB1 prior to receiving theRRCConnectionReestablishmentCompletemessage.

[0408] 2> if UE is connected to EPC, update the KeNBkey based on the KASMEkey to which the current KeNBis associated, using thenextHopChainingCountvalue indicated in theRRCConnectionReestablishmentmessage;

[0409] 2> else if UE is connected to 5GC, update the KeNBkey based on the KAMFkey to which the current KeNBis associated, using thenextHopChainingCountvalue indicated in theRRCConnectionReestablishmentmessage;

[0410] 2> store thenextHopChainingCountvalue;

[0411] 2> derive the KRRCintkey associated with the previously configured integrity algorithm;

[0412] 2> derive the KRRCenckey and the KUPenckey associated with the previously configured ciphering algorithm;

[0413] 2> if connected as an RN; or

[0414] 2> if capable of user plane integrity protection:

[0415] 3> derive the KUPintkey associated with the previously configured integrity algorithm;

[0416] 2> configure lower layers to activate integrity protection using the previously configured algorithm and the KRRCintkey immediately, i.e., integrity protection shall be applied to all subsequent messages received and sent by the UE, including the message used to indicate the successful completion of the procedure;

[0417] 2> if connected as an RN:

[0418] 3> configure lower layers to apply integrity protection using the previously configured algorithm and the KUPintkey, for subsequently resumed or subsequently established DRBs that are configured to apply integrity protection, if any;

[0419] 2> configure lower layers to apply ciphering using the previously configured algorithm, the KRRCenckey and the KUPenckey immediately, i.e., ciphering shall be applied to all subsequent messages received and sent by the UE, including the message used to indicate the successful completion of the procedure;

[0420] 2> if the UE is not a NB-IoT UE:

[0421] 3> set the content ofRRCConnectionReestablishmentCompletemessage as follows:

[0422] 4> if the UE has radio link failure or handover failure information available inVarRLF-Reportand if the RPLMN is included inplmn-IdentityListstored inVarRLF-Report:

[0423] 5> include therlf-InfoAvailable;

[0424] 4> if the UE has MBSFN logged measurements available for E-UTRA and if the RPLMN is included inplmn-IdentityListstored inVarLogMeasReportand if T330 is not running:

[0425] 5> includelogMeasAvailableMBSFN;

[0426] 4> else if the UE has logged measurements available for E-UTRA and if the RPLMN is included inplmn-IdentityListstored inVarLogMeasReport:

[0427] 5> include thelogMeasAvailable;

[0428] 5> if Bluetooth measurement results are included in the logged measurements the UE has available:

[0429] 6> include thelogMeasAvailableBT;

[0430] 5> if WLAN measurement results are included in the logged measurements the UE has available:

[0431] 6> include thelogMeasAvailableWLAN;

[0432] 4> if the UE has connection establishment failure information available inVarConnEstFailReportand if the RPLMN is equal toplmn-Identitystored inVarConnEstFailReport:

[0433] 5> include theconnEstFailInfoAvailable;

[0434] 4> if the UE has flight path information available and if the UE is connected to EPC:

[0435] 5> includeflightPathInfoAvailable;

[0436] 3> perform the measurement related actions;

[0437] 3> perform the measurement identity autonomous removal;

[0438] Hereinafter technical features related to UE information procedure is described.

[0439] FIG. 13 shows an example of UE information procedure.

[0440] The UE information procedure is used by E-UTRAN to request the UE to report information.

[0441] E-UTRAN initiates the procedure by sending theUEInformationRequestmessage. E-UTRAN should initiate this procedure only after successful security activation.

[0442] Reception of theUEInformationRequestmessage

[0443] Upon receiving theUEInformationRequestmessage, the UE shall, only after successful security activation:

[0444] 1> except for NB-IoT, ifflightPathInfoReqfield is present and the UE has flight path information available:

[0445] 2> include theflightPathInfoReportand set it to include the list of waypoints along the flight path;

[0446] 2> if theincludeTimeStampis set to TRUE:

[0447] 3> set the fieldtimeStampto the time when UE intends to arrive to each waypoint if this information is available at the UE;

[0448] 1> for NB-IoT, ifanr-ReportReqis set totrueand the UE hasmeasResultListavailable inVarANR-MeasReport-NB:

[0449] 2> set theanr-MeasReportin theUEInformationResponsemessage as follows:

[0450] 3> if the global cell identity of the PCell is different fromservCellIdentityin theVarANR-MeasReport-NB;

[0451] 4> include theservCellIdentityand set it to the value ofservCellIdentityin theVarANR-MeasReport-NB;

[0452] 3> setmeasResultServCellto the value ofmeasResultServCellin theVarANR-MeasReport-NB;

[0453] 3> setrelativeTimeStampto the value ofrelativeTimeStampin theVarANR-MeasReport-NB;

[0454] 3> setmeasResultListto the value ofmeasResultListin theVarANR-MeasReport-NB;

[0455] 2> discard theVarANR-MeasReport-NBupon successful delivery of theUEInformationResponsemessage confirmed by lower layers;

[0456] 1> except for NB-IoT, if thecoarseLocationReqis set to true:

[0457] 2> if available, include thecoarseLocationInfo;

[0458] 1> if thelogMeasReportis included in theUEInformationResponse:

[0459] 2> submit theUEInformationResponsemessage to lower layers for transmission via SRB2;

[0460] 2> discard the logged measurement entries included in thelogMeasInfoListfromVarLogMeasReportupon successful delivery of theUEInformationResponsemessage confirmed by lower layers;

[0461] 1> else:

[0462] 2> submit theUEInformationResponsemessage to lower layers for transmission via SRB1;

[0463] Meanwhile, as per the Electronic Communications Committee (ECC) requirement, with the harmonized technical conditions for mobile / fixed communication networks (MFCN) bands and for spectrum compatibility purpose, there is some spectrum operational restrictions. This can be done using "no-transmit zones (NTZ)", which is defined at a geographical area where aerial UE are not allowed to operate in a certain frequency band. This restriction can be applied to LTE and 5G NR in the following MFCN harmonised bands: 703-733 MHz, 832-862 MHz, 880-915 MHz, 1710-1785 MHz, 1920-1980 MHz, 2500-2570 MHz and 2570-2620 MHz.

[0464] In order to decide on appropriate mobility configuration, and to provide early resource reservation in cells suitable for a handover, the network can utilize the flight path information received from UE. UE can indicate that a flight path is available or updated, and it can send that information with up to 20 waypoints in the flight path information.

[0465] If the network knows the no-transmit zones, it can configure the UE with the suitable configuration, e.g., removal NTZ frequency related configuration when the UE enters NTZ area and re-configuration of NTZ frequency related when the UE leaves NTZ area. However, it is difficult to properly configure the UE without accurate entry and exit information for NTZ zones. In particular, when entering the NTZ area, if the network does not release the operation related to the NTZ frequency, the UE may transmit control / user data through the NTZ frequency in the NTZ area, thereby violating the ECC requirement.

[0466] Therefore, studies for flight path information in a wireless communication system are required.

[0467] Hereinafter, a method for flight path information in a wireless communication system, according to some embodiments of the present disclosure, will be described with reference to the following drawings.

[0468] The following drawings are created to explain specific embodiments of the present disclosure. The names of the specific devices or the names of the specific signals / messages / fields shown in the drawings are provided by way of example, and thus the technical features of the present disclosure are not limited to the specific names used in the following drawings. Herein, a wireless device may be referred to as a user equipment (UE).

[0469] FIG. 14 shows an example of a method for flight path information in a wireless communication system.

[0470] In particular, FIG. 14 shows an example of a method performed by a wireless device in a wireless communication system.

[0471] In step S1401, a wireless device may acquire information related to at least one specific zone in which the wireless device is not allowed to perform transmission.

[0472] For example, the wireless device may receive, from a network, the information related to the at least one specific zone.

[0473] For other example, the information related to the at least one specific zone may be preconfigured within the wireless device.

[0474] For example, the at least one specific zone may include a no-transmit zone (NTZ).

[0475] For example, the wireless device may be not allowed to perform transmission in the at least one specific zone. For example, the wireless device may be not allowed to perform transmission or reception in the at least one specific zone. For example, the wireless device may be not allowed to perform transmission and reception in the at least one specific zone.

[0476] In step S1402, a wireless device may identify a flight path of the wireless device.

[0477] For example, the wireless device may determine or drive the flight path of the wireless device based on a navigation system. For example, the wireless device may determine or drive the flight path of the wireless device based on a current position of the wireless device and a destination position.

[0478] For example, the wireless device may determine a current position of the wireless device based on information related to Global Positioning System (GPS). For another example, the wireless device may calculate the current position based on information from the network.

[0479] In step S1403, a wireless device may transmit the information related to the flight path.

[0480] For example, the information related to the flight path may include information related to whether the flight path passes the at least one specific zone.

[0481] For example, the information related to the flight path may include information related to a time point at which the wireless device enters the at least one specific zone.

[0482] For example, the information related to the flight path may include information related to a time point at which the wireless device leaves the at least one specific zone.

[0483] For example, the information related to the flight path may include information related to a frequency band which is prohibited in the at least one specific zone.

[0484] For example, the information related to the flight path may include information related to a location where the wireless device enters the at least one specific zone.

[0485] For example, the information related to the flight path may include information related to a location where the wireless device leaves the at least one specific zone.

[0486] For example, the information related to the flight path may be included in a radio resource control (RRC) message, a User Equipment (UE) Assistance Information (UAI) message, a UE information response message, and / or a measurement report message.

[0487] For example, the wireless device may transmit information informing that the information related to the flight path is available. For example, the wireless device may receive a request message for the information related to the flight path. For example, the wireless device may trigger transmission of the information related to the flight path upon receiving the request message.

[0488] For example, the wireless device may determine whether the flight path passes the at least one specific zone. The wireless device may trigger transmission of the information related to the flight path upon determining that the flight path passes the at least one specific zone.

[0489] According to some embodiments of the present disclosure, the wireless device may be in communication with at least one of a user equipment, a network, or an autonomous vehicle other than the wireless device.

[0490] Hereinafter, some embodiments of a method related to flight path information about entering and exiting a specific area are described.

[0491] When the aerial UE plans flight path, it can inform the network of the flight path information. If the planned flight paths have one or more specific area, such as NTZ area, the UE can notify additional information related to the specific area. The network can utilize the additional information for mobility configuration (i) to disallow any mobility to the NTZ frequency in the NTZ area, and (ii) to re-reserve network resource related to NTZ frequency when leaving the NTZ area.

[0492] For example, the UE can inform the network of when / where it enters / leaves a specific area.

[0493] - UE may include location information where the UE enters / leaves the specific area

[0494] - UE may include time information when the UE enters / leaves the specific area

[0495] FIG. 15 shows an example of a method related to flight path information about entering and exiting a specific area.

[0496] In step S1501, UE may acquire area information.

[0497] For example, in step S1501-1, network may configure UE with area information.

[0498] >The area information may be related to a block area

[0499] >>In the block area, any UL transmission, e.g., PUCCH, PUSCH, may not be allowed

[0500] >>In the block area, any access operation, e.g., RACH, may not be allowed

[0501] >>In the block area, some of DL signalling may be not transmitted

[0502] >The area information may include location information

[0503] >>Each information may be configured with a specific ID

[0504] >>The location information may include at least one of the following:

[0505] >>>Polygon type information

[0506] >>>>Polygon type information may include ordered series of points for a geographic shape

[0507] >>>Latitude / longitude information

[0508] >>>>Latitude / longitude information may include a point at a specific distance

[0509] >>>>Latitude / longitude information may include degree information

[0510] >>>>Latitude / longitude information may include the direction (vector located in 2D coordinate axes)

[0511] >>>>Coordinate information

[0512] >>>Altitude information

[0513] >>>>Altitude information may include a point at a specific distance

[0514] >>>>Altitude information may include the direction (vector located in 3D coordinate axes)

[0515] >>>>Coordinate information

[0516] >>>Time information

[0517] >>>>Time information may include the time, e.g., UTC time and time offset

[0518] >>>Distance information

[0519] >>>>Distance information may include a reference point

[0520] >>>>Distance information may include a distance from the reference point

[0521] >>>Velocity information

[0522] >>>>Velocity information may include the vertical speed

[0523] >>>>Velocity information may include the horizontal speed

[0524] >>>>Velocity information may include the direction (vector located in 2D / 3D coordinate axes)

[0525] >>>>Coordinate information

[0526] For example, in step S1501-2, the area information may be pre-determined in the specification.

[0527] For example, in step S1501-3, the area information may be pre-configured from the upper layer.

[0528] In step S1502, UE may acquire specific frequency band information.

[0529] For example, in step S1502-1, a network may configure UE with specific frequency band information.

[0530] >The specific frequency band may be related to a block frequency

[0531] >>With the block frequency, any UL transmission, e.g., PUCCH, PUSCH, may not be allowed

[0532] >>With the block frequency, any access operation, e.g., RACH, may not be allowed

[0533] >>With the block frequency, some of DL signalling may not be transmitted

[0534] >The specific frequency may be applied in the block area

[0535] >The specific frequency band information may include a specific frequency(ies) or a specific frequency group(s)

[0536] >The specific frequency band information may include a cell(s) or a cell group(s)

[0537] >The specific frequency band information may include a beam(radio resource)(s) or a beam(radio resource) group(s)

[0538] For example, in step S1502-2, the specific frequency band information may pre-determined in the specification.

[0539] For example, in step S1502-3, the specific frequency band information may pre-configured from the upper layer.

[0540] In step S1503, UE may determine the flight path.

[0541] In step S1504, UE may determine whether the flight path includes a specific area(s) based on the area information.

[0542] >UE may derive the location-related information where the UE enters / leaves the specific area

[0543] >>For example, latitude, longitude and / or altitude

[0544] >>For example, distance information from a certain location

[0545] >>For example, velocity information

[0546] >>For example, vector information based on a certain location

[0547] >>For example, direction information based on a certain location

[0548] >UE may derive the time-related information when the UE enters / leaves the specific area

[0549] >>For example, UTC time information

[0550] >>For example, time offset information from a certain time

[0551] >>For example, time window information, e.g., start time and duration

[0552] >>For example, staying time information, from entering time to leaving time

[0553] >Specific area-related information may consist of location-related information and time-related information

[0554] In step S1505, UE may send a first indication indicating whether it includes the specific area-related information.

[0555] >UE may include the first indication for a certain waypoint, i.e., including the specific area

[0556] >UE may include the first indication for all waypoint

[0557] >UE may send the first indication via RRC message, e.g., UE assistance Information message and measurement report message

[0558] >UE may send the first indication via MAC CE

[0559] In step S1506, UE may receive a second indication indicating whether the UE includes the specific area-related information.

[0560] That is, network may send a second indication indicating whether the UE includes the specific area-related information.

[0561] >Network may send the second indication for the certain waypoint

[0562] >Network may send the second indication for all waypoint

[0563] >Network may send the second indication via RRC message, e.g., UE information request message

[0564] >Network may send the second indication via MAC CE

[0565] In step S1507, UE may include the specific area-related information in the flightpath information derived from step S1504.

[0566] >The specific area-related information may be included in each waypoint

[0567] >The specific area-related information may be included as separate information

[0568] >UE may include the location-related information derived from step 4

[0569] >UE may include the time-related information derived from step 4

[0570] >UE may include the entire specific area based on the area information (step S1501)

[0571] >UE may include the entire specific frequency band based on the specific frequency band information (step S1502)

[0572] >UE may include the UE-capable-specific frequency band information (UE capable block frequency band information)

[0573] >UE may send the flightpath information via RRC message, e.g., UE assistance Information message, UE information response message and measurement report message

[0574] FIG. 16 shows an example of a method related to flight path information including information about entering and exiting a specific area.

[0575] In particular, FIG. 16 shows an example of a method performed by a wireless device in a wireless communication system.

[0576] In step S1601, a wireless device may determine whether the flight path information includes one or more specific area(s).

[0577] In step S1602, based on the determination, a wireless device may transmit the flight path information with the time and / or location information at which the UE enters and / or leaves the specific area(s).

[0578] - Specific Area:

[0579] - UE received specific area related information from network

[0580] - UE has specific area related information

[0581] - Additional information

[0582] -UE indicates whether the time / location information is available

[0583] -UE includes UE capable specific (block) frequency information

[0584] Some of the detailed steps shown in the examples of FIGS. 14, 15, and 16 may not be essential steps and may be omitted. In addition to the steps shown in FIGS. 14, 15, and 16, other steps may be added, and the order of the steps may vary. Some of the above steps may have their own technical meaning.

[0585] Hereinafter, an apparatus for flight path information in a wireless communication system, according to some embodiments of the present disclosure, will be described. Herein, the apparatus may be a wireless device (100 or 200) in FIGS. 2, 3, and 5.

[0586] For example, a wireless device may perform the methods described above. The detailed description overlapping with the above-described contents could be simplified or omitted.

[0587] Referring to FIG. 5, a wireless device 100 may include a processor 102, a memory 104, and a transceiver 106.

[0588] According to some embodiments of the present disclosure, the processor 102 may be configured to be coupled operably with the memory 104 and the transceiver 106.

[0589] The processor 102 may be configured to information related to at least one specific zone in which the wireless device is not allowed to perform transmission. The processor 102 may be configured to identify a flight path of the wireless device. The processor 102 may be configured to control the transceiver 106 to transmit the information related to the flight path. The information related to the flight path may include information related to whether the flight path passes the at least one specific zone.

[0590] For example, the information related to the flight path may include information related to a time point at which the wireless device enters the at least one specific zone.

[0591] For example, the information related to the flight path may include information related to a time point at which the wireless device leaves the at least one specific zone.

[0592] For example, the information related to the flight path may include information related to a frequency band which is prohibited in the at least one specific zone.

[0593] For example, the information related to the flight path may include information related to a location where the wireless device enters the at least one specific zone.

[0594] For example, the information related to the flight path may include information related to a location where the wireless device leaves the at least one specific zone.

[0595] For example, the processor 102 may be configured to control the transceiver 106 to receive, from a network, the information related to the at least one specific zone.

[0596] For example, the information related to the at least one specific zone may be preconfigured within the wireless device.

[0597] For example, the information related to the flight path may be included in a radio resource control (RRC) message, a User Equipment (UE) Assistance Information (UAI) message, a UE information response message, and / or a measurement report message.

[0598] For example, the processor 102 may be configured to control the transceiver 106 to transmit information informing that the information related to the flight path is available.

[0599] For example, the processor 102 may be configured to control the transceiver 106 to receive a request message for the information related to the flight path.

[0600] For example, the processor 102 may be configured to trigger transmission of the information related to the flight path upon receiving the request message.

[0601] For example, the processor 102 may be configured to trigger transmission of the information related to the flight path upon determining that the flight path passes the at least one specific zone.

[0602] For example, the processor 102 may be configured to control the transceiver 106 to be in communication with at least one of a user equipment, a network, or an autonomous vehicle other than the wireless device.

[0603] Hereinafter, a processor for a wireless device for flight path information in a wireless communication system, according to some embodiments of the present disclosure, will be described.

[0604] The processor may be configured to control the wireless device to information related to at least one specific zone in which the wireless device is not allowed to perform transmission. The processor may be configured to control the wireless device to identify a flight path of the wireless device. The processor may be configured to control the wireless device to transmit the information related to the flight path. The information related to the flight path may include information related to whether the flight path passes the at least one specific zone.

[0605] For example, the information related to the flight path may include information related to a time point at which the wireless device enters the at least one specific zone.

[0606] For example, the information related to the flight path may include information related to a time point at which the wireless device leaves the at least one specific zone.

[0607] For example, the information related to the flight path may include information related to a frequency band which is prohibited in the at least one specific zone.

[0608] For example, the information related to the flight path may include information related to a location where the wireless device enters the at least one specific zone.

[0609] For example, the information related to the flight path may include information related to a location where the wireless device leaves the at least one specific zone.

[0610] For example, the processor may be configured to control the wireless device to receive, from a network, the information related to the at least one specific zone.

[0611] For example, the information related to the at least one specific zone may be preconfigured within the wireless device.

[0612] For example, the information related to the flight path may be included in a radio resource control (RRC) message, a User Equipment (UE) Assistance Information (UAI) message, a UE information response message, and / or a measurement report message.

[0613] For example, the processor may be configured to control the wireless device to transmit information informing that the information related to the flight path is available.

[0614] For example, the processor may be configured to control the wireless device to receive a request message for the information related to the flight path.

[0615] For example, the processor may be configured to control the wireless device to trigger transmission of the information related to the flight path upon receiving the request message.

[0616] For example, the processor may be configured to control the wireless device to trigger transmission of the information related to the flight path upon determining that the flight path passes the at least one specific zone.

[0617] For example, the processor may be configured to control the wireless device to be in communication with at least one of a user equipment, a network, or an autonomous vehicle other than the wireless device.

[0618] Hereinafter, a non-transitory computer-readable medium has stored thereon a plurality of instructions for flight path information in a wireless communication system, according to some embodiments of the present disclosure, will be described.

[0619] According to some embodiment of the present disclosure, the technical features of the present disclosure could be embodied directly in hardware, in a software executed by a processor, or in a combination of the two. For example, a method performed by a wireless device in a wireless communication may be implemented in hardware, software, firmware, or any combination thereof. For example, a software may reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, a removable disk, a CD-ROM, or any other storage medium.

[0620] Some example of storage medium is coupled to the processor such that the processor can read information from the storage medium. In the alternative, the storage medium may be integral to the processor. The processor and the storage medium may reside in an ASIC. For other example, the processor and the storage medium may reside as discrete components.

[0621] The computer-readable medium may include a tangible and non-transitory computer-readable storage medium.

[0622] For example, non-transitory computer-readable media may include random access memory (RAM) such as synchronous dynamic random access memory (SDRAM), read-only memory (ROM), non-volatile random access memory (NVRAM), electrically erasable programmable read-only memory (EEPROM), FLASH memory, magnetic or optical data storage media, or any other medium that can be used to store instructions or data structures. Non-transitory computer-readable media may also include combinations of the above.

[0623] In addition, the method described herein may be realized at least in part by a computer-readable communication medium that carries or communicates code in the form of instructions or data structures and that can be accessed, read, and / or executed by a computer.

[0624] According to some embodiment of the present disclosure, a non-transitory computer-readable medium has stored thereon a plurality of instructions. The stored plurality of instructions may be executed by a processor of a wireless device.

[0625] The stored plurality of instructions may cause the wireless device to information related to at least one specific zone in which the wireless device is not allowed to perform transmission. The stored plurality of instructions may cause the wireless device to identify a flight path of the wireless device. The stored plurality of instructions may cause the wireless device to transmit the information related to the flight path. The information related to the flight path may include information related to whether the flight path passes the at least one specific zone.

[0626] For example, the information related to the flight path may include information related to a time point at which the wireless device enters the at least one specific zone.

[0627] For example, the information related to the flight path may include information related to a time point at which the wireless device leaves the at least one specific zone.

[0628] For example, the information related to the flight path may include information related to a frequency band which is prohibited in the at least one specific zone.

[0629] For example, the information related to the flight path may include information related to a location where the wireless device enters the at least one specific zone.

[0630] For example, the information related to the flight path may include information related to a location where the wireless device leaves the at least one specific zone.

[0631] For example, the stored plurality of instructions may cause the wireless device to receive, from a network, the information related to the at least one specific zone.

[0632] For example, the information related to the at least one specific zone may be preconfigured within the wireless device.

[0633] For example, the information related to the flight path may be included in a radio resource control (RRC) message, a User Equipment (UE) Assistance Information (UAI) message, a UE information response message, and / or a measurement report message.

[0634] For example, the stored plurality of instructions may cause the wireless device to transmit information informing that the information related to the flight path is available.

[0635] For example, the stored plurality of instructions may cause the wireless device to receive a request message for the information related to the flight path.

[0636] For example, the stored plurality of instructions may cause the wireless device to trigger transmission of the information related to the flight path upon receiving the request message.

[0637] For example, the stored plurality of instructions may cause the wireless device to trigger transmission of the information related to the flight path upon determining that the flight path passes the at least one specific zone.

[0638] According to some embodiments of the present disclosure, the stored plurality of instructions may cause the wireless device to be in communication with at least one of a user equipment, a network, or an autonomous vehicle other than the wireless device.

[0639] Hereinafter, a method performed by a base station (BS) for flight path information in a wireless communication system, according to some embodiments of the present disclosure, will be described.

[0640] The BS may receive, from a wireless device, information related to a flight path of the wireless device. The information related to the flight path may include information related to whether the flight path passes at least one specific zone. The wireless device may not be allowed to perform transmission in the at least one specific zone.

[0641] Hereinafter, a base station (BS) for flight path information in a wireless communication system, according to some embodiments of the present disclosure, will be described.

[0642] The BS may include a transceiver, a memory, and a processor operatively coupled to the transceiver and the memory.

[0643] The processor may be configured to control the transceiver to receive, from a wireless device, information related to a flight path of the wireless device. The information related to the flight path may include information related to whether the flight path passes at least one specific zone. The wireless device may not be allowed to perform transmission in the at least one specific zone.

[0644] The present disclosure can have various advantageous effects.

[0645] According to some embodiments of the present disclosure, a wireless device could efficiently provide flight path information related to the NTZ in a wireless communication system.

[0646] For example, by including additional information with location / time related to the specific area in the flight path information, the network can proactively configure the UE with appropriate configuration considering the characteristic of the specific area. In particular, when the UE is planned to go into a no-transmit zone, the network can disallow mobility related to the NTZ frequency in advance. The network can utilize the additional information in T1 / D1 condition configuration as well.

[0647] In other words, the wireless device can include information related to whether the flight path passes through the NTZ in the flight path information. Therefore, the network can efficiently configure the wireless device.

[0648] According to some embodiments of the present disclosure, the wireless communication system could provide an efficient solution for flight path information about entering and exiting a specific area.

[0649] Advantageous effects which can be obtained through specific embodiments of the present disclosure are not limited to the advantageous effects listed above. For example, there may be a variety of technical effects that a person having ordinary skill in the related art can understand and / or derive from the present disclosure. Accordingly, the specific effects of the present disclosure are not limited to those explicitly described herein, but may include various effects that may be understood or derived from the technical features of the present disclosure.

[0650] Claims in the present disclosure can be combined in a various way. For instance, technical features in method claims of the present disclosure can be combined to be implemented or performed in an apparatus, and technical features in apparatus claims can be combined to be implemented or performed in a method. Further, technical features in method claim(s) and apparatus claim(s) can be combined to be implemented or performed in an apparatus. Further, technical features in method claim(s) and apparatus claim(s) can be combined to be implemented or performed in a method. Other implementations are within the scope of the following claims.

Claims

1.A method performed by a wireless device in a wireless communication system, the method comprising:acquiring information related to at least one specific zone in which the wireless device is not allowed to perform transmission;identifying a flight path of the wireless device; andtransmitting the information related to the flight path,wherein the information related to the flight path includes information related to whether the flight path passes the at least one specific zone.2.The method of claim 1,wherein the information related to the flight path includes information related to a time point at which the wireless device enters the at least one specific zone.3.The method of claim 1,wherein the information related to the flight path includes information related to a time point at which the wireless device leaves the at least one specific zone.4.The method of claim 1,wherein the information related to the flight path includes information related to a frequency band which is prohibited in the at least one specific zone.5.The method of claim 1,wherein the information related to the flight path includes information related to a location where the wireless device enters the at least one specific zone.6.The method of claim 1,wherein the information related to the flight path includes information related to a location where the wireless device leaves the at least one specific zone.7.The method of claim 1, wherein the method further comprising:receiving, from a network, the information related to the at least one specific zone.8.The method of claim 1,wherein the information related to the at least one specific zone is preconfigured within the wireless device.9.The method of claim 1,wherein the information related to the flight path is included in a radio resource control (RRC) message, a User Equipment (UE) Assistance Information (UAI) message, a UE information response message, and / or a measurement report message.10.The method of claim 1, wherein the method further comprising:transmitting information informing that the information related to the flight path is available.11.The method of claim 10, wherein the method further comprising:receiving a request message for the information related to the flight path.12.The method of claim 11, wherein the method further comprising:triggering transmission of the information related to the flight path upon receiving the request message.13.The method of claim 1, wherein the method further comprising:triggering transmission of the information related to the flight path upon determining that the flight path passes the at least one specific zone.14.The method of claim 1,wherein the wireless device is in communication with at least one of a user equipment, a network, or an autonomous vehicle other than the wireless device.15.A wireless device in a wireless communication system comprising:at least one transceiver;at least one memory; andat least one processor operatively coupled to the at least one transceiver and the at least one memory, and adapted to:acquire information related to at least one specific zone in which the wireless device is not allowed to perform transmission;identify a flight path of the wireless device; andtransmit the information related to the flight path,wherein the information related to the flight path includes information related to whether the flight path passes the at least one specific zone.16.The wireless device of claim 15,wherein the information related to the flight path includes information related to a time point at which the wireless device enters the at least one specific zone.17.The wireless device of claim 15,wherein the information related to the flight path includes information related to a time point at which the wireless device leaves the at least one specific zone.18.The wireless device of claim 15,wherein the information related to the flight path includes information related to a frequency band which is prohibited in the at least one specific zone.19.The wireless device of claim 15,wherein the information related to the flight path includes information related to a location where the wireless device enters the at least one specific zone.20.The wireless device of claim 15,wherein the information related to the flight path includes information related to a location where the wireless device leaves the at least one specific zone.21.The wireless device of claim 15, wherein the at least one processor is further adapted to:receive, from a network, the information related to the at least one specific zone.22.The wireless device of claim 15,wherein the information related to the at least one specific zone is preconfigured within the wireless device.23.The wireless device of claim 15,wherein the information related to the flight path is included in a radio resource control (RRC) message, a User Equipment (UE) Assistance Information (UAI) message, a UE information response message, and / or a measurement report message.24.The wireless device of claim 15, wherein the at least one processor is further adapted to:transmit information informing that the information related to the flight path is available.25.The wireless device of claim 24, wherein the at least one processor is further adapted to:receive a request message for the information related to the flight path.26.The wireless device of claim 25, wherein the at least one processor is further adapted to:trigger transmission of the information related to the flight path upon receiving the request message.27.The wireless device of claim 15, wherein the at least one processor is further adapted to:trigger transmission of the information related to the flight path upon determining that the flight path passes the at least one specific zone.28.The wireless device of claim 15,wherein the wireless device is in communication with at least one of a user equipment, a network, or an autonomous vehicle other than the wireless device.29.A processor for a wireless device in a wireless communication system, wherein the processor is configured to control the wireless device to perform operations comprising:acquiring information related to at least one specific zone in which the wireless device is not allowed to perform transmission;identifying a flight path of the wireless device; andtransmitting the information related to the flight path,wherein the information related to the flight path includes information related to whether the flight path passes the at least one specific zone.30.A non-transitory computer-readable medium having stored thereon a plurality of instructions, which, when executed by a processor of a wireless device, cause the wireless device to perform operations, the operations comprises,acquiring information related to at least one specific zone in which the wireless device is not allowed to perform transmission;identifying a flight path of the wireless device; andtransmitting the information related to the flight path,wherein the information related to the flight path includes information related to whether the flight path passes the at least one specific zone.31.A method performed by a base station in a wireless communication system, the method comprising,receiving, from a wireless device, information related to a flight path of the wireless device,wherein the information related to the flight path includes information related to whether the flight path passes at least one specific zone, andwherein the wireless device is not allowed to perform transmission in the at least one specific zone.32.A base station in a wireless communication system comprising:at least one transceiver;at least one memory; andat least one processor operatively coupled to the at least one transceiver and the at least one memory, and adapted to:receive, from a wireless device, information related to a flight path of the wireless device,wherein the information related to the flight path includes information related to whether the flight path passes at least one specific zone, andwherein the wireless device is not allowed to perform transmission in the at least one specific zone.

Images