Method and apparatus for uplink frequency selection based on altitude in a wireless communication system

Abstract

A method and apparatus for uplink frequency selection based on altitude in a wireless communication system is provided. The method comprises: receiving information related to multiple uplink frequencies and an altitude threshold; identifying a current altitude of the wireless device; selecting an uplink frequency among the multiple uplink frequencies based on the current altitude of the wireless device and the altitude threshold; and performing uplink transmission based on the selected uplink frequency.

Description

METHOD AND APPARATUS FOR UPLINK FREQUENCY SELECTION BASED ON ALTITUDE IN A WIRELESS COMMUNICATION SYSTEM

[0001] The present disclosure relates to a method and apparatus for uplink frequency selection based on altitude 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] In the No-Transmit Zone (NTZ), airborne UE cannot perform uplink transmission using a certain frequency / band. If the certain frequency is allowed to use on the ground, operator want to use it for UEs on the ground even in NTZ.

[0006] However, if the uplink frequency of a cell deployed in NTZ is not allowed to use for airborne UE, and if there is no alternative cell, airborne UEs would lose the RRC connection or cannot perform initial access.

[0007] Therefore, studies for uplink frequency selection based on altitude in a wireless communication system are required.

[0008] In an aspect, a method performed by a wireless device in a wireless communication system is provided. The method comprises: receiving information related to multiple uplink frequencies and an altitude threshold; identifying a current altitude of the wireless device; selecting an uplink frequency among the multiple uplink frequencies based on the current altitude of the wireless device and the altitude threshold; and performing uplink transmission based on the selected uplink frequency.

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

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

[0011] According to some embodiments of the present disclosure, the wireless device could efficiently perform uplink frequency selection based on altitude.

[0012] For example, though the normal uplink frequency of a cell deployed in NTZ is not allowed to use for airborne UE, airborne UEs can perform uplink transmission using the aerial uplink frequency.

[0013] In other words, by performing uplink frequency selection according to the altitude of the wireless device, the prohibited uplink frequency may not be used.

[0014] According to some embodiments of the present disclosure, the wireless communication system could provide an efficient solution for uplink frequency selection based on altitude.

[0015] 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.

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

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

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

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

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

[0021] 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.

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

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

[0024] FIG. 10 shows an example of a Measurement Report procedure.

[0025] FIG. 11 shows an example of a UE Information procedure.

[0026] FIG. 12 shows an example of a method for uplink frequency selection based on altitude in a wireless communication system, according to some embodiments of the present disclosure.

[0027] FIG. 13 show an example of uplink frequency selection procedure based on altitude.

[0028] 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.

[0029] 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.

[0030] 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.

[0031] 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".

[0032] 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".

[0033] 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".

[0034] 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".

[0035] 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".

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

[0037] 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.

[0038] 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.

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

[0040] 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.

[0041] 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).

[0042] 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.

[0043] 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.

[0044] 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.

[0045] 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.

[0046] 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.

[0047] 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.

[0048] 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.

[0049] 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.

[0050] 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.

[0051] 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.

[0052] 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.

[0053] 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.

[0054] 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.

[0055] 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.

[0056] 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.

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

[0058] 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.

[0059] 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.

[0060] 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.

[0061] 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.

[0062] 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.

[0063] 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.

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

[0065] 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.

[0066] 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.

[0067] 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.

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

[0069] 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.

[0070] 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.

[0071] 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.

[0072] 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.

[0073] 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.

[0074] 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.

[0075] 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.

[0076] 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).

[0077] 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.

[0078] 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.

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

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

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

[0082] 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.

[0083] 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.

[0084] 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.

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

[0086] 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.

[0087] 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.

[0088] 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.

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

[0090] 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.

[0091] 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.

[0092] 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.

[0093] 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.

[0094] 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.

[0095] 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.

[0096] 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.

[0097] 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.

[0098] 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.

[0099] 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.

[0100] 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).

[0101] 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.

[0102] 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.

[0103] 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.

[0104] 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).

[0105] 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.

[0106] 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.

[0107] 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.

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

[0109] 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).

[0110] 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.

[0111] 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.

[0112] uNslotsymbNframe,uslotNsubframe,uslot01410111420221440431480841416016

[0113] 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.

[0114] uNslotsymbNframe,uslotNsubframe,uslot212404

[0115] 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.

[0116] 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.

[0117] 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).

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

[0119] 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).

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

[0121] 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.

[0122] 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.

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

[0124] 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.

[0125] 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.

[0126] Hereinafter, technical features related to altitude reporting are described. Section 5.5.5 of 3GPP TS 36.331 v17.3.0 may be referred.

[0127] FIG. 10 shows an example of a Measurement Report procedure.

[0128] In FIG. 10, UE may transmit a measurement report to EUTRAN.

[0129] The purpose of this procedure is to transfer measurement results from the UE to E-UTRAN. The UE shall initiate this procedure only after successful security activation.

[0130] For themeasIdfor which the measurement reporting procedure was triggered, the UE shall set themeasResultswithin theMeasurementReportmessage as follows:

[0131] 1> set themeasIdto the measurement identity that triggered the measurement reporting;

[0132] 1> set themeasResultPCellto include the quantities of the PCell;

[0133] 1> set themeasResultServFreqListto include for each E-UTRA SCell that is configured, if any, withinmeasResultSCellthe quantities of the concerned SCell, if available according to performance requirements, except ifpurposefor thereportConfigassociated with themeasIdthat triggered the measurement reporting is set toreportLocation;

[0134] 1> if thereportConfigassociated with themeasIdthat triggered the measurement reporting includesreportAddNeighMeas:

[0135] 2> for each E-UTRA serving frequency for whichmeasObjectIdis referencedin themeasIdList, other than the frequency corresponding with themeasIdthat triggered the measurement reporting:

[0136] 3> set themeasResultServFreqListto include withinmeasResultBestNeighCellthephysCellIdand the quantities of the best non-serving cell, based on RSRP, on the concerned serving frequency;

[0137] 1> if thetriggerTypeis set toevent; and if the corresponding measObject concerns NR; and ifeventIdis set toeventB1-NRoreventB2-NR; or

[0138] 1> if thetriggerTypeis set toevent; and ifeventIdis set toeventA3oreventA4oreventA5:

[0139] 2> if (NG)EN-DC is configured, and ifpurposefor thereportConfigorreportConfigInterRATassociated with themeasIdthat triggered the measurement reporting is set to a value other thanreportLocationor ifpurposeis not configured:

[0140] 3> set themeasResultServFreqListNRto include for each NR serving frequency that the UE is configured to measure if any, the following:

[0141] 4> setmeasResultSCellto include the available results of the NR serving cell;

[0142] 4> if thereportConfigassociated with themeasIdthat triggered the measurement reporting includesreportAddNeighMeasand ifeventIdis set toeventA3oreventA4oreventA5:

[0143] 5> setmeasResultBestNeighCellto include the available results, of the non-serving cell with the highest sorting quantity determined;

[0144] 3> for each (serving or neighbouring) cell for which the UE reports results according to the previous, additionally include available beam results according to the following:

[0145] 4> ifmaxReportRS-Indexis configured, setmeasResultRS-IndexListto include available results, of up tomaxReportRS-Indexbeams, ordered based on the quantity;

[0146] 1> if there is at least one applicable neighbouring cell to report:

[0147] 2> set themeasResultNeighCellsto include the best neighbouring cells up tomaxReportCellsin accordance with the following:

[0148] 3> if thetriggerTypeis set toevent:

[0149] 4> include the cells included in thecellsTriggeredListas defined within theVarMeasReportListfor thismeasId;

[0150] 3> else:

[0151] 4> include the applicable cells for which the new measurement results became available since the last periodical reporting or since the measurement was initiated or reset;

[0152] The reliability of the report (i.e. the certainty it contains the strongest cells on the concerned frequency) depends on the measurement configuration i.e. thereportInterval.

[0153] 3> for each cell that is included in themeasResultNeighCells, include thephysCellId;

[0154] 3> if thetriggerTypeis set toevent; or thepurposeis set toreportStrongestCellsor toreportStrongestCellsForSON:

[0155] 4> for each included cell, include the layer 3 filtered measured results in accordance with thereportConfigfor thismeasId, ordered as follows:

[0156] 5> if themeasObjectassociated with thismeasIdconcerns E-UTRA:

[0157] 6> set themeasResultto include the quantity(ies) indicated in thereportQuantitywithin the concernedreportConfig;

[0158] 6> sort the included cells in order of decreasingtriggerQuantity, i.e. the best cell is included first;

[0159] 5> if themeasObjectassociated with thismeasIdconcerns NR:

[0160] 6> set themeasResultCellto include the quantity(ies) indicated in thereportQuantityCellNRwithin the concernedreportConfig;

[0161] 6> ifmaxReportRS-IndexandreportQuantityRS-IndexNRare configured, setmeasResultRS-IndexListto include the result of the best beam ifthreshRS-Indexis included in theVarMeasConfigfor the correspondingmeasObject, and the remaining beams whose quantity is abovethreshRS-Index, up tomaxReportRS-Indexbeams in total:

[0162] 7> order beams based on the sorting quantity;

[0163] 7> for each included beam:

[0164] 8> includessbIndex;

[0165] 8> ifreportRS-IndexResultsNRis set to TRUE, for each quantity indicated, include the corresponding measurement result inmeasResultSSB-Indexfor eachssb-Index;

[0166] 6> sort the included cells in order of decreasing sorting quantity;

[0167] 5> if themeasObjectassociated with thismeasIdconcerns UTRA FDD and ifReportConfigInterRATincludes thereportQuantityUTRA-FDD:

[0168] 6> set themeasResultto include the quantities indicated by thereportQuantityUTRA-FDDin order of decreasingmeasQuantityUTRA-FDDwithin thequantityConfig, i.e. the best cell is included first;

[0169] 5> if themeasObjectassociated with thismeasIdconcerns UTRA FDD and ifReportConfigInterRATdoes not include thereportQuantityUTRA-FDD; or

[0170] 5> if themeasObjectassociated with thismeasIdconcerns UTRA TDD, GERAN or CDMA2000:

[0171] 6> set themeasResultto the quantity as configured for the concerned RAT within thequantityConfigin order of either decreasing quantity for UTRA and GERAN or increasing quantity for CDMA2000pilotStrength, i.e. the best cell is included first;

[0172] 3> else if thepurposeis set toreportCGIand the correspondingmeasObjectconcerns a RAT other than NR:

[0173] 4> if the mandatory present fields of thecgi-Infofor the cell indicated by thecellForWhichToReportCGIin the associatedmeasObjecthave been obtained:

[0174] 5> if theincludeMultiBandInfois configured:

[0175] 6> include thefreqBandIndicator;

[0176] 6> if the cell broadcasts themultiBandInfoList, include themultiBandInfoList;

[0177] 6> if the cell broadcasts thefreqBandIndicatorPriority, include thefreqBandIndicatorPriority;

[0178] 5> if the cell broadcasts a CSG identity:

[0179] 6> include thecsg-Identity;

[0180] 6> include thecsg-MemberStatusand set it tomemberif the cell is a CSG member cell;

[0181] 5> if thesi-RequestForHOis configured within thereportConfigassociated with thismeasId:

[0182] 6> include thecgi-Infocontaining all the fields other than theplmn-IdentityListthat have been successfully acquired;

[0183] 6> include, within thecgi-Info, the fieldplmn-IdentityListin accordance with the following:

[0184] 7> if the cell is a CSG member cell, determine the subset of the PLMN identities, starting from the second entry of PLMN identities in the broadcast information, that meet the following conditions:

[0185] a) equal to the RPLMN or an EPLMN; and

[0186] b) the Permitted CSG list of the UE includes an entry comprising of the concerned PLMN identity and the CSG identity broadcast by the cell;

[0187] 7> if the subset of PLMN identities determined according to the previous includes at least one PLMN identity, include theplmn-IdentityListand set it to include this subset of the PLMN identities;

[0188] 7> if the cell is a CSG member cell, include theprimaryPLMN-Suitableif the primary PLMN meets conditions a) and b) specified above;

[0189] 7> if the cell does not broadcastcsg-Identityand the UE is capable of reporting theplmn-IdentityListfrom cells not broadcastingcsg-Identity:

[0190] 8> include in the plmn-IdentityList the list of identities starting from the second entry of PLMN identities in the broadcast information;

[0191] 5> else:

[0192] 6> include thecgi-Infocontaining all the fields that have been successfully acquired and in accordance with the following:

[0193] 7> include in theplmn-IdentityListthe list of identities starting from the second entry of PLMN Identities in the broadcast information;

[0194] 4> if thecellAccessRelatedInfoList-5GChas been acquired:

[0195] 5> includecgi-Info-5GC;

[0196] The UE may include thecgi-Info-5GCeven when the N1 mode is disabled.

[0197] 3> else if thepurposeis set toreportCGIand the correspondingmeasObjectconcerns NR RAT:

[0198] 4> if the Cell information ofcgi-Infofor the cell indicated by thecellForWhichToReportCGIin the associatedmeasObjecthas been obtained:

[0199] 5> includeplmn-IdentityInfoListincludingplmn-IdentityList,trackingAreaCode(if available),ran-AreaCode(if available) andcellIdentityfor each entry of theplmn-IdentityInfoList;

[0200] 5> includefrequencyBandListif broadcasted;

[0201] 5> for each entry inplmn-IdentityInfoList, if thegNB-ID-Lengthis broadcasted:

[0202] 6> includegNB-ID-Length;

[0203] 4> else if MIB associated with the concernedmeasObjectindicates that SIB1 is not broadcast:

[0204] 5> include thenoSIB1field;

[0205] 1> for the cells included according to the previous (i.e. covering the PCell, the SCells, the best non-serving cells on serving frequencies as well as neighbouring EUTRA cells) include results according to the extended RSRQ if corresponding results are available according to the associated performance requirements;

[0206] 1> if there is at least one applicable CSI-RS resource to report:

[0207] 2> set themeasResultCSI-RS-Listto include the best CSI-RS resources up tomaxReportCellsin accordance with the following:

[0208] 3> if thetriggerTypeis set toevent:

[0209] 4> include the CSI-RS resources included in thecsi-RS-TriggeredListas defined within theVarMeasReportListfor thismeasId;

[0210] 3> else:

[0211] 4> include the applicable CSI-RS resources for which the new measurement results became available since the last periodical reporting or since the measurement was initiated or reset;

[0212] The reliability of the report (i.e. the certainty it contains the strongest CSI-RS resources on the concerned frequency) depends on the measurement configuration i.e. thereportInterval.

[0213] 3> for each CSI-RS resource that is included in themeasResultCSI-RS-List:

[0214] 4> include themeasCSI-RS-Id;

[0215] 4> include the layer 3 filtered measured results in accordance with thereportConfigfor thismeasId, ordered as follow:

[0216] 5> set thecsi-RSRP-Resultto include the quantity indicated in thereportQuantitywithin the concernedreportConfigin order of decreasingtriggerQuantityCSI-RS, i.e. the best CSI-RS resource is included first;

[0217] 4> ifreportCRS-Measis set totruewithin the associatedreportConfig, and the cell indicated byphysCellIdof this CSI-RS resource is not a serving cell:

[0218] 5> set themeasResultNeighCellsto include the cell indicated byphysCellIdof this CSI-RS resource, and include thephysCellId;

[0219] 5> set thersrpResultto include the RSRP of the concerned cell, if available;

[0220] 5> set thersrqResultto include the RSRQ of the concerned cell, if available;

[0221] 1> if theue-RxTxTimeDiffPeriodicalis configured within the correspondingreportConfigfor thismeasId;

[0222] 2> set theue-RxTxTimeDiffResultto the measurement result provided by lower layers;

[0223] 2> set thecurrentSFN;

[0224] 1> if themeasRSSI-ReportConfigis configured within the correspondingreportConfigfor thismeasId:

[0225] 2> set therssi-Resultto the average of sample value(s) provided by lower layers in thereportInterval;

[0226] 2> set thechannelOccupancyto the rounded percentage of sample values which are beyond to thechannelOccupancyThresholdwithin all the sample values in thereportInterval;

[0227] 1> if themeasRSSI-ReportConfigNRis configured within the correspondingreportConfigInterRATfor thismeasId:

[0228] 2> set therssi-ResultNRto the average of sample value(s) provided by lower layers in thereportInterval;

[0229] 2> set thechannelOccupancyNRto the rounded percentage of sample values which are beyond to thechannelOccupancyThresholdNRwithin all the sample values in thereportInterval;

[0230] 1> if uplink PDCP delay results are available:

[0231] 2> set theul-PDCP-DelayResultListto include the uplink PDCP delay results available;

[0232] 1> if uplink PDCP delay value results are available:

[0233] 2> set theul-PDCP-DelayValueResultListto include the corresponding average uplink PDCP delay values;

[0234] 1> if theincludeLocationInfois configured in the correspondingreportConfigfor thismeasIdor ifpurposefor thereportConfigassociated with themeasIdthat triggered the measurement reporting is set toreportLocation; and detailed location information that has not been reported is available, set the content of thelocationInfoas follows:

[0235] 2> include thelocationCoordinates;

[0236] 2> if available, include thegnss-TOD-msec, except ifpurposefor thereportConfigassociated with themeasIdthat triggered the measurement reporting is set toreportLocation;

[0237] 2> include theverticalVelocityInfo, if available;

[0238] 1> if thecoarseLocationReqis set totruein the correspondingreportConfigfor thismeasId:

[0239] 2> if available, include thecoarseLocationInfo;

[0240] 1> if theincludeWLAN-Measis configured in the correspondingreportConfigfor thismeasId, set themeasResultsas follows:

[0241] 2> if available, include thelogMeasResultListWLAN, in order of decreasing RSSI for WLAN APs;

[0242] 1> if theincludeBT-Measis configured in the correspondingreportConfigfor thismeasId, set themeasResultsas follows:

[0243] 2> if available, include thelogMeasResultListBT, in order of decreasing RSSI for Bluetooth beacons;

[0244] 1> if theincludeUncomBarPreMeasis configured in the correspondingreportConfigfor thismeasIdand ifincludeUncomBarPreMeasis set totrue, set themeasResultsas follows:

[0245] 2> if available, include theuncomBarPreMeasResult;

[0246] 1> if thereportSSTD-Measis set totrueorpSCellwithin the correspondingreportConfigfor thismeasId:

[0247] 2> set themeasResultSSTDto the measurement results provided by lower layers;

[0248] 1> if thereportSFTD-Measis set toneighborCellsorpSCellwithin the correspondingreportConfigInterRATfor thismeasId, for each applicable cell for which results are available:

[0249] 2> setsfn-OffsetResultandframeBoundaryOffsetResultto the measurement results provided by lower layers;

[0250] 2> if thess-rsrpin thereportQuantityCellNRis set toTRUEwithin the correspondingreportConfigInterRATfor thismeasId:

[0251] 3> includersrpResultset to the RSRP of the concerned cell;

[0252] 1> if there is at least one applicable transmission resource pool to report:

[0253] 2> set themeasResultListCBRto include the CBR measurement results in accordance with the following:

[0254] 3> if thetriggerTypeis set toevent:

[0255] 4> include the transmission resource pools included in thepoolsTriggeredListas defined within theVarMeasReportListfor thismeasId;

[0256] 3> else:

[0257] 4> include the applicable transmission resource pools for which the new measurement results became available since the last periodical reporting or since the measurement was initiated or reset;

[0258] 3> for each transmission resource pool to be reported:

[0259] 4> set thepoolIdentityto thepoolReportIdof this transmission resource pool;

[0260] 4> ifadjacencyPSCCH-PSSCHis set toTRUEfor this transmission resource pool:

[0261] 5> set thecbr-PSSCHto the CBR measurement result on PSSCH and PSCCH of this transmission resource pool provided by lower layers;

[0262] 4> else:

[0263] 5> set thecbr-PSSCHto the CBR measurement result on PSSCH of this transmission resource pool provided by lower layers if available;

[0264] 5> set thecbr-PSCCHto the CBR measurement result on PSCCH of this transmission resource pool provided by lower layers if available;

[0265] 2> set themeasResultSensingto include the sensing measurement results in accordance with the following:

[0266] 3> include the applicable transmission resource pools for which the new measurement results became available since the last periodical reporting or since the measurement was initiated or reset;

[0267] 3> for each transmission resource pool to be reported:

[0268] 4> set thesensingResultto the sensing measurement results provided by the lower layers;

[0269] 1> if thetriggerTypeis set toevent; and ifeventIdis set toeventH1oreventH2:

[0270] 2> set theheightUEto include the altitude of the UE;

[0271] 1> increment thenumberOfReportsSentas defined within theVarMeasReportListfor thismeasIdby 1;

[0272] 1> stop the periodical reporting timer, if running;

[0273] 1> if thenumberOfReportsSentas defined within theVarMeasReportListfor thismeasIdis less than thereportAmountas defined within the correspondingreportConfigfor thismeasId:

[0274] 2> start the periodical reporting timer with the value ofreportIntervalas defined within the correspondingreportConfigfor thismeasId;

[0275] 1> else:

[0276] 2> if thetriggerTypeis set toperiodical:

[0277] 3> remove the entry within theVarMeasReportListfor thismeasId;

[0278] 3> remove thismeasIdfrom themeasIdListwithinVarMeasConfig;

[0279] 1> if the measured results are for CDMA2000 HRPD:

[0280] 2> set thepreRegistrationStatusHRPDto the UE's CDMA2000 upper layer's HRPDpreRegistrationStatus;

[0281] 1> if the measured results are for CDMA2000 1xRTT:

[0282] 2> set the　preRegistrationStatusHRPD toFALSE;

[0283] 1> if the measured results are for WLAN:

[0284] 2> set themeasResultListWLANto include the quantities within thequantityConfigWLANfor up tomaxReportCellsWLAN(s), determined according to the following:

[0285] 3> include WLAN the UE is connected to, if any;

[0286] 3> ifreportAnyWLANis set to TRUE:

[0287] 4> consider WLAN with any WLAN identifiers to be applicable for measurement reporting;

[0288] 3> else:

[0289] 4> consider only WLANs which do not match all WLAN identifiers of any entry withinwlan-MobilitySetinVarWLAN-MobilityConfigto be applicable for measurement reporting;

[0290] 3> include applicable WLAN in order of decreasing WLAN RSSI, i.e. the best WLAN is included first;

[0291] 2> for each included WLAN:

[0292] 3> setwlan-Identifiersto include all WLAN identifiers that can be acquired for the WLAN measured;

[0293] 3> setconnectedWLANtoTRUEif the UE is connected to the WLAN measured;

[0294] 3> ifreportQuantityWLANexistswithin theReportConfigInterRATwithin theVarMeasConfigfor thismeasId:

[0295] 4> ifbandRequestWLANis set toTRUE:

[0296] 5> setbandWLANto include WLAN band of the WLAN measured;

[0297] 4> ifcarrierInfoRequestWLANis set toTRUE:

[0298] 5> setcarrierInfoWLANto include WLAN carrier information of the WLAN measured if it can be acquired;

[0299] 4> ifavailableAdmissionCapacityRequestWLANis set toTRUE:

[0300] 5> set themeasResultto includeavaiableAdmissionCapacityWLANif it can be acquired;

[0301] 4> ifbackhaulDL-BandwidthRequestWLANis set toTRUE:

[0302] 5> set themeasResultto includebackhaulDL-BandwidthWLANif it can be acquired;

[0303] 4> ifbackhaulUL-BandwidthRequestWLANis set toTRUE:

[0304] 5> set themeasResultto includebackhaulUL-BandwidthWLANif it can be acquired;

[0305] 4> ifchannelUtilizationRequestWLANis set toTRUE:

[0306] 5> set themeasResultto includechannelUtilizationWLANif it can be acquired;

[0307] 4> ifstationCountRequestWLANis set toTRUE:

[0308] 5> set themeasResultto includestationCountWLANif it can be acquired;

[0309] 1> if the measurement configuration that triggered the measurement reporting procedure was configured by ansl-ConfigDedicatedEUTRAthat was received within an NRRRCReconfigurationmessage:

[0310] 2> submit theMeasurementReportmessage via SRB1 embedded in NR RRC messageULInformationTransferIRAT.

[0311] 1> else if the UE is configured with NE-DC:

[0312] 2> submit theMeasurementReportmessage via SRB1 embedded in NR RRC messageULInformationTransferMRDC.

[0313] 1> else:

[0314] 2> submit theMeasurementReportmessage to lower layers for transmission, upon which the procedure ends;

[0315] Hereinafter, technical features related to supplementary uplink in RRC are described. Section 5.2.2.3.3 of 3GPP TS 38.331 v17.5.0 may be referred.

[0316] Request for on demand system information

[0317] The UE shall, while SDT procedure is not ongoing:

[0318] 1> ifSIB1includessi-SchedulingInfocontainingsi-RequestConfigSULand criteria to select supplementary uplink is met:

[0319] 2> trigger the lower layer to initiate the Random Access procedure on supplementary uplink using the PRACH preamble(s) and PRACH resource(s) insi-RequestConfigSULcorresponding to the SI message(s) that the UE requires to operate within the cell, and for whichsi-BroadcastStatusis set tonotBroadcasting;

[0320] 2> if acknowledgement for SI request is received from lower layers:

[0321] 3> acquire the requested SI message(s) immediately;

[0322] 1> else if the UE is a RedCap UE and ifinitialUplinkBWP-RedCapis configured inUplinkConfigCommonSIBand ifSIB1includessi-SchedulingInfocontainingsi-RequestConfigRedCapand criteria to select normal uplink is met:

[0323] 2> trigger the lower layer to initiate the Random Access procedure on normal uplink using the PRACH preamble(s) and PRACH resource(s) insi-RequestConfigRedcapcorresponding to the SI message(s) that the UE requires to operate within the cell, and for whichsi-BroadcastStatusis set tonotBroadcasting;

[0324] 2> if acknowledgement for SI request is received from lower layers:

[0325] 3> acquire the requested SI message(s), immediately;

[0326] 1> else:

[0327] 2> if the UE is not a RedCap UE and ifSIB1includessi-SchedulingInfocontainingsi-RequestConfigand criteria to select normal uplink is met; or

[0328] 2> if the UE is a RedCap UE and ifinitialUplinkBWP-RedCapis not configured inUplinkConfigCommonSIBand ifSIB1includessi-SchedulingInfocontainingsi-RequestConfigand criteria to select normal uplink is met:

[0329] 3> trigger the lower layer to initiate the Random Access procedure on normal uplink using the PRACH preamble(s) and PRACH resource(s) insi-RequestConfigcorresponding to the SI message(s) that the UE requires to operate within the cell, and for whichsi-BroadcastStatusis set tonotBroadcasting;

[0330] 3> if acknowledgement for SI request is received from lower layers:

[0331] 4> acquire the requested SI message(s), immediately;

[0332] 2> else:

[0333] 3> apply the default L1 parameter values as specified in corresponding physical layer specifications except for the parameters for which values are provided inSIB1;

[0334] 3> apply the default MAC Cell Group configuration;

[0335] 3> apply thetimeAlignmentTimerCommonincluded inSIB1;

[0336] 3> apply the CCCH configuration;

[0337] 3> initiate transmission of theRRCSystemInfoRequestmessage withrrcSystemInfoRequest;

[0338] 3> if acknowledgement forRRCSystemInfoRequestmessage withrrcSystemInfoRequestis received from lower layers:

[0339] 4> acquire the requested SI message(s), immediately;

[0340] 1> if cell reselection occurs while waiting for the acknowledgment for SI request from lower layers:

[0341] 2> reset MAC;

[0342] 2> if SI request is based onRRCSystemInfoRequestmessage withrrcSystemInfoRequest:

[0343] 3> release RLC entity for SRB0.

[0344] After RACH failure for SI request it is up to UE implementation when to retry the SI request.

[0345] Hereinafter, technical features related to supplementary uplink in MAC are described. Section 5.1.1 of 3GPP TS 38.321 v17.5.0 may be referred.

[0346] Random Access procedure initialization

[0347] The Random Access procedure described in this clause is initiated by a PDCCH order, by the MAC entity itself, or by RRC for the events in accordance with TS 38.300 [2]. There is only one Random Access procedure ongoing at any point in time in a MAC entity. The Random Access procedure on an SCell shall only be initiated by a PDCCH order withra-PreambleIndexdifferent from 0b000000.

[0348] If a new Random Access procedure is triggered while another is already ongoing in the MAC entity, it is up to UE implementation whether to continue with the ongoing procedure or start with the new procedure (e.g. for SI request).

[0349] If there was an ongoing Random Access procedure that is triggered by a PDCCH order while the UE receives another PDCCH order indicating the same Random Access Preamble, PRACH mask index and uplink carrier, the Random Access procedure is considered as the same Random Access procedure as the ongoing one and not initialized again.

[0350] Hereinafter, technical features related to SUL operation are described. Section 5.16 of 3GPP TS 38.321 v17.5.0 may be referred.

[0351] The Supplementary UL (SUL) carrier can be configured as a complement to the normal UL (NUL) carrier. Switching between the NUL carrier and the SUL carrier means that the UL transmissions move from one carrier to the other carrier, which is done by:

[0352] - an indication in DCI;

[0353] - the Random Access procedure;

[0354] - the SDT procedure.

[0355] If the MAC entity receives a UL grant indicating an SUL switch while a Random Access procedure is ongoing, the MAC entity shall ignore the UL grant.

[0356] The Serving Cell configured withsupplementaryUplinkbelongs to a single TAG.

[0357] Hereinafter, technical features related to Small Data Transmission operation are described. Section 5.27 of 3GPP TS 38.321 v17.5.0 may be referred.

[0358] The MAC entity may be configured by RRC with SDT and the SDT procedure may be initiated by RRC layer. The SDT procedure can be performed either by Random Access procedure with 2-step RA type or 4-step RA type (i.e., RA-SDT) or by configured grant Type 1 (i.e., CG-SDT).

[0359] RRC configures the following parameters for SDT procedure:

[0360] -sdt-DataVolumeThreshold: data volume threshold for the UE to determine whether to perform SDT procedure;

[0361] -sdt-RSRP-Threshold: RSRP threshold for UE to determine whether to perform SDT procedure;

[0362] -cg-SDT-RSRP-ThresholdSSB: an RSRP threshold configured for SSB selection for CG-SDT.

[0363] The MAC entity shall, if initiated by the upper layers for SDT procedure:

[0364] 1> if the data volume of the pending UL data across all RBs configured for SDT is less than or equal tosdt-DataVolumeThreshold; and

[0365] For SDT procedure, the MAC entity also considers the suspended RBs configured with SDT for data volume calculation. It is up to the UE's implementation how the UE calculates the data volume for the suspended RBs. Size of the CCCH message is not considered for data volume calculation

[0366] 1> if the RSRP of the downlink pathloss reference is higher thansdt-RSRP-Threshold; or

[0367] 1> ifsdt-RSRP-Thresholdis not configured:

[0368] 2> if the Serving Cell is configured with supplementary uplink; and

[0369] 2> if the RSRP of the downlink pathloss reference is less thanrsrp-ThresholdSSB-SUL:

[0370] 3> select the SUL carrier.

[0371] 2> else:

[0372] 3> select the NUL carrier.

[0373] 2> if CG-SDT is configured on the selected UL carrier, and TA for CG-SDT is valid in the first available CG occasion for initial CG-SDT transmission with CCCH message; and

[0374] 2> if, for each RB having data available for transmission,configuredGrantType1Allowed, if configured for CG-SDT, is configured with valuetruefor the corresponding logical channel; and

[0375] 2> if at least one SSB configured for CG-SDT with SS-RSRP abovecg-SDT-RSRP-ThresholdSSBis available:

[0376] 3> indicate to the upper layers that the conditions for initiating SDT procedure are fulfilled;

[0377] 3> perform CG-SDT procedure on the selected UL carrier.

[0378] 2> else if a set of Random Access resources for RA-SDT is configured and can be selected on the selected UL carrier on the BWP configured byinitialUplinkBWP-RedCap, if configured for a RedCap UE; otherwise, on the BWP configured byinitialUplinkBWP:

[0379] 3> ifcg-SDT-TimeAlignmentTimeris running, considercg-SDT-TimeAlignmentTimeras expired and perform the corresponding actions;

[0380] 3> indicate to the upper layers that the conditions for initiating SDT procedure are fulfilled.

[0381] 2> else:

[0382] 3> indicate to the upper layers that the conditions for initiating SDT procedure are not fulfilled.

[0383] 1> else:

[0384] 2> indicate to the upper layers that the conditions for initiating SDT procedure are not fulfilled.

[0385] If RA-SDT is selected above and after the Random Access procedure is successfully completed, the UE monitors PDCCH addressed to C-RNTI received in random access response until the RA-SDT procedure is terminated. If CG-SDT is selected above and after the initial transmission for CG-SDT is performed, the UE monitors PDCCH addressed to C-RNTI as stored in UE Inactive AS context and CS-RNTI until the CG-SDT procedure is terminated.

[0386] When the UE determines if there is an SSB with SS-RSRP abovecg-SDT-RSRP-ThresholdSSB, the UE uses the latest unfiltered L1-RSRP measurement.

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

[0388] Reception of theRRCConnectionSetupby theUE

[0389] The UE shall:

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

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

[0392] 3> except for NB-IoT:

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

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

[0395] 5> includeflightPathInfoAvailable;

[0396] 1> submit theRRCConnectionSetupCompletemessage to lower layers for transmission;

[0397] 1> for NB-IoT:

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

[0399] 3> perform measurements.

[0400] 1> the procedure ends.

[0401] Reception of theRRCConnectionResumeby theUE

[0402] The UE shall:

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

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

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

[0406] 2> except for NB-IoT:

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

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

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

[0410] 5> includeflightPathInfoAvailable;

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

[0412] 4> includemobilityHistoryAvail;

[0413] 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;

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

[0415] 1> for NB-IoT:

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

[0417] 3> perform measurements.

[0418] 1> the procedure ends.

[0419] Reception of an RRCConnectionReconfiguration including the mobilityControlInfo by theUE(handover)

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

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

[0422] 3> includenumFreqEffectiveReduced;

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

[0424] 3> includeflightPathInfoAvailable;

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

[0426] 3> includescg-ConfigResponseNR;

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

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

[0429] Reception of theRRCConnectionReestablishmentby the UE

[0430] The UE shall:

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

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

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

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

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

[0436] 5> include theconnEstFailInfoAvailable;

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

[0438] 5> includeflightPathInfoAvailable;

[0439] 3> perform the measurement related actions;

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

[0441] Hereinafter, technical features related to UE information procedure are described.

[0442] FIG. 11 shows an example of a UE Information procedure.

[0443] In FIG. 11, UE may transmit a UE Information Request to EUTRAN. EUTRAN may transmit a UE Information Response to UE.

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

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

[0446] Reception of theUEInformationRequestmessage

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

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

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

[0450] 2> if theincludeTimeStampis set to TRUE:

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

[0452] Hereinafter, technical features related to LTE UAV, Measurements are described. Section 5.5.4.1 of 3GPP TS 36.331 v17.5.0 may be referred.

[0453] If security has been activated successfully, the UE shall:

[0454] 1> for eachmeasIdincluded in themeasIdListwithinVarMeasConfig:

[0455] 2> if thetriggerTypeis set toeventand if the correspondingreportConfigincludesnumberOfTriggeringCells,and if the entry condition applicable for this event, i.e. the event corresponding with theeventIdof the correspondingreportConfigwithinVarMeasConfig, is fulfilled for one or more applicable cells for all measurements after layer 3 filtering taken duringtimeToTriggerdefined for this event within theVarMeasConfig:

[0456] 3> If theVarMeasReportListdoes not include a measurement reporting entry for thismeasId(a first cell triggers the event):

[0457] 4> include a measurement reporting entry within theVarMeasReportListfor thismeasId;

[0458] 3> If the number of cell(s) in thecellsTriggeredListis larger than or equal tonumberOfTriggeringCells:

[0459] 4> include the concerned cell(s) in thecellsTriggeredListdefined within theVarMeasReportListfor thismeasId;

[0460] 3> else:

[0461] 4> include the concerned cell(s) in thecellsTriggeredListdefined within theVarMeasReportListfor thismeasId;

[0462] 4> If the number of cell(s) in thecellsTriggeredListis larger than or equal tonumberOfTriggeringCells:

[0463] 5> set thenumberOfReportsSentdefined within theVarMeasReportListfor thismeasIdto 0;

[0464] 5> initiate the measurement reporting procedure; ...

[0465] 2> if thetriggerTypeis set toeventand if theeventIdis set toeventH1oreventH2and if the entering condition applicable for this event, i.e. the event corresponding with theeventIdof the correspondingreportConfigwithinVarMeasConfig, is fulfilled duringtimeToTriggerdefined within theVarMeasConfigfor this event, while theVarMeasReportListdoes not include a measurement reporting entry for thismeasId:

[0466] 3> include a measurement reporting entry within theVarMeasReportListfor thismeasId;

[0467] 3> set thenumberOfReportsSentdefined within theVarMeasReportListfor thismeasIdto 0;

[0468] 3> initiate the measurement reporting procedure;

[0469] 2> if thetriggerTypeis set toeventand if theeventIdis set toeventH1oreventH2and if the leaving condition applicable for this event, i.e. the event corresponding with theeventIdof the correspondingreportConfigwithinVarMeasConfig, is fulfilled duringtimeToTriggerdefined within theVarMeasConfigfor this event:

[0470] 3> remove the measurement reporting entry within theVarMeasReportListfor thismeasId;

[0471] Event H1 (The AerialUEheight is above a threshold)

[0472] The UE shall:

[0473] 1> consider the entering condition for this event to be satisfied when condition H1-1, as specified below, is fulfilled;

[0474] 1> consider the leaving condition for this event to be satisfied when condition H1-2, as specified below, is fulfilled;

[0475] Inequality H1-1 (Entering condition)

[0476] - Ms-Hys>Thresh+Offset

[0477] Inequality H1-2 (Leaving condition)

[0478] - Ms+Hys<Thresh+Offset

[0479] The variables in the formula are defined as follows:

[0480] Ms is the Aerial UE height, not taking into account any offsets.

[0481] Hys is the hysteresis parameter (i.e. h1-Hysteresis as defined within ReportConfigEUTRA) for this event.

[0482] Thresh is the reference threshold parameter for this event given in MeasConfig(i.e. heightThreshRef as defined within MeasConfig).

[0483] Offset is the offset value to heightThreshRef to obtain the absolute threshold for this event. (i.e. h1-ThresholdOffset as defined within ReportConfigEUTRA)

[0484] Ms is expressed in meters.

[0485] Thresh is expressed in the same unit as Ms.

[0486] Event H2 (The AerialUEheight is below a threshold)

[0487] The UE shall:

[0488] 1> consider the entering condition for this event to be satisfied when condition H2-1, as specified below, is fulfilled;

[0489] 1> consider the leaving condition for this event to be satisfied when condition H2-2, as specified below, is fulfilled;

[0490] Inequality H2-1 (Entering condition)

[0491] - Ms+Hys<Thresh+Offset

[0492] Inequality H2-2 (Leaving condition)

[0493] - Ms-Hys>Thresh+Offset

[0494] The variables in the formula are defined as follows:

[0495] Ms is the Aerial UE height, not taking into account any offsets.

[0496] Hys is the hysteresis parameter (i.e. h2-Hysteresis as defined within ReportConfigEUTRA) for this event.

[0497] Thresh is the reference threshold parameter for this event given in MeasConfig(i.e. heightThreshRef as defined within MeasConfig).

[0498] Offset is the offset value to heightThreshRef to obtain the absolute threshold for this event. (i.e. h2-ThresholdOffset as defined within ReportConfigEUTRA)

[0499] Ms is expressed in meters.

[0500] Thresh is expressed in the same unit as Ms.

[0501] The purpose of this procedure is to transfer measurement results from the UE to E-UTRAN. The UE shall initiate this procedure only after successful security activation.

[0502] For the measId for which the measurement reporting procedure was triggered, the UE shall set the measResults within the MeasurementReport message as follows:

[0503] 1> if theincludeLocationInfois configured in the correspondingreportConfigfor thismeasIdor ifpurposefor thereportConfigassociated with themeasIdthat triggered the measurement reporting is set toreportLocation; and detailed location information that has not been reported is available, set the content of thelocationInfoas follows:

[0504] 2> include thelocationCoordinates;

[0505] 2> if available, include thegnss-TOD-msec, except ifpurposefor thereportConfigassociated with themeasIdthat triggered the measurement reporting is set toreportLocation;

[0506] 2> include theverticalVelocityInfo, if available; ...

[0507] 1> if thetriggerTypeis set toevent; and ifeventIdis set toeventH1oreventH2:

[0508] 2> set theheightUEto include the altitude of the UE; ...

[0509] 1> if the measurement configuration that triggered the measurement reporting procedure was configured by ansl-ConfigDedicatedEUTRAthat was received within an NRRRCReconfigurationmessage:

[0510] 2> submit theMeasurementReportmessage via SRB1 embedded in NR RRC messageULInformationTransferIRAT.

[0511] 1> else if the UE is configured with NE-DC:

[0512] 2> submit theMeasurementReportmessage via SRB1 embedded in NR RRC messageULInformationTransferMRDC.

[0513] 1> else:

[0514] 2> submit theMeasurementReportmessage to lower layers for transmission, upon which the procedure ends;

[0515] 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.

[0516] In the No-Transmit Zone (NTZ), airborne UE cannot perform uplink transmission using a certain frequency / band. If the certain frequency is allowed to use on the ground, operator want to use it for UEs on the ground even in NTZ.

[0517] However, if the uplink frequency of a cell deployed in NTZ is not allowed to use for airborne UE, and if there is no alternative cell, airborne UEs would lose the RRC connection or cannot perform initial access.

[0518] Therefore, studies for uplink frequency selection based on altitude in a wireless communication system are required.

[0519] Hereinafter, a method for uplink frequency selection based on altitude in a wireless communication system, according to some embodiments of the present disclosure, will be described with reference to the following drawings.

[0520] 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).

[0521] FIG. 12 shows an example of a method for uplink frequency selection based on altitude in a wireless communication system, according to some embodiments of the present disclosure.

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

[0523] In step S1201, a wireless device may receive information related to multiple uplink frequencies and an altitude threshold.

[0524] For example, the multiple uplink frequencies may be configured for a serving cell.

[0525] In step S1202, a wireless device may identify a current altitude of the wireless device.

[0526] For example, the wireless device may derive the current altitude of the wireless device based on the current position of the wireless device. For example, the wireless device may derive the current altitude of the wireless device based on the flight path.

[0527] In step S1203, a wireless device may select an uplink frequency among the multiple uplink frequencies based on the current altitude of the wireless device and the altitude threshold.

[0528] For example, the wireless device may determine whether the wireless device is an aerial wireless device or not. For example, the wireless device may perform uplink frequency selection based on determining that the wireless device is the aerial wireless device.

[0529] According to some embodiments of the present disclosure, the multiple uplink frequencies may include a normal uplink frequency and an aerial uplink frequency.

[0530] For example, the normal uplink frequency may be selected based on that the wireless device is a non-aerial wireless device. That is, the wireless device may select the normal uplink frequency based on that the wireless device is a non-aerial wireless device.

[0531] For example, the normal uplink frequency may be selected based on that the current altitude of the wireless device is less than the altitude threshold. That is, the wireless device may select the normal uplink frequency based on that the current altitude of the wireless device is less than the altitude threshold.

[0532] For example, the aerial uplink frequency may be selected based on that the wireless device is an aerial wireless device. That is, the wireless device may select the aerial uplink frequency based on that the wireless device is an aerial wireless device.

[0533] For example, the aerial uplink frequency may be selected based on that the current altitude of the wireless device is equal to or greater than the altitude threshold. That is, the wireless device may select the aerial uplink frequency based on that the current altitude of the wireless device is equal to or greater than the altitude threshold.

[0534] According to some embodiments of the present disclosure, the information related to multiple uplink frequencies and an altitude threshold may include information related to a first aerial uplink frequency, a second aerial uplink frequency, a first altitude threshold, and a second altitude threshold.

[0535] For example, the first aerial uplink frequency may be selected based on the current altitude of the wireless device and the first altitude threshold. That is, the wireless device may select the first aerial uplink frequency based on the current altitude of the wireless device is equal to or greater than the first altitude threshold.

[0536] For example, the second aerial uplink frequency may be selected based on the current altitude of the wireless device and the second altitude threshold. That is, the wireless device may select the second altitude uplink frequency based on the current altitude of the wireless device is equal to or greater than the second altitude threshold.

[0537] According to some embodiments of the present disclosure, the wireless device may trigger uplink frequency selection.

[0538] For example, the wireless device may trigger uplink frequency selection based on that a random access channel procedure is initiated.

[0539] For example, the wireless device may trigger uplink frequency selection based on that a small data transmission procedure is initiated.

[0540] For example, the wireless device may trigger uplink frequency selection upon entering a No-Transmit Zone (NTZ).

[0541] In step S1204, a wireless device may perform uplink transmission based on the selected uplink frequency.

[0542] For example, the wireless device may use the selected uplink frequency.

[0543] 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.

[0544] Hereinafter, technical features for uplink frequency selection based on altitude are described.

[0545] According to the present disclosure, if more than one uplink frequencies are configured for serving cell, UE selects an uplink frequency among them based on its altitude or based on whether it is aerial UE or not.

[0546] A normal uplink frequency configured for serving cell may not be associated with any altitude, or may be associated with an altitude threshold.

[0547] Non-aerial UE selects the normal uplink frequency.

[0548] If a UE's altitude is below than the altitude threshold, the UE selects the normal uplink frequency.

[0549] An aerial uplink frequency configured for serving cell may be associated with an altitude threshold.

[0550] Aerial UE selects the aerial uplink frequency.

[0551] If a UE's altitude is higher than the threshold, the UE selects the aerial uplink frequency.

[0552] If more than one aerial uplink frequencies configured for serving cell associated with the same threshold, and if a UE's altitude is higher than the threshold, the UE selects one aerial uplink frequency that the UE supports.

[0553] Different uplink frequency may be associated with different altitude threshold. UE selects an uplink frequency which is associated with its current altitude. For example, three-uplink frequencies are configured for serving cell, i.e., frequency A, B and C. The uplink frequency A, B and C are associated with 'below 500m', 'below 1000m' and 'above 1000m', respectively.

[0554] When UE's altitude is below 500m, the UE selects frequency A as an uplink frequency.

[0555] When UE's altitude is below 1000m but above 500m, the UE selects frequency B as an uplink frequency.

[0556] When UE's altitude is above 1000m, the UE selects frequency C as an uplink frequency.

[0557] UE performs uplink transmission using the selected uplink frequency.

[0558] UE performs the uplink frequency selection when RACH procedure is initiated. When the Random Access procedure is initiated on a Serving Cell, if the Serving Cell for the Random Access procedure is configured with the aerial uplink, and if the altitude of the UE is higher than the altitude threshold, the UE selects the aerial uplink carrier for performing Random Access procedure. If the altitude of the UE is lower than the altitude threshold, the UE selects the normal uplink carrier for performing Random Access procedure.

[0559] UE performs the uplink frequency selection upon reception of the aerial uplink configuration from network. The aerial uplink frequency configuration may include basic parameters of an uplink carrier, such as absolute uplink frequency, subcarrier spacing specific virtual carriers and frequency band indicator, and the initial uplink BWP configuration. The aerial uplink frequency configuration may include the criteria to select the aerial uplink frequency, e.g., altitude threshold or UE type, e.g., whether UE is aerial UE.

[0560] UE performs the uplink frequency selection when System Information request procedure is initiated. When a request to acquire the SI message(s) is triggered, if the aerial frequency specific configuration on MSG1 based SI request is provided, e.g., via SIB1, and criteria to select the aerial uplink frequency is met, UE triggers the lower layer to initiate the Random Access procedure on the aerial uplink frequency using the PRACH preamble(s) and PRACH resource(s) in the aerial frequency specific configuration on MSG1 based SI request corresponding to the SI message(s) that the UE requires to operate within the cell, and for which is not being broadcast.

[0561] UE performs the uplink frequency selection when Small Data Transmission procedure is initiated. If SDT procedure is initiated by the upper layers, e.g., RRC layer or NAS layer, if the Serving Cell is configured with aerial uplink, and if the altitude of the UE is higher than the altitude threshold, the UE select the aerial uplink carrier. If the altitude of the UE is lower than the altitude threshold, the UE select the normal uplink carrier.

[0562] The aerial uplink carrier can be configured as a complement to the normal uplink carrier. Switching between the aerial uplink carrier and the normal uplink carrier means that the UL transmissions move from one carrier to the other carrier, which is done by:

[0563] - an indication in DCI;

[0564] - the Random Access procedure;

[0565] - the SDT procedure.

[0566] If the MAC entity receives a UL grant indicating an aerial uplink carrier switch while a Random Access procedure is ongoing, the MAC entity shall ignore the UL grant.

[0567] No-Transmit Zone (NTZ)

[0568] UE performs the uplink frequency selection upon entering the NTZ.

[0569] When UE is inside the NTZ, UE selects an uplink frequency among uplink frequencies configured for serving cell based on its altitude or based on whether it is aerial UE or not.

[0570] When UE is outside the NTZ, UE selects a normal uplink frequency, e.g., associated with the altitude below the threshold, though its altitude is higher than the threshold.

[0571] Example using supplementaryuplink

[0572] If the UE's altitude is lower than the altitude threshold configured by network, UE selects a normal uplink frequency (=non-supplementary uplink frequency).

[0573] If the UE's altitude is higher than the altitude threshold configured by network, UE selects a supplementary uplink frequency.

[0574] The UE selects the supplementary uplink frequency if the UE supports the uplink frequency, e.g., if UE supports at least oneadditionalSpectrumEmissionin theNR-NS-PmaxListfor a supported supplementary uplink band; and supports an uplink channel bandwidth with a maximum transmission bandwidth configuration which is smaller than or equal to thecarrierBandwidth(indicated insupplementaryUplinkfor the SCS of the initial uplink BWP), and which is wider than or equal to the bandwidth of the initial uplink BWP of the SUL.

[0575] FIG. 13 show an example of uplink frequency selection procedure based on altitude.

[0576] In particular, FIG. 13 shows an example of a method performed by a UE in a wireless communication system.

[0577] In step S1301, a UE may receive information on uplink frequency including a first uplink frequency, a second uplink frequency, and an altitude threshold.

[0578] In step S1302, a UE may determine whether to select the first uplink frequency or the second uplink frequency based on its altitude and the altitude threshold.

[0579] In step S1303, a UE may perform uplink transmission using the selected uplink frequency.

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

[0581] Hereinafter, an apparatus for uplink frequency selection based on altitude 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.

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

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

[0584] 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.

[0585] For example, the wireless device may include at least one transceiver, at least one processor, and at least one memory operably connectable to the at least one processor and storing instructions that, based on being executed by the at least one processor, perform operations.

[0586] The at least one processor may be adapted to receive information related to multiple uplink frequencies and an altitude threshold. The at least one processor may be adapted to identify a current altitude of the wireless device. The at least one processor may be adapted to select an uplink frequency among the multiple uplink frequencies based on the current altitude of the wireless device and the altitude threshold. The at least one processor may be adapted to perform uplink transmission based on the selected uplink frequency.

[0587] For example, the at least one processor may be adapted to determine whether the wireless device is an aerial wireless device or not.

[0588] For example, the at least one processor may be adapted to perform uplink frequency selection based on determining that the wireless device is the aerial wireless device.

[0589] For example, the multiple uplink frequencies may be configured for a serving cell.

[0590] For example, the multiple uplink frequencies may include a normal uplink frequency and an aerial uplink frequency.

[0591] For example, the normal uplink frequency may be selected based on that the wireless device is a non-aerial wireless device.

[0592] For example, the normal uplink frequency may be selected based on that the current altitude of the wireless device is less than the altitude threshold.

[0593] For example, the aerial uplink frequency may be selected based on that the wireless device is an aerial wireless device.

[0594] For example, the aerial uplink frequency may be selected based on that the current altitude of the wireless device is equal to or greater than the altitude threshold.

[0595] For example, the information related to multiple uplink frequencies and an altitude threshold may include information related to a first aerial uplink frequency, a second aerial uplink frequency, a first altitude threshold, and a second altitude threshold.

[0596] For example, the first aerial uplink frequency may be selected based on the current altitude of the wireless device and the first altitude threshold. For example, the second aerial uplink frequency may be selected based on the current altitude of the wireless device and the second altitude threshold.

[0597] For example, the at least one processor may be adapted to trigger uplink frequency selection based on that a random access channel procedure is initiated.

[0598] For example, the at least one processor may be adapted to trigger uplink frequency selection based on that a small data transmission procedure is initiated.

[0599] For example, the at least one processor may be adapted to trigger uplink frequency selection upon entering a No-Transmit Zone (NTZ).

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

[0601] Hereinafter, a processor for a wireless device for uplink frequency selection based on altitude in a wireless communication system, according to some embodiments of the present disclosure, will be described.

[0602] The processor may be adapted to control the wireless device to receive information related to multiple uplink frequencies and an altitude threshold. The processor may be adapted to control the wireless device to identify a current altitude of the wireless device. The processor may be adapted to control the wireless device to select an uplink frequency among the multiple uplink frequencies based on the current altitude of the wireless device and the altitude threshold. The processor may be adapted to control the wireless device to perform uplink transmission based on the selected uplink frequency.

[0603] For example, the processor may be adapted to control the wireless device to determine whether the wireless device is an aerial wireless device or not.

[0604] For example, the processor may be adapted to control the wireless device to perform uplink frequency selection based on determining that the wireless device is the aerial wireless device.

[0605] For example, the multiple uplink frequencies may be configured for a serving cell.

[0606] For example, the multiple uplink frequencies may include a normal uplink frequency and an aerial uplink frequency.

[0607] For example, the normal uplink frequency may be selected based on that the wireless device is a non-aerial wireless device.

[0608] For example, the normal uplink frequency may be selected based on that the current altitude of the wireless device is less than the altitude threshold.

[0609] For example, the aerial uplink frequency may be selected based on that the wireless device is an aerial wireless device.

[0610] For example, the aerial uplink frequency may be selected based on that the current altitude of the wireless device is equal to or greater than the altitude threshold.

[0611] For example, the information related to multiple uplink frequencies and an altitude threshold may include information related to a first aerial uplink frequency, a second aerial uplink frequency, a first altitude threshold, and a second altitude threshold.

[0612] For example, the first aerial uplink frequency may be selected based on the current altitude of the wireless device and the first altitude threshold. For example, the second aerial uplink frequency may be selected based on the current altitude of the wireless device and the second altitude threshold.

[0613] For example, the processor may be adapted to control the wireless device to trigger uplink frequency selection based on that a random access channel procedure is initiated.

[0614] For example, the processor may be adapted to control the wireless device to trigger uplink frequency selection based on that a small data transmission procedure is initiated.

[0615] For example, the processor may be adapted to control the wireless device to trigger uplink frequency selection upon entering a No-Transmit Zone (NTZ).

[0616] For example, the processor may be adapted 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.

[0617] Hereinafter, a non-transitory computer-readable medium has stored thereon a plurality of instructions for uplink frequency selection based on altitude in a wireless communication system, according to some embodiments of the present disclosure, will be described.

[0618] 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.

[0619] 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 another example, the processor and the storage medium may reside as discrete components.

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

[0621] 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.

[0622] 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.

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

[0624] The stored a plurality of instructions may cause the wireless device to receive information related to multiple uplink frequencies and an altitude threshold. The stored a plurality of instructions may cause the wireless device to identify a current altitude of the wireless device. The stored a plurality of instructions may cause the wireless device to select an uplink frequency among the multiple uplink frequencies based on the current altitude of the wireless device and the altitude threshold. The stored a plurality of instructions may cause the wireless device to perform uplink transmission based on the selected uplink frequency.

[0625] For example, the stored a plurality of instructions may cause the wireless device to determine whether the wireless device is an aerial wireless device or not.

[0626] For example, the stored a plurality of instructions may cause the wireless device to perform uplink frequency selection based on determining that the wireless device is the aerial wireless device.

[0627] For example, the multiple uplink frequencies may be configured for a serving cell.

[0628] For example, the multiple uplink frequencies may include a normal uplink frequency and an aerial uplink frequency.

[0629] For example, the normal uplink frequency may be selected based on that the wireless device is a non-aerial wireless device.

[0630] For example, the normal uplink frequency may be selected based on that the current altitude of the wireless device is less than the altitude threshold.

[0631] For example, the aerial uplink frequency may be selected based on that the wireless device is an aerial wireless device.

[0632] For example, the aerial uplink frequency may be selected based on that the current altitude of the wireless device is equal to or greater than the altitude threshold.

[0633] For example, the information related to multiple uplink frequencies and an altitude threshold may include information related to a first aerial uplink frequency, a second aerial uplink frequency, a first altitude threshold, and a second altitude threshold.

[0634] For example, the first aerial uplink frequency may be selected based on the current altitude of the wireless device and the first altitude threshold. For example, the second aerial uplink frequency may be selected based on the current altitude of the wireless device and the second altitude threshold.

[0635] For example, the stored a plurality of instructions may cause the wireless device to trigger uplink frequency selection based on that a random access channel procedure is initiated.

[0636] For example, the stored a plurality of instructions may cause the wireless device to trigger uplink frequency selection based on that a small data transmission procedure is initiated.

[0637] For example, the stored a plurality of instructions may cause the wireless device to trigger uplink frequency selection upon entering a No-Transmit Zone (NTZ).

[0638] For example, the stored a 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 uplink frequency selection based on altitude in a wireless communication system, according to some embodiments of the present disclosure, will be described.

[0640] The BS may transmit, to a wireless device, information related to multiple uplink frequencies and an altitude threshold. For example, the wireless device identifies a current altitude of the wireless device. The wireless device selects an uplink frequency among the multiple uplink frequencies based on the current altitude of the wireless device and the altitude threshold. The wireless device performs uplink transmission based on the selected uplink frequency.

[0641] Hereinafter, a base station (BS) for uplink frequency selection based on altitude 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 adapted to control the transceiver to transmit, to a wireless device, information related to multiple uplink frequencies and an altitude threshold. For example, the wireless device identifies a current altitude of the wireless device. The wireless device selects an uplink frequency among the multiple uplink frequencies based on the current altitude of the wireless device and the altitude threshold. The wireless device performs uplink transmission based on the selected uplink frequency.

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

[0645] According to some embodiments of the present disclosure, the wireless device could efficiently perform uplink frequency selection based on altitude.

[0646] For example, though the normal uplink frequency of a cell deployed in NTZ is not allowed to use for airborne UE, airborne UEs can perform uplink transmission using the aerial uplink frequency.

[0647] In other words, by performing uplink frequency selection according to the altitude of the wireless device, the prohibited uplink frequency may not be used.

[0648] According to some embodiments of the present disclosure, the wireless communication system could provide an efficient solution for uplink frequency selection based on altitude.

[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:receiving information related to multiple uplink frequencies and an altitude threshold;identifying a current altitude of the wireless device;selecting an uplink frequency among the multiple uplink frequencies based on the current altitude of the wireless device and the altitude threshold; andperforming uplink transmission based on the selected uplink frequency.2.The method of claim 1, wherein the method further comprises:determining whether the wireless device is an aerial wireless device or not.3.The method of claim 2, wherein the method further comprises:performing uplink frequency selection based on determining that the wireless device is the aerial wireless device.4.The method of claim 1,wherein the multiple uplink frequencies are configured for a serving cell.5.The method of claim 1,wherein the multiple uplink frequencies includes a normal uplink frequency and an aerial uplink frequency.6.The method of claim 5,wherein the normal uplink frequency is selected based on that the wireless device is a non-aerial wireless device.7.The method of claim 5,wherein the normal uplink frequency is selected based on that the current altitude of the wireless device is less than the altitude threshold.8.The method of claim 5,wherein the aerial uplink frequency is selected based on that the wireless device is an aerial wireless device.9.The method of claim 5,wherein the aerial uplink frequency is selected based on that the current altitude of the wireless device is equal to or greater than the altitude threshold.10.The method of claim 1,wherein the information related to multiple uplink frequencies and an altitude threshold includes information related to a first aerial uplink frequency, a second aerial uplink frequency, a first altitude threshold, and a second altitude threshold.11.The method of claim 10,wherein the first aerial uplink frequency is selected based on the current altitude of the wireless device and the first altitude threshold; andwherein the second aerial uplink frequency is selected based on the current altitude of the wireless device and the second altitude threshold.12.The method of claim 1, wherein the method further comprising:triggering uplink frequency selection based on that a random access channel procedure is initiated.13.The method of claim 1, wherein the method further comprising:triggering uplink frequency selection based on that a small data transmission procedure is initiated.14.The method of claim 1, wherein the method further comprising:triggering uplink frequency selection upon entering a No-Transmit Zone (NTZ).15.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.16.A wireless device in a wireless communication system comprising:at least one transceiver;at least one processor; andat least one memory operably connectable to the at least one processor and storing instructions that, based on being executed by the at least one processor, perform operations comprising:receiving information related to multiple uplink frequencies and an altitude threshold;identifying a current altitude of the wireless device;selecting an uplink frequency among the multiple uplink frequencies based on the current altitude of the wireless device and the altitude threshold; andperforming uplink transmission based on the selected uplink frequency.17.The wireless device of claim 16, wherein the operations further comprising:determining whether the wireless device is an aerial wireless device or not.18.The wireless device of claim 17, wherein the operations further comprising:performing uplink frequency selection based on determining that the wireless device is the aerial wireless device.19.The wireless device of claim 16,wherein the multiple uplink frequencies are configured for a serving cell.20.The wireless device of claim 16,wherein the multiple uplink frequencies includes a normal uplink frequency and an aerial uplink frequency.21.The wireless device of claim 20,wherein the normal uplink frequency is selected based on that the wireless device is a non-aerial wireless device.22.The wireless device of claim 20,wherein the normal uplink frequency is selected based on that the current altitude of the wireless device is less than the altitude threshold.23.The wireless device of claim 20,wherein the aerial uplink frequency is selected based on that the wireless device is an aerial wireless device.24.The wireless device of claim 20,wherein the aerial uplink frequency is selected based on that the current altitude of the wireless device is equal to or greater than the altitude threshold.25.The wireless device of claim 16,wherein the information related to multiple uplink frequencies and an altitude threshold includes information related to a first aerial uplink frequency, a second aerial uplink frequency, a first altitude threshold, and a second altitude threshold.26.The wireless device of claim 25,wherein the first aerial uplink frequency is selected based on the current altitude of the wireless device and the first altitude threshold; andwherein the second aerial uplink frequency is selected based on the current altitude of the wireless device and the second altitude threshold.27.The wireless device of claim 16, wherein the operations further comprising:triggering uplink frequency selection based on that a random access channel procedure is initiated.28.The wireless device of claim 16, wherein the operations further comprising:triggering uplink frequency selection based on that a small data transmission procedure is initiated.29.The wireless device of claim 16, wherein the operations further comprising:triggering uplink frequency selection upon entering a No-Transmit Zone (NTZ).30.The wireless device of claim 16,wherein the at least one processor is further adapted to be in communication with at least one of a user equipment, a network, or an autonomous vehicle other than the wireless device.31.A processor for a wireless device in a wireless communication system, wherein the processor is adapted to control the wireless device to perform operations comprising:receiving information related to multiple uplink frequencies and an altitude threshold;identifying a current altitude of the wireless device;selecting an uplink frequency among the multiple uplink frequencies based on the current altitude of the wireless device and the altitude threshold; andperforming uplink transmission based on the selected uplink frequency.32.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 comprising,receiving information related to multiple uplink frequencies and an altitude threshold;identifying a current altitude of the wireless device;selecting an uplink frequency among the multiple uplink frequencies based on the current altitude of the wireless device and the altitude threshold; andperforming uplink transmission based on the selected uplink frequency.33.A method performed by a base station in a wireless communication system, the method comprising,transmitting, to a wireless device, information related to multiple uplink frequencies and an altitude threshold,wherein the wireless device identifies a current altitude of the wireless device,wherein the wireless device selects an uplink frequency among the multiple uplink frequencies based on the current altitude of the wireless device and the altitude threshold, andwherein the wireless device performs uplink transmission based on the selected uplink frequency.34.A base station in a wireless communication system comprising:a transceiver;a memory; andat least one processor operatively coupled to the transceiver and the memory, and adapted to:transmit, to a wireless device, information related to multiple uplink frequencies and an altitude threshold,wherein the wireless device identifies a current altitude of the wireless device,wherein the wireless device selects an uplink frequency among the multiple uplink frequencies based on the current altitude of the wireless device and the altitude threshold, andwherein the wireless device performs uplink transmission based on the selected uplink frequency.

Images