CN106686751B

CN106686751B - Configuration method and device of radio bearer

Info

Publication number: CN106686751B
Application number: CN201510760425.7A
Authority: CN
Inventors: 杨立
Original assignee: ZTE Corp
Current assignee: ZTE Corp
Priority date: 2015-11-10
Filing date: 2015-11-10
Publication date: 2021-08-17
Anticipated expiration: 2035-11-10
Also published as: WO2016197989A1; CN106686751A

Abstract

The invention discloses a method and a device for configuring a radio bearer, wherein the method comprises the following steps: the network side configures a DRB type constraint rule; and the network side determines the type of the DRB required to be configured by the UE according to the constraint rule and a preset strategy. The configuration method and the configuration device of the radio bearer can reduce the complexity and the burden of processing the data packet on the radio link, thereby reducing the complexity and the burden of processing a system.

Description

Configuration method and device of radio bearer

Technical Field

The present invention relates to the field of mobile communications, and in particular, to a method and an apparatus for configuring a radio bearer.

Background

In a Long Term Evolution (LTE) or Long Term Evolution upgrade (LTE-a) system of the third Generation Partnership Project (3GPP, 3rd Generation Partnership Project) standard specification, a very important Dual Connectivity (DC) function is introduced in the R12(Release 12) version, so that a single terminal (UE) can simultaneously perform wireless connection and uplink and downlink User traffic data transmission and reception with two LTE serving base stations (a Master evolved Node B and a Secondary base station (SeNB)). As shown in fig. 1, the UE in the LTE DC operating mode can perform duplex communication of uplink and downlink service Data with the MeNB and the SeNB through Uu-U air interface user plane bearers (Data Radio bearers (DRBs), each DRB corresponds to and carries one user service Data stream). The MeNB is a UE Radio Resource Control (RRC) anchor Control element, and is responsible for mobility of the UE/functions such as Radio Resource configuration Control and management over an air interface through a Uu-C air interface Control plane Bearer (SRB). The SeNB must be attached under the MeNB through the X2-U ground interface user plane and the X2-C ground interface control plane to provide additional traffic data offloading and bearers for the UE, thereby enhancing the overall data transmission rate of the UE. The MeNB may be connected to a control plane network element Mobility Management Entity (MME) and a user plane network element Serving Gateway (SGW) of the LTE core network, and respectively correspond to S1-MME and S1-u (MeNB) ground interfaces, while the SeNB may only be connected to the user plane network element SGW and correspond to S1-u (SeNB) ground interfaces. The interaction of the UE and the non-access layer control signaling of the LTE core network can be realized only by the MeNB, and the interaction of the UE and the access layer control signaling of the LTE access network can also be realized only by the MeNB; the service data interaction between the UE and the LTE core network and the access network may be implemented by a Master Cell Group (MCG) Bearer configured by the MeNB, or may be implemented by an MCG Bearer configured by the SeNB; when the SeNB interacts with the MME or the UE for control signaling, it must be implemented by relay negotiation forwarding of the MeNB.

The LTE DC operating mode may provide three basic DRB types, as shown in fig. 2, where the bold line in (a) of fig. 2 represents MCG Bearer, and uplink and downlink transmission of user service data is implemented through MCG Link (Link); the bold line in (b) of fig. 2 represents a Split (Split) Bearer, and uplink and downlink transmission of user service data is simultaneously achieved through an MCG Link and a Secondary Cell Group (SCG) Link; the bold line in (c) of fig. 2 represents SCG Bearer, and uplink and downlink data transmission of user service data is realized through SCG Link.

In the LTE/LTE-a system specified in the 3GPP standard, a very important long term evolution and Wireless Local area Network Aggregation (LWA) function is introduced in the R13(Release 13) version, that is, Aggregation of radio resources is performed in a radio Access layer between the LTE system and a Wireless Local Access Network (WLAN) system. The MeNB is directly connected to a wireless local area network node (WT) through an internal interface or an Xw interface, and shunts a Packet Data Convergence Protocol (PDCP) Packet corresponding to one or more DRBs to a WLAN transmission node (e.g., Access Control (AC)/Access node (AP, Access Point)) in the WT, so that the WLAN AP node transmits Data through the WLAN Link and the UE. As shown in fig. 3, because LWA adopts a DC-like working architecture, WT is similar to SeNB in the architecture of fig. 1 in terms of logical role and status, but UE and MeNB/SeNB in DC dual connectivity in fig. 1 have one LTE Link respectively, while UE and MeNB/WT in LWA in fig. 3 have one LTE Link and one WLAN Link respectively. Common to the DC and LWA modes of operation are: and the network side and the control plane radio bearer (SRB) of the UE can only go through an MeNB Uu-C interface.

The LWA working mode may provide two basic DRB types (which may be collectively referred to as LWA Bearer), as shown in fig. 4, where a bold line in (a) of fig. 4 represents LWA Split Bearer, and uplink and downlink transmission of user service data is simultaneously achieved through an LTE Link at the MeNB side and a WLAN Link air interface resource at the WT side; the bold line in (b) of fig. 4 represents LWA handover (Switched) Bearer, and uplink and downlink transmission of user service data is realized only through forwarding of MeNB at Xw-U and WLAN Link air interface resources at WT side; fig. 4 (b) is a special case of fig. 4 (a), that is, the MeNB or the UE shunts all PDCP packets belonging to a DRB to the WT side according to a 0: 100% shunt ratio, and fig. 4 (a) reorders and integrates downlink PDCP data flows from the LTE Link and the WLAN Link when the UE is required to be the downlink receiving side; fig. 4 (a) also requires that when the MeNB is used as the uplink receiving side, the uplink PDCP data flows from the LTE Link and the WLAN Link are reordered and integrated; fig. 4 (b) only involves one WLAN Link data stream, so the processing on both the MeNB and UE sides is relatively simple.

In release R13, the joint coexistence configuration of LTE DC dual connectivity operation and LWA operation for the UE is not supportable due to the large system processing complexity. This may cause that when the UE is in the DC working mode at a certain time, if the UE enters the effective WLAN coverage area, the LTE network side wants to perform LWA operation, and must first go through multiple RRC control signaling to let the UE exit the DC configuration, and then go through multiple RRC control signaling to let the UE enter the LWA configuration, or vice versa. Along with the above-mentioned conversion between the DC and LWA working modes, not only a large amount of air interface signaling resources are consumed for reconfiguration, but also the DRBs data transmission on the user plane of the UE is interrupted for a while, thus, the data service experience (such as data rate peak) of the user is reduced, and performance degradation such as service fluency is caused. Therefore, in versions following R13, mobile operators require that the system be able to support joint coexistence configuration and operation of DC dual connectivity operation and LWA operation.

Disclosure of Invention

In order to solve the above technical problems, the present invention provides a method and an apparatus for configuring a radio bearer, which can reduce the complexity and burden of packet processing on a radio link, and further reduce the complexity and burden of system processing.

In order to achieve the above technical object, the present invention provides a method for configuring a radio bearer, including: a network side configures a constraint rule of a Data Radio Bearer (DRB) type; and the network side determines the type of the DRB required to be configured by the terminal UE according to the constraint rule and a preset strategy.

Further, the network side determines the type of the DRB that the UE needs to configure according to the constraint rule and a preset policy, including: and the network side selects a DRB type meeting the constraint rule from DRB types determined according to a Radio Resource Management (RRM) measurement result of the UE, a corresponding input parameter and an RRM algorithm, and determines the DRB type to be configured by the UE.

Further, the constraint rule includes:

constraint terms for different DRB types;

any newly created or reconfigured DRB type and all configured DRB types satisfy the constraint terms.

Further, the constraint rule further includes: and when the newly built or reconfigured DRB type can not meet the constraint terms, performing type reconfiguration on all the configured DRBs until any newly built or reconfigured DRB type and all the configured DRB types meet the constraint terms.

Further, the constraint term includes at least one of:

the complexity of processing a Packet Data Convergence Protocol (PDCP) data packet to which the DRB belongs by the base station and/or the UE is prevented from exceeding the constraint clause of the system processing capacity;

avoiding the processing burden of the base station and/or the UE from exceeding the constraint terms of the system cost;

avoiding the coexistence of multiple DRBs of different types results in a lower air interface radio resource efficiency than expected by the network operator and/or the user communication experience.

Further, the constraint term includes: the following two DRB types are constrained to be configured to coexist within the same base station and/or UE: split (Split) Bearer (Bearer), Long Term Evolution (LTE), and wireless local area network aggregation (LWA) Bearer in a Long Term Evolution (LTE) dual connectivity configuration.

Further, the constraint term includes at least one of:

when the following DRB types have been configured: a primary cell set (MCG) Bearer, and when not offloading to a wireless local area network node (WT) or a secondary base station (SeNB), a DRB type that can coexist with the DRB type is unconstrained;

when the following DRB types have been configured: the MCG side LWA Bearer, and only shunting to WT, constrains the DRB type from coexisting with the following DRB types: split Bearer, secondary cell Set (SCG) side LWA Bearer;

when the following DRB types have been configured: SCG Bearer, and without offloading to WT or primary base station (MeNB), restricts the DRB type from coexisting with the following DRB types: split Bearer;

when the following DRB types have been configured: the SCG side LWA Bearer, and only shunting to WT, constrains the DRB type from coexisting with the following DRB types: split Bearer, MCG side LWA Bearer;

when the following DRB types have been configured: split Bearer, and without offloading to WT, constrains the DRB type from coexisting with the following DRB types: SCG Bearer, MCG side LWA Bearer, SCG side LWA Bearer;

constraints cannot support configuring the following DRB types: split Bearer, and the MCG fraction in Split Bearer is shunted to WT;

constraints cannot support configuring the following DRB types: the SCG part in the Split Bearer is shunted to the WT;

constraints cannot support configuring the following DRB types: split Bearer, and both MCG and SCG fractions in Split Bearer are shunted to WT.

The invention also provides a configuration device of radio bearer, which is applied to a network side and comprises the following components: the configuration module is used for configuring the constraint rule of the DRB type; and the processing module is used for determining the type of the DRB required to be configured by the terminal UE according to the constraint rule and a preset strategy.

Further, the processing module is configured to determine, according to the constraint rule and a preset policy, a type of a DRB that the terminal UE needs to configure, including: and selecting the DRB type meeting the constraint rule from the DRB types determined according to the RRM measurement result of the UE, the corresponding input parameters and the RRM algorithm, and determining the DRB type required to be configured for the UE.

Further, the constraint rule includes:

constraint terms for different DRB types;

Further, the constraint term includes at least one of:

the method can avoid the constraint clause that the complexity of the PDCP data packet processing of the DRB by the base station and/or the UE exceeds the system processing capacity;

avoiding coexistence of multiple DRBs of different types results in a constraint that the air interface radio resource efficiency is lower than expected by the network operator and/or the user communication experience.

Further, the constraint term includes: the following two DRB types are constrained to be configured to coexist within the same base station and/or UE: split Bearer, LWA Bearer.

Further, the constraint term includes at least one of:

when the following DRB types have been configured: MCG Bearer, and when not shunting to WT or SeNB, there is no constraint on DRB type that can coexist with the DRB type;

when the following DRB types have been configured: the MCG side LWA Bearer, and only shunting to WT, constrains the DRB type from coexisting with the following DRB types: split Bearer, SCG side LWA Bearer;

when the following DRB types have been configured: SCG Bearer, and without offloading to WT or MeNB, constrains the DRB type from coexisting with the following DRB types: split Bearer;

In the invention, a network side configures a constraint rule of a Data Radio Bearer (DRB) type; and the network side determines the type of the DRB required to be configured by the terminal UE according to the constraint rule and a preset strategy. By the invention, when the network side is faced to select the bearer configuration types for a certain specific DRB of the UE, the combination selection of the bearer configuration types is restricted and controlled by the restriction rule, thereby reducing the complexity and burden of data packet processing on a wireless link, further reducing the complexity of system level development, realization of tests and the like of the network side and the UE side and avoiding cost rise.

Drawings

FIG. 1 is a network element node architecture diagram for LTE DC mode;

fig. 2 is a schematic diagram of three basic DRB type configurations provided by the LTE DC mode;

FIG. 3 is a network element node architecture diagram for LTE LWA mode;

fig. 4 is a schematic diagram of two basic DRB type configurations provided by LTE LWA mode;

fig. 5 is a flowchart of a method for configuring a radio bearer according to an embodiment of the present invention;

fig. 6 is a network node architecture diagram for LTE DC mode and LTE LWA mode joint coexistence configuration according to a first embodiment of the present invention;

FIG. 7 is a flow chart provided by the first embodiment of the present invention;

FIG. 8 is a schematic deployment diagram of a second embodiment of the present invention;

fig. 9 is a schematic deployment diagram of the third embodiment of the present invention.

Detailed Description

The embodiments of the present invention will be described in detail below with reference to the accompanying drawings, and it should be understood that the embodiments described below are only for illustrating and explaining the present invention and are not intended to limit the present invention.

Fig. 5 is a flowchart of a method for configuring a radio bearer according to an embodiment of the present invention. As shown in fig. 5, the method for configuring a radio bearer provided in this embodiment includes the following steps:

step 501: and the network side configures the constraint rule of the DRB type.

Wherein the constraint rules include:

constraint terms for different DRB types;

Further, the constraint term includes at least one of:

Further, the constraint term includes: the following two DRB types are constrained to be configured to coexist within the same base station and/or UE: split (Split) Bearer (Bearer), LWA Bearer in a long term evolution dual connectivity configuration.

Further, the constraint term includes at least one of:

when the following DRB types have been configured: SCG Bearer, and when not offloading to WT or the main base station MeNB, it is constrained that the DRB type cannot coexist with the following DRB types: split Bearer;

It should be noted that the present invention is not limited to the contents of the constraint clauses. In practical applications, the constraint terms can be further strengthened or released according to the needs and the system processing capacity.

The details of the above constraint clauses may be configured by the network side, and the above enumeration is only one possibility. Here, the above examples mainly illustrate some combination cases of DC dual connectivity + LWA coexistence; however, for the future evolution of the system, more LWA operations of connecting with multiple APs may occur, and at this time, the invention is also applicable for the future evolution of the system by setting the constraint terms meeting the requirements according to the setting principle of the constraint terms.

Step 502: and the network side determines the type of the DRB required to be configured by the UE according to the constraint rule and a preset strategy.

Further, step 502 includes: and the network side selects a DRB type meeting the constraint rule from DRB types determined according to a Radio Resource Management (RRM) measurement result of the UE, corresponding input parameters and an RRM algorithm, and determines the DRB type to be configured by the UE.

The present invention is described in detail below by way of examples.

Example one

Fig. 6 is a network node architecture diagram for LTE DC mode and LTE LWA mode joint coexistence configuration according to a first embodiment of the present invention. As shown in FIG. 6, the WT is directly connected to the MeNB through the external Xw interface (or the WT is built inside the MeNB), and the UE is configured with three wireless links, MCG Link (Uu-U (MeNB)), SCG Link (Uu-U (SeNB)), and WLAN Link at the same time. It is assumed here that there is still only one set of WLAN-related modules inside the UE, and therefore only one WLAN Link can be supported; if there are multiple sets of WLAN-related modules in the UE, and the UE may support multiple WLAN Links, the UE can be configured with more than three radio Links at the same time.

In this embodiment, assuming that the UE is in an initial state, and is neither in a DC mode nor in an LWA mode, when a core Network MME initiates establishment of a first DRB service data bearer to a Radio Access Network (RAN), the MeNB may make the following DRB type configuration selections according to the UE or other input condition parameters and an internal RRM algorithm:

opt 1-1: MCG Bearer only is established, with no shunting to WT or SeNB (pure DC operating mode support in Re12 version); thereafter, if the MeNB needs to re-establish a second DRB for the same UE, the type of configuring the second DRB for the UE may be selected as: any one of MCG Bearer, SCG Bearer, Split Bearer, MCG-side LWA Bearer, and SCG-side LWA Bearer, that is, the above-described various configuration types and the MCG Bearer already configured may coexist;

opt 1-2: establishing an MCG side LWA Bearer, and only shunting to WT (pure LWA working mode support in R13 version); thereafter, if the MeNB needs to re-establish a second DRB for the same UE, the type of configuring the second DRB for the UE may be selected as: any one of MCG Bearer, SCG Bearer, and MCG-side LWA Bearer, but the Split Bearer and the SCG-side LWA Bearer are constrained not to be configured, and here, in order to alleviate complexity and cost of system development implementation tests, the two configuration types and the already configured MCG-side LWA Bearer are constrained not to coexist;

opt 2-1: SCG Bearer only is established, with no shunting to WT or MeNB (pure DC mode of operation support in version R12); thereafter, if the MeNB needs to re-establish the second DRB for the same UE, the type of configuring the second DRB for the UE may be selected as: any one of MCG Bearer, SCG Bearer, MCG-side LWA Bearer, and SCG-side LWA Bearer, but the Split Bearer is constrained not to be configured, and here, in order to alleviate complexity and cost of system development implementation tests, this type of configuration and the already configured SCG Bearer are constrained not to coexist;

opt 2-2: establishing an SCG side LWA Bearer, and only shunting to WT (supported by pure LWA working mode of future evolution version); at this time, if the SeNB and the WT do not have an external Xw interface to be directly connected, they can be relayed by means of the X2 interface, so the X2 interface also needs to support the Xw related function and the information element transfer function, otherwise it is not necessary; thereafter, if the MeNB needs to re-establish a second DRB for the same UE, the type of configuring the second DRB for the UE may be selected as: any one of MCG Bearer, SCG Bearer, and SCG-side LWA Bearer, but the Split Bearer and the MCG-side LWA Bearer are constrained not to be configured, and here, in order to alleviate complexity and cost of system development implementation tests, the two configuration types and the configured SCG-side LWA Bearer are constrained not to coexist;

opt 3-1: only Split Bearer is established, but not shunted to WT (pure DC mode of operation support in version R12); thereafter, if the MeNB needs to re-establish a second DRB for the same UE, the type of configuring the second DRB for the UE may be selected as: any one of MCG Bearer and Split Bearer, but SCG Bearer, MCG-side LWA Bearer and SCG-side LWA Bearer are constrained from being configured, where, in order to alleviate complexity and cost of system development implementation testing, the three configuration types and already configured Split Bearer are constrained from coexisting;

opt 3-2: only build the Split Bearer, try to shunt the MCG part in the Split Bearer to the WT, where this configuration is constrained from being supported;

opt 3-3: only build the Split Bearer, try to shunt SCG part in the Split Bearer to WT, here, constrain that this configuration cannot support;

opt 3-4: only Split Bearer is established, and an attempt is made to shunt MCG/SCG part in Split Bearer to WT, thereby restricting this configuration from being supported.

Here, Opt1-1, Opt1-2, Opt2-1, Opt2-2, Opt3-1 to 3-4 are only examples of constraint clauses. In this way, the MeNB/UE can be prevented from performing Split/rearrangement (Reorder) operation processing on the PDCP data packets belonging to two or more DRBs at the same time, for example, the Split Bearer and the LWA Bearer can be prevented from being configured and coexisting in the same eNB/UE, so that the processing complexity and burden of the MeNB/SeNB/UE baseband chip can be greatly reduced.

It should be noted that: the constraint terms described above may be changed by static configuration in advance on the network side. The invention is not limited to the specific terms of the constraints. In other embodiments, the network side may set different constraint terms according to the needs and system processing capabilities, so as to further strengthen or release the coexistence configuration relationship between DRB types.

In addition, when the UE needs to support configuring more concurrent service data flows, more than two DRBs may be configured by the MeNB, and then a third, a fourth, or even more DRBs are established, where the MeNB still complies with the configuration constraint rule formed between the first DRB and the second DRB. Any newly-built DRB type can coexist with all configured and built DRBs configuration types, and all the DRB types are required to meet the limitation of the constraint terms of network side configuration.

FIG. 7 is a flowchart of the first embodiment of the present invention. As shown in fig. 7, the present embodiment includes the following steps:

step 701: the UE and the network side nodes MeNB/SeNB and WT support related DC working modes and LWA working modes, and the network side generates a constraint rule table of coexistence relations among configured DRB types in advance, wherein the constraint rule table comprises Opt1-1, Opt1-2, Opt2-1, Opt2-2 and Opt 3-1-3-4;

step 702: after the UE completes RRC connection with the network side, the MeNB needs to establish/reconfigure a first service bearer DRB (1) for the UE;

step 703: the MeNB determines the type of the DRB (1) according to the RRM measurement report result of the UE, other input parameters and the RRM algorithm of the MeNB;

for example, if the UE is in a better signal coverage/load level of the MCG cell, the MeNB determines to use the MCG Link to establish an MCG Bearer for the DRB (1); if the UE is in a better signal coverage/load degree of the SCG cell, the MeNB determines to utilize the SCG Link to establish an SCG Bearer for the DRB (1); if the UE is in a better signal coverage/load degree shared by the MCG/SCG cells, the MeNB determines to simultaneously utilize the MCG/SCG Link to establish a Split Bearer for the DRB (1); if the UE is in a better signal coverage/load degree of a WT/AP cell on the MCG side, the MeNB determines to utilize the WLAN Link to establish an LWA Bearer on the MCG side for the DRB (1); if the UE is in a better signal coverage/load degree of the WT/AP cell on the SCG side, the MeNB determines to utilize the WLAN Link to establish an LWA Bearer on the SCG side for the DRB (1);

step 704: when the MeNB needs to establish/reconfigure more service data bearers DRBs (i) for the same UE, besides input parameters such as RRM measurement report results and RRM algorithms of the MeNB, the MeNB strictly complies with the constraint rules configured above, and any newly-established/reconfigured drb (i) type can coexist with all configured established/reconfigured DRBs configuration types, otherwise, the MeNB must reselect the drb (i) type, or perform type (type) reconfiguration on the configured DRBs. Here, DRB (i) represents the ith DRB, where i is an integer greater than or equal to 1.

In addition, as time goes by, when the network coverage environment/service node load status of the UE is also changing, the MeNB needs to reconfigure all established DRBs types, and also needs to strictly comply with the constraint rules of the above configuration.

Example two

Fig. 8 is a deployment diagram of a second embodiment of the present invention. The present embodiment is explained below with reference to fig. 8:

as shown in fig. 8, a main (macro) base station MeNB and a secondary (micro) base station SeNB are connected via an X2 interface, the MeNB/SeNB is connected via an Xw interface with respective independent WT/AP nodes, both MeNB/SeNB, WT/AP support related DC mode and LWA mode operations;

the UE is already in RRC connected state at a certain time and under good signal coverage of potential target MCG serving cells (a group of cells under MeNB), SCG serving cells (a group of cells under SeNB), and MCG-side WT/AP, the signal coverage of SCG-side WT/AP is not good; the UE supports related DC mode and LWA mode operations;

the MeNB generates a constraint rule table for DRB type coexistence, for example, the same as the example described in the first embodiment;

when a user starts a data downloading service, a service MeNB needs to selectively establish/reconfigure a first service bearer DRB (1) for UE;

the MeNB learns, according to RRM Measurement results reported by the UE through an RRC Measurement Report (Measurement Report) message: the UE is currently under the good signal coverage of a target MCG service cell, a target SCG service cell and a target MCG side WT/AP, in addition, the MeNB learns that the load of the target SCG service cell is relatively light at the moment through an X2 interface interaction message, and learns that the load of the target MCG side WT/AP is relatively light at the moment through an Xw interface interaction message, so that the type of the DRB (1) is determined to be SCG Bearer;

when the user starts the online video watching service, the service MeNB needs to establish/reconfigure a second service bearer DRB (2) for the UE selection; at this time, assuming that the network signal coverage/load status of the UE does not change, according to the preconfigured constraint rule, the MeNB may select the configuration types for the DRB (2) as follows: any one of MCG Bearer, SCG Bearer, MCG-side LWA Bearer, and SCG-side LWA Bearer; the MeNB determines the type of DRB (2) as the MCG-side LWA Bearer (e.g., may be configured as the LWA Switched Bearer in (b) of fig. 4) in combination with the RRM algorithm input conditions. The MCG Link in fig. 8 runs on the SRB radio bearer, the WLAN Link on the MCG side runs on DRB (2), and the SCG Link runs on DRB (1).

As time changes, the network coverage environment/serving node load status of the UE also changes, and therefore, the MeNB may need to reconfigure the established DRB (1)/DRB (2) types, such as reconfiguring DRB (1) into MCG Bearer, DRB (2) into LWA Split Bearer in (a) of MCG-side fig. 4, and so on.

In addition, if the user starts more data services during the period, the MeNB needs to establish more DRBs (i) for the UE, any newly-established/reconfigured DRBs (i) type can coexist with all configured DRBs configuration types according to the constraint rule, otherwise, the type of the DRBs (i) must be reselected, or the configured DRBs are subjected to type reconfiguration. Here, DRB (i) represents the ith DRB, where i is an integer greater than or equal to 1.

EXAMPLE III

Fig. 9 is a deployment diagram of a third embodiment of the present invention. The present embodiment is explained below with reference to fig. 9:

as shown in fig. 9, the main (macro) enb and the auxiliary (micro) enb are connected via an X2 interface, the MeNB/SeNB is connected via an Xw interface to respective independent WT/AP nodes, and both the MeNB/SeNB and the WT/AP support the related DC operation mode and LWA operation mode;

the UE is already in RRC connected state at a certain time and under good signal coverage of potential target MCG serving cells (a group of cells under MeNB), SCG serving cells (a group of cells under SeNB), and SCG-side WT/AP, signal coverage of MCG-side WT/AP is not good; the UE supports related DC mode and LWA mode operations;

the MeNB generates a constraint rule table of DRB type coexistence configuration in advance, for example, the example described in the first embodiment;

when a user starts a file uploading service, a service MeNB needs to selectively establish/reconfigure a first service bearer DRB (1) for UE;

the MeNB learns, according to RRM Measurement results reported by the UE through an RRC Measurement Report (Measurement Report) message: the UE is currently under good signal coverage of the target MCG serving cell, the target SCG serving cell and the target SCG-side WT/AP, and further, the MeNB knows that the target MCG/SCG serving cell has almost the same load at the moment through the X2 interface interaction message, and knows that the target SCG-side WT/AP has relatively lighter load at the moment through the Xw + X2 interface interaction message, and thus, it is determined that the DRB (1) is of the type LWA Bearer on the SCG side (which may be specifically configured as the LWA Switched Bearer in (b) of fig. 4);

when the user starts the voice service of VOLTE (Voice over LTE) again, the service MeNB needs to establish/reconfigure a second service bearer DRB (2) for the UE; at this time, assuming that the network signal coverage/serving node load state where the UE is located does not change, according to the preconfigured constraint rule, the MeNB may select the configuration types for the DRB (2) as follows: any one of MCG Bearer, SCG Bearer, and SCG-side LWA Bearer; and finally determining the type of the DRB (2) as MCG Bearer by the MeNB in combination with the RRM algorithm input condition. The MCG Link in fig. 9 runs on the SRB radio bearer and DRB (2), and the SCG side WLAN Link runs on DRB (1).

As time goes by, the network coverage environment/serving node load status of the UE also changes, and therefore, the MeNB may need to reconfigure the DRB (1)/DRB (2) types already established, such as reconfiguring DRB (1) into SCG Bearer, reconfiguring DRB (2) into LWA Switched Bearer in (b) of MCG-side fig. 4, and so on.

In addition, an embodiment of the present invention further provides a radio bearer configuration apparatus, applied to a network side, including: the configuration module is used for configuring the constraint rule of the DRB type; and the processing module is used for determining the type of the DRB required to be configured by the terminal UE according to the constraint rule and a preset strategy.

Further, the processing module is configured to determine, according to the constraint rule and a preset policy, a type of a DRB that the terminal UE needs to configure, including: and selecting a DRB type meeting the constraint rule from the DRB types determined according to the RRM measurement result of the UE, the corresponding input parameters and the RRM algorithm, and determining the DRB type required to be configured by the UE.

Further, the constraint rule includes:

constraint terms for different DRB types;

Further, the constraint term includes at least one of:

The specific processing flow of the above device is the same as that of the above method, and therefore, the detailed description thereof is omitted.

It will be understood by those skilled in the art that all or part of the steps of the above methods may be implemented by instructing the relevant hardware through a program, and the program may be stored in a computer readable storage medium, such as a read-only memory, a magnetic or optical disk, and the like. Alternatively, all or part of the steps of the above embodiments may be implemented using one or more integrated circuits. Accordingly, each module/unit in the above embodiments may be implemented in the form of hardware, and may also be implemented in the form of a software functional module. The present invention is not limited to any specific form of combination of hardware and software.

It should be noted that the embodiments and features of the embodiments in the present application may be arbitrarily combined with each other without conflict. The above description is only a preferred embodiment of the present invention, and not intended to limit the scope of the present invention, and all modifications of equivalent structures and equivalent processes, which are made by using the contents of the present specification and the accompanying drawings, or directly or indirectly applied to other related technical fields, are included in the scope of the present invention. The present invention is capable of other embodiments, and various changes and modifications may be made by one skilled in the art without departing from the spirit and scope of the invention.

The foregoing shows and describes the general principles and broad features of the present invention and advantages thereof. The present invention is not limited to the above-described embodiments, which are described in the specification and illustrated only for illustrating the principle of the present invention, but various changes and modifications may be made within the scope of the present invention as claimed without departing from the spirit and scope of the present invention.

Claims

1. A method for configuring a radio bearer, comprising:

a network side configures a constraint rule of a Data Radio Bearer (DRB) type;

the network side determines the type of the DRB required to be configured by the terminal UE according to the constraint rule and a preset strategy; wherein the constraint rules include: constraint terms for different DRB types; any newly-built or reconfigured DRB type and all configured DRB types meet the constraint terms;

the constraint term includes at least one of:

the method includes the steps that the complexity of processing a packet data convergence protocol PDCP data packet to which a DRB belongs by a base station and/or UE is prevented from exceeding the constraint clause of system processing capacity;

2. The method of claim 1, wherein the determining, by the network side according to the constraint rule and a preset policy, the type of the DRB that the UE needs to configure includes: and the network side selects a DRB type meeting the constraint rule from DRB types determined according to the RRM measurement result of the UE, the corresponding input parameters and the RRM algorithm, and determines the DRB type required to be configured for the UE.

3. The method of claim 1, wherein the constraint rule further comprises: and when the newly built or reconfigured DRB type can not meet the constraint terms, performing type reconfiguration on all the configured DRBs until any newly built or reconfigured DRB type and all the configured DRB types meet the constraint terms.

4. The method of claim 1, wherein the constraint term comprises: the following two DRB types are constrained to be configured to coexist within the same base station and/or UE: the Split bearing Bearer, the long term evolution and the wireless local area network aggregation LWA Bearer under the long term evolution LTE dual-connection configuration.

5. The method of claim 1, wherein the constraint term comprises at least one of:

when the following DRB types have been configured: a main cell set MCG Bearer, and when not shunting to a wireless local area network (WT) node or a secondary base station (SeNB), a DRB type which can coexist with the DRB type is unconstrained;

when the following DRB types have been configured: the MCG side LWA Bearer, and only shunting to WT, constrains the DRB type from coexisting with the following DRB types: the Split Bearer and the LWA Bearer at the SCG side of the secondary cell set;

constraints cannot support configuring the following DRB types: split Bearer, and the SCG fraction in Split Bearer is shunted to WT;

6. A radio bearer configuration device applied to a network side includes:

the configuration module is used for configuring the constraint rule of the DRB type;

the processing module is used for determining the type of the DRB required to be configured by the terminal UE according to the constraint rule and a preset strategy; wherein the constraint rules include: constraint terms for different DRB types; any newly-built or reconfigured DRB type and all configured DRB types meet the constraint terms;

the constraint term includes at least one of:

7. The apparatus of claim 6, wherein the processing module is configured to determine the type of the DRB that the terminal UE needs to configure according to the constraint rule and a preset policy, and includes: and selecting a DRB type meeting the constraint rule from the DRB types determined according to the RRM measurement result of the UE, the corresponding input parameters and the RRM algorithm, and determining the DRB type required to be configured by the UE.

8. The apparatus of claim 6, wherein the constraint rule further comprises: and when the newly built or reconfigured DRB type can not meet the constraint terms, performing type reconfiguration on all the configured DRBs until any newly built or reconfigured DRB type and all the configured DRB types meet the constraint terms.

9. The apparatus of claim 6, wherein the constraint term comprises: the following two DRB types are constrained to be configured to coexist within the same base station and/or UE: split Bearer, LWA Bearer.

10. The apparatus of claim 6, wherein the constraint term comprises at least one of: