Initializing Multicarrier Mode

This section describes how to use API functions to initialize multicarrier mode.

Note: See an example of the API usage in the lte_enb_as.pr.m LTE process model.

Procedure 5: Initializing Multicarrier Mode

  1. Create a function callback that initializes the PHY framing characteristics.

    1.1 Indicate to the PHY module that a multicarrier initialization will be required by using oms_wp_phy_attr_module_intialize_multi_carrier().

    This will switch the PHY module of the advanced wireless package into multicarrier mode and will make the advanced wireless package wait until the initialization information is provided. This will allow the client module to collect all necessary information (e.g., read attributes, obtain data from other modules via `oms_pr`).
    
    Example:
    
    ```c
    phy_module_hdl = oms_wp_phy_attr_module_intialize_multi_carrier(phy_module_name);
    ```
    
  2. Set the PHY initialization information to the PHY handle.

    Once all the initialization information is available, the client process can enter the information into the PHY handle by using oms_wp_phy_module_attr_set(). The PHY properties in the following example are mandatory for multicarrier mode:

    oms_wp_phy_module_attr_set (phy_module_hdl,
    	OMSC_WP_ATTR_PHY_TYPE, 					OmsC_WP_OFDMA,
    	OMSC_WP_ATTR_PHY_MODEL, 					OmsC_WP_Lte_Ofdma,
    	OMSC_WP_ATTR_PHY_CELL_ID, 					enb_id,
    	OMSC_WP_ATTR_PHY_MAC_TO_PHY_PARAMS_CONVERT_PROC,	(void*)
    	lte_support_mac_config_to_phy_convert,
    	OMSC_WP_ATTR_PHY_CLIENT_INFO,			 (void*) &chnl_descriptor,
    	OMSC_WP_ATTR_PHY_MCARRIER_SUBBAND_MEASURE_PROC, (void*) OPC_NIL,
    	OMSC_WP_ATTR_ARG_END);
    
    • In the example above, the first two properties indicate that the PHY type is configured as OFDMA (which must be used, in general, when using multicarrier mode) with the particular LTE OFDMA model implementation. Alternatively, LTE SCFDMA can also be specified (currently used in the LTE model for uplink transmissions, as in the process model lte_ue_as.pr.m).

    • A cell ID must be provided. The current multicarrier model implementation assumes that the network topology is point-to-multipoint, and the cell ID is used to associate the client nodes (e.g., LTE UEs) with the cell base station nodes (e.g., LTE eNodeBs).

    • The property OMSC_WP_ATTR_PHY_MAC_TO_PHY_PARAMS_CONVERT_PROC is a function callback that initializes the frame characteristics of the multicarrier system. In this example, the function provided (lte_support_mac_config_to_phy_convert) prepares the frequency and timing information to the PHY module to work under LTE specifications, the function must fill this information into a data structure of type WrlsT_Phy_Bw_Profile, which the PHY module uses to define the radio frame. Please see the external file lte_support.ex.c to observe the actual definition of the callback function lte_support_mac_config_to_phy_convert.

    • The function callback specified for property OMSC_WP_ATTR_PHY_MAC_TO_PHY_PARAMS_CONVERT_PROC must receive an argument with the necessary information to perform such initialization. That argument is passed in the property OMSC_WP_ATTR_PHY_CLIENT_INFO, which in the example above passes a pre-defined data structure that the callback expects to receive with the information.

  3. Commit the PHY handle's new settings into the actual PHY module.

    In this case, the commit operation must use oms_wp_phy_module_activate(), as it also restarts the PHY module initialization. During the simulation, the function oms_wp_phy_module_changes_commit() can be used to commit new property changes made to the PHY handle. Typically those changes are applied to the client nodes (e.g., UEs), as they may change their association and PHY settings across various cells.

End of Procedure 5