Terminal device implemented method and terminal device

Abstract

To provide a method, a device, and a computer-readable medium for reporting failed conditional handover (CHO) attempts.SOLUTION: A method of implementing a new failure reporting mechanism includes obtaining configuration information regarding a candidate cell for conditional handover of a terminal device, initiating at least one conditional handover attempt to at least one candidate cell, storing failure information of the at least one conditional handover attempt in response to failure of at least one conditional handover attempt to the at least one candidate cell in a conditional handover procedure.SELECTED DRAWING: Figure 3

Description

[Technical field]

[0001] FIELD OF THE DISCLOSURE Embodiments of the present disclosure relate generally to the field of communications, and more specifically to a communications method, device, and computer-readable medium for reporting failed conditional handover (CHO) attempts. [Background technology]

[0002] As is well known, a terminal device can be handed over from a source cell to a target cell if the handover (HO) procedure is successful. However, handover failures occur mainly due to failures in sending handover commands. In order to improve the reliability of handover, it has been agreed to apply conditional handover (CHO) in Rel-16 LTE and NR.

[0003] If the channel between the source network device (gNB or eNB) and the terminal device is still in a good state, the source network device can send a CHO configuration associated with multiple CHO candidate cells to the terminal device. The CHO configuration includes a configuration of the CHO candidate cell and a CHO execution condition. If there is a CHO candidate cell that satisfies the CHO execution condition, for example, if the channel state between the target cell (CHO candidate cell) and the terminal device has a better offset than the channel state between the serving cell and the terminal device, the terminal device can autonomously connect to the target cell. In this case, the source network device does not need to send a message to instruct the start of CHO execution. Summary of the Invention [Problem to be solved by the invention]

[0004] In general, the exemplary embodiments of the present disclosure provide a method, device, and computer-readable medium for reporting failed conditional handover (CHO) attempts. [Means for solving the problem]

[0005] In a first aspect, a method is provided for implementation in a terminal device, the method comprising: obtaining configuration information related to candidate cells for a conditional handover of the terminal device; initiating at least one conditional handover attempt to at least one candidate cell; and storing failure information of the at least one conditional handover attempt in response to a failure of the at least one conditional handover attempt to the at least one candidate cell in a conditional handover procedure.

[0006] In a second aspect, a method is provided for implementation in a terminal device, the method comprising: obtaining configuration information related to candidate cells for a conditional handover of the terminal device; initiating at least one conditional handover attempt to at least one candidate cell; and ignoring a failure of the at least one conditional handover attempt in response to a failure of the at least one conditional handover attempt to the at least one candidate cell in a conditional handover procedure.

[0007] In a third aspect, there is provided a terminal device comprising a processor and a memory coupled to the processor unit and having instructions stored thereon, the instructions, when executed by the processor unit, causing the terminal device to perform operations according to the first aspect.

[0008] In a fourth aspect, there is provided a terminal device comprising a processor and a memory coupled to the processor unit and having instructions stored thereon, the instructions, when executed by the processor unit, causing the terminal device to perform operations according to the second aspect.

[0009] In a fifth aspect, there is provided a computer readable medium having stored thereon instructions which, when executed on at least one processor, cause the at least one processor to perform a method according to the first aspect.

[0010] In a sixth aspect, there is provided a computer readable medium having stored thereon instructions which, when executed on at least one processor, cause the at least one processor to perform a method according to the second aspect.

[0011] Other features of the present disclosure will become readily apparent from the following description. [Brief description of the drawings]

[0012] Hereinafter, several embodiments of the present disclosure will be described in more detail in the drawings, so that the above and other objects, features, and advantages of the present disclosure will become more apparent.

[0013] [Figure 1] FIG. 1 illustrates a schematic diagram of a communication environment in which some embodiments of the present disclosure may be implemented.

[0014] [Diagram 2] 2 illustrates a schematic diagram of a process 200 for reporting a failed conditional handover (CHO) attempt, according to an exemplary embodiment of the present disclosure.

[0015] [Diagram 3] 3 shows a flowchart of an example method 300 according to some embodiments of the present disclosure.

[0016] [Figure 4] 4 shows a flowchart of an example method 400 according to some embodiments of the present disclosure.

[0017] [Diagram 5] 5 shows a flowchart of an example method 500 according to some embodiments of the present disclosure.

[0018] [Figure 6] FIG. 1 is a schematic block diagram of a device suitable for implementing embodiments of the present disclosure.

[0019] In all figures, the same or similar drawing numbers represent the same or similar elements. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0020] The principles of the present disclosure will be described below with reference to some exemplary embodiments. It should be understood that these embodiments are merely described for illustrative purposes, to assist those skilled in the art in understanding and implementing the present disclosure, and do not imply any limitations on the scope of the present disclosure. The present disclosure described herein can be implemented in various ways other than those described below.

[0021] In the following description and claims, unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure belongs.

[0022] The term "network device" or "base station" (BS) as used herein refers to a device capable of providing or hosting a cell or coverage over which terminal devices can communicate. Examples of network devices include, but are not limited to, Node B (NodeB or NB), evolved Node B (eNodeB or eNB), next generation Node B (gNB), remote radio unit (RRU), radio head (RH), remote radio head (RRH), low power nodes such as femto nodes, pico nodes, etc. For discussion purposes, some embodiments are described below with reference to a gNB as an example of a network device.

[0023] The term "terminal device" as used herein refers to any device that has wireless or wired communication capabilities. Examples of terminal devices include, but are not limited to, user equipment (UE), personal computers, desktop computers, mobile phones, cell phones, smart phones, personal digital assistants (PDAs), handheld computers, image capture devices such as digital cameras, gaming devices, music storage and playback devices, or Internet devices capable of wirelessly or wired access to and browsing the Internet.

[0024] When used in the text, the singular forms "a", "an" and "the" are meant to include the plural forms unless the context clearly indicates otherwise. The term "comprises" and variations thereof should be understood as open-ended terms meaning "including, but not limited to." The term "based on" should be understood as "based at least in part on." The terms "embodiment" and "one embodiment" should be understood as "at least one embodiment." The term "other embodiments" should be understood as "at least one other embodiment." The terms "first," "second," etc. can refer to different or the same object. Other explicit and implicit definitions may be included in the text below.

[0025] In some instances, values, processes or devices are referred to as "optimum," "lowest," "highest," "minimum," "maximum," etc. It should be understood that such descriptions are intended to indicate choices that may be made among multiple functional alternatives that are used, and that such choices are not necessarily better, lesser, higher, or more preferred than other choices.

[0026] FIG. 1 illustrates an exemplary communication network 100 in which embodiments of the present disclosure may be implemented. The network 100 includes a terminal device 110 and network devices 120-1 through 120-4 (collectively referred to as network devices 120). For example, the terminal device 110 may be served by the network device 120-1. The serving area of ​​the network device 120-1 may be referred to as a cell 101. It should be understood that the number of network devices and terminal devices is for illustrative purposes only and does not imply any limitation. The network 100 may include any suitable number of network devices and terminal devices suitable for implementing embodiments of the present disclosure. Although not illustrated, it should be understood that one or more terminal devices may be located within the cell 101 and may be served by the network device 120-1.

[0027] In the communication network 100, the network devices 120 can send data and control information to the terminal devices 110, and the terminal devices 110 can also send data and control information to the network devices 120. The link from the network devices 120 to the terminal devices 110 is referred to as the downlink (DL) or forward link, while the link from the terminal devices 110 to the network devices 120 is referred to as the uplink (UL) or reverse link.

[0028] In one embodiment, the terminal device can be connected to a first network device and a second network device. Of the first network device and the second network device, one can be a master node and the other can be a secondary node. The first network device and the second network device can use different radio access technologies (RATs). In one embodiment, the first network device can be a first RAT device and the second network device can be a second RAT device. In one embodiment, the first RAT device is an eNB and the second RAT device is a gNB. Information related to the different RATs can be transmitted to the terminal device from at least one of the first network device and the second network device. In one embodiment, the first information can be transmitted to the terminal device from the first network device, and the second information can be transmitted from the second network device directly or via the first network device. In one embodiment, information related to a configuration of the terminal device configured by the second network device can be transmitted from the second network device via the first network device. Also, information related to a reconfiguration of the terminal device configured by the second network device can be transmitted to the terminal device from the second network device directly or via the first network device.

[0029] Depending on the communication technology, the network 100 may be a code division multiple access (CDMA) network, a time division multiple access (TDMA) network, a frequency division multiple access (FDMA) network, an orthogonal frequency division multiple access (OFDMA) network, a single carrier frequency division multiple access (SC-FDMA) network, or any other network. The communications discussed with respect to the network 100 may conform to any suitable standard, including, but not limited to, New Radio Access (NR), Long Term Evolution (LTE), LTE Evolution, LTE-Advanced (LTE-A), Wideband Code Division Multiple Access (WCDMA), Code Division Multiple Access (CDMA), cdma2000, Global System for Mobile Communications (GSM), and the like. Additionally, communications may be performed according to any generation of communication protocols now known or developed in the future. Examples of communication protocols include, but are not limited to, first generation (1G), second generation (2G), 2.5G, 2.75G, third generation (3G), fourth generation (4G), 4.5G, and fifth generation (5G) communication protocols. The techniques described herein may be used in the wireless networks and radio technologies mentioned above as well as other wireless networks and radio technologies. For clarity, some aspects of these technologies are described below with respect to LTE, and LTE technical terminology is used in most of the following description.

[0030] In the communication network 100, when the channel condition between the terminal device 110 and the network device 120-1 deteriorates, the network device 120-1 may initiate a handover (HO) procedure and notify the terminal device 110 of a handover from its serving cell to a target cell. During the handover procedure, the terminal device 110 may attempt to access the target cell. If the handover procedure is successfully executed, the terminal device 110 may be served from another serving area, for example, from the serving cell 102 of the network device 120-2.

[0031] However, if the terminal device 110 does not receive a response from the network device 120-2 indicating that the access attempt was successful before the timer of the handover procedure expires, the access attempt fails. Failure information of this failed access attempt (which may be referred to as a handover failure (HOF)) may be recorded in the terminal device 110.

[0032] In addition, if a connection between the terminal device 110 and its serving network device 120-1 fails, failure information of the failed connection (which may be referred to as a radio link failure (RLF)) may also be recorded in the terminal device 110.

[0033] The terminal device 110 may indicate the availability of the RLF report information in subsequent (re)establishment of an RRC connection and handover to the target cell. If the upper device requires an RLF report, the newly connected network device (e.g., network device 120-2) may send a UEInformationRequest message to request feedback of the RLF report information to the terminal device 110. The terminal device 110 responds with a UEInformationResponse message.

[0034] The recorded failure information can be introduced into the RLF report variable. According to the current failure recording mechanism, the terminal device 110 can only store the information of the latest radio link failure or handover failure. Before setting the information field, the terminal device 110 always clears the information contained in the current RLF report variable.

[0035] As mentioned above, conditional handover (CHO) has been proposed to improve the reliability of handover. In the conditional handover procedure, when the channel between the network device 120-1 and the terminal device 110 is still in a good state, the network device 120-1 can send a CHO configuration associated with multiple CHO candidate cells (e.g., cells 102-104 shown in FIG. 1) to the terminal. The CHO configuration includes the configuration of the CHO candidate cells and a CHO execution condition.

[0036] Optionally, when any CHO candidate cell satisfies the CHO execution condition, the terminal device 110 can perform an autonomous access attempt to the CHO candidate cell, and the network device 120-1 does not need to send a message to instruct the start of CHO execution. Since a set of candidate cells can be provided to the terminal device 110 to perform a conditional handover procedure, multiple access attempts may be performed before the handover is successful.

[0037] As another option, if an RLF or CHO has already occurred, the terminal device 110 may initiate a CHO procedure even if the CHO candidate cell does not meet the CHO execution condition.

[0038] According to the failure recording mechanism as described above, the previous failure information may always be deleted before new failure information is recorded. In this case, the RLF report may not reflect the state of the entire network. For example, the RLF and HOF information recorded before CHO may be deleted when recording the CHO failure information. Also, if all CHO attempts for multiple CHO candidate cells fail, the terminal device 110 can only submit the RLF report related to the last CHO execution. Furthermore, how to indicate handover failure in the CHO procedure has not yet been fully discussed.

[0039] For this reason, this disclosure discusses a method for reporting failed conditional handover (CHO) attempts.

[0040] Hereinafter, the principles and exemplary embodiments will be described in detail with reference to the drawings. However, those skilled in the art will easily understand that the present disclosure goes beyond these limited embodiments, and therefore the contents described in detail with reference to the drawings herein are for the purpose of explanation.

[0041] 2 illustrates a schematic diagram of a process 200 for reporting a failed CHO attempt, according to an exemplary embodiment of the present disclosure. For purposes of discussion, the process 200 will be described with reference to FIG 1. The process 200 may involve the terminal device 110 and the network devices 120-1 to 120-4 shown in FIG 1.

[0042] As shown in FIG. 2, the terminal device 110 obtains configuration information regarding candidate cells for CHO from the network device 120-1 (205). When the channel between the network device 120-1 and the terminal device 110 is still in a good state, the configuration information can be sent from the network device 120-1. The configuration information can include a cell ID of each candidate cell and other related configurations for CHO. For example, the candidate cells can refer to the cells 102-104 shown in FIG. 1.

[0043] If a condition for triggering CHO is reached, for example, the channel conditions between network devices 120-2 to 120-4 and terminal device 110 are offset better than the channel conditions between network device 120-1 and terminal device 110, terminal device 110 may initiate a conditional handover (210). Terminal device 110 may perform at least one conditional handover attempt to a candidate cell.

[0044] In a first conditional handover attempt, the terminal device 110 may, for example, transmit an access request to one of the candidate cells (e.g., cell 102 of network device 120-2) (215). If a timer for the conditional handover attempt expires and no response is received from network device 120-2, the handover attempt may be considered a failed attempt. If the handover attempt to cell 102 fails, the terminal device 110 stores failure information of the failed conditional handover attempt (220).

[0045] In some example embodiments, the terminal device 110 may determine whether the failure of the first handover attempt to the cell 102 in the CHO procedure is the first connection failure after the terminal device 110 connects with the current serving cell (i.e., the cell 102) (in this situation, the connection between the terminal device 110 and the network device does not fail). If the failure of the first handover attempt to the cell 102 is the first connection failure, the terminal device 110 may delete previously stored failure information. For example, it may delete history of failure information related to other cells other than the cells 101-104.

[0046] As another option, the terminal device 110 may determine whether the handover attempt to the cell 102 is triggered by an RLF or a HOF. If the terminal device 110 determines that the handover attempt to the cell 102 is triggered by an RLF or a HOF, the terminal device 110 may ignore the failure information.

[0047] In some exemplary embodiments, terminal device 110 may perform a further conditional handover attempt. For example, terminal device 110 may send an access request to one of the candidate cells (e.g., cell 103 of network device 120-3) (225). Similarly, if a timer for the conditional handover attempt expires and no response is received from network device 120-3, the handover attempt may be considered a failed attempt.

[0048] If the handover attempt to the cell 103 fails, failure information of this failed conditional handover attempt may also be stored in the terminal device 110. As described above, the failure information of the first conditional handover attempt has already been stored.

[0049] In some demonstrative embodiments, terminal device 110 may store (230) both failure information of the first conditional handover attempt to cell 102 and failure information of the second conditional handover attempt to cell 103 based on the starting time points of the first conditional handover attempt and the second conditional handover attempt.

[0050] In some exemplary embodiments, if the first conditional handover attempt to cell 102 is the first conditional handover attempt in a conditional handover procedure, terminal device 110 may store only failure information of the first conditional handover attempt.

[0051] In some exemplary embodiments, if the second conditional handover attempt to cell 103 is the last conditional handover attempt in the conditional handover procedure, terminal device 110 may store only failure information of the second conditional handover attempt.

[0052] In some exemplary embodiments, terminal device 110 may store a predetermined number of failed conditional handover attempts.

[0053] For example, if the predetermined number is 2 and the terminal device 110 can store the earliest failure, then only the failure information of the first conditional handover attempt and the failure information of the second conditional handover attempt can be stored, i.e., other failed conditional handover attempts occurring after the first conditional handover attempt and the second conditional handover attempt will not be stored.

[0054] As another option, if the predetermined number is 2 and the terminal device is able to store the most recent failures, and if the first conditional handover attempt failure information and the second conditional handover attempt failure information have already been stored, when storing the further failure information, the terminal device 110 may determine whether the sum of the failure number of the previously stored failure information and the failure number of the further failure information exceeds a threshold number, and if the sum exceeds the threshold number, some of the previously stored failure information may be deleted so that further conditional handover attempt failure information can be stored.

[0055] Before at least one conditional handover attempt initiated by the terminal device 110, some previous failure information may already be stored in the terminal device 110. Such previous failure information may be referred to as an RLF, a HOF, or another CHO failure. An RLF may indicate that a connection between the terminal device 110 and the network device 120-1 has failed, and an HOF may indicate that the terminal device has attempted to access a dedicated cell before the CHO but the access attempt has failed.

[0056] Optionally, failure information of at least one conditional handover attempt may be stored without deleting previous failure information.

[0057] As a further option, if the terminal device 110 stores a predetermined number of failed conditional handover attempts, the terminal device 110 may determine whether the sum of the failure count associated with the previous failure information and the failure count associated with the failure information exceeds a threshold number of failure events that are allowed to be stored. If the terminal device 110 determines that the sum does not exceed the threshold number, the terminal device 110 may store the failure information without deleting the previous failure information.

[0058] If the terminal device 110 determines that the sum exceeds a threshold number of times, the terminal device 110 may delete some of the previous failure information so that failure information can be stored.

[0059] 2, terminal device 110 may further transmit (235) an access request to another cell 104 of network device 120-4 in a conditional handover procedure. If terminal device 110 receives (240) a response from the network device indicating that access is acceptable, terminal device 110 may determine (245) that the conditional handover attempt to cell 104 is successful.

[0060] As another option, the handover attempt to the cell 104 may fail, but the terminal device 110 may successfully access an available cell, i.e., re-establish a connection between the terminal device 110 and the network.

[0061] Both cell 104 and the available cell may be referred to as target cells in the following text.

[0062] The terminal device 110 may transmit (250) a message to the target cell indicating that information of at least one connection failure that occurred at the terminal device is available.

[0063] For example, the message may include at least one of the following: a failure type of the at least one connection failure (i.e., one of RLF, HOF, and CHOF), a number of the at least one connection failure, and information of a successful handover attempt to the target cell. In some embodiments, the failure report may further indicate a number of failures that occurred in the CHO procedure. An example of the information about the at least one connection failure (i.e., the RLF variables of the terminal device) may be represented in the following table: Table 1: RLF variables TIFF0007616326000001.tif229155

[0064] If the terminal device 110 receives 255 a request for information regarding at least one connection failure, the terminal device 110 may generate 260 a failure report. The failure report may include at least one of previous failure information, failure information, and information regarding a successful handover attempt to a target cell.

[0065] In some embodiments, the information regarding a successful handover attempt to the target cell may include one or more of the following parameters: an identifier of the target cell, a timestamp of an access to the target cell, a location of the target cell, channel conditions of the target cell, and channel conditions of at least one neighboring cell of the target cell.

[0066] In some embodiments, the failure report may indicate the types of failures that occurred at the terminal device and the failure information for each type. An example of a failure report may be represented in the following table: Table 2: Failure reports TIFF0007616326000002.tif51165TIFF0007616326000003.tif235164TIFF0007616326000004.tif237164TIFF0007616326000005.tif56165

[0067] The terminal device 110 may then transmit a failure report to the target cell.

[0068] In some embodiments, any failures that occur in the CHO procedure are not stored in the terminal device 110. In other words, failures related to the CHO procedure are ignored.

[0069] In some embodiments, the terminal device 110 may determine whether a radio link failure or a legacy handover failure occurred prior to the at least one conditional handover attempt. If the terminal device 110 determines that a radio link failure or a legacy handover failure occurred prior to the at least one conditional handover attempt, the terminal device 110 may ignore failures in the CHO procedure.

[0070] In this way, a new mechanism for failure reporting can be realized.

[0071] Exemplary embodiments of the present disclosure will now be described in greater detail with reference to FIGS.

[0072] 3 illustrates a flowchart of an example method 300 according to some embodiments of the present disclosure. The method 300 may be implemented in a terminal device 110, as shown in FIG 1. For ease of discussion, the method 300 will be described with reference to FIG 1.

[0073] At 310, the terminal device 110 obtains configuration information regarding at least one candidate cell for conditional handover of the terminal device.

[0074] At 320, the terminal device 110 initiates at least one conditional handover attempt to the at least one candidate cell.

[0075] At 330, if at least one conditional handover attempt to the at least one candidate cell in a conditional handover procedure fails, the terminal device 110 stores, at 340, failure information of the at least one conditional handover attempt.

[0076] At 330, if at least one conditional handover attempt to the at least one candidate cell in a conditional handover procedure fails, the operation of the terminal device may be described as follows with reference to FIG.

[0077] 4 illustrates a flowchart of an example method 400 according to some embodiments of the present disclosure. The method 400 may be implemented, for example, in the terminal device 110 illustrated in FIG 1. For ease of discussion, the method 400 will be described with reference to FIG 1.

[0078] At 410, the terminal device 110 transmits a message to a target cell indicating that information of at least one connection failure occurring at the terminal device is available, where the target cell may include at least one candidate cell or one available cell among available cells other than the at least one candidate cell.

[0079] At 420, when the terminal device 110 receives a request for information from the target cell, the terminal device 110 generates 430 a failure report including at least one of previous failure information, failure information, and information regarding successful conditional handover attempts.

[0080] At 440, the terminal device 110 transmits a failure report to the target cell.

[0081] 5 illustrates a flowchart of an example method 500 according to some embodiments of the present disclosure. The method 500 may be implemented, for example, in the terminal device 110 illustrated in FIG 1. For ease of discussion, the method 500 will be described with reference to FIG 1.

[0082] At 510, the terminal device 110 obtains configuration information regarding at least one candidate cell for conditional handover of the terminal device.

[0083] At 520, the terminal device 110 initiates at least one conditional handover attempt to the at least one candidate cell.

[0084] If at least one conditional handover attempt to the at least one candidate cell in a conditional handover procedure fails at 530, the terminal device 110 ignores the failure of the at least one conditional handover attempt at 540.

[0085] 6 is a schematic block diagram of a device 600 suitable for implementing an embodiment of the present disclosure. The device 600 can be considered as a further exemplary embodiment of the terminal device 110 shown in FIG. 1. Thus, the device 600 can be implemented in the terminal device 110 or as at least a part of the terminal device 110.

[0086] As shown in FIG. 6, the device 600 comprises a processor 610, a memory 620 coupled to the processor 610, a suitable transmitter (TX) and receiver (RX) 640 coupled to the processor 610, and a communication interface coupled to the TX / RX 640. The memory 620 stores at least a portion of a program 630. The TX / RX 640 is used for bidirectional communication. The TX / RX 640 has at least one antenna for communication, and in practice, the access nodes described herein may have multiple antennas. The communication interface may represent any interface required for communication with other network members, such as an X2 interface for bidirectional communication between eNBs, an S1 interface for communication between a mobility management entity (MME) / serving gateway (S-GW) and an eNB, an Un interface for communication between an eNB and a relay node (RN), or an Uu interface for communication between an eNB and a terminal device.

[0087] Assuming that the program 630 includes program instructions that, when executed by an associated processor 610, cause the device 600 to operate according to the embodiments of the present disclosure described herein with reference to FIGS. 2-5. The embodiments of the present disclosure may be implemented by computer software executable by the processor 610 of the device 600, by hardware, or by a combination of software and hardware. The processor 610 may be configured to implement embodiments of the present disclosure. Additionally, the combination of the processor 610 and the memory 620 may constitute a processing member 650 suitable for implementing embodiments of the present disclosure.

[0088] The memory 620 may be of any type suitable for a local technology network and may be implemented by any suitable data storage technology, including, but not limited to, computer-readable non-transitory storage media, semiconductor-based storage devices, magnetic storage devices and systems, optical storage devices and systems, fixed and removable memories, etc. Although only one memory 620 is shown in the device 600, multiple physically distinct memory modules may be installed in the device 600. By way of example, the processor 610 may be of any type suitable for a local technology network and may include, but is not limited to, one or more of a general purpose computer, a special purpose computer, a microprocessor, a digital signal processor (DSP), and a processor based on a multi-core processor configuration. The device 600 may have multiple processors, for example application specific integrated circuit chips time-slaved to a clock that synchronizes a master processor.

[0089] Typically, embodiments of the present disclosure can be implemented in hardware or dedicated circuits, software, logic, or any combination thereof. Some aspects can be implemented by hardware, and other aspects can be implemented by firmware or software executed by a controller, microprocessor, or other computing device. Although aspects of the embodiments of the present disclosure are shown and described as block diagrams, flow charts, or illustrated by some other graphic representations, it should be understood that the blocks, apparatus, systems, techniques, or methods described herein can be implemented in, for example, but not limited to, hardware, software, firmware, dedicated circuits or logic, general-purpose hardware or controller or other computing device, or combinations thereof.

[0090] The present disclosure further provides at least one computer program product tangibly stored in a computer-readable non-transitory storage medium. The computer program product includes computer-executable instructions. The computer-executable instructions execute on a target real or virtual processor device, for example, included in a program module to perform the process or method described above with reference to FIG. 2. Generally, a program module includes routines, programs, libraries, objects, classes, components, data structures, etc. that perform particular tasks or implement particular abstract data types. The functionality of the program modules may be combined or split between program modules as desired for each embodiment. The machine-executable instructions of the program modules may be executed in a local device or a distributed device. In a distributed device, the program modules may be located in both local and remote storage media.

[0091] The program codes for carrying out the methods of the present disclosure can be written in any combination of one or more programming languages. These program codes can be provided to a processor or controller of a general purpose computer, a special purpose computer or other programmable data processing apparatus, and when executed by the processor or controller, the program codes can implement the functions / operations specified in the flowcharts and / or block diagrams. The program codes can be executed entirely on the machine, partially on the machine, as a separate software package, partially on the machine and partially on a remote machine, or entirely on a remote machine or server.

[0092] The above-mentioned program code may be embodied on a machine-readable medium, which may be any tangible medium that contains or stores a program for use by or in conjunction with an instruction execution system, apparatus, or device. The machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. The machine-readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of machine-readable storage media include one or more electrical connections of cables, a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable-programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

[0093] Although operations have been described in a particular order, it should not be understood that the operations must be performed in the particular order or sequence shown, or that all of the operations shown must be performed, to achieve desired results. In some situations, multiple tasks and parallel processing may be advantageous. Similarly, the above discussion includes some specific implementation details, but these should not be construed as limitations on the scope of the disclosure, but rather as descriptions of features of particular embodiments. Some features described in the context of individual embodiments may be implemented in combination in an implementation. Conversely, various features described in the context of an embodiment may be implemented in multiple embodiments alone or in any suitable subcombination.

[0094] Although the present disclosure has been described in terms of structural features and / or method and operation language, it is to be understood that the present disclosure as defined by the appended claims is not necessarily limited to the specific features or operations described above. Rather, the specific features and operations are disclosed as example forms of implementing the claims.

Claims

1. Receiving a conditional handover (CHO) configuration; in response to a first failure and a second failure, storing failure-related information of two successive failures including the first failure and the second failure in a radio link failure (RLF) report; where The first failure is an RLF in a source cell and the second failure is a failure to select a configured candidate CHO cell and to connect to the configured candidate CHO cell; or The first failure is a handover (HO) failure in performing a CHO to a first candidate CHO cell set by satisfying a set condition, and the second failure is a failure in selecting a second candidate CHO cell set and connecting to the second candidate CHO cell set, or The first failure is an HO failure occurring when performing HO to a target cell, and the second failure is a failure to select a configured candidate CHO cell and to connect to the configured candidate CHO cell. The method is implemented on a terminal device.

2. Further comprising: in response to a successful CHO, sending a message including information of the successful CHO. The method of claim 1.

3. The successful CHO information includes at least one of an identity or location information of the target cell. The method of claim 2.

4. A method for receiving a conditional handover (CHO) configuration, comprising: means for storing, in response to a first failure and a second failure, failure-related information of two successive failures including the first failure and the second failure in a Radio Link Failure (RLF) report; wherein: The first failure is an RLF in a source cell and the second failure is a failure to select a configured candidate CHO cell and to connect to the configured candidate CHO cell; or The first failure is a handover (HO) failure in performing a CHO to a first candidate CHO cell set by satisfying a set condition, and the second failure is a failure in selecting a second candidate CHO cell set and connecting to the second candidate CHO cell set, or The first failure is an HO failure occurring when performing HO to a target cell, and the second failure is a failure to select a configured candidate CHO cell and to connect to the configured candidate CHO cell. Terminal device.

5. Further comprising: means for transmitting a message in response to a successful CHO, the message including information of the successful CHO. A terminal device according to claim 4.

6. The successful CHO information includes at least one of an identity or location information of the target cell. A terminal device according to claim 5.

Images