WO2024073980A1 - Procédés et appareils pour des améliorations de son - Google Patents

Procédés et appareils pour des améliorations de son Download PDF

Info

Publication number
WO2024073980A1
WO2024073980A1 PCT/CN2023/072712 CN2023072712W WO2024073980A1 WO 2024073980 A1 WO2024073980 A1 WO 2024073980A1 CN 2023072712 W CN2023072712 W CN 2023072712W WO 2024073980 A1 WO2024073980 A1 WO 2024073980A1
Authority
WO
WIPO (PCT)
Prior art keywords
report
format
pscell
target
information
Prior art date
Application number
PCT/CN2023/072712
Other languages
English (en)
Inventor
Le Yan
Mingzeng Dai
Lianhai WU
Shuigen Yang
Yibin ZHUO
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/CN2023/072712 priority Critical patent/WO2024073980A1/fr
Publication of WO2024073980A1 publication Critical patent/WO2024073980A1/fr

Links

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
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/10—Scheduling measurement reports ; Arrangements for measurement reports
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/15—Setup of multiple wireless link connections

Definitions

  • the present disclosure relates to wireless communication, and particularly relates to methods and apparatuses for self-organizing network (SON) enhancements.
  • SON self-organizing network
  • a report of a successful PSCell change, a successful PSCell addition, a successful conditional PSCell addition (CPA) , or a successful conditional PSCell change (CPC) may be referred to as an SPR, and they may be used for SON enhancements in the MR-DC scenario.
  • E-UTRAN evolved universal terrestrial radio access network
  • NG-RAN next-generation radio access network
  • NGEN-DC next-generation radio access network
  • NE-DC NR-E-UTRAN dual connectivity
  • MN master node
  • SN secondary node
  • a user equipment which includes: a transceiver; and a processor coupled with the transceiver and configured to: receive a configuration regarding first information associated with a successful PSCell change, a successful PSCell addition, a successful CPA, or a successful CPC in an MR-DC scenario, wherein an MN and an SN in the MR-DC scenario utilize different radio access technologies (RATs) , and the configuration is related to one or more trigger conditions for storing the first information; and generate a report including the first information in the MR-DC scenario when at least one trigger condition within the one or more trigger conditions is fulfilled.
  • RATs radio access technologies
  • the processor is further configured to: transmit an indication for indicating a UE capability, which indicates that the UE is able to store the first information or generate the report in the MR-DC scenario.
  • the processor is further configured to: encode the report or the first information with one of the following format: an RAT format of the MN; an RAT format of NR; an RAT format of the MN, wherein a trigger condition within the one or more trigger conditions is generated by the MN, and the trigger condition is fulfilled; or an RAT format of an SN, wherein a trigger condition within the one or more trigger conditions is generated by the SN, and the trigger condition is fulfilled, and the SN is a source SN or a target SN.
  • the RAT format of the MN or the RAT format of the SN is one of: a format of an evolved universal terrestrial radio access network (E-UTRAN) ; a format of new radio (NR) ; or a format of a next generation.
  • E-UTRAN evolved universal terrestrial radio access network
  • NR new radio
  • the one or more trigger conditions in response to a trigger condition within the one or more trigger conditions is generated by the target SN, include a first threshold associated with timer T304.
  • the one or more trigger conditions in response to a trigger condition within the one or more trigger conditions is generated by the MN or the source SN, include at least one of a second threshold associated with timer T310; or a third threshold associated with timer T312.
  • the processor is further configured to: transmit, the report, or both the report and at least one of cell information associated with a source PSCell or cell information associated with a target PSCell.
  • the report or the first information includes at least one of the following: information associated with a source PSCell; information associated with a target PSCell; information associated with one or more neighbor cells; a cause value indicating which trigger condition for storing the first information is fulfilled; time information associated with the successful CPA or the successful CPC; UE location information; or information associated with a random access procedure to the target PSCell.
  • the cell information includes at least one of the following: a public land mobile network (PLMN) identity (ID) ; a cell ID; a tracking area code (TAC) ; a physical cell identifier (PCI) ; or an absolute radio frequency channel number (ARFCN) .
  • PLMN public land mobile network
  • ID a cell ID
  • TAC tracking area code
  • PCI physical cell identifier
  • ARFCN absolute radio frequency channel number
  • the processor is further configured to: transmit an indication indicating an availability of the report; receive a request for the report; and transmit the report.
  • an MN which includes: a transceiver; and a processor coupled with the transceiver and configured to:determine a configuration regarding first information associated with a successful PSCell change, a successful PSCell addition, a successful CPA, or a successful CPC in an MR-DC scenario, wherein the MN and an SN in the MR-DC scenario utilize different RATs, and the configuration is related to one or more trigger conditions for storing the first information or generating a report including the first information; and transmit, to a UE, the configuration regarding the first information.
  • the processor is further configured to: receive, from the UE, an indication for indicating a UE capability, which indicates that the UE is able to store the first information or generate the report in the MR-DC scenario.
  • the processor is further configured to: receive, from each of one or more candidate target secondary nodes (SNs) , a first threshold associated with timer T304; and determine the configuration.
  • SNs candidate target secondary nodes
  • the processor is further configured to perform one of the following: generate at least one of a second threshold associated with timer T310, or a third threshold associated with timer T312; and determine the configuration; receive, from a source SN, at least one of a second threshold associated with timer T310, or a third threshold associated with timer T312; and determine the configuration; generate a second threshold associated with timer T310; receive, from the source SN, a third threshold associated with timer T312; and determine the configuration; or generate a third threshold associated with timer T312; receive, from the source SN, a second threshold associated with timer T310; and determine the configuration.
  • the processor is further configured to perform one of the following: receive, from the UE or a target SN, the report or the first information; or receive, from the UE or the target SN, the report or the first information, and at least one of cell information associated with a source PSCell or cell information associated with a target PSCell.
  • the report or the first information includes at least one of the following: information associated with a source PSCell; information associated with a target PSCell; information associated with one or more neighbor cells; a cause value indicating which trigger condition for storing the first information is fulfilled; time information associated with the successful CPA or the successful CPC; UE location information; or information associated with a random access procedure to the target PSCell.
  • the cell information associated with a source PSCell or the cell information associated with a target PSCell includes at least one of the following: a PLMN ID; a cell ID; a TAC; a PCI; or an ARFCN.
  • the processor is further configured to: receive, from the UE, an indication indicating an availability of the report; transmit, to the UE, a request for the report; and receive, from the UE, the report.
  • the report is encoded with a first format
  • the processor is further configured to perform one of the following: decode the report encoded with the first format for mobility robustness optimization (MRO) ; transmit the report encoded with the first format to a source SN, a target SN, or both the source SN and the target SN; decode the report encoded with the first format, re-encode the decoded report with a second format of the target SN, and transmit the report encoded with the second format to the target SN; decode the report encoded with the first format, re-encode the decoded report with a third format of the source SN, and transmit the report encoded with the third format to the source SN; decode the report encoded with the first format, re-encode the decoded report with the second format of the target SN, re-encode the decoded report with the third format of the source SN, transmit the report encoded with the second format to the target SN, and transmit the report encoded with the third
  • the first format, the second format, or the third format is one of: a format of an E-UTRAN; a format of NR; or a format of a next generation.
  • the processor is further configured to perform one of the following: transparently transmit the report to a target SN based on cell information associated with the target PSCell in response to the cell information associated with the target PSCell is received; transparently transmit the report to a source SN based on cell information associated with the source PSCell in response to the cell information associated with the source PSCell is received; or transparently transmit the report to the target SN based on cell information associated with the target PSCell and transparently transmit the report to the source SN based on cell information associated with the source PSCell in response to the cell information associated with the target PSCell and the cell information associated with the source PSCell are received.
  • an SN which includes: a transceiver; and a processor coupled with the transceiver and configured to: determine at least one trigger condition for storing first information associated with a successful PSCell change or PSCell addition or CPA or CPC in an MR-DC scenario, wherein an MN and the SN in the MR-DC scenario utilize different RATs; and transmit, to the MN or a UE, the at least one trigger condition.
  • the SN is a target SN
  • the at least one trigger condition includes a first threshold associated with timer T304.
  • the SN is a target SN
  • the processor is further configured to perform one of the following: receive a report including the first information from the UE; receive a report including the first information from the MN, wherein the report is encoded with an RAT format of the SN; receive a report including the first information from the MN, wherein the report is encoded with an RAT format of the MN; receive a report including the first information from the MN, wherein the report is encoded with an RAT format of the SN by the MN; or receive explicit information including the first information from the MN.
  • the SN is a source SN
  • the at least one trigger condition includes at least one of a second threshold associated with timer T310, or a third threshold associated with timer T312.
  • the SN is a source SN
  • the processor is further configured to perform one of the following: receive a report including the first information from the MN, wherein the report is encoded with an RAT format of the SN; receive a report including the first information from the MN, wherein the report is encoded with an RAT format of the MN; receive a report including the first information from the MN, wherein the report is encoded with an RAT format of the SN by the MN; or receive explicit information including the first information from the MN.
  • the first information includes at least one of the following: information associated with a source PSCell; information associated with a target PSCell; information associated with one or more neighbor cells; a cause value indicating which trigger condition for storing the first information is fulfilled ; time information associated with the successful CPA or the successful CPC; UE location information; or information associated with a random access procedure to the target PSCell.
  • the RAT format of the MN or the RAT format of the SN is one of: a format of an E-UTRAN; a format of NR; or a format of a next generation.
  • Yet another embodiment of the present disclosure provides a method performed by a UE which includes: receiving a configuration regarding first information associated with a successful PSCell change, a successful PSCell addition, a successful CPA, or a successful CPC in a multi-radio dual connectivity (MR-DC) scenario, wherein an MN and an SN in the MR-DC scenario utilize different RATs, and the configuration is related to one or more trigger conditions for storing the first information; and generating a report including the first information in the MR-DC scenario when at least one trigger condition within the one or more trigger conditions is fulfilled.
  • MR-DC multi-radio dual connectivity
  • Yet another embodiment of the present disclosure provides a method performed by an MN which includes: determining a configuration regarding first information associated with a successful PSCell change, a successful PSCell addition, a successful CPA, or a successful CPC in an MR-DC scenario, wherein the MN and an SN in the MR-DC scenario utilize different RATs, and the configuration is related to one or more trigger conditions for storing the first information or generating a report including the first information; and transmitting, to a UE, the configuration regarding the first information.
  • Yet another embodiment of the present disclosure provides a method performed by an SN which includes: determining at least one trigger condition for storing first information associated with a successful PSCell change or PSCell addition or CPA or CPC in an MR-DC scenario, wherein an MN and the SN in the MR-DC scenario utilize different RATs; and transmitting, to the MN or the UE, the at least one trigger condition.
  • 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 SON enhancements according to some embodiments of the present disclosure.
  • Fig. 3 illustrates a method performed by an MN for SON enhancements according to some embodiments of the present disclosure.
  • Fig. 4 illustrates a method performed by an SN for SON enhancements according to some embodiments of the present disclosure.
  • Fig. 5 illustrates a simplified block diagram of an apparatus according to some embodiments of the present disclosure.
  • Fig. 1 illustrates an MR-DC system according to some embodiments of the present disclosure.
  • the MR-DC system may include an MN (e.g., MN 102) , a UE (e.g., UE 101) , and an SN (e.g., SN 104) .
  • MN e.g., MN 102
  • UE e.g., UE 101
  • SN e.g., SN 104
  • the MN and SN are connected via a network interface (for example, an Xn interface or an X2 interface as specified in 3GPP standard documents) , and at least the MN is connected to the core network.
  • the MN and the SN may perform communications with different technologies.
  • the MN may perform communication with the UE with E-UTRAN (4G) air-interface and protocols
  • the SN e.g., an en-gNB or a gNB
  • the MN may perform communication with the UE with NR (5G) air-interface and protocols
  • the MN e.g., a gNB
  • the SN e.g., an ng-eNB
  • the MN may perform communication with the UE with E-UTRAN (4G) air-interface and protocols
  • the SN e.g., an ng-eNB
  • MN 102 may refer to a radio access node that provides a control plane connection to the core network.
  • MN 102 in the EN-DC scenario, MN 102 may be an eNB.
  • MN 102 in the NGEN-DC scenario, MN 102 may be an ng-eNB.
  • MN 102 in the NE-DC scenario or the NR-NR dual connectivity (NR-DC) scenario, MN 102 may be a gNB.
  • SN 104 may refer to a radio access node without a control plane connection to the core network but providing additional resources to UE 101.
  • SN 104 in the EN-DC scenario, may be an en-gNB.
  • SN 104 in the NE-DC scenario, may be an ng-eNB.
  • SN 104 in the NR-DC scenario or the NGEN-DC scenario, may be a gNB.
  • MR-DC system in the present disclosure may include any MR-DC cases, for example, the MN may perform communication with the UE with 6G technology while the SN may perform communication with the UE with 4G or 5G technologies, or vice versa.
  • Other different types of communication technologies are not limited.
  • the UEs may be 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
  • SCell secondary cell
  • SCG secondary cell group
  • the UEs 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, and modems) , or the like.
  • the UEs 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 UEs include wearable devices, such as smart watches, fitness bands, optical head-mounted displays, or the like.
  • the UEs may be referred to as a subscriber unit, a mobile phone, a mobile station, a user, a terminal, a mobile terminal, a wireless terminal, a fixed terminal, a subscriber station, a user terminal, or any device described using other terminology used in the art.
  • the UEs may communicate directly with the MN and the SN via uplink communication signals.
  • the MN and the SN may be distributed over a geographic region.
  • the MN and the SN may also be referred to as an access point, an access terminal, a base, a macro cell, a Node-B, an enhanced Node B (eNB) , a gNB, a Home Node-B, a relay node, or any device described using other terminology used in the art.
  • eNB enhanced Node B
  • the MR-DC system is compatible with any type of network that is capable of sending and receiving wireless communication signals.
  • the MR-DC system is compatible 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, an LTE network, a 3 rd generation partnership project (3GPP) -based network, a 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
  • the MR-DC system is compatible with the 5G NR of the 3GPP protocol, wherein the MN and the SN transmit data using an OFDM modulation scheme on the downlink and the UE transmits data on the uplink using discrete Fourier transform-spread-orthogonal frequency division multiplexing (DFT-S-OFDM) or cyclic prefix-orthogonal frequency division multiplexing (CP-OFDM) scheme.
  • DFT-S-OFDM discrete Fourier transform-spread-orthogonal frequency division multiplexing
  • CP-OFDM cyclic prefix-orthogonal frequency division multiplexing
  • the MR-DC system may implement some other open or proprietary communication protocols, for example, WiMAX, among other protocols.
  • the UE may perform a PSCell change procedure, a PSCell addition procedure, a CPA procedure, or a CPC procedure.
  • the detailed processes of these procedures may be referred to the 3GPP documents, such as 3GPP release 15 specification, 3GPP release 16 specification and 3GPP release 17 specifications.
  • a report may be stored (or logged, generated, or reported) .
  • the expression "report" or "SPR" may refer to any one of the successful PSCell change report, the successful PSCell addition report, the successful CPA report, or the successful CPC report for simplicity, and the SPR may be triggered by one or more trigger conditions.
  • the UE may store (or log, generate, or report) information associated with the successful PSCell change, the successful PSCell addition, the successful CPA, or the successful CPC, and may store (or log, generate, or report) the report (e.g., the SPR) including the information, then transmit the report (e.g., the SPR) or the information to the MN, to the source SN, or to the target SN.
  • the report e.g., the SPR
  • the UE capability for the report e.g., the SPR
  • the information e.g., the information
  • RAN node may decide, generate, or configure the one or more trigger conditions
  • the report e.g., the SPR
  • the information which may include:
  • the report e.g., the SPR
  • the information e.g., the information
  • Embodiment 1 generally relates to how to trigger the report (e.g., the SPR) or how to trigger the UE storing the information associated with a successful PSCell change, a successful PSCell addition, a successful CPA, or a successful CPC in an MR-DC scenario.
  • the report e.g., the SPR
  • the report in an MR-DC scenario can be called as an inter-RAT SPR.
  • Embodiment 1-1 generally relates to the UE capability for storing or logging the information or the report in an MR-DC scenario.
  • Pre-configuration e.g., an information element (IE) such as successInterRATSPR-Config IE
  • the report e.g. the inter-RAT SPR
  • the network may need to know the UE capability in order to configure a proper configuration to trigger the report (e.g. the inter-RATSPR) or trigger the UE to store the information associated with a successful PSCell change, a successful PSCell addition, a successful CPA, or a successful CPC in an MR-DC scenario.
  • IE information element
  • successInterRATSPR-Config IE successInterRATSPR-Config IE
  • the network may need to know the UE capability in order to configure a proper configuration to trigger the report (e.g. the inter-RATSPR) or trigger the UE to store the information associated with a successful PSCell change, a successful PSCell addition, a
  • storing (or logging, generating, or reporting) the report (e.g., the SPR in an MR-DC scenario or the inter-RAT SPR) or the information associated with a successful PSCell change, a successful PSCell addition, a successful CPC, or a successful CPA in the MR-DC scenario is optional even if the UE support the PSCell change, the PSCell addition, CPC, or the CPA in the MR-DC scenarios.
  • the UE may transmit an indication to the network (for example, the MN, or the source SN) , to indicate a UE capability.
  • the UE capability may indicate that the UE is able to store (or log, generate, or report) the report (e.g., the SPR in an MR-DC scenario or the inter-RAT SPR) or the information associated with a successful PSCell change, a successful PSCell addition, a successful CPC, or a successful CPA in the MR-DC scenario.
  • the UE capability may be explicitly signalled to network, i.e., an explicit capability signalling is needed, or an optional UE capability with signalling is needed.
  • the UE may transmit a message, for example, a UECapabilityInformation message, which may include an optional UE capability indication indicating the UE capability to the network.
  • a message for example, a UECapabilityInformation message, which may include an optional UE capability indication indicating the UE capability to the network.
  • the UE capability may be implicitly signalled to network, i.e., an optional UE capability without signalling is needed.
  • the UE may reuse an existing indication to indicate the UE capability, e.g. an existing optional UE capability indication for intra-NR SPR may be reused , for indicating that the UE is able to store (or log, generate, or report) the information associated with a successful PSCell change, a successful PSCell addition, a successful CPC, or a CPA or the report in the EN-DC scenario, the NGEN-DC scenario, the NE-DC scenario or a evolved MR-DC scenario.
  • some types of UEs are capable of storing (or logging, generating, or reporting) the report (e.g., the SPR in an MR-DC scenario or the inter-RAT SPR) or the information associated with a successful PSCell change, a successful PSCell addition, a successful CPC, or a successful CPA, for example, a UE that performs wireless communication with NR (5G) air-interface and protocols. Therefore, these types of UE may not transmit the indication indicating the UE capability.
  • the network may transmit a message, e.g., an RRC reconfiguration message or an RRC connection reconfiguration message, to the UE, which may include configurations (e.g., an InterRATSPR-Config IE) for the UE to store (or log, generate, or report) information associated with a successful PSCell change, a successful PSCell addition, a successful CPC, or a successful CPA, or a report in the MR-DC scenarios (e.g., an SPR in an MR-DC scenario or an inter-RAT SPR) .
  • a message e.g., an RRC reconfiguration message or an RRC connection reconfiguration message
  • configurations e.g., an InterRATSPR-Config IE
  • the message may include one or more trigger conditions for triggering the UE to store (or log, generate, or report) information associated with a successful PSCell change, a successful PSCell addition, a successful CPC, or a successful CPA, or a report (e.g., an SPR in an MR-DC scenario or an inter-RAT SPR) , which means that when at least one trigger condition is fulfilled, the UE may store (or log, generate, or report) the report (e.g., an SPR in an MR-DC scenario or an inter-RAT SPR) .
  • the one or more trigger conditions may include at least one of the following:
  • the first threshold may be a percentage value
  • the UE may store (or log, generate, or report) the report (e.g., an SPR in an MR-DC scenario or an inter-RAT SPR) when the ratio between the value of the elapsed time of the timer T304 (e.g. related with target PSCell) and the configured value of the timer T304 (e.g. related with target PSCell, and may be included in the last RRC message for a PSCell change, a PSCell addition, a CPC, or a CPA procedure) , is greater than the first threshold (e.g. the first threshold may be included in the last RRC message before executing the PSCell change, PSCell addition, CPC, or CPA procedure) .
  • the report e.g., an SPR in an MR-DC scenario or an inter-RAT SPR
  • the first threshold may be an absolute value
  • the UE may store (or log, generate, or report) the report (e.g., an SPR in an MR-DC scenario or an inter-RAT SPR) when the elapsed time of the timer T304 (e.g. related with target PSCell) is greater than the first threshold (e.g. the first threshold may be included in the last RRC message before executing the PSCell change, PSCell addition, CPC, or CPA procedure) .
  • the first threshold associated with timer T304 may also be referred to as "the first trigger condition associated with timer T304" .
  • timer T310 a second threshold associated with timer T310, which may be decided or generated by the MN or the source SN;
  • the second threshold may be a percentage value
  • the UE may store (or log, generate, or report) the report (e.g., an SPR in an MR-DC scenario or an inter-RAT SPR) when the ratio between the value of the elapsed time of the timer T310 (e.g. related with source PSCell) and the configured value of the timer T310 (e.g. related with source PSCell) , configured while the UE was connected to the source SN before executing the PSCell change, PSCell addition, CPC, or CPA procedure, is greater than the second threshold (e.g. the second threshold may be included in the RRC message before executing the PSCell change, PSCell addition, CPC, or CPA procedure) .
  • the second threshold may be included in the RRC message before executing the PSCell change, PSCell addition, CPC, or CPA procedure
  • the second threshold may be an absolute value
  • the UE may store (or log, generate, or report) the report (e.g., an SPR in an MR-DC scenario or an inter-RAT SPR) when the elapsed time of the timer T310 (e.g. related with source PSCell) is greater than the second threshold (e.g. the first threshold may be included in the last RRC message before executing the PSCell change, PSCell addition, CPC, or CPA procedure) .
  • the report e.g., an SPR in an MR-DC scenario or an inter-RAT SPR
  • the second threshold associated with timer T310 may also be referred to as "the second trigger condition associated with timer T310" .
  • timer T312 a third threshold associated with timer T312, which may be decided or generated by the MN or the source SN.
  • the third threshold may be a percentage value
  • the UE may store (or log, generate, or report) the report (e.g., an SPR in an MR-DC scenario or an inter-RAT SPR) when the timer T312 associated with the measurement identity of the target PSCell was running at the time of initiating the PSCell change, the PSCell addition, the CPC, or the CPA procedure, and the ratio between the value of the elapsed time of the timer T312 and the configured value of the timer T312, configured while the UE was connected to the source PSCell before executing the last PSCell change, the last PSCell addition, the last CPC, or the last CPA procedure, is greater than the third threshold (which may be included in the RRC message before executing the PSCell change, PSCell addition, CPC, or CPA procedure, and it may be decided or generated by the MN or source SN before executing the last PSCell change, the last PSCell addition, the last CPC, or the last CPA procedure
  • the third threshold may be an absolute value
  • the UE may store (or log, generate, or report) the report (e.g., an SPR in an MR-DC scenario or an inter-RAT SPR) when the timer T312 associated with the measurement identity of the target PSCell was running at the time of initiating the PSCell change, the PSCell addition, the CPC, or the CPA procedure, and the elapsed time of the timer T312 is greater than the third threshold (which may be included in the RRC message before executing the PSCell change, PSCell addition, CPC, or CPA procedure, and it may be decided or generated by the MN or source SN before executing the last PSCell change, the last PSCell addition, the last CPC, or the last CPA procedure) .
  • the third threshold which may be included in the RRC message before executing the PSCell change, PSCell addition, CPC, or CPA procedure, and it may be decided or generated by the MN or source SN before executing the last PSC
  • the third threshold associated with timer T312 may also be referred to as "the third trigger condition associated with timer T312" .
  • the UE may store (or log, generate, or report) the report (e.g., the SPR in an MR-DC scenario or an inter-RAT SPR) or the information associated with a successful PSCell change, a successful PSCell addition, a successful CPC, or a successful CPA in an MR-DC scenario.
  • the report e.g., the SPR in an MR-DC scenario or an inter-RAT SPR
  • the MN may be an RAN node using the E-UTRAN (4G) or LTE format or an RAT format of E-UTRA, or in other words, RAT format of the MN may be E-UTRAN or LTE access technology format
  • the specifications of 36 series are used for communication, e.g., TS36.300, TS36.331, TS36.413, TS36.423, for example, TS36.331 is used for information encoding or decoding between UE and the MN
  • the SNs e.g., a source SN or one or more target SNs
  • the SNs may be RAN nodes using the NR (5G) format or an RAT format of NR, or in other words, RAT format of the SN may be NR access technology format
  • the specifications of 38 series are used for communication, e.g., TS38.300, TS38.331, TS38.413,
  • the MN may be an RAN node using the NR (5G) format or an RAT format of NR, or in other words, RAT format of the MN may be NR access technology format
  • the specifications of 38 series are used for communication, e.g., TS38.300, TS38.331, TS38.413, TS38.423, for example, TS38.331 is used for information encoding or decoding between UE and the MN
  • the SNs e.g., a source SN or one or more target SNs
  • the SNs may be RAN nodes using the E-UTRAN (4G) or LTE format or an RAT format of E-UTRA
  • RAT format of the SN may be E-UTRAN or LTE access technology format
  • the specifications of 36 series are used for communication, e.g., TS36.300, TS36.331, TS36.413, TS36.423, for example, TS36.331 is used for information
  • the MN or the SN may be an RAN node which uses an RAT format of next generation access technology format, and all embodiments in the present disclosure are also applicable to similar technical problems.
  • the terminologies recited in the present disclosure may change, which should not affect the principle of the present disclosure.
  • the LTE nodes may not determine (or decide, generate) the trigger conditions for triggering the UE to store (or log, generate, or report) information associated with a successful PSCell change, a successful PSCell addition, a successful CPC, or a successful CPA, or a report (e.g., an SPR in an MR-DC scenario or an inter-RAT SPR) .
  • the MN may use the E-UTRAN (4G) or LTE format or an RAT format of E-UTRA, thus the MN may not determine (or decide, generate) the second trigger condition associated with timer T310 or the third trigger condition associated with timer T312.
  • the SN may use the NR (5G) format or an RAT format of NR, the source SN may determine (or decide, generate) at least one of the second trigger condition associated with timer T310 or the third trigger condition associated with timer T312; the target SN may determine (or decide, generate) the first trigger condition associated with timer T304.
  • the MN may use the NR (5G) format or an RAT format of NR, the MN may determine (or decide, generate) at least one of the second trigger condition associated with timer T310 or the third trigger condition associated with timer T312.
  • the SN may use the E-UTRAN (4G) or LTE format or an RAT format of E-UTRA, the source SN may not determine (or decide, generate) the second trigger condition associated with timer T310 or the third trigger condition associated with timer T312, the target SN may not determine (or decide, generate) the first trigger condition associated with timer T304.
  • the LTE node may determine (or decide, generate) the trigger conditions for triggering the UE to store (or log, generate, or report) information associated with a successful PSCell change, a successful PSCell addition, a successful CPC, or a successful CPA, or a report (e.g., an SPR in an MR-DC scenario or an inter-RAT SPR) .
  • the decides or generated trigger conditions may be different, and there are the following cases:
  • Case 1-1 in the EN-DC scenario and the NGEN-DC scenario, at least a candidate target SN may determine (or decide, generate) the first trigger condition associated with timer T304, and may transmit the first trigger condition to the MN.
  • the MN may transmit the first trigger condition (s) associated with timer T304 received from candidate target SN (s) to the UE.
  • the MN may transmit the first trigger condition (s) associated with timer T304 received from candidate target SN(s) to the source SN
  • the source SN may transmit the first trigger condition (s) associated with timer T304 to the UE through a signalling radio bearer (SRB) , e.g., SRB3.
  • SRB signalling radio bearer
  • Case 1-2 in the NE-DC scenario, in the case that the LTE nodes may not determine (or decide, generate) the trigger conditions, the target SN (an LTE node, e.g. ng-eNB) may not determine (or decide, generate) the trigger condition, thus the first trigger condition associated with timer T304 may not be supported.
  • the target SN an LTE node, e.g. ng-eNB
  • the LTE node may determine (or decide, generate) the trigger conditions
  • the first trigger condition (s) associated with timer T304 are generated and transmitted in a similar fashion as Case 1-1.
  • the PSCell change or the CPC procedure may be initiated by the MN or the SN, accordingly, two scenarios are as follows:
  • Case 2-1 an MN initiated PSCell change or an MN initiated CPC procedure.
  • either the MN or the source SN may determine (or decide, generate) at least one of the second trigger condition associated with timer T310 or the third trigger condition associated with timer T312, and there are the following scenarios.
  • the MN an LTE node, e.g. eNB or ng-eNB
  • the SNs NR nodes, e.g. en-gNB or gNB
  • the second trigger condition associated with timer T310 or the third trigger condition associated with timer T312 is not supported, and at least a candidate target SN may determine (or decide, generate) the first trigger condition associated with timer T304, and may transmit the trigger condition to the MN.
  • the MN may transmit the first trigger condition (s) associated with timer T304 from one or more candidate target SNs to the UE.
  • the MN may transmit the first trigger condition (s) associated with timer T304 from one or more candidate target SNs to the source SN, and the source SN may transmit the first trigger condition (s) associated with timer T304 to the UE through a signalling radio bearer, e.g., SRB3.
  • a signalling radio bearer e.g., SRB3.
  • the MN (a NR node, e.g. gNB) may determine (or decide, generate) the trigger conditions, and the SNs (LTE nodes e.g. ng-eNB) may not determine (or decide, generate) the trigger conditions. Accordingly, the MN may determine (or decide, generate) at least one of the second trigger condition associated with timer T310 or the third trigger condition associated with timer T312, while the first trigger condition associated with timer T304 is not supported.
  • the MN may transmit the at least one of the second trigger condition associated with timer T310 or the third trigger condition associated with timer T312 to the UE.
  • the MN may transmit the at least one of the second trigger condition associated with timer T310 or the third trigger condition associated with timer T312 to the source SN
  • the source SN may transmit the at least one of the second trigger condition associated with timer T310 or the third trigger condition associated with timer T312 to the UE through a signalling radio bearer, e.g., SRB3.
  • the SN determines (or decide, generate) at least one of the second trigger condition associated with timer T310 or the third trigger condition associated with timer T312, and in the case that the LTE nodes may not determine (or decide, generate) the trigger conditions, there may be the following scenarios.
  • the MN an LTE node, e.g. eNB or ng-eNB
  • the SNs NR nodes, e.g. en-gNB or gNB
  • the SNs may determine (or decide, generate) at least one of the trigger condition associated with timer T310, the trigger condition associated with timer T312, or the trigger condition associated with timer T304.
  • the source SN may determine (or decide, generate) at least one of the second trigger condition associated with timer T310 or the third trigger condition associated with timer T312; and at least a candidate target SN may determine (or decide, generate) the first trigger condition associated with timer T304, and may transmit the trigger condition to the MN or to the source SN.
  • the source SN may transmit the first trigger condition (s) associated with timer T304 (which may be received from at least a candidate target SN, or from the MN) , as well as the generated at least one of the second trigger condition associated with timer T310 or the third trigger condition associated with timer T312, to the UE through a signalling radio bearer, e.g., SRB3.
  • a signalling radio bearer e.g., SRB3.
  • the source SN may transmit the trigger conditions (including the first trigger condition (s) associated with timer T304 from at least a candidate target SN, and/or, the generated at least one of the second trigger condition associated with timer T310 or the third trigger condition associated with timer T312) within the container through the MN to the UE.
  • the trigger conditions including the first trigger condition (s) associated with timer T304 from at least a candidate target SN, and/or, the generated at least one of the second trigger condition associated with timer T310 or the third trigger condition associated with timer T312
  • the MN (a NR node, e.g. gNB) may determine (or decide, generate) the trigger conditions, and the SNs (LTE nodes e.g. ng-eNB) may not determine (or decide, generate) the trigger conditions.
  • the SN LTE nodes e.g. ng-eNB
  • Case 2-2 an SN initiated PSCell change or an SN initiated CPC procedure.
  • source SN determine (or decide, generate) at least one of the second trigger condition associated with timer T310 or the third trigger condition associated with timer T312, and in the case that the LTE nodes may not determine (or decide, generate) the trigger conditions, there may be the following scenarios.
  • the MN an LTE node, e.g. eNB or ng-eNB
  • the SNs NR nodes, e.g. en-gNB or gNB
  • the source SN may determine (or decide, generate) at least one of the second trigger condition associated with timer T310 or the third trigger condition associated with timer T312; and at least a candidate target SN may determine (or decide, generate) the first trigger condition associated with timer T304, and may transmit the trigger condition to the MN or to the source SN.
  • the source SN may transmit the first trigger condition (s) associated with timer T304 from at least a candidate target SN, and/or its generated at least one of the second trigger condition associated with timer T310 or the third trigger condition associated with timer T312, to the UE through a signalling radio bearer, e.g., SRB3.
  • a signalling radio bearer e.g., SRB3.
  • the source SN may transmit the trigger condition (s) (including the first trigger condition associated with timer T304 from at least a candidate target SN, and/or its generated at least one of the second trigger condition associated with timer T310 or the third trigger condition associated with timer T312) within the container through MN to the UE.
  • the trigger condition (s) including the first trigger condition associated with timer T304 from at least a candidate target SN, and/or its generated at least one of the second trigger condition associated with timer T310 or the third trigger condition associated with timer T312
  • At least a candidate target SN may transmit the trigger condition associated with timer T304 to the MN.
  • the MN may transmit the first trigger condition (s) associated with timer T304 from at least a candidate target SN to the UE.
  • the source SN may transmit the generated at least one of the second trigger condition associated with timer T310 or the third trigger condition associated with timer T312, to the UE through SRB3.
  • the MN (a NR node, e.g. gNB) may determine (or decide, generate) the trigger conditions, and the SNs (LTE nodes, e.g. ng-eNB) may not determine (or decide, generate) the trigger conditions.
  • the source SN since it is the source SN that may determine (or decide, generate) at least one of the second trigger condition associated with timer T310 or the third trigger condition associated with timer T312.
  • the source SN may not determine (or decide, generate) at least one of the second trigger condition associated with timer T310 or the third trigger condition associated with timer T312.
  • the target SN may not determine (or decide, generate) the first trigger condition associated with timer T304, either. Accordingly, in this scenario, a trigger condition associated with timer T304, a trigger condition associated with timer T310, and a trigger condition associated with timer T312, are not supported.
  • the LTE nodes may determine (or decide, generate) the trigger conditions, there may be the following cases:
  • Case Y-1 an MN initiated PSCell change or an MN initiated CPC procedure.
  • the MN or the source SN may determine (or decide, generate) the trigger conditions (at least one of the second trigger condition associated with timer T310 or the third trigger condition associated with timer T312) , and one or more candidate target SNs may determine (or decide, generate) the first trigger condition associated with timer T304.
  • the trigger condition (s) may include: one or more first trigger condition (s) associated with timer T304 (determined by at least a candidate target SN) , the second trigger condition associated with timer T310 (determined by the source SN or the MN) , or the third trigger condition associated with timer T312 (determined by the source SN or the MN) .
  • Case Y-2 an SN initiated PSCell change or an SN initiated CPC procedure.
  • the source SN may determine (or decide, generate) the at least one of the second trigger condition associated with timer T310 or the third trigger condition associated with timer T312, and at least a candidate target SN may determine (or decide, generate) the first trigger condition associated with timer T304.
  • the trigger condition (s) may include: one or more first trigger condition (s) associated with timer T304 (determined by at least a target SN) , the second trigger condition associated with timer T310 (determined by the source SN) , or the third trigger condition associated with timer T312 (determined by the source SN) .
  • the transmission of the trigger conditions to the UE is similar to the above scenarios, and details are omitted here.
  • some trigger conditions may be provided or configured or transmitted to the UE by an RAN node, however, the corresponding trigger conditions may not be generated or decided by the RAN node.
  • the source SN may generate or decide at least one of the second trigger condition associated with timer T310 or the third trigger condition associated with timer T312, but it is the MN rather than the source SN to determine the configuration (e.g.
  • the MN rather than the source SN to transmit the configuration (e.g. including at least one of the second trigger condition associated with timer T310 or the third trigger condition associated with timer T312) to the UE.
  • the configuration e.g. including at least one of the second trigger condition associated with timer T310 or the third trigger condition associated with timer T312
  • the UE may store (or log, generate, or report) the information associated with a successful PSCell change, a successful PSCell addition, a successful CPC, or a successful CPA, or the UE may store (or log, generate, or report) the report (e.g., the SPR in an MR-DC scenario or an inter-RAT SPR) , which may include at least one of the following:
  • the source PSCell may include cell information associated with the source PSCell or CGI information of the source PSCell (e.g., at least one of: a PLMN ID; a cell ID; a TAC; a PCI; or an ARFCN) , and one or more measurements results of the source PSCell, etc.
  • the source PSCell may be an LTE or NR cell;
  • a target PSCell which may include cell information associated with the target PSCell or CGI information of the target PSCell (e.g., at least one of: a PLMN ID; a cell ID; a TAC; a PCI; or an ARFCN) , and one or more measurements results of the target PSCell, etc.
  • the target PSCell may be an LTE or NR cell;
  • the neighbor cell may be an LTE or NR cell;
  • a cause value indicating which trigger condition for storing the information associated with the successful PSCell change, the successful PSCell addition, the successful CPA, or the successful CPC, or the report e.g., an SPR in an MR-DC scenario or an inter-RAT SPR
  • the report e.g., an SPR in an MR-DC scenario or an inter-RAT SPR
  • time information associated with the successful CPA or the successful CPC e.g., time elapsed between the CPA execution towards the target PSCell and the corresponding latest configuration for the CPA or CPC procedure is received;
  • RA-InformationCommon information associated with a random access procedure to the target PSCell, e.g., RA-InformationCommon, in the case that the first trigger condition associated with timer T304 is fulfilled.
  • the above information may be stored in a UE variable (e.g., VarInterRATSPR IE) .
  • the UE may store the above information in the report (e.g., the SPR in an MR-DC scenario or an inter-RAT SPR) .
  • the UE may transmit the above information or the report (e.g., the SPR in an MR-DC scenario or an inter-RAT SPR) to the MN or to the target SN.
  • the report e.g., the SPR in an MR-DC scenario or an inter-RAT SPR
  • the UE may transmit an indication, e.g., an indication included in RRC (connection) reconfiguration complete message, to the MN or to the target SN, to indicate the availability of the above information or the report (e.g., the SPR in an MR-DC scenario or an inter-RAT SPR) .
  • an indication e.g., an indication included in RRC (connection) reconfiguration complete message
  • the MN or the target SN may send a message, e.g. a UE information request message, which may include an indication requesting for the above information or the report (e.g., the SPR in an MR-DC scenario or an inter-RAT SPR) .
  • a message e.g. a UE information request message, which may include an indication requesting for the above information or the report (e.g., the SPR in an MR-DC scenario or an inter-RAT SPR) .
  • the UE may transmit a message, e.g. a UE information response message, to the MN or the target SN, which includes the above information or the report (e.g., the SPR in an MR-DC scenario or an inter-RAT SPR) .
  • a message e.g. a UE information response message
  • the MN or the target SN which includes the above information or the report (e.g., the SPR in an MR-DC scenario or an inter-RAT SPR) .
  • the UE may discard or release the stored information, or the report (e.g., the SPR in an MR-DC scenario or an inter-RAT SPR) or the UE variable VarInterRATSPR IE, 48 hours after the information is stored or the report is generated or stored.
  • the report e.g., the SPR in an MR-DC scenario or an inter-RAT SPR
  • the UE variable VarInterRATSPR IE 48 hours after the information is stored or the report is generated or stored.
  • Embodiment 2 generally relates to how the UE encodes the report (e.g., the SPR in an MR-DC scenario or an inter-RAT SPR) , or the information associated with the successful PSCell change, the successful PSCell addition, the successful CPA, or the successful CPC, and, which and how RAN node may perform MRO.
  • the report e.g., the SPR in an MR-DC scenario or an inter-RAT SPR
  • Case A a successful PSCell addition or a successful CPA, and the LTE nodes may not determine (or decide, generate) the trigger conditions:
  • the first trigger condition associated with timer T304 is fulfilled (which may be decided by the target SN) .
  • the report (e.g., the SPR in an MR-DC scenario or an inter-RAT SPR) or the information associated with a successful PSCell addition or a successful CPA, may be encoded with the format of the MN, i.e., the E-UTRAN format (or the LTE format, or an RAT format of E-UTRA) .
  • the UE may store or generate or encode the report (e.g., the SPR in an MR-DC scenario or an inter-RAT SPR) or the information with the RAT format of the MN (i.e., the E-UTRAN format, or the LTE format, or a format of E-UTRA) .
  • the report or the information associated with the successful PSCell addition or the successful CPA may include information associated with the target PSCell (which is a NR cell) , a cause to indicate the first trigger condition associated with timer T304 is fulfilled, time information associated with the successful CPA, etc.
  • the UE may transmit the report (e.g., the SPR in an MR-DC scenario or an inter-RAT SPR) or the information associated with the successful PSCell addition or the successful CPA to the MN, and the MN may perform the one of the following options:
  • the MN may transfer the report (e.g., the SPR in an MR-DC scenario or an inter-RAT SPR) or the information in the format of the MN (i.e., the E-UTRAN format or the LTE format, or an RAT format of E-UTRA) to the target SN (i.e., en-gNB or gNB) , and the target SN may have the capability to decode the report (e.g., the SPR in an MR-DC scenario or an inter-RAT SPR) or the information in E-UTRAN or LTE format for MRO, for example, the target SN may modify or update PSCell change or PSCell addition or CPA or CPC related configurations, e.g.
  • the report e.g., the SPR in an MR-DC scenario or an inter-RAT SPR
  • the information in the format of the MN i.e., the E-UTRAN format or the LTE format, or an RAT format of E-UTRA
  • the target SN
  • s including optimizing trigger condition (s) of CPA or CPC, a trigger threshold of PCell change or PSCell addition, candidate PSCell (s) for CPA or CPC, a target PSCell for PCell change or PSCell addition, and/or random access channel (RACH) resource (s) for accessing to (candidate) target PSCell (s) .
  • the MN may decode the received report or information, and re-encode/re-organize the report (e.g., the SPR in an MR-DC scenario or an inter-RAT SPR) or the information with the RAT format of the target SN (i.e. with NR format or an RAT format of NR) .
  • the MN may decode the report (e.g., the SPR in an MR-DC scenario or an inter-RAT SPR) or the information encoded in the RAT format of MN, and obtain the explicit information .
  • the MN may re-encode (or re-organize) the explicit information with the RAT format of the target SN, and may forward the re-encoded (or re-organized) report or information to the target SN, e.g. via a message or an inter-node RRC message, the inter-node RRC message may be a new introduced message, or a reused existing inter-node RRC message (e.g., CG-ConfigInfo) with extension.
  • the target SN may perform MRO, for example, the target SN may modify or update PSCell change or PSCell addition or CPA or CPC related configurations, e.g.
  • trigger condition (s) of CPA or CPC including optimizing trigger condition (s) of CPA or CPC, a trigger threshold of PCell change or PSCell addition, candidate PSCell (s) for CPA or CPC, a target PSCell for PCell change or PSCell addition, and/or RACH resource (s) for accessing to (candidate) target PSCell (s) .
  • the MN may decode the received report (e.g., the SPR in an MR-DC scenario or an inter-RAT SPR) or the information encoded with the RAT format of MN, and obtain the explicit information.
  • the MN may transfer the decoded explicit information (e.g. information associated with the target PSCell, a cause to indicate the first trigger condition associated with timer T304 is fulfilled, time information associated with the successful CPA, etc. ) to the target SN, e.g. with messages such as an X2 message or an Xn message. That is, the MN may transmit the explicit information to the target SN.
  • the target SN may perform MRO.
  • the report (e.g., the SPR in an MR-DC scenario or an inter-RAT SPR) or the information associated with the successful PSCell addition or the successful CPA (which may include information associated with the target PSCell (which is a NR cell) , a cause to indicate the first trigger condition associated with timer T304 is fulfilled, time information associated with the successful CPA, etc. ) may be encoded with an RAT format of NR or, may be encoded with an RAT format of the target SN (i.e., en-gNB or gNB) .
  • the UE may store or generate or encode the report (e.g., the SPR in an MR-DC scenario or an inter-RAT SPR) or the information with the RAT format of NR (i.e., the NR format, or a format of NR) , or, the UE may store or generate or encode the report (e.g., the SPR in an MR-DC scenario or an inter-RAT SPR) or the information with an RAT format of the target SN (wherein a trigger condition associated with timer T304 is generated by the SN, and the trigger condition is fulfilled) .
  • the MN an LTE node, i.e., eNB or ng-eNB
  • the following option may be used:
  • the UE may transmit cell information associated with the target PSCell or CGI information of the target PSCell (e.g., at least one of: PLMN ID, cell ID, TAC, PCI, or ARFCN) .
  • cell information associated with the target PSCell e.g., at least one of: PLMN ID, cell ID, TAC, PCI, or ARFCN
  • the MN may transparently transfer the report (e.g., the SPR in an MR-DC scenario or an inter-RAT SPR) or the information encoded with the NR format or an RAT format of NR to target SN (i.e., en-gNB or gNB) , based on the cell information associated with the target PSCell or the CGI information of the target PSCell.
  • the target SN may perform MRO.
  • the report (e.g., the SPR in an MR-DC scenario or an inter-RAT SPR) or the information may not be supported, either.
  • Case B a successful PSCell change or a successful CPC initiated by the MN or by the SN, and the LTE nodes may not determine (or decide, generate) the trigger conditions.
  • one or more of the first trigger condition associated with timer T304, the second trigger condition associated with timer T310, or the third trigger condition associated with timer T312 may be configured and fulfilled, and depending on the fulfilled trigger conditions, the MR-DC scenarios, and the encoding format, several cases are presented as follows:
  • the PSCell change or the CPC is initiated by the MN or by the SN
  • the first trigger condition associated with timer T304 is fulfilled (which may be decided by the target SN)
  • the second trigger condition associated with timer T310 and the third trigger condition associated with timer T312 are not fulfilled (or not supported, or not configured or may be configured by the MN or by the source SN but are not fulfilled) .
  • Case B1-1 the report (e.g., the SPR in an MR-DC scenario or an inter-RAT SPR) or the information associated with the successful PSCell change or the successful CPC may be encoded with the format of the MN, i.e., the E-UTRAN format (or the LTE format, or an RAT format of E-UTRA) .
  • the UE may store or generate or encode the report (e.g., the SPR in an MR-DC scenario or an inter-RAT SPR) or the information with the RAT format of the MN (i.e., the E-UTRAN format, or the LTE format, or a format of E-UTRA) .
  • the report (e.g., the SPR in an MR-DC scenario or an inter-RAT SPR) or the information associated with the successful PSCell change or the successful CPC may include: information associated with the source PSCell (which is an LTE cell) , information associated with the target PSCell (which is a NR cell) , a cause to indicate the first trigger condition associated with timer T304 is fulfilled, time information associated with the successful CPC, etc.
  • the UE may transmit the report (e.g., the SPR in an MR-DC scenario or an inter-RAT SPR) or the information associated with the successful PSCell change or the successful CPC to the MN, and the MN may perform the following options:
  • the MN may transfer the report (e.g., the SPR in an MR-DC scenario or an inter-RAT SPR) or the information in the format of the MN (i.e., the E-UTRAN format or the LTE format, or an RAT format of E-UTRA) to the target SN (i.e., en-gNB or gNB) , and the target SN may have the capability to decode the report (e.g., the SPR in an MR-DC scenario or an inter-RAT SPR) or the information in E-UTRAN or LTE format for MRO, for example, the target SN may modify or update PSCell change or PSCell addition or CPA or CPC related configurations, e.g.
  • the report e.g., the SPR in an MR-DC scenario or an inter-RAT SPR
  • the information in the format of the MN i.e., the E-UTRAN format or the LTE format, or an RAT format of E-UTRA
  • the target SN
  • trigger condition (s) of CPA or CPC including optimizing trigger condition (s) of CPA or CPC, a trigger threshold of PCell change or PSCell addition, candidate PSCell (s) for CPA or CPC, a target PSCell for PCell change or PSCell addition, and/or RACH resource (s) for accessing to (candidate) target PSCell (s) .
  • the MN may decode the received report or information, and re-encode/re-organize the report (e.g., the SPR in an MR-DC scenario or an inter-RAT SPR) or the information with the RAT format of the target SN (i.e. with NR format or an RAT format of NR) .
  • the MN may decode the report (e.g., the SPR in an MR-DC scenario or an inter-RAT SPR) or the information encoded in the RAT format of MN, and obtain the explicit information.
  • the MN may re-encode (or re-organize) the explicit information with the RAT format of the target SN, and may forward the re-encoded (or re-organized) report or information to the target SN, e.g. via a message or an inter-node RRC message, the inter-node RRC message may be a new introduced message, or a reused existing inter-node message (e.g., CG-ConfigInfo) with extension.
  • the target SN may perform MRO, for example, the target SN may modify or update PSCell change or PSCell addition or CPA or CPC related configurations, e.g.
  • trigger condition (s) of CPA or CPC including optimizing trigger condition (s) of CPA or CPC, a trigger threshold of PCell change or PSCell addition, candidate PSCell (s) for CPA or CPC, a target PSCell for PCell change or PSCell addition, and/or RACH resource (s) for accessing to (candidate) target PSCell (s) .
  • the MN may decode the received report (e.g., the SPR in an MR-DC scenario or an inter-RAT SPR) or the information encoded with the RAT format of MN, and obtain the explicit information.
  • the MN may transfer the decoded explicit information (e.g. information associated with the source PSCell, information associated with the target PSCell, a cause to indicate the first trigger condition associated with timer T304 is fulfilled, time information associated with the successful CPC, etc. ) to the target SN, e.g. with messages such as an X2 message or an Xn message. That is, the MN may transmit the explicit information to the target SN.
  • the target SN may perform MRO.
  • Case B1-2 the report (e.g., the SPR in an MR-DC scenario or an inter-RAT SPR) or the information associated with the successful PSCell change or the successful CPC may be encoded with an RAT format of NR, or, may be encoded with an RAT format of the target SN (i.e., en-gNB or gNB) .
  • the report e.g., the SPR in an MR-DC scenario or an inter-RAT SPR
  • the information associated with the successful PSCell change or the successful CPC may be encoded with an RAT format of NR, or, may be encoded with an RAT format of the target SN (i.e., en-gNB or gNB) .
  • the UE may store or generate or encode the report (e.g., the SPR in an MR-DC scenario or an inter-RAT SPR) or the information with the RAT format of NR (i.e., the NR format, or a format of NR) , or, the UE may store or generate or encode the report (e.g., the SPR in an MR-DC scenario or an inter-RAT SPR) or the information with an RAT format of the target SN (wherein a trigger condition associated with timer T304 is generated by the SN, and the trigger condition is fulfilled) .
  • the MN an LTE node, i.e., eNB or ng-eNB
  • the following option may be applied:
  • the UE may transmit cell information associated with the target PSCell or the CGI information of the target PSCell (e.g., at least one of: PLMN ID, cell ID, TAC, PCI, or ARFCN) .
  • cell information associated with the target PSCell e.g., at least one of: PLMN ID, cell ID, TAC, PCI, or ARFCN
  • the MN may transparently transfer the report (e.g., the SPR in an MR-DC scenario or an inter-RAT SPR) or the information encoded with the NR format or an RAT format of NR to target SN (i.e., en-gNB or gNB) , based on the cell information associated with the target PSCell or the CGI information of the target PSCell.
  • the target SN may perform MRO.
  • the first trigger condition associated with timer T304 may not be supported, configured, or configured but not fulfilled, and at least one of the second trigger condition associated with timer T310 or the third trigger condition associated with timer T312 may be configured and fulfilled (which is determined (or decided, generated) by the MN) .
  • the report (e.g., the SPR in an MR-DC scenario or an inter-RAT SPR) or the information associated with the successful PSCell change or the successful CPC may be encoded with the RAT format of the MN, i.e., NR format or a format of NR, or the report or the information may be encoded with the RAT format of the MN (wherein a trigger condition associated with timer T310 and is fulfilled, and/or a trigger condition associated with timer T312 is generated by the MN and is fulfilled) .
  • the UE may store or generate or encode the report (e.g., the SPR in an MR-DC scenario or an inter-RAT SPR) or the information with the RAT format of the MN (i.e., NR format or a format of NR) , or, the UE may store or generate or encode the report or the information with the RAT format of the MN (wherein a trigger condition associated with timer T310 and is fulfilled, and/or a trigger condition associated with timer T312 is generated by the MN and is fulfilled) .
  • the SPR in the NE-DC scenario or an inter-RAT SPR may include e.g. information associated with the source PSCell (i.e.
  • the MN may decode the report (e.g., the SPR in an MR-DC scenario or an inter-RAT SPR) or the information associated with the successful PSCell change or the successful CPC, and may perform MRO, for example, the MN may modify or update PSCell change or PSCell addition or CPA or CPC related configurations, e.g.
  • trigger condition (s) of CPA or CPC including optimizing trigger condition (s) of CPA or CPC, a trigger threshold of PCell change or PSCell addition, candidate PSCell (s) for CPA or CPC, a target PSCell for PCell change or PSCell addition, and/or RACH resource (s) for accessing to (candidate) target PSCell (s) .
  • the report e.g., the SPR in an MR-DC scenario or an inter-RAT SPR
  • the information associated with the successful PSCell change or the successful CPC is not supported.
  • the PSCell change or the CPC is initiated by the MN or by the SN
  • the first trigger condition associated with timer T304 is not configured or not fulfilled (which may be determined (or decided, generated) by the target SN)
  • at least one of the second trigger condition associated with timer T310 or the third trigger condition associated with timer T312 is fulfilled (which may be determined (or decided, generated) by the source SN) .
  • the report (e.g., the SPR in an MR-DC scenario or an inter-RAT SPR) or the information associated with the successful PSCell change or the successful CPC, is encoded with the format of the MN, i.e., the E-UTRAN format (or the LTE format, or an RAT format of E-UTRA) .
  • the UE may store or generate or encode the report (e.g., the SPR in an MR-DC scenario or an inter-RAT SPR) or the information with the RAT format of the MN (i.e., the E-UTRAN format, or the LTE format, or a format of E-UTRA) .
  • the report (e.g., the SPR in an MR-DC scenario or an inter-RAT SPR) or the information associated with the successful PSCell change or the successful CPC may include: information associated with the source PSCell (which is an LTE cell) , information associated with the target PSCell (which is a NR cell) , a cause to indicate the second trigger condition associated with timer T310 is fulfilled and/or a cause to indicate the third trigger condition associated with timer T312 is fulfilled, time information associated with the successful CPC, etc.
  • the UE may transmit the report (e.g., the SPR in an MR-DC scenario or an inter-RAT SPR) or the information associated with the successful PSCell change or the successful CPC to the MN.
  • the MN may take the following options:
  • the MN may transfer the report (e.g., the SPR in an MR-DC scenario or an inter-RAT SPR) or the information in the format of the MN (i.e., the E-UTRAN format or the LTE format, or an RAT format of E-UTRA) to the source SN (i.e., en-gNB or gNB) , and the source SN may have the capability to decode the report (e.g., the SPR in an MR-DC scenario or an inter-RAT SPR) or the information in E-UTRAN or LTE format for MRO, for example, the source SN may modify or update PSCell change or PSCell addition or CPA or CPC related configurations, e.g.
  • the report e.g., the SPR in an MR-DC scenario or an inter-RAT SPR
  • the source SN may have the capability to decode the report (e.g., the SPR in an MR-DC scenario or an inter-RAT SPR) or the information in E-
  • trigger condition (s) of CPA or CPC including optimizing trigger condition (s) of CPA or CPC, a trigger threshold of PCell change or PSCell addition, candidate PSCell (s) for CPA or CPC, a target PSCell for PCell change or PSCell addition, and/or RACH resource (s) for accessing to (candidate) target PSCell (s) .
  • the MN may decode the received report or information, and re-encode/re-organize the report (e.g., the SPR in an MR-DC scenario or an inter-RAT SPR) or the information with the RAT format of the source SN (i.e. with NR format or an RAT format of NR) .
  • the MN may decode the report (e.g., the SPR in an MR-DC scenario or an inter-RAT SPR) or the information encoded in the RAT format of MN, and obtain the explicit information.
  • the MN may re-encode (or re-organize) the explicit information (i.e., the decoded report) with the RAT format of the source SN, and may forward the re-encoded (or re-organized) report or information to the source SN, e.g. via a message or an inter-node RRC message, the inter-node RRC message may be a new introduced message, or a reused existing inter-node message (e.g., CG-ConfigInfo) with extension.
  • the inter-node RRC message may be a new introduced message, or a reused existing inter-node message (e.g., CG-ConfigInfo) with extension.
  • the source SN may perform MRO, for example, source SN may modify or update PSCell change or PSCell addition or CPA or CPC related configurations, e.g. including optimizing trigger condition (s) of CPA or CPC, a trigger threshold of PCell change or PSCell addition, candidate PSCell (s) for CPA or CPC, a target PSCell for PCell change or PSCell addition, and/or RACH resource (s) for accessing to (candidate) target PSCell (s) .
  • source SN may modify or update PSCell change or PSCell addition or CPA or CPC related configurations, e.g. including optimizing trigger condition (s) of CPA or CPC, a trigger threshold of PCell change or PSCell addition, candidate PSCell (s) for CPA or CPC, a target PSCell for PCell change or PSCell addition, and/or RACH resource (s) for accessing to (candidate) target PSCell (s) .
  • the MN may decode the received report (e.g., the SPR in an MR-DC scenario or an inter-RAT SPR) or the information encoded with the RAT format of MN, and obtain the explicit information.
  • the MN may transfer the decoded explicit information (e.g. information associated with the source PSCell, information associated with the target PSCell, a cause to indicate the second trigger condition associated with timer T310 is fulfilled and/or a cause to indicate the third trigger condition associated with timer T312 is fulfilled, time information associated with the successful CPC, etc. ) to the source SN, e.g. with messages such as an X2 message or an Xn message. That is, the MN may transmit the explicit information to the source SN.
  • the source SN may perform MRO.
  • the report e.g., the SPR in an MR-DC scenario or an inter-RAT SPR
  • the information associated with the successful PSCell change or the successful CPC is encoded with an RAT format of NR, or, may be encoded with an RAT format of the source SN (i.e., en-gNB or gNB) which decides at least one of the second trigger condition associated with timer T310 or the third trigger condition associated with timer T312.
  • the UE may store or generate or encode the report (e.g., the SPR in an MR-DC scenario or an inter-RAT SPR) or the information with the RAT format of NR (i.e., the NR format, or a format of NR) , or, the UE may store or generate or encode the report (e.g., the SPR in an MR-DC scenario or an inter-RAT SPR) or the information with an RAT format of the source SN (wherein a trigger condition associated with timer T310 is generated by the source SN and the trigger condition is fulfilled, and/or, a trigger condition associated with timer T312 is generated by the source SN and the trigger condition is fulfilled) .
  • the MN an LTE node, i.e., eNB or ng-eNB
  • the following option may be applied:
  • the UE may also transmit cell information associated with the source PSCell or the CGI information of the source PSCell (e.g., at least one of: PLMN ID, cell ID, TAC, PCI, or ARFCN) outside of the report or the information.
  • cell information associated with the source PSCell or the CGI information of the source PSCell e.g., at least one of: PLMN ID, cell ID, TAC, PCI, or ARFCN
  • the MN may transparently transfer the report (e.g., the SPR in an MR-DC scenario or an inter-RAT SPR) or the information encoded with the NR format or an RAT format of NR to source SN (i.e., en-gNB or gNB) , based on the cell information associated with the source PSCell or the CGI information of the source PSCell.
  • the source SN may perform MRO.
  • the first trigger condition associated with timer T304 is fulfilled (which may be decided by the target SN)
  • at least one of the second trigger condition associated with timer T310 or the third trigger condition associated with timer T312 is fulfilled (which may be decided by the source SN) .
  • the report e.g., the SPR in an MR-DC scenario or an inter-RAT SPR
  • the information associated with the successful PSCell change or the successful CPC is encoded with the format of the MN, i.e., the E-UTRAN format (or the LTE format, or an RAT format of E-UTRA) .
  • the UE may store or generate or encode the report (e.g., the SPR in an MR-DC scenario or an inter-RAT SPR) or the information with the RAT format of the MN (i.e., the E-UTRAN format, or the LTE format, or a format of E-UTRA) .
  • the report (e.g., the SPR in an MR-DC scenario or an inter-RAT SPR) or the information associated with the successful PSCell change or the successful CPC may include: information associated with the source PSCell (which is an LTE cell) , information associated with the target PSCell (which is a NR cell) , a cause to indicate the second trigger condition associated with timer T310 is fulfilled and/or a cause to indicate the third trigger condition associated with timer T312 is fulfilled, a cause to indicate the first trigger condition associated with timer T304 is fulfilled, time information associated with the successful CPC, etc.
  • the UE may transmit the report (e.g., the SPR in an MR-DC scenario or an inter-RAT SPR) or the information associated with the successful PSCell change or the successful CPC to the MN.
  • the MN may take the following options:
  • the MN may transfer the report (e.g., the SPR in an MR-DC scenario or an inter-RAT SPR) or the information in the format of the MN (i.e., the E-UTRAN format or the LTE format, or an RAT format of E-UTRA) to the source SN (i.e., en-gNB or gNB) and the target SN (i.e., en-gNB or gNB) separately, and the source SN and the target SN may have the capability to decode the report (e.g., the SPR in an MR-DC scenario or an inter-RAT SPR) or the information in E-UTRAN or LTE format for MRO separately, for example, source SN or target SN may modify or update PSCell change or PSCell addition or CPA or CPC related configurations, e.g.
  • the report e.g., the SPR in an MR-DC scenario or an inter-RAT SPR
  • the information in the format of the MN i.e
  • trigger condition (s) of CPA or CPC including optimizing trigger condition (s) of CPA or CPC, a trigger threshold of PCell change or PSCell addition, candidate PSCell (s) for CPA or CPC, target PSCell for PCell change or PSCell addition, and/or RACH resource (s) for accessing to (candidate) target PSCell (s) .
  • the MN may decode the received report or information, and re-encode/re-organize the report (e.g., the SPR in an MR-DC scenario or an inter-RAT SPR) or the information with the RAT format of the SN (including the source SN or the target SN, i.e. re-encode/re-organize the report or the information with NR format or an RAT format of NR) .
  • the MN may decode the report or the information encoded in the RAT format of MN, and obtain the explicit information.
  • the source SN and the target SN may use the same RAT format, and the MN may re-encode (or re-organize) the explicit information (i.e., the decoded report) with the RAT format of the SN (either the RAT format of the source SN or the RAT format of the target SN, which are the same RAT format) , and may forward the re-encoded (or re-organized) report or information to the source SN and the target SN separately, e.g.
  • the inter-node RRC message may be a new introduced message, or a reused existing inter-node message (e.g., CG-ConfigInfo) with extension.
  • the source SN and the target SN may perform MRO.
  • the source SN and the target SN may use different RAT formats (for example, any two of an E- UTRAN format, an NG format, or a next generation format)
  • the MN may re-encode the decoded report with the RAT format of the source SN, and transmit the report encoded with the RAT format of the source SN to the source SN.
  • the MN may re-encode the decoded report with the RAT format of the target SN, and transmit the report encoded with the RAT format of the target SN to the target SN.
  • the MN may decode the received report (e.g., the SPR in an MR-DC scenario or an inter-RAT SPR) or the information encoded with the RAT format of MN, and obtain the explicit information (for example, information associated with the source PSCell, information associated with the target PSCell, a cause to indicate the second trigger condition associated with timer T310 is fulfilled and/or a cause to indicate the third trigger condition associated with timer T312 is fulfilled, a cause to indicate the first trigger condition associated with timer T304 is fulfilled, time information associated with the successful CPC, etc. ) .
  • the MN may transfer the decoded explicit information to the source SN and the target SN separately, e.g. with messages such as an X2 message or an Xn message. That is, the MN may transmit the explicit information to the source SN and the target SN. After receiving the explicit information from the MN, the source SN and the target SN may perform MRO.
  • the report e.g., the SPR in an MR-DC scenario or an inter-RAT SPR
  • the information associated with the successful PSCell change or the successful CPC is encoded with an RAT format of NR, or, may be encoded with an RAT format of the source SN (i.e., en-gNB or gNB) , or may be encoded with an RAT format of the target SN (i.e., en-gNB or gNB) .
  • the UE may store or generate or encode the report (e.g., the SPR in an MR-DC scenario or an inter-RAT SPR) or the information with the RAT format of NR (i.e., the NR format, or a format of NR) , or, the UE may store or generate or encode the report (e.g., the SPR in an MR-DC scenario or an inter-RAT SPR) or the information with an RAT format of the source SN (wherein a trigger condition associated with timer T310 is generated by the source SN and the trigger condition is fulfilled, and/or, a trigger condition associated with timer T312 is generated by the source SN and the trigger condition is fulfilled) , or the UE may store or generate or encode the report (e.g., the SPR in an MR-DC scenario or an inter-RAT SPR) or the information with an RAT format of the target SN (wherein a trigger condition associated with timer T304 is generated by the target SN and the trigger condition is fulfilled)
  • the UE may transmit cell information associated with the source PSCell or the CGI information of the source PSCell (e.g., at least one of: PLMN ID, cell ID, TAC, PCI, or ARFCN) , and cell information associated with the target PSCell or the CGI information of the target PSCell outside of the report (e.g., the SPR in an MR-DC scenario or an inter-RAT SPR) or the information.
  • cell information associated with the source PSCell or the CGI information of the source PSCell e.g., at least one of: PLMN ID, cell ID, TAC, PCI, or ARFCN
  • cell information associated with the target PSCell or the CGI information of the target PSCell outside of the report e.g., the SPR in an MR-DC scenario or an inter-RAT SPR
  • the MN may transparently transfer the report (e.g., the SPR in an MR-DC scenario or an inter-RAT SPR) or the information encoded with the NR format or an RAT format of NR to source SN (i.e., en-gNB or gNB) based on the cell information associated with the source PSCell or the CGI information of the source PSCell, and, the MN may transparently transfer the report (e.g., the SPR in an MR-DC scenario or an inter-RAT SPR) or the information encoded with the NR format or an RAT format of NR to target SN (i.e., en-gNB or gNB) based on the cell information associated with the target PSCell or the CGI information of the target PSCell.
  • the source SN and target SN may perform MRO separately.
  • Case C a successful PSCell change, a successful PSCell addition, a successful CPC, or a successful CPA, and the LTE nodes may determine (or decide, generate) the trigger conditions.
  • first trigger condition associated with timer T304 may be determined (or decided, generated) by the target SN
  • second trigger condition associated with timer T310 may be determined (or decided, generated) by the MN, or by the source SN, or by both the MN and the source SN (the MN and the source SN may determine one of the second trigger condition associated with timer T310 and the third trigger condition associated with timer T312 respectively) .
  • the successful PSCell addition, the successful CPC, or the successful CPA is encoded with the format of the MN, i.e., the E-UTRAN format, or the LTE format, or an RAT format of E-UTRA.
  • the UE may store or generate or encode the report (e.g., the SPR in an MR-DC scenario or an inter-RAT SPR) or the information with the RAT format of the MN (i.e., the E-UTRAN format, or the LTE format, or a format of E-UTRA) .
  • the UE may transmit the report (e.g., the SPR in an MR-DC scenario or an inter-RAT SPR) or the information associated with the successful PSCell change, the successful PSCell addition, the successful CPA, or the successful CPC, to the MN.
  • the MN may take the following options:
  • the MN may transfer the report or the information in the format of the MN (i.e., the E-UTRAN format or the LTE format, or an RAT format of E-UTRA) to the target SN (in the case that the first trigger condition associated with timer T304 generated by the target SN is fulfilled) , and the target SN may have the capability to decode the report or the information in E-UTRAN or LTE format for MRO.
  • the target SN in the case that the first trigger condition associated with timer T304 generated by the target SN is fulfilled
  • the MN may perform MRO (in the case that a trigger condition generated by the MN is fulfilled) .
  • the MN may transfer the report or the information in the format of the MN (i.e., the E-UTRAN format or the LTE format, or an RAT format of E-UTRA) to the source SN (in the case that a trigger condition generated by the source SN is fulfilled) , and/or the target SN (in the case that the first trigger condition associated with timer T304 generated by the target SN is fulfilled) , and the source SN and the target SN may have the capability to decode the report or the information in E-UTRAN or LTE format for MRO.
  • the source SN in the case that a trigger condition generated by the source SN is fulfilled
  • the target SN in the case that the first trigger condition associated with timer T304 generated by the target SN is fulfilled
  • the MN may have the capability to decode the received report or information, and the MN may perform MRO (in the case that a trigger condition generated by the MN is fulfilled) . Also, the MN may re-encode the report (e.g., the SPR in an MR-DC scenario or an inter-RAT SPR) or the information with the RAT format of the SN (including the source SN and/or the target SN, i.e. re-encode/re-organize the report or the information with NR format or an RAT format of NR) . The MN may decode the report or the information which is encoded in the RAT format of MN, and obtain the explicit information.
  • MRO in the case that a trigger condition generated by the MN is fulfilled
  • the source SN and the target SN may use the same RAT format, and the MN may re-encode the explicit information with the RAT format of the SN (either the RAT format of the source SN or the RAT format of the target SN, which are the same RAT format) , and may forward the re-encoded information or report to the source SN (in the case that a trigger condition generated by the source SN is fulfilled) and/or the target SN (in the case that the first trigger condition associated with timer T304 generated by the target SN is fulfilled) separately, e.g.
  • the inter-node RRC message may be a new introduced message, or a reused existing inter-node message (e.g., CG-ConfigInfo) with extension.
  • the source SN and the target SN may use different RAT formats (for example, any two of an E-UTRAN format, an NG format, or a next generation format, etc. )
  • the MN may re-encode the decoded report with the RAT format of the source SN, and transmit the report encoded with the RAT format of the source SN to the source SN (in the case that a trigger condition generated by the source SN is fulfilled) .
  • the MN may re-encode the decoded report with the RAT format of the target SN, and transmit the report encoded with the RAT format of the target SN to the target SN (in the case that the first trigger condition associated with timer T304 generated by the target SN is fulfilled) .
  • the source SN in the case that a trigger condition generated by the source SN is fulfilled
  • the target SN in the case that the first trigger condition associated with timer T304 generated by the target SN is fulfilled
  • MRO MRO
  • the MN may decode the received report (e.g., the SPR in an MR-DC scenario or an inter-RAT SPR) or the information encoded in the RAT format of MN, and obtain the explicit information (for example, information associated with the source PSCell, information associated with the target PSCell, a cause to indicate the second trigger condition associated with timer T310 is fulfilled and/or a cause to indicate the third trigger condition associated with timer T312 is fulfilled and/or a cause to indicate the first trigger condition associated with timer T304 is fulfilled, time information associated with the successful CPC and etc. ) .
  • the MN may perform MRO (in the case that a trigger condition generated by the MN is fulfilled) .
  • the MN may transfer the decoded explicit information to the source SN (in the case that a trigger condition generated by the source SN is fulfilled) and the target SN (in the case that the first trigger condition associated with timer T304 generated by the target SN is fulfilled) , e.g. with messages such as an X2 message or an Xn message. That is, the MN may transmit the explicit information to the source SN and the target SN.
  • the source SN in the case that a trigger condition generated by the source SN is fulfilled
  • the target SN in the case that the first trigger condition associated with timer T304 generated by the target SN is fulfilled
  • MRO MRO
  • the report e.g., the SPR in an MR-DC scenario or an inter-RAT SPR
  • the successful PSCell addition, the successful CPC, or the successful CPA is encoded with the format the NR
  • the MN an LTE node, i.e., eNB or ng-eNB
  • the MN an LTE node, i.e., eNB or ng-eNB
  • the UE may transmit cell information associated with the source PSCell or the CGI information of the source PSCell (e.g., at least include PLMN ID, cell ID, TAC, PCI, or ARFCN) (in the case that a trigger condition generated by the source SN is fulfilled) , and cell information associated with the target PSCell or the CGI information of the target PSCell outside of the report or the information (in the case that the first trigger condition associated with timer T304 generated by the target SN is fulfilled) .
  • cell information associated with the source PSCell or the CGI information of the source PSCell e.g., at least include PLMN ID, cell ID, TAC, PCI, or ARFCN
  • the MN may transparently transfer the report or the information encoded in the NR format to source SN based on cell information associated with the source PSCell or the CGI information of the source PSCell (in the case that a trigger condition generated by the source SN is fulfilled) , and/or, the MN may transparently transfer the report (e.g., the SPR) or the information encoded in the NR format to target SN based on cell information associated with the target PSCell or the CGI information of the target PSCell (in the case that the first trigger condition associated with timer T304 generated by the target SN is fulfilled) .
  • the report e.g., the SPR
  • the information encoded in the NR format to target SN based on cell information associated with the target PSCell or the CGI information of the target PSCell (in the case that the first trigger condition associated with timer T304 generated by the target SN is fulfilled) .
  • the source SN (in the case that a trigger condition generated by the source SN is fulfilled) and/or the target SN (in the case that the first trigger condition associated with timer T304 generated by the target SN is fulfilled) may perform MRO.
  • the UE may store or generate or decode only one report (e.g., the SPR in an MR-DC scenario or an inter-RAT SPR) , with the RAT format of the MN, or with the RAT format of NR, or with the RAT format of an RAN node wherein at least one trigger condition within the multiple trigger conditions is decided or generated by the RAN node and the at least one trigger condition is fulfilled.
  • the SPR in an MR-DC scenario or an inter-RAT SPR e.g., the SPR in an MR-DC scenario or an inter-RAT SPR
  • the UE may store or generate or decode more than one reports (e.g., more than one SPRs in an MR-DC scenario or more than one inter-RAT SPRs) correspondingly, wherein each report is encoded with the RAT format of the RAN node wherein at least one trigger condition within the multiple trigger conditions is decided or generated by the RAN node and the at least one trigger condition is fulfilled.
  • more than one reports e.g., more than one SPRs in an MR-DC scenario or more than one inter-RAT SPRs
  • the UE may store or generate or decode two reports (e.g., two inter-RAT SPRs) correspondingly, wherein one report is encoded with the RAT format of the MN, wherein the second trigger condition associated with timer T310 is generated by the MN and is fulfilled (after the MN receives this report, the MN may perform MRO) , and another report is encoded with the RAT format of the target SN, wherein the first trigger condition associated with timer T304 is generated by the target SN and is fulfilled, outside of the another report, the UE may transmit cell information associated with the target PSCell or the CGI information of the target PSCell (e.g., at least one of: PLMN ID, cell ID, TAC, PCI, or ARFCN) , then, the MN may forward the another report to
  • Fig. 2 illustrates a method performed by a UE for SON enhancements according to some embodiments of the present disclosure.
  • the UE may receive a configuration regarding first information associated with a successful PSCell change, a successful PSCell addition, a successful CPA, or a successful CPC in an MR-DC scenario, wherein an MN and an SN in the MR-DC scenario utilize different RATs, and the configuration is related to one or more trigger conditions for storing the first information.
  • the UE may generate a report including the first information in the MR-DC scenario when at least one trigger condition within the one or more trigger conditions is fulfilled.
  • the report may be an SPR.
  • the processor is further configured to: transmit an indication for indicating a UE capability, which indicates that the UE is able to store the first information or generate the report in the MR-DC scenario.
  • the processor is further configured to: encode the report or the first information with one of the following format: an RAT format of the MN; an RAT format of NR; an RAT format of the MN, wherein a trigger condition within the one or more trigger conditions is generated by the MN, and the trigger condition is fulfilled; or an RAT format of an SN, wherein a trigger condition within the one or more trigger conditions is generated by the SN, and the trigger condition is fulfilled, and the SN is a source SN or a target SN.
  • the RAT format of the MN or the RAT format of the SN is one of: a format of an E-UTRAN; a format of NR; or a format of a next generation.
  • the one or more trigger conditions in response to a trigger condition within the one or more trigger conditions is generated by the target SN, include a first threshold associated with timer T304.
  • the one or more trigger conditions in response to a trigger condition within the one or more trigger conditions is generated by the MN or the source SN, include at least one of a second threshold associated with timer T310; or a third threshold associated with timer T312.
  • the processor is further configured to: transmit, the report, or both the report and at least one of cell information associated with a source PSCell or cell information associated with a target PSCell.
  • the report is encoded with the NR format
  • the RAT format of the MN is E-UTRAN or LTE
  • cell information associated with a source PSCell and/or cell information associated with a target PSCell may be transmitted.
  • the report or the first information includes at least one of the following: information associated with a source PSCell; information associated with a target PSCell; information associated with one or more neighbor cells; a cause value indicating which trigger condition for storing the first information is fulfilled; time information associated with the successful CPA or the successful CPC; UE location information; or information associated with a random access procedure to the target PSCell.
  • the cell information includes at least one of the following: a PLMN ID; a cell ID; a TAC; a PCI; or an ARFCN.
  • the processor is further configured to: transmit an indication indicating an availability of the report; receive a request for the report; and transmit the report.
  • the indication may be transmitted to the MN, or to the target SN.
  • Fig. 3 illustrates a method performed by an MN for SON enhancements according to some embodiments of the present disclosure.
  • the MN may determine a configuration regarding first information associated with a successful PSCell change, a successful PSCell addition, a successful CPA, or a successful CPC in an MR-DC scenario, wherein the MN and an SN in the MR-DC scenario utilize different RATs, and the configuration is related to one or more trigger conditions for storing the first information or generating a report including the first information; and transmit, to a UE, the configuration regarding the first information.
  • the processor is further configured to: receive, from the UE, an indication for indicating a UE capability, which indicates that the UE is able to store the first information or generate the report in the MR-DC scenario.
  • the processor is further configured to: receive, from each of one or more candidate target SNs, a first threshold associated with timer T304; and determine the configuration.
  • the configuration may be determined at least based on the first threshold associated with timer T304.
  • the processor is further configured to perform one of the following: generate at least one of a second threshold associated with timer T310, or a third threshold associated with timer T312; and determine the configuration.
  • the configuration may be determined based on at least one of a second threshold associated with timer T310, or a third threshold associated with timer T312.
  • the configuration may be determined based on the first threshold associated with timer T304, and/or, at least one of a second threshold associated with timer T310, or a third threshold associated with timer T312.
  • the processor is further configured to: receive, from a source SN, at least one of a second threshold associated with timer T310, or a third threshold associated with timer T312; and determine the configuration (for example, determine the configuration based on the received first threshold associated with timer T304 and at least one of the received second threshold associated with timer T310, or the received third threshold associated with timer T312) .
  • the processor is further configured to: generate a second threshold associated with timer T310; receive, from the source SN, a third threshold associated with timer T312 (for example, determine the configuration based on the received first threshold associated with timer T304, the generated second threshold associated with timer T310, and the received third threshold associated with timer T312) ; and determine the configuration;
  • the processor is further configured to: generate a third threshold associated with timer T312; receive, from the source SN, a second threshold associated with timer T310; and determine the configuration (for example, determine the configuration based on the received first threshold associated with timer T304, the received second threshold associated with timer T310, and the generated third threshold associated with timer T312) .
  • the processor is further configured to perform one of the following: receive, from the UE or a target SN, the report or the first information; or receive, from the UE or the target SN, the report or the first information, and at least one of cell information associated with a source PSCell or cell information associated with a target PSCell.
  • the processor is further configured to: receive, from the UE, an indication indicating an availability of the report; transmit, to the UE, a request for the report; and receive, from the UE, the report.
  • the report is encoded with a first format
  • the processor is further configured to perform one of the following:
  • the report encoded with the first format to a source SN, a target SN, or both the source SN and the target SN (for example, in option c1, the report is encoded with the E-UTRAN or LTE format, and is transmitted to the source SN) ;
  • the decode the report encoded with the first format re-encode the decoded report with a second format of the target SN, and transmit the report encoded with the second format to the target SN (for example, in option b2, the report is encoded with the RAT format of the target SN, and is transmitted to the target SN) ;
  • the decode the report encoded with the first format re-encode the decoded report with a third format of the source SN, and transmit the report encoded with the third format to the source SN (for example, in option c2, the report received by the MN is re-encoded/re-organized with the RAT format of the source SN, and is transmitted to the source SN) ;
  • the report received by the MN is re-encoded/re-organized with the RAT format of the SN (the SN may be the source SN or the target SN) , and the re-encoded/re-organized report is transmitted to the target SN and the source SN separately; ) , wherein the second format of the target SN and the third format of the source SN are different;
  • the processor is further configured to perform one of the following: transparently transmit the report to a target SN based on cell information associated with the target PSCell in response to the cell information associated with the target PSCell is received; transparently transmit the report to a source SN based on cell information associated with the source PSCell in response to the cell information associated with the source PSCell is received; or transparently transmit the report to the target SN based on cell information associated with the target PSCell and transparently transmit the report to the source SN based on cell information associated with the source PSCell in response to the cell information associated with the target PSCell and the cell information associated with the source PSCell are received.
  • the report is transparently transmitted to the source SN and the target SN separately.
  • Fig. 4 illustrates a method performed by an SN for SON enhancements according to some embodiments of the present disclosure.
  • the SN may determine at least one trigger condition for storing first information associated with a successful PSCell change or PSCell addition or CPA or CPC in an MR-DC scenario, wherein an MN and the SN in the MR-DC scenario utilize different RATs; and in operation 402, the SN may transmit, to the MN or a UE, the at least one trigger condition.
  • the SN is a target SN
  • the at least one trigger condition includes a first threshold associated with timer T304.
  • the SN is a target SN
  • the processor is further configured to perform one of the following: receive a report including the first information from the UE; receive a report including the first information from the MN, wherein the report is encoded with an RAT format of the SN; receive a report including the first information from the MN, wherein the report is encoded with an RAT format of the MN; receive a report including the first information from the MN, wherein the report is encoded with an RAT format of the SN by the MN; or receive explicit information including the first information from the MN.
  • the target SN may receive the above reports from the MN.
  • the SN is a source SN
  • the at least one trigger condition includes at least one of a second threshold associated with timer T310, or a third threshold associated with timer T312.
  • the SN is a source SN
  • the processor is further configured to perform one of the following: receive a report including the first information from the MN, wherein the report is encoded with an RAT format of the SN; receive a report including the first information from the MN, wherein the report is encoded with an RAT format of the MN; receive a report including the first information from the MN, wherein the report is encoded with an RAT format of the SN by the MN; or receive explicit information including the first information from the MN.
  • the source SN may receive the above report or information from the MN.
  • Fig. 5 illustrates a simplified block diagram of an 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, an RAN node, an MN, an SN, a source node, a target node, a third node, 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 an RAN node.
  • the transceiver 502 and the processor 504 may interact with each other so as to perform the operations of the RAN 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 RAN node as described above.
  • the computer-executable instructions when executed, cause the processor 504 interacting with transceiver 502 to perform the operations of the RAN 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 demande concerne des procédés et des appareils pour des améliorations de SON. Un mode de réalisation de la présente divulgation concerne un équipement utilisateur (UE) qui comprend : un émetteur-récepteur ; et un processeur couplé à l'émetteur-récepteur et configuré pour : recevoir une configuration concernant des premières informations associées à un changement PSCell réussi, à une addition PSCell réussie, à une addition PSCell conditionnelle réussie (CPA), ou à un changement PSCell conditionnel réussi (CPC) dans un scénario MR-DC, un nœud maître (MN) et un nœud secondaire (SN) dans le scénario MR-DC utilisant différentes technologies d'accès radio (RAT), et la configuration étant associée à une ou plusieurs conditions de déclenchement pour stocker les premières informations ; et générer un rapport comprenant les premières informations dans le scénario MR-DC lorsqu'au moins une condition de déclenchement dans les une ou plusieurs conditions de déclenchement est satisfaite.
PCT/CN2023/072712 2023-01-17 2023-01-17 Procédés et appareils pour des améliorations de son WO2024073980A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2023/072712 WO2024073980A1 (fr) 2023-01-17 2023-01-17 Procédés et appareils pour des améliorations de son

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2023/072712 WO2024073980A1 (fr) 2023-01-17 2023-01-17 Procédés et appareils pour des améliorations de son

Publications (1)

Publication Number Publication Date
WO2024073980A1 true WO2024073980A1 (fr) 2024-04-11

Family

ID=90607405

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/072712 WO2024073980A1 (fr) 2023-01-17 2023-01-17 Procédés et appareils pour des améliorations de son

Country Status (1)

Country Link
WO (1) WO2024073980A1 (fr)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022082644A1 (fr) * 2020-10-22 2022-04-28 Oppo广东移动通信有限公司 Procédé de changement de nœud secondaire, dispositif de terminal et dispositif de réseau
WO2022084019A1 (fr) * 2020-10-21 2022-04-28 Nokia Technologies Oy Système de communication mobile à double connectivité
US20230007550A1 (en) * 2021-07-01 2023-01-05 Qualcomm Incorporated Reporting for conditional primary secondary cell addition or change

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022084019A1 (fr) * 2020-10-21 2022-04-28 Nokia Technologies Oy Système de communication mobile à double connectivité
WO2022082644A1 (fr) * 2020-10-22 2022-04-28 Oppo广东移动通信有限公司 Procédé de changement de nœud secondaire, dispositif de terminal et dispositif de réseau
US20230007550A1 (en) * 2021-07-01 2023-01-05 Qualcomm Incorporated Reporting for conditional primary secondary cell addition or change

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
QUALCOMM INCORPORATED: "CPA and MN initiated Inter-SN CPC procedures: preparation, execution, and data forwarding", 3GPP DRAFT; R3-211757, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG3, no. E-meeting; 20210517 - 20210528, 7 May 2021 (2021-05-07), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP052002040 *
QUALCOMM INCORPORATED: "CPAC procedures from network perspective", 3GPP DRAFT; R2-2105260, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Online; 20210519 - 20210527, 11 May 2021 (2021-05-11), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP052006909 *

Similar Documents

Publication Publication Date Title
WO2022141470A1 (fr) Procédé et appareil d'exécution de procédure de transfert intercellulaire
EP3432678B1 (fr) Dispositif et procédé de configuration d'un noeud secondaire et de rapport en double connectivité
US20210377832A1 (en) Mobility enhancement in a connected state
US10631236B2 (en) Method of handling measurement and related communication device
WO2023130315A1 (fr) Procédés et appareils de mro pour un changement de cellule primaire secondaire ou cpac dans nr-u
JP7306474B2 (ja) ビーム失敗回復方法、装置及び通信システム
US20220377630A1 (en) Method and apparatus for performing mobility robustness optimization in a handover procedure
US20240032105A1 (en) Method and apparatus for performing random access
US20230422135A1 (en) Method and apparatus for mobility robustness optimization
WO2024073980A1 (fr) Procédés et appareils pour des améliorations de son
US20240121832A1 (en) Method and apparatus for performing random access
US20240121797A1 (en) Method and apparatus for monitoring downlink control information
WO2023283931A1 (fr) Procédé et appareil de détermination de formats de créneau de transmission de liaison montante et de liaison descendante
US20240224246A1 (en) Method and apparatus for determining slot formats of uplink and downlink transmission
WO2024000097A1 (fr) Procédés et appareils d'améliorations pour une procédure ho inter-rat
IL273668B (en) Wireless communication method and device
WO2022082584A1 (fr) Procédés et appareils pour un mécanisme de désactivation de scg et un mécanisme d'activation de scg dans un scénario mr-dc
WO2024082460A1 (fr) Procédés et appareils pour prendre en charge la coexistence de différents types de mobilité
WO2022032637A1 (fr) Procédés et appareils pour une procédure de partage de groupe entre des ue de liaison latérale rn
WO2023050349A1 (fr) Procédés et appareils pour mécanisme mro
WO2023193240A1 (fr) Procédés et appareils pour une préparation de transfert dans un cas de relais u2n l2
US20240073968A1 (en) Method and apparatus for handling fallback of data transmission
WO2022040870A1 (fr) Procédé et appareil de détection de défaillance de faisceau et de reprise sur défaillance de faisceau dans une liaison latérale
WO2024007306A1 (fr) Dispositif réseau et procédé d'échange d'informations de prédiction dans un mode à double connectivité
US20230412240A1 (en) Method and apparatus for beam failure recovery in multi-dci based multiple trps

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

Country of ref document: EP

Kind code of ref document: A1