Method and system for cell measurement and measurement reporting in fast mobility based on lower layer signaling

By performing cell measurement and reporting configuration within layer-1 or layer-2 of the cellular wireless access network, rapid service cell changes during UE movement are realized, and the delay and signaling overhead during cell handover during UE movement is solved. Problem, improving communication efficiency and speed.

CN119072956AActive Publication Date: 2024-12-03ZTE CORP
View PDF 3 Cites 0 Cited by

Patent Information

Application Number
CN202280095211.0
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2022-04-22
Publication Date
2024-12-03
Estimated Expiration
2042-04-22

AI Technical Summary

Technical Problem

In cellular wireless access network, during cell handover during UE mobile time, the prior art is difficult to achieve fast, low latency and efficient service cell changes, especially when switching between cells of different CU services, which often leads to user plane data flow Interrupts and large signaling overhead.

Method used

By realizing rapid service cell changes during UE movement within layer-1 or layer-2 of the wireless communication protocol stack, using cell measurement and measurement report configuration, using L1/L2 signaling and message delivery, triggering the fast service cell change process , reduce dependence on L3 signaling, optimize signaling overhead and delay.

Benefits of technology

Fast and inter-cell mobility during UE movement is achieved, user plane data flow interruption and signaling overhead are reduced, communication efficiency and speed are improved, especially during inter-cell handover in the DU or CU.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119072956A_ABST
    Figure CN119072956A_ABST
Patent Text Reader

Abstract

The present disclosure relates to measurement reporting of UE measurements and serving cells, and configuration for cell measurements and reporting to enable fast serving cell changes during UE mobility within a lower network layer, such as layer-1 or layer-2 of a wireless communication protocol stack. The disclosure further relates to signaling procedures associated with fast serving cell changes for the UE triggered by the network based on cell measurements and reports, as well as various lower layer configurations and operations for enabling actual fast serving cell changes at and for the UE.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present disclosure relates generally to mobility of wireless terminal devices, and more particularly to a fast serving cell change procedure triggered by layer-1 or layer-2 signaling. Background Art

[0002] In a cellular radio access network, each cell may be associated with a coverage area. The coverage areas of multiple cells together provide wireless services for user equipment (UE). As the UE moves, the cell to which it can connect may change, and therefore the active wireless data connection of the UE may change or switch from one cell to another. Such a cell change or switch may involve complex signaling and operations at various layers of the wireless communication network protocol stack of the UE and the network. For the signaling and operations of the cell change, it is generally preferred to minimize the communication overhead and maximize the communication efficiency and speed. Summary of the invention

[0003] The present disclosure generally relates to UE mobility in a wireless access network, and in particular to UE measurements and measurement reports of serving cells, and configuration of cell measurements and reports to enable fast serving cell changes during UE mobility within lower network layers (such as layer-1 or layer-2 of a wireless communication protocol stack). The present disclosure further relates to signaling procedures associated with fast serving cell changes for UEs triggered by the network based on cell measurements and reports, and various lower layer configurations and operations for implementing the actual fast serving cell changes at and for the UE.

[0004] In some implementations, a method performed by a wireless device for preparing a serving cell change procedure is disclosed. The method may include receiving a cell measurement and measurement reporting configuration from a wireless communication node; performing cell measurement based on the cell measurement and measurement reporting configuration to generate a cell measurement report associated with the cell measurement; and sending the cell measurement report in a cell measurement reporting message according to the cell measurement and measurement reporting configuration, the cell measurement reporting message including a layer-1 or layer-2 control message.

[0005] In the above implementation, layer-1 includes a physical (PHY) layer, and layer-2 includes at least one of the following: a medium access control (MAC) layer, a radio link control (RLC) layer, or a packet data convergence protocol (PDCP) layer.

[0006] In any of the above implementations, sending the cell measurement report may include: reporting the cell measurement via a layer-1 uplink control information (UCI) message or a layer-2 MAC control element (MAC CE) message.

[0007] In any of the above implementations, the cell measurement report may include: measurement results of a source serving cell of the wireless device and at least one or more neighboring cells of the source serving cell.

[0008] In any of the above implementations, the method may further include: identifying one or more suitable neighbor serving cells from a set of candidate neighbor serving cells for a source serving cell of the wireless device based on performing cell measurement, wherein the cell measurement report includes physical cell information of the one or more suitable neighbor serving cells.

[0009] In any of the above implementations, the cell measurement report may further include beam information for one or more suitable neighboring cells, and the beam information is provided to indicate one or more recommended beams among the one or more suitable neighboring cells for the serving cell change process.

[0010] In any of the above implementations, the cell measurement and measurement reporting configuration may indicate to the wireless device a triggering event condition for sending a cell measurement report.

[0011] In any of the above implementations, the trigger event conditions for sending a cell measurement report may include at least one trigger event condition from the following set of trigger event conditions: a first result of the cell measurement indicates that a source service cell of the wireless device is continuously at or below a first threshold measurement level during a first preconfigured measurement time period; a second result of the cell measurement indicates that at least one neighboring cell of the source service cell of the wireless device is continuously at or above a second threshold measurement level during a second preconfigured measurement time period; or a difference measurement result between the first result and the second result is continuously at or above a cell measurement gap threshold level.

[0012] In any of the above implementations, the first threshold measurement level may include: a sum of a first preconfigured baseline threshold level and a first configurable tolerance threshold level offset.

[0013] In any of the above implementations, the second threshold measurement level may include: a sum of a second preconfigured baseline threshold level and a second configurable tolerance threshold level offset.

[0014] In any of the above implementations, the cell measurement gap threshold level may include: a sum of a preconfigured baseline gap threshold level and a configurable tolerance gap threshold level offset.

[0015] In any of the above implementations, the first preconfigured measurement time period may include: N consecutive measurement opportunities on a source serving cell for the wireless device, where N is a preconfigured positive integer.

[0016] In any of the above implementations, the second preconfigured measurement time period may include: M consecutive measurement opportunities performed on at least one neighboring cell of a source serving cell for the wireless device, where M is a preconfigured positive integer.

[0017] In any of the above implementations, the first result or the second result may include at least one of the following: reference signal received power (RSRP), signal to interference and noise ratio (SINR), or reference signal received quality (RSRQ).

[0018] In any of the above implementations, each of the first result and the second result may include a cell-level measurement result or a beam-level measurement result associated with a source serving cell of the wireless device and at least one neighboring cell of the source serving cell, respectively.

[0019] In any of the above implementations, the cell-level measurement result of the serving cell may be obtained from measurements of multiple beams associated with the serving cell.

[0020] In any of the above implementations, the beam-level measurement results may include measurement results associated with: a predetermined number of best beams with a source serving cell of the wireless device or at least one suitable neighboring cell of the source serving cell.

[0021] In any of the above implementations, the first result may include a measurement result of a first merged N consecutive cell measurements performed by the wireless device on the source service cell, where N is a preconfigured positive integer. The second measurement result includes a measurement result of a second merged N consecutive cell measurements performed on at least one neighboring cell of the source service cell. The trigger event condition for sending a cell measurement report includes: sending a cell measurement report when the difference between the measurement result of the first merged N consecutive cell measurements and the measurement result of the second merged N consecutive cell measurements is at or exceeds the cell measurement gap threshold level.

[0022] In any of the above implementations, sending a cell measurement report in a cell measurement report message may include, when at least one trigger event condition in a set of trigger event conditions is met: sending a MAC CE message containing a cell measurement report to a wireless communication node; or triggering a wireless device to send a cell measurement report message as layer-1 uplink control information (UCI) to a wireless communication node.

[0023] In any of the above implementations, the applicable trigger event conditions in the set of trigger event conditions may be configured for each serving cell or for a candidate serving cell list.

[0024] In any of the above implementations, a first neighboring cell and a second neighboring cell in at least one neighboring cell of the source serving cell may be independently configured with different triggering event conditions in a set of triggering event conditions.

[0025] In any of the above implementations, a set of trigger event conditions may further include the wireless device detecting a beam failure in a source service cell, and less than P suitable beams of the source service cell can be identified; or the wireless device detecting a radio link failure with respect to the source service cell.

[0026] In some other implementations, a wireless device including a processor and a memory is disclosed. The processor may be configured to read computer code from the memory to implement any of the above methods.

[0027] In some other implementations, a computer program product is disclosed, including a non-transitory computer-readable program medium having computer code stored thereon. When the computer code is executed by a processor, the processor may implement any of the above methods.

[0028] Other aspects and alternatives of the above-described embodiments and their implementations will be described in more detail in the following figures, description and claims. BRIEF DESCRIPTION OF THE DRAWINGS

[0029] Figure 1 An example wireless communication network including a radio access network, a core network, and a data network is illustrated.

[0030] Figure 2 An example radio access network including a plurality of mobile stations or UEs and radio access network nodes communicating with each other via an over-the-air radio communications interface is illustrated.

[0031] Figure 3 An example communication protocol stack in a wireless access network node or a wireless terminal device including various network layers is shown.

[0032] Figure 4 A split architecture for splitting a radio access network node into a central unit (CU) and one or more distributed units (DUs) is described.

[0033] Figure 5 An example signaling and operational flow diagram for the preparation phase of a lower layer fast serving cell change is shown.

[0034] Figure 6 An example signaling and operational flow diagram for the execution phase of a lower layer fast serving cell change is shown. DETAILED DESCRIPTION

[0035] The techniques and examples of implementations and / or embodiments described in the present disclosure may be used to facilitate air radio resource allocation, configuration, and signaling in a wireless access network. The term "example" is used to mean "an example" and does not mean an ideal or preferred example, implementation, or embodiment unless otherwise specified. The section titles used in the present disclosure are intended to facilitate understanding of the disclosed implementations and are not intended to limit the techniques disclosed in each section to the corresponding section. The disclosed implementations may be further embodied in a variety of different forms, and therefore, the scope of the present disclosure or claimed subject matter is intended to be interpreted as not being limited to any embodiment described below. Various implementations may be embodied as methods, devices, components, systems, or non-transitory computer-readable media. Thus, for example, the embodiments of the present disclosure may take the form of hardware, software, firmware, or any combination thereof.

[0036] The present disclosure is directed to UE measurements and measurement reporting of serving cells, and configurations for cell measurements and reporting to enable fast serving cell changes during UE mobility within lower network layers (e.g., layer-1 or layer-2 of a wireless communication protocol stack). The present disclosure is further directed to signaling procedures associated with fast serving cell changes of UEs triggered by the network based on cell measurements and reporting, and various lower layer configurations and operations for implementing the actual fast serving cell changes at and for the UE. Wireless Network Overview

[0037] like Figure 1 The example wireless communication network 100 shown in FIG. 1 may include user equipment (UE) 110, 111, and 112, an operator network 102, various service applications 140, and other data networks 150. For example, the operator network 102 may include access networks 120 and 121 and a core network 130. The operator network 110 may be configured to transmit voice, data, and other information (collectively referred to as data traffic) between the UEs 110, 111, and 112, between the UEs and the service applications 140, or between the UEs and other data networks 150. The access networks 120 and 121 may be configured as various wireless access network nodes (WANNs, alternatively referred to as base stations) to interact with the UEs on one side of a communication session and with the core network 130 on the other side. The core network 130 may include various network nodes configured to control the communication session and perform network access management and traffic routing. The service applications 140 may be hosted by various application servers deployed outside the core network 130 but connected to the core network 130. Likewise, other data networks 150 may also be connected to the core network 130 .

[0038] exist Figure 1In the wireless communication network of 100, UEs can communicate with each other via a wireless access network. For example, UEs 110 and 112 can be connected to the same access network 120 and communicate via the same access network 120. UEs can communicate with each other via both the access network and the core network. For example, UE 110 can be connected to the access network 120, and UE 111 can be connected to the access network 121, so UE 110 and UE 111 can communicate with each other via the access networks 120 and 121 and the core network 130. The UE can further communicate with the service application 140 and the data network 150 via the core network 130. In addition, as shown in 113, the UEs can communicate directly with each other via sidelink communications.

[0039] Figure 2 Further shown is an example system diagram of a wireless access network 120, which includes a WANN 202 that provides services to UEs 110 and 112 via an air interface 204. The wireless transmission resources of the air interface 204 include a combination of frequency, time and / or space resources. Each of the UEs 110 and 112 can be a mobile or fixed terminal device that is equipped with a mobile access unit (such as a SIM / USIM module) for accessing the wireless communication network 100. Both UEs 110 and 112 can be implemented as terminal devices, including but not limited to mobile phones, smart phones, tablet computers, laptops, vehicle-mounted communication devices, roadside communication devices, sensor devices, smart appliances (such as televisions, refrigerators and ovens), or other devices that can communicate wirelessly over a network. As shown in FIG. Figure 2 As shown, each UE (such as UE 112) may include a transceiver circuit 206 coupled to one or more antennas 208 to enable wireless communication with WANN 120 or another UE (such as UE 110). Transceiver circuit 206 may also be coupled to processor 210, which may also be coupled to memory 212 or other storage device. Memory 212 may be transient or non-transient and may store computer instructions or codes therein, which, when read and executed by processor 210, cause processor 210 to implement various methods described herein.

[0040] Similarly, WANN 120 may include a base station or other wireless network access point capable of wirelessly communicating with one or more UEs via air interface 204, as well as communicating with core network 130. For example, but not limitation, WANN 120 may be implemented in the form of a 2G base station, a 3G nodeB, an LTE eNB, a 4G LTE base station, a 5G NR base station, a 5G central unit base station, or a 5G distributed unit base station. Each type of these WANNs may be configured to perform a corresponding set of wireless network functions. WANN 202 may include a transceiver circuit 214 coupled to one or more antennas 216, which may include various forms of antenna towers 218 to enable wireless communications with UEs 110 and 112. Transceiver circuit 214 may be coupled to one or more processors 220, which may be further coupled to a memory 222 or other storage device. The memory 222 may be transient or non-transitory and may store therein instructions or codes that, when read and executed by the one or more processors 220 , cause the one or more processors 220 to implement various functions of the WANN 120 described herein.

[0041] Such as Figure 2 Data packets in the wireless access network of the example may be sent as protocol data units (PDUs). The data contained therein may be encapsulated as PDUs at various network layers wrapped with nested and / or layered protocol headers. Once a connection (e.g., a radio link control (RRC) connection) is established between the transmitting end and the receiving end, the PDUs may be communicated between a transmitting device or transmitting end (these two terms are used interchangeably) and a receiving device or receiving end (these two terms are also used interchangeably). Any transmitting device or receiving device may be a wireless terminal device, such as Figure 2 The devices 110 and 120 in the embodiment may be wireless access network nodes, such as Figure 2 Node 202 in. For bidirectional communication, each device can be a sending device and a receiving device.

[0042] like Figure 3 As shown, for example, WANN 120 may further include a plurality of separate access network nodes in the form of a central unit (CU) 302 and at least one distributed unit (DU) 304 and 306. CU 122 may be connected to DU1 304 and DU2 306 via various F1 interfaces. For example, the F1 interface may further include an F1-C interface and an F1-U interface, which may be used to transmit control plane data and user plane data, respectively. The UE may be connected to the core network 130 via the WANN 120 through a wireless interface.

[0043] Each DU can provide services to UEs via one or more cells. Each cell is associated with a coverage area. These cells may alternatively be referred to as serving cells. The coverage areas between cells may partially overlap. Each UE can actively communicate with at least one cell and can potentially connect or be connected to more than one cell at the same time. Figure 3 In the example of , UE1, UE2, and UE3 may be served by cell 1 320 of DU1, while UE4 and UE5 may be served by cell 2 330 of DU1. In some implementations, the UE may be served by two or more cells simultaneously. Each UE may be mobile, and the signal strength and quality from each cell at the UE may depend on the UE location. In some implementations, the CU may be a gNB central unit (gNB-CU) and the DU may be a gNB distributed unit (gNB-DU). Although the various implementations described below are provided in the context of a 5G cellular wireless network, the basic principles described herein are applicable to other types of radio access networks, including but not limited to other generations of cellular networks as well as Wi-Fi, Bluetooth, ZigBee, and WiMax networks.

[0044] In some example implementations, Figure 3 The cells shown in the figure may be referred to as service cells alternatively. The service cells may be grouped into service cell groups (CGs). The service cell group may be a main CG (MCG) or a secondary CG (SCG). In each type of cell group, there may be one main cell and one or more secondary cells. For example, the main cell in the MCG may be referred to as a PCell, and the main cell in the SCG may be referred to as a PScell. The secondary cells in the MCG or SCG may be referred to as SCells. The main cells including the PCell and the PScell ​​may be collectively referred to as SpCells. All these cells may be referred to as service cells or multiple cells. Unless otherwise specifically distinguished, "cell" and "service cell" may be used interchangeably. The term "service cell" may refer to a cell that is serving, will serve, or may serve a UE. In other words, a "service cell" may not currently be providing service to the UE. Although the various embodiments described below may sometimes refer to one of the above types of service cells, the basic principles apply to all types of service cells in these two types of service cell groups.

[0045] Figure 4 Further explained in Figure 1-Figure 3 404. A simplified view of the various network layers involved in sending a user plane PDU from a sending device 402 to a receiving device 404 in an example wireless access network of FIG. Figure 4 It is not intended to encompass all basic device components or network layers used to handle the transmission of PDUs. Figure 4It is illustrated that data encapsulated by the upper network layer 420 at the transmitting device 402 may be sent to the corresponding upper layer 430 (such as a radio resource control or RRC layer) at the access device 304 via: the packet data convergence protocol layer (PDCP layer, Figure 4 The network entities in each of these layers may be configured to handle the transmission and retransmission of the PDU.

[0046] exist Figure 4 In the embodiment, the upper layer 420 may be referred to as layer-3 or L3, while the intermediate layers such as the RLC layer and / or the MAC layer and / or the PDCP layer ( Figure 4 The layers of the physical layer and the radio interface (not shown) may be collectively referred to as layer-2 or L2, and the term layer-1 is used to refer to layers such as the physical layer and the radio interface associated layers. In some cases, the term "lower layer" may be used to refer to the set of L1 and L2, and the term "high layer" may be used to refer to layer-3. The term "lower layer" may be used to refer to the layers of L1, L2, and L3 that are lower than the current reference layer. Control signaling may be initiated and triggered within each layer from L1 to L3 and within each network layer therein. These signaling messages may be encapsulated and cascaded into lower layer packets and sent via the allocated control or data air radio resources and interfaces. The term "layer" generally includes various corresponding entities. For example, the MAC layer includes corresponding MAC entities that may be created. For example, layer-1 includes a PHY entity. For another example, layer-2 includes a MAC layer / entity, an RLC layer / entity, and / or a PDCP layer / entity.

[0047] Back to Figure 3 , various functions of the radio access network node can be split between the CU and the DU. For example, the DU can host the lower layers including the L2 and L1 layers, such as the RLC, MAC, and PHY (physical) layers, while the CU can host the higher layers of the network, such as the L3. General UE mobility and serving cell change

[0048] As the UE moves between the coverage areas of various cells, the signal level and quality from the cells change. The UE may be configured to measure and monitor the cell signal level and quality. The parameters associated with performing these measurements may be configured by the network. In some cases, the signal difference between the cells may require a change in the serving cell from the source serving cell (alternatively referred to as the original serving cell) to the target serving cell (alternatively referred to as serving cell switching, PCell and SCell role change or serving cell switching) to actively provide services to the UE. The source serving cell and the target (serving) cell may be served by the same DU, or may be served by different DUs associated with the same CU, or may be served by different CUs. Therefore, the serving cell change may be intra-DU (when changing the cell in one or more cells served by the same DU), or may be inter-DU (when changing from a source cell served by one DU to a target cell served by another DU). Inter-DU serving cell changes may be intra-CU (when changing from a source cell to a target cell served by the same CU) or inter-CU (when changing from a source cell served by one CU to a target cell served by another CU). These cell changes represent different levels of cell changes and may involve various levels of serving cell change configuration, reset and handover procedures.

[0049] In some implementations, regardless of whether the source serving cell and the target serving cell are inter-CU or intra-CU, a serving cell switch may be triggered as a result of L3 measurements and may be implemented by radio resource control (RRC) signaling with synchronization. For example, RRC signaling may be used to implement a change of SpCell (from one SpCell to another SpCell) (the SpCell may be a PCell or a PSCell), and to release / add SCells when applicable. Such a SpCell change procedure initiated via RRC reconfiguration typically results in a long interruption in user plane data communications / flows, noticeable delays in updating user plane data transmissions, and is typically associated with considerable RRC signaling overhead.

[0050] This high-latency RRC reconfiguration-based serving cell change procedure from one serving cell to another may sometimes be difficult to avoid, especially when the change involves a source serving cell and a target serving cell served by different CUs (inter-CU serving cell change). However, in most cases, the handover may occur from one cell to another cell served by the same DU (intra-DU serving cell change), or between cells served by different DUs of the same CU (inter-DU, but intra-CU). In these cases, the UE serving cell change may not require involving any change of the serving CU hosting the L3 entity. In this case, the UE mobility only needs to involve the non-L3 lower layers in the communication protocol stack residing in the DU, including, for example, the L1 and / or L2 layers, such as the RLC / MAC / PHY layers, as Figure 3 In this case, there is no need to require the UE to perform a serving cell change procedure based on L3 signaling.

[0051] The service cell change process implemented by only L1 and / or L2 signaling is fast / flexible, has minimal impact / interference on user plane data flow, and helps reduce switching delays and signaling overhead. This L1 / L2-based service cell change can be referred to as a fast service cell change, and the change process can be correspondingly referred to as a fast cell change process, or a fast service cell change process. A hyphen ("-") can be added between the words in these terms without modifying their meaning. In a cellular network where DU switching occurs frequently during UE mobility, for example, when the carrier frequency of the air radio band can only provide a short communication distance and requires dense cells, the cumulative reduction in communication delay and signaling overhead will be very significant.

[0052] The disclosure herein provides various example implementations of mobility measurement / reporting and its configuration and signaling, serving cell change signaling, cell change procedure, and data communication update as a result of cell change in the context of fast cell change relying on low-level signaling and operation. Such a procedure can provide fast, efficient and low-latency cell change with minimal user plane data flow interruption and based on L1 / L2 UE mobility. General L1 / L2-based fast inter-cell mobility

[0053] In general, UE mobility can be achieved by monitoring the signal levels from various cells during UE movement, reporting cell measurement results to the network, performing a service cell change process when specific cell switching conditions are met, and performing various processes to update the current communication session. Each unit of the access network, including the UE and the WANN (or base station, referred to as NW in this article, representing the network side), jointly participates in completing the entire mobile process. For example, the base station may be responsible for providing various configurations related to UE mobility, while the UE may be responsible for various cell measurements and reports. The base station, rather than the UE, may ultimately determine whether to perform a service cell change and whether to trigger a cell handover, thereby balancing the UE load served by the source service cell and the target service cell. For example, the target service cell may be determined and signaled by the NW based on a cell measurement report from the UE. In some implementations of L1 / L2-centric fast mobility, similar to traditional L3-based mobility, the actions on the UE side during the mobility process can be divided into two stages: ● Preparation phase: includes L1 and / or L3 measurements of each cell, and reporting the measurement results from the UE to the NW. ●Execution phase: includes the behavior of UE / NW at each network layer when receiving L1 / L2 signaling for mobility, including PHY layer (L1), MAC layer, RLC layer, PDCP (L2) and RRC (L3) layer, as well as the evaluation of the service cell change results and the execution of corresponding UE / NW operations after the service cell change. Preparing for L1 / L2-based Fast Mobility - Overview

[0054] Figure 5 The example UE and NW (e.g., base station) interactions during the preparation phase associated with the fast serving cell change process are illustrated in the flowchart of FIG. In such an example preparation phase, the general process may include, but is not limited to: ●Step 1: NW configures cell measurement configuration and cell measurement reporting configuration for UE. ●Step 2: The UE performs cell measurement according to the received cell measurement configuration, and determines whether to trigger a measurement result report to the NW based on the cell measurement reporting configuration, such as a pre-configured reporting condition (e.g., a time trigger condition, such as periodic, semi-continuous periodic reporting, or an event trigger condition, as described in further detail below). ● Step 3: If the cell measurement reporting condition is met, the UE reports the cell measurement results related to the source cell and one or more candidate cells adjacent to the source cell to the NW. Preparation phase for fast L1 / L2 based mobility - cell measurement configuration and cell measurement

[0055] The cell measurements may be of different types, including but not limited to L3 measurements and / or L1 measurements. The measurement objects within the serving cell may include those features that can be used to determine the signal quality and channel state of the cell, including but not limited to synchronization system blocks (SSBs), channel state information reference signals (CSI-RSs), etc. The reporting timing modes include periodic, aperiodic, semi-continuous periodic, or moments triggered by predefined or configured events. For example, the communication resources used to send cell measurement reports may include physical uplink control channel (PUCCH) resources and / or physical uplink shared channel (PUSCH) resources (in the time domain and frequency domain).

[0056] For example, measurements may be performed in the L1 layer on SSB and / or CSI-RS. L1 measurements may include: • L1 measurements on the source cell currently providing active service to the UE. • L1 measurements on one or more neighboring cells of the source cell.

[0057] In some implementations, the cell measurement configuration and the cell measurement reporting configuration may be signaled separately from the NW. In some other implementations, these configurations may be signaled to the UE as an integral signaling message. These configurations or configurations may specify the measurements to be performed, the content to be reported, the format of the report, the reporting timing, the reporting triggering conditions, the report transmission resource allocation, etc.

[0058] For example, the cell measurement configuration and the cell measurement reporting configuration may indicate the following items used for various CSI measurements: ●CSI-MeasConfig, specifies a set of CSI measurement and reporting configurations for the following CSI ■ CSI-ResourceConfig (e.g., periodic, aperiodic, semi-persistent periodic reporting configuration). ■ NZP-CSI-RS-ResourceSet (ie, a set of non-zero power CIS-RS resources measured in, for example, a periodic, aperiodic, or semi-persistent periodic manner). ■ CSI-RS-SSB-ResourceSet (ie, a CSI-RS-SSB resource set measured in, for example, a periodic, aperiodic, or semi-persistent periodic manner). ■CSI-ReportConfig (i.e., report trigger configuration, used to report cell measurements in a periodic, aperiodic, or semi-continuous periodic manner in time, or report when triggered by an event).

[0059] The above example cell measurement and cell measurement reporting configurations may be cell specific. For example, different cell measurements and cell measurement reporting configurations may be provided for source cells and neighboring cells. The neighboring cells to be measured may be configured as a candidate neighboring cell list for the source cell for cell changes. The candidate cell list may be predetermined due to the cell configuration in the area, or may be signaled from the network. Using the above example implementation, both / either NZP-CSI-RS-ResourceSet and / or CSI-RS-SSB-ResourceSet may be associated with a cell indicated by PhysicalCellID or additionalPCIIndex. Preparation phase for fast L1 / L2 based mobility - cell measurement report

[0060] In some implementations, the signaling and messaging of the cell measurement report may be performed in the L1 and / or L2 layers instead of the L3 layer. The above one or more layers may be predefined, preconfigured, or may be dynamically configured by the NW, from which the cell measurement report is sent. In some example implementations, the signaling / transmission of the cell measurement report may be specified as part of the above cell measurement reporting configuration. For example, the cell measurement report may be signaled / sent via: L1 signaling and messaging (e.g., via uplink signaling, such as uplink control information (UCI), which may be transmitted over PUCCH or PUSCH); and / or - L2 signaling and messaging (eg, via MAC CE for reporting cell measurements for serving cell change procedure).

[0061] For the above L1 or L2 signaling / messaging, the measurement results that can be included in the cell measurement report can also be predefined or preconfigured, for example, configured as specified in the above cell measurement reporting configuration. The following can be signaled as optional or alternative content that can be included in the cell measurement report: 1. Direct measurement results of the source serving cell and one or more neighboring cells of the source serving cell, for example, may include at least one of the following information: ① Direct measurement results of one or more neighboring cells that are potential target cells for cell change; ② Direct measurement results of the source serving cell; or 2. Identification and related information of one or more neighboring cells of the current source serving cell suitable for handover, for example including: ① Physical cell information (PCI), indicating one or more neighboring physical cells determined by the UE to be suitable as target cells for serving cell change; ② Optionally, additional beam information for the indicated physical cell to indicate a beam of a suitable adjacent physical cell suitable as a serving beam for the serving cell change.

[0062] The first alternative described above may be particularly suitable for L1 signaling / messaging of L1 cell measurement reports, since the L1 measurements are directly included in the L1 measurement report message without involving other higher layers. By reporting direct measurement results via L1 or L2 signaling / messaging, the NW makes a decision for determining and identifying a target serving cell for a serving cell change based on the direct measurement results as reported in the cell measurement report and other factors known to the NW. The direct measurement results of the source cell or one or more neighboring cells may include overall measurement results of neighboring cells and individual beams within each neighboring cell.

[0063] Regarding the second alternative, the UE may select a suitable neighboring cell for fast serving cell change based on direct cell measurements performed by layer-1 in the UE. For example, the selection may be made among a set of candidate cells, which are predetermined, preconfigured, or signaled from the NW as described above. One or more such suitable neighboring cells may be selected and reported. Upon receiving the selection, the NW may further determine a target serving cell for fast serving cell change.

[0064] Further with respect to the second alternative described above, the cell measurement report may include physical cell information of any suitable neighboring cells and beam information of any suitable beams. Such information may include, but is not limited to: ● Physical cell information of suitable neighboring cells, for example, including at least one of the following: oPhysical cell identity; o The position or index of the suitable cell in the candidate cell list (for example, 0 represents the first cell information in the candidate cell information list, and 1 represents the second cell information in the candidate cell information list, etc.); ●Indicated beam information of a suitable physical cell, for example, including at least one of the following: o CSI-RS ID and / or SSB identifier associated with the beam; o The beam position or index associated with the candidate beam list for the physical cell (ie, 0 represents the first beam in the candidate beam list, and 1 represents the second beam in the candidate beam list, etc.).

[0065] In some implementations for L1 signaling / messaging, such physical cell and beam information may be reported by code points. In some other implementations, the physical cell information and beam information may be indicated by one or more bitmaps for L1 or L2 signaling / messaging. For example, a physical cell bitmap may be included in a cell measurement report to indicate one or more suitable neighboring cells in a set of candidate cells for serving cell changes. In addition, in a suitable physical cell, a beam bitmap may be included in the cell measurement report to indicate one or more beams of a physical cell that the UE considers suitable for serving cell changes. In addition to code points or bitmaps, other methods may be implemented for cell measurement reports to indicate the above-mentioned physical cell information and beam information.

[0066] In some other example implementations, the cell measurement report may include a combination of the above two alternatives. Specifically, via L1 or L2 signaling / message delivery, the cell measurement report may include direct measurement results of one or more suitable neighboring cells or beams selected by the UE from the candidate cells or beams for serving cell change. Preparation phase for fast L1 / L2 based mobility - Cell measurement reporting based on triggering event conditions

[0067] In some implementations, the cell measurement results may be reported to the NW according to a predefined or preconfigured timing, for example, the cell measurement results may be reported periodically in a preconfigured time slot.

[0068] In some other example implementations, the cell measurement report may be sent according to one or more triggering events. Whether to send the cell measurement report according to time or triggering events may be pre-configured, for example, indicated in the above cell measurement reporting configuration.

[0069] Regarding event-based cell measurement reporting, for example, the cell measurement reporting may be triggered at L1 or L2 by satisfying one or more of the following event conditions: 1: The measurement result of the source serving cell meets the following conditions (called the source cell judgment rule (BSC)): The measurement result of the source cell ≤ Threshold 1 + Offset 1 (1) and / or 2: The measurement result of at least one candidate neighboring target cell meets the following conditions (called the target cell arbitration principle (GTC)): The measurement result of the candidate target cell ≥ threshold 2 + offset 2 (2)

[0070] Meeting the above BSC conditions indicates that the source service cell may not be suitable for providing services to the UE and that the service cell may need to be changed. Meeting the above GTC conditions indicates that at least one neighboring service cell is suitable for switching as a potential target cell. The above "Threshold 1" represents a baseline cell signal quality threshold, which is used to determine whether the source service cell has become unsuitable for supporting a communication link, and "Offset 1" represents the tolerance level of Threshold 1. Similarly, the above "Threshold 2" represents a baseline cell signal quality threshold, which is used to determine whether a neighboring cell is suitable as a potential target service cell for a service cell change, and "Offset 2" represents the tolerance level of Threshold 2. Each of "Threshold 1", "Threshold 2", "Offset 1" and "Offset 2" may be predetermined, preconfigured or dynamically configured. In some example implementations, the baseline threshold may be predefined and the tolerance level may be configurable.

[0071] In some cases, especially when the UE is at the cell edge or border, the relative signal between the current source serving cell and one or more of the neighboring cells may fluctuate significantly. Therefore, using this mechanism to determine whether the current source serving cell is poor and whether at least one of the neighboring cells is excellent (based on the above mechanism) may result in frequent serving cell changes due to the ping-pong effect. The ping-pong effect may cause serious inefficiency and communication overhead. In order to avoid or reduce the ping-pong effect of L1 / L2 mobility, and taking into account the computational and signal processing capability limitations of the L1 / L2 layer, the UE may adopt the following enhanced mechanism for event-based triggering of sending cell measurement results to the NW: ●BSC condition: N consecutive measurement results of the source serving cell satisfy the condition of formula (1) above, and / or ●GTC condition: while or after the source serving cell is measured, M consecutive measurement results of at least one neighboring cell meet the condition of the above formula (2).

[0072] In another specific implementation manner of avoiding or reducing the ping-pong effect, the UE may adopt another enhanced mechanism for event-based triggering of sending cell measurement results to the NW: ●BSC condition: the average measurement result of N consecutive measurement results of the source serving cell satisfies the condition of the above formula (1), and / or ●GTC condition: the average measurement result of M consecutive measurement results of at least one neighboring cell satisfies the condition of the above formula (2).

[0073] In some example implementations, the measurement results of the source serving cell or the neighboring cell may be cell-level measurement results or beam-level measurement results. The cell-level measurement results may be obtained, for example, from the measurement results of one or more beams. The beam-level measurement results may include, for example, a predetermined or preconfigured number P of best beams for a specific cell. In the above implementations, M, N, and P may be predefined, preconfigured, or dynamically configured positive integers.

[0074] The N consecutive source cell measurement results and the M consecutive neighbor cell measurement results correspond to the source cell measurement time window and the neighbor cell measurement time window, respectively. The enhancement mechanism represents a filtering process, which can smooth the consecutive measurement results and more accurately represent the channel quality of each cell to avoid or reduce the ping-pong effect.

[0075] In some example implementations, the measurement results may include one or more of the following: reference signal received power (RSRP), signal to interference and noise ratio (SINR), reference signal received quality (RSRQ) level, etc., as a reflection of the channel state. When more than one result is used, the results may be aggregated or combined (e.g., averaged, weighted averaged, etc.), and accordingly, the baseline thresholds and offset values ​​in the above formulas (1) and (2) may also be aggregated or combined. Alternatively, each of the multiple measurement results of a cell may be associated with its own threshold and offset, thereby providing sub-conditions based on formulas (1) and (2). For example, each of these formulas may be considered to be satisfied when all or most of the sub-conditions are satisfied.

[0076] As an example of the above implementation, when it is detected that the number of consecutive measurements indicating that the source cell is a poor cell is equal to or greater than N, and / or when it is detected that the number of consecutive measurements indicating that at least one of the candidate neighboring cells is a good target cell is equal to or greater than M, the MAC layer may generate and / or send a MAC CE or notify the L1 layer to send an L1 message to report the cell measurement results to the NW. Therefore, the MAC layer can be configured to track the number of BSC and GTC measurements by using simple logic and counters, thereby eliminating the need for the MAC layer to have complex computing capabilities.

[0077] In some implementations of simple logic and counters, the MAC layer or entity may maintain one or two counters, referred to as counter A and counter B. When receiving an indication from a lower layer regarding a BSC, the MAC layer or entity may increment counter A by 1, and when receiving an indication from a lower layer regarding a GTC, the MAC layer or entity may increment counter B by 1. With this implementation, one or two timers may be maintained at the MAC layer, referred to as timer A and timer B, respectively. Timer A may be associated with counter A, and / or timer B may be associated with counter B. When counter A increments, timer A may be started or restarted, and when counter B increments, timer B may be started or restarted. When timer A expires, counter A may be reset to 0, and when timer B expires, counter B may be reset to 0. In addition, one or two maximum values ​​M and / or N may be preconfigured for counter A and counter B to trigger or send a cell measurement report. When counter A and / or counter B reaches the maximum value M and / or N, a cell measurement report may be triggered and / or sent.

[0078] As an example of the above implementation, when notified by the L1 layer to send a MAC CE, the MAC layer may generate and / or send a MAC CE, or when the L1 layer detects that an average value greater than or equal to N consecutive measurement results indicates a source cell judgment condition, and / or when the L1 layer detects that an average value greater than or equal to M consecutive measurement results indicates that at least one of the candidate neighboring cells is a preferred target cell, the L1 layer may send an L1 message to report the cell measurement result to the NW. Therefore, the MAC layer may be configured to track indications from lower layers about BSC and GTC information to generate and send a MAC CE for a cell measurement report. Therefore, when an indication of BSC and / or GTC information is received from a lower layer, the MAC layer may trigger and / or send a cell measurement report.

[0079] In some other implementations, the event triggering condition may be based on a combination of a source cell measurement result (referred to as a "first cell measurement result") and one or more neighboring cell measurement results (referred to as a "second cell measurement result"). For example, a differential result between the first cell measurement result and the second cell measurement result may be used as a basis for a triggering event for reporting the cell measurement result. Specifically, the example triggering event condition may be expressed as: Neighboring cell result - source cell result ≥ threshold 3 + offset 3, (3) Among them, the definition or configuration of "Threshold 3" and "Offset 3" may be similar to those of the above-mentioned "Threshold 1", "Threshold 2", "Offset 1" and "Offset 2".

[0080] In order to avoid or reduce the ping-pong effect of L1 / L2 mobility and taking into account the limited L1 / L2 computing power, the above differential measurement can be performed continuously within the measurement window, and when X consecutive different measurements meet the conditions in the above formula (3), the cell measurement report can be triggered. In the specific details of the present implementation, a counter (referred to as counter C) and a timer (referred to as timer C) can be introduced in the L2 layer. For example, counter C can be associated with timer C, and when the MAC layer receives an indication from the lower layer that formula (3) is satisfied, counter C can be incremented by 1. As long as counter C is incrementing, timer C can be started or restarted. When timer C expires, counter C can be reset to 0. In addition, a maximum value X can be pre-configured, and when counter C reaches the maximum value X, the L2 layer can generate and / or send a cell measurement report, and / or the L2 layer can instruct the lower layer to generate and / or send a cell measurement report when counter C reaches the maximum value X.

[0081] In another implementation, in order to avoid or reduce the ping-pong effect of L1 / L2 mobility and taking into account the limited L1 / L2 computing power, the measurement result of the neighboring cell may be the average value of Y consecutive measurements of the neighboring cell, and the measurement result of the source cell may be the average value of Y consecutive measurements of the source serving cell. In the details of this implementation, the L2 layer may trigger and / or generate a cell measurement report upon receiving an indication from a lower layer satisfying formula (3), and / or the L1 layer may trigger and / or generate a cell measurement report when the difference satisfies formula (3).

[0082] Similarly, the measurement result reflected in the above formula (3) may be a cell-level differential measurement result, or may be a beam-level differential measurement result. The cell-level differential measurement result may be obtained from the differential measurement results of one or more beams. For example, the beam-level measurement result may include a predetermined or preconfigured number P of best beams for a particular cell. The differential measurement result may be a differential RSRP, SINR, RSRQ, and / or other differential characteristics reflecting the channel state of the measured cell.

[0083] In various implementations of the above event-triggered cell measurement report, the triggering event related to the neighboring cell may be configured for each candidate neighboring cell, for each candidate neighboring cell list, or for each cell group.

[0084] The triggering events for different candidate cells, different candidate cell lists or different candidate cell groups may be configured differently. For example, each candidate cell, each candidate cell list or each candidate cell group may be independently configured with its respective triggering event. For example, one neighboring candidate cell may be associated with a triggering event based on formulas (1) and (2) under filtering, while another neighboring candidate cell may be associated with a triggering event based on formula (3) under filtering, or vice versa. Then, any neighboring cell that satisfies its respective triggering event will cause a cell measurement report to be sent.

[0085] In some other implementations, one or more of the following events may also trigger a cell measurement report: ● A BF (beam failure) on the source serving cell is detected, and fewer than P suitable beams of the source serving cell can be identified, where P is a predetermined, configured positive integer; and / or • Radio link failure is detected for the source serving cell.

[0086] Meeting these conditions indicates that the source serving cell can no longer support communications and a cell handover needs to occur, and the triggered cell measurement report will be used to urge the NW to provide and designate a target serving cell for serving cell change, regardless of the quality of the target cell. Execution Phase - Overview

[0087] In some implementations, once the cell measurement results are reported, the NW may determine whether a fast serving cell change should be performed for the reporting UE based on the reported cell measurement results. If it is decided to proceed with the fast serving cell change, the NW may determine the target serving cell and begin the execution phase of the fast serving cell change.

[0088] Figure 6 Example steps of the execution phase of a fast serving cell change are described. Figure 6 As shown, these steps may include:

[0089] Step 1: The source cell sends an L1 and / or L2 signaling message to the UE to trigger the fast serving cell change procedure.

[0090] Step 2: The UE performs a set of fast serving cell change operations.

[0091] Step 3: The UE notifies the target serving cell of the fast serving cell change.

[0092] Step 4: The target serving cell confirms the UE notification.

[0093] Step 5: If the fast serving cell change fails according to the response or no response from the target serving cell in step 4, the UE performs further operations. L1 / L2 signaling to trigger fast serving cell change

[0094] The source serving cell may trigger a fast serving cell change based on L1 / L2 signaling / message delivery. For example, the trigger may be based entirely on L1 signaling / message delivery, such as via a downlink control information (DCI) message. In this example implementation, the L1 trigger DCI message may include at least one of a set of information items, the set of information items including, but not limited to: ●Target service cell information: ○ Physical Cell ID (PCI): Indicates the target serving cell to which the UE should transfer; ○ Serving cell ID: indicates the target serving cell to which the UE should transfer; or ○ Candidate cell ID: Indicates the target serving cell to which the UE should transfer. ●Beam information: For example, used to indicate which transmission configuration indicator (TCI) state can be activated for uplink and / or downlink after the UE transfers to the target serving cell. In some implementations, the beam indication can be based on the CSI-RS ID and / or SSBID. In some implementations, the beam indication can be indicated via the TCI state ID. In some implementations, the transmit receive point (TRP) indication can be indicated via the position of the TRP in the TRP list. ● Timing Advance (TA) information: indicates the TA value of the indicated target serving cell. ● Preamble index: The preamble index indicating the UE to perform RACH on the indicated target serving cell. ● RO Index: The RACH opportunity (RO) index indicating that the UE performs RACH on the indicated target serving cell. ●Cell Radio Network Temporary Identifier (C-RNTI): Indicates the new C-RNTI when the UE transfers to the target serving cell. ● Key: used by UE to authenticate L1 signaling from NW (source serving cell). It may also be included in the RRC configuration of the indicated target serving cell indicated by the physical cell information.

[0095] In some other example implementations, the source serving cell triggering the fast serving cell change process may be completely based on L2 signaling / message delivery, such as via one or more MAC CEs. In such example implementations, the L2 triggering MAC CE may include at least one information item in a set of information items similar to the information items listed above for LI triggering DCI.

[0096] In some other example implementations, L1 DCI and L2 MAC CE may be used together to trigger a fast serving cell change process. For example, one or more MAC CEs may be used to activate one or more candidate cells in a candidate cell list to achieve a fast serving cell change. Such a MAC CE may be sent to one or more candidate cells for activation. The MACCE may be further sent to the UE as part of the trigger to indicate to the UE which of the candidate serving cells are activated for fast serving cell change. In addition, one or more DCIs may be used to actually trigger a fast serving cell change to a specific target serving cell among those candidate serving cells activated by one or more MAC CEs. In one implementation, the MAC CE used to activate the candidate serving cell for fast serving cell change may include at least one of the following information: ●Target serving cell information, which may be indicated by a physical cell identifier or by an index of a candidate serving cell in a candidate target serving cell list. ●Beam information: beam information associated with each current target serving cell information in the same MAC CE, which can be indicated by SSB information and / or CSI-RS information and / or TCI status identifier. UE fast serving cell change operation - Overview

[0097] The following describes a set of example fast serving cell change operations performed by the UE in response to receiving L1 or L2 fast serving cell change signaling or triggering.

[0098] For example, the L2 layer of the UE may perform at least one of the following: ●Key code verification used to verify fast serving cell change signaling. • One or more Random Access Channel (RACH) procedures used to access the target serving cell. ●One or more complete MAC layer resets or adapted MAC layer resets. ●One or more serving cell activation / deactivation operations.

[0099] For another example, one or more RLC layer operations may also be performed in the UE. In addition, one or more PDCP layer operations may also be performed in the UE. In addition, one or more RRC layer operations may be performed in the UE.

[0100] These example operations in various network layers in response to fast serving cell change signaling by the UE are described in further detail below. UE fast serving cell change operation - MAC layer

[0101] In some implementations, after receiving the fast service cell change signaling from the source service cell, the UE may first perform a key code verification for the fast service cell change. In some example implementations, if the key code in the received L1 / L2 signaling for the fast service cell change matches the value of the reference key code in the RRC configuration associated with the target service cell and / or source service cell for the fast service cell change, the UE may determine that the key code verification is successful. The UE may then continue to notify the upper layer of the fast service cell change. Otherwise, the UE may ignore the received L1 / L2 fast service cell change signaling without performing further service cell change operations.

[0102] After successful authentication, the UE may, for example, perform one or more RACH procedures to access the target serving cell. For example, the RACH procedure may involve the UE first determining whether any RACH operation needs to be performed. More specifically, the UE may determine whether to perform a RACH procedure to access the target serving cell as part of the serving cell change procedure based on the fast serving cell change signaling, and in response to determining that the RACH procedure is to be performed, continue to perform the RACH procedure.

[0103] In some example implementations, as long as L1 / L2 signaling for a fast serving cell change is received and successfully verified via the key code process described above, a RACH operation may be initiated in the target serving cell.

[0104] In some alternative implementations, when L1 / L2 signaling of a fast serving cell change is received, whether a RACH operation should be initiated on the target serving cell may be determined by one or more of the following explicit indications: ● An explicit RACH procedure indication pre-stored in the RRC reconfiguration message associated with the target serving cell. For example, there may be an information element in the RRC reconfiguration message indicating whether a RACH procedure is required. • There is a RACH configuration associated with the target serving cell. • Explicit RACH triggering indication in layer-1 or layer-2 signaling for fast serving cell change.

[0105] If one or more of the above explicit conditions are met, RACH operation may be performed.

[0106] In some other alternative implementations, when L1 / L2 signaling of a fast serving cell change is received, whether a RACH operation should be initiated on the target serving cell may be determined by one or more of the following implicit indications: • The Timing Advance (TA) value associated with the target serving cell is invalid. • There is no TA value or Timing Advance Group (TAG) ID associated with the target serving cell. ●There is no TA value in the fast serving cell change signaling. ●Perform a MAC reset.

[0107] If one or more of the above implicit conditions are met, RACH operation may be performed.

[0108] In some example implementations, once the UE determines to perform a RACH procedure on the target serving cell, the RACH operation may proceed. Various parameters of the RACH operation may be pre-configured in an RRC configuration associated with the target serving cell. Additionally, the RACH procedure may be a contention-free RACH (CFRA) procedure or a contention-based RACH (CBRA) procedure.

[0109] In some example implementations, when the NW provides a RACH preamble identifier and / or a RACH opportunity (RO) identifier for a fast serving cell change or RRC signaling via layer-1 signaling or layer-2 signaling, the UE may determine to follow the CFRA procedure and may continue to perform the CFRA procedure using the RACH preamble identifier and RO identifier explicitly provided by the NW.

[0110] In some example implementations, when no RACH preamble identifier or a RACH RO identifier is signaled, or the current RACH preamble identifier is equal to 0b000000 or the dedicated RRC configuration is not signaled, the UE may determine that a CBRA procedure is to be followed and may proceed to select a target signal block (SSB) having a synchronization signal-RSRP (SS-RSRP) higher than a reference signal received power threshold and a RACH preamble corresponding to the target SSB from among a plurality of SSBs to perform the CBRA procedure.

[0111] In some example implementations, a normal full MAC reset or an adapted MAC reset may be performed. For example, the UE may first determine whether to perform a full MAC reset or an adapted MAC reset. For example, an explicit RRC information element in an RRC configuration associated with a target serving cell or a target serving cell list including the target serving cell may indicate to the UE whether to perform a normal full MAC reset or an adapted MAC reset. For another example, an explicit indication in fast serving cell change signaling may indicate to the UE whether to perform a normal full MAC reset or an adapted MAC reset.

[0112] In some implementations, adapting the MAC reset may include performing one or more of the following: ●Cancel the ongoing RACH process; ● Refresh RACH message-3 buffer; ● Refresh RACH message-A buffer; ●Cancel the beam failure recovery (BFR) process triggered on the target serving cell; ●Cancel the Power Headroom Report (PHR) process triggered on the target cell; ● Cancel the consistent listen-before-talk (LBT) failure for triggering of the wireless device's original cell and target serving cell; ● Reset the beam failure instance BFI counter (BFI-COUNTER) for the wireless device's original cell and target serving cell; ● Reset the LBT_COUNTER for the wireless device's original cell and target serving cell; ●Cancel the triggered Scheduling Request (SR) process; ● flush the soft buffers of all downlink hybrid automatic repeat request (DL HARQ) processes for the original cell and treat the next received transport block (TB) transmission as the first transmission; or • Set the New Data Indicator (NDI) of all UL HARQ process IDs of the original cell and the target cell to zero.

[0113] In some implementations, the adapted MAC reset may be a subset of a normal full MAC reset. In some implementations, some operations in the adapted MAC reset may be modified from the corresponding normal MAC reset operations. In some implementations, the main difference between the full MAC reset and the adapted MAC reset may be that the full MAC reset includes considering all TA timers expired for all time advance groups (TAGs), while the adapted MAC reset may not include such considerations. For the adapted MAC reset, some example modifications and adaptations for fast serving cell changes are reflected in the above list.

[0114] In some implementations, the AllowedServingCell of an LCH (e.g., mapped to a DRB of a serving cell) may be determined. In one implementation, if an LCH has been configured with an AllowedServingCell containing a target cell, and the target cell is the only cell, and if the target cell is one of the SCells, the UE considers the serving cell with ID=0 as the AllowedServingCell. In one implementation, the AllowedServingCell of the LCH MACCE may be introduced to dynamically adjust the AllowedServingCell of one or more LCHs. In another implementation, the MAC CE may include at least one of the following information: ●LCH ID: Indicates the LCH used for remapping to the serving cell. ● Serving cell ID: Indicates the serving cell to which the LCH should be mapped.

[0115] In one implementation, it is up to the NW to decide whether to adjust the allowed serving cell of the LCH via RRC reconfiguration before sending the L1 / L2 signal for the serving cell change or after the serving cell change is sent to the UE.

[0116] In some implementations, the MAC layer operations of the UE in response to receiving the fast service cell change signaling may further include service cell activation and deactivation operations. The UE may determine whether to perform any service cell deactivation based on the indication contained in the fast service cell change signaling. For example, when receiving and verifying the L1 / L2 fast service cell change signaling, the UE may deactivate all activated service cells, such as the SCells of the cell group associated with the MAC entity. For example, the UE may deactivate all SCells of the MCG in the case of a PCell change, or deactivate all SCells of the SCG in the case of a PSCell change. In some example implementations, the UE may deactivate all activated SCells that are not included in the service cell list indicated by the RRC information element in the RRC configuration associated with the target service cell or the candidate target service cell list. UE fast serving cell change operation - RLC layer

[0117] In some implementations, upon receiving and verifying L1 / L2 fast serving cell change signaling, the UE may perform one or more RLC layer operations. For example, the RLC layer operation may include re-establishing an RLC entity. In some implementations, whether the RLC entity is to be re-established may be indicated by an information element in the RRC configuration associated with the target serving cell or an indication (e.g., a flag indicator) in the fast serving cell change signaling. In some implementations, such an indication information element may be for each RLC entity of the cell group involved. In some other implementations, the indication information element may be configured for each cell group. UE fast serving cell change operation - PDCP layer

[0118] In some implementations, upon receiving and verifying L1 / L2 fast serving cell change signaling, the UE may perform one or more PDCP layer operations.

[0119] In some implementations, when a signal radio bearer (SRB) is configured with carrier aggregation (CA) duplication, the UE may suspend PDCP duplication of the SRB until the serving cell change procedure is completed. In such implementations, the PDCP entity may generate only one PDCP PDU and send it to the lower layers of the primary path.

[0120] In some implementations, when there are only two RLC entities associated with PDCP duplication of one data radio bearer (DRB), the UE may automatically deactivate PDCP duplication upon receiving fast serving cell change signaling, regardless of MCG or SCG.

[0121] In some other implementations, when there are more than two RLC entities associated with PDCP replication of a DRB, the UE may deactivate RLC entities other than the primary RLC entity for PDCP replication upon receiving fast serving cell change signaling, regardless of the MCG and SCG.

[0122] In another example implementation, in the case where there are more than two RLC entities associated with PDCP repetition and the RLC entities belong to different CGs, if the primary path is located in the MCG and if L1 / L2 signaling for fast serving cell change is received for the SCG, the UE may deactivate PDCP repetition for all RLC entities in the SCG. In another implementation, in the case where there are more than two RLC entities associated with PDCP repetition and the RLC entities belong to different CGs, if the primary path is located in the SCG and if L1 / L2 signaling for fast serving cell change is received for the MCG, the UE may deactivate PDCP repetition for all RLC entities in the MCG.

[0123] In some implementations, the UE may perform PDCP recovery. For example, an information element may be included in an RRC configuration associated with a target cell and / or a candidate target cell list. The information element may be used to indicate to the UE whether the UE needs to perform PDCP recovery for an acknowledged mode (AM) DRB. If so, the UE may proceed to perform such PDCP recovery for an AM DRB. UE fast serving cell change operation - RRC layer

[0124] In some example implementations, upon receiving and verifying L1 / L2 fast serving cell change signaling, the UE may perform one or more RRC layer operations. The RRC layer operations may depend on various RRC models. Two example RRC models are described below along with corresponding RRC layer operations that the UE may perform under each RRC model. RRC Mode #1

[0125] In the example RRC mode #1, the fast serving cell change based on L1 / L2 signaling can continue to use the pre-configured RRCReconfiguration message to implement the fast serving cell change. More specifically, the UE can still follow the normal behavior of the RRC reconfiguration process to reuse, for example, the information element reconfigurationWithSync to implement the fast serving cell change.

[0126] In some implementations, the NW may pre-configure the UE with L1L2CentricRRCReconfig including an RRCReconfiguration message. The UE may then store the L1L2CentricRRCReconfig information in a UE variable for fast serving cell change based on L1 / L2 signaling. An example RRC structure is shown in Table 1 below. In some example implementations, a key code may be configured in this example RRC structure for fast serving cell change. Table 1

[0127] As shown in Table 1, the RRC unit reoconfigurationWithSync2 may be introduced into the information unit of CellGroupConfig, and the unit may be mutually exclusive with reconfigurationWithSync.

[0128] In some implementations, if ReconfigurewithSync is received / configured in the RRCReconfiguration message for fast serving cell change, the MAC layer may be completely reset in a normal manner and the TA values ​​of all TAGs may be considered invalid. Conversely, if ReconfigurewithSync2 is received / configured in the RRCReconfiguration message for fast serving cell change, the MAC layer may be adaptively reset as described above, and if the corresponding TA timer has not expired, the TA value of the MAC entity may still be considered valid.

[0129] In some implementations of ReconfigurationWithSync2, the following information units may be further included: ●SCellID / ServingCellID / AssistanceCellID / CandidateCellID / Physic alCellID: indicates the target cell for fast serving cell change. In one implementation, the UE may apply the cell configuration associated with this information element (ie, ServingCellConfigComm and / or ServingCellConfig) as the serving cell configuration for fast serving cell change. ●ServingCellConfigCommon: cell-specific parameters of the target serving cell. ●ServingCellConfig: UE-specific parameters serving as the target serving cell. ● NewUE-ID: Indicates the new C-RNTI that should be used after a fast serving cell change. If not present, the old C-RNTI should be retained for use when transferring to the target serving cell.

[0130] Utilizing RRC Model #1, and in some example implementations, the UE may store the current CellGroupConfiguration and / or C-RNTI and / or servingCellConfigCommon and / or servingCellConfigDedicated into a list of candidate target cells with minimized L1L2CentricRRCReconfigID that is currently available when receiving an indication of a fast serving cell change from lower layers.

[0131] In some other implementations, the UE may store the current CellGroupConfiguration and / or C-RNTI and / or servingCellConfigCommon and / or servingCellConfigDedicated in a list of candidate target cells with the sameL1L2CentricRRCReconfigID, which belongs to the target serving cell indicated by the L1 / L2 signaling for fast serving cell change.

[0132] Therefore, the UE may perform the following example steps under RRC Model #1: ●Step 1: The UE may determine whether an indication of a fast serving cell change is received from a lower layer, and if so, proceed to step 2, otherwise, proceed to the end. ●Step 2: The UE may perform the RRC reconfiguration procedure according to the RRCReconfiguration message of the target serving cell stored in the L1L2CentricRRCReconfigToADDmodList indicated by the indication from the lower layer, and then go to step 3. ●Step 3: The UE may store the current CellGroupConfiguration and / or C-RNTI and / or servingCellConfigCommon and / or servingCellConfigDedicated in the RRCReconfiguration message of the source serving cell into the L1L2CentricRRCReconfigToADDmodList with the sameL1L2CentricRRCReconfigID of the target serving cell.

[0133] In another example implementation, the UE may perform the following steps under RRC Model #1: ● Step 1: The UE may determine whether the RRC reconfiguration message includes reconfigurationWithSync2 or reconfigurationWithSync. If reconfigurationWithSync is included, go to step 2A, otherwise go to step 2B. • Step 2A: The UE may perform RRC reconfiguration for fast serving cell change normally (ie normal full MAC reset) and then go to end. ● Step 2B: The UE may perform RRC reconfiguration for fast serving cell change with adaptive reset of the MAC entity. Then go to the end. RRC Model #2

[0134] In the example RRC model #2, the candidate target serving cell configurations for fast serving cell change may be in one or more cell configuration lists, which may be configured in the cell group configuration CellGroupConfig and / or the cell configuration SpCellConfig.

[0135] In some example implementations, if the target serving cell is one of the SCells, the UE may apply a differential reconfiguration of the target serving cell in the list for a fast serving cell change. In such implementations, the deltaConfigurationForSpCellChange information element may include at least one of the following information: ●PUCCH channel related configuration New UE logo ●Radio link monitoring related configuration ●Beam failure recovery related configuration RACH related configuration, including: ■RACH resource allocation ■ Dedicated RACH resource configuration ●ResetMAC / PartialResetMAC flag ●Timer for fast serving cell change Key code

[0136] In some example implementations, if the target serving cell is not one of the SCells in SCellToAddModlist, the UE may apply the RRC configuration for the target serving cell for fast serving cell change. In other words, the target serving cell cannot be activated as an SCell, and the RRC configuration of the target serving cell may include at least one of the following information: =ServingCellConfigCommon: Indicates the cell-specific parameters for the target serving cell. ●ServingCellConfigDedicated: Indicates UE-dedicated parameters for the target serving cell. ●RACH related configuration: Indicates the RACH resources / parameters of the target serving cell, including At least one of the following: ■RACH resource allocation ■ Dedicated RACH resource configuration ● Timer for fast serving cell change: A timer used by the UE to determine whether the fast serving cell change is successfully terminated. ●NewUEIdentity: C-RNTI that should be used after a fast serving cell change. ●ResetMAC: Indicates whether the MAC entity should be reset. ●TAG ID: Indicates the TAG to which the target serving cell belongs. Key code

[0137] Therefore, the UE may perform the following example steps under RRC Model #2: ● Step 1: The UE may determine whether an indication of a fast serving cell change is received from a lower layer, and if so, go to step 2. Otherwise, go to the end. ●Step 2: The UE may determine whether the RRC configuration of the target serving cell indicated by the L1 / L2 signaling from the lower layer is the SCell within the SCellToAddmodList, and if so, proceed to step 3; if not, proceed to step 4. ●Step 3: The UE may adapt at least one of the following operations and then go to the end. ■Configure the SCell based on the delta configuration of the target serving cell. ■ If the SCell is not activated yet, activate the SCell. ■ Release the serving cell configuration and notify the lower layers to release the resources of the current serving cell. ■ The SCell is regarded as the serving cell. In one implementation, the serving cell ID of the SCell is regarded as equal to 0. ■Reset or adaptively reset (eg, partially reset) the MAC entity of the cell group. ■ Apply ueNewIdentity as the C-RNTI for this cell group (if present). ●Step 4: The UE may adapt at least one of the following operations and then go to the end. ■ Configure lower layers for the target serving cell according to ServingCellConfigCommon (if present). ■ Configure lower layers for the target serving cell according to ServigCellConfigDedicated (if present). ■Reset or adaptively reset (eg, partially reset) the MAC entity of the cell group. ■Apply ueNewIdentity as the C-RNTI for the cell group (if present). Notify the target serving cell

[0138] After the UE performs the above-mentioned various fast serving cell change operations, a notification of completion of the fast serving cell change operation may be sent to the target serving cell. For example, such a notification may be sent in at least one of the following formats: ● MAC CE-like notifications, including one of the following: ■C-RNTI MAC CE ■BSR MAC CE ■ New MAC CE, which may contain information of UE identity and / or key in RRC configuration associated with target serving cell / candidate target serving cell list / source cell or / and configured in L1 / L2 signaling for triggering fast serving cell change. ●UCI, such as scheduling requests RRC messages RACH process

[0139] In some implementations involving MAC CEs, a Scheduling Request (SR) should be triggered if there is no available PUSCH for transmitting them. Response to notification from target serving cell

[0140] The response from the target serving cell to the notification may include an acknowledgement (ACK), a negative acknowledgement (NACK), or no response.

[0141] In some implementations, if a RACH procedure has been performed for a fast serving cell change based on L1 / L2 signaling, successful termination of the RACH procedure may be considered as an ACK indication.

[0142] In some implementations, receiving a DCI for a new C-RNTI may be considered an ACK indication.

[0143] In some implementations, the reception of a MAC CE may be considered as an ACK indication. In such implementations, the MAC CE may include only a subheader without a payload, or the MAC CE may include at least one of the following information: ● key code; or New C-RNTI

[0144] In some implementations, the ACK indication may be considered received when a UL grant is received for a new transmission for the HARQ process ID used to send a notification to the NW.

[0145] In some implementations, a timer (FastServingCellChangeTimer) configured in the configuration associated with the target serving cell and / or the candidate target serving cell list and / or the source serving cell may be used to determine whether the fast serving cell change based on L1 / L2 signaling is successful. For example, if an ACK is not received before the FastServingCellChangeTimer expires, a NACK indication may be considered to have been received. UE actions in case of NACK for notification

[0146] If the UE determines that a NACK is indicated from the target serving cell, for example, the UE may trigger an RRC re-establishment procedure.For another example, if the source serving cell configuration has not been released and / or has been stored and is still available, the UE may revert to the source serving cell.

[0147] The above description and accompanying drawings provide specific example embodiments and implementations. However, the described subject matter may be embodied in a variety of different forms, and therefore, the subject matter covered or claimed is intended to be interpreted as not being limited to any example embodiment set forth herein. The claimed or covered subject matter is intended to be reasonably broad. Among other things, for example, the subject matter may be embodied as a method, device, component, system, or non-transitory computer-readable medium for storing computer code. Therefore, the embodiment may be in the form of, for example, hardware, software, firmware, storage media, or any combination thereof. For example, a component, device, or system including a memory and a processor may implement the above method embodiment by executing computer code stored in the memory.

[0148] Throughout the specification and claims, terms may have nuanced meanings that are suggested or implied from the context rather than the explicitly stated meanings. Likewise, the phrase "in one embodiment / implementation" as used herein does not necessarily refer to the same embodiment, and the phrase "in another embodiment / implementation" as used herein does not necessarily refer to a different embodiment. For example, it is intended that the claimed subject matter includes combinations of all or part of the example embodiments.

[0149] In general, terms may be understood at least in part based on their usage in context. For example, terms used herein, such as "and", "or" or "and / or" may include multiple meanings that depend at least in part on the context in which the terms are used. Typically, "or", if used in an associative list, such as A, B, or C, is intended to mean A, B, and C (here in an inclusive sense) as well as A, B, or C (here in an exclusive sense). In addition, the term "one or more" as used herein, depending at least in part on the context, may be used to describe any feature, structure, or characteristic in a singular sense, and may also be used to describe a combination of features, structures, or characteristics in a plural sense. Similarly, the terms "one", "an", or "the" may also be understood to convey singular usage or to convey plural usage, depending at least in part on the context. In addition, the term "based on" may be understood to not necessarily be intended to convey a set of exclusive factors, and on the contrary, may allow for the presence of other factors that are not necessarily explicitly described, which again depends at least in part on the context.

[0150] Reference throughout this specification to features, advantages, or similar language does not imply that all features and advantages that may be realized by the present solution should be included or included in any single implementation. Rather, language referring to features and advantages is understood to mean that a particular feature, advantage, or characteristic described in connection with an embodiment is included in at least one embodiment of the present solution. Thus, discussion of features and advantages and similar language throughout the specification may, but do not necessarily, refer to the same embodiment.

[0151] In addition, the features, advantages, and characteristics of the present solution may be combined in any suitable manner in one or more embodiments. Based on the description herein, one of ordinary skill in the relevant art will recognize that the present solution may be practiced without one or more specific features or advantages of a particular embodiment. In other cases, additional features and advantages may be recognized in certain embodiments, which may not be present in all embodiments of the present solution.

Claims

1. A method for preparing a serving cell change procedure performed by a wireless device, the method include: receiving cell measurement and measurement reporting configuration from a wireless communication node; performing cell measurement based on the cell measurement and measurement reporting configuration to generate a cell measurement report associated with the cell measurement; as well as The cell measurement report is sent in a cell measurement report message according to the cell measurement and measurement report configuration, and the cell measurement report message includes a layer-1 or layer-2 control message.

2. The method according to claim 1, in: The layer-1 comprises a physical (PHY) layer; and The layer-2 includes at least one of the following: a medium access control (MAC) layer, a radio link control (RLC) layer, or a packet data convergence protocol (PDCP) layer.

3. The method according to claim 1, wherein sending the cell measurement report include: The cell measurements are reported via a layer-1 Uplink Control Information (UCI) message or a layer-2 MAC Control Element (MAC CE) message.

4. The method according to claim 3, wherein the cell measurement report include: The wireless device further includes a source serving cell and at least one or more neighboring cells of the source serving cell.

5. The method according to claim 4, further comprising: include: In accordance with performing the cell measurement, one or more suitable neighbor serving cells are identified from a set of candidate neighbor cells of the source serving cell for the wireless device, wherein the cell measurement report includes physical cell information of the one or more suitable neighbor cells.

6. The method according to claim 5, in: The cell measurement report further includes beam information for the one or more suitable neighboring cells; and The beam information is provided to indicate one or more recommended beams among the one or more suitable neighboring cells for the serving cell change procedure.

7. The method of claim 4, wherein the cell measurement and measurement reporting configuration indicates to the wireless device a triggering event condition for sending the cell measurement report.

8. The method according to claim 7, wherein the trigger event condition for sending the cell measurement report comprises at least one trigger event condition in the following group of trigger event conditions: The first result of the cell measurement indicates that: the source serving cell for the wireless device is continuously at or below a first threshold measurement level during a first preconfigured measurement time period; The second result of the cell measurement indicates that at least one neighboring cell of the source serving cell for the wireless device is continuously at or above a second threshold measurement level during a second preconfigured measurement time period; or The difference measurement result between the first result and the second result is continuously at or above a cell measurement gap threshold level.

9. The method of claim 8, wherein the first threshold measurement level include: The sum of a first preconfigured baseline threshold level and a first configurable tolerance threshold level offset.

10. The method of claim 8, wherein the second threshold measurement level include: The sum of a second preconfigured baseline threshold level and a second configurable tolerance threshold level offset.

11. The method of claim 8, wherein the cell measurement gap threshold level include: The sum of the preconfigured baseline gap threshold level and the configurable tolerance gap threshold level offset.

12. The method according to claim 8, wherein the first preconfigured measurement time period include: At N consecutive measurement occasions on the source serving cell for the wireless device, N is a preconfigured positive integer.

13. The method according to claim 8, wherein the second preconfigured measurement time period include: M consecutive measurement occasions are performed on the at least one neighboring cell of the source serving cell for the wireless device, where M is a preconfigured positive integer.

14. The method of claim 8, wherein the first result or the second result comprises at least one of: a reference signal received power (RSRP), a signal to interference and noise ratio (SINR), or a reference signal received quality (RSRQ).

15. The method of claim 8, wherein the first result and the second result are each include: Cell-level measurements or beam-level measurements respectively associated with the source serving cell and the at least one neighboring cell of the source serving cell for the wireless device.

16. The method of claim 15, wherein the cell-level measurement result of the serving cell is derived from measurements of multiple beams associated with the serving cell.

17. The method of claim 15, wherein the beam-level measurements comprise measurements associated with a predetermined number of best beams for the source serving cell of the wireless device or the at least one suitable neighboring cell of the source serving cell.

18. The method according to claim 8, in: The first result includes N consecutive cell measurements for a first combination performed by the wireless device on the source serving cell, where N is a preconfigured positive integer; The second result comprises second combined N consecutive cell measurements performed on the at least one neighboring cell of the source serving cell; as well as The trigger event condition for sending the cell measurement report includes: sending the cell measurement report when the difference between the first combined N consecutive cell measurements and the second combined N consecutive cell measurements is at or above the cell measurement difference threshold level.

19. The method according to claim 8, wherein sending the cell measurement report in the cell measurement report message comprises, when at least one trigger event condition in the set of trigger event conditions is met: sending a MAC CE message including the cell measurement report to the wireless communication node; or The wireless device is triggered to send the cell measurement reporting message as layer-1 uplink control information (UCI) to the wireless communication node.

20. The method according to claim 8, wherein the applicable trigger event condition in the set of trigger event conditions is configured for each serving cell or for a candidate serving cell list.

21. The method according to claim 8, wherein a first neighboring cell and a second neighboring cell of the at least one neighboring cell of the source serving cell are independently configured with different triggering event conditions in the set of triggering event conditions.

22. The method of claim 8, wherein the set of trigger event conditions further comprises: include: The wireless device detects a beam failure in the source serving cell and fewer than P suitable beams of the source serving cell can be identified; or The wireless device detects a radio link failure with the source serving cell.

23. A wireless device comprising a processor and a memory, wherein the processor is configured to read computer code from the memory to cause the wireless device to: receiving cell measurement and measurement reporting configuration from a wireless communication node; performing cell measurement based on the cell measurement and measurement reporting configuration to generate a cell measurement report associated with the cell measurement; as well as The cell measurement report is sent in a cell measurement report message according to the cell measurement and measurement report configuration, and the cell measurement report message includes a layer-1 or layer-2 control message.

24. A computer program product comprising a non-transitory computer readable program medium having computer code stored thereon, the computer code, when executed by a processor, causing the processor to: receiving cell measurement and measurement reporting configuration from a wireless communication node; performing cell measurement based on the cell measurement and measurement reporting configuration to generate a cell measurement report associated with the cell measurement; as well as The cell measurement report is sent in a cell measurement report message according to the cell measurement and measurement report configuration, and the cell measurement report message includes a layer-1 or layer-2 control message.

Citation Information

Patent Citations

  • 3GPP mmw access link system architecture

    US20200084680A1

  • Cell measurement reporting schemes in wireless communications

    WO2022056808A1

  • Methods and nodes for measuring a serving cell in l1 / l2-centric mobility

    WO2022074602A1