CN117479245A

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

Info

Publication number: CN117479245A
Application number: CN202310364343.5A
Authority: CN
Inventors: 许丽香; 汪巍崴; 王弘
Original assignee: Samsung Electronics Co Ltd
Current assignee: Samsung Electronics Co Ltd
Priority date: 2022-07-27
Filing date: 2023-04-06
Publication date: 2024-01-30
Also published as: WO2024025349A1

Abstract

The application provides a method and a device for supporting self-configuration self-optimization, wherein the method executed by a first network node of a communication system comprises the following steps: receiving information related to SCG failure of a secondary cell group from User Equipment (UE); and sending the first failure report information to the second network node.

Description

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

Technical Field

The present application relates to wireless communication technology, and in particular, to a method and apparatus for supporting self-configuration self-optimization.

Background

In order to meet the increasing demand for wireless data communication services since the deployment of 4G communication systems, efforts have been made to develop improved 5G or quasi 5G communication systems. Therefore, a 5G or quasi 5G communication system is also referred to as a "super 4G network" or a "LTE-after-system".

Wireless communication is one of the most successful innovations in modern history. Recently, the number of subscribers to wireless communication services exceeds 50 billion and continues to grow rapidly. As smartphones and other mobile data devices (e.g., tablet computers, notebook computers, netbooks, e-book readers, and machine type devices) become increasingly popular among consumers and businesses, the demand for wireless data services is rapidly growing. To meet the high-speed growth of mobile data services and support new applications and deployments, it is important to improve the efficiency and coverage of the wireless interface.

Disclosure of Invention

For enhanced mobility schemes, how to support mobility robustness in the dual connectivity procedure is a problem that needs to be addressed at present.

According to an aspect of the present disclosure, there is provided a method performed by a first network node of a communication system, comprising: receiving information related to SCG failure of a secondary cell group from User Equipment (UE); and sending the first failure report information to the second network node.

According to an embodiment of the present disclosure, further comprising: sending second failure report information to a third network node; receiving third failure report information from a third network node, wherein the third failure report information is in response to the second failure report information sent to the third network node; wherein the first failure report information sent to the second network node is sent based on the third failure report information.

According to an embodiment of the present disclosure, the second network node is a network node bringing about the SCG failure.

According to an embodiment of the present disclosure, further comprising: based on the SCG failure related information, judging the network node bringing the failure and/or the type of the failure.

According to an embodiment of the present disclosure, wherein the first failure report information or the second failure report information includes at least one of the following information: the method comprises the steps of a source primary secondary cell PSCell cell identifier, a target PSCell cell identifier, a failed PSCell cell identifier, a proper PSCell cell identifier, information related to SCG failure received from UE, a candidate PSCell list recommended by a primary network node or a source secondary network node, a condition PSCell changing CPC executing condition, a candidate PSCell list selected by the target network node or the candidate target network node, estimated arrival possibility, failure type, proper but not selected PSCell cell identifier of the target network node or the candidate target network node and indication information of improper selected candidate PSCell.

According to an embodiment of the present disclosure, the third failure report information includes at least one of the following information: the method comprises the steps of identifying an MN UE AP ID by a main network node UE access protocol, identifying an SN UE AP ID by a secondary network node UE access protocol, recommending a candidate primary and secondary cell PSCell list by a source secondary network node, selecting a candidate PSCell list by a target secondary network node or a candidate target network node, identifying a proper PSCell cell, information related to SCG failure, identifying a source PSCell cell, identifying a target PSCell cell, identifying a proper PSCell cell which is not selected by a target network node or a candidate target network node, and indicating information that the selected candidate PSCell is not proper.

According to an embodiment of the present disclosure, further comprising: receiving, from a second network node, modification requirement information of the second network node, wherein the modification requirement information comprises at least one of: the candidate primary and secondary cells PSCell list, the conditional primary and secondary cells change CPC execution conditions, and the maximum number of pscells.

According to an embodiment of the present disclosure, further comprising: receiving information about a second network node triggering a cell change procedure from the second network node, wherein the information about the second network node triggering the cell change procedure comprises at least one of: the second network device triggers information of the CPC process of the conditional primary and secondary cells, a candidate primary and secondary cell PScell list, and CPC execution conditions.

According to an embodiment of the present disclosure, the SCG failure related information includes at least one of: the method includes the steps of a primary and secondary cell changing indication information of whether CPC is executed, time from CPC execution to failure, primary and secondary cell PSCell cell identification of failure, source PSCell cell identification of last PSCell change, cell list of CPC candidate PSCell, CPC execution condition, time from UE to failure receiving CPC configuration, time from UE to CPC execution, indication information of which CPC execution condition is satisfied corresponding to the CPC execution condition when one CPC execution condition is satisfied for execution, information of which CPC execution condition is satisfied first, time between two CPC execution conditions are satisfied, CPC or indication information of CPA added by a primary and secondary cell, information about the state of SCG, and information about the state of a primary cell group MCG.

According to another aspect of the present disclosure, there is provided a method performed by a second network node of a communication system, comprising: transmitting an RRC reconfiguration message including a conditional primary and secondary cell change CPC configuration to User Equipment (UE); first failure report information is received from a first network node.

According to an embodiment of the disclosure, the received first failure report information is sent by the first network node based on third failure report information sent by a third network node in response to second failure report information sent by the first network node to the third network node.

According to an embodiment of the present disclosure, the third failure report information includes at least one of the following information: the method comprises the steps of identifying an MN UE AP ID by a main network node UE access protocol, identifying an SN UE AP ID by an auxiliary network node UE access protocol, recommending a candidate primary and auxiliary cell PSCell list by a source auxiliary network node, selecting a candidate PSCell list by a target auxiliary network node or a candidate target network node, identifying a proper PSCell cell, information related to SCG failure, identifying a source PSCell cell, identifying a target PSCell cell, identifying a proper PSCell cell which is not selected by a target network node or a candidate target network node, and indicating information that the selected candidate PSCell is not proper.

According to an embodiment of the present disclosure, further comprising: transmitting modification requirement information of the second network node to the first network node, wherein the modification requirement information comprises at least one of the following information: the candidate primary and secondary cells PSCell list, the conditional primary and secondary cells change CPC execution conditions, and the maximum number of pscells.

According to an embodiment of the present disclosure, further comprising: transmitting information about a second network node triggering a cell change procedure to a first network node, wherein the information about the second network node triggering the cell change procedure comprises at least one of: the secondary network node triggers information of the CPC process of the conditional primary and secondary cells, a candidate primary and secondary cell PScell list and CPC execution conditions.

According to another aspect of the present disclosure, there is provided a method performed by a first network node of a communication system, comprising: transmitting an RRC reconfiguration message including a conditional primary and secondary cell change CPC configuration configured by a first network node to User Equipment (UE); information is received from the second network node regarding completion of CPC execution of the second network node configuration.

According to an embodiment of the present disclosure, the information about completion of CPC execution of the second network node configuration includes at least one of the following information: UE identity, PScell identity, and indication information to cancel CPC.

According to an embodiment of the present disclosure, the second network node receives from the UE indication information that the first network node is CPC configured.

According to another aspect of the present disclosure, there is provided a method performed by a second network node of a communication system, comprising: transmitting an RRC reconfiguration message including a conditional primary and secondary cell change CPC configuration configured by the second network node to the user equipment UE; information is sent to the first network node regarding completion of CPC execution configured by the second network node.

According to an embodiment of the present disclosure, further comprising: indication information is received from the UE that the first network node is CPC configured.

According to another aspect of the present disclosure, there is provided a network node in a communication system, comprising a transceiver configured to transmit and receive signals; and a controller coupled with the transceiver and configured to perform operations in the method as described in the present disclosure.

By the method for supporting self-configuration and self-optimization, the robustness of primary and secondary cell (PSCell) switching in the enhanced moving process can be supported. Further, by the method for supporting self-configuration self-optimization, the reason of failure can be ensured to be correctly identified, so that reasonable optimization is performed, the failure is reduced, the service continuity is ensured, and the labor cost of operators is reduced.

Drawings

FIG. 1 is a system architecture diagram of System Architecture Evolution (SAE);

FIG. 2 is a schematic diagram of an initial overall architecture of FIG. 5G;

FIG. 3 is a flow chart of a method one according to an embodiment of the present invention;

FIG. 4 is a schematic diagram of a first method according to an embodiment of the invention;

FIG. 5 is a schematic diagram of a second method according to an embodiment of the present invention;

FIG. 6 is a schematic diagram of a method III according to an embodiment of the invention;

FIG. 7 is a schematic diagram of a method four according to an embodiment of the invention;

FIG. 8 is a schematic diagram of a fifth method according to an embodiment of the invention;

fig. 9 is a block diagram of a network device according to an embodiment of the present invention.

Detailed Description

For the purpose of making the objects, technical solutions and advantages of the embodiments of the present disclosure more apparent, the technical solutions of the embodiments of the present disclosure will be clearly and completely described below with reference to the accompanying drawings of the embodiments of the present disclosure. It will be apparent that the described embodiments are some, but not all, of the embodiments of the present disclosure. All other embodiments, which can be made by one of ordinary skill in the art without the need for inventive faculty, are within the scope of the present disclosure, based on the described embodiments of the present disclosure.

Before proceeding with the description of the detailed description that follows, it may be advantageous to set forth definitions of certain words and phrases used throughout this patent document. The term "couple" and its derivatives refer to any direct or indirect communication between two or more elements, whether or not those elements are in physical contact with one another. The terms "transmit," "receive," and "communicate," and derivatives thereof, encompass both direct and indirect communication. The terms "include" and "comprise," as well as derivatives thereof, are intended to be inclusive and not limited to. The term "or" is inclusive, meaning and/or. The phrase "associated with" and its derivatives are intended to include, be included within, be connected to, be interconnected with, be included within, be connected to or be connected with, be coupled to or be coupled with, be able to communicate with, be co-operative with, be interwoven with, be juxtaposed with, be proximate to, be bound to or be in relation to, be bound to, be provided with an · attribute, be provided with an · relationship or be provided with a relationship with the · and the like. The term "controller" means any device, system, or portion thereof that controls at least one operation. Such a controller may be implemented in hardware, or in a combination of hardware and software and/or firmware. The functionality associated with any particular controller may be centralized or distributed, whether locally or remotely. At least one of the phrases "..when used with a list of items means that different combinations of one or more of the listed items can be used and that only one item in the list may be required. For example, "at least one of A, B and C" includes any one of the following combinations: 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 any one of the following combinations: A. b, C, A and B, A and C, B and C, and a and B and C.

Furthermore, the various functions described below may be implemented or supported by one or more computer programs, each of which is formed from computer readable program code and embodied in a computer readable medium. 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 portions thereof adapted for implementation 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 (Random Access Memory, RAM), a hard disk drive, a Compact Disc (CD), a Digital Video Disc (DVD), or any other type of Memory. "non-transitory" computer-readable media exclude wired, wireless, optical, or other communication links that transmit transitory electrical or other signals. Non-transitory computer readable media include media that can permanently store data and media that can store and later rewrite data, such as rewritable optical disks or erasable memory devices.

The terminology used herein to describe embodiments of the present application is not intended to limit and/or define the scope of the present application. For example, unless defined otherwise, technical or scientific terms used in this disclosure should be given the ordinary meaning as understood by one of ordinary skill in the art to which this application belongs.

It should be understood that the terms "first," "second," and the like, as used in this disclosure, do not denote any order, quantity, or importance, but rather are used to distinguish one element from another. The singular forms "a," "an," or "the" and similar terms do not denote a limitation of quantity, but rather denote the presence of at least one, unless the context clearly dictates otherwise.

As used herein, any reference to "one example" or "an example," "one embodiment," or "an embodiment" means that a particular element, feature, structure, or characteristic described in connection with the embodiment 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.

As used herein, a "portion of an item" means at least some of the item, and thus may mean less than all of the item or all of the item. Thus, a "portion of an object" includes the entire object as a special case, i.e., the entire object is an example of a portion of an object.

It will be further understood that the terms "comprises" and "comprising," and the like, when used in this specification, specify the presence of stated features and advantages, but do not preclude the presence of other features and advantages, and that the terms "comprising" and "include" specify the presence of stated features and advantages, but rather than preclude the presence of other features and advantages. The terms "connected" or "connected," and the like, are not limited to physical or mechanical connections, but may include electrical connections, whether direct or indirect. "upper", "lower", "left", "right", etc. are used merely to indicate relative positional relationships, which may also be changed when the absolute position of the object to be described is changed.

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 disclosure. Those skilled in the art will understand that the principles of the present disclosure may be implemented in any suitably arranged wireless communication system. For example, although the following detailed description of embodiments of the present disclosure will be directed to LTE and 5G communication systems, it will be appreciated by those skilled in the art that the main gist of the present disclosure may be applied to other communication systems having similar technical contexts and channel formats with slight modifications without substantially departing from the scope of the present disclosure. The technical solution of the embodiments of the present application may be applied to various communication systems, for example, the communication systems may include a global system for mobile communications (global system for mobile communications, GSM) system, a code division multiple access (code division multiple access, CDMA) system, a wideband code division multiple access (wideband code division multiple access, WCDMA) system, a general packet radio service (general packet radio service, GPRS), a long term evolution (long term evolution, LTE) system, an LTE frequency division duplex (frequency division duplex, FDD) system, an LTE time division duplex (time division duplex, TDD), a general mobile communication system (universal mobile telecommunication system, UMTS), a worldwide interoperability for microwave access (worldwide interoperability for microwave access, wiMAX) communication system, a fifth generation (5th generation,5G) system, or a New Radio (NR), etc. In addition, the technical scheme of the embodiment of the application can be applied to future-oriented communication technologies. In addition, the technical scheme of the embodiment of the application can be applied to future-oriented communication technologies.

The following description with reference to the accompanying drawings is provided to facilitate a thorough understanding of the various embodiments of the present disclosure as defined by the claims and their equivalents. The description includes various specific details to facilitate understanding but should be considered exemplary only. Accordingly, one of ordinary skill 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 may be omitted for clarity and conciseness.

The terms and phrases used in the following specification and claims are not limited to their dictionary meanings, but are used only by the inventors to enable a clear and consistent understanding of the disclosure. Accordingly, it should be apparent to those skilled in the art that the following descriptions of the various embodiments of the present disclosure are provided for illustration only and not for the purpose of limiting the disclosure as defined by the appended claims and their equivalents.

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 such surfaces.

The terms "comprises" or "comprising" may refer to the presence of a corresponding disclosed function, operation or component that may be used in various embodiments of the present disclosure, rather than to the presence of one or more additional functions, operations or features. Furthermore, the terms "comprises" or "comprising" may be interpreted as referring to certain features, numbers, steps, operations, constituent elements, components, or combinations thereof, but should not be interpreted as excluding the existence of one or more other features, numbers, steps, operations, constituent elements, components, or combinations thereof.

The term "or" as used in the various embodiments of the present disclosure includes any listed term and all combinations thereof. For example, "a or B" may include a, may include B, or may include both a and B.

Unless defined differently, all terms (including technical or scientific terms) used in this disclosure have the same meaning as understood by one of ordinary skill in the art to which this disclosure pertains. The general terms as defined in the dictionary are to be construed to have meanings consistent with the context in the relevant technical field, and should not be interpreted in an idealized or overly formal manner unless expressly so defined in the present disclosure.

Figures 1 through 9, discussed below, and the various embodiments used to describe 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 disclosure. Those skilled in the art will appreciate that the principles of the present disclosure may be implemented in any suitably arranged system or device.

Fig. 1 is an exemplary system architecture 100 for System Architecture Evolution (SAE). A User Equipment (UE) 101 is a terminal device for receiving data. An evolved universal terrestrial radio access network (E-UTRAN) 102 is a radio access network including macro base stations (enodebs/nodebs) providing an access radio network interface for UEs. The Mobility Management Entity (MME) 103 is responsible for managing the UE's mobility context, session context and security information. Serving Gateway (SGW) 104 mainly provides the functions of the user plane, and MME 103 and SGW 104 may be in the same physical entity. The packet data network gateway (PGW) 105 is responsible for charging, lawful interception, etc. functions, and may also be in the same physical entity as the SGW 104. A 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 in the Universal Mobile Telecommunications System (UMTS) that provides a route for the transmission of data. A Home Subscriber Server (HSS) 109 is a home subsystem of the UE and is responsible for protecting user information including the current location of the user equipment, the address of the service node, user security information, packet data context of the user equipment, etc.

Fig. 2 is an exemplary system architecture 200 according to various embodiments of the present disclosure. Other embodiments of the system architecture 200 can be used without departing from the scope of this disclosure.

A User Equipment (UE) 201 is a terminal device for receiving data. The next generation radio access network (NG-RAN) 202 is a radio access network including base stations (gnbs or enbs connected to a 5G core network 5GC, also called NG-gnbs) providing access radio network interfaces for UEs. An access control and mobility management function (AMF) 203 is responsible for managing the mobility context of the UE, and security information. The User Plane Function (UPF) 204 mainly provides the functions of the user plane. The session management function entity SMF205 is responsible for session management. The Data Network (DN) 206 contains services such as operators, access to the internet, and third party traffic, among others.

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

The text and drawings are provided as examples only to aid in the understanding of the present disclosure. They should not be construed as limiting the scope of the disclosure in any way. While certain embodiments and examples have been provided, it will be apparent to those of ordinary skill in the art from this disclosure that variations can be made to the embodiments and examples shown without departing from the scope of the disclosure.

In order to improve the reliability of primary and secondary cell (PSCell, spCell of secondary cell group (primary cell of primary or secondary cell group, primary cell of a master or secondary cell group), spCell of a secondary cell group) change, a conditional PSCell change (CPC, conditional PSCell Change) is defined in the current technology. CPC is internal to a Secondary Node (SN). Furthermore, the CPC procedure between the conditions PSCell increase (CPA, conditional PSCell Addition) and SN is further defined in the current art. Unreasonable configuration or triggering of the CPA or CPC procedure may also cause the secondary cell group (SCG, secondary Cell Group) to fail. How to identify the type of failure for reasonable optimization is a problem that needs to be addressed at present.

In an embodiment according to the invention, a recommended candidate primary secondary cell (PSCell) list, CPC execution conditions, a selected candidate PSCell list, type of CPC failure, and/or estimated likelihood of arrival (Arrival Probability) may be included in the secondary cell group failure information report (SCG Failure Information Report).

In an embodiment according to the invention, CPC execution conditions may be included in the secondary node modification requirements (SN Modification Required).

In the embodiment according to the present invention, the SN informs the Master Node (MN) of indication information that the SN triggered the CPC procedure, and the SN may also inform the MN of the candidate PSCell list configured by the SN and CPC execution conditions.

In an embodiment according to the invention, the secondary cell group failure transfer (SCG Failure Transfer) by the SN to the MN may comprise a candidate PSCell list recommended by the Source SN (S-SN, source SN), a candidate PSCell list selected by the destination SN (T-SN, target SN) or candidate destination SN, a suitable PSCell cell identity, SCG failure information, a Source PSCell cell identity, a destination PSCell cell identity, a suitable PSCell cell identity but not selected by the destination SN or candidate destination SN, and/or an indication that the selected candidate PSCell is unsuitable.

In an embodiment according to the invention, the secondary cell group failure information (SCG Failure information) may contain information see steps 301, 409, 607, 706, 809.

It should be noted that, in the present invention, CPC is taken as an example to describe the present invention, and the problems and methods described in the present invention are also applicable to the CPA process. When the CPA is suitable for CPA, CPC is replaced by CPA. Likewise, the problems and methods described in the present invention are equally applicable to processes that condition PSCell increase or change (CPAC, conditional PSCell Addition or Change), where appropriate with CPAC instead of CPC.

In addition, the term "list" is used in the present invention to represent one form of representation of information, but the present invention is not limited to the list of information, and the list of information in the present invention may be represented in various other forms. For example, a cell list may represent information about one or more cells, but is not limited to the form of a list.

An example of a method one of the present invention supporting self-configuration self-optimization is shown in fig. 3. The method is described from the perspective of the master base station. The method comprises the following steps:

in step 301, the primary node receives information from the UE that the secondary cell group failed.

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

-information indicating whether CPC or CPA was performed;

-time from CPC or CPA execution to failure;

-failed PSCell cell identity. The cell identity may be a global cell identity, or information of a physical cell identity and a frequency. The global cell identity may also contain a tracking area code TAC (Tracking Area Code) or tracking area identity of the cell; for failures in the PSCell change procedure, the failed PSCell cell identity is the cell identity of the destination PSCell.

-a source PSCell cell identity of a last PSCell change. The cell identity may be a global cell identity, or information of a physical cell identity and a frequency. The method can also comprise a tracking area code TAC or a tracking area identifier of the cell;

cell list of CPC or CPA candidate PSCell. The list of candidate CPC or CPA cells may be directly contained, or indication information that is a CPC or CPA candidate cell is contained in the measurement result for a cell that is a CPC or CPA candidate cell, and one or more CPC or CPA candidate cells that are CPC or CPA candidate cells but are not in the measurement result are contained in the secondary cell group failure information. Each candidate PSCell contains a cell identity, which may be a global cell identity. The cell identity may also contain a tracking area code TAC;

CPC or CPA execution conditions. CPC or CPA execution conditions may be one or more. For each candidate PSCell cell, there are one or more execution conditions;

-time from the UE receipt of CPC or CPA configuration to failure;

-time from reception of CPC or CPA configuration by UE to CPC execution;

-when a CPC or CPA execution condition is satisfied for execution, indication information corresponding to the CPC or CPA execution condition being satisfied for execution;

-information of which CPC or CPA execution conditions are satisfied first;

the time between the satisfaction of two CPC or CPA execution conditions, for example the time may be the time difference between the satisfaction of two CPC or CPA execution conditions;

-indication information of CPC or CPA, the indication information being indication information that CPC or CPA is configured;

the state of the SCG, e.g. whether the SCG is active or inactive, e.g. SCG suspension (Suspend);

the state of the master cell group MCG (Master Cell Group), e.g. whether MCG is active or inactive, and again e.g. MCG is suspended.

The failure described above may be an SCG failure, but the present invention is not limited thereto, and may be other types of failures occurring in a secondary cell.

In step 302, the master node decides which node is the failure. For example, whether the master node is a source or destination or other candidate. In addition, the master node can also directly forward SCG failure information to the secondary node where failure occurs.

The master node decides which node is the failure based on the information in the SCG failure information received from the UE and/or the information stored by the MN.

The master node may also determine the type of failure occurrence, e.g., too early a PSCell change, too late a PSCell change, or trigger a PSCell change to the wrong PSCell.

If the UE fails SCG after a PSCell has been in progress for a long period of time, e.g., the UE does not report time from CPC execution to failure occurrence or the time from CPC execution to failure occurrence reported by the UE is greater than a configured threshold, there is an appropriate PSCell other than the PSCell in which the UE was in progress for failure, then CPC execution is too late. The MN knows the appropriate PSCell from the measurement report received from the UE, or the MN knows the appropriate PSCell from the measurement report received from the UE and the information the MN maintains.

Too early PSCell changes: there is a recent CPC execution or PSCell change before failure occurs, e.g., the source PSCell is the appropriate PSCell, then it is too early a PSCell change, based on an indication of CPC execution or based on the time the CPC begins execution until failure occurs less than a configured threshold. The MN or the source node triggering the PSCell change knows the appropriate PSCell from the measurement report received from the UE, or the MN or the source node triggering the PSCell change knows the appropriate PSCell from the measurement report received from the UE and the information saved by the MN or the source node triggering the PSCell change. The SCG failure may be a failure occurring shortly after a successful change from the source PSCell to the destination PSCell or a failure occurring during a PSCell change. The source PSCell is the last time the PSCell was changed.

Too early CPA execution, failure of CPA execution or failure of SCG occurring soon after successful CPA execution, no suitable PSCell is known from measurement reports received from the UE, or from measurement reports received from the UE and information held by the node. For example, a CPA execution that is too early may be performed without a suitable PScell, based on an indication of CPA execution or based on the time that the CPA begins execution until failure occurs being less than a configured threshold. The MN knows that there is no suitable PSCell from the measurement report received from the UE, or the MN knows that there is no suitable PSCell from the measurement report received from the UE and the information the MN maintains.

Triggering a PSCell change to the wrong PSCell: there is a recent CPC execution or PSCell change before failure occurs, e.g., according to an indication of CPC execution or according to the time the CPC starts execution until failure occurs is less than a configured threshold, and the appropriate PSCell is not the source PSCell or the destination PSCell, but triggers the PSCell to change to the wrong PSCell. The MN knows the appropriate PSCell from the measurement report received from the UE, or the MN knows the appropriate PSCell from the measurement report received from the UE and the information the MN maintains. The SCG failure may be a failure occurring shortly after a successful change from the source PSCell to the destination PSCell or a failure occurring during a PSCell change. The source PSCell is the last time the PSCell was changed. The target PSCell is the last time the PSCell was changed.

For too late a PSCell change, MN and source SN are nodes that bring about failure.

For too early a PSCell change, if the PSCell change is triggered by the MN, the MN is the node that brought the failure. If the PSCell change is triggered by the source SN, the source SN is the node that brings the failure. Corresponding to too early CPA execution, the MN is the node that brings failure.

For triggering a PSCell change to a false PSCell, if the PSCell change is triggered by the MN, the MN is the node that brought the failure. If the PSCell change is triggered by the source SN, the source SN is the node that brings the failure.

For triggering a PSCell change to the wrong PSCell, the MN may further determine whether the CPC candidate cell configuration is unreasonable or if the CPC execution condition configuration is unreasonable. If the appropriate cell is not among the CPC candidate cells configured for the UE, it is a failure due to unreasonable CPC candidate cell configuration. If the appropriate cell is not in the CPC candidate cell list recommended by the source base station (MN or source SN) that triggered the PSCell change, it is a problem with the source base station that triggered the PSCell change, for example, if the PSCell change is MN triggered, it is a problem with the MN if the PSCell change is source SN triggered. If the appropriate cell is in the CPC candidate cell list recommended by the source base station (MN or source SN) that triggered the PSCell change, but not in the candidate PSCell list selected by the destination SN or candidate destination SN, it is a failure by the destination SN or candidate destination SN.

The MN or source SN may also determine whether it is a failure due to an improper set of estimated likelihood of arrival. For example, the estimated arrival likelihood that the MN or source SN sends to the candidate destination SN through the MN is set too low, resulting in the destination SN or the candidate SN not selecting the candidate cell as the selected candidate cell or not timely allocating appropriate resources to the candidate cell, and the appropriate cell is the candidate SN, where the MN or source SN is the node that caused the failure. If it is the estimated arrival likelihood decided by the source SN, it is the failure by the source SN.

The MN or source SN may also determine whether it is a failure due to improper setting of the maximum number of pscells to be prepared. For example, the maximum number of prepared pscells that a MN or source SN sends to a candidate destination SN through the MN is too low, resulting in the destination SN or candidate SN not selecting the appropriate cell as the selected candidate cell, and the appropriate cell is the candidate SN, where the MN or source SN is the node that caused the failure. If the maximum number of prepared PSCells is determined by the source SN, the failure is caused by the source SN.

The above-described PSCell for triggering PSCell change to error is described by taking CPC as an example, and is equally applicable to the CPA process.

If the MN is the node that brings the failure, step 303 need not be performed. If it is a problem with the source SN, destination SN or candidate destination SN, step 303 is performed.

In step 303, the master node sends an indication or report of the failure of the secondary cell group to the node that brought the failure. The failing node may be the source SN, the destination SN, or a candidate SN.

From the description in step 302, the MN knows that it is a source SN, destination SN, or candidate destination SN that has failed.

The MN may send the secondary cell group failure information to the problematic node via a secondary cell group failure information report message or other message.

The message sent by the master node to the node with the problem contains one or more of the following information elements:

a source PScell cell identity;

a destination PSCell cell identity or a failed PSCell cell identity;

a suitable PSCell cell identity;

SCG failure information received from the UE;

a list of candidate PSCell recommended by MN or source SN; each candidate PSCell contains a cell identity, which may be a global cell identity, which may also contain a tracking area code TAC;

CPC execution conditions; for each candidate PSCell cell, there are one or more execution conditions;

A list of candidate PSCell selected by the destination SN or candidate destination SN; each candidate PSCell contains a cell identity, which may be a global cell identity, which may also contain a tracking area code TAC. The message may include a candidate PSCell list selected by the destination SN or the candidate destination SN, or the destination SN or the candidate destination SN knows which of the candidate PSCell list recommended by the MN or the source SN are candidate pscells accepted by the destination SN or the candidate destination SN and which are candidate pscells not accepted by the destination SN or the candidate destination SN according to the indication information in the candidate PSCell list recommended by the MN or the source SN;

a PSCell list which is not accepted by the target SN or the candidate target SN in the candidate PSCell list recommended by the MN or the source SN;

the maximum number of pscells prepared;

estimated likelihood of arrival;

the type of failure includes too early a PSCell change, too late a PSCell change, triggering a PSCell change to the wrong PSCell, improper CPC candidate cell configuration, improper CPC execution conditions, improper maximum number of prepared pscells, and/or improper estimated likelihood of arrival configuration. This information is included when the MN determines the type of failure, and if it is the type of failure for SN determination that causes a problem, this information element is not included.

If the MN only judges which node brings about the failure, the source SN, the destination SN or the candidate SN judges the type of the failure after receiving the message from the MN. Such as too early a PSCell change, too late a PSCell change, or triggering a PSCell change to the wrong PSCell cell.

If the UE fails SCG after a PSCell has been in progress for a long period of time, e.g., the UE does not report time from CPC execution to failure occurrence or the time from CPC execution to failure occurrence reported by the UE is greater than a configured threshold, there is an appropriate PSCell other than the PSCell in which the UE was in progress for failure, then CPC execution is too late. The SN knows the appropriate PSCell from the measurement report received from the UE, or the SN knows the appropriate PSCell from the measurement report received from the UE and the information the SN maintains. The measurement report received from the UE is received through SCG failure information received from the UE by the MN.

Too early PSCell changes: there is a recent CPC execution or PSCell change before failure occurs, e.g., the source PSCell is the appropriate PSCell, then it is too early a PSCell change, based on an indication of CPC execution or based on the time the CPC begins execution until failure occurs less than a configured threshold. The SN knows the appropriate PSCell from the measurement report received from the UE, or the SN knows the appropriate PSCell from the measurement report received from the UE and the information the SN maintains. The SCG failure may be a failure occurring shortly after a successful change from the source PSCell to the destination PSCell or a failure occurring during a PSCell change. The source PSCell is the last time the PSCell was changed. The measurement report received from the UE is received through SCG failure information received from the UE by the MN.

Triggering a PSCell change to the wrong PSCell: there is a recent CPC execution or PSCell change before failure occurs, e.g., according to an indication of CPC execution or according to the time the CPC starts execution until failure occurs is less than a configured threshold, and the appropriate PSCell is not the source PSCell or the destination PSCell, but triggers the PSCell to change to the wrong PSCell. The SN knows the appropriate PSCell from the measurement report received from the UE, or the SN knows the appropriate PSCell from the measurement report received from the UE and the information the SN maintains. The SCG failure may be a failure occurring shortly after a successful change from the source PSCell to the destination PSCell or a failure occurring during a PSCell change. The source PSCell is the last time the PSCell was changed. The target PSCell is the last time the PSCell was changed. The measurement report received from the UE is received through SCG failure information received from the UE by the MN.

The source SN may further determine whether the CPC candidate cell is configured unreasonably or fails due to an unreasonable CPC execution condition configuration. If the appropriate cell is not among the CPC candidate cells configured for the UE, it is a failure due to unreasonable CPC candidate cell configuration. If the appropriate cell is not in the CPC candidate cell list recommended by the source SN that triggered the PSCell change, it is a problem with the source SN that triggered the PSCell change. If the appropriate cell is in the CPC candidate cell list recommended by the source SN that triggered the PSCell change, but not in the candidate PSCell list selected by the destination SN or candidate destination SN, it is a failure by the destination SN or candidate destination SN. For triggering a PSCell change to the wrong PSCell, the source SN may further determine if it is a failure due to unreasonable candidate cell configuration. The source SN may determine whether the maximum number of pscells prepared is unsuitable, and/or the estimated likelihood of arrival configures unsuitable failures.

For failures caused by the target SN or the candidate target SN, there are two methods in the present invention for indicating the failure to the target SN or the candidate target SN:

mode one: the MN determines whether it is a destination SN or a candidate destination SN, and the specific method is as described in step 302. The MN sends an indication or report of SCG failure to the destination SN or candidate destination SNs. The message includes a list of candidate PSCell recommended by the MN or the source SN, indication information accepted by the destination SN or the candidate destination SN in the list of candidate PSCell recommended by the MN or the source SN, indication information not accepted by the destination SN or the candidate destination SN in the list of candidate PSCell recommended by the MN or the source SN, a maximum number of prepared pscells, a list of candidate pscells selected by the destination SN or the candidate destination SN, a suitable PSCell cell identification, SCG failure information, a source PSCell cell identification, a destination PSCell cell identification, a failed PSCell cell identification, a suitable PSCell cell identification but not selected by the destination SN or the candidate destination SN, and/or indication information that the selected candidate PSCell is unsuitable. The SCG failure information is SCG failure information received from the UE. Each candidate PSCell contains a cell identity, which may be a global cell identity, which may also contain a tracking area code TAC.

Mode two: the MN sends an indication or report of SCG failure to the source SN, which further determines the type of failure. If the source SN determines that it is a problem with the destination SN or candidate destination SNs, the source SN sends a message to the MN. The message sent by the source SN to the MN includes an Access Protocol (AP) identifier of the MN UE, an AP ID of the SN UE, a candidate PSCell list recommended by the source SN, indication information accepted by the destination SN or the candidate destination SN in the candidate PSCell list recommended by the source SN, indication information not accepted by the destination SN or the candidate destination SN in the candidate PSCell list recommended by the source SN, a maximum number of prepared pscells, a candidate PSCell list selected by the destination SN or the candidate destination SN, a suitable PSCell cell identifier, SCG failure information, a source PSCell cell identifier, a destination PSCell cell identifier, a failed PSCell cell identifier, a suitable PSCell cell identifier not selected by the destination SN or the candidate destination SN, and/or indication information not suitable for the selected candidate PSCell. Each candidate PSCell contains a cell identity, which may be a global cell identity. The global cell identity may also contain a tracking area code TAC. The source SN may send this information to the MN via an SCG failover message or other message. The MN sends a message to the destination SN or the candidate destination SN, where the message includes the same information as in the first mode, and will not be described herein.

The source SN may also determine if it is a failure due to an improper set of estimated likelihood of arrival, e.g., the estimated likelihood of arrival of the source SN sent to the candidate destination SN by the MN is set too low, and the appropriate cell is the candidate SN, at which point the source SN is the node that caused the failure. The source SN may also determine whether it is a failure due to improper setting of the maximum number of pscells to be prepared. For example, the maximum number of prepared pscells that the source SN sends to the candidate destination SN through the MN is too low, resulting in the destination SN or candidate SN not selecting the appropriate cell as the selected candidate cell, and the appropriate cell is the candidate SN, which is the node that caused the failure.

Nodes with failure (source SN, destination SN or candidate destination SN, or MN) reasonably optimize CPC.

The method for supporting self-configuration and self-optimization is completed, the robustness of PSCell change in the enhanced moving process can be supported, the cause of failure is correctly identified, reasonable optimization is performed, the failure is reduced, the service continuity is ensured, and the labor cost of operators is reduced.

An embodiment of a method one supporting self-configuration self-optimization is shown in fig. 4. The method comprises the following steps:

the UE is in a dual connectivity state, while connected to the MN and source SN (S-SN).

The s-SN sends an SN change need message to the MN, step 401. The message contains candidate destination node identifications. The message may also contain a list of candidate PSCell suggested by the source SN and CPC execution conditions, maximum number of pscells to prepare. This step need not be performed for MN-triggered CPC change procedures. Each candidate PSCell contains a cell identity, which may be a global cell identity. The global cell identity may also contain a tracking area code TAC. For each candidate PSCell cell, there are one or more execution conditions.

The MN saves information of the S-SN triggered CPC procedure.

The mn sends an SN addition request message to one or more destination SNs, step 402. The MN holds information whether the MN or S-SN triggered the CPC procedure.

In step 403, the destination SN or other candidate destination SNs send an SN add request acknowledgement message to the MN.

The mn sends a Radio Resource Control (RRC) reconfiguration message to the UE in step 404. The message contains a CPC configuration.

In step 405, the ue saves the CPC configuration and sends an RRC reconfiguration complete message to the MN. The RRC reconfiguration complete message is RRC reconfiguration complete.

The UE starts evaluating the execution conditions.

In step 406, if the execution condition of one candidate PSCell is satisfied, the UE applies an RRC reconfiguration message corresponding to the selected candidate PSCell. The UE sends an RRC reconfiguration complete message to the MN. The RRC reconfiguration complete message is RRC reconfiguration complete. The message contains information of the selected PSCell.

In step 407, the ue performs a random access procedure to the destination SN, synchronizing to the destination SN.

The UE may fail in executing the CPC to the destination SN, and step 407 may fail or may not need to execute in response to the CPC execution failure.

In step 408, scg failure occurs. The SCG failure may be a failure occurring when the UE performs CPC to the destination SN or a failure occurring after the procedure of step 407 is performed. The UE saves failure related information. The failure related information is information of the failure of the secondary cell group in step 301, and will not be described herein.

In step 409, the ue sends SCG failure information to the MN. The SCG failure information includes the same information as that described in step 301, and will not be described here again. The UE may send the SCG failure information in step 301 to the MN through an existing SCG failure information message or other RRC message.

The mn determines which node is the failure in step 410. The method of MN determination is the same as that in step 302, and will not be described here again. The MN may further determine the type of failure, and the specific determination method is the same as that in step 302, and will not be described here again.

If the MN fails, the process ends and subsequent steps do not need to be performed.

Step 411 is performed for problems with the source SN.

For problems with SN being destination or candidate destination, if it is a MN triggered PSCell change, step 413 is performed directly. For the problem caused by the SN being the destination or the candidate destination, if the PSCell is changed triggered by the source SN, corresponding to the first mode of the present invention (the first mode in step 303), step 413 is directly executed; step 411, step 412 and step 413 are executed corresponding to mode two of the present invention (mode two in step 303).

In step 411, the mn sends an 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 303, and will not be described here again. The message sent by the MN to the source SN may be an existing SCG failure information report or other message. If the failure type is determined by the source SN, the method of source SN determination is the same as described in step 303.

If the appropriate PSCell is recommended by the source SN and the destination SN or candidate destination SN does not select the appropriate PSCell as a candidate PSCell, step 412 is performed.

In step 412, the source SN sends an SCG failure indication or an SCG failover message to the MN, where the message includes the same information as the content sent by the source SN to the MN in step 303, and details are not repeated here. The source SN may send the information described in step 303 to the MN via an existing SCG failover message or other message.

In step 413, the mn sends an SCG failure information report to the destination SN or other candidate destination SNs. The SCG failure information report contains the same information as the information sent to the destination SN or other candidate destination SNs by the MN in step 303, and will not be described herein. The MN may send SCG failure information to the destination SN or other candidate destination SNs via an existing SCG failure information report or other message.

The description of the first embodiment of the method for supporting self-configuration and self-optimization is completed, the robustness of PSCell change in the enhanced moving process can be supported, the reasons of failure are correctly identified, reasonable optimization is performed, the failure is reduced, the service continuity is ensured, and the labor cost of operators is reduced.

For the CPC procedure, the present invention finds the following technical problems:

problem one: the SN triggers a CPC procedure through the signaling radio bearer (Signalling Radio Bearer) 3 (SRB 3), which does not go through the participation of the MN, which also triggers a CPC procedure from the source SN to the destination SN. In the scenario, after the UE successfully performs the CPC configured by SN, the UE may release the procedure of the CPC configured by MN. The UE sends an RRC reconfiguration complete message to the new PSCell of the SN. Resources of candidate pscells configured by the MN are also reserved, so that the resources cannot be released in time, and waste of radio resources is caused.

And a second problem: the SN triggers the CPC procedure through signaling radio bearer 3 (SRB 3), which does not go through the participation of the MN, which also triggers the CPC procedure from the source SN to the destination SN. If the UE fails in the CPC process of executing the SN configuration or the UE fails after executing the CPC of the SN configuration, the UE sends SCG failure information to the MN, the MN does not know that the SN triggers the CPC process, the MN does not have a candidate PSCell list of the CPC of the SN configuration and CPC executing conditions, if the MN judges which node fails or judges the type of failure according to the candidate PSCell list of the CPC process triggered by the MN and the CPC executing conditions, the judgment error can be caused, the purpose of network self-optimization is not achieved, and negative influence is brought to the network self-optimization.

The second method for supporting self-configuration and self-optimization is shown in fig. 5. This approach can solve problem one. The method comprises the following steps:

the UE is in a dual connectivity state, while connected to the MN and SN. For MN-initiated inter-SN CPC procedures, the SN is also the source SN (S-SN).

In step 501a, the SN sends an SN RRC reconfiguration message to the UE. The SN sends the message to the UE via SRB 3. The message contains a CPC configuration.

In step 501b, the ue starts evaluating CPC performance conditions for one or more candidate pscells. The UE maintains a connection with the source PSCell. The UE sends an RRC reconfiguration complete message to the SN. The UE sends the message to the SN via SRB 3.

The mn sends an SN addition request message to one or more candidate destination SNs, step 502 a. The MN holds information that the MN triggered the CPC procedure.

The destination SN or other candidate destination SN sends an SN add request acknowledgement message to the MN, step 502 b.

In step 502c, the mn sends an RRC reconfiguration message to the UE. The message contains a CPC configuration.

In step 502d, the ue saves the CPC configuration and sends an RRC reconfiguration complete message to the MN. The RRC reconfiguration complete message is RRC reconfiguration complete.

The UE starts evaluating CPC performance conditions for one or more candidate pscells configured by the MN.

The mn sends an Xn user plane address indication message to the source SN, step 502 e.

In step 503, the execution condition of at least one candidate PSCell configured by sn is satisfied, and the UE applies the stored configuration of the candidate PSCell selected correspondingly, and synchronizes to the candidate PSCell.

The UE releases other CPC configurations, including the CPC configuration of the MN configuration and/or the configuration of other CPCs of the SN configuration. In step 504, the ue sends an RRC reconfiguration complete message to the SN. The UE sends the message to the SN via SRB 3. The message contains indication that the MN is CPC configured. By including indication that the MN has configured CPC, the SN can be aware that the MN has also configured CPC procedures so that the SN can request the MN to timely release resources of one or more candidate pscells prepared by the MN.

The sn sends information to the MN that the UE has performed CPC through SRB3, step 505. The information contains a UE identity, which is a MN UE Xn AP ID and/or a SN UE Xn AP ID of the UE. The information contains a new PSCell identity. The information may also contain indication information to cancel the CPC. The SN may send the information of this step to the MN when knowing that the MN triggered the CPC procedure, or the SN always sends said information to the MN. The SN may know that the MN triggered the CPC procedure upon receipt of the Xn user plane indication message (e.g., the message in step 502 e), thereby sending the information of this step to the MN. The SN may also know that the MN triggered the CPC procedure by other means, for example, if the MN does not need to perform step 502e after receiving the RRC reconfiguration complete message of step 502d, the MN sends indication information that the CPC is triggered to the source SN, so that the SN knows that the MN also triggered the CPC procedure. The SN may also know that the MN triggered the CPC procedure through the UE, and corresponding to this method, the RRC reconfiguration complete message of step 504 includes information that the MN configured the CPC procedure.

The MN sends an SN release request message to one or more candidate SNs requesting release of the CPC.

The description of the second embodiment of the method for supporting self-configuration and self-optimization is completed, so that the robustness of PSCell change in the enhanced moving process can be supported, and the reserved wireless resources can be released in time.

The third method for supporting self-configuration and self-optimization is shown in fig. 6. The method can solve the second problem. A detailed description of steps irrelevant to the present invention is omitted here. The method comprises the following steps:

Steps 601a to 602e are the same as steps 501a to 502e, and will not be described again here.

The SN sends information to the MN that the SN triggered the CPC procedure, step 603. The message contains information that the SN triggered the CPC procedure, a list of candidate pscells, and/or CPC execution conditions. Each candidate PSCell contains a cell identity, which may be a global cell identity. The global cell identity may also contain a tracking area code TAC. For each candidate PSCell cell, there are one or more execution conditions. The SN may send the information to the MN when the CPC procedure is configured, or the SN may send the information to the MN when it knows that the MN also triggered the CPC procedure. The SN knows that the MN also triggered the CPC procedure by receiving the Xn user plane address indication message. If the Xn user plane address indicates that the message is not needed (e.g., no early (early) data forwarding is needed), the MN may send the MN-triggered CPC procedure information to the SN through other messages, e.g., the MN sends the MN-triggered CPC procedure information to the SN after receiving the RRC reconfiguration complete message of step 602d, so that the SN knows that the MN triggered CPC procedure. The SN may also know in other ways that the MN triggered the CPC procedure to send the information of step 603 without affecting the main content of the invention.

The SN in this step is also the source SN for MN to trigger SN changes.

In step 604, the execution condition of at least one candidate PSCell configured by sn is satisfied, and the UE applies the saved configuration of the corresponding selected candidate PSCell, and synchronizes to the candidate PSCell.

The UE releases other CPC configurations, including the CPC configuration of the MN configuration and/or the configuration of other CPCs of the SN configuration.

The SN in this step is also the source SN for MN to trigger SN changes.

In step 605, the ue sends an RRC reconfiguration complete message to the SN. The UE sends the message to the SN via SRB 3.

The SN in this step is also the source SN for MN to trigger SN changes.

In step 606, an scg failure occurs. The SCG failure may occur after the CPC to the SN is successful, or during the execution of the CPC to the SN, i.e., the CPC to the SN fails to execute. In the case that CPC execution corresponding to SN fails, the random access of step 604 may be failed or need not be performed, and step 605 need not be performed.

The UE saves the failed information. The failed information includes one or more of the following:

-list of candidate PSCell configured by SN. Each candidate PSCell contains a cell identity, which may be a global cell identity, which may also contain a tracking area code TAC;

-one or more CPC execution conditions of the SN configuration. For each candidate PSCell cell, there are one or more execution conditions;

-indication of CPC failure of SN configuration;

-information of which execution condition is fulfilled;

-information of which execution condition is fulfilled first;

the time between the satisfaction of the two execution conditions, for example the time may be the time difference between the satisfaction of the two CPC execution conditions;

-PSCell cell identity where failure occurs;

-cell identity of source PSCell;

-time from CPC execution to failure;

-time from receipt of CPC configuration to CPC execution. Time from CPC configuration of the received SN to CPC of the new PSCell to the SN, and/or time from CPC configuration of the received MN to candidate pscells to MN configuration;

-the MN is configured with indication information of the CPC procedure;

-a list of candidate PSCell configured by the MN. Each candidate PSCell contains a cell identity, which may be a global cell identity, which may also contain a tracking area code TAC;

-MN configured CPC execution conditions. For each candidate PSCell cell, there are one or more execution conditions;

-indication of CPC failure for MN configuration.

The failure information is SCG failure information.

In step 607, the ue sends SCG failure information to the MN. The SCG failure information contains one or more of the failure information saved in step 606.

The mn determines which node brings about the failure, step 608. If the MN receives the indication information of the CPC failure configured by the SN, the MN directly sends an SCG failure report message to the SN. The message contains SCG failure information received from the UE. The MN can also determine which node failed according to the method in step 302. The MN may know from the SN that the SN triggered the CPC procedure, the CPC candidate PSCell list, and/or the CPC execution conditions, via step 603. The MN may also know from the UE that the SN triggered the CPC procedure, the SN configured CPC candidate PSCell list, the SN configured CPC execution conditions, and/or the CPC failure of the SN, via step 607. Wherein the CPC failure of the SN includes a CPC execution failure to the SN or an SCG failure occurs after a CPC execution success to the SN. Each candidate PSCell contains a cell identity, which may be a global cell identity. A tracking area code TAC may also be included. For each candidate PSCell cell, there are one or more execution conditions.

If the MN judges that the SN brings failure, the MN cancels CPC process to other candidate SNs prepared by the MN, wherein the CPC process is the CPC process to the target candidate SN triggered and prepared by the MN. As another implementation of the present invention, the MN may reserve the CPC procedure prepared by the MN.

The mn sends an SCG failure information report to the SN, step 609. The message contains one or more of the following information elements:

a source PScell cell identity;

a target PSCell cell identity, where the target PSCell is at least one candidate PSCell configured by SN, and UE fails to perform CPC to the PSCell or fails to perform CPC after the execution is successful;

a suitable PSCell cell identity;

SCG failure information received from the UE;

a list of candidate PSCell configured by SN; each candidate PSCell contains a cell identity, which may be a global cell identity, which may also contain a tracking area code TAC;

the SN configures CPC execution conditions; for each candidate PSCell cell, there are one or more execution conditions.

The SN determines the type of failure after receiving the message from the MN. Such as too early a PSCell change, too late a PSCell change, or triggering a PSCell change to the wrong PSCell cell. The specific determination method is the same as that described in step 303, and will not be described here again.

The SN may further determine whether the CPC candidate cell is unreasonable in configuration or fails due to unreasonable CPC execution condition configuration. If the appropriate cell is not among the CPC candidate cells configured for the UE, it is a failure due to unreasonable CPC candidate cell configuration.

SN performs a reasonable optimization of CPC.

It should be noted that, in the method, except that the SNs in step 602a and step 602b are destination SNs or other candidate destination SNs, SNs in other steps are source SNs for triggering the CPC procedure by the MN.

The third description of the method for supporting self-configuration and self-optimization is completed, the robustness of PSCell change in the enhanced moving process can be supported, the reasons of failure are correctly identified, reasonable optimization is performed, the failure is reduced, the service continuity is ensured, and the labor cost of operators is reduced.

The invention supports a self-configuration self-optimization method four as shown in fig. 7. The method can solve the second problem. A detailed description of steps irrelevant to the present invention is omitted here. The method comprises the following steps:

Steps 701a to 702e are the same as steps 501a to 502e, and will not be repeated here.

In step 703, the execution condition of at least one candidate PSCell configured by sn is satisfied, and the UE applies the saved configuration of the corresponding selected candidate PSCell, and synchronizes to the candidate PSCell.

The UE releases other CPC configurations, including the CPC configuration of the MN configuration and/or the CPC configuration of other candidate pscells of the SN configuration.

The SN in this step is also the source SN for MN to trigger SN changes.

In step 704, the ue sends an RRC reconfiguration complete message to the SN. The UE sends the message to the SN via SRB 3.

The SN in this step is also the source SN for MN to trigger SN changes.

In step 705, an scg failure occurs. The SCG failure may occur after the CPC to the SN succeeds, or may occur in the process of performing the CPC to the SN, i.e., the candidate PSCell CPC to the SN fails to perform. In the case that CPC execution corresponding to SN fails, the random access of step 703 may be failed or need not be performed, and step 704 need not be performed.

The UE saves the failure information, and the saved failure information is one or more pieces of information included in the SCG failure information in step 706.

In step 706, the ue sends SCG failure information to the MN. The SCG failure information includes one or more of the following:

-list of candidate PSCell configured by SN. Each candidate PSCell contains a cell identity, which may be a global cell identity. A tracking area code TAC can also be included;

-indication of CPC failure of SN configuration;

-information of which execution condition is fulfilled;

-information of which execution condition is fulfilled first;

-PSCell cell identity where failure occurs;

-cell identity of source PSCell;

-time from CPC execution to failure;

-the MN is configured with indication information of the CPC procedure;

-a list of candidate PSCell configured by the MN. Each candidate PSCell contains a cell identity, which may be a global cell identity. A tracking area code TAC can also be included;

-indication of CPC failure for MN configuration.

In step 707, the mn determines which node brings about the failure. If the MN receives the indication information of the CPC failure configured by the SN, the MN directly sends an SCG failure report message to the SN. The message contains SCG failure information received from the UE. The MN can also determine which node failed according to the method in step 302.

The mn sends an SCG failure information report to the SN, step 708. The message contains one or more of the following information elements:

a source PScell cell identity;

a destination PSCell cell identity; the target PSCell is at least one of candidate PSCells configured by a source SN, and CPC of the UE to the PSCell fails to execute or fails after execution is successful;

a suitable PSCell cell identity;

SCG failure information received from the UE;

SN performs a reasonable optimization of CPC.

It should be noted that, in the method, except that the SNs in step 702a and step 702b are destination SNs or other candidate destination SNs, SNs in other steps are source SNs for triggering the CPC procedure by the MN.

The method for supporting self-configuration self-optimization is described, the robustness of PSCell change in the enhanced moving process can be supported, and the reasons of failure are correctly identified, so that reasonable optimization is performed, the failure is reduced, the service continuity is ensured, and the labor cost of operators is reduced.

The fifth method for supporting self-configuration and self-optimization is shown in fig. 8. A detailed description of steps irrelevant to the present invention is omitted here. The method comprises the following steps:

the SN sends an SN modification required message to the MN, step 801. The message includes an SN RRC reconfiguration message. The message contains a list of one or more candidate pscells. The message also contains CPC execution conditions. For each candidate PSCell cell, there are one or more execution conditions.

In step 802, the mn sends an RRC reconfiguration message to the UE. The MN forwards the SN RRC reconfiguration message to the UE.

In step 803, the ue sends an RRC reconfiguration complete message to the MN. The RRC reconfiguration complete message includes an SN RRC reconfiguration complete message.

The UE starts evaluating CPC performance conditions for one or more candidate pscells.

In step 804, the mn forwards the SN RRC reconfiguration complete message to the SN. The MN sends an SN RRC reconfiguration complete message to the SN through the SN modification confirmation message.

In step 805, if at least one CPC candidate PSCell meets a corresponding CPC implementation condition, the UE sends an uplink information transmission message to the MN. The message contains an RRC reconfiguration complete message to the selected destination PSCell. The uplink information transmission may also be referred to as uplink information transmission multiple radio access technology dual connectivity (MRDC).

The mn forwards the RRC reconfiguration complete message to the SN, step 806. The MN sends an RRC reconfiguration complete message to the SN through RRC transmission.

In step 807, the ue synchronizes to the selected candidate PSCell.

In step 808, the scg fails. The SCG failure may occur after the CPC execution is successful, or may occur during the CPC execution, that is, the CPC execution to the selected candidate PSCell fails, and the random access procedure of step 807 is failed or does not need to be performed.

The UE saves the failed information, and the specific saved failed information is one or more of the SCG failed information in step 809.

In step 809, the ue sends SCG failure information to the MN. The SCG failure information contains one or more of the following:

-indication of CPC failure of SN configuration;

-list of candidate PSCell configured by SN. Included is the latest candidate PSCell list configured for the UE, or the candidate PSCell list of measurement results in the candidate PSCell cell configured for the UE but not in the UE. Each candidate PSCell contains a cell identity, which may be a global cell identity, which may also contain a tracking area code TAC;

-SN configured CPC execution conditions. For each candidate PSCell cell, there are one or more execution conditions;

-information of which CPC execution conditions are fulfilled;

-time from CPC execution to failure;

-time from CPC configuration to failure;

-time from CPC configuration to CPC execution;

-information of which CPC execution condition was satisfied first;

-a time between the satisfaction of two events, for example, the event may be the CPC execution condition described above, the time may be a time difference between the satisfaction of two events;

-results of UE measurements. Including measurements of serving PSCell and neighbor pscells. The cell of the candidate PSCell configured by SN in the measurement result also contains indication information of the candidate PSCell. In response to this method, candidate pscells among candidate PSCell cells allocated to the UE but not the measurement result of the UE are included in the candidate PSCell list of SCG failure information.

The mn determines which node is the failure at step 810. If the MN receives the indication information of the CPC failure configured by the SN, the MN directly sends an SCG failure report message to the SN. The message contains SCG failure information received from the UE. The MN can also determine which node failed according to the method in step 302.

The mn sends an SCG failure information report to the SN, step 811. The message contains one or more of the following information elements:

a source PScell cell identity;

a destination PSCell cell identity; the target PSCell is one of candidate PSCells configured by a source SN, and CPC from the UE to the PSCell fails to execute or fails after execution is successful;

a suitable PSCell cell identity;

SCG failure information received from the UE;

a list of candidate PSCell configured by SN; each candidate PSCell contains a cell identity, which may be a global cell identity. A tracking area code TAC can also be included;

SN performs a reasonable optimization of CPC.

Fig. 9 is a block diagram of a node device in a network according to the present invention.

Node devices in the network may be used to implement MN, SN, S-SN, T-SN, other candidate T-SNs, etc. in the present invention. Referring to fig. 9, the network device according to the present invention includes a transceiver 910, a controller 920, and a memory 930. The transceiver 910, controller 920, and memory 930 are configured to perform the operations of the methods and/or embodiments of the present invention. Although transceiver 910, controller 920, and memory 930 are shown as separate entities, they may be implemented as a single entity, such as a single chip. The transceiver 910, the controller 920, and the memory 930 may be electrically connected or coupled to each other. The transceiver 910 may send and receive signals to and from other network node devices, such as UE, MN, SN, S-SN, T-SN, other candidate T-SNs, or core network nodes. The controller 920 may include one or more processing units and may control the network device to perform operations and/or functions according to one of the above-described embodiments. Memory 930 may store instructions for carrying out the operations and/or functions of one of the embodiments described above.

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

Those of skill in the art will appreciate that the various illustrative logical blocks, modules, circuits, and steps described herein may be implemented as hardware, software, or combinations of both. 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 may implement the described functionality in varying ways for each particular application, but such design decisions should not be interpreted as causing a departure from the scope of the present application.

The various illustrative logical blocks, modules, and circuits described herein may be implemented or performed with a general purpose processor, a digital signal processor (Digital Signal Processor, DSP), an application specific integrated circuit (Application Specific Integrated Circuit, ASIC), a field programmable gate array (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 may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. A processor may 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.

The steps of a method or algorithm described in connection with the disclosure herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. A software module may 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 the processor can read information from, and write information to, the storage medium. In the alternative, the storage medium may be integral to the processor. The processor and the storage medium may reside in an ASIC. The ASIC may reside in a user terminal. In the alternative, the processor and the storage medium may reside as discrete components in a user terminal.

In one or more exemplary designs, the functions described may be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium. Computer-readable media includes 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 may be any available media that can be accessed by a general purpose or special purpose computer.

The foregoing is merely exemplary embodiments of the present application and is not intended to limit the scope of the present application, which is defined by the appended claims.

Claims

1. A method performed by a first network node of a communication system, comprising:

receiving information related to SCG failure of a secondary cell group from User Equipment (UE);

and sending the first failure report information to the second network node.

2. The method of claim 1, further comprising:

sending second failure report information to a third network node;

receiving third failure report information from a third network node, wherein the third failure report information is in response to the second failure report information sent to the third network node;

Wherein the first failure report information sent to the second network node is sent based on the third failure report information.

3. The method according to any one of claim 1 to 2, wherein,

the second network node is a network node that brings the SCG failure.

4. The method of any one of claims 1 to 2, further comprising:

based on the SCG failure related information, judging the network node bringing the failure and/or the type of the failure.

5. The method of any of claims 1 to 4, wherein the first or second failure report information comprises at least one of:

source primary secondary cell PSCell cell identity,

the cell identity of the destination PSCell,

the cell identity of the failed PSCell,

a suitable PSCell cell identity is used for the cell,

the SCG failure related information received from the UE,

a list of candidate PSCell recommended by the primary or source secondary network node,

the condition PSCell changes the CPC execution condition,

a list of candidate pscells selected by the destination network node or candidate destination network nodes,

the estimated likelihood of arrival,

the type of failure is that of the type,

suitable PSCell cell identity but not selected by the destination network node or candidate destination network node, and

Indication that the selected candidate PSCell is unsuitable.

6. The method of any of claims 2 to 4, wherein the third failure report information includes at least one of:

the primary network node UE access protocol identifies the MN UE AP ID,

the secondary network node UE access protocol identifies the SN UE AP ID,

a list of candidate primary and secondary cells PSCell recommended by the source and secondary network nodes,

a list of candidate pscells selected by the destination secondary network node or candidate destination network node,

a suitable PSCell cell identity is used for the cell,

information about the failure of the SCG,

the cell identity of the source PSCell,

the cell identity of the destination PSCell,

indication that the selected candidate PSCell is unsuitable.

7. The method of any one of claims 1 to 4, further comprising:

receiving from the second network node modification requirement information of the second network node,

wherein the modification requirement information includes at least one of the following information:

a list of candidate primary and secondary cells pscells,

conditional primary and secondary cells change CPC execution conditions

Maximum number of pscells.

8. The method of any one of claims 1 to 4, further comprising:

Information is received from the second network node regarding the second network node triggering a cell change procedure,

wherein the information about the second network node triggering a cell change procedure comprises at least one of the following information:

the second network device triggers information that the primary and secondary cells change CPC procedures,

candidate primary and secondary cell PSCell list

CPC execution conditions.

9. The method of any one of claims 1 to 4, wherein the SCG failure related information comprises at least one of:

the primary and secondary cells are conditioned on indication information of whether CPC was performed,

the time from CPC execution to failure,

the failed primary and secondary cell PSCell cell identity,

the source PSCell cell identity of the last PSCell change,

a cell list of CPC candidate pscells,

the CPC execution condition is that,

from the time the UE receives the CPC configuration to failure,

the time from the reception of CPC configuration by the UE to CPC execution,

when one CPC execution condition is satisfied for execution, corresponding to the indication information that the CPC execution condition is satisfied for execution,

information of which CPC execution condition is satisfied first,

the time between the satisfaction of the two CPC execution conditions,

CPC or conditional primary and secondary cells increase the indication of CPA,

Information about the state of the SCG

Information about the state of the master cell group MCG.

10. A method performed by a second network node of a communication system, comprising:

transmitting an RRC reconfiguration message including a conditional primary and secondary cell change CPC configuration to User Equipment (UE);

first failure report information is received from a first network node.

11. The method according to claim 10,

wherein the received first failure report information is sent by the first network node based on third failure report information sent by a third network node in response to second failure report information sent by the first network node to the third network node.

12. The method of any of claims 10 to 11, wherein the first or second failure report information comprises at least one of:

source primary secondary cell PSCell cell identity,

the cell identity of the destination PSCell,

the cell identity of the failed PSCell,

a suitable PSCell cell identity is used for the cell,

the SCG failure related information received from the UE,

the condition PSCell changes the CPC execution condition,

the estimated likelihood of arrival,

the type of failure is that of the type,

indication that the selected candidate PSCell is unsuitable.

13. The method of any of claims 10 to 11, wherein the third failure report information includes at least one of:

the primary network node UE access protocol identifies the MN UE AP ID,

the secondary network node UE access protocol identifies the SN UE AP ID,

a suitable PSCell cell identity is used for the cell,

information about the failure of the SCG,

the cell identity of the source PSCell,

the cell identity of the destination PSCell,

suitable but non-selected PSCell cell identities of the destination network node or candidate destination network node,

indication that the selected candidate PSCell is unsuitable.

14. A method performed by a first network node of a communication system, comprising:

transmitting an RRC reconfiguration message including a conditional primary and secondary cell change CPC configuration configured by a first network node to User Equipment (UE);

Information is received from the second network node regarding completion of CPC execution of the second network node configuration.

15. A method performed by a second network node of a communication system, comprising:

transmitting an RRC reconfiguration message including a conditional primary and secondary cell change CPC configuration configured by the second network node to the user equipment UE;

information is sent to the first network node regarding completion of CPC execution configured by the second network node.