WO2017140277A1

WO2017140277A1 - Radio link control function entity, and data processing method and storage medium thereof

Info

Publication number: WO2017140277A1
Application number: PCT/CN2017/074164
Authority: WO
Inventors: 孙军帅; 王莹莹; 崔春风; 陈卓; 黄学艳; 易芝玲
Original assignee: 中国移动通信集团公司
Priority date: 2016-02-18
Filing date: 2017-02-20
Publication date: 2017-08-24
Also published as: CN107094121B; CN107094121A

Abstract

Disclosed in the present invention are an RLC function entity and a data processing method thereof, the method comprising: dividing an RLC function entity into a centralised RLC sub-function entity and distributed RLC sub-function entities; the method comprises: the centralised RLC sub-function entity sending first data to each distributed RLC sub-function entity; and each distributed RLC sub-function entity sending the received second data to the centralised RLC sub-function entity, the centralised RLC sub-function entity sorting the second data, and sending the sorted second data to a PDCP function entity.

Description

Wireless link control function entity and method thereof, storage medium

Technical field

The present invention relates to access network technologies in the wireless field, and in particular, to a radio link control function entity, a method for processing data thereof, and a storage medium.

Background technique

Next Generation Fronthaul Interface (NGFI) network architecture for cloud platforms based on centralized, collaborative, cloud-based and green wireless access networks (C-RAN, Centralized, Cooperative, Cloud&Clean-Radio Access Network) For 2G/3G/4G and 5G diverse scenarios, coverage of various scenes is accomplished through a flexible fronthaul interface. Referring to FIG. 1, a wireless cloud center (RCC) performs a big data operation, and then sends an instruction to a radio remote system (RRS, Radio Remote System), and the RRS completes resource allocation of the corresponding air interface based on the RCC operation result. . Similarly, each RRS performs certain processing on the information collected from the air interface and reports it to the RCC. A flexible connection between the RCC and the RRS is adopted. In order to reduce the data transmission pressure between the RCC and the RRS, the functions between the RCC and the RRS can be flexibly divided, and the RCC and the RRS are connected through a transmission network. The network connection between the RCC and the RRS introduces a large delay. Referring to the performance specifications of the transmission network delay and jitter of the currently supported long-distance evolution-based voice service (VoLTE), the maximum one-way time The delay is about 1.5ms, and the one-way delay between the physical access control (MAC) function entity and the radio link control (RLC) functional entity generally does not exceed 10us, and the MAC function The delay from the time when the entity sends the data request (Data Req) to the data received by the RLC function entity (Data) is generally within 300 us. Obviously, the RLC/MAC function partitioning method under the fronthaul of the traditional or ideal transmission network cannot be applied to the NGFI network architecture.

The prior art performs segmentation and reconstruction between a Packet Data Convergence Protocol (PDCP) functional entity and an RLC functional entity, and adds a reordering of PDCP Packet Data Unit (PDU) in the PDCP functional entity. Function, the function of the RLC function entity remains unchanged. However, this solution has the following problems:

1. It is necessary to add a sorting function to the data packet in the PDCP functional entity. This method confuses the functional division of the RLC functional entity and the PDCP functional entity, and destroys the principle of the protocol stack function division that only the RLC is responsible for packet sorting.

2. It is necessary to add a complete set of sequential send and receive reordering mechanisms in the PDCP functional entity, which is very large for the PDCP protocol stack.

3. In the current protocol, the PDCP function entity does not need to process the transparent mode (TM) data. If the PDCP function entity supports the data packet sorting function, in order to complete the protocol function, it is necessary to increase the TM mode. deal with.

4. When the PDCP function entity sorts the serial number (SN, Serial Number) of the PDCP PDU, it is necessary to receive the PDCP PDUs sent by multiple RLC function entities before they are sorted, resulting in large complexity and prolonged sorting.

Summary of the invention

To solve the above technical problem, an embodiment of the present invention provides a radio link control function entity, a method for processing data, and a storage medium.

The method for processing data by the RLC function entity provided by the embodiment of the present invention, the RLC function entity is divided into a centralized RLC sub-function entity and a distributed RLC sub-function entity; the method includes:

Transmitting, by the centralized RLC sub-function entity, the first data to each of the distributed RLC sub-function entities;

Transmitting, by the distributed RLC sub-function entity, the received second data to the centralized RLC sub-function entity, the centralized RLC sub-function entity sorting the second data, and sorting the second data The second data is sent to the Packet Data Convergence Protocol PDCP functional entity.

In the embodiment of the present invention, the centralized RLC sub-function entity sends the first data to each of the distributed RLC sub-function entities, including:

The service data unit SDU sent by the centralized RLC sub-function entity to each of the distributed RLC sub-function entities constitutes an RLC SDU cluster;

The centralized RLC sub-function entity sends the RLC SDUs in the RLC SDU cluster to each of the distributed RLC sub-function entities in a receiving order.

In the embodiment of the present invention, the centralized RLC sub-function entity sorts the second data, and sends the sorted second data to the packet data convergence protocol PDCP functional entity, including:

The centralized RLC sub-function entity sorts the RLC SDUs in the RLC SDU cluster, and sends the sorted RLC SDUs to the PDCP functional entities in order.

In the embodiment of the present invention, each of the distributed RLC sub-function entities sends the received second data to the centralized RLC sub-function entity, including:

Each of the distributed RLC sub-function entities receives the second data in sequence, and reassembles the second data, and sequentially sends the reassembled second data to the centralized RLC sub-function entity.

In the embodiment of the present invention, the centralized RLC sub-function entity includes: a transparent mode RLC function entity, an acknowledge mode/non-acknowledge mode RLC sending entity, and an acknowledge mode/non-acknowledge mode RLC receiving entity.

A radio link control RLC function entity provided by the embodiment of the present invention includes: a centralized RLC sub-function entity and a distributed RLC sub-function entity;

The centralized RLC sub-function entity is configured to send first data to each of the distributed RLC sub-function entities;

The distributed RLC sub-function entity is configured to send the received second data to the centralized RLC sub-function entity;

The centralized RLC sub-function entity is further configured to sort the second data sent by the distributed RLC sub-function entity, and send the sorted second data to the PDCP function entity.

In the embodiment of the present invention, the SDUs that are sent by the centralized RLC sub-function entity to each of the distributed RLC sub-function entities constitute an RLC SDU cluster;

The centralized RLC sub-function entity is further configured to send the RLC SDUs in the RLC SDU cluster to each of the distributed RLC sub-function entities in a receiving order.

In the embodiment of the present invention, the centralized RLC sub-function entity is further configured to sort the RLC SDUs in the RLC SDU cluster, and send the sorted RLC SDUs to the PDCP functional entity in sequence.

In the embodiment of the present invention, the distributed RLC sub-function entity is further configured to receive the second data in order, and reassemble the second data, and then send the reassembled second data to the centralized RLC sub-function entity.

An embodiment of the present invention provides a storage medium, where the computer program stores a computer program, where the computer program is configured to execute the wireless link control RLC function entity to process data when the processor runs the computer program. method.

In the technical solution of the embodiment of the present invention, the RLC functional entity is divided into a centralized RLC sub-function entity and a distributed RLC sub-function entity; the centralized RLC sub-function entity sends data to each distributed RLC sub-function entity. Transmitting, by the distributed RLC sub-function entity, the received data to the centralized RLC sub-function entity, the centralized RLC sub-function entity sorting the data, and sending the sorted data to PDCP functional entity. It can be seen that the embodiment of the present invention provides a distributed RLC functional entity of an Open Loop Push Mode in a wireless mobile network, and the solution of the embodiment of the present invention is not a PDCP functional entity. Any changes are made to divide the RLC functional entity into two functional parts: a centralized RLC sub-function entity (C-RLC, Centralized RLC) and a distributed RLC sub-function entity (D-RLC, Distributed RLC). The C-RLC function is new. Added function, the D-RLC function keeps the existing RLC function unchanged. When transmitting data, the C-RLC directly sends the data to the D-RLC. When receiving the data, the D-RLC directly sends the data to the C-RLC. No need to exchange data flow control information, send and receive data through open-loop cramming. It is compatible with the delay caused by discontinuous transmission; it has good scalability and can quickly support a large number of users. Good compatibility and compatibility with RLC functional entities in 4G/5G networks.

DRAWINGS

Figure 1 is a schematic diagram of RCC and RRS deployment under NGFI;

2 is a schematic flowchart of a method for processing data by an RLC function entity according to an embodiment of the present invention;

3 is an overall frame diagram of an open-loop cramming distributed RLC according to an embodiment of the present invention;

4 is an overall frame diagram of an RLC function according to an embodiment of the present invention;

FIG. 5 is a schematic structural diagram of an RLC functional entity according to an embodiment of the present invention.

detailed description

The embodiments of the present invention are described in detail below with reference to the accompanying drawings.

The 5G network architecture proposes a distributed architecture of access networks. The air interface protocol stacks are respectively running on different distributed entities, and the transmission between distributed entities is non-ideal transmission. Taking the RCC-RRS distributed architecture as an example, the transmission between RCC-RRS is non-ideal transmission, so it is necessary to consider the partition reconstruction of the protocol stack function under non-ideal transmission. Based on this, the embodiment of the present invention re-divides the functions of the RLC functional entity according to the non-ideal fronthaul transmission characteristics between the RCC-RRSs, so as to adapt to various performance indexes when the non-ideal transmission network is used between the RCC-RRSs.

For the distributed architecture of the 5G access network, and the existing problems of the PDCP/RLC segmentation and reconstruction, the embodiment of the present invention provides an Open Loop Push Mode distributed RLC scheme, which is an embodiment of the present invention. The technical solution is compatible with the existing RLC protocol stack function and adds new processing functions, and does not have any influence on the PDCP protocol function.

2 is a schematic flowchart of a method for processing data by an RLC function entity according to an embodiment of the present invention. In this example, an RLC functional entity is divided into a centralized RLC sub-function entity and a distributed RLC sub-function entity; as shown in FIG. 2 The method for processing data by a distributed RLC functional entity includes the following steps:

Step 201: The centralized RLC sub-function entity sends the first data to each of the distributed RLC sub-function entities.

Referring to FIG. 3, an embodiment of the present invention divides an RLC functional entity into two functional entities, C-RLC and D-RLC. The C-RLC refers to a centralized RLC sub-function entity, and the D-RLC refers to a distributed RLC sub-function entity.

Each D-RLC is a Branch of the Radio Link, one C-RLC may correspond to multiple D-RLCs, and the C-RLC corresponds to one radio bearer (RB, Radio Bearer) of each UE, and each The D-RLC is responsible for providing data transmission and reception functions for an air interface channel of a user equipment (UE, User Equipment).

In the embodiment of the present invention, the C-RLC and the D-RLC exchange and receive data packets, and there is no need to exchange any data amount control information between the two, and the D-RLC does not need to send a data request to the C-RLC. The RLC sends data to the D-RLC according to the data throughput sent by each D-RLC.

Step 202: The distributed RLC sub-function entity sends the received second data to the centralized RLC sub-function entity, and the centralized RLC sub-function entity sorts the second data, and The sorted second data is sent to the packet data convergence protocol PDCP functional entity. It should be noted that the first data and the second data in the embodiment of the present invention are different data.

In the embodiment of the present invention, each D-RLC sends the received data to the C-RLC, and the C-RLC sorts according to the order specified by the protocol, and then delivers to the PDCP functional entity in order. Each D-RLC receives data in the order in which it is sent to the C-RLC. The C-RLC is only responsible for the ordering of data packets between different D-RLCs.

In the embodiment of the present invention, the connection between the C-RLC and the D-RLC may be performed through a non-ideal transmission network of the NGFI, or may be performed through an ideal transmission network.

In the embodiment of the present invention, the function of the C-RLC (that is, the centralized RLC sub-function entity) is: when the data is sent, the service data unit (SDU) sent to each D-RLC forms an RLC SDU cluster ( Cluster), the RLC SDUs in the RLC SDU cluster are sent to each D-RLC in the order of reception, and the RLC SDUs are not cut to ensure that all RLC SDUs are sent; when receiving data, multiple D-RLCs are completed. The sorted RLC SDU cluster data is sorted and reported to the upper layer (that is, the PDCP functional entity) in the correct order.

In the embodiment of the present invention, the function of the D-RLC (that is, the distributed RLC sub-function entity) is: when the data is sent, after receiving multiple RLC SDU data packets in the RLC SDU cluster from the C-RLC, according to the current 36.322 protocol The existing RLC protocol function completes the sequential transmission of data, including data cascading, header expansion, retransmission, and the like; when receiving data, the data is sequentially received according to the existing RLC protocol function in the 36.322 protocol. And reorganizing, the data is submitted to the C-RLC in the correct order of the RLC SDU cluster.

According to the foregoing solution of the embodiment of the present invention, the centralized RLC sub-function entity sends data to each of the distributed RLC sub-function entities, including:

Sending the number of the distributed RLC sub-function entity to each of the distributed RLC sub-function entities According to, including:

The distributed RLC sub-function entity sends the received data to the centralized RLC sub-function entity, including:

Each of the distributed RLC sub-function entities receives the data in order, and reorganizes the data, and sequentially sends the reassembled data to the centralized RLC sub-function entity.

In addition, the RLC functional entity of the embodiment of the present invention also has multiple transmission modes. Referring to FIG. 4, the RLC functional entity in the transparent mode (TM)/unacknowledged mode (UM)/acknowledgement mode (AM) in the 36.322 protocol is compared. The solution of the embodiment of the present invention designs an overall functional solution in three modes on the basis of ensuring compatibility, and adds a C-RLC function to the original functional entity, and the D-RLC function is a function of the existing three modes. .

In the three modes, the C-RLC function is the distribution of data and the reorganization of data on each D-RLC. For the RLC under the AM, since the AM RLC functional entity has both receiving and transmitting functions, the AM RLC functional entity has the C-RLC transceiving function at the same time. For TM/UM RLC, since the reception and transmission are separated in the function of TM/UM RLC, the transmission function of C-RLC is combined with the TM/UM RLC transmission entity, and the reception function of C-RLC and TM/UM The RLC receiving entities are combined.

According to the foregoing solution of the embodiment of the present invention, the centralized RLC sub-function entity includes: a transparent mode RLC function entity, an acknowledge mode/non-acknowledge mode RLC sending entity, and an acknowledge mode/non-acknowledge mode RLC receiving entity;

When in the transparent mode, the centralized RLC sub-function entity performs data reception/transmission through the transparent mode RLC function entity; when in the acknowledge mode/non-acknowledge mode, The centralized RLC sub-function entity transmits data through the acknowledge mode/non-acknowledge mode RLC transmitting entity, and receives data through the acknowledge mode/non-acknowledge mode RLC receiving entity.

5 is a schematic structural diagram of an RLC functional entity according to an embodiment of the present invention. As shown in FIG. 5, the functional entity includes: a centralized RLC sub-function entity 51 and a distributed RLC sub-function entity 52;

The centralized RLC sub-function entity 51 is configured to send the first data to each of the distributed RLC sub-function entities 52;

The distributed RLC sub-function entity 52 is configured to send the received second data to the centralized RLC sub-function entity 51;

The centralized RLC sub-function entity 51 is further configured to sort the second data sent by the distributed RLC sub-function entity 52, and send the sorted second data to the PDCP function entity.

In the embodiment of the present invention, the first data and the second data are different data.

The SDUs sent by the centralized RLC sub-function entity 51 to each of the distributed RLC sub-function entities 52 constitute an RLC SDU cluster;

The centralized RLC sub-function entity 51 is further configured to send the RLC SDUs in the RLC SDU cluster to each of the distributed RLC sub-function entities 52 in a receiving order.

The centralized RLC sub-function entity 51 is further configured to sort the RLC SDUs in the RLC SDU cluster, and send the sorted RLC SDUs to the PDCP functional entities in order.

The distributed RLC sub-function entity 52 is further configured to receive the second data in order, and reassemble the second data, and then send the reassembled second data to the centralized RLC sub-function entity 51 in sequence. .

The centralized RLC sub-function entity 51 includes: a transparent mode RLC function entity 511, an acknowledge mode/non-acknowledge mode RLC transmitting entity 512, an acknowledge mode/non-acknowledge mode RLC reception Entity 513; wherein

When in the transparent mode, the centralized RLC sub-function entity 51 performs data reception/transmission through the transparent mode RLC function entity 511; when in the acknowledge mode/non-acknowledge mode, the centralized RLC sub-function entity 51 The data is transmitted by the acknowledgment mode/non-acknowledgment mode RLC transmitting entity 512, and the data is received by the acknowledgment mode/non-acknowledgment mode RLC receiving entity 513.

Those skilled in the art should understand that the implementation functions of each unit in the RLC functional entity shown in FIG. 5 can be understood by referring to the related description of the method for processing data by the foregoing RLC functional entity. The functions of each unit in the RLC functional entity shown in FIG. 5 can be implemented by a program running on a processor, or can be implemented by a specific logic circuit.

The embodiment of the invention further describes a storage medium, wherein the storage medium stores a computer program, and the computer program is configured to execute the radio link control RLC described in the foregoing embodiments when the processor runs the computer program. A method by which a functional entity processes data.

The technical solutions described in the embodiments of the present invention can be arbitrarily combined without conflict.

In the several embodiments provided by the present invention, it should be understood that the disclosed method and smart device may be implemented in other manners. The device embodiments described above are merely illustrative. For example, the division of the unit is only a logical function division. In actual implementation, there may be another division manner, such as: multiple units or components may be combined, or Can be integrated into another system, or some features can be ignored or not executed. In addition, the coupling, or direct coupling, or communication connection of the components shown or discussed may be indirect coupling or communication connection through some interfaces, devices or units, and may be electrical, mechanical or other forms. of.

The units described above as separate components may or may not be physically separated, and the components displayed as the unit may or may not be physical units, that is, may be located in one place or distributed to multiple network units; You can choose some of them according to your actual needs. Or all of the units to achieve the purpose of the solution of the embodiment.

In addition, each functional unit in each embodiment of the present invention may be integrated into one second processing unit, or each unit may be separately used as one unit, or two or more units may be integrated into one unit; The above integrated unit can be implemented in the form of hardware or in the form of hardware plus software functional units.

The above is only a specific embodiment of the present invention, but the scope of the present invention is not limited thereto, and any person skilled in the art can easily think of changes or substitutions within the technical scope of the present invention. It should be covered by the scope of the present invention.

Industrial applicability

The present invention proposes an open-loop cramming distributed RLC functional entity, which does not make any changes to the PDCP functional entity, and divides the RLC functional entity into two functional parts: a centralized RLC sub-functional entity and a distributed RLC sub-functional entity, C - The RLC function is a new function. The D-RLC function keeps the existing RLC function unchanged. When the data is transmitted, the C-RLC directly sends the data to the D-RLC. When receiving the data, the D-RLC directly sends the data to the C-RLC. There is no need to exchange data flow control information between the two, and send and receive data through open-loop cramming. It is compatible with the delay caused by discontinuous transmission; it has good scalability and can quickly support a large number of users.

Claims

A radio link control method for processing data by an RLC function entity, the RLC functional entity is divided into a centralized RLC sub-function entity and a distributed RLC sub-function entity; the method includes:

Transmitting, by the centralized RLC sub-function entity, the first data to each of the distributed RLC sub-function entities;

Transmitting, by the distributed RLC sub-function entity, the received second data to the centralized RLC sub-function entity, the centralized RLC sub-function entity sorting the second data, and sorting the second data The second data is sent to the Packet Data Convergence Protocol PDCP functional entity.
The method for processing data by a radio link control RLC function entity according to claim 1, wherein the centralized RLC sub-function entity sends the first data to each of the distributed RLC sub-function entities, including:

The service data unit SDU sent by the centralized RLC sub-function entity to each of the distributed RLC sub-function entities constitutes an RLC SDU cluster;

The centralized RLC sub-function entity sends the RLC SDUs in the RLC SDU cluster to each of the distributed RLC sub-function entities in a receiving order.
The method for processing data by a radio link control RLC function entity according to claim 1, wherein said centralized RLC sub-function entity sorts said second data and transmits the sorted second data to packet data Convergence Protocol PDCP functional entities, including:

The centralized RLC sub-function entity sorts the RLC SDUs in the RLC SDU cluster, and sends the sorted RLC SDUs to the PDCP functional entities in order.
The method for processing data by a radio link control RLC function entity according to claim 1, wherein each of the distributed RLC sub-function entities transmits the received second data to the centralized RLC sub-function entity, including :

Each of the distributed RLC sub-function entities sequentially receives the second data, and reassembles the second data, and sequentially sends the reassembled second data to the centralized RLC sub-function. body.
The method for processing data by a radio link control RLC function entity according to any one of claims 1 to 4, wherein the centralized RLC sub-function entity comprises at least one of: a transparent mode RLC function entity, an acknowledge mode/non- Acknowledgment mode RLC transmitting entity, acknowledge mode/non-acknowledgment mode RLC receiving entity.
A radio link control RLC functional entity, the functional entity comprising: a centralized RLC sub-function entity and a distributed RLC sub-function entity;

The centralized RLC sub-function entity is configured to send first data to each of the distributed RLC sub-function entities;

The distributed RLC sub-function entity is configured to send the received second data to the centralized RLC sub-function entity;

The centralized RLC sub-function entity is further configured to sort the second data sent by the distributed RLC sub-function entity, and send the sorted second data to the PDCP function entity.
The radio link control RLC function entity according to claim 6, wherein the SDUs sent by the centralized RLC sub-function entity to each of the distributed RLC sub-function entities constitute an RLC SDU cluster;

The centralized RLC sub-function entity is further configured to send the RLCSDUs in the RLC SDU cluster to each of the distributed RLC sub-function entities in a receiving order.
The radio link control RLC functional entity according to claim 7, wherein the centralized RLC sub-function entity is further configured to sort RLC SDUs in the RLC SDU cluster and send the sorted RLC SDUs in order Give the PDCP functional entity.
The radio link control RLC function entity according to claim 6, wherein the distributed RLC sub-function entity is further configured to receive the second data in order, and reorganize the second data and then reorganize in order The second data is sent to the centralized RLC sub-function entity.
The radio link control RLC functional entity according to any one of claims 6 to 9, The centralized RLC sub-function entity includes at least one of the following: a transparent mode RLC function entity, an acknowledge mode/non-acknowledge mode RLC sending entity, and an acknowledge mode/non-acknowledge mode RLC receiving entity.
A storage medium having stored therein a computer program configured to perform the radio link control RLC functional entity of any one of claims 1 to 5 when the processor runs the computer program The method of processing data.