Configuration method, communication equipment and storage medium

Abstract

Disclosed are a configuration method, a communication device and a storage medium, the configuration method comprising: a network device sending a condition reconfiguration message to enable a terminal device to configure an execution condition of a continuous CPC. According to the technical scheme, the method for configuring the execution condition of the continuous CPC under the condition that RRC (Radio Resource Control) reception is not needed is provided for an SN (Serial Node) reception-SN continuous CPC scene, and the scene requirement is met.

Description

Configuration method, communication device and storage medium Technical Field

[0001] The present application relates to the field of communication technology, and in particular to a configuration method, communication equipment and storage medium. Background Art

[0002] According to Release 18 Widget ID (WID), the UE must support continuous CPC (Conditional PSCell Change) without requiring RRC reconfiguration (Radio Resource Control reconfiguration). This means that after CPC execution, the UE does not release the CPC candidate cell configuration and must maintain the CPC candidate cell list for the next CPC evaluation. Existing protocols specify that the UE uses the condReconfigId (Conditional Reconfiguration Identifier) ​​to identify, store, and maintain the CPC conditional configuration and execution conditions for each candidate cell.

[0003] During the development and implementation of this application, the inventors discovered that for SN initiated inter-SN CPC 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 required to pre-configure the target PSCell's CPC execution conditions for other candidate PSCells.

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

[0005] The main purpose of this application is to provide a configuration method, a communication device and a storage medium, which support the configuration of execution conditions for continuous or subsequent CPC without the need for RRC reconfiguration for SN initiated inter-SN continuous or subsequent CPC scenarios.

[0006] This application proposes a configuration method that can be applied to network equipment (such as a base station), including the following steps:

[0007] S20: Send a condition reconfiguration message to enable the terminal device to configure the execution conditions of continuous or subsequent CPCs.

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

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

[0010] S10: Determine or generate a conditional reconfiguration message based on the configuration information.

[0011] Optionally, the 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 conditional configurations and / or measurement configurations to other candidate PSCells according to the secondary node modification request message;

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

[0015] The first network node determines, generates, or updates a conditional reconfiguration message according to the secondary node 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 to other candidate PSCells determined or generated by the second network node includes at least one of the following: a conditional reconfiguration ID, a CPC execution condition, and a conditional RRC reconfiguration message.

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

[0019] Optionally, when the second network node does not determine or generate conditional configurations for other candidate PSCells, the terminal device does 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, the process further includes:

[0021] The third network node requests the candidate network node set to allocate resources according to the secondary node change request message.

[0022] Optionally, the first network node allocates a conditional reconfiguration ID to the candidate PSCell to which resources are successfully allocated.

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

[0024] This application also proposes a configuration method that can be applied to a terminal device (such as a mobile phone), including the following steps:

[0025] S30: Receive a condition reconfiguration message to configure execution conditions of continuous or subsequent CPCs.

[0026] Optionally, the conditional reconfiguration message includes conditional configuration of 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 conditional configurations and / or measurement configurations to other candidate PSCells according to the secondary node modification request message;

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

[0031] The first network node determines, generates, or updates a conditional reconfiguration message according to the secondary node modification request confirmation message.

[0032] 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.

[0033] Optionally, the conditional configuration for connecting to 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, conditional RRC reconfiguration message.

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

[0036] Optionally, when the second network node does not determine or generate conditional configurations for other candidate PSCells, the terminal device does not perform conditional evaluation on the other candidate PSCells when switching to the second network node.

[0037] Optionally, after the terminal device executes CPC switching to the target candidate PSCell, the conditional configuration of the target PSCell is applied, the conditional configuration of other candidate PSCells is retained, and the execution conditions and / or conditional RRC reconfiguration message of the PSCell to other candidate PSCells are updated according to the conditional configuration of the target PSCell.

[0038] The present application also provides a configuration device, comprising:

[0039] The sending module is used to send a condition reconfiguration message to enable the terminal device to configure the execution conditions of continuous or subsequent CPCs.

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

[0041] The receiving module is used to receive a condition reconfiguration message to configure the execution conditions of continuous or subsequent CPCs.

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

[0043] The present application also provides a storage medium having a computer program stored thereon. When the computer program is executed by a processor, the configuration method as described in any of the above embodiments is implemented.

[0044] In the technical solution of this application, a conditional reconfiguration message is sent by a network device to enable a terminal device to configure the execution conditions for continuous or subsequent CPC. This application proposes a method for configuring the execution conditions for continuous or subsequent CPC without the need for RRC reconfiguration in SN initiated inter-SN continuous or subsequent CPC scenarios. BRIEF DESCRIPTION OF THE DRAWINGS

[0045] The accompanying drawings herein are incorporated into and constitute a part of the specification, illustrate embodiments consistent with the present application, and together with the specification, are used to explain the principles of the present application. In order to more clearly illustrate the technical solutions of the embodiments of the present application, the following is a brief introduction to the drawings required for describing the embodiments. Obviously, for those skilled in the art, other drawings can be obtained based on these drawings without inventive work.

[0046] FIG1 is a schematic diagram of the hardware structure of a mobile terminal for implementing various embodiments of the present application;

[0047] FIG2 is a diagram of a communication network system architecture provided by an embodiment of the present application;

[0048] FIG3 is a schematic diagram of the hardware structure of the controller 140 involved in the configuration method embodiment of the present application;

[0049] FIG4 is a schematic diagram of the hardware structure of the network node 150 involved in the configuration method embodiment of the present application;

[0050] FIG5 is a flowchart illustrating a scenario interaction for configuring execution conditions for continuous or subsequent CPC in an SN initiated inter-SN continuous or subsequent CPC scenario in an embodiment of the present application, supporting the configuration of execution conditions for continuous or subsequent CPC without the need for RRC reconfiguration;

[0051] FIG6 is a schematic diagram of the interaction process between a terminal device and a network device according to the first embodiment of the configuration method of the present application;

[0052] FIG7 is a schematic diagram of the interaction process between a terminal device and a network device according to the second embodiment of the configuration method of the present application;

[0053] FIG8 is a schematic diagram of the interaction process between a terminal device and a network device according to the third embodiment of the configuration method of the present application;

[0054] FIG9 is a schematic diagram of the scene interaction process of the fourth embodiment of the configuration method of the present application.

[0055] The purpose of this application, its features, and advantages will be further described in conjunction with the embodiments and with reference to the accompanying drawings. The accompanying drawings illustrate specific embodiments of this application, which will be described in more detail below. These drawings and the accompanying text are not intended to limit the scope of the present application in any way, but rather to illustrate the concepts of this application to those skilled in the art by reference to specific embodiments.

[0056] Implementation Methods of the Application

[0057] Exemplary embodiments will be described in detail herein, with examples illustrated in the accompanying drawings. In the following description, when referring to the drawings, identical numerals in different figures represent identical or similar elements, unless otherwise indicated. The embodiments described in the following exemplary embodiments are not intended to represent all embodiments consistent with the present application. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present application, as detailed in the appended claims.

[0058] It should be noted that, in this document, the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device comprising a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, an element defined by the sentence "comprising a ..." does not exclude the presence of other identical elements in the process, method, article or device comprising the element. In addition, components, features, and elements with the same name in different embodiments of the present application may have the same meaning or different meanings, and their specific meanings need to be determined by their explanation in the specific embodiment or further combined with the context of the 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 solely to distinguish information of the same type from one another. For example, without departing from the scope of this disclosure, 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 term "if," as used herein, may be interpreted as "upon," "when," or "in response to a determination." Furthermore, as used herein, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context indicates otherwise. It should be further understood that the terms "comprising" and "including" indicate the presence of the recited features, steps, operations, elements, components, items, types, and / or groups, but do not preclude the presence, occurrence, or addition of one or more other features, steps, operations, elements, components, items, types, and / or groups. The terms "or," "and / or," "including at least one of the following," etc., as used herein, may be interpreted as inclusive, meaning any one or any combination. For example, “comprising at least one of the following: A, B, C” means “any of the following: A; B; C; A and B; A and C; B and C; A and B and C”; and for another example, “A, B or C” or “A, B and / or C” means “any of the following: A; B; C; A and B; A and C; B and C; A and B and C”. An exception to this definition will occur only when a combination of elements, functions, steps or operations are inherently mutually exclusive in some manner.

[0060] It should be understood that, although the various steps in the flowchart in the embodiment of the present application are shown in sequence according to the indication of the arrows, these steps are not necessarily performed in sequence in the order indicated by the arrows. Unless clearly stated herein, the execution of these steps is not strictly limited in order, and they can be performed in other orders. Moreover, at least a portion of the steps in the figure may include multiple sub-steps or multiple stages, and these sub-steps or stages are not necessarily performed at the same time, but can be performed at different times, and their execution order is not necessarily performed in sequence, but can be performed in turn or alternately with at least a portion of other steps or sub-steps or stages of other steps.

[0061] As used herein, the words "if" and "if" may be interpreted as "at the time of" or "when" or "in response to determining" or "in response to detecting," depending on the context. Similarly, the phrases "if it is determined" or "if (stated condition or event) is detected" may be interpreted as "when it is determined" or "in response to the determination" or "when detecting (stated condition or event)" or "in response to detecting (stated condition or event)," depending on the context.

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

[0063] It should be understood that the specific embodiments described herein are only used to explain the present application and are not intended to limit the present application.

[0064] In the subsequent description, the use of suffixes such as "module", "component" or "unit" to represent elements is only for the purpose of facilitating the description of the present application and has no specific meaning. Therefore, "module", "component" or "unit" can be used interchangeably.

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

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

[0067] The subsequent description will be made by taking a mobile terminal as an example. It will be understood by those skilled in the art that, in addition to components specifically used for mobile purposes, the configuration according to the embodiments of the present application can also be applied to fixed-type terminals.

[0068] Please refer to Figure 1, which is a schematic diagram of the hardware structure of a mobile terminal for implementing various embodiments of the present application. The mobile terminal 100 may include components such as 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. Those skilled in the art will appreciate that the mobile terminal structure shown in Figure 1 does not limit the mobile terminal. The mobile terminal may include more or fewer components than shown, or may combine certain components, or arrange the components differently.

[0069] The following is a detailed introduction to the various components of the mobile terminal in conjunction with Figure 1:

[0070] The RF unit 101 can be used to send and receive information or receive signals during calls. Specifically, it receives downlink information from the base station and transmits it to the processor 110 for processing. It also transmits uplink data to the base station. Typically, the RF unit 101 includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a low-noise amplifier, a duplexer, and more. Furthermore, the RF unit 101 can communicate with the network and other devices via wireless communication. The above-mentioned 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. A mobile terminal, through WiFi module 102, enables users to send and receive emails, browse web pages, and access streaming media, providing wireless broadband Internet access. Although FIG1 illustrates WiFi module 102, it is understood that it is not a required component of the mobile terminal and can be omitted as needed without altering the essence of the invention.

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

[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 from still images or videos captured by an image capture device (such as a camera) in video capture mode or image capture mode. The processed image frames may be displayed on the display unit 106. The image frames processed by the GPU 1041 may be stored in the memory 109 (or other storage medium) or transmitted via the RF unit 101 or the WiFi module 102. The microphone 1042 can receive sound (audio data) in various operating modes, such as phone call mode, recording mode, and voice recognition mode, and process such sound into audio data. In phone call mode, the processed audio (voice) data may be converted into a format that can be transmitted to a mobile communication base station via the RF unit 101. The microphone 1042 may implement various 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, or 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 based on the brightness of the ambient light, and the proximity sensor can turn off the display panel 1061 and / or the backlight when the mobile terminal 100 is brought to your ear. An accelerometer, a type of motion sensor, can detect acceleration in all directions (typically three axes) and, when stationary, can detect the magnitude and direction of gravity. This can be used for applications that recognize the phone's posture (e.g., switching between landscape and portrait modes, related games, magnetometer posture calibration), vibration recognition-related functions (e.g., pedometer, tapping), and other functions. Other sensors that may be configured on a mobile phone, such as a fingerprint sensor, pressure sensor, iris sensor, molecular sensor, gyroscope, barometer, hygrometer, thermometer, infrared sensor, etc., are not described 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] The user input unit 107 can be used to receive input digital or character information and generate key signal input related to user settings and function control of the mobile terminal. Optionally, the user input unit 107 may include a touch panel 1071 and other input devices 1072. The touch panel 1071, also known as a touch screen, can detect user touch operations on or near it (for example, operations performed on or near the touch panel 1071 using a finger, stylus, or any other suitable object or accessory) and drive corresponding connected devices according to pre-set programs. The 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 detects signals generated by the touch operation, transmitting the signals to the touch controller. The touch controller receives the touch information from the touch detection device, converts it into touch point coordinates, and then sends it to the processor 110. The touch controller can also receive and execute commands from the processor 110. Furthermore, the touch panel 1071 can be implemented using various types of sensors, including resistive, capacitive, infrared, and surface acoustic wave. In addition to the touch panel 1071, the user input unit 107 may further include other input devices 1072. Optionally, the other input devices 1072 may include, but are not limited to, one or more of a physical keyboard, function keys (such as volume control keys, power keys, etc.), a trackball, a mouse, a joystick, etc., and the specifics are not limited here.

[0077] Optionally, the touch panel 1071 may overlay 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. The processor 110 then provides a corresponding visual output on the display panel 1061 based on the type of touch event. Although in FIG1 , the touch panel 1071 and the display panel 1061 are shown as two separate components to implement the input and output functions of the mobile terminal, in some embodiments, the touch panel 1071 and the display panel 1061 may be integrated to implement the input and output functions of the mobile terminal, which is not limited to this specific embodiment.

[0078] The interface unit 108 serves as an interface through which at least one external device can be connected to the 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, etc. The interface unit 108 may be used to receive input (e.g., data information, power, etc.) from an external device and transmit the received input to one or more elements within the mobile terminal 100 or may be used to transmit data between the mobile terminal 100 and an external device.

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

[0080] Processor 110 is the control center of the mobile terminal, connecting all components of the mobile terminal using various interfaces and circuits. By running or executing software programs and / or modules stored in memory 109 and accessing data stored in memory 109, it executes various functions of the mobile terminal and processes data, thereby providing overall monitoring of the mobile terminal. Processor 110 may include one or more processing units; preferably, processor 110 may integrate an application processor and a modem processor. Optionally, the application processor primarily handles the operating system, user interface, and application programs, while the modem processor primarily handles wireless communications. It is understood that the modem processor may not be integrated into processor 110.

[0081] The mobile terminal 100 may further include a power supply 111 (such as a battery) for supplying power to various components. Preferably, the power supply 111 may be logically connected to the processor 110 via a power management system, thereby enabling the power management system to manage charging, discharging, and power consumption.

[0082] Although not shown in FIG. 1 , the mobile terminal 100 may further include a Bluetooth module, etc., which will not be described in detail here.

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

[0084] Please refer to Figure 2, which is a communication network system architecture diagram provided in an embodiment of the present application. The communication network system is an LTE system of 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 an operator's IP service 204, which are connected in sequence.

[0085] Optionally, UE201 may be the above-mentioned terminal 100, which will not be described in detail here.

[0086] E-UTRAN 202 includes eNodeB 2021 and other eNodeBs 2022 . Optionally, eNodeB 2021 may be connected to other eNodeBs 2022 via a backhaul (eg, an X2 interface). eNodeB 2021 is connected to EPC 203 , and eNodeB 2021 may provide UE 201 with access to EPC 203 .

[0087] The EPC 203 may include an MME (Mobility Management Entity) 2031, an HSS (Home Subscriber Server) 2032, other MMEs 2033, an SGW (Serving Gate Way) 2034, a PGW (PDN Gate Way) 2035, and a PCRF (Policy and Charging Rules Function) 2036. Optionally, the MME 2031 is a control node that processes signaling between the UE 201 and the EPC 203, providing bearer and connection management. The HSS 2032 provides registers for managing functions such as the Home Location Register (not shown) and stores user-specific information such as service features and data rates. All user data can be sent through SGW2034. PGW2035 can provide IP address allocation and other functions for UE 201. PCRF2036 is the policy and charging control policy decision point for service data flows and IP bearer resources. It selects and provides available policy and charging control decisions for the policy and charging execution function unit (not shown in the figure).

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

[0089] Although the above introduction takes 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., which are not limited here.

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

[0091] FIG3 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 principles and beneficial effects are similar and will not be repeated 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 is a schematic diagram of the hardware structure of a network node 150 provided in this application. Network node 150 includes: a memory 1501 and a processor 1502. Memory 1501 is used to store program instructions, and processor 1502 is used to call the program instructions in memory 1501 to execute the steps performed by the first node in the first embodiment of the above method. The implementation principles and beneficial effects are similar and will not be repeated 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 implemented in the form of software function modules can be stored in a computer-readable storage medium. The software function modules stored in a storage medium include a number of instructions for causing a computer device (which can be a personal computer, server, or network device, etc.) or a processor to execute some of the steps of the methods of various embodiments of the present application.

[0096] Technical terms involved in this embodiment:

[0097] CPA: Conditional PSCell Addition, conditional primary and secondary cell addition;

[0098] CPC: Conditional PSCell Change, conditional primary and secondary cell switching;

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

[0100] PCell: Primary Cell, primary cell;

[0101] PSCell: Primary SCG Cell, primary and secondary cell;

[0102] SN: Secondary Node, auxiliary node;

[0103] MN: Master Node, master node;

[0104] RRC reconfiguration, RRC reconfiguration;

[0105] CPC SCG change: CPC switch;

[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 and secondary cell handover;

[0108] SN Change Required: SN switching request;

[0109] SN Addition procedure: SN addition procedure;

[0110] SN Addition Req: SN addition request;

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

[0112] SN Modification Request Acknowledge: SN modification request confirmation.

[0113] 5 , FIG5 is a flowchart showing a scenario interaction for an SN initiated inter-SN continuous or subsequent CPC scenario, supporting configuration of execution conditions for continuous or subsequent CPC without the need for RRC reconfiguration, according to an embodiment of the present application.

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

[0115] 1. The source SN initiates an SN Change Required message to the MN. The message carries the candidate PSCell list 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 the list of recommended candidate PSCells received from the source SN. The candidate SN allocates CPC resource configuration for the candidate PSCell and sends it to the MN.

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

[0118] 4. The MN initiates an SN Modification Request message to each candidate SN. The message includes the information of the candidate PSCell accepted by other candidate SNs (such as SSB frequency, PCI, etc.) and its corresponding condReconfigId.

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

[0120] 5. Based on the information provided by the MN, the candidate PSCell is configured to the CPC execution conditions of other candidate PSCells and / or updates 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 the SN Modification Request Acknowledge.

[0121] Optionally, the candidate PSCell may not be configured with CPC execution conditions for certain candidate PSCells (such as based on neighboring cell relations or historical switching records, etc.). Not configuring CPC execution conditions means that after the UE switches to the PSCell, it is not necessary to perform conditional evaluation on 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 via an RRC Reconfiguration message. The UE maintains the execution conditions and CPC condition configuration of each candidate PSCell.

[0123] 7. After the UE executes CPC switching to a target candidate PSCell, the condition configuration of the target candidate PSCell is applied, and 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 continued to be evaluated.

[0124] In this technical solution, a conditional reconfiguration message is sent by a network device to enable a terminal device to configure the execution conditions for continuous or subsequent CPCs. This method, designed for SN initiated inter-SN continuous or subsequent CPC scenarios, supports configuring the execution conditions for continuous or subsequent CPCs without requiring RRC reconfiguration, meeting the requirements of these scenarios.

[0125] First embodiment

[0126] 6 , the first embodiment of the present application proposes a configuration method, including the following steps:

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

[0128] S30: The terminal device receives a condition reconfiguration message to configure execution conditions for continuous or subsequent CPCs.

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

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

[0131] Therefore, for the SN initiated inter-SN continuous or subsequent CPC scenario, a method is proposed to support the configuration of execution conditions for continuous or subsequent CPC without the need for RRC reconfiguration, which meets the scenario requirements.

[0132] Second embodiment

[0133] 7 , based on the above embodiment, a second embodiment of the present application proposes a configuration method, which further includes the following steps before step S20:

[0134] S10: Determine or generate a conditional reconfiguration message based on the configuration information.

[0135] Optionally, the 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 conditional configurations and / or measurement configurations to other candidate PSCells according to the secondary node modification request message;

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

[0139] The first network node determines, generates, or updates a conditional reconfiguration message according to the secondary node modification request confirmation message.

[0140] Optionally, the first network node is a MN, and the second network node is a 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 to other candidate PSCells determined or generated by the second network node includes at least one of the following: a conditional reconfiguration ID, a CPC execution condition, and a conditional RRC reconfiguration message.

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

[0144] Optionally, when the second network node does not determine or generate conditional configurations for other candidate PSCells, the terminal device does 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, the process further includes:

[0146] The third network node requests the candidate network node set to allocate resources according to the secondary node change request message.

[0147] Optionally, the first network node allocates a conditional reconfiguration ID to the candidate PSCell to which resources are successfully allocated.

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

[0149] Recommended candidate PSCell list;

[0150] Execution conditions corresponding to the recommended candidate PSCell;

[0151] Measurement configuration.

[0152] In the technical solution of this application, a network device determines or generates a conditional reconfiguration message based on configuration information and sends the conditional reconfiguration message to enable the terminal device to configure the execution conditions for continuous or subsequent CPC. The conditional reconfiguration message includes the conditional configuration of the target PSCell in the SN to other candidate PSCells. This application proposes a method for supporting the configuration of the execution conditions for continuous or subsequent CPC without the need for RRC reconfiguration in SN initiated inter-SN continuous or subsequent CPC scenarios, meeting the scenario requirements.

[0153] Third embodiment

[0154] 8 , the third embodiment of the present 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 conditional configurations and / or measurement configurations for other candidate PSCells according to the secondary node modification request message;

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

[0158] S14: The first network node determines, generates, or updates a condition reconfiguration message according to the secondary node modification request confirmation message and sends the message to the terminal device, so that the terminal device configures execution conditions for continuous or subsequent CPCs.

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

[0160] Optionally, the second network node is a 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 to other candidate PSCells determined or generated by the second network node includes at least one of the following: a conditional reconfiguration ID, a CPC execution condition, and a conditional RRC reconfiguration message.

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

[0164] Optionally, when the second network node does not determine or generate conditional configurations for other candidate PSCells, the terminal device does 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, the process further includes:

[0166] The third network node requests the candidate network node set to allocate resources according to the secondary node change request message.

[0167] Optionally, the first network node allocates a conditional reconfiguration ID to the candidate PSCell to which resources are successfully allocated.

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

[0169] In the technical solution of this application, a network device determines or generates a conditional reconfiguration message based on configuration information and sends the conditional reconfiguration message to enable the terminal device to configure the execution conditions for continuous or subsequent CPC. The conditional reconfiguration message includes the conditional configuration of the target PSCell in the SN to other candidate PSCells. This application proposes a method for supporting the configuration of the execution conditions for continuous or subsequent CPC without the need for RRC reconfiguration in SN initiated inter-SN continuous or subsequent CPC scenarios, meeting the scenario requirements.

[0170] Fourth embodiment

[0171] As shown in FIG9 , based on the above embodiment, a fourth embodiment of the present application proposes a configuration method, taking the terminal device as an example of a UE, the method includes the steps of:

[0172] 1. The source SN (i.e., PSCell) initiates an SN Change Required message to the MN (i.e., PCell). The SN Change Required message carries the candidate PSCell list recommended by the source SN (e.g., PSCell A, PSCell B, PSCell C) and the corresponding execution conditions (e.g., 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 SN Addition Req includes the recommended candidate PSCell list received from the source SN. The candidate SN allocates CPC resource configuration (condRRCReconfig A, condRRCReconfig B, condRRCReconfig C) for the candidate PSCell and sends it to the MN.

[0174] 3. When the MN determines or generates a conditional reconfiguration message (i.e., CondReconfigToAddMod), it assigns a condReconfigId to each candidate PSCell. Each condReconfigId corresponds to a 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 initiates an SN Modification Request message to each candidate SN. The message includes the information of the candidate PSCell accepted by other candidate SNs (such as SSB frequency, PCI, etc.) and its corresponding condReconfigId.

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

[0177] 5. Based on the information provided by the MN, the candidate PSCell is configured to the CPC execution conditions of other candidate PSCells and / or the measurement configuration in the corresponding CPC configuration is updated. 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 the 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, for updating the measurement configuration in the corresponding CPC configuration, it means that when the CPC resource configuration allocated by the candidate SN to the candidate PSCell in step 2 does not include the execution conditions configured in step 5 (that is, the MeasConfig measurement configuration in the condition configuration does not include the configured execution conditions), the corresponding MeasConfig needs to be updated.

[0182] Optionally, the candidate PSCell may not be configured with CPC execution conditions or condition configurations of certain candidate PSCells (such as based on neighboring cell relationships or historical switching records, etc.). Not configuring CPC execution conditions or condition configurations means that after the UE CPC switches to the PSCell, it is not necessary to perform conditional evaluation on these candidate PSCells.

[0183] Optionally, if the candidate PSCell C is not configured with the execution condition of PSCell B in step 5, it means that the UE CPC does not perform the condition evaluation on 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 via RRCReconfiguration. The UE maintains the execution conditions and CPC condition configuration of each candidate PSCell.

[0185] 7. After the UE executes CPC switching to a target candidate PSCell, the condition configuration of the target candidate PSCell is applied, and 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 continued to be evaluated.

[0186] Optionally, if the SCG currently configured by the UE is PSCell, the VarConditionalReconfig stored and maintained by the UE 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, condRRCReconfig = A corresponds to the following configuration:

[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, condRRCReconfig = B corresponds to the following configuration:

[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 conditional evaluation and finds that PSCell A meets the CPC execution condition (ie, MeasId_A is satisfied). The UE performs a conditional switch to PSCell A and applies the configuration corresponding to condRRCReconfig = A. The UE updates the stored VarConditionalReconfig to:

[0203] condReconfigId=1, condRRCReconfig=A, CondReconfigExecCondSCG = MeasId_A (the current cell configuration continues to 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 conditional evaluation and finds that PSCell B meets the CPC execution condition (i.e., MeasId_A-B is satisfied). The UE performs conditional switching to PSCell B and applies the configuration corresponding to condRRCReconfig=B. The UE then updates the stored VarConditionalReconfig to:

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

[0208] condReconfigId = 2, condRRCReconfig = B, CondReconfigExecCondSCG = MeasId_A-B (the current cell configuration continues to be retained);

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

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

[0211] The present application also provides a configuration device, which is applied to a network device or is a network device, and includes:

[0212] The sending module is used to send a condition reconfiguration message to enable the terminal device to configure the execution conditions of continuous or subsequent CPCs.

[0213] Optionally, the device further comprises:

[0214] The determining or generating module is used to determine or generate a conditional reconfiguration message based on the configuration information.

[0215] Optionally, the determining or generating module is further configured 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 conditional configurations and / or measurement configurations to other candidate PSCells according to the secondary node modification request message;

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

[0219] The first network node determines, generates, or updates a conditional reconfiguration message according to the secondary node 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 to other candidate PSCells determined or generated by the second network node includes at least one of the following: a conditional reconfiguration ID, a CPC execution condition, and a conditional RRC reconfiguration message.

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

[0223] Optionally, when the second network node does not determine or generate conditional configurations for other candidate PSCells, the terminal device does 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, the process further includes:

[0225] The third network node requests the candidate network node set to allocate resources according to the secondary node change request message.

[0226] Optionally, the first network node allocates a conditional reconfiguration ID to the candidate PSCell to which resources are successfully allocated; and / or the secondary node change request message includes at least one of the following:

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

[0228] The present application also provides a configuration device, which is applied to a terminal device or is the terminal device, and includes:

[0229] The receiving module is used to receive a condition reconfiguration message to configure the execution conditions of continuous or subsequent CPCs.

[0230] Optionally, the conditional reconfiguration message includes a conditional configuration of the target PSCell in the SN to other candidate PSCells; 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 conditional configurations and / or measurement configurations to other candidate PSCells according to the secondary node modification request message;

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

[0234] The first network node determines, generates, or updates a conditional reconfiguration message according to the secondary node modification request confirmation message.

[0235] 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 IDs of other candidate PSCells;

[0236] The conditional configuration determined or generated by the second network node for connecting to another candidate PSCell includes at least one of the following:

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

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

[0239] Optionally, when the second network node does not determine or generate conditional configurations for other candidate PSCells, the terminal device does not perform conditional evaluation on the other candidate PSCells when switching to the second network node.

[0240] Optionally, after the terminal device executes CPC switching to the target candidate PSCell, the conditional configuration of the target PSCell is applied, the conditional configuration of other candidate PSCells is retained, and the execution conditions and / or conditional RRC reconfiguration message of the PSCell to other candidate PSCells are updated according to the conditional configuration of the target PSCell.

[0241] An embodiment of the present application also provides a communication system, comprising the terminal device described in any of the above embodiments, and the network device described in any of the above embodiments.

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

[0243] An embodiment of the present application further provides a storage medium having a computer program stored thereon. When the computer program is executed by a processor, the configuration method as described in any of the above embodiments is implemented.

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

[0245] An embodiment of the present application further provides a computer program product, which includes computer program code. When the computer program code runs on a computer, the computer executes the methods in the various possible implementation modes described above.

[0246] An embodiment of the present application also provides a chip, including a memory and a processor, wherein the memory is used to store computer programs, and the processor is used to call and run the computer programs from the memory, so that a device equipped with the chip executes the methods in the various possible implementation modes as described above.

[0247] It is understood that the above scenarios are merely examples and do not limit 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, those skilled in the art will appreciate that with the evolution of system architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of this application will also be applicable to similar technical problems.

[0248] The serial numbers of the above embodiments of the present application are for description only and do not represent the advantages or disadvantages of the embodiments.

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

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

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

[0252] In this application, the description of each embodiment has its own focus. For parts that are not described or recorded in detail in a certain embodiment, please refer to the relevant description of other embodiments.

[0253] The various technical features of the technical solution of this application can be combined arbitrarily. In order to make the description concise, not all possible combinations of the various 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 this application.

[0254] Through the description of the above implementation methods, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of software plus the necessary general hardware platform, and of course 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 the present application is essentially or the part that contributes to the prior art can be embodied in the form of a software product, which is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) as mentioned above, and includes a number of instructions for enabling a terminal device (which can be a mobile phone, computer, server, controlled terminal, or network device, etc.) to execute the method of each embodiment of the present application.

[0255] In the above embodiments, all or part of the embodiments can be implemented using software, hardware, firmware, or any combination thereof. When implemented using software, all or part of the embodiments can be implemented in the form of 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 processes or functions according to the embodiments of the present application are 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, the 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, optical fiber, digital subscriber line) or wireless (e.g., infrared, wireless, microwave, etc.) means. The storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server or data center that integrates one or more available media. Available media can be magnetic media (e.g., floppy disks, storage disks, magnetic tapes), optical media (e.g., DVDs), or semiconductor media (e.g., solid-state disks (SSDs)).

[0256] The above are only preferred embodiments of the present application and do not limit the patent scope of the present application. Any equivalent structure or equivalent process transformation made using the contents of the present application specification and drawings, or directly or indirectly applied in other related technical fields, are also included in the patent protection scope of the present application.

Claims

1. A configuration method, wherein: Includes steps: S20: Send a condition reconfiguration message to enable the terminal device to configure the execution conditions of the continuous CPC.

2. The method according to claim 1, wherein: The conditional reconfiguration message includes the conditional configuration of the target PSCell in the SN to other candidate PSCells; and / or, before the step S20, the step further includes: S10: Determine or generate a conditional reconfiguration message based on the configuration information.

3. The method according to claim 2, wherein: The step S10 comprises: 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 conditional configuration and / or measurement configuration to other candidate PSCells according to the secondary node modification request message; The second network node sends the conditional configuration and / or measurement configuration to other candidate PSCells to the first network node through a secondary node modification request confirmation message; The first network node determines, generates or updates a conditional reconfiguration message according to the secondary node modification request confirmation message.

4. The method according to claim 3, wherein: The method further comprises at least one of the following: 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; The conditional configuration to other candidate PSCells determined or generated by the second network node includes at least one of the following: a conditional reconfiguration ID, a CPC execution condition, and a conditional RRC reconfiguration message; The conditional configuration to the other candidate PSCell determined or generated by the second network node is associated with the conditional reconfiguration ID of the other candidate PSCell; When the second network node does not determine or generate conditional configurations for other candidate PSCells, the terminal device does not perform conditional evaluation on the other candidate PSCells when switching to the second network node.

5. The method according to claim 3, wherein: Before the first network node sends the secondary node modification request message to the candidate network node set, the method further includes: The resource allocation is requested from the candidate network node set according to the secondary node change request message of the third network node.

6. The method according to claim 5, wherein: The first network node allocates a conditional reconfiguration ID to a candidate PSCell to which resources are successfully allocated; and / or the secondary node change request message includes at least one of the following: Recommended candidate PSCell list; The execution conditions corresponding to the recommended candidate PSCell; Measurement configuration.

7. A configuration method, wherein: Includes steps: S30: Receive a condition reconfiguration message to configure execution conditions of the continuous CPC.

8. The method according to claim 7, wherein: The conditional reconfiguration message includes a conditional configuration of the target PSCell in the SN to other candidate PSCells; and / or, 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 conditional configuration and / or measurement configuration to other candidate PSCells according to the secondary node modification request message; The second network node sends the conditional configuration and / or measurement configuration to other candidate PSCells to the first network node through a secondary node modification request confirmation message; The first network node determines, generates or updates a conditional reconfiguration message according to the secondary node modification request confirmation message.

9. The method according to claim 8, wherein: The method further comprises at least one of the following: 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, Conditional reconfiguration IDs of other candidate PSCells; The conditional configuration determined or generated by the second network node to other candidate PSCells includes at least one of the following: Conditional reconfiguration ID, CPC execution conditions, Conditional RRC reconfiguration message; The conditional configuration to the other candidate PSCell determined or generated by the second network node is associated with the conditional reconfiguration ID of the other candidate PSCell; When the second network node does not determine or generate conditional configurations for other candidate PSCells, the terminal device does not perform conditional evaluation on the other candidate PSCells when switching to the second network node; After the terminal device executes CPC switching to the target candidate PSCell, the conditional configuration of the target PSCell is applied, the conditional configurations of other candidate PSCells are retained, and the execution conditions and / or conditional RRC reconfiguration messages of the PSCell to other candidate PSCells are updated according to the conditional configuration of the target PSCell.

10. A communication device, wherein: include: A memory and a processor, wherein a configuration program is stored in the memory, and when the configuration program is executed by the processor, the configuration method according to claim 1 or 7 is implemented.

11. A storage medium, wherein: The storage medium stores a computer program, and when the computer program is executed by the processor, the configuration method according to claim 1 or 7 is implemented.

Images