CN108337633B

CN108337633B - Data distribution configuration method, base station system and user terminal

Info

Publication number: CN108337633B
Application number: CN201810254570.1A
Authority: CN
Inventors: 黄曲芳; 曾清海
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2012-04-20
Filing date: 2012-12-05
Publication date: 2020-11-17
Anticipated expiration: 2032-12-05
Also published as: CN104247547A; CN108337633A; CN104247547B

Abstract

The embodiment of the invention discloses a data distribution configuration method, a base station system and a user terminal, relates to the field of communication, and can realize dynamic distribution. The data distribution configuration method of the embodiment of the invention comprises the following steps: the method comprises the steps that a main base station sends a first message to an auxiliary base station, so that the auxiliary base station determines an RB to be shunted and sets configuration parameters for the RB to be shunted; receiving a second message from the auxiliary base station, wherein the second message comprises the configuration parameters of the RB to be shunted; and sending a third message to the User Equipment (UE) so that the UE establishes a second Packet Data Convergence Protocol (PDCP) entity and a second Radio Link Control (RLC) entity for the RB to be shunted and performs data shunt configuration.

Description

Data distribution configuration method, base station system and user terminal

The present application requires a divisional application of a chinese patent application with an application number of 201280072392.1, entitled "data distribution configuration method, base station system, and user terminal", filed in 2014, 10, month 14, which is incorporated herein by reference in its entirety.

Technical Field

The present invention relates to the field of communications, and in particular, to a data offloading configuration method, a base station system, and a user terminal.

Background

With the development of mobile communication systems, the transmission rate and the service quality that can be provided by the communication systems are higher and higher, and users also put higher demands on the transmission rate. In order to guarantee The rate of most users without greatly increasing The configured bandwidth and provide higher throughput for a part of users, The third Generation Partnership Project (3 GPP) introduces a Carrier Aggregation (CA) technology. Carrier aggregation refers to that a User Equipment (User Equipment, UE for short) can simultaneously use multiple Component carriers (Component carriers, CC for short) to perform uplink and downlink communication, so as to support high-speed data transmission. When the user rate is reduced, some member carriers can be released, only one resident carrier is reserved, and the released transmission resources can be used by other users, so that the flexible and dynamic purpose is achieved.

According to the location of the base station where the aggregated carrier is located, carrier aggregation of a Long Term Evolution (LTE) system can be roughly divided into intra-base-station cell aggregation, inter-base-station cell aggregation, and the like. In the inter-base station cell aggregation scenario, data may be transmitted via multiple cells. According to the mechanism of data offloading, data offloading can be divided into two categories: one is data offloading based on Radio Bearer (RB), and the other is data offloading based on data packets.

Data distribution based on RB means that data distribution according to services is performed, when a UE has multiple services at the same time, data of some services is transmitted through one base station, and data of other services is transmitted through another base station.

The data distribution based on the data packet determines which base station the data is transmitted through according to the real-time air interface condition, so that two communication parties can select a proper base station for transmission according to the quality and the congestion degree of the air interface. In such data offloading, a Serving Gateway (SGW) determines through which base station each downlink data packet is transmitted, and two base stations negotiate to determine through which base station an uplink data packet is transmitted, and notify the UE through a scheduling command. Uplink data is transmitted through different base stations and finally converged to the SGW. Because data offloading is determined by the SGW, if the air interface condition changes and the data offloading policy is to be changed, the configuration of the protocol stack of the SGW needs to be changed, which involves behavior change at the network side, and the data offloading dynamic is poor, thereby affecting the use of users.

Disclosure of Invention

Various aspects of the present application provide a data offloading configuration method, a base station system, and a user terminal, which implement dynamic offloading.

One aspect of the present application provides a data offloading configuration method, including:

a main base station sends a first message to a secondary base station, wherein the first message is used for requesting the secondary base station to carry out data distribution, and the first message comprises an identification of a Radio Bearer (RB) and a quality of service (Qos) parameter of the RB, so that the secondary base station determines the RB to be distributed and sets configuration parameters for the RB to be distributed;

the main base station receives a second message from an auxiliary base station, wherein the second message comprises the configuration parameters of the RB to be shunted;

the master base station sends a third message to User Equipment (UE), wherein the third message comprises the identifier of the RB to be shunted and the configuration parameters of the RB to be shunted, so that the UE establishes a second PDCP entity and a second RLC entity for the RB to be shunted and performs data shunt configuration;

the UE is provided with a first PDCP entity, a first RLC entity and a MAC entity, and the second PDCP entity and the second RLC entity are positioned between the first RLC entity and the MAC entity.

Another aspect of the present application provides a downlink data transmission method for data offloading, including:

a PDCP entity of a main base station receives data from a Service Gateway (SGW) and processes the data to form first data, wherein the type of data distribution is partial distribution, the partial distribution refers to that the data part of one RB is transmitted by a secondary base station, and the partial distribution is transmitted by the main base station;

the RLC entity of the main base station adds a first RLC sequence number to the first data to form second data, and sends data to be shunted in the second data to a PDCP entity of an auxiliary base station;

the PDCP entity of the auxiliary base station sends the data to be shunted to the RLC entity of the auxiliary base station;

and the auxiliary base station processes the data to be distributed and sends the processed data to be distributed to the UE.

In another aspect of the present application, a downlink data transmission method is provided for data offloading, including:

the PDCP entity of the main base station receives data from a Service Gateway (SGW) and processes the data to form first data, wherein the data shunting type is complete shunting, and the complete shunting refers to that all data of one RB are transmitted through a secondary base station;

the RLC entity of the main base station receives the first data and sends the first data to a PDCP entity of a secondary base station;

the PDCP entity of the auxiliary base station receives the first data from the main base station and sends the first data to the RLC entity of the auxiliary base station;

and the auxiliary base station processes the first data and sends the processed first data to the UE.

In another aspect of the present application, a method for uplink data transmission is provided, including:

the method comprises the steps that UE reports BSR to a main base station and/or an auxiliary base station so that the main base station and/or the auxiliary base station can distribute uplink transmission resources for the UE;

a first PDCP entity of the UE processes the received data to form first data;

the first RLC entity of the UE carries out segmentation cascade connection on the first data, adds a first RLC sequence number to form second data, and sends data to be shunted in the second data to a second PDCP entity according to the received uplink transmission resources distributed by the auxiliary base station;

the second PDCP entity of the UE sends the shunt data to a second RLC entity of the UE;

a second RLC entity of the UE adds a second RLC sequence number to the received data to be distributed to form third data;

and the UE sends the processed third data to the auxiliary base station.

a first PDCP entity of the UE processes the received data to form first data;

a first RLC entity of the UE adds a first RLC sequence number to the first data to form second data, and sends data to be shunted in the second data to a second PDCP entity of the UE;

the second PDCP entity of the UE sends the data to be shunted to a second RLC entity of the UE;

the second RLC entity of the UE adds a second RLC sequence number to form third data after segmenting and cascading the received shunted data according to the received uplink transmission resources distributed by the auxiliary base station;

and the UE sends the processed third data to the auxiliary base station.

In another aspect of the present application, there is provided a base station, including:

a transmitter for:

sending a first message to a secondary base station, wherein the first message is used for requesting the secondary base station to perform data distribution, and the first message comprises an identifier of a Radio Bearer (RB) and a quality of service (Qos) requirement parameter of the RB, so that the secondary base station determines the RB to be distributed and sets configuration parameters for the RB to be distributed; and

sending a third message to the User Equipment (UE), wherein the third message comprises the identifier of the RB to be shunted and the configuration parameters of the RB to be shunted, so that the UE establishes a second PDCP entity and a second RLC entity for the RB to be shunted and performs data shunt configuration;

a receiver, configured to receive a second message from the secondary base station, where the second message includes a configuration parameter of the RB to be shunted;

In still another aspect of the present application, a base station system is provided, which includes a main base station and a secondary base station, wherein the main base station includes a PDCP entity and an RLC entity, and the secondary base station includes a PDCP entity and an RLC entity;

the PDCP entity of the main base station is used for receiving data from a Service Gateway (SGW) and processing the data to form first data, wherein the transmission method of the data is partial shunting;

the RLC entity of the main base station is used for adding a first RLC sequence number to the first data to form second data and sending data to be shunted in the second data to the PDCP entity of the auxiliary base station;

the PDCP entity of the auxiliary base station is used for sending the data to be shunted to the RLC entity of the auxiliary base station;

and the auxiliary base station is used for processing the data to be distributed and sending the processed data to be distributed to the UE.

the PDCP entity of the primary base station is configured to receive data from a serving gateway SGW, and process the data to form first data, where a transmission method of the data is complete offloading;

the RLC entity of the main base station is used for receiving the first data and sending the first data to the PDCP entity of the auxiliary base station;

the PDCP entity of the auxiliary base station is used for receiving the first data from the main base station and sending the first data to the RLC entity of the auxiliary base station;

In another aspect of the present application, a user equipment is provided, which includes a first PDCP entity, a first RLC entity, an MAC entity, and a physical layer, and further includes: the UE comprises a BSR reporting unit, a second PDCP entity and a second RLC entity, wherein the second PDCP entity and the second RLC entity are positioned between a first RLC entity and an MAC of the UE.

The BSR reporting unit is configured to report a BSR to a primary base station and/or a secondary base station, so that the primary base station and/or the secondary base station allocate uplink transmission resources to the UE;

the first PDCP entity is configured to process received data to form first data;

the first RLC entity is configured to perform segmentation and concatenation on the first data, add a first RLC sequence number to form second data, and send data to be shunted in the second data to the second PDCP entity according to the received uplink transmission resource allocated by the secondary base station;

the second PDCP entity is configured to send the shunted data to a second RLC entity of the UE;

the second RLC entity is configured to add a second RLC sequence number to the received data to be shunted to form third data, and send the third data to the MAC entity of the UE;

and the physical layer of the UE is used for sending the processed third data to the auxiliary base station.

the first RLC entity is configured to add a first RLC sequence number to the first data to form second data, and send data to be shunted in the second data to a second PDCP entity of the UE;

the second PDCP entity is configured to send the data to be shunted to a second RLC entity of the UE;

the second RLC entity is configured to add a second RLC sequence number after the received shunted data is segmented and cascaded according to the received uplink transmission resource allocated by the auxiliary base station, form third data, and send the third data to the MAC entity of the UE;

and the physical layer of the UE is used for sending the processed third data to the secondary base station.

The data distribution configuration method, the base station system and the user terminal described above have fast response to the change of the air interface condition measured at the bottom layer, and have good dynamic distribution effect.

Drawings

Fig. 1 is a schematic flow chart of a data offloading configuration method in an embodiment of the present invention;

fig. 2 is a schematic signaling interaction diagram of a data offloading configuration method in an embodiment of the present invention;

FIG. 3 is a diagram illustrating a protocol stack structure according to an embodiment of the present invention;

FIG. 4 is a schematic diagram illustrating a front-to-back comparison of data splitting configurations in an embodiment of the present invention;

fig. 5 is a flowchart illustrating a downlink data transmission method according to an embodiment of the present invention;

fig. 6 is a schematic diagram illustrating a downlink data transmission process according to an embodiment of the present invention;

fig. 7 is a second schematic diagram illustrating a downlink data transmission process according to an embodiment of the present invention;

fig. 8 is a second flowchart illustrating a downlink data transmission method according to an embodiment of the present invention;

fig. 9 is a flowchart illustrating an uplink data transmission method according to an embodiment of the present invention;

fig. 10 is a diagram illustrating an uplink data transmission process according to an embodiment of the present invention;

fig. 11 is a schematic diagram of a UE in an uplink data transmission process according to an embodiment of the present invention;

fig. 12 is a second flowchart illustrating an uplink data transmission method according to an embodiment of the present invention;

FIG. 13 is a diagram illustrating a base station according to an embodiment of the present invention;

FIG. 14 is a diagram illustrating a base station system according to an embodiment of the present invention;

fig. 15 is a schematic structural diagram of a user terminal in an embodiment of the present invention.

Detailed Description

The embodiment of the invention provides a data distribution configuration method, a base station system and a user terminal, which have the advantages of quick response to the change of air interface conditions and good dynamic distribution effect.

In the following description, for purposes of explanation and not limitation, specific details are set forth such as the particular system architecture, interfaces, techniques, etc., in order to provide a thorough understanding of the present invention. It will be apparent, however, to one skilled in the art that the present invention may be practiced in other embodiments that depart from these specific details. In other instances, detailed descriptions of well-known devices, circuits, and methods are omitted so as not to obscure the description of the present invention with unnecessary detail.

The various techniques described herein may be used in various Wireless communication systems, such as current 2G, 3G communication systems and next generation communication systems, such as Global System for Mobile communications (GSM), Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Wideband Code Division Multiple Access (WCDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), FDMA, General Packet Radio Service (Radio-Access, Long Term Evolution (GPRS), and other communication systems.

Various aspects are described herein in connection with a terminal and/or a base station controller.

A user terminal, which may be a wireless terminal or a wired terminal, may refer to a device that provides voice and/or data connectivity to a user, a handheld device having wireless connection capability, or other processing device connected to a wireless modem. A wireless terminal, which may be a mobile terminal such as a mobile telephone (or "cellular" telephone) and a computer having a mobile terminal, e.g., a portable, pocket, hand-held, computer-included, or vehicle-mounted mobile device, may communicate with one or more core networks via a Radio Access Network (RAN), and may exchange language and/or data with the RAN. For example, devices such as Personal Communication Service (PCS) phones, cordless phones, Session Initiation Protocol (SIP) phones, Wireless Local Loop (WLL) stations, and Personal Digital Assistants (PDAs) are known. A wireless Terminal may also be referred to as a system, a Subscriber Unit (Subscriber Unit), a Subscriber Station (Subscriber Station), a Mobile Station (Mobile), a Remote Station (Remote Station), an Access Point (Access Point), a Remote Terminal (Remote Terminal), an Access Terminal (Access Terminal), a User Terminal (User Terminal), a User Agent (User Agent), a User Device (User Device), or a User Equipment (User Equipment).

A base station (e.g., access point) can refer to a device in an access network that communicates over the air-interface, through one or more sectors, with wireless terminals. The base station may be configured to interconvert received air frames and IP packets as a router between the wireless terminal and the rest of the access network, which may include an Internet Protocol (IP) network. The base station may also coordinate management of attributes for the air interface. For example, the Base Station may be a Base Transceiver Station (BTS) in GSM or CDMA, a Base Station (NodeB) in WCDMA, or an evolved Node B (NodeB or eNB or e-NodeB) in LTE, and the present invention is not limited thereto.

The base station Controller may be a Base Station Controller (BSC) in GSM or CDMA, or may be a Radio Network Controller (RNC) in WCDMA, and the present invention is not limited thereto.

Additionally, the terms "system" and "network" are often used interchangeably herein. The term "and/or" herein is merely an association describing an associated object, meaning that three relationships may exist, e.g., a and/or B, may mean: a exists alone, A and B exist simultaneously, and B exists alone. In addition, the character "/" herein generally indicates that the former and latter related objects are in an "or" relationship.

In the embodiment, a data part partially split into one RB is transmitted via the secondary base station, and a part is transmitted via the primary base station; the data completely split into one RB is all transmitted via the secondary base station.

The present embodiment provides a data offloading configuration method, as shown in fig. 1 and fig. 2, the method includes:

101. the method comprises the steps that a main base station sends a first message to a secondary base station, wherein the first message is used for requesting the secondary base station to carry out data distribution, and the first message comprises an identification of a Radio Bearer (RB) and a quality of service (Qos) parameter of the RB, so that the secondary base station determines the RB to be distributed and sets configuration parameters for the RB to be distributed.

In this embodiment, a Primary base station (Primary evolved NodeB, abbreviated P-eNB) refers to a serving base station of a UE, and a Secondary evolved NodeB (abbreviated S-eNB) refers to a base station that participates in carrier aggregation of the UE and performs data offloading. In the architecture of this embodiment, the RAN side is connected to the SGW through the master base station.

Before data distribution, a flow of data distribution configuration is started first. After deciding to start data offloading, the primary base station sends a first message to the secondary base station through an X2 interface, where the first message may be, for example, a data offloading request message, and the first message includes RB identifiers and Quality of Service (Qos) parameters corresponding to each RB. In this embodiment, each RB identity and the Qos parameter corresponding to each RB may be presented in a list format including the RB with split, or in an array format. The Qos parameter may include any one or any combination of the following: the priority of the RB, whether the RB can be preempted, the uplink maximum bit rate, the uplink guaranteed bit rate, the downlink maximum bit rate, the downlink guaranteed bit rate, the maximum allowable delay, and the like. After receiving the data offloading request message, the secondary base station sets configuration parameters for each RB to be offloaded according to the RB list, where the configuration parameters may include any one or any combination of the following: packet Data Convergence Protocol (PDCP) entity, Radio Link Control (RLC) entity, Medium Access Control (MAC) entity, and Physical layer (Phy) related parameters.

Optionally, after receiving the first message, the secondary base station further determines which RBs may be allowed to be accessed according to its load condition, so as to determine which RBs to be configured with parameters, and after determining the RBs to be shunted, establishes a PDCP entity and an RLC entity for each RB to be shunted according to the Qos parameters of the RB, and sets configuration parameters. Such as: the main base station sends an RB list to the auxiliary base station, the RB list comprises three RBs of A/B/C, the auxiliary base station is requested to carry out shunt processing, and after the auxiliary base station is connected with a control algorithm, the auxiliary base station considers that the auxiliary base station can only bear two RBs of A/B, and then the auxiliary base station responds to the main base station: only two RBs a/B can be split.

PDCP is a radio transport protocol stack in UMTS or LTE that is generally responsible for compressing and decompressing IP headers, ciphering and deciphering packets, transmitting user data, and maintaining sequence numbers of radio bearers set for a lossless radio network service subsystem (SRNS). If the PDCP is configured to be 'without compression and without encryption and decryption', the PDCP entity transparently processes the data packet, i.e. does not process the data packet. The RLC entity is located above the MAC entity and mainly provides a segmentation concatenation and retransmission service for user data.

In addition, the first message may further include: and the shunting type identifier is used for indicating that the data shunting transmission is complete shunting or partial shunting. When the auxiliary base station sets the configuration parameters for each RB, whether the data on a certain RB is completely shunted or partially shunted can be known through the configuration parameters.

102. And the main base station receives a second message from the auxiliary base station, wherein the second message comprises the configuration parameters of the RB to be shunted.

After finishing setting the configuration parameters for each RB to be shunted, the secondary base station sends a second message to the primary base station, where the second message may be, for example, a data shunting response message, where the data shunting response message includes the configuration parameters of each RB to be shunted. And the main base station receives the data distribution response message.

In the above flow, the configuration parameters set by the secondary base station are described in detail as follows:

the parameters of the PDCP entity may include: the discardTimer length used by the secondary base station.

The parameters of the RLC entity may include any one or any combination of the following:

RLC mode of RB: AM or UM;

-RLC SN length used by RB;

-RLC reordering timer length used by RB receiver;

-RLC status report prohibit timer length used by RB receiver;

-RLC maximum number of retransmissions used by RB sender;

-number of Poll triggered packets used by RB sender;

-number of Poll triggered data bytes used by RB sender;

poll retransmission timer length used by the RB sender.

The parameters of the MAC entity may include any one or any combination of the following:

-the respective logical channel priorities participating in the forking;

-a logical channel group in which each logical channel participating in the splitting is located;

-maximum number of HARQ retransmissions for each RB at the secondary base station;

-the period length of a periodic Buffer Status Report (BSR) sent by the UE to the secondary base station;

-length of retransmission timer for UE to send BSR to secondary base station;

-DRX parameters used by the UE within the secondary base station cell;

-TAT timer length used by UE within secondary base station cell;

-a periodic PHR timer length used by the UE within the secondary base station cell;

-PHR prohibit timer length used by the UE in the secondary base station cell;

-a path loss change threshold for PHR transmissions used by the UE in the secondary base station cell.

The parameters of the physical layer may include any one or any combination of the following:

-time-frequency domain location of SR resources used by the UE within the secondary base station cell;

-time-frequency domain location of CQI resources used by the UE within the secondary base station cell;

-a time-frequency domain location of SRS resources used by the UE within the secondary base station cell;

note: the three parameters comprise period and offset in a time domain, and comprise frequency point information in a frequency domain;

-PRACH resource location used by the UE within the secondary base station cell;

-preamble sequences used by the UE within the secondary base station cell generate relevant parameters;

-deactivation timer length used by the UE within the secondary base station cell.

103. And the master base station sends a third message to the User Equipment (UE), wherein the third message comprises the identification of the RB to be shunted and the configuration parameters of the RB to be shunted, so that the UE establishes a second grouping data convergence protocol (PDCP) entity and a second Radio Link Control (RLC) entity for the RB to be shunted and performs data shunt configuration.

The master base station sends a third message to the UE, for example, the third message may be a data offloading configuration message, the data offloading configuration message includes an RB identity and configuration parameters of an RB to be offloaded, and after receiving the data offloading configuration message, the UE establishes a second PDCP entity and a second RLC entity for the RB to be offloaded according to content in the message, for example, the RB identity and configuration parameters of the RB to be offloaded, where the UE has a first PDCP entity, a first RLC entity and an MAC entity, and the second PDCP entity and the second RLC entity are located between the first RLC entity and the MAC entity of the UE, as shown in fig. 3. In addition, the third message may further include: and the shunting type identifier is used for indicating that the data shunting is complete shunting or partial shunting.

It should be noted that the second PDCP entity of the UE corresponds to the PDCP entity logic of the secondary base station, and the second RLC entity of the UE corresponds to the RLC entity logic of the secondary base station. The first PDCP entity of the UE corresponds to a PDCP entity of the main base station, and the first RLC entity of the UE corresponds to an RLC entity of the main base station. Here, "corresponding" is a logical relationship, and since what operation the primary base station and the secondary base station perform on data during data transmission and the UE needs to perform the corresponding inverse operation when receiving data, as shown in fig. 3, two sides are logically equivalent from the viewpoint of protocol stack structure.

Optionally, after establishing the second PDCP entity and the second RLC entity for each RB to be shunted, the UE sends a data shunting configuration response message to the main base station to notify the main base station that the establishment of the second PDCP entity and the second RLC entity is completed, as shown in fig. 4. And the main base station receives a data distribution configuration response message sent by the UE.

In the method of this embodiment, the second PDCP entity and the second RLC entity are arranged between the first RLC entity and the MAC entity of the UE, so as to change the processing flow of data to be shunted in the prior art, and the method has the advantages of small protocol modification, fast response to changes in air interface conditions measured by the bottom layer, and good dynamic shunting effect.

Further, in this embodiment, after the primary base station sends the data offloading request message to the secondary base station, the secondary base station further determines whether a cell has been established for the UE:

if the auxiliary base station establishes a cell for the UE, establishing a PDCP entity and an RLC entity for each RB in the list according to the Qos parameter and setting configuration parameters;

if the secondary base station does not establish a cell for the UE, the secondary base station establishes a cell for the UE to carry RBs, and the secondary base station establishes a Hybrid Automatic Repeat Request (HARQ) entity between the cell and the UE while establishing a PDCP entity and an RLC entity for each RB. Generally, 8 HARQ entities corresponding to one UE need to be established in each cell.

Further, the data offloading response message further includes: and a preamble (preamble) of the UE, where the preamble is allocated by a secondary base station after the secondary base station determines that the UE does not establish connection and/or synchronous connection with the secondary base station, and is used for initiating random access to a specific cell in the secondary base station by the UE to access the secondary base station after the primary base station receives a data distribution configuration response message sent by the UE. In this embodiment, the preamble may be allocated by a cell served by a secondary base station. Correspondingly, the data distribution configuration message further includes the preamble and a corresponding relationship between the preamble and the cell, so that the UE knows the preamble.

Further, the data offloading response message further includes: a BSR threshold, which is allocated by the secondary base station and used for the UE to report a BSR, and the BSR is used by the primary base station and/or the secondary base station to allocate uplink transmission resources to the UE. Correspondingly, the data offloading configuration message further includes the BSR threshold, so that the UE can know the BSR threshold.

Further, after the primary base station sends the first message to the secondary base station, the method further includes:

when the data volume of the downlink data in the buffer of the auxiliary base station is less than or equal to the buffer threshold set by the auxiliary base station, the main base station receives the data request of the auxiliary base station; or;

and the main base station sends data to the auxiliary base station according to the buffer condition of the auxiliary base station periodically reported by the auxiliary base station.

After a main base station sends a data distribution request message to an auxiliary base station, the auxiliary base station also sets a buffer threshold, and when the data quantity of downlink data in the buffer of the auxiliary base station is less than or equal to the buffer threshold, the auxiliary base station requests the data from the main base station. The buffering threshold does not need to be notified to the main base station and the UE, and therefore, the buffering threshold does not need to be carried in the data distribution response message. Or the secondary base station periodically reports the buffer condition of the secondary base station to the main base station, so that the main base station sends data to the secondary base station according to the reported buffer condition (for example, when the data amount of the buffered downlink data of the secondary base station is less than or equal to a certain threshold value).

Optionally, after the main base station receives the data offloading configuration response message sent by the UE, the method further includes:

and the main base station receives a data distribution configuration ready message from the auxiliary base station or the UE and starts data distribution transmission. After the configuration of the secondary base station is completed and the UE establishes synchronous connection with the secondary base station, it needs to notify the completion of the configuration of the control plane of the primary base station, and the structures of the nodes before and after the configuration are as shown in fig. 4. In this embodiment, the data offloading configuration ready message may be sent by the UE, or may be sent by the secondary base station, and it should be noted that, if the data offloading configuration ready message is sent by the secondary base station, the primary base station may determine that the configuration is completed; if the data stream distribution configuration is sent by the UE, the primary base station needs to wait for the secondary base station to send a data stream distribution configuration ready message after receiving the data stream distribution configuration ready message, so as to perform data stream distribution transmission.

In actual operation, the air interface condition of the secondary base station changes or other reasons may cause the data amount that the secondary base station can share to change. In this case, the primary base station may apply for adjusting the data allocation amount through the X2 port, and update the configuration parameters, where the updated configuration parameters include BSR threshold, RB configuration parameters, and the like, and the updating process includes the following steps:

the main base station receives a data distribution configuration modification request message from the auxiliary base station, wherein the data distribution configuration modification request message comprises RB configuration parameters to be modified and a BSR threshold to be modified; and

and the master base station or the auxiliary base station sends a data distribution configuration modification message to the UE, wherein the data distribution configuration modification message comprises the RB configuration parameters to be modified and the BSR threshold to be modified.

For example, the update process may be embodied as follows:

the first step is as follows: the auxiliary base station sends a data distribution configuration modification request message to the main base station, wherein the data distribution configuration modification request message comprises RB configuration parameters to be modified and a BSR threshold;

the second step is that: the auxiliary base station receives a data distribution configuration modification request response message from the main base station;

the third step: the auxiliary base station sends a data distribution configuration modification message to the UE, wherein the data distribution configuration modification message comprises RB configuration parameters to be modified and a BSR threshold;

the fourth step: and the secondary base station receives a data distribution configuration modification response message returned by the UE.

As another embodiment of the present invention, the update process may further specifically be:

the first step is as follows: the method comprises the steps that a main base station receives a data distribution configuration modification request message from a secondary base station, wherein the data distribution configuration modification request message comprises RB configuration parameters to be modified and a BSR threshold;

the second step is that: the main base station sends a data distribution configuration modification request response message to the auxiliary base station;

the third step: the main base station sends a data distribution configuration modification message to the UE, wherein the data distribution configuration modification message comprises RB configuration parameters to be modified and a BSR threshold;

the fourth step: and the main base station receives a data distribution configuration modification response message returned by the UE.

On the basis of the foregoing data offloading configuration method, this embodiment further provides a downlink (SGW-UE) data transmission method, as shown in fig. 5, where the method of this embodiment is a transmission method based on partially offloaded downlink data, and when the data offloading type of the method is partial offloading, the method includes:

201. the PDCP entity of the main base station receives the data from the SGW and processes the data to form first data.

First, the partial splitting here means that a data portion of one RB is transmitted via the secondary base station and a portion is transmitted via the primary base station.

Specifically, the processing performed by the PDCP entity of the primary base station includes data ciphering and header compression. In this embodiment, only the primary base station receives data from the SGW, and the secondary base station does not receive data from the SGW.

202. And the RLC entity of the main base station adds a first RLC sequence number to the first data to form second data, and sends the shunt data to be shunted in the second data to the PDCP entity of the auxiliary base station.

And the RLC entity of the main base station adds a first RLC sequence number to the first data and then sends the first data to the PDCP entity in the auxiliary base station. Illustratively, as shown in fig. 6, one RB packet is added with sequence number "X + 1" at the RLC entity of the main base station, and another RB packet is added with sequence number "Y + 1" at the RLC entity of the main base station, and each RLC SDU corresponds to a separate RLC sequence number.

203. And the PDCP entity of the auxiliary base station sends the shunt data to the RLC entity of the auxiliary base station.

Illustratively, after receiving the shunted data from the primary base station, the PDCP entity of the secondary base station transparently processes the shunted data, that is, does not process the shunted data, and then sends the shunted data to the RLC entity of the secondary base station. Since the basic functions of the PDCP entity are already implemented in the PDCP entity of the primary base station, such as data ciphering, header compression, etc., the PDCP entity of the secondary base station may not process the packetized data.

204. And the auxiliary base station processes the data to be distributed and sends the processed data to be distributed to the UE.

As shown in fig. 6, the secondary base station processes the data to be shunted, for example, first, the RLC entity of the secondary base station performs segmentation and concatenation on the received shunted data, then adds a second RLC sequence number to form third data, and sends the third data to the MAC layer. The "segment concatenation" of the present embodiment includes three processes: segmentation, namely segmenting and recombining the high-layer PDU packets with different lengths into smaller RLC load units (PUs); cascading, when the content of one RLC SDU cannot fill up one complete RLC PDU, the first segment of the next RLC SDU can also be placed in the PU and concatenated with the last segment of the previous RLC SDU; padding, when the contents of an RLC SDU cannot fill up a complete RLC PDU and concatenation cannot be performed, the remaining space can be filled up with padding bits.

The RLC entity of the secondary base station performs segmentation and concatenation on the data packet, and adds a second RLC sequence number to form third data, i.e., an RLC PDU, in the figure, the two RLC entities respectively add sequence numbers "K + 1" and "P + 1" to the data packet generated by the two RLC entities, and then send the data packet to the MAC entity.

Specifically, the MAC entity of the secondary base station processes the third data and then sends the processed third data to the physical layer, so that the physical layer (Phy) sends the processed third data to the user terminal. Here, "processing" may specifically be multiplexing, that is, combining together the third data corresponding to one or more RBs. If only the third data from one RB is received in a TTI, multiplexing is not needed.

And multiplexing the data packets from the plurality of RBs by the MAC entity of the secondary base station to form MAC PDU, and finally transmitting the MAC PDU to a physical layer for transmission. For example, as shown in fig. 6, the MAC entity puts data packets with sequence numbers "K + 1" and "P + 1" in the same MAC PDU, and adds a "MAC Header", finally forming a MAC PDU. And finally, the physical layer sends the processed third data to the UE.

In the method for transmitting downlink data according to this embodiment, when the data offloading type is partial offloading, a part of the offloaded data is transmitted to the PDCP entity of the secondary base station to be sent to the UE through the secondary base station, and when an air interface condition of the secondary base station changes, the MAC entity of the secondary base station can timely reflect a situation to the primary base station, so that dynamic offloading is achieved, and a protocol is less modified and is easy to implement.

Optionally, after the RLC entity of the main base station adds the first RLC sequence number to the first data, the method further includes:

and the secondary base station prestores the second data to be distributed in a cache of an RLC entity of the secondary base station.

In this embodiment, the secondary base station may store the second data in a buffer of an RLC entity of the secondary base station in advance, and when the amount of data in the buffer is less than or equal to a certain threshold, transmit some data again. When the scheduler of the secondary base station decides to transmit data, the data packet can be directly taken out from the buffer of the secondary base station, so that the processing speed can be increased.

Further, the RLC entity of the master base station adds a first RLC sequence number to the first data, specifically:

and the RLC entity of the main base station carries out segmentation cascade processing on the first data and adds a first RLC sequence number to the first data after segmentation cascade processing.

In this embodiment, as shown in fig. 7, the RLC entity of the main base station performs a concatenation process on the first data, that is, several data packets from the PDCP entity are combined into one data packet, so as to form a larger data packet, but the maximum size of the data packet cannot exceed the maximum size 8188Bytes required by the protocol. Illustratively, in fig. 7, two RLC SDUs are concatenated into one RLC PDU and delivered to the PDCP entity of the secondary base station. The method has the advantages that a plurality of data packets from the SGW share one sequence number in the main base station RLC entity, so that fewer RLC sequence numbers are occupied, and when the data volume is large and the air interface condition is good, the data delay caused by limited RLC window pushing is reduced.

It should be noted that, the two technical features mentioned above, "the primary base station stores the first data to be shunted in the buffer of the RLC entity of the secondary base station in advance" and "the RLC entity of the primary base station cascades the first data", may be implemented by freely combining, and there are four embodiments after combining, as shown in table 1:

TABLE 1

And after the physical layer of the auxiliary base station sends out the processed data to be shunted, the physical layer of the UE receives fourth data from the auxiliary base station, and the fourth data is processed by the MAC entity, the second RLC entity, the second PDCP entity, the first RLC entity and the first PDCP entity of the UE in sequence to form fifth data. The processing of the data packet by the UE and the processing of the data packet by the primary base station and the secondary base station are inverse processes, that is:

the physical layer of the UE receives fourth data from the secondary base station;

the MAC entity of the UE divides each data packet of the fourth data into a plurality of RLC PDUs;

the second RLC entity of the UE restores each RLC PDU into a data packet before segmentation and concatenation, removes a second RLC sequence number and sends the second RLC sequence number to the second PDCP entity of the UE;

the second PDCP entity of the UE sends the restored data packet to the first RLC entity of the UE;

a first RLC entity of the UE removes a first RLC sequence number of a data packet, restores the cascaded packets into a plurality of packets and then sends the packets to a first PDCP entity of the UE;

and the first PDCP entity of the UE restores the first processing to obtain fifth data, and finally obtains the data sent by the SGW.

The specific processing of the data packet by the UE may be similar to the transmission method of the downlink data, and is not described herein again.

In the base station system of this embodiment, after being processed by the RLC entity of the main base station, part of the shunted data enters the PDCP entity of the auxiliary base station, and corresponds to the PDCP entity and the RLC entity of the auxiliary base station.

As shown in fig. 8, the method of this embodiment is a data transmission method based on complete split, and includes:

301. the PDCP entity of the main base station receives data from the SGW and processes the data to form first data;

first, it should be noted that the complete offloading here means that all data of one RB is transmitted via the secondary base station.

302. And the RLC entity of the main base station receives the first data and sends the first data to the PDCP entity of the auxiliary base station.

In this embodiment, the RLC entity of the main base station performs transparent processing on the first data, that is, does not perform any processing.

303. And the PDCP entity of the auxiliary base station receives the first data from the main base station and sends the first data to the RLC entity of the auxiliary base station.

After receiving the first data from the main base station, the PDCP entity of the secondary base station transparently processes the first data, i.e., does not perform any processing, and then sends the first data to the RLC entity of the secondary base station. Since the basic functions of the PDCP entity are already implemented in the PDCP entity of the primary base station, such as data ciphering, header compression, etc., the PDCP entity of the secondary base station may not perform any processing on the packetized data.

304. And the auxiliary base station processes the first data and sends the processed first data to the UE.

Optionally, the processing, by the secondary base station, the first data specifically includes the following contents: and the RLC entity of the auxiliary base station carries out segmentation cascade on the received first data, then adds a second RLC sequence number to form third data, and sends the third data to the MAC entity. And after the MAC entity of the auxiliary base station processes the third data, fourth data is formed and is sent to the physical layer, so that the physical layer sends the fourth data to the UE.

Here, "processing" may specifically be multiplexing, that is, combining together the third data corresponding to one or more RBs. If only the third data from one RB is received in a Transmission Time Interval (TTI), multiplexing is not required.

Since the completely shunted data does not need to be transmitted through the main base station, in this embodiment, the RLC entity of the main base station does not need to allocate an RLC sequence number to the data packet, which simplifies the processing flow, reduces signaling overhead, and speeds up data transmission. In addition, the working principle of the main base station and the secondary base station of the downlink data transmission method of this embodiment is the same as that of the above embodiment, and is not described herein again.

Further, the physical layer of the UE receives fourth data from the secondary base station, and the fourth data is processed by the MAC entity, the second RLC entity, the second PDCP entity, the first RLC entity, and the first PDCP entity of the UE in sequence to form fifth data. The processing of the data packet by the UE and the processing of the data packet by the primary base station and the secondary base station are inverse processes, and are not described herein again.

In this embodiment, since the completely shunted data does not need to be transmitted through the main base station, the RLC entity of the main base station does not need to allocate an RLC sequence number to the data packet, which simplifies the processing procedure, reduces signaling overhead, and speeds up data transmission. In addition, corresponding to the PDCP entity and the RLC entity of the secondary base station, in this embodiment, the second PDCP entity and the second RLC entity are set between the first RLC entity and the MAC entity of the UE, so that the processing flow of data to be shunted in the prior art is changed, the response to the change of the air interface condition measured at the bottom layer is fast, and the dynamic shunting effect is good.

As shown in fig. 9, the method of this embodiment is a method for transmitting uplink data, and includes:

401. and the UE reports the BSR to the main base station and/or the auxiliary base station so that the main base station and/or the auxiliary base station distributes uplink transmission resources for the UE.

When the UE reports the BSR, for the RB which does not participate in shunting, the UE only reports the BSR to the main base station; for the RBs participating in the offloading, if configured as partial offloading, the UE preferentially sends a BSR to the secondary base station.

Further, when the data offloading type of the method is partial offloading, the UE reports a BSR to the primary base station and/or the secondary base station, specifically:

reporting a BSR to the secondary base station after judging that the total amount of the data to be transmitted is less than or equal to a pre-configured BSR threshold; and after judging that the total amount of the data to be distributed is greater than a pre-configured BSR threshold, reporting a BSR to the auxiliary base station, and reporting a difference value between the total amount of the data to be distributed and the BSR threshold to the main base station.

That is, if the total amount of data to be shunted in the RBs participating in shunting is less than or equal to the pre-configured BSR threshold, only reporting the BSR to the secondary base station, if the total amount of data to be shunted is greater than the BSR threshold, reporting data below the BSR threshold to the secondary base station, reporting other data to the primary base station, that is, reporting the BSR to the secondary base station, and reporting the difference between the total amount of data to be shunted and the BSR threshold to the primary base station. And if the configuration is full shunting, only reporting the BSR to the main base station.

For example, as shown in fig. 10, the BSR threshold is 600Bytes, and when the UE needs to report 800Bytes, 200Bytes are reported to the primary base station, and 600Bytes are reported to the secondary base station. After receiving the BSR, the main base station and the auxiliary base station respectively distribute uplink transmission resources for the UE, and mutual negotiation between the two base stations is not needed.

402. And the first PDCP entity of the UE carries out first processing on the data to form first data.

Specifically, the processing performed by the first PDCP entity includes data ciphering and header compression. After the UE receives the uplink resource, if the uplink resource is allocated by the main base station, the MAC entity directly asks for data from the first RLC entity; if the uplink resource is allocated by the secondary base station, the MAC entity asks for data from the second RLC entity, and the second RLC entity asks for data from the first RLC entity.

403. And the first RLC entity of the UE carries out segmentation cascade connection on the first data, adds a first RLC sequence number to form second data, and sends shunted data to be shunted in the second data to a second PDCP entity according to the received uplink transmission resources distributed by the secondary base station.

In this embodiment, the first RLC entity of the UE performs segmentation and concatenation on the first data, and then adds the first RLC sequence number and sends the first data to the second PDCP entity. For example, as shown in fig. 10 and fig. 11, as an embodiment of the present invention, before the UE receives the uplink resource, its data is stored in the buffer of the primary RLC. Illustratively, the MAC entity receives the uplink resource allocated by the secondary base station, and decides to let one RB transmit 150 bytes and the other RB transmit 180 bytes through the decision of the scheduler. After the distribution information is transmitted to the first RLC entity through the second RLC entity, the first RLC entities of the two RBs respectively carry out segmentation and cascade on the data packets buffered by the first RLC entities, and the first RLC sequence numbers are added to form two RLC PDUs. One of the sizes is 150 bytes, the first RLC sequence number is "X + 1", the other size is 180 bytes, and the first RLC sequence number is "Y + 1".

404. And the second PDCP entity of the UE sends the shunt data to the second RLC entity of the UE.

After receiving the shunted data, the second PDCP entity transparently processes the shunted data, i.e., does not perform any processing, and then sends the shunted data to the second RLC entity. Since the basic functions of the PDCP entity are already implemented in the first PDCP entity, such as data ciphering, header compression, etc., the second PDCP entity may not perform any processing on the packetized data.

405. And the second RLC entity of the UE adds a second RLC sequence number to the received distributed data to form third data.

Specifically, the RLC PDU reaches the auxiliary RLC layer after being transparently transferred from the PDCP layer. The two second RLC entities add their second RLC sequence numbers to the two packets, respectively, to form an RLC PDU, for example, in fig. 10, the two second RLC entities add the second RLC sequence numbers "K + 1" and "P + 1" to the data packets generated by themselves, respectively, and then send the data packets to the MAC entity of the UE.

406. And the UE sends the processed third data to the auxiliary base station.

Specifically, after the MAC entity of the UE processes the third data, fourth data is formed, and the fourth data is sent to the physical layer, so that the physical layer sends the processed third data to the primary base station and/or the secondary base station. For example, as shown in fig. 10, the MAC entity puts data packets with sequence numbers "K + 1" and "P + 1" in the same MAC PDU, and adds a "MAC Header", finally forming a MAC PDU. Finally, the physical layer transmits the fourth data to the primary base station and/or the secondary base station.

Further, after the first RLC entity adds the first RLC sequence number to the first data, the method further includes:

and the UE prestores the first data to be distributed in a buffer of a second RLC entity.

Further, the first RLC entity adds a first RLC sequence number to the first data, specifically:

and the first RLC entity cascades the first data and adds a first RLC sequence number to the cascaded first data.

In this embodiment, the first RLC entity performs concatenation processing on the first data, but does not perform segmentation, that is, combines a plurality of data packets from the first PDCP entity into one data packet, so as to form a larger data packet, but the maximum size of the data packet cannot exceed the maximum size of 8188Bytes required by the protocol. The method has the advantages that a plurality of data packets share one sequence number in the first RLC entity, so that fewer RLC sequence numbers are occupied, and when the data volume is larger and the air interface condition is better, the data delay caused by limited RLC window pushing is reduced.

It should be noted that, the two technical features "the UE stores the first data to be shunted in the buffer of the second RLC entity in advance" and "the first RLC entity of the UE concatenates the first data" may be implemented by freely combining, and there are four implementation manners after combining, as shown in table 2:

TABLE 2

And after the physical layer of the UE sends out the fourth data, the physical layer of the auxiliary base station receives the fourth data from the UE, and the fourth data is processed by the MAC entity, the RLC entity and the PDCP entity of the auxiliary base station and the RLC entity and the PDCP entity of the main base station in sequence to form fifth data.

The processing of the data packet by the primary base station and the secondary base station and the processing of the data packet by the UE are inverse processes, and are not described herein again.

According to the embodiment of the invention, the second PDCP entity and the second RLC entity are arranged between the first RLC entity and the MAC entity, the second PDCP entity is logically corresponding to the PDCP entity of the auxiliary base station, and the second RLC entity is logically corresponding to the RLC entity of the auxiliary base station, so that the processing flow of data to be shunted in the prior art is changed, the response to the change of the air interface condition measured at the bottom layer is quicker, and the dynamic shunting effect is better.

The present embodiment further provides an uplink data transmission method, as shown in fig. 12, including:

501. and the UE reports the BSR to the main base station and/or the auxiliary base station so that the main base station and/or the auxiliary base station distributes uplink transmission resources for the UE.

502. A first PDCP entity of the UE receives data from an application layer and processes the data to form first data.

503. And a first RLC entity of the UE adds a first RLC sequence number to the first data to form second data, and sends shunted data to be shunted in the second data to a second PDCP entity.

504. And the second PDCP entity of the UE receives the shunted data and sends the shunted data to the second RLC entity of the UE.

505. And the second RLC entity of the UE sectionally concatenates the received shunted data according to the received uplink transmission resource distributed by the auxiliary base station, and then adds a second RLC sequence number to form third data.

Specifically, the second RLC entity of the UE sends the third data to the MAC entity of the UE.

506. And the UE sends the processed third data to the auxiliary base station.

Specifically, after the MAC entity of the UE processes the third data, fourth data is formed, and the fourth data is sent to the physical layer, so that the physical layer sends the fourth data to the secondary base station.

Different from the first uplink data transmission method, in this embodiment, before receiving the uplink transmission resource allocated by the secondary base station, the data enters the second PDCP entity, so that the first RLC entity of the UE only performs sequence numbering on the data packet, but does not perform segmentation concatenation on the data packet, and the second RLC entity is required to perform segmentation concatenation on the data packet. In addition, other steps of the present embodiment are the same as the first uplink data transmission method, and are not described herein again.

Further, after the physical layer of the UE sends out the fourth data, the physical layer of the secondary base station receives the fourth data from the UE, and the fourth data is processed by the MAC entity, the RLC entity, and the PDCP entity of the secondary base station, and the RLC entity and the PDCP entity of the primary base station in sequence to form fifth data. The processing of the data packet by the primary base station and the secondary base station and the processing of the data packet by the UE are inverse processes, which is not described herein again.

After the first RLC entity of the UE adds the first RLC sequence number to the first data, the method further includes:

When the data distribution type of the method is partial distribution, the UE reports a BSR to the primary base station and/or the secondary base station, specifically:

after judging that the total amount of the data to be transmitted is less than or equal to a pre-configured BSR threshold, only reporting the BSR to the secondary base station;

and after judging that the total amount of the data to be distributed is greater than a pre-configured BSR threshold, reporting the BSR to the auxiliary base station, and reporting the difference value between the total amount of the data to be distributed and the BSR threshold to the main base station.

When the data distribution type of the method is partial distribution, the UE only reports the BSR to the main base station.

Corresponding to the above embodiment of the data offloading configuration method, this embodiment further provides a base station, as shown in fig. 13, including a transmitter 131 and a receiver 132, where:

a transmitter 131 for:

a receiver 132, configured to receive a second message from the secondary base station, where the second message includes a configuration parameter of the RB to be shunted;

Further, the second message further includes: a Buffer Status Report (BSR) threshold, where the BSR threshold is allocated by the secondary base station and used for the UE to report a BSR, and the BSR is used for enabling the primary base station and/or the secondary base station to allocate uplink transmission resources for the UE.

Further, the receiver 132 is further configured to receive a data request of the auxiliary base station when the data amount of the downlink data in the buffer of the auxiliary base station is less than or equal to the buffer threshold set by the auxiliary base station;

the transmitter 131 is further configured to transmit data to the secondary base station according to the buffer condition of the secondary base station periodically reported by the secondary base station.

Further, the first message further includes: a shunting type identifier for indicating the data shunting to be complete shunting or partial shunting, wherein:

the partial splitting means that data of one RB is partially transmitted via the secondary base station and partially transmitted via the primary base station, and the full splitting means that all data of one RB is transmitted via the secondary base station.

This embodiment further provides a base station system, as shown in fig. 14, including a main base station 2 and a secondary base station 3, where the main base station includes a PDCP entity 21 and an RLC entity 22, and the secondary base station includes a PDCP entity 31 and an RLC entity 32; wherein:

the PDCP entity 21 of the primary base station 2 is configured to receive data from a serving gateway SGW, process the data, and form first data, where a transmission method of the data is partial offloading;

the RLC entity 22 of the master base station 2 is configured to add a first RLC sequence number to the first data to form second data, and send data to be shunted in the second data to the PDCP entity of the secondary base station;

the PDCP entity 31 of the secondary base station 3 is configured to send the data to be shunted to the RLC entity 32 of the secondary base station 3;

and the auxiliary base station 3 is configured to process the data to be distributed, and send the processed data to be distributed to the UE.

Further, the RLC entity 22 of the master base station 2 is further configured to perform segmentation and concatenation processing on the first data, and add a first RLC sequence number to the first data after segmentation and concatenation.

The primary base station in the base station system of this embodiment can perform the actions of the primary base station in the above-mentioned method embodiment, and the secondary base station in the base station system can perform the actions of the secondary base station in the above-mentioned method embodiment.

The present embodiment also provides a base station system, as shown in fig. 14, including a main base station 2 and a secondary base station 3, where the main base station includes a PDCP entity 21 and an RLC entity 22, and the secondary base station includes a PDCP entity 31 and an RLC entity 32.

The PDCP entity 21 of the primary base station 2 is configured to receive data from a serving gateway SGW, and process the data to form first data, where a transmission method of the data is complete offloading;

the RLC entity 22 of the master base station 2 is configured to receive the first data and send the first data to the PDCP entity 31 of the secondary base station 3;

the PDCP entity 31 of the secondary base station 3 is configured to receive the first data from the primary base station 2, and send the first data to the RLC entity 32 of the secondary base station 3;

and the auxiliary base station 3 processes the first data and sends the processed first data to the UE.

The present embodiment further provides a user equipment, as shown in fig. 15, including a first PDCP entity 41, a first RLC entity 42, a MAC entity 43, and a physical layer 44, and further including: a BSR reporting unit 40, a second PDCP entity 45, and a second RLC entity 46, where the second PDCP entity 45 and the second RLC entity 46 are located between the first RLC entity 42 and the MAC43 of the UE, where:

a BSR reporting unit 40, configured to report a BSR to a primary base station and/or a secondary base station, so that the primary base station and/or the secondary base station allocate uplink transmission resources for the UE;

a first PDCP entity 41, configured to perform a first process on the data to form first data;

the first RLC entity 42 is configured to perform segmentation and concatenation on the first data, add a first RLC sequence number to form second data, and send shunted data to be shunted in the second data to the second PDCP entity 45 according to the received uplink transmission resource allocated by the secondary base station;

a second PDCP entity, configured to send the shunted data to a second RLC entity 46 of the UE;

a second RLC entity 46, configured to add a second RLC sequence number to the received shunted data to form third data, and send the third data to the MAC entity 43 of the UE;

and the physical layer 44 of the UE is configured to send the processed third data to the secondary base station.

Further, when the data offloading method is partial offloading, the BSR reporting unit is specifically configured to:

reporting a BSR to the secondary base station after judging that the total amount of the data to be transmitted is less than or equal to a pre-configured BSR threshold; or

And after judging that the total amount of the data to be distributed is greater than a pre-configured BSR threshold, reporting a BSR to the auxiliary base station, and reporting a difference value between the total amount of the data to be distributed and the BSR threshold to the main base station.

The UE in the base station system of this embodiment may perform the actions of the UE in the above method embodiments.

According to the user terminal provided by the embodiment of the invention, the second PDCP entity and the second RLC entity are arranged between the first RLC entity and the MAC entity, the second PDCP entity is logically corresponding to the PDCP entity of the auxiliary base station, and the second RLC entity is logically corresponding to the RLC entity of the auxiliary base station, so that the processing flow of data to be shunted in the prior art is changed, the response to the change of the air interface condition measured at the bottom layer is quicker, and the dynamic shunting effect is better.

The present embodiment further provides a user equipment, as shown in fig. 15, including a first PDCP entity 41, a first RLC entity 42, a MAC entity 43, and a physical layer 44, and further including: a BSR reporting unit 40, a second PDCP entity 45 and a second RLC entity 46, wherein the second PDCP entity 45 and the second RLC entity 46 are located between the first RLC entity 42 and the MAC43 of the UE.

a first RLC entity 42, configured to add a first RLC sequence number to the first data to form second data, and send shunted data to be shunted in the second data to a second PDCP entity 45 of the UE;

a second PDCP entity 45, configured to send the shunted data to a second RLC entity 46 of the UE;

a second RLC entity 46, configured to add a second RLC sequence number after the received shunted data is segmented and concatenated according to the received uplink transmission resource allocated by the secondary base station, to form third data, and send the third data to the MAC entity 43;

the physical layer 44 is configured to send the processed third data to the secondary base station.

reporting a BSR to the secondary base station after judging that the total amount of the data to be transmitted is less than or equal to a pre-configured BSR threshold;

after the total amount of the data to be distributed is judged to be larger than a pre-configured BSR threshold, reporting a BSR to the auxiliary base station, and reporting a difference value between the total amount of the data to be distributed and the BSR threshold to the main base station.

The working principle and working process of each entity unit in this embodiment are the same as those of the above method embodiments, and are not described herein again.

Through the above description of the embodiments, it is clear to those skilled in the art that, for convenience and simplicity of description, the foregoing division of the functional modules is merely used as an example, and in practical applications, the above function distribution may be completed by different functional modules according to needs, that is, the internal structure of the device may be divided into different functional modules to complete all or part of the above described functions. For the specific working processes of the system, the apparatus and the unit described above, reference may be made to the corresponding processes in the foregoing method embodiments, and details are not described here again.

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

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

In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.

The integrated unit, if implemented in the form of a software functional unit and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application may be substantially implemented or contributed to by the prior art, or all or part of the technical solution may be embodied in a software product, which is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, a server, or a network device) or a processor to execute all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: flash memory, removable hard drive, read only memory, random access memory, magnetic or optical disk, and the like.

The above description is only an embodiment of the present application, but the scope of the present application is not limited thereto, and any changes or substitutions within the technical scope of the present disclosure should be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

1. A data distribution configuration method is characterized by comprising the following steps:

a main base station sends a first message to a secondary base station, wherein the first message is used for requesting the secondary base station to carry out data distribution, and the first message comprises an identifier of a Radio Bearer (RB) and a quality of service (Qos) parameter of the RB;

the main base station receives a second message from the auxiliary base station, wherein the second message comprises configuration parameters of the RB to be shunted;

the master base station sends a third message to the User Equipment (UE), wherein the third message comprises the identifier of the RB to be shunted and the configuration parameters of the RB to be shunted;

the first message and/or the third message are/is further used for indicating that the data offloading is complete offloading or partial offloading;

wherein the data partially split into one RB is partially transmitted through the secondary base station, partially transmitted through the main base station, and completely transmitted through the secondary base station.

2. The data offloading configuration method of claim 1, wherein the second message further comprises:

and the preamble of the UE is coded.

3. The data offloading configuration method according to claim 1 or 2, wherein the third message further includes:

and the preamble of the UE is coded.

4. The data offloading configuration method according to claim 1 or 2, wherein after the primary base station sends the first message to the secondary base station, the method further includes:

and when the data volume of the downlink data in the buffer of the auxiliary base station is less than or equal to the buffer threshold set by the auxiliary base station, the main base station receives the data request of the auxiliary base station.

5. The data offloading configuration method according to claim 1 or 2, further comprising:

and the main base station receives a data distribution configuration ready message sent by the auxiliary base station or the UE and starts data distribution transmission.

6. The data distribution configuration method according to claim 1 or 2, characterized in that:

the QoS parameters of the RB to be shunted comprise at least one of the following parameters:

the priority of the RB, whether the RB can be preempted, the uplink maximum bit rate, the uplink guaranteed bit rate, the downlink maximum bit rate, the downlink guaranteed bit rate and the maximum allowable time delay.

7. The data distribution configuration method according to claim 1 or 2, characterized in that:

the master base station is a service base station of the UE;

and the auxiliary base station is a base station which participates in the carrier aggregation of the UE and performs data distribution.

8. A data distribution configuration method is characterized by comprising the following steps:

user Equipment (UE) receives a third message sent by a main base station, wherein the third message comprises an identification of an RB to be shunted and configuration parameters of the RB to be shunted;

the third message is sent after the main base station sends the first message to the auxiliary base station and receives the second message from the auxiliary base station;

the first message is used for requesting the secondary base station to perform data offloading, the first message includes an identifier of a Radio Bearer (RB) and a quality of service (Qos) requirement parameter of the RB, and the second message includes a configuration parameter of the RB to be offloaded.

9. The data offloading configuration method according to claim 8, wherein the first message and/or the third message are further used to indicate that the data offloading is a full offloading or a partial offloading;

10. The data offloading configuration method of claim 8, wherein the second message further comprises:

and the preamble of the UE is coded.

11. The data offloading configuration method according to claim 8 or 10, wherein the third message further includes:

and the preamble of the UE is coded.

12. The data offloading configuration method according to claim 8 or 10, further comprising:

and the UE sends a data distribution configuration ready message to the main base station to indicate the main base station to start data distribution transmission.

13. The data offloading configuration method according to claim 8 or 10, wherein:

14. The data offloading configuration method according to claim 8 or 10, wherein:

the master base station is a service base station of the UE;

15. A base station, comprising:

a transmitter for:

sending a first message to a secondary base station, wherein the first message is used for requesting the secondary base station to perform data distribution, and the first message comprises an identifier of a Radio Bearer (RB) and a quality of service (Qos) requirement parameter of the RB; and

sending a third message to the User Equipment (UE), wherein the third message comprises an identification of the RB to be shunted and configuration parameters of the RB to be shunted;

the partial splitting refers to that the data of one RB is partially transmitted through the secondary base station, and is partially transmitted through the base station, and the full splitting refers to that the data of one RB is completely transmitted through the secondary base station.

16. The base station of claim 15, wherein the second message further comprises:

and the preamble of the UE is coded.

17. The base station of claim 15 or 16, wherein the third message further comprises:

and the preamble of the UE is coded.

18. The base station according to claim 15 or 16,

the receiver is further configured to receive a data request of the auxiliary base station when the data amount of the downlink data in the buffer of the auxiliary base station is less than or equal to the buffer threshold set by the auxiliary base station.

19. The base station according to claim 15 or 16, characterized by:

the receiver is further configured to receive a data offloading configuration ready message sent by the secondary base station or the UE, and start data offloading transmission.

20. The base station according to claim 15 or 16, characterized by:

21. The base station according to claim 15 or 16, characterized by:

the base station is a service base station of the UE;

22. A UE for data offloading configuration, comprising:

a receiving unit, configured to receive a third message sent by a master base station, where the third message includes an identifier of an RB to be shunted and a configuration parameter of the RB to be shunted;

23. The UE of claim 22, wherein the first message and/or the third message are further configured to indicate that the data offloading is a full offloading or a partial offloading;

24. The UE of claim 22, wherein the second message further comprises:

and the preamble of the UE is coded.

25. The UE of claim 22 or 24, wherein the third message further comprises:

and the preamble of the UE is coded.

26. The UE of claim 22 or 24, further comprising:

27. The UE of claim 22 or 24, wherein:

28. The UE of claim 22 or 24, wherein:

the master base station is a service base station of the UE;