Clone
26
how to establish dedicated bearers
nikaeinn edited this page 2016-09-29 19:50:22 +02:00

Tutorial on how to establish dedicated bearers

Note: for the moment, openair-cn does not yet support the establishment of dedicated bearer (i.e. e_RAB_SETUP procedure), so to test you need to use a 3rd party EPC

E_RAB_SETUP Procedure

Figure below shows the messaging to establish one or multiple dedicated bearers. E_RAB_SETUP

Required information for the E-RABSETUPprocedure

The following information needs to be provided to MME (either directly or through PCRF), and used during the e_RAB_SETUP procedure. It is tested for lte-softmodem with S1 and COTS UE (SG V and VI, Huawei Dongle E392 and 398, and Bandrich C500), oaisim with S1, and oaisim with no S1. In all cases, the data were correctly sent and received through the dedicated bearers.

In the following, we highlight the main parameters required to setup the E_RAB and TFT.

E-RAB and QoS Parameters

  1. E-RAB-ID, valid values 5-15
  2. QCI, valid value 1-9.
  3. ARP (allocationRetentionParameters): it is used to deide whether to accept or reject or drop a bearer request due to resource limitations (typically GBR bearers).
  • priorityLevel: valid value (1-15), where 1 is the highest priority, and 15 is the lowest.
  • pre-emptionCapability: valid values "shall not trigger pre-emption", where cannot preempt other bearers, and "may trigger preemption", where it can trigger preemtion of other bearers.
  • pre-emptionVulnerability: valide values "not preemptable", where this bearer cannot be pre-emptable by other bearers, and "preemptable", where this bearer can be released/dropped by other bearers.
  1. gbrQoS Information:
  • e-RAB-MaximumBitrateDL: Max bearer bit rate in bps for downlink
  • e-RAB-MaximumBitrateUL: Max bearer bit rate in bps for uplink
  • e-RAB-GuranteedBitrateDL: Guaranted bearer bit rate in bps for downlink
  • e-RAB-GuranteedBitrateDL: Guaranted bearer bit rate in bps for uplink

Traffic Flow Template (TFT) Parameters

  1. Packet filter direction : up, down, bidirectional
  2. P-GW IP address and subnet mask
  3. Port range
  4. Protocol/header, i.e. icmp, udp, tcp.

Mapping the QCI

Currently, the QCIs 1 (GBR), 2 (GBR), 3 (GBR), 4 (GBR), 7 (non-GBR), 9 (non-GBR), 65 (GBR), 66 (GBR) are mapped to the RLC UM, and QCIs 5 (non-GBR), 6 (non-GBR), 8 (non-GBR), 69 (non-GBR), and 70 (non-GBR) are mapped to RLC AM (see the openair2/RRC/LITE/rrc_eNB.c). The QCI table can be found at here.

Example of VoIP E_RABSETUP configuration

IMS signalling

  1. e-RAB-ID = 6
  2. QCI = 5
  3. arp priorityLevel = 7
  4. arp pre-emptionCapability = shall-not-trigger-pre-emption,
  5. pre-emptionVulnerability = not-pre-emptable

Data

  1. e-RAB-ID = 7
  2. QCI = 2
  3. arp priorityLevel = 6
  4. arp pre-emptionCapability = shall-not-trigger-pre-emption,
  5. pre-emptionVulnerability = not-pre-emptable
  6. GBR QoS e-RAB-MaximumBitrateDL = 100000
  7. GBR QoS e-RAB-MaximumBitrateUL = 100000
  8. GBR QoS e-RAB-GuaranteedBitrateDL = 100000
  9. GBR QoS e-RAB-GuaranteedBitrateUL = 100000

PCAP File Example

DEDICATED_DRB_1.pcapng

ToDo

  1. Support the E_RAB_SETUP procedure in openair-cn
  2. Stability and right configuration parameters of the RLC AM under heavy traffic
  3. test and improve the MAC scheduling across different logical channels
  4. revise the mapping of QCI to RLC/PDCP instance (check the code at openair2/RRC/LITE/rrc_eNB.c)
  5. support of the E-RABRelease procedure
  6. support of dedicated bearer setup and release in OAI UE NAS

Some links: