 1.2. QCI parameters Network Architecture The scheduling of traffic data carried out at the level of the eNB, SGW and PGW entities is based on the QCI priority level. The bit rate control is done from the GBR and MBR parameters for guaranteed bit rate bearers. The bit rate control is conducted for each bearer at the eNB and PGW entities for incoming data in the EPS network. The bit rate control is done from the APN-AMBR and UE-AMBR parameters for non-GBR type bearers. This control is performed for aggregated bit rates of non-GBR bearers of a mobile. The APN-AMBR parameter controlled by the PGW entity corresponds to the maximum bit rate authorized for all the streams of a mobile phone using non-GBR bearers at the PGW entity level. The UE-AMBR parameter controlled by the eNB entity corresponds to the maximum authorized bit rate for all streams of a mobile phone using non-GBR bearers, at the eNB entity level. The pre-emption implemented at the eNB and PGW entity level corresponds to the ARP parameter that defines the following information: - pre-emption capability: this parameter is used for the establishment of a new session, if the resource is not available. This parameter determines whether or not a new session can pre-empt an existing session; - pre-emption vulnerability: this parameter is used by the existing session. This parameter is compared to the pre-emption capability parameter of the new session to determine whether the existing session can be pre- empted or not; - priority: this determines the priority level associated with pre-emption. This priority level is independent of that set for the QCI parameter. The QoS parameters (QCI, ARP and APN-AMBR) relating to default bearers are stored in the HSS entity. These values can be changed by the PCRF entity. The QoS parameters (QCI, ARP, GBR and MBR) relating to dedicated bearers are stored in the subscription profile repository (SPR) entity associated with the PCRF entity. VoLTE and ViLTE The MME entity replaces the UE-AMBR parameter provided by the HSS entit