Cell handover method and electronic device

Abstract

Embodiments of the present application disclose a cell switching method and electronic equipment, the method comprising: a first device receiving a first switching message of a first cell sent by a second device, the first cell being a neighbor cell; successfully switching to the first cell according to the first switching message; when the first cell receives an RRC release message sent by the second device and the first device has traffic, sending a first service request message to the second device and receiving a first service rejection message sent by the second device; determining that the first service rejection message is received and the first service rejection message carries a first cause value, and re-accessing to a second cell, the second cell being a neighbor cell different from the first cell. After a cell where the terminal device is located has a problem, the terminal device can avoid switching to the problem cell again, thereby avoiding a call being disconnected due to a link being disconnected, and improving user experience.

Description

Technical Field

[0001] This invention relates to the field of computer technology, and in particular to a cell handover method and electronic device. Background Technology

[0002] During a call, if the cell where the terminal device is located experiences an issue and initiates an RRC connection release, the terminal device will attempt to re-establish the connection for service reasons. At this point, the terminal device will receive a service rejection message from the base station carrying the cause value "Implicitly de-registered," causing the link to disconnect and the call to end. Subsequently, the terminal device may report the problematic cell to the base station again, causing the base station to issue a Radio Resource Control (RRC) reconfiguration instruction to switch to the same problematic cell. The problematic cell will then again initiate an RRC connection release, and the terminal device will attempt to re-establish the connection for service reasons. This process will then continue to result in the terminal device receiving service rejection messages, causing the link to disconnect, and so on. If the terminal device remains in the problematic cell after the call ends, subsequent calls will still encounter problems, severely impacting the user experience.

[0003] Therefore, if a problem occurs in the cell where the terminal device is located, it may switch back to the problematic cell, causing frequent link disconnections and reducing user experience. Summary of the Invention

[0004] In view of this, embodiments of the present invention provide a cell handover method and electronic device, which enables the terminal device to avoid handover to the problematic cell again after a problem occurs in the cell it is in, thereby reducing link disconnection and improving user experience.

[0005] In a first aspect, embodiments of the present invention provide a cell handover method, applied to a first device, the method comprising:

[0006] The device receives a first handover message from the second device for the first cell, where the first cell is a neighboring cell. The first measurement report of the first cell has been reported to the second device. The first measurement report is a measurement report obtained by performing measurement events on the first cell.

[0007] Successfully switched to the first cell based on the first handover message;

[0008] When the first device receives an RRC release message from the second device and has services in operation, it sends a first service request message to the second device and receives a first service rejection message from the second device.

[0009] Upon determining that a first service rejection message has been received and that the first service rejection message carries a first reason value, the system switches to a second cell. The second cell is a neighboring cell different from the first cell. The second measurement report of the second cell has been reported to the second device. The second measurement report is a measurement report obtained by performing measurement events on the second cell.

[0010] For example, measurement events include A3 measurement events.

[0011] For example, the first handover message is an RRC reconfiguration message containing the first cell, namely RRCReconfiguration(first cell).

[0012] After the first device successfully switches to the first cell based on the first handover message, if there is a problem with the first cell, it will receive a service rejection message with a first reason value sent by the second device, causing the link to be disconnected.

[0013] For example, the first reason value is Implicitly de-registered.

[0014] In this embodiment of the invention, after the first device successfully switches to the first cell, if the first cell encounters a problem, it can switch to the second cell, i.e., another good cell, to avoid switching to the same problematic cell again. This avoids receiving a service rejection message with a first cause value due to switching to the same problematic cell, reduces the occurrence of link disconnection, and improves user experience.

[0015] In conjunction with the first aspect, some implementations of the first aspect, before switching to the second cell, also include:

[0016] Once it is determined that a first service rejection message has been received and the first service rejection message carries a first reason value, the first timer is started and the first rejection count is started. The first rejection count is the number of service rejection messages carrying the first reason value received when the cell is the first cell.

[0017] When the first timer reaches the first preset time, if the first rejection count is less than or equal to the first threshold, the first timer stops and the counting of the first rejection count stops.

[0018] If the first rejection count exceeds the first threshold before the first preset time has elapsed, the first timer is stopped, the first rejection count is stopped, and the first cell is added to the blacklist. Cells in the blacklist will not be reported to the second device.

[0019] In this embodiment of the invention, when a problem occurs in the first cell where the first device is located, resulting in the receipt of a service rejection message carrying the cause value "Implicitly de-registered", a branch for first timing and counting the first number of rejections is added: when the first timing reaches a first preset time, the number of rejections is less than or equal to a first threshold, for example, the number of rejections in the first cell within 1 minute is less than or equal to 3 times, indicating that the first cell may be temporarily unstable but not a problem cell, and therefore can continue to be used as a cell to be handed over, so the first timing and counting of the first number of rejections are stopped; if the first number of rejections is greater than the first threshold before the first preset time, for example, the number of rejections in the first cell within 1 minute is greater than 3 times, indicating that the first cell is a problem cell, the first cell is added to the blacklist.

[0020] The newly added branch in this embodiment of the invention can add the cell to the blacklist when the cell where the first device is located is a problematic cell, and stop reporting the measurement report of the problematic cell to the second device. This avoids the second device sending a handover message to the first device to switch to the problematic cell, thereby preventing the first device from switching to the problematic cell again. This avoids receiving a service rejection message with the cause value Implicitly de-registered due to switching to the same problematic cell, reducing the occurrence of link disconnection and improving user experience.

[0021] In conjunction with the first aspect, in certain implementations of the first aspect, after determining that a first service rejection message has been received and that the first service rejection message carries a first reason value, the method further includes:

[0022] The device receives a second handover message from the second device for the third cell, which is a neighboring cell that is different from the first and second cells. The third measurement report of the third cell has been reported to the second device. The third measurement report is a measurement report obtained by performing measurement events on the third cell.

[0023] Successfully switched to the third cell based on the second handover message;

[0024] When an RRC release message is received and the first device has services in operation, a second service request message is sent to the second device and a second service rejection message is received from the second device.

[0025] If a second service rejection message is received and carries a first reason value, the user switches to the second cell.

[0026] In this embodiment of the invention, if a first device experiences a link disconnection due to a problem in its first cell receiving a service rejection message with the cause value "Implicitly de-registered", it may subsequently receive handover messages from a second device. Each handover message may contain a different or the same cell as the first cell. When the neighboring cell in the handover message is different from the first cell (i.e., the cell in the handover message is a third cell), if a successful handover to the third cell is followed by a problem in that third cell also resulting in receiving a service rejection message with the cause value "Implicitly de-registered", then the device switches to the second cell, which is a good cell. Therefore, this embodiment of the invention enables a quick handover to other good cells after a problem in the cell where the device is located results in receiving a service rejection message with the cause value "Implicitly de-registered", avoiding frequent reception of such messages by switching back to the same problematic cell, thereby reducing link disconnections and improving user experience.

[0027] In conjunction with the first aspect, some implementations of the first aspect, before switching to the second cell, also include:

[0028] Once it is determined that a second service rejection message has been received and the second service rejection message carries a first reason value, a second timer is started and the number of second rejections is counted. The number of second rejections is the number of service rejection messages carrying the first reason value received when the cell is a third cell.

[0029] When the second timer reaches the first preset time, if the second rejection count is less than or equal to the first threshold, the second timer stops and the counting of the second rejection count stops.

[0030] If the second rejection count exceeds the first threshold before the second timing reaches the first preset time, the second timing is stopped, the second rejection count is stopped, and the third cell is added to the blacklist.

[0031] In this embodiment of the invention, after the first device successfully switches to the third cell, if a link disconnection occurs due to a problem in the third cell resulting in the receipt of a service rejection message with the cause value "Implicitly de-registered", the first device will also time and count the number of rejections for the third cell. Upon discovering that the third cell is a problematic cell, the first device will also add it to its blacklist and will not continue to report measurement reports for the third cell to the second device. This prevents the second device from sending a switchover message to the third cell to the first device, thus preventing the first device from switching to the third cell again. Furthermore, adding the third cell to the blacklist avoids the frequent receipt of service rejection messages with the cause value "Implicitly de-registered" when switching to the same problematic cell again, thereby reducing link disconnections and improving user experience.

[0032] In conjunction with the first aspect, in some implementations of the first aspect, before receiving the first handover message for the first cell sent by the second device, the method further includes:

[0033] Receive measurement configuration messages for measurement events sent by the second device;

[0034] Based on the measurement configuration message, the measurement events of the neighboring cells are measured, and the first measurement report of the first cell is obtained;

[0035] If the first measurement report does not meet the first condition of the measurement event, the first measurement report will not be sent to the second device; or

[0036] When the first measurement report meets the first condition of the measurement event, the first measurement report is sent to the second device.

[0037] In this embodiment of the invention, before the second device sends the first handover message of the first cell to the first device, it first sends a measurement configuration message of a measurement event to the first device. The first device performs measurement events on neighboring cells according to the measurement configuration message, obtaining measurement reports from the neighboring cells. The first cell is one of the neighboring cells surrounding the cell where the first device is located, thus obtaining a first measurement report for the first cell. If the first measurement report does not meet the first condition of the measurement event, the first device does not send the first measurement report to the second device; if the first measurement report meets the first condition of the measurement event, the first measurement report is sent to the second device. This allows the second device to subsequently send the first handover message of the first cell to the first device based on the first measurement report of the first cell.

[0038] In conjunction with the first aspect, in some implementations of the first aspect, the first timing begins and the first rejection count begins to be counted, specifically including:

[0039] Start the first timer and the first counter bound to the first cell and increment the first counter by one; the timeout period of the first timer is the first preset time, and the initial value of the first counter is 0;

[0040] Each time the cell in question is the first cell and a service rejection message carrying the first reason value is received, the first counter is incremented by one.

[0041] In this embodiment of the invention, timers and counters can be bound to cells to time and count the number of rejections for that cell.

[0042] In conjunction with the first aspect, in certain implementations of the first aspect, stopping the first timing and stopping the counting of the first rejection count includes:

[0043] Stop the first timer and the first counter.

[0044] In this embodiment of the invention, the first timer timeout indicates that the first timing time exceeds the first preset time, and the value of the first counter is less than or equal to the first threshold, indicating that the first rejection count is less than or equal to the first threshold, indicating that the first cell may be temporarily unstable but not a problem cell, and therefore can continue to be a cell to be handed over, and the first timer and the first counter are stopped.

[0045] In conjunction with the first aspect, some implementations of the first aspect, including stopping the first timing and stopping the counting of the first rejections, also include:

[0046] Unbind the first timer and the first counter from the first cell.

[0047] In this embodiment of the invention, after stopping the first timer and the first counter, if they are not unbound from the first cell, they will only be restarted after a successful handover to the first cell, when a service rejection message carrying the cause value "Implicitly de-registered" is received due to a problem in the first cell. During this period, the first timer and the first counter will be idle and not fully utilized. This embodiment of the invention also unbounds the first timer and the first counter from the first cell after stopping them, so that the first timer and the first counter can continue to be used and will not be idle.

[0048] In conjunction with the first aspect, some implementations of the first aspect, when adding the first cell to the blacklist, also include:

[0049] Start the third timing; if the third timing has not reached the second preset time, do not send the first measurement report corresponding to the first cell to the second device.

[0050] When the third timing reaches the second preset time, the third timing stops and the first cell is removed from the blacklist.

[0051] In this embodiment of the invention, when a first cell is found to be a problematic cell, it is added to a blacklist and a third timer is started. The third timer is used to track the time the first cell has been added to the blacklist. Since the first cell is unlikely to remain a problematic cell and may become a good cell after a period of time, this embodiment of the invention removes the first cell from the blacklist when the time the first cell has been added to the blacklist exceeds a second preset time. The transmission of measurement reports to the second device for the first cell is no longer suppressed, allowing the second device to continue sending handover messages to the first cell, enabling the first device to handover to the first cell again.

[0052] In conjunction with the first aspect, in certain implementations of the first aspect, a third timing is initiated, and before the third timing reaches the second preset time, the first measurement report corresponding to the first cell is not sent to the second device, including:

[0053] Start the second timer bound to the first cell, and the timeout period of the second timer is the second preset time;

[0054] If the second timer does not expire, the first measurement report corresponding to the first cell will not be sent to the second device.

[0055] In this embodiment of the invention, the second timer can be bound to the first cell, and the second timer can be started when the first cell is added to the blacklist, so that the second timer can be used to count the time when the first cell is added to the blacklist.

[0056] The timeout period of the second timer is the second preset time. If the second timer does not time out, it means that the time for adding the first cell to the blacklist has not reached the second preset time, and the first measurement report corresponding to the first cell will not be sent to the second device.

[0057] In conjunction with the first aspect, in certain implementations of the first aspect, when the third timing reaches the second preset time, the third timing is stopped and the first cell is removed from the blacklist, including:

[0058] When the second timer expires, the second timer is stopped and the first cell is removed from the blacklist.

[0059] In this embodiment of the invention, the timeout period of the second timer is a second preset time. The timeout of the second timer indicates that the time for the first cell to be added to the blacklist exceeds the second preset time. The second timer is stopped to stop the third timer and the first cell is removed from the blacklist.

[0060] In conjunction with the first aspect, in some implementations of the first aspect, a second timing is started and the second number of rejections is counted, including...

[0061] Start the third timer and the second counter bound to the third cell and increment the second counter by one; the timeout period of the third timer is the first preset time, and the initial value of the second counter is 0;

[0062] Each time the cell in question is the third cell and a service rejection message carrying the first reason value is received, the second counter is incremented by one.

[0063] In this embodiment of the invention, timers and counters can be bound to cells to time and count the number of rejections for that cell. This embodiment of the invention can bind timers and counters to multiple cells simultaneously, thereby identifying multiple problematic cells.

[0064] In conjunction with the first aspect, some implementations of the first aspect, when adding a third cell to the blacklist, also include:

[0065] Start the fourth timing. If the fourth timing does not reach the second preset time, the third measurement report corresponding to the third cell will not be sent to the second device.

[0066] When the fourth timer reaches the second preset time, the fourth timer stops and the third cell is removed from the blacklist.

[0067] In this embodiment of the invention, when a third cell is found to be a problematic cell, the third cell is added to a blacklist and a fourth timer is started. The fourth timer is used to count the time the third cell has been added to the blacklist. Since the third cell is unlikely to remain a problematic cell and may become a good cell after a period of time, this embodiment of the invention removes the third cell from the blacklist when the time the third cell has been added to the blacklist exceeds a second preset time. Measurement reports for the third cell are no longer suppressed from being sent to the second device, allowing the second device to continue sending handover messages for the third cell, enabling the first device to handover to the third cell again.

[0068] In conjunction with the first aspect, in certain implementations of the first aspect, a fourth timing is initiated, and before the fourth timing reaches the second preset time, the third measurement report corresponding to the third cell is not sent to the second device, including:

[0069] When the third cell is added to the blacklist, the fourth timer bound to the third cell is started, and the timeout time of the fourth timer is the second preset time.

[0070] The third measurement report corresponding to the third cell will not be sent to the second device before the fourth timer expires.

[0071] In this embodiment of the invention, the fourth timer can be bound to the third cell, and the fourth timer can be started when the third cell is added to the blacklist, so that the fourth timer can be used to count the time when the third cell is added to the blacklist.

[0072] The timeout period of the fourth timer is the second preset time. If the fourth timer does not time out, it means that the time for adding the third cell to the blacklist has not reached the second preset time, and the third measurement report corresponding to the third cell will not be sent to the second device.

[0073] In conjunction with the first aspect, in some implementations of the first aspect, after determining that the first service rejection message carries the first reason value, it also includes:

[0074] Based on the first service rejection message, the service is terminated and an initial registration is triggered to re-initiate attachment registration to the second device;

[0075] After initial registration is completed, the device receives measurement configuration messages for measurement events sent by the second device.

[0076] Secondly, embodiments of the present invention provide a first electronic device, including a processor and a memory, wherein the memory is used to store a computer program, the computer program including program instructions, and when the processor executes the program instructions, the electronic device performs the method described above.

[0077] Thirdly, embodiments of the present invention provide a computer-readable storage medium storing a computer program, the computer program including program instructions that, when executed by a computer, cause the computer to perform the method described above.

[0078] Fourthly, embodiments of the present invention provide a computer program product, the computer program product storing a computer program, the computer program including program instructions, which, when executed by a computer, cause the computer to perform the method described above.

[0079] The cell handover method and electronic device provided in this invention include: a first device receiving a first handover message for a first cell from a second device, wherein the first cell is a neighboring cell, and a first measurement report of the first cell has been reported to the second device (the first measurement report is a measurement report obtained by performing measurement events on the first cell); successfully handing over to the first cell based on the first handover message; when receiving an RRC release message from the second device and the first device has services in operation, sending a first service request message to the second device and receiving a first service rejection message from the second device; determining that the first service rejection message has been received and carries a first reason value, handing over to a second cell, wherein the second cell is a neighboring cell different from the first cell, and a second measurement report of the second cell has been reported to the second device (the second measurement report is a measurement report obtained by performing measurement events on the second cell). This method avoids handover to the problematic cell again after a problem occurs in the cell where the terminal device is located, thereby reducing link disconnections and improving user experience. Attached Figure Description

[0080] Figure 1 A flowchart of a cell handover method;

[0081] Figure 2 This is a schematic diagram of the structure of a device provided in an embodiment of the present invention;

[0082] Figure 3 A schematic diagram of a cell handover system provided in an embodiment of the present invention;

[0083] Figure 4 Signaling interaction diagram of a cell handover method provided in an embodiment of the present invention;

[0084] Figure 5 for Figure 4 The flowchart shows the process of the first device in the middle starting to perform the first timing for the cell corresponding to the cell ID and starting to count the number of rejections;

[0085] Figure 6 for Figure 4 The flowchart shows the process of the first device stopping the first timing, stopping the counting of rejections, adding the cell corresponding to the cell ID to the blacklist, and starting the second timing for the cell corresponding to the cell ID.

[0086] Figure 7 This is a schematic diagram illustrating the operation of a timer and counter bound to multiple cells in an embodiment of the present invention;

[0087] Figure 8 A flowchart of a cell handover method provided in an embodiment of the present invention;

[0088] Figure 9A flowchart illustrating another cell handover method provided in an embodiment of the present invention;

[0089] Figure 10 This is a schematic diagram of the structure of an electronic device provided in an embodiment of the present invention. Detailed Implementation

[0090] To better understand the technical solution of the present invention, the embodiments of the present invention will be described in detail below with reference to the accompanying drawings.

[0091] It should be understood that the described embodiments are merely some, not all, of the embodiments of the present invention. All other embodiments obtained by those skilled in the art based on the embodiments of the present invention without inventive effort are within the scope of protection of the present invention.

[0092] The terminology used in the embodiments of this invention is for the purpose of describing particular embodiments only and is not intended to limit the invention. The singular forms “a,” “the,” and “the” as used in the embodiments of this invention and the appended claims are also intended to include the plural forms unless the context clearly indicates otherwise.

[0093] It should be understood that the term "and / or" used in this article is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing alone. Additionally, the character " / " in this article generally indicates that the preceding and following related objects have an "or" relationship.

[0094] To better understand the embodiments of this application, the terms or concepts that may be involved in the embodiments are explained below.

[0095] Taking the measurement configuration of the base station sending A3 measurement events to the terminal device as an example, Figure 1 A flowchart of a cell handover method, such as Figure 1 As shown, the method includes:

[0096] Step 101: During a call, the terminal device receives a measurement configuration message for the A3 measurement event sent by the base station.

[0097] When a terminal device makes a call in a New Radio (NR) or Long Term Evolution (LTE) scenario, the base station issues A3 measurement configuration.

[0098] Step 102: Based on the measurement configuration message, perform A3 measurement on the neighboring cell to obtain a measurement report.

[0099] Among them, neighboring cells are cells adjacent to the cell where the terminal device is currently located.

[0100] Step 103: Determine whether the measurement report meets the measurement threshold of measurement event A3. If not, proceed to step 104; if yes, proceed to step 105.

[0101] Step 104: Do not report the measurement report to the base station. Process ends.

[0102] Step 105: Submit the measurement report to the base station.

[0103] Step 106: Receive the handover message from the base station to neighboring cell A and successfully handover to neighboring cell A.

[0104] After the terminal device detects that there is a neighboring cell A that meets the measurement threshold, it will report the A3 measurement report of the neighboring cell A to the base station, and the base station will issue an RRC reconfiguration instruction to switch to the neighboring cell A.

[0105] Step 107: Receive the RRC release message sent by the base station, and the terminal device enters the Idle state.

[0106] When a problem occurs in neighboring cell A, the base station will abnormally send an RRC Release message to disconnect the RRC connection, and the terminal device will enter the Idle state.

[0107] For example, when the Central Processing Unit (CPU) is not executing any tasks and has not received any interrupt / exception signals, the CPU is in an idle state.

[0108] Step 108: Determine that the terminal device is conducting a service and send a Service Request (SR) message to the base station.

[0109] After the RRC connection is disconnected, since the terminal device is still conducting a call, it sends a ServiceRequest message to the base station to re-establish the RRC connection.

[0110] Step 109: Receive the service rejection message sent by the base station, which includes the reason value Implicitly de-registered.

[0111] Because of a problem in neighboring cell A, the base station will reject the SR request and send a service rejection message with the reason value "Implicitly de-registered" to the terminal device.

[0112] For example, the reason value "Implicitly de-registered" indicates that the device was implicitly deregistered by the network, rather than through a traditional deregistration request process. This can occur in various scenarios, such as when the network decides to no longer maintain the registration status with a specific User Equipment (UE), or when a deregistration process is automatically triggered due to certain conditions being met. In this embodiment of the invention, a problem in neighboring cell A causes the terminal device to receive a service rejection message containing the reason value "Implicitly de-registered".

[0113] Step 110: The call service is disconnected and the initial attachment registration is triggered; continue to step 101.

[0114] The call was interrupted because the SR request was rejected.

[0115] After receiving a service rejection message with the cause value "Implicitly de-registered", the terminal device disconnects the link, causing the call to end and triggering an initial registration to re-initiate attach registration. After registration, the terminal device may repeat steps 101-114, causing the problematic cell to be reported to the base station again. This leads the base station to continue issuing RRC reconfiguration instructions to switch to the same problematic cell, creating a vicious cycle. Furthermore, if the terminal device remains in the problematic cell after the call ends, subsequent calls will still encounter problems, severely impacting the user experience.

[0116] To address the aforementioned technical problems, embodiments of the present invention provide a cell handover system that prevents a terminal device from re-handing to the problematic cell after a problem occurs there, thereby reducing link disconnections and improving user experience. The cell handover system provided in this embodiment includes a first device and a second device, which are connected via wired or wireless means.

[0117] Figure 2 This is a schematic diagram of the structure of a device provided in an embodiment of the present invention.

[0118] like Figure 2 As shown, device 200 may include one or more processors and one or more memories. Taking device 200 including one processor and one memory as an example, as... Figure 2 As shown, device 200 includes processor 210 and memory 220.

[0119] It is understood that the structures illustrated in the embodiments of the present invention do not constitute a specific limitation on the device 200. In other embodiments of this application, the device 200 may include more or fewer components than illustrated, or combine some components, or split some components, or have different component arrangements. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

[0120] Processor 210 may include one or more processing units, such as application processors, modem processors, graphics processors, image signal processors, controllers, video codecs, digital signal processors, baseband processors, and / or neural network processors. These different processing units may be independent devices or integrated into one or more processors.

[0121] The controller can generate operation control signals based on the instruction opcode and timing signals to complete the control of instruction fetching and execution.

[0122] The processor 210 may also include a memory for storing instructions and data. In some embodiments, the memory in the processor 210 is a cache memory. This memory can store instructions or data that the processor 210 has just used or that are used repeatedly. If the processor 210 needs to use the instruction or data again, it can directly retrieve it from the memory. This avoids repeated accesses, reduces the waiting time of the processor 210, and thus improves the efficiency of the system.

[0123] In some embodiments, the processor 210 may include one or more interfaces. Interfaces may include integrated circuit interfaces, integrated circuit built-in audio interfaces, pulse code modulation interfaces, universal asynchronous transceiver interfaces, mobile industry processor interfaces, universal input / output interfaces, user identity module interfaces, and / or universal serial bus interfaces, etc.

[0124] It is understood that the interface connection relationships between the modules illustrated in the embodiments of the present invention are merely illustrative and do not constitute a structural limitation on the device 200. In other embodiments of this application, the device 200 may also employ different interface connection methods or combinations of multiple interface connection methods as described in the above embodiments.

[0125] like Figure 2 As shown, the device 200 may also include a communication module 230. The communication module 230 includes a mobile communication module and a wireless communication module.

[0126] The mobile communication module can provide solutions for wireless communication applications including 2G / 3G / 4G / 5G applied to device 200. The mobile communication module may include at least one filter, switch, power amplifier, low-noise amplifier, etc. The wireless communication module can provide solutions for wireless communication applications including wireless local area networks (WLAN) (such as wireless fidelity (Wi-Fi) networks) applied to device 200. The wireless communication module may be one or more devices integrating at least one communication processing module. Memory 220 can be used to store programs. Memory 220 may include a program storage area and a data storage area. The program storage area may store the operating system, applications required for at least one function, etc. The data storage area may store data created during the use of device 200, etc. Furthermore, memory 220 may include high-speed random access memory and may also include non-volatile memory. Processor 210 executes various functional applications and data processing of device 200 by running instructions stored in memory 220 and / or instructions stored in memory located in the processor.

[0127] Figure 3 This is a schematic diagram of a cell handover system provided in an embodiment of the present invention, such as... Figure 3 As shown, the cell handover system provided in this embodiment of the invention includes: a first device 310 and a second device 320. The first device 310 and the second device 320 are connected by wired or wireless means.

[0128] The hardware and software structures of the first device 310 and the second device 320 provided in the embodiments of the present invention can be found in [reference needed]. Figure 2 The relevant description of equipment 200 in the text.

[0129] For example, the first device 310 includes a terminal device, such as a handheld terminal, a portable computer, a wearable device, or an entertainment device.

[0130] For example, the second device 320 includes a base station.

[0131] Based on the above-described cell handover system, this embodiment of the invention provides a cell handover method.

[0132] Taking the A3 measurement event as an example, Figure 4 This is a signaling interaction diagram of a cell handover method provided in an embodiment of the present invention. For example... Figure 4 As shown, the method includes steps 402-446.

[0133] Step 402: The second device sends a measurement configuration message for the A3 measurement event to the first device.

[0134] For example, the measurement configuration message for the A3 measurement event is the RRC connection reconfiguration message for the A3 measurement event, namely RRCConnectionReconfiguration(eventA3).

[0135] Step 404: The first device sends a measurement configuration completion message to the second device based on the measurement configuration message.

[0136] For example, the measurement configuration completion message is the RRC connection reconfiguration completion message, i.e., RRCConnectionReconfigurationComplete.

[0137] Step 406: The first device performs A3 measurement on the neighboring cell according to the measurement configuration message and obtains the measurement report of the target cell.

[0138] The target cell is a neighboring cell of the cell where the first device is located.

[0139] Step 408: The first device determines whether the measurement report meets the A3 measurement threshold. If not, proceed to step 410; if yes, proceed to step 412.

[0140] Step 410: The first device does not send the measurement report to the second device.

[0141] Step 412: The first device sends a measurement report to the second device.

[0142] For example, the measurement report for an A3 measurement event is MeasurementReport(eventA3).

[0143] Step 414: The second device sends a handover message for the target cell to the first device based on the measurement report.

[0144] For example, the handover message is an RRC reconfiguration message containing the target cell, namely RRCReconfiguration(target cell).

[0145] Step 416: The first device successfully switches to the target cell based on the handover message.

[0146] Step 418: The second device sends an RRC release message to the first device.

[0147] When a problem occurs in the first cell, the second device sends an RRC release message to the first device to disconnect the RRC connection.

[0148] Step 420: The first device enters the Idle state according to the RRC release message and determines that there is a service to be performed.

[0149] Step 422: The first device sends a service request message to the second device.

[0150] The service request message is an SR message.

[0151] After the RRC connection is disconnected, since the first device is still conducting a call, it sends a ServiceRequest message to the second device to re-establish the RRC connection.

[0152] Step 424: The second device sends a service rejection message to the first device.

[0153] Because of a problem in the first cell, the second device will reject the SR request and send a service rejection message with the reason value "Implicitly de-registered" to the first device.

[0154] Step 426: The first device determines that it has received a service rejection message and that the service rejection message contains the reason value Implicitly de-registered, and continues to execute steps 428 and 434.

[0155] Step 428: The first device terminates its service.

[0156] In this step, if the service is a call service, the link is broken because the SR request is rejected, the call cannot continue, and the call service ends.

[0157] Step 430: The first device sends a registration request message to the second device.

[0158] After receiving a service rejection message with the cause value "Implicitly de-registered", the first device will trigger an initial registration and re-initiate an attachment registration with the second device.

[0159] For example, the registration request message is called a Registration request.

[0160] Step 432: The second device sends a registration acceptance message to the first device, and then proceeds to step 402.

[0161] In this step, the first device receives a registration acceptance message from the second device, indicating that the initial registration has been completed.

[0162] For example, the registration acceptance message is "Registration accept".

[0163] Figure 1The cell handover method shown may result in an infinite loop if, after a problem occurs in the current cell and a service rejection message carrying the cause value "Implicitlyde-registered" is received, it continues to handover to the same problematic cell. The cell handover method provided in this embodiment of the invention, after a problem occurs in the current cell and a service rejection message carrying a first cause value is received, compared to... Figure 1 The cell handover method shown, in addition to ending the current service, triggering the initial registration and re-initiating the attachment registration, and continuing to search for and handover cells, adds another branch, namely steps 434-446. The new branch can stop reporting the measurement report of the problematic cell when the cell where the first device is located is found to be a problematic cell. This allows the first device to avoid handover to the problematic cell again, and to maintain the current cell or wait to measure other good cells before handover. This avoids frequent service rejection messages with the cause value Implicitly de-registered, which can cause frequent link disconnections and improves user experience.

[0164] Step 434: The first device records the cell ID of the target cell, starts the first timing for the cell corresponding to the cell ID, and starts counting the number of rejections. The number of rejections is the number of times a service rejection message carrying the first reason value is received when the device is the cell corresponding to the cell ID.

[0165] In this embodiment of the invention, when the first device receives a service rejection message carrying a first cause value due to a problem in the cell it is in, it records the cell ID of the cell, and starts counting the number of rejections for the cell based on the cell ID.

[0166] In some possible embodiments, such as Figure 5 As shown, step 434 specifically includes: step 434a-step 434b.

[0167] Step 434a: The first device starts the timer T1 and counter A bound to the cell ID and increments the counter A by one; the timeout time of timer T1 is the first preset time, and the initial value of counter A is 0.

[0168] Step 434b: Each time the first device is in the cell corresponding to the cell ID and receives a service rejection message carrying the first reason value, it increments the counter A by one.

[0169] In this embodiment of the invention, timers and counters can be bound to cells to time and count the number of rejections for that cell.

[0170] Step 436: The first device determines whether the number of rejections exceeds the first threshold before the first preset time is reached in the first time. If not, proceed to step 438; if yes, proceed to step 440.

[0171] In this step, if the first device determines that when the time of the first timing reaches the first preset time (e.g., 1 minute), the number of rejections of the cell is less than or equal to the first threshold (e.g., 3 times), that is, the number of times the cell has a problem within 1 minute and receives a service rejection message carrying the first reason value is less than or equal to 3 times, it indicates that the cell may be temporarily unstable but not a problem cell, and step 438 is continued.

[0172] In this step, if the first device determines that the number of rejections of the cell is greater than the first threshold (3 times) before the first preset time (e.g., 1 minute) is reached during the first time, that is, the number of times the cell has a problem within 1 minute and has received a service rejection message carrying the first reason value is greater than 3 times, it indicates that the cell corresponding to the cell ID is a problem cell, so step 440 is continued.

[0173] In some possible embodiments, step 436 specifically includes: the first device determining whether the value of counter A during the timeout period of timer T1 is greater than a first threshold; if the value of counter A when timer T1 times out is less than or equal to the first threshold, step 438 is executed; if the value of counter A when timer T1 does not time out is greater than the first threshold, step 440 is executed.

[0174] Step 438: The first device stops the first timing and stops counting the number of rejections.

[0175] In this step, if the first device determines that the cell corresponding to the cell ID may be a temporarily unstable but not a problem cell, it can continue to be used as a cell to be handed over. Therefore, the first timer is stopped and the count of rejections is stopped so that the cell can be reported to the second device again by the first device.

[0176] In some possible embodiments, step 438 specifically includes: the first device stopping timer T1 and counter A, and unbinding timer T1 and counter A from the cell corresponding to the cell ID.

[0177] In this embodiment of the invention, when it is determined that the cell corresponding to the cell ID is not a problematic cell, the timer and counter bound to that cell are unbound so that the unbound timer and counter can continue to be used. The timer and counter will only be bound to that cell again and the first time the counting of rejections will begin when a service rejection message carrying a first reason value is received after a successful handover to that cell and a problem occurs in that cell.

[0178] Step 440: The first device stops the first timing, stops counting the number of rejections, adds the cell corresponding to the cell ID to the blacklist, and starts the second timing for the cell corresponding to the cell ID.

[0179] In this step, if the cell corresponding to the cell ID is a problematic cell, the first timing is stopped, the number of failures is stopped, the cell corresponding to the cell ID is added to the blacklist, and the second timing for the cell corresponding to the cell ID begins.

[0180] For example, the second timing is used to record the time when the cell corresponding to the cell ID is added to the blacklist.

[0181] In some possible embodiments, such as Figure 6 As shown, step 440 specifically includes: step 440a-step 440a.

[0182] Step 440a: The first device stops timer T1 and counter A.

[0183] Step 440b: The first device adds the cell corresponding to the cell ID to the blacklist and starts the timer T2 bound to the cell ID. The timeout time of the timer T2 is the second preset time.

[0184] Step 442: The first device determines whether the second timing time has reached the second preset time. If not, proceed to step 444; if yes, proceed to step 446.

[0185] In this step, the first device determines whether the time for adding the cell corresponding to the cell ID to the blacklist has reached the second preset time.

[0186] In some possible embodiments, step 442 specifically includes: the first device determining whether timer T2 has timed out; if not, executing step 444; if so, executing step 446.

[0187] Step 444: The first device does not send the measurement report of the cell corresponding to the cell ID to the second device, and continues to execute step 442.

[0188] In this step, the first device determines that the time for adding the cell corresponding to the cell ID to the blacklist has not reached the second preset time, and continues to execute step 442.

[0189] Step 446: The first device stops the second timing and removes the cell corresponding to the cell ID from the blacklist.

[0190] In this step, the first device determines that the time for adding the cell corresponding to the cell ID to the blacklist has reached the second preset time, stops the second timer, and deletes the cell corresponding to the cell ID from the blacklist.

[0191] In some possible embodiments, step 446 specifically includes: the first device stopping timer T2, unbinding timer T2 from the cell ID, and deleting the cell ID from the blacklist.

[0192] In this embodiment of the invention, when the cell corresponding to the cell ID is removed from the blacklist, the timer T2 bound to that cell is unbound so that the unbound timer T2 can continue to be used.

[0193] It should be understood that the timer can be bound to the cell ID, or it can be directly bound to the cell corresponding to the cell ID.

[0194] For example, Figure 7 This is a schematic diagram illustrating the operation of a timer and counter bound to multiple cells in an embodiment of the present invention. Assume a first preset time of 60 seconds, a first threshold of 3, and a second preset time of 120 seconds. The first device is in cell A. Due to a problem in cell A, such as... Figure 7 As shown, at time t0, a service denial message containing the first cause value is received, and timer TA1 and counter A1 bound to cell A are started. If timer TA1 has not timed out after 50 seconds, but counter A1 is equal to 3, then cell A is added to the blacklist, and timer TA2 bound to cell A is started.

[0195] Then, the first device successfully switched to cell B, but cell B then experienced problems, such as... Figure 7 As shown, at time t2 after 60s, a service denial message containing the first cause value is received, and timer TB1 and counter A2 bound to cell B are started. At this time, timer TA2 bound to cell A has not timed out.

[0196] like Figure 7 As shown, if timer TB1 does not time out at time t3 after 40 seconds, but counter A2 equals 3, then cell B is added to the blacklist, and timer TB2 bound to cell B is started. At this time, the time remaining from time t1 is 100 seconds, which is less than 120 seconds, and timer TA2 bound to cell A also does not time out.

[0197] It should be understood that restarting a timer and counter means resetting the value of the timer and counter and then starting it again. Stopping a timer and counter means resetting the value of the timer and counter and then shutting it down.

[0198] Therefore, in this embodiment of the invention, when the cell where the first device is currently located is a problematic cell, the problematic cell is added to a blacklist. The first device will suppress the reporting of measurement reports of cells in the blacklist, that is, it will not report the measurement reports of cells in the blacklist to the second device, thereby avoiding switching to the problematic cell again, reducing the phenomenon of link disconnection, and improving user experience.

[0199] In this embodiment of the invention, when a problem occurs in the target cell where the first device is located, resulting in the receipt of a service rejection message carrying the cause value "Implicitly de-registered", the cell ID of the target cell is recorded. Since the target cell in each handover message received by the first device from the second device may be different, the cell ID of the target cell is recorded when a problem occurs in the target cell for the first time, resulting in the receipt of a service rejection message carrying the cause value "Implicitly de-registered". This allows a timer and a counter to be bound to the cell corresponding to the cell ID, so as to count the number of rejections of the cell within a first preset time period, and determine whether the cell is a problem cell based on the number of rejections within the first preset time period.

[0200] In this embodiment of the invention, after determining that the cell corresponding to the cell ID is a problematic cell, the cell is added to a blacklist, and the time for adding the cell to the blacklist is recorded. After a second preset time, the cell is removed from the blacklist, and the first device can continue to report the measurement report of the cell, thus preventing the continuous suppression of the cell's measurement report reporting.

[0201] Figure 8 This is a flowchart illustrating a cell handover method provided in an embodiment of the present invention. Figure 8 As shown, the method includes steps 502-508.

[0202] Step 502: The first device receives the first handover message of the first cell sent by the second device. The first cell is a neighboring cell. The first measurement report of the first cell has been reported to the second device. The first measurement report is the measurement report obtained by performing measurement events on the first cell.

[0203] Step 504: Successfully switched to the first cell according to the first handover message.

[0204] Step 506: When the RRC release message sent by the second device is received and the first device has services in operation, the first device sends a first service request message to the second device and receives a first service rejection message sent by the second device.

[0205] Step 508: Determine that a first service rejection message has been received and that the first service rejection message carries a first reason value, and switch to the second cell. The second cell is a neighboring cell that is different from the first cell. The second measurement report of the second cell has been reported to the second device. The second measurement report is a measurement report obtained by performing measurement events on the second cell.

[0206] The cell handover method provided in this invention includes the following steps: a first device receives a first handover message for a first cell from a second device. The first cell is a neighboring cell, and a first measurement report of the first cell has been reported to the second device. The first measurement report is a measurement report obtained by performing measurement events on the first cell. The device successfully hands over to the first cell based on the first handover message. When the first device receives an RRC release message from the second device and has services running, it sends a first service request message to the second device and receives a first service rejection message from the second device. If the first service rejection message is received and carries a first reason value, the device hands over to a second cell, which is a neighboring cell different from the first cell. A second measurement report of the second cell has been reported to the second device. The second measurement report is a measurement report obtained by performing measurement events on the second cell. This method avoids handover to the problematic cell again after a problem occurs in the cell where the terminal device is located, thereby reducing link disconnections and improving user experience.

[0207] Figure 9 This is a flowchart illustrating another cell handover method provided in an embodiment of the present invention. Figure 9 As shown, the method includes steps 602-642.

[0208] Step 602: The first device receives the first measurement configuration message of the measurement event sent by the second device, performs measurement of the measurement event on the neighboring cell according to the first measurement configuration message, and obtains the first measurement report of the first cell.

[0209] For example, the measurement event includes the A3 measurement event. The measurement events in this embodiment are not limited to the A3 measurement event; any measurement event used for cell handover is acceptable.

[0210] Step 604: When the first measurement report meets the first condition of the measurement event, send the first measurement report to the second device.

[0211] For example, the first condition corresponds to the measurement event. If the measurement event is A3 measurement event, then the first condition is the measurement threshold of A3 measurement event.

[0212] If the first measurement report does not meet the first condition of the measurement event, the first measurement report will not be sent to the second device.

[0213] In this embodiment of the invention, before the second device sends the first handover message of the first cell to the first device, it first sends a measurement configuration of a measurement event to the first device. The first device performs measurement events on neighboring cells according to the measurement configuration, obtaining measurement reports from the neighboring cells. The first cell is one of the neighboring cells surrounding the cell where the first device is located, thus obtaining a first measurement report for the first cell. If the first measurement report does not meet the first condition of the measurement event, the first device does not send the first measurement report to the second device; if the first measurement report meets the first condition of the measurement event, the first measurement report is sent to the second device. This allows the second device to subsequently send the first handover message of the first cell to the first device based on the first measurement report of the first cell.

[0214] Step 606: Receive the first handover message of the first cell sent by the second device, and successfully hand over to the first cell according to the first handover message.

[0215] For example, the first handover message is an RRC reconfiguration message containing the first cell, namely RRCReconfiguration(first cell).

[0216] Step 608: When the RRC release message sent by the second device is received and the first device has services in operation, the first device sends a first service request message to the second device and receives a first service rejection message sent by the second device.

[0217] In this step, when a problem occurs in the first cell, the first device will receive an RRC release message sent by the second device and enter the Idle state; then the first device determines that there is a service to be performed and sends a first service request message to the second device; due to the problem in the first cell, the second device sends a first service rejection message to the first device.

[0218] Step 610: If it is determined that a first service rejection message has been received and the first service rejection message carries a first reason value, continue to execute step 612 or step 620.

[0219] The current cell handover method, when a problem occurs in the current cell and a service denial message with the first cause value is received, can only continue to switch to the same problematic cell, thus getting stuck in an infinite loop.

[0220] The cell handover method provided in this embodiment of the invention, when a problem occurs in the current cell resulting in the receipt of a service rejection message carrying a first cause value, is compared to... Figure 1The cell handover method shown, in addition to ending the current service, triggering the initial registration and re-initiating the attachment registration, and continuing to search for and handover cells, also continues to execute the branch of step 620, that is, adding a branch for the first timing and counting the first rejection count: when the first timing reaches the first preset time, the rejection count is less than or equal to the first threshold. For example, if the rejection count caused by the first cell having a problem within 1 minute is less than or equal to 3 times, it indicates that the first cell may be temporarily unstable but not a problem cell. Therefore, it can continue to be used as a cell to be handed over. So the first timing restarts and the counting of the first rejection count restarts. If the first rejection count is greater than the first threshold before the first preset time is reached, for example, if the rejection count caused by the first cell having a problem within 1 minute is greater than 3 times, it indicates that the first cell is a problem cell and the first cell is added to the blacklist.

[0221] Step 612: Start the first timing and start counting the first rejection count. The first rejection count is the number of service rejection messages with the first reason value received when the cell is the first cell. Continue to execute step 614 or step 616.

[0222] In some possible embodiments, step 612 specifically includes: steps 612a-612b.

[0223] Step 612a: Start the first timer and the first counter bound to the first cell and increment the first counter by one; the timeout time of the first timer is the first preset time, and the initial value of the first counter is 0.

[0224] Step 612b: Each time the cell in question is the first cell and a service rejection message carrying the first reason value is received, increment the first counter by one.

[0225] In this embodiment of the invention, timers and counters can be bound to cells to time and count the number of rejections for that cell.

[0226] Step 614: When the first timer reaches the first preset time, if the first rejection count is less than or equal to the first threshold, stop the first timer and stop counting the first rejection count.

[0227] In some possible embodiments, step 614 specifically includes: when the first timer times out, if the value of the first counter is less than or equal to the first threshold, stopping the first timer and the first counter and unbinding the first timer and the first counter from the first cell.

[0228] In this embodiment of the invention, a first timer timeout indicates that the first timing period exceeds a first preset time, and a first counter value less than or equal to a first threshold indicates that the first rejection count is less than or equal to the first threshold, indicating that the first cell may be temporarily unstable but not a problem cell, and therefore can continue to be used as a cell awaiting handover. The first timer and first counter are stopped and unbound from the first cell so that the unbound timer and counter can continue to be used.

[0229] Step 616: If the first rejection count exceeds the first threshold before the first preset time has elapsed, stop the first timer, stop counting the first rejection count, add the first cell to the blacklist, and start the third timer.

[0230] In this embodiment of the invention, when a first cell is found to be a problematic cell, the first cell is added to the blacklist and a third timer is started. The third timer is used to count the time it takes for the first cell to be added to the blacklist.

[0231] In some possible embodiments, step 616 specifically includes: when the first timer has not expired, the value of the first counter is greater than the first threshold, stopping the first timer and the first counter, adding the first cell to the blacklist and starting the second timer bound to the first cell, wherein the timeout time of the second timer is the second preset time.

[0232] In this embodiment of the invention, the second timer can be bound to the first cell, and the second timer can be started when the first cell is added to the blacklist, so that the second timer can be used to count the time when the first cell is added to the blacklist.

[0233] In this embodiment of the invention, if the first timer does not time out, it means that the first timing time has not exceeded the first preset time. If the value of the first counter is greater than the first threshold, it means that the first rejection count is greater than the first threshold, indicating that the first cell is a problem cell. Then, the first timer and the first counter are stopped to stop the first timing and count the first rejection count.

[0234] Step 618: If the third timing time has not reached the second preset time, do not send the first measurement report corresponding to the first cell to the second device; or if the third timing time reaches the second preset time, stop the third timing and delete the first cell from the blacklist.

[0235] In some possible embodiments, step 618 specifically includes: not sending the first measurement report corresponding to the first cell to the second device when the second timer has not expired; or stopping the second timer and deleting the first cell from the blacklist when the second timer expires.

[0236] The timeout period of the second timer is the second preset time. If the second timer does not time out, it means that the time for adding the first cell to the blacklist has not reached the second preset time, and the first measurement report corresponding to the first cell will not be sent to the second device. If the second timer times out, it means that the time for adding the first cell to the blacklist has exceeded the second preset time, the second timer will be stopped to stop the third timer, and the first cell will be removed from the blacklist.

[0237] The newly added branch in this embodiment of the invention, namely steps 612-618, can add the cell to the blacklist when a problem is first discovered in the cell where the first device is located, and stop reporting the measurement report of the problematic cell to the second device. This avoids the second device sending a handover message to the first device to switch to the problematic cell, thereby preventing the first device from switching to the problematic cell again, reducing link disconnection and improving user experience.

[0238] Since the first cell cannot always be a problematic cell and may become a good cell after a period of time, this embodiment of the invention removes the first cell from the blacklist when the time for adding the first cell to the blacklist exceeds a second preset time, and no longer inhibits the reporting of measurement reports to the second device for the first cell, so that the second device can continue to send the handover message of the first cell, enabling the first device to hand over to the first cell again.

[0239] Step 620: Terminate the service according to the first service rejection message, trigger initial registration to re-initiate attachment registration with the second device, and receive the second measurement configuration message of the measurement event sent by the second device after the initial registration is completed.

[0240] Step 622: Perform measurement events on neighboring cells according to the second measurement configuration message to obtain the third measurement report of the third cell; when the third measurement report meets the first condition of the measurement event, send the third measurement report to the second device.

[0241] For example, the third cell is a neighboring cell that is different from the first cell.

[0242] In this embodiment of the invention, before the second device sends the second handover message for the third cell to the first device, it first sends a measurement configuration of a measurement event to the first device. The first device performs measurement events on neighboring cells according to the measurement configuration, obtaining measurement reports for the neighboring cells. The third cell is one of the neighboring cells different from the first cell in the vicinity of the cell where the first device is located, thus obtaining a third measurement report for the third cell. If the third measurement report does not meet the first condition of the measurement event, the first device does not send the third measurement report to the second device; if the third measurement report meets the first condition of the measurement event, the first device sends the third measurement report to the second device. This allows the second device to subsequently send the second handover message for the third cell to the first device based on the third measurement report of the third cell.

[0243] Step 624: Receive the second handover message for the third cell sent by the second device, and successfully hand over to the third cell according to the second handover message.

[0244] Step 626: When an RRC release message is received and the first device has services in operation, a second service request message is sent to the second device and a second service rejection message is received from the second device.

[0245] Step 628: If it is determined that a second service rejection message has been received and the second service rejection message carries a first reason value, continue to execute step 630 or step 638.

[0246] Step 630: Start the second timing and start counting the second rejection count. The second rejection count is the number of service rejection messages with the first reason value received when the cell is the third cell. Continue to execute step 632 or step 634.

[0247] In some possible embodiments, step 630 specifically includes: steps 630a-630b.

[0248] Step 630a: Start the third timer and the second counter bound to the third cell and increment the second counter by one; the timeout time of the third timer is the first preset time, and the initial value of the second counter is 0;

[0249] Step 630b: Each time the cell in question is the third cell and a service rejection message carrying the first reason value is received, increment the second counter by one.

[0250] In this embodiment of the invention, timers and counters can be bound to cells to time and count the number of rejections for that cell. This embodiment of the invention can bind timers and counters to multiple cells simultaneously, thereby identifying multiple problematic cells.

[0251] Step 632: When the second timing reaches the first preset time, if the second rejection count is less than or equal to the first threshold, stop the second timing and count the second rejection count.

[0252] In some possible embodiments, step 632 specifically includes: when the third timer times out, if the value of the second counter is less than or equal to the first threshold, stopping the third timer and the second counter and unbinding the third timer and the second counter from the third cell.

[0253] In this embodiment of the invention, the timeout of the third timer indicates that the time of the second timer exceeds the first preset time, and the value of the second counter is less than or equal to the first threshold, indicating that the second rejection count is less than or equal to the first threshold, indicating that the third cell may be temporarily unstable but not a problem cell, and therefore can continue to be used as a cell to be handed over. The third timer and the second counter are stopped and the third timer and the second counter are unbound from the third cell so that the unbound timer and counter can continue to be used.

[0254] Step 634: If the second rejection count exceeds the first threshold before the second timing reaches the first preset time, stop the second timing, stop counting the second rejection count, add the third cell to the blacklist, and start the fourth timing.

[0255] In this embodiment of the invention, when a third cell is found to be a problematic cell, the third cell is added to the blacklist and a fourth timer is started. The fourth timer is used to count the time it takes for the third cell to be added to the blacklist.

[0256] In some possible embodiments, step 634 specifically includes: when the third timer has not expired, the value of the second counter is greater than the first threshold, stopping the third timer and the second counter, adding the third cell to the blacklist and starting the fourth timer bound to the third cell, the timeout time of the fourth timer being the second preset time.

[0257] In this embodiment of the invention, if the third timer does not time out, it indicates that the second timing time has not exceeded the first preset time. If the value of the second counter is greater than the first threshold, it indicates that the second rejection count is greater than the first threshold, indicating that the third cell is a problem cell. Then, the third timer and the second counter are stopped to stop the second timing and count the second rejection count.

[0258] In this embodiment of the invention, the fourth timer can be bound to the second cell, and the fourth timer can be started when the third cell is added to the blacklist, so that the fourth timer can be used to count the time when the third cell is added to the blacklist.

[0259] Step 636: If the fourth timing time has not reached the second preset time, do not send the second measurement report corresponding to the third cell to the second device; or if the fourth timing time reaches the second preset time, stop the fourth timing and delete the third cell from the blacklist.

[0260] In some possible embodiments, step 636 specifically includes: not sending the third measurement report corresponding to the third cell to the second device when the fourth timer has not expired; or stopping the fourth timer and deleting the third cell from the blacklist when the fourth timer expires.

[0261] The timeout period of the fourth timer is the second preset time. If the fourth timer does not time out, it means that the time for adding the third cell to the blacklist has not reached the second preset time, and the third measurement report corresponding to the third cell will not be sent to the second device.

[0262] The fourth timer timeout indicates that the third cell has been added to the blacklist for longer than the second preset time. The fourth timer is then stopped, and the third cell is removed from the blacklist. Since the third cell is unlikely to remain a problematic cell and may become a good cell after a period of time, this embodiment of the invention removes the third cell from the blacklist when the time it has been added exceeds the second preset time. This stops the suppression of measurement reports from the third cell to the second device, allowing the second device to continue sending handover messages for the third cell, enabling the first device to handover to the third cell again.

[0263] In this embodiment of the invention, after the first device receives a service rejection message carrying the cause value "Implicitly de-registered" due to a problem in the first cell it is in, the second device will continue to send a handover message. The cell included in the handover message may be different from the first cell or the same as the first cell. When the cell included in the handover message is different from the first cell, that is, when the cell included in the handover message is the third cell, if a service rejection message carrying the cause value "Implicitly de-registered" is also received due to a problem in the third cell after handover, the first device will also time and count the number of rejections for the third cell. When the third cell is found to be a problematic cell, the first device will also add the third cell to the blacklist and will not continue to report the measurement report of the third cell to the second device, thereby preventing the second device from sending a handover message to the first device to hand over to the third cell, and thus preventing the first device from handing over to the third cell again.

[0264] Step 638: Terminate the service according to the second service rejection message, trigger initial registration to re-initiate attachment registration with the second device, and receive the third measurement configuration message of the measurement event sent by the second device after the initial registration is completed.

[0265] Step 640: Perform measurement of the measurement event on the neighboring cell according to the third measurement configuration message to obtain the second measurement report of the second cell; when the second measurement report meets the first condition of the measurement event, send the second measurement report to the second device.

[0266] The second cell is a neighboring cell that is different from the first and third cells. If the second measurement report does not meet the first condition of the measurement event, the second measurement report will not be sent to the second device.

[0267] Step 642: Receive the third handover message of the second cell sent by the second device, and successfully hand over to the second cell according to the third handover message.

[0268] The cell handover method provided in this embodiment of the invention requires chip manufacturers to modify the program before the equipment leaves the factory. After the equipment leaves the factory, users can use it directly but cannot modify it.

[0269] Figure 10 This is a schematic diagram of an electronic device provided in an embodiment of the present invention. It should be understood that the electronic device 700 is capable of executing the various steps of the first device in the above method embodiment. To avoid repetition, these steps will not be described in detail here. The electronic device 700 includes: a first transceiver 701 and a first processor 702.

[0270] The first transceiver 701 is used to receive a first handover message of a first cell sent by the second device. The first cell is a neighboring cell. The first measurement report of the first cell has been reported to the second device. The first measurement report is a measurement report obtained by performing a measurement event on the first cell.

[0271] The first processor 702 is configured to successfully switch to the first cell based on the first handover message.

[0272] When the first transceiver 701 receives the RRC release message sent by the second device and the first processor 702 determines that the first device has a service in progress, the first transceiver 701 is further configured to send a first service request message to the second device and receive a first service rejection message sent by the second device.

[0273] The first processor 702 is further configured to determine that the first service rejection message has been received and the first service rejection message carries a first reason value, and to switch to a second cell, the second cell being a neighboring cell different from the first cell, and the second measurement report of the second cell has been reported to the second device, the second measurement report being a measurement report obtained by performing the measurement event in the second cell.

[0274] Optionally, before the first processor 702 switches to the second cell, it is further configured to determine that the first service rejection message has been received and the first service rejection message carries the first reason value, start a first timer and start counting the first rejection count, wherein the first rejection count is the number of times the service rejection message carrying the first reason value has been received when the cell is the first cell; when the timer reaches a first preset time, the first rejection count is less than or equal to a first threshold, the first timer is stopped and the counting of the first rejection count is stopped; when the timer has not reached the first preset time, the first rejection count is greater than the first threshold, the first timer is stopped, the counting of the first rejection count is stopped and the first cell is added to the blacklist, wherein cells in the blacklist will not be reported to the second device.

[0275] Optionally, after the first processor 702 determines that it has received the first service rejection message and that the first service rejection message carries the first reason value, the first transceiver 701 is further configured to receive a second handover message for a third cell sent by the second device, wherein the third cell is a neighboring cell different from the first cell and the second cell, and a third measurement report of the third cell has been reported to the second device, wherein the third measurement report is a measurement report obtained by performing the measurement event on the third cell.

[0276] The first processor 702 is also configured to successfully switch to the third cell according to the second handover message.

[0277] When the first transceiver 701 receives the RRC release message and the first processor 702 determines that the first device has a service in progress, the first transceiver 701 is also used to send a second service request message to the second device and receive a second service rejection message sent by the second device.

[0278] The first processor 702 is further configured to determine that the second service rejection message has been received and the second service rejection message carries the first reason value, and then switch to the second cell.

[0279] Optionally, before the first processor 702 switches to the second cell, it is further configured to determine that the second service rejection message is received and the second service rejection message carries the first reason value, start a second timer and start counting the second rejection count, the second rejection count being the number of service rejection messages carrying the first reason value received when the cell is the third cell; when the second timer reaches the first preset time and the second rejection count is less than or equal to the first threshold, stop the second timer and stop counting the second rejection count; when the second timer does not reach the first preset time and the second rejection count is greater than the first threshold, stop the second timer, stop counting the second rejection count, and add the third cell to the blacklist.

[0280] Optionally, before the first transceiver 701 receives the first handover message of the first cell sent by the second device, it is further configured to receive the measurement configuration message of the measurement event sent by the second device.

[0281] The first processor 702 is further configured to perform the measurement of the measurement event on the neighboring cell according to the measurement configuration message, and obtain the first measurement report of the first cell.

[0282] The first transceiver 701 is further configured to not send the first measurement report to the second device when the first measurement report does not meet the first condition of the measurement event; or

[0283] When the first measurement report meets the first condition of the measurement event, the first measurement report is sent to the second device.

[0284] Optionally, the first processor 702 is specifically configured to start a first timer and a first counter bound to the first cell and increment the first counter by one; the timeout period of the first timer is the first preset time, and the initial value of the first counter is 0; in subsequent instances, each time the cell it is in is the first cell and a service rejection message carrying the first reason value is received, the first counter is incremented by one.

[0285] Optionally, the first processor 702 is specifically used to stop the first timer and the first counter.

[0286] Optionally, the first processor 702 is specifically used to unbind the first timer and the first counter from the first cell.

[0287] Optionally, when the first processor 702 adds the first cell to the blacklist, it is also used to start a third timing, and when the time of the third timing has not reached the second preset time, it does not send the first measurement report corresponding to the first cell to the second device; when the time of the third timing reaches the second preset time, it stops the third timing and deletes the first cell from the blacklist.

[0288] Optionally, the first processor 702 is specifically used to start a second timer bound to the first cell, the timeout period of the second timer being the second preset time; when the second timer has not expired, the first measurement report corresponding to the first cell is not sent to the second device.

[0289] Optionally, the first processor 702 is specifically configured to stop the second timer and remove the first cell from the blacklist when the second timer times out.

[0290] Optionally, the first processor 702 is specifically configured to start a third timer and a second counter bound to the third cell and increment the second counter by one; the timeout period of the third timer is the first preset time, and the initial value of the second counter is 0; in subsequent instances, each time the cell is the third cell and a service rejection message carrying the first reason value is received, the second counter is incremented by one.

[0291] Optionally, when the first processor 702 adds the third cell to the blacklist, it is also used to start a fourth timing, and if the time of the fourth timing has not reached the second preset time, it does not send the third measurement report corresponding to the third cell to the second device; if the time of the fourth timing reaches the second preset time, it stops the fourth timing and deletes the third cell from the blacklist.

[0292] Optionally, the first processor 702 is specifically configured to start a fourth timer bound to the third cell when the third cell is added to the blacklist, the timeout period of the fourth timer being the second preset time; and not send the third measurement report corresponding to the third cell to the second device when the fourth timer has not expired.

[0293] Optionally, after the first processor 702 determines that the first service rejection message carries the first reason value, it is further configured to terminate the service and trigger initial registration based on the first service rejection message so that the first transceiver 701 re-initiates attachment registration with the second device.

[0294] The first transceiver 701 is also configured to receive a measurement configuration message of the measurement event sent by the second device after the initial attachment registration is completed.

[0295] This application also provides an electronic device, including a processor and a memory, wherein the memory is used to store a computer program, and when the processor runs the computer program, the electronic device performs the operations involved in the first device in the above method embodiments.

[0296] This application also provides a computer-readable storage medium storing a computer program that, when run by an electronic device, causes the electronic device to perform the operations involved in the first device described in the above method embodiments.

[0297] This application also provides a computer program product that stores a computer program that, when run on an electronic device or at least one processor, causes the electronic device to perform the operations involved in the first device described in the above method embodiments.

[0298] In this application embodiment, "at least one" refers to one or more, and "more than one" refers to two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent the existence of A alone, the simultaneous existence of A and B, or the existence of B alone. A and B can be singular or plural. The character " / " generally indicates that the preceding and following related objects are in an "or" relationship. "At least one of the following" and similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, and c can represent: a, b, c, ab, ac, bc, or abc, where a, b, and c can be single or multiple.

[0299] Those skilled in the art will recognize that the units and algorithm steps described in the embodiments disclosed herein can be implemented using electronic hardware, computer software, or a combination of electronic hardware and software. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0300] Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0301] In the several embodiments provided in this application, any function, if implemented as a software functional unit and sold or used as an independent product, can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or a part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause an electronic device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0302] The above description is merely a specific embodiment of this application. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the protection scope of this application. The protection scope of this application should be determined by the protection scope of the claims.

Claims

1. A cell handover method, characterized in that, Applied to a first device, the method includes: The device receives a first handover message for a first cell from a second device. The first cell is a neighboring cell. The first measurement report of the first cell has been reported to the second device. The first measurement report is a measurement report obtained by performing a measurement event on the first cell. Successfully switched to the first cell according to the first handover message; When the first device receives an RRC release message from the second device and has services in operation, it sends a first service request message to the second device and receives a first service rejection message from the second device. Upon determining that the first service rejection message has been received and that the first service rejection message carries a first reason value, the device switches to a second cell, which is a neighboring cell different from the first cell. The second measurement report of the second cell has been reported to the second device. The second measurement report is a measurement report obtained by performing the measurement event in the second cell.

2. The method according to claim 1, characterized in that, Before switching to the second cell, the process also includes: Once it is determined that the first service rejection message has been received and the first service rejection message carries the first reason value, a first timer is started and the first rejection count is started. The first rejection count is the number of service rejection messages carrying the first reason value received when the cell is the first cell. When the first timeout period reaches the first preset time, the first rejection count is less than or equal to the first threshold, the first timeout is stopped and the counting of the first rejection count is stopped. If the first rejection count exceeds the first threshold before the first preset time has elapsed, the first timing is stopped, the counting of the first rejection count is stopped, and the first cell is added to the blacklist. Cells in the blacklist will not be reported to the second device.

3. The method according to claim 1 or 2, characterized in that, After determining that the first service rejection message has been received and that the first service rejection message carries the first reason value, the method further includes: The device receives a second handover message for a third cell from the second device. The third cell is a neighboring cell that is different from the first cell and the second cell. The third measurement report of the third cell has been reported to the second device. The third measurement report is a measurement report obtained by performing the measurement event on the third cell. Successfully switched to the third cell according to the second handover message; When the RRC release message is received and the first device has a service in progress, a second service request message is sent to the second device and a second service rejection message is received from the second device. If it is determined that the second service rejection message has been received and the second service rejection message carries the first reason value, then switch to the second cell.

4. The method according to any one of claims 1-3, characterized in that, Before switching to the second cell, the following also applies: Once it is determined that the second service rejection message has been received and the second service rejection message carries the first reason value, a second timer is started and the second rejection count is started. The second rejection count is the number of times a service rejection message carrying the first reason value has been received when the cell is the third cell. When the second timer reaches the first preset time, and the second rejection count is less than or equal to the first threshold, the second timer is stopped and the counting of the second rejection count is stopped. If the second rejection count exceeds the first threshold before the second timing reaches the first preset time, the second timing is stopped, the second rejection count is stopped, and the third cell is added to the blacklist.

5. The method according to any one of claims 1-4, characterized in that, Before receiving the first handover message of the first cell sent by the second device, the method further includes: Receive the measurement configuration message for the measurement event sent by the second device; The measurement event is performed on the neighboring cell according to the measurement configuration message to obtain the first measurement report of the first cell; If the first measurement report does not meet the first condition of the measurement event, the first measurement report will not be sent to the second device; or When the first measurement report meets the first condition of the measurement event, the first measurement report is sent to the second device.

6. The method according to claim 2, characterized in that, The process of starting the first timing and counting the first rejections specifically includes: Start the first timer and the first counter bound to the first cell and increment the first counter by one; the timeout period of the first timer is the first preset time, and the initial value of the first counter is 0; Each time the cell in question is the first cell and a service rejection message carrying the first reason value is received, the first counter is incremented by one.

7. The method according to claim 2 or 6, characterized in that, The step of stopping the first timing and stopping the counting of the first rejection count includes: Stop the first timer and the first counter.

8. The method according to claim 7, characterized in that, The step of stopping the first timing and stopping the counting of the first rejections also includes: Unbind the first timer and the first counter from the first cell.

9. The method according to any one of claims 2-8, characterized in that, Adding the first cell to the blacklist also includes: Start the third timing; if the third timing time has not reached the second preset time, do not send the first measurement report corresponding to the first cell to the second device. When the third timing reaches the second preset time, the third timing is stopped and the first cell is removed from the blacklist.

10. The method according to claim 9, characterized in that, The step of starting the third timing, whereby the first measurement report corresponding to the first cell is not sent to the second device before the third timing reaches the second preset time, includes: Start a second timer bound to the first cell, the timeout period of the second timer being the second preset time; If the second timer does not expire, the first measurement report corresponding to the first cell will not be sent to the second device.

11. The method according to claim 9, characterized in that, The step of stopping the third timing and removing the first cell from the blacklist when the third timing reaches the second preset time includes: When the second timer expires, the second timer is stopped and the first cell is removed from the blacklist.

12. The method according to claim 4, characterized in that, The process of starting the second timing and counting the second rejection count includes... Start the third timer and the second counter bound to the third cell and increment the second counter by one; the timeout period of the third timer is the first preset time, and the initial value of the second counter is 0; Each time the cell in question is the third cell and a service rejection message carrying the first reason value is received, the second counter is incremented by one.

13. The method according to claim 12, characterized in that, Adding the third cell to the blacklist also includes: Start the fourth timing; if the fourth timing time has not reached the second preset time, do not send the third measurement report corresponding to the third cell to the second device. When the fourth timing reaches the second preset time, the fourth timing is stopped and the third cell is removed from the blacklist.

14. The method according to claim 13, characterized in that, The step of starting the fourth timing, whereby the third measurement report corresponding to the third cell is not sent to the second device before the fourth timing reaches the second preset time, includes: When the third cell is added to the blacklist, a fourth timer bound to the third cell is started, and the timeout period of the fourth timer is the second preset time. If the fourth timer does not expire, the third measurement report corresponding to the third cell will not be sent to the second device.

15. The method according to any one of claims 1-14, characterized in that, After determining that the first service rejection message carries the first reason value, the method further includes: Based on the first service rejection message, the service is terminated and an initial registration is triggered to re-initiate attachment registration with the second device; After the initial registration is completed, the measurement configuration message for the measurement event sent by the second device is received.

16. An electronic device, characterized in that, It includes a processor and a memory, wherein the memory is used to store a computer program that, when the processor runs the computer program, causes the electronic device to perform the method as described in any one of claims 1-15.

17. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when executed by a computer, causes the computer to perform the method as described in any one of claims 1-15.

18. A computer program product, characterized in that, The computer program product stores a computer program that, when run on a computer or any at least one processor, causes the computer to perform the method as described in any one of claims 1-15.

Images