WO2024025362A1 - Procédé et appareil pour la prise en charge d'une auto-configuration et d'une auto-optimisation - Google Patents

Procédé et appareil pour la prise en charge d'une auto-configuration et d'une auto-optimisation Download PDF

Info

Publication number
WO2024025362A1
WO2024025362A1 PCT/KR2023/010932 KR2023010932W WO2024025362A1 WO 2024025362 A1 WO2024025362 A1 WO 2024025362A1 KR 2023010932 W KR2023010932 W KR 2023010932W WO 2024025362 A1 WO2024025362 A1 WO 2024025362A1
Authority
WO
WIPO (PCT)
Prior art keywords
failure
pscell
information
cpc
scg
Prior art date
Application number
PCT/KR2023/010932
Other languages
English (en)
Inventor
Lixiang Xu
Weiwei Wang
Original Assignee
Samsung Electronics Co., Ltd.
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
Priority claimed from CN202211236864.4A external-priority patent/CN117528678A/zh
Application filed by Samsung Electronics Co., Ltd. filed Critical Samsung Electronics Co., Ltd.
Publication of WO2024025362A1 publication Critical patent/WO2024025362A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/24—Reselection being triggered by specific parameters
    • H04W36/30—Reselection being triggered by specific parameters by measured or perceived connection quality data
    • H04W36/305—Handover due to radio link failure
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/19—Connection re-establishment
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0055—Transmission or use of information for re-establishing the radio link
    • H04W36/0069—Transmission or use of information for re-establishing the radio link in case of dual connectivity, e.g. decoupled uplink/downlink
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/34—Reselection control
    • H04W36/36—Reselection control by user or terminal equipment
    • H04W36/362—Conditional handover
    • 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 generally to wireless communication technology, and more specifically, the present disclosure relates to a method and apparatus for supporting self-configuration and self-optimization.
  • 5G mobile communication technologies define broad frequency bands such that high transmission rates and new services are possible, and can be implemented not only in “Sub 6GHz” bands such as 3.5GHz, but also in “Above 6GHz” bands referred to as mmWave including 28GHz and 39GHz.
  • 6G mobile communication technologies referred to as Beyond 5G systems
  • terahertz bands for example, 95GHz to 3THz bands
  • IIoT Industrial Internet of Things
  • IAB Integrated Access and Backhaul
  • DAPS Dual Active Protocol Stack
  • 5G baseline architecture for example, service based architecture or service based interface
  • NFV Network Functions Virtualization
  • SDN Software-Defined Networking
  • MEC Mobile Edge Computing
  • multi-antenna transmission technologies such as Full Dimensional MIMO (FD-MIMO), array antennas and large-scale antennas, metamaterial-based lenses and antennas for improving coverage of terahertz band signals, high-dimensional space multiplexing technology using OAM (Orbital Angular Momentum), and RIS (Reconfigurable Intelligent Surface), but also full-duplex technology for increasing frequency efficiency of 6G mobile communication technologies and improving system networks, AI-based communication technology for implementing system optimization by utilizing satellites and AI (Artificial Intelligence) from the design stage and internalizing end-to-end AI support functions, and next-generation distributed computing technology for implementing services at levels of complexity exceeding the limit of UE operation capability by utilizing ultra-high-performance communication and computing resources.
  • FD-MIMO Full Dimensional MIMO
  • OAM Organic Angular Momentum
  • RIS Reconfigurable Intelligent Surface
  • an aspect of the present invention provides a method and apparatus for supporting self-configuration and self-optimization.
  • a method performed by a first network node of a communication system may include receiving information related to Secondary Cell Group (SCG) failure from a User Equipment (UE); transmitting first failure report information to a second network node.
  • SCG Secondary Cell Group
  • UE User Equipment
  • the method may further comprise receiving second failure report information from the second network node, and transmitting third failure report information to a third network node based on the second failure message.
  • the information related to the SCG failure includes a Radio Resource Control (RRC) container, which refers to a RRC format of a Radio Access Technology (RAT) supported by a Primary SCG Cell (PSCell), or refers to the RRC format of the RAT supported by the second network node or the third network node.
  • RRC Radio Resource Control
  • RAT Radio Access Technology
  • PSCell Primary SCG Cell
  • the RRC container may contain SCG failure information SCGFailureInformation.
  • the first failure report information or the third failure report information includes at least a part of the information related to the SCG failure.
  • the first failure report information or the third failure report information includes the RRC container.
  • the first failure report information or the third failure report information may include at least one of the following information: a cell identity of a source Primary SCG Cell (PSCell), a cell identity of a target PSCell, a cell identity of a suitable PSCell, Secondary Cell Group (SCG) failure information received from the UE, a list of candidate PSCells recommended by a source Master Node (MN) or a source Secondary Node (SN), Conditional PSCell Change (CPC) execution condition(s), a list of candidate PSCells selected by a target SN or a candidate target SN, an estimated arrival probability, a type of the failure, a cell identity of a failed PSCell, a time duration from receiving a RRC reconfiguration message for a PSCell change to the failure, information related to a random access, a measurement result of the UE, location information of the UE, a list of CPC candidate cells, and CPC execution condition(s).
  • PSCell Primary SCG Cell
  • SCG Secondary Cell Group
  • it may further comprise: determining which network node leads to the failure based on the information related to the SCG failure.
  • it may further include determining a type of the failure based on the information related to the SCG failure.
  • the first failure report information or the third failure report information is transmitted through an inter-base station interface message.
  • the inter-base station interface message may be an inter-base station RRC message, an inter-node RRC message, an Xn or X2 message of an inter-base station interface, other inter-base station interface messages, or other network interface messages.
  • the second failure report information may include at least one of the following information: a Master Node UE Access Protocol Identity (MN UE AP ID); a Secondary Node UE Access Protocol Identity (SN UE AP ID); a list of candidate Primary SCG Cells (PSCells) recommended by a source secondary node; a list of candidate PSCells selected by a target secondary node or a candidate target secondary node; a cell identity of a suitable PSCell; information related to the SCG failure; a cell identity of a source PSCell; a cell identity of a target PSCell; a cell identity of a suitable PSCell which is not selected by the target network node or the candidate target network node; and indication information that the selected candidate PSCell is not suitable.
  • MN UE AP ID Master Node UE Access Protocol Identity
  • SN UE AP ID Secondary Node UE Access Protocol Identity
  • PSCells Primary SCG Cells
  • the PSCell in case that there is recent PSCell change, the PSCell is the source PSCell of the recent PSCell change, or in case there is no recent PSCell change, the PSCell is a PSCell serving the UE when the SCG failure occurs.
  • the information related to the SCG failure received from the UE may include at least one of the following information: indication information that whether the CPC has been executed; a time from the CPC execution to the failure; a cell identity of a failed PSCell; a cell identity of a source PSCell of the latest PSCell change; a cell list of CPC candidate PSCells; CPC execution condition(s); a time from the UE receiving a RRC reconfiguration message of the PSCell change from to the failure; a time from the UE receiving CPC configuration to the failure; a time from the UE receiving the CPC configuration to the CPC execution; when a CPC execution condition is fulfilled for execution, indication information corresponding to the CPC execution condition being fulfilled for execution; information that which CPC execution condition is fulfilled first; a time duration between two CPC execution conditions being fulfilled; indication information on the CPC or CPA; a type of the failure; measurement result of the UE; location information of the UE; and information related to a random access
  • a first network node in a communication system may include a transceiver configured to transmit and receive signals; and a controller coupled to the transceiver and configured to perform operations in the methods as described in the embodiments of the present disclosure.
  • the robustness of the Primary SCG Cell (PSCell) change in the mobility procedure can be supported by the method. Furthermore, through the method, the robustness of the PSCell change between the different RATs can be supported. Thus, a cause of failure can be correctly identified, so as to make reasonable optimization, reduce occurrence of failure, ensure service continuity, and reduce labor cost of operators.
  • PSCell Primary SCG Cell
  • Couple and its derivatives refer to any direct or indirect communication between two or more elements, whether or not those elements are in physical contact with one another.
  • transmit and “communicate,” as well as derivatives thereof, encompass both direct and indirect communication.
  • the term “or” is inclusive, meaning and/or.
  • controller means any device, system, or part thereof that controls at least one operation. Such a controller may be implemented in hardware or a combination of hardware and software and/or firmware. The functionality associated with any particular controller may be centralized or distributed, whether locally or remotely.
  • phrases "at least one of,” when used with a list of items, means that different combinations of one or more of the listed items may be used, and only one item in the list may be needed.
  • “at least one of: A, B, and C” includes any of the following combinations: A, B, C, A and B, A and C, B and C, and A and B and C.
  • various functions described below can be implemented or supported by one or more computer programs, each of which is formed from computer readable program code and embodied in a computer readable medium.
  • application and “program” refer to one or more computer programs, software components, sets of instructions, procedures, functions, objects, classes, instances, related data, or a portion thereof adapted for implementation in a suitable computer readable program code.
  • computer readable program code includes any type of computer code, including source code, object code, and executable code.
  • computer readable medium includes any type of medium capable of being accessed by a computer, such as read only memory (ROM), random access memory (RAM), a hard disk drive, a compact disc (CD), a digital video disc (DVD), or any other type of memory.
  • ROM read only memory
  • RAM random access memory
  • CD compact disc
  • DVD digital video disc
  • a "non-transitory” computer readable medium excludes wired, wireless, optical, or other communication links that transport transitory electrical or other signals.
  • a non-transitory computer readable medium includes media where data can be permanently stored and media where data can be stored and later overwritten, such as a rewritable optical disc or an erasable memory device.
  • Fig. 1 is a system architecture diagram of System Architecture Evolution (SAE);
  • Fig. 2 is a schematic diagram illustrating an initial overall architecture of 5G
  • Fig. 3 is a flowchart of a first method according to an embodiment of the present disclosure
  • Fig. 4 is a schematic diagram of an embodiment of the first method according to an embodiment of the present disclosure.
  • Fig. 5 is a schematic diagram of another embodiment of the first method according to an embodiment of the present disclosure.
  • Fig. 6 is a flowchart diagram of an embodiment of a second method according to anembodiment of the present disclosure
  • Fig. 7 is a schematic diagram of an embodiment of the second method according to anembodiment of the present disclosure.
  • Fig. 8 is a schematic diagram of another embodiment of the second method according to anembodiment of the present disclosure.
  • Fig. 9 is a block diagram of a network node according to an embodiment of the present disclosure.
  • Couple and its derivatives refer to any direct or indirect communication between two or more elements, whether or not those elements are in physical contact with one another.
  • transmit and “communicate,” as well as derivatives thereof, encompass both direct and indirect communication.
  • the term “or” is inclusive, meaning and/or.
  • controller means any device, system or part thereof that controls at least one operation. Such a controller can be implemented in hardware or a combination of hardware and software and/or firmware. The functionality associated with any particular controller can be centralized or distributed, whether locally or remotely.
  • phrases "at least one of,” when used with a list of items, means that different combinations of one or more of the listed items can be used, and only one item in the list can be needed.
  • “at least one of: A, B, and C” includes any of the following combinations: A, B, C, A and B, A and C, B and C, and A and B and C.
  • “at least one of: A, B, or C” includes any of the following combinations: A, B, C, A and B, A and C, B and C, and A, B and C.
  • various functions described below can be implemented or supported by one or more computer programs, each of which is formed from computer-readable program code and embodied in a computer-readable medium.
  • application and “program” refer to one or more computer programs, software components, sets of instructions, procedures, functions, objects, classes, instances, related data, or a portion thereof adapted for implementation in an appropriate computer-readable program code.
  • computer-readable program code includes any type of computer code, including source code, object code, and executable code.
  • computer-readable medium includes any type of medium capable of being accessed by a computer, such as Read-Only Memory (ROM), Random Access Memory (RAM), a hard disk drive, a Compact Disc (CD), a Digital Video Disc (DVD), or any other type of memory.
  • ROM Read-Only Memory
  • RAM Random Access Memory
  • CD Compact Disc
  • DVD Digital Video Disc
  • a "non-transitory” computer-readable medium excludes wired, wireless, optical, or other communication links that transport transitory electrical or other signals.
  • a non-transitory computer-readable medium includes media where data can be permanently stored and media where data can be stored and later overwritten, such as a rewritable optical disc or an erasable memory device.
  • any reference to “an example” or “example”, “an embodiment” or “embodiment” means that particular elements, features, structures or characteristics described in connection with the embodiment is included in at least one embodiment.
  • the phrases “in one embodiment” or “in one example” appearing in different places in the specification do not necessarily refer to the same embodiment.
  • a portion of something means “at least some of” the thing, and as such may mean less than all of, or all of, the thing.
  • a portion of a thing includes the entire thing as a special case, i.e., the entire thing is an example of a portion of the thing.
  • the technical schemes of the embodiments of the present application can be applied to various communication systems, and for example, the communication systems may include global systems for mobile communications (GSM), code division multiple access (CDMA) systems, wideband code division multiple access (WCDMA) systems, general packet radio service (GPRS) systems, long term evolution (LTE) systems, LTE frequency division duplex (FDD) systems, LTE time division duplex (TDD) systems, universal mobile telecommunications system (UMTS), worldwide interoperability for microwave access (WiMAX) communication systems, 5th generation (5G) systems or new radio (NR) systems, etc.
  • GSM global systems for mobile communications
  • CDMA code division multiple access
  • WCDMA wideband code division multiple access
  • GPRS general packet radio service
  • LTE long term evolution
  • TDD LTE time division duplex
  • UMTS universal mobile telecommunications system
  • WiMAX worldwide interoperability for microwave access
  • 5G 5th generation
  • NR new radio
  • the term “include” or “may include” refers to the existence of a corresponding disclosed functions, operations or components which can be used in various embodiments of the present disclosure and does not limit one or more additional functions, operations, or components.
  • the terms such as “include” and/or “have” may be construed to denote a certain characteristic, number, step, operation, constituent element, component or a combination thereof, but may not be construed to excludea possibility of the existence of one or more other characteristics, numbers, steps, operations, constituent elements, components or combinations thereof.
  • a or B may include A, may include B, or may include both A and B.
  • Figs. 1 to 9 discussed below and various embodiments for describing the principles of the present disclosure in the present patent document are only for illustration and should not be interpreted as limiting the scope of the disclosure in any way. Those skilled in the art will understand that the principles of the present disclosure can be implemented in any suitably arranged system or device.
  • Fig. 1 is an exemplary system architecture 100 of system architecture evolution (SAE).
  • UE User equipment
  • E-UTRAN evolved universal terrestrial radio access network
  • E-UTRAN is a radio access network, which includes a macro base station (eNodeB/NodeB) that provides UE with interfaces to access the radio network.
  • a mobility management entity (MME) 103 is responsible for managing mobility context, session context and security information of the UE.
  • MME mobility management entity
  • SGW serving gateway
  • a packet data network gateway (PGW) 105 is responsible for functions of charging, lawful interception, etc., and may be in the same physical entity as the SGW 104.
  • a policy and charging rules function entity (PCRF) 106 provides quality of service (QoS) policies and charging criteria.
  • a general packet radio service support node (SGSN) 108 is a network node device that provides routing for data transmission in a universal mobile telecommunications system (UMTS).
  • UMTS universal mobile telecommunications system
  • a home subscriber server (HSS)109 is a home subsystem of the UE, and is responsible for protecting user information including a current position of the user equipment, an address of a serving node, user security information, and packet data context of the user equipment, etc.
  • Fig. 2 is an exemplary system architecture 200 according to various embodiments of the present disclosure. Other embodiments of the system architecture 200 can be used without departing from the scope of the present disclosure.
  • User equipment (UE) 201 is a terminal device for receiving data.
  • a next generation radio access network (NG-RAN) 202 is a radio access network, which includes a base station (a gNB or an eNB connected to 5G core network 5GC, and the eNB connected to the 5GC is also referred to as ng-gNB) that provides UE with interfaces to access the radio network.
  • An access control and mobility management function entity (AMF) 203 is responsible for managing mobility context and security information of the UE.
  • a user plane function entity (UPF) 204 mainly provides functions of user plane.
  • a session management function entity SMF 205 is responsible for session management.
  • a data network (DN) 206 includes, for example, services of operators, access of Internet and service of third parties.
  • Secondary Cell Group (SCG) Failure Information Report contains contents of SCGFailureInformation received from a UE.
  • An MN Master Node
  • the MN decides whether to forward the SCGFailureInformation to the Secondary Node (SN) which causes the failure or to copy information in the SCGFailureInformation into the SCG Failure Information Report message, according to whether different Radio Access Technologies (RATs) are supported by the SN which causes the failure and the Master Node (MN).
  • RATs Radio Access Technologies
  • the MN includes the SCGFailureInformation as a container into an inter-base station interface message transmitted to the SN, and this container is an Information Element (IE) in the inter-base station interface message.
  • IE Information Element
  • the MN includes one or more or all of information elements in the SCGFailureinformation into the SCG Failure Information Report, and the SCGFailureInformation container may not be included or may be included at the same time. In this way, the SN which causes the issue can obtain the information related to SCG failure transmitted by the UE without parsing the RRC container encoded in the RRC format of the MN.
  • the SCGFailureInformation here can be SCGFailureInformation, SCGFailureInformationEUTRA, or SCGFailureInformationNR.
  • the UE transmits the SCGFailureInformation in the NR RRC to the MN;
  • the UE transmits SCGFailureInformationEUTRA to the MN;
  • the UE transmits SCGFailureInformation in the E-UTRA RRC to the MN;
  • the UE transmits SCGFailureInformationNR to the MN.
  • the SCGFailureinformation or SCGFailureinformationEUTRA of the RRC of the first radio access technology contains the SCGFailureInformation in the RRC format of the second radio access technology.
  • the SCGFailureinformation or SCGFailureinformationEUTRA in NR RRC contains the SCGFailureInformation in the LTE RRC format.
  • the SCGFailureInformation in the LTE RRC format is a container in the NR RRC message.
  • the SCGFailureinformation or the SCGFailureinformationNR in the LTE RRC contains the SCGFailureInformation in the NR RRC format.
  • the UE includes SCGFailueInformation in the source PSCell RRC format (i.e., a container) into the SCGFailueInformation or the SCGFailueInformationEUTRA or the SCGFailueInformationNR in the MN RRC, according to whether there is a recent Primary SCG Cell (PSCell, SpCell (a primary cell of a master or secondary cell group) of a secondary cell group) change and the source PSCell and the MN supporting different RATs.
  • the SCGFailureInformation in the PSCell RRC format is a container, the container referring to the Radio Resource Control (RRC) format of the Radio Access Technology (RAT) supported by the PSCell.
  • RRC Radio Resource Control
  • the UE can also include the SCGFailueInformation in the target PSCell RRC format into the SCGFailueInformation or the SCGFailueInformationEUTRA or the SCGFailueInformationNR in the MN RRC, according to whether there is a recent PSCell change and the target PSCell and the MN supporting different RATs.
  • the approach proposed in the present disclosure is applicable to the PSCell change procedure, including a normal PSCell Change procedure and a Conditional PSCell Change (CPC) procedure or a Conditional PSCell Addition (CPA) procedure.
  • CPC Conditional PSCell Change
  • CPA Conditional PSCell Addition
  • the CPC and CPA procedure although the CPC is taken as an example in the present disclosure, the problems and methods described in the present disclosure are also applicable to the CPA procedure. When applying to the CPA, it is only necessary to replace the CPC with the CPA. Similarly, the methods described in the present disclosure are also applicable to a Conditional PSCell Addition or Change (CPAC) procedure, and the CPC is replaced by the CPAC when applying.
  • CPAC Conditional PSCell Addition or Change
  • Fig. 3 illustrates an example of a first method for supporting self-configuration and self-optimization according to the present disclosure.
  • the method is described from a perspective of a master base station.
  • the method comprises the following steps:
  • a master node receives information on Secondary Cell Group (SCG) failure from a UE.
  • the information on the SCG failure may be SCGFailureInformation or SCGFailureInformationEUTRA in TS38.331, or SCGFailureInformation or SCGFailureInformationNR in TS36.331, or it may be the information on the SCG failure received through other messages.
  • the information on the SCG failure includes one or more of the following information elements:
  • the cell identity may be information on a global cell identity, or a physical cell identity and a frequency.
  • the global cell identity may further include Tracking Area Code (TAC) or a tracking area identity of the cell;
  • TAC Tracking Area Code
  • the cell identity may be information on a global cell identity, or a physical cell identity and a frequency.
  • the global cell identity can also include the Tracking Area Code (TAC) or the tracking area identity of the cell;
  • TAC Tracking Area Code
  • a cell list of CPC candidate PSCells A list of candidate CPC cells may be included directly, or indication information that a cell is CPC candidate cell is included for the cells in a measurement result which are the CPC candidate cell, additionally, information on one or more cells which are the CPC candidate cells but not in the measurement result is comprised in the secondary cell group failure information.
  • Each of the candidate PSCells contains a cell identity, which may be a global cell identity.
  • the cell identity may further include Tracking Area Code (TAC);
  • the CPC execution condition(s) can be one or more. There are one or more execution conditions for each of candidate PSCell cells;
  • RA Random Access
  • the above failure is a SCG failure.
  • the master node decides which node leads to the failure. For example, it is the Master Node (MN), the Source Secondary Node(S-SN), the Target Secondary Node (T-SN) or other candidate secondary node.
  • the master node may transmit the SCG failure information to the secondary node where the failure occurs, and the secondary node, where the failure occurs, determines whether the failure is caused by itself.
  • the master node decides which node leads to the failure according to information in the SCG failure information received from the UE and/or information stored by the MN.
  • the master node can also determine a type of failure occurring, such as a too early PSCell change, a too late PSCell change or trigger of a PSCell change to a wrong PSCell cell.
  • a type of failure occurring such as a too early PSCell change, a too late PSCell change or trigger of a PSCell change to a wrong PSCell cell.
  • a SCG failure occurs after a UE has stayed in a PSCell for a long time, for example, if the UE does not report the time from an RRC reconfiguration message including SCG reconfiguration with synchronization to the SCG failure occurrence or the time is greater than a configured threshold, and there is a suitable PSCell different from the PSCell where the UE is located at the time that the failure occurs, then it is the too late PSCell change.
  • the UE does not report the time from the CPC execution to the failure occurrence, or the time from the CPC execution to the failure occurrence reported by the UE is greater than a configured threshold, and there is a suitable PSCell different from the PSCell where the UE is located at the time the failure occurrs, then it is the too late CPC execution or the too late PSCell change.
  • the MN knows the suitable PSCell according to a measurement report received from the UE, or the MN knows the suitable PSCell according to the measurement report received from the UE and the information stored by the MN.
  • Too early PSCell change there is a recent CPC execution or PSCell change before the failure occurs, for example, according to an indication on CPC execution or according to a time from the CPC execution to the failure occurrence being smaller than a configured threshold or according to the time from the RRC reconfiguration message including SCG reconfiguration with synchronization to the SCG failure occurrence being smaller than a configured threshold, and the source PSCell is a suitable PSCell, thus it is a too early PSCell change.
  • the MN knows the suitable PSCell according to the measurement report received from the UE, or the MN knows the suitable PSCell according to the measurement report received from the UE and the information stored by the MN.
  • the SCG failure can be a failure which occurs shortly after a successful change from a source PSCell to a target PSCell or a failure which occurs during the PSCell change procedure.
  • the source PSCell is a source PSCell of the latest PSCell change.
  • the MN knows the suitable PSCell according to the measurement report received from the UE, or the MN knows the suitable PSCell according to the measurement report received from the UE and the information stored by the MN.
  • the SCG failure can a failure which occurs shortly after a successful change from a source PSCell to a target PSCell or a failure which occurs during the PSCell change procedure.
  • the source PSCell is a source PSCell of the latest PSCell change.
  • the target PSCell is a target PSCell of the latest PSCell change.
  • the MN and the source SN serving the UE are the nodes that lead to the failure.
  • the MN is the node that leads to the failure. If the PSCell change is triggered by the source SN, the source SN is the node that leads to the failure.
  • the MN is the node that leads to the failure. If the PSCell change is triggered by the source SN, the source SN is the node that leads to the failure.
  • the MN can further determine whether the failure is caused by the unreasonable configuration of CPC candidate cells or by the unreasonable configuration of CPC execution condition. If the suitable cell is not in the CPC candidate cells configured to the UE, the failure is caused by the unreasonable configuration of CPC candidate cells. If the suitable cell is not in the list of the CPC candidate cells recommended by a source base station (the MN or a source SN) that triggers the PSCell change, the problem is caused by the source base station that triggers the PSCell change.
  • a source base station the MN or a source SN
  • the PSCell change is triggered by the MN
  • a problem is caused by the MN
  • the PSCell change is triggered by the source SN
  • the problem is caused by the source SN.
  • the suitable cell is in the list of the CPC candidate cells recommended by the source base station (the MN or the source SN) that triggers the PSCell change, but not in the list of the candidate PSCells selected by the target SN or the candidate target SN, the failure is caused by the target SN or the candidate target SN.
  • the MN can also determine whether the failure is caused by an estimated arrival possibility which is set improperly.
  • the estimated arrival probability transmitted to the candidate target SN by the MN or by the source SN through the MN is set too low, while the suitable cell is in the candidate SN, and thus the MN or the source SN is the node that leads to the failure. If the estimated arrival probability is decided by the source SN, then the failure is caused by the source SN.
  • step 303 does not need to be performed. If the problem is caused by the source SN, the target SN or the candidate target SN, step 303 is performed.
  • the master node transmits the secondary cell group failure indication or report to the secondary node which leads to the failure.
  • the secondary node which leads to the failure can be the source SN, the target SN or the candidate SN.
  • the secondary node which leads to the failure can be the target SN or the candidate SN.
  • the secondary node which leads to the failure can be the source SN or the SN where the failure occurs.
  • the MN knows that the failure is caused by the source SN, the target SN or the candidate target SN.
  • the MN can transmit information on the secondary cell group failure to the secondary node which leads to the failure through the secondary cell group failure information report message or other messages. If the MN and the SN which leads to the failure are nodes supporting different Radio Access Technologies (RATs), the MN includes one or more or all information contained in the SCG failure information received from the UE into the inter-base station interface (such as Xn or X2 interface) message to be transmitted to the SN.
  • RATs Radio Access Technologies
  • the MN directly includes the secondary cell group failure information (such as SCGFailureInformation or SCGFailureInformationEUTRA or SCGFailureNR) received from the UE into the inter-base station interface message to be transmitted to the SN, that is, it is transmitted to the SN in the form of a Radio Resource Control (RRC) container.
  • RRC Radio Resource Control
  • the MN puts a part of or all content of the secondary cell group failure information in the RRC message into the inter-base station interface message respectively and transmits themessage to the SN.
  • the inter-base station interface message may be an inter-base station RRC message, an inter-node RRC message, an Xn or X2 message of an inter-base station interface, other inter-base station interface messages, or other network interface messages.
  • the MN puts the information in the SCG failure information into the inter-base station interface message and transmits the inter-base station interface message to the SN.
  • the inter-base station interface message may be an inter-base station interface RRC message or an inter-node RRC message, and the MN transmits the inter-base station interface RRC message or the inter-node RRC message to the SN.
  • the MN may include the inter-base station interface RRC message or the inter-node RRC message into the Xn or X2 message and transmit the same to the SN.
  • the inter-base station interface RRC message or inter-node RRC message is encoded according to the RRC format of the radio access technology supported by the SN.
  • the inter-base station interface RRC message or inter-node RRC message may be a newly defined inter-node RRC message or an existing inter-node RRC message, and no limitation is made on the method of the present disclosure.
  • the MN can also respectively put a part of or all contents of the secondary cell group failure information into the Xn or X2 or other network interface messages transmitted to the SN, and what is included into the message is a plurality of IEs in the secondary cell group failure information. In this way, even if the SN does not support the RRC of the radio access technology of the MN, the SN can obtain necessary information from the inter-base station interface message, so as to detect the type of the failure and make corresponding optimization.
  • the MN may not include the secondary cell group failure information (such as SCGFailureInformation or SCGFailureInformationEUTRA or SCGFailureNR) received from the UE into the message to be transmitted to the SN, that is, the inter-base station interface message may not include the RRC container, and the MN may also include the secondary cell group failure information container into the inter-base station interface message.
  • the secondary cell group failure information such as SCGFailureInformation or SCGFailureInformationEUTRA or SCGFailureNR
  • the MN is a gNB supporting the new radio (NR) access technology
  • the SN is an ng-eNB supporting the evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (E-UTRA).
  • E-UTRA evolved Universal Mobile Telecommunications System
  • the MN includes the SCGFailureInformationEUTRA into the SCG failure information report message to be transmitted to the SN.
  • the MN includes one or more or all information elements contained in the SCGFailureInformationEUTRA into the inter-base station interface RRC message or the inter-node RRC message respectively, and transmits the inter-base station interface RRC message or the inter-node RRC message to the SN.
  • the MN transmits the inter-base station interface RRC message or the inter-node RRC message to the SN through the SCG failure information report message.
  • the inter-base station interface RRC message or the inter-node RRC message is encoded according to the RRC format of the radio access technology supported by the SN.
  • the inter-base station interface RRC message or the inter-node RRC message is encoded according to the RRC format of the E-UTRA, for example, defined in TS36.331; or the MN includes one or more or all information elements contained in the SCGFailureInformationEUTRA into the SCG failure information report message, respectively.
  • a type of failure, measurement result, location information, a source PSCell identity, a failed PSCell identity, a list of PSCell candidate cells, and/or PSCell execution condition(s) contained in the SCGFailureInformationEUTRA are included into the SCG failure information report message, and the SCGFailureInformationEUTRA container may be or may not be included in SCG failure information report message.
  • the message transmitted by the master node to the secondary node which caused the problem contains one or more information elements in the secondary cell group failure information received from the UE. For example:
  • Each of candidate PSCells includes a cell identity, which may be a global cell identity.
  • the global cell identity may further include a tracking area code (TAC);
  • Each of candidate PSCells includes a cell identity, which may be a global cell identity.
  • a Tracking Area Code (TAC) can be further included;
  • the type of the failure includes a too early PSCell change, a too late PSCell change or trigger of a PSCell change to a wrong PSCell, an inappropriate configuration for the CPC candidate cell, an inappropriate CPC execution condition, and/or an inappropriate configuration for the estimated arrival probability.
  • the information is included when the type of the failure is determined by the MN, and the information element is not included if the type of failure is determined by the SN which leads to the problem.
  • the source SN, the target SN or the candidate SN determines the type of failure, such as, e.g., a too early PSCell change, a too late PSCell change or trigger of a PSCell change to a wrong PSCell, after receiving the message from the MN.
  • a SCG failure occurs after a UE has stayed in a PSCell for a long time, for example, if the UE does not report the time from the RRC reconfiguration message including SCG reconfiguration with synchronization to the SCG failure occurrence, or the time is greater than a configured threshold, and there is a suitable PSCell different from the PSCell where the UE is located at the time the failure occurs, then it is the too late PSCell change.
  • the UE does not report the time from the CPC execution to the failure occurrence, or the time from the CPC execution to the failure occurrence reported by the UE is greater than a configured threshold, and there is a suitable PSCell different from the PSCell where the UE is located at the time the failure occurs, then it is the too late CPC execution or the too late PSCell change.
  • the SN knows the suitable PSCell according to a measurement report received from the UE, or the SN knows the suitable PSCell according to the measurement report received from the UE and the information stored by the SN.
  • Too early PSCell change there is a recent CPC execution or PSCell change before the failure occurs, for example, according to an indication on CPC execution or according to a time from the CPC execution to the failure occurrence being smaller than a configured threshold or according to a time from the RRC reconfiguration message including SCG reconfiguration with synchronization to the SCG failure occurrence being smaller than a configured threshold, and the source PSCell is a suitable PSCell, thus it is a too early PSCell change.
  • the SN knows the suitable PSCell according to a measurement report received from the UE, or the SN knows the suitable PSCell according to the measurement report received from the UE and the information stored by the SN.
  • the SCG failure can a failure which occurs shortly after a successful change from a source PSCell to a target PSCell or a failure which occurs during the PSCell change procedure.
  • the source PSCell is a source PSCell of the latest PSCell change.
  • Trigger of a PSCell change to a wrong PSCell before the failure occurs, there is a recent CPC execution or PSCell change, for example, according to an indication on CPC execution or according to a time from the CPC execution to the failure occurrence being smaller than a configured threshold or according to a time the RRC reconfiguration message including SCG reconfiguration with synchronization to the SCG failure occurrence being smaller than a configured threshold, and the suitable PSCell is not the source PSCell or the target PSCell, it is trigger of the PSCell change to a wrong PSCell.
  • the SN knows the suitable PSCell according to a measurement report received from the UE, or the SN knows the suitable PSCell according to the measurement report received from the UE and the information stored by the SN.
  • the SCG failure can a failure which occurs shortly after a successful change from a source PSCell to a target PSCell or a failure which occurs during the PSCell change procedure.
  • the source PSCell is a source PSCell of the latest PSCell change.
  • the target PSCell is a target PSCell of the latest PSCell change.
  • the source SN can further determine whether the failure is caused by the unreasonable configuration of CPC candidate cells or by the unreasonable configuration of CPC execution condition. If the suitable cell is not in the CPC candidate cells configured to the UE, the failure is caused by the unreasonable configuration of CPC candidate cells. If the suitable cell is not in the list of the CPC candidate cells recommended by the source SN that triggers the PSCell change, the problem is caused by the source SN that triggers the PSCell change. If the suitable cell is in the list of the CPC candidate cells recommended by the source SN that triggers the PSCell change, but not in the list of the candidate PSCells selected by the target SN or the candidate target SN, the failure is caused by the target SN or the candidate target SN. For the trigger of the PSCell change to the wrong PSCell, the source SN can further determine whether the failure is caused by the unreasonable configuration of the candidate cell.
  • the present disclosure proposes two approaches for indicating to the target SN or the candidate target SN:
  • the MN transmits indication or report information on the SCG failure to the target SN or the candidate target SN.
  • the message includes one or more information elements in the SCG failure information, and the MN directly includes the one or more information elements into the message to be transmitted to the SN instead of including the RRC container into the message to be transmitted to the SN.
  • the message may also contain other information without affecting the main content of the present disclosure.
  • the MN transmits the indication or report information on the SCG failure to the source SN, and the source SN further determines a type of the failure. If the source SN determines that the problem is caused by the target SN or the candidate target SN, the source SN transmits a message to the MN.
  • the message transmitted by the source SN to the MN includes a MN UE Access Protocol (AP) Identity (ID), a SN UE AP ID, a list of candidate PSCells recommended by the source SN, a list of candidate PSCells selected by the target SN or the candidate target SN, a cell identity of a suitable PSCell, a cell identity of a source PSCell, a cell identity of a target PSCell, a cell identity of a suitable PSCell which is not selected by the target SN or the candidate target SN, and/or indication information that the selected candidate PSCell is unsuitable.
  • Each of candidate PSCells contains a cell identity, which may be a global cell identity.
  • a Tracking Area Code (TAC) can be further included.
  • the source SN can transmit the above information to the MN through a SCG failure transfer message or other message.
  • the MN transmits a message to the target SN or the candidate target SN, and the message includes the same information as those described in the first approach, which will not be repeated here.
  • the source SN can also determine whether the failure is caused by an estimated arrival probability which is set improperly, for example, the estimated arrival probability transmitted by the source SN to the candidate target SN via the MN is set too low, and the suitable cell is in the candidate SNs. In such a case, the source SN is the node that leads to the failure.
  • the PSCell change or CPC is optimized reasonably by the node (the source SN, the target SN or the candidate target SN, or the MN) which leads to the failure.
  • the first method for supporting self-configuration and self-optimization proposed in the present disclosure has been described, and the method can support robustness of PSCell change in the mobility procedure, especially the robustness in the PSCell change between the different RATs, and thus correctly identify the causes of failure, so as to make reasonable optimization, reduce occurrence of a failure, ensure service continuity, and reduce labor cost of an operator.
  • Fig. 4 illustrates a first embodiment of the first method supporting self-configuration and self-optimization according to the present disclosure.
  • the MN is a gNB
  • the source SN is a gNB or an ng-eNB.
  • the method comprises the following steps:
  • a SCG failure occurs.
  • the SCG failure may be a failure when the UE accesses to the target PSCell of the target SN or a failure occurring in the CPC execution to the target PSCell or a failure occurring after a successful PSCell change.
  • the UE stores information related to the failure.
  • the information related to the failure is the information on the secondary cell group failure described at step 301, which will not be repeated here.
  • the UE transmits the SCG failure information to the MN.
  • the SCG failure information may be the SCGFailureInformation or SCGFailureInformationEUTRA. If the PSCell where the failure occurs is an NR cell, the the SCG failure information is the SCGFailureInformation. If the PSCell where the failure occurs is an E-UTRA cell, the SCG failure information is the secondary cell group failure information EUTRA (SCGFailureInformationEUTRA). The information included in the SCG failure information is the same as those described at step 301, which will not be repeated here.
  • the UE may transmit the SCG failure information to the MN through the existing SCG failure information message or other RRC messages.
  • the MN determines which node causes the failure.
  • the determining method used by the MN is the same as that at step 302, and will not be described here repeatedly.
  • the MN can further determine a type of the failure, and the specific determining method is the same as that at step 302, which will not be repeated here.
  • step 404 is performed.
  • the MN transmits SCG failure information report message to the source SN.
  • the MN directly contains the SCG failure information in the SCG failure information report message. If the source SN and the MN support different radio access technologies (such as ng-eNB), the MN puts the information in the SCG failure information into an inter-node message or an inter-node RRC message, and transmits the information in the SCG failure information to the source SN through the inter-node message or the inter-node RRC message; and the MN includes the inter-node message or the inter-node RRC message into the SCG failure information report message, and transmits the inter-node message or the inter-node RRC message to the source SN through the SCG failure information report message.
  • different radio access technologies such as ng-eNB
  • the MN may also include one or more or all of the information contained in the SCG failure information into the SCG failure information report message, respectively.
  • the information contained in the SCG failure information is, for example, a cell identity of the source PSCell, a cell identity of the failed PSCell, a time duration from receiving the RRC reconfiguration message for the PSCell change to the failure, RA information, measurement result of the UE, location information of the UE, a list of CPC candidate cells, and/or CPC execution condition(s), etc.
  • the MN includes the above information into the SCG failure information report message.
  • the SCG failure information report message may or may not contain the SCG failure information container.
  • the message may also include the information transmitted by the MN to the source SN in step 303, which will not be repeated here.
  • the message transmitted by the MN to the source SN may be an existing SCG failure information report or other messages. If the type of the failure is determined by the source SN, the determining method used by the source SN is the same as that described at step 303.
  • the first embodiment of the first method for supporting self-configuration and self-optimization proposed in the present disclosure has been described, which can support robustness of the PSCell change in the mobility procedure, especially the robustness of the PSCell change between the different RATs, and thus correctly identify the causes of the failure, so as to make reasonable optimization, reduce occurrence of a failure, ensure service continuity, and reduce labor cost of an operator.
  • Fig. 5 illustrates a second embodiment of the first method supporting self-configuration and self-optimization according to the present disclosure.
  • the MN is an eNB or an ng-eNB
  • the source SN is a gNB (en-gNB) as the SN in the EN-DC.
  • the MN is an ng-eNB
  • the source SN may be a gNB or an ng-eNB.
  • the method comprises the following steps:
  • a SCG failure occurs.
  • the SCG failure may be a failure when the UE accesses to the target PSCell of the target SN or a failure occurring in the CPC execution to the target PSCell or a failure occurring after the successful PSCell change.
  • the UE stores information related to the failure.
  • the information related to the failure is the information on the secondary cell group failure described at step 301, which will not be repeated here.
  • the UE transmits SCG failure information to the MN.
  • the SCG failure information may be SCGFailureInformation or secondary cell group failure information NR (SCGFailureInformationNR). If the PSCell where the failure occurs is an NR cell, the the SCG failure information is SCGFailureInformationNR. If the PSCell where the failure occurs is an E-UTRA cell, the SCG failure information is SCGFailureInformation.
  • the information included in the SCG failure information is the same as that described at step 301, which will not be repeated here.
  • the UE may transmit the SCG failure information to the MN through the existing SCG failure information message or other RRC messages. The information included in the SCG failure information is the same as that described at step 301, which will not be repeated here.
  • the MN determines which node causes the failure.
  • the determining method used by the MN is the same as that described at step 302, and will not be described here.
  • the MN can further determine a type of failure, and the specific determining method is the same as that at step 302, which will not be repeated here.
  • step 504 is performed.
  • the MN transmits SCG failure information report message to the source SN.
  • the MN directly includes the SCG failure information into the SCG failure information report message. If the source SN and the MN support different radio access technologies (such as gNB or en-gNB), the MN puts the information in the SCG failure information into an inter-node message or an inter-node RRC message, and transmits the information in the SCG failure information to the source SN through the inter-node message or the inter-node RRC message; and the MN includes the inter-node message or the inter-node RRC message into the SCG failure information report message, and transmits the inter-node message or the inter-node RRC message to the source SN through the SCG failure information report message.
  • the source SN and the MN support different radio access technologies (such as gNB or en-gNB)
  • the MN puts the information in the SCG failure information into an inter-node message or an inter-node RRC message, and transmits the information in the SCG failure information to the source SN
  • the MN may also include one or more or all of the information contained in the SCG failure information into the SCG failure information report message, respectively.
  • the information contained in the SCG failure information is, for example, a cell identity of the source PSCell, a cell identity of the failed PSCell, a time duration from receiving the RRC reconfiguration message for the PSCell change to the failure occurrence, RA information, measurement result of the UE, location information of the UE, a list of the CPC candidate cells, and/or CPC execution condition(s), etc.
  • the MN includes the above information into the SCG failure information report message.
  • the SCG failure information report message may or may not contain the SCG failure information container.
  • the message may also include the information transmitted by the MN to the source SN at step 303, which will not be repeated here.
  • the message transmitted by the MN to the source SN may be an existing SCG failure information report or other messages. If the type of the failure is determined by the source SN, the determining method used by the source SN is the same as that described at step 303.
  • the second embodiment of the first method for supporting self-configuration and self-optimization proposed in the present disclosure can support robustness of the PSCell change in the mobility procedure, especially the robustness in the PSCell change between the different RATs, and thus correctly identify the causes of the failure, so as to make reasonable optimization, reduce occurrence of a failure, ensure service continuity, and reduce labor cost of an operator.
  • Fig. 6 illustrates an example of a second method supporting self-configuration and self-optimization according to the present disclosure.
  • the method comprises the following steps:
  • a SCG failure occurs for a UE.
  • the UE stores information on the failure.
  • the UE includes the SCG failure information in the RRC format of the radio access technology of the source PSCell, into the SCG failure information to be transmitted to the MN. If there is no recent PSCell change, the UE includes the SCG failure information (i.e., RRC container) in the RRC format of the radio access technology of the PSCell serving the UE at the time of the failure occurs, into the SCG failure information to be transmitted to the MN.
  • SCG failure information i.e., RRC container
  • the MN is a gNB
  • the SN which controls the PSCell serving the UE is an ng-eNB
  • the SCG failure occurs for the UE, and the UE generates the SCG failure information according to the NR RRC, and herein the SCG failure information is SCGFailureInformationEUTRA.
  • the SCG failure information in the LTE RRC is included in the SCG failure information in the NR RRC.
  • the MN is a gNB, and there is a recent PSCell change; the source SN is an ng-eNB, and the target SN is a gNB; the PSCell change fails or the SCG failure occurs just after a successful PSCell change, the UE generates the SCG failure information according to the NR RRC, and includes the SCG failure information in LTE RRC into the SCG failure information in the NR RRC.
  • the SCG failure information in the NR RRC can be SCGFailureInformation or SCGFailureInformationEUTRA.
  • the UE knows whether there is a recent PSCell change according to the time from configuration of the recent PSCell change to the failure or the time from execution of the recent PSCell change to the failure.
  • the secondary cell group failure information includes one or more of following information:
  • the cell identity may be information on a global cell identity, or a physical cell identity and a frequency.
  • the global cell identity may further include Tracking Area Code (TAC) or a tracking area identity of the cell;
  • TAC Tracking Area Code
  • the cell identity may be information on a global cell identity, or a physical cell identity and a frequency.
  • the global cell identity can also include the Tracking Area Code (TAC) or the tracking area identity of the cell;
  • TAC Tracking Area Code
  • a cell list of CPC candidate PSCells may directly include a list of candidate CPC cells, or indication information on the CPC candidate cells for the cells contained in a measurement result which are the CPC candidate cells, or additionally include information on one or more CPC candidate cells which are the CPC candidate cells but not in the measurement result, in a secondary cell group failure information.
  • Each of the candidate PSCells contains a cell identity, which may be a global cell identity.
  • the global cell identity may further include Tracking Area Code (TAC);
  • the CPC execution condition(s) can be one or more. There are one or more execution conditions for each of the candidate PSCell cells;
  • RA Random Access
  • the above failure is the SCG failure.
  • Both the NR RRC SCG failure information and LTE RRC SCG failure information include the above information.
  • the master node decides which node leads to the failure. For example, it is the master node, the source secondary node, the target secondary node or other candidate secondary node.
  • the master node decides which node leads to the failure according to information in the SCG failure information received from the UE and/or the information stored by the MN.
  • the master node can also determine a type of a failure occurring, such as a too early PSCell change, a too late PSCell change or trigger of a PSCell change to a wrong PSCell cell.
  • the method used by the master node for determining is the same as that in step 302, and the detail is omitted.
  • the MN and the source SN serving the UE are the node that leads to the failure.
  • the MN is the node that leads to the failure. If the PSCell change is triggered by the source SN, the source SN is the node that leads to the failure.
  • the MN is the node that leads to the failure. If the PSCell change is triggered by the source SN, the source SN is the node that leads to the failure.
  • the MN can further determine whether the failure is caused by unreasonable configuration of CPC candidate cells or by unreasonable configuration of CPC execution condition(s).
  • the specific method for determining is the same as that described above, and the detail is omitted.
  • step 604 does not need to be performed. If the problem is caused by the source SN or the last serving SN for the UE, step 604 is performed.
  • the master node transmits the secondary cell group failure indication or report to the secondary node that caused the failure.
  • the MN knows that the failure is caused by the source SN, the last serving SN for the UE, the target SN or the candidate target SN.
  • the MN can transmit the information on the secondary cell group failure to the secondary node that caused the problem through the secondary cell group failure information report message or other messages.
  • the MN and the SN which caused the problem are nodes supporting different Radio Access Technologies (RATs)
  • the MN includes SCG failure information contained in the SCG failure information received from the UE, into an inter-base station interface (such as Xn or X2) message to be transmitted to the SN.
  • an inter-base station interface such as Xn or X2
  • the MN is a gNB
  • the SN which caused the failure is an ng-eNB.
  • the NR RRC SCG failure information received by the MN from the UE includes SCGFailureInformation in the LTE RRC, and the MN transmits the SCGFailureInformation in the LTE RRC to the SN which caused the problem.
  • the MN is an eNB and the source SN is a gNB; the PSCell change fails or the SCG failure occurs just after a successful PSCell change, and the MN transmits the SCGFailureInformation in the NR RRC contained in the LTE RRC SCG failure information received from the UE to the SN that caused the problem.
  • the MN directly includes the secondary cell group failure information (such as SCGFailureInformation or SCGFailureInformationEUTRA or SCGFailureNR) in the radio access technology RRC supported by the MN received from the UE, into the interface message between base stations to be transmitted to the SN, thus resulting in a problem that if the SN and the MN support different radio access technologies, the SN may not be able to read the secondary cell group failure information encoded according to the Radio Resource Control (RRC) of the MN, so that the SN cannot determine the cause of the SCG failure, and accordingly corresponding optimization cannot be made.
  • RRC Radio Resource Control
  • the MN does not directly include the secondary cell group failure information (such as SCGFailureInformation or SCGFailureInformationEUTRA or SCGFailureNR) received from the UE, into the interface message between base stations to be transmitted to the SN, and instead, the MN puts the SCG failure information in the RRC of the radio access technology supported by the secondary base station contained in the secondary cell group failure information of the MN RRC message, into the message between base stations and transmits the same to the SN.
  • the SN can obtain necessary information from the interface message between base stations, so as to detect a type of the failure and make corresponding optimization.
  • the MN when the MN receives the SCG failure information in the NR RRC from the UE, in the prior art, the MN includes the SCG failure information in the NR RRC into the message between base stations to be transmitted to the SN.
  • the MN includes the SCG failure information in LTE RRC format contained in the SCG failure information in NR RRC, into message between base stations to be transmitted to the SN.
  • the source SN, the target SN or the candidate SN determines the type of failure, for example, the too early PSCell change, too late PSCell change, or trigger of the PSCell change to the wrong PSCell, after receiving the message from the MN.
  • the specific method for determining is the same as that in step 303, and will not be described here.
  • the source SN can further determine whether the failure is caused by unreasonable configuration of CPC candidate cells or by unreasonable configuration of CPC execution condition(s). If the suitable cell is not in the CPC candidate cells configured to the UE, the failure is caused by the unreasonable configuration of CPC candidate cells. If the suitable cell is not in the list of the CPC candidate cells recommended by the source SN that triggers the PSCell change, the problem is caused by the source SN that triggers the PSCell change. If the suitable cell is in the list of the CPC candidate cells recommended by the source SN that triggers the PSCell change, but not in the list of the candidate PSCells selected by the target SN or the candidate target SN, the failure is caused by the target SN or the candidate target SN. For the trigger of the PSCell change to the wrong PSCell, the source SN can further determine whether the failure is caused by the unreasonable configuration of the candidate cell.
  • the source SN can also determine whether the failure is caused by an estimated arrival possibility which is set improperly. For example, the estimated arrival probability transmitted by the source SN to the candidate target SN via the MN is set too low, while the suitable cell is in the candidate SNs, and thus the source SN is the node that leads to the failure.
  • the node (source SN, target SN or candidate target SN, or MN) which leads to the failure also make reasonable optimizations for the PSCell change or the CPC.
  • the second method for supporting self-configuration and self-optimization proposed in the present disclosure can support robustness of the PSCell change in the mobility procedure, especially the robustness in the PSCell change between the different RATs, and thus correctly identify the causes of the failure, so as to make reasonable optimization, reduce occurrence of failure, ensure service continuity, and reduce labor cost of an operator.
  • Fig. 7 illustrates a first embodiment of the second method supporting self-configuration and self-optimization according to the present disclosure.
  • the MN is a gNB and the source SN can be an ng-eNB.
  • the method comprises the following steps:
  • a SCG failure occurs.
  • the SCG failure may be a failure of the target PSCell access to the target SN perform by a UE or a failure occurring in the CPC execution to the target PSCell or a failure occurring after a successful PSCell change.
  • the UE stores information related to the failure.
  • the source PSCell for the recent PSCell change and the MN support different radio access technologies, and the MN supports the NR radio access technology and the source SN supports the E-UTRA radio access technology.
  • the UE stores the LTE RRC SCG failure information and NR RRC SCG failure information.
  • the information related to the failure is the information on the secondary cell group failure described in step 301, which is not repeated here.
  • the UE transmits the SCG failure information to the MN.
  • the SCG failure information can be the SCGFailureInformation or SCGFailureInformationEUTRA.
  • the SCG failure information includes the information as described at step 301, and further includes SCGFailureInformation in the format of LTE RRC. Information contained in the SCGFailureInformation in the format of LTE RRC is the same as that described in step 301, which will not be repeated here.
  • the MN determines which node causes the failure.
  • the MN uses the same determining method as that at step 302, which will not be described here.
  • the MN can further determine the type of failure, and the specific determining method is the same as that at step 302, which will not be repeated here.
  • step 704 is performed.
  • the MN transmits SCG failure information report message to the source SN.
  • the message includes the SCGFailureInformation in the LTE RRC.
  • the SCGFailureInformation in the LTE RRC is included in the SCGFailureInformation or SCGFailureInformationEUTRA in the NR RRC received from the UE.
  • the message may also include the information transmitted by the MN to the source SN at step 303, which will not be repeated here.
  • the message transmitted by the MN to the source SN may be an existing SCG failure information report or other messages. If the type of the failure is determined by the source SN, the source SN uses the same determining method as that described at step 303.
  • the first embodiment of the second method for supporting self-configuration and self-optimization proposed in the present disclosure has been described, and such a method can support robustness of the PSCell change in the mobility procedure, especially the robustness in the PSCell change between the different RATs, and thus correctly identify the cause of the failure, so as to make reasonable optimization, reduce occurrence of failure, ensure service continuity, and reduce labor cost of an operators.
  • Fig. 8 illustrates a second embodiment of the second method supporting self-configuration and self-optimization according to the present disclosure.
  • the MN is an eNB or an ng-eNB
  • the source SN is a gNB (en-gNB) as the SN in the EN-DC.
  • the MN is an ng-eNB
  • the source SN can be a gNB.
  • the method comprises the following steps:
  • a SCG failure occurs.
  • the SCG failure may be a failure when the UE accesses to the target PSCell of the target SN or a failure occurring in the CPC execution to the target PSCell or a failure occurring after a successful PSCell change.
  • the UE stores information related to the failure.
  • the information related to the failure is the information on the secondary cell group failure described at step 301, which will not be repeated here.
  • the source PSCell for the recent PSCell change and the MN support different radio access technologies
  • the MN supports the LTE radio access technology
  • the source SN supports the NR radio access technology.
  • the UE stores the LTE RRC SCG failure information and NR RRC SCG failure information.
  • the information related to the failure is the information on the secondary cell group failure described in step 301, which is not repeated here.
  • the UE transmits the SCG failure information to the MN.
  • the SCG failure information may be the secondary cell group failure information (SCGFailureInformation) or the secondary cell group failure information NR (SCGFailureInformationNR). If the PSCell where the failure occurs is an NR cell, the SCG failure information is the SCGFailureInformationNR. If the PSCell where the failure occurs is an E-UTRA cell, the SCG failure information is the SCGFailureInformation.
  • the SCG failure information includes the information as described at step 301, and further includes the SCGFailureInformation in the format of NR RRC. The information contained in the SCGFailureInformation in the format of NR RRC is the same as that described in step 301, which will not be repeated here
  • the UE may transmit the SCG failure information to the MN through an existing SCG failure information message or other RRC messages.
  • the MN determines which node causes the failure.
  • the MN uses the same determining method as that at step 302, which will not be described here.
  • the MN can further determine a type of failure, and the specific decision method is the same as that at step 302, which will not be repeated here.
  • step 804 is performed.
  • the MN transmits SCG failure information report message to the source SN.
  • the message includes the SCGFailureInformation in the NR RRC.
  • the SCGFailureInformation in the NR RRC is included in the SCGFailureInformation or the SCGFailureInformationNR in the LTE RRC received from the UE.
  • the message may also include the information transmitted by the MN to the source SN at step 303, which will not be repeated here.
  • the message transmitted by the MN to the source SN may be an existing SCG failure information report or other messages. If the type of the failure is determined by the source SN, the source SN uses the same determining method as that described at step 303.
  • the second embodiment of the second method for supporting self-configuration and self-optimization proposed in the present disclosure can support robustness of the PSCell change in the mobility procedure, especially the robustness in the PSCell change between the different RATs, and thus correctly identify the cause of the failure, so as to make reasonable optimization, reduce occurrence of the failure, ensure service continuity, and reduce labor cost of an operator.
  • the method of the disclosure can support the robustness of the PSCell change in the mobility procedure, especially the robustness of the PSCell change between different RATs, and thus correctly identify the causes of the failure, so as to make reasonable optimization, reduce the occurrence of failure, ensure service continuity, and reduce the labor cost of operators.
  • Fig. 9 is a block diagram of a network node in a network according to the present disclosure.
  • the network node in the network can be used to implement the MN, the SN, the S-SN, the T-SN, other candidate T-SNs, etc. in the present disclosure.
  • the network node according to the present disclosure includes a transceiver 910, a controller 920 and a memory 930.
  • the transceiver 910, the controller 920 and the memory 930 are configured to perform operations of the methods and/or embodiments of the present disclosure.
  • the transceiver 910, the controller 920 and the memory 930 are illustrated as separate entities, they can be implemented as a single entity, such as a single chip.
  • the transceiver 910, the controller 920 and the memory 930 may be electrically connected or coupled to each other.
  • Transceiver 910 can transmit signals to other network nodes and receive signals from other network entities, such as UE, MN, SN, S-SN, T-SN, other candidate T-SNs or core network nodes.
  • the controller 920 may include one or more processing units, and may control network nodes to perform operations and/or functions according to one of the above embodiments.
  • the memory 930 may store instructions for implementing the operations and/or functions of one of the above embodiments.
  • the various illustrative logic blocks, modules, and circuits described in the present application can be implemented with a general purpose processor, a Digital Signal Processor (DSP), an application specific integrated circuit (ASIC), a Field Programmable Gate Array (FPGA) or other programmable logic devices, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein.
  • the general-purpose processor may be a microprocessor, but in an alternative, the processor may be any conventional processor, controller, microcontroller, or state machine.
  • the processor can also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors cooperating with a DSP core, or any other such configuration.
  • the steps of the method or algorithm described in the present application can be directly embodied in hardware, in a software module executed by a processor, or in a combination of the two.
  • the software modules may reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disks, removable disks, or any other form of storage media known in the art.
  • An exemplary storage medium is coupled to the processor so that the processor can read and write information from/to the storage medium.
  • the storage medium may be integrated into the processor.
  • the processor and the storage medium may reside in the ASIC.
  • the ASIC may reside in the user terminal.
  • the processor and the storage medium may reside as discrete components in the user terminal.
  • the functions can be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, each function can be stored on or transferred by a computer-readable medium as one or more instructions or codes.
  • Computer readable media include both computer storage media and communication media, the latter including any media that facilitates the transfer of computer programs from one place to another. Storage media can be any available media that can be accessed by general-purpose or special-purpose computers.

Landscapes

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

Abstract

La divulgation se rapporte à un système de communication 5G ou 6G destiné à prendre en charge un plus haut débit de transmission de données. La divulgation concerne un procédé et un appareil pour la prise en charge d'une auto-configuration et d'une auto-optimisation. Le procédé mis en œuvre par un premier nœud de réseau d'un système de communication consiste à recevoir des informations relatives à une défaillance de groupe de cellules secondaires (SCG) en provenance d'un équipement utilisateur (UE) ; et à transmettre des premières informations de rapport de défaillance à un second nœud de réseau.
PCT/KR2023/010932 2022-07-28 2023-07-27 Procédé et appareil pour la prise en charge d'une auto-configuration et d'une auto-optimisation WO2024025362A1 (fr)

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
CN202210901827.4 2022-07-28
CN202210901827 2022-07-28
CN202211236864.4A CN117528678A (zh) 2022-07-28 2022-10-10 支持自配置自优化的方法和装置
CN202211236864.4 2022-10-10

Publications (1)

Publication Number Publication Date
WO2024025362A1 true WO2024025362A1 (fr) 2024-02-01

Family

ID=89707006

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/KR2023/010932 WO2024025362A1 (fr) 2022-07-28 2023-07-27 Procédé et appareil pour la prise en charge d'une auto-configuration et d'une auto-optimisation

Country Status (1)

Country Link
WO (1) WO2024025362A1 (fr)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2019137161A1 (fr) * 2018-01-09 2019-07-18 电信科学技术研究院有限公司 Procédé et dispositif de traitement d'une défaillance de scg
US20210153281A1 (en) * 2017-05-04 2021-05-20 Samsung Electronics Co., Ltd Methods and systems for reporting a secondary node failure in dual connectivity networks
WO2021150014A1 (fr) * 2020-01-23 2021-07-29 Samsung Electronics Co., Ltd. Procédé et dispositif d'auto-optimisation
US20210377755A1 (en) * 2017-12-27 2021-12-02 JRD Communication (Shenzhen) Ltd. Communication method for scenario with secondary cell group failure
US20220225457A1 (en) * 2021-01-11 2022-07-14 Qualcomm Incorporated User equipment communications while operating in a secondary cell group deactivated state

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20210153281A1 (en) * 2017-05-04 2021-05-20 Samsung Electronics Co., Ltd Methods and systems for reporting a secondary node failure in dual connectivity networks
US20210377755A1 (en) * 2017-12-27 2021-12-02 JRD Communication (Shenzhen) Ltd. Communication method for scenario with secondary cell group failure
WO2019137161A1 (fr) * 2018-01-09 2019-07-18 电信科学技术研究院有限公司 Procédé et dispositif de traitement d'une défaillance de scg
WO2021150014A1 (fr) * 2020-01-23 2021-07-29 Samsung Electronics Co., Ltd. Procédé et dispositif d'auto-optimisation
US20220225457A1 (en) * 2021-01-11 2022-07-14 Qualcomm Incorporated User equipment communications while operating in a secondary cell group deactivated state

Similar Documents

Publication Publication Date Title
WO2022216087A1 (fr) Procédés et systèmes de gestion de contrôle d'admission de tranche de réseau pour un équipement d'utilisateur
WO2023146310A1 (fr) Procédé et appareil pour la prise en charge de changement de tranche de réseau dans un système de communication sans fil
WO2022225315A1 (fr) Procédé et dispositif de notification d'état de mbs
WO2022240153A1 (fr) Procédé et appareil de commande d'une session pdu
WO2022173256A1 (fr) Procédé et appareil pour gérer l'enregistrement d'un équipement utilisateur à un service d'itinérance en cas de catastrophe dans un système de communication sans fil
WO2023191478A1 (fr) Procédé et dispositif de support de mouvement de véhicule aérien sans pilote
WO2024025362A1 (fr) Procédé et appareil pour la prise en charge d'une auto-configuration et d'une auto-optimisation
WO2022086170A1 (fr) Station de base prenant en charge une auto-configuration et une auto-optimisation et son procédé
WO2024177439A1 (fr) Procédé et appareil prenant en charge une auto-configuration et une auto-optimisation
WO2023211089A1 (fr) Procédé et appareil de transfert intercellulaire
WO2024029892A1 (fr) Procédé et appareil pour prendre en charge une auto-configuration et une auto-optimisation
WO2023249383A1 (fr) Procédé et nœud de configuration dans un système de communication prenant en charge un accès et une liaison terrestre intégrés (iab)
WO2023234664A1 (fr) Station de base et procédé pour prendre en charge une auto-configuration et une auto-optimisation
WO2023140701A1 (fr) Procédé exécuté par un nœud de communication et nœud de communication dans un système de communication
WO2024096502A1 (fr) Procédé et dispositif de prise en charge d'une transmission de service de multidiffusion
WO2024172542A1 (fr) Noeuds et procédés exécutés par des noeuds
WO2024172490A1 (fr) Procédé et appareil pour notifier un changement de tranche de réseau dans un système de communication sans fil
WO2024172540A1 (fr) Procédé et dispositif pour prendre en charge une transmission de service de diffusion de groupe
WO2024014787A1 (fr) Procédé et appareil pour effectuer un transfert intercellulaire conditionnel dans un système de communication sans fil
WO2024101949A1 (fr) Connexion de nœud répéteur à un réseau
WO2024091073A1 (fr) Procédés et appareil de gestion de cellules primaires réussies et rapport de réussite de pscell (spr) dans un réseau sans fil
WO2024172456A1 (fr) Procédé et dispositif pour prendre en charge une auto-configuration et une auto-optimisation
WO2024096417A1 (fr) Procédé de mise à jour de zone de suivi et dispositif de communication sans fil
WO2024072135A1 (fr) Procédés de gestion de données ciot pour un id de session pdu invalide
WO2024172591A1 (fr) Procédé et appareil de configuration et de signalisation de multiples événements de déclenchement de rapport de mesure dans un système de communication

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

Country of ref document: EP

Kind code of ref document: A1