Configuration method, communication device, and storage medium

Abstract

This application discloses a configuration method, communication device, and storage medium. The configuration method includes: a network device sending a conditional reconfiguration message to enable a terminal device to configure the execution conditions for continuous CPC. This application's technical solution addresses the SN-initiated inter-SN continuous CPC scenario by proposing a method that supports configuring the execution conditions for continuous CPC without requiring RRC reconfiguration, thus meeting the scenario requirements.

Description

Technical Field

[0001] This application relates to the field of communication technology, specifically to a configuration method, communication device, and storage medium. Background Technology

[0002] According to R18 WID, the UE needs to support continuous CPC (Conditional PSCell Change) without requiring RRCreconfiguration (RadioResourceControlreconfiguration). This means that after CPC execution, the UE does not release the CPC candidate cell configuration but needs to maintain the CPC candidate cell list for the next CPC evaluation. Existing protocols stipulate that the UE uses condReconfigId (Conditional Reconfiguration Identifier) ​​to identify and maintain the CPC condition configuration and execution conditions for each candidate cell.

[0003] In conceiving and implementing this application, the inventors discovered that in SN-initiated inter-SN CPC (SPC handover) scenarios, the target PSCell (Primary SCG Cell) determines or generates CPC execution conditions for other candidate PSCells. To support continuous CPC without requiring RRC reconfiguration, a mechanism is needed to pre-configure the CPC execution conditions of the target PSCell for other candidate PSCells.

[0004] The preceding description is intended to provide general background information and does not necessarily constitute prior art. Invention Overview Technical solutions

[0005] The main objective of this application is to provide a configuration method, communication device, and storage medium that, for SNinitiated inter-SN continuous or subsequent CPC scenarios, supports configuring the execution conditions of continuous or subsequent CPC without requiring RRC reconfiguration.

[0006] This application proposes a configuration method applicable to network devices (such as base stations), comprising the following steps:

[0007] S20: Send a conditional reconfiguration message to enable the terminal device to configure the execution conditions for consecutive or subsequent CPCs.

[0008] Optionally, the conditional reconfiguration message includes conditional configurations for the target PSCell in the SN to other candidate PSCells.

[0009] Optionally, before step S20, the method further includes the following step:

[0010] S10: Determine or generate conditional reconfiguration messages based on configuration information.

[0011] Optionally, step S10 includes:

[0012] The first network node sends a secondary node modification request message to the candidate network node set;

[0013] The second network node in the candidate network node set determines or generates the conditional configuration and / or measurement configuration for other candidate PSCells based on the auxiliary node modification request message;

[0014] The second network node sends the conditional configuration and / or measurement configuration for other candidate PSCells to the first network node through the auxiliary node modification request confirmation message;

[0015] The first network node determines, generates, or updates the conditional reconfiguration message based on the secondary node's modification request confirmation message.

[0016] Optionally, the secondary node modification request message includes at least one of the following: SSB frequency information of other candidate PSCells, PCI information of other candidate PSCells, and conditional reconfiguration ID of other candidate PSCells.

[0017] Optionally, the conditional configuration determined or generated by the second network node for other candidate PSCells includes at least one of the following: conditional reconfiguration ID, CPC execution condition, and conditional RRC reconfiguration message.

[0018] Optionally, the conditional configuration determined or generated by the second network node for other candidate PSCells is associated with the conditional reconfiguration ID of those other candidate PSCells.

[0019] Optionally, if the second network node has not determined or generated conditional configurations for other candidate PSCells, the terminal device will not perform conditional evaluation on the other candidate PSCells when switching to the second network node.

[0020] Optionally, before the first network node sends the secondary node modification request message to the candidate network node set, it also includes:

[0021] The third network node requests resource allocation from the candidate network node set based on the auxiliary node change request message.

[0022] Optionally, the first network node is a candidate PSCell allocation condition reconfiguration ID for successfully allocated resources.

[0023] Optionally, the auxiliary node change request message includes at least one of the following: a recommended candidate PSCell list, the execution conditions corresponding to the recommended candidate PSCell, and the measurement configuration.

[0024] This application also proposes a configuration method applicable to terminal devices (such as mobile phones), including the following steps:

[0025] S30: Receive condition reconfiguration messages to configure execution conditions for consecutive or subsequent CPCs.

[0026] Optionally, the conditional reconfiguration message includes conditional configurations for the target PSCell in the SN to other candidate PSCells.

[0027] Optionally, the conditional reconfiguration message is determined or generated in the following manner:

[0028] The first network node sends a secondary node modification request message to the candidate network node set;

[0029] The second network node in the candidate network node set determines or generates the conditional configuration and / or measurement configuration for other candidate PSCells based on the auxiliary node modification request message;

[0030] The second network node sends the conditional configuration and / or measurement configuration for other candidate PSCells to the first network node through the auxiliary node modification request confirmation message;

[0031] The first network node determines, generates, or updates the conditional reconfiguration message based on the secondary node's modification request confirmation message.

[0032] Optionally, the auxiliary node modification request message includes at least one of the following: SSB frequency information of other candidate PSCells, PCI information of other candidate PSCells, and conditional reconfiguration ID of other candidate PSCells.

[0033] Optionally, the conditional configuration for other candidate PSCells determined or generated by the second network node includes at least one of the following:

[0034] Conditional reconfiguration ID, CPC execution condition, and conditional RRC reconfiguration message.

[0035] Optionally, the conditional configuration determined or generated by the second network node for other candidate PSCells is associated with the conditional reconfiguration ID of those other candidate PSCells.

[0036] Optionally, if the second network node has not determined or generated conditional configurations for other candidate PSCells, the terminal device will not perform conditional evaluation on the other candidate PSCells when switching to the second network node.

[0037] Optionally, after the terminal device performs CPC to switch to the target candidate PSCell, the condition configuration of the target PSCell is applied, the condition configurations of the other candidate PSCells are retained, and the execution conditions and / or condition RRC reconfiguration messages of the PSCell to the other candidate PSCells are updated according to the condition configuration of the target PSCell.

[0038] This application also provides a configuration device, including:

[0039] The sending module is used to send conditional reconfiguration messages to enable the terminal device to configure the execution conditions for consecutive or subsequent CPCs.

[0040] This application also proposes a configuration device, comprising:

[0041] The receiving module is used to receive conditional reconfiguration messages to configure the execution conditions for consecutive or subsequent CPCs.

[0042] This application also provides a communication device, including: a memory, a processor, and a configuration program stored in the memory and executable on the processor. When executed by the processor, the configuration program implements any of the configuration methods described above. The communication device mentioned in this application can be a terminal device (such as a smart terminal, specifically a mobile phone) or a network device (such as a base station); the specific meaning needs to be clarified in the context.

[0043] This application also provides a storage medium storing a computer program, which, when executed by a processor, implements the configuration method as described in any of the above embodiments.

[0044] In this application's technical solution, a conditional reconfiguration message is sent by the network device to enable the terminal device to configure the execution conditions for consecutive or subsequent CPCs. This application proposes a method for configuring the execution conditions of consecutive or subsequent CPCs without requiring RRC reconfiguration, specifically for SN-initiated inter-SN consecutive or subsequent CPC scenarios. Attached Figure Description

[0045] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application. To more clearly illustrate the technical solutions of the embodiments of this application, the drawings used in the description of the embodiments will be briefly introduced below. Obviously, those skilled in the art can obtain other drawings based on these drawings without any creative effort.

[0046] Figure 1A schematic diagram of the hardware structure of a mobile terminal to implement the various embodiments of this application;

[0047] Figure 2 A communication network system architecture diagram provided for an embodiment of this application;

[0048] Figure 3 A schematic diagram of the hardware structure of the controller 140 involved in the configuration method embodiment of this application;

[0049] Figure 4 A schematic diagram of the hardware structure of the network node 150 involved in the configuration method embodiment of this application;

[0050] Figure 5 This application embodiment provides a scenario interaction flowchart for configuring the execution conditions of consecutive or subsequent CPCs without requiring RRC reconfiguration, specifically for SN-initiated inter-SN continuous or subsequent CPC scenarios.

[0051] Figure 6 This is a schematic diagram illustrating the interaction process between the terminal device and the network device in the first embodiment of the configuration method of this application;

[0052] Figure 7 This is a schematic diagram illustrating the interaction process between the terminal device and the network device in the second embodiment of the configuration method of this application;

[0053] Figure 8 This is a schematic diagram of the interaction process between the terminal device and the network device in the third embodiment of the configuration method of this application;

[0054] Figure 9 This is a schematic diagram of the scene interaction process of the fourth embodiment of the configuration method of this application.

[0055] The realization of the objectives, functional features, and advantages of this application will be further explained in conjunction with the embodiments and with reference to the accompanying drawings. The accompanying drawings have illustrated specific embodiments of this application, which will be described in more detail below. These drawings and textual descriptions are not intended to limit the scope of the concept in any way, but rather to illustrate the concepts of this application to those skilled in the art through reference to specific embodiments.

[0056] Implementation methods of this application

[0057] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numbers in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this application. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this application as detailed in the appended claims.

[0058] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element. Furthermore, components, features, and elements with the same names in different embodiments of this application may have the same meaning or different meanings, the specific meaning of which must be determined by its interpretation in that specific embodiment or further in conjunction with the context of that specific embodiment.

[0059] It should be understood that although the terms first, second, third, etc., may be used herein to describe various information, such information should not be limited to these terms. These terms are used only to distinguish information of the same type from one another. For example, without departing from the scope of this document, first information may also be referred to as second information, and similarly, second information may also be referred to as first information. Depending on the context, the word "if," as used herein, may be interpreted as "when," "when," or "in response to determination." Furthermore, as used herein, the singular forms "a," "an," and "the" are intended to also include the plural forms unless the context indicates otherwise. It should be further understood that the terms "comprising," "including," indicate the presence of the stated feature, step, operation, element, component, item, kind, and / or group, but do not exclude the presence, occurrence, or addition of one or more other features, steps, operations, elements, components, items, kinds, and / or groups. The terms "or," "and / or," "including at least one of the following," etc., as used in this application, may be interpreted as inclusive, or mean any one or any combination thereof. For example, "including at least one of the following: A, B, C" means "any one of the following: A; B; C; A and B; A and C; B and C; A and B and C." Similarly, "A, B, or C" or "A, B, and / or C" means "any one of the following: A; B; C; A and B; A and C; B and C; A and B and C." Exceptions to this definition only occur when the combination of elements, functions, steps, or operations is inherently mutually exclusive in some way.

[0060] It should be understood that although the steps in the flowcharts of this application's embodiments are shown sequentially according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some of the steps in the figures may include multiple sub-steps or multiple stages. These sub-steps or stages are not necessarily completed at the same time, but can be executed at different times, and their execution order is not necessarily sequential, but can be performed alternately or in turn with other steps or at least a portion of the sub-steps or stages of other steps.

[0061] Depending on the context, the words “if” or “suppose” as used here can be interpreted as “when” or “in response to determination” or “in response to detection.” Similarly, depending on the context, the phrases “if determination” or “if detection (of the stated condition or event)” can be interpreted as “when determination” or “in response to determination” or “when detection (of the stated condition or event)” or “in response to detection (of the stated condition or event).”

[0062] It should be noted that step designations such as S10 and S20 are used in this document for the purpose of more clearly and concisely describing the corresponding content, and do not constitute a substantial limitation on the order. In specific implementation, those skilled in the art may execute S20 first and then S10, etc., but these should all be within the protection scope of this application.

[0063] It should be understood that the specific embodiments described herein are merely illustrative of this application and are not intended to limit this application.

[0064] In the following description, the use of suffixes such as "module," "part," or "unit" to denote elements is solely for the purpose of illustrative purposes and has no specific meaning in itself. Therefore, "module," "part," or "unit" may be used interchangeably.

[0065] The communication equipment mentioned in this application may be a terminal device (such as a mobile terminal, specifically a mobile phone) or a network device (such as a base station). The specific meaning needs to be clarified in the context.

[0066] Optionally, the terminal device can be implemented in various forms. For example, the terminal devices described in this application may include smart terminals such as mobile phones, tablets, laptops, handheld computers, personal digital assistants (PDAs), portable media players (PMPs), navigation devices, wearable devices, smart bracelets, pedometers, and fixed terminals such as digital TVs and desktop computers.

[0067] The following description will use a mobile terminal as an example. Those skilled in the art will understand that, apart from elements specifically designed for mobile purposes, the construction according to the embodiments of this application can also be applied to fixed-type terminals.

[0068] Please see Figure 1 This is a schematic diagram of the hardware structure of a mobile terminal implementing various embodiments of this application. The mobile terminal 100 may include: an RF (Radio Frequency) unit 101, a WiFi module 102, an audio output unit 103, an A / V (Audio / Video) input unit 104, a sensor 105, a display unit 106, a user input unit 107, an interface unit 108, a memory 109, a processor 110, and a power supply 111, etc. Those skilled in the art will understand that... Figure 1 The mobile terminal structure shown does not constitute a limitation on the mobile terminal. The mobile terminal may include more or fewer components than shown, or combine certain components, or have different component arrangements.

[0069] The following is combined Figure 1 A detailed introduction to each component of the mobile terminal:

[0070] The radio frequency unit 101 can be used for receiving and transmitting signals during information transmission or calls. Specifically, it receives downlink information from the base station and processes it with the processor 110; additionally, it transmits uplink data to the base station. Typically, the radio frequency unit 101 includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a low-noise amplifier, and a duplexer. Furthermore, the radio frequency unit 101 can also communicate wirelessly with networks and other devices. The aforementioned wireless communications may use any communication standard or protocol, including but not limited to GSM (Global System of Mobile communication), GPRS (General Packet Radio Service), CDMA2000 (Code Division Multiple Access 2000), WCDMA (Wideband Code Division Multiple Access), TD-SCDMA (Time Division-Synchronous Code Division Multiple Access), FDD-LTE (Frequency Division Duplexing-Long Term Evolution), TDD-LTE (Time Division Duplexing-Long Term Evolution), and 5G, etc.

[0071] WiFi is a short-range wireless transmission technology. Mobile terminals, through the WiFi module 102, can help users send and receive emails, browse web pages, and access streaming media, providing users with wireless broadband internet access. Although Figure 1 WiFi module 102 is shown, but it is understood that it is not a necessary component of a mobile terminal and can be omitted as needed without changing the nature of the invention.

[0072] The audio output unit 103 can convert audio data received by the radio frequency unit 101 or the WiFi module 102 or stored in the memory 109 into audio signals and output them as sound when the mobile terminal 100 is in call signal receiving mode, call mode, recording mode, voice recognition mode, broadcast receiving mode, etc. Furthermore, the audio output unit 103 can also provide audio output related to specific functions performed by the mobile terminal 100 (e.g., call signal receiving sound, message receiving sound, etc.). The audio output unit 103 may include a speaker, a buzzer, etc.

[0073] The A / V input unit 104 is used to receive audio or video signals. The A / V input unit 104 may include a graphics processing unit (GPU) 1041 and a microphone 1042. The GPU 1041 processes image data of still images or videos acquired by an image capture device (such as a camera) in video capture mode or image capture mode. The processed image frames can be displayed on the display unit 106. The image frames processed by the GPU 1041 can be stored in the memory 109 (or other storage medium) or transmitted via the radio frequency unit 101 or the WiFi module 102. The microphone 1042 can receive sound (audio data) in operating modes such as telephone call mode, recording mode, and voice recognition mode, and can process such sound into audio data. The processed audio (voice) data can be converted into a format that can be transmitted to a mobile communication base station via the radio frequency unit 101 in telephone call mode. The microphone 1042 can implement various types of noise cancellation (or suppression) algorithms to eliminate (or suppress) noise or interference generated during the reception and transmission of audio signals.

[0074] The mobile terminal 100 also includes at least one sensor 105, such as a light sensor, a motion sensor, and other sensors. Optionally, the light sensor includes an ambient light sensor and a proximity sensor. Optionally, the ambient light sensor can adjust the brightness of the display panel 1061 according to the ambient light level, and the proximity sensor can turn off the display panel 1061 and / or backlight when the mobile terminal 100 is moved to the ear. As a type of motion sensor, an accelerometer sensor can detect the magnitude of acceleration in various directions (generally three axes), and can detect the magnitude and direction of gravity when stationary. It can be used for applications that recognize the phone's posture (such as landscape / portrait switching, related games, magnetometer posture calibration), vibration recognition related functions (such as pedometer, tapping), etc. Other sensors that may be configured in the phone, such as fingerprint sensors, pressure sensors, iris sensors, molecular sensors, gyroscopes, barometers, hygrometers, thermometers, and infrared sensors, will not be described in detail here.

[0075] The display unit 106 is used to display information input by the user or information provided to the user. The display unit 106 may include a display panel 1061, which may be configured in the form of a liquid crystal display (LCD), an organic light-emitting diode (OLED), or the like.

[0076] User input unit 107 can be used to receive input numerical or character information, and generate key signal inputs related to user settings and function control of the mobile terminal. Optionally, user input unit 107 may include touch panel 1071 and other input devices 1072. Touch panel 1071, also known as a touch screen, can collect touch operations performed by the user on or near it (such as operations performed by the user using a finger, stylus, or any suitable object or accessory on or near touch panel 1071), and drive corresponding connection devices according to a pre-set program. Touch panel 1071 may include a touch detection device and a touch controller. Optionally, the touch detection device detects the user's touch position and the signal generated by the touch operation, and transmits the signal to the touch controller; the touch controller receives touch information from the touch detection device, converts it into touch point coordinates, sends it to processor 110, and can receive and execute commands sent by processor 110. In addition, touch panel 1071 can be implemented using various types such as resistive, capacitive, infrared, and surface acoustic wave. In addition to the touch panel 1071, the user input unit 107 may also include other input devices 1072. Optionally, other input devices 1072 may include, but are not limited to, one or more of the following: physical keyboard, function keys (such as volume control buttons, power buttons, etc.), trackball, mouse, joystick, etc., without being specifically limited here.

[0077] Optionally, the touch panel 1071 may cover the display panel 1061. When the touch panel 1071 detects a touch operation on or near it, it transmits the information to the processor 110 to determine the type of touch event. Subsequently, the processor 110 provides corresponding visual output on the display panel 1061 based on the type of touch event. Although in Figure 1 In this embodiment, the touch panel 1071 and the display panel 1061 are two independent components to realize the input and output functions of the mobile terminal. However, in some embodiments, the touch panel 1071 and the display panel 1061 can be integrated to realize the input and output functions of the mobile terminal. The specific implementation is not limited here.

[0078] Interface unit 108 serves as an interface through which at least one external device can connect to mobile terminal 100. For example, the external device may include a wired or wireless headset port, an external power supply (or battery charger) port, a wired or wireless data port, a memory card port, a port for connecting a device with an identification module, an audio input / output (I / O) port, a video I / O port, a headphone port, and so on. Interface unit 108 may be used to receive input (e.g., data, power, etc.) from the external device and transmit the received input to one or more elements within mobile terminal 100, or it may be used to transmit data between mobile terminal 100 and the external device.

[0079] The memory 109 can be used to store software programs and various data. The memory 109 may primarily include a program storage area and a data storage area. Optionally, the program storage area may store the operating system, applications required for at least one function (such as sound playback, image playback, etc.), etc.; the data storage area may store data created based on the use of the mobile phone (such as audio data, phonebook, etc.). Furthermore, the memory 109 may include high-speed random access memory, and may also include non-volatile memory, such as at least one disk storage device, flash memory device, or other volatile solid-state storage device.

[0080] The processor 110 is the control center of the mobile terminal. It connects various parts of the mobile terminal via various interfaces and lines. By running or executing software programs and / or modules stored in the memory 109, and by calling data stored in the memory 109, it performs various functions and processes data of the mobile terminal, thereby providing overall monitoring of the mobile terminal. The processor 110 may include one or more processing units; preferably, the processor 110 may integrate an application processor and a modem processor. Optionally, the application processor mainly handles the operating system, user interface, and applications, while the modem processor mainly handles wireless communication. It is understood that the modem processor may not be integrated into the processor 110.

[0081] The mobile terminal 100 may also include a power supply 111 (such as a battery) that supplies power to various components. Preferably, the power supply 111 can be logically connected to the processor 110 through a power management system, thereby enabling functions such as charging, discharging, and power consumption management through the power management system.

[0082] although Figure 1 As not shown, the mobile terminal 100 may also include a Bluetooth module, etc., which will not be described in detail here.

[0083] To facilitate understanding of the embodiments of this application, the communication network system on which the mobile terminal of this application is based is described below.

[0084] Please see Figure 2 , Figure 2 This application provides a communication network system architecture diagram. The communication network system is an LTE system based on the universal mobile communication technology. The LTE system includes a UE (User Equipment) 201, an E-UTRAN (Evolved UMTS Terrestrial Radio Access Network) 202, an EPC (Evolved Packet Core) 203, and the operator's IP services 204, which are connected in sequence.

[0085] Optionally, UE201 can be the aforementioned terminal 100, which will not be described in detail here.

[0086] E-UTRAN202 includes eNodeB2021 and other eNodeB2022, etc. Optionally, eNodeB2021 can connect to other eNodeB2022 via backhaul (e.g., X2 interface), and eNodeB2021 connects to EPC203, providing access from UE201 to EPC203.

[0087] EPC203 may include MME (Mobility Management Entity) 2031, HSS (Home Subscriber Server) 2032, other MMEs 2033, SGW (Serving Gateway) 2034, PGW (Packet Data Network Gateway) 2035, and PCRF (Policy and Charging Rules Function) 2036, etc. Optionally, MME2031 is the control node that handles signaling between UE201 and EPC203, providing bearer and connection management. HSS2032 is used to provide registers to manage functions such as the Home Location Register (not shown in the figure) and stores user-specific information such as service characteristics and data rates. All user data can be sent through SGW2034. PGW2035 can provide UE 201 IP address allocation and other functions. PCRF2036 is the policy and charging control decision point for service data flow and IP bearer resources. It selects and provides available policy and charging control decisions for the policy and charging enforcement function unit (not shown in the figure).

[0088] IP services 204 may include the Internet, intranet, IMS (IP Multimedia Subsystem), or other IP services.

[0089] Although the above description uses the LTE system as an example, those skilled in the art should know that this application is not only applicable to the LTE system, but also to other wireless communication systems, such as GSM, CDMA2000, WCDMA, TD-SCDMA, 5G and future new network systems (such as 6G), etc., without limitation.

[0090] Based on the above-described mobile terminal hardware structure and communication network system, various embodiments of this application are proposed.

[0091] Figure 3 This is a schematic diagram of the hardware structure of a controller 140 provided in this application. The controller 140 includes a memory 1401 and a processor 1402. The memory 1401 is used to store program instructions, and the processor 1402 is used to call the program instructions in the memory 1401 to execute the steps performed by the controller in the first embodiment of the above method. The implementation principle and beneficial effects are similar, and will not be described again here.

[0092] Optionally, the controller further includes a communication interface 1403, which can be connected to the processor 1402 via a bus 1404. The processor 1402 can control the communication interface 1403 to implement the receiving and sending functions of the controller 140.

[0093] Figure 4 This application provides a schematic diagram of the hardware structure of a network node 150. The network node 150 includes a memory 1501 and a processor 1502. The memory 1501 is used to store program instructions, and the processor 1502 is used to call the program instructions in the memory 1501 to execute the steps performed by the first node in the first embodiment of the above method. The implementation principle and beneficial effects are similar, and will not be described again here.

[0094] Optionally, the controller further includes a communication interface 1503, which can be connected to the processor 1502 via a bus 1504. The processor 1502 can control the communication interface 1503 to implement the receiving and sending functions of the network node 150.

[0095] The integrated modules described above, implemented as software functional modules, can be stored in a computer-readable storage medium. These software functional modules, stored in a storage medium, include several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) or processor to execute some steps of the methods of the various embodiments of this application.

[0096] Technical terms used in this embodiment:

[0097] CPA: Conditional PSCell Addition, adding primary and secondary cells under certain conditions;

[0098] CPC: Conditional PSCell Change;

[0099] NR-DC: NR-NR Dual Connectivity;

[0100] PCell: Primary Cell;

[0101] PSCell: Primary SCG Cell;

[0102] SN: Secondary Node;

[0103] MN: Master Node;

[0104] RRC reconfiguration;

[0105] CPC SCG change: CPC switchover;

[0106] condReconfigId: Conditional reconfiguration ID / conditional reconfiguration identifier;

[0107] SN initiated inter-SN CPC: SN-initiated inter-SN CPC / SN-initiated inter-SN conditional primary / secondary cell handover;

[0108] SN Change Required: SN switching request;

[0109] SN Addition procedure: SN addition process;

[0110] SN Addition Req: SN addition request;

[0111] SN Modification Request message: SN modification request message;

[0112] SN Modification Request Acknowledge: Acknowledgement of SN modification request.

[0113] Reference Figure 5 , Figure 5 This application embodiment provides a scenario interaction flowchart for configuring the execution conditions of continuous or subsequent CPC in SN-initiated inter-SN continuous or subsequent CPC scenarios without requiring RRC reconfiguration.

[0114] like Figure 5 As shown, the network side includes: MN, PSCell X, PSCell A, PSCell B, and PSCell C. Optionally, PSCell X belongs to the source SN. The process for configuring the execution conditions of consecutive or subsequent CPCs includes:

[0115] 1. The source SN sends an SN Change Required message to the MN. This message carries the list of candidate PSCells recommended by the source SN and the corresponding execution conditions.

[0116] 2. After receiving the message, the MN sends an SN Addition Req to each candidate SN through the SN Addition procedure to request resource allocation. The SN Addition Req includes a list of recommended candidate PSCells received from the source SN. The candidate SN allocates CPC resource configurations for the candidate PSCells and sends them to the MN.

[0117] 3. MN determines or generates a conditional reconfiguration message (CondReconfigToAddMod), assigns a condReconfigId (conditional reconfiguration ID / conditional reconfiguration identifier) ​​to each candidate PSCell, and each condReconfigId corresponds to a candidate PSCell.

[0118] 4. The MN sends an SN Modification Request message to each candidate SN. This message includes information about the candidate PSCells accepted by other candidate SNs (such as SSB frequency point, PCI, etc.) and their corresponding condReconfigId.

[0119] Optionally, the information of the candidate PSCell can include the current PSCell, that is, the current PSCell can be used as a candidate PSCell.

[0120] 5. Based on the information provided by the MN, the candidate PSCell is configured to update the CPC execution conditions of other candidate PSCells and / or update the measurement configuration in the corresponding CPC configuration. The CPC execution conditions are associated with the condReconfigId of the candidate PSCell, and the updated execution conditions and / or measurement configuration are provided to the MN through SN Modification Request Acknowledge.

[0121] Optionally, candidate PSCells may not be configured with CPC execution conditions for certain candidate PSCells (such as based on neighbor cell relationships or historical handover records). Not configuring CPC execution conditions means that after the UE switches to that PSCell, it is not necessary to evaluate the execution conditions of these candidate PSCells.

[0122] 6. The MN determines or generates a conditional reconfiguration message based on the received CPC resource configuration and the updated CPC configuration of each candidate PSCell, and sends it to the UE through the RRC Reconfiguration message. The UE maintains the execution conditions and CPC condition configuration of each candidate PSCell.

[0123] 7. After the UE performs CPC handover to a target candidate PSCell, the condition configuration of the target candidate PSCell is applied, while the condition configurations of other candidate PSCells are retained. The execution conditions of the target candidate PSCell to other candidate PSCells are updated according to the condition configuration of the target candidate PSCell, and the execution conditions of other candidate PSCells are evaluated.

[0124] In this application's technical solution, a conditional reconfiguration message is sent by the network device to enable the terminal device to configure the execution conditions for consecutive or subsequent CPCs. Therefore, for SN-initiated inter-SN consecutive or subsequent CPC scenarios, a method is proposed that supports configuring the execution conditions for consecutive or subsequent CPCs without requiring RRC reconfiguration, thus meeting the scenario requirements.

[0125] First Embodiment

[0126] Reference Figure 6 As shown, the first embodiment of this application proposes a configuration method, including the following steps:

[0127] S20, the network device sends a conditional reconfiguration message to enable the terminal device to configure the execution conditions for consecutive or subsequent CPCs;

[0128] S30, the terminal device receives a condition reconfiguration message to configure the execution conditions for consecutive or subsequent CPCs.

[0129] Optionally, the conditional reconfiguration message includes conditional configurations for the target PSCell in the SN to other candidate PSCells.

[0130] Optionally, the condition configuration includes at least one of the following: condition reconfiguration ID, CPC execution condition, and condition RRC reconfiguration message.

[0131] Therefore, for SN-initiated inter-SN continuous or subsequent CPC scenarios, a method is proposed to support configuring the execution conditions of continuous or subsequent CPC without requiring RRC reconfiguration, thus meeting the scenario requirements.

[0132] Second Embodiment

[0133] Reference Figure 7As shown, based on the above embodiments, the second embodiment of this application proposes a configuration method, which further includes the following step before step S20:

[0134] S10: Determine or generate conditional reconfiguration messages based on configuration information.

[0135] Optionally, step S10 includes:

[0136] The first network node sends a secondary node modification request message to the candidate network node set;

[0137] The second network node in the candidate network node set determines or generates the conditional configuration and / or measurement configuration for other candidate PSCells based on the auxiliary node modification request message;

[0138] The second network node sends the conditional configuration and / or measurement configuration for other candidate PSCells to the first network node through the auxiliary node modification request confirmation message;

[0139] The first network node determines, generates, or updates the conditional reconfiguration message based on the secondary node's modification request confirmation message.

[0140] Optionally, the first network node is MN and the second network node is SN.

[0141] Optionally, the secondary node modification request message includes at least one of the following: SSB frequency information of other candidate PSCells, PCI information of other candidate PSCells, and conditional reconfiguration ID of other candidate PSCells.

[0142] Optionally, the conditional configuration determined or generated by the second network node for other candidate PSCells includes at least one of the following: conditional reconfiguration ID, CPC execution condition, and conditional RRC reconfiguration message.

[0143] Optionally, the conditional configuration determined or generated by the second network node for other candidate PSCells is associated with the conditional reconfiguration ID of those other candidate PSCells.

[0144] Optionally, if the second network node has not determined or generated conditional configurations for other candidate PSCells, the terminal device will not perform conditional evaluation on the other candidate PSCells when switching to the second network node.

[0145] Optionally, before the first network node sends the secondary node modification request message to the candidate network node set, it also includes:

[0146] The third network node requests resource allocation from the candidate network node set based on the auxiliary node change request message.

[0147] Optionally, the first network node is a candidate PSCell allocation condition reconfiguration ID for successfully allocated resources.

[0148] Optionally, the secondary node change request message includes at least one of the following:

[0149] Recommended candidate PSCell list;

[0150] Recommended execution conditions for candidate PSCells;

[0151] Measurement configuration.

[0152] In this application's technical solution, network devices determine or generate conditional reconfiguration messages based on configuration information and send these messages to enable terminal devices to configure execution conditions for consecutive or subsequent CPCs. The conditional reconfiguration messages include conditional configurations from the target PSCell in the SN to other candidate PSCells. This application proposes a method for configuring execution conditions for consecutive or subsequent CPCs in SN-initiated inter-SN consecutive or subsequent CPC scenarios without requiring RRC reconfiguration, thus meeting the scenario requirements.

[0153] Third Embodiment

[0154] Reference Figure 8 As shown, the third embodiment of this application proposes a configuration method, including the following steps:

[0155] S11, the first network node sends a secondary node modification request message to the candidate network node set;

[0156] S12, the second network node in the candidate network node set determines or generates the conditional configuration and / or measurement configuration for other candidate PSCells based on the auxiliary node modification request message;

[0157] S13, the second network node sends the conditional configuration and / or measurement configuration for other candidate PSCells to the first network node through the auxiliary node modification request confirmation message;

[0158] S14, the first network node determines, generates, or updates the condition reconfiguration message based on the auxiliary node's modification request confirmation message and sends it to the terminal device so that the terminal device can configure the execution conditions of continuous or subsequent CPCs.

[0159] Optionally, the first network node is MN.

[0160] Optionally, the second network node is SN.

[0161] Optionally, the secondary node modification request message includes at least one of the following: SSB frequency information of other candidate PSCells, PCI information of other candidate PSCells, and conditional reconfiguration ID of other candidate PSCells.

[0162] Optionally, the conditional configuration determined or generated by the second network node for other candidate PSCells includes at least one of the following: conditional reconfiguration ID, CPC execution condition, and conditional RRC reconfiguration message.

[0163] Optionally, the conditional configuration determined or generated by the second network node for other candidate PSCells is associated with the conditional reconfiguration ID of those other candidate PSCells.

[0164] Optionally, if the second network node has not determined or generated conditional configurations for other candidate PSCells, the terminal device will not perform conditional evaluation on the other candidate PSCells when switching to the second network node.

[0165] Optionally, before the first network node sends the secondary node modification request message to the candidate network node set, it also includes:

[0166] The third network node requests resource allocation from the candidate network node set based on the auxiliary node change request message.

[0167] Optionally, the first network node is a candidate PSCell allocation condition reconfiguration ID for successfully allocated resources.

[0168] Optionally, the auxiliary node change request message includes at least one of the following: a recommended candidate PSCell list, the execution conditions corresponding to the recommended candidate PSCell, and the measurement configuration.

[0169] In this application's technical solution, network devices determine or generate conditional reconfiguration messages based on configuration information and send these messages to enable terminal devices to configure execution conditions for consecutive or subsequent CPCs. The conditional reconfiguration messages include conditional configurations from the target PSCell in the SN to other candidate PSCells. This application proposes a method for configuring execution conditions for consecutive or subsequent CPCs in SN-initiated inter-SN consecutive or subsequent CPC scenarios without requiring RRC reconfiguration, thus meeting the scenario requirements.

[0170] Fourth embodiment

[0171] Reference Figure 9 As shown, based on the above embodiments, the fourth embodiment of this application proposes a configuration method, taking the terminal device as a UE as an example. The method includes the following steps:

[0172] 1. The source SN (i.e., PSCell) sends an SN Change Required message to the MN (i.e., PCell). This SN Change Required message carries the candidate PSCell list recommended by the source SN (such as PSCell A, PSCell B, PSCell C) and the corresponding execution conditions (such as MeasId_A, MeasId_B, MeasId_C).

[0173] 2. After receiving the message, the MN requests resource allocation from each candidate SN through the SN Addition procedure. The SNAddition Req includes a list of recommended candidate PSCells received from the source SN. The candidate SN allocates CPC resource configurations (condRRCReconfig A, condRRCReconfig B, condRRCReconfig C) to the candidate PSCells and sends them to the MN.

[0174] 3. When the MN is determined or a conditional reconfiguration message is generated (i.e., CondReconfigToAddMod), a condReconfigId is assigned to each candidate PSCell, and each condReconfigId corresponds to one candidate PSCell. For example, PSCell A corresponds to condReconfigId 1, PSCell B corresponds to condReconfigId 2, and PSCell C corresponds to condReconfigId 3.

[0175] 4. The MN sends an SN Modification Request message to each candidate SN. This message includes information about the candidate PSCells accepted by other candidate SNs (such as SSB frequency point, PCI, etc.) and their corresponding condReconfigId.

[0176] Optionally, the information of the candidate PSCell can include the current PSCell, that is, the current PSCell can be used as a candidate PSCell.

[0177] 5. Based on the information provided by the MN, the candidate PSCell is configured to update the CPC execution conditions and / or the measurement configuration in the corresponding CPC configuration of other candidate PSCells. The CPC execution conditions are associated with the condReconfigId of the candidate PSCell, and the updated execution conditions and / or measurement configuration are provided to the MN through SN Modification Request Acknowledge.

[0178] Optionally, taking candidate PSCell A as an example, the execution condition of PSCell A on PSCell B is MeasId_A-B, corresponding to condReconfigId 2; the execution condition of PSCell A on PSCell C is MeasId_A-C, corresponding to condReconfigId 3.

[0179] Optionally, taking candidate PSCell B as an example, the execution condition of PSCell B on PSCell A is MeasId_B-A, corresponding to condReconfigId 1; the execution condition of PSCell B on PSCell C is MeasId_B-C, corresponding to condReconfigId 3.

[0180] Optionally, taking candidate PSCell C as an example, the execution condition of PSCell C on PSCell A is MeasId_C-A, corresponding to condReconfigId 1.

[0181] Optionally, updating the measurement configuration in the corresponding CPC configuration means that if the CPC resource allocation configuration for the candidate SN to the candidate PSCell in step 2 does not include the execution conditions configured in step 5 (i.e., the MeasConfig measurement configuration in the condition configuration does not include the configured execution conditions), then the corresponding MeasConfig needs to be updated.

[0182] Optionally, when the CPC execution conditions or condition configurations of certain candidate PSCells are not configured (such as based on neighbor cell relationships or historical handover records), not configuring CPC execution conditions or condition configurations means that after the UE CPC hands over to that PSCell, it is not necessary to evaluate the execution conditions of these candidate PSCells.

[0183] Optionally, if candidate PSCell C is not configured with the execution conditions for PSCell B in step 5, it means that the UE CPC will not perform the condition evaluation for PSCell B after switching to PSCell C.

[0184] 6. The MN determines or generates a conditional reconfiguration message based on the received CPC resource configuration and the updated CPC configuration of each candidate PSCell (optional), and sends it to the UE through RRCReconfiguration. The UE maintains the execution conditions and CPC condition configuration of each candidate PSCell.

[0185] 7. After the UE performs CPC handover to a target candidate PSCell, the condition configuration of the target candidate PSCell is applied, while the condition configurations of other candidate PSCells are retained. The execution conditions of the target candidate PSCell to other candidate PSCells are updated according to the condition configuration of the target candidate PSCell, and the execution conditions of other candidate PSCells are evaluated.

[0186] Optionally, if the current UE is configured with SCG as PSCell, the VarConditionalReconfig maintained by the UE storage is:

[0187] condReconfigId=1, condRRCReconfig=A, CondReconfigExecCondSCG=MeasId_A;

[0188] condReconfigId=2, condRRCReconfig=B, CondReconfigExecCondSCG=MeasId_B;

[0189] condReconfigId=3, condRRCReconfig=C, CondReconfigExecCondSCG=MeasId_C.

[0190] Optionally, the configuration corresponding to condRRCReconfig=A is:

[0191] MeasConfig: MeasId_A-X, MeasId_A-B, MeasId_A-C;

[0192] condReconfigId=2, condRRCReconfig=B (optional), CondReconfigExecCondSCG=MeasId_A-B;

[0193] condReconfigId=3, condRRCReconfig=C (optional), CondReconfigExecCondSCG=MeasId_A-C.

[0194] Optionally, the configuration corresponding to condRRCReconfig=B is:

[0195] MeasConfig: MeasId_B-A, MeasId_B-C;

[0196] condReconfigId=1, condRRCReconfig=A (optional), CondReconfigExecCondSCG=MeasId_B-A;

[0197] condReconfigId=3, condRRCReconfig=C (optional), CondReconfigExecCondSCG=MeasId_B-C.

[0198] Optionally, the configuration corresponding to condRRCReconfig=C is:

[0199] MeasConfig: MeasId_C-A, MeasId_C-B;

[0200] condReconfigId=1, condRRCReconfig=A (optional), CondReconfigExecCondSCG=MeasId_C-A;

[0201] condReconfigId=2, condRRCReconfig=B (optional), CondReconfigExecCondSCG=MeasId_C-B.

[0202] Optionally, the UE performs a condition evaluation. If it finds that PSCellA meets the CPC execution condition (i.e., MeasId_A is met), the UE execution condition switches to PSCellA, and the configuration corresponding to condRRCReconfig=A is applied. Then, the UE updates the stored VarConditionalReconfig to:

[0203] condReconfigId=1, condRRCReconfig=A, CondReconfigExecCondSCG=MeasId_A (Current cell configuration will be retained);

[0204] condReconfigId=2, condRRCReconfig=B, CondReconfigExecCondSCG=MeasId_A-B;

[0205] condReconfigId=3, condRRCReconfig=C, CondReconfigExecCondSCG=MeasId_A-C.

[0206] The UE continues to perform condition evaluation and finds that PSCell B meets the CPC execution conditions (i.e., MeasId_A-B is met). The UE switches the execution condition to PSCell B and applies the configuration corresponding to condRRCReconfig=B. Then, the UE updates the stored VarConditionalReconfig to:

[0207] condReconfigId=1, condRRCReconfig=A, CondReconfigExecCondSCG=MeasId_B-A;

[0208] condReconfigId=2, condRRCReconfig=B, CondReconfigExecCondSCG=MeasId_A-B (Current cell configuration will be retained);

[0209] condReconfigId=3, condRRCReconfig=C, CondReconfigExecCondSCG=MeasId_B-C.

[0210] In this embodiment, the network device determines or generates a conditional reconfiguration message based on configuration information and sends the message to enable the terminal device to configure the execution conditions for consecutive or subsequent CPCs. The conditional reconfiguration message includes the conditional configuration from the target PSCell in the SN to other candidate PSCells. This application proposes a method for configuring the execution conditions of consecutive or subsequent CPCs without requiring RRC reconfiguration, specifically for SN-initiated inter-SN consecutive or subsequent CPC scenarios, thus meeting the scenario requirements.

[0211] This application embodiment also provides a configuration device, applied to a network device or being a network device, the device comprising:

[0212] The sending module is used to send conditional reconfiguration messages to enable the terminal device to configure the execution conditions for consecutive or subsequent CPCs.

[0213] Optionally, the device further includes:

[0214] The determine or generate module is used to determine or generate conditional reconfiguration messages based on configuration information.

[0215] Optionally, the determining or generating module is also used to implement the following functions:

[0216] The first network node sends a secondary node modification request message to the candidate network node set;

[0217] The second network node in the candidate network node set determines or generates the conditional configuration and / or measurement configuration for other candidate PSCells based on the auxiliary node modification request message;

[0218] The second network node sends the conditional configuration and / or measurement configuration for other candidate PSCells to the first network node through the auxiliary node modification request confirmation message;

[0219] The first network node determines, generates, or updates the conditional reconfiguration message based on the secondary node's modification request confirmation message.

[0220] Optionally, the secondary node modification request message includes at least one of the following: SSB frequency information of other candidate PSCells, PCI information of other candidate PSCells, and conditional reconfiguration ID of other candidate PSCells.

[0221] Optionally, the conditional configuration determined or generated by the second network node for other candidate PSCells includes at least one of the following: conditional reconfiguration ID, CPC execution condition, and conditional RRC reconfiguration message.

[0222] Optionally, the conditional configuration determined or generated by the second network node for other candidate PSCells is associated with the conditional reconfiguration ID of those other candidate PSCells.

[0223] Optionally, if the second network node has not determined or generated conditional configurations for other candidate PSCells, the terminal device will not perform conditional evaluation on the other candidate PSCells when switching to the second network node.

[0224] Optionally, before the first network node sends the secondary node modification request message to the candidate network node set, it also includes:

[0225] The third network node requests resource allocation from the candidate network node set based on the auxiliary node change request message.

[0226] Optionally, the first network node reconfigures the allocation condition ID for the candidate PSCell that has successfully allocated resources; and / or, the secondary node change request message includes at least one of the following:

[0227] Recommended candidate PSCell list, corresponding execution conditions for recommended candidate PSCells, and measurement configuration.

[0228] This application also proposes a configuration device, applied to a terminal device or being a terminal device, the device comprising:

[0229] The receiving module is used to receive conditional reconfiguration messages to configure the execution conditions for consecutive or subsequent CPCs.

[0230] Optionally, the conditional reconfiguration message includes conditional configurations for the target PSCell to other candidate PSCells in the SN; and / or, the conditional reconfiguration message is determined or generated in the following manner:

[0231] The first network node sends a secondary node modification request message to the candidate network node set;

[0232] The second network node in the candidate network node set determines or generates the conditional configuration and / or measurement configuration for other candidate PSCells based on the auxiliary node modification request message;

[0233] The second network node sends the conditional configuration and / or measurement configuration for other candidate PSCells to the first network node through the auxiliary node modification request confirmation message;

[0234] The first network node determines, generates, or updates the conditional reconfiguration message based on the secondary node's modification request confirmation message.

[0235] Optionally, the auxiliary node modification request message includes at least one of the following: SSB frequency information of other candidate PSCells, PCI information of other candidate PSCells, and conditional reconfiguration ID of other candidate PSCells;

[0236] The conditional configurations for determining or generating other candidate PSCells by the second network node include at least one of the following:

[0237] Conditional reconfiguration ID, CPC execution condition, and conditional RRC reconfiguration message.

[0238] Optionally, the conditional configuration determined or generated by the second network node for other candidate PSCells is associated with the conditional reconfiguration ID of those other candidate PSCells.

[0239] Optionally, if the second network node has not determined or generated conditional configurations for other candidate PSCells, the terminal device will not perform conditional evaluation on the other candidate PSCells when switching to the second network node.

[0240] Optionally, after the terminal device performs CPC to switch to the target candidate PSCell, the condition configuration of the target PSCell is applied, the condition configurations of the other candidate PSCells are retained, and the execution conditions and / or condition RRC reconfiguration messages of the PSCell to the other candidate PSCells are updated according to the condition configuration of the target PSCell.

[0241] This application also provides a communication system, including the terminal device described in any of the above embodiments and the network device described in any of the above embodiments.

[0242] This application also provides a communication device, including: a memory, a processor, and a configuration program stored in the memory and executable on the processor. When executed by the processor, the configuration program implements the configuration method as described in any of the above embodiments. The communication device mentioned in this application can be a terminal device (such as a smart terminal, specifically a mobile phone) or a network device (such as a base station); the specific meaning needs to be clarified in the context.

[0243] This application also provides a storage medium storing a computer program, which, when executed by a processor, implements the configuration method as described in any of the above embodiments.

[0244] In the embodiments of the communication device and storage medium provided in this application, all the technical features of any of the above-described configuration method embodiments may be included. The extended and explained contents of the specification are basically the same as those of the embodiments of the above methods, and will not be repeated here.

[0245] This application also provides a computer program product, which includes computer program code. When the computer program code is run on a computer, it causes the computer to perform the methods described in the various possible implementations above.

[0246] This application also provides a chip, including a memory and a processor. The memory is used to store a computer program, and the processor is used to call and run the computer program from the memory, so that a device with the chip installed performs the methods described in the various possible implementations above.

[0247] It is understood that the above scenarios are merely examples and do not constitute a limitation on the application scenarios of the technical solutions provided in the embodiments of this application. The technical solutions of this application can also be applied to other scenarios. For example, as those skilled in the art will know, with the evolution of system architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems.

[0248] The sequence numbers of the embodiments in this application are for descriptive purposes only and do not represent the superiority or inferiority of the embodiments.

[0249] The steps in the method of this application embodiment can be adjusted, combined, or deleted according to actual needs.

[0250] The units in the device of this application embodiment can be merged, divided, and deleted according to actual needs.

[0251] In this application, the same or similar terms, concepts, technical solutions and / or application scenario descriptions are generally described in detail only when they appear for the first time. When they appear again, they are generally not repeated for the sake of brevity. When understanding the technical solutions and other contents of this application, the same or similar terms, concepts, technical solutions and / or application scenario descriptions that are not described in detail later can be referred to their previous relevant detailed descriptions.

[0252] In this application, the descriptions of the various embodiments have different focuses. For parts that are not described in detail or recorded in a certain embodiment, please refer to the relevant descriptions of other embodiments.

[0253] The technical features of the present application can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of the present application.

[0254] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) as described above, and includes several instructions to cause a terminal device (which may be a mobile phone, computer, server, controlled terminal, or network device, etc.) to execute the methods of each embodiment of this application.

[0255] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented, in whole or in part, as a computer program product. A computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the flow or function according to the embodiments of this application is generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a storage medium or transmitted from one storage medium to another. For example, computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, digital subscriber line) or wireless (e.g., infrared, wireless, microwave, etc.) means. The storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that integrates one or more available media. The available medium can be a magnetic medium (e.g., floppy disk, storage disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., a solid-state disk (SSD)).

[0256] The above are merely preferred embodiments of this application and do not limit the patent scope of this application. Any equivalent structural or procedural transformations made using the content of this application's specification and drawings, or direct or indirect applications in other related technical fields, are similarly included within the patent protection scope of this application.

Claims

1. A configuration method, characterized by, Including the following steps: S20: The first network node sends a conditional reconfiguration message to enable the terminal device to configure the execution conditions for continuous CPC; The conditional reconfiguration message includes the conditional configuration of the target PSCell in the candidate SN to other candidate PSCells; The conditional configuration of the target PSCell to other candidate PSCells in the candidate SN is determined or generated by the candidate SN according to the auxiliary node modification request message sent by the first network node; The secondary node modification request message contains at least one of the following: SSB frequency information of other candidate PSCells, PCI information of other candidate PSCells, and conditional reconfiguration ID of other candidate PSCells; The conditional configuration from the target PSCell to other candidate PSCells in the candidate SN includes at least one of the following: conditional reconfiguration ID, CPC execution condition, and conditional RRC reconfiguration message; The first network node is the master node; the terminal device does not release the candidate cell configuration and / or execution conditions after CPC is executed.

2. The method of claim 1, wherein, Before step S20, the method further includes the following steps: S10: Determine or generate conditional reconfiguration messages based on configuration information.

3. The method of claim 2, wherein, Step S10 includes: The first network node sends a secondary node modification request message to the candidate network node set; The second network node in the candidate network node set determines or generates the conditional configuration and / or measurement configuration for other candidate PSCells based on the auxiliary node modification request message; The second network node sends the conditional configuration and / or measurement configuration for other candidate PSCells to the first network node through the auxiliary node modification request confirmation message; The first network node determines, generates, or updates the conditional reconfiguration message based on the secondary node's modification request confirmation message.

4. The method of claim 3, wherein, The method further includes at least one of the following: The conditional configuration determined or generated by the second network node for other candidate PSCells is associated with the conditional reconfiguration ID of those other candidate PSCells. When the second network node has not determined or generated the condition configuration for other candidate PSCells, the terminal device will not perform condition evaluation on the other candidate PSCells when switching to the second network node.

5. The method of claim 3, wherein, Before the first network node sends the secondary node modification request message to the candidate network node set, it also includes: The third network node requests resource allocation from the candidate network node set based on the auxiliary node change request message.

6. The method of claim 5, wherein, The first network node reconfigures the allocation condition ID for the candidate PSCell that has successfully allocated resources; and / or, the secondary node change request message includes at least one of the following: Recommended candidate PSCell list; Recommended execution conditions for candidate PSCells; Measurement configuration.

7. A configuration method, characterized in that, Including the following steps: S30: The terminal device receives a condition reconfiguration message to configure the execution conditions for continuous CPC; The conditional reconfiguration message includes the conditional configuration of the target PSCell in the candidate SN to other candidate PSCells; The conditional configuration of the target PSCell to other candidate PSCells in the candidate SN is determined or generated by the candidate SN according to the auxiliary node modification request message sent by the first network node; The secondary node modification request message contains at least one of the following: SSB frequency information of other candidate PSCells, PCI information of other candidate PSCells, and conditional reconfiguration ID of other candidate PSCells; The conditional configuration from the target PSCell to other candidate PSCells in the candidate SN includes at least one of the following: conditional reconfiguration ID, CPC execution condition, and conditional RRC reconfiguration message; The first network node is the master node; the terminal device does not release the candidate cell configuration and / or execution conditions after CPC is executed.

8. The method according to claim 7, characterized in that, The conditional reconfiguration message is determined or generated in the following manner: The first network node sends a secondary node modification request message to the candidate network node set; The second network node in the candidate network node set determines or generates the conditional configuration and / or measurement configuration for other candidate PSCells based on the auxiliary node modification request message; The second network node sends the conditional configuration and / or measurement configuration for other candidate PSCells to the first network node through the auxiliary node modification request confirmation message; The first network node determines, generates, or updates the conditional reconfiguration message based on the secondary node's modification request confirmation message.

9. The method according to claim 8, characterized in that, The method further includes at least one of the following: The conditional configuration determined or generated by the second network node for other candidate PSCells is associated with the conditional reconfiguration ID of those other candidate PSCells. When the second network node has not determined or generated the condition configuration for other candidate PSCells, the terminal device will not perform condition evaluation on the other candidate PSCells when switching to the second network node. After the terminal device performs CPC to switch to the target candidate PSCell, the condition configuration of the target PSCell is applied, the condition configurations of the other candidate PSCells are retained, and the execution conditions and / or condition RRC reconfiguration messages of the PSCell to the other candidate PSCells are updated according to the condition configuration of the target PSCell.

10. A communication device, characterized in that, include: The memory and the processor, wherein the memory stores a configuration program, which, when executed by the processor, implements the configuration method as described in claim 1 or 7.

11. A storage medium, characterized in that, The storage medium stores a computer program that, when executed by a processor, implements the configuration method as described in claim 1 or 7.

Images