WO2020164614A1

WO2020164614A1 - Assistance information and method and apparatus for delivering same

Info

Publication number: WO2020164614A1
Application number: PCT/CN2020/075359
Authority: WO
Inventors: 韩锋; 杨旭东; 晋英豪; 杨水根; 谭巍
Original assignee: 华为技术有限公司
Priority date: 2019-02-15
Filing date: 2020-02-14
Publication date: 2020-08-20
Also published as: CN111585723A; CN111585723B

Abstract

Provided in the embodiments of the present application is an assistance information delivery method used for data packet duplication. The method comprises: a first radio access network RAN device determines first information, the first information comprising information of at least one logical channel in the first RAN device; and the first RAN device sends the first information to a second RAN device, the first information being used for indicating data packet duplication assistance information of the first RAN device. The present method can effectively support the second RAN device to implement data packet duplication decision making.

Description

Auxiliary information and its transmission method and device

Technical field

The present invention relates to the field of wireless communication, in particular to a method and device for auxiliary information and its transmission.

Background technique

With the rapid development of wireless communication technology, the fifth generation (5th Generation, 5G) wireless communication technology has become a hot spot in the industry. 5G will support diversified application requirements, including support for higher-rate experience and greater bandwidth access capabilities, lower latency and high-reliability information interaction, and the connection of larger-scale and low-cost machine-type communication devices. Entry and management, etc. In addition, 5G will support various vertical industry application scenarios such as the Internet of Vehicles, emergency communications, and industrial Internet.

Ultra-Reliable and Low Latency Communications (URLLC) is an important communication type in 5G. URLLC is a communication service that requires high latency and reliability. For example, it is used in scenarios such as unmanned driving and telemedicine. The user plane delay requirement of this type of service needs to reach 0.5ms for uplink/downlink transmission; for 32-byte transmission, the reliability needs to reach 1-10 ^-5 when the user plane delay is 1ms. In order to support the URLLC service, the same data packet can be repeatedly transmitted on the air interface to improve the reliability and robustness of data transmission. For example, the terminal device can be wirelessly connected to two base stations at the same time, and transmit the same data packet simultaneously through its wireless links with the two base stations. How to make full use of the capabilities of the base station to achieve high-efficiency repetitive transmission, there is currently no appropriate solution.

Summary of the invention

The embodiment of the present application provides an auxiliary information and a method for transferring it, which effectively supports the RAN device to make a data packet repetition decision.

The following describes the application from multiple aspects. It is easy to understand that the implementation manners of the following multiple aspects can be referred to each other.

In a first aspect, the present application provides an information transfer method for data packet repetition, including: a first radio access network RAN device determines first information, the first information includes information about at least one logical channel in the first RAN device Information; the first RAN device sends the first information to the second RAN device, and the first information is used to indicate that the data packet of the first RAN device repeats auxiliary information.

It can be seen that the method provided by the embodiment of the present application realizes that the first RAN device sends the data packet repetition auxiliary information to the second RAN device at the granularity of a logical channel, so that the second RAN device can obtain richer information of the first RAN device. Make decisions about packet duplication more efficiently. For example, the second RAN device may decide to activate one or more logical channels of the first RAN device to perform data packet repetition according to the data packet repetition auxiliary information.

In a possible implementation manner, the information of the at least one logical channel includes at least one of the following information: the logical channel identifier of the at least one logical channel, the logical channel index of the at least one logical channel, and the at least one logical channel The wireless quality auxiliary information of the at least one logical channel, the tunnel identifier of the at least one tunnel corresponding to the at least one logical channel, the tunnel index of the at least one tunnel, and the downlink tunnel transport layer address and the tunnel endpoint identifier TEID of the at least one tunnel. Among them, one logical channel corresponds to one tunnel.

In a possible implementation manner, the first information is assistance information data, and the assistance information data includes packet data convergence layer protocol PDCP duplication activation suggestion (PDCP duplication activation suggestion) and radio quality assistance information (radio At least one of quality assistance information).

Using the auxiliary information data of the existing standard to transfer the repeated auxiliary information of the data packet can be better compatible with the existing standard.

In a possible implementation manner, the PDCP repeated activation suggestion is used to indicate the at least one logical channel or the at least one tunnel where the activation data packet suggested by the first RAN device is repeated.

In a possible implementation manner, the wireless quality assistance information includes wireless quality assistance information of the at least one logical channel of the first RAN device, or wireless quality assistance information of at least one logical channel corresponding to the at least one tunnel.

In a possible implementation, the PDCP repeated activation suggestion is used to indicate that the at least one logical channel or the at least one tunnel in which the activation data packet suggested by the first RAN device is repeated includes: the PDCP repeated activation suggestion includes at least two One bit of information, and the at least two bits of information are used to indicate the at least one logical channel or the at least one tunnel in which the activation data packet suggested by the first RAN device is repeated.

By modifying the PDCP repeated activation suggestion field of the auxiliary information data in the existing standard, the identification information of the activated logical channel or tunnel can be transmitted with the smallest possible change and information overhead.

In a possible implementation manner, the second RAN device is a managed PDCP entity node, and the first RAN device is a corresponding node; or the second RAN device is a centralized unit CU, and the first RAN device is a distributed unit DU .

In a possible implementation manner, the first RAN device receives the downlink data packet sent by the second RAN device through the at least one tunnel. In the case that the first RAN device receives the downlink data packet sent by the second RAN device through at least two tunnels, the downlink data packet has the same PDCP sequence number.

It can be seen that the first RAN device receives the downlink data packet from the second RAN device through the corresponding tunnel, which can ensure that the corresponding RLC entity in the first RAN device correctly receives the data packet that needs to be repeated.

In a possible implementation manner, that the first RAN device sends the first information to the second RAN device includes: the first RAN device sends the first information to the second RAN device via a third RAN device.

In a possible implementation manner, the second RAN device is a centralized unit control plane network element CU-CP, the first RAN device is a distributed unit DU, and the third RAN device is a centralized unit user plane network element CU-CP. UP.

In a possible implementation manner, the first RAN device receives the downlink data packet sent by the third RAN device through the at least one tunnel. In the case where the first RAN device receives the downlink data packet sent by the third RAN device through at least two tunnels, the downlink data packet has the same PDCP sequence number.

It can be seen that when the second RAN device only performs the control plane function, the first RAN device receives the downlink data packet from the third RAN device performing the user plane function through the corresponding tunnel, which can ensure the corresponding RLC in the first RAN device The entity correctly receives data packets that need to be repeated.

In a second aspect, the present application provides an information transfer method for data packet repetition, including: a first radio access network RAN device determines first information, the first information includes at least one logical channel group in the first RAN device The one logical channel group includes at least one logical channel; the first RAN device sends the first information to the second RAN device, and the first information is used to indicate the data packet repetition auxiliary information of the first RAN device.

It can be seen that the method provided in the embodiments of the present application realizes that the first RAN device sends the data packet repetition auxiliary information to the second RAN device at the granularity of a logical channel group, so that the second RAN device can obtain richer information of the first RAN device. The decision of data packet repetition can be made more effectively. For example, the second RAN device may decide to activate a certain logical channel group of the first RAN device for data packet repetition according to the data packet repetition auxiliary information. In addition, the granularity of logical channel groups is used to form data packets to repeat auxiliary information, which can effectively reduce information overhead.

In a possible implementation manner, the information of the at least one logical channel group includes at least one of the following information: the logical channel group identifier of the at least one logical channel group, the logical channel group index of the at least one logical channel group, The wireless quality auxiliary information of the at least one logical channel group, the tunnel identifier of the at least one tunnel group corresponding to the at least one logical channel group, the tunnel group index of the at least one tunnel group, and the downlink tunnel transport layer address of the at least one tunnel group And the tunnel endpoint identification TEID. Among them, a logical channel group corresponds to a tunnel group.

In a possible implementation, a logical channel group may be any combination of logical channels in the first RAN device; or, a tunnel group may be any combination of tunnels in the first RAN device.

In a possible implementation manner, a logical channel group can be any combination of one or more specific logical channels in the first RAN device and other logical channels; or, a tunnel group can be one of the first RAN device. Or any combination of multiple specific tunnels and other tunnels.

It can be seen that the division of logical channel groups or tunnel groups can be flexible to adapt to network applications in various scenarios.

In a possible implementation manner, the first information is assistance information data, and the assistance information data includes PDCP duplication activation suggestion (PDCP duplication activation suggestion) and radio quality assistance information (radio At least one of quality assistance information).

In a possible implementation manner, the PDCP repeated activation suggestion is used to indicate the at least one logical channel group or the at least one tunnel group in which the activation data packet suggested by the first RAN device is repeated.

In a possible implementation manner, the radio quality auxiliary information includes radio quality auxiliary information of the at least one logical channel group of the first RAN device, or radio quality of at least one logical channel group corresponding to the at least one tunnel group Supplementary information.

In a possible implementation, the PDCP repeated activation suggestion is used to indicate that the at least one logical channel group or the at least one tunnel group in which the activation data packet suggested by the first RAN device is repeated includes: the PDCP repeated activation suggestion includes At least two bits of information, where the at least two bits of information are used to indicate the at least one logical channel group or the at least one tunnel group in which the activation data packet suggested by the first RAN device is repeated.

In a possible implementation manner, the wireless quality auxiliary information of the at least one logical channel group includes the wireless quality auxiliary information of each logical channel in the at least one logical channel group or the wireless quality auxiliary information of each logical channel is mathematically calculated Wireless quality auxiliary information.

By modifying the PDCP repeated activation suggestion field of the auxiliary information data in the existing standard, the identification information of the activated logical channel group or tunnel group can be transmitted with the smallest possible change and information overhead.

In a possible implementation manner, the first RAN device receives the downlink data packet sent by the second RAN device through the at least one tunnel group. In a case where the first RAN device receives the downlink data packet sent by the second RAN device through at least two tunnels in the at least one tunnel group, the downlink data packet has the same PDCP sequence number.

It can be seen that the first RAN device receives the downlink data packet from the second RAN device through the corresponding tunnel group, which can ensure that the corresponding RLC entity in the first RAN device correctly receives the data packet that needs to be repeated.

In a possible implementation manner, the first RAN device receives the downlink data packet sent by the third RAN device through the at least one tunnel group. In a case where the first RAN device receives the downlink data packet sent by the third RAN device through at least two tunnels in the at least one tunnel group, the downlink data packet has the same PDCP sequence number.

It can be seen that when the second RAN device only performs the control plane function, the first RAN device receives the downlink data packet from the third RAN device performing the user plane function through the corresponding tunnel group, which can ensure that the corresponding The RLC entity correctly receives data packets that need to be repeated.

In a third aspect, this application provides an information transfer method for data packet repetition, including: a second radio access network RAN device receives first information sent by a first RAN device, and the first information includes the first RAN device The first information is used to indicate the data packet repetition auxiliary information of the first RAN device; the second RAN device decides the data packet repetition according to the first information.

It can be seen that the method provided in the embodiments of the present application realizes that the second RAN device receives the data packet repetition auxiliary information sent by the first RAN device at the granularity of a logical channel, so that the second RAN device can obtain richer information of the first RAN device. The decision of data packet repetition can be made more effectively. For example, the second RAN device may decide to activate one or more logical channels of the first RAN device to perform data packet repetition according to the data packet repetition auxiliary information.

In a possible implementation manner, the second RAN device decides data packet repetition according to the first information, including: the second RAN device decides to activate the at least one logical channel or the data of the at least one tunnel according to the first information The package is repeated.

It can be seen that the second RAN device makes a finer data packet repetition decision with the granularity of the logical channel or tunnel, and can better utilize the resources of the first RAN device for data packet repetition.

In a possible implementation manner, the second RAN device sends a downlink data packet to the first RAN device through the at least one tunnel. In the case where the second RAN device sends a downlink data packet to the first RAN device through at least two tunnels, the downlink data packet has the same PDCP sequence number.

It can be seen that the second RAN device sends a downlink data packet to the first RAN device through the corresponding tunnel, which can ensure that the corresponding RLC entity in the first RAN device correctly receives the data packet that needs to be repeated.

In a possible implementation manner, that the second RAN device receives the first information sent by the first RAN device includes: the second RAN device receives the first information sent by the first RAN device via a third RAN device.

In a possible implementation manner, the second RAN device sends data packet repeated transmission information to the third RAN device, where the data packet repeated transmission information includes transmission information of the at least one logical channel, and the data packet is used for repeated transmission information. Instruct the third RAN device to send downlink data to the first RAN device according to the data packet repeated transmission information.

In a possible implementation manner, the transmission information of the at least one logical channel includes at least one of the following information: the logical channel identifier of the at least one logical channel, the logical channel index of the at least one logical channel, the at least one logical channel The tunnel identifier of the at least one tunnel corresponding to the channel, the tunnel index of the at least one tunnel, and the downlink tunnel transport layer address and TEID of the at least one tunnel.

It can be seen that when the second RAN device only performs control plane functions, the second RAN device instructs the third RAN device performing user plane functions to send downlink data packets to the first RAN device through the corresponding tunnel, which can ensure that the first RAN The corresponding RLC entity in the device correctly receives the data packets that need to be repeated.

In a fourth aspect, this application provides an information transfer method for data packet repetition, including: a second radio access network RAN device receives first information sent by a first RAN device, and the first information includes the first RAN device Information of at least one logical channel group in the RAN, the logical channel group includes at least one logical channel; the first information is used to indicate the data packet repetition auxiliary information of the first RAN device; the second RAN device makes a decision based on the first information The data packet is duplicated.

It can be seen that the method provided by the embodiments of the present application enables the second RAN device to receive the data packet repetition auxiliary information sent by the first RAN device at the granularity of the logical channel group, so that the second RAN device can obtain richer information of the first RAN device , Can make the decision of data packet repetition more effectively. For example, the second RAN device may decide to activate one or more logical channels of the first RAN device to perform data packet repetition according to the data packet repetition auxiliary information. In addition, the granularity of logical channel groups is used to form data packets to repeat auxiliary information, which can effectively reduce information overhead.

In a possible implementation manner, the information of the at least one logical channel group includes at least one of the following information: the logical channel group identifier of the at least one logical channel group, the logical channel group index of the at least one logical channel group, The wireless quality auxiliary information of the at least one logical channel group, the tunnel group identifier of the at least one tunnel group corresponding to the at least one logical channel group, the tunnel group index of the at least one tunnel group, and the downlink tunnel transmission layer of the at least one tunnel group Address and tunnel endpoint identification TEID. Among them, a logical channel group corresponds to a tunnel group.

In a possible implementation manner, the second RAN device decides to repeat the data packet according to the first information, including: the second RAN device decides to activate the at least one logical channel group or the at least one tunnel group according to the first information The packet is duplicated.

It can be seen that the second RAN device makes a finer data packet repetition decision at the granularity of the logical channel group or tunnel group, and can better utilize the resources of the first RAN device for data packet repetition.

In a possible implementation manner, the second RAN device sends a downlink data packet to the first RAN device through the at least one tunnel group. In a case where the second RAN device sends a downlink data packet to the first RAN device through at least two tunnels in the at least one tunnel group, the downlink data packet has the same PDCP sequence number.

It can be seen that the second RAN device sends a downlink data packet to the first RAN device through the corresponding tunnel group, which can ensure that the corresponding RLC entity in the first RAN device correctly receives the data packet that needs to be repeated.

In a possible implementation manner, the second RAN device sends data packet repeated transmission information to the third RAN device, the data packet repeated transmission information includes transmission information of the at least one logical channel group, and the data packet repeated transmission information It is used to instruct the third RAN device to send downlink data to the first RAN device according to the data packet repeated transmission information.

In a possible implementation manner, the transmission information of the at least one logical channel group includes at least one of the following information: the logical channel group identifier of the at least one logical channel group, the logical channel group index of the at least one logical channel group , The tunnel group identifier of the at least one tunnel group corresponding to the at least one logical channel group, the tunnel group index of the at least one tunnel group, and the downlink tunnel transport layer address and TEID of the at least one tunnel group.

It can be seen that when the second RAN device only performs the control plane function, the second RAN device instructs the third RAN device performing the user plane function to send downlink data packets to the first RAN device through the corresponding tunnel group, which can ensure that the first The corresponding RLC entity in the RAN device correctly receives the data packets that need to be repeated.

In a fifth aspect, the present application provides an information transfer method for data packet repetition, including: a third radio access network RAN device receives first information sent by a first RAN device, and the first information includes the first RAN device Information of at least one logical channel in the RAN; the first information is used to indicate the data packet repetition auxiliary information of the first RAN device; the third RAN device sends the first information to the second RAN device.

It can be seen that the method provided in the embodiments of the present application realizes that the first RAN device sends the data packet repetition auxiliary information to the second RAN device through the third RAN device at the granularity of a logical channel, so that the second RAN device can obtain the update of the first RAN device. Abundant information can make data packet repetition decisions more effectively.

In a possible implementation manner, the third RAN device receives the data packet repeated transmission information sent by the second RAN device, the data packet repeated transmission information includes transmission information of the at least one logical channel, and the data packet repeated transmission information It is used to instruct the third RAN device to send downlink data to the first RAN device according to the data packet repeated transmission information.

In a possible implementation manner, the transmission information of the at least one logical channel includes at least one of the following information: the logical channel identifier of the at least one logical channel, the logical channel index of the at least one logical channel, and the at least one logical channel The tunnel identifier of the at least one tunnel corresponding to the channel, the tunnel index of the at least one tunnel, and the downlink tunnel transport layer address and TEID of the at least one tunnel.

In a possible implementation manner, the third RAN device sends a downlink data packet to the first RAN device through the at least one tunnel. In the case where the third RAN device sends a downlink data packet to the first RAN device through at least two tunnels, the downlink data packet has the same PDCP sequence number.

It can be seen that when the second RAN device only performs the control plane function, the third RAN device performing the user plane function receives the instruction from the second RAN device and sends the downlink data packet to the first RAN device through the corresponding tunnel, which can guarantee The corresponding RLC entity in the first RAN device correctly receives the data packets that need to be repeated.

In a sixth aspect, this application provides an information transfer method for data packet repetition, including: a third radio access network RAN device receives first information sent by a first RAN device, and the first information includes the first RAN device Information of at least one logical channel group in the RAN, the logical channel group includes at least one logical channel; the first information is used to indicate the data packet repetition auxiliary information of the first RAN device; the third RAN device sends to the second RAN device The first information.

It can be seen that the method provided by the embodiment of the present application realizes that the first RAN device sends the data packet repetition assistance information to the second RAN device through the third RAN device at the granularity of logical channel groups, so that the second RAN device can obtain the first RAN device. Richer information enables more effective decision-making on data packet repetition. In addition, the granularity of logical channel groups is used to form data packets to repeat auxiliary information, which can effectively reduce information overhead.

In a possible implementation, the wireless quality auxiliary information of the at least one logical channel group includes the wireless quality auxiliary information of each logical channel in the at least one logical channel group or the wireless quality auxiliary information of each logical channel is subjected to a mathematical operation Wireless quality auxiliary information.

In a possible implementation manner, the third RAN device receives the data packet repeated transmission information sent by the second RAN device, the data packet repeated transmission information includes transmission information of the at least one logical channel group, and the data packet is repeatedly transmitted The information is used to instruct the third RAN device to send downlink data to the first RAN device according to the data packet repeated transmission information.

In a possible implementation manner, the third RAN device sends a downlink data packet to the first RAN device through the at least one tunnel group. In a case where the third RAN device sends a downlink data packet to the first RAN device through two tunnels of the at least one tunnel group, the downlink data packet has the same PDCP sequence number.

It can be seen that when the second RAN device only performs the control plane function, the third RAN device performing the user plane function receives the instruction from the second RAN device, and sends the downlink data packet to the first RAN device through the corresponding tunnel group. Ensure that the corresponding RLC entity in the first RAN device correctly receives data packets that need to be repeated.

In the seventh aspect, an access network RAN device is provided, which is used to implement the first aspect or any one of the possible implementation manners of the first aspect, or the second aspect or any one of the possible implementation manners of the second aspect Specifically, the RAN device may include a method for executing the method in the first aspect or any one of the possible implementation manners of the first aspect, or the second aspect or any one of the possible implementation manners of the second aspect unit.

In the eighth aspect, another access network RAN device is provided, which is used to implement the third aspect or any possible implementation manner of the third aspect, or any possible implementation manner of the fourth aspect or the fourth aspect Specifically, the RAN device may include a method for executing the third aspect or any one of the possible implementation manners of the third aspect, or any one of the fourth aspect or the fourth aspect. Unit.

The ninth aspect provides yet another access network RAN device, which is used to implement the fifth aspect or any possible implementation manner of the fifth aspect, or the sixth aspect or any possible implementation manner of the sixth aspect Specifically, the RAN device may include a method for executing the fifth aspect or any possible implementation manner of the fifth aspect, or the sixth aspect or any possible implementation manner of the sixth aspect Unit.

In a tenth aspect, a computer program product is provided, the computer program product includes: computer program code, when the computer program code is used by a communication unit, a processing unit or a transceiver of a communication device (for example, an access network device or a terminal device) When the processor is running, the communication device is caused to execute the method in any one of the first to sixth aspects or any one of the first to sixth aspects.

In an eleventh aspect, a computer-readable storage medium is provided, and the computer-readable storage medium stores a program that enables a computer to execute any possible implementation of the first to sixth aspects or the first to sixth aspects The method in the way.

These and other aspects of the present invention will be more concise and understandable in the description of the following embodiment(s).

Description of the drawings

The following briefly introduces the drawings used in the embodiments of the application or in the description of the prior art:

Fig. 1 is a schematic diagram of a wireless communication system provided by an embodiment of the present application;

FIG. 2 is a schematic diagram of the architecture of a gNB divided into CU and DU according to an embodiment of the present application;

FIG. 3 is a schematic diagram of a protocol stack of a user plane layer 2 of a RAN device provided by an embodiment of the present application;

4 is a schematic diagram of a user plane L2 protocol stack for data packet repetition when each RAN device has a carrier aggregation function in a dual connectivity scenario according to an embodiment of the present application;

FIG. 5 is a schematic flowchart of an improved auxiliary information and its transmission method in a dual connection scenario provided by an embodiment of the present application;

6 is a schematic diagram of a user plane layer 2 protocol stack used for data packet repetition under a RAN device architecture divided into CU and DU according to an embodiment of the present application;

FIG. 7 is a schematic flowchart of an improved auxiliary information and its transmission method in another dual-connection scenario provided by an embodiment of the present application;

FIG. 8 is a schematic flowchart of another improved auxiliary information and its transmission method in a dual-connection scenario provided by an embodiment of the present application;

FIG. 9 is a schematic block diagram of a first network device according to an embodiment of the present application;

FIG. 10 is another schematic block diagram of the first network device according to an embodiment of the present application;

FIG. 11 is a schematic block diagram of a second network device according to an embodiment of the present application;

FIG. 12 is another schematic block diagram of a second network device according to an embodiment of the present application;

FIG. 13 is a schematic block diagram of a third network device according to an embodiment of the present application;

FIG. 14 is another schematic block diagram of a third network device provided by an embodiment of the present application.

detailed description

The embodiments of the present application will be described below in conjunction with the drawings in the embodiments of the present application.

In this application, the word "exemplary" is used to mean "serving as an example, illustration, or illustration." Any embodiment described as "exemplary" in this application is not necessarily construed as being more preferred or advantageous over other embodiments. In order to enable any person skilled in the art to implement and use the present invention, the following description is given. In the following description, the details are listed for the purpose of explanation. It should be understood that those of ordinary skill in the art may realize that the present invention can also be implemented without using these specific details. In other instances, well-known structures and processes will not be elaborated to avoid unnecessary details to obscure the description of the present invention. Therefore, the present invention is not intended to be limited to the illustrated embodiments, but is consistent with the widest scope that conforms to the principles and features disclosed in this application.

The terms "first", "second", "third", "fourth", etc. (if any) in the specification and claims of this application and the above-mentioned drawings are used to distinguish similar objects, without having to use To describe a specific order or sequence. It should be understood that the data used in this way can be interchanged under appropriate circumstances so that the embodiments of the present application described herein can be implemented in a sequence other than those illustrated or described herein. In addition, the terms "including" and "having" and any variations of them are intended to cover non-exclusive inclusions. For example, a process, method, system, product or device that includes a series of steps or units is not necessarily limited to the clearly listed Those steps or units may include other steps or units that are not clearly listed or are inherent to these processes, methods, products, or equipment.

The terms "system" and "network" in this article are often used interchangeably in this article.

The technical solutions of the present invention will be described in detail below with specific embodiments. The following specific embodiments can be combined with each other, and the same or similar concepts or processes may not be repeated in some embodiments.

The technical solutions of the embodiments of this application can be applied to various wireless communication systems, such as: Long Term Evolution (LTE) system, fifth generation (5G) mobile communication system, new radio (NR) Communication system, next generation (NG) communication system and future mobile communication system, etc.

In a wireless communication system, a terminal device is connected to a radio access network (RAN) device through a wireless link, and communicates with other terminal devices via the core network (CN) device connected to the RAN device. Communication or access to wireless Internet, etc. Generally, a terminal device is wirelessly connected with a RAN device to achieve communication. Further, one terminal device can also be wirelessly connected with two RAN devices to achieve communication. Fig. 1 shows a schematic diagram of a wireless communication system 100 provided by an embodiment of the present application. Wherein, the terminal device 120 is wirelessly connected with the RAN device 140 through the air interface 160. Optionally, the wireless communication system further includes the terminal device 120 wirelessly connecting with the RAN device 142 through the air interface 162. In this case, the RAN device 140 is called a master node (master node, MN), and the RAN device 142 is called a secondary node (secondary node, SN). The RAN device 140 realizes the transmission of user plane (UP) data with the 5G core network (5G core, 5GC) 180 through the NG user plane (NG-U) interface, and through the NG control plane (NG control plane). ,NG-C) interface realizes the transmission of data with the control plane (CP) of 5GC. The RAN device 142 realizes the transmission of user plane data with the 5GC device 180 through the NG-U interface. The RAN device 140 and the RAN device 142 realize the interaction of control plane data through the Xn control plane (Xn-C) interface, and realize the interaction of user plane data through the Xn user plane (Xn-U) interface . Exemplarily, MN 140 is connected to the access and mobility management function (AMF) network element in 5GC 180 through the NG-C interface, and MN 140 and SN 142 are connected to 5GC 180 through the NG-U interface. The user plane function (UPF) network element connection in the In the case that the terminal device has a wireless connection with two RAN devices, the user plane data sent by the two RAN devices to the terminal device can be transmitted over the air interface through multiple wireless links, and each wireless link can transmit the same Data packets, thereby improving the reliability of data transmission.

In an actual system, the RAN device shown in Figure 1 can be a next-generation base station, such as next-generation Node B (gNB) or next-generation evolved Node B (ng-eNB) ), etc., it may also be an access point (AP) in a wireless local area network (Wireless Local Area Networks, WLAN), or an evolved base station (evolved Node B, eNB or eNodeB) in LTE, or a relay station or access point Point, or vehicle-mounted device, wearable device, and transmission and reception point (TRP), etc. It should be understood that the terminal device communicates with the RAN device through the transmission resources (for example, frequency domain resources, time domain resources, code domain resources, etc.) used by one or more cells managed by the RAN device, and the cell may belong to a macro cell (macro cell). cell, hypercell, or small cell, where the small cell may include: metro cell, micro cell, pico cell, femto cell Femto cells, etc. These small cells have the characteristics of small coverage and low transmit power, and are suitable for providing high-rate data transmission services. The terminal equipment in Figure 1 can also be referred to as user equipment (UE), access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile equipment, user terminal, terminal, wireless Communication equipment, user agent or user device. The terminal device can be a station (ST) in a WLAN, a cellular phone, a cordless phone, a SIP phone, a wireless local loop (WLL) station, a personal digital assistant (PDA) device, Handheld devices with wireless communication functions, relay devices, computing devices or other processing devices coupled to wireless modems, in-vehicle devices, wearable devices, and next-generation communication systems, such as terminal devices in 5G networks or future evolution of public land Terminal equipment in the mobile network (public land mobile network, PLMN) network, etc. As an example and not a limitation, in the embodiment of the present application, the terminal device may also be a wearable device. Wearable devices can also be called wearable smart devices. It is a general term for the application of wearable technology to intelligently design daily wear and develop wearable devices, such as glasses, gloves, watches, clothing and shoes. A wearable device is a portable device that is directly worn on the body or integrated into the user's clothes or accessories. Wearable devices are not only a hardware device, but also realize powerful functions through software support, data interaction, and cloud interaction. In a broad sense, wearable smart devices include full-featured, large-sized, complete or partial functions that can be achieved without relying on smart phones, such as smart watches or smart glasses, and only focus on a certain type of application function, and need to cooperate with other devices such as smart phones. Use, such as various smart bracelets and smart jewelry for physical sign monitoring.

Generally, the air interface user plane protocol stack of a RAN device includes at least a packet data convergence protocol (PDCP) layer, a radio link control (RLC) layer, and a media access control (media access control) layer. , MAC) layer and physical (PHY) layer; in the NR system, the air interface user plane protocol stack of the RAN device also includes a service data adaptation protocol (SDAP) layer, where the SDAP layer is the upper layer of the PDCP layer. The air interface control plane protocol stack of a RAN device includes a radio resource control (radio resource control, RRC) layer, a PDCP layer, an RLC layer, a MAC layer, and a PHY layer. It can be seen that the PDCP layer, RLC layer, MAC layer, and PHY layer have both control plane functions and user plane functions. Correspondingly, a terminal device also has an air interface user plane and control plane protocol stack corresponding to the RAN device.

Optionally, in a 5G system, a RAN device (such as gNB) can be further divided into a centralized unit (CU) and a distributed unit (DU) according to the protocol stack, where CU and DU can be separately Deploy on different physical devices. The CU is responsible for the operations of the RRC layer, the SDAP layer and the PDCP layer, and the DU is responsible for the operations of the RLC layer, the MAC layer and the PHY layer. Figure 2(a) shows an architecture of gNB divided into CU and DU. Among them, one gNB may include one CU and one or more DUs, and the one or more DUs are controlled by the one CU. A DU and CU are connected through a control plane interface (such as F1-C) for transmitting control plane data; a DU and CU are connected through a user plane interface (such as F1-U) for transmitting user plane data. Further, the CU can also be divided into a centralized unit of the control plane (that is, a centralized unit control plane CU-CP network element) and a centralized unit of the user plane (that is, a centralized unit user plane CU-UP network element), where CU-CP and CU -UP can also be deployed on different physical devices. CU-CP is responsible for the processing of the RRC layer and the control plane of the PDCP layer, and CU-UP is responsible for the processing of the user plane of the SDAP layer and the PDCP layer. Figure 2(b) shows an architecture of gNB divided into CU-CP, CU-UP and DU. Among them, one gNB may include one CU-CP, one or more CU-UPs, and one or more DUs. A CP-UP is only connected to one CU-CP through a control plane interface (such as E1) for transmission of control plane data; a DU is only connected to one CU-CP through a control plane interface (such as F1-C) for transmission Control plane data; under the control of CU-CP, a DU can be connected to one or more CU-UPs, and a CU-UP can also be connected to one or more DUs. CU-UP and DU are connected through a user plane interface (Such as F1-U) connection, used to transmit user plane data. It is worth noting that, in order to maintain the flexibility of the network, one DU or one CU-UP can also be connected to multiple CU-CPs. At this time, multiple CU-CPs serve as backups to each other; in practical applications, only one CU-CP is running at the same time. It should be understood that for the RAN device architecture divided into CU and DU, the protocol stack division method according to which the above-mentioned RAN device is divided into CU and DU is only exemplary, and the RAN device may also divide CU and DU according to other division methods. For example, the CU may be responsible for the operations of the RRC layer, SDAP layer, PDCP layer, and RLC layer, and the DU may be responsible for the MAC layer and PHY layer operations; or the CU may be responsible for the RRC layer and SDAP layer operations, and the DU may be responsible for the PDCP layer and RLC layer. , MAC layer and PHY layer operations, etc.; similarly, the protocol stack division method between CU-CP and CU-UP in the CU is also variable; the application does not specifically limit this.

To facilitate understanding, first introduce several concepts involved in the embodiments of the present application. It should be understood that the following conceptual explanations may be limited due to the specific circumstances of the embodiments of the present application, but it does not mean that the present application can only be limited to the specific circumstances. The following conceptual interpretations may also be accompanied by the specific circumstances of different embodiments. There will be differences.

Packet duplication: Packet duplication is the transmission of the same data packet between the RAN device and the terminal device through two wireless links. Generally, the data transmission between RAN equipment and terminal equipment is based on radio bearer (data radio bearer, DRB), that is, data with similar quality of service (QoS) requirements will be carried and transmitted on a DRB. . When a DRB is established, both the RAN device and the terminal device respectively configure the corresponding PDCP entity, RLC entity, and MAC entity for the DRB. When the RAN device wants to send a downlink data packet, the PDCP entity that processes the DRB carried by the downlink data packet will allocate a PDCP sequence number for the downlink data packet, and include the PDCP sequence number in the PDCP protocol data unit (protocol data unit). data unit, PDU) header and sent to the RLC entity for processing. When data packets are repeated, the PDCP entity corresponding to the DRB should be configured with two RLC entities, corresponding to two logical channels (LC). The PDCP entity will send two downlink data packets with the same PDCP sequence number to Two RLC entities, where the two RLC entities may be on one physical device or on different physical devices. Then, the common MAC entity or respective MAC entities corresponding to the two RLC entities schedule the downlink data packets with the same PDCP sequence number to multiple wireless links for transmission to the terminal device. After the terminal device receives downlink data packets through multiple wireless links, its PDCP entity performs repetitive detection. It should be understood that for data packet repetition of one DRB, the terminal device also has two RLC entities and one PDCP entity for the DRB. In one case, the terminal device correctly receives the PDCP PDU on one of the logical channels, and the PDCP entity performs subsequent processing such as data packet analysis on the received PDCP PDU; in another case, the terminal device performs subsequent processing such as packet analysis on the two logical channels. If the PDCP PDU is correctly received on the channel, the PDCP entity checks whether the two PDCP PDUs received are the same in their PDCP sequence numbers. If a PDCP PDU with the same PDCP sequence number is received, one of the PDCP PDUs is reserved, and the PDCP entity pairs The reserved PDCP PDU is subjected to subsequent processing such as data packet analysis.

Carrier aggregation: Carrier aggregation is that a RAN device communicates with a terminal device through multiple carriers. That is, the downlink data between the RAN device and the terminal device can be transmitted on multiple wireless links through multiple carriers. Increase the data transmission rate. Among them, one carrier may correspond to a cell. When a RAN device communicates with a terminal device through multiple carriers, the RAN device corresponds to a group of cells, and the RAN device may be called a cell group (CG). The multiple carriers used for communication between the RAN device and the terminal device and the bandwidth of each carrier are determined by the network configuration or the RAN device and the terminal device through negotiation. For the transmission of a DRB in a carrier aggregation scenario, the RAN device configures a PDCP entity, an RLC entity, and a MAC entity for the DRB, and an RLC entity corresponds to a logical channel. The MAC entity schedules each downlink data packet in the downlink data of the logical channel to different carriers and sends it to the terminal device. That is, the MAC entity schedules the downlink data of one logical channel to multiple carriers and sends it through multiple wireless links. To the terminal equipment. For data packet repetition in the carrier aggregation scenario, Figure 3(a) shows a schematic diagram of the protocol stack of the user plane layer 2 (L2) of the RAN device. Among them, the RRC entity of the RAN device configures one PDCP entity, two RLC entities, and one MAC entity for one DRB. The PDCP entity corresponding to the DRB sends PDCP PDUs with the same PDCP sequence number to two RLC entities, and transmits them to the MAC entity through two logical channels, and the MAC entity then transmits the downlink data packets of the two logical channels with the same PDCP sequence number. Scheduled to multiple carriers and sent to terminal equipment.

Dual connectivity (dual connectivity): Dual connectivity means that a terminal device simultaneously wirelessly communicates with two RAN devices (such as the RAN device 140 and the RAN device 142 in FIG. 1). The two RAN devices may use the same radio access technology (RAT), for example, both use NR; they may also use different RATs, for example, one uses LTE technology and the other uses NR technology. Each RAN device manages its own cell group, and each cell group has at least one cell. Figure 3(b) shows a schematic diagram of a user plane L2 protocol stack of a RAN device under dual connectivity. Among them, for a DRB, the RAN device corresponding to CG1 has a PDCP entity corresponding to the DRB, which is also called a host PDCP entity, and the RAN device corresponding to CG2 does not have a PDCP entity. Generally, a RAN device hosting a PDCP entity is called a hosting PDCP entity node, and a RAN device without a PDCP entity is called a corresponding node. In addition, the user plane L2 of the RAN device corresponding to CG1 also includes the RLC layer and the MAC layer; the user plane L2 of the RAN device corresponding to CG2 includes the RLC layer and the MAC layer, but does not include the PDCP layer. Exemplarily, for a DRB, the node hosting the PDCP entity configures an RLC entity and a MAC entity for itself and the corresponding node respectively. During downlink data transmission, the escrow PDCP entity node sends part of the downlink data of the DRB to the terminal device; in addition, the escrow PDCP entity node sends another part of the DRB downlink data through the tunnel between the escrow PDCP entity node and the corresponding node (tunnel) Sent to the corresponding node, and the corresponding node sends the other part of the downlink data to the terminal device. In the dual connectivity scenario, the managed PDCP entity node decides how to allocate downlink data for the DRB to the managed PDCP entity node and the corresponding node for transmission. The node hosting the PDCP entity can map part of the PDCP PDU of the DRB to its own logical channel, and map another part of the PDCP PDU of the DRB to the logical channel of the corresponding node. The host PDCP entity node and the respective MAC entities of the corresponding node can respectively map their respective logical channels. The downlink data of the channel is scheduled for transmission on the wireless link between the respective node and the terminal equipment. It is worth noting that in the process of establishing a dual connection, a tunnel is established between the managed PDCP entity node and the corresponding node so that the DRB data can be transmitted between the two nodes. Exemplarily, the node hosting the PDCP entity sends the uplink tunnel information (that is, the receiving endpoint information of the hosting PDCP entity as the receiving endpoint of the tunnel) to the corresponding node; the corresponding node sends the downlink tunnel information (that is, the corresponding node is the receiving endpoint of the tunnel). Receive endpoint information) and send it to the node hosting the PDCP entity. For downlink data transmission, the hosted PDCP entity node sends downlink data to the corresponding node according to the downlink tunnel information provided by the corresponding node; for uplink data transmission, the corresponding node sends uplink data to the hosted PDCP entity node according to the uplink tunnel information provided by the hosted PDCP entity node. The uplink tunnel information can be the uplink tunnel transport layer address of the tunnel and the tunnel endpoint identifier (TEID), the index of the tunnel, or the identifier or identity of the tunnel (identifier or identity, ID), etc.; accordingly, the downlink tunnel information It can be the downlink tunnel transport layer address and TEID of the tunnel, the index of the tunnel, or the identifier of the tunnel, etc. For data packet duplication in the dual-connection scenario, the PDCP entity hosting the PDCP entity node maps the data packets with the same PDCP sequence number to the logical channel hosting the PDCP entity node and the corresponding node, and the MAC entity of the respective node will download the data packet. The data packets are respectively dispatched to their respective wireless links and transmitted to the terminal equipment.

It is worth noting that in this article, the terms "RLC entity" and "logical channel" are used interchangeably.

In the prior art, when data packet repetition is implemented in a dual connection scenario, the corresponding node needs to provide auxiliary information to the managed PDCP entity node, so that the managed PDCP entity node can decide how to perform data packet repetition. Specifically, the auxiliary information may be a suggestion on whether the corresponding node activates data packet repetition or wireless quality information of the corresponding node. The inventor found that when the corresponding node has the carrier aggregation function, the corresponding node can be configured with multiple logical channels to further optimize the data packet repetition, but the corresponding node in the prior art cannot provide enough auxiliary information for the host PDCP entity node to perform data Package duplicate decision. To this end, the embodiments of the present application provide an improved technical solution for auxiliary information and its transmission. Further, the technical solution of the embodiment of the present application is also applied to a RAN device architecture with CU and DU, where the CU may also include the case where the CU-CP and CU-UP are separated.

This article specifically provides the following embodiments. The technical solutions of the present application will be described in detail with specific method embodiments in conjunction with FIGS. 4 to 8. The following specific embodiments can be combined with each other, and the same or similar concepts or processes may not be repeated in some embodiments. It should be understood that FIG. 5, FIG. 7 and FIG. 8 are schematic flowcharts of the communication method of the embodiment of the present application, showing the detailed communication steps or operations of the method, but these steps or operations are only examples. The example can also perform other operations or variations of the various operations in FIG. 5, FIG. 7, and FIG. 8. In addition, the steps in Figure 5, Figure 7 and Figure 8 can be performed in a different order from that shown in Figure 5, Figure 7 and Figure 8, and it may not be necessary to perform the steps in Figure 5, Figure 7 and Figure 8. All operations.

FIG. 4 shows a schematic diagram of a user plane L2 protocol stack for data packet repetition when each RAN device has a carrier aggregation function in a dual connectivity scenario according to an embodiment of the present application, where M is greater than or equal to 1 An integer, N is an integer greater than or equal to 2. The RAN device corresponding to CG1 has a PDCP entity, which is a managed PDCP entity node, and the RAN device corresponding to CG2 is a corresponding node. It is worth noting that, unlike Figure 3(b), for one DRB, multiple RLC entities are configured in the corresponding node. Correspondingly, multiple tunnels are established between the managed PDCP entity node and the corresponding node, among which there is a one-to-one correspondence between the RLC entity and the tunnel, that is, the number of tunnels between the managed PDCP entity node and the corresponding node and the number of the corresponding node The number of RLC entities is the same. In a possible implementation, the managed PDCP entity node configures multiple RLC entities of the corresponding node through the control plane signaling of the Xn-C interface; the managed PDCP entity node sends multiple uplink tunnel information to the corresponding node, and the corresponding node will The information of the corresponding multiple downlink tunnels is sent to the managed PDCP entity node; wherein, the number of RLC entities or tunnels of the corresponding node is determined by the managed PDCP entity node. In another possible implementation, the managed PDCP entity node corresponding to the DRB notifies the corresponding node of the maximum number of RLC entities or tunnels that it allows to establish through the control plane signaling of the Xn-C interface, and the corresponding node accordingly Determine the number of RLC entities or tunnels by itself, and send the corresponding downlink tunnel information to the node hosting the PDCP entity. This article does not specifically limit the number of RLC entities or tunnels of the corresponding node. Optionally, the configuration of the RLC entity or tunnel of the corresponding node by the hosting PDCP entity node is carried on a secondary node addition required (SN addition required) message or a secondary node modification required (SN modification required) message.

FIG. 5 shows a schematic flow chart of a method for auxiliary information and its transmission in a dual connection scenario provided by an embodiment of the present application. The method 500 can be applied to the information exchange between the MN 140 and the SN 142 shown in FIG. 1. Among them, when MN is hosting the PDCP entity node, SN is the corresponding node; when SN is hosting the PDCP entity node, MN is the corresponding node. The process described in Figure 5 includes the following steps:

501. The corresponding node determines that the data packet repeats auxiliary information.

The data packet repetition auxiliary information includes information of at least one logical channel of the corresponding node, and the data packet repetition auxiliary information is used to assist the hosting PDCP entity node to make a data packet repetition decision. Wherein, the information of the at least one logical channel may be at least one logical channel that the activation data packet suggested by the corresponding node is repeated, it may also be the wireless quality assistance information of at least one logical channel of the corresponding node, or the activation data packet suggested by the corresponding node The repeated at least one logical channel and the wireless quality auxiliary information corresponding to the at least one logical channel may also be at least one logical channel suggested by the corresponding node that the active data packet is repeated and other information related to the wireless quality auxiliary information corresponding to the at least one logical channel random combination. Exemplarily, for a DRB, three RLC entities RLC1, RLC2, and RLC3 (corresponding to three logical channels: LC1, LC2 and LC3) are configured in the corresponding node, that is, there are three tunnels between the managed PDCP entity node and the corresponding node , Corresponding to LC1, LC2 and LC3 are the first tunnel, the second tunnel and the third tunnel respectively. The logical channel where the activation data packet is repeated may be any one of LC1 to LC3, or any two of LC1 to LC3, or LC1 to LC3. In a possible implementation manner, the data packet repetition auxiliary information may include the logical channel identifier or the logical channel index of the logical channel that the corresponding node recommends to activate the data packet repetition. It is worth noting that since one logical channel corresponds to one tunnel, the data packet repetition auxiliary information may include information about at least one downlink tunnel that the corresponding node recommends to activate the data packet repetition. Specifically, the data packet repetition auxiliary information may include at least one tunnel identifier, or at least one tunnel index, or the transport layer address and TEID of at least one downlink tunnel that the corresponding node recommends to activate the data packet repetition. For example, when the corresponding node proposes to activate the data packet duplication of LC1 and LC3, the data packet duplication auxiliary information may include the first tunnel identifier and the third tunnel identifier, or the first tunnel index and the third tunnel index, or the first downlink tunnel The transport layer address and TEID of and the transport layer address and TEID of the third downstream tunnel. It should be understood that the information in which way to express the tunnel may be determined through negotiation between the hosting PDCP entity node and the corresponding node, or may be defined by the 3GPP standard, or may be configured by the network management system, which is not specifically limited in this document. In another possible implementation manner, the data packet repetition assistance information may include the wireless quality assistance information of some or all of the logical channels in LC1 to LC3 of the corresponding node. The radio quality auxiliary information of one of the logical channels can be downlink radio quality index (DL radio quality index), uplink radio quality index (UL radio quality index), average CQI, average HARQ failure, average HARQ retransmission, and power headroom report ( At least one of power headroom report, PHR). In another possible implementation manner, the data packet repetition assistance information may include logical channels (such as LC1 and LC2) for which the corresponding node recommends to activate the data packet repetition, and the respective wireless quality assistance information of these logical channels (LC1 and LC2). It should be understood that if the downlink tunnel information is used to represent the data packet repeated auxiliary information, the wireless quality auxiliary information of a logical channel is the wireless quality auxiliary information of the logical channel corresponding to a tunnel.

502. The corresponding node sends the data packet repeated auxiliary information to the node hosting the PDCP entity. Correspondingly, the host PDCP entity node receives the data packet repeated auxiliary information sent by the corresponding node.

In this step, the corresponding node uses the auxiliary information forwarding process to provide the data packet repeated auxiliary information to the node hosting the PDCP entity. The auxiliary information forwarding process is used by the corresponding node to provide auxiliary information to the managed PDCP entity node for the managed PDCP entity node to use for user plane management and optimization. Exemplarily, the corresponding node sends the data packet repeat auxiliary information to the node hosting the PDCP entity through the NR user plane protocol frame. The NR user plane protocol frame format specified in the current 3GPP standard can be found in the 3GPP TS38.425 v15.4.0 technical specification. Table 1 shows the NR user plane protocol frame format of the auxiliary information data in this technical specification. In this technical specification, the corresponding node has a logical channel, which can provide auxiliary information such as whether to activate the logical channel of the corresponding node or the wireless quality auxiliary information of the logical channel to the host PDCP entity node.

Table 1 NR user plane protocol frame format of auxiliary information data in 3GPP3GPP TS38.425 v15.4.0

The value of the "PDU Type" field is 2, indicating that the NR user plane protocol data is used to represent auxiliary information data. The "PDCP Duplication Indication" field is used to identify whether the "PDCP Duplication Activation Suggestion (PDCP Duplication Activation Suggestion)" field exists. For example, the value of the "PDCP Repeat Indication" field is 0, which means that there is no "PDCP Repeated Activation Suggestion" field; the value of the "PDCP Repeat Indication" field is 1, which means that there is a "PDCP Repeated Activation Suggestion" field. The "Assistance Information Indication (Assistance Information Indication)" field is used to identify whether the "Number of Assistance Information Field (Number of Assistance Information Field)" field exists. For example, the value of the "Auxiliary Information Indication" field is 0, which means that there is no "Auxiliary Information Field Number" field; the "Auxiliary Information Indication" field has a value of 1, which means that the "Auxiliary Information Field Number" field is present. The "spare" field usually has a value of 0, which is reserved for use by subsequent versions. The "PDCP reactivation suggestion" field is used to identify whether the corresponding node activates PDCP repetition. For example, the value of the "PDCP reactivation suggestion" field is 0, which means that PDCP repetition is not activated; the value of the "PDCP reactivation suggestion" field is 1, which means that the PDCP repetition is activated. The "Number of Auxiliary Information Fields" field is used to indicate the number of the "Assistance Information Type" field and the concatenated "Radio Quality Assistance Information (Radio Quality Assistance Information)" field; the "Assistance Information Type" field is used to describe The type of wireless quality assistance information provided by the corresponding node to the NR PDCP entity node. Among them, the downlink radio quality index (DL Radio Quality Index) is a numeric index used to indicate the downlink DRB radio quality, where the value 0 represents the lowest quality; the uplink radio quality index (UL Radio Quality Index) is a numeric index used to indicate the uplink DRB radio quality The numerical index of quality, where the value 0 represents the lowest quality; the average window of average CQI, average HARQ failure, and average HARQ retransmission is set by configuration; power headroom report is the report PHR MAC CE defined by the 3GPP standard specification . The "Number of Radio Quality Auxiliary Information Fields" field is used to indicate the number of bytes required for the radio quality auxiliary information field. For average CQI, average HARQ failure, average HARQ retransmission, downlink radio quality index, and uplink radio quality index, this field should be indicated as "1"; for power headroom report, this field should indicate the power headroom report used Number of bytes. The "wireless quality auxiliary information" field is used to indicate one item of auxiliary information indicated by the auxiliary information type. It should be understood that the auxiliary information data in Table 1 refers to the data packet duplication of the auxiliary information in the embodiment of the present application, and the PDCP duplication in Table 1 refers to the data packet duplication in the embodiment of the present application.

In the embodiment of the present application, the corresponding node has multiple logical channels. Therefore, in the auxiliary information data, the corresponding node can not only indicate whether to activate PDCP repetition, but also indicate which logical channel or logical channels to activate. As in the above example, the corresponding node may indicate whether to activate data packet repetition in any combination of LC1, LC2, and LC3. For this reason, the 1-bit length of the "PDCP repeated activation suggestion" field in Table 1 is no longer adapted. In the embodiment of the present application, the length of the "PDCP repeated activation suggestion" field can be set according to the number of logical channels of the corresponding node. Similarly, in the "wireless quality assistance information" field, the corresponding node may also indicate the wireless quality assistance information of different logical channels. To this end, the wireless quality auxiliary information for one type of auxiliary information in Table 1 may be the wireless quality auxiliary information of one or more logical channels under the auxiliary information type. As in the above example, the corresponding node may indicate the wireless quality auxiliary information of each of LC1, LC2, and LC3 whose auxiliary information type is "downlink wireless quality index".

Exemplarily, Table 2 shows the NR user plane protocol frame format of the auxiliary information data in the embodiment of the present application. As in the above example, when the data packet repetition auxiliary information is at least one logical channel suggested by the corresponding node to activate the data packet repetition, in a possible implementation manner, the length of the "PDCP repeated activation suggestion" field can be set to 2. Bit (as shown in Table 2), for example, when the value of this field is 00, it indicates that it is recommended to activate LC1 for PDCP repetition; when the value of this field is 01, it indicates that it is recommended to activate LC2 for PDCP repetition; when the value of this field is 10 At the time, the instruction suggests that LC3 is activated for PDCP repetition. Or, when the value of this field is 00, it indicates that it is recommended to activate the first tunnel for PDCP repetition; when the value of this field is 01, it indicates that it is recommended to activate the second tunnel for PDCP repetition; when the value of this field is 10, it indicates that it is recommended The third tunnel is activated for PDCP repetition. In another possible implementation, the length of the "PDCP reactivation suggestion" field can be set to 3 bits. For example, when the value of this field is 001, it indicates that it is recommended to activate LC1 for PDCP repetition; when the value of this field is 010 When the value of this field is 100, it indicates that it is recommended to activate LC2 for PDCP repetition; when the value of this field is 011, it indicates that it is recommended to activate LC1 and LC2 for PDCP repetition; when the value of this field is When it is 110, it indicates that it is recommended to activate LC2 and LC3 for PDCP repetition; when the value of this field is 101, it indicates that it is recommended to activate LC1 and LC3 for PDCP repetition; when the value of this field is 111, it indicates that it is recommended to activate LC1 to LC3 for PDCP repetition. repeat. Or, when the value of this field is 001, it indicates that it is recommended to activate the first tunnel for PDCP repetition; when the value of this field is 010, it indicates that it is recommended to activate the second tunnel for PDCP repetition; when the value of this field is 100, it indicates that it is recommended Activate the third tunnel for PDCP repetition; when the value of this field is 011, it indicates that it is recommended to activate the first tunnel and the second tunnel for PDCP repetition; when the value of this field is 110, it indicates that it is recommended to activate the second and third tunnel Perform PDCP repetition; when the value of this field is 101, it indicates that it is recommended to activate the first tunnel and the third tunnel for PDCP repetition; when the value of this field is 111, it indicates that it is recommended to activate the first tunnel to the third tunnel for PDCP repetition. When the data packet repetition auxiliary information is the wireless quality auxiliary information of at least one logical channel of the corresponding node, as an example, for any type of auxiliary information, the "wireless quality auxiliary information" field may contain the wireless quality auxiliary information of LC1 or LC2 The wireless quality auxiliary information of LC3, or the wireless quality auxiliary information of LC1 and LC2, or the wireless quality auxiliary information of LC1 and LC3, or the wireless quality auxiliary information of LC2 and LC3, or the wireless quality auxiliary information of LC1 to LC3. Quality auxiliary information. When the data packet repetition auxiliary information is at least one logical channel suggested by the corresponding node to activate the data packet repetition and the wireless quality auxiliary information corresponding to the at least one logical channel, as an example, the "PDCP repeated activation suggestion" field has a value of 010, indicating Activate LC2 for PDCP repetition, and the "Wireless Quality Assistance Information" field contains LC2's wireless quality assistance information; or, it means that the second tunnel is activated for PDCP repetition, and the "Wireless Quality Assistance Information" field contains the logical channel corresponding to the second tunnel Wireless quality auxiliary information. As another example, the "PDCP repeated activation suggestion" field has a value of 110, indicating that LC2 and LC3 are activated for PDCP repetition, and the "wireless quality assistance information" field contains the wireless quality assistance information of LC2 and LC3; or, it indicates that the second tunnel is activated. Perform PDCP repetition with the third tunnel, and the "radio quality assistance information" field contains the radio quality assistance information of the logical channels corresponding to the second tunnel and the third tunnel respectively. It is worth noting that the wireless quality auxiliary information of a logical channel may be the wireless quality auxiliary information obtained after mathematical operations (such as taking arithmetic average or weighted average) of the wireless quality auxiliary information of each carrier corresponding to the logical channel group The wireless quality auxiliary information of a logical channel may also be the wireless quality auxiliary information of each carrier corresponding to the logical channel without processing.

Optionally, the correspondence between the various values of the "PDCP repeated activation suggestion" field and the logical channel or tunnel is carried on the secondary node addition requirement (SN addition required) message or secondary node modification requirement (SN modification required) message .

Table 2 NR user plane protocol frame format of auxiliary information data in the embodiment of the application

Optionally, the corresponding node sends the data packet repeated auxiliary information to the node hosting the PDCP entity through the auxiliary information data of the Xn-U interface.

Optionally, before step 501, the corresponding node also obtains its logical channel group. Logical channel grouping is to divide the logical channels of corresponding nodes into multiple groups, and a logical channel group (LCG) contains one or more logical channels. It is worth noting that one logical channel corresponds to one RLC entity, so one logical channel group corresponds to one or more RLC entities, that is, a group of RLC entities. In a possible implementation manner, the managed PDCP entity node groups the logical channels of the corresponding nodes, and informs the corresponding nodes of the grouping; the corresponding nodes can save the logical channel grouping information and use it later. In another possible implementation manner, the corresponding node groups its own logical channels and notifies the escrow PDCP entity node of the grouping; the escrow PDCP entity node obtains the logical channel grouping information and can save and use it later. There are many ways to group logical channels. In a possible implementation, one LCG is any combination of the respective LCs of the corresponding node. Exemplarily, the corresponding nodes have LC1, LC2, and LC3, and the logical channels can be divided into four groups. Specifically, LCG1 includes LC1 and LC2, LCG2 includes LC2 and LC3, LCG3 includes LC1 and LC3, and LCG4 includes LC1 to LC3. In another possible implementation manner, an LCG may be any combination of a specific LC of the corresponding node and other LCs. In other words, in this manner, any LCG will always include the specific LC of the corresponding node, and the specific LC may also be referred to as a primary (primary) LC. In the above example, when LC1 is the main LC, its logical channels can be divided into three groups. Specifically, LCG1 includes LC1 and LC2, LCG2 includes LC1 and LC3, and LCG3 includes LC1 to LC3. It is worth noting that the main LC may be determined by the host PDCP entity node or the corresponding node, and the main LC may include multiple LCs. For example, if the managed PDCP entity node sets LC1 and LC2 as the main LC, its logical channels can be divided into two groups. Specifically, LCG1 includes LC1 and LC2, and LCG2 includes LC1 to LC3. Tables 3 and 4 show the logical channel grouping information sent to the corresponding node after the host PDCP entity node determines the logical channel grouping of the corresponding node, or the logical channel sent to the host PDCP entity node after the corresponding node determines the logical channel grouping of the corresponding node Illustration of grouping information. Optionally, the logical channel grouping information is carried on a secondary node addition requirement (SN addition required) message or a secondary node modification requirement (SN modification required) message.

Table 3 Logical channel grouping information

>DRB ID>DRB ID
>LCID grouping list>LCID grouping list
>>LCG1 ID>>LCG1 ID
>>>LC1 ID,LC2 ID>>>LC1 ID,LC2 ID
>>LCG2 ID>>LCG2 ID
>>>LC2 ID,LC3 ID>>>LC2 ID,LC3 ID
>>LCG3 ID>>LCG3 ID
>>>LC1 ID,LC3 ID>>>LC1 ID,LC3 ID
……

Table 4 Logical channel grouping information with main logical channel

>DRB ID>DRB ID
>LCID grouping list>LCID grouping list
>>LCG1 ID>>LCG1 ID
>>>LC1 ID,LC2 ID>>>LC1 ID,LC2 ID
>>LCG2 ID>>LCG2 ID
>>>LC1 ID,LC3 ID>>>LC1 ID,LC3 ID
>>LCG3 ID>>LCG3 ID
>>>LC1 ID,LC2 ID,LC3 ID>>>LC1 ID,LC2 ID,LC3 ID
……

Among them, DRB ID represents the identification of the DRB served by the corresponding node. LCID grouping list represents a list of logical channel group identifiers, which includes multiple logical channel group identifiers (LCG IDs). In the case that the corresponding node will have three logical channels, Table 3 gives an illustration of dividing the logical channels of the corresponding node into three logical channel groups. Among them, LCG1 ID identifies LCG1 composed of LC1 and LC2, LCG2 ID identifies LCG2 composed of LC2 and LC3, and LCG3 ID identifies LCG3 composed of LC1 and LC3. In the case that the corresponding node has a main logical channel (such as LC1), Table 4 shows a schematic diagram of dividing the logical channel of the corresponding node into three logical channel groups. LCG1 ID identifies LCG1 composed of LC1 and LC2, LCG2 ID identifies LCG2 composed of LC1 and LC3, and LCG3 ID identifies LCG3 composed of LC1 and LC2.

It should be pointed out that in the case that the corresponding node has logical channel grouping, in step 501, the data packet repetition auxiliary information generated by the corresponding node is granular with the logical channel group. Exemplarily, the data packet repetition auxiliary information may be at least one logical channel group suggested by the corresponding node to activate the data packet repetition, or it may be the respective wireless quality auxiliary information of part or all of the logical channel groups of the corresponding node, or the corresponding node At least one logical channel group that the proposed activation data packet repeats and the wireless quality auxiliary information corresponding to the at least one logical channel group. The wireless quality auxiliary information of a logical channel group may be the wireless quality auxiliary information obtained after the wireless quality auxiliary information of each logical channel in the logical channel group undergoes mathematical operations (such as taking arithmetic average or weighted average); a logical channel group The wireless quality auxiliary information of may also be unprocessed wireless quality auxiliary information of each logical channel in the logical channel group. Correspondingly, in step 502, the data packet repeated auxiliary information sent by the corresponding node is also granular with the logical channel group.

It is worth noting that since one logical channel corresponds to one tunnel, before step 501, the corresponding node can also obtain its tunnel group. Similar to the correspondence between logical channel groups and logical channels, a tunnel group can contain one or more tunnels. The tunnel grouping information can be carried on the secondary node addition required (SN addition required) message or the secondary node modification required (SN modification required) message. In a possible implementation, a tunnel group is any combination of tunnels. In another possible implementation, a tunnel group can be any combination of a specific tunnel and other tunnels. In the case of tunnel grouping, the above Table 3 and Table 4 correspond to tunnel grouping information, where the LCID grouping list corresponds to Tunnel ID grouping list, which represents a tunnel group identification list; and corresponds to any tunnel group identification in the list, Contains the downlink tunnel information of each tunnel included in the tunnel group, such as the tunnel identifier of each tunnel, or the tunnel index of each tunnel, or the transport layer address and TEID of each downlink tunnel.

Since a logical channel group contains one or more logical channels, the data packet repeating auxiliary information with the granularity of the logical channel group or tunnel group can effectively reduce the data amount of auxiliary information and reduce the information overhead.

503. The decision data packet of the managed PDCP entity node is repeated.

The managed PDCP entity node receives the data packet repetition auxiliary information sent by the corresponding node, and can determine the data packet duplication according to the situation of the managed PDCP entity node (such as the wireless quality of each logical channel of the managed PDCP entity node, the load of the managed PDCP entity node, etc.) . Specifically, the managed PDCP entity node decides to activate at least two logical channels for data packet repetition. The at least two logical channels may be composed of logical channels hosting the PDCP entity node, or composed of logical channels of the corresponding node, or composed of the logical channels hosting the PDCP entity node and the corresponding node. Exemplarily, the managed PDCP entity node activates its own at least one logical channel and at least one logical channel of the corresponding node to perform data packet repetition according to the data packet repetition suggestions of the corresponding node and its own situation; The wireless quality auxiliary information of a logical channel decides to activate multiple logical channels of the corresponding node for data packet repetition; or the managed PDCP entity node decides to activate only its own multiple logical channels for data packet repetition according to the data packet repetition auxiliary information of the corresponding node. Similarly, if the data packet repetition auxiliary information contains tunnel information, the managed PDCP entity node decides whether to activate the tunnel with the corresponding node, or activate several tunnels with the corresponding node for data packet repetition.

Through the above steps of the embodiment of the present application, the corresponding node can send the data packet repetition auxiliary information to the escrow PDCP entity node at the granularity of the logical channel, so that the auxiliary escrow PDCP entity node can effectively make the data packet repetition decision. For example, the managed PDCP entity node may decide to activate multiple logical channels of the corresponding node to perform data packet repetition according to the data packet repetition auxiliary information.

Optionally, this embodiment of the present application further includes step 504.

504. The managed PDCP entity node sends a downlink data packet to the corresponding node through at least one tunnel.

In this step, when the hosting PDCP entity node decides to activate at least one logical channel of the corresponding node for data packet repetition, the hosting PDCP entity node sends a downlink data packet to the corresponding node through at least one tunnel corresponding to the at least one logical channel , So that the corresponding node can schedule the corresponding downlink data packet on the at least one logical channel to at least one wireless link and send it to the terminal device. Exemplarily, when a managed PDCP entity node configures a DRB, the DRB is configured to host the PDCP entity node's LH1 and LH2 and the corresponding node's LH3 and LH4, and the managed PDCP entity node and the corresponding node are configured to correspond to Two tunnels of LH3 and LH4, such as the first tunnel and the second tunnel, where the first tunnel corresponds to LH3 and the second tunnel corresponds to LH4. Correspondingly, if in step 503 the hosting PDCP entity node decides to activate its own LH1 and the corresponding node's LH3 for data packet repetition, then in this step, the hosting PDCP entity node sends the downlink data packet to the corresponding node through the first tunnel. In addition, the managed PDCP entity node also sends the downlink data packet to its own RLC1. If in step 503 the host PDCP entity node decides to activate LH3 and LH4 of the corresponding node for data packet repetition, then in this step, the host PDCP entity node will pass the downlink data packets with the same PDCP sequence number through the first tunnel and the second tunnel respectively Sent to the corresponding node. Similarly, if in step 503, the hosting PDCP entity node decides to activate at least one tunnel with the corresponding node for data packet repetition, then in this step, the hosting PDCP entity node sends the downlink data packet to the corresponding node through the at least one tunnel. node.

Through this step, the managed PDCP entity node sends the downlink data packet to the corresponding node through the corresponding tunnel according to the decision of the data packet repetition, and the corresponding RLC entity in the corresponding node correctly receives the downlink data packet, so that the corresponding node can correctly perform the data packet repetition .

Further, the wireless communication system shown in FIG. 1 may also include a terminal device for wireless connection with three or more RAN devices, which may also be referred to as multiple connections. It should be understood that when a terminal device is wirelessly connected to three or more RAN devices, one of the RAN devices is an MN, and the other multiple RAN devices are SNs. MN realizes the transmission of control plane data and user plane data with 5GC equipment through NG-C and NG-U interfaces, SN realizes the transmission of user plane data with 5GC equipment through NG-U interface, and MN and SN can be separated The transmission of control plane data and user plane data is realized through Xn-C and Xn-U interfaces. In this case, one RAN device is a managed PDCP entity node, and multiple other RAN devices are corresponding nodes. For a DRB, multiple RLC entities are configured in some or all corresponding nodes. When multiple corresponding nodes exist, the method flow shown in FIG. 5 is applicable to the interaction between each corresponding node configured with multiple RLC entities and the node hosting the PDCP entity. The managed PDCP entity node obtains the data packet repetition auxiliary information of multiple corresponding nodes, which can further optimize the data packet repetition decision-making, if there is more freedom to activate the appropriate logical link for data packet repetition, etc.

In the architecture where the RAN device is divided into CU and DU according to the protocol stack, for a DRB, the CU contains the PDCP entity corresponding to the DRB. In order to achieve data packet repetition, the DU needs to send the data packet repetition auxiliary information to the CU, and the CU decides the data packet repetition. FIG. 6 shows a schematic diagram of a user plane L2 protocol stack used for data packet repetition in a RAN device architecture divided into CU and DU according to an embodiment of the present application. Among them, Figure 6(a) shows the case where the RAN equipment consists of one CU and one DU, where L is an integer greater than 2; Figure 6(b) shows the case where the RAN equipment consists of one CU and two DUs , Where P is an integer greater than or equal to 2, and Q is an integer greater than or equal to 2. It should be understood that for one DRB, multiple RLC entities are configured in the DU. Correspondingly, multiple tunnels are established between a CU and a DU, and the number of tunnels is the same as the number of RLC entities of a DU. In a possible implementation, the CU configures multiple RLC entities of the DU through the control plane signaling of the F1-C interface; the CU sends the information of multiple uplink tunnels to the DU, and the DU sends the information of the corresponding multiple downlink tunnels to CU; where the number of RLC entities or tunnels of the DU is determined by the CU. In another possible implementation manner, the CU informs the DU of the maximum number of RLC entities or tunnels that it allows to establish through the control plane signaling of the F1-C interface, and the DU determines the number of RLC entities or tunnels by itself, and The corresponding downlink tunnel information is sent to the CU. This article does not specifically limit the number of RLC entities of the DU. Optionally, the configuration of the RLC entity or tunnel of the CU to the DU is carried on a terminal device context setup request (UE context setup request) message or a terminal device context modification request (UE context modification request) message.

FIG. 7 shows a schematic flowchart of an improved auxiliary information and a method for transferring it under a RAN device architecture divided into CU and DU according to an embodiment of the present application. The method 700 can be applied to the scenario of FIG. 6(a) or FIG. 6(b). It should be understood that the CU in FIG. 7 is similar to the managed PDCP entity node in FIG. 5, and the DU in FIG. 7 is similar to the corresponding node in FIG. 5. The process described in Figure 7 includes the following steps:

701. The DU determines that the data packet repeats auxiliary information.

In this step, the DU determines that the data packet repeats the auxiliary information, and the DU may be any DU in FIG. 6(a) or FIG. 6(b).

The data packet repetition auxiliary information determined by the DU is similar to the data packet repetition auxiliary information determined by the corresponding node in step 501 of the foregoing embodiment, and will not be repeated here.

702. The DU sends the data packet repeat auxiliary information to the CU. Correspondingly, the CU receives the repeated auxiliary information of the data packet sent by the DU.

This step is similar to step 502 in the foregoing embodiment, and will not be repeated here.

Optionally, the DU sends the data packet repeated auxiliary information to the CU through the auxiliary information data of the F1-U interface.

Optionally, before step 701, the DU also obtains its logical channel group or tunnel group. In a possible implementation manner, the CU groups the logical channels of the DU or the tunnel between the CU and the DU, and notifies the DU of the grouping; the DU can save the grouping information and use it later. In another possible implementation manner, the DU groups its own logical channels or the tunnels between it and the CU, and notifies the CU of the grouping; the CU can save the grouping information and use it later.

Optionally, the logical channel grouping information or tunnel grouping information may be carried on a terminal device context setup request (UE context setup request) message or a terminal device context modification request (UE context modification request) message.

It should be understood that, similar to the foregoing embodiment, in the case of logical channel grouping or tunnel grouping in the DU, in step 701, the data packet repetition auxiliary information generated by the DU is granular with the logical channel group or tunnel group; in step 702 In the data packet repetition auxiliary information sent by the DU, the granularity is also based on the logical channel group or tunnel group.

703. The CU decision data packet is repeated.

In this step, the CU decides that the data packet is repeated according to the received data packet repetition sent by the DU. In a scenario where the CU is connected to a DU, exemplarily, the CU activates at least two logical channels suggested by the DU to perform data packet repetition according to the DU's packet repetition suggestion decision; or the CU makes a decision based on the radio quality assistance information of multiple logical channels of the DU Activate at least two logical channels of the DU to repeat data packets and so on. In a scenario where a CU is connected to two DUs, exemplarily, the CU activates some or all of the logical channels in the two DUs to perform data packet repetition according to any one DU or two DU data packet repetition suggestions; The radio quality assistance information of multiple logical channels of one DU or two DUs decides to activate some or all of the logical channels in the two DUs for data packet repetition.

Through the above-mentioned steps in the embodiments of the present application, the DU can send the data packet repetition auxiliary information to the CU at the granularity of a logical channel, so that the CU can effectively make the decision of data packet repetition. For example, the CU may decide to activate multiple logical channels of at least one DU for data packet repetition according to the data packet repetition auxiliary information.

Optionally, this embodiment of the present application further includes step 704.

704. The CU sends a downlink data packet to the DU through at least one tunnel.

In this step, when the CU decides to activate at least one logical channel of a DU for data packet repetition, the CU sends a downlink data packet to the DU through at least one tunnel corresponding to the at least one logical channel, so that the DU The corresponding downlink data packet on the at least one logical channel can be scheduled to at least one wireless link and sent to the terminal device. Exemplarily, in the scenario where the CU is connected to a DU, when the CU configures the DRB, it configures the DRB in the DU's LH1, LH2, and LH3, and configures the three tunnels between the CU and the DU corresponding to LH1 to LH3 , Such as the first tunnel, the second tunnel and the third tunnel, where the first tunnel corresponds to LH1, the second tunnel corresponds to LH2, and the third tunnel corresponds to LH3. Correspondingly, if in step 703 the CU decides to activate LH1 and LH3 of the DU for data packet repetition, then in this step, the CU sends downlink data packets with the same PDCP sequence number to the DU through the first tunnel and the third tunnel. In the scenario where the CU is connected to two DUs, when the CU is configured with DRB, the DRB is configured in LH1 and LH2 of DU1 and LH3 and LH4 of DU2, and the CU and the two DUs are configured to correspond to LH1 to LH4 The four tunnels, such as the first tunnel, the second tunnel, the third tunnel, and the fourth tunnel, where the first tunnel corresponds to LH1, the second tunnel corresponds to LH2, and so on. Correspondingly, if in step 703, the CU decides to activate LH1 of DU1 and LH3 and LH4 of DU2 for data packet repetition, then in this step, the CU sends the downlink data packets with the same PDCP sequence number to DU1 and DU1 through the first tunnel respectively. Send to DU2 through the third tunnel and the fourth tunnel.

Through this step, it is realized that the CU sends the downlink data packet to at least one DU through the corresponding tunnel according to the decision of the data packet repetition, and the corresponding RLC entity in the at least one DU correctly receives the downlink data packet, so that the at least one DU can correctly perform data The package is repeated.

Further, one RAN device may also consist of one CU and three or more DUs. In this case, the method flow shown in FIG. 7 is also applicable to the interaction between each DU and CU. The CU obtains the data packet repetition auxiliary information of three or more DUs, which can further optimize the decision of the data packet repetition, if there is more freedom to activate the appropriate logical link for data packet repetition, etc.

In the architecture where the RAN device is divided into CU and DU according to the protocol stack, the CU is further divided into one CU-CP and one or more CU-UPs. For a DRB, the CU-CP includes the control plane entity in the CU that processes the DRB, and the CU-UP includes the user plane entity in the CU that processes the DRB. Therefore, for the user plane, the L2 protocol stack of this scenario is similar to that of Fig. 6, except that the CU in Fig. 6 becomes CU-UP. Since CU-UP only has user plane functions, DU and CU-UP also need to be connected to CU-CP and CU-CP provides control plane functions. In order to realize the data packet repetition, the DU needs to send auxiliary information to the CU-UP, which is sent to the CU-CP, and then the CU-CP decides the data packet repetition. It should be understood that for one DRB, multiple RLC entities are configured in the DU. Correspondingly, multiple tunnels are established between a CU-UP and a DU, and the number of tunnels is the same as the number of RLC entities of the DU. In a possible implementation, the CU-CP configures multiple RLC entities of the DU through the control plane signaling of the F1-C interface, and notifies the CU-UP to which the DU is connected through the control plane signaling of the E1 interface of the configuration result; The CU-CP sends the information of the multiple uplink tunnels of the CU-UP to the DU, and sends the information of the multiple downlink tunnels of the DU to the CU-UP. Among them, the number of RLC entities or tunnels of the DU is determined by the CU-CP. In another possible implementation manner, the CU-CP informs the DU of the maximum number of RLC entities or tunnels that it allows to establish through the control plane signaling of the F1-C interface, and the DU determines the number of RLC entities or tunnels by itself. And send the corresponding downlink tunnel information to CU-UP. This article does not specifically limit the number of RLC entities of the DU. Optionally, the configuration of the CU-CP in the RLC entity of the DU is carried on a terminal device context setup request (UE context setup request) message or a terminal device context modification request (UE context modification request) message.

FIG. 8 shows a schematic flow diagram of the improved auxiliary information and its transfer method under a RAN device architecture divided into CU-CP, CU-UP and DU provided by an embodiment of the present application. The method 800 can be applied to the RAN device architecture corresponding to FIG. 2(b), where one DU is connected to one CU-UP, the CU-UP is connected to the CU-CP, and the DU is also connected to the CU-CP. The process described in Figure 8 includes the following steps:

801. The DU determines that the data packet repeats auxiliary information.

The data packet repetition auxiliary information determined by the DU is similar to the data packet repetition auxiliary information determined by the DU in step 701 of the foregoing embodiment, and details are not described herein again.

802. The DU sends the packet repeat auxiliary information to the CU-UP. Correspondingly, the CU-UP receives the repeated auxiliary information of the data packet sent by the DU.

This step is similar to step 702 in the foregoing embodiment, and will not be repeated here.

Optionally, the DU sends the data packet repeated auxiliary information to the CU-UP through the auxiliary information data of the F1-U interface.

Optionally, before step 801, the DU also obtains its logical channel group or tunnel group. In a possible implementation, CU-CP groups the logical channels of the DU or the tunnel between CU-UP and DU, and informs CU-UP and DU of the grouping; CU-UP and DU obtain the grouping The information can be saved and used later. In another possible implementation manner, the DU groups its own logical channel or the tunnel between it and CU-UP, and informs CU-UP and CU-CP of the grouping; CU-UP and CU-CP After obtaining the logical channel grouping information, it can be saved and used later.

Optionally, the CU-CP carries the logical channel grouping information or the tunnel grouping information on a bearer context setup request message or a bearer context modification request message and sends it to the CU-UP; CU- The CP carries the logical channel grouping information or tunnel grouping information on the terminal device context setup request (UE context setup request) message or the terminal device context modification request (UE context modification request) message and sends it to the DU.

803. The CU-UP sends the data packet repeat auxiliary information to the CU-CP. Correspondingly, the CU-CP receives the data packet repeated auxiliary information sent by the CU-UP.

In this step, the CU-UP sends the repeated auxiliary information of the data packet received from the DU to the CU-CP. Exemplarily, the CU-UP sends auxiliary information data to the CU-CP through the E1 interface. Optionally, the auxiliary information data is carried in a bearer context modification request (bearer context modification requried) message.

It should be understood that in the case of logical channel grouping or tunnel grouping in the DU, in step 801, the data packet repetition auxiliary information generated by the DU is granular with the logical channel group or tunnel group; in step 802, the data sent by the DU The packet repetition auxiliary information is also granular with the logical channel group or tunnel group; in step 803, the packet repetition auxiliary information sent by the CU-UP is also granular with the logical channel group or tunnel group.

804. The CU-CP decision data packet is repeated.

In this step, the CU-CP decides that the data packet is repeated according to the received data packet sent by the CU-UP and the auxiliary information is repeated. This step is similar to step 703 in the foregoing embodiment, and will not be repeated here.

Through the above steps of the embodiments of the present application, the DU can send the data packet repetition auxiliary information to the CU-CP through the CU-UP at the granularity of a logical channel, so that the CU-CP can effectively make the decision of data packet repetition. For example, the CU-CP may decide to activate multiple logical channels of at least one DU for data packet repetition according to the data packet repetition auxiliary information.

Optionally, this embodiment of the present application further includes steps 805 and 806.

805. The CU-CP sends the data packet repeated transmission information to the CU-UP. Correspondingly, the CU-UP receives the repeated transmission information of the data packet sent by the CU-CP.

In this step, when the CU decides to activate at least one logical channel of a DU for data packet repetition, the CU-CP sends data packet repeated transmission information to the CU-UP, and the data packet repeated transmission information is used to indicate the activation of DU data The transmission information of at least one logical channel in which the packet is repeated. The transmission information of a logical channel may be at least one of the following parameters: the logical channel identifier of the logical channel, the logical channel index of the logical channel, the tunnel identifier of the tunnel corresponding to the logical channel, the tunnel index of the tunnel, and the The downstream tunnel transport layer address and TEID of the tunnel. Exemplarily, after CU-CP decides which logical channels to activate for data packet repetition, CU-CP sends the downlink tunnel information corresponding to these logical channels to CU-UP, so that CU-UP knows which tunnels will be downlinked The data packet is sent to the corresponding DU. For example, when CU-CP configures DRB, it configures the DRB in LH1, LH2, and LH3 of DU1 and LH4, LH5, and LH6 of DU2, and configures the corresponding LH1 to DU2 between CU-UP and DU1 and DU2. The six tunnels of LH6, such as the first tunnel to the sixth tunnel, where the first tunnel corresponds to LH1, the second tunnel corresponds to LH2, and so on. If the CU-CP receives the packet repetition auxiliary information suggested by DU1 in LH1 and LH3 and the packet repetition suggested by DU2 in LH5 in step 803, and decides to activate LH2, LH3, and LH5 in step 804 To repeat the data packet, in this step, the CU-CP sends the respective downlink tunnel information of the second tunnel, the third tunnel and the fifth tunnel between the CU-UP and the DU corresponding to LH2, LH3, and LH5 to the CU -UP.

It should be understood that if the data packet repetition auxiliary information is based on the logical channel group or tunnel group as the granularity, then in this step, when the CU decides to activate at least one logical channel group of a DU for data packet repetition, the CU-CP sends The data packet repeated transmission information sent by the CU-UP includes transmission information of the at least one logical channel group or at least one tunnel group. The transmission information of a logical channel group or tunnel group may be the transmission information of each logical channel in the logical channel group or each logical channel corresponding to the tunnel group.

806. The CU-UP sends a downlink data packet to the DU through at least one tunnel.

In this step, the CU-UP sends a downlink data packet to the DU according to the repeated transmission information of the data packet received in step 805. Specifically, the data packet repeated transmission information includes downlink tunnel information of at least one tunnel. In this step, the CU-UP sends the downlink data packet to the at least one DU through the at least one tunnel. In the above example of step 805, in this step, CU-UP sends downlink data packets with the same PDCP sequence number to DU1 and DU2 through the second tunnel and the third tunnel respectively.

Through steps 805 and 806, it is realized that the CU instructs the CU-UP to send the downlink data packet to at least one DU through the corresponding tunnel according to the decision of data packet repetition, and the corresponding RLC entity in the at least one DU correctly receives the downlink data packet, so that the at least One DU can correctly repeat data packets.

Further, the method flow shown in FIG. 8 is also applicable to the CU-UP connected to each DU and the interaction between the CU-UP and the CU when the CU-CP is connected to three or more DUs. It is worth noting that in the RAN device architecture shown in Figure 2(b), one DU can also be connected to multiple CU-UPs, and one CU-UP can also be connected to multiple DUs. For a DRB, in the DRB configuration process, the CU-CP is configured with multiple DUs and multiple CU-UPs for processing the DRB. Therefore, before step 801, the multiple CU-UPs connected to a DU and the connection between the multiple CU-UPs and the CU-CP are determined, and each RLC entity in the DU is connected to the DU The tunnel between multiple CU-UPs is also determined. In the method flow shown in FIG. 8, after the DU determines the data packet repetition auxiliary information, the data packet repetition auxiliary information of the corresponding logical channel is sent to the CU-UP connected to the logical channel and sent by the CU-UP To CU-CP. Exemplarily, if a DU is connected to the first CU-UP and the second CU-UP, and RLC1 and RLC2 in the DU are connected to the first CU-UP, RLC3 and RLC4 in the DU are connected to the second CU-UP Is connected, when the DU determines to send the wireless quality auxiliary information of LC1, LC2, and LC4, the DU sends the wireless quality auxiliary information of LC1 and LC2 to the first CU-UP, and the wireless quality auxiliary information of LC4 to the second CU -UP.

In the above embodiments, it may be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented by software, it can be implemented in the form of a computer program product in whole or in part. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on the computer, the processes or functions described in the embodiments of the present application are generated in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions may be transmitted from a website, computer, server, or data center. Transmission to another website site, computer, server or data center via wired (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (such as infrared, wireless, microwave, etc.). The computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server or a data center integrated with one or more available media. The usable medium may be a magnetic medium (for example, a floppy disk, a hard disk, and a magnetic tape), an optical medium (for example, a DVD), or a semiconductor medium (for example, a solid state disk (SSD)). Professionals and technicians can use different methods for each specific application to realize the described functions, but such realization should not be considered beyond the scope of this patent application.

The method embodiment of the present application is described in detail above with reference to Figs. 5, 7 and 8, and the device embodiment of the present application is described in detail below in conjunction with Figs. 9 to 14. It should be understood that the device embodiment and the method embodiment correspond to each other, and similar descriptions may refer to the method embodiment. It is worth noting that the device embodiment can be used in conjunction with the above-mentioned method or used alone.

FIG. 9 shows a schematic block diagram of a first network device 900 according to an embodiment of the present application. The first network device 900 may correspond to (for example, may be configured in or be itself) the corresponding node described in the above method 500, or the above The distributed unit described in method 700, or the distributed unit described in method 800 above. The first network device 900 may include a processor 901 and a transceiver 902, and the processor 901 and the transceiver 902 are communicatively coupled. Optionally, the first network device 900 further includes a memory 903, and the memory 903 is communicatively coupled with the processor 901. Optionally, the processor 901, the memory 903, and the transceiver 902 may be communicatively coupled, the memory 903 may be used to store instructions, and the processor 901 may be used to execute instructions stored in the memory 903 to control the transceiver 902 to receive and/or Send information or signals. Wherein, the processor 901 and the transceiver 902 are respectively configured to execute the corresponding node described in the above method 500, or the distributed unit described in the above method 700, or the distributed unit described in the above method 800, each action or Processing process. Here, in order to avoid redundant description, detailed descriptions are omitted.

FIG. 10 shows another schematic block diagram of the first network device 1000 according to an embodiment of the present application. The first network device 1000 may correspond to (for example, may be configured in or be itself) the corresponding node described in the above method 500, Or the distributed unit described in the above method 700, or the distributed unit described in the above method 800. The first network device 1000 may include: a receiving module 1001, a processing module 1002, and a sending module 1003, and the processing module 1002 is communicatively coupled with the receiving module 1001 and the sending module 1003, respectively. The first network device 1000 may take the form shown in FIG. 9. The processing module 1002 may be implemented by the processor 901 in FIG. 9, and the receiving module 1001 and/or the sending module 1003 may be implemented by the transceiver 902 in FIG. 9. The first network device 1000 may further include a storage unit for storing programs or data to be executed by the processing module 1002, or storing information received through the receiving module 1001 and/or sent through the sending module 1003. Each module or unit in the first network device 1000 is respectively used to execute the corresponding node described in the above method 500, or the distributed unit described in the above method 700, or the distributed unit described in the above method 800, each of which is executed Action or process. Here, in order to avoid redundant description, detailed descriptions are omitted.

FIG. 11 shows a schematic block diagram of a second network device 1100 according to an embodiment of the present application. The second network device 1100 may correspond to (for example, may be configured in or be itself) the managed PDCP entity node described in the above method 500, Or the centralized unit described in the above method 700, or the centralized unit control plane network element described in the above method 800. The second network device 1100 may include: a processor 1101 and a transceiver 1102, and the processor 1101 and the transceiver 1102 are communicatively coupled. Optionally, the second network device 1100 further includes a memory 1103, and the memory 1103 is communicatively coupled with the processor 1101. Optionally, the processor 1101, the memory 1103, and the transceiver 1102 may be communicatively coupled, the memory 1103 may be used to store instructions, and the processor 1101 may be used to execute instructions stored in the memory 1103 to control the transceiver 1102 to receive and/or Send information or signals. The processor 1101 and the transceiver 1102 are respectively configured to execute the managed PDCP entity node described in the above method 500, or the centralized unit described in the above method 700, or the centralized unit control plane network element described in the above method 800. Each action or process. Here, in order to avoid redundant description, detailed descriptions are omitted.

FIG. 12 shows another schematic block diagram of a second network device 1200 according to an embodiment of the present application. The second network device 1200 may correspond to (for example, may be configured in or be itself) the managed PDCP entity described in the above method 500 The node, or the centralized unit described in the above method 700, or the centralized unit described in the above method 800, controls the plane network element. The second network device 1200 may include: a receiving module 1201, a processing module 1202, and a sending module 1203, and the processing module 1202 is communicatively coupled with the receiving module 1201 and the sending module 1203, respectively. The second network device 1200 may adopt the form shown in FIG. 11. The processing module 1202 may be implemented by the processor 1101 in FIG. 11, and the receiving module 1201 and/or the sending module 1203 may be implemented by the transceiver 1102 in FIG. 11. The second network device 1200 may further include a storage unit for storing programs or data to be executed by the processing module 1202, or storing information received through the receiving module 1201 and/or sent through the sending module 1203. Each module or unit in the second network device 1200 is used to execute the managed PDCP entity node described in the above method 500, or the centralized unit described in the above method 700, or the centralized unit control plane network element described in the above method 800, Each action or process performed. Here, in order to avoid redundant description, detailed descriptions are omitted.

FIG. 13 shows a schematic block diagram of a third network device 1300 according to an embodiment of the present application. The third network device 1300 may correspond to (for example, be configured in or be itself) the centralized unit user plane network described in the above method 800 yuan. The third network device 1300 may include: a processor 1301 and a transceiver 1302, and the processor 1301 and the transceiver 1302 are communicatively coupled. Optionally, the third network device 1300 further includes a memory 1303, and the memory 1303 is communicatively coupled with the processor 1301. Optionally, the processor 1301, the memory 1303, and the transceiver 1302 may be communicatively coupled, the memory 1303 may be used to store instructions, and the processor 1301 may be used to execute instructions stored in the memory 1303 to control the transceiver 1302 to receive and/or Send information or signals. The processor 1301 and the transceiver 1302 are respectively configured to execute the actions or processing procedures performed by the user plane network element of the centralized unit described in the above method 800. Here, in order to avoid redundant description, detailed descriptions are omitted.

FIG. 14 shows another schematic block diagram of a third network device 1400 according to an embodiment of the present application. The third network device 1400 may correspond to (for example, be configured in or be itself) the centralized unit user described in the above method 800 Surface network element. The third network device 1400 may include: a receiving module 1401, a processing module 1402, and a sending module 1403, and the processing module 1402 is communicatively coupled with the receiving module 1401 and the sending module 1403, respectively. The third network device 1400 may adopt the form shown in FIG. 13. The processing module 1402 may be implemented by the processor 1301 in FIG. 13, and the receiving module 1401 and/or the sending module 1403 may be implemented by the transceiver 1302 in FIG. 13. The third network device 1400 may further include a storage unit for storing programs or data to be executed by the processing module 1402, or storing information received through the receiving module 1401 and/or sent through the sending module 1403. The modules or units in the third network device 1400 are respectively configured to execute the actions or processing procedures performed by the centralized unit user plane network element described in the above method 800. Here, in order to avoid redundant description, detailed descriptions are omitted.

It should be understood that the processor (901, 1101, 1301) in the device embodiment of the present application may be a central processing unit (CPU), a network processor (NP), a hardware chip, or any combination thereof. The aforementioned hardware chip may be an application-specific integrated circuit (ASIC), a programmable logic device (PLD) or a combination thereof. The above-mentioned PLD may be a complex programmable logic device (CPLD), a field-programmable gate array (FPGA), a generic array logic (GAL) or any combination thereof.

The memory (903, 1103, 1303) in the device embodiment of the present application may be a volatile memory (volatile memory), such as a random-access memory (RAM); it may also be a non-volatile memory (non-volatile memory). -volatile memory, such as read-only memory (ROM), flash memory (flash memory), hard disk drive (HDD) or solid-state drive (SSD); it can also be the above A combination of types of storage.

In the several embodiments provided in this application, it should be understood that the disclosed device and method may be implemented in other ways. For example, the device embodiments described above are merely illustrative, for example, the division of units is only a logical function division, and there may be other divisions in actual implementation, for example, multiple units or components can be combined or integrated. To another system, or some features can be ignored, or not implemented. In addition, the displayed or discussed mutual coupling or direct coupling or communication coupling may be indirect coupling or communication coupling through some interfaces, devices or units, and may be in electrical, mechanical or other forms.

The units described as separate components may or may not be physically separate, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the objectives of the solutions of the embodiments.

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

If the function is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer readable storage medium. Based on this understanding, the technical solution of the patent application can be embodied in the form of a software product in essence or a part that contributes to the existing technology or a part of the technical solution, and the computer software product is stored in a storage medium. It contains several instructions to make a computer device (which can be a personal computer, a server, or a network device, etc.) execute all or part of the steps of the methods in the various embodiments of the patent application. The aforementioned storage media include: U disk, mobile hard disk, read-only memory (ROM), random access memory (RAM), magnetic disk or optical disk and other media that can store program code .

The above are only specific implementations of this patent application, but the protection scope of this patent application is not limited to this. Any person skilled in the art can easily think of changes or substitutions within the technical scope disclosed in this patent application. All should be covered within the protection scope of this patent application. Therefore, the protection scope of this patent application shall be subject to the protection scope of the claims.

Claims

An information transmission method for data packet repetition, characterized in that it comprises:

A first radio access network RAN device determines first information, where the first information includes information about at least one logical channel in the first RAN device;

The first RAN device sends the first information to the second RAN device, where the first information is used to indicate the data packet repetition auxiliary information of the first RAN device.
An information transmission method for data packet repetition, characterized in that it comprises:

The second radio access network RAN device receives first information sent by the first RAN device, where the first information includes information about at least one logical channel in the first RAN device, and the first information is used to indicate the second A data packet of a RAN device repeats auxiliary information;

The second RAN device decides that the data packet is repeated according to the first information.
The method according to claim 1 or 2, wherein the information of the at least one logical channel comprises at least one of the following information: the logical channel identifier of the at least one logical channel, the information of the at least one logical channel Logical channel index, radio quality auxiliary information of the at least one logical channel, the tunnel identifier of the at least one tunnel corresponding to the at least one logical channel, the tunnel index of the at least one tunnel, and the downlink tunnel transmission of the at least one tunnel Layer address and tunnel endpoint identification TEID.
The method according to claim 1 or 3, or the method according to claim 2 or 3, wherein the first information is auxiliary information data, and the auxiliary information data includes PDCP repeated activation of the packet data convergence layer protocol At least one of suggestions and wireless quality auxiliary information.
The method according to claim 4, wherein the PDCP repeated activation suggestion is used to indicate the at least one logical channel or the at least one tunnel in which the activation data packet suggested by the first RAN device is repeated.
The method according to claim 4, wherein the wireless quality assistance information comprises wireless quality assistance information of the at least one logical channel of the first RAN device, or at least one corresponding to the at least one tunnel The wireless quality auxiliary information of the logical channel.
The method according to claim 5, wherein the PDCP repeated activation suggestion is used to indicate the at least one logical channel or the at least one tunnel in which the activation data packet suggested by the first RAN device is repeated, comprising:

The PDCP repeated activation suggestion includes at least two bits of information, and the at least two bits of information are used to indicate the at least one logical channel or the at least one tunnel in which the activation data packet suggested by the first RAN device is repeated .
The method according to claim 2 or 3, wherein the second RAN device determines data packet repetition according to the first information, comprising:

The second RAN device decides to activate the at least one logical channel or the data packet repetition of the at least one tunnel according to the first information.
The method according to claim 1, or the method according to claim 2 or 8, wherein the second RAN device is a managed PDCP entity node, and the first RAN device is a corresponding node.
The method according to claim 1, or the method according to claim 2 or 8, wherein the second RAN device is a centralized unit CU, and the first RAN device is a distributed unit DU.
The method according to claim 1, wherein the sending of the first information by the first RAN device to the second RAN device comprises:

The first RAN device sends the first information to the second RAN device via a third RAN device.
The method according to claim 2, wherein the second RAN device receiving the first information sent by the first RAN device comprises:

The second RAN device receives the first information sent by the first RAN device via a third RAN device.
The method according to claim 11 or 12, wherein the second RAN device is a centralized unit control plane network element CU-CP, the first RAN device is a distributed unit DU, and the third RAN device It is a centralized unit user plane network element CU-UP.
The method according to claim 1, 9 or 10, wherein the method further comprises:

The first RAN device receives the downlink data packet sent by the second RAN device through the at least one tunnel.
The method according to claim 14, wherein when the first RAN device receives the downlink data packet sent by the second RAN device through at least two tunnels, the downlink data packet has the same PDCP Serial number.
The method according to claim 11 or 13, wherein the method further comprises:

The first RAN device receives the downlink data packet sent by the third RAN device through the at least one tunnel.
The method according to claim 16, wherein when the first RAN device receives downlink data packets sent by the third RAN device through at least two tunnels, the downlink data packets have the same PDCP Serial number.
The method according to claim 2, 9 or 10, wherein the method further comprises:

The second RAN device sends a downlink data packet to the first RAN device through the at least one tunnel.
The method according to claim 18, wherein in the case where the second RAN device sends a downlink data packet to the first RAN device through at least two tunnels, the downlink data packet has the same PDCP sequence number .
The method according to claim 12 or 13, wherein the method further comprises:

The second RAN device sends data packet repeated transmission information to the third RAN device, where the data packet repeated transmission information includes transmission information of the at least one logical channel, and the data packet repeated transmission information is used to indicate the The third RAN device sends downlink data to the first RAN device according to the repeated transmission information of the data packet.
The method according to claim 20, wherein the transmission information of the at least one logical channel comprises at least one of the following information: the logical channel identifier of the at least one logical channel, the logical channel identifier of the at least one logical channel The channel index, the tunnel identifier of the at least one tunnel corresponding to the at least one logical channel, the tunnel index of the at least one tunnel, and the downlink tunnel transport layer address and TEID of the at least one tunnel.
A network device, characterized in that, the network device is a first radio access network RAN device, and the first RAN device includes a processor and a transceiver, wherein:

The processor is configured to determine first information, where the first information includes information about at least one logical channel in the first RAN device;

The transceiver is communicatively coupled with the processor, and is configured to send the first information to a second RAN device, where the first information is used to indicate the data packet repetition auxiliary information of the first RAN device.
A network device, wherein the network device is a second radio access network RAN device, and the second RAN device includes a processor and a transceiver, wherein,

The transceiver is configured to receive first information sent by a first RAN device, where the first information includes information about at least one logical channel in the first RAN device, and the first information is used to indicate the first Data packets of RAN equipment repeat auxiliary information;

The processor is communicatively coupled with the transceiver, and is configured to decide data packet repetition according to the first information.
The network device according to claim 22 or 23, wherein the information of the at least one logical channel comprises at least one of the following information: the logical channel identifier of the at least one logical channel, the at least one logical channel The logical channel index of the at least one logical channel, the wireless quality auxiliary information of the at least one logical channel, the tunnel identifier of the at least one tunnel corresponding to the at least one logical channel, the tunnel index of the at least one tunnel, and the downlink tunnel of the at least one tunnel The transport layer address and the tunnel endpoint identification TEID.
The network device according to claim 22 or 24, or the network device according to claim 23 or 24, wherein the first information is auxiliary information data, and the auxiliary information data includes a packet data convergence layer protocol PDCP Repeat at least one of the activation suggestion and the wireless quality assistance information.
The network device according to claim 25, wherein the PDCP repeated activation suggestion is used to indicate the at least one logical channel or the at least one tunnel in which the activation data packet suggested by the first RAN device is repeated.
The network device according to claim 25, wherein the wireless quality assistance information comprises wireless quality assistance information of the at least one logical channel of the first RAN device, or at least one corresponding to the at least one tunnel. The wireless quality auxiliary information of a logical channel.
The network device according to claim 26, wherein the PDCP repeated activation suggestion is used to indicate the at least one logical channel or the at least one tunnel in which the activation data packet suggested by the first RAN device is repeated, comprising :

The PDCP repeated activation suggestion includes at least two bits of information, and the at least two bits of information are used to indicate the at least one logical channel or the at least one tunnel in which the activation data packet suggested by the first RAN device is repeated .
The network device according to claim 23 or 24, wherein the processor is configured to decide data packet repetition according to the first information, comprising:

The processor is configured to decide to activate the data packet repetition of the at least one logical channel or the at least one tunnel according to the first information.
The network device according to claim 22, or the network device according to claim 23 or 29, wherein the second RAN device is a managed PDCP entity node, and the first RAN device is a corresponding node.
The network device according to claim 22, or the network device according to claim 23 or 29, wherein the second RAN device is a centralized unit CU, and the first RAN device is a distributed unit DU.
The network device according to claim 22, wherein the transceiver is configured to send the first information to a second RAN device, comprising:

The transceiver is configured to send the first information to the second RAN device via a third RAN device.
The network device according to claim 23, wherein the transceiver is configured to receive the first information sent by the first RAN device, comprising:

The transceiver is configured to receive the first information sent by the first RAN device via a third RAN device.
The network device according to claim 32 or 33, wherein the second RAN device is a centralized unit control plane network element CU-CP, the first RAN device is a distributed unit DU, and the third RAN device The equipment is a centralized unit user plane network element CU-UP.
The network device according to claim 22, 30 or 31, characterized by comprising:

The transceiver is further configured to receive a downlink data packet sent by the second RAN device through the at least one tunnel.
The network device according to claim 35, wherein when the transceiver is used to receive downlink data packets sent by the second RAN device through at least two tunnels, the downlink data packets have the same PDCP Serial number.
The network device according to claim 32 or 34, characterized by comprising:

The transceiver is further configured to receive a downlink data packet sent by the third RAN device through the at least one tunnel.
The network device according to claim 37, wherein, in a case where the transceiver is used to receive downlink data packets sent by the third RAN device through at least two tunnels, the downlink data packets have the same PDCP Serial number.
The network device according to claim 23, 30 or 31, characterized by comprising:

The transceiver is further configured to send a downlink data packet to the first RAN device through the at least one tunnel.
The network device according to claim 39, wherein when the transceiver is used to send downlink data packets to the first RAN device through at least two tunnels, the downlink data packets have the same PDCP sequence number .
The network device according to claim 33 or 34, characterized by comprising:

The transceiver is further configured to send data packet repeated transmission information to the third RAN device, where the data packet repeated transmission information includes transmission information of the at least one logical channel, and the data packet repeated transmission information is used to indicate The third RAN device sends downlink data to the first RAN device according to the data packet repeated transmission information.
The network device according to claim 41, wherein the transmission information of the at least one logical channel includes at least one of the following information: a logical channel identifier of the at least one logical channel, The logical channel index, the tunnel identifier of the at least one tunnel corresponding to the at least one logical channel, the tunnel index of the at least one tunnel, and the downlink tunnel transport layer address and TEID of the at least one tunnel.
A computer-readable storage medium, characterized in that the computer-readable storage medium stores computer instructions, when the instructions run on a computer, the computer executes any one of claims 1 to 21 method.