EUTRAN Local Mode Design for TEST

SW design document Group Confidential Renesas Mobile Dennis M Senyonjo/S.Balducci

10/17/2011  

Eutran  local  mode   SW  design  document        

[Type  the  abstract  of  the  document  here.  The  abstract  is  typically  a  short  summary  of  the  contents  of  the   document.  Type  the  abstract  of  the  document  here.  The  abstract  is  typically  a  short  summary  of  the  contents  of   the  document.]  

2 (15) SW design document Group Confidential 10/17/2011

ACRONYME NBPM: Narrow Band Power Measurement. RB: Resource Block RFGUI: Radio Frequency Graphical User Interface. RF: Radio Frequency HW: Hardware SF: Sub Frame BB: Base Band

Renesas Mobile Dennis M Senyonjo/S.Balducci

3 (15) SW design document Group Confidential Renesas Mobile Dennis M Senyonjo/S.Balducci

10/17/2011 1. VERSIONS HISTORY Version

author

Comments

0.1 0.2 0.3

Dennis M Senyonjo/S.Balducci Dennis M Senyonjo Dennis M Senyonjo

Draft version Update after phase 1 Updated TX dynamic SF and combined RX/TX

4 (15) SW design document Group Confidential Renesas Mobile Dennis M Senyonjo/S.Balducci

10/17/2011 2. INTRODUCTION

This document describes the local mode functionalities and design implementation for EUTRAN.

3. SCOPE AND USAGE: The local mode is a tool allowing the very basic verification of the complete UE including the RF modem. It is possible to make basic verification of the RF- BB functionalities, i.e check if commands and data are sent or executed properly, change the band, channel, power, expected received RF power level to set the AGC… . In addition it also provides mean for the RF team to debug and measure the RF HW performances via the different data streams (0, 1, random or PN9) on the TX side while on the RX side the narrow band measurement (NBPM) from the modem is provided. Flexible configuration should be possible for each sub-frame however this work is not implemented yet.

4. LOCAL MODE ARCHITECTURE: The Figure 1 shows the overview of the local mode architecture. The advantage of this is that the BB test SW uses the BB HAL interface which means that all the changes and update behind that interface would be transparent to the local mode resulting in a low maintenance effort. Most of the changes would take place in either BB test SW or RF test SW.

Figure 1

Message flow overview: The RFGUI sends an ISI message to Mexe test server (OS task) with the RF control parameters. The message is routed further to the RF test server in RF test SW. After receiving the test message with the control parameters, the RF test server will turn ON the RF HW and setup the RF HW and calls the corresponding l1_utils interface functions according to the requested test (RX. TX). Depending upon the received command from l1_utils interface functions, the BB test server in BB Test SW would request the service to L1 SW driver via the BB HAL interface. When done, a response message is sent from RF test server back to the os task handler and further on to the trace interface (not shown on the picture above). Note that the messaging flow from the BB HAL would be also available at Fasttrace/Ntrace. The RF is then running continuously until a STOP request message is received. The STOP message would stop the RF test control loop after a delay of 1 radio frames and, turn the RF OFF.

5 (15) SW design document Group Confidential Renesas Mobile Dennis M Senyonjo/S.Balducci

10/17/2011 4.1 RFGUI interface: Figure 2 shows the RFGUI interface and the configurable parameters.

Figure 3: RFGUI configuration panel in EUTRAN.

4.1.1 General configurable parameters Band Path1: main path, valid for both Rx and Tx. Path2: diversity path, valid for Rx only 4.1.2 Commands Rx Tx Stop. 4.1.3 Control parameters in Tx: Currently the following parameters are to be configured in TX: Channel. Power. Tx data type: 0,1, random and PN9. Modulation for each SF. Modulation type: QPSK/16QAM.

6 (15) SW design document Group Confidential Renesas Mobile Dennis M Senyonjo/S.Balducci

10/17/2011 Number of resource block: RB for each SF. The number of resource block offset for each SF. The target is to be able to configure also:

Power for each SF. Power reduction. Exended Cyclic prefix for each SF. 4.1.4 Control parameters in Rx: Currently the following parameters are configurable in Rx: Channel. Power level The target is to able to configure:

The channel for each SF. The power for each SF. All these parameters are passed to the RF test server and further to the modem via a specific interface in local mode which would be described in 4.3.

4.2 RF test server: The RF test server (rf_hal_test_control.c) is responsible for handling the test request messages originaly from the RFGUI. Figure 4 shows the location of the test server in CMSynergy. After receiving a request from the RFGUI (C_HAL_RF_TEST_CONTROL_REQ) the rf test server is initialized (init_rhtc), the test loop control is started (rhts_test_loop_set) and the RF is powered up. The corresponding test command (eutran_rf hal_rx_test_control, eutran_rf hal_tx_test_control, c_hal_rf_test_control_stop) is running with specified control parameters. The corresponding interface functions in l1_utils.c is called (l1_lte_rx_start, l1_lte_rx_stop, l1_lte_ebb_hal_ul_start, l1_lte_ebb_hal_ul_stop).

7 (15) SW design document Group Confidential Renesas Mobile Dennis M Senyonjo/S.Balducci

10/17/2011

Figure 4: rf hal test server.

4.3 Interface between RF and digital BB (Modem): In local mode, the RF test server under rf_hal (rf_hal_test_control.c) would not have direct access to the Modem SW. Instead it uses l1_utils interface function (l1_utils.c) located under gsm_sw. Figure 5 shows the location of the interface function l1_utils.c in CMSynergy.

8 (15) SW design document Group Confidential Renesas Mobile Dennis M Senyonjo/S.Balducci

10/17/2011 Figure 5: l1_utils.c

The current interface functions (l1_lte_ebb_hal_ul_start, l1_lte_ebb_hal_ul_stop, l1_lte_rx_start, l1_lte_rx_stop) allows the RF test server to request to the modem a Tx start with the control parameters given in 4.1.3 and a Tx stop; an Rx start with the control parameters given in 4.1.4 and an Rx stop. The individual SF configuration is not supported yet for RX. It is partly supported for TX. 4.3.1 l1_lte_ebb_hal_ul_start(bw, ul_format, subframes). This function should be called to start the local mode TX. The needed parameters for this function are: uint8 bw uint8 ul_format void* subframes In practice the function l1_lte_ebb_hal_ul_start sends 2 messages to BB HW test server: l1_lte_send_ul_sf_req(bw, 0, subframes) l1_lte_send_ul_sf_req(bw, 1, subframes) l1_lte_send_rxtx_req(bw, command, control, modulation, rb_start_index, rb_count); l1_lte_send_emac_init_req(ul_format, emac_command)

The first two messages send a UL_SF_REQ, where the first contains the sub frame 1-5 and the second 6–9. The second message send rx/tx request to enable a continous tx loop in PUSCH format. It contains configuration for sub frame 0. The seconds sends EMAC_INIT_REQ to enable an UL configuration. Parameters in the functions called are: uint32 control = (E_USE_LOOPED_TX|E_USE_UL_SF_CONFIGS) sets the TX in continous loop. uint32 command = E_ENABLE_PUSCH sets the modem to TX mode. uint8 emac_command = E_ENABLE_UL sets the modem to TX mode. uint8 ul_format = E_BITS_ZEROS, E_BITS_ONES, E_BITS_RANDOM, E_BITS_PN9 prepares the modem to send data in PUSCH mode. Bw, ul_format, modulation, rb_start_index, rb_count are set by the user.

4.3.2 l1_lte_ebb_hal_ul_stop(). This function should be called to stop the local mode TX. No parameter is needed for the function call e.g. the parameters are set to default and the most important one is to disable TX E_DISABLE_UL. bw = EPHY_TEST_EUTRAN_BW_0140MHZ; ul_format = E_BITS_ZEROS; modulation = E_BB_MODULATION_QPSK; rb_start_index= rb_count=9

0

9 (15) SW design document Group Confidential Renesas Mobile Dennis M Senyonjo/S.Balducci

10/17/2011 4.3.3 l1_lte_rx_start (bw). This function should be called to start the local mode RX.

In practice l1_lte_rx_start sends 2 messages to BB HW test server. Only needed parameter is the selected bandwidth

bw.

l1_lte_rx_local_mode_send_rxtx_req(bw, command, control); l1_lte_rx_local_mode_send_emac_init_req(emac_command); The first message sends a rx/tx request to enable a NBPM. The seconds sends EMAC_INIT_REQ to enable the DL configuration. Parameters in the functions called are: uint32 control = 0x00000000; uint8 emac_command = E_ENABLE_DL; uint32 command = E_ENABLE_PM;

Both RX paths main and diversity are enabled by default for the EFE to be able to report the Narrow Band Power Measurement (NBPM). 4.3.4 l1_lte_rx_stop(). This function should be called to stop the local mode RX. No parameter is needed e.g. the parameters are set to default and the most important one is to disable the NBPM: E_DISABLE_PM. bw = EPHY_TEST_EUTRAN_BW_0140MHZ;

4.3.5 l1_lte_rx_nb_power_get(uint8 rf_path) To get the NBPM from BB HAL (e.g EFE) for a specific RX path, this function must be called in RF HAL (rf_hal_testcontrol.c). The returned results are the NBPM in dBm etest_nbpm_db[0], etest_nbpm_db[1] in int16_q6 format. However further calculations are needed depending on the AGC headroom (AGC_headroom) and the digital part in the RF design as indicated by [

Equation 1]. The reported NBPM from BB HAL nbpm_dbm needs to be adjusted in order to get the correct RF power at antenna port. RF power at the antenna input PNant according to the equation [

Equation 1]: =

_

[ ]−(

+

−

_

)

Equation 1

Where: AGC_headroom is the allocated headroom in dB for the chosen RF. For LinkoE 15dB has been allocated. Psat_rxdfe is the maximum RF power that can be represented in didital format (depending on the ADC bits). As an example, the Psat_rxdfe is set to 57.2 dB for LinkoE RF. Pant_prov is the expected RF power. In the context of local mode this the dBm level provided by the RF GUI.

10 (15) SW design document Group Confidential Renesas Mobile Dennis M Senyonjo/S.Balducci

10/17/2011

Note: There has been a preliminary definition of the l1_utils functions in [15] but this document needs to be updated to the current implementation. 4.3.6 Combined RX/TX This special case is also supported. For example if ‘force RX before TX’ option is selected in RFGUI. Then l1_lte_rx_start will be called first and start RX. After which directly l1_lte_ebb_hal_ul_start will be called. It will handle combined RX/TX. In practice it means it will first stop RX and then send the same messages with the same parameters except for these: uint8 emac_command = (E_ENABLE_DL| E_ENABLE_UL); uint32 command = (E_ENABLE_PM| E_ENABLE_PUSCH)

4.4 BB HW test server: The BB HW test server was originaly designed for BB HW validation test but it has been extended to include the local mode for the RF verification purpose also. The main advantage of this test server is that it is able to send/receive the messages to/from BB HAL. However the test messages were sent via Fasttrace message sender. Changes are therefore needed to be able to send messages from RFGUI using l1_utils interface functions. One potential major drawback of using the BB HW test server is that this code would not be part of the final release to customers and therefor the local mode would not be supported in for example in after sales service centers where the phones need to be reworked. Figure 6 shows the location of the HW test server in CMSynergy.

11 (15) SW design document Group Confidential Renesas Mobile Dennis M Senyonjo/S.Balducci

10/17/2011

Figure 6: HW test server

Most of the changes needed for the local mode are done in the functions below: Etest_rx_msg.c Etest_rx_sstm.c Etest_stm.c Etest_stm.h Etest_tx_sstm.c Etest_tx_msg.c

4.5 SW design: 4.5.1 Rx local mode 4.5.1.1 Phase 1: The phase1 design does not have the possibility to configure the SF parameters (channel, gain). - The control parameters are set by the user in the RFGUI (band, channel, power level in dBm and the rx path).

12 (15) SW design document Group Confidential Renesas Mobile Dennis M Senyonjo/S.Balducci

10/17/2011

-

Upon the Rx activation the RFGUI sends the control parameters to the ISI message router C_HAL_RF_TEST_CONTROL_REQ which forwards the message to test message handler (rf_hal_test_control.c). The test message handler sets up the test control loop and calls the l1_utils interface function l1_lte_rx_start and initializes the RF HW. The AFC tuning word is also sent to RFDD to set the AFC control to the specified value.

-

Upon the l1_lte_rx_start call, 2 messages are sent from l1_utils in gsm_sw to initialize the BB test server to send and receive messages to and from BB HAL: l1_lte_rx_local_mode_send_ txrx_req and l1_lte_local_mode_emac_init_req. The txrx_req initializes the BB HAL by sending an E_BB_DL_CONFIG_REQ message to it while the emac_ init_req emulates the upper layer messaging which are not available in local mode. After the BB test server receives the E_BB_DL_CONFIG_RESP message, the E_BB_POWER_MEAS_REQ is sent to BB HAL using etest_rx_dl_pm_req_s to request a continous power measurement. BB HAL will return E_BB_POWER_MEAS_RESP followed by EHW_EFE_PM_READY_NTF and E_BB_POWER_MEAS_IND_RESP which includes the narrow band power measurement (NBPM) results. The NBPM is returned in dBm format and correction is needed in the rf_hal_test_control according to Equation 1. The NBPM will run continuously until a power measurement with a window_len = 0 is received.

-

When the C_HAL_RF_TEST_CONTROL_STOP_REQ is sent from the RFGUI similar messages are sent to the RF test message handler and from the BB test server, another l1_lte_rx_local_mode_send_ txrx_req is sent to BB HAL with window_len = 0. This wouldl stop the NBPM from BB HAL and upon reception of E_BB_DL_CONFIG_RESP the rx test state machine is terminated. On the RF side the test loop control is also stopped and the RF powered down.

-

Figure 7 shows the message flow in Rx local mode

13 (15) SW design document Group Confidential Renesas Mobile Dennis M Senyonjo/S.Balducci

10/17/2011

Figure 7: message flow in rx local mode.

4.5.1.2 Phase 2: It should be possible to configure the SF parameters (channel, gain). Work has not been started. 4.5.2 TX local mode 4.5.2.1 Phase 1: The phase1 design does not have the possibility to configure the SF parameters (channel, power level, modulation) and the power reduction scheme. The TX control parameters are valid for all SF in the radio frame. - The control parameters are set by the user in the RFGUI (band, channel, modulation on/off, modulation type (QPSK, 16QAM) data stream (0,1 random or PN9), power level). Note that the 0 and 1 data stream are valid only at the encoder input. -

Upon the TX activation the RFGUI sends the control parameters to the ISI message router C_HAL_RF_TEST_CONTROL_REQ which forwards the message to test message handler (rf_hal_test_control.c). The test message handler sets up the test control loop and calls the l1_utils interface function l1_lte_ebb_hal_ul_start and initializes the RF HW. The AFC tuning word is also sent to RFDD to set the AFC control to the specified value.

-

Upon the l1_lte_ebb_hal_ul_start call, 4 messages are sent from l1_utils in gsm_sw to initialize the BB test server to send and receive messages to and from BB HAL: l1_lte_send_ul_sf_req (two times), l1_lte_send_ txrx_req and l1_lte_send_emac_init_req.

14 (15) SW design document Group Confidential Renesas Mobile Dennis M Senyonjo/S.Balducci

10/17/2011

-

o

The txrx message further sends to BB HAL the E_BB_UL_CONFIG_REQ (using etest_tx_ul_config_req_s) to initialize BB HAL to TX with the required sample rate (e.g bandwidth).

o

When E_BB_UL_CONFIG_RESP is received etest_tx_ul_data_ind_s is sent to emac stub which returns EPHY_DL_DATA_IND message (using emac_ephy_ul_data_req_send) and the EPHY_UL_DATA_REQ message (via emac_ephy_ul_data_req_send)

o

When receiving the EPHY_UL_DATA_REQ, BB test server send to BB HAL E_BB_UL_TFI_CONFIG_REQ containing the all the remaining PUSH configuration parameters for all SF ( RB, resource block offset, modulation…)

o

BB HAL configure the SF accordingly and send the SF and returns E_BB_UL_TFI_CONFIG_RESP to BB test server which then resends another E_BB_UL_TFI_CONFIG_REQ and the loops continues until a stop request is received.

When the C_HAL_RF_TEST_CONTROL_STOP_REQ is sent from the RFGUI similar messages are sent to the RF test message handler and from the BB test server, another l1_lte_send_ txrx_req is sent to BB HAL with command word=0. This command would stop the BB HAL E_BB_UL_TFI_CONFIG_REQ the TX state machine is terminated. On the RF side the test loop control is also stopped and the RF powered down.

-

Figure 8: message flow in tx local mode.

4.5.2.2 Phase 2: Power and resource blocks are configurable for each SF. It has only been tested on kestrel_lte_r2. Updates are needed for RDF team before Gekko can be tested. 4.5.2.3 Phase 3: Power should be configurable for each SF.

15 (15) SW design document Group Confidential 10/17/2011 4.6 Reference: 1. Eutran L1 test SW, DocStore: 2255736099. 2. RF HAL L1 utilities API. 3. AS&IS – EUTRAN RX AGC 3.7.doc DCS07150-EN

Renesas Mobile Dennis M Senyonjo/S.Balducci