Processing method, communication device, and storage medium

Abstract

The application provides a processing method, a communication device and a storage medium. The processing method comprises the following steps: in response to the first content satisfying the first condition, performing layer two reset and / or releasing configuration parameters. Through the technical scheme, the technical mechanism of cell switching can be improved, thereby supporting reduction of memory occupation of the terminal device, and / or ensuring consistency between the configuration content of the terminal device and the network device.

Description

Technical Field

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

[0002] During cell handover, performing a Layer 2 reset and / or releasing configuration parameters is one solution for handling cell handover failures.

[0003] In the process of conceiving and implementing this application, the inventors discovered at least the following problems: the technical mechanism for cell handover in the existing protocol is imperfect. For example, the mechanism for performing Layer 2 reset and / or releasing configuration parameters is imperfect, which may lead to the occupation of terminal device memory and / or inconsistency between configuration content and network device. Therefore, it is necessary to improve the technical mechanism for cell handover.

[0004] The preceding description is intended to provide general background information and does not necessarily constitute prior art. Summary of the Invention

[0005] The main objective of this application is to provide a processing method, communication device, and computer-readable storage medium, which aims to improve the technical mechanism of cell handover, thereby supporting the reduction of memory usage of terminal devices, and / or ensuring the consistency of terminal device configuration content with network devices.

[0006] This application provides a processing method applicable to terminal devices (such as mobile phones), comprising the following steps:

[0007] S2: In response to the first content satisfying the first condition, perform layer 2 reset and / or release configuration parameters.

[0008] Optionally, the first content includes at least one of the following:

[0009] The selected community safety signage remains unchanged;

[0010] The signage remains unchanged to ensure community safety.

[0011] The security signage for the target residential area remains unchanged.

[0012] Try triggering mobility switching at level 1-2;

[0013] Community selection results;

[0014] Reasons for the community's decision to initiate the initiative.

[0015] Optionally, the method further includes at least one of the following:

[0016] The configuration information for triggering mobility handover at layer 1 to layer 2 includes at least one of the following: the service cell security does not change the identifier, the target cell security does not change the identifier, and the attempt to trigger mobility handover at layer 1 to layer 2.

[0017] Cell selection results include candidate cells for triggering mobility at each of the first and second layers.

[0018] Reasons for initiating cell selection include cell selection initiated due to failure of the primary cell group radio link;

[0019] Reasons for initiating cell selection include cell selection initiated due to failure of synchronization reconfiguration of the main cell group.

[0020] Optionally, the first condition is met if at least one of the following is included:

[0021] There is an attempt to trigger mobility handover at layer 1-2, and the selected cell security unchanging identifier is different from the serving cell security unchanging identifier;

[0022] There is an attempt to trigger mobility handover at layer 1-2, and the selected cell security unchanged identifier is different from the target cell security unchanged identifier;

[0023] The cell selection result is a layer-1-2 mobility candidate cell, and the selected cell security unchanging identifier is different from the serving cell security unchanging identifier;

[0024] The cell selection result is a layer-1-2 mobility candidate cell, and the selected cell's security-unchanged identifier is different from the target cell's security-unchanged identifier;

[0025] Cell selection initiated due to failure of the primary cell group radio link, and the selected cell security unchanging identifier is different from the serving cell security unchanging identifier;

[0026] Cell selection initiated due to failure of the primary cell group radio link, and the selected cell security unchanged identifier is different from the target cell security unchanged identifier;

[0027] The cell selection was initiated due to the failure of the main cell group synchronization reconfiguration, and the selected cell's security status indicator is different from that of the serving cell;

[0028] The cell selection was initiated because the main cell group synchronization reconfiguration failed, and the selected cell's security unchanged identifier is different from the target cell's security unchanged identifier;

[0029] There is an attempt to trigger mobility handover at layer 1 to layer 2. The cell selection result is a candidate cell for mobility handover triggered at layer 1 to layer 2, and the selected cell security unchanging identifier is different from the serving cell security unchanging identifier.

[0030] There is an attempt to trigger mobility handover at layer 1 to layer 2. The cell selection result is a candidate cell for mobility handover triggered at layer 1 to layer 2, and the selected cell's security unchanged identifier is different from the target cell's security unchanged identifier.

[0031] There are instances of attempted layer 1-2 triggered mobility handover, cell selection initiated due to failure of the primary cell group radio link, cell selection result being a layer 1-2 triggered mobility candidate cell, and the selected cell security unchanging identifier being different from the serving cell security unchanging identifier;

[0032] There are attempts to trigger mobility handover at layer 1 to layer 2, cell selection initiated due to failure of the primary cell group radio link, cell selection result is a layer 1 to layer 2 mobility candidate cell, and the selected cell security unchanging identifier is different from the target cell security unchanging identifier;

[0033] There are instances of attempts to trigger mobility handover at layer 1 to layer 2, cell selection initiated due to failure of primary cell group synchronization reconfiguration, cell selection results being layer 1 to layer 2 mobility candidate cells, and the selected cell security unchanging identifier being different from the serving cell security unchanging identifier.

[0034] There are instances of attempts to trigger mobility handover at layer 1 to layer 2, cell selection initiated due to failure of primary cell group synchronization reconfiguration, cell selection results being layer 1 to layer 2 mobility candidate cells, and the selected cell security unchanging identifier being different from the target cell security unchanging identifier.

[0035] This application also provides a processing method applicable to network devices (such as base stations), comprising the following steps:

[0036] S1: Send Layer 1-2 trigger mobility handover configuration information so that the terminal device responds to the first content meeting the first condition by performing Layer 2 reset and / or releasing configuration parameters.

[0037] Optionally, the first content includes at least one of the following:

[0038] The selected community safety signage remains unchanged;

[0039] The signage remains unchanged to ensure community safety.

[0040] The security signage for the target residential area remains unchanged.

[0041] Try triggering mobility switching at level 1-2;

[0042] Community selection results;

[0043] Reasons for the community's decision to initiate the initiative.

[0044] Optionally, the method further includes at least one of the following:

[0045] The configuration information for triggering mobility handover at layer 1 to layer 2 includes at least one of the following: the service cell security does not change the identifier, the target cell security does not change the identifier, and the attempt to trigger mobility handover at layer 1 to layer 2.

[0046] Cell selection results include candidate cells for triggering mobility at each of the first and second layers.

[0047] Reasons for initiating cell selection include cell selection initiated due to failure of the primary cell group radio link;

[0048] Reasons for initiating cell selection include cell selection initiated due to failure of synchronization reconfiguration of the main cell group.

[0049] Optionally, the first condition is met if at least one of the following is included:

[0050] There is an attempt to trigger mobility handover at layer 1-2, and the selected cell security unchanging identifier is different from the serving cell security unchanging identifier;

[0051] There is an attempt to trigger mobility handover at layer 1-2, and the selected cell security unchanged identifier is different from the target cell security unchanged identifier;

[0052] The cell selection result is a layer-1-2 mobility candidate cell, and the selected cell security unchanging identifier is different from the serving cell security unchanging identifier;

[0053] The cell selection result is a layer-1-2 mobility candidate cell, and the selected cell's security-unchanged identifier is different from the target cell's security-unchanged identifier;

[0054] Cell selection initiated due to failure of the primary cell group radio link, and the selected cell security unchanging identifier is different from the serving cell security unchanging identifier;

[0055] Cell selection initiated due to failure of the primary cell group radio link, and the selected cell security unchanged identifier is different from the target cell security unchanged identifier;

[0056] The cell selection was initiated due to the failure of the main cell group synchronization reconfiguration, and the selected cell's security status indicator is different from that of the serving cell;

[0057] The cell selection was initiated because the main cell group synchronization reconfiguration failed, and the selected cell's security unchanged identifier is different from the target cell's security unchanged identifier;

[0058] There is an attempt to trigger mobility handover at layer 1 to layer 2. The cell selection result is a candidate cell for mobility handover triggered at layer 1 to layer 2, and the selected cell security unchanging identifier is different from the serving cell security unchanging identifier.

[0059] There is an attempt to trigger mobility handover at layer 1 to layer 2. The cell selection result is a candidate cell for mobility handover triggered at layer 1 to layer 2, and the selected cell's security unchanged identifier is different from the target cell's security unchanged identifier.

[0060] There are instances of attempted layer 1-2 triggered mobility handover, cell selection initiated due to failure of the primary cell group radio link, cell selection result being a layer 1-2 triggered mobility candidate cell, and the selected cell security unchanging identifier being different from the serving cell security unchanging identifier;

[0061] There are attempts to trigger mobility handover at layer 1 to layer 2, cell selection initiated due to failure of the primary cell group radio link, cell selection result is a layer 1 to layer 2 mobility candidate cell, and the selected cell security unchanging identifier is different from the target cell security unchanging identifier;

[0062] There are instances of attempts to trigger mobility handover at layer 1 to layer 2, cell selection initiated due to failure of primary cell group synchronization reconfiguration, cell selection results being layer 1 to layer 2 mobility candidate cells, and the selected cell security unchanging identifier being different from the serving cell security unchanging identifier.

[0063] There are instances of attempts to trigger mobility handover at layer 1 to layer 2, cell selection initiated due to failure of primary cell group synchronization reconfiguration, cell selection results being layer 1 to layer 2 mobility candidate cells, and the selected cell security unchanging identifier being different from the target cell security unchanging identifier.

[0064] This application also provides a communication device, including: a memory, a processor, and a processing program stored in the memory and executable on the processor, wherein the processing program, when executed by the processor, implements the steps of any of the processing methods described above.

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

[0066] This application also provides a computer-readable storage medium storing a processing program, which, when executed by a processor, implements the steps of any of the processing methods described above.

[0067] The technical solution of this application includes: in response to the first content satisfying the first condition, performing a layer 2 reset and / or releasing configuration parameters. Through this technical solution, the cell handover mechanism can be improved, thereby supporting a reduction in the memory usage of terminal devices, and / or ensuring the consistency of terminal device configuration content with network devices. Attached Figure Description

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

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

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

[0071] Figure 3 A schematic diagram of the hardware structure of a controller 140 provided in this application;

[0072] Figure 4 A schematic diagram of the hardware structure of a network node 150 provided in this application;

[0073] Figure 5 This is a flowchart illustrating the processing method according to the first embodiment;

[0074] Figure 6 This is a schematic diagram of the interaction timing according to the second embodiment;

[0075] Figure 7 This is a flowchart illustrating the processing method according to the sixth embodiment;

[0076] Figure 8 Schematic diagram of the processing apparatus provided in the embodiments of this application Figure 1 ;

[0077] Figure 9 Schematic diagram of the processing apparatus provided in the embodiments of this application Figure 2 ;

[0078] Figure 10 This is a schematic diagram of the structure of a communication device provided in an embodiment of this application.

[0079] 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. Detailed Implementation

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

[0081] 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, and / or, 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.

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

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

[0084] 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).”

[0085] It should be noted that step designations such as S1 and S2 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 S2 first and then S1, etc., but these should all be within the protection scope of this application.

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

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

[0088] The communication equipment mentioned in this application may be a terminal device (such as a mobile phone), a network device (such as a base station), or a chip (such as a SOC or a baseband chip with communication functions). The specific meaning needs to be clarified according to the context.

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

[0090] 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 terminal devices.

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

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

[0093] 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, a duplexer, etc. And / or, 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), 5G, and 6G.

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

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

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

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

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

[0099] 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 touch screen, can collect touch operations on or near the user (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 two parts: touch detection device and touch controller. Optionally, touch detection device detects the user's touch position and the signal generated by the touch operation, and transmits the signal to touch controller; touch controller receives touch information from touch detection device, converts it into touch point coordinates, sends it to processor 110, and can receive and execute commands from processor 110. And / or, 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.

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

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

[0102] 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.). And / or, 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.

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

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

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

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

[0107] Please see Figure 2 , Figure 2This application provides a communication network system architecture diagram. The communication network system is a New Radio (NR) system based on general mobile communication technology. The NR 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.

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

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

[0110] EPC203 may include an MME (Mobility Management Entity) 2031, an HSS (Home Subscriber Server) 2032, other MMEs 2033, an SGW (Serving Gateway) 2034, a PGW (Packet Data Network Gateway) 2035, and a 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).

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

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

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

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

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

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

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

[0118] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented in 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 (DSL)) 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, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., solid-state disk, SSD), etc.

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

[0120] Technical terms used in the embodiments of this application:

[0121] MR: Measurement Report;

[0122] CU: Central Unit;

[0123] LTM: L1 / L2 Triggered Mobility;

[0124] BM: Beam Management;

[0125] LTM Configuration Update: Layer 1-2 triggers mobility configuration update;

[0126] LTM Configuration Update Acknowledge: Layer 1-2 triggers confirmation of mobility configuration update;

[0127] TCI: Transmission Configuration Indicator;

[0128] MAC: Medium Access Control;

[0129] MAC CE: MAC Control Element, Media Access Control Unit;

[0130] CG: Configured Grant;

[0131] HO: Handover;

[0132] Handover Request: Request switching;

[0133] CHO: Conditional Handover;

[0134] PDCCH: Physical Downlink Control Channel;

[0135] MIMO: Multiple Input Multiple Output;

[0136] MR-DC: MultiRadio-DualConnectivity.

[0137] First Embodiment

[0138] Reference Figure 5 , Figure 5 The flowchart illustrating the processing method according to the first embodiment is shown below. The processing method of this application embodiment can be applied to a terminal device (such as a mobile phone) and includes the following steps:

[0139] S2: In response to the first content satisfying the first condition, perform layer 2 reset and / or release configuration parameters.

[0140] Optionally, the first content includes the selected cell security not changing identifier, the serving cell security not changing identifier, the target cell security not changing identifier, attempting layer 1-2 to trigger mobility handover, cell selection result, and the reason for initiating cell selection.

[0141] Optionally, at least one of the following—serving cell security does not change identifier, target cell security does not change identifier, and attempt to trigger mobility handover at layer 1 to layer 2—is carried in the layer 1 to layer 2 mobility handover configuration information.

[0142] Optionally, the cell selection results include candidate cells for triggering mobility at layer 1 and layer 2.

[0143] Optionally, cell selection can be initiated for reasons including cell selection due to failure of the primary cell group radio link.

[0144] Optionally, the reason for initiating cell selection includes cell selection initiated due to failure of synchronization reconfiguration of the primary cell group.

[0145] Optionally, the first condition is met if at least one of the following is included:

[0146] There is an attempt to trigger mobility handover at layer 1-2, and the selected cell security unchanging identifier is different from the serving cell security unchanging identifier;

[0147] There is an attempt to trigger mobility handover at layer 1-2, and the selected cell security unchanged identifier is different from the target cell security unchanged identifier;

[0148] The cell selection result is a layer-1-2 mobility candidate cell, and the selected cell security unchanging identifier is different from the serving cell security unchanging identifier;

[0149] The cell selection result is a layer-1-2 mobility candidate cell, and the selected cell's security-unchanged identifier is different from the target cell's security-unchanged identifier;

[0150] Cell selection initiated due to failure of the primary cell group radio link, and the selected cell security unchanging identifier is different from the serving cell security unchanging identifier;

[0151] Cell selection initiated due to failure of the primary cell group radio link, and the selected cell security unchanged identifier is different from the target cell security unchanged identifier;

[0152] The cell selection was initiated due to the failure of the main cell group synchronization reconfiguration, and the selected cell's security status indicator is different from that of the serving cell;

[0153] The cell selection was initiated because the main cell group synchronization reconfiguration failed, and the selected cell's security unchanged identifier is different from the target cell's security unchanged identifier;

[0154] There is an attempt to trigger mobility handover at layer 1 to layer 2. The cell selection result is a candidate cell for mobility handover triggered at layer 1 to layer 2, and the selected cell security unchanging identifier is different from the serving cell security unchanging identifier.

[0155] There is an attempt to trigger mobility handover at layer 1 to layer 2. The cell selection result is a candidate cell for mobility handover triggered at layer 1 to layer 2, and the selected cell's security unchanged identifier is different from the target cell's security unchanged identifier.

[0156] There are instances of attempted layer 1-2 triggered mobility handover, cell selection initiated due to failure of the primary cell group radio link, cell selection result being a layer 1-2 triggered mobility candidate cell, and the selected cell security unchanging identifier being different from the serving cell security unchanging identifier;

[0157] There are attempts to trigger mobility handover at layer 1 to layer 2, cell selection initiated due to failure of the primary cell group radio link, cell selection result is a layer 1 to layer 2 mobility candidate cell, and the selected cell security unchanging identifier is different from the target cell security unchanging identifier;

[0158] There are instances of attempts to trigger mobility handover at layer 1 to layer 2, cell selection initiated due to failure of primary cell group synchronization reconfiguration, cell selection results being layer 1 to layer 2 mobility candidate cells, and the selected cell security unchanging identifier being different from the serving cell security unchanging identifier.

[0159] There are instances of attempts to trigger mobility handover at layer 1 to layer 2, cell selection initiated due to failure of primary cell group synchronization reconfiguration, cell selection results being layer 1 to layer 2 mobility candidate cells, and the selected cell security unchanging identifier being different from the target cell security unchanging identifier.

[0160] The technical solution of this embodiment, specifically by responding to the first content satisfying the first condition and performing layer 2 reset and / or release of configuration parameters, can improve the technical mechanism of cell handover, thereby supporting the reduction of terminal device memory usage and / or ensuring the consistency of terminal device configuration content with network device.

[0161] Second Embodiment

[0162] Reference Figure 6 , Figure 6 This is a schematic diagram of the interaction timing according to the second embodiment, as shown below. Figure 6 As shown, based on the first embodiment described above, the processing method further includes: the terminal device reporting a measurement report to the network device, and the network device sending a radio resource control reconfiguration signaling to the terminal device.

[0163] Optionally, the terminal device reports a measurement report to the network device (e.g., the source base station).

[0164] Optionally, the measurement report is a Layer 3 Measurement Report (MR).

[0165] Optionally, the source base station initiates Layer 1-2 mobility preparation, for example, by sending a Handover Request signaling.

[0166] Optionally, the source base station sends a handover request signaling to at least one candidate base station, such as the target base station and / or other base stations.

[0167] Optionally, Layer 1-2 mobility preparation is used to provide and / or obtain Layer 1-2 mobility configuration.

[0168] Optionally, the target base station and / or other base stations respond to the source base station by initiating Layer 1.2 mobility preparation, for example by sending a Handover Request Acknowledge signaling.

[0169] Optionally, the source base station, the target base station, and other base stations are all different Central Unit (CU) base stations.

[0170] Optionally, the handover request signaling and / or handover request confirmation signaling carries at least one of the following: LTM configuration identifier, LTM configuration, early uplink synchronization configuration, scheduling configuration, measurement configuration, serving cell security-invariant identifier, and candidate cell security-invariant identifier.

[0171] Optionally, the measurement configuration includes a layer 3 measurement configuration and / or a layer 1 measurement configuration.

[0172] Optionally, the Layer 1 measurement configuration also includes Layer 1-2 mobility events.

[0173] Optionally, a Tier 1-2 mobility event includes at least one of the following:

[0174] Event LTM2: The serving cell beam becomes worse than the absolute threshold;

[0175] Event LTM3: The beam of the candidate cell becomes more offset than the beam of the serving cell after compensation.

[0176] Event LTM4: The beam of candidate cell becomes better than the absolute threshold;

[0177] Event LTM5: The serving cell beam becomes worse than absolute threshold1 and the candidate cell beam becomes better than another absolute threshold2.

[0178] Optionally, a layer-one measurement event can be a beam management (BM) measurement event.

[0179] Optionally, the Layer 3 measurement configuration can be referenced in protocol TS 38.331 Release 18, 5.5.

[0180] Optionally, the source base station initiates a Layer 1-2 Mobility Configuration Update, for example, by sending a Layer 1-2 Mobility Configuration Update (LTM Configuration Update) signaling.

[0181] Optionally, the target base station and / or other base stations respond to the source base station by initiating a Layer 1 / 2 mobility configuration update, for example by sending a Layer 1 / 2 Mobility Configuration Update Acknowledge (LTM) signaling.

[0182] Optionally, the layer 1.2 mobility configuration update signaling and / or layer 1.2 mobility configuration update confirmation signaling carries at least one of the following: updated LTM configuration identifier, updated LTM configuration, updated advance uplink synchronization configuration, updated scheduling configuration, and updated measurement configuration.

[0183] Optionally, the source cell generates an LTM configuration, including at least one of the following: LTM configuration identifier, candidate cell LTM configuration, candidate cell security no-change identifier (NoSecurityChangeID), serving cell security no-change identifier (ServingCellNoSecurityChangeID), and attemptLTM-Switch. Other configurations can be found in protocol TS 38.300 Release 18, 6.3.2, LTM configuration (LTM-Config).

[0184] Optionally, the candidate cell LTM configuration includes candidate cell LTM configurations with the same center unit and / or candidate cell LTM configurations with different center units.

[0185] Optionally, the candidate cell security no-change identifier and / or the serving cell security no-change identifier are used to determine at least one of the following:

[0186] Whether the serving cell and the candidate cell are the same central unit cell;

[0187] Does the handover between the first and second mobility cells at the execution layer require security updates and / or parameter resets?

[0188] Should fast recovery be performed during handover between Layer 1 and Layer 2 mobile cells?

[0189] Perform layer 2 reset and / or release configuration parameters.

[0190] Optionally, the Radio Resource Control (RRC) reconfiguration signaling carries the LTM configuration and / or the LTM configuration generated by the source cell.

[0191] Optionally, the radio resource control reconfiguration signaling may also carry configurations from special cell configurations (SpCellConfig) and / or other configurations (OtherConfig), such as delay budget reporting configuration, overheat assist configuration, discontinuous period preference configuration, maximum bandwidth preference configuration, maximum carrier preference configuration, maximum MIMO layer preference configuration, and other configurations, which can be found in protocol TS 38.321 release 18, 5.3.5.5.7, 5.3.5.9.

[0192] Alternatively, other configurations can also control reconfiguration signaling carry-over and / or configuration via additional radio resources.

[0193] Optionally, the terminal device stores the LTM configuration.

[0194] Optionally, the terminal device sends a radio resource control reconfiguration completion signaling.

[0195] Optionally, the Radio Resource Control (RRC) reconfiguration completion signaling is used in response to the source cell sending the RRC reconfiguration signaling.

[0196] Optionally, the source cell can also be configured with multi-link dual-connection (MR-DC) and / or secondary cells (Scells) for terminal equipment, as can be found in TS 38.321 release 18, 5.3.5.3, 5.3.5.5.9.

[0197] Optionally, the source cell can be configured with multi-link dual-link and / or secondary cell via additional radio resource control reconfiguration signaling.

[0198] The technical solution of this embodiment specifically involves the terminal device reporting a measurement report to the network device, and the network device sending a radio resource control reconfiguration signaling to the terminal device, so that the terminal device receives and stores the LTM configuration, and then performs a layer 2 reset and / or releases the configuration parameters based on the LTM configuration. This can improve the technical mechanism of cell handover, thereby supporting the reduction of the terminal device's memory usage, and / or ensuring the consistency between the terminal device's configuration content and the network device's configuration content.

[0199] Third Embodiment

[0200] Based on any of the foregoing embodiments of this application, this embodiment further discloses the process by which a terminal device performs cell handover based on a layer-1-2 triggered mobility cell handover command.

[0201] Optionally, the source base station and / or serving cell may trigger early downlink synchronization.

[0202] Optionally, the source base station determines the candidate cells for early downlink synchronization by activating / deactivating the MAC CE based on the candidate cell TCI status.

[0203] Optionally, the measurement report includes a Layer 1 measurement report and / or a Layer 3 measurement report.

[0204] Optionally, the source base station and / or serving cell can trigger early downlink synchronization according to the following protocols: TS 38.321 Release 18, 5.18.36, 6.1.3.76.

[0205] Optionally, the source base station and / or serving cell may trigger early uplink synchronization.

[0206] Optionally, the source base station and / or serving cell can trigger early uplink synchronization with the candidate cell via PDCCH order.

[0207] Optionally, the terminal device sends a random access preamble to the candidate cell based on the received PDCCH order.

[0208] Optionally, the terminal device and the candidate cell may perform early uplink synchronization according to the following protocols: TS 38.321 Release 18.5.1 and TS 38.213 Release 18.8.21.

[0209] Optionally, the terminal device may report measurement results based on the measurement configuration and / or report measurement results when the candidate cell meets the measurement conditions, as per protocols TS 38.331 Release 18, 5.5 and TS 38.214 Release 18, 5.2.1.4.

[0210] Optionally, the source base station sends a Layer 1-2 trigger mobile cell handover command.

[0211] Optionally, the Layer 1-2 triggered mobile cell handover command carries the candidate cell identifier and / or advance time information, as can be found in protocol TS 38.321 Release 18, 6.1.3.75.

[0212] Optionally, the terminal device initiates Layer 1-2 to trigger a mobile cell handover, which can be referenced in protocols TS38.321 Release 18, 5.18.35 and TS 38.331 Release 18, 5.3.5.18.6.

[0213] Optionally, the terminal device is detached from the source cell and the target cell configuration is applied.

[0214] Optionally, when at least one candidate cell meets the candidate cell condition LTM execution condition, separation and synchronization with the target cell are performed.

[0215] Optionally, the terminal device starts timer T304.

[0216] Optionally, the terminal device initiates a random access procedure.

[0217] Optionally, if the terminal device does not have a target cell time advance and / or the target cell time advance value is at its maximum (e.g., FFF), then a random access procedure is initiated.

[0218] Optionally, a random access procedure is initiated when the LTM candidate time advance timer is not running and / or when the LTM candidate time advance timer expires.

[0219] Optionally, after the terminal device completes the random access process, the timer T304 is stopped.

[0220] Optionally, the terminal device completes conditional LTM cell handover.

[0221] Optionally, the terminal device sends a radio resource control reconfiguration completion signaling based on the configured grant (CG).

[0222] Optionally, the terminal device sends a radio resource control reconfiguration completion signaling based on the random access response uplink scheduling (UL Grant).

[0223] Optionally, the terminal device sends a radio resource control reconfiguration completion signaling to the target cell.

[0224] Optionally, when the terminal device performs a conditional LTM handover without random access and receives the first downlink data and / or uplink data scheduling, the conditional LTM handover is considered complete.

[0225] Optionally, the terminal device stops timer T304 after receiving an instruction from the underlying and / or MAC layer indicating that random access exemption has been completed.

[0226] Optionally, the source cell sends a cell switch notification to the target base station.

[0227] Optionally, the cell handover notification may carry the cell identifier and / or TCI status identifier, as can be found in TS38.473 Release 18, 9.2.2.15, and 9.2.2.16.

[0228] Optionally, if the terminal device fails to access the target cell, including random access failure and / or non-random access failure, please refer to protocol TS 38.331 release 18, 7.1.

[0229] Optionally, if the terminal device fails to access the target cell, including failing to receive uplink data scheduling and / or downlink data scheduling from the target cell, refer to protocol TS 38.321 release 18, 5.3.1, 5.4.1.

[0230] Optionally, if the terminal device fails to access the target cell during the T304 timer operation and / or the T304 timer times out, a radio resource control reconstruction procedure is initiated.

[0231] Optionally, after restoring the configuration of the terminal equipment in the source primary cell, the terminal equipment initiates a radio resource control reconstruction process.

[0232] The technical solution in this embodiment, which specifically executes cell handover by triggering a mobility cell handover command based on layer 1-2 of the terminal device, can improve the technical mechanism of cell handover, thereby reducing the memory usage of the terminal device and / or ensuring the consistency between the configuration content of the terminal device and the network device.

[0233] Fourth embodiment

[0234] Based on any of the foregoing embodiments of this application, this embodiment further discloses the process by which a terminal device performs a layer 2 reset and / or release of configuration parameters based on the first content.

[0235] Optionally, during the initial process of radio resource control reconstruction, the terminal device determines to perform a layer 2 reset and / or release configuration parameters, such as selecting a suitable cell.

[0236] Optionally, a suitable cell can be selected by referring to protocol TS 38.304 release 18, 5.2.

[0237] Optionally, the initial process for re-establishing radio resource control includes cell selection.

[0238] Optionally, in response to the first content satisfying the first condition, the terminal device performs a layer 2 reset and / or releases the configuration parameters.

[0239] Optionally, the first content includes at least one of the following: the selected community security unchanged sign, the service community security unchanged sign, and the target community security unchanged sign.

[0240] Optionally, the terminal device determines whether to perform a Layer 2 reset and / or release configuration parameters based on at least one of the selected cell security unchanged identifier, the serving cell security unchanged identifier, and the target cell security unchanged identifier.

[0241] Optionally, if the selected cell security unchanging identifier is the same as the serving cell security unchanging identifier, the terminal device performs Layer 1.2 to trigger rapid mobility recovery.

[0242] Optionally, if the selected cell security non-change identifier is the same as the target cell security non-change identifier, the terminal device performs Layer 1-2 triggering of rapid mobility recovery.

[0243] Optionally, if the selected cell security non-change identifier is different from the serving cell security non-change identifier, the terminal device performs a layer 2 reset and / or releases the configuration parameters.

[0244] Optionally, if the selected cell security non-change identifier is different from the target cell security non-change identifier, the terminal device performs a layer 2 reset and / or releases the configuration parameters.

[0245] Optionally, the first content also includes at least one of the following: attempt to trigger mobility handover at layer 1 / 2, cell selection result, and reason for initiating cell selection.

[0246] Optionally, the terminal device determines whether to perform a Layer 2 reset and / or release configuration parameters based on at least one of the following: the selected cell security does not change identifier, the serving cell security does not change identifier, the target cell security does not change identifier, an attempt to trigger a Layer 1-2 mobility handover, the cell selection result, and the reason for initiating the cell selection.

[0247] Optionally, when an LTM handover attempt is configured and the selected cell security non-change identifier is different from the serving cell security non-change identifier, the terminal device performs a Layer 2 reset and / or releases the configuration parameters.

[0248] Optionally, when LTM handover is configured to attempt, and the selected cell security non-change identifier is different from the target cell security non-change identifier, the terminal device performs a Layer 2 reset and / or releases the configuration parameters.

[0249] Optionally, when the selected cell is a Layer 1 Level 2 mobility candidate cell, and the selected cell security immutability identifier is different from the serving cell security immutability identifier, the terminal device performs a Layer 2 reset and / or releases the configuration parameters.

[0250] Optionally, when the selected cell is a Layer 1 Level 2 mobility candidate cell, and the selected cell's security immutability identifier is different from the target cell's security immutability identifier, the terminal device performs a Layer 2 reset and / or releases the configuration parameters.

[0251] Optionally, if cell selection is initiated due to the failure of the primary cell group radio link, and the selected cell security immutability identifier is different from the serving cell security immutability identifier, the terminal device performs a layer 2 reset and / or releases the configuration parameters.

[0252] Optionally, if cell selection is initiated due to the failure of the primary cell group radio link, and the selected cell security immutability identifier is different from the target cell security immutability identifier, the terminal device performs a layer 2 reset and / or releases the configuration parameters.

[0253] Optionally, if the cell selection initiated due to the failure of the primary cell group synchronization reconfiguration is different from the security immutability identifier of the selected cell and the security immutability identifier of the serving cell is different, the terminal device shall perform a layer 2 reset and / or release the configuration parameters.

[0254] Optionally, if the cell selection initiated due to the failure of the primary cell group synchronization reconfiguration, and the selected cell security immutability identifier is different from the target cell security immutability identifier, the terminal device shall perform a layer 2 reset and / or release the configuration parameters.

[0255] Optionally, when LTM handover is attempted, the selected cell is a Layer 1 Level 2 Mobility Candidate Cell, and the selected cell's Security Invariant Identifier is different from the Serving Cell's Security Invariant Identifier, the terminal device performs a Layer 2 reset and / or releases the configuration parameters.

[0256] Optionally, when LTM handover is attempted, the selected cell is a Layer 1 Level 2 Mobility Candidate Cell, and the selected cell's Security Invariant Identifier is different from the target cell's Security Invariant Identifier, the terminal device performs a Layer 2 reset and / or releases the configuration parameters.

[0257] Optionally, when the configuration includes attempts at LTM handover, cell selection initiated due to failure of the primary cell group radio link, the selected cell being a Layer 1 / 2 mobility candidate cell, and the selected cell's security immutability identifier being different from the serving cell's security immutability identifier, the terminal device performs a Layer 2 reset and / or releases the configuration parameters.

[0258] Optionally, when the configuration includes LTM handover attempt, cell selection initiated due to primary cell group radio link failure, the selected cell is a Layer 1 / 2 mobility candidate cell, and the selected cell security invariant identifier is different from the target cell security invariant identifier, the terminal device performs a Layer 2 reset and / or releases the configuration parameters.

[0259] Optionally, when the configuration includes an attempt to perform LTM handover, a cell selection initiated due to failure of primary cell group synchronization reconfiguration, a selected cell being a Layer 1 Level 2 mobility candidate cell, and the selected cell's security immutability identifier being different from the serving cell's security immutability identifier, the terminal device performs a Layer 2 reset and / or releases the configuration parameters.

[0260] Optionally, when the configuration includes an attempt to perform LTM handover, a cell selection initiated due to failure of primary cell group synchronization reconfiguration, a selected cell being a Layer 1 Level 2 mobility candidate cell, and the selected cell's security invariant identifier being different from the target cell's security invariant identifier, the terminal device performs a Layer 2 reset and / or releases the configuration parameters.

[0261] Optionally, the target cell security non-change identifier is the security non-change identifier configured for the cell handover triggered by the layer 1-2 mobility cell.

[0262] The technical solution of this embodiment specifically improves the cell handover mechanism by clarifying that the terminal device performs a Layer 2 reset and / or release configuration parameters based on at least one of the following: the selected cell security does not change identifier, the serving cell security does not change identifier, the target cell security does not change identifier, attempting Layer 1-2 mobility handover, the cell selection result, and the reason for initiating cell selection. This can support reducing the memory usage of the terminal device and / or ensuring the consistency between the configuration content of the terminal device and the network device.

[0263] Fifth Embodiment

[0264] Based on any of the foregoing embodiments of this application, this embodiment further discloses the process by which a terminal device performs a layer 2 reset and / or release of configuration parameters.

[0265] Optionally, performing a Layer 2 reset includes a MAC reset, as detailed in Protocol TS 38.321 Release 18, 5.12.

[0266] Optionally, the release configuration parameters include at least one of the following: release special cell configuration, primary cell group secondary cell, delay budget report configuration, overheating auxiliary configuration, multi-link dual-link configuration, non-continuous period preference configuration, maximum bandwidth preference configuration, maximum carrier preference configuration, and maximum MIMO layer preference configuration, as can be found in protocol TS 38.321 release 18, 5.3.7.3.

[0267] Optionally, releasing configuration parameters may include releasing configurations in other configurations, such as at least one of the following: delay budget report configuration, overheat assist configuration, discontinuous period preference configuration, maximum bandwidth preference configuration, maximum carrier preference configuration, and maximum MIMO layer preference configuration, as can be found in protocol TS 38.321 release 18, 5.3.5.9.

[0268] Optionally, the layer-1-2 triggering of fast mobility recovery includes at least one of the following:

[0269] After the cell selection is re-established in Radio Resource Control, Layer 1-2 triggers mobile cell handover;

[0270] Do not send a Radio Resource Control Reconstruction Request;

[0271] Do not initiate the wireless resource control reconstruction process.

[0272] Optionally, a synchronization reconfiguration failure includes at least one of the following: handover (HO) failure, conditional handover (CHO) failure, layer-1-2 triggered mobile cell handover failure, and T304 timer timeout.

[0273] Optionally, the serving cell security unchanging identifier includes: the serving cell security unchanging identifier stored in the current terminal device configuration, and / or the serving cell security unchanging identifier stored in a variable.

[0274] Optionally, the selected cell security non-change identifier includes: the candidate cell security non-change identifier in the Layer 1 Level 2 Triggered Mobility Configuration, and / or, the candidate cell security non-change identifier in the selected Layer 1 Level 2 Triggered Mobility Configuration.

[0275] Optionally, the terminal device may send a Radio Resource Control Reconstruction Request and / or trigger a Radio Resource Control Reconstruction Procedure based on the selected cell.

[0276] Optionally, triggering the Radio Resource Control (RRC) re-establishment process includes at least one of sending a RRC re-establishment request, accepting a RRC re-establishment request, and sending a RRC re-establishment completion message, as detailed in TS38.331 release 18, 5.3.7.4, and 5.3.5.5.

[0277] Optionally, the terminal device performs fast recovery or radio resource control reconstruction with the candidate cell of the source base station.

[0278] Optionally, the terminal device performs fast recovery or radio resource control reconstruction with the candidate cells of the target base station.

[0279] Optionally, the terminal device performs radio resource control reconstruction with other base stations.

[0280] By implementing the technical solution of this embodiment, specifically by having the terminal device perform a Layer 2 reset and / or release of configuration parameters, it is possible to ensure that the configuration parameters of the terminal device are consistent with those of the network device, thereby improving the technical mechanism of cell handover, and thus supporting the reduction of the memory usage of the terminal device, and / or ensuring the consistency of the configuration content of the terminal device with that of the network device.

[0281] Sixth Embodiment

[0282] Reference Figure 7 , Figure 7 This is a flowchart illustrating the processing method according to the sixth embodiment. The method described in this embodiment can be applied to network devices (such as base stations) and includes the following steps:

[0283] S1: Send Layer 1-2 trigger mobility handover configuration information so that the terminal device responds to the first content meeting the first condition by performing Layer 2 reset and / or releasing configuration parameters.

[0284] Optionally, the first content includes at least one of the following: the selected cell security does not change identifier, the serving cell security does not change identifier, the target cell security does not change identifier, attempting layer 1-2 to trigger mobility handover, cell selection result, and reason for initiating cell selection.

[0285] Optionally, the network device sends configuration parameters, including at least one of special cell configuration, other configuration, multi-link dual-link configuration, and secondary cell configuration.

[0286] Optionally, configuration parameters and / or Layer 1 / 2 trigger mobility handover configuration information are carried and / or configured via Radio Resource Control reconfiguration signaling.

[0287] Optionally, configuration parameters are carried and / or configured via at least one radio resource control reconfiguration signaling.

[0288] Optionally, at least one of the following—serving cell security does not change identifier, target cell security does not change identifier, and attempt to trigger mobility handover at layer 1 to layer 2—is carried in the layer 1 to layer 2 mobility handover configuration information.

[0289] Optionally, the cell selection results include candidate cells for triggering mobility at layer 1 and layer 2.

[0290] Optionally, cell selection can be initiated for reasons including cell selection due to failure of the primary cell group radio link.

[0291] Optionally, the reason for initiating cell selection includes cell selection initiated due to failure of synchronization reconfiguration of the primary cell group.

[0292] Optionally, the first condition is met if at least one of the following is included:

[0293] There is an attempt to trigger mobility handover at layer 1-2, and the selected cell security unchanging identifier is different from the serving cell security unchanging identifier;

[0294] There is an attempt to trigger mobility handover at layer 1-2, and the selected cell security unchanged identifier is different from the target cell security unchanged identifier;

[0295] The cell selection result is a layer-1-2 mobility candidate cell, and the selected cell security unchanging identifier is different from the serving cell security unchanging identifier;

[0296] The cell selection result is a layer-1-2 mobility candidate cell, and the selected cell's security-unchanged identifier is different from the target cell's security-unchanged identifier;

[0297] Cell selection initiated due to failure of the primary cell group radio link, and the selected cell security unchanging identifier is different from the serving cell security unchanging identifier;

[0298] Cell selection initiated due to failure of the primary cell group radio link, and the selected cell security unchanged identifier is different from the target cell security unchanged identifier;

[0299] The cell selection was initiated due to the failure of the main cell group synchronization reconfiguration, and the selected cell's security status indicator is different from that of the serving cell;

[0300] The cell selection was initiated because the main cell group synchronization reconfiguration failed, and the selected cell's security unchanged identifier is different from the target cell's security unchanged identifier;

[0301] There is an attempt to trigger mobility handover at layer 1 to layer 2. The cell selection result is a candidate cell for mobility handover triggered at layer 1 to layer 2, and the selected cell security unchanging identifier is different from the serving cell security unchanging identifier.

[0302] There is an attempt to trigger mobility handover at layer 1 to layer 2. The cell selection result is a candidate cell for mobility handover triggered at layer 1 to layer 2, and the selected cell's security unchanged identifier is different from the target cell's security unchanged identifier.

[0303] There are instances of attempted layer 1-2 triggered mobility handover, cell selection initiated due to failure of the primary cell group radio link, cell selection result being a layer 1-2 triggered mobility candidate cell, and the selected cell security unchanging identifier being different from the serving cell security unchanging identifier;

[0304] There are attempts to trigger mobility handover at layer 1 to layer 2, cell selection initiated due to failure of the primary cell group radio link, cell selection result is a layer 1 to layer 2 mobility candidate cell, and the selected cell security unchanging identifier is different from the target cell security unchanging identifier;

[0305] There are instances of attempts to trigger mobility handover at layer 1 to layer 2, cell selection initiated due to failure of primary cell group synchronization reconfiguration, cell selection results being layer 1 to layer 2 mobility candidate cells, and the selected cell security unchanging identifier being different from the serving cell security unchanging identifier.

[0306] There are instances of attempts to trigger mobility handover at layer 1 to layer 2, cell selection initiated due to failure of primary cell group synchronization reconfiguration, cell selection results being layer 1 to layer 2 mobility candidate cells, and the selected cell security unchanging identifier being different from the target cell security unchanging identifier.

[0307] Optionally, in response to the first content satisfying the first condition, the terminal device performs a layer 2 reset and / or releases the configuration parameters.

[0308] Optionally, the first content includes at least one of the following: the selected community security unchanged sign, the service community security unchanged sign, and the target community security unchanged sign.

[0309] Optionally, the terminal device determines whether to perform a Layer 2 reset and / or release configuration parameters based on at least one of the selected cell security unchanged identifier, the serving cell security unchanged identifier, and the target cell security unchanged identifier.

[0310] Optionally, if the selected cell security unchanging identifier is the same as the serving cell security unchanging identifier, the terminal device performs Layer 1.2 to trigger rapid mobility recovery.

[0311] Optionally, if the selected cell security non-change identifier is the same as the target cell security non-change identifier, the terminal device performs Layer 1-2 triggering of rapid mobility recovery.

[0312] Optionally, if the selected cell security non-change identifier is different from the serving cell security non-change identifier, the terminal device performs a layer 2 reset and / or releases the configuration parameters.

[0313] Optionally, if the selected cell security non-change identifier is different from the target cell security non-change identifier, the terminal device performs a layer 2 reset and / or releases the configuration parameters.

[0314] Optionally, the first content also includes at least one of the following: attempt to trigger mobility handover at layer 1 / 2, cell selection result, and reason for initiating cell selection.

[0315] Optionally, the terminal device determines whether to perform a Layer 2 reset and / or release configuration parameters based on at least one of the following: the selected cell security does not change identifier, the serving cell security does not change identifier, the target cell security does not change identifier, an attempt to trigger a Layer 1-2 mobility handover, the cell selection result, and the reason for initiating the cell selection.

[0316] Optionally, when an LTM handover attempt is configured and the selected cell security non-change identifier is different from the serving cell security non-change identifier, the terminal device performs a Layer 2 reset and / or releases the configuration parameters.

[0317] Optionally, when LTM handover is configured to attempt, and the selected cell security non-change identifier is different from the target cell security non-change identifier, the terminal device performs a Layer 2 reset and / or releases the configuration parameters.

[0318] Optionally, when the selected cell is a Layer 1 Level 2 mobility candidate cell, and the selected cell security immutability identifier is different from the serving cell security immutability identifier, the terminal device performs a Layer 2 reset and / or releases the configuration parameters.

[0319] Optionally, when the selected cell is a Layer 1 Level 2 mobility candidate cell, and the selected cell's security immutability identifier is different from the target cell's security immutability identifier, the terminal device performs a Layer 2 reset and / or releases the configuration parameters.

[0320] Optionally, if cell selection is initiated due to the failure of the primary cell group radio link, and the selected cell security immutability identifier is different from the serving cell security immutability identifier, the terminal device performs a layer 2 reset and / or releases the configuration parameters.

[0321] Optionally, if cell selection is initiated due to the failure of the primary cell group radio link, and the selected cell security immutability identifier is different from the target cell security immutability identifier, the terminal device performs a layer 2 reset and / or releases the configuration parameters.

[0322] Optionally, if the cell selection initiated due to the failure of the primary cell group synchronization reconfiguration is different from the security immutability identifier of the selected cell and the security immutability identifier of the serving cell is different, the terminal device shall perform a layer 2 reset and / or release the configuration parameters.

[0323] Optionally, if the cell selection initiated due to the failure of the primary cell group synchronization reconfiguration, and the selected cell security immutability identifier is different from the target cell security immutability identifier, the terminal device shall perform a layer 2 reset and / or release the configuration parameters.

[0324] Optionally, when LTM handover is attempted, the selected cell is a Layer 1 Level 2 Mobility Candidate Cell, and the selected cell's Security Invariant Identifier is different from the Serving Cell's Security Invariant Identifier, the terminal device performs a Layer 2 reset and / or releases the configuration parameters.

[0325] Optionally, when LTM handover is attempted, the selected cell is a Layer 1 Level 2 Mobility Candidate Cell, and the selected cell's Security Invariant Identifier is different from the target cell's Security Invariant Identifier, the terminal device performs a Layer 2 reset and / or releases the configuration parameters.

[0326] Optionally, when the configuration includes attempts at LTM handover, cell selection initiated due to failure of the primary cell group radio link, the selected cell being a Layer 1 / 2 mobility candidate cell, and the selected cell's security immutability identifier being different from the serving cell's security immutability identifier, the terminal device performs a Layer 2 reset and / or releases the configuration parameters.

[0327] Optionally, when the configuration includes LTM handover attempt, cell selection initiated due to primary cell group radio link failure, the selected cell is a Layer 1 / 2 mobility candidate cell, and the selected cell security invariant identifier is different from the target cell security invariant identifier, the terminal device performs a Layer 2 reset and / or releases the configuration parameters.

[0328] Optionally, when the configuration includes an attempt to perform LTM handover, a cell selection initiated due to failure of primary cell group synchronization reconfiguration, a selected cell being a Layer 1 Level 2 mobility candidate cell, and the selected cell's security immutability identifier being different from the serving cell's security immutability identifier, the terminal device performs a Layer 2 reset and / or releases the configuration parameters.

[0329] Optionally, when the configuration includes an attempt to perform LTM handover, a cell selection initiated due to failure of primary cell group synchronization reconfiguration, a selected cell being a Layer 1 Level 2 mobility candidate cell, and the selected cell's security invariant identifier being different from the target cell's security invariant identifier, the terminal device performs a Layer 2 reset and / or releases the configuration parameters.

[0330] Optionally, the target cell security non-change identifier is the security non-change identifier configured for the cell handover triggered by the layer 1-2 mobility cell.

[0331] The technical solution of this embodiment specifically sends layer 1-2 mobility handover configuration information through the network device, so that the terminal device responds to the first content meeting the first condition, performs layer 2 reset and / or release of configuration parameters, and ensures that the configuration parameters of the terminal device are consistent with those of the network device. This can improve the technical mechanism of cell handover, thereby supporting the reduction of the terminal device's memory usage, and / or ensuring the consistency of the terminal device's configuration content with that of the network device.

[0332] Seventh Embodiment

[0333] Reference Figure 8 , Figure 8 Schematic diagram of the processing apparatus provided in the embodiments of this application Figure 1 The device can be mounted on or is the terminal device in the above method embodiments. Figure 8 The processing apparatus shown can be used to perform some or all of the functions described in the method embodiments above. For example... Figure 8 As shown, the processing device 1100 includes:

[0334] Processing module 1101 is used to perform layer 2 reset and / or release configuration parameters in response to the first content satisfying the first condition.

[0335] Optionally, the first content includes at least one of the following:

[0336] The selected community safety signage remains unchanged;

[0337] The signage remains unchanged to ensure community safety.

[0338] The security signage for the target residential area remains unchanged.

[0339] Try triggering mobility switching at level 1-2;

[0340] Community selection results;

[0341] Reasons for the community's decision to initiate the initiative.

[0342] Optionally, the device further includes at least one of the following:

[0343] The configuration information for triggering mobility handover at layer 1 to layer 2 includes at least one of the following: the service cell security does not change the identifier, the target cell security does not change the identifier, and the attempt to trigger mobility handover at layer 1 to layer 2.

[0344] Cell selection results include candidate cells for triggering mobility at each of the first and second layers.

[0345] Reasons for initiating cell selection include cell selection initiated due to failure of the primary cell group radio link;

[0346] Reasons for initiating cell selection include cell selection initiated due to failure of synchronization reconfiguration of the main cell group.

[0347] Optionally, the first condition is met if at least one of the following is included:

[0348] There is an attempt to trigger mobility handover at layer 1-2, and the selected cell security unchanging identifier is different from the serving cell security unchanging identifier;

[0349] There is an attempt to trigger mobility handover at layer 1-2, and the selected cell security unchanged identifier is different from the target cell security unchanged identifier;

[0350] The cell selection result is a layer-1-2 mobility candidate cell, and the selected cell security unchanging identifier is different from the serving cell security unchanging identifier;

[0351] The cell selection result is a layer-1-2 mobility candidate cell, and the selected cell's security-unchanged identifier is different from the target cell's security-unchanged identifier;

[0352] Cell selection initiated due to failure of the primary cell group radio link, and the selected cell security unchanging identifier is different from the serving cell security unchanging identifier;

[0353] Cell selection initiated due to failure of the primary cell group radio link, and the selected cell security unchanged identifier is different from the target cell security unchanged identifier;

[0354] The cell selection was initiated due to the failure of the main cell group synchronization reconfiguration, and the selected cell's security status indicator is different from that of the serving cell;

[0355] The cell selection was initiated because the main cell group synchronization reconfiguration failed, and the selected cell's security unchanged identifier is different from the target cell's security unchanged identifier;

[0356] There is an attempt to trigger mobility handover at layer 1 to layer 2. The cell selection result is a candidate cell for mobility handover triggered at layer 1 to layer 2, and the selected cell security unchanging identifier is different from the serving cell security unchanging identifier.

[0357] There is an attempt to trigger mobility handover at layer 1 to layer 2. The cell selection result is a candidate cell for mobility handover triggered at layer 1 to layer 2, and the selected cell's security unchanged identifier is different from the target cell's security unchanged identifier.

[0358] There are instances of attempted layer 1-2 triggered mobility handover, cell selection initiated due to failure of the primary cell group radio link, cell selection result being a layer 1-2 triggered mobility candidate cell, and the selected cell security unchanging identifier being different from the serving cell security unchanging identifier;

[0359] There are attempts to trigger mobility handover at layer 1 to layer 2, cell selection initiated due to failure of the primary cell group radio link, cell selection result is a layer 1 to layer 2 mobility candidate cell, and the selected cell security unchanging identifier is different from the target cell security unchanging identifier;

[0360] There are instances of attempts to trigger mobility handover at layer 1 to layer 2, cell selection initiated due to failure of primary cell group synchronization reconfiguration, cell selection results being layer 1 to layer 2 mobility candidate cells, and the selected cell security unchanging identifier being different from the serving cell security unchanging identifier.

[0361] There are instances of attempts to trigger mobility handover at layer 1 to layer 2, cell selection initiated due to failure of primary cell group synchronization reconfiguration, cell selection results being layer 1 to layer 2 mobility candidate cells, and the selected cell security unchanging identifier being different from the target cell security unchanging identifier.

[0362] The processing apparatus provided in this application embodiment can execute the technical solutions shown in the above method embodiments. Its implementation principle and beneficial effects are similar, and will not be described again here.

[0363] Eighth embodiment

[0364] Reference Figure 9 , Figure 9 Schematic diagram of the processing apparatus provided in the embodiments of this application Figure 2 The device can be mounted on or is the network device in the above method embodiments. Figure 9 The processing apparatus shown can be used to perform some or all of the functions described in the method embodiments above. For example... Figure 9 As shown, the processing apparatus 1200 includes:

[0365] The sending module 1201 is used to send layer 1-2 mobility handover configuration information so that the terminal device can perform layer 2 reset and / or release configuration parameters in response to the first content meeting the first condition.

[0366] Optionally, the first content includes at least one of the following:

[0367] The selected community safety signage remains unchanged;

[0368] The signage remains unchanged to ensure community safety.

[0369] The security signage for the target residential area remains unchanged.

[0370] Try triggering mobility switching at level 1-2;

[0371] Community selection results;

[0372] Reasons for the community's decision to initiate the initiative.

[0373] Optionally, the device further includes at least one of the following:

[0374] The configuration information for triggering mobility handover at layer 1 to layer 2 includes at least one of the following: the service cell security does not change the identifier, the target cell security does not change the identifier, and the attempt to trigger mobility handover at layer 1 to layer 2.

[0375] Cell selection results include candidate cells for triggering mobility at each of the first and second layers.

[0376] Reasons for initiating cell selection include cell selection initiated due to failure of the primary cell group radio link;

[0377] Reasons for initiating cell selection include cell selection initiated due to failure of synchronization reconfiguration of the main cell group.

[0378] Optionally, the first condition is met if at least one of the following is included:

[0379] There is an attempt to trigger mobility handover at layer 1-2, and the selected cell security unchanging identifier is different from the serving cell security unchanging identifier;

[0380] There is an attempt to trigger mobility handover at layer 1-2, and the selected cell security unchanged identifier is different from the target cell security unchanged identifier;

[0381] The cell selection result is a layer-1-2 mobility candidate cell, and the selected cell security unchanging identifier is different from the serving cell security unchanging identifier;

[0382] The cell selection result is a layer-1-2 mobility candidate cell, and the selected cell's security-unchanged identifier is different from the target cell's security-unchanged identifier;

[0383] Cell selection initiated due to failure of the primary cell group radio link, and the selected cell security unchanging identifier is different from the serving cell security unchanging identifier;

[0384] Cell selection initiated due to failure of the primary cell group radio link, and the selected cell security unchanged identifier is different from the target cell security unchanged identifier;

[0385] The cell selection was initiated due to the failure of the main cell group synchronization reconfiguration, and the selected cell's security status indicator is different from that of the serving cell;

[0386] The cell selection was initiated because the main cell group synchronization reconfiguration failed, and the selected cell's security unchanged identifier is different from the target cell's security unchanged identifier;

[0387] There is an attempt to trigger mobility handover at layer 1 to layer 2. The cell selection result is a candidate cell for mobility handover triggered at layer 1 to layer 2, and the selected cell security unchanging identifier is different from the serving cell security unchanging identifier.

[0388] There is an attempt to trigger mobility handover at layer 1 to layer 2. The cell selection result is a candidate cell for mobility handover triggered at layer 1 to layer 2, and the selected cell's security unchanged identifier is different from the target cell's security unchanged identifier.

[0389] There are instances of attempted layer 1-2 triggered mobility handover, cell selection initiated due to failure of the primary cell group radio link, cell selection result being a layer 1-2 triggered mobility candidate cell, and the selected cell security unchanging identifier being different from the serving cell security unchanging identifier;

[0390] There are attempts to trigger mobility handover at layer 1 to layer 2, cell selection initiated due to failure of the primary cell group radio link, cell selection result is a layer 1 to layer 2 mobility candidate cell, and the selected cell security unchanging identifier is different from the target cell security unchanging identifier;

[0391] There are instances of attempts to trigger mobility handover at layer 1 to layer 2, cell selection initiated due to failure of primary cell group synchronization reconfiguration, cell selection results being layer 1 to layer 2 mobility candidate cells, and the selected cell security unchanging identifier being different from the serving cell security unchanging identifier.

[0392] There are instances of attempts to trigger mobility handover at layer 1 to layer 2, cell selection initiated due to failure of primary cell group synchronization reconfiguration, cell selection results being layer 1 to layer 2 mobility candidate cells, and the selected cell security unchanging identifier being different from the target cell security unchanging identifier.

[0393] The processing apparatus provided in this application embodiment can execute the technical solutions shown in the above method embodiments. Its implementation principle and beneficial effects are similar, and will not be described again here.

[0394] See Figure 10 , Figure 10 This is a schematic diagram of the structure of a communication device provided in an embodiment of this application. Figure 10 As shown, the communication device 160 described in this embodiment can be a terminal device (or a component that can be used in a terminal device) or a network device (or a component that can be used in a network device) mentioned in the foregoing method embodiments. The communication device 160 can be used to implement the methods corresponding to the terminal device or network device described in the above method embodiments, as detailed in the descriptions in the above method embodiments.

[0395] The communication device 160 may include one or more processors 161, which may also be referred to as processing units, and can perform certain control or processing functions. The processor 161 may be a general-purpose processor or a dedicated processor, such as a baseband processor or a central processing unit. The baseband processor can be used to process communication protocols and communication data, while the central processing unit can be used to control the communication device, execute software programs, and process data from the software programs.

[0396] Optionally, the processor 161 may also store instructions 163 or data (e.g., intermediate data). Optionally, instructions 163 may be executed by the processor 161, causing the communication device 160 to perform the methods described in the above method embodiments corresponding to the terminal device or network device.

[0397] Optionally, the communication device 160 may include a circuit that can perform the functions of sending, receiving, or communicating in the foregoing method embodiments.

[0398] Optionally, the communication device 160 may include one or more memories 162, which may store instructions 164 that can be executed on the processor 161 to cause the communication device 160 to perform the methods described in the above method embodiments.

[0399] Optionally, the memory 162 may also store data. The processor 161 and the memory 162 may be configured separately or integrated together.

[0400] Optionally, the communication device 160 may further include a transceiver 165 and / or an antenna 166. The processor 161, which may be referred to as a processing unit, controls the communication device 160 (terminal device, core network device, or wireless access network device). The transceiver 165, which may be referred to as a transceiver unit, transceiver, transceiver circuit, or transceiver, is used to implement the transceiver functions of the communication device 160.

[0401] Optionally, if the communication device 160 is used to implement the operation corresponding to the terminal device in the above embodiments, for example, the transceiver 165 and / or the processor 161 may perform a layer two reset and / or release configuration parameters in response to the first content satisfying the first condition.

[0402] Optionally, the specific implementation process of processor 161 and transceiver 165 can be found in the relevant descriptions of the above embodiments, and will not be repeated here.

[0403] Optionally, if the communication device 160 is used to implement the operation corresponding to the network device in the above embodiments, for example, the transceiver 165 can send Layer 1-2 triggered mobility handover configuration information so that the terminal device can perform Layer 2 reset and / or release configuration parameters in response to the first content satisfying the first condition.

[0404] Optionally, the specific implementation process of processor 161 and transceiver 165 can be found in the relevant descriptions of the above embodiments, and will not be repeated here.

[0405] The processor 161 and transceiver 165 described in this application can be implemented on ICs (Integrated Circuits), analog integrated circuits, RFICs (Radio Frequency Integrated Circuits), mixed-signal integrated circuits, ASICs (Application Specific Integrated Circuits), PCBs (Printed Circuit Boards), electronic devices, etc. The processor 161 and transceiver 165 can also be manufactured using various integrated circuit process technologies, such as CMOS (Complementary Metal Oxide Semiconductor), NMOS (N-type Metal-Oxide-Semiconductor), PMOS (Positive channel Metal Oxide Semiconductor), BJT (Bipolar Junction Transistor), Bipolar CMOS (BiCMOS), silicon germanium (SiGe), gallium arsenide (GaAs), etc. In this application, the communication device can be a terminal device (such as a mobile phone) or a network device (such as a base station), depending on the context. Furthermore, the terminal device can be implemented in various forms. For example, the terminal devices described in this application may include mobile terminals such as mobile phones, tablets, laptops, handheld computers, personal digital assistants (PDAs), portable media players (PMPs), navigation devices, wearable devices, smart bracelets, pedometers, etc., as well as fixed terminal devices such as digital TVs and desktop computers.

[0406] Although the communication devices described above are exemplified as terminal devices or network devices, the scope of the communication devices described in this application is not limited to the aforementioned terminal devices or network devices, and the structure of the communication devices may vary. Figure 10 There are limitations. Communication equipment can be a standalone device or part of a larger device.

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

[0408] This application also provides a communication device, including a memory and a processor. The memory stores a processing program, and when the processing program is executed by the processor, it implements the steps of the processing method in any of the above embodiments.

[0409] The communication equipment mentioned in this application may be a terminal device (such as a mobile phone), a network device (such as a base station), or a chip (such as a SOC or a baseband chip with communication functions). The specific meaning needs to be clarified according to the context.

[0410] This application also provides a computer-readable storage medium storing a processing program, which, when executed by a processor, implements the steps of the processing method in any of the above embodiments.

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

[0412] 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. This application also provides a chip, including a memory and a processor. The memory stores a computer program, and the processor retrieves and runs the computer program from the memory, causing a device with the chip installed to perform the methods described in the various possible implementations above.

[0413] 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, those skilled in the art will know that 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. The sequence numbers of the embodiments of this application above are merely for description and do not represent the superiority or inferiority of the embodiments. The steps in the method of the embodiments of this application can be adjusted, merged, and deleted according to actual needs. The units in the device of the embodiments of this application can be merged, divided, and deleted according to actual needs. 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 later, they are generally not repeated for the sake of brevity. When understanding the technical solutions of this application, for the same or similar terms, concepts, technical solutions, and / or application scenario descriptions that are not described in detail later, you can refer to their previous related detailed descriptions. In this application, the descriptions of each embodiment have their own emphasis. For the parts that are not described or recorded in detail in a certain embodiment, you can refer to the relevant descriptions of other embodiments. 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.

[0414] 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 device, or network device, etc.) to execute the methods of each embodiment of this application. In the above embodiments, they can be implemented entirely or partially by software, hardware, firmware, or any combination thereof. When implemented using software, they can be implemented entirely or partially 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 flow or function according to the embodiments of this application is generated. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. 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 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 accessible to 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, memory disks, magnetic tapes), optical media (e.g., DVDs), or semiconductor media (e.g., solid-state drives (SSDs)). 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 based on the content of this 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 processing method, characterized in that, Applied to terminal devices, including the following steps: S2: In response to the first content satisfying the first condition, perform layer 2 reset and / or release configuration parameters; The first content includes: the selected cell security does not change the identifier, and at least one of the following: the serving cell security does not change the identifier, the target cell security does not change the identifier, the cell selection result, the attempt to trigger mobility handover at layer 1 or 2, and the reason for initiating cell selection; The first condition includes at least one of the following: Cell selection initiated due to failure of the primary cell group radio link, and the selected cell security unchanging identifier is different from the serving cell security unchanging identifier; Cell selection initiated due to failure of the primary cell group radio link, and the selected cell security unchanged identifier is different from the target cell security unchanged identifier; The cell selection was initiated due to the failure of the main cell group synchronization reconfiguration, and the selected cell's security status indicator is different from that of the serving cell; The cell selection was initiated because the main cell group synchronization reconfiguration failed, and the selected cell's security unchanged identifier is different from the target cell's security unchanged identifier; There is an attempt to trigger mobility handover at layer 1 to layer 2. The cell selection result is a candidate cell for mobility handover triggered at layer 1 to layer 2, and the selected cell security unchanging identifier is different from the serving cell security unchanging identifier. There is an attempt to trigger mobility handover at layer 1 to layer 2. The cell selection result is a candidate cell for mobility handover triggered at layer 1 to layer 2, and the selected cell's security unchanged identifier is different from the target cell's security unchanged identifier.

2. The method as described in claim 1, characterized in that, It also includes at least one of the following: The configuration information for triggering mobility handover at layer 1 to layer 2 includes at least one of the following: the service cell security does not change the identifier, the target cell security does not change the identifier, and the attempt to trigger mobility handover at layer 1 to layer 2. Cell selection results include candidate cells for triggering mobility at each of the first and second layers. Reasons for initiating cell selection include cell selection initiated due to failure of the primary cell group radio link; Reasons for initiating cell selection include cell selection initiated due to failure of synchronization reconfiguration of the main cell group.

3. The method as described in claim 2, characterized in that, The first condition must be met, including at least one of the following: There is an attempt to trigger mobility handover at layer 1-2, and the selected cell security unchanging identifier is different from the serving cell security unchanging identifier; There is an attempt to trigger mobility handover at layer 1-2, and the selected cell security unchanged identifier is different from the target cell security unchanged identifier; The cell selection result is a layer-1-2 mobility candidate cell, and the selected cell security unchanging identifier is different from the serving cell security unchanging identifier; The cell selection result is a layer-1-2 mobility candidate cell, and the selected cell security no-change identifier is different from the target cell security no-change identifier; There are instances of attempted layer 1-2 triggered mobility handover, cell selection initiated due to failure of the primary cell group radio link, cell selection result being a layer 1-2 triggered mobility candidate cell, and the selected cell security unchanging identifier being different from the serving cell security unchanging identifier; There are attempts to trigger mobility handover at layer 1 to layer 2, cell selection initiated due to failure of the primary cell group radio link, cell selection result is a layer 1 to layer 2 mobility candidate cell, and the selected cell security unchanging identifier is different from the target cell security unchanging identifier; There are instances of attempts to trigger mobility handover at layer 1 to layer 2, cell selection initiated due to failure of primary cell group synchronization reconfiguration, cell selection results being layer 1 to layer 2 mobility candidate cells, and the selected cell security unchanging identifier being different from the serving cell security unchanging identifier. There are instances of attempts to trigger mobility handover at layer 1 to layer 2, cell selection initiated due to failure of primary cell group synchronization reconfiguration, cell selection results being layer 1 to layer 2 mobility candidate cells, and the selected cell security unchanging identifier being different from the target cell security unchanging identifier.

4. A processing method, characterized in that, Applied to network devices, including the following steps: S1: Send Layer 1-2 trigger mobility handover configuration information so that the terminal device responds to the first content meeting the first condition by performing Layer 2 reset and / or releasing configuration parameters; The first content includes: the selected cell security does not change the identifier, and at least one of the following: the serving cell security does not change the identifier, the target cell security does not change the identifier, the cell selection result, the attempt to trigger mobility handover at layer 1 or 2, and the reason for initiating cell selection; The first condition includes at least one of the following: Cell selection initiated due to failure of the primary cell group radio link, and the selected cell security unchanging identifier is different from the serving cell security unchanging identifier; Cell selection initiated due to failure of the primary cell group radio link, and the selected cell security unchanged identifier is different from the target cell security unchanged identifier; The cell selection was initiated due to the failure of the main cell group synchronization reconfiguration, and the selected cell's security status indicator is different from that of the serving cell; The cell selection was initiated because the main cell group synchronization reconfiguration failed, and the selected cell's security unchanged identifier is different from the target cell's security unchanged identifier; There is an attempt to trigger mobility handover at layer 1 to layer 2. The cell selection result is a candidate cell for mobility handover triggered at layer 1 to layer 2, and the selected cell security unchanging identifier is different from the serving cell security unchanging identifier. There is an attempt to trigger mobility handover at layer 1 to layer 2. The cell selection result is a candidate cell for mobility handover triggered at layer 1 to layer 2, and the selected cell's security unchanged identifier is different from the target cell's security unchanged identifier.

5. The method as described in claim 4, characterized in that, It also includes at least one of the following: The configuration information for triggering mobility handover at layer 1 to layer 2 includes at least one of the following: the service cell security does not change the identifier, the target cell security does not change the identifier, and the attempt to trigger mobility handover at layer 1 to layer 2. Cell selection results include candidate cells for triggering mobility at each of the first and second layers. Reasons for initiating cell selection include cell selection initiated due to failure of the primary cell group radio link; Reasons for initiating cell selection include cell selection initiated due to failure of synchronization reconfiguration of the main cell group.

6. The method as described in claim 5, characterized in that, The first condition must be met, including at least one of the following: There is an attempt to trigger mobility handover at layer 1-2, and the selected cell security unchanging identifier is different from the serving cell security unchanging identifier; There is an attempt to trigger mobility handover at layer 1-2, and the selected cell security unchanged identifier is different from the target cell security unchanged identifier; The cell selection result is a layer-1-2 mobility candidate cell, and the selected cell security unchanging identifier is different from the serving cell security unchanging identifier; The cell selection result is a layer-1-2 mobility candidate cell, and the selected cell security no-change identifier is different from the target cell security no-change identifier; There are instances of attempted layer 1-2 triggered mobility handover, cell selection initiated due to failure of the primary cell group radio link, cell selection result being a layer 1-2 triggered mobility candidate cell, and the selected cell security unchanging identifier being different from the serving cell security unchanging identifier; There are attempts to trigger mobility handover at layer 1 to layer 2, cell selection initiated due to failure of the primary cell group radio link, cell selection result is a layer 1 to layer 2 mobility candidate cell, and the selected cell security unchanging identifier is different from the target cell security unchanging identifier; There are instances of attempts to trigger mobility handover at layer 1 to layer 2, cell selection initiated due to failure of primary cell group synchronization reconfiguration, cell selection results being layer 1 to layer 2 mobility candidate cells, and the selected cell security unchanging identifier being different from the serving cell security unchanging identifier. There are instances of attempts to trigger mobility handover at layer 1 to layer 2, cell selection initiated due to failure of primary cell group synchronization reconfiguration, cell selection results being layer 1 to layer 2 mobility candidate cells, and the selected cell security unchanging identifier being different from the target cell security unchanging identifier.

7. A communication device, characterized in that, include: A memory, a processor, and a processing program stored in the memory and executable on the processor, the processing program being executed by the processor to implement the steps of the processing method as described in any one of claims 1 to 6.

8. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program, which is executed by a processor to implement the steps of the processing method as described in any one of claims 1 to 6.

Images