Method and device for supporting self-configuration and self-optimization

Abstract

The present disclosure provides a method and apparatus for supporting self-configuration and self-optimization, including a method executed by a first network node of a communication system, comprising: receiving first information including failure related information from a user equipment (UE), the failure related to a secondary cell group (SCG); and determining a network node which causes a failure at least based on the failure-related information, the failure-related information comprising at least one of the following information: information related to increasing or changing S-CPAC by a subsequent conditional primary and secondary cell PSCell, cell identification information related to the PSCell, and information related to an SCG and / or a primary cell group MCG.

Description

TECHNICAL FIELD

[0001] The present application relates to the wireless communication technology, and particularly relates to a method and device supporting self-configuration and self-optimization. BACKGROUND

[0002] To meet the demand for wireless data traffic having increased since deployment of 4G communication systems, efforts have been made to develop an improved 5G or pre-5G communication system. Therefore, the 5G or pre-5G communication system is also called a 'Beyond 4G Network' or a '5G Network'.

[0003] Wireless communication is one of the most successful innovations in modern history. Recently, the number of subscribers to wireless communication services has exceeded 5 billion and is continuing to rapidly grow. As smart phones and other mobile data devices (e.g., tablet computers, notebook computers, netbooks, e-book readers, and machine-type devices) are increasingly popular among consumers and enterprises, demand for wireless data traffic is rapidly growing. In order to meet the high-speed growth of mobile data traffic and support new applications and deployments, it is essential to improve the efficiency and coverage of the wireless interface. SUMMARY

[0004] For enhanced mobile schemes, how to support mobile robustness in dual connectivity procedure is a problem to be solved.

[0005] According to an aspect of the present disclosure, a method performed by a first network node of a communication system includes receiving, from a user equipment (UE), first information including failure related information, the failure being related to a secondary cell group (SCG); and determining, based at least on the failure related information, a network node that caused the failure, wherein the failure related information includes at least one of: information related to a subsequent conditional primary secondary cell (PSCell) addition or change (S-CPAC), cell identification information related to a PSCell, and information related to a SCG and / or a master cell group (MCG).

[0006] According to an embodiment of the present disclosure, the method further includes transmitting, to the node that caused the failure or a second node, an indication or report information of the failure.

[0007] According to an embodiment of the present disclosure, the method further includes determining a type of the failure based on at least part of the failure related information.

[0008] According to an embodiment of the present disclosure, the method further includes forwarding, to the node that caused the failure, the failure related information.

[0009] According to an embodiment of the disclosure, wherein the subsequent conditional primary secondary cell (PSCell) addition or change S-CPAC related information includes at least one of the following: indication information of whether S-CPAC is performed, time from S-CPAC execution to failure, S-CPAC execution condition, time from receiving S-CPAC configuration from UE to failure, time from receiving S-CPAC configuration from UE to S-CPAC execution, indication information of S-CPAC execution condition meeting execution, information of which S-CPAC execution condition is met first, time between meeting two S-CPAC execution conditions, indication information of S-CPAC, initial S-CPAC execution condition, subsequent S-CPAC execution condition, indication information of initial S-CPAC failure or subsequent S-CPAC failure; or wherein the PSCell related cell identification information includes at least one of the following: failed PSCell cell identification, source PSCell cell identification of the last PSCell change, cell list of S-CPAC candidate PSCell; or wherein the SCG and / or MCG related information includes at least one of the following: state of SCG, SCG failure time, state of MCG.

[0010] According to an embodiment of the disclosure, wherein the failure indication or report information includes at least one of the following: source PSCell cell identification, destination PSCell cell identification or failed PSCell cell identification, suitable PSCell cell identification, SCG failure information received from UE, candidate PSCell list recommended by MN or source SN, initial S-CPAC execution condition, subsequent S-CPAC execution condition, candidate PSCell list selected by destination SN or candidate destination SN, PSCell list not accepted by destination SN or candidate destination SN from the candidate PSCell list recommended by MN or source SN, maximum number of prepared PSCells, estimated arrival probability, SCG failure time, type of failure.

[0011] According to another aspect of the present disclosure, a method performed by a first network node of a communication system is provided, comprising: transmitting, to a user equipment (UE), at least one of first configuration information, second configuration information, third configuration information, and fourth configuration information for a successful primary secondary cell (PSCell) change report; receiving, from the UE, information indicating that the successful PSCell change report is available, wherein the successful PSCell change report comprises one or more of: time information related to the successful PSCell change report, identification information related to a primary cell, a source PSCell, and a target PSCell related to the PSCell change, a cause of the successful PSCell change, information related to a clock configured by the first node, time information related to the PSCell change, movement information of the UE, and information of a node that initiated the PSCell change.

[0012] According to an embodiment of the present disclosure, the method further comprises: transmitting, to the first node, a request for the successful PSCell change report; and receiving, from the UE, the successful PSCell change report.

[0013] According to an embodiment of the present disclosure, the method further comprises: receiving, from a second node, the first configuration information for the successful PSCell change report.

[0014] According to an embodiment of the present disclosure, the method further comprises: receiving, from a third node, the third configuration information and / or the fourth configuration information for the successful PSCell change report.

[0015] According to an embodiment of the present disclosure, the method further comprises: transmitting, to a fifth node, information related to the successful PSCell change report, wherein the fifth node is determined based on the successful PSCell change report.

[0016] According to an embodiment of the present disclosure, wherein the first configuration information comprises at least one of a clock T310 and / or T312 triggered successful PSCell change report configuration and a clock T304 triggered successful PSCell change report configuration; or wherein the second configuration information comprises a clock T310 and / or T312 triggered successful PSCell change report configuration, or wherein the third configuration information comprises a clock T310 and / or a clock T312 triggered successful PSCell change report configuration, or wherein the fourth configuration information comprises a clock T304 triggered successful PSCell change report configuration.

[0017] According to another aspect of the present disclosure, a method performed by a first network node of a communication system is provided, comprising: receiving, from a user equipment (UE), a message including information about a primary secondary cell (PSCell) selected by the UE, and transmitting, to a target secondary node, a message including secondary cell group (SCG) history information of the UE, wherein the SCG history information of the UE includes information of PSCells arranged in a time sequence.

[0018] According to an embodiment of the present disclosure, wherein the SCG history information of the UE is transmitted through a secondary node reconfiguration complete message, and wherein the information of PSCells includes at least one of: identification information of the PSCells, residence time information of the UE, cell type information.

[0019] According to an embodiment of the present disclosure, wherein the SCG history information of the UE is used to detect whether there is a problem with PSCell change.

[0020] According to another aspect of the present disclosure, a method performed by a user equipment (UE) of a communication system is provided, comprising: the UE storing failure related information, the failure being related to a secondary cell group (SCG), and transmitting, to a first network node, first information including the failure related information, wherein the failure related information includes at least one of: information related to a subsequent conditional primary secondary cell (PSCell) addition or change (S-CPAC), cell identification information related to the PSCell, information related to the SCG and / or a master cell group (MCG).

[0021] According to an embodiment of the present disclosure, wherein the information related to the subsequent conditional primary secondary cell (PSCell) addition or change (S-CPAC) includes at least one of: indication information of whether the S-CPAC is performed, time from S-CPAC execution to failure, S-CPAC execution condition, time from receiving S-CPAC configuration from the UE to failure, time from receiving S-CPAC configuration from the UE to S-CPAC execution, indication information of S-CPAC execution condition being satisfied for execution, information of which S-CPAC execution condition is satisfied first, time between satisfaction of two S-CPAC execution conditions, indication information of S-CPAC, initial S-CPAC execution condition, subsequent S-CPAC execution condition, indication information of initial S-CPAC failure or subsequent S-CPAC failure; or wherein the cell identification information related to the PSCell includes at least one of: PSCell cell identification of the failure, source PSCell cell identification of the last PSCell change, cell list of S-CPAC candidate PSCell; or wherein the information related to the SCG and / or the MCG includes at least one of: status of the SCG, SCG failure time, status of the MCG.

[0022] According to an embodiment of the present disclosure, wherein the indication or report information of the failure is sent to the node or the second node which brings the failure, wherein the indication or report information of the failure comprises at least one of the following: source PSCell cell identity, destination PSCell cell identity or failed PSCell cell identity, suitable PSCell cell identity, SCG failure information received from the UE, candidate PSCell list recommended by the MN or source SN, initial S-CPAC execution condition, subsequent S-CPAC execution condition, candidate PSCell list selected by the destination SN or candidate destination SN, PSCell list not accepted by the destination SN or candidate destination SN in the candidate PSCell list recommended by the MN or source SN, maximum number of prepared PSCells, estimated arrival probability, SCG failure time, type of failure.

[0023] According to another aspect of the present disclosure, a method performed by a user equipment (UE) of a communication system is provided, comprising: receiving, from a first network node, at least one of first configuration information, second configuration information, third configuration information and fourth configuration information of a successful primary secondary cell (PSCell) change report; and sending, to the first network node, information indicating that the successful PSCell change report is available, wherein the successful PSCell change report comprises one or more of: time information related to the successful PSCell change report, identification information related to a primary cell, a source PSCell and a destination PSCell related to the PSCell change, a cause of the successful PSCell change, clock related information configured by the first node, time information related to the PSCell change, movement information of the UE, and information of a node initiating the PSCell change.

[0024] According to an embodiment of the present disclosure, wherein the first configuration information comprises at least one of a clock T310 and / or T312 triggered successful primary secondary cell change report configuration and a clock T304 triggered successful primary secondary cell change report configuration; or wherein the second configuration information comprises a clock T310 and / or T312 triggered successful primary secondary cell change report configuration, or wherein the third configuration information comprises a clock T310 and / or a clock T312 triggered successful primary secondary cell change report configuration, or wherein the fourth configuration information comprises a clock T304 triggered successful primary secondary cell change report configuration.

[0025] According to another aspect of the present disclosure, a method performed by a user equipment, UE, of a communication system is provided, comprising: selecting a target primary secondary cell, PSCell; sending, to a first network node, a message comprising information about the target PSCell selected by the UE, wherein in response to the information about the PSCell selected by the UE, secondary cell group, SCG, history information of the UE is sent to a target secondary node, wherein the SCG history information of the UE comprises information of PSCells arranged in a time sequence.

[0026] According to an embodiment of the present disclosure, wherein the SCG history information of the UE is sent through a secondary node reconfiguration complete message, and wherein the information of PSCells comprises at least one of the following: identification information of the PSCell, residence time information of the UE, cell type information.

[0027] According to an embodiment of the present disclosure, wherein the SCG history information of the UE is used to detect whether there is a problem in PSCell change.

[0028] According to another aspect of the present disclosure, a first network node device in a communication system is provided, comprising: a transceiver configured to receive and send signals; and a processor coupled to the transceiver and configured to control the network node device to perform the method according to the embodiments of the present disclosure.

[0029] According to another aspect of the present disclosure, a user equipment, UE, in a communication system is provided, comprising: a transceiver configured to receive and send signals; and a processor coupled to the transceiver and configured to control the UE device to perform the method according to the embodiments of the present disclosure.

[0030] By the method for supporting self-configuration and self-optimization of the present disclosure, in the case of dual connectivity, problems in the process of handover or PSCell change can be correctly identified, including failure, potential failure in the process of success, or unnecessary handover or PSCell change process (such as ping-pong handover or PSCell change), so as to perform reasonable optimization, reduce the occurrence of subsequent failures, ensure service continuity, and reduce the labor cost of operators. BRIEF DESCRIPTION OF DRAWINGS

[0031] Figure 1 a system architecture diagram for system architecture evolution (SAE);

[0032] Figure 2 an initial overall architecture schematic diagram for 5G;

[0033] Figure 3 an example flowchart of the method for supporting self-configuration and self-optimization according to the present disclosure;

[0034] Figure 4 Example flow chart for method two to support self-configuration and self-optimization according to the present application;

[0035] Figure 5 Example flow chart for method three to support self-configuration and self-optimization according to the present application;

[0036] Figure 6 Example signal flow chart for embodiment one of method one to support self-configuration and self-optimization according to the present application;

[0037] Figure 7 Example signal flow chart for embodiment two of method one to support self-configuration and self-optimization according to the present application;

[0038] Figure 8 Example signal flow chart for embodiment three of method two to support self-configuration and self-optimization according to the present application;

[0039] Figure 9 Example signal flow chart for embodiment four of method three to support self-configuration and self-optimization according to the present application;

[0040] Figure 10 Example flow chart for method four to support self-configuration and self-optimization;

[0041] Figure 11 Example signal flow chart for embodiment one of method four to support self-configuration and self-optimization according to the present application;

[0042] Figure 12 Example flow chart for method five to support self-configuration and self-optimization;

[0043] Figure 13 Example flow chart for method six to support self-configuration and self-optimization;

[0044] Figure 14 Example flow chart for method seven to support self-configuration and self-optimization;

[0045] Figure 15 Example flow chart for method eight to support self-configuration and self-optimization;

[0046] Figure 16 Block diagram of a network node according to embodiments of the present application;

[0047] Figure 17 Block diagram of a user equipment, UE, according to embodiments of the present application. DETAILED DESCRIPTION

[0048] To make the purposes, technical solutions, and advantages of the embodiments of the present disclosure clearer, the technical solutions of the embodiments of the present disclosure will be described clearly and completely below with reference to the drawings of the embodiments of the present disclosure. Obviously, the described embodiments are only some of the embodiments of the present disclosure, but not all the embodiments of the present disclosure. Based on the described embodiments of the present disclosure, all other embodiments obtained by a person of ordinary skill in the art without creative effort belong to the scope of protection of the present disclosure.

[0049] Before undertaking a description of the specific embodiments in the following detailed description, it can be advantageous to set forth definitions of certain words and phrases that have been used throughout this patent document. The term “coupled” and variations thereof, means any direct or indirect communication between two or more elements, regardless of the type of physical connection or physical contact between them. The terms “send,” “receive,” and “communicate,” and variations thereof, encompass both direct and indirect communication. The terms “include” and “comprise,” and variations thereof, mean “including but not limited to.” The term “or” is inclusive, meaning and / or. The phrase “associated with,” and variations thereof, means includes, is included in, connected to, is part of, contains, contains in, connected to or with, coupled to or with, is communicable with, cooperates with, interlaced with, is in proximity to, is bound to or with, has, has properties, has relationships, or has relations with, and the like. The term “controller” means any device, system or part thereof that controls at least one operation. Such a controller can be implemented in hardware or in a combination of hardware and software and / or firmware. The functionality associated with any particular controller can be centralized or distributed, local or remote, in association with the same or different controller. The phrase “at least one of” when used with a list of items means that a combination of one or more of the listed items can be used and that only one item from the list can be needed. For example, “at least one of A, B, and C” includes: A, B, C, A and B, A and C, B and C, and A and B and C. For example, “at least one of A, B, or C” includes: A, B, C, A and B, A and C, B and C, and A and B and C.

[0050] Moreover, 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. The terms "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, that are implemented in a suitable computer readable program code. The phrase "computer readable program code" includes any type of computer code, including source code, object code, and executable code. The phrase "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. A "non-transitory" computer readable medium excludes wired, wireless, optical, or other communication links. Non-transitory computer readable media include media that can be permanently stored and media that can be stored and re-writable, such as a rewritable optical disc or an erasable memory device.

[0051] The terminology used herein for the purpose of describing embodiments of the present application is not intended to be limiting and / or all inclusive. For example, unless otherwise defined, technical and scientific terms used in the present disclosure shall have the meaning commonly understood by one of ordinary skill in the art to which this present application pertains.

[0052] It should be understood that the use of "first", "second", and like terms in the present disclosure are not intended to denote any order, quantity, or importance, but are used to distinguish one element from another, and that the singular forms "a," "an," and "the" include plural referents unless the context clearly dictates otherwise.

[0053] As used herein, any reference to "one example" or "an example," "one embodiment" or "an embodiment" means that a particular element, structure, or characteristic described in connection with the example is included in at least one embodiment. The appearances of the phrase "in one embodiment" or "in one example" in various places in the specification are not necessarily all referring to the same embodiment.

[0054] As used herein, a "portion" of something means "at least some" of that thing, and thus can mean less than all of that thing or all of that thing. Thus, a "portion" of a thing includes the whole thing as a special case, i.e., the whole thing is an example of a portion of the thing.

[0055] It will be further understood that the terms "comprises" and / or "comprising," or like terms, as used herein, refer to the elements listed after such terms and / or figures, including equivalents thereof, and not to the exclusion of other elements. The terms "connected" and / or "coupled" and / or like terms as used herein, refer not only to direct connection and / or coupling, but also to indirect connections and / or couplings between two or more elements, and / or any combination thereof. The terms "upper," "lower," "left," "right," and the like as used herein are used for description only and are not to be construed as limiting the scope of the disclosure in any way.

[0056] The various embodiments discussed below for describing the principles of the present disclosure in this patent document are by way of illustration only and should not be construed in any way to limit the scope of the present disclosure. Those skilled in the art will understand that the principles of the present disclosure can be implemented in any suitably arranged wireless communication system. For example, although the detailed description of the embodiments of the present disclosure below will be directed to LTE and 5G communication systems, those skilled in the art will understand that the main points of the present disclosure can also be applied to other communication systems with similar technical backgrounds and channel formats with slight modifications without substantially departing from the scope of the present disclosure. The technical solutions of the embodiments of the present application can be applied to various communication systems, for example, the communication system can include a global system for mobile communications (GSM) system, a code division multiple access (CDMA) system, a wideband code division multiple access (WCDMA) system, a general packet radio service (GPRS), a long term evolution (LTE) system, an LTE frequency division duplex (FDD) system, an LTE time division duplex (TDD), a universal mobile telecommunications system

[0057] The communication system can be a 3rd Generation Partnership Project Long Term Evolution (3GPP LTE) system, a 5th Generation (5G) system, a New Radio (NR) system, a Global System for Mobile Communications (GSM) system, a Code Division Multiple Access (CDMA) system, a Wideband CDMA (WCDMA) system, a Long Term Evolution (LTE) system, a 5th Generation (5G) system, a New Radio (NR) system, a worldwide interoperability for microwave access (WiMAX) system, etc. In addition, the technical solutions of the embodiments of the present application can be applied to future-oriented communication technologies. In addition, the technical solutions of the embodiments of the present application can be applied to future-oriented communication technologies.

[0058] The following description of the reference drawings is provided to assist in understanding various embodiments of the present disclosure defined by the claims and their equivalents. The description includes various specific details to assist in understanding the various embodiments but these are to be regarded as merely exemplary. Accordingly, those skilled in the art will recognize that various changes and modifications of the various embodiments described herein can be made without departing from the scope and spirit of the present disclosure. In addition, descriptions of well-known functions and constructions can be omitted for clarity and conciseness.

[0059] The terms and phrases used in the following specification and claims are not limited to the dictionary meanings, but are only used to enable a clear and consistent understanding of the present disclosure. Accordingly, it should be apparent to those skilled in the art that the description of the various embodiments of the present disclosure provided below is only for illustrative purposes and is not intended to limit the scope of the present disclosure as defined by the appended claims and their equivalents.

[0060] It should be understood that the singular forms "a," "an," and "the" include plural referents unless the context clearly dictates otherwise. Thus, for example, reference to "a component surface" includes reference to one or more of such surfaces.

[0061] The terms "comprise" or "may comprise" refer to the existence of the corresponding disclosed function, operation, or component in the various embodiments of the present disclosure, and are not limited to the existence of one or more additional functions, operations, or features. In addition, the terms "comprise" or "have" can be interpreted to mean certain characteristics, numbers, steps, operations, constituent elements, components, or combinations thereof, but should not be interpreted to exclude the possibility of the existence of one or more other characteristics, numbers, steps, operations, constituent elements, components, or combinations thereof.

[0062] The term "or" used in the various embodiments of the present disclosure includes any listed term and all combinations thereof. For example, "A or B" can include A, can include B, or can include both A and B.

[0063] Unless otherwise defined, all terms (including technical or scientific terms) used in this disclosure have the same meaning as understood by those skilled in the art described in this disclosure. Common terms as defined in dictionaries are interpreted as having a meaning consistent with the context in the relevant technical field and should not be interpreted in an idealized or overly formal manner unless explicitly defined in this disclosure.

[0064] The following discussion Figures 1 to 13 The various embodiments used to describe the principles of the present disclosure in this patent document are for illustration only and should not be interpreted in any way as limiting the scope of the present disclosure. Those skilled in the art will understand that the principles of the present disclosure can be implemented in any suitably arranged system or device.

[0065] Figure 1 This is an exemplary system architecture 100 of System Architecture Evolution (SAE). User Equipment (UE) 101 is a terminal device used to receive data. Evolved Universal Terrestrial Radio Access Network (E-UTRAN) 102 is a radio access network, which includes a macro base station (eNodeB / NodeB) that provides the UE with an access wireless network interface. The Mobility Management Entity (MME) 103 is responsible for managing the UE's mobility context, session context and security information. The Serving Gateway (SGW) 104 mainly provides user plane functions, and the MME 103 and SGW 104 may be in the same physical entity. The Packet Data Network Gateway (PGW) 105 is responsible for functions such as billing and lawful interception, and may also be in the same physical entity as the SGW 104. The Policy and Charging Rules Function (PCRF) 106 provides Quality of Service (QoS) policies and charging criteria. The General Packet Radio Service Support Node (SGSN) 108 is a network node device that provides routing for data transmission in the Universal Mobile Telecommunications System (UMTS). The Home Subscriber Server (HSS) 109 is the home subsystem of the UE and is responsible for protecting user information including the current location of the user equipment, the address of the serving node, user security information, and the packet data context of the user equipment.

[0066] Figure 2 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.

[0067] A user equipment (UE) 201 is a terminal device to receive data. A next generation radio access network (NG-RAN) 202 is a radio access network including a base station (gNB or eNB connected to a 5G core network 5GC, eNB connected to 5GC is also called ng-gNB) that provides a radio network interface for the UE to access the wireless network. An access and mobility management function entity (AMF) 203 is responsible for managing the mobility context of the UE, and security information. A user plane function entity (UPF) 204 mainly provides the function of the user plane. A session management function entity SMF 205 is responsible for session management. A data network (DN) 206 includes, for example, operator services, access to the Internet, and third party services.

[0068] Exemplary embodiments of the present disclosure are further described below with reference to the accompanying drawings.

[0069] The text and drawings are provided only as examples to assist in understanding the present disclosure. They should not be construed as limiting the scope of the present disclosure in any way. Although certain embodiments and examples have been provided, it will be apparent to those skilled in the art based on the disclosure provided herein that modifications can be made to the embodiments and examples shown without departing from the scope of the present disclosure.

[0070] In order to improve the reliability of primary secondary cell (PSCell, SpCell of a secondary cell group (primary or secondary cell group, primary cell of a master or secondary cell group), SpCell of a secondary cell group) addition or change, conditional PSCell change (CPC, Conditional PSCell Change) is defined in the current technology. Moreover, conditional PSCell addition (CPA, Conditional PSCell Addition) and conditional PSCell addition or change (CPAC, Conditional PSCell Addition or Change) are defined in the current technology. Among them, CPC can be intra-secondary node (SN, Secondary Node) or inter-SN. In the current technology, a subsequent conditional PSCell addition or change (Subsequent Conditional PSCell Addition or Change, also referred to as Subsequent CPAC or S-CPAC) procedure is further defined. In S-CPAC, when the network configures the UE with S-CPAC, the UE performs the first CPA or CPC (CPA / CPC) (in S-CPAC, it can also be referred to as performing the initial S-CPAC), after completing the addition or change of PSCell, the UE retains the S-CPAC configuration for performing the following (or next) S-CPAC (following Subsequent CPAC / S-CPAC). The execution condition configured for the initial S-CPAC execution can be referred to as the initial S-CPAC execution condition, and the execution condition configured for the following (or next) S-CPAC execution can be referred to as the following (or next) S-CPAC execution condition.

[0071] According to embodiments of the present application, unreasonable configuration or triggering of S-CPAC can cause SCG failure or potential failure in the S-CPAC procedure. According to embodiments of the present application, unreasonable configuration or triggering of PSCell change can cause PSCell change ping-pong in the PSCell procedure. The PSCell change includes general PSCell change, conditional handover with SCG, CPAC, S-CPAC, etc.

[0072] According to embodiments of the present application, under dual connectivity, the master node can also be referred to as a master base station, and the secondary node can also be referred to as a secondary base station.

[0073] As understood by a person skilled in the art, the "timer" described in the present disclosure can also be referred to as a timer or a clock, and these terms are used interchangeably in the present disclosure.

[0074] As understood by a person skilled in the art, in the present disclosure, conditional PSCell change (CPC) and conditional PSCell addition (CPA), or subsequent conditional PSCell addition or change (S-CPAC) can also be considered as a handover or change of a cell.

[0075] Note that in this document, "base station" and "node" are used interchangeably unless explicitly indicated otherwise, for example, a master node can also be referred to as a master base station, a secondary node can also be referred to as a secondary base station, a source node can also be referred to as a source base station, a destination node can also be referred to as a destination base station, a candidate node can also be referred to as a candidate base station, and other nodes can also be referred to as other base stations, and so on, without being limited to one by one. In addition, the base station or node can also be a central unit (CU) in the base station, and can also be a central unit control plane (CU-CP) in the base station. The node can also be other functional entities in the radio access network (RAN), which are not limited by the present application.

[0076] An example of the method of self-configuration and self-optimization supported by the present application is shown in Figure 3 The method includes the steps of:

[0077] Step 301: The UE occurs a failure, and saves the failure related information.

[0078] The failure can be one or more of S-CPAC execution failure, SCG failure after S-CPAC execution, and radio link failure (RLF) after S-CPAC execution, but the present application is not limited thereto, and can also be other types of failures occurring in the secondary cell. The failure related information includes secondary cell group failure information (SCG failure information).

[0079] Step 302: The UE sends the failure related information to the master node. The failure related information includes the secondary cell group failure information.

[0080] The secondary cell group failure information includes one or more of the following information elements:

[0081] - Indicating information of whether a subsequent CPAC (S-CPAC) is executed;

[0082] - Time from the execution of the subsequent CPAC to the failure;

[0083] - failed PSCell cell identity. The cell identity can be global cell identity, or physical cell identity and frequency information. The global cell identity can also contain Tracking Area Code, TAC, or Tracking Area Identity of the cell; for failure in PSCell change procedure, the failed PSCell cell identity is the cell identity of the target PSCell;

[0084] - source PSCell cell identity of the last PSCell change. The cell identity can be global cell identity, or physical cell identity and frequency information. It can also contain Tracking Area Code, TAC, or Tracking Area Identity of the cell; in S-CPAC procedure, the cell identity is the source PSCell cell of the last CPAC execution. The last CPAC execution can be initial S-CPAC execution or later S-CPAC execution. For later S-

[0085] CPAC execution, the source PSCell cell of the last CPAC execution is the candidate PSCell cell of S-CPAC, which is contained in ConditionalReconfiguration IE. The source PSCell cell identity of the last PSCell change can also be referred to as previousPSCellId;

[0086] - cell list of subsequent CPAC candidate PSCell. The list of subsequent CPAC candidate cells can be directly contained, or in the measurement results, for the cells which are subsequent CPAC candidate cells, contain the indication information that they are subsequent CPAC candidate cells, and the one or more subsequent CPAC candidate cells which are subsequent CPAC candidate cells but not in the measurement results are contained in the secondary cell group failure information. Each candidate PSCell contains cell identity, which can be global cell identity. The cell identity can also contain Tracking Area Code, TAC;

[0087] - subsequent CPAC execution condition. The subsequent CPAC execution condition can be one or more.

[0088] For each candidate PSCell cell, there is one or more execution condition;

[0089] - time from receiving subsequent CPAC configuration to failure;

[0090] - time from receiving subsequent CPAC configuration to subsequent CPAC execution;

[0091] - an indication information corresponding to the subsequent CPAC execution condition satisfying execution, and / or a cell identity information of the PSCell corresponding to the execution condition satisfying;

[0092] - information of which subsequent CPAC execution condition is satisfied first;

[0093] - a time between the two subsequent CPAC execution conditions satisfying, for example, the time can be a time difference between the two subsequent CPAC execution conditions satisfying;

[0094] - an indication information of the subsequent CPAC, the indication information is an indication information of the subsequent CPAC being configured;

[0095] - a status of the SCG, for example, whether the SCG is activated or deactivated, for example, the SCG is suspended;

[0096] - an initial S-CPAC execution condition. Wherein, if the S-CPAC is triggered by the master node, the initial S-CPAC execution condition is configured by the master node, and if the S-CPAC is triggered by the secondary node, the initial S-CPAC execution condition is configured by the source secondary node. S-

[0097] The CPAC execution condition can be one or more. There is one or more S-CPAC execution conditions for each candidate PSCell cell;

[0098] - a subsequent S-CPAC execution condition. The subsequent S-CPAC execution condition is configured by the candidate secondary node. The subsequent S-CPAC execution condition can be one or more. There is one or more S-CPAC execution conditions for each candidate PSCell cell;

[0099] - a SCG failure time, indicating the time from the last time of executing the RRC reconfiguration message containing the PSCell switching information to the SCG failure. For the S-CPAC procedure, the SCG failure time is the time from the last time of executing the RRC reconfiguration message containing the condition reconfiguration information unit (IE ConditionalReconfiguration) to the failure. The condition reconfiguration information unit is sent by the network to the UE, containing the S-CPAC configuration or configuration information, and the S-CPAC configuration includes at least one of the following information:

[0100] S-CPAC candidate cell information, initial S-CPAC execution condition, subsequent S-CPAC configuration, and condition RRC reconfiguration corresponding to the S-CPAC candidate cell. The subsequent S-

[0101] CPAC configuration contains the S-

[0102] The candidate cell list of the CPAC procedure and the S-CPAC execution condition of each candidate cell. The condition RRC reconfiguration contains the RRC reconfiguration message;

[0103] - the indication information of the initial S-CPAC failure or the subsequent S-CPAC failure;

[0104] - the status of the master cell group (MCG), for example, whether the MCG is activated or deactivated, for example, the MCG is suspended;

[0105] - the indication information of the MN triggered S-CPAC or the SN triggered S-CPAC.

[0106] The above-mentioned failure can be an SCG failure, but the present application is not limited thereto, and can also be other types of failures occurring in the secondary cell.

[0107] Step 303, the master node (MN) decides which node causes the failure. For example, it can be decided that the node causing the failure is the master node or the source secondary node (source SN) or the target secondary node or other candidate target secondary node. In an embodiment of the present application, in the S-CPAC, the source secondary node is the source secondary node of the last S-CPAC, and the source PSCell is the source PSCell of the last S-CPAC. The target secondary node or the candidate target secondary node is the target secondary node or the candidate target secondary node of the last S-CPAC. The last S-CPAC can also be said to be the last PSCell change in the S-CPAC procedure.

[0108] The master node can also directly forward the SCG failure information to the secondary node where the failure occurs.

[0109] The master node decides which node causes the failure according to the information in the SCG failure information received from the UE and / or the information saved by the MN.

[0110] The master node can also judge the type of failure, for example, too early PSCell change, too late PSCell change or triggering PSCell change to the wrong PSCell.

[0111] If SCG failure happens after UE stays in one PSCell for a long time, for example, UE does not report the time from S-CPAC execution to failure occurrence or UE reports the time from S-CPAC execution to failure occurrence is larger than a configured threshold, there is a suitable PSCell different from the PSCell UE stays in when failure happens, then it is too late S-CPAC execution. MN knows the suitable PSCell according to the measurement report received from UE, or MN knows the suitable PSCell according to the measurement report received from UE and the information MN saves.

[0112] Too early PSCell change: there is a recent S-CPAC execution or PSCell change before failure happens, for example, according to the indication of S-CPAC execution or according to the time from S-CPAC start execution to failure occurrence is less than a configured threshold, the source PSCell is the suitable PSCell, then it is too early PSCell change. MN or the source node triggering PSCell change knows the suitable PSCell according to the measurement report received from UE, or MN or the source node triggering PSCell change knows the suitable PSCell according to the measurement report received from UE and the information MN or the source node triggering PSCell change saves. SCG failure can be failure happens shortly after PSCell change from source PSCell to target PSCell succeeds or failure happens during PSCell change. The source PSCell is the source PSCell of the last PSCell change.

[0113] Too early S-CPAC execution: S-CPAC execution failure or SCG failure happens shortly after successful S-CPAC execution, there is no suitable PSCell according to the measurement report received from UE, or there is no suitable PSCell according to the measurement report received from UE and the information the node saves. For example, according to the indication of S-CPAC execution or according to the time from S-CPAC start execution to failure occurrence is less than a configured threshold, there is no suitable PSCell, then it is too early S-CPAC execution. MN knows there is no suitable PSCell according to the measurement report received from UE, or MN knows there is no suitable PSCell according to the measurement report received from UE and the information MN saves.

[0114] Triggering PSCell change to wrong PSCell: Failure happens before the latest S-CPAC execution or PSCell change, e.g. according to the indication of S-CPAC execution or according to the time from S-CPAC start execution to failure, the suitable PSCell is not the source PSCell or the target PSCell, then it is triggering PSCell change to wrong PSCell. 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 saved by the MN. The SCG failure can be failure happens shortly after the PSCell change from source PSCell to target PSCell is successful or failure happens during the PSCell change procedure. The source PSCell is the source PSCell of the latest PSCell change. The target PSCell is the target PSCell of the latest PSCell change.

[0115] For too late PSCell change, the MN and the source SN are the nodes that bring the failure.

[0116] For too early PSCell change, if the PSCell change is MN triggered and is initial S-CPAC, the MN is the node that brings the failure. If the PSCell change is source SN triggered and is initial S-CPAC, the source SN is the node that brings the failure. If it is the MN triggered CPA execution that is too early, the MN is the node that brings the failure. For later too early PSCell change, the SN where the corresponding source PSCell is located is the node that brings the failure.

[0117] For triggering PSCell change to wrong PSCell, if the PSCell change is MN triggered and is initial S-CPAC, the MN is the node that brings the failure. If the PSCell change is source SN triggered and is initial S-CPAC, the source SN is the node that brings the failure. For later triggering PSCell change to wrong PSCell, the SN where the corresponding source PSCell is located is the node that brings the failure.

[0118] For the PSCell change triggered to the wrong PSCell, the MN can further determine whether the failure is caused by unreasonable S-CPAC candidate cell configuration or unreasonable S-CPAC execution condition configuration. If the suitable cell is not in the S-CPAC candidate cell configured to the UE, the failure is caused by unreasonable S-CPAC candidate cell configuration. For the initial S-CPAC, if the suitable cell is not in the S-CPAC candidate cell list recommended by the source base station (MN or source SN) that triggers the PSCell change, the problem is caused by the source base station that triggers the PSCell change, e.g. the MN if the PSCell change is triggered by the MN, the source SN if the PSCell change is triggered by the source SN, the destination SN or candidate destination SN if the suitable cell is in the S-CPAC candidate cell list recommended by the source base station (MN or source SN) that triggers the PSCell change, but not in the candidate PSCell list selected by the destination SN or candidate destination SN. For the later S-CPAC, if the suitable cell is not in the S-CPAC candidate cell list configured by the source secondary base station for the later S-CPAC, the problem is caused by the corresponding source secondary base station.

[0119] The MN or source SN can also determine whether the failure is caused by inappropriate estimated arrival probability setting. For example, the MN or source SN sets the estimated arrival probability too low by the MN sending to the candidate destination SN, resulting in the destination SN or candidate SN not selecting the candidate cell as the selected candidate cell or not allocating appropriate resources to the candidate cell in time, while the suitable cell is in the candidate SN, then the MN or source SN is the node that causes the failure. If the estimated arrival probability is decided by the source SN, the failure is caused by the source SN.

[0120] The MN or source SN can also determine whether the failure is caused by inappropriate maximum number of prepared PSCells setting. For example, the MN or source SN sets the maximum number of prepared PSCells too low by the MN sending to the candidate destination SN, resulting in the destination SN or candidate SN not selecting the suitable cell as the selected candidate cell, while the suitable cell is in the candidate SN, then the MN or source SN is the node that causes the failure. If the maximum number of prepared PSCells is decided by the source SN, the failure is caused by the source SN.

[0121] The above description for the PSCell change triggered to the wrong PSCell is described by taking CPC as an example, which is also applicable to the process of CPA and the process of S-CPAC.

[0122] If the MN is the node that causes the failure, step 304 does not need to be performed. If the problem is caused by the source SN, destination SN or candidate destination SN, step 304 is performed.

[0123] Step 304, the master node sends the indication or report of the secondary cell group failure to the node that brings the failure. The node that brings the failure can be the source SN, the target SN or the candidate SN.

[0124] According to the description in step 303, the MN knows that the failure is brought by the source SN, the target SN or the candidate target SN.

[0125] The MN can send the information of the secondary cell group failure to the node that brings the problem through the secondary cell group failure information report message or other messages.

[0126] The message sent by the master node to the node that brings the problem contains one or more of the following information elements:

[0127] The source PSCell cell identity;

[0128] The target PSCell cell identity or the failed PSCell cell identity;

[0129] The suitable PSCell cell identity;

[0130] The SCG failure information received from the UE;

[0131] The candidate PSCell list recommended by the MN or the source SN; each candidate PSCell contains a cell identity, which can be a global cell identity, which can also contain a tracking area code TAC;

[0132] The initial S-CPAC execution condition, for each candidate PSCell cell, there is one or more execution conditions;

[0133] The subsequent S-CPAC execution condition, for each candidate PSCell cell, there is one or more execution conditions;

[0134] The candidate PSCell list selected by the target SN or the candidate target SN; each candidate PSCell contains a cell identity, which can be a global cell identity, which can also contain a tracking area code TAC. The message can contain the candidate PSCell list selected by the target SN or the candidate target SN, or by containing the indication information of whether it is selected by the target SN or the candidate target SN in the candidate PSCell list recommended by the MN or the source SN, the target SN or the candidate target SN knows which candidate PSCell in the candidate PSCell list recommended by the MN or the source SN is selected by the target SN or the candidate target SN, and which candidate PSCell is not selected by the target SN or the candidate target SN according to the indication information in the candidate PSCell list recommended by the MN or the source SN;

[0135] PSCell list recommended by the MN or source SN that is not selected by the target SN or target candidate SN;

[0136] Maximum number of prepared PSCells;

[0137] Estimated arrival likelihood;

[0138] SCG failure time;

[0139] Type of failure, the type of failure includes too early PSCell change, too late PSCell change, triggering PSCell change to wrong PSCell, S-CPAC candidate cell configuration is not suitable, S-CPAC execution condition is not suitable, maximum number of prepared PSCells is not suitable, and / or estimated arrival likelihood configuration is not suitable. This information is included when the MN judges the type of failure, and is not included if the SN that brings the problem judges the type of failure.

[0140] If the MN only judges which node brings the failure, the source SN, target SN or target candidate SN judges the type of failure after receiving the message from the MN. For example, too early PSCell change, too late PSCell change, or triggering PSCell change to wrong PSCell cell.

[0141] If the UE has been in one PSCell for a long time and SCG failure occurs, for example, the UE does not report the time from S-CPC execution to failure occurrence or the UE reports the time from S-CPC execution to failure occurrence is greater than a configured threshold, there is a suitable PSCell different from the PSCell where the UE is at the time of failure occurrence, it is too late S-CPC execution. The SN knows the suitable PSCell according to the 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 saved by the SN. The measurement report received from the UE is received by the MN from the SCG failure information received from the UE.

[0142] Too early PSCell change: there is a recent S-CPAC execution or PSCell change before the failure occurs, e.g., according to the indication of S-CPAC execution or according to the time from the start of S-CPAC execution to the failure occurrence is less than a configured threshold, the source PSCell is the suitable PSCell, then it is a too early PSCell change. The SN knows the suitable PSCell according to the 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 saved by the SN. The SCG failure can be a failure occurred shortly after the successful PSCell change from the source PSCell to the target PSCell or a failure occurred during the PSCell change procedure. The source PSCell is the source PSCell of the last PSCell change. The measurement report received from the UE is received by the MN from the SCG failure information received from the UE.

[0143] Trigger PSCell change to wrong PSCell: there is a recent S-CPAC execution or PSCell change before the failure occurs, e.g., according to the indication of S-CPAC execution or according to the time from the start of S-CPAC execution to the failure occurrence is less than a configured threshold, the suitable PSCell is not the source PSCell or the target PSCell, then it is a trigger PSCell change to wrong PSCell. The SN knows the suitable PSCell according to the 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 saved by the SN. The SCG failure can be a failure occurred shortly after the successful PSCell change from the source PSCell to the target PSCell or a failure occurred during the PSCell change procedure. The source PSCell is the source PSCell of the last PSCell change. The target PSCell is the target PSCell of the last PSCell change. The measurement report received from the UE is received by the MN from the SCG failure information received from the UE.

[0144] The source SN can further determine whether the failure is caused by unreasonable CPC / S-CPAC candidate cell configuration or unreasonable CPC / S-CPAC execution condition configuration. If the suitable cell is not in the CPC / S-CPAC candidate cell configured to the UE, the failure is caused by unreasonable CPC / S-CPAC candidate cell configuration. If the suitable cell is not in the CPC / S-CPAC candidate cell list recommended by the source SN triggering PSCell change, the problem is caused by the source SN triggering PSCell change. If the suitable cell is in the CPC / S-CPAC candidate cell list recommended by the source SN triggering PSCell change, but not in the candidate PSCell list selected by the target SN or candidate target SN, the failure is caused by the target SN or candidate target SN. For the source SN triggering PSCell change to the wrong PSCell, the source SN can further determine whether the failure is caused by unreasonable candidate cell configuration. The source SN can determine whether the failure is caused by the maximum number of prepared PSCells being inappropriate, and / or the estimated arrival probability configuration being inappropriate.

[0145] For the failure caused by the target SN or candidate target SN, there are two methods in the present application to indicate the failure to the target SN or candidate target SN:

[0146] Method one: the MN determines the problem caused by the target SN or candidate target SN, and the specific method is as described in step 303. The MN sends the indication or report information of SCG failure to the target SN or candidate target SN. The message contains the candidate PSCell list recommended by the MN or source SN, the indication information of the candidate PSCell list recommended by the MN or source SN accepted by the target SN or candidate target SN, the indication information of the candidate PSCell list recommended by the MN or source SN not accepted by the target SN or candidate target SN, the maximum number of prepared PSCells, the candidate PSCell list selected by the target SN or candidate target SN, the suitable PSCell cell identity, the SCG failure information, the source PSCell cell identity, the target PSCell cell identity, the failed PSCell cell identity, the suitable PSCell cell identity not selected by the target SN or candidate target SN, and / or the indication information of the selected candidate PSCell being inappropriate, and the SCG failure time. The SCG failure information is the SCG failure information received from the UE. Each candidate PSCell contains a cell identity, which can be a global cell identity, and the global cell identity can further contain a tracking area code (TAC).

[0147] The second way: the MN sends the indication or report information of SCG failure to the source SN, and the source SN further judges the type of failure. If the source SN judges that the problem is caused by the target SN or the candidate target SN, the source SN sends a message to the MN. The message sent by the source SN to the MN includes the MN UE access protocol (AP) identifier, the SN UE AP ID, the candidate PSCell list recommended by the source SN, the indication information of the candidate PSCell list recommended by the source SN accepted by the target SN or the candidate target SN, the indication information of the candidate PSCell list recommended by the source SN not accepted by the target SN or the candidate target SN, the maximum number of prepared PSCells, the candidate PSCell list selected by the target SN or the candidate target SN, the suitable PSCell cell identifier, the SCG failure information, the source PSCell cell identifier, the target PSCell cell identifier, the failed PSCell cell identifier, the suitable PSCell cell identifier not selected by the target SN or the candidate target SN, and / or the indication information of the selected candidate PSCell being unsuitable, and the SCG failure time. Each candidate PSCell includes a cell identifier, which can be a global cell identifier. The global cell identifier can further include a tracking area code (TAC). The source SN can send the above information to the MN through an SCG failure transfer message or other messages. The MN sends a message to the target SN or the candidate target SN, which includes the same information as in the first way, which will not be described here.

[0148] The source SN can also judge whether the failure is caused by the unsuitable setting of the estimated arrival possibility, for example, the estimated arrival possibility set by the source SN to the candidate target SN through the MN is too low, and the suitable cell is in the candidate SN, at this time, the source SN is the node causing the failure. The source SN can also judge whether the failure is caused by the unsuitable setting of the maximum number of prepared PSCells. For example, the maximum number of prepared PSCells sent by the source SN to the candidate target SN through the MN is too low, resulting in that the target SN or the candidate SN does not select the suitable cell as the selected candidate cell, and the suitable cell is in the candidate SN, at this time, the source SN is the node causing the failure.

[0149] The node causing the failure (the source SN, the target SN or the candidate target SN, or the MN) reasonably optimizes the CPC.

[0150] The above description of triggering the PSCell change to the wrong PSCell is based on the CPC, which is also applicable to the process of CPA.

[0151] So far, the method of supporting self-configuration and self-optimization of the application is completed, which can support the robustness of PSCell change in the enhanced mobile process, for example, in S-CPAC, correctly identify the cause of failure occurrence, make reasonable optimization, reduce the occurrence of failure, ensure service continuity, and reduce the labor cost of operators.

[0152] The method of supporting self-configuration and self-optimization of the application is completed, which can support the robustness of PSCell change in the enhanced mobile process, for example, in S-CPAC, correctly identify the cause of failure occurrence, make reasonable optimization, reduce the occurrence of failure, ensure service continuity, and reduce the labor cost of operators. Figure 4 The method can be used to configure UE success PSCell change or increase report in S-CPAC, secondary node addition and / or change process. In the embodiment of the present disclosure, the addition and / or change of the secondary node can also be referred to as the change of the secondary node, and the PSCell change or increase can also be referred to as the change of the PSCell.

[0153] In the embodiment of the present disclosure, each node can be as follows:

[0154] The first node is a single base station or a single node in single connection, and is a master node (MN) in dual connection;

[0155] The second node is a candidate destination secondary node or a destination secondary node. In S-CPAC, there can be one or more candidate destination secondary nodes;

[0156] The third node is a source secondary node in dual connection.

[0157] If the S-CPAC triggered by the first node, the method comprises steps 401-405.

[0158] If the S-CPAC triggered by the third node, the method comprises steps 400-405.

[0159] The specific steps are described as follows:

[0160] Step 400, the first node receives the third configuration information and / or the fourth configuration information of the success master secondary cell change report sent by the third node.

[0161] Under dual connection, if the third node, that is, the source secondary node (S-SN) triggers S-CPAC, the S-SN will provide the third configuration information of the success master secondary cell change report. The third configuration information is used for triggering / generating the success master secondary cell change report when the initial S-CPAC is executed, that is, when the initial CPC is executed.

[0162] The third configuration information of the success master secondary cell change report contains at least one of the following information:

[0163] - the first configuration information of the success primary and secondary cell change report (SPR) comprises at least one of the following information:

[0164] n the threshold of the timer T310 and / or the threshold of the timer T312. Wherein, the threshold is a timer percentage threshold.

[0165] - if the cell in the source SN is a candidate PSCell of S-CPAC, the source SN further provides fourth configuration information of the success primary and secondary cell change report. The fourth configuration information comprises the second configuration information of the success primary and secondary cell change report (SPR) triggered by the timer T304. In S-CPAC, the third node serves as a target secondary node or a candidate target secondary node in the next S-CPAC, and the configuration is used as the configuration of the success primary and secondary cell change report provided by the target secondary node or the candidate target secondary node. The configuration comprises at least one of the following information:

[0166] n the threshold of the timer T304.

[0167] In the embodiments of the present application, the threshold is a timer percentage threshold.

[0168] Step 401, the first node receives the first configuration information of the success primary and secondary cell change report sent by the second node.

[0169] In the embodiments of the present application, the success primary and secondary cell change report and its configuration are also applicable to the case of secondary cell addition, and the success primary and secondary cell change report can also be referred to as the success primary and secondary cell change or addition report, and the configuration of the success primary and secondary cell change report can also be referred to as the configuration of the primary and secondary cell change or addition report. For the convenience of description, the success primary and secondary cell change report and the configuration of the success primary and secondary cell change report are used uniformly in the present application.

[0170] The first configuration information of the success primary and secondary cell change report comprises at least one of the following information:

[0171] - the first configuration information of the success primary and secondary cell change report (SPR) comprises at least one of the following information:

[0172] - the first configuration information of the success primary and secondary cell change report (SPR) comprises at least one of the following information:

[0173] n the threshold of the timer T310 and / or the threshold of the timer T312.

[0174] - a successful primary secondary cell change report (SPR) configuration triggered by a timer T304. In S-CPAC, the second node acts as a target secondary node or a candidate target secondary node at initial S-CPAC or at a later S-CPAC, the configuration is used as a successful primary secondary cell change report configuration provided by the target secondary node or the candidate target secondary node. The configuration contains at least one of the following information:

[0175] a threshold of the timer T304.

[0176] In an embodiment of the disclosure, the threshold is a timer percentage threshold.

[0177] When the first node triggers the S-CPAC, the first node selects a candidate PSCell, and sends a message to a node where the candidate PSCell is located (the second node, i.e., a target SN or a candidate target SN), to request the configuration of the candidate PSCell for the S-CPAC, and provides related configuration. The message can be an SN addition request message or a request message.

[0178] The second node sends a response message to the first node, and the message contains the first configuration information of the successful primary secondary cell change report. The message can be an SN addition request acknowledgement message or other messages.

[0179] The first node sends the first configuration information of the successful primary secondary cell change report and / or the second configuration information of the successful primary secondary cell change report and / or the third configuration information of the successful primary secondary cell change report and / or the fourth configuration information of the successful primary secondary cell change report to the UE.

[0180] In dual connectivity, if the first node, i.e., a master node (MN) triggers the S-CPAC, the MN will provide the second configuration information of the successful primary secondary cell change report to the UE, for triggering / generating the successful primary secondary cell change report when the initial S-CPAC is performed, i.e., when the initial CPC is performed. If the third node, i.e., a source secondary node (S-SN) triggers the S-CPAC, the MN will send the third configuration information of the successful primary secondary cell change report and / or the fourth configuration information of the successful primary secondary cell change report provided by the S-SN in step 400 to the UE.

[0181] The first configuration information is received by the first node from the second node in step 401.

[0182] The second configuration information of the successful primary secondary cell change report contains at least one of the following information:

[0183] - a successful primary secondary cell change report (SPR) configuration triggered by a timer T310 and / or T312. The configuration contains at least one of the following information:

[0184] a threshold of a clock T310 and / or a threshold of a clock T312. Wherein the threshold is a clock percentage threshold.

[0185] When the first node triggers S-CPAC,

[0186] - If it is single connectivity case, in step 402, the first node sends the first configuration information of the successful primary secondary cell change report received from step 401 to the UE.

[0187] - If it is dual connectivity case, in step 402, the first node sends the first configuration information of the successful primary secondary cell change report received from step 401 and / or the second configuration information of the successful primary secondary cell change report provided by the MN to the UE.

[0188] When the second node triggers S-CPAC,

[0189] - The first node sends the third configuration information of the successful primary secondary cell change report provided by the S-SN received from step 400 and / or the fourth configuration information of the successful primary secondary cell change report, and / or the first configuration information of the successful primary secondary cell change report received from step 401 to the UE.

[0190] The UE saves the successful primary secondary cell change report. When the configuration of the successful primary secondary cell change report is satisfied, the UE saves the information of the successful primary secondary cell change report.

[0191] The information saved by the UE contains one or more of the following:

[0192] - The time from receiving the configuration of the successful primary secondary cell change report to sending the successful primary secondary cell change report;

[0193] - The time from the UE saving the successful primary secondary cell change report to sending the successful primary secondary cell change report;

[0194] - The time from performing the primary secondary cell change or addition to sending the successful primary secondary cell change report;

[0195] - The cell information of the primary cell at the time of the primary secondary cell change or addition. The cell information of the primary cell contains the cell identity of the primary cell, and / or the tracking area identity where the primary cell is located. The primary secondary cell change or addition corresponds to the primary secondary cell change or addition corresponding to the successful primary secondary cell change report;

[0196] - The cell information of the source PSCell. The cell information contains the cell identity of the cell, and / or the tracking area identity where the cell is located.

[0197] or a tracking area identity where the cell is located. The identity can be represented using sourcePSCellld. In S-CPAC, the source PSCell is the source PSCell of the last PSCell change. For example, if the report is sent by the UE after the initial S-CPAC execution, the source PSCell cell is the initial source PSCell, i.e. the PSCell on the initial source SN. If the report is sent by the UE after the later S-CPAC execution,

[0198] the source PSCell is the PSCell on the source SN of the last PSCell change; - a cell identity of the target PSCell. The cell information contains the cell identity of the cell, and / or a tracking area identity where the cell is located. The identity can be represented using targetPSCellld. In S-CPAC, the cell of the target PSCell is the PSCell cell that the UE accesses after the S-

[0199] CPAC execution, including the initial S-CPAC and the later S-CPAC execution;

[0200] - a C-RNTI (Cell-Radio Network Temporary Identifier, sourcePSCellldistributed by the source PSCell, which is the same as above;

[0201] - a C-RNTI distributed by the target PSCell, which is the same as above;

[0202] - a C-RNTI distributed by the PCell;

[0203] - a cell identity of the PCell;

[0204] - a C-RNTI distributed by the PCell;

[0205] - UE location information;

[0206] - a cause of the successful PSCell change report. That is, the cause that triggers the SPR. The cause includes:

[0207] - a cause of the timer T310 or T312;

[0208] - a cause of the timer T304;

[0209] - a cause of the timer T316.

[0210] - common random access information;

[0211] - For CPC or CPA, the successful primary secondary cell change report sent by the UE can also contain the time from CPC or CPA configuration to CPC or CPA execution;

[0212] - Whether the primary secondary cell change is MN or SN initiated;

[0213] - Measurement results of the UE;

[0214] - Threshold of T310, threshold of T312 and / or threshold of T304 configured by the MN. When the threshold of T310, threshold of T312 and / or threshold of T304 is configured by the MN, the successful primary secondary cell change report contains the threshold of T310, threshold of T312 and / or threshold of T304;

[0215] - Mobility information of the UE in the PCell of the MN, mobility information of the UE in the source PSCell and / or mobility information of the UE in the target PSCell;

[0216] - The UE receives information from the RRC reconfiguration message whether the primary secondary cell change is MN or SN initiated;

[0217] - Time from S-CPAC configuration to initial S-CPAC execution;

[0218] - Whether the S-CPAC is MN or SN initiated;

[0219] - The UE receives information from the RRC reconfiguration message whether the S-CPAC is MN or SN initiated.

[0220] Step 403, the UE sends a message to the first node or the fourth node, and the message contains information available in the successful primary secondary cell change report. In an embodiment of the present disclosure, the fourth node can also be the second node or the third node. If the UE has a saved successful primary secondary cell change report, the UE sends the information available in the successful primary secondary cell change report to the first node or the fourth node. The method for the UE to save the successful primary secondary cell change report is the same as in step 402, which will not be repeated here.

[0221] The message can be an RRC reconfiguration complete message, an RRC reestablishment complete message, an RRC setup complete message or other messages.

[0222] Step 404, the first node or the fourth node requests the UE to send a successful primary secondary cell change report, and receives the successful primary secondary cell change report sent by the UE. The first node or the fourth node can request the successful primary secondary cell change report through a UE information request message or other messages. The first node or the fourth node receives the successful primary secondary cell change report sent by the UE. The UE can send the information of the successful PSCell change report to the first node or the fourth node through a UE information response message or other RRC messages.

[0223] The successful primary secondary cell change report (SPR) is the same as that in step 402, which is not described here.

[0224] If the fourth node receives the successful primary secondary cell change report (SPR), the fourth node sends the received SPR to the first node. The fourth node knows the first node according to the PCell cell identifier in the received message.

[0225] Step 405, the first node sends the received SPR to the relevant node. The relevant node is the node that needs to perform cause analysis or the node that needs to be optimized. The relevant node can be the MN, or the source SN, or the target SN, or the candidate target SN.

[0226] The first node determines which node to send the SPR according to the information contained in the received SPR. The specific determination method is as follows:

[0227] When the first node triggers S-CPAC,

[0228] -If the reason for triggering the SPR is clock T310 and / or T312:

[0229] nIf the received source PSCell identifier (sourcePSCellId) is the identifier of the source PSCell when the initial S-CPAC is performed, the first node performs root cause analysis and optimization;

[0230] nIf the received source PSCell identifier (sourcePSCellId) is the identifier of the source PSCell when the subsequent S-CPAC is performed, the first node sends the SPR to the SN that controls the cell indicated by the sourcePSCellId, that is, the SN where the cell indicated by the sourcePSCellId is located, that is, the current source SN.

[0231] -If the reason for triggering the SPR is clock T304:

[0232] nThe first node sends the SPR to the SN that controls the target PSCell identifier

[0233] (targetPSCellID) indicated by the targetPSCellID, that is, the target SN. In the third node triggers the initial S-CPAC,

[0234] - If the reason for triggering the SPR is the clock T310 and / or T312:

[0235] n the first node sends the SPR to the SN that controls the cell indicated by the sourcePSCellId, that is, the source SN.

[0236] - If the reason for triggering the SPR is the clock T304:

[0237] n the first node sends the SPR to the SN that controls the cell indicated by the targetPSCellID, that is, the target SN.

[0238] In S-CPAC, after the UE completes the initial S-CPAC execution and successfully accesses the target PSCell (at this time, the target SN becomes the new source SN, that is, the current source SN), the UE determines whether to generate a SPR report according to the SPR configuration of the new source SN and the candidate target SN. Therefore, steps 403-405 will be repeated.

[0239] In an embodiment of the present disclosure, in subsequent S-CPAC, the UE will determine whether to generate a SPR report according to the successful master secondary cell change report configuration provided by the current source SN and the successful master secondary cell change report configuration provided by the candidate target SN corresponding to the current source SN.

[0240] So far, method two of the present application supporting self-configuration and self-optimization is completed. Through this method, in the case of successful master secondary cell change or addition, for example, in the S-CPAC process, the potential failure can be correctly identified to perform reasonable optimization, avoid failure, ensure service continuity, and reduce the manual cost of operators.

[0241] An example of method three of the present application supporting self-configuration and self-optimization is shown in the following table. Figure 5 This method can be used in S-CPAC, secondary node addition and / or change to provide detection of whether there is PSCell change ping-pong. In an embodiment of the present disclosure, the addition and / or change of the secondary node can also be referred to as the change of the secondary node, and the change of the PSCell or addition can also be referred to as the change of the PSCell. The specific steps of method three are described as follows:

[0242] Step 501, the UE accesses the target PSCell and sends a message to the master node.

[0243] In S-CPAC, the UE performs conditional evaluation and accesses the candidate PSCell that meets the execution condition. The UE sends a message to the master node, which contains the destination PSCell information selected by the UE, and the SN RRC response sent to the destination SN, and also contains the RRC reconfiguration message sent by the UE to the SN.

[0244] The message can be an RRC reconfiguration complete message or other message.

[0245] Step 502: The master node sends the SCG history information of the UE to the destination secondary node.

[0246] When the master node receives the destination PSCell information selected by the UE, the master node sends a message to the destination SN. The message contains the SCG history information of the UE. The message can be an SN reconfiguration complete message or other message. The message contains at least one of the following information:

[0247] The SCG history information of the UE contains a list of information of PSCells accessed by the UE. The list contains one or more PSCell information in the order of the UE accessing the PSCells. The PSCell information contains at least one of the following information:

[0248] n Cell identity, which is the PSCell cell identity, i.e., the PSCell cell identity accessed by the UE. The identity can be CGI or other cell identity;

[0249] n UE residence time, i.e., the time the UE stays in the cell;

[0250] n Cell type.

[0251] The RRC reconfiguration complete message is the RRC reconfiguration complete message sent by the UE to the SN.

[0252] In an embodiment of the disclosure, in S-CPAC, the UE performs multiple PSCell switching (or PSCell change), so the same PSCell can appear multiple times in the list. The PSCell that appears at the front of the list is the most recently accessed PSCell.

[0253] Step 503: The destination secondary node saves the SCG history information of the UE. The SCG history information can be used to detect whether there is a ping-pong switching of PSCells.

[0254] The target SN receives the SCG history information of the UE sent by the master node, and according to the history information, the PSCell accessed by the UE and the time spent in the PSCell can be determined. Whether the UE has PSCell ping-pong handover can be detected.

[0255] In S-CPAC, the UE evaluates the execution condition in the subsequent S-CPAC, and selects the target PSCell in the candidate PSCell that meets the execution condition for switching (or changing). Since the UE will perform multiple subsequent S-CPACs, such as performing multiple CPCs, PSCell switching will be performed between candidate PSCells. Therefore, in S-CPAC, steps 501-503 will be repeated.

[0256] So far, the third method of supporting self-configuration and self-optimization of the application is completed. Through this method, in the case of successful master secondary cell change or addition, for example, under S-CPAC, whether there is PSCell ping-pong handover can be correctly identified to perform reasonable optimization, avoid unnecessary switching, avoid unnecessary processing of the network and the UE, ensure service continuity, and reduce the labor cost of the operator.

[0257] An example of embodiment one of the first method of supporting self-configuration and self-optimization of the application is shown in the following table. Figure 6 The method is used for the steps of initial S-CPAC as follows.

[0258] The UE is in a dual connectivity state and is connected to the MN and the source SN (S-SN) at the same time.

[0259] Step 601, the S-SN sends an SN change requirement message to the MN. The message contains the candidate target node identifier. The message can also contain the candidate PSCell list of the S-CPAC recommended by the source SN and the initial S-CPAC execution condition, and the maximum number of PSCells that each candidate target SN can prepare. For the S-CPAC process triggered by the MN, this step does not need to be performed. Each candidate PSCell contains a cell identifier, which can be a global cell identifier. The global cell identifier can also contain a tracking area code (TAC). For each candidate PSCell cell, there is one or more execution conditions.

[0260] The MN saves the information of the S-CPAC process triggered by the S-SN.

[0261] Step 602, the MN sends an SN addition request message to one or more target SNs or candidate target SNs. The message contains at least one of the following information:

[0262] -Indicate that the request is for S-CPAC;

[0263] - Measurement results. If the S-CPAC is MN triggered, the measurement results are provided by the MN, containing the measurement results of the candidate PSCell cells suggested by the MN for S-CPAC; if the S-CPAC is SN triggered, the measurement results are provided by the SN, which can contain the measurement results of the candidate PSCell cells not for S-CPAC;

[0264] - Maximum number of candidate PSCell, indicating the maximum number of candidate PSCell that the target SN or candidate target SN can prepare;

[0265] - Information of other candidate target SNs, containing the information of one or more other candidate target SNs, which contains the candidate PSCell list of each other candidate target SN. The SN receiving the message selects the candidate PSCell for the next S-CPAC. If the S-CPAC is MN triggered, the candidate PSCell list is provided by the MN; if the S-CPAC is SN triggered, the candidate PSCell list is provided by the SN. The candidate PSCell list can directly contain the candidate cell list or the measurement results.

[0266] The MN saves the information that the S-CPAC procedure is triggered by the MN or S-SN.

[0267] Step 603, the target SN or other candidate target SN sends an SN addition request confirmation message to the MN.

[0268] The message contains at least one of the following information:

[0269] - Prepared candidate PSCell list, the target or candidate target SN selects the prepared candidate PSCell according to the candidate PSCell suggested by the MN or S-SN;

[0270] - Next S-CPAC information, corresponding to each of the prepared candidate PSCell. The information includes at least one of the following information:

[0271] Candidate PSCell list, containing the candidate PSCell for the next S-CPAC;

[0272] Execution condition, containing the execution condition for the next S-CPAC.

[0273] If the prepared candidate PSCell list received from the candidate target SN and the candidate PSCell list suggested by step 601 or 602 are different, steps 603a and 603b will be performed. Through the SN modification procedure, the prepared candidate PSCell list updated by other candidate target SNs is provided to all candidate target SNs.

[0274] Step 603a, the MN sends a message to the candidate target SN, providing the prepared candidate PSCell list updated by other candidate target SNs. The message can be a SN modification request message, or other message.

[0275] Step 603b, the candidate target SN sends a message to the MN for confirmation. The updated SCG configuration and / or the execution condition for the subsequent S-CPAC are provided. The message can be a SN modification request acknowledge message, or other message.

[0276] Step 604, the MN sends a radio resource control (RRC) reconfiguration message to the UE. The message contains the S-CPAC configuration.

[0277] Step 605, the UE saves the S-CPAC configuration and sends an RRC reconfiguration complete message to the MN. The RRC reconfiguration complete message is RRC reconfiguration complete*.

[0278] The UE starts to perform the execution condition evaluation. In S-CPAC, the execution condition evaluation is the initial execution condition evaluation, that is, the initial S-CPAC execution condition evaluation.

[0279] Step 605a, the MN sends a SN change confirm message to the source SN.

[0280] Step 606, if at least one candidate PSCell meets the execution condition, the UE sends an RRC reconfiguration complete message to the MN. The message contains the information of the selected target PSCell. The UE is configured using the RRC reconfiguration message corresponding to the target PSCell. In S-CPAC, the execution condition is the initial S-CPAC execution condition. The RRC reconfiguration complete message is RRC reconfiguration complete**.

[0281] Step 607, the UE performs a random access procedure to the target SN and synchronizes to the target SN.

[0282] The UE may fail when performing the initial S-CPAC to the target SN, corresponding to the S-CPAC execution failure case, step 607 fails or does not need to be performed.

[0283] According to embodiments of the present disclosure, the order of steps 606 and 607 is not limited.

[0284] Steps 607a-607b, the MN triggers the SN Modification Request procedure, indicating the SN to stop sending data to the UE. The SN is the source SN or the last serving SN. If it is the source SN, the MN triggers the SN Modification Request procedure when the source SN is a candidate target SN, otherwise the MN will trigger the SN Release procedure.

[0285] Step 608, the SCG failure occurs. The SCG failure can be the failure that occurs when the UE performs the initial S-CPAC and accesses to the target SN or the failure that occurs after the procedure of step 607 is performed. The UE saves the failure related information. The failure related information is the information of the secondary cell group failure in step 302, which is not repeated here.

[0286] Step 609, the UE sends the SCG failure information to the MN. The information contained in the SCG failure information is the same as that described in step 302, which is not repeated here. The UE can send the SCG failure information in step 302 to the MN through the existing SCG failure information message or other RRC message.

[0287] Step 610, the MN determines which node causes the failure. The method of the MN determination is the same as that in step 303, which is not repeated here. The MN can further determine the type of failure, and the specific determination method is the same as that in step 303, which is not repeated here.

[0288] If it is the failure caused by the MN, the procedure ends and the subsequent steps do not need to be performed.

[0289] For the problem caused by the source SN, step 611 is performed.

[0290] For the problem caused by the target SN or the candidate target SN, if it is the PSCell change triggered by the MN, step 613 is directly performed. For the problem caused by the target SN or the candidate target SN, if it is the PSCell change triggered by the source SN, corresponding to the first mode of the present application (the first mode in step 304), step 613 is directly performed; corresponding to the second mode of the present application (the second mode in step 304), steps 611, 612 and 613 are performed.

[0291] Step 611, the MN sends the SCG failure information report message to the source SN. The information contained in the message is the same as that sent by the MN to the source SN in step 304, which is not repeated here. The message sent by the MN to the source SN can be the existing SCG failure information report or other message. If the source SN determines the failure type, the method of the source SN determination is the same as that described in step 304.

[0292] If the suitable PSCell is recommended by the source SN, and the target SN or the candidate target SN does not select the suitable PSCell as the candidate PSCell, step 612 is performed.

[0293] In step 612, the source SN sends an SCG failure indication or an SCG failure transfer message to the MN, and the message contains the same information as that sent by the source SN to the MN in step 304, which will not be repeated here. The source SN can send the information in step 304 to the MN through the existing SCG failure transfer message or other messages.

[0294] In step 613, the MN sends an SCG failure information report to the target SN or other candidate target SN. The SCG failure information report contains the same information as that sent by the MN to the target SN or other candidate target SN in step 304, which will not be repeated here. The MN can send the SCG failure information to the target SN or other candidate target SN through the existing SCG failure information report or other messages.

[0295] So far, the description of the embodiment of the method for supporting self-configuration and self-optimization of the present application has been completed. Through the embodiment, the robustness of PSCell change can be improved in the support of enhanced mobile process, such as S-CPAC, the cause of failure occurrence can be correctly identified, reasonable optimization can be performed, the occurrence of failure can be reduced, service continuity can be ensured, and the labor cost of operators can be reduced.

[0296] An example of the second embodiment of the method for supporting self-configuration and self-optimization of the present application is shown in the following table. Figure 7 The method is used for the following steps in the next S-CPAC.

[0297] The UE is in a dual connection state and is connected to the MN and the source SN (S-SN) at the same time.

[0298] Steps 701-706 are the same as steps 601-606, which will not be repeated here.

[0299] In step 706a, the MN sends an SN reconfiguration complete message to the target SN. According to the target PSCell information selected by the UE received in step 706, if the target PSCell selected by the UE is in the target SN, the MN sends an SN reconfiguration complete message to the target SN to indicate the target PSCell selected by the UE.

[0300] Step 707, the UE performs a random access procedure to the target SN, synchronizes to the target SN, and accesses the target PSCell. The UE has performed the initial S-CPAC and accessed the target cell. At this time, the target SN (SN2) becomes the new source SN, and the target PSCell becomes the new source PSCell. The next S-CPAC candidate PSCell configured by the target PSCell becomes the candidate PSCell, and the SN where the candidate PSCell is located becomes the new candidate SN. If the cell in the initial source SN (SN1) is configured as the S-CPAC candidate PSCell afterwards, at this time, the initial source SN (SN1) also becomes the candidate target SN.

[0301] In an embodiment of the present disclosure, the order of steps 706 and 707 is not limited.

[0302] 707a-707b, the MN triggers an SN modification request procedure and instructs the SN to stop sending data to the UE. The SN is the last serving SN.

[0303] The UE starts to perform the next execution condition evaluation. In the S-CPAC, the next execution condition evaluation is the next S-CPAC execution condition evaluation. When the UE completes the initial S-CPAC execution, the next S-CPAC execution condition evaluation is performed.

[0304] If there is a candidate PSCell that meets the next S-CPAC execution condition, the UE selects the target PSCell of the next S-CPAC and performs step 707c.

[0305] Step 707c is the same as step 706, which will not be described here.

[0306] Step 707d, the UE performs a random access procedure to the target SN, synchronizes to the new target SN, and accesses the new target PSCell. At this time, the source SN of the UE is SN2, the target SN is SN3, and the candidate target SN is SN1.

[0307] The UE may fail when performing the next S-CPAC to the new target SN. Corresponding to the S-CPAC execution failure case, step 707d fails or does not need to be performed.

[0308] Step 708, the SCG failure occurs. The SCG failure can be the failure that occurs when the UE performs the next S-CPAC and accesses the new target SN or the failure that occurs after the process of step 707d is performed. The UE saves the failure-related information. The failure-related information includes the information of the secondary cell group failure in step 302, which will not be described here.

[0309] Step 709, the UE sends SCG failure information to the MN. The SCG failure information contains the same information as in step 302, which will not be repeated here. The UE can send the SCG failure information in step 302 to the MN through the existing SCG failure information message or other RRC message.

[0310] Step 710, the MN determines which node causes the failure. The method of determination of the MN is the same as in step 303, which will not be repeated here. The MN can further determine the type of failure, and the specific determination method is the same as in step 303, which will not be repeated here.

[0311] If the failure is caused by the MN, the process ends, and the subsequent steps do not need to be performed.

[0312] In the subsequent S-CPAC, the SCG failure is not caused by the MN, but by the source SN or the candidate destination SN.

[0313] For the problem caused by the source SN, step 711 is performed.

[0314] For the problem caused by the destination SN or the candidate destination SN, the first mode (mode one in step 304) of the present application is directly performed in step 713; the second mode (mode two in step 304) of the present application is performed in steps 711, 712 and 713.

[0315] Steps 711-713 and steps 611-613 are the same, which will not be repeated here.

[0316] So far, the description of the first embodiment of the method for supporting self-configuration and self-optimization of the present application has been completed. Through the embodiment of the present application, the robustness of PSCell change in the enhanced mobile process, such as in S-CPAC, can be supported, the cause of failure can be correctly identified, reasonable optimization can be performed, the occurrence of failure can be reduced, service continuity can be ensured, and the labor cost of operators can be reduced.

[0317] An example of the third embodiment of the second method for supporting self-configuration and self-optimization of the present application is shown in Figure 8 .

[0318] If the S-CPAC is triggered by the SN, the method includes steps 801-812b.

[0319] If the S-CPAC is triggered by the MN, steps 801 and 805a can be omitted.

[0320] Step 801, the source SN sends an SN change required message to the MN. The message is used for the source SN to trigger S-CPAC. The message contains the successful PSCell change report third configuration information and / or the successful PSCell change report fourth configuration information. The message contains at least one of the following information:

[0321] The successful PSCell change report third configuration information, the specific content can be referred to step 400;

[0322] The successful PSCell change report fourth configuration information, the specific content can be referred to step 400;

[0323] The UE's movement information in the source PSCell;

[0324] The UE's C-RNTI in the source PSCell;

[0325] The candidate PSCell list information contains one or more candidate PSCell information of the source SN's recommended S-CPAC, and the candidate PSCell list information contains one of the following information:

[0326] The cell identity, which is the cell identity of the candidate PSCell, and the cell identity can be a global cell identity (CGI) or other identity.

[0327] The execution condition of the candidate PSCell. In the S-CPAC, the execution condition is the initial S-CPAC execution condition.

[0328] The maximum number of PSCells that each candidate target SN can prepare.

[0329] Step 802, the MN sends an SN addition request message to the candidate target SN. The MN sends the message to the candidate target SN where the candidate PSCell is located, indicating that the request is for S-CPAC.

[0330] In the embodiment of the present disclosure, if it is the source SN triggered S-CPAC, the MN determines the candidate PSCell according to the candidate PSCell list information received in step 801. If it is the source MN triggered S-CPAC, the MN selects the candidate PSCell according to the measurement result.

[0331] Step 803, the candidate target SN sends an SN addition request confirmation message to the MN. The message contains the successful PSCell change report first configuration information. The message contains at least one of the following information:

[0332] - the first configuration information of the successful PSCell change report, the specific content of which can be referred to step 401;

[0333] - the mobility information of the UE in the target PSCell;

[0334] - the C-RNTI of the UE in the target PSCell.

[0335] Step 804, the MN sends an RRC reconfiguration message to the UE. The message contains at least one of the following information:

[0336]

[0337] - the first configuration information of the successful PSCell change report;

[0338] - the second configuration information of the successful PSCell change report;

[0339] - the third configuration information of the successful PSCell change report;

[0340] - the fourth configuration information of the successful PSCell change report;

[0341] - information indicating whether the PSCell change is MN-initiated or SN-initiated;

[0342] - the mobility information of the UE in the PCell of the MN;

[0343] - the mobility information of the UE in the source PSCell;

[0344] - the mobility information of the UE in the target PSCell;

[0345] - S-CPAC configuration, the configuration including at least one of the following information: S-CPAC candidate cell identification, S-CPAC execution condition (including initial S-CPAC execution condition and next S-CPAC execution condition), and conditional RRC reconfiguration corresponding to the S-CPAC candidate cell.

[0346]

[0347] In the embodiments of the present disclosure, the first configuration information of the successful PSCell change report can be received from the candidate target SN, and the second configuration information of the successful PSCell change report can be configured by the MN. The third configuration information of the successful PSCell change report and the fourth configuration information of the successful PSCell change report can be received from the source SN. The specific content and role of the configuration information can be referred to the description in the second method of self-configuration and self-optimization.

[0348] ​​Step 805, the UE saves the received information and sends an RRC reconfiguration complete message to the MN. The RRC reconfiguration complete message can be RRC Reconfiguration Complete*. The UE saves the configuration information of the successful PSCell change report.

[0349] The UE performs the condition evaluation for the selection of the target PSCell.

[0350] The UE determines whether to generate the SPR report according to the first configuration information of the successful PSCell change report and / or the second configuration information of the successful PSCell change report and / or the third configuration information of the successful PSCell change report and / or the fourth configuration information of the successful PSCell change report received in step 804. If the SPR report is generated, the information available for the successful PSCell change report is sent to the MN.

[0351] Step 805a, the MN sends an SN change confirm message to the source SN.

[0352] If it is an S-CPAC triggered by the source SN, the MN sends an SN change confirm message to the source SN after receiving the RRC reconfiguration complete message sent by the UE.

[0353] Step 806, the UE sends an RRC reconfiguration complete message to the MN. If at least one candidate PSCell meets the execution condition, the UE sends an RRC reconfiguration complete message to the MN. The message contains the information of the selected target PSCell. The message can also contain the information available for the successful PSCell change report. The RRC reconfiguration complete message can be RRC Reconfiguration Complete**. If the target PSCell selected by the UE belongs to SN2, then SN2 is the target SN.

[0354] Step 807, the MN sends an SN reconfiguration complete message to the target SN. The message also contains the movement information of the UE in the PCell of the MN and / or the movement information of the UE in the source PSCell. The message also contains the C-RNTI of the UE in the PCell of the MN and / or the C-RNTI of the UE in the source PSCell.

[0355] Step 807a, the MN sends a message to the source SN. The message can be an SN release request message, or an SN modification request message, or a UE context release message, or other messages.

[0356] If the source SN is a candidate target SN for S-CPAC, the message is an SN modification request message.

[0357] Step 807b, the source SN sends a message to the MN. The message can be a SN Release Request Acknowledge message, or a SN Modification Request Acknowledge message, or other message.

[0358] Step 808a, the MN sends a UE Information Request message to the UE, requesting the UE to report a successful PSCell change report.

[0359] Step 808b, the UE sends a message to the MN. The message contains a successful PSCell change report. The content of the successful PSCell change report is the same as in step 404, which will not be repeated here. The message can be a UE Information Response message or other RRC message.

[0360] In an embodiment of the disclosure, steps 808 (including 808a and 808b) and steps 807 and 807a do not have an absolute order. Step 808 can be performed first, and then steps 807 and 807a are performed. Or steps 807 and 807a are performed first, and then step 808 is performed. Or step 807 is performed first, and then step 808 is performed, and then step 807a is performed. That is, according to an embodiment of the disclosure, steps 808 (including 808a and 808b) and steps 807 and 807a can be performed in any order as needed.

[0361] The MN decides whether the successful PSCell change report is caused by the configuration of the MN, or caused by the configuration of the source SN or the configuration of the target SN, so that the MN decides to send the SPR to which node. If it is caused by the configuration of the target SN, the MN sends the successful PSCell change report to the target SN. If it is caused by the configuration of the source SN, the MN sends the successful PSCell change report to the source SN. If it is caused by the MN, the MN performs the corresponding optimization. The method of determining which node to send the SPR to is shown in step 405, which will not be repeated here.

[0362] The MN sends the information of the successful PSCell change report to the source SN or the target SN through the Access and Mobility Indication message or a newly defined message. The MN can also send the successful PSCell change report to the target SN through the SN Reconfiguration Complete message. The MN can also send the successful PSCell change report to the source SN through the UE Context Release message or the SN Modification Request message or the SN Release Request message.

[0363] In S-CPAC, after the UE successfully accesses the target PSCell cell, when performing the next S-CPAC, the target PSCell is selected according to the saved configuration information received in step 804, and it is determined whether to generate a SPR report. That is, steps 809-812b are performed.

[0364] Step 809 is the same as step 806, except that SN2 is the current source SN of the UE, and the target PSCell selected by the UE belongs to SN3, and SN3 is the target SN of the UE.

[0365] Step 810: The MN sends an SN Reconfiguration Complete message to the target SN. At this time, the target SN of the UE is SN3. For details, see step 807, which will not be described here.

[0366] Step 811a: The MN sends a message to the source SN. At this time, the source SN is SN2. The message can be an SN Release Request message, or an SN Modification Request message, or a UE Context Release message, or other messages. If the source SN is a candidate target SN of S-CPAC, the message is an SN Modification Request message.

[0367] Step 811b: The source SN sends a message to the MN. At this time, the source SN is SN2. The message can be an SN Release Request Ack message, or an SN Modification Request Ack message, or other messages.

[0368] Steps 812a-812b are the same as steps 808a-808b, and the UE sends a successful PSCell change report to the MN according to the request of the MN. For details, see steps 808a-808b, which will not be described here.

[0369] In an embodiment of the present disclosure, steps 812 (including 812a and 812b) and steps 810 and 811a do not have an absolute order. Step 812 can be performed first, and then steps 810 and 811a can be performed. Or steps 810 and 811a can be performed first, and then step 812 can be performed. Or step 810 can be performed first, and then step 812 can be performed, and then step 811a can be performed. That is, according to an embodiment of the present disclosure, steps 812 (including 812a and 812b) and steps 810 and 811a can be performed in any order as needed.

[0370] The MN decides which node to send the successful PSCell change report to. For details of the method of determining which node to send the SPR to, see step 405, which will not be described here. In an embodiment of the present disclosure, at this time, the source SN is SN2, and the target SN is SN3.

[0371] So far, the description of the embodiment of the second method of the present application supporting self-configuration and self-optimization has been completed. Through the embodiment of the present application, the successful PSCell change report can be reasonably configured and processed in an enhanced mobile process, for example, in S-CPAC, potential failures can be correctly identified, the robustness of PSCell change can be enhanced, reasonable optimization can be performed, the occurrence of failures can be reduced, service continuity can be ensured, and the labor cost of operators can be reduced.

[0372] An example of embodiment four of method three of self-configuration and self-optimization supported by the present application is shown as follows. Figure 9

[0373] The specific steps are as follows:

[0374] The S-CPAC configuration for the UE is completed, and the UE performs the execution condition evaluation. If at least one candidate PSCell meets the execution condition, step 901 is performed.

[0375] Step 901, the UE sends an RRC reconfiguration complete message to the MN. The message contains information of the selected destination PSCell, such as PSCell identification, which can be a conditional reconfiguration identification, or a PCI, or a CGI, or other cell identification. The message can be an RRC reconfiguration complete message, or other messages.

[0376] Step 902, the MN sends an SN reconfiguration complete message to the destination SN.

[0377] If the UE selected destination PSCell is a cell in SN2, then the destination SN is SN2.

[0378] The message contains SCG history information of the UE. The message can be an SN reconfiguration complete message, or other messages. The information contained in the message can refer to step 502, and will not be described here. For example, if the source PSCell in the source SN (SN1) is PSCell1, the SCG history information will contain the identification of PSCell1, and the time the UE stays in PSCell1, and other information.

[0379] The destination secondary node (SN2) receives and saves the SCG history information of the UE. The information can be used to detect whether there is a PSCell ping-pong handover. According to the history information, the destination SN can determine the PSCells the UE has accessed, and the time the UE stays in the PSCells, thereby detecting whether there is a PSCell ping-pong handover of the UE. For example, if the UE stays in a PSCell for a very short time, the SN2 can not configure the cell as a candidate cell, thereby avoiding unnecessary PSCell change to the cell. Alternatively, the destination SN can avoid PSCell ping-pong handover by adjusting or deleting the configured candidate PSCell.

[0380] In S-CPAC, after the UE successfully accesses the destination PSCell cell, the UE continues to perform the execution condition evaluation according to the saved S-CPAC configuration. If at least one candidate PSCell meets the execution condition, step 903 is performed. ​

[0381] Step 903, the UE sends an RRC reconfiguration complete message to the MN. The message contains information of the selected new target PSCell, such as PSCell identity, which can be conditional reconfiguration identity, or PCI, or CGI, or other cell identity. The message can be an RRC reconfiguration complete message, or other message.

[0382] Step 904, the MN sends an SN reconfiguration complete message to the target SN.

[0383] If the UE selected target PSCell is a cell in SN3, the target SN is SN3.

[0384] The message contains SCG history information of the UE. The message can be an SN reconfiguration complete message, or other message. The information contained in the message can refer to step 502, and will not be described here.

[0385] For example, before accessing SN3, the UE has accessed SN1 and SN2, if the cell accessed in SN1 is PSCell1, and the cell accessed in SN2 is PSCell2, the SCG history information will sequentially contain information of PSCell1 and PSCell2. The information contains identity of PSCell, and time of the UE staying in the PSCell.

[0386] The target secondary node (SN3) receives and saves the SCG history information of the UE. The information is used to detect whether there is PSCell ping-pong switching. The target SN can determine PSCells accessed by the UE and time of the UE staying in the PSCells according to the history information, so as to detect whether there is PSCell ping-pong switching of the UE. Optionally, the target SN can avoid PSCell ping-pong switching by adjusting or deleting candidate PSCells configured by it.

[0387] An example of method four of supporting self-configuration and self-optimization is shown in the following table. Figure 10 Based on the method, selection of candidate PSCell cells can be optimized. The specific steps are described as follows:

[0388] The state of SCG of the PSCell includes an activated state and a deactivated state. The state of SCG can be changed. In the embodiment of the present application, the master node, the secondary node and the UE can all trigger adjustment of the state of SCG.

[0389] Step 1001, the master node saves or records the SCG state information of the PSCell accessed by the UE. In the embodiment of the present application, the PSCell accessed by the UE is the PSCell recently accessed by the UE, including the PSCell currently serving the UE.

[0390] The SCG state information can include SCG state, SCG state duration, and / or time of SCG state adjustment, and can also include other information. The SCG state includes SCG deactivation state and / or SCG activation state. The SCG deactivation state information includes SCG deactivation state and / or duration of SCG deactivation state.

[0391] The UE will perform PSCell change and / or addition multiple times, and the UE will have multiple accessed PSCells and the current PSCell. Therefore, the master node can save the SCG state information of the PSCell recently accessed (or accessed) by the UE and / or the current source PSCell. In the embodiment of the present application, the SCG state information includes SCG deactivation state information, for example, including SCG deactivation state and / or duration of SCG deactivation state. Optionally, the master node can store the information of multiple accessed PSCells in the order of time of the PSCells accessed by the UE, with the most recently accessed PSCell placed first.

[0392] In the embodiment of the present application, the SCG state information can be saved in the UE accessed PSCell history information.

[0393] The master node saves or records the UE accessed PSCell history information. The UE accessed PSCell history information can also be SCG UE history information. The UE accessed PSCell history information includes a list of PSCells accessed by the UE. The list of PSCells accessed by the UE includes information of the PSCell recently accessed by the UE. The PSCell information includes PSCell identification, time of the UE staying in the PSCell, state of the PSCell, deactivation time of the PSCell, deactivation state duration of the PSCell, activation time of the PSCell, and / or activation state duration of the PSCell.

[0394] Optionally, the master node can optimize the selection of candidate PSCell or target PSCell according to the stored SCG state information. Optionally, the existing candidate PSCell candidate cell can be adjusted or deleted.

[0395] In embodiments of the application, when the SCG status of a PSCell is adjusted, the master node and / or the secondary node need to perform the update and store the SCG status information of the PSCell. The SCG status adjustment can be triggered by the master node or the secondary node or the UE. The procedures of SCG status adjustment triggered by different nodes are described below respectively.

[0396] SCG status adjustment procedure triggered by the master node

[0397] If the master node determines that the SCG status needs to be adjusted, the master node sends a message to the source secondary node, the message contains the SCG status request, the SCG status request can be to activate the SCG or to deactivate the SCG. The master node determines the SCG status adjustment can be based on one or more of the following: load condition, amount of traffic transmitted, resource condition or other factors.

[0398] The message can be a SN Modification Request message or other message. The message contains at least the following information:

[0399] -SCG status request (or SCG activation request). The request can be to activate the SCG or to deactivate the SCG.

[0400] The source secondary node sends a feedback message to the master node, the message contains the accepted adjusted SCG status. The message can be a SN Modification Request Acknowledge message or other message. The message contains at least the following information:

[0401] -SCG status or SCG activation status. The status can be SCG activated or SCG deactivated.

[0402] Optionally, the source secondary node can record or store the SCG status information of the source PSCell. The SCG status information can include one or more of the following: SCG status, status duration, and time of status adjustment or other information. The record can also include recording the SCG deactivation status information, for example, the duration of the deactivation status.

[0403] The master node sends the received SCG status to the UE.

[0404] The master node can record or store the SCG status information of the source PSCell. The SCG status information can include one or more of the following: SCG status, status duration, and time of status adjustment or other information. The record can also include recording the SCG deactivation status information, for example, the duration of the deactivation status.

[0405] SCG status adjustment triggered by the source secondary node

[0406] If the source secondary node determines that the SCG status needs to be adjusted, the source secondary node sends a message to the master node, the message contains a SCG status request, the SCG status request can be to activate the SCG or to deactivate the SCG. The source secondary node determines the SCG status adjustment based on one or more of the following factors: the amount of traffic transmitted, the resource status, or other factors.

[0407] The message can be a SN modification required message, or other message. The message contains at least the following information:

[0408] -SCG status request (or SCG activation request). The request can be to activate the SCG, or to deactivate the SCG.

[0409] The master node determines the information sent to the UE based on the received SCG status request. If the received SCG status request is a SCG deactivation status request, the master node sends the requested SCG status to the UE, otherwise the requested SCG status does not need to be sent to the UE. The message sent to the UE to request the SCG status can be a RRC reconfiguration message, or other message. The UE determines whether to activate or deactivate the SCG based on whether the received message contains the SCG status. If the received message contains the SCG status, the SCG is deactivated, otherwise the SCG is activated.

[0410] The master node sends a message to the source secondary node to feedback the SCG status request sent by the source secondary node after receiving the feedback message from the UE. In an embodiment of the application, the feedback message received by the master node from the UE can be a RRC reconfiguration complete message, or other message. The message sent by the master node to the source secondary node can be a SN modification confirm message.

[0411] Optionally, the master node and / or the source secondary node can record or store the SCG status information of the source PSCell. The SCG status information can include one or more of the following: the SCG status, the duration of the status, and the time of the status adjustment, or other information. The record can also include recording the SCG deactivation status information, for example, the duration of the deactivation status.

[0412] UE triggered SCG status adjustment

[0413] If the SCG status is deactivated, when there is uplink data arriving on the SCG bearer, the UE sends a message to the master node to indicate that there is uplink data transmitted through the SCG bearer. The UE can also send a message to the master node to indicate that the SCG deactivation is preferred, if the network configures the UE to send the information.

[0414] The message can be a UE Assistance Information message, or other message. The message contains at least one of the following information:

[0415] SCG-deactivation Preference, which can also be referred to as SCG-deactivation Preference. The SCG-deactivation Preference is used to indicate whether the UE prefers or has a preference for SCG deactivation. The SCG-deactivation Preference contains two options: prefer SCG deactivation, no preference.

[0416] Uplink Data, which is used to indicate whether there is uplink data. If the Uplink Data is included in the message, it is used by the UE to indicate that there is uplink data on the SCG to be deactivated.

[0417] The master node determines whether the SCG state needs to be adjusted based on the information contained in the message received from the UE. If the SCG state needs to be adjusted, the master node sends a message to the source secondary node requesting the SCG state, and the source secondary node sends a feedback message to the master node containing the accepted adjusted SCG state. The master node sends the received SCG state to the UE. In embodiments of the present application, the message transmission between the master node and the source secondary node and the behavior of the master node and the source secondary node are the same as described in the SCG state adjustment process triggered by the master node, and will not be described again here.

[0418] When a PSCell change needs to be performed, such as a PSCell change triggered by the MN or the SN, step 1002 is performed. The SN at this time is also the source SN. In the present method, the SN described above is also the source SN. The PSCell change can be a normal PSCell change, a conditional handover with SCG, CPC, or S-CPAC.

[0419] In step 1002, the master node sends a message to the target secondary node containing the SCG state information of the PSCell visited by the UE. The SCG state information of the PSCell visited by the UE is the same as described in step 1001, and will not be described again here.

[0420] The master node can send the SCG state information of the PSCell recently visited by the UE stored by it to the target secondary node.

[0421] The master node can also request the SCG state information of the PSCell recently visited by the UE stored by the source secondary node by sending a message to the source secondary node, and receive the SCG state information of the PSCell visited by the UE from the source secondary node.

[0422] When the UE selects a target PSCell, or the network selects a target PSCell for the UE, or the UE completes the PSCell change access to the target PSCell, the master node sends the stored SCG state information of the last visited PSCell to the target secondary node. The information can be used to optimize the selection of the candidate PSCell or the target PSCell. Optionally, the candidate cells of the existing candidate PSCell can be adjusted or deleted.

[0423] The message can be an SN reconfiguration complete message, or an SN addition request message, or an SN modification request message, or other messages. The message contains one or more SCG state information of the PSCell visited by the UE, and the multiple SCG state information is sorted according to the time when the UE visits the PSCell, and the most recently visited is placed in front. The SCG state information contains at least one of the following information:

[0424] (1) Cell identification, the cell identification is the PSCell cell identification, that is, the PSCell cell identification visited by the UE. The identification can be CGI, or other cell identification;

[0425] (2) SCG state information, the SCG state information contains at least one of the following information:

[0426] -SCG deactivation state;

[0427] -SCG deactivation state duration;

[0428] -SCG activation state;

[0429] -SCG activation state duration

[0430] -SCG activation time;

[0431] -SCG deactivation time.

[0432] So far, the fourth method of supporting self-configuration and self-optimization of the application is completed. Through the method of the application, reasonable optimization of target PSCell or candidate PSCell selection in enhanced mobile process can be supported, business continuity and effective use of resources are guaranteed, and the manual cost of operators is reduced.

[0433] An example of the fifth embodiment of the fourth method of supporting self-configuration and self-optimization of the application is shown in Figure 11 .

[0434] The UE is in a dual connection state, simultaneously connected to the MN and the source SN (S-SN).

[0435] According to the description in Method Four, the master node, the source secondary node and the UE can all trigger the adjustment of the SCG state. According to an embodiment of the present application,

[0436] The process of the SCG state adjustment triggered by the source secondary node is shown in steps 1101-1104.

[0437] The process of the SCG state adjustment triggered by the master node is shown in steps 1106-1110.

[0438] The process of the SCG state adjustment triggered by the UE is shown in steps 1105-1110.

[0439] In an embodiment of the present application, the adjustment of the SCG state can be triggered multiple times, which can be triggered by the master node and / or the source secondary node and / or the UE. The above three processes have no sequence.

[0440] In step 1101, the source secondary node sends a message to the master node for sending the SCG state request. The message can be an SN modification required message or other messages.

[0441] When the source SN decides to adjust the SCG state, the source SN sends the SCG state request to the MN. The message contains at least the following information:

[0442] SCG state request (or SCG activation request). The request can be to activate the SCG or to deactivate the SCG.

[0443] In step 1102, the master node sends a message to the UE. The message can be an RRC reconfiguration message or other messages.

[0444] When the master node receives the SCG state request sent by the source SN, it determines the information sent to the UE according to the received SCG state request. If the received SCG state request is a SCG deactivation state request, the master node sends the requested SCG state to the UE, otherwise it does not need to send the requested SCG state to the UE. The message contains at least the following information:

[0445] SCG state, which can be a deactivation state.

[0446] In step 1103, the UE sends a message to the master node. The message can be an RRC reconfiguration complete message or other messages. The message can indicate that the UE has completed the reconfiguration, including the completion of the activation or deactivation of the SCG. The UE determines whether to activate or deactivate the SCG according to whether the SCG state is contained in the message received from the master node. If the SCG state is contained in the received message, the SCG is deactivated, otherwise the SCG is activated.

[0447] At this time, the master node can record or store the SCG status information of the source PSCell, which can include one or more of the SCG status, the status duration, and the time of status adjustment or other information. The recording can also include recording the SCG deactivation status information, such as the duration of the deactivation status. In an embodiment of the present application, the master node saves the SCG status of multiple source PSCells (including the PSCells visited by the UE and the current source PSCell) in the order of the time when the UE visits the PSCells.

[0448] At step 1104, the master node sends a message to the source secondary node. The message can be an SN modification confirmation message or other message.

[0449] After receiving the feedback message from the UE, the master node sends a message to the source secondary node to feedback the SCG status request sent by the source secondary node. The message sent by the master node to the source secondary node can be an SN modification confirmation message.

[0450] Optionally, the source secondary node can record or store the SCG status information. The SCG status information can include one or more of the SCG status, the status duration, and the time of status adjustment or other information. The recording can also include recording the SCG deactivation status information, such as the duration of the deactivation status.

[0451] At step 1105, the UE sends a message to the master node to provide information for SCG status adjustment. The message can be a UE assistance information (UEAssistanceInformation) message or other message. The message contains at least one of the following information:

[0452] (1) SCG deactivation preference, which can also be referred to as SCG deactivation tendency. The SCG deactivation preference is used to indicate whether the UE tends to or prefers SCG deactivation. The SCG deactivation preference contains two options: prefer SCG deactivation, no preference;

[0453] (2) Uplink data, which is used to indicate whether there is uplink data. If the message contains the uplink data, it is used for the UE to indicate that there is uplink data on the deactivated SCG.

[0454] At step 1106, the master node sends a message to the source secondary node, which contains the SCG status request. The message can be an SN modification request message or other message. When the MN decides to adjust the SCG status, it sends the SCG status request to the source SN. The message contains at least the following information:

[0455] SCG status request (or SCG activation request). The request can be to activate SCG, or to deactivate SCG.

[0456] In embodiments of the application, the MN decides to adjust the SCG status, which can be determined according to one or more of load conditions, amount of traffic transmitted, resource conditions, or other factors. It can also be determined according to the information of the UE received in step 1105.

[0457] In step 1107, the source secondary node sends a message to the master node. The message contains the acceptance of the adjusted SCG status by the secondary node. The message can be a SN modification request acknowledge message, or other message. The message contains at least the following information:

[0458] SCG status, or SCG activation status. The status can be SCG activated, or SCG deactivated.

[0459] Optionally, the source secondary node can record or store SCG status information. The SCG status information can include one or more of SCG status, duration of the status, and time of the status adjustment, or other information. The recording can also include recording SCG deactivation status information, such as duration of the deactivation status.

[0460] In steps 1108-1109, the master node sends the received SCG status to the UE. In embodiments of the application, steps 1108-1109 are the same as steps 1102-1103, which are not repeated here.

[0461] In step 1110, the master node sends a message to the source secondary node. Optionally, the master node sends the message to the source secondary node after receiving the message sent by the UE. The message is used to indicate that the UE has completed the SCG configuration, which can include completion of the SCG status adjustment.

[0462] Step PSCell change, which can be a PSCell change triggered by the MN or the source SN, or a PSCell change by the UE selecting a target PSCell under CPC or S-CAPC.

[0463] In step 1111, the UE sends a message to the master node. The message can be an RRC reconfiguration complete message, or other message. The message can contain at least one of the following information:

[0464] (1) Cell identity, which is the cell identity of the target PSCell. The identity can be CGI, or PCI, or other cell identity.

[0465] (2) SN RRC response, containing the RRC reconfiguration complete message sent by the UE to the SN.

[0466] Step 1112, the master node sends a message to the target SN (T-SN). The master node sends the SCG state information to the target SN.

[0467] The message can be an SN reconfiguration complete message, or an SN addition request message, or an SN modification request message, or other messages. In an embodiment of the application, the SCG state information can be stored by the master node, or obtained by the master node from the source secondary node. The message contains at least one of the following information:

[0468] (1) SCG state information of one or more PSCells accessed by the UE. The multiple SCG state information is sorted according to the time when the UE accesses the PSCell. The state information contains at least one of the following information:

[0469] - Cell identity, which is the PSCell cell identity, that is, the PSCell cell identity accessed by the UE. The identity can be CGI, or other cell identity;

[0470] - SCG state information, which contains at least one of the following information:

[0471] - SCG deactivation state;

[0472] - SCG deactivation state duration.

[0473] (2) RRC reconfiguration complete message, which is the RRC reconfiguration complete message sent by the UE to the SN.

[0474] Optionally, the target SN uses the received SCG state information to optimize the selection of the candidate PSCell or the target PSCell. Optionally, the existing candidate cell of the candidate PSCell can be adjusted or deleted.

[0475] So far, the description of the embodiment of the method four of the application supporting self-configuration and self-optimization is completed. Through the embodiment of the application, the reasonable optimization of the selection of the target PSCell or the candidate PSCell in the enhanced mobile process can be supported, the service continuity and the effective use of resources can be ensured, and the manual cost of the operator can be reduced.

[0476] An example of the method five of the application supporting self-configuration and self-optimization is shown in the following table. Figure 12 The method is used in the failure scenario occurring in the process of MN triggered SCPAC. The method comprises the following steps:

[0477] At step 1201, the MN receives the SCG failure information from the UE. The information contained in the SCG failure information is the same as that in step 302, which will not be repeated here.

[0478] At step 1202, the MN performs initial analysis. The MN determines the type of PSCell change or addition.

[0479] For the MN triggered S-CPAC, the MN performs cause analysis. The cause analysis includes determining whether it is too early CPC / CPA execution, too late CPC execution, or CPC / CPA execution to the wrong PSCell. The specific determination method is the same as that in step 303, which will not be repeated here. The cause analysis also includes determining whether it is due to unreasonable candidate PSCell cell configuration or unreasonable execution condition configuration. It can also include determining which node causes the failure and / or which node needs related optimization. The MN knows that it is the MN triggered S-CPAC according to the saved information or according to the SCG failure information received from the UE, for example, the MN knows that it is the MN triggered S-CPAC according to the indication information of the MN triggered S-CPAC or the SN triggered S-CPAC contained in the SCG failure information. The cause analysis in the present application can also be referred to as root cause analysis.

[0480] If the suitable PSCell is not one of the candidate PSCells recommended by the MN or is one of the candidate PSCells recommended by the MN but is not one of the candidate PSCells selected by the candidate or target SN, it is due to unreasonable candidate PSCell configuration, otherwise it is due to unreasonable execution condition. 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 saved by the MN, which is the same below.

[0481] For the initial S-CPAC of the MN initiated S-CPAC, if the suitable PSCell is one of the candidate PSCells recommended by the MN but is not one of the candidate PSCells selected by the candidate or target SN, step 1203 is performed, otherwise the MN performs related optimization. If the suitable PSCell is not reasonably recommended by the MN or the execution condition is not reasonably configured, the MN needs to perform corresponding optimization. Here, the initial S-CPAC of the MN initiated S-CPAC refers to the failure due to the initial S-CPAC or the failure related to the initial S-CPAC.

[0482] For the subsequent S-CPAC of MN initiated S-CPAC, if the suitable PSCell is not the one recommended by MN, the MN performs the related optimization, otherwise, step 1203 is performed. If the suitable PSCell is one of the candidate PSCells recommended by MN but not one of the candidate PSCells selected by the candidate or target SN or the execution condition is unreasonable, it is the failure caused by the candidate or target SN, the target or candidate SN needs to perform the related optimization, and step 1203 is performed. Here, the subsequent S-CPAC of MN initiated S-CPAC refers to the failure caused by the subsequent S-CPAC or the failure related to the subsequent S-CPAC.

[0483] If the MN performs the related optimization, step 1203 does not need to be performed.

[0484] The MN knows whether it is the initial S-CPAC or the subsequent S-CPAC according to the saved information or according to the indication information of the initial S-CPAC failure or the subsequent S-CPAC failure in the SCG failure information received from the UE.

[0485] In step 1203, the MN sends a message to the node that needs to perform the related optimization. For the MN triggered S-CPAC, the MN sends a message to the candidate or target SN, and the candidate SN or target SN performs the related optimization. The candidate SN also includes the source SN of the subsequent S-CPAC. The message contains the same information as in step 304, which will not be repeated here. The message can be an SCG failure information report or other message, and the present application does not limit it. If the MN only judges which node causes the failure, the source SN, target SN or candidate target SN judges the type of failure after receiving the message from the MN. The specific judgment method is the same as in step 304, which will not be repeated here.

[0486] So far, the method five of the present application supporting self-configuration and self-optimization is completed. It can support the robustness of PSCell change in the enhanced mobile process, such as in S-CPAC, correctly identify the cause of failure to occur, perform reasonable optimization, reduce the occurrence of failure, ensure service continuity, and reduce the labor cost of operators.

[0487] An example of the method six of the present application supporting self-configuration and self-optimization is shown in the following table. Figure 13 The method is used in the scenario of failure occurring in the process of MN triggered SCPAC. The method includes the following steps:

[0488] In step 1301, the MN receives the SCG failure information from the UE. The information contained in the SCG failure information is the same as in step 302, which will not be repeated here.

[0489] Step 1302, the MN performs initial analysis. The MN determines the type of PSCell change or addition.

[0490] For MN triggered S-CPAC, the MN performs cause analysis due to the failure of initial S-CPAC. The failure due to initial S-CPAC can also be said to be the failure related to initial S-CPAC. The cause analysis is performed the same as in step 1202. The MN knows it is MN triggered S-CPAC according to the saved information or according to the indication information of MN triggered S-CPAC or SN triggered S-CPAC contained in the SCG failure information received from the UE. The MN knows whether it is initial S-CPAC or subsequent S-CPAC according to the saved information or according to the indication information of initial S-CPAC failure or subsequent S-CPAC failure in the SCG failure information received from the UE. If the suitable PSCell is one of the candidate PSCells recommended by the MN but not one of the candidate PSCells selected by the candidate or target SN, the MN sends a message to the node that needs to perform the related optimization, otherwise the MN performs the related optimization. The MN sends the message to the node that needs to perform the related optimization specifically the same as described in step 1203, which will not be repeated here. The MN needs to perform the corresponding optimization if the suitable PSCell is not recommended by the MN or the execution condition configuration is unreasonable.

[0491] For MN triggered S-CPAC, the MN sends a message to the source SN of the corresponding CPC, and the source SN performs cause analysis. The cause analysis is performed the same as in step 1202. The source SN is the source SN corresponding to the subsequent CPC. The message sent by the MN to the source SN includes MN UE XnAP ID, SN UE XnAP ID, SCG failure information, S-CPAC configuration, SN mobility information, source PSCell cell identity, and / or failed PSCell cell identity. The SCG failure information is the SCG failure information received from the UE. The S-CPAC configuration can be all or part of the configuration information of the S-CPAC received by the MN from the source SN in the S-CPAC preparation process. The SN mobility information is the information related to PSCell change received by the MN from the source SN, used for analysis of the case of erroneous PSCell change. The message sent by the MN to the source SN can be SCG failure information report or other message.

[0492] For MN triggered S-CPAC, in case of failure due to subsequent S-CPAC, if the suitable PSCell is not the one recommended by the MN, the MN needs to perform the related optimization, the source SN indicates to the MN the cause of SCG failure occurs in the MN, otherwise the source SN indicates to the MN the cause of SCG failure occurs in the other node. If the suitable PSCell is one of the candidate PSCells recommended by the MN but not one of the candidate or target SN selected candidate PSCells or the execution condition configuration is unreasonable, it is the failure caused by the candidate or target SN, the cause of SCG failure occurs in the other node, the target or candidate SN needs to perform the related optimization. The message sent by the source SN to the MN contains the MN UE XnAP ID, the SN UE XnAP ID, and the information of whether the cause of SCG failure occurs in the MN or the other candidate or target SN. Here, the failure due to subsequent S-CPAC can also be referred to as subsequent S-CPAC related failure. The MN receives the message from the source SN, if the cause of SCG failure occurs in the MN, the MN performs the corresponding optimization, if the cause of SCG failure occurs in the other node (candidate or target SN), the MN sends a message to the candidate or target SN, the message contains the same information as in step 304, which will not be repeated here. The message can be an SCG failure information report or other message, which is not limited by the present application.

[0493] For MN triggered S-CPAC, in case of failure due to subsequent S-CPAC, another method is that if the suitable PSCell is not the one recommended by the source SN, the source SN needs to perform the related optimization, otherwise the source SN indicates to the MN the cause of SCG failure occurs in the other node. The source SN sends a message to the MN to indicate to the MN the cause of SCG failure occurs in the other node. If the suitable PSCell is one of the candidate PSCells recommended by the source SN but not one of the candidate or target SN selected candidate PSCells or the execution condition configuration is unreasonable, it is the failure caused by the candidate or target SN, the cause of SCG failure occurs in the other node, the target or candidate SN needs to perform the related optimization. The message sent by the source SN to the MN contains the MN UE XnAP ID and the SN UE XnAP ID. Here, the failure due to subsequent S-CPAC can also be referred to as subsequent S-CPAC related failure. The MN receives the message from the source SN, and the MN sends a message to the candidate or target SN, the message contains the same information as in step 304, which will not be repeated here. The message can be an SCG failure information report or other message, which is not limited by the present application.

[0494] So far, the sixth method of supporting self-configuration and self-optimization of the present application is completed, which can support the robustness of PSCell change in enhanced mobile process, for example, in S-CPAC, correctly identify the cause of failure occurrence, make reasonable optimization, reduce the occurrence of failure, ensure service continuity, and reduce the labor cost of operators.

[0495] The seventh method of supporting self-configuration and self-optimization of the present application is shown in the following example. Figure 14 The method is used in the scenario of failure occurring in the process of SN triggered S-CPAC. The method comprises the following steps:

[0496] In step 1401, the MN receives SCG failure information from the UE. The information contained in the SCG failure information is the same as that in step 302, which will not be repeated here.

[0497] In step 1402, the MN performs initial analysis. The MN determines the type of PSCell change or addition.

[0498] For SN triggered S-CPAC, the MN sends a message to the SN that initiates S-CPAC. The MN knows that it is SN triggered S-CPAC according to the saved information or according to the SCG failure information received from the UE, for example, the MN knows that it is SN triggered S-CPAC according to the indication information of MN triggered S-CPAC or SN triggered S-CPAC contained in the SCG failure information. The SN that initiates S-CPAC is the source SN of the initial S-CPAC. The message contains one or more of the following information elements:

[0499] Source PSCell cell identity;

[0500] Destination PSCell cell identity or failed PSCell cell identity;

[0501] Suitable PSCell cell identity;

[0502] SCG failure information received from the UE;

[0503] Candidate PSCell list recommended by the MN or the initial SN; each candidate PSCell contains a cell identity, which can be a global cell identity, and the global cell identity can also contain a tracking area code (TAC);

[0504] Initial S-CPAC execution condition, for each candidate PSCell cell, there is one or more execution conditions;

[0505] Subsequent S-CPAC execution condition, for each candidate PSCell cell, there is one or more execution conditions;

[0506] A list of candidate PSCells for target SN or candidate target SN selection; each candidate PSCell contains a cell identity, which can be a global cell identity, which can further contain a tracking area code (TAC). The message can contain a list of candidate PSCells for target SN or candidate target SN selection, or by containing indication information in the list of candidate PSCells recommended by the MN or source SN whether the candidate PSCells are selected by the target SN or candidate target SN, the target SN or candidate target SN knows which candidate PSCells in the list of candidate PSCells recommended by the MN or source SN are selected by the target SN or candidate target SN and which candidate PSCells are not selected by the target SN or candidate target SN according to the indication information in the list of candidate PSCells recommended by the MN or source SN;

[0507] A list of PSCells not selected by the target SN or candidate target SN in the list of candidate PSCells recommended by the MN or initial SN;

[0508] A maximum number of prepared PSCells;

[0509] An estimated arrival probability;

[0510] An SCG failure time.

[0511] The message can be an SCG failure information report or other message.

[0512] Step 1403: The SN initiating S-CPAC performs cause analysis. The cause analysis is the same as that in step 1202.

[0513] If the suitable PSCell is not one of the candidate PSCells recommended by the SN initiating S-CPAC or is one of the candidate PSCells recommended by the SN initiating S-CPAC but is not one of the candidate PSCells selected by the candidate or target SN, it is a failure caused by unsuitable candidate PSCell configuration, otherwise it is a failure caused by unsuitable execution condition. The SN initiating S-CPAC 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 sends it to the SN initiating S-CPAC through the SCG failure information report message or other message described above.

[0514] For the initial S-CPAC of SN initiated S-CPAC, if the suitable PSCell is one of the candidate PSCells recommended by the SN initiating the S-CPAC but not one of the candidate PSCells selected by the candidate or target SN, the SN initiating the S-CPAC indicates to the MN the cause of SCG failure is at other nodes, otherwise the SN initiating the S-CPAC performs the corresponding optimization. The MN sends the SCG failure information report to the candidate or target SN after receiving the message from the SN initiating the S-CPAC, the message contains the same information as in step 304, and the candidate or target SN performs the corresponding optimization.

[0515] For the subsequent S-CPAC of SN initiated S-CPAC, if the suitable PSCell is not recommended by the SN initiating the S-CPAC, the SN initiating the S-CPAC performs the related optimization, otherwise the SN initiating the S-CPAC indicates to the MN the cause of SCG failure is at other nodes. If the suitable PSCell is one of the candidate PSCells recommended by the SN initiating the S-CPAC but not one of the candidate PSCells selected by the candidate or target SN or the execution condition configuration is unreasonable, it is the failure caused by the candidate or target SN, and the target or candidate SN needs to perform the related optimization. The MN sends the SCG failure information report to the candidate or target SN after receiving the message from the SN initiating the S-CPAC, the message contains the same information as in step 304, and the candidate or target SN performs the corresponding optimization. Here, the subsequent S-CPAC of SN initiated S-CPAC refers to the failure caused by the subsequent S-CPAC or the failure related to the subsequent S-CPAC.

[0516] The SN initiating the S-CPAC knows whether it is the initial S-CPAC or the subsequent S-CPAC according to the saved information or according to the indication information of the initial S-CPAC failure or the subsequent S-CPAC failure in the SCG failure information received from the UE.

[0517] The candidate SN also contains the source SN of the subsequent S-CPAC.

[0518] So far, the seventh method of supporting self-configuration and self-optimization of the application is completed, which can support the robustness of PSCell change in the enhanced mobile process, for example, in S-CPAC, correctly identify the cause of failure occurrence, perform reasonable optimization, reduce the occurrence of failure, ensure service continuity, and reduce the labor cost of operators.

[0519] An example of the eighth method of supporting self-configuration and self-optimization of the application is shown in the following table. Figure 15 The method is used in the scenario of failure occurring in the process of SN triggered S-CPAC. The method comprises the steps of:

[0520] At step 1501, the MN receives the SCG failure information from the UE. The information contained in the SCG failure information is the same as that in step 302, which will not be repeated here.

[0521] At step 1502, the MN performs the initial analysis. The MN determines the type of PSCell change or addition.

[0522] For SN triggered S-CPAC, the MN sends a message to the SN that initiated the S-CPAC, the SN that initiated the S-CPAC performs the cause analysis, the MN sends a message to the source SN of the corresponding subsequent CPC procedure, and the corresponding source SN performs the cause analysis. The failure due to the initial S-CPAC can also be referred to as the failure related to the initial S-CPAC. The cause analysis is the same as that in step 1202. The MN knows that it is SN triggered S-CPAC according to the saved information or according to the SCG failure information received from the UE, for example, the MN knows that it is SN triggered S-CPAC according to the indication information of the MN triggered S-CPAC or the SN triggered S-CPAC contained in the SCG failure information. The MN knows whether it is the initial S-CPAC or the subsequent S-CPAC according to the saved information or according to the indication information of the initial S-CPAC failure or the subsequent S-CPAC failure in the SCG failure information received from the UE.

[0523] The information contained in the message sent by the MN to the SN that initiated the S-CPAC or the source SN of the candidate CPC procedure is the same as that in step 1402, which will not be repeated here.

[0524] The SN that initiated the S-CPAC receives the message from the MN, and the behavior of the SN that initiated the S-CPAC is the same as that described in step 1403, which will not be repeated here.

[0525] The source SN of the subsequent S-CPAC receives the message from the MN and performs the cause analysis. If the appropriate PSCell is not recommended by the source SN, the source SN performs the related optimization, otherwise the source SN indicates to the MN that the cause of the SCG failure is in another node, and the MN sends the SCG failure information report message to the candidate or target SN. The MN sending the message to the node that needs to perform the related optimization or the MN sending the SCG failure information report message to the candidate or target SN is the same as that described in step 1203, which will not be repeated here. If the appropriate PSCell is one of the candidate PSCells recommended by the source SN but not one of the candidate PSCells selected by the candidate or target SN or the execution condition configuration is unreasonable, the candidate or target SN needs to perform the corresponding optimization.

[0526] For SN triggered S-CPAC, due to the failure caused by the subsequent S-CPAC, the MN sends a message to the source SN of the corresponding CPC, and the source SN performs cause analysis. The source SN is the source SN corresponding to the subsequent CPC. The message sent by the MN to the source SN contains the same information as in step 1302. The message sent by the MN to the source SN can be an SCG failure information report or other messages.

[0527] For SN triggered S-CPAC, due to the failure caused by the subsequent S-CPAC, another method is: if the appropriate PSCell is not recommended by the SN that initiates the S-CPAC, the relevant optimization is performed by the SN that initiates the S-CPAC, the source SN indicates to the MN that the cause of the SCG failure occurs in the SN that initiates the S-CPAC, otherwise the source SN indicates to the MN that the cause of the SCG failure occurs in the candidate or target SN. If the appropriate PSCell is one of the candidate PSCells recommended by the SN that initiates the S-CPAC but not one of the candidate PSCells selected by the candidate or target SN or the execution condition configuration is unreasonable, it is the failure caused by the candidate or target SN, the cause of the SCG failure occurs in the candidate or target SN, and the target or candidate SN needs to perform the relevant optimization. The message sent by the source SN to the MN contains the MN UE XnAP ID, the SN UE XnAP ID, and the information of whether the cause of the SCG failure occurs in the SN that initiates the S-CPAC or other candidate or target SN. Here, the failure caused by the subsequent S-CPAC can also be referred to as the failure related to the subsequent S-CPAC. The MN receives the message from the source SN, and if the cause of the SCG failure occurs in the SN that initiates the S-CPAC, the MN sends a message to the SN that initiates the S-CPAC, and if the cause of the SCG failure occurs in other nodes (candidate or target SN), the MN sends a message to the candidate or target SN, and the message contains the same information as in step 304, which is not described here. The message can be an SCG failure information report or other messages, which are not limited by the present application.

[0528] So far, the eighth method of supporting self-configuration and self-optimization of the present application is completed, which can support the robustness of PSCell change in the enhanced mobile process, for example, in S-CPAC, correctly identify the cause of the failure to occur, perform reasonable optimization, reduce the occurrence of failure, ensure service continuity, and reduce the labor cost of operators.

[0529] It should be noted that the subsequent S-CPAC in the present application can also be referred to as the subsequent CPC or the subsequent CPC of the S-CPAC process, and the subsequent S-CPAC can also be referred to as the subsequent CPC or the subsequent CPC of the S-CPAC process. The source SN of the subsequent S-CPAC can also be referred to as the source SN of the subsequent CPC or the corresponding source SN of the subsequent CPC of the S-CPAC process, which refers to the source SN in the subsequent CPC process of the S-CPAC.

[0530] Figure 12 And Figure 14 The methods of steps 1202 and 1203 in the method of Figure 12 Or steps 1403 and 1404 in the method of Figure 14 .

[0531] Figure 12 And Figure 15 The methods of steps 1202 and 1203 in the method of Figure 12 Or steps 1502 in the method of Figure 15 .

[0532] Figure 13 And Figure 14 The methods of steps 1302 in the method of Figure 13 Or steps 1403 and 1404 in the method of Figure 14 .

[0533] Figure 13 And Figure 15 The methods of steps 1302 in the method of Figure 13 Or steps 1502 in the method of .

[0534] Figure 16 A block diagram of a network node in a network according to the present application.

[0535] The network node in the network can be used to implement the MN, SN, S-SN, T-SN, other candidate T-SN, etc. in the present application. For reference Figure 16The network node according to the present application comprises a transceiver 1610, a controller 1620 and a memory 1630. The transceiver 1610, the controller 1620 and the memory 1630 are configured to perform the operations of the method and / or embodiments of the present application. Although the transceiver 1610, the controller 1620 and the memory 1630 are shown as separate entities, they can be implemented as a single entity, like a single chip. The transceiver 1610, the controller 1620 and the memory 1630 can be electrically connected or coupled to each other. The transceiver 1610 can transmit signals to and receive signals from other network nodes, e.g. a UE, a MN, a SN, a S-SN, a T-SN, a candidate T-SN or a core network node. The controller 1620 can comprise one or more processing units and can control the network node to perform operations and / or functions according to one of the above embodiments. The memory 1630 can store instructions for implementing operations and / or functions of one of the above embodiments.

[0536] Figure 17 Block diagram of a user equipment, UE, according to the present application.

[0537] Reference Figure 17 The UE according to the present application comprises a transceiver 1710, a controller 1720 and a memory 1730. The transceiver 1710, the controller 1720 and the memory 1730 are configured to perform the operations of the method and / or embodiments of the present application. Although the transceiver 1710, the controller 1720 and the memory 1730 are shown as separate entities, they can be implemented as a single entity, like a single chip. The transceiver 1710, the controller 1720 and the memory 1730 can be electrically connected or coupled to each other. The transceiver 1710 can transmit signals to and receive signals from other network nodes, e.g. a UE, a MN, a SN, a S-SN, a T-SN, a candidate T-SN or a core network node. The controller 1720 can comprise one or more processing units and can control the UE to perform operations and / or functions according to one of the above embodiments. The memory 1730 can store instructions for implementing operations and / or functions of one of the above embodiments.

[0538] Those skilled in the art will appreciate that the above described illustrative embodiments are described herein and are not intended to be limiting. It should be understood that any two or more of the disclosed embodiments herein can be combined in any combination. In addition, other embodiments can be utilized and other changes can be made without departing from the spirit and scope of the subject matter presented herein. It will be readily understood to those skilled in the art that the various aspects of the present disclosure, as generally described herein, and illustrated in the Figures, can be arranged, substituted, combined, separated, and designed in various different configurations, all of which are contemplated herein.

[0539] Those of skill would understand that the various illustrative logical blocks, modules, circuits, and steps described in connection with the disclosure herein can be implemented as hardware, software, or combinations thereof. To clearly illustrate this interchangeability of hardware and software, various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system. Skilled artisans can implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present disclosure.

[0540] The various illustrative logical blocks, modules, and circuits described in connection with the disclosure herein can be implemented or performed 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 device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor can be a microprocessor, but in the alternative, the processor can be any conventional processor, controller, microcontroller, or state machine. A processor can also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.

[0541] The steps of a method or algorithm described in connection with the disclosure herein can be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. A software module can reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, a removable disk, or any other form of storage medium known in the art. An exemplary storage medium is coupled to the processor such that the processor can read information from, and write information to, the storage medium. In the alternative, the storage medium can be integral to the processor. The processor and the storage medium can reside in an ASIC. The ASIC can reside in a user terminal. In the alternative, the processor and the storage medium can reside as discrete components in a user terminal.

[0542] In one or more exemplary designs, the functions described can be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, the functions can be stored on or transmitted over as one or more instructions or code on a computer-readable medium. Computer-readable media include both computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A storage media can be any available media that can be accessed by a general purpose or special purpose computer.

[0543] The above description is intended to be illustrative and not restrictive. Many other examples will be apparent to those of skill in the art upon reading the above description. The scope of the application should, therefore, be determined not with reference to the above description, but instead with reference to the appended claims, along with their full scope of equivalents.

Claims

1. A method performed by a first network node of a communication system, comprising: receiving first information including failure related information from a user equipment UE, where the failure is related to a secondary cell group SCG; determining the network node that caused the failure based at least on the failure-related information, The failure-related information includes at least one of the following: The subsequent conditional primary and secondary cells PSCell add or change S-CPAC related information, Cell identification information related to PSCell, Information related to the SCG and / or master cell group MCG.

2. The method according to claim 1, further comprising: An indication or report of the failure is sent to the node causing the failure or the second node.

3. The method according to claim 1, further comprising: Based on at least a portion of the failure-related information, a type of the failure is determined.

4. The method according to claim 1, further comprising: Forwarding information related to the failure to the node that caused the failure.

5. The method according to claim 1, wherein The subsequent information related to adding or changing the S-CPAC of the conditional primary and secondary cells (PSCells) includes at least one of the following: Indication of whether S-CPAC has been executed, Time from the implementation of S-CPAC to its failure, S-CPAC execution conditions, Time from when the UE receives the S-CPAC configuration to when it fails, The time from when the UE receives the S-CPAC configuration to when the S-CPAC is executed, S-CPAC execution conditions are met. Information on which S-CPAC execution condition is met first, The time between two S-CPAC execution conditions being met, S-CPAC instructions, Initial S-CPAC execution conditions, The subsequent S-CPAC execution conditions, An indication of an initial S-CPAC failure or a subsequent S-CPAC failure; or The cell identification information related to the PSCell includes at least one of the following: Failed PSCell cell identifier, The source PSCell cell identifier of the most recent PSCell change, A list of candidate PSCells for S-CPAC; or The information related to the SCG and / or MCG includes at least one of the following: The status of the SCG, SCG failure time, The status of MCG.

6. The method according to claim 2, wherein: The failure indication or report information includes at least one of the following: Source PSCell cell ID, Destination PSCell cell ID or failed PSCell cell ID, Appropriate PSCell cell identifier, SCG failure information received from UE, The candidate PSCell list recommended by the MN or source SN, Initial S-CPAC execution conditions, The subsequent S-CPAC execution conditions, The candidate PSCell list selected by the target SN or candidate target SN, The candidate PSCell list recommended by the MN or source SN does not have a PSCell list accepted by the destination SN or candidate destination SN. The maximum number of PSCells to prepare, Estimated probability of arrival, SCG failure time, Type of failure.

7. A method performed by a first network node of a communication system, comprising: At least one of the first configuration information, the second configuration information, the third configuration information, and the fourth configuration information of sending a successful primary / secondary cell (PSCell) change report to the user equipment UE; Receive information from the UE indicating that a successful PSCell change report is available, The successful PSCell change report includes one or more of the following: Timing information associated with successful PSCell change reporting, Identification information related to the primary cell, source PSCell, and destination PSCell related to the PSCell change, The reasons for the changes in successful PSCell, Clock-related information configured by the first node, Time information related to changes in PSCell, UE mobility information, Information about the node that initiated the PSCell change.

8. The method according to claim 7, further comprising: Sending a request for a successful PSCell change report to the first node, Receive a successful PSCell change report from the UE.

9. The method according to claim 7, further comprising: The first configuration information of a successful PSCell change report is received from the second node.

10. The method according to claim 7, further comprising: The third configuration information and / or the fourth configuration information of the successful PSCell change report are received from the third node.

11. The method according to claim 8, further comprising: Send information about successful PSCell change report to the fifth node, The fifth node is determined based on a successful PSCell change report.

12. The method according to claim 1, in, The first configuration information includes at least one of a successful primary / secondary cell change report configuration triggered by clocks T310 and / or T312 and a successful primary / secondary cell change report configuration triggered by clock T304; or The second configuration information includes a report configuration of a successful primary / secondary cell change triggered by clock T310 and / or T312, or The third configuration information includes a report configuration of a successful primary / secondary cell change triggered by clock T310 and / or clock T312, or The fourth configuration information includes a report configuration of a successful primary / secondary cell change triggered by clock T304.

13. A method performed by a first network node of a communication system, comprising: receiving a message from a user equipment UE including information about a primary secondary cell (PSCell) selected by the UE, Sending the secondary cell group (SCG) history information including the user equipment (UE) to the target secondary node, The SCG history information of the UE includes information of PSCells arranged in chronological order.

14. The method according to claim 13, in, The UE's SCG history information is sent via the secondary node reconfiguration complete message. The PSCell information includes at least one of the following: PSCell identification information, UE's residence time information, Cell type information.

15. The method according to claim 13, wherein: The UE's SCG history information is used to detect whether there is a problem with the PSCell change.

16. A method performed by a user equipment (UE) of a communication system, comprising: The UE saves information related to a failure, where the failure is related to the secondary cell group (SCG); sending first information including failure related information to the first network node, The failure-related information includes at least one of the following: The subsequent conditional primary and secondary cells PSCell add or change S-CPAC related information, Cell identification information related to PSCell, Information related to the SCG and / or master cell group MCG.

17. A method performed by a user equipment (UE) of a communication system, comprising: receiving at least one of the first configuration information, the second configuration information, the third configuration information, and the fourth configuration information of a successful primary / secondary cell (PSCell) change report from the first network node; Sending information indicating that a successful PSCell change report is available to the first network node, The successful PSCell change report includes one or more of the following: Timing information associated with successful PSCell change reporting, Identification information related to the primary cell, source PSCell, and destination PSCell related to the PSCell change, The reasons for the changes in successful PSCell, Clock-related information configured by the first node, Time information related to changes in PSCell, UE mobility information, Information about the node that initiated the PSCell change.

18. A method performed by a user equipment (UE) of a communication system, comprising: Select the target primary and secondary cell PSCell; Sending a message including information about the target PSCell selected by the UE to the first network node, In response to the information about the primary and secondary cells (PSCells) selected by the UE, the UE's secondary cell group (SCG) history information is sent to the destination secondary node. The SCG history information of the UE includes information of PSCells arranged in chronological order.

19. A first network node device in a communication system, comprising: a transceiver configured to receive and transmit signals; as well as A processor is coupled to the transceiver and configured to control the network node device to perform the method according to any one of claims 1-6, or the method according to any one of claims 7-12, or the method according to any one of claims 13-15.

20. A user equipment (UE) in a communication system, comprising: a transceiver configured to receive and transmit signals; as well as A processor is coupled to the transceiver and configured to control the UE to perform the method according to any one of claims 16-18.

Images