WO2015062873A2

WO2015062873A2 - A method and apparatus for uplink prioritization using dual connectivity

Info

Publication number: WO2015062873A2
Application number: PCT/EP2014/072228
Authority: WO
Inventors: Benoist Pierre Sebire; Chunli Wu
Original assignee: Nokia Solutions And Networks Oy
Priority date: 2013-11-01
Filing date: 2014-10-16
Publication date: 2015-05-07
Also published as: WO2015062873A3

Abstract

A method and apparatus may be configured to make a communications connection, using dual connectivity, to a first network node and to a second network node. The method may also comprise maintaining a variable corresponding to a common bucket. The common bucket is used for both a first entity corresponding to the first network node and a second entity corresponding to the second network node.

Description

DESCRIPTION TITLE

A METHOD AND APPARATUS FOR UPLINK PRIORITIZATION USING DUAL

CONNECTIVITY

BACKGROUND:

Field:

[0001] Embodiments of the invention relate to uplink prioritization using dual connectivity. Description of the Related Art:

[0002] In the following, different exemplifying embodiments will be described using, as an example of an access architecture to which the embodiments may be applied, a radio access architecture based on long term evolution advanced (LTE Advanced, LTE- A).

[0003] Long-term Evolution (LTE) is a standard for wireless communication that seeks to provide improved speed and capacity for wireless communications by using new modulation/signal processing techniques. The standard was proposed by the 3 rd Generation Partnership Project (3GPP), and is based upon previous network technologies. Since its inception, LTE has seen extensive deployment in a wide variety of contexts involving the communication of data.

SUMMARY:

[0004] According to a first embodiment, a method may comprise making a communications connection, by a user equipment, using dual connectivity, to a first network node and to a second network node. The method may also comprise maintaining a variable corresponding to a common bucket. The common bucket is used for both a first entity corresponding to the first network node and a second entity corresponding to the second network node.

[0005] In the method of the first embodiment, the maintaining comprises maintaining the variable while the user equipment may be using a split bearer in dual-connectivity. [0006] In the method of the first embodiment, the first entity is a medium-access-control entity corresponding to a first evolved Node B and the second entity is a medium-access-control entity corresponding to a second evolved Node B.

[0007] In the method of the first embodiment, the first network node may be a master evolved Node B, and the second network node may be a secondary evolved Node B.

[0008] In the method of the first embodiment, the variable may be initialized to zero only by the first entity.

[0009] In the method of the first embodiment, the split bearer may be a bearer that uses radio resources on both the first network node and the second network node.

[0010] In the method of the first embodiment, the common bucket may be used in uplink logical channel prioritization.

[0011] In the method of the first embodiment, the variable is incremented only by the first entity.

[0012] According to a second embodiment, an apparatus may comprise at least one processor. The apparatus may also comprise at least one memory including computer program code. The at least one memory and the computer program code may be configured, with the at least one processor, to cause the apparatus at least to make a communications connection, using dual connectivity, to a first network node and to a second network node. The apparatus may also maintain a variable corresponding to a common bucket. The common bucket is used for both a first entity corresponding to the first network node and a second entity corresponding to the second network node.

[0013] In the apparatus of the second embodiment, the maintaining comprises maintaining the variable while the user equipment may be using a split bearer in dual-connectivity.

[0014] In the apparatus of the second embodiment, the first entity is a medium-access-control entity corresponding to a first evolved Node B and the second entity is a medium-access-control entity corresponding to a second evolved Node B.

[0015] In the apparatus of the second embodiment, the first network node may be a master evolved Node B, and the second network node may be a secondary evolved Node B.

[0016] In the apparatus of the second embodiment, the variable may be initialized to zero only by the first entity. [0017] In the apparatus of the second embodiment, the split bearer may be a bearer that uses radio resources on both the first network node and the second network node.

[0018] In the apparatus of the second embodiment, the common bucket may be used in uplink logical channel prioritization.

[0019] In the apparatus of the second embodiment, the variable is incremented only by the first entity.

[0020] According to a third embodiment, a computer program product may be embodied on a non-transitory computer readable medium. The computer program product may be configured to control a processor to perform a process including making a communications connection, using dual connectivity, to a first network node and to a second network node. The process may also comprise maintaining a variable corresponding to a common bucket. The common bucket is used for both a first entity corresponding to the first network node and a second entity corresponding to the second network node.

[0021] In the computer program product of the third embodiment, the maintaining comprises maintaining the variable while the user equipment may be using a split bearer in dual- connectivity.

[0022] In the computer program product of the third embodiment, the first entity is a medium- access-control entity corresponding to a first evolved Node B and the second entity is a medium- access-control entity corresponding to a second evolved Node B.

[0023] In the computer program product of the third embodiment, the first network node may be a master evolved Node B, and the second network node may be a secondary evolved Node B.

[0024] In the computer program product of the third embodiment, the variable may be initialized to zero only by the first entity.

[0025] In the computer program product of the third embodiment, the split bearer may be a bearer that uses radio resources on both the first network node and the second network node.

[0026] In the computer program product of the third embodiment, the common bucket may be used in uplink logical channel prioritization. [0027] In the computer program product of the third embodiment, the variable is incremented only by the first entity.

[0028] According to a fourth embodiment, a method may comprise making a communications connection, by an evolved Node B, to a user equipment. The method may also comprise ensuring that a prioritized bit rate is the same across two logical channels. The method may also comprise ensuring that a bucket size duration is the same across the two logical channels.

[0029] According to a fifth embodiment, an apparatus may comprise at least one processor. The apparatus may comprise at least one memory including computer program code. The at least one memory and the computer program code may be configured, with the at least one processor, to cause the apparatus at least to make a communications connection to a user equipment. The apparatus may be caused to ensure that a prioritized bit rate is the same across two logical channels. The apparatus may also be caused to ensure that a bucket size duration is the same across the two logical channels.

[0030] According to a sixth embodiment, a computer program product may be embodied on a non-transitory computer readable medium. The computer program product may be configured to control a processor to perform a process including making a communications connection to a user equipment. The process may also comprise ensuring that a prioritized bit rate is the same across two logical channels. The process may also comprise ensuring that a bucket size duration is the same across the two logical channels.

[0031] According to a seventh embodiment, an apparatus may comprise making means for making a communications connection, using dual connectivity, to a first network node and to a second network node. The apparatus may also comprise maintaining means for maintaining a variable corresponding to a common bucket. The common bucket may be used for both a first entity corresponding to the first network node and a second entity corresponding to the second network node.

[0032] In the apparatus of the seventh embodiment, the maintaining means maintains the variable while the user equipment may be using a split bearer in dual-connectivity.

[0033] In the apparatus of the seventh embodiment, the first entity may be a medium-access- control entity corresponding to a first evolved Node B and the second entity may be a medium- access-control entity corresponding to a second evolved Node B. [0034] In the apparatus of the seventh embodiment, the first network node may be a master evolved Node B, and the second network node may be a secondary evolved Node B.

[0035] In the apparatus of the seventh embodiment, the variable may be initialized to zero only by the first entity.

[0036] In the apparatus of the seventh embodiment, the split bearer may be a bearer that uses radio resources on both the first network node and the second network node.

[0037] In the apparatus of the seventh embodiment, the common bucket may be used in uplink logical channel prioritization.

[0038] In the apparatus of the seventh embodiment, the variable is incremented only by the first entity.

[0039] According to an eighth embodiment, an apparatus comprises making means for making a communications connection to a user equipment. The apparatus may also comprise first ensuring means for ensuring that a prioritized bit rate may be the same across two logical channels. The apparatus may also comprise second ensuring means for ensuring that a bucket size duration may be the same across the two logical channels.

BRIEF DESCRIPTION OF THE DRAWINGS:

[0040] For proper understanding of embodiments of the invention, reference should be made to the accompanying drawings, wherein:

[0041] Fig. 1 illustrates examples of two user plane alternatives.

[0042] Fig. 2 illustrates an exemplifying flowchart of a method in accordance with embodiments of the invention.

[0043] Fig. 3 illustrates an exemplifying flowchart of a method in accordance with embodiments of the invention.

[0044] Fig. 4 illustrates an example of an apparatus in accordance with embodiments of the invention.

[0045] Fig. 5 illustrates an example of an apparatus in accordance with embodiments of the invention. [0046] Fig. 6 illustrates an example of an apparatus in accordance with embodiments of the invention.

[0047] Fig. 7 illustrates an example of an apparatus in accordance with embodiments of the invention.

[0048] Fig. 8 illustrates an example of an apparatus in accordance with embodiments of the invention.

DETAILED DESCRIPTION:

[0049] The following embodiments are only examples. Although the specification may refer to "an", "one", or "some" embodiment(s) in several locations, this does not necessarily mean that each such reference is to the same embodiment(s), or that the feature only applies to a single embodiment. Single features of different embodiments may also be combined to provide other embodiments. Furthermore, words "comprising" and "including" should be understood as not limiting the described embodiments to consist of only those features that have been mentioned and such embodiments may also contain also features, structures, units, modules, etc. that have not been specifically mentioned. Technical specifications cited herein should only be taken as examples giving further clarifications, not as limiting the implementation of embodiments.

[0050] In LTE, a radio bearer may act as a service access point when using Packet Data Convergence Protocol (PDCP), and a logical channel may act as a service access point when using Medium Access Control (MAC) protocol (See Technical Specification 36.300). There is generally a one-to-one mapping between the radio bearer and the logical channel to maintain one data path when processing packets through the sublayers of layer 2. In order to control how the user equipment (UE) fulfills uplink grants that the UE receives from a base station and/or an evolved Node B (eNB), a PBR (Prioritized Bit Rate) may be configured per bearer/per logical channel.

[0051] The PBR may ensure that high-priority logical channels (LCHs) are scheduled first, while also scheduling the lower priority channels after the high-priority LCHs are scheduled. In other words, the PBR may guarantee that the quality-of-service (QoS) that a bearer experiences in uplink will be satisfactory. The PBR may be used by Token Bucket mechanisms in Logical Channel Prioritization (LCP) in MAC (See Technical Specification 36.321). [0052] Small cell enhancements are being considered for 3GPP Release 12. In order to decrease a signaling load experienced by a core network as well as to benefit from flexible- resource usage across eNBs, dual connectivity is being considered. In dual connectivity, a UE simultaneously makes a communications connection to both a Master eNB (MeNB) and a Secondary eNB (SeNB). The MeNB and the SeNB may be connected via a backhaul link that may be an Xn interface. One property of an Xn interface is that the Xn interface may be a non- ideal backhaul link. Transmission delays in the range of approximately 20 ms may occur, and the bit rate may be limited.

[0053] Different alternatives of using user planes and control planes for supporting dual connectivity may be found in 3GPP Technical Report 36.842. As described above, a common characteristic of dual connectivity is that two eNBs are involved. As described above, the two eNBs may be a Master eNB (MeNB) and a Secondary eNB (SeNB).

[0054] Fig. 1 illustrates examples of two user plane alternatives. The options/alternatives to be used may be determined based on whether they allow bearer splitting. A bearer split refers to the ability to split a bearer over multiple eNBs. Splitting a bearer may mean sharing usage of bearer resources. Among all user plane alternatives that have been considered, two user planes were recently agreed upon for further work. These two user plane alternatives are referred to as 1A and as 3C, as illustrated in Fig. 1, and as described below.

[0055] With regard to Alternative 3C, two logical channels may be used for the split radio bearer. One logical channel may be for a Master eNB (MeNB) and another logical channel may be for a Secondary eNB (SeNB). These two logical channels may correspond to two separate MAC entities (one in MeNB and another in SeNB), and therefore be granted resources through two separate Logical Channel Prioritization (LCP) procedures, which processes grants from the two different eNBs. Because the one-to-one mapping between the logical channel and the radio bearer no longer exists, the two LCP procedures together may no longer maintain Quality of Service (QoS) of the bearer.

[0056] According to previous approaches, logical channel prioritization may be specified per a logical channel, i.e., per bearer due to the one-to-one mapping. Referring to Technical Specification 36.321:

5.4.3.1 Logical channel prioritization The Logical Channel Prioritization procedure is applied when a new transmission is performed.

RRC controls the scheduling of uplink data by signalling for each logical channel: priority where an increasing priority value indicates a lower priority level,

prioritisedBitRate which sets the Prioritized Bit Rate (PBR), bucketSizeDuration which sets the Bucket Size Duration (BSD).

The UE shall maintain a variable Bj for each logical channel j. Bj shall be initialized to zero when the related logical channel is established, and incremented by the product PBR x TTI duration for each TTI, where PBR is Prioritized Bit Rate of logical channel j. However, the value of Bj can never exceed the bucket size and if the value of Bj is larger than the bucket size of logical channel j, it shall be set to the bucket size. The bucket size of a logical channel is equal to PBR x BSD, where PBR and BSD are configured by upper layers.

The UE shall perform the following Logical Channel Prioritization procedure when a new transmission is performed:

The UE shall allocate resources to the logical channels in the following steps:

Step 1 : All the logical channels with B j > 0 are allocated resources in a decreasing priority order. If the PBR of a radio bearer is set to "infinity", the UE shall allocate resources for all the data that is available for transmission on the radio bearer before meeting the PBR of the lower priority radio bearer(s);

Step 2: the UE shall decrement Bj by the total size of MAC SDUs served to logical channel j in Step 1

NOTE: The value of Bj can be negative.

Step 3: if any resources remain, all the logical channels are served in a strict decreasing priority order (regardless of the value of Bj) until either the data for that logical channel or the UL grant is exhausted, whichever comes first. Logical channels configured with equal priority should be served equally.

[0057] Referring to Technical Specification 36.331:

DRB-ToAddMod ::= SEQUENCE { eps-Bearerldentity INTEGER (0..15)

OPTIONAL, - Cond DRB-Setup

drb-Identity DRB -Identity,

pdcp-Config PDCP-Config

OPTIONAL, - Cond PDCP

rlc-Config RLC-Config

OPTIONAL, - Cond Setup

logicalChannelldentity INTEGER (3..10)

OPTIONAL, - Cond DRB-Setup

logicalChannelConfig LogicalChannelConfig OPTIONAL, - Cond Setup

LogicalChannelConfig ::= SEQUENCE {

ul-SpecificParameters SEQUENCE {

priority INTEGER

(1- 16),

prioritisedBitRate ENUMERATED { kBpsO, kBps8, kBpsl6, kBps32, kBps64, kBpsl28, kBps256, infinity, kBps512-vl020, kBpsl024-vl020, kBps2048-vl020, spare5, spare4, spare3, spare2, sparel },

buckets izeDuration ENUMERATED { ms50, mslOO, msl50, ms300, ms500, mslOOO, spare2, sparel },

logic alChannelGroup INTEGER (0..3) OPTIONAL Need OR

} OPTIONAL,

Cond UL

[[ logicalChannelSR-Mask-r9 ENUMERATED { setup }

OPTIONAL — Cond SRmask

]]

} It should be appreciated that these technical specifications are presented herein for clarification purposes. They should not be taken as limiting features.

[0058] Without further modification, the previous approaches are generally not applicable to bearer splitting. A split bearer may mean a radio bearer that uses radio resources provided by both nodes, e.g., a MeNB and a SeNB. In order to maintain or provide (a predefined) QoS of a split bearer in dual connectivity, embodiments of the present invention may use a common bucket in the two network entities, such as media access control (MAC) entities involved. In other words, for a split bearer, one common bucket (Bj) may be used for the MAC entity corresponding to the MeNB and for the MAC entity corresponding to the SeNB. A bucket may also be considered to be a storage device.

[0059] Embodiments described herein are applicable to any user device or user equipment (UE), such as a user terminal, as well as to any network element, relay node, server, node, host, corresponding component, and/or to any communication system or any combination of different communication systems that support required functionalities.

[0060] The user device typically refers to a portable computing device that comprises wireless mobile communication devices operating with or without a subscriber identification module (SIM), including, but not limited to, the following types of devices: a mobile station (mobile phone), smartphone, personal digital assistant (PDA), handset, device using a wireless modem (alarm or measurement device, etc.), laptop and/or touch screen computer, tablet, game console, notebook, and multimedia device. It should be appreciated that a user device may also be a nearly exclusive uplink only device, of which an example is a camera or video camera loading images or video clips to a network.

[0061] In one embodiment of the present invention, only the MAC entity corresponding to the MeNB may initialize a variable Bj (corresponding to the common bucket) to 0. Adding and removing SeNBs should not initialize the variable Bj to zero for split bearers. In one embodiment of the present invention, incrementing the variable Bj may be done by one MAC entity.

[0062] Depending on how Radio-Resource-Control (RRC) signalling is implemented, in embodiments of the present invention, for a split bearer, a UE may ignore a PBR (as indicated by prioritisedBitRate, for example) and a bucket-size duration (as indicated by bucketSizeDuration, for example) of the MAC entity corresponding to the SeNB. Alternatively, if prioritisedBitRate and bucketSizeDuration are configured for both logical channels of the same bearer, an eNB may ensure that (1) the prioritisedBitRate is the same across both logical channels, and (2) the bucketSizeDuration is the same across both logical channels.

[0063] In view of the above, embodiments of the present invention are suitable for maintaining QoS for split bearers.

[0064] Fig. 2 illustrates an exemplifying flowchart of a method in accordance with embodiments of the invention. The method illustrated in Fig. 2 comprises, at 200, making a communications connection, using dual connectivity, to a first network node and to a second network node. The method, at 201, comprises maintaining a variable corresponding to a common bucket. The common bucket is used for both a first entity corresponding to the first network node and a second entity corresponding to the second network node.

[0065] Fig. 3 illustrates an exemplifying flowchart of a method in accordance with embodiments of the invention. The method illustrated in Fig. 3 comprises, at 300, making a communications connection, by an evolved Node B, to a user equipment. The method, at 301, comprises ensuring that a prioritized bit rate is the same across two logical channels. The method, at 302, comprises ensuring that a bucket size duration is the same across the two logical channels.

[0066] Fig. 4 illustrates an example of an apparatus in accordance with embodiments of the invention. In one embodiment, the apparatus may be a user device. In another embodiment, the apparatus may be an eNB/base station/node, host or server. Apparatus 10 may comprise a processor 22 for processing information and executing instructions or operations. Processor 22 may be any type of general or specific purpose processor. While a single processor 22 is shown in Fig. 4, multiple processors may be utilized according to other embodiments. Processor 22 may also comprise one or more of general-purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs), field-programmable gate arrays (FPGAs), application- specific integrated circuits (ASICs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), processors, controllers, micro-controllers, digitally enhanced circuits, single-chip computer elements, chipsets, other electronic units designed to perform the functions described herein or processors based on a multi-core processor architecture, as examples, or any combination thereof.

[0067] Apparatus 10 may further comprise at least one external and/or internal memory 14, coupled to processor 22, for storing information and instructions that may be executed by processor 22. Memory 14 may be one or more memories and of any type suitable to the local application environment, and may be implemented using any suitable volatile or nonvolatile data storage technology such as a semiconductor-based memory device, a magnetic memory device and system, an optical memory device and system, fixed memory, and removable memory. For example, memory 14 comprises any combination of random access memory (RAM), read only memory (ROM), static storage such as a magnetic or optical disk, or any other type of non-transitory machine or computer readable media. The instructions stored in memory 14 may comprise program instructions or computer program code that, when executed by processor 22, enable the apparatus 10 to perform tasks as described herein.

[0068] Apparatus 10 may also comprise one or more antennas (not shown) or being coupled to a remote radio head for transmitting and/or receiving signals and/or data to and from apparatus 10. Apparatus 10 may further comprise or being coupled to a transceiver 28 that modulates information on to a carrier waveform for transmission by the antenna(s) and demodulates information received via the antenna(s) for further processing by other elements of apparatus 10. In other embodiments, transceiver 28 may be capable of transmitting and receiving signals or data directly.

[0069] Processor 22 may perform functions associated with the operation of apparatus 10 including, without limitation, precoding of antenna gain/phase parameters, encoding and decoding of individual bits forming a communication message, formatting of information, and overall control of the apparatus 10, including processes related to management of communication resources. In an embodiment, memory 14 may store software modules that provide functionality when executed by processor 22. The modules may comprise an operating system 15 that provides operating system functionality for apparatus 10. The memory may also store one or more functional modules 18, such as an application or program, to provide additional functionality for apparatus 10. The components of apparatus 10 may be implemented in hardware, or as any suitable combination of hardware and software.

[0070] The apparatus may be, comprise or be associated with at least one software application, module, unit or entity configured as arithmetic operation, or as a program (including an added or updated software routine), executed by at least one operation processor. Programs, also called program products or computer programs, including software routines, applets and macros, may be stored in any apparatus-readable data storage medium and they comprise program instructions to perform particular tasks. A computer program product may comprise one or more computer-executable components which, when the program is run, are configured to carry out embodiments. Functionality of each embodiment may be performed as at least one routine, which may be implemented as added or updated software routine(s) downloadable into an apparatus.

[0071] Embodiments provide computer programs embodied on a distribution medium, comprising program instructions which, when loaded into apparatuses, constitute the apparatuses as explained above. The distribution medium may be a non-transitory medium.

[0072] Fig. 5 illustrates an example of an apparatus in accordance with another embodiment. Apparatus 500 may be a user equipment or user device, for example. Apparatus 500 may comprise a making unit 501 that makes a communications connection, using dual connectivity, to a first network node and to a second network node. Apparatus 500 may also comprise a maintaining unit 502 that maintains a variable corresponding to a common bucket. The common bucket is used for both a first entity corresponding to the first network node and a second entity corresponding to the second network node.

[0073] Fig. 6 illustrates an example of an apparatus in accordance with another embodiment. Apparatus 600 may be an eNB/base station/node, host or server, for example. Apparatus 600 may comprise a making unit 601 that makes a communications connection to a user equipment. Apparatus 600 may also comprise a first ensuring unit 602 that ensures that a prioritized bit rate is the same across two logical channels. Apparatus 600 may also comprise a second ensuring unit 603 that ensures that a bucket size duration is the same across the two logical channels.

[0074] Fig. 7 illustrates an example of an apparatus in accordance with embodiments of the invention. Apparatus 700 may be a user equipment or user device, for example. Apparatus 700 may comprise making means 701 for making a communications connection, using dual connectivity, to a first network node and to a second network node. Apparatus 700 may also comprise maintaining means 702 for maintaining a variable corresponding to a common bucket. The common bucket may be used for both a first entity corresponding to the first network node and a second entity corresponding to the second network node.

[0075] Fig. 8 illustrates an example of an apparatus in accordance with embodiments of the invention. Apparatus 800 may be an eNB/base station/node, host or server, for example. Apparatus 800 may comprise making means 801 for making a communications connection to a user equipment. Apparatus 800 may also comprise first ensuring means 802 for ensuring that a prioritized bit rate is the same across two logical channels. Apparatus 800 may also comprise second ensuring means 803 for ensuring that a bucket size duration is the same across the two logical channels.

[0076] The described features, advantages, and characteristics of the invention may be combined in any suitable manner in one or more embodiments. One skilled in the relevant art will recognize that the invention may be practiced without one or more of the specific features or advantages of a particular embodiment. In other instances, additional features and advantages may be recognized in certain embodiments that may not be present in all embodiments of the invention. One having ordinary skill in the art will readily understand that the invention as discussed above may be practiced with steps in a different order, and/or with hardware elements in configurations which are different than those which are disclosed. Therefore, although the invention has been described based upon these preferred embodiments, it would be apparent to those of skill in the art that certain modifications, variations, and alternative constructions would be apparent, while remaining within the spirit and scope of the invention.

Claims

WE CLAIM:

1. A method, comprising:

making a communications connection, by a user equipment, using dual connectivity, to a first network node and to a second network node; and

maintaining a variable corresponding to a common bucket, wherein the common bucket is used for both a first entity corresponding to the first network node and a second entity corresponding to the second network node.

2. The method according to claim 1, wherein the maintaining comprises maintaining the variable while the user equipment is using a split bearer in dual-connectivity.

3. The method according to claim 1, wherein the first entity is a medium-access-control entity corresponding to a first evolved Node B and the second entity is a medium-access-control entity corresponding to a second evolved Node B.

4. The method according to claim 1, wherein the first network node is a master evolved Node B, and the second network node is a secondary evolved Node B.

5. The method according to claim 1, wherein the variable can be initialized to zero only by the first entity.

6. The method according to claim 1, wherein the split bearer may be a bearer that uses radio resources on both the first network node and the second network node.

7. The method according to claim 1, wherein the common bucket may be used in uplink logical channel prioritization.

8. The method according to claim 1, wherein the variable is incremented only by the first entity.

9. An apparatus, comprising: at least one processor; and

at least one memory including computer program code,

the at least one memory and the computer program code configured, with the at least one processor, to cause the apparatus at least to

make a communications connection, using dual connectivity, to a first network node and to a second network node; and

maintain a variable corresponding to a common bucket, wherein the common bucket is used for both a first entity corresponding to the first network node and a second entity corresponding to the second network node.

10. The apparatus according to claim 9, wherein the maintaining comprises maintaining the variable while the user equipment is using a split bearer in dual-connectivity.

11. The apparatus according to claim 9, wherein the first entity is a medium-access- control entity corresponding to a first evolved Node B and the second entity is a medium-access- control entity corresponding to a second evolved Node B.

12. The apparatus according to claim 9, wherein the first network node is a master evolved Node B, and the second network node is a secondary evolved Node B.

13. The apparatus according to claim 9, wherein the variable can be initialized to zero only by the first entity.

14. The apparatus according to claim 9, wherein the split bearer may be a bearer that uses radio resources on both the first network node and the second network node.

15. The apparatus according to claim 9, wherein the common bucket may be used in uplink logical channel prioritization.

16. The apparatus according to claim 9, wherein the variable is incremented only by the first entity.

17. A computer program product, embodied on a non-transitory computer readable medium, the computer program product configured to control a processor to perform a process, comprising:

making a communications connection, using dual connectivity, to a first network node and to a second network node; and

18. The computer program product according to claim 17, wherein the maintaining comprises maintaining the variable while the user equipment is using a split bearer in dual- connectivity.

19. The computer program product according to claim 17, wherein the first entity is a medium-access-control entity corresponding to a first evolved Node B and the second entity is a medium-access-control entity corresponding to a second evolved Node B.

20. The computer program product according to claim 17, wherein the first network node is a master evolved Node B, and the second network node is a secondary evolved Node B.

21. The computer program product according to claim 17, wherein the variable can be initialized to zero only by the first entity.

22. The computer program product according to claim 17, wherein the split bearer may be a bearer that uses radio resources on both the first network node and the second network node.

23. The computer program product according to claim 17, wherein the common bucket may be used in uplink logical channel prioritization.

24. The computer program product according to claim 17, wherein the variable is incremented only by the first entity.

25. A method, comprising:

making a communications connection, by an evolved Node B, to a user equipment; ensuring that a prioritized bit rate is the same across two logical channels; and ensuring that a bucket size duration is the same across the two logical channels.

26. An apparatus, comprising:

at least one processor; and

at least one memory including computer program code,

make a communications connection to a user equipment;

ensure that a prioritized bit rate is the same across two logical channels; and

ensure that a bucket size duration is the same across two logical channels.

27. A computer program product, embodied on a non-transitory computer readable medium, the computer program product configured to control a processor to perform a process, comprising:

making a communications connection to a user equipment;

ensuring that a prioritized bit rate is the same across two logical channels; and ensuring that a bucket size duration is the same across the two logical channels.

28. An apparatus, comprising:

making means for making a communications connection, using dual connectivity, to a first network node and to a second network node; and

maintaining means for maintaining a variable corresponding to a common bucket, wherein the common bucket is used for both a first entity corresponding to the first network node and a second entity corresponding to the second network node.

29. The apparatus according to claim 28, wherein the maintaining means maintains the variable while the user equipment is using a split bearer in dual-connectivity.

30. The apparatus according to claim 28, wherein the first entity is a medium- access- control entity corresponding to a first evolved Node B and the second entity is a medium-access- control entity corresponding to a second evolved Node B.

31. The apparatus according to claim 28, wherein the first network node is a master evolved Node B, and the second network node is a secondary evolved Node B.

32. The apparatus according to claim 28, wherein the variable can be initialized to zero only by the first entity.

33. The apparatus according to claim 28, wherein the split bearer may be a bearer that uses radio resources on both the first network node and the second network node.

34. The apparatus according to claim 28, wherein the common bucket may be used in uplink logical channel prioritization.

35. The apparatus according to claim 28, wherein the variable is incremented only by the first entity.

36. An apparatus, comprising:

making means for making a communications connection to a user equipment;

first ensuring means for ensuring that a prioritized bit rate is the same across two logical channels; and

second ensuring means for ensuring that a bucket size duration is the same across the two logical channels.