<bcs_config_params>
	<!-- Primary Flow monitor period in seconds -->
    <!-- This parameter denotes the monitor period for the device to
	acquire the Primary Flow message. -->
    <!-- Allowed range is 60 to 600 -->
	<T_primary_monitor>317</T_primary_monitor>
	
	<!-- This parameter denotes the time in seconds at which the device will give up on 
         attempting to acquire the Notification flow. -->
    <!-- Allowed range is 30 to 180-->
	<T_notification_fail>30</T_notification_fail>
	
	<!-- Config Flow Fail Timeout in seconds -->
    <!-- This parameter denotes the time (in seconds) after which the device 
         gives up when attempting a config message acquisition. -->
    <!-- Allowed range is 300 to 600 -->
	<T_config_flow_fail>300</T_config_flow_fail>
	
	<!-- This parameter defines the time (in seconds) interval at which the device will attempt
         transmission to the network when receiving notification of service delivery after the
	 guard.  This value is only used for determining frequency of transmission attempts if
         notification is received after the time guard period. -->
    <!-- Allowed range is 15 to 600 -->
	<T_post>300</T_post>
	
	<!-- This parameter defines the time (in seconds) the device will wait 
         for a response from a DNS query. -->
    <!-- Allowed Range is 15 to 90 -->
	<T_srv>60</T_srv>
	
	<!-- This parameter denotes the maximum waiting time (in seconds) for the device to
         acquire the HTTP header of the response message when making an HTTP request. -->
    <!-- Allowed Range is 15 to 90-->
    <T_header>60</T_header>
	
	<!-- This parameter denotes the maximum waiting time (in seconds) for the device to
         acquire either part or all of the HTTP message body in response message when waiting
	 for a unicast response message. -->
    <!-- Allowed range is 15 to 90 -->
    <T_body_chunk>60</T_body_chunk>
	
	<!-- This value is the minimum time (in seconds) between two Unicast request
         message delivery attempts. -->
    <!-- Allowed range is 5 to 90 -->
	<T_reattempt>60</T_reattempt>
	
	<!-- Timeout (in seconds) for bringing up the data session. -->
	<!-- Allowed range is 15 to 90 -->
	<T_data_session_timeout>45</T_data_session_timeout>
	
	<!-- Estimated maximum time (in seconds) needed to upload per kilobyte
         of the Usage Tracking log data over the Unicast connection. -->
    <!-- Allowed Range is 5 to 15 -->
	<T_usage_tracking_upload_1KB>8</T_usage_tracking_upload_1KB>
	
	<!-- BREW-directed SMS replay timeout in secs -->
	<!-- Allowed Range is 120 to 432000 -->
	<T_brew_sms_anti_replay>18000</T_brew_sms_anti_replay>
	
	<!-- This parameter defines the maximum number of transmission attempts the
         device is to make when the notification time is less than or equal to
	 the guard time. -->
    <!-- Allowed range is 1 to 5 -->
	<N_pre>4</N_pre>
	
	<!-- This parameter defines the maximum number of transmission attempts the
         device is to make when the notification time is greater than or equal
         to the guard time. -->
    <!-- Allowed range is 1 to 5 -->
	<N_post>3</N_post>
	
	<!-- This parameter defines the maximum number of delivery attempts for a Unicast
         message that are to be made by the device before the delivery of the request
         message permanently fails. -->
    <!-- Allowed Range is 1 to 5 -->
	<N_max_attempts>3</N_max_attempts>
	
	<!-- [SYS-BDSMS3-0020] The MediaFLO application shall process a BREW-Directed message 
	if CLI_BD_SMS_ENABLED is set to TRUE, otherwise discard it. -->
	<!-- Allowed values are true or false -->
	<brew_sms_enabled>true</brew_sms_enabled>
	
	<!-- T_header for user initiated transaction -->
	<!-- Allowed Range is 15 to 90-->
	<T_header_uinit>30</T_header_uinit>
	
	<!-- T_reattempt for user initiated transactions -->
	<!-- Allowed range is 5 to 90 -->
	<T_reattempt_uinit>30</T_reattempt_uinit>
	
	<!-- N_max_attempts for user initiated transactions -->
	<!-- Allowed Range is 1 to 5 -->
	<N_max_attempts_uinit>1</N_max_attempts_uinit>
	
	<!-- Parameter that determines the total time a device waits for resource (icons) acquisition. 
	This parameter is assumed to be the average time required to acquire 1 resource (icon). -->
	<!-- Allowed Range is 10 to 100 secs -->
	<T_config_rsrc>50</T_config_rsrc>
	
	<!-- Number of attempts made by the device to acquire resources (icons) -->
	<!-- Allowed Range is 1 to 10 -->
	<N_config_rsrc_attempts>3</N_config_rsrc_attempts>
	
	<!-- Time between any two attempts to acquire resources (icons) -->
	<!-- Allowed Range is 100 to 1000 sec -->
	<T_config_rsrc_reattempt>300</T_config_rsrc_reattempt>
	
	<!-- Flag that indicates whether unicast is allowed for acquired resources (icons) -->
	<!-- Allowed values are true or false -->
	<unicast_rsrc_msg_enabled>false</unicast_rsrc_msg_enabled>
	
	<!-- Hysterisis time for device to delete a resource (icon) that is not needed anymore as a result of mobility. -->
	<!-- Allowed Range is 43200 to 432000 secs  -->
	<T_config_rsrc_hysterisis>86400</T_config_rsrc_hysterisis>
	
	<!-- Hysterisis time to invalidate a config flow version of an old multiplex as a result of mobility. -->
	<!-- Allowed Range is 86400 to 864000 secs secs  -->
	<T_config_version_hysterisis>432000</T_config_version_hysterisis>
	
	<!-- At startup if system time is not valid, this interval will be used to monitor for valid time  -->
	<!-- Once time gets valid no more monitoring is done. -->
	<!-- Allowed Range is 30 to 3600 secs  -->
	<T_valid_time_monitor_interval>30</T_valid_time_monitor_interval>

    <!-- Flag to indicate if PIN reset via secret key sequence is allowed or not. -->
    <!-- System requirement for CLI_RESET_SEQUENCE_ENABLED -->
    <!-- Allowed values are true or false  -->
    <PIN_reset_sequence_enabled>true</PIN_reset_sequence_enabled>

    <!-- This parameter provides secret key sequence to reset PIN.
         Default value is 746 ("PIN"). -->
    <!-- System requirement for CLI_RESET_SEQUENCE -->
    <!-- Allowed range is 0 to 9999, both inclusive. -->
    <PIN_reset_sequence>746</PIN_reset_sequence>

	<!-- N_max_attempts for subscription sync triggered by a BREW directed SMS message -->
	<!-- Allowed Range is 1 to 5 -->
	<N_sms_sub_sync_attempts>2</N_sms_sub_sync_attempts>

	<!-- T_reattempt for subscription sync triggered by a BREW directed SMS message -->
	<!-- Allowed range is 5 to 90 -->
	<T_sms_sub_sync_reattempt>300</T_sms_sub_sync_reattempt>

</bcs_config_params>
