WO2023065156A1

WO2023065156A1 - Wireless communication method, terminal device, and network device

Info

Publication number: WO2023065156A1
Application number: PCT/CN2021/125022
Authority: WO
Inventors: 刘洋
Original assignee: Oppo广东移动通信有限公司
Priority date: 2021-10-20
Filing date: 2021-10-20
Publication date: 2023-04-27
Also published as: CN117678320A

Abstract

A wireless communication method, a terminal device, and a network device. The method comprises: upon successful handover from a source cell to a target cell, a terminal device processes a recorded successful handover report (SHR) according to first information, the first information comprising at least one of the following: whether a radio link failure (RLF) occurs on the target cell during operation of a first timer; a first duration, the first duration being a duration from completion of the handover of the terminal device to occurrence of the RLF on the target cell; and a second duration, the second duration being a duration from start of the handover by the terminal device to the occurrence of the RLF on the target cell.

Description

Wireless communication method, terminal device and network device

technical field

The embodiments of the present application relate to the communication field, and in particular to a wireless communication method, a terminal device, and a network device.

Background technique

In related technologies, in order to improve and optimize user handover experience, a successful handover report (successful handover report, SHR) is introduced to record problems found in successful handover, and network devices can adjust handover-related parameters according to the SHR. If a radio link failure (radio link failure, RLF) occurs on the target cell after the handover of the terminal device is successfully completed, in this case, the terminal device will generate an RLF report to record the RLF that occurred on the target cell, and the network device can according to The RLF report adjusts handover related parameters.

In some scenarios, for the same handover, the terminal device may report both the SHR and the RLF report, which will cause the network device to not know how to adjust the parameters related to the handover.

Contents of the invention

The present application provides a wireless communication method, terminal equipment and network equipment, which is beneficial to avoid that for the same handover, the terminal equipment reports both the SHR and the RLF report, so that the network equipment does not know how to adjust the parameters related to the subsequent handover question.

In a first aspect, a wireless communication method is provided, including: in the case of a successful handover from a source cell to a target cell, a terminal device processes a recorded successful handover report SHR according to first information, wherein the The first information includes at least one of the following: whether a radio link failure RLF occurs on the target cell during the first timer running; The duration of the RLF occurring on the target cell; the second duration, wherein the second duration is the duration of the RLF occurring on the target cell when the terminal device starts to perform handover.

In a second aspect, a wireless communication method is provided, including: a network device receives a successful handover report SHR sent by a terminal device, the SHR is used to indicate that the terminal device is successfully handed over from a source cell to a target cell; the network device Receive first indication information sent by the terminal device, where the first indication information is used to indicate that the SHR is unavailable.

In a third aspect, a wireless communication method is provided, including: a terminal device sends a successful handover report SHR and/or a radio link failure RLF report to a network device, wherein the SHR includes time information corresponding to successful handover and/or The identification information related to the successful handover, the RLF report includes the time information when the RLF event occurs and/or the identification information related to the RLF event.

In a fourth aspect, a wireless communication method is provided, including: a network device receiving a successful handover report SHR and/or a radio link failure RLF report sent by a terminal device, wherein the SHR includes time information corresponding to successful handover and/or Or the identification information related to the successful handover, the RLF report includes the time information when the RLF event occurs and/or the identification information related to the RLF event.

In a fifth aspect, a terminal device is provided, configured to execute the method in the foregoing first aspect or various implementation manners thereof.

Specifically, the terminal device includes a functional module for executing the method in the above first aspect or its various implementation manners.

In a sixth aspect, a network device is provided, configured to execute the method in the above-mentioned second aspect or various implementation manners thereof.

Specifically, the network device includes a functional module for executing the method in the above second aspect or each implementation manner thereof.

In a seventh aspect, a terminal device is provided, configured to execute the method in the foregoing third aspect or various implementation manners thereof.

Specifically, the terminal device includes a functional module for executing the method in the above third aspect or its various implementation manners.

In an eighth aspect, a network device is provided, configured to execute the method in the above fourth aspect or its various implementation manners.

Specifically, the network device includes a functional module for executing the method in the above fourth aspect or each implementation manner thereof.

A ninth aspect provides a terminal device, 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 first aspect, or the third aspect, or each implementation manner thereof.

In a tenth 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 method in the second aspect or the fourth aspect or its various implementations.

In an eleventh aspect, a chip is provided for implementing any one of the first aspect to the fourth aspect 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 device executes any one of the above-mentioned first to fourth aspects or any of the implementations thereof. method.

In a twelfth aspect, there is provided a computer-readable storage medium for storing a computer program, and the computer program causes a computer to execute any one of the above-mentioned first to fourth aspects or the method in each implementation manner thereof.

A thirteenth aspect provides a computer program product, including computer program instructions, the computer program instructions cause a computer to execute any one of the above first to fourth aspects or the method in each implementation manner.

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

Through the above technical solution, the terminal device processes the recorded SHR according to the first information, which is beneficial to avoid that for the same handover, the terminal device reports both the SHR and the RLF report, causing the network device to be unclear how to perform subsequent handover related parameters. The problem of making adjustments.

Description of drawings

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

Fig. 2 is a schematic diagram of a wireless communication method provided according to an embodiment of the present application.

Fig. 3 is a schematic flowchart of a method for wireless communication according to an embodiment of the present application.

Fig. 4 is a schematic diagram of a first duration and a second duration according to an embodiment of the present application.

Fig. 5 is a schematic diagram of another wireless communication method provided according to an embodiment of the present application.

Fig. 6 is a schematic interaction diagram of another wireless communication method provided according to an embodiment of the present application.

Fig. 7 is a schematic block diagram of a terminal device provided according to an embodiment of the present application.

Fig. 8 is a schematic block diagram of a network device provided according to an embodiment of the present application.

Fig. 9 is a schematic block diagram of a terminal device provided according to an embodiment of the present application.

Fig. 10 is a schematic block diagram of a network device provided according to an embodiment of the present application.

Fig. 11 is a schematic block diagram of a communication device provided according to an embodiment of the present application.

Fig. 12 is a schematic block diagram of a chip provided according to an embodiment of the present application.

Fig. 13 is a schematic block diagram of a communication system provided according to an embodiment of the present application.

Detailed ways

The technical solutions in the embodiments of the present application will be described below with reference to the drawings in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, but not all of the embodiments. With regard to the embodiments in this application, all other embodiments obtained by persons of ordinary skill in the art without making creative efforts belong to the scope of protection of this application.

The technical solution of the embodiment of the present application can be applied to various communication systems, such as: Global System of Mobile communication (Global System of Mobile communication, GSM) system, code division multiple access (Code Division Multiple Access, CDMA) system, broadband code division multiple access (Wideband Code Division Multiple Access, WCDMA) system, General Packet Radio Service (GPRS), Long Term Evolution (LTE) system, Advanced long term evolution (LTE-A) system , New Radio (NR) system, evolution system of NR system, LTE (LTE-based access to unlicensed spectrum, LTE-U) system on unlicensed spectrum, NR (NR-based access to unlicensed spectrum) on unlicensed spectrum unlicensed spectrum (NR-U) system, Non-Terrestrial Networks (NTN) system, Universal Mobile Telecommunications System (UMTS), Wireless Local Area Networks (WLAN), Wireless Fidelity (Wireless Fidelity, WiFi), fifth-generation communication (5th-Generation, 5G) system or other communication systems, etc.

Generally speaking, the number of connections supported by traditional communication systems is limited and easy to implement. However, with the development of communication technology, mobile communication systems will not only support traditional communication, but also support, for example, Device to Device (Device to Device, D2D) communication, Machine to Machine (M2M) communication, Machine Type Communication (MTC), Vehicle to Vehicle (V2V) communication, or Vehicle to everything (V2X) communication, etc. , the embodiments of the present application may also be applied to these communication systems.

Optionally, the communication system in the embodiment of the present application may be applied to a carrier aggregation (Carrier Aggregation, CA) scenario, may also be applied to a dual connectivity (Dual Connectivity, DC) scenario, and may also be applied to an independent (Standalone, SA) deployment Web scene.

Optionally, the communication system in the embodiment of the present application may be applied to an unlicensed spectrum, where the unlicensed spectrum may also be considered as a shared spectrum; or, the communication system in the embodiment of the present application may also be applied to a licensed spectrum, where, Licensed spectrum can also be considered as non-shared spectrum.

The embodiments of the present application describe various embodiments in conjunction with network equipment and terminal equipment, wherein the terminal equipment may also be referred to as user equipment (User Equipment, UE), access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent or user device, etc.

The terminal device can be a station (STATION, ST) in a WLAN, a cellular phone, a cordless phone, a Session Initiation Protocol (Session Initiation Protocol, SIP) phone, a wireless local loop (Wireless Local Loop, WLL) station, a personal digital assistant (Personal Digital Assistant, PDA) devices, handheld devices with wireless communication functions, computing devices or other processing devices connected to wireless modems, vehicle-mounted devices, wearable devices, next-generation communication systems such as terminal devices in NR networks, or future Terminal equipment in the evolved public land mobile network (Public Land Mobile Network, PLMN) network, etc.

In the embodiment of this application, the terminal device can be deployed on land, including indoor or outdoor, handheld, wearable or vehicle-mounted; it can also be deployed on water (such as ships, etc.); it can also be deployed in the air (such as aircraft, balloons and satellites) superior).

In this embodiment of the application, the terminal device may be a mobile phone (Mobile Phone), a tablet computer (Pad), a computer with a wireless transceiver function, a virtual reality (Virtual Reality, VR) terminal device, an augmented reality (Augmented Reality, AR) terminal Equipment, wireless terminal equipment in industrial control, wireless terminal equipment in self driving, wireless terminal equipment in remote medical, wireless terminal equipment in smart grid , wireless terminal equipment in transportation safety, wireless terminal equipment in smart city, or wireless terminal equipment in smart home.

As an example but not a limitation, in this embodiment of the present application, the terminal device may also be a wearable device. Wearable devices can also be called wearable smart devices, which is a general term for the application of wearable technology to intelligently design daily wear and develop wearable devices, such as glasses, gloves, watches, clothing and shoes. A wearable device is a portable device that is worn directly on the body or integrated into the user's clothing or accessories. Wearable devices are not only a hardware device, but also achieve powerful functions through software support, data interaction, and cloud interaction. Generalized wearable smart devices include full-featured, large-sized, complete or partial functions without relying on smart phones, such as smart watches or smart glasses, etc., and only focus on a certain type of application functions, and need to cooperate with other devices such as smart phones Use, such as various smart bracelets and smart jewelry for physical sign monitoring.

In the embodiment of the present application, the network device may be a device for communicating with the mobile device, and the network device may be an access point (Access Point, AP) in WLAN, a base station (Base Transceiver Station, BTS) in GSM or CDMA , or a base station (NodeB, NB) in WCDMA, or an evolved base station (Evolutional Node B, eNB or eNodeB) in LTE, or a relay station or access point, or a vehicle-mounted device, a wearable device, and an NR network The network equipment (gNB) in the network or the network equipment in the future evolved PLMN network or the network equipment in the NTN network, etc.

As an example but not a limitation, in this embodiment of the present application, the network device may have a mobile feature, for example, the network device may be a mobile device. Optionally, the network equipment may be a satellite or a balloon station. For example, the satellite can be a low earth orbit (low earth orbit, LEO) satellite, a medium earth orbit (medium earth orbit, MEO) satellite, a geosynchronous earth orbit (geosynchronous earth orbit, GEO) satellite, a high elliptical orbit (High Elliptical Orbit, HEO) satellite. ) Satellite etc. Optionally, the network device may also be a base station installed on land, water, and other locations.

In this embodiment of the present application, the network device may provide services for a cell, and the terminal device communicates with the network device through the transmission resources (for example, frequency domain resources, or spectrum resources) used by the cell, and the cell may be a network device ( For example, a cell corresponding to a base station), the cell may belong to a macro base station, or may belong to a base station corresponding to a small cell (Small cell), and the small cell here may include: a metro cell (Metro cell), a micro cell (Micro cell), a pico cell ( Pico cell), Femto cell, etc. These small cells have the characteristics of small coverage and low transmission power, and are suitable for providing high-speed data transmission services.

Exemplarily, a communication system 100 applied in this embodiment of the application is shown in FIG. 1 . The communication system 100 may include a network device 110, and the network device 110 may be a device for communicating with a terminal device 120 (or called a communication terminal, terminal). The network device 110 can provide communication coverage for a specific geographical area, and can communicate with terminal devices located in the coverage area.

FIG. 1 exemplarily shows one network device and two terminal devices. Optionally, the communication system 100 may include multiple network devices and each network device may include other numbers of terminal devices within the coverage area. This application The embodiment does not limit this.

Optionally, the communication system 100 may further include other network entities such as a network controller and a mobility management entity, which is not limited in this embodiment of the present application.

It should be understood that a device with a communication function in the network/system in the embodiment of the present application may be referred to as a communication device. Taking the communication system 100 shown in FIG. 1 as an example, the communication equipment may include a network equipment 110 and a terminal equipment 120 with communication functions. The network equipment 110 and the terminal equipment 120 may be the specific equipment described above, and will not be repeated here. The communication device may also include other devices in the communication system 100, such as network controllers, mobility management entities and other network entities, which are not limited in this embodiment of the present application.

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

It should be understood that the "indication" mentioned in the embodiments of the present application may be a direct indication, may also be an indirect indication, and may also mean that there is an association relationship. For example, A indicates B, which can mean that A directly indicates B, for example, B can be obtained through A; it can also indicate that A indirectly indicates B, for example, A indicates C, and B can be obtained through C; it can also indicate that there is an association between A and B relation.

In the description of the embodiments of the present application, the term "corresponding" may indicate that there is a direct or indirect correspondence between the two, or that there is an association between the two, or that it indicates and is indicated, configuration and is configuration etc.

In the embodiment of this application, "predefinition" can be realized by pre-saving corresponding codes, tables or other methods that can be used to indicate related information in devices (for example, including terminal devices and network devices). The implementation method is not limited. For example, predefined can refer to those defined in the protocol.

In the embodiment of the present application, the "protocol" may refer to a standard protocol in the communication field, for example, it may include the LTE protocol, the NR protocol, and related protocols applied in future communication systems, which is not limited in the present application.

In order to facilitate understanding of the technical solutions of the embodiments of the present application, the technical solutions of the present application are described in detail below through specific examples. The following related technologies may be optionally combined with the technical solutions of the embodiments of the present application as optional solutions, and all of them belong to the protection scope of the embodiments of the present application. The embodiment of the present application includes at least part of the following contents.

In some scenarios, in order to improve and optimize the user handover experience, a successful handover report (successful handover report, SHR) is introduced to record the problems found in the successful handover.

In some embodiments, a successful handover report is only logged when certain conditions are met. Such as exceeding the relevant thresholds of timers T310, T312 and T304.

In some embodiments, the timer T304 is started when a radio resource control (Radio Resource Control, RRC) connection reconfiguration (Connection Reconfiguration) message is received, wherein the RRC reconfiguration message includes mobility control information (Mobility Control info). Timer T304 is stopped when the handover is successfully completed.

In some embodiments, timer T310 is started when a physical layer problem of the primary cell (PCell) is detected. When the N311 continuous in-sync indications (consecutive in-sync indications) of the PCell sent by the lower layer are received, or when the switching process is triggered, or when the connection re-establishment procedure (connection re-establishment procedure) is started, the timer T310 stops.

In some embodiments, when the timer 310 is running, a measurement report of the measurement identifier is triggered, wherein the measurement identifier has been configured as T312, and in this case, the timer T312 is started. When the N311 continuous in-sync indications of the PCell sent by the lower layer are received, or when the handover process is triggered, or when the connection re-establishment procedure is started, or, the T310 timer When expired, timer T312 is stopped.

In some scenarios, when the terminal device takes a long time to access the target network (for example, T304 exceeds a certain threshold), when the terminal device has a physical layer problem, it takes a long time to initiate the handover process, or when the terminal device If the measurement report is sent but the handover command (handover command) is received after a certain period of time, it may cause the terminal device to record the SHR and report a successful handover report when the network device needs it.

In some cases, when the T304 operation exceeds a certain time limit, the reason why the terminal device completes the access goal is likely to be a problem encountered in random access, or the quality of the downlink measurement beam corresponding to the random access resource of the terminal device is poor. , causing the terminal device to perform random access only by using contention random access resources. In this case, recording information related to random access resources in the SHR can help the network optimize random access resource allocation. That is, the network device can adjust subsequent handover-related parameters according to the SHR.

In some scenarios, there may be problems such as handover to wrong cell (handover to wrong cell) or premature handover when the terminal device performs handover.

Handover failure occurs when the terminal device accesses the target network node (or target cell), or radio link failure (RLF) occurs on the target network node (or target cell) after the handover is successfully completed. , it can be considered as handover to wrong cell or premature handover.

For switching to a wrong cell, the terminal device may select a third cell different from the target cell or the source cell through cell selection or cell reselection, and initiate a reestablishment process.

After the terminal device completes the reconstruction, the terminal device can send the RLF report to the base station where the current serving cell is located. The network device can adjust subsequent handover-related parameters according to the RLF report.

Further, the base station where the current serving cell is located sends the RLF report to the base station where the target cell is located, and the base station where the target cell is located determines according to the RLF report that this handover is a handover to a wrong cell.

For example, the base station where the target cell is located may determine that the handover is a handover to a wrong cell when the following conditions are met:

The terminal reported timer (UE reported timer) is less than a certain time threshold (such as Tstore_UE_context), wherein the terminal reported timer is used to record the time spent from the initialization of the last handover to the connection failure;

The first cell to attempt reestablishment or the cell to which the terminal device attempts to reconnect is not the cell that served the terminal device in the latest handover initialization, or the target cell of the handover.

The base station where the target cell is located sends the judgment result to the base station where the source cell is located, and the base station where the source cell is located changes the threshold setting of the measurement object (MO) corresponding to the terminal measurement report event according to the judgment result.

For premature handover, the terminal equipment can select the source cell through cell selection or cell reselection, and initiate the reestablishment process.

After the terminal device completes the reconstruction, the terminal device can send the RLF report to the base station where the source cell is located. Wherein, the failed primary cell identifier (failedPCellID) in the RLF report is set to the identifier (Identifier, ID) of the target cell, and the value of the connection failure type (connectionFailureType) is set to 'hof' or 'rlf'.

The base station where the source cell is located determines that this handover is premature handover according to the RLF report.

For example, the base station where the source cell is located may determine that this handover is premature handover if the following conditions are met:

The first cell to attempt re-establishment or to which a terminal device attempts to reconnect is the cell that served the terminal device during the most recent handover initialization.

The base station where the source cell is located changes the threshold setting of the measurement object (MO) corresponding to the terminal measurement report event according to the judgment result.

In some scenarios, for the same handover, the terminal device may report the SHR and the RLF report, which will cause the network device to be unclear about the adjustment direction and/or adjustment range of the handover-related parameters.

FIG. 2 is a schematic flowchart of a wireless communication method 1000 according to an embodiment of the present application. The method 1000 can be executed by a terminal device in the communication system shown in FIG. 1. As shown in FIG. 2, the method 1000 includes the following content :

S1010. In the case of successful handover from the source cell to the target cell, the terminal device processes the recorded successful handover report SHR according to the first information, where the first information includes at least one of the following:

Whether a radio link failure RLF occurs on the target cell during the running of the first timer;

The first duration, wherein the first duration is the duration from when the handover of the terminal equipment is completed to when RLF occurs on the target cell;

The second duration, wherein the second duration is the duration when the terminal device starts to perform handover to the target cell and RLF occurs.

In some embodiments of the present application, in the case of a successful handover from the source cell to the target cell (recorded as the first handover), the terminal device may generate an SHR and further save the SHR, wherein the SHR is used to record the first handover related information, such as the random access resource used by the terminal device to perform the first handover, the source cell of the first handover, the target cell of the first handover, and the like.

Optionally, in some embodiments of the present application, the terminal device processes the recorded successful handover report SHR according to the first information, which may include but not limited to at least one of the following:

According to the first information, determine whether to discard the recorded SHR, or in other words, whether to keep the recorded SHR;

According to the first information, it is determined whether to send the SHR to the network device.

In some embodiments of the present application, the network device is a network device corresponding to the current serving cell.

Optionally, the current serving cell may be a target cell, that is, the network device may be a target base station.

Optionally, the current serving cell is the source cell, that is, the network device is the source base station.

Optionally, the current serving cell may also be other cells except the source cell and the target cell.

Optionally, in some embodiments, the terminal device may determine, according to the first information, whether the occurrence of RLF on the target cell is related to the first handover (or whether the occurrence of RLF on the target cell is caused by the first handover), and further Determines whether to discard the recorded SHR, or whether to send the SHR to the network device.

For example, if the terminal device determines according to the first information that the occurrence of RLF on the target cell is related to the first handover, discard the SHR, and/or not send the SHR to the network device. That is to say, for the same handover, the terminal device will not report both the SHR and the RLF report.

For another example, if the terminal device determines according to the first information that the occurrence of RLF on the target cell is not related to the first handover, the SHR is not discarded, and/or the SHR is sent to the network device. That is to say, the terminal device can report the SHR and RLF reports of different handovers.

In some embodiments of the present application, the terminal device starts the first timer when at least one of the following conditions is met:

The terminal device successfully executes the cell handover, or in other words, completes the handover;

The terminal device records the SHR.

It should be understood that, in the embodiment of the present application, during the running of the first timer, whether RLF occurs on the target cell may be used to determine whether the RLF is related to the first handover, or whether the RLF is caused by the first handover.

Optionally, if RLF occurs on the target cell during the running of the first timer (or before timeout), it may be considered that the RLF is related to the first handover, or the RLF is caused by the first handover, Alternatively, the first handover should not be considered a successful handover, or the SHR is invalid.

Optionally, if RLF occurs on the target cell after the first timer expires, it can be considered that the RLF is not related to the first handover, or that the RLF is not caused by the first handover, or that the first handover can be considered to be A successful handover, or SHR is valid.

In some embodiments of this application, S1010 may include:

If the RLF occurs on the target cell before the first timer expires, the terminal device discards the SHR.

As mentioned above, if the RLF occurs on the target cell before the first timer expires, it can be considered that this RLF is related to the first handover, therefore, the terminal device can discard the SHR.

In this case, the terminal device may also generate an RLF report according to the occurrence of the RLF on the target cell, and the RLF report is used to record relevant information of the occurrence of the RLF in the target cell.

Further, the terminal device may report the RLF report to the network device without reporting the SHR. Therefore, for the same handover, the terminal device will not report both the RLF report and the SHR, which is beneficial to avoid affecting the network device's adjustment strategy for subsequent handover-related parameters.

In other embodiments of the present application, if RLF occurs on the target cell after the first timer expires, the terminal device does not discard the SHR.

As mentioned above, after the first timer expires, RLF occurs on the target cell, it can be considered that this RLF is not related to the first handover, therefore, the terminal device may not discard the SHR.

Further, the terminal device may report the SHR and the RLF report to the network device, where the SHR and the RLF report may not be considered to correspond to the same handover. Therefore, for the same handover, the terminal device will not report both the RLF report and the SHR, which is beneficial to avoid affecting the adjustment strategy of the network device for subsequent handover parameters, but it can report the SHR and RLF reports of different handovers.

In conjunction with the description in FIG. 3 , the specific process will be described. As shown in Figure 3, the following steps may be included:

S1011, the terminal device executes the handover and records the SHR.

S1012. The terminal device starts a first timer when the handover is completed or the SHR is recorded.

S1013. Determine whether to discard the SHR according to whether RLF occurs on the target cell before the first timer expires.

If yes, execute S1014, otherwise execute S1015.

S1014. Before the first timer expires, no RLF occurs in the target cell, and the terminal device does not discard the SHR.

S1015. After the first timer expires, RLF occurs on the target cell, and the terminal device does not discard the SHR.

In some embodiments of the present application, the terminal device temporarily does not send the SHR after generating the SHR, and further determines whether to send the SHR to the network device according to whether RLF occurs on the target cell during the running of the first timer.

For example, if the RLF occurs on the target cell before the first timer expires, the terminal device does not send the SHR.

For another example, if RLF occurs on the target cell after the first timer expires, the terminal device sends an SHR.

In some other embodiments of the present application, after the terminal device generates the SHR, it sends the SHR to the network device, and further, determines whether the SHR is valid according to whether RLF occurs on the target cell during the running of the first timer and further determining whether to send first indication information to the network device, where the first indication information is used to indicate that the SHR is invalid, or that the SHR is unavailable.

For example, if RLF occurs on the target cell before the first timer expires, in this case, the sent SHR may be considered invalid, and therefore, the terminal device may send the first indication information to the network device.

For another example, if RLF occurs on the target cell after the first timer expires, in this case, it may be considered that the sent SHR is valid, and the terminal device does not send the first indication information to the network device.

Therefore, for a handover, after the terminal device reports the SHR, it can be determined whether the sent SHR is valid according to whether RLF occurs on the target cell during the running of the first timer, and further indicates to the network device whether the reported SHR is available. If it is unavailable, the network device may not adjust handover-related parameters according to the SHR, and if available, the network device may adjust handover-related parameters according to the SHR.

In some embodiments of the present application, the duration of the first timer may be a preset value, or may be a value configured by a network device, or may be determined according to other parameters, which is not limited in this application.

In some embodiments, the duration of the first timer is determined according to the duration threshold (for example, Tstore_UE_context) from the initialization of the handover to the occurrence of the RLF event and the duration (denoted as T) from the initialization of the handover to the completion of the handover (or SHR generation), for example , the duration of the first timer may be set as Tstore_UE_context-T.

In some embodiments of the present application, it is possible to count the duration from when the terminal equipment completes handover (or SHR generation) to the RLF occurrence on the target cell, that is, the first duration, as shown in FIG. 4 , and further determines whether to discard the SHR according to the first duration, And/or, whether to report the SHR to the network device.

It should be understood that, in this embodiment of the present application, the size of the first duration may be used to determine whether the RLF is related to the first handover, or whether the RLF is caused by the first handover.

Optionally, when the first duration is short, it may be considered that the RLF is related to the first handover, or the RLF is caused by the first handover, or the first handover should not be considered as a successful handover, or is SHR invalid.

Optionally, when the first duration is relatively long, it can be considered that the RLF is not related to the first handover, or that the RLF is not caused by the first handover, or that the first handover can be considered as a successful handover, or that the SHR is valid .

In some embodiments, the terminal device may determine whether to discard the SHR according to the first duration and the first time threshold, and/or whether to report the SHR to the network device.

For example, if the first duration is less than or equal to the first time threshold, the terminal device discards the SHR, and/or does not report the SHR to the network.

For another example, if the first duration is greater than the first time threshold, the terminal device does not discard the SHR, and/or reports the SHR to the network device.

In some embodiments, the first time threshold may be predefined or configured by the network device.

In some other embodiments of the present application, it is possible to count the duration from the handover initialization of the terminal equipment to the occurrence of RLF on the target cell, that is, the second duration, as shown in FIG. 4 , and further determine whether to discard the SHR according to the second duration, and/or, Whether to report SHR to network devices.

It should be understood that, in this embodiment of the present application, the size of the second duration may be used to determine whether the RLF is related to the first handover, or whether the RLF is caused by the first handover.

Optionally, when the second duration is short, it may be considered that the RLF is related to the first handover, or the RLF is caused by the first handover, or the first handover should not be considered as a successful handover, or is SHR invalid.

Optionally, when the second duration is longer, it can be considered that the RLF is not related to the first handover, or that the RLF is not caused by the first handover, or that the first handover can be considered as a successful handover, or that the SHR is valid .

In some embodiments, the terminal device may determine whether to discard the SHR according to the second duration and the second time threshold, and/or whether to report the SHR to the network device.

For example, if the second duration is less than or equal to the second time threshold, the terminal device discards the SHR, and/or does not report the SHR to the network.

For another example, if the second duration is greater than the second time threshold, the terminal device does not discard the SHR, and/or reports the SHR to the network device.

In some embodiments, the second time threshold is predefined, or configured by the network device, for example, configured by the network device through a handover command (handover command), for example, the second time threshold may be set to Tstore_UE_context.

Optionally, in some embodiments, the first time threshold may be determined according to the second time threshold and the duration (denoted as T) from handover initialization to completion of handover (or SHR generation), for example, the first time may be The threshold is set to Tstore_UE_context-T.

Optionally, in some embodiments, the occurrence of RLF on the target cell may be caused by premature handover, or may also be caused by handover to a wrong cell, or may also be caused by other reasons.

Based on the above embodiments, the terminal device can determine whether to discard the SHR and/or send the SHR to the network device according to whether RLF occurs on the target cell during the running of the first timer, which is beneficial to avoid reporting both the SHR and the RLF report for the same handover , affecting the adjustment strategy of the network device for handover-related parameters.

Alternatively, the terminal device may determine whether to discard the SHR and/or send the SHR to the network device according to the duration from the completion of the handover to the occurrence of the RLF on the target cell (i.e. the first duration), which is beneficial to avoid both reporting the SHR and Report the RLF report, which affects the adjustment strategy of the network equipment for handover-related parameters.

Alternatively, the terminal device may determine whether to discard the SHR and/or send the SHR to the network device according to the duration (i.e. the second duration) from handover initialization to the occurrence of RLF on the target cell, which is beneficial to avoid both reporting the SHR and Report the RLF report, which affects the adjustment strategy of the network equipment for handover-related parameters.

The above describes in detail the wireless communication method according to one embodiment of the present application from the perspective of terminal equipment in conjunction with FIG. 2 to FIG. method of communication. It should be understood that the description on the network device side corresponds to the description on the terminal device side, similar descriptions can be referred to above, and will not be repeated here to avoid repetition.

FIG. 5 is a schematic flowchart of a wireless communication method 1100 according to another embodiment of the present application. The method 1100 may be executed by a network device in the communication system shown in FIG. 1 . As shown in FIG. 5 , the method 1100 includes As follows:

S1110. The network device receives a successful handover report SHR sent by the terminal device, where the SHR is used to indicate that the terminal device is successfully handed over from the source cell to the target cell;

S1120. The network device receives first indication information sent by the terminal device, where the first indication information is used to indicate that the SHR is unavailable.

It should be understood that, in the method 1100, the first indication information may correspond to the first indication information in the method 1000. For specific implementation, refer to the relevant descriptions of the foregoing embodiments, and for brevity, details are not repeated here.

Optionally, the current serving cell may also be a cell other than the source cell and the target cell, and the network device in this case is marked as a third base station.

In some embodiments of the present application, the method also includes:

The network device does not send the SHR to the network device corresponding to the source cell; and/or

The network device does not send the SHR to the network device corresponding to the target cell.

In some embodiments, the network device is a source base station, and the network device does not send the SHR to the target base station before receiving the first indication information. After receiving the first indication information, the source base station may stop sending the SHR to the target base station, or discard the SHR. Further, the source base station may not adjust handover related parameters based on the SHR.

In some other embodiments, the network device is a target base station, and the network device does not send the SHR to the source base station before receiving the first indication information. After receiving the first indication information, the target base station may stop sending the SHR to the source base station. Further, the target base station may not adjust handover related parameters based on the SHR.

In some other embodiments, the network device is a third base station, and before receiving the first indication information, the network device does not send the SHR to the source base station and/or the target base station. After receiving the first indication information, the third base station may stop sending the SHR to the source base station and/or the target base station.

In some embodiments of the present application, the method 1100 further includes:

The network device sends second indication information to the network device corresponding to the source cell, and/or

The network device sends second indication information to the network device corresponding to the target cell;

Wherein, the second indication information is used to indicate that the SHR is unavailable.

In some embodiments, the network device is a source base station, and before receiving the first indication information, the network device has sent the SHR to the target base station. In this case, the source base station may send second indication information to the target base station, where the second indication information is used to indicate that the SHR is unavailable. Further, the source base station and the target base station may not adjust handover related parameters based on the SHR.

In some other embodiments, the network device is a target base station, and before receiving the first indication information, the network device has sent the SHR to the source base station. In this case, the target base station may send second indication information to the source base station, where the second indication information is used to indicate that the SHR is unavailable. Further, the source base station and the target base station may not adjust handover related parameters based on the SHR.

In still some embodiments, the network device is a third base station, and before receiving the first indication information, the network device has sent the SHR to the source base station and/or the target base station. In this case, the third base station may send second indication information to the source base station and/or the target base station, where the second indication information is used to indicate that the SHR is unavailable. Further, the base station that receives the second indication information may not adjust handover related parameters based on the received SHR.

In some embodiments of the present application, the first indication information is sent by the terminal device when the SHR is invalid, wherein the invalid SHR includes: before the first timer expires, the target RLF occurs on the cell.

In some embodiments of the present application, the first timer is turned on when at least one of the following conditions is met:

The terminal device executes cell handover successfully;

The terminal device records the SHR.

FIG. 6 is a schematic interaction diagram of a wireless communication method according to another embodiment of the present application. As shown in FIG. 6, the method 1200 includes at least part of the following:

S1210, the terminal device sends a successful handover report SHR and/or a radio link failure RLF report to the network device.

In the method 1200, the terminal device may carry information for the network device to distinguish whether the RLF event corresponding to the RLF report is related to the handover corresponding to the SHR in the reported SHR and RLF report. Therefore, based on the method 1100, the network device can determine whether the RLF event corresponding to the RLF report is related to the handover corresponding to the SHR according to the SHR reported by the terminal device and the information carried in the RLF report, or whether the RLF event is related to the handover corresponding to the SHR. switch causes. Further, in the case that the RLF event is related to the handover corresponding to the SHR, the network device may adjust handover-related parameters based on the RLF report.

It should be understood that, in the embodiment of the present application, for the same handover, if the terminal device reports both the SHR and the RLF report, in this case, the reported SHR can be considered invalid. Therefore, the network device is adjusting the handover related parameter, may not refer to an invalid SHR.

Optionally, in this embodiment of the present application, when the RLF event corresponding to the RLF report reported by the terminal device is related to the handover corresponding to the reported SHR, the terminal device considers that the handover corresponding to the SHR is not a successful handover, or, the SHR Therefore, the SHR may not be referred to when adjusting handover-related parameters.

In some embodiments of the present application, the SHR includes time information corresponding to a successful handover and/or identification information related to the successful handover.

In some embodiments of the present application, the RLF report includes time information when the RLF event occurs and/or identification information related to the RLF event.

Therefore, the network device can determine whether the RLF event corresponding to the RLF report is related to the handover corresponding to the SHR according to the SHR reported by the terminal device and the time information and identification information in the RLF report.

In some embodiments of the present application, the identification information related to the successful handover includes at least one of the following:

The identification information of the terminal device performing the successful handover, the identification information of the successful handover, the identification information of the source cell corresponding to the successful handover, and the identification information of the target cell corresponding to the successful handover.

Optionally, the identification information of the terminal device performing the successful handover may be the identification information allocated to the terminal device in the successful handover.

Optionally, the identification information of the successful handover may be used to uniquely identify the successful handover.

In some embodiments, the identification information related to the RLF event includes at least one of the following:

Identification information of the target cell corresponding to the RLF event, and identification information of the RLF event.

Optionally, the identification information of the RLF event may be used to uniquely identify the RLF event.

In some embodiments, the time information corresponding to the successful handover may be the time information when the successful handover is completed.

In some embodiments of the present application, the method 1200 further includes:

S1220, the time information corresponding to the successful handover included in the SHR of the network device and/or the identification information related to the successful handover, and the RLF report includes the time information of the occurrence of the RLF event and/or the related information of the RLF event identification information of the RLF event, and determine whether the RLF event is related to the successful handover.

As an example, if the time interval between the time information of the occurrence of the RLF event and the time information corresponding to the successful handover is less than or equal to the third time threshold, and the identification information related to the successful handover and the identification information related to the RLF event The information is the same, and it is determined that the RLF event is related to the successful handover.

As another example, if the time interval between the time information corresponding to the RLF event and the time information corresponding to the successful handover is greater than the third time threshold, or the identification information related to the successful handover and the time information related to the RLF event The identification information is different, and it is determined that the RLF event is not related to the successful handover.

Optionally, the identification information related to the successful handover is the same as the identification information related to the RLF event, including: the identification information of the target cell corresponding to the successful handover is the same as the identification information of the target cell corresponding to the RLF event.

Optionally, the identification information related to the successful handover is different from the identification information related to the RLF event, including: the identification information of the target cell corresponding to the successful handover is different from the identification information of the target cell corresponding to the RLF event.

In some embodiments, the third time threshold may be predefined, or configured by the network device, for example, configured by the network device through a handover command.

In some embodiments, the third time threshold may be determined according to the duration threshold (for example, Tstore_UE_context) from handover initialization to the occurrence of the RLF event and the time length (denoted as T) from handover initialization to completion of handover (or SHR generation), for example, A third temporal threshold may be set to Tstore_UE_context-T.

Based on the above embodiments, the terminal device may carry information used for the network device to distinguish whether the RLF event corresponding to the RLF report is related to the handover corresponding to the SHR in the reported SHR and RLF report. Therefore, the network device can determine whether the RLF event corresponding to the RLF report is related to the handover corresponding to the SHR according to the SHR reported by the terminal device and the information carried in the RLF report. Further, when the RLF event is related to the handover corresponding to the SHR, the network device can adjust the handover-related parameters based on the RLF report, which is beneficial to avoid that for the same handover, the terminal device reports both the SHR and the RLF report, causing the network device to It is not clear how to adjust the parameters related to the subsequent switching.

The method embodiment of the present application is described in detail above in conjunction with FIG. 2 to FIG. 6 , and the device embodiment of the present application is described in detail below in conjunction with FIG. 7 to FIG. 13 . It should be understood that the device embodiment and the method embodiment correspond to each other, similar to The description can refer to the method embodiment.

Fig. 7 shows a schematic block diagram of a terminal device 400 according to an embodiment of the present application. As shown in FIG. 7, the terminal device 400 includes:

The processing unit 410 is configured to process the recorded successful handover report SHR according to the first information in the case of successful handover from the source cell to the target cell, wherein the first information includes at least one of the following:

In some embodiments of the present application, the processing unit 410 is further configured to:

If RLF occurs on the target cell before the first timer expires, discarding the SHR; and/or

If RLF occurs on the target cell after the first timer expires, the SHR is not discarded.

If RLF occurs on the target cell before the first timer expires, and the terminal device has sent the SHR, it is determined to send first indication information to the network equipment, and the first indication information is used to indicate The SHR is not available.

Determine whether to discard the SHR according to the first duration and the first time threshold.

If the first duration is less than or equal to the first time threshold, discarding the SHR; or

If the first duration is greater than the first time threshold, the SHR is not discarded.

In some embodiments of the present application, the first time threshold is predefined or configured by a network device.

Determine whether to discard the SHR according to the second duration and the second time threshold.

discarding the SHR if the second duration is less than or equal to the second time threshold; or

If the second duration is greater than the second time threshold, the SHR is not discarded.

In some embodiments of the present application, the second time threshold is configured by the network device through a handover command, or the first time threshold is predefined.

In some embodiments of the present application, the terminal device further includes:

A communication unit, configured to report an RLF report to the network device when RLF occurs on the target cell and the SHR is discarded; or, when RLF occurs on the target cell and the SHR is not discarded , reporting the SHR and RLF report to the network device.

The terminal device executes cell handover successfully;

The terminal device records the SHR.

Optionally, in some embodiments, the above-mentioned communication unit may be a communication interface or a transceiver, or an input-output interface of a communication chip or a system-on-chip. The aforementioned processing unit may be one or more processors.

It should be understood that the terminal device 400 according to the embodiment of the present application may correspond to the terminal device in the method embodiment of the present application, and the above-mentioned and other operations and/or functions of each unit in the terminal device 400 are to realize the For the sake of brevity, the corresponding process of the terminal device in the shown method 1000 is not repeated here.

Fig. 8 is a schematic block diagram of a network device according to an embodiment of the present application. The network device 500 of FIG. 8 includes:

The communication unit 510 is configured to receive a successful handover report SHR sent by the terminal device, where the SHR is used to indicate that the terminal device is successfully handed over from the source cell to the target cell; and

Receive first indication information sent by the terminal device, where the first indication information is used to indicate that the SHR is unavailable.

In some embodiments of the present application, the network device is a network device corresponding to the current serving cell, and the communication unit 510 is further configured to:

Not sending the SHR to the network device corresponding to the source cell; and/or

The SHR is not sent to the network device corresponding to the target cell.

sending second indication information to the network device corresponding to the source cell, and/or

Sending second indication information to a network device corresponding to the target cell;

The terminal device executes cell handover successfully;

The terminal device records the SHR.

It should be understood that the network device 500 according to the embodiment of the present application may correspond to the network device in the method embodiment of the present application, and the above-mentioned and other operations and/or functions of each unit in the network device 500 are for realizing the method shown in FIG. 5 For the sake of brevity, the corresponding flow of the network device in 1100 will not be repeated here.

FIG. 9 shows a schematic block diagram of a terminal device 800 according to an embodiment of the present application. As shown in FIG. 9, the terminal device 800 includes:

The communication unit 810 is configured to send a successful handover report SHR and/or a radio link failure RLF report to the network device, wherein the SHR includes time information corresponding to the successful handover and/or identification information related to the successful handover, the The RLF report includes time information when the RLF event occurs and/or identification information related to the RLF event.

In some embodiments of the present application, the identification information related to the RLF event includes at least one of the following:

It should be understood that the terminal device 800 according to the embodiment of the present application may correspond to the terminal device in the method embodiment of the present application, and the above-mentioned and other operations and/or functions of each unit in the terminal device 800 are for realizing the method shown in FIG. 6 For the sake of brevity, the corresponding process of the terminal device in 1200 will not be repeated here.

Fig. 10 is a schematic block diagram of a network device according to an embodiment of the present application. The network device 1300 of FIG. 10 includes:

The communication unit 1310 is configured to receive a successful handover report SHR and/or a radio link failure RLF report sent by the terminal device, wherein the SHR includes time information corresponding to the successful handover and/or identification information related to the successful handover, and the RLF The report includes time information when the RLF event occurs and/or identification information related to the RLF event.

In some embodiments of the present application, the network device 1300 further includes:

The processing unit is configured to include the time information corresponding to the successful handover included in the SHR and/or the identification information related to the successful handover, and the RLF report includes the time information of the occurrence of the RLF event and/or the related information of the RLF event identification information.

In some embodiments of the present application, the processing unit is also used for:

If the time interval between the time information of the occurrence of the RLF event and the time information corresponding to the successful handover is less than or equal to the third time threshold, and the identification information related to the successful handover is the same as the identification information related to the RLF event, determine said RLF event is associated with said successful handover; or

If the time interval between the time information of the occurrence of the RLF event and the time information corresponding to the successful handover is greater than the third time threshold, or the identification information related to the successful handover is different from the identification information related to the RLF event, determine the The RLF event is not related to the successful handover.

In some embodiments of this application,

In some embodiments of the present application, the identification information related to the successful handover is the same as the identification information related to the RLF event, including: the identification information of the target cell corresponding to the successful handover and the target cell corresponding to the RLF event The identification information is the same;

The identification information related to the successful handover is different from the identification information related to the RLF event, including: the identification information of the target cell corresponding to the successful handover is different from the identification information of the target cell corresponding to the RLF event.

It should be understood that the network device 1300 according to the embodiment of the present application may correspond to the network device in the method embodiment of the present application, and the above-mentioned and other operations and/or functions of each unit in the network device 1300 are for realizing the method shown in FIG. 6 For the sake of brevity, the corresponding flow of the network device in 1200 will not be repeated here.

FIG. 11 is a schematic structural diagram of a communication device 600 provided by an embodiment of the present application. The communication device 600 shown in FIG. 11 includes a processor 610, and the processor 610 can call and run a computer program from a memory, so as to implement the method in the embodiment of the present application.

Optionally, as shown in FIG. 11 , the communication device 600 may further include a memory 620 . Wherein, the processor 610 can invoke and run a computer program from the memory 620, so as to implement the method in the embodiment of the present application.

Wherein, the memory 620 may be an independent device independent of the processor 610 , or may be integrated in the processor 610 .

Optionally, as shown in FIG. 11 , the communication device 600 may further include a transceiver 630, and the processor 610 may control the transceiver 630 to communicate with other devices, specifically, to send information or data to other devices, or receive other Information or data sent by the device.

Wherein, the transceiver 630 may include a transmitter and a receiver. The transceiver 630 may further include antennas, and the number of antennas may be one or more.

Optionally, the communication device 600 may specifically be the network device of the embodiment of the present application, and the communication device 600 may implement the corresponding processes 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. .

Optionally, the communication device 600 may specifically be the mobile terminal/terminal device of the embodiment of the present application, and the communication device 600 may implement the corresponding processes implemented by the mobile terminal/terminal device in each method of the embodiment of the present application, for the sake of brevity , which will not be repeated here.

FIG. 12 is a schematic structural diagram of a chip according to an embodiment of the present application. The chip 700 shown in FIG. 12 includes a processor 710, and the processor 710 can call and run a computer program from a memory, so as to implement the method in the embodiment of the present application.

Optionally, as shown in FIG. 12 , the chip 700 may further include a memory 720 . Wherein, the processor 710 can invoke and run a computer program from the memory 720, so as to implement the method in the embodiment of the present application.

Wherein, the memory 720 may be an independent device independent of the processor 710 , or may be integrated in the processor 710 .

Optionally, the chip 700 may also include an input interface 730 . Wherein, the processor 710 can control the input interface 730 to communicate with other devices or chips, specifically, can obtain information or data sent by other devices or chips.

Optionally, the chip 700 may also include an output interface 740 . Wherein, the processor 710 can control the output interface 740 to communicate with other devices or chips, specifically, can output information or data to other devices or chips.

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

Optionally, the chip can be applied to the mobile terminal/terminal device in the embodiments of the present application, and the chip can implement the corresponding processes implemented by the mobile terminal/terminal device in the various methods of the embodiments of the present application. For the sake of brevity, here No longer.

It should be understood that the chip mentioned in the embodiment of the present application may also be called a system-on-chip, a system-on-chip, a system-on-a-chip, or a system-on-a-chip.

Fig. 13 is a schematic block diagram of a communication system 900 provided by an embodiment of the present application. As shown in FIG. 13 , the communication system 900 includes a terminal device 910 and a network device 920 .

Wherein, the terminal device 910 can be used to realize the corresponding functions realized by the terminal device in the above method, and the network device 920 can be used to realize the corresponding functions realized by the network device in the above method. .

It should be understood that the processor in the embodiment of the present application may be an integrated circuit chip, which has a signal processing capability. In the implementation process, each step of the above-mentioned method embodiments may be completed by an integrated logic circuit of hardware in a processor or instructions in the form of software. The above-mentioned processor can be a general-purpose processor, a digital signal processor (Digital Signal Processor, DSP), an application-specific integrated circuit (Application Specific Integrated Circuit, ASIC), an off-the-shelf programmable gate array (Field Programmable Gate Array, FPGA) or other available Program logic devices, discrete gate or transistor logic devices, discrete hardware components. Various methods, steps, and logic block diagrams disclosed in the embodiments of the present application may be implemented or executed. A general-purpose processor may be a microprocessor, or the processor may be any conventional processor, or the like. The steps of the method disclosed in connection with the embodiments of the present application may be directly implemented by a hardware decoding processor, or implemented 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, register. 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 embodiments of the present application may be a volatile memory or a nonvolatile memory, or may include both volatile and nonvolatile memories. 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), electronically programmable Erase Programmable Read-Only Memory (Electrically EPROM, EEPROM) or Flash. The volatile memory can be Random Access Memory (RAM), which acts as external cache memory. By way of illustration and not limitation, 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 Memory Bus Random Access Memory (Direct Rambus RAM, DR RAM). It should be noted that the memory of the systems and methods described herein is intended to include, but not be limited to, these and any other suitable types of memory.

It should be understood that the above-mentioned memory is illustrative but not restrictive. For example, the memory in the embodiment of the present application may also be a static random access memory (static RAM, SRAM), a 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, the memory in the embodiments of the present application is intended to include, but not be 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 can be applied to the network device in the embodiments of the present application, and the computer program enables the computer to execute the corresponding processes implemented by the network device in the methods of the embodiments of the present application. For brevity, here No longer.

Optionally, the computer-readable storage medium can be applied to the mobile terminal/terminal device in the embodiments of the present application, and the computer program enables the computer to execute the corresponding processes implemented by the mobile terminal/terminal device in the various methods of the embodiments of the present application , for the sake of brevity, it is not repeated here.

The embodiment of the present application also provides 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, the Let me repeat.

Optionally, the computer program product can be applied to the mobile terminal/terminal device 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/terminal device in the methods of the embodiments of the present application, For the sake of brevity, details are not repeated 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 is run on the computer, the computer executes the corresponding process implemented by the network device in each method of the embodiment of the present application. For the sake of brevity , which will not be repeated here.

Optionally, the computer program can be applied to the mobile terminal/terminal device in the embodiment of the present application. When the computer program is run on the computer, the computer executes each method in the embodiment of the present application to be implemented by the mobile terminal/terminal device For the sake of brevity, the corresponding process will not be repeated here.

Those skilled in the art can appreciate that the units and algorithm steps of the examples described in conjunction 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 constraints of the technical solution. Those skilled in the art may use different methods to implement the described functions for each specific application, but such implementation should not be regarded as exceeding the scope of the present application.

Those skilled in the art can clearly understand that for the convenience and brevity of the 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 systems, devices and methods 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. In actual implementation, there may be other division methods. For example, multiple units or components can be combined or May be integrated into another system, or some features may be ignored, or not implemented. In another point, the mutual coupling or direct coupling or communication connection shown or discussed may be through some interfaces, and the indirect coupling or communication connection of devices or units may be in electrical, mechanical or other forms.

The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place, or may be distributed to multiple network units. Part or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.

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

If the functions described above are realized in the form of software function units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application is essentially or the part that contributes to the prior art 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 methods described in the various embodiments 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 disc and other media that can store program codes. .

The above is only a specific implementation of the application, but the scope of protection of the application is not limited thereto. Anyone familiar with the technical field can easily think of changes or substitutions within the technical scope disclosed in the application. Should be covered within the protection scope of this application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

Claims

A method for wireless communication, comprising:

In the case of a successful handover from the source cell to the target cell, the terminal device processes the recorded successful handover report SHR according to the first information, wherein the first information includes at least one of the following:

Whether a radio link failure RLF occurs on the target cell during the running of the first timer;

The first duration, wherein the first duration is the duration from when the handover of the terminal equipment is completed to when RLF occurs on the target cell;

The second duration, wherein the second duration is the duration when the terminal device starts to perform handover to the target cell and RLF occurs.
The method according to claim 1, wherein the terminal device processes the recorded successful handover report SHR according to the first information, including:

If RLF occurs on the target cell before the first timer expires, the terminal device discards the SHR; and/or

If the RLF occurs on the target cell after the first timer expires, the terminal device does not discard the SHR.
The method according to claim 1, wherein the terminal device processes the recorded successful handover report SHR according to the first information, including:

If RLF occurs on the target cell before the first timer expires, and the terminal equipment has sent the SHR, the terminal equipment sends first indication information to the network equipment, and the first indication information Used to indicate that the SHR is unavailable.
The method according to any one of claims 1-3, wherein the terminal device processes the recorded successful handover report SHR according to the first information, including:

The terminal device determines whether to discard the SHR according to the first duration and the first time threshold.
The method according to claim 4, wherein the terminal device determines whether to discard the SHR according to the first duration and the first time threshold, comprising:

If the first duration is less than or equal to the first time threshold, the terminal device discards the SHR; or

If the first duration is greater than the first time threshold, the terminal device does not discard the SHR.
The method according to claim 5, wherein the first time threshold is predefined, or configured by a network device.
The method according to any one of claims 1-6, wherein the terminal device processes the recorded successful handover report SHR according to the first information, including:

The terminal device determines whether to discard the SHR according to the second duration and the second time threshold.
The method according to claim 7, wherein the terminal device determines whether to discard the SHR according to the second duration and the first time threshold, comprising:

If the second duration is less than or equal to the second time threshold, the terminal device discards the SHR; or

If the second duration is greater than the second time threshold, the terminal device does not discard the SHR.
The method according to claim 7 or 8, wherein the second time threshold is configured by a network device through a handover command, or the second time threshold is predefined.
The method according to any one of claims 1-9, further comprising:

When RLF occurs on the target cell and the terminal device discards the SHR, the terminal device reports an RLF report to the network device; or

When RLF occurs on the target cell and the terminal device does not discard the SHR, the terminal device reports the SHR and the RLF report to the network device.
The method according to any one of claims 1-10, wherein the first timer is turned on when at least one of the following conditions is met:

The terminal device executes cell handover successfully;

The terminal device records the SHR.
A method for wireless communication, comprising:

The network device receives a successful handover report SHR sent by the terminal device, where the SHR is used to indicate that the terminal device is successfully handed over from the source cell to the target cell;

The network device receives first indication information sent by the terminal device, where the first indication information is used to indicate that the SHR is unavailable.
The method according to claim 12, wherein the network device is a network device corresponding to the current serving cell, and the method further comprises:

The network device does not send the SHR to the network device corresponding to the source cell; and/or

The network device does not send the SHR to the network device corresponding to the target cell.
The method according to claim 12, wherein the network device is a network device corresponding to the current serving cell, and the method further comprises:

The network device sends second indication information to the network device corresponding to the source cell, and/or

The network device sends second indication information to the network device corresponding to the target cell;

Wherein, the second indication information is used to indicate that the SHR is unavailable.
The method according to any one of claims 12-14, wherein the first indication information is sent by the terminal device when the SHR is invalid, wherein the invalid SHR includes: Before the first timer expires, RLF occurs on the target cell.
The method according to claim 15, wherein the first timer is turned on when at least one of the following conditions is met:

The terminal device executes cell handover successfully;

The terminal device records the SHR.
A method for wireless communication, comprising:

The terminal device sends a successful handover report SHR and/or a radio link failure RLF report to the network device, wherein the SHR includes time information corresponding to the successful handover and/or identification information related to the successful handover, and the RLF report includes occurrence Time information of the RLF event and/or identification information related to the RLF event.
The method according to claim 17, wherein the identification information related to the successful handover includes at least one of the following:

The identification information of the terminal device performing the successful handover, the identification information of the successful handover, the identification information of the source cell corresponding to the successful handover, and the identification information of the target cell corresponding to the successful handover.
The method according to claim 16 or 17, wherein the identification information related to the RLF event includes at least one of the following:

Identification information of the target cell corresponding to the RLF event, and identification information of the RLF event.
A method for wireless communication, comprising:

The network device receives a successful handover report SHR and/or a radio link failure RLF report sent by the terminal device, wherein the SHR includes time information corresponding to the successful handover and/or identification information related to the successful handover, and the RLF report includes Time information when the RLF event occurs and/or identification information related to the RLF event.
The method according to claim 20, wherein the identification information related to the successful handover includes at least one of the following:

The identification information of the terminal device performing the successful handover, the identification information of the successful handover, the identification information of the source cell corresponding to the successful handover, and the identification information of the target cell corresponding to the successful handover.
The method according to claim 20 or 21, wherein the identification information related to the RLF event includes at least one of the following:

Identification information of the target cell corresponding to the RLF event, and identification information of the RLF event.
The method according to any one of claims 21-25, further comprising:

According to the time information corresponding to the successful handover included by the network device in the SHR and/or the identification information related to the successful handover, and the RLF report includes the time information of the occurrence of the RLF event and/or the information related to the RLF event Identification information, used to determine whether the RLF event is related to the successful handover.
The method according to claim 23, wherein the network device includes the time information corresponding to the successful handover and/or the identification information related to the successful handover included in the SHR, and the RLF report includes an occurrence of RLF Time information of the event and/or identification information related to the RLF event, determining whether the RLF event is related to the successful handover, including:

If the time interval between the time information of the occurrence of the RLF event and the time information corresponding to the successful handover is less than or equal to the third time threshold, and the identification information related to the successful handover is the same as the identification information related to the RLF event, determine said RLF event is associated with said successful handover; or

If the time interval between the time information of the occurrence of the RLF event and the time information corresponding to the successful handover is greater than the third time threshold, or the identification information related to the successful handover is different from the identification information related to the RLF event, determine the The RLF event is not related to the successful handover.
The method according to claim 24, wherein the identification information related to the successful handover is the same as the identification information related to the RLF event, comprising: the identification information of the target cell corresponding to the successful handover and the RLF event The identification information of the corresponding target cells is the same;

The identification information related to the successful handover is different from the identification information related to the RLF event, including: the identification information of the target cell corresponding to the successful handover is different from the identification information of the target cell corresponding to the RLF event.
A terminal device, characterized in that it includes:

The processing unit is configured to process the recorded successful handover report SHR according to the first information in the case of successful handover from the source cell to the target cell, wherein the first information includes at least one of the following:

Whether a radio link failure RLF occurs on the target cell during the running of the first timer;

The first duration, wherein the first duration is the duration from when the handover of the terminal equipment is completed to when RLF occurs on the target cell;

The second duration, wherein the second duration is the duration when the terminal device starts to perform handover to the target cell and RLF occurs.
The terminal device according to claim 26, wherein the processing unit is further used for:

If RLF occurs on the target cell before the first timer expires, discarding the SHR; and/or

If RLF occurs on the target cell after the first timer expires, the SHR is not discarded.
The terminal device according to claim 26, wherein the processing unit is further used for:

If RLF occurs on the target cell before the first timer expires, and the terminal device has sent the SHR, it is determined to send first indication information to the network equipment, and the first indication information is used to indicate The SHR is not available.
The terminal device according to any one of claims 26-28, wherein the processing unit is further configured to:

Determine whether to discard the SHR according to the first duration and the first time threshold.
The terminal device according to claim 29, wherein the processing unit is further used for:

If the first duration is less than or equal to the first time threshold, discarding the SHR; or

If the first duration is greater than the first time threshold, the SHR is not discarded.
The terminal device according to claim 30, wherein the first time threshold is predefined, or configured by a network device.
The terminal device according to any one of claims 26-31, wherein the processing unit is further configured to:

Determine whether to discard the SHR according to the second duration and the second time threshold.
The terminal device according to claim 34, wherein the processing unit is further used for:

discarding the SHR if the second duration is less than or equal to the second time threshold; or

If the second duration is greater than the second time threshold, the SHR is not discarded.
The terminal device according to claim 32 or 33, wherein the second time threshold is configured by the network device through a handover command, or the second time threshold is predefined.
The terminal device according to any one of claims 26-34, wherein the terminal device further comprises:

A communication unit, configured to report an RLF report to the network device when RLF occurs on the target cell and the SHR is discarded; or, when RLF occurs on the target cell and the SHR is not discarded , reporting the SHR and RLF report to the network device.
The terminal device according to any one of claims 26-35, wherein the first timer is turned on when at least one of the following conditions is met:

The terminal device executes cell handover successfully;

The terminal device records the SHR.
A network device, characterized in that it includes:

A communication unit, configured to receive a successful handover report SHR sent by the terminal device, where the SHR is used to indicate that the terminal device is successfully handed over from the source cell to the target cell; and

Receive first indication information sent by the terminal device, where the first indication information is used to indicate that the SHR is unavailable.
The network device according to claim 37, wherein the network device is a network device corresponding to the current serving cell, and the communication unit is further used for:

Not sending the SHR to the network device corresponding to the source cell; and/or

The SHR is not sent to the network device corresponding to the target cell.
The network device according to claim 37, wherein the network device is a network device corresponding to the current serving cell, and the communication unit is further used for:

sending second indication information to the network device corresponding to the source cell, and/or

Sending second indication information to a network device corresponding to the target cell;

Wherein, the second indication information is used to indicate that the SHR is unavailable.
The network device according to any one of claims 37-39, wherein the first indication information is sent by the terminal device when the SHR is invalid, wherein the invalid SHR includes: RLF occurs on the target cell before the first timer expires.
The network device according to claim 40, wherein the first timer is turned on when at least one of the following conditions is met:

The terminal device executes cell handover successfully;

The terminal device records the SHR.
A terminal device, characterized in that it includes:

A communication unit, configured to send a successful handover report SHR and/or a radio link failure RLF report to the network device, wherein the SHR includes time information corresponding to the successful handover and/or identification information related to the successful handover, and the RLF The report includes time information when the RLF event occurs and/or identification information related to the RLF event.
The terminal device according to claim 42, wherein the identification information related to the successful handover includes at least one of the following:

The identification information of the terminal device performing the successful handover, the identification information of the successful handover, the identification information of the source cell corresponding to the successful handover, and the identification information of the target cell corresponding to the successful handover.
The terminal device according to claim 42 or 43, wherein the identification information related to the RLF event includes at least one of the following:

Identification information of the target cell corresponding to the RLF event, and identification information of the RLF event.
A network device, characterized in that it includes:

The communication unit receives a successful handover report SHR and/or a radio link failure RLF report sent by the terminal device, wherein the SHR includes time information corresponding to the successful handover and/or identification information related to the successful handover, and the RLF report Including time information when the RLF event occurs and/or identification information related to the RLF event.
The network device according to claim 45, characterized in that,

The identification information related to the successful handover includes at least one of the following:

The identification information of the terminal device performing the successful handover, the identification information of the successful handover, the identification information of the source cell corresponding to the successful handover, and the identification information of the target cell corresponding to the successful handover.
The network device according to claim 45 or 46, characterized in that,

The identification information related to the RLF event includes at least one of the following:

The identification information of the target cell corresponding to the RLF event, the identification information of the RLF event, and the identification information of the target cell corresponding to the RLF event.
The network device according to any one of claims 45-47, wherein the network device further comprises:

The processing unit is configured to include the time information corresponding to the successful handover included in the SHR and/or the identification information related to the successful handover, and the RLF report includes the time information of the occurrence of the RLF event and/or the related information of the RLF event identification information of the RLF event, and determine whether the RLF event is related to the successful handover.
The network device according to claim 48, wherein the processing unit is further used for:

If the time interval between the time information of the occurrence of the RLF event and the time information corresponding to the successful handover is less than or equal to the third time threshold, and the identification information related to the successful handover is the same as the identification information related to the RLF event, determine said RLF event is associated with said successful handover; or

If the time interval between the time information of the occurrence of the RLF event and the time information corresponding to the successful handover is greater than the third time threshold, or the identification information related to the successful handover is different from the identification information related to the RLF event, determine the The RLF event is not related to the successful handover.
The network device according to claim 49, wherein the identification information related to the successful handover is the same as the identification information related to the RLF event, including: the identification information of the target cell corresponding to the successful handover and the RLF event The identification information of the target cell corresponding to the event is the same;

The identification information related to the successful handover is different from the identification information related to the RLF event, including: the identification information of the target cell corresponding to the successful handover is different from the identification information of the target cell corresponding to the RLF event.
A terminal device, characterized by comprising: a processor and a memory, the memory is used to store a computer program, the processor is used to call and run the computer program stored in the memory, and execute any of claims 1 to 11 A method according to any one of claims 17 to 19.
A chip, characterized in that it includes: a processor, configured to call and run a computer program from a memory, so that a device equipped with the chip executes the method according to any one of claims 1 to 11, or as described in A method as claimed in any one of claims 17 to 19.
A computer-readable storage medium, characterized in that it is used to store a computer program, the computer program causes a computer to perform the method according to any one of claims 1 to 11, or any one of claims 17 to 19 method described in the item.
A computer program product, characterized in that it includes computer program instructions, the computer program instructions cause the computer to perform the method as described in any one of claims 1 to 11, or as described in any one of claims 17 to 19 Methods.
A computer program, characterized in that the computer program causes a computer to execute the method according to any one of claims 1-11, or the method according to any one of claims 17-19.
A network device, characterized by comprising: a processor and a memory, the memory is used to store a computer program, the processor is used to invoke and run the computer program stored in the memory, and execute any of the following claims 12 to 16 A method according to one, or a method according to any one of claims 20 to 25.
A chip, characterized in that it includes: a processor, used to call and run a computer program from a memory, so that the device installed with the chip executes the method according to any one of claims 12 to 16, or as A method as claimed in any one of claims 20 to 25.
A computer-readable storage medium, characterized in that it is used to store a computer program, the computer program causes the computer to perform the method according to any one of claims 12 to 16, or any one of claims 20 to 25 method described in the item.
A computer program product, characterized in that it includes computer program instructions, the computer program instructions cause the computer to perform the method as described in any one of claims 12 to 16, or as described in any one of claims 20 to 25 Methods.
A computer program, characterized in that the computer program causes a computer to execute the method according to any one of claims 12-16, or the method according to any one of claims 20-25.