A communication method, a communication device and a computer readable storage medium

Abstract

This application discloses a communication method, a communication device, and a computer-readable storage medium. According to the method, a first terminal can receive a first message sent by a first network device, the first message instructing the first terminal to report mobility history information. The first terminal can also send a second message to the first network device, the second message including first information indicating the handover mechanism used by the first terminal. Through this method, the network can directly obtain the handover mechanism used by the UE, thereby adjusting the handover mechanism in a timely manner, which not only improves handover performance but also avoids resource waste.

Description

Technical Field

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

[0002] Existing 5G communication protocols include multiple handover mechanisms, each suitable for different scenarios. Without considering resource waste, configuring multiple handover mechanisms in parallel can significantly improve handover performance. However, in such scenarios, using only one handover mechanism for an extended period may waste the resources available for the remaining mechanisms.

[0003] The handover mechanism adopted by user equipment (UE) plays an important role in handover management. However, the network needs to obtain it through a relatively complex method, and some handover mechanisms are difficult to obtain. For example, some handover mechanisms are triggered directly by events, and the network cannot directly obtain the handover mechanism adopted by the UE. This will cause the network to be unable to adjust the handover mechanism in a timely manner, which will not only affect handover performance, but may also cause resource waste. Summary of the Invention

[0004] This application provides a communication method, a communication device, and a computer-readable storage medium. According to this method, based on a network-side request for mobile history information, a terminal can send a message carrying a newly added field indicating the handover mechanism previously used by the terminal to the network side. This allows the network side to directly obtain the handover mechanism used by the terminal, enabling timely adjustments to the handover mechanism. This not only improves handover performance but also avoids resource waste.

[0005] Firstly, this application provides a communication method. This method can be applied to a first terminal. The method may include: receiving a first message sent by a first network device, the first message instructing the first terminal to report mobility history information; and sending a second message to the first network device, the second message including first information, the first information indicating the handover mechanism used by the first terminal.

[0006] Through the above implementation, if the network requests mobility history information from a terminal, the terminal can send the handover mechanism it used when accessing a cell, along with other mobility history information, to the network. This allows the network to adjust the handover mechanism used by the terminal in a timely manner, or adjust the handover mechanism used by other terminals requesting access to a specific area (such as one or more cells accessed by the terminal) based on the handover mechanism used by the terminal. This not only allows each terminal to use the most suitable handover mechanism, such as using CHO in complex scenarios to meet the requirements of high reliability and accuracy, but also allows using LTM in scenarios that require fast handover (or have high latency requirements), which can complete the handover through only the underlying signaling interaction, thereby reducing handover latency. It also avoids the waste of resources caused by configuring other handover mechanisms.

[0007] In conjunction with the first aspect, in one possible implementation, the first message is used to instruct the first terminal to report MDT measurement information, which includes the aforementioned mobility history information.

[0008] Through the above implementation, the terminal can report the switching mechanism it has used to the network in the original MDT measurement scenario without setting up a separate communication mechanism for the terminal to report the switching mechanism to the network. This means that the terminal can report the switching mechanism it has used to the network without making significant modifications to the communication protocol, which is simple and effective.

[0009] In conjunction with the first aspect, in one possible implementation, the second message includes second information used to indicate the mobility history information of the first terminal, and the second information includes the first information.

[0010] Through the above implementation, the terminal can carry the handover mechanisms it has used in its mobility history information and send it to the network. In this way, whenever the network requests the terminal to report its mobility history information, the terminal can send the handover mechanisms it has used along with other mobility history information to the network. This can be achieved by leveraging the existing mobility history information reporting mechanism to further realize the reporting of the handover mechanisms used by the terminal.

[0011] In conjunction with the first aspect, in one possible implementation, the second information includes third information, which includes access information of one or more primary cells accessed by the first terminal. This access information for a primary cell includes a first field, which indicates the handover mechanism used by the first terminal when accessing that primary cell. The first information includes the first field.

[0012] Through the above implementation, based on the original communication mechanism, the terminal can add fields to existing information cells to make the information cell carry the handover type information of the terminal. For example, adding a first field to the information cell involving access information of the primary cell to report the handover mechanism used by the terminal when accessing the primary cell. In this way, the terminal can promptly send the handover mechanism used when accessing the primary cell to the network, so that the network can directly obtain the handover mechanism used by the terminal and adjust the handover mechanism used by the terminal for subsequent access to the primary cell or the handover mechanism used by terminal devices requesting access to a specific primary cell in a timely manner. This can not only improve handover performance, but also avoid resource waste.

[0013] In conjunction with the first aspect, in one possible implementation, the aforementioned one or more primary cells include a first primary cell, and the access information of the first primary cell in the third information includes fourth information. The fourth information includes access information of one or more primary and secondary cells accessed by the first terminal during its access to the first primary cell. The access information of the primary and secondary cells includes a second field, which is used to indicate the handover mechanism used by the first terminal when accessing the primary and secondary cells. The first information also includes the second field.

[0014] Through the above implementation, based on the original communication mechanism, the terminal can add fields to existing information cells to make the information cell carry the handover type information of the terminal. For example, not only can a first field be added to the information cell involving access information of the primary cell to report the handover mechanism used by the terminal when accessing the primary cell, but a second field can also be added to the information cell involving access information of primary and secondary cells to report the handover mechanism used by the terminal when accessing primary and secondary cells. In this way, the terminal can promptly send the handover mechanisms it has used when accessing more cells to the network, so that the network can adjust the handover mechanism used by the terminal in the future based on more complete historical information on handover mechanisms, or adjust the handover mechanism used by other terminals requesting access to a specific area. This not only enables the terminal to adopt a more reasonable handover mechanism and further improves handover performance, but also avoids the waste of resources caused by configuring other handover mechanisms but not using them.

[0015] In conjunction with the first aspect, in one possible implementation, the value of the first field includes one of N preset values, which correspond to N switching mechanisms, where N is an integer greater than 1.

[0016] In conjunction with the first aspect, in one possible implementation, the value of the second field includes one of N preset values, which correspond to N switching mechanisms, where N is an integer greater than 1.

[0017] Through the above implementation, the preset values ​​of the new field used to indicate the handover mechanism used by the terminal can be defined as multiple. In this way, if the terminal has used multiple handover mechanisms to access the cell, all the handover mechanisms used can be reported to the network, so that the network can more comprehensively analyze the multiple handover mechanisms used by the terminal and make adjustments accordingly.

[0018] Secondly, this application provides a communication method. This method can be applied to a first network device. The method may include: sending a first message to a first terminal, the first message instructing the first terminal to report mobility history information; and receiving a second message sent by the first terminal, the second message including first information, the first information indicating the handover mechanism used by the first terminal.

[0019] In conjunction with the second aspect, in one possible implementation, the first message is used to instruct the first terminal to report MDT measurement information, which includes the aforementioned mobility history information.

[0020] In conjunction with the second aspect, in one possible implementation, the second message includes second information used to indicate the mobility history information of the first terminal, and the second information includes the first information.

[0021] In conjunction with the second aspect, in one possible implementation, the second information includes third information, which includes access information of one or more primary cells accessed by the first terminal. The access information of the primary cell includes a first field, which indicates the handover mechanism used by the first terminal when accessing the primary cell. The first information includes the first field.

[0022] In conjunction with the second aspect, in one possible implementation, the aforementioned one or more primary cells include a first primary cell, and the access information of the first primary cell in the third information includes fourth information. The fourth information includes access information of one or more primary and secondary cells accessed by the first terminal during its access to the first primary cell. The access information of the primary and secondary cells includes a second field, which is used to indicate the handover mechanism used by the first terminal when accessing the primary and secondary cells. The first information also includes the second field.

[0023] In conjunction with the second aspect, in one possible implementation, the value of the first field includes one of N preset values, which correspond to N switching mechanisms, where N is an integer greater than 1.

[0024] In conjunction with the second aspect, in one possible implementation, the value of the second field includes one of N preset values, which correspond to N switching mechanisms, where N is an integer greater than 1.

[0025] In conjunction with the second aspect, in one possible implementation, after the first network device receives the second message sent by the first terminal, the method may further include: sending a third message to the second network device, the third message including the first information.

[0026] Thirdly, this application provides a communication method. This method can be applied to two network devices. The method may include: receiving a third message sent by a first network device, the third message including first information, the first information indicating a handover mechanism previously used by a first terminal; and sending a fourth message to either the first network device or the third network device based on the first information, the fourth message being used to adjust the handover mechanism used by the terminal device.

[0027] Through the above implementation, after the network receives handover mechanisms reported by one or more terminals, it can analyze them and adjust the handover mechanism used by a specific terminal (e.g., if only one terminal reports its handover mechanisms, the handover mechanism used by that terminal can be adjusted by analyzing these handover mechanisms) or by terminals requesting access to a specific area (e.g., if multiple terminals report their handover mechanisms, the handover mechanism used by terminals requesting access to a specific cell accessed by those multiple terminals can be adjusted by analyzing these handover mechanisms). This improves handover performance and avoids resource waste caused by terminals not using other handover mechanisms due to their configuration.

[0028] Fourthly, a communication device is provided, including a processor. The processor is coupled to a memory and can be used to execute instructions or data in the memory to implement the methods described in the first aspect or any possible implementation thereof. Optionally, the communication device further includes a memory. Optionally, the communication device further includes a communication interface, and the processor is coupled to the communication interface.

[0029] In one implementation, the communication interface may be a transceiver, or an input / output interface.

[0030] In another implementation, the communication device is a chip configured in the first terminal. When the communication device is a chip configured in the first terminal, the communication interface can be an input / output interface.

[0031] Fifthly, a communication device is provided, including a processor. The processor is coupled to a memory and can be used to execute instructions or data in the memory to implement the methods in the second aspect above or any possible implementation thereof. Optionally, the communication device further includes a memory. Optionally, the communication device further includes a communication interface, and the processor is coupled to the communication interface.

[0032] In one implementation, the communication interface may be a transceiver, or an input / output interface.

[0033] In another implementation, the communication device is a chip configured in the first network device. When the communication device is a chip configured in the first network device, the communication interface can be an input / output interface.

[0034] Sixthly, a communication device is provided, including a processor. The processor is coupled to a memory and can be used to execute instructions or data in the memory to implement the method of the third aspect described above. Optionally, the communication device further includes a memory. Optionally, the communication device further includes a communication interface, and the processor is coupled to the communication interface.

[0035] In one implementation, the communication interface may be a transceiver, or an input / output interface.

[0036] In another implementation, the communication device is a chip configured in a second network device. When the communication device is a chip configured in a second network device, the communication interface can be an input / output interface.

[0037] In a seventh aspect, a processor is provided, comprising: an input circuit, an output circuit, and a processing circuit. The processing circuit is configured to receive signals through the input circuit and transmit signals through the output circuit, causing the processor to execute a method in any possible implementation of any aspect.

[0038] In specific implementation, the processor can be one or more chips, the input circuit can be input pins, the output circuit can be output pins, and the processing circuit can be transistors, gate circuits, flip-flops, and various logic circuits. The input signal received by the input circuit can be received and input by, for example, but not limited to, a receiver, and the signal output by the output circuit can be, for example, but not limited to, output to and transmitted by a transmitter. Furthermore, the input circuit and the output circuit can be the same circuit, which is used as both the input circuit and the output circuit at different times. This application does not limit the specific implementation of the processor and various circuits.

[0039] Eighthly, a communication device is provided, including a processor and a memory. The processor is used to read instructions stored in the memory, receive signals via a receiver, and transmit signals via a transmitter to execute the method in any possible implementation of any of the preceding aspects.

[0040] Optionally, the processor may be one or more, and the memory may be one or more.

[0041] Ninthly, a computer program product is provided, the computer program product comprising: a computer program (also referred to as code or instructions), which, when the computer program is run, causes a computer to perform a method in any possible implementation of any of the above aspects.

[0042] In a tenth aspect, a computer-readable storage medium is provided that stores a computer program (also referred to as code or instructions) that, when run on a computer, causes the computer to perform the method in any possible implementation of any of the above aspects.

[0043] Eleventhly, embodiments of this application provide a chip system including one or more processors for calling and executing instructions stored in memory, causing the methods in any of the above aspects or possible implementations to be executed. The chip system may be composed of chips or may include chips and other discrete devices.

[0044] The chip system may include input circuits or interfaces for transmitting information or data, and output circuits or interfaces for receiving information or data.

[0045] In a twelfth aspect, a communication system is provided, including the aforementioned first terminal, first network device, and second network device. Optionally, the communication system may further include other devices that communicate with the first terminal and / or the first network device and / or the second network device.

[0046] The technical effects achieved in the above aspects can be referred to each other or to the beneficial effects in the method embodiments shown below, which will not be repeated here. Attached Figure Description

[0047] Figure 1 A switching diagram provided for an embodiment of this application;

[0048] Figure 2 A schematic diagram of a communication system provided in an embodiment of this application;

[0049] Figure 3 A flowchart illustrating a communication method provided in an embodiment of this application;

[0050] Figure 4 A flowchart illustrating yet another communication method provided in an embodiment of this application;

[0051] Figure 5A and Figure 5B This is yet another switching diagram provided in the embodiments of this application;

[0052] Figure 6A flowchart illustrating yet another communication method provided in an embodiment of this application;

[0053] Figure 7 This is a schematic diagram of the structure of a communication device provided in an embodiment of this application;

[0054] Figure 8 This is a schematic diagram of the structure of another communication device provided in the embodiments of this application. Detailed Implementation

[0055] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. In the description of the embodiments of this application, unless otherwise stated, " / " means "or," for example, A / B can mean A or B; the word "and / or" in the text is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, and B existing alone.

[0056] In this application, the use of singular pronouns to denote "one or more" rather than "one and only one," unless otherwise specified. Furthermore, "at least one," "one or more of the following," or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, or c can represent: a, b, c; a and b; a and c; b and c; or a and b and c. Here, a, b, and c can be single or multiple. Additionally, in the description of embodiments in this application, "multiple" means two or more.

[0057] It is understood that the terms "first," "second," etc., in the specification, claims, and drawings of this application are used to distinguish different objects, rather than to describe a specific order. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or apparatus that includes a series of steps or units is not limited to the listed steps or units, but may optionally include steps or units not listed, or may optionally include other steps or units inherent to these processes, methods, products, or apparatuses.

[0058] In the description of this application, the words "exemplary" or "for example" are used to indicate that something is an example, illustration, or illustration. Any embodiment or design that is described as "exemplary," "for example," or "for example" in this application should not be construed as being more preferred or advantageous than other embodiments or designs. Rather, the use of the words "exemplary," "for example," or "for example" is intended to present the relevant concepts in a specific manner.

[0059] It is understood that in the description of this application, "when," "under what circumstances," "if," and "if" all refer to the device performing a corresponding action under certain objective circumstances, and are not time-limited, nor do they require the device to perform a judgment action when it is implemented, nor do they imply any other limitations. Specifically, the device performing a corresponding action under certain objective circumstances includes: satisfying the objective circumstances, i.e., being able to perform the corresponding action; or satisfying both the objective circumstances and other circumstances, in order to perform the corresponding action.

[0060] In this application, the reference to "embodiment" means that a specific feature, structure, or characteristic described in connection with an embodiment may be included in at least one embodiment of this application. The appearance of this phrase in various places throughout the specification does not necessarily refer to the same embodiment, nor is it a mutually exclusive, independent, or alternative embodiment. It will be explicitly and implicitly understood by those skilled in the art that the embodiments described in this application can be combined with other embodiments.

[0061] The terms "system" and "network" in this application embodiment are often used interchangeably herein.

[0062] The terms “access” and “access” in this application embodiment are often used interchangeably herein.

[0063] In this application, "connection" refers to various connection methods, such as direct connection or indirect connection, to achieve communication between devices, and is not specifically limited thereto.

[0064] To better understand the embodiments of this application, the terminology used in the embodiments of this application will be introduced below. The following terminology is only for describing specific embodiments and is not intended to limit this application.

[0065] 1. Switch

[0066] Handover refers to the process by which a terminal device (or UE) moves from one network resource (e.g., a base station, cell, or wireless access point) to another network resource during communication.

[0067] Switching can occur in various scenarios, such as when terminal devices move, signal quality changes, network load becomes unbalanced, or user service needs change.

[0068] For example, such as Figure 1As shown, base stations a, b, and c cover locations P1, P2, and P3 respectively, and each base station contains cells C1, C2, and C3. When a terminal device is located at location P1, it camps in cell C1. When the terminal device moves from location P1 to location P2, it enters the coverage area of ​​base station b from the coverage area of ​​base station a. This can trigger a handover, for example, if the terminal device switches from cell C1 to cell C2. In this case, when the terminal device is located at location P2, it camps in cell C2. Similarly, when the terminal device moves from location P2 to location P3, it enters the coverage area of ​​base station c from the coverage area of ​​base station b. This can trigger a handover, for example, if the terminal device switches from cell C2 to cell C3. In this case, when the terminal device is located at location P3, it camps in cell C3.

[0069] 2. Switching Mechanism

[0070] (1) Traditional handover (HO)

[0071] Traditional handover mechanisms are primarily triggered by the network side, with the handover process completed based on Radio Resource Control (RRC) layer signaling. The process is as follows:

[0072] Measurement phase: The UE measures the signal quality of surrounding cells according to the measurement parameters configured in the network and reports the measurement results.

[0073] Handover decision phase: Based on measurement reports and radio resource management (RRM) information, the network decides whether to perform a handover and which target cell to hand over to.

[0074] Handover execution phase: The network sends a handover command to the UE, and the UE establishes a connection with the target cell according to the command and completes RRC reconfiguration.

[0075] (2) Dual active protocol stack (DAPS) switching

[0076] DAPS handover primarily refers to maintaining the connection between the source and target cells during the handover process until the UE successfully accesses the target cell, at which point the source cell connection is released. Its handover mechanism is as follows:

[0077] Dual protocol stack persistence: After receiving a handover command, the UE maintains a connection with both the source cell and the target cell and continues to receive downlink data from the source cell.

[0078] Data forwarding: During the handover process, the source cell forwards downlink data to the target cell. After completing random access, the UE can directly transmit uplink data in the target cell.

[0079] Handover complete: After the UE completes random access in the target cell, it sends an RRC reconfiguration complete message to the target cell and then releases the source cell connection.

[0080] The source cell refers to the cell where the UE is located before the handover process begins, and it is responsible for providing the current radio resources and services. The target cell refers to the cell that the UE will be handed to during the handover process. It is the target of the handover and is usually a cell with better signal quality or that is more suitable for the UE's current needs.

[0081] (3) Condition handover (CHO)

[0082] CHO is a pre-configured handover mechanism that allows the UE to autonomously perform a handover when preset conditions are met. Its handover mechanism is as follows:

[0083] Pre-configuration: The network configures multiple candidate target cells (e.g., CHO candidate list) and their handover conditions for the UE. After receiving the configuration, the UE begins to evaluate these conditions.

[0084] Autonomous handover: When a UE meets the handover conditions of a candidate cell, it can autonomously hand over to that cell without waiting for the network to trigger it.

[0085] Handover complete: After the UE completes the handover, it sends an RRC reconfiguration complete message to the target cell and releases the stored CHO configuration.

[0086] (4) Lower layer triggered mobility (LTM) switching

[0087] LTM is a mobility handover mechanism triggered by L1 / L2 signaling, which does not rely on traditional RRC layer signaling and aims to reduce latency, overhead, and downtime during handover. Its handover mechanism is as follows:

[0088] L1 / L2 signaling triggering and early synchronization: Before the handover, the network uses the physical downlink control channel (PDCCH) command to allow the UE to obtain the timing advance (TA) of the target cell in advance, so as to complete the uplink synchronization in advance.

[0089] Handover execution: After receiving the handover instruction, the UE quickly establishes a connection with the target cell and completes the handover process.

[0090] (5) Conditional LTM (C-LTM) switching

[0091] C-LTM is a handover mechanism that combines CHO and LTM. It combines the flexibility of CHO with the low latency of LTM, making it suitable for complex network environments. Its handover mechanism is as follows:

[0092] Pre-configuration and condition assessment: The network configures LTM candidate cells and their handover conditions for the UE, and the UE performs LTM handover autonomously when the conditions are met.

[0093] LTM handover process: During the handover process, the UE uses L1 / L2 signaling to quickly complete synchronization and connection with the target cell.

[0094] (6) L3 switching

[0095] L3 handover is a traditional handover mechanism triggered by RRC (L3) layer measurements. It is triggered and managed through RRC signaling (synchronization cell reconfiguration) and is primarily used to change the serving cell (primary or secondary cell) when the UE (User Equipment) moves. The primary cell (PCell) is the main serving cell for the UE in connected mode (RRC_CONNECTED), carrying the UE's basic connection and control information. The secondary cell (SCell) is an additional cell allocated to the UE besides the PCell, used to increase data transmission capacity or provide additional radio resources.

[0096] It is understandable that the above-mentioned HO, DAPS and CHO are handover mechanisms triggered by RRC signaling, which belong to L3 handover.

[0097] 3. Self-organizing network (SON)

[0098] SON (Self-Configuration Network) technology is an advanced network architecture designed to automate the self-configuration, self-optimization, and self-healing of wireless networks, thereby reducing manual intervention, lowering operating costs, and improving network performance and user experience. SON technology is widely used in the optimization and management of cellular networks, including Automatic Neighbor Relation (ANR), automatic configuration of Physical Cell Identifiers (PCI), coverage and capacity optimization, and load balancing. These features significantly improve the intelligence level of the network and reduce operating costs.

[0099] 4. Minimization of drive test (MDT)

[0100] MDT (Drive Testing) is a technique that optimizes network performance by utilizing UE (User Equipment) measurement data. The main purpose of MDT configuration is to reduce the resources and time required for traditional drive testing while improving the efficiency of network optimization.

[0101] (1) MDT model

[0102] There are two modes of MDT measurement: logged MDT and immediate MDT. In addition, there are some measurements that are not explicitly classified as immediate or logged MDT, such as accessibility measurements.

[0103] Logged MDT is a measurement data collection method performed when the UE is in idle state (RRC_IDLE) or inactive state (RRC_INACTIVE). The UE performs measurements in these states and saves the results in the form of log files in local memory, and then reports them to the network when it enters connected state (RRC_CONNECTED).

[0104] (2) Configuration and reporting process of MDT measurement

[0105] Measurement configuration process: The network sends the MDT measurement configuration to the UE via an RRC message (e.g., a LoggedMeasurementConfiguration message). Accordingly, the UE records measurement data in either the idle or inactive state based on this configuration.

[0106] In some embodiments of this application, the MDT measurement configuration may include measurement tasks, recording duration, geographical area restrictions, etc.

[0107] Measurement reporting process: When the UE enters the connected state, the network requests the UE to report measurement logs via a UE Information Request. Correspondingly, the UE reports the measurement logs to the network via RRC signaling, supporting segmented transmission.

[0108] The system architecture involved in the embodiments of this application will be described in detail below.

[0109] The embodiments of this application can be applied to long term evolution (LTE) systems, advanced long term evolution (LTE-A) systems, new radio (NR) systems, evolution systems of NR systems, LTE-based access to unlicensed spectrum (LTE-U) systems, NR-based access to unlicensed spectrum (NR-U) systems, non-terrestrial networks (NTN) systems, universal mobile telecommunication system (UMTS), 6th-generation (6G) communication systems, device-to-device (D2D) communication, machine-to-machine (M2M) communication, machine-type communication (MTC), vehicle-to-vehicle (V2V) communication, vehicle-to-everything (V2X) communication, narrowband internet of things (NB-IoT) communication, or other future communication systems, etc. It is understood that the embodiments of this application can also be applied to other communication systems, and this application does not limit them.

[0110] Please see Figure 2 , Figure 2 A schematic diagram of a system architecture provided by an embodiment of this application is shown as an example. Figure 2 The system architecture shown may include, but is not limited to, terminal device 101, network device 201, and network device 202. Terminal device 101 is connected to network device 201 wirelessly, and network device 201 is connected to network device 202 wirelessly or via a wired connection. Network device 201 and network device 202 may be independent physical devices, or the functions of network device 201 and network device 202 may be integrated into the same physical device, or a single physical device may integrate some of the functions of network device 201 and some of the functions of network device 202.

[0111] Optionally, network device 201 can be an access network device.

[0112] Optionally, network device 202 can be an access network device.

[0113] Optionally, network device 202 can be a core network device.

[0114] Optionally, network device 202 may include access network devices and core network devices.

[0115] Optionally, network device 202 can be a device used to implement SON.

[0116] Figure 2 The number and form of the devices are for illustrative purposes only and do not constitute a limitation on the embodiments of this application. For example, in practical applications... Figure 2 The system architecture shown can also include more terminal devices and network devices. For example, Figure 2 The system architecture shown may also include terminal device 102, network device 203, and network device 204. Network device 203 is the network device corresponding to the cell where terminal device 101 previously camped, and network device 204 is the network device corresponding to the cell where terminal device 102 currently camps. Network device 203 and network device 202 can be independent physical devices, or the functions of network device 203 and network device 202 can be integrated into the same physical device, or a single physical device can integrate some of the functions of network device 203 and some of the functions of network device 202. Similarly, network device 204 and network device 202 can be independent physical devices, or the functions of network device 204 and network device 202 can be integrated into the same physical device, or a single physical device can integrate some of the functions of network device 204 and some of the functions of network device 202.

[0117] Optionally, network device 203 can be an access network device.

[0118] Optionally, network device 204 can be an access network device.

[0119] It should be noted that, if Figure 2 The system architecture shown includes multiple terminal devices, all of which can execute the communication method provided in this application (see below for details).

[0120] It should also be noted that the embodiments of this application do not limit the form of the aforementioned devices (e.g., terminal device 101, network device 201, network device 202, network device 203, and network device 204). For example, the device for implementing the function of the terminal device can be the terminal device itself, or it can be a device that supports the terminal device in implementing that function, such as a chip, chip module, apparatus, or unit. This device can be installed in the terminal device or used in conjunction with the terminal device. Similarly, the device for implementing the function of the network device can be a network device; or it can be a device that supports the network device in implementing that function, such as a chip, chip module, apparatus, or unit. This device can be installed in the network device or used in conjunction with the network device. In the embodiments of this application, the chip system can be composed of chips, or it can include chips and other discrete devices.

[0121] certainly, Figure 2 This is merely an example of a system architecture provided in this application and does not constitute a limitation on the system architecture involved in this application.

[0122] The terminal equipment, access network, and core network involved in the embodiments of this application will be briefly introduced below.

[0123] (1) Terminal equipment: also known as user equipment (UE), user terminal, mobile station (MS), mobile terminal (MT), etc. UE can be a device that includes radio transceiver functions and can cooperate with network equipment (such as the access network equipment mentioned above) to provide communication services to users. The UE can be a handheld terminal, laptop computer, subscriber unit, cellular phone, smartphone, wireless data card, personal digital assistant (PDA) computer, tablet computer, wireless modem, handheld device, laptop computer, cordless phone, wireless local loop (WLL) station, machine type communication (MTC) terminal, wearable device (e.g., smartwatch, smart bracelet, pedometer, etc.), in-vehicle equipment (e.g., car, bicycle, electric vehicle, airplane, ship, train, high-speed rail, etc.), virtual reality (VR) device, augmented reality (AR) device, wireless terminal in industrial control, smart home device (e.g., refrigerator, television, air conditioner, electricity meter, etc.), smart robot, workshop equipment, wireless terminal in self-driving, wireless terminal in remote medical surgery, smart grid (smart) Wireless terminals in various fields, including wireless terminals in grids, transportation safety, smart cities, smart homes, flying equipment (e.g., intelligent robots, drones), 5G networks, or future communication networks, are not specifically limited to these categories in this application.

[0124] (2) Access Network: Used to implement access-related functions, it can provide network access for authorized users in a specific area and determine different quality transmission channels to transmit user data based on user level, service requirements, etc. The access network forwards control signals and user data between terminal equipment and the core network. Access network equipment can be devices that provide access for terminal equipment.

[0125] Access network equipment refers to the radio access network (RAN) nodes (or devices) that connect the UE to the wireless network; it can also be called a base station. Examples of RAN nodes include: evolved Node B (gNB), transmission reception point (TRP), evolved Node B (eNB), radio network controller (RNC), Node B (NB), base station controller (BSC), base transceiver station (BTS), home base station (e.g., home evolved Node B, or home Node B, HNB), base band unit (BBU), and wireless fidelity (Wi-Fi) access point (AP). Furthermore, in a network architecture, multiple access network devices can collaborate to assist terminal devices in achieving wireless access, with different access network devices each implementing some of the functions of a base station. For example, access network equipment can be a central unit (CU), a distributed unit (DU), a CU-control plane (CP), a CU-user plane (UP), or a radio unit (RU), etc. It should be noted that the CU (or CU-CP and CU-UP), DU, or RU may have different names in different systems, and this application does not impose specific limitations on this.

[0126] (3) Core Network: Its main functions are to provide user connections, manage users, and carry out services, serving as the bearer network and providing an interface to external networks. The establishment of user connections includes functions such as mobility management (MM), call management (CM), switching / routing, and recording notification (which, in conjunction with intelligent network services, establishes connections to intelligent network peripheral devices).

[0127] Core network equipment can be categorized as core network elements. Core network elements are physical or logical devices that constitute the core network. They work together to perform functions such as user data processing, transmission, management, and control.

[0128] It should be noted that the access network and core network involved in this application can be the access network and core network in the wireless communication system mentioned above (e.g., LTE communication system, 5G communication system, 6G communication system, etc.), and this application does not impose specific restrictions on them.

[0129] Combination Figure 2 The communication system shown below is followed by a description of a communication method provided by an embodiment of this application.

[0130] Please see Figure 3 , Figure 3 This is a flowchart illustrating a communication method provided in an embodiment of this application.

[0131] In this embodiment, the execution is performed by a first terminal, which may also be a module within the first terminal (e.g., a chip, chip system, integrated circuit, or control unit); in this embodiment, the execution is performed by a first network device, which may also be a module within the first network device (e.g., a chip, chip system, integrated circuit, or control unit); in this embodiment, the execution is performed by a second network device, which may also be a module within the second network device (e.g., a chip, chip system, integrated circuit, or control unit).

[0132] like Figure 3 As shown, the communication method may include the following steps:

[0133] S101: The first network device sends a first message to the first terminal, the first message being used to instruct the first terminal to report mobility history information.

[0134] Correspondingly, the first terminal receives the first message sent by the first network device.

[0135] For example, the first message could be a UEInformationRequest. This UEInformationRequest could include a field called mobilityHistoryReportReq set to true, indicating that the first terminal needs to report a MobilityHistoryReport.

[0136] Optionally, before sending the first message to the first terminal, the first network device may send MDT measurement configuration information to the first terminal, or the network device corresponding to the cell where the first terminal previously camped (i.e., the source cell mentioned below) may send MDT measurement configuration information to the first terminal to instruct the first terminal to perform MDT measurements. In this case, the first message may be used to instruct the first terminal to report MDT measurement information, such as an MDT report mentioned below (e.g., a Logged MDT report), which may include mobility history information.

[0137] Optionally, the first terminal can be terminal device 101, and the first network device can be network device 201.

[0138] Optionally, the first terminal can be terminal device 102, and the first network device can be network device 204.

[0139] Of course, the first terminal can also be Figure 2 Other terminal devices not shown, the first network device may also provide Figure 2 Other access network devices not shown are not limited in this application.

[0140] S102: The first terminal sends a second message to the first network device. The second message includes first information, which is used to indicate the handover mechanism used by the first terminal.

[0141] Correspondingly, the first network device receives the second message sent by the first terminal.

[0142] For example, the second message could be a UEInformationResponse. This UEInformationResponse could include the first information. That is, the first information could be carried on the UEInformationResponse.

[0143] Optionally, the second message may include MDT measurement information recorded by the first terminal, such as the MDT report mentioned below (e.g., Logged MDT report), which may include mobility history information.

[0144] Optionally, the first piece of information can be the switching type information mentioned below.

[0145] Optionally, the second message may include second information, which may be used to indicate the mobility history information of the first terminal, and the second information may include the first information.

[0146] For example, the second information could be a MobilityHistoryReport. This MobilityHistoryReport could include the first information. That is, the first information could be configured within the MobilityHistoryReport cell.

[0147] Optionally, the second information may include third information, which includes access information for one or more primary cells accessed by the first terminal. The access information for the primary cell includes a first field indicating the handover mechanism used by the first terminal when accessing the primary cell. In one possible implementation, for each of the one or more primary cells accessed by the first terminal, the access information for that primary cell may include a first field, which can be used to indicate the handover mechanism used by the first terminal when accessing the primary cell. The first information may include the first field from the access information for each primary cell.

[0148] For example, the third piece of information can be VisitedCellInfoList, and the access information of the primary cells accessed by the first terminal can be VisitedCellInfo. It is understood that if the first terminal has only accessed one primary cell, VisitedCellInfoList can contain only one VisitedCellInfo; if the first terminal has accessed multiple primary cells, VisitedCellInfoList can contain multiple VisitedCellInfos. It should be noted that if the first terminal accesses the same primary cell multiple times, VisitedCellInfoList can contain multiple VisitedCellInfos corresponding to that primary cell. Each VisitedCellInfo corresponding to that primary cell corresponds to one access of the first terminal to that primary cell, i.e., it contains information about that access (such as cell identifier, dwell time, and handover mechanism).

[0149] In one possible implementation, the order in which the access information of each main cell is arranged in the third information is the order in which the first terminal accesses each main cell.

[0150] Of course, the order in which the first terminal accesses each main cell can also be represented in other ways. For example, the third information may include records of the first terminal's access to each main cell in sequence. This application does not limit this.

[0151] Optionally, the first field can be the handoverType mentioned below.

[0152] Optionally, the value of the first field may include one of N preset values, which correspond to N switching mechanisms, where N is an integer greater than 1.

[0153] For example, the preset value can refer to a key, such as traditionalHO, dapsHO, conditionalHO, ltmHO, c-ltmHO, spare3, spare2, and spare1 in the handoverType structure mentioned below. Alternatively, the preset value can refer to an encoding value or an enumeration value, such as 0, 1, 2, 3, 4, 5, 6, and 7 in the handoverType structure mentioned below. In the underlying implementation of the protocol, the encoding value is used to convert enumeration type fields to binary format (encoding) or convert them back to enumeration type from binary format (decoding).

[0154] Of course, the name, type, and value of the first field can be other things, and this application does not restrict them.

[0155] It should be noted that if the third information includes access information of multiple primary cells accessed by the first terminal, the values ​​of the first field in the access information of these multiple primary cells may be the same or different.

[0156] For example, the third information may include access information for PCell1, PCell2, and PCell3. The first field in the access information for PCell1 indicates the handover mechanism used when the first terminal previously accessed PCell1; the first field in the access information for PCell2 indicates the handover mechanism used when the first terminal previously accessed PCell2; and the first field in the access information for PCell3 indicates the handover mechanism used when the first terminal previously accessed PCell3. If the first fields in the access information for PCell1, PCell2, and PCell3 are the same, it indicates that the first terminal has used the same handover mechanism to successively handover to these three primary cells. If the first fields in the access information for PCell1, PCell2, and PCell3 are different, it indicates that the first terminal has used different handover mechanisms to successively handover to these three primary cells.

[0157] Optionally, the one or more primary cells accessed by the first terminal may include the first primary cell. That is, the third information may include access information of the first primary cell. This access information of the first primary cell may include fourth information, which may include access information of one or more secondary and primary cells accessed by the first terminal during its access to the first primary cell. This access information of the secondary and primary cells may include a second field, which can be used to indicate the handover mechanism used by the first terminal when accessing the secondary and primary cell. In this case, the first information may include not only the first field but also the second field. In one possible implementation, for each of the one or more secondary and primary cells accessed by the first terminal during its access to the first primary cell, the access information of each secondary and primary cell may include a second field, which can be used to indicate the handover mechanism used by the first terminal when accessing the secondary and primary cell. The first information may include the second field from the access information of each secondary and primary cell.

[0158] For example, the fourth piece of information can be a VisitedPSCellInfoList. The VisitedCellInfo corresponding to the first primary cell can include VisitedPSCellInfoList, and the access information of the primary and secondary cells accessed by the first terminal during its access to the first primary cell can be VisitedPSCellInfo. It is understood that if the first terminal accesses only one primary or secondary cell during its access to the first primary cell, then the VisitedPSCellInfoList can include only one VisitedPSCellInfo; if the first terminal accesses multiple primary and secondary cells during its access to the first primary cell, then the VisitedPSCellInfoList can include multiple VisitedPSCellInfos. It should be noted that if the first terminal accesses the same primary or secondary cell multiple times during its access to the first primary cell, then the VisitedPSCellInfoList can include multiple VisitedPSCellInfos corresponding to that primary or secondary cell. Each VisitedPSCellInfo corresponding to that primary or secondary cell corresponds to one access by the first terminal to that primary or secondary cell, i.e., it includes information about that access (such as cell identifier, dwell time, and handover mechanism).

[0159] In one possible implementation, the order in which the access information of each primary and secondary cell is arranged in the fourth information is the order in which the first terminal accesses each primary and secondary cell.

[0160] Of course, the order in which the first terminal accesses each primary and secondary cell can also be represented in other ways. For example, the fourth information may include records of the first terminal's access to each primary and secondary cell in sequence. This application does not limit this.

[0161] In one possible implementation, the first terminal accesses one or more primary and secondary cells during the process of accessing the multiple primary cells. In this case, each of the multiple primary cells can include access information of the corresponding one or more primary and secondary cells. Accordingly, the first information can include not only the first field in the access information corresponding to each primary cell accessed by the first terminal, but also the second field in the access information corresponding to each primary and secondary cell accessed by the first terminal during the process of accessing the multiple primary cells.

[0162] Optionally, the second field can be the handoverType mentioned below.

[0163] Optionally, the value of the second field includes one of N preset values, which correspond to N switching mechanisms, where N is an integer greater than 1. The meaning of these preset values ​​can be understood as described above, and will not be repeated here.

[0164] Of course, the name, type, and value of the second field can be other things, and this application does not impose any restrictions on them.

[0165] It should be noted that if the fourth information includes access information of multiple primary and secondary cells accessed by the first terminal during the process of accessing the first primary cell, the value of the second field in the access information of these multiple primary and secondary cells may be the same or different.

[0166] For example, the first primary cell can be PCell1, and the first terminal accesses PSCell1 and PSCell2 sequentially during the process of accessing PCell1. Thus, the fourth information can include access information for PSCell1 and access information for PSCell2. The second field in the access information of PSCell1 indicates the handover mechanism used by the first terminal when accessing PSCell1 during the process of accessing PCell1, and the second field in the access information of PSCell2 indicates the handover mechanism used by the first terminal when accessing PSCell2 during the process of accessing PCell1. If the second fields in the access information of PSCell1 and PSCell2 are the same, it means that the first terminal used the same handover mechanism to switch to these two primary and secondary cells sequentially during the process of accessing PCell1. If the second fields in the access information of PSCell1 and PSCell2 are different, it means that the first terminal used different handover mechanisms to switch to these two primary and secondary cells sequentially during the process of accessing PCell1.

[0167] It is understandable that the first and second fields can be the same fields configured in different information elements (such as handoverType mentioned below). Although both are used to indicate the handover mechanism used by the first terminal, the first field indicates the handover mechanism used by the first terminal to access the primary cell, while the second field indicates the handover mechanism used by the first terminal to access the primary and secondary cells. The content indicated by the first field also differs in different access information; please refer to the explanation of the first field in different access information above for details. Similarly, the content indicated by the second field also differs in different access information; please refer to the explanation of the second field in different access information above for details.

[0168] S103: The first network device sends a third message to the second network device, the third message including the first information.

[0169] Correspondingly, the second network device receives the third message sent by the first network device.

[0170] For example, the third message may include an MDT report (e.g., a Logged MDT report), which may include the first information.

[0171] Optionally, in addition to the first information, the third message may also include other mobility history information, such as dwell time and cell identifier, etc. This application does not impose any restrictions on this.

[0172] Optionally, the second network device can be network device 202.

[0173] Of course, the second network device can also provide Figure 2 Other network devices not shown are not limited in this application.

[0174] S104: The second network device sends a fourth message to the first network device or the third network device based on the first information. The fourth message is used to adjust the handover mechanism adopted by the terminal device.

[0175] Correspondingly, the first network device or the third network device receives the fourth message sent by the second network device.

[0176] Optionally, the second network device may send a fourth message to the first network device based on the first information. In this case, the aforementioned terminal device may include the first terminal. That is, the fourth message can be used to adjust the handover mechanism adopted by the first terminal.

[0177] Optionally, the second network device may send a fourth message to the third network device based on the first information. In this case, the terminal device may include terminal devices requesting access to the cell corresponding to the third network device; for example, the terminal device may include all terminal devices requesting access to the cell corresponding to the third network device, but not necessarily the first terminal. That is, the fourth message can be used to adjust the handover mechanism adopted by the terminal devices requesting access to the cell corresponding to the third network device.

[0178] It is understandable that the cell corresponding to the third network device is the cell accessed by the first terminal. Optionally, the cell corresponding to the third network device can be a specific area mentioned below.

[0179] For example, the second network device can receive information from multiple network devices indicating the handover mechanisms used by the corresponding terminal devices (such as handover type information of multiple terminal devices). In this case, the second network device can analyze the information it receives and send a fourth message to network devices in a specific area (such as a third network device) to adjust the handover mechanism used by the terminal devices in that specific area.

[0180] Optionally, the third network device can be network device 203.

[0181] Of course, third-party network devices can also provide Figure 2 Other access network devices not shown are not limited in this application.

[0182] In some embodiments of this application, steps S103 and S104 are optional steps.

[0183] above Figure 3 The method embodiments shown include many possible implementation schemes, such as adjusting the switching mechanism used by the first terminal, or adjusting the switching mechanism used by terminal devices in specific areas accessed by the first terminal. The following will combine... Figure 4 and Figure 6 Examples of some of the implementation schemes are provided.

[0184] It should be noted that, Figure 4 and Figure 6 For any unexplained related concepts, operations, or logical relationships, please refer to [link / reference]. Figure 3 The corresponding description in the illustrated embodiment.

[0185] In this application, Figure 4 and Figure 6 The illustrated embodiment can be considered as a standalone embodiment. Figure 4 and Figure 6 The embodiments shown can all be implemented without relying on Figure 3 The technical solution; Figure 4 and Figure 6 Some of the steps in the illustrated embodiments can also be used as separate embodiments.

[0186] In this application, Figure 4 and Figure 6 The illustrated embodiments can be combined into a single embodiment.

[0187] Please see Figure 4 , Figure 4 This is a flowchart of another communication method provided in the embodiments of this application. The embodiments of this application exemplify the following: a first terminal is terminal device 101, a first network device is network device 201, a second network device is network device 202, a first message is UEInformationRequest, a second message is UEInformationResponse, a third message includes handover type information, and a fourth message is message A1.

[0188] like Figure 4 As shown, the method may include the following steps:

[0189] S201: Network device 201 sends MDT measurement configuration information to terminal device 101. Correspondingly, terminal device 101 receives the MDT measurement configuration information sent by network device 201. The MDT measurement configuration information is used to instruct terminal device 101 to perform MDT measurements.

[0190] Optionally, network device 201 can be the network device corresponding to the cell where terminal device 101 is currently camped, such as the base station to which the cell where terminal device 101 is currently camped belongs.

[0191] Optionally, network device 201 may periodically send MDT measurement configuration information to terminal device 101.

[0192] Optionally, network device 201 may send MDT measurement configuration information to terminal device 101 based on a request from network device 202. For example, network device 202 may send a message to network device 201 instructing the issuance of MDT measurement configuration, and after receiving the message, network device 201 may send the MDT measurement configuration information to terminal device 101.

[0193] Optionally, network device 201 can configure MDT-related measurement tasks for terminal device 101 by sending RRC signaling carrying MDT measurement configuration information to terminal device 101.

[0194] Optionally, the network device corresponding to the source cell can send MDT measurement configuration information to the terminal device 101. The source cell is the cell that the terminal device 101 camped on before switching to the current camping cell (i.e., the cell corresponding to the network device 201), that is, the previous cell that the terminal device 101 camped on.

[0195] Optionally, MDT measurement configuration information can be carried in RRC signaling. That is, network device 201 or the network device corresponding to the source cell can configure MDT-related measurement tasks for terminal device 101 by sending RRC signaling carrying MDT measurement configuration information to terminal device 101.

[0196] Optionally, the Logged Measurement Configuration information element may include MDT measurement configuration information, and the Logged Measurement Configuration information element may be carried in RRC signaling. In this case, network device 201 or the network device corresponding to the source cell can instruct terminal device 101 to perform MDT measurement by sending RRC signaling carrying the Logged Measurement Configuration information element to terminal device 101.

[0197] For example, during the handover process from the source cell to the cell corresponding to the network device 201, the network device corresponding to the source cell can send an RRC connection reconfiguration message carrying a LoggedMeasurementConfiguration information element to the terminal device 101. This RRC connection reconfiguration message can not only be used to instruct the terminal device 101 to handover to the target cell, i.e., the cell corresponding to the network device 201, but also to instruct the terminal device 101 to perform MDT measurements.

[0198] It is understood that MDT measurement configuration information can also be carried in other RRC signaling (e.g., RRCConnectionSetup message, RRCConnectionReestablishment message, or RRCResume message, etc.), and this application does not impose any restrictions on this.

[0199] It is understood that there are other ways for network device 201 or source cell to send MDT measurement configuration information to terminal device 101, and this application does not limit this.

[0200] Optionally, the MDT measurement configuration information may include one or more of the following: report triggering conditions (or the timing of measurement data reporting, such as periodic reporting, event-triggered reporting, etc.); measurement cycle and duration; area range (e.g., measuring a specified cell or a specified geographical area); measurement content (e.g., signal strength, signal quality, cell identifier, etc.); location information (e.g., GNSS coordinates); timestamp.

[0201] S202: Terminal device 101 performs MDT measurement.

[0202] After receiving the MDT measurement configuration information sent by the network device 201, the terminal device 101 can perform measurements based on the MDT measurement configuration information, obtain measurement information, and record it.

[0203] S203: Network device 201 sends a UE information request to terminal device 101. Correspondingly, terminal device 101 receives the UE information request from network device 201. The UE information request instructs terminal device 101 to report measurement information.

[0204] Optionally, network device 201 may send UE Information Requests to terminal device 101 based on network requirements. For example, network device 201 may send UE Information Requests to terminal device 101 periodically. Another example is that network device 201 may send UE Information Requests to terminal device 101 based on events. Yet another example is that network device 201 may send UE Information Requests to terminal device 101 based on a request from network device 202.

[0205] Optionally, after receiving the RRC Setup Complete message sent by the terminal device 101, the network device 201 may send a UE Information Request to the terminal device 101 to instruct the terminal device 101 to report its measurement information, based on the information carried in the RRC Setup Complete message indicating that the terminal device 101 has recorded measurement information.

[0206] In one possible implementation, the RRCSetupComplete message received by network device 201 from terminal device 101 includes mobilityHistoryAvail, indicating that terminal device 101 supports storing mobility history information and has mobility history information available in VarMobilityHistoryReport. In other words, the information carried in the aforementioned RRCSetupComplete message indicating that terminal device 101 has recorded measurement information can be mobilityHistoryAvail. After receiving the RRCSetupComplete message including mobilityHistoryAvail, network device 201 can send a UE information request to terminal device 101.

[0207] For example, after terminal device 101 hands over from the source cell to the cell corresponding to network device 201, if it needs to re-establish the RRC connection (e.g., if the handover fails and reconstruction fails), it can send an RRC setup request to network device 201. Correspondingly, network device 201 can respond to the request, such as allocating radio resources to terminal device 101. After successfully configuring the radio resources, terminal device 101 can send an RRC setup complete message to network device 201. This RRC setup complete message may include mobilityHistoryAvail to indicate that terminal device 101 has available mobility history information in VarMobilityHistoryReport.

[0208] Optionally, after receiving the RRC recovery complete message sent by the terminal device 101, the network device 201 may send a UE information request to the terminal device 101 to instruct the terminal device 101 to report its measurement information, based on the information carried in the RRC recovery complete message indicating that the terminal device 101 has recorded measurement information.

[0209] In one possible implementation, the RRCResumeComplete message received by network device 201 from terminal device 101 includes mobilityHistoryAvail, indicating that terminal device 101 supports storing mobility history information and has mobility history information available in VarMobilityHistoryReport. In other words, the information carried in the RRCResumeComplete message indicating that terminal device 101 has recorded measurement information can be mobilityHistoryAvail. After receiving the RRCResumeComplete message including mobilityHistoryAvail, network device 201 can send a UE information request to terminal device 101.

[0210] For example, when terminal device 101 is in the RRC_INACTIVE state (deactivated state) (e.g., after terminal device 101 switches from the source cell to the cell corresponding to network device 201 but does not immediately transmit data, network device 201 can put terminal device 101 into the RRC_INACTIVE state), it can send an RRC recovery request (RRCResumeRequest) to network device 201. Correspondingly, network device 201 can respond to the request and, based on context information and the current network state, decide whether to restore the RRC connection. If the restoration is successful, network device 201 can send an RRC recovery (RRCResume) message to terminal device 101. Upon receiving the RRCesume message, terminal device 101 can perform the restoration and send an RRCesumeComplete message to network device 201 to complete the restoration. The RRCesumeComplete message may include mobilityHistoryAvail to indicate that terminal device 101 has available mobility history information in VarMobilityHistoryReport.

[0211] As you can understand, VarMobilityHistoryReport is a UE variable used to store mobility history information internally within the UE. VarMobilityHistoryReport can include VisitedCellInfoList, which records information about the primary cell (PCell) visited by the UE. In dual-connectivity (DC) scenarios, VarMobilityHistoryReport can also include VisitedPSCellInfoList, which records information about the primary secondary cell (PSCell) visited by the UE. During movement, the UE updates this variable based on cell change events (such as changes to PCell or PSCell). When the network requests the UE to report mobility history information, the UE can generate a MobilityHistoryReport based on VarMobilityHistoryReport.

[0212] Optionally, after receiving the RRC Reconfiguration Complete message sent by the terminal device 101, the network device 201 can send a UE information request to the terminal device 101 to instruct the terminal device 101 to report its measurement information, based on the information carried in the RRC Reconfiguration Complete message indicating that the terminal device 101 has recorded measurement information.

[0213] For example, terminal device 101 can switch from the source cell to the target cell, i.e., the cell corresponding to network device 201. After successfully accessing the cell corresponding to network device 201, terminal device 101 can send an RRCReconfigurationComplete message to network device 201. This RRCReconfigurationComplete message can not only be used to confirm that the handover has been successfully completed, but also to indicate that terminal device 101 has recorded measurement information.

[0214] It is understood that network devices may also send UE information requests to terminal devices 101 based on other signaling received, and this application does not impose any restrictions on this.

[0215] Optionally, the UE information request can be used to instruct the terminal device 101 to report the handover mechanisms it has used. The handover mechanisms used by the terminal device 101 may include the handover mechanisms used by the terminal device 101 in previous communication processes, such as the handover mechanisms used by the terminal device 101 before it camped on the current cell (i.e., the cell corresponding to the network device 201), or the handover mechanisms used by the terminal device 101 before it moved to the current cell.

[0216] Optionally, the UE information request can be used to instruct the terminal device 101 to report an MDT report (or MDT log), which includes the handover mechanisms used. Optionally, the MDT report can be a Logged MDT report, i.e., a measurement log.

[0217] Optionally, the UE information request can be used to instruct the terminal device 101 to report its mobility history information, which includes the handover mechanisms it has used. The mobility history information includes cell-related information recorded by the UE during movement, such as information related to cell handover, information related to cell reselection, dwell time, access order, etc.

[0218] Optionally, the UE information request can be used to instruct terminal device 101 to report a Mobility History Report, which includes the handover mechanisms used. The Mobility History Report is a report generated by the UE based on a network request and contains historical mobility information. It should be noted that in addition to the mobility history information in the Mobility History Report, other types of mobility history information also exist. That is, the network can request the UE to report not only the Mobility History Report but also other types of mobility history information. The UE can not only report the Mobility History Report to the network but also report other types of mobility history information to the network based on its own configuration.

[0219] For example, the UE information request sent by network device 201 to terminal device 101 may include a `mobilityHistoryReportReq` field set to `true`. `mobilityHistoryReportReq` is a field indicating whether the UE needs to report a mobility history report. If `mobilityHistoryReportReq` is set to `true`, it means the UE needs to report a mobility history report; if `mobilityHistoryReportReq` is set to `false`, it means the UE does not need to report a mobility history report.

[0220] S204: Terminal device 101 sends a UE information response to network device 201. Correspondingly, network device 201 receives the UE information response sent by terminal device 101. The UE information response includes handover type information from terminal device 101.

[0221] For ease of understanding and description, this application refers to the information used to indicate the handover mechanism used by the terminal device as handover type information.

[0222] After receiving the UE information request sent by the network device 201, the terminal device 101 can send a UE information response to the network device 201 based on the measurement information obtained from the measurement. The UE information response may include information indicating the handover mechanism used by the terminal device 101, that is, the handover type information of the terminal device 101.

[0223] Optionally, the handover type information of terminal device 101 included in the UE information response can be handover type information within a specific time period. It is understood that this application does not impose specific limitations on this specific time period. For example, this specific time period can be 6 hours before terminal device 101 hands over to the cell corresponding to network device 201. For example, this specific time period can be 1 day before terminal device 101 hands over to the cell corresponding to network device 201. Yet another example, this specific time period can be 7 days before terminal device 101 hands over to the cell corresponding to network device 201.

[0224] Optionally, after receiving the UE information request sent by the network device 201, the terminal device 101 can send a UE information response (UEInformationResponse) to the network device 201 without continuing measurement.

[0225] For example, a UE information request can be used to instruct terminal device 101 to report currently recorded mobility history information. In this case, after receiving the UE information request sent by network device 201, terminal device 101 can read the recorded measurement information (e.g., read the recorded measurement information directly from local storage) and report it to network device 201 through a UE information response.

[0226] Optionally, after receiving the UE information request sent by the network device 201, the terminal device 101 may continue to measure and then send a UE information response to the network device 201.

[0227] For example, a UE information request can be used to instruct the terminal device 101 to report mobility history information within a specific time period. In this case, after receiving the UE information request sent by the network device 201, the terminal device 101 can continue to measure and record new measurement data, and after completing the measurement within the specific time period, report it to the network device 201 through a UE information response.

[0228] Optionally, the UE information response may include an MDT report from terminal device 101, which may include handover type information of terminal device 101. For example, the MDT report from terminal device 101 may include a MobilityHistoryReport, which may include handover type information of terminal device 101.

[0229] For example, the UE information response may include a MobilityHistoryReport, which may contain mobility history information of the terminal device 101, such as a list of visited cells (e.g., VisitedCellInfoList). In other words, the MobilityHistoryReport may include handover type information.

[0230] In one possible implementation, MobilityHistoryReport-r16::=VisitedCellInfoList-r16 means that the specific content of MobilityHistoryReport is VisitedCellInfoList.

[0231] The VisitedCellInfoList can include mobility history information of one or more primary cells recently visited by the terminal device.

[0232] In one possible implementation, the VisitedCellInfoList in MobilityHistoryReport can include handover type information. Here, VisitedCellInfoList-r16::=SEQUENCE(SIZE(1..maxCellHistory-r16))OF VisitedCellInfo-r16, indicating that VisitedCellInfoList is a sequence (SEQUENCE) used to store multiple elements of type VisitedCellInfo, with the number of elements ranging from 1 to maxCellHistory. VisitedCellInfo can represent access information for a single cell. This means that VisitedCellInfoList can include mobility history information for at most maxCellHistory primary cells recently visited by the terminal device.

[0233] Specifically, in order to carry the handover type information of the terminal device in the UE information response, a new field handoverType can be added to the existing protocol-defined information element VisitedCellInfo, as shown below:

[0234]

[0235] The `VisitedCellInfo` is a sequence describing access information for a cell. `visitedCellId` is an optional field identifying the visited cell ID. `timeSpent` is an integer field ranging from 0 to 4095, representing the time spent in the cell, typically in seconds or milliseconds (the specific unit depends on the context). `visitedPSCellInfoListReport` is an optional field introduced in R17. It's a list reporting information about visited primary and secondary cells (PSCells), specifically in the format `VisitedPSCellInfoList`. `VisitedPSCellInfoList` is a sequence storing multiple `VisitedPSCellInfo` elements, ranging from 1 to `maxPSCellHistory`. `VisitedPSCellInfo` can represent access information for a single primary and secondary cell. This means that `VisitedPSCellInfoList` can include mobility history information for at most `maxPSCellHistory` primary and secondary cells recently visited by the terminal device. It should be noted that VisitedPSCellInfoList is typically used in dual-connectivity scenarios, where the user device is connected to both the PCCell and the PSCell simultaneously. HandoverType is a new field in VisitedCellInfo, and its specific format is HandoverType.

[0236] In this way, for primary cells previously accessed by the terminal device, the terminal device can record the handover mechanism used in that primary cell's access information (i.e., the VisitedCellInfo corresponding to that primary cell). If the terminal device has previously accessed multiple primary cells, it can record the handover mechanism used when accessing each primary cell separately in the access information of each primary cell. After the network subsequently obtains this access information, it can determine the handover mechanism used by the terminal device and adjust the handover mechanism accordingly for subsequent accesses to these primary cells or other cells. This not only improves handover performance but also avoids resource waste.

[0237] In one possible implementation, if the terminal device 101 has visited a certain primary cell multiple times before camping on the cell corresponding to the network device 201, then the VisitedCellInfoList in the UE information response sent by the terminal device 101 to the network device 201 may include multiple VisitedCellInfos corresponding to the primary cell, and each VisitedCellInfo represents the mobility history information recorded by the terminal device 101 when it accesses the primary cell once.

[0238] In one possible implementation, the VisitedPSCellInfoList in VisitedCellInfoList can also include switching type information.

[0239] Specifically, in order to carry the handover type information of the terminal device in the UE information response, a new field handoverType can be added to the VisitedPSCellInfo field in the VisitedPSCellInfoList field specified in the existing protocol, as shown below:

[0240]

[0241] Among them, VisitedPSCellInfo is a sequence used to describe the access information of a cell. visitedPSCellId is an optional field used to identify the ID of the visited cell. The meaning of timeSpent can be found above, and will not be repeated here. visitedPSCellInfoListReport is an optional field introduced in R17. handoverType is a new field in VisitedPSCellInfo, and its specific format is HandoverType.

[0242] In this way, in a dual-connectivity scenario, the terminal device can not only record the handover mechanism it used when accessing the primary cell, but also the handover mechanism it used when accessing the secondary cell. This means that the terminal device can record the handover mechanism it has used more comprehensively, which makes it easier for the network to adjust the subsequent handover mechanism based on the handover mechanism used by the terminal device in a timely manner. This will not only further improve handover performance, but also avoid resource waste.

[0243] In one possible implementation, if the terminal device 101 has visited a primary or secondary cell multiple times before camping on the cell corresponding to the network device 201, the VisitedPSCellInfoList in the UE information response sent by the terminal device 101 to the network device 201 may include multiple VisitedPSCellInfos corresponding to the primary or secondary cell, and each VisitedPSCellInfo represents the mobility history information recorded by the terminal device 101 for visiting the primary or secondary cell once.

[0244] The structure of HandoverType is given below as an example:

[0245]

[0246]

[0247] As shown in the data structure above, HandoverType is an enumeration type, with enumeration values ​​including traditionalHO, dapsHO, conditionalHO, ltmHO, c-ltmHO, spare3, spare2, and spare1. Specifically, traditionalHO corresponds to the integer value 0, dapsHO to the integer value 1, conditionalHO to the integer value 2, ltmHO to the integer value 3, c-ltmHO to the integer value 4, spare3 to the integer value 5, spare2 to the integer value 6, and spare1 to the integer value 7. In other words, a value of 0 in the handoverType field indicates a traditional HO switching mechanism; a value of 1 indicates a traditional DAPS switching mechanism; a value of 2 indicates a CHO switching mechanism; a value of 3 indicates an LTM switching mechanism; and a value of 4 indicates a C-LTM switching mechanism. spare3, spare2, and spare1 are reserved values. If new states or options need to be added later, these reserved values ​​can be used without redefining the entire enumeration type.

[0248] It should be noted that the above-described HandoverType structure is merely an example provided in this application, and it may include more or fewer enumeration values, and its enumeration values ​​may include more or fewer reserved values. This application does not impose any limitations on this.

[0249] Of course, HandoverType can also be other types, and this application does not impose any restrictions on this.

[0250] S205: Network device 201 sends the handover type information of terminal device 101 to network device 202. Correspondingly, network device 202 receives the handover type information of terminal device 101 sent by network device 201.

[0251] After receiving the UE information response sent by the terminal device 101, the network device 201 can send the handover type information in the UE information response to the network device 202. The handover type information in the UE information response is the handover type information of the terminal device 101.

[0252] Optionally, network device 201 may also send other mobility history information to network device 202. This other mobility history information may include one or more of the following: cell identifier, dwell time, location, handover time (e.g., handover timestamp), or handover result (success / failure), etc.

[0253] Optionally, network device 201 may send an MDT report to network device 202, which may include handover type information and other mobility history information of terminal device 101.

[0254] S206: Network device 202 sends message A1 to network device 201 based on the handover type information of terminal device 101. Message A1 is used to adjust the handover mechanism adopted by terminal device 101.

[0255] After receiving the handover type information of the terminal device 101 sent by the network device 201, the network device 202 can analyze the handover type information, that is, analyze the handover mechanism used by the terminal device 101, obtain the adjustment decision on the handover mechanism and / or configuration parameters, and send message A1 to the network device 201 based on the adjustment decision.

[0256] Optionally, message A1 can be used to instruct network device 201 to prohibit sending configuration information for one or more handover mechanisms other than its dominant handover mechanism to terminal device 101.

[0257] This not only enables network device 201 to issue a reasonable handover mechanism to terminal device 101, improving handover performance, but also avoids resource consumption caused by configuring other handover mechanisms.

[0258] The aforementioned dominant handover mechanism can be determined based on the number of handovers and the type of handover mechanism. For example, the dominant handover mechanism can be the handover mechanism with the most handovers. Another example is that the dominant handover mechanism can be any one or more handover mechanisms with a handover count greater than Y1. Yet another example is that the dominant handover mechanism can be any one or more handover mechanisms where the ratio of the handover count to the total handover count is greater than Y2. Yet another example is that the dominant handover mechanism can be any one or more handover mechanisms that satisfy at least two of the above conditions. The number of times each handover mechanism was used and the total number of handovers previously used by the terminal device 101 can both be determined based on the handover type information of the terminal device 101. Y1 is a positive integer, and Y2 is greater than 0 and less than 1. Y1 and Y2 can be set according to actual needs, and this application does not impose any restrictions on them.

[0259] For example, the dominant handover mechanism of terminal device 101 can be CHO, and message A1 can be used to instruct network device 201 to prohibit the distribution of LTM configuration information to terminal device 101.

[0260] Optionally, message A1 can be used to instruct the network device 201 to send configuration information of a specific handover mechanism to the terminal device 101 at a certain frequency. This specific handover mechanism can be a handover mechanism based on an upper layer (e.g., the RRC layer) of L1 / L2 (such as CHO), and / or a handover mechanism based on a lower layer (i.e., the layer below the RRC layer, such as L1 / L2) (such as LTM).

[0261] For example, if terminal device 101 is in a stationary / low-speed state, message A1 can be used to instruct network device 201 to prohibit the transmission of LTM configuration information to terminal device 101.

[0262] For example, if terminal device 101 is in a stationary / low-speed state, message A1 can be used to instruct network device 201 to prohibit the sending of configuration information for one or more handover mechanisms other than CHO to terminal device 101.

[0263] This satisfies the requirements for high reliability and high accuracy in handover, and avoids the resource consumption caused by frequent MAC CE signaling interactions and ping-pong handovers by terminal device 101.

[0264] For example, if terminal device 101 is in high-speed mode, message A1 can be used to instruct network device 201 to prohibit the sending of CHO configuration information to terminal device 101.

[0265] For example, if terminal device 101 is in high-speed mode, message A1 can be used to instruct network device 201 to prohibit the sending of configuration information for one or more handover mechanisms other than LTM to terminal device 101.

[0266] In this way, terminal device 101 can complete the handover only through the underlying signaling interaction, thereby reducing the handover latency and avoiding the resource consumption caused by configuring other handover mechanisms based on upper-layer signaling interaction.

[0267] For example, if terminal device 101 is in high-speed mode, message A1 can be used to instruct network device 201 to shorten the TA corresponding to LTM. For instance, message A1 can be used to instruct network device 201 to shorten the TA corresponding to LTM from 40 milliseconds (ms) to 20 ms.

[0268] In this way, network device 201 can reduce the uplink transmission lead of terminal device 101, thereby optimizing network performance, reducing signal transmission delay, and improving communication efficiency.

[0269] In one possible implementation, the terminal device 101 is in a stationary / low-speed state, which may include one or more of the following:

[0270] (1) The number of times terminal device 101 has switched is less than Y3;

[0271] (2) The dwell time of the terminal device 101 in the cell where it previously stayed was greater than t1.

[0272] The number of times the terminal device 101 has switched can be determined based on the switching type information of the terminal device 101.

[0273] It is understood that Y3 is a positive integer and t1 is a positive number. Y3 and t1 can be set according to actual needs, and this application does not impose any restrictions on them. For example, Y3 is 2.

[0274] For example, Y3 is 2 hours, t1 is 3 hours, and network device 201 can be as follows: Figure 5A Base station d2 is shown. (As shown) Figure 5AAs shown, base station d2 can send the handover type information of terminal device 101 to network device 202. Correspondingly, network device 202 can determine, based on this handover type information, that terminal device 101 has only performed one handover previously, i.e., from cell C4 corresponding to base station d1 to cell C5 corresponding to base station d2. In one possible implementation, based on the fact that terminal device 101 has only performed one handover previously (the number of handovers performed by terminal device 101 is less than Y3), network device 202 can send a message to base station d1 instructing base station d1 to prohibit the distribution of LTM configuration information to terminal device 101. In one possible implementation, the dwell time of terminal device 101 in cell C4 is 6 hours, and base station d2 can send the dwell time of terminal device 101 in cell C4 to network device 202. In this case, since terminal device 101 has only performed one handover before and the duration of terminal device 101's stay in cell C4 is greater than t1, network device 202 can send a message to base station d1 to instruct base station d1 to prohibit the distribution of LTM configuration information to terminal device 101.

[0275] In one possible implementation, the terminal device 101 is in a high-speed state, which may include one or more of the following:

[0276] (1) The number of times terminal device 101 has switched is greater than Y41;

[0277] (2) The number of times terminal device 101 used LTM for handover was greater than Y42;

[0278] (3) The dwell time of terminal device 101 in the cell where it previously stayed is less than t2.

[0279] The number of times the terminal device 101 has switched can be determined based on the switching type information of the terminal device 101.

[0280] It is understood that Y41 and Y42 are positive integers, Y41 is greater than Y3, Y42 is greater than Y3, t2 is a positive number, and t2 is less than t1. Y41, Y42, and t2 can be set according to actual needs, and this application does not impose any restrictions on them.

[0281] For example, Y41 is 6 minutes, t2 is 3 minutes, and network device 201 can be as follows: Figure 5B Base station e4 is shown. (For example...) Figure 5B As shown, base station e4 can send the handover type information of terminal device 101 to network device 202. Accordingly, network device 202 can determine based on this handover type information that terminal device 101 has previously performed 8 handovers, including the following: Figure 5BThe four handovers shown are from cell C6 corresponding to base station e1 to cell C7 corresponding to base station e2, from cell C7 corresponding to base station e2 to cell C8 corresponding to base station e3, and from cell C8 corresponding to base station e3 to cell C9 corresponding to base station e4. In one possible implementation, based on the fact that terminal device 101 has performed eight handovers previously (i.e., the number of handovers performed by terminal device 101 is greater than Y41), network device 202 can send a message to base station e4 instructing base station e4 to prohibit the distribution of CHO configuration information to terminal device 101. In another possible implementation, if the dwell time of terminal device 101 in each of the cells it has visited is less than 1 minute, base station d2 can send the dwell time of terminal device 101 in the eight cells it has visited to network device 202. In this case, based on the fact that terminal device 101 has performed 8 handovers and that the dwell time of terminal device 101 in the 8 cells it has visited is less than t2, network device 202 can send a message to base station e4 to instruct base station e4 to prohibit the distribution of CHO configuration information to terminal device 101.

[0282] Optionally, since terminal device 101 is an energy-sensitive device, message A1 can be used to instruct network device 201 to prohibit sending configuration information for one or more handover mechanisms to terminal device 101.

[0283] For example, given that terminal device 101 is an energy-sensitive device, message A1 can be used to instruct network device 201 to prohibit sending configuration information for one or more handover mechanisms other than its dominant handover mechanism to terminal device 101. It is understood that the confirmation method for the dominant handover mechanism can be referred to above, and will not be repeated here.

[0284] Optionally, since terminal device 101 is an energy-sensitive device, message A1 can be used to instruct network device 201 to send configuration information for a handover mechanism to terminal device 101 only.

[0285] This avoids resource consumption caused by configuring other handover mechanisms for energy-sensitive devices, enabling them to communicate for longer periods. It also allows energy-sensitive devices to be configured with handover mechanisms that offer better handover performance.

[0286] For example, message A1 can be used to instruct network device 201 to prohibit the distribution of configuration information for one or more handover mechanisms (such as CHO and / or LTM) other than HO to terminal device 101.

[0287] For example, message A1 can be used to instruct network device 201 to prohibit the sending of configuration information for one or more handover mechanisms (such as CLTM and / or LTM, etc.) other than CHO to terminal device 101.

[0288] Please see Figure 6 , Figure 6 This is a flowchart illustrating another communication method provided in this application embodiment. This application embodiment exemplifies an example where the first terminal includes terminal device 101 and terminal device 102, the first network device includes network device 201 and network device 204, the second network device is network device 202, the third network device is network device 203, the first message is UEInformationRequest, the second message is UEInformationResponse, the third message includes handover type information of terminal device 101 and handover type information of terminal device 102, and the fourth message is message A2.

[0289] like Figure 6 As shown, the method may include the following steps:

[0290] S301: Network device 201 sends MDT measurement configuration information to terminal device 101. Correspondingly, terminal device 101 receives the MDT measurement configuration information sent by network device 201.

[0291] S302: Terminal device 101 performs MDT measurement.

[0292] S303: Network device 201 sends a UE information request to terminal device 101. Correspondingly, terminal device 101 receives the UE information request from network device 201.

[0293] S304: Terminal device 101 sends a UE information response to network device 201. Correspondingly, network device 201 receives the UE information response sent by terminal device 101. The UE information response includes handover type information from terminal device 101.

[0294] S305: Network device 201 sends the handover type information of terminal device 101 to network device 202. Correspondingly, network device 202 receives the handover type information of terminal device 101 sent by network device 201.

[0295] It is understood that the specific implementation of steps S301-S305 can be referred to the relevant descriptions of steps S201-S205, and this application will not repeat them here.

[0296] S306: Network device 204 sends MDT measurement configuration information to terminal device 102. Correspondingly, terminal device 102 receives the MDT measurement configuration information sent by network device 204.

[0297] S307: Terminal device 102 performs MDT measurement.

[0298] S308: Network device 204 sends a UE information request to terminal device 102. Correspondingly, terminal device 102 receives the UE information request from network device 204.

[0299] S309: Terminal device 102 sends a UE information response to network device 204. Correspondingly, network device 204 receives the UE information response sent by terminal device 102. The UE information response includes handover type information from terminal device 102.

[0300] S310: Network device 204 sends the handover type information of terminal device 102 to network device 202. Correspondingly, network device 202 receives the handover type information of terminal device 102 sent by network device 204.

[0301] It is understood that the process of collecting and reporting handover type information of terminal device 102 shown in steps S305-S310 can refer to the relevant description of the process of collecting and reporting handover type information of terminal device 101 shown in steps S201-S205, and this application will not repeat it here.

[0302] S311: Network device 202 sends message A2 to network device 203 based on the handover type information of multiple terminal devices. Message A2 is used to adjust the handover mechanism adopted by the terminal devices accessing cell 1.

[0303] Network device 202 can receive handover type information from multiple terminal devices, such as handover type information for terminal device 101 sent by network device 201 and handover type information for terminal device 102 sent by network device 204. After receiving the handover type information from these multiple terminal devices, network device 202 can analyze the handover type information, that is, analyze the handover mechanisms used by these multiple terminal devices (such as terminal device 101 and terminal device 102), obtain adjustment decisions regarding the handover mechanisms and / or configuration parameters, and send message A2 to network device 203 based on the adjustment decisions.

[0304] In other words, network device 202 can receive not only the handover type information of terminal device 101 and terminal device 102, but also the handover type information of one or more other terminal devices. This means that network device 202 can analyze the handover type information of more terminal devices, thereby obtaining more reasonable adjustment decisions.

[0305] Optionally, network device 202 can determine the dominant handover mechanism for cell 1 based on the handover type information received from multiple terminal devices. In this case, message A2 can be used to instruct network device 203 to prohibit the distribution of configuration information for one or more handover mechanisms other than the dominant handover mechanism for cell 1 to terminal devices accessing cell 1.

[0306] This not only ensures that terminal devices use a reasonable handover mechanism when entering a specific area, improving handover performance, but also avoids resource consumption caused by configuring handover mechanisms other than the primary handover mechanism.

[0307] Optionally, message A2 can also be used to instruct network device 203 to shorten the TA corresponding to the dominant handover mechanism of cell 1. For example, if the dominant handover mechanism of cell 1 can be LTM, message A2 can be used to instruct network device 203 to shorten the TA corresponding to LTM from 40ms to 20ms.

[0308] In this way, when the terminal device moves to cell 1, the network device 203 can reduce its uplink transmission lead when the terminal device adopts the dominant handover mechanism of cell 1, thereby optimizing network performance, reducing signal transmission delay, and improving communication efficiency.

[0309] In one possible implementation, the dominant handover mechanism of cell 1 needs to satisfy one or more of the following:

[0310] (1) The number of times these multiple terminal devices have used this handover mechanism to switch to cell 1 is greater than Y7;

[0311] (2) The ratio of the number of times the multiple terminal devices previously used this handover mechanism to handover to cell 1 to the total number of handovers to cell 1 is greater than Y8;

[0312] (3) This handover mechanism is the most frequently used handover mechanism by these multiple terminal devices when they previously switched to cell 1;

[0313] (4) The number of times these multiple terminal devices have successfully switched to cell 1 using this handover mechanism is greater than Y9;

[0314] (5) The ratio of the number of times the multiple terminal devices successfully switched to cell 1 using this switching mechanism to the total number of switching to cell 1 is greater than Y10;

[0315] (6) The success rate of these multiple terminal devices switching to cell 1 using this handover mechanism is greater than that of Y11.

[0316] The number of times the multiple terminal devices previously used each handover mechanism to hand over to cell 1 can be determined based on their respective handover type information. The total number of handovers to cell 1 by the multiple terminal devices can be determined based on the handover type information of the multiple terminal devices. The success rate of the multiple terminal devices previously using the handover mechanism to hand over to cell 1 is the ratio of the number of times the multiple terminal devices previously successfully hand over to cell 1 using the handover mechanism to the number of times the multiple terminal devices previously hand over to cell 1 using the handover mechanism.

[0317] It is understood that Y7 and Y9 are positive integers, and Y8, Y10, and Y11 are all greater than 0 and less than 1. Y7, Y9, Y8, Y10, and Y11 can be set according to actual needs, and this application does not impose any restrictions on them.

[0318] For example, the dominant handover mechanism for cell 1 can be LTM, and Y8 can be 60%. If network device 202 determines, based on the handover type information of multiple terminal devices it receives, that the majority of the handover mechanisms used by these terminal devices when they previously switched to cell 1 were LTM (e.g., 80% were LTM) and a smaller number were CHO (e.g., 10% were CHO), then network device 202 can determine that the dominant handover mechanism for cell 1 is LTM. Furthermore, network device 202 can send message A2 to the network device corresponding to cell 1, i.e., network device 203, to instruct network device 203 to prohibit the distribution of CHO configuration information to terminal devices accessing cell 1.

[0319] Optionally, network device 202 may determine the dominant handover mechanism of cell 1 for a specific time period based on the handover type information received from multiple terminal devices.

[0320] Optionally, message A2 can be used to instruct network device 203 to send configuration information of the dominant handover mechanism of cell 1 for a specific time period to terminal devices accessing cell 1 in advance.

[0321] Optionally, message A2 can be used to instruct network device 203 to prioritize configuring the transmission configuration indicator (TCI) status set and / or pre-activate neighboring area (e.g., one or more cells) beams for the dominant handover mechanism of cell 1 before a specific time period.

[0322] Optionally, message A2 can also be used to instruct network device 203 to shorten the TA corresponding to the dominant handover mechanism of cell 1 during that specific time period.

[0323] This allows terminal devices to use a reasonable handover mechanism when entering a specific area during a specific time period, thereby improving handover performance.

[0324] Optionally, message A2 can also be used to instruct network device 203 to prohibit the distribution of configuration information for one or more handover mechanisms other than the dominant handover mechanism to terminal devices accessing cell 1 during a specific time period. This avoids resource consumption caused by configuring handover mechanisms other than the dominant handover mechanism.

[0325] In one possible implementation, the dominant handover mechanism of cell 1 during a specific time period needs to satisfy one or more of the following:

[0326] (1) The number of times these multiple terminal devices used this handover mechanism to switch to cell 1 during a specific time period was greater than Y12;

[0327] (2) The ratio of the number of times the multiple terminal devices used the handover mechanism to switch to cell 1 in a specific time period to the total number of handovers to cell 1 in the specific time period is greater than Y13;

[0328] (3) This handover mechanism is the most frequently used handover mechanism by these multiple terminal devices when switching to cell 1 during a specific time period;

[0329] (4) The number of times the multiple terminal devices successfully switched to cell 1 using this handover mechanism during a specific time period was greater than Y14;

[0330] (5) The ratio of the number of times the multiple terminal devices successfully switched to cell 1 using the handover mechanism in a specific time period to the total number of handovers to cell 1 in the specific time period is greater than Y15;

[0331] (6) The success rate of these multiple terminal devices switching to cell 1 using this handover mechanism during a specific time period is greater than that of Y16.

[0332] The number of times the multiple terminal devices previously used each handover mechanism to switch to cell 1 within a specific time period can be determined based on their respective handover type information and handover time. The total number of handovers of the multiple terminal devices previously used to switch to cell 1 within a specific time period can be determined based on the handover type information and handover time of the multiple terminal devices. The success rate of the multiple terminal devices previously used the handover mechanism to switch to cell 1 within a specific time period is the ratio of the number of times the multiple terminal devices previously used the handover mechanism to successfully switch to cell 1 within a specific time period to the number of times the multiple terminal devices previously used the handover mechanism to switch to cell 1 within a specific time period.

[0333] It is understood that Y12 and Y14 are positive integers, and Y13, Y15, and Y16 are all greater than 0 and less than 1. Y12, Y13, Y14, Y15, and Y16 can be set according to actual needs, and this application does not impose any restrictions on them.

[0334] For example, the handover mechanism of cell 1 during a specific time period can be LTM, Y13 can be 80%, and the specific time period can include 8:00 AM to 10:00 AM and 5:00 PM to 7:00 PM. If network device 202 determines, based on the handover type information of multiple terminal devices it receives, that the majority of the handover mechanisms used by these terminal devices when handover to cell 1 between 8:00 AM and 10:00 AM were LTM (e.g., 90% LTM) and a smaller number were CHO (e.g., 5% CHO), then network device 202 can determine that the dominant handover mechanism of cell 1 during the time period from 8:00 AM to 10:00 AM is LTM. If network device 202 determines, based on the handover type information of multiple terminal devices it receives, that the majority of the handover mechanisms used by these terminal devices when handover to cell 1 between 5:00 PM and 7:00 PM were LTM (e.g., 85% LTM) and a smaller number were CHO (e.g., 10% CHO), then network device 202 can determine that the dominant handover mechanism of cell 1 during the time period from 5:00 PM to 7:00 PM is LTM. Network device 202 can send message A2 to the network device corresponding to cell 1, namely network device 203, to instruct network device 203 to pre-configure LTM candidate TCI status to traffic hotspot cells, pre-activate neighbor cell beams, and prohibit the distribution of CHO configuration information to terminal devices accessing cell 1 between 8:00 and 10:00 in the morning and between 5:00 and 7:00 in the evening.

[0335] Optionally, if cell 2 is not in the candidate cell list of a certain handover mechanism, but the handover performance of that handover mechanism is better than the handover performance of the dominant handover mechanism of cell 2, message A2 can be used to instruct network device 203 to add cell 2 to the candidate cell list corresponding to the handover mechanism with better handover performance.

[0336] Optionally, the handover performance of this handover mechanism is superior to that of the dominant handover mechanism in cell 2, and may specifically include one or more of the following:

[0337] (1) The handover delay of this handover mechanism is lower than that of the dominant handover mechanism in cell 2;

[0338] (2) The handover success rate of this handover mechanism is higher than that of the dominant handover mechanism in cell 2;

[0339] (3) The handover interruption time of this handover mechanism is less than the handover interruption time of the dominant handover mechanism of cell 2;

[0340] (4) The flexibility of network resource allocation when using this handover mechanism is better than that when using the dominant handover mechanism of cell 2.

[0341] This allows terminal devices to use a more efficient handover mechanism when entering a specific area, thus improving handover performance.

[0342] It is understandable that the determination method of the dominant handover mechanism of cell 2 can refer to the description of the dominant handover mechanism of cell 1 above, and this application will not repeat it here.

[0343] For example, the dominant handover mechanism for cell 2 can be HO (House of Origin). If network device 202 determines, based on the handover type information received from multiple terminal devices, that the majority of the handover mechanisms used by these terminal devices when handover from cell 1 to cell 2 were HO (e.g., 90% HO), then network device 202 can determine that the dominant handover mechanism for handover from cell 1 to cell 2 is HO. In one possible implementation, if network device 202 determines, based on the handover type information received from multiple terminal devices, that the CHO candidate list corresponding to cell 1 does not include cell 2, then network device 202 can send message A2 to the network device corresponding to cell 1, i.e., network device 203, to instruct network device 203 to add cell 2 to the CHO candidate cell list corresponding to cell 1. In another possible implementation, if network device 202 determines, based on the handover type information received from multiple terminal devices, that the LTM candidate cell list corresponding to cell 1 does not include cell 2, then network device 202 can send message A2 to the network device corresponding to cell 1, i.e., network device 203, to instruct network device 203 to add cell 2 to the LTM candidate cell list corresponding to cell 1.

[0344] For example, the dominant handover mechanism for cell 2 can be LTM. If network device 202 determines, based on the handover type information received from multiple terminal devices, that the majority of the handover mechanisms used by these terminal devices when handover from cell 1 to cell 2 were LTM (e.g., 85% LTM), then network device 202 can determine that the dominant handover mechanism for handover from cell 1 to cell 2 is LTM. If network device 202 determines, based on the handover type information received from multiple terminal devices, that the C-LTM candidate list corresponding to cell 1 does not include cell 2, then network device 202 can send message A2 to the network device corresponding to cell 1, i.e., network device 203, to instruct network device 203 to add cell 2 to the C-LTM candidate cell list corresponding to cell 1.

[0345] The foregoing details the method provided in this application. To facilitate the implementation of the above-described solutions in the embodiments of this application, corresponding apparatus or devices are also provided in the embodiments of this application.

[0346] This application divides network devices (such as a first network device and a second network device) and terminal devices (such as a first terminal) into functional modules based on the above-described method embodiments. For example, each function can be divided into its own functional modules, or two or more functions can be integrated into one processing module. The integrated modules can be implemented in hardware or as software functional modules. It should be noted that the module division in this application is illustrative and represents only one logical functional division; other division methods may be used in actual implementation. The following will combine... Figure 7 The communication device of the embodiments of this application is described in detail.

[0347] See Figure 7 , Figure 7 This is a schematic diagram of the structure of a communication device provided in an embodiment of this application. Figure 7 As shown, the communication device may include a transceiver unit 10.

[0348] In some embodiments of this application, Figure 7 The communication device shown can be the first terminal shown above, or a chip or circuit disposed in the first terminal. That is, the communication device can be used to perform the steps or functions performed by the first terminal in the method embodiments described above.

[0349] In one possible implementation, the transceiver unit 10 can be used to: receive a first message sent by a first network device, the first message being used to instruct the first terminal to report mobility history information; and send a second message to the first network device, the second message including first information, the first information being used to instruct the first terminal on the handover mechanism used.

[0350] In one possible implementation, the first message is used to instruct the first terminal to report MDT measurement information, which includes the aforementioned mobility history information.

[0351] In one possible implementation, the second message includes second information used to indicate the mobility history information of the first terminal, and the second information includes the first information.

[0352] In one possible implementation, the second information includes third information, which includes access information for one or more primary cells accessed by the first terminal. This access information for a primary cell includes a first field, which indicates the handover mechanism used by the first terminal when accessing that primary cell. The first information includes the first field.

[0353] In one possible implementation, the aforementioned one or more primary cells include a first primary cell. The access information of the first primary cell in the third information includes fourth information. The fourth information includes access information of one or more primary and secondary cells accessed by the first terminal during its access to the first primary cell. The access information of the primary and secondary cells includes a second field, which is used to indicate the handover mechanism used by the first terminal when accessing the primary and secondary cells. The first information also includes the second field.

[0354] In one possible implementation, the value of the first field includes one of N preset values, which correspond to N switching mechanisms, where N is an integer greater than 1.

[0355] In one possible implementation, the value of the second field includes one of N preset values, which correspond to N switching mechanisms, where N is an integer greater than 1.

[0356] In some embodiments of this application, Figure 7 The communication device shown can be the first network device shown above, or a chip or circuit disposed in the first network device. That is, the communication device can be used to perform the steps or functions performed by the first network device in the method embodiments described above.

[0357] In one possible implementation, the transceiver unit 10 can be used to: send a first message to a first terminal, the first message being used to instruct the first terminal to report mobility history information; and receive a second message sent by the first terminal, the second message including first information, the first information being used to instruct the first terminal on the handover mechanism used.

[0358] In one possible implementation, the first message is used to instruct the first terminal to report MDT measurement information, which includes the aforementioned mobility history information.

[0359] In one possible implementation, the second message includes second information used to indicate the mobility history information of the first terminal, and the second information includes the first information.

[0360] In one possible implementation, the second information includes third information, which includes access information for one or more primary cells accessed by the first terminal. This access information for a primary cell includes a first field, which indicates the handover mechanism used by the first terminal when accessing that primary cell. The first information includes the first field.

[0361] In one possible implementation, the aforementioned one or more primary cells include a first primary cell. The access information of the first primary cell in the third information includes fourth information. The fourth information includes access information of one or more primary and secondary cells accessed by the first terminal during its access to the first primary cell. The access information of the primary and secondary cells includes a second field, which is used to indicate the handover mechanism used by the first terminal when accessing the primary and secondary cells. The first information also includes the second field.

[0362] In one possible implementation, the value of the first field includes one of N preset values, which correspond to N switching mechanisms, where N is an integer greater than 1.

[0363] In one possible implementation, the value of the second field includes one of N preset values, which correspond to N switching mechanisms, where N is an integer greater than 1.

[0364] In one possible implementation, the transceiver unit 10 can also be used to: after receiving the second message sent by the first terminal, send a third message to the second network device, the third message including the first information.

[0365] In some embodiments of this application, Figure 7 The communication device shown can be the second network device shown above, or a chip or circuit disposed in the second network device. That is, the communication device can be used to perform the steps or functions performed by the second network device in the method embodiments above.

[0366] In one possible implementation, the transceiver unit 10 can be used to: receive a third message sent by a first network device, the third message including first information, the first information being used to indicate the handover mechanism used by the first terminal; and send a fourth message to the first network device or the third network device based on the first information, the fourth message being used to adjust the handover mechanism used by the terminal device.

[0367] The first terminal, first network device, and second network device according to embodiments of this application have been described above. The following describes possible product forms of the first terminal, first network device, and second network device. It should be understood that any device possessing the above-described features... Figure 7 Any form of product that incorporates the functions of the first terminal, the first network device, or the second network device described herein falls within the protection scope of this application. It should also be understood that the following description is merely illustrative and does not limit the product form of the communication device in this application to these examples.

[0368] In one possible implementation, Figure 7In the communication device shown, the transceiver unit 10 can be a communication circuit. Specifically, when the communication device is a first terminal, a first network device, or a second network device, the communication circuit can be a transceiver circuit, which can be a transceiver unit; when the communication device is a chip or a chip system, the communication circuit can be an interface circuit; when the communication device is a server, the communication circuit can be an interface circuit or a transceiver circuit. The transceiver unit 10 can also be a transmitting unit and / or a receiving unit, where the transmitting unit can be a transmitting circuit and the receiving unit can be a receiving circuit, and the transmitting unit and receiving unit are integrated into a single device.

[0369] In one possible implementation, Figure 7 In the communication device shown, the transceiver unit 10 can be a transceiver, or the transceiver unit 10 can also be a transmitting unit and / or a receiving unit. The transmitting unit can be a transmitter, and the receiving unit can be a receiver. The transmitting unit and the receiving unit are integrated into one device, such as a transceiver.

[0370] In some embodiments of this application, Figure 7 The communication device shown may further include a processing unit that can perform the steps described above, together with the transceiver unit 10, of sending a fourth message to a first network device or a third network device based on the first information.

[0371] In some embodiments of this application, Figure 7 The processing unit in the communication device shown can be a processing circuit. The processing circuit and the communication circuit can be coupled, etc., and the connection method between the processing circuit and the communication circuit is not limited in this embodiment. During the execution of the above method, the process of sending information can be understood as the process of the processing circuit outputting the information. When outputting the information, the processing circuit outputs the information to the communication circuit for transmission. After being output by the processing circuit, the information may require further processing before reaching the communication circuit. Similarly, the process of receiving information in the above method can be understood as the process of the processing circuit receiving the input information. When the processing circuit receives the input information, the communication circuit receives the information and inputs it into the processing circuit. Furthermore, after the communication circuit receives the information, the information may require further processing before being input into the processing circuit.

[0372] In some embodiments of this application, Figure 7The processing unit in the communication device shown can be a processing circuit, which can be one or more processors, or all or part of the control or processing circuitry within one or more processors. In this embodiment, the processor and transceiver can be coupled, etc., and the connection method between the processor and transceiver is not limited in this embodiment. During the execution of the above method, the process of sending information can be understood as the process of the processor outputting the information. When outputting the information, the processor outputs the information to the transceiver so that the transceiver can transmit it. After being output by the processor, the information may require further processing before reaching the transceiver. Similarly, the process of receiving information in the above method can be understood as the process of the processor receiving the input information. When the processor receives the input information, the transceiver receives the information and inputs it to the processor. Furthermore, after the transceiver receives the information, the information may require further processing before being input to the processor.

[0373] See Figure 8 , Figure 8 This is a schematic diagram of the structure of another communication device provided in the embodiments of this application. For example... Figure 8 As shown, the communication device provided in this application embodiment can be used to implement the methods described in the above method embodiments, and the description in the above method embodiments can be referred to. The communication device can be a first terminal, or a chip in the first terminal, or a first network device, or a chip in the first network device, or a second network device, or a chip in the second network device. For example, the communication device includes a transceiver 1001. Optionally, the communication device may further include one or more processors 1002. Optionally, the communication device may further include a memory 1003. In one implementation, the communication device further includes an input / output device (...). Figure 8 (Not shown).

[0374] The processor 1002 is primarily used for processing communication protocols and data, controlling the entire communication device, executing software programs, and processing software program data. The memory 1003 is primarily used for storing software programs and data. In one possible implementation, the transceiver 1001 may include control circuitry and an antenna; the transceiver may also be a communication circuit, a communication interface, an input / output interface, or chip pins. The control circuitry is primarily used for converting baseband signals to radio frequency signals and processing radio frequency signals. The antenna is primarily used for transmitting and receiving radio frequency signals in the form of electromagnetic waves. Input / output devices, such as touchscreens, displays, and keyboards, are primarily used for receiving user input data and outputting data to the user.

[0375] In one possible implementation, processor 1002 can read software programs from memory 1003, interpret and execute the instructions of the software programs, and process the data of the software programs. When data needs to be transmitted wirelessly, processor 1002 performs baseband processing on the data to be transmitted and outputs a baseband signal to the radio frequency (RF) circuit. The RF circuit then performs RF processing on the baseband signal and transmits the RF signal outward in the form of electromagnetic waves through an antenna. When data is sent to the communication device, the RF circuit receives the RF signal through the antenna, converts the RF signal into a baseband signal, and outputs the baseband signal to processor 1002. Processor 1002 converts the baseband signal into data and processes the data.

[0376] In another implementation, the radio frequency circuitry and antenna can be set up independently of the processor performing baseband processing. For example, in a distributed scenario, the radio frequency circuitry and antenna can be arranged remotely, independent of the communication device.

[0377] In one possible implementation, the transceiver 1001, processor 1002, and memory 1003 can be connected via a communication bus.

[0378] For example, when the communication device is used to perform the above... Figure 3 , Figure 4 , Figure 6 In the illustrated embodiment, when the first terminal executes a step, method, or function, the transceiver 1001 can be used to perform... Figure 3 Steps S101-S102 in the illustrated embodiment, or Figure 4 Steps S201, S203, and S204 in the illustrated embodiment, or Figure 6 Steps S301, S303, and S304 in the illustrated embodiment, or Figure 6 Steps S306, S308, and S309 in the illustrated embodiment.

[0379] For example, when the communication device is used to perform the above... Figure 3 , Figure 4 , Figure 6 In the illustrated embodiment, when the first network device performs a step, method, or function, the transceiver 1001 can be used to perform... Figure 3 Steps S103 and S104 in the illustrated embodiment, or Figure 4 Steps S205 and S206 in the illustrated embodiment, or Figure 6 Steps S301, S303, S304, and S305 in the illustrated embodiment, or Figure 6 Steps S306, S308, S309, and S310 in the illustrated embodiment.

[0380] For example, when the communication device is used to perform the above... Figure 3 , Figure 4 , Figure 6 When the second network device in the illustrated embodiment performs a step, method, or function, the transceiver 1001 can be used to perform... Figure 3 Steps S103 and S104 in the illustrated embodiment, or Figure 4 Steps S205 and S206 in the illustrated embodiment, or Figure 6 Steps S305, S310, and S311 in the illustrated embodiment.

[0381] Optionally, the processor 1002 may be used to perform processes for the techniques described herein (such as determining, based on first information, the switching mechanism adopted by the terminal device, as shown in steps S206 and S311).

[0382] In any of the above implementations, the processor 1002 may include a transceiver for implementing receiving and transmitting functions. For example, the transceiver may be a transceiver circuit, an interface, or an interface circuit. The transceiver circuit, interface, or interface circuit for implementing receiving and transmitting functions may be separate or integrated. The aforementioned transceiver circuit, interface, or interface circuit can be used for reading and writing code / data, or it can be used for transmitting or relaying signals.

[0383] In any of the above implementations, the processor 1002 may store instructions, which may be computer programs. These computer programs, running on the processor 1002, cause the communication device to execute the methods described in the above method embodiments. The computer program may be embedded in the processor 1002; in this case, the processor 1002 may be implemented in hardware.

[0384] In one implementation, the communication device may include a circuit that can perform the functions of transmitting, receiving, or communicating in the aforementioned method embodiments. The processor and transceiver described in this application can be implemented on integrated circuits (ICs), analog ICs, radio frequency integrated circuits (RFICs), mixed-signal ICs, application-specific integrated circuits (ASICs), printed circuit boards (PCBs), electronic devices, etc. The processor and transceiver can also be manufactured using various IC process technologies, such as complementary metal-oxide semiconductors (CMOS), n-metal-oxide-semiconductor (NMOS), positive-channel metal-oxide semiconductors (PMOS), bipolar junction transistors (BJTs), bipolar CMOS (BiCMOS), silicon-germanium (SiGe), gallium arsenide (GaAs), etc.

[0385] For example, the processor described in this application may include one or more of the following: a central processing unit (CPU), an ASIC, a digital signal processor (DSP), a microprocessor unit (MPU), a microcontroller unit (MCU), a graphics processing unit (GPU), a field programmable gate array (FPGA), an artificial intelligence processor (AI processor), or a neural processing unit (NPU).

[0386] It is understood that the communication device shown in the embodiments of this application may also have more than Figure 8This application does not limit the use of other components or other related elements. The methods performed by the processor and transceiver shown above are merely examples; for the specific steps performed by the processor and transceiver, please refer to the description of the method embodiments above.

[0387] In another possible implementation, the communication device provided in this application embodiment may include one or more processors and a memory. The processor is used to execute a program stored in the memory, and when the program is executed, the method embodiment described above is performed. Exemplarily, the processor and memory may also be integrated into a single device, i.e., the processor and memory may be integrated together.

[0388] For example, the memory described in this application (e.g., memory 1003) may include, but is not limited to, cache, read-only memory (ROM), random access memory (RAM), synchronous dynamic random access memory (SDRAM), hard disk drive (HDD) or solid-state drive (SSD), erasable programmable read-only memory (EPROM), or compact disc read-only memory (CD-ROM), etc. Memory is any other medium capable of carrying or storing desired program code having an instruction or data structure form and accessible by a computer, but is not limited thereto. The memory in the embodiments of this application may also be a circuit or any other means capable of implementing storage functions for storing computer programs or instructions, and / or data.

[0389] This application also provides a communication system, which includes a first terminal, a first network device, and a second network device. The first terminal, the first network device, and the second network device can be used to execute any of the foregoing method embodiments. Figure 3 , Figure 4 , Figure 6 The method in ).

[0390] In addition, this application also provides a computer program for implementing the operations and / or processes performed by a communication device (such as the first terminal, the first network device, and the second network device described above) in the method provided in this application.

[0391] This application also provides a computer-readable storage medium storing computer code that, when executed on a computer, causes the computer to perform the operations and / or processes performed by a communication device (such as the first terminal, the first network device, and the second network device described above) in the method provided in this application.

[0392] This application also provides a computer program product, which includes computer code or a computer program that, when run on a computer, causes the operations and / or processes performed by a communication device (such as the first terminal, the first network device, and the second network device described above) in the method provided in this application to be executed.

[0393] In the embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative. For instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. In addition, the coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interfaces, devices, or units, or it may be an electrical, mechanical, or other form of connection.

[0394] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected according to actual needs to achieve the technical effects of the solutions provided in the embodiments of this application.

[0395] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

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

[0397] The above embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit it. 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 scope of the technical solutions of the embodiments of this application.

Claims

1. A communication method, characterized in that, The method is applied to a first terminal, and the method includes: Receive a first message sent by a first network device, the first message being used to instruct the first terminal to report mobility history information; A second message is sent to the first network device. The second message includes first information, which is used to indicate the handover mechanism used by the first terminal.

2. The method as described in claim 1, characterized in that, The first message is used to instruct the first terminal to report MDT measurement information, which includes the mobility history information.

3. The method as described in claim 1 or 2, characterized in that, The second message includes second information, which is used to indicate the mobility history information of the first terminal, and the second information includes the first information.

4. The method as described in claim 3, characterized in that, The second information includes the third information, which includes access information of one or more primary cells accessed by the first terminal. The access information of the primary cells includes a first field, which is used to indicate the handover mechanism used by the first terminal when accessing the primary cell. The first information includes the first field.

5. The method as described in claim 4, characterized in that, The one or more primary cells include a first primary cell, and the access information of the first primary cell in the third information includes fourth information. The fourth information includes access information of one or more primary and secondary cells accessed by the first terminal during the process of accessing the first primary cell. The access information of the primary and secondary cells includes a second field, which is used to indicate the handover mechanism used by the first terminal when accessing the primary and secondary cells. The first information also includes the second field.

6. The method as described in claim 4 or 5, characterized in that, The value of the first field includes one of N preset values, which correspond to N switching mechanisms, where N is an integer greater than 1.

7. The method as described in claim 5, characterized in that, The value of the second field includes one of N preset values, which correspond to N switching mechanisms, where N is an integer greater than 1.

8. A communication method, characterized in that, The method is applied to a first network device, and the method includes: Send a first message to the first terminal, the first message being used to instruct the first terminal to report mobility history information; The system receives a second message sent by the first terminal, the second message including first information, the first information being used to indicate the switching mechanism used by the first terminal.

9. The method as described in claim 8, characterized in that, The first message is used to instruct the first terminal to report MDT measurement information, which includes the mobility history information.

10. The method as described in claim 8 or 9, characterized in that, The second message includes second information, which is used to indicate the mobility history information of the first terminal, and the second information includes the first information.

11. The method as described in claim 10, characterized in that, The second information includes the third information, which includes access information of one or more primary cells accessed by the first terminal. The access information of the primary cells includes a first field, which is used to indicate the handover mechanism used by the first terminal when accessing the primary cell. The first information includes the first field.

12. The method as described in claim 11, characterized in that, The one or more primary cells include a first primary cell, and the access information of the first primary cell in the third information includes fourth information. The fourth information includes access information of one or more primary and secondary cells accessed by the first terminal during the process of accessing the first primary cell. The access information of the primary and secondary cells includes a second field, which is used to indicate the handover mechanism used by the first terminal when accessing the primary and secondary cells. The first information also includes the second field.

13. The method as described in claim 11 or 12, characterized in that, The value of the first field includes one of N preset values, which correspond to N switching mechanisms, where N is an integer greater than 1.

14. The method as described in claim 12, characterized in that, The value of the second field includes one of N preset values, which correspond to N switching mechanisms, where N is an integer greater than 1.

15. The method according to any one of claims 8-14, characterized in that, After receiving the second message sent by the first terminal, the method further includes: A third message is sent to a second network device, the third message including the first information.

16. A communication method, characterized in that, The method is applied to a second network device, and the method includes: Receive a third message sent by a first network device, the third message including first information, the first information being used to indicate the handover mechanism used by the first terminal; Based on the first information, a fourth message is sent to the first network device or the third network device, the fourth message being used to adjust the handover mechanism adopted by the terminal device.

17. A communication device, characterized in that, It includes at least one processor and a memory, the memory storing a computer program or instructions, the processor executing the computer program or instructions to implement the method of any one of claims 1-16.

18. A computer-readable storage medium, characterized in that, It stores a computer program or instructions, which, when executed, perform the method according to any one of claims 1-16.

Images