WO2016197989A1

WO2016197989A1 - Radio bearer configuration method and apparatus

Info

Publication number: WO2016197989A1
Application number: PCT/CN2016/085717
Authority: WO
Inventors: 杨立
Original assignee: 中兴通讯股份有限公司
Priority date: 2015-11-10
Filing date: 2016-06-14
Publication date: 2016-12-15
Also published as: CN106686751B; CN106686751A

Abstract

A radio bearer configuration method and apparatus, comprising: a network side configures a DRB type constraint rule; and the network side, on the basis of the constraint rule and a preset policy, determines that a UE requires the configured DRB type. The present technical solution can reduce the complexity and load of data packet processing on wireless links, and thus reduce the complexity and load of system processing.

Description

Method and device for configuring wireless bearer

Technical field

This document relates to, but is not limited to, the field of mobile communications, and in particular, to a method and an apparatus for configuring a radio bearer.

Background technique

The Long Term Evolution (LTE) and Long Term Evolution (LTE-A, LTE-Advanced) systems of the 3rd Generation Partnership Project (3GPP, 3rd Generation Partnership Project) were introduced in the R12 (Release 12) version. The very important dual connectivity (DC, Dual Connectivity) function enables a single terminal (UE, User Equipment) to simultaneously and two LTE serving base stations (MeNB, Master evolved Node B) and Secondary base station (SeNB, Secondary evolved Node). B)) Transmitting and transmitting wireless data and uplink and downlink user service data. As shown in FIG. 1 , a UE in an LTE DC working mode can simultaneously carry a User Radio Bearer (Data Radio Bearer) on the Uu-U air interface with the MeNB and the SeNB, and each DRB corresponds to and carries one user service. Data stream) Performs duplex communication of uplink and downlink service data. The MeNB is a UE RRC (Radio Resource Control) anchor control network element, and is responsible for UE mobility and/or through a Uu-C air interface control plane bearer (Signaling Radio Bearer (SRB)). Or air interface radio resource configuration control management and other functions. The SeNB must connect to the MeNB through the X2-U ground interface user plane and the X2-C ground interface control plane to provide additional service data offload and bearer for the UE, thereby enhancing the overall data transmission rate of the UE. The MeNB may be connected to the control plane network element mobility management entity (MME, Mobility Management Entity) and the user plane network element service gateway (SGW, Serving Gateway) of the LTE core network, respectively corresponding to the S1-MME and the S1-U (MeNB) ground. The interface, and the SeNB can only be connected to the user plane network element SGW, corresponding to the S1-U (SeNB) terrestrial interface. The non-access stratum control signaling interaction between the UE and the LTE core network can only be implemented by the MeNB, and the access layer control signaling interaction between the UE and the LTE access network can only be implemented by the MeNB; and the UE and the LTE core network and The service data interaction of the access network can be carried by the primary cell group (MCG, Master Cell Group) configured by the MeNB. (Bearer) can be implemented by the MCG Bearer configured by the SeNB. When the SeNB performs control signaling interaction with the MME or the UE, it must be implemented by the MeNB's transit negotiation and forwarding.

The LTE DC working mode can provide three basic DRB types, as shown in Figure 2. The bold line in Figure 2(a) indicates the MCG Bearer, and the uplink and downlink transmission of user service data is realized through the MCG link (Link); The bold line in (b) indicates the split Bearer, and the uplink and downlink transmission of the user service data is simultaneously realized by the MCG Link and the Secondary Cell Group (SCG); the bold line in FIG. 2(c) indicates the SCG. Bearer implements uplink and downlink data transmission of user service data through SCG Link.

The LTE and LTE-A systems of the 3GPP standard specification introduce a very important long-term evolution and LTE WLAN Aggregation (LWA) function in the R13 (Release 13) version, namely LTE system and wireless local area network (WLAN, Wireless Local). Access Network) The aggregation of wireless resources between the systems at the wireless access layer. The MeNB directly connects to the WLAN transmission node in the WT by using one or more DRBs corresponding to the Packet Data Converge Protocol (PDCP) by connecting the internal interface or the Xw interface to the WLAN (Terminal WLAN Termination). (For example, access control (AC, Access Control) and/or access node (AP, Access Point)), and then the WLAN AP node performs data transmission through the WLAN Link and the UE. As shown in FIG. 3, since the LWA adopts a DC-like working architecture, the WT is similar to the logical role and status of the SeNB in the architecture of FIG. 1, but the UE in the DC dual connectivity and the MeNB and the SeNB respectively have an LTE in FIG. Link, and the UE in the LWA and the MeNB and the WT in FIG. 3 each have an LTE Link and a WLAN Link. The common mode of the DC and LWA working modes is that the network side and the control plane radio bearer SRB of the UE can only take the MeNB Uu-C interface.

The LWA working mode can provide two basic DRB types (which can be collectively referred to as LWA Bearer), as shown in Figure 4, where the bold line in Figure 4(a) represents the LWA Split Bearer, passing the LTE Link and WT on the MeNB side. The WLAN Link air interface resource on the side implements the uplink and downlink transmission of the user service data at the same time. The bold line in Figure 4(b) indicates the LWA switched (Beared) Bearer. The MeNB only forwards the Xw-U and the WLAN Link air interface resource on the WT side. Realize the uplink and downlink transmission of user service data; Figure 4 (b) is a special case of Figure 4 (a), namely MeNB Or the UE diverts all PDCP data packets belonging to the DRB to the WT side according to the 0:100% split ratio. FIG. 4(a) requires the UE to act as the downlink receiving side, and performs downlink PDCP data flows from the LTE Link and the WLAN Link. Reordering and integration; Figure 4(a) also requires the MeNB to be used as the uplink receiving side to reorder and integrate the uplink PDCP data streams from the LTE Link and the WLAN Link; Figure 4(b) only involves one data of the WLAN Link. Flow, therefore, the processing on both the MeNB and the UE side is relatively simple.

In the R13 version, due to the large processing complexity of the system, the joint coexistence configuration of the UE's LTE DC dual connectivity operation and LWA operation cannot be supported. This causes the UE to be in the DC working mode at a time. If the LTE network side wants to perform the LWA operation, the LTE network side must first pass multiple RRC control signaling, so that the UE first exits the DC configuration and then passes. Multiple RRC control signaling allows the UE to re-enter the LWA configuration and vice versa. Along with the 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 user plane DRBs data transmission of the UE is interrupted for a period of time, thus reducing the user's data service experience. (such as peak data rates), and caused performance degradation such as business fluency. Therefore, in versions after R13, mobile operators need systems capable of supporting joint coexistence configuration and operation of DC dual connectivity operations and LWA operations.

Summary of the invention

The following is an overview of the topics detailed in this document. This Summary is not intended to limit the scope of the claims.

The embodiments of the present invention provide a method and an apparatus for configuring a radio bearer, which can reduce the complexity and burden of data packet processing on a wireless link, thereby reducing system processing complexity and burden.

The embodiment of the present invention provides a method for configuring a radio bearer, including: configuring a data radio bearer (DRB) type constraint rule on the network side; and determining, by the network side, the type of the DRB that the terminal UE needs to be configured according to the constraint rule and the preset policy. .

Optionally, the network side determines, according to the constraint rule and the preset policy, the type of the DRB that the UE needs to be configured, including: the network side from the radio resource management (RRM) measurement result according to the UE, and corresponding The input parameter and the DRB type determined by the RRM algorithm select the DRB type that satisfies the constraint rule, and determine the type of the DRB that the UE needs to configure.

Optionally, the constraint rule includes:

Different DRB type constraints;

Any new or reconfigured DRB type and all configured DRB types satisfy the constraint terms.

Optionally, the constraint rule further includes: when the newly created or reconfigured DRB type cannot meet the constraint clause, perform type reconfiguration on all configured DRBs until all the newly created or reconfigured DRB types are met. The constraint terms are met with all configured DRB types.

Optionally, the constraint clause includes at least one of the following:

Avoiding the complexity of the packet data convergence protocol (PDCP) packet processing of the DRB to which the base station and/or the UE is performed exceeds the constraint of the processing capability of the system;

Avoiding the constraint that the processing burden of the base station and/or UE exceeds the system cost;

Avoiding different types of multiple DRB coexistence results in air interface radio resource efficiency being lower than the network operator and/or user communication experience expected constraints.

Optionally, the constraint clause further includes: restricting the following two types of DRBs from being configured to coexist in the same base station and/or the UE: splitting (Bearer) and long-term evolution in a long-term evolution (LTE) dual-connection configuration And Wireless LAN Aggregation (LWA) Bearer.

Optionally, the constraint clause further includes at least one of the following:

When the following DRB type has been configured: a primary cell set (MCG) Bearer, and is not offloaded to a wireless local area network (WT) or a secondary base station (SeNB), the DRB type that can coexist with the DRB type has no constraint;

When the following DRB types are configured: the MCG side LWA Bearer, and only the WT is offloaded, the DRB type cannot be coexisted with the following DRB types: Split Bearer, Secondary Cell Set (SCG) side LWA Bearer;

When the following DRB type is configured: SCG Bearer, and is not offloaded to the WT or the primary base station (MeNB), the DRB type is not allowed to coexist with the following DRB types: Split Bearer;

The DRB type cannot be coexisted with the following DRB types: Split Bearer, MCG side LWA Bearer, when the DRB type is configured on the SCG side, and only the WT is offloaded to the WT.

When the following DRB types are configured: Split Bearer, and the traffic is not offloaded to the WT, the DRB type cannot be coexisted with the following DRB types: SCG Bearer, LSG Bearer on the MCG side, and LWA Bearer on the SCG side.

The constraint cannot support the configuration of the following DRB type: Split Bearer, and the MCG part in the Split Bearer is offloaded to the WT;

The constraint cannot support the configuration of the following DRB type: Split Bearer, and the SCG part in the Split Bearer is offloaded to the WT;

The constraint cannot support the following DRB types: Split Bearer, and the MCG and SCG parts in the Split Bearer are offloaded to the WT.

The embodiment of the present invention further provides a device for configuring a radio bearer, which is applied to a network side, and includes: a configuration module, configured to configure a constraint rule of a DRB type; and a processing module configured to determine the terminal according to the constraint rule and a preset policy. The type of DRB that the UE needs to configure.

Optionally, the processing module is configured to determine, according to the constraint rule and the preset policy, a type of the DRB that the terminal UE needs to configure according to the following: from the RRM measurement result according to the UE, the corresponding input parameter And selecting a DRB type that satisfies the constraint rule among the DRB types determined by the RRM algorithm, and determining the type of the DRB that the UE needs to be configured.

Optionally, the constraint rule includes:

Different DRB type constraints;

Optionally, the constraint rule further includes: when the newly created or reconfigured DRB type cannot meet the constraint clause, perform type reconfiguration on all the configured DRBs until the type of the newly created or reconfigured DRB is satisfied. The constraint terms are met with all configured DRB types.

Optionally, the constraint clause includes at least one of the following:

The complexity of avoiding the PDCP packet processing of the DRB by the base station and/or the UE exceeds the constraint of the processing capability of the system;

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

Optionally, the constraint clause further includes: the following two DRB types cannot be configured to coexist in the same base station and/or the UE: Split Bearer, LWA Bearer.

When the following DRB type is configured: MCG Bearer, and the WT or SeNB is not offloaded, the DRB type that can coexist with the DRB type has no constraint;

When the following DRB types are configured: the LGW Bearer on the MCG side, and only the WT is offloaded, the DRB type cannot be coexisted with the following DRB types: Split Bearer, SCG side LWA Bearer;

When the following DRB type is configured: SCG Bearer, and the WT or MeNB is not offloaded, the DRB type cannot be coexisted with the following DRB types: Split Bearer;

In the embodiment of the present invention, the network side configuration data radio bears the DRB type constraint rule; the network side determines the type of the DRB that the terminal UE needs to configure according to the constraint rule and the preset policy. When the network side faces the selection of a bearer configuration type for a specific DRB of the UE, the constraint control is performed on the combination selection of the bearer configuration types by using the constraint rule, thereby reducing the complexity of data packet processing on the wireless link. Degree and burden, thereby reducing the complexity of system-level development and implementation testing on the network side and the UE side and avoiding cost increases.

Other aspects will be apparent upon reading and understanding the drawings and detailed description.

BRIEF abstract

1 is a network element node architecture diagram of an LTE DC mode;

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

3 is a network element node architecture diagram of an LTE LWA mode;

4 is a schematic diagram of two basic DRB type configurations provided by the 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 structural diagram of a node structure of a joint coexistence configuration network of an LTE DC mode and an LTE LWA mode according to a first embodiment of the present invention;

Figure 7 is a flowchart provided by the first embodiment of the present invention;

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

FIG. 9 is a schematic diagram of deployment according to a third embodiment of the present invention; FIG.

FIG. 10 is a schematic structural diagram of a radio bearer configuration apparatus applied to a network side according to an embodiment of the present invention.

Embodiments of the invention

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

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 by this embodiment includes the following steps:

Step 501: Configure a constraint rule of the DRB type on the network side.

The constraint rule includes:

Different DRB type constraints;

Optionally, the constraint rule further includes: when there is a newly created or reconfigured DRB type that cannot be satisfied In the constraint clause, the type reconfiguration is performed on all the configured DRBs until the DRB type of any new or reconfigured type and all the configured DRB types satisfy the constraint clause.

Optionally, the constraint clause includes at least one of the following:

Optionally, the constraint clause includes: restricting the following two types of DRBs from being configured to coexist in the same base station and/or the UE: a split bearer (Bearer) and an LWA Bearer in a long-term evolution dual-connection configuration.

Optionally, the constraint clause includes at least one of the following:

When the following DRB type is configured: SCG Bearer, and the WT or the primary base station MeNB is not offloaded, the DRB type cannot be coexisted with the following DRB types: Split Bearer;

It should be noted that the present invention does not limit the content of the constraint. In practical applications, the constraints can be further enhanced or released according to needs and system processing capabilities.

The details of the above constraint clauses can be configured by the network side, and the above enumeration is only one possibility. Here, the above example mainly illustrates some combinations of DC dual connectivity + LWA coexistence; however, for the future evolution of the system, there may be more LWA operations of connection + multi-AP, in this case, according to the setting principle of the constraint clause The present invention is equally applicable to the future evolution of the system by setting constraints that meet the requirements.

Step 502: The network side determines, according to the constraint rule and the preset policy, the type of the DRB that the UE needs to be configured.

Optionally, step 502 includes: the network side selects a DRB type that satisfies the constraint rule from a DRB type determined according to a radio resource management (RRM) measurement result of the UE, a corresponding input parameter, and a RRM algorithm. Determine the type of DRB that the UE needs to configure.

The invention is described in detail below by means of a plurality of embodiments.

Embodiment 1

FIG. 6 is a structural diagram of a node structure of a joint coexistence configuration network of an LTE DC mode and an LTE LWA mode according to a first embodiment of the present invention. As shown in Figure 6, the WT is directly connected to the MeNB through the external Xw interface (or the WT is built in the MeNB). For example, the UE is configured with the following three radio links: MCG Link (Uu-U (MeNB)) and SCG Link. (Uu-U (SeNB)), WLAN Link. It is assumed that there is still only one WLAN-related module in the UE, so only one WLAN Link can be supported. If the UE has multiple WLAN-related modules, the UE may support multiple WLAN Links, and the UE can be configured with more than three at the same time. Wireless link.

In this embodiment, it is assumed that the initial state of the UE is neither in the DC mode nor in the LWA mode. When the core network MME initiates the establishment of the first DRB service data bearer to the radio access network (RAN, Radio Access Network) The MeNB can perform the following DRB type configuration selections according to the UE or other input condition parameters and the internal RRM algorithm:

Opt1-1: Only the MCG Bearer is established, and the WT or the SeNB is not offloaded (the pure DC working mode is supported in the Re12 version). Thereafter, if the MeNB needs to establish a second DRB for the same UE, the configuration may be selected for the UE. The two DRBs are of the MCG Bearer, the SCG Bearer, the Split Bearer, the MCG side LWA Bearer, and the SCG side LWA Bearer. That is, the above various configuration types and the configured MCG Bearer can coexist;

Opt1-2: Establishes the LGW Bearer on the MCG side, and only offloads to the WT (supported by the pure LWA working mode in the R13 version). After that, if the MeNB needs to establish a second DRB for the same UE, you can select the second configuration for the UE. The type of the DRB is any one of the MCG Bearer, the SCG Bearer, and the MCG side LWA Bearer, but the constraint Split Bearer and the SCG side LWA Bearer cannot be configured. Therefore, in order to reduce the complexity and cost of the system development and implementation test, The two configuration types are restricted and the configured MCG side LWA Bearer cannot coexist;

Opt2-1: Only the SCG Bearer is established, and the WT or MeNB is not offloaded (the pure DC working mode support in the R12 version). Thereafter, if the MeNB needs to establish a second DRB for the same UE, the configuration may be selected for the UE. The types of the two DRBs are: MCG Bearer, SCG Bearer, LSG Bearer on the MCG side, and LWA Bearer on the SCG side. However, the constraint Split Bearer cannot be configured. In this case, the complexity and cost of the test for system development are reduced. , the constraint of this configuration type and the already configured SCG Bearer cannot coexist;

Opt2-2: Establishes the LWA Bearer on the SCG side and only offloads to the WT (supported in the pure LWA working mode of the future evolved version). At this time, if the SeNB and the WT do not have an external Xw interface directly connected, they can be relayed by means of the X2 interface, so X2 The interface also needs to support the Xw related function and the cell transfer function, and vice versa. After that, if the MeNB needs to establish a second DRB for the same UE, the type of the second DRB can be selected for the UE: MCG Bearer, Any one of SCG Bearer and SCG side LWA Bearer, but the constraint Split Bearer and MCG side LWA Bearer cannot be configured. In order to reduce the complexity and cost of system development and implementation test, the two configuration types are constrained and configured. The SCG side LWA Bearer cannot coexist;

Opt3-1: Only the Split Bearer is established, but the WT is not offloaded (the pure DC working mode is supported in the R12 version). After that, if the MeNB needs to establish a second DRB for the same UE, the second configuration can be selected for the UE. The type of DRB is: MCG Bearer and Split Bearer, but constrains SCG Bearer, MCG side LWA Bearer, and SCG side LWA. Bearer can't be configured. In order to reduce the complexity and cost of system development and implementation testing, the three configuration types and the configured Split Bearer cannot be coexisted.

Opt3-2: Only the Split Bearer is established, and the MCG part in the Split Bearer is attempted to be offloaded to the WT. Therefore, the configuration is not supported by the configuration.

Opt3-3: Only the Split Bearer is established, and the SCG part in the Split Bearer is attempted to be offloaded to the WT. Here, the configuration is not supported;

Opt3-4: Only the Split Bearer is established. Attempts to split the MCG and SCG part in the Split Bearer to the WT. Therefore, this configuration cannot be supported.

Here, the above Opt1-1, Opt1-2, Opt2-1, Opt2-2, Opt3-1 to 3-4 are merely examples of the constraint terms. In this case, it is possible to prevent the MeNB and the UE from performing the Split or Reorder operation of the PDCP packets to which the DRB belongs to the two or more devices, for example, to prevent the configuration of the Split Bearer and the LWA Bearer from coexisting in the same eNB and the UE. The processing complexity and burden of the MeNB, SeNB, and UE baseband chips can be greatly reduced.

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

In addition, when the UE needs to support configuring more concurrent traffic data flows, the MeNB may configure more than two DRBs, and then establish third, fourth, or even more DRBs. At this time, the MeNB still complies with the above first A configuration constraint rule formed between the strip DRB and the second DRB. The newly created DRB type must coexist with all the configured DRBs configuration types, and all of them must meet the restrictions of the network side configuration constraints.

Figure 7 is a flow chart of the first embodiment of the present invention. As shown in FIG. 7, the embodiment includes the following steps:

Step 701: The UE and the network side node MeNB, the SeNB, and the WT support the related DC working mode and the LWA working mode, and the network side generates a constraint rule table of the configured DRB type coexistence relationship in advance, for example, including Opt1-1 and Opt1-2. Opt2-1, Opt2-2, Opt3-1~3-4;

Step 702: The UE has completed the RRC connection with the network side, and the MeNB needs to establish or Reconfigure the first service bearer DRB(1);

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 its own RRM algorithm.

For example, if the UE is in a good signal coverage and/or load level of the MCG cell, the MeNB decides to use the MCG Link to establish an MCG Bearer for the DRB (1); if the UE is in a good signal coverage and/or load of the SCG cell To the extent that the MeNB decides to use the SCG Link to establish an SCG Bearer for the DRB (1); if the UE is in a good signal coverage and/or load level between the MCG and the SCG cell, the MeNB decides to use both the MCG and the SCG Link as the DRB ( 1) Establishing a Split Bearer; if the UE is in a good signal coverage and/or load level of the MCG side WT or AP cell, the MeNB decides to use the WLAN Link to establish the MCG side LWA Bearer for the DRB (1); if the UE is on the SCG side WT Or the AP coverage of the AP cell is better, and the MeNB decides to use the WLAN Link to establish the SCG side LWA Bearer for the DRB (1);

Step 704: When the MeNB needs to establish or reconfigure more service data bearers DRB(i) for the same UE, in addition to the input parameters and the RRM algorithm based on the RRM measurement report result of the UE, the above configuration is strictly adhered to. For the constraint rule, any new or reconfigured DRB(i) type can coexist with all DRBs configuration types that have been configured or reconfigured. If there is a new or reconfigured DRB(i) type, it cannot be configured with all the configurations. The reconfigured DRBs configuration type coexist, and the DRB(i) type must be re-selected, or the type reconfiguration of the configured DRBs. Here, DRB(i) represents the i-th DRB, where i is an integer greater than or equal to 1.

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

Embodiment 2

FIG. 8 is a schematic diagram of deployment according to Embodiment 2 of the present invention. The present embodiment will be described with reference to FIG. 8 as follows:

As shown in FIG. 8, the primary (macro) base station MeNB and the secondary (micro) base station SeNB are connected through an X2 interface, and the MeNB and the SeNB are connected to respective independent WT or AP nodes through an Xw interface, and the MeNB and the SeNB, the WT or the AP are both connected. Support related DC mode and LWA mode operation;

The UE is already in the RRC connected state at a moment, and is under the good coverage of the signal of the potential target MCG serving cell (a group of cells subordinate to the MeNB), the SCG serving cell (a group of cells subordinate to the SeNB), and the MCG side WT or AP. The signal coverage of the WT or AP on the SCG side is poor; the UE supports the related DC mode and LWA mode operation;

The MeNB generates a constraint rule table in which the DRB type coexists, for example, the example described in the first embodiment;

When the user initiates the data download service, the serving MeNB needs to select to establish or reconfigure the first service bearer DRB (1) for the UE;

The MeNB learns that the UE is currently under the good coverage of the target MCG serving cell, the target SCG serving cell, and the target MCG side WT or AP according to the RRM measurement reported by the UE through the RRC Measurement Report message. In addition, the MeNB passes The X2 interface interaction message is that the target SCG serving cell is relatively light at the moment, and the XW interface exchange message is that the target MCG side WT or AP is relatively light at the moment, and therefore, the type of the DRB (1) is determined to be SCG Bearer;

When the user then initiates the online video viewing service, the serving MeNB needs to select to establish or reconfigure the second service bearer DRB (2) for the UE; at this time, assume that the network signal coverage and/or load status of the UE does not change, according to Pre-configured constraint rules, the MeNB may select one of the types configured for the DRB (2): MCG Bearer, SCG Bearer, MCG side LWA Bearer, and SCG side LWA Bearer; the MeNB combines the RRM algorithm input conditions to determine the DRB ( 2) The type is the MCG side LWA Bearer (for example, it can be configured as the LWA Switched Bearer in Fig. 4(b)). The MCG Link in Figure 8 runs the SRB radio bearer, the MCG side WLAN Link runs DRB (2), and the SCG Link runs DRB (1).

As time changes, the network coverage environment and/or service node load status of the UE is also changing. Therefore, the MeNB may need to reconfigure the established DRB(1) and DRB(2) types, such as DRB ( 1) Reconfigure the MCG Bearer, reconfigure the DRB (2) into the LWA Split Bearer in Figure 4 (a) on the MCG side, and so on.

In addition, if the user initiates more data services during the period, the MeNB needs to establish more DRB(i) for the UE, and any new or reconfigured DRB(i) type must be configured according to the above constraint rules and all configured. The DRBs configuration type that is established or reconfigured coexists. If there is a new or reconfigured DRB(i) type, the DRBs cannot be established or reconfigured according to the above constraint rules. If the configuration type coexists, you must re-select the DRB(i) type or reconfigure the configured DRBs. Here, DRB(i) represents the i-th DRB, where i is an integer greater than or equal to 1.

Embodiment 3

FIG. 9 is a schematic diagram of deployment according to Embodiment 3 of the present invention. The present embodiment will be described with reference to FIG. 9 as follows:

As shown in FIG. 9, the primary (macro) base station MeNB and the secondary (micro) base station SeNB are connected through an X2 interface, and the MeNB and the SeNB are connected to respective independent WT or AP nodes through the Xw interface, and the MeNB and the SeNB, the WT or the AP are both connected. Support related DC working mode and LWA working mode;

The UE is already in the RRC connected state at a moment, and is under good coverage of the signal of the potential target MCG serving cell (a group of cells subordinate to the MeNB), the SCG serving cell (a group of cells subordinate to the SeNB), and the SCG side WT or AP. The signal coverage of the WT or AP on the MCG side is poor; the UE supports the related DC mode and LWA mode operation;

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

When the user initiates the file upload service, the serving MeNB needs to select to establish or reconfigure the first service bearer DRB (1) for the UE;

The MeNB learns that the UE is currently under the good coverage of the target MCG serving cell, the target SCG serving cell, and the target SCG side WT or AP according to the RRM measurement reported by the UE through the RRC Measurement Report message. In addition, the MeNB passes The X2 interface interaction message is that the target MCG and the SCG serving cell are at the same load at the moment. The Xw+X2 interface exchange message indicates that the target SCG side WT or AP is relatively light at the moment. Therefore, it is determined that the DRB(1) type is the SCG side. LWA Bearer (can be configured as LWA Switched Bearer in Figure 4(b));

When the user then initiates the VOLTE (Voice over LTE) voice service, the serving MeNB needs to select to establish or reconfigure the second service bearer DRB (2) for the UE; at this time, assume that the network signal coverage and/or service the UE is located on. The node load status does not change. According to the pre-configured constraint rules, the MeNB can select one of the types configured for the DRB (2): MCG Bearer, SCG Bearer, and SCG side LWA Bearer; the MeNB combines the RRM algorithm input conditions, and finally Determine DRB(2) The type is MCG Bearer. The MCG Link in Figure 9 runs the SRB radio bearer and the DRB (2), and the SCG side WLAN Link runs the DRB (1).

As time changes, the network coverage environment and/or service node load status of the UE is also changing. Therefore, the MeNB may need to reconfigure the established DRB(1) and DRB(2) types, such as DRB ( 1) Re-arranged into SCG Bearer, re-arranged DRB (2) into LWA Switched Bearer in Figure 4 (b) on the MCG side.

In addition, if the user initiates more data services during the period, the MeNB needs to establish more DRB(i) for the UE, and any new or reconfigured DRB(i) type must be configured according to the above constraint rules and all configured. The DRBs configuration type of the established or reconfigured coexistence. If any of the newly created or reconfigured DRB(i) types cannot coexist with all the DRBs configuration types that have been configured or reconfigured according to the above constraint rules, DRB(i) must be reselected. Type, or, type reconfiguration of already configured DRBs. Here, DRB(i) represents the i-th DRB, where i is an integer greater than or equal to 1.

The embodiment of the invention further provides a computer storage medium, wherein the computer storage medium stores computer executable instructions, and the computer executable instructions are used to execute the above method.

In addition, the embodiment of the present invention further provides a device for configuring a radio bearer, which is applied to the network side, as shown in FIG. 10, and includes: a configuration module configured to configure a constraint rule of a DRB type; and a processing module configured to be according to the constraint The rule and the preset policy determine the type of the DRB that the terminal UE needs to configure.

Optionally, the processing module is configured to determine, according to the constraint rule and the preset policy, a type of the DRB that the terminal UE needs to configure, including: managing RRM measurement result according to the radio resource of the UE, and corresponding input parameter And selecting a DRB type that satisfies the constraint rule among the DRB types determined by the RRM algorithm, and determining the type of the DRB that the UE needs to be configured.

Optionally, the constraint rule includes:

Different DRB type constraints;

Any newly created or reconfigured DRB type meets all of the already configured DRB types. Bundle terms.

Optionally, the constraint clause includes at least one of the following:

Optionally, the constraint clause includes: the following two DRB types cannot be configured to coexist in the same base station and/or the UE: Split Bearer, LWA Bearer.

Optionally, the constraint clause includes at least one of the following:

The constraint cannot support the configuration of the following DRB types: Split Bearer, and SCG in Split Bearer Partially diverted to the WT;

The specific processing flow of the above device is the same as that described above, and thus will not be described herein.

One of ordinary skill in the art will appreciate that all or a portion of the steps described above can be accomplished by a program that instructs the associated hardware, 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 also be implemented using one or more integrated circuits. Correspondingly, each module/unit in the foregoing embodiment may be implemented in the form of hardware or in the form of a software function module. The invention is not limited to any specific form of combination of hardware and software.

It should be noted that, in the case of no conflict, the features in the embodiments and the embodiments in the present application may be arbitrarily combined with each other. The above is only the preferred embodiment of the present invention, and is not intended to limit the scope of the invention, and the equivalent structure or equivalent process transformations made by the description of the invention and the drawings are directly or indirectly applied to other related The technical field is equally included in the scope of patent protection of the present invention. The invention may, of course, be embodied in various other embodiments and various modifications and changes can be made in accordance with the present invention without departing from the spirit and scope of the invention. And modifications are intended to fall within the scope of the appended claims.

The basic principles and main features of the present invention and the advantages of the present invention are shown and described above. The present invention is not limited by the above-described embodiments, and the above-described embodiments and the description are merely illustrative of the principles of the present invention, and various changes and modifications may be made without departing from the spirit and scope of the invention. And modifications are intended to fall within the scope of the invention as claimed.

Industrial applicability

The above technical solution can reduce the complexity and burden of data packet processing on the wireless link, thereby reducing the complexity of system-level development and implementation testing on the network side and the UE side and avoiding cost increase.

Claims

A method for configuring a radio bearer includes:

The network side configuration data radio bears the DRB type constraint rule;

The network side determines the type of the DRB that the terminal UE needs to configure according to the constraint rule and the preset policy.
The method of claim 1, wherein the network side determines the type of the DRB that the UE needs to be configured according to the constraint rule and the preset policy, including: the network side manages the RRM according to the radio resource of the UE. The DRB type that meets the constraint rule is selected from the measurement result, the corresponding input parameter, and the DRB type determined by the RRM algorithm, and is determined as the type of the DRB that the UE needs to be configured.
The method of claim 1 wherein said constraint rules comprise:

Different DRB type constraints;

Any new or reconfigured DRB type and all configured DRB types satisfy the constraint terms.
The method according to claim 3, wherein the constraint rule further comprises: when there is a newly created or reconfigured DRB type that cannot satisfy the constraint clause, performing type reconfiguration on all configured DRBs until any one of the new or The reconfigured DRB type satisfies the constraint terms with all configured DRB types.
The method of claim 3 or 4, wherein the constraint clause comprises at least one of the following:

Avoiding the complexity of the PDCP packet processing of the packet data convergence protocol of the DRB belonging to the base station and/or the UE exceeding the constraint of the processing capability of the system;

Avoiding the constraint that the processing burden of the base station and/or UE exceeds the system cost;

Avoiding different types of multiple DRB coexistence results in air interface radio resource efficiency being lower than the network operator and/or user communication experience expected constraints.
The method of claim 5, the constraint clause further comprising: constraining the following two types of DRBs to fail to configure coexistence within the same base station and/or UE: in a Long Term Evolution (LTE) dual connectivity configuration Split Split Bearer, Long Term Evolution and Wireless LAN Aggregation LWA Bearer.
The method of claim 5, the constraint clause further comprising at least one of the following:

When the following DRB types have been configured: the primary cell set MCG bearers Bearer, and does not offload to the wireless local area network node WT or the secondary base station SeNB, the DRB type that can coexist with the DRB type has no constraint;

When the following DRB types are configured: the MCG side long-term evolution and the WLAN aggregation LWA Bearer, and only the WT is offloaded, the DRB type cannot be coexisted with the following DRB types: split Split Bearer, secondary cell set SCG side LWA Bearer;

When the following DRB type is configured: SCG Bearer, and the WT or the primary base station MeNB is not offloaded, the DRB type cannot be coexisted with the following DRB types: Split Bearer;

The DRB type cannot be coexisted with the following DRB types: Split Bearer, MCG side LWA Bearer, when the DRB type is configured on the SCG side, and only the WT is offloaded to the WT.

When the following DRB types are configured: Split Bearer, and the traffic is not offloaded to the WT, the DRB type cannot be coexisted with the following DRB types: SCG Bearer, LSG Bearer on the MCG side, and LWA Bearer on the SCG side.

The constraint cannot support the configuration of the following DRB type: Split Bearer, and the MCG part in the Split Bearer is offloaded to the WT;

The constraint cannot support the configuration of the following DRB type: Split Bearer, and the SCG part in the Split Bearer is offloaded to the WT;

The constraint cannot support the following DRB types: Split Bearer, and the MCG and SCG parts in the Split Bearer are offloaded to the WT.
A radio bearer configuration device is applied to the network side, and includes:

The configuration module is configured to configure a data radio bearer DRB type constraint rule;

The processing module is configured to determine, according to the constraint rule and the preset policy, a type of the DRB that the terminal UE needs to configure.
The device according to claim 8, wherein the processing module is configured to determine, according to the constraint rule and the preset policy, that the DRB of the terminal UE needs to be configured according to the following manner Type: The DRB type that satisfies the constraint rule is selected from the radio resource management RRM measurement result of the UE, the corresponding input parameter, and the DRB type determined by the RRM algorithm, and is determined as the type of the DRB that the UE needs to be configured.
The apparatus of claim 8 wherein said constraint rules comprise:

Different DRB type constraints;

Any new or reconfigured DRB type and all configured DRB types satisfy the constraint terms.
The apparatus according to claim 10, wherein the constraint rule further comprises: when there is a newly created or reconfigured DRB type that cannot satisfy the constraint clause, performing type reconfiguration on all configured DRBs until any one of the new or The type of reconfiguration DRB and all already configured DRB types satisfy the constraint terms.
The apparatus of claim 10 or 11, wherein the constraint clause comprises at least one of the following:

The complexity of avoiding the PDCP packet processing of the DRB by the base station and/or the UE exceeds the constraint of the processing capability of the system;

Avoiding the constraint that the processing burden of the base station and/or UE exceeds the system cost;

Avoiding the coexistence of different types of multiple DRBs results in air interface radio resource efficiency being lower than the network operator and/or user communication experience expected constraints.
The apparatus according to claim 12, wherein the constraint clause further comprises: restricting the following two DRB types from being coexistible in the same base station and/or the UE: splitting the split bearer Bearer, long term evolution, and the long term evolution LTE dual connectivity configuration Wireless LAN aggregates LWA Bearer.
The apparatus of claim 12, the constraint clause further comprising at least one of the following:

When the following DRB types are configured: the MCG bears the Bearer and does not offload to the WT or the SeNB, the DRB type that can coexist with the DRB type has no constraint;

When the following DRB types are configured: the MCG side long-term evolution and the WLAN aggregation LWA Bearer, and only the WT is offloaded, the DRB type cannot be coexisted with the following DRB types: split Split Bearer, SCG side LWA Bearer;

When the following DRB type is configured: SCG Bearer, and the WT or MeNB is not offloaded, the DRB type cannot be coexisted with the following DRB types: Split Bearer;

The DRB type cannot be coexisted with the following DRB types: Split Bearer, MCG side LWA Bearer, when the DRB type is configured on the SCG side, and only the WT is offloaded to the WT.

When the following DRB types are configured: Split Bearer, and the traffic is not offloaded to the WT, the DRB type cannot be coexisted with the following DRB types: SCG Bearer, LSG Bearer on the MCG side, and LWA Bearer on the SCG side.

The constraint cannot support the configuration of the following DRB type: Split Bearer, and the MCG part in the Split Bearer is offloaded to the WT;

The constraint cannot support the configuration of the following DRB type: Split Bearer, and the SCG part in the Split Bearer is offloaded to the WT;

The constraint cannot support the following DRB types: Split Bearer, and the MCG and SCG parts in the Split Bearer are offloaded to the WT.