WO2023245338A1 - Procédés et appareils pour des améliorations de réseau d'auto-optimisation - Google Patents

Procédés et appareils pour des améliorations de réseau d'auto-optimisation Download PDF

Info

Publication number
WO2023245338A1
WO2023245338A1 PCT/CN2022/099832 CN2022099832W WO2023245338A1 WO 2023245338 A1 WO2023245338 A1 WO 2023245338A1 CN 2022099832 W CN2022099832 W CN 2022099832W WO 2023245338 A1 WO2023245338 A1 WO 2023245338A1
Authority
WO
WIPO (PCT)
Prior art keywords
lbt
information
period
failure
time
Prior art date
Application number
PCT/CN2022/099832
Other languages
English (en)
Inventor
Le Yan
Mingzeng Dai
Lianhai WU
Congchi ZHANG
Original Assignee
Lenovo (Beijing) Limited
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 Lenovo (Beijing) Limited filed Critical Lenovo (Beijing) Limited
Priority to PCT/CN2022/099832 priority Critical patent/WO2023245338A1/fr
Publication of WO2023245338A1 publication Critical patent/WO2023245338A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/02—Arrangements for optimising operational condition
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/08—Testing, supervising or monitoring using real traffic
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/002—Transmission of channel access control information
    • H04W74/004—Transmission of channel access control information in the uplink, i.e. towards network
    • 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/0069—Transmission or use of information for re-establishing the radio link in case of dual connectivity, e.g. decoupled uplink/downlink

Definitions

  • the present disclosure relates to wireless communication in a new radio unlicensed (NR-U) spectrum, and more specifically relates to methods and apparatuses for self-optimization network (SON) enhancements for NR-U.
  • NR-U new radio unlicensed
  • SON self-optimization network
  • the NR-U feature is introduced in Rel-16, and the user equipment (UE) can operate in the unlicensed spectrum with the PCell, PSCell and SCells.
  • any type of transmission can be transmitted in the unlicensed spectrum.
  • both the UE and the base station (BS) should perform the listen before talk (LBT) procedure and/or sense the wireless channel, in order to ensure that the wireless channel is not occupied by other transmissions which could be generated by non-3GPP technologies such as WiFi.
  • LBT listen before talk
  • mobility failure may be caused by radio link problem, and may also be caused by channel occupancy, i.e. the channel is not available and the LBT procedure is not successful. Therefore, it is necessary to provide solutions for SON enhancements for NR-U.
  • One embodiment of the present disclosure provides a UE, which includes: a transceiver; and a processor coupled with the transceiver and configured to: store information including one of the following: a first period of time elapsed since a last handover (HO) execution until an event; or a second period of time elapsed since a last primary secondary cell group (SCG) cell (PSCell) change execution until the event; wherein the event includes at least one of the following: a successful LBT procedure, a preamble transmission, MSG3 transmission, or MSGA transmission; and perform one of the following operations: transmit the information to a RAN node; or determine whether the information is used for mobility robustness optimization (MRO) .
  • MRO mobility robustness optimization
  • the information further includes at least one of the following: a time duration for LBT before or during per RACH attempt; a time duration for LBT per BWP; a total number of LBT failure indications received from a physical layer in a medium access control (MAC) layer before or during per random access channel (RACH) attempt; an indication indicating whether LBT before or during per RACH attempt is successful or not; an absolute time when an LBT procedure is successful; or an absolute time when LBT before or during per RACH attempt is successful.
  • MAC medium access control
  • RACH random access channel
  • determining whether the information is used for MRO based on a criteria includes a ratio being greater than a threshold, wherein the ratio is determined based on the first period of time and a third period of time, and the third period of time includes a period of time elapsed since a last HO execution until a connection failure; or wherein the ratio is determined based on the second period of time and a fourth period of time, and the fourth period of time includes a period of time elapsed since a last PSCell change execution until a connection failure.
  • the information is included in at least one of the following: a radio link failure (RLF) report; a RACH report; a connection establishment failure (CEF) report; a successful handover report (SHR) ; an SCG failure information message; or a secondary node (SN) RACH report.
  • RLF radio link failure
  • CEF connection establishment failure
  • SHR successful handover report
  • SN secondary node
  • the processor is further configured to store or transmit at least one of the following: an indication indicating the information is ignored for MRO in the case that the criteria is fulfilled; an indication indicating configuration associated with LBT needs to be modified; an indication indicating a consistent LBT failure in a MAC layer; an indication indicating a consistent LBT failure in a radio resource control (RRC) layer; or an indication indicating a connection failure is due to LBT failure.
  • an indication indicating the information is ignored for MRO in the case that the criteria is fulfilled
  • an indication indicating configuration associated with LBT needs to be modified an indication indicating a consistent LBT failure in a MAC layer
  • an indication indicating a consistent LBT failure in a radio resource control (RRC) layer an indication indicating a connection failure is due to LBT failure.
  • RRC radio resource control
  • the processor is further configured to discard the information in the case that the criteria is fulfilled.
  • a RAN node which includes: a transceiver; and a processor coupled with the transceiver and configured to: receive information from a UE including one of the following: a first period of time elapsed since a last HO execution until an event; or a second period of time elapsed since a last PSCell change execution until the event; wherein the event includes at least one of the following: a successful LBT procedure, a preamble transmission, MSG3 transmission, or MSGA transmission; and perform one of the following operations: transmit the information to another RAN node; determine whether the information is used for MRO; indicate another RAN node to modify the configuration associated with LBT; or perform MRO based on the information.
  • the information further includes at least one of the following: a time duration for LBT before or during per RACH attempt; a time duration for LBT per BWP; a total number of LBT failure indications received from a physical layer in a MAC layer before or during per RACH attempt; an indication indicating whether LBT before or during per RACH attempt is successful or not; an absolute time when an LBT procedure is successful; or an absolute time when LBT before or during per RACH attempt is successful.
  • determining whether the information is used for MRO based on a criteria includes a ratio being greater than a threshold, wherein the ratio is determined based on the first period of time and a third period of time, and the third period of time includes a period of time elapsed since a last HO execution until a connection failure; or wherein the ratio is determined based on the second period of time and a fourth period of time, and the fourth period of time includes a period of time elapsed since a last PSCell change execution until a connection failure.
  • the information is included in at least one of the following: an RLF report; a RACH report; a CEF report; an SHR; an SCG failure information message; or an SN RACH report.
  • the processor is further configured to receive at least one of the following: an indication indicating the information is ignored for MRO; an indication indicating configuration associated with LBT needs to be modified; an indication indicating a consistent LBT failure in a MAC layer; an indication indicating a consistent LBT failure in a RRC layer; or an indication indicating a connection failure is due to LBT failure.
  • the processor is further configured to discard the information in the case that an indication indicating the information is ignored for MRO is received.
  • the processor in the case that the criteria is fulfilled, is further configured to perform at least one of the following operations: discard the information; or transmit an indication indicating the another RAN node to modify the configuration associated with LBT; and wherein in the case that the criteria is not fulfilled, the processor is further configured to perform at least one of the following operations: transmit the information to the another RAN node; or transmit an indication indicating the another RAN node to modify the mobility related configuration.
  • a RAN node which includes: a transceiver; and a processor coupled with the transceiver and configured to: receive information from another RAN node including at least one of the following: a first period of time elapsed since a last HO execution until an event; a second period of time elapsed since a last PSCell change execution until the event; or a message or an indication indicating configuration associated with LBT needs to be modified; wherein the event includes at least one of the following: a successful LBT procedure, a preamble transmission, MSG3 transmission, or MSGA transmission; and perform one of the following operations: determine whether the information is used for MRO; or perform MRO based on the information.
  • the information further includes at least one of the following: a time duration for LBT before or during per RACH attempt; a time duration for LBT per BWP; a total number of LBT failure indications received from a physical layer in a MAC layer before or during per RACH attempt; an indication indicating whether LBT before or during per RACH attempt is successful or not; an absolute time when an LBT procedure is successful; or an absolute time when LBT before or during per RACH attempt is successful.
  • determining whether the information is used for MRO based on a criteria includes a ratio being greater than a threshold, wherein the ratio is determined based on the first period of time and a third period of time, and the third period of time includes a period of time elapsed since a last HO execution until a connection failure; or wherein the ratio is determined based on the second period of time and a fourth period of time, and the fourth period of time includes a period of time elapsed since a last PSCell change execution until a connection failure.
  • the processor is further configured to receive at least one of the following: an indication indicating the information is ignored for MRO; an indication indicating configuration associated with LBT needs to be modified; an indication indicating a consistent LBT failure in a MAC layer; an indication indicating a consistent LBT failure in a RRC layer; or an indication indicating a connection failure is due to LBT failure.
  • the processor is further configured to discard the information in the case that the indication indicating the information is ignored for MRO is received.
  • the information is included in at least one of the following: an RLF report; a RACH report; a CEF report; an SHR; an SCG failure information report message; or an SN RACH report.
  • the processor is further configured to: in the case that the criteria is not fulfilled, modify mobility related configuration; or in the case that the criteria is fulfilled, the processor is further configured to perform at least one of the following operations: discard the information, or modify configuration associated with LBT.
  • Yet another embodiment of the present disclosure provides a method performed by a UE, which includes: storing information including one of the following: a first period of time elapsed since a last HO execution until an event; or a second period of time elapsed since a last PSCell change execution until the event; wherein the event includes at least one of the following: a successful LBT procedure, a preamble transmission, MSG3 transmission, or MSGA transmission; and performing one of the following operations: transmitting the information to a RAN node; or determining whether the information is used for MRO.
  • the information further includes at least one of the following: a time duration for LBT before or during per RACH attempt; a time duration for LBT per BWP; a total number of LBT failure indications received from a physical layer in a MAC layer before or during per RACH attempt; an indication indicating whether LBT before or during per RACH attempt is successful or not; an absolute time when an LBT procedure is successful; or an absolute time when LBT before or during per RACH attempt is successful.
  • determining whether the information is used for MRO based on a criteria includes a ratio being greater than a threshold, wherein the ratio is determined based on the first period of time and a third period of time, and the third period of time includes a period of time elapsed since a last HO execution until a connection failure; or wherein the ratio is determined based on the second period of time and a fourth period of time, and the fourth period of time includes a period of time elapsed since a last PSCell change execution until a connection failure.
  • the information is included in at least one of the following: an RLF report; a RACH report; a CEF report; an SHR; an SCG failure information message; or an SN RACH report.
  • the method further includes storing or transmitting at least one of the following: an indication indicating the information is ignored for MRO in the case that the criteria is fulfilled; an indication indicating configuration associated with LBT needs to be modified; an indication indicating a consistent LBT failure in a MAC layer; an indication indicating a consistent LBT failure in a RRC layer; or an indication indicating a connection failure is due to LBT failure.
  • the method further includes discarding the information in the case that the criteria is fulfilled.
  • Yet another embodiment of the present disclosure provides a method performed by a RAN node, which includes: receiving information from a UE including one of the following: a first period of time elapsed since a last HO execution until an event; or a second period of time elapsed since a last PSCell change execution until the event; wherein the event includes at least one of the following: a successful LBT procedure, a preamble transmission, MSG3 transmission, or MSGA transmission; and performing one of the following operations: transmitting the information to another RAN node; determining whether the information is used for MRO; indicating another RAN node to modify the configuration associated with LBT; or performing MRO based on the information.
  • the information further includes at least one of the following: a time duration for LBT before or during per RACH attempt; a time duration for LBT per BWP; a total number of LBT failure indications received from a physical layer in a MAC layer before or during per RACH attempt; an indication indicating whether LBT before or during per RACH attempt is successful or not; an absolute time when an LBT procedure is successful; or an absolute time when LBT before or during per RACH attempt is successful.
  • determining whether the information is used for MRO based on a criteria includes a ratio being greater than a threshold, wherein the ratio is determined based on the first period of time and a third period of time, and the third period of time includes a period of time elapsed since a last HO execution until a connection failure; or wherein the ratio is determined based on the second period of time and a fourth period of time, and the fourth period of time includes a period of time elapsed since a last PSCell change execution until a connection failure.
  • the information is included in at least one of the following: an RLF report; a RACH report; a CEF report; an SHR; an SCG failure information message; or an SN RACH report.
  • the method further includes receiving at least one of the following: an indication indicating the information is ignored for MRO; an indication indicating configuration associated with LBT needs to be modified; an indication indicating a consistent LBT failure in a MAC layer; an indication indicating a consistent LBT failure in a RRC layer; or an indication indicating a connection failure is due to LBT failure.
  • the method further includes discarding the information in the case that an indication indicating the information is ignored for MRO is received.
  • the method further includes at least one of the following operations: discarding the information; or transmitting an indication indicating the another RAN node to modify the configuration associated with LBT; and wherein in the case that the criteria is not fulfilled, the method further includes at least one of the following operations: transmitting the information to the another RAN node; or transmitting an indication indicating the another RAN node to modify the mobility related configuration.
  • Yet another embodiment of the present disclosure provides a method performed by a RAN node, which includes: receiving information from another RAN node including at least one of the following: a first period of time elapsed since a last HO execution until an event; a second period of time elapsed since a last PSCell change execution until the event; or a message or an indication indicating configuration associated with LBT needs to be modified; wherein the event includes at least one of the following: a successful LBT procedure, a preamble transmission, MSG3 transmission, or MSGA transmission; and performing one of the following operations: determining whether the information is used for MRO; or performing MRO based on the information.
  • the information further includes at least one of the following: a time duration for LBT before or during per RACH attempt; a time duration for LBT per BWP; a total number of LBT failure indications received from a physical layer in a MAC layer before or during per RACH attempt; an indication indicating whether LBT before or during per RACH attempt is successful or not; an absolute time when an LBT procedure is successful; or an absolute time when LBT before or during per RACH attempt is successful.
  • determining whether the information is used for MRO based on a criteria includes a ratio being greater than a threshold, wherein the ratio is determined based on the first period of time and a third period of time, and the third period of time includes a period of time elapsed since a last HO execution until a connection failure; or wherein the ratio is determined based on the second period of time and a fourth period of time, and the fourth period of time includes a period of time elapsed since a last PSCell change execution until a connection failure.
  • the method further includes receiving at least one of the following: an indication indicating the information is ignored for MRO; an indication indicating configuration associated with LBT needs to be modified; an indication indicating a consistent LBT failure in a MAC layer; an indication indicating a consistent LBT failure in a RRC layer; or an indication indicating a connection failure is due to LBT failure.
  • the method further includes discarding the information in the case that the indication indicating the information is ignored for MRO is received.
  • the information is included in at least one of the following: an RLF report; a RACH report; a CEF report; an SHR; an SCG failure information report message; or an SN RACH report.
  • the method further includes: in the case that the criteria is not fulfilled, modifying mobility related configuration; or in the case that the criteria is fulfilled, the method further includes at least one of the following operations: discarding the information, or modifying configuration associated with LBT.
  • Fig. 1 illustrates a schematic diagram of a wireless communication system according to some embodiments of the present disclosure.
  • Fig. 2 illustrates a method performed by a UE for wireless communication according to some embodiments of the present disclosure.
  • Fig. 3 illustrates a method performed by a RAN node for wireless communication according to some embodiments of the present disclosure.
  • Fig. 4 illustrates a method performed by a RAN node for wireless communication according to some embodiments of the present disclosure.
  • Fig. 5 illustrates a simplified block diagram of an exemplary apparatus according to some embodiments of the present disclosure.
  • Fig. 1 depicts a wireless communication system according to some embodiments of the present disclosure.
  • the wireless communication system includes the UE 101, the BS 102-A, the BS 102-B, and the BS 102-C. Even though a specific number of UE and BSs are depicted in Fig. 1, persons skilled in the art will recognize that any number of UEs and BSs may be included in the wireless communication system.
  • the UE 101 may include computing devices, such as desktop computers, laptop computers, personal digital assistants (PDAs) , tablet computers, smart televisions (e.g., televisions connected to the Internet) , set-top boxes, game consoles, security systems (including security cameras) , vehicle on-board computers, network devices (e.g., routers, switches, modems) , or the like.
  • the UE 101 may include a portable wireless communication device, a smart phone, a cellular telephone, a flip phone, a device having a subscriber identity module, a personal computer, a selective call receiver, or any other device that is capable of sending and receiving communication signals on a wireless network.
  • the UE 101 includes wearable devices, such as smart watches, fitness bands, optical head-mounted displays, or the like. Moreover, the UE 101 may be referred to as subscriber units, mobiles, mobile stations, users, terminals, mobile terminals, wireless terminals, fixed terminals, subscriber stations, user terminals, a device, or by other terminology used in the art. The UE 101 may communicate directly with a BS via uplink (UL) communication signals.
  • UL uplink
  • the BSs may be distributed over a geographic region.
  • a BS may also be referred to as an access point, an access terminal, a base, a base station, a macro cell, a Node-B, an enhanced Node B (eNB) , a Home Node-B, a relay node, a device, or by any other terminology used in the art.
  • the BSs are generally part of a radio access network that may include one or more controllers communicably coupled to one or more corresponding BSs.
  • the wireless communication system is compliant with any type of network that is capable of sending and receiving wireless communication signals.
  • the wireless communication system is compliant with a wireless communication network, a cellular telephone network, a time division multiple access (TDMA) -based network, a code division multiple access (CDMA) -based network, an orthogonal frequency division multiple access (OFDMA) -based network, a LTE network, a 3 rd generation partnership project (3GPP) -based network, 3GPP 5G network, a satellite communications network, a high altitude platform network, and/or other communications networks.
  • TDMA time division multiple access
  • CDMA code division multiple access
  • OFDMA orthogonal frequency division multiple access
  • LTE Long Term Evolution
  • 3GPP 3 rd generation partnership project
  • 3GPP 5G 3 rd generation partnership project
  • the wireless communication system is compliant with the NR of the 3GPP protocol, wherein the BS transmits using an orthogonal frequency division multiplexing (OFDM) modulation scheme on the DL and the UE 101 transmits on the uplink using a single-carrier frequency division multiple access (SC-FDMA) scheme or OFDM scheme. More generally, however, the wireless communication system may implement some other open or proprietary communication protocol, for example, WiMAX, among other protocols.
  • OFDM orthogonal frequency division multiplexing
  • SC-FDMA single-carrier frequency division multiple access
  • the BS may communicate using other communication protocols, such as the IEEE 802.11 family of wireless communication protocols. Further, in some embodiments the BS may communicate over licensed spectrum, while in other embodiments the BS may communicate over unlicensed spectrum. The present disclosure is not intended to be limited to the implementation of any particular wireless communication system architecture or protocol. In another embodiment, the BS may communicate with UE 101 using the 3GPP 5G protocols.
  • the UE 101 is currently served by the BS 102-A, and is moving towards the BS 102-B.
  • the UE 101 may need to perform the normal handover procedure from a source primary cell (PCell) or a source cell managed by the BS 102-Ato a target PCell or a target cell managed by the BS 102-B.
  • the source cell or target cell may use the unlicensed spectrum.
  • the BS 102-A may considered as the source RAN node, the source BS, the source gNB, the source eNB, or the like.
  • the BS 102-B is considered as the target RAN node, the target BS, the target gNB, the target eNB, etc.
  • the UE101 may perform a re-establishment procedure, and re-connect/access to the BS 102-C.
  • the BS 102-C is considered as the re-establishment RAN node, the re-establishment BS, the re-establishment gNB, the re-establishment eNB, etc.
  • the UE may select the source node as the re-establishment node and re-connect/access to the BS 102-A.
  • the serving RAN node may be the source RAN node or the re-establishment RAN node.
  • the UE 101 may perform a DAPS handover procedure, or a CHO handover procedure.
  • a MR-DC system where the UE is configured with a master cell group (MCG) , which is a group of serving cells associated with the MN, including a primary cell (PCell) and optionally one or more secondary cells (SCells) .
  • MCG master cell group
  • SCells secondary cells
  • the UE is also configured with a secondary cell group (SCG) , which is a group of serving cells associated with the SN, including a primary secondary cell (PSCell) and optionally one or more SCells.
  • SCG secondary cell group
  • the PCell, PSCell, or SCells may use the unlicensed spectrum.
  • the UE may perform a PSCell change procedure, or a conditional PSCell addition and change (CPAC) procedure.
  • CPAC conditional PSCell addition and change
  • both the UE and the BS Before performing any transmission in such as the normal handover procedure, a DAPS handover procedure, a CHO handover procedure, a PSCell change procedure, or a CPAC procedure, in the unlicensed spectrum, both the UE and the BS should perform the LBT procedure and sense the wireless channel, in order to ensure that the spectrum is not occupied by other transmissions which may be generated by non-3GPP technologies such as WiFi.
  • the UE may be configured with a number of bandwidth parts (BWPs) in the unlicensed spectrum, after receiving the handover command (i.e. a RRC reconfiguration message including ReconfigurationWithSync information element (IE) ) , the UE starts timer T304, and performs LBT failure detection and recovery procedure with the target PCell before timer T304 expires.
  • BWPs bandwidth parts
  • the MAC entity may be configured by RRC with a consistent LBT failure recovery procedure.
  • consistent LBT failure is detected per UL BWP in MAC entity by counting LBT failure indications received from the lower layers i.e. PHY layer.
  • the UE may perform LBT in a BWP, if the number of LBT failure indications from the physical layer within the valid time which represented as lbt-FailureDetectionTimer, exceeds the maximum value, which may be represented as: lbt-FailureInstanceMaxCount, then the UE determines that a consistent LBT failure happens in this BWP. If consistent LBT failure happens in all UL BWPs configured with PRACH occasions, MAC entity may indicate to the upper layer, i.e. RRC layer that LBT failure occurs.
  • RRC configures the following parameters in the lbt-FailureRecoveryConfig: lbt-FailureInstanceMaxCount for the consistent LBT failure detection; and lbt-FailureDetectionTimer for the consistent LBT failure detection.
  • the following UE variable is used for the consistent LBT failure detection procedure:
  • LBT_COUNTER (per serving cell) : counter for LBT failure indication which is initially set to 0.
  • the MAC entity For each activated serving cell configured with lbt-FailureRecoveryConfig, the MAC entity shall perform the following steps:
  • a handover failure may happen.
  • the handover failure may include: too late handovers, too early handover, or handover to the wrong cell, which are as follows:
  • an RLF occurs shortly after a successful handover from a source cell to a target cell, or a handover failure occurs during the handover procedure; and the UE attempts to re-establish the radio link connection in a cell other than the source cell and the target cell.
  • the cell other than the source cell and the target cell may be referred as the wrong cell.
  • the expression “successful handover” refers to the UE state, namely the successful completion of the RA procedure.
  • the UE may perform re-establishment in a cell.
  • UE may store some information related with RLF failure and/or handover failure information, which are included in the RLF report (or in VarRLF-report) , which may include the following:
  • CGI cell global identifier
  • C-RNTI Cell radio network temporary identifier
  • E-UTRAN evolved universal terrestrial radio access network
  • NR UE RLF report NR UE RLF report.
  • RRM radio resource management
  • ⁇ Measurement can be done on different RS types such as:
  • CSI-RS Channel state information-reference signal
  • Tracking reference signal TRS
  • DMRS demodulation reference signal
  • Logging sensor data including UE orientation/altitude to log in addition to location, speed and heading (e.g. digital compass, gyroscope as well as barometer, etc. ) .
  • a UE speed state (low, mid, high) detected by the UE as part of speed-based scaling procedure.
  • the UE may store the latest RLF report until the RLF report is fetched by the network, or for 48 hours after the connection failure is detected. For analysis of connection failures, the UE may transmit a message to the network indicating that the RLF report is available at the UE.
  • the availability of an RLF report may be indicated by the RRCSetupComplete, RRCResumeComplete, or RRCReconfigurationComplete or RRCRe-establishmentComplete message, e.g.
  • the UE may include rlf-InfoAvailable in the RRCSetupComplete message, the RRCResumeComplete message, the RRCReconfigurationComplete message, or the RRCRe-establishmentComplete message.
  • the network may fetch information of an RLF report via UE information request/response mechanism, i.e. the BS may transmit UEinformationrequest to UE, as a response, the UE may transmit UEinformationresponse which includes the RLF report to the BS. In this way, the network may optimize the mobility problem based on the response from UE.
  • the mobility failure may be caused by radio link problem and/or channel occupancy.
  • the present disclosure proposes some solutions as follows.
  • Solution 1 relates to the handover cases.
  • a handover procedure in NR-U which may include a normal handover procedure, a dual active protocol stack (DAPS) handover procedure, or a conditional handover (CHO) handover procedure
  • the UE may need to perform an LBT procedure before transmitting the preamble (or the MSG3, or the MSGA) towards the target PCell.
  • DAPS dual active protocol stack
  • CHO conditional handover
  • the time when the UE executes the handover procedure for example, the time when the UE receives the handover command (i.e. a RRC reconfiguration message including ReconfigurationWithSync IE) , when the UE applies the configuration included in the handover command, or when the CHO execution condition is met;
  • the handover command i.e. a RRC reconfiguration message including ReconfigurationWithSync IE
  • - T2 the time when any one of the following events happens: when the LBT procedure is successful, when the UE transmits the preamble towards a target PCell, when the UE transmits MSG3 towards the target PCell in a 4-step RA procedure; or when UE transmits MSGA towards the target PCell in a 2-step RA procedure; and
  • the time when the connection failure happens which may include the time when the handover failure (HOF) happens or the time when the RLF happens.
  • the UE may first perform the LBT procedure. Only when the LBT procedure is successful, the UE can transmit the uplink message or uplink data to the target PCell, for example, upon the LBT procedure with the target PCell before transmitting a preamble, MSG3, or MSGA is successful, the UE may transmit the preamble, the MSG3, or the MSGA towards the target PCell.
  • the connection failure may be caused in the following cases:
  • the HOF is mainly caused by a radio link problem or a RACH problem.
  • the period of time of the LBT procedure which may be a period of time elapsed since the HO execution (i.e. T1) until the preamble transmission, the MSG3 transmission, or the MSGA transmission, towards the target PCell (i.e. T2) , may be short, and the LBT procedure before the preamble transmission, the MSG3 transmission, or the MSGA transmission is successful.
  • the HOF happens.
  • the radio link problem or the RACH problem may be the main cause for the HOF.
  • the HOF is mainly caused by the long period of time for the LBT procedure.
  • the LBT procedure before or during the RA procedure is successful, e.g. the LBT procedure before the preamble transmission or the MSGA transmission is successful, or the LBT procedure before the MSG3 transmission during the RA procedure is successful, but a HOF happens, a long time duration of LBT elapsed from HO execution (i.e. T1) until the preamble transmission, the MSG3 transmission, or the MSGA transmission, towards a target PCell (i.e. T2) , is the main cause for the HOF.
  • timer T304 is set as 50ms, and the period of time for the LBT procedure occupies 48ms, and there is only 2ms left for performing the RA procedure towards the target PCell, which may not be enough for the RA procedure, which renders the HOF.
  • the HOF is mainly caused by a LBT failure, e.g. at least one consistent LBT failure in MAC entity or RRC entity.
  • a LBT failure e.g. at least one consistent LBT failure in MAC entity or RRC entity.
  • the consistent LBT failure is detected by the MAC layer or the RRC layer of the target PCell, the LBT procedure before or during the RA procedure fails, and a HOF happens.
  • the UE may store (or log, record, etc.
  • store, “ “record, “ or “log” may be used interchangeably where appropriate) , and report information associated with the HOF, to enable the proper and necessary MRO analysis at the network side.
  • the information may include: a period of time elapsed since the last HO execution until one of: a successful LBT procedure, a preamble transmission, MSG3 transmission, or MSGA transmission.
  • the information can be per RA procedure or per RACH attempt.
  • the information may include at least one of the following:
  • the information may include at least one of the following:
  • the information may further include:
  • the time duration for LBT before a RACH attempt may include: the time duration for LBT after HO execution (i.e. T1) and before the MSGA transmission, or the time duration for LBT after HO execution (i.e. T1) and before the preamble transmission.
  • the time duration for LBT during the RACH attempt may include the time duration for LBT after HO execution (i.e. T1) and before the MSG3 transmission.
  • the time duration for LBT per BWP includes the time duration for LBT on beam 1 and the time duration for LBT on beam 2.
  • the LBT procedure is successful at 12: 00 13 June 2022, UTC time; or
  • the UE may store at least a part or all of the above information. After the UE stores the information, the UE may report the information to a RAN node, e.g. based on a request from the RAN node.
  • the RAN node may be referred to as a receiving RAN node, which may be the source RAN node in the case that the UE reconnects the source RAN node, or may be a third RAN node (or a re-established RAN node) in the case that UE connects the third RAN node after the handover failure.
  • the UE may report the information in various manners, for example, the UE may store or report the above information in the RLF report, the RACH report, CEF report, SHR, a VarRLF report, or the like. Alternatively, the UE may report the above information by a dedicated message, e.g. UE information response message.
  • a dedicated message e.g. UE information response message.
  • the present disclosure proposes a criteria, which may be used for determining whether the information may be used for MRO.
  • the criteria may include a ratio being greater than a threshold.
  • the ratio which may be represented as: ratio HO , may be determined based on the following two periods of time, Period 1 and Period 2, which are defined as follows:
  • Period 1 the period of time elapsed since the last HO execution (i.e. T1) until the time when one of the following events happens: a successful LBT procedure, a preamble transmission, MSG3 transmission in a 4-step RA procedure, or MSGA transmission in a 2-step RA procedure (i.e. T2) .
  • the length of the Period 1 equals to T2-T1
  • Period 2 the period of time elapsed since the last HO execution (i.e. T1) until a connection failure (i.e. T3) .
  • the length of Period 2 equals to T3-T1.
  • the connection failure means handover failure or RLF.
  • Period 2 can be represented by the timeConnFailure IE.
  • the ratio, ratio HO may be calculated by the following function (1) :
  • the criteria associated with ratio HO may be: when the ratio (ratio HO ) is greater than a threshold, the information may be ignored for MRO.
  • ratio HO ' is calculated as the following function (2) :
  • ratio HO ' may be: when the ratio (ratio HO ') is smaller than a threshold, the information may be ignored for MRO. Other criteria that may achieve the same function (i.e. determining whether the information may be used for MRO) may also be applied in the present disclosure.
  • the present disclosure proposes to use the criteria associated with ratio HO as an example to illustrate the solutions.
  • the threshold may be configured by operation administration and maintenance (OAM) , or by implementation, by the specification, or pre-configuration, etc.
  • OAM operation administration and maintenance
  • the threshold may be configured to the UE by the HO command.
  • the ratio (e.g. ratio HO ) is smaller than or equal to the threshold, which means during the handover procedure, the time for the RA procedure may be adequate, and the main cause of the handover failure may be a mobility related issue. Accordingly, the mobility related configuration may need to be modified, thus the information from the UE may be used for MRO.
  • the UE may reconnect or re-establish with a receiving RAN node (which is not the source RAN node or the target RAN node, and it may be referred to as the third RAN node, the re-established RAN node, or the like) .
  • the UE may transmit the information to the receiving RAN node.
  • the receiving RAN node may determine whether the criteria is met or not, i.e. whether the ratio (e.g. ratio HO ) is greater than the threshold or not. When the criteria is met, i.e. the ratio (e.g. ratio HO ) is greater than the threshold, the receiving RAN node may determine that the information may be ignored for MRO.
  • the receiving RAN node may release the information from the UE, and may not deliver the information to the source RAN node.
  • the receiving RAN node may determine whether the configuration associated with LBT needs to be modified, which may be based on the information associated with LBT received from the UE (for example, the time duration for LBT before or during per RACH attempt, the time duration for LBT per BWP, the total number of LBT failure indications received from a physical layer in a MAC layer before or during per RACH attempt, the an indication indicating whether LBT before or during per RACH attempt is successful or not, an absolute time when an LBT procedure is successful; or an absolute time when LBT before or during per RACH attempt is successful, or other information associated with LBT) , and the receiving RAN node may transmit an indication indicating that the configuration associated with LBT needs to be modified.
  • the information associated with LBT received from the UE for example, the time duration for LBT before or during per RACH attempt, the time duration for LBT per BWP, the total number of LBT failure indications received from a physical layer in a MAC layer before or during per RACH attempt, the an indication indicating whether
  • the receiving RAN node may inform the source RAN node to modify the received signal strength indicator (RSSI) or channel occupancy (CO) measurement configuration, or other configuration associated with LBT, e.g. via a message or an indication.
  • the receiving RAN node may also inform the target RAN node to update the configuration for LBT failure recovery directly or via the source RAN node indirectly, e.g. via a message or an indication.
  • RSSI received signal strength indicator
  • CO channel occupancy
  • the configuration for LBT failure recovery may include the timer for consistent uplink LBT failure detection, lbt-FailureDetectionTimer, the maximum number that determines after how many consistent uplink LBT failure events the UE triggers uplink LBT failure recovery, lbt-FailureInstanceMaxCount, or other configuration associated with LBT.
  • the receiving RAN node may transmit at least one of the following indications to the source RAN node: an indication indicating at least one consistent LBT failure in a MAC layer, an indication indicating a consistent LBT failure in a RRC layer; or an indication indicating a connection failure is due to LBT failure.
  • the UE may reconnect the source RAN node, and the UE may transmit the information to the source RAN node.
  • the UE may re-establish with a receiving RAN node (which is a third node that is not the source RAN node or the target RAN node) , and the UE may transmit the information to the receiving RAN node.
  • the receiving RAN node may transmit the received information from the UE to the source RAN node.
  • the source RAN node may determine whether the criteria is met or not, i.e. whether the ratio (e.g. ratio HO ) is greater than the threshold or not. When the criteria is met, i.e. the ratio is greater than the threshold, the source RAN node may determine that the information may be ignored for MRO. The source RAN node may release the information from the UE.
  • the source RAN node may determine the configuration associated with LBT needs to be modified. For example, the source RAN node may modify the RSSI or CO measurement configuration, or other configuration associated with LBT.
  • the source RAN node may also inform the target RAN node to update the configuration for LBT failure recovery in a similar way as the receiving RAN node.
  • the source RAN node may modify mobility related configurations (e.g. threshold for HO execution or CHO execution condition) based on the received information.
  • the UE may store the same information as in Embodiment 1-1, for example the UE may store the period of time elapsed since the last HO execution until one of: a successful LBT procedure, a preamble transmission, MSG3 transmission, or MSGA transmission, the time duration for LBT before or during per RACH attempt, the total number of LBT failure indications received from a physical layer in a MAC layer before or during per RACH attempt, etc.
  • the UE may determine whether the information may be used for MRO, for LBT related configuration modification, or both. Specifically, the UE may also use the same criteria in embodiment 1-1 for determining whether the information may be used for MRO, for LBT related configuration modification, or both.
  • the UE may determine whether the ratio (e.g. ratio HO ) is greater than a threshold or not, which may be configured by the network to the UE via an RRC signalling (ahandover command, e.g. RRCReconfiguration message with reconfigurationWithSync) , or by UE implementation.
  • a threshold may be pre-configured, or defined in the specification.
  • the UE may determine that the criteria is fulfilled, i.e. the ratio (e.g. ratio HO ) is greater than the threshold, and the information may be ignored for MRO.
  • the UE may transmit the information to the receiving RAN node, and the UE may further store and/or transmit at least one of the following indications to the receiving RAN node:
  • an indication indicating that the information is ignored for MRO This indication may be stored and/or transmitted in any one of the above cases 1-3; when receiving the indication indicating that the information is ignored for MRO, the receiving RAN node may ignore the received failure related information for MRO.
  • this indication may be stored and/or transmitted in the above case 1-3) , or a consistent LBT failure in the RRC layer (this indication may be stored and/or transmitted in the above case 3) .
  • an indication indicating a connection failure is due to LBT failure.
  • the UE may reconnect or re-establish with a receiving RAN node (which is not the source RAN node or the target RAN node, and it may be referred to as the third RAN node, the re-established RAN node, or the like) .
  • the UE may transmit above information to the receiving RAN node.
  • the receiving RAN node may release the information from the UE and may not deliver the information to the source RAN node, e.g. based on the received indication (s) ; or the receiving RAN node may transfer the information from the UE to the source RAN node, and the source RAN node may release the information from the UE or ignore the information for MRO, e.g. based on the received indication (s) .
  • the receiving RAN node may determine the configuration associated with LBT needs to be modified, the details can be similar as Embodiment 1-1.
  • the receiving RAN node is a third RAN node, it may inform the source RAN node to modify the RSSI or CO measurement configuration.
  • the receiving RAN node may inform the target RAN node to update the configuration for LBT failure recovery directly or via the source RAN node indirectly.
  • the UE may reconnect or re-establish with the source RAN node.
  • the UE may transmit above information to the source RAN node.
  • the source RAN node may release the information from the UE or do not take the information into account for MRO, e.g. based on the received indication (s) .
  • the source RAN node may determine the configuration associated with LBT needs to be modified. For example, the source RAN node may modify the RSSI or CO measurement configuration, or other configuration associated with LBT.
  • the source RAN node may also inform the target RAN node to update the configuration for LBT failure recovery.
  • the UE when the UE determines that the criteria is met, i.e. the ratio (e.g. ratio HO ) is greater than the threshold, the above stored information may be ignored for MRO, the UE may not transmit the stored information to the receiving RAN node, rather, the UE may discard (or remove, release, etc.
  • the stored failure related information e.g. the UE releases the stored information, or, may transmit an RLF report or UE variable VarRLF-Report including non-LBT related information as legacy in licensed system but without the above LBT related information.
  • the UE may discard the RLF report or the VarRLF-Report, e.g. the UE does not send the RLF report or the VarRLF-Report to the network.
  • Solution 2 relates to the SCG change, the PSCell change, or CPAC cases.
  • a PSCell change procedure or a CPAC procedure when the UE has experienced any SCG failure, such as SCG radio link failure, failure of SCG reconfiguration with sync, SCG configuration failure for RRC message on signaling radio bearer 3 (SRB3) , or SCG integrity check failure, the UE may send the SCG failure information message to the network e.g. MN.
  • SCG failure type, measurement results in MCG and measurement results in SCG, or other information may be included in the SCG failure information message.
  • the MN may be responsible for MRO, e.g., the MN performs root cause analysis, determines whether to modify PSCell change or CPAC related configuration, and/or how to modify PSCell change or CPAC related configuration, for example, the MN may updates at least one of the following: a reference signal received power (RSRP) threshold, a reference signal received quality (RSRQ) threshold, or a signal to interference plus noise ratio (SINR) trigger threshold for PSCell change or CPAC, time to trigger (TTT) of measurement report for PSCell change or CPAC, TTT for CPAC evaluation, etc.
  • RSRP reference signal received power
  • RSRQ reference signal received quality
  • SINR signal to interference plus noise ratio
  • a PSCell change failure or CPAC failure for SN initiated PSCell change or SN initiated CPAC procedure, it is the SN initiating the last PSCell change or the last serving SN that is responsible for MRO, the MN needs to forward the SCG failure related information (e.g. information in the SCGFailureInformation from the UE and/or some other information (e.g. mobility information, failure type, etc. ) ) to the SN initiating the last PSCell change or the last serving SN, then the SN determines whether and/or how to modify PSCell change or CPAC related configuration.
  • SCG failure related information e.g. information in the SCGFailureInformation from the UE and/or some other information (e.g. mobility information, failure type, etc. )
  • the UE may need to perform an LBT procedure before transmitting the preamble (or the MSG3, or the MSGA) towards the target PSCell.
  • the preamble or the MSG3, or the MSGA
  • the time when the UE executes the PSCell change procedure for example, the time when the UE receives the PSCell change command (i.e. a RRC reconfiguration message including ReconfigurationWithSync IE for SCG) , when the UE applies the configuration included in the PSCell change command, or when the CPAC execution condition is met;
  • the PSCell change command i.e. a RRC reconfiguration message including ReconfigurationWithSync IE for SCG
  • - TB the time when any one of the following events happens: when the LBT procedure is successful, when the UE transmits the preamble towards target the PSCell, when the UE transmits MSG3 towards the target PSCell in a 4-step RA procedure; or when UE transmits MSGA towards the target PSCell in a 2-step RA procedure; and
  • the time when the connection failure happens which may include the time when the PSCell change failure happens, or the time when the SCG failure happens.
  • the UE may first perform the LBT procedure. Only when the LBT procedure is successful, may the UE transmit the uplink message or uplink data to the target PSCell, for example, upon the LBT procedure with the target PSCell before transmitting a preamble, MSG3, or MSGA is successful, the UE may transmit the preamble, the MSG3, or the MSGA towards the target PSCell.
  • the connection failure may be caused in the following cases:
  • Case A the PSCell change failure or the SCG failure is mainly caused by a radio link problem or a RACH problem.
  • the period of time of the LBT procedure which may be a period of time elapsed since the PSCell change execution until the preamble transmission, the MSG3 transmission, or the MSGA transmission, towards the target PSCell, may be short, and the LBT procedure before or during the RA procedure is successful.
  • the radio link problem or the RACH problem is the main cause for the PSCell change failure or the SCG failure;
  • Case B the PSCell change failure or the SCG failure is mainly caused by the long period of time for the LBT procedure.
  • the LBT procedure before or during the RA procedure is successful, e.g. the LBT procedure before the preamble transmission or the MSG3 transmission or the MSGA transmission is successful, but the PSCell change or SCG failure happens, a long time duration of LBT elapsed from the PSCell change execution (i.e. TA) until the preamble transmission, the MSG3 transmission, or the MSGA transmission, towards the target PSCell (i.e. TB) , is the main cause for the PSCell change failure or the SCG failure.
  • TA the PSCell change execution
  • timer T304 is set as 50ms, and the period of time for the LBT procedure occupies 49ms, and there is only 1ms left for performing the RA procedure towards the target PSCell, which may not be enough for the RA procedure, which renders the PSCell change or SCG failure.
  • Case C the PSCell change failure or the SCG failure is mainly caused by a LBT failure, e.g. at least one consistent LBT failure in MAC entity or RRC entity.
  • a LBT failure e.g. at least one consistent LBT failure in MAC entity or RRC entity.
  • the consistent LBT failure is detected by the MAC layer or the RRC layer of the target PSCell, the LBT procedure before or during the RA procedure fails, and the PSCell change failure or the SCG failure happens.
  • the UE may store and report information associated with the PSCell change failure or the SCG failure, to enable the proper and necessary MRO analysis at the network side.
  • the information may include: a period of time elapsed since the last PSCell change execution or when the CPAC execution condition is met (i.e. TA) , until one of the following events: a successful LBT procedure with the target PSCell, a preamble transmission towards the target PSCell, MSG3 transmission towards the target PSCell, or MSGA transmission towards the target PSCell (i.e. TB) .
  • the information can be per RA procedure or per RACH attempt.
  • the information may be included in the SCG failure information message, SN RACH report, a dedicated message, or the like.
  • the information may further include at least one of the following:
  • the time duration for LBT before a RACH attempt may include: the time duration for LBT after HO execution (i.e. T1) and before the MSGA transmission, or the time duration for LBT after HO execution (i.e. T1) and before the preamble transmission.
  • the time duration for LBT during the RACH attempt may include the time duration for LBT after HO execution (i.e. T1) and before the MSG3 transmission.
  • the time duration for LBT per BWP includes the time duration for LBT on beam 1 and the time duration for LBT on beam 2.
  • the LBT procedure is successful at 12: 00 13 June 2022, UTC time; or
  • the UE may report the stored information to the network.
  • the UE may report the information in various manners, for example, the UE may store or report the above information included in the RLF report, the RACH report, CEF report, a SN RACH report or the like. Alternatively, the UE may report the above information by a dedicated message, e.g. UE information response message.
  • a dedicated message e.g. UE information response message.
  • the UE may report the information in various manners, for example, the UE may store or report the above information in the SCG failure information message, a successful PSCell change report, or the like.
  • Scenario 1 in this scenario, it is the MN that initiated the PSCell change or the CPAC, and when the MN receives the above information from the UE, the MN may decide whether the information may be used for MRO.
  • a criteria may be used for determining whether the information may be used for MRO.
  • the criteria may include a ratio being greater than a threshold.
  • the ratio which may be represented as: ratio SCG , may be determined based on the following two periods of time, Period A and Period B, which are defined as follows:
  • Period A the period of time elapsed since the last PSCell change execution (i.e. TA) until the time when one of the following events happens: a successful LBT procedure, a preamble transmission, MSG3 transmission in a 4-step RA procedure, or MSGA transmission in a 2-step RA procedure (i.e. TB) .
  • the length of Period A equals to TB-TA, and
  • Period B the period of time elapsed since the last PSCell execution (i.e. TA) until PSCell change failure or SCG failure (i.e. TC) .
  • the length of Period B equals to TC-TA.
  • Period B can be represented by the timeSCGFailure IE, which indicates the time elapsed since the last execution of RRCReconfiguration with reconfigurationWithSync for the SCG until the SCG failure.
  • the ratio, ratio SCG may be calculated by the following function (3) :
  • ratio SCG may be: when the ratio (ratio SCG ) is greater than a threshold, the information may be ignored for MRO.
  • ratio SCG ' is calculated as the following function (4) :
  • ratio SCG ' may be: when the ratio (ratio SCG ') is smaller than a threshold, the information may be ignored for MRO. Other criteria that may achieve the same function (i.e. determining whether the information may be used for MRO) may also be applied in the present disclosure.
  • the present disclosure proposes to use the criteria associated with ratio SCG as an example to illustrate the solutions.
  • the threshold which means during the PSCell change procedure or the CPAC procedure, the UE may have spent too much time on the LBT procedure, the main cause of the SCG failure may be the LBT issue, and a mobility related configuration may not need to be modified, thus the information from the UE may be discarded, or ignored for MRO.
  • the threshold may be configured by OAM, or by MN implementation, by the specification, or pre-configuration, etc.
  • the threshold may be configured to the UE by the PSCell change command or CPAC command, e.g. RRCReconfiguration message with reconfigurationWithSync for the SCG.
  • the ratio (e.g. ratio SCG ) is smaller than or equal to the threshold, which means during the PSCell change procedure or the CPAC procedure, the time for the LBT procedure may not be adequate, and the main cause of the SCG failure may be a mobility related issue. Accordingly, the mobility related configuration may need to be modified, thus the information from the UE may be used for MRO, for example, for MN initiated PSCell change or CPAC, e.g. the MN may modify PSCell change or CPAC related configurations, for example, modify a RSRP threshold, a RSRQ threshold, a SINR threshold for PSCell change or CPAC execution condition.
  • MRO for example, for MN initiated PSCell change or CPAC
  • the MN may modify PSCell change or CPAC related configurations, for example, modify a RSRP threshold, a RSRQ threshold, a SINR threshold for PSCell change or CPAC execution condition.
  • the MN may also determine whether the configuration associated with LBT needs to be modified based on the information from the UE.
  • the MN may transmit a message or an indication indicating that the configuration associated with LBT needs to be modified to the source SN, the last serving SN, or the target SN.
  • the MN may modify the RSSI or CO measurement configuration, or other measurement configuration associated with LBT.
  • the MN may also inform the target SN to update the configuration for LBT failure recovery, e.g.
  • the configuration for LBT failure recovery may include the timer for consistent uplink LBT failure detection, lbt-FailureDetectionTimer, the maximum number that determines after how many consistent uplink LBT failure events the UE triggers uplink LBT failure recovery, lbt-FailureInstanceMaxCount, or other configuration associated with LBT, e.g. via an indication or a message.
  • Scenario 2 in this scenario, it is the SN that initiated the PSCell change or the CPAC, and when the MN receives the above information from the UE, the MN may take the following options:
  • the MN may transmit the information received from the UE to the source SN, or the last serving SN.
  • the source SN or the last serving SN may determine whether the information received from the UE is used for MRO based on a criteria associated with ratio SCG , the criteria is the same as above in Scenario 1.
  • the criteria is met, i.e. ratio SCG is greater than the threshold, the information may be discarded, and ignored for MRO.
  • the threshold may be configured by OAM, by MN, by SN implementation, by the specification, or pre-configuration, etc.
  • the information may be used for MRO, e.g. the source SN or the last serving SN may update PSCell change or CPAC related configurations, for example, modify the RSRP threshold, the RSRQ threshold, or the SINR threshold for PSCell change or CPAC execution condition.
  • the last serving SN or the source SN may decide whether the configuration associated with LBT needs to be modified.
  • the last serving SN or the source SN may modify the RSSI or CO measurement configuration, or other measurement configuration associated with LBT.
  • the last serving SN or the source SN may also inform target SN to update the configuration for LBT failure recovery directly or via the MN indirectly, e.g. via an indication or a message.
  • the MN may determine whether the received information from the UE is used for MRO based on the above criteria associated with ratio SCG . When the criteria is fulfilled, i.e. ratio SCG is greater than the threshold, the information may be discarded, and ignored for MRO.
  • the MN may not transmit the information received from the UE to the last serving SN or the source SN.
  • the MN may transmit the information received from the UE to the last serving SN or the source SN as well as an optional indication indicating the information is ignored for MRO.
  • the information may be used for MRO, and the MN may transmit the information to the last serving SN or the source SN, and may also transmit an indication to the last serving SN or the source SN indicating the information is used for MRO, i.e. to modify the mobility related configuration, then the source SN or the last serving SN may modify PSCell change or CPAC related configurations, for example, modify the RSRP threshold, the RSRQ threshold, or the SINR threshold for PSCell change or CPAC execution condition.
  • the MN may also transmit a message or an indication indicating the last serving SN or the source SN to modify the configuration associated with LBT. For example, the MN may inform the last serving SN or the source SN to modify the RSSI or CO measurement configuration, or other measurement configuration associated with LBT, e.g. via an indication or a message. Also, the MN may inform the target SN to update the configuration for LBT failure recovery, e.g. via an indication or a message.
  • the UE may store the information as in Embodiment 2-1, for example, the UE may store the Period A and Period B, etc.
  • the UE may determine whether the information may be used for MRO, for LBT related configuration modification, or both.
  • the UE may also use the same criteria in embodiment 2-1 for determining whether the information may be used for MRO, for LBT related configuration modification, or both.
  • the UE may determine whether the ratio (e.g. ratio SCG ) is greater than a threshold or not, which may be configured to the UE by the network, for example, the threshold may be configured by the MN or the source SN via an RRC signalling (aPSCell change command or a CPAC command, e.g. RRCReconfiguration message with reconfigurationWithSync for the SCG) , or by UE implementation.
  • the threshold may be pre-configured, or defined in the specification.
  • the UE may determine that the criteria is met, i.e. the ratio (e.g. ratio SCG ) is greater than the threshold, and the information may be ignored for MRO.
  • the UE may transmit the information as in Embodiment 2-1 to the MN, and the UE may further store and/or transmit at least one of the following indications to the MN:
  • This indication may be stored and/or transmitted in any one of the above cases A-C;
  • this indication may be stored and/or transmitted in the above case A-C) , or a consistent LBT failure in the RRC layer (this indication may be stored and/or transmitted in the above case C) .
  • the MN may take the following options:
  • the MN may discard the received information, and not take this information into account for MRO.
  • the MN may decide the configuration associated with LBT needs to be modified, then the MN then may modify the RSSI measurement, the CO measurement configuration, or other configurations associated with LBT.
  • the MN may also inform the target SN to update the configuration for LBT failure recovery or other configurations associated with LBT, e.g. via a message or an indication.
  • the MN may discard the received information, and not transmit the information received from the UE to the source SN or the last serving SN.
  • the MN may decide the NR-U related configuration needs to be modified.
  • the MN may modify the RSSI measurement or the CO measurement configuration or other configurations associated with LBT.
  • the MN may inform the target SN to update the configuration for LBT failure recovery or other configurations associated with LBT, e.g. via a message or an indication.
  • the MN may transmit the received information from the UE to the last serving SN or the source SN. Based on the received information, the last serving SN or the source SN may discard the received information, or not take the received information into account for MRO.
  • the last serving SN or the source SN may decide the configuration associated with LBT needs to be modified, the last serving SN or the source SN may modify the RSSI measurement or the CO measurement configuration or other configurations associated with LBT.
  • the last serving SN or the source SN may inform the MN to modify the RSSI measurement or the CO measurement configuration or other configurations associated with LBT, e.g. via a message or an indication.
  • the last serving SN or the source SN may also inform target SN to update the configuration for LBT failure recovery or other configurations associated with LBT recovery directly or via the MN, e.g. via a message or an indication.
  • the UE when the UE determines that the criteria is met, i.e. the ratio (e.g. ratio SCG ) is greater than the threshold, the above stored information may be ignored for MRO, the UE may not transmit the above stored information to the MN, rather, the UE may discard (or remove, release, etc.
  • the UE may discard all stored information (including non-LBT related information as legacy in licensed system and the above stored LBT related information) , the UE may discard the SCG failure information message, or may not transmit the SCG failure information message.
  • the UE may transmit an SCG failure information message without the above information (e.g. the UE only transmits non-LBT related information as legacy in a licensed system, but without the above stored LBT related information) .
  • Fig. 2 illustrates a method performed by a UE for wireless communication according to some embodiments of the present disclosure.
  • the UE may store information including one of the following: a first period of time elapsed since a last HO execution until an event; or a second period of time elapsed since a last PSCell change execution until the event; wherein the event includes at least one of the following: a successful LBT procedure, a preamble transmission, MSG3 transmission, or MSGA transmission.
  • the UE may store the first period of time, i.e. Period 1.
  • the UE may also store the second period of time, i.e. Period A.
  • the UE may perform one of the following operations: transmit the information to a RAN node; or determine whether the information is used for MRO.
  • the UE may transmit Period 1 or Period 2 to a receiving RAN node.
  • the UE may determine whether the information is used for MRO based on certain criteria associated with Period 1 or Period 2.
  • the UE may transmit Period A or Period B to a receiving RAN node.
  • the UE may determine whether the information is used for MRO based on certain criteria associated with Period A or Period B.
  • the information further includes at least one of the following:
  • determining whether the information is used for MRO based on a criteria includes a ratio being greater than a threshold, wherein the ratio is determined based on the first period of time and a third period of time, and the third period of time includes a period of time elapsed since a last HO execution until a connection failure; or wherein the ratio is determined based on the second period of time and a fourth period of time, and the fourth period of time includes a period of time elapsed since a last PSCell change execution until a connection failure.
  • the criteria is calculated based on function (1) , i.e.
  • ratio HO is determined based on the first period of time (Period 1) and the third period of time (Period 2) .
  • the criteria is calculated based on function (3) , i.e. and the ratio (ratio SCG ) is determined based on the second period of time (Period A) and the fourth period of time (Period B) .
  • the information is included in at least one of the following:
  • the UE may store or transmit at least one of the following:
  • an indication indicating a connection failure is due to LBT failure.
  • the UE may discard the information in the case that the criteria is fulfilled.
  • Fig. 3 illustrates a method performed by a RAN node for wireless communication according to some embodiments of the present disclosure.
  • the RAN node may receive information from a UE including one of the following: a first period of time elapsed since a last HO execution until an event; or a second period of time elapsed since a last PSCell change execution until the event; wherein the event includes at least one of the following: a successful LBT procedure, a preamble transmission, MSG3 transmission, or MSGA transmission.
  • the RAN node may perform one of the following operations: transmit the information to another RAN node; determine whether the information is used for MRO; indicate another RAN node to modify the configuration associated with LBT; or perform MRO based on the information.
  • the RAN node may be the receiving RAN node, and the receiving RAN node may transmit the information to the source RAN node.
  • the receiving RAN node may determine whether the information is used for MRO.
  • the receiving RAN node may indicate the source RAN node to modify the configuration associated with LBT.
  • the RAN node may be a MN, and may perform MRO based on the information.
  • the RAN node may discard the information in the case that an indication indicating the information is ignored for MRO is received.
  • the RAN node may discard the information; or transmit an indication indicating another RAN node to modify the configuration associated with LBT. In the case that the criteria is not fulfilled, the RAN node may transmit the information to another RAN node; or transmit an indication indicating another RAN node to modify the mobility related configuration.
  • Fig. 4 illustrates a method performed by a RAN node for wireless communication according to some embodiments of the present disclosure.
  • the RAN node may receive information from another RAN node including at least one of the following: a first period of time elapsed since a last HO execution until an event; a second period of time elapsed since a last PSCell change execution until the event; or a message or an indication indicating configuration associated with LBT needs to be modified; wherein the event includes at least one of the following: an LBT procedure, a preamble transmission, MSG3 transmission, or MSGA transmission.
  • the information may include one of the following:
  • the RAN node may perform one of the following operations: determine whether the information is used for MRO; or perform MRO based on the information.
  • the source RAN node may receive information from the receiving RAN node, and may determine whether the information is used for MRO; or perform MRO based on the information.
  • the RAN node may be configured to discard the information in the case that the indication indicating the information is ignored for MRO is received.
  • the RAN node in the case that the criteria is not fulfilled, may modify the mobility related configuration; or in the case that the criteria is fulfilled, the RAN node may discard the information, or modify the configuration associated with LBT.
  • Fig. 5 illustrates a simplified block diagram of an exemplary apparatus according to some embodiments of the present disclosure.
  • an example of the apparatus 500 may include at least one processor 504 and at least one transceiver 502 coupled to the processor 504.
  • the apparatus 500 may be a UE, a BS, a RAN node, a MN, an SN, or any other device with similar functions.
  • the transceiver 502 may be divided into two devices, such as a receiving circuitry and a transmitting circuitry.
  • the apparatus 500 may further include an input device, a memory, and/or other components.
  • the apparatus 500 may be a UE.
  • the transceiver 502 and the processor 504 may interact with each other so as to perform the operations of the UE described in any of Figs. 1-4.
  • the apparatus 500 may be a node.
  • the transceiver 502 and the processor 504 may interact with each other so as to perform the operations of the node described in any of Figs. 1-4.
  • the apparatus 500 may further include at least one non-transitory computer-readable medium.
  • the non-transitory computer-readable medium may have stored thereon computer-executable instructions to cause the processor 504 to implement the method with respect to the UE as described above.
  • the computer-executable instructions when executed, cause the processor 504 interacting with transceiver 502 to perform the operations of the UE described in any of Figs. 1-4.
  • the non-transitory computer-readable medium may have stored thereon computer-executable instructions to cause the processor 504 to implement the method with respect to the node as described above.
  • the computer-executable instructions when executed, cause the processor 504 interacting with transceiver 502 to perform the operations of the node described in any of Figs. 1-4.
  • controllers, flowcharts, and modules may also be implemented on a general purpose or special purpose computer, a programmed microprocessor or microcontroller and peripheral integrated circuit elements, an integrated circuit, a hardware electronic or logic circuit such as a discrete element circuit, a programmable logic device, or the like.
  • any device that has a finite state machine capable of implementing the flowcharts shown in the figures may be used to implement the processing functions of the present disclosure.

Landscapes

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

Abstract

La présente invention concerne des procédés et des appareils pour des améliorations de réseau d'auto-optimisation (SON) pour nouvelle radio sans licence (NR-U). Un mode de réalisation de la présente invention concerne un équipement utilisateur (UE), qui comprend: un émetteur-récepteur; et un processeur couplé à l'émetteur-récepteur et configuré pour: stocker une information comprenant un parmi les éléments suivants: une première période de temps écoulée depuis une dernière exécution de transfert intercellulaire (HO) jusqu'à un événement; ou une seconde période de temps écoulée depuis qu'une dernière cellule de groupe de cellules secondaires (SCG) primaire (PSCell) change d'exécution jusqu'à l'événement; l'événement comprenant au moins un des éléments suivants: une procédure d'écoute avant de parler (LBT) réussie, une transmission de préambule, une transmission de norme MSG3 ou une transmission MSGA; et effectuer une des opérations suivantes: transmettre l'information à un noeud d'accès radio (RAN); ou déterminer si l'information est utilisée pour une opération MRO.
PCT/CN2022/099832 2022-06-20 2022-06-20 Procédés et appareils pour des améliorations de réseau d'auto-optimisation WO2023245338A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2022/099832 WO2023245338A1 (fr) 2022-06-20 2022-06-20 Procédés et appareils pour des améliorations de réseau d'auto-optimisation

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2022/099832 WO2023245338A1 (fr) 2022-06-20 2022-06-20 Procédés et appareils pour des améliorations de réseau d'auto-optimisation

Publications (1)

Publication Number Publication Date
WO2023245338A1 true WO2023245338A1 (fr) 2023-12-28

Family

ID=89378979

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/099832 WO2023245338A1 (fr) 2022-06-20 2022-06-20 Procédés et appareils pour des améliorations de réseau d'auto-optimisation

Country Status (1)

Country Link
WO (1) WO2023245338A1 (fr)

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102804840A (zh) * 2009-06-22 2012-11-28 高通股份有限公司 使用 son 解决方案进行网络优化的方法和装置
CN103428783A (zh) * 2012-05-22 2013-12-04 北京三星通信技术研究有限公司 支持检测rlf或者切换失败原因的方法
CN107666672A (zh) * 2016-07-26 2018-02-06 中兴通讯股份有限公司 鲁棒性的优化方法、装置及系统
US20190387546A1 (en) * 2018-06-14 2019-12-19 Samsung Electronics Co., Ltd. Method and apparatus on enhancements of nr random access for unlicensed operations
CN113767710A (zh) * 2019-03-28 2021-12-07 瑞典爱立信有限公司 基于dl cca操作信息适配ue服务小区过程
WO2022057783A1 (fr) * 2020-09-16 2022-03-24 夏普株式会社 Procédé de rapport de défaillance de liaison radio et équipement utilisateur

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102804840A (zh) * 2009-06-22 2012-11-28 高通股份有限公司 使用 son 解决方案进行网络优化的方法和装置
CN103428783A (zh) * 2012-05-22 2013-12-04 北京三星通信技术研究有限公司 支持检测rlf或者切换失败原因的方法
CN107666672A (zh) * 2016-07-26 2018-02-06 中兴通讯股份有限公司 鲁棒性的优化方法、装置及系统
US20190387546A1 (en) * 2018-06-14 2019-12-19 Samsung Electronics Co., Ltd. Method and apparatus on enhancements of nr random access for unlicensed operations
CN113767710A (zh) * 2019-03-28 2021-12-07 瑞典爱立信有限公司 基于dl cca操作信息适配ue服务小区过程
WO2022057783A1 (fr) * 2020-09-16 2022-03-24 夏普株式会社 Procédé de rapport de défaillance de liaison radio et équipement utilisateur

Similar Documents

Publication Publication Date Title
CN111034302B (zh) 用于波束故障恢复的随机接入的方法和设备
EP3171632B1 (fr) Dispositif et procédé de gestion de défaillance de communication
EP3442304A1 (fr) Procédé de manipulation d'une liaison radio défaillante et dispositif de communication associé
EP2540109B1 (fr) Détection de défaillance de liaison radio (rlf) pour la récupération
US20240073755A1 (en) Method and apparatus for performing handover procedure
US11546816B2 (en) Method and apparatus for performing a handover procedure
WO2021138905A1 (fr) Procédé de gestion de défaillance dans un transfert intercellulaire conditionnel
WO2023130315A1 (fr) Procédés et appareils de mro pour un changement de cellule primaire secondaire ou cpac dans nr-u
US20230422135A1 (en) Method and apparatus for mobility robustness optimization
US20230141380A1 (en) Method and apparatus for sidelink resource re-evaluation
US20220377630A1 (en) Method and apparatus for performing mobility robustness optimization in a handover procedure
WO2023245338A1 (fr) Procédés et appareils pour des améliorations de réseau d'auto-optimisation
US20230362778A1 (en) Methods and apparatuses of a mobility robustness optimization mechanism for a conditional handover procedure
WO2022155955A1 (fr) Procédé et appareil pour déterminer un type de défaillance
WO2024082418A1 (fr) Procédés et appareils prenant en charge une commutation de cellule ltm
WO2023065146A1 (fr) Procédés et appareils permettant d'améliorer un mécanisme mdt pour une procédure sdt
WO2024082498A1 (fr) Procédés et appareils pour maintenir des valeurs de ta
US20230422137A1 (en) Methods and apparatuses for a daps failure recovery mechanism and a mro mechanism for cho and daps procedures
US20230397297A1 (en) Methods and apparatuses for a scg deactivation mechanism and a scg activation mechanism in a mr-dc scenario
WO2024011586A1 (fr) Procédés et appareils pour apporter des améliorations à un shr
WO2024074038A1 (fr) Procédé et appareil d'acquisition d'avance temporelle
WO2023065119A1 (fr) Procédés et appareil pour procédures de récupération après défaillance de faisceau à base de trp, et mro
EP4312452A1 (fr) Gestion de préparations de transfert conditionnel dans des scénarios de défaillance
WO2024087416A1 (fr) Procédés et appareils pour une procédure conditionnelle de commutation de cellule
WO2024065529A1 (fr) Procédés et appareils pour un mécanisme d'amélioration de surveillance de pdcch pour un trafic xr

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: 22947119

Country of ref document: EP

Kind code of ref document: A1