CN110636562A

CN110636562A - Data processing method and equipment for wireless backhaul path

Info

Publication number: CN110636562A
Application number: CN201810646131.5A
Authority: CN
Inventors: 刘佳敏; 张大钧; 陈喆
Original assignee: Telecommunications Science and Technology Research Institute Co Ltd
Current assignee: Datang Mobile Communications Equipment Co Ltd
Priority date: 2018-06-21
Filing date: 2018-06-21
Publication date: 2019-12-31
Anticipated expiration: 2038-06-21
Also published as: CN110636562B

Abstract

The embodiment of the invention provides a data processing method and equipment of a wireless backhaul path. In the method of the embodiment of the invention, the first donor base station sends an indication message for indicating the starting of a Packet Data Convergence Protocol (PDCP) data recovery process or a PDCP reconstruction process to the terminal under the condition that the wireless backhaul of the terminal needs to be changed. The embodiment of the invention can provide stable data transmission service for the terminal under the conditions of terminal switching and relay node link switching, and can reduce the complexity of a wireless backhaul system.

Description

Data processing method and equipment for wireless backhaul path

Technical Field

The embodiment of the invention relates to the technical field of communication, in particular to a data processing method and equipment of a wireless backhaul path.

Background

In the future development of mobile communication systems, in order to better meet user requirements and greatly improve network capacity and throughput, more transmission nodes and larger transmission bandwidth must be introduced. In a fifth-generation communication technology (5G) network, the number of access stations is greatly increased, but it cannot be guaranteed that all access stations have wired backhaul conditions, and introduction of a wireless access station cannot be avoided. In the face of the requirement of higher transmission rate and transmission delay of 5G, higher requirements are put on a wireless backhaul network.

However, in the prior art, there is no data processing method for the multi-hop multi-connection 5G wireless relay node switching. Since the Relay (Relay) of 3GPP R10 version is a layer three device and single hop connection, its data processing method directly multiplexes the processing method of the wired access network, and is not suitable for Integrated access and Backhaul node (IAB node) networks, so a new data processing method during handover needs to be studied to meet the requirement of providing stable data transmission service for users, and to control the system complexity within a reasonable range.

Disclosure of Invention

An object of the embodiments of the present invention is to provide a method and an apparatus for processing data of a wireless backhaul path of a wireless backhaul node, which can provide a stable data transmission service for a terminal and reduce implementation complexity of a wireless backhaul system.

The embodiment of the invention provides a data processing method of a wireless backhaul path, which is applied to a first donor base station and comprises the following steps:

the method comprises the steps that a first donor base station sends an indication message used for indicating the starting of a Packet Data Convergence Protocol (PDCP) data recovery process or a PDCP reestablishment process to a terminal under the condition that a wireless backhaul path of the terminal needs to be changed.

The embodiment of the invention also provides another data processing method of a wireless backhaul path, which is applied to a terminal and comprises the following steps:

the terminal receives an indication message sent by the first donor base station and used for indicating the starting of a Packet Data Convergence Protocol (PDCP) data recovery process or a PDCP reconstruction process.

An embodiment of the present invention further provides a first donor base station, including: a transceiver, a memory, a processor, and a program stored on the memory and executable on the processor;

the transceiver is used for sending an indication message for indicating the starting of a Packet Data Convergence Protocol (PDCP) data recovery process or a PDCP reconstruction process to the terminal through the transceiver under the condition that the wireless backhaul of the terminal needs to be changed.

An embodiment of the present invention further provides a first donor base station, including:

a sending processing unit, configured to send, to the terminal through the transceiver, an indication message for indicating to start a packet data convergence protocol PDCP data recovery procedure or a PDCP re-establishment procedure when a wireless backhaul of the terminal needs to be changed.

An embodiment of the present invention further provides a terminal, including: a transceiver, a memory, a processor, and a program stored on the memory and executable on the processor;

the transceiver is configured to receive an indication message sent by the first donor base station and used for indicating to start a packet data convergence protocol PDCP data recovery procedure or a PDCP re-establishment procedure.

An embodiment of the present invention further provides a terminal, including:

and the sending processing unit is used for receiving an indication message which is sent by the first donor base station and used for indicating the starting of a Packet Data Convergence Protocol (PDCP) data recovery process or a PDCP reconstruction process.

Embodiments of the present invention also provide a computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, implements the steps of the method as described above.

The data processing method and the data processing equipment for the wireless backhaul path provided by the embodiment of the invention can provide stable data transmission service for the terminal under the conditions of terminal switching and relay node link switching, and can reduce the complexity of a wireless backhaul system.

Drawings

Various other advantages and benefits will become apparent to those of ordinary skill in the art upon reading the following detailed description of the preferred embodiments. The drawings are only for purposes of illustrating the preferred embodiments and are not to be construed as limiting the invention. Also, like reference numerals are used to refer to like parts throughout the drawings. In the drawings:

fig. 1 is a schematic structural diagram of a prior art 5G mobile communication system;

fig. 2 is a schematic diagram of a protocol stack architecture of a user plane of a 5G mobile communication system in the prior art;

fig. 3 is a schematic diagram of a protocol stack architecture of a control plane of a 5G mobile communication system in the prior art;

fig. 4 is a schematic view of an application scenario of the data processing method of the wireless backhaul path according to the embodiment of the present invention;

fig. 5 is a flowchart of a data processing method of a wireless backhaul path according to an embodiment of the present invention;

fig. 6 is a second flowchart of a data processing method of a wireless backhaul path according to an embodiment of the present invention;

fig. 7 is a first scenario diagram of a data processing method of a wireless backhaul path according to an embodiment of the present invention;

fig. 8 is a schematic diagram of a first scenario of a data processing method of a wireless backhaul path according to an embodiment of the present invention;

fig. 9 is a first scenario diagram of a data processing method of a wireless backhaul path according to an embodiment of the present invention;

fig. 10 is a schematic diagram of a first scenario of a data processing method of a wireless backhaul path according to an embodiment of the present invention;

fig. 11 is one of structural diagrams of a first donor base station according to an embodiment of the present invention;

fig. 12 is a second structural diagram of a first donor base station according to the embodiment of the present invention;

fig. 13 is one of the structural diagrams of a terminal of the embodiment of the present invention;

fig. 14 is a second structural diagram of a terminal according to an embodiment of the present invention.

Detailed Description

The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are some, not all, embodiments of the present invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.

The terms "comprises," "comprising," or any other variation thereof, in the description and claims of this application, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed, but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus. Furthermore, the use of "and/or" in the specification and claims means that at least one of the connected objects, such as a and/or B, means that three cases, a alone, B alone, and both a and B, exist.

In the embodiments of the present invention, words such as "exemplary" or "for example" are used to mean serving as examples, illustrations or descriptions. Any embodiment or design described as "exemplary" or "e.g.," an embodiment of the present invention is not necessarily to be construed as preferred or advantageous over other embodiments or designs. Rather, use of the word "exemplary" or "such as" is intended to present concepts related in a concrete fashion.

For better understanding of the technical solution of the embodiment of the present invention, the following technical points are first introduced:

(1) introduction to 5G mobile communication system.

In a 5G mobile communication system, nodes on a network side are mostly connected by wire, a gbb (nr nodeb) may be connected by wire, and a gbb and a 5G core network node are also connected by wire, as shown in fig. 1. The 5G core network node may include Access and Mobility Management Function (AMF) entities, User Plane Function (UPF) entities, and other device or network functions. The NG-eNB in fig. 1 is an eNB node providing E-UTRA user plane and control plane protocols and functions to a terminal (UE), which may be connected to a 5G core network node through an NG interface.

(2) Introduction to the 5G radio protocol architecture.

The 5G basic user plane protocol layer comprises: service Data Adaptation Protocol (SDAP), Packet Data Convergence Protocol (PDCP), Radio Link Control (RLC), Media Access Control (MAC), and physical layer (PHY). The control plane protocol layers include: non-access stratum (NAS), Radio Resource Control (RRC), PDCP, RLC, MAC, and PHY. The protocol stack architecture diagrams of the user plane and the control plane are shown in fig. 2 and fig. 3, respectively.

Embodiments of the present invention are described below with reference to the accompanying drawings. The data processing method and the data processing equipment of the wireless backhaul path provided by the embodiment of the invention can be applied to a wireless communication system. The wireless communication system may be a 5G system, or an Evolved Long Term Evolution (lte) system, or a subsequent Evolved communication system.

Fig. 4 shows an application scenario of the data processing method of the wireless backhaul path according to an embodiment of the present invention. The wireless relay nodes 1 to 7 in fig. 4 constitute a wireless backhaul network, in which a multi-hop wireless backhaul path is established from a network side node, such as a Donor base station (Donor base station), to a terminal through the wireless relay node 2, the wireless relay node 4, and the wireless relay node 5 in sequence. Taking the 5G system as an example, the wireless relay node in fig. 4 may be an Integrated Access and Backhaul node (IAB node). The IAB node may have full base station functionality or may only have data forwarding functionality similar to the base station. The network side node connected by the wired interface is a base station, which is also called a Donor base station (Donor base station, also called DgNB) in the embodiment of the present invention. The Donor base station and the wireless relay node can communicate through a wireless interface. The wireless relay nodes may also communicate over a wireless interface.

In the embodiments of the present invention, the donor base stations are usually connected by wires, and the donor base stations and the core network node are also usually connected by wires. The donor base station in the embodiment of the present invention may be a base station used in general, may also be an evolved node base station (eNB), and may also be a network side device (e.g., a next generation base station (gNB) or a Transmission and Reception Point (TRP)) in a 5G system.

The wireless relay node of the embodiment of the present invention, also referred to as a relay node for short, may have a complete base station function, or may only have a data forwarding function similar to a base station, and specifically may be an IAB node, a wireless relay, or other devices. A relay node is typically attributed to a donor base station, i.e. is accessed to the core network through the donor base station, and a relay node attributed to a donor base station is also referred to herein as a relay node under the donor base station.

The terminal according to the embodiment of the present invention may specifically be a mobile phone (or a mobile phone), or other devices capable of sending or receiving wireless signals, including User Equipment (UE), a Personal Digital Assistant (PDA), a wireless modem, a wireless communication apparatus, a handheld apparatus, a laptop computer, a cordless phone, a Wireless Local Loop (WLL) station, a CPE (Customer premises Equipment) or a mobile intelligent hotspot capable of converting a mobile signal into a WiFi signal, an intelligent appliance, or other devices capable of autonomously communicating with a mobile communication network without human operation, and the like.

In the embodiment of the present invention, the parent node at the upper level of a certain device (including a wireless relay node and a terminal) refers to a previous-hop node in a wireless backhaul path from a Donor base station to the terminal, where the device sequentially passes through one or more wireless relay nodes.

In the prior art, the Relay (Relay) related standard of 3GPP R10 version is directed to a scenario of layer three devices and single-hop connection, and its data processing method directly multiplexes the processing method of the wired access network, and is not suitable for the scenario of fig. 4 in which the multi-hop multi-connection 5G wireless Relay node is switched. In order to provide stable data transmission service for users and control the system complexity within a reasonable range, the embodiment of the present invention provides a solution suitable for the application scenario of fig. 4.

Referring to fig. 5, a data processing method of a wireless backhaul provided in an embodiment of the present invention, when applied to a first donor base station, includes:

step 51, the first donor base station sends an indication message for indicating to start a Packet Data Convergence Protocol (PDCP) Data recovery process or a PDCP reestablishment process to the terminal when the wireless backhaul of the terminal needs to be changed.

Here, the donor base station on the current wireless backhaul path of the terminal is the first donor base station, that is, the PDCP Anchor (PDCP Anchor) of the terminal is the first donor base station. The first donor base station may send an indication message indicating to start a PDCP data recovery procedure or a PDCP re-establishment procedure to the terminal when a change of a wireless backhaul path of the terminal is required. Changing the wireless backhaul path of the terminal may specifically include switching a node or a link on the wireless backhaul path, switching a PDCP anchor, updating a security parameter, and the like.

For example, when the wireless backhaul path of a terminal needs to be changed, if the PDCP anchor point of the terminal is not changed and the security parameters are not updated, the first donor base station may send a first indication message to the terminal, where the first indication message indicates to start a PDCP data recovery procedure; if the PDCP anchor of the terminal is changed or the security parameter is updated, a second indication message indicating that the PDCP re-establishment procedure is started may be transmitted to the terminal. Here, the indication message, such as the first indication message or the second indication message, may be sent in an RRC signaling manner, or may be sent by using a custom signaling or other signaling, which is not specifically limited in this embodiment of the present invention.

Through the steps, the donor base station on the wireless backhaul path is provided, and the PDCP data recovery or reconstruction process is started by sending the indication message to the terminal when the wireless backhaul path needs to be changed, so that the reliability of data transmission on the wireless backhaul path can be ensured.

In step 51, the first donor base station receives a first message sent by a first relay node and/or a second message sent by a second relay node, where the second relay node is a parent node of the first relay node on the wireless backhaul path, and the first message and the second message are any one of a measurement report message, a load report message, a link change request message, and a link failure indication message. Here, the first message may carry link quality information of a candidate serving relay node of the first relay node, so that the first donor base station may select a target relay node for handover according to the link quality information. And then, the first donor base station sends the first indication message to the terminal when determining that the parent node of the previous stage of the first relay node needs to be replaced by a third relay node according to the first message and/or the second message, wherein the second relay node and the third relay node are both relay nodes belonging to the first donor base station.

In the first scenario, when determining that the parent node at the previous stage of the first relay node needs to be replaced by the third relay node, the first donor base station may further send a first release message to the first class of relay node, send a first setup message to the second class of relay node, and send a first reset message to the third class of relay node. Wherein the first class of relay nodes includes relay nodes deleted from the wireless backhaul path after the change, the second class of relay nodes includes relay nodes newly added from the wireless backhaul path after the change, and the third class of relay nodes includes relay nodes existing in the wireless backhaul path before and after the change and having links changed in the wireless backhaul path.

Correspondingly, after receiving the first release message, the relay node may perform processing such as deleting context configuration of the corresponding terminal and clearing cache data according to the first release message. After receiving the first establishment message, the relay node may perform processing such as newly establishing a context of the corresponding terminal and configuring a cache according to the first establishment message. After receiving the first reset message, the relay node may perform, according to the first reset message, processing of resetting the RLC layer and the MAC layer protocol stack, newly establishing a context of the corresponding terminal, configuring a cache, and the like. The corresponding terminals mentioned above may include all terminals or some terminals involved in the change of the wireless backhaul path. For example, when a plurality of terminals access the network through the wireless backhaul, when a relay node in the wireless backhaul needs to be changed, corresponding processing may be performed on all or a part of terminals involved in the wireless backhaul (for example, terminals performing acknowledged mode AM traffic).

In step 51, in a second scenario where a relay node directly accessed by a terminal in a wireless backhaul path is switched and relay nodes before and after the switching are all relay nodes under the same donor base station, the second scenario is also referred to as a scenario where the terminal is switched in the donor base station, and the first donor base station receives a measurement report message sent by the terminal; furthermore, the first donor base station may send the first indication message to the terminal when determining that the serving node of the terminal needs to be switched from the fourth relay node to a fifth relay node according to a measurement report message sent by the terminal, where the fourth relay node and the fifth relay node are both relay nodes under the first donor base station.

In the second scenario, when determining that the serving node of the terminal needs to be switched from the fourth relay node to the fifth relay node, the first donor base station may send a second release message to the first class of relay node, send a second setup message to the second class of relay node, send a second reset message to the third class of relay node, and further instruct the terminal to reset the RLC and MAC layer protocol stack in the first instruction message and configure the fifth relay node as the serving node; wherein the first class of relay nodes includes relay nodes deleted from the wireless backhaul path after the change, the second class of relay nodes includes relay nodes newly added from the wireless backhaul path after the change, and the third class of relay nodes includes relay nodes existing in the wireless backhaul path before and after the change and having links changed in the wireless backhaul path.

Correspondingly, after receiving the second release message, the relay node may perform processing such as deleting the context configuration of the corresponding terminal and clearing the cache data according to the second release message. After receiving the second establishment message, the relay node may perform processing such as newly establishing a context of the corresponding terminal and configuring a cache according to the second establishment message. After receiving the second reset message, the relay node may perform, according to the second reset message, processing of resetting the RLC layer and the MAC layer protocol stack, newly establishing a context of the corresponding terminal, configuring a cache, and the like. Similarly, the corresponding terminals mentioned above may include all or some of the terminals involved in the change of the wireless backhaul path.

In the first and second scenarios, after the first indication message is sent, the transmission of the relevant data packet may be performed through a PDCP data recovery procedure.

Specifically, the first donor base station may receive a first PDCP status report sent by the terminal, where the first PDCP status report indicates a reception condition of a PDCP data packet sent by the first donor base station, and specifically, the first PDCP status report includes that the terminal sends after receiving the first indication message, and/or that the terminal sends at a first sending opportunity. Here, the first sending opportunity includes a predetermined first sending time period or a first PDCP status request message sent by a first donor base station or each time the terminal receives a first predetermined number or a first predetermined size of PDCP data packets, where the first PDCP status request message is sent by the first donor base station after each time the first predetermined number or the first predetermined size of PDCP data packets is sent. Furthermore, the first donor base station may determine and transmit a PDCP data packet that needs to be transmitted in a PDCP data recovery process according to the receiving condition indicated by the first PDCP status report.

Correspondingly, the first donor base station may also generate and send a second PDCP status report to the terminal according to a reception condition of a PDCP data packet sent by the terminal at a second sending opportunity and/or when a wireless backhaul of the terminal needs to be changed; wherein the second sending opportunity includes a predetermined second sending time period, a second PDCP status request message sent by the receiving terminal, or a second PDCP status request message sent by the first donor base station every time the first donor base station receives a second predetermined number of PDCP data packets or a second predetermined size, where the second PDCP status request message is sent by the receiving terminal every time the second donor base station sends a second predetermined number of PDCP data packets or a second predetermined size of PDCP data packets.

By sending the PDCP status report at the first sending opportunity/the second sending opportunity, the enhancement of the PDCP function is realized, and the data packet which does not obtain the receiving confirmation of the opposite end can be retransmitted in time.

In addition, another enhancement mode of the PDCP function is further provided in the embodiments of the present invention, specifically, after the first indication message is sent, the first donor base station may delete a packet whose remaining time is less than a predetermined threshold or delete a packet whose discard timer is out of date according to a sending queue of the PDCP packet of the terminal and the remaining time of the discard timer of the packet in the queue to be confirmed; and then, determining the PDCP data packets which need to be sent in the PDCP data recovery process and sending the PDCP data packets according to the sending queue and the data packets left in the queue to be confirmed. Here, the predetermined threshold may be determined according to an end-to-end transmission Delay and a Packet Delay Budget (PDB) of the Packet, which is not specifically limited in the embodiment of the present invention.

For example, when the enhancement modes are simultaneously adopted, the PDCP data packet which is not required to be sent in the PDCP data recovery process can be determined and deleted according to each enhancement mode, and the PDCP data packet which is required to be sent can be obtained.

In a third scenario in which a relay node directly accessed by a terminal in a wireless backhaul path is switched and the relay nodes before and after the switching do not belong to relay nodes under the same donor base station, the third scenario is also referred to as a scenario in which the relay nodes cross the donor base station, and in the third scenario, a PDCP anchor of the terminal is changed or a security parameter is updated, at this time, in step 51, the first donor base station receives a third message sent by a sixth relay node and/or a fourth message sent by a seventh relay node, the seventh relay node is a parent node of an upper level of the sixth relay node in the wireless backhaul path, and the third message and the fourth message are any one of a measurement report message, a load report message, a link change request message, and a link failure indication message. Here, the third message may carry link quality information of a candidate serving relay node of the sixth relay node, so that the first donor base station may select the target relay node. And the first donor base station sends the second indication message to the terminal when determining that the parent node at the upper stage of the sixth relay node needs to be replaced by an eighth relay node according to the third message and/or the fourth message, wherein the seventh relay node is a relay node which belongs to the first donor base station and is directly accessed to the first donor base station, and the eighth relay node is a relay node which belongs to the second donor base station and is directly accessed to the second donor base station.

In the third scenario, when determining that the parent node at the upper stage of the sixth relay node needs to be replaced by the eighth relay node, the first donor base station may further send a third release message to the relay nodes of the fourth class, send a third establishment message to the relay nodes of the fifth class, and send a third reset message to the relay nodes of the sixth class. The fourth class of relay nodes includes relay nodes deleted from the wireless backhaul path after the change, the fifth class of relay nodes includes relay nodes newly added from the wireless backhaul path after the change, and the sixth class of relay nodes includes relay nodes existing in the wireless backhaul paths before and after the change.

Correspondingly, after receiving the third release message, the relay node may perform processing such as deleting the context configuration of the corresponding terminal and clearing the cache data according to the third release message. After receiving the third establishment message, the relay node may perform processing such as newly establishing a context of the corresponding terminal and configuring a cache according to the third establishment message. After receiving the third reset message, the relay node may perform, according to the third reset message, processing of resetting the RLC layer and the MAC layer protocol stack, newly establishing a context of the corresponding terminal, configuring a cache, and the like. Similarly, the corresponding terminals mentioned above may include all or some of the terminals involved in the change of the wireless backhaul path.

In a fourth scenario in which a relay node directly accessed by a terminal in a wireless backhaul path is switched and the relay nodes before and after switching do not belong to relay nodes under the same donor base station, the fourth scenario is also referred to as a scenario in which the terminal switches across donor base stations, and in the fourth scenario, the first donor base station changes at a PDCP anchor point of the terminal or updates security parameters, and at this time, in step 51, the first donor base station receives a measurement report message sent by the terminal; the first donor base station sends the second indication message to the terminal when determining that the service node of the terminal needs to be switched from the ninth relay node to the tenth relay node according to the measurement report message sent by the terminal; the ninth relay node is a relay node belonging to the first donor base station, and the tenth relay node is a relay node belonging to the second donor base station.

In the fourth scenario, when determining that the serving node of the terminal needs to be switched from the ninth relay node to the tenth relay node, the first donor base station may further send a fourth release message to the fourth class of relay node, send a fourth establishment message to the fifth class of relay node, send a fourth reset message to the sixth class of relay node, and further instruct the terminal to reset the RLC and MAC protocol stacks and configure the tenth relay node as the serving node in the second indication message. The fourth class of relay nodes includes relay nodes deleted from the wireless backhaul path after the change, the fifth class of relay nodes includes relay nodes newly added from the wireless backhaul path after the change, and the sixth class of relay nodes includes relay nodes existing in the wireless backhaul paths before and after the change.

Correspondingly, after receiving the fourth release message, the relay node may perform processing such as deleting context configuration of the corresponding terminal and clearing cache data according to the fourth release message. After receiving the fourth establishment message, the relay node may perform processing such as newly establishing a context of the corresponding terminal and configuring a cache according to the fourth establishment message. After receiving the fourth reset message, the relay node may perform, according to the fourth reset message, processing of resetting the RLC layer and the MAC layer protocol stack, newly establishing a context of the corresponding terminal, configuring a cache, and the like. Similarly, the corresponding terminals mentioned above may include all or some of the terminals involved in the change of the wireless backhaul path.

In the third and fourth scenarios, after the second indication message is sent, the transmission of the relevant data packet may be performed through a PDCP reestablishment procedure.

Specifically, the first donor base station may receive a third PDCP status report sent by the terminal, where the third PDCP status report indicates a reception condition of a PDCP data packet sent by the first donor base station, and the third PDCP status report includes a first PDCP status request message generated by the terminal after receiving the second indication message, and/or the terminal sends the third PDCP status report at a first sending opportunity, where the first sending opportunity includes a predetermined first sending time period, or receives a first PDCP status request message sent by the first donor base station, or the terminal receives a first predetermined number of PDCP data packets or a first predetermined size each time, where the first PDCP status request message is sent by the first donor base station after sending the first predetermined number of PDCP data packets or the first predetermined size each time. And determining the PDCP data packets which need to be sent in the PDCP rebuilding process according to the receiving condition indicated by the third PDCP status report.

Further, the first donor base station may also forward the determined PDCP data packet and Sequence Number (SN) information thereof to be sent in the PDCP re-establishment procedure to a second donor base station, so that the second donor base station can send the PDCP data packet in the PDCP re-establishment procedure, where the second donor base station is the donor base station where the changed PDCP anchor point is located.

Correspondingly, the first donor base station may also generate and send a fourth PDCP status report to the terminal according to a reception condition of a PDCP data packet sent by the terminal at a second sending opportunity and/or when a wireless backhaul of the terminal needs to be changed; wherein the second sending opportunity includes a predetermined second sending time period, a second PDCP status request message sent by the receiving terminal, or a second PDCP status request message sent by the first donor base station every time the first donor base station receives a second predetermined number of PDCP data packets or a second predetermined size, where the second PDCP status request message is sent by the receiving terminal every time the second donor base station sends a second predetermined number of PDCP data packets or a second predetermined size of PDCP data packets.

In addition, another enhancement mode of the PDCP function is further provided in the embodiments of the present invention, specifically, after the second indication message is sent, the first donor base station may delete a data packet whose remaining time is less than a predetermined threshold or delete a data packet whose discarding timer is out of date according to a sending queue of the PDCP data packet of the terminal and the remaining time of the discarding timer of the data packet in the queue to be confirmed; and then, determining the PDCP data packets which need to be sent in the PDCP reconstruction process according to the sending queue and the data packets left in the queue to be confirmed. Here, the predetermined threshold may be determined according to an end-to-end transmission Delay and a Packet Delay Budget (PDB) of the Packet, which is not specifically limited in the embodiment of the present invention. Further, the first donor base station may also forward the determined PDCP data packet and Sequence Number (SN) information thereof to be sent in the PDCP re-establishment procedure to a second donor base station, so that the second donor base station can send the PDCP data packet in the PDCP re-establishment procedure, where the second donor base station is the donor base station where the changed PDCP anchor point is located.

In view of that an anchor point of a certain terminal (referred to as another terminal) may also be handed over from a third donor base station to a first donor base station, in this case, the method of the embodiment of the present invention may further include: and receiving a PDCP data packet which is forwarded by a third donor base station and needs to be sent to another terminal in the PDCP reestablishment process and serial number SN information thereof, wherein the first donor base station is the donor base station where a PDCP anchor point after the wireless backhaul path of the another terminal is changed, the third donor base station is the donor base station where the PDCP anchor point before the wireless backhaul path of the another terminal is changed, and at the moment, the first donor base station generates and sends a PDCP state report to the another terminal according to the PDCP data packet and the serial number SN information thereof.

As can be seen from the above description, the data processing method of the wireless backhaul path according to the embodiment of the present invention can perform a data recovery or reconstruction process as soon as possible in various scenarios where links in the wireless backhaul path are switched, so as to meet the requirement of lossless terminal data, improve system efficiency, and the implementation complexity of the method is relatively low.

The method of the embodiment of the present invention is described above from the donor base station side, and will be explained below from the terminal side.

Referring to fig. 6, a data processing method of a wireless backhaul provided in an embodiment of the present invention, when applied to a terminal, includes:

and step 61, the terminal receives an indication message which is sent by the first donor base station and used for indicating the starting of the PDCP data recovery process or the PDCP reconstruction process.

Here, the first donor base station is a donor base station on a current wireless backhaul path of the terminal. The first donor base station may send the indication information when the wireless backhaul path of the terminal needs to be changed, where the indication information may be sent by RRC signaling, custom signaling, or other signaling, and this is not specifically limited in this embodiment of the present invention. Specifically, the indication information may be a first indication message for indicating to start a PDCP data recovery procedure or a second indication message for indicating to start a PDCP re-establishment procedure.

After receiving the indication information, the terminal according to the embodiment of the present invention may further start a PDCP data recovery procedure or a PDCP re-establishment procedure, so as to provide reliability of data transmission on a wireless backhaul.

In the above step 61, the indication message may include a first indication message for indicating to start the PDCP data recovery procedure and a second indication message for indicating to start the PDCP re-establishment procedure.

For the case that the indication information is a first indication message:

preferably, the first indication message may be further configured to indicate that the terminal is further configured to reset the RLC and MAC layer protocol stacks and configure the fifth relay node as the serving node, and at this time, after step 61, the terminal may further reset the RLC and MAC layer protocol stacks and configure the serving node as the fifth relay node according to the first indication message. Further, a PDCP data recovery procedure may be initiated to transmit PDCP data packets.

Preferably, in the above method of the embodiment of the present invention, the terminal may further generate and send a first PDCP status report to the first donor base station according to a receiving condition of a PDCP data packet sent by the first donor base station at a first sending opportunity and/or when receiving the first indication message; the first sending opportunity comprises a preset first sending time period or a first PDCP state request message sent by a first donor base station or the first PDCP state request message is sent by the first donor base station after the first donor base station sends the PDCP data packets of the first preset number or the first preset size every time the terminal receives the PDCP data packets of the first preset number or the first preset size.

Preferably, in the above method of the embodiment of the present invention, after receiving the first indication message, the terminal may further receive a second PDCP status report transmitted by the first donor base station, the second PDCP status report indicating a reception condition of PDCP data packets transmitted by the terminal, the second PDCP status report includes a report that is transmitted when the first donor base station needs to change a radio backhaul path of the terminal, and/or the first donor base station transmits at a second transmission opportunity, where the second transmission opportunity includes a predetermined second transmission time period or a second PDCP status request message transmitted by the receiving terminal or every time the first donor base station receives a second predetermined number of PDCP data packets or a second predetermined size, wherein the second PDCP status request message is transmitted by the terminal every time a second predetermined number or size of PDCP data packets is transmitted; and the terminal determines the PDCP data packet which needs to be sent in the PDCP data recovery process and sends the PDCP data packet according to the receiving condition indicated by the second PDCP status report.

Preferably, in the above method of the embodiment of the present invention, after receiving the first indication message, the terminal may further delete a data packet whose remaining time is less than a predetermined threshold or delete a data packet whose discard timer is overtime according to the transmission queue of the PDCP data packet of the first donor base station and the remaining time of the discard timer of the data packet in the queue to be acknowledged; and determining the PDCP data packets which need to be sent in the PDCP data recovery process and sending the PDCP data packets according to the sending queue and the data packets left in the queue to be confirmed.

For the case that the indication information is second indication information:

preferably, after receiving the second indication message, the terminal may reset the RLC and MAC layer protocol stacks according to the second indication message, and start a PDCP re-establishment procedure.

Preferably, the second indication message is further configured to indicate the terminal to reset the RLC and MAC layer protocol stacks and configure the tenth relay node as the service node, and after receiving the second indication message, the terminal may reset the RLC and MAC layer protocol stacks and configure the service node as the tenth relay node according to the second indication message, and start a PDCP re-establishment procedure.

Preferably, after receiving the second indication message, the terminal may further generate and send a third PDCP status report to the first donor base station according to a receiving condition of a PDCP data packet sent by the first donor base station at the first sending opportunity and/or when receiving the second indication message; the first sending opportunity comprises a preset first sending time period or a first PDCP state request message sent by a first donor base station or the first PDCP state request message is sent by the first donor base station after the first donor base station sends the PDCP data packets of the first preset number or the first preset size every time the terminal receives the PDCP data packets of the first preset number or the first preset size.

Preferably, after receiving the second indication message, the terminal may further receive a fourth PDCP status report transmitted by the first donor base station, the fourth PDCP status report indicates a reception condition of a PDCP packet transmitted by the terminal, the fourth PDCP status report includes information transmitted when the first donor base station needs to change a radio backhaul of the terminal, and/or the first donor base station transmits at a second transmission opportunity, where the second transmission opportunity includes a predetermined second transmission time period or a second PDCP status request message transmitted by the receiving terminal or every time the first donor base station receives a second predetermined number of PDCP data packets or a second predetermined size, wherein the second PDCP status request message is transmitted by the terminal every time a second predetermined number or size of PDCP data packets is transmitted; and further determining the PDCP data packets which need to be sent in the PDCP rebuilding process and sending the PDCP data packets according to the receiving condition indicated by the fourth PDCP status report.

Preferably, after receiving the second indication message, the terminal may further delete a data packet whose remaining time is less than a predetermined threshold or delete a data packet whose discard timer is out of time according to the transmission queue of the PDCP data packet of the first donor base station and the remaining time of the discard timer of the data packet in the queue to be confirmed; and determining the PDCP data packets which need to be sent in the PDCP reconstruction process and sending the PDCP data packets according to the sending queue and the data packets left in the queue to be confirmed.

Exemplary views of the first scenario to the fourth scenario are further provided below to describe the above method flow in more detail. In the following multiple scenarios, a wireless relay node is taken as an IAB node, a terminal is taken as a UE, and a Donor base station is taken as a Donor gNB.

A first scenario: scenario of relay node switching in donor base station

Referring to fig. 7, the UE accesses the Donor gNB1 through the IABs 1 and 2, the wireless backhaul path is UE-IAB1-IAB2-Donor gNB1, and it is assumed that the Donor gNB1 needs to switch the parent node at the previous stage of the IAB1 from the IAB2 to the IAB3, which causes the wireless backhaul path to change, and the changed wireless backhaul path is UE-IAB1-IAB3-Donor gNB 1.

Fig. 7 shows a specific example of an IAB node handover. The IAB1 is one of the IAB nodes participating in serving the UE, and generally, the IAB node is fixed and does not move actively, but does not exclude the case of performing link reselection to the IAB1 due to factors such as high frequency flash/occlusion, or due to a shutdown or overload of a parent node of the IAB 1. As shown in FIG. 7, the parent IAB2 of IAB1 can no longer provide service for it, and then the IAB1 node needs to be replaced with the new parent IAB 3.

Triggering of IAB1 path switching generally has two ways:

1) and reporting the measurement based on the IAB 1.

In this way, since the IAB1 is a wireless relay node, the Donor gNB1 may configure its measurement configuration similar to that of the UE, and request the IAB1 to perform monitoring of its parent node link and neighboring IAB node links, and once the link between the IAB1 and its parent node IAB2 is found to deteriorate to a point that the service requirement cannot be met, the IAB1 needs to report the measurement result to the Donor gNB1, which may carry potential link quality measurement conditions of other IAB nodes for subsequent reselection of the parent node. Another special case is if the IAB1 has a radio link failure and is not able to report any measurement reports. At this time, the IAB1 may select another IAB node to access the Donor gNB1, initiate re-establishment with the UE identity, optionally report its own condition, and request the Donor gNB1 to reselect an available parent node. Or, if the IAB1 has obtained a candidate serving cell list (candidate serving cell list) in the process of initial power-on through OAM and other manners, at this time, only one cell (parent node) needs to be selected from the list for connection, and the identity of the UE does not need to be reestablished, and the Donor gbb 1 may confirm or reconfigure its parent node.

2) Based on the reporting trigger of the original parent node IAB 2.

In this way, for example, when the IAB2 has a problem, for example, the load is too high, and the IAB1 cannot be served any more, the IAB2 may report to the Donor gNB1 to request that the IAB1 be handed over to another new parent node.

For the Donor gNB1, if the report from the IAB node is received and it is determined that the IAB2 can no longer continue to provide service for the IAB1, a new parent IAB3 needs to be reselected for the IAB 1. Typically, when selecting a new parent node, such as IAB3, the following factors need to be considered:

1) the link communication quality between IAB3 and IAB1 meets basic communication quality requirements. Regarding the link quality between IAB3 and IAB1, it can be reported by some a priori knowledge, such as deployment of network node topology, node location deployment, or some measurement of IAB nodes.

2) The IAB3 can provide data transmission service for the IAB1 in terms of load and capacity.

3) From the viewpoint of simplifying the topology, the IAB3 can be used as a parent node of the IAB1, and for example, the requirement that the number of hops to pass is as small as possible and a cyclic parent node (that is, two nodes are parent nodes to each other from the viewpoint of different path maintenance) does not occur is met.

After the Donor gNB1 replaces the IAB1 with a new parent IAB3, in addition to the corresponding configuration update procedure, it needs to be considered how the data of the UE concerned can be guaranteed to be lossless in the path switching procedure. One possible way is to start a PDCP data recovery (PDCP data recovery) procedure, send a PDCP data recovery command to all bearers/AM bearers related to the UE, and for the nodes related to the intermediate path, if a path change occurs, perform layer 2(L2) reset (e.g., reset the RLC and MAC layers), delete all buffered data, wait for end-to-end recovery, and if no path change occurs, keep the existing protocol layers and data unchanged and continue transmission. In the example of fig. 7, the path between IAB1 and IAB2 is changed, so that all of the relevant L2 is reset, the relevant buffered packets are deleted, and a new L2 protocol layer is established between IAB1 and IAB3 for new transmission. And the link between the UE and the IAB1 can be kept as it is and the transmission is continued because no change occurs.

The UE and the network side respectively start an uplink PDCP data recovery process and a downlink PDCP data recovery process, wherein the data recovery process mainly comprises the following actions:

1) the receiving end feeds back a PDCP status report to the transmitting end, wherein the PDCP status report comprises data packets which are not correctly received and need to be retransmitted, and the data packets which are correctly received;

2) the transmitting end starts retransmission from the first data that has not received an acknowledgement of receipt (ACK) according to the PDCP status report feedback situation. In a typical one-hop network, this ACK may be an ACK for the lower layer RLC because the RLC ACK feedback mechanism is more sophisticated and frequent, and once the opposite end RLC receives correctly, the PDCP also receives correctly. However, in the multi-hop network of the embodiment of the present invention, the role played by the RLC ACK is different, because in the multi-hop network, the RLC ACK can only indicate that the first hop transmission is successful, and the gap is large from reaching the PDCP at the opposite end. Therefore, in the multi-hop backhaul network according to the embodiment of the present invention, the PDCP layer retransmission needs to be performed based on the status report of the PDCP layer, and the retransmission determination cannot be performed according to the feedback of the RLC layer.

There are two ways in which PDPC retransmission can be enhanced:

the first is that: configuring an end-to-end status report of the PDCP into a regular report, for example, a status report feedback trigger based on a periodic timer, or a status report feedback trigger based on a certain PDCP PDU number, a byte size threshold and the like, requesting a status report from a sending end to a receiving end PDCP by the sending end at intervals or after N PDUs/M byte PDUs are sent/received, or automatically starting the status report feedback by the receiving end, so that the sending end can know whether the sending is successful or not in time, and the data which is not confirmed by the ACK of the opposite end can be retransmitted in time when various links are switched; it should be noted here that even if the receiving end displays NACK for a certain PDU in the status report, the sending end only records its status and does not trigger active retransmission, and the unacknowledged data is actively retransmitted unless receiving an indication of PDCP data recovery (PDCP data recovery) or PDCP re-establishment (PDCP re-acknowledgement) of the higher layer, which is performed for the purpose of ensuring correctness of data transmission because for the Acknowledged Mode (AM), the RLC has a good retransmission mechanism, the PDCP only needs to start active retransmission under RLC re-establishment, and the rest of the cases still depend on RLC retransmission to ensure correctness.

Secondly, the following steps: in the IAB architecture, due to the introduction of the multi-hop path, the PDCP end-to-end transmission Delay is relatively long, and is limited by the QoS parameter from the service transmission perspective, so that there is a limitation on the maximum allowed transmission Delay, that is, the end-to-end maximum allowed Delay is defined by the packet Delay budget (pdb) parameter in QoS. When each data packet arrives at the PDCP sending end, a Discard Timer (Discard Timer) is started, a timeout value of the Timer is usually slightly smaller than a PDB parameter, and mainly needs to deduct a transmission delay of the data in the core network, for example, the PDB parameter may be configured to 150ms for a normal AM service, deduct the transmission delay of the core network by 20ms, which is equivalent to a maximum allowed transmission delay at an air interface of 130ms, and when a duration of the data waiting in a sending queue or a queue waiting for acknowledgement exceeds 130ms, the data packet may be deleted (Discard). Then, when the PDCP sending end receives the command of requesting PDCP Datarecovery or PDCP re-acknowledgement from the higher layer, it can examine the data in its own sending queue and queue waiting for acknowledgement, and only those data whose remaining time of Discard timer is still longer than the average PDCP end-to-end transmission delay are retransmitted.

For example, if the PDCP end-to-end needs to undergo 4-hop transmission and the average transmission delay is estimated to be about 40ms, when the PDCP Data recovery or PDCP re-acknowledgement is needed, the PDCP sending end only needs to transmit and retransmit the Data whose remaining duration of the Discard timer in the PDCP sending queue and the queue waiting for acknowledgement is still greater than 40ms, and the rest of the Data can be directly deleted. Certainly, in the retransmission process, the data to be retransmitted can still be updated according to the status report of the opposite end of the PDCP layer, and if there is an ACK acknowledgement, the Discard PDU can be directly sent to the sending end without continuing retransmission. The main benefit of doing so is that retransmission and data recovery processes can be started as early as possible before the PDCP status report arrives, and fine adjustment of retransmission can be continued once the PDCP status report arrives, so that the requirement of fast retransmission is met while retransmission efficiency is also considered.

A second scenario: scenario of terminal switching in donor base station

Referring to fig. 8, the UE accesses the Donor gbb 1 through the IABs 1 and 2, and the wireless backhaul path is UE-IAB1-IAB2-Donor gbb 1, assuming that the Donor gbb 1 needs to switch the relay node directly accessed by the UE from IAB1 to IAB3, which results in a change of the wireless backhaul path, and the changed wireless backhaul path is UE-IAB3-IAB4-DonorgNB 1.

Fig. 8 shows a specific example of UE handover. When the UE needs to be handed over to the IAB3 by the IAB1 due to movement or link change. Generally, the handover is triggered by measurement reporting of the UE, and the UE reports the measurement result to the DonorgNB1 through the RRC layer, so as to inform the DonorgNB1 of the link degradation of the original IAB1, and the link quality of the IAB3 is better enough to bear the data transmission requirement of the UE.

In this case, when the Donor gNB1 determines that the UE needs to be handed over from the IAB1 to the IAB3, it may notify the relevant node and UE through signaling, for example, the IAB1 and the IAB2 need to be notified, the data of the UE is transferred from there, the context configuration information and data of the UE buffered by the two nodes may be deleted, and the IAB3 and the IAB4 may also be notified, and the UE configuration is ready for serving the UE.

For the UE, the Donor gNB1 may send a handover command to the UE informing the serving node of the UE to handover from IAB1 to IAB3, and the corresponding underlying configuration may change, which needs to adapt to the resource situation of the new IAB 3. In addition, in order to ensure that data between the UE and the Donor gNB1 is not damaged, especially data of AM service is not damaged, the PDCP layer between the Donor gNB1 and the UE may start a PDCP data recovery process, where the data recovery process includes a PDCP status report and retransmission, details may refer to the first scenario described above, and the same two enhancement modes may also be adopted, and are not described herein again for brevity.

Since the serving node of the UE has not changed in the first scenario, the first scenario may not have any configuration change, but only a data recovery procedure is initiated between the UE and the Donor gNB1 to ensure that the data is lossless. However, in the second scenario, since the serving node of the UE is changed, the Donor gNB1 configures the UE according to the new serving node, and thus the process is usually a new configuration accompanying data recovery process.

A third scenario: scenario for handover of relay node across donor base stations

Referring to fig. 9, the UE accesses the Donor gNB1 through the IABs 1 and IABs 2, the wireless backhaul path is UE-IAB1-IAB2-Donor gNB1, it is assumed that the Donor gNB1 needs to switch the parent node at the upper stage of the IAB1 from the IAB2 to the IAB3, which causes the wireless backhaul path to change, and the changed wireless backhaul path is UE-IAB1-IAB3-Donor gNB2, the IAB2 belongs to the Donor gNB1, and the IAB3 belongs to the Donor gNB 2.

Fig. 9 shows a scenario for an IAB node handover across Donor gNB, which typically occurs at the edge of a Donor gNB cell. When the IAB1 node cannot provide service for the parent node IAB2 due to link degradation or load condition abnormality of the parent node IAB2, the IAB1 node needs to replace the new parent node IAB3, and the IAB3 and the IAB2 node belong to different control ranges of the Donor gNB, which is equivalent to that the PDCP layer and RRC layer anchors of the UE are also switched, and the Donor gNB1 is switched to the Donor gNB 2.

This procedure may be generally based on measurement report triggering of the IAB1, or abnormal reporting of the IAB2 node, etc. And reporting the information to the Donor gNB1, and if the IAB is judged to need to be switched to the Donor gNB2, switching preparation, execution and other processes can be carried out between the gNBs, and the process is similar to the existing cross-base station switching. If the IAB1 link is degraded, then the re-establishment procedure is selected, and re-establishment to the prepared donor gNB2 is also a feasible case, similar to the existing re-establishment procedure.

In this case, since the Donor gNB is changed, the UE and the IAB1 are not changed, but both of them are equivalent to a handover procedure. And since the PDCP anchor point changes (from Donor gNB1 to Donor gNB2), generally, the PDCP entity needs to be rebuilt, which is the biggest difference from the data recovery process in that the operations such as security parameters and header compression are restarted. Starting from the first data after reconstruction, security operations are performed using the new key, and header compression is also resumed from the initial state.

Specifically, after receiving the handover command sent by the Donor gNB1, the UE side performs RLC and MAC layer reset, PDCP re-establishment, configuration of new parameters of layer one and layer two, and starts new transmission according to the handover command. In order to ensure the lossless data, especially AM data, PDCP reconstruction needs to keep Hyper Frame Number (HFN) and Sequence Number (SN) continuous, and send status report feedback to the opposite end according to the receiving situation, meanwhile, according to the above two enhanced modes, under the condition of new security parameters and header compression reset, data transmission can be restarted, and according to the received PDCP status report sent by the base station side, retransmission is abandoned for the data in which ACK has been sent, and only NACK data and data which has not been sent are transmitted.

For the IAB1, since the higher layer PDCP is re-established, the security parameters and header compression are reset, the IAB1 needs layer two reset/re-establishment, such as RLC layer flush buffer, and all state variables and timers are reset to initial values, although the link with the UE is not changed. The IAB2 is equivalent to directly deleting context and buffers related to the UE. The IAB3 creates context and related layer two entities related to the UE, such as RLC and MAC entities.

For the Donor gNB, since the change of the data anchor point occurs during the handover, in order to maintain the lossless data, it is necessary to transmit PDCP data and SN information between the original base station and the target base station, for example, discontinuous data received in uplink may be forwarded from the source base station to the target base station, so that the target base station generates a status report feedback of the receiving end according to the data and SN status information forwarding content, and sends the feedback to the UE for lossless guarantee of the uplink data. And the data to be sent in downlink or without receiving the positive acknowledgement also needs to be forwarded to the target base station, so as to perform retransmission or new transmission. It should be noted here that the ACK of the RLC layer cannot be directly used as a judgment criterion without receiving the data of the positive acknowledgement, because the ACK of the RLC layer can only indicate whether the transmission of one hop is successful or not. The judgment basis can refer to the two enhancing methods, and the PDCP conventional state feedback is taken as the basis and/or the QoS time delay parameter of the data is taken as the judgment standard. For the downlink data forwarded to the target base station, before receiving the status report feedback of the UE, the downlink data may be directly and sequentially transmitted, and once receiving the status report of the UE, the retransmission of the data that has been successfully transmitted may be abandoned.

A fourth scenario: scenario for terminal handover across donor base stations

Referring to fig. 10, the UE accesses the Donor gNB1 through the IABs 1 and 2, the wireless backhaul path is UE-IAB1-IAB2-Donor gNB1, and it is assumed that the Donor gNB1 needs to switch the relay node directly accessed by the UE from IAB1 to IAB3, which results in a change of the wireless backhaul path, and the changed wireless backhaul path is UE-IAB3-IAB4-Donor gnnb 2, the IAB2 belongs to Donor gNB1, and the IAB3 belongs to or gNB 2.

The fourth scenario may occur more easily than the third scenario. Since the IAB node is not generally moving, and the UE is usually moving, crossing the edge of the Donor gNB and entering the range of another Donor gNB, is a common handover scenario. Also, links on either side of the UE, such as the source link or the target link, do not exclude IABs from being involved, and connections directly to the legacy gNB are similar.

In this procedure, the Donor gNB1 determines, according to the measurement report of the UE, that the UE needs to switch to the IAB3-IAB4 link under the Donor gNB 2. The Donor gNB1 configures involved nodes, releases the contexts and buffers of the IAB1 and the IAB2, establishes the contexts and new entities of the IAB3 and the IAB4, and sends a handover command carrying a reestablishment indication to the UE.

The UE behavior is similar to that in the third scenario, except that the UE needs to access a new IAB3 node over the air interface, configure new relevant parameters, and perform other data processing consistent with 3. The processing on the gbb side is the same as in the third scenario. And will not be described herein for brevity.

It can be seen from the above multiple scenarios that the donor base station in the embodiment of the present invention can select a data recovery process or a data reconstruction process for the data of the UE in various scenarios, and the PDCP layer ensures that the data is lossless when the path is switched.

Based on the method, the embodiment of the invention also provides equipment for implementing the method.

Referring to fig. 11, an embodiment of the present invention provides a structural diagram of a first donor base station 1100, including: a processor 1101, a transceiver 1102, a memory 1103, and a bus interface, wherein:

the transceiver 1102 is configured to send, to the terminal through the transceiver, an indication message indicating to start a packet data convergence protocol PDCP data recovery procedure or a PDCP re-establishment procedure when a wireless backhaul of the terminal needs to be changed.

Preferably, the transceiver is further configured to send a first indication message for indicating to start a PDCP data recovery procedure to the terminal when the PDCP anchor of the terminal is not changed and the security parameter is not updated.

Preferably, the transceiver is further configured to receive a first message sent by a first relay node and/or a second message sent by a second relay node, where the second relay node is an upper parent node of the first relay node in the wireless backhaul path, and the first message and the second message are any one of a measurement report message, a load report message, a link change request message, and a link failure indication message.

In this embodiment of the present invention, the first donor base station 1100 further includes: a computer program stored on the memory 1103 and executable on the processor 1101.

The processor is used for reading the program in the memory and executing the following processes: determining that the parent node at the upper stage of the first relay node needs to be replaced by a third relay node according to the first message and/or the second message;

the transceiver is further configured to send the first indication message to the terminal when a parent node of an upper stage of the first relay node needs to be replaced by a third relay node, where the second relay node and the third relay node are both relay nodes belonging to the first donor base station.

In fig. 11, the bus architecture may include any number of interconnected buses and bridges, with one or more processors, represented by processor 1101, and various circuits, represented by memory 1103, linked together. The bus architecture may also link together various other circuits such as peripherals, voltage regulators, power management circuits, and the like, which are well known in the art, and therefore, will not be described any further herein. The bus interface provides an interface. The transceiver 1102 may be a plurality of elements including a transmitter and a receiver that provide a means for communicating with various other apparatus over a transmission medium.

The processor 1101 is responsible for managing the bus architecture and general processing, and the memory 1103 may store data used by the processor 1101 in performing operations.

Preferably, the first message carries link quality information of a candidate serving relay node of the first relay node.

Preferably, the transceiver 1102 is further configured to send a first release message to the first class relay node, send a first setup message to the second class relay node, and send a first reset message to the third class relay node when it is determined that the parent node at the upper stage of the first relay node needs to be replaced by the third relay node;

wherein the first class of relay nodes includes relay nodes deleted from the wireless backhaul path after the change, the second class of relay nodes includes relay nodes newly added from the wireless backhaul path after the change, and the third class of relay nodes includes relay nodes existing in the wireless backhaul path before and after the change and having links changed in the wireless backhaul path.

Preferably, the transceiver 1102 is further configured to receive a measurement report message sent by the terminal;

the processor 1101 is further configured to send the first indication message to the terminal when it is determined that the serving node of the terminal needs to be switched from a fourth relay node to a fifth relay node according to the measurement report message sent by the terminal, where the fourth relay node and the fifth relay node are both relay nodes under the first donor base station.

Preferably, the transceiver 1102 is further configured to send a second release message to the first class of relay node, send a second setup message to the second class of relay node, send a second reset message to the third class of relay node, and further instruct the terminal to reset an RLC and MAC layer protocol stack and configure the fifth relay node as the serving node in the first instruction message, when it is determined that the serving node of the terminal needs to be switched from the fourth relay node to the fifth relay node;

Preferably, the transceiver 1102 is further configured to receive a first PDCP status report sent by the terminal after sending the first indication message, where the first PDCP status report indicates a receiving condition of a PDCP data packet sent by the first donor base station, and/or the terminal sends the first PDCP status report at a first sending opportunity, where the first sending opportunity includes a predetermined first sending time period or receives a first PDCP status request message sent by the first donor base station or every time the terminal receives a first predetermined number or a first predetermined size of PDCP data packets, where the first PDCP status request message is sent by the first donor base station every time the first donor base station sends the first predetermined number or the first predetermined size of data packets;

the processor 1101 is further configured to determine, according to the receiving condition indicated by the first PDCP status report, a PDCP data packet that needs to be sent in a PDCP data recovery process, and send the PDCP data packet.

Preferably, the processor 1101 is further configured to generate and send a second PDCP status report to the terminal according to a receiving condition of a PDCP data packet sent by the terminal when a second sending opportunity and/or a wireless backhaul of the terminal needs to be changed; wherein the second sending opportunity includes a predetermined second sending time period, a second PDCP status request message sent by the receiving terminal, or a second PDCP status request message sent by the first donor base station every time the first donor base station receives a second predetermined number of PDCP data packets or a second predetermined size, where the second PDCP status request message is sent by the receiving terminal every time the second donor base station sends a second predetermined number of PDCP data packets or a second predetermined size of PDCP data packets.

Preferably, the processor 1101 is further configured to delete a data packet whose remaining time is less than a predetermined threshold or delete a data packet whose discarding timer is out of time according to the sending queue of the PDCP data packet of the terminal and the remaining time of the discarding timer of the data packet in the queue to be acknowledged after sending the first indication message; and determining the PDCP data packets which need to be sent in the PDCP data recovery process and sending the PDCP data packets according to the sending queue and the data packets left in the queue to be confirmed.

Preferably, the transceiver 1102 is further configured to send a second indication message to the terminal, where the PDCP anchor of the terminal is changed or the security parameter is updated, for indicating to start a PDCP re-establishment procedure.

Preferably, the transceiver 1102 is further configured to receive a third message sent by a sixth relay node and/or a fourth message sent by a seventh relay node, where the seventh relay node is a parent node of the sixth relay node on an upper level in the wireless backhaul path, and the third message and the fourth message are any one of a measurement report message, a load report message, a link change request message, and a link failure indication message;

the processor 1101 is further configured to send the second indication message to the terminal when it is determined that the parent node at the upper stage of the sixth relay node needs to be replaced by an eighth relay node according to the third message and/or the fourth message, where the seventh relay node is a relay node that belongs to the first donor base station and directly accesses the first donor base station, and the eighth relay node is a relay node that belongs to the second donor base station and directly accesses the second donor base station.

Preferably, the third message carries link quality information of the candidate serving relay node of the sixth relay node.

Preferably, the transceiver 1102 is further configured to send a third release message to a fourth class of relay node, a third establishment message to a fifth class of relay node, and a third reset message to a sixth class of relay node when it is determined that the parent node at the upper stage of the sixth relay node needs to be replaced by the eighth relay node;

the fourth class of relay nodes includes relay nodes deleted from the wireless backhaul path after the change, the fifth class of relay nodes includes relay nodes newly added from the wireless backhaul path after the change, and the sixth class of relay nodes includes relay nodes existing in the wireless backhaul paths before and after the change.

the processor 1101 is further configured to send the second indication message to the terminal when it is determined that the serving node of the terminal needs to be switched from the ninth relay node to the tenth relay node according to the measurement report message sent by the terminal;

the ninth relay node is a relay node belonging to the first donor base station, and the tenth relay node is a relay node belonging to the second donor base station.

Preferably, the transceiver 1102 is further configured to send a fourth release message to a fourth class of relay node, send a fourth setup message to a fifth class of relay node, send a fourth reset message to a sixth class of relay node, and further instruct the terminal to reset RLC and MAC protocol stacks and configure the tenth relay node as the serving node in the second instruction message, when it is determined that the serving node of the terminal needs to be switched from the ninth relay node to the tenth relay node;

Preferably, the transceiver 1102 is further configured to receive, after sending the second indication message, a third PDCP status report sent by the terminal, where the third PDCP status report indicates a reception condition of a PDCP data packet sent by the first donor base station, and the third PDCP status report includes a status report generated by the terminal after receiving the second indication message, and/or the terminal sends the status report at a first sending opportunity, where the first sending opportunity includes a predetermined first sending time period or a receiving time of a first PDCP status request message sent by the first donor base station or every time the terminal receives a first predetermined number or a first predetermined size of PDCP data packets, where the first PDCP status request message is sent by the first donor base station every time the first donor base station sends the first predetermined number or the first predetermined size of data packets;

the processor 1101 is further configured to determine PDCP data packets that need to be sent in a PDCP re-establishment procedure according to the receiving condition indicated by the third PDCP status report.

Preferably, the processor 1101 is further configured to, in a case that a PDCP anchor point of the terminal is changed, forward the determined PDCP data packet that needs to be sent in the PDCP re-establishment procedure and the sequence number SN information thereof to a second donor base station after determining the PDCP data packet that needs to be sent in the PDCP re-establishment procedure, where the second donor base station is the donor base station where the changed PDCP anchor point is located.

Preferably, the processor 1101 is further configured to generate and send a fourth PDCP status report to the terminal according to a receiving condition of a PDCP data packet sent by the terminal when a second sending opportunity and/or a wireless backhaul of the terminal needs to be changed; wherein the second sending opportunity includes a predetermined second sending time period, a second PDCP status request message sent by the receiving terminal, or a second PDCP status request message sent by the first donor base station every time the first donor base station receives a second predetermined number of PDCP data packets or a second predetermined size, where the second PDCP status request message is sent by the receiving terminal every time the second donor base station sends a second predetermined number of PDCP data packets or a second predetermined size of PDCP data packets.

Preferably, the processor 1101 is further configured to delete a data packet whose remaining time is less than a predetermined threshold or delete a data packet whose discarding timer is out of time according to the sending queue of the PDCP data packet of the terminal and the remaining time of the discarding timer of the data packet in the queue to be acknowledged after sending the second indication message; and determining the PDCP data packets which need to be sent in the PDCP reconstruction process according to the sending queue and the data packets left in the queue to be confirmed.

Referring to fig. 12, another structure of the first donor base station 120 is provided in the embodiments of the present invention, as shown in fig. 7, the first donor base station 120 includes:

a sending processing unit 121, configured to send, through the transceiver, an indication message to the terminal for indicating to start a packet data convergence protocol PDCP data recovery procedure or a PDCP re-establishment procedure when a wireless backhaul of the terminal needs to be changed.

Optionally, the sending processing unit 121 is specifically configured to send, to the terminal, a first indication message for indicating to start a PDCP data recovery process when the PDCP anchor of the terminal is not changed and the security parameter is not updated.

Optionally, the sending processing unit 121 includes:

a first receiving unit, configured to receive a first message sent by a first relay node and/or a second message sent by a second relay node, where the second relay node is a parent node of the first relay node on an upper level in the wireless backhaul path, and the first message and the second message are any one of a measurement report message, a load report message, a link change request message, and a link failure indication message;

a first sending unit, configured to send the first indication message to the terminal when it is determined that a parent node of a previous stage of the first relay node needs to be replaced by a third relay node according to the first message and/or the second message, where the second relay node and the third relay node are both relay nodes belonging to the first donor base station.

Optionally, the first message carries link quality information of a candidate serving relay node of the first relay node.

Optionally, the first donor base station further includes:

the first configuration unit is used for sending a first release message to the first class of relay nodes, sending a first establishment message to the second class of relay nodes and sending a first reset message to the third class of relay nodes when the fact that the superior father node of the first relay node needs to be replaced by the third relay node is determined;

Optionally, the sending processing unit 121 includes:

a second receiving unit, configured to receive a measurement report message sent by the terminal;

a second sending unit, configured to send the first indication message to the terminal when it is determined that the serving node of the terminal needs to be switched from a fourth relay node to a fifth relay node according to the measurement report message sent by the terminal, where the fourth relay node and the fifth relay node are both relay nodes under the first donor base station.

Optionally, the first donor base station further includes:

a second configuration unit, configured to send a second release message to the first class relay node, send a second setup message to the second class relay node, send a second reset message to the third class relay node, and further instruct the terminal to reset RLC and MAC layer protocol stacks in the first instruction message and configure the fifth relay node as a serving node when it is determined that the serving node of the terminal needs to be switched from the fourth relay node to the fifth relay node;

Optionally, the first donor base station further includes:

a third receiving unit, configured to receive, after sending the first indication message, a first PDCP status report sent by the terminal, where the first PDCP status report indicates a reception condition of PDCP data packets sent by the first donor base station, and the first PDCP status report includes that the terminal sent after receiving the first indication message, and/or that the terminal sent at a first sending opportunity, where the first sending opportunity includes a predetermined first sending time period or receives a first PDCP status request message sent by the first donor base station or every time the terminal receives a first predetermined number or a first predetermined size of PDCP data packets, where the first PDCP status request message is sent by the first donor base station every time the first donor base station sends the first predetermined number or first predetermined size of PDCP data packets;

and a third sending unit, configured to determine, according to the receiving condition indicated by the first PDCP status report, a PDCP data packet that needs to be sent in a PDCP data recovery process, and send the PDCP data packet.

Optionally, the first donor base station further includes:

a fourth sending unit, configured to generate and send a second PDCP status report to the terminal according to a receiving condition of a PDCP data packet sent by the terminal when a second sending opportunity and/or a wireless backhaul of the terminal needs to be changed; wherein the second sending opportunity includes a predetermined second sending time period, a second PDCP status request message sent by the receiving terminal, or a second PDCP status request message sent by the first donor base station every time the first donor base station receives a second predetermined number of PDCP data packets or a second predetermined size, where the second PDCP status request message is sent by the receiving terminal every time the second donor base station sends a second predetermined number of PDCP data packets or a second predetermined size of PDCP data packets.

Optionally, the first donor base station further includes:

a first data sending unit, configured to delete, after sending the first indication message, a data packet whose remaining time is less than a predetermined threshold or a data packet whose discard timer is overtime, according to a sending queue of PDCP data packets of the terminal and remaining time of a discard timer of data packets in a queue to be acknowledged; and determining the PDCP data packets which need to be sent in the PDCP data recovery process and sending the PDCP data packets according to the sending queue and the data packets left in the queue to be confirmed.

Optionally, the sending processing unit is specifically configured to send, to the terminal, a second indication message for indicating to start a PDCP reestablishment procedure when a PDCP anchor of the terminal is changed or a security parameter is updated.

Optionally, the sending processing unit includes:

a fourth receiving unit, configured to receive a third message sent by a sixth relay node and/or a fourth message sent by a seventh relay node, where the seventh relay node is a parent node of the sixth relay node on an upper level in the wireless backhaul path, and the third message and the fourth message are any one of a measurement report message, a load report message, a link change request message, and a link failure indication message;

a fifth sending unit, configured to send the second indication message to the terminal when it is determined that a parent node at a higher level of the sixth relay node needs to be replaced by an eighth relay node according to the third message and/or the fourth message, where the seventh relay node is a relay node that belongs to the first donor base station and directly accesses the first donor base station, and the eighth relay node is a relay node that belongs to the second donor base station and directly accesses the second donor base station.

Optionally, the third message carries link quality information of a candidate serving relay node of the sixth relay node.

Optionally, the first donor base station further includes:

a third configuration unit, configured to send a third release message to a fourth class of relay nodes, send a third establishment message to a fifth class of relay nodes, and send a third reset message to the sixth class of relay nodes when it is determined that a parent node at a previous stage of the sixth relay node needs to be replaced with an eighth relay node;

Optionally, the sending processing unit includes:

a fifth receiving unit, configured to receive a measurement report message sent by the terminal;

a sixth sending unit, configured to send the second indication message to the terminal when determining that the serving node of the terminal needs to be switched from the ninth relay node to the tenth relay node according to the measurement report message sent by the terminal;

Optionally, the first donor base station further includes:

a fourth configuration unit, configured to send a fourth release message to a fourth class of relay node, send a fourth establishment message to a fifth class of relay node, send a fourth reset message to a sixth class of relay node, and further instruct the terminal to reset an RLC and MAC protocol stack and configure the tenth relay node as the service node in the second instruction message, when it is determined that the service node of the terminal needs to be switched from the ninth relay node to the tenth relay node;

Optionally, the first donor base station further includes:

a sixth receiving unit, configured to receive, after sending the second indication message, a third PDCP status report sent by the terminal, where the third PDCP status report indicates a reception condition of PDCP data packets sent by the first donor base station, and the third PDCP status report includes a status generated by the terminal after receiving the second indication message, and/or is sent by the terminal at a first sending opportunity, where the first sending opportunity includes a predetermined first sending time period or a first PDCP status request message sent by the first donor base station or every time the terminal receives a first predetermined number or a first predetermined size of PDCP data packets, where the first PDCP status request message is sent by the first donor base station every time the first donor base station sends a first predetermined number or a first predetermined size of PDCP data packets;

a first data determining unit, configured to determine, according to the receiving condition indicated by the third PDCP status report, a PDCP data packet that needs to be sent in a PDCP reestablishment process.

Optionally, the first donor base station further includes:

the first forwarding unit is configured to forward, after determining a PDCP data packet that needs to be sent in a PDCP reestablishment process, the determined PDCP data packet that needs to be sent in the PDCP reestablishment process and sequence number SN information thereof to a second donor base station in a case that a PDCP anchor of the terminal is changed, where the second donor base station is a donor base station where the changed PDCP anchor is located.

Optionally, the first donor base station further includes:

a seventh sending unit, configured to generate and send a fourth PDCP status report to the terminal according to a receiving condition of a PDCP data packet sent by the terminal when a second sending opportunity and/or a wireless backhaul of the terminal needs to be changed; wherein the second sending opportunity includes a predetermined second sending time period, a second PDCP status request message sent by the receiving terminal, or a second PDCP status request message sent by the first donor base station every time the first donor base station receives a second predetermined number of PDCP data packets or a second predetermined size, where the second PDCP status request message is sent by the receiving terminal every time the second donor base station sends a second predetermined number of PDCP data packets or a second predetermined size of PDCP data packets.

Optionally, the first donor base station further includes:

a second data determining unit, configured to delete, after sending the second indication message, a data packet whose remaining time is less than a predetermined threshold or a data packet whose discard timer is overtime, according to a sending queue of PDCP data packets of the terminal and the remaining time of the discard timer of the data packet in the queue to be confirmed; and determining the PDCP data packets which need to be sent in the PDCP reconstruction process according to the sending queue and the data packets left in the queue to be confirmed.

Optionally, the first donor base station further includes:

and the second forwarding unit is used for forwarding the determined PDCP data packet which needs to be sent in the PDCP rebuilding process and the sequence number SN information thereof to a second donor base station under the condition that the PDCP anchor point of the terminal is changed, wherein the second donor base station is the donor base station where the changed PDCP anchor point is located.

Referring to fig. 13, a schematic structural diagram of a terminal according to an embodiment of the present invention is shown, where the terminal 800 includes: a processor 1301, a transceiver 1302, a memory 1303, a user interface 1304, and a bus interface, wherein:

in this embodiment of the present invention, the terminal 1300 further includes: a computer program stored on the memory 1303 and executable on the processor 1301.

The transceiver 1302 is configured to receive an indication message sent by the first donor base station to indicate to start a packet data convergence protocol PDCP data recovery procedure or a PDCP re-establishment procedure.

Preferably, the transceiver is further configured to receive a first indication message sent by the first donor base station for indicating to start a PDCP data recovery procedure.

Preferably, the first indication message is further configured to instruct the terminal to reset RLC and MAC layer protocol stacks and configure a fifth relay node as a serving node, and the processor is configured to read a program in a memory and execute the following processes: and resetting the RLC and the MAC layer protocol stack and configuring a service node as the fifth relay node according to the first indication message.

In fig. 13, the bus architecture may include any number of interconnected buses and bridges, with one or more processors represented by processor 1301 and various circuits of memory represented by memory 1303 linked together. The bus architecture may also link together various other circuits such as peripherals, voltage regulators, power management circuits, and the like, which are well known in the art, and therefore, will not be described any further herein. The bus interface provides an interface. The transceiver 1302 may be a plurality of elements including a transmitter and a receiver that provide a means for communicating with various other apparatus over a transmission medium. The user interface 1304 may also be an interface capable of interfacing with a desired device for different user devices, including but not limited to a keypad, display, speaker, microphone, joystick, etc.

The processor 1301 is responsible for managing a bus architecture and general processing, and the memory 1303 may store data used by the processor 1301 in performing operations.

Preferably, the processor 1301 is further configured to generate and send a first PDCP status report to the first donor base station according to a receiving condition of a PDCP data packet sent by the first donor base station at a first sending opportunity and/or when the first indication message is received; the first sending opportunity comprises a preset first sending time period or a first PDCP state request message sent by a first donor base station or the first PDCP state request message is sent by the first donor base station after the first donor base station sends the PDCP data packets of the first preset number or the first preset size every time the terminal receives the PDCP data packets of the first preset number or the first preset size.

Preferably, the transceiver 1302 is further configured to receive a second PDCP status report sent by the first donor base station after receiving the first indication message, the second PDCP status report indicates a reception condition of a PDCP packet transmitted by the terminal, the second PDCP status report includes a report that is transmitted when the first donor base station needs to change a radio backhaul path of the terminal, and/or the first donor base station transmits at a second transmission opportunity, where the second transmission opportunity includes a predetermined second transmission time period or a second PDCP status request message transmitted by the receiving terminal or every time the first donor base station receives a second predetermined number of PDCP data packets or a second predetermined size, wherein the second PDCP status request message is transmitted by the terminal every time a second predetermined number or size of PDCP data packets is transmitted; and determining the PDCP data packets which need to be sent in the PDCP data recovery process and sending the PDCP data packets according to the receiving condition indicated by the second PDCP status report.

Preferably, the transceiver 1302 is further configured to delete a data packet whose remaining time is less than a predetermined threshold or delete a data packet whose discarding timer is out of time according to the sending queue of the PDCP data packet of the first donor base station and the remaining time of the discarding timer of the data packet in the queue to be acknowledged after receiving the first indication message; and determining the PDCP data packets which need to be sent in the PDCP data recovery process and sending the PDCP data packets according to the sending queue and the data packets left in the queue to be confirmed.

Preferably, the transceiver 1302 is further configured to receive a second indication message sent by the first donor base station for indicating to start the PDCP re-establishment procedure.

Preferably, the processor 1301 is further configured to reset the RLC and MAC layer protocol stacks according to the second indication message and start a PDCP reestablishment process after receiving the second indication message.

Preferably, the second indication message is further configured to instruct the terminal to reset the RLC and MAC layer protocol stacks and configure a tenth relay node as a service node, and the processor 1301 is further configured to reset the RLC and MAC layer protocol stacks and configure the service node as the tenth relay node according to the second indication message, and start a PDCP re-establishment procedure.

Preferably, the processor 1301 is further configured to generate and send a third PDCP status report to the first donor base station according to a receiving condition of a PDCP data packet sent by the first donor base station at a first sending opportunity and/or when the second indication message is received after the second indication message is received; the first sending opportunity comprises a preset first sending time period or a first PDCP state request message sent by a first donor base station or the first PDCP state request message is sent by the first donor base station after the first donor base station sends the PDCP data packets of the first preset number or the first preset size every time the terminal receives the PDCP data packets of the first preset number or the first preset size.

Preferably, the processor 1301 is further configured to receive a fourth PDCP status report sent by the first donor base station after receiving the second indication message, the fourth PDCP status report indicates a reception condition of a PDCP packet transmitted by the terminal, the fourth PDCP status report includes information transmitted when the first donor base station needs to change a radio backhaul of the terminal, and/or the first donor base station transmits at a second transmission opportunity, where the second transmission opportunity includes a predetermined second transmission time period or a second PDCP status request message transmitted by the receiving terminal or every time the first donor base station receives a second predetermined number of PDCP data packets or a second predetermined size, wherein the second PDCP status request message is transmitted by the terminal every time a second predetermined number or size of PDCP data packets is transmitted; and determining the PDCP data packets which need to be sent in the PDCP rebuilding process and sending the PDCP data packets according to the receiving condition indicated by the fourth PDCP status report.

Preferably, the transceiver 1302 is further configured to delete a data packet whose remaining time is less than a predetermined threshold or delete a data packet whose discarding timer is out of time according to the sending queue of the PDCP data packet of the first donor base station and the remaining time of the discarding timer of the data packet in the queue to be acknowledged after receiving the second indication message; and determining the PDCP data packets which need to be sent in the PDCP reconstruction process and sending the PDCP data packets according to the sending queue and the data packets left in the queue to be confirmed.

Referring to fig. 14, an embodiment of the present invention provides another terminal 140, including:

a sending processing unit 141, configured to receive an indication message sent by the first donor base station and used to indicate to start a packet data convergence protocol PDCP data recovery procedure or a PDCP re-establishment procedure.

Optionally, the sending processing unit is further configured to receive a first indication message sent by the first donor base station and used for indicating to start a PDCP data recovery procedure.

Optionally, the first indication message is further configured to indicate the terminal to reset RLC and MAC layer protocol stacks and configure a fifth relay node as a serving node, where the terminal further includes:

and the resetting unit is used for resetting the RLC and the MAC layer protocol stack and configuring a service node as the fifth relay node according to the first indication message.

Optionally, the terminal further includes:

a first report sending unit, configured to generate and send a first PDCP status report to the first donor base station according to a receiving condition of a PDCP data packet sent by the first donor base station at a first sending opportunity and/or when the first indication message is received; the first sending opportunity comprises a preset first sending time period or a first PDCP state request message sent by a first donor base station or the first PDCP state request message is sent by the first donor base station after the first donor base station sends the PDCP data packets of the first preset number or the first preset size every time the terminal receives the PDCP data packets of the first preset number or the first preset size.

Optionally, the terminal further includes:

a first report receiving unit, configured to receive, after receiving the first indication message, a second PDCP status report sent by a first donor base station, where the second PDCP status report indicates a reception situation of a PDCP data packet sent by the terminal, and the second PDCP status report includes a second PDCP status request message sent by the first donor base station when the first donor base station needs to change a wireless backhaul path of the terminal, and/or the first donor base station sends the second PDCP status report at a second sending opportunity, where the second sending opportunity includes a predetermined second sending time period or a second PDCP status request message sent by the receiving terminal or every time the first donor base station receives a second predetermined number of PDCP data packets or a second predetermined size, where the second PDCP status request message is sent by the terminal after every time the second predetermined number of PDCP data packets or the second predetermined size data packets are sent;

and the first data recovery unit is used for determining the PDCP data packets which need to be sent in the PDCP data recovery process and sending the PDCP data packets according to the receiving condition indicated by the second PDCP status report.

Optionally, the terminal further includes:

a second data recovery unit, configured to delete, after receiving the first indication message, a data packet whose remaining time is less than a predetermined threshold or a data packet whose discard timer is out of time according to a transmission queue of PDCP data packets of the first donor base station and remaining time of the discard timer of the data packet in the queue to be acknowledged; and determining the PDCP data packets which need to be sent in the PDCP data recovery process and sending the PDCP data packets according to the sending queue and the data packets left in the queue to be confirmed.

Optionally, the sending processing unit is further configured to receive a second indication message sent by the first donor base station and used for indicating to start a PDCP re-establishment procedure.

Optionally, the terminal further includes:

and the first reestablishing unit is used for resetting the RLC and the MAC layer protocol stack and starting the PDCP reestablishing process according to the second indication message after receiving the second indication message.

Optionally, the second indication message is further configured to indicate the terminal to reset RLC and MAC layer protocol stacks and configure a tenth relay node as a serving node, where the terminal further includes:

and the second reconstruction unit is used for resetting an RLC and MAC layer protocol stack, configuring a service node as the tenth relay node and starting a PDCP reconstruction process according to the second indication message.

Optionally, the terminal further includes:

a second report sending unit, configured to generate and send a third PDCP status report to the first donor base station according to a receiving condition of a PDCP data packet sent by the first donor base station at a first sending opportunity and/or when the second indication message is received after the second indication message is received; the first sending opportunity comprises a preset first sending time period or a first PDCP state request message sent by a first donor base station or the first PDCP state request message is sent by the first donor base station after the first donor base station sends the PDCP data packets of the first preset number or the first preset size every time the terminal receives the PDCP data packets of the first preset number or the first preset size.

Optionally, the terminal further includes:

a second report receiving unit, configured to receive, after receiving the second indication message, a fourth PDCP status report sent by the first donor base station, where the fourth PDCP status report indicates a reception situation of a PDCP data packet sent by the terminal, and the fourth PDCP status report includes a status that the first donor base station needs to change a wireless backhaul path of the terminal, and/or the first donor base station sends at a second sending opportunity, where the second sending opportunity includes a predetermined second sending time period or a second PDCP status request message sent by the receiving terminal or every time the first donor base station receives a second predetermined number of PDCP data packets or a second predetermined size, where the second PDCP status request message is sent by the terminal after every time the second predetermined number of PDCP data packets or the second predetermined size data packets are sent;

and a first reestablishment sending unit, configured to determine, according to the receiving condition indicated by the fourth PDCP status report, a PDCP data packet that needs to be sent in a PDCP reestablishment process, and send the PDCP data packet.

Optionally, the terminal further includes:

a second reconfiguration transmitting unit, configured to delete, after receiving the second indication message, a packet whose remaining time is less than a predetermined threshold or a packet whose discard timer is out of time according to a transmission queue of PDCP packets of the first donor base station and remaining time of a discard timer of packets in a queue to be confirmed; and determining the PDCP data packets which need to be sent in the PDCP reconstruction process and sending the PDCP data packets according to the sending queue and the data packets left in the queue to be confirmed.

Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present invention.

It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.

In the embodiments provided in the present application, it should be understood that the disclosed apparatus and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.

The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment of the present invention.

In addition, functional units in the embodiments of the present invention may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit.

The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present invention may be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the data processing method of the wireless backhaul path according to the embodiments of the present invention. And the aforementioned storage medium includes: various media capable of storing program codes, such as a U disk, a removable hard disk, a ROM, a RAM, a magnetic disk, or an optical disk.

The above description is only for the specific embodiments of the present invention, but the scope of the present invention is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present invention, and all the changes or substitutions should be covered within the scope of the present invention. Therefore, the protection scope of the present invention shall be subject to the protection scope of the claims.

Claims

1. A data processing method of a wireless backhaul path is applied to a first donor base station, and the method comprises the following steps:

2. The method of claim 1, wherein the step of sending an indication message to the terminal for indicating initiation of a Packet Data Convergence Protocol (PDCP) data recovery procedure or a PDCP re-establishment procedure comprises:

and the first donor base station sends a first indication message for indicating to start a PDCP data recovery process to the terminal under the condition that the PDCP anchor point of the terminal is not changed and the security parameters are not updated.

3. The method of claim 2, wherein the step of the first donor base station sending a first indication message to the terminal for indicating to start PDCP data recovery procedure when the PDCP anchor of the terminal is not changed and the security parameters are not updated comprises:

the first donor base station receives a first message sent by a first relay node and/or a second message sent by a second relay node, the second relay node is an upper-level father node of the first relay node in the wireless backhaul path, and the first message and the second message are any one of a measurement report message, a load report message, a link change request message and a link failure indication message;

and the first donor base station sends the first indication message to the terminal when determining that the parent node at the upper stage of the first relay node needs to be replaced by a third relay node according to the first message and/or the second message, wherein the second relay node and the third relay node are both relay nodes belonging to the first donor base station.

4. The method of claim 3, wherein the first message carries link quality information of candidate serving relay nodes of the first relay node.

5. The method of claim 3, wherein upon determining that a change of a parent node of a previous level of the first relay node to a third relay node is required, the method further comprises:

sending a first release message to a first class of relay nodes, sending a first establishment message to a second class of relay nodes, and sending a first reset message to a third class of relay nodes;

6. The method of claim 2, wherein the step of the first donor base station sending a first indication message to the terminal for indicating to start PDCP data recovery procedure when the PDCP anchor of the terminal is not changed and the security parameters are not updated comprises:

the first donor base station receives a measurement report message sent by the terminal;

and the first donor base station sends the first indication message to the terminal when determining that the service node of the terminal needs to be switched from a fourth relay node to a fifth relay node according to the measurement report message sent by the terminal, wherein the fourth relay node and the fifth relay node are both relay nodes under the first donor base station.

7. The method of claim 6, wherein upon determining that the serving node for the terminal needs to be handed over from the fourth relay node to a fifth relay node, the method further comprises:

sending a second release message to the first class of relay nodes, sending a second establishment message to the second class of relay nodes, sending a second reset message to the third class of relay nodes, further instructing the terminal to reset an RLC and MAC layer protocol stack in the first instruction message, and configuring a fifth relay node as a service node;

8. The method according to any of claims 2 to 7, wherein after sending the first indication message, the method further comprises:

receiving a first PDCP status report sent by the terminal, where the first PDCP status report indicates a reception condition of PDCP data packets sent by the first donor base station, and the first PDCP status report includes a first PDCP status request message sent by the terminal after receiving the first indication message, and/or the terminal sends the first PDCP status report at a first sending opportunity, where the first sending opportunity includes a predetermined first sending time period or a first PDCP status request message sent by the first donor base station or every time the terminal receives a first predetermined number of PDCP data packets or a first predetermined size, where the first PDCP status request message is sent by the first donor base station every time the first predetermined number of PDCP data packets or the first predetermined size is sent;

and determining the PDCP data packets which need to be sent in the PDCP data recovery process and sending the PDCP data packets according to the receiving condition indicated by the first PDCP status report.

9. The method of claim 8, further comprising:

generating and sending a second PDCP status report to the terminal according to the receiving condition of a PDCP data packet sent by the terminal when a second sending opportunity and/or a wireless backhaul path of the terminal needs to be changed; wherein the second sending opportunity includes a predetermined second sending time period, a second PDCP status request message sent by the receiving terminal, or a second PDCP status request message sent by the first donor base station every time the first donor base station receives a second predetermined number of PDCP data packets or a second predetermined size, where the second PDCP status request message is sent by the receiving terminal every time the second donor base station sends a second predetermined number of PDCP data packets or a second predetermined size of PDCP data packets.

10. The method according to any of claims 2 to 7, wherein after sending the first indication message, the method further comprises:

deleting the data packets with the remaining time less than a preset threshold or deleting the data packets with overtime discarding timer according to the sending queue of the PDCP data packets of the terminal and the remaining time of the discarding timer of the data packets in the queue to be confirmed;

and determining the PDCP data packets which need to be sent in the PDCP data recovery process and sending the PDCP data packets according to the sending queue and the data packets left in the queue to be confirmed.

11. The method of claim 1, wherein the step of sending an indication message to the terminal for indicating initiation of a Packet Data Convergence Protocol (PDCP) data recovery procedure or a PDCP re-establishment procedure comprises:

and the first donor base station sends a second indication message for indicating to start a PDCP rebuilding process to the terminal under the condition that a PDCP anchor point of the terminal is changed or the security parameter is updated.

12. The method of claim 11, wherein the step of the first donor base station sending a second indication message to the terminal for indicating to start PDCP re-establishment procedure when the PDCP anchor of the terminal is changed or the security parameter is updated comprises:

the first donor base station receives a third message sent by a sixth relay node and/or a fourth message sent by a seventh relay node, the seventh relay node is a parent node of the sixth relay node on the upper stage in the wireless backhaul path, and the third message and the fourth message are any one of a measurement report message, a load report message, a link change request message and a link failure indication message;

and the first donor base station sends the second indication message to the terminal when determining that the parent node at the upper stage of the sixth relay node needs to be replaced by an eighth relay node according to the third message and/or the fourth message, wherein the seventh relay node is a relay node which belongs to the first donor base station and is directly accessed to the first donor base station, and the eighth relay node is a relay node which belongs to the second donor base station and is directly accessed to the second donor base station.

13. The method of claim 12, wherein the third message carries link quality information of candidate serving relay nodes of the sixth relay node.

14. The method of claim 12, wherein upon determining that the parent node of the sixth relay node is required to be replaced with the parent node of the eighth relay node, the method further comprises:

sending a third release message to the fourth class of relay nodes, sending a third establishment message to the fifth class of relay nodes, and sending a third reset message to the sixth class of relay nodes;

15. The method of claim 11, wherein the step of the first donor base station sending a second indication message to the terminal for indicating to start PDCP re-establishment procedure when the PDCP anchor of the terminal is changed or the security parameter is updated comprises:

the first donor base station sends the second indication message to the terminal when determining that the service node of the terminal needs to be switched from a ninth relay node to a tenth relay node according to the measurement report message sent by the terminal;

16. The method of claim 15, wherein upon determining that the serving node for the terminal needs to be handed over from the ninth relay node to a tenth relay node, the method further comprises:

sending a fourth release message to a fourth class of relay nodes, sending a fourth establishment message to a fifth class of relay nodes, sending a fourth reset message to a sixth class of relay nodes, and further instructing the terminal to reset the RLC and MAC protocol stacks and configuring a tenth relay node as a service node in the second indication message;

17. The method according to any of claims 11 to 16, wherein after sending the second indication message, the method further comprises:

receiving a third PDCP status report sent by the terminal, where the third PDCP status report indicates a reception condition of PDCP data packets sent by the first donor base station, and the third PDCP status report includes a first PDCP status request message sent by the first donor base station or every time the terminal receives a first predetermined number of PDCP data packets or a first predetermined size, where the first PDCP status request message is sent by the first donor base station every time the first predetermined number of PDCP data packets or the first predetermined size is sent, and/or is sent by the terminal at a first sending opportunity, where the first PDCP status report includes a first predetermined sending time period or a first PDCP status request message sent by the terminal after the terminal receives the second predetermined number of PDCP data packets or the first predetermined size;

and determining the PDCP data packets which need to be sent in the PDCP rebuilding process according to the receiving condition indicated by the third PDCP status report.

18. The method as claimed in claim 17, wherein after the step of determining the PDCP data packet to be transmitted in the PDCP re-establishment procedure in case that the PDCP anchor of the terminal is changed, the method further comprises:

and forwarding the determined PDCP data packet which needs to be sent in the PDCP rebuilding process and the sequence number SN information thereof to a second donor base station, wherein the second donor base station is the donor base station where the changed PDCP anchor point is located.

19. The method of claim 17, further comprising:

generating and sending a fourth PDCP status report to the terminal according to the receiving condition of a PDCP data packet sent by the terminal when a second sending opportunity and/or a wireless backhaul of the terminal needs to be replaced; wherein the second sending opportunity includes a predetermined second sending time period, a second PDCP status request message sent by the receiving terminal, or a second PDCP status request message sent by the first donor base station every time the first donor base station receives a second predetermined number of PDCP data packets or a second predetermined size, where the second PDCP status request message is sent by the receiving terminal every time the second donor base station sends a second predetermined number of PDCP data packets or a second predetermined size of PDCP data packets.

20. The method according to any of claims 11 to 16, wherein after sending the second indication message, the method further comprises:

and determining the PDCP data packets which need to be sent in the PDCP reconstruction process according to the sending queue and the data packets left in the queue to be confirmed.

21. The method as claimed in claim 20, wherein after the step of determining the PDCP data packet to be transmitted in the PDCP re-establishment procedure in case that the PDCP anchor of the terminal is changed, the method further comprises:

22. A data processing method of a wireless backhaul path is applied to a terminal, and is characterized by comprising the following steps:

the terminal receives an indication message which is sent by the first donor base station and used for indicating the starting of a Packet Data Convergence Protocol (PDCP) data recovery process or a PDCP reconstruction process.

23. The method of claim 22, wherein receiving an indication message sent by the first donor base station to indicate initiation of a packet data convergence protocol PDCP data recovery procedure or a PDCP re-establishment procedure comprises:

the terminal receives a first indication message sent by a first donor base station and used for indicating the starting of a PDCP data recovery process.

24. The method of claim 23, wherein the first indication message is further used for instructing the terminal to reset RLC and MAC layer protocol stacks and configure a fifth relay node as a serving node, and wherein the method further comprises:

and resetting the RLC and the MAC layer protocol stack and configuring a service node as the fifth relay node according to the first indication message.

25. The method of claim 23, further comprising:

generating and sending a first PDCP status report to the first donor base station according to the receiving condition of the PDCP data packet sent by the first donor base station at a first sending opportunity and/or when the first indication message is received; the first sending opportunity comprises a preset first sending time period or a first PDCP state request message sent by a first donor base station or the first PDCP state request message is sent by the first donor base station after the first donor base station sends the PDCP data packets of the first preset number or the first preset size every time the terminal receives the PDCP data packets of the first preset number or the first preset size.

26. The method of claim 25, wherein after receiving the first indication message, the method further comprises:

receiving a second PDCP status report sent by a first donor base station, where the second PDCP status report indicates a receiving condition of a PDCP data packet sent by the terminal, and the second PDCP status report includes a second sending opportunity sent by the first donor base station when the first donor base station needs to change a wireless backhaul path of the terminal, and/or the first donor base station sends the second PDCP status report at a second sending opportunity, where the second sending opportunity includes a predetermined second sending time period, or a second PDCP status request message sent by a receiving terminal, or every time the first donor base station receives a second predetermined number of PDCP data packets or a second predetermined size, where the second PDCP status request message is sent by the terminal after every sending the second predetermined number of PDCP data packets or the second predetermined size;

and determining the PDCP data packets which need to be sent in the PDCP data recovery process and sending the PDCP data packets according to the receiving condition indicated by the second PDCP status report.

27. The method of claim 23, wherein after receiving the first indication message, the method further comprises:

deleting the data packets with the remaining time less than a preset threshold or deleting the data packets with overtime discarding timer according to the sending queue of the PDCP data packets of the first donor base station and the remaining time of the discarding timer of the data packets in the queue to be confirmed;

28. The method of claim 22, wherein receiving an indication message sent by the first donor base station to indicate initiation of a packet data convergence protocol PDCP data recovery procedure or a PDCP re-establishment procedure comprises:

and the terminal receives a second indication message which is sent by the first donor base station and used for indicating the starting of the PDCP rebuilding process.

29. The method of claim 28, wherein after receiving the second indication message, the method further comprises:

and resetting the RLC and the MAC layer protocol stack according to the second indication message, and starting a PDCP reconstruction process.

30. The method of claim 28, wherein the second indication message is further used for instructing the terminal to reset RLC and MAC layer protocol stacks and configure a tenth relay node as a serving node, and wherein the method further comprises:

and resetting an RLC and MAC layer protocol stack, configuring a service node as the tenth relay node and starting a PDCP reconstruction process according to the second indication message.

31. The method according to any of claims 28 to 30, wherein after receiving the second indication message, the method further comprises:

generating and sending a third PDCP status report to the first donor base station according to the receiving condition of the PDCP data packet sent by the first donor base station at the first sending opportunity and/or when the second indication message is received; the first sending opportunity comprises a preset first sending time period or a first PDCP state request message sent by a first donor base station or the first PDCP state request message is sent by the first donor base station after the first donor base station sends the PDCP data packets of the first preset number or the first preset size every time the terminal receives the PDCP data packets of the first preset number or the first preset size.

32. The method of claim 31, wherein after receiving the second indication message, the method further comprises:

receiving a fourth PDCP status report sent by a first donor base station, where the fourth PDCP status report indicates a reception condition of a PDCP data packet sent by the terminal, and the fourth PDCP status report includes a second sending opportunity sent by the first donor base station when the first donor base station needs to change a radio backhaul path of the terminal, and/or the first donor base station sends the second sending opportunity, where the second sending opportunity includes a predetermined second sending time period, or a second PDCP status request message sent by a receiving terminal, or a second PDCP status request message sent by the first donor base station every time the first donor base station receives a second predetermined number of PDCP data packets or a second predetermined size, where the second PDCP status request message is sent by the terminal every time the second predetermined number of PDCP data packets or the second predetermined size of PDCP data packets is sent;

and determining the PDCP data packets which need to be sent in the PDCP rebuilding process and sending the PDCP data packets according to the receiving condition indicated by the fourth PDCP status report.

33. The method according to any of claims 28 to 30, wherein after receiving the second indication message, the method further comprises:

and determining the PDCP data packets which need to be sent in the PDCP reconstruction process and sending the PDCP data packets according to the sending queue and the data packets left in the queue to be confirmed.

34. A first donor base station, comprising: a transceiver, a memory, a processor, and a program stored on the memory and executable on the processor;

35. The first donor base station of claim 34, wherein the transceiver is further configured to send a first indication message to the terminal indicating initiation of a PDCP data recovery procedure if the PDCP anchor of the terminal has not changed and security parameters have not been updated.

36. The first donor base station of claim 35,

the transceiver is further configured to receive, after sending the first indication message, a first PDCP status report sent by the terminal, where the first PDCP status report indicates a reception condition of PDCP data packets sent by the first donor base station, and the first PDCP status report includes that the terminal sent after receiving the first indication message, and/or that the terminal sent at a first sending opportunity, where the first sending opportunity includes a predetermined first sending time period or receives a first PDCP status request message sent by the first donor base station or every time the terminal receives a first predetermined number or a first predetermined size of PDCP data packets, where the first PDCP status request message is sent by the first donor base station every time the first donor base station sends a first predetermined number or a first predetermined size of PDCP data packets;

the processor is further configured to determine, according to the receiving condition indicated by the first PDCP status report, a PDCP data packet that needs to be sent in a PDCP data recovery process, and send the PDCP data packet.

37. The first donor base station of claim 35,

the processor is further configured to delete a data packet whose remaining time is less than a predetermined threshold or delete a data packet whose discard timer is overtime according to a transmission queue of the PDCP data packet of the terminal and the remaining time of the discard timer of the data packet in the queue to be acknowledged after the first indication message is transmitted; and determining the PDCP data packets which need to be sent in the PDCP data recovery process and sending the PDCP data packets according to the sending queue and the data packets left in the queue to be confirmed.

38. The first donor base station of claim 34,

the transceiver is further configured to send a second indication message to the terminal for indicating to start a PDCP reestablishment procedure when a PDCP anchor of the terminal is changed or a security parameter is updated.

39. The first donor base station of claim 38,

the transceiver is further configured to receive, after sending the second indication message, a third PDCP status report sent by the terminal, where the third PDCP status report indicates a reception condition of PDCP data packets sent by the first donor base station, and the third PDCP status report includes a status generated by the terminal after receiving the second indication message, and/or is sent by the terminal at a first sending opportunity, where the first sending opportunity includes a predetermined first sending time period or a first PDCP status request message sent by the first donor base station or every time the terminal receives a first predetermined number or a first predetermined size of PDCP data packets, where the first PDCP status request message is sent by the first donor base station every time the first donor base station sends a first predetermined number or a first predetermined size of PDCP data packets;

the processor is further configured to determine PDCP data packets that need to be sent in a PDCP re-establishment procedure according to the receiving condition indicated by the third PDCP status report.

40. The first donor base station of claim 38,

the processor is further configured to delete a data packet whose remaining time is less than a predetermined threshold or delete a data packet whose discard timer is overtime according to a transmission queue of the PDCP data packet of the terminal and the remaining time of the discard timer of the data packet in the queue to be confirmed after the second indication message is transmitted; and determining the PDCP data packets which need to be sent in the PDCP reconstruction process according to the sending queue and the data packets left in the queue to be confirmed.

41. A first donor base station, comprising:

42. A terminal, comprising: a transceiver, a memory, a processor, and a program stored on the memory and executable on the processor;

43. The terminal of claim 42,

the transceiver is further configured to receive a first indication message sent by the first donor base station for indicating to start a PDCP data recovery procedure.

44. The terminal of claim 43,

the processor is further configured to generate and send a first PDCP status report to the first donor base station according to a receiving condition of a PDCP data packet sent by the first donor base station at a first sending opportunity and/or when the first indication message is received; the first sending opportunity comprises a preset first sending time period or a first PDCP state request message sent by a first donor base station or the first PDCP state request message is sent by the first donor base station after the first donor base station sends the PDCP data packets of the first preset number or the first preset size every time the terminal receives the PDCP data packets of the first preset number or the first preset size.

45. The terminal of claim 43,

the transceiver is further configured to delete a data packet whose remaining time is less than a predetermined threshold or delete a data packet whose discard timer is overtime according to a transmission queue of PDCP data packets of the first donor base station and the remaining time of the discard timer of the data packet in the queue to be confirmed after receiving the first indication message; and determining the PDCP data packets which need to be sent in the PDCP data recovery process and sending the PDCP data packets according to the sending queue and the data packets left in the queue to be confirmed.

46. The terminal of claim 42,

the transceiver is further configured to receive a second indication message sent by the first donor base station for indicating to start a PDCP re-establishment procedure.

47. The terminal of claim 46,

the processor is further configured to generate and send a third PDCP status report to the first donor base station according to a receiving condition of a PDCP data packet sent by the first donor base station at a first sending opportunity and/or when the second indication message is received after the second indication message is received; the first sending opportunity comprises a preset first sending time period or a first PDCP state request message sent by a first donor base station or the first PDCP state request message is sent by the first donor base station after the first donor base station sends the PDCP data packets of the first preset number or the first preset size every time the terminal receives the PDCP data packets of the first preset number or the first preset size.

48. The terminal of claim 46,

the transceiver is further configured to delete a data packet whose remaining time is less than a predetermined threshold or delete a data packet whose discard timer is overtime according to a transmission queue of the PDCP data packet of the first donor base station and the remaining time of the discard timer of the data packet in the queue to be confirmed after receiving the second indication message; and determining the PDCP data packets which need to be sent in the PDCP reconstruction process and sending the PDCP data packets according to the sending queue and the data packets left in the queue to be confirmed.

49. A terminal, comprising:

50. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out the steps of the data processing method of a wireless backhaul path according to any one of claims 1 to 33.