Method for low-layer inter-cell mobility management

Abstract

Some embodiments include apparatus, methods, and computer program products for inter-cell mobility management using low-layer protocols in a 5G wireless communication system. A serving 5G Node B (gNB) may configure reports that a user equipment (UE) transmits to the serving gNB to make a handover decision. The serving gNB may configure a set of transmission configuration indication (TCI) states (e.g., a set of beams) corresponding to a physical cell, and the report includes layer 3 measurements corresponding to the TCI state of a neighbor or serving cell. The report may be transmitted using a lower layer protocol. The report may include layer 1 measurements transmitted using a layer 1 protocol, and the serving gNB may perform filtering to generate corresponding layer 3 measurements. Based on these reports, the serving gNB may use lower layer protocols to perform handover and synchronization from one TCI state to another TCI state.

Description

Background Art Technical Field

[0002] Embodiments described in the present disclosure generally relate to 5G wireless including switching.

[0003] Related fields

[0004] 5G wireless communication systems include handover from a serving 5G Node B (gNB) cell to a neighbor cell, which is handled at Layer 3 by Radio Resource Control (RRC) signaling. Summary of the invention

[0005] Using radio resource control (RRC) signaling at Layer 3 for 5G wireless handovers can result in significant latency, particularly at the interface between the user equipment (UE) and the serving 5G Node B (gNB). Some embodiments include the serving gNB collecting neighbor cell information via the user equipment (UE) and then making handover decisions based on the collected information. The collected information may include Layer 3 (L3) signal measurements, Layer 1 (L1) signal measurements (which are then filtered by the serving gNB via L3), and beam information (enabling the serving gNB to group beams according to 5G wireless cells). Some embodiments include the serving gNB using low-layer signaling (e.g., L1 and / or L2 signaling) to handover 5G wireless communications from a beam of the serving gNB to a different beam of a neighbor cell.

[0006] Some embodiments include apparatus, methods, and computer program products for low-layer inter-cell mobility management to reduce handover delays on a UE to serving gNB interface. Some embodiments include a serving gNB that determines a synchronization signal block (SSB) or channel state information reference signal (CSI-RS) measurement result to be performed on a neighbor cell as a channel measurement resource (CMR) in a reportConfig, and collects data including a physical cell ID of a neighbor cell based at least on the reportConfig. The serving gNB may configure N groups of transmission configuration indication (TCI) states for the UE, wherein the TCI states correspond to beams. A first group of the N groups corresponds to a serving gNB cell, and a second group of the N groups corresponds to a physical cell ID of a neighbor cell. The serving gNB may decide to perform a handover based at least on the collected data, and perform a handover from a TCI state in the first group to a TCI state in the second group.

[0007] To collect L3 data, the serving gNB may trigger an L3 result report and receive the L3 result report from the UE via an uplink control information (UCI) signal, wherein the L3 result report includes: L3-reference signal received power (RSRP), L3-reference signal received quality (RSRQ), or L3-signal to interference and noise ratio (SINR). The UCI signal may include a physical uplink control channel (PUCCH) signal or a physical uplink shared channel (PUSCH) signal. The serving gNB may trigger the L3 result report using RRC signaling, media access control (MAC) control element (CE) signaling, or downlink control information (DCI) signaling.

[0008] In some embodiments, the serving gNB may determine an event that triggers an event-based L3 report and reserve resources in a PUCCH signal or a PUSCH signal that enables the UE to provide an event-based report. The serving gNB may transmit the event that triggers the event-based report and the reserved resources to the UE. The serving gNB may receive an event-based report from the UE via a UCI signal, wherein the event-based report includes L3 measurement results such as: L3-RSRP, L3-RSRQ, or L3-SINR.

[0009] In some embodiments, the serving gNB may trigger an L1 result report and receive the L1 result report from the UE via a UCI signal, wherein the L1 result report may include L1 measurement results, such as: L1-RSRP, L1-RSRQ, or L1-SINR. The serving gNB may receive an indication as to whether the L1 result report is from the same or different TCI state as the previous L1 result report. When the serving gNB determines based on the indication that the L1 result report is from the same TCI state (e.g., the same beam) as the previous L1 result report, the serving gNB may continue to perform L3 filtering based on the previous L1 result report and the L1 result report. When the serving gNB receives an indication that the L1 result report is from a different TCI state than the previous L1 result report, the serving gNB may restart L3 filtering based on only the L1 result report. The serving gNB may use the results of the L3 filtering to configure N sets of TCI states and decide whether to perform switching.

[0010] The serving gNB may perform a handover by converting the 5G wireless communication from the TCI state of one cell to the TCI state of another cell using L1 or L2 signaling. For example, to perform a handover, the serving gNB may use a MAC CE to convert from a TCI state in a first set of TCI states corresponding to the serving gNB cell to a TCI state in a second set of TCI states corresponding to the neighbor cell. In some embodiments, the serving gNB may use a downlink control information (DCI) signal to convert from a TCI state in the first set to a TCI state in the second set to perform a handover, wherein the DCI signal includes a downlink allocation, an uplink grant, or a dedicated DCI format.

[0011] In some embodiments, the UE may receive instructions from the serving gNB to report measurement results, and the UE may transmit reports to the serving gNB based on these instructions. Subsequently, the UE may receive a transition from the TCI of the serving gNB to the new TCI state from the serving gNB via a MAC CE or DCI including the new TCI state of the neighbor cell, and communicate with the neighbor cell via the new TCI state. In response to the transition to the new TCI state, the UE may start a confirmation timer. In order to communicate with the neighbor cell via the new TCI state, the UE may receive a dedicated physical downlink control channel (PDCCH) from the neighbor cell via the new TCI state and stop the confirmation timer. Before transmitting an uplink signal, the UE may apply a new timing advance group (TAG) corresponding to the neighbor cell.

[0012] When the instruction received from the serving gNB includes a request for an L3 result report, the UE may transmit the L3 result report via a PUCCH signal or a PUSCH signal. In some embodiments, the instructions include an event that triggers an event-based report and reserved resources, and the UE may determine that the event is triggered. The UE may transmit the event-based report according to the reserved resources via a PUCCH signal or a PUSCH signal. If the PUCCH signal or the PUSCH signal collides with a second signal, the UE may discard and subsequently resend the PUCCH signal or the PUSCH signal. The second signal may be: a physical random access channel (PRACH) signal, a scheduling request (SR) signal, or a hybrid automatic repeat request (HARQ)-ACK signal. If the instruction from the serving gNB does not include reserved resources, the UE may determine that the event is triggered and request resources for transmitting the event-based report to the serving gNB through a dedicated or normal scheduling request (SR). BRIEF DESCRIPTION OF THE DRAWINGS

[0013] The accompanying drawings, which are incorporated herein and form a part of the specification, illustrate the disclosed disclosure and, together with the description, further serve to explain the principles of the disclosure and enable one skilled in the relevant art to make and use the disclosure.

[0014] Figure 1 An exemplary system for low-layer inter-cell mobility management according to some embodiments of the present disclosure is shown.

[0015] Figure 2 A block diagram of an exemplary wireless system for low-layer inter-cell mobility management according to some embodiments of the present disclosure is shown.

[0016] Figure 3 An exemplary configuration report request for low-layer inter-cell mobility management according to some embodiments of the present disclosure is shown.

[0017] Figure 4A A 5G Node B (gNB) triggering and receiving Layer 3 (L3) result reporting according to some embodiments of the present disclosure is shown.

[0018] Figure 4B Event triggering and gNB receiving L3 result reporting according to some embodiments of the present disclosure are shown.

[0019] Figure 5 A gNB is shown triggering and receiving a Layer 1 (L1) result report and then performing L3 filtering according to some embodiments of the present disclosure.

[0020] Figure 6 L3 filtering of L1 result reports according to some embodiments of the present disclosure is shown.

[0021] Figure 7 The grouping of transmission configuration indication (TCI) states into groups corresponding to cells is shown according to some embodiments of the present disclosure.

[0022] Figure 8 An exemplary gNB method for low-layer inter-cell mobility management according to some embodiments of the present disclosure is shown.

[0023] Fig. 9 An exemplary user equipment (UE) method for low-layer inter-cell mobility management according to some embodiments of the present disclosure is shown.

[0024] Fig.10 is an exemplary computer system for implementing some embodiments or one or more portions of embodiments.

[0025] Fig.11 is an exemplary system for inter-cell mobility management according to some embodiments of the present disclosure.

[0026] The present disclosure is described with reference to the accompanying drawings. In the drawings, generally, the same reference numerals represent the same or functionally similar elements. In addition, generally, the leftmost digit of a reference numeral identifies the drawing in which the reference numeral first appears. DETAILED DESCRIPTION

[0027] The 5G wireless communication system can perform a handover from a serving 5G Node B (gNB) cell to a neighbor cell, where such a handover is managed at Layer 3 by radio resource control (RRC) signaling. Fig.11 An exemplary system 1100 for inter-cell mobility management according to some embodiments of the present disclosure is shown. The system 1100 includes a user equipment (UE) 1105, a source gNB 1110, and a target gNB 1115, wherein the UE 1105 first communicates with the source gNB 1110. After a handover occurs, the UE 1105 communicates with the target gNB 1115. In the system 1100, measurement results and reports 1120, handover triggers 1145, and synchronization to a new cell and completion of an RRC handover process 1175 are handled by RRC signaling at layer 3, and these three stages together can result in large latency. Layer 3 (L3) refers to the network layer in the Open Systems Interconnection (OSI) model.

[0028] Some embodiments herein include apparatus, methods, and computer program products for inter-cell mobility management using low-layer protocols in a 5G wireless communication system. A serving gNB may configure and request reports based on which a UE collects neighbor cell information for each beam of a neighbor cell, including L3 signal measurements and layer 1 (e.g., physical layer (L1) of OSI) signal measurements. The UE collects the information in the report and transmits it to the serving gNB for it to make a handover decision. The serving gNB may use the report to organize corresponding measurements according to beams within different 5G wireless cells. For example, the serving gNB may configure a set of transmission configuration indication (TCI) states (e.g., a set of beams) to correspond to a physical cell ID. The report may be transmitted to the serving gNB using a lower layer protocol. When the report includes L1 measurement results, the serving gNB may perform filtering to generate corresponding layer 3 measurement results. Based on these reports, the serving gNB may use the lower layer protocol to perform handover and synchronization from one TCI state to another TCI state. In the present disclosure, the serving gNB provides 5G wireless communication for a serving cell, and the neighbor gNB provides 5G wireless communication for a neighbor cell. The serving gNB may also be referred to as the source gNB, and the neighbor gNB may be referred to as the target gNB.

[0029] Figure 1An exemplary system 100 for low-layer inter-cell mobility management according to some embodiments of the present disclosure is shown. The system 100 includes a UE 105 that first communicates with a source gNB 110 and then, after handover, communicates with a target gNB 115. In some embodiments, the source gNB 110 transmits a signal to the UE 105 for configuring a channel state information (CSI) frame and a TCI state group 120. Thus, the UE 105 performs measurements based on the CSI frame and reports the measurement results to the source gNB 110.

[0030] The exchange is shown as measurement results and reports 130 of L1 / Layer 2 (L2) signaling. Source gNB 110 receives the measurement results in reports. Based on these reports, source gNB 110 can group TCI states (e.g., group beams) from neighbor cells (e.g., target gNB cells) into one group. And, source gNB 110 can group TCI states from source gNB cells (e.g., serving gNB cells) into another group. Using the measurement results and TCI state groupings, source gNB 110 makes a switching decision 140 using L1 or L2 signaling to change from one beam (e.g., TCI state) to another beam (TCI state). For example, the switching decision 140 may indicate a switch from a first TCI state in a first group associated with source gNB 110 to a second TCI state in a second group associated with target gNB 115.

[0031] The source gNB 110 may provide a TCI indication to the UE 105 based on a media access control (MAC) control element (CE) or downlink control information (DCI) signaling, as shown at 160. MAC CE signaling occurs at L2 and DCI signaling occurs at L1. The UE 105 then uses the received TCI indication to transition from the TCI state of the source gNB 110 to the TCI state of the target gNB 115. After a given number of time slots (e.g., after a given number of milliseconds) when appropriate, such as after an ACK, the UE 105 sets an acknowledgement timer and begins communicating with the new cell and the target gNB 115, as shown at 185.

[0032] The confirmation timer is a mechanism that allows the UE 105 to revert to communicating with the source gNB 110 in the event that handover to the target gNB 115 fails. For example, at 190, if the UE 105 receives a signal from the target gNB 115 (e.g., a physical downlink control channel (PDCCH) signal), the confirmation timer is reset, i.e., essentially stopped. The UE 105 disconnects from the source gNB cell and continues to communicate with the target gNB 115. Otherwise, the confirmation timer may expire and the UE 105 begins communicating with the source gNB cell. Thus, unlike handovers that rely on RRC layer signaling (e.g., Fig.11 )'s 5G wireless system, Figure 1 Inter-cell mobility management is performed using low layer signaling (e.g., L1 and / or L2). Fig.11 Compared with system 1100, the corresponding function has lower latency.

[0033] Figure 2 A block diagram of an exemplary wireless system 200 for low-level inter-cell mobility management according to some embodiments of the present disclosure is shown. For convenience and not limitation, Figure 1 The system 200 can be described by the elements of Figure 1 UE 105, source gNB 110, or target gNB 115. For example, the gNB may be a 5G base station. The UE may be a computing electronic device such as a smart phone, a cellular phone, and for simplicity, may include other computing devices including, but not limited to, laptops, desktop computers, tablets, personal assistants, routers, monitors, televisions, printers, and appliances. The system 200 may include a processor 210, a transceiver 220, a communication infrastructure 230, a memory 235, and an antenna 225, which together perform operations to implement low-layer inter-cell mobility management. The transceiver 220 transmits and receives 5G wireless communication signals via the antenna 225. The communication infrastructure 230 may be a bus. The memory 235 may include random access memory (RAM) and / or a cache, and may include control logic components (e.g., computer software), computer instructions, and / or data. The processor 210, when executing computer instructions, may be configured to perform the functionality described herein for low-layer inter-cell mobility management. Alternatively, the processor 210 may include its own internal memory (not shown), and / or may be "hardwired" (e.g., in a state machine) configured to perform the functionality described herein for low-layer inter-cell mobility management. The antenna 225 coupled to the transceiver 220 may include one or more antennas that may be the same or different types to enable wireless communications over a wireless network.

[0034] Figure 3An exemplary configuration report request 300 for low-layer inter-cell mobility management according to some embodiments of the present disclosure is shown. For convenience and not limitation, the Figure 1 and / or Figure 2 elements to describe Figure 3 For example, in Figure 1 In the configuration 120 of the CSI framework and TCI state group signal, the configuration report request 300 may include a configuration report request 300, which may be a reportConfig including a physical cell ID (e.g., PhysCellId). The source gNB 110 may configure a synchronization signal block (SSB) and / or a channel state information (CSI)-reference signal (RS) from the target gNB 115 as a channel measurement resource (CMR) in the reportConfig, as shown in the configuration report request 300. The physical cell ID may be configured for each CMR (e.g., for each gNB). Therefore, the source gNB 110 may use the configuration report request 300 to request the UE 105 to measure the CMR in different cells (e.g., measurement results from different beams in neighbor cells) and transmit the measurement results back to the source gNB 110 in a result report. Using the measurement results from various beams and neighbor cells, the source gNB 110 may determine whether to switch the 5G wireless communication to the neighbor cell and the corresponding TCI state (e.g., the corresponding beam).

[0035] Figure 4A An example 400 of a gNB triggering and receiving an L3 result report according to some embodiments of the present disclosure is shown. Figure 4B An example 450 of event triggering and gNB receiving L3 result report according to some embodiments of the present disclosure is shown. For convenience and not limitation, Figure 1 , Figure 2 and / or Figure 3 Examples 400 and 450 are described using elements of the present invention. Examples 400 and 450 illustrate the use of L1 signaling and L2 signaling (such as Figure 1 Instead of using RRC signaling at L3 (such as Fig.11 As described above, example 400 is described first from the perspective of source gNB 110 and then from the perspective of UE 105. Similar descriptions for example 450 are provided later.

[0036] Example 400 from the viewpoint of source gNB 110 :

[0037] At 405, the source gNB 110 transmits RRC signaling for configuring CMR and other reporting configurations. The RRC signaling may include Figure 3 The configuration report request 300 (e.g., reportConfig) for low layer inter-cell mobility management may be requested. The configuration may request L3 measurement results in the report, including but not limited to: L3-reference signal received power (RSRP), L3-reference signal received quality (RSRQ), or L3-signal to interference and noise ratio (SINR). The report may be configured to be periodic, semi-persistent, or aperiodic, and the report may be configured to be transmitted to the source gNB 110 via uplink control information (UCI) signaling.

[0038] At 410, the source gNB 110 transmits a signal triggering the UE 105 to respond to the L3 result report based on the report configuration arranged at 405 (e.g., configuration report request 300). For example, the report can be triggered by an RRC signal, a MAC CE, or a DCI signal.

[0039] At 415, the source gNB 110 receives an L3 result report at L1 via UCI signaling (e.g., via a physical uplink control channel (PUCCH) signal or a physical uplink shared channel (PUSCH) signal). The L3 result report may include, for example, measurement results from neighbor cells and corresponding TCI states collected by the UE 105 based on the configuration report request 300 and other configurations at 405.

[0040] Example 400 from the viewpoint of UE 105 :

[0041] At 405, UE 105 receives RRC signaling for configuring CMR and other reporting configurations, which may include, for example Figure 3 Configuration report request 300 for low layer inter-cell mobility management. The configuration may request L3 measurement results in the report, including but not limited to: L3-RSRP, L3-RSRQ or L3-SINR. Reports may be configured as periodic, semi-persistent or aperiodic, and reports may be configured to be transmitted to the source gNB 110 via uplink control information (UCI) signaling.

[0042] At 410, the UE 105 receives a gNB signal that triggers an L3 result report. For example, the report may be triggered by an RRC signal, a MACCE, or a DCI signal. In response, the UE 105 may collect measurement results and corresponding TCI states from neighbor cells based on the configuration report request 300.

[0043] At 415, the UE 105 transmits the collected measurement results via UCI signaling (e.g., via a PUCCH signal or a PUSCH signal). There may be conflicts between the PUCCH or PUSCH signal carrying the collected measurement results (e.g., report) and other signals. Some examples of how the UE responds are shown below, but the implementation is not limited to these examples.

[0044] In some embodiments, when a PUCCH or PUSCH signal (e.g., a report) carrying collected measurement results collides with a second signal, the UE 105 discards and later retransmits the PUCCH or PUSCH signal carrying the collected measurement results. In some examples, the UE 105 may instead discard the second signal and then retransmit the second signal. Examples of the second signal include a physical random access channel (PRACH), a scheduling request (SR), or a hybrid automatic repeat request (HARQ)-ACK signal.

[0045] In some examples, when a PUCCH or PUSCH signal (e.g., report) carrying collected measurement results collides with UCI other than SR / HARQ-ACK, UE 105 discards the UCI signal and retransmits the UCI signal later. In some examples, when a PUCCH signal (e.g., report) carrying collected measurement results collides with a PUSCH signal, UE 105 discards the PUCCH signal, multiplexes the content of the PUCCH signal carrying the collected measurement results with the content of the PUSCH signal, and then transmits the multiplexed information via the PUSCH signal. In some examples, when a PUCCH or PUSCH signal (e.g., report) carrying collected measurement results collides with a sounding reference signal (SRS), UE 105 discards the SRS signal and retransmits the SRS signal later.

[0046] Example 450 from the viewpoint of source gNB 110 :

[0047] In the above example 400, the source gNB 110 triggers L3 result reporting. In the following example 450, the source gNB 110 defines one or more events for the UE. When the one or more events are true, the one or more events trigger corresponding event-based reporting.

[0048] At 455, the source gNB 110 transmits RRC signaling for configuring CMR and other reporting configurations, which may include, for example Figure 3A configuration report request 300 for low layer inter-cell mobility management may be requested. The configuration may request L3 measurement results in the report, including but not limited to: L3-RSRP, L3-RSRQ or L3-SINR. The report may be configured to be periodic, semi-persistent or aperiodic, and the report may be configured to be transmitted to the source gNB 110, for example, via uplink control information (UCI) signaling.

[0049] At 460, the source gNB 110 transmits a signal including one or more events that trigger event-based reporting, and one or more reserved resources for the UE 105 to report the measurement results.

[0050] Some examples of events include, but are not limited to, the following:

[0051] Event 1—One or more values ​​of RSRP, RSRQ, or SINR from a source gNB beam, a primary cell (PCell) beam, or a primary secondary cell (PSCell) beam meet (e.g., become worse than) one or more configurable thresholds.

[0052] Event 2—One or more values ​​of RSRP, RSRQ, or SINR from a neighbor gNB beam (e.g., the target gNB 115 beam) satisfies one or more configurable offset thresholds (e.g., becomes better than the corresponding values ​​at the source gNB beam, primary cell (PCell) beam, or primary secondary cell (PSCell) beam by some offset).

[0053] Event 3—One or more values ​​of RSRP, RSRQ, or SINR from a neighbor gNB beam (e.g., target gNB 115 beam) meets (e.g., becomes better than) one or more configurable thresholds.

[0054] Event 4—One or more values ​​of RSRP, RSRQ, or SINR from a source gNB beam, a primary cell (PCell) beam, or a primary secondary cell (PSCell) beam satisfies (e.g., becomes worse than) a first settable threshold, and one or more values ​​of RSRP, RSRQ, or SINR from a neighbor gNB beam (e.g., a target gNB 115 beam) satisfies (e.g., becomes better than) a second settable threshold.

[0055] Event 5—One or more values ​​of RSRP, RSRQ, or SINR from a neighbor gNB beam (e.g., target gNB 115 beam) meets (e.g., becomes better than) the corresponding values ​​of the secondary cell (SCell) beam by some offset.

[0056] At 470, the source gNB 110 receives one or more corresponding event-based reports in reserved resources specified by the source gNB 110 at 460 in a PUCCH or PUSCH signal (e.g., L1 signaling). The one or more corresponding event-based reports include data collected according to the configuration at 455. The one or more corresponding event-based reports are triggered by one or more events specified by the source gNB 110 at 460.

[0057] In the event that the source gNB 110 does not reserve resources at 460, then in response to the UE 105 requesting resources for transmitting the one or more corresponding event-based reports to the source gNB 110 via a dedicated or normal scheduling request (SR) (e.g., L2 signaling), the source gNB 110 may receive the one or more corresponding event-based reports via the resources. Otherwise, in response to the UE 105 triggering a contention-based PRACH (e.g., L3 signaling) to transmit the one or more corresponding event-based reports to the source gNB 110, the source gNB 110 thereby receives the one or more corresponding event-based reports.

[0058] Example 450 from the viewpoint of UE 105 :

[0059] At 455, UE 105 receives RRC signaling for configuring CMR and other reporting configurations, which may include, for example Figure 3 A configuration report request 300 for low layer inter-cell mobility management may be requested. The configuration may request L3 measurement results in the report, including but not limited to: L3-RSRP, L3-RSRQ or L3-SINR. The report may be configured to be periodic, semi-persistent or aperiodic, and the report may be configured to be transmitted to the source gNB 110, for example, via uplink control information (UCI) signaling.

[0060] At 460, UE 105 receives a signal including one or more events that trigger event-based reporting, and one or more reserved resources provided by source gNB 110. UE 105 collects measurements according to 455. Examples of events are described above.

[0061] At 465, the UE 105 determines that one or more of the collected measurements meets criteria for one or more events that trigger one or more corresponding event-based reports. The UE 105 collects information for each event-based report accordingly.

[0062] At 470, the UE 105 transmits the one or more corresponding event-based reports using the reserved resources specified by the source gNB 110 in the PUCCH or PUSCH signal (e.g., L1 signaling). In the event that the source gNB 110 does not reserve resources (e.g., at 460), the UE 105 may request resources for transmitting the one or more corresponding event-based reports to the source gNB 110 via a dedicated or normal scheduling request (SR) (e.g., L2 signaling). Otherwise, the UE 105 may trigger a contention-based PRACH (e.g., L3 signaling) to transmit the one or more corresponding event-based reports to the source gNB 110.

[0063] If a collision occurs with a signal when the UE 105 transmits a PUCCH or PUSCH signal carrying collected measurements (eg, event-based reporting), the UE may take various actions as described above.

[0064] In some embodiments, the gNB configures events based on which UE (e.g., which specific UEs) can report L3 results. In some examples, the event is a default event and is not specific to a specific UE. ) If multiple events are configured, the UE can report the multiple events detected. The gNB can configure the UE to determine events based on a single beam (e.g., a single TCI state) or a group of beams (e.g., a group of TCI states). If the gNB configures a group of beams, the measurement results can be based on the minimum, maximum, or average results in the group of beams.

[0065] Figure 5 An example 500 of a gNB triggering and receiving an L1 result report and then performing L3 filtering according to some embodiments of the present disclosure is shown. The gNB uses the filtered data to make a handover decision. For convenience and not limitation, the gNB may be used Figures 1 to 3 , Figure 4A and / or Figure 4B Example 500 is described with reference to the elements of FIG. 500. Example 500 is first described from the perspective of source gNB 110 and then from the perspective of UE 105.

[0066] Example 500 from the viewpoint of source gNB 110 :

[0067] At 510, the source gNB 110 transmits RRC signaling for configuring CMR and other reporting configurations. The RRC signaling may include Figure 3The configuration report request 300 (e.g., reportConfig) for low layer inter-cell mobility management may request L1 measurement results in the report, including but not limited to: L1-RSRP, L1-RSRQ, or L1-SINR. The report may be configured as periodic, semi-persistent, or aperiodic, and the report may be configured to be transmitted to the source gNB 110 via uplink control information (UCI) signaling.

[0068] At 520, the source gNB 110 transmits a signal triggering the UE 105 to respond to the L1 result report based on the report configuration arranged at 510 (e.g., configuring the report request 300). For example, the report can be triggered by an RRC signal, a MAC CE, or a DCI signal.

[0069] At 530, the source gNB 110 receives an L1 result report at L1 via UCI signaling (e.g., via a PUCCH signal or a PUSCH signal). The L1 result report may include, for example, measurement results of TCI states from neighbor cells collected by the UE 105 based on the configuration report request 300 and other configurations at 405. The source gNB 110 also receives an indication as to whether the L1 result report is received from the same TCI state as a previous L1 result report (not shown). For example, if the L1 result report is received from the same TCI state as the previous L1 result report (e.g., the same beam), the source gNB 110 may treat the L1 result report as a continuation of the previous L1 result report. However, if the source gNB 110 instead receives an indication that the L1 result report is received from a different TCI state than the previous L1 result report (e.g., a different beam), the source gNB 110 does not process the L1 result report as a continuation of the previously received L1 result report.

[0070] At 540, the source gNB 110 performs L3 filtering on the one or more L1 result reports received at 530.

[0071] 550 is similar to 530 and 560 is similar to 540. 550 and 560 show reporting and filtering continuing over time.

[0072] Figure 6 An example 600 of L3 filtering of L1 result reports according to some embodiments of the present disclosure is shown. For convenience and not limitation, Figures 1 to 3 , Figure 4A , Figure 4BExample 600 is described using elements of and / or Example 500. For a TCI state, the UE may apply different Rx beams (e.g., downlink receive beams) to different SSB / CSI-RS instances. The TCI state may indicate that the UE may use the same downlink receive beam (e.g., Rx beam) to receive signals A and B, where signal A is a source reference signal (RS) configured in the TCI state and signal B is a target channel to which the TCI state is applied. Therefore, the UE may accompany each L1 result report transmission indication (e.g., a flag) to inform the gNB: whether the L1 result report is received from the same downlink receive beam and L3 filtering should continue; or whether the L1 result report is from a different downlink receive beam and therefore L3 filtering should restart.

[0073] At 610, source gNB 110 receives a first L1 result report at timeslot N and an indication (e.g., Flag=0) that the L1 result report is from the same measurement configuration (e.g., the same downlink receive beam). Since this is the first L1 result report, there is no previous L1 result report. Therefore, source gNB 110 starts L3 filtering based on the L1 result report received in timeslot N.

[0074] At 620, source gNB 110 receives a second L1 result report at timeslot 2N and an indication (e.g., Flag=0) that the second L1 result report is from the same measurement configuration (e.g., the same downlink receive beam) as the previous result report (e.g., the first L1 result report). Therefore, source gNB 110 interprets the second L1 result report as a continuation of the first L1 result report and continues to perform L3 filtering based on the second L1 result report received in timeslot 2N.

[0075] At 630, source gNB 110 receives a third L1 result report at timeslot 3N and an indication (e.g., Flag=1) that the third L1 result report is from a different measurement configuration (e.g., a different downlink receive beam) than the previous L1 result report (e.g., the second L1 result report). Therefore, source gNB 110 interprets the third L1 result report as a new L1 signal and restarts L3 filtering based on the third L1 result report received in timeslot 3N.

[0076] Figure 7 An example 700 of grouping transmission configuration indication (TCI) states into groups corresponding to cells according to some embodiments of the present disclosure is shown. For convenience and not limitation, the Figures 1 to 3 , Figure 4A , Figure 4B , Figure 5 and / or Figure 6In some embodiments, a gNB such as a serving gNB (e.g., source gNB 110) may provide a signal to the source gNB 110 via RRC signaling (e.g., see Figure 3 ) configures N groups of TCI states for a UE (e.g., UE 105). A TCI state within a group may be used for one cell. In some embodiments, the TCI state groups may be explicitly configured, as shown in serving gNB cell 710. TCI group 1 corresponds to physical cell ID = x. Each TCI state in the TCI state (e.g., each beam) may be explicitly configured, such as "TCI 1" at 715a, "TCI 2" at 715b, and so on. TCI group 2 corresponds to physical cell ID = y. TCI group 2 may be implicitly configured. The TCI states in group 1 and group 2 may involve different RRC parameters and configurations because they belong to different cells. The configurations of cell 1 and cell 2 may differ greatly. In particular, group 1 may involve RRC reconfiguration parameters that are different from those of group 2.

[0077] Figure 8 An exemplary gNB method 800 for low-layer inter-cell mobility management according to some embodiments of the present disclosure is shown. For convenience and not limitation, the Figures 1 to 3 , Figure 4A , Figure 4B , Figure 5 , Figure 6 and / or Figure 7 Method 800 is described by using elements of Figure 1 The source gNB 110 or Figure 2 system 200.

[0078] At 810, the system 200 configures a channel state information (CSI) framework. For example, the system 200 may modify RRC layer (e.g., L3) signaling to carry neighbor cell information in reportConfig. In some examples, the system 200 may configure SSB / PBCH and / or CSI-RS from neighbor cells to enable a source gNB (e.g., source gNB 110) to configure CMRs for N groups of beams (e.g., TCI states) for a UE, where each group of beams is associated with a different physical cell.

[0079] At 820, the system 200 enables the collection of measurement results defined in the CSI framework, and measurement reports for L1 and / or L2 signaling. As described above, the system 200 can trigger L3 reporting or schedule events to trigger L3 reporting, which is then transmitted by L1 and / or L2 signaling. The system 200 can also trigger L1 reporting and perform L3 filtering to obtain measurement results.

[0080] At 830, the system 200 associates TCI states (e.g., beams) with various physical cell IDs based on L3 reports and / or L3 filtered L1 reports. In other words, the system 200 classifies the beams into N groups, where each group corresponds to a 5G wireless cell from which the UE has received one or more signals and reported measurement results. For example, the system 200 uses RRC signaling to configure X TCI states, which TCI states may belong to N groups, which may include a first TCI state group corresponding to a serving gNB cell (e.g., a source gNB 110 cell) and a second TCI state group corresponding to a neighbor cell (e.g., a target gNB 115 cell). Subsequently, the system 200 selects a TCI state from the X TCI states using MAC CE signaling. In this example, the system 200 may select a TCI state from the second TCI state group corresponding to the target gNB 115 cell using MAC CE signaling.

[0081] At 850, the system 200 determines whether to switch the 5G wireless communication to a neighbor cell (e.g., to a different beam in the neighbor cell) based on the L3 report and / or the L1 report filtered by L3. When the switch is determined, the method 800 proceeds to 860. Otherwise, the method 800 returns to 830 to continue collecting and evaluating measurement results.

[0082] At 860, the system 200 performs switching based on the TCI state transition. The TCI state group may be associated with a set of RRC parameters configured in the RRC reconfiguration. The gNB may reconfigure these RRC parameters for each TCI state group via RRC signaling or via MAC CE. Given that the MAC CE occurs at L2 and requires less overhead, using MAC CE to reconfigure the RRC parameters for each TCI state group will experience less delay than using RRC signaling at L3.

[0083] The system 200 may perform a TCI state transition via a MAC CE or through DCI signaling. In some embodiments, the system 200 may transmit a new TCI state from a different group (e.g., a different 5G wireless cell, such as a neighbor cell) to the UE via a MAC CE (e.g., L2 signaling). After receiving the new TCI state via the MAC CE, the UE sends an ACK for the MAC CE and waits for a given number of time slots (or milliseconds) before the UE can start communicating with the new cell, which corresponds to the physical cell ID associated with the new TCI state.

[0084] In some embodiments, the system 200 may transmit new TCI states from different groups (e.g., different 5G wireless cells, such as neighbor cells) to the UE via DCI signaling (e.g., L1 signaling). The DCI signaling may be: i) downlink allocation, ii) uplink grant, or iii) dedicated DCI format. If a DCI downlink allocation is used, the format may be as follows: DCI format 1_0 or DCI format 1_1. After receiving the new TCI state via the DCI downlink allocation, the UE sends an ACK for the DCI downlink allocation and waits for a given number of time slots (or milliseconds) to pass before the UE starts communicating with the new cell, which corresponds to the physical cell ID associated with the new TCI state. If a DCI uplink grant is used, the format may be as follows: DCI format 0_0 or DCI format 0_1. After receiving the new TCI state via the DCI uplink grant, the UE waits for a given number of time slots (or milliseconds) after the UE sends a PUSCH signal, and then the UE may start communicating with the new cell, which corresponds to the physical cell ID associated with the new TCI state. Finally, if a dedicated DCI format is used, the format may be as follows: DCI format 0_0 or DCI format 0_1. After receiving the new TCI state via the dedicated DCI format, the UE waits a given number of time slots (or milliseconds) after the time slot carrying the dedicated DCI format has passed, and the UE may then begin communicating with the new cell corresponding to the physical cell ID associated with the new TCI state.

[0085] Fig. 9 900 is a method of an exemplary user equipment (UE) for low-layer inter-cell mobility management according to some embodiments of the present disclosure. For convenience and not limitation, the system 900 may be described using elements of one or more of the previous figures. For example, the method 800 may be performed by Figure 1 UE 105 or Figure 2 Executed by system 200.

[0086] At 910, the system 200 receives instructions from the source gNB to report measurement results.

[0087] At 920, the system 200 transmits a report based on the instructions. For example, the system 200 may transmit the report based on a trigger signal from the source gNB, or the system 200 may transmit the report based on an event that triggers the report. The report includes measurement results corresponding to various TCI states (e.g., beams) of the 5G wireless cell.

[0088] At 930, the system 200 receives a new TCI state via MAC CE or DCI signaling.

[0089] At 940, the system 200 acknowledges receipt of the MAC CE or DCI signaling and waits for an appropriate amount of time slots or time to pass before communicating with the new cell corresponding to the physical cell ID associated with the new TCI state.

[0090] At 950, the system 200 starts a confirmation timer. The confirmation timer is a mechanism by which the system 200 can revert to communicating with the previous serving cell if handover to a new cell fails.

[0091] At 960, the system 200 determines whether a dedicated PDCCH signal is received from the new cell. When a dedicated PDCCH signal is received from the new cell, the handover is successful and the method 900 proceeds to 970. Otherwise, the handover fails and the method 900 proceeds to 980.

[0092] The handover is successful at 970. The system 200 stops the confirmation timer and applies a new timing advance group (TAG) associated with the new cell.

[0093] At 980, the handover has failed and the system 200 reverts to communicating with the previous serving cell.

[0094] You can use, for example, Fig.10 The computer system 1000 shown may be any known computer system capable of performing the functions described herein. For example, and without limitation, Figure 2 System 200, Figure 8 800 and Fig. 9 The method 900 (and / or other devices and / or components shown in the figure) can be implemented using the computer system 1000 or a portion thereof.

[0095] Computer system 1000 includes one or more processors (also referred to as central processing units or CPUs), such as processor 1004. Processor 1004 is connected to a communication infrastructure or bus 1006. One or more processors 1004 may each be a graphics processing unit (GPU). In an embodiment, a GPU is a processor of a dedicated electronic circuit designed to process mathematically intensive applications. A GPU may have an efficient parallel structure for processing large blocks of data in parallel, such as mathematically intensive data commonly used in computer graphics applications, images, videos, etc.

[0096] The computer system 1000 also includes user input / output devices 1003, such as a monitor, keyboard, pointing device, etc., that communicate with the communication infrastructure 1006 through the user input / output interface 1002. The computer system 1000 also includes a main memory or primary storage 1008, such as a random access memory (RAM). The main memory 1008 may include one or more levels of cache. The main memory 1008 has control logic components (e.g., computer software) and / or data stored therein.

[0097] The computer system 1000 may also include one or more secondary storage devices or memories 1010. The secondary storage 1010 may include, for example, a hard disk drive 1012 and / or a removable storage device or drive 1014. The removable storage drive 1014 may be a floppy disk drive, a tape drive, an optical drive, an optical storage device, a tape backup device, and / or any other storage device / drive.

[0098] The removable storage drive 1014 may interact with a removable storage unit 1018. The removable storage unit 1018 includes a computer usable or readable storage device having computer software (control logic) and / or data stored therein. The removable storage unit 1018 may be a floppy disk, a magnetic tape, a compact disk, a DVD, an optical storage disk, and / or any other computer data storage device. The removable storage drive 1014 reads from and / or writes to the removable storage unit 1018 in a well-known manner.

[0099] According to some embodiments, secondary storage 1010 may include other devices, means, or other methods for allowing computer system 1000 to access computer programs and / or other instructions and / or data. Such devices, means, or other methods may include, for example, a removable storage unit 1022 and an interface 1020. Examples of removable storage unit 1022 and interface 1020 may include a program cartridge and cartridge interface (such as found in video game devices), a removable memory chip (such as an EPROM or PROM) and associated socket, a memory stick and USB port, a memory card and associated memory card slot, and / or any other removable storage unit and associated interface.

[0100] The computer system 1000 may also include a communication or network interface 1024. The communication interface 1024 enables the computer system 1000 to communicate and interact with any combination of remote devices, remote networks, remote entities, etc. (individually and collectively referenced by reference numeral 1028). For example, the communication interface 1024 may allow the computer system 1000 to communicate with the remote device 1028 via a communication path 1026, which may be wired and / or wireless and may include any combination of a LAN, a WAN, the Internet, etc. Control logic components and / or data may be transmitted to and from the computer system 1000 via the communication path 1026.

[0101] The operations in the foregoing embodiments can be implemented in various configurations and architectures. Thus, some or all of the operations in the foregoing embodiments can be performed in hardware, software, or in both hardware and software. In some embodiments, a tangible, non-transient device or article includes a tangible, non-transient computer-usable or readable medium on which a control logic component (software) is stored, also referred to herein as a computer program product or program storage device. This includes but is not limited to computer system 1000, main memory 1008, auxiliary memory 1010, and removable storage units 1018 and 1022, as well as tangible articles embodying any combination of the foregoing. When executed by one or more data processing devices (such as computer system 1000), this control logic component causes such data processing devices to operate as described herein.

[0102] Based on the teachings contained in this disclosure, it will be apparent to those skilled in the relevant art how to use the Fig.10 The embodiments of the present disclosure may be made and used with data processing devices, computer systems, and / or computer architectures other than those shown. In particular, the embodiments may operate with software, hardware, and / or operating system implementations other than those described herein.

[0103] It should be understood that the Detailed Description section, rather than the Summary and Abstract sections, is intended to be used to interpret the claims. The Summary and Abstract sections may set forth one or more but not all exemplary embodiments of the present disclosure as contemplated by the inventors, and thus, are not intended to limit the present disclosure or the appended claims in any way.

[0104] Although the present disclosure has been described herein with reference to exemplary embodiments of exemplary fields and applications, it should be understood that the present disclosure is not limited thereto. Other embodiments and modifications are possible and within the scope and essence of the present disclosure. For example, and without limiting the generality of this paragraph, the embodiments are not limited to the software, hardware, firmware, and / or entities shown in the figures and / or described herein. In addition, the embodiments (whether or not explicitly described herein) have significant practicality for fields and applications outside the examples described herein.

[0105] Embodiments have been described herein by means of functional building blocks that illustrate implementations of specific functions and relationships thereof. For ease of description, the boundaries of these functional building blocks have been arbitrarily defined herein. Alternative boundaries may be defined as long as the specified functions and relationships (or their equivalents) are properly performed. In addition, alternative embodiments may perform functional blocks, steps, operations, methods, etc., in an order different from that described herein.

[0106] References herein to "one embodiment," "an embodiment," "an exemplary embodiment," or similar phrases indicate that the described embodiment may include a particular feature, structure, or characteristic, but every embodiment may not necessarily include the particular feature, structure, or characteristic. Furthermore, such phrases do not necessarily refer to the same embodiment. Furthermore, when a particular feature, structure, or characteristic is described in conjunction with an embodiment, it is within the knowledge of those skilled in the relevant art to incorporate such feature, structure, or characteristic into other embodiments, whether or not explicitly mentioned or described herein.

[0107] The breadth and scope of the present disclosure should not be limited by any of the above-described exemplary embodiments, but should be defined only in accordance with the following claims and their equivalents.

[0108] As described above, various aspects of the present technology may include collecting and using data available from various sources, thereby (for example) improving or enhancing functionality. The present disclosure contemplates that, in some instances, these collected data may include personal information data that uniquely identifies or can be used to contact or locate a specific person. Such personal information data may include demographic data, location-based data, phone numbers, email addresses, Twitter IDs, home addresses, data or records related to the user's health or fitness level (e.g., vital sign measurements, medication information, exercise information), date of birth, or any other identifying information or personal information. The present disclosure recognizes that the use of such personal information data in the present technology can be used to benefit users.

[0109] The present disclosure envisions that entities responsible for collecting, analyzing, disclosing, transmitting, storing or otherwise using such personal information data will comply with established privacy policies and / or privacy practices. Specifically, such entities should implement and adhere to privacy policies and practices that are recognized as meeting or exceeding industry or government requirements for maintaining the privacy and security of personal information data. Such policies should be easily accessible to users and should be updated as the collection and / or use of data changes. Personal information from users should be collected for the legitimate and reasonable purposes of the entity and not shared or sold outside of these legitimate uses. In addition, such collection / sharing should only be done after receiving the user's informed consent. In addition, such entities should consider taking any necessary steps to defend and safeguard access to such personal information data and ensure that others who have access to personal information data comply with their privacy policies and processes. In addition, such entities may subject themselves to third-party assessments to demonstrate their compliance with widely accepted privacy policies and practices. In addition, policies and practices should be adjusted to specific types of personal information data collected and / or accessed, and to applicable laws and standards that include specific considerations of jurisdiction. For example, in the United States, the collection or access of certain health data may be governed by federal and / or state laws, such as the Health Insurance Portability and Accountability Act (HIPAA), while health data in other countries may be subject to other regulations and policies and should be handled accordingly. Therefore, different privacy practices should be maintained in each country for different types of personal data.

[0110] Regardless of the foregoing, the present disclosure also contemplates implementation schemes in which users selectively block the use or access of personal information data. That is, the present disclosure contemplates providing hardware elements and / or software elements to prevent or block access to such personal information data. For example, the present technology may be configured to allow users to selectively participate in "opt-in" or "opt-out" of collecting personal information data at any time during (for example) registration for a service or thereafter. In addition to providing "opt-in" and "opt-out" options, the present disclosure contemplates providing notifications related to access or use of personal information. For example, a user may be notified that their personal information data will be accessed when downloading an application, and then reminded again just before the personal information data is accessed by the application.

[0111] In addition, it is an object of the present disclosure that personal information data should be managed and processed to minimize the risk of unintentional or unauthorized access or use. Risks can be minimized by limiting data collection and deleting data once it is no longer needed. In addition, and when applicable, including in certain health-related applications, data de-identification can be used to protect the privacy of users. De-identification can be facilitated by removing specific identifiers (e.g., date of birth, etc.), controlling the amount or specificity of stored data (e.g., collecting location data at the city level rather than at the address level), controlling how data is stored (e.g., aggregating data between users), and / or other methods when appropriate.

[0112] Thus, while the present disclosure may broadly cover the use of personal information data to implement one or more of the various disclosed embodiments, the present disclosure also contemplates that various embodiments may also be implemented without access to such personal information data. That is, various embodiments of the present technology will not fail to function properly due to the lack of all or part of such personal information data.

Claims

1. A serving base station BS, comprising: a transceiver configured to transmit and receive wireless communications; a processor coupled to the transceiver and configured to: Determine to use the synchronization signal block SSB or channel state information reference signal CSI-RS measurement result performed on the neighboring cell as the channel measurement resource CMR in reportConfig; Transmitting the reportConfig to a user equipment UE using the transceiver; collecting data including a physical cell ID of the neighbor cell based at least on the reportConfig; Configuring N groups of transmission configuration indication (TCI) states for the UE, wherein a first group of the N groups corresponds to a cell of the serving BS, and a second group of the N groups corresponds to the physical cell ID of the neighbor cell; deciding to perform a handover based at least on the data; as well as The switching is performed from a TCI state in the first group to a TCI state in the second group.

2. The serving BS according to claim 1, wherein in order to collect data, the processor is further configured to: Triggering layer 3L3 result reporting; and The L3 result report is received from the UE via an uplink control information (UCI) signal, wherein the L3 result report includes: L3-reference signal received power RSRP, L3-reference signal received quality RSRQ or L3-signal to interference and noise ratio SINR.

3. The serving BS according to claim 2, wherein in order to trigger the L3 result report, the processor is configured to: Use radio resource control RRC signaling, medium access control MAC control element CE signaling or downlink control information DCI signaling. 4 . The serving BS according to claim 2 , wherein the UCI signal comprises a physical uplink control channel (PUCCH) signal or a physical uplink shared channel (PUSCH) signal.

5. The serving BS according to claim 1, wherein the processor is further configured to: Identify events that trigger event-based reporting; reserving resources in a physical uplink control channel (PUCCH) signal or a physical uplink shared channel (PUSCH) signal to enable the UE to provide the event-based report; and The event triggering the event-based reporting and the reserved resources are transmitted to the UE using the transceiver.

6. The serving BS according to claim 5, wherein the processor is further configured to: The event-based report is received from the UE via an uplink control information (UCI) signal, wherein the event-based report comprises: L3-reference signal received power RSRP, L3-reference signal received quality RSRQ or L3-signal to interference and noise ratio SINR.

7. The serving BS according to claim 1, wherein the processor is further configured to: Trigger layer 1L1 result report; and The L1 result report is received from the UE via an uplink control information (UCI) signal, wherein the L1 result report includes: L1-reference signal received power RSRP, L1-reference signal received quality RSRQ or L1-signal to interference and noise ratio SINR.

8. The serving BS according to claim 7, wherein the processor is further configured to: receiving an indication of whether the L1 results report is received from the same downlink receive beam as a previous L1 results report; determining, based on the indication, that the L1 result report is from the same downlink receive beam as the previous L1 result report; performing L3 filtering based on the previous L1 result report and the L1 result report; as well as The N sets of TCI states are configured based at least on a result of the L3 filtering, and wherein a decision to perform the switching is based at least on the result of the L3 filtering.

9. The serving BS according to claim 7, wherein the processor is further configured to: receiving an indication of whether the L1 results report is received from the same downlink receive beam as a previous L1 results report; determining, based on the indication, that the L1 result report is from a different downlink receive beam than the previous L1 result report; performing L3 filtering on the L1 result report; as well as The N sets of TCI states are configured based at least on a result of the L3 filtering, and wherein a decision to perform the switching is based at least on the result of the L3 filtering.

10. The serving BS of claim 1, wherein in order to perform the handover, the processor is configured to: A medium access control MAC control element CE is used to transition from a TCI state in the first group to a TCI state in the second group.

11. The serving BS of claim 1 , wherein in order to perform the handover, the processor is configured to: A downlink control information (DCI) signal is used to transition from a TCI state in the first group to a TCI state in the second group, wherein the DCI signal includes a downlink assignment, an uplink grant, or a dedicated DCI format.

12. A user equipment UE, comprising: a transceiver configured to transmit and receive wireless communications; a processor coupled to the transceiver and configured to: receiving, via the transceiver, from a serving base station BS, a resportConfig having an instruction for reporting a measurement result corresponding to a synchronization signal block SSB or a channel state information reference signal CSI-RS measurement result performed on a neighboring cell as a channel measurement resource CMR; transmitting data including a physical cell ID of a neighbor cell to the serving BS via the transceiver based at least on the reportConfig; After transmitting the data, receiving a new transmission configuration indication TCI state of the neighbor cell from the serving BS via a medium access control MAC control element CE or downlink control information DCI; Transitioning from the TCI of the cell of the serving BS to the new TCI state; and Communicating with the neighbor cell via the new TCI state via the transceiver.

13. The UE according to claim 12, wherein the instruction comprises a request for a layer 3 L3 result report, and the processor is configured to: The L3 result report is transmitted using the transceiver via a physical uplink control channel (PUCCH) signal or a physical uplink shared channel (PUSCH) signal.

14. The UE according to claim 12, wherein the instruction includes an event triggering event-based reporting and reserved resources, and the processor is configured to: determining that the event is triggered; and The event-based report is transmitted according to the reserved resources via a physical uplink control channel (PUCCH) signal or a physical uplink shared channel (PUSCH) signal using the transceiver.

15. The UE according to claim 14, wherein the processor is further configured to: Determining that the PUCCH signal or the PUSCH signal conflicts with a second signal; discarding the PUCCH signal or the PUSCH signal; and Then, the PUCCH signal or the PUSCH signal is retransmitted.

16. The UE according to claim 15, wherein the second signal is: a physical random access channel PRACH signal, a scheduling request SR signal or a hybrid automatic repeat request HARQ-ACK signal.

17. The UE of claim 12, wherein the instruction comprises an event that triggers event-based reporting, and the processor is configured to: determining that the event is triggered; and Resources for transmitting the event-based report are requested by a dedicated or normal scheduling request SR.

18. The UE of claim 12, wherein in order to communicate with the neighbor cell via the new TCI state, the processor is configured to: Start confirmation timer; receiving a dedicated physical downlink control channel (PDCCH) from the neighbor cell via the new TCI state; stopping the acknowledgement timer in response to the PDCCH; and A new timing advance group TAG corresponding to the neighbor cell is applied before transmitting an uplink signal.

19. A method for a serving base station BS, comprising: Define reportConfig including physical cell IDs of neighbor cells; Transmitting the reportConfig to the user equipment UE; Receive a result report based on the reportConfig; Grouping a first set of transmission configuration indication (TCI) states corresponding to the cell of the serving BS and a second set of TCI states corresponding to the neighboring cell; Deciding to perform a handover based at least on the result report; as well as The switching is performed from a TCI state in the first group to a TCI state in the second group.

20. The method of claim 19, wherein said performing said switching comprises: A medium access control MAC control element CE or a downlink control information DCI signal is used to transition from the TCI state in the first group to the TCI state in the second group.

Images