Wireless communication method, terminal device and network device

Abstract

The embodiment of the present application provides a wireless communication method, a terminal device and a network device. In DAPS switching, the terminal device can report a continuous uplink LBT failure message to the source base station to avoid interrupting the data transmission between the terminal device and the source base station due to triggering the reconstruction process, thereby ensuring the data transmission in the DAPS switching. The wireless communication method includes: the terminal device receives a switching command sent by the source base station, and the switching command is used to instruct the terminal device to switch from the source cell to the target cell using the DAPS switching method; the terminal device initiates a random access process to the target base station according to the switching command; in the case of triggering an uplink continuous LBT failure, the terminal device sends a first message to the source base station, and the first message is used to indicate that an uplink continuous LBT failure is triggered in the random access process initiated to the target base station.

Description

Technical Field

[0001] Embodiments of the present application relate to the field of communications, and more particularly, to a wireless communication method, a terminal device, and a network device. Background Art

[0002] In a New Radio-based access to unlicensed spectrum (NR-U) system on unlicensed spectrum, the spectrum used is shared spectrum. In a communication system deployed on shared spectrum, such as an NR-U system, in order to ensure fair coexistence among systems on unlicensed spectrum, a Listen Before Talk (LBT) mechanism is adopted. Additionally, in mobility handover, such as dual active protocol stack (DAPS) handover, the terminal device will maintain downlink data reception from the source cell before releasing the source cell, and at the same time, the terminal device will maintain uplink data transmission to the source cell until the terminal device successfully completes the random access procedure with the target cell. However, at present, there is no solution on how to design for the case where continuous uplink LBT fails during the DAPS handover process, thus affecting the communication of the NR-U system on shared spectrum. Summary of the Invention

[0003] Embodiments of the present application provide a wireless communication method, a terminal device, and a network device. During DAPS handover, the terminal device can report a continuous uplink LBT failure message to the source base station, avoiding interruption of data transmission between the terminal device and the source base station due to triggering a reconstruction process, thereby ensuring data transmission during DAPS handover.

[0004] In a first aspect, a wireless communication method is provided. The method includes:

[0005] The terminal device receives a handover command sent by the source base station, where the handover command is used to instruct the terminal device to perform a DAPS handover from the source cell to the target cell;

[0006] The terminal device initiates a random access procedure to the target base station according to the handover command;

[0007] In the case where uplink continuous LBT fails, the terminal device sends first information to the source base station, where the first information is used to indicate that uplink continuous LBT fails during the process of initiating a random access procedure to the target base station.

[0008] In a second aspect, a wireless communication method is provided. The method includes:

[0009] The source base station sends a handover command to the terminal device, and the handover command is used to instruct the terminal device to perform a handover from the source cell to the target cell in the DAPS handover manner;

[0010] The source base station receives first information sent by the terminal device, and the first information is used to indicate that the terminal device has triggered an uplink persistent LBT failure in the random access procedure initiated towards the target base station.

[0011] In a third aspect, a terminal device is provided for performing the method in the first aspect or its various implementation manners above.

[0012] Specifically, the terminal device includes functional modules for performing the method in the first aspect above.

[0013] In a fourth aspect, a network device is provided for performing the method executed by the source base station in the second aspect above.

[0014] Specifically, the network device includes functional modules for performing the method executed by the source base station in the second aspect above.

[0015] In a fifth aspect, a terminal device is provided, including a processor and a memory. 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 above.

[0016] In a sixth aspect, a network device is provided, including a processor and a memory. 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 executed by the source base station in the second aspect above.

[0017] In a seventh aspect, a device is provided for implementing the method in any one of the first aspect to the second aspect or its various implementation manners above.

[0018] Specifically, the device includes: a processor, which is used to call and run a computer program from the memory, so that the device equipped with the device executes the method in any one of the first aspect to the second aspect or its various implementation manners above.

[0019] In an eighth aspect, a computer-readable storage medium is provided for storing a computer program, and the computer program causes a computer to execute the method in any one of the first aspect to the second aspect or its various implementation manners above.

[0020] In a ninth aspect, a computer program product is provided, including computer program instructions, and the computer program instructions cause a computer to execute the method in any one of the first aspect to the second aspect or its various implementation manners above.

[0021] In a tenth aspect, there is provided a computer program which, when running on a computer, causes the computer to execute the method according to any one of the first aspect to the second aspect or any implementation thereof described above.

[0022] Through the above technical solution, in DAPS handover, the terminal device can report a continuous uplink LBT failure message to the source base station, avoiding interruption of data transmission between the terminal device and the source base station due to triggering a reconstruction process, thereby ensuring data transmission during DAPS handover. BRIEF DESCRIPTION OF THE DRAWINGS

[0023] Figure 1 FIG. is a schematic diagram of a communication system architecture provided by an embodiment of the present application.

[0024] Figure 2 FIG. is a schematic flowchart of a DAPS handover provided by an embodiment of the present application.

[0025] Figure 3 FIG. is a schematic flowchart of a wireless communication method provided by an embodiment of the present application.

[0026] Figure 4 FIG. is a schematic flowchart of reporting SCG failure information provided by an embodiment of the present application.

[0027] Figure 5 FIG. is a schematic flowchart of reporting failure information provided by an embodiment of the present application.

[0028] Figure 6 FIG. is a schematic block diagram of a terminal device provided by an embodiment of the present application.

[0029] Figure 7 FIG. is a schematic block diagram of a network device provided by an embodiment of the present application.

[0030] Figure 8 FIG. is a schematic block diagram of a communication device provided by an embodiment of the present application.

[0031] Figure 9 FIG. is a schematic block diagram of a device provided by an embodiment of the present application.

[0032] Figure 10 FIG. is a schematic block diagram of a communication system provided by an embodiment of the present application. DETAILED DESCRIPTION OF THE EMBODIMENTS

[0033] Next, the technical solutions in the embodiments of the present application will be described with reference to the accompanying drawings in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, rather than all the embodiments. For the embodiments of the present application, all other embodiments obtained by those of ordinary skill in the art without creative efforts shall fall within the protection scope of the present application.

[0034] 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, the evolved system of the NR system, LTE-based access to unlicensed spectrum (LTE-U) system, NR-based access to unlicensed spectrum (NR-U) system, Universal Mobile Telecommunication System (UMTS), Wireless Local Area Networks (WLAN), Wireless Fidelity (WiFi), next-generation communication system or other communication systems, etc.

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

[0036] Optionally, the communication system in the embodiments of the present application can be applied to a Carrier Aggregation (CA) scenario, a Dual Connectivity (DC) scenario, or a Standalone (SA) networking scenario.

[0037] The embodiments of the present application do not limit the spectrum to be applied. For example, the embodiments of the present application can be applied to licensed spectrum or unlicensed spectrum.

[0038] Exemplarily, the communication system 100 applied in the embodiments of the present application is as Figure 1 shown. The communication system 100 may include a network device 110, and the network device 110 may be a device that communicates with a terminal device 120 (or referred to as a communication terminal, terminal). The network device 110 can provide communication coverage for a specific geographical area and can communicate with terminal devices located within the coverage area.

[0039] Figure 1 Exemplarily, one network device and two terminal devices are shown. Optionally, the communication system 100 may include multiple network devices, and each network device's coverage area may include other numbers of terminal devices. The embodiments of the present application do not limit this.

[0040] Optionally, the communication system 100 may further include other network entities such as a network controller and a mobility management entity. The embodiments of the present application do not limit this.

[0041] It should be understood that in the embodiments of the present application, a device with communication functions in a network / system may be referred to as a communication device. Taking Figure 1 the shown communication system 100 as an example, the communication devices may include the network device 110 and the 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 elaborated here; the communication devices may also include other devices in the communication system 100, such as other network entities like a network controller and a mobility management entity. The embodiments of the present application do not limit this.

[0042] It should be understood that the terms "system" and "network" are often used interchangeably in this article. The term " / and" in this article is merely a description of the association relationship between associated objects, indicating that there can be three relationships. For example, A and / or B can represent: A exists alone, A and B exist simultaneously, and B exists alone. Additionally, the character " / " in this article generally represents an "or" relationship between the associated objects before and after.

[0043] The embodiments of the present application describe various embodiments in combination with a terminal device and a network device, where: The terminal device may also be referred to as a user equipment (UE), access terminal, user unit, user station, mobile station, mobile terminal, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent, or user device, etc. The terminal device may 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 capabilities, a computing device, or other processing devices connected to a wireless modem, a vehicle-mounted device, a wearable device, and a next-generation communication system. For example, a terminal device in an NR network or a terminal device in a future evolved Public Land Mobile Network (PLMN) network, etc.

[0044] By way of example and not limitation, in the embodiments of the present application, the terminal device may also be a wearable device. A wearable device may also be referred to as a wearable intelligent device, which is a general term for devices developed by applying wearable technologies to the intelligent design of daily wear, such as glasses, gloves, watches, clothing, and shoes, etc. A wearable device is a portable device that is directly worn on the body or integrated into the user's clothes or accessories. A wearable device is not only a hardware device, but also realizes powerful functions through software support, data interaction, and cloud interaction. Broadly speaking, wearable intelligent devices include those with complete functions and large sizes that can realize complete or partial functions without relying on a smart phone, such as smart watches or smart glasses, etc., and those that only focus on a certain type of application function and need to cooperate with other devices such as smart phones, such as various smart bracelets and smart jewelry for physical sign monitoring.

[0045] A network device may be a device used to communicate with a mobile device. The network device may be an access point (Aceess Point, AP) in a WLAN, a base transceiver station (BTS) in GSM or CDMA, a base station (NodeB, NB) in WCDMA, an evolved base station (Evolutional Node B, eNB or eNodeB) in LTE, or a relay station or access point, or a vehicle-mounted device, a wearable device, a network device or a base station (gNB) in an NR network, or a network device in a future evolved PLMN network, etc.

[0046] In the embodiments of the present application, the network device provides 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 in other words, spectrum resources). The cell can be a cell corresponding to the network device (such as a base station). The cell can belong to a macro base station or a base station corresponding to a small cell. Here, the small cells can include: Metro cell, Micro cell, Picocell, Femto cell, etc. These small cells have the characteristics of small coverage range and low transmission power, and are suitable for providing high-rate data transmission services.

[0047] It should be noted that NR operates in the unlicensed band. For example, it can include the following working scenarios:

[0048] Scenario A: Carrier aggregation scenario. The Primary Cell (PCell) is in the licensed spectrum, and the Secondary Cell (SCell) operating in the unlicensed spectrum is aggregated through carrier aggregation.

[0049] Scenario B: Dual-connection working scenario. The PCell is in the LTE licensed spectrum, and the PSCell is in the NR unlicensed spectrum.

[0050] Scenario C: Stand-alone working scenario. NR operates as an independent cell in the unlicensed spectrum.

[0051] Scenario D: NR single-cell scenario. The uplink (UL) operates in the licensed spectrum, and the downlink (DL) operates in the unlicensed spectrum.

[0052] Scenario E: Dual-connection working scenario. The PCell is in the NR licensed spectrum, and the Primary SecondaryCell (PSCell) is in the NR unlicensed spectrum.

[0053] Generally speaking, the working band of NR-U is the 5GHz unlicensed spectrum and the 6GHz unlicensed spectrum. In the unlicensed spectrum, the design of NR-U should ensure fairness with other systems that are already operating in these unlicensed spectrums, such as WiFi. The principle of fairness is that the impact of NR-U on the systems already deployed in the unlicensed spectrum (such as WiFi) should not exceed the impact between these systems.

[0054] To ensure fair coexistence among systems on unlicensed spectrum, energy detection has been agreed as a basic coexistence mechanism. The general energy detection mechanism is the LBT mechanism. The basic principle of this mechanism is that before transmitting data on unlicensed spectrum, the base station or terminal (transmitter) needs to listen for a period of time according to regulations. If the listening result indicates that the channel is idle, the transmitter can transmit data to the receiver. If the listening result indicates that the channel is occupied, the transmitter needs to back off for a period of time according to regulations and then continue to listen to the channel until the listening result of the channel is idle before transmitting data to the receiver.

[0055] For the uplink transmission initiated by the terminal device, there are mainly the following categories:

[0056] Scheduling Request (SR): Used to request uplink resources;

[0057] Physical Random Access Channel (PRACH) transmission: Triggered by Random Access Channel (RACH), the terminal device needs to send the first message (Msg1);

[0058] Physical Uplink Shared Channel (PUSCH) transmission: Includes uplink data transmission based on pre-configured grant and uplink data transmission based on dynamic grant;

[0059] Physical layer signaling transmission: Includes positive acknowledgement (ACK) / negative acknowledgement (NACK) feedback, channel state information (CSI) reporting, etc.

[0060] On the licensed band, for SR transmission, the Media Access Control (MAC) maintains a counter to count the number of SR failures (SR_COUNTER). When SR_COUNTER reaches the configured threshold, the terminal device will trigger the RACH process;

[0061] For PRACH transmission, the MAC layer also maintains a counter to count the number of PRACH failures (PREAMBLE_TRANSMISSION_COUNTER). When this counter reaches the configured threshold, the terminal device will trigger a Radio Link Failure (RLF) and initiate a Radio Resource Control (RRC) reestablishment procedure.

[0062] For configured grant-based uplink transmission, the terminal device does not maintain a counter. If data transmission fails, the network will schedule a retransmission. For the Radio Link Control (RLC) Acknowledged Mode (AM), there is a counter at the RLC layer. When the retransmission counter reaches the maximum number of times, it will also trigger an RLF. For the RLC Unacknowledged Mode (UM), it depends on the retransmission mechanisms of the MAC and physical layers.

[0063] On the unlicensed band, the terminal device needs to use LBT to listen to whether the channel is available before transmitting SR, PRACH, or PUSCH. If it is not available, i.e., the LBT fails, the terminal device needs to wait for the next transmission opportunity to perform LBT again.

[0064] It should be noted that LBT failures caused by continuous uplink transmission will cause RLF. In addition, the MAC layer will design a mechanism to handle the problem of UL LBT failures.

[0065] It should also be noted that continuous uplink LBT failure detection will consider LBT failures caused by all types of uplink transmissions; at the same time, the recovery mechanisms triggered by LBT failures of any uplink transmission type are the same; the network configures a threshold, and the MAC layer of the terminal device records the number of LBT failures. When this threshold is reached, the terminal device triggers a continuous LBT failure event; and a timer is introduced. When the timer times out, the terminal device resets the counter and starts or restarts the timer when it receives an LBT failure.

[0066] In addition, when the terminal device triggers a continuous uplink LBT failure, the terminal device has different behaviors according to whether the cell that triggers the failure belongs to the Master Cell Group (MCG) or the Secondary Cell Group (SCG). If the cell that triggers the continuous uplink LBT failure is located in the MCG, the terminal device directly triggers an RLF and will perform an RRC reconstruction; if the cell that triggers the continuous uplink LBT failure is located in the SCG, the UE reports the SCG failure to the network through the MCG.

[0067] In the embodiment of the present application, the basic process of DAPS handover is as Figure 2 shown. Specifically, as Figure 2 Steps 1 to 4 in it, the terminal device determines the handover type to be performed based on the RRC reconfiguration information (handover command) received in step 3. If it is a DAPS handover, the terminal device will maintain the downlink data reception from the source cell before releasing the source cell, and at the same time the terminal device will maintain the uplink data transmission to the source cell until the terminal device successfully completes the random access procedure with the target cell.

[0068] Furthermore, when the terminal device receives a DAPS handover command, the terminal device will perform the following operations:

[0069] Establish a MAC entity for the target cell;

[0070] For the Data Radio Bearer (DRB) configured with DAPS, establish an RLC entity and associate it with the Dedicated Transmission Channel (DTCH) corresponding to the DRB;

[0071] For the DRB configured with DAPS, reconfigure the Packet Data Convergence Protocol (PDCP) entity corresponding to the DRB. The PDCP entity includes the security and Robust Header Compression (ROHC) functions of the source cell and the target cell respectively;

[0072] Retain the configuration of the source cell until the source cell is released.

[0073] After the above process is completed, the terminal device initiates a random access procedure to the target base station. During this period, the terminal device maintains data transmission with the source cell, including uplink data transmission and downlink data reception. When the random access is successfully completed, the terminal device will switch the transmission of uplink data from the source cell to the target cell. That is to say, before successfully accessing the target cell, the uplink data of the terminal device is sent through the source cell side, and after successfully accessing the target cell, the uplink data of the terminal device is sent through the target cell side.

[0074] Finally, when the terminal device successfully accesses the target base station, the terminal device will release the connection with the source cell and stop data transceiver with the source cell based on the indication signaling from the network side, including the signaling radio bearers (SRB) resources, security configuration, etc. of the source cell.

[0075] In handover, if the DAPS handover mode is adopted, the terminal device performs random access to the target cell. If continuous uplink LBT fails, the terminal device will trigger a reconstruction process (due to RLF). However, in the DAPS scenario, the terminal device actually still maintains the connection with the source cell. At this time, the reconstruction caused by continuous LBT failure will interrupt the data transmission between the terminal device and the source base station.

[0076] Based on the above problems, the present application proposes a solution for continuous uplink LBT failure in DAPS handover. The terminal device can report the continuous uplink LBT failure message to the source base station to avoid interrupting the data transmission between the terminal device and the source base station due to triggering the reconstruction process, thereby ensuring the data transmission in DAPS handover.

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

[0078] Figure 3 is a schematic flowchart of a wireless communication method 200 according to an embodiment of the present application. As Figure 3 shown, the method 200 may include but is not limited to the following:

[0079] S210, the source base station sends a handover command to the terminal device, and the handover command is used to instruct the terminal device to switch from the source cell to the target cell in the DAPS handover mode;

[0080] S220, the terminal device receives the handover command sent by the source base station;

[0081] S230, the terminal device initiates a random access procedure to the target base station according to the handover command;

[0082] S240. When the uplink continuous LBT fails, the terminal device sends a first message to the source base station, and the first message is used to indicate that the uplink continuous LBT fails in the process of initiating a random access procedure to the target base station.

[0083] S250. The source base station receives the first message sent by the terminal device.

[0084] In the embodiments of the present application, in DAPS handover, the terminal device can report a continuous uplink LBT failure message to the source base station. Compared with triggering a reconstruction procedure after the continuous uplink LBT fails in DAPS handover, the solution in the present application avoids interrupting the data transmission between the terminal device and the source base station due to triggering the reconstruction procedure, thereby ensuring the data transmission in DAPS handover.

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

[0086] It should be noted that, in the embodiments of the present application, the handover command can also be referred to as the RRC reconfiguration information.

[0087] In the embodiments of the present application, the terminal device initiates a random access procedure to the target base station on the unlicensed frequency band according to the handover command.

[0088] Optionally, the random access procedure initiated by the terminal device can be a four-step random access procedure or a two-step random access procedure.

[0089] Optionally, in some embodiments, the handover command includes uplink LBT failure configuration information.

[0090] Furthermore, the terminal device detects uplink LBT failure and / or performs uplink LBT failure recovery operations during the handover process according to the uplink LBT failure configuration information.

[0091] Correspondingly, for the source base station, the uplink LBT failure configuration information is used for the terminal device to detect uplink LBT failure and / or perform uplink LBT failure recovery operations during the handover process.

[0092] Optionally, in some other scenarios, the uplink LBT failure configuration information can also be pre-configured in the terminal device.

[0093] Optionally, the uplink LBT failure configuration information includes a timer and / or a preset value. The timer is used for uplink LBT failure detection and starts or restarts when uplink LBT fails. The preset value is the maximum number of consecutive uplink LBT failures that triggers uplink LBT failure recovery.

[0094] Specifically, when uplink LBT fails, the terminal device starts or restarts the timer. The start or restart times of the timer can be recorded by a counter. When the start or restart times of the timer are greater than the preset value, the terminal device triggers consecutive uplink LBT failures and performs uplink LBT failure recovery operations.

[0095] For example, the timer is the LBT failure detection timer (lbt-FailureDetectionTimer).

[0096] For example, the preset value is the maximum number of LBT failures (lbt-FailureInstanceMaxCount).

[0097] Optionally, the duration of the timer can include but is not limited to one of the following:

[0098] 10ms, 20ms, 40ms, 80ms, 160ms, 320ms.

[0099] Optionally, the value of the preset can include but is not limited to one of the following:

[0100] 4, 8, 16, 32.

[0101] Optionally, the uplink LBT failure configuration information can be, for example:

[0102]

[0103] It should be noted that in the embodiments of the present application, the handover command may further include DAPS handover configuration information.

[0104] Optionally, in the embodiments of the present application, when the detected number of consecutive uplink LBT failures is greater than the maximum number of consecutive uplink LBT failures, the terminal device triggers consecutive uplink LBT failures.

[0105] Optionally, in the embodiments of the present application, the terminal device sends the first information to the source base station during DAPS handover.

[0106] Correspondingly, the source base station receives the first information sent by the terminal device during DAPS handover.

[0107] Optionally, in some embodiments, when an uplink continuous LBT failure is triggered, the terminal device triggers an RLF of the SCG.

[0108] Optionally, in some other embodiments, when an uplink continuous LBT failure is triggered, the terminal device may also trigger an RLF of the MCG, that is, trigger a reconstruction process.

[0109] Optionally, the first information is SCG failure information (SCGFailureInformation).

[0110] Optionally, the terminal device may report SCG failure information (SCGFailureInformation) according to the SCG failure procedure. For example, as Figure 4 shown.

[0111] Optionally, in some other embodiments, when an uplink continuous LBT failure is triggered, the terminal device triggers a failure information (FailureInformation) reporting procedure and sets the failure type in the failure information to LBT failure during DAPS handover. For example, as Figure 5 shown.

[0112] Optionally, in some embodiments, the first information may be carried in SRB1.

[0113] The following details the procedure for triggering an uplink continuous LBT failure with an example. Specifically, the terminal device receives RRC configuration information, which includes LBT failure recovery configuration (lbt-FailureRecoveryConfig), and the LBT failure recovery configuration includes the maximum number of LBT failures (lbt-FailureInstanceMaxCount) and the LBT failure detection timer (lbt-FailureDetectionTimer). Additionally, an LBT counter (LBT_COUNTER) is introduced in the continuous LBT failure detection, which is used to record the number of LBT failures, and the initial value of the LBT counter is 0.

[0114] In this example, the MAC entity performs the following operations for each serving cell configured with LBT failure recovery configuration:

[0115] If an LBT failure indication is received from the lower layer, start or restart the LBT failure detection timer, and increment the count value of the LBT counter. If the count value of the LBT counter ≥ the maximum number of LBT failures, trigger a continuous LBT failure on the activated uplink BWP in this serving cell.

[0116] In addition, if the count value of the LBT counter ≥ the maximum number of LBT failures, and this serving cell is a special cell (such as the primary cell in MCG or the primary cell in SCG), if continuous LBT failures are triggered in all UL BWPs configured with PRACH on the same carrier of this serving cell, the MAC entity indicates continuous LBT failures to the upper layer; otherwise, stop any ongoing random access procedure in this serving cell; or, otherwise, switch the active UL BWP to the target UL BWP, which is on the same carrier of this serving cell, and the target UL BWP is configured with PRACH resources and no continuous LBT failures are triggered; or, otherwise, trigger a random access procedure.

[0117] As described above in conjunction with Figures 3 to 5 , the method embodiments of the present application are described in detail. Below in conjunction with Figures 6 to 10 , the apparatus embodiments of the present application are described in detail. It should be understood that the apparatus embodiments correspond to the method embodiments, and similar descriptions can refer to the method embodiments.

[0118] Figure 6 FIG. shows a schematic block diagram of a terminal device 300 according to an embodiment of the present application. As Figure 6 shown, the terminal device 300 includes:

[0119] A communication unit 310, configured to receive a handover command sent by a source base station, where the handover command is used to instruct the terminal device to perform a handover from a source cell to a target cell in a DAPS handover manner;

[0120] A processing unit 320, configured to initiate a random access procedure to a target base station according to the handover command;

[0121] In the case of triggering an uplink continuous LBT failure, the communication unit 310 is further configured to send first information to the source base station, where the first information is used to indicate that an uplink continuous LBT failure is triggered in the process of initiating a random access procedure to the target base station.

[0122] Optionally, the handover command includes uplink LBT failure configuration information.

[0123] Optionally, the uplink LBT failure configuration information includes a timer and / or a preset value, where the timer is used for uplink LBT failure detection, and the timer starts or restarts when an uplink LBT failure occurs; the preset value is the maximum number of uplink continuous LBT failures that trigger uplink LBT failure recovery.

[0124] Optionally, the processing unit 320 is further configured to detect uplink LBT failures and / or perform uplink LBT failure recovery operations during the handover process according to the uplink LBT failure configuration information.

[0125] Optionally, when the number of detected UL continuous LBT failures is greater than the maximum number of UL continuous LBT failures, the processing unit 320 is further configured to trigger a UL continuous LBT failure.

[0126] Optionally, the communication unit 310 is specifically configured to:

[0127] Send the first information to the source base station during DAPS handover.

[0128] Optionally, the processing unit 320 is further configured to trigger an RLF of the SCG.

[0129] Optionally, the first information is an SCG failure message.

[0130] Optionally, the processing unit 320 is further configured to trigger a failure message reporting process and set the failure type in the failure message to an LBT failure during DAPS handover.

[0131] Optionally, the first information is carried in SRB1.

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

[0133] It should be understood that the terminal device 300 according to the embodiments of the present application may correspond to the terminal device in the method embodiments of the present application, and the foregoing and other operations and / or functions of each unit in the terminal device 300 are respectively for implementing Figure 3 the corresponding processes executed by the terminal device in the method 200 shown. For the sake of brevity, details are not described herein again.

[0134] Figure 7 Fig. shows a schematic block diagram of a network device 400 according to an embodiment of the present application. As Figure 7 shown, the network device 400 is a source base station, and the network device 400 includes:

[0135] A communication unit 410, configured to send a handover command to a terminal device, where the handover command is used to instruct the terminal device to perform a handover from a source cell to a target cell in a DAPS handover manner;

[0136] The communication unit 410 is further configured to receive first information sent by the terminal device, where the first information is used to indicate that the terminal device has triggered an UL continuous LBT failure during a random access procedure to a target base station.

[0137] Optionally, the handover command includes UL LBT failure configuration information.

[0138] Optionally, the uplink LBT failure configuration information includes a timer and / or a preset value, where the timer is used for uplink LBT failure detection and is started or restarted when an uplink LBT failure occurs; the preset value is the maximum number of consecutive uplink LBT failures that trigger uplink LBT failure recovery.

[0139] Optionally, the uplink LBT failure configuration information is used for the terminal device to detect uplink LBT failures and / or perform uplink LBT failure recovery operations during handover.

[0140] Optionally, the communication unit 410 is specifically configured to:

[0141] Receive the first information sent by the terminal device during DAPS handover.

[0142] Optionally, the first information is SCG failure information.

[0143] Optionally, the first information is carried in SRB1.

[0144] Optionally, in some embodiments, the above communication unit may be a communication interface or transceiver, or an input / output interface of a communication chip or system-on-chip.

[0145] It should be understood that the network device 400 according to the embodiments of the present application may correspond to the source base station in the method embodiments of the present application, and the above and other operations and / or functions of each unit in the network device 400 are respectively for implementing Figure 3 the corresponding processes executed by the source base station in the method 200 shown, and for the sake of brevity, will not be elaborated here.

[0146] Figure 8 is a schematic structural diagram of a communication device 500 provided by an embodiment of the present application. Figure 8 The shown communication device 500 includes a processor 510, and the processor 510 can call and run a computer program from a memory to implement the method in the embodiments of the present application.

[0147] Optionally, as Figure 8 shown, the communication device 500 may further include a memory 520. Among them, the processor 510 can call and run a computer program from the memory 520 to implement the method in the embodiments of the present application.

[0148] Among them, the memory 520 may be a separate device independent of the processor 510, or may be integrated in the processor 510.

[0149] Optionally, as Figure 8As shown, the communication device 500 may further include a transceiver 530. The processor 510 may control the transceiver 530 to communicate with other devices. Specifically, it may send information or data to other devices, or receive information or data sent by other devices.

[0150] Among them, the transceiver 530 may include a transmitter and a receiver. The transceiver 530 may further include an antenna, and the number of antennas may be one or more.

[0151] Optionally, the communication device 500 may specifically be the network device of the embodiment of the present application, and the communication device 500 may implement the corresponding processes implemented by the source base station in each method of the embodiment of the present application. For the sake of brevity, details are not described herein again.

[0152] Optionally, the communication device 500 may specifically be the mobile terminal / terminal device of the embodiment of the present application, and the communication device 500 may implement the corresponding processes implemented by the mobile terminal / terminal device in each method of the embodiment of the present application. For the sake of brevity, details are not described herein again.

[0153] Figure 9 is a schematic structural diagram of the device of the embodiment of the present application. Figure 9 The device 600 shown includes a processor 610. The processor 610 may call and run a computer program from a memory to implement the methods in the embodiments of the present application.

[0154] Optionally, as Figure 9 shown, the device 600 may further include a memory 620. Among them, the processor 610 may call and run a computer program from the memory 620 to implement the methods in the embodiments of the present application.

[0155] Among them, the memory 620 may be a separate device independent of the processor 610, or may be integrated in the processor 610.

[0156] Optionally, the device 600 may further include an input interface 630. Among them, the processor 610 may control the input interface 630 to communicate with other devices or chips. Specifically, it may obtain information or data sent by other devices or chips.

[0157] Optionally, the device 600 may further include an output interface 640. Among them, the processor 610 may control the output interface 640 to communicate with other devices or chips. Specifically, it may output information or data to other devices or chips.

[0158] Optionally, the device may be applied to the source base station in the embodiments of the present application, and the device may implement the corresponding processes implemented by the source base station in each method of the embodiments of the present application. For the sake of brevity, details are not described herein again.

[0159] Optionally, the device can be applied to the mobile terminal / terminal device in the embodiments of the present application, and the device can implement the corresponding processes implemented by the mobile terminal / terminal device in each method of the embodiments of the present application. For the sake of brevity, it will not be elaborated here.

[0160] Optionally, the device mentioned in the embodiments of the present application can also be a chip. For example, it can be a system-on-chip, system chip, chip system or system-on-chip, etc.

[0161] Figure 10 is a schematic block diagram of a communication system 700 provided by the embodiments of the present application. As Figure 10 shown, the communication system 700 includes a terminal device 710 and a network device 720.

[0162] Among them, the terminal device 710 can be used to implement the corresponding functions implemented by the terminal device in the above method, and the network device 720 can be used to implement the corresponding functions implemented by the source base station in the above method. For the sake of brevity, it will not be elaborated here.

[0163] It should be understood that the processor in the embodiments of the present application may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method embodiments can be completed by the integrated logic circuit in the hardware of the processor or by instructions in software form. The above-mentioned processor can be 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 devices, discrete gate or transistor logic devices, discrete hardware components. It can implement or execute the various methods, steps and logic block diagrams disclosed in the embodiments of the present application. The general-purpose processor can be a microprocessor or the processor can also be any conventional processor, etc. The steps of the method disclosed in combination with the embodiments of the present application can be directly embodied as being executed by the hardware decoding processor, or executed by a combination of the hardware and software modules in the decoding processor. The software module can be located in a mature storage medium in the art such as a random access memory, flash memory, read-only memory, programmable read-only memory or electrically erasable programmable memory, register, etc. The storage medium is located in the memory, and the processor reads the information in the memory and combines its hardware to complete the steps of the above method.

[0164] 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 but 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), synchlink dynamic random access memory (SLDRAM), and direct rambus random access memory (DR RAM). It should be noted that the memory of the systems and methods described herein is intended to include but not be limited to these and any other suitable types of memory.

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

[0166] The embodiments of the present application also provide a computer-readable storage medium for storing a computer program.

[0167] Optionally, the computer-readable storage medium can be applied to the source base station in the embodiments of the present application, and the computer program enables the computer to execute the corresponding processes implemented by the source base station in the various methods of the embodiments of the present application. For the sake of brevity, details are not described herein again.

[0168] 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, details are not described herein again.

[0169] The embodiments of the present application also provide a computer program product including computer program instructions.

[0170] Optionally, the computer program product can be applied to the source base station in the embodiments of the present application, and the computer program instructions enable the computer to execute the corresponding processes implemented by the source base station in the various methods of the embodiments of the present application. For the sake of brevity, details are not described herein again.

[0171] 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, details are not described herein again.

[0172] The embodiments of the present application also provide a computer program.

[0173] Optionally, the computer program can be applied to the source base station in the embodiments of the present application. When the computer program runs on the computer, it enables the computer to execute the corresponding processes implemented by the source base station in the various methods of the embodiments of the present application. For the sake of brevity, details are not described herein again.

[0174] 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, it 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, details are not described herein again.

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

[0176] 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 foregoing method embodiments and will not be elaborated herein.

[0177] In several embodiments provided in this 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 merely illustrative. For example, the division of the units is only a logical function division, and there can be other division methods in actual implementation. For example, 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 displayed or discussed couplings or direct couplings or communication connections to each other can be through some interfaces, and the indirect couplings or communication connections of the devices or units can be in electrical, mechanical, or other forms.

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

[0179] In addition, the functional units in each embodiment of this application can be integrated in a processing unit, or each unit can exist physically alone, or two or more units can be integrated in one unit.

[0180] When the above-mentioned 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 understanding, the technical solution of this application, essentially or the part that contributes to the prior art or a part of this technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in various embodiments of this application. The foregoing storage medium includes: various media such as USB flash drives, mobile hard disks, read-only memories (ROMs), random access memories (RAMs), magnetic disks, or optical discs that can store program codes.

[0181] As described above, the above are only specific implementation manners of this application, but the protection scope of this application is not limited thereto. Any person skilled in the art within the technical scope disclosed by this application can easily think of changes or substitutions, which should all be covered by the protection scope of this application. Therefore, the protection scope of this application should be subject to the protection scope of the claims.

Claims

1. A wireless communication method, characterized in that, it includes: The terminal device receives a handover command sent by the source base station, and the handover command is used to instruct the terminal device to switch from the source cell to the target cell by using the dual active protocol stack DAPS handover mode; The terminal device initiates a random access procedure to the target base station according to the handover command, wherein the handover command includes uplink LBT failure configuration information; In the case of triggering an uplink continuous listen-before-transmit LBT failure, the terminal device sends a first message to the source base station during the DAPS handover, and the first message is used to indicate that an uplink continuous LBT failure is triggered during the random access procedure to the target base station; Wherein, the terminal device sending the first message to the source base station during the DAPS handover includes: If the serving cell of the terminal device is a special cell, and a continuous LBT failure is triggered in all uplink bandwidth parts BWPs configured with the physical random access channel PRACH on the same carrier of the serving cell, the terminal device sends the first message to the source base station during the DAPS handover, otherwise, stop any ongoing random access procedure in this serving cell, or switch the activated UL BWP to the target UL BWP, which is on the same carrier of this serving cell, and the target UL BWP is configured with PRACH resources and no continuous LBT failure is triggered; The method further includes: The terminal device triggers a failure information reporting process, and sets the failure type in the failure information to the LBT failure during the DAPS handover, wherein the first message is carried in the signaling radio bearer SRB1.

2. The method according to claim 1, characterized in that, The uplink LBT failure configuration information includes a timer and / or a preset value, wherein the timer is used for uplink LBT failure detection, and the timer starts or restarts when an uplink LBT failure occurs; the preset value is the maximum number of uplink continuous LBT failures that trigger uplink LBT failure recovery.

3. The method according to claim 1, characterized in that, The method further includes: The terminal device detects uplink LBT failure and / or performs uplink LBT failure recovery operations during the handover according to the uplink LBT failure configuration information.

4. The method according to any one of claims 1 to 3, characterized in that, The method further includes: In the case where the detected number of uplink continuous LBT failures is greater than the maximum number of uplink continuous LBT failures, the terminal device triggers an uplink continuous LBT failure.

5. A wireless communication method, characterized in that, it includes: The source base station sends a handover command to the terminal device, and the handover command is used to instruct the terminal device to switch from the source cell to the target cell by using the dual active protocol stack DAPS handover mode, wherein the handover command includes uplink LBT failure configuration information; The source base station receives first information sent by the terminal device during DAPS handover, where the first information is used to indicate that the terminal device has triggered an uplink Listen-Before-Talk (LBT) failure during the random access procedure initiated towards the target base station; Among them, the first information is sent when continuous LBT failures are triggered in all the uplink bandwidth parts (BWPs) configured with Physical Random Access Channel (PRACH) on the same carrier of the serving cell of the terminal, and the serving cell is a special cell; Among them, the first information is carried in the Signaling Radio Bearer (SRB1), and the first information is sent after the terminal device triggers a failure information reporting procedure and sets the failure type in the failure information to the LBT failure during DAPS handover.

6. The method according to claim 5, characterized in that, the uplink LBT failure configuration information includes a timer and / or a preset value, where the timer is used for uplink LBT failure detection, and the timer starts or restarts when an uplink LBT failure occurs; the preset value is the maximum number of consecutive uplink LBT failures that trigger uplink LBT failure recovery.

7. The method according to claim 5 or 6, characterized in that, the uplink LBT failure configuration information is used for the terminal device to detect uplink LBT failures and / or perform uplink LBT failure recovery operations during handover.

8. A terminal device, characterized in that, comprising: a communication unit, configured to receive a handover command sent by a source base station, where the handover command is used to instruct the terminal device to perform a Dual-Active Protocol Stack (DAPS) handover from a source cell to a target cell; a processing unit, configured to initiate a random access procedure towards the target base station according to the handover command, where the handover command includes uplink LBT failure configuration information; in case of triggering an uplink Listen-Before-Talk (LBT) failure, the communication unit is further configured to send first information to the source base station during DAPS handover, where the first information is used to indicate that an uplink continuous LBT failure has been triggered during the random access procedure initiated towards the target base station; otherwise, stop any ongoing random access procedure in this serving cell, or switch the activated UL BWP to the target UL BWP, where the target UL BWP is on the same carrier of this serving cell, the target UL BWP is configured with PRACH resources, and no continuous LBT failure has been triggered; wherein, the processing unit is specifically configured to: if the serving cell of the terminal device is a special cell, and continuous LBT failures are triggered in all the uplink bandwidth parts (BWPs) configured with Physical Random Access Channel (PRACH) on the same carrier of the serving cell, send the first information to the source base station during DAPS handover; the processing unit is further configured to trigger a failure information reporting procedure and set the failure type in the failure information to the LBT failure during DAPS handover, where the first information is carried in the Signaling Radio Bearer (SRB1).

9. The terminal device according to claim 8, characterized in that, The uplink LBT failure configuration information includes a timer and / or a preset value. Among them, the timer is used for uplink LBT failure detection, and the timer starts or restarts when uplink LBT failure occurs; the preset value is the maximum number of consecutive uplink LBT failures that trigger uplink LBT failure recovery.

10. The terminal device according to claim 8, wherein, the processing unit is further configured to detect uplink LBT failure and / or perform uplink LBT failure recovery operations during the handover process according to the uplink LBT failure configuration information.

11. The terminal device according to any one of claims 8 to 10, wherein, in the case where the detected number of consecutive uplink LBT failures is greater than the maximum number of consecutive uplink LBT failures, the processing unit is further configured to trigger consecutive uplink LBT failure.

12. A network device, wherein, the network device is a source base station, and the network device includes: a communication unit, configured to send a handover command to a terminal device, the handover command being used to instruct the terminal device to perform a Dual Active Protocol Stack (DAPS) handover from a source cell to a target cell, wherein the handover command includes uplink LBT failure configuration information; the communication unit is further configured to receive first information sent by the terminal device during the DAPS handover, the first information being used to indicate that the terminal device triggers an uplink consecutive Listen Before Talk (LBT) failure during a random access procedure to the target base station; wherein, the first information is sent when continuous LBT failure is triggered in all uplink bandwidth parts (BWPs) configured with a Physical Random Access Channel (PRACH) on the same carrier of the serving cell of the terminal and the serving cell is a special cell; the first information is carried in a Signaling Radio Bearer (SRB1), and the first information is sent after the terminal device triggers a failure information reporting procedure and sets the failure type in the failure information to LBT failure during DAPS handover.

13. The network device according to claim 12, wherein, the uplink LBT failure configuration information includes a timer and / or a preset value. Among them, the timer is used for uplink LBT failure detection, and the timer starts or restarts when uplink LBT failure occurs; the preset value is the maximum number of consecutive uplink LBT failures that trigger uplink LBT failure recovery.

14. The network device according to claim 12 or 13, wherein, the uplink LBT failure configuration information is used for the terminal device to detect uplink LBT failure and / or perform uplink LBT failure recovery operations during the handover process.

15. A terminal device, wherein, includes: a processor and a memory, 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 according to any one of claims 1 to 4.

16. A network device, wherein, includes: A processor and a memory for storing a computer program, the processor being configured to call and run the computer program stored in the memory to execute the method according to any one of claims 5 to 7.

17. A chip, characterized in that it comprises: a processor configured to call and run a computer program from a memory, such that a device installed with the chip executes the method according to any one of claims 1 to 4.

18. A chip, characterized in that it comprises: a processor configured to call and run a computer program from a memory, such that a device installed with the chip executes the method according to any one of claims 5 to 7.

19. A computer-readable storage medium, characterized in that it is configured to store a computer program, the computer program causing a computer to execute the method according to any one of claims 1 to 4.

20. A computer-readable storage medium, characterized in that it is configured to store a computer program, the computer program causing a computer to execute the method according to any one of claims 5 to 7.

Images