7.4.1 Requirements
Operating Environment
UEs must support VoIP, and the EPC must support IMS.
Transmission Networking
N/A
License
N/A
7.4.2 Data Preparation
This section describes the data that you need to collect for setting parameters. Required data is data that you must collect for all scenarios. Collect scenario-specific data when necessary for a specific feature deployment scenario.
There are three types of data sources:
l Network plan (negotiation required): parameter values planned by the operator and negotiated with the EPC or peer transmission equipment
l Network plan (negotiation not required): parameter values planned and set by the operator l User-defined: parameter values set by users
Required Data
None
Scenario-specific Data
Different QCIs require different RLC modes. The eNodeB supports adaptive configuration based on QCIs.
The following table describes the parameters that must be set in the StandardQci MO to modify a standardized QCI.
Parameter Name Parameter ID Data Source Setting Notes QoS Class Indication StandardQci.Qci Network plan
(negotiation not required)
N/A
RLC PDCP parameter group ID
StandardQci.
RlcPdcpParaGrou-pId
Network plan (negotiation not required)
N/A
The following table describes the parameter that must be set in the RlcPdcpParaGroup MO to configure an RLC mode.
Parameter Name Parameter ID Data Source Setting Notes UM or
RLC-AM mode
RlcPdcpParaGrou p.RlcMode
Network plan (negotiation not required)
N/A
7.4.3 Precautions
None
7.4.4 Hardware Adjustment
None
7.4.5 Initial Configuration
Using the CME to Perform Batch Configuration for Newly Deployed eNodeBs
Enter the values of the parameters listed in Table 7-1 in a summary data file, which also contains other data for the new eNodeBs to be deployed. Then, import the summary data file into the Configuration Management Express (CME) for batch configuration. For detailed instructions, see section "Creating eNodeBs in Batches" in the initial configuration guide for the eNodeB.
The summary data file may be a scenario-specific file provided by the CME or a customized file, depending on the following conditions:
l The MOs in Table 7-1 are contained in a scenario-specific summary data file. In this situation, set the parameters in the MOs, and then verify and save the file.
l Some MOs in Table 7-1 are not contained in a scenario-specific summary data file. In this situation, customize a summary data file to include the MOs before you can set the parameters.
Table 7-1 Parameters related to RLC modes
MO Sheet in the Summary Data
File Parameter Group Remar
ks
StandardQci StandardQci QOS Class Indication,
RlcPdcpParaGroupId;
RLC and PDCP Parameter Group Configuration
RlcPdcpParaGroupId, UM or RLC-AM mode
User-defined sheet
Using the CME to Perform Batch Configuration for Existing eNodeBs
Batch reconfiguration using the CME is the recommended method to activate a feature on existing eNodeBs. This method reconfigures all data, except neighbor relationships, for multiple eNodeBs in a single procedure. The procedure is as follows:
Step 1 Choose CME > Advanced > Customize Summary Data File, or choose Advanced > Customize Summary Data File, to customize a summary data file for batch reconfiguration.
NOTE
For context-sensitive help on a current task in the client, press F1.
Step 2 Choose CME > LTE Application > Export Data > Export Base Station Bulk Configuration Data, or choose LTE Application > Export Data > Export Base Station Bulk Configuration Data, to export the eNodeB data stored on the CME into the customized summary data file.
Step 3 In the summary data file, set the parameters in the MOs listed in Table 7-1 and close the file.
Step 4 Choose CME > LTE Application > Import Data > Import Base Station Bulk Configuration Data, or choose LTE Application > Import Data > Import Base Station Bulk Configuration Data, to import the summary data file into the CME.
Step 5 Choose CME > Planned Area > Export Incremental Scripts, or choose Area Management >
Planned Area > Export Incremental Scripts, to export and activate the incremental scripts.
----End
Using the CME to Perform Single Configuration
On the CME, set the parameters listed in the 7.4.2 Data Preparation section for a single eNodeB.
The procedure is as follows:
Step 1 In the planned data area, click Base Station in the upper left corner of the configuration window.
Step 2 In area 1 shown in Figure 7-1, select the eNodeB to which the MOs belong.
Figure 7-1 MO search and configuration window
Step 3 On the Search tab page in area 2, enter an MO name, for example, CELL.
Step 4 In area 3, double-click the MO in the Object Name column. All parameters in this MO are displayed in area 4.
Step 5 Set the parameters in area 4 or 5.
Step 6 Choose CME > Planned Area > Export Incremental Scripts, or choose Area Management
> Planned Area > Export Incremental Scripts, to export and activate the incremental scripts.
----End
Using MML Commands
Step 1 Run the MOD RLCPDCPPARAGROUP command to set the RLC/PDCP parameter group.
Step 2 Run the MOD STANDARDQCI command to set parameters related to standardized QCIs.
----End
MML Command Examples
MOD RLCPDCPPARAGROUP: RlcPdcpParaGroupId=0, RlcMode=RlcMode_UM, PdcpSnSize=PdcpSnsize_12bits;
MOD STANDARDQCI: Qci=QCI1, InterRatPolicyCfgGroupId=0;
7.4.6 Activation Observation
The eNodeB can configure RLC modes based on QCIs.
To check whether the RLC mode for conversational voice (QCI 1) is UM and that for IMS signaling (QCI 5) is AM, perform the following steps:
Step 1 Enable a UE to access a cell and perform a VoIP service.
Step 2 Check the S1AP_INITIAL_CONTEXT_SETUP_REQ or S1AP_ERAB_SETUP_REQ message using a drive test tool or S1 tracing task on the M2000 client. Check whether QCI 1 and QCI 5 in the bearer request messages are correct.
Figure 7-2 QCI 1 in the dedicated bearer request message
Figure 7-3 QCI 5 in the dedicated bearer request message
Step 3 Record the e-RAB-IDs that map QCI 1 and QCI 5 in the bearer request messages. In Figure 7-2 and Figure 7-3, the e-RAB-IDs that map QCI 1 and QCI 5 are 6 and 5, respectively.
Then, check RLC mode for bearer setup in the Uu tracing result. If the RLC mode for QCI 1 is UM and that for QCI 5 is AM, the configurations are correct.
Step 4 Check the Uu tracing result. If the RLC mode for QCI 1 is UM and that for QCI 5 is AM, the configurations are correct.
Figure 7-4 Uu tracing result
Figure 7-5 UM for QCI 1
Figure 7-6 AM for QCI 5
----End
7.4.7 Reconfiguration
N/A