Method and apparatus for supporting DL only operation

Abstract

A method and apparatus for supporting DL-only operation is provided. The wireless device transmits, to a network, assistance information informing that the wireless device is going to enter a specific area. The wireless device disables feedback related to downlink transmission while in the specific area. The wireless device receives, from the network, downlink transmission while in the specific area without performing feedback related to the downlink transmission.

Description

METHOD AND APPARATUS FOR SUPPORTING DL ONLY OPERATION

[0001] The present disclosure relates to a method and apparatus for supporting DL-only operation.

[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] There is a specific area where the transmission on a certain frequency resource is prohibited by the national regulation or mobile network operator's requirement. For example, a no-transmit-zone (NTZ) is one kind of specific area for the aerial UE. The aerial UE has prior knowledge of the NTZ to observe the national regulation. Within the specific area, UE is prohibited to transmit a signal on a frequency or a frequency band associated with the specific area. The UE cannot transmit feedback for DL transmission in this area. As a result, the UE may not be able to receive downlink data properly requiring feedback for DL transmission.

[0006] If feedback of downlink signal is not required within the specific area, the UE may be able to receive downlink data even if it is within the specific area. However, the network may not know whether the UE is within the specific area or not, even though the network may have flight path of the UE and the information about the specific area. Therefore, the UE and the network may have different understanding about feedback operation for DL transmission.

[0007] Therefore, studies for supporting DL-only operation are required.

[0008] In an aspect, a method is provided. The method comprises: transmitting, by a wireless device to a network, assistance information informing that the wireless device is going to enter a specific area, wherein the specific area is a zone in which uplink data transmission from the wireless device is not allowed; disabling, by the wireless device, feedback related to downlink transmission while in the specific area; and receiving, by the wireless device from the network, downlink transmission while in the specific area without performing feedback related to the downlink transmission.

[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 support DL-only operation in a specific area.

[0012] For example, the wireless device can receive DL transmission without feedback within the specific area.

[0013] For example, the wireless device can improve DL transmission efficiency by performing DL data transmission without feedback in no transmission zone (NTZ).

[0014] According to some embodiments of the present disclosure, the wireless communication system could provide an efficient solution for assisting DL-only operation of a wireless device in a specific area.

[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 successful operation for RRC reconfiguration.

[0025] FIG. 11 shows an example of a failure operation for RRC reconfiguration.

[0026] FIG. 12 shows an example of a UE information procedure.

[0027] FIG. 13 shows an example of a method for supporting DL-only operation, according to some embodiments of the present disclosure.

[0028] FIG. 14 shows an example of a method for assisting DL-only operation in a specific area.

[0029] FIG. 15 shows an example of a method for assisting DL-only operation in a specific area.

[0030] FIG. 16 shows an example of a method for assisting DL-only operation in a specific area.

[0031] FIG. 17 shows an example of a method for assisting DL-only operation in a specific area.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0077] The one or more processors 102 and 202 may be referred to as controllers, microcontrollers, microprocessors, or microcomputers. The one or more processors 102 and 202 may be implemented by hardware, firmware, software, or a combination thereof. As an example, one or more application specific integrated circuits (ASICs), one or more digital signal processors (DSPs), one or more digital signal processing devices (DSPDs), one or more programmable logic devices (PLDs), or one or more field programmable gate arrays (FPGAs) may be included in the one or more processors 102 and 202. descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed in the present disclosure may be implemented using firmware or software and the firmware or software may be configured to include the modules, procedures, or functions. Firmware or software configured to perform the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed in the present disclosure may be included in the one or more processors 102 and 202 or stored in the one or more memories 104 and 204 so as to be driven by the one or more processors 102 and 202. The descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed in the present disclosure may be implemented using firmware or software in the form of code, commands, and / or a set of commands.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0116] uNslotsymbNframe,uslotNsubframe,uslot01410111420221440431480841416016

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

[0118] uNslotsymbNframe,uslotNsubframe,uslot212404

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

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

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

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

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

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

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

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

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

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

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

[0130] Hereinafter, technical features related to mobility in RRC_CONNECTED are described. Sections of 3GPP TS 38.331 v17.5.0 may be referred.

[0131] FIG. 10 shows an example of a successful operation for RRC reconfiguration.

[0132] FIG. 11 shows an example of a failure operation for RRC reconfiguration.

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

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

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

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

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

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

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

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

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

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

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

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

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

[0146] In (NG)EN-DC and NR-DC, SRB3 can be used for measurement configuration and reporting, for UE assistance (re-)configuration and reporting for power savings, for IP address (re-)configuration and reporting for IAB-nodes, to (re-)configure MAC, RLC, BAP, physical layer and RLF timers and constants of the SCG configuration, and to reconfigure PDCP for DRBs associated with the S-KgNB or SRB3, and to reconfigure SDAP for DRBs associated with S-KgNB in NGEN-DC and NR-DC, and to add / modify / release conditional PSCell change configuration, provided that the (re-)configuration does not require any MN involvement, and to transmit RRC messages between the MN and the UE during fast MCG link recovery. In (NG)EN-DC and NR-DC, only measConfig, radioBearerConfig, conditionalReconfiguration, bap-Config, iab-IP-AddressConfigurationList, otherConfig and / or secondaryCellGroup are included in RRCReconfiguration received via SRB3, except when RRCReconfiguration is received within DLInformationTransferMRDC.

[0147] The Network may initiate the RRC reconfiguration procedure to a UE in RRC_CONNECTED. The Network applies the procedure as follows:

[0148] - the establishment of RBs (other than SRB1, that is established during RRC connection establishment) is performed only when AS security has been activated;

[0149] - the establishment of BH RLC Channels for IAB is performed only when AS security has been activated;

[0150] - the establishment of Uu Relay RLC channels and PC5 Relay RLC channels (other than SL-RLC0 and SL-RLC1) for L2 U2N Relay UE is performed only when AS security has been activated, and the establishment of PC5 Relay RLC channels for L2 U2N Remote UE (other than SL-RLC0 and SL-RLC1) is performed only when AS security has been activated;

[0151] - the addition of Secondary Cell Group and SCells is performed only when AS security has been activated;

[0152] - the reconfigurationWithSync is included in secondaryCellGroup only when at least one RLC bearer or BH RLC channel is setup in SCG;

[0153] - the reconfigurationWithSync is included in masterCellGroup only when AS security has been activated, and SRB2 with at least one DRB or multicast MRB or, for IAB, SRB2, are setup and not suspended;

[0154] - the conditionalReconfiguration for CPC is included only when at least one RLC bearer is setup in SCG;

[0155] - the conditionalReconfiguration for CHO or CPA is included only when AS security has been activated, and SRB2 with at least one DRB or multicast MRB or, for IAB, SRB2, are setup and not suspended.

[0156] Hereinafter, technical features related to flight path information for UAV are described. Sections of 3GPP TS 36.331 v17.5.0 may be referred.

[0157] Reception of the RRCConnectionSetup by the UE

[0158] The UE shall:

[0159] 1> except when the UE connected to 5GC is a BL UE or UE in CE, if the RRCConnectionSetup is received in response to an RRCConnectionResumeRequest from a suspended RRC connection:

[0160] 2> if the UE is resuming an RRC connection after early security reactivation:

[0161] 3> discard any current AS security context including the KRRCenc key, the KRRCint key, the KUPint key and the KUPenc key;

[0162] 2> release all radio resources, including release of the RLC entity, the MAC configuration and the associated PDCP entity for all established or suspended RBs, except for SRB0;

[0163] 2> discard the stored UE AS context and resumeIdentity;

[0164] 2> if stored, discard the stored nextHopChainingCount;

[0165] 2> if stored, discard the stored drb-ContinueROHC;

[0166] 2> indicate to upper layers fallback of the RRC connection;

[0167] 1> if the RRCConnectionSetup is received in response to an RRCConnectionResumeRequest from RRC_INACTIVE:

[0168] 2> stop T380 if running;

[0169] 2> discard the stored UE Inactive AS context;

[0170] 2> release rrc-InactiveConfig, if configured;

[0171] 1> if the UE connected to 5GC is a BL UE or UE in CE, and the RRCConnectionSetup is received in response to an RRCConnectionResumeRequest from a suspended RRC connection:

[0172] 2> discard the stored UE AS context and resumeIdentity;

[0173] 2> if stored, discard the stored nextHopChainingCount;

[0174] 2> if stored, discard the stored drb-ContinueROHC;

[0175] 1> if the RRCConnectionSetup is received in response to an RRCConnectionResumeRequest from RRC_INACTIVE; or

[0176] 1> if the UE connected to 5GC is a BL UE or UE in CE, and the RRCConnectionSetup is received in response to an RRCConnectionResumeRequest from a suspended RRC connection:

[0177] 2> discard any current AS security context including the KRRCenc key, the KRRCint key, the KUPint key and the KUPenc key;

[0178] 2> release radio resources for all established RBs except SRB0, including release of the RLC entities, of the associated PDCP entities and of SDAP entities;

[0179] 2> release the RRC configuration except for the default L1 parameter values, default MAC main configuration and CCCH;

[0180] 2> apply the default NR PDCP configuration for SRB1;

[0181] 2> use NR PDCP for all subsequent messages received and sent by the UE via SRB1;

[0182] 2> indicate to upper layers fallback of the RRC connection;

[0183] 1> if the RRCConnectionSetup is received in response to an RRCEarlyDataRequest or RRCConnectionResumeRequest for transmission using PUR:

[0184] 2> instruct the associated MAC entity to start timeAlignmentTimer;

[0185] 1> perform the radio resource configuration procedure;

[0186] 1> if stored, discard the cell reselection priority information provided by the idleModeMobilityControlInfo or inherited from another RAT;

[0187] 1> if stored, discard the altFreqPriorities provided by the RRCConnectionRelease;

[0188] 1> if stored, discard the dedicated offset provided by the redirectedCarrierOffsetDedicated;

[0189] 1> stop timer T300;

[0190] 1> if T302 is running:

[0191] 2> stop timer T302;

[0192] 2> if the UE is connected to 5GC:

[0193] 3> perform the actions;

[0194] 1> stop timer T303, if running;

[0195] 1> stop timer T305, if running;

[0196] 1> stop timer T306, if running;

[0197] 1> stop timer T308, if running;

[0198] 1> perform the actions;

[0199] 1> stop timer T320, if running;

[0200] 1> stop timer T350, if running;

[0201] 1> perform the actions;

[0202] 1> release rclwi-Configuration, if configured;

[0203] 1> stop timer T360, if running;

[0204] 1> stop timer T322, if running;

[0205] 1> if timer T331 is running:

[0206] 2> stop timer T331;

[0207] 2> perform the actions;

[0208] 1> stop timer T323, if running;

[0209] 1> forward the dedicatedInfoNAS, if received, to the upper layers;

[0210] 1> if T309 is running:

[0211] 2> stop timer T309 for all access categories;

[0212] 2> perform the actions.

[0213] 1> enter RRC_CONNECTED;

[0214] 1> stop the cell re-selection procedure;

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

[0216] 1> except for NB-IoT:

[0217] 2> if the UE supports RLF report for inter-RAT MRO EUTRA, and if the UE has radio link failure or handover failure information available in VarRLF-Report and if the RPLMN is included in plmn-IdentityList stored in VarRLF-Report:

[0218] 3> if reconnectCellId in VarRLF-Report is not set, and if the UE failed to perform reestablishment:

[0219] 4> set timeUntilReconnection in VarRLF-Report to the time that elapsed since the last radio link failure or handover failure;

[0220] 4> set eutraReconnectCellId in reconnectCellId in VarRLF-Report to the global cell identity and the tracking area code of the PCell;

[0221] 2> if the UE radio link failure or handover failure information available in VarRLF-Report and if the RPLMN is included in plmn-IdentityList stored in VarRLF-Report:

[0222] 3> if reconnectCellId in VarRLF-Report is not set, and if the UE failed to perform reestablishment:

[0223] 4> set timeUntilReconnection in VarRLF-Report to the time that elapsed since the last radio link failure or handover failure;

[0224] 4> set eutraReconnectCellId in reconnectCellId in VarRLF-Report to the global cell identity and the tracking area code of the PCell;

[0225] 1> set the content of RRCConnectionSetupComplete message as follows:

[0226] 2> if the RRCConnectionSetup is received in response to an RRCConnectionResumeRequest:

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

[0228] 4> set the s-TMSI to the value received from upper layers;

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

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

[0231] 5> set the ng-5G-S-TMSI to the value received from upper layers;

[0232] 4> else:

[0233] 5> set the ng-5G-S-TMSI-Bits to ng-5G-S-TMSI with the value received from upper layers;

[0234] 2> else if upper layers provide a 5G-S-TMSI:

[0235] 3> except for NB-IoT, set the ng-5G-S-TMSI-Bits to ng-5G-S-TMSI-Part2 to the leftmost 8 bits of 5G-S-TMSI received from upper layers;

[0236] 2> set the selectedPLMN-Identity to the PLMN selected by upper layers from the PLMN(s) included in the plmn-IdentityList in SystemInformationBlockType1 (or SystemInformationBlockType1-NB in NB-IoT);

[0237] 2> if upper layers provide the 'Registered MME', include and set the registeredMME as follows:

[0238] 3> if the PLMN identity of the 'Registered MME' is different from the PLMN selected by the upper layers:

[0239] 4> include the plmnIdentity in the registeredMME and set it to the value of the PLMN identity in the 'Registered MME' received from upper layers;

[0240] 3> set the mmegi and the mmec to the value received from upper layers;

[0241] 2> if upper layers provided the 'Registered MME':

[0242] 3> include and set the gummei-Type to the value provided by the upper layers;

[0243] 2> if upper layers provide the 'Registered AMF', include and set the registeredAMF as follows:

[0244] 3> if the PLMN identity of the 'Registered AMF' is different from the PLMN selected by the upper layers:

[0245] 4> include the plmnIdentity in the registeredAMF and set it to the value of the PLMN identity in the 'Registered AMF' received from upper layers;

[0246] 3> set the amf-Identifier to AMF Identifier of the 'Registered AMF' received from upper layers;

[0247] 2> if upper layers provided the 'Registered AMF':

[0248] 3> include and set the guami-Type to the value provided by the upper layers;

[0249] 2> if upper layers provide one or more S-NSSAI:

[0250] 3> include the s-NSSAI-list and set the content to the values provided by the upper layers;

[0251] 2> if the UE supports CIoT EPS optimisation(s):

[0252] 3> include attachWithoutPDN-Connectivity if received from upper layers;

[0253] 3> include up-CIoT-EPS-Optimisation if received from upper layers;

[0254] 3> except for NB-IoT, include cp-CIoT-EPS-Optimisation if received from upper layers;

[0255] 2> if the UE supports CIoT 5GS optimisation(s):

[0256] 3> for NB-IoT, include ng-U-DataTransfer if received from upper layers;

[0257] 3> except for NB-IoT, include cp-CIoT-5GS-Optimisatoin if received from upper layers;

[0258] 2> if connecting as an RN:

[0259] 3> include the rn-SubframeConfigReq;

[0260] 2> if the RRCConnectionSetup is received in response to RRCEarlyDataRequest:

[0261] 3> set the dedicatedInfoNAS to a zero-length octet string;

[0262] 2> else:

[0263] 3> set the dedicatedInfoNAS to include the information received from upper layers;

[0264] 2> if the RRCConnectionSetup is not in response to transmission using PUR and the UE has a stored pur-Config including pur-ConfigID:

[0265] 3> include the stored pur-ConfigID;

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

[0267] 3> except for NB-IoT:

[0268] 4> include the mobilityState and set it to the mobility state of the UE just prior to entering RRC_CONNECTED state;

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

[0270] 5> include flightPathInfoAvailable;

[0271] 3> for NB-IoT:

[0272] 4> if the UE has radio link failure information available in VarRLF-Report-NB and if the RPLMN is included in plmn-IdentityList stored in VarRLF-Report-NB:

[0273] 5> include rlf-InfoAvailable;

[0274] 4> if the UE has ANR measurements information available in VarANR-MeasReport-NB and if the RPLMN is included in plmn-IdentityList stored in VarANR-MeasReport-NB:

[0275] 5> include anr-InfoAvailable;

[0276] 3> include dcn-ID if a DCN-ID value is received from upper layers;

[0277] 2> else (i.e. the UE is connected to 5GC):

[0278] 3> if the UE is a BL UE:

[0279] 4> include lte-M;

[0280] 2> except for NB-IoT:

[0281] 3> if the UE has radio link failure or handover failure information available in VarRLF-Report and if the RPLMN is included in plmn-IdentityList stored in VarRLF-Report:

[0282] 4> include rlf-InfoAvailable;

[0283] 3> if the UE has MBSFN logged measurements available for E-UTRA and if the RPLMN is included in plmn-IdentityList stored in VarLogMeasReport:

[0284] 4> include logMeasAvailableMBSFN;

[0285] 3> if the UE has logged measurements available for E-UTRA and if the RPLMN is included in plmn-IdentityList stored in VarLogMeasReport:

[0286] 4> include logMeasAvailable;

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

[0288] 5> include logMeasAvailableBT;

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

[0290] 5> include logMeasAvailableWLAN;

[0291] 3> if the UE has connection establishment failure information available in VarConnEstFailReport and if the RPLMN is equal to plmn-Identity stored in VarConnEstFailReport:

[0292] 4> include connEstFailInfoAvailable;

[0293] 3> if the UE supports storage of mobility history information and the UE has mobility history information available in VarMobilityHistoryReport:

[0294] 4> include the mobilityHistoryAvail;

[0295] 3> if the SIB2 contains idleModeMeasurements and the UE has E-UTRA idle / inactive measurement information concerning cells other than the PCell available in VarMeasIdleReport; or

[0296] 3> if the SIB2 contains idleModeMeasurementsNR and the UE has NR idle / inactive measurement information available in VarMeasIdleReport:

[0297] 4> include the idleMeasAvailable;

[0298] 3> if upper layers indicate that access to RLOS is initiated:

[0299] 4> set rlos-Request to true;

[0300] 2> if UE needs UL gaps during continuous uplink transmission:

[0301] 3> include ue-CE-NeedULGaps;

[0302] 2> for NB-IoT:

[0303] 3> if the UE supports serving cell idle mode measurements reporting and servingCellMeasInfo is present in SystemInformationBlockType2-NB:

[0304] 4> set the measResultServCell to include the measurements of the serving cell;

[0305] - The UE includes the latest results of the serving cell measurements as used for cell selection / reselection evaluation, which are performed.

[0306] 2> if connecting as an IAB-node:

[0307] 3> include iab-NodeIndication;

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

[0309] 3> include gnss-validityDuration in accordance with the remaining time of the GNSS validity duration;

[0310] 2> if UE supports uplink RRC Segmentation of UECapabilityInformation:

[0311] 3> except for NB-IoT, may include ul-RRC-Segmentation if upper layers indicate that they are performing an Attach or TA Update;

[0312] 1> submit the RRCConnectionSetupComplete message to lower layers for transmission;

[0313] 1> for NB-IoT:

[0314] 2> if the UE supports connected mode measurements and connMeasConfig is present in SystemInformationBlockType3-NB:

[0315] 3> perform measurements.

[0316] 1> the procedure ends.

[0317] Reception of theRRCConnectionResumeby theUE

[0318] The UE shall:

[0319] 1> stop timer T300;

[0320] 1> if T309 is running:

[0321] 2> stop timer T309 for all access categories;

[0322] 2> perform the actions.

[0323] 1> stop T380 if running;

[0324] 1> if the RRCConnectionResume is received in response to an RRCConnectionResumeRequest for EDT or for transmission using PUR:

[0325] 2> discard the stored UE AS context and resumeIdentity;

[0326] 2> if the RRCConnectionResume is received in response to an RRCConnectionResumeRequest for transmission using PUR:

[0327] 3> instruct the associated MAC entity to start timeAlignmentTimer;

[0328] 1> else:

[0329] 2> if resuming an RRC connection from a suspended RRC connection in EPC; or

[0330] 2> for NB-IoT, if resuming an RRC connection from a suspended RRC connection in 5GC and fullConfig is not present in the RRCConnectionResume message:

[0331] 3> restore the PDCP state and re-establish PDCP entities for SRB2, if configured with E-UTRA PDCP, and for all DRBs that are configured with E-UTRA PDCP;

[0332] 3> if drb-ContinueROHC is included:

[0333] 4> indicate to lower layers that stored UE AS context is used and that drb-ContinueROHC is configured;

[0334] 4> continue the header compression protocol context for the DRBs configured with the header compression protocol;

[0335] 3> else:

[0336] 4> indicate to lower layers that stored UE AS context is used;

[0337] 4> reset the header compression protocol context for the DRBs configured with the header compression protocol;

[0338] 3> if restoreMCG-SCells is included:

[0339] 4> restore the MCG SCell(s) configuration, if stored;

[0340] 3> else:

[0341] 4> release the MCG SCell(s) from the UE AS context, if stored;

[0342] 3> if restoreSCG is included:

[0343] 4> restore nr-SecondaryCellGroupConfig, if stored;

[0344] 3> else if the UE was configured with EN-DC:

[0345] 4> perform MR-DC release;

[0346] 4> release tdm-PatternConfig or tdm-PatternConfig2, if configured;

[0347] 3> discard the stored UE AS context and resumeIdentity;

[0348] 3> configure lower layers to consider the restored MCG and SCG SCell(s) (if any) to be in deactivated state;

[0349] 2> else if the RRCConnectionResume message includes the fullConfig (i.e., for resuming an RRC connection from RRC_INACTIVE or for resuming a suspended RRC connection in 5GC):

[0350] 3> perform the radio configuration procedure;

[0351] 2> else if resuming an RRC connection from RRC_INACTIVE:

[0352] 3> restore the following from the stored UE Inactive AS context:

[0353] - MCG physical layer configuration,

[0354] - MCG MAC configuration,

[0355] - MCG RLC configuration,

[0356] - PDCP configuration;

[0357] 3> if restoreMCG-SCells is included:

[0358] 4> restore the MCG SCell(s) configuration, if stored;

[0359] 3> else:

[0360] 4> release the MCG SCell(s) from the UE Inactive AS context, if stored;

[0361] 3> if restoreSCG is included:

[0362] 4> restore nr-SecondaryCellGroupConfig, if stored;

[0363] 3> else if the UE was configured with NGEN-DC:

[0364] 4> perform MR-DC release;

[0365] 4> release tdm-PatternConfig or tdm-PatternConfig2, if configured;

[0366] 3> discard the stored UE Inactive AS context;

[0367] 3> configure lower layers to consider the restored MCG and SCG SCell(s) (if any) to be in deactivated state;

[0368] 3> release the rrc-InactiveConfig, except ran-NotificationAreaInfo;

[0369] 2> else (i.e., except for NB-IoT for resuming a suspended RRC connection in 5GC):

[0370] 3> restore the physical layer configuration, the MAC configuration, the RLC configuration and the PDCP configuration from the stored UE AS context;

[0371] 3> discard the stored UE AS context and resumeIdentity;

[0372] 1> perform the radio resource configuration procedure;

[0373] - When performing the radio resource configuration procedure, for the physical layer configuration and the MAC Main configuration, the restored RRC configuration from the stored UE AS context is used as basis for the reconfiguration.

[0374] 1> if the received RRCConnectionResume includes the sCellToReleaseList:

[0375] 2> perform SCell release;

[0376] 1> if the received RRCConnectionResume includes the sCellToAddModList:

[0377] 2> perform SCell addition or modification;

[0378] 1> if the received RRCConnectionResume includes the sCellGroupToReleaseList:

[0379] 2> perform SCell group release;

[0380] 1> if the received RRCConnectionResume includes the sCellGroupToAddModList:

[0381] 2> perform SCell group addition or modification;

[0382] 1> if the received RRCConnectionResume message includes the nr-SecondaryCellGroupConfig:

[0383] 2> perform NR RRC Reconfiguration;

[0384] 1> if the received RRCConnectionResume message includes the sk-Counter:

[0385] 2> perform key update procedure;

[0386] 1> if the received RRCConnectionResume message includes the nr-RadioBearerConfig1:

[0387] 2> perform radio bearer configuration;

[0388] 1> if the received RRCConnectionResume message includes the nr-RadioBearerConfig2:

[0389] 2> perform radio bearer configuration;

[0390] 1> except if the RRCConnectionResume is received in response to an RRCConnectionResumeRequest for EDT or for transmission using PUR:

[0391] 2> resume SRB2, SRB3 (if configured), and all DRBs, if any, including RBs configured with NR PDCP;

[0392] - If the NR SCG is deactivated, resuming SRB3 and all DRBs does not imply that PDCP or RRC PDUs can be transmitted or received on SCG RLC bearers.

[0393] 1> if stored, discard the cell reselection priority information provided by the idleModeMobilityControlInfo or inherited from another RAT;

[0394] 1> if stored, discard the altFreqPriorities provided by the RRCConnectionRelease;

[0395] 1> if stored, discard the dedicated offset provided by the redirectedCarrierOffsetDedicated;

[0396] 1> if the RRCConnectionResume message includes the measConfig:

[0397] 2> perform the measurement configuration procedure;

[0398] 1> if T302 is running:

[0399] 2> stop timer T302;

[0400] 2> if the UE is connected to 5GC:

[0401] 3> perform the actions;

[0402] 1> stop timer T303, if running;

[0403] 1> stop timer T305, if running;

[0404] 1> stop timer T306, if running;

[0405] 1> stop timer T308, if running;

[0406] 1> perform the actions;

[0407] 1> stop timer T320, if running;

[0408] 1> stop timer T350, if running;

[0409] 1> perform the actions;

[0410] 1> stop timer T360, if running;

[0411] 1> stop timer T322, if running;

[0412] 1> stop timer T323, if running;

[0413] 1> if timer T331 is running:

[0414] 2> stop timer T331;

[0415] 2> perform the actions;

[0416] 1> if the UE is resuming an RRC connection after early security reactivation or RRCConnectionResume is received in response to an RRCConnectionResumeRequest from RRC_INACTIVE:

[0417] 2> ignore the nextHopChainingCount value indicated in the RRCConnectionResume message;

[0418] 1> else:

[0419] 2> if resuming an RRC connection from a suspended RRC connection in EPC:

[0420] 3> update the KeNB key based on the KASME key to which the current KeNB is associated, using the nextHopChainingCount value indicated in the RRCConnectionResume message;

[0421] 3> store the nextHopChainingCount value;

[0422] 3> derive the KRRCint key associated with the previously configured integrity algorithm;

[0423] 3> request lower layers to verify the integrity protection of the RRCConnectionResume message, using the previously configured algorithm and the KRRCint key;

[0424] 3> if the integrity protection check of the RRCConnectionResume message fails:

[0425] 4> perform the actions upon leaving RRC_CONNECTED, with release cause 'other', upon which the procedure ends;

[0426] 3> derive the KRRCenc key and the KUPenc key associated with the previously configured ciphering algorithm;

[0427] 3> configure lower layers to resume integrity protection using the previously configured algorithm and the KRRCint key immediately, i.e., integrity protection shall be applied to all subsequent messages received and sent by the UE;

[0428] 3> configure lower layers to resume ciphering and to apply the ciphering algorithm, the KRRCenc key and the KUPenc key, i.e. the ciphering configuration shall be applied to all subsequent messages received and sent by the UE;

[0429] 1> enter RRC_CONNECTED;

[0430] 1> indicate to upper layers that the suspended RRC connection has been resumed;

[0431] 1> stop the cell re-selection procedure;

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

[0433] 1> set the content of RRCConnectionResumeComplete message as follows:

[0434] 2> set the selectedPLMN-Identity to the PLMN selected by upper layers from the PLMN(s) included in the plmn-IdentityList in SystemInformationBlockType1;

[0435] 2> set the dedicatedInfoNAS to include the information received from upper layers;

[0436] 2> except for NB-IoT:

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

[0438] 4> if the UE has radio link failure or handover failure information available in VarRLF-Report and if the RPLMN is included in plmn-IdentityList stored in VarRLF-Report:

[0439] 5> include rlf-InfoAvailable;

[0440] 4> if the UE has MBSFN logged measurements available for E-UTRA and if the RPLMN is included in plmn-IdentityList stored in VarLogMeasReport:

[0441] 5> include logMeasAvailableMBSFN;

[0442] 4> else if the UE has logged measurements available for E-UTRA and if the RPLMN is included in plmn-IdentityList stored in VarLogMeasReport:

[0443] 5> include logMeasAvailable;

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

[0445] 6> include logMeasAvailableBT;

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

[0447] 6> include logMeasAvailableWLAN;

[0448] 4> if the UE has connection establishment failure information available in VarConnEstFailReport and if the RPLMN is equal to plmn-Identity stored in VarConnEstFailReport:

[0449] 5> include connEstFailInfoAvailable;

[0450] 4> include the mobilityState and set it to the mobility state of the UE just prior to entering RRC_CONNECTED state;

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

[0452] 5> include flightPathInfoAvailable;

[0453] 3> if the UE supports storage of mobility history information and the UE has mobility history information available in VarMobilityHistoryReport:

[0454] 4> include mobilityHistoryAvail;

[0455] 3> if the idleModeMeasurementReq is included in the RRCConnectionResume message:

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

[0457] 5> set the measResultListIdle-r16 in the RRCConnectionResumeComplete message to the value of measReportIdle-r15 in the VarMeasIdleReport;

[0458] 5> set the measResultListExtIdle in the RRCConnectionResumeComplete message to the value of measReportIdle-r16 in the VarMeasIdleReport, if available;

[0459] 5> set the measResultListIdleNR in the RRCConnectionResumeComplete message to the value of measReportIdleNR in the VarMeasIdleReport, if available;

[0460] 5> discard the VarMeasIdleReport upon successful delivery of the RRCConnectionResumeComplete message is confirmed by lower layers;

[0461] 3> else:

[0462] 4> if the SIB2 contains idleModeMeasurements and the UE has E-UTRA idle / inactive measurement information concerning cells other than the PCell available in VarMeasIdleReport; or

[0463] 4> if the SIB2 contains idleModeMeasurementsNR and the UE has NR idle / inactive measurement information available in VarMeasIdleReport:

[0464] 5> include the idleMeasAvailable;

[0465] 3> if the RRCConnectionResume message includes nr-SecondaryCellGroupConfig:

[0466] 4> include scg-ConfigResponseNR;

[0467] 2> for NB-IoT:

[0468] 3> if the UE supports serving cell idle mode measurements reporting and servingCellMeasInfo is present in SystemInformationBlockType2-NB:

[0469] 4> set the measResultServCell to include the measurements of the serving cell;

[0470] - The UE includes the latest results of the serving cell measurements as used for cell selection / reselection evaluation.

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

[0472] 4> if the UE has radio link failure information available in VarRLF-Report-NB and if the RPLMN is included in plmn-IdentityList stored in VarRLF-Report-NB:

[0473] 5> include rlf-InfoAvailable;

[0474] 4> if the UE has ANR measurements information available in VarANR-MeasReport-NB and if the RPLMN is included in plmn-IdentityList stored in VarANR-MeasReport-NB:

[0475] 5> include anr-InfoAvailable;

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

[0477] 3> include gnss-validityDuration in accordance with the remaining time of the GNSS validity duration;

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

[0479] 1> submit the RRCConnectionResumeComplete message to lower layers for transmission;

[0480] 1> for NB-IoT:

[0481] 2> if the UE supports connected mode measurements and connMeasConfig is present in SystemInformationBlockType3-NB:

[0482] 3> perform measurements.

[0483] 1> the procedure ends.

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

[0485] If the RRCConnectionReconfiguration message includes the mobilityControlInfo and the UE is able to comply with the configuration included in this message, the UE shall:

[0486] 1> if the RRCConnectionReconfiguration is applied due to a conditional reconfiguration execution upon cell selection performed while timer T311 was running:

[0487] 2> remove all the entries within VarConditionalReconfiguration, if any;

[0488] 1> if daps-HO is not configured for any DRB:

[0489] 2> stop timer T310, if running;

[0490] 2> if timer T316 is running:

[0491] 3> stop timer T316;

[0492] 3> clear the information included in VarRLF-Report, if any;

[0493] 2> resume MCG transmission, if suspended;

[0494] 1> stop timer T312, if running;

[0495] 1> stop timer T317, if running;

[0496] 1> start timer T304 with the timer value set to t304, as included in the mobilityControlInfo;

[0497] 1> stop timer T370, if running;

[0498] 1> if the carrierFreq is included:

[0499] 2> consider the target PCell to be one on the frequency indicated by the carrierFreq with a physical cell identity indicated by the targetPhysCellId;

[0500] 1> else:

[0501] 2> consider the target PCell to be one on the frequency of the source PCell with a physical cell identity indicated by the targetPhysCellId;

[0502] 1> if T309 is running:

[0503] 2> stop timer T309 for all access categories;

[0504] 2> perform the actions.

[0505] 1> start synchronising to the DL of the target PCell;

[0506] - The UE should perform the handover as soon as possible following the reception of the RRC message triggering the handover, which could be before confirming successful reception (HARQ and ARQ) of this message.

[0507] 1> if BL UE or UE in CE:

[0508] 2> if sameSFN-Indication is not present in mobilityControlInfo:

[0509] 3> acquire the MasterInformationBlock in the target PCell;

[0510] 1> if makeBeforeBreak is configured:

[0511] 2> perform the remainder of this procedure including and following resetting MAC after the UE has stopped the uplink transmission / downlink reception with the source PCell;

[0512] - It is up to UE implementation when to stop the uplink transmission / downlink reception with the source PCell to initiate re-tuning for connection to the target cell, if makeBeforeBreak is configured.

[0513] - It is up to UE implementation when to stop the uplink transmission / downlink reception with the source SCell(s) after receiving RRCConnectionReconfiguration message.

[0514] 1> if daps-HO is configured for any DRB:

[0515] 2> establish a MAC entity for the target PCell, with the same configuration as the MAC entity for the source PCell;

[0516] 2> for each DRB configured with daps-HO:

[0517] 3> establish the RLC entity or entities and the associated DTCH logical channel for the target PCell, with the same configurations as for the source PCell;

[0518] 3> reconfigure the PDCP entity to configure DAPS.

[0519] 2> for each DRB not configured with daps-HO:

[0520] 3> re-establish PDCP;

[0521] 3> re-establish the RLC entity and associate it, and the associated DTCH logical channel, to the target PCell;

[0522] 2> for each SRB:

[0523] 3> establish a PDCP entity for the target PCell, with the same configuration as the PDCP entity for the source PCell;

[0524] 3> establish an RLC entity and an associated DCCH logical channel for the target PCell, with the same configuration as for the source PCell;

[0525] 2> suspend the SRBs for the source PCell;

[0526] - In order to understand if a daps-HO is configured, the UE needs to check the presence of the field daps-HO within the received RadioResourceConfigDedicated IE.

[0527] - In DAPS handover, the UE may re-establish PDCP and RLC entity for a DRB not configured with daps-HO when MAC successfully completes the random access procedure. In this case, the UE suspends data transmission and reception for all DRBs not configured with daps-HO in the source PCell for the duration of the DAPS handover.

[0528] 1> else (if daps-HO is not configured):

[0529] 2> reset MCG MAC and SCG MAC, if configured;

[0530] 2> release uplinkDataCompression, if configured;

[0531] 2> re-establish PDCP for all RBs configured with pdcp-config that are established;

[0532] - The handling of the radio bearers after the successful completion of the PDCP re-establishment, e.g. the re-transmission of unacknowledged PDCP SDUs (as well as the associated status reporting), the handling of the SN and the HFN.

[0533] - At handover the reestablishPDCP flag will be set for all RBs configured with NR PDCP in nr-RadioBearerConfig1 or nr-RadioBearerConfig2 which will cause the PDCP entity to be re-established also for these RBs.

[0534] 2> re-establish MCG RLC and SCG RLC, if configured, for all RBs that are established;

[0535] 1> for each SCell configured for the UE other than the PSCell:

[0536] 2> if the received RRCConnectionReconfiguration message includes sCellState for the SCell and indicates activated:

[0537] 3> configure lower layers to consider the SCell to be in activated state;

[0538] 2> else if the received RRCConnectionReconfiguration message includes sCellState for the SCell and indicates dormant:

[0539] 3> configure lower layers to consider the SCell to be in dormant state;

[0540] 2> else:

[0541] 3> configure lower layers to consider the SCell to be in deactivated state;

[0542] 1> apply the value of the newUE-Identity as the C-RNTI in the target MCG;

[0543] 1> if the RRCConnectionReconfiguration message includes the fullConfig:

[0544] 2> perform the radio configuration procedure as specified in 5.3.5.8;

[0545] 1> configure lower layers in accordance with the received radioResourceConfigCommon;

[0546] 1> if the received RRCConnectionReconfiguration message includes the rach-Skip:

[0547] 2> configure lower layers to apply the rach-Skip for the target MCG;

[0548] 1> if UE supports timing advance reporting and the received radioResourceConfigCommon includes the ta-Report:

[0549] 2> instruct the associated MAC entity to trigger Timing Advance reporting;

[0550] 1> configure lower layers in accordance with any additional fields, not covered in the previous, if included in the received mobilityControlInfo;

[0551] 1> if the received RRCConnectionReconfiguration includes the sCellToReleaseList:

[0552] 2> perform SCell release;

[0553] 1> if the received RRCConnectionReconfiguration includes the sCellGroupToReleaseList:

[0554] 2> perform SCell group release;

[0555] 1> if the received RRCConnectionReconfiguration includes the scg-Configuration; or

[0556] 1> if the current UE configuration includes one or more split DRBs and the received RRCConnectionReconfiguration includes radioResourceConfigDedicated including drb-ToAddModList:

[0557] 2> perform SCG reconfiguration;

[0558] 1> if the RRCConnectionReconfiguration message includes the radioResourceConfigDedicated:

[0559] 2> perform the radio resource configuration procedure;

[0560] 1> if the securityConfigHO (without suffix) is included in the RRCConnectionReconfiguration:

[0561] 2> if the keyChangeIndicator received in the securityConfigHO is set to TRUE:

[0562] 3> update the KeNB key based on the KASME key taken into use with the latest successful NAS SMC procedure;

[0563] 2> else:

[0564] 3> update the KeNB key based on the current KeNB or the NH, using the nextHopChainingCount value indicated in the securityConfigHO;

[0565] - If the UE needs to update the S-KeNB key, the UE updates the S-KeNB after updating the KeNB key.

[0566] 2> store the nextHopChainingCount value;

[0567] 2> if the securityAlgorithmConfig is included in the securityConfigHO:

[0568] 3> derive the KRRCint key associated with the integrityProtAlgorithm;

[0569] 3> if connected as an RN; or

[0570] 3> if capable of user plane integrity protection:

[0571] 4> derive the KUPint key associated with the integrityProtAlgorithm;

[0572] 3> derive the KRRCenc key and the KUPenc key associated with the cipheringAlgorithm;

[0573] 2> else:

[0574] 3> derive the KRRCint key associated with the current integrity algorithm;

[0575] 3> if connected as an RN; or

[0576] 3> if capable of user plane integrity protection:

[0577] 4> derive the KUPint key associated with the current integrity algorithm;

[0578] 3> derive the KRRCenc key and the KUPenc key associated with the current ciphering algorithm;

[0579] 2> configure lower layers to apply the integrity protection algorithm and the KRRCint key, i.e. the integrity protection configuration shall be applied to all subsequent messages received and sent by the UE, including the message used to indicate the successful completion of the procedure;

[0580] 2> configure lower layers to apply the ciphering algorithm, the KRRCenc key and the KUPenc key, i.e. the ciphering configuration shall be applied to all subsequent messages received and sent by the UE, including the message used to indicate the successful completion of the procedure;

[0581] - For a DRB configured for DAPS HO, the new ciphering algorithm and the KUPenc key is applied for traffic exchange between the UE and the target MCG while the old ciphering algorithm and KUPenc key is applied for traffic exchange between the UE and the source MCG.

[0582] 1> else if the securityConfigHO-v1530 is included in the RRCConnectionReconfiguration:

[0583] 2> if the nas-Container is received:

[0584] 3> forward the nas-Container to upper layers;

[0585] 2> if the keyChangeIndicator-r15 is received and is set to TRUE:

[0586] 3> update the KeNB key based on the KAMF key;

[0587] 2> else:

[0588] 3> update the KeNB key based on the current KeNB or the NH, using the received nextHopChainingCount-r15;

[0589] 2> store the nextHopChainingCount-r15 value;

[0590] 2> if the securityAlgorithmConfig-r15 is received:

[0591] 3> derive the KRRCint key associated with the integrityProtAlgorithm;

[0592] 3> derive the KRRCenc key and the KUPenc key associated with the cipheringAlgorithm;

[0593] 2> else:

[0594] 3> derive the KRRCint key associated with the current integrity algorithm;

[0595] 3> derive the KRRCenc key and the KUPenc key associated with the current ciphering algorithm;

[0596] 1> if the received RRCConnectionReconfiguration includes the nr-Config and it is set to release; or

[0597] 1> if the received RRCConnectionReconfiguration includes endc-ReleaseAndAdd and it is set to TRUE:

[0598] 2> perform MR-DC release;

[0599] 1> if the received RRCConnectionReconfiguration includes the sk-Counter:

[0600] 2> perform key update procedure;

[0601] 1> if the received RRCConnectionReconfiguration includes the nr-SecondaryCellGroupConfig:

[0602] 2> perform NR RRC Reconfiguration.

[0603] 1> if the received RRCConnectionReconfiguration includes the nr-RadioBearerConfig1:

[0604] 2> perform radio bearer configuration;

[0605] 1> if the received RRCConnectionReconfiguration includes the nr-RadioBearerConfig2:

[0606] 2> perform radio bearer configuration.

[0607] 1> if connected as an RN:

[0608] 2> configure lower layers to apply the integrity protection algorithm and the KUPint key, for current or subsequently established DRBs that are configured to apply integrity protection, if any;

[0609] 1> if the received RRCConnectionReconfiguration includes the sCellToAddModList:

[0610] 2> perform SCell addition or modification;

[0611] 1> if the received RRCConnectionReconfiguration includes the sCellGroupToAddModList:

[0612] 2> perform SCell group addition or modification;

[0613] 1> if the received RRCConnectionReconfiguration includes the systemInformationBlockType1Dedicated:

[0614] 2> perfom the actions upon reception of the SystemInformationBlockType1 message;

[0615] 1> if the received RRCConnectionReconfiguration includes the systemInformationBlockType31Dedicated:

[0616] 2> perform the actions upon reception of the SystemInformationBlockType31 message;

[0617] 1> perform the measurement related actions;

[0618] 1> if the RRCConnectionReconfiguration message includes the measConfig:

[0619] 2> perform the measurement configuration procedure;

[0620] 1> perform the measurement identity autonomous removal;

[0621] 1> release reportProximityConfig and clear any associated proximity status reporting timer;

[0622] 1> if the RRCConnectionReconfiguration message includes the otherConfig:

[0623] 2> perform the other configuration procedure;

[0624] 1> if the RRCConnectionReconfiguration message includes the sl-DiscConfig or sl-CommConfig:

[0625] 2> perform the sidelink dedicated configuration procedure;

[0626] 1> if the RRCConnectionReconfiguration message includes wlan-OffloadInfo:

[0627] 2> perform the dedicated WLAN offload configuration procedure;

[0628] 1> if handoverWithoutWT-Change is not configured:

[0629] 2> release the LWA configuration, if configured;

[0630] 1> release the LWIP configuration, if configured;

[0631] 1> if the RRCConnectionReconfiguration message includes rclwi-Configuration:

[0632] 2> perform the WLAN traffic steering command procedure;

[0633] 1> if the RRCConnectionReconfiguration message includes lwa-Configuration:

[0634] 2> perform the LWA configuration procedure;

[0635] 1> if the RRCConnectionReconfiguration message includes lwip-Configuration:

[0636] 2> perform the LWIP reconfiguration procedure;

[0637] 1> if the RRCConnectionReconfiguration message includes the sl-V2X-ConfigDedicated or mobilityControlInfoV2X:

[0638] 2> perform the V2X sidelink communication dedicated configuration procedure;

[0639] - In case of conditional reconfiguration the text "if the received RRCConnectionReconfiguration. . ." corresponds to applying the stored RRCConnectionReconfiguration message.

[0640] 1> if the UE is configured to operate in EN-DC as result of this procedure, forward upperLayerIndication, as if the UE receives this field from SIB2, to upper layers, otherwise indicate upper layers absence of this field;

[0641] 1> set the content of RRCConnectionReconfigurationComplete message as follows:

[0642] 2> if the UE has radio link failure or handover failure information available in VarRLF-Report and if the RPLMN is included in plmn-IdentityList stored in VarRLF-Report:

[0643] 3> include rlf-InfoAvailable;

[0644] 2> if the UE has MBSFN logged measurements available for E-UTRA and if the RPLMN is included in plmn-IdentityList stored in VarLogMeasReport and if T330 is not running:

[0645] 3> include logMeasAvailableMBSFN;

[0646] 2> else if the UE has logged measurements available for E-UTRA and if the RPLMN is included in plmn-IdentityList stored in VarLogMeasReport:

[0647] 3> include the logMeasAvailable;

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

[0649] 4> include logMeasAvailableBT;

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

[0651] 4> include logMeasAvailableWLAN;

[0652] 2> if the UE has connection establishment failure information available in VarConnEstFailReport and if the RPLMN is equal to plmn-Identity stored in VarConnEstFailReport:

[0653] 3> include connEstFailInfoAvailable;

[0654] 2> if the RRCConnectionReconfiguration message includes perCC-GapIndicationRequest:

[0655] 3> include perCC-GapIndicationList and numFreqEffective;

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

[0657] 3> include numFreqEffectiveReduced;

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

[0659] 3> include flightPathInfoAvailable;

[0660] 2> if the received RRCConnectionReconfiguration message included nr-SecondaryCellGroupConfig:

[0661] 3> include scg-ConfigResponseNR;

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

[0663] 3> include gnss-validityDuration in accordance with the remaining time of the GNSS validity duration;

[0664] 1> submit the RRCConnectionReconfigurationComplete message to lower layers for transmission;

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

[0666] 1> if MAC indicates the successful reception of a PDCCH transmission addressed to C-RNTI and if rach-Skip is configured:

[0667] 2> stop timer T304;

[0668] 2> if daps-HO is configured for any DRB:

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

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

[0671] 2> release rach-Skip;

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

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

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

[0675] 3> if the UE has initiated the transmission of an InDeviceCoexIndication message during the last 1 second preceding reception of the RRCConnectionReconfiguration message including mobilityControlInfo; or

[0676] 3> if the RRCConnectionReconfiguration message is applied due to a conditional reconfiguration execution and the UE has initiated transmission of an InDeviceCoexIndication message since it was configured to do:

[0677] 4> initiate transmission of the InDeviceCoexIndication message;

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

[0679] 3> if the UE has initiated the transmission of a UEAssistanceInformation message during the last 1 second preceding reception of the RRCConnectionReconfiguration message including mobilityControlInfo; or

[0680] 3> if the RRCConnectionReconfiguration message is applied due to a conditional reconfiguration execution, and the UE has initiated transmission of a UEAssistanceInformation message for the corresponding cell group since it was configured to do:

[0681] 4> initiate transmission of the UEAssistanceInformation message;

[0682] 2> if SystemInformationBlockType15 is broadcast by the PCell:

[0683] 3> if the UE has initiated the transmission of a MBMSInterestIndication message during the last 1 second preceding reception of the RRCConnectionReconfiguration message including mobilityControlInfo; or

[0684] 3> if the RRCConnectionReconfiguration message is applied due to a conditional reconfiguration execution and the UE supports MBMS reception and the UE has initiated transmission of an MBMSInterestIndication message since it was configured to do:

[0685] 4> ensure having a valid version of SystemInformationBlockType15 for the PCell;

[0686] 4> determine the set of MBMS frequencies of interest;

[0687] 4> determine the set of MBMS services of interest;

[0688] 4> initiate transmission of the MBMSInterestIndication message;

[0689] 2> if SystemInformationBlockType18 is broadcast by the target PCell; and the UE initiated the transmission of a SidelinkUEInformation message indicating a change of sidelink communication related parameters relevant in target PCell (i.e. change of commRxInterestedFreq or commTxResourceReq, commTxResourceReqUC if SystemInformationBlockType18 includes commTxResourceUC-ReqAllowed or commTxResourceInfoReqRelay if PCell broadcasts SystemInformationBlockType19 including discConfigRelay) during the last 1 second preceding reception of the RRCConnectionReconfiguration message including mobilityControlInfo; or

[0690] 2> if SystemInformationBlockType19 is broadcast by the target PCell; and the UE initiated the transmission of a SidelinkUEInformation message indicating a change of sidelink discovery related parameters relevant in target PCell (i.e. change of discRxInterest or discTxResourceReq, discTxResourceReqPS if SystemInformationBlockType19 includes discConfigPS or discRxGapReq or discTxGapReq if the UE is configured with gapRequestsAllowedDedicated set to true or if the UE is not configured with gapRequestsAllowedDedicated and SystemInformationBlockType19 includes gapRequestsAllowedCommon) during the last 1 second preceding reception of the RRCConnectionReconfiguration message including mobilityControlInfo; or

[0691] 2> if SystemInformationBlockType21 is broadcast by the target PCell; and the UE initiated the transmission of a SidelinkUEInformation message indicating a change of V2X sidelink communication related parameters relevant in target PCell (i.e. change of v2x-CommRxInterestedFreqList or v2x-CommTxResourceReq) during the last 1 second preceding reception of the RRCConnectionReconfiguration message including mobilityControlInfo; or

[0692] 2> if the RRCConnectionReconfiguration message is applied due to a conditional reconfiguration execution, and at least one of SystemInformationBlockType18, SystemInformationBlockType19, and SystemInformationBlockType21 is broadcast by the target PCell, and the UE has initiated transmission of a SidelinkUEInformation message since it was configured to do:

[0693] 3> initiate transmission of the SidelinkUEInformation message;

[0694] 2> remove all the entries within VarConditionalReconfiguration, if any;

[0695] 2> for each measId, if the associated reportConfig is condReconfigurationTriggerEUTRA:

[0696] 3> remove the entry with the matching measId from the measIdList within the VarMeasConfig;

[0697] 3> remove the entry with the matching reportConfigId from the reportConfigList within the VarMeasConfig;

[0698] 3> if the measObjectId is only included in a MeasIdToAddMod:

[0699] 4> remove the entry with the matching measObjectId from the measObjectList within the VarMeasConfig;

[0700] 2> the procedure ends;

[0701] - The UE is not required to determine the SFN of the target PCell by acquiring system information from that cell before performing RACH access in the target PCell, except for BL UEs or UEs in CE when sameSFN-Indication is not present in mobilityControlInfo.

[0702] Reception of the RRCConnectionReestablishment by the UE

[0703] The UE shall:

[0704] 1> stop timer T301;

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

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

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

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

[0709] 2> else:

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

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

[0712] 2> perform the radio resource configuration procedure;

[0713] 2> resume SRB1;

[0714] - E-UTRAN should not transmit any message on SRB1 prior to receiving the RRCConnectionReestablishmentComplete message.

[0715] 2> if UE is connected to EPC, update the KeNB key based on the KASME key to which the current KeNB is associated, using the nextHopChainingCount value indicated in the RRCConnectionReestablishment message;

[0716] 2> else if UE is connected to 5GC, update the KeNB key based on the KAMF key to which the current KeNB is associated, using the nextHopChainingCount value indicated in the RRCConnectionReestablishment message;

[0717] 2> store the nextHopChainingCount value;

[0718] 2> derive the KRRCint key associated with the previously configured integrity algorithm;

[0719] 2> derive the KRRCenc key and the KUPenc key associated with the previously configured ciphering algorithm;

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

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

[0722] 3> derive the KUPint key associated with the previously configured integrity algorithm;

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

[0724] 2> if connected as an RN:

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

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

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

[0728] 3> set the content of RRCConnectionReestablishmentComplete message as follows:

[0729] 4> if the UE has radio link failure or handover failure information available in VarRLF-Report and if the RPLMN is included in plmn-IdentityList stored in VarRLF-Report:

[0730] 5> include the rlf-InfoAvailable;

[0731] 4> if the UE has MBSFN logged measurements available for E-UTRA and if the RPLMN is included in plmn-IdentityList stored in VarLogMeasReport and if T330 is not running:

[0732] 5> include logMeasAvailableMBSFN;

[0733] 4> else if the UE has logged measurements available for E-UTRA and if the RPLMN is included in plmn-IdentityList stored in VarLogMeasReport:

[0734] 5> include the logMeasAvailable;

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

[0736] 6> include the logMeasAvailableBT;

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

[0738] 6> include the logMeasAvailableWLAN;

[0739] 4> if the UE has connection establishment failure information available in VarConnEstFailReport and if the RPLMN is equal to plmn-Identity stored in VarConnEstFailReport:

[0740] 5> include the connEstFailInfoAvailable;

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

[0742] 5> include flightPathInfoAvailable;

[0743] 3> perform the measurement related actions;

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

[0745] 2> else:

[0746] 3> if the UE supports serving cell idle mode measurements reporting and servingCellMeasInfo is present in SystemInformationBlockType2-NB:

[0747] 4> set the measResultServCell to include the measurements of the serving cell;

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

[0749] 4> if the UE has radio link failure information available in VarRLF-Report-NB and if the RPLMN is included in plmn-IdentityList stored in VarRLF-Report-NB:

[0750] 5> include the rlf-InfoAvailable;

[0751] 4> if the UE has ANR measurements information available in VarANR-MeasurementReport-NB and if the RPLMN is included in plmn-IdentityList stored in VarANR-MeasurementReport-NB:

[0752] 5> include the anr-InfoAvailable;

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

[0754] 3> include gnss-validityDuration in accordance with the remaining time of the GNSS validity duration;

[0755] 2> submit the RRCConnectionReestablishmentComplete message to lower layers for transmission;

[0756] 2> if SystemInformationBlockType15 is broadcast by the PCell:

[0757] 3> if the UE has transmitted an MBMSInterestIndication message during the last 1 second preceding detection of radio link failure:

[0758] 4> ensure having a valid version of SystemInformationBlockType15 for the PCell;

[0759] 4> determine the set of MBMS frequencies of interest;

[0760] 4> determine the set of MBMS services of interest;

[0761] 4> initiate transmission of the MBMSInterestIndication message;

[0762] 2> if SystemInformationBlockType18 is broadcast by the PCell; and the UE transmitted a SidelinkUEInformation message indicating a change of sidelink communication related parameters relevant in PCell (i.e. change of commRxInterestedFreq or commTxResourceReq, commTxResourceReqUC if SystemInformationBlockType18 includes commTxResourceUC-ReqAllowed or commTxResourceInfoReqRelay if PCell broadcasts SystemInformationBlockType19 including discConfigRelay) during the last 1 second preceding detection of radio link failure; or

[0763] 2> if SystemInformationBlockType19 is broadcast by the PCell; and the UE transmitted a SidelinkUEInformation message indicating a change of sidelink discovery related parameters relevant in PCell (i.e. change of discRxInterest or discTxResourceReq, discTxResourceReqPS if SystemInformationBlockType19 includes discConfigPS or discRxGapReq or discTxGapReq if the UE is configured with gapRequestsAllowedDedicated set to true or if the UE is not configured with gapRequestsAllowedDedicated and SystemInformationBlockType19 includes gapRequestsAllowedCommon) during the last 1 second preceding detection of radio link failure; or

[0764] 2> if SystemInformationBlockType21 including sl-V2X-ConfigCommon is broadcast by the PCell; and the UE transmitted a SidelinkUEInformation message indicating a change of V2X sidelink communication related parameters relevant in PCell (i.e. change of v2x-CommRxInterestedFreqList or v2x-CommTxResourceReq) during the last 1 second preceding detection of radio link failure:

[0765] 3> initiate transmission of the SidelinkUEInformation message;

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

[0767] 2> validate dl-NAS-MAC;

[0768] 2> if dl-NAS-MAC check fails:

[0769] 3> perform the actions upon leaving RRC_CONNECTED, with release cause 'RRC connection failure', upon which the procedure ends;

[0770] 2> except for a UE that only supports the Control Plane CIoT EPS / 5GS optimisation:

[0771] 3> re-establish PDCP for SRB1;

[0772] 3> re-establish RLC for SRB1;

[0773] 2> re-establish RLC for SRB1bis;

[0774] 2> perform the radio resource configuration procedure in accordance with the received radioResourceConfigDedicated;

[0775] 2> except for a UE that only supports the Control Plane CIoT EPS / 5GS optimisation:

[0776] 3> resume SRB1;

[0777] 2> resume SRB1bis;

[0778] - E-UTRAN should not transmit any message on SRB1bis prior to receiving the RRCConnectionReestablishmentComplete message.

[0779] 2> if the UE supports serving cell idle mode measurements reporting and servingCellMeasInfo is present in SystemInformationBlockType2-NB:

[0780] 3> set the measResultServCell to include the measurements of the serving cell;

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

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

[0783] 3> include gnss-validityDuration in accordance with the remaining time of the GNSS validity duration;

[0784] 2> submit the RRCConnectionReestablishmentComplete message to lower layers for transmission;

[0785] 1> for NB-IoT:

[0786] 2> if the UE supports connected mode measurements and connMeasConfig is present in SystemInformationBlockType3-NB:

[0787] 3> perform measurements.

[0788] 1> the procedure ends;

[0789] FIG. 12 shows an example of a UE information procedure.

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

[0791] E-UTRAN initiates the procedure by sending the UEInformationRequest message. E-UTRAN should initiate this procedure only after successful security activation.

[0792] Upon receiving the UEInformationRequest message, the UE shall, only after successful security activation:

[0793] 1> if rach-ReportReq is set to true, set the contents of the rach-Report in the UEInformationResponse message as follows:

[0794] 2> set the numberOfPreamblesSent to indicate the number of preambles sent by MAC for the last successfully completed random access procedure;

[0795] 2> if contention resolution was not successful for at least one of the transmitted preambles for the last successfully completed random access procedure:

[0796] 3> set the contentionDetected to true;

[0797] 2> else:

[0798] 3> set the contentionDetected to false;

[0799] 2> if the UE is a BL UE or UE in CE:

[0800] 3> set the initialCEL to indicate the initial CE level used for the last successfully completed random access procedure;

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

[0802] 3> set the initialNRSRP-Level to indicate the NRSRP level of the NPRACH resource selected for the first preamble transmission for the last successfully completed random access procedure;

[0803] 2> if the UE is a BL UE, UE in CE or NB-IoT UE:

[0804] 3> if the last successfully completed random access procedure was initiated with EDT PRACH resource and succeeded after receiving EDT fallback indication from lower layers:

[0805] 4> set the edt-Fallback to true;

[0806] 3> else:

[0807] 4> set the edt-Fallback to false;

[0808] 1> if rlf-ReportReq is set to true and the UE has radio link failure information or handover failure information available in VarRLF-Report (VarRLF-Report-NB in NB-IoT) and if the RPLMN is included in plmn-IdentityList stored in VarRLF-Report:

[0809] 2> for NB-IoT, if the global cell identity of the selected cell is the same as the reestablishmentCellId in the VarRLF-Report-NB:

[0810] 3> remove the reestablishmentCellId from the VarRLF-Report-NB;

[0811] 2> set timeSinceFailure in VarRLF-Report (VarRLF-Report-NB in NB-IoT) to the time that elapsed since the last radio link or handover failure in E-UTRA;

[0812] 2> set the rlf-Report in the UEInformationResponse message to the value of rlf-Report in VarRLF-Report (VarRLF-Report-NB in NB-IoT);

[0813] 2> discard the rlf-Report from VarRLF-Report (VarRLF-Report-NB in NB-IoT) upon successful delivery of the UEInformationResponse message confirmed by lower layers;

[0814] 1> except for NB-IoT, if connEstFailReportReq is set to true and the UE has connection establishment failure information in VarConnEstFailReport and if the RPLMN is equal to plmn-Identity stored in VarConnEstFailReport:

[0815] 2> set timeSinceFailure in VarConnEstFailReport to the time that elapsed since the last connection establishment failure in E-UTRA;

[0816] 2> set the connEstFailReport in the UEInformationResponse message to the value of connEstFailReport in VarConnEstFailReport;

[0817] 2> discard the connEstFailReport from VarConnEstFailReport upon successful delivery of the UEInformationResponse message confirmed by lower layers;

[0818] 1> except for NB-IoT, if the logMeasReportReq is present and if the RPLMN is included in plmn-IdentityList stored in VarLogMeasReport:

[0819] 2> if VarLogMeasReport includes one or more logged measurement entries, set the contents of the logMeasReport in the UEInformationResponse message as follows:

[0820] 3> include the absoluteTimeStamp and set it to the value of absoluteTimeInfo in the VarLogMeasReport;

[0821] 3> include the traceReference and set it to the value of traceReference in the VarLogMeasReport;

[0822] 3> include the traceRecordingSessionRef and set it to the value of traceRecordingSessionRef in the VarLogMeasReport;

[0823] 3> include the tce-Id and set it to the value of tce-Id in the VarLogMeasReport;

[0824] 3> include the logMeasInfoList and set it to include one or more entries from the VarLogMeasReport starting from the entries logged first, and for each entry of the logMeasInfoList that is included, include all information stored in the corresponding logMeasInfoList entry in VarLogMeasReport;

[0825] 3> if the VarLogMeasReport includes one or more additional logged measurement entries that are not included in the logMeasInfoList within the UEInformationResponse message:

[0826] 4> include the logMeasAvailable;

[0827] 4> if logMeasResultListBT is included in one or more of the additional logged measurement entries in VarLogMeasReport that are not included in the logMeasInfoList within the UEInformationResponse message:

[0828] 5> include the logMeasAvailableBT;

[0829] 4> if logMeasResultListWLAN is included in one or more of the additional logged measurement entries in VarLogMeasReport that are not included in the logMeasInfoList within the UEInformationResponse message:

[0830] 5> include the logMeasAvailableWLAN;

[0831] 1> except for NB-IoT, if mobilityHistoryReportReq is set to true:

[0832] 2> include the mobilityHistoryReport and set it to include entries from VarMobilityHistoryReport;

[0833] 2> include in the mobilityHistoryReport an entry for the current cell, possibly after removing the oldest entry if required, and set its fields as follows:

[0834] 3> set visitedCellId to the global cell identity or the physical cell identity and carrier frequency of the current cell:

[0835] 3> set field timeSpent to the time spent in the current cell;

[0836] 1> except for NB-IoT, if the idleModeMeasurementReq is included in the UEInformationRequest and the UE has stored VarMeasIdleReport that contains measurement information concerning cells other than the PCell:

[0837] 2> set the measResultListIdle-r15 in the UEInformationResponse message to the value of measReportIdle-r15 in the VarMeasIdleReport;

[0838] 2> set the measResultListExtIdle in the UEInformationResponse message to the value of measReportIdle-r16 in the VarMeasIdleReport, if available;

[0839] 2> set the measResultListIdleNR in the UEInformationResponse message to the value of measReportIdleNR in the VarMeasIdleReport, if available;

[0840] 2> discard the VarMeasIdleReport upon successful delivery of the UEInformationResponse message confirmed by lower layers;

[0841] 1> except for NB-IoT, if flightPathInfoReq field is present and the UE has flight path information available:

[0842] 2> include the flightPathInfoReport and set it to include the list of waypoints along the flight path;

[0843] 2> if the includeTimeStamp is set to TRUE:

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

[0845] 1> for NB-IoT, if anr-ReportReq is set to true and the UE has measResultList available in VarANR-MeasReport-NB:

[0846] 2> set the anr-MeasReport in the UEInformationResponse message as follows:

[0847] 3> if the global cell identity of the PCell is different from servCellIdentity in the VarANR-MeasReport-NB;

[0848] 4> include the servCellIdentity and set it to the value of servCellIdentity in the VarANR-MeasReport-NB;

[0849] 3> set measResultServCell to the value of measResultServCell in the VarANR-MeasReport-NB;

[0850] 3> set relativeTimeStamp to the value of relativeTimeStamp in the VarANR-MeasReport-NB;

[0851] 3> set measResultList to the value of measResultList in the VarANR-MeasReport-NB;

[0852] 2> discard the VarANR-MeasReport-NB upon successful delivery of the UEInformationResponse message confirmed by lower layers;

[0853] 1> except for NB-IoT, if the coarseLocationReq is set to true:

[0854] 2> if available, include the coarseLocationInfo;

[0855] 1> if the logMeasReport is included in the UEInformationResponse:

[0856] 2> submit the UEInformationResponse message to lower layers for transmission via SRB2;

[0857] 2> discard the logged measurement entries included in the logMeasInfoList from VarLogMeasReport upon successful delivery of the UEInformationResponse message confirmed by lower layers;

[0858] 1> else:

[0859] 2> submit the UEInformationResponse message to lower layers for transmission via SRB1;

[0860] Hereinafter, technical features related to mobility in ARQ procedures are described. Sections of 3GPP TS 38.322 v17.3.0 may be referred.

[0861] ARQ procedures are only performed by an AM RLC entity.

[0862] The transmitting side of an AM RLC entity can receive a negative acknowledgement (notification of reception failure by its peer AM RLC entity) for an RLC SDU or an RLC SDU segment by the following:

[0863] - STATUS PDU from its peer AM RLC entity.

[0864] When receiving a negative acknowledgement for an RLC SDU or an RLC SDU segment by a STATUS PDU from its peer AM RLC entity, the transmitting side of the AM RLC entity shall:

[0865] - if the SN of the corresponding RLC SDU falls within the range TX_Next_Ack <= SN < = the highest SN of the AMD PDU among the AMD PDUs submitted to lower layer:

[0866] - consider the RLC SDU or the RLC SDU segment for which a negative acknowledgement was received for retransmission.

[0867] When an RLC SDU or an RLC SDU segment is considered for retransmission, the transmitting side of the AM RLC entity shall:

[0868] - if the RLC SDU or RLC SDU segment is considered for retransmission for the first time:

[0869] - set the RETX_COUNT associated with the RLC SDU to zero.

[0870] - else, if it (the RLC SDU or the RLC SDU segment that is considered for retransmission) is not pending for retransmission already and the RETX_COUNT associated with the RLC SDU has not been incremented due to another negative acknowledgment in the same STATUS PDU:

[0871] - increment the RETX_COUNT.

[0872] - if RETX_COUNT = maxRetxThreshold:

[0873] - indicate to upper layers that max retransmission has been reached.

[0874] When retransmitting an RLC SDU or an RLC SDU segment, the transmitting side of an AM RLC entity shall:

[0875] - if needed, segment the RLC SDU or the RLC SDU segment;

[0876] - form a new AMD PDU which will fit within the total size of AMD PDU(s) indicated by lower layer at the particular transmission opportunity;

[0877] - submit the new AMD PDU to lower layer.

[0878] When forming a new AMD PDU, the transmitting side of an AM RLC entity shall:

[0879] - only map the original RLC SDU or RLC SDU segment to the Data field of the new AMD PDU;

[0880] - modify the header of the new AMD PDU in accordance with the description;

[0881] - set the P field.

[0882] Polling

[0883] An AM RLC entity can poll its peer AM RLC entity in order to trigger STATUS reporting at the peer AM RLC entity.

[0884] Transmission of aAMDPDU

[0885] Upon notification of a transmission opportunity by lower layer, for each AMD PDU submitted for transmission such that the AMD PDU contains either a not previously transmitted RLC SDU or an RLC SDU segment containing not previously transmitted byte segment, the transmitting side of an AM RLC entity shall:

[0886] - increment PDU_WITHOUT_POLL by one;

[0887] - increment BYTE_WITHOUT_POLL by every new byte of Data field element that it maps to the Data field of the AMD PDU;

[0888] - if PDU_WITHOUT_POLL >= pollPDU; or

[0889] - if BYTE_WITHOUT_POLL >= pollByte:

[0890] - include a poll in the AMD PDU as described below.

[0891] Upon notification of a transmission opportunity by lower layer, for each AMD PDU submitted for transmission, the transmitting side of an AM RLC entity shall:

[0892] - if both the transmission buffer and the retransmission buffer becomes empty (excluding transmitted RLC SDUs or RLC SDU segments awaiting acknowledgements) after the transmission of the AMD PDU; or

[0893] - if no new RLC SDU can be transmitted after the transmission of the AMD PDU (e.g. due to window stalling);

[0894] - include a poll in the AMD PDU as described below.

[0895] NOTE: Empty RLC buffer (excluding transmitted RLC SDUs or RLC SDU segments awaiting acknowledgements) should not lead to unnecessary polling when data awaits in the upper layer. Details are left up to UE implementation.

[0896] To include a poll in an AMD PDU, the transmitting side of an AM RLC entity shall:

[0897] - set the P field of the AMD PDU to "1";

[0898] - set PDU_WITHOUT_POLL to 0;

[0899] - set BYTE_WITHOUT_POLL to 0.

[0900] Upon submission of an AMD PDU including a poll to lower layer, the transmitting side of an AM RLC entity shall:

[0901] - set POLL_SN to the highest SN of the AMD PDU among the AMD PDUs submitted to lower layer;

[0902] - if t-PollRetransmit is not running:

[0903] - start t-PollRetransmit.

[0904] - else:

[0905] - restart t-PollRetransmit.

[0906] Hereinafter, technical features related to NTZ are described.

[0907] INTRODUCTION

[0908] In CEPT countries, there is a fast-growing demand to operate aerial UE (User equipment) in particular under beyond-visual-line-of-sight (BVLOS) conditions, mainly for professional purposes. To enable these kinds of applications, there is the need for communication links between the aerial UE and mobile / fixed communication networks (MFCN) using bands harmonised for MFCN.

[0909] In this Decision, the term aerial UE refers to an UE supporting UAS features and services and requiring an aerial subscription. An aerial UE is installed either on-board an Unmanned Aircraft (e.g. drones) or on-board manned aircraft (e.g. helicopter). It identifies itself to the mobile network as being in this class.

[0910] Based on CEPT analysis, this ECC Decision provides harmonised technical conditions for the usage of aerial UE for communications 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. This framework does not address civil aviation regulation.

[0911] BACKGROUND

[0912] Further to market demands expressed during a CEPT workshop on 29-30 May 2018, ECC analysed the conditions for the usage of aerial UE for communications in the following MFCN harmonised bands: 700 MHz, 800 MHz, 900 MHz, 1800 MHz, 2 GHz, 2.6 GHz, 3.4-3.8 GHz (with AAS BS scenario only for that band). Such studies only considered scenarios where one UE is located on the flying platform.

[0913] After the approval of ECC Report 309, ECC recognised a demand for further studies of aerial UE connected to 5G NR AAS base stations on the ground in the 1.8 GHz, 2 GHz and 2.6 GHz frequency bands and developed ECC Report 348 accordingly.

[0914] The communication links of aerial UE are intended to be used primarily for data communication within MFCN bands.

[0915] This ECC Decision has been developed on the basis of assumptions, analysis and main conclusions of ECC Report 309 and ECC Report 348. These Reports assume that aerial UE use data payload. For aerial UE that do not use data payload (i.e. command and control aerial UE only) less stringent regulatory provisions might be applicable but further studies are required before these provisions can be relaxed.

[0916] In accordance with market demands and in order to use a technology widely available, the initial ECC studies (ECC Report 309) mainly focused on LTE which provides extensive MFCN coverage in CEPT countries. Additional analysis included in the ECC Report 348 extended conclusions of ECC Report 309 for the usage of aerial UE in the 1.8 GHz, 2.1 GHz and 2.6 GHz frequency bands with MFCN AAS base stations. ECC Report 348 also includes a technology comparison between LTE and 5G NR. Based on this analysis, technical and operational conditions such as OOBE limits or no-transmit zone based on the studies from the ECC Report 309 are valid for both LTE and 5G NR aerial UE.

[0917] This harmonised framework is limited to these two MFCN technologies which are already deployed and available in different MFCN frequency bands. Studies have been performed based on standardised LTE and 5G NR UE with usage of aerial UE operating up to 10000 m altitude with the assumption of usage of already existing MFCN base stations (BS), which are typically deployed to provide effective coverage at ground level. At this stage, ECC noted that mobile operators do not intend to develop specific network planning to respond to these new aerial use cases.

[0918] In addition to the already harmonised technical conditions for MFCN bands and for spectrum compatibility purposes, there is the need to define some spectrum operational restrictions. This can be done using "no-transmit zones", which should be defined at national level as a geographical area where aerial UE are not allowed to operate in a certain frequency band. Another measure to achieve coexistence is to define additional OOB emission limits specific to aerial UE (to avoid interference to other services in some other bands (e.g. to protect MetSat at 1675-1710 MHz) . The requirement may apply to aerial UE according to their operational frequency band, e.g. aerial UE operating in a specific band or specific channel. In some cases, operation of aerial UE also requires respective cross-border coordination agreements.

[0919] The defined spectrum operational restrictions and / or additional emission limits are mostly independent from the used MFCN technology. Even though ECC Report 309 studies focused on LTE technology, there is no fundamental difference between LTE and 5G NR (non-AAS). Therefore, the conclusions in ECC Report 309 are valid for both and are confirmed in ECC Report 348.

[0920] FRMCS cab-radio receivers at 1900-1910 MHz are assumed to be designed in a way that ensures robustness against blocking signals emitted by aerial UE.

[0921] Regarding the 2 GHz band (1920-1980 MHz), ECC Report 309 contains several studies, which used different methodologies and assumptions for the number of aerial UE and consequently has different options for the regulatory measures to provide compatibility. This Decision is based on the "Approach 2" option of ECC Report 309.

[0922] The coexistence conditions have been developed under the assumption that there is the mechanism to differentiate between an aerial UE and a conventional UE and this mechanism cannot be changed by the end-user. A mechanism is necessary to ensure that aerial UE respect no-transmit zones.

[0923] In addition, to manage the potential interference to MFCN, the control of aerial UE density may be necessary.

[0924] There is no interference between neighbouring FDD MFCN networks operating in adjacent channels.

[0925] As is the case for other UE operating under the control of an MFCN network, the aerial UE usage on MFCN networks may benefit from international roaming.

[0926] ECC noted that the following frequency bands: 703-733 MHz, 832-862 MHz, 880-915 MHz, 2500-2570 MHz, 2570-2620 MHz and 3400-3600 MHz are allocated to Mobile except aeronautical mobile service in Region 1 (Radio Regulations). Nevertheless, studies performed by CEPT in ECC Report 309 and ECC Report 348 provide the technical and operational background conditions which form the basis for this ECC Decision providing a harmonised framework to be implemented on national basis. In addition, CEPT will develop relevant guidance for usage of aerial UE at the border usages. These ECC deliverables are providing operational and technical conditions for use of aerial UE as an application in these frequency bands avoiding harmful interference into services in-band and in adjacent bands.

[0927] The next review of this ECC Decision will assess relevant impact of technology evolution, mechanisms to enable aerial UE to respect the frequency band dependent no-transmit-zones, specific aerial UE use case scenarios and will consider if the band 3.4-3.8 GHz can be included in this Decision.

[0928] REQUIREMENT FOR AN ECC DECISION

[0929] To ensure confidence of all spectrum users, including those in adjacent bands, there is a need for an ECC decision providing harmonised technical conditions of the usage of aerial UE for communications based on 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.

[0930] ECC Decision on Harmonised technical conditions for the usage of aerial UE for communications based on LTE and 5g NR in the 703-733 MHz, 832-862 MHz, 880-915 MHz ,1710-1785 MHz, 1920-1980 MHz, 2500-2570 MHz and 2570-2620 MHz MFCN harmonised bands (ECC decision (22)07)

[0931] Meanwhile, there is a specific area where the transmission on a certain frequency resource is prohibited by the national regulation or mobile network operator's requirement. For example, a no-transmit-zone (NTZ) is one kind of specific area for the aerial UE. The aerial UE has prior knowledge of the NTZ to observe the national regulation. Within the specific area, UE is prohibited to transmit a signal on a frequency or a frequency band associated with the specific area. The UE cannot transmit feedback for DL transmission in this area. As a result, the UE may not be able to receive downlink data properly requiring feedback for DL transmission.

[0932] If feedback of downlink signal is not required within the specific area, the UE may be able to receive downlink data even if it is within the specific area. However, the network may not know whether the UE is within the specific area or not, even though the network may have flight path of the UE and the information about the specific area. Therefore, the UE and the network may have different understanding about feedback operation for DL transmission.

[0933] Therefore, studies for supporting DL-only operation are required.

[0934] Hereinafter, a method for supporting DL-only operation, according to some embodiments of the present disclosure, will be described with reference to the following drawings.

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

[0936] FIG. 13 shows an example of a method for supporting DL-only operation, according to some embodiments of the present disclosure.

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

[0938] In step S1301, the wireless device may transmit, to a network, assistance information informing that the wireless device is going to enter a specific area.

[0939] For example, the specific area may be a zone in which uplink data transmission from the wireless device is not allowed.

[0940] For example, the wireless device may estimate at least one time point at which the wireless device enters or leaves the specific area. The wireless device may estimate at least one time point at which the wireless device enters or leaves the specific area based on a current location, a flight path, and a velocity.

[0941] For example, the wireless device may estimate at least one time point at which the wireless device enters or leaves the specific area and / or a time duration in which the wireless device stays in the specific area.

[0942] For example, the assistance information may include information related to at least one time point at which the wireless device enters or leaves the specific area.

[0943] For example, the assistance information may include information related to a time duration in which the wireless device stays in the specific area.

[0944] For example, the assistance information may include information related to at least one frequency for the specific area.

[0945] For example, the assistance information may be transmitted to the network via a radio resource control message. For example, the radio resource control message may include a UEAssistanceInformation message.

[0946] For example, the wireless device may receive, to a network, a first feedback configuration includes information informing that feedback for downlink transmission is required. The wireless device may apply the first feedback configuration based on the wireless device being not in the specific area. That is, the wireless device may perform feedback operation (For example, a HARQ feedback procedure) in response to the downlink transmission.

[0947] For example, the wireless device may initiate transmission of the assistance information before entering the specific area. For example, the wireless device may initiate transmission of the assistance information after leaving the specific area.

[0948] In step S1302, the wireless device may disable feedback related to downlink transmission while in the specific area.

[0949] For example, the wireless device may receive, from the network, a second feedback configuration including information related to disabling feedback for downlink transmission. For example, the wireless device may apply the second feedback configuration upon entering the specific area.

[0950] In step S1303, the wireless device may receive, from the network, downlink transmission while in the specific area without performing feedback related to the downlink transmission.

[0951] For example, since the wireless device disables the feedback in response to downlink transmission, the wireless device may perform downlink transmission without performing feedback operation.

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

[0953] Hereinafter, technical features for assisting DL-only operation of UE in a specific area are described.

[0954] In the present disclosure, UE transmits an assistance information to inform whether it is going to enter or outside of a special area to network. The network disables feedback for DL transmission of the UE based on the assistance information. Alternatively, the UE decides to disable HARQ feedback and notifies it to the network to synchronize their behavior about disabled HARQ feedback for downlink transmission.

[0955] FIG. 14 shows an example of a method for assisting DL-only operation in a specific area.

[0956] In particular, FIG. 14 illustrates a method performed by a User Equipment (UE).

[0957] In FIG. 14, UE autonomously disables feedback for DL transmission and informs that it is going to enter or leaves the specific area to the network.

[0958] In step S1401, UE may estimate when the UE enters or leaves the specific area based on its current location, flight path, and velocity.

[0959] 1> Estimated time may be an absolute time (e.g., UTC time).

[0960] 1> Estimated time may be a relative period (e.g. seconds, minutes, hours, days) and reference time.

[0961] 2> Estimated time can be converted to remaining distance until the UE enters or leaves the specific area.

[0962] In step S1402, UE may set an assistance information as follows.

[0963] 1> The UE may set the assistance information based on the estimated time derived in step S1401.

[0964] 2> If the estimated time is less than time threshold, the UE sets the assistance information.

[0965] 3> The time threshold can be

[0966] 4> determined by UE itself.

[0967] 4> determined by pre-determined value in a specification

[0968] 4> provided by the network.

[0969] 2> If the time is estimated time or the estimated time is passed, the UE sets the assistance information.

[0970] 2> If the remaining distance is less than distance threshold, the UE sets the assistance information.

[0971] 3> The distance threshold can be determined by UE itself.

[0972] 3> The distance threshold can be determined by pre-determined value in a specification

[0973] 3> The distance threshold can be provided by the network.

[0974] 1> The assistance information consists of

[0975] 2> Indicator whether the UE is going to enter or outside of the specific area.

[0976] 3> The indicator may be a flag.

[0977] 4> For example,

[0978] 5> If the indicator is set to true, the UE is going to enter the specific area.

[0979] 5> If the indicator is set to false, the UE is outside of the specific area.

[0980] 5> Or vice versa.

[0981] 3> The indicator may be pair of absolute time point and relative time duration.

[0982] 4> The reference time.

[0983] 5> The reference time may be represented by UTC time.

[0984] 4> The estimated remaining time to enter the specific area.

[0985] 5> The estimated remaining time may be represented by relative period (e.g. seconds, minutes, hours, days).

[0986] 3> The indicator may be absolute time point.

[0987] 4> The estimated time to enter the specific area.

[0988] 5> The estimated time may be represented by UTC time.

[0989] 2> Estimated location information of entering / leaving a specific area

[0990] 2> Carrier frequency or frequency band associated with the specific area.

[0991] 3> The carrier frequency may be represented by ARFCN value.

[0992] 3> The frequency band may be represented by frequency band indicator.

[0993] In step S1403, UE may transmit the assistance information to network when the UE enters or leaves the specific zone.

[0994] The assistance information may be transmitted via RRC message, e.g., UEAssistanceInformation or new RRC message.

[0995] In step S1404, UE may apply the configuration of feedback for DL transmission autonomously.

[0996] 1> The configuration consists of

[0997] 2> If the UE enters the specific area, the UE disables feedback for DL transmission.

[0998] 2> If the UE leaves the specific area, the UE enables feedback for DL transmission.

[0999] In step S1405, UE may estimate when the UE enters or leaves the specific area based on its current location, flight path, and velocity.

[1000] That is, in step S1405, UE may go back to step S1401.

[1001] For example, when the UE disables feedback for DL transmission,

[1002] 1> HARQ RTT Timer

[1003] 2> it may stop / expire HARQ RTT Timer for DL-SCH transmission received previously

[1004] 2> it may not start HARQ RTT Timer for DL-SCH transmission received

[1005] 1> Decoding result check

[1006] 2> it may not check decoding results

[1007] 2> it may check decoding results (ACK or NACK) regardless of HARQ RTT Timer

[1008] 2> if the UE keeps the HARQ RTT Timer, it may check decoding result (ACK or NACK) after HARQ RTT Timer is expired

[1009] 2> Decoding results may be utilized in Carrier Aggregation and / or Dual Connectivity Scenario

[1010] 2> Decoding results may be utilized to determine whether QoS satisfaction is confirmed

[1011] 3> If the QoS is not satisfied, the UE can bar the corresponding frequency and / or cell

[1012] 3> If the QoS is not satisfied, the UE can perform Radio Link Failure / RRC re-establishment procedure

[1013] 1> Retransmission Timer

[1014] 2> it may not start Retransmission Timer

[1015] 2> it may start Retransmission Timer depending on decoding results. It may be utilized Carrier Aggregation and / or Dual Connectivity Scenario

[1016] For example, in Carrier Aggregation and / or Dual Connectivity Scenario,

[1017] 1> it may send HARQ feedback (decoding result) for a carrier via another carrier with non-restricted frequency band

[1018] 1> it may send HARQ feedback (decoding result) for a cell group via another cell group with non-restricted frequency band

[1019] FIG. 15 shows an example of a method for assisting DL-only operation in a specific area.

[1020] In particular, FIG. 15 illustrates a method performed by a User Equipment (UE).

[1021] In FIG. 15, network disables HARQ feedback based on assistance information.

[1022] In step S1501, UE may estimate when the UE enters or leaves the specific area based on its current location, flight path and velocity.

[1023] 1> Estimated time may be an absolute time (e.g., UTC time).

[1024] 1> Estimated time may be a relative period (e.g. seconds, minutes, hours, days) and reference time.

[1025] 2> Estimated time can be converted to remaining distance until the UE enters or leaves the specific area.

[1026] In step S1502, UE may set an assistance information as follows.

[1027] 1> The UE may set the assistance information based on the estimated time or remaining distance derived in step S1501.

[1028] 2> If the estimated time is less than time threshold, the UE sets the assistance information.

[1029] 3> The time threshold can be

[1030] 4> determined by UE itself.

[1031] 4> provided by the network.

[1032] 2> If the time is estimated time or the estimated time is passed, the UE sets the assistance information.

[1033] 2> If the remaining distance is less than distance threshold, the UE sets the assistance information.

[1034] 3> The distance threshold can be determined by UE itself.

[1035] 3> The distance threshold can be provided by the network.

[1036] The assistance information consists of

[1037] 2> Indicator whether the UE is going to enter the specific area or not.

[1038] 3> The indicator may be an flag.

[1039] 4> For example,

[1040] 5> If the indicator is set to true, the UE is going to enter the specific area.

[1041] 5> If the indicator is set to false, the UE is outside of the specific area.

[1042] 5> Or vice versa.

[1043] 3> The indicator may be pair of absolute time point and relative time duration.

[1044] 4> The reference time.

[1045] 5> The reference time may be represented by UTC time.

[1046] 4> The estimated remaining time to enter the specific area.

[1047] 5> The estimated remaining time may be represented by relative period (e.g. seconds, minutes, hours, days).

[1048] 3> The indicator may be an absolute time point.

[1049] 4> The estimated time to enter the specific area.

[1050] 5> The estimated time may be represented by UTC time.

[1051] 2> Carrier frequency or frequency band associated with the specific area.

[1052] 3> The carrier frequency may be represented by ARFCN value.

[1053] 3> The frequency band may be represented by frequency band indicator.

[1054] In step S1503, UE may transmit the assistance information to network.

[1055] 1> The assistance information may be transmitted via RRC message, e.g., UEAssistanceInformation or new RRC message.

[1056] In step S1504, UE may receive a configuration of feedback for DL transmission from the network.

[1057] In step S1505, UE may apply feedback configuration for DL transmission.

[1058] In step S1506, UE may estimate when the UE enters or leaves the specific area based on its current location, flight path, and velocity.

[1059] That is, in step S1506, UE may go back to step S1501.

[1060] FIG. 16 shows an example of a method for assisting DL-only operation in a specific area.

[1061] In particular, FIG. 16 illustrates a method performed by a UE in a wireless communication system.

[1062] In step S1601, UE may set the assistance information based on its current location, flight path and velocity.

[1063] The assistance information may consist of an indicator whether the UE is going to enter the specific area or not, and carrier frequency or frequency band associated with the specific area.

[1064] In step S1602, UE may transmit the assistance information to the network.

[1065] In step S1603, UE may receive a configuration of feedback for DL transmission from the network.

[1066] In step S1604, UE may apply the configuration of feedback for DL transmission.

[1067] FIG. 17 shows an example of a method for assisting DL-only operation in a specific area.

[1068] In particular, FIG. 17 illustrates a method performed by a UE in a wireless communication system.

[1069] In step S1701, UE may set the assistance information based on its current location, flight path and velocity.

[1070] The assistance information may consist of an indicator whether the UE is going to enter the specific area or not, and carrier frequency or frequency band associated with the specific area.

[1071] In step S1702, UE may transmit the assistance information to the network.

[1072] In step S1703, UE may apply the configuration of feedback for DL transmission autonomously.

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

[1074] Hereinafter, an apparatus for supporting DL-only operation, 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, 5, and 10.

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

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

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

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

[1079] The operations comprise: transmitting, to a network, assistance information informing that the wireless device is going to enter a specific area, wherein the specific area is a zone in which uplink data transmission from the wireless device is not allowed; disabling feedback related to downlink transmission while in the specific area; and receiving, from the network, downlink transmission while in the specific area without performing feedback related to the downlink transmission.

[1080] For example, the operations comprises: estimating at least one time point at which the wireless device enters or leaves the specific area.

[1081] For example, the assistance information includes information related to at least one time point at which the wireless device enters or leaves the specific area.

[1082] For example, the assistance information includes information related to a time duration in which the wireless device stays in the specific area.

[1083] For example, the assistance information includes information related to at least one frequency for the specific area.

[1084] For example, the assistance information is transmitted to the network via a radio resource control message.

[1085] For example, the operations comprises: receiving, to a network, a first feedback configuration includes information informing that feedback for downlink transmission is required.

[1086] For example, the operations comprises: applying, by the wireless device, the first feedback configuration based on the wireless device being not in the specific area.

[1087] For example, the operations comprises: receiving, from the network, a second feedback configuration including information related to disabling feedback for downlink transmission.

[1088] For example, the operations comprises: applying, by the wireless device, the second feedback configuration upon entering the specific area.

[1089] For example, the operations comprises: initiating transmission of the assistance information before entering the specific area.

[1090] For example, the operations comprises: initiating transmission of the assistance information after leaving the specific area.

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

[1092] Hereinafter, a processor for a wireless device for supporting DL-only operation, according to some embodiments of the present disclosure, will be described.

[1093] The processor may be adapted to control the wireless device to perform operations.

[1094] The operations comprise: transmitting, to a network, assistance information informing that the wireless device is going to enter a specific area, wherein the specific area is a zone in which uplink data transmission from the wireless device is not allowed; disabling feedback related to downlink transmission while in the specific area; and receiving, from the network, downlink transmission while in the specific area without performing feedback related to the downlink transmission.

[1095] For example, the operations comprises: estimating at least one time point at which the wireless device enters or leaves the specific area.

[1096] For example, the assistance information includes information related to at least one time point at which the wireless device enters or leaves the specific area.

[1097] For example, the assistance information includes information related to a time duration in which the wireless device stays in the specific area.

[1098] For example, the assistance information includes information related to at least one frequency for the specific area.

[1099] For example, the assistance information is transmitted to the network via a radio resource control message.

[1100] For example, the operations comprises: receiving, to a network, a first feedback configuration includes information informing that feedback for downlink transmission is required.

[1101] For example, the operations comprises: applying, by the wireless device, the first feedback configuration based on the wireless device being not in the specific area.

[1102] For example, the operations comprises: receiving, from the network, a second feedback configuration including information related to disabling feedback for downlink transmission.

[1103] For example, the operations comprises: applying, by the wireless device, the second feedback configuration upon entering the specific area.

[1104] For example, the operations comprises: initiating transmission of the assistance information before entering the specific area.

[1105] For example, the operations comprises: initiating transmission of the assistance information after leaving the specific area.

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

[1107] Hereinafter, a non-transitory computer-readable medium has stored thereon a plurality of instructions for supporting DL-only operation, according to some embodiments of the present disclosure, will be described.

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

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

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

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

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

[1113] 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. The stored a plurality of instructions may cause the wireless device to perform operations.

[1114] The operations comprise: transmitting, to a network, assistance information informing that the wireless device is going to enter a specific area, wherein the specific area is a zone in which uplink data transmission from the wireless device is not allowed; disabling feedback related to downlink transmission while in the specific area; and receiving, from the network, downlink transmission while in the specific area without performing feedback related to the downlink transmission.

[1115] For example, the operations comprises: estimating at least one time point at which the wireless device enters or leaves the specific area.

[1116] For example, the assistance information includes information related to at least one time point at which the wireless device enters or leaves the specific area.

[1117] For example, the assistance information includes information related to a time duration in which the wireless device stays in the specific area.

[1118] For example, the assistance information includes information related to at least one frequency for the specific area.

[1119] For example, the assistance information is transmitted to the network via a radio resource control message.

[1120] For example, the operations comprises: receiving, to a network, a first feedback configuration includes information informing that feedback for downlink transmission is required.

[1121] For example, the operations comprises: applying, by the wireless device, the first feedback configuration based on the wireless device being not in the specific area.

[1122] For example, the operations comprises: receiving, from the network, a second feedback configuration including information related to disabling feedback for downlink transmission.

[1123] For example, the operations comprises: applying, by the wireless device, the second feedback configuration upon entering the specific area.

[1124] For example, the operations comprises: initiating transmission of the assistance information before entering the specific area.

[1125] For example, the operations comprises: initiating transmission of the assistance information after leaving the specific area.

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

[1127] Hereinafter, a method performed by a base station (BS) for supporting DL-only operation, according to some embodiments of the present disclosure, will be described.

[1128] The method comprises: receiving, by a base station from a wireless device, assistance information informing that the wireless device is going to enter a specific area, wherein the specific area is a zone in which uplink data transmission from the wireless device is not allowed, and wherein the wireless device disables feedback related to downlink transmission while in the specific area; and transmitting, by the base station to the wireless device, downlink transmission while in the specific area without performing feedback related to the downlink transmission.

[1129] Hereinafter, a base station (BS) for supporting DL-only operation, according to some embodiments of the present disclosure, will be described.

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

[1131] The processor may be adapted to control the transceiver to perform operations. The operations comprises: receiving, from a wireless device, assistance information informing that the wireless device is going to enter a specific area, wherein the specific area is a zone in which uplink data transmission from the wireless device is not allowed, and wherein the wireless device disables feedback related to downlink transmission while in the specific area; and transmitting, to the wireless device, downlink transmission while in the specific area without performing feedback related to the downlink transmission.

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

[1133] According to some embodiments of the present disclosure, the wireless device could efficiently support DL-only operation in a specific area.

[1134] For example, the wireless device can receive DL transmission without feedback within the specific area.

[1135] For example, the wireless device can improve DL transmission efficiency by performing DL data transmission without feedback in no transmission zone (NTZ).

[1136] According to some embodiments of the present disclosure, the wireless communication system could provide an efficient solution for assisting DL-only operation of a wireless device in a specific area.

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

[1138] 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, comprising:transmitting, by a wireless device to a network, assistance information informing that the wireless device is going to enter a specific area,wherein the specific area is a zone in which uplink data transmission from the wireless device is not allowed;disabling, by the wireless device, feedback related to downlink transmission while in the specific area; andreceiving, by the wireless device from the network, downlink transmission while in the specific area without performing feedback related to the downlink transmission.2.The method of claim 1, wherein the method further comprising:estimating, by the wireless device, at least one time point at which the wireless device enters or leaves the specific area.3.The method of claim 1,wherein the assistance information includes information related to at least one time point at which the wireless device enters or leaves the specific area.4.The method of claim 1,wherein the assistance information includes information related to a time duration in which the wireless device stays in the specific area.5.The method of claim 1,wherein the assistance information includes information related to at least one frequency for the specific area.6.The method of claim 1,wherein the assistance information is transmitted to the network via a radio resource control message.7.The method of claim 1, wherein the method further comprising:receiving, by a wireless device to a network, a first feedback configuration includes information informing that feedback for downlink transmission is required.8.The method of claim 7, wherein the method further comprising:applying, by the wireless device, the first feedback configuration based on the wireless device being not in the specific area.9.The method of claim 1, wherein the method further comprising:receiving, by the wireless device from the network, a second feedback configuration including information related to disabling feedback for downlink transmission.10.The method of claim 9, wherein the method further comprising:applying the second feedback configuration upon entering the specific area.11.The method of claim 1, wherein the method further comprising:initiating, by the wireless device, transmission of the assistance information before entering the specific area.12.The method of claim 1, wherein the method further comprising:initiating, by the wireless device, transmission of the assistance information after leaving the specific area.13.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.14.A wireless device, 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:transmitting, to a network, assistance information informing that the wireless device is going to enter a specific area,wherein the specific area is a zone in which uplink data transmission from the wireless device is not allowed;disabling feedback related to downlink transmission while in the specific area; andreceiving, from the network, downlink transmission while in the specific area without performing feedback related to the downlink transmission.15.The wireless device of claim 14, wherein the operations further comprising:estimating at least one time point at which the wireless device enters or leaves the specific area.16.The wireless device of claim 14,wherein the assistance information includes information related to at least one time point at which the wireless device enters or leaves the specific area.17.The wireless device of claim 14,wherein the assistance information includes information related to a time duration in which the wireless device stays in the specific area.18.The wireless device of claim 14,wherein the assistance information includes information related to at least one frequency for the specific area.19.The wireless device of claim 14,wherein the assistance information is transmitted to the network via a radio resource control message.20.The wireless device of claim 14, wherein the operations further comprising:receiving, to a network, a first feedback configuration includes information informing that feedback for downlink transmission is required.21.The wireless device of claim 20, wherein the operations further comprising:applying, by the wireless device, the first feedback configuration based on the wireless device being not in the specific area.22.The wireless device of claim 14, wherein the operations further comprising:receiving, from the network, a second feedback configuration including information related to disabling feedback for downlink transmission.23.The wireless device of claim 22, wherein the operations further comprising:applying, by the wireless device, the second feedback configuration upon entering the specific area.24.The wireless device of claim 14, wherein the operations further comprising:initiating transmission of the assistance information before entering the specific area.25.The wireless device of claim 14, wherein the operations further comprising:initiating transmission of the assistance information after leaving the specific area.26.The wireless device of claim 14,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.27.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:transmitting, to a network, assistance information informing that the wireless device is going to enter a specific area,wherein the specific area is a zone in which uplink data transmission from the wireless device is not allowed;disabling feedback related to downlink transmission while in the specific area; andreceiving, from the network, downlink transmission while in the specific area without performing feedback related to the downlink transmission.28.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,transmitting, to a network, assistance information informing that the wireless device is going to enter a specific area,wherein the specific area is a zone in which uplink data transmission from the wireless device is not allowed;disabling feedback related to downlink transmission while in the specific area; andreceiving, from the network, downlink transmission while in the specific area without performing feedback related to the downlink transmission.29.A method, the method comprising,receiving, by a base station from a wireless device, assistance information informing that the wireless device is going to enter a specific area,wherein the specific area is a zone in which uplink data transmission from the wireless device is not allowed, andwherein the wireless device disables feedback related to downlink transmission while in the specific area; andtransmitting, by the base station to the wireless device, downlink transmission while in the specific area without performing feedback related to the downlink transmission.30.A base station, comprising:a transceiver;a memory; andat least one processor operatively coupled to the transceiver and the memory, and adapted to perform operations, the operations comprising:receiving, from a wireless device, assistance information informing that the wireless device is going to enter a specific area,wherein the specific area is a zone in which uplink data transmission from the wireless device is not allowed, andwherein the wireless device disables feedback related to downlink transmission while in the specific area; andtransmitting, to the wireless device, downlink transmission while in the specific area without performing feedback related to the downlink transmission.

Images