CN116097737A

CN116097737A - Communication method and communication device

Info

Publication number: CN116097737A
Application number: CN202080103914.4A
Authority: CN
Inventors: 胡星星; 张宏平
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2020-08-14
Filing date: 2020-08-14
Publication date: 2023-05-09
Also published as: CN116097737A8; WO2022032687A1

Abstract

The application provides a communication method and a communication device, which can obtain more accurate movement history information of terminal equipment. The method comprises the following steps: the first network equipment determines that the terminal equipment is changed to a first cell, wherein the change comprises dual-activation protocol stack DAPS switching, conditional switching CHO or radio resource control RRC reestablishment; the first network device starts recording first movement history information, which is history information of the terminal device in the first cell, at or after determining a time when the terminal device is changed to the first cell.

Description

Communication method and communication device

Technical Field

The present application relates to the field of communications, and more particularly, to a method of communication and a communication apparatus.

Background

Currently, in order to optimize mobility of a terminal device, the terminal device or a network device records movement history information of the terminal device. In the switching process of the terminal equipment, the target network equipment starts to record the movement history information of the terminal equipment at the moment of receiving the switching request message. However, at the time when the target network device receives the request message, the terminal device may not yet be switched to the target network device, and thus it is not reasonable for the target network device to start recording the movement history information of the terminal device at the time when the switch request message is received.

For example. In the conditional handover (condition handover, CHO) mechanism, the time when the source network device sends a handover request message to the target network device and the time when the terminal device selects the target cell (i.e. a candidate cell) to access may differ significantly, and it is not reasonable to record movement history information of the terminal device if the target network device starts recording from the time when the handover request message is received. For another example, during a dual active protocol stack handover (dual active protocol stack handover, DAPS HO), the terminal device has a connection with both the source network device (or source cell) and the target network device (or target cell) for a period of time, so it is not reasonable for the target network device to start recording the movement history information of the terminal device after receiving the handover request message.

Disclosure of Invention

The application provides a communication method for obtaining more accurate movement history information of terminal equipment.

In a first aspect, there is provided a method of communication, the method comprising: the first network equipment determines that the terminal equipment is changed to a first cell, wherein the change comprises dual-activation protocol stack DAPS switching, conditional switching CHO or radio resource control RRC reestablishment; the first network device starts recording first movement history information, which is history information of the terminal device in the first cell, at or after determining a time when the terminal device is changed to the first cell.

Based on the above technical solution, in the process that the terminal device performs CHO handover, DAPS handover or RRC reestablishment, when the target network device (i.e., the first network device) or the target cell (i.e., the first cell) determines that the terminal device is replaced to the target cell (i.e., the first cell), recording of movement history information of the terminal device is started, that is, recording of history information of the terminal device in the target cell is started, so that more accurate movement history information of the terminal device can be recorded, and thus the target network device can acquire more accurate movement conditions of the terminal device, so as to perform some optimizations more accurately.

With reference to the first aspect, in certain implementations of the first aspect, the first network device determining that the terminal device is changed to the first cell includes: the first network equipment determines that the terminal equipment is replaced to the first cell under the condition that the terminal equipment is successfully accessed to the first cell at random; the first network device starting recording of the first movement history information at or after determining a time when the terminal device is changed to the first cell includes: the first network device starts recording the first movement history information at or after the moment when the terminal device is determined to succeed in random access of the first cell.

With reference to the first aspect, in some implementations of the first aspect, if the change is a DAPS handoff, the determining, by the first network device, that the terminal device is changed to the first cell includes: the first network equipment determines that the terminal equipment is replaced to the first cell under the condition that first indication information is sent, wherein the first indication information is used for indicating the terminal equipment to disconnect from a second cell; the first network device starting recording of the first movement history information at or after determining a time when the terminal device is changed to the first cell includes: the first network device starts recording the first movement history information at or after the time when the first instruction information is transmitted.

With reference to the first aspect, in some implementations of the first aspect, if the change is a DAPS handoff, the first network device determining that the terminal device is changed to the first cell includes: the first network device determines that the terminal device is replaced to the first cell under the condition that second indication information is sent, wherein the second indication information is used for indicating a second cell or the second network device to release the context of the terminal device; the first network device starting recording of the first movement history information at or after determining a time when the terminal device is changed to the first cell includes: the first network device starts recording the first movement history information at or after the time when the second instruction information is transmitted.

With reference to the first aspect, in some implementations of the first aspect, the first movement history information further includes third indication information, where the third indication information is used to instruct the terminal device to switch from the first cell to the third cell in a DAPS handover manner.

With reference to the first aspect, in some implementations of the first aspect, the third indication information is further used to indicate a first period, where the first period represents a duration in which the terminal device is to be in the first cell and the third cell simultaneously in a DAPS handover procedure.

With reference to the first aspect, in some implementations of the first aspect, if the change is CHO, the determining, by the first network device, that the terminal device is changed to the first cell includes: the first network equipment determines that the terminal equipment is replaced to the first cell under the condition that a handover success message is sent; the first network device starting recording of the first movement history information at or after determining a time when the terminal device is changed to the first cell includes: the first network device starts recording the first movement history information at or after the time when the handover success message is transmitted.

With reference to the first aspect, in some implementations of the first aspect, if the change is CHO, the determining, by the first network device, that the terminal device is changed to the first cell includes: the first network equipment determines that the terminal equipment is replaced to the first cell under the condition that the first network equipment receives a serial number state transition message; the first network device starting recording of the first movement history information at or after determining a time when the terminal device is changed to the first cell includes: the first network device starts recording the first movement history information at or after the time when the sequence number state transition message is received.

With reference to the first aspect, in certain implementations of the first aspect, the method further includes: the first network device sends the first movement history information to a third network device, wherein the first movement history information comprises a second period of time, and the second period of time is the duration that the terminal device waits in the first cell.

With reference to the first aspect, in certain implementations of the first aspect, before the first network device determines that the terminal device is changed to the first cell, the method further includes: the first network device receives a handover request message from a second network device, wherein the handover request message comprises second movement history information recorded by the second network device, and the second movement history information comprises a third period of time, and the third period of time is a duration of time to be spent in a second cell at the terminal device; the first network device compensates for the duration from receiving the handover request message to determining that the terminal device is changed to the first cell into the third period.

Based on the above technical solution, the target network device may modify the time for the terminal device to stay in the source cell (the second cell) received in the handover request message, that is, compensate the time for the terminal device to stay in the source cell after the terminal device successfully switches to the target cell from the time for receiving the handover request message, so that the target network device may learn more accurate history information of the terminal device in the source cell, so as to perform some optimizations more accurately.

In a second aspect, a communication method is provided, applied to a dual-activation protocol stack switching process, and the method includes: the terminal equipment determines to switch from the second cell to the first cell; the terminal equipment records fourth movement history information after or at the moment of determining to switch from the second cell to the first cell, wherein the fourth movement history information is the history information of the terminal equipment in the second cell, and comprises a fourth period of time, and the fourth period of time is the waiting time in the second cell; the terminal device determining to switch from the first cell to the second cell comprises: under the condition that the terminal equipment receives first indication information, determining to switch from the second cell to the first cell, wherein the first indication information is used for indicating the terminal equipment to disconnect from the second cell; the terminal device recording fourth movement history information at or after determining a time of handover from the second cell to the first cell includes: the terminal device records the fourth movement history information at or after the time when the first indication information is received.

Based on the above technical solution, in the process of executing handover by the terminal device, when the terminal device determines that handover from the source cell (second cell) to the target cell (first cell) is successful, the terminal device records the history information (i.e., the third movement history information) of the source cell, so that more accurate movement history information of the terminal device can be recorded, and thus the network device can learn more accurate movement conditions of the terminal device, so as to more accurately perform some optimizations.

With reference to the second aspect, in some implementations of the second aspect, the fourth period includes a time to be spent in the second cell before the terminal device receives the first indication information.

With reference to the second aspect, in certain implementations of the second aspect, the method further includes:

the terminal equipment starts to record a fifth time period at the moment of determining that the random access of the first cell is successful, wherein the fifth time period is the time for the terminal equipment to wait in the first cell.

the terminal equipment starts to record a fifth time period at the moment of receiving the first indication information, wherein the fifth time period is the waiting time of the terminal equipment in the first cell.

With reference to the second aspect, in some implementations of the second aspect, the fourth movement history information further includes fourth indication information, where the fourth indication information is used to instruct the terminal device to switch from the second cell to the first cell in a DAPS handover manner.

With reference to the second aspect, in some implementations of the second aspect, the fourth indication information is further used to indicate a sixth period, where the sixth period represents a duration in which the terminal device is to be in the first cell and the second cell simultaneously during the DAPS handover.

In a third aspect, a communication method is provided, the method comprising: the central unit CU-control plane CP entity sends a minimization drive tests MDT measurement result to a tracking collection entity TCE or a core network CN;

the CU-CP entity sends the coexisting IDC information in the device detected by the terminal device to the TCE or the CN.

Based on the technical scheme, in the CU/DU architecture, the CU-CP sends MDT measurement results and IDC information to the TCE, and meanwhile, the TCE can obtain whether the MDT measurement results are affected by IDC interference or not, so that the MDT measurement results can be analyzed more accurately.

With reference to the third aspect, in certain implementations of the third aspect, the method further includes: the CU-CP entity receives a cell service tracking message from a distributed unit DU or CU-user plane UP entity; the CU-CP entity sending, to the TCE or the CN, the in-device coexistence IDC information detected by the terminal device, including: in case of receiving the cell service tracking message, the CU-CP entity transmits IDC information detected by the terminal device to the TCE or the CN.

With reference to the third aspect, in some implementations of the third aspect, the MDT measurement result is included in the cell traffic tracking message.

With reference to the third aspect, in certain implementations of the third aspect, the IDC information includes at least one of: whether the terminal device detects the IDC, which frequency points the terminal device detects the IDC in corresponding cells, the start time and the end time of the IDC, and the duration of the IDC.

With reference to the third aspect, in certain implementations of the third aspect, the MDT measurement includes a start time and an end time at which the MDT measurement is collected.

With reference to the third aspect, in certain implementations of the third aspect, the cell traffic trace message includes a trace identity and an internet protocol, IP, address of the TCE entity, the trace identity including a trace reference and a trace record session reference.

With reference to the third aspect, in some implementations of the third aspect, the cell service tracking message includes a request message for requesting the CU-CP entity to report IDC information detected by the terminal device.

With reference to the third aspect, in some implementations of the third aspect, the CU-CP entity receives indication information from a terminal device, where the indication information is used to indicate IDC information detected by the terminal device.

With reference to the third aspect, in some implementations of the third aspect, the indication information is further used to indicate frequency point information corresponding to frequency points where the terminal device detects IDC interference, or the indication information is used to indicate at which frequency points IDC interference is detected.

With reference to the third aspect, in some implementations of the third aspect, the indication information is further used to indicate information of a direction in which the terminal device detects IDC interference.

In a fourth aspect, a communication device is provided. The communication means may be a network device or a component in a network device. The communication device may comprise individual modules or units for performing the method of the first aspect and any one of the possible implementations of the first aspect.

In a fifth aspect, a communication device is provided that includes a processor. The processor is coupled to the memory and operable to execute instructions in the memory to implement the method of any one of the possible implementations of the first aspect. Optionally, the communication device further comprises a memory. Optionally, the communication device further comprises a communication interface, and the processor is coupled with the communication interface, and the communication interface is used for inputting and/or outputting information, and the information comprises at least one of instructions and data.

In one implementation, the communication apparatus is a network device. When the communication apparatus is a network device, the communication interface may be a transceiver, or an input/output interface.

Alternatively, the transceiver may be a transceiver circuit. Alternatively, the input/output interface may be an input/output circuit.

In another implementation, the communication device is a chip or a system of chips configured in a network device. When the communication device is a chip or a chip system configured in a network device, the communication interface may be an input/output interface, an interface circuit, an output circuit, an input circuit, a pin, or related circuits, etc. The processor may also be embodied as processing circuitry or logic circuitry.

In a sixth aspect, a communication device is provided. The communication means may be a terminal device or a component in a terminal device. The communication device may comprise individual modules or units for performing the method of the second aspect and any of the possible implementations of the second aspect.

In a seventh aspect, a communication device is provided that includes a processor. The processor is coupled to the memory and operable to execute instructions in the memory to implement the method of any one of the possible implementations of the second aspect described above. Optionally, the communication device further comprises a memory. Optionally, the communication device further comprises a communication interface, and the processor is coupled with the communication interface, and the communication interface is used for inputting and/or outputting information, and the information comprises at least one of instructions and data.

In one implementation, the communication device is a terminal device. When the communication device is a terminal device, the communication interface may be a transceiver, or an input/output interface.

In another implementation, the communication device is a chip or a system of chips configured in a terminal device. When the communication device is a chip or a chip system configured in a terminal device, the communication interface may be an input/output interface, an interface circuit, an output circuit, an input circuit, a pin, or a related circuit, or the like. The processor may also be embodied as processing circuitry or logic circuitry.

In an eighth aspect, a communication device is provided. The communication means may be a network device or a component in a network device. The communication device may comprise individual modules or units for performing the method of the third aspect and any possible implementation of the third aspect.

In a ninth aspect, a communications apparatus is provided that includes a processor. The processor is coupled to the memory and operable to execute instructions in the memory to implement the method of any one of the possible implementations of the third aspect. Optionally, the communication device further comprises a memory. Optionally, the communication device further comprises a communication interface, and the processor is coupled with the communication interface, and the communication interface is used for inputting and/or outputting information, and the information comprises at least one of instructions and data.

In one implementation, the communication device is a CU-CP entity. When the communication device is a CU-CP entity, the communication interface may be a transceiver, or an input/output interface.

In another implementation, the communication device is a chip or a system of chips configured in a CU-CP entity. When the communication device is a chip or a system of chips configured in a CU-CP entity, the communication interface may be an input/output interface, an interface circuit, an output circuit, an input circuit, a pin, or related circuitry, etc. The processor may also be embodied as processing circuitry or logic circuitry.

In a tenth aspect, there is provided a processor comprising: input circuit, output circuit and processing circuit. The processing circuit is configured to receive a signal via the input circuit and transmit a signal via the output circuit, such that the processor performs the method of any one of the possible implementations of the first to third aspects.

In a specific implementation process, the processor may be a chip, the input circuit may be an input pin, the output circuit may be an output pin, and the processing circuit may be a transistor, a gate circuit, a trigger, various logic circuits, and the like. The input signal received by the input circuit may be received and input by, for example and without limitation, a receiver, the output signal may be output by, for example and without limitation, a transmitter and transmitted by a transmitter, and the input circuit and the output circuit may be the same circuit, which functions as the input circuit and the output circuit, respectively, at different times. The embodiments of the present application do not limit the specific implementation manner of the processor and the various circuits.

In an eleventh aspect, a processing apparatus is provided that includes a communication interface and a processor. The communication interface is coupled with the processor. The communication interface is used for inputting and/or outputting information. The information includes at least one of instructions and data. The processor is configured to execute a computer program to cause the processing device to perform the method in any one of the possible implementations of the first to third aspects.

Optionally, the processor is one or more, and the memory is one or more.

In a twelfth aspect, a processing device is provided that includes a processor and a memory. The processor is configured to read instructions stored in the memory and is configured to receive a signal via the receiver and to transmit a signal via the transmitter, such that the processing means performs the method according to any one of the possible implementations of the first to third aspects.

Optionally, the processor is one or more, and the memory is one or more.

Alternatively, the memory may be integrated with the processor or the memory may be separate from the processor.

In a specific implementation process, the memory may be a non-transient (non-transitory) memory, for example, a Read Only Memory (ROM), which may be integrated on the same chip as the processor, or may be separately disposed on different chips.

It will be appreciated that the relevant information interaction process, for example, transmitting the indication information may be a process of outputting the indication information from the processor, and receiving the indication information may be a process of inputting the received indication information to the processor. Specifically, the information output by the processing may be output to the transmitter, and the input information received by the processor may be from the receiver. Wherein the transmitter and receiver may be collectively referred to as a transceiver.

The apparatus in the above eleventh and twelfth aspects may be a chip, and the processor may be implemented by hardware or by software, and when implemented by hardware, the processor may be a logic circuit, an integrated circuit, or the like; when implemented in software, the processor may be a general-purpose processor, implemented by reading software code stored in a memory, which may be integrated in the processor, or may reside outside the processor, and exist separately.

In a thirteenth aspect, there is provided a computer program product comprising: a computer program (which may also be referred to as code, or instructions) which, when executed, causes a computer to perform the method of any one of the possible implementations of the first to third aspects.

In a fourteenth aspect, there is provided a computer readable medium storing a computer program (which may also be referred to as code, or instructions) which, when run on a computer, causes the computer to perform the method of any one of the possible implementations of the first to third aspects.

A fifteenth aspect provides a communication system comprising the aforementioned terminal device and network device.

Drawings

Fig. 1 is a schematic diagram of a communication system suitable for use in the method of communication provided in an embodiment of the present application.

Fig. 2-5 are schematic flow diagrams of methods of communication provided by embodiments of the present application.

Fig. 6 and 7 are schematic block diagrams of communication apparatuses provided in embodiments of the present application.

Fig. 8 is a schematic structural diagram of a terminal device provided in an embodiment of the present application.

Fig. 9 is a schematic structural diagram of a network device according to an embodiment of the present application.

Detailed Description

The technical solutions in the present application will be described below with reference to the accompanying drawings.

The technical solution of the embodiment of the application can be applied to various communication systems, for example: long term evolution (Long Term Evolution, LTE) system, LTE frequency division duplex (frequency division duplex, FDD) system, LTE time division duplex (time division duplex, TDD), universal mobile telecommunications system (universal mobile telecommunication system, UMTS), worldwide interoperability for microwave access (worldwide interoperability for microwave access, wiMAX) telecommunications system, fifth generation (5th Generation,5G) telecommunications system or new radio access technology (new radio access technology, NR), vehicle-to-other devices (Vehicle-to-X V X), where V2X may include Vehicle-to-internet (Vehicle to network, V2N), vehicle-to-Vehicle (V2V), vehicle-to-infrastructure (Vehicle to infrastructure, V2I), vehicle-to-pedestrian (Vehicle to pedestrian, V2P), etc., workshop communication long term evolution technology (Long Term Evolution-Vehicle, LTE-V), vehicle networking, machine-like communications (Machine type communication, MTC), internet of things (internet of things, ioT), inter-Machine communication long term evolution technology (Long Term Evolution-Vehicle, LTE-X V), machine-to-Machine (Machine to Machine, M2M), etc.

In this embodiment of the present application, the network device may be any device having a wireless transceiver function. The apparatus includes, but is not limited to: an evolved Node B (eNB), a radio network controller (radio network controller, RNC), a Node B (Node B, NB), a base station controller (base station controller, BSC), a base transceiver station (base transceiver station, BTS), a home base station (home evolved NodeB, or a home Node B, HNB, for example), a Base Band Unit (BBU), an Access Point (AP) in a wireless fidelity (qireless fidelity, WIFI) system, a wireless relay Node, a wireless backhaul Node, a transmission point (transmission point, TP), or a transmission reception point (transmission and reception point, TRP), etc., may also be 5G, e.g., NR, a gNB in a system, or a transmission point (TRP or TP), one or a group of base stations (including multiple antenna panels) in a 5G system, or may also be a network Node constituting a gNB or a transmission point, such as a baseband unit (BBU), or a Distributed Unit (DU), etc.

In some deployments, the gNB may include a Centralized Unit (CU) and DUs. The gNB may also include an active antenna unit (active antenna unit, AAU). The CU implements part of the functionality of the gNB and the DU implements part of the functionality of the gNB, e.g. the CU is responsible for handling non-real time protocols and services, implementing radio resource control (radio resource control, RRC), traffic data adaptation protocol stack (service data adaptation protocol, SDAP) protocol layer, packet data convergence layer protocol (packet data convergence protocol, PDCP) layer. The DUs are responsible for handling physical layer protocols and real-time services, implementing the functions of the radio link control (radio link control, RLC), medium access control (media access control, MAC) and Physical (PHY) layers. The AAU realizes part of physical layer processing function, radio frequency processing and related functions of the active antenna. Since the information of the RRC layer may eventually become information of the PHY layer or be converted from the information of the PHY layer, under this architecture, higher layer signaling, such as RRC layer signaling, may also be considered to be transmitted by the DU or by the du+aau. It is understood that the network device may be a device comprising one or more of a CU node, a DU node, an AAU node. In addition, the CU may be divided into network devices in an access network (radio access network, RAN), or may be divided into network devices in a Core Network (CN), which is not limited in this application.

The functionality of a CU entity may be implemented by one or more entities. For example, the functions of the CU entity may be further split, e.g. the functions of the Control Plane (CP) and the functions of the User Plane (UP) may be separated, i.e. the CU entity includes a control plane (CU-CP) entity and a CU user plane (CU-UP) entity of the CU, which may be coupled to the DU entity, together completing the functions of the network device. In one possible way, the CU-CP entity is responsible for the control plane functions, mainly comprising RRC protocol layer and PDCP control plane (PDCP control plane, PDCP-C) protocol layer. The PDCP-C protocol layer is mainly responsible for encryption and decryption of control plane data, integrity protection, data transmission and the like. The CU-UP entity is responsible for the user plane functions, mainly comprising an SDAP protocol layer and a PDCP user plane (PDCP-U) protocol layer. The SDAP protocol layer is mainly responsible for mapping the data flow (flow) of the core network to the bearer. The PDCP-U protocol layer is mainly responsible for encryption and decryption of a data surface, integrity protection, header compression, sequence number maintenance, data transmission and the like. In this embodiment of the present application, the CU-CP entity and the CU-UP entity are connected through an interface (e.g., an E1 interface). The CU-CP entity is connected with the DU entity through F1-C (control plane), and the CU-UP entity is connected with the DU entity through F1-U (user plane). Furthermore, the CU-CP entity represents a network device and a control plane of the core network (e.g. a mobility management entity (mobility management entity, MME) of the fourth generation (4th generation,4G) core network, or an access mobility management function (access and mobility management function, AMF) network element of the 5G core network (5G core,5 gc); the CU-UP entity represents a network device and a user plane (e.g., a Serving Gateway (SGW) of a 4G core network, or a user plane function (user plane function, UPF) network element of a 5G core network) connection of the core network; the DU entity represents the network device and terminal device connection.

The network device provides services for the cell, and the terminal device communicates with the cell through transmission resources (e.g., frequency domain resources, or spectrum resources) allocated by the network device, where the cell may belong to a macro base station (e.g., macro eNB or macro gNB, etc.), or may belong to a base station corresponding to a small cell (small cell), where the small cell may include: urban cells (metro cells), micro cells (micro cells), pico cells (pico cells), femto cells (femto cells) and the like, and the small cells have the characteristics of small coverage area and low transmitting power and are suitable for providing high-rate data transmission services.

In an embodiment of the present application, the terminal device includes a User Equipment (UE), an access terminal, a subscriber unit, a subscriber station, a mobile station, a remote terminal, a mobile device, a user terminal, a wireless communication device, a user agent, or a user equipment. The terminal device in the embodiments of the present application may be a mobile phone (mobile phone), a tablet (pad), a computer with a wireless transceiving function, a Virtual Reality (VR) terminal device, an augmented reality (augmented reality, AR) terminal device, a wireless terminal in an industrial control (industrial control), a wireless terminal in an unmanned driving (self driving), a wireless terminal in a remote medical (remote medium), a wireless terminal in a smart grid (smart grid), a wireless terminal in a transportation security (transportation safety), a wireless terminal in a smart city (smart city), a wireless terminal in a smart home (smart home), a cellular phone, a cordless phone, a session initiation protocol (session initiation protocol, SIP) phone, a wireless local loop (wireless local loop, WLL) station, a personal digital assistant (personal digital assistant, PDA), a handheld device with a wireless communication function, a computing device or other processing device connected to a wireless modem, a vehicle-mounted device, a wearable device, a terminal in a smart city (smart city) or an evolved-from-to-land (PLMN) network, a public network (PLMN) or the like.

The wearable device can also be called as a wearable intelligent device, and is a generic name for intelligently designing daily wearing and developing wearable devices by applying a wearable technology, such as glasses, gloves, watches, clothes, shoes and the like. The wearable device is a portable device that is worn directly on the body or integrated into the clothing or accessories of the user. The wearable device is not only a hardware device, but also can realize a powerful function through software support, data interaction and cloud interaction. The generalized wearable intelligent device includes full functionality, large size, and may not rely on the smart phone to implement complete or partial functionality, such as: smart watches or smart glasses, etc., and focus on only certain types of application functions, and need to be used in combination with other devices, such as smart phones, for example, various smart bracelets, smart jewelry, etc. for physical sign monitoring.

Furthermore, the terminal device may also be a terminal device in an internet of things (internet of things, ioT) system. IoT is an important component of future information technology development, and its main technical feature is to connect an item with a network through a communication technology, so as to implement man-machine interconnection and an intelligent network for object interconnection.

The specific form of the terminal device is not limited in this application.

To facilitate an understanding of the embodiments of the present application, a communication system suitable for use in the embodiments of the present application will be described in detail with reference to fig. 1. Fig. 1 shows a schematic diagram of a communication system suitable for use in the communication method and the communication apparatus of the embodiments of the present application. As shown in fig. 1, communication system 100 may include at least two network devices, such as network device 110 and network device 120 shown in fig. 1; the communication system 100 may also include at least one terminal device, such as the terminal device 130 shown in fig. 1. Wherein the terminal device 130 may be mobile or stationary. Both network device 110 and network device 120 are devices that may communicate with terminal device 130, such as base stations or base station controllers, via wireless links. Each network device may provide communication coverage for a particular geographic area and may communicate with terminal devices located within the coverage area (cell).

Fig. 1 illustrates two network devices and one terminal device by way of example, and the communication system 100 may alternatively include at least one network device and may include other numbers of terminal devices within the coverage area of each network device, which is not limited in this embodiment of the present application.

Each of the above-described communication devices, such as the network device 110, the network device 120, or the terminal device 130 in fig. 1, may be configured with a plurality of antennas. The plurality of antennas may include at least one transmitting antenna for transmitting signals and at least one receiving antenna for receiving signals. In addition, each communication device may additionally include a transmitter chain and a receiver chain, each of which may include a plurality of components (e.g., processors, modulators, multiplexers, demodulators, demultiplexers, antennas, etc.) associated with the transmission and reception of signals, as will be appreciated by one skilled in the art. Thus, communication between the network device and the terminal device may be via multiple antenna technology.

Optionally, the wireless communication system 100 may further include a network controller, a mobility management entity, and other network entities, which embodiments of the present application are not limited thereto.

To facilitate an understanding of the embodiments of the present application, the terms referred to in this application are first briefly described.

1. Dual active protocol stack handover (dual active protocol stack handover, DAPS HO): in order to ensure zero interruption in the switching process of terminal equipment, DAPS switching is introduced in the communication industry standard.

In the conventional handover process, after receiving a handover command of a source network device, a terminal device disconnects from a source cell and accesses to a target cell. Unlike the conventional handoff, in the DAPS handoff process, after receiving the handoff command sent by the source network device, the terminal device accesses to the target cell, and at the same time, maintains communication with the source cell link until the target network device notifies the terminal device to completely release the source cell configuration, and the terminal device does not stop communication with the source cell and releases the communication link with the source cell.

The handoff procedure of the DAPS is similar to the conventional handoff procedure in that the source network device determines to perform handoff and then the source network device sends a handoff request to the target network device. Further, the target network device replies a handover confirm message to the source network device, indicating that the receiving terminal is handed over to the target cell. Further, the source network device sends a handover command to the terminal device, instructing the terminal device to handover to the target cell. The terminal device then simultaneously maintains the connection of the source cell and the target cell. When the terminal equipment is successfully accessed to the target cell, the target cell sends a message to the core network, the core network switches the converted downlink data stream to the target network equipment, and simultaneously issues an end marker (end marker) data packet to the source network equipment. The source network device then forwards the data to the target network device. After the terminal device successfully accesses to the target cell, the target network device can inform the terminal device to release the source cell connection, thereby completing the DAPS switching process.

In the DAPS switching process, after the terminal equipment is successfully accessed to the target network equipment, the terminal equipment stops sending new uplink data to the source network equipment. After the terminal device successfully releases the connection with the source cell, the terminal device stops all communication with the source network device. When the terminal equipment is successfully accessed to the target network equipment, the source network equipment receives a switching success indication message sent by the target network equipment, and therefore the source network equipment stops sending new downlink data to the terminal equipment.

2. Conditional switch (condition handover, CHO):

in the conventional handover procedure, mobility management of the connected terminal device is controlled by the network device, i.e. the network device instructs the terminal device which cell to handover to by sending a handover message, and instructs the terminal device how to perform the handover. Specifically, the source network device sends a handover message to the terminal device to control the terminal device to switch from the source cell to the target cell, and the terminal device accesses the target cell according to the content contained in the handover message after receiving the handover message. Thus, successful transmission of the handover message is a necessary condition to ensure successful handover under the conventional handover mechanism. However, in the LTE system, the NR system, or other systems, rapid degradation of signal quality, rapid movement of a terminal device, shielding of an object, long duration of handover preparation, and the like all cause failure of transmission of a handover message, and further cause failure of handover, and reduce success rate of handover. In addition, in the conventional handover procedure, the network device generally determines whether to instruct the terminal device to perform handover according to the signal quality reported by the terminal device, for example, when the terminal device detects that the signal quality of the neighboring cell is better than the signal quality of the current serving cell by a certain threshold, the terminal device reports the measurement result. However, in the LTE system, the NR system, or other systems, rapid degradation of signal quality, rapid movement of a terminal device, and shielding of an object may all cause failure of sending a measurement report, and further cause handover failure, thereby reducing the success rate of handover.

In view of the above, CHO mechanisms are introduced in the communication industry standard to improve the handover success rate.

In the CHO mechanism, when the source link quality is good, the source cell sends CHO configuration information to the terminal device, where the CHO configuration information may include CHO trigger conditions and information of one or more candidate cells, where the information of the candidate cells may include a cell global identifier (cell global identifier, CGI) of the candidate cell, or may include a physical cell identifier (physical cell identifier, PCI) of the candidate cell and frequency information corresponding to the candidate cell. After receiving the CHO configuration information, the terminal device determines whether the candidate cell satisfies the CHO trigger condition according to the CHO configuration information, and takes a candidate cell satisfying the CHO trigger condition as a target cell. Then, the terminal device performs a random access procedure with the determined target cell, and when the random access is successfully completed, the terminal device sends an RRC message (e.g., an RRC reconfiguration complete message) to the target cell, so as to notify that the condition handover of the target cell is completed.

3. Movement history information of the terminal device:

one of the purposes of introducing movement history information of a terminal device in the prior art is to optimize the mobility of the terminal device. For example, in macro-micro networking (i.e. some cells have a relatively large coverage area (e.g. frequency point f1 is adopted), and other cells have a relatively small coverage area (e.g. frequency point f2 is adopted), the terminal device is switched only in the macro station (cell with a large coverage area) as much as possible, so as to reduce the number of RRC messages interacted between the terminal device and the network device. Because the coverage of the microcell is relatively small, if the terminal device is handed over in the microcell, the terminal device may be handed over between a plurality of cells in a short time, resulting in a relatively large number of RRC messages interacted between the terminal device and the network device.

Another object of the prior art is to introduce movement history information of a terminal device: when the terminal equipment is switched between cells, the network equipment can estimate the speed or the history cell of the terminal equipment according to the movement history information of the terminal equipment, so as to configure different measurement parameters for the terminal equipment. For example, the network device may learn, according to the movement history information of the terminal device, that the terminal device may perform ping-pong handover between different cells, so that the network device may replace parameters corresponding to the handover, and so on.

The movement history information of the terminal device may be recorded by the terminal device or by the network device.

If the terminal device supports storing the movement history information, the terminal device records the movement history information in the following manner:

(1) When a cell is changed (i.e., a primary cell in an RRC connected state or a serving cell in an RRC idle state of the terminal device is changed to another co-system cell or a different system cell, or the terminal device enters a non-serving cell), the terminal device includes or adds an entity that records a movement history, including visitedcyllnfo, which is information of an access cell, including visitedcylid (the number of entities that the terminal device can save is limited, and if the number exceeds the maximum number, the first saved entity is deleted), in a variable that saves the movement history, and records the relevant contents in the following manner:

a, if the CGI of the previous primary or serving cell is available, carrying the CGI in the entity; if the VGI of the previous primary or serving cell is not available, the PCI and frequency point of the primary or serving cell are carried in this entity.

b, the time that the terminal device is waiting in the previous primary or serving cell is saved in the entity.

(2) When the terminal device enters the current RAT from other radio access technologies (radio access technology, RAT) or the terminal device enters the current RAT from a non-service area, the terminal device includes or adds an entity recording the movement history, including the information visitedcylinfo of the visited cell, in a variable holding the movement history (the number of entities that the terminal device can hold is limited, if the number exceeds the maximum number, the first stored entity is deleted first), and the time to wait outside the current RAT is recorded in the entity.

When the terminal device re-accesses the network from an inactive state (inactive) or an idle state (idle), the terminal device instructs the network device when accessing the network, and the terminal device stores the movement history information. For example, the terminal device may carry an indication information in an RRC connection setup complete (RRCConnection setupcomplete) message or an RRC connection setup resume complete (rrcconnectionresuxemplete) message for indicating that the terminal device has saved the movement history information. Further, the network device may request the terminal device to report the movement history information. For example, the network device may carry a request movement history information indication in a terminal device information request (ueinfo request) message. Further, after receiving the request of the network device, the terminal device may report the movement history information to the network device. For example, the terminal device may carry the movement history information in a terminal device information response (ueinfo response) message.

If the terminal device switches between different cells or network devices, the source cell/network device will send the movement history information reported by the terminal device to the target cell/network device. For example, the source cell/network device may carry the movement history information of the terminal device in a handover request message.

If the network device supports storing the movement history information of the terminal device, the network device records the movement history information of the terminal device in the following manner:

the network device may also record movement history information of the terminal device when the terminal device is in the RRC connected state. For example, if the serving cell corresponding to the terminal device changes, the network device may record the cell corresponding to the serving cell before the change, for example, may record the CGI of the cell, the type of the cell (for example, the size of the cell, the value may be very small, medium, and large), and the time when the terminal device is waiting in the cell. If the terminal equipment is switched, the source network equipment sends the previously recorded movement history information of the terminal equipment to the target network equipment. For example, the source network device carries the movement history information of the terminal device in a handover request message, and sends the handover request message to the target network device. Further, the target network device may perform some movement optimization according to the movement history information, and start recording the movement history information of the terminal device.

The network device may perform other purposes according to the movement history information of the terminal device, for example, the network device may reduce the number of times the terminal device measures the cell or the frequency point according to the movement history information of the terminal device, so as to save the electric quantity of the terminal device.

As described above, in the case where the terminal device performs the handover between network devices, the source network device may carry the movement history information of the terminal device in the handover request message and send the handover request message to the target network device. Accordingly, the target network device starts to collect and store the movement history information of the terminal device after receiving the handover request message from the source network device, that is, the handover request message sent by the source network device to the target network device may trigger the target network device to start collecting and storing the movement history information of the terminal device (for example, start recording the waiting time of the terminal device in the cell of the target network device).

However, in the CHO mechanism, the time when the source network device sends the handover request message to the target network device and the time when the terminal device selects the target cell (i.e., a candidate cell) for access may be relatively different, and if the target network device starts recording the movement history information of the terminal device from the time when the handover request message is received, it is not reasonable.

In addition, in the prior art, after the source network device sends a handover message carrying the movement history information of the terminal device to the target network device, recording of the movement history information of the terminal device is stopped. However, in the DAPS handover procedure, the terminal device is connected to both the source network device (or the source cell) and the target network device (or the target cell) for a period of time, so it is not reasonable for the source network device to stop recording the movement history information of the terminal device after sending the handover request message, because the terminal device is still connected to the source cell. At the same time, the terminal equipment also needs to explicitly generate the information of the access cell (i.e. the source cell) during the DAPS handover process.

Based on the above, the present application provides a communication method, in which, in the process of switching the terminal device, the terminal device and the network device can reasonably record the movement history information of the terminal device.

The method provided by the embodiment of the application is described in detail below with reference to the accompanying drawings.

It should be understood that the following details of the method provided in the embodiments of the present application are given only for easy understanding and explanation, taking the interaction between the terminal device and the network device as an example. This should not be construed as limiting the subject matter of the methods provided herein. For example, the terminal device shown in the following embodiments may be replaced with a component (such as a chip or a circuit) or the like configured in the terminal device. The network device shown in the following embodiments may also be replaced with a component (such as a chip or a circuit) or the like configured in the network device.

The embodiments shown below are not particularly limited to the specific structure of the execution body of the method provided in the embodiments of the present application, as long as the communication can be performed by the method provided in the embodiments of the present application by running the program recorded with the code of the method provided in the embodiments of the present application, and for example, the execution body of the method provided in the embodiments of the present application may be a terminal device or a network device, or a functional module in the terminal device or the network device that can call the program and execute the program.

Fig. 2 is a schematic flow chart of a method 200 of communication provided by an embodiment of the present application, shown from the perspective of device interaction. The steps in method 200 are described in detail below.

S201, the network device #2 (an example of the second network device) transmits a CHO request message to the network device #1 (an example of the first network device). Accordingly, in S201, network device #1 receives the CHO request message from network device # 2.

The network device #1 is a network device to which the cell #1 (an example of the first cell) belongs, the cell #1 is a cell to which the terminal device is to be connected, the cell #1 may be referred to as a candidate cell or a target cell, and the network device #1 may be referred to as a target network device.

Network device #2 is a network device to which cell #2 belongs, cell #2 is a cell that serves a terminal device before CHO, cell #2 may also be referred to as a source cell, and network device #2 may also be referred to as a source network device.

The network device #1 and the network device #2 may be the same network device or different network devices, which is not limited in the embodiment of the present application.

In S201, cell #2 may transmit a CHO request message (an example of a handover request message) to cell # 1.

Alternatively, the CHO request message may carry movement history information #1 (an example of the second movement history information).

The movement history information #1 is movement history information of the terminal device recorded by the network device #2 before the CHO request message was transmitted, and the movement history information #1 includes history information of the terminal device in the cell # 2. For example, the movement history information #1 may include one or more of the following: CGI of cell #2, PCI of cell #2, center frequency point of cell #2, period #1 (an example of the third period), period #1 representing a time when the terminal device is waiting in cell # 2. Since the movement history information #1 is information recorded by the network device #2 before transmitting the CHO request message, the movement history information #1 includes a period #1 that is a time for the terminal device to wait in the cell #2 before the network device #2 transmits the CHO request message.

It will be appreciated that if network device #1 is the same network device as network device #2, the CHO request message may not carry the movement history information #1.

Alternatively, the CHO request message may be a handover request message, in which case the handover request message may further include indication information #1, where the indication information #1 is used to indicate that the handover request message is a handover request message under the CHO handover mechanism.

S202, the network device #1 transmits a CHO request acknowledgement message to the network device # 2. Accordingly, in S202, network device #2 receives the CHO request confirm message from network device #1.

The CHO request confirm message includes RRC configuration information configured by the network device #1 for the terminal device. Specifically, the CHO request confirm message includes RRC configuration information configured by cell #1 for the terminal device. For more description of RRC configuration information, reference may be made to the prior art, and for brevity, embodiments of the present application will not be repeated.

S203, the network device #2 transmits CHO configuration information to the terminal device. Accordingly, in S203, the terminal device receives CHO configuration information from the network device # 2.

The CHO configuration information includes RRC configuration information configured by the network device #1 for the terminal device. Specifically, the CHO configuration information includes RRC configuration information configured by the cell #1 for the terminal device. The CHO configuration information further includes a trigger condition for the terminal device to access to cell #1.

S204, the terminal equipment judges whether the triggering condition of the cell #1 is met.

In case the triggering condition of cell #1 is fulfilled, the terminal device may switch to cell #1, i.e. switch from cell #2 to cell #1. Such as initiating a random access procedure or sending an RRC reconfiguration complete message to cell #1.

For example, the triggering condition for the terminal device to access the cell #1 is that the signal quality of the cell #1 is greater than a preset threshold. The terminal device initiates random access to the cell #1 in case that the signal quality of the cell #1 is greater than a preset threshold.

When the triggering condition of the cell #1 is not met, when the terminal equipment detects that the cell #2 fails in radio link, the terminal equipment performs an RRC reestablishment process, in which the terminal equipment performs cell selection, if the selected cell is a candidate cell in CHO configuration information sent by the network equipment #2 to the terminal equipment, and the network equipment #2 sends an indication information to the terminal equipment, where the indication information indicates that the terminal equipment can perform a condition reconfiguration (i.e., perform RRC configuration information corresponding to the candidate cell) if the selected cell is the candidate cell when the terminal equipment detects that the radio link fails, the terminal equipment is changed to the candidate cell (e.g., the cell # 1), i.e., is switched from the cell #2 to the candidate cell (the terminal equipment sends an RRC reconfiguration complete message to the candidate cell).

S210, the terminal equipment is changed to cell #1. Accordingly, in S210, the network device #1 determines that the terminal device is changed to the cell #1.

It should be understood that in S210 the terminal device is changed to cell #1, indicating that the terminal device is successfully changed to cell #1, i.e. the terminal device successfully establishes a connection with cell #1.

The terminal device changes to the cell #1, which may be that the terminal device successfully switches from the cell #2 to the cell #1, or that the terminal device initiates the RRC reestablishment successfully in the cell #1 (here, the terminal device selects a candidate cell in CHO in the RRC reestablishment process after detecting the radio link failure). The present application is not limited in this regard.

In S210, it may be that cell #1 determines that the terminal device is changed to cell #1.

S220, the network device #1 starts recording movement history information #2 (an example of the first movement history information) at or after the time when it is determined that the terminal device is changed to the cell #1, the movement history information #2 being history information of the terminal device in the cell #1.

In S220, the cell #1 may start recording the movement history information #2 at or after the time when the terminal is determined to be changed to the cell #1.

The movement history information #2 may include one or more of the following: CGI of cell #1, PCI of cell #1, center frequency point of cell #1, period #2 (an example of the second period), period #2 being a time when the terminal device is waiting in cell #1.

The network device #1 starts recording the movement history information #2 can be understood as that the network device #1 starts recording the time the terminal device is waiting in the cell #1. That is, the network device #1 considers that the terminal device starts to be in the cell #1 at or after the timing of determining that the terminal device is changed to the cell #1. Optionally, the network device #1 may also start recording the CGI of the cell #1 or the PCI and center frequency point of the cell #1. The time at which the network device #1 generates the movement history information #2 is not limited to itself. The network device #1 may generate the movement history information #2 after determining that the terminal device is handed over from the cell #1 to the other cell. The network device #1 starting to record the movement history information #2 can also be understood as the network device #1 starting to collect the movement history information #2. Recording movement history information in this application may be understood as collecting movement history information.

The embodiment of the present application does not limit how the network device #1 determines whether the terminal device is changed to the cell #1. It should be understood that, in different manners, the time when the network device #1 determines that the terminal device is changed to the cell #1 may be different, and further, the time when the network device #1 starts recording the movement history information #2 may be different.

The network device #1 can determine whether the terminal device is changed to the cell #1 according to the following manner:

in the first mode, the network device #1 determines that the terminal device is replaced to the cell #1 when determining that the terminal device is successfully accessed in the cell #1 at random.

For example, if the terminal device adopts two-step random access, the network device #1 determines that the random access of the terminal device in the cell #1 is successful when the random access response signaling is sent to the terminal device.

For another example, if the terminal device adopts four-step random access, the network device #1 determines that the terminal device succeeds in random access in the cell #1 when the conflict resolution signaling is sent to the terminal device.

Further, the network device #1 may start recording the movement history information #2 at or after the timing at which it is determined that the terminal device succeeds in the random access of the cell #1.

In the second mode, when the network device #1 transmits a handover success (HO success) message to the terminal device, it is determined that the terminal device is changed to the cell #1.

Further, the network device #1 may start recording the movement history information #2 at or after the timing of transmitting the handover success message.

Mode three, network device #1 may determine that the terminal device is changed to cell #1 upon receiving the sequence number state transition (sequence number status transfer) message.

Further, the network device #1 may start recording the movement history information #2 at or after the time when the sequence number state transition message is received.

Optionally, after S210, the method 200 may further include S230: the network device #2 transmits the movement history information #3 to the network device # 1.

The movement history information #3 is movement history information of the terminal device recorded by the network device #2, and the movement history information #3 includes history information of the terminal device in the cell #2. For example, the movement history information #3 may include one or more of the following: CGI of cell #2, PCI of cell #2, center frequency point of cell #2, period #3 being a time for which the terminal device is waiting in cell #2.

As described earlier, the network device #1 may start recording the movement history information of the terminal device in the case where it is determined that the terminal device is changed to the cell #1, and accordingly, the network device #2 may stop recording the movement history information of the terminal device at the time of determining that the terminal device is changed to the cell #1 and transmit the recorded movement history information (i.e., movement history information # 3) of the terminal device to the network device # 1. Therefore, the period #3 included in the movement history information #3 is a time to be spent in the cell #2 before the terminal device is changed to the cell # 1.

Network device #2 may determine whether the terminal device is changed to cell #1 according to the following manner:

in the first embodiment, the network device #2 may determine that the terminal device is changed to the cell #1 at the time when the handover success message is received from the network device #1. That is, the network device #2 may stop recording the movement history information of the terminal device and transmit the movement history information #3 to the network device #1 at the time of receiving the handover success message.

Mode two, network device #2 may determine that the terminal device is changed to cell #1 at the time of transmitting the sequence number state transition message. That is, the network device #2 area may stop recording the movement history information of the terminal device at the time of transmitting the sequence number state transition message and transmit the movement history information #3 to the network device #1.

Alternatively, the network device #2 may send the movement history information #3 to the network device #1, carried in a sequence number state transition message; alternatively, the network device #2 may send the movement history information #3 to the network device #1 in other messages, for example, a new message may be defined.

Optionally, if in S201, the CHO request message sent by the network device #2 to the network device #1 carries the movement history information #1, after S210, the method 200 may further include: the network device #1 modifies the movement history information #1 in the case where it is determined that the terminal device is changed to the cell #1. Specifically, the network device #1 modifies the duration of the period #1 included in the movement history information #1, i.e., the network device #1 can compensate for the period from the reception of the CHO request message to the determination of the terminal device change to the cell #1 into the period #1.

As described above, under the CHO mechanism, the terminal device does not switch immediately after the network device #2 transmits the CHO request message to the network device #1, i.e., the terminal device may still stay in the cell #2, and the period #1 is the time the terminal device stays in the cell #2 before the network device #2 transmits the CHO request message, that is, the period #1 may not be the time the terminal device actually stays in the cell #2.

The time the terminal device actually waits in cell #2 is equal to period #1 plus the period of time that network device #2 sends a CHO request message to network device #2 to determine that the terminal device has changed to cell # 1. For example, the period #1 included in the movement history information #1 is t1, and the network device #2 transmits a CHO request message (or the network device #1 receives the CHO request message) to the period t2 for which it is determined that the terminal device is changed to the cell #1, the network device #1 may modify the period #1 to t1+t2.

Optionally, after S220, if the terminal device is changed from cell #1 to cell #3, the method 200 may further include S240: the network device #1 transmits the movement history information #2 to the network device #3 (an example of the third network device). Network device #3 is a network device to which cell #3 belongs. It will be appreciated that in the process of changing the terminal device from cell #1 to cell #3, cell #1 may be referred to as a source cell, network device #1 may be referred to as a source network device, and accordingly, cell #3 may be referred to as a target cell or candidate cell, and network device #3 may be referred to as a target network device.

According to the embodiment of the application, in the process that the terminal equipment executes CHO handover or RRC reestablishment, when the target network equipment (i.e., network equipment # 1) or the target cell (cell # 1) determines that the terminal equipment is replaced to the target cell, recording of movement history information of the terminal equipment is started, i.e., recording of history information of the terminal equipment in the target cell is started, so that more accurate movement history information of the terminal equipment can be recorded, and therefore the target network equipment can acquire more accurate movement conditions of the terminal equipment, so that some optimization can be performed more accurately.

In addition, the target network device may modify the time for the terminal device to stay in the source cell (cell # 2) received in the handover request message, that is, compensate the time for the terminal device to stay in the source cell after the terminal device successfully hands over to the target cell from the time for receiving the handover request message, so that the target network device may learn more accurate history information of the terminal device in the source cell, so as to perform some optimizations more accurately.

Fig. 3 is a schematic flow chart of a method 200 of communication provided by an embodiment of the present application, shown from the perspective of device interaction. The steps in method 300 are described in detail below.

S301, the network device #2 (an example of the second network device) transmits a handover request message to the network device #1 (an example of the first network device). Accordingly, in S301, the network device #1 receives a handover request message from the network device # 2.

Network device #2 is a network device to which cell #2 belongs, cell #2 is a cell that serves a terminal device before a DAPS handover, cell #2 may also be referred to as a source cell, and network device #2 may also be referred to as a source network device.

In S301, the cell #2 may transmit a handover request message to the cell # 1.

Alternatively, the handover request message may carry movement history information #1 (an example of the second movement history information).

The movement history information #1 is movement history information of the terminal device recorded by the network device #2 before the handover request message is transmitted, and the movement history information #1 includes history information of the terminal device in the cell # 2. For example, the movement history information #1 may include one or more of the following: CGI of cell #2, PCI of cell #2, center frequency point of cell #2, period #1 (an example of the third period), period #1 representing a time when the terminal device is waiting in cell # 2. Since the movement history information #1 is information recorded by the network device #2 before transmitting the handover request message, the movement history information #1 includes a period #1 that is a time for the terminal device to wait in the cell #2 before the network device #2 transmits the handover request message.

Optionally, the movement history information #1 may further include indication information #2, where the indication information #2 is used to instruct the terminal device to switch from the cell #2 to the cell #1 in a DAPS switching manner.

It will be appreciated that if network device #1 is the same network device as network device #2, the handover request message may not carry the movement history information #1.

S302, the network device #1 transmits a handover request confirm message to the network device # 2. Accordingly, in S302, the network device #2 receives the handover request confirm message from the network device #1.

The handover request confirm message includes RRC configuration information configured by the network device #1 for the terminal device. Specifically, the handover request confirm message includes RRC configuration information configured by the cell #1 for the terminal device. Optionally, the RRC configuration information may also carry indication information indicating which data radio bearers (Data Radio Bearer, DRBs) perform the DAPS operation, i.e. the DAPS handoff may be performed only on some DRBs, and other DRBs may still be processed according to the conventional handoff. For more description of RRC configuration information, reference may be made to the prior art, and for brevity, embodiments of the present application will not be repeated.

S303, the network device #2 transmits a handover command to the terminal device. Accordingly, in S303, the terminal device receives a handover command from the network device # 2.

The handover command sent by the network device #2 to the terminal device may be in the form of an RRC reconfiguration message, where the RRC reconfiguration message includes RRC configuration information configured by the network device #1 for the terminal device. Specifically, the RRC reconfiguration message includes RRC configuration information configured by the cell #1 for the terminal device.

S310, the terminal device changes to cell #1. Accordingly, in S310, the network device #1 determines that the terminal device is changed to the cell #1.

It should be understood that in S310, the terminal device is changed to cell #1, which means that the terminal device is successfully changed to cell #1, i.e., the terminal device successfully establishes a connection with cell #1.

The terminal device is replaced with the cell #1, which may be that the terminal device is successfully handed over from the cell #2 to the cell #1. The present application is not limited in this regard.

In S310, it may be that cell #1 determines that the terminal device is changed to cell #1.

At S320, the network device #1 starts recording movement history information #2 (an example of the first movement history information) at or after the time when it is determined that the terminal device is changed to the cell #1, the movement history information #2 being history information of the terminal device in the cell #1.

In S320, the cell #1 may start recording the movement history information #2 at or after the time when the terminal is determined to be changed to the cell #1.

Optionally, the movement history information #2 may further include indication information #3 (an example of third indication information), where the indication information #3 is used to instruct the terminal device to switch from the cell #1 to the cell #3 (an example of third cell) in a DAPS switching manner.

Optionally, the indication information #3 is also used to indicate a period #5, where the period #5 represents a duration in which the terminal device is to be in both cell #1 and cell #3 during the DAPS handover.

The network device #1 starts recording the movement history information #2 can be understood as that the network device #1 starts recording the time the terminal device is waiting in the cell #1. That is, the network device #1 considers that the terminal device starts to be in the cell #1 at or after the timing of determining that the terminal device is changed to the cell #1. Optionally, the network device #1 may also start recording the CGI of the cell #1 or the PCI and center frequency point of the cell #1. The present application does not limit the time when the network device #1 generates the movement history information #2. The network device #1 may generate the movement history information #2 after determining that the terminal device is handed over from the cell #1 to the other cell. The network device #1 starting to record the movement history information #2 can also be understood as the network device #1 starting to collect the movement history information #2. Recording movement history information in this application may be understood as collecting movement history information.

For example, if the terminal device adopts the two-step access method, the network device #1 determines that the terminal device has successfully accessed randomly in the cell #1 when a random access response signaling is sent to the terminal device.

For another example, if the terminal device adopts the four-step access method, the network device #1 determines that the terminal device has successfully accessed at the cell #1 at random, when the conflict resolution signaling is sent to the terminal device.

In the second aspect, when the network device #1 transmits instruction information #4 (an example of the first instruction information) to the terminal device, the network device determines that the terminal device is changed to the cell #1, and the instruction information #4 instructs the terminal device to disconnect from the cell #2. The instruction information #4 can also be used to instruct the terminal device to stop the DAPS operation at cell #2 and release the configuration information of the terminal device at cell #2.

Further, the network device #1 may start recording the movement history information #2 at or after the timing of transmitting the instruction information # 4.

In the third aspect, when the network device #1 transmits the instruction information #5 (an example of the second instruction information), it is determined that the terminal device is changed to the cell #1, and the instruction information #5 instructs the cell #2 or the network device #2 to release the context of the terminal device.

Further, the network device #1 may start recording the movement history information #2 at or after the timing of transmitting the instruction information # 5.

Optionally, if the network device #1 and the network device #2 are different network devices, after S310, the method 300 may further include S330: the network device #2 transmits the movement history information #3 to the network device 1.

The network device #2 may determine that the terminal device is changed to the cell #1 at the time of receiving the indication information # 5. That is, the network device #2 may stop recording the movement history information of the terminal device at the timing of receiving the instruction information #5, and transmit the movement history information #3 to the network device #1.

Optionally, the movement history information #3 may further include indication information #2, where the indication information #2 is used to instruct the terminal device to switch from the cell #2 to the cell #1 in a DAPS switching manner.

Optionally, the indication information #2 is also used to indicate a period #4, where the period #4 represents a duration in which the terminal device is to be in both cell #2 and cell #1 during the DAPS handover.

Optionally, if in S301, the handover request message sent by the network device #2 to the network device #1 carries the movement history information #1, after S310, the method 300 may further include: the network device #1 modifies the movement history information #1 in the case where it is determined that the terminal device is changed to the cell #1. Specifically, the network device #1 modifies the duration of the period #1 included in the movement history information #1, i.e., the network device #1 can compensate for the period from the reception of the handover request message to the replacement of the terminal device into the cell #1 into the period #1.

As described above, under the DAPS handoff mechanism, after the network device #2 transmits the handoff request message to the network device #1, the terminal device remains connected to the cell #2, and the period #1 is the time the terminal device was waiting in the cell #2 before the network device #2 transmits the handoff request message, that is, the period #1 may not be the time the terminal device was actually waiting in the cell #2.

The time the terminal device actually waits in cell #2 is equal to period #1 plus the time during which network device #2 sends a handover request message to the terminal device to change to cell # 1. For example, the period #1 included in the movement history information #1 is t1, and the period of time from when the network device #2 transmits the handover request message (or when the network device #1 receives the handover request message) to when the terminal device changes to the cell #1 is t2, the network device #1 may modify the period #1 to t1+t2.

Optionally, after S320, if the terminal device is changed from cell #1 to cell #3, the method 300 may further include S340: the network device #1 transmits the movement history information #2 to the network device #3 (an example of the third network device). Network device #3 is a network device to which cell #3 belongs. It will be appreciated that in the process of changing the terminal device from cell #1 to cell #3, cell #1 may be referred to as a source cell, network device #1 may be referred to as a source network device, and accordingly, cell #3 may be referred to as a target cell or candidate cell, and network device #3 may be referred to as a target network device.

According to the embodiment of the application, in the process that the terminal equipment executes DAPS switching or RRC reestablishment, under the condition that the terminal equipment is determined to be replaced to the target cell, the target network equipment (namely the network equipment # 1) or the target cell (the cell # 1) starts to record the movement history information of the terminal equipment, namely the history information of the terminal equipment in the target cell, so that the movement history information of the more accurate terminal equipment can be recorded, and the target network equipment can acquire the movement condition of the more accurate terminal equipment, so that some optimizations can be more accurately performed.

Fig. 4 is a schematic flow chart of a method 400 of communication provided by an embodiment of the present application, shown from the perspective of device interaction. The method illustrated in FIG. 4 is described by taking as an example a handoff of a terminal device from a source cell to a target cell using a DAPS handoff mechanism, and the steps in method 400 are described in detail below.

S401, the network device #2 transmits a handover request message to the network device #1.

S301 in the method 300 is not described in detail here.

S402, the network device #1 transmits a handover request confirm message to the network device # 2.

Like S302 in method 300, this is not described in detail herein.

S403, the network device #2 transmits a handover command to the terminal device.

Like S303 in method 300, it is not described in detail here.

S410, the terminal device changes to cell #1.

Like S310 in method 300, this is not described in detail herein.

S420, the terminal device records movement history information #4 at or after the time of determining handover from cell #2 (an example of the second cell) to cell #1 (an example of the first cell), the movement history information #4 being history information of the terminal device in cell # 2.

The movement history information #4 may include one or more of the following: CGI of cell #2, PCI of cell #2, center frequency point of cell #2, period #6 (an example of the fourth period), period #6 being a time when the terminal device is waiting in cell # 2.

The terminal device recording the movement history information #4 may be understood as that the terminal device adds the movement history information #4, i.e., adds the CGI of the cell #2 or the PCI and center frequency point of the cell #2, to one variable of the stored movement history information, and adds the period #6, and the period #6 may be a time to be spent in the cell #2 before the terminal device is replaced to the cell #1.

The embodiment of the present application does not limit how the terminal device determines whether to change from cell #2 to cell #1. It should be understood that, in different manners, the timing at which the terminal device determines that the handover to the cell #1 is successful may be different, and further, the timing at which the terminal device records the movement history information #4 may be different.

As one example, the terminal device determines that the handover from cell #2 to cell #1 is successful in the case where it is determined that the random access in cell #1 is successful.

For example, if the terminal device adopts two-step random access, the terminal device determines that the random access is successful in the cell #1 under the condition of receiving the random access response signaling.

For another example, if the terminal device adopts four-step random access, the terminal device determines that the terminal device succeeds in random access in the cell #1 under the condition that the terminal device receives the conflict resolution signaling.

Further, the terminal device may record the movement history information #4 at or after the timing of determining that the random access of the cell #1 is successful.

Optionally, the terminal device starts recording period #7 (an example of the fifth period) at the time when it is determined that the random access of cell #1 is successful, and period #7 is the time when the terminal device is waiting in cell #1. That is, before the random access of the terminal device in the cell #1 is successful, the terminal device is considered to be in the cell #2, and after the random access of the terminal device in the cell #1 is successful, the terminal device is considered to be in the cell #1.

As another example, the terminal device determines to change to the cell #1 upon receiving the instruction information #4 transmitted by the network device #1, the instruction information #4 being used to instruct the terminal device to disconnect from the cell # 2.

Further, the terminal device may record the movement history information #4 at or after the time when the instruction information #4 is received.

Alternatively, the terminal device starts the recording period #7 at the moment when it is determined that the cell #1 was randomly successful. That is, before the terminal device receives the instruction information #4, the terminal device is considered to be still in the cell #2, and after the terminal device determines that the random access in the cell #1 is successful, the terminal device is considered to be still in the cell #1. That is, the terminal device is considered to be in both cell #2 and cell #1 from the time when the terminal device determines that the random access in cell #1 is successful to the time when the indication information #4 is received. That is, the end point of the time to be received by the terminal device in the cell #2 is the terminal device receiving the indication information #4, and the start point of the time to be received by the terminal device in the cell #1 is the terminal device determining that the random access in the cell #1 is successful.

Alternatively, the terminal device starts the recording period #7 at the time of receiving the instruction information #4. That is, before the terminal device receives the indication information #4, the terminal device is considered to be in cell #2, and after the terminal device receives the indication information #4, the terminal device is considered to be in cell #1.

Alternatively, the movement history information #4 may further include indication information #6 for indicating that the terminal device switches from cell #2 to cell #1 using the DAPS switching mechanism.

Alternatively, the indication information #6 is also used to indicate a period #8 (an example of a sixth period), the period #8 representing a period in which the terminal device is to be in both the cell #2 and the cell #1 during DAPS handover.

Optionally, in the case that the terminal device re-accesses the cell #3 from the inactive state (inactive) or the idle state (idle), the method 400 may further include: s430, the terminal device transmits the movement history information #4 to the network device # 3. Network device #3 is a network device to which cell #3 belongs.

According to the embodiment of the application, in the process of performing handover by the terminal equipment, when the terminal equipment determines that the handover is successfully performed from the source cell (cell # 2) to the target cell (cell # 1), the history information (namely, the movement history information # 4) of the source cell is recorded, so that more accurate movement history information of the terminal equipment can be recorded, and the network equipment can acquire more accurate movement conditions of the terminal equipment, so that some optimizations can be performed more accurately.

To save data collection costs, minimization of drive tests (minimization of drive tests, MDT) techniques incorporating automated measurement collection (measurement collection) have been introduced in the prior art to accomplish part of the conventional drive test work to detect and optimize problems or faults in wireless networks. The application scenario of the MDT technology may include, for example: operators typically do a routine network coverage test every month, or do some network coverage test for a specific area for customer complaints, etc.

Currently, MDT techniques may be applied to automatic measurement collection of base stations, such as quality of service (quality of service, qoS) measurement collection, cell signal quality measurement collection, or accessibility measurement collection, etc. The measurement types of MDT techniques can be divided into the following:

first, signal level measurement: the terminal device measures the signal level of the radio signal, such as the reference signal received power (reference signal receiving power, RSRP) or the reference signal received quality (reference signal receiving quality, RSRQ), and reports the measurement collection result to the network device.

Second, qoS measurement (QoS measurement): qoS measurements are typically performed by network devices such as traffic of the traffic, internet protocol (internet protocol, IP) throughput of the traffic, packet loss rate of the traffic, or processing delay of the traffic, etc.; of course, qoS measurement may also be performed by the terminal device, such as uplink processing delay, which is not specifically limited in the embodiments of the present application.

Third, accessibility measurement (accessibility measurement): the terminal device records information such as random access channel (random access channel, RACH) failure statistics, radio link failure (radio link failure, RLF) statistics, RRC connection access failure statistics, etc., and reports the information to the network device.

The MDT includes a record MDT (logged MDT) (or referred to as log MDT) and an immediate MDT (immediate MDT). The Immediate MDT mainly aims at measurement collection of terminal equipment in an RRC connection state (RRC_CONNECTED), and the logged MDT mainly aims at measurement collection of terminal equipment in an IDLE state (RRC_IDLE) or terminal equipment in an RRC INACTIVE state (RRC_INACTIVE) (for example, the terminal equipment in the IDLE state or the terminal equipment in the INACTIVE state measures a cell of a frequency point corresponding to a currently resident cell and a different frequency/different system neighbor cell corresponding to cell reselection broadcasted in the currently resident cell, and the terminal equipment records and reports measurement results). The Immediate MDT is generally used to measure the data volume, IP throughput, packet transmission delay, packet loss rate, processing delay, etc. of the terminal device. While the logged MDT generally refers to a measurement of the received signal strength by the UE.

The wireless system also defines some layer 2 measurements for the network side to count some network performances so as to perform functions of wireless link management, wireless resource management, network maintenance and the like. Some of the layer 2 measurements are counted for one terminal device, such as throughput of service, traffic of service, processing delay of the terminal device, air interface delay of the terminal device, etc.

In both scenarios, the access network device may initiate an MDT measurement collection task. One is signaling-based MDT (signalling based MDT) and one is management-based MDT (management based MDT). The MDT based on signaling refers to an MDT for a specific terminal device, and the access network device receives a message for MDT for a specific terminal device from a Core Network (CN). The management-based MDT is not an MDT for a specific terminal device, and the access network device receives a message for MDT from an operation and maintenance manager (operation administration and maintenance, OAM) or an Element Manager (EM). For MDT based on management, the access network equipment selects terminal equipment from terminal equipment under the access network equipment based on a certain policy to collect MDT measurement. For signaling-based MDT, the CN does not initiate signaling MDT for the UE unless the user has agreed to MDT. For management-based MDT, the access network device may consider whether the terminal device agrees to perform MDT when selecting the terminal device, such as selecting only those terminal devices that have agreed to perform MDT for MDT measurement collection. In a CU/DU architecture, OAM may send management-based MDT measurement collection tasks independently to CU-CP/CU-UP/CU-DU. For the MDT measurement collection task based on signaling, if a task corresponding to a measurement type needed in the MDT measurement collection task needs to participate in a CU-UP/DU, when the CU-CP receives the MDT measurement collection task from the CN, the CU-CP sends the corresponding measurement task to the CU-UP or the DU, so that the CU-UP or the DU is triggered to conduct MDT measurement. After receiving the MDT measurement result, the access network device or CU-CP/CU-UP/DU sends the MDT measurement result to a trace collection entity (trace collection entity, TCE)

In practice, the terminal device may detect coexistence problems (In-Device Coexistence, IDC) within the device while making MDT measurements. The IDC problem refers to that the terminal device detects interference problems in some subframes/slots when wirelessly communicating with the network side device. For those frequency points corresponding to the activated serving cells, the IDC problem means that the terminal equipment cannot solve the interference problems by itself. For those frequency points corresponding to serving cells that are not active, the IDC problem refers to the fact that the terminal device is expected to monitor the interference problem and cannot solve itself when the serving cells are active. For the frequency points corresponding to the non-serving cells, the IDC problem refers to that when the frequency points corresponding to the non-serving cells become the frequency points corresponding to the serving cells, the terminal equipment can monitor the interference problem and cannot solve the interference problem. These IDC problems may affect the communication performance of the terminal device. If the network device cannot know whether the terminal device detects IDC problems when collecting the MDT measurement results, an erroneous conclusion may be obtained when analyzing the MDT measurement results (for example, IDC interference may affect the accuracy of the MDT measurement results, if IDC interference is detected, the quality of the wireless signal of the cell in the base station may be reduced in the MDT measurement results, so that the actual wireless performance cannot be reflected).

Based on this, the embodiment of the application provides a communication method, which can realize that the MDT measurement result and the IDC result acquired by the CU-CP/CU-UP/DU are associated under the CU/DU architecture.

Fig. 5 illustrates a method of communication provided by an embodiment of the present application, and as illustrated, method 500 may include S501 and S502, and the steps are described in detail below.

S501, the DU or CU-UP sends a cell traffic trace (cell traffic trace) message to the CU-CP. Accordingly, in S501, the CU-CP receives the cell traffic trace message from the DU or CU-UP.

It can be appreciated that the names of the cell service tracking messages are given by way of example, and the embodiment of the present application does not limit the message names. The message carries the tracking identifier and the TCE IP address. The trace identification may include a trace reference (trace reference) and a trace record session reference (trace recording session reference), among others. Optionally, the cell service tracking message may also carry a request message for requesting the CU-CP to report IDC information detected by the terminal device.

Optionally, the DU or CU-UP may send the corresponding MDT measurement to the TCE after obtaining the corresponding MDT measurement result when performing the MDT measurement.

Optionally, when the DU or CU-UP sends the MDT measurement results to the TCE, the DU or CU-UP also carries time information corresponding to the collection of the MDT measurement results (such as start time and end time of the MDT measurement corresponding to the MDT measurement results).

S502, the CU-CP sends IDC information to the TCE or the CN.

Here, the CU-CP may transmit IDC information directly to the TCE or transmit IDC information to the TCE through the CN.

After receiving the cell service tracking message from the DU or CU-UP, the CU-CP transmits IDC information detected by the terminal device to the TCE or CN.

It can be understood that, in the case that the cell service trace message carries a request message requesting to report IDC information detected by the terminal device, the CU-CP transmits IDC information to the TCE or CN. The CU-CP may also actively send IDC information to the TCE or CN, which is not limited by the embodiment of the present application. That is, S501 is an optional step.

Optionally, the CU-CP may learn, from a message received from the terminal device, information that the terminal device detects IDC interference. For example, the terminal device sends an RRC message (such as a terminal device side information message) to the CU-CP, where the RRC message includes information for determining whether IDC interference is detected (such as a boolean variable carried in the RRC message, which represents that the terminal device detects IDC interference when the value is 1, and represents that the terminal device does not detect IDC interference when the value is 0). Optionally, the RRC message may also include frequency point information corresponding to a frequency point indicating that IDC interference is detected or frequency point information indicating that IDC interference is affected. That is, the terminal device may indicate to the network device whether interference is detected and at which frequency points IDC problems are detected (e.g., the RRC message carries a list of frequency points, representing IDC problems detected in these frequency points). Optionally, the RRC message may further include information about the direction in which IDC interference is detected, where the direction of IDC interference may refer to who is the victim of IDC interference compared to NR, or other wireless (such as industrial, scientific, and medical frequency band (scientific and medical band) or global navigation satellite system (global navigation satellite system, GNSS)) is the victim of IDC interference.

Alternatively, the terminal device may send the RRC message to the network device based on a notification or an indication of the network device. For example, the network device notifies or indicates, through a message or an instruction, which frequency points need to be reported by the terminal device are subjected to IDC interference, and when the terminal device detects IDC interference, the terminal device reports that the frequency points are subjected to IDC interference to the network device.

Optionally, IDC information detected by the terminal device sent by the CU-CP to the TCE or CN includes at least one of the following: whether the terminal device detects IDC, at which cells the terminal device detects IDC at which corresponding frequency points, start time and end time of IDC are detected (or duration length of IDC is detected). It should be noted that, it is possible that the terminal device may not continuously detect IDC, that is, may detect IDC for a certain period of time, then may not detect IDC for a certain period of time, and then may detect IDC again for a certain period of time. The CU-CP may send a plurality of start times and end times of the detected IDCs (or duration of the detected IDCs).

Alternatively, the CU-CP may carry IDC information in a cell traffic tracking message sent to the CN. After the CN receives the IDC information, the CN sends the corresponding IDC information to the TCE.

When the CU-CP performs MDT measurement, after obtaining the corresponding MDT measurement result, the CU-CP sends the corresponding MDT measurement result to the TCE.

The TCE knows whether the corresponding MDT measurement result is affected by IDC interference according to the MDT measurement result received from the CU-CP or DU or CU-UP, and the received IDC information, and the time information corresponding to the MDT measurement result.

According to the embodiment of the application, in the CU/DU architecture, the CU-CP or the CU-UP or the DU sends MDT measurement results to the TCE, and meanwhile, the TCE can obtain whether the MDT measurement results are affected by IDC interference or not, so that the MDT measurement results can be analyzed more accurately.

It should be understood that in the above embodiments, the terminal device and/or the network device may perform some or all of the steps in the embodiments. These steps or operations are merely examples, and embodiments of the present application may also perform other operations or variations of the various operations. Furthermore, the various steps may be performed in a different order presented by the various embodiments, and it is possible that not all of the operations in the embodiments of the present application may be performed. The sequence number of each step does not mean the sequence of execution sequence, and the execution sequence of each process should be determined by its function and internal logic, and should not constitute any limitation to the implementation process of the embodiments of the present application.

Fig. 6 is a schematic block diagram of a communication device provided in an embodiment of the present application. As shown in fig. 6, the communication apparatus 1000 may include a processing unit 1100 and a transceiving unit 1200.

Alternatively, the communication apparatus 1000 may correspond to the terminal device in the above method embodiment, for example, may be a terminal device, or a component (such as a circuit, a chip, or a chip system) configured in the terminal device.

It is to be understood that the communication apparatus 1000 may correspond to the terminal device in the methods 200 to 400 according to embodiments of the present application, and that the communication apparatus 1000 may comprise means for performing the method 200 in fig. 2, the method 300 in fig. 3, the method 400 in fig. 4, and the method performed by the terminal device. And, each unit in the communication device 1000 and the other operations and/or functions described above are respectively for implementing the corresponding flows of the method 200 in fig. 2, the method 300 in fig. 3, and the method 400 in fig. 4. It should be understood that the specific process of each unit performing the corresponding steps has been described in detail in the above method embodiments, and is not described herein for brevity.

It should be understood that when the communication apparatus 1000 is a terminal device, the transceiver unit 1200 in the communication apparatus 1000 may be implemented by a transceiver, for example, may correspond to the transceiver 2020 in the communication apparatus 2000 shown in fig. 7 or the transceiver 3020 in the terminal device 3000 shown in fig. 8. The processing unit 1100 in the communication device 1000 may be implemented by at least one processor, and may correspond to the processor 2010 in the communication device 2000 shown in fig. 7 or the processor 3010 in the terminal device 3000 shown in fig. 8, for example.

It should be further understood that, when the communication device 1000 is a chip or a chip system configured in a terminal device, the transceiver unit 1200 in the communication device 1000 may be implemented by an input/output interface, a circuit, etc., and the processing unit 1100 in the communication device 1000 may be implemented by a processor, a microprocessor, an integrated circuit, etc. integrated on the chip or the chip system.

Alternatively, the communication apparatus 1000 may correspond to the network device in the above method embodiment, for example, may be a network device, or may be a component (such as a circuit, a chip, or a chip system) configured in the network device.

It is to be understood that the communication apparatus 1000 may correspond to the network device in the methods 200 to 400 according to the embodiments of the present application, and the communication apparatus 1000 may include units for performing the method 200 in fig. 2, the method 300 in fig. 3, the method 400 in fig. 4, and the method performed by the network device. And, each unit in the communication device 1000 and the other operations and/or functions described above are respectively for implementing the corresponding flows of the method 200 in fig. 2, the method 300 in fig. 3, and the method 400 in fig. 4. It should be understood that the specific process of each unit performing the corresponding steps has been described in detail in the above method embodiments, and is not described herein for brevity.

It should be understood that when the communication apparatus 1000 is a network device, the transceiver unit 1200 in the communication apparatus 1000 may be implemented by a transceiver, for example, may correspond to the transceiver 2020 in the communication apparatus 2000 shown in fig. 7 or the RRU 4100 in the base station 4000 shown in fig. 9, and the processing unit 1100 in the communication apparatus 1000 may be implemented by at least one processor, for example, may correspond to the processor 2010 in the communication apparatus 2000 shown in fig. 7 or the processing unit 4200 or the processor 4202 in the base station 4000 shown in fig. 8.

It should be further understood that, when the communication apparatus 1000 is a chip or a chip system configured in a network device, the transceiver unit 1200 in the communication apparatus 1000 may be implemented by an input/output interface, a circuit, etc., and the processing unit 1100 in the communication apparatus 1000 may be implemented by a processor, a microprocessor, an integrated circuit, etc. integrated on the chip or the chip system.

Alternatively, the communication device 1000 may correspond to the DU in the above method embodiment, for example, may be a DU, or a component (such as a circuit, a chip, or a chip system) configured in the DU.

It is to be understood that the communication device 1000 may correspond to a DU in the method 500 according to an embodiment of the present application, and the communication device 1000 may include a unit for performing the method performed by the DU in the method 500 in fig. 5. And, each unit in the communication device 1000 and the other operations and/or functions described above are respectively for implementing the corresponding flow of the method 500 in fig. 5. It should be understood that the specific process of each unit performing the corresponding steps has been described in detail in the above method embodiments, and is not described herein for brevity.

Alternatively, the communication device 1000 may correspond to the CU-UP in the above method embodiment, for example, may be the CU-UP, or a component (such as a circuit, a chip, or a chip system, etc.) configured in the CU-UP.

It is to be appreciated that the communication device 1000 may correspond to a CU-UP in the method 500 according to an embodiment of the present application, and that the communication device 1000 may include means for performing the method performed by the CU-UP in the method 500 in fig. 5. And, each unit in the communication device 1000 and the other operations and/or functions described above are respectively for implementing the corresponding flow of the method 500 in fig. 5. It should be understood that the specific process of each unit performing the corresponding steps has been described in detail in the above method embodiments, and is not described herein for brevity.

Alternatively, the communication device 1000 may correspond to the CU-CP in the above method embodiment, for example, may be the CU-CP, or a component (such as a circuit, a chip, or a chip system, etc.) configured in the CU-CP.

It is to be understood that the communication apparatus 1000 may correspond to the DU in the method 500 according to an embodiment of the present application, and the communication apparatus 1000 may include a unit for performing the method performed by the CU-CP in the method 500 in fig. 5. And, each unit in the communication device 1000 and the other operations and/or functions described above are respectively for implementing the corresponding flow of the method 500 in fig. 5. It should be understood that the specific process of each unit performing the corresponding steps has been described in detail in the above method embodiments, and is not described herein for brevity.

Alternatively, the communication device 1000 may correspond to the TCE in the above method embodiments, for example, may be a TCE, or a component (such as a circuit, a chip, or a chip system) configured in the TCE.

It is to be understood that the communication device 1000 may correspond to the TCE in the method 500 according to an embodiment of the present application, and that the communication device 1000 may comprise means for performing the method performed by the TCE in the method 500 in fig. 5. And, each unit in the communication device 1000 and the other operations and/or functions described above are respectively for implementing the corresponding flow of the method 500 in fig. 5. It should be understood that the specific process of each unit performing the corresponding steps has been described in detail in the above method embodiments, and is not described herein for brevity.

Alternatively, the communication device 1000 may correspond to the CN in the above method embodiments, for example, may be the CN, or a component (such as a circuit, a chip, or a chip system) configured in the CN.

It should be understood that the communication device 1000 may correspond to a CN in the method 500 according to an embodiment of the present application, and the communication device 1000 may include a unit for performing the method performed by the CN in the method 500 in fig. 5. And, each unit in the communication device 1000 and the other operations and/or functions described above are respectively for implementing the corresponding flow of the method 500 in fig. 5. It should be understood that the specific process of each unit performing the corresponding steps has been described in detail in the above method embodiments, and is not described herein for brevity.

Fig. 7 is another schematic block diagram of a communication device 2000 provided by an embodiment of the present application. As shown in fig. 7, the communication device 2000 includes a processor 2010, a transceiver 2020, and a memory 2030. Wherein the processor 2010, the transceiver 2020, and the memory 2030 are in communication with each other through an internal connection path, the memory 2030 is for storing instructions, and the processor 2010 is for executing the instructions stored in the memory 2030 to control the transceiver 2020 to transmit signals and/or receive signals.

It should be understood that the communication apparatus 2000 may correspond to a terminal device in the above-described method embodiment and may be used to perform various steps and/or procedures performed by a network device or a terminal device in the above-described method embodiment. Alternatively, the memory 2030 may include read only memory and random access memory and provide instructions and data to the processor. A portion of the memory may also include non-volatile random access memory. The memory 2030 may be a separate device or may be integrated within the processor 2010. The processor 2010 may be configured to execute instructions stored in the memory 2030 and when the processor 2010 executes the instructions stored in the memory, the processor 2010 is configured to perform the steps and/or flow of the method embodiments described above corresponding to the network device or the terminal device.

Alternatively, the communication apparatus 2000 is the terminal device in the foregoing embodiment.

Optionally, the communication apparatus 2000 is a network device in the foregoing embodiment.

The transceiver 2020 may include a transmitter and a receiver, among other things. The transceiver 2020 may further include antennas, the number of which may be one or more. The processor 2010 and memory 2030 may be separate devices integrated on different chips than the transceiver 2020. For example, the processor 2010 and the memory 2030 may be integrated in a baseband chip and the transceiver 2020 may be integrated in a radio frequency chip. The processor 2010 and memory 2030 may also be integrated on the same chip as the transceiver 2020. The present application is not limited in this regard.

Alternatively, the communication device 2000 is a component configured in a terminal device, such as a circuit, a chip system, or the like.

Alternatively, the communication apparatus 2000 is a component configured in a network device, such as a circuit, a chip system, or the like.

Alternatively, the communication device 2000 is a component configured in a DU, such as a circuit, a chip system, or the like.

Alternatively, the communication device 2000 is a component configured in CU-UP, such as a circuit, chip, system-on-chip, or the like.

Alternatively, the communication device 2000 is a component, such as a circuit, chip, system-on-chip, etc., configured in the CU-CP.

Alternatively, the communication device 2000 is a component configured in a TCE, such as a circuit, chip, system-on-chip, or the like.

Alternatively, the communication device 2000 is a component configured in the CN, such as a circuit, a chip system, or the like.

The transceiver 2020 may also be a communication interface such as an input/output interface, circuitry, etc. The transceiver 2020 may be integrated in the same chip as the processor 2010 and the memory 2020, e.g., in a baseband chip.

Fig. 8 is a schematic structural diagram of a terminal device 3000 provided in an embodiment of the present application. The terminal device 3000 may be applied to a system as shown in fig. 1, and perform the functions of the terminal device in the above-described method embodiment. As shown, the terminal device 3000 includes a processor 3010 and a transceiver 3020. Optionally, the terminal device 3000 further comprises a memory 3030. Wherein the processor 3010, the transceiver 3020 and the memory 3030 may communicate with each other via an internal connection path for transferring control and/or data signals, the memory 3030 is used for storing a computer program, and the processor 3010 is used for calling and running the computer program from the memory 3030 to control the transceiver 3020 to send and receive signals. Optionally, the terminal device 3000 may further include an antenna 3040, for sending uplink data or uplink control signaling output by the transceiver 3020 through a wireless signal.

The processor 3010 and the memory 3030 may be combined into one processing device, and the processor 3010 is configured to execute program codes stored in the memory 3030 to implement the functions described above. In particular implementations, the memory 3030 may also be integrated into the processor 3010 or independent of the processor 3010. The processor 3010 may correspond to the processing unit 1100 of fig. 6 or the processor 2010 of fig. 7.

The transceiver 3020 may correspond to the transceiver unit 1200 in fig. 6 or the transceiver 2020 in fig. 7. The transceiver 3020 may include a receiver (or receiver, receiving circuitry) and a transmitter (or transmitter, transmitting circuitry). Wherein the receiver is for receiving signals and the transmitter is for transmitting signals.

It should be understood that the terminal device 3000 shown in fig. 8 is capable of implementing the various processes involving the terminal device in the method embodiments shown in fig. 2-4. The operations and/or functions of the respective modules in the terminal device 3000 are respectively for implementing the respective flows in the above-described method embodiments. Reference is specifically made to the description in the above method embodiments, and detailed descriptions are omitted here as appropriate to avoid repetition.

The above-described processor 3010 may be used to perform actions described in the foregoing method embodiments as being implemented internally by the terminal device, and the transceiver 3020 may be used to perform actions described in the foregoing method embodiments as being transmitted to or received from the network device by the terminal device. Please refer to the description of the foregoing method embodiments, and details are not repeated herein.

Optionally, the terminal device 3000 may further include a power source 3050 for providing power to various devices or circuits in the terminal device.

In addition to this, in order to make the functions of the terminal device more complete, the terminal device 3000 may further include one or more of an input unit 3060, a display unit 3070, an audio circuit 3080, a camera 3090, a sensor 3100, etc., and the audio circuit may further include a speaker 3082, a microphone 3084, etc.

Fig. 9 is a schematic structural diagram of a network device provided in the embodiment of the present application, for example, may be a schematic structural diagram of a base station. The base station 4000 may be applied to the system shown in fig. 1 to perform the functions of the network device in the above-described method embodiment. As shown, the base station 4000 may include one or more radio frequency units, such as a remote radio frequency unit (remote radio unit, RRU) 4100 and one or more baseband units (BBUs) (also referred to as Distributed Units (DUs)) 4200. The RRU 4100 may be referred to as a transceiver unit and may correspond to the transceiver unit 1200 in fig. 6 or the transceiver 2020 in fig. 7. Alternatively, the RRU 4100 may also be referred to as a transceiver, transceiving circuitry, or transceiver, etc., which may include at least one antenna 4101 and a radio frequency unit 4102. Alternatively, the RRU 4100 may include a receiving unit, which may correspond to a receiver (or receiver, receiving circuit), and a transmitting unit, which may correspond to a transmitter (or transmitter, transmitting circuit). The RRU 4100 part is mainly used for receiving and transmitting radio frequency signals and converting radio frequency signals into baseband signals, for example, for sending indication information to a terminal device. The BBU 4200 portion is mainly used for baseband processing, control of a base station, and the like. The RRU 4100 and BBU 4200 may be physically located together or may be physically separate, i.e., distributed base stations.

The BBU 4200 is a control center of the base station, and may also be referred to as a processing unit, and may correspond to the processing unit 1100 in fig. 6 or the processor 2010 in fig. 7, and is mainly configured to perform baseband processing functions, such as channel coding, multiplexing, modulation, spreading, and so on. For example, the BBU (processing unit) may be configured to control the base station to perform the operation procedure with respect to the network device in the above-described method embodiment, for example, generate the above-described indication information, etc.

In one example, the BBU 4200 may be formed by one or more single boards, where the multiple single boards may support a single access radio access network (such as an LTE network) together, or may support different access radio access networks (such as an LTE network, a 5G network, or other networks) respectively. The BBU 4200 also includes a memory 4201 and a processor 4202. The memory 4201 is used to store necessary instructions and data. The processor 4202 is configured to control the base station to perform necessary actions, for example, to control the base station to perform the operation procedures related to the network device in the above-described method embodiment. The memory 4201 and processor 4202 may serve one or more boards. That is, the memory and the processor may be separately provided on each board. It is also possible that multiple boards share the same memory and processor. In addition, each single board can be provided with necessary circuits.

It should be appreciated that the base station 4000 shown in fig. 9 is capable of implementing various processes involving network devices in the method embodiments shown in fig. 2-4. The operations and/or functions of the respective modules in the base station 4000 are respectively for implementing the corresponding procedures in the above-described method embodiments. Reference is specifically made to the description in the above method embodiments, and detailed descriptions are omitted here as appropriate to avoid repetition.

The BBU 4200 described above may be used to perform actions described in the previous method embodiments as being implemented internally by the network device, while the RRU 4100 may be used to perform actions described in the previous method embodiments as being transmitted to or received from the terminal device by the network device. Please refer to the description of the foregoing method embodiments, and details are not repeated herein.

It should be understood that the base station 4000 shown in fig. 9 is only one possible configuration of a network device and should not be construed as limiting the present application. The method provided by the application can be applied to network equipment in other forms. For example, including AAUs, but also CUs and/or DUs, or BBUs and adaptive radio units (adaptive radio unit, ARUs), or BBUs; the network device may be a customer premise equipment (customer premises equipment, CPE), or may be in other forms, and the specific form of the network device is not limited in the present application.

Wherein a CU and/or DU may be used to perform actions described in the previous method embodiments as being implemented internally by a network device, and an AAU may be used to perform actions described in the previous method embodiments as being transmitted to or received from a terminal device by the network device. Please refer to the description of the foregoing method embodiments, and details are not repeated herein.

The application also provides a processing device, which comprises at least one processor, and the at least one processor is used for executing a computer program stored in a memory, so that the processing device executes the method executed by the terminal equipment or the network equipment in any method embodiment.

The embodiment of the application also provides a processing device which comprises a processor and a communication interface. The communication interface is coupled with the processor. The communication interface is used for inputting and/or outputting information. The information includes at least one of instructions and data. The processor is configured to execute a computer program, so that the processing apparatus performs a method performed by the terminal device or the network device in any of the method embodiments described above.

The embodiment of the application also provides a processing device, which comprises a processor and a memory. The memory is used for storing a computer program, and the processor is used for calling and running the computer program from the memory, so that the processing device executes the method executed by the terminal device or the network device in any method embodiment.

It should be understood that the processing means described above may be one or more chips. For example, the processing device may be a field programmable gate array (field programmable gate array, FPGA), an application specific integrated chip (application specific integrated circuit, ASIC), a system on chip (SoC), a central processing unit (central processor unit, CPU), a network processor (network processor, NP), a digital signal processing circuit (digital signal processor, DSP), a microcontroller (micro controller unit, MCU), a programmable controller (programmable logic device, PLD) or other integrated chip.

In implementation, the steps of the above method may be performed by integrated logic circuits of hardware in a processor or by instructions in the form of software. The steps of a method disclosed in connection with the embodiments of the present application may be embodied directly in a hardware processor for execution, or in a combination of hardware and software modules in the processor for execution. The software modules may be located in a random access memory, flash memory, read only memory, programmable read only memory, or electrically erasable programmable memory, registers, etc. as well known in the art. The storage medium is located in a memory, and the processor reads the information in the memory and, in combination with its hardware, performs the steps of the above method. To avoid repetition, a detailed description is not provided herein.

It should be noted that the processor in the embodiments of the present application may be an integrated circuit chip with signal processing capability. In implementation, the steps of the above method embodiments may be implemented by integrated logic circuits of hardware in a processor or instructions in software form. The processor may be a general purpose processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other programmable logic device, discrete gate or transistor logic, or discrete hardware components. The disclosed methods, steps, and logic blocks in the embodiments of the present application may be implemented or performed. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of a method disclosed in connection with the embodiments of the present application may be embodied directly in hardware, in a decoded processor, or in a combination of hardware and software modules in a decoded processor. The software modules may be located in a random access memory, flash memory, read only memory, programmable read only memory, or electrically erasable programmable memory, registers, etc. as well known in the art. The storage medium is located in a memory, and the processor reads the information in the memory and, in combination with its hardware, performs the steps of the above method.

It will be appreciated that the memory in embodiments of the present application may be either volatile memory or nonvolatile memory, or may include both volatile and nonvolatile memory. The nonvolatile memory may be a read-only memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an electrically Erasable EPROM (EEPROM), or a flash memory. The volatile memory may be random access memory (random access memory, RAM) which acts as an external cache. By way of example, and not limitation, many forms of RAM are available, such as Static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), synchronous DRAM (SLDRAM), and direct memory bus RAM (DR RAM). It should be noted that the memory of the systems and methods described herein is intended to comprise, without being limited to, these and any other suitable types of memory.

According to the method provided by the embodiment of the application, the application further provides a computer program product, which comprises: computer program code which, when run on a computer, causes the computer to perform the method performed by the terminal device or the method performed by the network device in the embodiments shown in fig. 2 to 5.

According to the method provided in the embodiments of the present application, there is further provided a computer readable storage medium storing a program code, which when executed on a computer, causes the computer to perform the method performed by the terminal device or the method performed by the network device in the embodiments shown in fig. 2 to 5.

According to the method provided by the embodiment of the application, the application further provides a system, which comprises one or more of the terminal devices and one or more of the network devices.

The network device in the above-mentioned respective apparatus embodiments corresponds entirely to the network device or the terminal device in the terminal device and method embodiments, the respective steps are performed by respective modules or units, for example, the steps of receiving or transmitting in the method embodiments are performed by the communication unit (transceiver), and other steps than transmitting and receiving may be performed by the processing unit (processor). Reference may be made to corresponding method embodiments for the function of a specific unit. Wherein the processor may be one or more.

In the above embodiments, the terminal device may be an example of the receiving device, and the network device may be an example of the transmitting device. But this should not constitute any limitation to the present application. For example, the transmitting apparatus and the receiving apparatus may be both terminal apparatuses or the like. The present application is not limited to a specific type of transmitting apparatus and receiving apparatus.

As used in this specification, the terms "component," "module," "system," and the like are intended to refer to a computer-related entity, either hardware, firmware, a combination of hardware and software, or software in execution. For example, a component may be, but is not limited to being, a process running on a processor, an object, an executable, a thread of execution, a program, and/or a computer. By way of illustration, both an application running on a computing device and the computing device can be a component. One or more components may reside within a process and/or thread of execution and a component may be localized on one computer and/or distributed between 2 or more computers. Furthermore, these components can execute from various computer readable media having various data structures stored thereon. The components may communicate by way of local and/or remote processes such as in accordance with a signal having one or more data packets (e.g., data from two components interacting with one another in a local system, distributed system, and/or across a network such as the internet with other systems by way of the signal).

Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

It will be clear to those skilled in the art that, for convenience and brevity of description, specific working procedures of the above-described systems, apparatuses and units may refer to corresponding procedures in the foregoing method embodiments, and are not repeated herein.

In the several embodiments provided in this application, it should be understood that the disclosed systems, devices, and methods may be implemented in other manners. For example, the apparatus embodiments described above are merely illustrative, e.g., the division of the units is merely a logical function division, and there may be additional divisions when actually implemented, e.g., multiple units or components may be combined or integrated into another system, or some features may be omitted or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices or units, which may be in electrical, mechanical or other form.

The units described as separate units may or may not be physically separate, and units shown as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

In addition, each functional unit in each embodiment of the present application may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit.

The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer-readable storage medium. Based on such understanding, the technical solution of the present application may be embodied essentially or in a part contributing to the prior art or in a part of the technical solution, in the form of a software product stored in a storage medium, including several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the methods described in the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a read-only memory (ROM), a random access memory (random access memory, RAM), a magnetic disk, or an optical disk, or other various media capable of storing program codes.

The foregoing is merely specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily think about changes or substitutions within the technical scope of the present application, and the changes and substitutions are intended to be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

A method of communication, comprising:

the first network equipment determines that the terminal equipment is changed to a first cell, wherein the change comprises dual-activation protocol stack DAPS switching, conditional switching CHO or radio resource control RRC reestablishment;

the first network device starts recording first movement history information at or after the moment when the terminal device is determined to be replaced to the first cell, wherein the first movement history information is the history information of the terminal device in the first cell.
The method of claim 1, wherein the first network device determining that the terminal device is changed to the first cell comprises:

the first network equipment determines that the terminal equipment is replaced to the first cell under the condition that the terminal equipment is successfully accessed in the first cell at random;

The first network device starting recording first movement history information at or after determining a time when the terminal device is changed to the first cell includes:

the first network device starts recording the first movement history information after or at the moment when the terminal device is determined to be successful in the random access of the first cell.
The method of claim 1, wherein if the change is a DAPS handoff, the first network device determining that a terminal device is changed to a first cell comprises:

the first network equipment determines that the terminal equipment is replaced to the first cell under the condition that first indication information is sent, wherein the first indication information is used for indicating the terminal equipment to disconnect from a second cell;

the first network device starting recording first movement history information at or after determining a time when the terminal device is changed to the first cell includes:

the first network device starts recording the first movement history information at or after the time when the first instruction information is transmitted.
The method of claim 1, wherein if the change is a DAPS handoff, the first network device determining that a terminal device is changed to a first cell comprises:

The first network device determines that the terminal device is replaced to the first cell under the condition that second indication information is sent, wherein the second indication information is used for indicating a second cell or a second network device to release the context of the terminal device;

the first network device starting recording first movement history information at or after determining a time when the terminal device is changed to the first cell includes:

the first network device starts recording the first movement history information at or after the time when the second instruction information is transmitted.
The method according to any one of claims 1 to 4, wherein the first movement history information further comprises third indication information for indicating that the terminal device is handed over from the first cell to a third cell in a DAPS handover manner.
The method of claim 5, wherein the third indication information is further for indicating a first time period, the first time period representing a duration for which a terminal device is to be in both the first cell and the third cell during a DAPS handoff.
The method of claim 1, wherein if the change is CHO, the first network device determining that the terminal device is changed to the first cell comprises:

The first network equipment determines that the terminal equipment is replaced to the first cell under the condition that the first network equipment sends a switching success message;

the first network device starting recording first movement history information at or after determining a time when the terminal device is changed to the first cell includes:

the first network device starts recording the first movement history information at or after the time when the handover success message is transmitted.
The method of claim 1, wherein if the change is CHO, the first network device determining that the terminal device is changed to the first cell comprises:

the first network equipment determines that the terminal equipment is replaced to the first cell under the condition that the first network equipment receives a serial number state transition message;

the first network device starting recording first movement history information at or after determining a time when the terminal device is changed to the first cell includes:

the first network device starts recording the first movement history information at or after the moment when the serial number state transition message is received.
The method according to any one of claims 1 to 8, further comprising:

The first network device sends the first movement history information to a third network device, wherein the first movement history information comprises a second period of time, and the second period of time is the duration that the terminal device waits in the first cell.
The method according to any of claims 1 to 8, wherein before the first network device determines that a terminal device is changed to a first cell, the method further comprises:

the first network device receives a handover request message from a second network device, wherein the handover request message comprises second movement history information recorded by the second network device, and the second movement history information comprises a third period of time, and the third period of time is a duration of time when the terminal device is in a second cell;

the first network device compensates for the duration from receiving the handover request message to determining that the terminal device is changed to the first cell into the third period.
A method for communication, applied in a handover process of a dual-active protocol stack, comprising:

the terminal equipment determines to switch from the second cell to the first cell;

The terminal equipment records fourth movement history information after or at the moment of determining to switch from the second cell to the first cell, wherein the fourth movement history information is the history information of the terminal equipment in the second cell, and comprises a fourth period of time, and the fourth period of time is the time waiting in the second cell;

the terminal device determining to switch from a first cell to a second cell comprises:

the terminal equipment determines to switch from the second cell to the first cell under the condition of receiving first indication information, wherein the first indication information is used for indicating the terminal equipment to disconnect from the second cell;

the terminal device recording fourth movement history information at or after determining a time of handover from the second cell to the first cell includes:

the terminal device records the fourth movement history information at or after the moment of receiving the first indication information.
The method of claim 11, wherein the fourth time period comprises a time to be in the second cell before the terminal device receives the first indication information.
The method according to claim 11 or 12, characterized in that the method further comprises:

and the terminal equipment starts to record a fifth time period at the moment of determining that the random access of the first cell is successful, wherein the fifth time period is the time for the terminal equipment to wait in the first cell.
The method according to claim 11 or 12, characterized in that the method further comprises:

and the terminal equipment starts to record a fifth time period at the moment of receiving the first indication information, wherein the fifth time period is the time for the terminal equipment to stay in the first cell.
The method according to any of claims 11 to 14, wherein the fourth movement history information further comprises fourth indication information for instructing the terminal device to handover from the second cell to the first cell in a DAPS handover manner.
The method of claim 15, wherein the fourth indication information is further for indicating a sixth period of time, the sixth period of time representing a duration for which a terminal device is to be in both the first cell and the second cell during a DAPS handoff.
A communication device, comprising:

A processing unit, configured to determine that a terminal device is changed to a first cell, where the change includes dual-activation protocol stack DAPS handover, conditional handover CHO, or radio resource control RRC reestablishment;

the processing unit is further configured to start recording first movement history information after or at the moment when it is determined that the terminal device is changed to the first cell, where the first movement history information is history information of the terminal device in the first cell.
The communication device according to claim 17, wherein the processing unit is specifically configured to:

under the condition that the terminal equipment is successfully accessed in the first cell at random, the terminal equipment is determined to be replaced to the first cell;

and starting to record the first movement history information after or at the moment when the terminal equipment is determined to be successful in the random access of the first cell.
The communications apparatus of claim 17, wherein if the change is a DAPS handoff, the processing unit is configured to:

under the condition that first indication information is sent, determining that the terminal equipment is replaced to the first cell, wherein the first indication information is used for indicating the terminal equipment to disconnect from a second cell;

Recording of the first movement history information is started at or after the time when the first instruction information is transmitted.
The communications apparatus of claim 17, wherein if the change is a DAPS handoff, the processing unit is configured to:

determining that the terminal equipment is replaced to the first cell under the condition that second indication information is sent, wherein the second indication information is used for indicating a second cell or a second network equipment to release the context of the terminal equipment;

recording of the first movement history information is started at or after the time when the second instruction information is transmitted.
The communication apparatus according to any one of claims 17 to 20, wherein the first movement history information further comprises third indication information for indicating that the terminal device is handed over from the first cell to a third cell in a DAPS handover manner.
The communications apparatus of claim 21, wherein the third indication information is further configured to indicate a first period of time that indicates a duration for which a terminal device is to be in both the first cell and the third cell during a DAPS handoff.
The communication device according to claim 17, wherein if the replacement is CHO, the processing unit is specifically configured to:

under the condition that a handover success message is sent, determining that the terminal equipment is replaced to the first cell;

recording of the first movement history information is started at or after the time when the handover success message is transmitted.
The communication device according to claim 17, wherein if the replacement is CHO, the processing unit is specifically configured to:

determining that the terminal equipment is replaced to the first cell under the condition that a serial number state transition message is received;

recording of the first movement history information is started at or after the time when the sequence number state transition message is received.
The communication apparatus according to any one of claims 17 to 24, characterized in that the communication apparatus further comprises:

and the receiving and transmitting unit is used for transmitting the first movement history information to third network equipment, wherein the first movement history information comprises a second time period, and the second time period is the duration of the terminal equipment waiting in the first cell.
The communication apparatus according to any one of claims 17 to 25, characterized in that the communication apparatus further comprises:

A transceiver unit, configured to receive a handover request message from a second network device, where the handover request message includes second movement history information, where the second movement history information is recorded by the second network device, and the second movement history information includes a third period, where the third period is a duration of time that the terminal device waits in a second cell;

the processing unit is further configured to compensate for a duration from receiving the handover request message to determining that the terminal device is changed to the first cell into the third period.
A communication device for use in a dual-active protocol stack handoff procedure, comprising:

a processing unit for determining a handover from the second cell to the first cell;

the processing unit is further configured to record fourth movement history information after or at the time of determining to switch from the second cell to the first cell, where the fourth movement history information is history information of the terminal device in the second cell, and the fourth movement history information includes a fourth period of time, and the fourth period of time is a time to be spent in the second cell;

the processing unit is further configured to determine to switch from the second cell to the first cell when first indication information is received, where the first indication information is used to instruct the terminal device to disconnect from the second cell;

The processing unit is further configured to record the fourth movement history information at or after the time when the first indication information is received.
The communication apparatus of claim 27, wherein the fourth time period comprises a time to be in the second cell before the terminal device receives the first indication information.
The communication apparatus according to claim 27 or 28, wherein the processing unit is further configured to start recording a fifth period of time at a time when the random access of the first cell is determined to be successful, the fifth period of time being a time the terminal device is waiting in the first cell.
The communication apparatus according to claim 27 or 28, wherein the processing unit is further configured to start recording a fifth period of time at a time when the first indication information is received, the fifth period of time being a time when the terminal device is to be in the first cell.
The communication apparatus according to any one of claims 27 to 30, wherein the fourth movement history information further comprises fourth indication information for instructing the terminal device to switch from the second cell to the first cell in a DAPS handover manner.
The method of claim 31, wherein the fourth indication information is further for indicating a sixth period of time, the sixth period of time representing a duration for which a terminal device is to be in both the first cell and the second cell during a DAPS handoff.
A communication device, comprising: a processor and a communication interface, the processor to execute computer instructions received through the communication interface to cause the apparatus to implement: the method of any one of claims 1 to 16.
A computer readable storage medium, characterized in that a computer program is stored thereon, which computer program, when executed, is caused to perform the method of any of claims 1 to 16.