# QoS Management and Flexible Traffic Detection Architecture for 5G Mobile Networks
## 3 Proposed Architecture
### EPS-Bearer with QoS Requirement Creation  
Figure 6 describes the procedure to create a specific EPS-Bearer with QoS considering a 4G UE (a similar procedure can be defined using 5G access technology). As shown, it is not necessary to make changes in the 4G EU. The proposed EPS-Bearer with the QoS creation procedure requires significant changes if it is compared with those defined in the actual PCC (Policy Control and Charging) architecture [38], and it is described next. Initially, the traffic with QoS requirements is immediately forwarded through the default OF-Bearer, and it is sent to the appropriate traffic detection table, which sends the packet to the SDD. The SDD processes the packet and determines the service characteristics. This information is sent to the PCRF (or a new element with its functions), which is responsible for defining the policy to be applied. If additional information is required, the PCRF could make an additional query to other mobile elements. For example, it is possible to make a query to the OCS (Online Charging System) related to the available credit for the service to be transported. With the signaling information, the user profile, and the available credit, the PCRF defines the policy to be applied (the EPS-Bearer characteristics are defined). The policy is communicated to the MME and to the Controller. If there is an OF-Bearer with the appropriate QoS for this traffic, it will be used. On the other hand, if it does not exist, the Controller creates a new OF-Bearer with an appropriate QoS. To do so, the Controller determines the outer labels and creates the appropriate flow entry in each OpenFlow switch involved in the optimal OF-Bearer with the QoS path. Next, performing the following steps, the Radio Bearer with appropriate QoS characteristics is created:  
Figure 6: EPS-Bearer with QoS creation. UL-TFT, Uplink Traffic Flow Template; OCS, Online Charging System. The MME sends a standard 3 GPP bearer setup requestmessage (through the standard S1-MME interface) to the OF-NB indicating the need to create the appropriate radio bearer. 2. OF-NB sends the corresponding standard RRC (Radio Resource Control) connection reconfigurationto the UE (standard procedure using the E-UTRAN-Uu interface) indicating that the Radio Bearer with QoS must be created. This message has the required information associated with the QoS parameters and the TFT (Traffic Flow Template) filters to be applied at the UE. These filters incorporate the rules to classify the uplink traffic and forward it to the new Radio Bearer with QoS. 3. The UE responds to the OF-NB with a standard RRC connection reconfiguration completenessage. 4. The OF-NB responds to the MME with a standard bearer setup responsivenessage, completing the Radio Bearer creation stage. At the end of this step, the traffic continues being routed using the default OF-Bearer. 6. The Radio Bearer with QoS and the OF-Bearer with QoS are linked to create the EPS-Bearer with QoS as described next. 1. The Controller defines the necessary flow entry in the downlink direction (configured in OF-NB) to link the traffic coming from the OF-Bearer with QoS with the newly-created Radio Bearer with QoS. This step defines the inner MPLS label, which identifies the UE/Radio Bearer. 2. The Controller defines the flow entry in the downlink direction that must be applied at the OF-GW to route the QoS service traffic through the OF-Bearer with QoS to the UE. These flow entries are similar to a specific service flow entry put in the OF-NB (see Figure 4), and the matching criteria are based on the service characteristics and target UE IP address (the appropriate two MPLS labels must be added). In this step, the downlink traffic can already be forwarded through the new EPS-Bearer with QoS. 3. If not previously configured, the Controller creates the specific flow entries (at OF-GW) in the uplink direction. 4.