A method and apparatus for wireless communication

Abstract

A method and apparatus for wireless communication are disclosed, including detecting a first bearer failure; the first bearer is associated with a first cell group; performing a first set of operations in response to detecting the first bearer failure, the first set of operations is related to a type of the first bearer; sending a first information in response to detecting the first bearer failure; the first information is used to indicate the first bearer failure; sending a second message in response to all conditions in a first set of conditions being met; the second message indicates that there is available information. By detecting the first bearer failure and performing the first set of operations, the application helps network optimization, improves the reliability of communication, and avoids communication interruption.

Description

TECHNICAL FIELD

[0001] The present application relates to transmission methods and devices in a wireless communication system, and in particular to methods and devices for network optimization, improving service quality of service, relaying communication and the like in communication. BACKGROUND

[0002] The application scenarios of future wireless communication systems are increasingly diversified, and different application scenarios put forward different performance requirements for the system. In order to meet the different performance requirements of various application scenarios, it is decided at the 72nd plenary meeting of 3GPP (3rd Generation Partnership Project) RAN (Radio Access Network) to study New Radio (NR) (or Fifth Generation, 5G), and the NR WI (Work Item) is passed at the 75th plenary meeting of 3GPP RAN, and the standardization work of NR begins.

[0003] In communication, whether it is LTE (Long Term Evolution) or 5G NR, it involves accurate reception of reliable information, optimized energy efficiency, determination of information effectiveness, flexible resource allocation, scalable system structure, efficient non-access layer information processing, low service interruption and drop rate, support for low power consumption, which is of great significance to the normal communication of base stations and user equipment, reasonable scheduling of resources, balancing of system load. It can be said that it is the cornerstone of high throughput, meeting the communication needs of various services, improving spectrum utilization, and improving service quality. Whether it is eMBB (enhanced Mobile BroadBand), URLLC (Ultra Reliable Low Latency Communication) or eMTC (enhanced Machine Type Communication) is indispensable. At the same time, in IIoT (Industrial Internet of Things), in V2X (Vehicular to X) communication, in Device to Device communication, in unlicensed spectrum communication, in user communication quality monitoring, in network planning optimization, in NTN (Non Territerial Network) communication, in TN (Territerial Network) communication, in dual connectivity system, in wireless resource management and multi-antenna codebook selection, in signaling design, neighbor management, service management, in beamforming, there are extensive demands. The transmission mode of information is divided into broadcast and unicast, and the two transmission modes are indispensable for 5G system because they are very helpful to meet the above demands. The way UE connects with network can be direct connection or through relay connection.

[0004] With the increasing complexity and scenarios of the system, higher requirements are put forward for reducing the interruption rate, reducing the delay, enhancing the reliability, enhancing the stability of the system, the flexibility of the service, and the power saving. At the same time, when designing the system, the compatibility between different systems and different versions also needs to be considered.

[0005] 3GPP standardization organization has done relevant standardization work for 5G and formed a series of standards. The standard content can be referred to:

[0006] https: / / www.3gpp.org / ftp / Specs / archive / 38_series / 38.211 / 38211-g60.zip

[0007] https: / / www.3gpp.org / ftp / Specs / archive / 38_series / 38.213 / 38213-g60.zip

[0008] https: / / www.3gpp.org / ftp / Specs / archive / 38_series / 38.331 / 38331-g60.zip SUMMARY

[0009] In various communication scenarios, the use of relay can be involved, for example, when a UE (User Equipment) is at the edge of a cell, the coverage is poor, and the UE can access the network through a relay, which can be another UE. The relay mainly includes layer 3 relay and layer 2 relay (L2U2N relay), both of which provide network access services for remote nodes (U2N remote UEs) through relay nodes. The layer 3 relay is transparent to the access network, that is, the remote UE only establishes a connection with the core network, and the access network cannot identify whether the data is from the remote node or the relay node. The layer 2 relay has an RRC connection between the remote node (U2N remote UE) and the access network (RAN), and the access network can manage the remote node. The access network and the remote node can establish a wireless bearer. The relay can be another UE. In a system supporting layer 2 relay, a UE can communicate with the network through an L2 relay UE (L2 U2N relay UE), that is, use an indirect path, or directly communicate with the network without using a relay, that is, use a direct path. In some scenarios, a UE can use both a direct path and an indirect path to obtain better reliability and higher throughput. The direct path and the indirect path are different in terms of wireless resource management and network optimization. For the direct path, if a failure including a radio link failure occurs, it is better to perform corresponding operations, such as recording and reporting failure information, so as to perform network optimization. For the indirect path, for example, a failure occurs between a remote UE and its relay, that is, a sidelink, since the relay UE is not a fixed infrastructure, it is difficult to effectively optimize the network, and therefore the recording and reporting of corresponding failure information is not very necessary. When a UE uses both a direct path and an indirect path, and a failure occurs in one of the paths, for example, a radio link failure occurs, it should not lead to a failure in communication with the network. Specifically, the UE should be able to maintain communication with the master cell group through the other path. In the prior art, the UE only records information related to the failure of the master cell group when the failure of the master cell group is caused by the failure of the direct path, for example, information related to the radio link failure of the direct path or information related to the handover failure of the direct path. This will lead to the problem that when a UE can use both a direct path and an indirect path, if the direct path fails first, since there is still an indirect path, if it does not cause a failure of the master cell group, information related to the failure of the direct path will not be recorded. If the indirect path fails next, although the master cell group can be considered to have failed at this time, since only the indirect path is available at this time, detailed failure information will not be recorded, and information related to the previous failure of the direct path will not be recorded, thereby failing to optimize the network in the scenario where a direct path and an indirect path are used simultaneously, especially the network optimization for the direct path in such a scenario.Of course, the solution proposed in the present application can also solve other problems in the communication system, and is not limited to the above problems.

[0010] In view of the above problems, the present application provides a solution.

[0011] It should be noted that the embodiments in any node of the present application and the features in the embodiments can be applied to any other node without conflict. The embodiments of the present application and the features in the embodiments can be arbitrarily combined with each other without conflict.

[0012] The present application discloses a method used in a first node for wireless communication, comprising:

[0013] detecting that a first bearer is failed; the first bearer is associated with a first cell group; in response to the behavior of detecting that the first bearer is failed, performing a first set of operations, the first set of operations is related to a type of the first bearer;

[0014] in response to the behavior of detecting that the first bearer is failed, sending a first information; the first information is used to indicate that the first bearer is failed; in response to all conditions in a first set of conditions being met, sending a second message; the second message indicates that there is available information;

[0015] Wherein, the first cell group is a master cell group; the first set of conditions includes that a first state variable stores available information; the meaning of the sentence that the first set of operations is related to the type of the first bearer is: when the first bearer is a first type of bearer, the first set of operations includes at least one of reestablishing an RLC entity associated with the first bearer and storing information for the failure of the first bearer in the first state variable; when the first bearer is a second type of bearer, the first set of operations includes at least releasing an RLC entity associated with the first bearer.

[0016] As an embodiment, the problem to be solved by the present application includes: in the scenario of using L2 relay, especially when direct path and indirect path are used at the same time, how to perform network optimization, especially when direct path and indirect path fail in succession, how to record and report corresponding information to assist network optimization.

[0017] As an embodiment, the benefits of the above method include: supporting network optimization when using L2 relay, especially when direct path and indirect path are used at the same time, reducing communication interruption, improving service quality, increasing coverage, and better supporting mobility and service continuity.

[0018] Specifically, according to an aspect of the present application, the first information is transmitted on a second bearer; the second bearer is associated with the first cell group; one of the first bearer and the second bearer is the first type of bearer and the other is the second type of bearer;

[0019] Wherein, the RLC entity associated with the first type of bearer is an RLC entity of a Uu interface; the RLC entity associated with the second type of bearer is an RLC entity of a PC5 interface; the first type of bearer uses a primary link; the second type of bearer uses a secondary link.

[0020] Specifically, according to an aspect of the present application, the SRB1 of the first node is simultaneously associated with the first bearer and the second bearer; the first node is only configured with one cell group.

[0021] Specifically, according to an aspect of the present application, the first set of operations includes resetting a MAC associated with the first bearer; the first type of bearer is an RLC bearer and the second type of bearer is a secondary link RLC bearer.

[0022] Specifically, according to an aspect of the present application, the first bearer is the first type of bearer; the behavior stores, in the first state variable, information for failure of the first bearer includes storing a reason for failure of the first bearer and whether to use a second type of bearer; the reason for failure of the first bearer belongs to a first candidate reason set, and the first candidate reason set includes radio link failure, cell handover failure and path switching failure.

[0023] Specifically, according to an aspect of the present application, first signaling is received, the first signaling is used to configure a second bearer; one of the first bearer and the second bearer is the first type of bearer and the other is the second type of bearer; the second bearer is associated with the first cell group;

[0024] Before transmitting the first information, a primary path of a PDCP entity of SRB1 is set to be for the second bearer;

[0025] Wherein, the first signaling indicates that SRB1 is simultaneously associated with the first bearer and the second bearer and a primary path of a PDCP entity of SRB1 is for the first bearer; SRB1 is not configured with PDCP repetition; the first information includes a first measurement result; the first information is used to indicate whether the first bearer is the second type of bearer.

[0026] Specifically, according to an aspect of the present application, first signaling is received, the first signaling is used to configure a second bearer; the second bearer is associated with the first cell group; after the behavior detects that the first bearer fails, it is detected that the second bearer fails;

[0027] in response to the behavior detecting the second bearer failure, initiating an RRC reestablishment procedure, suspending SRB1 in conjunction with the RRC reestablishment procedure, performing any one of cell selection and relay selection; sending a third message, the third message being used to indicate the second bearer failure;

[0028] wherein the first bearer is the first type of bearer; the second bearer is the second type of bearer; the first bearer is not recovered when the behavior detects the second bearer failure; the RLC entity associated with the first type of bearer is a RLC entity of a Uu interface; the RLC entity associated with the second bearer is a RLC entity of a PC5 interface.

[0029] Specifically, according to an aspect of the present application, a first signaling is received, the first signaling being used to configure a second bearer; the second bearer is associated with the first cell group; after the behavior detects the first bearer failure, the second bearer failure is detected;

[0030] in response to the behavior detecting the second bearer failure, initiating an RRC reestablishment procedure, suspending SRB1 in conjunction with the RRC reestablishment procedure, performing any one of cell selection and relay selection; sending a third message, the third message being used to indicate the second bearer failure;

[0031] wherein the first bearer is the second type of bearer; the second bearer is the first type of bearer; the first bearer is not recovered when the behavior detects the second bearer failure; the RLC entity associated with the first type of bearer is a RLC entity of a Uu interface; the RLC entity associated with the second bearer is a RLC entity of a PC5 interface.

[0032] Specifically, according to an aspect of the present application, in response to the behavior detecting the first bearer failure, the first information is sent according to whether the first bearer is the first type of bearer or the second type of bearer;

[0033] wherein the meaning of the sentence that the first information is sent according to whether the first bearer is the first type of bearer or the second type of bearer is: when the first bearer is the first type of bearer, initiating a failure information transmission procedure, the behavior initiating the failure information transmission procedure including sending the first information; when the first bearer is the second type of bearer, initiating a sidelink UE information transmission procedure for NR sidelink communication, the behavior initiating the sidelink UE information transmission procedure for NR sidelink communication including sending the first information.

[0034] Specifically, according to an aspect of the present application, the first node is an Internet of Things terminal.

[0035] Specifically, according to an aspect of the present application, the first node is a relay.

[0036] Specifically, according to an aspect of the present application, the first node is a U2N remote UE.

[0037] Specifically, according to an aspect of the present application, the first node is a vehicle terminal.

[0038] Specifically, according to an aspect of the present application, the first node is an aircraft.

[0039] Specifically, according to an aspect of the present application, the first node is a mobile phone.

[0040] Specifically, according to an aspect of the present application, the first node is a communication terminal supporting multi-SIM card communication.

[0041] The present application discloses a first node used for wireless communication, comprising:

[0042] a first receiver, detecting that a first bearer is failed; the first bearer is associated with a first cell group; in response to the behavior of detecting that the first bearer is failed, performing a first operation set, the first operation set is related to the type of the first bearer;

[0043] a first transmitter, in response to the behavior of detecting that the first bearer is failed, sending a first information; the first information is used to indicate that the first bearer is failed; in response to all conditions in a first condition set being met, sending a second message; the second message indicates that there is available information;

[0044] wherein, the first cell group is a master cell group; the first condition set includes that a first state variable stores available information; the meaning of the sentence that the first operation set is related to the type of the first bearer is: when the first bearer is a first type of bearer, the first operation set includes at least one of reestablishing an RLC entity associated with the first bearer and storing information in the first state variable for the failure of the first bearer; when the first bearer is a second type of bearer, the first operation set includes at least releasing an RLC entity associated with the first bearer.

[0045] As an embodiment, compared with the conventional scheme, the present application has the following advantages:

[0046] Supporting relay, especially network optimization when using L2 U2N (UE to Network) relay UE, for example, rich and accurate information about the occurrence of bearer failure when L2 U2N relay can be provided to the network.

[0047] Supporting simultaneous configuration of direct and indirect paths, the network optimization based on failure of one of them, in particular, when the direct path fails first, and before the direct path has recovered, the indirect path also fails, recording information about the failure of the direct path accurately.

[0048] The details of the path failure can be recorded more accurately, which is conducive to accurate and targeted network optimization. The use of the indirect path is also recorded in the information about the path failure.

[0049] Supporting simultaneous use of direct and indirect paths, only when both the direct and indirect paths fail, i.e. there is no available path, the cell group is considered to fail, which improves the reliability of communication. BRIEF DESCRIPTION OF DRAWINGS

[0050] Other features, objects and advantages of the present application will become more apparent from the following detailed description of non-limiting embodiments thereof, read in conjunction with the accompanying drawings:

[0051] Figure 1 A flowchart showing detection of a first bearer failure, performing a first set of operations, sending a first message, and sending a second message according to one embodiment of the present application is shown;

[0052] Figure 2 A schematic diagram showing a network architecture according to one embodiment of the present application is shown;

[0053] Figure 3 A schematic diagram showing an embodiment of a wireless protocol architecture of a user plane and a control plane according to one embodiment of the present application is shown;

[0054] Figure 4 A schematic diagram showing a first communication device and a second communication device according to one embodiment of the present application is shown;

[0055] Figure 5 A flowchart showing wireless signal transmission according to one embodiment of the present application is shown;

[0056] Figure 6 A flowchart showing wireless signal transmission according to one embodiment of the present application is shown;

[0057] Figure 7 A schematic diagram showing a protocol stack of a relay communication according to one embodiment of the present application is shown;

[0058] Figure 8 A schematic diagram showing a topology according to one embodiment of the present application is shown;

[0059] Figure 9A schematic diagram is shown illustrating how first information, according to one embodiment of this application, is used to indicate a first bearer failure;

[0060] Figure 10 A schematic diagram is shown illustrating how first information, according to an embodiment of this application, is used to indicate whether a first bearer is a second type of bearer;

[0061] Figure 11 A schematic diagram is shown illustrating how a third message, according to one embodiment of this application, is used to indicate a second bearer failure;

[0062] Figure 12 A schematic diagram of a processing apparatus for a first node according to an embodiment of this application is illustrated. Implementation

[0063] The technical solution of this application will be further described in detail below with reference to the accompanying drawings. It should be noted that, unless otherwise specified, the embodiments and features in the embodiments of this application can be arbitrarily combined with each other.

[0064] Embodiment 1

[0065] Example 1 illustrates a flowchart of a process according to an embodiment of this application, including detecting a first bearer failure, executing a first set of operations, sending a first message, and sending a second message, as shown in the attached diagram. Figure 1 As shown. (Attached) Figure 1 In the diagram, each box represents a step. It is particularly important to emphasize that the order of the boxes in the diagram does not represent the chronological order of the steps they represent.

[0066] In Embodiment 1, the flowchart of the first node in this application detecting a first bearer failure in step 101, executing a first set of operations in step 102, sending first information in step 103, and sending a second message in step 104 is as follows:

[0067] Wherein, the first bearer is associated with a first cell group; as a response to the detection of the first bearer failure, a first set of operations is executed, the first set of operations being related to the type of the first bearer;

[0068] The first node, in response to the detection of a first bearer failure, sends a first message; the first message is used to indicate the first bearer failure, and in response to all conditions in a first set of conditions being met, sends a second message; the second message indicates that information is available.

[0069] The first cell group is a master cell group; the first condition set includes a first state variable storing available information; the meaning of the sentence "the first operation set is related to the type of the first bearer" is: when the first bearer is a first type of bearer, the first operation set includes at least one of reestablishing an RLC entity associated with the first bearer and storing in the first state variable information invalid for the first bearer; when the first bearer is a second type of bearer, the first operation set includes at least releasing an RLC entity associated with the first bearer.

[0070] As an embodiment, the first node is a UE (User Equipment).

[0071] As an embodiment, the first node is a UE (User Equipment).

[0072] As an embodiment, the direct path refers to a UE-to-network transmission path, and transmission through the direct path means that data is sent between a remote UE of UE-to-network (U2N) and a network without passing through a relay.

[0073] As a sub-embodiment of this embodiment, the data includes higher layer data and signaling.

[0074] As a sub-embodiment of this embodiment, the data includes RRC signaling.

[0075] As a sub-embodiment of this embodiment, the data includes a bit string or a bit block.

[0076] As a sub-embodiment of this embodiment, the data only includes signaling or data carried by an RB (radio bearer).

[0077] As an embodiment, the indirect path refers to a UE-to-network transmission path, and transmission through the indirect path means that data is forwarded between a remote UE of UE-to-network (U2N) and a network through a relay UE of UE-to-network (U2N).

[0078] As a sub-embodiment of this embodiment, the data includes higher layer data and signaling.

[0079] As a sub-embodiment of this embodiment, the data includes RRC signaling.

[0080] As a sub-embodiment of this embodiment, the data includes a bit string or a bit block.

[0081] As a sub-example of this example, the data includes only signaling or data carried by a radio bearer (RB).

[0082] As an example, a wireless link is either the direct path or a non-direct path.

[0083] As an example, a U2N relay UE refers to a UE that provides functionality to support connectivity of a U2N remote UE to a network.

[0084] As an example, a U2N remote UE refers to a UE that needs to go through a U2N relay UE for communication with a network.

[0085] As an example, a U2N remote UE refers to a UE that needs to go through a U2N relay UE for communication with a network.

[0086] As an example, a U2N remote UE refers to a UE that supports relay service for communication with a network.

[0087] As an example, a U2N relay is a U2N relay UE.

[0088] As an example, both the U2N relay and the U2N remote node are in RRC connected state when communicating unicast service with a network.

[0089] As an example, the U2N relay UE can be in any RRC state, including RRC connected state, RRC idle state, and RRC inactive state, when the U2N remote UE is in RRC idle state or RRC inactive state.

[0090] As an example, not transmitting through a direct path is equivalent to transmitting through a non-direct path.

[0091] As an example, not transmitting through a direct path includes transmitting through a relay.

[0092] As an example, transmitting through a direct path is or includes not transmitting through a relay.

[0093] As an example, transmitting through a direct path is or includes not transmitting through a relay hop.

[0094] As an example, a U2N relay UE is a UE that provides functionality to support connectivity of a U2N remote UE to a network.

[0095] As a sub-example of this example, a U2N relay UE is a UE.

[0096] As a sub-example of this example, the U2N relay UE provides a relay service to the U2N remote UE to the network.

[0097] As an example, the U2N remote UE is a UE that communicates with the network through the U2N relay UE.

[0098] As an example, the direct mode is a mode that uses the direct path.

[0099] As an example, the direct mode is a mode that the U2N remote UE uses the direct path to communicate with the network.

[0100] As an example, the direct mode is a mode that the U2N remote UE uses the direct path to transmit RRC signaling or establish an RRC connection between the U2N remote UE and the network.

[0101] As an example, the indirect mode is a mode that uses the indirect path.

[0102] As an example, the indirect mode is a mode that uses the indirect path.

[0103] As an example, the direct mode is a mode that the U2N remote UE uses the indirect path to communicate with the network.

[0104] As an example, the direct mode is a mode that the U2N remote UE uses the indirect path to transmit RRC signaling or establish an RRC connection between the U2N remote UE and the network.

[0105] As an embodiment, the serving cell is or includes a cell in which the UE is camped. Performing a cell search includes the UE searching for a suitable cell of a selected PLMN (Public Land Mobile Network) or SNPN (Stand-alone Non-Public Network) that provides available service, monitoring control channels of the suitable cell, which is defined as camping on a cell; that is, a camped cell is a serving cell for the UE. Camping on a cell in RRC IDLE or RRC INACTIVE state has the following benefits: the UE can receive system information from the PLMN or SNPN; if the UE wishes to establish an RRC connection or continue a suspended RRC connection after registration, the UE can do so by performing initial access on the control channels of the camped cell; the network can page the UE; the UE can receive ETWS (Earthquake and Tsunami Warning System) and CMAS (Commercial Mobile Alert System) notifications.

[0106] As an embodiment, for a U2N remote node, the serving cell is or includes a cell in which the U2N relay is camped or connected.

[0107] As an embodiment, for a UE in RRC CONNECTED state without CA / DC (carrier aggregation / dual connectivity) configured, there is only one serving cell including a primary cell. For a UE in RRC CONNECTED state with CA / DC (carrier aggregation / dual connectivity) configured, the serving cells are used to indicate a set of cells including a special cell (SpCell) and all secondary cells. The primary cell (PCell) is a MCG (Master Cell Group) cell operating on a primary frequency, on which the UE performs initial connection establishment procedure or initiates connection re-establishment. For dual connectivity operation, the special cell refers to the PCell of the MCG or the PSCell (Primary SCG Cell) of the SCG (Secondary Cell Group); if not dual connectivity operation, the special cell refers to the PCell.

[0108] As one embodiment, the frequency at which the SCell (Secondary Cell) operates is from the frequency.

[0109] As one embodiment, the individual content of an information element is referred to as a field.

[0110] As one embodiment, MR-DC (Multi-Radio Dual Connectivity) refers to dual connectivity of E-UTRA and NR nodes, or dual connectivity between two NR nodes.

[0111] As one embodiment, in MR-DC, the radio access node that provides the control plane connection to the core network is the master node, which can be a master eNB, a master ng-eNB, or a master gNB.

[0112] As one embodiment, MCG refers to, in MR-DC, a set of serving cells associated with the master node, including the SpCell, and, optionally, one or more SCells.

[0113] As one embodiment, the PCell is the SpCell of the MCG.

[0114] As one embodiment, the PSCell is the SpCell of the SCG.

[0115] As one embodiment, in MR-DC, the radio access node that does not provide the control plane connection to the core network, but provides additional resources to the UE, is the secondary node. The secondary node can be an en-gNB, a secondary ng-eNB, or a secondary gNB.

[0116] As one embodiment, in MR-DC, the set of serving cells associated with the secondary node is the SCG (Secondary Cell Group), including the SpCell and, optionally, one or more SCells.

[0117] As one embodiment, the access stratum functionality that enables V2X (Vehicle-to-Everything) communication defined in 3GPP standard TS 23.285 is V2X sidelink communication, where the V2X sidelink communication occurs between proximal UEs and uses E-UTRA technology without traversing a network node.

[0118] As one embodiment, the at least enabled access layer functionality defined for V2X (Vehicle-to-Everything) communication in 3GPP standard TS 23.287 is NR sidelink communication, wherein the NR sidelink communication occurs between two or more UEs in proximity and uses NR technology but does not traverse a network node.

[0119] As one embodiment, the sidelink is a direct communication link between UEs-to-UEs using a sidelink resource allocation mode, physical layer signals or channels, and physical layer procedures.

[0120] As one embodiment, not in or not within coverage equals out of coverage.

[0121] As one embodiment, within coverage equals in-coverage.

[0122] As one embodiment, out of coverage equals out-of-coverage.

[0123] As one embodiment, the first node is a U2N remote node.

[0124] As one embodiment, the PDCP entities corresponding to the radio bearers between the UE and the network are respectively located in the UE and the network.

[0125] As one embodiment, the direct path is a communication link or channel or bearer used for the direct path transmission.

[0126] As one embodiment, the direct path transmission refers to data carried by at least a SRB (Signaling radio bearer) between the UE and the network without relaying or forwarding by other nodes.

[0127] As one embodiment, the direct path transmission refers to RLC bearers associated with at least a SRB (Signaling radio bearer) between the UE and the network are respectively terminated at the UE and the network.

[0128] As one embodiment, the direct path transmission refers to RLC entities associated with at least a SRB (Signaling radio bearer) between the UE and the network are respectively terminated at the UE and the network.

[0129] As one embodiment, the direct path transmission refers to a direct communication link between the UE and the network.

[0130] As one embodiment, the direct path transmission refers to the existence of a Uu interface between the UE and the network.

[0131] As one embodiment, the direct path transmission refers to the existence of a MAC layer of a Uu interface between the UE and the network, and the MAC layer of the Uu interface carries RRC signaling.

[0132] As one embodiment, the direct path transmission refers to the existence of a physical layer of a Uu interface between the UE and the network.

[0133] As one embodiment, the direct path transmission refers to the existence of a logical channel and / or a transport channel between the UE and the network.

[0134] As one embodiment, the non-direct path is a non-direct path or a communication link or a channel or a bearer used when the non-direct path transmission is performed.

[0135] As one embodiment, the non-direct path transmission refers to the relaying or forwarding of data carried by at least a SRB (Signaling radio bearer) between the UE and the network through another node.

[0136] As one embodiment, the non-direct path transmission refers to that the RLC bearers associated with at least a SRB (Signaling radio bearer) between the UE and the network are respectively terminated at the UE and the other node, the other node and the network.

[0137] As one embodiment, the non-direct path transmission refers to that the RLC entities associated with at least a SRB (Signaling radio bearer) between the UE and the network are respectively terminated at the UE and the other node, the other node and the network.

[0138] As one embodiment, the meaning of the phrase at least SRB includes at least one of {SRB0, SRB1, SRB2, SRB3}.

[0139] As one embodiment, the meaning of the phrase at least SRB includes SRB and DRB (data radio bearer).

[0140] As one embodiment, the non-direct path transmission refers to the non-existence of a direct communication link between the UE and the network.

[0141] As one embodiment, the non-direct path transmission refers to the non-existence of a MAC layer of a Uu interface between the UE and the network.

[0142] As one embodiment, the non-direct path transmission refers to that there is no physical layer of Uu interface between the UE and the network.

[0143] As one embodiment, the non-direct path transmission refers to that there is no logical channel and no transport channel between the UE and the network.

[0144] As one embodiment, the network comprises a radio access network (RAN) and / or a serving cell and / or a base station.

[0145] As one embodiment, the phrase the UE in the network comprises the first node.

[0146] As one embodiment, the other node comprises a relay node or other UE.

[0147] As one embodiment, when using direct path transmission, the UE can send physical layer signaling to the network; when using non-direct path transmission, the UE cannot send or directly send physical layer signaling to the network;

[0148] As one embodiment, when using direct path transmission, the UE can send MAC CE to the network; when using non-direct path transmission, the UE cannot send or directly send MAC CE to the network;

[0149] As one embodiment, when using direct path transmission, there is no other protocol layer between the PDCP layer and the RLC layer of the first node; when using non-direct path transmission, there is other protocol layer between the PDCP layer and the RLC layer of the first node.

[0150] As one sub-embodiment of this embodiment, the other protocol layer is or comprises an adaptation layer.

[0151] As one embodiment, when using direct path transmission, the network directly schedules uplink transmission of the first node through DCI; when using non-direct path transmission, the network does not directly schedule uplink transmission of the first node through DCI.

[0152] As one embodiment, when using direct path transmission, the SRB of the first node is associated with an RLC entity and / or an RLC layer and / or an RLC bearer; when using non-direct path transmission, the SRB of the first node is associated with an RLC entity of a PC5 interface.

[0153] As one embodiment, when using direct path transmission, the SRB of the first node has a mapping relationship with an RLC entity of a Uu interface; when using non-direct path transmission, the SRB of the first node has a mapping relationship with an RLC entity of a PC5 interface.

[0154] As one embodiment, the first node and the network have a direct path and / or a non-direct path.

[0155] As one embodiment, switching from a direct path to a non-direct path means that the non-direct path is started to be used while the direct path is stopped to be used.

[0156] As one embodiment, switching from a direct path to a non-direct path means that direct path transmission is stopped while non-direct path transmission is started to be used.

[0157] As one embodiment, switching from a direct path to a non-direct path means that direct path transmission is changed to non-direct path transmission.

[0158] As one embodiment, switching from a direct path to a non-direct path means that the first node associates the SRB with the RLC entity of the PC5 interface while releasing the RLC entity of the Uu interface associated with the SRB.

[0159] As one embodiment, switching from a direct path to a non-direct path means that the first node associates the SRB and the DRB with the RLC entity of the PC5 interface while releasing the RLC entity of the Uu interface associated with the SRB and the DRB.

[0160] As one embodiment, switching from a non-direct path to a direct path means that the direct path is started to be used while the non-direct path is stopped to be used.

[0161] As one embodiment, switching from a non-direct path to a direct path means that direct path transmission is started to be used while non-direct path transmission is stopped.

[0162] As one embodiment, switching from a non-direct path to a direct path means that non-direct path transmission is changed to direct path transmission.

[0163] As one embodiment, switching from a non-direct path to a direct path means that the first node releases the RLC entity of the PC5 interface associated with the SRB while associating the SRB with the RLC entity of the Uu interface.

[0164] As one embodiment, switching from a non-direct path to a direct path means that the first node releases all RLC entities of the PC5 interface associated with the DRB while associating the DRB with the RLC entity of the Uu interface.

[0165] As one embodiment, the first node supports switching from a non-direct path to a non-direct path.

[0166] As one embodiment, when the first node uses the indirect path, the relay used by the indirect path is a first relay.

[0167] As one embodiment, the relay in the present application refers to a U2N relay UE.

[0168] As one embodiment, the first node is in an RRC connected state.

[0169] As one embodiment, the first node in the present application does not use DC (dual connectivity).

[0170] As one embodiment, the first node in the present application is not configured with DC (dual connectivity).

[0171] As one embodiment, the first node in the present application has only one cell group.

[0172] As one embodiment, the first node in the present application has only one cell group, i.e., a master cell group (MCG).

[0173] As one embodiment, the first node in the present application is not configured with a secondary cell group (SCG).

[0174] As one embodiment, the relay in the present application refers to a L2 U2N relay UE.

[0175] As one embodiment, the first node in the present application uses both the direct path and the indirect path.

[0176] As one embodiment, the first type of bearer is a direct path; and the second type of bearer is an indirect path.

[0177] As one embodiment, the first type of bearer is an indirect path; and the second type of bearer is a direct path.

[0178] As one embodiment, the first type of bearer is an RLC bearer; and the second type of bearer is a PC5 RLC bearer.

[0179] As one embodiment, the first type of bearer is a Uu RLC bearer; and the second type of bearer is a PC5 RLC bearer.

[0180] As one embodiment, the first type of bearer is a primary link radio link; and the second type of bearer is a secondary link radio link.

[0181] As one embodiment, the first type of bearer is a DRB; and the second type of bearer is a MRB.

[0182] As one embodiment, the first type of bearer is SRB; the second type of bearer is DRB.

[0183] As one embodiment, the first type of bearer is SRB; the second type of bearer is MRB.

[0184] As one embodiment, the first type of bearer is MRB; the second type of bearer is DRB or SRB.

[0185] As one embodiment, the first type of bearer is a radio link between the first node and the first cell group; the second type of bearer is a sidelink radio link between the first node and an L2 U2N relay UE and the L2 U2N relay UE is an L2 U2N relay between the first node and the first cell group.

[0186] As one embodiment, the first type of bearer and the second type of bearer are both bearers of AS layer.

[0187] As one embodiment, one of the first type of bearer and the second type of bearer is a bearer of AS layer, and the other is a bearer of NAS layer.

[0188] As one sub-embodiment of this embodiment, the first type of bearer is a bearer of AS layer, and the second type of bearer is a bearer of NAS layer.

[0189] As one sub-embodiment of this embodiment, the second type of bearer is a bearer of AS layer, and the first type of bearer is a bearer of NAS layer.

[0190] As one embodiment, the first type of bearer is a channel of a primary link, and the second type of bearer is a channel of a secondary link.

[0191] As one sub-embodiment of this embodiment, the primary link is a link without relay between the first node and a base station of the first cell group or the first cell group.

[0192] As one embodiment, the first type of bearer is a physical channel of a primary link, and the second type of bearer is a physical channel of a secondary link.

[0193] As one sub-embodiment of this embodiment, the primary link is a link without relay between the first node and a base station of the first cell group or the first cell group.

[0194] As one embodiment, the first type of bearer is a transport channel of a primary link, and the second type of bearer is a transport channel of a secondary link.

[0195] As a sub-example of this example, the primary link is a non-relayed link between the first node and a base station of the first cell group or first cell group.

[0196] As an example, the first type of bearer is a logical channel of a primary link and the second type of bearer is a logical channel of a secondary link.

[0197] As a sub-example of this example, the primary link is a non-relayed link between the first node and a base station of the first cell group or first cell group.

[0198] As an example, the first bearer is a direct path.

[0199] As an example, the first bearer is a non-direct path.

[0200] As an example, the first bearer is a radio bearer.

[0201] As an example, the first bearer is an RLC bearer.

[0202] As an example, the first bearer is a secondary link RLC bearer.

[0203] As an example, the first bearer is a unicast bearer.

[0204] As an example, the first bearer is a broadcast or multicast or groupcast bearer.

[0205] As an example, the first bearer is a radio link.

[0206] As an example, the first bearer is a secondary link.

[0207] As an example, the first bearer is a communication link.

[0208] As an example, the first bearer is a channel.

[0209] As an example, the first bearer is a network channel.

[0210] As an example, the first bearer belongs to an AS layer.

[0211] As an example, the first bearer is a radio link between the first node and the first cell group.

[0212] As one embodiment, the first bearer is a sidelink radio link between the first node and a L2 U2N relay UE, and the first bearer is associated with at least one of a DRB or a SRB or a MRB of the first node, and the DRB or the SRB or the MRB of the first node is a radio bearer between the first node and the first cell group.

[0213] As one embodiment, the first bearer is a sidelink radio link between the first node and a L2 U2N relay UE, and the first bearer is used for transmitting PDCP PDUs for the first cell group.

[0214] As one embodiment, the first bearer is a direct unicast link between the first node and a L2 U2N relay UE, and the direct unicast link is used for transmitting data between the first node and the first cell group.

[0215] As one embodiment, the phrase the first bearer fails means that the first bearer experiences a radio link failure.

[0216] As one embodiment, the phrase the first bearer fails means that the first bearer experiences a sidelink radio link failure.

[0217] As one embodiment, the phrase the first bearer fails means that the first bearer experiences a failure.

[0218] As one embodiment, the phrase the first bearer fails means that the first bearer experiences an unrecoverable failure.

[0219] As one embodiment, the phrase the first bearer fails means that the first bearer cannot continue to be used.

[0220] As one embodiment, the phrase the first bearer fails means that the first bearer has to be released or suspended.

[0221] As one embodiment, the phrase the first bearer fails means that a link to which the first bearer belongs experiences a failure.

[0222] As one embodiment, the phrase the first bearer fails means that the first bearer is invalid or illegal.

[0223] As one embodiment, the phrase the first bearer fails means that the first bearer needs to be stopped from being used.

[0224] As one embodiment, the phrase the first bearer fails means that the first bearer needs to be stopped from transmitting data on the first bearer.

[0225] As one embodiment, the phrase the first bearer is deactivated means that data reception on the first bearer needs to be stopped.

[0226] As one embodiment, the phrase the first bearer is deactivated means that data transmission on the first bearer needs to be stopped, but data reception on the first bearer can continue.

[0227] As one embodiment, the phrase the first bearer is deactivated means that a direct unicast link related to the first bearer needs to be released.

[0228] As one embodiment, the first cell group is a MCG.

[0229] As one embodiment, the first cell group only includes a PCell.

[0230] As one embodiment, the first cell group includes a PCell and at least one SCell.

[0231] As one embodiment, the phrase the first bearer is associated with a first cell group means that the first bearer is a bearer between the first node and the first cell group.

[0232] As one embodiment, the phrase the first bearer is associated with a first cell group means that the first bearer terminates at the first node and the first cell group.

[0233] As one embodiment, the phrase the first bearer is associated with a first cell group means that the first bearer terminates at the first node and a base station of the first cell group.

[0234] As one embodiment, the phrase the first bearer is associated with a first cell group means that a PDCP entity corresponding to the first bearer is at the first node and the first cell group, respectively.

[0235] As one embodiment, the phrase the first bearer is associated with a first cell group means that an RLC entity corresponding to the first bearer is at the first node and the first cell group, respectively.

[0236] As one embodiment, the phrase the first bearer is associated with a first cell group means that a MAC corresponding to or used by or mapped by the first bearer is for the first cell group.

[0237] As one embodiment, the phrase the first bearer is associated with a first cell group means that the first bearer is used for transmitting PDCP PDUs between the first node and the first cell group.

[0238] As one embodiment, the phrase "the first bearer is associated with the first cell group" means that the first bearer is used for transmitting PDCP SDUs between the first node and the first cell group.

[0239] As one embodiment, the phrase "the first bearer is associated with the first cell group" means that the first bearer is used for transmitting RLC PDUs between the first node and the first cell group.

[0240] As one embodiment, the phrase "the first bearer is associated with the first cell group" means that the first bearer is used for transmitting MAC PDUs between the first node and the first cell group.

[0241] As one embodiment, the phrase "the first bearer is associated with the first cell group" means that the first bearer is used for transmitting data between the first node and the first cell group.

[0242] As one embodiment, the phrase "the first bearer is associated with the first cell group" means that at least SRB1 between the first node and the first cell group uses the first bearer.

[0243] As one embodiment, the phrase "the first bearer is associated with the first cell group" means that at least SRB1 between the first node and the first cell group has a mapping relationship with the first bearer.

[0244] As one embodiment, the phrase "the first bearer is associated with the first cell group" means that the first bearer is a bearer between the first node and an L2 U2N relay UE, and the L2 U2N relay UE is a relay between the first node and the first cell group.

[0245] As one embodiment, the phrase "the first bearer is associated with the first cell group" means that the first bearer is a bearer between the first node and an L2 U2N relay UE, and the L2 U2N relay UE forwards data between the first node and the first cell group.

[0246] As one embodiment, the phrase "the first bearer is associated with the first cell group" means that the first bearer is an RLC bearer between the first node and an L2 U2N relay UE, and the L2 U2N relay UE is a relay between the first node and the first cell group.

[0247] As one embodiment, the phrase "the first bearer is associated with the first cell group" means that the first bearer is an RLC bearer between the first node and an L2 U2N relay UE, and the L2 U2N relay UE forwards data between the first node and the first cell group.

[0248] As one embodiment, the phrase the first bearer is associated with the first cell group means that the first bearer is a sidelink radio link between the first node and an L2 U2N relay UE, the L2 U2N relay UE being a relay between the first node and the first cell group.

[0249] As one embodiment, the phrase the first bearer is associated with the first cell group means that the first bearer is a sidelink radio link between the first node and an L2 U2N relay UE, the L2 U2N relay UE forwarding data between the first node and the first cell group.

[0250] As one embodiment, the phrase the first bearer is associated with the first cell group means that the first bearer is an RLC bearer between the first node and an L2 U2N relay UE, the first bearer being used to carry at least SRB1, the at least SRB1 being an SRB between the first node and the first cell group.

[0251] As one embodiment, the first set of operations includes at least one operation.

[0252] As one embodiment, the second message is an RRC message.

[0253] As one embodiment, the second message is used to indicate that an operation of one RRC layer is performed.

[0254] As one embodiment, the second message includes RRCReconfigurationComplete.

[0255] As one embodiment, the second message includes RRCResumeComplete.

[0256] As one embodiment, the second message includes RRCSetupComplete.

[0257] As one embodiment, the second message includes RRCReestablishmentComplete.

[0258] As one embodiment, the phrase the second message indicates that there is available information means that the first node has or stores available information.

[0259] As one embodiment, the phrase the second message indicates that there is available information means that the available information includes information that the first bearer is invalid.

[0260] As one embodiment, the meaning of the phrase that the second message indicates that there is available information is that the available information includes information about failure of the first type of bearer.

[0261] As one embodiment, the meaning of the phrase that the second message indicates that there is available information is that the available information includes radio link failure information.

[0262] As one embodiment, the meaning of the phrase that the second message indicates that there is available information is that the available information includes cell handover failure information.

[0263] As one embodiment, the meaning of the phrase that the second message indicates that there is available information is that the available information includes path switch failure information.

[0264] As one embodiment, the meaning of the phrase that the second message indicates that there is available information is that the second message includes an enumerated field with a value of true to indicate that there is available information.

[0265] As one embodiment, the meaning of the phrase that the second message indicates that there is available information is that the second message includes a field with a name that includes available with a value of true to indicate that there is available information.

[0266] As one embodiment, the meaning of the phrase that the second message indicates that there is available information is that the UE-MeasurementsAvailable field of the second message indicates that there is available information.

[0267] As one embodiment, the meaning of the phrase that the second message indicates that there is available information is that the rlf-InfoAvailable field of the UE-MeasurementsAvailable field of the second message indicates that there is available information.

[0268] As one embodiment, the meaning of the phrase that the second message indicates that there is available information is that there is available information about failure of the first bearer.

[0269] As one embodiment, the meaning of the phrase that the second message indicates that there is available information is that there is available information about failure of the first type of bearer.

[0270] As one embodiment, the meaning of the phrase that the second message indicates that there is available information is that there is available information about failure of the second type of bearer.

[0271] As one embodiment, the meaning of the phrase that the second message indicates that there is available information is that the information stored in the first state variable about failure of the first bearer is the available information.

[0272] As one embodiment, the meaning of the phrase "the second message indicates that there is available information" is that the information stored in the first status variable related to the failure of the first type of bearer is the available information.

[0273] As one embodiment, the RLC entity associated with the first bearer refers to that the first bearer is an RLC bearer, and the RLC entity associated with the first bearer is the RLC entity corresponding to the RLC bearer.

[0274] As one embodiment, the RLC entity associated with the first bearer refers to that the first bearer is a sidelink RLC bearer, and the RLC entity associated with the first bearer is the RLC entity of the PC5 interface corresponding to the sidelink RLC bearer.

[0275] As one embodiment, the RLC entity associated with the first bearer refers to that the first bearer is a radio bearer, and the RLC entity associated with the first bearer is the RLC entity corresponding to the RLC bearer carrying the first bearer.

[0276] As one embodiment, the RLC entity associated with the first bearer refers to that the first bearer is a radio bearer, and the RLC entity associated with the first bearer is the RLC entity of the PC5 interface corresponding to the sidelink RLC bearer carrying the first bearer.

[0277] As one embodiment, the RLC entity associated with the first bearer refers to that the first bearer is a physical channel, and the RLC entity associated with the first bearer is the RLC entity generating the RLC PDU carried by the first bearer.

[0278] As one embodiment, the RLC entity associated with the first bearer refers to that the first bearer is a transport channel, and the RLC entity associated with the first bearer is the RLC entity generating the RLC PDU carried by the first bearer.

[0279] As one embodiment, the RLC entity associated with the first bearer refers to that the first bearer is a logical channel, and the RLC entity associated with the first bearer is the RLC entity corresponding to the first bearer.

[0280] As one embodiment, the RLC entity associated with the first bearer refers to that the first bearer is a sidelink physical channel, and the RLC entity associated with the first bearer is the RLC entity generating the RLC PDU carried by the first bearer.

[0281] As an embodiment, the RLC entity associated with the first bearer refers to: the first bearer is a sidelink transport channel, the RLC entity associated with the first bearer is an RLC entity generating RLC PDUs carried by the first bearer.

[0282] As an embodiment, the RLC entity associated with the first bearer refers to: the first bearer is a sidelink logical channel, the RLC entity associated with the first bearer is an RLC entity corresponding to the first bearer.

[0283] As an embodiment, the RLC entity associated with the first bearer refers to: the first bearer is a radio link for the first cell group, the RLC entity associated with the first bearer is an RLC entity generating RLC PDUs transmitted by the first bearer.

[0284] As an embodiment, the RLC entity associated with the first bearer refers to: the first bearer is a sidelink radio link for an L2 U2N relay UE, the L2 U2N relay UE is an L2 U2N relay UE between the first node and the first cell group, the RLC entity associated with the first bearer is an RLC entity generating RLC PDUs transmitted by the first bearer for carrying PDCP PDUs for the first cell group.

[0285] As an embodiment, the RLC entity associated with the first bearer comprises an RLC entity of a Uu interface.

[0286] As an embodiment, the RLC entity associated with the first bearer comprises an RLC entity of a PC5 interface.

[0287] As an embodiment, the RLC entity associated with the first bearer is an RLC entity having a mapping relationship with the first bearer.

[0288] As an embodiment, the RLC entity associated with the first bearer is an RLC entity encapsulating data on the first bearer.

[0289] As an embodiment, the RLC entity associated with the first bearer is an RLC entity generating data carried by the first bearer.

[0290] As an embodiment, the first state variable is a state variable of the first node.

[0291] As an embodiment, the name of the first state variable comprises “var”.

[0292] As an embodiment, the name of the first state variable comprises “report”.

[0293] As one embodiment, the name of the first status variable comprises "relay".

[0294] As one embodiment, the name of the first status variable comprises "path".

[0295] As one embodiment, the name of the first status variable comprises "relay".

[0296] As one embodiment, the first status variable is VarRLF-Report.

[0297] As one embodiment, the first information is sent through an RRC message.

[0298] As one embodiment, the first information is sent through a MAC CE.

[0299] As one embodiment, when the first bearer is the first type of bearer, the first information is sent through a MAC CE; when the first bearer is the second type of bearer, the first information is sent through an RRC message.

[0300] As one embodiment, the behavior of storing information about the failure of the first bearer in the first status variable comprises storing the identity of the first cell group.

[0301] As one embodiment, the behavior of storing information about the failure of the first bearer in the first status variable comprises storing the identity of the PCell of the first cell group.

[0302] As one embodiment, the behavior of storing information about the failure of the first bearer in the first status variable comprises storing the cause of the failure of the first bearer.

[0303] As one embodiment, the behavior of storing information about the failure of the first bearer in the first status variable comprises storing the type of the failure of the first bearer.

[0304] As one embodiment, the behavior of storing information about the failure of the first bearer in the first status variable comprises storing whether a second type of bearer is used.

[0305] As one embodiment, the behavior of storing information about the failure of the first bearer in the first status variable comprises storing measurement results.

[0306] As one embodiment, the behavior of storing information about the failure of the first bearer in the first status variable comprises storing measurement results of configured measurement objects.

[0307] As an embodiment, said behavior storing in said first state variable information for failure of said first bearer comprises storing an identity of a used L2 U2N relay UE.

[0308] As an embodiment, said first node sends said first information on a second bearer; said second bearer is associated with said first cell group; one of said first bearer and said second bearer is said first type of bearer and the other is said second type of bearer;

[0309] wherein the RLC entity associated with said first type of bearer is a RLC entity of a Uu interface; the RLC entity associated with said second type of bearer is a RLC entity of a PC5 interface; said first type of bearer uses a primary link; said second type of bearer uses a secondary link.

[0310] As an embodiment, the phrase said second bearer is associated with a first cell group means that said second bearer is a bearer between said first node and said first cell group.

[0311] As an embodiment, the phrase said second bearer is associated with a first cell group means that said second bearer terminates at said first node and said first cell group.

[0312] As an embodiment, the phrase said second bearer is associated with a first cell group means that said second bearer terminates at said first node and a base station of said first cell group.

[0313] As an embodiment, the phrase said second bearer is associated with a first cell group means that a PDCP entity corresponding to said second bearer is at said first node and said first cell group, respectively.

[0314] As an embodiment, the phrase said second bearer is associated with a first cell group means that a RLC entity corresponding to said second bearer is at said first node and said first cell group, respectively.

[0315] As an embodiment, the phrase said second bearer is associated with a first cell group means that a MAC corresponding to or used by or mapped by said second bearer is for said first cell group.

[0316] As an embodiment, the phrase said second bearer is associated with a first cell group means that said second bearer is used for transmitting PDCP PDUs between said first node and said first cell group.

[0317] As an embodiment, the phrase said second bearer is associated with a first cell group means that said second bearer is used for transmitting PDCP SDUs between said first node and said first cell group.

[0318] As one embodiment, the phrase "the second bearer is associated with the first cell group" means that the second bearer is used for transmitting RLC PDUs between the first node and the first cell group.

[0319] As one embodiment, the phrase "the second bearer is associated with the first cell group" means that the second bearer is used for transmitting MAC PDUs between the first node and the first cell group.

[0320] As one embodiment, the phrase "the second bearer is associated with the first cell group" means that the second bearer is used for transmitting data between the first node and the first cell group.

[0321] As one embodiment, the phrase "the second bearer is associated with the first cell group" means that at least SRB1 between the first node and the first cell group uses the second bearer.

[0322] As one embodiment, the phrase "the second bearer is associated with the first cell group" means that at least SRB1 between the first node and the first cell group has a mapping relationship with the second bearer.

[0323] As one embodiment, the phrase "the second bearer is associated with the first cell group" means that the second bearer is a bearer between the first node and an L2 U2N relay UE, and the L2 U2N relay UE is a relay between the first node and the first cell group.

[0324] As one embodiment, the phrase "the second bearer is associated with the first cell group" means that the second bearer is a bearer between the first node and an L2 U2N relay UE, and the L2 U2N relay UE forwards data between the first node and the first cell group.

[0325] As one embodiment, the phrase "the second bearer is associated with the first cell group" means that the second bearer is an RLC bearer between the first node and an L2 U2N relay UE, and the L2 U2N relay UE is a relay between the first node and the first cell group.

[0326] As one embodiment, the phrase "the second bearer is associated with the first cell group" means that the second bearer is an RLC bearer between the first node and an L2 U2N relay UE, and the L2 U2N relay UE forwards data between the first node and the first cell group.

[0327] As one embodiment, the phrase the second bearer is associated with a first cell group means that the second bearer is a sidelink radio link between the first node and a L2 U2N relay UE, the L2 U2N relay UE is a relay between the first node and the first cell group.

[0328] As one embodiment, the phrase the second bearer is associated with a first cell group means that the second bearer is a sidelink radio link between the first node and a L2 U2N relay UE, the L2 U2N relay UE forwards data between the first node and the first cell group.

[0329] As one embodiment, the phrase the second bearer is associated with a first cell group means that the second bearer is an RLC bearer between the first node and a L2 U2N relay UE, the second bearer is used to carry at least SRB1, the at least SRB1 is an SRB between the first node and the first cell group.

[0330] As one embodiment, the RLC entity associated with the first type of bearer means that the first type of bearer is an RLC bearer, the RLC entity associated with the first type of bearer is the RLC entity corresponding to the RLC bearer.

[0331] As one embodiment, the RLC entity associated with the first type of bearer means that the first type of bearer is a sidelink RLC bearer, the RLC entity associated with the first type of bearer is the RLC entity of the PC5 interface corresponding to the sidelink RLC bearer.

[0332] As one embodiment, the RLC entity associated with the first type of bearer means that the first type of bearer is a radio bearer, the RLC entity associated with the first type of bearer is the RLC entity corresponding to the RLC bearer used to carry the first type of bearer.

[0333] As one embodiment, the RLC entity associated with the first type of bearer means that the first type of bearer is a radio bearer, the RLC entity associated with the first type of bearer is the RLC entity of the PC5 interface corresponding to the sidelink RLC bearer used to carry the first type of bearer.

[0334] As one embodiment, the RLC entity associated with the first type of bearer means that the first type of bearer is a physical channel, the RLC entity associated with the first type of bearer is the RLC entity generating the RLC PDU carried by the first type of bearer.

[0335] As an embodiment, the RLC entity associated with the first type of bearer refers to: the first type of bearer is a logical channel, and the RLC entity associated with the first type of bearer is an RLC entity corresponding to the first type of bearer.

[0336] As an embodiment, the RLC entity associated with the first type of bearer refers to: the first type of bearer is a logical channel, and the RLC entity associated with the first type of bearer is an RLC entity corresponding to the first type of bearer.

[0337] As an embodiment, the RLC entity associated with the first type of bearer refers to: the first type of bearer is a logical channel, and the RLC entity associated with the first type of bearer is an RLC entity corresponding to the first type of bearer.

[0338] As an embodiment, the RLC entity associated with the first type of bearer refers to: the first type of bearer is a logical channel, and the RLC entity associated with the first type of bearer is an RLC entity corresponding to the first type of bearer.

[0339] As an embodiment, the RLC entity associated with the first type of bearer refers to: the first type of bearer is a logical channel, and the RLC entity associated with the first type of bearer is an RLC entity corresponding to the first type of bearer.

[0340] As an embodiment, the RLC entity associated with the first type of bearer refers to: the first type of bearer is a logical channel, and the RLC entity associated with the first type of bearer is an RLC entity corresponding to the first type of bearer.

[0341] As an embodiment, the RLC entity associated with the first type of bearer refers to: the first type of bearer is a logical channel, and the RLC entity associated with the first type of bearer is an RLC entity corresponding to the first type of bearer.

[0342] As an embodiment, the RLC entity associated with the first type of bearer refers to: the first type of bearer is a logical channel, and the RLC entity associated with the first type of bearer is an RLC entity corresponding to the first type of bearer.

[0343] As an embodiment, the RLC entity associated with the first type of bearer refers to: the first type of bearer is a logical channel, and the RLC entity associated with the first type of bearer is an RLC entity corresponding to the first type of bearer.

[0344] As one embodiment, the RLC entity associated with the first type of bearer refers to that the first type of bearer is a radio bearer, and the RLC entity associated with the first type of bearer is an RLC entity corresponding to the radio bearer.

[0345] As one embodiment, the RLC entity associated with the second type of bearer refers to that the second type of bearer is a radio bearer, and the RLC entity associated with the second type of bearer is an RLC entity corresponding to the radio bearer.

[0346] As one embodiment, the RLC entity associated with the second type of bearer refers to that the second type of bearer is a sidelink radio bearer, and the RLC entity associated with the second type of bearer is an RLC entity corresponding to a PC5 interface of the sidelink radio bearer.

[0347] As one embodiment, the RLC entity associated with the second type of bearer refers to that the second type of bearer is a radio bearer, and the RLC entity associated with the second type of bearer is an RLC entity corresponding to an RLC bearer carrying the second type of bearer.

[0348] As one embodiment, the RLC entity associated with the second type of bearer refers to that the second type of bearer is a sidelink radio bearer, and the RLC entity associated with the second type of bearer is an RLC entity corresponding to a PC5 interface of a sidelink RLC bearer carrying the second type of bearer.

[0349] As one embodiment, the RLC entity associated with the second type of bearer refers to that the second type of bearer is a physical channel, and the RLC entity associated with the second type of bearer is an RLC entity generating an RLC PDU carried by the second type of bearer.

[0350] As one embodiment, the RLC entity associated with the second type of bearer refers to that the second type of bearer is a transport channel, and the RLC entity associated with the second type of bearer is an RLC entity generating an RLC PDU carried by the second type of bearer.

[0351] As one embodiment, the RLC entity associated with the second type of bearer refers to that the second type of bearer is a logical channel, and the RLC entity associated with the second type of bearer is an RLC entity corresponding to the second type of bearer.

[0352] As one embodiment, the RLC entity associated with the second type of bearer refers to that the second type of bearer is a sidelink physical channel, and the RLC entity associated with the second type of bearer is an RLC entity generating an RLC PDU carried by the second type of bearer.

[0353] As an embodiment, the RLC entity associated with the second type of bearer refers to that the second type of bearer is a sidelink transport channel, and the RLC entity associated with the second type of bearer is an RLC entity generating RLC PDUs carried by the second type of bearer.

[0354] As an embodiment, the RLC entity associated with the second type of bearer refers to that the second type of bearer is a sidelink logical channel, and the RLC entity associated with the second type of bearer is an RLC entity corresponding to the second type of bearer.

[0355] As an embodiment, the RLC entity associated with the second type of bearer refers to that the second type of bearer is a radio link for the first cell group, and the RLC entity associated with the second type of bearer is an RLC entity generating RLC PDUs transmitted by the second type of bearer.

[0356] As an embodiment, the RLC entity associated with the second type of bearer refers to that the second type of bearer is a sidelink radio link for an L2 U2N relay UE, the L2 U2N relay UE is an L2 U2N relay UE between the first node and the first cell group, and the RLC entity associated with the second type of bearer is an RLC entity generating RLC PDUs transmitted by the second type of bearer for carrying PDCP PDUs for the first cell group.

[0357] As an embodiment, the RLC entity associated with the second type of bearer is an RLC entity having a mapping relationship with the second type of bearer.

[0358] As an embodiment, the RLC entity associated with the second type of bearer is an RLC entity encapsulating data on the second type of bearer.

[0359] As an embodiment, the RLC entity associated with the second type of bearer is an RLC entity generating data carried by the second type of bearer.

[0360] As an embodiment, the RRC message including the first information is sent using the second bearer.

[0361] As an embodiment, the first bearer is different from the second bearer.

[0362] As an embodiment, the first type of bearer is different from the second type of bearer.

[0363] As an embodiment, a peer RLC entity of the RLC entity of the Uu interface is located at a base station corresponding to the first cell group or the first cell.

[0364] As one embodiment, the peer RLC entity of the RLC entity of the PC5 interface is located in the L2U2N relay UE of the first node.

[0365] As one embodiment, the RLC entity of the PC5 interface is for sidelink communication.

[0366] As one embodiment, the RLC entity of the Uu interface is for non-sidelink communication or for primary link communication.

[0367] As one embodiment, the meaning of the phrase the first type of bearer uses the primary link is that the first type of bearer is a primary link.

[0368] As one embodiment, the meaning of the phrase the first type of bearer uses the primary link is that the first type of bearer is a primary link radio link.

[0369] As one embodiment, the meaning of the phrase the first type of bearer uses the primary link is that the first type of bearer is a direct path.

[0370] As one embodiment, the meaning of the phrase the first type of bearer uses the primary link is that the first type of bearer is a bearer between the first node and the first cell group and does not go through any relay.

[0371] As one embodiment, the meaning of the phrase the first type of bearer uses the primary link is that the first type of bearer corresponds to a Uu interface.

[0372] As one embodiment, the meaning of the phrase the first type of bearer uses the primary link is that the physical channel corresponding to or associated with the first type of bearer is a physical channel of a Uu interface.

[0373] As one embodiment, the meaning of the phrase the first type of bearer uses the primary link is that the physical channel corresponding to or associated with or used by the first type of bearer includes a PUCCH (physical uplink control channel) and a PDCCH (physical downlink control channel).

[0374] As one embodiment, the meaning of the phrase the first type of bearer uses the primary link is that the first type of bearer is an RLC bearer, and the RLC entity corresponding to the RLC bearer is located in the first node and the first cell group.

[0375] As one embodiment, the meaning of the phrase the first type of bearer uses the primary link is that the protocol entity corresponding to the first type of bearer is located in the first node and the first cell group.

[0376] As an embodiment, the phrase "said first type of bearer uses a primary link" means that said first type of bearer is a channel, and said first bearer is a channel between said first node and said first group of cells.

[0377] As an embodiment, the phrase "said first type of bearer uses a primary link" means that said first type of bearer is a channel, and said first bearer is a channel between said first node and said first group of cells.

[0378] As an embodiment, the phrase "said second type of bearer uses a secondary link" means that said second type of bearer is a secondary link.

[0379] As an embodiment, the phrase "said second type of bearer uses a secondary link" means that said second type of bearer is a secondary link radio link.

[0380] As an embodiment, the phrase "said second type of bearer uses a secondary link" means that said second type of bearer is a non-direct path.

[0381] As an embodiment, the phrase "said second type of bearer uses a secondary link" means that said second type of bearer is a bearer between said first node and said first group of cells via a L2 U2N relay UE.

[0382] As an embodiment, the phrase "said second type of bearer uses a secondary link" means that said second type of bearer corresponds to a PC5 interface.

[0383] As an embodiment, the phrase "said second type of bearer uses a secondary link" means that said second type of bearer corresponds or is associated with a physical channel of a PC5 interface.

[0384] As an embodiment, the phrase "said second type of bearer uses a secondary link" means that said second type of bearer corresponds or is associated with or uses a physical channel including a PSSCH (physical sidelink shared channel) and a PSCCH (physical sidelink control channel).

[0385] As an embodiment, the phrase "said second type of bearer uses a secondary link" means that said second type of bearer is a sidelink RLC bearer, and said RLC bearer corresponds to a RLC entity located at said first node and a L2 U2N relay UE.

[0386] As an embodiment, the phrase "said second type of bearer uses a secondary link" means that said second type of bearer corresponds to a protocol entity located at said first node and a L2 U2N relay UE.

[0387] As an embodiment, the meaning of the phrase "the second type of bearer uses sidelink" is that the second type of bearer is a channel, and the first bearer is a channel between the first node and the L2 U2N relay UE.

[0388] As an embodiment, the meaning of the phrase "the second type of bearer uses sidelink" is that the channel corresponding to the second type of bearer is a channel between the first node and the L2 U2N relay UE.

[0389] As an embodiment, the first node is configured with only one cell group.

[0390] As an embodiment, the first node is configured with only a master cell group and not a secondary cell group.

[0391] As an embodiment, the SRB1 of the first node is associated with both the first bearer and the second bearer.

[0392] As an embodiment, the meaning of the phrase "the SRB1 of the first node is associated with both the first bearer and the second bearer" is that the SRB1 of the first node has a mapping relationship with both the first bearer and the second bearer.

[0393] As an embodiment, the meaning of the phrase "the SRB1 of the first node is associated with both the first bearer and the second bearer" is that the data of the SRB1 is sent using either the first bearer or the second bearer.

[0394] As an embodiment, the meaning of the phrase "the SRB1 of the first node is associated with both the first bearer and the second bearer" is that the data of the SRB1 is sent using both the first bearer and the second bearer.

[0395] As an embodiment, the meaning of the phrase "the SRB1 of the first node is associated with both the first bearer and the second bearer" is that the first bearer is an RLC bearer, the second bearer is a sidelink RLC bearer, and the first bearer is used to carry data of the first bearer; the second bearer is also used to carry data of the first bearer.

[0396] As an embodiment, the meaning of the phrase "the SRB1 of the first node is associated with both the first bearer and the second bearer" is that the first bearer is an RLC bearer, the second bearer is a sidelink RLC bearer, and the RB carried by the first bearer includes the SRB1; the RB carried by the second bearer includes the SRB1.

[0397] As an embodiment, the first type of bearer is an RLC bearer, and the second type of bearer is a sidelink RLC bearer.

[0398] As one embodiment, the first set of operations comprises resetting a MAC associated with the first bearer.

[0399] As one embodiment, the MAC associated with the first bearer is a MAC that is mapped to the first bearer.

[0400] As one embodiment, the MAC associated with the first bearer is a MAC that carries data of the first bearer.

[0401] As one embodiment, the MAC associated with the first bearer is a MAC that carries PDU of the first bearer.

[0402] As one embodiment, the MAC associated with the first bearer is a MAC that is the first bearer is a physical channel, and a MAC that generates a MAC PDU that occupies the first bearer is the MAC associated with the first bearer.

[0403] As one embodiment, the MAC associated with the first bearer is a MAC that is a MAC that generates a MAC PDU that occupies the first bearer is the MAC associated with the first bearer.

[0404] As one embodiment, the MAC associated with the first bearer is a MAC of a primary link or a Uu interface.

[0405] As one embodiment, the MAC associated with the second bearer is a MAC of a secondary link or a PC5 interface.

[0406] As one embodiment, the action of resetting the MAC associated with the first bearer is reset the MAC associated with the first bearer.

[0407] As one embodiment, the first bearer is associated with only one MAC.

[0408] As one embodiment, the MAC associated with the first bearer is different from the MAC associated with the second bearer.

[0409] As one embodiment, the MAC associated with the first type of bearer is different from the MAC associated with the second type of bearer.

[0410] As one embodiment, the MAC associated with the first type of bearer is the same as the MAC associated with the second type of bearer.

[0411] As one embodiment, the first bearer is the first type of bearer; the behavior storing, in the first state variable, information for failure of the first bearer comprises storing a cause of the first bearer failure and whether a second type of bearer is used; the cause of the first bearer failure belongs to a first candidate cause set, the first candidate cause set comprising radio link failure, handover failure, and path switch failure.

[0412] As one sub-embodiment of this embodiment, the second type of bearer is a sidelink related bearer.

[0413] As one sub-embodiment of this embodiment, the second type of bearer is a sidelink radio link.

[0414] As one sub-embodiment of this embodiment, at least one of the handover failure and the path switch failure comprised in the first candidate cause set belongs to reconfiguration with sync failure.

[0415] As one sub-embodiment of this embodiment, both of the handover failure and the path switch failure comprised in the first candidate cause set belong to reconfiguration with sync failure.

[0416] As one embodiment, the behavior detecting failure of the first bearer comprises detecting expiration of a T310 timer.

[0417] As one embodiment, the behavior detecting failure of the first bearer comprises detecting expiration of a T310 timer associated with the first bearer.

[0418] As one embodiment, the behavior detecting failure of the first bearer comprises detecting expiration of a T312 timer.

[0419] As one embodiment, the behavior detecting failure of the first bearer comprises detecting expiration of a T312 timer associated with the first bearer.

[0420] As one embodiment, the behavior detecting failure of the first bearer comprises detecting expiration of a T304 timer.

[0421] As one embodiment, the behavior detecting failure of the first bearer comprises detecting expiration of a T304 timer associated with the first bearer.

[0422] As one embodiment, the behavior detecting failure of the first bearer comprises detecting expiration of a first timer for path switch.

[0423] As one sub-example of this embodiment, the first timer is started as a response to receiving Reconfiguration with SYNC for path switch.

[0424] As one embodiment, the behavior detecting the first bearer failure comprises detecting expiry of a first timer associated with the first bearer, the first timer being for path switch.

[0425] As one sub-example of this embodiment, the first timer is started as a response to receiving Reconfiguration with SYNC for path switch.

[0426] As one embodiment, the behavior detecting the first bearer failure comprises detecting radio link failure, the first bearer being the first type of bearer.

[0427] As one embodiment, the behavior detecting the first bearer failure comprises detecting sidelink radio link failure, the first bearer being the second type of bearer.

[0428] As one embodiment, the behavior detecting the first bearer failure comprises detecting sidelink RRC configuration incompatibility, the first bearer being the second type of bearer.

[0429] As one embodiment, the behavior detecting the first bearer failure comprises detecting expiry of T400 timer, the first bearer being the second type of bearer.

[0430] As one embodiment, the behavior detecting the first bearer failure comprises receiving from MAC an indication that a maximum number of HARQ (Hybrid Automatic Repeat Request) DTX (discontinuous transmission) is reached, the first bearer being the second type of bearer.

[0431] As one embodiment, the behavior detecting the first bearer failure comprises detecting an indication from a higher layer that the first bearer is released or unavailable or failed.

[0432] As one embodiment, the behavior detecting the first bearer failure comprises detecting failure in security aspect.

[0433] As one embodiment, the behavior detecting the first bearer failure comprises receiving a first notification, the first notification being used to determine the first bearer failure, the first bearer being the second type of bearer.

[0434] As a sub-embodyment of this embodiment, the sender of the first notification is an L2 U2N relay UE of the first node.

[0435] As a sub-embodyment of this embodiment, the first notification is transmitted on a sidelink.

[0436] As a sub-embodyment of this embodiment, the first notification is a NotificationMessageSidelink.

[0437] As a sub-embodyment of this embodiment, the first notification indicates that an L2 U2N relay UE of the first node experiences radio link failure.

[0438] As a sub-embodyment of this embodiment, the first notification indicates that an L2 U2N relay UE of the first node receives an RRCreconfiguration message including ReconfigurationWithSync.

[0439] As a sub-embodyment of this embodiment, the first notification indicates that an L2 U2N relay UE of the first node receives an RRCreconfiguration message including ReconfigurationWithSync related to MCG.

[0440] As a sub-embodyment of this embodiment, the first notification indicates that an L2 U2N relay UE of the first node experiences cell reselection.

[0441] As an embodiment, the behavior detecting the failure of the first bearer comprises receiving an indication from a MAC that there is a problem with random access, the first bearer being the first type of bearer.

[0442] As an embodiment, the behavior detecting the failure of the first bearer comprises receiving an indication from an RLC entity that a maximum number of retransmissions is reached, the first bearer being the first type of bearer.

[0443] As a sub-embodyment of this embodiment, the RLC entity indicating that a maximum number of retransmissions is reached is associated with the first bearer or is the RLC entity corresponding to the first bearer.

[0444] As an embodiment, the behavior detecting the failure of the first bearer comprises receiving an indication from a MAC that there is a problem of persistent LBT (listen before talk) failure, the first bearer being the first type of bearer.

[0445] As an embodiment, the first node is not configured with SRB3.

[0446] As one embodiment, the SRB1 of the first node is an SRB between the first node and the first cell group.

[0447] As one embodiment, when the first bearer is a second type of bearer, the first set of operations does not include reestablishing an RLC entity associated with the first bearer.

[0448] As one embodiment, when the first bearer is a second type of bearer, the first set of operations does not include storing information for the first bearer failure in the first state variable.

[0449] As one embodiment, the meaning of the sentence "the first set of operations does not include storing information for the first bearer failure in the first state variable" is that information for the first bearer failure is not stored.

[0450] As one embodiment, the meaning of the sentence "the first set of operations does not include storing information for the first bearer failure in the first state variable" is that information for the first bearer failure is stored in a variable other than the first state variable.

[0451] As one embodiment, the first set of conditions includes the first bearer being failed.

[0452] As one embodiment, the first set of conditions includes the second bearer being failed.

[0453] As one embodiment, the first set of conditions includes both the first bearer and the second bearer being failed.

[0454] As one embodiment, the first set of conditions includes the first bearer being successful and the second bearer being detected as failed before being resumed.

[0455] As one embodiment, the first set of conditions includes the second bearer being detected as failed and there being no failed bearers or radio links for the first cell group when the second bearer is detected as failed.

[0456] As one embodiment, the second bearer is not detected as failed before the first bearer is detected as failed.

[0457] As one embodiment, the first set of operations does not include initiating RRC reestablishment.

[0458] As one embodiment, the first set of operations does not include discarding stored RRC message segments.

[0459] As one embodiment, the behavior detects the first bearer failure without triggering performance of RRC reestablishment.

[0460] As one subembodiment of this embodiment, the first bearer is the first type of bearer.

[0461] As one subembodiment of this embodiment, the first node is configured with both the first type of bearer and the second type of bearer and no failure is detected for bearers other than the first bearer among the configured first type of bearer and the second type of bearer.

[0462] As one embodiment, the behavior of reestablishing the RLC entity associated with the first bearer includes discarding all RLC SDUs, RLC SDU segments, and RLC PDUs.

[0463] As one embodiment, the behavior of reestablishing the RLC entity associated with the first bearer includes stopping and resetting all timers of the RLC entity associated with the first bearer.

[0464] As one embodiment, the behavior of reestablishing the RLC entity associated with the first bearer includes resetting all state variables of the RLC entity associated with the first bearer to initial values.

[0465] Embodiment 2

[0466] Embodiment 2 illustrates a diagram of a network architecture according to the present application, as shown in FIG. 2. Figure 2 As shown in FIG. 2, the network architecture includes a first node 200, a second node 202, and a third node 204. The first node 200 is configured with a first type of bearer and a second type of bearer. The first node 200 is configured to detect a failure of the first bearer among the configured first type of bearer and the second type of bearer. As shown in FIG. 2, the network architecture includes a first node 200, a second node 202, and a third node 204. The first node 200 is configured with a first type of bearer and a second type of bearer. The first node 200 is configured to detect a failure of the first bearer among the configured first type of bearer and the second type of bearer.

[0467] As shown in FIG. 2, the network architecture includes a first node 200, a second node 202, and a third node 204. The first node 200 is configured with a first type of bearer and a second type of bearer. The first node 200 is configured to detect a failure of the first bearer among the configured first type of bearer and the second type of bearer. Figure 2A diagram illustrating a network architecture 200 of a 5G NR, LTE (Long-Term Evolution), and LTE-A (Long-Term Evolution Advanced) system is shown. The 5G NR or LTE network architecture 200 can be referred to as a 5GS (5G System) / EPS (Evolved Packet System) 200 or some other suitable terminology. The 5GS / EPS 200 can include one or more UEs (User Equipment) 201, NG-RAN (Next Generation Radio Access Network) 202, 5GC (5G Core Network) / EPC (Evolved Packet Core) 210, HSS (Home Subscriber Server) / UDM (Unified Data Management) 220, and Internet services 230. The 5GS / EPS can 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 can be extended to networks providing circuit- switched services or other cellular networks. The NG-RAN includes an NR Node-B (gNB) 203 and other gNBs 204. The gNB 203 provides user and control plane protocol terminations toward the UE 201. The gNB 203 can be connected to the other gNBs 204 via an Xn interface (e.g., backhaul). The gNB 203 can 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 (Transmission Reception Point), or some other suitable terminology. The gNB 203 provides access to the 5GC / EPC 210 for the UE 201. Examples of UEs 201 include a cellular phone, a smart phone, a session initiation protocol (SIP) phone, a laptop, a personal digital assistant (PDA), a satellite radio, a non-tethered personal branch station, a satellite mobile communication, 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, a flying vehicle, a narrow-band internet of things device, a machine type communication device, a land vehicle, a car, a wearable device, or any other similar functional device. Those skilled in the art will also readily appreciate that the UE 201 can be referred to as a mobile station, a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wirelessThe gNB 203 is connected to the 5GC / EPC 210 over the S1 / NG interface. The 5GC / EPC 210 includes MME (Mobility Management Entity) / AMF (Authentication Management Field) / SMF (Session Management Function) 211, other MME / AMF / SMF 214, S-GW (Service Gateway) / UPF (User Plane Function) 212, and P-GW (Packet Data Network Gateway) / UPF 213. The MME / AMF / SMF 211 is the control node that handles signaling between the UE 201 and the 5GC / EPC 210. Generally, the MME / AMF / SMF 211 provides bearer and connection management. All user IP (Internet Protocal) packets are transferred through the S-GW / UPF 212, which 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 / UPF 213 is connected to the Internet services 230. The Internet services 230 include operator corresponding Internet protocol services, which can specifically include the Internet, intranet, IMS (IP Multimedia Subsystem), and packet exchange streaming services.

[0468] As one embodiment, the first node in the present application is the UE 201.

[0469] As one embodiment, the base station of the first node in the present application is the gNB 203.

[0470] As one embodiment, the wireless link from the UE 201 to the NR Node B is uplink.

[0471] As one embodiment, the wireless link from the NR Node B to the UE 201 is downlink.

[0472] As one embodiment, the UE 201 supports relay transmission.

[0473] As one embodiment, the UE 201 is a mobile phone.

[0474] As one embodiment, the UE 201 is a vehicle including a car.

[0475] As one embodiment, the UE 201 supports multiple SIM cards.

[0476] As an example, the UE201 supports secondary link transmission.

[0477] As an example, the UE201 supports MBS transmission.

[0478] As an example, the UE201 supports MBMS transmission.

[0479] As an example, the gNB203 is a macrocell base station.

[0480] As an example, the gNB203 is a microcell base station.

[0481] As an example, the gNB203 is a PicoCell base station.

[0482] As one example, the gNB203 is a flight platform device.

[0483] As an example, the gNB203 is a satellite device.

[0484] Embodiment 3

[0485] Example 3 illustrates a schematic diagram of an embodiment of a wireless protocol architecture for a user plane and a control plane according to this application, as shown in the attached diagram. Figure 3 As shown. Figure 3 This is a schematic diagram illustrating an embodiment of a radio protocol architecture for the user plane 350 and the control plane 300. Figure 3The radio protocol architecture for the control plane 300 between a first node (UE, gNB, or satellite or aircraft in NTN) and a second node (gNB, UE, or satellite or aircraft in NTN), or between two UEs, is shown using 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 as the PHY 301 in this document. Layer 2 (L2 layer) 305 is above the PHY 301 and is responsible for the link between the first node and the second node, as well as between two UEs, over the PHY 301. The L2 layer 305 includes a MAC (Medium Access Control) sublayer 302, a RLC (Radio Link Control) sublayer 303, and a PDCP (Packet Data Convergence Protocol) sublayer 304, which are terminated at the second node. The PDCP sublayer 304 provides multiplexing between different radio bearers and logical channels. The PDCP sublayer 304 also provides security functions, through encryption of data packets, and handover between the first node and the second node. The RLC sublayer 303 provides segmentation and reassembly of upper layer data packets, retransmission of lost data packets, and reordering of data 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 the various radio resources (e.g., resource blocks) in one cell among the UEs. The MAC sublayer 302 is also responsible for HARQ operations. The RRC (Radio Resource Control) sublayer 306 in Layer 3 (L3 layer) in the control plane 300 is responsible for obtaining radio resources (i.e., radio bearers) and configuring the lower layers using RRC signaling between the second node and the first node. The PC5-S (PC5 Signaling Protocol) sublayer 307 is responsible for handling of the signaling protocol for the PC5 interface. The radio protocol architecture for the user plane 350 includes Layer 1 (L1 layer) and Layer 2 (L2 layer), which are generally the same 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 for the first node and the second node, but the PDCP sublayer 354 also provides header compression for upper layer data packets to reduce radio transmission overhead.The L2 layer 355 in the user plane 350 also includes a SDAP (Service Data Adaptation Protocol) sublayer 356, which is responsible for mapping between a QoS flow and a data radio bearer (DRB) to support the diversity of services. Although not illustrated, the first node can have several upper layers above the L2 layer 355. Further included are network layers (e.g., IP layer) that are terminated at the P-GW on the network side and application layers that are terminated at the other end of the connection (e.g., a remote UE, a server, etc.). For UEs involving relay services, the control plane of the UE can also include an adaptation sublayer SRAP (Sidelink Relay Adaptation Protocol) 308, and the user plane of the UE can also include an adaptation sublayer SRAP 358, the introduction of the adaptation layer helps the lower layers, e.g., the MAC layer, e.g., the RLC layer, to multiplex and / or differentiate data from multiple source UEs.

[0486] As one embodiment, the wireless protocol architecture in Figure 3 is applicable to the first node in the present application.

[0487] As one embodiment, the wireless protocol architecture in Figure 3 is applicable to the second node in the present application.

[0488] As one embodiment, the first information in the present application is generated at the RRC 306 or the MAC 302.

[0489] As one embodiment, the first signaling in the present application is generated at the RRC 306.

[0490] As one embodiment, the second message in the present application is generated at the RRC 306.

[0491] As one embodiment, the third message in the present application is generated at the RRC 306.

[0492] Embodiment 4

[0493] Embodiment 4 shows a schematic diagram of a first communication device and a second communication device according to one embodiment of the present application, as shown in Figure 4 . Figure 4 is a block diagram of a first communication device 450 and a second communication device 410 that communicate with each other in an access network.

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

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

[0496] In the transmission from the second communication device 410 to the first communication device 450, upper layer packets from a core network are provided to the controller / processor 475 at the second communication device 410. The controller / processor 475 implements functionality of the L2 layer. In the transmission from the second communication device 410 to the first communication device 450, the controller / processor 475 provides header compression, ciphering, packet segmentation and reordering, multiplexing between logical and transport channels, and radio resource allocation for the first communication 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 LI layer (i.e., physical layer). The transmit processor 416 implements coding and interleaving to facilitate forward error correction (FEC) at the second communication device 410, and mapping of coded and interleaved data onto signal constellations 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 of the coded and modulated symbols, including codebook-based precoding and non-codebook-based precoding, and beamforming processing, generating one or more spatial streams. The transmit processor 416 then maps to each spatial stream to a subcarrier, multiplexes the stream with reference signals (e.g., pilot) in the time and / or frequency domain, and then performs an inverse fast Fourier transform (IFFT) to generate a time-domain multicarrier symbol stream for the physical channel. The multi-antenna transmit processor 471 then performs transmit analog precoding / beamforming operations on the time-domain multicarrier symbol streams. Each transmitter 418 converts the baseband multicarrier symbol streams provided by the multi-antenna transmit processor 471 into radio frequency streams, and then provides the radio frequency streams to the different antennas 420.

[0497] In transmissions from the second communication device 410 to the first communication device 450, at the first communication device 450, each receiver 454 receives a signal through its respective antenna 452. Each receiver 454 recovers information modulated onto an RF carrier and provides the recovered information at baseband as a stream of symbols to a receive processor 456. The receive processor 456 and a multiple access receiver processor 458 implement various signal processing functions of the Ll layer. The multiple access receiver processor 458 performs receive analog precoding / beamforming operations on the baseband multiple access symbol streams from the receivers 454. The receive processor 456 converts the baseband multiple access symbol streams 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 are demultiplexed from the received symbol streams by the receive processor 456, with the reference signals to be used for channel estimation and the data signals to be recovered after multiple access detection in the multiple access receiver processor 458 for any spatial streams destined for the first communication device 450. The symbols on each spatial stream are demodulated and recovered by the receive processor 456 and used to generate soft decisions. The receive processor 456 then decodes and de-interleaves the soft decisions to recover the upper layer data and control signals transmitted by the second communication 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 functions of the L2 layer. The controller / processor 459 can be associated with a memory 460 that stores program codes and data. The memory 460 can be referred to as a computer-readable medium. In transmissions from the second communication device 410 to the second communication 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 data packets from the core network. The upper layer data packets are then provided to all protocol layers above the L2 layer. Various control signals can also be provided to the L3 for L3 processing.

[0498] In the transmission from the first communication device 450 to the second communication device 410, at the first communication device 450, a data source 467 is used to provide upper layer data packets to a controller / processor 459. The data source 467 represents all protocol layers above the L2 layer. Similar to the transmit function at the second communication device 410 described in the transmission from the second communication device 410 to the first communication device 450, the controller / processor 459 implements header compression, ciphering, packet segmentation and reordering, and multiplexing between logical and transport channels based on radio resource allocations, implements L2 layer functionality for the user plane and control plane. The controller / processor 459 is also responsible for error detection, retransmission of lost packets, and signaling to the second communication device 410. A transmit processor 468 performs modulation mapping, channel coding processing, and a multi-antenna transmit processor 457 performs digital multi-antenna spatial precoding, including codebook-based precoding and non-codebook-based precoding, and beamforming processing, and then the transmit processor 468 modulates the resulting spatial streams into multi-carrier / single-carrier symbol streams, which are then provided to different antennas 452 via transmitters 454 after analog precoding / beamforming operations 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 signal, and then provides the radio frequency signal to the antenna 452.

[0499] In the transmission from the first communication device 450 to the second communication device 410, the functions at the second communication device 410 are similar to the receive functions 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 a radio frequency signal through its respective antenna 420, converts the received radio frequency signal into 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 multi-antenna receive processor 472 collectively implement the functionality of the L1 layer. A controller / processor 475 implements the functionality of the L2 layer. The controller / processor 475 can be associated with a memory 476 that stores program codes and data. The memory 476 can be referred to as a computer readable medium. In the transmission from the first communication device 450 to the second communication 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 data packets from the UE 450. Upper layer data packets from the controller / processor 475 can be provided to a core network.

[0500] As one embodiment, the first communication device 450 comprises: at least one processor and at least one memory including a computer program code; the at least one memory and the computer program code are configured to, with the at least one processor, cause the first communication device 450 to perform at least the following: detect a first bearer failure; the first bearer is associated with a first cell group; in response to the act of detecting the first bearer failure, perform a first set of operations; the first set of operations is related to a type of the first bearer; in response to the act of detecting the first bearer failure, send a first information; the first information is used to indicate the first bearer failure; in response to all conditions in a first set of conditions being met, send a second message; the second message indicates that there is available information; wherein the first cell group is a master cell group; the first set of conditions comprises that a first status variable stores the available information; the meaning of the sentence that the first set of operations is related to the type of the first bearer is that: when the first bearer is a first type of bearer, the first set of operations comprises at least one of re-establishing an RLC entity associated with the first bearer and storing information for the first bearer failure in the first status variable; when the first bearer is a second type of bearer, the first set of operations comprises at least releasing an RLC entity associated with the first bearer.

[0501] As one embodiment, the first communication device 450 comprises: a memory storing a computer readable program of instructions which, when executed by at least one processor, causes actions comprising: detecting a first bearer failure; the first bearer is associated with a first cell group; in response to the act of detecting the first bearer failure, performing a first set of operations; the first set of operations is related to a type of the first bearer; in response to the act of detecting the first bearer failure, sending a first information; the first information is used to indicate the first bearer failure; in response to all conditions in a first set of conditions being met, sending a second message; the second message indicates that there is available information; wherein the first cell group is a master cell group; the first set of conditions comprises that a first status variable stores the available information; the meaning of the sentence that the first set of operations is related to the type of the first bearer is that: when the first bearer is a first type of bearer, the first set of operations comprises at least one of re-establishing an RLC entity associated with the first bearer and storing information for the first bearer failure in the first status variable; when the first bearer is a second type of bearer, the first set of operations comprises at least releasing an RLC entity associated with the first bearer.

[0502] As one embodiment, the first communication device 450 corresponds to the first node in the present application.

[0503] As an example, the second communication device 410 corresponds to the second node in this application.

[0504] As an example, the first communication device 450 is a UE.

[0505] As an example, the first communication device 450 is a vehicle-mounted terminal.

[0506] As one embodiment, the second communication device 450 is a relay.

[0507] As one example, the second communication device 450 is a satellite.

[0508] As one example, the second communication device 450 is an aircraft.

[0509] As one embodiment, receiver 454 (including antenna 452), receiver processor 456 and controller / processor 459 are used in this application to receive the first signaling.

[0510] As one embodiment, a transmitter 454 (including an antenna 452), a transmitter processor 468, and a controller / processor 459 are used in this application to transmit the first information.

[0511] As one embodiment, a transmitter 454 (including an antenna 452), a transmitter processor 468, and a controller / processor 459 are used in this application to transmit the second message.

[0512] As one embodiment, a transmitter 454 (including an antenna 452), a transmitter processor 468, and a controller / processor 459 are used to transmit the third message in this application.

[0513] Embodiment 5

[0514] Example 5 illustrates a wireless signal transmission flowchart according to an embodiment of this application, as shown in the attached diagram. Figure 5 As shown. (Attached) Figure 5 In this example, U01 corresponds to the first node of this application. It should be noted that the order in this example does not limit the signal transmission order and the implementation order in this application. The steps in F51 and F52 are optional.

[0515] for First node U01 In step S5101, a first signaling is received; in step S5102, a first bearer failure is detected; in step S5103, a first message is sent; in step S5104, a second bearer failure is detected; in step S5105, a second message is sent; and in step S5106, a third message is sent.

[0516] forSecond node U02 The first signaling is sent in step S5201; the first information is received in step S5202; the second message is received in step S5203; and the third message is received in step S5204.

[0517] For the first node U01, the first information is forwarded in step S5301. Third node U03

[0518] In embodiment 5, the first bearer is associated with a first cell group; the first node U01, in response to the behavior detecting the failure of the first bearer, performs a first set of operations, the first set of operations being related to a type of the first bearer;

[0519] The first node U01, in response to the behavior detecting the failure of the first bearer, sends first information, the first information being used to indicate the failure of the first bearer, and in response to all conditions in a first set of conditions being met, sends a second message; the second message indicates that there is available information;

[0520] In one embodiment, the first cell group is a master cell group; the first set of conditions includes a first status variable storing the available information; and the first set of operations being related to the type of the first bearer means that when the first bearer is a first type of bearer, the first set of operations includes at least one of reestablishing an RLC entity associated with the first bearer and storing information about the failure of the first bearer in the first status variable; and when the first bearer is a second type of bearer, the first set of operations includes releasing at least an RLC entity associated with the first bearer.

[0521] In one embodiment, the first node U01 is a U2N relay UE.

[0522] In one embodiment, the first node U01 is a U2N remote UE.

[0523] In one embodiment, the first node U01 is a NR ProSe U2N remote UE.

[0524] In one embodiment, the third node U03 is a L2 U2N relay UE.

[0525] In one embodiment, the third node U03 is a neighbor cell of the first node U01.

[0526] In one embodiment, the third node U03 belongs to a same CU as the second node U02.

[0527] In one embodiment, the third node U03 belongs to a same DU as the second node U02. ​

[0528] As an embodiment, the third node U03 and the second node U02 belong to one gNB.

[0529] As an embodiment, the third node U03 and the second node U02 are cells with different PCI (physical cell identity) respectively.

[0530] As an embodiment, the third node U03 and the second node U02 are cells within the first cell group respectively.

[0531] As an embodiment, the third node U03 and the second node U02 are another TRP.

[0532] As an embodiment, the third node U03 and the second node U02 are another beam, corresponding to another group of CSI-RS reference signals.

[0533] As an embodiment, the second node U02 is a base station.

[0534] As an embodiment, the second node U02 is a primary cell of the first node U01.

[0535] As an embodiment, the second node U02 is a primary cell group of the first node U01.

[0536] As an embodiment, the second node U02 corresponds to the first cell group or the base station corresponding to the first cell group.

[0537] As an embodiment, the first signaling is sent directly by the second node U02 to the first node U01 without relay.

[0538] As an embodiment, the first signaling is sent by the second node U02 to the first node U01 through the forwarding of the third node U03.

[0539] As an embodiment, the first signaling is sent by the second node U02 to the first node U01 through both relay forwarding and direct sending.

[0540] As an embodiment, the first signaling is RRC signaling.

[0541] As an embodiment, the first signaling includes SIB12.

[0542] As an embodiment, the first signaling includes RRCReconfiguration.

[0543] As one embodiment, the first signaling comprises ReconfigurationWithSync.

[0544] As one embodiment, the first signaling comprises cellgroupconfig.

[0545] As one embodiment, the first signaling comprises masterCellGroup.

[0546] As one embodiment, the first signaling does not comprise secondaryCellGroup.

[0547] As one embodiment, the first type of bearer is configured by radioBearerConfig comprised in the first signaling.

[0548] As one embodiment, the first type of bearer is configured by masterCellGroup comprised in the first signaling.

[0549] As one embodiment, the first type of bearer is configured by spCellGroup comprised in the first signaling.

[0550] As one embodiment, the second type of bearer is configured by SL-ConfigDedicatedNR comprised in the first signaling.

[0551] As one embodiment, the second type of bearer is configured by sl-L2RemoteConfig comprised in the first signaling.

[0552] As one embodiment, the first type of bearer is a bearer between the first node U01 and the second node U02 without relay.

[0553] As one embodiment, the second type of bearer is a bearer between the first node U01 and the second node U02 with relay by the third node U03.

[0554] As one embodiment, the first type of bearer is an RLC bearer between the first node U01 and the second node U02.

[0555] As one embodiment, the first type of bearer is a wireless link between the first node U01 and the second node U02.

[0556] As one embodiment, a protocol entity corresponding to the first type of bearer is located at the first node U01 and the second node U02.

[0557] As an embodiment, the second type of bearer is a sidelink RLC bearer between the first node U01 and the third node U03 for transmitting data between the first node U01 and the second node U02.

[0558] As an embodiment, the second type of bearer is a sidelink radio link between the first node U01 and the third node U03.

[0559] As an embodiment, the protocol entity corresponding to the second type of bearer is located at the first node U01 and the third node U03.

[0560] As an embodiment, both the first type of bearer and the second type of bearer are used for processing data between the first node U01 and the second node U02.

[0561] As an embodiment, the first signaling is used for configuring the first bearer.

[0562] As an embodiment, the first signaling is used for configuring the second bearer, and the second signaling is associated with the first cell group.

[0563] As a sub-embodiment of this embodiment, the first bearer is the first type of bearer, and the second bearer is the second type of bearer.

[0564] As a sub-embodiment of this embodiment, the first bearer is the second type of bearer, and the second bearer is the first type of bearer.

[0565] As an embodiment, after the first node U01 detects the failure of the first bearer at step S5102, and before the first node U01 transmits the first information at step S5103, the primary path of the PDCP entity of SRB1 is set to be for the second bearer;

[0566] wherein the first signaling indicates that SRB1 is associated with both the first bearer and the second bearer and the primary path of the PDCP entity of SRB1 is for the first bearer; SRB1 is not configured with PDCP duplication; the first information includes a first measurement result; and the first information is used to indicate whether the first bearer is the second type of bearer.

[0567] As a sub-embodiment of this embodiment, the SRB1 of the first node U01 is an SRB between the first node U01 and the second node U02.

[0568] As a sub-embodiment of this embodiment, the meaning of the first signaling indicating that SRB1 is associated with both the first bearer and the second bearer is that both the first bearer and the second bearer are associated with the SRB1.

[0569] As one sub-embodying of the embodiment, the meaning of the sentence that the first signaling indicates that the SRB1 is associated with the first bearer and the second bearer simultaneously is that both the first bearer and the second bearer have mapping relationship with the SRB1.

[0570] As one sub-embodying of the embodiment, the meaning of the sentence that the first signaling indicates that the SRB1 is associated with the first bearer and the second bearer simultaneously is that both the first bearer and the second bearer are used to transmit data of the SRB1.

[0571] As one sub-embodying of the embodiment, the meaning of the sentence that the first signaling indicates that the SRB1 is associated with the first bearer and the second bearer simultaneously is that data of the SRB1 of the first node U01 can be transmitted in any of the first bearer and the second bearer.

[0572] As one sub-embodying of the embodiment, the meaning of the sentence that the first signaling indicates that the SRB1 is associated with the first bearer and the second bearer simultaneously is that data of the SRB1 of the first node U01 is repeatedly transmitted on the first bearer and the second bearer.

[0573] As one sub-embodying of the embodiment, the SRB1 corresponds to and only corresponds to one PDCP entity, that is, the PDCP entity of the SRB1.

[0574] As one sub-embodying of the embodiment, the meaning of the sentence that the SRB1 is not configured PDCP duplication is that the SRB1 of the first node U01 is not configured PDCP duplication (pdcp-Duplication).

[0575] As one sub-embodying of the embodiment, the meaning of the sentence that the SRB1 is not configured PDCP duplication is that the SRB1 of the first node U01 is configured with the value false of the PDCP duplication (pdcp-Duplication) field.

[0576] As one sub-embodying of the embodiment, the first measurement result included in the first information includes a measurement result on a primary link.

[0577] As one sub-embodying of the embodiment, the first measurement result included in the first information includes a measurement result on a secondary link wireless link.

[0578] As one sub-embodying of the embodiment, the first measurement result included in the first information includes a measurement result for a measurement object configured for the first node U01.

[0579] As one sub-embodying of the embodiment, the first measurement result comprised in the first information comprises RSRP and / or RSRQ for the second node U02.

[0580] As one sub-embodying of the embodiment, the first measurement result comprised in the first information comprises RSRP for the third node U03.

[0581] As one sub-embodying of the embodiment, the first measurement result comprised in the first information comprises measurement result for a neighbor cell.

[0582] As one sub-embodying of the embodiment, the first measurement result comprised in the first information comprises measurement result for a beam of the second node U02.

[0583] As one sub-embodying of the embodiment, the first measurement result comprised in the first information comprises measurement result for a candidate relay.

[0584] As one sub-embodying of the embodiment, the first information explicitly indicates whether the first bearer is the second type of bearer.

[0585] As one sub-embodying of the embodiment, the first information implicitly indicates whether the first bearer is the second type of bearer.

[0586] As one sub-embodying of the embodiment, the PDCP entity of SRB1 of the first node U01 has at most one primary path.

[0587] As one sub-embodying of the embodiment, the sentence "the first signaling indicates that SRB1 is associated with both the first bearer and the second bearer and the primary path of the PDCP entity of SRB1 is for the first bearer" means that the identity of the cell group of the primary path of the PDCP entity of SRB1 of the first node U01 is the identity of the first cell for which the first bearer is.

[0588] As one sub-embodying of the embodiment, the sentence "the first signaling indicates that SRB1 is associated with both the first bearer and the second bearer and the primary path of the PDCP entity of SRB1 is for the first bearer" means that the identity of the logical channel of the primary path of the PDCP entity of SRB1 of the first node U01 is the identity of the first bearer.

[0589] As a sub-embodiment of this embodiment, the first signaling of the sentence indicating that SRB1 is simultaneously associated with the first bearer and the second bearer and the meaning of the primary path of the PDCP entity of SRB1 being for the first bearer is that the identity of the logical channel of the primary path of the PDCP entity of SRB1 of the first node U01 is the identity of the logical channel associated or used by the first bearer.

[0590] As a sub-embodiment of this embodiment, the behavior of setting the primary path of the PDCP entity of SRB1 to be for the second bearer means that the identity of the cell group of the primary path of the PDCP entity of SRB1 of the first node U01 is set to the identity of the first cell group associated by the second bearer.

[0591] As a sub-embodiment of this embodiment, the behavior of setting the primary path of the PDCP entity of SRB1 to be for the second bearer means that the identity of the logical channel of the primary path of the PDCP entity of SRB1 of the first node U01 is set to the identity of the second bearer.

[0592] As a sub-embodiment of this embodiment, the behavior of setting the primary path of the PDCP entity of SRB1 to be for the second bearer means that the identity of the logical channel of the primary path of the PDCP entity of SRB1 of the first node U01 is set to the identity of the sidelink logical channel associated by the second bearer.

[0593] As a sub-embodiment of this embodiment, the behavior of setting the primary path of the PDCP entity of SRB1 to be for the second bearer means that the identity of the logical channel of the primary path of the PDCP entity of SRB1 of the first node U01 is set to the identity of the sidelink logical channel occupied by the second bearer.

[0594] As a sub-embodiment of this embodiment, the behavior of setting the primary path of the PDCP entity of SRB1 to be for the second bearer means that the identity of the node of the primary path of the PDCP entity of SRB1 of the first node U01 is set to the identity of the relay associated by the second bearer.

[0595] As a sub-embodiment of this embodiment, the behavior of setting the primary path of the PDCP entity of SRB1 to be for the second bearer means that the identity of the node of the primary path of the PDCP entity of SRB1 of the first node U01 is set to the identity of the third node U03.

[0596] As an embodiment, the first information is forwarded through the third U03.

[0597] As one embodiment, the first information is sent using the second bearer.

[0598] As one sub-embodiment of this embodiment, the second bearer is the second type of bearer.

[0599] As one sub-embodiment of this embodiment, the first information is at least part of fields in an RRC message for the second node U02.

[0600] As one embodiment, step S5102 detecting the first bearer failure comprises detecting that the first bearer experiences radio link failure.

[0601] As one embodiment, step S5102 detecting the first bearer failure comprises detecting that the radio link between the first node U01 and the second node U02 experiences radio link failure.

[0602] As one embodiment, step S5102 detecting the first bearer failure comprises detecting that a timer T310 expires.

[0603] As one embodiment, step S5102 detecting the first bearer failure comprises detecting that a timer T312 expires.

[0604] As one embodiment, step S5102 detecting the first bearer failure comprises detecting that a timer T304 expires.

[0605] As one embodiment, step S5102 detecting the first bearer failure comprises detecting that a random access procedure for the second node U02 experiences problem.

[0606] As one embodiment, step S5102 detecting the first bearer failure comprises detecting that the first bearer reaches RLC maximum retransmission number.

[0607] As one embodiment, step S5102 detecting the first bearer failure comprises detecting that persistent LBT failure occurs.

[0608] As one embodiment, in response to step S5102 detecting the first bearer failure, the first node U01 performs the first set of operations, the first bearer being the first type of bearer.

[0609] As one sub-embodiment of this embodiment, the first operation comprises re-establishing RLC entity associated with the first bearer, and not storing information for the first bearer failure in the first status variable.

[0610] As a sub-embodiment of this embodiment, the first operation comprises storing in the first state variable information for the first bearer failure, without reestablishing an RLC entity associated with the first bearer.

[0611] As a sub-embodiment of this embodiment, the first operation comprises storing in the first state variable information for the first bearer failure, including reestablishing an RLC entity associated with the first bearer.

[0612] As one embodiment, step S5104 occurs after step S5102.

[0613] As one embodiment, in step S5104, the behavior detecting the second bearer failure comprises: a radio link failure occurs for the second bearer.

[0614] As one embodiment, in step S5104, the behavior detecting the second bearer failure comprises: a sidelink radio link failure occurs between the first node U01 and the third node U03.

[0615] As one embodiment, in step S5104, the behavior detecting the second bearer failure comprises: an RRC message compatibility failure occurs for the second bearer.

[0616] As one embodiment, in step S5104, the behavior detecting the second bearer failure comprises: a compatibility failure of an RRC message of a PC5 interface occurs between the first node U01 and the third node U03.

[0617] As one embodiment, in step S5104, the behavior detecting the second bearer failure comprises: the second bearer is released.

[0618] As one embodiment, in step S5104, the behavior detecting the second bearer failure comprises: a higher layer of the first node U01 indicates the second bearer failure.

[0619] As one embodiment, in step S5104, the behavior detecting the second bearer failure comprises: detecting that a timer for the second bearer expires.

[0620] As one embodiment, in step S5104, the behavior detecting the second bearer failure comprises: detecting that a T400 timer for the second bearer expires.

[0621] As one embodiment, in step S5104, the behavior detecting the second bearer failure comprises: detecting that a T404 timer for the second bearer expires.

[0622] As one embodiment, in step S5104, said behavior detecting the failure of the second bearer comprises detecting that a timer related to a path switch for said second bearer expires.

[0623] As one embodiment, in step S5104, said behavior detecting the failure of the second bearer comprises detecting that a path switch for said second bearer fails.

[0624] As one embodiment, in step S5104, said first bearer has not been restored when said behavior detects the failure of the second bearer.

[0625] As one embodiment, in step S5104, when said behavior detects the failure of the second bearer, there is no bearer between said first node U01 and said second node U02 belonging to said first type of bearer and to said second type of bearer other than said first bearer and said second bearer.

[0626] As one embodiment, the meaning of the sentence "said behavior suspending SRB1, performing any of cell selection and relay selection, is accompanied by said RRC reestablishment procedure" is that said behavior suspending SRB1 belongs to said RRC reestablishment procedure.

[0627] As one embodiment, the meaning of the sentence "said behavior suspending SRB1, performing any of cell selection and relay selection, is accompanied by said RRC reestablishment procedure" is that suspending SRB1 necessarily occurs when RRC reestablishment occurs.

[0628] As one embodiment, the meaning of the sentence "said behavior suspending SRB1, performing any of cell selection and relay selection, is accompanied by said RRC reestablishment procedure" is that said behavior performing any of cell selection and relay selection belongs to said RRC reestablishment procedure.

[0629] As one embodiment, the meaning of the sentence "said behavior suspending SRB1, performing any of cell selection and relay selection, is accompanied by said RRC reestablishment procedure" is that performing any of cell selection and relay selection necessarily occurs when RRC reestablishment occurs.

[0630] As one embodiment, the meaning of the sentence "said behavior suspending SRB1, performing any of cell selection and relay selection, is accompanied by said RRC reestablishment procedure" is that performing cell selection or performing relay selection or performing both cell selection and relay selection occurs when RRC reestablishment occurs.

[0631] As one embodiment, said RRC reestablishment procedure comprises initiating an RRC reestablishment request for said second node U02.

[0632] As one embodiment, said RRC reestablishment procedure comprises sending an RRC reestablishment request for a node other than said second node U02.

[0633] As one embodiment, the RRC re-establishment procedure comprises forwarding the RRC re-establishment request by the third node U03.

[0634] As one embodiment, the third message is an RRC message.

[0635] As one embodiment, the third message comprises UEAssistanceInformation.

[0636] As one embodiment, the third message comprises SidelinkUEInformation.

[0637] As one embodiment, the third message comprises FailureInformation.

[0638] As one embodiment, the third message comprises UEInformationResponse.

[0639] As one embodiment, the third message comprises ulInformationTransfer.

[0640] As one embodiment, the RLC entity associated with the first type of bearer is a Uu interface RLC entity.

[0641] As one sub-embodiment of this embodiment, the Uu interface RLC entity corresponds to RLC 303 in embodiment 3.

[0642] As one sub-embodiment of this embodiment, the Uu interface RLC entity corresponds to RLC 353 in embodiment 3.

[0643] As one sub-embodiment of this embodiment, the Uu interface RLC entity is the Uu-RLC entity in (c) of embodiment 7.

[0644] As one embodiment, the second message uses the first bearer.

[0645] As one embodiment, the second message uses the second bearer.

[0646] As one embodiment, the second message uses the first type of bearer.

[0647] As one embodiment, the second message uses the second type of bearer.

[0648] As one embodiment, the second message does not use the first bearer nor the second bearer.

[0649] As one embodiment, the third message uses the first bearer.

[0650] As one embodiment, the third message uses the second bearer.

[0651] As one embodiment, the third message does not use the first bearer and does not use the second bearer.

[0652] As one embodiment, the third message uses the first type of bearer.

[0653] As one embodiment, the third message uses the second type of bearer.

[0654] As one embodiment, the first type of bearer is MRB and the second type of bearer is DRB.

[0655] As one embodiment, the first bearer is for broadcast or groupcast service.

[0656] As one embodiment, the first bearer is a PTM leg of MRB.

[0657] As one embodiment, the second bearer is for broadcast or groupcast service.

[0658] As one embodiment, the second bearer is for unicast service.

[0659] As one embodiment, the second bearer is a PTP leg of MRB.

[0660] As one embodiment, the first signaling includes a first sub-signaling and a second sub-signaling, the first sub-signaling is used to configure the first bearer, and the second sub-signaling is used to configure the second bearer.

[0661] As one embodiment, the first information is FailureInformation, and the third message is SidelinkUEInformationNR.

[0662] As one embodiment, the first information and the third message are both SidelinkUEInformationNR, and the first bearer is the second type of bearer.

[0663] As one embodiment, when the second bearer is detected to fail, there is no available direct path for the first set of cells.

[0664] As one embodiment, the meaning of the phrase "there is no available direct path for the first set of cells" is that the first bearer does not recover from failure.

[0665] As an example, the phrase "no available direct path for the first cell group" means that the first node U01 is not configured with a direct path for the first cell group other than the first bearer.

[0666] As an example, the phrase "no available direct path for the first cell group" means that the radio link corresponding to the first bearer is released and the first node U01 is not configured with a direct path for the first cell group other than the first bearer.

[0667] As an example, the first node U01, in response to the detection of the first bearer failure, sends the first information based on whether the first bearer is the first type of bearer or the second type of bearer;

[0668] The meaning of the sentence "Sending the first information based on whether the first bearer is the first type of bearer or the second type of bearer" is as follows: When the first bearer is the first type of bearer, a failure information transmission process is initiated, which includes sending the first information; when the first bearer is the second type of bearer, a sidelink UE information transmission process for NR sidelink communication is initiated, which includes sending the first information.

[0669] Embodiment 6

[0670] Example 6 illustrates a wireless signal transmission flowchart according to an embodiment of this application, as shown in the attached diagram. Figure 6 As shown. (Attached) Figure 6 In this example, U11 corresponds to the first node of this application. It should be noted that the order in this example does not limit the signal transmission order or the implementation order in this application. Embodiment 6 is based on Embodiment 5. Parts in Embodiment 6 that are needed but not described can be referred to Embodiment 5. The steps in F61 are optional, and step S6105 is also optional.

[0671] for First node U11 In step S6101, a first signaling is received; in step S6102, a first signal is received; in step S6103, a first bearer failure is detected; in step S6104, a first message is sent; and in step S6105, a second bearer failure is detected.

[0672] for Second node U12 In step S6201, the first signaling is sent; in step S6201, the first information is received.

[0673] For Third node U13 The first signal is transmitted in step S6301.

[0674] As one embodiment, the first node U11 is a U2N relay UE.

[0675] As one embodiment, the first node U11 is a U2N remote UE.

[0676] As one embodiment, the first node U11 is a NR ProSe U2N remote UE.

[0677] As one embodiment, the third node U13 is a L2 U2N relay UE.

[0678] As one embodiment, the third node U13 is a neighbor cell of the first node U11.

[0679] As one embodiment, the third node U13 belongs to a same CU as the second node U12.

[0680] As one embodiment, the third node U13 belongs to a same DU as the second node U12.

[0681] As one embodiment, the third node U13 belongs to a same gNB as the second node U12.

[0682] As one embodiment, the third node U13 and the second node U12 are cells with different PCI (physical cell identity) respectively.

[0683] As one embodiment, the third node U13 and the second node U12 are cells within the first cell group respectively.

[0684] As one embodiment, the third node U13 and the second node U12 are another TRP of the first node U11.

[0685] As one embodiment, the third node U13 and the second node U12 are another beam of the first node U11, corresponding to another group of CSI-RS reference signals.

[0686] As one embodiment, the second node U12 is a base station.

[0687] As one embodiment, the second node U12 is a primary cell of the first node U11.

[0688] As one embodiment, the second node U12 is a primary cell group of the first node U11.

[0689] As one embodiment, the second node U12 corresponds to the first cell group or a base station corresponding to the first cell group.

[0690] As one embodiment, the first signaling is sent by the second node U12 directly to the first node U11 without relayed forwarding.

[0691] As one embodiment, the first signaling is sent by the second node U12 to the first node U11 via the third node U13.

[0692] As one embodiment, the first signaling is sent using the first bearer.

[0693] As one embodiment, the first signaling is sent using the first type of bearer.

[0694] As one embodiment, the first signaling is sent using the second bearer.

[0695] As one embodiment, the first signaling is sent using the second type of bearer.

[0696] As one embodiment, the first signaling is sent using a bearer other than the first bearer and the second bearer.

[0697] As one embodiment, the first signaling comprises a first sub-signaling and a second sub-signaling, the first sub-signaling is used to configure the first bearer, and the second sub-signaling is used to configure the second bearer.

[0698] As one embodiment, the first signaling is used to configure the first bearer and the second bearer of the first cell group; the second bearer is associated with the first cell group.

[0699] As one embodiment, the first bearer is the second type of bearer.

[0700] As one embodiment, the first bearer is a sidelink radio link between the first node U11 and the third node U13.

[0701] As one embodiment, the first bearer is a sidelink RLC bearer between the first node U11 and the third node U13.

[0702] As one embodiment, the first bearer is a sidelink RLC bearer between the first node U11 and the third node U13.

[0703] As one embodiment, the first bearer is a sidelink RLC bearer between the first node U11 and the third node U13.

[0704] As one embodiment, the second bearer is not failed when the first bearer is detected to be failed in step S6103.

[0705] As one embodiment, the second bearer is available when the first bearer is detected to be failed in step S6103.

[0706] As one embodiment, the second bearer is the first type of bearer.

[0707] As one embodiment, the first information is sent to the second node U12 through the second bearer.

[0708] As one embodiment, the second bearer is detected to be failed in step S6105 after step S6103.

[0709] As one embodiment, the first bearer has not been recovered when the second bearer is detected to be failed in step S6105.

[0710] As one embodiment, there is no first type of bearer or second type of bearer other than the first bearer and the second bearer when the second bearer is detected to be failed in step S6105.

[0711] As one embodiment, the first signaling is used to configure the second bearer; the second bearer is associated with the first cell group; the second bearer is detected to be failed after the behavior detects the first bearer to be failed.

[0712] As one embodiment, the first node U11 initiates an RRC reestablishment procedure in response to the behavior detecting the second bearer to be failed, suspends SRB1, performs any one of cell selection and relay selection, and sends a third message used to indicate the second bearer to be failed, accompanying the RRC reestablishment procedure.

[0713] As one embodiment, the first bearer is the second type of bearer; the second bearer is the first type of bearer.

[0714] As one embodiment, the RLC entity associated with the first type of bearer is an RLC entity of a Uu interface; the RLC entity associated with the second bearer is an RLC entity of a PC5 interface.

[0715] As one embodiment, the behavior detecting the first bearer to be failed in step S6103 includes that the first bearer occurs a radio link failure.

[0716] As one embodiment, the behavior detecting the first bearer to be failed in step S6103 includes that a sidelink radio link failure occurs between the first node U01 and the third node U03.

[0717] As one embodiment, in step S6103, the behavior detecting the first bearer failure comprises: detecting that HARQ DTX on the first bearer reaches a maximum number of times.

[0718] As one embodiment, in step S6103, the behavior detecting the first bearer failure comprises: detecting that RLC retransmission on the first bearer reaches a maximum number of times.

[0719] As one embodiment, in step S6103, the behavior detecting the first bearer failure comprises: RRC message compatibility failure occurs on the first bearer.

[0720] As one embodiment, in step S6103, the behavior detecting the first bearer failure comprises: RRC message compatibility failure occurs on the PC5 interface between the first node U01 and the third node U03.

[0721] As one embodiment, in step S6103, the behavior detecting the first bearer failure comprises: the first bearer is released.

[0722] As one embodiment, in step S6103, the behavior detecting the first bearer failure comprises: a higher layer of the first node U01 indicates the first bearer failure.

[0723] As one embodiment, in step S6103, the behavior detecting the first bearer failure comprises: detecting that a timer for the first bearer expires.

[0724] As one embodiment, in step S6103, the behavior detecting the first bearer failure comprises: detecting that a T400 timer for the first bearer expires.

[0725] As one embodiment, in step S6103, the behavior detecting the first bearer failure comprises: detecting that a T404 timer for the first bearer expires.

[0726] As one embodiment, in step S6103, the behavior detecting the first bearer failure comprises: detecting that a timer related to path switch for the first bearer expires.

[0727] As one embodiment, in step S6103, the behavior detecting the first bearer failure comprises: detecting that a path switch failure for the first bearer.

[0728] As one embodiment, in response to detecting the first bearer failure in step S6103, the first node U11 performs the first set of operations, and the first bearer is the second type of bearer.

[0729] As one subembodiment of this embodiment, the first operation comprises releasing the RLC entity associated with the first bearer.

[0730] As one subembodiment of this embodiment, the first operation comprises storing information about the first bearer being failed in the first state variable.

[0731] As one subembodiment of this embodiment, the first operation does not comprise storing information about the first bearer being failed in the first state variable.

[0732] As one subembodiment of this embodiment, the first operation comprises storing information about the first bearer being failed in a variable other than the first state variable.

[0733] As one subembodiment of this embodiment, the first operation does not comprise storing information about the first bearer being failed.

[0734] As one embodiment, step S6103 detecting the second bearer being failed comprises detecting that a radio link failure occurs for the second bearer.

[0735] As one embodiment, step S6103 detecting the second bearer being failed comprises detecting that a radio link failure occurs for the radio link between the first node U11 and the second node U12.

[0736] As one embodiment, step S6103 detecting the second bearer being failed comprises detecting that a timer T310 expires.

[0737] As one embodiment, step S6103 detecting the second bearer being failed comprises detecting that a timer T312 expires.

[0738] As one embodiment, step S6103 detecting the second bearer being failed comprises detecting that a timer T304 expires.

[0739] As one embodiment, step S6103 detecting the second bearer being failed comprises detecting that a problem occurs for a random access procedure towards the second node U12.

[0740] As one embodiment, step S6103 detecting the second bearer being failed comprises detecting that the second bearer reaches a maximum number of RLC retransmissions.

[0741] As one embodiment, step S6103 detecting the second bearer being failed comprises detecting that a persistent LBT failure occurs.

[0742] As one embodiment, step S6105 triggering the first node U11 to initiate RRC reestablishment.

[0743] As an example, the first signal is a signal on the secondary link.

[0744] As one embodiment, the first signal is or includes a reference signal.

[0745] As one embodiment, the first signal is or includes a wireless link on a secondary link.

[0746] As one embodiment, the first signal is or includes data or signaling on the secondary link.

[0747] As one embodiment, the first signal is or includes a discovery signal on the secondary link.

[0748] As one embodiment, the first signal is or includes an RRC message on the secondary link.

[0749] As one embodiment, the first signal is or includes notificationMessageSidelink.

[0750] As one embodiment, the first signal is or includes a signal for releasing the link between the first node U11 and the third node U13.

[0751] As an example, the first signal is or includes DIRECT LINK RELEASE REQUEST.

[0752] As an example, the first information indicates the mapping relationship between the SRB1 of the first node U11 and the first bearer.

[0753] As an example, the first information indicates the mapping relationship between the SRB1 of the first node U11 and the second bearer.

[0754] Embodiment 7

[0755] Example 7 illustrates a schematic diagram of a relay communication protocol stack according to an embodiment of this application, as shown in the attached diagram. Figure 7 As shown.

[0756] Appendix Figure 7 Divide into three subgraphs: (a), (b), and (c).

[0757] Appendix Figure 7 The protocol stack shown is applicable to L2 U2N relay communication. Example 7 is based on Example 3.

[0758] Appendix Figure 7 (a) in the text corresponds to the user plane protocol stack in L2 U2N relay communication; Appendix Figure 7(b) in the L2 U2N relay communication corresponds to the control plane protocol stack in the L2 U2N relay communication.

[0759] As an embodiment, the first relay is a relay when the first node uses a non-direct path.

[0760] As an embodiment, the first relay is a L2 U2N relay UE between the first node and the first cell group.

[0761] As an embodiment, the gNB in (a) is a gNB in the first cell group. Figure 7 As an embodiment, the gNB in (a) is a gNB corresponding to the first cell group.

[0762] Figure 7 As an embodiment, the gNB in (a) is a gNB belonging to the first cell group.

[0763] As an embodiment, the gNB in (a) is a gNB corresponding to a PCell of the first cell group. Figure 7 As an embodiment, the gNB in (a) is a gNB belonging to the first cell group.

[0764] Figure 7 As an embodiment, the gNB in (a) is a gNB corresponding to the first cell group.

[0765] In embodiment 7, the PC5 interface is an interface between the first node and the first relay, and protocol entities {PC5-SRAP, PC5-RLC, PC5-MAC, PC5-PHY} related to the PC5 interface are terminated at the first node and the first relay; the Uu interface is an interface between a UE and a gNB, and protocol entities of the Uu interface are terminated at the UE and the gNB, respectively.

[0766] As an embodiment, the first relay is a U2N relay UE, and before performing the first signaling, the first relay provides L2 U2N relay service to the first node.

[0767] As an embodiment, the first node and the first relay are both UEs.

[0768] As an embodiment, the gNB in (a) corresponds to the second node of the application. Figure 7 As an embodiment, the gNB in (a) corresponds to the second node of the application.

[0769] As an embodiment, protocol entities {Uu-SRAP, Uu-RLC, Uu-MAC, Uu-PHY} of the Uu interface are terminated at the first relay and the gNB.

[0770] ​​As an embodiment, in (a), the protocol entities {Uu-SDAP, Uu-PDCP} of the Uu interface are terminated at the first node and the gNB, the SDAP PDU and the PDCP PDU of the first node are forwarded through the first relay, but the first relay does not modify the SDAP PDU and the PDCP PDU of the first node, that is, the SDAP PDU and the PDCP PDU sent by the first node to the gNB are transparent to the first relay.

[0771] As an embodiment, in (b), the protocol entities {Uu-RRC, Uu-PDCP} of the Uu interface are terminated at the first node and the gNB, the RRC PDU and the PDCP PDU of the first node are forwarded through the first relay, but the first relay does not modify the RRC PDU and the PDCP PDU sent by the first node, that is, the RRC PDU and the PDCP PDU sent by the first node to the gNB are transparent to the first relay.

[0772] As an embodiment, in (a), the PC5-SRAP corresponds to the SRAP 357 in the PC5-SL interface, the PC5-RLC corresponds to the RLC 353 in the PC5-SL interface, the PC5-MAC corresponds to the MAC 352 in the PC5-SL interface, the PC5-PHY corresponds to the PHY 351 in the PC5-SL interface. Figure 3 Figure 3 As an embodiment, in (a), the Uu-SDAP corresponds to the SDAP 356 in the Uu interface, the Uu-PDCP corresponds to the PDCP 354 in the Uu interface. Figure 3 Figure 3 As an embodiment, in (a), the PC5-SRAP corresponds to the SRAP 357 in the PC5-SL interface, the PC5-RLC corresponds to the RLC 353 in the PC5-SL interface, the PC5-MAC corresponds to the MAC 352 in the PC5-SL interface, the PC5-PHY corresponds to the PHY 351 in the PC5-SL interface.

[0773] As an embodiment, in (b), the Uu-RRC corresponds to the RRC 306 in the Uu interface, the Uu-PDCP corresponds to the PDCP 304 in the Uu interface. Figure 3 Figure 3 As an embodiment, in (b), the PC5-SRAP corresponds to the SRAP 307 in the PC5-SL interface, the PC5-RLC corresponds to the RLC 303 in the PC5-SL interface, the PC5-MAC corresponds to the MAC 302 in the PC5-SL interface, the PC5-PHY corresponds to the PHY 301 in the PC5-SL interface.

[0774] As an embodiment, in (b), the Uu-RRC corresponds to the RRC 306 in the Uu interface, the Uu-PDCP corresponds to the PDCP 304 in the Uu interface. Figure 3 Figure 3 As an embodiment, in (b), the PC5-SRAP corresponds to the SRAP 307 in the PC5-SL interface, the PC5-RLC corresponds to the RLC 303 in the PC5-SL interface, the PC5-MAC corresponds to the MAC 302 in the PC5-SL interface, the PC5-PHY corresponds to the PHY 301 in the PC5-SL interface. Figure 3 Figure 3 As an embodiment, in (b), the Uu-RRC corresponds to the RRC 306 in the Uu interface, the Uu-PDCP corresponds to the PDCP 304 in the Uu interface.

[0775] As an embodiment, in (b), the Uu-RRC corresponds to the RRC 306 in the Uu interface, the Uu-PDCP corresponds to the PDCP 304 in the Uu interface. Figure 3 Figure 3 As an embodiment, in (b), the PC5-SRAP corresponds to the SRAP 307 in the PC5-SL interface, the PC5-RLC corresponds to the RLC 303 in the PC5-SL interface, the PC5-MAC corresponds to the MAC 302 in the PC5-SL interface, the PC5-PHY corresponds to the PHY 301 in the PC5-SL interface.

[0776] As an embodiment, in (b), the Uu-RRC corresponds to the RRC 306 in the Uu interface, the Uu-PDCP corresponds to the PDCP 304 in the Uu interface. Figure 7 ​​​​​​One cell of the gNB is a PCell of the first relay, the first relay is in RRC connected state.

[0777] As one embodiment, the first cell group is a MCG of the first relay.

[0778] As one embodiment, PC5-SRAP is only used for specific RB or message or data.

[0779] As one sub-embodiment of this embodiment, PC5-SRAP layer is not used when the first relay forwards system information of gNB.

[0780] As one embodiment, the first node is a relay node. Figure 7 In one embodiment, the communication between the first node and the gNB uses non-direct path.

[0781] As one embodiment, the first node is a relay node. Figure 7 In one embodiment, the communication between the first node and the gNB uses direct path.

[0782] As one embodiment, the first node is a relay node. Figure 7 In one embodiment, the communication between the first node and the gNB uses both direct path and non-direct path.

[0783] As one embodiment, the first signaling is generated by Uu-RRC of the gNB in (b), received by Uu-RRC of the first node. Figure 7

[0784] As one embodiment, the first signaling is transparent to the first relay.

[0785] As one embodiment, the first information is forwarded by the first relay to gNB.

[0786] As one embodiment, the first information is directly sent to gNB without forwarding by relay.

[0787] As one embodiment, when non-direct path is used, Uu-PDCP of the first node is associated with PC5-RLC, or associated with PC5-RLC through PC5-SRAP.

[0788] As one embodiment, when direct path is used, the first node will establish Uu-RLC, Uu-PDCP of the first node is associated with Uu-RLC.

[0789] As one sub-embodiment of this embodiment, after switching to the direct path, the first node releases PC5-RLC.

[0790] ​As a sub-implementation of this embodiment, after switching to the direct path, the first node releases PC5-SRAP.

[0791] As a sub-implementation of this embodiment, after switching to the direct path, the first node releases PC5-MAC and PC5-PHY.

[0792] As a sub-implementation of this embodiment, after switching to the direct path, the first node no longer uses PC5-SRAP.

[0793] As a sub-implementation of this embodiment, after switching to the direct path, there are no other protocol layers between the Uu-PDCP and Uu-RLC of the first node.

[0794] As one embodiment, the second type of bearer is attached Figure 7 The wireless link between the first node and the first relay in (a) and / or (b).

[0795] As one embodiment, the second type of bearer is attached Figure 7 The secondary wireless link between the first node and the first relay in (a) and / or (b).

[0796] As one embodiment, the second type of bearer is attached Figure 7 The secondary link RLC bearer between the first node and the first relay in (a) and / or (b).

[0797] As one embodiment, the second type of bearer is attached Figure 7 The transmission channel between the first node and the first relay in (a) and / or (b).

[0798] As one embodiment, the second type of bearer is attached Figure 7 The logical channel between the first node and the first relay in (a) and / or (b).

[0799] As one embodiment, the second type of bearer is attached Figure 7 The physical channel between the first node and the first relay in (a) and / or (b).

[0800] As one embodiment, the second type of bearer is attached Figure 7 The direct unicast link between the first node and the first relay in (a) and / or (b).

[0801] As one embodiment, the second type of bearer is attached Figure 7 The interface between the first node and the first relay PC5-SRAP entity in (a) and / or (b).

[0802] As one embodiment, the second type of bearer is a PC5 interface between the first node and the first relay in (a) and / or (b). Figure 7

[0803] As one embodiment, the second type of bearer is a PC5 interface between the first node and the first relay in (a) and / or (b). Figure 7 As one embodiment, the second type of bearer is a PC5 interface between the first node and the first relay in (a) and / or (b).

[0804] Figure 7 As one embodiment, the second type of bearer is a PC5 interface between the first node and the first relay in (a) and / or (b).

[0805] As one embodiment, the first type of bearer is a radio bearer between the first node and the gNB in (c). Figure 7 As one embodiment, the first type of bearer is a radio link between the first node and the gNB in (c).

[0806] Figure 7 As one embodiment, the first type of bearer is a RLC bearer between the first node and the gNB in (c).

[0807] As one embodiment, the first type of bearer is a channel between the first node and the gNB in (c). Figure 7 As one embodiment, the first type of bearer is a logical channel between the first node and the gNB in (c).

[0808] Figure 7 As one embodiment, the first type of bearer is a physical channel between the first node and the gNB in (c).

[0809] As one embodiment, the first type of bearer is a Uu interface between the first node and the gNB in (c). Figure 7

[0810] Embodiment 8

[0811] Figure 8

[0812] Embodiment 9

[0813] Embodiment 8 illustrates a diagram of a topology according to one embodiment of the present application, as shown in FIG. 8. Figure 9

[0814] The topology of Embodiment 8 and the definitions of the first type of bearer and the second type of bearer apply to other embodiments including Embodiment 5.​​​​​​​​​​

[0815] The first node in Embodiment 8 corresponds to the first node of the present application.

[0816] As one embodiment, the second node in Embodiment 8 corresponds to the first cell group of the present application.

[0817] As one embodiment, the second node in Embodiment 8 corresponds to the primary cell of the first cell group of the present application.

[0818] As one embodiment, the second node in Embodiment 8 corresponds to the gNB corresponding to the first cell group of the present application.

[0819] As one embodiment, the second node in Embodiment 8 corresponds to the PCell of the first node of the present application.

[0820] As one embodiment, the second node in Embodiment 8 corresponds to one transmission point of the primary cell group of the first node of the present application.

[0821] As one embodiment, the third node in Embodiment 8 is a relay node of the first node.

[0822] As one embodiment, the third node in Embodiment 8 is a relay node of the first node to the second node.

[0823] As one embodiment, the third node in Embodiment 8 is an L2 U2N relay UE of the first node.

[0824] As one embodiment, the third node in Embodiment 8 is an SCell of the first cell group.

[0825] As one embodiment, the third node in Embodiment 8 is a transmission point of the first cell group.

[0826] As one embodiment, the third node in Embodiment 8 is a cell other than a PCell.

[0827] As one embodiment, the third node in Embodiment 8 is a neighbor cell.

[0828] As one embodiment, the third node in Embodiment 8 is a repeater of the first cell group.

[0829] As one embodiment, the third node in Embodiment 8 is a node of TN.

[0830] As one embodiment, the third node in Embodiment 8 is a node of NTN.

[0831] As one embodiment, the first type of bearer refers to a bearer between the first node and the second node.

[0832] As one embodiment, the first type of bearer refers to a wireless link between the first node and the second node.

[0833] As one embodiment, the first type of bearer refers to an RLC bearer between the first node and the second node.

[0834] As one embodiment, the first type of bearer refers to a communication link between the first node and the second node.

[0835] As one embodiment, the first type of bearer refers to a channel between the first node and the second node.

[0836] As one embodiment, the first type of bearer refers to a communication interface between the first node and the second node.

[0837] As one embodiment, the first type of bearer is relay independent.

[0838] As one embodiment, the second type of bearer is relay dependent.

[0839] As one embodiment, the second type of bearer is a bearer between the first node and the third node.

[0840] As one embodiment, the second type of bearer is a sidelink wireless link between the first node and the third node.

[0841] As one embodiment, the second type of bearer is a communication link between the first node and the third node.

[0842] As one embodiment, the second type of bearer is a communication interface between the first node and the third node.

[0843] As one embodiment, the second type of bearer is a sidelink RLC bearer between the first node and the third node.

[0844] As one embodiment, the second type of bearer is a channel between the first node and the third node.

[0845] As one embodiment, the second type of bearer is a bearer between the first node and the second node, via the third node.

[0846] As one embodiment, the second type of bearer is a communication link between the first node and the second node, via the third node.

[0847] As one embodiment, the second type of bearer comprises a sidelink RLC bearer between the first node and the third node and a RLC bearer between the third node and the second node.

[0848] As one embodiment, the second type of bearer comprises a channel between the first node and the third node and a channel between the third node and the second node.

[0849] As one embodiment, the second type of bearer comprises a sidelink radio link between the first node and the third node and a radio link between the third node and the second node.

[0850] As one embodiment, the first type of bearer is a direct path.

[0851] As one embodiment, the link between the first node and the second node that is not forwarded through the third node is a direct path.

[0852] As one embodiment, the link between the first node and the second node that is forwarded through the third node is a non-direct path.

[0853] As one embodiment, a direct path is a way or transmission path in which the first node and the second node communicate without the third node.

[0854] As one embodiment, a non-direct path is a way or transmission path in which the first node and the second node communicate through the third node.

[0855] As one embodiment, the first type of bearer is or belongs to a direct path.

[0856] As one embodiment, the second type of bearer is a non-direct path.

[0857] As one embodiment, the first type of bearer and the second type of bearer are both for the first node.

[0858] As one embodiment, the first type of bearer and the second type of bearer are both for data transmission of the first node and the second node.

[0859] As one embodiment, the second type of bearer comprises a transmission path between the first node and the third node and between the third node and the second node.

[0860] As one subembodiment of this embodiment, the first bearer is the second type of bearer, and the behavior detecting the first bearer failure means detecting any one of a failure between the first node and the third node, or between the third node and the second node.

[0861] As one subembodiment of this embodiment, the second bearer is the second type of bearer, and the behavior detecting the second bearer failure means detecting any one of a failure between the first node and the third node, or between the third node and the second node.

[0862] As one embodiment, the failure of the second type of bearer includes a failure of a direct link between the first node and the third node.

[0863] As one embodiment, the failure of the second type of bearer includes a release of a direct link between the first node and the third node.

[0864] As one embodiment, detecting the failure of the second type of bearer includes not receiving feedback for keep alive from the third node.

[0865] As one embodiment, the second type of bearer includes a direct link between the first node and the third node.

[0866] As one embodiment, the second type of bearer includes a PC5 direct link between the first node and the third node.

[0867] Embodiment 10

[0868] Embodiment 9 illustrates a diagram of first information being used to indicate a first bearer failure, according to one embodiment of the application, as shown in FIG. 9. Figure 10

[0869] As one embodiment, the first information explicitly indicates the first bearer failure.

[0870] As one embodiment, the first information implicitly indicates the first bearer failure.

[0871] As one embodiment, the first information explicitly indicates a cause of the first bearer failure.

[0872] As one embodiment, the first information explicitly indicates a type of the first bearer failure.

[0873] As one embodiment, the sending of the first information indicates the first bearer failure.

[0874] As one embodiment, the first information is one or more fields of an RRC message.​

[0875] As one embodiment, the first information is one or more information elements of an RRC message.

[0876] As one embodiment, the first information indicates an identity of the first bearer.

[0877] As one embodiment, the first information indicates a logical channel identity of the first bearer.

[0878] As one embodiment, the first information indicates a cell group identity of the first bearer.

[0879] As one embodiment, the first information indicates a cell identity of the first bearer.

[0880] As one embodiment, the first information indicates a time of deactivation of the first bearer.

[0881] As one embodiment, the first information indicates whether the first bearer is the first type of bearer.

[0882] As one embodiment, the first information indicates whether the first bearer is the second type of bearer.

[0883] As one embodiment, a resource occupied by the first information indicates whether the first bearer is the first type of bearer or the second type of bearer.

[0884] As one embodiment, a bearer occupied by the first information indicates whether the first bearer is the first type of bearer or the second type of bearer.

[0885] As one embodiment, the first information indicates deactivation of the second type of bearer when the first information is sent on the first type of bearer.

[0886] As one embodiment, the first information indicates deactivation of the first type of bearer when the first information is sent on the second type of bearer.

[0887] As one embodiment, the first information indicates an identity of a relay of the first node.

[0888] As one sub-embodiment of this embodiment, the first bearer is the first type of bearer.

[0889] As one sub-embodiment of this embodiment, the first bearer is the second type of bearer.

[0890] As one embodiment, the first information indicates rlc-failure when the first bearer is the first type of bearer.

[0891] As an example, when the first bearer is the second type of bearer, the first information indicates sl-rlc-failure.

[0892] As one example, the first information includes the failureType field.

[0893] As one embodiment, the first information indicates the logical channel identity corresponding to the first bearer.

[0894] As an example, the first information indicates the temporary identity of the first node, which is an identity in the SRAP layer of the first node.

[0895] As a sub-implementation of this embodiment, the first bearer is the first type of bearer.

[0896] As a sub-implementation of this embodiment, the first bearer is the second type of bearer.

[0897] Embodiment 11

[0898] Example 10 illustrates a schematic diagram of how first information, according to an embodiment of this application, is used to indicate whether a first bearer is a second type of bearer, as shown in the attached diagram. Figure 11 As shown.

[0899] As an example, the first information explicitly indicates whether the first bearer is the second type of bearer.

[0900] As an example, the first information explicitly indicates that the first bearer is the first type of bearer, and when the first information does not indicate that the first bearer is the first type of bearer, the first bearer is the second type of bearer.

[0901] As an example, a field of the first information explicitly indicates whether the first bearer is the second type of bearer.

[0902] As one embodiment, the first information indicates that the first bearer is the second type of bearer by indicating a non-direct path.

[0903] As one embodiment, the first information indicates that the first bearer is the second type of bearer by indicating the L2 U2N relay UE.

[0904] As an example, the first information indicates that the first bearer is the second type of bearer by indicating a configuration index of a non-direct path.

[0905] As an example, the first information indicates that the first bearer is the second type of bearer by indicating a configuration index used for relaying.

[0906] As one embodiment, the first information indicates that the first bearer is the second type of bearer by indicating a sidelink configuration index used for relaying.

[0907] As one embodiment, the first information indicates that the first bearer is the second type of bearer by indicating a configuration used for PC5 interface.

[0908] As one embodiment, the first information indicates that the first bearer is the second type of bearer by indicating an RLC entity associated with the first bearer.

[0909] As one embodiment, the first information indicates that the first bearer is the second type of bearer by indicating a type of RLC entity associated with the first bearer.

[0910] As one embodiment, the first information indicates that the first bearer is the second type of bearer by indicating a logical channel associated with the first bearer.

[0911] As one embodiment, the first information indicates that the first bearer is the second type of bearer by indicating a specific failure type.

[0912] As one embodiment, the first information indicates that the first bearer is the second type of bearer by indicating a reason or a type of failure of the first bearer.

[0913] Embodiment 12

[0914] Embodiment 11 illustrates a diagram of a third message being used to indicate a failure of a second bearer according to one embodiment of the application, as shown in FIG. 11. Figure 12 As one embodiment, the third message is an uplink message.

[0915] As one embodiment, the third message is an RRC message.

[0916] As one embodiment, the third message is an RRC message.

[0917] As one embodiment, at least one field of the third message indicates the failure of the second bearer.

[0918] As one embodiment, the third message explicitly indicates the failure of the second bearer.

[0919] As one embodiment, the third message implicitly indicates the failure of the second bearer.

[0920] As one embodiment, the sending of the third message indicates the failure of the second bearer.

[0921] As one embodiment, a resource occupied by the third message indicates the failure of the second bearer.

[0922] As one embodiment, the third message indicates the second bearer is deactivated using a bearer used by the third message.

[0923] As one embodiment, the third message indicates the second bearer is deactivated using the first bearer transmission.

[0924] As one embodiment, the third message indicates the second bearer is deactivated by indicating an identity of the second bearer.

[0925] As one embodiment, the third message indicates the second bearer is deactivated by indicating a configuration index of the second bearer.

[0926] As one embodiment, the third message indicates the second bearer is deactivated by indicating a logical channel identity associated with or corresponding to the second bearer.

[0927] As one embodiment, the third message indicates the second bearer is deactivated by indicating an interface associated with or corresponding to the second bearer.

[0928] As one embodiment, the third message indicates the second bearer is deactivated by indicating an index of the second bearer.

[0929] As one embodiment, the third message indicates the second bearer is deactivated by indicating a transmission path associated with or corresponding to the second bearer.

[0930] As one embodiment, the third message indicates the second bearer is deactivated by indicating a non-direct path.

[0931] As one embodiment, the third message indicates the second bearer is deactivated by indicating an L2 U2N relay UE of the first node.

[0932] As one embodiment, the third message indicates the second bearer is deactivated by indicating a candidate relay.

[0933] As one embodiment, the third message indicates the second bearer is deactivated by indicating a measurement result of an L2 U2N relay UE of the first node.

[0934] As one embodiment, the third message indicates the second bearer is deactivated by indicating a measurement report or a triggering event associated with a sidelink of the second bearer is satisfied.

[0935] As one embodiment, the third message indicates the second bearer is deactivated by indicating a temporary identity associated with the second bearer.

[0936] Figure 12

[0937] Embodiment 12 illustrates a structure block diagram of a processing apparatus in a first node according to one embodiment of the present application; as shown in FIG. 12. In FIG. 12, the processing apparatus 1200 in the first node includes a first receiver 1201 and a first transmitter 1202. In Embodiment 12, the first receiver 1201 detects a first bearer failure; the first bearer is associated with a first cell group; in response to the act of detecting the first bearer failure, performs a first set of operations; the first set of operations is related to a type of the first bearer. ​ ​ In Embodiment 12, the first transmitter 1202, in response to the act of detecting the first bearer failure, transmits a first information; the first information is used to indicate the first bearer failure; in response to all conditions in a first set of conditions being met, transmits a second message; the second message indicates that there is available information.

[0938] In Embodiment 12, the first set of conditions includes a first state variable storing the available information; the meaning of the sentence that the first set of operations is related to the type of the first bearer is that: when the first bearer is a first type of bearer, the first set of operations includes at least one of reestablishing an RLC entity associated with the first bearer and storing information for the first bearer failure in the first state variable; when the first bearer is a second type of bearer, the first set of operations includes at least releasing the RLC entity associated with the first bearer.

[0939] In Embodiment 12, the first transmitter 1202, in response to the act of detecting the first bearer failure, transmits a first information; the first information is used to indicate the first bearer failure; in response to all conditions in a first set of conditions being met, transmits a second message; the second message indicates that there is available information.

[0940] In Embodiment 12, the first set of conditions includes a first state variable storing the available information; the meaning of the sentence that the first set of operations is related to the type of the first bearer is that: when the first bearer is a first type of bearer, the first set of operations includes at least one of reestablishing an RLC entity associated with the first bearer and storing information for the first bearer failure in the first state variable; when the first bearer is a second type of bearer, the first set of operations includes at least releasing the RLC entity associated with the first bearer.

[0941] In Embodiment 12, the first transmitter 1202, in response to the act of detecting the first bearer failure, transmits a first information; the first information is used to indicate the first bearer failure; in response to all conditions in a first set of conditions being met, transmits a second message; the second message indicates that there is available information.

[0942] In Embodiment 12, the first set of conditions includes a first state variable storing the available information; the meaning of the sentence that the first set of operations is related to the type of the first bearer is that: when the first bearer is a first type of bearer, the first set of operations includes at least one of reestablishing an RLC entity associated with the first bearer and storing information for the first bearer failure in the first state variable; when the first bearer is a second type of bearer, the first set of operations includes at least releasing the RLC entity associated with the first bearer.

[0943] In Embodiment 12, the first transmitter 1202, in response to the act of detecting the first bearer failure, transmits a first information; the first information is used to indicate the first bearer failure; in response to all conditions in a first set of conditions being met, transmits a second message; the second message indicates that there is available information.

[0944] ​As an embodiment, the first set of operations comprises resetting a MAC associated with the first bearer; the first type of bearer is an RLC bearer, and the second type of bearer is a sidelink RLC bearer.

[0945] As an embodiment, the first bearer is the first type of bearer; the storing, in the first state variable, of information for failure of the first bearer comprises storing a cause of the failure of the first bearer and whether a second type of bearer is used; the cause of the failure of the first bearer belongs to a first set of candidate causes, the first set of candidate causes comprising radio link failure, cell handover failure, and path switch failure.

[0946] As an embodiment, the first receiver 1201 receives first signaling, the first signaling being used to configure a second bearer; one of the first bearer and the second bearer is the first type of bearer and the other is the second type of bearer; the second bearer is associated with the first set of cells;

[0947] The first transmitter 1202, before transmitting the first information, sets a primary path of a PDCP entity of SRB1 to be for the second bearer;

[0948] wherein the first signaling indicates that SRB1 is associated with both the first bearer and the second bearer and the primary path of the PDCP entity of SRB1 is for the first bearer; SRB1 is not configured with PDCP duplication; the first information comprises a first measurement result; and the first information is used to indicate whether the first bearer is the second type of bearer.

[0949] As an embodiment, the first receiver 1201 receives first signaling, the first signaling being used to configure a second bearer; the second bearer is associated with the first set of cells; after the behavior detects failure of the first bearer, failure of the second bearer is detected;

[0950] The first transmitter 1202, in response to the behavior detecting failure of the second bearer, initiates an RRC re-establishment procedure, suspends SRB1, performs any one of cell selection and relay selection, and transmits a third message, the third message being used to indicate the failure of the second bearer;

[0951] wherein the first bearer is the first type of bearer; the second bearer is the second type of bearer; the first bearer is not recovered when the behavior detects failure of the second bearer; an RLC entity associated with the first type of bearer is an RLC entity of a Uu interface; and an RLC entity associated with the second bearer is an RLC entity of a PC5 interface.

[0952] As an embodiment, the first receiver 1201 receives a first signaling, the first signaling being used for configuring a second bearer; the second bearer being associated with the first cell group; after the behavior detects that the first bearer is failed, detecting that the second bearer is failed;

[0953] The first transmitter 1202 initiates a RRC reestablishment procedure in response to the behavior detecting that the second bearer is failed, suspends SRB1, performs any one of cell selection and relay selection, and sends a third message, the third message being used for indicating that the second bearer is failed;

[0954] Wherein, the first bearer is the second type of bearer; the second bearer is the first type of bearer; when the behavior detects that the second bearer is failed, the first bearer is not recovered; the RLC entity associated with the first type of bearer is a RLC entity of a Uu interface; the RLC entity associated with the second bearer is a RLC entity of a PC5 interface.

[0955] As an embodiment, the first transmitter 1202 sends the first information according to whether the first bearer is the first type of bearer or the second type of bearer in response to the behavior detecting that the first bearer is failed;

[0956] Wherein, the meaning of the sentence sending the first information according to whether the first bearer is the first type of bearer or the second type of bearer is: when the first bearer is the first type of bearer, initiating a failure information transmission procedure, the behavior initiating the failure information transmission procedure including sending the first information; when the first bearer is the second type of bearer, initiating a sidelink UE information transmission procedure for NR sidelink communication, the behavior initiating the sidelink UE information transmission procedure for NR sidelink communication including sending the first information.

[0957] As an embodiment, the first node is a user equipment (UE).

[0958] As an embodiment, the first node is a terminal supporting large latency difference.

[0959] As an embodiment, the first node is a terminal supporting NTN.

[0960] As an embodiment, the first node is an aircraft or a ship.

[0961] As an embodiment, the first node is a mobile phone or a vehicle terminal.

[0962] As an embodiment, the first node is a relay UE and / or a U2N remote UE.

[0963] As an embodiment, the first node is an Internet of Things terminal or an Industrial Internet of Things terminal.

[0964] As an embodiment, the first node is a device supporting low latency and high reliability transmission.

[0965] As an embodiment, the first node is a sidelink communication node.

[0966] As an embodiment, the first receiver 1201 includes at least one of the antenna 452, the receiver 454, the receiving processor 456, the multi-antenna receiving processor 458, the controller / processor 459, the memory 460, or the data source 467 in Embodiment 4.

[0967] As an embodiment, the first transmitter 1202 includes at least one of the antenna 452, the transmitter 454, the transmitting processor 468, the multi-antenna transmitting processor 457, the controller / processor 459, the memory 460, or the data source 467 in Embodiment 4.

[0968] A person of ordinary skill in the art can understand that all or part of the steps of the above method can be instructed by a program to complete the relevant hardware, and the program can be stored in a computer readable storage medium, such as a read-only memory, a hard disk, or an optical disk, etc. Alternatively, all or part of the steps of the above embodiment can also be implemented using one or more integrated circuits. Correspondingly, each module unit in the above embodiment can be implemented in the form of hardware or in the form of a software function module, and the present application is not limited to any specific form of combination of software and hardware. The user equipment, terminal and UE in the present application include but are not limited to unmanned aerial vehicles, communication modules on unmanned aerial vehicles, remote control aircrafts, aircrafts, small aircrafts, mobile phones, tablet computers, notebooks, vehicle-mounted communication devices, wireless sensors, network cards, Internet of Things terminals, RFID terminals, NB-IoT terminals, MTC (Machine Type Communication) terminals, eMTC (enhanced MTC) terminals, data cards, network cards, vehicle-mounted communication devices, low-cost mobile phones, low-cost tablet computers, satellite communication devices, ship communication devices, NTN user equipment, and other wireless communication devices. The base station or system equipment in the present application includes but is not limited to macro cellular base stations, micro cellular base stations, home base stations, relay base stations, gNB (NR NodeB) NR NodeB, TRP (Transmitter Receiver Point), NTN base station, satellite equipment, flight platform equipment, and other wireless communication devices.

[0969] This application can be implemented in other specific forms without departing from its core or essential characteristics. Accordingly, the presently disclosed embodiments are to be considered in all respects as illustrative and not restrictive, the scope of the application being indicated by the appended claims rather than by the foregoing description, and all changes which come within the meaning and range of equivalency of the claims are to be embraced therein.

Claims

1. A first node for wireless communication, wherein, comprising: a first receiver that detects a failure of a first bearer, the first bearer being associated with a first cell group; in response to detecting the failure of the first bearer, a first set of operations is performed, the first set of operations being related to a type of the first bearer; a first transmitter that, in response to detecting the failure of the first bearer, transmits first information on a second bearer, the first information being used to indicate the failure of the first bearer; in response to all conditions in a first set of conditions being met, a second message is transmitted, the second message indicating that there is information available; the second bearer being associated with the first cell group; wherein the first cell group is a master cell group; wherein the first set of conditions includes a first status variable storing the information available; wherein the first set of operations being related to the type of the first bearer means that when the first bearer is a first type of bearer, the first set of operations includes at least one of re-establishing a RLC (Radio Link Control) entity associated with the first bearer and storing in the first status variable information for the failure of the first bearer; when the first bearer is a second type of bearer, the first set of operations includes at least releasing a RLC entity associated with the first bearer; wherein the RLC entity associated with the first type of bearer is a RLC entity of a Uu interface; wherein the RLC entity associated with the second type of bearer is a RLC entity of a PC5 interface; wherein the first type of bearer uses a primary link; the second type of bearer uses a secondary link; and wherein a SRB1 (signaling radio bearer 1) of the first node is associated with both the first bearer and the second bearer.

2. The first node of claim 1, wherein: the first bearer is the second type of bearer, and the second bearer is the first type of bearer.

3. The first node of claim 2, wherein: the first node is configured with only one cell group.

4. The first node of claim 2, wherein: the first set of operations includes resetting a MAC (medium access control) associated with the first bearer, the first type of bearer is a RLC bearer, and the second type of bearer is a secondary link RLC bearer.

5. The first node of claim 1, wherein: the first bearer is the first type of bearer; storing in the first status variable information for the failure of the first bearer includes storing a cause of the failure of the first bearer and whether the second type of bearer is used; the cause of the failure of the first bearer belongs to a first set of candidate causes, the first set of candidate causes including a radio link failure, a cell handover failure, and a path switch failure.

6. The first node of claim 1, wherein: the first type of bearer is a SRB (signaling radio bearer), and the second type of bearer is a DRB (data radio bearer).

7. The first node of claim 1, wherein: the first receiver is further configured to receive first signaling, the first signaling being used to configure the second bearer; detect the second bearer failure after detecting the first bearer failure; the first transmitter is further configured to initiate a radio resource control (RRC) re-establishment procedure in response to detecting the second bearer failure, suspend SRB1 in conjunction with the RRC re-establishment procedure, and perform any one of cell selection and relay selection; and transmit a third message, the third message being used to indicate the second bearer failure; wherein the first bearer is the first type of bearer and the second bearer is the second type of bearer; and the first bearer is not recovered when the second bearer failure is detected.

8. The first node of claim 1, wherein the first receiver is further configured to receive first signaling, the first signaling being used to configure the second bearer; detect the second bearer failure after detecting the first bearer failure; the first transmitter is further configured to initiate a radio resource control (RRC) re-establishment procedure in response to detecting the second bearer failure, suspend SRB1 in conjunction with the RRC re-establishment procedure, and perform any one of cell selection and relay selection; and transmit a third message, the third message being used to indicate the second bearer failure; wherein the first bearer is the second type of bearer and the second bearer is the first type of bearer; and the first bearer is not recovered when the second bearer failure is detected.

9. The first node of claim 1, wherein the first transmitter is further configured to transmit the first information in response to detecting the first bearer failure according to whether the first bearer is the first type of bearer or the second type of bearer; wherein transmitting the first information according to whether the first bearer is the first type of bearer or the second type of bearer means: initiating a failure information transfer procedure when the first bearer is the first type of bearer, the failure information transfer procedure including transmitting the first information; and initiating a sidelink UE information transfer procedure for NR sidelink communication when the first bearer is the second type of bearer, the sidelink UE information transfer procedure for NR sidelink communication including transmitting the first information.

10. The first node of claim 2, wherein the first transmitter is further configured to transmit the first information in response to detecting the first bearer failure according to whether the first bearer is the first type of bearer or the second type of bearer; wherein transmitting the first information according to whether the first bearer is the first type of bearer or the second type of bearer means: initiating a failure information transfer procedure when the first bearer is the first type of bearer, the failure information transfer procedure including transmitting the first information; and initiating a sidelink UE information transfer procedure for NR sidelink communication when the first bearer is the second type of bearer, the sidelink UE information transfer procedure for NR sidelink communication including transmitting the first information.

11. The first node of claim 1, wherein ​ when the first bearer is the second type of bearer, the first set of operations does not include reestablishing an RLC entity associated with the first bearer.

12. The first node of claim 1, wherein, when the first bearer is the second type of bearer, the first set of operations does not include storing information for the first bearer failure in the first status variable.

13. The first node of claim 2, wherein, when the first bearer is the second type of bearer, the first set of operations does not include reestablishing an RLC entity associated with the first bearer.

14. The first node of claim 4, wherein, when the first bearer is the second type of bearer, the first set of operations does not include reestablishing an RLC entity associated with the first bearer.

15. The first node of claim 9, wherein, when the first bearer is the second type of bearer, the first set of operations does not include reestablishing an RLC entity associated with the first bearer.

16. The first node of claim 11, wherein, the first bearer is associated with a first cell group means that at least SRB1 between the first node and the first cell group is mapped to the first bearer; wherein the first bearer is the first type of bearer.

17. The first node of claim 13, wherein, the first bearer is associated with a first cell group means that at least SRB1 between the first node and the first cell group is mapped to the first bearer; wherein the first bearer is the first type of bearer.

18. The first node of claim 1, wherein, the first receiver detects the second bearer failure; wherein the second bearer is the first type of bearer, detecting the second bearer failure is used to trigger initiating RRC reestablishment; detecting the second bearer failure includes one of detecting radio link failure of the second bearer, detecting T310 expiry, or detecting the second bearer reaches RLC maximum retransmission number.

19. The first node of claim 18, wherein, the first information is generated at RRC.

20. A method in a first node used for wireless communication, wherein, including: detecting the first bearer failure, the first bearer is associated with a first cell group; performing a first set of operations in response to detecting the first bearer failure, the first set of operations is related to a type of the first bearer; sending first information on a second bearer in response to detecting the first bearer failure, the first information is used to indicate the first bearer failure, the second bearer is associated with the first cell group; sending a second message in response to all conditions in a first set of conditions are met; the second message indicates there is available information; wherein the first cell group is a master cell group; wherein the first set of conditions includes a first status variable stores the available information. wherein the first set of operations, in relation to the type of the first bearer, comprises at least one of re-establishing a RLC entity associated with the first bearer and storing in the first status variable information about failure of the first bearer, when the first bearer is a first type of bearer; and the first set of operations comprises releasing at least a RLC entity associated with the first bearer, when the first bearer is a second type of bearer; wherein the RLC entity associated with the first type of bearer is a RLC entity of a Uu interface; wherein the RLC entity associated with the second type of bearer is a RLC entity of a PC5 interface; wherein the first type of bearer uses a primary link; and the second type of bearer uses a secondary link; wherein the SRB1 (signaling radio bearer 1) of the first node is associated with both the first bearer and the second bearer.

21. The method in the first node according to claim 20, wherein the first bearer is the second type of bearer, and the second bearer is the first type of bearer.

22. The method in the first node according to claim 21, wherein the first node is configured with only one cell group.

23. The method in the first node according to claim 21, wherein the first set of operations comprises resetting a MAC (medium access control) associated with the first bearer, the first type of bearer is a RLC bearer, and the second type of bearer is a sidelink RLC bearer.

24. The method in the first node according to claim 20, wherein the first bearer is the first type of bearer; storing in the first status variable information about failure of the first bearer comprises storing a cause of the failure of the first bearer and whether the second type of bearer is used; and the cause of the failure of the first bearer belongs to a first set of candidate causes, the first set of candidate causes comprises radio link failure, cell handover failure, and path switch failure.

25. The method in the first node according to claim 20, wherein the first type of bearer is a SRB (signaling radio bearer), and the second type of bearer is a DRB (data radio bearer).

26. The method in the first node according to claim 20, further comprising: receiving a first signaling, the first signaling being used to configure a second bearer; detecting failure of the second bearer after having detected failure of the first bearer; initiating a RRC (radio resource control) re-establishment procedure in response to detecting failure of the second bearer, along with the RRC re-establishment procedure, suspending the SRB1, and performing any one of cell selection and relay selection; sending a third message, the third message being used to indicate the failure of the second bearer; wherein the first bearer is the first type of bearer; wherein the second bearer is the second type of bearer; wherein the first bearer is not resumed upon detecting the second bearer failure.

27. The method in a first node according to claim 20, further comprising: receiving first signaling, the first signaling being used for configuring a second bearer; detecting the second bearer failure after having detected the first bearer failure; initiating, as a response to detecting the second bearer failure, an RRC re-establishment procedure, with the RRC re-establishment procedure suspending SRB1, performing any of cell selection and relay selection; sending a third message, the third message being used for indicating the second bearer failure; wherein the first bearer is the second type of bearer; wherein the second bearer is the first type of bearer; wherein the first bearer is not resumed upon detecting the second bearer failure.

28. The method in a first node according to claim 20, further comprising: sending the first information as a response to detecting a first bearer failure, depending on whether the first bearer is the first type of bearer or the second type of bearer; wherein sending the first information depending on whether the first bearer is the first type of bearer or the second type of bearer means that when the first bearer is the first type of bearer, initiating a failure information transfer procedure, initiating the failure information transfer procedure comprising sending the first information, and when the first bearer is the second type of bearer, initiating a sidelink UE information transfer procedure for NR sidelink communication and sending the first information in the sidelink UE information transfer procedure for NR sidelink communication.

29. The method in a first node according to claim 21, further comprising: sending the first information as a response to detecting a first bearer failure, depending on whether the first bearer is the first type of bearer or the second type of bearer; wherein sending the first information depending on whether the first bearer is the first type of bearer or the second type of bearer means that when the first bearer is the first type of bearer, initiating a failure information transfer procedure, initiating the failure information transfer procedure comprising sending the first information, and when the first bearer is the second type of bearer, initiating a sidelink UE information transfer procedure for NR sidelink communication and sending the first information in the sidelink UE information transfer procedure for NR sidelink communication.

30. The method in a first node according to claim 20, wherein, when the first bearer is the second type of bearer, the first set of operations does not comprise re-establishing an RLC entity associated with the first bearer.

31. The method in a first node according to claim 20, wherein, when the first bearer is the second type of bearer, the first set of operations does not comprise storing information for the first bearer failure in the first state variable.

32. The method in a first node according to claim 21, wherein, when the first bearer is the second type of bearer, the first set of operations does not comprise re-establishing an RLC entity associated with the first bearer.

33. The method in a first node according to claim 23, wherein, when the first bearer is a second type of bearer, the first set of operations does not include reestablishing an RLC entity associated with the first bearer.

34. The method in a first node according to claim 28, wherein when the first bearer is a second type of bearer, the first set of operations does not include reestablishing an RLC entity associated with the first bearer.

35. The method in a first node according to claim 30, wherein the first bearer is associated with a first cell group implies that at least SRB1 between the first node and the first cell group has a mapping relationship with the first bearer; wherein the first bearer is the first type of bearer.

36. The method in a first node according to claim 32, wherein the first bearer is associated with a first cell group implies that at least SRB1 between the first node and the first cell group has a mapping relationship with the first bearer; wherein the first bearer is the first type of bearer.

37. The method in a first node according to claim 20, further comprising: detecting that the second bearer is failed; wherein the second bearer is the first type of bearer, detecting that the second bearer is failed is used to trigger initiating RRC reestablishment; detecting that the second bearer is failed comprises one of detecting that the second bearer has radio link failure, detecting that T310 expires or detecting that the second bearer reaches RLC maximum retransmission times.

38. The method in a first node according to claim 37, wherein the first information is generated at RRC.

Images