CN107454623B - Radio link control function entity and data processing method thereof - Google Patents

Radio link control function entity and data processing method thereof Download PDF

Info

Publication number
CN107454623B
CN107454623B CN201610369757.7A CN201610369757A CN107454623B CN 107454623 B CN107454623 B CN 107454623B CN 201610369757 A CN201610369757 A CN 201610369757A CN 107454623 B CN107454623 B CN 107454623B
Authority
CN
China
Prior art keywords
rlc
entity
data
sub
function
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
CN201610369757.7A
Other languages
Chinese (zh)
Other versions
CN107454623A (en
Inventor
孙军帅
王莹莹
陈锋
黄学艳
陈卓
易芝玲
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
China Mobile Communications Group Co Ltd
China Mobile Communications Ltd Research Institute
Original Assignee
China Mobile Communications Group Co Ltd
China Mobile Communications Ltd Research Institute
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by China Mobile Communications Group Co Ltd, China Mobile Communications Ltd Research Institute filed Critical China Mobile Communications Group Co Ltd
Priority to CN201610369757.7A priority Critical patent/CN107454623B/en
Publication of CN107454623A publication Critical patent/CN107454623A/en
Application granted granted Critical
Publication of CN107454623B publication Critical patent/CN107454623B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/06—Optimizing the usage of the radio link, e.g. header compression, information sizing, discarding information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/04—Error control
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
    • H04W80/02—Data link layer protocols

Abstract

The invention discloses an RLC functional entity and a method for processing data thereof, wherein the method comprises the following steps: dividing the RLC functional entity into at least one distributed RLC sub-functional entity and a centralized RLC sub-functional entity borne by a wireless cloud center (RCC), wherein each distributed RLC sub-functional entity comprises an RLC receiving entity borne by the RCC and an RLC transmitting entity borne by an RRS; the method comprises the following steps: the centralized RLC sub-function entity distributes first data to RLC sending entities of all distributed RLC sub-function entities; and the RLC receiving entity of each distributed RLC sub-function entity sends second data to the centralized RLC sub-function entity.

Description

Radio link control function entity and data processing method thereof
Technical Field
The present invention relates to an access network technology in the wireless field, and in particular, to a radio link control function entity and a method for processing data thereof.
Background
Aiming at various scenes such as 2G/3G/4G and 5G, the Next Generation Fronthaul Interface (NGFI) Network architecture of a Cloud platform based on centralization, collaboration, Cloud architecture and a green Radio Access Network (C-RAN) completes coverage of various scenes through a flexible Fronthaul Interface. Referring to fig. 1, a wireless cloud center (RCC) completes big data operation, and then sends an instruction to a Radio Remote System (RRS), and the RRS completes resource allocation of a corresponding air interface on the basis of an RCC operation result. Similarly, each RRS performs certain processing on information collected from the air interface and reports the processed information to the RCC.
As can be seen, the RCC-RRS distributed architecture mode needs to re-partition and distribute functions of the protocol stack placed thereon; exemplarily, if the RCC-RRS distributed architecture needs to implement a bidirectional Radio Bearer (RB), a protocol stack function of a Radio Link Control (RLC) functional entity on the RCC-RRS distributed architecture needs to be redesigned.
Here, the bidirectional RB has a data transmission function in both uplink and downlink directions, for example, referring to fig. 2, the bidirectional RB between a Base Station (Base Station) and a User Equipment (UE) is denoted as RBi, and the RBi may transmit data in the downlink direction from the Base Station to the UE or in the uplink direction from the UE to the Base Station; when the RBi performs data transmission between the base station and the UE, it needs to utilize a Packet Data Convergence Protocol (PDCP) functional entity and an RLC functional entity on the base station side, and a PDCP functional entity and an RLC functional entity on the UE side.
The 5G network architecture provides a distributed architecture of an access network, air interface protocol stacks are respectively operated on different equipment entities, and transmission among the distributed entities can be non-ideal transmission; in a base station architecture represented by an RCC-RRS distributed architecture, the protocol stack function of an RLC functional entity needs to be redesigned so as to realize the control of a bidirectional RB carried by the RCC-RRS distributed architecture, and further meet various performance indexes such as the transmission network requirement, the data processing delay requirement, the data control (data out-of-order delivery and the like during reconstruction) requirement and the like of the RCC-RRS distributed architecture; in the prior art, a design scheme of a new RLC functional entity proposed for the control of bidirectional RBs carried by an RCC-RRS distributed architecture is lacked.
Disclosure of Invention
In order to solve the above technical problems, embodiments of the present invention provide an RLC functional entity and a method for processing data thereof, which can implement clear segmentation of a protocol stack function between RCC-RRS, and fully meet requirements on time delay for ideal and non-ideal transmission between RCC-RRS.
The technical scheme of the invention is realized as follows:
the embodiment of the invention provides a method for processing data by an RLC functional entity, which comprises the steps of dividing the RLC functional entity into at least one distributed RLC sub-functional entity and a centralized RLC sub-functional entity borne by an RCC, wherein each distributed RLC sub-functional entity comprises an RLC receiving entity borne by the RCC and an RLC sending entity borne by an RRS; the method comprises the following steps:
the centralized RLC sub-function entity distributes first data to RLC sending entities of all distributed RLC sub-function entities;
and the RLC receiving entity of each distributed RLC sub-function entity sends second data to the centralized RLC sub-function entity.
In this embodiment of the present invention, before the centralized RLC sub-function entity distributes the first data to the RLC sending entity of each distributed RLC sub-function entity, the method further includes: the centralized RLC sub-function entity receives data sent by the PDCP function entity in sequence;
correspondingly, the distributing the first data to the RLC sending entity of each distributed RLC sub-functional entity by the centralized RLC sub-functional entity includes:
and the centralized RLC sub-function entity distributes the first data to the RLC sending entities of each distributed RLC sub-function entity according to the sequence of receiving the data.
In this embodiment of the present invention, before the RLC receiving entity of each distributed RLC sub-function entity sends the second data to the centralized RLC sub-function entity, the method further includes: the RLC receiving entities of each distributed RLC sub-functional entity receive data in sequence;
correspondingly, the RLC receiving entity of each distributed RLC sub-functional entity sends second data to the centralized RLC sub-functional entity, including:
the RLC receiving entity of each distributed RLC sub-functional entity recombines the received data to generate second data; and the RLC receiving entity of each distributed RLC sub-function entity sends second data to the centralized RLC sub-function entity in sequence.
In this embodiment of the present invention, after the RLC receiving entity of each distributed RLC sub-function entity sends the second data to the centralized RLC sub-function entity, the method further includes:
the centralized RLC sub-function entity recombines the data sent by the RLC receiving entities of the distributed RLC sub-function entities and sends the recombined data to the PDCP function entity in sequence.
In the embodiment of the present invention, the method further includes: the centralized RLC sub-function entity controls at least one of the following processes: and establishing a distributed RLC sub-function entity and deleting the distributed RLC sub-function entity.
In the embodiment of the present invention, the method further includes:
and when the distributed RLC sub-functional entity is the acknowledged mode RLC functional entity, setting the Routing (Routing) function of the distributed RLC sub-functional entity to be realized through RRS.
The embodiment of the invention also provides an RLC functional entity, which comprises at least one distributed RLC sub-functional entity and a centralized RLC sub-functional entity borne by the RCC, wherein each distributed RLC sub-functional entity comprises an RLC receiving entity borne by the RCC and an RLC transmitting entity borne by the RRS; wherein the content of the first and second substances,
the centralized RLC sub-function entity is used for distributing first data to the RLC sending entities of all the distributed RLC sub-function entities;
and the RLC receiving entity of each distributed RLC sub-function entity is used for sending second data to the centralized RLC sub-function entity.
In the embodiment of the present invention, the centralized RLC sub-function entity is further configured to receive data sent by the PDCP function entity before the first data is distributed to the RLC sending entity of each distributed RLC sub-function entity;
accordingly, the centralized RLC sub-function entity is specifically configured to distribute the first data to the RLC sending entities of the distributed RLC sub-function entities according to the order of receiving the data.
In this embodiment of the present invention, the RLC receiving entity of each distributed RLC sub-function entity is further configured to receive data in sequence before sending the second data to the centralized RLC sub-function entity;
correspondingly, the RLC receiving entity of each distributed RLC sub-function entity is specifically configured to recombine the received data to generate second data; and sending the second data to the centralized RLC sub-function entity in sequence.
In the embodiment of the present invention, the centralized RLC sub-function entity is further configured to, after receiving data sent by the RLC receiving entity of each distributed RLC sub-function entity, reassemble the received data, and send the reassembled data to the PDCP function entity in sequence.
In this embodiment of the present invention, the centralized RLC sub-function entity is further configured to implement control over at least one of the following processes: and establishing a distributed RLC sub-function entity and deleting the distributed RLC sub-function entity.
In the embodiment of the present invention, when the distributed RLC sub-functional entity is an acknowledged mode RLC functional entity, the distributed RLC sub-functional entity is configured to set its Routing function to be implemented by an RRS.
In the technical scheme of the embodiment of the invention, the RLC functional entity is divided into at least one distributed RLC sub-functional entity and a centralized RLC sub-functional entity borne by the RCC, and each distributed RLC sub-functional entity comprises an RLC receiving entity borne by the RCC and an RLC sending entity borne by the RRS; the method comprises the following steps: the centralized RLC sub-function entity distributes first data to RLC sending entities of all distributed RLC sub-function entities; the RLC receiving entity of each distributed RLC sub-function entity sends second data to the centralized RLC sub-function entity; therefore, the embodiment of the invention provides a bidirectional function control scheme of a total-division RLC bidirectional RB on a distributed base station architecture, wherein the scheme takes the RLC of the bidirectional RB as an example; firstly, the basic functions of a centralized RLC sub-function entity and a distributed RLC sub-function entity are controlled, the RLC functions are arranged in a totally separated mode, and secondly, the functions of the distributed RLC sub-function entity are arranged in a separated mode according to a data receiving end (Rx) and a data sending end (Tx), so that the clear segmentation of the functions of a protocol stack between RCC-RRS is achieved, and the time delay requirements of ideal and non-ideal transmission between RCC-RRS are completely compatible; the time delay caused by discontinuous transmission can be compatible; the system has good expansibility, and can quickly support a large number of users; the compatibility is good, and the RLC protocol entity in the 4G/5G network can be compatible.
Drawings
FIG. 1 is a schematic diagram of RCC and RRS deployment under NGFI;
FIG. 2 is a schematic link diagram of a bi-directional RB between a base station and a UE;
fig. 3 is a first diagram illustrating the distribution of RLC functions in acknowledged mode according to an embodiment of the present invention;
fig. 4 is a flowchart illustrating a method for processing data by an RLC functional entity according to an embodiment of the present invention;
fig. 5 is a second diagram illustrating the distribution of the RLC functions in the acknowledged mode according to an embodiment of the present invention;
FIG. 6 is a schematic flow chart illustrating data interaction between AM C-RLC and AM D-RLC in the embodiment of the present invention;
fig. 7 is a schematic structural diagram of an RLC functional entity according to an embodiment of the present invention.
Detailed Description
So that the manner in which the features and aspects of the embodiments of the present invention can be understood in detail, a more particular description of the embodiments of the invention, briefly summarized above, may be had by reference to the embodiments, some of which are illustrated in the appended drawings.
Aiming at the two-stage architecture mode of RCC-RRS, the embodiment of the invention provides an RLC functional entity and a method for processing data by the same, adds a new processing function on the basis of being compatible with the existing RLC protocol stack function, and does not affect the protocol function of the PDCP functional entity.
Fig. 3 is a first diagram illustrating the distribution of the Acknowledged Mode (AM) RLC functions according to an embodiment of the present invention, as shown in fig. 3, the AM RLC function may be an RLC function applied to a non-ideal forward backhaul (nonideal fronthaul); the AM RLC functional entity interacts with the upper layer through a single Service Access Point (SAP), that is, interacts with the upper layer through the AM-SAP in fig. 3; the AM RLC functional entity can send or receive data through an uplink DCCH and a downlink DCCH and an uplink DTCH.
Referring to fig. 3, the AM RLC functional entity may include a first-level AM RLC subfunction entity and n second-level AM RLC subfunction entities, where n is a natural number greater than 1; each of the second-level AM RLC subfunction entities is a Branch of the Radio Link, and thus, the n second-level AM RLC subfunction entities may be respectively expressed as a 1 st Link (Branch 1th of RL) to an nth Link (Branch of RL); the first-level AM RLC sub-functional entities correspond to the n second-level AM RLC sub-functional entities described above, and each of the second-level sub-functional entities may include a second-level sub-functional transmission (Tx) entity and a second-level sub-functional reception (Rx) entity.
Referring to fig. 3, among the various functions implemented by each of the second-level AM RLC subfunction transmitting entities, the Segmentation (Segmentation) Concatenation (Concatenation), adding an RLC header (Add RLC header), RLC control (RLC control), Retransmission buffer (Retransmission buffer), Routing (Routing), and other functions may all adopt existing RLC protocol functions, such as the existing RLC protocol functions in the current 36.322 protocol; among various functions implemented by each second-level AM RLC subfunction receiving entity, functions such as receive buffering (Reception buffer) & Hybrid Automatic Repeat reQuest reordering (harq reordering), RLC header deletion (Remove RLC header), Service Data Unit reassembly (SDU reassembly), and the like, may all adopt existing RLC protocol functions, such as existing RLC protocol functions in the current 36.322 protocol.
The first-level AM RLC sub-function entity can realize a Centralized transmission buffer (Centralized Transmission buffer) function and a Centralized SDU reassembling (Centralized SDU reassembling) function, and the Centralized Transmission buffer function is responsible for distributing data to each second-level AM RLC sub-function entity according to the sequence of high-level data distribution and controlling the establishment and deletion of a second-level AM RLC sub-function entity D-RLC; the Centralized SDUreassementation function is responsible for receiving data sent by each second-level AM RLC sub-functional entity, finishing recombination and delivering the data to a high level in sequence; the higher layer may be a PDCP layer, and in this embodiment of the present invention, the functional entity may also be a layer.
Here, each of the second-level AM RLC subfunction transmitting entities may further implement a Distributed Transmission buffer (Distributed Transmission buffer) function, and the Distributed Transmission buffer function may use a Transmission buffer (Transmission buffer) function in the existing RLC protocol function, or may be redesigned; illustratively, when the first-level AM RLC sub-functional entity distributes higher-level data to each second-level AM RLC sub-functional entity, the Distributed Transmission buffer function is responsible for receiving the data sent by the first-level AM RLC sub-functional entity, and then, performs the next processing on the received data according to the 36.322 protocol.
It can be seen that, for the RCC-RRS distributed architecture, the function of the RLC functional entity needs to be redefined in the embodiments of the present invention, which is specifically described below with reference to several embodiments.
First embodiment
A first embodiment of the present invention provides a method for processing data by an RLC functional entity, and fig. 4 is a flowchart illustrating the method for processing data by an RLC functional entity according to the embodiment of the present invention.
Here, when the centralized RLC sub-function entity is carried by the RCC, all functions of the centralized RLC sub-function entity may be implemented by the RCC, for example, both functions of data downlink transmission and uplink reception of the centralized RLC sub-function entity are implemented by the RCC.
When the RLC receiving entity of each distributed RLC sub-function entity is carried in the RCC, a function of each distributed RLC sub-function entity receiving data from a Media Access Control (MAC) function entity is implemented by the RCC.
When the RLC receiving entity of each distributed RLC sub-functional entity is carried in the RRS, the function of each distributed RLC sub-functional entity transmitting data to the MAC functional entity is implemented by the RRS.
As shown in fig. 4, the method for processing data by the RLC functional entity includes the following steps:
step 401: the centralized RLC sub-function entity distributes the first data to the RLC transmitting entities of the respective distributed RLC sub-function entities.
Here, the centralized RLC sub-function entity receives data transmitted by the PDCP function entity in order before the centralized RLC sub-function entity distributes the first data to the RLC transmission entities of the respective distributed RLC sub-function entities.
Correspondingly, the distributing the first data to the RLC sending entity of each distributed RLC sub-functional entity by the centralized RLC sub-functional entity includes:
the centralized RLC sub-function entity distributes the first data to the RLC sending entities of the distributed RLC sub-function entities according to the order of receiving the data.
Further, after the centralized RLC sub-function entity distributes the first data to the RLC sending entity of each distributed RLC sub-function entity, the RLC sending entity of each distributed RLC sub-function entity processes the received data and sends the processed data to the MAC function entity; it should be noted that the data processing manner of the RLC sending entity of each distributed RLC sub-functional entity may follow the existing data processing manner of the RLC functional entity, for example, when each distributed RLC sub-functional entity is an acknowledged mode RLC functional entity, the RLC sending entity of each distributed RLC sub-functional entity may implement the following existing RLC protocol functions: transmission buffer, Segmentation & Concatenation, AddRLC header, RLC control, Transmission buffer, and Routing.
Step 402: and the RLC receiving entity of each distributed RLC sub-function entity sends second data to the centralized RLC sub-function entity. It should be noted that the first data and the second data in the embodiment of the present invention are different data.
Illustratively, before the RLC receiving entity of each distributed RLC sub-function entity sends second data to the centralized RLC sub-function entity, the method further comprises: and the RLC receiving entity of each distributed RLC sub-functional entity receives data in sequence.
Correspondingly, the RLC receiving entity of each distributed RLC sub-functional entity sends second data to the centralized RLC sub-functional entity, including: the RLC receiving entity of each distributed RLC sub-functional entity recombines the received data to generate second data; and the RLC receiving entity of each distributed RLC sub-function entity sends second data to the centralized RLC sub-function entity in sequence.
Here, the data received by the RLC receiving entity of each of the above-described distributed RLC sub-functional entities may be data from the MAC functional entity.
It should be noted that, the RLC receiving entity of each distributed RLC sub-functional entity may adopt the existing data reassembly process of the RLC functional entity to reassemble the received data; for example, when each distributed RLC sub-functional entity is an acknowledged mode RLC functional entity, the RLC receiving entity of each distributed RLC sub-functional entity may implement the following existing RLC protocol functions: receiption buffer & HARQ reordering, Remove RLC header and SDUreassambly.
Further, after the RLC receiving entity of each distributed RLC sub-function entity sends the received second data to the centralized RLC sub-function entity, the centralized RLC sub-function entity reassembles the data sent by the RLC receiving entity of each distributed RLC sub-function entity, and sends the reassembled data to the PDCP function entity in sequence.
In this embodiment of the present invention, the centralized RLC sub-function entity is further configured to control at least one of the following processes: and establishing a distributed RLC sub-function entity and deleting the distributed RLC sub-function entity.
It can be seen that, in the embodiment of the present invention, since the entire centralized RLC sub-function entity is completely loaded on the RCC, the RCC can be used to coordinate and control the transceiving of data of a plurality of distributed RLC sub-function entities at the same time.
The RLC sending entity of each distributed RLC sub-function entity is borne on the RRS, so that each distributed RLC sub-function entity can provide real-time data sending support for a bottom layer such as an MAC function entity, the influence of transmission delay brought by a transmission network between RCC-RRS can be avoided, and the flexibility of the control of the Serial Number (SN) of the RLC function entity is ensured;
the RLC receiving entity of each distributed RLC sub-functional entity is borne on the RCC, although the time delay of received data packet recombination is increased, because the uplink packet processing is insensitive to the time delay, the RCC has strong processing function and high processing speed, the transmission time delay can be compensated to a certain extent, and meanwhile, a (re-establishment) flow can be quickly established during handover (handover); therefore, by taking into account that the receiving process (Rx) of each distributed RLC sub-function entity is put on the RCC in its entirety, a higher gain can be obtained.
Further, the centralized RLC sub-function entity includes at least one of: a transparent mode RLC functional entity, a confirmed mode RLC functional entity and an unacknowledged mode RLC functional entity; the distributed RLC sub-functional entity comprises at least one of: a transparent mode RLC functional entity, an acknowledged mode RLC functional entity and an unacknowledged mode RLC functional entity.
When the distributed RLC sub-functional entity is the acknowledged mode RLC functional entity, the Routing function of the distributed RLC sub-functional entity is set to be realized through RRS.
It can be seen that, since Routing function can be implemented by RRS, and a packet data unit (AM RLC status PDU) for indicating status of the acknowledged mode RLC needs to be processed on the distributed RLC sub-functional entity of the acknowledged mode RLC functional entity, after the AM RLC status PDU is received by the distributed RLC sub-functional entity, the processing is directly performed on the distributed RLC sub-functional entity; after the distributed RLC sub-functional entity receives a packet data unit (AM RLC data PDU) for representing data of an acknowledged mode RLC, the AM RLC data PDU is sent to the RCC to be processed.
Second embodiment
To further illustrate the object of the present invention, the first embodiment of the present invention is further illustrated.
The second embodiment of the invention also provides a method for processing data by the RLC functional entity, wherein in the second embodiment of the invention, the RLC functional entity is an AM RLC functional entity; the second embodiment of the invention provides a bidirectional function control scheme of a total fractional RLC bidirectional RB on a distributed base station architecture aiming at an RCC-RRS distributed architecture and a corresponding distributed AM RLC function of a 5G access network, and the scheme realizes the combination of the total fractional AM RLC and the RCC-RRS architecture capable of effectively supporting various 4G/5G scene requirements by controlling the function of the total fractional AM RLC on the RCC-RRS of the bidirectional RB.
Here, each AM RLC functional Entity (Entity) may simultaneously possess a plurality of sub-links, thereby dividing the AM RLC functional Entity into an AM Centralized RLC sub-functional Entity (C-RLC, Centralized RLC) and an AM Distributed RLC sub-functional Entity (D-RLC, Distributed RLC) as a sub-link; the AM C-RLC function mainly comprises a newly-added Centralized Transmission buffer (Centralized Transmission buffer) and Centralized SDU reassembly (Centralized SDU reassembling) function and a newly-added control function for the AM D-RLC; the functions of the AM D-RLC mainly include the entire functions of the conventional AM RLC.
It can be understood that, when a bidirectional RB is established, functions in different directions of one RB need to be established respectively, and on this basis, according to the definition of the functions of C-RLC and D-RLC in the distributed AM RLC and the definition of the internal data transmission function and the internal data reception function of the D-RLC, a second embodiment of the present invention provides a method for processing data by an AM RLC functional entity, which is specifically described below with reference to the drawings.
Fig. 5 is a functional distribution diagram of an RLC in acknowledged mode according to an embodiment of the present invention, and as shown in fig. 5, the AM RLC functional entity may be an RLC functional entity applied to an imperfect forward backhaul; the AM RLC functional entity interacts with the upper layer through a single SAP, that is, interacts with the upper layer through the AM-SAP in fig. 5; the AM RLC functional entity can send or receive data through an uplink DCCH and a downlink DCCH and an uplink DTCH.
Referring to fig. 5, the AM RLC functional entity may include one AM C-RLC and n AM D-RLC, where n is a natural number greater than 1; wherein each AM D-RLC is a Branch Link (Branch of the Radio Link), and thus, the n AMD-RLC can be respectively expressed as Branch 1th (AM D-RLC) to nth (Branch of RL) (AM D-RLC); the AM C-RLC corresponds to the above n AM D-RLC, each of which may include a transmission (Tx) entity and a reception (Rx) entity, and the transmission entities of the above n AM D-RLC are respectively labeled as RRS #1(Tx) to RRS # n (Tx) in fig. 5.
Here, the AM C-RLC and the receiving entity of each AM D-RLC are carried on the RCC, and the transmitting entity of each AM D-RLC is carried on the RRS, that is, various functions of the AM C-RLC and the data receiving function of the AM D-RLC are carried on the RCC, and the data transmitting function of the AM D-RLC is carried on the RRS.
Referring to fig. 5, among various functions implemented by the transmitting entity of each AM D-RLC, functions such as Transmission buffer (Transmission buffer), Segmentation (Segmentation) Concatenation (Concatenation), adding RLC header (add RLC header), RLC control (RLC control), Retransmission buffer (Retransmission buffer), and Routing (Routing) may all adopt existing RLC protocol functions, such as existing RLC protocol functions in the existing 36.322 protocol; among various functions implemented by the receiving entity of each AM D-RLC, functions such as receive buffering (Reception buffer), Hybrid Automatic Repeat reQuest reordering (HARQ reordering), RLC header deletion (Remove RLC header), Service data unit reassembly (SDU reassembly), and the like, may all adopt existing RLC protocol functions, such as existing RLC protocol functions in the current 36.322 protocol.
It can be understood that, during the whole data receiving process, the receiving entity of each AM D-RLC delivers the data packets to the AM C-RLC in sequence according to the reassembled sequence, and in the AM C-RLC, the data from each AM D-RLC is processed next based on the Centralized SDU reassembling function.
The AM C-RLC can realize a Centralized Transmission buffer function and a Centralized SDUreassortment function, and the Centralized Transmission buffer function is responsible for distributing data to each AM D-RLC according to the sequence issued by the high-level data and controlling the establishment and deletion of the AM D-RLC; the Centralized SDU reassembling function is responsible for receiving data sent by each AM D-RLC, completing reassembly and submitting the data to a high layer in sequence; the higher layer may be a PDCP layer, and in this embodiment of the present invention, the functional entity may also be a layer.
Here, illustratively, when the first-level AM RLC sub-functional entity distributes higher-level data to each second-level AM RLC sub-functional entity, the Transmission buffer function is responsible for receiving the data sent by the first-level AM RLC sub-functional entity, and then, performs the next processing on the received data according to the 36.322 protocol.
It can be seen that, in the embodiment of the present invention, since the whole AM C-RLC is completely loaded on the RCC, the RCC can be used to coordinate and control the data transmission and reception of multiple AM D-RLC simultaneously.
Each AM D-RLC sending entity is borne on the RRS, so that each AM RLC functional entity can provide real-time data sending support for a bottom layer such as an MAC functional entity, the influence of transmission delay brought by a transmission network between RCC-RRS can be avoided, and the flexibility of the control of the Serial Number (SN) of the RLC functional entity is ensured; in addition, when the Routing function of each AM D-RLC is set to be realized through RRS, since AM RLC status PDU needs to be processed on the AM D-RLC, after the AM D-RLC receives the AM RLC status PDU, the AM D-RLC is directly processed on the AM D-RLC; and after receiving the AM RLC data PDU, the AM D-RLC sends the AM RLC data PDU to the RCC for processing.
Each AM D-RLC receiving entity is loaded on the RCC, although the time delay of received data packet recombination is increased, the uplink packet processing is insensitive to the time delay, the RCC has strong processing function and high processing speed, the transmission time delay can be compensated to a certain extent, and meanwhile, a re-estimation process can be rapidly carried out during handover; therefore, by taking comprehensive consideration, the receiving process of each AM D-RLC is completely put on the RCC to obtain higher gain.
FIG. 6 is a schematic diagram illustrating a data interaction procedure between AM C-RLC and AM D-RLC in an embodiment of the present invention, as shown in FIG. 6, PDCPRLIndicating PDCP functionEntity, MACUEMAC function entity representing UE side, AM D-RLC Rx representing AM D-RLC receiving entity, AM D-RLC Tx representing AM D-RLC transmitting entity, MACCC1To MACCCnRespectively represent MAC functional entities corresponding to the 1 st to nth control channels.
Referring to FIG. 6, for the transmitting end, when the AM C-RLC receives the data from the PDCPRLAfter the data is transmitted, the data is processed by a Centralized Transmission buffer function, where the AM C-RLC receives the data from the PDCPRLThe transmitted Data is user Data (UE's Data); the Centralized Transmission buffer function is responsible for assigning MAC addresses to MAC addressesUEInitiate a data send request (Allocation Req), MACUESending a data Allocation response (Allocation Resp) to the AM C-RLC according to the monitored air interface quality of the UE on each Control Channel (CC); then, in the AM C-RLC, the Centralized Transmission buffer function may respectively send a plurality of RLC SDUs to the corresponding AMD-RLC Tx according to the indication of the allocation response, and the AM D-RLC Tx may store the received data in the form of buffer data; in AM D-RLC Tx, RLC PDUs are sent to the MAC on each CC in a conventional manner based on the functions of Transmission buffer, etcCCIn FIG. 6, RLC PDUs can be transmitted to the MAC separatelyCC1To MACCCn。
For the receiving end, AM D-RLC Tx is receiving from MACCC1To MACCCnAfter the RLC PDU is received, determining the content of the RLC PDU by a Routing function; if the RLC PDU is a status PDU, processing the AM RLC PDU at the AM D-RLC Tx, and updating corresponding control parameters and states; if the RLC PDU is the data PDU, the RLC PDU is sent to an AM D-RLC Rx on the RCC to be processed, and after the AM D-RLC Rx completes data recombination, the recombined data are sequentially submitted to the AM C-RLC; in AM C-RLC, SDU Reordering (Reordering) processing may be performed on received Data, which is user Data (UE's Data); AM C-RLC sends processed data to PDCPRL。
Third embodiment
A third embodiment of the present invention further provides an RLC functional entity, which is directed to the method for processing data by an RLC functional entity in the first embodiment of the present invention.
Fig. 7 is a schematic structural diagram of an RLC functional entity according to an embodiment of the present invention, and as shown in fig. 7, the RLC functional entity includes: at least one distributed RLC sub-functional entity 72, and a centralized RLC sub-functional entity 71 carried by the RCC, each distributed RLC sub-functional entity 72 comprising: an RLC receiving entity 721 carried in the RCC and an RLC sending entity 722 carried in the radio remote system RRS; wherein the content of the first and second substances,
the centralized RLC sub-function 71 is configured to distribute the first data to the RLC sending entity 722 of each distributed RLC sub-function 72;
the RLC receiving entity 721 of each distributed RLC sub-function entity 72 is configured to send second data to the centralized RLC sub-function entity.
It should be noted that the first data and the second data in the embodiment of the present invention are different data.
Specifically, the RLC receiving entity 721 of each distributed RLC sub-functional entity 72 is further configured to receive data in sequence before sending the second data to the centralized RLC sub-functional entity;
correspondingly, the RLC receiving entity 721 of each distributed RLC sub-functional entity 72 is specifically configured to reassemble the received data to generate second data; and send the second data to the centralized RLC sub-function 71 in sequence.
Further, the centralized RLC sub-function 71 is further configured to receive data sent by a packet data convergence protocol PDCP function before distributing the first data to the RLC sending entity 722 of each distributed RLC sub-function 72;
accordingly, the centralized RLC sub-functional entity 71 is specifically configured to distribute the first data to the RLC sending entity 722 of each distributed RLC sub-functional entity 72 according to the order of receiving the data.
The centralized RLC sub-function 71 is further configured to, after receiving the data sent by the RLC receiving entity 721 of each distributed RLC sub-function 72, reassemble the received data, and send the reassembled data to the PDCP function in sequence.
Further, the centralized RLC sub-function entity 71 is further configured to implement control of at least one of the following processes: and establishing a distributed RLC sub-function entity and deleting the distributed RLC sub-function entity.
Further, when the distributed RLC sub-functional entity 72 is an acknowledged mode RLC functional entity, the distributed RLC sub-functional entity is configured to set the Routing function of the distributed RLC sub-functional entity to be implemented by the RRS.
Those skilled in the art will understand that the implementation functions of each unit in the RLC functional entity shown in fig. 7 can be understood by referring to the related description of the method for processing data by the RLC functional entity. The functions of the units in the RLC functional entity shown in fig. 7 may be implemented by a program running on a processor, or may be implemented by specific logic circuits.
The technical schemes described in the embodiments of the present invention can be combined arbitrarily without conflict.
In the embodiments provided in the present invention, it should be understood that the disclosed method and intelligent device may be implemented in other ways. The above-described device embodiments are merely illustrative, for example, the division of the unit is only a logical functional division, and there may be other division ways in actual implementation, such as: multiple units or components may be combined, or may be integrated into another system, or some features may be omitted, or not implemented. In addition, the coupling, direct coupling or communication connection between the components shown or discussed may be through some interfaces, and the indirect coupling or communication connection between the devices or units may be electrical, mechanical or other forms.
The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed on a plurality of network units; some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
In addition, all the functional units in the embodiments of the present invention may be integrated into one second processing unit, or each unit may be separately regarded as one unit, or two or more units may be integrated into one unit; the integrated unit can be realized in a form of hardware, or in a form of hardware plus a software functional unit.
The above description is only for the specific embodiments of the present invention, but the scope of the present invention is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present invention, and all the changes or substitutions should be covered within the scope of the present invention.

Claims (12)

1. A method for processing data by a Radio Link Control (RLC) functional entity is characterized in that the RLC functional entity is divided into at least one distributed RLC sub-functional entity and a centralized RLC sub-functional entity borne by a Radio Cloud Center (RCC), wherein each distributed RLC sub-functional entity comprises an RLC receiving entity borne by the RCC and an RLC transmitting entity borne by a radio frequency remote system (RRS); the method comprises the following steps:
the centralized RLC sub-function entity distributes first data to RLC sending entities of all distributed RLC sub-function entities; wherein, the first data is processed and issued by a Centralized Transmission buffer function after the Centralized RLC sub-function entity receives data sent by a PDCP entity;
the RLC receiving entity of each distributed RLC sub-function entity sends second data to the centralized RLC sub-function entity; and the second data is generated by recombining the received data by the RLC receiving entity of each distributed RLC sub-functional entity.
2. The method of claim 1, wherein before the centralized RLC sub-function entity distributes the first data to the RLC sending entities of the distributed RLC sub-function entities, the method further comprises: the centralized RLC sub-function entity receives data sent by a packet data convergence protocol PDCP function entity in sequence;
correspondingly, the distributing the first data to the RLC sending entity of each distributed RLC sub-functional entity by the centralized RLC sub-functional entity includes:
and the centralized RLC sub-function entity distributes the first data to the RLC sending entities of each distributed RLC sub-function entity according to the sequence of receiving the data.
3. The method of claim 1, wherein before the RLC receiving entity of each distributed RLC sub-function entity sends second data to the centralized RLC sub-function entity, the method further comprises: the RLC receiving entities of each distributed RLC sub-functional entity receive data in sequence;
correspondingly, the RLC receiving entity of each distributed RLC sub-functional entity sends second data to the centralized RLC sub-functional entity, including:
the RLC receiving entity of each distributed RLC sub-functional entity recombines the received data to generate second data; and the RLC receiving entity of each distributed RLC sub-function entity sends second data to the centralized RLC sub-function entity in sequence.
4. The method of claim 1, wherein after the RLC receiving entity of each distributed RLC sub-function entity sends second data to the centralized RLC sub-function entity, the method further comprises:
the centralized RLC sub-function entity recombines the data sent by the RLC receiving entities of the distributed RLC sub-function entities and sends the recombined data to the PDCP function entity in sequence.
5. The method according to any one of claims 1 to 4, further comprising: the centralized RLC sub-function entity controls at least one of the following processes: and establishing a distributed RLC sub-function entity and deleting the distributed RLC sub-function entity.
6. The method according to any one of claims 1 to 4, further comprising:
and when the distributed RLC sub-functional entity is the acknowledged mode RLC functional entity, setting the Routing function of the distributed RLC sub-functional entity to be realized through RRS.
7. The Radio Link Control (RLC) functional entity is characterized in that the RLC functional entity comprises at least one distributed RLC sub-functional entity and a centralized RLC sub-functional entity borne by a Radio Cloud Center (RCC), and each distributed RLC sub-functional entity comprises an RLC receiving entity borne by the RCC and an RLC transmitting entity borne by a Radio Remote System (RRS); wherein the content of the first and second substances,
the centralized RLC sub-function entity is used for distributing first data to the RLC sending entities of all the distributed RLC sub-function entities; wherein, the first data is processed and sent by a Centralized Transmission buffer function after the Centralized RLC sub-function entity receives data sent by a PDCP;
the RLC receiving entity of each distributed RLC sub-function entity is configured to send second data to the centralized RLC sub-function entity; and the second data is generated by recombining the received data by the RLC receiving entity of each distributed RLC sub-functional entity.
8. The RLC functional entity of claim 7, wherein the centralized RLC sub-functional entity is further configured to receive data transmitted by a packet data convergence protocol PDCP functional entity before distributing the first data to the RLC transmitting entities of the respective distributed RLC sub-functional entities;
accordingly, the centralized RLC sub-function entity is specifically configured to distribute the first data to the RLC sending entities of the distributed RLC sub-function entities according to the order of receiving the data.
9. The RLC functional entity of claim 7, wherein the RLC receiving entity of each distributed RLC sub-functional entity is further configured to receive data in order before sending second data to the centralized RLC sub-functional entity;
correspondingly, the RLC receiving entity of each distributed RLC sub-function entity is specifically configured to recombine the received data to generate second data; and sending the second data to the centralized RLC sub-function entity in sequence.
10. The RLC functional entity of claim 7, wherein the centralized RLC sub-functional entity is further configured to, after receiving data sent by the RLC receiving entity of each distributed RLC sub-functional entity, reassemble the received data, and send the reassembled data to the PDCP functional entity in sequence.
11. The RLC functional entity according to any of claims 7 to 10, wherein the centralized RLC sub-functional entity is further configured to implement control of at least one of: and establishing a distributed RLC sub-function entity and deleting the distributed RLC sub-function entity.
12. The RLC functional entity of any one of claims 7 to 10, wherein when the distributed RLC sub-functional entity is an acknowledged mode RLC functional entity, the distributed RLC sub-functional entity is configured to set its Routing function to be implemented by RRS.
CN201610369757.7A 2016-05-30 2016-05-30 Radio link control function entity and data processing method thereof Active CN107454623B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201610369757.7A CN107454623B (en) 2016-05-30 2016-05-30 Radio link control function entity and data processing method thereof

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201610369757.7A CN107454623B (en) 2016-05-30 2016-05-30 Radio link control function entity and data processing method thereof

Publications (2)

Publication Number Publication Date
CN107454623A CN107454623A (en) 2017-12-08
CN107454623B true CN107454623B (en) 2020-06-23

Family

ID=60484865

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201610369757.7A Active CN107454623B (en) 2016-05-30 2016-05-30 Radio link control function entity and data processing method thereof

Country Status (1)

Country Link
CN (1) CN107454623B (en)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107819764B (en) * 2017-11-13 2020-06-02 重庆邮电大学 Evolution method of C-RAN-oriented data distribution mechanism
CN108650258B (en) * 2018-05-09 2021-03-02 东南大学 Self-adaptive method for AM entity data transmission of narrow-band Internet of things wireless link protocol sublayer

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP4521430B2 (en) * 2007-08-10 2010-08-11 富士通株式会社 Wireless transmission device, wireless reception device, wireless transmission method, and wireless reception method
US8254410B2 (en) * 2009-04-30 2012-08-28 Telefonaktiebolaget L M Ericsson (Publ) Systems and methods for transmitting radio link control (RLC) data blocks
EP2777317B1 (en) * 2011-11-09 2018-06-27 Telefonaktiebolaget LM Ericsson (publ) Congestion control for multi flow data communication
CN104506279B (en) * 2014-12-29 2017-10-24 武汉虹信通信技术有限责任公司 For the up-downgoing method for parallel processing under RLC AM patterns in LTE

Also Published As

Publication number Publication date
CN107454623A (en) 2017-12-08

Similar Documents

Publication Publication Date Title
US10594615B2 (en) Method for controlling transmission of data
RU2762681C2 (en) Data transmission method, access network device, terminal and communication system
CN107484183B (en) Distributed base station system, CU, DU and data transmission method
CN104244426B (en) A kind of resource allocation methods and device of Data Radio Bearer DRB
CN102939729B (en) Packet control process in GSM and GSM
CN108282248B (en) Data transmission method, network side equipment and user equipment
JP2019517760A (en) System and method for cell switching
EP3244679A1 (en) Radio bearer reconfiguration method, establishing method, user equipment and base station
EP3447978A1 (en) Data transmission method and device
CN109392004A (en) Communication means, base station, terminal device and system
CN105532067A (en) Scheduling virtualization for mobile cloud for low latency backhaul
EP3664507B1 (en) Communication methods for a master base station and a terminal
CN103782569A (en) Data processing device and method
CN104519529A (en) Method, equipment and system for transmission control on user equipment
KR20180099135A (en) Method and apparatus of packet generation and distribution for inter-site ca
CN107454623B (en) Radio link control function entity and data processing method thereof
CN110012506B (en) Data transmission method and communication equipment
CN111757507A (en) Communication method and device
CN111742577B (en) Method for mobility enhancement and user equipment thereof
CN106851724B (en) Wireless resource processing method and device
CN107786493B (en) Data transmission method and device
US20220338288A1 (en) Communication method and apparatus
WO2017140184A1 (en) Data processing method self-adaptive to access network architectures, access network architecture, and storage medium
KR20190026239A (en) Method for controlling HARQ process in Cloud-RAN, base station system and user equipment therefor
CN106101286B (en) Data transmission method and device, UM RLC entity based on the unidirectional RB of total and fractional RLC

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant