CN114339881A

CN114339881A - Method and device used in wireless communication

Info

Publication number: CN114339881A
Application number: CN202011063813.7A
Authority: CN
Inventors: 张晓博
Original assignee: Shanghai Langbo Communication Technology Co Ltd
Current assignee: Shanghai Langbo Communication Technology Co Ltd
Priority date: 2020-09-30
Filing date: 2020-09-30
Publication date: 2022-04-12
Anticipated expiration: 2040-09-30
Also published as: CN114339881B

Abstract

A method and apparatus used in wireless communications is disclosed. A first node receives a first set of data units over a first radio bearer; determining that the first connection failed; monitoring a third set of data units over an air interface, the third set of data units carrying a second message; sending a second set of data units over the air interface in response to the behavior determining that the first connection failed, the second set of data units carrying a first message; wherein the first message is used to trigger the second message; the first radio bearer comprises a first PDCP entity and a first RLC bearer; the transmission of the second message passes through a second PDCP entity and the first RLC bearer; the first message is used to trigger association of the first RLC bearer to the second PDCP entity; the second message includes RRC signaling. The method and the device can quickly recover the wireless connection, ensure the service continuity and obviously reduce the signaling overhead.

Description

Method and device used in wireless communication

Technical Field

The present application relates to methods and apparatus in wireless communication systems, and more particularly, to methods and apparatus for fast recovery of a wireless connection in wireless communication.

Background

Dual-Connectivity (DC) is an important technology introduced by 3GPP (3rd Generation Partner Project) Rel. Through the dual connectivity technology, one UE (User Equipment) may use radio resources provided by two different base stations, and when the cell edge is located, the dual connectivity may increase the transmission rate and improve the transmission robustness. A terminal supporting dual connectivity may connect two LTE (Long Term Evolution) base stations at the same time, or connect one LTE base station and one NR (New Radio, New air interface) base station, or connect two NR base stations, and communicate between the two base stations through a backhaul (backhaul) X2 or Xn interface. One main base station is arranged in two base stations supporting dual connection, and the main base station maintains RRC (Radio Resource Control) connection of UE; the other secondary base station may not configure the RRC function, or may configure a part of the RRC function.

Disclosure of Invention

In a dual connectivity scenario, if a connection failure occurs in a primary cell maintaining a wireless connection, and if the secondary cell is not configured with an RRC function, then research needs to be performed to quickly recover the wireless connection based on Layer 1/Layer 2(Layer 1/Layer 2) of the user plane of the secondary cell.

In view of the above problems, the present application discloses a solution for fast wireless connection recovery based on layer 2 in an auxiliary cell when a connection failure occurs in a primary cell, and a user plane of the auxiliary cell is used for connection to assist in transmitting a control plane message, so that the wireless connection can be fast recovered, and service continuity can be guaranteed. Without conflict, embodiments and features in embodiments in a first node of the present application may be applied to a second node and vice versa. The embodiments and features of the embodiments of the present application may be combined with each other arbitrarily without conflict. Further, although the present application was originally directed to the Uu air interface, the present application can also be used for the PC5 interface. Further, although the original purpose of the present application is to the terminal and base station scenario, the present application is also applicable to the V2X (Vehicle-to-electrical networking) scenario, the communication scenario between the terminal and the relay, and the communication scenario between the relay and the base station, and achieves similar technical effects in the terminal and base station scenario. Furthermore, adopting a unified solution for different scenarios (including but not limited to V2X scenario and terminal to base station communication scenario) also helps to reduce hardware complexity and cost. In particular, the terms (telematics), nouns, functions, variables in the present application may be explained (if not specifically stated) with reference to the definitions in the 3GPP specification protocols TS36 series, TS38 series, TS37 series.

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

receiving a first set of data units over a first radio bearer; determining that the first connection failed; monitoring a third set of data units over an air interface, the third set of data units carrying a second message;

sending a second set of data units over the air interface in response to the behavior determining that the first connection failed, the second set of data units carrying a first message;

wherein the first message is used to trigger the second message; the first radio bearer comprises a first PDCP entity and a first RLC bearer; the transmission of the second message passes through a second PDCP entity and the first RLC bearer; the first message is used to trigger association of the first RLC bearer to the second PDCP entity; the second message comprises RRC signaling, the first set of data units comprises at least one data unit, the second set of data units comprises at least one data unit, and the third set of data units comprises at least one data unit.

As an embodiment, the present application is applicable to a dual connectivity scenario.

As an embodiment, the problem to be solved by the present application is: and rapidly recovering the radio connection under the condition that the connection failure occurs in the primary cell and the RRC function is not configured in the secondary cell.

As an example, the solution of the present application comprises: and utilizing the user plane connection of the secondary cell to assist in transmitting the control plane message.

As an embodiment, the beneficial effects of the present application include: the wireless connection is quickly recovered, the service continuity is guaranteed, and meanwhile, the signaling overhead is obviously reduced.

According to one aspect of the application, comprising: the second set of data units indicates a first set of reference values, which is used to indicate the second message.

According to one aspect of the application, comprising: receiving at least one data unit over the first radio bearer after sending the first message and before the second message is received; wherein the transmission of the at least one data unit is carried over the first RLC.

According to one aspect of the application, comprising: in response to the act of determining that the first connection failed, starting a first timer; stopping the first timer when the second message is received; stopping monitoring the third set of data units when the first timer expires.

According to one aspect of the application, comprising: after receiving the second message, establishing a second connection according to the second message; wherein the second connection is used for transmitting control plane information.

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

receiving a first set of data units over a backhaul link; receiving a second set of data units over an air interface, the second set of data units carrying a first message;

sending the first set of data units over a first RLC bearer; sending a third set of data units over the air interface, the third set of data units carrying a second message;

wherein the first message is used to trigger the second message; the first RLC bearer belongs to a first radio bearer, and the first radio bearer comprises a first PDCP entity; the transmission of the second message passes through a second PDCP entity and the first RLC bearer; the first message is used to trigger association of the first RLC bearer to the second PDCP entity; the second message comprises RRC signaling; determining that a first connection failure is used to trigger the first message.

According to one aspect of the application, comprising: receiving the second message over the backhaul link.

According to one aspect of the application, comprising: transmitting the first message over the backhaul link.

According to one aspect of the application, comprising: sending at least one data unit over the first RLC bearer after the first message is received and before the second message is sent.

According to one aspect of the application, comprising: determining that a first connection failure is used to start a first timer; the first timer is stopped when the second message is received; the third set of data units is stopped from monitoring when the first timer expires.

According to one aspect of the application, comprising: after the second message is received, the second message is used to establish a second connection; wherein the second connection is used for transmitting control plane information.

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

transmitting a first set of data units over a backhaul link; sending a second message over the backhaul link;

receiving a first message over the backhaul link;

wherein the first set of data units is transmitted over a first radio bearer, the first radio bearer including a first PDCP entity and a first RLC bearer; the first message is used to trigger the second message; the transmission of the second message passes through a second PDCP entity and the first RLC bearer; the first message is used to trigger association of the first RLC bearer to the second PDCP entity; the second message comprises RRC signaling; determining that a first connection failure is used to trigger the first message.

According to one aspect of the application, comprising: a second set of data units indicates a first set of reference values, the first set of reference values being used to indicate the second message; wherein the second set of data units carries the first message.

According to one aspect of the application, comprising: after the first message is sent and before the second message is received, at least one data unit is received over the first radio bearer; wherein the transmission of the at least one data unit is carried over the first RLC.

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

a first receiver that receives a first set of data units over a first radio bearer; determining that the first connection failed; monitoring a third set of data units over an air interface, the third set of data units carrying a second message;

a first transmitter, responsive to the behavior determining that the first connection failed, to transmit a second set of data units over the air interface, the second set of data units carrying a first message;

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

a second receiver that receives the first set of data units over a backhaul link; receiving a second set of data units over an air interface, the second set of data units carrying a first message;

a second transmitter to transmit the first set of data units over a first RLC bearer; sending a third set of data units over the air interface, the third set of data units carrying a second message;

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

a third transmitter to transmit the first set of data units over a backhaul link; sending a second message over the backhaul link;

a third receiver that receives the first message over the backhaul link;

Drawings

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

fig. 1 illustrates a transmission flow diagram of a first node according to an embodiment of the present application;

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

fig. 3 illustrates a schematic diagram of radio protocol architecture of a user plane and a control plane according to an embodiment of the present application;

FIG. 4 illustrates a hardware module diagram of a communication device according to one embodiment of the present application;

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

FIG. 6 illustrates a flow diagram for maintaining a first timer according to one embodiment of the present application;

figure 7 illustrates a schematic diagram of the relationship between a first PDCP entity, a second PDCP entity and a first RLC entity and their corresponding peer entities according to one embodiment of the present application;

FIG. 8 illustrates a MAC subpDU diagram according to one embodiment of the present application;

FIG. 9 illustrates an RLC PDU format diagram according to one embodiment of the present application;

FIG. 10 illustrates a block diagram of a processing device in a first node according to one embodiment of the present application;

FIG. 11 illustrates a block diagram of a processing device in a second node according to one embodiment of the present application;

fig. 12 illustrates a block diagram of a processing device in a third node according to an embodiment of the present application.

Detailed Description

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

Example 1

Embodiment 1 illustrates a transmission flow diagram of a first node according to an embodiment of the present application, as shown in fig. 1.

In embodiment 1, a first node 100 receives a first set of data units over a first radio bearer in step 101; determining in step 102 that the first connection failed; in step 103, as a response to the behavior determining that the first connection fails, sending a second set of data units over the air interface, the second set of data units carrying the first message; monitoring a third set of data units over an air interface in step 104, the third set of data units carrying a second message; wherein the first message is used to trigger the second message; the first radio bearer comprises a first PDCP entity and a first RLC bearer; the transmission of the second message passes through a second PDCP entity and the first RLC bearer; the first message is used to trigger association of the first RLC bearer to the second PDCP entity; the second message comprises RRC signaling, the first set of data units comprises at least one data unit, the second set of data units comprises at least one data unit, and the third set of data units comprises at least one data unit.

As one embodiment, the first radio bearer is a bi-directional radio bearer.

As one embodiment, the first radio bearer is a uni-directional radio bearer.

As an embodiment, the first Radio Bearer belongs to a DRB (Data Radio Bearer).

As an embodiment, the first radio bearer is used for transmitting traffic to which the first set of data units belongs.

As an embodiment, the first radio bearer is used for transmitting a QoS (Quality of Service) flow to which the first set of data units belongs.

As an embodiment, the first set of data units comprises at least one data unit.

As an embodiment, each Data Unit in the first set of Data units includes an IP (Internet Protocol) SDU (Service Data Unit).

As an embodiment, each data unit in the first set of data units includes an Address Resolution Protocol (ARP) SDU.

As an embodiment, each data unit in the first set of data units comprises a Non-IP (Non-IP) SDU.

As an embodiment, each data unit in the first set of data units includes an RLC (Radio Link Control protocol) SDU.

As an embodiment, each of the first data units comprises one RLC SDU segment.

As an embodiment, each of the first Data units includes an RLC PDU (Protocol Data Unit).

As an embodiment, each Data unit in the first set of Data units includes a PDCP (Packet Data Convergence Protocol) PDU.

As an embodiment, each data unit in the first set of data units comprises one PDCP SDU.

As an embodiment, each data unit in the first set of data units includes a MAC (Medium Access Control) SDU.

As an embodiment, one MAC SDU included in each data unit in the first set of data units is identified by the same LCID (Logical Channel IDentity).

As an embodiment, each data unit in the first set of data units is transmitted over the same PDCP Entity (Entity) and RLC Entity.

As one embodiment, the first connection comprises an RRC connection.

For one embodiment, the first connection includes a radio link with a first cell.

For one embodiment, the first connection includes a beam link with a first cell.

As one embodiment, the act of determining that the first connection failed comprises: determining Radio Link Failure (RLF) with a first cell from channel measurements, the first PDCP entity and the second PDCP entity being maintained by the first cell.

As one embodiment, the act of determining that the first connection failed comprises: determining a radio link failure with a first cell from expiration of a maintained timer T310 (timer 310), the first PDCP entity and the second PDCP entity being maintained by the first cell.

As one embodiment, the act of determining that the first connection failed comprises: determining a radio link failure with a first cell from expiration of a maintained timer T312 (timer 312), the first PDCP entity and the second PDCP entity being maintained by the first cell.

As one embodiment, the act of determining that the first connection failed comprises: determining a radio link failure with a first cell from a random access procedure failure, the first PDCP entity and the second PDCP entity being maintained by the first cell.

As one embodiment, the act of determining that the first connection failed comprises: determining a radio link failure with a first cell according to the maximum number of retransmissions of the RLC, the first PDCP entity and the second PDCP entity being maintained by the first cell.

As one embodiment, the act of determining that the first connection failed comprises: determining a radio link failure with a first cell according to an LBT (Listen Before Talk) monitoring failure, the first PDCP entity and the second PDCP entity being maintained by the first cell.

As one embodiment, the act of determining that the first connection failed comprises: determining a Beam Link Failure (BLF) with a first cell from measurements of a set of downlink reference signal resources, the first PDCP entity and the second PDCP entity being maintained by the first cell.

As one embodiment, the act of determining that the first connection failed comprises: determining a radio link Failure with a first cell according to a Beam Failure Recovery Failure (Beam Failure Recovery Failure), the first PDCP entity and the second PDCP entity being maintained by the first cell.

As one embodiment, the maintaining of the phrase by the first cell comprises: maintained by a serving base station of the first cell.

As one embodiment, the maintaining of the phrase by the second cell comprises: maintained by a serving base station of the second cell.

As one embodiment, the first radio bearer includes a first PDCP entity and a first RLC bearer.

For one embodiment, the first RLC bearer is maintained by a second cell.

As an embodiment, the second cell is a serving cell other than the first cell.

As an embodiment, there is an overlap (overlapping) between the frequency domain resource of the first cell and the frequency domain resource of the second cell.

As an embodiment, there is no overlap between the frequency domain resources of the first cell and the frequency domain resources of the second cell.

As an embodiment, the first cell and the second cell belong to intra-frequency cells (intra-frequency cells).

As an embodiment, the first cell and the second cell belong to inter-frequency cells (inter-frequency cells).

As an example, a Backhaul (Backhaul) link between the first cell and the second cell is non-ideal (i.e., delay cannot be ignored).

For one embodiment, the first RLC bearer includes a first RLC entity.

For one embodiment, the first RLC entity is maintained by the second cell.

As an embodiment, the first PDCP entity is maintained by the first cell.

As an embodiment, the first PDCP entity is associated with the first RLC bearer.

As an embodiment, the configuration message configuring the first radio bearer includes a first radio bearer identification; the first radio bearer identification is used to identify the first radio bearer.

As one embodiment, the configuration message of the first radio bearer comprises a RRC setup message.

As one embodiment, the configuration message of the first radio bearer includes an RRCConnectionSetup message.

As one embodiment, the configuration message of the first radio bearer comprises a rrcreesume (RRC resume) message.

As an embodiment, the configuration message of the first radio bearer comprises a rrcreeconfiguration (RRC reconfiguration) message.

As one embodiment, the configuration message of the first radio bearer includes an RRCConnectionReconfiguration message.

As an embodiment, the configuration message of the first radio bearer includes a radio bearer configuration IE (Information Element).

As an embodiment, the configuration message of the first radio bearer includes a radioResourceConfigDedicated IE.

As an embodiment, the first radio bearer identity includes eps (Evolved Packet System) -bearer identity.

For one embodiment, the first radio bearer Identity comprises a drb-Identity.

As an embodiment, the configuration message of the first radio bearer includes configuration information of the first PDCP entity.

As an embodiment, the configuration message configuring the first radio bearer includes a configuration message of the first PDCP entity; the first radio bearer flag is used to identify the first PDCP entity.

As an embodiment, the configuration message of the first PDCP entity includes a pdcd-Config (PDCP configuration) IE.

As an embodiment, the configuration message configuring the first RLC bearer includes the first radio bearer identity; the first radio bearer identification is used to identify the first RLC bearer.

As one embodiment, the first radio bearer identification is used to associate the first PDCP entity and the first RLC bearer.

As an embodiment, the first RLC bearer includes the first RLC entity.

As an embodiment, the configuration message of the first RLC bearer includes a configuration message for the first RLC entity.

As an embodiment, the configuration message of the first RLC bearer includes a first logical channel identification.

As an embodiment, the first logical channel identity indicates the first RLC entity.

As an embodiment, in the transfer of data units from an RLC entity to a MAC entity, a first logical channel identification is used to indicate the transfer of RLC PDUs from the first RLC entity to the MAC entity.

As an embodiment, in the delivery of data units from the MAC entity to the RLC entity, a first logical channel identification is used to indicate that a MAC SDU is delivered to the first RLC entity.

As an embodiment, the MAC entity implements a MAC sublayer protocol stack function.

As an embodiment, the configuration message of the first RLC bearer includes a cell identity indicating the second cell.

As an embodiment, the cell identity of the second cell is used to indicate a cell maintaining the first RLC bearer.

As an embodiment, the cell identity includes a physical cell ID (physical cell identity).

As an embodiment, the cell identifier includes a cell index (cell index).

As an embodiment, the cell identifier includes a global cell ID (global cell identifier).

As one embodiment, the configuration message of the first RLC bearer includes a RRCSetup (RRC setup) message.

As an embodiment, the configuration message of the first RLC bearer includes an RRCConnectionSetup (RRC connection setup) message.

For one embodiment, the configuration message of the first RLC bearer includes a rrcreesume (RRC resume) message.

As an embodiment, the configuration message of the first RLC bearer includes a rrcreeconfiguration (RRC reconfiguration) message.

As an embodiment, the configuration message of the first RLC bearer includes an RRCConnectionReconfiguration message.

As an embodiment, the configuration message carried by the first RLC includes a masterCellGroup IE.

As an embodiment, the configuration message of the first RLC bearer includes a secondary cell group IE.

As an embodiment, the configuration message of the first RLC bearer includes a CellGroupConfig (cell group configuration) IE.

As an embodiment, the configuration message of the first RLC bearer includes an RLC-bearerConfig (RLC bearer configuration) IE.

As one embodiment, the configuration message of the first radio bearer includes the configuration message of the first RLC bearer.

As an embodiment, the first radio bearers, the first RLC bearers are respectively configured by the third nodes.

As one embodiment, the second set of data units is sent over an air interface in response to the act of determining that the first connection failed.

In one embodiment, the first message is encapsulated by the sender into a second set of data units and sent over the air interface.

As an embodiment, the second set of data units carrying the first message is received over an air interface by a recipient of the first message.

For one embodiment, the air interface comprises an interface for wireless signal transmission.

For one embodiment, the air interface comprises an interface for wireless signaling.

For one embodiment, the air interface includes Uu.

For one embodiment, the air interface includes a PC 5.

As an embodiment, the second set of data units comprises at least one data unit.

As an embodiment, each data unit in the second set of data units comprises a Transport Block (TB).

For one embodiment, each data unit in the second set of data units comprises one MAC PDU.

As an embodiment, the second set of data units includes only one data unit, and the data unit in the second set of data units includes a MAC CE (Control Element), where the MAC CE carries the first message.

As an embodiment, the MAC CE carrying the first message and the data unit belonging to the first radio bearer are multiplexed and transmitted in one MAC PDU.

As an embodiment, the second set of data units comprises one MAC SDU.

As an embodiment, each data unit of the second set of data units comprises one MAC SDU segment of the MAC SDU comprised in the second set of data units.

As an embodiment, the MAC CE included in the second set of data units carries the first message.

As an embodiment, the second set of data units carries the first message.

As an embodiment, the MAC SDU segment included in each data unit of the second set of data units constitutes the first message.

For one embodiment, the first message includes control information.

For one embodiment, the first message includes RRC signaling.

As an embodiment, the first message comprises a RRC setup request.

For one embodiment, the first message includes an rrcreestablishrequest (RRC reestablishment request).

For one embodiment, the first message includes RRCReestab-initiated (RRC reestablishment initiation).

For one embodiment, the first message includes a RRC setup initiated RRC setup.

As an embodiment, the first message includes a UE RLF Report Container IE.

As one embodiment, the first message includes a reason for the first connection failure.

As one embodiment, the cause of the first connection failure is carried in an estabilishment cause field.

As an embodiment, the reason for the first connection failure is carried in a reseabattercause field.

As one embodiment, the cause of the first connection failure comprises RLF.

As one embodiment, the reason for the first connection failure includes BLF.

As one embodiment, the reason for the first connection failure includes a reconfigurationFailure.

As an embodiment, the reason for the first connection failure includes handover failure.

As one embodiment, the reason for the first connection failure includes otherFailure.

As an embodiment, the first message includes a frequency of an SSB (Synchronization Signal Block) of the first cell.

As one embodiment, the first message includes the cell identity of the first cell.

As an embodiment, the first message includes the cell identity of the re-established cell; the rebuilt cell is a cell outside the first cell.

For one embodiment, the first message includes a first subscriber identity.

As an embodiment, the first user identity includes a first C-RNTI (Cell-Radio Network Temporary identity).

As an embodiment, the first user identity comprises a UE-identity.

As an embodiment, the first subscriber identity comprises a random value.

As an embodiment, the first subscriber identity uniquely identifies the first node in the first cell.

As an embodiment, the serving node of the first cell allocates the first subscriber identity to the first node.

As an embodiment, the second set of data units carries a first extension message.

As an embodiment, the first extension message is not transmitted over a backhaul link.

As an embodiment, the first message is used to trigger the first RLC entity to be re-established.

As one embodiment, the first message is used to trigger generation of the second message.

As one embodiment, the target recipient of the first message is the third node.

As an embodiment, the first message is forwarded to the third node via the second node.

As an embodiment, the second message is generated at the third node.

As an embodiment, the second message is forwarded to the first node via the second node.

As one embodiment, the behavior monitoring a third set of data units includes receiving the third set of data units.

As one embodiment, the behavior monitoring the third set of data units includes monitoring a first set of signaling, each signaling in the first set of signaling being physical layer signaling.

As an embodiment, each signaling in the first signaling set includes a Downlink Control Information (DCI) of a Downlink Grant (Downlink Grant).

As an embodiment, each signaling in the first signaling set is transmitted through a PDCCH (Physical Downlink Control CHannel).

As an embodiment, each signaling in the first set of signaling is identified by a second C-RNTI.

As an embodiment, the second C-RNTI is configured by the second cell.

As an embodiment, each signaling in the first signaling set includes scheduling information of a physical layer channel occupied by a corresponding data unit in the third data unit set.

As a sub-embodiment of the foregoing embodiment, a first signaling in the first signaling set corresponds to scheduling information of a physical layer channel occupied by a first data unit in the third data unit set; the second signaling in the first signaling set corresponds to the scheduling information of the physical layer channel occupied by the second data unit in the third data unit set; by analogy, the description is omitted.

As an embodiment, a Physical layer CHannel occupied by each data unit in the third set of data units is a PDSCH (Physical Downlink Shared CHannel).

As an embodiment, the scheduling information of the physical layer channel includes at least one of a time-frequency resource used by the physical layer channel, an MCS (Modulation and Coding Scheme), or an HARQ (Hybrid Automatic Repeat reQuest) process identifier.

As one embodiment, the behavior monitoring a first set of signaling includes performing energy detection for each signaling in the first set of signaling.

As one embodiment, the behavior monitoring the first set of signaling includes performing coherent detection of a signature sequence for each signaling in the first set of signaling.

As one embodiment, the behavior monitoring the first set of signaling includes performing a CRC (Cyclic Redundancy Check) Check for each signaling in the first set of signaling.

As one embodiment, the behavior monitoring the first set of signaling includes performing blind coding for each signaling in the first set of signaling.

As an embodiment, the behavior monitoring the third set of data units includes monitoring a first set of signaling, and performing decoding on a physical layer channel indicated by scheduling information of the physical layer channel included in each signaling in the first set of signaling to obtain one data unit in the third set of data units.

As an embodiment, the third set of data units comprises at least one data unit.

As an embodiment, each data unit in the third set of data units comprises a TB.

As an embodiment, each data unit of the third set of data units comprises one MAC PDU.

As an embodiment, each data unit in the third set of data units comprises one RLC PDU.

As an embodiment, the third set of data units comprises one MAC SDU.

As an embodiment, each data unit of the third set of data units comprises one MAC SDU segment of the MAC SDU comprised in the third set of data units.

As an embodiment, each data unit in the third set of data units comprises the MAC SDU fragment identified by the same LCID.

As an embodiment, the LCID of the segment of the MAC SDU included in the third set of data units included in each data unit of the third set of data units is the same as the LCID of the MAC SDU included in each data unit of the first set of data units.

As an embodiment, the third set of data units carries the second message.

As an embodiment, the MAC SDU segment included in each data unit of the third set of data units constitutes the second message.

In one embodiment, the second message is encapsulated by the sender into a third set of data units and sent over the air interface.

As an embodiment, a third set of data units carrying the second message is received over an air interface by a recipient of the second message.

As one embodiment, the second message is used to reconfigure the first radio bearer.

For one embodiment, the second message includes RRC signaling.

As an embodiment, the second message is used for Reconfiguration (Reconfiguration) of RRC connection.

As an embodiment, the second message is used for RRC connection Setup (Setup).

As an embodiment, the second message is used for RRC connection Reestablishment (Reestablishment).

As an embodiment, the second message comprises a rrcreeconfiguration (RRC reconfiguration) message.

For one embodiment, the second message comprises an RRCConnectionReconfiguration message.

For one embodiment, the second message comprises a RRCSetup message.

For one embodiment, the second message comprises RRCConnectionSetup.

For one embodiment, the second message comprises a rrcreestablistering message.

For one embodiment, the second message comprises an RRCConnectionReestablishment message.

As an embodiment, the second message includes a radioBearerConfig IE.

As an embodiment, the second message includes a radioResourceConfigDedicated IE.

As an embodiment, the second message comprises a masterCellGroup message.

As an embodiment, the second message comprises a secondary cell group message.

For one embodiment, the second message includes an RLC-bearerConfig (RLC bearer configuration) message.

As an embodiment, the second PDCP entity is maintained by the first cell.

As an embodiment, the transmission of the second message passes through the second PDCP entity and the first RLC entity.

As one embodiment, the first message is used to trigger association of the first RLC bearer to the second PDCP entity.

As an embodiment, the first message is used to trigger associating the first RLC bearer to the first PDCP entity and the second PDCP entity simultaneously.

In one embodiment, the first RLC bearer is identified by both the first radio bearer identification and the second radio bearer identification in response to receiving the first message.

As one embodiment, the second radio bearer identification is used to identify a second radio bearer.

As an embodiment, the second Radio Bearer is an SRB (signaling Radio Bearer).

For one embodiment, the second radio bearer Identity comprises srb-Identity.

For one embodiment, the srb-Identity included in the second rb Identity is 1.

For one embodiment, the second rb Identity includes srb-Identity of 2.

For one embodiment, the second rb Identity includes srb-Identity of 3.

As an embodiment, the second radio bearer includes the second PDCP entity.

As an embodiment, the second radio bearer identification is used to associate the second PDCP entity with the first RLC bearer.

Example 2

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

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

As an embodiment, the NR node B203 corresponds to a second node in the present application.

As an embodiment, the other NR node B corresponds to the third node in the present application.

As an example, the gNB203 is a macro Cell (Marco Cell) base station.

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

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

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

As an embodiment, the gNB203 is a base station device supporting a large delay difference.

As an example, the gNB203 is a flight platform device.

As an embodiment, the gNB203 is a satellite device.

As an example, the gNB204 is a macro Cell (Marco Cell) base station.

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

As an example, the gNB204 is a Pico Cell (Pico Cell) base station.

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

As an example, the gNB204 is a flight platform device.

As one embodiment, the gNB204 is a satellite device.

As an embodiment, the radio link from the UE201 to the gNB203 is an uplink, which is used to perform uplink transmissions.

As an embodiment, the radio link from the gNB203 to the UE201 is a downlink, which is used to perform downlink transmission.

As an embodiment, the radio link between the UE201 and the UE241 is a sidelink.

As an embodiment, the UE201 and the gNB203 are connected through a Uu interface.

As an embodiment, the UE201 and the gNB204 are connected through a Uu interface.

Example 3

Embodiment 3 illustrates a schematic diagram of radio protocol architecture of a user plane and a control plane according to an embodiment of the present application, as shown in fig. 3. Fig. 3 is a schematic diagram illustrating an embodiment of radio protocol architecture for the user plane 350 and the control plane 300, fig. 3 showing the radio protocol architecture of the control plane 300 for the UE and the gNB in three layers: layer 1, layer 2 and layer 3. Layer 1(L1 layer) is the lowest layer and implements various PHY (physical layer) signal processing functions. The L1 layer will be referred to herein as PHY 301. Layer 2(L2 layer) 305 is above PHY301, and is responsible for the link between the UE and the gNB through PHY 301. The L2 layer 305 includes a MAC (Medium Access Control) sublayer 302, an RLC (Radio Link Control) sublayer 303, and a PDCP (Packet Data Convergence Protocol) sublayer 304, which terminate at the gbb on the network side. The PDCP sublayer 304 provides data ciphering and integrity protection, and the PDCP sublayer 304 also provides handover support for UEs between the gnbs. The RLC sublayer 303 provides segmentation and reassembly of packets, retransmission of missing packets by ARQ, and the RLC sublayer 303 also provides duplicate packet detection and protocol error detection. The MAC sublayer 302 provides mapping between logical and transport channels and multiplexing of logical channel identities. The MAC sublayer 302 is also responsible for allocating various radio resources (e.g., resource blocks) in one cell among the UEs. The MAC sublayer 302 is also responsible for HARQ (Hybrid Automatic Repeat Request) 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 gNB and the UE. Although not shown, the UE may further have a V2X layer above the RRC sublayer 306 in the control plane 300, where the V2X layer is responsible for generating a PC5 QoS parameter set and a QoS rule according to received service data or a service request, and generates a PC5 QoS stream corresponding to the PC5 QoS parameter set and sends a PC5 QoS stream identifier and a corresponding PC5 QoS parameter set to an AS (Access Stratum) layer for QoS processing of packets belonging to the PC5 QoS stream identifier by the AS layer; the V2X layer also comprises a PC5-S Signaling Protocol (PC5-Signaling Protocol) sublayer, and the V2X layer is responsible for indicating whether each transmission of the AS layer is PC5-S transmission or V2X service data transmission. The radio protocol architecture of the user plane 350 includes layer 1(L1 layer) and layer 2(L2 layer), the radio protocol architecture in the user plane 350 is substantially the same 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 as the corresponding layers and sublayers in the control plane 300, but the PDCP sublayer 354 also provides header compression for upper layer packets to reduce radio transmission overhead. The L2 layer 355 in the user plane 350 further includes an SDAP (Service Data Adaptation Protocol) sublayer 356, and the SDAP sublayer 356 is responsible for mapping between QoS (Quality of Service) streams and Data Radio Bearers (DRBs) to support diversity of services. The radio protocol architecture of the UE in the user plane 350 may include part or all of the protocol sublayers of the SDAP sublayer 356, the PDCP sublayer 354, the RLC sublayer 353, and the MAC sublayer 352 at the L2 layer. Although not shown, the UE may also have several upper layers above the L2 layer 355, including a network layer (e.g., IP layer) that terminates at the P-GW on the network side and an application layer that terminates at the other end of the connection (e.g., far end UE, server, etc.).

As an example, the entities of the sub-layers of the control plane in fig. 3 constitute an SRB in the vertical direction.

As an example, the entities of the sub-layers of the control plane in fig. 3 constitute a DRB in the vertical direction.

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

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

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

As an example, the first set of data units in this application is generated in the SDAP 356.

As an embodiment, the first set of data units in the present application is generated in the PDCP 354.

As an example, the first set of data units in this application is generated at the RLC 353.

As an example, the first set of data units in this application is generated at the MAC 352.

As an example, the second set of data units in this application is generated at the MAC 352.

As an example, the third set of data units in this application is generated at the RLC 353.

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

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

As an example, the

L2 layer

305 or 355 belongs to a higher layer.

As an embodiment, the RRC sublayer 306 in the L3 layer belongs to a higher layer.

Example 4

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

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

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

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

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

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

In a transmission from the first communication device 450 to the second communication device 410, the functionality at the second communication device 410 is similar to the receiving functionality at the first communication device 450 described in the transmission from the second communication device 410 to the first communication device 450. Each receiver 418 receives an rf signal through its respective antenna 420, converts the received rf signal to a baseband signal, and provides the baseband signal to a multi-antenna receive processor 472 and a receive processor 470. The receive processor 470 and the multiple antenna receive processor 472 collectively implement the functionality of the L1 layer. Controller/processor 475 implements the L2 layer functions. The controller/processor 475 can be associated with a memory 476 that stores program codes and data. Memory 476 may be referred to as a computer-readable medium. In transmission from the first 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 packets from the first communication device 450. Upper layer packets from the controller/processor 475 may be provided to the core network or all protocol layers above the L2 layer and various control signals may also be provided to the core network or L3 for L3 processing.

As an embodiment, the first communication device 450 apparatus includes: at least one processor and at least one memory including computer program code; the at least one memory and the computer program code configured to, for use with the at least one processor, the first communication device 450 apparatus at least: receiving a first set of data units over a first radio bearer; determining that the first connection failed; monitoring a third set of data units over an air interface, the third set of data units carrying a second message; sending a second set of data units over the air interface in response to the behavior determining that the first connection failed, the second set of data units carrying a first message; wherein the first message is used to trigger the second message; the first radio bearer comprises a first PDCP entity and a first RLC bearer; the transmission of the second message passes through a second PDCP entity and the first RLC bearer; the first message is used to trigger association of the first RLC bearer to the second PDCP entity; the second message comprises RRC signaling, the first set of data units comprises at least one data unit, the second set of data units comprises at least one data unit, and the third set of data units comprises at least one data unit.

As an embodiment, the first communication device 450 apparatus includes: a memory storing a program of computer readable instructions that when executed by at least one processor result in actions comprising: receiving a first set of data units over a first radio bearer; determining that the first connection failed; monitoring a third set of data units over an air interface, the third set of data units carrying a second message; sending a second set of data units over the air interface in response to the behavior determining that the first connection failed, the second set of data units carrying a first message; wherein the first message is used to trigger the second message; the first radio bearer comprises a first PDCP entity and a first RLC bearer; the transmission of the second message passes through a second PDCP entity and the first RLC bearer; the first message is used to trigger association of the first RLC bearer to the second PDCP entity; the second message comprises RRC signaling, the first set of data units comprises at least one data unit, the second set of data units comprises at least one data unit, and the third set of data units comprises at least one data unit.

As an embodiment, the second communication device 410 apparatus includes: at least one processor and at least one memory including computer program code; the at least one memory and the computer program code are configured for use with the at least one processor. The second communication device 410 means at least: receiving a first set of data units over a backhaul link; receiving a second set of data units over an air interface, the second set of data units carrying a first message; sending the first set of data units over a first RLC bearer; sending a third set of data units over the air interface, the third set of data units carrying a second message; wherein the first message is used to trigger the second message; the first RLC bearer belongs to a first radio bearer, and the first radio bearer comprises a first PDCP entity; the transmission of the second message passes through a second PDCP entity and the first RLC bearer; the first message is used to trigger association of the first RLC bearer to the second PDCP entity; the second message comprises RRC signaling; determining that a first connection failure is used to trigger the first message.

As an embodiment, the second communication device 410 apparatus includes: a memory storing a program of computer readable instructions that when executed by at least one processor result in actions comprising: receiving a first set of data units over a backhaul link; receiving a second set of data units over an air interface, the second set of data units carrying a first message; sending the first set of data units over a first RLC bearer; sending a third set of data units over the air interface, the third set of data units carrying a second message; wherein the first message is used to trigger the second message; the first RLC bearer belongs to a first radio bearer, and the first radio bearer comprises a first PDCP entity; the transmission of the second message passes through a second PDCP entity and the first RLC bearer; the first message is used to trigger association of the first RLC bearer to the second PDCP entity; the second message comprises RRC signaling; determining that a first connection failure is used to trigger the first message.

As an embodiment, the second communication device 410 apparatus includes: at least one processor and at least one memory including computer program code; the at least one memory and the computer program code are configured for use with the at least one processor. The second communication device 410 means at least: transmitting a first set of data units over a backhaul link; sending a second message over the backhaul link; receiving a first message over the backhaul link; wherein the first set of data units is transmitted over a first radio bearer, the first radio bearer including a first PDCP entity and a first RLC bearer; the first message is used to trigger the second message; the transmission of the second message passes through a second PDCP entity and the first RLC bearer; the first message is used to trigger association of the first RLC bearer to the second PDCP entity; the second message comprises RRC signaling; determining that a first connection failure is used to trigger the first message.

As an embodiment, the second communication device 410 apparatus includes: a memory storing a program of computer readable instructions that when executed by at least one processor result in actions comprising: transmitting a first set of data units over a backhaul link; sending a second message over the backhaul link; receiving a first message over the backhaul link; wherein the first set of data units is transmitted over a first radio bearer, the first radio bearer including a first PDCP entity and a first RLC bearer; the first message is used to trigger the second message; the transmission of the second message passes through a second PDCP entity and the first RLC bearer; the first message is used to trigger association of the first RLC bearer to the second PDCP entity; the second message comprises RRC signaling; determining that a first connection failure is used to trigger the first message.

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

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

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

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

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

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

For one embodiment, the second communication device 410 is a base station device.

For one embodiment, the second communication device 410 is a relay node.

For one embodiment, at least one of the antenna 420, the transmitter 418, the multi-antenna transmit processor 471, the transmit processor 416 or the controller/processor 475 is configured to transmit the first set of data units.

For one embodiment, at least one of the antenna 452, the receiver 454, the multi-antenna receive processor 458, the receive processor 456, or the controller/processor 459 is configured to receive a first set of data units described herein.

For one embodiment, at least one of the antenna 452, the transmitter 454, the multi-antenna transmit processor 457, the transmit processor 468, or the controller/processor 459 is configured to transmit a second set of data units as described herein.

For one embodiment, at least one of the antenna 420, the receiver 418, the multi-antenna receive processor 472, the receive processor 470 or the controller/processor 475 is configured to receive a second set of data units.

For one embodiment, at least one of the antenna 420, the transmitter 418, the multi-antenna transmit processor 471, the transmit processor 416 or the controller/processor 475 is configured to transmit a third set of data units as described herein.

For one embodiment, at least one of the antenna 452, the receiver 454, the multi-antenna receive processor 458, the receive processor 456, or the controller/processor 459 is configured to receive a third set of data units described herein.

For one embodiment, at least one of the antenna 452, the transmitter 454, the multi-antenna transmit processor 457, the transmit processor 468, or the controller/processor 459 is configured to transmit a first message as described herein.

For one embodiment, at least one of the antenna 420, the receiver 418, the multi-antenna receive processor 472, the receive processor 470 or the controller/processor 475 is configured to receive a first message in the present application.

For one embodiment, at least one of the antenna 420, the transmitter 418, the multi-antenna transmit processor 471, the transmit processor 416 or the controller/processor 475 is configured to send the second message.

For one embodiment, at least one of the antenna 452, the receiver 454, the multi-antenna receive processor 458, the receive processor 456, or the controller/processor 459 is configured to receive a second message as described herein.

For one embodiment, at least one of the antenna 452, the receiver 454, the multi-antenna receive processor 458, the receive processor 456, or the controller/processor 459 is configured to determine a first connection failure.

Example 5

Embodiment 5 illustrates a wireless signal transmission flow chart according to an embodiment of the present application, as shown in fig. 5. In fig. 5, a first node U1 and a second node N2 communicate over a wireless interface, and the second node N2 and a third node N3 communicate over a backhaul link. It is specifically noted that the order in this example does not limit the order of signal transmission and the order of implementation in this application. The steps in dashed boxes F0 and F1 are optional.

For theFirst node U1Receiving a first set of data units over a first radio bearer in step S11; determining that the first connection failed in step S12; in response to determining in step S13 that the first connection failed as a result of the action, sending a second set of data units over the air interface, the second set of data units carrying the first message; receiving at least one data unit over a first radio bearer in step S14; monitoring a third set of data units over the air interface in step S15, the third set of data units carrying a second message; a second connection is established according to the second message in step S16.

For theSecond node N2Receiving a first set of data units over the backhaul link in step S21; transmitting a first set of data units over a first RLC bearer in step S22; receiving a second set of data units over the air interface in step S23Combining, the second data unit set carries a first message; sending the first message over a backhaul link in step S24; transmitting at least one data unit over the first RLC bearer in step S25; receiving a second message over the backhaul link in step S26; a third set of data units is sent over the air interface in step S27, the third set of data units carrying the second message.

For theThird node N3Sending a first set of data units over the backhaul link in step S31; receiving a first message over the backhaul link in step S32; the second message is sent over the backhaul link in step S33.

As an embodiment, the second node is a serving base station of the second cell.

As an embodiment, the third node is a serving base station of the first cell.

As an embodiment, the backhaul link is a link connecting base stations.

For one embodiment, the backhaul link includes an Xn interface.

For one embodiment, the backhaul link includes an X2 interface.

For one embodiment, the backhaul link connects the second node and the third node.

For one embodiment, the backhaul link comprises a link that transmits wireless signals.

For one embodiment, the backhaul link comprises a link that transmits wireless signaling.

For one embodiment, the backhaul link includes a link that transmits wired signals.

For one embodiment, the backhaul link includes a link that carries wired signaling.

As an embodiment, the backhaul link includes one-hop (one-hop).

For one embodiment, the backhaul link includes multi-hop (multiple-hops).

For one embodiment, the backhaul link includes a Radio Network Control Plane (Radio Network Control Plane) and a User Plane (User Plane).

As an embodiment, the third node sends the first set of data units to the second node over the user plane of the backhaul link.

As an embodiment, the first set of data units is sent at the third node via the first PDCP entity.

As an embodiment, the first set of data units is sent over the first RLC bearer at the second node.

As an embodiment, the first set of data units is sent at the second node over the first RLC entity.

As an embodiment, the first set of data units is received at the first node over the first radio bearer, the first radio bearer including a peer PDCP entity of the first PDCP entity maintained by the third node at the first node and a peer RLC entity of the first RLC entity maintained by the second node at the first node.

As one embodiment, the first extension message comprised by the second set of data units indicates the first set of reference values.

As an embodiment, the first set of reference values comprises at least one reference value.

As an embodiment, the reference value is an RLC sequence number.

As one embodiment, the second set of data units indicates a first RLC sequence number, and the RLC PDU including the second message includes the first RLC sequence number.

As one embodiment, the second set of data units indicates a first set of RLC sequence numbers, the first set of RLC sequence numbers including at least 1 RLC sequence number.

As an embodiment, the RLC PDU including the second message comprises an RLC sequence number belonging to the first set of RLC sequence numbers.

As an embodiment, the RLC sequence numbers in the first set of RLC sequence numbers are consecutive.

As an embodiment, the RLC sequence numbers in the first set of RLC sequence numbers are cyclically consecutive (Cyclic Continuous).

As one embodiment, the second set of data units indicates one RLC sequence number of the first set of RLC sequence numbers and a number of RLC sequence numbers of the first set of RLC sequence numbers.

As an embodiment, the second set of data units indicates one RLC sequence number of the first set of RLC sequence numbers, and the number of RLC sequence numbers of the first set of RLC sequence numbers is predefined or fixed.

As an embodiment, one RLC sequence number in the first set of RLC sequence numbers is an RLC sequence number maintained by a second RLC entity before sending a first data unit in the second set of data units plus a value modulo a maximum value of a sequence number of the second RLC entity by a first offset; wherein the RLC sequence number maintained by the second RLC entity before the first one of the second set of data units is sent is denoted as SN _0, the first offset is denoted as SN _ offset, and the maximum value of the sequence number of the second RLC entity is denoted as SN _ max.

For one embodiment, the second RLC entity is an RLC entity maintained by the first node that is peer to peer with the first RLC entity maintained by the second node.

As an embodiment, one RLC sequence number in the first set of RLC sequence numbers is a value of (SN _0+ SN _ offset) mod (SN _ max).

For one embodiment, the first offset is 1/2 of a maximum value of the sequence number of the second RLC entity.

As one embodiment, the first offset is

The above-mentioned

Is a ceiling operation.

As a practical matterIn one embodiment, the first offset is

The above-mentioned

Is a rounding down operation.

As an embodiment, when the sequence number of the second RLC entity includes 6 bits, the maximum RLC sequence number of the second RLC entity is 2⁶。

As an embodiment, when the sequence number of the second RLC entity includes 12 bits, the maximum RLC sequence number of the second RLC entity is 2¹²。

As an embodiment, when the sequence number of the second RLC entity includes 18 bits, the maximum value of the RLC sequence number of the second RLC entity is 2¹⁸。

As an embodiment, the reference value is a type of RLC control PDU.

For one embodiment, the second set of data units indicates a first RLC control PDU type.

As an embodiment, the value of the first RLC control PDU type is one of 001 to 111.

As an embodiment, the first RLC control PDU type is included in the RLC PDU including the second message.

As one embodiment, the first set of reference values is not transmitted over a backhaul link.

As one embodiment, the first set of reference values is used to indicate that the second message is delivered from the second RLC entity of the first node to a third PDCP entity of the first node.

As an embodiment, the third PDCP entity is a PDCP entity maintained by the first node that is peer to the second PDCP entity maintained by the third node.

As one embodiment, the second node obtains the first message and sends the first message to the third node over the backhaul link.

As one embodiment, the first message is sent by the second node to the third node over the wireless network control plane in the backhaul link.

As an embodiment, the first message is sent by the second node to the third node via a FAILURE INDICATION (FAILURE INDICATION) flow.

As an embodiment, the second node determines the third node by the second C-RNTI of the sender of the second set of data units.

For one embodiment, the third node receives the first message over the backhaul link.

As an embodiment, the third node generates the second message from the first message.

As an embodiment, the second message is generated at a first RRC entity, the first RRC entity being maintained by the third node.

As an embodiment, the third node sends the second message to the second node through the wireless network control plane of the backhaul link.

As an embodiment, the third node sends an RRC Transfer message over the backhaul link, the RRC Transfer message carried by the RRC Transfer being forwarded to the first node, the RRC Transfer message including the second message.

As an embodiment, the name of the IE encapsulating the second message comprises a DRB.

As an embodiment, the name of the IE encapsulating the second message comprises RRCReconfig.

As an embodiment, the name of the IE encapsulating the second message comprises recovery.

As an embodiment, the name of the IE encapsulating the second message comprises Fast rrcreeconfig via DRB from MN to SN (Fast RRC reconfiguration over data radio bearer from primary to secondary network).

As one embodiment, the Container encapsulating the second message includes an RRC Container IE.

As an embodiment, the second message is transmitted at the third node through the second PDCP entity.

As an embodiment, the second message is used at the second node to generate the third set of data units, and the second node sends the third set of data units through the first RLC bearer, where the third set of data units carries the second message.

As an embodiment, the at least one data unit buffered at the first RLC entity is sent to the first node over the first RLC bearer after sending the first message and before the second message is received.

As one embodiment, the at least one set of data units is transmitted over the first radio bearer after the first message is sent and before the second message is received.

As a sub-embodiment of the above embodiment, the behavior comprises downlink transmission via the first radio bearer transmission.

As a sub-embodiment of the above embodiment, the behavior comprises uplink transmission via the first radio bearer transmission.

As one embodiment, the uplink transmission over the first radio bearer is suspended (suspend) after the first message is sent and before the second message is received.

As an embodiment, after receiving the second message, a second connection is established according to the second message.

As one embodiment, the second connection comprises an RRC connection.

As one embodiment, the second connection includes a radio link with the first cell.

As one embodiment, the second connection includes a radio link with the second cell.

As an embodiment, the second connection comprises a radio link with a third cell, the third cell being one cell other than the first cell and the second cell.

As an embodiment, the second connection is used for transmitting control signaling.

As an embodiment, the second connection is used for transmitting RRC signaling.

As an embodiment, the second connection is used for transmitting measurement information.

As an embodiment, the first PDCP entity and the second PDCP entity implement PDCP sublayer protocol stack functions, respectively.

As an embodiment, the first RLC entity and the second RLC entity respectively implement RLC sublayer protocol stack functions.

Example 6

Embodiment 6 illustrates a flow chart for maintaining the first timer according to an embodiment of the present application, as shown in fig. 6. The steps of fig. 6 are performed at the first node.

Determining whether the first connection fails in step S601, if so, performing step S602, and if not, ending; starting a first timer in step S602; monitoring the third set of data units at a next candidate slot in step S603 and updating the first timer; determining whether a second message is received in step S604, if yes, performing step S605, and if no, performing step S606; stopping the first timer in step S605; judging whether the first timer is expired in step S606, if so, executing step S607, otherwise, jumping back to step S603; monitoring of the third set of data units is stopped in step S607.

As an embodiment, the second RLC entity is re-established in response to the act of determining that the first connection failed.

For one embodiment, the first receiver maintains the first timer.

As an embodiment, the first receiver starts a first timer at a start time of a time slot in which a first data unit of the second set of data units is located.

As an embodiment, the first receiver starts a first timer at the end of the time slot in which the first data unit of the second set of data units is located.

As one embodiment, the starting the first timer is setting a value of the first timer to 0; the updating the first timer is incrementing the value of the first timer by 1; the first timer expires if the value of the first timer equals a first expiration value, otherwise the first timer does not expire.

As one embodiment, said starting said first timer is setting a value of said first timer to a first expiration value; the updating the first timer is subtracting 1 from a value of the first timer; if the value of the first timer is equal to 0, the first timer expires, otherwise the first timer does not expire.

For one embodiment, the first expiration value is configurable.

As an embodiment, the first outdated value is a positive integer greater than 1.

As one embodiment, the first expiration value is a fixed value.

As one embodiment, the act of maintaining the first timer includes updating the first timer every one time slot.

As an example, the one slot is 1 millisecond.

As an embodiment, the one slot includes 14 OFDM (Orthogonal Frequency Division Multiplexing) symbols.

As an embodiment, the one slot includes 12 OFDM symbols.

For one embodiment, the first receiver stops the first timer when the first timer expires.

As an embodiment, the first receiver stops the first timer when the second message is received.

As an example, the next candidate time slot is the nearest time slot to come.

As an example, the next candidate slot is the upcoming latest slot reserved for Uu.

As an example, the next candidate slot is the upcoming latest slot reserved for the PC 5.

As an embodiment, in the step S601 (i.e. when the first node does not determine that the first connection fails), a stop state of a first timer is maintained; in said step S602 (i.e. when said first node determines that said first connection fails), said first timer is started.

As an embodiment, in said step S601 (i.e. when said first node does not determine that said first connection fails), a count of a first timer is maintained (i.e. said first timer is running); in said step S602 (i.e. when said first node determines that said first connection fails), said first timer is restarted.

As one embodiment, the behaviorally ceasing to monitor the third set of data units comprises: a cell reselection is performed.

As one embodiment, the behaviorally ceasing to monitor the third set of data units comprises: releasing the first radio bearer.

As one embodiment, the behaviorally ceasing to monitor the third set of data units comprises: releasing the second radio bearer.

As an embodiment, the second set of data units indicates a first set of RLC sequence numbers, the first set of RLC sequence numbers including at least 1 RLC sequence number; when the first timer runs, if the RLC sequence number included in the received RLC PDU belongs to the first RLC sequence number set, the received RLC PDU is judged to carry at least part of information in the second message.

As an embodiment, the determining, by the action, that the received RLC PDU carries at least part of information in the second message includes: and transferring the RLC SDU included in the received RLC PDU to a PDCP entity which is maintained by the first node and is in peer with the second PDCP entity.

As an embodiment, the first PDCP entity and the second PDCP entity are maintained at a base station side.

As an embodiment, when the first timer is running, if the RLC sequence number included in the received RLC PDU does not belong to the first RLC sequence number set, it is determined that the received RLC PDU does not carry the second message.

As an embodiment, when the first timer is running, if the RLC sequence number included in the received RLC PDU does not belong to the first RLC sequence number set, the RLC SDU included in the received RLC PDU is delivered to a PDCP entity that is maintained by the first node and that is peer to the first PDCP entity.

As an embodiment, when the first timer is stopped or expires, if the RLC sequence number included in the received RLC PDU belongs to the first RLC sequence number set, it is determined that the received RLC PDU does not carry the second message.

As an embodiment, when the first timer is stopped or expires, if the RLC sequence number included in the received RLC PDU belongs to the first RLC sequence number set, it is determined that the received RLC PDU belongs to the user plane.

As an embodiment, when the first timer is stopped or expires, if the RLC sequence number included in the received RLC PDU belongs to the first RLC sequence number set, the received RLC PDU is discarded.

As an embodiment, the second message is delivered to a second RRC entity for processing after being processed by a PDCP entity maintained by the first node, which is peer to the second PDCP entity, the second RRC entity being maintained by the first node.

As an embodiment, the second RRC entity maintained by the first node is a peer RRC entity of the first RRC entity maintained by the third node.

As an embodiment, the first RRC entity and the second RRC entity respectively implement RRC sublayer protocol stack functions.

Example 7

Embodiment 7 illustrates a relationship diagram between a first PDCP entity, a second PDCP entity, a first RLC entity and their corresponding peer entities according to an embodiment of the present application, as shown in fig. 7.

For one embodiment, the third node maintains the first PDCP entity and the second PDCP entity.

As an embodiment, the second node maintains the first RLC entity, the first RLC entity belonging to the first RLC bearer.

For one embodiment, the first node maintains a fourth PDCP entity that is a peer PDCP entity of the first PDCP entity maintained by the third node at the first node.

As an embodiment, the first node maintains the third PDCP entity, which is a peer PDCP entity of the second PDCP entity maintained by the third node at the first node.

As an embodiment, the first node maintains the second RLC entity, which is a peer RLC entity of the first RLC entity maintained by the second node at the first node.

As one embodiment, the first radio bearer includes the fourth PDCP entity and the second RLC entity at the first node.

As one embodiment, the second radio bearer includes the third PDCP entity at the first node.

As one embodiment, in response to the act sending the second set of data units over the air interface, simultaneously associating the first node-maintained RLC entity that is peer to the first RLC entity to the first node-maintained PDCP entity that is peer to the first PDCP entity and the first node-maintained PDCP entity that is peer to the second PDCP entity.

Example 8

Embodiment 8 illustrates a MAC sub pdu diagram according to an embodiment of the present application, as shown in fig. 8.

As an embodiment, one MAC sub PDU (sub PDU) includes one MAC sub header (sub header) and one MAC CE.

As an embodiment, one MAC sub pdu includes one MAC subheader and one MAC SDU.

As an embodiment, one MAC PDU includes at least one MAC sub PDU.

As an embodiment, the MAC CE included in the second set of data units includes the first message and the first extension message.

As an embodiment, the MAC subheader of the MAC CE included in the second set of data units includes an LCID of 35.

As an embodiment, the MAC subheader of the MAC CE included in the second set of data units includes an LCID of 36.

As an embodiment, the MAC subheader of the MAC CE included in the second set of data units includes an LCID of 37.

As an embodiment, the MAC subheader of the MAC CE included in the second set of data units includes an LCID of 38.

As an embodiment, the MAC subheader of the MAC CE included in the second set of data units includes an LCID of 39.

As an embodiment, if the LCID included in the MAC subheader of the received MAC CE is 35, it is determined that the received MAC CE carries the first message.

As an embodiment, if the LCID included in the MAC subheader of the received MAC CE is 36, it is determined that the received MAC CE carries the first message.

As an embodiment, if the LCID included in the MAC subheader of the received MAC CE is 37, it is determined that the received MAC CE carries the first message.

As an embodiment, if the LCID included in the MAC subheader of the received MAC CE is 38, it is determined that the received MAC CE carries the first message.

As an embodiment, if an LCID included in a MAC subheader of a received MAC CE is 39, it is determined that the received MAC CE carries the first message.

As an embodiment, the one MAC SDU included in the second set of data units includes the first message and the first extension message.

As an embodiment, each data unit in the second set of data units comprises a MAC SDU segment that constitutes the first message and the first extension message.

As an embodiment, a 1-bit reserved bit R in a MAC subheader of the one MAC SDU included in the second set of data units is used to indicate the first message.

As an embodiment, a 1-bit reserved bit R in a MAC subheader of a MAC SDU fragment comprised by each data unit of the second set of data units is used to indicate the first message.

As an embodiment, that the 1-bit reserved bit R in the MAC subheader of the one MAC SDU is 0 indicates that the MAC SDU belongs to the first radio bearer; the 1-bit reserved bit R in the MAC subheader of the one MAC SDU is 1, indicating that the MAC SDU belongs to the first message.

As an embodiment, that the 1-bit reserved bit R in the MAC subheader of the one MAC SDU is 0 indicates that the MAC SDU belongs to the first message; the 1-bit reserved bit R in the MAC subheader of the one MAC SDU is 1, indicating that the MAC SDU belongs to the first radio bearer.

As an embodiment, if a reserved bit included in a MAC subheader of a received MAC SDU is 1, it is determined that the received MAC SDU carries the first message.

As an embodiment, if a reserved bit included in a MAC subheader of a received MAC SDU is 0, it is determined that the received MAC SDU carries the first message.

As an embodiment, if a reserved bit included in a MAC subheader of a received MAC SDU segment is 1, it is determined that the received MAC SDU segment carries at least part of information of the first message.

As an embodiment, if a reserved bit included in a MAC subheader of a received MAC SDU segment is 0, it is determined that the received MAC SDU segment carries at least part of information of the first message.

As an embodiment, when the MAC subheader of the received MAC SDU indicates that the MAC SDU belongs to the first message, the MAC SDU is not delivered to the first RLC entity.

As an embodiment, the LCID of the MAC SDU comprised by the second set of data units is not used for delivering the MAC SDU to the first RLC entity.

As an embodiment, the LCID of the MAC SDU segment included in each data unit of the second set of data units is not used to deliver the MAC SDU segment to the first RLC entity.

In case a of embodiment 8, the MAC subheader includes 1 byte, and 2 reserved bits R field each occupy 1 bit, where the most significant reserved bit R is used to indicate that the MAC sub pdu belongs to the first radio bearer or the first message; LCID field takes 6 bits; the most significant reserved bit is the leftmost bit in case a of embodiment 8.

In case a of embodiment 8, the MAC subheader includes 1 byte, and 2 reserved bits R field each occupy 1 bit, where the second highest reserved bit R is used to indicate that the MAC sub pdu belongs to the first radio bearer or the first message; LCID field takes 6 bits; (ii) a The second high order reserved bit is the second bit from the leftmost in case a of embodiment 8.

In case B of embodiment 8, the MAC subheader includes 2 bytes, where 1 reserved bit R field occupies 1 bit, the F field indicates the length of the L field, the F field is 0 indicates that the L field includes 8 bits, and the F field is 1 indicates that the L field includes 16 bits; LCID field takes 6 bits; the L field indicates the length of the MAC SDU or MAC CE indicated by the MAC subheader, i.e., the number of bytes included in the MAC SDU or MAC CE.

Example 9

Embodiment 9 illustrates a schematic RLC PDU format according to an embodiment of the present application, as shown in fig. 9.

As an embodiment, the second message is carried in a user plane RLC PDU, and the second message is indicated by a Sequence Number (SN); the RLC sequence number is indicated by the second set of data units.

As an embodiment, the second message is carried in a Control plane RLC PDU, where the second message is indicated by a Control PDU Type (CPT); the control PDU type is indicated by the second set of data units.

As an embodiment, the second message or at least part of the information of the second message is carried in an RLC PDU format defined in a protocol of 3GPP standard 38.322.

In case a of embodiment 9, one user plane RLC PDU includes the second message, where a D/C (Data/Control) field indicates that the RLC PDU carries Data; the P (Polling) domain is not resolved; an SI (Segmentation Info) field indicates whether the RLC PDU includes a complete RLC SDU or an RLC SDU segment; the SN field indicates the sequence number of the RLC SDU included in the RLC PDU; wherein the P field indicates whether the transmitting node requests a peer RLC entity of the RLC entity to transmit a STATUS report (STATUS).

In case B of embodiment 9, one user plane RLC PDU includes partial information of the second message, wherein the D/C field, the P field, the SI field, and the SN field are parsed as in case a of embodiment 9, and a newly added SO (Segmentation Offset) indicates a byte Offset of an RLC SDU segment included in the RLC PDU in one RLC SDU.

In case C of embodiment 9, one control plane RLC PDU includes the second message, where the D/C domain indicates that the RLC PDU carries a control message, and the CPT indicates a type of the control message; the R field is a reserved bit.

Example 10

Embodiment 10 illustrates a block diagram of a processing apparatus in a first node according to an embodiment of the present application, as shown in fig. 10. In fig. 10, a first node processing apparatus 1000 includes a first receiver 1001 and a first transmitter 1002. The first receiver 1001 includes at least one of the transmitter/receiver 454 (including the antenna 452), the receive processor 456, the multiple antenna receive processor 458, or the controller/processor 459 of fig. 4 herein; the first transmitter 1002 may include at least one of the transmitter/receiver 454 (including the antenna 452), the transmit processor 468, the multi-antenna transmit processor 457, or the controller/processor 459 of fig. 4.

In embodiment 10, a first receiver 1001 receives a first set of data units over a first radio bearer; determining that the first connection failed; monitoring a third set of data units over an air interface, the third set of data units carrying a second message; a first transmitter 1002, configured to send, as a response to the behavior determining that the first connection fails, a second set of data units over the air interface, where the second set of data units carries the first message; wherein the first message is used to trigger the second message; the first radio bearer comprises a first PDCP entity and a first RLC bearer; the transmission of the second message passes through a second PDCP entity and the first RLC bearer; the first message is used to trigger association of the first RLC bearer to the second PDCP entity; the second message comprises RRC signaling, the first set of data units comprises at least one data unit, the second set of data units comprises at least one data unit, and the third set of data units comprises at least one data unit.

As one embodiment, the second set of data units indicates a first set of reference values, which is used to indicate the second message.

As an embodiment, the first receiver 1001, after sending the first message and before the second message is received, receives at least one data unit over the first radio bearer; wherein the transmission of the at least one data unit is carried over the first RLC.

As an example, the first receiver 1001, in response to the act of determining that the first connection failed, starts a first timer; stopping the first timer when the second message is received; stopping monitoring the third set of data units when the first timer expires.

As an embodiment, the first receiver 1001, after receiving the second message, establishes a second connection according to the second message; wherein the second connection is used for transmitting control plane information.

Example 11

Embodiment 11 is a block diagram illustrating a processing apparatus in a second node according to an embodiment of the present application, as shown in fig. 11. In fig. 11, a second node processing apparatus 1100 includes a second receiver 1101 and a second transmitter 1102. The second receiver 1101 includes at least one of the transmitter/receiver 418 (including the antenna 420), the receive processor 470, the multiple antenna receive processor 472, or the controller/processor 475 of fig. 4 of the present application; the second transmitter 1102 includes at least one of the transmitter/receiver 418 (including the antenna 420), the transmit processor 416, the multi-antenna transmit processor 471 or the controller/processor 475 of fig. 4 of the present application.

In embodiment 11, the second receiver 1101, receives the first set of data units over the backhaul link; receiving a second set of data units over an air interface, the second set of data units carrying a first message; a second transmitter 1102 that transmits the first set of data units over a first RLC bearer; sending a third set of data units over the air interface, the third set of data units carrying a second message; wherein the first message is used to trigger the second message; the first RLC bearer belongs to a first radio bearer, and the first radio bearer comprises a first PDCP entity; the transmission of the second message passes through a second PDCP entity and the first RLC bearer; the first message is used to trigger association of the first RLC bearer to the second PDCP entity; the second message comprises RRC signaling; determining that a first connection failure is used to trigger the first message.

For one embodiment, the second receiver 1101 receives the second message over the backhaul link.

For one embodiment, the second transmitter 1102 transmits the first message over the backhaul link.

As an embodiment, the second transmitter 1102 sends at least one data unit over the first RLC bearer after the first message is received and before sending the second message.

As one embodiment, determining that the first connection failure is used to start a first timer; the first timer is stopped when the second message is received; the third set of data units is stopped from monitoring when the first timer expires.

As an embodiment, after the second message is received, the second message is used to establish a second connection; wherein the second connection is used for transmitting control plane information.

Example 12

Embodiment 12 is a block diagram illustrating a processing apparatus in a third node according to an embodiment of the present application, as shown in fig. 12. In fig. 12, the third node processing apparatus 1200 includes a third receiver 1201 and a third transmitter 1202. Third receiver 1201 includes at least one of transmitter/receiver 418 (including antenna 420), receive processor 470, multi-antenna receive processor 472, or controller/processor 475 of fig. 4 herein; the third transmitter 1202 includes at least one of the transmitter/receiver 418 (including the antenna 420), the transmit processor 416, the multi-antenna transmit processor 471 or the controller/processor 475 of fig. 4 of the present application.

In embodiment 12, the third transmitter 1202 transmits the first set of data units over the backhaul link; sending a second message over the backhaul link; a third receiver 1201 receiving a first message over the backhaul link; wherein the first set of data units is transmitted over a first radio bearer, the first radio bearer including a first PDCP entity and a first RLC bearer; the first message is used to trigger the second message; the transmission of the second message passes through a second PDCP entity and the first RLC bearer; the first message is used to trigger association of the first RLC bearer to the second PDCP entity; the second message comprises RRC signaling; determining that a first connection failure is used to trigger the first message.

As one embodiment, the second set of data units indicates a first set of reference values, the first set of reference values being used to indicate the second message; wherein the second set of data units carries the first message.

As an embodiment, at least one data unit is received over the first radio bearer after the first message is sent and before the second message is received; wherein the transmission of the at least one data unit is carried over the first RLC.

It will be understood by those skilled in the art that all or part of the steps of the above methods may be implemented by instructing relevant hardware through a program, and the program may be stored in a computer readable storage medium, such as a read-only memory, a hard disk or an optical disk. Alternatively, all or part of the steps of the above embodiments may be implemented by using one or more integrated circuits. Accordingly, the module units in the above embodiments may be implemented in a hardware form, or may be implemented in a form of software functional modules, and the present application is not limited to any specific form of combination of software and hardware. The first Type of Communication node or UE or terminal in the present application includes, but is not limited to, a mobile phone, a tablet computer, a notebook, a network card, a low power consumption device, an eMTC (enhanced Machine Type Communication) device, an NB-IoT device, a vehicle-mounted Communication device, an aircraft, an airplane, an unmanned aerial vehicle, a remote control plane, and other wireless Communication devices. The second type of communication node, base station or network side device in this application includes, but is not limited to, a macro cell base station, a micro cell base station, a home base station, a relay base station, an eNB, a gNB, a Transmission and Reception node TRP (Transmission and Reception Point), a relay satellite, a satellite base station, an air base station, and other wireless communication devices.

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

Claims

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

2. The first node of claim 1, wherein the second set of data units indicates a first set of reference values, the first set of reference values being used to indicate the second message.

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

the first receiver, after sending the first message and before the second message is received, receiving at least one data unit over the first radio bearer;

wherein the transmission of the at least one data unit is carried over the first RLC.

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

the first receiver, in response to the act of determining that the first connection failed, starting a first timer; stopping the first timer when the second message is received; stopping monitoring the third set of data units when the first timer expires.

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

the first receiver, after receiving the second message, establishes a second connection according to the second message;

wherein the second connection is used for transmitting control plane information.

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

7. The first node of claim 6, comprising:

the second receiver receives the second message over the backhaul link.

8. The first node according to claim 6 or 7, comprising:

the second transmitter transmits the first message through the backhaul link.

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

a third receiver that receives the first message over the backhaul link;

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

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

12. A method in a third node used for wireless communication, comprising:

receiving a first message over the backhaul link;