CN113498134A

CN113498134A - Method and arrangement in a communication node used for wireless communication

Info

Publication number: CN113498134A
Application number: CN202010267337.4A
Authority: CN
Inventors: 张晓博
Original assignee: Shanghai Langbo Communication Technology Co Ltd
Current assignee: Shanghai Langbo Communication Technology Co Ltd
Priority date: 2020-04-08
Filing date: 2020-04-08
Publication date: 2021-10-12
Anticipated expiration: 2040-04-08
Also published as: CN113498134B

Abstract

A method and arrangement in a communication node for wireless communication is disclosed. The communication node determines that a radio connection with a first serving cell fails; generating a first failure-related message; performing a handover for the second serving cell; determining that the handover for the second serving cell failed; generating a second failure-related message; receiving a first signaling; sending a second signaling; the second signaling comprises the second failure-related message; the first failure-related message comprises a first domain, the first domain of the first failure-related message comprising an identification of the first serving cell; a second field of the second failure-related message comprises an identification of the first serving cell; the first field of the second failure-related message comprises an identification of the second serving cell; the connection failure type field of the first failure related message is of a first type, and the connection failure type field of the second failure related message is of a second type.

Description

Method and arrangement in a communication node used for wireless communication

Technical Field

The present application relates to a transmission method and apparatus in a wireless communication system, and more particularly, to a transmission method and apparatus for a radio link failure report.

Background

Radio Link Failure (RLF) reports of a User Equipment (UE) are used for coverage optimization and mobility robustness optimization, and the UE stores the latest RLF or Handover Failure (HOF) related information and indicates RLF report availability at each subsequent RRC (Radio resource Control) connection re-establishment and cell Handover until the network acquires the RLF report or discards the RLF report after 48 hours of RLF. Self-organizing Networks (SON) include network Self-configuration and Self-optimization, and 3GPP (the 3rd Generation Partnership Project) passes through a data collection enhancement Work Item (WI) of NR (new radio, new air interface) SON/MDT (Minimization of Drive Tests) in RAN #86, supports SON data collection characteristics including mobility enhancement optimization and successful handover report; the MDT data collection characteristics are supported, and the characteristics comprise 2-step RACH (Random Access Channel) optimization, RLF (radio link failure) reporting and the like. Release 16 researches standardized work of Conditional Handover (CHO) and DAPS (Dual Active Protocol Stack) in a work project of "NR and LTE (Long Term Evolution) mobility enhancement", supports radio link Recovery (Recovery) through CHO after RLF occurs to UE, and supports DAPS Handover.

Disclosure of Invention

Before Release 16, when the UE has RLF, it keeps in RRC CONNECTED state (RRC _ CONNECTED), selects a cell and performs RRC connection Reestablishment (Reestablishment), and if no suitable cell is selected, enters into RRC IDLE state (RRC _ IDLE). Release 16 introduces CHO and supports the recovery of radio link through CHO, when the cell selected by UE is a CHO candidate cell, executing CHO process, otherwise, executing RRC connection reestablishment. When the UE generates RLF, the UE stores the RLF related information, and when the UE fails to execute CHO after RLF, the RLF related information is cleared and the CHO failure related information is stored. Due to the RLF and CHO failure essentially belonging to the same RLF related process of the UE, if the RLF information is cleared, the network cannot accurately determine whether the RLF occurs in the UE when receiving the RLF report of the UE. If the UE fails to perform the DAPS handover after the source cell generates the RLF in the process of performing the DAPS handover, the UE deletes the related information of the RLF of the source cell and stores the related information of the DAPS handover failure. When a UE experiences two connection failures in the same procedure, the radio connection failure report needs to be enhanced.

In view of the above, the present application provides a solution. In the above description of the problem, a failure scenario is recovered by CHO after RLF as an example; the method and the device are also suitable for the situation that the UE experiences the DAPS handover failure after experiencing the source cell RLF in the DAPS handover process, and the technical effect similar to the situation that the UE experiences the recovery failure through the CHO after the RLF is achieved. In addition, the adoption of a unified solution for different scenarios also helps to reduce hardware complexity and cost.

It should be noted that, in the case of no conflict, the embodiments and features in the embodiments in any node of the present application may be applied to any other node. The embodiments and features of the embodiments of the present application may be combined with each other arbitrarily without conflict.

The application discloses a method in a first node used for wireless communication, characterized by comprising:

determining that a radio connection with a first serving cell fails; in response to said determining that said radio connection with said first serving cell failed, generating a first failure-related message and selecting a second serving cell;

performing a handover for the second serving cell;

determining that the handover for the second serving cell failed; generating a second failure-related message in response to the determination of the handover failure for the second serving cell;

receiving a first signaling; sending a second signaling;

wherein the first signaling is received after the generating of the second failure-related message, the first signaling being used to trigger the second signaling, the second signaling comprising the second failure-related message; the first failure-related message comprises a first domain, the first domain of the first failure-related message comprising an identification of the first serving cell; a second field of the second failure-related message comprises an identification of the first serving cell; the first field of the second failure-related message comprises an identification of the second serving cell; the connection failure type field of the first failure related message is of a first type, and the connection failure type field of the second failure related message is of a second type.

As an embodiment, the problem to be solved by the present application includes: when the UE performs link recovery through CHO after RLF occurs, if CHO failure is experienced again, how the RLF related information of the UE is generated.

As an embodiment, the problem to be solved by the present application includes: when the UE generates RLF, the link recovery is carried out through CHO, and if the UE experiences CHO failure again, the UE reports the RLF related information.

As an embodiment, the problem to be solved by the present application includes: when the UE performs the DAPS handover, if the source cell fails to perform the DAPS handover after the RLF occurs, how the RLF related information of the UE is generated.

As an embodiment, the problem to be solved by the present application includes: when UE executes DAPS switching, if the source cell generates RLF and then fails DAPS switching, how the UE reports RLF related information.

As an embodiment, the characteristics of the above method include: when the UE fails to execute the CHO after RLF, the RLF information and the HOF information are stored.

As an embodiment, the characteristics of the above method include: when the UE executes the DAPS handover, if the source cell fails to perform the DAPS handover after the RLF occurs, the RLF information and the HOF information are stored.

As an example, the benefits of the above method include: when two connection failures occur continuously in the UE, the related information of the first connection failure is kept.

As an example, the benefits of the above method include: the UE may send multiple RLF reports simultaneously.

As an example, the benefits of the above method include: and the network coverage optimization is facilitated.

As an example, the benefits of the above method include: which is advantageous for mobility enhancement. As an example, the benefits of the above method include: more efficient RLF reporting is provided, avoiding uncertainty in the network interpretation of the UE behavior.

According to an aspect of the application, characterized in that the second signaling comprises the first failure related message.

According to one aspect of the present application, characterized in that,

sending a third signaling;

wherein the third signaling comprises a first message used to indicate that the first and second failure-related messages are generated.

According to an aspect of the present application, the first signaling indicates a message to be reported, the second signaling includes the message to be reported, and the message to be reported includes at least one of the first failure related message and the second failure related message.

According to one aspect of the present application, characterized in that,

receiving a fourth signaling;

wherein the fourth signaling comprises configuration information of the second serving cell.

According to one aspect of the present application, characterized in that,

as the response to the determination of the handover failure for the second serving cell, selecting a first target cell, setting a third domain in the second failure-related message as an identifier of the first target cell, and sending a fifth signaling;

wherein the fifth signaling is used to request the connection re-establishment and the first target cell is used for connection re-establishment.

According to one aspect of the present application, a first failure-related message is cleared, and the second failure-related message includes the first failure-related message.

The application discloses a method in a second node used for wireless communication, characterized by comprising:

sending a first signaling;

receiving a second signaling;

wherein, in response to determining that the radio connection with the first serving cell failed, a first failure-related message is generated and the second serving cell is selected; in response to determining that the handover to the second serving cell failed, a second failure-related message is generated; the first signaling is sent after the generating of the second failure-related message, the first signaling being used to trigger the second signaling, the second signaling comprising the second failure-related message; the first failure-related message comprises a first domain, the first domain of the first failure-related message comprising an identification of the first serving cell; a second field of the second failure-related message comprises an identification of the first serving cell; the first field of the second failure-related message comprises an identification of the second serving cell; the connection failure type field of the first failure related message is of a first type, and the connection failure type field of the second failure related message is of a second type.

According to one aspect of the present application, characterized in that,

receiving a third signaling;

According to an aspect of the present application, wherein the fourth signaling comprises configuration information of the second serving cell, and the sender of the fourth signaling comprises the first serving cell.

According to one aspect of the present application, characterized in that a fifth signaling is received;

wherein the fifth signaling is used to request connection re-establishment; in response to said determining that said handover to said second serving cell failed, a first target cell is selected, said first target cell being used for said connection re-establishment, a third field in said second failure related message being set as an identity of said first target cell.

According to one aspect of the application, a first failure-related message is cleared, and the second failure-related message includes the first failure-related message.

The present application discloses a first node for wireless communication, comprising:

a first receiver that determines that a radio connection with a first serving cell has failed; in response to said determining that said radio connection with said first serving cell failed, generating a first failure-related message and selecting a second serving cell;

a first transceiver to perform handover for the second serving cell;

the first receiver determining that the handover for the second serving cell failed; generating a second failure-related message in response to the determination of the handover failure for the second serving cell;

the first transceiver receives a first signaling; sending a second signaling;

The present application discloses a second node for wireless communication, comprising:

a first transmitter for transmitting a first signaling;

a second receiver receiving a second signaling;

As an example, compared with the conventional scheme, the method has the following advantages: in the conventional scheme, the UE can only keep the latest RLF or HOF related information once, and when the RLF or HOF is transmitted again, the RLF or HOF related information stored before is deleted. By means of the solution of the present application,

the UE may generate and store a plurality of RLF-related information;

UE may report multiple RLF reports;

when the execution of CHO fails after the occurrence of RLF or HOF in the UE, the RLF or HOF related information is not deleted;

when the UE performs the DAPS handover, if the source cell fails to perform the DAPS handover after the RLF occurs, the RLF related information of the source cell is not deleted;

favour of network coverage optimization;

is advantageous for mobility enhancement.

Drawings

Other features, objects and advantages of the present application will become more apparent upon reading of the following detailed description of non-limiting embodiments thereof with reference to the accompanying drawings in which:

fig. 1 shows a flow diagram of the transmission of a first signaling and a second signaling according to an embodiment of the application;

FIG. 2 shows a schematic diagram of a network architecture according to an embodiment of the present application;

figure 3 shows a schematic diagram of an embodiment of a radio protocol architecture for the user plane and the control plane according to an embodiment of the present application;

FIG. 4 shows a schematic diagram of a first communication device and a second communication device according to an embodiment of the present application;

FIG. 5 shows a flow diagram of wireless signal transmission according to one embodiment of the present application;

FIG. 6 illustrates a schematic diagram of a first failure-related message and a second failure-related message being generated and transmitted in accordance with one embodiment of the present application;

FIG. 7 illustrates a schematic diagram of a first failure-related message and a second failure-related message being generated and transmitted in accordance with another embodiment of the present application;

fig. 8 shows a schematic diagram of a third signaling first message used to indicate that a first failure-related message and a second failure-related message are generated, according to an embodiment of the application;

fig. 9 shows a schematic diagram of a third signaling of a first message used to indicate that a first failure related message and a second failure related message are generated, according to another embodiment of an embodiment of the application;

fig. 10 shows a schematic diagram of a third signaling that a first message is used to indicate that a first failure related message and a second failure related message are generated according to yet another embodiment of an embodiment of the present application;

fig. 11 shows a schematic diagram of a third signaling of a first message used to indicate that a first failure-related message and a second failure-related message are generated according to yet another embodiment of an embodiment of the present application;

fig. 12 shows an illustration of second signaling comprising a first failure related message and a second failure related message according to an embodiment of the application;

fig. 13 shows a schematic diagram of second signaling comprising a first failure related message and a second failure related message according to another embodiment of the present application;

FIG. 14 shows a block diagram of a processing device for use in a first node according to an embodiment of the present application;

fig. 15 shows a block diagram of a processing arrangement for use in a second node according to an embodiment of the present application.

Detailed Description

The technical solutions of the present application will be further described in detail with reference to the accompanying drawings, and it should be noted that the embodiments and features of the embodiments in the present application can be arbitrarily combined with each other without conflict.

Example 1

Embodiment 1 illustrates a flow chart of transmission of first signaling and second signaling according to an embodiment of the present application, as shown in fig. 1. In fig. 1, each block represents a step, and it is particularly emphasized that the sequence of the blocks in the figure does not represent a chronological relationship between the represented steps.

In embodiment 1, a first node in the present application determines in step 101 that a radio connection with a first serving cell fails; in response to said determining that said radio connection with said first serving cell failed, generating a first failure-related message and selecting a second serving cell; performing a handover for the second serving cell in step 102; determining in step 103 that the handover for the second serving cell failed; generating a second failure-related message in response to the determination of the handover failure for the second serving cell; receiving a first signaling in step 104; sending a second signaling; wherein the first signaling is received after the generating of the second failure-related message, the first signaling being used to trigger the second signaling, the second signaling comprising the second failure-related message; the first failure-related message comprises a first domain, the first domain of the first failure-related message comprising an identification of the first serving cell; a second field of the second failure-related message comprises an identification of the first serving cell; the first field of the second failure-related message comprises an identification of the second serving cell; the connection failure type field of the first failure related message is of a first type, and the connection failure type field of the second failure related message is of a second type.

As one embodiment, the first receiver determines that a radio connection with a first serving cell has failed.

As one embodiment, the first node determines that a radio connection with a first serving cell has failed.

As one embodiment, the first receiver determines that the handover for the second serving cell failed.

As one embodiment, the first node determines that the handover for the second serving cell failed.

For one embodiment, the first serving Cell comprises a Source Cell (Source Cell).

As one embodiment, the first serving Cell includes a Primary Cell (PCell).

For one embodiment, the second serving Cell comprises a Target Cell (Target Cell).

As an embodiment, the second serving cell includes a Conditional Handover (CHO) Candidate cell (Candidate).

As an embodiment, the first serving cell and the second serving cell belong to the same PLMN (Public land mobile network).

As a sub-embodiment of this embodiment, the RAT (Radio Access Technology ) adopted by the PLMN includes NR (New Radio, New air interface).

As a sub-embodiment of this embodiment, the RAT adopted by the PLMN includes LTE (Long Term Evolution).

As one embodiment, the phrase determining that the radio connection with the first serving cell failed comprises: the first node determines that a Radio Link Failure (RLF) occurs between the first node and the first serving cell.

As a sub-embodiment of this embodiment, when a Timer (Timer) T310 expires, the first node determines that the radio link failure occurs with the first serving cell.

As a sub-embodiment of this embodiment, when the timer T312 expires, the first node determines that the radio link failure occurs with the first serving cell.

As a sub-embodiment of this embodiment, when receiving an indication of reaching a maximum number of retransmissions from a Master Cell Group (MCG) RLC (Radio Link Control), it is determined that the Radio Link failure occurs with the first serving Cell.

As a sub-embodiment of this embodiment, when receiving an indication of a maximum number of retransmissions to reach one SRB (Signaling Radio Bearer) or DRB (Data Radio Bearer) from the MCG RLC, it is determined that the Radio link failure occurs with the first serving cell.

As a sub-embodiment of this embodiment, when a Random Access (RA) problem indication is received from a MCG MAC (Medium Access Control) and none of timers T300, T301, T304, T311, and T319 are running, it is determined that the radio link failure occurs with the first serving cell.

As a sub-embodiment of this embodiment, when a random access problem indication from the MCG MAC is received and none of the timers T300, T301, T304, and T311 are running, it is determined that the radio link failure occurs with the first serving cell.

As one embodiment, the phrase determining that the radio connection with the first serving cell failed comprises: it is determined that a Handover Failure (HOF) occurs.

As a sub-embodiment of this embodiment, the handover failure is determined to occur when the timer T304 expires.

As one embodiment, the handover comprises a conventional handover.

As one embodiment, the handover comprises a CHO handover.

As an embodiment, the handover includes a DAPS (Dual Active Protocol Stack) handover.

As an embodiment, the first node is performing the handover when the radio connection failure occurs.

In one embodiment, the first node does not perform the handover when the radio connection failure occurs.

As an example, the radio connection failure occurs during the operation of the timer T304.

For one embodiment, the radio connection failure occurs when the timer T304 is not running.

As an embodiment, the first failure-related message is stored in a variable.

As an embodiment, the first failure-related message is stored in a set of variables.

As an embodiment, the first failure related message is stored in VarRLF-Report.

As an embodiment, in response to the determining that the radio connection with the first serving cell fails, the radio connection failure related message is stored in a VarRLF-Report, and the first failure related message is generated.

As a sub-embodiment of this embodiment, the first failure related message includes all of the VarRLF-Report.

As a sub-embodiment of this embodiment, the first failure related message comprises a portion of the VarRLF-Report.

As an embodiment, the phrase, in response to the determining that the radio connection with the first serving cell failed, generating a first failure-related message and selecting a second serving cell comprises: generating a first failure-related message and selecting a second serving cell when the radio connection failure between the first node and the first serving cell is determined.

As an embodiment, the phrase, in response to the determining that the radio connection with the first serving cell failed, generating a first failure-related message and selecting a second serving cell comprises: when the first node asserts (clear) that the radio connection failure occurred, a first failure related message is generated and a second serving cell is selected.

As one embodiment, the generating the first failure-related message includes: storing (Store) the first failure related message.

As one embodiment, the generating the first failure-related message includes: saving (Save) the first failure related message.

As one embodiment, the generating the first failure-related message includes: setting (Set) the first failure related message.

As one embodiment, the generating the first failure-related message includes: recording (Log) the first failure related message.

As an embodiment, the first failure related message comprises a measurement result of the first serving cell.

As an embodiment, the first failure related message comprises measurement results of neighboring cells of the first serving cell.

As a sub-embodiment of this embodiment, the neighboring cells comprise LTE cells.

As a sub-embodiment of this embodiment, the neighboring cells comprise NR cells.

For one embodiment, the first failure-related message includes a connection failure type.

As an embodiment, the first failure-related message comprises a reason for the connection failure.

As a sub-embodiment of this embodiment, the reason for the connection failure comprises a basis for determining a radio connection failure with the first serving cell.

As a sub-embodiment of this embodiment, the reason for the connection failure includes t 310-expires.

As a sub-embodiment of this embodiment, the reason for the connection failure includes t 312-expires.

As a sub-embodiment of this embodiment, the reason for the connection failure includes randomaccessfolblem.

As a sub-embodiment of this embodiment, the reason for the connection failure includes rlc-MaxNumRetx.

As a sub-embodiment of this embodiment, the reason for the connection failure includes a beamFailureRecoveryFailure.

As an embodiment, the first failure related message comprises an identification of the first serving cell.

As an embodiment, the first failure related message comprises an identification of the second serving cell.

As one embodiment, the first failure-related message includes a message related to the radio connection failure.

For one embodiment, the first failure-related message comprises a VarRLF-Report.

As an embodiment, the first failure-related message includes all of the information stored in the VarRLF-Report.

As an embodiment, the first failure related message comprises part of the information stored in the VarRLF-Report.

For one embodiment, the first failure-related message comprises a measResultLastServCell.

As an embodiment, the first failure related message comprises measResultNeighCells.

As an embodiment, the first failure related message comprises measResultListNR.

As an embodiment, the first failure related message comprises measResultListEUTRA.

As an embodiment, the first failure-related message includes a connectionFailureType.

For one embodiment, the first failure-related message includes rlf-Cause.

As an embodiment, the first failure related message comprises a previousps cellid.

As an embodiment, the first failure related message comprises a failedPCellId.

As one embodiment, the phrase selecting a second serving cell comprises: determining the second serving cell.

As one embodiment, the phrase selecting a second serving cell comprises: performing a cell selection procedure, the cell selected by the cell selection procedure being the second serving cell.

As one embodiment, the second serving cell comprises a CHO candidate cell.

As one embodiment, the second serving cell includes a target cell of the handover.

As one embodiment, the phrase performing a handover for the second serving cell comprises: performing RRC (Radio Resource Control) connection Reconfiguration (Reconfiguration) for the second serving cell.

As one embodiment, the phrase performing a handover for the second serving cell comprises: performing RRC connection Reestablishment (Reestabilishment) for the second serving cell.

As one embodiment, the phrase performing a handover for the second serving cell comprises: RRC connection establishment is monitored.

As one embodiment, the performing the handover for the second serving cell comprises: and acquiring uplink synchronization with the second serving cell.

As one embodiment, the performing the handover for the second serving cell comprises: applying the RRC configuration of the second serving cell.

As one embodiment, the phrase performing a handover for the second serving cell comprises: initiating an RRC connection setup (Establishment) for the second serving cell.

As one embodiment, the phrase performing a handover for the second serving cell comprises: a random access procedure is initiated.

As a sub-embodiment of this embodiment, the random access procedure includes four-step (4-step) random access.

As a sub-embodiment of this embodiment, the random access procedure comprises a two-step (2-step) random access.

As one embodiment, the phrase performing a handover for the second serving cell comprises: an RRC connection setup request is sent.

As one embodiment, the phrase performing a handover for the second serving cell comprises: message 1(msg1) and message 3(msg3) are sent.

As one embodiment, the phrase performing a handover for the second serving cell comprises: message a (msga) is transmitted.

As one embodiment, the phrase performing a handover for the second serving cell comprises: message b (msgb) is received.

As one embodiment, the phrase performing a handover for the second serving cell comprises: message 1(msg1) is sent.

As one embodiment, the phrase performing a handover for the second serving cell comprises: message 2(msg2) is received.

As one embodiment, the phrase performing a handover for the second serving cell comprises: message 3(msg3) is sent.

As one embodiment, the phrase performing a handover for the second serving cell comprises: message 4(msg4) is received.

As an embodiment, when the first node performs the handover for the second serving cell, it leaves the first serving cell and synchronizes to the second serving cell.

As an embodiment, when the first node performs the handover for the second serving cell, it does not leave the first serving cell and synchronizes to the second serving cell.

As a sub-embodiment of this embodiment, the not leaving the first serving cell includes: not releasing SRB resources of the first serving cell.

As a sub-embodiment of this embodiment, the not leaving the first serving cell includes: reserving RRC configuration information of the first serving cell.

As one embodiment, the phrase determining that the handover for the second serving cell failed comprises: determining that a Radio Link Failure (RLF) occurs with the second serving cell.

As one embodiment, the phrase determining that the handover for the second serving cell failed comprises: determining that a handover failure (HOF) occurs with the second serving cell.

As one embodiment, the phrase determining that the handover for the second serving cell failed comprises: the random access procedure initiated to the second serving cell fails.

As one embodiment, the phrase determining that the handover for the second serving cell failed comprises: the RRC connection establishment request initiated to the second serving cell is not responded to.

As one embodiment, the phrase determining that the handover for the second serving cell failed comprises: the first timer expires.

As a sub-embodiment of this embodiment, the first timer includes T304, and when the timer T304 expires, the first node determines that a handover failure (HOF) occurs with the second serving cell.

As an embodiment, the second failure-related message is stored in a variable.

As an embodiment, the second failure-related message is stored in a set of variables.

As an embodiment, the second failure related message is stored in VarRLF-Report.

As an embodiment, the first failure-related message is cleared when the second failure-related message is generated.

As an embodiment, the first failure-related message is not cleared when the second failure-related message is generated.

As an embodiment, in response to the determining the handover failure for the second serving cell, the radio connection failure related message is stored to a VarRLF-Report, and the second failure related message is generated.

As a sub-embodiment of this embodiment, the second failure related message includes all of the VarRLF-Report.

As a sub-embodiment of this embodiment, the second failure related message comprises a portion of the VarRLF-Report.

As an embodiment, in response to the determining the handover failure for the second serving cell, generating a second failure-related message comprises: generating the second failure-related message when the handover failure for the second serving cell is determined.

As one embodiment, said determining said handover failure for said second serving cell in response comprises: when the timer T304 expires, a second failure-related message is generated.

As an embodiment, the generating the second failure-related message includes: storing (Store) the second failure related message.

As an embodiment, the generating the second failure-related message includes: saving (Save) the second failure related message.

As an embodiment, the generating the second failure-related message includes: setting (Set) the second failure related message.

As an embodiment, the generating the second failure-related message includes: recording (Log) the second failure related message.

As an embodiment, the second failure related message is used to store a message related to the handover failure for the second serving cell.

For one embodiment, the second failure-related message comprises a VarRLF-Report.

For one embodiment, the second failure-related message includes information stored in a VarRLF-Report.

For one embodiment, the second failure-related message includes all of the VarRLF-Report.

For one embodiment, the second failure related message includes a portion of a VarRLF-Report.

As an embodiment, the second failure related message comprises a measurement result of the first serving cell.

As an embodiment, the second failure related message comprises measurement results of neighboring cells of the first serving cell.

For one embodiment, the second failure-related message includes a connection failure type.

As an embodiment, the second failure-related message includes a reason for the connection failure.

As a sub-embodiment of this embodiment, the reason for the connection failure includes a basis for determining a radio connection failure with the second serving cell.

As a sub-embodiment of this embodiment, the reason for the connection failure includes T304-Expiry.

As an embodiment, the second failure-related message includes an identification of the first serving cell.

As an embodiment, the second failure related message includes an identification of the second serving cell.

As one embodiment, the second failure-related message includes a message related to the radio connection failure.

For one embodiment, the second failure-related message comprises a measResultLastServCell.

As an embodiment, the second failure related message comprises measResultNeighCells.

As an embodiment, the second failure related message comprises measResultListNR.

As an embodiment, the second failure related message comprises measResultListEUTRA.

As an embodiment, the second failure-related message includes a connectionFailureType.

For one embodiment, the second failure-related message includes rlf-Cause.

As an embodiment, the second failure related message comprises a previousps cellid.

As an embodiment, the second failure related message comprises a failedPCellId.

As one embodiment, the sender of the first signaling comprises a maintaining base station of the first serving cell.

As an embodiment, the sender of the first signaling comprises a maintaining base station of a current serving cell of the first node.

As an embodiment, the first signaling is transmitted over an air interface.

As an embodiment, the first signaling is transmitted over a wireless interface.

As an embodiment, the first signaling is transmitted through higher layer signaling.

As one embodiment, the first signaling comprises higher layer signaling.

As an embodiment, the first signaling comprises all or part of higher layer signaling.

For one embodiment, the first signaling comprises an RRC message.

As an embodiment, the first signaling comprises all or part of an IE of an RRC message.

As an embodiment, the first signaling comprises all or part of a field in one IE of an RRC message.

For one embodiment, the first signaling comprises a Downlink (DL) signaling.

For one embodiment, the signaling radio bearer for the first signaling comprises SRB 1.

As an embodiment, the logical channel carrying the first signaling comprises a DCCH.

As an embodiment, the first signaling is used to trigger the sending of the second signaling.

As an embodiment, the first signaling is used to request user equipment Information (UE Information).

As an embodiment, the first signaling is used for requesting (Request) radio link failure related information.

As an embodiment, the first signaling is used to determine to request the radio link failure recovery related message.

As an embodiment, the first signaling is used to determine that a successful handover-related message is requested.

As an embodiment, the first signaling includes a UEInformationRequest message.

As an embodiment, the first signaling includes an RLF-ReportReq IE.

For one embodiment, the first signaling includes an rlf-ReportReq field.

As an embodiment, the first signaling includes a success handover-report req field.

As an embodiment, the first signaling includes an rlfrecoverage-ReportReq field.

As one embodiment, said receiving said sentence after said generating said second failure-related message comprises: the first signaling is received when the second failure-related message is generated.

As one embodiment, said receiving said sentence after said generating said second failure-related message comprises: the first signaling is received when the first node determines that the radio connection with the first serving cell fails and determines that the handover to the second serving cell fails.

As one embodiment, the sentence where the first signaling is used to trigger the second signaling comprises: and sending the second signaling as a response to receiving the first signaling.

As one embodiment, the sentence where the first signaling is used to trigger the second signaling comprises: the first signaling is used for acknowledging the second signaling.

As one embodiment, the sentence where the first signaling is used to trigger the second signaling comprises: the second signaling is a Response (Response) to the first signaling.

As an embodiment, the receiver of the second signaling is the same as the sender of the first signaling.

As an embodiment, the second signaling is transmitted over an air interface.

As an embodiment, the second signaling is transmitted over a wireless interface.

As an embodiment, the second signaling is transmitted through higher layer signaling.

As an embodiment, the second signaling comprises higher layer signaling.

As an embodiment, the second signaling comprises all or part of a higher layer signaling.

As one embodiment, the second signaling comprises an RRC message.

As an embodiment, the second signaling includes all or part of an IE of an RRC message.

As an embodiment, the second signaling comprises all or part of a field in an IE of an RRC message.

As an embodiment, the second signaling includes an Uplink (UL) message.

As an embodiment, the second signaling is used for a user equipment information response.

As an embodiment, the second signaling is used for reporting a radio link failure related message.

For one embodiment, the signaling radio bearer for the second signaling comprises SRB 1.

As an embodiment, the signaling Radio Bearer of the second signaling includes SRB2 (signaling Radio Bearer 2).

As an embodiment, the logical channel carrying the second signaling comprises a DCCH.

As an embodiment, the second signaling comprises a UEInformationResponse message.

As an embodiment, the second signaling includes information stored in VarRLF-Report.

For one embodiment, the second signaling includes an RLF-Report field.

For one embodiment, the second signaling includes an nr-RLF-Report field.

For one embodiment, the second signaling includes an eutra-RLF-Report field.

For one embodiment, the second signaling includes rlf-Report field.

As an embodiment, the first signaling includes a success handover-Report field.

As an embodiment, the first signaling includes an rlfrecoverage-Report field.

For one embodiment, the second signaling includes a FailureInformation message

As an embodiment, the second signaling comprises a failurenfodaps IE.

As an embodiment, the second signaling includes a failurenfodaps domain.

As an embodiment, the second signaling including the second failure-related message includes: the second failure-related message includes one or more fields in the second signaling.

As an embodiment, the second signaling including the second failure-related message includes: the second failure-related message includes one or more IEs in the second signaling.

As an embodiment, the second signaling is used to indicate a second failure related message.

As an embodiment, the second signaling is used to determine a second failure related message.

As an embodiment, the second signaling includes all of the second failure-related message.

As an embodiment, the second signaling comprises part of the second failure related message.

For one embodiment, the phrase the first failure-related message including a first field includes: the first field is one field in the first failure-related message.

For one embodiment, the phrase the first failure-related message including a first field includes: the first failure-related message is used to determine the first domain.

As one embodiment, the phrase that the first field of the first failure-related message includes an identification of the first serving cell includes: the first field of the first failure-related message is used to determine a cell identity of the first serving cell.

As one embodiment, the phrase that the first field of the first failure-related message includes an identification of the first serving cell includes: the first field of the first failure related message is used to indicate a cell identity of the first serving cell.

As one embodiment, the phrase that the first field of the first failure-related message includes an identification of the first serving cell includes: the first field of the first failure related message is set to a cell identity of the first serving cell.

For one embodiment, the first field of the first failure-related message comprises a field in a VarRLF-Report.

As a sub-implementation of this embodiment, the VarRLF-Report includes an nr-RLF-Report.

As a sub-implementation of this embodiment, the VarRLF-Report includes an eutra-RLF-Report.

For one embodiment, the first field of the first failure-related message comprises one field of an RLF-Report.

As an embodiment, said first field of said first failure-related message comprises a field in a UEInformationResponse.

As an embodiment, the first field of the first failure related message is used to indicate a Source primary cell (Source PCell) at the last handover, the Source primary cell including the first serving cell.

As one embodiment, the first field of the first failure-related message includes a Cell Identity (Cell ID).

As one embodiment, the Cell Identity includes a Physical Cell Identity (PCI).

As one embodiment, the Cell Identity includes a Global Cell Identity (CGI).

As one embodiment, the Cell Identity includes an Evolved Global Cell Identity (ECGI).

As an embodiment, the cell identifier includes a Tracking Area identifier (TAC).

As an embodiment, the cell identity comprises CGI-Info-loggindedailed.

As an embodiment, the cell identity comprises a CGI-Info-loging.

As an embodiment, the cell identity comprises CGI-Info-loggindedailed.

As one embodiment, the cell identity includes physcellld.

As an embodiment, the cell identity comprises ARFCN-ValueNR.

As an embodiment, the cell Identity includes plmn-Identity.

As an embodiment, the cell identifier includes cellIdentity.

For one embodiment, the first field of the first failure-related message comprises a PLMN.

As an embodiment, the first field of the first failure related message comprises a previousps cellid.

As an embodiment, the first field of the first failure related message comprises a failedPCellId.

As an embodiment, the first field of the first failure-related message comprises cellGlobalId.

As an embodiment, the first field of the first failure-related message comprises a pci-arfcn.

As one embodiment, the first field of the first failure-related message comprises a physcellld.

As one embodiment, the first field of the first failure-related message comprises carrierFreq.

As an embodiment, when the first type comprises rlf, the first field of the first failure related message comprises a failedPCellId, the failedPCellId being used to indicate the identity of the first serving cell.

As a sub-embodiment of this embodiment, the second field of the first failure related message includes previousps cellid, which is used to indicate the cell identity of the target cell at the last handover.

As one embodiment, when the first type includes hof, the first domain includes a previousps cellid used to indicate the identity of the first serving cell.

As a sub-embodiment of this embodiment, the second field of the first failure related message comprises a failedPCellId, which is used to indicate the identity of the second serving cell.

As an embodiment, the phrase that the second field of the second failure-related message includes the identification of the first serving cell includes: the second field of the second failure-related message is used to determine an identity of the first serving cell.

As an embodiment, the phrase that the second field of the second failure-related message includes the identification of the first serving cell includes: the second field of the second failure-related message is used to indicate an identity of the first serving cell.

As an embodiment, the phrase that the second field of the second failure-related message includes the identification of the first serving cell includes: the second field of the second failure related message is set to the identity of the first serving cell.

For one embodiment, the second field of the second failure-related message comprises a field in a VarRLF-Report.

For one embodiment, the second field of the second failure-related message comprises one field of an RLF-Report.

As an embodiment, the second field of the second failure-related message comprises a field in a UEInformationResponse.

As an embodiment, the second field of the second failure related message is used to indicate a Source primary cell (Source PCell) at the last handover.

As a sub-embodiment of this embodiment, the source primary cell comprises the first serving cell.

As one embodiment, the second field of the second failure-related message includes a Cell Identity (Cell ID).

As an embodiment, the second field of the second failure-related message includes a Tracking Area identity (TAC).

For one embodiment, the second field of the second failure-related message comprises a PLMN.

As an embodiment, the second field of the second failure related message comprises a previousps cellid.

As an embodiment, the second field of the second failure related message comprises a failedPCellId.

As an embodiment, the second field of the second failure-related message comprises cellGlobalId.

As an embodiment, the second field of the second failure-related message comprises a pci-arfcn.

As one embodiment, the second field of the second failure-related message comprises a physcellld.

As one embodiment, the second field of the second failure-related message comprises carrierFreq.

As an embodiment, the second failure-related message includes a connection failure reason.

As a sub-embodiment of this embodiment, the connection failure cause includes a basis for determining a radio connection failure with the first serving cell.

As an embodiment, the second failure related message includes a cell identity of the first serving cell.

As an embodiment, the second failure related message includes a cell identity of the second serving cell.

For one embodiment, the second failure-related message includes rlf-Cause.

As an embodiment, the second failure related message comprises a failedPCellId.

As an embodiment, the second failure-related message is stored in a variable.

As an embodiment, the measurement result of the first serving cell in the first failure-related message is the same as the measurement result of the first serving cell in the second failure-related message.

As an embodiment, the measurement result of the first serving cell in the first failure-related message is different from the measurement result of the first serving cell in the second failure-related message.

As an embodiment, the measurement result of the neighbor cell of the first serving cell in the first failure related message is the same as the measurement result of the neighbor cell of the first serving cell in the second failure related message.

As an embodiment, the measurement result of the neighbor cell of the first serving cell in the first failure related message is different from the measurement result of the neighbor cell of the first serving cell in the second failure related message.

As an embodiment, the connection failure type in the first failure-related message is the same as the connection failure type in the second failure-related message.

As an embodiment, the connection failure type in the first failure-related message is different from the connection failure type in the second failure-related message.

As an embodiment, the connection failure cause in the first failure-related message is the same as the connection failure cause in the second failure-related message.

As an embodiment, the connection failure cause in the first failure-related message is different from the connection failure cause in the second failure-related message.

As one embodiment, the phrase that the first field of the second failure-related message includes the identity of the first serving cell includes: the second field of the second failure-related message is used to determine a cell identity of the first serving cell.

As one embodiment, the phrase that the first field of the second failure-related message includes the identity of the first serving cell includes: the second field of the second failure-related message is used to indicate a cell identity of the first serving cell.

As one embodiment, the phrase that the first field of the second failure-related message includes the identity of the first serving cell includes: the second field of the second failure-related message is set to a cell identity of the first serving cell.

For one embodiment, the first field of the second failure-related message comprises a field in a VarRLF-Report.

For one embodiment, the first field of the second failure-related message comprises one field of an RLF-Report.

As an embodiment, the first field of the second failure-related message comprises a field in a UEInformationResponse.

As an embodiment, the first field of the second failure related message is used to indicate a Source primary cell (Source PCell) at the last handover.

As an embodiment, the first field of the second failure-related message includes a cell identity.

As an embodiment, the first field of the second failure-related message comprises a tracking area identification.

For one embodiment, the first field of the second failure-related message comprises a PLMN.

As an embodiment, the first field of the second failure related message comprises a previousps cellid.

As an embodiment, the first field of the second failure related message comprises a failedPCellId.

As an embodiment, the first field of the second failure-related message comprises cellGlobalId.

As an embodiment, the first field of the second failure-related message comprises a pci-arfcn.

As one embodiment, the first field of the second failure-related message comprises a physcellld.

As one embodiment, the first field of the second failure-related message comprises carrierFreq.

For one embodiment, the connection failure type field includes a failureType field.

For one embodiment, the connection failure type field includes a connectionFailureType field.

As an embodiment, the connection failure type field is used to indicate the type of the connection failure.

As one embodiment, the connection failure type field is used to determine the type of the connection failure.

For one embodiment, the type of the connection failure includes rlf.

For one embodiment, the type of the connection failure includes hof.

As a sub-embodiment of this embodiment, the handover failure comprises a normal handover failure.

As a sub-embodiment of this embodiment, the handover failure includes a conditional handover failure.

As a sub-embodiment of this embodiment, the handover failure comprises a DAPS handover failure.

As one embodiment, the type of the connection failure comprises a daps-failure.

As one example, the type of the connection failure includes rlf-cho-failure.

As one example, the type of the connection failure includes hof-cho-failure.

As one embodiment, the type of the connection failure includes source-rlf-daps-failure.

For one embodiment, the first type includes a value of the connection failure type field.

As an embodiment, the second type comprises a value of the connection failure type field.

As an embodiment, the first type is the same as the second type.

As an embodiment, the first type is different from the second type.

As one embodiment, the first type includes hof and the second type includes hof.

As one embodiment, the first type includes rlf and the second type includes hof.

For one embodiment, the first type includes rlf and the second type includes daps-failure.

As an embodiment, the first type includes rlf and the second type includes cho-failure.

As an embodiment, the first type includes hof and the second type includes cho-failure.

As an example, the names in the present application may be changed to names corresponding to the functions thereof, thereby achieving the same technical effects as the names in the present application.

As an example, the upper and lower case letters in the names of signaling, IE, field and value in the present application can be interchanged to achieve the same technical effect as the names in the present application.

Example 2

Embodiment 2 illustrates a schematic diagram of a network architecture according to an embodiment of the present application, as shown in fig. 2. Fig. 2 illustrates a diagram of a network architecture 200 of a 5G NR (New Radio, New air interface), LTE (Long-Term Evolution), and LTE-a (Long-Term Evolution-Advanced) system. The 5G NR or LTE network architecture 200 may be referred to as a 5GS (5G System)/EPS (evolved packet System) 200 or some other suitable terminology. The 5GS/EPS 200 may include one or more UEs (user equipment) 201, NG-RANs (next generation radio access networks) 202, 5 GCs (5G Core networks )/EPCs (Evolved Packet cores) 210, HSS (Home Subscriber Server)/UDMs (Unified Data Management) 220, and internet services 230. The 5GS/EPS may interconnect with other access networks, but these entities/interfaces are not shown for simplicity. As shown, the 5GS/EPS provides packet switched services, however those skilled in the art will readily appreciate that the various concepts presented throughout this application may be extended to networks providing circuit switched services or other cellular networks. The NG-RAN includes NR node b (gNB)203 and other gnbs 204. The gNB203 provides user and control plane protocol termination towards the UE 201. The gnbs 203 may be connected to other gnbs 204 via an Xn interface (e.g., backhaul). The gNB203 may also be referred to as a base station, a base transceiver station, a radio base station, a radio transceiver, a transceiver function, a Basic Service Set (BSS), an Extended Service Set (ESS), a TRP (transmitting receiving node), or some other suitable terminology. The gNB203 provides the UE201 with an access point to the 5GC/EPC 210. Examples of the UE201 include a cellular phone, a smart phone, a Session Initiation Protocol (SIP) phone, a laptop, a Personal Digital Assistant (PDA), a satellite radio, non-terrestrial base station communications, satellite mobile communications, a global positioning system, a multimedia device, a video device, a digital audio player (e.g., MP3 player), a camera, a game console, a drone, an aircraft, a narrowband internet of things device, a machine type communication device, a terrestrial vehicle, an automobile, a wearable device, or any other similar functioning device. Those skilled in the art may also refer to UE201 as a mobile station, a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless communication device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a user agent, a mobile client, a client, or some other suitable terminology. The gNB203 is connected to the 5GC/EPC210 through an S1/NG interface. The 5GC/EPC210 includes MME (Mobility Management Entity)/AMF (Authentication Management field)/SMF (Session Management Function) 211, other MME/AMF/SMF214, S-GW (serving Gateway)/UPF (User Plane Function) 212, and P-GW (Packet data network Gateway)/UPF 213. The MME/AMF/SMF211 is a control node that handles signaling between the UE201 and the 5GC/EPC 210. In general, the MME/AMF/SMF211 provides bearer and connection management. All user IP (Internet protocol) packets are transported through the S-GW/UPF212, which S-GW/UPF212 itself is connected to the P-GW/UPF 213. The P-GW provides UE IP address allocation as well as other functions. The P-GW/UPF213 is connected to the internet service 230. The internet service 230 includes an operator-corresponding internet protocol service, and may specifically include the internet, an intranet, an IMS (IP Multimedia Subsystem), and a packet-switched streaming service.

As an embodiment, the UE201 corresponds to the first node in this application.

As an embodiment, the UE201 supports transmission in a Non-terrestrial network (NTN).

As an embodiment, the UE201 supports transmission in a large delay-difference network.

As an embodiment, the UE201 supports transmission of a Terrestrial Network (TN).

As an embodiment, the UE201 supports Dual Connectivity (DC) transmission.

As an embodiment, the UE201 supports the transmission of DAPS (Dual Active Protocol Stack).

As an embodiment, the UE201 is a User Equipment (UE).

As an embodiment, the UE201 is a terminal equipment (end).

As an embodiment, the gNB203 corresponds to the second node in this application.

As an embodiment, the gNB203 corresponds to the third node in the present application.

As one embodiment, the gNB203 supports transmissions over a non-terrestrial network (NTN).

As an embodiment, the gNB203 supports transmission in large latency difference networks.

As one embodiment, the gNB203 supports transmissions of a Terrestrial Network (TN).

As one embodiment, the gNB203 supports Dual Connectivity (DC) transmission.

As an example, the gNB203 is a macro cellular (MarcoCellular) base station.

As an embodiment, the gNB203 is a Micro Cell (Micro Cell) base station.

As an embodiment, the gNB203 is a pico cell (PicoCell) base station.

As an embodiment, the gNB203 is a home base station (Femtocell).

Example 3

Embodiment 3 shows a schematic diagram of an embodiment of a radio protocol architecture for the user plane and the control plane according to the present application, as shown in fig. 3. Fig. 3 is a schematic diagram illustrating an embodiment of a radio protocol architecture for the user plane 350 and the control plane 300, fig. 3 showing the radio protocol architecture for the control plane 300 with three layers: layer 1, layer 2 and layer 3. Layer 1(L1 layer) is the lowest layer and implements various PHY (physical layer) signal processing functions. The L1 layer will be referred to herein as PHY 301. Above the PHY301, a layer 2(L2 layer) 305 includes a MAC (Medium Access Control) sublayer 302, an RLC (Radio Link Control Protocol) sublayer 303, and a PDCP (Packet Data Convergence Protocol) sublayer 304. The PDCP sublayer 304 provides multiplexing between different radio bearers and logical channels. The PDCP sublayer 304 also provides security by ciphering packets and provides handover support. The RLC sublayer 303 provides segmentation and reassembly of upper layer packets, retransmission of lost packets, and reordering of packets to compensate for out-of-order reception due to HARQ. The MAC sublayer 302 provides multiplexing between logical and transport channels. The MAC sublayer 302 is also responsible for allocating various radio resources (e.g., resource blocks) in one cell. The MAC sublayer 302 is also responsible for HARQ operations. The RRC (Radio Resource Control) sublayer 306 in layer 3 (layer L3) in the Control plane 300 is responsible for obtaining Radio resources (i.e., Radio bearers) and configuring the lower layers using RRC signaling. The radio protocol architecture of the user plane 350, which includes layer 1(L1 layer) and layer 2(L2 layer), is substantially the same in the user plane 350 as the corresponding layers and sublayers in the control plane 300 for the physical layer 351, the PDCP sublayer 354 in the L2 layer 355, the RLC sublayer 353 in the L2 layer 355, and the MAC sublayer 352 in the L2 layer 355, but the PDCP sublayer 354 also provides header compression for upper layer packets to reduce radio transmission overhead. The L2 layer 355 in the user plane 350 further includes an SDAP (Service Data Adaptation Protocol) sublayer 356, and the SDAP sublayer 356 is responsible for mapping between QoS streams and Data Radio Bearers (DRBs) to support diversity of services.

As an example, the wireless protocol architecture in fig. 3 is applicable to the first node in this application.

As an example, the radio protocol architecture in fig. 3 is applicable to the second node in this application.

As an example, the radio protocol architecture in fig. 3 is applicable to the third node in the present application.

As an embodiment, the first signaling in this application is generated in the RRC 306.

As an embodiment, the second signaling in this application is generated in the RRC 306.

As an embodiment, the third signaling in this application is generated in the RRC 306.

As an embodiment, the fourth signaling in this application is generated in the RRC 306.

As an embodiment, the fifth signaling in this application is generated in the RRC 306.

Example 4

Embodiment 4 shows a schematic diagram of a first communication device and a second communication device according to the present application, as shown in fig. 4. Fig. 4 is a block diagram of a first communication device 450 and a second communication device 410 communicating with each other in an access network.

The first communications device 450 includes a controller/processor 459, a memory 460, a data source 467, a transmit processor 468, a receive processor 456, a multi-antenna transmit processor 457, a multi-antenna receive processor 458, a transmitter/receiver 454, and an antenna 452.

The second communication device 410 includes a controller/processor 475, a memory 476, a receive processor 470, a transmit processor 416, a multiple antenna receive processor 472, a multiple antenna transmit processor 471, a transmitter/receiver 418, and an antenna 420.

In the transmission from the second communication device 410 to the first communication device 450, at the second communication device 410, upper layer data packets from the core network are provided to the controller/processor 475. The controller/processor 475 implements the functionality of layer L2. In transmissions from the second communications device 410 to the first communications device 450, the controller/processor 475 provides header compression, encryption, packet segmentation and reordering, multiplexing between logical and transport channels, and radio resource allocation to the first communications device 450 based on various priority metrics. The controller/processor 475 is also responsible for retransmission of lost packets, and signaling to the first communication device 450. The transmit processor 416 and the multi-antenna transmit processor 471 implement various signal processing functions for the L1 layer (i.e., the physical layer). The transmit processor 416 implements coding and interleaving to facilitate Forward Error Correction (FEC) at the second communication device 410, as well as mapping of signal constellation based on various modulation schemes (e.g., Binary Phase Shift Keying (BPSK), Quadrature Phase Shift Keying (QPSK), M-phase shift keying (M-PSK), M-quadrature amplitude modulation (M-QAM)). The multi-antenna transmit processor 471 performs digital spatial precoding, including codebook-based precoding and non-codebook based precoding, and beamforming processing on the coded and modulated symbols to generate one or more spatial streams. Transmit processor 416 then maps each spatial stream to subcarriers, multiplexes with reference signals (e.g., pilots) in the time and/or frequency domain, and then uses an Inverse Fast Fourier Transform (IFFT) to generate the physical channels carrying the time-domain multicarrier symbol streams. The multi-antenna transmit processor 471 then performs transmit analog precoding/beamforming operations on the time domain multi-carrier symbol stream. Each transmitter 418 converts the baseband multicarrier symbol stream provided by the multi-antenna transmit processor 471 into a radio frequency stream that is then provided to a different antenna 420.

In a transmission from the second communications apparatus 410 to the first communications apparatus 450, each receiver 454 receives a signal through its respective antenna 452 at the first communications apparatus 450. Each receiver 454 recovers information modulated onto a radio frequency carrier and converts the radio frequency stream into a baseband multi-carrier symbol stream that is provided to a receive processor 456. Receive processor 456 and multi-antenna receive processor 458 implement the various signal processing functions of the L1 layer. A multi-antenna receive processor 458 performs receive analog precoding/beamforming operations on the baseband multi-carrier symbol stream from the receiver 454. Receive processor 456 converts the baseband multicarrier symbol stream after the receive analog precoding/beamforming operation from the time domain to the frequency domain using a Fast Fourier Transform (FFT). In the frequency domain, the physical layer data signals and the reference signals to be used for channel estimation are demultiplexed by the receive processor 456, and the data signals are subjected to multi-antenna detection in the multi-antenna receive processor 458 to recover any spatial streams destined for the first communication device 450. The symbols on each spatial stream are demodulated and recovered at a receive processor 456 and soft decisions are generated. The receive processor 456 then decodes and deinterleaves the soft decisions to recover the upper layer data and control signals transmitted by the second communications device 410 on the physical channel. The upper layer data and control signals are then provided to a controller/processor 459. The controller/processor 459 implements the functionality of the L2 layer. The controller/processor 459 may be associated with a memory 460 that stores program codes and data. Memory 460 may be referred to as a computer-readable medium. In transmissions from the second communications device 410 to the second communications device 450, the controller/processor 459 provides demultiplexing between transport and logical channels, packet reassembly, deciphering, header decompression, control signal processing to recover upper layer packets from the core network. The upper layer packet is then provided to all protocol layers above the L2 layer. Various control signals may also be provided to L3 for L3 processing.

In a transmission from the first communications device 450 to the second communications device 410, a data source 467 is used at the first communications device 450 to provide upper layer data packets to a controller/processor 459. Data source 467 represents all protocol layers above the L2 layer. Similar to the send function at the second communications apparatus 410 described in the transmission from the second communications apparatus 410 to the first communications apparatus 450, the controller/processor 459 implements header compression, encryption, packet segmentation and reordering, and multiplexing between logical and transport channels based on radio resource allocation, implementing L2 layer functions for the user plane and control plane. The controller/processor 459 is also responsible for retransmission of lost packets and signaling to said second communications device 410. A transmit processor 468 performs modulation mapping, channel coding, and digital multi-antenna spatial precoding by a multi-antenna transmit processor 457 including codebook-based precoding and non-codebook based precoding, and beamforming, and the transmit processor 468 then modulates the resulting spatial streams into multi-carrier/single-carrier symbol streams, which are provided to different antennas 452 via a transmitter 454 after analog precoding/beamforming in the multi-antenna transmit processor 457. Each transmitter 454 first converts the baseband symbol stream provided by the multi-antenna transmit processor 457 into a radio frequency symbol stream and provides the radio frequency symbol stream to the antenna 452.

In a transmission from the first communication device 450 to the second communication device 410, the functionality at the second communication device 410 is similar to the receiving functionality at the first communication device 450 described in the transmission from the second communication device 410 to the first communication device 450. Each receiver 418 receives an rf signal through its respective antenna 420, converts the received rf signal to a baseband signal, and provides the baseband signal to a multi-antenna receive processor 472 and a receive processor 470. The receive processor 470 and the multiple antenna receive processor 472 collectively implement the functionality of the L1 layer. Controller/processor 475 implements the L2 layer functions. The controller/processor 475 can be associated with a memory 476 that stores program codes and data. Memory 476 may be referred to as a computer-readable medium. In transmission from the first communications device 450 to the second communications device 410, the controller/processor 475 provides demultiplexing between transport and logical channels, packet reassembly, deciphering, header decompression, control signal processing to recover upper layer packets from the UE 450. Upper layer data packets from the controller/processor 475 may be provided to a core network.

As an embodiment, the first communication device 450 includes: at least one processor and at least one memory including computer program code; the at least one memory and the computer program code configured to, for use with the at least one processor, the first communication device 450 at least: determining that a radio connection with a first serving cell fails; in response to said determining that said radio connection with said first serving cell failed, generating a first failure-related message and selecting a second serving cell; performing a handover for the second serving cell; determining that the handover for the second serving cell failed; generating a second failure-related message in response to the determination of the handover failure for the second serving cell; receiving a first signaling; sending a second signaling; wherein the first signaling is received after the generating of the second failure-related message, the first signaling being used to trigger the second signaling, the second signaling comprising the second failure-related message; the first failure-related message comprises a first domain, the first domain of the first failure-related message comprising an identification of the first serving cell; a second field of the second failure-related message comprises an identification of the first serving cell; the first field of the second failure-related message comprises an identification of the second serving cell; the connection failure type field of the first failure related message is of a first type, and the connection failure type field of the second failure related message is of a second type.

As an embodiment, the first communication device 450 includes: a memory storing a program of computer readable instructions that when executed by at least one processor result in actions comprising: determining that a radio connection with a first serving cell fails; in response to said determining that said radio connection with said first serving cell failed, generating a first failure-related message and selecting a second serving cell; performing a handover for the second serving cell; determining that the handover for the second serving cell failed; generating a second failure-related message in response to the determination of the handover failure for the second serving cell; receiving a first signaling; sending a second signaling; wherein the first signaling is received after the generating of the second failure-related message, the first signaling being used to trigger the second signaling, the second signaling comprising the second failure-related message; the first failure-related message comprises a first domain, the first domain of the first failure-related message comprising an identification of the first serving cell; a second field of the second failure-related message comprises an identification of the first serving cell; the first field of the second failure-related message comprises an identification of the second serving cell; the connection failure type field of the first failure related message is of a first type, and the connection failure type field of the second failure related message is of a second type.

As an embodiment, the second communication device 410 includes: at least one processor and at least one memory including computer program code; the at least one memory and the computer program code are configured for use with the at least one processor. The second communication device 410 at least: sending a first signaling; receiving a second signaling; wherein, in response to determining that the radio connection with the first serving cell failed, a first failure-related message is generated and the second serving cell is selected; in response to determining that the handover to the second serving cell failed, a second failure-related message is generated; the first signaling is sent after the generating of the second failure-related message, the first signaling being used to trigger the second signaling, the second signaling comprising the second failure-related message; the first failure-related message comprises a first domain, the first domain of the first failure-related message comprising an identification of the first serving cell; a second field of the second failure-related message comprises an identification of the first serving cell; the first field of the second failure-related message comprises an identification of the second serving cell; the connection failure type field of the first failure related message is of a first type, and the connection failure type field of the second failure related message is of a second type.

As an embodiment, the second communication device 410 includes: a memory storing a program of computer readable instructions that when executed by at least one processor result in actions comprising: sending a first signaling; receiving a second signaling; wherein, in response to determining that the radio connection with the first serving cell failed, a first failure-related message is generated and the second serving cell is selected; in response to determining that the handover to the second serving cell failed, a second failure-related message is generated; the first signaling is sent after the generating of the second failure-related message, the first signaling being used to trigger the second signaling, the second signaling comprising the second failure-related message; the first failure-related message comprises a first domain, the first domain of the first failure-related message comprising an identification of the first serving cell; a second field of the second failure-related message comprises an identification of the first serving cell; the first field of the second failure-related message comprises an identification of the second serving cell; the connection failure type field of the first failure related message is of a first type, and the connection failure type field of the second failure related message is of a second type.

For one embodiment, the antenna 452, the receiver 454, the receive processor 456, the controller/processor 459 are configured to receive a first signaling; at least one of the antenna 420, the transmitter 418, the transmit processor 416, and the controller/processor 475 is configured to send first signaling.

As one implementation, the antenna 452, the transmitter 454, the transmit processor 468, the controller/processor 459 are configured to send second signaling; at least one of the antenna 420, the receiver 418, the receive processor 470, the controller/processor 475 is configured to receive second signaling.

As one implementation, the antenna 452, the transmitter 454, the transmit processor 468, the controller/processor 459 are configured to send third signaling; at least one of the antenna 420, the receiver 418, the receive processor 470, the controller/processor 475 is configured to receive third signaling.

For one embodiment, the antenna 452, the receiver 454, the receive processor 456, the controller/processor 459 are configured to receive fourth signaling; at least one of the antenna 420, the transmitter 418, the transmit processor 416, and the controller/processor 475 is configured to send fourth signaling.

As one implementation, the antenna 452, the transmitter 454, the transmit processor 468, the controller/processor 459 are configured to send fifth signaling; at least one of the antenna 420, the receiver 418, the receive processor 470, the controller/processor 475 is configured to receive fifth signaling.

As an embodiment, the first communication device 450 corresponds to a first node in the present application.

For one embodiment, the first communication device 450 is a user device.

As an embodiment, the first communication device 450 is a terminal device (end).

For one embodiment, the first communication device 450 is a user equipment that supports dual active protocol stacks.

For one embodiment, the first communication device 450 is a user equipment supporting dual connectivity.

For one embodiment, the first communication device 450 is a user equipment supporting a large delay difference.

As an embodiment, the first communication device 450 is a user equipment supporting NTN.

As an embodiment, the first communication device 450 is a TN-capable user equipment.

As an embodiment, the second communication device 410 corresponds to a second node in the present application.

As an embodiment, the second communication device 410 corresponds to a third node in the present application.

As an embodiment, the second communication device 410 is a base station device (gNB/eNB/ng-eNB).

As an embodiment, the second communication device 410 is a base station device supporting large delay inequality.

As an embodiment, the second communication device 410 is a base station device supporting NTN.

As an embodiment, the second communication device 410 is a base station device supporting TN.

Example 5

Embodiment 5 illustrates a wireless signal transmission flow chart according to an embodiment of the present application, as shown in fig. 5. The first node U01 includes a User Equipment (UE); the second node N02 comprises a maintaining base station of the second serving cell; the third node N03 comprises a maintaining base station of the first serving cell; it is specifically noted that the order in this example does not limit the order of signal transmission and the order of implementation in this application.

For theFirst node U01Receiving a fourth signaling in step S5101, determining in S5102 that a radio connection with the first serving cell failed, generating a first failure related message and selecting a second serving cell in step S5103, performing a handover to the second serving cell in step S5104, determining in step S5105 that the handover to the second serving cell failed, generating a second loss in step S5106If the correlation message is lost, the fifth signaling is transmitted in step S5107, the third signaling is transmitted in step S5108, the first signaling is received in step S5109, and the second signaling is transmitted in step S51010.

For theSecond node N02The fifth signaling is received in step S5201, the third signaling is received in step S5202, the first signaling is transmitted in step S5203, and the second signaling is received in step S5204.

For theThird node N03In step S5301, a fourth signaling is transmitted.

In embodiment 5, the first signaling is received after the generating of the second failure-related message, the first signaling is used for triggering the second signaling, and the second signaling includes the second failure-related message; the first failure-related message comprises a first domain, the first domain of the first failure-related message comprising an identification of the first serving cell; a second field of the second failure-related message comprises an identification of the first serving cell; the first field of the second failure-related message comprises an identification of the second serving cell; a connection failure type field of the first failure related message is a first type, and the connection failure type field of the second failure related message is a second type; the second signaling comprises the first failure-related message; the third signaling comprises a first message used to indicate that the first failure-related message and the second failure-related message are generated; the first signaling indicates a message to be reported, the second signaling comprises the message to be reported, and the message to be reported comprises at least one of the first failure related message and the second failure related message; the fourth signaling comprises configuration information of the second serving cell; as the response to determining the handover failure for the second serving cell, selecting a first target cell, and setting a third domain in the second failure-related message as an identifier of the first target cell; the fifth signaling is used to request the connection re-establishment, the first target cell is used for connection re-establishment; clearing the first failure-related message, wherein the second failure-related message comprises the first failure-related message.

For one embodiment, the first node U01 supports a Dual Active Protocol Stack (DAPS).

As an example, the second node N02 comprises a Conditional Handover (CHO) candidate cell.

For one embodiment, the second node N02 includes a Target Cell (Target Cell).

For one embodiment, the second node N02 includes a target cell where the handover failure occurs.

For one embodiment, the third node N03 includes a Source Cell (Source Cell).

As an embodiment, the third node N03 comprises a primary cell (PCell) where the radio connection failure occurs.

For one embodiment, the third node N03 includes a Source cell (Source PCell) where the radio connection failure occurs.

For one embodiment, the third node N03 includes a source cell where the handover failure occurs.

As an embodiment, the second signaling includes the first failure related message and does not include the second failure related message.

As an embodiment, the second signaling includes the second failure-related message and the first failure-related message.

As an embodiment, the second signaling including the first failure-related message includes: the first failure-related message is one or more fields (Filed) in the second signaling.

As an embodiment, the second signaling including the first failure-related message includes: the first failure-related message is one or more IEs (Information elements) in the second signaling.

As an embodiment, the second signaling including the first failure-related message includes: the second signaling is used to carry the first failure-related message.

As an embodiment, the second signaling including the first failure-related message includes: the second signaling is used to determine the first failure-related message.

As an embodiment, the second signaling includes all of the first failure-related message.

As an embodiment, the second signaling comprises part of the first failure-related message.

As an embodiment, the third signaling is transmitted over an air interface.

As an embodiment, the third signaling is transmitted over a wireless interface.

As an embodiment, the third signaling is transmitted through higher layer signaling.

As an embodiment, the third signaling comprises higher layer signaling.

As an embodiment, the third signaling comprises all or part of a higher layer signaling.

As an embodiment, the third signaling includes a Radio Resource Control (RRC) Message (Message).

As an embodiment, the third signaling includes all or part of ie (information element) of an RRC message.

As an embodiment, the third signaling comprises all or part of a field in an IE of an RRC message.

As an embodiment, the third signaling is used for RRC connection reconfiguration procedure.

As an embodiment, the third signaling is used for a recovery procedure of the radio connection failure.

As an embodiment, the signaling radio bearer of the third signaling comprises SRB 3.

As an embodiment, the third signaling includes an uplink signaling.

As an embodiment, the logical Channel of the third signaling includes a DCCH (Dedicated Control Channel).

As an embodiment, the third signaling includes an rrcconnectionreconfiguration complete message.

As an embodiment, the third signaling includes a rrcreeconfigurationcomplete message.

For one embodiment, the third signaling comprises a rrcreestablshmenticomplete message.

As an embodiment, the third signaling comprises an rrcconnectionreestablishingcomplete message.

As an embodiment, the third signaling comprises an RRCConnectionSetupComplete message.

As an embodiment, the third signaling comprises a RRCSetupComplete message.

As an embodiment, the third signaling comprises an rrcconnectionresummecomplete message.

For one embodiment, the third signaling comprises a RRCResumeComplete message.

For one embodiment, the first message includes the rlf-InfoAvailable field.

As one embodiment, the first message is used to replace the rlf-InfoAvailable field.

For one embodiment, the first message is used to indicate whether the first node U01 has the first failure-related message or the second failure-related message.

As an embodiment, the first message includes 1 bit.

As a sub-embodiment of this embodiment, the third signaling comprises that the first message is used to indicate to the first node U01 that the first failure related message or the second failure related message is present.

As an additional embodiment of this sub-embodiment, the first message is set to 0 to indicate that the first node U01 has the first failure related message.

As an additional embodiment of this sub-embodiment, the first message is set to 1 to indicate to the first node U01 that the second failure related message is present.

As a sub-embodiment of this embodiment, the third signaling does not include that the first message is used to indicate that the first node U01 does not have the first failure related message or the second failure related message.

For one embodiment, the first message includes Q1 bits, the Q1 being a positive integer greater than 1.

As an embodiment, the first message comprises 2 bits.

As a sub-embodiment of this embodiment, the first message indicates the first state from Q2 states, Q2 being a positive integer greater than 2.

As an additional embodiment of this sub-embodiment, the first status indicates that both the first failure-related message and the second failure-related message are generated.

As an additional embodiment of this sub-embodiment, the first status indicates that neither the first failure-related message nor the second failure-related message was generated.

As an additional embodiment of this sub-embodiment, the first status indicates that one of the first failure-related message and the second failure-related message is generated.

As a sub-embodiment of the above embodiment, said Q2 is equal to 3.

As an example, one of the Q2 states is reserved (i.e., undefined).

As a sub-embodiment of the above embodiment, said Q2 is equal to 4.

As an embodiment, the first signaling indication to-be-reported message includes: the first signaling is used for requesting the message to be reported.

As an embodiment, the first signaling indication to-be-reported message includes: the first signaling comprises a domain requesting the message to be reported.

As an embodiment, the to-be-reported message includes a stored radio link failure related message.

As an embodiment, the message to be reported includes a stored random access related message.

As an embodiment, the to-be-reported message includes a stored mobility related message.

As an embodiment, the to-be-reported message includes a stored radio link failure recovery related message.

As an embodiment, the first signaling includes a UEInformationRequest message.

As an embodiment, a first indicator is used to indicate the to-report message.

As an embodiment, the first indicator comprises a field in the first signaling.

As an embodiment, the first indicator is used to indicate the number of the messages to be reported.

As an embodiment, the first indicator is used to indicate an identity of the to-report message.

As an embodiment, the first indicator is used to indicate that all of the messages stored by the first node U01 to be reported are reported.

For one embodiment, the first indicator is used to indicate that the first node U01 reports the portion of the to-report message stored by the first node U01.

For one embodiment, the first indicator is used to indicate that the last to-report message of the to-report messages stored by the first node U01 is to be reported.

As an embodiment, the first indicator is used to indicate that the to-report message includes the first failure-related message.

As an embodiment, the first indicator is used to indicate that the to-report message includes the second failure-related message.

As an embodiment, the first indicator is used to indicate that the to-be-reported message includes the first failure-related message and the second failure-related message.

For one embodiment, the first indicator comprises a ra-ReportReq.

For one embodiment, the first indicator comprises a connEstFailReportReq.

For one embodiment, the first indicator comprises rlf-ReportReq.

As one embodiment, the first indicator includes a mobilityHistoryReportReq.

As an embodiment, the first indicator comprises noncritical extension.

For one embodiment, the first indicator comprises an rlfRecoveryReportReq.

As an embodiment, the first signaling includes a first indicator, and a value of the first indicator is set to tune and used to indicate that the message to be reported needs to be reported.

As an embodiment, the first signaling, excluding the first indicator, is used to indicate that the to-report message does not need to be reported.

As one embodiment, the first indicator includes K2 bits, the K2 being a positive integer greater than 1.

As a sub-embodiment of this embodiment, when the first indicator includes 00, the to-report message does not need to be reported.

As a sub-embodiment of this embodiment, when the first indicator includes 01, the to-be-reported message includes the first failure-related message.

As a sub-embodiment of this embodiment, when the first indicator includes 10, the to-be-reported message includes the second failure-related message.

As a sub-embodiment of this embodiment, when the first indicator includes 11, the to-be-reported message includes the first failure related message and the second failure related message.

As an embodiment, the second signaling that includes the to-be-reported message includes: the second signaling is used for carrying the message to be reported.

As an embodiment, the second signaling that includes the to-be-reported message includes: and reporting the message to be reported through the second signaling.

As an embodiment, the second signaling that includes the to-be-reported message includes: the second signaling is a response to the first signaling.

As an embodiment, the second signaling that includes the to-be-reported message includes: and the first node U01 reports the message to be reported according to the first signaling through the second signaling.

As an embodiment, the second signaling comprises an RA-Report.

As an embodiment, the second signaling includes a ConnEstFailReport.

For one embodiment, the second signaling comprises an RLF-Report.

As an embodiment, the second signaling comprises MobilityHistoryReport.

As an embodiment, the second signaling comprises RlfRecoveryReportReq.

As an embodiment, the sentence, the to-be-reported message includes at least one of the first failure related message and the first failure related message, which includes the following meanings: the message to be reported comprises the first failure related message.

As an embodiment, the sentence, the to-be-reported message includes at least one of the first failure related message and the first failure related message, which includes the following meanings: the message to be reported comprises the second failure related message.

As an embodiment, the sentence, the to-be-reported message includes at least one of the first failure related message and the first failure related message, which includes the following meanings: the message to be reported comprises the first failure related message and the second failure related message.

As an embodiment, the sentence indicating that the fourth signaling includes the configuration information of the second serving cell includes: the fourth signaling includes random access related information of the second serving cell.

As an embodiment, the sentence indicating that the fourth signaling includes the configuration information of the second serving cell includes: the fourth signaling includes RRC configuration related information of the second serving cell.

As an embodiment, the sentence indicating that the fourth signaling includes the configuration information of the second serving cell includes: the fourth signaling comprises uplink synchronization related information of the second serving cell.

As an embodiment, the sender of the fourth signaling comprises a maintaining base station of the first serving cell.

As an embodiment, the sender of the fourth signaling comprises a serving base station of a source cell.

As an embodiment, the fourth signaling is used to configure for the Conditional Handover (CHO).

As an embodiment, the fourth signaling is used to configure for Conditional Primary and secondary Cell (PSCell) condition Addition (CPA).

As one embodiment, the fourth signaling is used to configure for the Conditional primary secondary cell condition Change (CPC).

As an embodiment, the fourth signaling is used for configuring MCG (Master Cell Group) failure Recovery (Recovery).

As an embodiment, the fourth signaling is used to configure for DAPS handover.

As an embodiment, the fourth signaling is transmitted over an air interface.

As an embodiment, the fourth signaling is transmitted over a wireless interface.

As an embodiment, the fourth signaling is transmitted through higher layer signaling.

As an embodiment, the fourth signaling comprises higher layer signaling.

As an embodiment, the fourth signaling comprises all or part of a higher layer signaling.

As an embodiment, the fourth signaling is carried by an SRB1 (signaling Radio Bearer 1).

As an example, the fourth signaling is carried over Split SRB 1.

As an embodiment, the fourth signaling is carried by an SRB3 (signaling Radio Bearer 3).

For one embodiment, the fourth signaling comprises a Downlink (DL) signaling.

As an embodiment, the logical channel carrying the fourth signaling comprises a DCCH.

As an embodiment, the fourth signaling comprises an RRC message.

As an embodiment, the fourth signaling includes all or part of an IE of an RRC message.

As an embodiment, the fourth signaling comprises all or part of a Field (Field) in an IE of an RRC message.

As an embodiment, the fourth signaling includes a rrcreeconfiguration message.

As an embodiment, the fourth signaling includes RRCReconfiguration IE.

As an embodiment, the fourth signaling comprises a conditional reconfiguration IE.

As an embodiment, the fourth signaling comprises a conditional reconfiguration field

As an embodiment, the first signaling includes a condConfigId field.

As an embodiment, the fourth signaling comprises an RRCConnectionReconfiguration message.

As an embodiment, the fourth signaling includes rrcconnectionreconfiguration ie.

As an embodiment, the fourth signaling includes a configureid field.

As an embodiment, the fourth signaling comprises reconfigurationWithSync.

As an embodiment, the fourth signaling comprises a dapsConfig field.

As an embodiment, the fourth signaling includes a handover preparation information message.

As an embodiment, the fourth signaling comprises a configgrestrictinfodaps field.

As an embodiment, the fourth signaling comprises dapsHO-Config.

As an embodiment, the fourth signaling comprises drb-ToAddModList.

As an embodiment, the fourth signaling comprises daps-SourceRelease.

As one embodiment, the first target cell includes the second serving cell.

As an embodiment, the first target cell comprises a cell determined by cell selection.

For one embodiment, the first target cell is used for RRC connection Reestablishment (Reestablishment).

As an embodiment, the third field in the second failure-related message is used to determine an identity of an RRC re-established cell.

For one embodiment, the third field in the second failure-related message comprises a resessabelishmentcellid.

As a real-time flow, the receiver of the fifth signaling comprises the maintaining base station of the first target cell.

As an embodiment, the fifth signaling is transmitted over an air interface.

As an embodiment, the fifth signaling is transmitted over a wireless interface.

As an embodiment, the fifth signaling is transmitted through higher layer signaling.

As an embodiment, the fifth signaling comprises higher layer signaling.

As an embodiment, the fifth signaling comprises all or part of a higher layer signaling.

As an embodiment, the fifth signaling includes a Radio Resource Control (RRC) Message (Message).

As an embodiment, the fifth signaling includes all or part of IE of one RRC message.

As an embodiment, the fifth signaling comprises all or part of a Field (Field) in an IE of an RRC message.

As an embodiment, the signaling Radio Bearer for carrying the fifth signaling includes SRB0 (signaling Radio Bearer 1).

As an embodiment, the logical Channel carrying the fifth signaling includes a Common Control Channel (CCCH).

As an embodiment, the fifth signaling used to request the connection re-establishment comprises: the fifth signaling is used to initiate RRC reestablishment.

As an embodiment, the fifth signaling used to request the connection re-establishment comprises: the fifth signaling comprises a first message of an RRC reestablishment procedure.

For one embodiment, the fifth signaling comprises a rrcreestablishrequest message.

As an embodiment, the fifth signaling includes an rrcconnectionreestablishinrequest message.

As one embodiment, the meaning of clearing includes deleting (Clear).

As one example, the meaning of clearing includes Discard (Discard).

As an example, the meaning of clearance includes Release (Release).

As an embodiment, the phrase clearing the first failure related message includes the following meanings: clearing all of the first failure-related messages stored in the VarRLF-Report.

As an embodiment, the phrase clearing the first failure related message includes the following meanings: clearing portions of the first failure-related message stored in the VarRLF-Report.

As an example, the sentence, the second failure-related message, including the first failure-related message, includes the following meanings: the second failure-related message includes all of the first failure-related message.

As an example, the sentence, the second failure-related message, including the first failure-related message, includes the following meanings: the second failure-related message comprises part of the first failure-related message.

As one embodiment, dashed box F1 is optional.

As an example, the dashed box F1 exists.

As an example, the dashed box F1 is not present.

As an embodiment, when the dotted-line block F1 exists, the third signaling includes a rrcreestablshmentcomplete message.

As an embodiment, when the dotted-line block F1 does not exist, the third signaling includes an rrcconnectionreestablishingcomplete message.

Example 6

Embodiment 6 illustrates a schematic diagram in which a first failure-related message and a second failure-related message are generated and transmitted according to an embodiment of the present application.

As shown in fig. 6, the first node determines that the radio connection with the first serving cell fails in step S601, generates the first failure related message in step S602, performs handover to the second serving cell in step S603, determines that the handover to the second serving cell fails in step S604, clears the first failure related message in step S605, generates the second failure related message in step S606, and sends the second signaling in step S607. Wherein the second signaling comprises the second failure-related message.

As an embodiment, the generating the first failure-related message in step S602 includes: storing the first failure-related message to a VarRLF _ Report.

As an embodiment, the clearing the first failure-related message in step S605 includes: clearing the first failure-related message stored in the VarRLF _ Report.

As a sub-embodiment of this embodiment, all of the first failure-related messages stored in the VarRLF _ Report are cleared.

As a sub-embodiment of this embodiment, the part of the first failure-related message stored in the VarRLF _ Report is cleared.

As an embodiment, the generating the second failure-related message in step S606 includes: storing the second failure-related message to the VarRLF _ Report.

For one embodiment, the second failure-related message comprises the first failure-related message.

As a sub-embodiment of this embodiment, the sentence wherein the second failure-related message comprises the first failure-related message comprises: the second failure-related message includes all of the first failure-related message.

As a sub-embodiment of this embodiment, the sentence wherein the second failure-related message comprises the first failure-related message comprises: the second failure-related message comprises part of the first failure-related message.

As a sub-embodiment of this embodiment, the sentence wherein the second failure-related message comprises the first failure-related message comprises: store all of the first failure message to the VarRLF _ Report.

As a sub-embodiment of this embodiment, the sentence wherein the second failure-related message comprises the first failure-related message comprises: storing a portion of the first failure message to the VarRLF _ Report.

As an embodiment, the second failure-related message does not include the first failure-related message.

As a sub-embodiment of this embodiment, the sentence wherein the second failure related message does not include the first failure related message comprises: the first failure related message is completely cleared and the first failure message is not stored to the VarRLF _ Report.

As one embodiment, the phrase the second signaling including the second failure related message includes: the second signaling comprises the second failure-related message stored in the VarRLF _ Report.

As one embodiment, the phrase the second signaling including the second failure related message includes: the second signaling includes the second failure-related message and the first failure-related message.

As one embodiment, the phrase the second signaling including the second failure related message includes: the second signaling includes all of the second failure-related message and part of the first failure-related message.

Example 7

Embodiment 7 illustrates a schematic diagram in which a first failure-related message and a second failure-related message are generated and transmitted according to another embodiment of the present application.

As shown in fig. 7, the first node determines that the radio connection with the first serving cell fails in step S701, generates the first failure related message in step S702, performs handover to the second serving cell in step S703, determines that the handover to the second serving cell fails in step S704, generates the second failure related message in step S705, and sends the second signaling in step S706. Wherein the second signaling comprises the first failure-related message and the second signaling comprises the second failure-related message.

As an embodiment, the generating the first failure-related message in step S702 includes: storing the first failure-related message to a VarRLF _ Report.

As an embodiment, the generating the second failure-related message in step S705 includes: storing the second failure-related message to the VarRLF _ Report.

As an embodiment, the first failure-related message and the second failure-related message are both stored in the VarRLF _ Report.

As an embodiment, the sentence and the second signaling comprise the first failure-related message, and the second signaling comprises the second failure-related message including: the second signaling includes both the first failure-related message and the second failure-related message.

As an embodiment, the first and second failure-related messages are stored in a radio link failure report list, which is used to store a plurality of radio link failure reports.

As an embodiment, the radio link failure Report list includes one field in the VarRLF _ Report.

Example 8

Embodiment 8 illustrates a schematic diagram in which a first message of a third signaling is used to indicate that a first failure-related message and a second failure-related message are generated according to an embodiment of the present application, as shown in fig. 8. In fig. 8, a first line indicates a value of the first message, a second line indicates whether the first failure-related message is generated, and a third line indicates whether the second failure-related message is generated; symbol x indicates that no generation is made, and symbol √ indicates that generation is made.

In embodiment 8, the first message of the third signaling comprises 1 bit.

As an embodiment, when the first message is not set, it indicates that neither the first failure-related message nor the second failure-related message is generated.

As an embodiment, when the first message is set to tune, it indicates that both the first failure-related message and the second failure-related message are generated.

As an example, the unset meaning includes: the third signaling does not include the first message.

Example 9

Embodiment 9 illustrates a schematic diagram in which a first message of a third signaling according to another embodiment of the present application is used to indicate that a first failure-related message and a second failure-related message are generated, as shown in fig. 9. In fig. 9, a first line indicates a value of the first message, a second line indicates whether the first failure-related message is generated, and a third line indicates whether the second failure-related message is generated; symbol x indicates that no generation is made, and symbol √ indicates that generation is made.

In embodiment 9, the first message includes 1 bit.

As an embodiment, when the first message is not set, it is indicated that neither the first failure-related message nor the second failure-related message is generated.

As an embodiment, when the first message is set to 0, it indicates that the first failure related message is generated and the second failure related message is not generated.

As an embodiment, when the first message is set to 1, it indicates that the first failure-related message is not generated and the second failure-related message is generated.

Example 10

Embodiment 10 illustrates a schematic diagram in which a first message of a third signaling according to still another embodiment of the present application is used to indicate that a first failure-related message and a second failure-related message are generated, as shown in fig. 10. In fig. 10, a first line indicates a value of the first message, a second line indicates whether the first failure-related message is generated, and a third line indicates whether the second failure-related message is generated; symbol x indicates that no generation is made, and symbol √ indicates that generation is made.

In embodiment 10, the first message comprises 2 bits.

As an embodiment, when the first message is set to 00, it indicates that neither the first failure-related message nor the second failure-related message is generated.

As an embodiment, when the first message is set to 01, it indicates that the first failure related message is generated and the second failure related message is not generated.

As an embodiment, when the first message is set to 10, it indicates that the first failure-related message is not generated and the second failure-related message is generated.

As an embodiment, when the first message is set to 11, it indicates that the first failure-related message is generated and the second failure-related message is generated.

Example 11

Embodiment 11 illustrates a schematic diagram in which a first message of a third signaling according to still another embodiment of the present application is used to indicate that a first failure-related message and a second failure-related message are generated, as shown in fig. 11. In fig. 11, a first line indicates a value of the first message, a second line indicates whether the first failure-related message is generated, and a third line indicates whether the second failure-related message is generated; symbol x indicates that no generation is made, and symbol √ indicates that generation is made.

In embodiment 11, the first message includes 2 bits.

As an embodiment, when the first message is set to 00, it is reserved.

As an embodiment, the meaning of the reservation includes: is not defined.

Example 12

Embodiment 12 illustrates a schematic diagram that the second signaling includes a first failure related message and a second failure related message according to an embodiment of the present application, as shown in fig. 12. In fig. 12, the solid-line boxes represent the second failure-related message field descriptions; ellipses represent other fields or IEs.

In embodiment 12, the second signaling includes the second failure-related message; the second signaling comprises the first failure-related message; the second failure-related message comprises the first failure-related message; a second field of the second failure-related message comprises a cell identity of the first serving cell; the first field of the second failure-related message comprises a cell identity of the second serving cell; a second subzone or a first subzone of the second failure-related message includes a cell identification of the first serving cell; the first sub-field and the second sub-field of the second failure-related message are related to a type of the first connection failure; the connection failure type includes a first type or a second type.

Fig. 12 is a schematic diagram of a message structure of the second signaling, as an embodiment.

As an example, the ASN1START represents the beginning of an ASN.1 message.

As an embodiment, said-TAG-second signaling-START indicates the START of the second signaling.

As an embodiment, the-TAG-second signaling-STOP indicates the end of the second signaling.

As an example, the ASN1STOP represents the end of the ASN.1 message.

As an embodiment, the first structure type comprises SEQUENCE.

As an example, the second structure type includes ended.

As an embodiment, the first failure-related message is generated and stored.

As an embodiment, the first failure-related message is generated but not stored.

As an embodiment, the first failure-related message is stored to the second failure-related message.

As an embodiment, the first failure related message comprises a first field, and the first field of the first failure related message comprises an identity of the first serving cell.

For one embodiment, the first field of the second failure related message comprises a failedPCellId 2.

For one embodiment, the second field of the second failure related message comprises previouscellld 2.

For one embodiment, the first sub-domain of the second failure-related message includes a failedPCellId 1.

For one embodiment, the second sub-domain of the second failure-related message includes previouscellld 1.

As an embodiment, the first field of the second failure-related message is used to indicate an identity of the target cell at the time of handover failure.

As an embodiment, the second field of the second failure related message is used to indicate the identity of the source cell when handover fails.

As an embodiment, the first field of the second failure-related message and the second field of the second failure-related message are associated to a second radio connection failure.

As an embodiment, the first subzone of the second failure related message indicates a cell in which the RLF is detected or a target cell of the HOF.

As an embodiment, the second subzone of the second failure related message is used to indicate the source cell at the last handover.

As an embodiment, the first sub-domain and the second sub-domain of the second failure-related message are associated to a first connection failure.

For one embodiment, the first sub-domain of the second failure-related message comprises the first domain of the first failure-related message.

For one embodiment, the second sub-domain of the second failure-related message includes the first domain of the first failure-related message.

As an embodiment, when the type of the first connection failure comprises RLF, the first sub-domain of the second failure-related message comprises an identification of the first serving cell.

As an embodiment, when the type of the first connection failure comprises an HOF, the second subzone of the second failure-related message comprises an identification of the first serving cell.

As one embodiment, the connection failure type is used to indicate a type of connection failure.

Example 13

Embodiment 13 illustrates a schematic diagram of second signaling including a first failure-related message and a second failure-related message according to another embodiment of the present application, as shown in fig. 13. In fig. 13, the solid-line boxes represent the second failure-related message field descriptions; ellipses represent other fields or IEs.

In embodiment 13, the second signaling comprises a radio link failure report list, the radio link failure report list being used to store a plurality of radio link failure reports; the first failure-related message and the second failure-related message are generated; the second signaling comprises the second failure-related message; the second signaling comprises the first failure-related message; the first failure-related message comprises a first domain, the first domain of the first failure-related message comprising an identification of the first serving cell; a second field of the second failure-related message comprises an identification of the first serving cell; the first field of the second failure-related message comprises an identification of the second serving cell; the connection failure type field of the first failure related message is of a first type, and the connection failure type field of the second failure related message is of a second type.

As an example, the ASN1START represents the beginning of an ASN.1 message.

As an example, the ASN1STOP represents the end of the ASN.1 message.

As an embodiment, the first structure type comprises SEQUENCE.

As an example, the second structure type includes ended.

As an embodiment, the second signaling includes a radio link failure report list including the first failure related message and the second failure related message.

As an example, the radio link failure report list is used to store continuously occurring radio link failure reports that have not been reported.

As an example, the radio link failure report list is used to store a plurality of radio link failure reports occurring in the same procedure.

As one embodiment, the radio link failure report list stores radio link failure reports when a CHO failure is performed after RLF occurs.

As one embodiment, the radio link failure report list stores radio link failure reports when CHO failures are performed after HOF occurs.

As one embodiment, the radio link failure report list includes K1 of the radio link failure reports, the K1 being a positive integer greater than 1.

As a sub-embodiment of this embodiment, the first failure-related message comprises one failure-related message of the K1 radio link failure reports.

As a sub-embodiment of this embodiment, the second failure-related message comprises one failure-related message of the K1 radio link failure reports.

As a sub-embodiment of this embodiment, the K1 is not greater than 8.

As a sub-embodiment of this embodiment, the K1 is preconfigured.

As a sub-embodiment of this embodiment, the K1 is configurable.

As a sub-embodiment of this embodiment, the K1 is of a fixed size.

For one embodiment, the radio link failure report list comprises rlf-ReportList.

For one embodiment, the radio link failure Report includes rlf-Report.

As an embodiment, the second signaling includes a failure related message list, the failure related message list includes K1 first-type failure related messages, and the K1 is a positive integer.

As a sub-embodiment of this embodiment, the second signaling comprises rlf-ReportList.

As a sub-embodiment of this embodiment, the second signaling comprises rlf-Report.

As an example, the list of failure-related messages is stored in VarRLF _ Report.

As a sub-embodiment of this embodiment, the first failure related message comprises one rlf-Report of VarRLF _ reports.

As a sub-embodiment of this embodiment, the second failure related message comprises one rlf-Report of VarRLF _ reports.

As a sub-embodiment of this embodiment, the phrase generating a first failure related message comprises: the first failure related message is stored to one of the rlf-Report fields in the VarRLF _ Report, rlf-Report field.

As a sub-embodiment of this embodiment, the phrase generating a second failure related message comprises: storing the first failure related message to one rlf-Report field of one rlf-Report list in VarRLF _ Report.

As an example, the radio link failure report list field is used to indicate K1 radio link failure reports.

For one embodiment, the radio link failure reporting field is used to provide a radio link failure report in a radio link failure report list.

As an embodiment, the first domain is used to indicate a cell in which RLF is detected or a target cell of the HOF.

As an embodiment, the second field is used to indicate the source cell at the last handover.

Example 14

Embodiment 14 illustrates a block diagram of a processing apparatus for use in a first node according to an embodiment of the present application; as shown in fig. 14. In fig. 14, the processing means 1400 in the first node comprises a first receiver 1401, a first transceiver 1402.

A first receiver 1401 for determining that a radio connection with a first serving cell has failed; in response to the determination that the radio connection with the first serving cell failed, generating a first failure-related message and selecting a second serving cell.

A first transceiver 1402 that performs a handover for the second serving cell.

The first receiver 1401, determining that the handover for the second serving cell failed; generating a second failure-related message in response to the determination of the handover failure for the second serving cell.

The first transceiver 1402, receiving a first signaling; and sending the second signaling.

In embodiment 14, the first signaling is received after the generating of the second failure-related message, the first signaling is used for triggering the second signaling, and the second signaling includes the second failure-related message; the first failure-related message comprises a first domain, the first domain of the first failure-related message comprising an identification of the first serving cell; a second field of the second failure-related message comprises an identification of the first serving cell; the first field of the second failure-related message comprises an identification of the second serving cell; the connection failure type field of the first failure related message is of a first type, and the connection failure type field of the second failure related message is of a second type.

As an embodiment, the second signaling comprises the first failure-related message.

For one embodiment, the first transceiver 1402, transmits the third signaling; wherein the third signaling comprises a first message used to indicate that the first and second failure-related messages are generated.

As an embodiment, the first signaling indicates a message to be reported, the second signaling includes the message to be reported, and the message to be reported includes at least one of the first failure related message and the second failure related message.

As an example, the first receiver 1401, receives a fourth signaling; wherein the fourth signaling comprises configuration information of the second serving cell.

As an embodiment, the first transceiver 1402, as the response to determining the handover failure for the second serving cell, selects a first target cell, sets a third field in the second failure-related message as an identifier of the first target cell, and sends a fifth signaling; wherein the fifth signaling is used to request the connection re-establishment and the first target cell is used for connection re-establishment.

As an embodiment, the first failure-related message is cleared, and the second failure-related message comprises the first failure-related message.

For one embodiment, the first transceiver comprises a receiver.

For one embodiment, the first transceiver comprises a transmitter.

The first receiver 1401, for one embodiment, includes the antenna 452, the receiver 454, the multiple antenna receive processor 458, the receive processor 456, the controller/processor 459, the memory 460, and the data source 467 of fig. 4 of the present application.

For one embodiment, the first receiver 1401 includes the antenna 452, the receiver 454, the multi-antenna receive processor 458, and the receive processor 456 of fig. 4.

For one embodiment, the first receiver 1401 includes the antenna 452, the receiver 454, and the receive processor 456 of fig. 4.

The first transceiver 1402 includes, for one embodiment, the antenna 452, the transmitter 454, the multi-antenna transmit processor 457, the transmit processor 468, the controller/processor 459, the memory 460, the data source 467, the receiver 454, the multi-antenna receive processor 458, and the receive processor 456 of fig. 4 of the present application.

For one embodiment, the first transceiver 1402 includes the antenna 452, the transmitter 454, the multi-antenna transmit processor 457, the transmit processor 468, the receiver 454, the multi-antenna receive processor 458, and the receive processor 456 of fig. 4.

For one embodiment, the first transceiver 1402 includes the antenna 452, the transmitter 454, the transmit processor 468, the receiver 454, and the receive processor 456 of fig. 4.

Example 15

Embodiment 15 illustrates a block diagram of a processing apparatus for use in a second node according to an embodiment of the present application; as shown in fig. 15. In fig. 15, a processing arrangement 1500 in the second node comprises a first transmitter 1501 and a second receiver 1502.

The first transmitter 1501 transmits the first signaling.

The second receiver 1502 receives the second signaling.

In embodiment 15, in response to determining that the radio connection with the first serving cell failed, a first failure-related message is generated and the second serving cell is selected; in response to determining that the handover to the second serving cell failed, a second failure-related message is generated; the first signaling is sent after the generating of the second failure-related message, the first signaling being used to trigger the second signaling, the second signaling comprising the second failure-related message; the first failure-related message comprises a first domain, the first domain of the first failure-related message comprising an identification of the first serving cell; a second field of the second failure-related message comprises an identification of the first serving cell; the first field of the second failure-related message comprises an identification of the second serving cell; the connection failure type field of the first failure related message is of a first type, and the connection failure type field of the second failure related message is of a second type.

For an embodiment, the second receiver 1502 receives a third signaling; wherein the third signaling comprises a first message used to indicate that the first and second failure-related messages are generated.

As an embodiment, the fourth signaling includes configuration information of the second serving cell, and a sender of the fourth signaling includes the first serving cell.

For an embodiment, the second receiver 1502 receives a fifth signaling; wherein the fifth signaling is used to request connection re-establishment; in response to said determining that said handover to said second serving cell failed, a first target cell is selected, said first target cell being used for said connection re-establishment, a third field in said second failure related message being set as an identity of said first target cell.

The first transmitter 1501 includes, for one embodiment, the antenna 420, the transmitter 418, the multi-antenna transmit processor 471, the transmit processor 416, the controller/processor 475, and the memory 476 of fig. 4 of the present application.

The first transmitter 1501 includes the antenna 420, the transmitter 418, the multi-antenna transmit processor 471 and the transmit processor 416 of fig. 4.

For one embodiment, the first transmitter 1501 includes the antenna 420, the transmitter 418, and the transmit processor 416 of fig. 4.

For one embodiment, the second receiver 1502 includes the antenna 420, the receiver 418, the multi-antenna receive processor 472, the receive processor 470, the controller/processor 475, and the memory 476 of fig. 4.

For one embodiment, the second receiver 1502 includes the antenna 420, the receiver 418, the multi-antenna receive processor 472, and the receive processor 470 shown in fig. 4.

For one embodiment, the second receiver 1502 includes the antenna 420, the receiver 418, and the receive processor 470 shown in fig. 4.

It will be understood by those skilled in the art that all or part of the steps of the above methods may be implemented by instructing relevant hardware through a program, and the program may be stored in a computer readable storage medium, such as a read-only memory, a hard disk or an optical disk. Alternatively, all or part of the steps of the above embodiments may be implemented by using one or more integrated circuits. Accordingly, the module units in the above embodiments may be implemented in a hardware form, or may be implemented in a form of software functional modules, and the present application is not limited to any specific form of combination of software and hardware. User equipment, terminal and UE in this application include but not limited to unmanned aerial vehicle, Communication module on the unmanned aerial vehicle, remote control plane, the aircraft, small aircraft, the cell-phone, the panel computer, the notebook, vehicle-mounted Communication equipment, wireless sensor, network card, thing networking terminal, the RFID terminal, NB-IOT terminal, Machine Type Communication (MTC) terminal, eMTC (enhanced MTC) terminal, the data card, network card, vehicle-mounted Communication equipment, low-cost cell-phone, wireless Communication equipment such as low-cost panel computer. The base station or the system device in the present application includes, but is not limited to, a macro cell base station, a micro cell base station, a home base station, a relay base station, a gNB (NR node B) NR node B, a TRP (Transmitter Receiver Point), and other wireless communication devices.

The above description is only a preferred embodiment of the present application, and is not intended to limit the scope of the present application. Any modification, equivalent replacement, improvement and the like made within the spirit and principle of the present application shall be included in the protection scope of the present application.

Claims

1. A first node configured for wireless communication, comprising:

a first transceiver to perform handover for the second serving cell;

the first transceiver receives a first signaling; sending a second signaling;

2. The first node of claim 1, wherein the second signaling comprises the first failure-related message.

3. The first node according to claim 1 or 2, comprising:

the first transceiver transmits a third signaling;

4. The first node according to any of claims 1 to 3, wherein the first signaling indicates a message to be reported, and the second signaling comprises the message to be reported, and the message to be reported comprises at least one of the first failure related message and the second failure related message.

5. The first node according to any of claims 1 to 4, comprising:

the first receiver receives a fourth signaling;

6. The first node according to any of claims 1 to 5, comprising:

the first transceiver, as the response to the determination of the handover failure for the second serving cell, selects a first target cell, sets a third domain in the second failure-related message as an identifier of the first target cell, and sends a fifth signaling;

7. The first node according to any of claims 1 to 6, wherein a first failure related message is cleared and the second failure related message comprises the first failure related message.

8. A method in a first node used for wireless communication, comprising:

performing a handover for the second serving cell;

receiving a first signaling; sending a second signaling;

9. A second node configured for wireless communication, comprising:

a first transmitter for transmitting a first signaling;

a second receiver receiving a second signaling;

10. A method in a second node used for wireless communication, comprising:

sending a first signaling;

receiving a second signaling;