WO2020199026A1

WO2020199026A1 - Handoff processing method, user equipment, and network device

Info

Publication number: WO2020199026A1
Application number: PCT/CN2019/080648
Authority: WO
Inventors: 石聪; 杨宁; 尤心
Original assignee: Oppo广东移动通信有限公司
Priority date: 2019-03-29
Filing date: 2019-03-29
Publication date: 2020-10-08
Also published as: WO2020199026A9; CN112806061A; CN112806061B

Abstract

Disclosed are a handoff processing method, UE, a network device, a chip, a computer-readable storage medium, a computer program product, and a computer program. The method comprises: transmitting first information to user equipment (UE), wherein the first information is at least used to assist the UE to determine whether the effective duration of UE-related information at a UE side is consistent with that at a network side, or is used to determine an effective duration of UE-related information.

Description

Handover processing method, user equipment and network equipment

Technical field

The present invention relates to the field of information processing technology, and in particular to a handover processing method, User Equipment (UE, User Equipment), network equipment and computer storage media, chips, computer readable storage media, computer program products, and computer programs.

Background technique

In New Radio Unlicensed (NR-U, New Radio Unlicensed), for downlink transmission, network equipment needs to perform listening before transmission (LBT, Listen Before Talk). If the listening result indicates that the channel is in an occupied state, the network device needs to back off for a period of time according to regulations before continuing to listen to the channel, knowing that the channel listening result is idle, before transmitting data, such as a handover command, to the UE. Since the source network device can be an NR-U network device during the handover process, the network device can only send the handover command when the channel is idle. This leads to the fact that when the handover command is actually issued to the UE, it will follow the target network device to the source network device. There is a long time interval between sending handover commands (Handover Request Acknowledgement (ACK)), causing resource failure.

Summary of the invention

To solve the foregoing technical problems, embodiments of the present invention provide a handover processing method, UE, network equipment, and computer storage medium, chip, computer readable storage medium, computer program product, and computer program.

In the first aspect, a handover processing method is provided, which is applied to a source network device, including:

Sending the first information to the user equipment UE;

Wherein, the first information is at least used to assist the UE in determining that the effective duration of UE-related information on the UE side and the network side are consistent, or used to determine the effective duration of UE-related information

In a second aspect, a handover processing method is provided, which is applied to a user equipment UE, and the method includes:

Receiving the first information sent by the source network device;

In a third aspect, a handover processing method is provided, which is applied to a source network device, including:

Select the target network device for switching, and send a switching request to the target network device;

Receiving the handover request confirmation information fed back by the target network device;

Sending second information to the target network device; wherein the second information is used to assist the target network device in determining the effective duration of the UE-related information stored by the target network device, and the UE stored in the target network device determined by the UE The valid duration of the relevant information is the same.

In a fourth aspect, a handover processing method is provided, which is applied to a target network device, including:

Receive the handover request sent by the source network device;

Sending handover request confirmation information to the source network device;

Receiving second information sent by the source network device; where the second information is used to assist the target network device in determining the effective duration of the UE-related information stored by the target network device, and the information stored in the target network device determined by the UE The valid duration of UE-related information is consistent.

In a fifth aspect, a source network device is provided, including:

The first communication unit sends the first information to the user equipment UE;

Wherein, the first information is at least used to assist the UE in determining that the effective duration of UE-related information on the UE side and the network side are consistent, or used to determine the effective duration of UE-related information.

In a sixth aspect, a UE is provided, including:

The second communication unit receives the first information sent by the source network device;

In a seventh aspect, a source network device is provided, including:

The third processing unit selects the switching target network device;

The third communication unit sends a handover request to the target network device; receives the handover request confirmation information fed back by the target network device; sends second information to the target network device; wherein the second information is used to assist the target network device in determining the location The effective duration of the UE-related information stored by the target network device is consistent with the effective duration of the UE-related information stored by the target network device determined by the UE.

In an eighth aspect, a target network device is provided, including:

The fourth communication unit receives the handover request sent by the source network device;

Sending handover request confirmation information to the source network device;

In a ninth aspect, a handover processing method is provided, which is applied to a target network device, including:

Sending the first information to the source network device;

In a tenth aspect, a target network device is provided, including:

The fifth communication unit sends the first information to the source network device;

In an eleventh aspect, a terminal device is provided, including a processor and a memory. The memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory to execute the method in the above-mentioned second aspect or each of its implementation modes.

In a twelfth aspect, a network device is provided, including a processor and a memory. The memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory to execute the methods in the first aspect, the third aspect, the fourth aspect, the fifth aspect, or each implementation manner thereof.

In a thirteenth aspect, a chip is provided, which is used to implement any one of the above-mentioned first to fifth aspects or the method in each implementation manner thereof.

Specifically, the chip includes: a processor, configured to call and run a computer program from the memory, so that the device installed with the chip executes any one of the first aspect to the fifth aspect or the implementation manners thereof. method.

In a fourteenth aspect, a computer-readable storage medium is provided for storing a computer program that enables a computer to execute any one of the above-mentioned first to fifth aspects or the method in each implementation manner thereof.

In a fifteenth aspect, a computer program product is provided, including computer program instructions that cause a computer to execute any one of the above-mentioned first to fifth aspects or the method in each implementation manner thereof.

In a sixteenth aspect, a computer program is provided, which when running on a computer, causes the computer to execute any one of the above-mentioned first to fifth aspects or the method in each implementation manner thereof.

By adopting the above solution, the first information assists the UE in determining that the effective duration of its own UE-related information is consistent with the effective duration of the UE-related information on the network side, or assists in determining the effective duration of the UE-related information. In this way, it is ensured that the UE side and the network side have a corresponding understanding of the effective duration of storing UE-related information, thereby avoiding repeated access caused by the network side releasing UE-related information when the UE performs handover or random access. If necessary, increase the speed at which the UE and the network side restore the connection.

Description of the drawings

FIG. 1 is a schematic diagram 1 of a communication system architecture provided by an embodiment of the present application;

FIG. 2 is a first schematic flowchart of a handover processing method provided by an embodiment of the present application;

FIG. 3 is a second schematic diagram of the flow of a handover processing method provided by an embodiment of the present application;

FIG. 4 is a schematic diagram 1 of a scenario provided by an embodiment of the present application;

FIG. 5 is a second schematic diagram of a scenario provided by an embodiment of the present application;

FIG. 6 is a third schematic flowchart of a handover processing method provided by an embodiment of the present application;

FIG. 7 is a fourth schematic flowchart of a handover processing method provided by an embodiment of the present application;

FIG. 8 is a fifth schematic flowchart of a handover processing method provided by an embodiment of the present application;

FIG. 9 is a sixth schematic flowchart of a handover processing method provided by an embodiment of the present application;

FIG. 10 is a seventh schematic flowchart of a handover processing method provided by an embodiment of the present application;

FIG. 11 is an eighth flowchart of a handover processing method provided by an embodiment of the present application;

FIG. 12 is a ninth flowchart of a handover processing method provided by an embodiment of the present application;

FIG. 13 is a tenth schematic flowchart of a handover processing method provided by an embodiment of the present application;

FIG. 14 is an eleventh flowchart of a handover processing method provided by an embodiment of the present application;

15 is a schematic diagram 1 of the structure of a network device provided by an embodiment of the present application;

FIG. 16 is a schematic diagram of a structure of a UE provided by an embodiment of the present application;

FIG. 17 is a second schematic diagram of the composition structure of a network device provided by an embodiment of the present application;

FIG. 18 is a third schematic diagram of the composition structure of a network device provided by an embodiment of the present application;

FIG. 19 is a fourth schematic diagram of the composition structure of a network device provided by an embodiment of the present application;

20 is a schematic diagram of the structure of a communication device provided by an embodiment of the present invention;

FIG. 21 is a schematic block diagram of a chip provided by an embodiment of the present application;

FIG. 22 is a second schematic diagram of a communication system architecture provided by an embodiment of the present application.

detailed description

In order to understand the features and technical content of the embodiments of the present invention in more detail, the implementation of the embodiments of the present invention will be described in detail below with reference to the accompanying drawings. The accompanying drawings are for reference and description purposes only, and are not used to limit the embodiments of the present invention.

The technical solutions in the embodiments of the present application will be described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are a part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by those of ordinary skill in the art without creative work shall fall within the protection scope of this application.

The technical solutions of the embodiments of this application can be applied to various communication systems, such as: Global System of Mobile Communication (GSM) system, Code Division Multiple Access (CDMA) system, and Wideband Code Division Multiple Access (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), Universal Mobile Telecommunication System (UMTS), Worldwide Interoperability for Microwave Access (WiMAX) communication system or 5G system, etc.

Exemplarily, the communication system 100 applied in the embodiment of the present application may be as shown in FIG. 1. The communication system 100 may include a network device 110, and the network device 110 may be a device that communicates with a UE 120 (or called a communication terminal or a terminal). The network device 110 may provide communication coverage for a specific geographic area, and may communicate with UEs located in the coverage area. Optionally, the network equipment 110 may be a network equipment (Base Transceiver Station, BTS) in a GSM system or a CDMA system, a network equipment (NodeB, NB) in a WCDMA system, or an evolution in an LTE system Type network equipment (Evolutional Node B, eNB or eNodeB), or a wireless controller in the Cloud Radio Access Network (CRAN), or the network equipment may be a mobile switching center, a relay station, an access point, In-vehicle devices, wearable devices, hubs, switches, bridges, routers, network side devices in 5G networks, or network devices in the future evolution of the Public Land Mobile Network (PLMN), etc.

The communication system 100 also includes at least one UE 120 located within the coverage area of the network device 110. "UE" as used herein includes but is not limited to connection via wired lines, such as via public switched telephone networks (PSTN), digital subscriber lines (Digital Subscriber Line, DSL), digital cables, and direct cable connections; And/or another data connection/network; and/or via a wireless interface, such as for cellular networks, wireless local area networks (WLAN), digital TV networks such as DVB-H networks, satellite networks, AM-FM Broadcast transmitter; and/or another UE's device configured to receive/send communication signals; and/or Internet of Things (IoT) equipment. A UE set to communicate through a wireless interface may be referred to as a "wireless communication terminal", a "wireless terminal" or a "mobile terminal".

Optionally, direct terminal connection (Device to Device, D2D) communication may be performed between UEs 120.

The 3GPP RAN working group agreed to the establishment of the NR unlicensed working method (WID RP-182878) in December 2018. The goal of this project is to make NR work in the unlicensed frequency band, including the following working scenarios: carrier aggregation scenario; dual Connection work scene; independent work scene.

Generally speaking, the working band of NR-U is 5GHz unlicensed spectrum and 6GHz unlicensed spectrum, (eg, US 5925-7125MHz, or European 5925-6425MHz, or parts thereof); on unlicensed spectrum, NR -U's design should ensure fairness with other systems that are already working on these unlicensed spectrums, such as WiFi. The principle of fairness is that the impact of NR-U on systems that have been deployed on unlicensed spectrum (for example, WiFi) cannot exceed the impact between these systems.

In order to ensure fair coexistence between systems on unlicensed spectrum, energy detection has been agreed as a basic coexistence mechanism. The general energy detection mechanism is the LBT mechanism. The basic principle of the mechanism is that a network device or terminal (transmission end) needs to listen for a period of time according to regulations before transmitting data on an unlicensed spectrum. If the result of the listening indicates that the channel is idle, the transmitting end can transmit data to the receiving end. If the listening result indicates that the channel is in an occupied state, the transmitting end needs to back off for a period of time according to regulations before continuing to listen to the channel, knowing that the channel listening result is in an idle state, before transmitting data to the receiving end.

LTE LAA unlicensed frequency band channel access process:

For downlink data transmission, network equipment needs to perform LBT on unlicensed frequency bands; in LAA, the priority of channel access is determined by the following table:

Among them, Mp is related to the listening channel time for channel access. Specifically, the network device needs to perform channel listening for Td time first, where Td=16us+Mp×9us.

CWmin, p and CWmax, p are related to the random listening channel time during channel access. Specifically, when the network device listens to the channel for Td time and is idle, it needs to listen to the channel again N times, each with a duration of 9 us. Where N is a random number from 0 to CWp.

Tmcot, p is the longest time that the network device occupies the channel after it seizes the channel. It is related to the channel priority adopted by the network device. For example, if the priority is 1, the channel will be occupied for 2ms at most after the channel is successfully intercepted.

In summary, for the UE side, the network device needs to transmit data to the UE within the MCOT time. If the network device does not preempt the channel, that is, outside of the MCOT time, the UE will not receive the scheduling from the network device to the UE. data.

It should be understood that the terms "system" and "network" in this article are often used interchangeably in this article. The term "and/or" in this article is only an association relationship describing associated objects, which means that there can be three relationships, for example, A and/or B, which can mean: A alone exists, A and B exist at the same time, exist alone B these three situations. In addition, the character "/" in this text generally indicates that the associated objects before and after are in an "or" relationship.

The embodiment of the application provides a handover processing method, which is applied to a source network device, as shown in FIG. 2, including:

Step 21: Send the first information to the user equipment UE;

The following describes the solution provided by this embodiment in multiple scenarios:

Scenario 1. The target network device determines the first information and instructs it to the UE through the source network device. Specifically:

The method further includes: receiving handover request confirmation information sent by the candidate target network device, where the handover request confirmation information carries the first information.

In this scenario, the first information is carried in the handover command sent to the UE;

The first information is used to indicate the retention time of the UE related information in the target network device. The first information includes but is not limited to at least one of the following: the end time of the effective retention of UE-related information, the time period during which the UE-related information is effectively retained, the time difference information between the target network device and the source network device, and the value of the first timer The duration of the first timer when it is turned on.

Wherein, the UE-related information includes but is not limited to at least one of the following: contextual content of the UE, reserved resources/configuration, RA resources, bearer corresponding configuration, QoS (Quality of Service) parameters, and service type information.

Wherein, the time when the first timer is started may be understood as an absolute time, or expressed in a wireless frame. Among them, the absolute time can be determined based on world time.

In this scenario, the specific processing flow, combined with Figure 3, can be as follows:

The source network device selects a candidate switching target network device, and sends a switching request to the candidate target network device;

The candidate target network device makes a handover decision to determine whether it can access the UE. If possible, the candidate target network device (that is, one of the target network devices that can be accessed by the UE) will send a handover request confirmation to the source network device, and at the same time carry the first information in the message; wherein, the first timer , Used to maintain the effective duration of the UE-related information saved on the candidate target network device side. It should be pointed out that the first timer may be T304 on the network device side. The role of T304 can be shown in the following table:

It can be seen from the above table that in the handover, the T304 timer is introduced to indicate the effective handover time. T304 turns on when the handover command is received, and stops when RA is successful. If T304 times out, the handover of RA is unsuccessful, and RRC re-establishment or SCG failure information procedure is required. It is generally understood that the target network device carries the T304 of the UE in the handover request ACK, and starts the timer corresponding to T304 after the information is transmitted. When the timer expires, the target network device will delete the resource configuration reserved for the UE and UE context. Wherein, when the first timer expires, the network device releases UE-related information; when receiving a handover complete message sent by the UE, if the first timer is still running, the timer is stopped.

It should be pointed out that the first timer may also be a new timer, that is, a non-T304 timer. The target base station and/or UE determines the effective duration of UE-related information according to this new timer, or the assisting base station and/or UE determines that the effective duration of UE-related information on the UE side and the network side is consistent.

It should be pointed out that the source network device can instruct the target network device to start the first timer when the first preset condition is satisfied;

Wherein, the first preset condition includes at least one of the following:

Receive handover request confirmation message; send handover command; send handover command successfully. Wherein, the handover request confirmation information can be received when the handover request confirmation information is received, or when the first preset time period after the handover confirmation information is received; the first preset time period can be set according to actual conditions, for example, It can be 0.5ms and so on, and there is no limitation here.

Wherein, sending a handover command can be understood as the first preset condition when the source network device sends only one handover command to the UE; or, it can be the second preset after the source network device sends a handover command to the UE The duration is determined to meet the first preset condition; the second preset duration can be set according to actual conditions, and is not limited here.

The successful sending of the switching command can be understood as the moment when the switching command is successfully sent, or it can be understood as the third preset duration after the successful sending of the switching command; the third preset duration can also be set according to actual conditions and is not limited. ；

The handover command is sent successfully, or it can be understood as when the handover command sent by the UE is successfully received, or it can be understood as when the handover command sent by the UE is successfully received after the seventh preset duration; the seventh preset duration It can also be set according to the actual situation and is no longer limited. The lengths of the first preset duration, the second preset duration, the third preset duration, and the seventh preset duration may be the same or different, or may be partially the same.

In addition, the determination of the success of sending the handover command can be when the HARQ-acknowledge ACK feedback is received, or when the radio link control (RLC, Radio Link Control) ARQ-ACK is received.

The UE may use the first information to determine the time and duration to start the first timer (timer), and then determine the effective duration of the UE-related information on the network side, that is, determine the effective duration of the resource for storing UE-related information on the network side.

The time difference between the target network device and the source network device may be, for example, the time difference between the two network devices when the GPS time is not synchronized.

Based on the foregoing processing flow, referring to Figure 3 again, it may include:

The source network device sends a handover command to the UE;

The UE receives the handover command sent by the source network device, and executes the handover process according to the message of the handover command. In addition, the UE determines whether the UE-related information stored on the network device side is valid according to the first information carried in the handover command. When the UE-related information is valid, for example, the timer has not expired or the deadline for valid retention of the UE-related information has not expired, the UE performs the handover process or the RA process during the handover. Otherwise, it is considered that the handover has failed, and/or the UE performs the RRC connection re-establishment procedure (MCG handover) or indicates the SCG failure information procedure to the network.

Further, it will be described with reference to Figures 4 and 5, where the horizontal axis represents time, and from left to right represents time from small to large. Figure 4 illustrates that when the target network device side starts the first timer until the first timer expires, it saves the effective duration of UE-related information; when the UE side receives a handover command from the source network device, Starting its own first timer, it can be seen from the figure that when the first timer of the target network device expires, the first timer on the UE side has not stopped. Therefore, the UE may be in the handover process. The UE thinks that the target network device still saves related information, but the target network device actually releases the information.

As shown in Figure 5, the UE can receive the handover command sent by the source network device, and will also receive the first information carried therein, and determine the valid duration of the relevant information stored on the target network device side according to the first information. When it is determined that the target network device side has released relevant information, no more processing such as handover or random access is performed.

It can be seen that the disadvantage of the prior art is that the network may release the UE resources. At that time, the UE still believes that the current handover is feasible, resulting in unnecessary delay and signaling overhead. In this scenario, the UE can determine the effective time that the target network device actually maintains the UE context and the configured resources, avoiding the inconsistency between the UE and the network's understanding of resource reservation, and avoiding unnecessary UE behavior. For example, it has been trying RA, but the actual The network has released the UE context and so on, so that the UE can resume the connection with the network as soon as possible.

Scenario 2 is different from scenario 1 in that the first information in this scenario is generated by the source network device.

The method also includes:

Generate the first information.

The specific content of the first information in this scenario may be different from scenario 1, for example, it may include: the delay time for issuance of the handover command, or the number of times the issuance of the handover command fails.

The method also includes one of the following:

Carry the first information in the handover command;

The first information is carried in the RRC message.

That is, the source network device carries the first information in the handover command or the RRC message after the handover command. The RRC message may be a dedicated RRC message, which is used to notify the UE of the first information. The sending time of the RRC message may be sent to the UE when the handover command is issued or the first time after the handover command is issued. The time difference between the first moment and the handover command may be the fourth preset duration.

The processing of this scenario is described in conjunction with Figures 6 and 7:

The source network device selects a candidate to switch the target network device, and sends a switch request to the target network device;

The candidate target network device performs handover decision HO decision to determine whether it can access the UE. If possible, the candidate target network device will send a handover request ACK to the source network device.

The source network device generates the first information, and the first information includes at least one of the following: the delay time for the issuance of the HO command, or the number of times the issuance of the HO command fails. Correspondingly, the first information may be used to assist the UE to determine at least one of the following information: resources reserved by the target network device and/or the actual valid time/time duration/dead time of the UE context, and the configuration included in the handover command The actual valid time/time duration/expiration time of the information, the start time of the first timer of the target network device (for example, T304 timer), the start time of the target network device holding UE-related information, and the target network device holding UE-related information The deadline is the time that the timer of the target network device has been running when the handover command is received, the time when the target network device has retained UE-related information when the handover command is received, and the UE-related information remains valid in the target network device when the handover command is received time.

Among them, UE-related information includes but is not limited to at least one of the following: UE context, reserved resources/configuration, RA resources, bearer corresponding configuration, QoS parameters, and service pattern information.

Among them, the related description of the first timer is similar to scenario 1, and will not be repeated.

The source network device sends a switch command. In the manner shown in FIG. 6, the source network device sends the first information after sending the handover command, which may be carried by RRC signaling; in the manner shown in FIG. 7, the source network device may carry the first information in the handover command.

The UE receives the handover command sent by the source network device, and executes the handover process according to the message of the handover command. The UE receives the RRC message containing the first information, or the UE obtains the first information according to the handover command. The UE determines whether the UE-related information stored on the network device side is valid according to the first information. When the UE-related information is valid, for example, the timer has not expired or the deadline for valid retention of the UE-related information has not expired, the UE performs the handover process or the RA process during the handover. Otherwise, it is considered that the handover has failed, and/or the UE performs the RRC connection re-establishment procedure (MCG handover) or indicates the SCG failure information procedure to the network.

It should also be pointed out that a processing that is different from the foregoing processing flow can be:

The first information further includes at least one of the following:

Resources reserved by the target network equipment;

At least one of the actual effective time, effective duration, and deadline of the UE context;

At least one of the actual effective time, effective time, and deadline of the configuration information contained in the switching command;

The time when the first timer of the target network device is started;

The start time when the target network device holds UE-related information;

The deadline for the target network device to keep UE-related information;

The length of time the first timer of the target network device has been running when the handover command is sent;

The length of time the target network device has retained UE-related information when the handover command is sent;

The remaining effective duration of the UE related information in the target network device when the handover command is sent.

In other words, in this scenario, the source device side can confirm the auxiliary information and send it to the UE. The specific determination method and the resources reserved by the target network device can be determined by the information sent by the target network device. The valid time of the UE context can be determined according to the information sent by the target network device to determine the valid time for saving the information, the valid time, and at least one of the deadline. Since the effective time and deadline of the configuration information included in the handover command can be determined by the source network device itself according to the time when the handover command is sent by itself. In addition, the start time of the first timer in the target network device can be determined based on the handover request confirmation message sent by the target network device, and accordingly, the starting time for the target network device to retain UE-related information can be obtained; in addition, Since the source network device can obtain the duration of the first timer of the target network device, it can determine the deadline for the target network device to save UE-related information; in addition, since the source network device can determine the time when it sends the handover command, it can determine The length of time the first timer of the target network device has been running when the handover command is sent. Accordingly, the length of time the target network device has saved UE-related information when the handover command is sent, and the remaining amount of time the target network device can save UE-related information Effective duration. That is to say, the source device side can confirm the auxiliary information according to the handover request ACK message (content) from the target base station, or the source device side can confirm the auxiliary information according to the handover request ACK message (content) from the target base station and the following at least One is to confirm the auxiliary information: the delay time for the issuance of the handover command, and the number of times the issuance of the handover command fails. In this scenario, the source base station can send the updated information to the UE, or it can send all the information to the UE and the UE determines the updated information.

In this way, the processing based on the auxiliary information can be done by the source base station side. Or, the subsequent processing based on the auxiliary information can also be done by the UE side, and the source network device side can reduce its processing content.

The disadvantage of the prior art is that the network may release UE resources. At that time, the UE still believes that the current handover is feasible, resulting in unnecessary delay and signaling overhead. In this scenario, the UE can determine the effective time that the target network device actually maintains the UE context and the configured resources, avoiding the inconsistency between the UE and the network’s understanding of resource reservation, and avoiding unnecessary UE behavior (always try RA, but actually The network has released the UE context, etc.) so that the UE can resume the connection with the network as soon as possible.

Based on the above scenario 2, the following two sub-processing scenarios can also be included:

Sub-processing scenario 1,

The method also includes:

Determine the updated parameter of the first timer according to at least one of the following information, and send the updated parameter of the first timer to the UE:

The parameters of the original first timer, the delay time for handover command delivery, the number of failed handover commands, the time when the network starts the first timer, the deadline for valid retention of UE-related information, and the time period for valid retention of UE-related information , The time difference information between the target network device and the source network device, and the duration of the first timer.

For example, the source network device determines the modified T304 parameter according to one of the following information. For example, the original T304 parameter, the delay time of HO command delivery, or the number of failed HO command delivery, the time when the network starts T304/first timer, the time when T304timer on the network device side is turned on, and the deadline for valid retention of UE-related information Time, the time period during which UE-related information is effectively stored, the time difference information between the target network device and the source network device, and the duration of the first timer.

Alternatively, it may also include the parameters of the original first timer, the delay time for the issuance of the handover command, the number of times the handover command is failed to be issued, the time when the network starts the first timer, and the deadline for valid retention of UE-related information, The time period during which the UE-related information is effectively retained, the time difference information between the target network device and the source network device, and the duration of the first timer are sent to the UE so that the UE can determine the duration of the updated first timer. That is, the UE can update the duration of the first timer understood by itself to ensure that the remaining duration of the effective duration of the UE-related information stored on the network side as understood by the UE is the same as the remaining effective duration of the UE-related information stored on the network side.

In this way, the UE performs handover according to the updated T304. The updated T304 can ensure that the UE and the target network device have the same understanding of the retention time of UE-related information.

Sub scene 2,

The first information also includes:

The second duration; where the second duration is different from the duration in the parameters of the first timer.

The second duration is used to instruct the target network device for the UE to retain the effective duration of the UE-related information, or the second duration is used to make the UE and the network retain the effective duration of the UE-related information consistent. It should be pointed out that the second duration is implemented based on the second timer, that is, the second duration of the second timer is different from the duration in the parameter of the first timer (or the updated first timer).

Wherein, the method further includes: determining the parameter of the second duration based on at least one of the following information:

The parameters of the first timer, the delay time for the issuance of handover commands, the number of failed handover commands, the time when the network starts the first timer, the deadline for valid retention of UE-related information, and the time period for valid retention of UE-related information, The time difference information between the target network device and the source network device, and the duration of the first timer.

Wherein, the second duration may be implemented by a new timer, for example, it may be implemented by a second timer different from the first timer. Correspondingly, the UE starts the second timer after receiving the handover command. During the running of the second timer, the UE considers that the UE information retained by the target network device is valid.

The source network device determines the second duration by determining the effective duration of the remaining UE-related information that the source network device considers the target network device to retain; for example, the parameters of the first timer mentioned above, after the handover command has been sent multiple times When the transmission is successful, a certain time period is consumed at this time. At this time, the first timer needs to be subtracted from the time period to obtain the second time period. Alternatively, the remaining duration of the first timer may be determined according to the start time of the first timer and the time when the switching command is sent, and use it as the second duration. Or, you can combine the time difference between the target network device and the source network device, and subtract the time difference from the previously obtained second duration to obtain the adjusted second duration; because there is a time difference between the target network device and the source network device, so , There will be a certain delay when the source network device sends or receives information to the target network device, so this delay can be added to the process of correcting the second duration to obtain the adjusted second duration. Of course, the foregoing is only an example, and in fact, there may be other combinations and ways of determining the second duration, which are mainly determined based on the foregoing various parameters, which are not exhaustively listed in this embodiment.

For example, the source network device determines the timer parameter according to one of the following information, such as duration: T304 parameter/first timer parameter, the delay time for HO command delivery, or the number of failed HO command delivery, the network starts T304/ The time of the first timer, the time when the T304timer on the network device side is turned on, the deadline for valid retention of UE-related information, the time period for valid retention of UE-related information, the time difference information between the target network device and the source network device, and the duration of the first timer .

It can be seen that by adopting the above solution, the first information can assist the UE to determine that the effective duration of its own UE-related information is consistent with the effective duration of the UE-related information on the network side, or assist in determining the effective duration of the UE-related information. In this way, it is ensured that the UE side and the network side have a corresponding understanding of the effective duration of storing UE-related information, thereby avoiding repeated access caused by the network side releasing UE-related information when the UE performs handover or random access. If necessary, increase the speed at which the UE and the network side restore the connection.

The embodiment of the application provides a handover processing method, which is applied to a user equipment UE, as shown in FIG. 8, including:

Step 31: Receive the first information sent by the source network device;

Scenario 1. When the source network device sends the first information, the first information may be determined by the target network device. This scenario explains this situation.

The first information includes but is not limited to at least one of the following: the end time of the effective retention of UE-related information, the time period during which the UE-related information is effectively retained, the time difference information between the target network device and the source network device, and the value of the first timer The duration of the first timer when it is turned on.

Wherein, the UE-related information includes but is not limited to at least one of the following: contextual content of the UE, reserved resources/configuration, RA resources, bearer corresponding configuration, quality of service (QoS, Quality of Service,) parameters, service type information .

In this scenario, the specific processing flow can also be seen in Figure 3, which can be as follows:

The candidate target network device makes a handover decision to determine whether it can access the UE. If possible, the candidate target network device (that is, one of the target network devices that can be accessed by the UE) will send a handover request confirmation to the source network device, and at the same time carry the first information in the message; wherein, the first timer , Used to maintain the effective duration of the UE-related information saved on the candidate target network device side. It should be pointed out that the first timer may be T304 on the network device side. For the relevant description of T304, refer to the above-mentioned implementation manner, which will not be repeated here.

Wherein, when the first timer expires, the network device releases UE-related information; when receiving a handover complete message sent by the UE or when the RA is successful, if the first timer is still running, the timer is stopped.

The source network device sends a handover command to the UE;

The UE receives the handover command sent by the source network device, and executes the handover process according to the message of the handover command. In addition, the UE may determine the effective storage duration for storing the UE-related information on the target network device side based on the first information. For example, the UE may determine whether the UE-related information stored on the network device side is valid according to the first information carried in the handover command, or determine the effective storage duration of the UE-related information stored on the target network device side.

Specifically, methods for determining the effective storage duration may include:

According to the effective retention time of UE-related information, the deadline for saving UE-related information on the target network device side is determined, so that the UE can determine the remaining effective time during the process of performing handover or random access operation.

The time period during which the UE-related information is effectively stored can be understood as the absolute time period for storing the UE-related information on the network side. For example, it can be represented by radio frames, or can be represented by world time, so that the UE can determine the network side The effective length of time for saving its own UE-related information.

The time difference information between the target network device and the source network device, based on this information, the relative moment when the source network device obtains the first information of the target network device can be determined. For example, the target network device sends the first information at the first moment, then On the source network device side, it can be the first information acquired at the first moment + the time difference, so that when the first information is received, the remaining effective time for storing UE-related information on the target network device side can be adjusted. The effective length of time that the UE side understands the target network device side to save the UE-related information makes the two consistent. Alternatively, it is possible to determine the effective length of time for storing UE-related information on the target network device side, which is specific to the opening time and deadline for storing UE-related information. In this way, it can further ensure that the effective length of storing UE-related information confirmed by the UE side and the network side is consistent .

Based on the time when the first timer is started, and/or the duration of the first timer, the UE side can determine the effective duration for the network side to save the UE-related information based on the absolute time.

The method further includes: performing handover processing when determining that the UE-related information saved on the target network device side is valid based on the effective duration of the UE-related information saved on the target network device side, or performing random access during the handover process.入处理.

Further, the method may further include: when it is determined that the UE-related information stored on the target network device side is invalid based on the effective duration of the UE-related information stored on the target network device side, performing at least one of the following:

Confirm that the handover fails; perform the RRC connection re-establishment process; indicate the SCG failure information process to the network.

That is, when the UE determines that the UE-related information is valid, for example, the timer has not expired, or the deadline for valid retention of the UE-related information has not been reached, the UE performs the handover process or the RA process during the handover. Otherwise, it is considered that the handover has failed, and/or the UE performs the RRC connection re-establishment procedure (MCG handover) or indicates the SCG failure information procedure to the network.

The method also includes one of the following:

Obtain the first information carried by the handover command; obtain the first information carried by the RRC message.

The candidate target network device makes a HO decision to determine whether it can access the UE. If possible, the candidate target network device will send a handover request ACK to the source network device.

The UE receives the handover command sent by the source network device, and executes the handover process according to the message of the handover command. The UE receives the RRC message containing the first information.

The UE determines whether the UE-related information stored on the network device side is valid according to the first information. When the UE-related information is valid, for example, the timer does not expire or the deadline for valid retention of the UE-related information is not reached, the UE performs the handover process or the RA process during the handover. Otherwise, it is considered that the handover has failed, and/or the UE performs the RRC connection re-establishment procedure (MCG handover) or indicates the SCG failure information procedure to the network.

At this time, the UE can determine the following information: resources reserved by the target network device;

The time when the first timer of the target network device is started;

The start time when the target network device holds UE-related information;

The deadline for the target network device to keep UE-related information;

The specific determination method, the resources reserved by the target network device can be determined by the information sent by the source network device. The valid time of the UE context may be determined according to at least one of the termination time of the valid retention of the UE-related information and the time period during which the UE-related information is effectively retained. The start time of the first timer in the target network device can be determined based on the received first information, and accordingly, the start time at which the target network device retains UE-related information can be obtained; in addition, since the source network device can obtain the target network device The duration of the first timer of the target network device can therefore determine the deadline for the target network device to save UE-related information; in addition, since the UE can determine the moment when it receives the handover command, it can determine the first timing of the target network device when the handover command is received The length of time the device has been running, accordingly, it can be determined that when the handover command is received, the length of time the target network device has saved UE-related information, and the remaining effective length of time that the target network device can save UE-related information.

The foregoing information may be carried in the first information, that is to say, the first information sent by the source network device may also include at least one of the following:

Resources reserved by the target network equipment;

The time when the first timer of the target network device is started;

The start time when the target network device holds UE-related information;

The deadline for the target network device to keep UE-related information;

How to determine the foregoing information on the source network device side has been described in the foregoing embodiments, and will not be repeated here.

Sub-processing scenario 1,

The first information further includes: the updated first timer.

The source network device side modifies the parameters of the first timer, and then sends the updated first timer to the UE.

Alternatively, it is also possible to receive a parameter for modifying the first timer sent by the source network device, and update the first timer based on the parameter for modifying the first timer.

Among them, the parameters may include at least one of the following: the parameters of the original first timer, the delay time for the issuance of the handover command, the number of times the handover command fails to be issued, the time for the network to start the first timer, and the effective retention of UE-related information. Time, the time period during which UE-related information is effectively stored, the time difference information between the target network device and the source network device, and the length of the original first timer.

The UE determines the updated first timer according to one of the following information. For example, if the original T304 parameter is combined with the delay time for issuing the HO command, it is determined that the switching command will be sent a period of time after the first timer is started, then the original first duration of the first timer can be subtracted from this delay , Get the updated duration of the first timer. Or, the number of failed delivery of the HO command contained in the first information is used to determine the delay caused by several failed delivery of the handover command, combined with the length of the original first timer or the start of the first timer Time, to determine that if the UE side wants to be consistent with the network side, the first timer needs to be adjusted. For example, the first time length of the first timer is subtracted from the delivery failure time delay to obtain the updated first timer. Of course, the foregoing processing can also be combined with the effective retention deadline of the UE-related information, combined with the current time, to determine that the UE needs to adjust the first duration of the first timer. It should be understood that there may also be other adjustment methods, but the list is not exhaustive in this embodiment.

In this way, the UE performs handover according to the updated first timer, such as T304. Since the duration of the first timer is modified according to the related modification parameters, the UE side starts the updated first timer to determine the effective duration of the network side to save the UE-related information, which can keep the UE-related information with the target network device side. The remaining effective duration remains consistent, so that the updated T304 can ensure that the UE and the target network device have the same understanding of the retention time of the UE-related information.

Sub scene 2,

The first information also includes:

The second duration; where the second duration is different from the duration in the parameters of the first timer

The second duration is used to instruct the target network device for the UE to retain the effective duration of the UE-related information, or the second duration is used to make the UE and the network retain the effective duration of the UE-related information consistent.

The second duration is different from the duration of the first timer.

In this scenario, similarly, the second duration can also be determined by itself according to the information delivered by the source network device, for example, including at least one of the following:

For example, the second timer or the second duration parameter is determined according to one of the following information, such as duration: T304 parameter, the delay time of HO command delivery, or the number of failed HO command delivery, the network starts T304/first Timer time, T304timer on the network device side, deadline for valid retention of UE-related information, time period for valid retention of UE-related information, time difference information between the target network device and the source network device, and the duration of the first timer.

The way to determine the second duration can be to determine the second duration for the effective duration of the remaining UE-related information considered by the target network device; for example, for the parameters of the aforementioned first timer, the handover command is successfully sent after multiple failures. At this time, a certain period of time is consumed. At this time, the first timer needs to be subtracted from the period to obtain the second period. Alternatively, the remaining duration of the first timer may be determined according to the start time of the first timer and the time when the switching command is sent, and use it as the second duration. Or, you can combine the time difference between the target network device and the source network device, and subtract the time difference from the previously obtained second duration to obtain the adjusted second duration; because there is a time difference between the target network device and the source network device, so , There will be a certain delay when the source network device sends or receives information to the target network device, so this delay can be added to the process of correcting the second duration to obtain the adjusted second duration. Of course, the foregoing is only an example, and in fact, there may be other combinations and ways of determining the second duration, which are mainly determined based on the foregoing various parameters, which are not exhaustively listed in this embodiment.

On the basis of the foregoing multiple scenarios, combined with one or more of the foregoing multiple scenarios, this embodiment can also provide the following more processing scenarios. It should be pointed out that the following scenarios can also be used alone, or In other words, the following two processing scenarios can be executed without executing the processing provided by the foregoing embodiment, which are specifically as follows:

Processing scenario 1,

Perform handover based on the handover command, and fall back from non-contention-based random access to contention-based random access when a third preset condition is met during the handover process;

The third preset condition includes at least one of the following:

Random access resources based on non-competition are invalid;

Random access based on non-contention fails.

That is to say, during the handover process, when the UE fails in contention-based random access (CFRA, Contention Free Random Access), or when CFRA resources are invalid, the UE falls back from CFRA to contention-based random access (CBRA). , Contention Based Random Access).

See Figure 9, which may include:

The candidate target network device makes a HO decision to determine whether it can access the UE. If possible, the candidate target network device will send a handover request confirmation message to the source network device.

The source network device sends a switch command.

The UE executes the handover process according to the handover command, including the CFRA process. When at least one of the following third preset conditions is met, the UE rolls back from the CFRA process to the CBRA process: CRFA resources are invalid and CFRA fails.

When the UE fails in random access based on non-contention, it can indicate the random access failure to the higher layer.

Alternatively, the random access failure may not be indicated to the higher layer. Specifically, the method further includes: when the non-contention-based random access fails, not indicating the random access failure to the higher layer. That is to say, when the UE side judges that CFRA fails (or CFRA is invalid), the Media Access Control (MAC, Media Access Control) layer does not indicate random access failure (Random Access problem) to the higher layer.

Since it is uncertain whether the network side releases the UE context and the resource configuration reserved for the UE at the same time, there may be a problem that CFRA resources are not valid or CFRA fails when UE-related information such as the UE context is reserved. According to the existing agreement, if RA is directly considered to have failed, or re-establishment is triggered, or SCG change failure is triggered, without falling back to the UE CBRA process, it will cause the UE to access the network delay, and even miss the MCOT due to the delayed UE access. Time leads to long delays in the communication between the UE and the network, resulting in problems such as reduced service QoS and poor UE experience. In this processing scenario, this problem can be solved by returning CBRA and/or not reporting the RA problem.

Processing scenario 2,

In this scenario, multiple sets of non-contention random access resources can be configured for the UE.

The method also includes one of the following:

Processing is based on at least one set of non-competitive random access resources among multiple sets of non-competitive random access resources; when processing based on at least one set of non-competitive random access resources fails, random access is not indicated to the higher layer failure;

Perform processing based on at least one set of non-competitive random access resources among multiple sets of non-competitive random access resources; when processing based on at least one set of non-competitive random access resources fails, indicate random access failure to higher layers ；

Processing is performed based on the first non-competition-based random access resource among multiple sets of non-competition random access resources; when it is determined that the processing of the first non-competition-based random access resource fails, if there is a Non-competitive random access resources other than non-competitive random access resources will not indicate random access failure to the higher layer;

The processing is performed based on the first non-competition-based random access resource among the multiple sets of non-competition random access resources; when it is determined that the processing of the first non-competition-based random access resource fails, if there is a Other non-competitive random access resources other than the non-competitive random access resources indicate random access failure to the higher layer.

Specifically, the UE may perform processing through one set of non-contention random access resources. At this time, if a failure occurs, the random access failure can be indicated to the higher layer. Then the UE can again select another set of non-competitive random access resources for access.

This processing scenario may include: multiple sets of non-contention random access resources may be configured for the UE. At this time, the UE can perform processing through at least one set of non-contention random access resources. At this time, when any one set of access fails, the random access failure can be indicated to the upper layer, or the random access failure can not be indicated to the upper layer. Or, when all access fails, the random access failure may be indicated to the upper layer, or the random access failure may not be indicated to the upper layer.

In addition, this processing scenario may include: multiple sets of non-contention random access resources may be configured for the UE. At this time, when it is determined that the processing of the first non-contention-based random access resource has failed, if there are other non-competition random access resources other than the first non-contention-based random access resource, then no The upper layer indicates random access failure.

In other words, the UE can perform processing through one set of non-contention random access resources. At this time, if a failure occurs, the random access failure may not be indicated to the higher layer. Then the UE can again select another set of non-competitive random access resources for access.

The difference from the aforementioned processing scenario 1 is that multiple sets of CFRA resources can be set in this scenario. Among different CFRA resources, at least one of the following configurations is different: the valid start of the resource is different, the PRACH scenario occurrence identifier index is different, and the PRACH The resource time domain/frequency domain position interval is different, and the preamble identifier index of the preamble sequence is different.

Referring to Figure 10, this processing scenario may include the following processing steps:

The candidate target network device performs handover decision HO decision to determine whether it can access the UE. If possible, the candidate target network device will send a handover request ACK to the source network device. Among them, the target network device is configured with at least one set of CFRA resources, where different CFRA resources have at least one different configuration. The specific configuration content is as shown above, and will not be repeated here. In this way, multiple sets of CFRA resources can be utilized, the locations of the RA resources that can be tried are increased, the total valid time of the CFRA resources is increased, and the chance of success of the RA is improved.

Among them, different CFRA resources can correspond to different usage priorities, and the usage priorities of different CFRA resources can be configured for the UE.

The source network device sends a switch command. The handover command carries at least one set of CFRA resources as described above, which can be understood as the first CFRA resource.

The UE executes the handover process according to the message content in the handover command, including the CFRA process.

In this process, the UE can determine that CFRA has failed but there are other CFRA resources corresponding to the RA that has not been attempted, the MAC does not indicate the random access failure to the upper layer; or, when multiple sets of CFRA attempts fail, the MAC also does not report to the upper layer Indicates random access failure.

For example, configure three sets of CFRA resources for the handover UE. The start time of each set of resource valid is different, such as T1, T2, and T3. If the handover command is received by the UE between T1 and T2, the UE The CFRA process is performed using the CFRA resources corresponding to time T2 and/or time T3.

For another example, two sets of CFRA resources are configured for the handover UE. Each set of resources has a different PRACH occurrence index. For example, one is index1 and the other is index2. Due to LBT, the UE sends the handover request ACK long after the target network device before receiving the HO command. Improve the resource location/opportunity of CFRA that the UE can try. The UE uses two sets of CFRA resources to perform the CFRA process to increase the chance of the UE accessing the target network within the limited MCOT time.

For another example, two sets of CFRA resources are configured for the handover UE, and the start time of each set of resource valid is different. For example, it is valid from T1 and T2. Due to LBT, the UE sends the handover request ACK long after the target network device sends the HO before receiving the HO. command. At this time, a set of CFRA may not be valid. In order to improve the resource location/opportunity of CFRA that the UE can try, the UE uses two sets of CFRA resources to perform the CFRA process to increase the UE's access to the target network within the limited MCOT time Opportunity.

For another example, configure 2 sets of CFRA resources to the handover UE, and optionally notify the priority of each set of resources at the same time. The UE first uses the high-priority CFRA resources or one set of CFRA resources to perform the RA process. If the RA fails, the UE does not report the RA problem, and then tries to use another set of CFRA resources to perform the RA process until the RA fails or the RA succeeds. The advantage is to increase the chance of UE accessing the target network within the limited MCOT time.

Since it is uncertain whether the network side releases the UE context and the resource configuration reserved for the UE at the same time, there may be a problem that CFRA resources are not valid or CFRA fails when UE-related information such as the UE context is reserved. According to the existing agreement, if RA is directly considered to have failed, or re-establishment is triggered, or SCG change failure is triggered, without falling back to the UE CBRA process, it will cause the UE to access the network delay, and even miss the MCOT due to the delayed UE access. Time leads to long delays in the communication between the UE and the network, resulting in problems such as reduced service QoS and poor UE experience. This solution solves this problem by configuring/carrying at least one CFRA resource.

The embodiment of the present application provides a handover processing method, which is applied to a source network device, as shown in FIG. 11, including:

Step 41: Select the switching target network device, and send a switching request to the target network device;

Step 42: Receive handover request confirmation information fed back by the target network device;

Step 43: Send second information to the target network device; where the second information is used to assist the target network device in determining the effective duration of the UE-related information stored by the target network device and the target network device determined by the UE The valid duration of the saved UE-related information is consistent.

That is to say, the impact on the air interface and the UE is not involved in this embodiment, and the effect similar to the foregoing embodiment is achieved in the manner of network-side interaction.

After the handover command is sent by the source network device or after the handover command is successfully sent, specific indication information can be sent to the target network device/candidate target network device, such as a handover command sending confirmation message, to ensure that the UE and the target network device have relevant information about the UE Whether the understanding is valid or not is consistent, or indicate to the target network device that the handover command to the UE is sent successfully, or indicate to the target network device that the resource maintenance/timer maintenance state restarts.

Before sending the second information to the target network device, the method further includes:

Send a handover command to the UE; or send a handover command to the UE successfully; or, receive an indication that the UE has successfully received the handover command. Among them, sending a handover command to the UE can be understood as the source network device sending a handover command to the UE for the first time; in addition, sending the second information can be the fifth preset time period after the handover command is sent for the first time; of course, if The source network device can send the handover command multiple times, it can also be understood as sending the handover command for the second time, or the third time, which will not be exhaustive here. The successful sending of the handover command to the UE may be that when the confirmation information fed back by the UE is received, the handover command is considered to be successfully sent. In addition, the timing of sending the second information may be the time when the handover command is confirmed to be successfully sent, or the confirmation When the sixth preset duration after the switch command is successfully sent. The fifth preset duration and the sixth preset duration may be the same or different. In another case, the second message can be sent when the UE receives the indication of the successful reception of the handover command; here, it can also be specifically that the second message is sent when the indication of the successful reception of the handover command is received. The information can also be a period of time after receiving the indication that the handover command is successfully received, and then the second message is sent; here, the period of time can be set according to the actual situation, and it is not exhaustive.

Refer to 12 in this embodiment, and the process may include:

The source network device selects the candidate handover target network device and sends a handover request to the candidate target network device; optionally, the source network device notifies the target network device of the cell type of the cell, such as whether it is an NR-U cell, and/or Request the cell type of the candidate target cell from the target network device, such as whether it is an NR-U cell. Optionally, the above information is carried in the handover request message.

The candidate target network device makes a HO decision to determine whether it can access the UE. If possible, the candidate target network device will send a handover request ACK to the source network device. Optionally, the candidate target network device notifies the source network device of the cell type information of the candidate target cell. For example, the handover request ACK message carries the cell type information of the candidate target cell, such as whether it is an NR-U cell.

After the source network device sends an air interface handover command to the UE, or after the source network device sends the air interface handover command successfully, or after receiving the UE’s indication of the successful reception of the handover command, it sends a specific target network device/candidate target network device Indication message/information, such as a handover command sending confirmation message, that is, second information can be sent. The second information includes at least one of the following: indicating to the target network device that the handover command sent by the source network device to the UE is successfully sent; indicating to the target network device that the source network device has sent the handover command; indicating to the target network device a resource maintenance behavior /State reset; Instruct the target network device to restart the first timer; Instruct the target network device for the second duration; Instruct the target network device to start the timer for the UE; Instruct the target network device that the UE considers the target base station UE related information valid .

The second information, that is, a specific indication message/information, is used to ensure that the UE and the target network device have the same understanding of whether the UE-related information is valid, or indicate to the target network device that the handover command sent by the source network device to the UE is successfully sent, or , The source network device has sent a handover command, or instructs the target network device to perform resource maintenance actions/status reset, or instruct the target network device to restart the timer maintenance status.

The second message can be sent so that the target network device determines to start the first timer according to the indication that the handover command in the second message is successfully sent. Since the UE side will start the handover process when the handover command is received At this time, the UE will start to determine the effective length of time the target network device side saves UE-related information. When the target network device is indicated through the second information, the target network device starts the first timer at the same time as the target network device side understood by the UE. The time of the first timer can be basically consistent, so that the effective duration of the storage of the UE-related information on the target network device side can be consistent with the understanding of the UE side. Or, the source network device indicates to the target network device that the handover command is currently sent. At this time, the target network device can start the first timer to determine the valid duration of the UE-related information, which can also make the target network device start the first timer It is consistent with the time when the target network device side starts the first timer confirmed by the UE side. Or, by instructing the target network device to restart the first timer to indicate the start time of the first timer, the information can also be determined by referring to the time when the handover command is successfully sent. For example, when the handover command is successfully sent, it can be understood as The UE thinks that the first timer on the target network device side has started, and then the source network device instructs the target network device to restart the first timer so that the restart time of the first timer on the target network device side is the same as the UE side. Keep consistent, so that the effective duration of saving UE-related information understood by the UE side and the network side is consistent. Alternatively, the resource maintenance behavior and/or state reset can also be instructed to the target network device, that is, the resource maintenance behavior of the control target network device is processed based on sending a handover command or successfully sending a handover command, or according to sending a handover command Or at the moment when the handover command is successfully sent, the effective duration of saving the state of the UE-related information on the target network device side is reset. In another case, the second duration is indicated to the target network device. The second duration may be the effective duration that the source network device understands the UE side thinks the target network device saves UE-related information, and the second duration is indicated to the target network device , Can make the target network device and the UE keep the same effective duration.

Among them, UE-related information includes but is not limited to at least one of the following: UE context, reserved resources/configuration, RA resources, bearer corresponding configuration, QoS parameters, service pattern information

The disadvantage of the prior art is that the network may release UE resources. At that time, the UE still believes that the current handover is feasible, resulting in unnecessary delay and signaling overhead. This embodiment avoids the impact on the air interface and the UE, and achieves similar effects in a manner of network side interaction.

On the basis of the foregoing multiple scenarios, combined with one or more of the foregoing multiple scenarios, this embodiment may also provide the following more processing scenarios. It should be pointed out that the following scenarios can also be used alone, that is, the following two processing scenarios can be executed without performing the processing provided in the foregoing embodiment, as follows:

Processing scenario 1,

Configure non-contention-based random access resources for the UE;

Correspondingly, the UE performs handover based on the handover command, and during the handover process, when the third preset condition is met, fall back from non-contention-based random access to contention-based random access;

The third preset condition includes at least one of the following:

Random access resources based on non-competition are invalid;

Random access based on non-contention fails.

That is to say, during the handover process, when the UE fails in contention-based random access (CFRA, Contention Free Random Access), or when CFRA resources are invalid, the UE falls back from CFRA to contention-based random access (CBRA). , Contention Based Random Access). At this time, the UE may report random access failure, or may not report it.

The specific processing flow is consistent with the detailed description of processing scenario 1 provided in the foregoing embodiment, and will not be repeated here.

Processing scenario 2: Multiple sets of non-contention random access resources can be indicated for the UE.

This embodiment may further include: the method further includes:

Send a handover command to the UE;

Wherein, the handover command carries at least one set of non-competition-based random access resources, or the handover command carries at least one set of non-competition-based random access resources and the priority of each set of non-competition-based random access resources. level.

Wherein, at least one of the following information of different non-competition-based random access resources is different:

The effective start of the resource is different, the PRACH timing identifier is different, the time domain/frequency domain position interval of the PRACH resource is different, the preamble sequence parameter is different, and the preamble sequence identifier is different.

In this scenario, multiple sets of non-contention random access resources can be configured for the UE. At this time, the UE can perform processing through one set of non-contention random access resources. At this time, if a failure occurs, the random access failure can be indicated to the higher layer. Then the UE can again select another set of non-competitive random access resources for access.

This processing scenario may include: multiple sets of non-contention random access resources may be configured for the UE. At this time, the UE can perform processing through at least one set of non-contention random access resources. At this time, when any one set of access fails, the random access failure can be indicated to the upper layer, or the random access failure can not be indicated to the upper layer. Or, it can also indicate random access failure to higher layers when all access fails, or not indicate random access failure to higher layers

The specific processing flow is consistent with the detailed description of processing scenario 2 provided in the foregoing embodiment, and will not be repeated here.

Since it is uncertain whether the network side releases the UE context and the resource configuration reserved for the UE at the same time, there may be a problem that CFRA resources are not valid or CFRA fails when UE-related information such as the UE context is reserved. According to the existing agreement, if RA is directly considered to have failed, or re-establishment is triggered, or SCG change failure is triggered, without falling back to the UE CBRA process, it will cause the UE to access the network delay, and even miss the MCOT due to the delayed UE access. Time leads to long delays in the communication between the UE and the network, resulting in problems such as reduced service QoS and poor UE experience. This problem is solved by configuring/carrying at least one CFRA resource.

The embodiment of the application provides a handover processing method, which is applied to a target network device, as shown in FIG. 13, including:

Step 51: Receive a handover request sent by the source network device;

Step 52: Send handover request confirmation information to the source network device;

Step 53: Receive second information sent by the source network device; where the second information is used to assist the target network device in determining the effective duration of the UE-related information stored by the target network device and the target network determined by the UE The valid duration of UE-related information saved by the device is consistent.

In this embodiment, the process may include:

After the source network device sends an air interface handover command to the UE, or the source network device sends a specific indication message/information to the target network device/candidate target network device after the air interface handoff command is successfully sent, such as a handover command sending confirmation message, that is The second message can be sent. The second information includes at least one of the following:

An indication that the handover command sent by the source network device to the UE is successfully sent;

An indication that the source network device has sent a handover command;

Resource maintenance actions/state reset instructions;

An indication that the first timer is restarted;

Instructions for the second duration.

That is, the second information, that is, the specific indication message/information, is used to ensure that the UE and the target network device have the same understanding of whether the UE-related information is valid, or indicate to the target network device the handover command sent by the source network device to the UE The transmission is successful, or the source network device has sent a switching command, or instructs the resource maintenance behavior/status reset to the target network device, or instructs the target network device to restart the timer maintenance state.

That is to say, the second information can be sent to enable the target network device to determine to start the first timer according to the indication that the handover command in the second information is successfully sent. Because the UE side only receives the handover command, it Start the handover process. At this time, the UE will start to determine the effective duration of the storage of UE-related information on the target network device side. When the target network device is indicated through the second information, the time when the target network device starts the first timer is consistent with the target understood by the UE. The time when the network device side starts the first timer can be basically the same, so that the effective duration of the UE-related information on the target network device side can be kept consistent with what the UE side understands. Or, the source network device indicates to the target network device that the handover command is currently sent. At this time, the target network device can start the first timer to determine the valid duration of the UE-related information, which can also make the target network device start the first timer It is consistent with the time when the target network device side starts the first timer confirmed by the UE side. Or, by instructing the target network device to restart the first timer to indicate the start time of the first timer, the information can also be determined by referring to the time when the handover command is successfully sent. For example, when the handover command is successfully sent, it can be understood as The UE thinks that the first timer on the target network device side has started, and then the source network device instructs the target network device to restart the first timer so that the restart time of the first timer on the target network device side is the same as the UE side. Keep consistent, so that the effective duration of saving UE-related information understood by the UE side and the network side is consistent. Alternatively, the resource maintenance behavior and/or state reset can also be instructed to the target network device, that is, the resource maintenance behavior of the control target network device is processed based on sending a handover command or successfully sending a handover command, or according to sending a handover command Or at the moment when the handover command is successfully sent, the effective duration of saving the state of the UE-related information on the target network device side is reset. In another case, the second duration is indicated to the target network device. The second duration may be the effective duration that the source network device understands the UE side thinks the target network device saves UE-related information, and the second duration is indicated to the target network device , Can make the target network device and the UE keep the same effective duration.

Processing scenario 1,

Configure a non-contention-based random access resource for the UE; the random access resource may be configured for the UE by the target base station, and then sent to the UE through the source network device.

The method also includes:

Send at least one set of non-competition-based random access resources to the source network device, or,

Send at least one set of non-competition-based random access resources and the priority of each set of non-competition-based random access resources to the source network device.

It should be understood that, in this embodiment, at least one set of non-competition-based random access resources, or at least one set of non-competition random access resources and their corresponding priorities, sent to the source network device, is ultimately sent to the source network device. Sent to UE.

Other specific processing procedures are consistent with the detailed description of processing scenario 2 provided in the foregoing embodiment, and will not be repeated here.

The embodiment of the application provides a handover processing method, which is applied to a target network device, as shown in FIG. 14, includes:

Step 61: Send the first information to the source network device;

In this embodiment, the target network device determines the first information and instructs it to the UE through the source network device. Specifically:

The method further includes: sending handover request confirmation information to the source network device, where the handover request confirmation information carries the first information.

It should be pointed out that the method for the target network device to determine the first information can be to obtain the effective duration of its own storage of UE-related information, and then determine the termination of the effective retention of UE-related information based on the current time and the time when the first timer is started. Time; or, combined with the time difference information between the target network device and the source network device, to determine the time when the source network device receives the handover request confirmation information, determine the time when the first timer is started, and carry both parameters In the first information, when the UE side receives the first information, it can determine the effective duration for the target network device to save the UE-related information. In addition, the duration of the first timer can be determined by the target network device itself, so it can be directly added to the first information.

The candidate target network device makes a handover decision to determine whether it can access the UE. If possible, the candidate target network device (that is, one of the target network devices that can be accessed by the UE) will send a handover request confirmation to the source network device, and at the same time carry the first information in the message; wherein, the first timer , Used to maintain the effective duration of the UE-related information saved on the candidate target network device side. It should be pointed out that the first timer may be T304 on the network device side. The description of T304 is as mentioned before, and will not be repeated here.

It should be pointed out that when the second preset condition is met, the first timer is started;

Wherein, the second preset condition includes at least one of the following:

The target network device sends a handover request confirmation message; receives a message sent by the source network device indicating to start the first timer; and receives the second message.

Wherein, the target network device sending the handover request confirmation information can be when the handover request confirmation information is sent, or the first moment after the handover confirmation information is sent; the first moment can be set according to the actual situation, for example, it can be 0.6ms, etc. Wait, there is no limit here.

Wherein, receiving the message sent by the source network device instructing to start the first timer may be the moment when the instruction information sent by the source network device to start the first timer is received, the first timer is started, or it may also be At a second time after receiving the instruction message to start the first timer from the source network device, the first timer is started. Among them, the second time can be set according to the actual situation, for example, it can be set to 1ms.

The received second information may be receiving the second information sent by the source network device, and the second information is used to assist the target network device in determining the effective duration of the UE-related information stored by the target network device, which is determined by the UE. The effective duration of the UE-related information saved by the target network equipment is the same. By receiving the second information, it can be considered that the source network device has successfully sent the handover instruction, and based on the indication of the second information, the target network device can determine that the first timer needs to be started.

Based on the foregoing processing flow, referring to Figure 3 again, it may also include:

The source network device sends a handover command to the UE;

The UE receives the handover command sent by the source network device, and executes the handover process according to the message of the handover command.

The embodiment of the application provides a source network device, as shown in FIG. 15, including:

The first communication unit 71 sends the first information to the user equipment UE;

The first communication unit 71 receives handover request confirmation information sent by the candidate target network device, where the handover request confirmation information carries the first information.

It should be pointed out that the source network device may further include: a first processing unit 72, which may instruct the target network device to start the first timer when the first preset condition is satisfied;

Wherein, the first preset condition includes at least one of the following:

Receive handover request confirmation message; send handover command; send handover command successfully.

Wherein, the handover request confirmation information can be received when the handover request confirmation information is received, or when the first preset time period after the handover confirmation information is received; the first preset time period can be set according to actual conditions, for example, It can be 0.5ms and so on, and there is no limitation here.

The successful sending of the switching command can be understood as the moment when the switching command is successfully sent, or it can be understood as the third preset duration after the successful sending of the switching command; the third preset duration can also be set according to the actual situation and is no longer limited; The handover command is successful, or it can be understood as when the handover command sent by the UE is successfully received, or it can be understood as when the handover command sent by the UE is successfully received after the seventh preset duration; the seventh preset duration is also It can be set according to the actual situation and is no longer limited. The lengths of the first preset duration, the second preset duration, the third preset duration, and the seventh preset duration may be the same or different, or may be partially the same.

The first processing unit 72 generates first information.

The first communication unit 71 also performs one of the following:

Carry the first information in the handover command;

The first information is carried in the RRC message.

Sub-processing scenario 1,

The first processing unit 71 determines the updated parameters of the first timer according to at least one of the following information, and the first communication unit sends the updated parameters of the first timer to the UE:

Sub scene 2,

The first information also includes:

The second duration; where the second duration is different from the duration in the parameters of the first timer;

Wherein, the first processing unit 72 determines the parameter of the second duration based on at least one of the following information:

The embodiment of the present application provides a UE, as shown in FIG. 16, including:

The second communication unit 81 receives the first information sent by the source network device;

Further, the UE may further include: a second processing unit 82, based on the effective duration of the UE-related information stored on the target network device side, when determining that the UE-related information stored on the target network device side is invalid, perform at least the following one:

That is, when it is determined that the UE-related information is valid, for example, the timer has not expired, or the deadline for valid retention of the UE-related information has not been reached, the UE performs the handover process or the RA process during the handover. Otherwise, it is considered that the handover has failed, and/or the UE performs the RRC connection re-establishment procedure (MCG handover) or indicates the SCG failure information procedure to the network.

The method also includes one of the following:

At this time, the second processing unit 82 may determine the following information: resources reserved by the target network device;

The time when the first timer of the target network device is started;

The start time when the target network device holds UE-related information;

The deadline for the target network device to keep UE-related information;

Resources reserved by the target network equipment;

The time when the first timer of the target network device is started;

The start time when the target network device holds UE-related information;

The deadline for the target network device to keep UE-related information;

Sub-processing scenario 1,

The first information further includes: the updated first timer.

Alternatively, the second communication unit 81 may also: receive a parameter for modifying the first timer sent by the source network device, and the second processing unit 82 may update the first timer based on the parameter for modifying the first timer .

Sub scene 2,

The first information further includes: a second duration; where the second duration is different from the duration in the parameter of the first timer.

The second duration is different from the duration of the first timer.

In this scenario, similarly, the second processing unit 82 may also determine the second duration by itself according to the information issued by the source network device.

Processing scenario 1,

The second processing unit 82 performs handover based on the handover command, and during the handover process, when a third preset condition is met, fall back from non-contention-based random access to contention-based random access;

The third preset condition includes at least one of the following:

Random access resources based on non-competition are invalid;

Random access based on non-contention fails.

The second processing unit 82, when the non-contention-based random access fails, may indicate the random access failure to the higher layer through the second communication unit 81.

Processing scenario 2. The second processing unit performs one of the following:

The processing is performed based on the first non-competition-based random access resource among the multiple sets of non-competition random access resources; when it is determined that the processing of the first non-competition-based random access resource fails, if there is a Non-competitive random access resources other than non-competitive random access resources will not indicate random access failure to the higher layer;

Specifically, in this scenario, multiple sets of non-contention random access resources can be configured for the UE through the second communication unit. At this time, the second processing unit controls to perform processing through one set of non-competitive random access resources. At this time, if a failure occurs, the second communication unit can indicate the random access failure to the higher layer. Then you can select another set of non-competitive random access resources for access.

This processing scenario may include: multiple sets of non-contention random access resources may be configured for the UE. At this time, the second processing unit 82 controls to perform processing through at least one set of non-competitive random access resources. At this time, when any one set of access fails, the random access failure can be indicated to the upper layer, or the random access failure can not be indicated to the upper layer. Or, it can also indicate random access failure to higher layers when all access fails, or not indicate random access failure to higher layers

In addition, this processing scenario may include: a second processing unit 82, when it is determined that the processing of the first non-competition-based random access resource fails, if there are other than the first non-contention-based random access resource For other non-competitive random access resources, no random access failure is indicated to the higher layer.

The embodiment of the application provides a source network device, as shown in FIG. 17, including:

The third processing unit 91 selects a handover target network device;

The third communication unit 92 sends a handover request to the target network device; receives the handover request confirmation information fed back by the target network device; sends second information to the target network device; wherein the second information is used to assist the target network device in determining The effective duration of the UE-related information stored by the target network device is consistent with the effective duration of the UE-related information stored by the target network device determined by the UE.

Before sending the second information to the target network device, the third processing unit 91 sends a handover command to the UE; or, successfully sends a handover command to the UE, or receives an indication that the UE has successfully received the handover command.

Among them, sending a handover command to the UE can be understood as the source network device sending a handover command to the UE for the first time; in addition, sending the second information can be the fifth preset time period after the handover command is sent for the first time; of course, if The source network device can send the handover command multiple times, it can also be understood as sending the handover command for the second time, or the third time, which will not be exhaustive here. The successful sending of the handover command to the UE may be that when the confirmation information fed back by the UE is received, the handover command is considered to be successfully sent. In addition, the timing of sending the second information may be the time when the handover command is confirmed to be successfully sent, or the confirmation When the sixth preset duration after the switch command is successfully sent. The fifth preset duration and the sixth preset duration may be the same or different. In another case, the second message can be sent when the UE receives the indication of the successful reception of the handover command; here, it can also be specifically that the second message is sent when the indication of the successful reception of the handover command is received. The information can also be a period of time after receiving the indication that the handover command is successfully received, and then the second message is sent; here, the period of time can be set according to the actual situation, and it is not exhaustive.

Processing scenario 1,

The third communication unit 92 configures non-contention-based random access resources for the UE.

The detailed description is provided in the front of this processing scenario, so I won't repeat it here.

Processing scenario 2,

The third communication unit 92 sends a handover command to the UE;

The embodiment of the application provides a target network device, as shown in FIG. 18, including:

The fourth communication unit 1001 receives a handover request sent by a source network device; sends a handover request confirmation message to the source network device; receives second information sent by the source network device; wherein the second information is used to assist the target The network device determines that the effective duration of the UE-related information stored by the target network device is consistent with the effective duration of the UE-related information stored by the target network device determined by the UE.

Before sending the second information to the target network device, the fourth communication unit 1001 sends a handover command to the UE; or, successfully sends a handover command to the UE. Among them, sending a handover command to the UE can be understood as the source network device sending a handover command to the UE for the first time; in addition, sending the second information can be the fifth preset time period after the handover command is sent for the first time; of course, if The source network device can send the handover command multiple times, it can also be understood as sending the handover command for the second time, or the third time, which will not be exhaustive here. The successful sending of the handover command to the UE may be that when the confirmation information fed back by the UE is received, the handover command is considered to be successfully sent. In addition, the timing of sending the second information may be the time when the handover command is confirmed to be successfully sent, or the confirmation When the sixth preset duration after the switch command is successfully sent. The fifth preset duration and the sixth preset duration may be the same or different.

The second information includes at least one of the following:

An indication that the source network device has sent a handover command;

Resource maintenance actions/state reset instructions;

An indication that the first timer is restarted;

Instructions for the second duration.

Processing scenario 1,

The fourth communication unit 1001 configures non-contention-based random access resources for the UE;

The third preset condition includes at least one of the following:

Random access resources based on non-competition are invalid;

Random access based on non-contention fails.

This embodiment may further include: the fourth communication unit 1001 sending a handover command to the UE;

In this scenario, multiple sets of non-contention random access resources can be configured for the UE. At this time, the UE can perform processing through one set of non-contention random access resources. At this time, if a failure occurs, the random access failure can be indicated to the higher layer. Then the UE can again select another set of non-competitive random access resources for access. That is to say, at this time, the third communication unit may also receive the information that the access fails based on a certain set of non-competitive random access resources from the UE.

Since it is uncertain whether the network side releases the UE context and the resource configuration reserved for the UE at the same time, there may be a problem that CFRA resources are not valid or CFRA fails when UE-related information such as the UE context is reserved. According to the existing agreement, if RA is directly considered to fail, or re-establishment is triggered, or SCG change failure is triggered, instead of falling back to the UE CBRA process, it will cause the UE to access the network delay, and even miss the MCOT due to the delayed UE access. Time leads to long delays in the communication between the UE and the network, resulting in problems such as reduced service QoS and poor UE experience. This problem is solved by configuring/carrying at least one CFRA resource.

The embodiment of the application provides a target network device, as shown in FIG. 19, including:

The fifth communication unit 1101 sends the first information to the source network device;

The fifth communication unit 1101 sends handover request confirmation information to the source network device, where the handover request confirmation information carries the first information.

It should be pointed out that the target network equipment also includes:

The fifth processing unit 1102, when the second preset condition is met, starts the first timer;

Wherein, the second preset condition includes at least one of the following:

Processing scenario 1,

The fifth communication unit 1101 configures a non-contention-based random access resource for the UE; the random access resource may be configured by the target base station for the UE, and then sent to the UE through the source network device.

The method also includes:

FIG. 20 is a schematic structural diagram of a communication device 1200 provided by an embodiment of the present application. The communication device may be the aforementioned UE or network device in this embodiment. The communication device 1200 shown in FIG. 20 includes a processor 1210, and the processor 610 can call and run a computer program from a memory to implement the method in the embodiment of the present application.

Optionally, as shown in FIG. 20, the communication device 1200 may further include a memory 1220. The processor 1210 can call and run a computer program from the memory 1220 to implement the method in the embodiment of the present application.

The memory 1220 may be a separate device independent of the processor 1210, or may be integrated in the processor 610.

Optionally, as shown in FIG. 20, the communication device 1200 may further include a transceiver 1230, and the processor 1210 may control the transceiver 1230 to communicate with other devices. Specifically, it may send information or data to other devices, or receive other devices. Information or data sent by the device.

Optionally, the communication device 1200 may specifically be a UE or a network device of an embodiment of the present application, and the communication device 1200 may implement the corresponding procedures implemented by the mobile terminal/UE in each method of the embodiments of the present application. For simplicity, I will not repeat them here.

FIG. 21 is a schematic structural diagram of a chip of an embodiment of the present application. The chip 1300 shown in FIG. 21 includes a processor 1310, and the processor 1310 can call and run a computer program from the memory to implement the method in the embodiment of the present application.

Optionally, as shown in FIG. 21, the chip 1300 may further include a memory 1320. The processor 1310 may call and run a computer program from the memory 1320 to implement the method in the embodiment of the present application.

The memory 1320 may be a separate device independent of the processor 1310, or it may be integrated in the processor 1310.

Optionally, the chip 1300 may further include an input interface 1330 and an output interface 1340.

Optionally, the chip can be applied to the network device or UE in the embodiment of the present application, and the chip can implement the corresponding process implemented by the network device in each method of the embodiment of the present application. For the sake of brevity, details are not repeated here. .

FIG. 22 is a schematic block diagram of a communication system 1400 according to an embodiment of the present application. As shown in FIG. 22, the communication system 1400 includes a UE 1410 and a network device 1420.

Wherein, the UE 1410 may be used to implement the corresponding functions implemented by the UE in the foregoing method, and the network device 1420 may be used to implement the corresponding functions implemented by the network device in the foregoing method. For brevity, details are not described herein again.

It should be understood that the processor of the embodiment of the present application may be an integrated circuit chip with signal processing capability. In the implementation process, the steps of the foregoing method embodiments can be completed by hardware integrated logic circuits in the processor or instructions in the form of software. The aforementioned processor may be a general-purpose processor, a digital signal processor (Digital Signal Processor, DSP), an application specific integrated circuit (ASIC), a ready-made programmable gate array (Field Programmable Gate Array, FPGA) or other Programming logic devices, discrete gates or transistor logic devices, discrete hardware components. The methods, steps, and logical block diagrams disclosed in the embodiments of the present application can be implemented or executed. The general-purpose processor may be a microprocessor or the processor may also be any conventional processor or the like. The steps of the method disclosed in the embodiments of the present application may be directly embodied as being executed and completed by a hardware decoding processor, or executed and completed by a combination of hardware and software modules in the decoding processor. The software module can be located in a mature storage medium in the field such as random access memory, flash memory, read-only memory, programmable read-only memory, or electrically erasable programmable memory, registers. The storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware.

It can be understood that the memory in the embodiment of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memory. Among them, the non-volatile memory can be read-only memory (Read-Only Memory, ROM), programmable read-only memory (Programmable ROM, PROM), erasable programmable read-only memory (Erasable PROM, EPROM), and electrically available Erase programmable read-only memory (Electrically EPROM, EEPROM) or flash memory. The volatile memory may be a random access memory (Random Access Memory, RAM), which is used as an external cache. By way of exemplary but not restrictive description, many forms of RAM are available, such as static random access memory (Static RAM, SRAM), dynamic random access memory (Dynamic RAM, DRAM), synchronous dynamic random access memory (Synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (Double Data Rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (Enhanced SDRAM, ESDRAM), synchronous connection dynamic random access memory (Synchlink DRAM, SLDRAM) ) And Direct Rambus RAM (DR RAM). It should be noted that the memories of the systems and methods described herein are intended to include, but are not limited to, these and any other suitable types of memories.

It should be understood that the foregoing memory is exemplary but not restrictive. For example, the memory in the embodiment of the present application may also be static random access memory (static RAM, SRAM), dynamic random access memory (dynamic RAM, DRAM), Synchronous dynamic random access memory (synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (double data rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchronous connection Dynamic random access memory (synch link DRAM, SLDRAM) and direct memory bus random access memory (Direct Rambus RAM, DR RAM), etc. That is to say, the memory in the embodiment of the present application is intended to include but not limited to these and any other suitable types of memory.

The embodiment of the present application also provides a computer-readable storage medium for storing computer programs.

Optionally, the computer-readable storage medium may be applied to the network device in the embodiment of the present application, and the computer program causes the computer to execute the corresponding process implemented by the network device in each method of the embodiment of the present application. For brevity, here No longer.

Optionally, the computer-readable storage medium may be applied to the UE in the embodiment of the present application, and the computer program causes the computer to execute the corresponding process implemented by the mobile terminal/UE in each method of the embodiment of the present application. For brevity, This will not be repeated here.

The embodiments of the present application also provide a computer program product, including computer program instructions.

Optionally, the computer program product may be applied to the network device in the embodiment of the present application, and the computer program instructions cause the computer to execute the corresponding process implemented by the network device in each method of the embodiment of the present application. For the sake of brevity, it is not here. Repeat it again.

Optionally, the computer program product can be applied to the mobile terminal/UE in the embodiments of the present application, and the computer program instructions cause the computer to execute the corresponding processes implemented by the mobile terminal/UE in the various methods of the embodiments of the present application, for the sake of brevity , I won’t repeat it here.

The embodiment of the present application also provides a computer program.

Optionally, the computer program can be applied to the network device in the embodiment of the present application. When the computer program runs on the computer, the computer is caused to execute the corresponding process implemented by the network device in each method of the embodiment of the present application. For the sake of brevity , I won’t repeat it here.

Optionally, the computer program can be applied to the mobile terminal/UE in the embodiments of the present application. When the computer program runs on the computer, the computer can execute the corresponding methods implemented by the mobile terminal/UE in the various methods of the embodiments of the present application. For the sake of brevity, the process will not be repeated here.

A person of ordinary skill in the art may be aware that the units and algorithm steps of the examples described in combination with the embodiments disclosed herein can be implemented by electronic hardware or a combination of computer software and electronic hardware. Whether these functions are executed by hardware or software depends on the specific application and design constraint conditions of the technical solution. Professionals and technicians can use different methods for each specific application to implement the described functions, but such implementation should not be considered beyond the scope of this application.

Those skilled in the art can clearly understand that, for the convenience and conciseness of description, the specific working process of the above-described system, device, and unit can refer to the corresponding process in the foregoing method embodiment, which will not be repeated here.

In the several embodiments provided in this application, it should be understood that the disclosed system, device, and method may be implemented in other ways. For example, the device embodiments described above are only illustrative. For example, the division of the units is only a logical function division, and there may be other divisions in actual implementation, for example, multiple units or components can be combined or It can be integrated into another system, or some features can be ignored or not implemented. In addition, the displayed or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, devices or units, and may be in electrical, mechanical or other forms.

The units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the objectives of the solutions of the embodiments.

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

If the function is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer readable storage medium. Based on this understanding, the technical solution of this application essentially or the part that contributes to the existing technology or the part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including Several instructions are used to make a computer device (which may be a personal computer, a server, or a network device, etc.) execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage media include: U disk, mobile hard disk, read-only memory (Read-Only Memory,) ROM, random access memory (Random Access Memory, RAM), magnetic disk or optical disk and other media that can store program code .

The above are only specific implementations of this application, but the protection scope of this application is not limited to this. Any person skilled in the art can easily think of changes or substitutions within the technical scope disclosed in this application. Should be covered within the scope of protection of this application. Therefore, the protection scope of this application shall be subject to the protection scope of the claims.

Claims

A handover processing method, applied to source network equipment, includes:

Sending the first information to the user equipment UE;

Wherein, the first information is at least used to assist the UE in determining that the effective duration of UE-related information on the UE side and the network side are consistent, or used to determine the effective duration of UE-related information.
The method according to claim 1, wherein the method further comprises:

Receiving handover request confirmation information sent by the target network device, where the handover request confirmation information carries the first information.
The method according to claim 1 or 2, wherein the first information includes at least one of the following:

The termination time of the effective retention of UE-related information, the time period during which UE-related information is effectively retained, the time difference information between the target network device and the source network device, the time when the first timer is started, and the duration of the first timer.
The method according to claim 3, wherein the UE-related information includes but is not limited to at least one of the following: contextual content of the UE, reserved resources/configuration, random access to RA resources, bearer corresponding configuration, quality of service QoS Parameters, business type information.
The method according to claim 3, wherein the first timer is used to maintain the effective duration of the UE-related information stored on the candidate target network device side.
The method according to claim 5, wherein the method further comprises:

When the first preset condition is met, instruct the target network device to start the first timer;

Wherein, the first preset condition includes at least one of the following:

Receive handover request confirmation message; send handover command; send handover command successfully.
The method according to claim 1, wherein the method further comprises:

Generate the first information.
The method according to claim 7, wherein the first information includes:

The delay time for the issuance of the handover command, or the number of times the issuance of the handover command fails.
The method according to claim 8, wherein the first information further includes at least one of the following:

Resources reserved by the target network equipment;

At least one of the actual effective time, effective duration, and deadline of the UE context;

At least one of the actual effective time, effective time, and deadline of the configuration information contained in the switching command;

The time when the first timer of the target network device is started;

The start time when the target network device holds UE-related information;

The deadline for the target network device to keep UE-related information;

The length of time the first timer of the target network device has been running when the handover command is sent;

The length of time the target network device has retained UE-related information when the handover command is sent;

The remaining effective duration of the UE related information in the target network device when the handover command is sent.
The method according to any one of claims 7-9, wherein the method further comprises one of the following:

Carry the first information in the handover command;

The first information is carried in the RRC message.
The method according to claim 7, wherein the method further comprises:

Determine the updated parameter of the first timer according to at least one of the following information, and send the updated parameter of the first timer to the UE:

The parameters of the original first timer, the delay time for handover command delivery, the number of failed handover commands, the time when the network starts the first timer, the deadline for valid retention of UE-related information, and the time period for valid retention of UE-related information , The time difference information between the target network device and the source network device, and the length of the original first timer.
The method according to claim 7, wherein the first information further includes:

Second duration

The second duration is used to instruct the target network device for the UE to retain the effective duration of the UE-related information, or the second duration is used to make the UE and the network retain the effective duration of the UE-related information consistent.
The method according to claim 12, wherein the method further comprises:

Determine the parameter of the second duration based on at least one of the following information:

The parameters of the first timer, the delay time for the issuance of handover commands, the number of failed handover commands, the time when the network starts the first timer, the deadline for valid retention of UE-related information, and the time period for valid retention of UE-related information, The time difference information between the target network device and the source network device, and the duration of the first timer.
A handover processing method is applied to user equipment UE, and the method includes:

Receiving the first information sent by the source network device;

Wherein, the first information is at least used to assist the UE in determining that the effective duration of UE-related information on the UE side and the network side are consistent, or used to determine the effective duration of UE-related information.
The method according to claim 14, wherein the first information includes at least one of the following:

The termination time of the effective retention of UE-related information, the period of time that the UE-related information is effectively retained, the time difference information between the target network device and the source network device, the opening time of the first timer on the network device side, and the duration of the first timer.
The method according to claim 15, wherein the UE-related information includes but is not limited to at least one of the following: contextual content of the UE, reserved resources/configuration, RA resources, bearer corresponding configuration, QoS parameters, service type information .
The method according to claim 14, wherein the method further comprises:

Based on the first information, the effective storage duration for storing the UE-related information on the target network device side is determined.
The method of claim 17, wherein the method further comprises:

Based on the effective duration of the UE-related information stored on the target network device side, when it is determined that the UE-related information stored on the target network device side is valid, perform handover processing, or perform random access processing in the handover process.
The method of claim 18, wherein the method further comprises:

When it is determined that the UE-related information stored on the target network device side is invalid based on the effective duration of the UE-related information stored on the target network device side, at least one of the following is performed:

Confirm that the switch failed;

Perform the RRC connection re-establishment process;

Indicate the SCG failure information process to the network.
The method according to any one of claims 14, 18, 19, wherein the first information includes:

The delay time for the issuance of the handover command, or the number of times the issuance of the handover command fails.
The method of claim 20, wherein the method further comprises:

Based on the first information, at least one of the following information is determined:

Resources reserved by the target network equipment;

At least one of the actual effective time, effective duration, and deadline of the UE context;

At least one of the actual effective time, effective time, and deadline of the configuration information contained in the switching command;

The time when the first timer of the target network device is started;

The start time when the target network device holds UE-related information;

The deadline for the target network device to keep UE-related information;

The length of time the timer of the target network device has been running when the switch command is received;

The length of time that the target network device has retained UE-related information when receiving the handover command;

The remaining effective duration of the UE related information in the target network device when the handover command is received.
The method according to claim 20, wherein the first information further comprises at least one of the following:

Resources reserved by the target network equipment;

At least one of the actual effective time, effective duration, and deadline of the UE context;

At least one of the actual effective time, effective time, and deadline of the configuration information contained in the switching command;

The time when the first timer of the target network device is started;

The start time when the target network device holds UE-related information;

The deadline for the target network device to keep UE-related information;

The length of time the timer of the target network device has been running when the source network device sends the handover command;

The length of time the target network device has retained UE-related information when the source network device sends the handover command;

The remaining effective duration of UE-related information in the target network device when the source network device sends the handover command.
The method according to any one of claims 20-22, wherein the method further comprises one of the following:

Obtain the first information carried by the switching command;

Obtain the first information carried by the RRC message.
The method according to any one of claims 15, 20-22, wherein the method further comprises:

Determine the second duration.
The method of claim 24, wherein the method further comprises:

Determine the parameter of the second duration based on at least one of the following information:

The parameters of the first timer, the delay time for the issuance of handover commands, the number of failed handover commands, the time when the network starts the first timer, the deadline for valid retention of UE-related information, and the time period for valid retention of UE-related information, The time difference information between the target network device and the source network device, and the duration of the first timer.
The method according to any one of claims 20-22, wherein the first information further includes:

The updated parameter of the first timer, or the second duration;

Wherein, the second duration is different from the duration in the parameter of the first timer.
The method according to claim 14, wherein the method further comprises:

Receive the handover command sent by the source network device;

Perform handover based on the handover command, and fall back from non-contention-based random access to contention-based random access when a third preset condition is met during the handover process;

The third preset condition includes at least one of the following:

Random access resources based on non-competition are invalid;

Random access based on non-contention fails.
The method according to claim 27, wherein the method further comprises: when the non-contention-based random access fails, not indicating the random access failure to the higher layer.
The method according to claim 14, wherein the method further comprises one of the following:

Processing is based on at least one set of non-competitive random access resources among multiple sets of non-competitive random access resources; when processing based on at least one set of non-competitive random access resources fails, random access is not indicated to the higher layer failure;

Perform processing based on at least one set of non-competitive random access resources among multiple sets of non-competitive random access resources; when processing based on at least one set of non-competitive random access resources fails, indicate random access failure to higher layers ；

The processing is performed based on the first non-competition-based random access resource among the multiple sets of non-competition random access resources; when it is determined that the processing of the first non-competition-based random access resource fails, if there is a Non-competitive random access resources other than non-competitive random access resources will not indicate random access failure to the higher layer;

The processing is performed based on the first non-competition-based random access resource among the multiple sets of non-competition random access resources; when it is determined that the processing of the first non-competition-based random access resource fails, if there is a Other non-competitive random access resources other than the non-competitive random access resources indicate random access failure to the higher layer.
A handover processing method, applied to source network equipment, includes:

Select the target network device for switching, and send a switching request to the target network device;

Receiving the handover request confirmation information fed back by the target network device;

Sending second information to the target network device; wherein the second information is used to assist the target network device in determining the effective duration of the UE-related information stored by the target network device, and the UE stored in the target network device determined by the UE The valid duration of the relevant information is the same.
The method according to claim 30, wherein, before sending the second information to the target network device, the method further comprises:

Send a handover command to the UE;

Or, successfully sending a handover command to the UE;

Or, an indication that the UE has successfully received the handover command is received.
The method according to claim 30, wherein the second information includes at least one of the following:

Instruct the target network device that the handover command sent by the source network device to the UE is successfully sent;

Instruct the target network device that the source network device has sent a handover command;

Instruct the resource maintenance behavior/status reset to the target network device;

Instruct the target network device to restart the first timer;

Indicate the second duration to the target network device.
The method according to claim 30, wherein the UE-related information includes but is not limited to at least one of the following: contextual content of the UE, reserved resources/configuration, RA resources, bearer corresponding configuration, QoS parameters, service type information .
The method of claim 30, wherein the method further comprises:

Send a handover command to the UE;

Wherein, the handover command carries at least one set of non-competition-based random access resources, or the handover command carries at least one set of non-competition-based random access resources and the priority of each set of non-competition-based random access resources. level.
The method according to claim 34, wherein at least one of the following information of different non-competition-based random access resources is different:

The effective start of the resource is different, the PRACH timing identifier is different, the time domain/frequency domain position interval of the PRACH resource is different, the preamble sequence parameter is different, and the preamble sequence identifier is different.
A handover processing method, applied to a target network device, includes:

Receive the handover request sent by the source network device;

Sending handover request confirmation information to the source network device;

Receiving second information sent by the source network device; where the second information is used to assist the target network device in determining the effective duration of the UE-related information stored by the target network device, and the information stored in the target network device determined by the UE The valid duration of UE-related information is consistent.
The method according to claim 36, wherein the second information includes at least one of the following:

An indication that the handover command sent by the source network device to the UE is successfully sent;

An indication that the source network device has sent a handover command;

Resource maintenance actions/state reset instructions;

An indication that the first timer is restarted;

Instructions for the second duration.
The method according to claim 36, wherein the UE-related information includes but is not limited to at least one of the following: contextual content of the UE, reserved resources/configuration, RA resources, bearer corresponding configuration, QoS parameters, service type information .
The method of claim 36, wherein the method further comprises:

Send at least one set of non-competition-based random access resources to the source network device, or,

Send at least one set of non-competition-based random access resources and the priority of each set of non-competition-based random access resources to the source network device.
A source network device, including:

The first communication unit sends the first information to the user equipment UE;

Wherein, the first information is at least used to assist the UE in determining that the effective duration of UE-related information on the UE side and the network side are consistent, or used to determine the effective duration of UE-related information.
The source network device according to claim 40, wherein the first communication unit receives handover request confirmation information sent by the target network device, and the handover request confirmation information carries the first information.
The source network device according to claim 40 or 41, wherein the first information includes at least one of the following:

The termination time of the effective retention of UE-related information, the time period during which UE-related information is effectively retained, the time difference information between the target network device and the source network device, the time when the first timer is started, and the duration of the first timer.
The source network device according to claim 42, wherein the UE-related information includes but is not limited to at least one of the following: contextual content of the UE, reserved resources/configuration, random access to RA resources, bearer corresponding configuration, service Quality QoS parameters, service type information.
The source network device according to claim 42, wherein the first timer is used to maintain the effective duration of the UE-related information stored on the candidate target network device side.
The source network device according to claim 44, wherein the first communication unit,

When the first preset condition is met, instruct the target network device to start the first timer;

Wherein, the first preset condition includes at least one of the following:

Receive handover request confirmation message; send handover command; send handover command successfully.
The source network device according to claim 40, wherein the source network device further comprises:

The first processing unit generates first information.
The source network device according to claim 46, wherein the first information includes:

The delay time for the issuance of the handover command, or the number of times the issuance of the handover command fails.
The source network device according to claim 47, wherein the first information further includes at least one of the following:

Resources reserved by the target network equipment;

At least one of the actual effective time, effective duration, and deadline of the UE context;

At least one of the actual effective time, effective time, and deadline of the configuration information contained in the switching command;

The time when the first timer of the target network device is started;

The start time when the target network device holds UE-related information;

The deadline for the target network device to keep UE-related information;

The length of time the first timer of the target network device has been running when the handover command is sent;

The length of time the target network device has retained UE-related information when the handover command is sent;

The remaining effective duration of the UE related information in the target network device when the handover command is sent.
The source network device according to any one of claims 46-48, wherein the first processing unit performs one of the following:

Carry the first information in the handover command;

The first information is carried in the RRC message.
The source network device according to claim 49, wherein the first processing unit determines the parameters of the updated first timer based on at least one of the following information: the parameters of the original first timer, and the delay in issuing handover commands The number of times the handover command fails to be issued, the time when the network starts the first timer, the deadline for valid retention of UE-related information, the time period during which UE-related information is valid The duration of the first timer;

The first communication unit sends the updated parameter of the first timer to the UE.
The source network device according to claim 46, wherein the first information further includes:

Second duration

The second duration is used to instruct the target network device for the UE to retain the effective duration of the UE-related information, or the second duration is used to make the UE and the network retain the effective duration of the UE-related information consistent.
The source network device according to claim 51, wherein the first processing unit determines the parameter of the second duration based on at least one of the following information:

The parameters of the first timer, the delay time for the issuance of handover commands, the number of failed handover commands, the time when the network starts the first timer, the deadline for valid retention of UE-related information, and the time period for valid retention of UE-related information, The time difference information between the target network device and the source network device, and the duration of the first timer.
A type of UE, including:

The second communication unit receives the first information sent by the source network device;

Wherein, the first information is at least used to assist the UE in determining that the effective duration of UE-related information on the UE side and the network side are consistent, or used to determine the effective duration of UE-related information.
The UE according to claim 53, wherein the first information includes at least one of the following:

The termination time of the effective retention of UE-related information, the period of time that the UE-related information is effectively retained, the time difference information between the target network device and the source network device, the opening time of the first timer on the network device side, and the duration of the first timer.
The UE according to claim 54, wherein the UE-related information includes but is not limited to at least one of the following: contextual content of the UE, reserved resources/configuration, RA resources, bearer corresponding configuration, QoS parameters, service type information .
The UE according to claim 53, wherein the UE further comprises:

The second processing unit, based on the first information, determines the effective storage duration for storing the UE-related information on the target network device side.
The UE according to claim 56, wherein the second processing unit determines that the UE-related information stored on the target network device side is valid based on the effective duration of the UE-related information stored on the target network device side, executes Handover processing, or, perform random access processing during the handover process.
The UE according to claim 57, wherein the second processing unit determines that the UE-related information stored on the target network device side is invalid based on the effective duration of the UE-related information stored on the target network device side, executes At least one of the following:

Confirm that the switch failed;

Perform the RRC connection re-establishment process;

Indicate the SCG failure information process to the network.
The UE according to any one of claims 54, 57, 58, wherein the first information includes:

The delay time for the issuance of the handover command, or the number of times the issuance of the handover command fails.
The UE according to claim 59, wherein the second processing unit determines at least one of the following information based on the first information:

Resources reserved by the target network equipment;

At least one of the actual effective time, effective duration, and deadline of the UE context;

At least one of the actual effective time, effective time, and deadline of the configuration information contained in the switching command;

The time when the first timer of the target network device is started;

The start time when the target network device holds UE-related information;

The deadline for the target network device to keep UE-related information;

The length of time the timer of the target network device has been running when the switch command is received;

The length of time that the target network device has retained UE-related information when receiving the handover command;

The remaining effective duration of the UE related information in the target network device when the handover command is received.
The UE according to claim 59, wherein the first information further comprises at least one of the following:

Resources reserved by the target network equipment;

At least one of the actual effective time, effective duration, and deadline of the UE context;

At least one of the actual effective time, effective time, and deadline of the configuration information contained in the switching command;

The time when the first timer of the target network device is started;

The start time when the target network device holds UE-related information;

The deadline for the target network device to keep UE-related information;

The length of time the timer of the target network device has been running when the source network device sends the handover command;

The length of time the target network device has retained UE-related information when the source network device sends the handover command;

The remaining effective duration of UE-related information in the target network device when the source network device sends the handover command.
The UE according to any one of claims 59-61, wherein the second processing unit performs one of the following:

Obtain the first information carried by the switching command;

Obtain the first information carried by the RRC message.
The UE according to any one of claims 54, 59-61, wherein the second processing unit determines the second duration.
The UE according to claim 63, wherein the second processing unit determines the parameter of the second duration based on at least one of the following information:

The parameters of the first timer, the delay time for the issuance of handover commands, the number of failed handover commands, the time when the network starts the first timer, the deadline for valid retention of UE-related information, and the time period for valid retention of UE-related information, The time difference information between the target network device and the source network device, and the duration of the first timer.
The UE according to any one of claims 59-61, wherein the first information further includes:

The updated parameter of the first timer, or the second duration;

Wherein, the second duration is different from the duration in the parameter of the first timer.
The UE according to claim 54, wherein the second communication unit receives a handover command sent by a source network device;

The second processing unit performs handover based on the handover command, and during the handover process, when a third preset condition is met, fall back from non-contention-based random access to contention-based random access;

The third preset condition includes at least one of the following:

Random access resources based on non-competition are invalid;

Random access based on non-contention fails.
The UE according to claim 66, wherein the second processing unit does not indicate the random access failure to the higher layer when the non-contention based random access fails.
The UE according to claim 54, wherein the second processing unit,

Do one of the following:

Processing is based on at least one set of non-competitive random access resources among multiple sets of non-competitive random access resources; when processing based on at least one set of non-competitive random access resources fails, random access is not indicated to the higher layer failure;

Perform processing based on at least one set of non-competitive random access resources among multiple sets of non-competitive random access resources; when processing based on at least one set of non-competitive random access resources fails, indicate random access failure to higher layers ；

The processing is performed based on the first non-competition-based random access resource among the multiple sets of non-competition random access resources; when it is determined that the processing of the first non-competition-based random access resource fails, if there is a Non-competitive random access resources other than non-competitive random access resources will not indicate random access failure to the higher layer;

The processing is performed based on the first non-competition-based random access resource among the multiple sets of non-competition random access resources; when it is determined that the processing of the first non-competition-based random access resource fails, if there is a Other non-competitive random access resources other than the non-competitive random access resources indicate random access failure to the higher layer.
A source network device, including:

The third processing unit selects the switching target network device;

The third communication unit sends a handover request to the target network device; receives the handover request confirmation information fed back by the target network device; sends second information to the target network device; wherein the second information is used to assist the target network device in determining the location The effective duration of the UE-related information stored by the target network device is consistent with the effective duration of the UE-related information stored by the target network device determined by the UE.
The source network device according to claim 69, wherein the third communication unit sends a handover command to the UE;

Or, successfully sending a handover command to the UE;

Or, an indication that the UE has successfully received the handover command is received.
The source network device according to claim 69, wherein the second information includes at least one of the following:

Instruct the target network device that the handover command sent by the source network device to the UE is successfully sent;

Instruct the target network device that the source network device has sent a handover command;

Instruct the resource maintenance behavior/status reset to the target network device;

Instruct the target network device to restart the first timer;

Indicate the second duration to the target network device.
The source network device according to claim 69, wherein the UE-related information includes but is not limited to at least one of the following: contextual content of the UE, reserved resources/configuration, RA resources, bearer corresponding configuration, QoS parameters, services Type information.
The source network device according to claim 69, wherein the third communication unit sends a handover command to the UE;

Wherein, the handover command carries at least one set of non-competition-based random access resources, or the handover command carries at least one set of non-competition-based random access resources and the priority of each set of non-competition-based random access resources. level.
The source network device according to claim 73, wherein at least one of the following information of different non-competition-based random access resources is different:

The effective start of the resource is different, the PRACH timing identifier is different, the time domain/frequency domain position interval of the PRACH resource is different, the preamble sequence parameter is different, and the preamble sequence identifier is different.
A target network device, including:

The fourth communication unit receives the handover request sent by the source network device;

Sending handover request confirmation information to the source network device;

Receiving second information sent by the source network device; where the second information is used to assist the target network device in determining the effective duration of the UE-related information stored by the target network device, and the information stored in the target network device determined by the UE The valid duration of UE-related information is consistent.
The target network device according to claim 75, wherein the second information includes at least one of the following:

An indication that the handover command sent by the source network device to the UE is successfully sent;

An indication that the source network device has sent a handover command;

Resource maintenance actions/state reset instructions;

An indication that the first timer is restarted;

Instructions for the second duration.
The target network device according to claim 75, wherein the UE-related information includes but is not limited to at least one of the following: contextual content of the UE, reserved resources/configuration, RA resources, bearer corresponding configuration, QoS parameters, services Type information.
The target network device according to claim 75, wherein the fourth communication unit,

Send at least one set of non-competition-based random access resources to the source network device, or,

Send at least one set of non-competition-based random access resources and the priority of each set of non-competition-based random access resources to the source network device.
A handover processing method, applied to a target network device, includes:

Sending the first information to the source network device;

Wherein, the first information is at least used to assist the UE in determining that the effective duration of UE-related information on the UE side and the network side are consistent, or used to determine the effective duration of UE-related information.
The method of claim 79, wherein the method further comprises:

Sending handover request confirmation information to the source network device, where the handover request confirmation information carries the first information.
The method according to claim 79 or 80, wherein the first information includes at least one of the following:

The termination time of the effective retention of UE-related information, the time period during which UE-related information is effectively retained, the time difference information between the target network device and the source network device, the time when the first timer is started, and the duration of the first timer.
The method according to claim 81, wherein the UE-related information includes but is not limited to at least one of the following: contextual content of the UE, reserved resources/configuration, random access to RA resources, corresponding bearer configuration, quality of service (QoS) Parameters, business type information.
The method according to claim 81, wherein the first timer is used to maintain the effective duration of the UE-related information stored on the candidate target network device side.
The method of claim 83, wherein the method further comprises:

When the second preset condition is met, start the first timer;

Wherein, the second preset condition includes at least one of the following:

The target network device sends a handover request confirmation message; receives a message sent by the source network device indicating to start the first timer; and receives the second message.
The method of claim 79, wherein the method further comprises:

Send at least one set of non-competition-based random access resources to the source network device, or,

Send at least one set of non-competition-based random access resources and the priority of each set of non-competition-based random access resources to the source network device.
A target network device, including:

The fifth communication unit sends the first information to the source network device;

Wherein, the first information is at least used to assist the UE in determining that the effective duration of UE-related information on the UE side and the network side are consistent, or used to determine the effective duration of UE-related information.
The target network device according to claim 86, wherein the fifth communication unit sends handover request confirmation information to the source network device, and the handover request confirmation information carries the first information.
The target network device according to claim 86 or 87, wherein the first information includes at least one of the following:

The termination time of the effective retention of UE-related information, the time period during which UE-related information is effectively retained, the time difference information between the target network device and the source network device, the time when the first timer is started, and the duration of the first timer.
The target network device according to claim 88, wherein the UE-related information includes but is not limited to at least one of the following: contextual content of the UE, reserved resources/configuration, random access to RA resources, bearer corresponding configuration, service Quality QoS parameters, service type information.
The target network device according to claim 88, wherein the first timer is used to maintain the effective duration of the UE-related information stored on the candidate target network device side.
The target network device according to claim 90, wherein the target network device further comprises:

The fifth processing unit starts the first timer when the second preset condition is met;

Wherein, the second preset condition includes at least one of the following:

The target network device sends a handover request confirmation message; receives a message sent by the source network device indicating to start the first timer; and receives the second message.
The target network device according to claim 86, wherein the fifth communication unit,

Send at least one set of non-competition-based random access resources to the source network device, or,

Send at least one set of non-competition-based random access resources and the priority of each set of non-competition-based random access resources to the source network device.
A terminal device, including: a processor and a memory for storing a computer program that can run on the processor,

Wherein, the memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory to execute the steps of the method according to any one of claims 14-29.
A network device including: a processor and a memory for storing a computer program that can run on the processor,

Wherein, the memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory to execute the steps of the method according to any one of claims 1-13, 30-39, and 79-85 .
A chip comprising: a processor, configured to call and run a computer program from a memory, so that a device installed with the chip executes the method according to any one of claims 14-29.
A chip, comprising: a processor, used to call and run a computer program from a memory, so that the device installed with the chip executes the device described in any one of claims 1-13, 30-39, and 79-85 method.
A computer-readable storage medium for storing a computer program that enables a computer to execute the steps of the method according to any one of claims 1-39 and 79-85.
A computer program product, comprising computer program instructions that cause a computer to execute the method according to any one of claims 1-39 and 79-85.
A computer program that causes a computer to execute the method according to any one of claims 1-39 and 79-85.