WO2021232383A1 - 小区切换中的持续lbt失败检测和恢复的方法及装置 - Google Patents

小区切换中的持续lbt失败检测和恢复的方法及装置 Download PDF

Info

Publication number
WO2021232383A1
WO2021232383A1 PCT/CN2020/091672 CN2020091672W WO2021232383A1 WO 2021232383 A1 WO2021232383 A1 WO 2021232383A1 CN 2020091672 W CN2020091672 W CN 2020091672W WO 2021232383 A1 WO2021232383 A1 WO 2021232383A1
Authority
WO
WIPO (PCT)
Prior art keywords
cell
lbt failure
recovery
network device
continuous
Prior art date
Application number
PCT/CN2020/091672
Other languages
English (en)
French (fr)
Inventor
贾美艺
李国荣
路杨
张磊
Original Assignee
富士通株式会社
贾美艺
李国荣
路杨
张磊
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 富士通株式会社, 贾美艺, 李国荣, 路杨, 张磊 filed Critical 富士通株式会社
Priority to JP2022568974A priority Critical patent/JP2023526276A/ja
Priority to CN202080100636.7A priority patent/CN115516989A/zh
Priority to PCT/CN2020/091672 priority patent/WO2021232383A1/zh
Publication of WO2021232383A1 publication Critical patent/WO2021232383A1/zh
Priority to US17/983,572 priority patent/US20230072832A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/08—Non-scheduled access, e.g. ALOHA
    • H04W74/0808—Non-scheduled access, e.g. ALOHA using carrier sensing, e.g. carrier sense multiple access [CSMA]
    • H04W74/0825—Non-scheduled access, e.g. ALOHA using carrier sensing, e.g. carrier sense multiple access [CSMA] with collision detection
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0055—Transmission or use of information for re-establishing the radio link
    • H04W36/0079—Transmission or use of information for re-establishing the radio link in case of hand-off failure or rejection
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/08—Non-scheduled access, e.g. ALOHA
    • H04W74/0808—Non-scheduled access, e.g. ALOHA using carrier sensing, e.g. carrier sense multiple access [CSMA]

Definitions

  • the invention relates to the field of communications.
  • LBT Listen Before Talk
  • DMTC Discovery RS Measurement Timing Configuration
  • the continuous LBT failure detection and recovery mechanism refers to the detection of possible continuous LBT failures, and actions are taken to make the terminal fail from the detected continuous LBT failure recover.
  • the continuous LBT failure detection and recovery mechanism can also be referred to as the continuous LBT failure detection and recovery mechanism for uplink transmission, the LBT failure detection and recovery mechanism, the uplink LBT failure detection and recovery mechanism, or the continuous uplink LBT failure detection and recovery mechanism.
  • the continuous LBT failure detection and recovery mechanism can be the LBT failure detection process (also known as the continuous LBT failure detection process for uplink transmission), or the LBT failure recovery process (also known as the continuous LBT failure recovery process for uplink transmission), or both include LBT
  • the failure detection process also called the continuous LBT failure detection process of uplink transmission
  • also includes the LBT failure recovery process also called the continuous LBT failure recovery process of uplink transmission.
  • the Radio Resource Control (RRC) layer can configure the MAC entity of the Media Access Control (Medio Access Control, MAC) layer with a continuous LBT recovery process.
  • the detection of continuous LBT failure is performed on each upstream BWP (Bandwidth Part).
  • the MAC entity performs detection by counting the number of received LBT failure indications for all uplink transmissions from the lower layer (for example, the physical layer).
  • an LBT counter such as LBT_COUNTER
  • a timer are introduced.
  • the timer is started or restarted.
  • the MAC layer receives an upstream LBT failure indication from the lower layer, the counter is incremented by 1.
  • the count value exceeds the preset value, the continuous LBT failure is triggered.
  • the timer expires, the counter is reset.
  • LBT failure recovery configuration parameters such as lbt-FailureRecoveryConfig
  • LBT_COUNTER the LBT counter
  • maximum value of LBT failure such as lbt-FailureInstanceMaxCount
  • the serving cell is a special cell (SpCell)
  • PRACH occasions physical random access channel opportunity
  • UL BWP all uplink BWP
  • the MAC entity will indicate to the upper layer (such as the RRC layer) that the LBT fails to continue; otherwise, the MAC entity will stop any ongoing random access process in the serving cell, and switch to activate the UL BWP to the same carrier in the serving cell
  • the MAC entity will stop any ongoing random access process in the serving cell, and switch to activate the UL BWP to the same carrier in the serving cell
  • a UL BWP that is configured with PRACH occasion and has not yet triggered the continuous LBT failure and initiates a random access procedure.
  • Cell handover refers to the process of terminal equipment switching from data transmission through the source cell and network to data transmission through the target cell and network, including handover preparation (Handover Prepartion), handover execution (Handover Execution), and handover completion (Handover Completion) Three processes.
  • handover preparation Handover Prepartion
  • handover execution Handover Execution
  • handover completion Handover Completion
  • the network device of the source cell sends an RRC reconfiguration message (RRCReconfiguration message) to the terminal device to trigger the Uu handover, that is, the handover between the source cell and the target cell involved in the Uu port.
  • RRCReconfiguration message RRC reconfiguration message
  • the message includes the information required to access the target cell ;
  • the terminal device synchronizes to the target cell and completes the RRC handover process by sending an RRC reconfiguration complete message (RRCReconfigurationComplete message) to the network device of the target cell.
  • RRC reconfiguration Complete message (RRCReconfigurationComplete message)
  • DAPS Dual Active Protocol Stack
  • the terminal device receives the RRC reconfiguration message, the terminal device does not detach from the source cell, and the terminal device continues to connect to the source cell's network
  • the device performs data transmission.
  • the terminal device releases the signalling radio bearers (SRB) resources of the source cell and the security configuration of the source cell, and stops the downlink and/or connection with the source cell. Or uplink (DL/UL) transmission.
  • SRB signalling radio bearers
  • SCG configuration or secondary cell group
  • PSCell change primary and secondary cell change
  • a continuous uplink LBT failure indication from MCG MAC is received: if the continuous LBT failure indication is on the target cell, then, according to the existing mechanism, the terminal device will reestablish the connection regardless of whether the handover is successful. In addition, when the cell is switched to DAPS, if the persistent LBT failure indication is on the source cell, then, according to the existing mechanism, the terminal device will reestablish the connection regardless of whether the handover is successful.
  • the terminal device can use the target cell for transmission after the handover is successful. Therefore, the current mechanism may cause unnecessary connection re-establishment, resulting in interruption of user services, and thus a decrease in user experience.
  • the embodiments of the present application provide a method and device for detecting and recovering from continuous LBT failure in cell handover.
  • an apparatus for detecting and recovering from a continuous LBT failure in a cell handover is applied to a terminal device.
  • the apparatus includes: a first processing unit configured to , Receiving a continuous LBT failure indication; and, stopping the data transmission and/or receiving with the network device, and/or, the second processing unit, which is used to suspend continuous LBT failure detection and recovery during the cell handover.
  • an apparatus for detecting and recovering from continuous LBT failure in cell handover is applied to terminal equipment.
  • the apparatus includes: a third processing unit for When receiving the continuous LBT failure indication, stop data transmission and/or reception with the network device, and/or, the fourth processing unit, which is used to suspend continuous LBT failure detection and recovery during the cell handover.
  • an apparatus for detecting and recovering from a continuous LBT failure in a cell handover is applied to a network device.
  • the apparatus includes: a first sending unit configured to send An RRC reconfiguration message, where the RRC reconfiguration message includes configuration information related to LBT failure detection and recovery.
  • a terminal device which includes the apparatus according to the first aspect or the second aspect of the embodiments of the present application.
  • a network device including the apparatus according to the third aspect of the embodiments of the present application.
  • a communication system which includes the terminal device according to the fourth aspect of the embodiments of the present application and/or the terminal device according to the fifth aspect of the embodiments of the present application Network equipment.
  • a method for detecting and recovering a continuous LBT failure in a cell handover is provided.
  • the method is applied to a terminal device, and the method includes: receiving a continuous LBT failure indication during a cell handover;
  • the data transmission and/or reception with the network device is stopped, and/or the continuous LBT failure detection and recovery is suspended during the cell handover.
  • a method for detecting and recovering a continuous LBT failure in a cell handover is applied to a terminal device.
  • the method includes: during a cell handover, when a continuous LBT failure indication is received At the time, stop sending and/or receiving data with the network device, and/or, during the cell handover, suspend continuous LBT failure detection and recovery.
  • a method for detecting and recovering from continuous LBT failure in cell handover is provided.
  • the method is applied to a network device.
  • the method includes: sending an RRC reconfiguration message to a terminal device.
  • the reconfiguration message includes configuration information related to LBT failure detection and recovery.
  • a computer-readable program wherein when the program is executed in an apparatus or terminal device for continuous LBT failure detection and recovery in a cell handover, the The program makes the apparatus or terminal device for detecting and recovering from continuous LBT failure in cell handover execute the method for detecting and recovering from continuous LBT failure in cell handover according to the seventh aspect or the eighth aspect of the embodiment of the present invention.
  • a storage medium storing a computer-readable program, wherein the computer-readable program enables an apparatus or terminal device for detecting and recovering a continuous LBT failure in a cell handover to execute this
  • the seventh aspect or the eighth aspect of the embodiment of the invention is the method for detecting and recovering from a continuous LBT failure in a cell handover.
  • a computer-readable program wherein when the program is executed in an apparatus or a network device for detecting and recovering from a continuous LBT failure in a cell handover, the program causes all
  • the apparatus or network equipment for detecting and recovering from continuous LBT failure in cell handover executes the method for detecting and recovering from continuous LBT failure in cell handover according to the ninth aspect of the embodiment of the present invention.
  • a storage medium storing a computer readable program, wherein the computer readable program enables an apparatus or network device for detecting and recovering a continuous LBT failure in a cell handover to implement the present invention
  • One of the beneficial effects of the embodiments of the present application is that during the cell handover, when receiving a continuous LBT failure indication, the terminal device stops sending and/or receiving data with the network device, and/or, during the cell handover, the terminal device Suspend continuous LBT failure detection and recovery. In this way, during the cell handover, the terminal device will not initiate a connection re-establishment process due to continuous LBT failure, thereby avoiding the resulting user service interruption and user experience degradation.
  • Fig. 1 is a schematic diagram of a communication system according to an embodiment of the present application.
  • Figure 2 is a schematic diagram of a cell handover process in an embodiment of the present application.
  • Fig. 3 is a schematic diagram of a method for detecting and recovering from continuous LBT failure in cell handover in Embodiment 1 of the present application;
  • FIG. 4 is a schematic diagram of a method for detecting and recovering a continuous LBT failure in a cell handover in Embodiment 1 of the present application;
  • FIG. 5 is a schematic diagram of stopping data transmission and/or reception with a network device in Embodiment 1 of the present application;
  • FIG. 6 is another schematic diagram of stopping data transmission and/or reception with a network device in Embodiment 1 of the present application;
  • FIG. 7 is another schematic diagram of stopping data transmission and/or reception with a network device in Embodiment 1 of the present application.
  • FIG. 8 is a schematic diagram of a method for detecting and recovering a continuous LBT failure in a cell handover according to Embodiment 2 of the present application;
  • FIG. 9 is a schematic diagram of a method for detecting and recovering a continuous LBT failure in a cell handover according to Embodiment 3 of the present application.
  • FIG. 10 is a schematic diagram of an apparatus for detecting and recovering a continuous LBT failure in a cell handover according to Embodiment 4 of the present application;
  • FIG. 11 is a schematic diagram of an apparatus for detecting and recovering a continuous LBT failure in a cell handover according to Embodiment 5 of the present application;
  • FIG. 12 is a schematic block diagram of the system configuration of a terminal device according to Embodiment 6 of the present invention.
  • FIG. 13 is a schematic block diagram of the system configuration of a network device according to Embodiment 7 of the present invention.
  • the terms “first”, “second”, etc. are used to distinguish different elements from the terms, but they do not indicate the spatial arrangement or chronological order of these elements. These elements should not be used by these terms. Limited.
  • the term “and/or” includes any and all combinations of one or more of the associated listed terms.
  • the terms “comprising”, “including”, “having” and the like refer to the existence of the stated features, elements, elements or components, but do not exclude the presence or addition of one or more other features, elements, elements or components.
  • the term "communication network” or “wireless communication network” can refer to a network that meets any of the following communication standards, such as Long Term Evolution (LTE), and Enhanced Long Term Evolution (LTE-A, LTE-A). Advanced), Wideband Code Division Multiple Access (WCDMA, Wideband Code Division Multiple Access), High-Speed Packet Access (HSPA, High-Speed Packet Access), etc.
  • LTE Long Term Evolution
  • LTE-A Enhanced Long Term Evolution
  • LTE-A LTE-A
  • Advanced Wideband Code Division Multiple Access
  • WCDMA Wideband Code Division Multiple Access
  • High-Speed Packet Access High-Speed Packet Access
  • HSPA High-Speed Packet Access
  • the communication between devices in the communication system can be carried out according to any stage of communication protocol, for example, it can include but not limited to the following communication protocols: 1G (generation), 2G, 2.5G, 2.75G, 3G, 4G, 4.5G and future 5G, New Radio (NR, New Radio), etc., and/or other communication protocols currently known or to be developed in the future.
  • 1G generation
  • 2G 2.5G
  • 2.75G 3G
  • 4G 4G
  • 4.5G future 5G
  • New Radio NR, New Radio
  • Network device refers to, for example, a device in a communication system that connects a user equipment to a communication network and provides services for the user equipment.
  • Network equipment may include but not limited to the following equipment: base station (BS, Base Station), access point (AP, Access Point), transmission and reception point (TRP, Transmission Reception Point), broadcast transmitter, mobile management entity (MME, Mobile Management Entity), gateway, server, radio network controller (RNC, Radio Network Controller), base station controller (BSC, Base Station Controller), etc.
  • the base station may include but is not limited to: Node B (NodeB or NB), evolved Node B (eNodeB or eNB), 5G base station (gNB), etc., and may also include remote radio head (RRH, Remote Radio Head) , Remote Radio Unit (RRU, Remote Radio Unit), relay (relay), or low-power node (such as femto, pico, etc.).
  • NodeB Node B
  • eNodeB or eNB evolved Node B
  • gNB 5G base station
  • RRH Remote Radio Head
  • RRU Remote Radio Unit
  • relay relay
  • low-power node such as femto, pico, etc.
  • base station can include some or all of their functions, and each base station can provide communication coverage for a specific geographic area.
  • the term "cell” may refer to a base station and/or its coverage area, depending on the context in which the term is used.
  • the term "User Equipment” refers to, for example, a device that accesses a communication network through a network device and receives network services, and may also be referred to as "Terminal Equipment” (TE, Terminal Equipment).
  • the terminal device may be fixed or mobile, and may also be called a mobile station (MS, Mobile Station), terminal, subscriber station (SS, Subscriber Station), access terminal (AT, Access Terminal), station, etc.
  • terminal devices may include but are not limited to the following devices: cellular phones (Cellular Phone), personal digital assistants (PDAs, Personal Digital Assistant), wireless modems, wireless communication devices, handheld devices, machine-type communication devices, laptop computers, Cordless phones, smart phones, smart watches, digital cameras, etc.
  • cellular phones Cellular Phone
  • PDAs personal digital assistants
  • wireless modems wireless communication devices
  • handheld devices machine-type communication devices
  • laptop computers Cordless phones
  • smart phones smart watches, digital cameras, etc.
  • a terminal device may also be a machine or device that performs monitoring or measurement.
  • it may include, but is not limited to: Machine Type Communication (MTC) terminals, In-vehicle communication terminals, device to device (D2D, Device to Device) terminals, machine to machine (M2M, Machine to Machine) terminals, etc.
  • MTC Machine Type Communication
  • D2D Device to Device
  • M2M Machine to Machine
  • FIG. 1 is a schematic diagram of a communication system according to an embodiment of the present application, which schematically illustrates a case where a terminal device and a network device are taken as examples.
  • the communication system 100 may include: a first network device 101, a second network device 101, and a second network device.
  • Network equipment 102 and terminal equipment 103 are, for example, NR network devices gNB.
  • the first network device 101, the second network device 102, and the terminal device 103 can perform existing services or services that can be implemented in the future.
  • these services include but are not limited to: enhanced mobile broadband (eMBB, enhanced Mobile Broadband), large-scale machine type communication (mMTC, massive Machine Type Communication), and high-reliability and low-latency communication (URLLC, Ultra-Reliable and Low- Latency Communication), etc.
  • the terminal device 103 performs a cell handover
  • the first network device 101 is the network device of the source cell of the cell handover
  • the second network device 102 is the network device of the target cell of the cell handover.
  • the first network device 101 is the source network device or The source base station
  • the second network device 102 is a target network device or a target base station.
  • the first network device 101 may cover multiple cells including the source cell, and the multiple cells may be referred to as cells belonging to the first network device 101; the second network device 102 may cover multiple cells including the target cell.
  • a cell the multiple cells may be referred to as cells belonging to the second network device 102.
  • FIG. 2 is a schematic diagram of a cell handover process in an embodiment of the present application.
  • the terminal device 103 and the first network device 101 of the source cell exchange user data.
  • the terminal device 103 performs measurement control and reporting (Measurement Control and Reports);
  • the first network device 101 performs a handover decision (Handover Decision);
  • the first network device 101 sends a handover request (HANDOVER REQUEST) to the second network device 102;
  • the second network device 102 performs a handover decision.
  • Admission Control In step 205, the second network device 102 sends a handover request confirmation (HANDOVER REQUEST ACKNOWLEDGE) message to the first network device 101.
  • HANDOVER REQUEST ACKNOWLEDGE handover request confirmation
  • the handover request confirmation message may include the information required to access the target cell and Configuration information related to LBT failure detection and recovery.
  • the configuration information related to LBT failure detection and recovery is configuration information for the terminal to perform continuous LBT failure detection and recovery on the cell in the target network device; in step 206, perform RAN handover Start (RAN Handover Initiation).
  • the first network device 101 sends an RRC reconfiguration message (RRCReconfiguration message) to the terminal device 103 to trigger the Uu handover, that is, the handover between the source cell and the target cell involved in the Uu port.
  • RRCReconfiguration message RRC reconfiguration message
  • the message includes the access Information required by the target cell and configuration information related to LBT failure detection and recovery; in step 207, the first network device 101 sends SN STATUS TRANSFER to the second network device 102; in step 208, the terminal device 103 performs RAN Handover Completion. Specifically, the terminal device 103 synchronizes to the target cell and completes the RRC handover process by sending an RRC reconfiguration complete message (RRCReconfigurationComplete message) to the second network device 102 of the target cell.
  • RRCReconfigurationComplete message RRC reconfiguration complete message
  • the terminal device 103 When the cell handover is a Dual Active Protocol Stack (DAPS) handover, when the terminal device 103 receives the RRC reconfiguration message, the terminal device 103 does not detach from the source cell, and continues the downlink with the source cell And/or uplink (DL/UL) transmission.
  • the terminal device 103 When receiving an explicit release from the second network device 102 of the target cell, the terminal device 103 releases the signalling radio bearers (SRB) resources of the source cell and the security configuration of the source cell, and stops communicating with the source cell. Downlink and/or uplink (DL/UL) transmission.
  • SRB signalling radio bearers
  • LBT failure may occur.
  • the MAC layer of the terminal device 103 receives an LBT failure indication from the physical layer and the LBT counter is greater than or equal to the maximum value of LBT failure, the MAC layer of the terminal device 103 triggers the activation of the source cell and/or target cell Continuous LBT failure on BWP.
  • the MAC indicates the continuous LBT failure to the higher layer. If the continuous LBT failure indication is provided by the target MAC, that is, due to the continuous LBT failure on the target cell, indicating the continuous LBT failure to the higher layer, then, according to the existing mechanism, the terminal device 103 will perform connection re-establishment regardless of whether the handover is successful.
  • the terminal device 103 will Perform connection re-establishment, regardless of whether the handover is successful or not. In fact, if the terminal device 103 does not perform connection re-establishment, the terminal device 103 can use the target cell for transmission after the handover is successful. Therefore, the current mechanism may cause unnecessary connection re-establishment, resulting in interruption of user services, and thus a decrease in user experience.
  • the embodiment of the present application provides a method for detecting and recovering from a continuous LBT failure in a cell handover, and the method is applied to a terminal device.
  • this method is applied to the terminal device 103 in FIG. 1.
  • FIG. 3 is a schematic diagram of a method for detecting and recovering a continuous LBT failure in a cell handover in Embodiment 1 of the present application. As shown in Figure 3, the method includes:
  • Step 301 During the cell handover, receive a continuous LBT failure indication; and stop sending and/or receiving data with the network device, and/or,
  • Step 302 During the cell handover, the continuous LBT failure detection and recovery detection and recovery are suspended.
  • the method for detecting and recovering from a persistent LBT failure refers to a method for detecting a persistent LBT failure and a method for recovering a terminal device from a persistent LBT failure.
  • the cell handover period refers to the period during which cell handover is performed.
  • the cell handover period refers to the handover execution period, such as the period from step 206 to step 208 in FIG. 2.
  • step 301 during the cell handover, the terminal device receives a continuous LBT failure indication; and the terminal device stops sending and/or receiving data with the network device. For example, during the cell handover, when the terminal device receives a continuous LBT failure indication, the terminal device stops sending and/or receiving data with the network device. For another example, during the cell handover, the terminal device receives a continuous LBT failure indication; and when other conditions are met, the terminal device stops sending and/or receiving data with the network device.
  • FIG. 4 is a schematic diagram of a method for detecting and recovering a continuous LBT failure in a cell handover in Embodiment 1 of the present application. As shown in Figure 4, the method includes:
  • Step 401 During the cell handover, when receiving a continuous LBT failure indication, stop sending and/or receiving data with the network device, and/or,
  • Step 402 Suspend continuous LBT failure detection and recovery detection and recovery during the cell handover.
  • the terminal device when receiving the continuous LBT failure indication, the terminal device stops sending and/or receiving data with the network device, and/or, during the cell handover, the terminal device suspends the continuous LBT failure detection and recovery. In this way, during the cell handover, the terminal device will not initiate a connection re-establishment process due to continuous LBT failure, thereby avoiding the resulting user service interruption and user experience degradation.
  • that the terminal device receives the persistent LBT failure indication means that the RRC layer of the terminal device receives the persistent LBT failure indication.
  • the continuous LBT failure indication is also referred to as the continuous uplink LBT failure indication.
  • the physical layer of the terminal device performs LBT on the uplink transmission, and when the LBT fails, it indicates the LBT failure to the MAC layer.
  • the count value LBT_COUNTER is increased by 1.
  • the count value exceeds a preset value, for example, LBT_COUNTER ⁇ lbt-FailureInstanceMaxCount, the MAC layer triggers continuous LBT failure.
  • the serving cell is a special cell (SpCell)
  • the activated uplink BWP (UL BWP) of this serving cell triggers continuous LBT failure
  • it will switch to another BWP and initiate random access
  • All uplink BWPs (UL BWPs) configured with physical random access channel occasions (PRACH occasions) on the same carrier have triggered continuous LBT failure
  • the MAC entity will indicate to the higher layer, such as the RRC layer, the continuous LBT failure.
  • the cell handover may be: dual active protocol stack (DAPS) handover, or dual active protocol stack (DAPS) handover and non-DAPS handover, or non-DAPS handover.
  • DAPS dual active protocol stack
  • DAPS dual active protocol stack
  • dual active protocol stack (DAPS) handover refers to reconfiguration with sync in order to perform a reconfiguration with sync, and if dapsConfig is configured for any (any) DRB;
  • dual active protocol stack (DAPS) handover and non-DAPS handover It refers to reconfiguration in order to perform synchronization (a reconfiguration with sync);
  • non-DAPS handover refers to reconfiguration in order to perform synchronization (a reconfiguration with sync), and no (any) DRB is configured with dapsConfig.
  • cell handover refers to a process in which a terminal device performs data transmission through a source cell and a network and switches to perform data transmission through a target cell and the network.
  • the source cell belongs to a first network device
  • the target cell belongs to a second network device
  • the first network device may be referred to as a source base station
  • the second network device may be referred to as a target base station.
  • the source cell and the target cell are respectively a serving cell.
  • CA carrier aggregation
  • DC dual connectivity
  • the source cell and the target cell are the primary cells.
  • the first network device may cover multiple cells, the multiple cells including the source cell (primary cell), and may also include other cells, such as secondary cells;
  • the network device may also cover multiple cells, the multiple cells including the target cell (primary cell), and may also include other cells, such as secondary cells.
  • the method may include both step 301 and step 302, or include both step 401 and step 402.
  • step 301 and step 302 for example, during the cell handover, a continuous LBT failure indication is received, and/or data transmission and/or reception with the network device is stopped; and continuous LBT failure detection and recovery are suspended.
  • a continuous LBT failure indication is received; and the data transmission and/or reception with the network device is stopped; and the continuous LBT failure detection and recovery is suspended.
  • step 401 and step 402 for example, during cell handover, when a continuous LBT failure indication is received, and/or when data transmission and/or reception with the network device is stopped, the continuous LBT failure detection and recovery are suspended .
  • the continuous LBT failure detection and recovery are suspended;
  • the method may execute different steps for different cells, that is, different solutions may be adopted for different cells.
  • the cell handover is a dual active protocol stack (DAPS) handover, which corresponds to step 301 and step 302.
  • DAPS dual active protocol stack
  • a continuous LBT failure indication is received; and data transmission and reception with the first network device is stopped, and/ Or, during the cell handover, the continuous LBT failure detection and recovery of the second cell by the terminal device is suspended.
  • the cell handover is a dual active protocol stack (DAPS) handover, which corresponds to step 401 and step 402.
  • DAPS dual active protocol stack
  • the data transmission and reception with the first network device is stopped, And/or, during the cell handover, the continuous LBT failure detection and recovery of the second cell by the terminal device is suspended.
  • the second cell belongs to the second network device, the first network device is the source network device, and the second network device is the target network device.
  • the second cell may be a target cell, or another cell covered by the second network device, such as a secondary cell.
  • the cell handover is a dual-activity protocol stack (DAPS) handover.
  • DAPS dual-activity protocol stack
  • a continuous LBT failure indication is received; and data transmission and reception with the first network device is stopped, and/or, during the cell handover, hang Since the terminal device detects and recovers the continuous LBT failure of the target cell, the first network device is the source network device.
  • receiving a continuous LBT failure indication For example, during the cell handover, receiving a continuous LBT failure indication; and stopping data transmission and reception with the first network device.
  • the continuous LBT failure detection and recovery of the target cell by the terminal device is suspended, and the first network device is the source network device.
  • the first network device is the source network device.
  • step 301 and step 302 can be performed, or step 401 and step 402 can be performed; for the primary cell and the secondary cell , Step 302 or step 402 can be performed.
  • the received continuous LBT failure indication comes from the MAC layer of the terminal device.
  • the persistent LBT failure indication comes from at least one of the source MAC entity, the target MAC entity, and the MCG MAC entity of the terminal device.
  • the persistent LBT failure indicates a source MAC entity or a target MAC entity from the terminal device.
  • the continuous LBT failure indicates the MCG MAC entity from the terminal device.
  • stopping data transmission and/or reception with the network device may include at least one of the following:
  • the first network device is a source network device
  • the second network device is a target network device.
  • step 301 during the cell handover, a continuous LBT failure indication from the MCG MAC entity of the terminal device is received; and the data transmission and communication with the MCG network device are stopped. /Or receive.
  • step 401 during the cell handover, when receiving a continuous LBT failure indication from the MCG MAC entity of the terminal device, stop data transmission and/or reception with the MCG network device.
  • FIG. 5 is a schematic diagram of stopping data transmission and/or reception with a network device in Embodiment 1 of the present application.
  • the MAC entity performs continuous LBT failure detection. If the uplink BWP (UL BWP) activated on the primary cell (PCell) triggers the continuous LBT failure, it will switch to another BWP and initiate random access. All uplink BWPs (UL BWPs) configured with physical random access channel occasions (PRACH occasions) on the same carrier in the primary cell have triggered continuous LBT failure, and the MAC entity will indicate the continuous LBT failure to the RRC layer.
  • the RRC layer performs radio link failure (RLF) detection. When the RRC layer receives a continuous LBT failure indication from the MAC entity, it stops data transmission and/or reception (TX/RX) with the network device.
  • RLF radio link failure
  • step 301 during the cell handover, a continuous LBT failure indication from the source MAC entity of the terminal device is received; and the communication with the first network device is stopped. Data transmission and/or reception.
  • step 401 during the cell handover, when a continuous LBT failure indication from the source MAC entity of the terminal device is received, the data transmission and/or reception with the first network device is stopped.
  • step 301 during the cell handover, a continuous LBT failure indication from the target MAC entity of the terminal device is received; and the data transmission with the second network device is stopped and/or Receive, or stop sending and/or receiving data with the first network device and the second network device.
  • step 401 during the cell handover, when receiving a continuous LBT failure indication from the target MAC entity of the terminal device, stop data transmission with the second network device other than random access related data Or stop sending and/or receiving data with the first network device and the second network device's data sending and/or receiving other than data transmitted related to random access.
  • the source MAC entity and the target MAC entity respectively perform continuous LBT failure detection and respectively indicate the continuous LBT failure to the RRC layer, and the RRC layer stops the division of the first network device and/or the second network device. Random access related to data transmission and/or reception other than the transmitted data.
  • the source MAC entity and the target MAC entity perform continuous LBT failure detection and respectively indicate the continuous LBT failure to the RRC layer.
  • the RRC The layer stops sending and/or receiving data with the first network device, and does nothing with the second network device, including not performing connection re-establishment.
  • FIG. 6 is another schematic diagram of stopping data transmission and/or reception with a network device in Embodiment 1 of the present application.
  • the source MAC entity and the target MAC entity respectively perform continuous LBT failure detection and respectively indicate the continuous LBT failure of the RRC layer. If the uplink BWP (UL BWP) activated on the primary cell (PCell) triggers the continuous LBT failure, then Switch to another BWP and initiate random access.
  • UL BWP uplink BWP
  • PCell primary cell
  • the source MAC entity and/or the target MAC entity will indicate the continuous LBT failure to the RRC layer, and the RRC layer will perform radio link failure (RLF) detection.
  • RLF radio link failure
  • the RRC layer receives the continuous LBT failure indication from the source MAC entity, it will stop communicating with Data transmission and/or reception (TX/RX) of the first network device.
  • TX/RX Data transmission and/or reception
  • the RRC layer receives a continuous LBT failure indication from the target MAC entity, it stops data other than the data transmitted by the second network device except for random access related data. Send and/or receive (TX/RX).
  • FIG. 7 is another schematic diagram of stopping data transmission and/or reception with a network device in Embodiment 1 of the present application.
  • the source MAC entity and the target MAC entity respectively perform continuous LBT failure detection and indicate the continuous LBT failure of the RRC layer respectively. If the uplink BWP (UL BWP) activated on the primary cell (PCell) triggers the continuous LBT failure, then Switch to another BWP and initiate random access.
  • UL BWP uplink BWP
  • PCell primary cell
  • uplink BWPs uplink BWPs
  • PRACH occasions physical random access channel opportunities
  • the source MAC entity and/or the target MAC entity will indicate the persistent LBT failure to the RRC layer, and the RRC layer will perform radio link failure (RLF) detection.
  • RLF radio link failure
  • the method may further include at least one of the following steps: the terminal device remains in the RRC connection state; the terminal device releases the connection with the first network device; the terminal device maintains the RRC of the first network device Configuration; and the terminal device considers that the wireless link with the first network device has failed, wherein the first network device is the source network device.
  • the suspension of continuous LBT failure detection and recovery includes: during the cell handover, the suspension of the terminal device's continuous LBT failure detection of the first cell and/or the second cell With recovery, the first cell belongs to the first network device, the second cell belongs to the second network device, the first network device is the source network device, and the second network device is the target network device.
  • the first cell is a serving cell or a primary cell or a primary secondary cell or a secondary cell
  • the second cell is a serving cell or a primary cell or a primary secondary cell or a secondary cell.
  • the first cell is a serving cell
  • the second cell is a serving cell
  • the first cell may be a primary cell or a primary secondary cell or a secondary cell
  • the second cell may be a primary cell or a primary secondary cell or a secondary cell.
  • the suspension of continuous LBT failure detection and recovery includes at least one of the following:
  • the physical layer stops indicating LBT failure to the MAC layer; for example, when receiving an indication of continuous LBT failure detection and recovery from RRC, the physical layer stops indicating LBT failure to the MAC layer; that is, when no suspension is received In the case of continuous LBT failure detection and recovery indication and LBT failure, the physical layer indicates the LBT failure to the MAC layer;
  • the MAC layer does not trigger continuous LBT failure; for example, when receiving an indication of pending continuous LBT failure detection and recovery from RRC, the MAC layer does not trigger continuous LBT failure; that is, for services configured with LBT failure recovery configuration parameters
  • the LBT counter such as LBT_COUNTER
  • the maximum value of LBT failure such as LBT_COUNTER ⁇ lbt-FailureInstanceMaxCount
  • the MAC layer does not indicate continuous LBT failure to the upper layer (for example, the RRC layer); for example, when receiving an indication of pending continuous LBT failure detection and recovery from RRC, the MAC layer does not indicate continuous LBT failure to the upper layer; that is, when When the serving cell that triggered the continuous LBT failure is a special cell, and the physical random access channel opportunity (PRACH occasion) is configured on the same carrier in the serving cell without receiving the indication of suspension of the continuous LBT failure detection and recovery In the case that all upstream BWPs have triggered continuous LBT failure, the MAC entity indicates to the upper layer that continuous LBT failure;
  • a continuous LBT failure indication is received and the timer for cell handover (such as T304) is not running, it is considered that the radio link has failed; or, when the timer (such as T304) is running, a continuous LBT failure indication is received and the wireless link is not considered Failed or ignored the continuous LBT failure indication; and
  • connection re-establishment is not initiated.
  • the suspension of continuous LBT failure detection and recovery may also include: the RRC layer instructs the lower layer to suspend the continuous LBT failure detection and recovery.
  • the RRC layer instructs the lower layer to suspend continuous LBT failure detection and recovery.
  • the lower layer is the physical layer and/or the MAC layer.
  • the RRC may instruct the physical layer to suspend continuous LBT failure detection and recovery. For example, when the physical layer receives an indication of suspension and continuous LBT failure detection and recovery from the RRC, the physical layer stops indicating LBT failure to the MAC layer.
  • the RRC may instruct the MAC layer to suspend continuous LBT failure detection and recovery.
  • the MAC layer receives an indication of suspended continuous LBT failure detection and recovery from RRC, the MAC layer does not trigger continuous LBT failure, and/or, The MAC layer does not indicate the continuous LBT failure to the RRC layer.
  • the RRC can instruct the physical layer and the MAC layer to suspend continuous LBT failure detection and recovery. For example, when the physical layer receives an indication from the RRC to suspend continuous LBT failure detection and recovery, the physical layer stops indicating LBT failure to the MAC layer And, when the MAC layer receives the indication from the RRC to suspend the continuous LBT failure detection and recovery, the MAC layer does not trigger the continuous LBT failure, and/or the MAC layer does not indicate the continuous LBT failure to the RRC layer.
  • the method when the method includes step 302, as shown in FIG. 3, the method may further include:
  • Step 303 The cell handover is completed, and the continuous LBT failure detection and recovery mechanism is restored.
  • the continuous LBT failure detection and recovery mechanism is restored.
  • the continuous LBT failure detection and recovery mechanism is restored.
  • the method may further include:
  • Step 403 When the cell handover is completed, resume the continuous LBT failure detection and recovery mechanism.
  • the completion of the cell handover may refer to the completion of the handover or the synchronization of the terminal device to the target cell.
  • the terminal device synchronizes to the target cell and completes the RRC handover process by sending an RRCReconfigurationComplete message to the target network device, that is, the execution of step 208 in FIG. 2 is completed.
  • the restoration of the continuous LBT failure detection and recovery mechanism may refer to the restoration of the suspended continuous LBT failure detection and recovery mechanism, for example, the restoration of the suspended continuous LBT failure detection and recovery through step 302 and/or step 402 mechanism.
  • the recovery continuous LBT failure detection and recovery mechanism includes at least one of the following:
  • the physical layer When receiving an indication to resume continuous LBT failure detection and recovery and LBT fails, the physical layer indicates the LBT failure to the MAC layer;
  • the MAC entity when receiving an indication to resume continuous LBT failure detection and recovery and receiving an LBT failure indication from the lower layer, and the LBT counter (such as LBT_COUNTER) is greater than or equal to the maximum value of LBT failure (such as LBT_COUNTER) ⁇ lbt-FailureInstanceMaxCount), the MAC entity triggers the continuous LBT failure on the BWP of the serving cell; and
  • the serving cell that triggered the continuous LBT failure is a special cell
  • the MAC entity when receiving the instruction to resume the detection and recovery of the continuous LBT failure, and all the physical random access channel (PRACH) opportunities are configured on the same carrier in the serving cell
  • PRACH physical random access channel
  • step 303 and/or step 403 it may further include: when the RRC handover is completed or when the terminal device synchronizes to the second cell, the RRC layer instructs the lower layer to resume continuous LBT failure detection and recovery, and the second cell is the target cell.
  • the method may further include:
  • Step 304 Receive an RRC reconfiguration message from the first network device, where the RRC reconfiguration message includes configuration information related to LBT failure detection and recovery, and the first network device is the source network device.
  • the method may further include:
  • Step 404 Receive an RRC reconfiguration message from a first network device, where the RRC reconfiguration message includes configuration information related to LBT failure detection and recovery, and the first network device is the source network device.
  • step 304 and/or step 404 is a part of step 206 in FIG. 2 or step 206 in FIG. 2.
  • the configuration information related to LBT failure detection and recovery may include first configuration information and/or second configuration information.
  • the first configuration information is related to the LBT failure detection and recovery of the first cell.
  • the second configuration information is related to LBT failure detection and recovery of the second cell, the first cell is a cell belonging to the source network device, and the second cell is a cell belonging to the target network device.
  • the first cell may be a serving cell, a primary cell, a primary-secondary cell, or a secondary cell belonging to the source network device
  • the second cell may be a serving cell, a primary cell, a primary-secondary cell, or a secondary cell belonging to the target network device.
  • Community may be a serving cell, a primary cell, a primary-secondary cell, or a secondary cell belonging to the target network device.
  • the source MAC entity of the terminal device may perform continuous LBT failure detection and recovery on the first cell according to the configuration information related to the LBT failure detection and recovery of the first cell; and/or, the terminal The target MAC entity of the device can perform continuous LBT failure detection and recovery on the second cell according to the configuration information related to the LBT failure detection and recovery of the second cell.
  • the terminal device when receiving the continuous LBT failure indication, the terminal device stops sending and/or receiving data with the network device, and/or, during the cell handover, the terminal device suspends the continuous LBT failure Detection and recovery. In this way, during the cell handover, the terminal device will not initiate a connection re-establishment process due to continuous LBT failure, thereby avoiding the resulting user service interruption and user experience degradation.
  • the embodiment of the application provides a method for detecting and recovering persistent LBT failure in cell handover.
  • the method is applied to network equipment and corresponds to the method for detecting and recovering persistent LBT failure in cell handover applied to terminal equipment described in Embodiment 1. And the recovery method, the same content will not be repeated.
  • FIG. 8 is a schematic diagram of a method for detecting and recovering a continuous LBT failure in a cell handover in Embodiment 2 of the present application. As shown in Figure 8, the method includes:
  • Step 801 Send an RRC reconfiguration message to a terminal device, where the RRC reconfiguration message includes configuration information related to LBT failure detection and recovery.
  • step 801 is a part of step 206 in FIG. 2 or step 206 in FIG. 2.
  • the RRC reconfiguration information further includes information required to access the second cell, which is the target cell.
  • the network device is the source network device.
  • the configuration information related to LBT failure detection and recovery includes first configuration information and/or second configuration information.
  • the first configuration information is related to the LBT failure detection and recovery of the first cell
  • the second configuration information is The configuration information is related to the LBT failure detection and recovery of the second cell
  • the first cell is a cell belonging to the source network device
  • the second cell is a cell belonging to the target network device.
  • the first cell may be a serving cell, a primary cell, a primary-secondary cell, or a secondary cell belonging to the source network device
  • the second cell may be a serving cell, a primary cell, a primary-secondary cell, or a secondary cell belonging to the target network device.
  • Community may be a serving cell, a primary cell, a primary-secondary cell, or a secondary cell belonging to the target network device.
  • the configuration information related to LBT failure detection and recovery of the first cell is used by the source MAC entity of the terminal device to perform continuous LBT failure detection and recovery on the first cell, and/or the second cell
  • the configuration information related to the LBT failure detection and recovery of the cell is used for the target MAC entity of the terminal device to perform continuous LBT failure detection and recovery on the second cell.
  • the method may further include:
  • Step 802 Receive and send a handover request confirmation (HANDOVER REQUEST ACKNOWLEDGE) message from the second network device.
  • the second network device is the target network device.
  • the handover request confirmation message may include the information required to access the target cell and the configuration information related to LBT failure detection and recovery.
  • the configuration information related to LBT failure detection and recovery is the terminal's response to the target network.
  • step 802 is a part of step 205 in FIG. 2 or step 205 in FIG. 2.
  • the network device sends an RRC reconfiguration message including configuration information related to LBT failure detection and recovery to the terminal device, so that the terminal device can perform continuous LBT failure detection according to the configuration information related to LBT failure detection and recovery.
  • the embodiment of the present application provides a method for detecting and recovering from persistent LBT failure in cell handover, which is applied to network equipment and terminal equipment, and corresponds to the persistent LBT in cell handover applied to terminal equipment described in Embodiment 1.
  • the LBT failure detection and recovery method and the continuous LBT failure detection and recovery method applied to the cell handover of the network equipment described in Embodiment 2 are not repeated for the same content.
  • FIG. 9 is a schematic diagram of a method for detecting and recovering a continuous LBT failure in a cell handover in Embodiment 3 of the present application. As shown in Figure 9, the method includes:
  • Step 901 Perform RAN handover start. Specifically, the first network device sends an RRC reconfiguration message to the terminal device to trigger Uu handover.
  • the RRC reconfiguration message includes configuration information related to LBT failure detection and recovery; in order to synchronize to the target cell, the terminal The device can initiate a random access procedure to the target cell in the second network device;
  • Step 902 The terminal device receives a continuous LBT failure indication
  • Step 903 The terminal device stops sending and/or receiving data with the first network device and/or the second network device;
  • Step 904 the terminal device is suspended and continues LBT failure detection and recovery
  • Step 905 Perform RAN handover completion. Specifically, the terminal device synchronizes to the target cell and completes the RRC handover process by sending an RRC reconfiguration complete message (RRCReconfigurationComplete message) to the second network device of the target cell.
  • RRC reconfiguration Complete message RRCReconfigurationComplete message
  • the method may include step 903 and/or step 904.
  • the method may further include:
  • Step 906 The terminal device restores the continuous LBT failure detection and recovery mechanism.
  • the first network device is the source network device
  • the second network device is the target network device
  • the terminal device when receiving the continuous LBT failure indication, the terminal device stops sending and/or receiving data with the network device, and/or, during the cell handover, the terminal device suspends the continuous LBT failure Detection and recovery. In this way, during the cell handover, the terminal device will not initiate a connection re-establishment process due to continuous LBT failure, thereby avoiding the resulting user service interruption and user experience degradation.
  • the embodiment of the present application provides an apparatus for detecting and recovering from continuous LBT failure in cell handover, and the apparatus is applied to terminal equipment. Since the principle of the device to solve the problem is similar to the method of embodiment 1, its specific implementation can refer to the implementation of the method of embodiment 1, and the same content or related parts will not be repeated.
  • FIG. 10 is a schematic diagram of an apparatus for detecting and recovering a continuous LBT failure in a cell handover according to Embodiment 4 of the present application. As shown in FIG. 10, the apparatus 1000 includes:
  • the first processing unit 1001 is configured to receive a continuous LBT failure indication during the cell handover; and, stop data transmission and/or reception with the network device, and/or,
  • the second processing unit 1002 is used for detecting and recovering the suspension and continuous LBT failure during the cell handover.
  • the first processing unit 1001 may also be: during the cell handover, when receiving a continuous LBT failure indication, stop sending and/or receiving data with the network device
  • the cell handover includes: dual active protocol stack (DAPS) handover, or dual active protocol stack (DAPS) handover and non-DAPS handover, or, non-DAPS handover.
  • DAPS dual active protocol stack
  • DAPS dual active protocol stack
  • the apparatus 1000 may further include:
  • the recovery unit 1004 is used to recover the continuous LBT failure detection and recovery mechanism,
  • the recovery unit 1004 recovers the continuous LBT failure detection and recovery mechanism.
  • the recovery unit 1004 restores the continuous LBT failure detection and recovery mechanism.
  • the apparatus 1000 may further include:
  • the first receiving unit 1005 is configured to receive an RRC reconfiguration message from a first network device, where the RRC reconfiguration message includes configuration information related to LBT failure detection and recovery, and the first network device is a source network device.
  • the device 1000 may further include at least one of the following units (not shown):
  • a holding unit which is used for the terminal device to remain in the RRC connection state
  • a release unit which is used for the terminal device to release the connection with the first network device
  • the think unit which is used by the terminal device to think that the wireless link with the first network device has failed
  • the first network device is the source network device.
  • the device 1000 further includes at least one of the following units (not shown):
  • the first indication unit which is used to indicate the LBT failure to the MAC layer when the LBT fails and the LBT fails to be detected and resumed without receiving the indication of the suspension of the continuous LBT failure;
  • the first triggering unit which is used for the serving cell configured with the LBT failure recovery configuration parameter, when the LBT failure detection and recovery indication is not received from the suspension and the LBT failure indication is received from the lower layer and the LBT counter is greater than or equal to
  • the MAC entity triggers the continuous LBT failure on the BWP of the serving cell
  • the second indication unit is used for when the serving cell that triggered the continuous LBT failure is a special cell, when the continuous LBT failure detection and recovery instruction is not received and the physical randomness is configured on the same carrier in the serving cell
  • the MAC entity indicates the continuous LBT failure to the upper layer.
  • the terminal device when receiving the continuous LBT failure indication, the terminal device stops sending and/or receiving data with the network device, and/or, during the cell handover, the terminal device suspends the continuous LBT failure Detection and recovery. In this way, during the cell handover, the terminal device will not initiate a connection re-establishment process due to continuous LBT failure, thereby avoiding the resulting user service interruption and user experience degradation.
  • the embodiment of the present application provides an apparatus for detecting and recovering from a continuous LBT failure in a cell handover, and the apparatus is applied to a network device. Since the principle of the device to solve the problem is similar to the method of embodiment 2, its specific implementation can refer to the implementation of the method described in embodiment 2, and the same content or related parts will not be repeated.
  • FIG. 11 is a schematic diagram of an apparatus for detecting and recovering a continuous LBT failure in a cell handover according to Embodiment 5 of the present application. As shown in FIG. 11, the apparatus 1100 includes:
  • the first sending unit 1101 is configured to send an RRC reconfiguration message to the terminal device, where the RRC reconfiguration message includes configuration information related to LBT failure detection and recovery.
  • the RRC reconfiguration information may also include information required to access the second cell, which is the target cell.
  • the network device is the source network device.
  • the configuration information related to LBT failure detection and recovery includes first configuration information and/or second configuration information.
  • the first configuration information is related to the LBT failure detection and recovery of the first cell
  • the second configuration information is The configuration information is related to the LBT failure detection and recovery of the second cell
  • the first cell is a cell belonging to the source network device
  • the second cell is a cell belonging to the target network device.
  • the first cell may be a serving cell, a primary cell, a primary-secondary cell, or a secondary cell belonging to the source network device
  • the second cell may be a serving cell, a primary cell, a primary-secondary cell, or a secondary cell belonging to the target network device.
  • Community may be a serving cell, a primary cell, a primary-secondary cell, or a secondary cell belonging to the target network device.
  • the configuration information related to LBT failure detection and recovery of the first cell is used by the source MAC entity of the terminal device to perform continuous LBT failure detection and recovery on the first cell, and/or the second cell
  • the configuration information related to the LBT failure detection and recovery of the cell is used for the target MAC entity of the terminal device to perform continuous LBT failure detection and recovery on the second cell.
  • the device 1100 further includes:
  • the second receiving unit 1102 is configured to receive a handover request confirmation message sent from a second network device, which is a target network device.
  • the handover request confirmation message may include information required to access the target cell and configuration information related to LBT failure detection and recovery, and the configuration information related to LBT failure detection and recovery is the pair of terminal equipment Configuration information for the cell in the target network device to perform continuous LBT failure detection and recovery.
  • the network device sends an RRC reconfiguration message including configuration information related to LBT failure detection and recovery to the terminal device, so that the terminal device can perform continuous LBT failure detection according to the configuration information related to LBT failure detection and recovery.
  • An embodiment of the present application provides a terminal device, which includes the device for detecting and recovering from a continuous LBT failure in a cell handover as described in the fourth embodiment.
  • FIG. 12 is a schematic block diagram of the system configuration of a terminal device according to Embodiment 6 of the present invention.
  • the terminal device 1200 may include a processor 1210 and a memory 1220; the memory 1220 is coupled to the processor 1210. It is worth noting that this figure is exemplary; other types of structures can also be used to supplement or replace this structure to implement telecommunication functions or other functions.
  • the function of the apparatus for detecting and recovering from a continuous LBT failure in a cell handover may be integrated into the processor 1210.
  • the processor 1210 may be configured to: during the cell handover, receive a continuous LBT failure indication; and, stop data transmission and/or reception with the network device, and/or, during the cell handover, suspend continuous LBT failure detection and recover.
  • the cell handover includes: dual active protocol stack (DAPS) handover, or dual active protocol stack (DAPS) handover and non-DAPS handover, or, non-DAPS handover.
  • DAPS dual active protocol stack
  • DAPS dual active protocol stack
  • the continuous LBT failure detection and recovery is suspended.
  • the cell handover is a dual-activity protocol stack (DAPS) handover.
  • DAPS dual-activity protocol stack
  • a continuous LBT failure indication is received; and data transmission and reception with the first network device is stopped, and/or, during the cell handover, hang
  • the first network device is the source network device.
  • the received persistent LBT failure indication comes from the MAC layer of the terminal device.
  • the received persistent LBT failure indication comes from the MAC layer of the terminal device, including: the received persistent LBT failure indication comes from at least one of the source MAC entity, the target MAC entity, and the MCG MAC entity of the terminal device.
  • stopping the data transmission and/or reception with the network device includes at least one of the following: stopping the data transmission and/or reception with the first network device; stopping the data transmission and/or reception related to the second network device except for random access Data sending and/or receiving other than that; and stopping data sending and/or receiving with the MCG network device, the first network device is the source network device, and the second network device is the target network device.
  • the processor 1210 may be further configured to perform at least one of the following steps: the terminal device remains in the RRC connected state; the terminal device releases the connection with the first network device; the terminal device maintains the RRC configuration of the first network device ; And the terminal device considers that the wireless link with the first network device has failed, and the first network device is the source network device.
  • suspending the detection and recovery of continuous LBT failure during the cell handover includes: suspending the detection and recovery of the continuous LBT failure of the first cell and/or the second cell by the terminal device during the cell handover.
  • the first cell belongs to A first network device
  • the second cell belongs to a second network device
  • the first network device is a source network device
  • the second network device is a target network device.
  • the first cell is a serving cell or a primary cell or a primary secondary cell or a secondary cell
  • the second cell is a serving cell or a primary cell or a primary secondary cell or a secondary cell.
  • the suspension of continuous LBT failure detection and recovery includes at least one of the following: the physical layer stops indicating the LBT failure to the MAC layer; the MAC layer does not trigger the continuous LBT failure; the MAC layer does not indicate the continuous LBT failure to the upper layer; the continuous LBT is received If the failure indication and the timer used for cell handover are not running, the radio link is considered to have failed; or if the timer is running and a continuous LBT failure indication is received, the radio link is not considered to have failed or the continuous LBT failure indication is ignored; and The radio link fails, and the timer for cell handover is not running, and connection re-establishment is initiated; or, if the timer is running and the radio link fails, the connection re-establishment is not initiated.
  • the processor 1210 may be further configured to perform at least one of the following steps: in the case where the LBT fails to be detected and resumed without receiving an indication of suspending continuous LBT failure detection and recovery, the physical layer indicates the LBT failure to the MAC layer; for configuration If the serving cell that has configured the LBT failure recovery configuration parameters has not received an indication from the suspension of continuous LBT failure detection and recovery and has received an LBT failure indication from the lower layer and the LBT counter is greater than or equal to the maximum value of LBT failure, the MAC entity triggers this Continuous LBT failure on the BWP of the serving cell; and when the serving cell that triggered the continuous LBT failure is a special cell, it is configured on the same carrier in the serving cell without receiving an indication of suspension of continuous LBT failure detection and recovery In the case that all uplink BWPs at the physical random access channel (PRACH) timing trigger the continuous LBT failure, the MAC entity indicates to the upper layer the continuous LBT failure.
  • PRACH physical random access channel
  • the suspension of continuous LBT failure detection and recovery also includes:
  • the RRC layer instructs the lower layer to suspend continuous LBT failure detection and recovery.
  • the RRC layer instructs the lower layer to suspend continuous LBT failure detection and recovery.
  • the lower layer is the physical layer and/or the MAC layer.
  • the processor 1210 may also be configured to restore the continuous LBT failure detection and recovery mechanism when the cell handover is completed.
  • the recovery continuous LBT failure detection and recovery mechanism includes at least one of the following: when receiving an indication of recovering continuous LBT failure detection and recovery and the LBT fails, the physical layer indicates the LBT failure to the MAC layer; for LBT failure recovery configured Serving cell with configured parameters, when receiving an indication to resume continuous LBT failure detection and recovery and receiving an LBT failure indication from a lower layer and the LBT counter is greater than or equal to the maximum value of LBT failure, the MAC entity triggers the continuation on the BWP of the serving cell LBT failure; and when the serving cell that triggered the continuous LBT failure is a special cell, when receiving the instruction to resume the detection and recovery of the continuous LBT failure, and the physical random access channel (PRACH) is configured on the same carrier in the serving cell ) When all the uplink BWPs of the timing trigger the continuous LBT failure, the MAC entity indicates the continuous LBT failure to the upper layer.
  • PRACH physical random access channel
  • the recovery continuous LBT failure detection and recovery mechanism further includes: when the RRC handover is completed or when the terminal device synchronizes to the second cell, the RRC layer instructs the lower layer to recover the continuous LBT failure detection and recovery, and the second cell is the target cell .
  • the processor 1210 may be further configured to receive an RRC reconfiguration message from a first network device, where the RRC reconfiguration message includes configuration information related to LBT failure detection and recovery, and the first network device is the source network device.
  • the configuration information related to LBT failure detection and recovery includes first configuration information and/or second configuration information, the first configuration information is related to the LBT failure detection and recovery of the first cell, and the second configuration information is related to the second configuration information.
  • LBT failure detection of a cell is related to recovery.
  • the first cell is a cell belonging to the source network device, and the second cell is a cell belonging to the target network device.
  • the first cell may be a serving cell, a primary cell, a primary-secondary cell, or a secondary cell belonging to the source network device
  • the second cell may be a serving cell, a primary cell, a primary-secondary cell, or a secondary cell belonging to the target network device.
  • Community may be a serving cell, a primary cell, a primary-secondary cell, or a secondary cell belonging to the target network device.
  • the source MAC entity of the terminal device performs continuous LBT failure detection and recovery on the first cell according to the configuration information related to the LBT failure detection and recovery of the first cell; and/or, the target MAC entity of the terminal device according to The LBT failure detection and recovery related configuration information of the second cell is used to perform continuous LBT failure detection and recovery on the second cell.
  • the device for persistent LBT failure detection and recovery in cell handover can be configured separately from the processor 1210.
  • the device for persistent LBT failure detection and recovery in cell handover can be configured to be connected to the processor 1210.
  • the chip realizes the function of a device for detecting and recovering from continuous LBT failure in cell handover under the control of the processor 1210.
  • the terminal device 1200 may further include: a communication module 1230, an input unit 1240, a display 1250, and a power supply 1260. It should be noted that the terminal device 1200 does not necessarily include all the components shown in FIG. 12; in addition, the terminal device 1200 may also include components not shown in FIG. 12, and related technologies may be referred to.
  • the processor 1210 is sometimes called a controller or an operating control, and may include a microprocessor or other processor device and/or logic device.
  • the processor 1210 receives input and controls the operation of the various components of the terminal device 1200. operate.
  • the memory 1220 may be, for example, one or more of a cache, a flash memory, a hard drive, a removable medium, a volatile memory, a non-volatile memory, or other suitable devices.
  • Various data can be stored, in addition to programs that execute related information.
  • the processor 1210 can execute the program stored in the memory 1220 to implement information storage or processing.
  • the functions of other components are similar to the existing ones, so I won't repeat them here.
  • Each component of the terminal device 1200 can be implemented by dedicated hardware, firmware, software, or a combination thereof, without departing from the scope of the present invention.
  • the terminal device when receiving the continuous LBT failure indication, the terminal device stops sending and/or receiving data with the network device, and/or, during the cell handover, the terminal device suspends the continuous LBT failure Detection and recovery. In this way, during the cell handover, the terminal device will not initiate a connection re-establishment process due to continuous LBT failure, thereby avoiding the resulting user service interruption and user experience degradation.
  • the embodiment of the present invention provides a network device, which includes the device for detecting and recovering from a continuous LBT failure in a cell handover as described in the fifth embodiment.
  • FIG. 13 is a schematic block diagram of the system configuration of a network device according to Embodiment 7 of the present invention.
  • the network device 1300 may include: a processor (processor) 1310 and a memory 1320; the memory 1320 is coupled to the processor 1310.
  • the memory 1320 can store various data; in addition, it also stores an information processing program 1330, and executes the program 1330 under the control of the processor 1310 to receive various information sent by the terminal device and send various information to the terminal device .
  • the function of the apparatus for detecting and recovering from continuous LBT failure in cell handover may be integrated into the processor 1310.
  • the processor 1310 may be configured to send an RRC reconfiguration message to the terminal device, where the RRC reconfiguration message includes configuration information related to LBT failure detection and recovery.
  • the RRC reconfiguration information also includes information required to access the second cell, which is the target cell.
  • the network device is the source network device.
  • the configuration information related to LBT failure detection and recovery includes first configuration information and/or second configuration information, the first configuration information is related to the LBT failure detection and recovery of the first cell, and the second configuration information is related to the second configuration information.
  • LBT failure detection of a cell is related to recovery.
  • the first cell is a cell belonging to the source network device, and the second cell is a cell belonging to the target network device.
  • the first cell may be a serving cell, a primary cell, a primary-secondary cell, or a secondary cell belonging to the source network device
  • the second cell may be a serving cell, a primary cell, a primary-secondary cell, or a secondary cell belonging to the target network device.
  • Community may be a serving cell, a primary cell, a primary-secondary cell, or a secondary cell belonging to the target network device.
  • the configuration information related to the LBT failure detection and recovery of the first cell is used by the source MAC entity of the terminal device to perform continuous LBT failure detection and recovery on the first cell, and/or the LBT failure detection of the second cell
  • the configuration information related to recovery is used for the target MAC entity of the terminal device to detect and recover the continuous LBT failure on the second cell.
  • the device for persistent LBT failure detection and recovery in cell handover can be configured separately from the processor 1310.
  • the device for persistent LBT failure detection and recovery in cell handover can be configured to be connected to the processor 1310.
  • the chip realizes the function of a device for detecting and recovering from continuous LBT failure in cell handover under the control of the processor 1310.
  • the network device 1300 may further include: a transceiver 1340, an antenna 1350, etc.; wherein the functions of the above-mentioned components are similar to those of the prior art, and will not be repeated here. It is worth noting that the network device 1300 does not necessarily include all the components shown in FIG. 13; in addition, the network device 1300 may also include components not shown in FIG. 13, and the prior art can be referred to.
  • the network device sends an RRC reconfiguration message including configuration information related to LBT failure detection and recovery to the terminal device, so that the terminal device can perform continuous LBT failure detection according to the configuration information related to LBT failure detection and recovery.
  • An embodiment of the present application provides a communication system, including the terminal device according to Embodiment 7 and/or the network device according to Embodiment 8.
  • the structure of the communication system can refer to FIG. 1.
  • the communication system 100 includes a first network device 101, a second network device 102, and a terminal device 103.
  • the terminal device 103 is the same as the terminal device described in Embodiment 7.
  • the first network device 101 is the same as the network device recorded in Embodiment 7, and the repeated content will not be repeated.
  • the above devices and methods of the present invention can be implemented by hardware, or can be implemented by hardware combined with software.
  • the present invention relates to such a computer-readable program, when the program is executed by a logic component, the logic component can realize the above-mentioned device or constituent component, or the logic component can realize the above-mentioned various methods Or steps.
  • Logic components such as field programmable logic components, microprocessors, processors used in computers, etc.
  • the present invention also relates to storage media for storing the above programs, such as hard disks, magnetic disks, optical disks, DVDs, flash memory, and the like.
  • the method/device described in conjunction with the embodiments of the present application may be directly embodied as hardware, a software module executed by a processor, or a combination of the two.
  • one or more of the functional block diagrams and/or one or more combinations of the functional block diagrams shown in FIG. 11 may correspond to each software module of the computer program flow, or may correspond to each hardware module.
  • These software modules can respectively correspond to the steps shown in FIG. 3 or FIG. 4.
  • These hardware modules can be implemented by solidifying these software modules by using a field programmable gate array (FPGA), for example.
  • FPGA field programmable gate array
  • the software module can be located in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, removable disk, CD-ROM or any other form of storage medium known in the art.
  • a storage medium may be coupled to the processor, so that the processor can read information from the storage medium and write information to the storage medium; or the storage medium may be a component of the processor.
  • the processor and the storage medium may be located in the ASIC.
  • the software module can be stored in the memory of the mobile terminal, or can be stored in a memory card that can be inserted into the mobile terminal.
  • the software module can be stored in the MEGA-SIM card or a large-capacity flash memory device.
  • One or more of the functional blocks and/or one or more combinations of the functional blocks described in FIG. 11 can be implemented as a general-purpose processor or a digital signal processor ( DSP), application specific integrated circuit (ASIC), field programmable gate array (FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components, or any appropriate combination thereof.
  • DSP digital signal processor
  • ASIC application specific integrated circuit
  • FPGA field programmable gate array
  • One or more of the functional blocks and/or one or more combinations of the functional blocks described with respect to FIG. 11 can also be implemented as a combination of computing devices, for example, a combination of a DSP and a microprocessor, or multiple microcomputers.
  • An apparatus for detecting and recovering from continuous LBT failure in cell handover the apparatus is applied to terminal equipment, and the apparatus includes:
  • the first processing unit is configured to receive a continuous LBT failure indication during the cell handover; and, stop data transmission and/or reception with the network device, and/or,
  • the second processing unit is used to detect and recover the suspension and continuous LBT failure during the cell handover.
  • DAPS Dual Active Protocol Stack
  • Dual Active Protocol Stack (DAPS) handover and non-DAPS handover or,
  • Non-DAPS handover.
  • the device suspends continuous LBT failure detection and recovery when receiving a continuous LBT failure indication, and/or when stopping data transmission and/or reception with the network device.
  • the cell handover is a dual active protocol stack (DAPS) handover
  • the first processing unit is configured to receive a continuous LBT failure indication during the cell handover; and stop data transmission and reception with the first network device, and/or,
  • the second processing unit is configured to suspend continuous LBT failure detection and recovery of the target cell by the terminal device during the cell handover,
  • the first network device is a source network device.
  • the received persistent LBT failure indication comes from the MAC layer of the terminal device.
  • the received persistent LBT failure indication comes from at least one of the source MAC entity, the target MAC entity, and the MCG MAC entity of the terminal device.
  • the first network device is a source network device
  • the second network device is a target network device.
  • a holding unit which is used to keep the terminal device in an RRC connected state
  • a release unit which is used for the terminal device to release the connection with the first network device
  • a thinking unit which is used by the terminal device to consider that the wireless link with the first network device has failed
  • the first network device is a source network device.
  • the first cell belongs to a first network device
  • the second cell belongs to a second network device
  • the first network device is a source network device
  • the second network device is a target network device.
  • the first cell is a serving cell or a primary cell or a primary and secondary cell or a secondary cell, and/or,
  • the second cell is a serving cell or a primary cell or a primary and secondary cell or a secondary cell.
  • the physical layer stops indicating LBT failure to the MAC layer
  • the MAC layer does not trigger continuous LBT failure
  • the MAC layer does not indicate continuous LBT failure to the upper layer
  • the first indication unit which is used to indicate the LBT failure to the MAC layer when the LBT fails and the LBT fails to be detected and resumed without receiving the indication of the suspension of the continuous LBT failure;
  • the first triggering unit which is used for the serving cell configured with the LBT failure recovery configuration parameter, when the LBT failure detection and recovery indication is not received from the suspension and the LBT failure indication is received from the lower layer and the LBT counter is greater than or equal to
  • the MAC entity triggers the continuous LBT failure on the BWP of the serving cell
  • the second indication unit is used for when the serving cell that triggers the continuous LBT failure is a special cell, when the continuous LBT failure detection and recovery instruction is not received and the physical carrier is configured on the same carrier in the serving cell.
  • the MAC entity indicates the continuous LBT failure to the upper layer.
  • the RRC layer instructs the lower layer to suspend continuous LBT failure detection and recovery.
  • the RRC layer instructs the lower layer to suspend continuous LBT failure detection and recovery.
  • the lower layer is the physical layer and/or the MAC layer.
  • Handover completion unit which is used to complete the cell handover
  • the recovery unit is used to recover the persistent LBT failure detection and recovery mechanism.
  • the physical layer When receiving an indication to resume continuous LBT failure detection and recovery and LBT fails, the physical layer indicates the LBT failure to the MAC layer;
  • the MAC entity when receiving an indication to resume continuous LBT failure detection and recovery and receiving an LBT failure indication from the lower layer and the LBT counter is greater than or equal to the maximum value of LBT failure, the MAC entity triggers the Continuous LBT failure on the BWP of the serving cell;
  • the serving cell that triggered the continuous LBT failure is a special cell
  • the physical random access channel (PRACH) is configured on the same carrier in the serving cell
  • the MAC entity indicates to the upper layer the continuous LBT failure.
  • the RRC layer instructs the lower layer to resume continuous LBT failure detection and recovery, and the second cell is the target cell.
  • the first receiving unit is configured to receive an RRC reconfiguration message from a first network device, where the RRC reconfiguration message includes configuration information related to LBT failure detection and recovery, and the first network device is a source network device.
  • the configuration information related to LBT failure detection and recovery includes first configuration information and/or second configuration information, the first configuration information is related to LBT failure detection and recovery of the first cell, and the second configuration information is related to the first cell.
  • the LBT failure detection of the second cell is related to recovery
  • the first cell is a cell belonging to the source network device
  • the second cell is a cell belonging to the target network device.
  • the source MAC entity of the terminal device performs continuous LBT failure detection and recovery on the first cell according to the first configuration information; and/or,
  • the target MAC entity of the terminal device performs detection and recovery of the continuous LBT failure on the second cell according to the second configuration information.
  • a device for detecting and recovering from continuous LBT failure in cell handover is applied to terminal equipment, and the device includes:
  • the third processing unit is used to stop data transmission and/or reception with the network device when receiving a continuous LBT failure indication during the cell handover, and/or,
  • the fourth processing unit is used to detect and recover the suspension of continuous LBT failure during the cell handover.
  • DAPS Dual Active Protocol Stack
  • Dual Active Protocol Stack (DAPS) handover and non-DAPS handover or,
  • Non-DAPS handover.
  • the device is used to suspend continuous LBT failure detection and recovery when receiving a continuous LBT failure indication and/or when stopping data transmission and/or reception with the network device during the cell handover.
  • the cell handover is a dual active protocol stack (DAPS) handover
  • the first network device is a source network device.
  • the received persistent LBT failure indication comes from the MAC layer of the terminal device.
  • the received persistent LBT failure indication comes from at least one of the source MAC entity, the target MAC entity, and the MCG MAC entity of the terminal device.
  • the first network device is a source network device
  • the second network device is a target network device.
  • a holding unit which is used to keep the terminal device in an RRC connected state
  • a release unit which is used for the terminal device to release the connection with the first network device
  • a thinking unit which is used by the terminal device to consider that the wireless link with the first network device has failed
  • the first network device is a source network device.
  • the first cell belongs to a first network device
  • the second cell belongs to a second network device
  • the first network device is a source network device
  • the second network device is a target network device.
  • the first cell is a serving cell or a primary cell or a primary and secondary cell or a secondary cell, and/or,
  • the second cell is a serving cell or a primary cell or a primary and secondary cell or a secondary cell.
  • the physical layer stops indicating LBT failure to the MAC layer
  • the MAC layer does not trigger continuous LBT failure
  • the MAC layer does not indicate continuous LBT failure to the upper layer
  • the first indication unit which is used to indicate the LBT failure to the MAC layer when the LBT fails and the LBT fails to be detected and resumed without receiving the indication of the suspension of the continuous LBT failure;
  • the first triggering unit which is used for the serving cell configured with the LBT failure recovery configuration parameter, when the LBT failure detection and recovery indication is not received from the suspension and the LBT failure indication is received from the lower layer and the LBT counter is greater than or equal to
  • the MAC entity triggers the continuous LBT failure on the BWP of the serving cell
  • the second indication unit is used for when the serving cell that triggers the continuous LBT failure is a special cell, when the continuous LBT failure detection and recovery instruction is not received and the physical carrier is configured on the same carrier in the serving cell.
  • the MAC entity indicates the continuous LBT failure to the upper layer.
  • the RRC layer instructs the lower layer to suspend continuous LBT failure detection and recovery.
  • the RRC layer instructs the lower layer to suspend continuous LBT failure detection and recovery.
  • the lower layer is the physical layer and/or the MAC layer.
  • Handover completion unit which is used to complete the cell handover
  • the recovery unit is used to recover the persistent LBT failure detection and recovery mechanism.
  • the physical layer When receiving an indication to resume continuous LBT failure detection and recovery and LBT fails, the physical layer indicates the LBT failure to the MAC layer;
  • the MAC entity when receiving an indication to resume continuous LBT failure detection and recovery and receiving an LBT failure indication from the lower layer and the LBT counter is greater than or equal to the maximum value of LBT failure, the MAC entity triggers the Continuous LBT failure on the BWP of the serving cell;
  • the serving cell that triggered the continuous LBT failure is a special cell
  • the physical random access channel (PRACH) is configured on the same carrier in the serving cell
  • the MAC entity indicates to the upper layer the continuous LBT failure.
  • the RRC layer instructs the lower layer to resume continuous LBT failure detection and recovery, and the second cell is the target cell.
  • the first receiving unit is configured to receive an RRC reconfiguration message from a first network device, where the RRC reconfiguration message includes configuration information related to LBT failure detection and recovery, and the first network device is a source network device.
  • the configuration information related to LBT failure detection and recovery includes first configuration information and/or second configuration information, the first configuration information is related to LBT failure detection and recovery of the first cell, and the second configuration information is related to the first cell.
  • the LBT failure detection of the second cell is related to recovery
  • the first cell is a cell belonging to the source network device
  • the second cell is a cell belonging to the target network device.
  • the source MAC entity of the terminal device performs continuous LBT failure detection and recovery on the first cell according to the first configuration information; and/or,
  • the target MAC entity of the terminal device performs detection and recovery of the continuous LBT failure on the second cell according to the second configuration information.
  • a device for detecting and recovering from continuous LBT failure in cell handover is applied to network equipment, and the device includes:
  • the first sending unit is configured to send an RRC reconfiguration message to the terminal device, where the RRC reconfiguration message includes configuration information related to LBT failure detection and recovery.
  • the RRC reconfiguration information also includes information required to access the second cell, and the second cell is the target cell.
  • the network device is the source network device.
  • the configuration information related to LBT failure detection and recovery includes first configuration information and/or second configuration information, the first configuration information is related to LBT failure detection and recovery of the first cell, and the second configuration information is related to the first cell.
  • the LBT failure detection of the second cell is related to recovery
  • the first cell is a cell belonging to the source network device
  • the second cell is a cell belonging to the target network device.
  • the first configuration information is used by the source MAC entity of the terminal device to perform continuous LBT failure detection and recovery on the first cell, and/or,
  • the second configuration information is used by the target MAC entity of the terminal device to perform continuous LBT failure detection and recovery on the second cell.
  • the second receiving unit is configured to receive a handover request confirmation message sent from a second network device, where the second network device is a target network device.
  • the handover request confirmation message includes information required to access the target cell and configuration information related to LBT failure detection and recovery, and the configuration information related to LBT failure detection and recovery is the terminal device's response to the target network device.
  • the configuration information of the cell for continuous LBT failure detection and recovery is the terminal device's response to the target network device.
  • a terminal device comprising the device according to any one of Supplementary Notes 1-42.
  • a network device comprising the device according to any one of Supplements 43-49.
  • a communication system comprising the terminal equipment according to Supplement 50 and/or the network equipment according to Supplement 51.
  • a method for continuous LBT failure detection and recovery in cell handover the method is applied to terminal equipment, and the method includes:
  • a continuous LBT failure indication is received; and, the data transmission and/or reception with the network device is stopped, and/or,
  • DAPS Dual Active Protocol Stack
  • Dual Active Protocol Stack (DAPS) handover and non-DAPS handover or,
  • Non-DAPS handover.
  • the detection and recovery of the continuous LBT failure is suspended.
  • the cell handover is a dual active protocol stack (DAPS) handover
  • the first network device is a source network device.
  • the persistent LBT failure indication comes from the MAC layer of the terminal device.
  • the persistent LBT failure indication comes from at least one of the source MAC entity, the target MAC entity, and the MCG MAC entity of the terminal device.
  • the first network device is a source network device
  • the second network device is a target network device.
  • the terminal device remains in the RRC connected state
  • the terminal device releases the connection with the first network device
  • the terminal device maintains the RRC configuration of the first network device
  • the terminal device considers that the wireless link with the first network device has failed
  • the first network device is a source network device.
  • the first cell belongs to a first network device
  • the second cell belongs to a second network device
  • the first network device is a source network device
  • the second network device is a target network device.
  • the first cell is a serving cell or a primary cell or a primary and secondary cell or a secondary cell, and/or,
  • the second cell is a serving cell or a primary cell or a primary and secondary cell or a secondary cell.
  • suspension of continuous LBT failure detection and recovery includes at least one of the following:
  • the physical layer stops indicating LBT failure to the MAC layer
  • the MAC layer does not trigger continuous LBT failure
  • the MAC layer does not indicate continuous LBT failure to the upper layer
  • the physical layer indicates the LBT failure to the MAC layer
  • the MAC entity does not receive an indication from the suspension of continuous LBT failure detection and recovery and receives an LBT failure indication from the lower layer and the LBT counter is greater than or equal to the maximum value of LBT failure. Trigger the continuous LBT failure on the BWP of the serving cell;
  • the physical random access channel PRACH
  • PRACH physical random access channel
  • the RRC layer instructs the lower layer to suspend continuous LBT failure detection and recovery.
  • the RRC layer instructs the lower layer to suspend continuous LBT failure detection and recovery.
  • the lower layer is the physical layer and/or the MAC layer.
  • the cell handover is completed, and the continuous LBT failure detection and recovery mechanism is restored.
  • recovery-continuous LBT failure detection and recovery mechanism includes at least one of the following:
  • the physical layer When receiving an indication to resume continuous LBT failure detection and recovery and LBT fails, the physical layer indicates the LBT failure to the MAC layer;
  • the MAC entity when receiving an indication to resume continuous LBT failure detection and recovery and receiving an LBT failure indication from the lower layer and the LBT counter is greater than or equal to the maximum value of LBT failure, the MAC entity triggers the Continuous LBT failure on the BWP of the serving cell;
  • the serving cell that triggered the continuous LBT failure is a special cell
  • the physical random access channel (PRACH) is configured on the same carrier in the serving cell
  • the MAC entity indicates to the upper layer the continuous LBT failure.
  • the RRC layer instructs the lower layer to resume continuous LBT failure detection and recovery, and the second cell is the target cell.
  • An RRC reconfiguration message is received from a first network device, where the RRC reconfiguration message includes configuration information related to LBT failure detection and recovery, and the first network device is a source network device.
  • the configuration information related to LBT failure detection and recovery includes first configuration information and/or second configuration information, the first configuration information is related to LBT failure detection and recovery of the first cell, and the second configuration information is related to the first cell.
  • the LBT failure detection of the second cell is related to recovery
  • the first cell is a cell belonging to the source network device
  • the second cell is a cell belonging to the target network device.
  • the source MAC entity of the terminal device performs continuous LBT failure detection and recovery on the first cell according to the first configuration information; and/or,
  • the target MAC entity of the terminal device performs continuous LBT failure detection and recovery on the second cell.
  • a method for continuous LBT failure detection and recovery in cell handover the method is applied to terminal equipment, and the method includes:
  • DAPS Dual Active Protocol Stack
  • Dual Active Protocol Stack (DAPS) handover and non-DAPS handover or,
  • Non-DAPS handover.
  • the detection and recovery of the continuous LBT failure is suspended.
  • the cell handover is a dual active protocol stack (DAPS) handover
  • the first network device is a source network device.
  • the received persistent LBT failure indication comes from the MAC layer of the terminal device.
  • the received persistent LBT failure indication comes from at least one of the source MAC entity, the target MAC entity, and the MCG MAC entity of the terminal device.
  • the first network device is a source network device
  • the second network device is a target network device.
  • the terminal device remains in the RRC connected state
  • the terminal device releases the connection with the first network device
  • the terminal device maintains the RRC configuration of the first network device
  • the terminal device considers that the wireless link with the first network device has failed
  • the first network device is a source network device.
  • the first cell belongs to a first network device
  • the second cell belongs to a second network device
  • the first network device is a source network device
  • the second network device is a target network device.
  • the first cell is a serving cell or a primary cell or a primary and secondary cell or a secondary cell, and/or,
  • the second cell is a serving cell or a primary cell or a primary and secondary cell or a secondary cell.
  • the physical layer stops indicating LBT failure to the MAC layer
  • the MAC layer does not trigger continuous LBT failure
  • the MAC layer does not indicate continuous LBT failure to the upper layer
  • the physical layer indicates the LBT failure to the MAC layer
  • the MAC entity does not receive an indication from the suspension of continuous LBT failure detection and recovery and receives an LBT failure indication from the lower layer and the LBT counter is greater than or equal to the maximum value of LBT failure. Trigger the continuous LBT failure on the BWP of the serving cell;
  • the physical random access channel PRACH
  • PRACH physical random access channel
  • the RRC layer instructs the lower layer to suspend continuous LBT failure detection and recovery.
  • the RRC layer instructs the lower layer to suspend continuous LBT failure detection and recovery.
  • the lower layer is the physical layer and/or the MAC layer.
  • the physical layer When receiving an indication to resume continuous LBT failure detection and recovery and LBT fails, the physical layer indicates the LBT failure to the MAC layer;
  • the MAC entity when receiving an indication to resume continuous LBT failure detection and recovery and receiving an LBT failure indication from the lower layer and the LBT counter is greater than or equal to the maximum value of LBT failure, the MAC entity triggers the Continuous LBT failure on the BWP of the serving cell;
  • the serving cell that triggered the continuous LBT failure is a special cell
  • the physical random access channel (PRACH) is configured on the same carrier in the serving cell
  • the MAC entity indicates to the upper layer the continuous LBT failure.
  • the RRC layer instructs the lower layer to resume continuous LBT failure detection and recovery, and the second cell is the target cell.
  • An RRC reconfiguration message is received from a first network device, where the RRC reconfiguration message includes configuration information related to LBT failure detection and recovery, and the first network device is a source network device.
  • the configuration information related to LBT failure detection and recovery includes first configuration information and/or second configuration information, the first configuration information is related to LBT failure detection and recovery of the first cell, and the second configuration information is related to the first cell.
  • the LBT failure detection of the second cell is related to recovery
  • the first cell is a cell belonging to the source network device
  • the second cell is a cell belonging to the target network device.
  • the source MAC entity of the terminal device performs continuous LBT failure detection and recovery on the first cell according to the first configuration information; and/or,
  • the target MAC entity of the terminal device performs detection and recovery of the continuous LBT failure on the second cell according to the second configuration information.
  • a method for continuous LBT failure detection and recovery in cell handover is applied to a network device, and the method includes:
  • RRC reconfiguration message Send an RRC reconfiguration message to the terminal device, where the RRC reconfiguration message includes configuration information related to LBT failure detection and recovery.
  • the RRC reconfiguration information also includes information required to access the second cell, and the second cell is the target cell.
  • the network device is the source network device.
  • the configuration information related to LBT failure detection and recovery includes first configuration information and/or second configuration information, the first configuration information is related to LBT failure detection and recovery of the first cell, and the second configuration information is related to The LBT failure detection of the second cell is related to recovery,
  • the first cell is a cell belonging to the source network device
  • the second cell is a cell belonging to the target network device.
  • the first configuration information is used by the source MAC entity of the terminal device to perform continuous LBT failure detection and recovery on the first cell, and/or,
  • the second configuration information is used by the target MAC entity of the terminal device to perform continuous LBT failure detection and recovery on the second cell.
  • the handover request confirmation message includes information required to access the target cell and configuration information related to LBT failure detection and recovery, and the configuration information related to LBT failure detection and recovery is the terminal device's response to the target network device.
  • the configuration information of the cell for continuous LBT failure detection and recovery is the terminal device's response to the target network device.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

一种小区切换中的持续LBT失败检测和恢复的方法及装置。所述方法应用于终端设备，所述方法包括：在小区切换期间，收到持续LBT失败指示；并且，停止与网络设备的数据发送和/或接收，和/或，在小区切换期间，挂起持续LBT失败检测与恢复。

Description

小区切换中的持续LBT失败检测和恢复的方法及装置 技术领域
本发明涉及通信领域。
背景技术
为了在共享频谱信道接入(shared spectrum channel access)中提供3GPP服务，引入了以下机制：通话前监听(Listen Before Talk，LBT)以及发现信号测量定时配置(Discovery RS Measurement Timing Configuration，DMTC)。其中，低层执行LBT过程，根据LBT结果，如果信道确定被占用，不进行传输。当低层在传输前执行了LBT过程且该传输未执行，即上行传输由于LBT失败被阻挡时，低层向MAC层指示LBT失败。
应该注意，上面对技术背景的介绍只是为了方便，对本发明的技术方案进行清楚、完整的说明，并方便本领域技术人员的理解而阐述的。不能仅仅因为这些方案在本发明的背景技术部分进行了阐述而认为上述技术方案为本领域技术人员所公知。
发明内容
在共享频谱信道接入中，引入了持续LBT失败检测和恢复机制，持续LBT失败检测和恢复机制是指对可能发生的持续LBT失败进行检测，并采取行动，使终端从检测到的持续LBT失败恢复。持续LBT失败检测和恢复机制也可以称为上行传输的持续LBT失败检测和恢复机制、LBT失败检测和恢复机制、上行LBT失败检测和恢复机制或者持续上行LBT失败检测和恢复机制。持续LBT失败检测和恢复机制可以是LBT失败检测过程(又称为上行传输的持续LBT失败检测过程)，或者LBT失败恢复过程(又称为上行传输的持续LBT失败恢复过程)，或者既包括LBT失败检测过程(又称为上行传输的持续LBT失败检测过程)，又包括LBT失败恢复过程(又称为上行传输的持续LBT失败恢复过程)。
无线资源控制(Radio Resource Control，RRC)层可以为介质访问控制(Medio Access Control，MAC)层的MAC实体配置持续LBT失败的恢复过程。持续LBT失败的检测是在每个上行BWP(Bandwidth part)上进行的。MAC实体通过计算收到 的来自低层(例如物理层)的所有上行传输的LBT失败指示的数量进行检测。为此引入一个LBT计数器(例如LBT_COUNTER)和一个定时器，当上行LBT失败发生时，启动或重启定时器，每当MAC层收到来自低层的上行LBT失败指示时，计数器加1，当收到的计数值超过预设的数值时，触发持续LBT失败。另外当定时器超时时，该计数器重置。
例如，对于配置了LBT失败恢复配置参数(例如lbt-FailureRecoveryConfig)的服务小区，如果收到了来自低层的LBT失败指示且如果LBT计数器(例如LBT_COUNTER)大于或等于LBT失败最大值(例如lbt-FailureInstanceMaxCount)，MAC实体将会触发这个服务小区的BWP上的持续LBT失败(又称为该服务小区激活的上行BWP上的持续LBT失败)。
例如，当该服务小区是特殊小区(SpCell)时，如果在这个服务小区里相同载波(carrier)上配置了物理随机接入信道时机(PRACH occasions)的所有上行BWP(UL BWP)都触发了持续LBT失败，MAC实体将会向上层(例如RRC层)指示持续LBT失败；否则，MAC实体将会停止这个服务小区里任何正在进行的随机接入过程，切换激活UL BWP到该服务小区里相同载波配置了PRACH occasion且尚未触发持续LBT失败的一个UL BWP上，并发起随机接入过程。
小区切换是指终端设备从经源小区与网络进行数据传输切换到经目标小区与网络进行数据传输的过程，其包括切换准备(Handover Prepartion)、切换执行(Handover Execution)和切换完成(Handover Completion)三个过程。在切换执行期间，源小区的网络设备向终端设备发送RRC重配置消息(RRCReconfiguration消息)触发Uu切换，即Uu口涉及的源小区和目标小区的切换，该消息包括接入目标小区所需的信息；终端设备同步到目标小区并通过向目标小区的网络设备发送RRC重配置完成消息(RRCReconfigurationComplete消息)完成RRC切换过程。在小区切换是双活动协议栈(Dual Active Protocol Stack，DAPS)切换的情况下，终端设备收到RRC重配置消息时，终端设备不从源小区离开(detach)，终端设备继续与源小区的网络设备进行数据传输。当从目标小区的网络设备收到一个显式的释放时，终端设备释放源小区的信令无线承载(signalling radio bearers，SRB)资源以及源小区的安全配置，并停止与源小区的下行和/或上行(DL/UL)传输。
发明人发现，当在小区切换期间应用持续LBT失败检测和恢复机制时，根据当 前的小区切换机制，如果没有数据承载(Data RB，DRB)配置DAPS，当终端设备收到主小区组MAC(MCG MAC)的持续上行LBT失败指示时，终端设备将会认为为该MCG宣告无线链路失败，并丢弃收到的分段RRC消息的分段以及存储无线链路失败信息，且如果定时器T316未配置或辅小区组(SCG)传输被挂起或主辅小区改变(PSCell change)正在进行，则发起连接重建过程。
如果在小区切换期间，收到MCG MAC的持续上行LBT失败指示：如果该持续LBT失败指示是目标小区上的，那么，按照现有机制，终端设备将进行连接重建，而不论切换是否成功。另外，在小区切换为DAPS的情况下，如果该持续LBT失败指示是源小区上的，那么，按照现有机制，终端设备将进行连接重建，而不论切换是否成功。
而实际上，如果终端设备不进行连接重建，终端设备在切换成功后，可以使用目标小区进行传输。因此，当前的机制可能造成不必要的连接重建，导致用户服务中断，从而导致用户体验下降。
为了解决上述问题中的一个或多个，本申请实施例提供了一种小区切换中的持续LBT失败检测和恢复的方法及装置。
根据本申请实施例的第一方面，提供了一种小区切换中的持续LBT失败检测和恢复的装置，该装置应用于终端设备，该装置包括：第一处理单元，其用于在小区切换期间，收到持续LBT失败指示；并且，停止与网络设备的数据发送和/或接收，和/或，第二处理单元，其用于在小区切换期间，挂起持续LBT失败检测与恢复。
根据本申请实施例的第二方面，提供了一种小区切换中的持续LBT失败检测和恢复的装置，该装置应用于终端设备，该装置包括：第三处理单元，其用于在小区切换期间，当收到持续LBT失败指示时，停止与网络设备的数据发送和/或接收，和/或，第四处理单元，其用于在小区切换期间，挂起持续LBT失败检测与恢复。
根据本申请实施例的第三方面，提供了一种小区切换中的持续LBT失败检测和恢复的装置，该装置应用于网络设备，该装置包括：第一发送单元，其用于向终端设备发送RRC重配置消息，所述RRC重配置消息包括LBT失败检测与恢复相关的配置信息。
根据本申请实施例的第四方面，提供了一种终端设备，该终端设备包括根据根据本申请实施例的第一方面或第二方面所述的装置。
根据本申请实施例的第五方面，提供了一种网络设备，该网络设备包括根据本申请实施例的第三方面所述的装置。
根据本申请实施例的第六方面，提供了一种通信系统，该通信系统包括根据本申请实施例的第四方面所述的终端设备和/或根据本申请实施例的第五方面所述的网络设备。
根据本申请实施例的第七方面，提供了一种小区切换中的持续LBT失败检测和恢复的方法，该方法应用于终端设备，该方法包括：在小区切换期间，收到持续LBT失败指示；并且，停止与网络设备的数据发送和/或接收，和/或，在小区切换期间，挂起持续LBT失败检测与恢复。
根据本申请实施例的第八方面，提供了一种小区切换中的持续LBT失败检测和恢复的方法，该方法应用于终端设备，该方法包括：在小区切换期间，当收到持续LBT失败指示时，停止与网络设备的数据发送和/或接收，和/或，在小区切换期间，挂起持续LBT失败检测与恢复。
根据本申请实施例的第九方面，提供了一种小区切换中的持续LBT失败检测和恢复的方法，该方法应用于网络设备，该方法包括：向终端设备发送RRC重配置消息，所述RRC重配置消息包括LBT失败检测与恢复相关的配置信息。
根据本申请实施例的第十方面，提供了一种提供了一种计算机可读程序，其中当在小区切换中的持续LBT失败检测和恢复的装置或终端设备中执行所述程序时，所述程序使得所述小区切换中的持续LBT失败检测和恢复的装置或终端设备执行本发明实施例的第七方面或第八方面所述的小区切换中的持续LBT失败检测和恢复的方法。
根据本发明实施例的第十一方面，提供了一种存储有计算机可读程序的存储介质，其中所述计算机可读程序使得小区切换中的持续LBT失败检测和恢复的装置或终端设备执行本发明实施例的第七方面或第八方面所述的小区切换中的持续LBT失败检测和恢复的方法。
根据本发明实施例的第十二方面，提供了一种计算机可读程序，其中当在小区切换中的持续LBT失败检测和恢复的装置或网络设备中执行所述程序时，所述程序使得所述小区切换中的持续LBT失败检测和恢复的装置或网络设备执行本发明实施例的第九方面所述的小区切换中的持续LBT失败检测和恢复的方法。
根据本发明实施例的第十三方面，提供一种存储有计算机可读程序的存储介质，其中所述计算机可读程序使得小区切换中的持续LBT失败检测和恢复的装置或网络设备执行本发明实施例的第九方面所述的小区切换中的持续LBT失败检测和恢复的方法。
本申请实施例的有益效果之一在于：在小区切换期间，当收到持续LBT失败指示时，终端设备停止与网络设备的数据发送和/或接收，和/或，在小区切换期间，终端设备挂起持续LBT失败检测和恢复。这样，在小区切换期间，终端设备不会因为持续LBT失败发起连接重建过程，从而避免由此造成的用户服务中断和用户体验的下降。
参照后文的说明和附图，详细公开了本发明的特定实施方式，指明了本发明的原理可以被采用的方式。应该理解，本发明的实施方式在范围上并不因而受到限制。在所附权利要求的精神和条款的范围内，本发明的实施方式包括许多改变、修改和等同。
针对一种实施方式描述和/或示出的特征可以以相同或类似的方式在一个或更多个其它实施方式中使用，与其它实施方式中的特征相组合，或替代其它实施方式中的特征。
应该强调，术语“包括/包含/具有”在本文使用时指特征、整件、步骤或组件的存在，但并不排除一个或更多个其它特征、整件、步骤或组件的存在或附加。
附图说明
在本申请实施例的一个附图或一种实施方式中描述的元素和特征可以与一个或更多个其它附图或实施方式中示出的元素和特征相结合。此外，在附图中，类似的标号表示几个附图中对应的部件，并可用于指示多于一种实施方式中使用的对应部件。
所包括的附图用来提供对本申请实施例的进一步的理解，其构成了说明书的一部分，用于例示本发明的实施方式，并与文字描述一起来阐释本发明的原理。显而易见地，下面描述中的附图仅仅是本发明的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动性的前提下，还可以根据这些附图获得其它的附图。在附图中：
图1是本申请实施例的通信系统的一示意图；
图2是本申请实施例的小区切换过程的一示意图；
图3是本申请实施例1的小区切换中的持续LBT失败检测和恢复的方法的一示 意图；
图4是本申请实施例1的小区切换中的持续LBT失败检测和恢复的方法的一示意图；
图5是本申请实施例1的停止与网络设备的数据发送和/或接收的一示意图；
图6是本申请实施例1的停止与网络设备的数据发送和/或接收的另一示意图；
图7是本申请实施例1的停止与网络设备的数据发送和/或接收的又一示意图；
图8是本申请实施例2的小区切换中的持续LBT失败检测和恢复的方法的一示意图；
图9是本申请实施例3的小区切换中的持续LBT失败检测和恢复的方法的一示意图；
图10是本申请实施例4的小区切换中的持续LBT失败检测和恢复的装置的一示意图；
图11是本申请实施例5的小区切换中的持续LBT失败检测和恢复的装置的一示意图；
图12是本发明实施例6的终端设备的系统构成的一示意框图；
图13是本发明实施例7的网络设备的系统构成的一示意框图。
具体实施方式
参照附图，通过下面的说明书，本发明的前述以及其它特征将变得明显。在说明书和附图中，具体公开了本发明的特定实施方式，其表明了其中可以采用本发明的原则的部分实施方式，应了解的是，本发明不限于所描述的实施方式，相反，本发明包括落入所附权利要求的范围内的全部修改、变型以及等同物。
在本申请实施例中，术语“第一”、“第二”等用于对不同元素从称谓上进行区分，但并不表示这些元素的空间排列或时间顺序等，这些元素不应被这些术语所限制。术语“和/或”包括相关联列出的术语的一种或多个中的任何一个和所有组合。术语“包含”、“包括”、“具有”等是指所陈述的特征、元素、元件或组件的存在，但并不排除存在或添加一个或多个其他特征、元素、元件或组件。
在本申请实施例中，单数形式“一”、“该”等包括复数形式，应广义地理解为“一种”或“一类”而并不是限定为“一个”的含义；此外术语“所述”应理解为既 包括单数形式也包括复数形式，除非上下文另外明确指出。此外术语“根据”应理解为“至少部分根据……”，术语“基于”应理解为“至少部分基于……”，除非上下文另外明确指出。
在本申请实施例中，术语“通信网络”或“无线通信网络”可以指符合如下任意通信标准的网络，例如长期演进(LTE，Long Term Evolution)、增强的长期演进(LTE-A，LTE-Advanced)、宽带码分多址接入(WCDMA，Wideband Code Division Multiple Access)、高速报文接入(HSPA，High-Speed Packet Access)等等。
并且，通信系统中设备之间的通信可以根据任意阶段的通信协议进行，例如可以包括但不限于如下通信协议：1G(generation)、2G、2.5G、2.75G、3G、4G、4.5G以及未来的5G、新无线(NR，New Radio)等等，和/或其他目前已知或未来将被开发的通信协议。
在本申请实施例中，术语“网络设备”例如是指通信系统中将用户设备接入通信网络并为该用户设备提供服务的设备。网络设备可以包括但不限于如下设备：基站(BS，Base Station)、接入点(AP、Access Point)、发送接收点(TRP，Transmission Reception Point)、广播发射机、移动管理实体(MME、Mobile Management Entity)、网关、服务器、无线网络控制器(RNC，Radio Network Controller)、基站控制器(BSC，Base Station Controller)等等。
其中，基站可以包括但不限于：节点B(NodeB或NB)、演进节点B(eNodeB或eNB)以及5G基站(gNB)，等等，此外还可包括远端无线头(RRH，Remote Radio Head)、远端无线单元(RRU，Remote Radio Unit)、中继(relay)或者低功率节点(例如femto、pico等等)。并且术语“基站”可以包括它们的一些或所有功能，每个基站可以对特定的地理区域提供通信覆盖。术语“小区”可以指的是基站和/或其覆盖区域，这取决于使用该术语的上下文。
在本申请实施例中，术语“用户设备”(UE，User Equipment)例如是指通过网络设备接入通信网络并接收网络服务的设备，也可以称为“终端设备”(TE，Terminal Equipment)。终端设备可以是固定的或移动的，并且也可以称为移动台(MS，Mobile Station)、终端、用户台(SS，Subscriber Station)、接入终端(AT，Access Terminal)、站，等等。
其中，终端设备可以包括但不限于如下设备：蜂窝电话(Cellular Phone)、个人 数字助理(PDA，Personal Digital Assistant)、无线调制解调器、无线通信设备、手持设备、机器型通信设备、膝上型计算机、无绳电话、智能手机、智能手表、数字相机，等等。
再例如，在物联网(IoT，Internet of Things)等场景下，终端设备还可以是进行监控或测量的机器或装置，例如可以包括但不限于：机器类通信(MTC，Machine Type Communication)终端、车载通信终端、设备到设备(D2D，Device to Device)终端、机器到机器(M2M，Machine to Machine)终端，等等。
在本申请实施例中，“当……时”、“在……情况下”、“对于……的情况”以及“如果……”都表示基于某个或某些条件或状态等，另外，这些表述方式可以互相替换。
以下通过示例对本申请实施例的场景进行说明，但本发明不限于此。
图1是本申请实施例的通信系统的一示意图，其示意性说明了以终端设备和网络设备为例的情况，如图1所示，通信系统100可以包括：第一网络设备101、第二网络设备102和终端设备103。为简单起见，图1仅以一个终端设备为例进行说明。第一网络设备101、第二网络设备102例如为NR的网络设备gNB。
在本申请实施例中，第一网络设备101、第二网络设备102和终端设备103之间可以进行现有的业务或者未来可实施的业务。例如，这些业务包括但不限于：增强的移动宽带(eMBB，enhanced Mobile Broadband)、大规模机器类型通信(mMTC，massive Machine Type Communication)和高可靠低时延通信(URLLC，Ultra-Reliable and Low-Latency Communication)，等等。
例如，终端设备103进行小区切换，第一网络设备101为小区切换的源小区的网络设备，第二网络设备102为小区切换的目标小区的网络设备，例如第一网络设备101为源网络设备或源基站，第二网络设备102为目标网络设备或目标基站。另外，第一网络设备101可以覆盖包括源小区在内的多个小区，该多个小区可以称为属于第一网络设备101的小区；第二网络设备102可以覆盖包括目标小区在内的多个小区，该多个小区可以称为属于第二网络设备102的小区。
图2是本申请实施例的小区切换过程的一示意图。如图2所示，终端设备103和源小区的第一网络设备101之间进行用户数据的交互，在步骤201中，终端设备103进行测量控制和上报(Measurement Control and Reports)；在步骤202中，第一网络设备101执行切换决定(Handover Decision)；在步骤203中，第一网络设备101 向第二网络设备102发送切换请求(HANDOVER REQUEST)；在步骤204中，第二网络设备102执行准入控制(Admission Control)；在步骤205中，第二网络设备102向第一网络设备101发送切换请求确认(HANDOVER REQUEST ACKNOWLEDGE)消息，该切换请求确认消息可以包括接入目标小区所需的信息以及与LBT失败检测和恢复相关的配置信息，该与LBT失败检测和恢复相关的配置信息是终端对目标网络设备中的小区进行持续LBT失败检测与恢复的配置信息；在步骤206中，执行RAN切换启动(RAN Handover Initiation)，具体的，第一网络设备101向终端设备103发送RRC重配置消息(RRCReconfiguration消息)触发Uu切换，即Uu口涉及的源小区和目标小区的切换，该消息包括接入目标小区所需的信息以及LBT失败检测和恢复相关的配置信息；在步骤207中，第一网络设备101向第二网络设备102发送SN状态转移(SN STATUS TRANSFER)；在步骤208中，终端设备103执行RAN切换完成(RAN Handover Completion)，具体的，终端设备103同步到目标小区并通过向目标小区的第二网络设备102发送RRC重配置完成消息(RRCReconfigurationComplete消息)完成RRC切换过程。在小区切换是双活动协议栈(Dual Active Protocol Stack，DAPS)切换的情况下，终端设备103收到RRC重配置消息时，终端设备103不从源小区离开(detach)，继续与源小区的下行和/或上行(DL/UL)传输。当从目标小区的第二网络设备102收到一个显式的释放时，终端设备103释放源小区的信令无线承载(signalling radio bearers，SRB)资源以及源小区的安全配置，并停止与源小区的下行和/或上行(DL/UL)传输。
在小区切换期间，例如，在图2的步骤206至步骤208的期间，即切换执行期间，当终端设备103在对终端设备在源小区和/或目标小区上将要进行的上行传输进行LBT时，可能发生LBT失败，当终端设备103的MAC层收到来自物理层的LBT失败指示且LBT计数器大于或等于LBT失败最大值时，终端设备103的MAC层触发该源小区和/或目标小区的激活BWP上的持续LBT失败。如果该源小区和/或目标小区上配置了随机接入资源(PRACH occasion)的所有BWP(s)都触发了持续LBT失败，MAC向高层指示持续LBT失败。如果该持续LBT失败指示是目标MAC提供的，即由于目标小区上的持续LBT失败向高层指示持续LBT失败，那么，按照现有机制，终端设备103将进行连接重建，而不论切换是否成功。另外，在小区切换为DAPS的情况下，如果该持续LBT失败指示是源MAC提供的，即由于源小区上的持续LBT 失败向高层指示持续LBT失败，那么，按照现有机制，终端设备103将进行连接重建，而不论切换是否成功。而实际上，如果终端设备103不进行连接重建，终端设备103在切换成功后，可以使用目标小区进行传输。因此，当前的机制可能造成不必要的连接重建，导致用户服务中断，从而导致用户体验下降。
下面结合附图对本申请实施例的各种实施方式进行说明。这些实施方式只是示例性的，不是对本发明的限制。
实施例1
本申请实施例提供了一种小区切换中的持续LBT失败检测和恢复的方法，该方法应用于终端设备。例如，该方法应用于图1中的终端设备103。
图3是本申请实施例1的小区切换中的持续LBT失败检测和恢复的方法的一示意图。如图3所示，该方法包括：
步骤301：在小区切换期间，收到持续LBT失败指示；并且，停止与网络设备的数据发送和/或接收，和/或，
步骤302：在小区切换期间，挂起持续LBT失败检测与恢复检测和恢复。
在本申请实施例中，持续LBT失败检测与恢复的方法是指检测持续LBT失败的方法以及使终端设备从持续LBT失败恢复的方法。
在本申请实施例中，小区切换期间是指进行小区切换的期间，例如，小区切换期间指的是切换执行期间，例如图2中的步骤206至步骤208的期间。
在步骤301中，在小区切换期间，终端设备收到持续LBT失败指示；并且，终端设备停止与网络设备的数据发送和/或接收。例如，在小区切换期间，当终端设备收到持续LBT失败指示时，终端设备停止与网络设备的数据发送和/或接收。又例如，在小区切换期间，终端设备收到持续LBT失败指示；并且，当满足其他条件时，终端设备停止与网络设备的数据发送和/或接收。
图4是本申请实施例1的小区切换中的持续LBT失败检测和恢复的方法的一示意图。如图4所示，该方法包括：
步骤401：在小区切换期间，当收到持续LBT失败指示时，停止与网络设备的数据发送和/或接收，和/或，
步骤402：在小区切换期间，挂起持续LBT失败检测与恢复检测和恢复。
这样，在小区切换期间，当收到持续LBT失败指示时，终端设备停止与网络设 备的数据发送和/或接收，和/或，在小区切换期间，终端设备挂起持续LBT失败检测和恢复。这样，在小区切换期间，终端设备不会因为持续LBT失败发起连接重建过程，从而避免由此造成的用户服务中断和用户体验的下降。
在本申请实施例中，例如，终端设备收到持续LBT失败指示指的是终端设备的RRC层收到持续LBT失败指示。
在本申请实施例中，持续LBT失败指示又称为持续上行LBT失败指示。
例如，终端设备的物理层对上行传输执行LBT，当LBT失败时，向MAC层指示LBT失败。当MAC层收到来自物理层的LBT失败指示时，计数值LBT_COUNTER加1，当计数值超过预设的数值，例如LBT_COUNTER≥lbt-FailureInstanceMaxCount时，MAC层触发持续LBT失败。
例如，当服务小区是特殊小区(SpCell)时，如果这个服务小区激活的上行BWP(UL BWP)触发了持续LBT失败，则切换到另一个BWP上并发起随机接入；如果在这个服务小区里相同载波(carrier)上配置了物理随机接入信道时机(PRACH occasions)的所有上行BWP(UL BWP)都触发了持续LBT失败，MAC实体将会向高层，例如RRC层，指示持续LBT失败。
在本申请实施例中，小区切换可以是：双活动协议栈(DAPS)切换，或者，双活动协议栈(DAPS)切换和非DAPS切换，或者，非DAPS切换。
例如，双活动协议栈(DAPS)切换是指，为了执行同步的重配(a reconfiguration with sync)，且如果为任何(any)DRB配置了dapsConfig；双活动协议栈(DAPS)切换和非DAPS切换是指，为了执行同步的重配(a reconfiguration with sync)；非DAPS切换是指，为了执行同步的重配(a reconfiguration with sync)，且任何(any)DRB都未配置dapsConfig。
在本申请实施例中，小区切换是指终端设备经源小区与网络进行数据传输切换到经目标小区与网络进行数据传输的过程。
例如，该源小区属于第一网络设备，该目标小区属于第二网络设备，该第一网络设备可以称为源基站，该第二网络设备可以称为目标基站。
例如，对于终端设备既没有配置载波聚合(CA)，也没有配置双连接(DC)的情况，源小区和目标小区分别是一个服务小区。
例如，对于终端设备配置了载波聚合和/或双连接的情况，源小区和目标小区是 主小区。
另外，对于终端设备配置了载波聚合和/或双连接的情况，第一网络设备可以覆盖多个小区，该多个小区包括源小区(主小区)，还可以包括其他小区，例如辅小区；第二网络设备也可以覆盖多个小区，该多个小区包括目标小区(主小区)，还可以包括其他小区，例如辅小区。
在本申请实施例中，对于一个小区，该方法可以包括步骤301和步骤302这两者，或者包括步骤401和步骤402这两者。
对应于步骤301和步骤302，例如，在小区切换期间，收到持续LBT失败指示，和/或，停止与网络设备的数据发送和/或接收；并且，挂起持续LBT失败检测和恢复。
也就是说，
例如，在小区切换期间，收到持续LBT失败指示；并且，挂起持续LBT失败检测和恢复；
例如，在小区切换期间，停止与网络设备的数据发送和/或接收；并且，挂起持续LBT失败检测和恢复；
例如，在小区切换期间，收到持续LBT失败指示；并且，停止与网络设备的数据发送和/或接收；并且，挂起持续LBT失败检测和恢复。
对应于步骤401和步骤402，例如，在小区切换期间，当收到持续LBT失败指示时，和/或，当停止与网络设备的数据发送和/或接收时，挂起持续LBT失败检测和恢复。
也就是说，例如，在小区切换期间，当收到持续LBT失败指示时，挂起持续LBT失败检测和恢复；
例如，在小区切换期间，当停止与网络设备的数据发送和/或接收时，挂起持续LBT失败检测和恢复；
例如，在小区切换期间，当收到持续LBT失败指示，并且停止与网络设备的数据发送和/或接收时，挂起持续LBT失败检测和恢复；
在本申请实施例中，对于不同的小区，该方法可以针对不同的小区分别执行不同的步骤，即针对不同的小区分别采用不同的方案。
例如，该小区切换是双活动协议栈(DAPS)切换，对应于步骤301和步骤302，在小区切换期间，收到持续LBT失败指示；以及停止与第一网络设备的数据发送和 接收，和/或，在小区切换期间，挂起该终端设备对第二小区的持续LBT失败检测和恢复。
又例如，该小区切换是双活动协议栈(DAPS)切换，对应于步骤401和步骤402，在小区切换期间，当收到持续LBT失败指示时，停止与第一网络设备的数据发送和接收，和/或，在小区切换期间，挂起该终端设备对第二小区的持续LBT失败检测和恢复。
在上述示例中，该第二小区属于第二网络设备，该第一网络设备是源网络设备，该第二网络设备是目标网络设备。例如，该第二小区可以是目标小区，也可以是第二网络设备覆盖的其他小区，例如辅小区。
例如，该小区切换是双活动协议栈(DAPS)切换，在小区切换期间，收到持续LBT失败指示；以及停止与第一网络设备的数据发送和接收，和/或，在小区切换期间，挂起所述终端设备对目标小区的持续LBT失败检测与恢复，该第一网络设备是源网络设备。
也就是说，对于双活动协议栈(DAPS)切换，
例如，在小区切换期间，收到持续LBT失败指示；以及停止与第一网络设备的数据发送和接收。
例如，在小区切换期间，挂起所述终端设备对目标小区的持续LBT失败检测与恢复，该第一网络设备是源网络设备。
例如，在小区切换期间，收到持续LBT失败指示；以及停止与第一网络设备的数据发送和接收，并且，在小区切换期间，挂起所述终端设备对目标小区的持续LBT失败检测与恢复，该第一网络设备是源网络设备。
在本申请实施例中，在小区切换期间保留SCG和/或辅小区的情况下，对于主小区，可以执行步骤301和步骤302，或者，执行步骤401和步骤402；对于主辅小区和辅小区，可以执行步骤302或步骤402。
在步骤301和/或步骤401中，收到的该持续LBT失败指示来自终端设备的MAC层。例如，该持续LBT失败指示来自该终端设备的源MAC实体、目标MAC实体以及MCG MAC实体中的至少一个。
例如，在小区切换是DAPS切换的情况下，该持续LBT失败指示来自终端设备的源(source)MAC实体或目标(target)MAC实体。
例如，在定时器T304运行的情况下，该持续LBT失败指示来自终端设备的MCG MAC实体。
在步骤301和/或步骤401中，停止与网络设备的数据发送和/或接收，可以包括以下的至少一个：
停止与第一网络设备的数据发送和/或接收；
停止与第二网络设备的除随机接入相关传输的数据以外的数据发送和/或接收；以及
停止与MCG网络设备的数据发送和/或接收，
该第一网络设备是源网络设备，该第二网络设备是目标网络设备。
在本申请实施例中，对于非DAPS切换，例如，在步骤301中，在小区切换期间，收到来自终端设备的MCG MAC实体的持续LBT失败指示；并且，停止与MCG网络设备的数据发送和/或接收。相应的，在步骤401中，在小区切换期间，当收到来自终端设备的MCG MAC实体的持续LBT失败指示时，停止与MCG网络设备的数据发送和/或接收。
图5是本申请实施例1的停止与网络设备的数据发送和/或接收的一示意图。如图5所示，MAC实体进行持续LBT失败检测，如果主小区(PCell)上激活的上行BWP(UL BWP)触发了持续LBT失败，则切换到另一个BWP上并发起随机接入，如果在该主小区里相同载波(carrier)上配置了物理随机接入信道时机(PRACH occasions)的所有上行BWP(UL BWP)都触发了持续LBT失败，MAC实体将会向RRC层指示持续LBT失败。RRC层进行无线链路失败(RLF)检测，当RRC层收到来自MAC实体的持续LBT失败指示时，停止与网络设备的数据发送和/或接收(TX/RX)。
在本申请实施例中，对于DAPS切换，例如，在步骤301中，在小区切换期间，收到来自终端设备的源(source)MAC实体的持续LBT失败指示；并且，停止与该第一网络设备的数据发送和/或接收。相应的，在步骤401中，在小区切换期间，当收到来自终端设备的源(source)MAC实体的持续LBT失败指示时，停止与该第一网络设备的数据发送和/或接收。
对于DAPS切换，又例如，在步骤301中，在小区切换期间，收到来自终端设备的目标(target)MAC实体的持续LBT失败指示；并且，停止与该第二网络设备的 数据发送和/或接收，或者，停止与该第一网络设备以及该第二网络设备的数据发送和/或接收。相应的，在步骤401中，在小区切换期间，当收到来自终端设备的目标(target)MAC实体的持续LBT失败指示时，停止与该第二网络设备的除随机接入相关传输的数据以外的数据发送和/或接收，或者，停止与该第一网络设备数据发送和/或接收以及该第二网络设备的除随机接入相关传输的数据以外的数据发送和/或接收。
也就是说，对于DAPS切换，源MAC实体和目标MAC实体分别进行持续LBT失败检测并分别向RRC层指示持续LBT失败，并且，RRC层停止与第一网络设备和/或第二网络设备的除随机接入相关传输的数据以外的数据发送和/或接收。
或者，也可以是，源MAC实体和目标MAC实体分别进行持续LBT失败检测并分别向RRC层指示持续LBT失败，当收到来自源MAC实体和/或目标MAC实体的持续LBT失败指示时，RRC层停止与第一网络设备的数据发送和/或接收，而对于第二网络设备不做行为，包括不进行连接重建。
图6是本申请实施例1的停止与网络设备的数据发送和/或接收的另一示意图。如图6所示，源MAC实体和目标MAC实体分别进行持续LBT失败检测并分别指示RRC层持续LBT失败，如果主小区(PCell)上激活的上行BWP(UL BWP)触发了持续LBT失败，则切换到另一个BWP上并发起随机接入，如果在该主小区里相同载波(carrier)上配置了物理随机接入信道时机(PRACH occasions)的所有上行BWP(UL BWP)都触发了持续LBT失败，源MAC实体和/或目标MAC实体将会向RRC层指示持续LBT失败，RRC层进行无线链路失败(RLF)检测，当RRC层收到来自源MAC实体的持续LBT失败指示时，停止与第一网络设备的数据发送和/或接收(TX/RX)，当RRC层收到来自目标MAC实体的持续LBT失败指示时，停止与第二网络设备除随机接入相关传输的数据以外的数据发送和/或接收(TX/RX)。
图7是本申请实施例1的停止与网络设备的数据发送和/或接收的又一示意图。如图7所示，源MAC实体和目标MAC实体分别进行持续LBT失败检测并分别指示RRC层持续LBT失败，如果主小区(PCell)上激活的上行BWP(UL BWP)触发了持续LBT失败，则切换到另一个BWP上并发起随机接入，如果在该主小区里相同载波(carrier)上配置了物理随机接入信道时机(PRACH occasions)的所有上行BWP(UL BWP)都触发了持续LBT失败，源MAC实体和/或目标MAC实体将会向RRC 层指示持续LBT失败，RRC层进行无线链路失败(RLF)检测，当RRC层收到来自源MAC实体和/或目标MAC实体的持续LBT失败指示时，停止与第一网络设备的数据发送和/或接收(TX/RX)，而对于第二网络设备不做行为，包括不进行连接重建。
在本申请实施例中，该方法还可以包括以下步骤中的至少一个：该终端设备保持在RRC连接状态；该终端设备释放与第一网络设备的连接；该终端设备维持第一网络设备的RRC配置；以及该终端设备认为与第一网络设备的无线链路失败，其中，该第一网络设备是源网络设备。
在步骤302和/或步骤402中，在小区切换期间，挂起持续LBT失败检测与恢复，包括：在小区切换期间，挂起终端设备对第一小区和/或第二小区的持续LBT失败检测与恢复，该第一小区属于第一网络设备，该第二小区属于第二网络设备，该第一网络设备是源网络设备，该第二网络设备是目标网络设备。
其中，该第一小区是服务小区或者主小区或者主辅小区或者辅小区，和/或，该第二小区是服务小区或者主小区或者主辅小区或者辅小区。
例如，对于终端设备既没有配置载波聚合(CA)，也没有配置双连接(DC)的情况，该第一小区是一个服务小区，该第二小区是一个服务小区。
例如，对于终端设备配置了载波聚合和/或双连接的情况，该第一小区可以是主小区或主辅小区或辅小区，该第二小区可以是主小区或主辅小区或辅小区。
在步骤302和/或步骤402中，该挂起持续LBT失败检测与恢复，包括以下的至少一个：
物理层停止向MAC层指示LBT失败；例如，当收到来自RRC的挂起持续LBT失败检测和恢复的指示时，物理层停止向MAC层指示LBT失败；也就是说，在没有收到挂起持续LBT失败检测与恢复的指示且LBT失败的情况下，物理层向MAC层指示LBT失败；
MAC层不触发持续LBT失败；例如，当收到来自RRC的挂起持续LBT失败检测和恢复的指示时，MAC层不触发持续LBT失败；也就是说，对于配置了LBT失败恢复配置参数的服务小区，在没有收到来自挂起持续LBT失败检测与恢复的指示且收到了来自低层的LBT失败指示且LBT计数器(例如LBT_COUNTER)大于或等于LBT失败最大值(例如LBT_COUNTER≥lbt-FailureInstanceMaxCount)时，MAC实体触发该服务小区的BWP上的持续LBT失败；
MAC层不向上层(例如RRC层)指示持续LBT失败；例如，当收到来自RRC的挂起持续LBT失败检测和恢复的指示时，MAC层不向上层指示持续LBT失败；也就是说，当触发了持续LBT失败的服务小区是特殊小区时，在没有收到挂起持续LBT失败检测与恢复的指示且在该服务小区中的相同载波上配置了物理随机接入信道时机(PRACH occasion)的所有上行BWP都触发了持续LBT失败的情况下，MAC实体向上层指示持续LBT失败；
收到持续LBT失败指示且用于小区切换的定时器(例如T304)未运行，认为无线链路失败；或者，该定时器(例如T304)运行时，收到持续LBT失败指示，不认为无线链路失败或忽略该持续LBT失败指示；以及
发生无线链路失败且用于小区切换的定时器(例如T304)未运行，并发起连接重建；或者，该定时器(例如T304)运行且发生无线链路失败时，不发起连接重建。
在步骤302和/或步骤402中，该挂起持续LBT失败检测与恢复，还可以包括：RRC层指示低层挂起持续LBT失败检测和恢复。
例如，为了执行同步的重配(a reconfiguration with sync)，或者，当用于小区切换的定时器启动时，RRC层指示低层挂起持续LBT失败检测和恢复。
在本申请实施例中，该低层是物理层和/或MAC层。
例如，RRC可以指示物理层挂起持续LBT失败检测和恢复，例如，当物理层收到来自RRC的挂起持续LBT失败检测和恢复的指示时，物理层停止向MAC层指示LBT失败。
例如，RRC可以指示MAC层挂起持续LBT失败检测和恢复，例如，当MAC层收到来自RRC的挂起持续LBT失败检测和恢复的指示时，MAC层不触发持续LBT失败，和/或，MAC层不向RRC层指示持续LBT失败。
例如，RRC可以指示物理层和MAC层挂起持续LBT失败检测和恢复，例如，当物理层收到来自RRC的挂起持续LBT失败检测和恢复的指示时，物理层停止向MAC层指示LBT失败，并且，当MAC层收到来自RRC的挂起持续LBT失败检测和恢复的指示时，MAC层不触发持续LBT失败，和/或，MAC层不向RRC层指示持续LBT失败。
在本申请实施例中，当该方法包括步骤302时，如图3所示，该方法还可以包括：
步骤303：小区切换完成，并且，恢复持续LBT失败检测与恢复机制。
例如，当小区切换完成时，恢复持续LBT失败检测与恢复机制。
又例如，当小区切换完成，且满足其他条件时，恢复持续LBT失败检测与恢复机制。
相应的，当该方法包括步骤402时，如图4所示，该方法还可以包括：
步骤403：在小区切换完成时，恢复持续LBT失败检测与恢复机制。
在本申请实施例中，小区切换完成可以是指，切换执行完成或者该终端设备同步到目标小区。
例如，终端设备同步到目标小区并通过向目标网络设备发送RRCReconfigurationComplete消息完成RRC切换过程，即图2中的步骤208执行完成。
在本申请实施例中，恢复持续LBT失败检测与恢复机制可以是指，恢复挂起的持续LBT失败检测与恢复机制，例如恢复通过步骤302和/或步骤402挂起的持续LBT失败检测与恢复机制。
在步骤303和/或步骤403中，该恢复持续LBT失败检测与恢复机制，包括以下的至少一个：
当收到恢复持续LBT失败检测和恢复的指示且LBT失败时，物理层向MAC层指示LBT失败；
对于配置了LBT失败恢复配置参数的服务小区，当收到恢复持续LBT失败检测和恢复的指示且收到了来自低层的LBT失败指示且LBT计数器(例如LBT_COUNTER)大于或等于LBT失败最大值(例如LBT_COUNTER≥lbt-FailureInstanceMaxCount)时，MAC实体触发该服务小区的BWP上的持续LBT失败；以及
当触发了持续LBT失败的服务小区是特殊小区时，当收到恢复持续LBT失败检测和恢复的指示，且在该服务小区中的相同载波上配置了物理随机接入信道(PRACH)时机的所有上行BWP都触发了持续LBT失败的情况下，MAC实体向上层指示持续LBT失败。
在步骤303和/或步骤403中，还可以包括：当RRC切换完成或者当该终端设备同步到第二小区时，RRC层指示低层恢复持续LBT失败检测和恢复，该第二小区是目标小区。
在本申请实施例中，如图3所示，该方法还可以包括：
步骤304：从第一网络设备接收RRC重配置消息，该RRC重配置消息包括LBT失败检测与恢复相关的配置信息，该第一网络设备是源网络设备。
相应的，如图4所示，该方法还可以包括：
步骤404：从第一网络设备接收RRC重配置消息，该RRC重配置消息包括LBT失败检测与恢复相关的配置信息，该第一网络设备是源网络设备。
在本申请实施例中，步骤304和/或步骤404是图2中的步骤206或图2中的步骤206的一部分。
在本申请实施例中，该LBT失败检测与恢复相关的配置信息可以包括第一配置信息和/或第二配置信息，该第一配置信息与第一小区的LBT失败检测与恢复相关，该第二配置信息与第二小区的LBT失败检测与恢复相关，该第一小区是属于源网络设备的一个小区，该第二小区是属于目标网络设备的一个小区。
例如，该第一小区可以是属于源网络设备的一个服务小区、主小区、主辅小区或辅小区，该第二小区可以是属于目标网络设备的一个服务小区、主小区、主辅小区或辅小区。
在本申请实施例中，该终端设备的源MAC实体可以根据该第一小区的LBT失败检测与恢复相关的配置信息，进行第一小区上的持续LBT失败检测与恢复；和/或，该终端设备的目标MAC实体可以根据该第二小区的LBT失败检测与恢复相关的配置信息，进行第二小区上的持续LBT失败检测与恢复。
由上述实施例可知，在小区切换期间，当收到持续LBT失败指示时，终端设备停止与网络设备的数据发送和/或接收，和/或，在小区切换期间，终端设备挂起持续LBT失败检测和恢复。这样，在小区切换期间，终端设备不会因为持续LBT失败发起连接重建过程，从而避免由此造成的用户服务中断和用户体验的下降。
实施例2
本申请实施例提供了一种小区切换中的持续LBT失败检测和恢复的方法，该方法应用于网络设备，其对应于实施例1所述的应用于终端设备的小区切换中的持续LBT失败检测和恢复的方法，相同的内容不再重复说明。
图8是本申请实施例2的小区切换中的持续LBT失败检测和恢复的方法的一示意图。如图8所示，该方法包括：
步骤801：向终端设备发送RRC重配置消息，该RRC重配置消息包括LBT失 败检测与恢复相关的配置信息。
在本申请实施例中，步骤801是图2中的步骤206或图2中的步骤206的一部分。
在本申请实施例中，该RRC重配置信息还包括接入第二小区所需的信息，该第二小区是目标小区。
在本申请实施例中，该网络设备是源网络设备。
在本申请实施例中，该LBT失败检测与恢复相关的配置信息包括第一配置信息和/或第二配置信息，该第一配置信息与第一小区的LBT失败检测与恢复相关，该第二配置信息与第二小区的LBT失败检测与恢复相关，该第一小区是属于源网络设备的一个小区，该第二小区是属于目标网络设备的一个小区。
例如，该第一小区可以是属于源网络设备的一个服务小区、主小区、主辅小区或辅小区，该第二小区可以是属于目标网络设备的一个服务小区、主小区、主辅小区或辅小区。
在本申请实施例中，该第一小区的LBT失败检测与恢复相关的配置信息用于该终端设备的源MAC实体进行第一小区上的持续LBT失败检测与恢复，和/或，该第二小区的LBT失败检测与恢复相关的配置信息用于该终端设备的目标MAC实体进行第二小区上的持续LBT失败检测与恢复。
在本申请实施例中，如图8所示，该方法还可以包括：
步骤802：从第二网络设备接收发送切换请求确认(HANDOVER REQUEST ACKNOWLEDGE)消息。
该第二网络设备是目标网络设备。
在本申请实施例中，该切换请求确认消息可以包括接入目标小区所需的信息以及与LBT失败检测和恢复相关的配置信息，该与LBT失败检测和恢复相关的配置信息是终端对目标网络设备中的小区进行持续LBT失败检测与恢复的配置信息。
在本申请实施例中，步骤802是图2中的步骤205或图2中的步骤205的一部分。
由上述实施例可知，网络设备向终端设备发送包括LBT失败检测与恢复相关的配置信息的RRC重配置消息，使得终端设备能够根据该LBT失败检测与恢复相关的配置信息进行持续LBT失败检测。
实施例3
本申请实施例提供了一种小区切换中的持续LBT失败检测和恢复的方法，该方 法应用于网络设备和终端设备，其对应于实施例1所述的应用于终端设备的小区切换中的持续LBT失败检测和恢复的方法和实施例2所述的应用于网络设备的小区切换中的持续LBT失败检测和恢复的方法，相同的内容不再重复说明。
图9是本申请实施例3的小区切换中的持续LBT失败检测和恢复的方法的一示意图。如图9所示，该方法包括：
步骤901：执行RAN切换启动，具体的，第一网络设备向终端设备发送RRC重配置消息触发Uu切换，该RRC重配置消息包括LBT失败检测与恢复相关的配置信息；为了同步到目标小区，终端设备可以向第二网络设备中的目标小区发起随机接入过程；
步骤902：终端设备收到持续LBT失败指示；
步骤903：终端设备停止与第一网络设备和/或第二网络设备的数据发送和/或接收；
步骤904：终端设备挂起持续LBT失败检测与恢复；
步骤905：执行RAN切换完成，具体的，终端设备同步到目标小区并通过向目标小区的第二网络设备发送RRC重配置完成消息(RRCReconfigurationComplete消息)完成RRC切换过程。
在本申请实施例中，该方法可以包括步骤903和/或步骤904，当该方法包括步骤904时，还可以包括：
步骤906：终端设备恢复持续LBT失败检测与恢复机制。
在本申请实施例中，该第一网络设备是源网络设备，该第二网络设备是目标网络设备。
在本申请实施例中，图9中各个步骤的具体实施可以参照实施例1和实施例2的记载，此处不再重复说明。
由上述实施例可知，在小区切换期间，当收到持续LBT失败指示时，终端设备停止与网络设备的数据发送和/或接收，和/或，在小区切换期间，终端设备挂起持续LBT失败检测和恢复。这样，在小区切换期间，终端设备不会因为持续LBT失败发起连接重建过程，从而避免由此造成的用户服务中断和用户体验的下降。
实施例4
本申请实施例提供了一种小区切换中的持续LBT失败检测和恢复的装置，该装 置应用于终端设备。由于该装置解决问题的原理与实施例1的方法类似，因此其具体的实施可以参照实施例1所述的方法的实施，内容相同或相关之处不再重复说明。
图10是本申请实施例4的小区切换中的持续LBT失败检测和恢复的装置的一示意图，如图10所示，装置1000包括：
第一处理单元1001，其用于在小区切换期间，收到持续LBT失败指示；并且，停止与网络设备的数据发送和/或接收，和/或，
第二处理单元1002，其用于在小区切换期间，挂起持续LBT失败检测与恢复。
在本申请实施例中，第一处理单元1001也可以是：在小区切换期间，当收到持续LBT失败指示时，停止与网络设备的数据发送和/或接收
在本申请实施例中，该小区切换包括：双活动协议栈(DAPS)切换，或者，双活动协议栈(DAPS)切换和非DAPS切换，或者，非DAPS切换。
在本申请实施例中，如图10所示，该装置1000还可以包括：
切换完成单元1003，其用于小区切换完成；
恢复单元1004，其用于恢复持续LBT失败检测与恢复机制，
例如，在小区切换完成时，恢复单元1004恢复持续LBT失败检测与恢复机制。
又例如，当小区切换完成，且满足其他条件时，恢复单元1004恢复持续LBT失败检测与恢复机制。
在本申请实施例中，如图10所示，该装置1000还可以包括：
第一接收单元1005，其用于从第一网络设备接收RRC重配置消息，该RRC重配置消息包括LBT失败检测与恢复相关的配置信息，该第一网络设备是源网络设备。
在本申请实施例的一种实施方式中，该装置1000还可以包括以下单元中的至少一个(未图示)：
保持单元，其用于该终端设备保持在RRC连接状态；
释放单元，其用于该终端设备释放与第一网络设备的连接；
维持单元，其用于该终端设备维持第一网络设备的RRC配置；以及
认为单元，其用于该终端设备认为与第一网络设备的无线链路失败，
该第一网络设备是源网络设备。
在本申请实施例的一种实施方式中，该装置1000还包括以下单元中的至少一个(未图示)：
第一指示单元，其用于在没有收到挂起持续LBT失败检测与恢复的指示且LBT失败的情况下，物理层向MAC层指示LBT失败；
第一触发单元，其用于对于配置了LBT失败恢复配置参数的服务小区，在没有收到来自挂起持续LBT失败检测与恢复的指示且收到了来自低层的LBT失败指示且LBT计数器大于或等于LBT失败最大值时，MAC实体触发该服务小区的BWP上的持续LBT失败；以及
第二指示单元，其用于当触发了持续LBT失败的服务小区是特殊小区时，在没有收到挂起持续LBT失败检测与恢复的指示且在该服务小区中的相同载波上配置了物理随机接入信道(PRACH)时机的所有上行BWP都触发了持续LBT失败的情况下，MAC实体向上层指示持续LBT失败。
在本实施例中，上述各个单元的功能的实现可以参照实施例1中相关步骤的内容，此处不再重复说明。
由上述实施例可知，在小区切换期间，当收到持续LBT失败指示时，终端设备停止与网络设备的数据发送和/或接收，和/或，在小区切换期间，终端设备挂起持续LBT失败检测和恢复。这样，在小区切换期间，终端设备不会因为持续LBT失败发起连接重建过程，从而避免由此造成的用户服务中断和用户体验的下降。
实施例5
本申请实施例提供了一种小区切换中的持续LBT失败检测和恢复的装置，该装置应用于网络设备。由于该装置解决问题的原理与实施例2的方法类似，因此其具体的实施可以参照实施例2所述的方法的实施，内容相同或相关之处不再重复说明。
图11是本申请实施例5的小区切换中的持续LBT失败检测和恢复的装置的一示意图，如图11所示，装置1100包括：
第一发送单元1101，其用于向终端设备发送RRC重配置消息，该RRC重配置消息包括LBT失败检测与恢复相关的配置信息。
在本申请实施例中，该RRC重配置信息还可以包括接入第二小区所需的信息，该第二小区是目标小区。
在本申请实施例中，该网络设备是源网络设备。
在本申请实施例中，该LBT失败检测与恢复相关的配置信息包括第一配置信息和/或第二配置信息，该第一配置信息与第一小区的LBT失败检测与恢复相关，该第 二配置信息与第二小区的LBT失败检测与恢复相关，该第一小区是属于源网络设备的一个小区，该第二小区是属于目标网络设备的一个小区。
例如，该第一小区可以是属于源网络设备的一个服务小区、主小区、主辅小区或辅小区，该第二小区可以是属于目标网络设备的一个服务小区、主小区、主辅小区或辅小区。
在本申请实施例中，该第一小区的LBT失败检测与恢复相关的配置信息用于该终端设备的源MAC实体进行第一小区上的持续LBT失败检测与恢复，和/或，该第二小区的LBT失败检测与恢复相关的配置信息用于该终端设备的目标MAC实体进行第二小区上的持续LBT失败检测与恢复。
在本申请实施例中，如图11所示，该装置1100还包括：
第二接收单元1102，其用于接收从第二网络设备发送的切换请求确认消息，该第二网络设备是目标网络设备。
在本申请实施例中，该切换请求确认消息可以包括接入目标小区所需的信息以及与LBT失败检测和恢复相关的配置信息，该与LBT失败检测和恢复相关的配置信息是该终端设备对目标网络设备中的小区进行持续LBT失败检测与恢复的配置信息。
由上述实施例可知，网络设备向终端设备发送包括LBT失败检测与恢复相关的配置信息的RRC重配置消息，使得终端设备能够根据该LBT失败检测与恢复相关的配置信息进行持续LBT失败检测。
实施例6
本申请实施例提供了一种终端设备，该终端设备包括如实施例4所述的小区切换中的持续LBT失败检测和恢复的装置。
图12是本发明实施例6的终端设备的系统构成的一示意框图。如图12所示，终端设备1200可以包括处理器1210和存储器1220；存储器1220耦合到处理器1210。值得注意的是，该图是示例性的；还可以使用其他类型的结构，来补充或代替该结构，以实现电信功能或其他功能。
在本申请实施例的一个实施方式中，小区切换中的持续LBT失败检测和恢复的装置的功能可以被集成到处理器1210中。
处理器1210可以被配置为：在小区切换期间，收到持续LBT失败指示；并且，停止与网络设备的数据发送和/或接收，和/或，在小区切换期间，挂起持续LBT失败 检测与恢复。
例如，该小区切换包括：双活动协议栈(DAPS)切换，或者，双活动协议栈(DAPS)切换和非DAPS切换，或者，非DAPS切换。
例如，在小区切换期间，当收到持续LBT失败指示时，和/或，当停止与网络设备的数据发送和/或接收时，挂起持续LBT失败检测与恢复。
例如，该小区切换是双活动协议栈(DAPS)切换，在小区切换期间，收到持续LBT失败指示；以及停止与第一网络设备的数据发送和接收，和/或，在小区切换期间，挂起该终端设备对目标小区的持续LBT失败检测与恢复，该第一网络设备是源网络设备。
例如，收到的该持续LBT失败指示来自该终端设备的MAC层。
例如，收到的该持续LBT失败指示来自该终端设备的MAC层，包括：收到的该持续LBT失败指示来自该终端设备的源MAC实体、目标MAC实体以及MCG MAC实体中的至少一个。
例如，该停止与网络设备的数据发送和/或接收，包括以下的至少一个：停止与第一网络设备的数据发送和/或接收；停止与第二网络设备的除随机接入相关传输的数据以外的数据发送和/或接收；以及停止与MCG网络设备的数据发送和/或接收，该第一网络设备是源网络设备，该第二网络设备是目标网络设备。
例如，处理器1210还可以被配置为执行以下步骤中的至少一个：该终端设备保持在RRC连接状态；该终端设备释放与第一网络设备的连接；该终端设备维持第一网络设备的RRC配置；以及该终端设备认为与第一网络设备的无线链路失败，该第一网络设备是源网络设备。
例如，在小区切换期间，挂起持续LBT失败检测与恢复，包括：在小区切换期间，挂起终端设备对第一小区和/或第二小区的持续LBT失败检测与恢复，该第一小区属于第一网络设备，该第二小区属于第二网络设备，该第一网络设备是源网络设备，该第二网络设备是目标网络设备。
例如，该第一小区是服务小区或者主小区或者主辅小区或者辅小区，和/或，该第二小区是服务小区或者主小区或者主辅小区或者辅小区。
例如，该挂起持续LBT失败检测与恢复，包括以下的至少一个：物理层停止向MAC层指示LBT失败；MAC层不触发持续LBT失败；MAC层不向上层指示持续 LBT失败；收到持续LBT失败指示且用于小区切换的定时器未运行，认为无线链路失败；或者，该定时器运行，且收到持续LBT失败指示，不认为无线链路失败或忽略该持续LBT失败指示；以及发生无线链路失败，且用于小区切换的定时器未运行，并发起连接重建；或者，该定时器运行，且发生无线链路失败，不发起连接重建。
例如，处理器1210还可以被配置为执行以下步骤中的至少一个：在没有收到挂起持续LBT失败检测与恢复的指示且LBT失败的情况下，物理层向MAC层指示LBT失败；对于配置了LBT失败恢复配置参数的服务小区，在没有收到来自挂起持续LBT失败检测与恢复的指示且收到了来自低层的LBT失败指示且LBT计数器大于或等于LBT失败最大值时，MAC实体触发该服务小区的BWP上的持续LBT失败；以及当触发了持续LBT失败的服务小区是特殊小区时，在没有收到挂起持续LBT失败检测与恢复的指示且在该服务小区中的相同载波上配置了物理随机接入信道(PRACH)时机的所有上行BWP都触发了持续LBT失败的情况下，MAC实体向上层指示持续LBT失败。
例如，该挂起持续LBT失败检测与恢复，还包括：
RRC层指示低层挂起持续LBT失败检测和恢复。
例如，为了执行同步的重配，或者，当用于小区切换的定时器启动时，RRC层指示低层挂起持续LBT失败检测和恢复。
例如，该低层是物理层和/或MAC层。
例如，处理器1210还可以被配置为在小区切换完成时，恢复持续LBT失败检测与恢复机制。
例如，该恢复持续LBT失败检测与恢复机制，包括以下的至少一个：当收到恢复持续LBT失败检测和恢复的指示且LBT失败时，物理层向MAC层指示LBT失败；对于配置了LBT失败恢复配置参数的服务小区，当收到恢复持续LBT失败检测和恢复的指示且收到了来自低层的LBT失败指示且LBT计数器大于或等于LBT失败最大值时，MAC实体触发该服务小区的BWP上的持续LBT失败；以及当触发了持续LBT失败的服务小区是特殊小区时，当收到恢复持续LBT失败检测和恢复的指示，且在该服务小区中的相同载波上配置了物理随机接入信道(PRACH)时机的所有上行BWP都触发了持续LBT失败的情况下，MAC实体向上层指示持续LBT失败。
例如，该恢复持续LBT失败检测与恢复机制，还包括：当RRC切换完成或者当 该终端设备同步到第二小区时，RRC层指示低层恢复持续LBT失败检测和恢复，该第二小区是目标小区。
例如，处理器1210还可以被配置为从第一网络设备接收RRC重配置消息，该RRC重配置消息包括LBT失败检测与恢复相关的配置信息，该第一网络设备是源网络设备。
例如，该LBT失败检测与恢复相关的配置信息包括第一配置信息和/或第二配置信息，该第一配置信息与第一小区的LBT失败检测与恢复相关，该第二配置信息与第二小区的LBT失败检测与恢复相关，该第一小区是属于源网络设备的一个小区，该第二小区是属于目标网络设备的一个小区。
例如，该第一小区可以是属于源网络设备的一个服务小区、主小区、主辅小区或辅小区，该第二小区可以是属于目标网络设备的一个服务小区、主小区、主辅小区或辅小区。
例如，该终端设备的源MAC实体根据该第一小区的LBT失败检测与恢复相关的配置信息，进行第一小区上的持续LBT失败检测与恢复；和/或，该终端设备的目标MAC实体根据该第二小区的LBT失败检测与恢复相关的配置信息，进行第二小区上的持续LBT失败检测与恢复。
在另一个实施方式中，小区切换中的持续LBT失败检测和恢复的装置可以与处理器1210分开配置，例如可以将小区切换中的持续LBT失败检测和恢复的装置配置为与处理器1210连接的芯片，通过处理器1210的控制来实现小区切换中的持续LBT失败检测和恢复的装置的功能。
如图12所示，终端设备1200还可以包括：通信模块1230、输入单元1240、显示器1250、电源1260。值得注意的是，终端设备1200也并不是必须要包括图12中所示的所有部件；此外，终端设备1200还可以包括图12中没有示出的部件，可以参考相关技术。
如图12所示，处理器1210有时也称为控制器或操作控件，可以包括微处理器或其他处理器装置和/或逻辑装置，该处理器1210接收输入并控制终端设备1200的各个部件的操作。
其中，存储器1220，例如可以是缓存器、闪存、硬驱、可移动介质、易失性存储器、非易失性存储器或其它合适装置中的一种或更多种。可储存各种数据，此外还 可存储执行有关信息的程序。并且处理器1210可执行该存储器1220存储的该程序，以实现信息存储或处理等。其他部件的功能与现有类似，此处不再赘述。终端设备1200的各部件可以通过专用硬件、固件、软件或其结合来实现，而不偏离本发明的范围。
由上述实施例可知，在小区切换期间，当收到持续LBT失败指示时，终端设备停止与网络设备的数据发送和/或接收，和/或，在小区切换期间，终端设备挂起持续LBT失败检测和恢复。这样，在小区切换期间，终端设备不会因为持续LBT失败发起连接重建过程，从而避免由此造成的用户服务中断和用户体验的下降。
实施例7
本发明实施例提供了一种网络设备，该网络设备包括如实施例5所述的小区切换中的持续LBT失败检测和恢复的装置。
图13是本发明实施例7的网络设备的系统构成的一示意框图。如图13所示，网络设备1300可以包括：处理器(processor)1310和存储器1320；存储器1320耦合到处理器1310。其中该存储器1320可存储各种数据；此外还存储信息处理的程序1330，并且在处理器1310的控制下执行该程序1330，以接收终端设备发送的各种信息、并且向终端设备发送各种信息。
在一个实施方式中，小区切换中的持续LBT失败检测和恢复的装置的功能可以被集成到处理器1310中。其中，处理器1310可以被配置为：向终端设备发送RRC重配置消息，该RRC重配置消息包括LBT失败检测与恢复相关的配置信息。
例如，该RRC重配置信息还包括接入第二小区所需的信息，该第二小区是目标小区。
例如，该网络设备是源网络设备。
例如，该LBT失败检测与恢复相关的配置信息包括第一配置信息和/或第二配置信息，该第一配置信息与第一小区的LBT失败检测与恢复相关，该第二配置信息与第二小区的LBT失败检测与恢复相关，该第一小区是属于源网络设备的一个小区，该第二小区是属于目标网络设备的一个小区。
例如，该第一小区可以是属于源网络设备的一个服务小区、主小区、主辅小区或辅小区，该第二小区可以是属于目标网络设备的一个服务小区、主小区、主辅小区或辅小区。
例如，该第一小区的LBT失败检测与恢复相关的配置信息用于该终端设备的源MAC实体进行第一小区上的持续LBT失败检测与恢复，和/或，该第二小区的LBT失败检测与恢复相关的配置信息用于该终端设备的目标MAC实体进行第二小区上的持续LBT失败检测与恢复。
在另一个实施方式中，小区切换中的持续LBT失败检测和恢复的装置可以与处理器1310分开配置，例如可以将小区切换中的持续LBT失败检测和恢复的装置配置为与处理器1310连接的芯片，通过处理器1310的控制来实现小区切换中的持续LBT失败检测和恢复的装置的功能。
此外，如图13所示，网络设备1300还可以包括：收发机1340和天线1350等；其中，上述部件的功能与现有技术类似，此处不再赘述。值得注意的是，网络设备1300也并不是必须要包括图13中所示的所有部件；此外，网络设备1300还可以包括图13中没有示出的部件，可以参考现有技术。
由上述实施例可知，网络设备向终端设备发送包括LBT失败检测与恢复相关的配置信息的RRC重配置消息，使得终端设备能够根据该LBT失败检测与恢复相关的配置信息进行持续LBT失败检测。
实施例8
本申请实施例提供了一种通信系统，包括根据实施例7所述的终端设备和/或根据实施例8所述的网络设备。
例如，该通信系统的结构可以参照图1，如图1所示，通信系统100包括第一网络设备101、第二网络设备102和终端设备103，终端设备103与实施例7中记载的终端设备相同，第一网络设备101与实施例7中记载的网络设备相同，重复的内容不再赘述。
本发明以上的装置和方法可以由硬件实现，也可以由硬件结合软件实现。本发明涉及这样的计算机可读程序，当该程序被逻辑部件所执行时，能够使该逻辑部件实现上文所述的装置或构成部件，或使该逻辑部件实现上文所述的各种方法或步骤。逻辑部件例如现场可编程逻辑部件、微处理器、计算机中使用的处理器等。本发明还涉及用于存储以上程序的存储介质，如硬盘、磁盘、光盘、DVD、flash存储器等。
结合本申请实施例描述的方法/装置可直接体现为硬件、由处理器执行的软件模块或二者组合。例如，图11中所示的功能框图中的一个或多个和/或功能框图的一个 或多个组合，既可以对应于计算机程序流程的各个软件模块，亦可以对应于各个硬件模块。这些软件模块，可以分别对应于图3或图4中所示的各个步骤。这些硬件模块例如可利用现场可编程门阵列(FPGA)将这些软件模块固化而实现。
软件模块可以位于RAM存储器、闪存、ROM存储器、EPROM存储器、EEPROM存储器、寄存器、硬盘、移动磁盘、CD-ROM或者本领域已知的任何其它形式的存储介质。可以将一种存储介质耦接至处理器，从而使处理器能够从该存储介质读取信息，且可向该存储介质写入信息；或者该存储介质可以是处理器的组成部分。处理器和存储介质可以位于ASIC中。该软件模块可以存储在移动终端的存储器中，也可以存储在可插入移动终端的存储卡中。例如，若设备(如移动终端)采用的是较大容量的MEGA-SIM卡或者大容量的闪存装置，则该软件模块可存储在该MEGA-SIM卡或者大容量的闪存装置中。
针对附图11中描述的功能方框中的一个或多个和/或功能方框的一个或多个组合，可以实现为用于执行本发明所描述功能的通用处理器、数字信号处理器(DSP)、专用集成电路(ASIC)、现场可编程门阵列(FPGA)或者其它可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件或者其任意适当组合。针对附图11描述的功能方框中的一个或多个和/或功能方框的一个或多个组合，还可以实现为计算设备的组合，例如，DSP和微处理器的组合、多个微处理器、与DSP通信结合的一个或多个微处理器或者任何其它这种配置。
以上结合具体的实施方式对本发明进行了描述，但本领域技术人员应该清楚，这些描述都是示例性的，并不是对本发明保护范围的限制。本领域技术人员可以根据本发明的精神和原理对本发明做出各种变型和修改，这些变型和修改也在本发明的范围内。
根据本申请实施例公开的各种实施方式，还公开了如下附记：
附记一、
1、一种小区切换中的持续LBT失败检测与恢复的装置，所述装置应用于终端设备，所述装置包括：
第一处理单元，其用于在小区切换期间，收到持续LBT失败指示；并且，停止与网络设备的数据发送和/或接收，和/或，
第二处理单元，其用于在小区切换期间，挂起持续LBT失败检测与恢复。
2、根据附记1所述的装置，其中，所述小区切换包括：
双活动协议栈(DAPS)切换，或者，
双活动协议栈(DAPS)切换和非DAPS切换，或者，
非DAPS切换。
3、根据附记1或2所述的装置，其中，
所述装置在小区切换期间，当收到持续LBT失败指示时，和/或，当停止与网络设备的数据发送和/或接收时，挂起持续LBT失败检测与恢复。
4、根据附记1或2所述的装置，其中，
所述小区切换是双活动协议栈(DAPS)切换，
所述第一处理单元用于在小区切换期间，收到持续LBT失败指示；以及停止与第一网络设备的数据发送和接收，和/或，
所述第二处理单元用于在小区切换期间，挂起所述终端设备对目标小区的持续LBT失败检测与恢复，
所述第一网络设备是源网络设备。
5、根据附记1-4中任一项所述的装置，其中，
收到的所述持续LBT失败指示来自所述终端设备的MAC层。
6、根据附记5所述的装置，其中，收到的所述持续LBT失败指示来自所述终端设备的MAC层，包括：
收到的所述持续LBT失败指示来自所述终端设备的源MAC实体、目标MAC实体以及MCG MAC实体中的至少一个。
7、根据附记1-6中的任一项所述的装置，其中，所述第一处理单元停止与网络设备的数据发送和/或接收，包括以下的至少一个：
停止与第一网络设备的数据发送和/或接收；
停止与第二网络设备的除随机接入相关传输的数据以外的数据发送和/或接收；以及
停止与MCG网络设备的数据发送和/或接收，
所述第一网络设备是源网络设备，所述第二网络设备是目标网络设备。
8、根据附记1-7中的任一项所述的装置，其中，所述装置还包括以下单元中的至少一个：
保持单元，其用于所述终端设备保持在RRC连接状态；
释放单元，其用于所述终端设备释放与第一网络设备的连接；
维持单元，其用于所述终端设备维持第一网络设备的RRC配置；以及
认为单元，其用于所述终端设备认为与第一网络设备的无线链路失败，
所述第一网络设备是源网络设备。
9、根据附记1-8中的任一项所述的装置，其中，所述第二处理单元用于，
在小区切换期间，挂起所述终端设备对第一小区和/或第二小区的持续LBT失败检测与恢复，
所述第一小区属于第一网络设备，所述第二小区属于第二网络设备，
所述第一网络设备是源网络设备，所述第二网络设备是目标网络设备。
10、根据附记9所述的装置，其中，
所述第一小区是服务小区或者主小区或者主辅小区或者辅小区，和/或，
所述第二小区是服务小区或者主小区或者主辅小区或者辅小区。
11、根据附记1-10中的任一项所述的装置，其中，所述第二处理单元挂起持续LBT失败检测与恢复，包括以下的至少一个：
物理层停止向MAC层指示LBT失败；
MAC层不触发持续LBT失败；
MAC层不向上层指示持续LBT失败；
收到持续LBT失败指示且用于小区切换的定时器未运行，认为无线链路失败；或者，所述定时器运行，且收到持续LBT失败指示，不认为无线链路失败或忽略所述持续LBT失败指示；以及
发生无线链路失败，且用于小区切换的定时器未运行，并发起连接重建；或者，所述定时器运行，且发生无线链路失败，不发起连接重建。
12、根据附记1-11中的任一项所述的装置，其中，所述装置还包括以下单元中的至少一个：
第一指示单元，其用于在没有收到挂起持续LBT失败检测与恢复的指示且LBT失败的情况下，物理层向MAC层指示LBT失败；
第一触发单元，其用于对于配置了LBT失败恢复配置参数的服务小区，在没有收到来自挂起持续LBT失败检测与恢复的指示且收到了来自低层的LBT失败指示且LBT计数器大于或等于LBT失败最大值时，MAC实体触发所述服务小区的BWP上 的持续LBT失败；以及
第二指示单元，其用于当触发了持续LBT失败的服务小区是特殊小区时，在没有收到挂起持续LBT失败检测与恢复的指示且在所述服务小区中的相同载波上配置了物理随机接入信道(PRACH)时机的所有上行BWP都触发了持续LBT失败的情况下，MAC实体向上层指示持续LBT失败。
13、根据附记1-12中的任一项所述的装置，其中，所述第二处理单元还用于：
RRC层指示低层挂起持续LBT失败检测和恢复。
14、根据附记13所述的装置，其中，
为了执行同步的重配，或者，当用于小区切换的定时器启动时，RRC层指示低层挂起持续LBT失败检测和恢复。
15、根据附记13或14所述的装置，其中，
所述低层是物理层和/或MAC层。
16、根据附记1-15中的任一项所述的装置，其中，所述装置还包括：
切换完成单元，其用于小区切换完成；以及
恢复单元，其用于恢复持续LBT失败检测与恢复机制。
17、根据附记16所述的装置，其中，所述恢复单元恢复持续LBT失败检测与恢复机制，包括以下的至少一个：
当收到恢复持续LBT失败检测和恢复的指示且LBT失败时，物理层向MAC层指示LBT失败；
对于配置了LBT失败恢复配置参数的服务小区，当收到恢复持续LBT失败检测和恢复的指示且收到了来自低层的LBT失败指示且LBT计数器大于或等于LBT失败最大值时，MAC实体触发所述服务小区的BWP上的持续LBT失败；以及
当触发了持续LBT失败的服务小区是特殊小区时，当收到恢复持续LBT失败检测和恢复的指示，且在所述服务小区中的相同载波上配置了物理随机接入信道(PRACH)时机的所有上行BWP都触发了持续LBT失败的情况下，MAC实体向上层指示持续LBT失败。
18、根据附记16或17所述的装置，其中，所述恢复单元恢复持续LBT失败检测与恢复机制，还包括：
当RRC切换完成或者当所述终端设备同步到第二小区时，RRC层指示低层恢复 持续LBT失败检测和恢复，所述第二小区是目标小区。
19、根据附记1-18中的任一项所述的装置，其中，所述装置还包括：
第一接收单元，其用于从第一网络设备接收RRC重配置消息，所述RRC重配置消息包括LBT失败检测与恢复相关的配置信息，所述第一网络设备是源网络设备。
20、根据附记19所述的装置，其中，
所述LBT失败检测与恢复相关的配置信息包括第一配置信息和/或第二配置信息，所述第一配置信息与第一小区的LBT失败检测与恢复相关，所述第二配置信息与第二小区的LBT失败检测与恢复相关，
所述第一小区是属于源网络设备的一个小区，所述第二小区是属于目标网络设备的一个小区。
21、根据附记20所述的装置，其中，
所述终端设备的源MAC实体根据所述第一配置信息，进行第一小区上的持续LBT失败检测与恢复；和/或，
所述终端设备的目标MAC实体根据所述第二配置信息，进行第二小区上的持续LBT失败检测与恢复。
22、一种小区切换中的持续LBT失败检测与恢复的装置，所述装置应用于终端设备，所述装置包括：
第三处理单元，其用于在小区切换期间，当收到持续LBT失败指示时，停止与网络设备的数据发送和/或接收，和/或，
第四处理单元，其用于在小区切换期间，挂起持续LBT失败检测与恢复。
23、根据附记22所述的装置，其中，所述小区切换包括：
双活动协议栈(DAPS)切换，或者，
双活动协议栈(DAPS)切换和非DAPS切换，或者，
非DAPS切换。
24、根据附记22或23所述的装置，其中，
所述装置用于在小区切换期间，当收到持续LBT失败指示时，和/或，当停止与网络设备的数据发送和/或接收时，挂起持续LBT失败检测与恢复。
25、根据附记22或23所述的装置，其中，
所述小区切换是双活动协议栈(DAPS)切换，
在小区切换期间，当收到持续LBT失败指示时，停止与第一网络设备的数据发送和接收，和/或，
在小区切换期间，挂起所述第二终端设备对目标小区的持续LBT失败检测与恢复，
所述第一网络设备是源网络设备。
26、根据附记22-25中任一项所述的装置，其中，
收到的所述持续LBT失败指示来自所述终端设备的MAC层。
27、根据附记26所述的装置，其中，收到的所述持续LBT失败指示来自所述终端设备的MAC层，包括：
收到的所述持续LBT失败指示来自所述终端设备的源MAC实体、目标MAC实体以及MCG MAC实体中的至少一个。
28、根据附记22-27中的任一项所述的装置，其中，所述第三处理单元停止与网络设备的数据发送和/或接收，包括以下的至少一个：
停止与第一网络设备的数据发送和/或接收；
停止与第二网络设备的除随机接入相关传输的数据以外的数据发送和/或接收；以及
停止与MCG网络设备的数据发送和/或接收，
所述第一网络设备是源网络设备，所述第二网络设备是目标网络设备。
29、根据附记22-28中的任一项所述的装置，其中，所述装置还包括以下单元中的至少一个：
保持单元，其用于所述终端设备保持在RRC连接状态；
释放单元，其用于所述终端设备释放与第一网络设备的连接；
维持单元，其用于所述终端设备维持第一网络设备的RRC配置；以及
认为单元，其用于所述终端设备认为与第一网络设备的无线链路失败，
所述第一网络设备是源网络设备。
30、根据附记22-29中的任一项所述的装置，其中，所述第四处理单元用于：
在小区切换期间，挂起所述终端设备对第一小区和/或第二小区的持续LBT失败检测与恢复，
所述第一小区属于第一网络设备，所述第二小区属于第二网络设备，
所述第一网络设备是源网络设备，所述第二网络设备是目标网络设备。
31、根据附记30所述的装置，其中，
所述第一小区是服务小区或者主小区或者主辅小区或者辅小区，和/或，
所述第二小区是服务小区或者主小区或者主辅小区或者辅小区。
32、根据附记22-31中的任一项所述的装置，其中，所述第四处理单元挂起持续LBT失败检测与恢复，包括以下的至少一个：
物理层停止向MAC层指示LBT失败；
MAC层不触发持续LBT失败；
MAC层不向上层指示持续LBT失败；
收到持续LBT失败指示且用于小区切换的定时器未运行，认为无线链路失败；或者，所述定时器运行，且收到持续LBT失败指示，不认为无线链路失败或忽略所述持续LBT失败指示；以及
发生无线链路失败，且用于小区切换的定时器未运行，并发起连接重建；或者，所述定时器运行，且发生无线链路失败，不发起连接重建。
33、根据附记22-32中的任一项所述的装置，其中，所述装置还包括以下单元中的至少一个：
第一指示单元，其用于在没有收到挂起持续LBT失败检测与恢复的指示且LBT失败的情况下，物理层向MAC层指示LBT失败；
第一触发单元，其用于对于配置了LBT失败恢复配置参数的服务小区，在没有收到来自挂起持续LBT失败检测与恢复的指示且收到了来自低层的LBT失败指示且LBT计数器大于或等于LBT失败最大值时，MAC实体触发所述服务小区的BWP上的持续LBT失败；以及
第二指示单元，其用于当触发了持续LBT失败的服务小区是特殊小区时，在没有收到挂起持续LBT失败检测与恢复的指示且在所述服务小区中的相同载波上配置了物理随机接入信道(PRACH)时机的所有上行BWP都触发了持续LBT失败的情况下，MAC实体向上层指示持续LBT失败。
34、根据附记22-33中的任一项所述的装置，其中，所述第四处理单元还用于：
RRC层指示低层挂起持续LBT失败检测和恢复。
35、根据附记34所述的装置，其中，
为了执行同步的重配，或者，当用于小区切换的定时器启动时，RRC层指示低层挂起持续LBT失败检测和恢复。
36、根据附记34或35所述的装置，其中，
所述低层是物理层和/或MAC层。
37、根据附记22-36中的任一项所述的装置，其中，所述装置还包括：
切换完成单元，其用于小区切换完成；以及
恢复单元，其用于恢复持续LBT失败检测与恢复机制。
38、根据附记37所述的装置，其中，所述恢复单元恢复持续LBT失败检测与恢复机制，包括以下的至少一个：
当收到恢复持续LBT失败检测和恢复的指示且LBT失败时，物理层向MAC层指示LBT失败；
对于配置了LBT失败恢复配置参数的服务小区，当收到恢复持续LBT失败检测和恢复的指示且收到了来自低层的LBT失败指示且LBT计数器大于或等于LBT失败最大值时，MAC实体触发所述服务小区的BWP上的持续LBT失败；以及
当触发了持续LBT失败的服务小区是特殊小区时，当收到恢复持续LBT失败检测和恢复的指示，且在所述服务小区中的相同载波上配置了物理随机接入信道(PRACH)时机的所有上行BWP都触发了持续LBT失败的情况下，MAC实体向上层指示持续LBT失败。
39、根据附记37或38所述的装置，其中，所述恢复单元恢复持续LBT失败检测与恢复机制，还包括：
当RRC切换完成或者当所述终端设备同步到第二小区时，RRC层指示低层恢复持续LBT失败检测和恢复，所述第二小区是目标小区。
40、根据附记22-39中的任一项所述的装置，其中，所述装置还包括：
第一接收单元，其用于从第一网络设备接收RRC重配置消息，所述RRC重配置消息包括LBT失败检测与恢复相关的配置信息，所述第一网络设备是源网络设备。
41、根据附记40所述的装置，其中，
所述LBT失败检测与恢复相关的配置信息包括第一配置信息和/或第二配置信息，所述第一配置信息与第一小区的LBT失败检测与恢复相关，所述第二配置信息与第二小区的LBT失败检测与恢复相关，
所述第一小区是属于源网络设备的一个小区，所述第二小区是属于目标网络设备的一个小区。
42、根据附记41所述的装置，其中，
所述终端设备的源MAC实体根据所述第一配置信息，进行第一小区上的持续LBT失败检测与恢复；和/或，
所述终端设备的目标MAC实体根据所述第二配置信息，进行第二小区上的持续LBT失败检测与恢复。
43、一种小区切换中的持续LBT失败检测与恢复的装置，所述装置应用于网络设备，所述装置包括：
第一发送单元，其用于向终端设备发送RRC重配置消息，所述RRC重配置消息包括LBT失败检测与恢复相关的配置信息。
44、根据附记43所述的装置，其中，
所述RRC重配置信息还包括接入第二小区所需的信息，所述第二小区是目标小区。
45、根据附记43或44所述的装置，其中，
所述网络设备是源网络设备。
46、根据附记43-45中的任一项所述的装置，其中，
所述LBT失败检测与恢复相关的配置信息包括第一配置信息和/或第二配置信息，所述第一配置信息与第一小区的LBT失败检测与恢复相关，所述第二配置信息与第二小区的LBT失败检测与恢复相关，
所述第一小区是属于源网络设备的一个小区，所述第二小区是属于目标网络设备的一个小区。
47、根据附记46所述的装置，其中，
所述第一配置信息用于所述终端设备的源MAC实体进行第一小区上的持续LBT失败检测与恢复，和/或，
所述第二配置信息用于所述终端设备的目标MAC实体进行第二小区上的持续LBT失败检测与恢复。
48、根据附记43-47中的任一项所述的装置，其中，所述装置还包括：
第二接收单元，其用于接收从第二网络设备发送的切换请求确认消息，所述第二 网络设备是目标网络设备。
49、根据附记48所述的装置，其中，
所述切换请求确认消息包括接入目标小区所需的信息以及与LBT失败检测和恢复相关的配置信息，所述与LBT失败检测和恢复相关的配置信息是所述终端设备对目标网络设备中的小区进行持续LBT失败检测与恢复的配置信息。
50、一种终端设备，所述终端设备包括根据附记1-42中的任一项所述的装置。
51、一种网络设备，所述网络设备包括根据附记43-49中的任一项所述的装置。
52、一种通信系统，所述通信系统包括根据附记50所述的终端设备和/或根据附记51所述的网络设备。
附记二、
1、一种小区切换中的持续LBT失败检测与恢复的方法，所述方法应用于终端设备，所述方法包括：
在小区切换期间，收到持续LBT失败指示；并且，停止与网络设备的数据发送和/或接收，和/或，
在小区切换期间，挂起持续LBT失败检测与恢复。
2、根据附记1所述的方法，其中，所述小区切换包括：
双活动协议栈(DAPS)切换，或者，
双活动协议栈(DAPS)切换和非DAPS切换，或者，
非DAPS切换。
3、根据附记1或2所述的方法，其中，
在小区切换期间，当收到持续LBT失败指示时，和/或，当停止与网络设备的数据发送和/或接收时，挂起持续LBT失败检测与恢复。
4、根据附记1或2所述的方法，其中，
所述小区切换是双活动协议栈(DAPS)切换，
在小区切换期间，收到持续LBT失败指示；以及停止与第一网络设备的数据发送和接收，和/或，
在小区切换期间，挂起所述终端设备对目标小区的持续LBT失败检测与恢复，
所述第一网络设备是源网络设备。
5、根据附记1-4中任一项所述的方法，其中，
所述持续LBT失败指示来自所述终端设备的MAC层。
6、根据附记5所述的方法，其中，所述持续LBT失败指示来自所述终端设备的MAC层，包括：
所述持续LBT失败指示来自所述终端设备的源MAC实体、目标MAC实体以及MCG MAC实体中的至少一个。
7、根据附记1-3、5-6中的任一项所述的方法，其中，所述停止与网络设备的数据发送和/或接收，包括以下的至少一个：
停止与第一网络设备的数据发送和/或接收；
停止与第二网络设备的除随机接入相关传输的数据以外的数据发送和/或接收；以及
停止与MCG网络设备的数据发送和/或接收，
所述第一网络设备是源网络设备，所述第二网络设备是目标网络设备。
8、根据附记1-7中的任一项所述的方法，其中，所述方法还包括以下步骤中的至少一个：
所述终端设备保持在RRC连接状态；
所述终端设备释放与第一网络设备的连接；
所述终端设备维持第一网络设备的RRC配置；以及
所述终端设备认为与第一网络设备的无线链路失败，
所述第一网络设备是源网络设备。
9、根据附记1-3、5-8中的任一项所述的方法，其中，在小区切换期间，挂起持续LBT失败检测与恢复，包括：
在小区切换期间，挂起所述终端设备对第一小区和/或第二小区的持续LBT失败检测与恢复，
所述第一小区属于第一网络设备，所述第二小区属于第二网络设备，
所述第一网络设备是源网络设备，所述第二网络设备是目标网络设备。
10、根据附记9所述的方法，其中，
所述第一小区是服务小区或者主小区或者主辅小区或者辅小区，和/或，
所述第二小区是服务小区或者主小区或者主辅小区或者辅小区。
11、根据附记1-10中的任一项所述的方法，其中，所述挂起持续LBT失败检测 与恢复，包括以下的至少一个：
物理层停止向MAC层指示LBT失败；
MAC层不触发持续LBT失败；
MAC层不向上层指示持续LBT失败；
收到持续LBT失败指示且用于小区切换的定时器未运行，认为无线链路失败；或者，所述定时器运行，且收到持续LBT失败指示，不认为无线链路失败或忽略所述持续LBT失败指示；以及
发生无线链路失败，且用于小区切换的定时器未运行，并发起连接重建；或者，所述定时器运行，且发生无线链路失败，不发起连接重建。
12、根据附记1-11中的任一项所述的方法，其中，所述方法还包括以下步骤中的至少一个：
在没有收到挂起持续LBT失败检测与恢复的指示且LBT失败的情况下，物理层向MAC层指示LBT失败；
对于配置了LBT失败恢复配置参数的服务小区，在没有收到来自挂起持续LBT失败检测与恢复的指示且收到了来自低层的LBT失败指示且LBT计数器大于或等于LBT失败最大值时，MAC实体触发所述服务小区的BWP上的持续LBT失败；以及
当触发了持续LBT失败的服务小区是特殊小区时，在没有收到挂起持续LBT失败检测与恢复的指示且在所述服务小区中的相同载波上配置了物理随机接入信道(PRACH)时机的所有上行BWP都触发了持续LBT失败的情况下，MAC实体向上层指示持续LBT失败。
13、根据附记1-12中的任一项所述的方法，其中，所述挂起持续LBT失败检测与恢复，还包括：
RRC层指示低层挂起持续LBT失败检测和恢复。
14、根据附记13所述的方法，其中，
为了执行同步的重配，或者，当用于小区切换的定时器启动时，RRC层指示低层挂起持续LBT失败检测和恢复。
15、根据附记13或14所述的方法，其中，
所述低层是物理层和/或MAC层。
16、根据附记1-15中的任一项所述的方法，其中，所述方法还包括：
小区切换完成，并且，恢复持续LBT失败检测与恢复机制。
17、根据附记16所述的方法，其中，所述恢复持续LBT失败检测与恢复机制，包括以下的至少一个：
当收到恢复持续LBT失败检测和恢复的指示且LBT失败时，物理层向MAC层指示LBT失败；
对于配置了LBT失败恢复配置参数的服务小区，当收到恢复持续LBT失败检测和恢复的指示且收到了来自低层的LBT失败指示且LBT计数器大于或等于LBT失败最大值时，MAC实体触发所述服务小区的BWP上的持续LBT失败；以及
当触发了持续LBT失败的服务小区是特殊小区时，当收到恢复持续LBT失败检测和恢复的指示，且在所述服务小区中的相同载波上配置了物理随机接入信道(PRACH)时机的所有上行BWP都触发了持续LBT失败的情况下，MAC实体向上层指示持续LBT失败。
18、根据附记16或17所述的方法，其中，所述恢复持续LBT失败检测与恢复机制，还包括：
当RRC切换完成或者当所述终端设备同步到第二小区时，RRC层指示低层恢复持续LBT失败检测和恢复，所述第二小区是目标小区。
19、根据附记1-18中的任一项所述的方法，其中，所述方法还包括：
从第一网络设备接收RRC重配置消息，所述RRC重配置消息包括LBT失败检测与恢复相关的配置信息，所述第一网络设备是源网络设备。
20、根据附记19所述的方法，其中，
所述LBT失败检测与恢复相关的配置信息包括第一配置信息和/或第二配置信息，所述第一配置信息与第一小区的LBT失败检测与恢复相关，所述第二配置信息与第二小区的LBT失败检测与恢复相关，
所述第一小区是属于源网络设备的一个小区，所述第二小区是属于目标网络设备的一个小区。
21、根据附记20所述的方法，其中，
所述终端设备的源MAC实体根据所述第一配置信息，进行第一小区上的持续LBT失败检测与恢复；和/或，
所述终端设备的目标MAC实体根据所述第二配置信息，进行第二小区上的持续 LBT失败检测与恢复。
22、一种小区切换中的持续LBT失败检测与恢复的方法，所述方法应用于终端设备，所述方法包括：
在小区切换期间，当收到持续LBT失败指示时，停止与网络设备的数据发送和/或接收，和/或，
在小区切换期间，挂起持续LBT失败检测与恢复。
23、根据附记22所述的方法，其中，所述小区切换包括：
双活动协议栈(DAPS)切换，或者，
双活动协议栈(DAPS)切换和非DAPS切换，或者，
非DAPS切换。
24、根据附记22或23所述的方法，其中，
在小区切换期间，当收到持续LBT失败指示时，和/或，当停止与网络设备的数据发送和/或接收时，挂起持续LBT失败检测与恢复。
25、根据附记22或23所述的方法，其中，
所述小区切换是双活动协议栈(DAPS)切换，
在小区切换期间，当收到持续LBT失败指示时，停止与第一网络设备的数据发送和接收，和/或，
在小区切换期间，挂起所述终端设备对目标小区的持续LBT失败检测与恢复，
所述第一网络设备是源网络设备。
26、根据附记22-25中任一项所述的方法，其中，
收到的所述持续LBT失败指示来自所述终端设备的MAC层。
27、根据附记26所述的方法，其中，收到的所述持续LBT失败指示来自所述终端设备的MAC层，包括：
收到的所述持续LBT失败指示来自所述终端设备的源MAC实体、目标MAC实体以及MCG MAC实体中的至少一个。
28、根据附记22-27中的任一项所述的方法，其中，所述停止与网络设备的数据发送和/或接收，包括以下的至少一个：
停止与第一网络设备的数据发送和/或接收；
停止与第二网络设备的除随机接入相关传输的数据以外的数据发送和/或接收； 以及
停止与MCG网络设备的数据发送和/或接收，
所述第一网络设备是源网络设备，所述第二网络设备是目标网络设备。
29、根据附记22-28中的任一项所述的方法，其中，所述方法还包括以下步骤中的至少一个：
所述终端设备保持在RRC连接状态；
所述终端设备释放与第一网络设备的连接；
所述终端设备维持第一网络设备的RRC配置；以及
所述终端设备认为与第一网络设备的无线链路失败，
所述第一网络设备是源网络设备。
30、根据附记22-29中的任一项所述的方法，其中，在小区切换期间，挂起持续LBT失败检测与恢复，包括：
在小区切换期间，挂起所述终端设备对第一小区和/或第二小区的持续LBT失败检测与恢复，
所述第一小区属于第一网络设备，所述第二小区属于第二网络设备，
所述第一网络设备是源网络设备，所述第二网络设备是目标网络设备。
31、根据附记30所述的方法，其中，
所述第一小区是服务小区或者主小区或者主辅小区或者辅小区，和/或，
所述第二小区是服务小区或者主小区或者主辅小区或者辅小区。
32、根据附记22-31中的任一项所述的方法，其中，所述挂起持续LBT失败检测与恢复，包括以下的至少一个：
物理层停止向MAC层指示LBT失败；
MAC层不触发持续LBT失败；
MAC层不向上层指示持续LBT失败；
收到持续LBT失败指示且用于小区切换的定时器未运行，认为无线链路失败；或者，所述定时器运行，且收到持续LBT失败指示，不认为无线链路失败或忽略所述持续LBT失败指示；以及
发生无线链路失败，且用于小区切换的定时器未运行，并发起连接重建；或者，所述定时器运行，且发生无线链路失败，不发起连接重建。
33、根据附记22-32中的任一项所述的方法，其中，所述方法还包括以下步骤中的至少一个：
在没有收到挂起持续LBT失败检测与恢复的指示且LBT失败的情况下，物理层向MAC层指示LBT失败；
对于配置了LBT失败恢复配置参数的服务小区，在没有收到来自挂起持续LBT失败检测与恢复的指示且收到了来自低层的LBT失败指示且LBT计数器大于或等于LBT失败最大值时，MAC实体触发所述服务小区的BWP上的持续LBT失败；以及
当触发了持续LBT失败的服务小区是特殊小区时，在没有收到挂起持续LBT失败检测与恢复的指示且在所述服务小区中的相同载波上配置了物理随机接入信道(PRACH)时机的所有上行BWP都触发了持续LBT失败的情况下，MAC实体向上层指示持续LBT失败。
34、根据附记22-33中的任一项所述的方法，其中，所述挂起持续LBT失败检测与恢复，还包括：
RRC层指示低层挂起持续LBT失败检测和恢复。
35、根据附记34所述的方法，其中，
为了执行同步的重配，或者，当用于小区切换的定时器启动时，RRC层指示低层挂起持续LBT失败检测和恢复。
36、根据附记34或35所述的方法，其中，
所述低层是物理层和/或MAC层。
37、根据附记22-36中的任一项所述的方法，其中，所述方法还包括：
在小区切换完成时，恢复持续LBT失败检测与恢复机制。
38、根据附记37所述的方法，其中，所述恢复持续LBT失败检测与恢复机制，包括以下的至少一个：
当收到恢复持续LBT失败检测和恢复的指示且LBT失败时，物理层向MAC层指示LBT失败；
对于配置了LBT失败恢复配置参数的服务小区，当收到恢复持续LBT失败检测和恢复的指示且收到了来自低层的LBT失败指示且LBT计数器大于或等于LBT失败最大值时，MAC实体触发所述服务小区的BWP上的持续LBT失败；以及
当触发了持续LBT失败的服务小区是特殊小区时，当收到恢复持续LBT失败检 测和恢复的指示，且在所述服务小区中的相同载波上配置了物理随机接入信道(PRACH)时机的所有上行BWP都触发了持续LBT失败的情况下，MAC实体向上层指示持续LBT失败。
39、根据附记37或38所述的方法，其中，所述恢复持续LBT失败检测与恢复机制，还包括：
当RRC切换完成或者当所述终端设备同步到第二小区时，RRC层指示低层恢复持续LBT失败检测和恢复，所述第二小区是目标小区。
40、根据附记22-39中的任一项所述的方法，其中，所述方法还包括：
从第一网络设备接收RRC重配置消息，所述RRC重配置消息包括LBT失败检测与恢复相关的配置信息，所述第一网络设备是源网络设备。
41、根据附记40所述的方法，其中，
所述LBT失败检测与恢复相关的配置信息包括第一配置信息和/或第二配置信息，所述第一配置信息与第一小区的LBT失败检测与恢复相关，所述第二配置信息与第二小区的LBT失败检测与恢复相关，
所述第一小区是属于源网络设备的一个小区，所述第二小区是属于目标网络设备的一个小区。
42、根据附记41所述的方法，其中，
所述终端设备的源MAC实体根据所述第一配置信息，进行第一小区上的持续LBT失败检测与恢复；和/或，
所述终端设备的目标MAC实体根据所述第二配置信息，进行第二小区上的持续LBT失败检测与恢复。
43、一种小区切换中的持续LBT失败检测与恢复的方法，所述方法应用于网络设备，所述方法包括：
向终端设备发送RRC重配置消息，所述RRC重配置消息包括LBT失败检测与恢复相关的配置信息。
44、根据附记43所述的方法，其中，
所述RRC重配置信息还包括接入第二小区所需的信息，所述第二小区是目标小区。
45、根据附记43或44所述的方法，其中，
所述网络设备是源网络设备。
46、根据附记43-45中的任一项所述的方法，其中，
所述LBT失败检测与恢复相关的配置信息包括包括第一配置信息和/或第二配置信息，所述第一配置信息与第一小区的LBT失败检测与恢复相关，所述第二配置信息与第二小区的LBT失败检测与恢复相关，
所述第一小区是属于源网络设备的一个小区，所述第二小区是属于目标网络设备的一个小区。
47、根据附记46所述的方法，其中，
所述第一配置信息用于所述终端设备的源MAC实体进行第一小区上的持续LBT失败检测与恢复，和/或，
所述第二配置信息用于所述终端设备的目标MAC实体进行第二小区上的持续LBT失败检测与恢复。
48、根据附记43-47中的任一项所述的方法，其中，所述方法还包括：
接收从第二网络设备发送的切换请求确认消息，所述第二网络设备是目标网络设备。
49、根据附记48所述的方法，其中，
所述切换请求确认消息包括接入目标小区所需的信息以及与LBT失败检测和恢复相关的配置信息，所述与LBT失败检测和恢复相关的配置信息是所述终端设备对目标网络设备中的小区进行持续LBT失败检测与恢复的配置信息。

Claims (20)

  1. 一种小区切换中的持续LBT失败检测与恢复的装置，所述装置应用于终端设备，所述装置包括：
    第一处理单元，其用于在小区切换期间，收到持续LBT失败指示；并且，停止与网络设备的数据发送和/或接收，和/或，
    第二处理单元，其用于在小区切换期间，挂起持续LBT失败检测与恢复。
  2. 根据权利要求1所述的装置，其中，所述小区切换包括：
    双活动协议栈(DAPS)切换，或者，
    双活动协议栈(DAPS)切换和非DAPS切换，或者，
    非DAPS切换。
  3. 根据权利要求1所述的装置，其中，
    所述小区切换是双活动协议栈(DAPS)切换，
    所述第一处理单元用于在小区切换期间，收到持续LBT失败指示；以及停止与第一网络设备的数据发送和接收，和/或，
    所述第二处理单元用于在小区切换期间，挂起所述终端设备对目标小区的持续LBT失败检测与恢复，
    所述第一网络设备是源网络设备。
  4. 根据权利要求1所述的装置，其中，
    收到的所述持续LBT失败指示来自所述终端设备的MAC层。
  5. 根据权利要求4所述的装置，其中，收到的所述持续LBT失败指示来自所述终端设备的MAC层，包括：
    收到的所述持续LBT失败指示来自所述终端设备的源MAC实体、目标MAC实体以及MCG MAC实体中的至少一个。
  6. 根据权利要求1所述的装置，其中，所述第一处理单元停止与网络设备的数据发送和/或接收，包括以下的至少一个：
    停止与第一网络设备的数据发送和/或接收；
    停止与第二网络设备的除随机接入相关传输的数据以外的数据发送和/或接收； 以及
    停止与MCG网络设备的数据发送和/或接收，
    所述第一网络设备是源网络设备，所述第二网络设备是目标网络设备。
  7. 根据权利要求1所述的装置，其中，所述第二处理单元用于，
    在小区切换期间，挂起所述终端设备对第一小区和/或第二小区的持续LBT失败检测与恢复，
    所述第一小区属于第一网络设备，所述第二小区属于第二网络设备，
    所述第一网络设备是源网络设备，所述第二网络设备是目标网络设备。
  8. 根据权利要求7所述的装置，其中，
    所述第一小区是服务小区或者主小区或者主辅小区或者辅小区，和/或，
    所述第二小区是服务小区或者主小区或者主辅小区或者辅小区。
  9. 根据权利要求1所述的装置，其中，所述第二处理单元挂起持续LBT失败检测与恢复，包括以下的至少一个：
    物理层停止向MAC层指示LBT失败；
    MAC层不触发持续LBT失败；
    MAC层不向上层指示持续LBT失败；
    收到持续LBT失败指示且用于小区切换的定时器未运行，认为无线链路失败；或者，所述定时器运行，且收到持续LBT失败指示，不认为无线链路失败或忽略所述持续LBT失败指示；以及
    发生无线链路失败，且用于小区切换的定时器未运行，并发起连接重建；或者，所述定时器运行，且发生无线链路失败，不发起连接重建。
  10. 根据权利要求1所述的装置，其中，所述装置还包括：
    切换完成单元，其用于小区切换完成；以及
    恢复单元，其用于恢复持续LBT失败检测与恢复机制。
  11. 根据权利要求10所述的装置，其中，所述恢复单元恢复持续LBT失败检测与恢复机制，包括以下的至少一个：
    当收到恢复持续LBT失败检测和恢复的指示且LBT失败时，物理层向MAC层指示LBT失败；
    对于配置了LBT失败恢复配置参数的服务小区，当收到恢复持续LBT失败检测 和恢复的指示且收到了来自低层的LBT失败指示且LBT计数器大于或等于LBT失败最大值时，MAC实体触发所述服务小区的BWP上的持续LBT失败；以及
    当触发了持续LBT失败的服务小区是特殊小区时，当收到恢复持续LBT失败检测和恢复的指示，且在所述服务小区中的相同载波上配置了物理随机接入信道(PRACH)时机的所有上行BWP都触发了持续LBT失败的情况下，MAC实体向上层指示持续LBT失败。
  12. 根据权利要求10所述的装置，其中，所述恢复单元恢复持续LBT失败检测与恢复机制，还包括：
    当RRC切换完成或者当所述终端设备同步到第二小区时，RRC层指示低层恢复持续LBT失败检测和恢复，所述第二小区是目标小区。
  13. 根据权利要求1所述的装置，其中，所述装置还包括：
    第一接收单元，其用于从第一网络设备接收RRC重配置消息，所述RRC重配置消息包括LBT失败检测与恢复相关的配置信息，所述第一网络设备是源网络设备。
  14. 根据权利要求13所述的装置，其中，
    所述LBT失败检测与恢复相关的配置信息包括第一配置信息和/或第二配置信息，所述第一配置信息与第一小区的LBT失败检测与恢复相关，所述第二配置信息与第二小区的LBT失败检测与恢复相关，
    所述第一小区是属于源网络设备的一个小区，所述第二小区是属于目标网络设备的一个小区。
  15. 根据权利要求14所述的装置，其中，
    所述终端设备的源MAC实体根据所述第一配置信息，进行第一小区上的持续LBT失败检测与恢复；和/或，
    所述终端设备的目标MAC实体根据所述第二配置信息，进行第二小区上的持续LBT失败检测与恢复。
  16. 一种小区切换中的持续LBT失败检测与恢复的装置，所述装置应用于网络设备，所述装置包括：
    第一发送单元，其用于向终端设备发送RRC重配置消息，所述RRC重配置消息包括LBT失败检测与恢复相关的配置信息。
  17. 根据权利要求16所述的装置，其中，
    所述LBT失败检测与恢复相关的配置信息包括第一配置信息和/或第二配置信息，所述第一配置信息与第一小区的LBT失败检测与恢复相关，所述第二配置信息与第二小区的LBT失败检测与恢复相关，
    所述第一小区是属于源网络设备的一个小区，所述第二小区是属于目标网络设备的一个小区。
  18. 根据权利要求16所述的装置，其中，所述装置还包括：
    第二接收单元，其用于接收从第二网络设备接收发送的切换请求确认消息，所述第二网络设备是目标网络设备。
  19. 根据权利要求18所述的装置，其中，
    所述切换请求确认消息包括接入目标小区所需的信息以及与LBT失败检测和恢复相关的配置信息，所述与LBT失败检测和恢复相关的配置信息是所述终端设备对目标网络设备中的小区进行持续LBT失败检测与恢复的配置信息。
  20. 一种通信系统，所述通信系统包括终端设备和/或网络设备，所述终端设备包括根据权利要求1所述的装置，所述网络设备包括根据权利要求16所述的装置。
PCT/CN2020/091672 2020-05-21 2020-05-21 小区切换中的持续lbt失败检测和恢复的方法及装置 WO2021232383A1 (zh)

Priority Applications (4)

Application Number Priority Date Filing Date Title
JP2022568974A JP2023526276A (ja) 2020-05-21 2020-05-21 セルハンドオーバにおけるコンシステントｌｂｔ障害検出及び回復の方法及び装置
CN202080100636.7A CN115516989A (zh) 2020-05-21 2020-05-21 小区切换中的持续lbt失败检测和恢复的方法及装置
PCT/CN2020/091672 WO2021232383A1 (zh) 2020-05-21 2020-05-21 小区切换中的持续lbt失败检测和恢复的方法及装置
US17/983,572 US20230072832A1 (en) 2020-05-21 2022-11-09 Method and apparatus for consistent lbt failure detection and recovery in cell handover

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2020/091672 WO2021232383A1 (zh) 2020-05-21 2020-05-21 小区切换中的持续lbt失败检测和恢复的方法及装置

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US17/983,572 Continuation US20230072832A1 (en) 2020-05-21 2022-11-09 Method and apparatus for consistent lbt failure detection and recovery in cell handover

Publications (1)

Publication Number Publication Date
WO2021232383A1 true WO2021232383A1 (zh) 2021-11-25

Family

ID=78708973

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/091672 WO2021232383A1 (zh) 2020-05-21 2020-05-21 小区切换中的持续lbt失败检测和恢复的方法及装置

Country Status (4)

Country Link
US (1) US20230072832A1 (zh)
JP (1) JP2023526276A (zh)
CN (1) CN115516989A (zh)
WO (1) WO2021232383A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115669203A (zh) * 2020-05-18 2023-01-31 日本电气株式会社 用于通信的方法、设备和计算机可读介质

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116669084B (zh) * 2023-07-31 2023-11-10 浙江大华技术股份有限公司 基于蜂窝网络的故障修复方法、装置、设备以及存储介质

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109716853A (zh) * 2016-07-23 2019-05-03 韦勒斯标准与技术协会公司 非授权带中的信道接入的方法、装置和系统
US20190363843A1 (en) * 2018-05-27 2019-11-28 Brian Gordaychik Next generation radio technologies

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109716853A (zh) * 2016-07-23 2019-05-03 韦勒斯标准与技术协会公司 非授权带中的信道接入的方法、装置和系统
US20190363843A1 (en) * 2018-05-27 2019-11-28 Brian Gordaychik Next generation radio technologies

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
ERICSSON: "Corrections of NR operating with shared spectrum channel access in 38.321", 3GPP DRAFT; R2-2003875, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Electronic meeting; 20200420 - 20200430, 11 May 2020 (2020-05-11), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051882797 *
SAMSUNG ELECTRONICS: "Consistent LBT Failure Handling during Handover", 3GPP DRAFT; R2-2004529, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Electronic; 20200601 - 20200612, 20 May 2020 (2020-05-20), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051887375 *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115669203A (zh) * 2020-05-18 2023-01-31 日本电气株式会社 用于通信的方法、设备和计算机可读介质

Also Published As

Publication number Publication date
JP2023526276A (ja) 2023-06-21
US20230072832A1 (en) 2023-03-09
CN115516989A (zh) 2022-12-23

Similar Documents

Publication Publication Date Title
US9258747B2 (en) User equipment and methods for fast handover failure recovery in 3GPP LTE network
CN110798867B (zh) 用户设备的控制方法以及用户设备
WO2021008478A1 (zh) 信息上报方法及对应的用户设备
JP2021193804A (ja) ネットワーク接続の復旧装置
KR102587763B1 (ko) Lbt 모니터링 장애를 위한 처리 방법, 디바이스 및 시스템
US20220264687A1 (en) Methods for configurability of master cell group/primary cell fast recovery and related apparatuses
US20230072832A1 (en) Method and apparatus for consistent lbt failure detection and recovery in cell handover
CN101998469A (zh) 基于载波聚合的无线链路故障处理方法及用户设备
JP2023535123A (ja) マスターセルグループのための方法および装置
WO2021227881A1 (zh) 无线链路失败恢复方法及对应的用户设备
JP7322230B2 (ja) 通信制御方法
JP2023543514A (ja) Ｕｅ－ネットワーク間リレーシナリオにおけるリレー再選択およびデータ送信処理手順のための方法および装置
WO2021254197A1 (zh) 由用户设备执行的方法以及用户设备
WO2019193519A1 (en) Radio link failure management in wireless communication networks
WO2021203396A1 (zh) 持续lbt失败检测与恢复的方法及装置
CN115835318A (zh) 切换信息报告方法以及用户设备
WO2023193266A1 (zh) 下行无线链路质量的评估方法及装置
WO2024031293A1 (zh) 小区改变的方法及装置
WO2024065543A1 (zh) 失败检测及恢复方法和装置
WO2024031402A1 (zh) 测量放松的方法、装置以及通信系统
WO2023150963A1 (zh) 路径切换方法及装置
WO2021203395A1 (zh) 指示lbt失败的方法及装置
WO2021159402A1 (zh) Lbt失败的处理方法及装置
WO2024026894A1 (zh) 配置参数的方法、装置以及通信系统
WO2022237612A1 (zh) 网络转换方法以及用户设备

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 20936446

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2022568974

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 20936446

Country of ref document: EP

Kind code of ref document: A1