Method and apparatus for logging command type for ltm

Abstract

A method and apparatus for logging command type for LTM are provided. The wireless device triggers a mobility to a candidate cell based on a cell switch command or a conditional mobility configuration. The wireless device accesses the candidate cell. The wireless device logs first information and second information, wherein the first information includes information informing whether a random access procedure is used for accessing the candidate cell or not, and wherein the second information includes information informing whether the triggered mobility is either a mobility with a random access procedure or a mobility without a random access procedure.

Description

METHOD AND APPARATUS FOR LOGGING COMMAND TYPE FOR LTM

[0001] The present disclosure relates to a method and apparatus for logging command type for LTM.

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

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

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

[0005] In R19 SON / MDT, for MOB MRO, RAN2 made the following agreement but has not yet finalized more specific details: RAN2 include the specific access type in the RLF report, for example, whether it is RA-based or RA-less cell switch. FFS details, for example, if explicit or implicitly signalled.

[0006] We think that the RLF report should explicitly include the access type information for the attempted LTM cell switch. This is because, based on implicit access information, the network will not be able to accurately determine which access type the UE used for the entire LTM cell switch attempt in some cases.

[0007] A typical example is when the UE attempts a RACH-less LTM cell switch based on a dynamic grant (for example, DG-based RACH-less LTM). In this case, the UE receives a RACH-less LTM CSC (cell switch command) from the source cell and monitors the PDCCH in the target cell for the UL grant. However, for certain reasons from the network side, the target cell may command the UE to use RACH for LTM. Then, if RLF is detected in this case, the UE may include both RACH-less and RACH information as the access information. Without explicit access type information, the network cannot determine which access type the UE attempted until RLF unless the network receives this information explicitly.

[0008] By above reason, we think the implicit access type information will leave a fundamental lack of trust in the access type information reported by the UE seems not be enough. Thus, we think that the UE should log explicit access type information to provide clear information preventing any potential confusion from the network side.

[0009] In addition to introduce the explicit access type information, in the above example of DG-based RACH-less LTM, we confirmed that the UE may face a situation where RACH-less LTM CSC is commanded but RACH-based LTM should be performed. We think RAN2 need to consider more about this case where the UE actually tried different access type from the access type commanded by the network in LTM CSC.

[0010] In the above example, it is unclear whether the UE should log the RACH actually performed as the access type instead of the RACH-less commanded by the network. If the UE logs the access type as RACH, the network may not know that the LTM CSC has been indicated to RACH-less, the network may misunderstand that the cause of HOF / RLF is due to improper early synchronization before LTM. Otherwise, if the UE logs the access type as RACH-less, the network doesn't know that the UE had actually tried RACH based LTM until HOF occurs and the network may misunderstand that the UE failed RACH-less procedure during LTM.

[0011] Therefore, studies for logging command type for LTM are required.

[0012] In an aspect, a method is provided. The method comprises: receiving, by a wireless device from a network, a mobility configuration; triggering, by the wireless device, a mobility to a candidate cell based on a cell switch command or a conditional mobility configuration; accessing, by the wireless device, the candidate cell; and logging, by the wireless device, first information and second information, wherein the first information includes information informing whether a random access procedure is used for accessing the candidate cell or not, and wherein the second information includes information informing whether the triggered mobility is either a mobility with a random access procedure or a mobility without a random access procedure.

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

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

[0015] According to some embodiments of the present disclosure, the wireless device could efficiently log the command type for LTM.

[0016] For example, according to the present disclosure, since the UE can report both the access type information which has actually tried to perform mobility and the commanded access type information which was indicated by the mobility command to provide accurate access trial logging information to the network.

[0017] For example, based on the commanded access type information, the network can know which / how access type information should be provided to UEs which are in similar mobility situation.

[0018] For example, by logging whether RACH was indicated in the mobility command and logging whether RACH was actually performed during the access procedure, UE mobility can be efficiently controlled.

[0019] According to some embodiments of the present disclosure, the wireless communication system could provide an efficient solution for logging the command type for LTM.

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

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

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

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

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

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

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

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

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

[0029] FIG. 10 shows an example of an RRC connection establishment procedure.

[0030] FIG. 11 shows an example of an RRC reconfiguration procedure.

[0031] FIG. 12 shows an example of an RRC connection re-establishment procedure.

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

[0033] FIG. 14 shows an example of a method for logging command type for LTM, according to some embodiments of the present disclosure.

[0034] FIG. 15 shows an example of a method for logging command type for LTM.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0119] uNslotsymbNframe,uslotNsubframe,uslot01410111420221440431480841416016

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

[0121] uNslotsymbNframe,uslotNsubframe,uslot212404

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

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

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

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

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

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

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

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

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

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

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

[0133] Hereinafter, technical features related to mobility are described.

[0134] When the UE moves from the coverage area of one cell to another cell, at some point a serving cell change needs to be performed. Currently serving cell change is triggered by L3 measurements and is done by RRC signalling triggered Reconfiguration with Synchronisation for change of PCell and PSCell, as well as release add for SCells when applicable. All cases involve complete L2 (and L1) resets, leading to longer latency, larger overhead and longer interruption time than beam switch mobility. The goal of L1 / L2 mobility enhancements is to enable a serving cell change via L1 / L2 signalling, in order to reduce the latency, overhead and interruption time.

[0135] In Rel-17 Conditional PSCell change (CPC) / Conditional PSCell addition (CPA), a CPC / CPA-configured UE has to release the CPC / CPA configurations when completing random access towards the target PSCell. Hence the UE doesn't have a chance to perform subsequent CPC / CPA without prior CPC / CPA reconfiguration and re-initialization from the network. This will increase the delay for the cell change and increase the signaling overhead, especially in the case of frequent SCG changes when operating FR2. Therefore, MR-DC with selective activation of cell groups aims at enabling subsequent CPC / CPA after SCG change, without reconfiguration and re-initialization on the CPC / CPA preparation from the network. This results in a reduction of the signalling overhead and interrupting time for SCG change.

[0136] Currently, CHO and MR-DC cannot be configured simultaneously. This limits the usefulness of these two features when MR-DC is configured. If it is not completed in Rel-17, Rel-18 should specify mechanisms for CHO and MR-DC to be configured simultaneously. However, this alone may not be sufficient to optimise MR-DC mobility, as the radio link quality of the conditionally-configured PSCell may not be good enough or may not be the best candidate PSCell when the UE accesses the target PCell, and this may impact the UE throughput. To mitigate this throughput impact, Rel-18 CHO+MRDC can consider CHO including target MCG and multiple candidate SCGs for CPC / CPA.

[0137] The detailed objective of this work item are:

[0138] 1. To specify mechanism and procedures of L1 / L2 based inter-cell mobility for mobility latency reduction:

[0139] > Configuration and maintenance for multiple candidate cells to allow fast application of configurations for candidate cells [RAN2, RAN3]

[0140] > Dynamic switch mechanism among candidate serving cells (including SpCell and SCell) for the potential applicable scenarios based on L1 / L2 signalling [RAN2, RAN1]

[0141] > L1 enhancements for inter-cell beam management, including L1 measurement and reporting, and beam indication [RAN1, RAN2]

[0142] >> EarlyRAN2involvement is necessary, including the possibility of further clarifying the interaction between this bullet with the previous bullet

[0143] > Timing Advance management [RAN1, RAN2]

[0144] > CU-DU interface signaling to support L1 / L2 mobility, if needed [RAN3]

[0145] - FR2 specific enhancements are not precluded, if any.

[0146] - The procedure of L1 / L2 based inter-cell mobility are applicable to the following scenarios:

[0147] >> Standalone, CA andNR-DC case with serving cell change within one CG

[0148] >>Intra-DU case andintra-CU inter-DU case (applicable for Standalone and CA: no new RAN interfaces are expected)

[0149] >> Bothintra-frequency and inter-frequency

[0150] >> Both FR1 and FR2

[0151] >> Source and target cells may be synchronized or non-synchronized

[0152] 2. To specify mechanism and procedures of NR-DC with selective activation of the cell groups (at least for SCG) via L3 enhancements:

[0153] > To allow subsequent cell group change after changing CG without reconfiguration and re-initiation of CPC / CPA [RAN2, RAN3, RAN4]

[0154] - A harmonized RRC modelling approach for objectives 1 and 2 could be considered to minimize the workload inRAN2.

[0155] 3. For CHO including target MCG and target SCG in NR-DC [RAN3]:

[0156] > to specify data forwarding optimizations; and

[0157] > to specify, if needed, a solution to avoid unnecessary signaling exchange between source MN and target SN.

[0158] 4. To specify CHO including target MCG and candidate SCGs for CPC / CPA in NR-DC [RAN3, RAN2]

[0159] > CHO including target MCG and target SCG is used as the baseline

[0160] 5. To specify RRM core requirements for the following, as necessary [RAN4]:

[0161] > L1 / L2-based inter-cell mobility

[0162] > Enhanced CHO configurations addressed by this WI

[0163] 6. To specify RF requirements to cover inter-frequency L1 / L2-based mobility, as necessary [RAN4].

[0164] 7. To study and specify how to reuse the IDLE / INACTIVE mode measurement results which are to be reported during and / or after RRC connection setup / resume in order to improveSCell / SCGsetup delay [RAN4,RAN2], including:

[0165] > Availability and validation of the IDLE / INACTIVE mode measurement results to be reported [RAN4]; and

[0166] > Definition of correspondingRRMrequirements; and

[0167] > If necessary based onRAN4outcome, definition of corresponding signalling support.

[0168] -RAN4will coordinate in due course withRAN2to start the work.

[0169] - R4-2220415 serves as baseline for future work inRAN4

[0170] - With exception of the above scenarios, enhancements on IDLE / INACTIVE mode measurements and onUEbehavior in IDLE / INACTIVE mode are not in scope.

[0171] Hereinafter, technical features related to SON / MDT are described.

[0172] Self-Organising Networks (SON), which encompasses solutions for network self-configuration and self-optimisation, was introduced in LTE to support deployment of the system　and performance optimization.　SON / MDT for NR was first introduced in Rel-16 and new features enabled by data collection for SON / MDT in NR were enhanced in Rel-17 and Rel-18.

[0173] Taking the tangible commercial interests and the　stability　and　technological　maturity　into account, SON / MDT enhancements for some Rel-17 / Rel-18 new features are considered in Rel-19, potentially including MRO enhancement for LTM, CHO with candidate SCGs and Subsequent CPAC, SON / MDT enhancements for Intra NTN mobility, Network Slicing, etc.

[0174] Due to the time constraints, some of the features in the Rel-18 SON / MDT WID are postponed to Rel-19.

[0175] Therefore, this WI tackles SON / MDT enhancement for R18 mobility mechanisms, SON / MDT enhancements for new features introduced in Rel-17 / Rel-18 and Rel-18 leftover use cases.

[0176] The objective of this work item is to specify data collection enhancement in NR standalone and MR-DC for SON / MDT purpose. The specific objectives of this work item are:

[0177] - MRO enhancement for R18 mobility mechanisms, including, Lower layer triggered mobility (LTM), CHO with candidate SCGs, subsequent CPAC [RAN3, RAN2]:

[0178] > Specification of the inter-node information exchange, including possible enhancements to interfaces [RAN3]

[0179] > Identify and specify necessary UE reporting to enhance the mobility parameter tuning　[RAN2]

[0180] - Support of SON / MDT enhancements for [RAN3, RAN2]:

[0181] > Intra-NTN mobility

[0182] > Network Slicing

[0183] - Support of the leftovers in Rel-18 SON / MDT [RAN3, RAN2]:

[0184] > RACH optimization for SDT

[0185] > MHI Enhancement for SCG Deactivation / Activation

[0186] > MRO for MR-DC SCG failure

[0187] Hereinafter, technical features related to mobility are described. Sections of 3GPP TS 38.331 v18.2.0 may be referred.

[0188] Upon receivingSIB19in an NTN cell, the UE in RRC_CONNECTED shall:

[0189] 1> start or restart T430 for serving cell with the timer value set tontn-UlSyncValidityDurationfor the serving cell from the subframe indicated byepochTimefor the serving cell.

[0190] - UE should attempt to re-acquireSIB19before the end of the duration indicated byntn-UlSyncValidityDurationandepochTimeby UE implementation.

[0191] Satellite switch with resynchronization

[0192] A UE capable of hard satellite switch with resynchronization in RRC_CONNECTED initiates the procedure whenSatSwitchWithReSyncandt-Serviceare included inSIB19.

[0193] Upon initiating the procedure, the UE shall:

[0194] 1> ift-ServiceStartis included inSIB19and the UE supports soft satellite switch with resynchronization:

[0195] 2> start acquiring DL synchronization with the SpCell served by the satellite indicated byntn-ConfiginSatSwitchWithReSyncbetween the time indicated byt-ServiceStartand the time indicated byt-Servicefor the serving cell;

[0196] 1> upon the time indicated byt-Service:

[0197] 2> stop timer T430 if running;

[0198] 2> inform lower layers that UL synchronisation is lost due to satellite switch with resynchronization;

[0199] 2> synchronise to the DL of the SpCell served by the satellite indicated byntn-ConfiginSatSwitchWithReSync, if the UE has not previously synchronized to the DL of the SpCell;

[0200] 2> start timer T430 with the timer value set tontn-UlSyncValidityDurationfrom the subframe indicated byepochTimeinntn-ConfiginSatSwitchWithReSync;

[0201] 2> inform lower layers when UL synchronisation is obtained.

[0202] - UE should attempt to re-acquireSIB19after satellite switch with resynchronization. The exact time is left to UE implementation.

[0203] FIG. 10 shows an example of an RRC connection establishment procedure.

[0204] The purpose of this procedure is to establish an RRC connection. RRC connection establishment involves SRB1 establishment. The procedure is also used to transfer the initial NAS dedicated information / message from the UE to the network.

[0205] The network applies the procedure e.g.as follows:

[0206] - When establishing an RRC connection;

[0207] - When UE is resuming or re-establishing an RRC connection, and the network is not able to retrieve or verify the UE context. In this case, UE receivesRRCSetupand responds withRRCSetupComplete.

[0208] FIG. 11 shows an example of an RRC reconfiguration procedure.

[0209] 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 reconfiguration configuration, to add / modify / release LTM configuration, and to add / modify / release MP configuration. As part of the procedure, NAS dedicated information may be transferred from the Network to the UE.

[0210] Conditional Reconfiguration

[0211] The network configures the UE with one or more candidate target SpCells in the conditional reconfiguration. The UE evaluates the condition of each configured candidate target SpCell. The UE applies the conditional reconfiguration associated with one of the target SpCells which fulfils associated execution condition.

[0212] The network can also configure the UE with one or more candidate target PCells associated with one or more candidate target PSCells. The UE evaluates the conditions for the candidate target PCells and the associated candidate target PSCells in parallel and applies a target configuration that include PCell and PSCell for which the associated execution conditions are fullfiled. If there are multiple candidate PSCells associated with one candidate target PCell, the network provides multiple conditional configurations for the same candidate target PCell, i.e., each configuration contains one MCG configuration (for the same candidate target PCell) and one SCG configuration (for one of the multiple associated candidate PSCells). For this case, the network may also provide a complementary CHO only configuration, i.e., there is execution condition only for candidate PCell.

[0213] The network provides the configuration parameters for the target SpCell(s) in thecondRRCReconfig.

[0214] In NR-DC, the UE may receive two independentconditionalReconfiguration:

[0215] - aconditionalReconfigurationassociated with MCG, that is included in theRRCReconfigurationmessage received via SRB1; and

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

[0217] In this case:

[0218] - the UE maintains two independentVarConditionalReconfig, one associated with eachconditionalReconfiguration;

[0219] - the UE independently performs all the procedures for eachconditionalReconfigurationand the associatedVarConditionalReconfig, unless explicitly stated otherwise;

[0220] - the UE performs the procedures for theVarConditionalReconfigassociated with the same cell group like themeasConfig.

[0221] In EN-DC, theVarConditionalReconfigis associated with the SCG.

[0222] In NE-DC and when no SCG is configured, theVarConditionalReconfigis associated with the MCG.

[0223] FIG. 12 shows an example of an RRC connection re-establishment procedure.

[0224] The purpose of this procedure is to re-establish the RRC connection. A UE in RRC_CONNECTED, for which AS security has been activated with SRB2 and at least one DRB / multicast MRB setup or, for IAB and NCR, SRB2, may initiate the procedure in order to continue the RRC connection. The connection re-establishment succeeds if the network is able to find and verify a valid UE context or, if the UE context cannot be retrieved, and the network responds with anRRCSetup.

[0225] The network applies the procedure e.g as follows:

[0226] - When AS security has been activated and the network retrieves or verifies the UE context:

[0227] - to re-activate AS security without changing algorithms;

[0228] - to re-establish and resume the SRB1;

[0229] - When UE is re-establishing an RRC connection, and the network is not able to retrieve or verify the UE context:

[0230] - to discard the stored AS Context and release all RBs and BH RLC channels and Uu Relay RLC channels;

[0231] - to fallback to establish a new RRC connection.

[0232] If AS security has not been activated, the UE shall not initiate the procedure but instead moves to RRC_IDLE directly, with release cause 'other'. If AS security has been activated, but SRB2 and at least one DRB or multicast MRB or, for IAB and NCR, SRB2, are not setup, the UE does not initiate the procedure but instead moves to RRC_IDLE directly, with release cause 'RRC connection failure'.

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

[0234] The UE information procedure is used by the network to request the UE to report information.

[0235] The network initiates the procedure by sending theUEInformationRequestmessage. The network should initiate this procedure only after successful security activation.

[0236] Actions for the successful handover report determination

[0237] The UE shall for the PCell:

[0238] 1> if the procedure is triggered due to successful completion of reconfiguration with sync, and if the ratio between the value of the elapsed time of the timer T304 and the configured value of the timer T304, included in the last appliedRRCReconfigurationmessage including thereconfigurationWithSync, is greater thanthresholdPercentageT304if included in thesuccessHO-Configreceived before executing the last reconfiguration with sync; or

[0239] 1> if the procedure is triggered due to successful completion of reconfiguration with sync, and if the ratio between the value of the elapsed time of the timer T310 and the configured value of the timer T310, configured while the UE was connected to the source PCell before executing the last reconfiguration with sync, is greater thanthresholdPercentageT310included in thesuccessHO-Configif configured by the source PCell before executing the last reconfiguration with sync; or

[0240] 1> if the procedure is triggered due to successful completion of reconfiguration with sync, and if the T312 associated to the measurement identity of the target cell was running at the time of initiating the execution of the reconfiguration with sync procedure and if the ratio between the value of the elapsed time of the timer T312 and the configured value of the timer T312, configured while the UE was connected to the source PCell before executing the last reconfiguration with sync, is greater thanthresholdPercentageT312included in the successHO-Configif configured by the source PCell before executing the last reconfiguration with sync; or

[0241] 1> if the procedure is triggered due to successful completion of reconfiguration with sync, and ifsourceDAPS-FailureReportingis included in thesuccessHO-Configbefore executing the last reconfiguration with sync and is set totrueand if the last executed handover was a DAPS handover and if an RLF occurred at the source PCell during the DAPS handover while T304 was running; or:

[0242] 1> if the procedure is triggered due to successful completion of Mobility from NR to E-UTRA,and if the ratio between the value of the elapsed time of the timer T310 and the configured value of the timer T310, configured while the UE was connected to the source PCell before executing the last Mobility from NR to E-UTRA, is greater thanthresholdPercentageT310included in thesuccessHO-Configif configured by the source PCell before executing the last Mobility from NR to E-UTRA; or

[0243] 1> if the procedure is triggered due to successful completion of Mobility from NR to E-UTRA, and if the T312 associated to the measurement identity of the target cell was running at the time of initiating the execution of the Mobility from NR to E-UTRA and if the ratio between the value of the elapsed time of the timer T312 and the configured value of the timer T312, configured while the UE was connected to the source PCell before executing the last Mobility from NR to E-UTRA, is greater thanthresholdPercentageT312included in the successHO-Configif configured by the source PCell before executing the last Mobility from NR to E-UTRA:

[0244] 2> store the successful handover information inVarSuccessHO-Reportand determine the content inVarSuccessHO-Reportas follows:

[0245] 3> clear the information included inVarSuccessHO-Report, if any;

[0246] 3> if the UE is not in SNPN access mode, set theplmn-IdentityListto include the list of EPLMNs stored by the UE (i.e., includes the RPLMN);

[0247] 3> else if the UE is in SNPN access mode, set thesnpn-IdentityListto include the list of equivalent SNPNs stored by the UE (i.e., includes the registered SNPN identity), if available;

[0248] 3> set thec-RNTIto the C-RNTI assigned by the target PCell of the handover;

[0249] 3> if the procedure is triggered due to successful completion of reconfiguration with sync, for the source PCell in which the lastRRCReconfigurationmessage includingreconfigurationWithSyncwas applied; or

[0250] 3> if the procedure is triggered due to successful completion of Mobility from NR to E-UTRA, for the source PCell in which the lastMobilityFromNRCommandconcerning an inter-RAT handover from NR to E-UTRA was applied:

[0251] 4> set thesourcePCellIDinsourceCellInfoto the global cell identity and tracking area code, if available, of the source PCell;

[0252] 4> set thesourceCellMeasinsourceCellInfoto include the cell level RSRP, RSRQ and the available SINR, of the source PCell based on the available SSB and CSI-RS measurements collected up to the moment the UE sendsRRCReconfigurationCompletemessage if the procedure is triggered due to successful completion of reconfiguration with sync, or up to the moment the UE sends the EUTRARRCConnectionReconfigurationCompletemessage if the procedure is triggered due to successful completion of Mobility from NR to E-UTRA;

[0253] 4> set thersIndexResultsinsourceCellMeasto include all the available SSB and CSI-RS measurement quantities of the source PCell collected up to the moment the UE sendsRRCReconfigurationCompletemessage if the procedure is triggered due to successful completion of reconfiguration with sync, or up to the moment the UE sends the EUTRARRCConnectionReconfigurationCompletemessage if the procedure is triggered due to successful completion of Mobility from NR to E-UTRA;

[0254] 4> if the last executed handover was a DAPS handover and if an RLF occurred at the source PCell during the DAPS handover while T304 was running:

[0255] 5> set therlf-InSourceDAPSinsourceCellInfototrue;

[0256] 3> if the procedure is triggered due to successful completion of reconfiguration with sync, for the target PCell indicated in the last appliedRRCReconfigurationmessage includingreconfigurationWithSync:

[0257] 4> set thetargetPCellIDintargetCellInfoto the global cell identity and tracking area code, if available, of the target PCell;

[0258] 4> set thetargetCellMeasintargetCellInfoto include the cell level RSRP, RSRQ and the available SINR, of the target PCell based on the available SSB and CSI-RS measurements collected up to the moment the UE sendsRRCReconfigurationCompletemessage;

[0259] 4> set thersIndexResultsintargetCellMeasto include all the available SSB and CSI-RS measurement quantities of the target PCell collected up to the moment the UE sendsRRCReconfigurationCompletemessage;

[0260] 4> if the last appliedRRCReconfigurationmessage includingreconfigurationWithSyncwas included in the storedcondRRCReconfig:

[0261] 5> set thetimeSinceCHO-Reconfigto the time elapsed between the initiation of the execution of conditional reconfiguration for the target PCell and the reception of the lastconditionalReconfigurationincluding thecondRRCReconfigof the target PCell in the source PCell;

[0262] 3> if the procedure is triggered due to successful completion of Mobility from NR to E-UTRA, for the target PCell indicated in the last appliedMobilityFromNRCommandconcerning an inter-RAT handover from NR to E-UTRA:

[0263] 4> set thetargetPCellIdineutraTargetCellInfoto the global cell identity and tracking area code, if available, and otherwise to the physical cell identity and carrier frequency of the target PCell;

[0264] 4> set thetargetCellMeasineutraTargetCellInfoto include the cell level RSRP, RSRQ and the available SINR, of the target PCell based on the available measurements collected up to the moment the UE sendsRRCConnectionReconfigurationCompletemessage;

[0265] - IfeutraTargetCellInfois included, it is left to UE implementation how to set thetargetCellInfo.

[0266] 3> if the procedure is triggered due to successful completion of reconfiguration with sync and if the ratio between the value of the elapsed time of the timer T304 and the configured value of the T304 timer, included in the last appliedRRCReconfigurationmessage including thereconfigurationWithSync, is greater thanthresholdPercentageT304if included in thesuccessHO-Configreceived before executing the last reconfiguration with sync:

[0267] 4> sett304-causeinshr-Causetotrue;

[0268] 4> set thera-InformationCommonto include the random-access related information associated to the random access procedure in the target PCell, as specified in clause 5.7.10.5;

[0269] 3> if the ratio between the value of the elapsed time of the timer T310 and the configured value of the T310 timer, configured while the UE was connected to the source PCell before executing the last reconfiguration with sync or the last Mobility from NR to E-UTRA, is greater thanthresholdPercentageT310included in thesuccessHO-Configif configured by the source PCell before executing the last reconfiguration with sync or Mobility from NR to E-UTRA:

[0270] 4> sett310-causeinshr-Causetotrue;

[0271] 3> if the T312 associated to the measurement identity of the target cell was running at the time of initiating the execution of the reconfiguration with sync procedure or Mobility from NR to E-UTRA, and if the ratio between the value of the elapsed time of the timer T312 and the configured value of the T312 timer, configured while the UE was connected to the source PCell before executing the last reconfiguration with sync or Mobility from NR to E-UTRA, is greater thanthresholdPercentageT312included in the successHO-Configif configured by the source PCell before executing the last reconfiguration with sync, or Mobility from NR to E-UTRA:

[0272] 4> sett312-causeinshr-Causetotrue;

[0273] 3> if the procedure is triggered due to successful completion of reconfiguration with sync and ifsourceDAPS-FailureReportingincluded in thesuccessHO-Configif configured by the source PCell before executing the last reconfiguration with sync is set totrue, and if the last executed handover was a DAPS handover and if an RLF occurred at the source PCell during the DAPS handover while T304 was running:

[0274] 4> setsourceDAPS-Failureinshr-Causetotrue;

[0275] 3> if the procedure is triggered due to successful completion of reconfiguration with sync, for each of themeasObjectNR, configured by the source PCell, in which the lastRRCReconfigurationmessage includingreconfigurationWithSyncwas applied;or:

[0276] 3> if the procedure is triggered due to successful completion of Mobility from NR to E-UTRA, for each of themeasObjectNR, configured by the source PCell, in which the lastMobilityFromNRCommandconcerning an inter-RAT handover from NR to E-UTRA was applied:

[0277] 4> ifmeasRSSI-ReportConfigis configured for the frequency of the source PCell:

[0278] 5> if the procedure is triggered due to successful completion of reconfiguration with sync:

[0279] 6> set themeasResultServCell-RSSIto the linear average of the available RSSI sample value(s) provided by lower layers for the frequency of the source PCell up to the moment the UE sends theRRCReconfigurationCompletemessage

[0280] 5> else if the procedure is triggered due to successful completion of Mobility from NR to E-UTRA:

[0281] 6> set themeasResultServCell-RSSIto the linear average of the available RSSI sample value(s) provided by lower layers for the frequency of the source PCell up to the moment the UE sends the EUTRARRCConnectionReconfigurationCompletemessage;

[0282] 4> for each of the configuredmeasObjectNRifmeasRSSI-ReportConfigis configured for the configured frequency:

[0283] 5> if the procedure is triggered due to successful completion of reconfiguration with sync:

[0284] 6> set themeasResultNeighFreq-RSSIin themeasResultNeighFreqList-RSSIto the linear average of the available RSSI sample value(s) provided by lower layers for the associated neighbouring frequency up to the moment the UE sends theRRCReconfigurationCompletemessage;

[0285] 5> else if the procedure is triggered due to successful completion of Mobility from NR to E-UTRA:

[0286] 6> set themeasResultNeighFreq-RSSIin themeasResultNeighFreqList-RSSIto the linear average of the available RSSI sample value(s) provided by lower layers for the associated neighbouring frequency up to the moment the UE sends the EUTRARRCConnectionReconfigurationCompletemessage;

[0287] 4> if measurements are available for themeasObjectNR:

[0288] 5> if the SS / PBCH block-based measurement quantities are available:

[0289] 6> set themeasResultListNRinmeasResultNeighCellsto include all the available measurement quantities of the best measured cells, other than the source PCell or target PCell, ordered such that the cell with highest SS / PBCH block RSRP is listed first if SS / PBCH block RSRP measurement results are available, otherwise the cell with highest SS / PBCH block RSRQ is listed first if SS / PBCH block RSRQ measurement results are available, otherwise the cell with highest SS / PBCH block SINR is listed first, based on the available SS / PBCH block based measurements collected up to the moment the UE sends theRRCReconfigurationCompletemessage if the procedure is triggered due to successful completion of reconfiguration with sync, or up to the moment the UE sends the EUTRARRCConnectionReconfigurationCompletemessage if the procedure is triggered due to successful completion of Mobility from NR to E-UTRA;

[0290] 6> for each neighbour cell included, include the optional fields that are available;

[0291] - For the neighboring cells set included inmeasResultListNRinmeasResultNeighCellsordered based on the SS / PBCH block measurement quantities, the UE includes also the CSI-RS based measurement quantities, if available.

[0292] 5> if the CSI-RS measurement quantities are available:

[0293] 6> set themeasResultListNRinmeasResultNeighCellsto include all the available measurement quantities of the best measured cells, other than the source PCell and target PCell, ordered such that the cell with highest CSI-RS RSRP is listed first if CSI-RS RSRP measurement results are available, otherwise the cell with highest CSI-RS RSRQ is listed first if CSI-RS RSRQ measurement results are available, otherwise the cell with highest CSI-RS SINR is listed first, based on the available CSI-RS based measurements collected up to the moment the UE sends theRRCReconfigurationCompletemessage if the procedure is triggered due to successful completion of reconfiguration with sync, or up to the moment the UE sends the EUTRARRCConnectionReconfigurationCompletemessage if the procedure is triggered due to successful completion of Mobility from NR to E-UTRA;

[0294] 6> for each neighbour cell included, include the optional fields that are available;

[0295] - For the neighboring cells set ordered based on the CSI-RS measurement quantities, the UE includes measurements only for the cells not yet included inmeasResultListNRinmeasResultNeighCellsto avoid overriding SS / PBCH block-based ordered measurements.

[0296] 3> if the procedure is triggered due to successful completion of reconfiguration with sync, for each of themeasObjectEUTRA, configured by the source PCell in which the lastRRCReconfigurationmessage includingreconfigurationWithSyncwas applied; or:

[0297] 3> if the procedure is triggered due to successful completion of Mobility from NR to E-UTRA, for each of themeasObjectEUTRA, configured by the source PCell in which the lastMobilityFromNRCommandconcerning an inter-RAT handover from NR to E-UTRA was applied:

[0298] 4> if measurements are available for themeasObjectEUTRA:

[0299] 5> set themeasResultListEUTRAinmeasResultNeighCellsto include the best measured cells ordered such that the cell with highest RSRP is listed first if RSRP measurement results are available, otherwise the cell with highest RSRQ is listed first, based on measurements collected up to the moment the UE sends theRRCReconfigurationCompletemessage if the procedure is triggered due to successful completion of reconfiguration with sync, or up to the moment the UE sends the EUTRARRCConnectionReconfigurationCompletemessage if the procedure is triggered due to successful completion of Mobility from NR to E-UTRA;

[0300] 5> for each neighbour cell included, include the optional fields that are available;

[0301] 3> for each of the neighbour cells included inmeasResultNeighCells:

[0302] 4> if the cell was a candidate target cell included in thecondRRCReconfigwithin theconditionalReconfigurationconfigured by the source PCell, in which the lastRRCReconfigurationmessage includingreconfigurationWithSyncwas applied:

[0303] 5> set thechoCandidatetotrueinmeasResultNR;

[0304] 3> if available, set thelocationInfo;

[0305] 1> releasesuccessHO-Configconfigured by the source PCell andthresholdPercentageT304if configured by the target PCell.

[0306] The UE may discard the successful handover information, i.e., release the UE variableVarSuccessHO-Report, 48 hours after the last successful handover information is added to theVarSuccessHO-Report.

[0307] Actions for the successful PSCell change or addition report determination

[0308] The UE shall for the PSCell:

[0309] 1> if the ratio between the value of the elapsed time of the timer T304 and the configured value of the timer T304, included in the last appliedRRCReconfigurationmessage for the SCG including thereconfigurationWithSync, is greater thanthresholdPercentageT304-SCGif included in thesuccessPSCell-Configreceived before executing the last reconfiguration with sync for the SCG; or

[0310] 1> ifsn-InitiatedPSCellChangeis configured in theRRCReconfigurationincluding the last appliedRRCReconfigurationwithreconfigurationWithSyncfor the SCG and if the ratio between the value of the elapsed time of the timer T310 and the configured value of the timer T310, configured while the UE was connected to the source PSCell before executing the last reconfiguration with sync for the SCG, is greater thanthresholdPercentageT310-SCGincluded in thesuccessPSCell-Configif configured by the source PSCell before executing the last reconfiguration with sync for the SCG; or

[0311] 1> ifsn-InitiatedPSCellChangeis configured in theRRCReconfigurationincluding the last appliedRRCReconfigurationwithreconfigurationWithSyncfor the SCG and if the T312 associated to the measurement identity of the target PSCell was running at the time of initiating the execution of the reconfiguration with sync procedure for the SCG and if the ratio between the value of the elapsed time of the timer T312 and the configured value of the timer T312, configured while the UE was connected to the source PSCell before executing the last reconfiguration with sync, is greater thanthresholdPercentageT312-SCGincluded in the successPSCell-Configif configured by the source PSCell before executing the last reconfiguration with sync for the SCG:

[0312] 1> ifsn-InitiatedPSCellChangeis not configured in theRRCReconfigurationincluding the last appliedRRCReconfigurationwithreconfigurationWithSyncfor the SCG and if the ratio between the value of the elapsed time of the timer T310 and the configured value of the timer T310, configured while the UE was connected to the source PSCell before executing the last reconfiguration with sync for the SCG, is greater thanthresholdPercentageT310-SCGincluded in thesuccessPSCell-Configif configured by the PCell before executing the last reconfiguration with sync for the SCG; or

[0313] 1> ifsn-InitiatedPSCellChangeis not configured in theRRCReconfigurationincluding the last appliedRRCReconfigurationwithreconfigurationWithSyncfor the SCG and if the T312 associated to the measurement identity of the target PSCell was running at the time of initiating the execution of the reconfiguration with sync procedure for the SCG and if the ratio between the value of the elapsed time of the timer T312 and the configured value of the timer T312, configured while the UE was connected to the source PSCell before executing the last reconfiguration with sync, is greater thanthresholdPercentageT312-SCGincluded in the successPSCell-Configif configured by the PCell before executing the last reconfiguration with sync for the SCG:

[0314] 2> clear the information included inVarSuccessPSCell-Report, if any;

[0315] 2> store the successful PSCell change or addition information inVarSuccessPSCell-Reportand determine the content inVarSuccessPSCell-Reportas follows:

[0316] 3> if the UE is not in SNPN access mode, set theplmn-IdentityListto include the list of EPLMNs (including the RPLMN) stored by the UE;

[0317] 3> else if the UE is in SNPN access mode, set thesnpn-IdentityListto include the list of equivalent SNPN identities (including the registered SNPN identity) stored by the UE, if available;

[0318] 3> set thepCellIdto the global cell identity and tracking area code, if available, of the PCell;

[0319] 3> for the source PSCell (in case of PSCell change procedure) in which the lastRRCReconfigurationmessage for the SCG includingreconfigurationWithSyncwas applied:

[0320] 4> set thesourcePSCellIdinsourcePSCellInfoto the global cell identity and tracking area code, and otherwise to the physical cell identity and carrier frequency of the source PSCell;

[0321] 4> set thesourcePSCellMeasinsourcePSCellInfoto include the cell level RSRP, RSRQ and the available SINR, of the source PSCell based on the available SSB and CSI-RS measurements collected up to the moment the UE successfully completed the random access procedure for the SCG;

[0322] 4> set thersIndexResultsinsourcePSCellMeasto include all the available SSB and CSI-RS measurement quantities of the source PSCell collected up to the moment the UE successfully completed the random access procedure for the SCG;

[0323] 3> for the target PSCell indicated in the last appliedRRCReconfigurationmessage for the SCG includingreconfigurationWithSync:

[0324] 4> set thetargetPSCellIDintargetPSCellInfoto the global cell identity and tracking area code, if available, and otherwise to the physical cell identity and carrier frequency of the target PSCell;

[0325] 4> set thetargetPSCellMeasintargetPSCellInfoto include the cell level RSRP, RSRQ and the available SINR, of the target PSCell based on the available SSB and CSI-RS measurements collected up to the moment the UE successfully completed the random access procedure for the SCG;

[0326] 4> set thersIndexResultsintargetPSCellMeasto include all the available SSB and CSI-RS measurement quantities of the target PSCell collected up to the moment the UE successfully completed the random access procedure for the SCG;

[0327] 4> if the last appliedRRCReconfigurationmessage for the SCG includingreconfigurationWithSyncwas included in the storedcondRRCReconfig:

[0328] 5> set thetimeSinceCPAC-Reconfigto the time elapsed between the initiation of the execution of conditional reconfiguration for the target PSCell and the reception of the lastconditionalReconfigurationfor the SCG including thecondRRCReconfigof the target PSCell;

[0329] 3> if the ratio between the value of the elapsed time of the timer T304 and the configured value of the T304 timer, included in the last appliedRRCReconfigurationmessage for the SCG including thereconfigurationWithSync, is greater thanthresholdPercentageT304-SCGif included in thesuccessPSCell-Configreceived before executing the last reconfiguration with sync for the SCG:

[0330] 4> sett304-causeinspr-Causetotrue;

[0331] 4> set thera-InformationCommonto include the random-access related information associated to the random access procedure in the target PSCell, as specified in clause 5.7.10.5;

[0332] 3> if the ratio between the value of the elapsed time of the timer T310 and the configured value of the timer T310, configured while the UE was connected to the source PSCell before executing the last reconfiguration with sync for the SCG, is greater thanthresholdPercentageT310-SCGincluded in thesuccessPSCell-Configif configured before executing the last reconfiguration with sync:

[0333] 4> sett310-causeinspr-Causetotrue;

[0334] 3> if the T312 associated to the measurement identity of the target PSCell was running at the time of initiating the execution of the reconfiguration with sync procedure for the SCG and if the ratio between the value of the elapsed time of the timer T312 and the configured value of the timer T312, configured while the UE was connected to the source PSCell before executing the last reconfiguration with sync, is greater thanthresholdPercentageT312-SCGincluded in the successPSCell-Configif configured before executing the last reconfiguration with sync:

[0335] 4> sett312-causeinspr-Causetotrue;

[0336] 3> ifsn-InitiatedPSCellChangeis configured in theRRCReconfigurationincluding the last appliedRRCReconfigurationwithreconfigurationWithSyncfor the SCG:

[0337] 4> consider allmeasObjectNRconfigured by the the source PSCell;

[0338] 3> else:

[0339] 4> consider allmeasObjectNRconfigured by the the PCell;

[0340] 3> for each of the consideredmeasObjectNR:

[0341] 4> if measurements are available for themeasObjectNR:

[0342] 5> if the SS / PBCH block-based measurement quantities are available:

[0343] 6> include in themeasResultListNRinmeasResultNeighCellsall the available measurement quantities of the best measured cells, other than the source PSCell (in case of PSCell change procedure) or target PSCell, ordered such that the cell with highest SS / PBCH block RSRP is listed first if SS / PBCH block RSRP measurement results are available, otherwise the cell with highest SS / PBCH block RSRQ is listed first if SS / PBCH block RSRQ measurement results are available, otherwise the cell with highest SS / PBCH block SINR is listed first, based on the available SS / PBCH block based measurements collected up to the moment the UE successfully completed the random access procedure;

[0344] 6> for each neighbour cell included, include the optional fields that are available (including the CSI-RS based measurement quantities, if available);

[0345] 5> if the CSI-RS measurement quantities are available for the cells not yet included inmeasResultListNRinmeasResultNeighCells:

[0346] 6> include in themeasResultListNRinmeasResultNeighCellsall the available measurement quantities of the best measured cells, other than the source PSCell (in case of PSCell change procedure) and target PSCell, ordered such that the cell with highest CSI-RS RSRP is listed first if CSI-RS RSRP measurement results are available, otherwise the cell with highest CSI-RS RSRQ is listed first if CSI-RS RSRQ measurement results are available, otherwise the cell with highest CSI-RS SINR is listed first, based on the available CSI-RS based measurements collected up to the moment the UE successfully completed the random access procedure;

[0347] 6> for each neighbour cell included, include the optional fields that are available;

[0348] 3> for each of the neighbour cells included inmeasResultNeighCells:

[0349] 4> if the cell was a candidate target cell included in thecondRRCReconfigwithin theconditionalReconfiguration, configured by the source PCell or by the source PSCell (in case of PSCell change) when the lastRRCReconfigurationmessage for the SCG includingreconfigurationWithSyncwas applied:

[0350] 5> set thechoCandidatetotrueinmeasResultNR;

[0351] 3> ifsn-InitiatedPSCellChangeis configured in theRRCReconfigurationincluding the last appliedRRCReconfigurationwithreconfigurationWithSyncfor the SCG:

[0352] 4> if available, set thelocationInfoaccording to theotherConfigassociated with the source PSCell;

[0353] 4> includesn-InitiatedPSCellChange;

[0354] 3> else:

[0355] 4> if available, set thelocationInfoaccording to theotherConfigassociated with the PCell;

[0356] 1> releasesuccessPSCell-Configconfigured by the source PSCell if available andthresholdPercentageT304if configured by the target PSCell.

[0357] The UE may discard the successful PSCell change or addition information, i.e., release the UE variableVarSuccessPSCell-Report, 48 hours after the last successful PSCell change or addition information is added to theVarSuccessPSCell-Reportor upon deregistration from the network.

[0358] Radio link failure related actions

[0359] Detection of physical layer problems in RRC_CONNECTED

[0360] The UE shall:

[0361] 1> if any DAPS bearer is configured, upon receiving N310 consecutive "out-of-sync" indications for the source SpCell from lower layers and T304 is running:

[0362] 2> start timer T310 for the source SpCell.

[0363] 1> upon receiving N310 consecutive "out-of-sync" indications for the SpCell from lower layers while neither T300, T301, T304, T311, T316 nor T319 are running:

[0364] 2> start timer T310 for the corresponding SpCell.

[0365] Recovery of physical layer problems

[0366] Upon receiving N311 consecutive "in-sync" indications for the SpCell from lower layers while T310 is running, the UE shall:

[0367] 1> stop timer T310 for the corresponding SpCell.

[0368] 1> stop timer T312 for the corresponding SpCell, if running.

[0369] - In this case, the UE maintains the RRC connection without explicit signalling, i.e. the UE maintains the entire radio resource configuration.

[0370] - Periods in time where neither "in-sync" nor "out-of-sync" is reported by L1 do not affect the evaluation of the number of consecutive "in-sync" or "out-of-sync" indications.

[0371] Detection of radio link failure

[0372] The UE shall:

[0373] 1> if any DAPS bearer is configured and T304 is running:

[0374] 2> upon T310 expiry in source SpCell; or

[0375] 2> upon random access problem indication from source MCG MAC; or

[0376] 2> upon indication from source MCG RLC that the maximum number of retransmissions has been reached; or

[0377] 2> upon consistent uplink LBT failure indication from source MCG MAC:

[0378] 3> consider radio link failure to be detected for the source MCG i.e. source RLF;

[0379] 3> suspend the transmission and reception of all DRBs and multicast MRBs in the source MCG;

[0380] 3> reset MAC for the source MCG;

[0381] 3> release the source connection.

[0382] 1> else:

[0383] 2> during a DAPS handover: the following only applies for the target PCell;

[0384] 2> upon T310 expiry in PCell; or

[0385] 2> upon T312 expiry in PCell; or

[0386] 2> upon random access problem indication from MCG MAC while neither T300, T301, T304, T311 nor T319 are running and SDT procedure is not ongoing; or

[0387] 2> upon indication from MCG RLC that the maximum number of retransmissions has been reached while SDT procedure is not ongoing; or

[0388] 2> if connected as an IAB-node, upon BH RLF indication received on BAP entity from the MCG; or

[0389] 2> upon consistent uplink LBT failure indication from MCG MAC while T304 is not running:

[0390] 3> if the indication is from MCG RLC and CA duplication is configured and activated for MCG, and for the corresponding logical channelallowedServingCellsonly includes SCell(s):

[0391] 4> initiate the failure information procedure as specified in 5.7.5 to report RLC failure.

[0392] 3> else:

[0393] 4> consider radio link failure to be detected for the MCG, i.e. MCG RLF;

[0394] 4> discard any segments of segmented RRC messages stored;

[0395] 4> if AS security has not been activated:

[0396] 5> perform the actions upon going to RRC_IDLE as specified in 5.3.11, with release cause 'other';-

[0397] 4> else if AS security has been activated but SRB2 and at least one DRB or multicast MRB or, for IAB and NCR, SRB2, have not been setup:

[0398] 5> store the radio link failure information in theVarRLF-Report;

[0399] 5> perform the actions upon going to RRC_IDLE, with release cause 'RRC connection failure';

[0400] 4> else:

[0401] 5> store the radio link failure information in theVarRLF-Report;

[0402] 5> if MP is configured:

[0403] 6> if T316 is configured, and MP indirect path transmission is not suspended; and

[0404] 6> if neither MP indirect path change nor MP indirect path addition is ongoing:

[0405] 7> initiate the MCG failure information procedure to report MCG radio link failure.

[0406] 6> else:

[0407] 7> initiate the connection re-establishment procedure.

[0408] 5> else:

[0409] 6> if the UE supports RLF-Report for fast MCG recovery procedure and if T316 is configured:

[0410] 7> if the SCG is deactivated at the moment of detecting RLF in the MCG:

[0411] 8> set the mcgRecoveryFailureCause in the VarRLF-Report toscg-Deactivated;

[0412] 7> else if SCG transmission is suspended at the moment of detecting RLF in the MCG:

[0413] 8> set thepSCellIdin theVarRLF-Reportto the global cell identity of the PSCell, if available, otherwise to the physical cell identity and carrier frequency of the PSCell;

[0414] 8> set thescg-FailureCausevalue in theVarRLF-Report;

[0415] 8> set theelapsedTimeSCG-Failurein theVarRLF-Reportto the time elapsed between SCG failure and the MCG failure;

[0416] 6> if T316 is configured; and

[0417] 6> if SCG transmission is not suspended; and

[0418] 6> if the SCG is not deactivated; and

[0419] 6> if neither PSCell change nor PSCell addition is ongoing (i.e. timer T304 for the NR PSCell is not running in case of NR-DC or timer T307 of the E-UTRA PSCell is not running:

[0420] 7> initiate the MCG failure information procedure to report MCG radio link failure.

[0421] 6> else:

[0422] 7> initiate the connection re-establishment procedure.

[0423] The UE shall:

[0424] 1> upon T310 expiry in PSCell; or

[0425] 1> upon T312 expiry in PSCell; or

[0426] 1> upon random access problem indication from SCG MAC; or

[0427] 1> upon indication from SCG RLC that the maximum number of retransmissions has been reached; or

[0428] 1> if connected as an IAB-node, upon BH RLF indication received on BAP entity from the SCG; or

[0429] 1> upon consistent uplink LBT failure indication from SCG MAC:

[0430] 2> if the indication is from SCG RLC and CA duplication is configured and activated for SCG, and for the corresponding logical channelallowedServingCellsonly includes SCell(s):

[0431] 3> initiate the failure information procedure to report RLC failure.

[0432] 2> else:

[0433] 3> consider radio link failure to be detected for the SCG, i.e. SCG RLF;

[0434] 3> if the SCG is deactivated:

[0435] 4> stop radio link monitoring on the SCG;

[0436] 4> indicate to lower layers to stop beam failure detection on the PSCell;

[0437] 3> if MCG transmission is not suspended:

[0438] 4> initiate the SCG failure information procedure to report SCG radio link failure.

[0439] 3> else:

[0440] 4> if the UE is in NR-DC:

[0441] 5> if the UE supports RLF-Report for fast MCG recovery procedure and if the UE detected SCG failure while the timer T316 was running:

[0442] 6> set thepSCellIdin theVarRLF-Reportto the global cell identity of the PSCell, if available, otherwise to the physical cell identity and carrier frequency of the PSCell;

[0443] 6> set thescg-FailureCausein theVarRLF-Reportvalue;

[0444] 6> set theelapsedTimeSCG-Failurein theVarRLF-Reportto the time elapsed between MCG failure and the SCG failure;

[0445] 6> includescg-FailedAfterMCG;

[0446] 5> initiate the connection re-establishment procedure;

[0447] 4> else (the UE is in (NG)EN-DC):

[0448] 5> initiate the connection re-establishment procedure;

[0449] RLFcause determination

[0450] The UE shall set therlf-Causein theVarRLF-Reportas follows:

[0451] 1> if the UE declares radio link failure due to T310 expiry:

[0452] 2> set therlf-Causeast310-Expiry;

[0453] 1> else if the UE declares radio link failure due to the random access problem indication from MCG MAC:

[0454] 2> if the random access procedure was initiated for beam failure recovery:

[0455] 3> set therlf-CauseasbeamFailureRecoveryFailure;

[0456] 2> else:

[0457] 3> set therlf-CauseasrandomAccessProblem;

[0458] 1> else if the UE declares radio link failure due to the reaching of maximum number of retransmissions from the MCG RLC:

[0459] 2> set therlf-Causeasrlc-MaxNumRetx;

[0460] 1> else if the UE declares radio link failure due to consistent uplink LBT failures:

[0461] 2> set therlf-CauseaslbtFailure;

[0462] 1> else if the IAB-MT declares radio link failure due to the reception of a BH RLF indication on BAP entity:

[0463] 2> set therlf-Causeasbh-rlfRecoveryFailure.

[0464] 1> else if the UE declares radio link failure due to T312 expiry:

[0465] RLF report content determination

[0466] The UE shall determine the content in theVarRLF-Reportas follows:

[0467] 1> clear the information included inVarRLF-Report, if any;

[0468] 1> if the UE is not in SNPN access mode, set theplmn-IdentityListto include the list of EPLMNs stored by the UE (i.e. including the RPLMN);

[0469] 1> else if the UE is in SNPN access mode, set thesnpn-IdentityListto include the list of equivalent SNPNs stored by the UE (i.e., including the registered SNPN identity);

[0470] 1> set themeasResultLastServCellto include the cell level RSRP, RSRQ and the available SINR, of the source PCell (in case HO failure) or PCell (in case RLF) based on the available SSB and CSI-RS measurements collected up to the moment the UE detected failure;

[0471] 1> ifmeasRSSI-ReportConfigis configured for themeasObjectindicated as theservingCellMOof the source PCell (in case HO failure) or PCell (in case of RLF), set themeasResultLastServCellRSSIto the linear average of the available RSSI sample value(s) provided by lower layers for the frequency of the source PCell (in case HO failure) or PCell (in case of RLF) up to the moment the UE detected the failure;

[0472] 1> if the SS / PBCH block-based measurement quantities are available:

[0473] 2> set thersIndexResultsinmeasResultLastServCellto include all the available measurement quantities of the source PCell (in case HO failure) or PCell (in case RLF), ordered such that the highest SS / PBCH block RSRP is listed first if SS / PBCH block RSRP measurement results are available, otherwise the highest SS / PBCH block RSRQ is listed first if SS / PBCH block RSRQ measurement results are available, otherwise the highest SS / PBCH block SINR is listed first, based on the available SS / PBCH block based measurements collected up to the moment the UE detected failure;

[0474] 1> if the CSI-RS based measurement quantities are available:

[0475] 2> set thersIndexResultsinmeasResultLastServCellto include all the available measurement quantities of the source PCell (in case HO failure) or PCell (in case RLF), ordered such that the highest CSI-RS RSRP is listed first if CSI-RS RSRP measurement results are available, otherwise the highest CSI-RS RSRQ is listed first if CSI-RS RSRQ measurement results are available, otherwise the highest CSI-RS SINR is listed first, based on the available CSI-RS based measurements collected up to the moment the UE detected failure;

[0476] 1> for each of the configuredmeasObjectNRin which measurements are available:

[0477] 2> if the SS / PBCH block-based measurement quantities are available:

[0478] 3> set themeasResultListNRinmeasResultNeighCellsto include all the available measurement quantities of the best measured cells, other than the source PCell (in case HO failure) or PCell (in case RLF), ordered such that the cell with highest SS / PBCH block RSRP is listed first if SS / PBCH block RSRP measurement results are available, otherwise the cell with highest SS / PBCH block RSRQ is listed first if SS / PBCH block RSRQ measurement results are available, otherwise the cell with highest SS / PBCH block SINR is listed first, based on the available SS / PBCH block based measurements collected up to the moment the UE detected failure;

[0479] 4> for each neighbour cell included, include the optional fields that are available;

[0480] - For the neighboring cells included inmeasResultListNRinmeasResultNeighCellsordered based on the SS / PBCH block measurement quantities, UE also includes the CSI-RS based measurement quantities, if available.

[0481] 2> if the CSI-RS based measurement quantities are available:

[0482] 3> set themeasResultListNRinmeasResultNeighCellsto include all the available measurement quantities of the best measured cells, other than the source PCell (in case HO failure) or PCell (in case RLF), ordered such that the cell with highest CSI-RS RSRP is listed first if CSI-RS RSRP measurement results are available, otherwise the cell with highest CSI-RS RSRQ is listed first if CSI-RS RSRQ measurement results are available, otherwise the cell with highest CSI-RS SINR is listed first, based on the available CSI-RS based measurements collected up to the moment the UE detected radio link failure;

[0483] 4> for each neighbour cell included, include the optional fields that are available;

[0484] - For ordering the neighboring cells based on the CSI-RS measurement quantities, UE includes measurements only for the cells not yet included inmeasResultListNRinmeasResultNeighCellsto avoid overriding SS / PBCH block-based ordered measurements.

[0485] 2> for each neighbour cell, if any, included inmeasResultListNRinmeasResultNeighCells:

[0486] 3> if the UE supports RLF-Report for conditional handover and if the neighbour cell is one of the candidate cells for which thereconfigurationWithSyncis included in themasterCellGroupin the MCGVarConditionalReconfigat the moment of the detected failure:

[0487] 4> setchoConfiginMeasResult2NRto the execution condition for eachmeasIdwithincondTriggerConfigassociated to the neighbour cell within the MCGVarConditionalReconfig;

[0488] 4> if the first entry ofchoConfigcorresponds to a fulfilled execution condition at the moment of handover failure, or radio link failure; or

[0489] 4> if the second entry ofchoConfig, if available, corresponds to a fulfilled execution condition at the moment of handover failure, or radio link failure:

[0490] 5> setfirstTriggeredEventto the execution conditioncondFirstEventcorresponding to the first entry ofchoConfigor to the execution conditioncondSecondEventcorresponding to the second entry ofchoConfig, whichever execution condition was fulfilled first in time;

[0491] 5> settimeBetweenEventsto the elapsed time between the point in time of fulfilling the condition inchoConfigthat was fulfilled first in time, and the point in time of fulfilling the condition inchoConfigthat was fulfilled second in time, if both the first execution condition corresponding to the first entry and the second execution condition corresponding to the second entry in thechoConfigwere fulfilled;

[0492] 1> for each of the configuredmeasObjectNRassociated with neighboring cellsif the associatedreportConfigNRincludesmeasRSSI-ReportConfig:

[0493] 2> set themeasResultNeighFreqRSSIin themeasResultNeighFreqListRSSIto the linear average of the available RSSI sample value(s) provided by lower layers for the frequencies other than the frequency of the source PCell (in case HO failure) or of the PCell (in case RLF), up to the moment the UE detected failure;

[0494] 1> for each of the configured EUTRA frequencies in which measurements are available;

[0495] 2> set themeasResultListEUTRAinmeasResultNeighCellsto include the best measured cells ordered such that the cell with highest RSRP is listed first if RSRP measurement results are available, otherwise the cell with highest RSRQ is listed first, and based on measurements collected up to the moment the UE detected failure;

[0496] 3> for each neighbour cell included, include the optional fields that are available;

[0497] - The measured quantities are filtered by the L3 filter as configured in the mobility measurement configuration. The measurements are based on the time domain measurement resource restriction, if configured. Exclude-listed cells are not required to be reported.

[0498] 1> set thec-RNTIto the C-RNTI used in the source PCell (in case HO failure) or PCell (in case RLF);

[0499] 1> if the failure is detected due to reconfiguration with sync failure, set the fields inVarRLF-reportas follows:

[0500] 2> set theconnectionFailureTypetohof;

[0501] 2> if the UE supports RLF-Report for DAPS handover and if any DAPS bearer was configured while T304 was running:

[0502] 3> setlastHO-Typetodaps;

[0503] 3> if radio link failure was detected in the source PCell:

[0504] 4> settimeConnSourceDAPS-Failureto the time between the initiation of the DAPS handover execution and the radio link failure detected in the source PCell while T304 was running;

[0505] 4> set therlf-Causeto the trigger for detecting the source radio link failure;

[0506] 2> if the UE supports RLF-Report for conditional handover and if configuration of the conditional handover is available in the MCGVarConditionalReconfigat the moment of the handover failure:

[0507] 3> if the UE executed a conditional handover toward target PCell according to thecondRRCReconfigof the target PCell:

[0508] 4> settimeSinceCHO-Reconfigto the time elapsed between the execution of the lastRRCReconfigurationmessage includingreconfigurationWithSyncfor the target PCell of the failed conditional handover, and the reception in the source PCell of the lastconditionalReconfigurationincluding thecondRRCReconfigof the target PCell of the failed conditional handover;

[0509] 3> else:

[0510] 4> settimeSinceCHO-Reconfigto the time elapsed between the execution of the lastRRCReconfigurationmessage includingreconfigurationWithSyncfor the target PCell of the failed handover, and the reception in the source PCell of the lastconditionalReconfigurationincluding thecondRRCReconfig;

[0511] 3> setchoCandidateCellListto include the global cell identity, if available, and otherwise to the physical cell identity and carrier frequency of each of the candidate target cells for conditional handover included incondRRCReconfigwithin the MCGVarConditionalReconfigat the time of the failed handover, excluding the candidate target cells included inmeasResultNeighCells;

[0512] 2> if the UE supports RLF-Report for conditional handover and if the last executedRRCReconfigurationmessage includingreconfigurationWithSyncwas concerning a conditional handover:

[0513] 3> setlastHO-Typetocho;

[0514] 2> set thenrFailedPCellIdinfailedPCellIdto the global cell identity and tracking area code, if available, and otherwise to the physical cell identity and carrier frequency of the target PCell of the failed handover;

[0515] 2> includenrPreviousCellinpreviousPCellIdand set it to the global cell identity and tracking area code of the PCell where the lastRRCReconfigurationmessage includingreconfigurationWithSyncwas received;

[0516] 2> set thetimeConnFailureto the elapsed time since the execution of the lastRRCReconfigurationmessage including thereconfigurationWithSync;

[0517] 1> else if the failure is detected due to Mobility from NR failure, set the fields inVarRLF-reportas follows:

[0518] 2> set theconnectionFailureTypetohof;

[0519] 2> if lastMobilityFromNRCommandconcerned a failed inter-RAT handover from NR to E-UTRA and if the UE supports Radio Link Failure Report for Inter-RAT MRO EUTRA (NR to EUTRA):

[0520] 3> set theeutraFailedPCellIdinfailedPCellIdto the global cell identity and tracking area code, if available, and otherwise to the physical cell identity and carrier frequency of the target PCell of the failed handover;

[0521] 2> includenrPreviousCellinpreviousPCellIdand set it to the global cell identity and tracking area code of the PCell where the lastMobilityFromNRCommandmessage was received;

[0522] 2> set thetimeConnFailureto the elapsed time since the initialization of the handover associated to the lastMobilityFromNRCommandmessage;

[0523] 2> if the UE supports RLF report for inter-system handover for voice fallback and ifvoiceFallbackIndicationis included in the lastMobilityFromNRCommand:

[0524] 3> include the voiceFallbackHO;

[0525] 1> else if the failure is detected due to radio link failure, set the fields inVarRLF-reportas follows:

[0526] 2> set theconnectionFailureTypetorlf;

[0527] 2> set therlf-Causeto the trigger for detecting radio link failure;

[0528] 2> set thenrFailedPCellIdinfailedPCellIdto the global cell identity and the tracking area code, if available, and otherwise to the physical cell identity and carrier frequency of the PCell where radio link failure is detected;

[0529] 2> if anRRCReconfigurationmessage including thereconfigurationWithSyncwas received before the connection failure:

[0530] 3> if the last successfully executedRRCReconfigurationmessage including thereconfigurationWithSyncconcerned an intra NR handover and it was received while connected to the previous PCell to which the UE was connected before connecting to the PCell where radio link failure is detected; and

[0531] 3> if T316 was not running before entering the PCell in which the radio link failure was detected; and

[0532] 3> if T311 was not running before entering the PCell in which the radio link failure was detected:

[0533] 4> include thenrPreviousCellinpreviousPCellIdand set it to the global cell identity and the tracking area code of the PCell where the last executedRRCReconfigurationmessage includingreconfigurationWithSyncwas received;

[0534] 4> if the last executedRRCReconfigurationmessage includingreconfigurationWithSyncwas concerning a DAPS handover:

[0535] 5> setlastHO-Typetodaps;

[0536] 4> else if the last executedRRCReconfigurationmessage includingreconfigurationWithSyncwas concerning a conditional handover:

[0537] 5> setlastHO-Typetocho;

[0538] 4> set thetimeConnFailureto the elapsed time since the execution of the lastRRCReconfigurationmessage including thereconfigurationWithSync;

[0539] 3> else if the lastRRCReconfigurationmessage including thereconfigurationWithSyncconcerned a handover to NR from E-UTRA and if the UE supports Radio Link Failure Report for Inter-RAT MRO EUTRA:

[0540] 4> include theeutraPreviousCellinpreviousPCellIdand set it to the global cell identity and the tracking area code of the E-UTRA PCell where the lastRRCReconfigurationmessage includingreconfigurationWithSyncwas received embedded in E-UTRA RRC messageMobilityFromEUTRACommandmessage;

[0541] 4> set thetimeConnFailureto the elapsed time since reception of the lastRRCReconfigurationmessage including thereconfigurationWithSyncembedded in E-UTRA RRC messageMobilityFromEUTRACommandmessage;

[0542] 2> if configuration of the conditional handover is available in the MCGVarConditionalReconfigat the moment of declaring the radio link failure:

[0543] 3> settimeSinceCHO-Reconfigto the time elapsed between the detection of the radio link failure, and the reception, in the source PCell, of the lastconditionalReconfigurationincluding thecondRRCReconfigmessage;

[0544] 3> setchoCandidateCellListto include the global cell identity if available, and otherwise to the physical cell identity and carrier frequency of each of all the candidate target cells for conditional handover included incondRRCReconfigwithin the MCGVarConditionalReconfigat the time of radio link failure, excluding the candidate target cells included inmeasResultNeighCells;

[0545] 1> ifconnectionFailureTypeisrlfand therlf-Causeis set torandomAccessProblemorbeamFailureRecoveryFailure; or

[0546] 1> ifconnectionFailureTypeisrlfand therlf-Causeis set tolbtFailureand the radio link failure is detected during the random access procedure; or

[0547] 1> ifconnectionFailureTypeishofand if the failed handover is an intra-RAT handover:

[0548] 2> set thera-InformationCommonto include the random-access related information;

[0549] 1> ifconnectionFailureTypeisrlfand therlf-Causeis set tolbtFailure, and the radio link failure is not detected during the random access procedure:

[0550] 2> set thelocationAndBandwidthandsubcarrierSpacinginbwp-Infoassociated to the UL BWP in which the consistent uplink LBT failure was detected;

[0551] 1> if therlf-Causeis set tot310-Expiryort312-Expiry:

[0552] 2> set thessbRLMConfigBitmapand / orcsi-rsRLMConfigBitmapinmeasResultLastServCellto include the radio link monitoring configuration of the last serving cell, if available;

[0553] 1> if available, set thelocationInfo.

[0554] The UE may discard the radio link failure information or handover failure information, for example, release the UE variableVarRLF-Report, 48 hours after the radio link failure / handover failure is detected.

[0555] - In this clause, the term 'handover failure' has been used to refer to 'reconfiguration with sync failure'.

[0556] Hereinafter, technical features related to SON / MDT access type logging are described.

[0557] RLF report for LTM

[0558] The existingtimeConnFailureIE is used to indicate the time elapse since the last HO execution until connection failure, for example, since the last execution of the last RRC reconfiguration message including thereconfigurationWithSync.This time information is used for the network to determine the failure type, e.g., too late, too early and wrong cell. In our understanding, only the field description associated to the IE needs to be updated accordingly as below. Otherwise, no specification impact is foreseen.

[0559] timeConnFailure

[0560] This field is used to indicate the time elapsed since the last HO execution or the cell switch execution until connection failure. Actual value = field value * 100ms. The maximum value 1023 means 102.3s or longer.

[0561] ThereconnectCellIdindicates a cell in which UE comes to connected after failing to perform the reestablishment including the possible LTM recovery and normal RRC re-establishment. The field description and the procedural text applies to LTM scenario. No enhancement forreconnectCellIdis foreseen for LTM.

[0562] Proposal 1: only the field description associated to thetimeConnFailureIE needs to be updated accordingly. Otherwise, no specification impact fortimeConnFailureandreconnectCellIdis foreseen.

[0563] ThechoCellIdindicates the CHO candidate cell which the UE selects for CHO based recovery instead of RRC Reestablishment after the connection failure. Similar to the CHO recovery, the UE may perform LTM recovery instead of re-establishment procedure, for example, if the UE configured with LTM configurations for some candidate cells, selects a candidate cell to execute the HO using the LTM candidate cell configuration. Therefore, a new field in RLF report is needed to indicate the LTM recovery cell.

[0564] Proposal 2: introduce a new field in RLF report to indicate the LTM recovery cell.

[0565] When the HOF / RLF occurs in the target cell, the specific access type should be available to the gNB, for example, whether it is RA-based or RA-less cell switch.

[0566] Proposal 3: RAN2 include the specific access type in the RLF report, for example, whether it is RA-based or RA-less cell switch.

[0567] Meanwhile, in R19 SON / MDT, for MOB MRO, RAN2 made the following agreement but has not yet finalized more specific details: RAN2 include the specific access type in the RLF report, for example, whether it is RA-based or RA-less cell switch. FFS details, for example, if explicit or implicitly signalled.

[0568] We think that the RLF report should explicitly include the access type information for the attempted LTM cell switch. This is because, based on implicit access information, the network will not be able to accurately determine which access type the UE used for the entire LTM cell switch attempt in some cases.

[0569] A typical example is when the UE attempts a RACH-less LTM cell switch based on a dynamic grant (for example, DG-based RACH-less LTM). In this case, the UE receives a RACH-less LTM CSC (cell switch command) from the source cell and monitors the PDCCH in the target cell for the UL grant. However, for certain reasons from the network side, the target cell may command the UE to use RACH for LTM. Then, if RLF is detected in this case, the UE may include both RACH-less and RACH information as the access information. Without explicit access type information, the network cannot determine which access type the UE attempted until RLF unless the network receives this information explicitly.

[0570] By above reason, we think the implicit access type information will leave a fundamental lack of trust in the access type information reported by the UE seems not be enough. Thus, we think that the UE should log explicit access type information to provide clear information preventing any potential confusion from the network side.

[0571] In addition to introduce the explicit access type information, in the above example of DG-based RACH-less LTM, we confirmed that the UE may face a situation where RACH-less LTM CSC is commanded but RACH-based LTM should be performed. We think RAN2 need to consider more about this case where the UE actually tried different access type from the access type commanded by the network in LTM CSC.

[0572] In the above example, it is unclear whether the UE should log the RACH actually performed as the access type instead of the RACH-less commanded by the network. If the UE logs the access type as RACH, the network may not know that the LTM CSC has been indicated to RACH-less, the network may misunderstand that the cause of HOF / RLF is due to improper early synchronization before LTM. Otherwise, if the UE logs the access type as RACH-less, the network doesn't know that the UE had actually tried RACH based LTM until HOF occurs and the network may misunderstand that the UE failed RACH-less procedure during LTM.

[0573] Therefore, studies for logging command type for LTM are required.

[0574] Hereinafter, a method for logging command type for LTM, according to some embodiments of the present disclosure, will be described with reference to the following drawings.

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

[0576] FIG. 14 shows an example of a method for logging command type for LTM, according to some embodiments of the present disclosure.

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

[0578] In step S1401, the wireless device may receive, from a network, a mobility configuration.

[0579] For example, the network previously prepared and provided one or more mobility configurationto the wireless device before performing the mobility (for example, via RRC dedicated singaling). In each mobility configuration, cell configuration and related access information to be applied when performing the mobility. Once the network decides to command the mobility to the wireless device from a source cell to the candidate cell, the network may send a mobility command to the wireless device with indication which candidate configuration should be used.

[0580] For example, the network may provide one or more execution conditions corresponding to the one or more mobility configuration to trigger the mobility when providing candidate configuration to the wireless device. If one of the execution conditions are met, the wireless device may perform the mobility to the candidate cell without reception of the mobility command from the network.

[0581] In step S1402, the wireless device may trigger a mobility to a candidate cell based on a cell switch command or a conditional mobility configuration.

[0582] For example, the mobility to the candidate cell may be a lower layer triggered mobility to the candidate cell.

[0583] In step S1403, the wireless device may access the candidate cell.

[0584] For example, the wireless device may receive, from a serving cell, the cell switch command. The cell switch command may include an indication for a mobility without a random access procedure. The wireless device may monitor a physical downlink control channel (PDCCH) of the candidate cell based on a configured grant and / or a dynamic grant. The wireless device may receive, from the candidate cell, a command to use a random access procedure for the mobility to the candidate cell. The wireless device may perform the random access procedure for the mobility to the candidate cell, even though the cell switch command received from the serving cell includes an indication for a mobility without a random access procedure.

[0585] For example, the wireless device may receive, from a serving cell, the cell switch command. The the cell switch command may include an indication for a mobility with a random access procedure. The wireless device may determine that the wireless device has information for a valid timing advance (TA) for the mobility to the candidate cell. The wireless device may access the candidate cell without a random access procedure based on the information for the valid TA, even though the cell switch command received from the serving cell includes an indication for a mobility with a random access procedure.

[0586] For example, the mobility to the candidate cell without a random access procedure may be triggered based on that (i) at least one execution condition included in the conditional mobility configuration is met and (ii) a dynamic grant or a configured grant for the candidate cell included in the conditional mobility configuration is valid.

[0587] In step S1404, the wireless device may log first information and second information.

[0588] For example, the first information may include information informing whether a random access procedure is used for accessing the candidate cell or not. For example, the second information may include information informing whether the triggered mobility is either a mobility with a random access procedure or a mobility without a random access procedure.

[0589] For example, the first information may inform that a random access procedure is used for accessing the candidate cell, and the second information may inform that the triggered mobility is a mobility without a random access procedure.

[0590] For example, the first information may inform that a random access procedure is not used for accessing the candidate cell, and the second information inform that the triggered mobility is a mobility with a random access procedure.

[0591] For example, the logging the first information and the second information may be performed based on detecting a radio link failure for the candidate cell or a mobility failure to the candidate cell.

[0592] For example, the wireless device may transmit, to the network, a reporting message including the first information and the second information, based on receiving a request from the network.

[0593] For example, the reporting message may include the logged information. The logged information may include at least one following information.

[0594] - Target cell information: target cell identity, global cell identity, or conditional reconfiguration identity can be included for the target cell information, and / or

[0595] - Mobility purpose: The UE may indicate which mobility type such as CHO, LTM, CPA, CPC, etc. is initiated for the target cell. The UE may also log a mobility type for the current mobility whether the mobility is failure recovery or not, and / or

[0596] - Mobility result: The UE may log the result of the mobility trial whether the mobility trial was successful or failed. The mobility trial may include the case of the failure recovery, and / or

[0597] - Failure cause: In case of the failure, the UE may include the failure cause of the mobility trial. The failure cause can be a security mismatch between the network and the UE, no available security key, mobility validity timer expiry or random access failure, or rach skip failure, and so on, and / or

[0598] - Source cell signal quality: Information about the Layer 1 and / or Layer 3 measurement results of the source cell, and / or

[0599] - Target cell signal quality: Information about the Layer 1 and / or Layer 3 measurement results of the target cell, and / or

[0600] - Candidate cell signal quality: Information about the Layer 1 and / or Layer 3 measurement results of the other candidate cells, and / or

[0601] - Other neighbour cell measurement resuts: Information about measurement results of the other neighbour cells, and / or

[0602] - Access type information: 'RACH' or 'RACH-less' information that the UE has actually used to perform a mobility, and / or

[0603] - Another Access type information: 'RACH' or 'RACH-less' information that the network has commanded to the UE via the mobility command. The UE may log this another access type information only when the access type information is different from the indicated access type in the mobility command, and / or

[0604] - Elapsed T304 timer when performing RACH: Information about elapsed time of handover validity timer when target cell provides an PDCCH order to swith the access type (for example, from 'RACH-less' to 'RACH') during mobility. Or the UE may log a percentage value of the elapsed time / the rest time out of the total T304 time period.

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

[0606] Hereinafter, technical features related to command type logging for LTM are described.

[0607] According to implementations of the present disclosure, when logging a mobility trial towards a target cell, the UE determines whether to log not only an access type information which has actually used to perform a mobility but also another access type information which has commanded in the mobility command by the network. After logging with other mobility information, the UE reports the logging information when the network requests.

[0608] For the mobility, the network previously prepared and provided one or more candidate configuration to the UE before performing the mobility (e.g. via RRC dedicated signaling). In each candidate configuration, cell configuration and related access information to be applied when performing the mobility. Once the network decides to command the mobility to the UE from a source cell to the target cell, the network may send a mobility command to the UE with indication which candidate configuration should be used. Otherwise, the network may provide one or more execution conditions corresponding to the one or more candidate configuration to trigger the mobility when providing candidate configuration to the UE. If one of the execution conditions are met, the UE may perform the mobility to the target cell without reception of the mobility command from the network.

[0609] The access type information can be either 'RACH' or 'RACH-less'. If the access type information indicates 'RACH', 'RACH' means that the UE has / had tried to perform the mobility towards the target cell based on random access procedure. For the random access procedure, the UE performs the random access on the target cell based on the access information in the corresponding candidate configuration. If the access type information indicates 'RACH-less', 'RACH-less' means that the UE has / had tried to perform the mobility towards the target cell without the random access procedure. For the mobility without the random access procedure, the UE accesses the target cell using either a configured grant or a dynamic grant. The configured grant is provided in the candidate configuration for the mobility, and the UE selects the configured grant occasion associated with a beam indicated in the mobility command (e.g. LTM cell switch command). Upon initiation of the mobility to the target cell, the UE starts to monitor PDCCH on the target cell for dynamic scheduling.

[0610] For logging the mobility trial towards a target cell, the UE starts to log the access type information and the other mobility information related to the mobility when radio link failure is detected or handover failure is declared. The UE may start to log the access type information and the other mobility information related to the mobility when a sub-optimal successful handover is detected (for example, at least one of logging conditions for SHR, SuccessHO-Report, is met).

[0611] For the case of the radio link failure or the handover failure, the UE may log the other mobility information and the access type information in RLF-report. For the case of the sub-optimal successful handover, the UE may log the other mobility information and the access type information in SHR.

[0612] For the logging conditions to detect the sub-optimal successful handover, the UE may determine whether the mobility is the sub-optimal successful handover based on validity timer threshold (e.g.thresholdPercentageT304orthresholdPercentageT304-SCG) or based on a new logging condition that the access type information which has actually used to perform the mobility is different from the another access type which has commanded in the mobility command by the network.

[0613] For logging the mobility information, the UE may log the below information:

[0614] - Target cell information: target cell identity, global cell identity, or conditional reconfiguration identity can be included for the target cell information, AND / OR

[0615] - Mobility purpose: The UE may indicate which mobility type such as CHO, LTM, CPA, CPC, etc. is initiated for the target cell. The UE may also log a mobility type for the current mobility whether the mobility is failure recovery or not, AND / OR

[0616] - Mobility result: The UE may log the result of the mobility trial whether the mobility trial was successful or failed. The mobility trial may include the case of the failure recovery, AND / OR

[0617] - Failure cause: In case of the failure, the UE may include the failure cause of the mobility trial. The failure cause can be a security mismatch between the network and the UE, no available security key, mobility validity timer expiry or random access failure, or rach skip failure, and so on, AND / OR

[0618] - Source cell signal quality: Information about the Layer 1 and / or Layer 3 measurement results of the source cell, AND / OR

[0619] - Target cell signal quality: Information about the Layer 1 and / or Layer 3 measurement results of the target cell, AND / OR

[0620] - Candidate cell signal quality: Information about the Layer 1 and / or Layer 3 measurement results of the other candidate cells, AND / OR

[0621] - Other neighbour cell measurement results: Information about measurement results of the other neighbour cells, AND / OR

[0622] - Access type information: 'RACH' or 'RACH-less' information that the UE has actually used to perform a mobility, AND / OR

[0623] - Another Access type information: 'RACH' or 'RACH-less' information that the network has commanded to the UE via the mobility command. The UE may log this another access type information only when the access type information is different from the indicated access type in the mobility command.

[0624] - Elapsed T304 timer when performing RACH: Information about elapsed time of handover validity timer when target cell provides an PDCCH order to switch the access type (e.g. from 'RACH-less' to 'RACH') during mobility. Or the UE may log a percentage value of the elapsed time / the rest time out of the total T304 time period.

[0625] Each time the UE (re-)establishes or resumes an RRC connection, the UE checks if at least one available logged information to be reported to the network. If available, during the (re)establishment or resumption of the RRC connection, the UE notifies the network of an availability of the logging or reports the logging results. If the UE is (re)establishing the RRC connection, the UE first informs the network of the availability via RRC signaling. If the UE is resuming the suspended RRC connection, the UE can directly report the logging results to the network via RRC signaling.

[0626] The UE can also report this logging information to the network while maintaining the RRC connection. In this case, the UE can notify the network of the availability or directly report the logging results in the RRC message sent as a response to a received RRC message from the network.

[0627] FIG. 15 shows an example of a method for logging command type for LTM.

[0628] In particular, FIG. 15 shows an example of a method performed by a user equipment (UE) in a wireless communication system.

[0629] In step S1501, upon detection of radio link failure or mobility failure, the UE may log not only access type information but also commanded access type of a mobility command.

[0630] For example, the mobility command may indicate that the UE performs a mobility based on the commanded access type.

[0631] For example, the access type may be one of information between RACH and RACH-less and it may be different information from the commanded access type.

[0632] In step S1502, the UE may report the logging information when the network request.

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

[0634] Hereinafter, an apparatus for logging command type for LTM, 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.

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

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

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

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

[0639] The operations comprise: receiving, from a network, a mobility configuration; triggering a mobility to a candidate cell based on a cell switch command or a conditional mobility configuration; accessing the candidate cell; and logging first information and second information, wherein the first information includes information informing whether a random access procedure is used for accessing the candidate cell or not, and wherein the second information includes information informing whether the triggered mobility is either a mobility with a random access procedure or a mobility without a random access procedure.

[0640] For example, the first information informs that a random access procedure is used for accessing the candidate cell, and the second information informs that the triggered mobility is a mobility without a random access procedure.

[0641] For example, the first information informs that a random access procedure is not used for accessing the candidate cell, and the second information informs that the triggered mobility is a mobility with a random access procedure.

[0642] For example, the mobility to the candidate cell is a lower layer triggered mobility to the candidate cell.

[0643] For example, the operations further comprise: receiving, from a serving cell, the cell switch command, wherein the cell switch command includes an indication for a mobility without a random access procedure. For example, the operations further comprise: monitoring a physical downlink control channel of the candidate cell based on a configured grant and / or a dynamic grant. For example, the operations further comprise: receiving, from the candidate cell, a command to use a random access procedure for the mobility to the candidate cell.

[0644] For example, the operations further comprise: receiving, from a serving cell, the cell switch command, wherein the cell switch command includes an indication for a mobility with a random access procedure. For example, the operations further comprise: determining that the wireless device has information for a valid timing advance (TA) for the mobility to the candidate cell. For example, the operations further comprise: accessing the candidate cell without a random access procedure based on the information for the valid TA.

[0645] For example, the mobility to the candidate cell without a random access procedure is triggered based on that (i) at least one execution condition included in the conditional mobility configuration is met and (ii) a dynamic grant or a configured grant for the candidate cell included in the conditional mobility configuration is valid.

[0646] For example, the logging the first information and the second information is performed based on detecting a radio link failure for the candidate cell or a mobility failure to the candidate cell.

[0647] For example, the operations further comprise: transmitting, to the network, a reporting message including the first information and the second information, based on receiving a request from the network.

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

[0649] Hereinafter, a processor for a wireless device for logging command type for LTM, according to some embodiments of the present disclosure, will be described.

[0650] The processor may be adapted to control the wireless device to perform operations.

[0651] The operations comprise: receiving, from a network, a mobility configuration; triggering a mobility to a candidate cell based on a cell switch command or a conditional mobility configuration; accessing the candidate cell; and logging first information and second information, wherein the first information includes information informing whether a random access procedure is used for accessing the candidate cell or not, and wherein the second information includes information informing whether the triggered mobility is either a mobility with a random access procedure or a mobility without a random access procedure.

[0652] For example, the first information informs that a random access procedure is used for accessing the candidate cell, and the second information informs that the triggered mobility is a mobility without a random access procedure.

[0653] For example, the first information informs that a random access procedure is not used for accessing the candidate cell, and the second information informs that the triggered mobility is a mobility with a random access procedure.

[0654] For example, the mobility to the candidate cell is a lower layer triggered mobility to the candidate cell.

[0655] For example, the operations further comprise: receiving, from a serving cell, the cell switch command, wherein the cell switch command includes an indication for a mobility without a random access procedure. For example, the operations further comprise: monitoring a physical downlink control channel of the candidate cell based on a configured grant and / or a dynamic grant. For example, the operations further comprise: receiving, from the candidate cell, a command to use a random access procedure for the mobility to the candidate cell.

[0656] For example, the operations further comprise: receiving, from a serving cell, the cell switch command, wherein the cell switch command includes an indication for a mobility with a random access procedure. For example, the operations further comprise: determining that the wireless device has information for a valid timing advance (TA) for the mobility to the candidate cell. For example, the operations further comprise: accessing the candidate cell without a random access procedure based on the information for the valid TA.

[0657] For example, the mobility to the candidate cell without a random access procedure is triggered based on that (i) at least one execution condition included in the conditional mobility configuration is met and (ii) a dynamic grant or a configured grant for the candidate cell included in the conditional mobility configuration is valid.

[0658] For example, the logging the first information and the second information is performed based on detecting a radio link failure for the candidate cell or a mobility failure to the candidate cell.

[0659] For example, the operations further comprise: transmitting, to the network, a reporting message including the first information and the second information, based on receiving a request from the network.

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

[0661] Hereinafter, a non-transitory computer-readable medium has stored thereon a plurality of instructions for logging command type for LTM, according to some embodiments of the present disclosure, will be described.

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

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

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

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

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

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

[0668] The operations comprise: receiving, from a network, a mobility configuration; triggering a mobility to a candidate cell based on a cell switch command or a conditional mobility configuration; accessing the candidate cell; and logging first information and second information, wherein the first information includes information informing whether a random access procedure is used for accessing the candidate cell or not, and wherein the second information includes information informing whether the triggered mobility is either a mobility with a random access procedure or a mobility without a random access procedure.

[0669] For example, the first information informs that a random access procedure is used for accessing the candidate cell, and the second information informs that the triggered mobility is a mobility without a random access procedure.

[0670] For example, the first information informs that a random access procedure is not used for accessing the candidate cell, and the second information informs that the triggered mobility is a mobility with a random access procedure.

[0671] For example, the mobility to the candidate cell is a lower layer triggered mobility to the candidate cell.

[0672] For example, the operations further comprise: receiving, from a serving cell, the cell switch command, wherein the cell switch command includes an indication for a mobility without a random access procedure. For example, the operations further comprise: monitoring a physical downlink control channel of the candidate cell based on a configured grant and / or a dynamic grant. For example, the operations further comprise: receiving, from the candidate cell, a command to use a random access procedure for the mobility to the candidate cell.

[0673] For example, the operations further comprise: receiving, from a serving cell, the cell switch command, wherein the cell switch command includes an indication for a mobility with a random access procedure. For example, the operations further comprise: determining that the wireless device has information for a valid timing advance (TA) for the mobility to the candidate cell. For example, the operations further comprise: accessing the candidate cell without a random access procedure based on the information for the valid TA.

[0674] For example, the mobility to the candidate cell without a random access procedure is triggered based on that (i) at least one execution condition included in the conditional mobility configuration is met and (ii) a dynamic grant or a configured grant for the candidate cell included in the conditional mobility configuration is valid.

[0675] For example, the logging the first information and the second information is performed based on detecting a radio link failure for the candidate cell or a mobility failure to the candidate cell.

[0676] For example, the operations further comprise: transmitting, to the network, a reporting message including the first information and the second information, based on receiving a request from the network.

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

[0678] Hereinafter, a method performed by a base station (BS) for logging command type for LTM, according to some embodiments of the present disclosure, will be described.

[0679] The method comprises: transmitting, by a base station to a wireless device, a mobility configuration; wherein the wireless device triggers a mobility to a candidate cell based on a cell switch command or a conditional mobility configuration, wherein the wireless device accesses the candidate cell, wherein the wireless device logs first information and second information, wherein the first information includes information informing whether a random access procedure is used for accessing the candidate cell or not, and wherein the second information includes information informing whether the triggered mobility is either a mobility with a random access procedure or a mobility without a random access procedure; and receiving, by the base station from the wireless device, a reporting message including the first information and the second information.

[0680] Hereinafter, a base station (BS) for logging command type for LTM, according to some embodiments of the present disclosure, will be described.

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

[0682] The processor may be adapted to control the processor to perform operations. The operations comprise: transmitting, to a wireless device, a mobility configuration; wherein the wireless device triggers a mobility to a candidate cell based on a cell switch command or a conditional mobility configuration, wherein the wireless device accesses the candidate cell, wherein the wireless device logs first information and second information, wherein the first information includes information informing whether a random access procedure is used for accessing the candidate cell or not, and wherein the second information includes information informing whether the triggered mobility is either a mobility with a random access procedure or a mobility without a random access procedure; and receiving, from the wireless device, a reporting message including the first information and the second information.

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

[0684] According to some embodiments of the present disclosure, the wireless device could efficiently log the command type for LTM.

[0685] For example, according to the present disclosure, since the UE can report both the access type information which has actually tried to perform mobility and the commanded access type information which was indicated by the mobility command to provide accurate access trial logging information to the network.

[0686] For example, based on the commanded access type information, the network can know which / how access type information should be provided to UEs which are in similar mobility situation.

[0687] For example, by logging whether RACH was indicated in the mobility command and logging whether RACH was actually performed during the access procedure, UE mobility can be efficiently controlled.

[0688] According to some embodiments of the present disclosure, the wireless communication system could provide an efficient solution for logging the command type for LTM.

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

[0690] 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:receiving, by a wireless device from a network, a mobility configuration;triggering, by the wireless device, a mobility to a candidate cell based on a cell switch command or a conditional mobility configuration;accessing, by the wireless device, the candidate cell; andlogging, by the wireless device, first information and second information,wherein the first information includes information informing whether a random access procedure is used for accessing the candidate cell or not, andwherein the second information includes information informing whether the triggered mobility is either a mobility with a random access procedure or a mobility without a random access procedure.2.The method of claim 1,wherein the first information informs that a random access procedure is used for accessing the candidate cell, andwherein the second information informs that the triggered mobility is a mobility without a random access procedure.3.The method of claim 1,wherein the first information informs that a random access procedure is not used for accessing the candidate cell, andwherein the second information informs that the triggered mobility is a mobility with a random access procedure.4.The method of claim 1,wherein the mobility to the candidate cell is a lower layer triggered mobility to the candidate cell.5.The method of claim 1, wherein the method further comprising:receiving, by the wireless device from a serving cell, the cell switch command,wherein the cell switch command includes an indication for a mobility without a random access procedure.6.The method of claim 5, wherein the method further comprising:monitoring, by the wireless device, a physical downlink control channel of the candidate cell based on a configured grant and / or a dynamic grant.7.The method of claim 5, wherein the method further comprising:receiving, by the wireless device from the candidate cell, a command to use a random access procedure for the mobility to the candidate cell.8.The method of claim 1, wherein the method further comprising:receiving, by the wireless device from a serving cell, the cell switch command,wherein the cell switch command includes an indication for a mobility with a random access procedure.9.The method of claim 8, wherein the method further comprising:determining, by the wireless device, that the wireless device has information for a valid timing advance (TA) for the mobility to the candidate cell.10.The method of claim 9, wherein the method further comprising:accessing, by the wireless device, the candidate cell without a random access procedure based on the information for the valid TA.11.The method of claim 1,wherein the mobility to the candidate cell without a random access procedure is triggered based on that (i) at least one execution condition included in the conditional mobility configuration is met and (ii) a dynamic grant or a configured grant for the candidate cell included in the conditional mobility configuration is valid.12.The method of claim 1,wherein the logging the first information and the second information is performed based on detecting a radio link failure for the candidate cell or a mobility failure to the candidate cell.13.The method of claim 1, wherein the method further comprising:transmitting, by the wireless device to the network, a reporting message including the first information and the second information, based on receiving a request from the network.14.The method of claim 1,wherein the wireless device is in communication with at least one of a user equipment, a network, or an autonomous vehicle other than the wireless device.15.A wireless device, comprising:at least one transceiver;at least one processor; andat least one memory operably connectable to the at least one processor and storing instructions that, based on being executed by the at least one processor, perform operations comprising:receiving, from a network, a mobility configuration;triggering a mobility to a candidate cell based on a cell switch command or a conditional mobility configuration;accessing the candidate cell; andlogging first information and second information,wherein the first information includes information informing whether a random access procedure is used for accessing the candidate cell or not, andwherein the second information includes information informing whether the triggered mobility is either a mobility with a random access procedure or a mobility without a random access procedure.16.The wireless device of claim 15,wherein the first information informs that a random access procedure is used for accessing the candidate cell, andwherein the second information informs that the triggered mobility is a mobility without a random access procedure.17.The wireless device of claim 15,wherein the first information informs that a random access procedure is not used for accessing the candidate cell, andwherein the second information informs that the triggered mobility is a mobility with a random access procedure.18.The wireless device of claim 15,wherein the mobility to the candidate cell is a lower layer triggered mobility to the candidate cell.19.The wireless device of claim 15, wherein the operations further comprising:receiving, from a serving cell, the cell switch command,wherein the cell switch command includes an indication for a mobility without a random access procedure.20.The wireless device of claim 19, wherein the operations further comprising:monitoring a physical downlink control channel of the candidate cell based on a configured grant and / or a dynamic grant.21.The wireless device of claim 19, wherein the operations further comprising:receiving, from the candidate cell, a command to use a random access procedure for the mobility to the candidate cell.22.The wireless device of claim 15, wherein the operations further comprising:receiving, from a serving cell, the cell switch command,wherein the cell switch command includes an indication for a mobility with a random access procedure.23.The wireless device of claim 22, wherein the operations further comprising:determining that the wireless device has information for a valid timing advance (TA) for the mobility to the candidate cell.24.The wireless device of claim 23, wherein the operations further comprising:accessing the candidate cell without a random access procedure based on the information for the valid TA.25.The wireless device of claim 15,wherein the mobility to the candidate cell without a random access procedure is triggered based on that (i) at least one execution condition included in the conditional mobility configuration is met and (ii) a dynamic grant or a configured grant for the candidate cell included in the conditional mobility configuration is valid.26.The wireless device of claim 15,wherein the logging the first information and the second information is performed based on detecting a radio link failure for the candidate cell or a mobility failure to the candidate cell.27.The wireless device of claim 15, wherein the operations further comprising:transmitting, to the network, a reporting message including the first information and the second information, based on receiving a request from the network.28.The wireless device of claim 15,wherein the wireless device is in communication with at least one of a user equipment, a network, or an autonomous vehicle other than the wireless device.29.A processor for a wireless device in a wireless communication system, wherein the processor is adapted to control the wireless device to perform operations comprising:receiving, from a network, a mobility configuration;triggering a mobility to a candidate cell based on a cell switch command or a conditional mobility configuration;accessing the candidate cell; andlogging first information and second information,wherein the first information includes information informing whether a random access procedure is used for accessing the candidate cell or not, andwherein the second information includes information informing whether the triggered mobility is either a mobility with a random access procedure or a mobility without a random access procedure.30.A non-transitory computer-readable medium having stored thereon a plurality of instructions, which, when executed by a processor of a wireless device, cause the wireless device to perform operations, the operations comprising,receiving, from a network, a mobility configuration;triggering a mobility to a candidate cell based on a cell switch command or a conditional mobility configuration;accessing the candidate cell; andlogging first information and second information,wherein the first information includes information informing whether a random access procedure is used for accessing the candidate cell or not, andwherein the second information includes information informing whether the triggered mobility is either a mobility with a random access procedure or a mobility without a random access procedure.31.A method, the method comprising,transmitting, by a base station to a wireless device, a mobility configuration;wherein the wireless device triggers a mobility to a candidate cell based on a cell switch command or a conditional mobility configuration,wherein the wireless device accesses the candidate cell,wherein the wireless device logs first information and second information,wherein the first information includes information informing whether a random access procedure is used for accessing the candidate cell or not, andwherein the second information includes information informing whether the triggered mobility is either a mobility with a random access procedure or a mobility without a random access procedure; andreceiving, by the base station from the wireless device, a reporting message including the first information and the second information.32.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:transmitting, to a wireless device, a mobility configuration;wherein the wireless device triggers a mobility to a candidate cell based on a cell switch command or a conditional mobility configuration,wherein the wireless device accesses the candidate cell,wherein the wireless device logs first information and second information,wherein the first information includes information informing whether a random access procedure is used for accessing the candidate cell or not, andwherein the second information includes information informing whether the triggered mobility is either a mobility with a random access procedure or a mobility without a random access procedure; andreceiving, from the wireless device, a reporting message including the first information and the second information.

Images