A cell handover method, a terminal device and a readable storage medium

Abstract

This application provides a cell handover method, a terminal device, and a readable storage medium, relating to the field of communication technology. The method is applied to a terminal device accessing a first cell. The method includes: determining a second cell from neighboring cells of the first cell based on the service type of the terminal device's foreground service and the first cell's support for CDRX configuration capabilities; wherein the service type includes real-time services and non-real-time services; and handing over the cell accessed by the terminal device from the first cell to the second cell. Through the technical solution provided by the embodiments of this application, the terminal device can select a suitable cell to camp on based on the service type of the foreground service, thereby balancing the power consumption and latency requirements of the terminal device during cellular communication.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to a cell handover method, terminal equipment, and readable storage medium. Background Technology

[0002] Once a terminal device (such as a mobile phone) successfully registers with a cell, it can communicate with the network devices corresponding to that cell, access the cellular network, and thus make cellular calls or use cellular data.

[0003] Currently, terminal devices and network devices communicate by establishing a Radio Resource Control (RRC) connection. After a successful RRC connection, the terminal device is in an RRC connected state. For the RRC connected state, the network device typically configures a specific data reception mode for the terminal device, such as connected continuous reception (CCRX) or connected discontinuous reception (CDRX). In CCRX mode, the terminal device continuously receives data, resulting in higher power consumption but lower latency. In CDRX mode, the terminal device intermittently receives data, resulting in higher latency but lower power consumption. Since the communication services handled by the terminal device are diverse—some services (such as video calls) have high latency requirements, while others (such as SMS) have low latency requirements—if the terminal device continuously receives data in either CCRX or CDRX mode, it will be impossible to simultaneously meet the power consumption needs of the terminal device and the latency requirements of different services. Summary of the Invention

[0004] This application provides a cell handover method, a terminal device, and a readable storage medium to solve the problem in the prior art that terminal devices cannot simultaneously meet power consumption and latency requirements during cellular communication.

[0005] To achieve the above objectives, this application adopts the following technical solution:

[0006] In a first aspect, this application provides a cell handover method applied to a terminal device, wherein the terminal device accesses a first cell, and the method includes: determining a second cell from the neighboring cells of the first cell based on the service type of the terminal device's foreground service and the support of the first cell for CDRX configuration capabilities; wherein the service type includes real-time services and non-real-time services; and handing over the cell accessed by the terminal device from the first cell to the second cell.

[0007] The cell handover method provided in this application allows the terminal device to select a suitable second cell from the neighboring cells of the first cell for connection based on whether the foreground service is a real-time or non-real-time service and the support of the CDRX configuration capability of the currently camped first cell, thereby taking into account both the power consumption of the terminal and the latency requirements of the foreground service.

[0008] For example, for real-time services, terminal devices can choose to reside in cells that do not support CDRX configuration capabilities to meet the latency requirements of foreground services. For non-real-time services, terminal devices can choose to reside in cells that support CDRX configuration capabilities to reduce the power consumption of the terminal devices.

[0009] In some embodiments, after detecting the first triggering event, the terminal device determines the second cell from the neighboring cells of the first cell based on the service type of the terminal device's foreground service and the support of the first cell for CDRX configuration capabilities.

[0010] In some embodiments, the first triggering event is: during the process of processing foreground services, the terminal device detects a change in the neighboring cells of the first cell; or, the foreground of the terminal device switches from a state without services to processing foreground services; or, the foreground of the terminal device switches from processing the first service to processing the second service, and the service types of the first service and the second service are different.

[0011] It should be noted that the first service and the second service can be different specific services under the same application (such as the chat service and video call service of an instant messaging application), or they can be services of different applications (such as the chat service of an instant messaging application and the web browsing service of a browser).

[0012] In some embodiments, determining a second cell from the neighboring cells of the first cell based on the service type of the front-end service of the terminal device and the support of the first cell for CDRX configuration capability includes: if the service type of the front-end service is a real-time service and the first cell supports CDRX configuration capability, then determining a second cell from the neighboring cells of the first cell, wherein the second cell does not support CDRX configuration capability.

[0013] The cell handover method provided in this embodiment allows the terminal device to select a cell that does not support CDRX configuration capability for real-time services to camp on, so that the terminal device can receive downlink data sent by the network device in real time and reduce latency during communication.

[0014] In some embodiments, determining a second cell from the neighboring cells of the first cell based on the service type of the foreground service of the terminal device and the support of the first cell for CDRX configuration capability includes: if the service type of the foreground service is a real-time service, and both the first cell and the neighboring cells of the first cell support CDRX configuration capability, then determining a second cell from the neighboring cells of the first cell, wherein the CDRX cycle of the second cell is less than that of the first cell.

[0015] The method provided in this embodiment enables the terminal device to connect to a cell with a shorter CDRX period when both the primary cell and neighboring cells support CDRX configuration capabilities (i.e., they can only intermittently receive downlink data from network devices in CDRX mode). For example, the terminal device can select a neighboring cell with the shortest CDRX period as the second cell to minimize the latency of foreground services. Alternatively, a neighboring cell with a CDRX period comparable to the latency requirement can be selected as the second cell to simultaneously meet the power consumption and latency requirements of the terminal device.

[0016] In some embodiments, determining a second cell from the neighboring cells of the first cell based on the service type of the front-end service of the terminal device and the support of the first cell for CDRX configuration capability includes: if the service type of the front-end service is a non-real-time service and the first cell does not support CDRX configuration capability, then determining a second cell from the neighboring cells of the first cell, wherein the second cell supports CDRX configuration capability.

[0017] The method provided in this embodiment allows the terminal device to select a cell that supports CDRX configuration capability for non-real-time services, so that the terminal device can intermittently receive data sent by the network device and reduce the power consumption of the terminal device.

[0018] In some embodiments, determining a second cell from the neighboring cells of the first cell based on the service type of the front-end service of the terminal device and the support of the first cell for CDRX configuration capability includes: if the service type of the front-end service is a non-real-time service, and the first cell supports CDRX configuration capability, then determining a second cell from the neighboring cells of the first cell, wherein the second cell supports CDRX configuration capability, and the CDRX cycle of the second cell is greater than that of the first cell.

[0019] The method provided in this embodiment allows the terminal device to select a cell with a larger CDRX period for connection to non-real-time services, so that the terminal device can minimize power consumption when intermittently receiving data sent by the network device while meeting the latency requirements of foreground services.

[0020] In some embodiments, determining a second cell from the neighboring cells of a first cell, wherein the second cell does not support CDRX configuration capability, includes: determining a second cell from the neighboring cells of a first cell, wherein the second cell does not support CDRX configuration capability, and satisfies power screening conditions and / or signal-to-noise ratio screening conditions.

[0021] In some embodiments, determining a second cell from the neighboring cells of a first cell, the second cell supporting CDRX configuration capability, includes: determining a second cell from the neighboring cells of a first cell, the second cell supporting CDRX configuration capability, and satisfying at least one of periodic filtering conditions, power filtering conditions, and signal-to-noise ratio filtering conditions.

[0022] In some embodiments, the power screening condition is: |RSRP servingcell -RSRP(i)|<δ th Among them, RSRP servingcell Let δ be the reference signal received power of the first cell, RSRP(i) be the reference signal received power of the i-th neighboring cell of the first cell, and δ be the reference signal received power of the first cell. th A threshold is used to measure the difference in received power of the reference signal. Alternatively, the power screening condition is: RSRP(i) is greater than or equal to the received power threshold of the reference signal. Using the above power screening condition, the terminal device can determine a second cell with an RSRP no lower than that of the first cell, thus avoiding a deterioration in communication quality after the terminal device switches from the first cell to the second cell.

[0023] In some embodiments, the signal-to-noise ratio (SNR) screening condition is: SINR(i) > δ op Where SINR(i) is the signal-to-noise ratio of the i-th neighboring cell of the first cell, δ op This is the signal-to-noise ratio threshold.

[0024] Alternatively, the signal-to-noise ratio (SNR) selection criterion is: |SINR servingcell -SINR(i)|<δ SINR Among them, SINR servingcell Let δ be the signal-to-noise ratio of the first cell, SINR(i) be the signal-to-noise ratio of the i-th neighboring cell of the first cell, and δ be the signal-to-noise ratio of the i-th neighboring cell of the first cell. SINR The threshold is used to measure the difference in signal-to-noise ratio.

[0025] By using the above signal-to-noise ratio (SNR) filtering conditions, the terminal device can identify a second cell with a high SNR to ensure communication quality after the terminal device switches from the first cell to the second cell.

[0026] In some embodiments, the period filtering condition is: the CDRX period is less than a time threshold. This period filtering condition can prevent excessive latency in the terminal device during foreground processing.

[0027] Alternatively, the period selection criterion can be: the CDRX period is the maximum value among the CDRX periods of the candidate cells, which includes neighboring cells that meet the above power selection criterion and / or signal-to-noise ratio selection criterion. This period selection criterion minimizes the power consumption of the terminal device during foreground service processing.

[0028] Alternatively, the period selection criterion can be: the CDRX period is the minimum value among the CDRX periods of the candidate cells, which includes neighboring cells that meet the above power selection criterion and / or the above signal-to-noise ratio selection criterion. This period selection criterion can minimize the latency of the terminal device during the processing of foreground services.

[0029] Alternatively, the cycle selection criterion can be the correspondence between the latency requirements of foreground services and the CDRX cycle. This cycle selection criterion allows the terminal device to balance power consumption and latency when processing foreground services.

[0030] Optionally, in the above period selection criteria, the CDRX period is the long CDRX period. This is because when the foreground service is a non-real-time service, the terminal device usually receives downlink data based on the long CDRX period. Therefore, determining the second cell based on the long CDRX period can identify a more suitable second cell.

[0031] Secondly, embodiments of this application provide a cell handover device applied to a terminal device that accesses a first cell. The device includes:

[0032] The determination module is used to determine the second cell from the neighboring cells of the first cell based on the service type of the front-end service of the terminal device and the support of the first cell for CDRX configuration capabilities; wherein, the service type includes real-time services and non-real-time services.

[0033] The switching module is used to switch the cell accessed by the terminal device from the first cell to the second cell.

[0034] Thirdly, embodiments of this application provide a terminal device that accesses a first cell and is configured to perform the cell handover method as shown in the first aspect above.

[0035] Fourthly, embodiments of this application provide a chip including a processor that executes a computer program stored in a memory to implement the cell handover method as shown in the first aspect above.

[0036] Fifthly, embodiments of this application provide a computer-readable storage medium storing a computer program that, when executed by a processor, implements the cell handover method as described in the first aspect above.

[0037] In a sixth aspect, embodiments of this application provide a computer program product, which includes a computer program that, when run by a terminal device, enables the terminal device to implement the cell handover method shown in the first aspect above.

[0038] It is understood that the beneficial effects of the second to sixth aspects mentioned above can be found in the relevant descriptions in the first aspect mentioned above, and will not be repeated here. Attached Figure Description

[0039] Figure 1 This is a schematic diagram of cell distribution provided in an embodiment of this application;

[0040] Figure 2 This is a schematic diagram of an inter-device mobile communication system provided in an embodiment of this application;

[0041] Figure 3 This is a schematic diagram of the user plane and control plane protocol stacks of the terminal device and network device provided in the embodiments of this application;

[0042] Figure 4 This is a schematic diagram of the overall current of the terminal device provided in the embodiments of this application;

[0043] Figure 5 This is a schematic flowchart of a cell handover method provided in one embodiment of this application;

[0044] Figure 6 This is a schematic diagram of a CDRX cycle provided in an embodiment of this application;

[0045] Figure 7 This is a schematic flowchart of a cell handover method provided in another embodiment of this application;

[0046] Figure 8 This is a schematic diagram illustrating the process of determining a second cell according to an embodiment of this application;

[0047] Figure 9 This is a schematic diagram illustrating the process of determining a second cell according to another embodiment of this application;

[0048] Figure 10 This is a schematic diagram of the structure of a terminal device provided in an embodiment of this application;

[0049] Figure 11 This is a schematic diagram of the structure of a chip provided in an embodiment of this application. Detailed Implementation

[0050] The technical solutions provided in the embodiments of this application will be described below with reference to the accompanying drawings.

[0051] It should be understood that in the description of the embodiments of this application, unless otherwise stated, " / " means "or". For example, A / B can mean A or B. The "and / or" in this document is merely a description of the relationship between related objects, indicating that there can be three relationships. For example, A and / or B can mean: A exists alone, A and B exist simultaneously, and B exists alone.

[0052] In this embodiment, the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of indicated technical features. Therefore, a feature defined as "first" or "second" may explicitly or implicitly include one or more of that feature. In the description of this embodiment, unless otherwise stated, "a plurality of" means two or more.

[0053] In cellular mobile communication systems, the signal coverage area of ​​a network device or a portion of a network device (such as a sector antenna) is called a cell. For example, see [link to example]. Figure 1 As shown, to ensure that terminal devices located at the cell edge can detect cells, cells are typically distributed in an overlapping manner, with the overlap between two adjacent cells accounting for about one-third of a single cell. Therefore, terminal devices can detect multiple cells in certain locations (e.g., overlapping areas of multiple cells).

[0054] Currently, after a terminal device searches for multiple cells, it defaults to selecting the cell with the highest reference signal receiving power (RSRP) to camp on. Once camped on that cell, the terminal device can communicate with the network equipment corresponding to that cell, access the cellular network, and thus make cellular calls or use cellular data. In this embodiment, the cell currently camped on by the terminal device is referred to as the primary cell or serving cell, and cells that the terminal device can find but does not camp on are referred to as neighboring cells, adjacent cells, or neighboring cells.

[0055] Figure 2 This is a schematic diagram of a device-to-device mobile communication system provided in an embodiment of this application. See also... Figure 2 As shown, the communication system includes network devices and terminal devices. The link through which the terminal device sends data to the network device is called the uplink, while the link through which the terminal device receives data sent by the network device is called the downlink.

[0056] In mobile communication systems, the network equipment can be: an evolved node B (eNB), a home base station, an access point (AP) in a wireless fidelity (WiFi) system, a wireless relay node, a wireless backhaul node, a transmission point (TP), or a transmission and reception point (TRP), etc. It can also be a next-generation node B (gNB) in a new radio (NR) system, or it can be a component or part of the equipment that constitutes a base station, such as a central unit (CU), a distributed unit (DU), or a baseband unit (BBU), etc.

[0057] The terminal device in this mobile communication system can also be referred to as a terminal, user equipment (UE), mobile station (MS), mobile terminal (MT), etc. In this application embodiment, the terminal device can be a mobile phone, tablet computer, computer with wireless transceiver capabilities, or a wireless terminal applied in scenarios such as virtual reality (VR), augmented reality (AR), industrial control, self-driving, remote medical care, smart grid, transportation safety, smart city, and smart home. It should be noted that this application embodiment does not limit the specific technology or device form used in the terminal device.

[0058] In some embodiments, see Figure 3As shown, the user plane protocol stack of terminal and network devices includes the Packet Data Convergence Protocol (PDCP) layer, Radio Link Control (RLC) layer, Media Access Control (MAC) layer, and Physical Layer (PHY). The control plane protocol stack of terminal devices includes the Non-Access Stratum (NAS), Radio Resource Control (RRC) layer, PDCP layer, RLC layer, MAC layer, and PHY layer. The base station of network devices includes the RRC layer, PDCP layer, RLC layer, MAC layer, and PHY layer, and the mobility management entity (MME) of network devices includes the NAS. The PHY layer is the lowest layer, also known as Layer 1. The MAC, RLC, and PDCP layers are intermediate layers, also known as Layer 2. The RRC and NAS layers are higher layers, also known as Layer 3. The main function of Layer 1 is to provide reliable bit stream transmission between two physical entities and adapt the transmission medium. The main functions of Layer 2 are channel multiplexing and demultiplexing, data format encapsulation, and packet scheduling. The main functions of Layer 3 are addressing, routing, connection establishment and control, and resource allocation strategies.

[0059] For the RRC layer, the terminal device's state includes the RRC idle (RRC_IDLE) state and the RRC connected (RRC_CONNECTED) state. These will be explained below.

[0060] (1) RRC_IDLE state

[0061] If the terminal device and the network device do not establish an RRC connection, the terminal device is in the RRC_IDLE state. In the RRC_IDLE state, the terminal device can perform public land mobile network (PLMN) selection, receive system messages broadcast by the network device, perform cell reselection, receive paging messages, or receive indication information for the terminal device to be paged.

[0062] (2) RRC_CONNECTED state

[0063] If a terminal device establishes an RRC connection with a network device, the terminal device is in the RRC_CONNECTED state. In the RRC_CONNECTED state, the terminal device can establish user plane and control plane connections with the network device to transmit user plane data and control plane signaling.

[0064] When a terminal device needs to receive downlink data from a network device or send uplink data to a network device, it needs to enter RRC connection state. (See also...) Figure 4 As shown in the schematic diagram of the terminal device's overall current, in RRC connection mode, the terminal device continuously receives downlink data from the network device, leading to increased current and higher power consumption. Furthermore, in some embodiments, for example... Figure 4 As shown, in RRC connection mode, the terminal device spends relatively little time actually processing services, and the rest of the time is spent maintaining the channel without receiving downlink data, resulting in a certain degree of power consumption waste. Therefore, in some embodiments, the network device can configure the terminal device in CDRX mode, allowing the terminal device to intermittently receive downlink data, i.e., receiving downlink data for a period of time and not receiving downlink data for another period, thereby reducing the power consumption of the terminal device.

[0065] However, some network devices support configuring CDRX mode for terminal devices (this can also be described as the network device supporting CDRX configuration capability, or the network device being configured with CDRX, etc.). Other network devices do not support configuring CDRX mode for terminal devices (this can also be described as the network device not supporting CDRX configuration capability, or the network device not being configured with CDRX, etc.).

[0066] If the network device supports configuring CDRX mode for the terminal device, after establishing an RRC connection with the terminal device, the network device will send CDRX parameters (including the CDRX period) to the terminal device, configuring the terminal device's data reception mode to CDRX mode. During communication between the network device and the terminal device in the RRC connection state, the terminal device sends data according to the CDRX parameters, and the terminal device intermittently receives downlink data from the network device according to the CDRX parameters, achieving the purpose of saving power consumption. However, in CDRX mode, since the terminal device does not receive data for a period of time, there is usually a certain delay in the terminal device's data reception.

[0067] If the network device does not support CDRX configuration capability, during the communication between the network device and the terminal device in RRC connection state, the network device continuously sends data down, while the terminal device continuously receives downlink data in CCRX mode. This process consumes more power but has less latency.

[0068] A network device typically serves multiple (e.g., thousands) terminal devices and configures these devices with the same data reception mode. Therefore, after a terminal device establishes an RRC connection with the network device, its data reception mode in the RRC connection state is determined. In other words, the data reception mode configured by the network device for the terminal device is usually fixed. For example, a network device that supports CDRX configuration will configure the terminal device in CDRX mode, while a network device that does not support CDRX configuration will configure the terminal device in CCRX mode by default.

[0069] However, the communication services handled by terminal devices are diverse. Some services (such as video calls, gaming, and live streaming) have high latency requirements, while others (such as SMS and web browsing) have low latency requirements. If the terminal device always receives data in a fixed CCRX or CDRX mode, it will be impossible to balance the power consumption of the terminal device with the latency requirements of different services.

[0070] For example, if the primary cell of the terminal device does not support CDRX configuration capability, the terminal device can only continuously receive downlink data in RRC connected state. When the terminal device handles real-time services such as video calls, it can meet the latency requirements of the service without wasting unnecessary power. However, when the terminal device handles non-real-time services such as web browsing, since web browsing does not require the terminal device to receive downlink data in real time, the terminal device will waste unnecessary power.

[0071] In this embodiment, the services running on the terminal device include foreground services and background services. During the operation of foreground services, the corresponding service content can be displayed on the terminal device's screen for the user to view and operate. However, during the operation of background services, the user cannot view or operate the corresponding service content. In other words, the foreground application is in an active state (activity state) during operation, while the background application is in an inactive state (inactivity state).

[0072] For example, if the primary cell of the terminal device supports CDRX configuration capability and CDRX mode is configured for the terminal device, then the terminal device will intermittently receive downlink data. When the foreground service handled by the terminal device is a non-real-time service such as web browsing, since web browsing does not require the terminal device to receive downlink data in real time, the terminal device meets the latency requirements of web browsing while saving device power consumption. However, when the foreground service handled by the terminal device is a real-time service with high latency requirements such as video calls, the intermittent reception of downlink data in CDRX mode will lead to increased latency, potentially causing call stuttering and affecting the user's call experience.

[0073] Therefore, this application provides a cell handover method, which involves a terminal device switching cells based on the service type of the foreground service (i.e., whether the foreground service is a real-time service or a non-real-time service) and the support of the CDRX configuration capabilities of the primary cell and its neighboring cells. This method can flexibly switch cells, taking into account both the power consumption of the terminal device and the latency requirements of different services.

[0074] In the technical solution provided in this application, the terminal device can switch the cell it camps on when the foreground service remains unchanged but the neighboring cells change; it can also switch the cell it camps on after the service type of the foreground service changes. These will be explained separately below.

[0075] (i) Front-end services remain unchanged, but neighboring areas have changed.

[0076] During communication with network devices, terminal devices may move (e.g., follow the user's movement), causing changes in the terminal device's neighboring cells. These changes include: changes in neighboring cells when the primary cell remains unchanged; and changes in neighboring cells after the primary cell has changed.

[0077] Figure 5 This is a schematic flowchart illustrating a cell handover method provided in one embodiment of this application, involving the process of a terminal device switching cells based on the service type after a change in neighboring cells. Specifically, it includes the following:

[0078] S501, the terminal device is currently camped on the first cell and while running the first service in the foreground, it detects a change in the neighboring cells of the first cell.

[0079] The terminal device is currently camped on the first cell, which can be understood as the terminal device's primary cell being the first cell, or the terminal device currently accessing the cellular network through the first cell, or the terminal device being able to establish an RRC connection with the network device corresponding to the first cell and exchange data.

[0080] Terminal devices can detect neighboring cell information through a modem, including the neighboring cell's cell identity (CI), CDRX parameters (including whether CDRX configuration capability is supported, CDRX cycle, etc.), RSRP, and signal-to-interference plus noise ratio (SINR).

[0081] Optionally, after a detection, if the cell number of the neighboring cell detected by the terminal device this time is different from the cell number of the neighboring cell detected last time, then the terminal device is considered to have a change in the neighboring cells. For example, if the cell numbers of the neighboring cells detected this time are CI2, CI3, and CI4, while the cell numbers of the neighboring cells detected last time were CI1, CI2, and CI3, then the terminal device determines that the neighboring cells have changed.

[0082] Normally, after a terminal device camps on a cell and establishes an RRC connection with a network device, the network device will send the CDRX parameters of that cell to the terminal device. Based on this, the embodiments of this application can determine the CDRX parameters of neighboring cells in any of the following ways.

[0083] Method 1: The terminal device determines the CDRX parameters of the neighboring cell based on local historical records.

[0084] As a terminal device moves with the user, it typically switches automatically to the target cell with the highest RSRP (Responsible RSRP) based on the RSRP values ​​of the primary and neighboring cells. Once the terminal device establishes an RRC (Responsible RRC Connection) with the network device corresponding to the target cell, if the target cell supports CDRX (Content Configuration Parameters) capability, the terminal device can obtain the CDRX parameters of that target cell. It can be understood that as the terminal device moves, it can sequentially access multiple different target cells and obtain the CDRX parameters of these different target cells. After obtaining the CDRX parameters of a cell each time, the terminal device can store the correspondence between the cell number and the CDRX parameters, establishing a CDRX parameter mapping table.

[0085] Based on this, after detecting a change in a neighboring cell, the terminal device can query the CDRX parameter correspondence table according to the cell number of the neighboring cell to determine the CDRX parameters of each neighboring cell.

[0086] Method 2: The terminal device queries the CDRX parameters of the neighboring cell from the cloud.

[0087] A mobile network operator typically serves multiple terminal devices. After obtaining the CDRX parameters of the cell they are connected to, these devices can send the mapping between cell number and CDRX parameters to a cloud server for storage, forming a CDRX parameter mapping table. It's understandable that, because these terminal devices are widely distributed, the cloud server can obtain the CDRX parameters of the vast majority of the operator's cells.

[0088] Based on this, after detecting a change in a neighboring cell, the terminal device can query the CDRX parameter mapping table from the cloud server based on the neighboring cell's cell number to obtain the CDRX parameters of each neighboring cell. Alternatively, the terminal device can download the entire contents of the CDRX parameter mapping table, or the portion of the table related to the terminal device's location, to its local machine. After detecting a change in a neighboring cell, the terminal device can query the CDRX parameter mapping table based on the neighboring cell's cell number to determine the CDRX parameters of each neighboring cell.

[0089] It should be noted that if the terminal device cannot determine the CDRX parameters of a neighboring cell, the second cell will not be determined based on that neighboring cell in the subsequent process.

[0090] S502, the terminal device determines the second cell from the neighboring cells of the first cell based on the service type of the first service and the support of the first cell for CDRX configuration capabilities.

[0091] In this embodiment, the service types include real-time services and non-real-time services. This application embodiment refers to cellular communication services with high latency requirements (e.g., latency below or equal to a latency threshold) as real-time services, which can include video calls, live streaming, and gaming. Conversely, cellular communication services with low latency requirements (e.g., latency above a latency threshold) are referred to as non-real-time services, which can include SMS and web browsing.

[0092] In this embodiment, the first service running on the foreground of the terminal device may be a non-real-time service or a real-time service. The process of determining the second cell will be described below for both of these cases.

[0093] (1) The first service is a non-real-time service.

[0094] Non-real-time services typically have lower latency requirements. From the perspective of saving device power consumption, terminal devices can prioritize using CDRX mode to receive data sent by network devices when processing non-real-time services. Based on this, terminal devices can choose to camp on cells that support CDRX configuration capabilities when processing non-real-time services, thereby reducing the power consumption of terminal devices while meeting the latency requirements of non-real-time services.

[0095] In one possible implementation, after detecting a change in a neighboring cell, the terminal device can first determine whether the first cell supports CDRX configuration capability, and then determine whether it is necessary to determine the second cell from the neighboring cells.

[0096] If the first cell supports CDRX configuration capability, it means that when the terminal device is camped on the first cell, it is in CDRX mode, intermittently receiving downlink data sent by the network device, and the power consumption of the terminal device is low during the reception process. Therefore, the terminal device does not need to select other cells that support CDRX configuration capability from the neighboring cells of the first cell, that is, it does not need to determine the second cell from the neighboring cells.

[0097] Optionally, if the first cell supports CDRX configuration capability, the terminal device can also determine whether the CDRX period of the first cell is greater than the latency requirement of the first service. If the CDRX period of the first cell is less than or equal to the latency requirement of the first service, a second cell will not be selected from the neighboring cells. If the CDRX period of the first cell is greater than the service requirement of the first service, a second cell will be selected from the neighboring cells, and the CDRX period of the second cell will be less than or equal to the latency requirement of the first service.

[0098] If the first cell where the terminal device is camped does not support CDRX configuration capability, the terminal device will typically continuously receive downlink data from the network device in CCRX mode, resulting in high power consumption during reception. To save power consumption, a neighboring cell that supports CDRX configuration capability (i.e., the second cell) can be selected from the neighboring cells of the first cell. This allows the terminal device to receive data from the network device in CDRX mode, thus meeting the latency requirements of non-real-time services while reducing power consumption.

[0099] Optionally, when selecting a second cell from the neighboring cells of the first cell, the terminal device may select a second cell that supports CDRX configuration function from the neighboring cells of the first cell according to the CDRX cycle.

[0100] See Figure 6 As shown, the CDRX cycle includes "On Duration" (active period) and "Opportunity for CDRX" (dormant period). During "On Duration," the terminal device receives downlink service data based on information received on the physical downlink control channel (PDCCH). During "Opportunity for CDRX," the terminal device shuts down its receiving circuitry and does not receive downlink data to conserve power.

[0101] The ratio of active to dormant periods within a CDRX cycle is configurable. Within different CDRX cycles, the "OnDuration" (activation period) is the same, while the "Opportunity for DRX" (dormancy period) differs. Therefore, it can be understood that a longer CDRX cycle results in a longer dormancy period; conversely, a shorter CDRX cycle results in a shorter dormancy period. A "same CDRX cycle" specifically refers to a CDRX cycle where both the active and dormant periods are the same.

[0102] In some embodiments, a cell can be configured with two CDRX cycles: a long CDRX cycle and a short CDRX cycle. The activation period is the same in both the long and short CDRX cycles, but the sleep period differs. Therefore, in the short CDRX cycle, the terminal device only sleeps for a short time after the activation period ends to receive downlink data promptly, reducing latency during service processing. In the long CDRX cycle, compared to the short CDRX cycle, the terminal device needs to sleep for a longer time after the activation period ends, resulting in higher latency during service processing, but relatively lower power consumption. The specific values ​​of the long and short CDRX cycles are configurable. For example, the long CDRX cycle can be 80ms and the short CDRX cycle can be 20ms; or, the long CDRX cycle can be 60ms and the short CDRX cycle can be 20ms.

[0103] In RRC connected mode, network devices and terminal devices can selectively use long CDRX periods and short CDRX periods depending on the specific service processing. For example, when a terminal device is processing Voice over Internet Protocol (VoIP) services, the network device can send downlink data to the terminal device using a short CDRX period, while the terminal device receives downlink data using the same period, reducing latency. Conversely, during longer silent periods in a voice call, the network device can send data to the terminal device using a long CDRX period, while the terminal device receives downlink data using the same period, saving power.

[0104] Based on the above description, optionally, when the terminal device's first service (i.e., the terminal device's foreground service) is a non-real-time service, in RRC connection mode, since the terminal device actually processes services for a relatively short time, it mostly receives downlink data based on the long CDRX period. Therefore, the terminal device can select a second cell based on the long CDRX period. For example, it can select a neighboring cell with a longer CDRX period as the second cell, thereby minimizing the terminal device's power consumption. Of course, in some embodiments, the terminal device can also select a second cell from neighboring cells based on a short CDRX period; this embodiment does not impose any restrictions on this.

[0105] Furthermore, different non-real-time services have different latency requirements. To balance the latency requirements of non-real-time services with the power consumption of terminal devices, terminal devices can filter cells whose CDRX cycles (e.g., long CDRX cycles) meet the latency requirements of the service, thereby determining a second cell. Taking a web browsing service with a latency requirement of 500ms as an example, the terminal device can select a second cell from neighboring cells with a long CDRX cycle of around 500ms (e.g., between 450ms and 550ms, or between 480ms and 520ms).

[0106] (2) The first service is real-time service.

[0107] Real-time services typically have high latency requirements. To meet these requirements, in this embodiment, the terminal device can use CCRX mode to receive downlink data from the network device. Based on this, the terminal device can choose to camp on a cell that does not support CDRX configuration capabilities.

[0108] In one possible implementation, after detecting a change in a neighboring cell, the terminal device can first determine whether the first cell supports CDRX configuration capability, and then determine whether it is necessary to identify a second cell from the neighboring cells.

[0109] If the first cell supports CDRX configuration capability, it means that when the terminal device is camped on that first cell, it is in CDRX mode, intermittently receiving downlink data from the network device. However, since the primary service is a real-time service, the latency of receiving data in CDRX mode is relatively large, which cannot meet the latency requirements of real-time services and may lead to service interruptions and a poor user experience. For example, when the primary service running on the foreground of the terminal device is a video call, if the terminal device's current camped cell supports CDRX configuration capability after a change in neighboring cells, the latency of the terminal device intermittently receiving downlink data from the network device in CDRX mode will be relatively large, resulting in video interruptions or unclear images. To address this, the terminal device can select a neighboring cell (i.e., a second cell) that does not support CDRX configuration capability from the neighboring cells of the first cell, so that the terminal device can continuously receive data from the network device in CDRX mode, reducing latency.

[0110] Optionally, if the first service is a real-time service, and if the first cell currently in which the terminal device is camped supports CDRX configuration capability, and all neighboring cells of the first cell also support CDRX configuration capability, and the CDRX cycle of the first cell is greater than the service requirements of the first service, then the terminal device can also determine the CDRX cycle of each neighboring cell and select a neighboring cell with a CDRX cycle less than the latency requirements of the first service as the second cell. Through the method provided in this embodiment, the terminal device can minimize latency during real-time service processing, which helps improve the user experience.

[0111] Alternatively, if the first service is a real-time service, and the first cell currently in which the terminal device is camped supports CDRX configuration capability, and all neighboring cells of the first cell also support CDRX configuration capability, and the CDRX period of the first cell is greater than the latency requirement of the first service, then the terminal device can also determine the CDRX period of each neighboring cell and the latency requirement of the foreground service, and select a cell from these neighboring cells whose CDRX period is close to the latency requirement as the second cell. Taking the latency requirement of a certain live broadcast service as 80ms as an example, the terminal device can select a cell from the neighboring cells of the first cell with a CDRX period of around 80ms (e.g., between 60ms and 100ms) as the second cell. Through the method provided in this embodiment, the terminal device can simultaneously consider the latency requirements of the foreground service and the power consumption of the device, saving device power while also ensuring a good user experience.

[0112] If the first cell does not support CDRX configuration capability, it means that when the terminal device is camped on the first cell, it is in CCRX mode and continuously receives downlink data sent by the network device. The data reception latency is relatively small and can meet the latency requirements of real-time services. Therefore, the terminal device does not need to select a neighboring cell (i.e., the second cell) that does not support CDRX configuration capability from the neighboring cells of the first cell.

[0113] It should be noted that in the above embodiments, when the foreground service is a real-time service, the second cell selected by the terminal device does not support the CDRX configuration function, that is, the second cell does not have a CDRX cycle.

[0114] S503, the terminal device switches the cell it is camped on from the first cell to the second cell.

[0115] In RRC connected mode, after the terminal device searches for multiple cells and determines that the target cell is the second cell, it modifies the RSRPs of the remaining cells to be lower than the RSRP of the second cell. Subsequently, it reports the RSRP of the second cell and the modified RSRPs of the remaining cells to the network device. Upon receiving these cell RSRPs, the network device instructs the terminal device to connect to the cell with the highest RSRP (i.e., the second cell), thus enabling the terminal device to switch from the first cell to the second cell in RRC connected mode.

[0116] It should be noted that a network device may correspond to one cell or multiple cells, and the support for CDRX configuration capabilities among these multiple cells may be the same or different. In other words, multiple cells corresponding to a single network device may all support CDRX configuration capabilities and their CDRX parameters can be configured manually; or none of them may support CDRX configuration capabilities; or some cells may support CDRX configuration capabilities while others do not. Therefore, the first cell and the second cell may correspond to the same network device or different network devices.

[0117] When the first cell and the second cell correspond to the same network device, the terminal device does not need to switch networks when switching its camped cell from the first cell to the second cell. However, when the first cell and the second cell correspond to different network devices, the terminal device needs to switch networks when switching its camped cell from the first cell to the second cell.

[0118] In summary, during the foreground processing of services on a terminal device, if a neighboring cell changes, the terminal device can select a suitable cell for handover based on the service type of the foreground service and the support of the CDRX configuration capabilities of the primary and neighboring cells. This method allows for flexible cell switching while considering both the power consumption of the terminal device and the latency requirements of different services.

[0119] Furthermore, in some other embodiments, since the non-real-time services of the terminal device are usually more numerous than the real-time services, when the terminal device is not running communication services in the foreground, or when the terminal device has not established an RRC connection with the network device, or when the terminal device is in the RRC idle state, after the neighboring cells of the terminal device change, the terminal device can also select a second cell that supports CDRX configuration capability from the neighboring cells to camp in advance, in order to prepare for subsequent processing of non-real-time services and save the power consumption of the terminal device.

[0120] (ii) The business types of the front-end services of the terminal equipment have changed.

[0121] Figure 7 This is a schematic flowchart illustrating a cell handover method provided in another embodiment of this application, involving the process of a terminal device switching cells according to the changed service type of the foreground service after a change in the service type of the foreground service. Specifically, it includes the following:

[0122] S701, the terminal device is stationed in the first cell, and the front-end service is switched from the first service to the second service. The service types of the first service and the second service are different.

[0123] The terminal device switches its front-end services from the first service to the second service, including:

[0124] Scenario 1: The foreground service of the terminal device switches from a real-time service to a non-real-time service. In other words, the first service is a real-time service, and the second service is a non-real-time service. For example, the foreground service of the terminal device switches from a game service to an SMS service, or from a live streaming service to a web browsing service, etc.

[0125] Scenario 2: The terminal device's foreground service switches from a non-real-time service to a real-time service. In other words, the first service is non-real-time, and the second service is real-time. For example, the terminal device switches from web browsing to live video streaming, or from SMS to video calling.

[0126] Scenario 3: The terminal device switches from a no-service state (referring to cellular communication services) to handling non-real-time services. In other words, the first service is empty, and the second service is a non-real-time service. For example, the terminal device switches to displaying a webpage based on user instructions while in sleep mode or displaying the main screen interface.

[0127] Scenario 4: The terminal device switches from a no-service state (referring to cellular communication services) to handling real-time services. In other words, the first service is empty, and the second service is real-time. For example, the terminal device receives a video call while in sleep mode or displaying the main screen interface.

[0128] S702, the terminal device determines the second cell from the neighboring cells of the first cell based on the service type of the second service and the support of the first cell for CDRX configuration capabilities.

[0129] For scenario 1: The first service is a real-time service, and the second service is a non-real-time service.

[0130] When a terminal device switches its foreground service from real-time to non-real-time, the latency requirements of the foreground service decrease. From the perspective of saving device power consumption, the terminal device can choose to intermittently receive data sent by the network device in CDRX mode, thereby saving device power. For this purpose, the terminal device can choose to camp on a second cell that supports CDRX configuration capabilities.

[0131] In one possible implementation, after the terminal device detects that the foreground service has switched from a real-time service to a non-real-time service, it can first determine whether the first cell supports CDRX configuration capability, and then determine whether to identify a second cell in the neighboring cells.

[0132] If the first cell supports CDRX configuration capability, it means that when the terminal device is camped on that first cell, it is in CDRX mode, intermittently receiving downlink data from the network device. During data reception, the terminal device typically consumes relatively low power. Therefore, the terminal device does not need to select other cells supporting CDRX configuration capability from the neighboring cells of the first cell; that is, the terminal device does not need to determine a second cell supporting CDRX configuration capability from among the neighboring cells.

[0133] Optionally, if the first cell supports CDRX configuration capability, the terminal device can also determine whether the CDRX period of the first cell is greater than the latency requirement of the second service. If the CDRX period of the first cell is less than or equal to the latency requirement of the second service, the second cell will not be reselected from the neighboring cells. If the CDRX period of the first cell is greater than the latency requirement of the second service, a second cell that supports CDRX configuration capability and has a CDRX period less than the latency requirement of the second service will be selected from the neighboring cells.

[0134] If the first cell where the terminal device is camped does not support CDRX configuration capability, the terminal device will typically continuously receive downlink data from the network device in CCRX mode, which usually results in high power consumption during reception. To save power consumption, a neighboring cell that supports CDRX configuration capability (i.e., the second cell) can be selected from the neighboring cells of the first cell. This allows the terminal device to receive data from the network device in CDRX mode, meeting the latency requirements of non-real-time services while reducing power consumption.

[0135] Optionally, in the above embodiments, when the foreground service (i.e., the second service) is a non-real-time service, the terminal device can select the second cell from the neighboring cells of the first cell based on the CDRX cycle of each neighboring cell of the first cell when selecting the second cell. See the relevant description in S502 for details; this embodiment will not repeat them here.

[0136] For scenario 2: The first service is a non-real-time service, and the second service is a real-time service.

[0137] When a terminal device switches its foreground service from non-real-time to real-time, the latency requirements of the foreground service increase. From the perspective of prioritizing the latency requirements of the foreground service and ensuring its normal operation, the terminal device can choose to continuously receive data from the network device in CCRX mode. Therefore, the terminal device can choose to camp on a cell that does not support CDRX configuration capabilities.

[0138] In one possible implementation, after the terminal device detects that the foreground service has switched from a non-real-time service to a real-time service, it can first determine whether the first cell supports CDRX configuration capability, and then determine whether to identify a second cell in the neighboring cells.

[0139] If the first cell supports CDRX configuration capability, it means that when the terminal device is camped on this first cell, it is in CDRX mode, intermittently receiving downlink data from the network device. During data reception, the terminal device typically experiences significant latency. However, since the currently running second service is a real-time service, high latency can lead to service interruptions and a poor user experience. To reduce the terminal device's latency, the terminal device can select a neighboring cell (i.e., the second cell) from the neighboring cells of the first cell that does not support CDRX configuration capability, allowing the terminal device to receive data from the network device in CCRX mode.

[0140] If the first cell does not support CDRX configuration capability, it means that when the terminal device is camped on the first cell, it is in CCRX mode and continuously receives downlink data sent by the network device. The data reception latency is usually small and can meet the latency requirements of real-time services. Therefore, the terminal device does not need to select a neighboring cell (i.e., the second cell) that does not support CDRX configuration capability from the neighboring cells of the first cell.

[0141] It should be noted that when the foreground service is a real-time service, the second cell selected by the terminal device does not support CDRX configuration function. In other words, the second cell does not have CDRX cycle.

[0142] For scenario 3: the first service is empty, and the second service is a non-real-time service. The terminal device can refer to the cell selection method for scenario 1. If the first cell does not support CDRX configuration capability, it can select a neighboring cell that does support CDRX configuration capability to camp on, so as to receive downlink data from the network device in CDRX mode, thus meeting service latency requirements while saving device power consumption. If the first cell supports CDRX configuration capability, no cell selection or handover is performed to maintain the current power consumption of the terminal device.

[0143] For scenario 4: the first service is empty, and the second service is a real-time service. The terminal device can refer to the cell selection method for scenario 2. If the first cell supports CDRX configuration capabilities, it can select a neighboring cell that does not support CDRX configuration capabilities to camp on, so as to receive downlink data from the network device in CCRX mode to meet the service latency requirements. If the first cell does not support CDRX configuration capabilities, no cell selection or handover will be performed to maintain the current latency of the terminal device without increasing it.

[0144] S703, the terminal device switches the cell it is camped on from the first cell to the second cell.

[0145] For details regarding S703, please refer to the relevant description of S503. The embodiments in this application will not be repeated here.

[0146] In summary, when the service type of a terminal device's foreground service changes, the terminal device can select a suitable cell from the primary and neighboring cells for handover based on the current service type and the support of the primary and neighboring cells for CDRX configuration capabilities. This method allows for flexible cell switching while considering both the terminal device's power consumption and the latency requirements of different services.

[0147] The following examples illustrate the process of a terminal device selecting a second cell from neighboring cells, for two scenarios: when the second cell supports CDRX configuration capabilities and when the second cell does not support CDRX configuration capabilities.

[0148] (1) The second cell supports CDRX configuration capability

[0149] When the second cell supports CDRX configuration capability, the terminal device can consider at least one of the parameters of neighboring cells, such as RSRP, SINR, and CDRX period, when determining the second cell. That is, the terminal device can comprehensively determine the second cell from neighboring cells based on at least one of power selection criteria, signal-to-noise ratio selection criteria, and period selection criteria. For example, the terminal device can comprehensively determine the second cell from neighboring cells based solely on the period selection criteria. Alternatively, it can comprehensively determine the second cell from neighboring cells based on power selection criteria, signal-to-noise ratio selection criteria, and period selection criteria simultaneously.

[0150] When a terminal device comprehensively determines a second cell from neighboring cells based on multiple filtering conditions, this embodiment does not restrict the order in which these filtering conditions are executed. For example, when the terminal device simultaneously determines a second cell from neighboring cells based on three filtering conditions—power filtering condition, signal-to-noise ratio filtering condition, and periodic filtering condition—see [reference needed]. Figure 8 As shown, the terminal device can determine the second cell from neighboring cells by sequentially using power selection criteria, signal-to-noise ratio selection criteria, and periodic selection criteria. Alternatively, the terminal device can also determine the second cell from neighboring cells by sequentially using signal-to-noise ratio selection criteria, power selection criteria, and periodic selection criteria.

[0151] Figure 8 This is a schematic diagram illustrating the process of determining a second cell according to an embodiment of this application, involving the process by which a terminal device determines a second cell that supports CDRX configuration capabilities. Specifically, it includes the following:

[0152] S801, the terminal device determines the RSRP of all neighboring cells.

[0153] S802, the terminal device adds cells that meet the power screening conditions of RSRP to the candidate set S.

[0154] In some embodiments, RSRP satisfying the power screening condition includes satisfying a first power screening condition, which is that RSRP is greater than or equal to an RSRP threshold. For example, the RSRP threshold can be -95 dBm (decibels per milliwatt), -100 dBm, etc., and this embodiment does not limit this.

[0155] In other embodiments, RSRP satisfying the power screening condition includes satisfying a second power screening condition, which is: |RSRP servingcell -RSRP(i)|<δ th Among them, RSRP servingcellδ represents the reference signal received power of the first cell of the terminal equipment, RSRP(i) represents the reference signal received power of the neighboring cells, and δ th A threshold is used to measure the difference in received power as a reference signal. Since the first cell where the terminal equipment camps is usually the cell with the higher RSRP, the RSRP meeting the second power screening condition indicates that the RSRP is higher than the RSRP of the previous cell. servingcell The size is comparable, sufficient to maintain the normal operation of the current services of the terminal equipment. For example, when the RSRP(1) of the neighboring cell CI1 satisfies |RSRP servingcell -RSRP(1)|<δ th When, explain RSRP(1) and RSRP servingcell With a comparable size, CI1 can maintain the normal operation of front-end services on terminal devices.

[0156] It should be understood that after filtering by power selection criteria, the reference signal reception strength of all neighboring cells in the candidate set S meets the standard, and these candidate neighboring cells can ensure that the terminal equipment can process services normally after cell handover.

[0157] After executing S801 to S802, if the candidate set S is empty, meaning there are no cells with acceptable reference signal reception strength, the determination of the second cell fails. If the candidate set S is not empty, meaning there are cells with acceptable reference signal reception strength, the terminal device executes subsequent steps S803 to S804.

[0158] S803, the terminal device obtains the SINR of all neighboring cells in the candidate set S.

[0159] S804, the terminal device deletes cells in the candidate set S that do not meet the signal-to-noise ratio screening criteria and updates the candidate set S.

[0160] For example, the signal-to-noise ratio (SNR) screening condition could be SINR(i) > δ. op Where SINR(i) is the signal-to-noise ratio of each neighboring cell in the candidate set S, δ op This represents the signal-to-noise ratio (SNR) threshold. If the SINR of a neighboring cell meets the SNR screening criteria, it indicates that the data transmission quality of that neighboring cell is good and the noise during transmission is low.

[0161] Alternatively, the signal-to-noise ratio (SNR) filtering condition could be: |SINR servingcell -SINR(i)|<δ SINR Among them, SINR servingcell SINR(i) is the signal-to-noise ratio of the first cell of the terminal device, SINR(i) is the signal-to-noise ratio of the neighboring cells, and δ SINR This is a threshold for measuring the difference in signal-to-noise ratio (SNR). Since the first cell where the terminal device camps is usually a cell with a higher SNR, if the SNR meets this screening condition, it means that the SINR is different from the SINR. servingcellThe size is comparable, sufficient to maintain the normal operation of the terminal device's foreground services. For example, when the SINR(1) of the neighboring cell CI1 satisfies |SINR servingcell -SINR(1)|<δ SINR When, explain SINR(1) and SINR servingcell With a comparable size, CI1 is able to maintain the normal operation of the terminal device's current services.

[0162] After the terminal device completes steps S803 to S804, if the candidate set S is empty (i.e., there is no cell with a signal-to-noise ratio that meets the standard), the determination of the second cell fails. If the candidate set S is not empty (i.e., there is a cell with a signal-to-noise ratio that meets the standard), then the subsequent steps S805 to S806 are executed.

[0163] S805, the terminal device obtains the CDRX cycle of each cell in the updated candidate set S.

[0164] S806, the terminal device will identify a cell in the updated candidate set S that meets the periodic screening conditions as the second cell.

[0165] In some embodiments, the periodic filtering condition is a first periodic filtering condition, which specifically states that the CDRX period is less than a time threshold. By using the first periodic filtering condition, cells with long dormancy periods can be filtered out, preventing excessive latency from affecting normal service operation. If multiple cells in the device set S meet the first periodic filtering condition, the terminal device can designate any one of these cells as the second cell, or it can designate the cell with the longest CDRX period among all cells meeting the first periodic filtering condition as the second cell.

[0166] In other embodiments, the periodic filtering condition is a second periodic filtering condition, which is: the CDRX period is the maximum value in T(i), where T(i) is the CDRX period of each cell in the updated candidate set S. That is, the terminal device determines the cell with the largest CDRX period in the updated candidate set S as the second cell. The method provided by the embodiments of this application can maximize the saving of power consumption of the terminal device and extend the usage time of the terminal device (e.g., a phone watch, a smartwatch).

[0167] In some embodiments, the period selection condition is a third period selection condition, which is: the CDRX period is the minimum value in T(i), where T(i) is the CDRX period of each cell in the updated candidate set S. That is, the terminal device determines the cell with the smallest CDRX period in the updated candidate set S as the second cell. The method provided by this application embodiment can update service data in a timely manner while relatively saving power consumption.

[0168] In some other embodiments, the period selection condition is a fourth period selection condition, which is to satisfy the correspondence between the service latency requirements and the CDRX period.

[0169] Optionally, when the front-end service is a non-real-time service, since the latency requirements of non-real-time services are not high, from the perspective of saving equipment power consumption, the terminal device can select the first cell that meets the periodic filtering conditions from the updated candidate set S based on the long CDRX period in the CDRX cycle. That is, in the above periodic filtering conditions, the CDRX cycle refers to the long CDRX period.

[0170] When the foreground service is a non-real-time service, and all neighboring cells of the first cell also support CDRX configuration, the terminal device can determine the second cell from these neighboring cells by selecting the cell with the longest CDRX long period from the updated candidate set S. If there are multiple cells with the longest CDRX long period, for example, if the updated candidate set S has three cells with a CDRX long period of 500ms, and 500ms is the longest CDRX long period in the updated candidate set S, then the terminal device can select the cell with the shortest CDRX short period from these multiple cells with the longest CDRX long periods as the second cell.

[0171] (2) The second cell does not support CDRX configuration capability

[0172] When the second cell does not support CDRX configuration capability, the terminal device can determine the second cell from neighboring cells based on at least one of power selection criteria and signal-to-noise ratio (SNR) selection criteria during the cell determination process. For example, the terminal device can determine the second cell from neighboring cells based solely on power selection criteria. Alternatively, it can determine the second cell from neighboring cells based solely on SNR selection criteria. Or, it can determine the second cell from neighboring cells based on both power selection criteria and SNR selection criteria simultaneously.

[0173] When the terminal device simultaneously determines the second cell from neighboring cells based on both power selection criteria and signal-to-noise ratio selection criteria, this embodiment does not restrict the order in which these two selection criteria are executed. For example, see... Figure 9 As shown, the terminal device can determine the second cell from the neighboring cells by sequentially using power screening conditions and signal-to-noise ratio screening conditions.

[0174] Figure 9 This is a schematic diagram illustrating the process of determining a second cell according to another embodiment of this application, involving the process by which a terminal device determines a second cell that does not support CDRX configuration capabilities. Specifically, it includes the following:

[0175] S901, the terminal device obtains the RSRPs of all neighboring cells of the first cell.

[0176] S902, the terminal equipment adds cells that meet the power screening conditions of RSRP to the candidate set S.

[0177] In this embodiment, please refer to the relevant descriptions of S801 to S802 for the specific contents of S901 to S902, and they will not be repeated here.

[0178] After the terminal device completes steps S901 to S902, if the candidate set S is empty (i.e., there is no cell with the required reference signal reception power), the determination of the second cell fails. If the candidate set S is not empty (i.e., there is a cell with the required reference signal reception power), then the subsequent steps S903 to S904 are executed.

[0179] S903, the terminal device obtains the SINR of all neighboring cells in the candidate set S.

[0180] S904, the terminal device will select one cell from the candidate set S that meets the signal-to-noise ratio screening condition as the second cell.

[0181] In some embodiments, the signal-to-noise ratio (SNR) screening condition can be SINR(i) > δ. op Where SINR(i) is the signal-to-noise ratio of each neighboring cell in the candidate set S, δ op This represents the signal-to-noise ratio (SNR) threshold. If the SINR of a neighboring cell meets the SNR screening criteria, it indicates that the data transmission quality of the neighboring cell is good and the noise during transmission is low.

[0182] In some embodiments, the terminal device may determine the cell with the highest signal-to-noise ratio in the candidate set S as the second cell to ensure the quality of data transmission.

[0183] It is worth noting that the cell handover method provided in this application is applicable to scenarios where the terminal device has one subscriber identification module (SIM) card installed, and also applicable to scenarios where the terminal device has multiple subscriber identification module (SIM) cards installed.

[0184] When a terminal device has only one SIM card installed, both the first cell the terminal device is currently using and the second cell it is about to switch to belong to the same operator. Therefore, the terminal device does not need to switch operators when switching its cell from the first cell to the second cell.

[0185] When a terminal device has multiple SIM cards from different operators installed, it will simultaneously reside on multiple different primary cells. For example, if a terminal device has a first SIM card from operator A and a second SIM card from operator B installed, it will simultaneously reside on cell A of operator A and cell B of operator B. In this scenario, the first cell the terminal device resides on refers to the cell (e.g., cell A) used when processing foreground services. The neighboring cells of the first cell can include those within operator A's network, those within operator B's network, and cell B itself. Therefore, the second cell identified by the terminal device may belong to the same operator as the first cell, or it may belong to a different operator.

[0186] When the first and second cells belong to different operators, the second cell identified by the terminal device could be the primary cell where another SIM card is registered, or it could be a neighboring cell of that primary cell. See below for details.

[0187] When the second cell is the primary cell where the terminal device is hosted (e.g., cell B), the terminal device can switch SIM cards locally when switching from the first cell (e.g., cell A) to the second cell (e.g., cell B). For example, switching from the first SIM card corresponding to cell A to the second SIM card corresponding to cell B.

[0188] When the second cell is not the primary cell where the terminal device is camped, the terminal device needs to perform cell handover between different operators when switching from the first cell to the second cell.

[0189] During the handover process, the terminal device must first switch SIM cards. Taking the first cell corresponding to the first SIM card and the second cell corresponding to the second SIM card as an example, when the terminal device switches from the first cell to the second cell, it needs to switch the SIM card used by the foreground service from the first SIM card to the second SIM card. Subsequently, it accesses the second cell based on whether the second SIM card is in RRC idle mode or RRC connected mode. The details are as follows.

[0190] When the second SIM card is in RRC idle state, the relevant communication protocol stipulates that after the terminal device searches for multiple cells, it will default to connecting to the cell with the highest RSRP. Therefore, after determining that the target cell is the second cell, the terminal device can modify the RSRP of the remaining cells to be lower than that of the second cell. Thus, for this terminal device, the second cell is nominally the cell with the highest RSRP, and the terminal device can switch to the second cell according to the existing communication protocol.

[0191] When the second SIM card is in RRC connected state, the terminal device can modify the RSRP of all cells found except the second cell to a value lower than the RSRP of the second cell. Then, it reports the RSRP of the second cell and the modified RSRPs of the other cells to the network device. Upon receiving these RSRPs, the network device instructs the terminal device to connect to the cell with the highest RSRP (i.e., the second cell), thus enabling the terminal device to switch from the first cell to the second cell in RRC connected state.

[0192] It should be understood that the sequence number of each step in the above embodiments does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0193] Based on the cell handover methods provided in the above embodiments, this embodiment also provides the following content.

[0194] This application also provides a cell selection device, which is applied to a terminal device that accesses a first cell. The device includes a detection module, a determination module, and a handover module.

[0195] The determination module is used to determine the second cell from the neighboring cells of the first cell based on the service type of the front-end service of the terminal device and the support of the first cell for CDRX configuration capabilities; wherein, the service type includes real-time services and non-real-time services.

[0196] The switching module is used to switch the cell accessed by the terminal device from the first cell to the second cell.

[0197] Optionally, the device may also include a detection module for detecting the first triggering event.

[0198] The determination module is used to determine the second cell from the neighboring cells of the first cell based on the service type of the front-end service of the terminal device and the support of the first cell for CDRX configuration capability. Specifically, it is used to determine the second cell from the neighboring cells of the first cell after the detection module detects the first trigger event, based on the service type of the front-end service of the terminal device and the support of the first cell for CDRX configuration capability.

[0199] Optionally, the first triggering event is: during the process of processing foreground services, the terminal device detects a change in the neighboring cells of the first cell; or, the foreground of the terminal device switches from a state without services to processing foreground services; or, the foreground of the terminal device switches from processing the first service to processing the second service, where the service types of the first service and the second service are different.

[0200] Optionally, a determining module is used, after the occurrence of the first triggering event, to determine the second cell from the neighboring cells of the first cell based on the service type of the terminal device's foreground service and the support of the first cell for CDRX configuration capabilities, specifically including:

[0201] The determination module is used to determine the second cell from the neighboring cells of the first cell when the service type of the front-end service is real-time service and the first cell supports CDRX configuration capability. The second cell does not support CDRX configuration capability.

[0202] Alternatively, a determination module is used to determine a second cell from the neighboring cells of the first cell, where the service type of the foreground service is real-time service and both the first cell and its neighboring cells support CDRX configuration capability. The CDRX cycle of the second cell is shorter than that of the first cell.

[0203] Alternatively, a determination module can be used to determine a second cell from the neighboring cells of the first cell when the foreground service is a non-real-time service and the first cell does not support CDRX configuration capability. The second cell supports CDRX configuration capability.

[0204] Alternatively, a determination module is used to determine a second cell from the neighboring cells of the first cell when the service type of the foreground service of the terminal device is a non-real-time service, the first cell supports CDRX configuration capability, the second cell supports CDRX configuration capability, and the CDRX cycle of the second cell is greater than that of the first cell.

[0205] Optionally, a determining module is used to determine a second cell from the neighboring cells of the first cell, wherein the second cell does not support CDRX configuration capability, including: a determining module, used to determine a second cell from the neighboring cells of the first cell, wherein the second cell does not support CDRX configuration capability, and satisfies power screening conditions and / or signal-to-noise ratio screening conditions.

[0206] Optionally, a determining module is used to determine a second cell from the neighboring cells of the first cell. The second cell supports CDRX configuration capability. The determining module is used to determine a second cell from the neighboring cells of the first cell. The second cell supports CDRX configuration capability and satisfies at least one of periodic screening conditions, power screening conditions, and signal-to-noise ratio screening conditions.

[0207] Optionally, the power screening condition is: |RSRP servingcell -RSRP(i)|<δ th Among them, RSRP servingcell Let δ be the reference signal received power of the first cell, RSRP(i) be the reference signal received power of the i-th neighboring cell of the first cell, and δ be the reference signal received power of the first cell. thA threshold is used to measure the difference in received power of the reference signal. Alternatively, the power screening criterion is: RSRP(i) is greater than or equal to the received power threshold of the reference signal.

[0208] Optionally, the signal-to-noise ratio (SNR) selection criterion is: SINR(i) > δ op Where SINR(i) is the signal-to-noise ratio of the i-th neighboring cell of the first cell, δ op This is the signal-to-noise ratio (SNR) threshold. Alternatively, the SNR filtering condition is: |SINR servingcell -SINR(i)|<δ SINR Among them, SINR servingcell δ represents the signal-to-noise ratio of the first cell. SINR The threshold is used to measure the difference in signal-to-noise ratio.

[0209] By using this signal-to-noise ratio (SNR) filtering condition, the terminal device can determine a second cell with a better SNR to ensure the communication quality after the terminal device switches from the first cell to the second cell.

[0210] Optionally, the periodic filtering condition is: the CDRX period is less than a time threshold; or, the CDRX period is the maximum value among the CDRX periods of the candidate cells, which includes neighboring cells that meet the power filtering condition and / or signal-to-noise ratio filtering condition; or, the periodic filtering condition is: the CDRX period is the minimum value among the CDRX periods of the candidate cells; or, the condition satisfies the correspondence between the latency requirements of the front-end services and the CDRX period.

[0211] Optionally, in the above period selection criteria, the CDRX period is the CDRX long period.

[0212] This application also provides a terminal device configured to perform the cell handover methods shown in the above embodiments.

[0213] Figure 10This is a schematic diagram of the structure of a terminal device provided in an embodiment of this application. The terminal device may include a processor 210, an external memory interface 220, an internal memory 221, a universal serial bus (USB) interface 230, a charging management module 240, a power management module 241, a battery 242, an antenna 1, an antenna 2, a mobile communication module 250, a wireless communication module 260, an audio module 270, a speaker 270A, a receiver 270B, a microphone 270C, a headphone jack 270D, a sensor module 280, buttons 290, a motor 291, an indicator 292, a camera 293, a display screen 294, and a SIM card interface 295, etc. The sensor module 280 may include a pressure sensor 280A, a gyroscope sensor 280B, a barometric pressure sensor 280C, a magnetic sensor 280D, an accelerometer sensor 280E, a distance sensor 280F, a proximity sensor 280G, a fingerprint sensor 280H, a temperature sensor 280J, a touch sensor 280K, an ambient light sensor 280L, a bone conduction sensor 280M, etc.

[0214] It is understood that the structures illustrated in the embodiments of this application do not constitute a specific limitation on the terminal device. In other embodiments of this application, the terminal device 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.

[0215] For example, when the terminal device is a tablet computer, it may include all the components shown in the diagram, or it may include only some of the components shown in the diagram. For example, when the terminal device is a large-screen device, it may include all the components shown in the diagram, or it may include only some of the components shown in the diagram.

[0216] When the terminal device is a mobile phone, it may include the processor 210 shown in the figure, external memory interface 220, internal memory 221, universal serial bus (USB) interface 230, charging management module 240, power management module 241, wireless communication module 260, audio module 270, speaker 270A, receiver 270B, microphone 270C, camera 293, and display screen 294.

[0217] Processor 210 may include one or more processing units, such as application processor (AP), modem processor, graphics processing unit (GPU), image signal processor (ISP), controller, memory, video codec, digital signal processor (DSP), baseband processor, and / or neural network processing unit (NPU). Different processing units may be independent devices or integrated into one or more processors.

[0218] The controller can serve as the nerve center and command center of the terminal device. Based on the instruction opcode and timing signals, the controller generates operation control signals to control the fetching and execution of instructions.

[0219] 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 retrieve it directly from the memory. This avoids repeated accesses, reduces the waiting time of the processor 210, and thus improves the efficiency of the system.

[0220] In some embodiments, the processor 210 may include one or more interfaces. Interfaces may include an inter-integrated circuit (I2C) interface, an inter-integrated circuit sound (I2S) interface, a pulse code modulation (PCM) interface, a universal asynchronous receiver / transmitter (UART) interface, a mobile industry processor interface (MIPI), a general-purpose input / output (GPIO) interface, a subscriber identity module (SIM) interface, and / or a universal serial bus (USB) interface, etc.

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

[0222] The charging management module 240 receives charging input from a charger. The charger can be a wireless charger or a wired charger. In some wired charging embodiments, the charging management module 240 receives charging input from the wired charger via a USB interface 230. In some wireless charging embodiments, the charging management module 240 receives wireless charging input via the wireless charging coil of the terminal device. While charging the battery 242, the charging management module 240 can also supply power to the terminal device via the power management module 241.

[0223] The power management module 241 connects the battery 242, the charging management module 240, and the processor 210. The power management module 241 receives input from the battery 242 and / or the charging management module 240, providing power to the processor 210, internal memory 221, external memory, display 294, camera 293, and wireless communication module 260, etc. The power management module 241 can also monitor parameters such as battery capacity, battery cycle count, and battery health status (leakage current, impedance).

[0224] In some other embodiments, the power management module 241 may also be located within the processor 210. In other embodiments, the power management module 241 and the charging management module 240 may also be located in the same device.

[0225] The wireless communication function of the terminal device can be implemented through antenna 1, antenna 2, mobile communication module 250, wireless communication module 260, modem processor, and baseband processor.

[0226] Antenna 1 and antenna 2 are used to transmit and receive electromagnetic wave signals. Each antenna in the terminal device can be used to cover one or more communication frequency bands. Different antennas can also be reused to improve antenna utilization. For example, antenna 1 can be reused as a diversity antenna for a wireless local area network. In some other embodiments, the antennas can be used in conjunction with a tuning switch.

[0227] The mobile communication module 250 can provide solutions for wireless communication applications including 2G / 3G / 4G / 5G on terminal devices. The mobile communication module 250 may include at least one filter, switch, power amplifier, low noise amplifier (LNA), etc. The mobile communication module 250 can receive electromagnetic waves via antenna 1, and perform filtering, amplification, and other processing on the received electromagnetic waves before transmitting them to a modem processor for demodulation. The mobile communication module 250 can also amplify the signal modulated by the modem processor and convert it into electromagnetic waves for radiation via antenna 1.

[0228] In some embodiments, at least some functional modules of the mobile communication module 250 may be disposed in the processor 210. In some embodiments, at least some functional modules of the mobile communication module 250 and at least some modules of the processor 210 may be disposed in the same device.

[0229] The modem processor may include a modulator and a demodulator. The modulator modulates the low-frequency baseband signal to be transmitted into a mid-to-high frequency signal. The demodulator demodulates the received electromagnetic wave signal into a low-frequency baseband signal. The demodulator then transmits the demodulated low-frequency baseband signal to the baseband processor for processing. After processing by the baseband processor, the low-frequency baseband signal is transmitted to the application processor. The application processor outputs sound signals through an audio device (not limited to speaker 270A, receiver 270B, etc.) or displays images or videos through the display screen 294. In some embodiments, the modem processor may be a separate device. In other embodiments, the modem processor may be independent of the processor 210 and may be housed in the same device as the mobile communication module 250 or other functional modules.

[0230] The wireless communication module 260 can provide solutions for wireless communication applications on terminal devices, including wireless local area networks (WLANs) (such as wireless fidelity (Wi-Fi) networks), Bluetooth (BT), global navigation satellite system (GNSS), frequency modulation (FM), near field communication (NFC), and infrared (IR) technologies. The wireless communication module 260 can be one or more devices integrating at least one communication processing module. The wireless communication module 260 receives electromagnetic waves via antenna 2, performs frequency modulation and filtering of the electromagnetic wave signals, and sends the processed signal to processor 210. The wireless communication module 260 can also receive signals to be transmitted from processor 210, perform frequency modulation and amplification, and convert them into electromagnetic waves for radiation via antenna 2.

[0231] In some embodiments, antenna 1 of the terminal device is coupled to mobile communication module 250, and antenna 2 is coupled to wireless communication module 260, enabling the terminal device to communicate with networks and other devices via wireless communication technology. Wireless communication technologies may include Global System for Mobile Communications (GSM), General Packet Radio Service (GPRS), Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA), Time-Division Code Division Multiple Access (TD-SCDMA), Long Term Evolution (LTE), BT, GNSS, WLAN, NFC, FM, and / or IR technologies, etc. GNSS can include the Global Positioning System (GPS), the Global Navigation Satellite System (GLONASS), the BeiDou Navigation Satellite System (BDS), the Quasi-Zenith Satellite System (QZSS), and / or satellite-based augmentation systems (SBAS).

[0232] The terminal device implements display functions through a GPU, a display screen 294, and an application processor. The GPU is a microprocessor for image processing, connecting the display screen 294 and the application processor. The GPU performs mathematical and geometric calculations and is used for graphics rendering. The processor 210 may include one or more GPUs, which execute program instructions to generate or modify display information.

[0233] The display screen 294 is used to display images, videos, etc. For example, the teaching videos and user action video in this embodiment of the application. The display screen 294 includes a display panel. The display panel can be a liquid crystal display (LCD), an organic light-emitting diode (OLED), an active-matrix organic light-emitting diode (AMOLED), a flexible light-emitting diode (FLED), a Miniled LED, a MicroLED, a Micro-OLED, a quantum dot light-emitting diode (QLED), etc. In some embodiments, the terminal device may include one or N display screens 294, where N is a positive integer greater than 1.

[0234] Terminal devices can achieve shooting functions through ISP, camera 293, video codec, GPU, display 294 and application processor.

[0235] The external storage interface 220 can be used to connect an external storage card, such as a Micro SD card, to expand the storage capacity of the terminal device. The external storage card communicates with the processor 210 through the external storage interface 220 to perform data storage functions. For example, music, video, and other files can be saved on the external storage card.

[0236] Internal memory 221 can be used to store executable program code, including instructions. Processor 210 executes various functional applications and data processing of the terminal device by running the instructions stored in internal memory 221. Internal memory 221 may include a program storage area and a data storage area. The program storage area may store the operating system and at least one application program required for a given function (such as sound playback, image playback, etc.). The data storage area may store data created during the use of the terminal device (such as audio data, phonebook, etc.).

[0237] In addition, the internal memory 221 may include high-speed random access memory, and may also include non-volatile memory, such as at least one disk storage device, flash memory device, universal flash storage (UFS), etc.

[0238] The terminal device can implement audio functions through audio module 270, speaker 270A, receiver 270B, microphone 270C, headphone jack 270D, and application processor.

[0239] The audio module 270 is used to convert digital audio signals into analog audio signals for output, and also to convert analog audio inputs into digital audio signals. The audio module 270 can also be used for encoding and decoding audio signals. In some embodiments, the audio module 270 may be located in the processor 210, or some functional modules of the audio module 270 may be located in the processor 210.

[0240] The speaker 270A, also known as a "loudspeaker," is used to convert audio electrical signals into sound signals. Terminal devices can listen to music or hands-free calls through the speaker 270A. For example, the speaker can play the comparison analysis results provided in the embodiments of this application.

[0241] The receiver 270B, also known as the "earpiece," is used to convert audio electrical signals into sound signals. When a terminal device answers a phone call or voice message, the receiver 270B can be brought close to the user's ear to hear the voice.

[0242] Microphone 270C, also known as a "microphone" or "voice transducer," is used to convert sound signals into electrical signals. When making a phone call or sending a voice message, the user can speak by bringing their mouth close to microphone 270C, inputting the sound signal into microphone 270C. A terminal device can be equipped with at least one microphone 270C. In some embodiments, the terminal device can be equipped with two microphones 270C, which, in addition to collecting sound signals, can also perform noise reduction. In other embodiments, the terminal device can be equipped with three, four, or more microphones 270C, enabling sound signal collection, noise reduction, sound source identification, and directional recording functions, etc.

[0243] The headphone jack 270D is used to connect wired headphones. The headphone jack 270D can be a USB 230 interface or a 3.5mm Open Mobile Terminal Platform (OMTP) standard interface, a CTIA (Cellular Telecommunications Industry Association of the USA) standard interface.

[0244] Buttons 290 include a power button, volume buttons, etc. Buttons 290 can be mechanical buttons or touch-sensitive buttons. The terminal device can receive button input and generate key signal inputs related to user settings and function control of the terminal device.

[0245] Motor 291 can generate vibration alerts. Motor 291 can be used for incoming call vibration alerts or for touch vibration feedback. For example, different vibration feedback effects can be corresponding to touch operations applied to different applications (such as taking photos, playing audio, etc.). Motor 291 can also correspond to different vibration feedback effects for touch operations applied to different areas of the display screen 294. Different application scenarios (such as time reminders, receiving messages, alarm clocks, games, etc.) can also correspond to different vibration feedback effects. The touch vibration feedback effect can also be customized.

[0246] Indicator 292 can be an indicator light, which can be used to indicate charging status, power changes, messages, missed calls, notifications, etc.

[0247] The SIM card interface 295 is used to connect a SIM card. The SIM card can be inserted into or removed from the SIM card interface 295 to achieve contact and separation with the terminal device. The terminal device can support one or N SIM card interfaces, where N is a positive integer greater than 1. The SIM card interface 295 can support Nano SIM cards, Micro SIM cards, SIM cards, etc. Multiple cards can be inserted into the same SIM card interface 295 simultaneously. The multiple cards can be of the same or different types. The SIM card interface 295 is also compatible with different types of SIM cards. The SIM card interface 295 is also compatible with external memory cards. The terminal device interacts with the network through the SIM card to achieve functions such as calls and data communication. In some embodiments, the terminal device uses an eSIM, i.e., an embedded SIM card. The eSIM card can be embedded in the terminal device and cannot be separated from the terminal device.

[0248] This application also provides a chip, see [link to example]. Figure 11 As shown, the chip includes a processor and a memory, in which a computer program is stored. When the computer program is executed by the processor, it implements the cell handover methods described in the above embodiments.

[0249] This application also provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the cell handover methods provided in the above embodiments.

[0250] This application also provides a computer program product, which includes a computer program that, when run by a terminal device, enables the terminal device to implement the cell handover methods provided in the above embodiments.

[0251] It should be understood that the processor mentioned in the embodiments of this application can be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor can be a microprocessor or any conventional processor.

[0252] It should also be understood that the memory mentioned in the embodiments of this application can be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. The non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. The volatile memory can be random access memory (RAM), which is used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous linked dynamic random access memory (SLDRAM), and direct rambus RAM (DR RAM).

[0253] In the embodiments provided in this application, the division of each framework or module is only a logical functional division. In actual implementation, there may be other division methods. For example, multiple frameworks or modules may be combined or integrated into another system, or some features may be ignored or not executed.

[0254] Furthermore, the functional modules in the various embodiments of this application can be integrated into one processing module, or each module can exist physically separately, or two or more modules can be integrated into one module. The integrated modules described above can be implemented in hardware or as software functional modules.

[0255] Those skilled in the art will clearly 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.

[0256] References to "one embodiment" or "some embodiments" as described in this specification mean that one or more embodiments of this application include a specific feature, structure, or characteristic described in connection with that embodiment. Therefore, the phrases "in one embodiment," "in some embodiments," "in other embodiments," "in still other embodiments," etc., appearing in different parts of this specification do not necessarily refer to the same embodiment, but rather mean "one or more, but not all, embodiments," unless otherwise specifically emphasized. The terms "comprising," "including," "having," and variations thereof mean "including but not limited to," unless otherwise specifically emphasized.

[0257] The above-described embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of this application, and should all be included within the protection scope of this application.

Claims

1. A cell handover method, characterized in that, Applied to a terminal device, the terminal device accessing a first cell, the method includes: Based on the service type of the foreground service of the terminal device and the support of the first cell for the connected discontinuous reception CDRX configuration capability, a second cell is determined from the neighboring cells of the first cell; wherein, the service type includes real-time services and non-real-time services; The cell accessed by the terminal device is switched from the first cell to the second cell; The step of determining a second cell from the neighboring cells of the first cell based on the service type of the front-end service of the terminal device and the support of the first cell for CDRX configuration capability includes: if the service type of the front-end service is the real-time service and the first cell supports the CDRX configuration capability, then the second cell is determined from the neighboring cells of the first cell, and the second cell does not support the CDRX configuration capability.

2. The method according to claim 1, characterized in that, Based on the service type of the front-end service of the terminal device and the support of the first cell for CDRX configuration capabilities, a second cell is determined from the neighboring cells of the first cell, including: After detecting the first trigger event, the second cell is determined from the neighboring cells of the first cell based on the service type of the foreground service of the terminal device and the support of the first cell for CDRX configuration capabilities.

3. The method according to claim 2, characterized in that, The first triggering event is: During the processing of the foreground service, the terminal device detects a change in the neighboring cells of the first cell; or, The terminal device switches from a no-service state to processing the foreground service; or... The foreground of the terminal device switches from processing a first service to processing a second service, and the first service and the second service are of different types.

4. The method according to any one of claims 1 to 3, characterized in that, Based on the service type of the front-end service of the terminal device and the support of the first cell for CDRX configuration capabilities, the second cell is determined from the neighboring cells of the first cell, and the method further includes: If the service type of the front-end service is the real-time service, and both the first cell and its neighboring cells support the CDRX configuration capability, then the second cell is determined from the neighboring cells of the first cell, and the CDRX cycle of the second cell is less than that of the first cell.

5. The method according to any one of claims 1 to 3, characterized in that, Based on the service type of the front-end service of the terminal device and the support of the first cell for CDRX configuration capabilities, the second cell is determined from the neighboring cells of the first cell, and the method further includes: If the service type of the front-end service is the non-real-time service, and the first cell does not support the CDRX configuration capability, then the second cell is determined from the neighboring cells of the first cell, and the second cell supports the CDRX configuration capability.

6. The method according to any one of claims 1 to 3, characterized in that, Based on the service type of the front-end service of the terminal device and the support of the first cell for CDRX configuration capabilities, the second cell is determined from the neighboring cells of the first cell, and the method further includes: If the service type of the front-end service is the non-real-time service, and the first cell supports the CDRX configuration capability, then the second cell is determined from the neighboring cells of the first cell. The second cell supports the CDRX configuration capability, and the CDRX cycle of the second cell is greater than that of the first cell.

7. The method according to claim 1, characterized in that, The second cell is determined from the neighboring cells of the first cell, wherein the second cell does not support the CDRX configuration capability, including: The second cell is determined from the neighboring cells of the first cell. The second cell does not support the CDRX configuration capability and meets the power screening condition and / or signal-to-noise ratio screening condition.

8. The method according to claim 5, characterized in that, The second cell is determined from the neighboring cells of the first cell, and the second cell supports the CDRX configuration capability, including: The second cell is determined from the neighboring cells of the first cell. The second cell supports the CDRX configuration capability and satisfies at least one of the periodic filtering condition, power filtering condition, and signal-to-noise ratio filtering condition.

9. The method according to claim 7, characterized in that, The power screening conditions are as follows: ;in, The reference signal received power of the first cell. For the first cell i Reference signal received power of neighboring cells, A threshold is used to measure the difference in received power of the reference signal; or, The power screening condition is: It is greater than or equal to the reference signal received power threshold.

10. The method according to claim 7, characterized in that, The signal-to-noise ratio (SNR) screening criteria are as follows: ;in, For the first cell i Signal-to-noise ratio of adjacent cells The signal-to-noise ratio threshold; or, The signal-to-noise ratio (SNR) screening criteria are as follows: ;in, Let be the signal-to-noise ratio of the first cell. For the first cell i Signal-to-noise ratio of adjacent cells The threshold is used to measure the difference in signal-to-noise ratio.

11. The method according to claim 7, characterized in that, The periodic screening criteria are as follows: The CDRX period is less than the time threshold; or... The CDRX period is the maximum value among the CDRX periods of the candidate cells, and the candidate cells include neighboring cells that meet the power screening condition and / or the signal-to-noise ratio screening condition; or... The CDRX period is the minimum value among the CDRX periods of the candidate cells, and the candidate cells include neighboring cells that meet the power screening condition and / or the signal-to-noise ratio screening condition; or... The correspondence between the latency requirements of the front-end services and the CDRX cycle is satisfied.

12. The method according to claim 11, characterized in that, The CDRX period is the CDRX long period.

13. A terminal device, characterized in that, The terminal device accesses the first cell. The terminal device includes a processor and a memory. The memory stores a computer program. When the computer program is executed by the processor, it implements the cell handover method as described in any one of claims 1 to 12.

14. A chip, characterized in that, The chip includes a processor that executes a computer program stored in a memory to implement the cell handover method as described in any one of claims 1 to 12.

15. A computer-readable storage medium storing a computer program, characterized in that, When the computer program is executed by the processor, it implements the cell handover method as described in any one of claims 1 to 12.

16. A computer program product, characterized in that, The program product includes a computer program that, when run by a terminal device, causes the terminal device to implement the cell handover method as described in any one of claims 1 to 12.

Images