Wireless communication method and terminal equipment

Abstract

The invention provides a wireless communication method and terminal equipment. The terminal equipment can avoid transmission of unnecessary RRC messages when switching back to a source cell after DAPS switching fails. The wireless communication method comprises the following steps: the terminal equipment receives a switching command, wherein the switching command is used for indicating the terminal equipment to switch from a source cell to a target cell by adopting a DAPS switching mode; and under the condition that the DAPS switching fails and the source cell does not detect a radio link failure, the terminal equipment executes at least one of the following operations: indicating a PDCP layer corresponding to at least one SRB of the source cell to suspend a PDCP entity, reestablishing an RLC entity corresponding to at least one SRB of the source cell, and triggering a PDCP SDU deletion process.

Description

[0001] This application is a divisional application of the patent application filed on May 21, 2020, with application number 202010438172.2 and application name “Wireless Communication Method and Terminal Device”. Technical Field

[0002] The present invention relates to the field of communications, and more particularly, to a wireless communication method and terminal equipment. Background Art

[0003] In the New Radio (NR) and Long Term Evolution (LTE) systems, the dual active protocol stack (DAPS) is introduced to optimize the handover process to reduce the interruption time during the handover process. However, at this stage, it is not involved in how to handle the Radio Resource Control (RRC) messages cached in the source cell during DAPS handover to affect DAPS handover. Summary of the invention

[0004] The present application provides a wireless communication method and a terminal device, wherein the terminal device deletes an old RRC message cached in a source cell during a DAPS switching process, so that the terminal device can avoid transmitting unnecessary RRC messages when switching back to the source cell after a DAPS switching failure.

[0005] In a first aspect, a wireless communication method is provided, comprising:

[0006] The terminal device receives a handover command, where the handover command is used to instruct the terminal device to switch from a source cell to a target cell using a DAPS handover mode;

[0007] When the terminal device suspends at least one signaling radio bearer (SRB) of the source cell according to the handover command, the terminal device performs at least one of the following operations:

[0008] instructing a Packet Data Convergence Protocol (PDCP) entity corresponding to the at least one SRB to suspend the PDCP entity,

[0009] reestablishing a radio link control (RLC) entity corresponding to the at least one SRB,

[0010] Trigger the PDCP service data unit (SDU) deletion process.

[0011] In a second aspect, a wireless communication method is provided, including:

[0012] The terminal device receives a handover command, where the handover command is used to instruct the terminal device to switch from a source cell to a target cell using a DAPS handover mode;

[0013] In the case where the DAPS handover fails and the source cell does not detect a radio link failure, the terminal device performs at least one of the following operations:

[0014] Instruct the PDCP layer corresponding to at least one SRB of the source cell to suspend the PDCP entity,

[0015] Reestablishing the RLC entity corresponding to at least one SRB of the source cell,

[0016] Trigger the PDCP SDU deletion procedure.

[0017] In a third aspect, a terminal device is provided for executing the method in the first aspect or its various implementations.

[0018] Specifically, the terminal device includes a functional module for executing the method in the above-mentioned first aspect or its various implementation modes.

[0019] In a fourth aspect, a terminal device is provided for executing the method in the above-mentioned second aspect or its various implementation modes.

[0020] Specifically, the terminal device includes a functional module for executing the method in the above-mentioned second aspect or its various implementation modes.

[0021] In a fifth aspect, a terminal device is provided, comprising a processor and a memory, wherein the memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory to execute the method in the first aspect or its implementation manners.

[0022] In a sixth aspect, a terminal device is provided, comprising a processor and a memory, wherein the memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory to execute the method in the second aspect or its implementation manners.

[0023] In a seventh aspect, a device is provided for implementing the method in any one of the first to second aspects or any of their implementations.

[0024] Specifically, the apparatus includes: a processor, configured to call and run a computer program from a memory, so that a device equipped with the apparatus executes a method as described in any one of the first to second aspects or in each of their implementations.

[0025] In an eighth aspect, a computer-readable storage medium is provided for storing a computer program, wherein the computer program enables a computer to execute the method of any one of the first to second aspects or any of their implementations.

[0026] In a ninth aspect, a computer program product is provided, comprising computer program instructions, wherein the computer program instructions enable a computer to execute the method in any one of the first to second aspects above or in each of their implementations.

[0027] In a tenth aspect, a computer program is provided, which, when executed on a computer, enables the computer to execute the method in any one of the first to second aspects or in each of their implementations.

[0028] Through the above technical solution, the terminal device deletes the old RRC message cached in the source cell during the DAPS switching process, so that the terminal device can avoid transmitting unnecessary RRC messages when switching back to the source cell after the DAPS switching fails. BRIEF DESCRIPTION OF THE DRAWINGS

[0029] Figure 1 It is a schematic diagram of a communication system architecture provided in an embodiment of the present application.

[0030] Figure 2 It is a schematic flowchart of a wireless communication method provided according to an embodiment of the present application.

[0031] Figure 3 It is a schematic flowchart of another wireless communication method provided according to an embodiment of the present application.

[0032] Figure 4 It is a schematic block diagram of a terminal device provided according to an embodiment of the present application.

[0033] Figure 5 It is a schematic block diagram of another terminal device provided according to an embodiment of the present application.

[0034] Figure 6 It is a schematic block diagram of a communication device provided according to an embodiment of the present application.

[0035] Figure 7 It is a schematic block diagram of a device provided according to an embodiment of the present application.

[0036] Figure 8 It is a schematic block diagram of a communication system provided according to an embodiment of the present application. DETAILED DESCRIPTION

[0037] The following will describe the technical solutions in the embodiments of the present application in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, not all of the embodiments. For the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0038] The technical solutions of the embodiments of the present application can be applied to various communication systems, such as: Global System of Mobile communication (GSM) system, Code Division Multiple Access (CDMA) system, Wideband Code Division Multiple Access (WCDMA) system, General Packet Radio Service (GPRS), Long Term Evolution (LTE) system, Advanced Long Term Evolution (LTE-A) system, New Radio (NR) system, NR system evolution system, LTE on unlicensed spectrum (LTE-U) system, NR on unlicensed spectrum (NR-U) system, Non-Terrestrial Networks (NTN) system, Universal Mobile Telecommunication System (UMTS), Wireless Local Area Networks (WLAN), Wireless Fidelity (Wireless Fidelity) system. Fidelity, WiFi), fifth-generation communication (5th-Generation, 5G) system or other communication systems, etc.

[0039] Generally speaking, traditional communication systems support a limited number of connections and are easy to implement. However, with the development of communication technology, mobile communication systems will not only support traditional communications, but will also support, for example, device to device (Device to Device, D2D) communication, machine to machine (Machine to Machine, M2M) communication, machine type communication (Machine Type Communication, MTC), vehicle to vehicle (V2V) communication, or vehicle to everything (V2X) communication, etc. The embodiments of the present application can also be applied to these communication systems.

[0040] Optionally, the communication system in the embodiment of the present application can be applied to a carrier aggregation (CA) scenario, a dual connectivity (DC) scenario, or a standalone (SA) networking scenario.

[0041] Optionally, the communication system in the embodiment of the present application can be applied to an unlicensed spectrum, wherein the unlicensed spectrum can also be considered as a shared spectrum; or, the communication system in the embodiment of the present application can also be applied to an authorized spectrum, wherein the authorized spectrum can also be considered as an unshared spectrum.

[0042] The embodiments of the present application describe various embodiments in conjunction with network devices and terminal devices, wherein the terminal device may also be referred to as user equipment (UE), access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent or user device, etc.

[0043] The terminal device can be a station (STAION, ST) in a WLAN, a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA) device, a handheld device with wireless communication function, a computing device or other processing device connected to a wireless modem, a vehicle-mounted device, a wearable device, a terminal device in a next-generation communication system such as an NR network, or a terminal device in a future evolved Public Land Mobile Network (PLMN) network, etc.

[0044] In the embodiments of the present application, the terminal device can be deployed on land, including indoors or outdoors, handheld, wearable or vehicle-mounted; it can also be deployed on the water surface (such as ships, etc.); it can also be deployed in the air (for example, on airplanes, balloons and satellites, etc.).

[0045] In the embodiment of the present application, the terminal device can be a mobile phone, a tablet computer, a computer with wireless transceiver function, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal device in industrial control, a wireless terminal device in self driving, a wireless terminal device in remote medical, a wireless terminal device in a smart grid, a wireless terminal device in transportation safety, a wireless terminal device in a smart city, or a wireless terminal device in a smart home, etc.

[0046] As an example but not limitation, in the embodiments of the present application, the terminal device may also be a wearable device. Wearable devices may also be referred to as wearable smart devices, which are a general term for wearable devices that are intelligently designed and developed using wearable technology for daily wear, such as glasses, gloves, watches, clothing, and shoes. A wearable device is a portable device that is worn directly on the body or integrated into the user's clothes or accessories. Wearable devices are not only hardware devices, but also powerful functions achieved through software support, data interaction, and cloud interaction. Broadly speaking, wearable smart devices include full-featured, large-sized, and fully or partially independent of smartphones, such as smart watches or smart glasses, as well as devices that only focus on a certain type of application function and need to be used in conjunction with other devices such as smartphones, such as various types of smart bracelets and smart jewelry for vital sign monitoring.

[0047] In an embodiment of the present application, the network device may be a device for communicating with a mobile device. The network device may be an access point (AP) in WLAN, a base station (Base Transceiver Station, BTS) in GSM or CDMA, a base station (NodeB, NB) in WCDMA, an evolved base station (EvolutionalNode B, eNB or eNodeB) in LTE, or a relay station or access point, or a vehicle-mounted device, a wearable device, and a network device (gNB) in an NR network, or a network device in a future evolved PLMN network, or a network device in an NTN network, etc.

[0048] As an example but not limitation, in an embodiment of the present application, the network device may have a mobile characteristic, for example, the network device may be a mobile device. Optionally, the network device may be a satellite or a balloon station. For example, the satellite may be a low earth orbit (LEO) satellite, a medium earth orbit (MEO) satellite, a geostationary earth orbit (GEO) satellite, a high elliptical orbit (HEO) satellite, etc. Optionally, the network device may also be a base station set up in a location such as land or water.

[0049] In an embodiment of the present application, the network device can provide services for a cell, and the terminal device communicates with the network device through the transmission resources used by the cell (for example, frequency domain resources, or spectrum resources). The cell can be a cell corresponding to the network device (for example, a base station). The cell can belong to a macro base station or a base station corresponding to a small cell. The small cells here may include: metro cells, micro cells, pico cells, femto cells, etc. These small cells have the characteristics of small coverage and low transmission power, and are suitable for providing high-speed data transmission services.

[0050] For example, the communication system 100 used in the embodiment of the present application is as follows: Figure 1 The communication system 100 may include a network device 110, which may be a device that communicates with a terminal device 120 (or referred to as a communication terminal or terminal). The network device 110 may provide communication coverage for a specific geographical area and may communicate with terminal devices located in the coverage area.

[0051] Figure 1One network device and two terminal devices are shown exemplarily. Optionally, the communication system 100 may include multiple network devices and each network device may include another number of terminal devices within its coverage area, which is not limited in the embodiments of the present application.

[0052] Optionally, the communication system 100 may also include other network entities such as a network controller and a mobility management entity, which is not limited in the embodiments of the present application.

[0053] It should be understood that the device with communication function in the network / system in the embodiment of the present application can be referred to as a communication device. Figure 1 Taking the communication system 100 shown as an example, the communication equipment may include a network device 110 and a terminal device 120 with communication functions. The network device 110 and the terminal device 120 may be the specific devices described above and will not be repeated here. The communication equipment may also include other devices in the communication system 100, such as a network controller, a mobile management entity and other network entities, which is not limited in the embodiments of the present application.

[0054] It should be understood that the terms "system" and "network" are often used interchangeably in this article. The term "and / or" in this article is only a description of the association relationship of associated objects, indicating that three relationships can exist. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character " / " in this article generally indicates that the associated objects before and after are in an "or" relationship.

[0055] It should be understood that the "indication" mentioned in the embodiments of the present application can be a direct indication, an indirect indication, or an indication of an association relationship. For example, A indicates B, which can mean that A directly indicates B, for example, B can be obtained through A; it can also mean that A indirectly indicates B, for example, A indicates C, and B can be obtained through C; it can also mean that there is an association relationship between A and B.

[0056] In the description of the embodiments of the present application, the term "corresponding" may indicate a direct or indirect correspondence between two items, or an association relationship between the two items, or a relationship between indication and being indicated, configuration and being configured, and the like.

[0057] In the relevant research on mobility enhancement of the 3rd Generation Partnership Project (3GPP), including LTE and NR, a DAPS optimization method for reducing the interruption time during switching is proposed. The main idea is that the terminal device will maintain the protocol stacks of the source cell and the target cell at the same time during the switching. When the terminal device receives the DAPS switching command, it maintains the connection of the source cell and initiates a synchronization process / random access to the target cell. When the synchronization process / random access is completed, the terminal device will switch the uplink data, that is, the uplink data transmission of the terminal device after random access will be switched from the source base station side to the target base station side. The release of the source base station protocol stack after random access is based on the display indication of the network, that is, during the period from random access to releasing the connection on the source base station side, the terminal device can normally receive the downlink data sent by the source cell, and can send uplink feedback related information of the downlink data to the source cell.

[0058] For DAPS switching, during the period when the terminal device initiates random access to the target cell, the terminal device will maintain monitoring of the wireless link of the source cell. If the link of the source cell fails, the terminal device will release the connection with the source cell and stop sending and receiving data with the source cell. In addition, if the DAPS switching fails, the terminal device does not successfully access the target cell, and the wireless link failure does not occur in the source cell, the terminal device can switch back to the connection with the source cell, thereby avoiding the RRC connection re-establishment process caused by the switching failure.

[0059] It should be noted that, in the DAPS handover process, it is not involved how to handle the old RRC messages cached in the source cell, which affects the DAPS handover. For example, when the SRB of the source cell is restored due to a DAPS handover failure, how to handle the old RRC messages cached in the source cell.

[0060] Based on the above problems, the present application proposes a DAPS switching solution, in which the terminal device deletes the old RRC messages cached in the source cell during the DAPS switching process, so that the terminal device can avoid transmitting unnecessary RRC messages when switching back to the source cell after a DAPS switching failure.

[0061] The technical solution of the present application is described in detail below through specific embodiments.

[0062] Figure 2 is a schematic flow chart of a wireless communication method 200 according to an embodiment of the present application, such as Figure 2 As shown, the method 200 may include but is not limited to the following:

[0063] S210, the terminal device receives a handover command, where the handover command is used to instruct the terminal device to switch from a source cell to a target cell using a DAPS handover mode;

[0064] S220: When the terminal device suspends at least one SRB of the source cell according to the handover command, the terminal device performs at least one of the following operations:

[0065] instructing the PDCP entity corresponding to the at least one SRB to suspend the PDCP entity,

[0066] reestablishing the RLC entity corresponding to the at least one SRB,

[0067] Trigger the PDCP SDU deletion procedure.

[0068] It should be understood that the source base station serves the source cell, and the target base station serves the target cell.

[0069] It should be noted that the handover command (HO command) may also be referred to as RRC reconfiguration information (RRC reconfiguration).

[0070] It should be understood that during DAPS switching, the terminal device will maintain the protocol stacks of both the source cell and the target cell.

[0071] Optionally, the handover command may be sent by the source base station. That is, the above step S210 may specifically be: the terminal device receives the handover command sent by the source base station.

[0072] Optionally, in an embodiment of the present application, the terminal device may suspend at least one SRB of the source cell according to the switching command. In addition, the terminal device may also initiate a synchronization process / random access to the target cell according to the switching command.

[0073] It should be noted that the random access may be a two-step random access or a four-step random access.

[0074] Optionally, the embodiments of the present application may be applied to a licensed frequency band or to an unlicensed frequency band, and the present application is not limited to this.

[0075] In the embodiment of the present application, suspend may also be expressed as pause, or other words with similar meanings.

[0076] It should be noted that the at least one SRB may be all SRBs of the source cell or part of the SRBs of the source cell, which is not limited in the present application.

[0077] In an embodiment of the present application, when the terminal device suspends at least one SRB of the source cell according to a handover command, the terminal device instructs the PDCP entity corresponding to at least one SRB to suspend the PDCP entity, that is, the terminal device can process the old RRC message cached in the PDCP entity of the source cell during the DAPS handover process. Similarly, when the terminal device suspends at least one SRB of the source cell according to a handover command, the terminal device rebuilds the RLC entity corresponding to at least one SRB, that is, the terminal device can process the old RRC message cached in the RLC entity of the source cell during the DAPS handover process. Similarly, when the terminal device suspends at least one SRB of the source cell according to a handover command, the terminal device triggers the PDCP SDU deletion process, that is, the terminal device can delete the old RRC message cached in the PDCP SDU of the source cell during the DAPS handover process.

[0078] Optionally, as Example 1, when the terminal device instructs the PDCP entity corresponding to the at least one SRB to suspend the PDCP entity, the terminal device deletes all PDCP protocol data units (Protocol Data Unit, PDU) and / or PDCP SDU of the PDCP entity corresponding to the at least one SRB.

[0079] That is, in Example 1, the terminal device can instruct the PDCP entity corresponding to the at least one SRB to suspend the PDCP entity during the DAPS switching process, and delete the old RRC messages cached in all PDCP PDUs and / or PDCP SDUs of the PDCP entity corresponding to the at least one SRB.

[0080] Optionally, in Example 1, the terminal device may also reset the status information of the PDCP entity corresponding to the at least one SRB. For example, the terminal device resets the timer configured in the PDCP entity corresponding to the at least one SRB, and / or the terminal device initializes the status variable of the PDCP entity corresponding to the at least one SRB.

[0081] Optionally, the timer configured in the PDCP entity corresponding to the at least one SRB may be a timer for deletion and / or sorting.

[0082] Optionally, as Example 2, when the terminal device reconstructs the RLC entity corresponding to the at least one SRB, the terminal device deletes all data in the cache of the RLC entity corresponding to the at least one SRB.

[0083] Optionally, the all data includes at least one of the following:

[0084] All RLC SDUs, all RLC PDUs, RLC SDU segments.

[0085] That is to say, in Example 2, the terminal device can rebuild the RLC entity corresponding to the at least one SRB during the DAPS switching process, and delete all data in the cache of the RLC entity corresponding to the at least one SRB, that is, delete all cached old RRC messages in the RLC entity.

[0086] Optionally, in Example 2, the terminal device resets the state information of the RLC entity corresponding to the at least one SRB. For example, the terminal device resets the timer configured in the RLC entity corresponding to the at least one SRB, and / or the terminal device initializes the state variable of the RLC entity corresponding to the at least one SRB.

[0087] Optionally, the timer configured in the RLC entity corresponding to the at least one SRB may be a timer used for deletion and / or sorting.

[0088] Optionally, as Example 3, when the terminal device triggers the PDCP SDU deletion process, the terminal device deletes all PDCP PDUs and / or PDCP SDUs of the PDCP entity corresponding to the at least one SRB.

[0089] That is, in Example 3, the terminal device can trigger the PDCP SDU deletion process during the DAPS switching process, and delete the oldRRC message in the cache of all PDCP PDUs and / or PDCP SDUs of the PDCP entity corresponding to the at least one SRB.

[0090] It should be noted that, in an embodiment of the present application, after receiving the handover command and before suspending at least one SRB of the source cell according to the handover command, the terminal device may perform some other operations. For example, for each SRB, one or more RLC entities are established for the target cell using the same configuration as the source cell. For another example, for each SRB, a logical channel is established for the target primary cell (Primary Cell, PCell) using the same configuration as the source cell.

[0091] Therefore, in an embodiment of the present application, during the DAPS switching process, the terminal device hangs up at least one SRB of the source cell according to the switching command, and deletes the old RRC message cached in the source cell, so that the terminal device can avoid transmitting unnecessary RRC messages when switching back to the source cell after the DAPS switching fails.

[0092] Figure 3is a schematic flow chart of a wireless communication method 300 according to an embodiment of the present application, such as Figure 3 As shown, the method 300 may include but is not limited to the following:

[0093] S310, the terminal device receives a handover command, where the handover command is used to instruct the terminal device to switch from a source cell to a target cell using a DAPS handover mode;

[0094] S320: When the DAPS handover fails and the source cell does not detect a radio link failure, the terminal device performs at least one of the following operations:

[0095] Instruct the PDCP layer corresponding to at least one SRB of the source cell to suspend the PDCP entity,

[0096] Reestablishing the RLC entity corresponding to at least one SRB of the source cell,

[0097] Trigger the PDCP SDU deletion procedure.

[0098] It should be understood that the source base station serves the source cell, and the target base station serves the target cell.

[0099] It should be noted that the handover command may also be referred to as RRC reconfiguration information (RRC reconfiguration).

[0100] It should be understood that during the DAPS switching, the terminal device will maintain the protocol stacks of the source cell and the target cell at the same time. In addition, during the period when the terminal device initiates random access to the target cell, the terminal device will maintain the radio link monitoring of the source cell.

[0101] Optionally, the handover command may be sent by the source base station. That is, the above step S310 may specifically be: the terminal device receives the handover command sent by the source base station.

[0102] Optionally, in the embodiment of the present application, the terminal device may perform DAPS switching according to the switching command. For example, the terminal device may initiate a synchronization process / random access to the target cell according to the switching command.

[0103] It should be noted that the random access may be a two-step random access or a four-step random access.

[0104] Optionally, the embodiments of the present application may be applied to a licensed frequency band or to an unlicensed frequency band, and the present application is not limited to this.

[0105] It should be noted that the at least one SRB may be all SRBs of the source cell or part of the SRBs of the source cell, which is not limited in the present application.

[0106] In an embodiment of the present application, when the DAPS switching fails and the source cell does not detect a radio link failure, the terminal device instructs the PDCP entity corresponding to at least one SRB to suspend the PDCP entity, that is, the terminal device can process the old RRC message cached in the PDCP entity of the source cell during the DAPS switching process. Similarly, when the DAPS switching fails and the source cell does not detect a radio link failure, the terminal device rebuilds the RLC entity corresponding to at least one SRB, that is, the terminal device can process the old RRC message cached in the RLC entity of the source cell during the DAPS switching process. Similarly, when the DAPS switching fails and the source cell does not detect a radio link failure, the terminal device triggers the PDCP SDU deletion process, that is, the terminal device can delete the old RRC message cached in the PDCP SDU of the source cell during the DAPS switching process.

[0107] Optionally, as example a, when the terminal device instructs the PDCP entity corresponding to the at least one SRB to suspend the PDCP entity, the terminal device deletes all PDCP PDUs and / or PDCP SDUs of the PDCP entity corresponding to the at least one SRB.

[0108] That is to say, in example a, when the DAPS switching fails and the source cell does not detect the radio link failure, the terminal device can instruct the PDCP entity corresponding to the at least one SRB to suspend the PDCP entity, and delete the old RRC messages cached in all PDCP PDUs and / or PDCP SDUs of the PDCP entity corresponding to the at least one SRB.

[0109] Optionally, in example a, the terminal device may also reset the status information of the PDCP entity corresponding to the at least one SRB. For example, the terminal device resets the timer configured in the PDCP entity corresponding to the at least one SRB, and / or the terminal device initializes the status variable of the PDCP entity corresponding to the at least one SRB.

[0110] Optionally, the timer configured in the PDCP entity corresponding to the at least one SRB may be a timer for deletion and / or sorting.

[0111] Optionally, as example b, when the terminal device reconstructs the RLC entity corresponding to the at least one SRB, the terminal device deletes all data in the cache of the RLC entity corresponding to the at least one SRB.

[0112] Optionally, the all data includes at least one of the following:

[0113] All RLC SDUs, all RLC PDUs, RLC SDU segments.

[0114] That is to say, in example b, when the DAPS switching fails and the source cell does not detect the radio link failure, the terminal device can rebuild the RLC entity corresponding to the at least one SRB, and delete all data in the cache of the RLC entity corresponding to the at least one SRB, that is, delete all cached old RRC messages in the RLC entity.

[0115] Optionally, in example b, the terminal device resets the state information of the RLC entity corresponding to the at least one SRB. For example, the terminal device resets the timer configured in the RLC entity corresponding to the at least one SRB, and / or the terminal device initializes the state variable of the RLC entity corresponding to the at least one SRB.

[0116] Optionally, the timer configured in the RLC entity corresponding to the at least one SRB may be a timer used for deletion and / or sorting.

[0117] Optionally, as example c, when the terminal device triggers the PDCP SDU deletion process, the terminal device deletes all PDCP PDUs and / or PDCP SDUs of the PDCP entity corresponding to the at least one SRB.

[0118] That is to say, in example c, when the DAPS switching fails and the source cell does not detect the radio link failure, the terminal device can trigger the PDCP SDU deletion process and delete the old RRC message in the cache of all PDCP PDUs and / or PDCP SDUs of the PDCP entity corresponding to the at least one SRB.

[0119] In the embodiment of the present application, suspend may also be expressed as pause, or other words with similar meanings.

[0120] Optionally, in an embodiment of the present application, the terminal device may also restore the at least one SRB of the source cell.

[0121] It should be noted that, when the DAPS switching fails and the source cell does not detect the radio link failure, the above step S320 may be performed before the terminal device restores at least one SRB of the source cell, or the above step S320 may be performed after the terminal device restores at least one SRB of the source cell.

[0122] Optionally, when the DAPS handover fails and the source cell does not detect a radio link failure, and step S320 is performed before the terminal device restores at least one SRB of the source cell, the terminal device may also perform some other operations before executing step S320. For example, for each SRB, if the master key update is not received, the terminal device configures the PDCP entity for the source cell using the same state variables as the PDCP entity of the target cell. For another example, for each SRB, the PDCP entity of the target cell is released. For another example, for each SRB, the RLC entity of the target cell and the logical channel associated with the target cell are released. For another example, the physical channel configuration of the target cell is released. For another example, the Service Data Adaptation Protocol (SDAP) configuration used in the source cell is restored. For another example, the key used in the target cell is discarded.

[0123] Optionally, when the DAPS handover fails and the source cell does not detect a radio link failure, and step S320 is performed after the terminal device restores at least one SRB of the source cell, the terminal device may also perform some other operations before restoring at least one SRB of the source cell. For example, for each SRB, if the master key update is not received, the terminal device configures the PDCP entity for the source cell using the same state variables as the PDCP entity of the target cell. For another example, for each SRB, the PDCP entity of the target cell is released. For another example, for each SRB, the RLC entity of the target cell and the logical channel associated with the target cell are released. For another example, the physical channel configuration of the target cell is released. For another example, the SDAP configuration used in the source cell is restored. For another example, the key used in the target cell is discarded.

[0124] Optionally, when the DAPS handover fails and the source cell does not detect a radio link failure, and step S320 is performed before the terminal device restores at least one SRB of the source cell, step S320 may be for each SRB. For example, for each SRB, the terminal device instructs the PDCP layer corresponding to at least one SRB of the source cell to suspend the PDCP entity. For another example, for each SRB, the terminal device rebuilds the RLC entity corresponding to at least one SRB of the source cell. For another example, for each SRB, the terminal device triggers the PDCP SDU deletion process. In this case, the terminal device may also perform some other operations after executing step S320 and before restoring at least one SRB of the source cell. For example, for each SRB, if the master key update is not received, the terminal device configures the PDCP entity for the source cell using the same state variables as the PDCP entity of the target cell. For another example, for each SRB, the PDCP entity of the target cell is released. For another example, for each SRB, the RLC entity of the target cell and the logical channel associated with the target cell are released. For another example, the physical channel configuration of the target cell is released. For another example, the SDAP configuration used in the source cell is restored. For another example, the key used in the target cell is discarded.

[0125] Therefore, in an embodiment of the present application, during the DAPS switching process, when the DAPS switching fails and the source cell does not detect a radio link failure, the terminal device can delete the old RRC message cached by the source cell, so that the terminal device can avoid transmitting unnecessary RRC messages when switching back to the source cell after the DAPS switching fails.

[0126] Combination of the above Figure 2 and Figure 3 , describes in detail the method embodiment of the present application, and the following is combined with Figures 4 to 8 , the device embodiments of the present application are described in detail. It should be understood that the device embodiments and the method embodiments correspond to each other, and similar descriptions can refer to the method embodiments.

[0127] Figure 4 FIG. 4 shows a schematic block diagram of a terminal device 400 according to an embodiment of the present application. Figure 4 As shown, the terminal device 400 includes: a communication unit 410 and a processing unit 420, wherein:

[0128] The communication unit 410 is used to receive a handover command, where the handover command is used to instruct the terminal device to switch from a source cell to a target cell using a DAPS handover method;

[0129] When the terminal device suspends at least one SRB of the source cell according to the handover command, the processing unit 420 is configured to perform at least one of the following operations:

[0130] instructing the PDCP entity corresponding to the at least one SRB to suspend the PDCP entity,

[0131] reestablishing the RLC entity corresponding to the at least one SRB,

[0132] Trigger the PDCP SDU deletion procedure.

[0133] Optionally, when the terminal device instructs the PDCP entity corresponding to the at least one SRB to suspend the PDCP entity, the processing unit 420 is further used to delete all PDCP PDUs and / or PDCP SDUs of the PDCP entity corresponding to the at least one SRB.

[0134] Optionally, the processing unit 420 is further used to reset the status information of the PDCP entity corresponding to the at least one SRB.

[0135] Optionally, the processing unit 420 is specifically configured to:

[0136] Reset the timer configured in the PDCP entity corresponding to the at least one SRB, and / or initialize the state variable of the PDCP entity corresponding to the at least one SRB.

[0137] Optionally, in a case where the terminal device reconstructs the RLC entity corresponding to the at least one SRB, the processing unit 420 is further used to delete all data in the cache of the RLC entity corresponding to the at least one SRB.

[0138] Optionally, the all data includes at least one of the following:

[0139] All RLC SDUs, all RLC PDUs, RLC SDU segments.

[0140] Optionally, the processing unit 420 is further configured to reset status information of an RLC entity corresponding to the at least one SRB.

[0141] Optionally, the processing unit 420 is specifically configured to:

[0142] Reset a timer configured in the RLC entity corresponding to the at least one SRB, and / or initialize a state variable of the RLC entity corresponding to the at least one SRB.

[0143] Optionally, when the terminal device triggers the PDCP SDU deletion process, the processing unit 420 is also used to delete all PDCP PDUs and / or PDCP SDUs of the PDCP entity corresponding to the at least one SRB.

[0144] Optionally, in some embodiments, the communication unit may be a communication interface or a transceiver, or an input / output interface of a communication chip or a system on chip. The processing unit may be one or more processors.

[0145] It should be understood that the terminal device 400 according to the embodiment of the present application may correspond to the terminal device in the method embodiment of the present application, and the above and other operations and / or functions of each unit in the terminal device 400 are respectively to implement Figure 2 For the sake of brevity, the corresponding process of the terminal device in the method 200 is not repeated here.

[0146] Figure 5 FIG. 5 shows a schematic block diagram of a terminal device 500 according to an embodiment of the present application. Figure 5 As shown, the terminal device 500 includes: a communication unit 510 and a processing unit 520, wherein:

[0147] The communication unit 510 is used to receive a handover command, where the handover command is used to instruct the terminal device to switch from a source cell to a target cell using a DAPS handover method;

[0148] In the case where the DAPS handover fails and the source cell does not detect a radio link failure, the processing unit 520 is configured to perform at least one of the following operations:

[0149] Instruct the PDCP layer corresponding to at least one SRB of the source cell to suspend the PDCP entity,

[0150] Reestablishing the RLC entity corresponding to at least one SRB of the source cell,

[0151] Trigger the PDCP SDU deletion procedure.

[0152] Optionally, the processing unit 520 is further configured to restore at least one SRB of the source cell.

[0153] Optionally, when the terminal device instructs the PDCP entity corresponding to the at least one SRB to suspend the PDCP entity, the processing unit 520 is further used to delete all PDCP PDUs and / or PDCP SDUs of the PDCP entity corresponding to the at least one SRB.

[0154] Optionally, the processing unit 520 is further used to reset the status information of the PDCP entity corresponding to the at least one SRB.

[0155] Optionally, the processing unit 520 is specifically configured to:

[0156] Reset the timer configured in the PDCP entity corresponding to the at least one SRB, and / or initialize the state variable of the PDCP entity corresponding to the at least one SRB.

[0157] Optionally, in a case where the terminal device reconstructs the RLC entity corresponding to the at least one SRB, the processing unit 520 is further used to delete all data in the cache of the RLC entity corresponding to the at least one SRB.

[0158] Optionally, the all data includes at least one of the following:

[0159] All RLC SDUs, all RLC PDUs, RLC SDU segments.

[0160] Optionally, the processing unit 520 is further configured to reset status information of an RLC entity corresponding to the at least one SRB.

[0161] Optionally, the processing unit 520 is specifically configured to:

[0162] Reset a timer configured in the RLC entity corresponding to the at least one SRB, and / or initialize a state variable of the RLC entity corresponding to the at least one SRB.

[0163] Optionally, when the terminal device triggers the PDCP SDU deletion process, the processing unit 520 is also used to delete all PDCP PDUs and / or PDCP SDUs of the PDCP entity corresponding to the at least one SRB.

[0164] Optionally, in some embodiments, the communication unit may be a communication interface or a transceiver, or an input / output interface of a communication chip or a system on chip. The processing unit may be one or more processors.

[0165] It should be understood that the terminal device 500 according to the embodiment of the present application may correspond to the terminal device in the method embodiment of the present application, and the above and other operations and / or functions of each unit in the terminal device 500 are respectively to implement Figure 3 For the sake of brevity, the corresponding process of the terminal device in the method 300 is not repeated here.

[0166] Figure 6 It is a schematic structural diagram of a communication device 600 provided in an embodiment of the present application. Figure 6 The communication device 600 shown includes a processor 610, which can call and run a computer program from a memory to implement the method in the embodiment of the present application.

[0167] Alternatively, if Figure 6 As shown, the communication device 600 may further include a memory 620. The processor 610 may call and run a computer program from the memory 620 to implement the method in the embodiment of the present application.

[0168] The memory 620 may be a separate device independent of the processor 610 , or may be integrated into the processor 610 .

[0169] Alternatively, if Figure 6 As shown, the communication device 600 may further include a transceiver 630, and the processor 610 may control the transceiver 630 to communicate with other devices, specifically, may send information or data to other devices, or receive information or data sent by other devices.

[0170] The transceiver 630 may include a transmitter and a receiver. The transceiver 630 may further include an antenna, and the number of the antennas may be one or more.

[0171] Optionally, the communication device 600 may specifically be a network device of an embodiment of the present application, and the communication device 600 may implement the corresponding processes implemented by the network device in each method of the embodiment of the present application, which will not be described in detail here for the sake of brevity.

[0172] Optionally, the communication device 600 may specifically be a mobile terminal / terminal device of an embodiment of the present application, and the communication device 600 may implement the corresponding processes implemented by the mobile terminal / terminal device in each method of the embodiment of the present application, which will not be described in detail here for the sake of brevity.

[0173] Figure 7 It is a schematic structural diagram of the device of an embodiment of the present application. Figure 7 The device 700 shown includes a processor 710, which can call and run a computer program from a memory to implement the method in the embodiment of the present application.

[0174] Alternatively, if Figure 7 As shown, the apparatus 700 may further include a memory 720. The processor 710 may call and run a computer program from the memory 720 to implement the method in the embodiment of the present application.

[0175] The memory 720 may be a separate device independent of the processor 710 , or may be integrated into the processor 710 .

[0176] Optionally, the apparatus 700 may further include an input interface 730. The processor 710 may control the input interface 730 to communicate with other devices or chips, and specifically, may obtain information or data sent by other devices or chips.

[0177] Optionally, the apparatus 700 may further include an output interface 740. The processor 710 may control the output interface 740 to communicate with other devices or chips, and specifically, may output information or data to other devices or chips.

[0178] Optionally, the device can be applied to the network equipment in the embodiments of the present application, and the device can implement the corresponding processes implemented by the network equipment in the various methods in the embodiments of the present application. For the sake of brevity, they will not be repeated here.

[0179] Optionally, the apparatus may be applied to a mobile terminal / terminal device in an embodiment of the present application, and the apparatus may implement corresponding processes implemented by the mobile terminal / terminal device in each method of the embodiment of the present application, which will not be described in detail here for the sake of brevity.

[0180] Optionally, the device mentioned in the embodiments of the present application may also be a chip, for example, a system-on-chip, a system-on-chip, a chip system, or a system-on-chip chip.

[0181] Figure 8 8 is a schematic block diagram of a communication system 800 provided in an embodiment of the present application. Figure 8 As shown, the communication system 800 includes a terminal device 810 and a network device 820 .

[0182] Among them, the terminal device 810 can be used to implement the corresponding functions implemented by the terminal device in the above method, and the network device 820 can be used to implement the corresponding functions implemented by the network device in the above method. For the sake of brevity, they are not repeated here.

[0183] It should be understood that the processor of the embodiment of the present application may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method embodiment can be completed by the hardware integrated logic circuit or software instructions in the processor. The above processor can be a general processor, a digital signal processor (Digital Signal Processor, DSP), an application-specific integrated circuit (Application Specific Integrated Circuit, ASIC), a field programmable gate array (Field Programmable Gate Array, FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components. The methods, steps and logic block diagrams disclosed in the embodiments of the present application can be implemented or executed. The general processor can be a microprocessor or the processor can also be any conventional processor. The steps of the method disclosed in the embodiment of the present application can be directly embodied as a hardware decoding processor to perform, or the hardware and software modules in the decoding processor are combined and performed. The software module can be located in a random access memory, a flash memory, a read-only memory, a programmable read-only memory or an electrically erasable programmable memory, a register, and other mature storage media in the art. The storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware.

[0184] It can be understood that the memory in the embodiments of the present application can be a volatile memory or a non-volatile memory, or can include both volatile and non-volatile memories. Among them, the non-volatile memory can be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory can be a random access memory (RAM), which is used as an external cache. By way of example and not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct RAM bus random access memory (DR RAM). It should be noted that the memory of the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0185] It should be understood that the above-mentioned memory is exemplary but not restrictive. For example, the memory in the embodiments of the present application may also be static random access memory (static RAM, SRAM), dynamic random access memory (dynamic RAM, DRAM), synchronous dynamic random access memory (synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (double data rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchronous link dynamic random access memory (synch link DRAM, SLDRAM) and direct memory bus random access memory (Direct Rambus RAM, DR RAM), etc. That is to say, the memory in the embodiments of the present application is intended to include but not limited to these and any other suitable types of memory.

[0186] An embodiment of the present application also provides a computer-readable storage medium for storing a computer program.

[0187] Optionally, the computer-readable storage medium can be applied to the network device in the embodiments of the present application, and the computer program enables the computer to execute the corresponding processes implemented by the network device in the various methods of the embodiments of the present application. For the sake of brevity, they are not repeated here.

[0188] Optionally, the computer-readable storage medium can be applied to the mobile terminal / terminal device in the embodiments of the present application, and the computer program enables the computer to execute the corresponding processes implemented by the mobile terminal / terminal device in the various methods of the embodiments of the present application. For the sake of brevity, they are not repeated here.

[0189] An embodiment of the present application also provides a computer program product, including computer program instructions.

[0190] Optionally, the computer program product can be applied to the network device in the embodiments of the present application, and the computer program instructions enable the computer to execute the corresponding processes implemented by the network device in the various methods of the embodiments of the present application. For the sake of brevity, they are not repeated here.

[0191] Optionally, the computer program product can be applied to the mobile terminal / terminal device in the embodiments of the present application, and the computer program instructions enable the computer to execute the corresponding processes implemented by the mobile terminal / terminal device in the various methods of the embodiments of the present application. For the sake of brevity, they are not repeated here.

[0192] The embodiment of the present application also provides a computer program.

[0193] Optionally, the computer program can be applied to the network device in the embodiments of the present application. When the computer program runs on a computer, the computer executes the corresponding processes implemented by the network device in the various methods in the embodiments of the present application. For the sake of brevity, they are not described here.

[0194] Optionally, the computer program can be applied to the mobile terminal / terminal device in the embodiments of the present application. When the computer program runs on the computer, the computer executes the corresponding processes implemented by the mobile terminal / terminal device in the various methods of the embodiments of the present application. For the sake of brevity, they are not repeated here.

[0195] Those of ordinary skill in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0196] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0197] In the several embodiments provided in the present application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0198] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0199] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0200] If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. In view of such an understanding, the technical solution of the present application can be embodied in the form of a software product in essence or in other words, the part that contributes to the prior art or the part of the technical solution. The computer software product is stored in a storage medium, including several instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

[0201] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any technician familiar with the technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

Claims

1. A wireless communication method, characterized in that: include: The terminal device receives a handover command, where the handover command is used to instruct the terminal device to switch from a source cell to a target cell using a dual activation protocol stack (DAPS) handover mode; In the case where the DAPS handover fails and the source cell does not detect a radio link failure, the terminal device performs at least one of the following operations: Instructing a packet data convergence protocol (PDCP) layer corresponding to at least one signaling radio bearer (SRB) of the source cell to suspend a PDCP entity, reestablishing a radio link control RLC entity corresponding to at least one SRB of the source cell, Trigger the PDCP service data unit SDU deletion process.

2. The method according to claim 1, characterized in that The method further comprises: The terminal device restores at least one SRB of the source cell.

3. The method according to claim 1 or 2, characterized in that: In the case where the terminal device reestablishes the RLC entity corresponding to the at least one SRB, the method further includes: The terminal device deletes all data in the cache of the RLC entity corresponding to the at least one SRB.

4. The method according to claim 3, characterized in that The data includes at least one of the following: All RLC SDUs, all RLC PDUs, RLC SDU segments.

5. The method according to claim 3 or 4, characterized in that: The method further comprises: The terminal device resets the status information of the RLC entity corresponding to the at least one SRB.

6. The method according to claim 5, characterized in that The terminal device resetting the state information of the RLC entity corresponding to the at least one SRB includes: The terminal device resets a timer configured in the RLC entity corresponding to the at least one SRB, and / or the terminal device initializes a state variable of the RLC entity corresponding to the at least one SRB.

7. The method according to claim 1 or 2, characterized in that: In the case where the terminal device triggers the PDCP SDU deletion process, the method further includes: The terminal device deletes all PDCP PDUs and / or PDCP SDUs of the PDCP entity corresponding to the at least one SRB.

8. A terminal device, characterized in that: include: A communication unit and a processing unit, wherein The communication unit is used to receive a handover command, where the handover command is used to instruct the terminal device to switch from a source cell to a target cell using a dual activation protocol stack DAPS handover mode; In the case where the DAPS handover fails and the source cell does not detect a radio link failure, the processing unit is configured to perform at least one of the following operations: Instructing a packet data convergence protocol (PDCP) layer corresponding to at least one signaling radio bearer (SRB) of the source cell to suspend a PDCP entity, reestablishing a radio link control RLC entity corresponding to at least one SRB of the source cell, Trigger the PDCP service data unit SDU deletion process.

9. The terminal device according to claim 8, characterized in that: The processing unit is further configured to restore at least one SRB of the source cell.

10. The terminal device according to claim 8 or 9, characterized in that: In the case where the terminal device reconstructs the RLC entity corresponding to the at least one SRB, the processing unit is further configured to delete all data in the cache of the RLC entity corresponding to the at least one SRB.

11. The terminal device according to claim 10, characterized in that: The data includes at least one of the following: All RLC SDUs, all RLC PDUs, RLC SDU segments.

12. The terminal device according to claim 10 or 11, characterized in that: The processing unit is further configured to reset the state information of the RLC entity corresponding to the at least one SRB.

13. The terminal device according to claim 12, characterized in that: The processing unit is specifically used for: Reset a timer configured in the RLC entity corresponding to the at least one SRB, and / or initialize a state variable of the RLC entity corresponding to the at least one SRB.

14. The terminal device according to claim 8 or 9, characterized in that: In the case where the terminal device triggers the PDCP SDU deletion process, the processing unit is also used to delete all PDCP PDUs and / or PDCP SDUs of the PDCP entity corresponding to the at least one SRB.

15. A terminal device, characterized in that: include: A processor and a memory, the memory being used to store a computer program, the processor being used to call and run the computer program stored in the memory to execute the method according to any one of claims 1 to 7.

16. A chip, characterized in that: include: A processor, configured to call and run a computer program from a memory, so that a device equipped with the chip executes a method as claimed in any one of claims 1 to 7.

17. A computer-readable storage medium, characterized in that: Used to store a computer program, wherein the computer program causes a computer to execute the method according to any one of claims 1 to 7.

Images