WO2021056403A1 - 链路失败的信息处理方法和电子设备 - Google Patents

链路失败的信息处理方法和电子设备 Download PDF

Info

Publication number
WO2021056403A1
WO2021056403A1 PCT/CN2019/108478 CN2019108478W WO2021056403A1 WO 2021056403 A1 WO2021056403 A1 WO 2021056403A1 CN 2019108478 W CN2019108478 W CN 2019108478W WO 2021056403 A1 WO2021056403 A1 WO 2021056403A1
Authority
WO
WIPO (PCT)
Prior art keywords
link failure
condition
information
stored
failure information
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/CN2019/108478
Other languages
English (en)
French (fr)
Inventor
杨星
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Beijing Xiaomi Mobile Software Co Ltd
Original Assignee
Beijing Xiaomi Mobile Software Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Beijing Xiaomi Mobile Software Co Ltd filed Critical Beijing Xiaomi Mobile Software Co Ltd
Priority to CN201980002156.4A priority Critical patent/CN110915259B/zh
Priority to CN202210557016.7A priority patent/CN115002856B/zh
Priority to PCT/CN2019/108478 priority patent/WO2021056403A1/zh
Priority to US17/763,589 priority patent/US12127055B2/en
Priority to EP19946919.8A priority patent/EP4037425A4/en
Publication of WO2021056403A1 publication Critical patent/WO2021056403A1/zh
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0055—Transmission or use of information for re-establishing the radio link
    • H04W36/0079—Transmission or use of information for re-establishing the radio link in case of hand-off failure or rejection
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0083—Determination of parameters used for hand-off, e.g. generation or modification of neighbour cell lists
    • H04W36/0085—Hand-off measurements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/24—Reselection being triggered by specific parameters
    • H04W36/30—Reselection being triggered by specific parameters by measured or perceived connection quality data
    • H04W36/305—Handover due to radio link failure
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/18—Management of setup rejection or failure
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0083—Determination of parameters used for hand-off, e.g. generation or modification of neighbour cell lists
    • H04W36/00838—Resource reservation for handover
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/34—Reselection control
    • H04W36/36—Reselection control by user or terminal equipment
    • H04W36/362—Conditional handover
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/19—Connection re-establishment

Definitions

  • the present disclosure relates to the field of communication technology, and in particular, to an information processing method and electronic equipment for link failure.
  • the user equipment can switch the cell, that is, switch the cell in which it is located.
  • the conventional handover operation can be performed by the user equipment to measure the cell, and then report the measurement result to the base station, and the base station will hand over to the user equipment according to the measurement result.
  • the target cell sends a handover request. If the target cell confirms that the user equipment is allowed to switch, the base station can send a handover command to the user equipment.
  • the handover command carries configuration information about the handover, and the user equipment can switch to the target cell according to the configuration information.
  • Conditional HandOver (CHO for short) is proposed. Users do not need to report measurement results to the base station, and the base station sends a preamble to the user equipment in advance. Set the conditions and the target cell that can be handed over. When the network environment where the user equipment is located meets the preset conditions, the user equipment can be handed over to the target cell.
  • link failure will occur if the handover fails.
  • the user equipment sends the link failure, it can store the link failure information and report it to the base station so that the base station Determine the information of the network environment where the user equipment is located when the link fails, so that the base station can optimize the network.
  • the user equipment only stores the information about the latest link failure, that is, when a new link failure occurs, the stored link failure information will be deleted, and the information about the newly occurred link failure will be stored. .
  • the embodiments of the present disclosure propose a link failure information processing method, a link failure information processing device, and electronic equipment to solve technical problems in the related art.
  • a method for processing link failure information is proposed, which is applicable to a terminal, and the method includes:
  • condition-based switch fails, determine the trigger condition of the condition-based switch
  • the trigger condition it is determined whether to delete the stored link failure information.
  • a method for processing link failure information is proposed, which is applicable to a terminal, and the device includes:
  • the condition determination module is configured to determine the trigger condition of the condition-based switching after the condition-based switching fails
  • the storage determining module is configured to determine whether to delete the stored link failure information according to the trigger condition.
  • an electronic device including:
  • a memory for storing processor executable instructions
  • processor is configured to implement the method described in any of the foregoing embodiments.
  • the base station determines whether to delete the stored failure information according to the failed condition-based switching trigger condition, so as to ensure that the stored link failure information is sent to the base station, and the base station can clearly cause the user equipment link
  • the failed network environment is conducive to the optimization of the network by the base station.
  • Fig. 1 is a schematic flowchart showing a method for processing link failure information according to an embodiment of the present disclosure.
  • Fig. 2 is a schematic flowchart of another method for processing link failure information according to an embodiment of the present disclosure.
  • Fig. 3 is a schematic flowchart showing another method for processing link failure information according to an embodiment of the present disclosure.
  • Fig. 4 is a schematic flowchart showing yet another method for processing link failure information according to an embodiment of the present disclosure.
  • Fig. 5 is a schematic flowchart showing yet another method for processing link failure information according to an embodiment of the present disclosure.
  • Fig. 6 is a schematic flowchart showing yet another method for processing link failure information according to an embodiment of the present disclosure.
  • Fig. 7 is a schematic flowchart showing yet another method for processing link failure information according to an embodiment of the present disclosure.
  • Fig. 8 is a schematic flowchart showing yet another method for processing link failure information according to an embodiment of the present disclosure.
  • Fig. 9 is a schematic flowchart showing yet another method for processing link failure information according to an embodiment of the present disclosure.
  • Fig. 10 is a schematic block diagram showing an information processing device with a link failure according to an embodiment of the present disclosure.
  • Fig. 11 is a schematic block diagram showing another information processing device with a link failure according to an embodiment of the present disclosure.
  • Fig. 12 is a schematic block diagram showing yet another information processing device with a link failure according to an embodiment of the present disclosure.
  • Fig. 13 is a schematic block diagram showing an apparatus for processing link failure information according to an embodiment of the present disclosure.
  • link failures will occur when they fail.
  • RLF Radio Link Failure
  • the user equipment can perform cell selection. If the selected cell happens to be the target cell specified by the conditional handover, then the user equipment selecting the target cell for access is equivalent to performing the conditional handover again. When the user equipment fails the conditional switching again in the above manner, it will also be determined that a link failure has occurred, and then the stored link failure information will be deleted according to the method of storing the link failure information in the related technology.
  • the action that triggers the link failure again is based on the conditional switch failure.
  • the triggering conditions for the conditional switch are not the same. If the condition-based switch fails under all trigger conditions, the stored link failure information will be deleted, which may lead to The base station cannot fully understand the network status of the terminal based on the information of the link failure, which is not conducive to the optimization of the network by the base station.
  • Fig. 1 is a schematic flowchart showing a method for processing link failure information according to an embodiment of the present disclosure.
  • the method shown in this embodiment can be applied to terminals, which include but are not limited to electronic devices such as mobile phones, tablet computers, and wearable devices.
  • the terminals can be used as user equipment (the following embodiments are mainly used in the case where the terminal is used as the user equipment).
  • Communication with the base station for example, can communicate with the base station based on 4G LTE technology, or communicate with the base station based on 5G NR technology.
  • the method for processing link failure information may include the following steps:
  • step S1 after the condition-based switching fails, the triggering condition of the condition-based switching is determined
  • step S2 it is determined whether to delete the stored link failure information according to the trigger condition.
  • the link failure information includes but is not limited to the cell where the user equipment (that is, the terminal) is located when the link fails, the measurement data of the cell where the user equipment is located, and the location information of the user equipment, The C-RNTI (Cell-Radio Network Temporary Identifier) used by the user equipment before the link failure, the reason for the link failure (such as radio link failure, handover failure, handover failure based on conditions), etc., and
  • the link failure information may also include the target cell for conditional handover indicated by the base station for the user equipment.
  • the user equipment After the user equipment establishes a connection with the base station (including connection establishment, connection reestablishment, connection recovery, etc.), it can report the link failure information to the base station, and the base station can report the link failure information to the base station according to the received link
  • the failure information can determine the network environment when the user equipment link fails, so as to optimize the network in a targeted manner, so as to improve the communication effect of the user equipment.
  • the terminal when the terminal fails to switch based on conditions, although a link failure also occurs, the stored link failure information will not be deleted immediately, but the trigger condition of the failed condition based switch can be determined first .
  • the stored link failure information is the previous link failure Information.
  • the network environment where the user equipment is located does not frequently meet the preset conditions of condition-based switching, that is, the user equipment does not frequently switch based on the conditions, then the previous link fails, and the current time is based on the condition.
  • Handover fails usually a long time apart, and the network environment where the user equipment is located generally has undergone major changes.
  • the information of the previous link failure has a weak reference for the base station to optimize the network.
  • This link The failure information can make the base station know the network environment where the user equipment is located when the link fails this time, so the stored link information can be deleted, and the information about the link failure caused by the failure of the handover based on the conditions this time can be stored.
  • Condition-based handover is triggered when the network environment of the user equipment meets the preset conditions of condition-based handover. It can also be triggered after the link fails. Specifically, after the link fails, when the user equipment selects a cell, the selected cell happens to be Switching over the specified target cell based on the condition, then the user equipment selects the target cell to access, which is equivalent to performing the condition-based switch again.
  • the link failure may include wireless link failure, condition-based handover failure, handover failure (that is, the failure of the conventional handover operation in 4GLTE) and so on. That is, there are three main situations:
  • Case 1 After the radio link fails, the user equipment can perform condition-based handover during cell selection;
  • Case 2 After the condition-based handover fails, the user equipment can perform condition-based handover during cell selection. In this case, there are two condition-based handovers. In order to distinguish, the condition-based handover performed during cell selection is called the second The second switch based on conditions, the previous switch based on conditions is called the first switch based on conditions;
  • Case 3 After the handover fails, the user equipment can perform condition-based handover during cell selection.
  • condition-based handover is not triggered when the network environment of the user equipment meets the preset conditions, but is triggered by the wireless link failure, so the network environment that essentially causes the link failure is the wireless link failure
  • the network environment of the user equipment is not based on the network environment of the user equipment when the handover fails based on conditions.
  • the user equipment When the wireless link fails, the user equipment has determined that the link failure has occurred, and recorded the link failure information, including the link failure cause is the wireless link failure.
  • the user equipment When the user equipment’s network environment, that is, the network environment that is not essentially causing the link failure, sending the newly recorded link failure to the base station may cause the base station to be unable to accurately determine the network environment that caused the user equipment link failure. happensing.
  • the second condition-based handover is not triggered when the network environment of the user equipment meets the preset conditions, but is triggered by the failure of the first condition-based handover, which essentially causes the link failure in the network environment , Is the network environment of the user equipment when the handover fails based on the condition for the first time, not the network environment of the user equipment when the handover fails based on the condition for the second time.
  • the user equipment When the first handover based on conditions fails, the user equipment has determined that a link failure has occurred, and has recorded the link failure information, including the reason for the link failure as the failure of the handover based on the condition, if the second time based on the condition When the handover fails, the stored link failure information is deleted, and the new link failure information is recorded. Then the newly recorded link failure information corresponds to the network environment of the user equipment when the second conditional switch fails. Network environment, not the network environment of the user equipment when the handover fails based on the conditions for the first time, that is, the network environment that is not essentially causing the link failure, then sending the newly recorded link failure to the base station may cause the base station to be inaccurate To determine the conditions of the network environment that caused the link failure of the user equipment.
  • condition-based handover is not triggered when the network environment of the user equipment meets the preset conditions, but is triggered by the handover failure.
  • the network environment that essentially causes the link failure is the user equipment when the handover fails.
  • the network environment is not based on the network environment of the user equipment when the conditional handover fails.
  • the user equipment When the handover fails, the user equipment has determined that the link failure has occurred and recorded the link failure information, including the reason for the link failure as the handover failure. If the stored link is deleted when the handover fails based on the conditions Failed information, record the new link failure information, then the newly recorded link failure information corresponds to the network environment based on the network environment of the user equipment when the handover fails, not the network environment of the user equipment when the handover fails. , That is, it is not a network environment that essentially causes a link failure, so sending the newly recorded link failure to the base station may cause the base station to be unable to accurately determine the network environment that caused the link failure of the user equipment.
  • the trigger condition is that the network environment of the user equipment meets the preset condition of the condition-based switching, and the stored information can be deleted.
  • the stored link failure information can be retained to ensure that the stored link failure information is sent to the base station, and the base station can clearly cause the user The network environment where the equipment link fails is conducive to the optimization of the network by the base station.
  • the trigger condition includes one of the following:
  • the wireless link fails, the handover fails based on the condition, and the handover fails, and the network environment of the terminal meets the preset condition for the condition based handover.
  • Fig. 2 is a schematic flowchart of another method for processing link failure information according to an embodiment of the present disclosure.
  • the trigger condition is a wireless link failure
  • the determining whether to delete the stored link failure information according to the trigger condition includes:
  • step S201 the stored link failure information is retained.
  • the network environment that essentially causes the link failure is the wireless link
  • the user equipment When the wireless link fails, the user equipment has determined that the link failure has occurred, and recorded the link failure information, including the link failure cause is the wireless link failure.
  • the user equipment When the user equipment’s network environment, that is, the network environment that is not essentially causing the link failure, sending the newly recorded link failure to the base station may cause the base station to be unable to accurately determine the network environment that caused the user equipment link failure. happensing.
  • This embodiment retains the stored link failure information, that is, does not delete the stored link failure information, and then when reporting the link failure information to the base station, the stored link failure information (The information about the wireless link failure) is sent to the base station so that the base station can identify the network environment that caused the link failure of the user equipment, which is beneficial to the base station to optimize the network.
  • Fig. 3 is a schematic flowchart showing yet another method for processing link failure information according to an embodiment of the present disclosure.
  • the trigger condition is a radio link failure
  • the determining whether to delete the stored link failure information according to the trigger condition further includes:
  • step S202 the information about the link failure again is stored, where the information about the link failure again includes that the reason for the link failure again is the failure of the handover based on the condition after the wireless link fails.
  • the triggering condition is that the wireless link fails
  • it in addition to retaining the stored link failure information, it can also store the link failure information again, and indicate the link failure information in the link failure information again.
  • the reason for the failure is that the handover fails based on the conditions after the wireless link fails.
  • the stored link failure information and the newly stored link failure information can be reported to the base station, so that the base station can fully determine the specific circumstances of the two two-way failures. , Is conducive to the optimization of the network by the base station.
  • Fig. 4 is a schematic flowchart showing yet another method for processing link failure information according to an embodiment of the present disclosure.
  • the trigger condition is the failure of condition-based switching (the first condition-based switching) failure
  • the determining whether to delete the stored link failure information according to the trigger condition includes:
  • step S203 the stored link failure information is retained.
  • the second condition-based handover if the second condition-based handover is not triggered when the network environment of the user equipment meets the preset condition, but is triggered by the failure of the first condition-based handover, it essentially causes the link to fail.
  • the network environment is the network environment of the user equipment when the handover fails based on the conditions for the first time, rather than the network environment of the user equipment when the handover fails based on the conditions for the second time.
  • the user equipment When the first handover based on conditions fails, the user equipment has determined that a link failure has occurred, and has recorded the link failure information, including the reason for the link failure as the failure of the handover based on the condition, if the second time based on the condition When the handover fails, the stored link failure information is deleted, and the new link failure information is recorded. Then the newly recorded link failure information corresponds to the network environment of the user equipment when the second conditional switch fails. Network environment, not the network environment of the user equipment when the handover fails based on the conditions for the first time, that is, the network environment that is not essentially causing the link failure, then sending the newly recorded link failure to the base station may cause the base station to be inaccurate To accurately determine the network environment that caused the link failure of the user equipment
  • This embodiment retains the stored link failure information, that is, does not delete the stored link failure information, and then when reporting the link failure information to the base station, the stored link failure information ( The first time based on conditional handover failure information) is sent to the base station so that the base station can identify the network environment causing the link failure of the user equipment, which is beneficial to the base station to optimize the network.
  • Fig. 5 is a schematic flowchart showing yet another method for processing link failure information according to an embodiment of the present disclosure.
  • the trigger condition is a condition-based switching failure
  • the determining whether to delete the stored link failure information according to the trigger condition further includes:
  • step S204 the information about the link failure again is stored, where the information about the link failure again includes that the reason for the link failure again is that the switching based on the condition fails and the switching based on the condition fails again.
  • the link failure information when the triggering condition is a conditional switching failure, in addition to retaining the stored link failure information, the link failure information can also be stored, and the link failure information can be indicated in the link failure information again.
  • the reason for the failure is that the switch based on the condition fails and then the switch based on the condition fails again.
  • the stored link failure information and the newly stored link failure information when reporting link failure information to the base station, the stored link failure information and the newly stored link failure information can be reported to the base station, so that the base station can fully determine the specific circumstances of the two two-way failures. , Is conducive to the optimization of the network by the base station.
  • Fig. 6 is a schematic flowchart showing yet another method for processing link failure information according to an embodiment of the present disclosure.
  • the trigger condition is handover failure
  • the determining whether to delete the stored link failure information according to the trigger condition includes:
  • step S205 the stored link failure information is retained
  • condition-based handover is not triggered when the network environment of the user equipment meets the preset conditions, but is triggered by the handover failure, then the network environment that essentially causes the link failure is the user when the handover fails.
  • the network environment of the device not based on the network environment of the user device when the conditional handover fails.
  • the user equipment When the handover fails, the user equipment has determined that the link failure has occurred and recorded the link failure information, including the reason for the link failure as the handover failure. If the stored link is deleted when the handover fails based on the conditions Failed information, record the new link failure information, then the newly recorded link failure information corresponds to the network environment based on the network environment of the user equipment when the handover fails, not the network environment of the user equipment when the handover fails. , That is, it is not a network environment that essentially causes a link failure, so sending the newly recorded link failure to the base station may cause the base station to be unable to accurately determine the network environment that caused the link failure of the user equipment.
  • This embodiment retains the stored link failure information, that is, does not delete the stored link failure information, and then when reporting the link failure information to the base station, the stored link failure information ( The handover failure information) is sent to the base station so that the base station can identify the network environment that caused the link failure of the user equipment, which is beneficial to the base station to optimize the network.
  • Fig. 7 is a schematic flowchart showing yet another method for processing link failure information according to an embodiment of the present disclosure.
  • the trigger condition is a condition-based switching failure
  • the determining whether to delete the stored link failure information according to the trigger condition further includes:
  • step S206 the information about the link failure again is stored, where the information about the link failure again includes that the reason for the link failure again is that the switch fails based on the condition after the switch fails.
  • the link failure information when the triggering condition is handover failure, in addition to retaining the stored link failure information, the link failure information can also be stored, and the link failure information can be indicated in the link failure information again.
  • the reason is that the handover fails based on the conditions after the handover fails.
  • the stored link failure information and the newly stored link failure information can be reported to the base station, so that the base station can fully determine the specific circumstances of the two two-way failures. , Which is conducive to the optimization of the network by the base station.
  • Fig. 8 is a schematic flowchart showing yet another method for processing link failure information according to an embodiment of the present disclosure.
  • the trigger condition is that the network environment of the terminal satisfies the preset condition for condition-based switching, and the determining whether to delete the stored link failure information according to the trigger condition further includes:
  • step S207 delete the stored link failure information
  • step S208 the information about the link failure again is stored, where the information about the link failure again includes that the reason for the link failure again is the failure of the switching based on the condition.
  • the stored link failure information It is the information of the previous link failure.
  • the information of this link failure can make the base station know the network environment of the user equipment at the time of this link failure, so the stored link information can be deleted, and the link failure caused by the failure of the handover based on this condition can be stored. information. Thereby reducing the occupation of the storage space of the user equipment.
  • Fig. 9 is a schematic flowchart showing yet another method for processing link failure information according to an embodiment of the present disclosure. As shown in FIG. 9, before determining the trigger condition based on conditional switching, the method further includes:
  • step S3 a preset condition for condition-based switching sent by the base station is received.
  • the preset condition for condition-based handover sent by the base station may be received first, so as to determine the target cell for conditional handover, so that the target cell can be determined during the subsequent conditional handover.
  • the preset conditions include, but are not limited to, the identification of one or more target cells, handover trigger conditions, configuration of the target cell, etc. Based on the identification, the user equipment can determine one or more target cells, and then in the network environment of the user equipment When the handover trigger condition in the preset condition is met, the condition-based handover can be triggered, so that the user equipment attempts to handover to the target cell.
  • the preset conditions include the identities of 3 cells and the handover trigger conditions corresponding to the 3 cells:
  • the handover trigger condition is that the RSRP (Reference Signal Receiving Power) of the serving cell is lower than -98db, and the RSRP of cell 1 is higher than -98db;
  • the handover trigger condition is that the RSRP of cell 2 is 3db higher than the serving cell;
  • the handover trigger condition is that the RSRP of cell 3 is higher than -98db.
  • the user equipment detects that the network environment it is in meets the conditions for handover to cell 2, it performs condition-based handover to cell 2, but fails to handover to cell 2 for some reasons, then If the condition-based handover fails, the triggering condition of the condition-based handover can be determined. Specifically, the network environment of the user equipment satisfies the preset condition of the condition-based handover. Then, according to the embodiment shown in FIG. 7, the stored link failure can be deleted. Information, storing information about a new link failure, where the information about a new link failure may include the failure reason being a condition-based handover failure, and the handover trigger condition of cell 2.
  • the user equipment can perform cell selection.
  • the selection result is cell 3, which belongs to the target cell for conditional handover, and the user equipment can handover to cell 3.
  • the trigger condition for the conditional switch (the second conditional switch) can be determined.
  • the conditional switch fails.
  • the stored link failure information can be retained according to the embodiment shown in FIG. 4 , That is, the link failure information recorded during the first link failure is retained.
  • the link failure information can be further stored, and the link failure information is indicated in the link failure information again.
  • the reason for the path failure is that the switching based on the condition fails and the switching based on the condition fails again.
  • the stored link failure information can be deleted, and the new link failure information can be stored, that is, the wireless link failure information can be stored.
  • Link failure information if a wireless link failure occurs in the user equipment, this is also a link failure situation. Therefore, the stored link failure information can be deleted, and the new link failure information can be stored, that is, the wireless link failure information can be stored. Link failure information.
  • the user equipment can perform cell selection. For example, the selection result is cell 1.
  • Cell 1 belongs to the target cell for conditional handover, and the user equipment can handover to cell 1.
  • the user equipment fails to handover to cell 1, then a second If the conditional switching fails, the triggering condition of the conditional switching can be determined, specifically the wireless link failure, then the stored link failure information can be retained according to the embodiment shown in FIG. 2, that is, the wireless link failure
  • the link failure information recorded at the time can also be further stored according to the embodiment shown in FIG. 3, and the link failure information indicates that the reason for the link failure again is after the wireless link failure. Failed to switch based on conditions.
  • the present disclosure also provides an embodiment of the information processing device for link failure.
  • Fig. 10 is a schematic block diagram showing an information processing device with a link failure according to an embodiment of the present disclosure.
  • the device shown in this embodiment can be applied to a terminal.
  • the terminal includes but is not limited to electronic devices such as mobile phones, tablet computers, and wearable devices.
  • the terminal can be used as a user equipment (the following embodiments are mainly used when the terminal is used as a user equipment).
  • Communication with the base station for example, can communicate with the base station based on 4G LTE technology, or communicate with the base station based on 5G NR technology.
  • the information processing device for link failure may include
  • the condition determination module 1 is configured to determine the trigger condition of the condition-based switching when the condition-based switching fails;
  • the storage determining module 2 is configured to determine whether to delete the stored link failure information according to the trigger condition.
  • the trigger condition includes one of the following:
  • the wireless link fails, the handover fails based on the condition, and the handover fails, and the network environment of the terminal meets the preset condition for the condition based handover.
  • the trigger condition is a radio link failure
  • the storage determination module is configured to retain stored link failure information.
  • the trigger condition is a wireless link failure
  • the storage determining module is configured to store information about the link failure again, wherein the information about the link failure again includes that the reason for the link failure again is that the wireless link fails. After the link fails, the handover fails based on the conditions.
  • the triggering condition is switching failure based on the condition
  • the storage determining module is configured to retain the stored link failure information
  • the trigger condition is a switching failure based on a condition
  • the storage determining module is configured to store information about the link failure again, wherein the information about the link failure again includes the reason for the link failure again based on After the condition switch fails, the switch based on the condition fails again.
  • the trigger condition is handover failure
  • the storage determination module is configured to retain the stored link failure information
  • the trigger condition is a switch failure based on the condition
  • the storage determining module is configured to store information about the link failure again, wherein the information about the link failure again includes that the reason for the link failure again is the switch After the failure, the switch fails based on the conditions.
  • Fig. 11 is a schematic block diagram showing another information processing device with a link failure according to an embodiment of the present disclosure.
  • the trigger condition is that the network environment of the terminal satisfies a preset condition based on condition switching
  • the storage determination module 2 includes:
  • the deletion submodule 21 is configured to delete the stored link failure information
  • the storage sub-module 22 is configured to store the information about the link failure again, where the information about the link failure again includes that the reason for the link failure again is that the switch fails based on the condition.
  • Fig. 12 is a schematic block diagram showing yet another information processing device with a link failure according to an embodiment of the present disclosure. As shown in Figure 12, the device further includes:
  • the condition receiving module 3 is configured to receive the preset condition based on condition switching sent by the base station.
  • the relevant part can refer to the part of the description of the method embodiment.
  • the device embodiments described above are merely illustrative, and the modules described as separate components may or may not be physically separated, and the components displayed as modules may or may not be physical modules, that is, they may be located in One place, or it can be distributed to multiple network modules. Some or all of the modules can be selected according to actual needs to achieve the objectives of the solutions of the embodiments. Those of ordinary skill in the art can understand and implement it without creative work.
  • the embodiment of the present disclosure also proposes an electronic device, including:
  • a memory for storing processor executable instructions
  • processor is configured to implement the method described in any of the foregoing embodiments.
  • Fig. 13 is a schematic block diagram of an apparatus 1300 for processing link failure information according to an embodiment of the present disclosure.
  • the device 1300 may be a mobile phone, a computer, a digital broadcasting terminal, a messaging device, a game console, a tablet device, a medical device, a fitness device, a personal digital assistant, etc.
  • the device 1300 may include one or more of the following components: a processing component 1302, a memory 1304, a power supply component 1306, a multimedia component 1308, an audio component 1310, an input/output (I/O) interface 1312, a sensor component 1314, And the communication component 1316.
  • a processing component 1302 a memory 1304, a power supply component 1306, a multimedia component 1308, an audio component 1310, an input/output (I/O) interface 1312, a sensor component 1314, And the communication component 1316.
  • the processing component 1302 generally controls the overall operations of the device 1300, such as operations associated with display, telephone calls, data communications, camera operations, and recording operations.
  • the processing component 1302 may include one or more processors 1320 to execute instructions to complete all or part of the steps of the foregoing method.
  • the processing component 1302 may include one or more modules to facilitate the interaction between the processing component 1302 and other components.
  • the processing component 1302 may include a multimedia module to facilitate the interaction between the multimedia component 1308 and the processing component 1302.
  • the memory 1304 is configured to store various types of data to support the operation of the device 1300. Examples of such data include instructions for any application or method operating on the device 1300, contact data, phone book data, messages, pictures, videos, and the like.
  • the memory 1304 can be implemented by any type of volatile or non-volatile storage device or their combination, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable Programmable read only memory (EPROM), programmable read only memory (PROM), read only memory (ROM), magnetic memory, flash memory, magnetic disk or optical disk.
  • SRAM static random access memory
  • EEPROM electrically erasable programmable read-only memory
  • EPROM erasable Programmable read only memory
  • PROM programmable read only memory
  • ROM read only memory
  • magnetic memory flash memory
  • flash memory magnetic disk or optical disk.
  • the power supply component 1306 provides power to various components of the device 1300.
  • the power supply component 1306 may include a power management system, one or more power supplies, and other components associated with the generation, management, and distribution of power for the device 1300.
  • the multimedia component 1308 includes a screen that provides an output interface between the device 1300 and the user.
  • the screen may include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen may be implemented as a touch screen to receive input signals from the user.
  • the touch panel includes one or more touch sensors to sense touch, sliding, and gestures on the touch panel. The touch sensor may not only sense the boundary of a touch or slide action, but also detect the duration and pressure related to the touch or slide operation.
  • the multimedia component 1308 includes a front camera and/or a rear camera. When the device 1300 is in an operation mode, such as a shooting mode or a video mode, the front camera and/or the rear camera can receive external multimedia data. Each front camera and rear camera can be a fixed optical lens system or have focal length and optical zoom capabilities.
  • the audio component 1310 is configured to output and/or input audio signals.
  • the audio component 1310 includes a microphone (MIC), and when the device 1300 is in an operation mode, such as a call mode, a recording mode, and a voice recognition mode, the microphone is configured to receive external audio signals.
  • the received audio signal may be further stored in the memory 1304 or transmitted via the communication component 1316.
  • the audio component 1310 further includes a speaker for outputting audio signals.
  • the I/O interface 1312 provides an interface between the processing component 1302 and a peripheral interface module.
  • the above-mentioned peripheral interface module may be a keyboard, a click wheel, a button, and the like. These buttons may include, but are not limited to: home button, volume button, start button, and lock button.
  • the sensor component 1314 includes one or more sensors for providing the device 1300 with various aspects of status assessment.
  • the sensor component 1314 can detect the on/off status of the device 1300 and the relative positioning of components.
  • the component is the display and the keypad of the device 1300.
  • the sensor component 1314 can also detect the position change of the device 1300 or a component of the device 1300. , The presence or absence of contact between the user and the device 1300, the orientation or acceleration/deceleration of the device 1300, and the temperature change of the device 1300.
  • the sensor assembly 1314 may include a proximity sensor configured to detect the presence of nearby objects when there is no physical contact.
  • the sensor component 1314 may also include a light sensor, such as a CMOS or CCD image sensor, for use in imaging applications.
  • the sensor component 1314 may also include an acceleration sensor, a gyroscope sensor, a magnetic sensor, a pressure sensor or a temperature sensor.
  • the communication component 1316 is configured to facilitate wired or wireless communication between the apparatus 1300 and other devices.
  • the device 1300 can access a wireless network based on a communication standard, such as WiFi, 2G or 3G, 4G LTE, 5GNR, or a combination thereof.
  • the communication component 1316 receives a broadcast signal or broadcast related information from an external broadcast management system via a broadcast channel.
  • the communication component 1316 further includes a near field communication (NFC) module to facilitate short-range communication.
  • the NFC module can be implemented based on radio frequency identification (LFID) technology, infrared data association (IrDA) technology, ultra-wideband (UWB) technology, Bluetooth (BT) technology and other technologies.
  • LFID radio frequency identification
  • IrDA infrared data association
  • UWB ultra-wideband
  • Bluetooth Bluetooth
  • the apparatus 1300 may be implemented by one or more application specific integrated circuits (ASIC), digital signal processors (DSP), digital signal processing equipment (DSPD), programmable logic devices (PLD), field programmable A gate array (FPGA), controller, microcontroller, microprocessor, or other electronic components are implemented to implement the above methods.
  • ASIC application specific integrated circuits
  • DSP digital signal processors
  • DSPD digital signal processing equipment
  • PLD programmable logic devices
  • FPGA field programmable A gate array
  • controller microcontroller, microprocessor, or other electronic components are implemented to implement the above methods.
  • a non-transitory computer-readable storage medium including instructions such as a memory 1304 including instructions, and the foregoing instructions may be executed by the processor 1320 of the device 1300 to complete the foregoing method.
  • the non-transitory computer-readable storage medium may be ROM, random access memory (RAM), CD-ROM, magnetic tape, floppy disk, optical data storage device, etc.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本公开涉及链路失败的信息处理方法、装置和电子设备，所述方法包括：当基于条件切换失败后，确定基于条件切换的触发条件；根据所述触发条件，确定是否删除已存储的链路失败的信息根据本公开的实施例，可以根据失败的基于条件切换的触发条件，确定是否删除已存储的失败的信息，以便保证将存储的链路失败的信息发送至基站，基站能够明确造成用户设备链路失败的网络环境，有利于基站对网络优化。

Description

链路失败的信息处理方法和电子设备 技术领域
本公开涉及通信技术领域，具体而言，涉及链路失败的信息处理方法和电子设备。
背景技术
在用户设备与基站通信的过程中，用户设备可以对小区进行切换，也即切换所处的小区。
其中，在4G LTE(Long Term Evolution，长期演进)技术中，常规的切换操作，可以由用户设备对小区进行测量，然后将测量结果上报至基站，基站根据该测量结果向用户设备需要切换到的目标小区发送切换请求，若目标小区确认允许用户设备切换，基站可以给用户设备发送切换命令，在切换命令中携带有关切换的配置信息，用户设备可以根据该配置信息切换到目标小区。
为了提高切换的鲁棒性，在5G NR(New Radio，新空口)技术中，提出了基于条件切换(Conditional HandOver，简称CHO)，用户可以不必向基站上报测量结果，基站提前向用户设备发送预设条件以及可以切换的目标小区，当用户设备所处的网络环境满足预设条件，用户设备可以切换到目标小区。
对于常规的切换和基于条件的切换，切换失败都会发生链路失败(Link Failure，简称LF)，而当用户设备发送链路失败时，可以存储链路失败的信息，从而上报给基站，使得基站确定链路失败时用户设备所处网络环境的信息，以便基站对网络进行优化。但是在相关技术中，用户设备只存储最近一次链路失败的信息，也即当发生了新的链路失败，会删除已存储的链路失败的信息，并存储新发生的链路失败的信息。
可是链路失败的原因多种多样，按照目前的方式删除已存储的链路失败的信息，并存储新发生的链路失败的信息，可能会引发问题。
发明内容
有鉴于此，本公开的实施例提出了链路失败的信息处理方法、链路失败的信息处理装置和电子设备，以解决相关技术中的技术问题。
根据本公开实施例的第一方面，提出一种链路失败的信息处理方法，适用于终端，所述方法包括：
当基于条件切换失败后，确定基于条件切换的触发条件；
根据所述触发条件，确定是否删除已存储的链路失败的信息。
根据本公开实施例的第二方面，提出一种链路失败的信息处理方法，适用于终端，所述装置包括：
条件确定模块，被配置为当基于条件切换失败后，确定基于条件切换的触发条件；
存储确定模块，被配置为根据所述触发条件，确定是否删除已存储的链路失败的信息。
根据本公开实施例的第三方面，提出一种电子设备，包括：
处理器；
用于存储处理器可执行指令的存储器；
其中，所述处理器被配置为实现上述任一实施例所述的方法。
根据本公开的实施例，可以根据失败的基于条件切换的触发条件，确定是否删除已存储的失败的信息，以便保证将存储的链路失败的信息发送至基站，基站能够明确造成用户设备链路失败的网络环境，有利于基站对网络优化。
附图说明
为了更清楚地说明本公开实施例中的技术方案，下面将对实施例描述中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本公开的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动性的前提下，还可以根据这些附图获得其他的附图。
图1是根据本公开的实施例示出的一种链路失败的信息处理方法的示意流程图。
图2是根据本公开的实施例示出的另一种链路失败的信息处理方法的示意流程图。
图3是根据本公开的实施例示出的又一种链路失败的信息处理方法的示意流程 图。
图4是根据本公开的实施例示出的又一种链路失败的信息处理方法的示意流程图。
图5是根据本公开的实施例示出的又一种链路失败的信息处理方法的示意流程图。
图6是根据本公开的实施例示出的又一种链路失败的信息处理方法的示意流程图。
图7是根据本公开的实施例示出的又一种链路失败的信息处理方法的示意流程图。
图8是根据本公开的实施例示出的又一种链路失败的信息处理方法的示意流程图。
图9是根据本公开的实施例示出的又一种链路失败的信息处理方法的示意流程图。
图10是根据本公开的实施例示出的一种链路失败的信息处理装置的示意框图。
图11是根据本公开的实施例示出的另一种链路失败的信息处理装置的示意框图。
图12是根据本公开的实施例示出的又一种链路失败的信息处理装置的示意框图。
图13是根据本公开的实施例示出的一种用于处理链路失败的信息的装置的示意框图。
具体实施方式
下面将结合本公开实施例中的附图，对本公开实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例仅仅是本公开一部分实施例，而不是全部的实施例。基于本公开中的实施例，本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例，都属于本公开保护的范围。
除了常规的切换和基于条件的切换在失败时会发生链路失败，当用户设备发生无线链路失败(Radio Link Failure，简称RLF)，也会判定发生了链路失败。
而用户设备在发生链路失败的情况下，可以进行小区选择，如果选择的小区刚好是基于条件切换所指定的目标小区，那么用户设备选择目标小区接入，就相当于再次进行基于条件切换。当用户设备按照上述方式再次进行条件切换失败，也会认定发生了链路失败，那么按照相关技术中存储链路失败的信息的方式，会删除已存储的链路失败的信息。
可是引发再次链路失败的动作是基于条件切换失败，然而基于条件切换的触发条件不尽相同，如果对于所有触发条件下的基于条件切换失败，都删除已存储的链路失败的信息，可能导致基站无法基于链路失败的信息全面地了解终端所处网络的情况，不利于基站对网络优化。
图1是根据本公开的实施例示出的一种链路失败的信息处理方法的示意流程图。本实施例所示的方法可以适用于终端，所述终端包括但不限于手机、平板电脑、可穿戴设备等电子设备，所述终端可以作为用户设备(以下实施例主要在终端作为用户设备的情况下进行描述)与基站通信，例如可以基于4G LTE技术与基站通信，也可以基于5G NR技术与基站通信。
如图1所示，所述链路失败的信息处理方法，可以包括以下步骤：
在步骤S1中，当基于条件切换失败后，确定基于条件切换的触发条件；
在步骤S2中，根据所述触发条件，确定是否删除已存储的链路失败的信息。
在一个实施例中，链路失败的信息包括但不限于链路失败时用户设备(也即所述终端)所处的小区，用户设备对于所处的小区的测量数据，用户设备的位置信息，链路失败前用户设备所使用的C-RNTI(Cell-Radio Network Temporary Identifier，小区无线网络临时标识)，链路失败的原因(例如无线链路失败、切换失败、基于条件切换失败)等，而当链路失败是由基于条件切换所导致的，链路失败的信息还可以包括基站为用户设备指示的基于条件切换的目标小区。
对于所存储的链路失败的信息，用户设备在与基站建立连接(包括连接建立、连接重建、连接恢复等情况)后，可以将链路失败的信息上报给基站，基站根据接收到的链路失败的信息，可以确定用户设备链路失败时的网络环境，从而针对性地对网络进行优化，以便提高用户设备的通信效果。
根据本公开的实施例，当终端基于条件切换失败，虽然也是发生了链路失败，但是并不会马上删除已存储的链路失败的信息，而是可以先确定失败的基于条件切换 的触发条件。
若基于条件切换的触发条件是用户设备的网络环境满足基于条件切换的预设条件，这是一般情况下触发基于条件切换的条件，那么已存储的链路失败的信息，就是前一次链路失败的信息。
而一般情况下，用户设备所处的网络环境，不会频繁地满足基于条件切换的预设条件，也即用户设备不会频繁地基于条件切换，那么前一次链路失败，到本次基于条件切换失败，一般相距时间较长，用户设备所处网络环境一般也发生了较大变化，在这种情况下，前一次链路失败的信息对于基站优化网络的参考性较弱，本次链路失败的信息可以使得基站明确本次链路失败时用户设备所处的网络环境，所以可以删除已存储的链路信息，并存储本次基于条件切换失败而造成链路失败的信息。
基于条件切换除了在用户设备的网络环境满足基于条件切换的预设条件时触发，还可以在链路失败后触发，具体是在链路失败后，用户设备进行小区选择时，选择的小区刚好是基于条件切换所指定的目标小区，那么用户设备选择目标小区接入，就相当于再次进行基于条件切换。
而链路失败可以包括无线链路失败、基于条件切换失败、切换失败(也即4GLTE中常规的切换操作失败)等情况。也即主要存在三种情况：
情况一，在无线链路失败后，用户设备可以在小区选择时进行基于条件切换；
情况二，在基于条件切换失败后，用户设备可以在小区选择时进行基于条件切换，对于这种情况，存在两次基于条件切换，为了区分，将小区选择时进行的基于条件切换称作第二次基于条件切换，将前一次基于条件切换称作第一次基于条件切换；
情况三，在切换失败后，用户设备可以在小区选择时进行基于条件切换。
对于上述情况一，基于条件切换并不是在用户设备的网络环境满足预设条件时触发的，而是由无线链路失败触发的，那么本质上导致链路失败的网络环境，是无线链路失败时用户设备的网络环境，而非基于条件切换失败时用户设备的网络环境。
而在无线链路失败时，用户设备已经确定发生了链路失败，并记录了链路失败的信息，其中包括链路失败的原因为无线链路失败，如果在基于条件切换失败时删除了已存储的链路失败的信息，记录新的链路失败的信息，那么新记录的链路失败的信息，所对应网络环境的就是基于条件切换失败时用户设备的网络环境，而不是无线链路失败时用户设备的网络环境，也即不是本质上导致链路失败的网络环境，那么将新 纪录的链路失败的发送至基站，可能导致基站不能准确地确定导致用户设备链路失败的网络环境的情况。
对于上述情况二，第二次基于条件切换并不是在用户设备的网络环境满足预设条件时触发的，而是由第一次基于条件切换失败触发的，那么本质上导致链路失败的网络环境，是第一次基于条件切换失败时用户设备的网络环境，而非第二次基于条件切换失败时用户设备的网络环境。
而在第一次基于条件切换失败时，用户设备已经确定发生了链路失败，并记录了链路失败的信息，其中包括链路失败的原因为基于条件切换失败，如果在第二次基于条件切换失败时删除了已存储的链路失败的信息，记录新的链路失败的信息，那么新记录的链路失败的信息，所对应网络环境的就是第二次基于条件切换失败时用户设备的网络环境，而不是第一次基于条件切换失败时用户设备的网络环境，也即不是本质上导致链路失败的网络环境，那么将新纪录的链路失败的发送至基站，可能导致基站不能准确地确定导致用户设备链路失败的网络环境的情况。
对于上述情况三，基于条件切换并不是在用户设备的网络环境满足预设条件时触发的，而是由切换失败触发的，那么本质上导致链路失败的网络环境，是切换失败时用户设备的网络环境，而非基于条件切换失败时用户设备的网络环境。
而在切换失败时，用户设备已经确定发生了链路失败，并记录了链路失败的信息，其中包括链路失败的原因为切换失败，如果在基于条件切换失败时删除了已存储的链路失败的信息，记录新的链路失败的信息，那么新记录的链路失败的信息，所对应网络环境的就是基于条件切换失败时用户设备的网络环境，而不是切换失败时用户设备的网络环境，也即不是本质上导致链路失败的网络环境，那么将新纪录的链路失败的发送至基站，可能导致基站不能准确地确定导致用户设备链路失败的网络环境的情况。
根据本公开的实施例，可以根据失败的基于条件切换的触发条件，确定是否删除已存储的失败的信息，例如触发条件为用户设备的网络环境满足基于条件切换的预设条件，可以删除已存储的链路失败的信息，而对于上述情况一、情况二和情况三，则可以保留已存储的链路失败的信息，以便保证将存储的链路失败的信息发送至基站，基站能够明确造成用户设备链路失败的网络环境，有利于基站对网络优化。
可选地，所述触发条件包括以下之一：
无线链路失败，基于条件切换失败，切换失败，所述终端的网络环境满足基于条件切换的预设条件。
图2是根据本公开的实施例示出的另一种链路失败的信息处理方法的示意流程图。如图2所示，所述触发条件为无线链路失败，所述根据所述触发条件，确定是否删除已存储的链路失败的信息包括：
在步骤S201中，保留已存储的链路失败的信息。
在一个实施例中，若基于条件切换并不是在用户设备的网络环境满足预设条件时触发的，而是由无线链路失败触发的，那么本质上导致链路失败的网络环境，是无线链路失败时用户设备的网络环境，而非基于条件切换失败时用户设备的网络环境。
而在无线链路失败时，用户设备已经确定发生了链路失败，并记录了链路失败的信息，其中包括链路失败的原因为无线链路失败，如果在基于条件切换失败时删除了已存储的链路失败的信息，记录新的链路失败的信息，那么新记录的链路失败的信息，所对应网络环境的就是基于条件切换失败时用户设备的网络环境，而不是无线链路失败时用户设备的网络环境，也即不是本质上导致链路失败的网络环境，那么将新纪录的链路失败的发送至基站，可能导致基站不能准确地确定导致用户设备链路失败的网络环境的情况。
本实施例通过保留已存储的链路失败的信息，也即不删除已存储的链路失败的信息，进而在向基站上报链路失败的信息时，可以将已存储的链路失败的信息(无线链路失败的信息)发送至基站，以便基站能够明确造成用户设备链路失败的网络环境，有利于基站对网络优化。
图3是根据本公开的实施例示出的又一种链路失败的信息处理方法的示意流程图。如图3所示，所述触发条件为无线链路失败，所述根据所述触发条件，确定是否删除已存储的链路失败的信息还包括：
在步骤S202中，存储再次链路失败的信息，其中，所述再次链路失败的信息包括再次链路失败的原因为无线链路失败后基于条件切换失败。
在一个实施例中，在触发条件为无线链路失败时，除了保留已存储的链路失败的信息，还可以存储再次链路失败的信息，并在再次链路失败的信息中指明再次链路失败的原因为无线链路失败后基于条件切换失败。进而在向基站上报链路失败的信息时，可以将已存储的链路失败的信息以及新存储的再次链路失败的信息上报至基站， 使得基站能够全面地确定两次两路失败的具体情况，有利于基站对网络优化。
图4是根据本公开的实施例示出的又一种链路失败的信息处理方法的示意流程图。如图4所示，所述触发条件为基于条件切换(第一次基于条件切换)失败，所述根据所述触发条件，确定是否删除已存储的链路失败的信息包括：
在步骤S203中，保留已存储的链路失败的信息。
在一个实施例中，若第二次基于条件切换并不是在用户设备的网络环境满足预设条件时触发的，而是由第一次基于条件切换失败触发的，那么本质上导致链路失败的网络环境，是第一次基于条件切换失败时用户设备的网络环境，而非第二次基于条件切换失败时用户设备的网络环境。
而在第一次基于条件切换失败时，用户设备已经确定发生了链路失败，并记录了链路失败的信息，其中包括链路失败的原因为基于条件切换失败，如果在第二次基于条件切换失败时删除了已存储的链路失败的信息，记录新的链路失败的信息，那么新记录的链路失败的信息，所对应网络环境的就是第二次基于条件切换失败时用户设备的网络环境，而不是第一次基于条件切换失败时用户设备的网络环境，也即不是本质上导致链路失败的网络环境，那么将新纪录的链路失败的发送至基站，可能导致基站不能准确地确定导致用户设备链路失败的网络环境的情况
本实施例通过保留已存储的链路失败的信息，也即不删除已存储的链路失败的信息，进而在向基站上报链路失败的信息时，可以将已存储的链路失败的信息(第一次基于条件切换失败的信息)发送至基站，以便基站能够明确造成用户设备链路失败的网络环境，有利于基站对网络优化。
图5是根据本公开的实施例示出的又一种链路失败的信息处理方法的示意流程图。如图5所示，所述触发条件为基于条件切换失败，所述根据所述触发条件，确定是否删除已存储的链路失败的信息还包括：
在步骤S204中，存储再次链路失败的信息，其中，所述再次链路失败的信息包括再次链路失败的原因为基于条件切换失败后再次基于条件切换失败。
在一个实施例中，在触发条件为基于条件切换失败时，除了保留已存储的链路失败的信息，还可以存储再次链路失败的信息，并在再次链路失败的信息中指明再次链路失败的原因为基于条件切换失败后再次基于条件切换失败。进而在向基站上报链路失败的信息时，可以将已存储的链路失败的信息以及新存储的再次链路失败的信息 上报至基站，使得基站能够全面地确定两次两路失败的具体情况，有利于基站对网络优化。
图6是根据本公开的实施例示出的又一种链路失败的信息处理方法的示意流程图。如图6所示，所述触发条件为切换失败，所述根据所述触发条件，确定是否删除已存储的链路失败的信息包括：
在步骤S205中，保留已存储的链路失败的信息，
在一个实施例中，若基于条件切换并不是在用户设备的网络环境满足预设条件时触发的，而是由切换失败触发的，那么本质上导致链路失败的网络环境，是切换失败时用户设备的网络环境，而非基于条件切换失败时用户设备的网络环境。
而在切换失败时，用户设备已经确定发生了链路失败，并记录了链路失败的信息，其中包括链路失败的原因为切换失败，如果在基于条件切换失败时删除了已存储的链路失败的信息，记录新的链路失败的信息，那么新记录的链路失败的信息，所对应网络环境的就是基于条件切换失败时用户设备的网络环境，而不是切换失败时用户设备的网络环境，也即不是本质上导致链路失败的网络环境，那么将新纪录的链路失败的发送至基站，可能导致基站不能准确地确定导致用户设备链路失败的网络环境的情况。
本实施例通过保留已存储的链路失败的信息，也即不删除已存储的链路失败的信息，进而在向基站上报链路失败的信息时，可以将已存储的链路失败的信息(切换失败的信息)发送至基站，以便基站能够明确造成用户设备链路失败的网络环境，有利于基站对网络优化。
图7是根据本公开的实施例示出的又一种链路失败的信息处理方法的示意流程图。如图7所示，所述触发条件为基于条件切换失败，所述根据所述触发条件，确定是否删除已存储的链路失败的信息还包括：
在步骤S206中，存储再次链路失败的信息，其中，所述再次链路失败的信息包括再次链路失败的原因为切换失败后基于条件切换失败。
在一个实施例中，在触发条件为切换失败时，除了保留已存储的链路失败的信息，还可以存储再次链路失败的信息，并在再次链路失败的信息中指明再次链路失败的原因为切换失败后基于条件切换失败。进而在向基站上报链路失败的信息时，可以将已存储的链路失败的信息以及新存储的再次链路失败的信息上报至基站，使得基站 能够全面地确定两次两路失败的具体情况，有利于基站对网络优化。
图8是根据本公开的实施例示出的又一种链路失败的信息处理方法的示意流程图。如图8所示，所述触发条件为所述终端的网络环境满足基于条件切换的预设条件，所述根据所述触发条件，确定是否删除已存储的链路失败的信息还包括：
在步骤S207中，删除已存储的链路失败的信息；
在步骤S208中，存储再次链路失败的信息，其中，所述再次链路失败的信息包括再次链路失败的原因为基于条件切换失败。
在一个实施例中，若基于条件切换的触发条件是用户设备的网络环境满足基于条件切换的预设条件，这是一般情况下触发基于条件切换的条件，那么已存储的链路失败的信息，就是前一次链路失败的信息。然而本次链路失败的信息可以使得基站明确本次链路失败时用户设备所处的网络环境，所以可以删除已存储的链路信息，并存储本次基于条件切换失败而造成链路失败的信息。从而减少对用户设备存储空间的占用。
图9是根据本公开的实施例示出的又一种链路失败的信息处理方法的示意流程图。如图9所示，在确定基于条件切换的触发条件之前，所述方法还包括：
在步骤S3中，接收基站发送的基于条件切换的预设条件。
在一个实施例中，可以先接收基站发送的基于条件切换的预设条件，以便确定基于条件切换的目标小区，以便后续在基于条件切换时，能够确定到目标小区。
其中，预设条件包括但不限于一个或多个目标小区的标识、切换触发条件、目标小区的配置等，基于该标识，用户设备可以确定一个或多个目标小区，进而在用户设备的网络环境满足预设条件中的切换触发条件时，可以触发基于条件切换，使得用户设备尝试向目标小区切换。
例如预设条件包括3个小区的标识，以及3个小区对应的切换触发条件：
小区1，切换触发条件为服务小区的RSRP(Reference Signal Receiving Power,参考信号接收功率)低于-98db，小区1的RSRP高于-98db；
小区2，切换触发条件为小区2的RSRP比服务小区高3db；
小区3，切换触发条件为小区3的RSRP高于于-98db。
在一个实施例中，若用户设备检测到所处的网络环境满足向小区2切换的条件， 则进行基于条件切换，向小区2切换，但是出于某些原因未能切换到小区2，那么发生了基于条件切换失败，可以确定基于条件切换的触发条件，具体是用户设备的网络环境满足基于条件切换的预设条件，那么可以按照图7所示的实施例，删除已存储的链路失败的信息，存储新的链路失败的信息，其中，新的链路失败的信息可以包括失败原因为基于条件切换失败，以及小区2的切换触发条件。
然后用户设备可以进行小区选择，例如选择结果为小区3，小区3属于基于条件切换的目标小区，用户设备可以向小区3切换，而若用户设备也未能切换到小区3，那么发生了第二次基于条件切换失败，可以确定基于条件切换(第二次基于条件切换)的触发条件，具体是基于条件切换失败，那么可以按照图4所示的实施例，保留已存储的链路失败的信息，也即保留第一次链路失败时记录的链路失败的信息，还可以按照图5所示的实施例，进一步存储再次链路失败的信息，在再次链路失败的信息中指示再次链路失败的原因为基于条件切换失败后再次基于条件切换失败。
在一个实施例中，若用户设备发生了无线链路失败，这也属于链路失败的情况，所以可以删除已存储的链路失败的信息，存储新的链路失败的信息，也即存储无线链路失败的信息。
然后用户设备可以进行小区选择，例如选择结果为小区1，小区1属于基于条件切换的目标小区，用户设备可以向小区1切换，而若用户设备也未能切换到小区1，那么发生了第二次基于条件切换失败，可以确定基于条件切换的触发条件，具体是无线链路失败，那么可以按照图2所示的实施例，保留已存储的链路失败的信息，也即保留无线链路失败时记录的链路失败的信息，还可以按照图3所示的实施例，进一步存储再次链路失败的信息，在再次链路失败的信息中指示再次链路失败的原因为无线链路失败后基于条件切换失败。
与前述的链路失败的信息处理方法的实施例相对应，本公开还提供了链路失败的信息处理装置的实施例。
图10是根据本公开的实施例示出的一种链路失败的信息处理装置的示意框图。本实施例所示的装置可以适用于终端，所述终端包括但不限于手机、平板电脑、可穿戴设备等电子设备，所述终端可以作为用户设备(以下实施例主要在终端作为用户设备的情况下进行描述)与基站通信，例如可以基于4G LTE技术与基站通信，也可以基于5G NR技术与基站通信。
如图10所示，所述链路失败的信息处理装置，可以包括
条件确定模块1，被配置为当基于条件切换失败后，确定基于条件切换的触发条件；
存储确定模块2，被配置为根据所述触发条件，确定是否删除已存储的链路失败的信息。
可选地，所述触发条件包括以下之一：
无线链路失败，基于条件切换失败，切换失败，所述终端的网络环境满足基于条件切换的预设条件。
可选地，所述触发条件为无线链路失败，所述存储确定模块，被配置为保留已存储的链路失败的信息。
可选地，所述触发条件为无线链路失败，所述存储确定模块，被配置为存储再次链路失败的信息，其中，所述再次链路失败的信息包括再次链路失败的原因为无线链路失败后基于条件切换失败。
可选地，所述触发条件为基于条件切换失败，所述存储确定模块，被配置为保留已存储的链路失败的信息。
可选地，所述触发条件为基于条件切换失败，所述存储确定模块，被配置为存储再次链路失败的信息，其中，所述再次链路失败的信息包括再次链路失败的原因为基于条件切换失败后再次基于条件切换失败。
可选地，所述触发条件为切换失败，所述存储确定模块，被配置为保留已存储的链路失败的信息，
可选地，所述触发条件为基于条件切换失败，所述存储确定模块，被配置为存储再次链路失败的信息，其中，所述再次链路失败的信息包括再次链路失败的原因为切换失败后基于条件切换失败。
图11是根据本公开的实施例示出的另一种链路失败的信息处理装置的示意框图。如图11所示，所述触发条件为所述终端的网络环境满足基于条件切换的预设条件，所述存储确定模块2包括：
删除子模块21，被配置为删除已存储的链路失败的信息；
存储子模块22，被配置为存储再次链路失败的信息，其中，所述再次链路失败 的信息包括再次链路失败的原因为基于条件切换失败。
图12是根据本公开的实施例示出的又一种链路失败的信息处理装置的示意框图。如图12所示，所述装置还包括：
条件接收模块3，被配置为接收基站发送的基于条件切换的预设条件。
关于上述实施例中的装置，其中各个模块执行操作的具体方式已经在相关方法的实施例中进行了详细描述，此处将不做详细阐述说明。
对于装置实施例而言，由于其基本对应于方法实施例，所以相关之处参见方法实施例的部分说明即可。以上所描述的装置实施例仅仅是示意性的，其中所述作为分离部件说明的模块可以是或者也可以不是物理上分开的，作为模块显示的部件可以是或者也可以不是物理模块，即可以位于一个地方，或者也可以分布到多个网络模块上。可以根据实际的需要选择其中的部分或者全部模块来实现本实施例方案的目的。本领域普通技术人员在不付出创造性劳动的情况下，即可以理解并实施。
本公开的实施例还提出一种电子设备，包括：
处理器；
用于存储处理器可执行指令的存储器；
其中，所述处理器被配置为实现上述任一实施例所述的方法。
图13是根据本公开的实施例示出的一种用于处理链路失败的信息的装置1300的示意框图。例如，装置1300可以是移动电话，计算机，数字广播终端，消息收发设备，游戏控制台，平板设备，医疗设备，健身设备，个人数字助理等。
参照图13，装置1300可以包括以下一个或多个组件：处理组件1302，存储器1304，电源组件1306，多媒体组件1308，音频组件1310，输入/输出(I/O)的接口1312，传感器组件1314，以及通信组件1316。
处理组件1302通常控制装置1300的整体操作，诸如与显示，电话呼叫，数据通信，相机操作和记录操作相关联的操作。处理组件1302可以包括一个或多个处理器1320来执行指令，以完成上述的方法的全部或部分步骤。此外，处理组件1302可以包括一个或多个模块，便于处理组件1302和其他组件之间的交互。例如，处理组件1302可以包括多媒体模块，以方便多媒体组件1308和处理组件1302之间的交互。
存储器1304被配置为存储各种类型的数据以支持在装置1300的操作。这些数 据的示例包括用于在装置1300上操作的任何应用程序或方法的指令，联系人数据，电话簿数据，消息，图片，视频等。存储器1304可以由任何类型的易失性或非易失性存储设备或者它们的组合实现，如静态随机存取存储器(SRAM)，电可擦除可编程只读存储器(EEPROM)，可擦除可编程只读存储器(EPROM)，可编程只读存储器(PROM)，只读存储器(ROM)，磁存储器，快闪存储器，磁盘或光盘。
电源组件1306为装置1300的各种组件提供电力。电源组件1306可以包括电源管理系统，一个或多个电源，及其他与为装置1300生成、管理和分配电力相关联的组件。
多媒体组件1308包括在所述装置1300和用户之间的提供一个输出接口的屏幕。在一些实施例中，屏幕可以包括液晶显示器(LCD)和触摸面板(TP)。如果屏幕包括触摸面板，屏幕可以被实现为触摸屏，以接收来自用户的输入信号。触摸面板包括一个或多个触摸传感器以感测触摸、滑动和触摸面板上的手势。所述触摸传感器可以不仅感测触摸或滑动动作的边界，而且还检测与所述触摸或滑动操作相关的持续时间和压力。在一些实施例中，多媒体组件1308包括一个前置摄像头和/或后置摄像头。当装置1300处于操作模式，如拍摄模式或视频模式时，前置摄像头和/或后置摄像头可以接收外部的多媒体数据。每个前置摄像头和后置摄像头可以是一个固定的光学透镜系统或具有焦距和光学变焦能力。
音频组件1310被配置为输出和/或输入音频信号。例如，音频组件1310包括一个麦克风(MIC)，当装置1300处于操作模式，如呼叫模式、记录模式和语音识别模式时，麦克风被配置为接收外部音频信号。所接收的音频信号可以被进一步存储在存储器1304或经由通信组件1316发送。在一些实施例中，音频组件1310还包括一个扬声器，用于输出音频信号。
I/O接口1312为处理组件1302和外围接口模块之间提供接口，上述外围接口模块可以是键盘，点击轮，按钮等。这些按钮可包括但不限于：主页按钮、音量按钮、启动按钮和锁定按钮。
传感器组件1314包括一个或多个传感器，用于为装置1300提供各个方面的状态评估。例如，传感器组件1314可以检测到装置1300的打开/关闭状态，组件的相对定位，例如所述组件为装置1300的显示器和小键盘，传感器组件1314还可以检测装置1300或装置1300一个组件的位置改变，用户与装置1300接触的存在或不存在，装置1300方位或加速/减速和装置1300的温度变化。传感器组件1314可以包括接近传 感器，被配置用来在没有任何的物理接触时检测附近物体的存在。传感器组件1314还可以包括光传感器，如CMOS或CCD图像传感器，用于在成像应用中使用。在一些实施例中，该传感器组件1314还可以包括加速度传感器，陀螺仪传感器，磁传感器，压力传感器或温度传感器。
通信组件1316被配置为便于装置1300和其他设备之间有线或无线方式的通信。装置1300可以接入基于通信标准的无线网络，如WiFi，2G或3G，4G LTE、5GNR或它们的组合。在一个示例性实施例中，通信组件1316经由广播信道接收来自外部广播管理系统的广播信号或广播相关信息。在一个示例性实施例中，所述通信组件1316还包括近场通信(NFC)模块，以促进短程通信。例如，在NFC模块可基于射频识别(LFID)技术，红外数据协会(IrDA)技术，超宽带(UWB)技术，蓝牙(BT)技术和其他技术来实现。
在示例性实施例中，装置1300可以被一个或多个应用专用集成电路(ASIC)、数字信号处理器(DSP)、数字信号处理设备(DSPD)、可编程逻辑器件(PLD)、现场可编程门阵列(FPGA)、控制器、微控制器、微处理器或其他电子元件实现，用于执行上述方法。
在示例性实施例中，还提供了一种包括指令的非临时性计算机可读存储介质，例如包括指令的存储器1304，上述指令可由装置1300的处理器1320执行以完成上述方法。例如，所述非临时性计算机可读存储介质可以是ROM、随机存取存储器(RAM)、CD-ROM、磁带、软盘和光数据存储设备等。
本领域技术人员在考虑说明书及实践这里公开的公开后，将容易想到本公开的其它实施方案。本公开旨在涵盖本公开的任何变型、用途或者适应性变化，这些变型、用途或者适应性变化遵循本公开的一般性原理并包括本公开未公开的本技术领域中的公知常识或惯用技术手段。说明书和实施例仅被视为示例性的，本公开的真正范围和精神由下面的权利要求指出。
应当理解的是，本公开并不局限于上面已经描述并在附图中示出的精确结构，并且可以在不脱离其范围进行各种修改和改变。本公开的范围仅由所附的权利要求来限制。
需要说明的是，在本文中，诸如第一和第二等之类的关系术语仅仅用来将一个实体或者操作与另一个实体或操作区分开来，而不一定要求或者暗示这些实体或操作 之间存在任何这种实际的关系或者顺序。术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含，从而使得包括一系列要素的过程、方法、物品或者设备不仅包括那些要素，而且还包括没有明确列出的其他要素，或者是还包括为这种过程、方法、物品或者设备所固有的要素。在没有更多限制的情况下，由语句“包括一个……”限定的要素，并不排除在包括所述要素的过程、方法、物品或者设备中还存在另外的相同要素。
以上对本公开实施例所提供的方法和装置进行了详细介绍，本文中应用了具体个例对本公开的原理及实施方式进行了阐述，以上实施例的说明只是用于帮助理解本公开的方法及其核心思想；同时，对于本领域的一般技术人员，依据本公开的思想，在具体实施方式及应用范围上均会有改变之处，综上所述，本说明书内容不应理解为对本公开的限制。

Claims (12)

  1. 一种链路失败的信息处理方法，其特征在于，适用于终端，所述方法包括：
    当基于条件切换失败后，确定基于条件切换的触发条件；
    根据所述触发条件，确定是否删除已存储的链路失败的信息。
  2. 根据权利要求1所述的方法，其特征在于，所述触发条件包括以下之一：
    无线链路失败，基于条件切换失败，切换失败，所述终端的网络环境满足基于条件切换的预设条件。
  3. 根据权利要求2所述的方法，其特征在于，所述触发条件为无线链路失败，所述根据所述触发条件，确定是否删除已存储的链路失败的信息包括：
    保留已存储的链路失败的信息。
  4. 根据权利要求3所述的方法，其特征在于，所述触发条件为无线链路失败，所述根据所述触发条件，确定是否删除已存储的链路失败的信息还包括：
    存储再次链路失败的信息，其中，所述再次链路失败的信息包括再次链路失败的原因为无线链路失败后基于条件切换失败。
  5. 根据权利要求2所述的方法，其特征在于，所述触发条件为基于条件切换失败，所述根据所述触发条件，确定是否删除已存储的链路失败的信息包括：
    保留已存储的链路失败的信息。
  6. 根据权利要求5所述的方法，其特征在于，所述触发条件为基于条件切换失败，所述根据所述触发条件，确定是否删除已存储的链路失败的信息还包括：
    存储再次链路失败的信息，其中，所述再次链路失败的信息包括再次链路失败的原因为基于条件切换失败后再次基于条件切换失败。
  7. 根据权利要求2所述的方法，其特征在于，所述触发条件为切换失败，所述根据所述触发条件，确定是否删除已存储的链路失败的信息包括：
    保留已存储的链路失败的信息，
  8. 根据权利要求7所述的方法，其特征在于，所述触发条件为基于条件切换失败，所述根据所述触发条件，确定是否删除已存储的链路失败的信息还包括：
    存储再次链路失败的信息，其中，所述再次链路失败的信息包括再次链路失败的原因为切换失败后基于条件切换失败。
  9. 根据权利要求2所述的方法，其特征在于，所述触发条件为所述终端的网络环境满足基于条件切换的预设条件，所述根据所述触发条件，确定是否删除已存储的链路失败的信息还包括：
    删除已存储的链路失败的信息；
    存储再次链路失败的信息，其中，所述再次链路失败的信息包括再次链路失败的原因为基于条件切换失败。
  10. 根据权利要求1至9中任一项所述的方法，其特征在于，在确定基于条件切换的触发条件之前，所述方法还包括：
    接收基站发送的基于条件切换的预设条件。
  11. 一种链路失败的信息处理方法，其特征在于，适用于终端，所述装置包括：
    条件确定模块，被配置为当基于条件切换失败后，确定基于条件切换的触发条件；
    存储确定模块，被配置为根据所述触发条件，确定是否删除已存储的链路失败的信息。
  12. 一种电子设备，其特征在于，包括：
    处理器；
    用于存储处理器可执行指令的存储器；
    其中，所述处理器被配置为实现权利要求1至10中任一项权利要求所述的方法。
PCT/CN2019/108478 2019-09-27 2019-09-27 链路失败的信息处理方法和电子设备 Ceased WO2021056403A1 (zh)

Priority Applications (5)

Application Number Priority Date Filing Date Title
CN201980002156.4A CN110915259B (zh) 2019-09-27 2019-09-27 链路失败的信息处理方法和电子设备
CN202210557016.7A CN115002856B (zh) 2019-09-27 2019-09-27 链路失败的信息处理方法和电子设备
PCT/CN2019/108478 WO2021056403A1 (zh) 2019-09-27 2019-09-27 链路失败的信息处理方法和电子设备
US17/763,589 US12127055B2 (en) 2019-09-27 2019-09-27 Method for processing link failure information and electronic device
EP19946919.8A EP4037425A4 (en) 2019-09-27 2019-09-27 Link failure information processing method and electronic device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2019/108478 WO2021056403A1 (zh) 2019-09-27 2019-09-27 链路失败的信息处理方法和电子设备

Publications (1)

Publication Number Publication Date
WO2021056403A1 true WO2021056403A1 (zh) 2021-04-01

Family

ID=69814293

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/108478 Ceased WO2021056403A1 (zh) 2019-09-27 2019-09-27 链路失败的信息处理方法和电子设备

Country Status (4)

Country Link
US (1) US12127055B2 (zh)
EP (1) EP4037425A4 (zh)
CN (2) CN115002856B (zh)
WO (1) WO2021056403A1 (zh)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113677040B (zh) * 2020-05-13 2025-09-05 夏普株式会社 无线链路失败恢复方法及对应的用户设备
CN114765815B (zh) 2021-01-14 2024-07-30 大唐移动通信设备有限公司 小区切换方法、装置及存储介质

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104039023A (zh) * 2013-03-05 2014-09-10 电信科学技术研究院 一种进行rrc连接重建的方法及用户设备
WO2018203716A1 (ko) * 2017-05-04 2018-11-08 삼성전자 주식회사 단말 자율 핸드오버에서의 측정 리포트 이벤트 운용 및 네트워크 시그널링 방법

Family Cites Families (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102083115B (zh) * 2010-11-03 2013-09-25 大唐移动通信设备有限公司 一种长期演进系统中rlf指示消息的处理方法和设备
CN103391568A (zh) * 2012-05-11 2013-11-13 北京三星通信技术研究有限公司 支持检测rlf或者切换失败原因的方法
CN108243469B (zh) * 2016-12-23 2021-07-16 夏普株式会社 用户移动性方法和设备
US11272417B2 (en) * 2018-01-12 2022-03-08 FG Innovation Company Limited Conditional handover procedures
EP3766274B1 (en) 2018-03-12 2024-09-18 Nokia Technologies Oy Determination for conditional handover failure
EP3939353A1 (en) * 2019-03-15 2022-01-19 Telefonaktiebolaget LM Ericsson (publ) Storing and restoring conditional handover in suspend-resume
WO2021003598A1 (en) * 2019-07-05 2021-01-14 Nec Corporation Communication method, device and computer readable medium in wireless communication system

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104039023A (zh) * 2013-03-05 2014-09-10 电信科学技术研究院 一种进行rrc连接重建的方法及用户设备
WO2018203716A1 (ko) * 2017-05-04 2018-11-08 삼성전자 주식회사 단말 자율 핸드오버에서의 측정 리포트 이벤트 운용 및 네트워크 시그널링 방법

Non-Patent Citations (5)

* Cited by examiner, † Cited by third party
Title
ANONYMOUS: "3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification (Release 15)", 3GPP STANDARD; TECHNICAL SPECIFICATION; 3GPP TS 36.331, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. V15.6.0, 29 June 2019 (2019-06-29), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, pages 1 - 960, XP051754475 *
ERICSSON: "Conditional handover failures in NR", 3GPP TSG RAN WG2 #107 R2-1909334, 15 August 2019 (2019-08-15), XP051767136 *
INTEL CORP.: "Failure handling on CHO", 3GPP TSG RAN WG2 MEETING #106 R2-1906292, 3 May 2019 (2019-05-03), XP051710609 *
LG ELECTRONICS INC.: "Consideration on CHO Failure", 3GPP TSG-RAN WG2 MEETING #106 R2-1907998, 3 May 2019 (2019-05-03), XP051712246 *
See also references of EP4037425A4 *

Also Published As

Publication number Publication date
CN115002856B (zh) 2024-02-13
EP4037425A1 (en) 2022-08-03
US20220330108A1 (en) 2022-10-13
CN110915259A (zh) 2020-03-24
EP4037425A4 (en) 2023-06-28
CN110915259B (zh) 2022-06-17
CN115002856A (zh) 2022-09-02
US12127055B2 (en) 2024-10-22

Similar Documents

Publication Publication Date Title
US11452012B2 (en) Method, apparatus for cell handover and user equipment
CN106792987B (zh) 网络选择方法及装置
US10375613B2 (en) Method and device for cell reselection
CN109196909B (zh) 小区切换方法及装置
US11641618B2 (en) Cell access method and apparatus
US12089101B2 (en) Cell handover method and apparatus, handover configuration method and apparatus, and user equipment
US11197192B2 (en) Network connection management method, device and system
WO2020029285A1 (zh) 信息发送、接收方法及装置、基站和用户设备
CN115334582A (zh) 信息传输方法、装置、存储介质及芯片
CN115278760B (zh) 网络测量方法、装置及存储介质
CN115002856B (zh) 链路失败的信息处理方法和电子设备
WO2021232381A1 (zh) 信息发送方法、基站切换方法、信息接收方法以及装置
US11076367B2 (en) Power headroom report transmission method and apparatus
CN109451832B (zh) 无线通信方法、装置及计算机可读存储介质
US11265793B2 (en) Method and apparatus for determining motion state of user equipment
CN109451876B (zh) 信息记录方法和信息记录装置
CN107039054A (zh) 录音方法及装置
CN115348602B (zh) 终端接入方法、装置、存储介质及终端
WO2020237506A1 (zh) 信息配置方法及装置、业务处理方法及装置和基站
CN120547639A (zh) 小区切换方法、装置、电子设备及存储介质
CN115348602A (zh) 终端接入方法、装置、存储介质及终端
CN114786226A (zh) 小区重选方法及装置、存储介质

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 19946919

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

WWE Wipo information: entry into national phase

Ref document number: 2019946919

Country of ref document: EP

ENP Entry into the national phase

Ref document number: 2019946919

Country of ref document: EP

Effective date: 20220428