Fallback configuration in RRC reconfiguration in ltm

The introduction of a fallback configuration in RRC reconfiguration for wireless networks addresses the inefficiencies in serving cell changes by enabling RACHless handovers, reducing interruption times and improving network stability during handovers.

WO2024235550A1PCT designated stage expired Publication Date: 2024-11-21NOKIA TECHNOLOGIES OY
View PDF 0 Cites 2 Cited by

Patent Information

Application Number
PCT/EP2024/060369
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2023-05-12
Filing Date
2024-04-17
Publication Date
2024-11-21

AI Technical Summary

Technical Problem

Current RRC reconfiguration methods for serving cell changes in wireless communication networks involve longer latency, larger overhead, and longer interruption times due to the need for explicit RRC signaling and RACH procedures, which are inefficient, especially during handovers.

Method used

Implementing a fallback configuration within the RRC reconfiguration for terminal devices to enable RACHless handovers by determining a fallback configuration that allows the device to switch to a suitable cell without waiting for the expiration of timing alignment timers, thereby minimizing interruption time and avoiding RACH procedure failures.

Benefits of technology

This approach reduces interruption times and minimizes RACHless handover failures by allowing the terminal device to fall back to a suitable cell upon timing alignment timer expiry, ensuring continuous connectivity and reducing the need for re-establishment procedures.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure EP2024060369_21112024_PF_FP_ABST
    Figure EP2024060369_21112024_PF_FP_ABST
Patent Text Reader

Abstract

Exemplary embodiments of the present disclosure relate to improvement of random access channel-less (RACHless) L1 / L2 triggered mobility procedure. In an aspect, a first network device determines a radio resource control (RRC) reconfiguration for one or more prepared network devices prepared by the first network device, wherein the RRC reconfiguration comprises a fallback configuration to be used by a terminal device for performing cell switch; and transmits, from first network device to a second network device, the RRC reconfiguration. By this process, the UE may connect to a suitable cell after a RACHless handover failure in LTM cell switch procedure occurs.
Need to check novelty before this filing date? Find Prior Art

Description

FALLBACK CONFIGURATION IN RRC RECONFIGURATION IN LTMFIELD

[0001] Various example embodiments relate to the field of telecommunication and in particular, to a terminal device, network devices, methods, apparatuses and a computer readable storage medium for communication.BACKGROUND

[0002] When user equipment (UE) moves from one cell to another cell, at some points a serving cell change needs to be performed. Currently, serving cell change is triggered by Layer 3 (L3) measurements (radio resource control (RRC) measurement report from UE) and is done by downlink RRC signaling, i.e., RRC reconfiguration message with Synchronization for change of primary cell (PCell) and primary secondary cell (PSCell), as well as release and add for secondary cells (SCell)s when applicable. All cases involve complete L2 (and LI) resets, leading to longer latency, larger overhead, and longer interruption time than beam switch mobility.

[0003] Therefore, in 3 GPP Release 18, a new work item on further new radio (NR) mobility enhancements, named as layer 1 (LI) / layer 2 (L2)-triggered mobility (LTM). The goal of L1 / L2 mobility enhancements is to enable a serving cell change via L1 / L2 signaling, to reduce the latency, overhead and interruption time.SUMMARY

[0004] In general, exemplary embodiments of the present disclosure provide a solution for improving random access channel-less (RACHless) LTM procedure.

[0005] In a first aspect, there is provided a first network device. The first network device may include: at least one processor and at least one memory storing instructions that, when executed by the at least one processor, cause the first network device at least to: determine a radio resource control (RRC) reconfiguration for one or more prepared network devices prepared by the first network device, wherein the RRC reconfiguration comprises a fallbackconfiguration to be used by a terminal device for performing cell switch; and transmit, to a second network device, the RRC reconfiguration.

[0006] In a second aspect, there is provided a second network device. The second network device may include: at least one processor and at least one memory storing instructions that, when executed by the at least one processor, cause the second network device at least to: receive, from a first network device, a radio resource control (RRC) reconfiguration for one or more prepared network devices, wherein the RRC reconfiguration comprises a fallback configuration to be used by a terminal device for performing cell switch; and transmit, to the terminal device, the RRC reconfiguration.

[0007] In a third aspect, there is provided a terminal device. The terminal device may include: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the terminal device at least to: receive, from a second network device, a radio resource control (RRC) reconfiguration for one or more prepared network devices prepared by a first network device, wherein the RRC reconfiguration is determined by the first network device and comprises a fallback configuration; receive, from the second network device, a cell switch command; and perform, based on the fallback configuration, a cell switch.

[0008] In a fourth aspect, there is provided a method. The method may include: determining, at a first network device, a radio resource control (RRC) reconfiguration for one or more prepared network devices prepared by the first network device, wherein the RRC reconfiguration comprises a fallback configuration to be used by a terminal device for performing cell switch; and transmitting, from first network device to a second network device, the RRC reconfiguration.

[0009] In a fifth aspect, there is provided a method. The method may include: receiving, at a second network device from a first network device, a radio resource control (RRC) reconfiguration for one or more prepared network devices, wherein the RRC reconfiguration comprises a fallback configuration to be used by a terminal device for performing cell switch; and transmitting, from the second network device to the terminal device, the RRC reconfiguration.

[0010] In a sixth aspect, there is provided a method. The method may include: receiving, at a terminal device from a second network device, a radio resource control (RRC)reconfiguration for one or more prepared network devices prepared by a first network device, wherein the RRC reconfiguration is determined by the first network device and comprises a fallback configuration; receiving, from the second network device, a cell switch command; and performing, based on the fallback configuration, a cell switch.

[0011] In a seventh aspect, there is provided an apparatus. The apparatus may include: means for determining, at a first network device, a radio resource control (RRC) reconfiguration for one or more prepared network devices prepared by the first network device, wherein the RRC reconfiguration comprises a fallback configuration to be used by a terminal device for performing cell switch; and means for transmitting, from first network device to a second network device, the RRC reconfiguration.

[0012] In an eighth aspect, there is provided an apparatus. The apparatus may include: means for receiving, at a second network device from a first network device, a radio resource control (RRC) reconfiguration for one or more prepared network devices, wherein the RRC reconfiguration comprises a fallback configuration to be used by a terminal device for performing cell switch; and means for transmitting, from the second network device to the terminal device, the RRC reconfiguration.

[0013] In a ninth aspect, there is provided an apparatus. The apparatus may include: means for receiving, at a terminal device from a second network device, a radio resource control (RRC) reconfiguration for one or more prepared network devices prepared by a first network device, wherein the RRC reconfiguration is determined by the first network device and comprises a fallback configuration; means for receiving, from the second network device, a cell switch command; and means for performing, based on the fallback configuration, a cell switch.

[0014] In a tenth aspect, there is provided a non-transitory computer readable medium including program instructions for causing an apparatus to perform at least the method according to any of fourth or sixth aspects.

[0015] In an eleventh aspect, there is provided a computer program including instructions, which, when executed by an apparatus, cause the apparatus at least to: determine a radio resource control (RRC) reconfiguration for one or more prepared network devices prepared by the first network device, wherein the RRC reconfiguration comprises a fallbackconfiguration to be used by a terminal device for performing cell switch; and transmit, to a second network device, the RRC reconfiguration.

[0016] In a twelfth aspect, there is provided a computer program including instructions, which, when executed by an apparatus, cause the apparatus at least to: receive, from a first network device, a radio resource control (RRC) reconfiguration for one or more prepared network devices, wherein the RRC reconfiguration comprises a fallback configuration to be used by a terminal device for performing cell switch; and transmit, to the terminal device, the RRC reconfiguration.

[0017] In a thirteenth aspect, there is provided a computer program including instructions, which, when executed by an apparatus, cause the apparatus at least to: receive, from a second network device, a radio resource control (RRC) reconfiguration for one or more prepared network devices prepared by a first network device, wherein the RRC reconfiguration is determined by the first network device and comprises a fallback configuration; receive, from the second network device, a cell switch command; and perform, based on the fallback configuration, a cell switch.

[0018] In a fourteenth aspect, there is provided a first network device. The first network device may include: a determining circuitry for determining, at a first network device, a radio resource control (RRC) reconfiguration for one or more prepared network devices prepared by the first network device, wherein the RRC reconfiguration comprises a fallback configuration to be used by a terminal device for performing cell switch; and a transmitting circuitry for transmitting, from first network device to a second network device, the RRC reconfiguration.

[0019] In a fifteenth aspect, there is provided a second network device. The second network device may include: a receiving circuitry for receiving, at a second network device from a first network device, a radio resource control (RRC) reconfiguration for one or more prepared network devices, wherein the RRC reconfiguration comprises a fallback configuration to be used by a terminal device for performing cell switch; and a transmitting circuitry for transmitting, from the second network device to the terminal device, the RRC reconfiguration.

[0020] In a sixteenth aspect, there is provided a terminal device. The terminal device may include: a receiving circuitry for receiving, at a terminal device from a second networkdevice, a radio resource control (RRC) reconfiguration for one or more prepared network devices prepared by a first network device, wherein the RRC reconfiguration is determined by the first network device and comprises a fallback configuration; a receiving circuitry for receiving, from the second network device, a cell switch command; and a performing circuitry for performing based on the fallback configuration, a cell switch.

[0021] It is to be understood that the summary section is not intended to identify key or essential features of embodiments of the present disclosure, nor is it intended to be used to limit the scope of the present disclosure. Other features of the present disclosure will become easily comprehensible through the following description.BRIEF DESCRIPTION OF THE DRAWINGS

[0022] Some exemplary embodiments will now be described with reference to the accompanying drawings, in which:

[0023] Fig. 1A illustrates an example mobility scenario in which a terminal device experiences;

[0024] Fig. IB illustrates a communication environment in which some embodiments of the present disclosure can be implemented;

[0025] Fig. 2 illustrates a signaling chart illustrating communication process in accordance with some embodiments of the present disclosure;

[0026] Fig. 3 illustrates an exemplary signaling chart for performing cell switch in accordance with some embodiments of the present disclosure;

[0027] Fig. 4 illustrates an exemplary signaling chart for performing cell switch in accordance with some embodiments of the present disclosure;

[0028] Fig. 5 illustrates an exemplary signaling chart for performing cell switch in accordance with some embodiments of the present disclosure;

[0029] Fig. 6 illustrates an exemplary signaling chart for performing cell switch in accordance with some embodiments of the present disclosure;

[0030] Fig. 7 illustrates a flowchart of a method implemented at a first network device in accordance with some embodiments of the present disclosure;

[0031] Fig. 8 illustrates a flowchart of a method implemented at a second network devicein accordance with some embodiments of the present disclosure;

[0032] Fig. 9 illustrates a flowchart of a method implemented at a terminal device in accordance with some embodiments of the present disclosure;

[0033] Fig. 10 illustrates a simplified block diagram of an apparatus that is suitable for implementing embodiments of the present disclosure; and

[0034] Fig. 11 illustrates a block diagram of an example computer readable medium in accordance with some embodiments of the present disclosure.

[0035] Throughout the drawings, the same or similar reference numerals represent the same or similar elements.DETAILED DESCRIPTION

[0036] Principles of the present disclosure will now be described with reference to some example embodiments. It is to be understood that these embodiments are described only for the purpose of illustration and help those skilled in the art to understand and implement the present disclosure, without suggesting any limitation as to the scope of the disclosure. The disclosure described herein can be implemented in various manners other than the ones described below.

[0037] In the following description and claims, unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skills in the art to which this disclosure belongs.

[0038] References in the present disclosure to “one embodiment,” “an embodiment,” “an example embodiment,” and the like indicate that the embodiment described may include a particular feature, structure, or characteristic, but it is not necessary that every embodiment includes the particular feature, structure, or characteristic. Moreover, such phrases are not necessarily referring to the same embodiment. Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is submitted that it is within the knowledge of one skilled in the art to affect such feature, structure, or characteristic in connection with other embodiments whether or not explicitly described.

[0039] It shall be understood that although the terms “first” and “second” etc. may be used herein to describe various elements, these elements should not be limited by these terms.These terms are only used to distinguish one element from another. For example, a first element could be termed a second element, and similarly, a second element could be termed a first element, without departing from the scope of example embodiments. As used herein, the term “and / or” includes any and all combinations of one or more of the listed terms.

[0040] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of example embodiments. As used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises”, “comprising”, “has”, “having”, “includes” and / or “including”, when used herein, specify the presence of stated features, elements, and / or components etc., but do not preclude the presence or addition of one or more other features, elements, components and / or combinations thereof. As used herein, “at least one of the following: ” and “at least one of ” and similar wording, where the list of two or more elements are joined by “and” or “or”, mean at least any one of the elements, or at least any two or more of the elements, or at least all the elements.

[0041] As used in this application, the term “circuitry” may refer to one or more or all of the following:(a) hardware-only circuit implementations (such as implementations in only analog and / or digital circuitry) and(b) combinations of hardware circuits and software, such as (as applicable):(i) a combination of analog and / or digital hardware circuit(s) with software / firmware and(ii) any portions of hardware processor(s) with software (including digital signal processor(s)), software, and memory(ies) that work together to cause an apparatus, such as a mobile phone or server, to perform various functions) and(c) hardware circuit(s) and or processor(s), such as a microprocessor(s) or a portion of a microprocessor(s), that requires software (e.g., firmware) for operation, but the software may not be present when it is not needed for operation.

[0042] This definition of circuitry applies to all uses of this term in this application, including in any claims. As a further example, as used in this application, the term circuitry also covers an implementation of merely a hardware circuit or processor (or multiple processors) or portion of a hardware circuit or processor and its (or their) accompanying software and / or firmware. The term circuitry also covers, for example and if applicable to the particular claim element, a baseband integrated circuit or processor integrated circuit for a mobile device or a similar integrated circuit in server, a cellular network device, or other computing or network device.

[0043] As used herein, the term “communication network” refers to a network following any suitable communication standards, such as Long Term Evolution (LTE), LTE-Advanced (LTE-A), Wideband Code Division Multiple Access (WCDMA), High-Speed Packet Access (HSPA), Narrow Band Internet of Things (NB-IoT) and so on. Furthermore, the communications between a terminal device and a network device in the communication network may be performed according to any suitable generation communication protocols, including, but not limited to, the first generation (1G), the second generation (2G), 2.5G, 2.75G, the third generation (3G), the fourth generation (4G), 4.5G, the future fifth generation (5G) communication protocols, and / or any other protocols either currently known or to be developed in the future. Embodiments of the present disclosure may be applied in various communication systems. Given the rapid development in communications, there will of course also be future type communication technologies and systems with which the present disclosure may be embodied. It should not be seen as limiting the scope of the present disclosure to only the aforementioned system.

[0044] As used herein, the term “network device” refers to a node in a communication network via which a terminal device accesses the network and receives services therefrom. The network device may refer to a base station (BS) or an access point (AP), for example, a node B (NodeB or NB), an evolved NodeB (eNodeB or eNB), a NR NB (also referred to as a gNB), a Remote Radio Unit (RRU), a radio header (RH), a remote radio head (RRH), a relay, a low power node such as a femto, a pico, and so forth, depending on the applied terminology and technology.

[0045] The term “terminal device” refers to any end device that may be capable of wireless communication. By way of example rather than limitation, a terminal device may also be referred to as a communication device, user equipment (UE), a Subscriber Station (SS), aPortable Subscriber Station, a Mobile Station (MS), or an Access Terminal (AT). The terminal device may include, but not limited to, a mobile phone, a cellular phone, a smart phone, voice over IP (VoIP) phones, wireless local loop phones, a tablet, a wearable terminal device, a personal digital assistant (PDA), portable computers, desktop computer, image capture terminal devices such as digital cameras, gaming terminal devices, music storage and playback appliances, vehicle-mounted wireless terminal devices, wireless endpoints, mobile stations, laptop-embedded equipment (LEE), laptop-mounted equipment (LME), USB dongles, smart devices, wireless customer-premises equipment (CPE), an Internet of Things (loT) device, a watch or other wearable, a head-mounted display (HMD), a vehicle, a drone, a medical device and applications (e.g., remote surgery), an industrial device and applications (e.g., a robot and / or other wireless devices operating in an industrial and / or an automated processing chain contexts), a consumer electronics device, a device operating on commercial and / or industrial wireless networks, and the like. In the following description, the terms “terminal device”, “communication device”, “terminal”, “user equipment” and “UE” may be used interchangeably.

[0046] As mentioned above, when the UE moves from one cell to another cell, at some points a serving cell change needs to be performed. In the legacy, the serving cell change is done by explicit RRC reconfiguration signaling to trigger the synchronization of target cell based on L3 measurements report. It leads to longer latency, larger overhead, and longer interruption time than beam level mobility. Therefore, in 3 GPP Release 18, a new work item on further NR mobility enhancements, named as LTM, was approved to enable a serving cell change via L1 / L2 signaling, in order to reduce the latency, overhead and interruption time.

[0047] In released legacy L1 / L2 Triggered Mobility (LTM) Framework, in first step, the L3 measurement report is transmitted from the UE to the gNB (for example, the CU), and then the CU determines LTM candidate preparation based on the L3 measurement report, for example, the CU prepares the target cells for LTM, and the CU also provides the LTM configuration for prepared cells. In the second step, the CU transmits a RRC reconfiguration including the LTM candidate preparation to the UE, for example, the CU configures UE with LI measurement reporting needed for LTM execution. In third step, the RRC reconfiguration complete message is transmitted to the CU. In the fourth step, the UE performs early UL / DL synchronization procedure with candidate cells to minimize theinterruption during LTM execution. This is one of the main benefits of the LTM which differs from the traditional handover procedure where the interruption time caused by synchronization with target cell during the handover is minimized with early synchronization procedure. In the fifth to sixth steps, the UE sends the LI beam measurements of the target cells to the source cell and the source DU decides on which cell the UE should handover. In the seventh step, the UE performs RACH procedure. In the current framework, it is mentioned that if a timing advance of the target cell is still valid (from the synchronization procedure of fourth step), the UE then skips the RACH procedure (at seventh step) during Handover (HO).

[0048] Therefore, in the legacy LTM framework, the UE performs early uplink (UL) / downlink (DL) synchronization procedure with candidate cells to minimize the interruption time during LTM execution. Then, the LTM execution is performed, specifically, when UE receives cell switch command from a network device, the UE will perform cell switch based on random access channel (RACH) procedure. There is mentioned in current LTM framework that if a timing advance of a target cell is still valid from the early synchronization procedure, the UE may skip the RACH procedure, and thus there is a need for further development about RACHless LTM in which the UE may skip the RACH procedure during LTM execution.

[0049] In the present disclosure, it is proposed to perform the RACHless LTM as follows. First, the UE is prepared with target DU / cells. Then, the source DU (S-DU) decides to trigger a timing advance (TA) acquisition of the prepared target DU / cell. Then, the UE sends PRACH Preamble to the target DU / cell so that the target DU / cell estimates the TA thereof. Then, the UE receives the random access response (RAR) configured by the CU including the estimated TA. Therefore, the UE will receive the estimated TA): directly from the S-DU upon S-DU receives it from CU (Option #1), or from the S-DU along with the media access control (MAC) control element (MAC CE) when the cell change or cell switch is triggered (Option #2). Then, once the cell change is triggered, the UE will access to the target cell and skip the RACH procedure if the TA of the target cell is valid.

[0050] In the above mentioned LTM procedure, when the UE acquires the TA of the target cell(s), the UE will start the timeAlignmentTimer (TAT) for that acquired TA for monitoring the validity of acquired TA. As mentioned above, the UE may acquire the TA of the target cell in one of the following way: via RAR, or via MAC CE Cell Switch Command.

[0051] In option #1, when the TA is received via RAR first, the TAT starts to run. And then, the MAC CE command is received for triggering cell change, a timer 304 (T304) starts to run, and thus the TAT starts running before the T304, i.e., TAT starts when the RAR including the estimated TA is received. In option #2, when the TA is received via MAC CE cell switch command, the T304 timer and TAT starts running simultaneously as MAC CE includes the TA which triggers the TAT to start running.

[0052] In either case, T304 and TAT timers run independently. This is because T304 is a timer that is used to detect radio link related issues during the handover procedure whereas TAT is a timer that is used to identify if the acquired TA is still valid or not. Although T304 and TAT are independent timers, in LTM cell switch procedure, those two timers coincide with each other. When the TAT timer expires before the T304 timer expires the UE cannot complete the handover anymore (since the TA of the target cell is not valid anymore). However, the UE waits until the T304 timer to expire, and only then declares failure to initiate the re-establishment. This issue is illustrated in an example mobility scenario in Fig. 1A. Assuming that there are two cells with the coverage areas shown with elliptic areas and the UE is moving from left cell coverage to right cell coverage.

[0053] As shown in Fig. 1 A, at step 0, the UE receives the MAC CE for cell change trigger. At step 1, the UE cannot access to the target cell due to bad radio link. At step 2, if the MAC CE includes the TA of the target cell (for example, when RAR is not configured), then the UE will start running the TAT when it receives the TA in that MAC CE message. It should be noted that if the UE has received the TA of that target cell before the reception of the MAC CE (for example, when the RAR is configured, the estimated TA is received via RAR), it means that the TAT has been already running for the TA of that target cell before the time of receiving the MAC CE. In either case, the UE starts running the T304 when it receives the MAC CE.

[0054] As shown in Fig. 1A, at step 3, the TAT expires which indicates that the TA is invalid. The UE continues to run the T304 timer. At steps 4 and 5, even if the link between the UE and the target cell gets better, the UE cannot perform the RACHless HO as the TA of the target cell becomes invalid. Then, the UE waits until the T304 expires and experiences interruption during the running period of T304 until T304 expires. At steps 6 and 7, the UE declares failure after expiry of the T304 and the UE initiates the reestablishment procedure to find a suitable cell for reconnecting to the network. During thistime, the UE continues to experience the interruption as the UE cannot receive any service until the re-establishment is completed at step 7.

[0055] Therefore, according to above mobility scenario, the UE waits unnecessarily for T304 expiry after TAT has already expired, and during this waiting period, the UE will not try any recovery and T304 expiry with subsequent re-establishment is inevitable.

[0056] In view of the foregoing, according to embodiment of the present disclosure, there is provided a solution for improving RACHless LTM procedure and minimizing the interruption time of the RACHless handover failure in LTM cell switch procedure. In this process, the CU determines a RRC reconfiguration for prepared cells or DUs in which a target cell is included, and the RRC reconfiguration includes fallback configuration to be used by the UE to perform cell switch when a potential RACHless handover is failed. By using the fallback configuration, the UE may fall back to a suitable cell after a RACHless handover failure in LTM cell switch procedure occurs, thereby minimizing the interruption time or even without experiencing interruption time.

[0057] Principles and embodiments of the present disclosure will be described in detail below with reference to the accompanying drawings. Reference is first made to Fig. IB, which illustrates an example communication system 100 in which embodiments of the present disclosure may be implemented.

[0058] As shown in Fig. IB, the system 100 comprises a CU 110 (which is a network device, and also referred to as a first network device), a source DU 120 (which is a network device, and also referred to as a second network device), and a plurality of prepared candidate DUs 130 prepared by the CU 110. Among the plurality of prepared candidate DUs 130, a respective DU 131 is acted as a target DU 131 for cell switch. As shown in Fig. IB, the system 100 further comprises a terminal device 140 (also referred to as a UE). As shown in Fig. IB, the terminal device 140 is moving from source DU or cell 120 to target DU or cell 131, and a serving cell change needs to be performed at this time point.

[0059] It is to be understood that the particular number of various communication devices, the particular number of various communication links, the particular number of other elements, and the particular shape of the cells as shown in Fig. IB is for illustration purpose only without suggesting any limitations. The communication system 100 may include any suitable number of communication devices, any suitable number of communication links,and any suitable number of other elements and any suitable shape of the cells adapted for implementing embodiments of the present disclosure. In addition, it should be appreciated that there may be various wireless as well as wireline communications (if needed) among all of the communication devices.

[0060] Communications in the communication system 100 may be implemented according to any proper communication protocol(s), comprising, but not limited to, cellular communication protocols of the first generation (1G), the second generation (2G), the third generation (3G), the fourth generation (4G) and the fifth generation (5G) and on the like, wireless local network communication protocols such as Institute for Electrical and Electronics Engineers (IEEE) 1002.11 and the like, and / or any other protocols currently known or to be developed in the future. Moreover, the communication may utilize any proper wireless communication technology, comprising but not limited to: Code Division Multiple Access (CDMA), Frequency Division Multiple Access (FDMA), Time Division Multiple Access (TDM A), Frequency Division Duplex (FDD), Time Division Duplex (TDD), Multiple-Input Multiple-Output (MIMO), Orthogonal Frequency Division Multiple (OFDM), Discrete Fourier Transform spread OFDM (DFT-s-OFDM) and / or any other technologies currently known or to be developed in the future.

[0061] Hereinafter, the example method for performing the RACHless ETM will be described with reference to Fig. 2 to Fig. 6. Reference is first made to Fig.2, which illustrates an exemplary signaling chart illustrating communication process in accordance with some embodiments of the present disclosure.

[0062] As shown in Fig. 2, the CU or first network device 110 determines (205) a radio resource control (RRC) reconfiguration 201 for one or more prepared network devices 130 prepared by the CU or first network device 110. The RRC reconfiguration 201 includes a fallback configuration to be used by a UE or terminal device 140 for performing cell switch when receiving a cell switch command from a source DU or second network device 120. Then, the CU or first network device 110 transmits (210) the RRC reconfiguration 201 to the source DU or second network device 120.

[0063] As shown in Fig. 2, the source DU or second network device 120 receives (215) the RRC reconfiguration 201 from the CU or first network device 110 and then transmits (220) the RRC reconfiguration to the UE or terminal device 140. Then the UE or terminal device 140 receives (225) the RRC reconfiguration 201. As shown in Fig. 2, the source DU orsecond network device 120 further transmits (230) a cell switch command 202 to the UE or terminal device 140 to trigger cell change or cell switch, and the UE or terminal device 140 then receives (235) the cell switch command and then performs (240) cell switch based on the fallback configuration. By using this fallback configuration to perform cell switch, the UE or terminal device 140 may fall back to a suitable cell to establish connection with that cell with minimized interruption time or even without experiencing interruption time of the RACHless handover failure in LTM cell switch procedure.

[0064] In some embodiment, the fallback configuration included in the RRC reconfiguration 201 indicates the terminal device 140 to fall back to the source DU or second network device 120 upon expiry of the TAT of the target DU or cell 131 or upon invalidity of the TA of the target DU / cell 131, and the detailed steps of the mobility procedure for these embodiments will be described with reference to Fig. 3 hereinafter.

[0065] In some embodiments, the fallback configuration included in the RRC reconfiguration 201includes a RACH configuration of the target DU / cell 131, and the fallback configuration indicates the terminal device 140 to access to the target DU / cell 131 based on the RACH configuration upon expiry of the TAT of the target DU / cell 131 or upon invalidity of the TA of the target DU / cell 131, and the detailed steps of the mobility procedure for these embodiments will be described with reference to Fig. 4 hereinafter.

[0066] In some embodiment, the fallback configuration included in the RRC reconfiguration 201 includes an early failure declaration and re-establishment / recovery configuration, based on which, upon expiry of the TAT of the target DU / cell 131 or upon invalidity of the TA of the target DU / cell 131, the terminal device 140 declares failure and initiates re-establishment / recovery procedure, and the detailed steps of the mobility procedure for the embodiments will be described with reference to Fig. 5 hereinafter.

[0067] In some embodiment, in addition to the fallback configuration, the RRC reconfiguration 201 further includes a new RACHless timer, and this new timer is to be used by the terminal device 140 to perform cell switch based on the fallback configuration upon expiry of the new timer regardless of the expiry of the TAT of the target DU / cell 131 or the invalidity of the TA of the target DU / cell 131, and the detailed steps of the mobility procedure for the embodiments will be described with reference to Fig. 6 hereinafter.

[0068] Hereinafter, the exemplary signaling chart 300 for falling back to the source DU / cellbased on the fallback configuration will be described with reference to Fig. 3. In this solution, it is proposed that the UE 140 falls back to the source cell 120 if the TAT of the target cell 131 expires after the cell switch via MAC CE is triggered. Hence, the source cell 120 can reconfigure the UE 140 with a new mobility procedure. Towards fallback to the source DU 120, the fallback configuration indicates the terminal device 140 to fall back to the source DU or second network device 120 upon the expiry of the TAT of the target DU / cell 131 or the invalidity of the TA of the target DU / cell 131. The steps of the mobility procedure are shown in Fig. 3 and the steps are described as follows.

[0069] At steps 1 to 7, the UE 140 sends the L3 measurements to the source DU 120 and those measurements are forwarded to the CU 110. Based on the reported measurements, the CU 110 determines to prepare the target DUs / cells 130. The CU 110 prepares the target DUs / cells 130 and informs the source DU / cell 120 accordingly. At step 8, the CU 110 generates the RRC Reconfiguration for those prepared DUs / cells 130. The CU 110 also configures the fallback condition upon TAT of the target cell expires. The fallback condition for example includes: the validity of the TA of the source DU / cell 120 (i.e., if the TAT of the source / DU 120 has expired), and the link quality between the UE 140 and the source DU / cell 120 (i.e., if the source cell RSRP is above a certain threshold).

[0070] At step 9, via a downlink RRC message, the CU 110 sends the RRC Reconfiguration of the prepared DUs / cells 130 to the source DU 120 that includes the fallback configuration. The CU 110 also informs the source DU 120 about the fallback configuration as the source DU 120 should be also aware that the UE 140 may fallback to source DU 120 upon expiry of TAT of the target cell 131 after MAC CE is triggered. The uplink resource for fallback is pre-configured at source DU 120 for the UE 140 to indicate the return. In one embodiment, at this step, the RACH fallback configuration can also be given to the source DU 120 which can in turn provided it further to the UE 140 in step 19.

[0071] At step 10, the source DU 120 forwards the RRC Reconfiguration of the prepared DUs / cells 130 that includes the fallback configuration to the UE 140. At steps 11 to 12, the UE 140 sends the RRC Reconfiguration complete message to the source DU 120 and the source DU 120 forwards that message to the CU 110 to acknowledge the reception of the RRC Reconfigurations. At step 13, the UE 140 sends the LI measurement reports of serving and candidate cells. At step 14, the source DU 120 determines to trigger the early TA acquisition of the target DU / cell 131. At step 15, the UE 140 sends the PRACHpreamble towards the target DU / cell 131 and the target DU / cell 131 estimates the TA based on the received PRACH preamble. At step 16, the target DU / cell 131 sends the RAR that includes the estimated TA to the source DU 120 via the CU 110. Then, the UE 140 starts the TAT upon receiving the TA (either via RAR at step 17 (option #1) or via MAC CE at step 19 (option #2). Based the LI measurement report transmitted at step 18, once the cell switch condition is met, the source DU 120 sends the MAC CE to trigger the cell change at step 19.

[0072] At step 20, the source DU 120 waits for the UE 140 to come back as the UE 140 may fall back to the source DU 120 if the RACHless failure happens due to TAT expiry. At step 21, after receiving the MAC CE, the UE 140 starts the T304 timer. At step 22, the TAT for the TA of the target DU / cell 131 expires. At step 23, the UE 140 checks the fallback configuration obtained from step 10. Herein, the UE 140 can be configured to check the following: the validity of the TA of the source DU / cell 120 (i.e., if the TAT of the source / DU has expired); and the link quality between the UE 140 and the source DU / cell 120 (i.e., if the source cell RSRP is above a certain threshold). In one embodiment, the UE 140 may attempt to connect back to the source DU / cell 120 if the configured conditions are satisfied. In another embodiment, the UE 140 may not be configured with any condition and the UE 140 directly attempts to connect back to the source DU 120. At step 24, the UE 140 does not wait for the T304 to expire and connects back to the source DU / cell 120. The UE 140 also reports the TAT expiry of the target DU / cell 131 TA after MAC CE is received.

[0073] With this solution, the UE 140 falls back to the source cell 120 after TAT expiry of the target cell of handover, if source TAT has not expired but target TAT has expired. The uplink resource for fallback is pre-configured at the source DU 120 for the UE 140 to indicate the return. The UE 140 does not wait until T304 expiry and connects back to source cell 120 to avoid connection failure or longer interruption time of the RACHless handover failure in LTM cell switch procedure.

[0074] Hereinafter, the exemplary signaling chart 400 for falling back to the target DU / cell 131 based on the fallback configuration will be described with reference to Fig. 4. In this solution, it is proposed that the UE 140 will fall back to RACH procedure towards the target cell 131 if the TAT of the target cell 131 expires after the cell switch is triggered via MAC CE, which is received from the source DU 120. Hence, the UE 140 can still proceed withhandover towards the target DU / cell 131, although the RACHless handover is not possible. The steps of the mobility procedure are shown in Fig. 4 and the different than the steps of Fig. 3 are described as follows.

[0075] At step 8, the CU 110 provides a RACH configuration in the RRC Reconfiguration of the target DU / cell 131 that the UE 140 can use as fallback option for the RACHless handover. In one embodiment, the RACH fallback configuration can be given to the source DU 120 which can in turn further provide RACH fallback configuration to the UE 140 in step 19. At step 22: after the TAT expiry for the TA of the target DU / cell 131, the UE 140 falls back to RACH-based LTM procedure, i.e., the UE 140 initiates the RACH procedure towards the target DU / cell 131 that is triggered by MAC CE. In one embodiment, the UE 140 will use the RACH configuration provided in the RRC Reconfiguration of the target cell preparation determined by the CU 110. In another embodiment, the UE 140 will receive the RACH configuration via MAC CE cell switch command from the source DU 120 at step 19, and the source DU 120 includes the RACH configuration that is provided by the CU 110.

[0076] At step 23, the UE 140 performs RACH procedure towards the target DU / cell 131 and handovers to the target DU / cell 131. Hence, the UE 140 does not wait until the T304 expires and accesses the target DU / cell 131 upon expiry of the TAT or invalidity of TA of the target DU / cell 131, thereby reducing the interruption time of the RACHless failure in LTM. At step 24, the UE 140 reports the TAT expiry and RACH fallback that the UE 140 experienced during the LTM execution. At step 25, the UE 140 and the network proceed further with the LTM completion.

[0077] By this solution, the UE 140 falls back to RACH procedure after TAT expiry of the target cell of handover or based on radio-condition of the Reference Signal (SSB index) used as Quasi-co location (QCL) reference for PUSCH transmission (for using RACH configuration given in LTM RRC Reconfiguration). Further, the UE attempts for PUSCH transmission on cell-switch but switches to RACH-based scheme if the radio condition of the RS index that is used as reference for PUSCH transmission deteriorates or TAT expires before T304 expires. By this process, the UE 140 does not wait until T304 expires and initiates the RACH procedure that may have better coverage, e.g., switch to a better SSB / beam.

[0078] Hereinafter, the exemplary signaling chart 500 for performing fallback based on early failure declaration and early recovery / re-establishment procedure will be describedwith reference to Fig. 5. In this solution, it is proposed that the UE 140 declares early failure and initiates early recovery / re-establishment procedure if the TAT of the target cell expires after the cell switch via MAC CE is triggered. Hence, the UE 140 does not wait until the expiry of T304 and reduces the interruption time by detecting failure faster. The steps of the mobility procedure are shown in Fig. 5 and the steps that are different from those of Fig. 3 are described as follows.

[0079] As shown in Fig. 5, at step 8, the CU 110 configures the early failure declaration and recovery / re-establishment configuration for the UE 140 if the TAT expires after the MAC CE is triggered. In one embodiment, early failure, recovery / re-establishment configuration will be configured in the RRC Reconfiguration for the prepared target DUs / cells 130. In another embodiment, the early failure, recovery / re-establishment configuration will be provided from the CU 110 to the source DU 120. And then, the source DU 120 will provide further the recovery / re-establishment configuration to the UE 140 via MAC CE cell switch command.

[0080] At steps 22 to 24, after the cell switch is triggered via MAC CE, if the TAT of the TA for the target DU / cell 131 expires, the UE 140 declares failure without waiting for any further timer to expire, i.e., without waiting for T304 expiry. Then, if the UE 140 is configured with the recovery procedure, the UE 140 initiates the LTM recovery procedure, i.e., uses one of the preparation configurations for faster re-connection towards one of the prepared cells 130 which may be best or available candidate cell or prepared cell. If the recovery procedure is not configured, or if there is no suitable cell for the recovery procedure, the UE 140 proceeds with the regular re-establishment procedure to connect to a suitable cell after the TAT expiry. This suitable cell can be any cell that is suitable for the UE 140 to connect or re-establish. At step 25, the UE 140 reports the early failure declaration due to TAT expiry during RACHless LTM and indicates the recovery / re-establishment procedure that the UE 140 went through after the early failure declaration. At step 26, the UE 140 and the network proceed further with the LTM completion.

[0081] By this solution, the UE 140 declares early failure and initiates re- establishment / recovery after the TAT expiry of the target cell of handover. The UE 140 does not wait until T304 expiry and initiates the re-establishment (or recovery if configured). It may be a good approach in case fallback mechanisms are not applicable.

[0082] Hereinafter, the exemplary signaling chart 600 for performing fallback based on anew RACHless timer will be described with reference to Fig. 6. In this solution, an enhancement is proposed that will utilize a new timer, i.e., a RACHless timer that the network can control the RACHless failure with a timer different than the T304 timer. This is an enhancement for previous solutions described with reference to Figs. 3 to 5. In the case that the TA is not received with MAC CE, the UE 140 starts a RACHless timer or keeps track of the number of PUSCH transmission attempts before applying any other fallback mechanism (either fallback to RACH procedure, fallback to source cell, or early failure).

[0083] In the previous solutions, i.e., solutions described with reference to Figs. 3 to 5, the fallback mechanisms or early failure mechanisms are triggered by the expiry of the TAT or invalidity of TA of the target cell / DU 131 during RACHless LTM. However, in this solution, an enhancement for the triggering of the aforementioned solutions is enhanced with a new timer, in which the CU 110 configures this new timer or the source DU 120 configures this new timer to the UE 140 along with the MAC CE configured (for example, at steps 8 to 10). When the UE 140 receives the MAC CE, the UE 140 starts the RACHless timer if the MAC CE indicates or triggers RACHless cell switch. When the RACHless timer expires, irrespective of the TAT expiry (before or after TAT expires) or the invalidity of the TA, the UE 140 initiates one of the procedures described with reference to Figs. 3 to 5.

[0084] With this method, the network has the flexibility to control the RACHless procedure and its duration irrespective of the TAT timer (used for TA validity) and T304 timer (used for radio link quality). The steps of the mobility procedure are shown in Fig. 6 below. The actions that the UE 140 takes regarding the RACHless timer expiry, in steps 22 and 23.

[0085] As shown in Fig. 6, at step 8, the CU 110 generates the RRC reconfiguration including the fallback configuration and the new RACHless timer. At steps 9 to 10, the RRC reconfiguration including the fallback configuration and the new RACHless timer is transmitted to the source DU 120 and the terminal device 140.

[0086] At step 21, when the UE 140 receives the MAC CE from the source DU 120, the UE 140 starts the RACHless timer if the MAC CE indicates or triggers RACHless cell switch. At step 22, the RACHless timer expires, whereas the TAT of target cell 131 does not expire yet, and the expiry of the RACHless timer initiates a fallback mechanism according to any one of the procedures described with reference to Figs. 3 to 5 such that the fallback is performed based on a fallback to source cell, fallback to RACH procedure, or fallback based on early failure and re-establishment / recovery procedure.

[0087] In the present disclosure, the LTM switching command provides the timer value (or equivalently the number of PUSCH transmission attempts) during which the UE 140 should attempt to send Message 3 completing the handover execution (e.g., RRC Reconfiguration Complete) over PUSCH before switching to RACH-based access. For RACH-less handover with uplink grant provided by Target cell: In case of Intra-DU RACH-less scenario, PUSCH resource is not allocated at the time of switching. Instead, the UE 140 may get the UL grant for PUSCH from the PDCCH corresponds to best beam. If the UE 140 is not receiving the DCI for uplink grant within a short duration (Timer to switch for RACH-less) or number of PDCCH occasions, UE will switch to RACH based access.

[0088] Fig. 7 illustrates a flowchart of a method 700 implemented at a first network device (e.g. the CU 110) in accordance with some embodiments of the present disclosure. For the purpose of discussion, the method 700 will be described from the perspective of the CU 110 with reference to Fig. IB.

[0089] At block 710, the first network device 110 determines a radio resource control (RRC) reconfiguration for one or more prepared network devices prepared by the first network device, wherein the RRC reconfiguration comprises a fallback configuration to be used by a terminal device for performing cell switch. At block 720, the first network device 110 transmits, to a second network device, the RRC reconfiguration.

[0090] In some embodiments, the fallback configuration indicates the terminal device to fall back to the second network device upon expiry of a time alignment timer (TAT) of a target network device among the one or more prepared network devices or upon invalidity of a timing advance (TA) of the target network device. In some embodiments, the first network device 110 further determines a fallback condition, wherein upon satisfaction of the fallback condition and the expiry of the TAT of the target network device or the invalidity of the TA of the target network device, the terminal device connects back to the second network device. In some embodiments, the first network device 110 further transmits the fallback configuration to the second network device.

[0091] In some embodiments, the fallback configuration comprises a random access channel (RACH) configuration of a target network device among the one or more prepared network devices, and the fallback configuration indicates the terminal device to access to the target network device based on the RACH configuration upon expiry of a time alignment timer (TAT) of the target network device or upon invalidity of a timing advance (TA) of thetarget network device. In some embodiments, the RACH configuration provided in the RRC reconfiguration is to be used by the terminal device, or the first network device further transmits the RACH configuration to the second network device which in turn transmits the RACH configuration to the terminal device via a media access control (MAC) control element (MAC CE) cell switch command.

[0092] In some embodiments, the fallback configuration comprises an early failure declaration and recovery configuration, based on which, upon expiry of a time alignment timer (TAT) of a target network device among the one or more prepared network devices or upon invalidity of a timing advance (TA) of the target network device, the terminal device declares failure and initiates recovery procedure towards the one or more prepared network devices. In some embodiments, the fallback configuration comprises an early failure declaration and re-establishment configuration, based on which, upon expiry of a time alignment timer (TAT) of a target network device among the one or more prepared network devices or upon invalidity of a timing advance (TA) of the target network device, the terminal device declares failure and initiates re-establishment procedure towards a further network device that is suitable for the terminal device to re-establish or connect.

[0093] In some embodiments, the first network device 110 further determines a further timer in the RRC reconfiguration, wherein the further timer is to be used by the terminal device to perform cell switch based on the fallback configuration upon expiry of the further timer regardless of the expiry of the TAT of the target network device or the invalidity of the TA of the target network device, such that the terminal device is to be switched to at least one of the following: the second network device; the target network device; another network device rather than the target network device among the one or more prepared network devices; or a further network device that is suitable for the terminal device to re-establish or connect.

[0094] Fig. 8 illustrates a flowchart of a method 800 implemented at a second network device in accordance with some embodiments of the present disclosure. For the purpose of discussion, the method 800 will be described from the perspective of the source DU 120 with reference to Fig. IB.

[0095] At block 810, the second network device 120 receives, from a first network device, a radio resource control (RRC) reconfiguration for one or more prepared network devices, wherein the RRC reconfiguration comprises a fallback configuration to be used by a terminaldevice for performing cell switch. At block 820, the second network device 120 transmits, to the terminal device, the RRC reconfiguration.

[0096] In some embodiments, the second network device 120 further transmits, to the terminal device, a cell switch command, and the fallback configuration is to be used by the terminal device for performing cell switch upon reception of the cell switch command and expiry of a time alignment timer (TAT) of a target network device among the one or more prepared network devices or invalidity of a timing advance (TA) of the target network device.

[0097] In some embodiments, the second network device 120 further transmits, to the terminal device, a cell switch command, and the fallback configuration is to be used by the terminal device for performing cell switch upon reception of the cell switch command and expiry of a further timer comprised in the RRC reconfiguration configured by the first network device regardless of expiry of a time alignment timer (TAT) of a target network device among the one or more prepared network devices or invalidity of a timing advance (TA) of the target network device.

[0098] In some embodiments, the second network device 120 further transmit, to the terminal device, a cell switch command comprising a further timer, and the fallback configuration is to be used by the terminal device for performing cell switch upon reception of the cell switch command and expiry of a further timer configured by the second network device regardless of expiry of a time alignment timer (TAT) of a target network device among the one or more prepared network devices or invalidity of a timing advance (TA) of the target network device.

[0099] Fig. 9 illustrates a flowchart of a method implemented at a terminal device according to some other embodiments of the present disclosure. For the purpose of discussion, the method 900 will be described from the perspective of the terminal device 140 with reference to Fig. IB.

[0100] At block 910, the terminal device 140 receives, from a second network device, a radio resource control (RRC) reconfiguration for one or more prepared network devices prepared by a first network device, wherein the RRC reconfiguration is determined by the first network device and comprises a fallback configuration. At block 920, the terminal device 140 receives, from the second network device, a cell switch command. At block 930, the terminal device 140 performs, based on the fallback configuration, a cell switch.

[0101] In some embodiments, based on the fallback configuration, the terminal device 140 falls back to the second network device upon expiry of a time alignment timer (TAT) of a target network device among the one or more prepared network devices or upon invalidity of a timing advance (TA) of the target network device. In some embodiments, based on the fallback configuration, the terminal device 140 falls back to the second network device upon satisfaction of a fallback condition determined by the first network device and expiry of a time alignment timer (TAT) of a target network device among the one or more prepared network devices or invalidity of a timing advance (TA) of the target network device. In some embodiments, the fallback condition comprises at least one of the following: a validity of a timing advance (TA) of the second network device; or a link quality between the terminal device and the second network device. In some embodiments, the terminal device 140 falls back to the second network device through an uplink resource pre-configured by the second network device.

[0102] In some embodiments, based on a random access channel (RACH) configuration of a target network device among the one or more prepared network devices comprised in the fallback configuration, the terminal device 140 accesses to the target network device upon expiry of a time alignment timer (TAT) of the target network device or upon invalidity of a timing advance (TA) of the target network device. In some embodiments, the terminal device 140 uses the RACH configuration provided in the RRC reconfiguration; or receives, from the second network device, the RACH configuration via a media access control (MAC) control element (MAC CE) cell switch command.

[0103] In some embodiments, based on the fallback configuration comprising an early failure declaration and recovery configuration, the terminal device 140 declares failure and initiates recovery procedure towards the one or more prepared network devices upon expiry of a time alignment timer (TAT) of a target network device among the one or more prepared network devices or upon invalidity of a timing advance (TA) of the target network device. In some embodiments, based on the fallback configuration comprising an early failure declaration and re-establishment configuration, the terminal device 140 declares failure and initiates re-establishment procedure towards a further network device that is suitable for the terminal device to re-establish or connect upon expiry of a time alignment timer (TAT) of a target network device among the one or more prepared network devices or upon invalidity of a timing advance (TA) of the target network device.

[0104] In some embodiments, upon expiry of a further timer configured by the first network device in the RRC reconfiguration or configured by the second network device in the cell switch command, regardless of the expiry of the TAT of the target network device or the invalidity of the timing TA of the target network device, the terminal device 140 performs the cell switch based on the fallback configuration such that the terminal device is to be switched to at least one of the following: the second network device; the target network device; another network device rather than the target network device among the one or more prepared network devices; or a further network device that is suitable for the terminal device to re-establish or connect. In some embodiments, the terminal device 140 starts the further timer upon reception of the cell switch command.

[0105] In some embodiments, an apparatus (for example, the CU 110) capable of performing the method 700 may comprise means for performing the respective steps of the method 700. The means may be implemented in any suitable form. For example, the means may be implemented in a circuitry or software module.

[0106] In some embodiments, the apparatus comprises: means for determining a radio resource control (RRC) reconfiguration for one or more prepared network devices prepared by the first network device, wherein the RRC reconfiguration comprises a fallback configuration to be used by a terminal device for performing cell switch; and means for transmitting to a second network device, the RRC reconfiguration.

[0107] In some embodiments, the fallback configuration indicates the terminal device to fall back to the second network device upon expiry of a time alignment timer (TAT) of a target network device among the one or more prepared network devices or upon invalidity of a timing advance (TA) of the target network device. In some embodiments, the apparatus further comprises means for determining a fallback condition, wherein upon satisfaction of the fallback condition and the expiry of the TAT of the target network device or the invalidity of the TA of the target network device, the terminal device connects back to the second network device. In some embodiments, the apparatus further comprises means for transmitting the fallback configuration to the second network device.

[0108] In some embodiments, the fallback configuration comprises a random access channel (RACH) configuration of a target network device among the one or more prepared network devices, and the fallback configuration indicates the terminal device to access to the target network device based on the RACH configuration upon expiry of a time alignmenttimer (TAT) of the target network device or upon invalidity of a timing advance (TA) of the target network device. In some embodiments, the RACH configuration provided in the RRC reconfiguration is to be used by the terminal device, or the apparatus further comprises means for transmitting the RACH configuration to the second network device which in turn transmits the RACH configuration to the terminal device via a media access control (MAC) control element (MAC CE) cell switch command.

[0109] In some embodiments, the fallback configuration comprises an early failure declaration and recovery configuration, based on which, upon expiry of a time alignment timer (TAT) of a target network device among the one or more prepared network devices or upon invalidity of a timing advance (TA) of the target network device, the terminal device declares failure and initiates recovery procedure towards the one or more prepared network devices. In some embodiments, the fallback configuration comprises an early failure declaration and re-establishment configuration, based on which, upon expiry of a time alignment timer (TAT) of a target network device among the one or more prepared network devices or upon invalidity of a timing advance (TA) of the target network device, the terminal device declares failure and initiates re-establishment procedure towards a further network device that is suitable for the terminal device to re-establish or connect.

[0110] In some embodiments, the apparatus further comprises means for determining a further timer in the RRC reconfiguration, wherein the further timer is to be used by the terminal device to perform cell switch based on the fallback configuration upon expiry of the further timer regardless of the expiry of the TAT of the target network device or the invalidity of the TA of the target network device, such that the terminal device is to be switched to at least one of the following: the second network device; the target network device; another network device rather than the target network device among the one or more prepared network devices; or a further network device that is suitable for the terminal device to re-establish or connect.

[0111] In some embodiments, the apparatus further comprises means for performing other steps in some embodiments of the method 700. In some embodiments, the means comprises at least one processor and at least one memory including computer program code, the at least one memory and computer program code configured to, with the at least one processor, cause the performance of the apparatus.

[0112] In some embodiments, an apparatus (for example, the source DU 120) capable of performing the method 800 may comprise means for performing the respective steps of the method 800. The means may be implemented in any suitable form. For example, the means may be implemented in a circuitry or software module.

[0113] In some embodiments, the apparatus comprises: means for receiving, from a first network device, a radio resource control (RRC) reconfiguration for one or more prepared network devices, wherein the RRC reconfiguration comprises a fallback configuration to be used by a terminal device for performing cell switch; and means for transmitting, to the terminal device, the RRC reconfiguration.

[0114] In some embodiments, the apparatus further comprises means for transmitting, to the terminal device, a cell switch command, and the fallback configuration is to be used by the terminal device for performing cell switch upon reception of the cell switch command and expiry of a time alignment timer (TAT) of a target network device among the one or more prepared network devices or invalidity of a timing advance (TA) of the target network device.

[0115] In some embodiments, the apparatus further comprises means for transmitting, to the terminal device, a cell switch command, and the fallback configuration is to be used by the terminal device for performing cell switch upon reception of the cell switch command and expiry of a further timer comprised in the RRC reconfiguration configured by the first network device regardless of expiry of a time alignment timer (TAT) of a target network device among the one or more prepared network devices or invalidity of a timing advance (TA) of the target network device.

[0116] In some embodiments, the apparatus further comprises means for transmitting, to the terminal device, a cell switch command comprising a further timer, and the fallback configuration is to be used by the terminal device for performing cell switch upon reception of the cell switch command and expiry of the further timer configured by the second network device regardless of expiry of a time alignment timer (TAT) of a target network device among the one or more prepared network devices or invalidity of a timing advance (TA) of the target network device.

[0117] In some embodiments, the apparatus further comprises means for performing other steps in some embodiments of the method 800. In some embodiments, the meanscomprises at least one processor and at least one memory including computer program code, the at least one memory and computer program code configured to, with the at least one processor, cause the performance of the apparatus.

[0118] In some embodiments, an apparatus (for example, a terminal device 140) capable of performing the method 900 may comprise means for performing the respective steps of the method 900. The means may be implemented in any suitable form. For example, the means may be implemented in a circuitry or software module.

[0119] In some embodiments, the apparatus comprises: means for receive, from a second network device, a radio resource control (RRC) reconfiguration for one or more prepared network devices prepared by a first network device, wherein the RRC reconfiguration is determined by the first network device and comprises a fallback configuration; means for receiving receive, from the second network device, a cell switch command; and means for performing, based on the fallback configuration, a cell switch.

[0120] In some embodiments, the apparatus further comprises means for falling back to the second network device based on the fallback configuration upon expiry of a time alignment timer (TAT) of a target network device among the one or more prepared network devices or upon invalidity of a timing advance (TA) of the target network device. In some embodiments, the apparatus further comprises means for falling back to the second network device based on the fallback configuration upon satisfaction of a fallback condition determined by the first network device and expiry of a time alignment timer (TAT) of a target network device among the one or more prepared network devices or invalidity of a timing advance (TA) of the target network device.

[0121] In some embodiments, the fallback condition comprises at least one of the following: a validity of a timing advance (TA) of the second network device; or a link quality between the terminal device and the second network device. In some embodiments, the apparatus further comprises means for falling back to the second network device through an uplink resource pre-configured by the second network device.

[0122] In some embodiments, the apparatus further comprises means for accessing to the target network device upon expiry of a time alignment timer (TAT) of the target network device or upon invalidity of a timing advance (TA) of the target network device, based on a random access channel (RACH) configuration of a target network device among the one ormore prepared network devices comprised in the fallback configuration. In some embodiments, the apparatus further comprises means for using the RACH configuration provided in the RRC reconfiguration; or receiving, from the second network device, the RACH configuration via a media access control (MAC) control element (MAC CE) cell switch command.

[0123] In some embodiments, the apparatus further comprises means for declaring failure and initiating recovery procedure towards the one or more prepared network devices based on the fallback configuration comprising an early failure declaration and recovery configuration, upon expiry of a time alignment timer (TAT) of a target network device among the one or more prepared network devices or upon invalidity of a timing advance (TA) of the target network device. In some embodiments, the apparatus further comprises means for declaring failure and initiating re-establishment procedure towards a further network device that is suitable for the terminal device to re-establish or connect based on the fallback configuration comprising an early failure declaration and re-establishment configuration upon expiry of a time alignment timer (TAT) of a target network device among the one or more prepared network devices or upon invalidity of a timing advance (TA) of the target network device.

[0124] In some embodiments, the apparatus further comprises means for performing the cell switch based on the fallback configuration such that the terminal device is to be switched to at least one of the following: the second network device; the target network device; another network device rather than the target network device among the one or more prepared network devices; or a further network device that is suitable for the terminal device to re-establish or connect, upon expiry of a further timer configured by the first network device in the RRC reconfiguration or configured by the second network device in the cell switch command, regardless of the expiry of the TAT of the target network device or the invalidity of the timing TA of the target network device. In some embodiments, the apparatus further comprises means for starting the further timer upon reception of the cell switch command.

[0125] In some embodiments, the apparatus further comprises means for performing other steps in some embodiments of the method 900. In some embodiments, the means comprises at least one processor and at least one memory including computer program code,the at least one memory and computer program code configured to, with the at least one processor, cause the performance of the apparatus.

[0126] Fig. 10 is a simplified block diagram of a device 1000 that is suitable for implementing embodiments of the present disclosure. The device 1000 may be provided to implement the communication device, for example the terminal device 140, and the network devices 110, 120, and 130 as shown in Fig. IB. As shown, the device 1000 includes one or more processors 1010, one or more memories 1020 coupled to the processor 1010, and one or more communication modules 1040 coupled to the processor 1010.

[0127] The communication module 1040 is for bidirectional communications. The communication module 1040 has at least one antenna to facilitate communication. The communication interface may represent any interface that is necessary for communication with other network devices.

[0128] The processor 1010 may be of any type suitable to the local technical network and may include one or more of the following: general purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs) and processors based on multicore processor architecture, as non-limiting examples. The device 1000 may have multiple processors, such as an application specific integrated circuit chip that is slaved in time to a clock which synchronizes the main processor.

[0129] The memory 1020 may include one or more non-volatile memories and one or more volatile memories. Examples of the non-volatile memories include, but are not limited to, a read only memory (ROM) 1024, an electrically programmable read only memory (EPROM), a flash memory, a hard disk, a compact disc (CD), a digital video disk (DVD), and other magnetic storage and / or optical storage. Examples of the volatile memories include, but are not limited to, a random access memory (RAM) 1022 and other volatile memories that may not last in the power-down duration.

[0130] A computer program 1030 includes computer executable instructions that are executed by the associated processor 1010. The program 1030 may be stored in the ROM 1024. The processor 1010 may perform any suitable actions and processing by loading the program 1030 into the RAM 1022.

[0131] The embodiments of the present disclosure may be implemented by means of the program so that the device 1000 may perform any process of the disclosure as discussed withreference to Figs. 2 to 9. The embodiments of the present disclosure may also be implemented by hardware or by a combination of software and hardware.

[0132] In some embodiments, the program 1030 may be tangibly contained in a computer readable medium which may be included in the device 1000 (such as in the memory 1020) or other storage devices that are accessible by the device 1000. The device 1000 may load the program 1030 from the computer readable medium to the RAM 1022 for execution. The computer readable medium may include any types of tangible non-volatile storage, such as ROM, EPROM, a flash memory, a hard disk, CD, DVD, and the like.

[0133] Fig. 11 illustrates an example of the computer readable medium 1100 in form of CD or DVD in accordance with some embodiments of the present disclosure. The computer readable medium has the program 1030 stored thereon. It is noted that although the computer-readable medium 1100 is depicted in form of CD or DVD, the computer- readable medium 1100 may be in any other form suitable for carry or hold the program 1030.

[0134] Generally, various embodiments of the present disclosure may be implemented in hardware or special purpose circuits, software, logic or any combination thereof. Some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software which may be executed by a controller, microprocessor or other computing device. While various aspects of embodiments of the present disclosure are illustrated and described as block diagrams, flowcharts, or using some other pictorial representations, it is to be understood that the block, apparatus, system, technique or method described herein may be implemented in, as non-limiting examples, hardware, software, firmware, special purpose circuits or logic, general purpose hardware or controller or other computing devices, or some combination thereof.

[0135] The present disclosure also provides at least one computer program product tangibly stored on a non-transitory computer readable storage medium. The computer program product includes computer-executable instructions, such as those included in program modules, being executed in a device on a target real or virtual processor, to carry out the methods 700 to 900 as described above with reference to Fig. 7 to Fig. 9. Generally, program modules include routines, programs, libraries, objects, classes, components, data structures, or the like that perform particular tasks or implement particular abstract data types. The functionality of the program modules may be combined or split between program modules as desired in various embodiments. Machine-executable instructions for programmodules may be executed within a local or distributed device. In a distributed device, program modules may be located in both local and remote storage media.

[0136] Program code for carrying out methods of the present disclosure may be written in any combination of one or more programming languages. These program codes may be provided to a processor or controller of a general purpose computer, special purpose computer, or other programmable data processing apparatus, such that the program codes, when executed by the processor or controller, cause the functions / operations specified in the flowcharts and / or block diagrams to be implemented. The program code may execute entirely on a machine, partly on the machine, as a stand-alone software package, partly on the machine and partly on a remote machine or entirely on the remote machine or server.

[0137] In the context of the present disclosure, the computer program codes or related data may be carried by any suitable carrier to enable the device, apparatus or processor to perform various processes and operations as described above. Examples of the carrier include a signal, computer readable medium, and the like.

[0138] The computer readable medium may be a computer readable signal medium or a computer readable storage medium. A computer readable medium may include but not limited to an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of the computer readable storage medium would include an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. The term “non-transitory,” as used herein, is a limitation of the medium itself (i.e., tangible, not a signal) as opposed to a limitation on data storage persistency (e.g., RAM vs. ROM).

[0139] Further, while operations are depicted in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order, or that all illustrated operations be performed, to achieve desirable results. In certain circumstances, multitasking and parallel processing may be advantageous. Likewise, while several specific implementation details are contained in the above discussions, these should not be construed as limitations on the scope of the presentdisclosure, but rather as descriptions of features that may be specific to particular embodiments. Certain features that are described in the context of separate embodiments may also be implemented in combination in a single embodiment. Conversely, various features that may be described in the context of a single embodiment may also be implemented in multiple embodiments separately or in any suitable sub-combination.

[0140] Although the present disclosure has been described in languages specific to structural features and / or methodological acts, it is to be understood that the present disclosure defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above may be disclosed as example forms of implementing the claims.

Claims

WHAT IS CLAIMED IS:

1. A first network device comprising: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the first network device at least to: determine a radio resource control (RRC) reconfiguration for one or more prepared network devices prepared by the first network device, wherein the RRC reconfiguration comprises a fallback configuration to be used by a terminal device for performing cell switch; and transmit, to a second network device, the RRC reconfiguration.

2. The first network device of claim 1, wherein: the fallback configuration indicates the terminal device to fall back to the second network device upon expiry of a time alignment timer (TAT) of a target network device among the one or more prepared network devices or upon invalidity of a timing advance (TA) of the target network device.

3. The first network device of claim 2, wherein the first network device is further caused to: determine a fallback condition, wherein upon satisfaction of the fallback condition and the expiry of the TAT of the target network device or the invalidity of the TA of the target network device, the terminal device connects back to the second network device.

4. The first network device of any of claims 1-3, wherein the first network device is further caused to: transmit the fallback configuration to the second network device.

5. The first network device of claim 1, wherein: the fallback configuration comprises a random access channel (RACH) configuration of a target network device among the one or more prepared network devices, and the fallback configuration indicates the terminal device to access to the target network device based on the RACH configuration upon expiry of a time alignment timer(TAT) of the target network device or upon invalidity of a timing advance (TA) of the target network device.

6. The first network device of claim 5, wherein: the RACH configuration provided in the RRC reconfiguration is to be used by the terminal device, or the first network device is further caused to transmit the RACH configuration to the second network device which in turn transmits the RACH configuration to the terminal device via a media access control (MAC) control element (MAC CE) cell switch command.

7. The first network device of claim 1, wherein the fallback configuration comprises an early failure declaration and recovery configuration, based on which, upon expiry of a time alignment timer (TAT) of a target network device among the one or more prepared network devices or upon invalidity of a timing advance (TA) of the target network device, the terminal device declares failure and initiates recovery procedure towards the one or more prepared network devices.

8. The first network device of claim 1, wherein the fallback configuration comprises an early failure declaration and re-establishment configuration, based on which, upon expiry of a time alignment timer (TAT) of a target network device among the one or more prepared network devices or upon invalidity of a timing advance (TA) of the target network device, the terminal device declares failure and initiates re-establishment procedure towards a further network device that is suitable for the terminal device to re-establish or connect.

9. The first network device of any of claims 2 to 8, wherein the first network device is further caused to: determine a further timer in the RRC reconfiguration, wherein the further timer is to be used by the terminal device to perform cell switch based on the fallback configuration upon expiry of the further timer regardless of the expiry of the TAT of the target network device or the invalidity of the TA of the target network device, such that the terminal device is to be switched to at least one of the following: the second network device; the target network device;another network device rather than the target network device among the one or more prepared network devices; or a further network device that is suitable for the terminal device to re-establish or connect.

10. A second network device comprising: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the second network device at least to: receive, from a first network device, a radio resource control (RRC) reconfiguration for one or more prepared network devices, wherein the RRC reconfiguration comprises a fallback configuration to be used by a terminal device for performing cell switch; and transmit, to the terminal device, the RRC reconfiguration.

11. The second network device of claim 10, wherein the second network device is further caused to: transmit, to the terminal device, a cell switch command, wherein the fallback configuration is to be used by the terminal device for performing cell switch upon reception of the cell switch command and expiry of a time alignment timer (TAT) of a target network device among the one or more prepared network devices or invalidity of a timing advance (TA) of the target network device.

12. The second network device of claim 10, wherein the second network device is further caused to: transmit, to the terminal device, a cell switch command, wherein the fallback configuration is to be used by the terminal device for performing cell switch upon reception of the cell switch command and expiry of a further timer comprised in the RRC reconfiguration configured by the first network device regardless of expiry of a time alignment timer (TAT) of a target network device among the one or more prepared network devices or invalidity of a timing advance (TA) of the target network device.

13. The second network device of claim 10, wherein the second network device is further caused to: transmit, to the terminal device, a cell switch command comprising a further timer, wherein the fallback configuration is to be used by the terminal device for performing cell switch upon reception of the cell switch command and expiry of the further timer configured by the second network device regardless of expiry of a time alignment timer (TAT) of a target network device among the one or more prepared network devices or invalidity of a timing advance (TA) of the target network device.

14. A terminal device comprising: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the terminal device at least to: receive, from a second network device, a radio resource control (RRC) reconfiguration for one or more prepared network devices prepared by a first network device, wherein the RRC reconfiguration is determined by the first network device and comprises a fallback configuration; receive, from the second network device, a cell switch command; and perform, based on the fallback configuration, a cell switch.

15. The terminal device of claim 14, wherein the terminal device is caused to: based on the fallback configuration, fall back to the second network device upon expiry of a time alignment timer (TAT) of a target network device among the one or more prepared network devices or upon invalidity of a timing advance (TA) of the target network device.

16. The terminal device of claim 14, wherein the terminal device is caused to: based on the fallback configuration, fall back to the second network device upon satisfaction of a fallback condition determined by the first network device and expiry of a time alignment timer (TAT) of a target network device among the one or more prepared network devices or invalidity of a timing advance (TA) of the target network device.

17. The terminal device of claim 16, wherein the fallback condition comprises at least one of the following: a validity of a timing advance (TA) of the second network device; or a link quality between the terminal device and the second network device.

18. The terminal device of any of claims 15 to 17, wherein the terminal device is caused to: fall back to the second network device through an uplink resource pre-configured by the second network device.

19. The terminal device of claim 14, wherein the terminal device is caused to: based on a random access channel (RACH) configuration of a target network device among the one or more prepared network devices comprised in the fallback configuration, access to the target network device upon expiry of a time alignment timer (TAT) of the target network device or upon invalidity of a timing advance (TA) of the target network device.

20. The terminal device of claim 19, wherein the terminal device is caused to: use the RACH configuration provided in the RRC reconfiguration; or receive, from the second network device, the RACH configuration via a media access control (MAC) control element (MAC CE) cell switch command.

21. The terminal device of claim 14, wherein the terminal device is caused to: based on the fallback configuration comprising an early failure declaration and recovery configuration, declare failure and initiate recovery procedure towards the one or more prepared network devices upon expiry of a time alignment timer (TAT) of a target network device among the one or more prepared network devices or upon invalidity of a timing advance (TA) of the target network device.

22. The terminal device of claim 14, wherein the terminal device is caused to: based on the fallback configuration comprising an early failure declaration and reestablishment configuration, declare failure and initiate re-establishment procedure towards a further network device that is suitable for the terminal device to re-establish or connect upon expiry of a time alignment timer (TAT) of a target network device among the one ormore prepared network devices or upon invalidity of a timing advance (TA) of the target network device.

23. The terminal device of any of claims 15 to 22, wherein the terminal device is caused to: upon expiry of a further timer configured by the first network device in the RRC reconfiguration or configured by the second network device in the cell switch command, regardless of the expiry of the TAT of the target network device or the invalidity of the timing TA of the target network device, perform the cell switch based on the fallback configuration such that the terminal device is to be switched to at least one of the following: the second network device; the target network device; another network device rather than the target network device among the one or more prepared network devices; or a further network device that is suitable for the terminal device to re-establish or connect.

24. The terminal device of claim 23, wherein the terminal device is caused to: start the further timer upon reception of the cell switch command.

25. A method comprising: determining, at a first network device, a radio resource control (RRC) reconfiguration for one or more prepared network devices prepared by the first network device, wherein the RRC reconfiguration comprises a fallback configuration to be used by a terminal device for performing cell switch; and transmitting, from first network device to a second network device, the RRC reconfiguration.

26. A method comprising: receiving, at a second network device from a first network device, a radio resource control (RRC) reconfiguration for one or more prepared network devices, wherein the RRC reconfiguration comprises a fallback configuration to be used by a terminal device for performing cell switch; andtransmitting, from the second network device to the terminal device, the RRC reconfiguration.

27. A method comprising: receiving, at a terminal device from a second network device, a radio resource control (RRC) reconfiguration for one or more prepared network devices prepared by a first network device, wherein the RRC reconfiguration is determined by the first network device and comprises a fallback configuration; receiving, from the second network device, a cell switch command; and performing, based on the fallback configuration, a cell switch.

28. An apparatus comprising: means for determining, at a first network device, a radio resource control (RRC) reconfiguration for one or more prepared network devices prepared by the first network device, wherein the RRC reconfiguration comprises a fallback configuration to be used by a terminal device for performing cell switch; and means for transmitting, from first network device to a second network device, the RRC reconfiguration.

29. An apparatus comprising: means for receiving, at a second network device from a first network device, a radio resource control (RRC) reconfiguration for one or more prepared network devices, wherein the RRC reconfiguration comprises a fallback configuration to be used by a terminal device for performing cell switch; and means for transmitting, from the second network device to the terminal device, the RRC reconfiguration.

30. An apparatus comprising: means for receiving, at a terminal device from a second network device, a radio resource control (RRC) reconfiguration for one or more prepared network devices prepared by a first network device, wherein the RRC reconfiguration is determined by the first network device and comprises a fallback configuration; means for receiving, from the second network device, a cell switch command; andmeans for performing, based on the fallback configuration, a cell switch.

31. A non-transitory computer readable medium comprising program instructions for causing an apparatus to perform at least the method according to any of claims 25 to

Citation Information

Cited By

  • Lower-layer triggered mobility in mobile communication systems

    WO2026166678A1

  • Link failure recovery with unprepared handover

    WO2026166690A1