Timer processing method and device

Abstract

The embodiment of the invention provides a timer processing method and device, and the method comprises the steps: when a first timer is not operated, terminal equipment executes at least one of the following processing: quick recovery; performing cell switching based on random access; sending the first uplink data by using the dynamic authorization; the first timer is started or restarted; wherein the first timer is a configured authorization timer or a time alignment timer. According to the embodiment of the invention, the terminal equipment can continue to transmit the first uplink data when the first timer is not operated, thereby ensuring successful completion of LTM cell switching or completion of LTM execution.

Description

Timer processing method and device Technical Field

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

[0002] The PUSCH (Physical Uplink Shared Channel) can be scheduled by the DCI (Downlink Control Information) on the PDCCH (Physical Downlink Control Channel). The network device uses the uplink grant on the DCI to schedule the initial transmission of each uplink transmission. Alternatively, the PUSCH can provide a configured grant (CG) via the RRC (Radio Resource Control) protocol. Currently, the following two operations are supported:

[0003] Type-2: The first PUSCH is triggered by DCI, and subsequent PUSCH transmissions follow the RRC configuration and the scheduling received from the DCI;

[0004] Type-1: PUSCH is triggered by the arrival of buffered data sent by the terminal device, and the transmission of this PUSCH follows the RRC configuration.

[0005] For shared spectrum channel access, the terminal device can retransmit on the CG. To handle possible LBT (listen before talk) failures on the CG, a CG retransmission timer can be configured to ensure autonomous retransmission. When the CG retransmission timer is configured, the terminal device will automatically select the HARQ (Hybrid Automatic Repeat-reQuest) process for each CG resource.

[0006] For cell-level scheduling, CS-RNTI (Configured Scheduling RNTI) is a unique terminal device identifier used for downlink SPS (Semi-Persistent Scheduling) and uplink CG.

[0007] For a BWP (Bandwidth Part) of a serving cell, a terminal device can be configured with up to 12 activated CGs. When multiple CGs are configured, the network side decides which (including all) CGs to activate at a time. For Type-2, each CG is activated separately using a DCI command, and one DCI can be used to deactivate one or more CGs.

[0008] When SUL (Supplementary Uplink) is configured, the network side needs to ensure that an activated CG on the SUL does not overlap in time with another activated CG on another UL configuration.

[0009] For dynamic grant (DG) and CG Type-2, the number of repetitions can also be dynamically indicated in L1 signaling. If the number of repetitions also exists in RRC, the dynamically indicated number of repetitions overrides the number of repetitions configured in the RRC.

[0010] To improve NR (New Radio) uplink coverage, both dynamically granted and configured granted PUSCH transmissions support multi-slot aggregation enhancement with TB (Transport Block) repetition.

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

[0012] Summary of the Invention

[0013] The inventors discovered that in the L1 / L2 triggered mobility (LTM) process, the network device decides to perform a cell switch to the target cell and sends a MAC CE that triggers the cell switch and includes a target cell candidate configuration index. The terminal device switches to the target cell and applies the configuration indicated by the candidate configuration index; in addition, the terminal device also sends the first uplink data (also called the first UL data) in the target cell, such as an RRC reconfiguration completion message. If the random access process is not performed, that is, for RACH-less LTM, when the terminal device determines that the network side has successfully received its first uplink data, the terminal device considers that the LTM execution is completed. In addition, the terminal device determines the successful reception of its first uplink data by receiving a newly transmitted PDCCH addressed by the C-RNTI of the terminal device in the target cell and scheduling the first uplink data transmission.

[0014] According to the current discussion, either dynamic grant or configured grant can be used for the first uplink data transmission of the terminal device in the target cell during the LTM process. In the case of dynamic grant, it is assumed that the source DU (Distributed Unit) informs the target DU of the selected beam so that the target DU can start dynamically scheduling UL grant; in the case of configured grant, the terminal device selects the configured grant opportunity associated with the beam indicated in the LTM MAC CE.

[0015] However, RACH-less LTM has the following problems:

[0016] Question 1: When a terminal device uses the configured authorization to send the first uplink data, if the corresponding CG timer times out and the terminal device has not successfully completed LTM execution or LTM cell switching, the terminal device will not be able to continue transmitting the first uplink data, and will not be able to complete LTM execution or LTM cell switching, increasing service interruption between the terminal device and the network.

[0017] Question 2: During the LTM process, when an LTM cell switching command (MAC CE) including a TAC (Timing Advance Command) is received, the terminal device applies the TAC to the PTAG (Primary Timing Advance Group) of the indicated LTM target cell, and starts or restarts the TAT (TA timer) associated with the PTAG. According to the existing mechanism, if the TAT is not running, the terminal device cannot perform any uplink transmission except for the random access preamble and MSGA (message A) transmission. This means that if the terminal device has not successfully completed the LTM execution or LTM cell switching when the TAT times out, as shown in Figure 1, the terminal device cannot continue to transmit the first uplink data, and cannot complete the LTM execution or LTM cell switching, which increases the service interruption between the terminal device and the network.

[0018] In response to at least one of the above problems or other similar problems, an embodiment of the present application provides a timer processing method and device, so that the terminal device can continue to transmit the first uplink data and / or continue the cell switching process when the CG timer or TA timer (TAT) is not running, thereby ensuring the successful completion of the LTM cell switching or the completion of the LTM execution; or enable the terminal device to quickly recover when the CG timer or TA timer (TAT) is not running, thereby reducing service interruption.

[0019] According to one aspect of an embodiment of the present application, a timer processing device is configured in a terminal device, wherein the device includes:

[0020] The first processing unit performs at least one of the following processes when the first timer is not running:

[0021] Quick recovery;

[0022] Cell switching based on random access;

[0023] Send the first uplink data using dynamic grant; and

[0024] Starting or restarting the first timer;

[0025] The first timer is a configured authorization timer or a time alignment timer.

[0026] One of the beneficial effects of the embodiments of the present application is that: according to the embodiments of the present application, when the first timer is not running, the terminal performs at least one of (1) fast recovery, (2) cell switching based on random access, (3) sending the first uplink data using dynamic authorization, or (4) starting or restarting the first timer. As a result, the terminal device can continue to transmit the first uplink data and / or continue the cell switching process when the first timer is not running, thereby ensuring that the LTM cell switching is successfully completed or the LTM execution is completed; or enables the terminal device to perform fast recovery when the CG timer or TA timer (TAT) is not running, thereby reducing service interruption.

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

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

[0029] 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

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

[0031] FIG1 is a schematic diagram showing that a UE cannot send the first uplink data in a target cell when TAT times out;

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

[0033] FIG3 is a schematic diagram of an inter-cell mobility scenario based on L1 / L2;

[0034] FIG4 is a schematic diagram of an Intra-AMF / UPF handover scenario (ie, an L3 handover scenario);

[0035] FIG5 is a schematic diagram of an Intra-AMF / UPF conditional switching scenario (also known as a CHO scenario);

[0036] FIG6 is a schematic diagram of a timer processing method according to an embodiment of the present application;

[0037] FIG7 is a schematic diagram of a timer processing device according to an embodiment of the present application;

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

[0039] FIG9 is a schematic diagram of a terminal device according to an embodiment of the present application. DETAILED DESCRIPTION

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

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

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

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

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

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

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

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

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

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

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

[0051] FIG2 is a schematic diagram of the LTM process. As shown in FIG2 , the process includes the following steps:

[0052] 1. The UE sends a MeasurementReport message to the gNB, where the gNB-CU decides to use LTM and initiates candidate cell preparation.

[0053] 2. The gNB sends an RRCReconfiguration message to the UE, including the LTM candidate cell configuration of one or more candidate cells.

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

[0055] 4a / 4b. Before receiving the cell handover command, the UE may perform DL (Downlink, referred to as downlink) synchronization and TA (Timing Advance) acquisition of the candidate cell;

[0056] 5. The UE performs L1 measurements on the configured candidate cells and sends a low-layer measurement report to the gNB.

[0057] Note: The order of DL / UL (Uplink) synchronization and L1 measurement is not yet defined and can be changed.

[0058] 6. The gNB decides to perform a cell handover to the target cell and sends a MAC CE (MAC Control Element) triggering a cell handover LTM command by including the candidate configuration index of the target cell. The UE switches to the configuration of the target cell.

[0059] 7. If the cell handover requires the execution of a random access procedure, the UE performs a random access procedure to the target cell;

[0060] 8. The UE indicates the completion of the cell handover to the target cell.

[0061] The UE may perform steps 4-8 multiple times based on the configuration provided in step 2 for subsequent LTM cell handovers.

[0062] FIG3 is a schematic diagram of an inter-cell mobility scenario according to an embodiment of the present application.

[0063] As shown in Figure 3, in this embodiment of the present application, when a terminal device moves from the coverage area of ​​one cell to the coverage area of ​​another cell, a serving cell change is required at some point. Inter-cell mobility supports scenarios including inter-gNB, inter-DU, intra-DU, handover, CA, NR-DC, and inter-frequency scenarios.

[0064] In handover scenarios, handover refers to the mobility / change of the PCell, which involves both non-CA (i.e., PCell only) and CA scenarios (i.e., PCell and SCell(s)). It includes:

[0065] The target PCell / target SCell(s) is not the current serving cell (i.e., CA→CA scenario with PCell change), such as the cell change from B to D in the scenario shown in Figure 3;

[0066] The target PCell is a current SCell, such as the cell change from B to C in the scenario shown in FIG3 ; and

[0067] The target SCell is the current PCell, for example, the cell change from A to B in the scenario shown in FIG3 .

[0068] In the CA scenario, PCell changes without SCell changes and PCell changes with SCell changes are supported.

[0069] In the NR-DC scenario, PSCell changes that do not involve MN (Mobile Network) (i.e., intra-SN) are supported.

[0070] In the inter-frequency scenario, which includes mobility to an inter-frequency cell other than the current serving cell, inter-frequency L1 measurement is supported if feasible.

[0071] In the above scenarios, the source cell and the target cell may be synchronous or asynchronous, and may operate in FR1 or FR2.

[0072] Figure 4 is a schematic diagram of an Intra-AMF / UPF handover scenario (i.e., an L3 handover scenario). As shown in Figure 4, in this scenario, the following steps are included:

[0073] 0. The UE context in the source gNB contains information about roaming and access restrictions, which was provided during connection establishment or the last TA update.

[0074] 1. The source gNB configures the UE measurement process, and the UE reports based on the measurement configuration.

[0075] 2. The source gNB decides to hand over the UE based on the measurement report and RRM information.

[0076] 3. The source gNB issues a Handover Request message to the target gNB, which delivers a transparent RRC container with the necessary information to prepare the handover on the target side. The source gNB may also request DAPS handover for one or more DRBs.

[0077] 4. Admission control can be performed by the target gNB.

[0078] 5. The target gNB prepares for handover with L1 / L2 and sends a HANDOVER REQUEST ACKNOWLEDGE message to the source gNB, which includes a transparent container to be sent as an RRC message to the UE to perform the handover. The target gNB also indicates whether it accepts DAPS handover.

[0079] NOTE: Data forwarding can be started once the source gNB receives the Handover Request Acknowledgement or once the transmission of the Handover Command is initiated in the downlink.

[0080] 6. The source gNB triggers Uu handover by sending an RRCReconfiguration message to the UE.

[0081] 7. For DRBs not configured with DAPS, the source gNB sends an SN STATUS TRANSFER message to the target gNB to convey the uplink PDCP SN receive status and downlink PDCP SN transmit status for the DRB (i.e., RLC AM) to which PDCP status preservation is applied. The uplink PDCP SN receive status includes at least the PDCP SN of the first lost UL PDCP SDU and may include a bitmap indicating the receive status of out-of-sequence UL PDCP SDUs (if any) that the UE needs to retransmit in the target cell. The downlink PDCP SN transmit status indicates the next PDCP SN that the target gNB will assign to new PDCP SDUs that do not yet have a PDCP SN.

[0082] 8. The UE synchronizes with the target cell and completes the RRC handover procedure by sending an RRCReconfigurationComplete message to the target gNB. In the case of DAPS handover, the UE does not detach from the source cell upon receiving the RRCReconfiguration message. Upon receiving an explicit release from the target node, the UE releases the source resources and configuration and ceases DL / UL reception / transmission with the source.

[0083] 9. The target gNB sends a PATH SWITCH REQUEST message to the AMF to trigger the 5GC to switch the DL data path to the target gNB and establish the NG-C interface instance towards the target gNB.

[0084] 10. The 5GC switches the DL data path to the target gNB. The UPF sends one or more “end marker” packets per PDU session / tunnel on the old path to the source gNB. All U-Plane / TNL resources towards the source gNB may then be released.

[0085] 11.AMF uses the PATH SWITCH REQUEST ACKNOWLEDGE message to confirm the PATH SWITCH REQUEST message.

[0086] 12. Upon receiving the PATH SWITCH REQUEST ACKNOWLEDGE message from the AMF, the target gNB sends a UE CONTEXT RELEASE message to inform the source gNB of the handover success. The source gNB may then release the radio and C-plane related resources associated with the UE context. Any ongoing data forwarding may continue.

[0087] Figure 5 is a schematic diagram of an Intra-AMF / UPF conditional handover scenario (also known as a CHO scenario). As shown in Figure 5, in this scenario, the following steps are included:

[0088] 0. The UE context in the source gNB contains information about roaming and access restrictions, which was provided during connection establishment or the last TA update.

[0089] 1. The source gNB configures the UE measurement process, and the UE reports based on the measurement configuration.

[0090] 2. The source gNB decides to use CHO.

[0091] 3. The source gNB requests CHO for one or more candidate cells belonging to one or more candidate gNBs, sending a CHO request message for each candidate cell.

[0092] 4. Admission control may be performed by the target gNB. If slice information is sent to the target gNB, slice-aware admission control shall be performed. If a PDU Session is associated with an unsupported slice, the target gNB shall reject such a PDU Session.

[0093] 5. The candidate gNB sends a CHO response (HO REQUEST ACKNOWLEDGE) containing the CHO candidate cell configuration to the source gNB. Each candidate cell sends a CHO response message.

[0094] 6. The source gNB sends an RRCReconfiguration message to the UE, which includes the configuration of the CHO candidate cells and the CHO execution conditions.

[0095] The CHO configuration of the candidate cell can follow other reconfigurations of the source gNB.

[0096] 7. The UE sends an RRCReconfigurationComplete message to the source gNB.

[0097] 7a. If early data forwarding is applied, the source gNB sends an EARLY STATUS TRANSFER message.

[0098] 8. After receiving the CHO configuration, the UE maintains its connection to the source gNB and begins evaluating the CHO execution conditions for candidate cells. If at least one CHO candidate cell meets the corresponding CHO execution conditions, the UE detaches from the source gNB, applies the corresponding configuration stored for the selected candidate cell, synchronizes to the candidate cell, and completes the RRC handover process by sending an RRCReconfigurationComplete message to the target gNB.

[0099] 8a. The target gNB sends a HANDOVER SUCCESS message to the source gNB, notifying the UE that it has successfully accessed the target cell.

[0100] 8b. The source gNB sends an SN STATUS TRANSFER message.

[0101] 8c. The source gNB sends a HANDOVER CANCEL message to other signaling connections or other candidate target gNBs (if any) to cancel the UE’s CHO.

[0102] The embodiments of the present application are described below in conjunction with the accompanying drawings and specific embodiments. In the following description, "if ...", "under ..." and "when ..." can be used interchangeably without causing confusion.

[0103] Embodiments of the first aspect

[0104] An embodiment of the present application provides a timer processing method, which is described from the perspective of a terminal device.

[0105] FIG6 is a schematic diagram of a timer processing method according to an embodiment of the present application. As shown in FIG6 , the method includes:

[0106] 610: When the first timer is not running, the terminal device performs at least one of the following processes:

[0107] Quick recovery;

[0108] Cell switching based on random access;

[0109] Send the first uplink data using dynamic grant; and

[0110] Starting or restarting the first timer;

[0111] The first timer is a configured grant timer (configuredGrantTimer) or a time alignment timer (timeAlignmentTimer).

[0112] It is worth noting that FIG6 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 FIG6 above.

[0113] In the above embodiment, when the first timer is not running, the terminal performs at least one of (1) fast recovery, (2) cell switching based on random access, (3) sending the first uplink data using dynamic authorization, or (4) starting or restarting the first timer. As a result, the terminal device can continue to transmit the first uplink data and / or continue the cell switching process when the first timer is not running, thereby ensuring that the LTM cell switching is successfully completed or the LTM execution is completed; or enable fast recovery when the CG timer or TA timer (TAT) is not running, thereby reducing service interruption.

[0114] In the embodiment of the present application, the first timer not running means at least one of the following:

[0115] A first timer is configured and times out;

[0116] A first timer is configured and stopped;

[0117] The first timer is not configured.

[0118] In some embodiments, the terminal device performs fast recovery including: the terminal device initiates RRC connection reconstruction.

[0119] For example, the terminal device performs cell selection; if the first condition is met, that is, the selected cell is a conditional handover (CHO) candidate cell, and the network is configured to try CHO after failure, the terminal device attempts CHO execution once, or the terminal device applies the configuration of the CHO candidate cell; if the second condition is met, that is, the selected cell is an L1 / L2 triggered mobility (LTM) candidate cell, and the network is configured to try LTM after failure, the terminal device attempts LTM to the above-mentioned candidate cell once, or the terminal device applies the configuration of the LTM candidate cell; if the first condition and / or the second condition are not met, the terminal device sends an RRC connection re-establishment request.

[0120] In the above example, not meeting the first condition means that the selected cell is not a CHO candidate cell and the network has not configured a CHO attempt after failure. That is, if the selected cell is not a CHO candidate cell and the network has not configured a CHO attempt after failure, the terminal device sends an RRC connection reestablishment request.

[0121] In the above example, not meeting the second condition means that the selected cell is not an LTM candidate cell and the network has not configured LTM after failure. That is, if the selected cell is not an LTM candidate cell and the network has not configured LTM after failure, the terminal device sends an RRC connection reestablishment request.

[0122] In the above example, not satisfying the first and second conditions means that the selected cell is neither a CHO candidate cell nor an LTM candidate cell, and the network has not configured CHO and LTM attempts after failure. In other words, if the selected cell is neither a CHO candidate cell nor an LTM candidate cell, and the network has not configured CHO and LTM attempts after failure, the terminal device sends an RRC connection reestablishment request.

[0123] For another example, the terminal device performs cell selection; if the first condition is met, that is, the selected cell is a conditional handover (CHO) candidate cell, and the network is configured to try CHO after failure, the terminal device attempts CHO execution once, or the terminal device applies the configuration of the CHO candidate cell; otherwise, the terminal device sends an RRC connection re-establishment request.

[0124] For another example, the terminal device performs cell selection; if the second condition is met, that is, the selected cell is an L1 / L2 triggered mobility (LTM) candidate cell, and the network is configured to try LTM after failure, the terminal device attempts LTM to the above candidate cell once, or the terminal device applies the configuration of the LTM candidate cell; otherwise, the terminal device sends an RRC connection re-establishment request.

[0125] In the above embodiment, the MAC layer / entity of the terminal device may indicate to the upper layers (RACH-less) that the first timer has timed out or stopped, or that the cell handover has failed, or that the radio link has failed, or that failure recovery has been performed, and / or the terminal device may consider that the cell handover timer has timed out. Thus, compared to the existing mechanism, the behavior of the terminal device reuses the existing mechanism as much as possible, thereby reducing the complexity of the terminal device and reducing the cost of the terminal device. Here, the cell handover timer is, for example, T304. For the meaning of T304, please refer to the relevant technology and the description is omitted here.

[0126] According to the above embodiment, when the first timer is not running, the terminal device initiates RRC connection reestablishment, thereby enabling the terminal device to quickly recover and reduce service interruption.

[0127] In some embodiments, the terminal device performs random access-based cell switching, which may include: the MAC layer of the terminal device performs a random access process to the target cell.

[0128] For example, the terminal device uses the random access resources associated with the beam configured by RRC, the beam indicated by the lower layer (such as the MAC layer, this application is not limited to this), or the selected beam to send the random access preamble code associated with the above beam, thereby performing a random access process to the target cell.

[0129] In the above embodiment, the beam configured by the RRC / beam indicated by the lower layer / selected beam is, for example, SSB, TRS or CSI-RS, but the present application is not limited thereto.

[0130] For example, the beam configured by RRC is the SSBs in candidateBeamRSList / rach-ConfigDedicated, or the CSI-RSs in candidateBeamRSList / rach-ConfigDedicated, and so on.

[0131] For another example, the beam indicated by the lower layer is the beam corresponding to the TCI state index indicated by the LTM cell switch command MAC CE.

[0132] For another example, the selected beam is an SSB whose SS-RSRP selected by the UE is greater than a configured threshold or a CSI-RS whose CSI-RSRP is greater than a configured threshold.

[0133] In the above embodiment, the random access process may be a contention-based random access process or a non-contention-based random access process.

[0134] In the above embodiment, the MAC layer of the terminal device can also put the first uplink data from the HARQ process (second HARQ process) cache corresponding to the first timer into the multiplexing and assembly entity; indicate to the upper layers that the first timer has timed out or stopped, or indicate (RACH-less) cell switching failure, or indicate radio link failure, or indicate execution failure recovery, and / or the terminal device can consider that the cell switching timer has timed out. In this way, based on the indication or the consideration that the cell switching timer has timed out, the terminal device can perform corresponding operations and provide the lower layer with the configuration required for the random access process, thereby ensuring that when the first timer is not running, the terminal device can perform the random access process to the target cell. Here, the cell switching timer is, for example, T304. For the meaning of T304, please refer to the relevant technology, and the explanation is omitted here.

[0135] In the above embodiment, the RRC layer of the terminal device may further instruct the MAC layer to execute a random access procedure to the target cell and deliver a CCCH message or a first RRC message to the lower layer, thereby triggering the MAC layer to execute the random access procedure to the target cell. In this way, the terminal device can reuse the existing random access initiation procedure as much as possible, thereby reducing terminal complexity and lowering terminal device costs.

[0136] According to the above embodiment, when the first timer is not running, the terminal device performs a random access-based cell handover. Thus, the terminal device can perform a random access process on the target cell, thereby completing LTM execution or completing LTM cell handover and continuing to send the first uplink data.

[0137] In some embodiments, the terminal device sends first uplink data using a dynamic grant, including:

[0138] The terminal device monitors the PDCCH on the activated BWP of the target cell;

[0139] If an uplink grant is received on the PDCCH of the MAC C-RNTI, a corresponding HARQ process (referred to as a first HARQ process) is determined; the HARQ process obtains the MAC PDU from a multiplexing and assembly entity.

[0140] In the above embodiment, the terminal device can put the first uplink data from the buffer of the HARQ process corresponding to the first timer (configuredGrantTimer) (the original HARQ process, that is, the HARQ process corresponding to the first uplink data transmission when the first timer is not running, referred to as the second HARQ process) into the multiplexing and assembly entity. As a result, the first HARQ process can obtain the MAC PDU of the first uplink data from the multiplexing and assembly entity, thereby completing the transmission of the first uplink data.

[0141] Alternatively, in the above embodiment, the terminal device (e.g., the RRC layer of the terminal device) may also submit the first RRC message, such as the RRC reconfiguration complete message (CCCH message), to the lower layer (e.g., PDCP / RLC / MAC) again. Thus, when the above-mentioned first HARQ process is determined by monitoring the PDCCH on the activated BWP of the target cell, the terminal device may obtain the MAC PDU including the first RRC message from the multiplexing and assembly entity as the first uplink data transmission, thereby completing the transmission of the first uplink data.

[0142] In the above example, the MAC layer of the terminal device may also indicate to upper layers that the first timer (configuredGrantTimer) has timed out, thereby triggering the terminal device to submit the above first RRC message to the lower layers.

[0143] According to the above embodiment, when the configured Grant Timer is not running, the terminal device uses the dynamic grant to send the first uplink data. Thus, the terminal device can continue to send the first uplink data on the target cell, thereby completing LTM execution or completing LTM cell handover.

[0144] In some embodiments, the first timer is a configured grant timer (configuredGrantTimer), and the terminal device starts or restarts the first timer, including at least one of the following:

[0145] Restarting the first timer;

[0146] Monitor the PDCCH on the activated BWP of the target cell, and if an uplink grant (i.e., DG retransmission) is received on the PDCCH of the CS-RNTI of the MAC entity, start or restart the first timer;

[0147] Monitor the PDCCH on the activated BWP of the target cell. If an uplink authorization (ie, DG retransmission) is received on the PDCCH of the CS-RNTI of the MAC entity, and if the CG retransmission timer (eg, cg-LTM-RetransmissionTimer) is not configured, start or restart the above-mentioned first timer.

[0148] In the above embodiment, the terminal device may use the above uplink grant to retransmit the first uplink data.

[0149] In some other embodiments, the first timer is a time alignment timer (timeAlignmentTimer), and the terminal device starts or restarts the first timer, including:

[0150] Restart the first timer.

[0151] In the above embodiment, when the cell handover is completed or the first uplink data is deemed to be successfully received, the first timer is stopped or deemed to have timed out or stopped, thereby avoiding transmission errors or inconsistencies between the terminal and the network caused by the continuous operation of the first timer.

[0152] According to the above embodiment, when the first timer is not running, the terminal device starts or restarts the first timer. Thus, the terminal device can continue to send the first uplink data during the running period of the first timer, thereby completing LTM execution or completing LTM cell switching.

[0153] In the previous embodiments, the processing of the terminal device when the first timer is not running is described. In other embodiments, the terminal device may also perform at least one of the above-mentioned processing (i.e., (1) fast recovery, (2) cell switching based on random access, (3) sending the first uplink data using dynamic authorization, or (4) starting or restarting the first timer) when the first timer is not running and a certain condition (referred to as the third condition) is met.

[0154] In the above embodiment, the third condition includes at least one of the following:

[0155] Cell handover is in progress;

[0156] The first uplink data (transmission) mentioned above is sent;

[0157] The first uplink data (transmission) is not considered to be successfully received;

[0158] The downlink assignment on the PDCCH for the C-RNTI of the MAC has not yet been received;

[0159] An uplink grant on the PDCCH of the C-RNTI of the MAC of the HARQ entity of the HARQ process corresponding to the first timer (the aforementioned second HARQ process) has not yet been received.

[0160] In the above embodiment, the cell handover is being performed, such as LTM, HO, or CHO, etc., which means that T304 is running. For the definition of T304, reference can be made to related technologies.

[0161] In the above embodiment, it is considered that the first uplink data (transmission) is successfully received, including receiving the downlink allocation on the PDCCH of the MAC's C-RNTI, or receiving the uplink authorization on the PDCCH of the MAC's C-RNTI of the HARQ entity of the HARQ process corresponding to the first timer (the aforementioned second HARQ process).

[0162] In the above embodiment, the first timer is a configured authorization timer. The present application is not limited thereto, and the first timer may also be a time alignment timer.

[0163] According to the above embodiment, when the first timer is not running, the terminal device continues to determine whether the above third condition is met. If the third condition is also met, the terminal device then performs at least one of the above four processes, thereby sending the first uplink data and / or continuing the cell switching process to complete the LTM execution or complete the LTM cell switching; or can quickly recover when the CG timer or TA timer (TAT) is not running, thereby reducing service interruption.

[0164] In some embodiments, as shown in FIG6 , the method further includes:

[0165] 620: The terminal device starts or restarts the first timer.

[0166] In the above embodiment, if the first timer is a configured grant timer (configuredGrantTimer), the terminal device may start or restart the first timer in the following situations, including but not limited to at least one of the following:

[0167] When transmitting, if no LBT failure indication is received from the lower layer, start or restart the first timer of the corresponding HARQ process;

[0168] Upon receiving an uplink grant of the C-RNTI of the MAC entity on the PDCCH, and the confirmed HARQ process is configured with the configured uplink grant, the first timer of the corresponding HARQ process is started or restarted;

[0169] When an uplink grant of the PDCCH occasion of the CS-RNTI of the MAC entity is received on the PDCCH, and the NDI in the received HARQ information is 1, the first timer of the corresponding HARQ process is started or restarted.

[0170] In the above embodiment, if the first timer is a time alignment timer (timeAlignmentTimer), the terminal device may start or restart the first timer in the following circumstances, including but not limited to at least one of the following:

[0171] When a cell handover command including a TAC is received, start or restart the first timer associated with the PTAG;

[0172] When receiving a cell handover command including target cell information, if the terminal device has a valid TA value for the target cell, start or restart the first timer associated with the PTAG;

[0173] When the configuration of the target cell is applied, the first timer associated with the PTAG is started or restarted.

[0174] In the above embodiment, the cell switching command may be an LTM cell switching command MAC CE (see the process shown in FIG2 ), or the cell switching command may be an RRC reconfiguration with sync message (see the process shown in FIG4 ).

[0175] In the above embodiment, the target cell may be a CHO candidate cell, the RRC layer of the terminal device may apply the configuration of the CHO candidate cell and provide a first indication to the MAC layer, and the MAC layer starts or restarts the first timer associated with the PTAG based on the first indication.

[0176] In the above embodiment, the target cell may also be an LTM candidate cell. The RRC layer of the terminal device may apply the configuration of the LTM candidate cell and provide a second indication to the MAC layer. The MAC layer starts or restarts the first timer associated with the PTAG based on the second indication.

[0177] The above embodiments are merely exemplary descriptions of the methods of the present application, but the present application is not limited thereto, and appropriate modifications may be made based on the above embodiments. For example, the above embodiments may be used individually, or one or more of the above embodiments may be combined.

[0178] The method of the embodiment of the present application is described below with reference to the scenarios shown in Figures 2, 4 and 5. The contents in brackets are optional or further explained or replaceable.

[0179] Taking the scenario shown in FIG. 2 as an example, as shown in FIG. 2 , the cell switching command is the cell switching command MAC CE in step 6, the target cell is one of the LTM candidate cells, and the configuration of the target cell is included in the LTM candidate configuration included in the RRC reconfiguration message in step 2.

[0180] In one example, the first timer is a configured authorization timer.

[0181] As shown in Figure 2, the terminal device performs DL and UL synchronization with the candidate cell in step 4 (4a / 4b). In step 6, the gNB decides to perform a cell handover to a target cell and sends a MAC CE including the candidate configuration index of the target cell to trigger the cell handover. The terminal device switches to the target cell and applies the configuration indicated by the candidate configuration index. Based on step 4b, the network device can include the terminal device's valid TA in the target cell in the MAC CE in step 6. In this way, the terminal device can send the first UL data to the target cell without performing a random access procedure to the target cell to complete the LTM cell handover process.

[0182] In the above example, sending the first UL data to the target cell includes: selecting the associated configured grant opportunities based on the beam information indicated in the MAC CE in step 6 (and RRC signaling, such as the configured grant provided in the RRC reconfiguration message including the LTM candidate configuration in step 2 of Figure 2) and considering them valid. The terminal device uses these configured grants for initial transmission and retransmission of the first UL data.

[0183] In the above example, the configured authorization is used for the initial transmission of the first UL data, including: for each configured authorization, if configured and activated, the terminal device (e.g., MAC entity) will set the HARQ process ID to the HARQ process ID associated with the PUSCH duration of the configured authorization (e.g., the second HARQ process); if the CG LTM retransmission timer is configured but the corresponding HARQ process is not running (if the configured authorization is for the initial transmission during LTM cell switching, i.e., the initial new transmission), the configured authorization and associated HARQ information are submitted to the above-mentioned second HARQ process.

[0184] In the above example, the initial transmission of the first UL data using the configured authorization also includes: for each configured authorization, the terminal device (e.g., a HARQ entity) will confirm the HARQ process associated with the configured authorization, (if the MAC PDU has not been obtained, if the authorization is a priority authorization,) obtain the MAC PDU from the multiplexing and assembly entity; submit the MAC PDU, the configured authorization and the HARQ information of the TB to the confirmed HARQ process; instruct the HARQ process to trigger a new transmission; when the transmission is in progress, (if no LBT failure indication is received from the lower layer,) if configured, start or restart the corresponding configured authorization timer (i.e., the first timer) of the HARQ process; start or restart the CG LTM retransmission timer.

[0185] In the above example, when the configured authorization timer times out, (if the first condition is met), the terminal device performs at least one of the following:

[0186] (1) Quick recovery.

[0187] When the configured authorization timer times out, the MAC layer (MAC entity) indicates to the upper layer that the cell handover has failed (optional);

[0188] (Based on the indication,) the terminal device (e.g., RRC) initiates an RRC connection reestablishment process, i.e., performs cell selection. If the selected cell is an LTM candidate cell and the network is configured to try LTM after failure, the terminal device attempts LTM on the candidate cell once, i.e., the terminal device applies the configuration of the LTM candidate cell (at this time, the terminal device executes a random access-based process, and the problem of the first timer timing out or stopping will not occur); otherwise (i.e., the selected cell is not an LTM candidate cell or the network is configured to try LTM after failure, at least one of the above), the terminal device sends an RRC connection reestablishment request.

[0189] (2) Cell switching based on random access.

[0190] For example (option 1):

[0191] When the configured grant timer expires, the terminal device (second HARQ process) puts the obtained MAC PDU (from the corresponding HARQ process buffer) into / back into the application and assembly entity;

[0192] When the configured authorization timer times out, the terminal device (MAC layer / MAC entity) initiates a random access process to the target cell.

[0193] Another example (option 2):

[0194] When the configured authorization timer times out, the MAC layer (MAC entity) indicates to the upper layer that the cell handover has failed (optional);

[0195] The RRC instructs the MAC to perform a random access procedure to the target cell (optional) and delivers a first RRC message (e.g., an RRC reconfiguration complete message) to the lower layer.

[0196] When the configured authorization timer times out, the terminal device (MAC layer / MAC entity) initiates a random access process to the target cell.

[0197] (3) Use dynamic authorization to send the first uplink data.

[0198] For example (option 1):

[0199] When the configured grant timer expires, the terminal device (second HARQ process) puts the obtained MAC PDU (from the corresponding HARQ process buffer) into / back into the application and assembly entity;

[0200] (If the configured grant timer expires,) the terminal device (MAC layer / MAC entity) monitors the PDCCH on the activated BWP of the target cell, and if an UL grant of the PDCCH with the MAC C-RNTI is received, determines the corresponding HARQ process (the first HARQ process);

[0201] The terminal device (first HARQ process) obtains the MAC PDU from the multiplexing and assembly entity.

[0202] Another example (option 2):

[0203] When the configured authorization timer times out, the MAC layer (MAC entity) indicates to the upper layer that the cell handover has failed (optional);

[0204] The RRC delivers a first RRC message (e.g., an RRC reconfiguration complete message) to the lower layer;

[0205] (If the configured grant timer expires,) the terminal device (MAC layer / MAC entity) monitors the PDCCH on the activated BWP of the target cell, and if an UL grant of the PDCCH with the MAC C-RNTI is received, determines the corresponding HARQ process (the first HARQ process);

[0206] The terminal device (first HARQ process) obtains the MAC PDU from the multiplexing and assembly entity.

[0207] (4) Start or restart the authorization timer for this configuration.

[0208] When the authorization timer for the configuration times out, restart the authorization timer for the configuration; or

[0209] (If the configured authorization timer times out,) the terminal device (MAC layer / MAC entity) monitors the PDCCH on the activated BWP of the target cell; when the configured authorization timer times out, if an UL authorization of the PDCCH of the CS-RNTI of the MAC is received (and if the CG LTM retransmission timer, such as cg-LTM-RetransmissionTimer, is not configured), the configured authorization timer is restarted; the second HARQ process (entity) uses the UL authorization to retransmit the first UL data.

[0210] In another example, the first timer is a time alignment timer.

[0211] As shown in Figure 2, the terminal device performs DL and UL synchronization with the candidate cell in step 4 (4a / 4b). In step 6, the gNB decides to perform a cell handover to a target cell and sends a MAC CE including the candidate configuration index of the target cell to trigger the cell handover. The terminal device switches to the target cell and applies the configuration indicated by the candidate configuration index. Based on step 4b, the network device can include the terminal device's valid TA on the target cell in the MAC CE in step 6, so that the terminal device can send the first UL data to the target cell without performing a random access procedure to the target cell to complete the LTM cell handover process.

[0212] In the above example, when the LTM cell handover command MAC CE including the valid TA (eg, TAC) is received, the time alignment timer associated with the PTAG is started or restarted.

[0213] In the above example, when the time alignment timer expires, (if the first condition is met), the terminal device performs at least one of the following:

[0214] (1) Quick recovery.

[0215] When the time alignment timer times out, the MAC layer (MAC entity) indicates to the upper layer that the time alignment timer has timed out or the cell handover has failed (optional);

[0216] (Based on this indication,) the terminal device (RRC) initiates the RRC connection reestablishment process, that is: performs cell selection. If the selected cell is an LTM candidate cell and the network is configured to try LTM after failure, the terminal device attempts LTM on the candidate cell once, that is, the terminal applies the configuration of the LTM candidate cell; otherwise (that is, the selected cell is not an LTM candidate cell or the network is configured to try LTM after failure), the terminal device sends an RRC connection reestablishment request.

[0217] (2) Cell switching based on random access.

[0218] For example (option 1):

[0219] When the time alignment timer expires, the terminal device (second HARQ process) puts the obtained MAC PDU (from the corresponding HARQ process buffer) into / back into the application and assembly entity;

[0220] When the time alignment timer times out, the terminal device (MAC layer / MAC entity) initiates a random access process to the target cell.

[0221] Another example (option 2):

[0222] When the time alignment timer times out, the MAC layer (MAC entity) indicates to the upper layer that the time alignment timer has timed out or the cell handover has failed (optional);

[0223] The RRC instructs the MAC to perform a random access procedure to the target cell (optional) and delivers a first RRC message (e.g., an RRC reconfiguration complete message) to the lower layer.

[0224] When the time alignment timer times out, the terminal device (MAC layer / MAC entity) initiates a random access process to the target cell.

[0225] (3) Start or restart the time alignment timer.

[0226] When the time alignment timer times out, restart the time alignment timer;

[0227] When the LTM cell handover is completed (successfully) or the first uplink data is considered to be successfully received, the time alignment timer is stopped or considered to have timed out.

[0228] Taking the scenario shown in FIG. 4 as an example, as shown in FIG. 4 , the cell switching command is the RRC reconfiguration message in step 6 .

[0229] In one example, the first timer is a configured authorization timer.

[0230] As shown in Figure 4, before step 2 or step 6, the terminal device performs DL synchronization and UL synchronization with the candidate cell. In step 6, the gNB decides to perform cell switching to a target cell and sends an RRC reconfiguration message including the configuration of the target cell to trigger the cell switching. The terminal device switches to the target cell and applies the configuration. Based on the previous DL / UL synchronization, the network can include the valid TA of the terminal device on the target cell in the RRC reconfiguration message in step 6, so that the terminal device can avoid the random access process to the target cell (that is, "detach from old cell Synchronise to new cell" can be modified to "detach from old cell, apply target configurations") and send the first UL data to the target cell to complete the cell switching process.

[0231] The following steps are similar to the scenario shown in Figure 2 where the first timer is a configured authorization timer. The difference from the scenario shown in Figure 2 where the first timer is a configured authorization timer is that the "MAC CE" in the above situation is replaced by an RRC reconfiguration message.

[0232] In another example, the first timer is a time alignment timer.

[0233] As shown in Figure 4, before step 2 or step 6, the terminal device performs DL synchronization and UL synchronization with the candidate cell. In step 6, the gNB decides to perform cell switching to a target cell and sends an RRC reconfiguration message including the configuration of the target cell to trigger the cell switching. The terminal device switches to the target cell and applies the configuration. Based on the previous DL / UL synchronization, the network can include the valid TA of the terminal device on the target cell in the RRC reconfiguration message in step 6, so that the terminal device can avoid the random access process to the target cell (that is, "detach from old cell Synchronise to new cell" can be modified to "detach from old cell, apply target configurations") and send the first UL data to the target cell to complete the cell switching process.

[0234] The following steps are similar to the scenario shown in Figure 2 where the first timer is the time alignment timer. The difference from the scenario shown in Figure 2 where the first timer is the time alignment timer is that the "LTM cell switching command MAC CE" in the above case is replaced by the RRC reconfiguration message (for (L3) cell switching) and the "LTM cell switching completed" is replaced by the (L3) cell switching completed.

[0235] Taking the scenario shown in FIG5 as an example, as shown in FIG5 , applying the configuration of the target cell is to determine the target cell after evaluating the CHO condition and apply its configuration.

[0236] In one example, the first timer is a configured authorization timer.

[0237] As shown in Figure 5, in step 6, the gNB provides the terminal device with the configuration of the candidate cell and the CHO evaluation conditions, and the terminal device performs the CHO condition evaluation; before "detaching from old cell Synchronise to new cell", the terminal device performs DL synchronization and UL synchronization with the candidate cell. The terminal device decides to perform cell handover to a target cell and apply the configuration of the target cell. Based on the previous DL / UL synchronization, the network can include the terminal device's valid TA on the target cell in the RRC reconfiguration message in step 6, so that the terminal device can avoid the random access process to the target cell (that is, "detach from old cell Synchronise to new cell" can be modified to "detach from old cell, apply target configurations") and send the first UL data to the target cell to complete the cell handover process.

[0238] The following steps are similar to the scenario shown in Figure 2 where the first timer is a configured authorization timer. The difference from the scenario shown in Figure 2 where the first timer is a configured authorization timer is that the "MAC CE" in the above situation is replaced by an RRC reconfiguration message.

[0239] In another example, the first timer is a time alignment timer.

[0240] As shown in Figure 5, in step 6, the gNB provides the terminal device with the configuration of the candidate cell and the CHO evaluation conditions, and the terminal performs the CHO condition evaluation; before "detaching from old cell Synchronise to new cell", the terminal device performs DL synchronization and UL synchronization with the candidate cell. The terminal device decides to perform cell handover to a target cell and apply the configuration of the target cell. Based on the previous DL / UL synchronization, the network can include the terminal device's valid TA on the target cell in the RRC reconfiguration message in step 6, so that the terminal device can avoid the random access process to the target cell (that is, "detach from old cell Synchronise to new cell" can be modified to "detach from old cell, apply target configurations") and send the first UL data to the target cell to complete the cell handover process.

[0241] The following steps are similar to the scenario shown in Figure 2 where the first timer is the time alignment timer. The difference from the scenario shown in Figure 2 where the first timer is the time alignment timer is that the "LTM cell switching command MAC CE" in the above case is replaced by the RRC reconfiguration message (for (L3) cell switching) and the "LTM cell switching completed" is replaced by the (L3) cell switching completed.

[0242] According to the method of an embodiment of the present application, when the first timer is not running, the terminal performs at least one of (1) fast recovery, (2) cell switching based on random access, (3) sending the first uplink data using dynamic authorization, or (4) starting or restarting the first timer. As a result, the terminal device can continue to transmit the first uplink data and / or continue the cell switching process when the first timer is not running, thereby ensuring that the LTM cell switching is successfully completed or the LTM execution is completed; or can perform fast recovery when the CG timer or TA timer (TAT) is not running, thereby reducing service interruption.

[0243] Embodiments of the second aspect

[0244] The embodiments of the present application provide a timer processing device, which may be, for example, a terminal device, or one or more components or assemblies configured on the terminal device. Because the principle of solving the problem of this device is the same as the method of the embodiment of the first aspect, its specific implementation can refer to the implementation of the method of the embodiment of the first aspect, and the same content will not be repeated here.

[0245] FIG7 is a schematic diagram of a timer processing device according to an embodiment of the present application. As shown in FIG7 , the device 700 includes:

[0246] The first processing unit 710 performs at least one of the following processes when the first timer is not running:

[0247] Quick recovery;

[0248] Cell switching based on random access;

[0249] Send the first uplink data using dynamic grant; and

[0250] Starting or restarting the first timer;

[0251] The first timer is a configured authorization timer or a time alignment timer.

[0252] In the embodiment of the present application, the first timer not running means at least one of the following:

[0253] A first timer is configured and times out;

[0254] A first timer is configured and stopped;

[0255] The first timer is not configured.

[0256] In some embodiments, the first processing unit 710 performs fast recovery when the first timer is not running, including: the first processing unit 710 initiates RRC connection reestablishment.

[0257] In the foregoing embodiment, the first processing unit 710 initiating RRC connection reestablishment may include:

[0258] The first processing unit 710 performs cell selection;

[0259] If the first condition is met, that is, the selected cell is a conditional handover (CHO) candidate cell and the network is configured to attempt CHO after failure, the first processing unit 710 attempts a CHO execution or the first processing unit 710 applies the configuration of the CHO candidate cell;

[0260] If the second condition is met, that is, the selected cell is an L1 / L2 triggered mobility (LTM) candidate cell and the network is configured to try LTM after failure, the first processing unit 710 attempts LTM to the candidate cell once or the first processing unit 710 applies the configuration of the LTM candidate cell;

[0261] If the first condition and / or the second condition is not met, the first processing unit 710 sends an RRC connection reestablishment request.

[0262] In the above embodiment, the first processing unit 710 performs fast recovery, which may further include:

[0263] The first processing unit 710 indicates to an upper layer, at a MAC layer of the terminal device, that the first timer has timed out or stopped, or indicates that a cell handover has failed, or indicates that a radio link has failed; or

[0264] The first processing unit 710 indicates to an upper layer at the MAC layer of the terminal device to perform failure recovery; or

[0265] The first processing unit 710 considers that the cell switching timer has timed out.

[0266] In some embodiments, the first processing unit 710 performs random access-based cell switching when the first timer is not running, including:

[0267] The first processing unit 710 performs a random access procedure to a target cell at a MAC layer of a terminal device.

[0268] In the above embodiment, the first processing unit 710 performs a random access process to a target cell at the MAC layer of the terminal device, which may include:

[0269] The first processing unit 710 uses a random access resource associated with a beam configured by RRC, a beam indicated by a lower layer, or a selected beam to send a random access preamble associated with the beam.

[0270] In the above embodiment, the random access process may be a contention-based random access process or a non-contention-based random access process.

[0271] In the above embodiment, the first processing unit 710 performs cell switching based on random access, further comprising at least one of the following:

[0272] The first processing unit 710 puts the first uplink data from the HARQ process buffer corresponding to the first timer into the multiplexing and assembly entity at the MAC layer of the terminal device;

[0273] The first processing unit 710 indicates to an upper layer, at a MAC layer of the terminal device, that the first timer has timed out or stopped, or indicates that a cell handover has failed, or indicates that failure recovery is to be performed;

[0274] The first processing unit 710 instructs the MAC layer at the RRC layer of the terminal device to perform a random access procedure to the target cell and submit a CCCH message or a first RRC message to a lower layer.

[0275] In some embodiments, the first processing unit 710 sends first uplink data using a dynamic grant when the first timer is not running, including:

[0276] The first processing unit 710 monitors the PDCCH on the activated BWP of the target cell;

[0277] If an uplink grant is received on the PDCCH of the MAC's C-RNTI, a corresponding HARQ process is determined; the HARQ process obtains the MAC PDU from the multiplexing and assembly entity.

[0278] In the above embodiment, the first timer may be a configured grant timer, and the first processing unit 710 may send the first uplink data using the dynamic grant, and may further include:

[0279] The first processing unit 710 puts the first uplink data from the buffer of the HARQ process corresponding to the first timer into the multiplexing and assembly entity.

[0280] Alternatively, in the foregoing embodiment, the first timer is a configured grant timer, and the first processing unit 710 sends the first uplink data using a dynamic grant, and may further include:

[0281] The first processing unit 710 delivers a first RRC message to a lower layer.

[0282] In the above embodiment, the first processing unit 710 may further indicate to an upper layer at the MAC layer of the terminal device that the first timer has timed out or has stopped.

[0283] In some embodiments, the first timer is a configured authorization timer, and the first processing unit 710 starts or restarts the first timer when the first timer is not running, including at least one of the following:

[0284] Restarting the first timer;

[0285] Monitor the PDCCH on the activated BWP of the target cell, and if an uplink grant is received on the PDCCH of the CS-RNTI of the MAC entity, start or restart the first timer;

[0286] Monitor the PDCCH on the activated BWP of the target cell, and if an uplink grant is received on the PDCCH of the CS-RNTI of the MAC entity, and if the CG retransmission timer is not configured, start or restart the first timer.

[0287] In some embodiments, the first timer is a time alignment timer, and the first processing unit 710 starts or restarts the first timer when the first timer is not running, including:

[0288] Restart the first timer, as described.

[0289] In the above embodiment, when the cell handover is completed or the first uplink data is considered to be successfully received, the first processing unit 710 stops the first timer or considers that the first timer has timed out or stopped.

[0290] In some embodiments, the first processing unit 710 performs at least one of the above processes when the first timer is not running and a third condition is satisfied; the third condition includes at least one of the following:

[0291] Cell handover is in progress;

[0292] The first uplink data is sent;

[0293] It is not considered that the first uplink data is successfully received;

[0294] The downlink allocation on the PDCCH of the C-RNTI of the MAC has not yet been received;

[0295] An uplink grant on the PDCCH of the C-RNTI of the MAC of the HARQ entity of the HARQ process corresponding to the first timer has not been received.

[0296] In some embodiments, as shown in FIG7 , the apparatus 700 further includes:

[0297] The second processing unit 720 starts or restarts the first timer.

[0298] In the above embodiment, if the first timer is a configured authorization timer, the second processing unit 720 starts or restarts the first timer, which may include:

[0299] The second processing unit 720 performs at least one of the following processes:

[0300] When transmitting, if no LBT failure indication is received from the lower layer, starting or restarting the first timer of the corresponding HARQ process;

[0301] Receiving an uplink grant of the C-RNTI of the MAC entity on the PDCCH, and confirming the uplink grant configured by the HARQ process, and starting or restarting the first timer of the corresponding HARQ process;

[0302] When an uplink grant of a PDCCH occasion of the CS-RNTI of the MAC entity is received on the PDCCH, and the NDI in the received HARQ information is 1, the first timer of the corresponding HARQ process is started or restarted.

[0303] In the above embodiment, if the first timer is a time alignment timer, the second processing unit 720 starts or restarts the first timer, which may include:

[0304] The second processing unit 720 performs at least one of the following processes:

[0305] When a cell handover command including a TAC is received, starting or restarting the first timer associated with the PTAG corresponding to the TAC;

[0306] When receiving a cell handover command including target cell information, if the terminal device has a valid TA value of the target cell, start or restart the first timer associated with the PTAG corresponding to the TA;

[0307] When the configuration of the target cell is applied, the first timer associated with the PTAG corresponding to the target cell is started or restarted.

[0308] In the above embodiment, the cell switching command may be an LTM cell switching command MAC CE, or an RRC reconfiguration with sync message.

[0309] In the above embodiment, the target cell can be a CHO candidate cell. The second processing unit 720 can apply the configuration of the above CHO candidate cell at the RRC layer of the terminal device and provide a first indication to the MAC layer. The MAC layer starts or restarts the first timer associated with the above PTAG based on the first indication.

[0310] In the above embodiment, the target cell may also be an LTM candidate cell. The second processing unit 720 applies the configuration of the above LTM candidate cell at the RRC layer of the terminal device and provides a second indication to the MAC layer. The MAC layer starts or restarts the first timer associated with the above PTAG based on the second indication.

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

[0312] It is worth noting that the above description only describes the components or modules relevant 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, each of the above-mentioned components or modules may be implemented using hardware facilities such as processors, memories, transmitters, and receivers; the implementation of this application is not limited to this.

[0313] According to the apparatus of the embodiment of the present application, the terminal device can continue to transmit the first uplink data and / or continue the cell switching process when the first timer is not running, thereby ensuring the successful completion of the LTM cell switching or the completion of the LTM execution; or can quickly recover when the CG timer or TA timer (TAT) is not running, thereby reducing service interruption.

[0314] Embodiments of the third aspect

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

[0316] FIG8 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 FIG8 , a communication system 800 may include a network device 801 and terminal devices 802 and 803. For simplicity, FIG8 illustrates only two terminal devices and one network device as an example, but the embodiments of the present application are not limited thereto.

[0317] In the embodiment of the present application, existing services or future services can be transmitted between the network device 801 and the terminal devices 802 and 803. 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.

[0318] It is worth noting that FIG8 shows that both terminal devices 802 and 803 are within the coverage range of network device 801, but the present application is not limited thereto. Both terminal devices 802 and 803 may not be within the coverage range of network device 801, or one terminal device 802 may be within the coverage range of network device 801 while the other terminal device 803 is outside the coverage range of network device 801.

[0319] In some embodiments, the terminal device includes the apparatus 700 described in the embodiment of the second aspect, and is configured to perform the method described in 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.

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

[0321] Figure 9 is a schematic diagram of a terminal device according to an embodiment of the present application. As shown in Figure 9 , terminal device 900 may include a processor 901 and a memory 902. Memory 902 stores data and programs and is coupled to processor 901. 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.

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

[0323] In other embodiments, the device 700 of the embodiment of the second aspect can be configured separately from the processor 901. For example, the device 700 of the embodiment of the second aspect can be configured as a chip connected to the processor 901, and the functions of the device 700 of the embodiment of the second aspect can be realized through the control of the processor 901.

[0324] As shown in Figure 9 , the terminal device 900 may further include: a communication module 903, an input unit 904, a display 905, and a power supply 906. 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 900 does not necessarily include all of the components shown in Figure 9 , and these components are not essential. Furthermore, the terminal device 900 may also include components not shown in Figure 9 , for which reference may be made to related art.

[0325] An embodiment of the present application further 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 the embodiment of the first aspect.

[0326] 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 the embodiment of the first aspect.

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

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

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

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

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

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

[0333] 1. A timer processing method, wherein the method comprises:

[0334] When the first timer is not running, the terminal device performs at least one of the following processes:

[0335] Quick recovery;

[0336] Cell switching based on random access;

[0337] Send the first uplink data using dynamic grant; and

[0338] Starting or restarting the first timer;

[0339] The first timer is a configured authorization timer or a time alignment timer.

[0340] 2. The method according to Supplementary Note 1, wherein the terminal device performs a fast recovery, comprising:

[0341] The terminal device initiates RRC connection reconstruction.

[0342] 3. The method according to Supplementary Note 2, wherein the terminal device performs a fast recovery, further comprising:

[0343] The MAC layer of the terminal device indicates to the upper layer that the first timer has timed out or stopped, or indicates that the cell handover has failed, or indicates that the radio link has failed; or

[0344] The MAC layer of the terminal device instructs the upper layer to perform failure recovery; or

[0345] The terminal device considers that the cell switching timer has timed out.

[0346] 4. The method according to Supplementary Note 1, wherein the terminal device performs cell switching based on random access, comprising:

[0347] The MAC layer of the terminal device performs a random access process to the target cell.

[0348] 5. The method according to Note 4, wherein the MAC layer of the terminal device performs a random access procedure to the target cell, comprising:

[0349] The terminal device uses the random access resources associated with the beam configured by RRC, the beam indicated by the lower layer, or the selected beam to send the random access preamble code associated with the beam.

[0350] 6. The method according to Supplement 4 or 5, wherein:

[0351] The random access procedure is a contention-based random access procedure, or the random access procedure is a non-contention-based random access procedure.

[0352] 7. The method according to any one of Notes 1 to 6, further comprising:

[0353] The terminal device starts or restarts the first timer.

[0354] 8. The method according to Supplementary Note 7, wherein the first timer is a time alignment timer, and the terminal device starts or restarts the first timer, including at least one of the following:

[0355] When a cell handover command including a TAC is received, starting or restarting the first timer associated with the PTAG corresponding to the TAC;

[0356] When receiving a cell handover command including target cell information, if the terminal device has a valid TA value of the target cell, start or restart the first timer associated with the PTAG corresponding to the TA;

[0357] When the configuration of the target cell is applied, the first timer associated with the PTAG corresponding to the target cell is started or restarted.

[0358] 9. The method according to Supplementary Note 8, wherein:

[0359] The target cell is a CHO candidate cell, the RRC layer of the terminal device applies the configuration of the CHO candidate cell and provides a first indication to the MAC layer, and the MAC layer starts or restarts the first timer associated with the PTAG based on the first indication.

[0360] 10. The method according to Supplementary Note 8, wherein:

[0361] The target cell is an LTM candidate cell, the RRC layer of the terminal device applies the configuration of the LTM candidate cell and provides a second indication to the MAC layer, and the MAC layer starts or restarts the first timer associated with the PTAG based on the second indication.

Claims

1. A timer processing device, configured in a terminal device, wherein: The device comprises: The first processing unit performs at least one of the following processes when the first timer is not running: Quick recovery; Cell switching based on random access; Send the first uplink data using dynamic grant; and Starting or restarting the first timer; The first timer is a configured authorization timer or a time alignment timer.

2. The device according to claim 1, wherein: The first timer not running means at least one of the following: The first timer is configured and times out; The first timer is configured and stopped; The first timer is not configured.

3. The device according to claim 1, wherein: The first processing unit performs fast recovery, including: The first processing unit initiates RRC connection reestablishment.

4. The device according to claim 3, wherein: The first processing unit initiating RRC connection reestablishment includes: The first processing unit performs cell selection; If the first condition is met, that is, the selected cell is a conditional handover (CHO) candidate cell and the network is configured to attempt CHO after failure, the first processing unit attempts a CHO execution or the first processing unit applies the configuration of the CHO candidate cell; If the second condition is met, that is, the selected cell is an L1 / L2 triggered mobility (LTM) candidate cell and the network is configured to try LTM after failure, the first processing unit attempts LTM to the candidate cell once or the first processing unit applies the configuration of the LTM candidate cell; If the first condition and / or the second condition is not met, the first processing unit sends an RRC connection reestablishment request.

5. The device according to claim 1, wherein: The first processing unit performs cell switching based on random access, including: The first processing unit performs a random access process to a target cell at a MAC layer of the terminal device.

6. The device according to claim 5, wherein: The first processing unit performs cell switching based on random access, further comprising at least one of the following: The first processing unit puts the first uplink data from the HARQ process buffer corresponding to the first timer into the multiplexing and assembly entity at the MAC layer of the terminal device; The first processing unit indicates to an upper layer at a MAC layer of the terminal device that the first timer has timed out or stopped, or indicates that a cell handover has failed, or indicates that failure recovery has been performed; The first processing unit instructs the MAC layer at the RRC layer of the terminal device to execute a random access process to the target cell and submit a CCCH message or a first RRC message to a lower layer.

7. The device according to claim 1, wherein: The first processing unit sends first uplink data using the dynamic grant, including: The first processing unit monitors the PDCCH on the activated BWP of the target cell; If an uplink grant on the PDCCH of the C-RNTI of the MAC is received, a corresponding HARQ process is determined; the HARQ process obtains the MAC PDU from the multiplexing and assembly entity.

8. The device according to claim 7, wherein: The first timer is a configured authorization timer, and the first processing unit sends the first uplink data using dynamic authorization, further comprising: The first processing unit puts the first uplink data from the cache of the HARQ process corresponding to the first timer into the multiplexing and assembly entity.

9. The device according to claim 7, wherein: The first timer is a configured authorization timer, and the first processing unit sends the first uplink data using dynamic authorization, further comprising: The first processing unit delivers a first RRC message to a lower layer.

10. The device according to claim 9, wherein: The first processing unit also indicates to an upper layer at the MAC layer of the terminal device that the first timer has timed out or stopped.

11. The device according to claim 1, wherein: The first timer is a configured authorization timer, and the first processing unit starts or restarts the first timer, including at least one of the following: Restarting the first timer; Monitor the PDCCH on the activated BWP of the target cell, and if an uplink grant is received on the PDCCH of the CS-RNTI of the MAC entity, start or restart the first timer; Monitor the PDCCH on the activated BWP of the target cell, and if an uplink grant is received on the PDCCH of the CS-RNTI of the MAC entity, and if the CG retransmission timer is not configured, start or restart the first timer.

12. The device according to claim 1, wherein: The first timer is a time alignment timer, and the first processing unit starts or restarts the first timer, including: The first processing unit restarts the first timer.

13. The device according to claim 12, wherein: When the cell switching is completed or it is considered that the first uplink data is successfully received, the first processing unit stops the first timer or considers that the first timer has timed out or stopped.

14. The device according to claim 1, wherein: The first processing unit performs at least one of the above processes when the first timer is not running and the third condition is met; The third condition includes at least one of the following: Cell switching is in progress; The first uplink data is sent; It is not considered that the first uplink data is successfully received; The downlink allocation on the PDCCH of the C-RNTI of the MAC has not yet been received; An uplink grant on the PDCCH of the C-RNTI of the MAC of the HARQ entity of the HARQ process corresponding to the first timer has not been received.

15. The device according to claim 1, wherein: The device also includes: The second processing unit starts or restarts the first timer.

16. The device according to claim 15, wherein: The first timer is a configured authorization timer, and the second processing unit starts or restarts the first timer, including at least one of the following: When transmitting, if no LBT failure indication is received from the lower layer, starting or restarting the first timer of the corresponding HARQ process; Receiving an uplink grant of the C-RNTI of the MAC entity on the PDCCH, and confirming that the HARQ process is configured with the uplink grant of the configuration, and starting or restarting the first timer of the corresponding HARQ process; When an uplink grant of the PDCCH occasion of the CS-RNTI of the MAC entity is received on the PDCCH, and the NDI in the received HARQ information is 1, the first timer of the corresponding HARQ process is started or restarted.

17. The device according to claim 15, wherein: The first timer is a time alignment timer, and the second processing unit starts or restarts the first timer, including at least one of the following: When a cell handover command including the TAC is received, starting or restarting the first timer associated with the PTAG corresponding to the TAC; When receiving a cell handover command including target cell information, if the terminal device has a valid TA value of the target cell, start or restart the first timer associated with the PTAG corresponding to the TA reference; When the configuration of the target cell is applied, the first timer associated with the PTAG corresponding to the target cell is started or restarted.

18. The device according to claim 17, wherein: The cell switching command is an LTM cell switching command MAC CE, or, The cell switching command is an RRC reconfiguration with sync message.

19. A terminal device, characterized in that: The terminal device includes a memory and a processor, the memory stores a computer program, and the processor is configured to execute the computer program to implement the following method: When the first timer is not running, at least one of the following processes is performed: Quick recovery; Cell switching based on random access; Send the first uplink data using dynamic grant; and Starting or restarting the first timer; The first timer is a configured authorization timer or a time alignment timer.

20. A communication system, characterized in that: The communication system includes a network device and the terminal device described in claim 19.

Images