CN111345078A

CN111345078A - Wireless communication system and related aspects

Info

Publication number: CN111345078A
Application number: CN201880072305.XA
Authority: CN
Inventors: 奥利维尔·马克
Original assignee: Jiekai Communications Shenzhen Co Ltd
Current assignee: Jiekai Communications Shenzhen Co Ltd
Priority date: 2018-01-11
Filing date: 2018-12-21
Publication date: 2020-06-26
Anticipated expiration: 2038-12-21
Also published as: CN111345078B; GB201800504D0; WO2019137182A1; GB2570134A

Abstract

Methods for triggering a buffer status report in a wireless communication network operating a packet data convergence protocol are disclosed, wherein multiple logical channels are used to provide packet duplication. For example, when a medium access control entity is determined to have new uplink data available for a first logical channel belonging to a logical channel group, if one of the following is determined: a first logical channel with new uplink data has a higher priority than any other logical channel with available uplink data belonging to any logical channel group and wherein the other logical channels are allowed to use at least one serving cell allowed by the first logical channel with new uplink data; or no other logical channel of the at least one serving cell belonging to any logical channel group and allowed to use the first logical channel with new uplink data contains any available uplink data, a buffer status report is triggered.

Description

Wireless communication system and related aspects

Technical Field

Embodiments of the disclosed Technology relate to wireless communication systems and related aspects thereof, and in particular, but not limited to, wireless communication networks, so-called New Radio (NR) or 5G wireless communication networks, and related Network devices and methods for enabling wireless communication between, for example, User Equipment (UE) or mobile devices to Access wireless Network services via a Radio Access Technology (RAT) or a Radio Access Network (RAN). Embodiments of the present invention are particularly, but not exclusively, directed to a new radio wireless communication network implementing 5G Packet Data Convergence Protocol (PDCP) Packet replication.

Background

Wireless communication systems, such as third generation (3G) mobile telephone standards and technologies, are well known. Such 3G standards and techniques have been developed by the Third Generation Partnership Project (3 GPP). Third generation wireless communications have generally been developed to support macro-cell (macro-cell) mobile phone communications. Communication systems and networks have evolved towards wider bandwidth and mobile systems.

The third generation partnership project has developed a so-called Long Term Evolution (LTE) System for Mobile Access networks, i.e. an evolved universal Mobile telecommunications System terrestrial Radio Access Network (E-UTRAN), in which one or more macro cells are supported by base stations called enodebs or enbs (evolved nodebs). Recently, LTE is evolving further towards so-called fifth generation (5G) or NR (new radio) systems, where one or more cells are supported by base stations called gbbs.

In NR, when PDCP Data packet duplication is activated, a PDCP transmitter (transmitter) will create duplicates (duplicates) of PDCP Protocol Data Units (PDUs) and transmit them (transmit) on the duplicated links (Link) or legs (leg), i.e. different Radio Link Control (RLC) entities and associated logical channels (also called "RLC bearers"). The PDCP receiver (receiver) eliminates duplicate packets due to Sequence Number (SN) included in the PDCP PDUs. The use of PCDP packet replication may enhance reliability and reduce Latency (Latency), and thus is suitable for Ultra Reliable Low Latency Communications (URLLC) radio bearers, in which reliability and reduced Latency may be provided.

It may also be used to provide enhanced reliability for Signaling Radio Bearers (SRBs). In addition, PCDP packet replication is also useful for non-URLLC Dedicated Radio Bearers (DRBs), for example, in Handover (HO).

In addition to the initial link or leg, the duplicated link or leg may be configured to be pre-configured (pre-configured) for packet duplication by Radio Resource Control (RRC) at the Radio bearer level. Both associated with the same radio bearer PDCP entity. Packet replication is supported in both the Downlink (DL) and Uplink (UL). For DRBs, Acknowledged Mode (AM) and Unacknowledged Mode (UM) support PDCP packet replication. It is also supported for Dual Connectivity (DC), in which case there is only one branch or link per cell (cell) group, and Carrier Aggregation (CA), in which case each link or branch is mapped onto a different carrier(s). In the Uplink (UL), it can be dynamically activated/deactivated by a Medium Access Control (MAC) Control Element (CE) (a "MAC CE") on a per DRB basis.

Embodiments of the disclosed technology seek to address at least some of the salient problems in the art.

Disclosure of Invention

This summary is provided to introduce a selection of concepts in a simplified form that are further described below in the detailed description. This summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended as an aid in determining the scope of the claimed subject matter.

Some examples of embodiments of the disclosed technology relate to a method of triggering a buffer status report in a wireless communication network operating a packet data convergence protocol, wherein a plurality of logical channels are used to provide data packet duplication, the method comprising:

determining whether a Medium Access Control (MAC) entity has new uplink data available for a first logical channel belonging to a logical channel group;

and if so, if one of the following is determined:

the first logical channel with new uplink data has a higher priority than any other logical channel with available uplink data belonging to any logical channel group and wherein the other logical channel is allowed to use at least one serving cell allowed by the first logical channel with the new uplink data; or

None of the other logical channels belonging to any logical channel group and allowed to use at least one serving cell allowed by the first logical channel with the new uplink data contain any available UL data,

a buffer status report is triggered.

In some examples of embodiments of the disclosed technology, the buffer status report is triggered if one of:

said new UL data belonging to a logical channel having a higher priority than any logical channel with available UL data belonging to any LCG and allowed to use at least all serving cells allowed by said logical channel with new UL data; or

None of the logical channels of all serving cells that belong to an LCG and are allowed to use the logical channel with new UL data contain any available UL data.

In some examples of embodiments of the disclosed technology, the method of triggering the buffer status report is configurable in the wireless communication network through radio resource control.

In some examples of embodiments of the disclosed technology, the radio resource control configures the wireless network to implement a method of triggering the buffer status report, either explicitly when a logical channel or a dedicated radio bearer/packet data convergence protocol is configured in the network, or implicitly when a logical channel is configured to correspond to a duplicated dedicated radio bearer.

In some examples of embodiments of the disclosed technology, the method is implemented only for one or more specific logical channel groups in the wireless communication network.

determining whether a Medium Access Control (MAC) entity has new uplink data available for a logical channel belonging to a logical channel group;

and if so, if one of the following is determined:

the new uplink data belongs to a logical channel having a higher priority than any logical channel belonging to any logical channel group having available uplink data; or

No other logical channel belonging to any logical channel group contains any available uplink data; or

The new uplink data belongs to a logical channel configured for fast buffer status report triggering,

a buffer status report is triggered.

In some examples of embodiments of the disclosed technology, the buffer status reporting trigger is configured by radio resource control on a logical channel based or on a logical channel used by a dedicated radio bearer based.

In some examples of embodiments of the disclosed technology, the step of triggering the buffer status report further requires that the new uplink data belong to a logical channel that does not contain already available data.

Some examples of embodiments of the disclosed technology relate to a wireless network configured to operate using a packet data convergence protocol, wherein a plurality of logical channels are used to provide data packet duplication and the wireless network is capable of activating downlink data packet duplication, the network further comprising means for pre-configuring a reordering timer for use when a downlink duplication is activated as part of the packet data convergence protocol configuration of the wireless network.

In some examples of embodiments of the disclosed technology, the network is configured to: a reordering timer is preconfigured if at least activation and/or deactivation of downlink packet duplication is detected by using a mac ce.

In some examples of embodiments of the disclosed technology, the network is configured to: a reordering timer is preconfigured if activation and/or deactivation of uplink packet duplication is detected by using a mac ce.

In some examples of embodiments of the disclosed technology, the network is configured to: downlink packet replication is considered to be activated whenever uplink activation is detected.

In some examples of embodiments of the disclosed technology, the network is configured by a radio bearer-based radio resource control to: downlink packet replication is considered to be activated whenever uplink activation is detected.

In some examples of embodiments of the disclosed technology, the network is configured to: downlink replication is considered activated if it is determined that data for a radio bearer is also received on a second link after being received on a first link.

In some examples of embodiments of the disclosed technology, the network is configured to: the downlink replication is considered deactivated whenever data of a radio bearer is received on only one link within a predetermined time interval.

In some examples of embodiments of the disclosed technology, the wireless network includes at least one node at which a PDCP entity is located, the at least one node configured to adapt the reordering timer.

In some examples of embodiments of the disclosed technology, packet duplication is activated by a MAC CE from a primary node (MN) or a Secondary Node (SN) of the wireless network, and the receiving PDCP entity is located at the primary or secondary node, and wherein an indication of the decision is transmitted to the other of the primary or secondary node where the PDCP entity is located whenever the primary or secondary node decides to activate and/or deactivate an uplink duplication.

In some examples of embodiments of the disclosed technology, an indication of the decision is communicated to the other of the primary or secondary node where the PDCP entity is located using Xn/X2 signaling so that the node carrying the PCDP entity can adapt the reordering timer.

In some examples of embodiments of the disclosed technology, wherein packet replication is achieved by replicating packets and sending them along different logical channels along at least one or more or all links or legs in the wireless network.

In some examples of embodiments of the disclosed technology, the wireless communication network comprises a Radio Access Network (RAN), e.g., a new radio/5G radio access network.

In some examples of embodiments of the disclosed technology, a base station for use in a wireless network is provided in accordance with an embodiment of a disclosed technology.

Some examples of embodiments of the disclosed technology relate to a non-transitory computer-readable medium having stored thereon computer-readable instructions for execution by a processor to perform any of the methods of embodiments of the disclosed technology.

The non-transitory computer readable medium may include at least one of the group consisting of: hard disks, compact disk Read-Only memories (CD-ROMs), optical storage devices, magnetic storage devices, Read-Only memories (Read Only memories), Programmable Read Only memories (Programmable Read Only memories), Erasable Programmable Read Only Memories (EPROMs), Electrically Erasable Programmable Read Only memories (Electrically Erasable Programmable Read Only memories) and Flash memories (Flash memories).

One or more or all of the features of the embodiments of the disclosed technology described herein or in the appended claims may be combined with one or more or all of the features of other embodiments of the disclosed technology described herein or in the appended claims in any manner apparent to one of ordinary skill in the art.

Drawings

Further details, aspects and embodiments of the invention will be described below, by way of example only, with reference to the accompanying drawings. For simplicity and clarity of illustration, elements in the figures are illustrated and not necessarily drawn to scale. To facilitate understanding, like reference numerals have been used throughout the various figures.

Figure 1 schematically shows how PDCP packet replication with carrier aggregation is configured for a radio bearer;

figure 2A schematically illustrates a radio bearer that is not configured for PDCP packet duplication;

fig. 2B schematically illustrates a radio bearer configured for PDCP packet duplication on two LCHs;

fig. 3 schematically shows how a downlink packet data control protocol (DLPDCP) reordering window is implemented.

Detailed Description

Those skilled in the art will recognize and appreciate that the specifics of the described examples are merely illustrative of some embodiments and that the teachings set forth herein are applicable in a variety of alternative contexts.

Embodiments of the technology disclosed herein relate to addressing issues related to operation of networks proposed by NR/LTE 5G.

Some embodiments of the disclosed technology relate to providing enhanced Buffer Status Report (BSR) operations for replication in Carrier Aggregation (CA) (MAC layer). Although a basic packet replication operation does not require a specific (specific) BSR change in the case of replication in CA, with existing BSR solutions, a BSR may not always be triggered when new data arrives when CA replication is activated, whereas a BSR should be triggered if CA packet replication is not activated. This will reduce the radio bearer delay (latency) when replication is activated, as opposed to one of the intended targets of packet replication. Some embodiments propose a BSR triggering operation that eliminates any degraded performance if packet replication is activated.

Some other embodiments of the disclosed technology relate to providing an enhanced Downlink (DL) Physical Dedicated Control Channel (PDCP) copy operation (PDCP layer). For DL, it is assumed that the Network (NW) can configure and activate/deactivate the duplication operation when needed, without notifying the User Equipment (UE), and without affecting UE PDCP receive operation (since reordering and deduplication have been supported in the NR as part of normal PDCP operation). However, it is likely that a longer reordering timer (timer) is needed to account for the possible delay (delay) between the two branches when DL replication is used. The longer reordering timer should be used only when DL replication is activated, since otherwise it would reduce the RB delay (latency) whenever a PDCP COUNT gap occurs. Some embodiments propose to pre-configure a reordering timer to be used when DL replication is activated. Some embodiments propose several ways of detecting when DL replication is activated.

Enhanced BSR operation for replication in CA (MAC layer)

Consider a 5G new radio Network (NW) in which the NW has pre-configured two Logical Channels (LCHs) by Radio Resource Control (RRC) configuration (one for the initial link or leg and one for the duplicated link or leg) (see fig. 1 for an example of the figure, which schematically shows how PDCP packet duplication with CA can be implemented in an NR network). The UE is commanded (ordered) to dynamically activate/deactivate UL replication by using MAC CEs. If the NW configures the two LCHs with the same priority, activating CA replication may result in a reduced latency (latency) given that the two LCHs refer to the same bearer, which would not occur if replication were not activated. For example, the rate of data flow on the replicated leg or link may be reduced, possibly to the extent that data may be stranded on the replicated leg (e.g., due to temporary congestion of the replicated leg or link). In this case, the arrival of new data for the radio bearer does not trigger a regular (regular) BSR even if the initial leg or link is empty (i.e. not congested). The NW only knows the arrival of new data when a periodic (periodic) BSR or a padding (padding) BSR is eventually received, which may wait until a few milliseconds (ms).

Thus, activating a duplicated leg may affect the triggering of the BSR when new data arrives, and may even prevent triggering of the BSR in case the duplicated leg is not activated but should trigger the BSR, with a consequent reduction in the delay (latency) of the radio bearer. To avoid this, the NW may pre-configure the replicated LCH with a lower priority than the initial LCH. With this configuration, the radio bearer does experience a reduction in latency when packet replication is activated compared to when packet replication is not activated, since even if an event causes a congestion that causes a packet to be stuck on the replicated leg, such data is of lower priority than the data arriving on the original leg. This will then not prevent BSR triggering, i.e. the BSR triggering of the initial leg is not affected by the activation of the duplicated leg. However, if instead some data is stranded in the original LCH, this will prevent new UL data from reaching the replicated LCH, triggering a BSR. To address this problem, the replicated LCH should be preconfigured with a higher priority than the initial LCH.

Therefore, in the prior art, when CA replication for an RB is activated, even when data for the RB is stuck in one leg, a regular BSR is not triggered when new UL data arrives, even if data is not stuck on another leg, which reduces the RB latency (latency).

In LTE Rel-8 (also reused in NR), a regular BSR is triggered when there is new UL data available for a higher priority LCH than the priority of an LCH that already contains available UL data (within a MAC entity). This principle enables to limit the BSR overhead by triggering regular BSRs only in limited cases. When the condition for new UL data availability is not met (there is already UL data of the same or higher priority), the NW scheduler is informed about the UE buffer status using periodic BSR. However, this requires that the NW scheduler knows the existing higher or equal priority data, so that it schedules resources for this existing data first. While a UE may be configured to trigger a BSR in case of receiving the UL new data even when the same priority data has been buffered, some UEs may do so, some may not, and the NW scheduler will not have consistent information between UEs if the solution is left to UE execution. The best reliable BSR trigger is needed for packet replication only when the LCHs are mapped on different carriers. Triggering a BSR may add a significant amount of overhead if there is already data for an LCH and new data arrives at the LCH, so periodic BSR may be used instead. However, if the UE is allowed to transmit a BSR in this case, the periodic BSR becomes useless.

Some embodiments of the disclosed technology seek to address such situations by proposing a compromise between traditional BSR design (from LTE R8, etc.) and serving cell/Component Carrier (CC) limitations of packet replication introduced in CA, by ensuring that the BSR is always properly triggered to reduce the likelihood of increased latency problems when packet replication is activated.

Enhanced DLPDCP copy operation (PDCP layer)

Another problem that may arise when implementing PDCP layer packet replication is that the UE currently does not know when DL replication is used or not, and whether the NW wishes to activate DL replication through Dual Connectivity (DC) and non-ideal backhaul or through different queuing delays (delay), there is no convenient way to instruct the UE to use a different reordering timer. This also results in a reduced delay (latency) in the PDCP COUNT gap case.

One way to solve this problem is to let the NW pre-configure a larger reordering timer (a disadvantage in this case is that the delay (latency) is unnecessarily reduced due to the PDCP COUNT gap if the copy is not used) or configure a larger reordering timer when the copy is activated (a disadvantage in this case is that RRC signaling has to be added, which is not suitable for easily triggering DL copies when needed, especially in cell edge scenarios). For example, when a PDCP entity is configured, the UE may be configured with a larger reordering timer.

Some embodiments of the disclosed technology instead pre-configure additional/alternative reordering timers and use one mechanism to select the reordering timers to use (e.g., they may use a MAC CE (for UL) and/or use another mechanism to select the reordering timers to use to avoid the two drawbacks described above.

One embodiment of providing enhanced BSR operation for replication in carrier aggregation "CA" (MAC layer) will be described herein Some examples, however, if some contexts of carrier aggregation replication and regular buffer status reporting are given first are helpful And (4) assisting.

Background of CA replication

When CA replication is configured and activated for a radio bearer, a PDCP entity performs PDCP PDU replication and submits original and replicated PDCP PDUs to two different Radio Link Control (RLC) entities. The two RLC entities submit respective RLC PDUs to the same MAC entity over two logical channels. To ensure that those RLC PDUs are sent on different carriers, these logical channels are restricted to using different component carriers (or equivalent serving cells). This is illustrated in fig. 1 of the drawings, where a logical channel LCH1 is restricted to using a transport carrier channel CC1 and a transport carrier channel CC2, while another logical channel LCH2 is restricted to using another transport carrier channel CC 3. The mapping may be configured by Radio Resource Control (RRC), for example by setting the parameter lcp-allowedServingCells.

Background of conventional BSR

The conventional principle of a regular BSR reused in NR (triggered when new data arrives) is that a regular BSR should be triggered when there is new UL data available for a higher priority LCH than the priority of LCHs already containing available UL data.

This includes 2 cases:

i) new UL data may be used for one LCH and no data may be used for transmission in any other LCH;

ii) new UL data is available for an LCH and the LCH has a higher priority than all other LCHs that already contain available UL data.

Logical Channels (LCHs) must be assigned to a Logical Channel Group (LCG) that defines the granularity of reporting the buffer size to the NW (all data from LCHs belonging to the same LCG are aggregated for reporting UL data available in the BSR for transmission to the NW). It should be noted that (for reference only), any data for LCHs that are not mapped to an LCG are not reported and will not trigger BSR. "UL data available for LCH transmission", "UL data available for LCH" or "LCH containing available UL data" refers to UL data that will eventually be submitted to the corresponding LCH and buffered in the RLC or PDCP, as specified in MAC specification 38.321v 200. The MAC entity determines the amount of UL data available for a logical channel according to the data amount calculation procedures in TSs 38.322 and 38.323[3] [4],

the full MAC specification 38.321v200 text is as follows: a BSR should be triggered if any of the following events occur: the MAC entity has new UL data available for a logical channel belonging to an LCG; and the priority of the logical channel to which the new UL data belongs is higher than the priority of any logical channel containing available UL data belonging to any LCG, or the logical channel belonging to an LCG does not contain any available UL data; in this case, the BSR is referred to as a "regular BSR".

CA replication and regular BSR triggering

Some embodiments of the disclosed technology address ultra-reliable low latency communication (URLLC) use cases where a UE has one Dedicated Radio Bearer (DRB) configured to serve URLLC traffic. Typically, the corresponding URLLC LCH will be configured to have a higher priority than other LCHs, e.g. enhanced mobile broadband ((eMBB LCH) — this ensures that a regular BSR is triggered when new urllcull data arrives, even if there is already UL data available for eMBB.

When CA replication is configured, it is expected that the replicated URLLC LCH will be configured with a high priority similar to the original URLLC LCH. In one scenario, both LCHs use the same priority. In order for the base station (referred to as the gsdeb (gnb) in NR) scheduler to distinguish which LCH (and therefore carrier) UL data resources are needed, the two LCHs can be mapped to different Logical Channel Groups (LCGs).

When a first burst of data arrives at URLLC, new UL data is available for both LCHs at the same time. If the MAC entity considers two arrivals simultaneously, two conventional BSRs will be triggered, one for each LCH. As expected, the gNB has timely knowledge of the Buffer Status (BS) of the two LCHs. When a second burst of data arrives at URLLC, the same behavior is expected and no problems arise if the first burst is successfully transmitted on both links. However, one of the links may encounter problems, for example due to the use of high frequency related temporary congestion in the NR.

In some cases, the transmission of the first burst on the replicated link has not yet been completed (meaning that there is still UL data available for the replicated LCH) when the second burst of data arrives. In this scenario, the arrival of the new UL data will not trigger a BSR because a same LCH already has UL data available.

The gNB does not have timely knowledge of the BS of the original LCH. Due to the periodic BSR, the gNB scheduler only gets knowledge of the arrival of this data, which may happen a few milliseconds later, depending on the configuration. This may be contrasted with the case where no duplicate link is established at the first location, in which case a BSR would have been triggered at the arrival of the second burst. To avoid this problem, the replicated LCH may be configured with a lower priority than the initial LCH. However, the opposite problem may occur, namely that some data may be retained in the original LCH and new UL data may be prevented from reaching the replicated LCH to trigger a BSR.

Therefore, when CA replication for an RB is activated, in the existing BSR procedure, as long as data of the RB stays in one leg, a regular BSR is not triggered even if new UL data of the RB arrives, even if data does not stay on another leg. Due to this problem, the activation of CA replication may even reduce the latency (latency) of the RB, as opposed to one of the intended targets of replication. This problem does not occur in Dual Connectivity (DC) replication because there are 2 MAC entities in DC, one for each of Master Cell Group (MCG) and Secondary Cell Group (SCG), and there are independent BSR procedures for the Master Node (MN) and Secondary Node (SN) schedulers.

Some embodiments address the above issues by modifying the conventional BSR triggering mechanism as follows for an example of a network configuration with 3 Dedicated Radio Bearers (DRBs) pre-configured for replication. The 3 DRBs are configured and shown in table 1, where the numbered logical channels are referred to as lc1.. LC6, where: LC1/LC2 are branches of replicated DRBA; LC3/LC4 are both branches of replicated DRBB; and LC5/LC6 are branches of replicated DRBC. In this example, five Serving Cells (SCs)/Component Carriers (CCs) are provided, and Logical Channel (LCH) mapping restrictions for the Serving Cells (SCs)/Component Carriers (CCs) to the set of logical channels are shown in the following table (this indicates allowed serving cells/component carriers for each of the logical channels).

	CC1	CC2	CC3	CC4	CC5
						LC1	X	X
LC2			X	X	X
						LC3	X
LC4			X
						LC5	X		X
LC6		X		X

Table 1: example logical channel (LCh) (referred to in table 1 as lc1.. LC5) to component carrier (cc1.. CC5) mapping.

In this example of an embodiment of the disclosed technology, the DRBs have similar priorities, so the priorities of the Logical Channels (LCHs) are the same among the DRBs. We also assume that the priorities of the original and replicated LCHs are set equal. Thus, in this example configuration, all the LCHs (lc1... LC6 in table 1) are configured to have the same priority.

Now consider that when new data arrives for a logical channel within a MAC entity, if the MAC entity checks for available data on a subset of LCHs, a regular BSR is triggered only if there is no available data in the LCHs of the subset for LCHs. On this basis, among all LCGs, the subset is all LCHs with higher or equal priority than the LCH where new UL data arrives. This subset is called the baseline (baseline) subset. The presence of available data for any LCH in the subset prevents the triggering of a regular BSR upon arrival of new UL data for the LCH in question. The resulting conventional BSR triggering procedure is equivalent to a conventional BSR being triggered if already available data (if any) relates only to LCHs having a lower priority than LCHs with new UL data. In the example configuration described above, all the LCHs have the same priority, and the baseline LCHs subset will be detailed in table 2 below, depending on whether new data (new data, ND) arrives at LC 1-LC 6.

ND LC1

ND LC2

ND LC3

ND LC4

ND LC5

ND LC6

LC1

X

LC2

X

LC3

X

LC4

X

LC5

X

LC6

X

TABLE 2

In this case, when new data arrives at one LC, the data already available in the corresponding LCH subset will prevent BSR triggering. All the LCHs in the LCH subset are considered, and therefore any data that is retained on any of all the LCHs (lc1.. LC6) will prevent BSR triggering. This leads to two problems. One problem is that if data is stuck on the original leg or the replicated leg of a DRB, the BSR is not triggered (as described above). This is because in the case of NDLC1 (new data on LC 1), the data on LC2 is checked and vice versa, and similarly for LC3/4 and LC 5/6. Another problem is that data retention corresponding to one DRB may prevent BSR triggering of another DRB in consideration of a plurality of DRBs even if the another DRB is configured to use more Component Carriers (CCs). LC3 data may be stranded if CC1 is congested (because LC3 is configured to use only CC1 in this example). This will prevent all other LCHs from triggering BSR even if they are allowed to use other CCs.

In some embodiments, one or more "restricted LCHs" are used. Unless otherwise noted, the term "restricted LCH" refers to an LCH that is restricted to transmissions using a particular (specific) Component Carrier (CCs) or equivalent Serving Cell (SCs). For example, configuration may be performed by RRC using the parameter Lcp-allowedServingCells.

In some examples of embodiments of the disclosed technology, a MAC entity has new UL data available for a restricted LCH that belongs to a Logical Channel Group (LCG). In these examples of embodiments, for example, when an LCH containing available UL data is examined for the purpose of triggering a regular BSR, an additional (further) subset of the LCHs is used in addition to the baseline subset described herein above. For example, when checking an LCH containing available UL data for the purpose of triggering a regular BSR, the MAC entity will consider the LCHs related to the reference subset as well as the additional subset.

In one embodiment, the additional subset of LCHs is a set of LCHs that are allowed to use at least one same component carrier/serving cell as a restricted LCH for which the MAC entity has new UL data available. (equivalently, the additional subset of LCHs is the set of all LCHs except some LCHs that are not allowed to use any carriers/serving cells allowed by the restricted LCH for which the MAC entity has new UL data available.)

With the above exemplary configuration, the resulting subset of LCHs is detailed in Table 3 below, depending on whether New Data (ND) arrives at LC 1-LC 6.

ND LC1

ND LC2

ND LC3

ND LC4

ND LC5

ND LC6

LC1

X

-

X

LC2

-

X

LC3

X

-

X

LC4

X

-

X

LC5

X

-

LC6

-

X

TABLE 3

The above-mentioned set of all LCHs comprising at least one component carrier/serving cell that is allowed to use the same restricted LCH for which the MAC entity has new UL data available solves the above-mentioned first problem in the following cases: data stays on the original or duplicate legs of a DRB, the BSR for one DRB is not triggered, and the available data on one leg is not checked for data arrival on another leg (indicated by "-" in table 3 above).

However, the second problem still remains: where multiple DRBs are considered, data retention corresponding to one DRB may prevent BSR triggering of additional DRBs even if they are configured to use more CCs and all other LCHs even if they are allowed to use other CCs. If CC1 is blocked, LC3 may experience data retention and will prevent BSR triggering from new data on LC1 even though LC1 may also use CC 2.

This would result in a modification to known BSR techniques, such as proposed in the MAC specification 38.32v200, and according to an embodiment of the disclosed technique, a BSR is triggered if any of the following events occur:

-the MAC entity has new UL data available for a logical channel belonging to an LCG; and

-said new UL data belongs to a logical channel with a higher priority than any logical channel belonging to any LCG and allowed to use at least one serving cell allowed by said logical channel with new UL data, containing available UL data; or

-none of the logical channels of at least one (oneof) serving cells belonging to an LCG and allowed to use said logical channel with new UL data contains any available UL data;

in this case, the BSR is hereinafter referred to as "regular BSR";

accordingly, one embodiment of the present invention includes a method of triggering a BSR, the method comprising:

determining (determining) whether a MAC entity has new Uplink (UL) data available for logical channels belonging to a Logical Channel Group (LCG); and

triggering a BSR in response to any one of the following decisions (determining):

said new Uplink (UL) data belonging to a logical channel with a higher priority than any logical channel belonging to any LCG and allowed to use at least one or more or all serving cells allowed by said logical channel with new UL data, including any logical channel of available UL data; or

The logical channels of any serving cell belonging to any LCG and allowed to use said logical channel with new UL data do not contain any available UL data.

The triggered BSR is hereinafter referred to as "regular BSR";

in another embodiment, the additional subset of LCHs are LCHs of the restricted LCHs that are allowed to use at least the same component carrier/serving cell (i.e., all) as MAC entity with new UL data available. Equivalently, the additional subset of LCHs are all LCHs except some LCHs that are not allowed to use at least one carrier/serving cell allowed by the restricted LCH for which the MAC entity has new UL data available.

With the above exemplary configuration, the resulting subsets of LCHs are described in detail below, depending on whether New Data (ND) arrives at LC 1-LC 6.

ND LC1

ND LC2

ND LC3

ND LC4

ND LC5

ND LC6

LC1

X

-

X

LC2

-

X

LC3

X

-

LC4

-

X

LC5

X

-

LC6

-

X

Table 4:

the problem that this embodiment was solved is: when a BSR for a DRB is not triggered, data stays on the original or duplicate legs of the DRB, and the available data on one leg is not checked for data arrival on another leg (indicated by "-" in the table).

The above embodiment also solves the following problems: when multiple DRBs are used and data retention corresponding to one DRB prevents BSR triggering of another DRB even if the another DRBs are configured to use more CCs. Even if CC1 is blocked and LC3 experiences data retention, BSR triggering from new data on LC1 is not prevented because LC1 may also use CC 2. The LC3 available data is checked only when new data arrives for LC3 (i.e., only BSR can be blocked). In the case of new data arriving from a different LCH, the LC3 available data is not considered because all other LCHs may use a different CC than CC1. The LC2 available data may prevent BSR triggering of new data arrival from LC4 because LC4 may only use CC3 that has been used by LC 2.

-said new UL data belongs to a logical channel with a higher priority than any logical channel belonging to any LCG and allowed to use at least all serving cells allowed by said logical channel with new UL data, containing available UL data; or

-none of the logical channels of at least all (all) serving cells belonging to an LCG and allowed to use said logical channel with new UL data contain any available UL data;

in this case, the BSR is called a "regular BSR";

therefore, another example of a method of triggering a BSR according to an embodiment of the present invention includes:

determining whether a MAC entity has new Uplink (UL) data available for logical channels belonging to a Logical Channel Group (LCG); and

triggering a BSR in response to either:

-deciding that said new Uplink (UL) data belongs to a logical channel with a higher priority than any logical channel belonging to any LCG and allowed to use at least all serving cells allowed by said logical channel with new UL data, containing available UL data; or

-deciding that none of the logical channels of at least all serving cells belonging to an LCG and allowed to use said logical channel with new UL data contain any available UL data;

in another embodiment of the disclosed technology, a serving cell mapping restriction is configured for a purpose other than replication, and the proposed regular BSR trigger update is configurable. The previous embodiments are extended to apply the new behavior only when configured by Radio Resource Control (RRC), either explicitly (e.g. together with LCH or DRB/PDCP configuration) or implicitly (for LCHs corresponding to duplicated DRBs). This new behavior may also be configured to only apply to a particular (specific) LCGs.

In another embodiment of the disclosed technology, a "restricted LCH" refers to an LCH that is configured with one or more mapping restrictions, e.g., such as those specified in MAC specification 38.321v200, wherein RRC additionally controls the LCP process by configuring mapping restrictions for each logical channel:

-Lcp-allowedSCS sets the allowed subcarrier spacing(s) for transmission;

-Lcp-maxPUSCH-Duration sets the maximum PUSCH Duration allowed for transmission;

-Lcp-configurable granttype1Allowed sets whether a configured grant type1 can be used for transmission;

-Lcp-allowedServingCells sets the allowed cell(s) for transmission.

Other embodiments described herein may be similarly extended/extended to consider not only the mapping restriction(s) of any serving cell, but also any other mapping restriction(s).

Another example of an embodiment of the disclosed technology provides a "fast BSR trigger". In this example of an embodiment, a new trigger is defined. The new trigger is called "fast BSR trigger" and may be configured by RRC on an LCH or DRB basis (in which case it applies to the LCHs used by the DRB)

In case the MAC entity has new UL data available for an LCH belonging to an LCG configured as "fast BSR trigger", only the LCH containing available UL data needs to be considered when checking the LCH for the purpose of triggering a regular BSR.

With the above exemplary configuration, the resulting subsets of LCHs are detailed below in Table 5, depending on whether New Data (ND) arrives at LC 1-LC 6.

ND LC1

ND LC2

ND LC3

ND LC4

ND LC5

ND LC6

LC1

X

-

LC2

-

X

LC3

X

-

LC4

-

X

LC5

X

-

LC6

-

X

TABLE 5

The above embodiment also solves the following problems: when multiple DRBs are used and data retention corresponding to one DRB prevents BSR triggering of another DRB even if the another DRBs are configured to use more CCs. Although the above embodiments address both of these problems, there are still some disadvantages, for example, a new BRS flip-flop will be assigned instead of modifying an existing flip-flop, and the flip-flops are on an LCH basis. This may lead to overhead if we consider the case of several LCHs, since in the prior art, an LCH does not trigger a BSR even if there is already more or equal priority LCH data available. Moreover, the fast BSR trigger needs to be configured either explicitly (by RRC, e.g. as part of LCH configuration) or implicitly (e.g. for LCHs corresponding to replicated DRBs).

Accordingly, one example of an embodiment of the disclosed technology provides a method for triggering a Buffer Status Report (BSR) to modify a known technique (e.g., a technique known from MAC specification 38.321v 200). According to this exemplary embodiment, a BSR should be triggered if any of the following events occur:

-said new UL data belongs to a logical channel with a priority higher than the priority of any logical channel belonging to any LCG containing available UL data; or

None of the logical channels belonging to an LCG contain any available UL data; or

-the new UL data belongs to a logical channel configured for fast BSR triggering and the logical channel does not contain already available data,

in this case, the BSR is hereinafter referred to as a "regular BSR".

triggering a BSR in response to either:

-deciding that the new Uplink (UL) data belongs to a logical channel with a priority higher than any logical channel belonging to any LCG containing available UL data; or

-determining that none of the logical channels belonging to an LCG contain any available UL data; or

-deciding that the new UL data belongs to a logical channel configured for fast BSR triggering and that the logical channel does not contain already available data.

Another example of an embodiment also provides a very fast BRS triggering method. In this example of an embodiment, a new trigger is defined. The new trigger is called a "very fast BSR trigger" and may be configured by RRC on an LCH or DRB basis (in which case it applies to the LCHs used by the DRB). In case the MAC entity has new UL data available for an LCH belonging to an LCG configured as "very fast BSR trigger", a regular BSR is triggered independently of any available UL data.

This embodiment triggers regular BSRs even faster, but there may be some drawbacks because it requires a larger overhead of extra BSRs and will trigger more BSRs than known techniques (in known techniques, if there is already pending data for an LCH, then new data for the LCH will not trigger a BSR, since a padding or periodic BSR can handle the pending data).

-the new UL data belongs to a logical channel configured for fast BSR triggering and the logical channel does not contain already available data;

in this case, the BSR is hereinafter referred to as "regular BSR";

in some embodiments related to enhanced DLPDCP replication operations (PDCP layer)The UE is configured by RRC with two RLC entities/logical channels for one radio bearer. The NW may use these LCHs for packet replication in the DL. Fig. 2A of the accompanying drawings shows, as an example, how a radio bearer which is not configured for duplication differs from a radio bearer which is configured for duplication (see fig. 2B of the accompanying drawings). Once the NW has configured a radio bearer by RRC to use DL PDCP duplication (two RLC entities/logical channels are configured for one radio bearer), the NW can activate/deactivate a Downlink (DL) packet duplication operation when needed without notifying the UE. The duplication operation has no direct impact on UE Packet Data Control Protocol (PDCP) receive operations because reordering and deduplication operations are already needed and supported in baseline NRPDCP operations.

Figure 3 schematically illustrates an example of a PDCP receive operation using a PUSH based reordering window. The reordering window lower edge "RX _ DELIV" is pushed by the arrival of PDCP PDUs by COUNT ═ RX _ DELIV, or by the expiration of a reordering timer. The reordering timer is started whenever the reordering timer has not run and a gap is created in the received COUNT sequence. The reordering operation of the DL PDCP is used to configure in-order or out-of-order delivery (delivery) to the application layer.

In the new radio (NR or 5G), the Radio Link Control (RLC) will send the complete RLC Service Data Units (SDUs) to the PDCP immediately after they are received, i.e. there is no in-order delivery from RLC to PDCP as opposed to LTE (or 4G). Thus, even when a single LCH is used, PDCP reordering needs to be configured:

for the Unacknowledged Mode (UM), the reordering timer should be higher than the delay of the retransmission of the maximum HARQ;

for the Acknowledged Mode (AM), the reordering timer should be higher than a delay of retransmission of an automatic repeat request (ARQ).

However, whenever an in-order delivery is configured and there is a gap in the PDCP sequence, the reordering timer introduces a delay in delivering PDCP SDUs to the upper layer. Therefore, as small a value as possible should be configured.

It is known that when two LCHs are used for replication, then an additional delay between the two LCHs is expected in the case of a DC with non-ideal backhaul, or in the case of a DC/CA with different queuing delays. Currently, a UE does not know whether/when DL replication is used. Thus, if the NW were to activate DL replication through DC and non-ideal backhaul or through different queuing delays, the NW would have to configure a larger reordering timer. Using known procedures, the NW configures a larger reordering timer through RRC signaling. This can be done by:

-when configuring DL replication or more generally before activating DL replication. However, such known procedures may cause problems if the duplication is not activated, since the delay is reduced in case of PDCP COUNT interval when the duplication is not activated. The PDCP COUNT gap may occur due to packet loss on the air interface (in UM) or PDCP PDUs dropped from the NW end (in AM or UM). In case such a PDCP COUNT gap occurs, the PDCP entity at the UE will wait for the missing PDCP PDU(s) for a longer time than necessary, since it will actually wait for the potential arrival of PDCP PDUs from the alternative leg.

-when replication is activated: the problem is compounded by RRC signaling that is not adapted to easily trigger DL replication when needed, especially in cell edge scenarios. This is why a MAC CE is introduced to activate/deactivate replication in UL, and RRC signaling is also possible.

One example of an embodiment of the disclosed technology pre-configures a reordering timer for use when DL replication is activated. This may be part of the PDCP entity configuration

In addition to the baseline reordering timer used when DL replication is not activated, an alternative reordering timer may be configured to be used when DL replication is activated.

Activation/deactivation of DL replication may be detected:

explicitly, indicating activation/deactivation of DL replication by using a mac ce sent by the NW in DL, similarly for activation/deactivation of UL replication;

implicitly, by considering (consedering) that DL replication is activated each time UL replication is activated (this behavior can be configured by RRC on a RB basis);

implicitly, by considering DL replication to be activated whenever data for an RB is received on a second link after being received on a first link, DL replication is deactivated whenever data for an RB is received on only one link for a configured time.

One example of an embodiment of the disclosed technology, a reordering timer for Downlink (DL) dual link operation is preconfigured, e.g., may be used whenever the PDCP DL entity is associated with two Radio Link Control (RLC) entities. This may be applicable to overlay copy and split (split) operations, both of which are dual link operations.

One example of an embodiment of the disclosed technology, a reordering timer for Uplink (UL) PDCP replication (and/or (instead) Downlink (DL) PCDP) is preconfigured. This may also apply when DC (dual connectivity) is used.

In one example of an embodiment of the disclosed technology, packet replication is activated by a mac ce from a primary node (MN) or a Secondary Node (SN). The (received) Packet Data Convergence Protocol (PDCP) entity is located at the MN or SN. The PDCP entity needs to know that UL duplication is activated/deactivated to adapt the reordering timer, however, this decision can be made by a node not carrying (host) PDCP entity. In this example of an embodiment, the node that activates/deactivates UL replication indicates this decision to the node that carries the PDCP entity (if different) by Xn/X2 signaling. This enables a node carrying a PDCP entity to adapt the reordering timer.

Although not shown in detail, any device or apparatus forming part of a network may comprise at least a processor, a memory unit, and a communication interface, wherein the processor unit, the memory unit, and the communication interface are configured to perform the method of any aspect of the present invention. Further schemes and options are described below.

Embodiments of the present invention, and in particular the signal processing functions of the gNB and the UE, may be implemented using computing systems (computing systems) or architectures known to those skilled in the relevant art. Computing systems, such as desktop, portable or notebook computers, handheld computing devices (PDAs, cellular phones, palmtops, etc.), mainframes, servers, clients, or any other type of special or general purpose computing device may be used as may be suitable or appropriate for a particular application or environment. The computing system may include one or more processors, which may be implemented using a general or special purpose processing engine such as, for example, a microprocessor, microcontroller or other control processing module.

The computing system may also include a main memory, such as a Random Access Memory (RAM) or other dynamic memory, for storing information and instructions (instructions) to be executed by the processor. Such main memory may also be used for storing temporary variables or other intermediate information during execution of instructions to be executed by the processor. The computing system may also include a Read Only Memory (ROM) or other static storage device for the processor that stores static information and processor instructions.

The computing system may also include an information storage system, which may include, for example, a media drive (media drive) and a removable storage interface. The media drive may include a drive or other mechanism (mechanism) to support fixed or removable storage media, such as a hard disk drive, a floppy disk drive, a magnetic tape drive, an optical disk drive, a read or write drive (R or RW) for Compact Disc (CD) or Digital Video Drive (DVD), or other removable or fixed media drive. The storage media may include, for example, a hard disk, floppy disk, magnetic tape, optical disk, CD or DVD, or other fixed or removable medium (media) that is read by and written to by the media drive. The storage media may include a computer-readable storage medium having stored therein particular computer software or data.

In alternative embodiments, the information storage system may include other similar components for allowing computer programs or other instructions or data to be loaded into the computing system. These components may include, for example, removable storage units and interfaces such as program cartridges and cartridge interfaces, removable memory (e.g., flash memory or other removable memory modules) and memory slots, and other removable storage units and interfaces that allow software and data to be transferred from the removable storage unit to the computing system.

The computing system may also include a communication interface. Such communication interfaces may be used to allow software and data to be transferred between the computing system and external devices. In this embodiment, the communication interface may include a modem, a network interface (e.g., an ethernet or other NIC card), a communication port (e.g., a Universal Serial Bus (USB) port), a PCMCIA slot and card, etc. Software and data transferred via the communications interface are in the form of signals which may be electronic, electromagnetic, optical or other signals capable of being received by the communications interface media.

In this document, the terms "computer program product," "computer-readable medium" (media), and the like may be used generally to refer to a tangible medium, such as a memory, storage device, or storage unit. These and other forms of computer-readable media (media) may store one or more instructions for use by a processor, including a computer system, to cause the processor to perform specified operations. These instructions, generally referred to as "computer program code" (which may be combined in the form of a computer program or in other combinations) when executed, cause the computing system to perform the functions of embodiments of the present invention. It should be noted that the code may directly cause the processor to perform certain operations, be compiled to do so, and/or be combined with other software, hardware, and/or firmware elements (elements) (e.g., libraries for performing standard functions).

The non-transitory computer readable medium may include at least one of the group consisting of a hard disk, a compact disc Read Only Memory (CD-ROM), an optical storage device, a magnetic storage device, a Read Only Memory (Read Only Memory), a Programmable Read Only Memory (Programmable Read Only Memory), an Erasable Programmable Read Only Memory (EPROM), an Electrically Erasable Programmable Read Only Memory (Electrically Erasable Programmable Read Only Memory), and a flash Memory.

In embodiments where elements (elements) are implemented using software, the software may be stored on a computer-readable medium and loaded into a computing system using, for example, a removable storage drive. The control module (in this example, software instructions or executable computer program code), when executed by a processor in a computer system, causes the processor to perform the functions of the invention as described herein.

Furthermore, the inventive concept can be applied to any circuit for performing signal processing functions within a network element. It is further contemplated that, for example, a semiconductor manufacturer may use the concepts of the present invention in the design of a stand-alone device, such as a microcontroller of a Digital Signal Processor (DSP) or application-specific integrated circuit (ASIC) and/or any other subsystem element.

It will be appreciated that for clarity purposes, embodiments of the invention have been described above with reference to a single processing logic. However, the inventive concept may equally be implemented by means of a plurality of different functional units and processors to provide the signal processing functions. Thus, references to specific functional units are only to be seen as references to suitable means for providing the described functionality rather than indicative of a strict logical or physical structure or organization.

Aspects of the invention may be implemented in any suitable form including hardware, software, firmware or any combination of these. Alternatively, the invention may be implemented at least partly as computer software running on one or more data processors and/or digital signal processors or configurable modular components such as FPGA devices (devices). Thus, the elements and components of an embodiment of the invention may be physically, functionally and logically implemented in any suitable way. Indeed the functionality may be implemented in a single unit, in a plurality of units or as part of other functional units.

Although the present invention has been described in connection with some embodiments, it is not intended to be limited to the specific form set forth herein. Rather, the scope of the invention is limited only by the accompanying claims. In addition, although a feature may appear to be described in connection with particular embodiments, one skilled in the art would recognize that various features of the described embodiments may be combined. In the claims, the term "comprising" does not exclude the presence of other elements or steps.

Furthermore, although individually listed, a plurality of means, elements or method steps may be implemented by e.g. a single unit or processor. Furthermore, although individual features (features) may be included in different claims, these may possibly advantageously be combined, and the inclusion in different claims does not imply that a combination of features is not feasible and/or advantageous. Also, the inclusion of a feature in one category (category) of claims does not imply a limitation to this category, but rather indicates that the feature is equally applicable to other claim categories.

Furthermore, the order of features in the claims does not imply any specific order in which the features must be performed and in particular the order of individual steps in a method claim does not imply that the steps must be performed in this order. Rather, the steps may be performed in any suitable order. In addition, singular references do not exclude a plurality. Thus, references to "a", "an", "first", "second", etc. do not preclude a plurality.

Although the present invention has been described in connection with some embodiments, it is not intended to be limited to the specific form set forth herein. Rather, the scope of the invention is limited only by the accompanying claims. Furthermore, although a feature may appear to be described in connection with particular embodiments, one skilled in the art would appreciate that different features of the described embodiments may be combined in accordance with the invention. In the claims, the terms "comprising" or "including" do not exclude the presence of other elements.

Claims

1. A method for triggering a buffer status report in a wireless communication network operating a packet data convergence protocol, wherein a plurality of logical channels are used to provide packet replication, the method comprising:

determining whether a medium access control, MAC, entity has new uplink data available for a first logical channel belonging to a logical channel group;

and if so, if one of the following is determined:

None of the other logical channels of at least one serving cell belonging to any logical channel group and allowed to use the first logical channel with the new uplink data contains any available uplink data,

a buffer status report is triggered.

2. A method as claimed in claim 1, wherein the buffer status report is triggered if one of the following is determined:

said new uplink data belonging to a logical channel having a higher priority than any logical channel of available uplink data belonging to any logical channel group and allowed to use at least all serving cells allowed by said logical channel with new uplink data; or

None of the logical channels of all serving cells belonging to a logical channel group and allowed to use the logical channel with new uplink data contains any available uplink data.

3. A method according to any of claims 1 or 2, wherein said method of triggering said buffer status report is configurable in said wireless communication network by means of radio resource control.

4. A method according to claim 3, wherein the radio resource control configures the wireless network to implement the method of triggering the buffer status report according to claim 1 or 2, either explicitly when a logical channel or a dedicated radio bearer/packet data convergence protocol is configured in the network, or implicitly when a logical channel is configured to correspond to a duplicated dedicated radio bearer.

5. A method as claimed in any preceding claim, wherein the method is implemented only for one or more specific groups of logical channels in the wireless communications network.

6. A method for triggering a buffer status report in a wireless communication network operating a packet data convergence protocol, wherein a plurality of logical channels are used to provide packet replication, the method comprising:

determining whether a medium access control, MAC, entity has new uplink data available for a logical channel belonging to a logical channel group;

and if so, if one of the following is determined:

a buffer status report is triggered.

7. A method according to claim 6, wherein the buffer status report trigger is configured by radio resource control on a logical channel based or on a logical channel used by a dedicated radio bearer based.

8. The method of claim 6, wherein the step of triggering the buffer status report further requires that the new uplink data belong to a logical channel that does not contain already available data.

9. A method as claimed in any preceding claim, wherein the method is performed in a radio access network for a new radio/5G communications network.

10. Apparatus for triggering a buffer status report in a wireless communication network operating packet data convergence protocol, wherein a plurality of logical channels are used to provide packet duplication, the apparatus comprising:

means configured to provide a first positive determination if a medium access control entity has new uplink data available for a first logical channel belonging to a logical channel group;

means configured to provide a second positive decision when the available uplink data contained in any other logical channel belonging to the logical channel group is allowed to use at least one serving cell allowed by the first logical channel with the new uplink data, if the new uplink data belonging to the first logical channel has a higher priority than the priority of the available uplink data on the first logical channel; and

means configured to provide a third positive decision if none of the other logical channels belonging to the logical channel group to which the first logical channel belongs, of the at least one serving cell allowed to use the first logical channel with the new uplink data, contain any available uplink data, and

means configured to cause said triggering of a buffer status report in response to a positive first determination and a positive second determination or a positive third determination to provide a third positive determination.

11. A wireless network, characterized in that it comprises means for implementing any of the methods of claims 1 to 5 and/or of claims 6 to 9.

12. A wireless network configured to operate using a packet data convergence protocol, wherein a plurality of logical channels are used to provide packet replication and the wireless network is capable of activating downlink packet replication, characterized in that the network further comprises means for pre-configuring a reordering timer for use when a downlink replication is activated as part of the packet data convergence protocol configuration of the wireless network.

13. A wireless network as recited in claim 12, wherein the network is configured to: a reordering timer is preconfigured if at least activation and/or deactivation of downlink packet duplication is detected by using a MAC CE.

14. A wireless network as claimed in claim 12 or 13, wherein the network is configured to: a reordering timer is preconfigured if activation and/or deactivation of uplink packet duplication is detected by using a MAC CE.

15. A wireless network according to any one of claims 12 to 13, wherein the network is configured to: downlink packet replication is considered to be activated whenever uplink activation is detected.

16. A wireless network according to any one of claims 12 to 13, wherein the network is configured by a radio bearer based radio resource control to: downlink packet replication is considered to be activated whenever uplink activation is detected.

17. A wireless network according to any one of claims 12 to 13, wherein the network is configured to: downlink replication is considered activated if it is determined that data for a radio bearer is also received on a second link after being received on a first link.

18. A wireless network as recited in claim 17, wherein the network is configured to: the downlink replication is considered deactivated whenever data of a radio bearer is received on only one link within a predetermined time interval.

19. A radio network according to any of claims 12 to 18, wherein the radio network comprises at least one node in which a PDCP entity is located, the at least one node being configured to adapt the reordering timer.

20. A wireless network as recited in claim 19, wherein:

the data packet replication is activated by a MAC CE from a primary node MN or a secondary node SN of the wireless network and the receiving PDCP entity is located at the primary node or the secondary node, and

wherein an indication of a decision is communicated to the other of the primary or secondary node where the PDCP entity is located whenever a primary or secondary node decides to activate and/or deactivate an uplink replication.

21. The wireless network of claim 21, wherein an indication of the decision is communicated to the other of the primary or secondary node where the PDCP entity is located using Xn/X2 signaling so that the node carrying the PCDP entity can adapt the reordering timer.

22. A wireless communication network according to any of claims 12 to 21, further configured with means for implementing a method according to any of claims 1 to 9.

23. A network device, comprising: a processor, a memory unit and a communication interface, wherein the processor unit, memory unit and communication interface are configured to perform the method of any of claims 1 to 9.

24. A non-transitory computer readable medium having stored thereon computer readable instructions for execution by a processor to perform the method of any of claims 1 to 9.

25. A method for triggering a buffer status report in a wireless communication network operating a packet data convergence protocol, wherein a plurality of logical channels are used to provide packet replication, the method comprising:

determining, by a network node, at least two conditions for triggering transmission of a buffer status report, the first condition comprising:

if the medium access control MAC entity has new uplink data available for a first logical channel belonging to a logical channel group; and

in the at least second condition, one or more of:

if the new uplink data belonging to the first logical channel has a higher priority than the priority of the available uplink data on any other logical channel belonging to the logical channel group, when the available uplink data contained in the other logical channel is allowed to use at least one serving cell allowed by the first logical channel with the new uplink data;

if none of the other logical channels belonging to the logical channel group to which the first logical channel belongs, of the at least one serving cell allowed to use the first logical channel with the new uplink data contains any available uplink data;

if no other logical channel belonging to any logical channel group contains any available uplink data; or

If the new uplink data belongs to a logical channel configured for fast buffer status report triggering,

triggering transmission of the buffer status report when the at least two conditions are satisfied.

26. A method for triggering a buffer status report in a wireless communication network operating a packet data convergence protocol, wherein a plurality of logical channels are used to provide packet replication, the method comprising:

determining whether a medium access control entity has new uplink data available for a first logical channel belonging to a logical channel group;

and if so, if it is determined to be one of:

the new uplink data belonging to the first logical channel has a higher priority than the priority of available uplink data on any other logical channel belonging to the logical channel group when the available uplink data contained in the other logical channel is allowed to use at least one serving cell allowed by the first logical channel with the new uplink data; and/or

None of the other logical channels belonging to the logical channel group to which the first logical channel belongs, of at least one serving cell allowed to use the first logical channel with the new uplink data, contain any available uplink data,

a buffer status report is triggered.