SWITCHING PROCESSING METHOD AND TERMINAL DEVICE.

Abstract

A processing and switching method, a terminal device, a chip, a computer-readable storage medium, a computer program product, and a computer program are described; the method comprises: when a terminal device successfully randomly accesses a target network device in the process of executing a first type of switching, the terminal device switches uplink data transmission to the target network device, and when a pre-set condition is met, the terminal device executes one of the following processing: release the connection with a source network device; do not activate the re-establishment of the connection with the source network device; and do not activate a random access process with the source network device.

Description

SWITCHING PROCESSING METHOD AND TERMINAL DEVICE TECHNICAL FIELD This description relates to the field of information processing technologies, and in particular to a method for processing transfer, a terminal device, a chip, a computer-readable storage medium, a computer program product, and a computer program. BACKGROUND OF THE INVENTION In the related technique, during a handover process in which both a source network device and a target network device are connected, a terminal device maintains both a protocol stack from the source cell and a protocol stack from the target cell throughout the handover. However, in this type of processing, the terminal device may activate some unnecessary processing procedures, thereby incurring additional interrupt time and processing complexity. BRIEF DESCRIPTION OF THE INVENTION To solve the above technical problems, modalities of the present description provide a method for processing transfer, a terminal device, chips, a computer-readable storage medium, a computer program product, and a computer program. First, a method for processing transfers is provided. The method includes the following operations. In a process where a terminal device performs a first type of handover, in response to that random access between the terminal device and a target network device being successful, the terminal device hands off uplink transmission data to the target network device and performs one of the following processes in a case where a pre-established condition is met: release a connection with a source network device; do not initiate a reset of a connection with the source network device; or do not initiate a random access procedure with the source network device. Secondly, a terminal device is provided. The terminal device includes a communication unit. LPRAnn / zznz / E / YiAi The communication unit is configured to: in a process where the terminal device performs a first type of handover, in response to that random access between the terminal device and target network device being successful, hand off uplink data transmission to the target network device and perform one of the following processes in a case where a preset condition is met: release a connection with a source network device; do not trigger a reset of a connection with the source network device; or do not trigger random access processing with the source network device. In a third aspect, a terminal device is provided. The terminal device includes a processor and memory. The memory is configured to store computer programs, and the processor is configured to call and execute the computer programs stored in memory to perform the methods described in the first aspect above, using various implementation methods. In a fourth aspect, a chip is provided to implement the methods in the various implementations. Specifically, the chip includes a processor. The processor is configured to call and execute computer programs from memory to cause a device installed with the chip to perform the methods described in the first aspect above, or various implementations thereof. In a fifth aspect, a computer-readable storage medium for storing computer programs is provided. Computer programs cause a computer to perform the methods described in the first aspect above, or various implementations thereof. In a sixth aspect, a computer program product that includes computer program instructions is provided. The computer program instructions cause a computer to perform the methods of the first aspect above or various implementations thereof. In a seventh aspect, a computer program is provided. The computer program is running on a computer to cause the computer to perform the methods in the first aspect above, or various implementations thereof. By adopting the above solution, after a successful random access between the terminal device and a target network device in a process where the terminal device performs a first type of handover, in a case where the predefined condition is met, the terminal device releases the connection with the source network device and does not initiate a re-establishment of a connection with the source network device, nor does it initiate a random access procedure with the source network device. In this way, it can be ensured that, in a LPRAnn / zznz / E / YiAi process that the terminal device performs a first type of handover, after a random access between the terminal device and a target network device is successful and the terminal device establishes a connection with the target network device, no useless connection is activated between the terminal device and the source network device, and thus no additional interruption time and additional processing complexity is carried out on the terminal device. BRIEF DESCRIPTION OF THE FIGURES Figure 1 is a first schematic diagram of a communication system architecture provided by the modalities of the present description. Figure 2 is a schematic flowchart of a method for processing transfer provided by the modalities of the present description. Figure 3 is a schematic flow chart of a transfer. Figure 4 is a first schematic flow chart in an example provided by the modalities of the present description. Figure 5 is a second schematic flowchart in an example provided by the modalities of the present description. Figure 6 is a schematic structural diagram of a terminal device provided by the modalities of the present description. Figure 7 is a schematic structural diagram of a communication device provided by the modalities of the present description. Figure 8 is a schematic block diagram of a chip provided by the modalities of the present description. Figure 9 is a second schematic diagram of a communication system architecture provided by the modalities of the present description. DETAILED DESCRIPTION OF THE INVENTION To better understand the characteristics and technical content of the modalities described herein, their implementation will be detailed below with reference to the attached figures. The attached figures are for reference only and are not intended to define the modalities described herein. The technical solutions for the modalities described herein will be described below with reference to the figures attached to those modalities. Obviously, the described modalities are part of the modalities described herein, not LPRAnn / zznz / E / YiAi all modalities. Based on the modalities in this description, all other modalities obtained by those skilled in the art with average knowledge without creative effort will fall within the scope of protection of this description. The technical solutions of the modalities described herein can be applied to various communication systems, for example, a Global System for Mobile Communications (GSM) system, a Code Division Multiple Access (CDMA) system, a Wideband Code Division Multiple Access (WCDMA) system, General Packet Radio Service (GPRS), Long Term Evolution (LTE) system, LTE Frequency Division Duplex (FDD) system, LTE Time Division Duplex (TDD) system, Universal Mobile Telecommunications System (UMTS), Worldwide Interoperability Communication System for Microwave Access (WiMAX) or 5G system, etc. For illustrative purposes, a communication system to which the modalities of the present description apply may be as shown in Figure 1. The communication system 100 may include a network device 110, and the network device 110 may be a device that communicates with the UE 120 (or referred to as a communication terminal, a terminal). The network device 110 may provide communication coverage for a particular geographic area and may communicate with UEs located within the coverage area.Optionally, the 110 network device can be a network device in a GSM system or a CDMA system (Base Transceiver Station (BTS)), or a network device in a WCDMA system (NodeB, NB), or an evolving network device in an LTE system (evolving NodeB, eNB or an eNodeB), or a wireless controller in a Cloud Radio Access Network (CRAN), or the network device can be a mobile switching center, relay station, access point, vehicle-mounted devices, wearable devices, hubs, switches, bridges, routers, a network-side device of the 5G network, or a network device in the future evolved Public Land Mobile Network (PLMN), etc. The communication system 100 also includes at least one terminal 120 located within the coverage area of ​​the network device 110. The terminal used herein includes, but is not limited to, devices connected via a wired line, such as public switched telephone networks (PSTN), digital subscriber line (DSL), digital cable, and direct cable, and / or via another data connection / network, and / or via a wireless interface, such as a cellular network, a wireless local area network (WLAN), a digital television network such as a DVB-H network, a satellite network, and an AM / FM broadcast transmitter, and / or a device of another terminal configured to receive / transmit a communication signal, and / or an Internet of Things (IoT) device. A terminal LPRAnn / zznz / E / YiAi configured to communicate via a wireless interface may be referred to as a wireless communication terminal, wireless terminal, or mobile terminal. Optionally, device-to-device (D2D) communication can be performed between UE 120. It should be understood that the terms system and network are frequently used interchangeably here. The term and / or in this description is solely an association relationship to describe the associated objects, and it represents that three types of relationships can exist; for example, A and / or B can represent three types of cases: A exists alone, both A and B exist, and B exists alone. Furthermore, the / character in this description generally represents a relationship of or between the associated objects before and after. To better understand the characteristics and technical content of the modalities described herein, their implementation will be detailed below with reference to the attached figures. The attached figures are for reference only and are not intended to define the modalities described herein. The methods described herein provide a way to process transfers. As shown in Figure 2, the method includes the following operations. In operation 21, in a process where a terminal device performs a first type of handover, in response to that random access between the terminal device and a target network device that is successful, the terminal device hands off uplink data transmission to the target network device, and in the event that a pre-set condition is met, the terminal device performs one of the following processes: release a connection with a source network device, do not initiate a reset of a connection with the source network device; or do not initiate a random access procedure with the source network device. The first type of handover is a handover during which the terminal device maintains both a protocol stack from the source network device and a protocol stack from the target network device. This first type of handover can be referred to as a Dual Active Protocol Stack Handover (DAPS). In these modes, a network device can be a base station on one side of the network. The source network device can be a source base station connected to the terminal device, and the target network device can be a target base station. The terminal device is a device that can maintain a connection with both the source network device and the target network device during the handover. First, a scenario of the modes will be described. Similar to an LTE system, a New Radio (NR) system supports a handover process of the terminal device in a connected state. When the terminal device is using a network service When LPRAnn / zznz / E / YiAi moves from one cell to another, or in cases of wireless transmission traffic load adjustment, activation operation maintenance, device failure, etc., in order to ensure communication continuity and quality of service, the system needs to transfer a communication link from the terminal device of the original cell to a new cell; that is, to perform the handover process. Taking a handover process corresponding to an Xn interface handover product as an example for illustration, the entire handover process involves three stages. As shown in Figure 3, the handover process includes a handover preparation stage, a handover execution stage, and a handover completion stage. In the handover preparation stage, as shown in Figure 0-5, a target network device and a source network device perform processes in accordance with the mobility control information provided by an Access and Mobility Management (AMF) function entity. A terminal device performs metering control and reporting, the source network device makes a handover decision, and then the source network device sends a handover request to the target network device. The target network device performs management control and handover request information. The handover confirmation message includes a handover command generated by the target cell, and the source network device is not allowed to modify the handover command generated by the target network device and directly sends the handover command to the terminal device. In the handover execution stage, as shown in Figure 6-7, the terminal device immediately performs a handover procedure after receiving the handover command. The handover procedure may include the following operations: a Radio Access Network (RAN) handover is performed between the terminal device and the source network device; the terminal device disconnects from the source cell, synchronizes with the target cell and establishes a connection (such as by performing random access, sending an RRC handover completion message to the target base station, etc.), and performs an SN state transition; and the handover procedure may also include the source network device transmitting new data from a User Plane Function (UPF) entity, and transmitting buffered data to the target network device. In the handover completion stage, as shown in Figure 8-12, after the RAN handover is complete, user data is transmitted between the terminal device and the target network device, and user data is transmitted between the target network device and the UPF. Then, the target network device sends a path handover request to the AMF. The UPF performs the path handover, and then the AMF notifies the target network device of the path handover completion via the source network device. The AMF sends a path handover request acknowledgment to the target network device, and then the network device LPRANN / zznz / E / YiAi target notifies the source network device to perform user data release. In addition, another handover scenario that corresponds to the modalities can also include the following two architectures, namely, a handover based on a dual connection and a handover during which connections are maintained with both the source network device and the target network device. In a case of a dual-connection-based handover, during the handover, the target network device is first added as a secondary node (SN), and then the SN is changed to a master node (MN) through role-conversion signaling, and finally the source network device is released, to achieve an effect of reducing downtime when handing over. Another architecture is handover, during which connections to both the source and target network devices are maintained. This can be understood as an enhanced do-before-break (eMBB) handover. The difference is that when the terminal device receives the handover command (HO command), it initiates random access to the target network device while continuously maintaining a connection to the source network device. The connection to the source network device is released only after the terminal device has fully accessed the target network device. Furthermore, regarding 3GPP mobility improvements (including LTE and NR), a Dual Active Protocol Stack (DAPS) optimization method is proposed to reduce downtime during handovers. The key point is that the terminal device will maintain both a protocol stack from the source network device and a protocol stack from the target network device during the handover. After receiving the DAPS handover command, the terminal device maintains a connection with the source network device and initiates a synchronization process with the target network device. Once the synchronization / random access process is complete, the terminal device will perform uplink data handover; that is, the uplink data transmission for the network device will be transferred from the source network device to the target network device after random access.After random access, the release of the protocol stack of the source network device is based on an explicit indication from the network, i.e., during the period after random access until the release of the connection with the source network device, the terminal device can normally receive downlink data sent by the source cell, and can send uplink feedback information related to the downlink data and similar to the source cell. In the procedure where the terminal device performs the first type of transfer (DAPS transfer), in a case where random access between the terminal device and the If the LPRAnn / zznz / E / YiAi connection to the target network device is successful, and the terminal device passes the uplink data transmission to the target network device, the terminal device also retains the protocol stack from the source network device, or it is understood that the terminal device maintains the connection to the source network device. In such a scenario, the solution provided in the modalities aims to address how to avoid triggering a pointless connection procedure, and the additional transmission downtime and complexity introduced by the pointless connection procedure to the terminal device. As shown in Figure 4, the solution provided by the modalities may include the following operations. In operation 41, the terminal device receives a handover command, and the handover command instructs the terminal device to perform the first type of handover, i.e., DAPS handover. In operation 42, the terminal device performs a synchronization / random access process with the target network device using a handover command. If the random access is successful, the terminal device hands off the uplink data transmission to the target network device. If the preset condition is met, the terminal device performs one of the following processes: releases a connection with a source network device; does not initiate a connection reset with the source network device; and does not initiate a random access procedure with the source network device. Based on the above, the solution is illustrated with examples. A first example The pre-set condition includes that a Radio Link Failure (RLF) occurs in a connection between the terminal device and the source network device. In a case where the pre-established condition is met, a process performed by the terminal device is: to release the connection with the source network device; or not to activate the re-establishment of the connection with the source network device. For example: In a case where an RLF occurs in a connection between the terminal device and the source network device (or source cell), the terminal device releases the connection with the source cell. The process of releasing the connection to the source network device may include: releasing a protocol stack from the source network device and releasing a secret key associated with the source network device. In other words, if an activator condition about an RLF is met, the device LPRAnn / zznz / E / YiAi terminal and the source network device, when it is determined that an RLF occurs, the re-establishment of the connection with the source network device in accordance with the existing protocol regulation is not performed, but the connection with the source network device is released. In other words, once an RLF occurs in a connection between the terminal device and the source network device, the connection to the source network device is completely prevented by releasing the connection to the source network device, which includes the protocol stack corresponding to the source network device and other related information, so that the connection reset is not performed. For another case as shown in Figure 5: In operation 51, in case of RLF, the connection between the terminal device and the source network device is lost, the re-establishment of the connection with the source network device is not activated. That is, if the trigger condition is met between the RLF of the terminal device and the source network device, when it is determined that RLF occurs, the re-establishment of the connection with the source network device in accordance with the existing protocol regulation is not performed, but the terminal device is controlled not to perform the connection re-establishment processing with the source network devices. This operation may also include: if the process performed by the terminal device is not enabled for re-establishing the connection with the source network device, the terminal device retains a protocol stack from the source network device. The difference from the previous example is that in this case, the terminal device is only controlled to prevent the connection from being re-established, but it retains the protocol stack from the source network device; or, it can be understood that the terminal device retains information related to the source network device. Based on this, in operation 52, the terminal device receives first indication information; the first indication information is used to instruct the release of the connection with the source network device. In operation 53, the terminal device releases the connection to the source network device based on the initial location information. The process of releasing the connection to the source network device includes: releasing a protocol stack from the source network device and releasing a secret key associated with the source network device. In other words, if an RLF occurs in the connection between the terminal device and the source network device, the terminal device does not initiate a connection reset and retains the protocol stack of the source network device (or the information related to the network device). LPRAnn / zznz / E / YiAi source) until the first indication information used to explicitly instruct release of the source network device is received. The first indication information used to instruct the release of the source network device can be sent by the source network device to the terminal device (or it can also be sent by the target network device to the terminal device). The initial indication information can be carried by at least one type of downlink information or channel. For example, it can be carried by downlink control information (DCI), or by radio resource control (RRC) signaling, or by a medium access control (MAC) control element (CE), or by a physical downlink shared channel (PSCH), or by a physical downlink control channel (PDCCH), etc., which is not exhaustive here. Additionally, in this example, the method may also include the terminal device reporting to the target network device that the RLF occurs in connection with the source network device. For example, in the process of performing operation 51, in a case where the terminal device determines that the RLF occurs between the terminal device and the source network device, the terminal device reports to the target network device that the RLF occurs in the connection with the source network device. Alternatively, in the process of performing operation 52 or operation 53, for example, before (or after) receiving the first indication information, the terminal device reports to the target network device that the RLF occurs in the connection with the source network device. In this example, the RLF trigger condition includes at least one of: expiration of a timer started after indication of radio link problems from a physical layer (if radio link problems are recovered before the timer expires, the UE stops the timer); for example, in one case, the timer is started in an out-of-sync event, and when the timer expires, the out-of-sync problem is not resolved, then RLF is considered to have occurred; A procedural failure of random access with the source network device, for example, may be the failure that occurs in the process of activating random access in an uplink out-of-sync case, or, it may be the failure that occurs in the process of activating random access in a beam fault recovery (BFR) case, and others like it, and may be considered to be an RLF; or a Radio Link Control (RLC) failure. LPRAnn / zznz / E / YiAi A second example The preset section includes that a condition to enable random access is met between the terminal device and the source network device. In a case where the pre-established condition is met, a process performed by the terminal device is: similar to releasing the connection with the source network device; or not activating the random access process with the source network device. In this example, the condition for enabling random access includes at least one of: uplink out of sync; scheduling request (SR)-activated random access; beam fault recovery (BFR); or connection re-establishment. Since the scenario for this mode is that random access between the terminal device and a target network device is successful, in the process the terminal device performs the first type of handoff (DAPS handoff). While the terminal device hands off the uplink data transmission to the target network device, the terminal device also retains the protocol stack of the source network device, or it is understood that the terminal device maintains a connection with the source network device. Therefore, in this example, the described random access procedure refers to the random access procedure when the terminal device is in a connected state (with the source network device). This example may also include the terminal device reporting a terminal device process status to the target network device. Specifically, if the terminal device releases the connection to the source network device in a case where the preset condition is met, the process status of the terminal device can be reported to the target network device. Alternatively, if the terminal device does not initiate the random access procedure with the source network device in a case where the preset condition is met, the processing status of the terminal device can be reported to the target network device. The terminal device process situation includes at least: a terminal device cause that triggers the random access procedure. The cause for activating the random access procedure can correspond to the condition for activating random access. For example, if the condition for activating random access is a connection reset, then in the event that the terminal device determines not to activate the random access process with the source network device, the terminal device can send a second indication information from the target network device to indicate a random access process between the terminal device and the source network device activated by the connection reset. LPRAnn / zznz / E / YiAi Furthermore, the cause for activating the random access procedure can be a reason value, for example, reason value A, which may correspond to outside uplink synchronization, etc., which is not exhaustive here. Furthermore, the terminal device's previous processing status, in addition to the previous cause of triggering the random access procedure, may also include a specific processing action taken by the terminal when the condition for triggering the random access procedure is met. For example, the processing action indicated by the terminal device to the target network device might include: not triggering the random access procedure with the source network device, or releasing the connection with the source network device, and similar actions. In one way, if the random access procedure with the source network device is not activated, some of the processes in the previous examples can also be combined. For example, the terminal device might receive the first indication information. This first indication information is used to instruct the terminal device to release the connection with the source network device. The terminal device releases the connection with the source network device based on this first indication information. It can be observed that by adopting the above solutions, after a random access between the terminal device and a target network device that is successful in a process in which the terminal device performs a first type of handover, in a case in which the pre-established condition is met, the terminal device releases the connection with the source network device, or does not trigger a reset of a connection with the source network device, or does not trigger a random access procedure with the source network device.In this way, it can be ensured that, in a process where the terminal device performs a first type of handover, after a random access between the terminal device and a target network device that is successful and the terminal device establishes a connection with the target network device, no useless connection is activated between the terminal device and the source network device, and thus no additional interrupt time and additional processor complexity is sealed from the terminal device. The modalities described herein provide a terminal device. As shown in Figure 6, the terminal device includes a communication unit 61. Communication unit 61 is configured to: in a terminal device process, perform a first type of handover, in response to a successful random access between the terminal device and a target network device, hand off uplink data transmission to the target network device and perform one of the following processes if a predefined condition is met: release a connection to a source network device; fail to trigger a reset of a connection to the source network device; or fail to trigger a LPRAnn / zznz / E / YiAi random access procedure with the source network device. The first type of handover is a handover during which the terminal device maintains both the protocol stack of the source network device and the protocol stack of the target network device. This first type of handover can be referred to as a Dual Active Protocol Stack Handover (DAPS). In these modes, a network device can be a base station on one side of the network. The source network device can be a source base station connected to the terminal device, and the target network device can be a target base station. The terminal device is a device that can maintain connections with both the source and target network devices during the handover. The solution provided by the modalities is as follows. In the process where the terminal device performs the first type of handover (DAPS handover), in a case where random access between the terminal device and the target network device is successful, while the terminal device hands off the uplink data transmission to the target network device, the terminal device also retains the protocol stack of the source network device, or it is understood that the terminal device retains the connection to the source network device. In such a scenario, how to avoid triggering an unnecessary connection procedure and avoid additional transmission downtime and the added complexity introduced by the unnecessary connection procedure to the terminal device is the problem to be solved by the solution provided in the modalities. Based on the above, the solution is illustrated for example. A first example The preset condition includes that a Radio Link Failure (RLF) occurs in the connection between the terminal device and the source network device. Communication unit 61 is configured to: in a case where the preset condition is met, perform a process that includes releasing the connection to the source network device; or not activate the re-establishment of the connection to the source network device. For example: In the event of an RLF occurring in a connection between the terminal device's communication unit 61 and the source network device (or source cell), the communication unit 61 will release the connection to the source cell. The process of releasing the connection to the source network device may include: releasing a protocol stack from the source network device and releasing a secret key associated with the source network device. In another case: In the event of an RLF occurring in the connection between communication unit 61 and the LPRAnn / zznz / E / YiAi source network device, the reset of the connection with the source network device is not activated. This may also include: if the process performed by the terminal device is not triggering the re-establishment of the connection with the source network device, the terminal device's communication unit 61 retains the protocol stack of the source network device. The difference from the previous example is that in this case, the terminal device is only controlled not to perform the re-establishment of the connection, but it retains the protocol stack of the source network device, or it is understood that the terminal device retains information related to the source network device. Based on this, the terminal device's communication unit 61 receives the first indication information. This first indication information is used to instruct the terminal device to release the connection to the source network device. The terminal device releases the connection to the source network device based on this first indication information. The process of releasing the connection to the source network device includes releasing the protocol stack of the source network device and releasing a secret key associated with the source network device. Additionally, in this example, communication unit 61 is also configured to report to the target network device that the RLF occurs in connection with the source network device. In this example, the trigger condition for RLF includes at least one of: expiration of a timer started after indication of radio link problems from a physical layer (if radio link problems are recovered before the timer expires, the UE stops the timer); for example, in one case, the timer is started in an out-of-sync event, and when the timer expires, the out-of-sync problem is not resolved, then RLF is considered to have occurred; A random access procedure failure with the source network device, for example, may be the failure that occurs in the process of activating random access in an uplink out-of-sync case, or, it may be the failure that occurs in the process of activating random access in a beam fault recovery (BFR) case, and others like it, and is considered to be an RLF; or a Radio Link Control (RLC) failure. A second example The preset condition includes that a condition to enable random access is met between the terminal device and the source network device. In a case where the specified condition is met, a process performed by the communication unit 61 of the terminal device is: releasing the connection with the device of LPRAnn / zznz / E / YiAi source network; or do not activate the random access procedure with the source network device. In this example, the condition for enabling random access includes at least one of: uplink out of sync; scheduling request (SR)-activated random access; beam fault recovery (BFR); or connection reset. This example may also include that the terminal device's communication unit 61 is configured to report a terminal device process status to the target network device. The terminal device process situation at least includes: a terminal device cause that triggers the random access procedure. It can be observed that by adopting the above situations, after a random access between the terminal device and a target network device that is successful in a process in which the terminal device performs a first type of handover, in the case that the pre-established condition is met, the terminal device releases the connection with the source network device, or does not trigger a connection reset with the source network device, or does not trigger a random access procedure with the source network device.In this way, it can be ensured that, in a process where the terminal device performs a first type of handover, after a random access between the terminal device and a target network device that is successful and the terminal device establishes a connection with the target network device, no useless connection is activated between the terminal device and the source network device, and thus no additional interruption and additional processing complexity is carried out on the terminal device. Figure 7 is a schematic structural diagram of a 900 communication device provided by the modalities described herein. The communication device in these modalities may specifically be the network device described above. The 900 communication device shown in Figure 7 includes a 910 processor, and the 910 processor can call and execute computer programs from memory to implement the methods described herein. Alternatively, as shown in Figure 7, the 900 communication device may also include a 920 memory. The 910 processor can carry and run computer tests from the 920 memory to implement the methods in the modes of the present description. The 920 memory can be a separate device independent of the 910 processor, or it can be integrated into the 910 processor. Alternatively, as shown in Figure 7, the communication device 900 may further include a transceiver 930, and process 910 may control the transceiver 930 to LPRAnn / zznz / E / YiAi communicate with other devices, specifically, it can send information or data to other devices, or receive information or data sent by other devices. The 930 transceiver may include a transmitter and a receiver. The 930 transceiver may also include antennas, and the number of antennas may be one or more. Alternatively, the 900 communication device may specifically be a terminal device or a network device of the types described herein, and the 900 communication device may implement the corresponding processes implemented by the mobile terminal / terminal device in various methods within the types described herein. For the sake of brevity, further elaboration is omitted. Figure 8 is a schematic structural diagram of a chip in accordance with the modalities of the present description. The chip 1000 shown in Figure 8 includes a processor 1010, and the processor 1010 can call and execute computer programs from memory to implement the methods in the modalities of the present description. Alternatively, as shown in Figure 8, the 1000 chip may also include a 1020 memory. The 1010 processor may call and execute computer programs from the 1020 memory to implement the methods of the modalities described herein. The 1020 memory can be a separate device independent of the 1010 processor, or it can be integrated into the 1010 processor. Alternatively, the 1000 chip may also include an input interface 1030. The 1010 processor can control the input interface 1030 to communicate with other devices or chips, and specifically, it can obtain information or data sent by other devices or chips. Alternatively, the 1000 chip may also include a 1040 output interface. The 1010 processor can control the 1040 output interface to communicate with other devices or chips, and specifically, it can send information or data to other chip devices. Alternatively, the chip can be applied to the corresponding processes implemented by the terminal device using various methods as described herein. For the sake of brevity, further details are omitted. It should be understood that the chip referred to in the modalities of the present description may also be referred to as a system-level chip, a system chip, a system-on-a-chip, or a system-on-a-chip, or similar. It should be understood that the processor in the modalities described herein can be an integrated circuit chip capable of processing signals. In the implementation process, various operations of the aforementioned method modalities can be completed by a hardware integrated logic circuit in a processor or by a software instruction. The processor in question can be a general-purpose processor or a digital signal processor. LPRAnn / zznz / E / YiAi (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components. Various methods, operations, and logic block diagrams described in the modalities of this description may be implemented or executed. A general-purpose processor may be a microprocessor, or the processor may be any conventional or similar processor. The operations of the method described in conjunction with the modalities of this description may be directly represented as executed by a hardware decoding processor, or executed by a combination of hardware and software modules within the decoding processor.Software modules can be located in random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, and other mature storage media. The storage medium is located in memory; the processor reads the information from memory and completes the operations described above in conjunction with its hardware. It should be understood that the memory in the modalities described herein may be volatile or non-volatile memory, or may include both. Non-volatile memory may be read-only memory (ROM), programmable ROM (PROM), erasable PROM (EPROM), electrically erasable EPROM (EEPROM), or flash memory. Volatile memory may be random-access memory (RAM), which acts as an external cache.By way of example, and not as a limitation, many forms of RAM are available, such as static RAM (RAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (ESDRAM), enhanced SDRAM (ESDRAM), synchronous link DRAM (SLDRAM), and direct RAM bus RAM (DR RAM). It should be noted that the memory systems and methods described herein are intended to include, but are not limited to, these and any other suitable types of memory. It should be understood that the preceding description is illustrative but not exhaustive. For example, memory in the forms described herein may also be static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), synchronous link DRAM (SLDRAM), and direct RAM bus RAM (DR RAM), and so on. That is, memory in the forms described herein is intended to include, but is not limited to, these and any other suitable type of memory. LPRAnn / zznz / E / YiAi Figure 9 is a schematic block diagram of an 800 communication system provided by the modalities described herein. As shown in Figure 9, the 800 communication system includes a terminal device 810 and a network device 820. Here, the network device can include either the source network device or the target network device. The 810 terminal device can be used to implement the corresponding functions implemented by the UE in the methods described above, and the 820 network device can be used to implement the method described above on the source network device side or the corresponding functions implemented by the network device on the target network device side. For the sake of brevity, further explanation is omitted here. The modalities described herein also provide a computer-readable storage medium for storing a computer program. Alternatively, the computer-readable storage medium can be applied to a network device or a terminal device in the ways described herein, and the computer program causes the computer to execute the corresponding processes implemented by the network device using various methods described herein. For the sake of brevity, further details are omitted. The modalities of this description also provide a computer program product, including computer program instructions. Alternatively, the computer program product can be applied to a network device or a terminal device in the embodiments of the present invention, and the computer program instructions cause the computer to execute the corresponding processes implemented by the network device in various ways described herein. For the sake of brevity, further elaboration is omitted. The modalities described herein also provide a computer program. Alternatively, the computer program can be applied to a network device or a terminal device in the ways described herein, and when the computer program is executed on the computer, the computer executes the corresponding processes implemented by the network device using various methods described herein. For the sake of brevity, further details are omitted. Those skilled in the art may realize that the algorithmic units and operations of the various examples described, in conjunction with the modalities of this description, can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Skilled professionals can implement LPRAnn / zznz / E / YiAi The functionality described uses different methods for each particular application, but such implementations should not be considered beyond the scope of this description. Those skilled in the technique will readily understand that, for the sake of convenience and brevity, the specific operating processes of the aforementioned systems, devices, and units may refer to the corresponding processes in the previous methodologies. Further elaboration is omitted here. In the various modalities provided by this description, it should be understood that the systems, devices, and methods described may be implemented in other ways. For example, the apparatus modalities described above are merely illustrative. For instance, the division of units is simply a division of logical function. In actual implementation, there may be other methods of division. For example, multiple units or components may be combined or integrated into another system, or some features may be omitted or not implemented. On the other hand, the mutual coupling shown or discussed, or direct coupling or communication connection, may be a communication connection or indirect coupling through some interfaces, devices, or units, and may be electrical, mechanical, or otherwise. The units described as separate components may or may not be physically separate, and components illustrated as units may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units may be selected according to actual needs to implement the purpose of the modal solutions. Furthermore, several functional units in various modalities of the present description may be integrated into one processing unit, or each unit may physically exist alone, or two or more units may be integrated into one unit. The functions, if implemented as functional software units and sold or used as standalone products, can be stored on a computer-readable storage medium. Based on this understanding, the essence of the technical solution described herein is the portion that contributes to the technique described above, and the portion of the technical solution that can be represented as a software product. The computer software product is stored on a storage medium and includes various instructions to cause a computer device (which may be a personal computer, a server, a network device, etc.) to execute all or part of the operations of the methods described in the various modalities of this description.The above storage media includes: U disk, mobile hard disk, read-only memory (ROM), random access memory (RAM), magnetic disk or optical disk, or other media that can store program code. The above are merely specific variations of the present description, LPRAnn / zznz / E / YiAi, but the scope of protection of this description is not limited to this. Anyone skilled in the art can easily think of changes or substitutions within the technical scope described herein, which should be covered within the scope of protection of this description. Therefore, the scope of protection of this description should be subject to the scope of protection of claim 5.

Claims

1. A method for processing handover, characterized in that it comprises: in a process in which a terminal device performs a first type of handover, in response to a successful random access between the terminal device and a target network device, handing off, by the terminal device, uplink data transmission to the target network device; and performing, by the terminal device, one of the following processes in a case in which a pre-established condition is met: releasing a connection to a source network device; not triggering a reset of a connection to the source network device; or not triggering a random access procedure with the source network device.

2. The method according to claim 1, further characterized in that the pre-established condition comprises: a Radio Link Failure (RLF) occurring in a connection between the terminal device and the source network device; and in an event that the pre-established condition is met, a process performed by the terminal device is: to release the connection with the source network device; or to fail to initiate the restoration of the connection with the source network device.

3. The method according to claim 2, further characterized in that it additionally comprises: retaining, by the terminal device, a protocol stack from the source network device in response to the process performed by the terminal device that is not activating the re-establishment of the connection with the source network device.

4. The method according to claim 3, further characterized in that it further comprises: receiving, by the terminal device, first indication information, wherein the first indication information is used to instruct the release of the connection with the source network device; releasing, by the terminal device, the connection with the source network device based on the first indication information.

5. The method according to any of claims 1 to 4, further characterized in that the process for releasing the connection to the source network device comprises: releasing a protocol stack from the source network device and releasing a secret key associated with the source network device.

6. The method according to claim 3, further characterized in that it additionally comprises: reporting, by the terminal device, to the target network device that the RLF occurs in the connection with the source network device.

7. The method according to any of claims 2 to 6, further characterized in that an RLF activation condition comprises at least one of: expiration of a timer initiated after an indication of radio link problems at a physical layer; a random access procedure failure with the source network device; or a Radio Link Control (RLC) failure.

8. The method according to claim 1, further characterized in that the pre-established condition comprises: a condition for activating random access that is met between the terminal device and the source network device; and in an event that the pre-established condition is met, a process performed by the terminal device is: to release the connection with the source network device; or not to activate the random access procedure with the source network device.

9. The method according to claim 8, further characterized in that it additionally comprises: reporting, by the terminal device, a process status of the terminal device to the target network device.

10. The method according to claim 9, further characterized in that the process situation of the terminal device at least comprises: a cause of the terminal device that activates the random access process.

11. The method according to claim 8 or 9, further characterized in that the condition for activating random access comprises at least one of: uplink out of synchronization; scheduling request (SR)-activated random access; beam fault recovery (BFR); or connection re-establishment.

12. The method according to any of claims 1 to 11, further characterized in that the first type of handover is a handover during which the terminal device maintains a protocol stack of the source network device and a protocol stack of the target network device.

13. A terminal device, characterized in that it comprises: a communication unit, configured to: in a process in which the terminal device performs a first type of handover, in response to a successful random access between the terminal device and a target network device, hand off uplink data transmission to the target network device and perform one of the following processes in the event that a pre-established condition is met: release a connection with a source network device; do not activate a reset of a connection with the source network device; or do not activate a random access procedure with the source network device.

14. The terminal device according to claim 13, further characterized in that the preset condition comprises: a Radio Link Failure (RLF) occurring in a connection between the terminal device and the source network device, and the LPRAnn / zznz / E / YiAi communication unit is configured to: in the event that the preset condition is met, perform a process that includes releasing the connection to the source network device; or fail to activate the re-establishment of the connection to the source network device.

15. The terminal device according to claim 14, further characterized in that the communication unit is configured to retain a protocol stack from the source network device in response to the process performed that is not activating the re-establishment of the connection with the source network device.

16. The terminal device according to claim 15, further characterized in that the communication unit is configured to: receive first indication information, wherein the first indication information is used to instruct the release of the connection to the source network device; and release the connection to the source network device based on the first indication information.

17. The terminal device according to any of claims 13 to 16, further characterized in that the process of releasing the connection with the source network device comprises: releasing a protocol stack from the source network device and releasing a secret key associated with the source network device.

18. The terminal device according to claim 15, further characterized in that the communication unit is configured to report to a target network device that the RLF occurs in connection with the source network device.

19. The terminal device according to any of claims 14 to 18, further characterized in that an RLF activation condition comprises at least one of: expiration of a timer initiated after an indication of radio link problems from a physical layer; a random access procedure failure with the source network device; or a Radio Link Control (RLC) failure.

20. The terminal device according to claim 13, further characterized in that the preset condition comprises: a condition for activating random access that is met between the terminal device and the source network device; and the communication unit is configured to: in the event that the preset condition is met, perform a process that includes releasing the connection with the source network device; or not activate the random access procedure with the source network device.

21. The terminal device according to claim 20, further characterized in that the communication unit is configured to report a process status of the terminal device to the target network device.

22. The terminal device according to claim 21, further characterized in that the process situation of the terminal device comprises at least: a cause of the LPRAnn / zznz / E / YiAi terminal device that activates the random access procedure.

23. The terminal device according to claim 21 or 22, further characterized in that the condition for activating random access comprises at least one of: uplink out of synchronization; request-activated random access (SR); beam fault recovery (BFR); or connection reset.

24. The terminal device according to any of claims 13 to 23, further characterized in that the first type of handover is: a handover during which the terminal device maintains a protocol stack from the source network device and a protocol stack from the target network device.

25. A terminal device characterized in that it comprises: a processor and a memory for storing computer programs executable in the processor, wherein the memory is configured to store computer programs, and the processor is configured to call and execute the computer programs stored in the memory to perform the operations in the method of any of claims 1 to 12.

26. A chip characterized in that it comprises: a processor, wherein the processor is configured to call and execute computer programs from a memory to cause a device in which the chip is installed to perform the method of any one of claims 1 to 12.

27. A computer-readable storage medium for storing computer programs, characterized in that the computer programs cause a computer to perform operations in the method of any of claims 1 to 12.

28. A computer program product characterized in that it comprises computer program instructions, wherein computer program instructions cause a computer to perform the method of any one of claims 1 to 12.

29. A computer program, characterized in that it causes a computer to perform the method of any one of claims 1 to 12.

Images