Data Unit Processing Method, Apparatus, Node, and Storage Medium

Abstract

The present application provides a data unit processing method, apparatus, node, and storage medium. The method includes an IAB node performing a data unit processing operation during a handover association period, where the data unit processing operation includes at least one of the following: retaining a first BAP PDU for which there is no matching BAP routing configuration in the IAB node; routing a second BAP PDU with a target BAP address being the original host donor distribution unit (DU) to the target donor DU; processing according to a BAP routing identifier in a third BAP PDU, where the third BAP PDU includes two BAP routing identifiers. The present application can improve the transmission performance of the IAB node.

Description

Technical Field

[0001] The present invention relates to the field of communication technologies, and in particular, to a method, apparatus, node, and storage medium for processing data units. Background Art

[0002] In some communication systems (such as: 5G systems), an integrated access backhaul (IAB) system is introduced. In the IAB system, an IAB node includes two parts of functions: a Distributed Unit (DU) and a Mobile Termination (MT). However, currently, when an IAB node switches, the entity of the Backhaul Adaptation Protocol (BAP) of the IAB node will be reconstructed or the BAP route will be reconfigured, which may cause some BAP Protocol Data Units (PDUs) of the IAB node to be discarded, resulting in relatively low transmission performance of the IAB node. Summary of the Invention

[0003] Embodiments of the present application provide a method, apparatus, node, and storage medium for processing data units to solve the problem of relatively low transmission performance of IAB nodes.

[0004] Embodiments of the present application provide a method for processing data units, including:

[0005] During a handover-related period, an IAB node performs a data unit processing operation, where the data unit processing operation includes at least one of the following:

[0006] Retain a first BAP PDU for which there is no matching BAP route configuration in the IAB node;

[0007] Route a second BAP PDU with a target BAP address of the original donor meta-DU to the target donor DU;

[0008] Process according to a BAP route identifier in a third BAP PDU, where the third BAP PDU includes two BAP route identifiers.

[0009] Embodiments of the present application also provide a method for processing data units, including:

[0010] A control node sends indication information to a self-backhaul IAB node, where the indication information is used to instruct the IAB node to perform a data unit processing operation during a handover-related period, and the data unit processing operation includes at least one of the following:

[0011] Retain a first BAP protocol data unit (PDU) for which there is no matching backhaul adaptation protocol (BAP) routing configuration in the IAB node.

[0012] Route a second BAP PDU with a target BAP address of the original host donor distribution unit (DU) to the target donor DU.

[0013] Process according to a BAP routing identifier in a third BAP PDU, where the third BAP PDU includes two BAP routing identifiers.

[0014] An embodiment of the present application further provides a data unit processing apparatus, including:

[0015] An execution module, configured to perform data unit processing operations during a handover association period, where the data unit processing operations include at least one of the following:

[0016] Retain a first BAP protocol data unit (PDU) for which there is no matching backhaul adaptation protocol (BAP) routing configuration in the self-backhaul IAB node.

[0017] Route a second BAP PDU with a target BAP address of the original host donor distribution unit (DU) to the target donor DU.

[0018] Process according to a BAP routing identifier in a third BAP PDU, where the third BAP PDU includes two BAP routing identifiers;

[0019] Wherein, the IAB node includes the apparatus.

[0020] An embodiment of the present application further provides a data unit processing apparatus, including:

[0021] A first sending module, configured to send indication information to a self-backhaul IAB node, where the indication information is used to instruct the IAB node to perform data unit processing operations during a handover association period, and the data unit processing operations include at least one of the following:

[0022] Retain a first BAP protocol data unit (PDU) for which there is no matching backhaul adaptation protocol (BAP) routing configuration in the IAB node.

[0023] Route a second BAP PDU with a target BAP address of the original host donor distribution unit (DU) to the target donor DU.

[0024] Process according to a BAP routing identifier in a third BAP PDU, where the third BAP PDU includes two BAP routing identifiers;

[0025] Among them, the control node includes the said device.

[0026] An embodiment of this application also provides a self-backhaul IAB node, including: a memory, a processor, and a program or instruction stored on the memory and executable on the processor. When the program or instruction is executed by the processor, the steps in the data unit processing method provided by the embodiment of this application are implemented.

[0027] An embodiment of this application also provides a network node, including: a memory, a processor, and a program or instruction stored on the memory and executable on the processor. When the program or instruction is executed by the processor, the steps in the data unit processing method provided by the embodiment of this application are implemented.

[0028] An embodiment of this application also provides a readable storage medium. A program or instruction is stored on the readable storage medium. When the program or instruction is executed by a processor, the steps in the data unit processing method on the IAB node side provided by the embodiment of this application are implemented, or when the program or instruction is executed by a processor, the steps in the data unit processing method on the control node side provided by the embodiment of this application are implemented.

[0029] In an embodiment of this application, during the handover association period, the IAB node performs data unit processing operations. Among them, the data unit processing operations include at least one of the following: retaining a first BAP PDU that does not have a matching BAP routing configuration in the IAB node; routing a second BAP PDU with a target BAP address being the original host donor distribution unit (DU) to the target donor DU; processing according to a BAP routing identifier in a third BAP PDU, where the third BAP PDU includes two BAP routing identifiers. This can reduce the discarding of BAP PDUs, thereby improving the transmission performance of the IAB node. Description of the Drawings

[0030] Figure 1 A schematic diagram of a wireless communication system to which an embodiment of this application can be applied is shown;

[0031] Figure 2 is a block diagram of another wireless communication system to which an embodiment of this application can be applied;

[0032] Figure 3 is a flowchart of a data unit processing method provided by an embodiment of this application;

[0033] Figure 4 is a flowchart of another data unit processing method provided by an embodiment of this application;

[0034] Figure 5It is a schematic diagram of a data unit processing method provided by an embodiment of the present application;

[0035] Figure 6 It is a schematic diagram of another data unit processing method provided by an embodiment of the present application;

[0036] Figure 7 It is a structural diagram of a data unit processing device provided by an embodiment of the present application;

[0037] Figure 8 It is a structural diagram of another data unit processing device provided by an embodiment of the present application;

[0038] Figure 9 It is a structural diagram of a network node provided by an embodiment of the present application. Detailed implementation manners

[0039] Next, the technical solutions in the embodiments of the present application will be clearly and completely described in conjunction with the accompanying drawings in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, rather than all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative efforts belong to the scope of protection of the present application.

[0040] The terms "first", "second", etc. in the description and claims of the present application are used to distinguish similar objects, rather than to describe a specific order or sequence. It should be understood that such data can be interchanged under appropriate circumstances so that the embodiments of the present application can be implemented in an order other than those illustrated or described herein, and the objects distinguished by "first" and "second" are usually of the same category, and the number of objects is not limited. For example, the first object can be one or multiple. In addition, "and / or" in the description and claims means at least one of the connected objects, and the character " / " generally means an "or" relationship between the associated objects before and after.

[0041] It should be noted that the technology described in the embodiments of this application is not limited to the Long Term Evolution (LTE) / LTE-Advanced (LTE-A) system, and can also be used in other wireless communication systems, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-carrier Frequency-Division Multiple Access (SC-FDMA), and other systems. The terms "system" and "network" in the embodiments of this application are often used interchangeably, and the described technology can be used in the above-mentioned systems and radio technologies, as well as in other systems and radio technologies. However, the following description describes the New Radio (NR) system for example purposes, and the NR term is used in most of the following descriptions, although these technologies can also be applied to applications other than NR system applications, such as the 6th Generation (6G) communication system.

[0042] Figure 1 FIG. shows a schematic diagram of a wireless communication system to which the embodiments of this application can be applied. The wireless communication system includes a terminal 11, an IAB node 12, a parent IAB node 13, and a Centralized Unit (CU) 14.

[0043] In the above system, the IAB node 12 can rely on the MT to find the parent IAB node 13 and establish a wireless connection with the DU of the parent IAB node 13. This wireless connection is called the backhaul link of the IAB node 12 and becomes the access link of the parent IAB node 13. After establishing a complete backhaul link, the IAB node 12 turns on its DU function, and the DU will provide cell services, that is, the DU can provide access services for the terminal 11. The DUs of all IAB nodes can be connected to the CU 14.

[0044] In addition, as Figure 2As shown in the figure, the CU can configure the DU of the IAB node through the F1-C (F1-AP) protocol. The CU can configure the MT of the IAB node through the Radio Resource Control (RRC) protocol. And the CU14 can be a donor IAB node or a separate network node, specifically including: a CU-control plane (CP) and a CU-user plane (UP).

[0045] It should be noted that Figure 1 only the terminal 11, the IAB node 12, the parent IAB node 13, and the CU14 are used as examples for illustration. In practical applications, the number of IAB nodes in the embodiments of the present application is not limited.

[0046] In addition, the terminal 11 can also be referred to as a terminal device or a user terminal (User Equipment, UE). The terminal 11 can be a mobile phone, a tablet personal computer, a laptop computer or a notebook computer, a personal digital assistant (PDA), a handheld computer, a netbook, an ultra-mobile personal computer (UMPC), a mobile Internet device (MID), or a vehicle-mounted device (VUE), a pedestrian terminal (PUE), a RedCap UE, etc. terminal-side devices. Among them, the RedCap UE can include: wearable devices, industrial sensors, video surveillance devices, etc. Wearable devices include: bracelets, earphones, glasses, etc. It should be noted that the specific type of the terminal 11 is not limited in the embodiments of the present application.

[0047] Next, with reference to the accompanying drawings, the resource configuration methods, devices, network nodes, and storage media provided by the embodiments of the present application will be described in detail through specific embodiments and their application scenarios.

[0048] Please refer to Figure 3 , Figure 3 which is a flowchart of a data unit processing method provided by an embodiment of the present application. As Figure 3 shown, it includes the following steps:

[0049] Step 301, the IAB node performs a data unit processing operation during the handover association period, where the data unit processing operation includes at least one of the following:

[0050] Retain the first BAP PDU for which there is no matching BAP routing configuration in the IAB node;

[0051] Route the second BAP PDU with the target BAP address being the original donor DU to the target donor DU;

[0052] Process according to a BAP routing identifier in the third BAP PDU, where the third BAP PDU includes two BAP routing identifiers.

[0053] Wherein, the above original donor DU is the donor DU of the IAB node before execution, and the above target donor DU is the donor DU of the IAB node after execution, also referred to as the new donor DU. Wherein, the above original donor DU and target donor DU may belong to the same CU or different CUs.

[0054] The above handover can be a handover of the same CU with a different donor DU, that is, switching the donor DU within the same CU; or, the above handover can be a handover between different CUs, that is, switching from one CU to another CU.

[0055] That is to say, the above handover associated period may include one of the following:

[0056] The period associated with the handover process of the IAB node switching from the original donor DU to the target donor DU in the same meta CU;

[0057] The period associated with the handover process of the IAB node switching from the original CU to the target CU, where the original donor DU is the DU in the original CU and the target donor DU is the DU in the target CU.

[0058] The above original CU may be the original donor CU, and the above target CU may be the target donor CU.

[0059] In the embodiments of the present application, for the handover of the IAB node from the original CU to the target CU, the BAP entity of the IAB node can be reconstructed, and the BAP addresses and BAP routes of the IAB node and its downstream IAB nodes can all change; for the handover of the IAB node from the original donor-DU to the target donor-DU in the same CU, the BAP route can be reconfigured. For example: the BAP path of the downlink data is reconfigured from the target donor-DU to the BAP path of the access IAB node; the target BAP address of the uplink data is reconfigured from the address of the original donor DU to the address of the target donor DU.

[0060] In the embodiments of the present application, the original CU and the original donor DU can both represent the original control nodes of the mobile IAB system; the target CU and the original donor DU can both represent the target control nodes of the mobile IAB system.

[0061] The above switching-related period can include at least one of: a preset period before the switching process and a preset period after the switching process.

[0062] The above first BAP PDU can be such that no BAP routing configuration matching the BAP PDU can be found in the above IAB node. For example: the above IAB node cannot find a forwarding route to the destination address of the first BAP PDU. In this way, the above IAB node cannot route the above BAP PDU, and the above first BAP PDU is retained according to the above processing operation to avoid discarding the first BAP PDU.

[0063] The above processing based on one BAP routing identifier in the third BAP PDU can be that the third BAP PDU includes two BAP routing identifiers, where different BAP routing identifiers route to different donor DUs. Thus, according to the above processing operation, it can be processed according to one of the BAP routing identifiers to avoid the situation where the BAP PDU only includes one BAP routing identifier and the IAB node cannot route according to this BAP routing identifier resulting in discarding.

[0064] In addition, in the embodiments of the present application, the above IAB node can perform the above data unit processing operation according to an instruction received, or the above IAB node can be pre-configured to perform the data unit processing operation during the switching-related period, which can save transmission overhead because no instruction needs to be sent. In addition, since performing the above data unit processing operation can achieve uninterrupted data transmission during the switching process.

[0065] In the embodiments of the present application, through the above steps, the IAB node can perform the above data unit processing operation during the switching-related period, thereby reducing or even avoiding the discarding of the BAP PDU, and further improving the transmission performance of the IAB node.

[0066] As an optional implementation manner, the method further includes at least one of:

[0067] The IAB node receives a first instruction sent by the original CU or the original donor DU, and the first instruction is used to instruct to stop discarding the first BAP PDU;

[0068] The IAB node receives a second indication sent by the target CU or the target donor DU, where the second indication is used to indicate to stop discarding the first BAP PDU;

[0069] The IAB node receives a third indication sent by the target CU or the target donor DU, where the third indication is used to indicate to route the second BAP PDU to the target donor DU.

[0070] The above-mentioned stopping discarding the first BAP PDU may be to stop the discarding behavior of discarding the BAP PDU due to the inability to find a matching BAP route, so that the above-mentioned IAB node retains the first BAP PDU for which a matching BAP route configuration cannot be found before and / or for a period of time after the handover.

[0071] The above-mentioned routing the second BAP PDU to the target donor DU may be that the above-mentioned IAB node re-routes the old BAP PDU to the destination donor DU according to the new BAP route configuration.

[0072] In the above-mentioned implementation manner, it is possible to perform the above-mentioned data unit processing operation according to at least one of the above-mentioned first indication, second indication, and third indication, so as to ensure the understanding consistency between the IAB node and the donor DU and CU, and further improve the transmission performance of the IAB system.

[0073] Optionally, at least one of the first indication, second indication, and third indication is carried in the handover command or received before the handover starts; or

[0074] At least one of the first indication, second indication, and third indication is received after the handover is completed.

[0075] In this implementation manner, it is possible to obtain the above-mentioned first indication, second indication, and third indication before, during, or after the handover. For example: the target CU notifies each handover IAB node before the handover to route the old BAP PDU to the target donor DU, or the target CU sends a notification to each handover IAB node after determining that all handover IAB nodes have completed the handover to route the old BAP PDU to the target donor DU.

[0076] As an optional implementation manner, the handover associated period includes a first period after the handover is completed, and the method further includes:

[0077] When the first period ends, the IAB node receives a fourth indication sent by the target CU or the target donor DU, where the fourth indication stops executing the data unit processing operation.

[0078] In this embodiment, when the first time period ends, the execution of the data unit processing operation can be stopped in a timely manner according to the above fourth indication, so as to resume the normal abnormal BAP PDU detection in a timely manner. Of course, in some embodiments, after the end of the above first time period, the IAB node can also execute the data unit processing operation by itself.

[0079] As an optional embodiment, the handover associated time period includes a first time period after the handover is completed. During the first time period, the IAB node retains the BAP address of the original donor DU, and after the end of the first time period, the IAB node removes the BAP address of the original donor DU.

[0080] In this embodiment, since the IAB node retains the BAP address of the original donor DU, the IAB node can accurately identify which BAP PDUs were originally sent to the original donor DU, and these BAP PDUs can be sent to the target donor DU through the above processing operation, thereby further improving the transmission performance of the IAB node. In addition, since the IAB node removes the BAP address of the original donor DU after the end of the first time period, the normal abnormal BAP PDU detection can be resumed in a timely manner, and the storage consumption of the IAB can also be reduced.

[0081] As an optional embodiment, routing the second BAP PDU with the target BAP address being the original host donor distribution unit DU to the target donor DU includes:

[0082] Performing a rewriting operation on the second BAP PDU and routing the rewritten second BAP PDU to the target donor DU, where the rewriting operation includes at least one of the following:

[0083] Rewriting the first routing identifier of the second BAP PDU as a second routing identifier, where the first routing identifier is used to route to the original donor DU, and the second routing identifier is used to route to the target donor DU;

[0084] Rewriting the BAP path of the second BAP PDU as the BAP path to the target donor DU.

[0085] Among them, the above routing identifier may be the BAP routing ID, and the rewriting of the first routing identifier of the second BAP PDU into the second routing identifier may be to rewrite the BAP routing ID in the BAP header of the BAP PDU into the BAP routing ID of the target donor DU, so as to send the rewritten BAP PDU to the target donor DU. Among them, rewriting the BAP routing ID includes rewriting the destination BAP address of the BAP PDU into the address of the target donor DU.

[0086] The above rewriting of the BAP path of the second BAP PDU into the BAP path to the target donor DU may be to rewrite the BAP path of the BAP routing ID into the BAP path to the target donor DU.

[0087] In this embodiment, through the above rewriting operation, the second BAP PDU can be routed to the target donor DU to avoid discarding the second BAP PDU and improve the transmission performance of the IAB node.

[0088] As an optional embodiment, the processing based on a BAP routing identifier in the third BAP PDU includes one of the following:

[0089] Modify the third BAP PDU to a BAP PDU that only includes one BAP routing identifier, and transmit it according to the one BAP routing identifier;

[0090] When the third BAP PDU includes a BAP routing identifier for routing to the original donor DU and a BAP routing identifier for routing to the target donor DU, route and transmit the third BAP PDU to the original donor DU or the target donor DU;

[0091] When the BAP address carried by a BAP routing identifier included in the third BAP PDU is the BAP address of the IAB node, cache the BAP PDU or deliver the service data unit (SDU) carried by the BAP PDU to the upper layer.

[0092] The above-mentioned modification of the third BAP PDU to include only one BAP routing identifier in the BAP PDU may be to delete the BAP routing identifier that the above-mentioned IAB node currently does not support in the third BAP PDU. For example, remove the routing identifier to the original donor DU in the BAP header of the third BAP PDU to retain the BAP routing identifier supported by the IAB node and transmit it according to the BAP routing identifier. Of course, in some cases, the IAB node may support two BAP routing identifiers included in the third BAP PDU, so either BAP routing identifier can be deleted.

[0093] The above-mentioned routing and transmission of the third BAP PDU to the original donor DU or the target donor DU may be to route and transmit the third BAP PDU to the original donor DU or the target donor DU according to actual needs.

[0094] The above-mentioned caching of the third BAP PDU or delivering the SDU carried by the BAP PDU to the upper layer may be that for a downlink BAP PDU, after the IAB node receives the BAP PDU, if the BAP address of the IAB node matches the BAP address carried by any BAP routing ID, the data is submitted to the upper layer. Alternatively, the BAP entity of the IAB node may decide whether to cache the data or directly send the data to the upper layer based on the matching BAP routing ID.

[0095] In this embodiment, it is possible to process the third BAP PDU according to a BAP routing ID in the third BAP PDU to avoid discarding the BAP PDU.

[0096] Optionally, the third BAP PDU further includes a fifth indication, and the fifth indication is used to indicate that the third BAP PDU includes two BAP routing identifiers;

[0097] In this embodiment, it can be determined that the third BAP PDU includes two BAP routing identifiers through the above-mentioned fifth indication, so that the IAB node can process the third BAP PDU according to the data unit processing operation described in the above embodiment.

[0098] Further, in the case of modifying the third BAP PDU to include only one BAP routing identifier in the BAP PDU and transmitting it according to the one BAP routing identifier, the method may further include: modifying the fifth indication to be used to indicate that the third BAP PDU includes one BAP routing identifier.

[0099] As an optional implementation manner, when the switching associated period includes the period associated with the switching process of the IAB node from the original CU to the target CU, the third BAP PDU further includes a sixth indication, where the sixth indication is used to indicate that the third BAP PDU is generated according to the encryption information of the original CU, or is used to indicate that the third BAP PDU is generated according to the encryption information of the target CU.

[0100] The above encryption information may include a ciphering key.

[0101] In this implementation manner, the encryption information of the third BAP PDU can be indicated by the above sixth indication, so that the terminal or the CU decrypts the third BAP PDU in a corresponding manner when receiving the third BAP PDU, thereby improving the reliability of the third BAP PDU.

[0102] Optionally, when the third BAP PDU is a downlink BAP PDU, the method further includes:

[0103] The IAB node indicates to the terminal that the third BAP PDU is generated according to the encryption information of the original CU, or indicates that the third BAP PDU is generated according to the encryption information of the target CU.

[0104] Among them, indicating the above content to the terminal may be performed in an explicit or implicit manner. For example, the above IAB may indicate the above content to the terminal through a Packet Data Convergence Protocol (PDCP) configuration. For example, a Radio Network Temporary Identity (RNTI) or a dedicated logical channel (LCH) is used to schedule the transmission of the PDCP PDU generated by the original CU, so that the terminal can identify whether the PDCP is generated by the encryption information configured by the original CU or the new CU, and then can complete decryption with the corresponding one.

[0105] In this implementation manner, since the above content is indicated to the terminal, it helps the terminal to accurately decrypt the above BAP PDU.

[0106] As an optional implementation manner, the third BAP PDU includes:

[0107] A BAP routing identifier that only contains a BAP address;

[0108] A BAP routing identifier that contains a BAP address and a BAP path.

[0109] In this embodiment, it is possible to implement that one of the above-mentioned third BAP PDUs has a BAP routing ID that only contains the BAP address, and the other BAP routing ID contains the BAP address and the BAP path. For example: the BAP routing ID for routing to the original donor DU only contains the BAP address, while the BAP routing ID for routing to the target donor DU contains the BAP address and the BAP path; the BAP routing ID for routing to the target donor DU only contains the BAP address, while the BAP routing ID for routing to the original donor DU contains the BAP address and the BAP path.

[0110] In this embodiment, since one BAP routing ID only contains the BAP address, that is, the BAP path can be omitted, the overhead of the BAP PDU can be reduced.

[0111] As an alternative embodiment, the above-mentioned third BAP PDU includes a third BAP routing identifier configured by the original CU and a fourth BAP routing identifier configured by the target CU, and the order of the third BAP routing identifier and the fourth BAP routing identifier is used to indicate that the third BAP PDU is generated by the original CU or the target CU.

[0112] In this embodiment, when generating a BAP PDU including a dual BAP routing ID, it is possible to identify whether the PDCP PDU carried by the BAP PDU is generated by the PDCP entity configured by the original CU or the PDCP configured by the target CU through the placement order of the BAP routing ID in the BAP header. For example, if the BAP routing ID for routing to the original donor DU is placed before the BAP routing ID for routing to the target donor DU, it indicates that the BAP PDU is generated by the PDCP entity configured by the original CU.

[0113] In this embodiment, since it is indicated by the above order that the third BAP PDU is generated by the original CU or the target CU, the overhead of the third BAP PDU can be reduced.

[0114] As an alternative embodiment, the method further includes at least one of the following:

[0115] When the IAB node receives a fourth BAP PDU, route the fourth BAP PDU to the target donor DU, where the target BAP address of the fourth BAP PDU matches the BAP address of the target donor DU;

[0116] When the IAB node receives a fifth BAP PDU, discard the fifth BAP PDU, where the destination BAP address of the fifth BAP PDU does not match the BAP address of the original donor DU and does not match the BAP address of the target donor DU;

[0117] When the IAB node receives a sixth BAP PDU, discard the sixth BAP PDU, where the destination BAP address of the sixth BAP PDU does not match at least one of the following:

[0118] The old BAP address of the IAB node that can be reached by the BAP routing configuration of the IAB node;

[0119] The new BAP address of the IAB node that can be reached by the BAP routing configuration of the IAB node;

[0120] The BAP address of the IAB node.

[0121] In this embodiment, it can be realized that if the destination BAP address carried by a BAP PDU matches the BAP address of the target donor DU, the BAP PDU is directly sent to the target donor DU; if the destination BAP address carried by the received uplink BAP PDU does not match the BAP address of the original donor DU nor the BAP address of the target donor DU, it is determined that the BAP PDU is an abnormal BAP PDU and the BAP PDU is discarded: if the destination BAP address carried by the received downlink BAP PDU does not match any of the old BAP address and the new BAP address of the access IAB node that can be reached by the BAP routing configuration of the IAB node, the BAP PDU is discarded, or if the destination BAP address of the received downlink BAP PDU is not the BAP address of the above IAB node, the BAP PDU is discarded.

[0122] In the embodiments of the present application, during the handover association period, the IAB node performs data unit processing operations, where the data unit processing operations include at least one of the following: retaining a first BAP PDU for which there is no matching BAP routing configuration in the IAB node; routing a second BAP PDU with the destination BAP address being the original host donor distribution unit DU to the target donor DU; processing according to a BAP routing identifier in a third BAP PDU, where the third BAP PDU includes two BAP routing identifiers. This can reduce the discarding of BAP PDUs, thereby improving the transmission performance of the IAB node.

[0123] Please refer to Figure 4 ,Figure 4 is a flowchart of another data unit processing method provided by an embodiment of the present application. As Figure 4 shown, it includes the following steps:

[0124] Step 401, the control node sends indication information to the self-backhaul IAB node, and the indication information is used to instruct the IAB node to perform data unit processing operations during the handover association period. Among them, the data unit processing operations include at least one of the following:

[0125] Retain the first BAP protocol data unit (PDU) for which there is no matching backhaul adaptation protocol (BAP) routing configuration in the IAB node;

[0126] Route the second BAP PDU with the target BAP address being the original host donor distribution unit (DU) to the target donor DU;

[0127] Process according to a BAP routing identifier in the third BAP PDU, where the third BAP PDU includes two BAP routing identifiers.

[0128] Optionally, the control node includes one of the following:

[0129] The original donor DU, the target donor DU, the original control unit (CU), the target CU.

[0130] For the above handover association period and data unit processing operations, reference can be made to the corresponding descriptions in the Figure 3 embodiment shown, which will not be elaborated here.

[0131] In this embodiment, by using the above indication information to instruct the IAB node to perform data unit processing operations during the handover association period, the transmission performance of the IAB node can be improved.

[0132] Optionally, when the control node includes the original CU or the original donor DU, the method further includes:

[0133] The control node sends the BAP address of the original donor DU to the target donor DU or the target CU.

[0134] In this implementation manner, since the BAP address of the original donor DU is sent to the target donor DU or the target CU, it can be ensured that for the BAP PDU with the target address being the original donor DU, the IAB node can be instructed to adopt the above data unit processing operations to avoid discarding these BAP PDUs.

[0135] Optionally, when the control node includes the original CU or the original donor DU, the method further includes:

[0136] The control node sends a request message to the target donor DU or the target CU, where the request message is used to request to perform a lossless data handover;

[0137] The control node sends indication information to the self-backhaul IAB node, including:

[0138] When the control node receives a response message from the target donor DU or the target CU agreeing to the request message, the control node sends indication information to the self-backhaul IAB node.

[0139] Among them, the above request to perform a lossless data handover means requesting the target donor DU or the target CU to perform the operations corresponding to the above IAB node to avoid discarding BAP PDUs and achieve a lossless data handover.

[0140] Optionally, the method further includes at least one of the following:

[0141] When the control node includes the original CU or the original donor DU, the control node sends a first indication to the IAB node, where the first indication is used to indicate to stop discarding the first BAP PDU;

[0142] When the control node includes the target CU or the target donor DU, the control node sends a second indication to the IAB node, where the second indication is used to indicate to stop discarding the first BAP PDU;

[0143] When the control node includes the target CU or the target donor DU, the control node sends a third indication to the IAB node, where the third indication is used to indicate to route the second BAP PDU to the target donor DU.

[0144] Optionally, at least one of the first indication, the second indication, and the third indication is carried in the handover command or sent before the handover starts; or

[0145] At least one of the first indication, the second indication, and the third indication is sent after the handover is completed.

[0146] Among them, the corresponding descriptions of the above first indication, second indication, and third indication can be referred to Figure 3 the corresponding descriptions of the embodiments shown, which will not be elaborated here.

[0147] Optionally, the handover associated period includes a first period after the handover is completed, and the method further includes:

[0148] When the first period ends, the control node sends an instruction to the IAB node to stop executing the data unit processing operation.

[0149] Among them, the above instruction for stopping the execution of the data unit processing operation can be referred to Figure 3 the corresponding description of the embodiments shown, which will not be elaborated here.

[0150] Optionally, when the handover associated period includes the period associated with the handover process in which the IAB node switches from the original CU to the target CU, the third BAP PDU further includes a sixth indication, and the sixth indication is used to indicate that the third BAP PDU is generated according to the encryption information of the original CU, or is used to indicate that the third BAP PDU is generated according to the encryption information of the target CU.

[0151] Among them, the above sixth indication can be referred to Figure 3 the corresponding description of the embodiments shown, which will not be elaborated here.

[0152] Optionally, when the control node includes the target CU, the method further includes:

[0153] When the control node receives the third BAP PDU and the sixth indication is used to indicate that the third BAP PDU is generated according to the encryption information of the original CU, the control node sends the third BAP PDU to the original CU;

[0154] The control node receives the data for decrypting the third BAP PDU sent by the original CU;

[0155] Or,

[0156] When the control node includes the original CU, the method further includes:

[0157] When the control node receives the third BAP PDU and the sixth indication is used to indicate that the third BAP PDU is generated according to the encryption information of the target CU, the control node sends the third BAP PDU to the target CU;

[0158] The control node receives the data for decrypting the third BAP PDU sent by the target CU.

[0159] In this embodiment, the data of the third BAP PDU can be accurately decrypted through the interaction between the original CU and the target CU.

[0160] Optionally, when the control node includes the target CU or the target donor DU, the method further includes:

[0161] When the control node receives an abnormal BAP PDU, discard the abnormal BAP PDU, where the abnormal BAP PDU carries a destination BAP address that does not match the BAP address of the control node and does not match the BAP address of the original donor DU or the original CU.

[0162] In this embodiment, the control node can discard the abnormal BAP PDU.

[0163] It should be noted that, as an embodiment corresponding to the control node side in the Figure 3 shown embodiment, the specific implementation can refer to the relevant description of the Figure 3 shown embodiment. To avoid repeated description, this embodiment will not be elaborated here. In this embodiment, the transmission performance of the IAB node can also be improved.

[0164] The following uses multiple embodiments to illustrate the data unit processing method provided by the embodiments of the present application:

[0165] Embodiment 1:

[0166] This embodiment mainly describes the handover process without BAP PDU loss for switching the donor DU within the same CU (intra-CU inter-donor DU). Specifically, it can be as Figure 5 shown, Figure 5 shows the handover process for switching the donor DU within the same CU without data loss.

[0167] As shown in step 1 in Figure 5 shown, before switching the donor DU within the same CU, the CU sends a notification message to the IAB node to be switched, notifying the IAB node to be switched to stop discarding the received BAP PDU due to the inability to find the BAP routing configuration. After receiving this message, the IAB node should cache the received BAP PDU that cannot find the BAP routing configuration until the IAB node receives the new BAP routing-related configuration information sent by the CU. Here, the inability to find the BAP routing configuration means that the forwarding route to the destination address of the BAP PDU cannot be found.

[0168] As Figure 5As shown in Steps 2, 3, and 4, the above IAB node receives a handover command, which may include the handover configuration of the MT and the F1-AP BAP routing reconfiguration information; the IAB node completes the IAB-MT and BAP routing configurations according to the handover command; then the IAB node sends the MT handover completion and BAP reconfiguration completion information to the CU. After the handover, the IAB node saves the BAP address of the original donor-DU.

[0169] As Figure 5 shown in Step 5, the IAB node (which can be the above handover IAB node or a downstream node of the handover IAB node) performs BAP routing detection and forwarding on the cached BAP PDUs and newly received BAP PDUs as follows:

[0170] Method 1: If the destination BAP address carried in a BAP PDU matches the BAP address of the original donor DU, rewrite the BAP routing ID in the BAP header of the BAP PDU to the BAP routing ID of the target donor DU (or called the new donor DU), and send the rewritten BAP PDU to the target donor DU; where rewriting the BAP routing ID includes rewriting the destination BAP address of the BAP PDU to the address of the target donor DU, and / or rewriting the BAP path of the BAP PDU to the BAP path of the target donor DU;

[0171] Method 2: If the destination BAP address carried in a BAP PDU matches the BAP address of the target donor DU, directly send the BAP PDU to the target donor DU;

[0172] An intermediate IAB node after the handover determines whether to discard the cached or received BAP PDU as follows:

[0173] Method 3: If the destination BAP address carried in the received uplink BAP PDU does not match the BAP address of the original donor DU nor the BAP address of the target donor DU, regard the BAP PDU as an abnormal BAP PDU and discard the BAP PDU:

[0174] Method 4: If the destination BAP address carried in the received downlink BAP PDU does not match any of the old BAP addresses and new BAP addresses of the access IAB nodes that the BAP routing configuration of this IAB node can reach, discard the BAP PDU;

[0175] The target donor DU determines whether the received BAP PDU is discarded as follows

[0176] Method 5: If the destination BAP address carried in the BAP PDU received by a donor DU node does not match either its own BAP address or the BAP address of the original donor DU, the BAP PDU is regarded as an abnormal BAP PDU and discarded;

[0177] This embodiment further includes that the original CU node sends the BAP address of the original donor DU to the target donor DU node.

[0178] As Figure 5 shown in step 6, the CU sends a BAP PDU to the handover IAB node to stop retaining the BAP routing configuration that cannot be found. The IAB node removes the BAP address of the original donor DU and resumes normal detection of abnormal BAP PDUs.

[0179] It should be noted that step 1 of this embodiment is an optional step. For example, when the handover IAB node receives a handover command without receiving a data caching notification from the original CU, it still retains the BAP address of the original donor DU for forwarding the cached BAP data. The handover IAB node removes the BAP address of the original donor DU by itself after a period of time when the handover of this node is completed.

[0180] In particular, step 6 of this embodiment is an optional step. The handover IAB node removes the BAP address of the original donor DU by itself after a period of time when the handover of this node is completed.

[0181] Embodiment 2:

[0182] This embodiment takes the handover process of switching the donor DU (inter-CU inter-donor DU) between different CUs without BAP PDU loss as an example for illustration. As Figure 6 shown, Figure 6 shows an example of the handover process of the donor DU between different CUs without data loss.

[0183] This embodiment is applicable to the case of lossless data transmission during the handover between different CUs. Among them, Figure 6 the display of the original donor DU and the target donor DU is omitted.

[0184] As Figure 6As shown in step 1, the original CU sends a request for lossless data handover to the target CU. This request indicates that each handover IAB node supports lossless data handover. When responding to this request, the target CU can either approve or reject the request for lossless data handover.

[0185] As Figure 6 shown in step 2, if the request for lossless handover is approved, a request to start lossless data handover is sent to the original CU. After receiving this instruction, the original CU sends a notice to start the lossless data handover mode to each handover IAB node, notifying the IAB node to be handed over to stop discarding the received BAP PDU due to the inability to find the BAP routing configuration.

[0186] As Figure 6 shown in step 3, after receiving this message, an IAB node should cache the received BAP PDU for which the BAP routing configuration cannot be found.

[0187] As Figure 6 shown in steps 4, 5, and 6, the IAB node receives a handover command, which includes the handover configuration of the MT and the F1-AP information on BAP routing reconfiguration; completes the IAB-MT and BAP routing configurations according to the handover command; and then the IAB node sends information indicating that the MT handover and BAP reconfiguration are completed to the CU. After the handover, the IAB node saves the BAP address of the original donor-DU.

[0188] As Figure 6 shown in step 7, the IAB node performs BAP routing detection on the cached BAP PDU and the newly received BAP PDU. Among them, this detection process can handle the cached data in the same way as the detection process shown in Embodiment 1, so it will not be elaborated here. In particular, when the access IAB node performs BAP address matching detection on the received BAP PDU, if the BAP address carried in the BAP PDU matches its new BAP address or old BAP address, the BAP SDU is submitted to the upper layer.

[0189] As Figure 6 shown in step 8, after the target CU confirms that the handover transition time has ended, it sends a message to the handover IAB node to stop retaining the BAP PDU for which the BAP routing configuration cannot be found. The IAB node removes the BAP address of the original donor DU and resumes normal detection of abnormal BAP PDUs.

[0190] In particular, note that steps 1 and 2 of this embodiment are optional steps. The original CU can configure the handover IAB node to cache the BAP PDU during the handover process by itself. After the BAP reconfiguration is completed, the handover IAB node forwards the cached BAP PDU according to step 7 above;

[0191] In particular, note that steps 1, 2, and 3 of this embodiment are all optional steps. When the switching IAB node receives a handover command without receiving a data caching notification from the original CU, it still retains the BAP address of the original donor DU for forwarding the BAP data for caching. The switching IAB node removes the BAP address of the original donor DU by itself after a period of time when the handover of this node is completed.

[0192] In particular, step 8 of this embodiment is an optional step. The switching IAB node removes the BAP address of the original donor DU by itself after a period of time when the handover of this node is completed.

[0193] In particular, the data lossless handover request initiated by the original CU to the target CU may include the BAP address of the original donor DU.

[0194] It should be noted that for simplicity of expression, Figure 6 the target donor-DU and the original donor-DU nodes in are omitted. Before the IAB node handover, the signaling and data interaction between the CU and the IAB node are implemented through the original donor DU, and after the IAB node handover, the IAB node conducts signaling and data interaction with the new CU through the new donor DU.

[0195] Embodiment 3:

[0196] In this embodiment, the BAP PDU forwarding process based on dual BAP routing is used as an example for illustration:

[0197] In this embodiment, the original CU or the target CU can configure a data sending process for the switching IAB node to use dual BAP routing for a period of time after the handover and return to the single BAP routing data sending process after the handover. Dual BAP routing means that the same BAP PDU contains both the BAP routing ID to the original donor DU and the BAP routing ID to the target donor DU. At the same time, an indication is included in the BAP header indicating whether the BAP PDU carries one BAP routing ID or two BAP routing IDs. When an IAB node receives such a BAP PDU, if the BAP address carried in any BAP routing ID can be found in the BAP routing configuration of this IAB node, the BAP PDU is not discarded.

[0198] For uplink data, after receiving a BAP PDU containing dual BAP routing, the top IAB node of the switched IAB network can remove the routing to the original donor DU in the BAP header of the BAP PDU, reset the dual BAP routing ID indication, change the BAP PDU to a BAP PDU with a single BAP routing ID, and continue the transmission.

[0199] The BAP PDU with dual BAP routing can also be directly sent to the target / original donor DU node. The target / original donor node, if the BAP address carried in any BAP routing ID matches the BAP address of the donor DU itself, submits the data to the upper layer.

[0200] For the downlink BAP PDU, after receiving the BAP PDU, if the BAP address of the access IAB node matches the BAP address carried in any BAP routing ID, the data is submitted to the upper layer. Optionally, the BAP entity can decide whether to cache the data or directly send the data to the upper layer according to the matching BAP routing ID.

[0201] Optionally, for the handover between CUs, the BAP header can also indicate whether the carried BAP PDU is generated using the PDCP ciphering key before the handover or the PDCP ciphering key after the handover.

[0202] For uplink data, the target donor DU can determine whether the PDCP deciphering should be completed by the original CU or itself. If the original donor CU needs to complete it, the data is sent to the target CU, and the target CU forwards it to the original CU via Xn. After the original CU completes the PDCP deciphering, it forwards the data to the target CU again. Similarly, after receiving a BAP PDU, the original donor DU can also determine whether the carried PDCP PDU needs the original CU or the target CU to complete the PDCP deciphering. If the original CU completes the deciphering, the PDCP SDU after completing the deciphering of the PDCP PDU is forwarded to the original CU. Otherwise, the PDCP PDU is sent to the new CU, and the target CU completes the deciphering.

[0203] For downlink data, the access IAB node can indicate the PDCP configuration. For example, the PDCP PDU generated by the original CU is sent using a temporary RNTI or dedicated LCH scheduling. The UE identifies whether the PDCP is generated by the ciphering key configured by the original CU or the new CU, and then uses the corresponding one to complete deciphering.

[0204] When generating the dual BAP routing ID PDU, the placement order of the BAP routing ID in the BAP header can be fixed to identify whether the PDCP PDU carried by the BAP PDU is generated by the PDCP entity configured by the original CU or the PDCP generated by the target CU. For example, if the BAP routing ID to the original donor DU is placed before the BAP routing ID to the target donor DU, it means that the BAP PDU is generated by the PDCP entity configured by the original CU.

[0205] The dual BAP routing method can be used to switch the BAP routing of the IAB network during the handover of the donor DU within the same CU. The receiving IAB node determines whether it is the destination IAB node of the BAP PDU or forwards the BAP PDU based on any BAP routing ID. Compared with the handover between CUs, the dual BAP header under the handover of the donor DU within the same CU does not need to indicate the PDCP ciphering key because the sending and receiving PDCP entities of the PDCP carried by the BAP PDU remain unchanged before and after the handover.

[0206] Optionally, one of the BAP routing IDs in the BAP PDU can only contain the BAP address, that is, the BAP path can be omitted.

[0207] Please refer to Figure 7 , Figure 7 which is the structural diagram of a data unit processing device provided by an embodiment of the present invention. As Figure 7 shown, the data unit processing device 700 includes:

[0208] An execution module 701, configured to perform data unit processing operations during the handover association period, where the data unit processing operations include at least one of the following:

[0209] Retain the first BAP protocol data unit PDU that does not have a matching backhaul adaptation protocol BAP routing configuration in the self-backhaul IAB node;

[0210] Route the second BAP PDU with the target BAP address being the original host donor distribution unit (DU) to the target donor DU;

[0211] Process according to a BAP routing identifier in the third BAP PDU, where the third BAP PDU includes two BAP routing identifiers;

[0212] Wherein, the IAB node includes the device.

[0213] Optionally, the handover association period includes one of the following:

[0214] The period associated with the handover process of the IAB node when the same central control unit (CU) switches from the original donor DU to the target donor DU;

[0215] The period associated with the handover process of the IAB node when switching from the original CU to the target CU, where the original donor DU is the DU in the original CU and the target donor DU is the DU in the target CU.

[0216] Optionally, the device further includes at least one of the following:

[0217] A first receiving module, configured to receive a first indication sent by the original CU or the original donor DU, where the first indication is used to indicate to stop discarding the first BAP PDU;

[0218] A second receiving module, configured to receive a second indication sent by the target CU or the target donor DU, where the second indication is used to indicate to stop discarding the first BAP PDU;

[0219] A third receiving module, configured to receive a third indication sent by the target CU or the target donor DU, where the third indication is used to indicate to route the second BAP PDU to the target donor DU.

[0220] Optionally, at least one of the first indication, the second indication, and the third indication is carried in a handover command or received before the handover starts; or

[0221] At least one of the first indication, the second indication, and the third indication is received after the handover is completed.

[0222] Optionally, the handover association period includes a first period after the handover is completed, and the device further includes:

[0223] A fourth receiving module, configured to receive a fourth indication sent by the target CU or the target donor DU when the first time period ends, where the fourth indication stops the execution of the data unit processing operation.

[0224] Optionally, the handover associated time period includes a first time period after the handover is completed. During the first time period, the IAB node retains the BAP address of the original donor DU, and after the first time period ends, the IAB node removes the BAP address of the original donor DU.

[0225] Optionally, routing the second BAP PDU with the target BAP address being the second BAP of the original host donor distribution unit DU to the target donor DU includes:

[0226] Performing a rewriting operation on the second BAP PDU, and routing the rewritten second BAP PDU to the target donor DU, where the rewriting operation includes at least one of the following:

[0227] Rewriting the first routing identifier of the second BAP PDU to a second routing identifier, where the first routing identifier is used to route to the original donor DU, and the second routing identifier is used to route to the target donor DU;

[0228] Rewriting the BAP path of the second BAP PDU to the BAP path to the target donor DU.

[0229] Optionally, processing according to a BAP routing identifier in the third BAP PDU includes one of the following:

[0230] Modifying the third BAP PDU to a BAP PDU that only includes one BAP routing identifier, and transmitting according to the one BAP routing identifier;

[0231] When the third BAP PDU includes a BAP routing identifier for routing to the original donor DU and a BAP routing identifier for routing to the target donor DU, routing and transmitting the third BAP PDU to the original donor DU or the target donor DU;

[0232] When a BAP address carried by a BAP routing identifier included in the third BAP PDU is the BAP address of the IAB node, caching the BAP PDU or delivering the service data unit SDU carried by the BAP PDU to the upper layer.

[0233] Optionally, the third BAP PDU further includes a fifth indication for indicating that the third BAP PDU includes two BAP routing identifiers.

[0234] Optionally, in a case where the handover association period includes a period associated with a handover process in which the IAB node handovers from the original CU to the target CU, the third BAP PDU further includes a sixth indication for indicating that the third BAP PDU is generated according to the encryption information of the original CU, or for indicating that the third BAP PDU is generated according to the encryption information of the target CU.

[0235] Optionally, in a case where the third BAP PDU is a downlink BAP PDU, the apparatus further includes:

[0236] An indication module, configured to indicate to a terminal that the third BAP PDU is generated according to the encryption information of the original CU, or indicate that the third BAP PDU is generated according to the encryption information of the target CU.

[0237] Optionally, the third BAP PDU includes:

[0238] A BAP routing identifier that only contains a BAP address;

[0239] A BAP routing identifier that contains a BAP address and a BAP path.

[0240] Optionally, the third BAP PDU includes a third BAP routing identifier configured by the original CU and a fourth BAP routing identifier configured by the target CU, and the order of the third BAP routing identifier and the fourth BAP routing identifier is used to indicate that the third BAP PDU is generated by the original CU or the target CU.

[0241] Optionally, the apparatus further includes at least one of the following:

[0242] A first processing module, configured to route the fourth BAP PDU to the target donor DU when receiving the fourth BAP PDU, where a target BAP address of the fourth BAP PDU matches a BAP address of the target donor DU;

[0243] A second processing module, configured to discard the fifth BAP PDU when the IAB node receives the fifth BAP PDU, where the target BAP address of the fifth BAP PDU does not match the BAP address of the original donor DU and does not match the BAP address of the target donor DU;

[0244] A third processing module, configured to discard the sixth BAP PDU when the IAB node receives the sixth BAP PDU, where the destination BAP address of the sixth BAP PDU does not match at least one of the following:

[0245] The old BAP address of the IAB node that can be reached by the BAP routing configuration of the IAB node;

[0246] The new BAP address of the IAB node that can be reached by the BAP routing configuration of the IAB node;

[0247] The BAP address of the IAB node.

[0248] The data unit processing device provided in the embodiments of the present application can implement Figure 3 each process in the method embodiments. To avoid repetition, details are not described herein again, and the transmission performance of the IAB node can be improved.

[0249] It should be noted that the data unit processing device in the embodiments of the present application can be a device, or a component, an integrated circuit, or a chip in the IAB node.

[0250] Please refer to Figure 8 , Figure 8 which is a structural diagram of another data unit processing device provided in the embodiments of the present invention. As shown in Figure 8 , the data unit processing device 800 includes:

[0251] A first sending module 801, configured to send indication information to the self-backhaul IAB node, where the indication information is used to instruct the IAB node to perform data unit processing operations during a handover association period, and where the data unit processing operations include at least one of the following:

[0252] Retain a first BAP protocol data unit PDU that does not have a matching backhaul adaptation protocol BAP routing configuration in the IAB node;

[0253] Route a second BAP PDU with a destination BAP address of the original host donor distribution unit DU to the target donor DU;

[0254] Process according to a BAP routing identifier in a third BAP PDU, where the third BAP PDU includes two BAP routing identifiers;

[0255] Wherein, the control node includes the device.

[0256] Optionally, the control node includes one of the following:

[0257] The original donor DU, the target donor DU, the original control unit CU, and the target CU.

[0258] Optionally, when the control node includes the original CU or the original donor DU, the device further includes:

[0259] A second sending module, configured to send the BAP address of the original donor DU to the target donor DU or the target CU.

[0260] Optionally, when the control node includes the original CU or the original donor DU, the device further includes:

[0261] A third sending module, configured to send a request message to the target donor DU or the target CU, where the request message is used to request to perform a lossless data handover;

[0262] The sending the indication information to the self-backhaul IAB node includes:

[0263] When the control node receives a response message from the target donor DU or the target CU agreeing to the request message, sending the indication information to the self-backhaul IAB node.

[0264] Optionally, the device further includes at least one of the following:

[0265] A fourth sending module, configured to, when the control node includes the original CU or the original donor DU, send a first indication to the IAB node, where the first indication is used to indicate to stop discarding the first BAP PDU;

[0266] A fifth sending module, configured to, when the control node includes the target CU or the target donor DU, send a second indication to the IAB node, where the second indication is used to indicate to stop discarding the first BAP PDU;

[0267] A sixth sending module, configured to, when the control node includes the target CU or the target donor DU, send a third indication to the IAB node, where the third indication is used to indicate to route the second BAP PDU to the target donor DU.

[0268] Optionally, at least one of the first indication, the second indication, and the third indication is carried in a handover command or sent before the handover starts; or

[0269] At least one of the first indication, the second indication, and the third indication is sent after the handover is completed.

[0270] Optionally, the handover associated period includes a first period after the handover is completed, and the apparatus further includes:

[0271] A seventh sending module, configured to send an indication for stopping the execution of the data unit processing operation to the IAB node when the first period ends.

[0272] Optionally, when the handover associated period includes a period associated with the handover process of the IAB node from the original CU to the target CU, the third BAP PDU further includes a sixth indication, where the sixth indication is used to indicate that the third BAP PDU is generated according to the encryption information of the original CU, or is used to indicate that the third BAP PDU is generated according to the encryption information of the target CU.

[0273] Optionally, when the control node includes the target CU, the apparatus further includes:

[0274] An eighth sending module, configured to send the third BAP PDU to the original CU when the third BAP PDU is received and the sixth indication is used to indicate that the third BAP PDU is generated according to the encryption information of the original CU;

[0275] A first receiving module, configured to receive data obtained by decrypting the third BAP PDU sent by the original CU;

[0276] Or,

[0277] When the control node includes the original CU, the apparatus further includes:

[0278] A ninth sending module, configured to send the third BAP PDU to the target CU when the control node receives the third BAP PDU and the sixth indication is used to indicate that the third BAP PDU is generated according to the encryption information of the target CU;

[0279] A second receiving module, configured to receive data obtained by decrypting the third BAP PDU sent by the target CU.

[0280] Optionally, when the control node includes the target CU or the target donor DU, the apparatus further includes:

[0281] A discard module, configured to discard the abnormal BAP PDU when the control node receives an abnormal BAP PDU, where the abnormal BAP PDU carries a destination BAP address that does not match the BAP address of the control node and does not match the BAP address of the original donor DU or the original CU.

[0282] The data unit processing device provided by the embodiments of the present application can implement Figure 4 each process in the method embodiment, to avoid repetition, it will not be elaborated here, and it can improve the transmission performance of the IAB node.

[0283] It should be noted that the data unit processing device in the embodiments of the present application can be a device, or a component, an integrated circuit, or a chip in a control node.

[0284] See Figure 9 , Figure 9 is a structural diagram of a network node provided by an embodiment of the present invention. As Figure 9 shown, the network node 900 includes: a processor 901, a transceiver 902, a memory 903, and a bus interface, where:

[0285] In one embodiment, the above network node is an IAB node, specifically as follows:

[0286] The processor 901 or the transceiver 902 is configured to perform data unit processing operations during a handover association period, where the data unit processing operations include at least one of the following:

[0287] Retain the first BAP protocol data unit PDU that does not have a matching backhaul adaptation protocol BAP routing configuration in the IAB node;

[0288] Route the second BAP PDU with the target BAP address being the original host donor distribution unit DU to the target donor DU;

[0289] Process according to a BAP routing identifier in the third BAP PDU, where the third BAP PDU includes two BAP routing identifiers.

[0290] Optionally, the handover association period includes one of the following:

[0291] The period associated with the handover process of the IAB node when the same central control unit CU switches from the original donor DU to the target donor DU;

[0292] The period associated with the handover process of the IAB node from the original CU to the target CU, where the original donor DU is the DU in the original CU, and the target donor DU is the DU in the target CU.

[0293] Optionally, the transceiver 902 is further configured to at least one of the following:

[0294] The IAB node receives a first indication sent by the original CU or the original donor DU, where the first indication is used to indicate stopping discarding the first BAP PDU;

[0295] The IAB node receives a second indication sent by the target CU or the target donor DU, where the second indication is used to indicate stopping discarding the first BAP PDU;

[0296] The IAB node receives a third indication sent by the target CU or the target donor DU, where the third indication is used to indicate routing the second BAP PDU to the target donor DU.

[0297] Optionally, at least one of the first indication, the second indication, and the third indication is carried in a handover command or received before the handover starts; or

[0298] At least one of the first indication, the second indication, and the third indication is received after the handover is completed.

[0299] Optionally, the handover-related period includes a first period after the handover is completed, and the transceiver 902 is further configured to:

[0300] When the first period ends, receive a fourth indication sent by the target CU or the target donor DU, where the fourth indication stops executing the data unit processing operation.

[0301] Optionally, the handover-related period includes a first period after the handover is completed. During the first period, the IAB node retains the BAP address of the original donor DU, and after the first period ends, the IAB node removes the BAP address of the original donor DU.

[0302] Optionally, routing the second BAP PDU with the target BAP address being the original host donor distribution unit DU to the target donor DU includes:

[0303] Performing a rewriting operation on the second BAP PDU and routing the rewritten second BAP PDU to the target donor DU, where the rewriting operation includes at least one of the following:

[0304] Rewriting the first routing identifier of the second BAP PDU to a second routing identifier, where the first routing identifier is used to route to the original donor DU, and the second routing identifier is used to route to the target donor DU;

[0305] Rewrite the BAP path of the second BAP PDU to the BAP path to the target donor DU.

[0306] Optionally, the processing based on a BAP routing identifier in the third BAP PDU includes one of the following:

[0307] Modify the third BAP PDU to a BAP PDU that only includes one BAP routing identifier, and transmit it according to the one BAP routing identifier;

[0308] When the third BAP PDU includes a BAP routing identifier for routing to the original donor DU and a BAP routing identifier for the target donor DU, route and transmit the third BAP PDU to the original donor DU or the target donor DU;

[0309] When a BAP address carried by a BAP routing identifier included in the third BAP PDU is the BAP address of the IAB node, cache the BAP PDU or deliver a service data unit SDU carried by the BAP PDU to the upper layer.

[0310] Optionally, the third BAP PDU further includes a fifth indication, and the fifth indication is used to indicate that the third BAP PDU includes two BAP routing identifiers.

[0311] Optionally, when the handover association period includes a period associated with the handover process of the IAB node from the original CU to the target CU, the third BAP PDU further includes a sixth indication, and the sixth indication is used to indicate that the third BAP PDU is generated according to the encryption information of the original CU, or is used to indicate that the third BAP PDU is generated according to the encryption information of the target CU.

[0312] Optionally, when the third BAP PDU is a downlink BAP PDU, the transceiver 902 is further configured to:

[0313] Indicate to the terminal that the third BAP PDU is generated according to the encryption information of the original CU, or indicate that the third BAP PDU is generated according to the encryption information of the target CU.

[0314] Optionally, the third BAP PDU includes:

[0315] A BAP routing identifier that only includes a BAP address;

[0316] A BAP routing identifier that includes a BAP address and a BAP path.

[0317] Optionally, the third BAP PDU includes a third BAP routing identifier configured by the original CU and a fourth BAP routing identifier configured by the target CU, and the order of the third BAP routing identifier and the fourth BAP routing identifier is used to indicate that the third BAP PDU is generated by the original CU or the target CU.

[0318] Optionally, the processor 901 or the transceiver 902 is further configured to perform at least one of the following:

[0319] When the IAB node receives a fourth BAP PDU, route the fourth BAP PDU to the target donor DU, where the target BAP address of the fourth BAP PDU matches the BAP address of the target donor DU;

[0320] When the IAB node receives a fifth BAP PDU, discard the fifth BAP PDU, where the target BAP address of the fifth BAP PDU does not match the BAP address of the original donor DU and does not match the BAP address of the target donor DU;

[0321] When the IAB node receives a sixth BAP PDU, discard the sixth BAP PDU, where the target BAP address of the sixth BAP PDU does not match at least one of the following:

[0322] The old BAP address of the IAB node that can be reached by the BAP routing configuration of the IAB node;

[0323] The new BAP address of the IAB node that can be reached by the BAP routing configuration of the IAB node;

[0324] The BAP address of the IAB node.

[0325] In one embodiment, the above network node is a control node, specifically as follows:

[0326] The processor 901 or the transceiver 902 is configured to send indication information to the self-backhaul IAB node, where the indication information is used to instruct the IAB node to perform data unit processing operations during the handover association period, and the data unit processing operations include at least one of the following:

[0327] Retain the first BAP protocol data unit (PDU) for which there is no matching backhaul adaptation protocol BAP routing configuration in the IAB node;

[0328] Route the second BAP PDU with the target BAP address being the original host donor distribution unit (DU) to the target donor DU;

[0329] Process according to a BAP routing identifier in the third BAP PDU, where the third BAP PDU includes two BAP routing identifiers.

[0330] Optionally, the control node includes one of the following:

[0331] The original donor DU, the target donor DU, the original control unit CU, the target CU.

[0332] Optionally, when the control node includes the original CU or the original donor DU, the transceiver 902 is further configured to:

[0333] Send the BAP address of the original donor DU to the target donor DU or the target CU.

[0334] Optionally, when the control node includes the original CU or the original donor DU, the transceiver 902 is further configured to:

[0335] Send a request message to the target donor DU or the target CU, where the request message is used to request to perform a lossless data handover;

[0336] The sending of the indication information to the self-backhaul IAB node includes:

[0337] When the control node receives a response message from the target donor DU or the target CU agreeing to the request message, send indication information to the self-backhaul IAB node.

[0338] Optionally, the transceiver 902 is further configured to perform at least one of the following:

[0339] When the control node includes the original CU or the original donor DU, send a first indication to the IAB node, where the first indication is used to indicate to stop discarding the first BAP PDU;

[0340] When the control node includes the target CU or the target donor DU, send a second indication to the IAB node, where the second indication is used to indicate to stop discarding the first BAP PDU;

[0341] When the control node includes the target CU or the target donor DU, send a third indication to the IAB node, where the third indication is used to indicate to route the second BAP PDU to the target donor DU.

[0342] Optionally, at least one of the first indication, the second indication, and the third indication is carried in the handover command or sent before the handover starts; or

[0343] At least one of the first indication, the second indication, and the third indication is sent after the handover is completed.

[0344] Optionally, the handover-related period includes a first period after the handover is completed, and the transceiver 902 is further configured to:

[0345] When the first period ends, the control node sends an indication to the IAB node to stop executing the data unit processing operation.

[0346] Optionally, when the handover-related period includes the period associated with the handover process of the IAB node switching from the original CU to the target CU, the third BAP PDU further includes a sixth indication, where the sixth indication is used to indicate that the third BAP PDU is generated according to the encryption information of the original CU, or is used to indicate that the third BAP PDU is generated according to the encryption information of the target CU.

[0347] Optionally, when the control node includes the target CU, the transceiver 902 is further configured to:

[0348] When the control node receives the third BAP PDU and the sixth indication is used to indicate that the third BAP PDU is generated according to the encryption information of the original CU, the control node sends the third BAP PDU to the original CU;

[0349] The control node receives the data for decrypting the third BAP PDU sent by the original CU;

[0350] Or,

[0351] When the control node includes the original CU, the method further includes:

[0352] When the control node receives the third BAP PDU and the sixth indication is used to indicate that the third BAP PDU is generated according to the encryption information of the target CU, the control node sends the third BAP PDU to the target CU;

[0353] The control node receives the data for decrypting the third BAP PDU sent by the target CU.

[0354] Optionally, when the control node includes the target CU or the target donor DU, the transceiver 902 is further configured to:

[0355] When the control node receives an abnormal BAP PDU, the abnormal BAP PDU is discarded, where the abnormal BAP PDU carries a destination BAP address that does not match the BAP address of the control node and does not match the BAP address of the original donor DU or the original CU.

[0356] Among them, the transceiver 902 is used to receive and send data under the control of the processor 901, and the transceiver 902 includes at least two antenna ports.

[0357] In Figure 9 In, the bus architecture may include any number of interconnected buses and bridges, specifically, various circuits represented by one or more processors represented by the processor 901 and the memory represented by the memory 903 are linked together. The bus architecture can also link together various other circuits such as peripheral devices, voltage regulators, and power management circuits, which are well known in the art, and therefore, will not be further described herein. The bus interface provides an interface. The transceiver 902 may be a plurality of components, that is, including a transmitter and a receiver, and provides a unit for communicating with various other devices on the transmission medium.

[0358] The processor 901 is responsible for managing the bus architecture and general processing, and the memory 903 may store data used by the processor 901 when executing operations.

[0359] Preferably, an embodiment of the present invention further provides an IAB node, including a processor 901, a memory 903, a program or instruction stored on the memory 903 and executable on the processor 901. When the program or instruction is executed by the processor 901, it implements each process of the above data unit processing method embodiment and can achieve the same technical effect. To avoid repetition, it will not be elaborated here.

[0360] Preferably, an embodiment of the present invention further provides a control node, including a processor 901, a memory 903, a program or instruction stored on the memory 903 and executable on the processor 901. When the program or instruction is executed by the processor 901, it implements each process of the above data unit processing method embodiment and can achieve the same technical effect. To avoid repetition, it will not be elaborated here.

[0361] An embodiment of the present application further provides a readable storage medium, on which a program or instruction is stored. When the program or instruction is executed by a processor, it implements the steps in the data unit processing method on the IAB node side provided by the embodiment of the present application.

[0362] An embodiment of this application also provides a program product. The program product is stored in a non-volatile storage medium and is executed by at least one processor to implement the steps in the data unit processing method provided by the embodiment of this application on the control node side.

[0363] Wherein, the processor is the processor in the terminal or network device described in the above embodiment. The readable storage medium includes computer-readable storage media, such as computer read-only memory (ROM), random access memory (RAM), magnetic disks, or optical discs, etc.

[0364] Another embodiment of this application provides a chip. The chip includes a processor and a communication interface. The communication interface is coupled to the processor. The processor is used to run programs or instructions to implement the various processes of the above data unit processing method embodiment and can achieve the same technical effects. To avoid repetition, it will not be elaborated here.

[0365] It should be understood that the chip mentioned in the embodiment of this application can also be referred to as a system-on-chip, system chip, chip system, or system-on-chip, etc.

[0366] It should be noted that in this article, the term "including", "comprising", or any other variant thereof is intended to cover non-exclusive inclusion, so that a process, method, article, or device including a series of elements not only includes those elements but also includes other elements not expressly listed, or further includes elements inherent to such process, method, article, or device. Without further limitation, an element defined by the statement "including one..." does not exclude the existence of additional identical elements in the process, method, article, or device including that element. In addition, it should be pointed out that the methods and devices in the embodiments of this application are not limited to performing functions in the order shown or discussed, and may also include performing functions in a substantially simultaneous manner or in the reverse order according to the functions involved. For example, the described methods may be performed in an order different from that described, and various steps may be added, omitted, or combined. Additionally, the features described with reference to certain examples may be combined in other examples.

[0367] Through the description of the above embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus a necessary general hardware platform. Of course, they can also be implemented by hardware, but in many cases, the former is a better implementation method. Based on such an understanding, the technical solution of the present application, in essence or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) and includes several instructions for causing a terminal (which can be a mobile phone, computer, server, air conditioner, or network device, etc.) to execute the methods described in various embodiments of the present application.

[0368] The embodiments of the present application have been described above in conjunction with the accompanying drawings. However, the present application is not limited to the above specific implementation manners. The above specific implementation manners are merely illustrative rather than restrictive. Under the inspiration of the present application, those of ordinary skill in the art can also make many forms without departing from the purpose of the present application and the scope protected by the claims, and all of them belong to the protection scope of the present application.

Claims

1. A data unit processing method, characterized in that, Including: During the handover association period, the self-backhaul IAB node performs data unit processing operations, where the data unit processing operations include: Routing the second BAP PDU with the target BAP address being the original host donor distribution unit (DU) to the target donor DU, where the second BAP PDU is the newly received BAP PDU; The method further includes: The IAB node receives a third indication sent by the target CU or the target donor DU, where the third indication is used to indicate routing the second BAP PDU to the target donor DU; Wherein, routing the second BAP PDU with the target BAP address being the original donor DU to the target donor DU includes: Performing a rewriting operation on the second BAP PDU and routing the rewritten second BAP PDU to the target donor DU, where the rewriting operation includes: Rewriting the BAP path of the second BAP PDU to the BAP path to the target donor DU.

2. The method according to claim 1, characterized in that, The handover association period includes one of the following: The period associated with the handover process when the same centralized control unit (CU) of the IAB node switches from the original donor DU to the target donor DU; The period associated with the handover process when the IAB node switches from the original CU to the target CU, where the original donor DU is the DU in the original CU and the target donor DU is the DU in the target CU.

3. The method according to claim 1, characterized in that, The third indication is carried in the handover command or received before the handover starts; or The third indication is received after the handover is completed.

4. The method according to claim 1, characterized in that The handover association period includes a first period after the handover is completed, and the method further includes: When the first period ends, the IAB node receives a fourth indication sent by the target CU or the target donor DU, where the fourth indication stops the execution of the data unit processing operation.

5. The method according to claim 1, wherein The handover association period includes a first period after the handover is completed. During the first period, the IAB node retains the BAP address of the original donor DU, and after the first period ends, the IAB node removes the BAP address of the original donor DU.

6. The method according to claim 1, characterized in that, The method further includes at least one of the following: When the IAB node receives a fourth BAP PDU, routing the fourth BAP PDU to the target donor DU, where the target BAP address of the fourth BAP PDU matches the BAP address of the target donor DU; When the IAB node receives a fifth BAP PDU, discarding the fifth BAP PDU, where the target BAP address of the fifth BAP PDU does not match the BAP address of the original donor DU and does not match the BAP address of the target donor DU; In the case that the IAB node receives the sixth BAP PDU, discard the sixth BAP PDU, where the destination BAP address of the sixth BAP PDU does not match at least one of the following: The old BAP address of the IAB node that can be reached by the BAP routing configuration of the IAB node; The new BAP address of the IAB node that can be reached by the BAP routing configuration of the IAB node; The BAP address of the IAB node.

7. A data unit processing method, characterized in that Including: The control node sends indication information to the self-backhaul IAB node, and the indication information is used to instruct the IAB node to perform data unit processing operations during the handover association period, where the data unit processing operations include: Route the second BAP PDU with the destination BAP address being the original host donor distribution unit (DU) to the target donor DU, and the second BAP PDU is the newly received BAP PDU; The method further includes: In the case that the control node includes the target CU or the target donor DU, the control node gives a third indication to the IAB node, and the third indication is used to instruct to route the second BAP PDU to the target donor DU; Wherein, routing the second BAP PDU with the destination BAP address being the donor DU to the target donor DU includes: Performing a rewriting operation on the second BAP PDU and routing the rewritten second BAP PDU to the target donor DU, where the rewriting operation includes: Rewriting the BAP path of the second BAP PDU to the BAP path to the target donor DU.

8. The method according to claim 7, wherein The control node includes one of the following: The original donor DU, the target donor DU, the original control unit (CU), the target CU.

9. The method according to claim 8, characterized in that In the case that the control node includes the original CU or the original donor DU, the method further includes: The control node sends the BAP address of the original donor DU to the target donor DU or the target CU.

10. The method according to claim 8, wherein In the case that the control node includes the original CU or the original donor DU, the method further includes: The control node sends a request message to the target donor DU or the target CU, and the request message is used to request to perform a lossless handover; The control node sending indication information to the self-backhaul IAB node includes: In the case that the control node receives a response message from the target donor DU or the target CU agreeing to the request message, the control node sends indication information to the self-backhaul IAB node.

11. The method according to claim 7, characterized in that, The third indication is carried in the handover command or sent before the handover starts; or At least one of the third indications is sent after the handover is completed.

12. The method according to claim 7, characterized in that, The handover association period includes a first period after the handover is completed, and the method further includes: At the end of the first period, the control node sends an indication for stopping the execution of the data unit processing operation to the IAB node.

13. The method according to claim 8, characterized in that, When the control node includes the target CU or the target donor DU, the method further includes: When the control node receives an abnormal BAP PDU, discarding the abnormal BAP PDU, where the abnormal BAP PDU carries a destination BAP address that does not match the BAP address of the control node and does not match the BAP address of the original donor DU or the original CU.

14. A data unit processing device, characterized in that, Including: An execution module, configured to perform a data unit processing operation during a handover association period, where the data unit processing operation includes: Routing a second BAP PDU with a target BAP address being the original host donor distribution unit DU to the target donor DU, where the second BAP PDU is a newly received BAP PDU; The apparatus further includes: A third receiving module, configured to receive a third indication sent by the target CU or the target donor DU, where the third indication is used to indicate routing the second BAP PDU to the target donor DU; Wherein, routing the second BAP PDU with a target BAP address being the donor DU to the target donor DU includes: Performing a rewriting operation on the second BAP PDU and routing the rewritten second BAP PDU to the target donor DU, where the rewriting operation includes: Rewriting the BAP path of the second BAP PDU to the BAP path to the target donor DU; Wherein, the IAB node includes the apparatus.

15. The device according to claim 14, characterized in that, The handover association period includes one of the following: The period associated with the handover process of the IAB node when the same central control unit CU hands over from the original donor DU to the target donor DU; The period associated with the handover process of the IAB node from the original CU to the target CU, where the original donor DU is the DU in the original CU and the target donor DU is the DU in the target CU.

16. A data unit processing device, characterized in that, Including: A first sending module, configured to send indication information to the self-backhaul IAB node, where the indication information is used to indicate that the IAB node performs a data unit processing operation during a handover association period, where the data unit processing operation includes: Routing a second BAP PDU with a target BAP address being the original host donor distribution unit DU to the target donor DU, where the second BAP PDU is a newly received BAP PDU; The apparatus further includes: A sixth sending module, configured to send a third indication to the IAB node when the control node includes the target CU or the target donor DU, where the third indication is used to indicate routing the second BAP PDU to the target donor DU; Wherein, routing the second BAP PDU with a target BAP address being the donor DU to the target donor DU includes: Perform a rewriting operation on the second BAP PDU and route the rewritten second BAP PDU to the target donor DU, where the rewriting operation includes: Rewrite the BAP path of the second BAP PDU to the BAP path to the target donor DU; Wherein, the control node includes the device.

17. The device according to claim 16, wherein When the control node includes the original CU or the original donor DU, the device further includes: A second sending module, configured to send a request message to the target donor DU or the target CU, where the request message is used to request to perform a lossless data handover; The first sending module is configured to, when the control node receives a response message from the target donor DU or the target CU agreeing to the request message, the control node sends indication information to the self-backhaul IAB node.

18. A self-backhauling IAB node, characterized in that, Comprising: A memory, a processor, and a program or instruction stored on the memory and executable on the processor, where when the program or instruction is executed by the processor, the steps in the data unit processing method according to any one of claims 1 to 6 are implemented.

19. A network node, characterized in that, Comprising: A memory, a processor, and a program or instruction stored on the memory and executable on the processor, where when the program or instruction is executed by the processor, the steps in the data unit processing method according to any one of claims 7 to 13 are implemented.

20. A readable storage medium, characterized in that, A program or instruction is stored on the readable storage medium, where when the program or instruction is executed by the processor, the steps in the data unit processing method according to any one of claims 1 to 6 are implemented, or when the program or instruction is executed by the processor, the steps in the data unit processing method according to any one of claims 7 to 13 are implemented.

Images