Cell switch method and apparatus

Abstract

Provided in the embodiments of the present application are a cell switch method and apparatus. The method comprises: a terminal device receiving candidate configurations and execution conditions which are sent by a network device; and the terminal device performing a first behavior when a first condition is met, wherein the first behavior comprises applying a target configuration, but does not comprise executing a second random access procedure, and the target configuration is a configuration among the candidate configurations sent by the network device meeting the first condition. According to the embodiments of the present application, a terminal device can implement LTM execution or CHO execution triggered by the terminal device, and can obtain corresponding information to perform corresponding processing, thereby avoiding or reducing mobility failures or wireless link failures due to the fact that a trigger command of a network device cannot be received, and improving the robustness.

Description

Method and device for cell change Technical Field

[0001] The embodiments of the present application relate to the field of communication technologies. Background Art

[0002] Network-controlled mobility applies to connected terminals and can be categorized into two types: cell-level mobility and beam-level mobility. Figure 1 illustrates an inter-cell mobility scenario. As shown in Figure 1, when a terminal moves from one cell's coverage area to another, a serving cell change is required at some point.

[0003] Currently, serving cell changes are triggered by L3 (Layer 3) measurements and completed via RRC (Radio Resource Control) signaling. Reconfiguration with Synchronization is also being triggered for PCell (Primary Cell) and PSCell (Special Cell) changes, as well as the release of SCells (Secondary Cells) when applicable. Cell-level mobility is now triggered by explicit RRC signaling, known as handover. The RRC-triggered handover mechanism requires the UE (also known as user equipment, terminal device, terminal, user) to at least reset the MAC (Media Access Control) entity and re-establish the RLC (Radio Link Control). RRC-managed handovers are supported with and without re-establishment of the PDCP (Packet Data Convergence Protocol) entity. For DRBs (Data Radio Bearers) using RLC AM (RLC Acknowledged Mode), PDCP can either re-establish with security key update or initiate data recovery without key update. For DRBs using RLC UM (RLC Unacknowledged Mode), PDCP can re-establish with security key update or remain unchanged without key update. For SRBs (Signaling Radio Bearers), PDCP can remain unchanged without key update, discard stored PDCP PDUs / SDUs, or re-establish with security key update.

[0004] For RRC-triggered handover mechanisms, all cases involve a complete L2 (and L1) reset, resulting in longer latency, greater overhead, and longer disruption than beam switching mobility. The goal of L1 (Layer 1) / L2 (Layer 2) mobility enhancements is to ensure that serving cell changes via L1 / L2 signaling reduce latency, overhead, and disruption.

[0005] LTM (L1 / L2 Triggered Mobility) is a process in which the gNB (also known as network equipment, network, base station, etc.) receives Layer 1 measurement reports from the UE. Based on these reports, the gNB changes the UE's serving cell via a cell change command sent via a MAC Control Element (MAC CE). The MAC-triggered cell change mechanism (i.e., LTM cell switch) requires the UE to at least reset the MAC entity. The RLC handling depends on the network configuration.

[0006] Figure 2 is a schematic diagram of the overall LTM process. The basic process on the air interface is applicable to MCG LTM (Master Cell Group LTM) or SCG LTM (Secondary Cell Group LTM). As shown in Figure 2, the process includes the following steps:

[0007] 1. The UE sends a MeasurementReport message to the gNB, in which the gNB-CU decides to configure LTM and initiates LTM preparation.

[0008] 2. The gNB sends an RRCReconfiguration message to the UE including the LTM candidate configuration.

[0009] 3. The UE stores the LTM candidate configuration and sends an RRCReconfigurationComplete message to the gNB.

[0010] 4a. Before receiving the cell change command, the UE performs DL (Downlink, downlink, referred to as downlink) synchronization with the candidate cell;

[0011] 4b. When UE-based TA (Timing Advance) measurement is configured, the UE obtains the TA value of the candidate cell through measurement;

[0012] It is worth noting that before receiving the cell change command, the UE performs an early TA acquisition with the candidate cell at the request of the network. This is done through CFRA (Contention Free Random Access), which is triggered by the PDCCH (Physical Downlink Control Channel) command of the source cell, and then the UE sends a preamble to the indicated candidate cell, as shown in Figure 3, which is a schematic diagram of the random access process. In order to minimize the data interruption of the source cell caused by the CFRA to the candidate cell, the UE does not receive a random access response from the network for the purpose of obtaining the TA value of the candidate cell indicated in the cell change command. The UE does not maintain the TA timer of the candidate cell, but relies on the network implementation to ensure the validity of the TA.

[0013] 5. The UE performs L1 measurements on the configured candidate cells and sends an L1 measurement report to the gNB. L1 measurements should be performed whenever RRC reconfiguration (step 2) is applicable.

[0014] 6. The gNB decides to perform a cell handover to a target cell and sends a MAC CE triggering a cell handover including the candidate configuration index of the target cell. The UE switches to the target cell and applies the configuration indicated by the candidate configuration index.

[0015] 7. If the UE does not have a valid TA for the target cell, the UE performs a random access procedure to the target cell;

[0016] 8. The UE completes the LTM cell handover process by sending an RRCReconfigurationComplete message to the target cell.

[0017] It is worth noting that if the UE performs a random access procedure in step 7, the UE considers the LTM cell handover to have been successfully completed when the random access procedure is successfully completed. For RACH-less LTM, that is, when step 7 is not performed, the UE considers the LTM cell handover to have been successfully completed when it determines that the network has successfully received its first UL data.

[0018] Furthermore, for the random access procedure on LTM candidate cells used for early UL TA acquisition, a CFRA triggered by a PDCCH order is used. As shown in Figure 3, the UE sends MSG1 (Message 1) to the cell and does not listen for responses from the cell. To support UE power ramping, the UE can retransmit MSG1 as instructed by the network.

[0019] In addition, for subsequent LTM, the LTM candidate configuration provided in step 2 can be used to perform steps 4 to 8 multiple times, that is, the subsequent LTM is achieved by repeating the early synchronization, LTM cell switching execution and LTM cell switching completion steps and not releasing other LTM candidate configurations after each LTM cell switching is completed.

[0020] The above is a cell change triggered by the network.

[0021] For terminal-initiated cell changes, for UEs in the RRC_CONNECTED state, terminal-triggered mobility includes at least conditional reconfiguration and RLF (Radio Link Failure) or cell failure recovery on the MCG. Conditional reconfiguration includes conditional handover (CHO) and conditional PSCell addition / change (CPAC).

[0022] Among them, for conditional reconfiguration:

[0023] The network configures one or more candidate target special cells for the terminal in a conditional reconfiguration. The terminal evaluates the conditions of each configured candidate target special cell and applies the associated conditional reconfiguration to the target cell that meets the associated execution conditions.

[0024] FIG4 is a schematic diagram of UE behavior for conditional reconfiguration.

[0025] As shown in Figure 4, based on a received ConditionalReconfiguration IE, the UE performs the following actions:

[0026] If ConditionalReconfiguration includes condReconfigToRemoveList: execute the conditional reconfiguration removal process;

[0027] If ConditionalReconfiguration includes condReconfigToAddModList: Perform conditional reconfiguration addition / modification.

[0028] Among them, conditional reconfiguration additions / modifications include:

[0029] For each condReconfigId received in condReconfigToAddModList, the UE shall:

[0030] If an entry matching condReconfigId exists in condReconfigToAddModList in VarConditionalReconfig:

[0031] If the entry in condReconfigToAddModList includes a condExecutionCond, condExecutionCondSCG, or condExecutionCondPSCell: replace the entry with the received value of condReconfigId;

[0032] If the entry in condReconfigToAddModList includes a condRRCReconfig: replace the entry with the received value of condReconfigId;

[0033] Otherwise: add a new entry in VarConditionalReconfig for this condReconfigId; perform conditional reconfiguration evaluation.

[0034] Among them, conditional reconfiguration evaluation includes:

[0035] UE will:

[0036] For each condReconfigId in VarConditionalReconfig:

[0037] A cell having a Physical Cell Identity (PCI) matching the value indicated in ServingCellConfigCommon in reconfigurationWithSync in the received condRRCReconfig is considered an applicable cell;

[0038] For each measId included in the measIdList in the VarMeasConfig indicated in the condExecutionCond associated with the condReconfigId:

[0039] If the entry conditions applicable to this event associated with condReconfigId, i.e. the events corresponding to the condEventId(s) of the corresponding condTriggerConfig in VarConditionalReconfig, are met for all measurements after layer 3 filtering for the applicable cell, during the corresponding timeToTrigger defined for this event in VarConditionalReconfig: the event associated with measId is considered met;

[0040] If the leaving condition applicable to the event associated with condReconfigId, i.e. the event corresponding to the condEventId(s) of the corresponding condTriggerConfig in VarConditionalReconfig, is satisfied for all measurements after layer 3 filtering for the applicable cell, the corresponding timeToTrigger period defined for this event in VarConditionalReconfig: the event associated with measId is considered not satisfied;

[0041] If for a target candidate cell in the stored condRRCReconfig, all events associated with measId(s) in condTriggerConfig are satisfied:

[0042] The target candidate cell associated with condReconfigId in the stored condRRCReconfig is considered to be a triggered cell;

[0043] Initiates conditional reconfiguration execution.

[0044] Among them, the conditional reconfiguration execution includes:

[0045] UE will:

[0046] If there is a triggered cell: selecting a triggered cell as a selected cell for conditional reconfiguration execution;

[0047] For the selected cell for conditional reconfiguration execution, the stored condRRCReconfig of this selected cell is applied.

[0048] The network provides the configuration parameters of the target special cell in the ConditionalReconfiguration IE. In NR-DC, the UE may receive two independent conditionalReconfigurations: one conditionalReconfiguration associated with the MCG, that is, included in the RRCReconfiguration message received via SRB1; one conditionalReconfiguration associated with the SCG, that is, included in the RRCReconfiguration message received via SRB3, or included in an RRCReconfiguration message encapsulated in an RRCReconfiguration message received via SRB1. In this case, the UE maintains two independent VarConditionalReconfigs, one associated with each conditionalReconfiguration; unless otherwise explicitly stated, the UE performs all the above processes independently for each conditionalReconfiguration and the associated VarConditionalReconfig; for VarConditionalReconfigs associated with the same cell group, the UE performs the measurement process.

[0049] As mentioned previously, conditional reconfiguration includes two scenarios: conditional handover (CHO) and conditional PSCell change. Conditional handover is defined as a handover executed by the UE when one or more handover execution conditions are met. The UE begins evaluating these execution conditions upon receiving the CHO configuration and ceases evaluating them once the handover is executed.

[0050] The following principles apply to CHO:

[0051] The CHO configuration includes the configuration of the CHO candidate cells generated by the candidate gNB(s) and the execution conditions generated by the source gNB;

[0052] An execution condition can include one or two trigger conditions (CHO events A3 / A5). The CHO execution condition only supports a single RS (Reference Signal) type and a single candidate cell, and can be configured with up to two different trigger quantities (such as Reference Signal Received Power RSRP and Reference Signal Received Quality RSRQ, RSRP and Signal to Interference and Noise Ratio SINR, etc.).

[0053] When a HO (handover) command is received (without CHO configuration) before any CHO execution conditions are met, the UE performs the HO procedure regardless of any CHO configuration received previously;

[0054] When performing CHO, that is, from the time the UE starts synchronizing with the target cell, the UE does not monitor the source cell.

[0055] The process of CHO in AMF (Access and Mobility Management Function) is shown in Figure 5. The specific process can be referred to related technologies and will not be repeated here.

[0056] It should be noted that the above introduction to the technical background is merely intended to provide a clear and complete description of the technical solutions of this application and facilitate understanding by those skilled in the art. Simply because these solutions are described in the background technology section of this application, it should not be assumed that the above technical solutions are well known to those skilled in the art.

[0057] Summary of the Invention

[0058] The inventors discovered that LTM, introduced in Rel-18 (Release 18), provides a short interruption time. However, LTM requires pre-signaling interaction with the source cell, including UE reporting of Layer 1 measurement results and LTM cell change commands sent by the source cell for LTM execution. This means that the terminal device must wait for a command from the network to trigger LTM. In the event of a sudden change in the radio environment, the terminal device may not receive this command in time, resulting in handover failure or radio link failure, making it less robust than the Layer 3-based mobility process.

[0059] To address at least one of the above problems or other similar problems, embodiments of the present application provide a method and apparatus for cell change.

[0060] According to one aspect of an embodiment of the present application, a cell change apparatus is configured in a terminal device, wherein the apparatus includes:

[0061] a receiving unit configured to receive candidate configurations and execution conditions sent by a network device;

[0062] A processing unit, which performs a first behavior when a first condition is met, wherein the first behavior includes applying a target configuration and does not include performing a second random access process, and the target configuration is one of the candidate configurations sent by the network device that meets the first condition.

[0063] One of the beneficial effects of the embodiments of the present application is that: according to the embodiments of the present application, the terminal device can realize LTM execution or CHO execution triggered by the terminal device, and can obtain corresponding information for corresponding processing, thereby avoiding or reducing mobility failure or wireless link failure caused by the inability to receive the trigger command of the network device, and improving robustness.

[0064] With reference to the following description and accompanying drawings, specific embodiments of the present application are disclosed in detail, indicating the manner in which the principles of the present application can be employed. It should be understood that the embodiments of the present application are not limited in scope. Within the spirit and scope of the appended claims, the embodiments of the present application include many variations, modifications and equivalents.

[0065] Features described and / or illustrated with respect to one embodiment may be used in the same or similar manner in one or more other embodiments, combined with features in other embodiments, or substituted for features in other embodiments.

[0066] It should be emphasized that the term "include / comprising" when used herein refers to the presence of features, integers, steps or components, but does not exclude the presence or addition of one or more other features, integers, steps or components. BRIEF DESCRIPTION OF THE DRAWINGS

[0067] The elements and features described in one figure or one embodiment of the present application can be combined with the elements and features shown in one or more other figures or embodiments. In addition, in the accompanying drawings, similar reference numerals represent corresponding parts in several figures and can be used to indicate corresponding parts used in more than one embodiment.

[0068] FIG1 is a schematic diagram of an inter-cell mobility scenario;

[0069] FIG2 is a schematic diagram of the overall process of LTM;

[0070] FIG3 is a schematic diagram of a random access process;

[0071] FIG4 is a schematic diagram of UE behavior for conditional reconfiguration;

[0072] FIG5 is a schematic diagram of the process of CHO in AMF;

[0073] FIG6 is a schematic diagram of RLF / HOF recovery;

[0074] FIG7 is a schematic diagram of a cell change method according to an embodiment of the present application;

[0075] FIG8 is a schematic diagram of a signaling process of a method according to an embodiment of the present application;

[0076] FIG9 is a schematic diagram of a configuration method according to an embodiment of the present application;

[0077] FIG10 is a schematic diagram of an apparatus for cell change according to an embodiment of the present application;

[0078] FIG11 is a schematic diagram of a configuration device according to an embodiment of the present application;

[0079] FIG12 is a schematic diagram of a communication system according to an embodiment of the present application;

[0080] FIG13 is a schematic diagram of a terminal device according to an embodiment of the present application;

[0081] FIG14 is a schematic diagram of a network device according to an embodiment of the present application. DETAILED DESCRIPTION

[0082] The above and other features of the present application will become apparent through the following description with reference to the accompanying drawings. In the description and the accompanying drawings, specific embodiments of the present application are disclosed in detail, which illustrate some embodiments in which the principles of the present application can be adopted. It should be understood that the present application is not limited to the described embodiments. On the contrary, the present application includes all modifications, variations and equivalents that fall within the scope of the appended claims.

[0083] In the embodiments of the present application, the terms "first", "second", etc. are used to distinguish different elements from the name, but do not indicate the spatial arrangement or temporal order of these elements, and these elements should not be limited by these terms. The term "and / or" includes any one and all combinations of one or more of the associated listed terms. The terms "comprising", "including", "having", etc. refer to the presence of the stated features, elements, components or components, but do not exclude the presence or addition of one or more other features, elements, components or components.

[0084] In the embodiments of this application, the singular forms "a," "the," etc. include plural forms and should be broadly understood to mean "a" or "a type" rather than being limited to "one." Furthermore, the term "said" should be understood to include both singular and plural forms, unless the context clearly indicates otherwise. Furthermore, the term "according to" should be understood to mean "at least in part based on...", and the term "based on" should be understood to mean "at least in part based on...", unless the context clearly indicates otherwise.

[0085] In the embodiments of the present application, the term "communication network" or "wireless communication network" may refer to a network that complies with any of the following communication standards, such as Long Term Evolution (LTE), enhanced Long Term Evolution (LTE-A, LTE-Advanced), Wideband Code Division Multiple Access (WCDMA), High-Speed ​​Packet Access (HSPA), etc.

[0086] Furthermore, communication between devices in the communication system may be carried out according to communication protocols of any stage, for example, including but not limited to the following communication protocols: 1G (generation), 2G, 2.5G, 2.75G, 3G, 4G, 4.5G and 5G, New Radio (NR), etc., and / or other communication protocols currently known or to be developed in the future.

[0087] In the embodiments of the present application, the term "network device" refers to, for example, a device in a communication system that connects a terminal device to the communication network and provides services to the terminal device. Network devices may include, but are not limited to, the following devices: base station (BS), access point (AP), transmission reception point (TRP), broadcast transmitter, mobile management entity (MME), gateway, server, radio network controller (RNC), base station controller (BSC), etc.

[0088] Base stations may include, but are not limited to, NodeBs (NBs), evolved NodeBs (eNodeBs or eNBs), and 5G base stations (gNBs), among others. They may also include remote radio heads (RRHs), remote radio units (RRUs), relays or low-power nodes (e.g., femeto, pico, etc.), IAB (Integrated Access and Backhaul) nodes, IAB-DUs, or IAB-donors. The term "base station" may include some or all of these functions, and each base station may provide communication coverage for a specific geographic area. The term "cell" may refer to a base station and / or its coverage area, depending on the context in which the term is used. The terms "cell" and "base station" are interchangeable to avoid confusion.

[0089] In the embodiments of the present application, the term "user equipment" (UE) or "terminal equipment" (TE) refers to, for example, a device that accesses a communication network through a network device and receives network services. A terminal device can be fixed or mobile and may also be referred to as a mobile station (MS), a terminal, a subscriber station (SS), an access terminal (AT), an IAB-MT (Mobile Terminal), a station, and so on.

[0090] Terminal devices may include, but are not limited to, the following devices: cellular phones, personal digital assistants (PDAs), wireless modems, wireless communication devices, handheld devices, machine-type communication devices, laptop computers, cordless phones, smartphones, smart watches, digital cameras, etc.

[0091] For another example, in scenarios such as the Internet of Things (IoT), the terminal device can also be a machine or device for monitoring or measurement, including but not limited to: machine type communication (MTC) terminal, vehicle-mounted communication terminal, device-to-device (D2D) terminal, machine-to-machine (M2M) terminal, and so on.

[0092] In addition, the term "network side" or "network device side" refers to one side of the network, which can be a base station or one or more network devices as described above. The term "user side" or "terminal side" or "terminal device side" refers to the user or terminal side, which can be a UE or one or more terminal devices as described above. Unless otherwise specified herein, "device" can refer to either network equipment or terminal equipment.

[0093] Rel-18 introduced Layer 2 (L2) mobility (LTM). Compared to Layer 3 (L3) mobility, LTM introduced in Rel-18 can improve handover latency and interruption time. However, compared to Layer 3 mobility, LTM introduced in Rel-18 also has some limitations.

[0094] For example, LTM operation only supports inter-cell mobility within the same gNB (the same CU (Centralized Unit)). This significantly limits the opportunities for LTM use cases, depending on network deployment scenarios. By ensuring LTM operation between cells of different gNBs (i.e., inter-CU), the network will be able to benefit from LTM in more scenarios.

[0095] In addition, Layer 3 based mobility uses Layer 3 measurement reporting, which supports events evaluated by the UE to trigger measurement reports, reducing signaling overhead compared to periodic measurement reporting. However, Layer 1 (L1) measurements for LTM mobility do not support such triggering events. Layer 1 measurements for the LTM process are limited to SSB (Synchronization Signal / PBCH Block) measurements. Extending Layer 1 measurements to include CSI-RS (Channel State Information-Reference Signal) can address this limitation and is expected to achieve greater throughput on the target cell immediately after cell handover.

[0096] Currently, Rel-19 (release 19) has been proposed to address the limitations of LTM introduced in Rel-18 (release 18). The objectives of the Rel-19 work items include: defining support for inter-CU Layer 2 Mobility (LTM), measurement-related enhancements to support LTM, defining support conditions for LTM, and, where necessary, defining RRM (Radio Resource Management) requirements related to the above objectives.

[0097] In the above objectives, support for inter-CU Layer 2 Mobility (LTM) is defined including:

[0098] Prioritize the case where the CU (Central Unit) acts as the MN (Master Node) when DC (Dual Connectivity) is not configured;

[0099] As a secondary priority, it supports the configuration of NR-DC, CU as SN (Secondary Node) and the MN remains unchanged;

[0100] As a secondary priority, it supports the configuration of NR-DC and CU as MN and the SCG (Secondary Cell Group) remains unchanged or is released. Note: This excludes the case where both MCG (Master Cell Group) and SCG are configured with LTM.

[0101] According to Rel-18 LTM, support for subsequent LTM mobility procedures is defined, with the goal of avoiding inter-cell handover RRC (Radio Resource Control) configuration; and security key handling is negotiated with the SA3 (Security Group).

[0102] Among the above objectives, it is worth noting that the Rel-18 intra-CU LTM process is considered as a baseline for increasing inter-CU support.

[0103] Among the above goals, measurement-related enhancements to support LTM include:

[0104] Measurement-related enhancements are applicable to intra-CU MCG / SCG LTM and inter-CU MCG / SCG LTM;

[0105] Define the necessary components to support event-triggered L1 measurement reporting; where RAN1 and RAN2 independently advance event-triggered measurement targets within their respective MIMO and mobility enhancement WIs; review progress at RAN#105 to see if targets need to be modified to avoid / manage any duplication of work;

[0106] Define CSI-RS measurements to support the LTM process and ensure necessary physical layer operations on CSI-RS based beam management and / or other pre-LTM candidate cells.

[0107] In the above objectives, the definition of supporting conditions LTM includes:

[0108] Define the conditions for triggering LTM evaluated by the UE;

[0109] The goal is to support conditional LTM that includes subsequent LTM;

[0110] Prioritize intra-CU LTM;

[0111] RAN#105 is the checkpoint for the review. RAN WG work will not begin before this checkpoint.

[0112] In an embodiment of the present application, when RLF or handover failure (HOF) occurs, the terminal initiates an RRC connection reestablishment process, that is, first performs cell selection; if the selected cell is a CHO candidate cell, the UE attempts CHO execution once; otherwise, if the selected cell is an LTM candidate cell, the UE attempts LTM execution once; otherwise, continues the RRC connection reestablishment process, that is, sends an RRC reestablishment request message.

[0113] According to the above mechanism, when an RLF or HOF occurs, if the selected cell is an LTM or CHO candidate cell, the UE attempts an LTM or CHO execution, as shown in Figure 6. The CHO or LTM execution for RLF / HOF recovery shown in Figure 6 can be considered a terminal-initiated cell change. LTM execution is based on the random access LTM process.

[0114] This shows that during a cell change initiated by a terminal for RLF or HOF fast recovery, or during a cell change initiated by the terminal under other conditions, the network does not make an LTM decision and therefore does not send a cell change command MAC CE to the terminal, resulting in the terminal being unable to obtain the corresponding information. This means that the terminal needs to obtain the corresponding information during or after the cell change process, just like L3HO (for example, L3CHO). This makes the advantages of the existing network-triggered LTM process unattainable in terminal-triggered LTM / CHO.

[0115] The present application is proposed to address the above-mentioned issues. The embodiments of the present application are described below in conjunction with the accompanying drawings and specific implementation methods. In the following description, "if...", "under...", and "when..." can be used interchangeably without causing confusion.

[0116] Embodiments of the first aspect

[0117] An embodiment of the present application provides a method for cell change, which is described from the perspective of a terminal device.

[0118] FIG7 is a schematic diagram of a method for changing a cell according to an embodiment of the present application. As shown in FIG7 , the method includes:

[0119] 710: The terminal device receives the candidate configuration and execution condition sent by the network device;

[0120] 720: The terminal device performs a first behavior when a first condition is met. The first behavior includes applying a target configuration, but does not include executing a second random access process. The target configuration is one of the candidate configurations sent by the network device that meets the first condition.

[0121] It is worth noting that FIG7 above only schematically illustrates an embodiment of the present application, and the present application is not limited thereto. For example, other operations may be added or some operations may be reduced. Those skilled in the art may make appropriate modifications based on the above content, and are not limited to the description of FIG7 above.

[0122] In the embodiment of the present application, for the convenience of explanation, the random access process is divided into a first random access process and a second random access process. Unless otherwise specified, the first random access process is a random access process on a candidate cell, at least including sending a random preamble code on the candidate cell; the second random access process is a random access process performed during the LTM / CHO execution process, at least including sending a random preamble code on the target cell and receiving a possible network response.

[0123] In the above embodiment, the candidate configuration includes the configuration of the candidate cell, and the execution condition includes the trigger condition of the event and / or parameters related to the trigger condition, such as the threshold, the maximum number and the duration of the timer, etc. For the relevant content of the candidate configuration and the execution condition, please refer to the relevant technology and will not be repeated here.

[0124] In the above embodiment, the first condition is a condition for the terminal device to execute the first behavior, and the first condition may include at least one of the following: an NR suitable cell is selected in the cell selection, the cell is a CHO / LTM candidate cell and is configured to allow CHO / LTM to be attempted; the serving cell is poor; the candidate cell is good; the candidate cell is better than the serving cell. In the above first condition, the cell selection is initiated after RLF or HOF on the MCG is triggered, and the condition is for executing the corresponding first condition for CHO / LTM for rapid recovery after RLF / HOF.

[0125] In the above embodiment, the first behavior can be LTM execution or CHO execution. For the specific content of LTM execution and CHO execution, please refer to the relevant technology and will not be repeated here.

[0126] According to the above embodiment, the terminal device can implement LTM execution or CHO execution triggered by the terminal device, thereby avoiding or reducing mobility failure or wireless link failure caused by failure to receive trigger commands from network devices, and improving robustness.

[0127] In the LTM mechanism triggered by existing network devices, the network device indicates the (UL / DL) TCI (Transmission Configuration Indication) status of the target cell in the LTM cell change command MAC CE to perform beam management of the target cell. However, in the first behavior triggered by the terminal device of this solution, there is no LTM cell change command MAC CE provided by the network device, and the terminal device cannot determine the TCI status before performing the above-mentioned first behavior. This means that the terminal device needs to determine the TCI status during or after the first behavior. If the terminal device determines the TCI status during the first behavior, this increases the execution time of the first behavior, resulting in longer service interruption; if the terminal device determines the TCI status after the first behavior, the terminal device may use an inappropriate beam or TCI status from the completion of the first behavior to the determination of the TCI status, which increases service overhead and causes a decrease in system throughput.

[0128] In response to the above problem, in an embodiment of the present application, the terminal device determines the TCI state (TCI state), such as the joint TCI state, uplink (UL) TCI state, downlink (DL) TCI state, etc., before performing the above first behavior, thereby solving the above problem.

[0129] In some embodiments, the terminal device determines the TCI state based on the downlink reference signal associated with the TCI state. For example, the terminal device determines the TCI state based on the measurement result of the downlink reference signal associated with the TCI state, such as L1 RSRP. For example, the terminal device is configured with two TCI states, wherein the TCI state with TCI State ID=1 is associated with a QCL, which includes a first downlink reference signal, and the TCI state with TCI State ID=2 is associated with a QCL, which includes a second downlink reference signal. If the L1 RSRP of the first downlink reference signal is better than the L1 RSRP of the second downlink reference signal, the terminal device selects / determines to use the TCI state associated with the first downlink reference signal, i.e., the TCI state with TCI State ID=1; or, if the L1 RSRP of the first downlink reference signal is better than a threshold and the L1 RSRP of the second downlink reference signal is worse than a threshold, the terminal device selects / determines to use the TCI state associated with the first downlink reference signal, i.e., the TCI state with TCI State ID=1. Similarly, the terminal device can determine the TCI state based on the L1 SINR of the downlink reference signal associated with the TCI state. Alternatively, the terminal device may determine the TCI state based on the L1 RSRP and L1 SINR of the downlink reference signal associated with the TCI state.

[0130] In other embodiments, the terminal device determines the TCI state based on the downlink reference signal determined in the first random access process. For example, the terminal device determines the TCI state using the downlink reference signal determined in the first random access process. The first random access process here is a random access process on the candidate cell initiated by the UL TA on this candidate cell in order to obtain. For example, the terminal device is configured with two TCI states, wherein the TCI state with TCI State ID=1 is associated with a QCL, which includes the first downlink reference signal, and the TCI state with TCI State ID=2 is associated with a QCL, which includes the second downlink reference signal. In the first random access process, if the terminal device sends a random access preamble code on the random access resource associated with the first downlink reference signal, the terminal device selects / determines to use the TCI state associated with the first downlink reference signal, that is, the TCI state with TCI State ID=1.

[0131] In some further embodiments, the terminal device determines the TCI state based on the downlink reference signal of the candidate cell in the TA measurement based on the terminal device. For example, the terminal device is configured with two TCI states, wherein the TCI state with TCI State ID=1 is associated with a QCL, which includes a first downlink reference signal, and the TCI state with TCI State ID=2 is associated with a QCL, which includes a second downlink reference signal. If the terminal device uses the first downlink reference signal of the candidate cell in the UE-based TA measurement to calculate / determine the TA value of the candidate cell, then the terminal device selects / determines the TCI state associated with the first downlink reference signal, i.e., the TCI state with TCI State ID=1.

[0132] In some further embodiments, the terminal device determines the TCI state based on first signaling sent by the network device and including TCI state information. The first signaling may be a MAC CE or DCI, such as a MAC CE or DCI from a serving cell; the TCI state information may include at least one of the following: a TCI state identifier (ID), downlink reference signal information, uplink reference signal information, etc. The downlink reference signal here may be, for example, an SSB or CSI-RS; the uplink reference signal here may be, for example, an SRS (Sounding Reference Signal).

[0133] In some further embodiments, the terminal device determines the TCI state based on the TCI state associated with the above-mentioned first condition. In this implementation, the above-mentioned candidate configuration and / or the above-mentioned execution condition include beam information and the first condition associated with the beam information. Thus, when the first condition is met, the terminal device selects / determines to use the beam information / TCI state associated with the first condition. In this implementation, the beam information / TCI state may be included in the above-mentioned candidate configuration, or in the above-mentioned execution condition, and the first condition associated with the beam information / TCI state may be included in the above-mentioned execution condition. The present application is not limited to this.

[0134] The above is an exemplary description of the method for determining the TCI status of a terminal device, but the present application is not limited thereto. Appropriate modifications can be made based on the above embodiments. For example, the above embodiments can be used individually, or one or more of the above embodiments can be combined.

[0135] In the above embodiment, according to the TCI state, the terminal device can perform processing related to the TCI state, for example, the terminal device performs beam management of the target cell according to the TCI state, etc.

[0136] In the existing LTM mechanism triggered by network devices, the network device indicates the UL TA of the target cell in the LTM cell change command MAC CE for UL synchronization. However, in the first action triggered by the terminal device of this solution, there is no LTM cell change command MAC CE provided by the network device, and therefore the TA value of the target cell cannot be provided. This means that the terminal device needs to obtain the UL TA value or perform uplink synchronization during or after the first action. If the terminal device performs UL synchronization during the first action, the execution time of the first action is increased, which will cause more service interruption. If the terminal device performs UL synchronization after the first action, the terminal device cannot perform UL transmission before UL synchronization, which increases system throughput and causes greater service interruption.

[0137] To address the above problem, in an embodiment of the present application, the terminal device obtains an uplink TA (UL TA) value before performing the above first behavior.

[0138] In some embodiments, the terminal device may obtain the UL TA value based on TA measurements based on the terminal device before performing the above first behavior.

[0139] In the above embodiment, the terminal device does not use the random access procedure on the candidate cell, but uses UE-based TA measurement to obtain the TA value of the candidate cell (ie, the target cell).

[0140] For example, if the above-mentioned candidate configuration sent by the network device includes a configuration based on UE TA measurement, and if the configuration of the candidate cell is the same as the configuration of the serving cell, the terminal device can use the method based on UE TA measurement to obtain the above-mentioned uplink TA value. In this case, the terminal device performs the above-mentioned first behavior, or, if the above-mentioned candidate configuration sent by the network device indicates or includes the configuration of the same TA or a configuration with TA being 0, the terminal device performs the above-mentioned first behavior; otherwise, that is, if the above-mentioned candidate configuration sent by the network device does not include a configuration based on UE TA measurement, or, if the configuration of the candidate cell is different from the configuration of the serving cell, the terminal device cannot use the method based on UE TA measurement to obtain the above-mentioned uplink TA value. In this case, and if the above-mentioned candidate configuration sent by the network device does not indicate or include the configuration of the same TA or a configuration with TA being 0, the terminal device performs the second behavior, which includes a second random access process.

[0141] In the above example, the second behavior includes applying a target configuration, which is one of the candidate configurations sent by the network device and satisfies the first condition. The second behavior can be executed by LTM or CHO.

[0142] According to the above embodiment, if the above-mentioned candidate configuration sent by the network device includes a configuration based on the TA measurement of the UE, and if the configuration of the candidate cell is the same as the configuration of the serving cell, or if the above-mentioned candidate configuration sent by the network device indicates or includes the configuration of the same TA or a configuration in which TA is 0, the terminal device performs the first behavior (applying the target configuration and not performing the second random access); otherwise, that is, if the above-mentioned candidate configuration sent by the network device does not include a configuration based on the TA measurement of the UE, or if the configuration of the candidate cell is different from the configuration of the serving cell, and if the above-mentioned candidate configuration sent by the network device does not indicate or include the configuration of the same TA or a configuration in which TA is 0, the terminal device performs the second behavior (applying the target configuration and performing the second random access).

[0143] That is, if the network provides a TA value (=0 or the same TA), or configures UE-based TA measurement and is the same as the configuration of the serving cell, the second device performs the first behavior (excluding random access); wherein, UE-based TA measurement is configured and is the same as the configuration of the serving cell, and the second device obtains TA through UE-based TA measurement; on the other hand, if the network does not provide a TA value (=0 or the same TA), and UE-based TA measurement is not configured or is the same as the configuration of the serving cell, the second device performs the second behavior (including random access).

[0144] In other embodiments, the terminal device may obtain the UL TA value through a random access process on the candidate cell before performing the above-mentioned first behavior. For example, the terminal device sends a preamble code to the candidate cell and receives response information from the network, where the response information includes TA information or includes TA information and candidate configuration information indicating the candidate cell, such as a candidate configuration ID. Thus, the terminal device can determine the uplink TA value of the candidate cell based on the TA information or the TA information and the candidate configuration information.

[0145] In the above embodiment, the response information may include, for example, at least one of the following: RAR (Random Access Response), a first TAC MAC CE (Time Advance Command MAC CE), and a first signaling.

[0146] In the above example, the RAR can be sent by the source cell or the candidate cell, and the RAR may include the candidate configuration information and / or the TA information. If the RAR is not received within the first time, the terminal device retransmits the preamble. When the terminal device receives the RAR, reaches the maximum number of transmissions, or reaches the maximum transmit power, the random access procedure on the candidate cell is considered complete.

[0147] In the above example, the first TAC MAC CE may be a new MAC CE including a TAC sent by the source cell, and the new MAC CE may include the above candidate configuration information and / or the above TA information.

[0148] In the above example, the first signaling may be sent by the source cell, and the first signaling at least includes the above candidate configuration information and / or the above TA information.

[0149] In the above embodiment, the candidate cell may also provide the above candidate configuration information and / or TA information or the above RAR to the source cell. For example, if the responding network is the source cell, that is, after the terminal device sends the above preamble to the candidate cell, it receives the response information from the source cell, then the candidate cell transmits the above candidate configuration information and / or TA information to the source cell or provides the above RAR, and then the source cell sends the above response information including the above candidate configuration information and / or TA information to the terminal device. If the source cell and the candidate cell are in different DUs of the same gNB, the DU where the candidate cell is located uses the F1 interface to transmit the above candidate configuration information and / or TA information to the DU where the source cell is located via the CU. Alternatively, if the source cell and the candidate cell are in different gNBs, the gNB / CU where the candidate cell is located transmits the above candidate configuration information and / or TA information to the gNB / CU where the source cell is located via the X2 interface.

[0150] In the above embodiment, the source cell may be a serving cell, such as a PCell or a PSCell.

[0151] In the above embodiment, the terminal device sends the above preamble code to the candidate cell, which may be triggered by a PDCCH order sent by the network device or initiated by the terminal device itself.

[0152] In yet other embodiments, the terminal device may obtain a UL TA value based on the uplink TA information associated with the first condition before performing the first action. In this implementation, the candidate configuration and / or the execution condition include the uplink TA information and the first condition associated with the uplink TA information. Thus, when the first condition is met, the terminal device may use the UL TA information associated with the first condition.

[0153] In the above embodiment, the above uplink TA information may be included in the above candidate configuration, or may be included in the above execution condition. The first condition associated with the uplink TA information may be included in the above execution condition, but the present application is not limited thereto.

[0154] In the above embodiment, the UL TA information may include a TA offset value (N TAoffset ) and TA value (N TA ), the terminal device can obtain the above-mentioned UL TA value according to the UL TA information.

[0155] The above is an exemplary description of the method for a terminal device to obtain a UL TA value, but the present application is not limited thereto. Appropriate modifications can be made based on the above embodiments. For example, the above embodiments can be used individually, or one or more of the above embodiments can be combined.

[0156] In the above embodiment, the terminal device can perform uplink transmission according to the obtained UL TA value, and can also be used for other purposes, which are not limited here.

[0157] In the embodiment of the present application, the terminal device optionally determines the validity of the uplink TA. For example, the first behavior includes determining the validity of the uplink TA, that is, the terminal device applies the target configuration to determine the validity of the uplink TA when the first condition is met.

[0158] In some embodiments, the terminal device determines the validity of the uplink TA based on a TA timer. For example, whether the uplink TA is valid is determined based on whether the TA timer has expired. If the TA timer has expired, is not running, or is configured but not running, the uplink TA is considered invalid. If the TA timer has not expired, is running, or is not configured, the uplink TA is considered valid.

[0159] In other embodiments, the terminal device determines the validity of the uplink TA based on the change in L1 RSRP. For example, the validity of the uplink TA is determined based on whether the change in L1 RSRP exceeds a first threshold. If the change in L1 RSRP exceeds the first threshold, the uplink TA is considered invalid; if the change in L1 RSRP does not exceed the first threshold, the uplink TA is considered valid.

[0160] In yet other embodiments, the terminal device determines the validity of the uplink TA based on changes in the L3 RSRP. For example, the validity of the uplink TA is determined based on whether the change in the L3 RSRP exceeds a second threshold. If the change in the L3 RSRP exceeds the second threshold, the uplink TA is considered invalid; if the change in the L3 RSRP does not exceed the second threshold, the uplink TA is considered valid.

[0161] In the above embodiment, the RSRP may be filtered RSRP, which may be a measurement value of a downlink reference signal of at least one of a source cell, a candidate cell, and a target cell.

[0162] In the above embodiment, the change may be an absolute change in the downlink reference signal of at least one of the source cell, the candidate cell, and the target cell. For example, the absolute change in the DL RS of the source cell is an increase or decrease in the measurement result r2 of the DL RS at t2 compared to the measurement result r1 of the DL RS at t1, or an increase or decrease in the measurement result r2 of the DL RS at t2 compared to a specified or configured measurement result r0. The change may be a relative change in the downlink reference signal of the candidate cell and / or the target cell compared to the downlink reference signal of the source cell, such as a change in the L1 RSRP / L3 RSRP of the DL RS of the candidate cell relative to the L1 RSRP / L3 RSRP of the DL RS of the source cell; or a relative change in the downlink reference signal of the source cell compared to the downlink reference signal of the candidate cell and / or the target cell, such as a change in the L1 RSRP / L3 RSRP of the DL RS of the source cell relative to the L1 RSRP / L3 RSRP of the DL RS of the candidate cell.

[0163] The above is an exemplary description of the method for a terminal device to determine the validity of an uplink TA, but the present application is not limited thereto, and appropriate modifications can be made based on the above embodiments. For example, the above embodiments can be used alone, or one or more of the above embodiments can be combined.

[0164] In the above embodiment, if the terminal device determines that the uplink TA is valid, it continues or performs the above first behavior. Otherwise, that is, if the terminal device determines that the UL TA is invalid, it performs the above second behavior. The relevant contents of the first behavior and the second behavior have been explained above and will not be repeated here.

[0165] In an embodiment of the present application, optionally, the terminal device uses a dynamic grant (DG) and / or a configured grant (CG) to send a first uplink transmission on the target cell. For example, the first behavior includes sending the first uplink transmission on the target cell. When the first condition is met, the terminal device applies the target configuration and sends the first uplink transmission on the target cell.

[0166] In some embodiments, the first uplink transmission carries / includes an RRC reconfiguration complete message or a MAC CE including a C-RNT or a contention resolution ID.

[0167] In some embodiments, the terminal device sends the first uplink transmission in the target cell using a dynamic grant (DG).

[0168] According to the existing mechanism, the source cell determines and initiates the LTM cell change process, so that the network side can be aware of the movement of the terminal device. However, for mobility or cell changes triggered by the terminal device, the network side or the target cell is unaware of the arrival of the terminal device, and the target cell cannot schedule the first UL transmission of the terminal device in the target cell through dynamic grant.

[0169] In response to the above problem, according to an embodiment of the present application, the target cell can transmit TA information to the source cell after receiving the random access preamble code of the terminal device, and then use dynamic authorization to schedule the terminal device.

[0170] In the above embodiment, the first behavior may also include the terminal device monitoring and / or receiving the PDCCH of the target cell, and sending the above first uplink transmission on the uplink authorization indicated by the PDCCH.

[0171] In the above embodiment, the network may configure a PDCCH occasion for the above scheduling. The terminal device may monitor and / or receive the above PDCCH on the PDCCH occasion configured by the network device. After the terminal device completes the first action (e.g., LTM execution), the PDCCH occasion becomes invalid or released or is used for the first UL transmission in a subsequent first action (e.g., LTM execution).

[0172] In the above embodiment, when the network device (successfully) receives the first UL transmission, the network device considers that the first behavior (e.g., LTM execution) is completed. When the terminal device considers that the network device (successfully) receives the first UL transmission, the terminal device considers that the first behavior (e.g., LTM execution) is completed.

[0173] In other embodiments, the terminal device sends a first uplink transmission in the target cell using a configured grant (CG).

[0174] According to the existing mechanism, the terminal device determines the associated configured authorization based on the beam information provided by the source cell in the LTM cell change command. However, for mobility or cell changes triggered by the terminal device, the source cell does not send the LTM cell change command. As a result, the terminal device cannot determine the configured authorization for the first uplink transmission of the target cell according to the existing mechanism.

[0175] To address the above problem, according to an embodiment of the present application, the terminal device may use at least one of the following configured authorizations to send a first uplink transmission:

[0176] A valid configured authorization, such as any valid configured authorization, in this example, the association of the CG with the beam (TCI state) is not configured;

[0177] The authorization of the configuration associated with the determined TCI status. The method for determining the TCI status is as described above and will not be repeated here.

[0178] The configuration authorization associated with the first condition, wherein the candidate configuration and / or the execution condition include the configuration authorization and the first condition associated with the configuration authorization. For example, when the first condition is met, the terminal device uses the configuration authorization associated with the first condition to send the first UL transmission.

[0179] In the above example, the authorization of the configuration may be included in the above candidate configurations, or may be included in the above execution conditions, and the first condition associated with the authorization of the configuration may be included in the above execution conditions.

[0180] In yet other embodiments, the terminal device sends the first uplink transmission on the target cell using a dynamic grant (DG) and / or a configured grant (CG).

[0181] For example, if there is a configured grant, the terminal device sends the first uplink transmission using the configured grant, or the terminal device sends the first uplink transmission without using a dynamic grant.

[0182] For another example, the first uplink transmission is sent using the grant that is earlier in time among the dynamic grant and the configured grant.

[0183] For another example, a first uplink transmission is sent using a dynamic grant or a configured grant according to the configuration on the network side. This application does not limit the specific configuration method, which can be explicit configuration, such as explicit configuration by a network device (gNB or target cell / DU / CU), or implicit configuration, etc.

[0184] The above is an exemplary description of a method in which a terminal device uses DG and / or CG to send a first uplink transmission, but the present application is not limited thereto, and appropriate modifications can be made based on the above embodiments. For example, the above embodiments can be used individually, or one or more of the above embodiments can be combined.

[0185] In the embodiment of the present application, optionally, after completing the first behavior, the terminal device retains the candidate configuration and evaluates other candidate configurations in the candidate configuration or candidate cells in the other candidate configurations for subsequent use.

[0186] The method of the embodiment of the present application is described below with reference to the accompanying drawings. In the following description, the first behavior is LTM execution as an example, but the present application is not limited thereto, and the first behavior may also be CHO.

[0187] FIG8 is a schematic diagram of a signaling process according to an embodiment of the present application. As shown in FIG8 , the process includes:

[0188] 810: The UE sends a measurement report to the gNB, and the gNB makes a CLTM (conditional LTM) decision.

[0189] 820: The gNB sends an RRC reconfiguration message to the UE. The RRC reconfiguration message includes the LTM candidate configuration and LTM execution conditions.

[0190] 830: The UE sends an RRC reconfiguration complete message to the gNB.

[0191] 840a / b: uplink and downlink synchronization with the candidate cell;

[0192] The UE evaluates the CLTM condition (i.e., the first condition), and when the first condition is met, leaves the source and applies the target configuration;

[0193] 850: RACH process (optional);

[0194] 860: LTM cell change completed.

[0195] The present application also provides a configuration method, which is described from the perspective of a network device. This method is a network-side process corresponding to the cell change method in the aforementioned embodiment, and the same contents will not be repeated here.

[0196] FIG9 is a schematic diagram of a configuration method according to an embodiment of the present application. As shown in FIG9 , the method includes:

[0197] 910: The network device sends a candidate configuration and execution conditions to the terminal device, where the candidate configuration and execution conditions are used for the terminal device to perform a first behavior when a first condition is met. The first behavior includes applying a target configuration but does not include performing a second random access process. The target configuration is one of the candidate configurations sent by the network device that meets the first condition.

[0198] In the above embodiment, the relevant contents of the candidate configuration, execution condition, first condition and first behavior have been explained in the previous embodiment and will not be repeated here.

[0199] In some embodiments, the network device may further send a first signaling to the terminal device. The first signaling may include TCI status information and TA information. The relevant content of the first signaling has been described in the previous embodiments and will not be repeated here.

[0200] In some embodiments, the network device may also perform random access on a candidate cell with the terminal device, for example, the network device receives a preamble sent by the terminal device and sends a response to the terminal device. In addition, the network device may also send a PDCCH command to the terminal device, which may trigger the terminal device to send a preamble to the candidate cell. The relevant content of the response has been described in the previous embodiment and will not be repeated here.

[0201] In some embodiments, the network device may further configure a PDCCH occasion for the terminal device, where the PDCCH occasion is used for the terminal device to monitor and / or receive a PDCCH sent by the network device. The configuration related to the PDCCH occasion may be included in the above candidate configurations.

[0202] In some embodiments, the network device may also receive a first uplink transmission sent by the terminal device. The relevant content of the first uplink transmission has been described in the previous embodiments and will not be repeated here.

[0203] The above is an exemplary description of the method of the embodiment of the present application, but the present application is not limited thereto, and appropriate modifications can be made based on the above embodiments. For example, the above embodiments can be used alone, or one or more of the above embodiments can be combined.

[0204] According to the method of an embodiment of the present application, the first condition is used as a trigger condition for the terminal device to perform the first behavior. When the first condition is met, the terminal device performs the first behavior, including applying the target configuration, and does not include executing the second random access process, thereby avoiding or reducing switching failure or wireless link failure, thereby improving robustness.

[0205] Embodiments of the second aspect

[0206] An embodiment of the present application provides a device for cell change.

[0207] Figure 10 is a schematic diagram of an apparatus for cell change according to an embodiment of the present application. The apparatus may be, for example, a terminal device, or one or more components or assemblies configured in the terminal device. Since the principle of solving the problem of this apparatus is the same as the method shown in Figure 7 of the embodiment of the first aspect, its specific implementation can refer to the implementation of the method shown in Figure 7 of the embodiment of the first aspect, and the same content will not be repeated here.

[0208] As shown in FIG10 , the apparatus 1000 includes:

[0209] a receiving unit 1010 for receiving candidate configurations and execution conditions sent by a network device; and

[0210] The processing unit 1020 performs a first behavior when a first condition is met, the first behavior including applying a target configuration and not including performing a second random access process, the target configuration being one of the candidate configurations sent by the network device that meets the first condition.

[0211] In the embodiment of the present application, the first behavior can be executed by LTM or CHO.

[0212] In some embodiments, the processing unit 1020 determines the TCI state before performing the first action. Optionally, the processing unit 1020 may perform beam management of the target cell based on the TCI state.

[0213] In the above embodiment, the processing unit 1020 may determine the TCI status according to at least one of the following:

[0214] The downlink reference signal associated with the TCI state;

[0215] A downlink reference signal determined during the first random access process;

[0216] Downlink reference signals of candidate cells based on TA measurements of the terminal device;

[0217] First signaling including TCI status information sent by the network device;

[0218] The TCI state associated with the first condition, wherein the above-mentioned candidate configuration and / or the above-mentioned execution condition include beam information and the first condition associated with the beam information.

[0219] In the above embodiment, the TCI state information may include at least one of the following: a TCI state ID, downlink reference signal information, and uplink reference signal information.

[0220] In the above embodiment, the beam information may include at least one of the following: TCI state ID, downlink reference signal information, and uplink reference signal information.

[0221] In the above embodiment, the downlink reference signal includes SSB and / or CSI-RS; the uplink reference signal includes SRS, but the present application is not limited thereto.

[0222] In some embodiments, the processing unit 1020 obtains an uplink TA value before performing the first action. Optionally, the processing unit 1020 may perform uplink transmission according to the uplink TA value.

[0223] In the above embodiment, the processing unit 1020 may obtain the uplink TA value before performing the above first behavior according to at least one of the following:

[0224] TA measurement based on terminal equipment;

[0225] Random access procedure on candidate cells;

[0226] Uplink TA information associated with the first condition, wherein the candidate configuration and / or the execution condition include the uplink TA information and the first condition associated with the uplink TA information.

[0227] In the above embodiment, the processing unit 1020 obtains the uplink TA value according to the TA measurement based on the terminal device, including:

[0228] If the candidate configuration sent by the network device includes a configuration based on the TA measurement of the terminal device, and if the configuration of the candidate cell is the same as the configuration of the serving cell, the processing unit 1020 obtains the uplink TA value according to the configuration based on the TA measurement of the terminal device.

[0229] In one possible implementation, if the above-mentioned candidate configuration sent by the network device includes a configuration based on the TA measurement of the terminal device, and if the configuration of the candidate cell is the same as the configuration of the serving cell, or if the above-mentioned candidate configuration sent by the network device indicates or includes the configuration of the same TA or a configuration with TA being 0, the terminal device performs the above-mentioned first behavior; otherwise, that is, if the above-mentioned candidate configuration sent by the network device does not include a configuration based on the TA measurement of the terminal device, or the configuration of the candidate cell is different from the configuration of the serving cell, and the above-mentioned candidate configuration sent by the network device does not indicate or include the configuration of the same TA or a configuration with TA being 0, the processing unit 1020 performs the second behavior, which includes the above-mentioned second random access process.

[0230] In the above embodiment, the second behavior may further include applying a target configuration, where the target configuration is one of the candidate configurations sent by the network device that meets the above first condition.

[0231] In the above embodiment, the second behavior may be executed by LTM or CHO.

[0232] In the above embodiment, the processing unit 1020 obtains the uplink TA value according to the random access process on the candidate cell, including:

[0233] Sending a preamble to the candidate cell;

[0234] receiving response information from the network, where the response information includes TA information or includes TA information and candidate configuration information indicating the candidate cell;

[0235] The uplink TA value of the candidate cell is determined according to the TA information or according to the TA information and the candidate configuration information.

[0236] In the above embodiment, the response information may include at least one of the following: RAR, the first TAC MAC CE, and the first signaling.

[0237] The RAR may come from the source cell or the candidate cell; the first TAC MAC CE and / or the first signaling may come from the source cell.

[0238] In the above embodiment, the TA information or the TA information and the candidate configuration information may be provided by the candidate cell to the source cell.

[0239] In the above embodiment, the sending of the preamble code by the terminal device to the candidate cell may be triggered by a PDCCH command sent by the network device, or may be triggered autonomously by the terminal device.

[0240] In the above embodiment, the uplink TA information may include at least one of a TA offset value and a TA value.

[0241] In some embodiments, the processing unit 1020 determines the validity of the uplink TA.

[0242] In the above embodiment, if the uplink TA is valid, the processing unit 1020 continues or performs the first action; otherwise, that is, if the uplink TA is invalid, the processing unit 1020 performs the second action. For details about the second action, please refer to the previous description and will not be repeated here.

[0243] In the above embodiment, the processing unit 1020 may determine the validity of the uplink TA according to at least one of the following:

[0244] Whether the TA timer has expired;

[0245] Whether the change of L1 RSRP exceeds a first threshold;

[0246] Whether the change of L3 RSRP exceeds the second threshold.

[0247] The RSRP may be a measurement value of a downlink reference signal of at least one of a source cell, a candidate cell, and a target cell.

[0248] In addition, the above-mentioned change can be an absolute change in the downlink reference signal of at least one of the source cell, the candidate cell, and the target cell, or a relative change in the downlink reference signal of the candidate cell and / or the target cell compared to the downlink reference signal of the source cell, or a relative change in the downlink reference signal of the source cell compared to the downlink reference signal of the candidate cell and / or the target cell.

[0249] In some embodiments, the processing unit 1020 sends the first uplink transmission in the target cell using the dynamic grant and / or the configured grant.

[0250] In the above embodiment, the processing unit 1020 sends the first uplink transmission using the dynamic grant, which may include:

[0251] Sending a random access preamble to the target cell;

[0252] Monitor and / or receive the PDCCH of the target cell and send the first uplink transmission based on the uplink grant indicated by the PDCCH.

[0253] The processing unit 1020 may monitor and / or receive the PDCCH on a PDCCH occasion configured by the network device.

[0254] After the processing unit 1020 completes the LTM execution, the PDCCH occasion is deactivated / released or used for the first uplink transmission in the subsequent LTM execution.

[0255] In the above embodiment, the processing unit 1020 sends the first uplink transmission using the configured grant, which may include:

[0256] The processing unit 1020 sends the first uplink transmission using at least one of the following configured grants:

[0257] Valid configured authorization;

[0258] Authorization of the configuration associated with the determined TCI state;

[0259] The authorization of the configuration associated with the first condition, wherein the candidate configuration and / or the execution condition include the authorization of the configuration and the first condition associated with the authorization of the configuration.

[0260] In the above embodiment, the processing unit 1020 sends the first uplink transmission using the dynamic grant and / or the configured grant, which may include at least one of the following:

[0261] If there is a configured grant, the processing unit 1020 sends the first transmission using the configured grant or sends the first uplink transmission without using the dynamic grant;

[0262] Sending a first uplink transmission using the grant that is earlier in time among the dynamic grant and the configured grant;

[0263] The first uplink transmission is sent using a dynamic grant or a configured grant according to the configuration on the network side.

[0264] In some embodiments, after completing the first behavior, the processing unit 1020 may further retain the candidate configuration and evaluate other candidate configurations in the candidate configuration or candidate cells in the other candidate configurations.

[0265] An embodiment of the present application also provides a configuration device.

[0266] Figure 11 is a schematic diagram of a configuration device according to an embodiment of the present application. The device may be, for example, a network device, or one or more components or assemblies configured on the network device. Since the principle of solving the problem of this device is the same as that of the method shown in Figure 9 of the embodiment of the first aspect, its specific implementation can refer to the implementation of the method shown in Figure 9 of the embodiment of the first aspect, and the same content will not be repeated here.

[0267] As shown in FIG11 , the apparatus 1100 includes:

[0268] A sending unit 1110 sends a candidate configuration and an execution condition to a terminal device, where the candidate configuration and the execution condition are used for the terminal device to perform a first behavior when a first condition is met. The first behavior includes applying a target configuration but does not include performing a second random access process. The target configuration is one of the candidate configurations sent by the network device that meets the first condition.

[0269] In some embodiments, the sending unit 1110 may further send a first signaling to the terminal device. The first signaling may include TCI status information and TA information. The relevant content of the first signaling has been described in the previous embodiment and will not be repeated here.

[0270] In some embodiments, as shown in FIG11 , the apparatus 1100 further includes:

[0271] The configuration unit 1120 is configured to configure a PDCCH occasion, which is used by the terminal device to monitor and / or receive a PDCCH sent by the network device. The configuration related to the PDCCH occasion may be included in the candidate configurations.

[0272] In some embodiments, as shown in FIG11 , the apparatus 1100 further includes:

[0273] The receiving unit 1130 receives a first uplink transmission sent by the terminal device.

[0274] In some embodiments, the receiving unit 1130 may further receive a preamble sent by the terminal device, and the sending unit 1110 may further send a response to the terminal device.

[0275] In the above embodiment, the sending unit 1110 may further send a PDCCH command to the terminal device, and the PDCCH command may trigger the terminal device to send a preamble code to the candidate cell.

[0276] The above embodiments of the present application are illustrative, but the present application is not limited thereto, and appropriate modifications can be made based on the above embodiments. For example, the above embodiments can be used alone, or one or more of the above embodiments can be combined.

[0277] It is worth noting that the above description only describes the components or modules related to this application, but this application is not limited thereto. The above-mentioned device may also include other components or modules. For the specific content of these components or modules, please refer to the relevant art. In addition, the above-mentioned components or modules can be implemented by hardware facilities such as processors, memories, transmitters, and receivers; the implementation of this application is not limited to this.

[0278] According to the apparatus of an embodiment of the present application, a first condition is used as a trigger condition for the terminal device to perform a first behavior. When the first condition is met, the terminal device performs the first behavior, including applying the target configuration, and does not include executing a second random access process, thereby avoiding or reducing switching failures or wireless link failures, thereby improving robustness.

[0279] Embodiments of the third aspect

[0280] An embodiment of the present application also provides a communication system, including a network device and a terminal device.

[0281] FIG12 is a schematic diagram of a communication system according to an embodiment of the present application, schematically illustrating a situation using a terminal device and a network device as an example. As shown in FIG12 , a communication system 1200 may include a network device 1201 and terminal devices 1202 and 1203. For simplicity, FIG12 illustrates only two terminal devices and one network device as an example, but the embodiments of the present application are not limited thereto.

[0282] In the embodiment of the present application, existing services or future services can be transmitted between the network device 1201 and the terminal devices 1202 and 1203. For example, these services may include but are not limited to: enhanced mobile broadband (eMBB), massive machine type communication (mMTC), and ultra-reliable and low-latency communication (URLLC), etc.

[0283] It is worth noting that Figure 12 shows that both terminal devices 1202 and 1203 are within the coverage range of network device 1201, but the present application is not limited thereto. Both terminal devices 1202 and 1203 may not be within the coverage range of network device 1201, or one terminal device 1202 may be within the coverage range of network device 1201 while the other terminal device 1203 is outside the coverage range of network device 1201.

[0284] In some embodiments, the terminal device includes the apparatus 1000 described in the embodiment of the second aspect, and is configured to execute the method shown in FIG7 of the embodiment of the first aspect. Since the method has been described in detail in the embodiment of the first aspect, its content is incorporated herein and will not be repeated.

[0285] An embodiment of the present application further provides a terminal device, which may be, for example, a UE, but the present application is not limited thereto and may also be other terminal devices.

[0286] Figure 13 is a schematic diagram of a terminal device according to an embodiment of the present application. As shown in Figure 13 , terminal device 1300 may include a processor 1301 and a memory 1302. Memory 1302 stores data and programs and is coupled to processor 1301. It should be noted that this diagram is exemplary; other types of structures may be used to supplement or replace this structure to implement telecommunication or other functions.

[0287] In some embodiments, the functions of the device 1000 of the embodiment of the second aspect can be integrated into the processor 1301, wherein the processor 1301 can be configured to execute a program to implement the method described in Figure 7 of the embodiment of the first aspect, the content of which is incorporated herein and will not be repeated here.

[0288] In other embodiments, the apparatus 1000 of the embodiment of the second aspect may be configured separately from the processor 1301. For example, the apparatus 1000 of the embodiment of the second aspect may be configured as a chip connected to the processor 1301, and the functions of the apparatus 1000 of the embodiment of the second aspect may be implemented through the control of the processor 1301.

[0289] As shown in Figure 13 , the terminal device 1300 may further include: a communication module 1303, an input unit 1304, a display 1305, and a power supply 1306. The functions of these components are similar to those in the prior art and are not described in detail here. It is worth noting that the terminal device 1300 does not necessarily include all of the components shown in Figure 13 , and these components are not essential. Furthermore, the terminal device 1300 may also include components not shown in Figure 13 , for which reference may be made to related art.

[0290] An embodiment of the present application further provides a network device, which includes a memory and a processor, wherein the memory stores a computer program, and the processor is configured to execute the computer program to implement the method described in FIG9 of the embodiment of the first aspect.

[0291] Figure 14 is a schematic diagram of a network device according to an embodiment of the present application. As shown in Figure 14, network device 1400 may include a central processing unit (CPU) 1410 and a memory 1420; memory 1420 is coupled to CPU 1410. Memory 1420 can store various data and information processing programs, which are executed under the control of CPU 1410 to receive various information sent by terminal devices and send various information to terminal devices.

[0292] For example, the processor 1410 may be configured to execute a program to implement the method described in FIG. 9 in the embodiment of the first aspect.

[0293] In addition, as shown in FIG14 , network device 1400 may further include: a transceiver 1430 and an antenna 1440, etc.; wherein, the functions of the above components are similar to those in the prior art and are not described in detail here. It is worth noting that network device 1400 does not necessarily include all the components shown in FIG14 ; in addition, network device 1400 may also include components not shown in FIG14 , and reference may be made to the prior art for details.

[0294] An embodiment of the present application also provides a computer program, wherein when the program is executed in a terminal device, the program causes the terminal device to execute the method described in FIG. 7 of the embodiment of the first aspect.

[0295] An embodiment of the present application further provides a storage medium storing a computer program, wherein the computer program enables a terminal device to execute the method described in FIG. 7 of the embodiment of the first aspect.

[0296] An embodiment of the present application also provides a computer program, wherein when the program is executed in a network device, the program causes the network device to execute the method described in FIG. 9 of the embodiment of the first aspect.

[0297] An embodiment of the present application further provides a storage medium storing a computer program, wherein the computer program enables the network device to execute the method described in FIG. 9 of the embodiment of the first aspect.

[0298] The above devices and methods of the present application can be implemented by hardware or by a combination of hardware and software. The present application relates to such a computer-readable program that, when executed by a logic component, enables the logic component to implement the devices or components described above, or enables the logic component to implement the various methods or steps described above. The present application also relates to a storage medium for storing the above program, such as a hard disk, a magnetic disk, an optical disk, a DVD, a flash memory, etc.

[0299] The method / device described in conjunction with the embodiments of the present application can be directly embodied as hardware, a software module executed by a processor, or a combination of the two. For example, one or more of the functional block diagrams shown in the figure and / or one or more combinations of functional block diagrams can correspond to various software modules of the computer program flow or to various hardware modules. These software modules can respectively correspond to the various steps shown in the figure. These hardware modules can be implemented by solidifying these software modules, for example, using a field programmable gate array (FPGA).

[0300] The software module may be located in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. A storage medium may be coupled to a processor so that the processor can read information from the storage medium and write information to the storage medium; or the storage medium may be an integral part of the processor. The processor and the storage medium may be located in an ASIC. The software module may be stored in the memory of the mobile terminal or in a memory card that can be inserted into the mobile terminal. For example, if the device (such as a mobile terminal) uses a large-capacity MEGA-SIM card or a large-capacity flash memory device, the software module may be stored in the MEGA-SIM card or the large-capacity flash memory device.

[0301] One or more of the functional blocks and / or one or more combinations of functional blocks described in the accompanying drawings may be implemented as a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic device, a discrete hardware component, or any appropriate combination thereof for performing the functions described in this application. One or more of the functional blocks and / or one or more combinations of functional blocks described in the accompanying drawings may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in communication with a DSP, or any other such configuration.

[0302] The present application has been described above in conjunction with specific embodiments. However, those skilled in the art should understand that these descriptions are merely illustrative and are not intended to limit the scope of protection of the present application. Those skilled in the art may make various modifications and variations to the present application based on the spirit and principles of the present application, and such modifications and variations are also within the scope of the present application.

[0303] Regarding the implementation methods including the above embodiments, the following additional notes are also disclosed:

[0304] 1. A method for cell change, wherein the method comprises:

[0305] The terminal device receives the candidate configuration and execution conditions sent by the network device;

[0306] The terminal device performs a first behavior when a first condition is met, the first behavior including applying a target configuration and not including executing a second random access process, the target configuration being one of the candidate configurations sent by the network device that meets the first condition.

[0307] 2. The method according to Supplement 1, wherein the method further comprises:

[0308] The terminal device determines the TCI state before performing the first behavior;

[0309] The terminal device performs beam management of the target cell according to the TCI status.

[0310] 3. The method according to Note 2, wherein the terminal device determines the TCI status according to at least one of the following:

[0311] A downlink reference signal associated with the TCI state;

[0312] A downlink reference signal determined during the first random access process;

[0313] Downlink reference signals of candidate cells based on TA measurements of the terminal device;

[0314] A first signaling including TCI status information sent by the network device;

[0315] a TCI state associated with the first condition, wherein the candidate configuration and / or the execution condition includes beam information and the first condition associated with the beam information;

[0316] in,

[0317] The TCI state information includes at least one of the following: a TCI state ID, downlink reference signal information, and uplink reference signal information;

[0318] The beam information includes at least one of the following: TCI state ID, downlink reference signal information, and uplink reference signal information;

[0319] The downlink reference signal includes SSB and / or CSI-RS;

[0320] The uplink reference signal includes an SRS.

[0321] 4. The method according to any one of Notes 1 to 3, further comprising:

[0322] The terminal device obtains an uplink TA value before performing the first behavior;

[0323] The terminal device performs uplink transmission according to the uplink TA value.

[0324] 5. The method according to Note 4, wherein the terminal device obtains the uplink TA value before performing the first behavior, including:

[0325] TA measurements based on terminal equipment; and / or,

[0326] a random access procedure on a candidate cell; and / or,

[0327] The uplink TA information associated with the first condition, wherein the candidate configuration and / or the execution condition includes uplink TA information and the first condition associated with the uplink TA information.

[0328] 6. The method according to Note 5, wherein the terminal device obtains the uplink TA value based on a TA measurement based on the terminal device, comprising:

[0329] If the candidate configuration sent by the network device includes a configuration based on a TA measurement of a terminal device, and if the configuration of the candidate cell is the same as the configuration of the serving cell, the terminal device obtains the uplink TA value according to the configuration based on the TA measurement of the terminal device;

[0330] If the candidate configuration sent by the network device includes a configuration based on the TA measurement of the terminal device, and if the configuration of the candidate cell is the same as the configuration of the serving cell; or if the candidate configuration sent by the network device indicates or includes a configuration of the same TA or a configuration in which the TA is 0, the terminal device performs the first behavior;

[0331] If the candidate configuration sent by the network device does not include a configuration based on the TA measurement of the terminal device, or the configuration of the candidate cell is different from the configuration of the serving cell, and the above-mentioned candidate configuration sent by the network device does not indicate or does not include a configuration of the same TA or a configuration in which the TA is 0, the terminal device performs a second behavior, and the second behavior includes the second random access process.

[0332] 7. The method according to Supplementary Note 6, wherein:

[0333] The second behavior is LTM execution or CHO execution.

[0334] 8. The method according to Note 5, wherein the terminal device obtains the uplink TA value according to a random access procedure on the candidate cell, comprising:

[0335] The terminal device sends a preamble code to the candidate cell;

[0336] The terminal device receives response information from the network, where the response information includes TA information or includes TA information and candidate configuration information indicating the candidate cell;

[0337] The terminal device determines the uplink TA value of the candidate cell according to the TA information or according to the TA information and the candidate configuration information;

[0338] in,

[0339] The response information includes at least one of the following: a RAR, a first TAC MAC CE, and a first signaling, wherein the RAR comes from a source cell or a candidate cell, and the first TAC MAC CE and / or the first signaling comes from the source cell;

[0340] The TA information or the TA information and the candidate configuration information are provided by the candidate cell to the source cell;

[0341] The TA information includes at least one of a TA offset value and a TA value.

[0342] 9. The method according to any one of Notes 1 to 8, further comprising:

[0343] The terminal device sends a first uplink transmission in the target cell using the dynamic authorization and / or the configured authorization;

[0344] The terminal device sending a first uplink transmission using a dynamic grant includes:

[0345] The terminal device sends a random access preamble code to the target cell;

[0346] The terminal device monitors and / or receives the PDCCH of the target cell and sends the first uplink transmission on the uplink grant indicated by the PDCCH.

[0347] 10. The method according to Supplementary Note 9, wherein:

[0348] The terminal device monitors and / or receives the PDCCH on the PDCCH occasion configured by the network device;

[0349] After the terminal device completes the LTM execution, the PDCCH occasion is invalidated / released or used for the first uplink transmission in a subsequent LTM execution.

Claims

1. A cell change device, configured in a terminal device, wherein: The device comprises: a receiving unit configured to receive candidate configurations and execution conditions sent by a network device; A processing unit, which performs a first behavior when a first condition is met, wherein the first behavior includes applying a target configuration and does not include performing a second random access process, and the target configuration is one of the candidate configurations sent by the network device that meets the first condition.

2. The device according to claim 1, wherein The first behavior is a layer 1 or layer 2 triggered mobility (LTM) execution or a conditional handover (CHO) execution.

3. The device according to claim 1, wherein The processing unit also determines a transmission configuration indication (TCI) state before performing the first behavior.

4. The device according to claim 3, wherein The processing unit determines the TCI status according to at least one of the following: A downlink reference signal associated with the TCI state; A downlink reference signal determined during the first random access process; Downlink reference signals of candidate cells based on the timing advance (TA) measurement of the terminal device; A first signaling including TCI status information sent by the network device; The TCI state associated with the first condition, wherein the candidate configuration and / or the execution condition includes beam information and the first condition associated with the beam information.

5. The device according to claim 1, wherein The processing unit further obtains an uplink TA value before performing the first behavior.

6. The device according to claim 5, wherein The processing unit obtaining the uplink TA value before performing the first behavior includes: Acquiring the uplink TA value based on TA measurement of the terminal device; and / or, Acquiring the uplink TA value according to a random access process on a candidate cell; and / or, The uplink TA value is acquired according to the uplink TA information associated with the first condition, wherein the candidate configuration and / or the execution condition includes uplink TA information and the first condition associated with the uplink TA information.

7. The device according to claim 6, wherein The processing unit obtains the uplink TA value according to TA measurement based on the terminal device, including: If the candidate configuration sent by the network device includes a configuration based on TA measurement of the terminal device, and If the configuration of the candidate cell is the same as the configuration of the serving cell, the processing unit obtains the uplink TA value according to the configuration based on the TA measurement of the terminal device.

8. The device according to claim 7, wherein If the candidate configuration sent by the network device does not include a configuration based on the TA measurement of the terminal device, or the configuration of the candidate cell is different from the configuration of the serving cell, and the candidate configuration sent by the network device does not indicate or does not include a configuration of the same TA or a configuration with a TA of 0, the processing unit performs a second behavior, and the second behavior includes the second random access process.

9. The device according to claim 8, wherein The second behavior includes applying a target configuration, where the target configuration is one of the candidate configurations sent by the network device that meets the first condition.

10. The device according to claim 6, wherein The processing unit obtains the uplink TA value according to a random access process on the candidate cell, including: The processing unit sends a preamble code to the candidate cell; The processing unit receives response information from the network, where the response information includes TA information or includes TA information and candidate configuration information indicating the candidate cell; The processing unit determines the uplink TA value of the candidate cell according to the TA information or according to the TA information and the candidate configuration information.

11. The device according to claim 10, wherein The response information includes at least one of the following: a random access response (RAR), a first timing advance command medium access control control element (TAC MAC CE), and a first signaling.

12. The device according to claim 10, wherein The sending of the preamble code by the processing unit to the candidate cell is triggered by a physical downlink control channel (PDCCH) command sent by the network device or by the terminal device.

13. The device according to claim 1, wherein The processing unit further determines the validity of the uplink TA.

14. The device according to claim 13, wherein In a case where the uplink TA is valid, the processing unit continues or performs the first behavior.

15. The device according to claim 13, wherein The device further comprises: In the case that the uplink TA is invalid, the processing unit performs a second action.

16. The device according to claim 13, wherein The processing unit determines the validity of the uplink TA according to at least one of the following: Whether the TA timer has expired; whether a change in layer 1 reference signal received power (L1RSRP) exceeds a first threshold; Whether a change in layer 3 reference signal received power (L3RSRP) exceeds a second threshold.

17. The device according to claim 1, wherein The processing unit further sends a first uplink transmission in the target cell using the dynamic grant and / or the configured grant.

18. The device according to claim 17, wherein The processing unit sends a first uplink transmission using the configured grant, comprising: The processing unit sends the first uplink transmission using at least one of the following configured grants: Valid configured authorization; Authorization of the configuration associated with the determined TCI state; The first condition is associated with the authorization of the configuration, wherein the candidate configuration and / or the execution condition includes the authorization of the configuration and the first condition associated with the authorization of the configuration.

19. The device according to claim 17, wherein The processing unit sends a first uplink transmission using the dynamic grant and / or the configured grant, including at least one of the following: If there is a configured grant, the processing unit sends the first uplink transmission using the configured grant or sends the first uplink transmission without using the dynamic grant; Sending the first uplink transmission using the grant that is earlier in time between the dynamic grant and the configured grant; The first uplink transmission is sent using a dynamic grant or a configured grant according to a configuration on the network side.

20. The device according to claim 1, wherein After completing the first behavior, the processing unit retains the candidate configuration and evaluates other candidate configurations in the candidate configuration or candidate cells in the other candidate configurations.

Images