<bcs_prov>

    <!-- FDS-AS3-0048 Billing and Customer Service ID -->
    <!-- This parameter is also used in determining App Id. -->
    <!-- App Id consists of bcs_id, bcs_reserved_value and device_type  -->
    <!-- IMPORTANT: This parameter has to be defined and provisioned -->
    <bcs_id>100</bcs_id>
	
	<!-- FDS-AS3-0027 CLI_NO_PACKAGE_SUBSCRIPTION_TIMER -->
    <!-- Time interval, in unit of hour, at which the device automatically transitions into vacation 
	state as the device does not have any non-auto-subscribed package subscription.. -->
    <!-- Allowed range is 1 to 720 --> 
    <!--<no_pkg_sub_timer>360</no_pkg_sub_timer>-->
	
	<!-- SYS-UNI3-005 Default domain name used to resolve hostnames of MediaFLO servers. -->
	<!-- IMPORTANT: This parameter has to be defined and provisioned -->
    <mediaflo_domain>525-flo.mediaflousa.com</mediaflo_domain>

    <!-- FDS-AS3-0122 and FDS-AS3-0123 HTTP Proxy Configuration
    This parameter determines if the MediaFLO client should relay the
    activation request through a HTTP proxy (WAP gateway).

    If set to 0, MediaFLO client will send activation request directly
    to the SBS.

    If set to 1, MediaFLO client will use the HTTP proxy host and port
    information provided by appropriate APIs on the device platform. Note
    that OEM support may be required.
    -->
    <!-- <http_proxy>0</http_proxy> -->

    <!-- FDS-UNI3-0254 Additional HTTP header(s) meant for proxy

    This parameters allows extra HTTP header(s) required by the HTTP proxy
    (see http_proxy) to be inserted into the activation request.

    Note that this parameter value should contain properly formatted HTTP
    header(s) including CRLF(s)

    NOTE: The "1" in the following example setting should be replaced
    with the correct BCS ID. See bcs_id.
    -->
    <http_hdrs_for_proxy>User-Agent: MediaFLO-Client-1
Accept: */*
Accept-Language: *
x-wap-profile: &quot;http://www.mediaflo.com/uaprof/client_1.xml&quot;
</http_hdrs_for_proxy>

    <!-- Optional HTTP Proxy Configuration
    This parameter allows for the update subscription request to be
    relayed via the HTTP proxy as well.

    Note that this parameter will take effect only if HTTP proxy is enabled.
    See http_proxy.
    -->
    <!-- <relay_update_sub_via_proxy>false</relay_update_sub_via_proxy> -->

	<!-- FDS-AS3-0109 Check for memory upon activation policy-->
    <!--<check_memory_upon_activation>on</check_memory_upon_activation>-->
	
    <!-- [FDS-MM3-0032] The device shall be provisioned with the CLI_MEM_MARGIN 
         parameter in the device configuration file. (assume units of KB)-->
    <!--<margin_memory>0</margin_memory>-->

    <!-- Device ID formatting policy -->
    <!-- Following table shows the permissible values and corresponding formats:

        Value   Format
        =====   ======
        0       'E' + 15 digits of IMSI + 8 hex digits of ESN
        1       'M' + MDN
        2       'I' + 14 digits of IMEI
        3       'N' + 8 hex digits of ESN
        255     NONE (Note: this parameter not included in activation request)

        NOTE: Values 0 & 3 are valid only on CDMA devices, and 2 is
        valid only on UMTS ones.
    -->
    <!-- IMPORTANT: This parameter has to be defined and provisioned -->
    <device_id_format>1</device_id_format>

    <!-- Service Account formatting policy -->
    <!-- Following table shows the permissible values and corresponding formats:

        Value   Format
        =====   ======
        0       MIN
        1       MDN
        2       IMSI
        255     NONE (Note: this parameter not included in activation request)
    -->
    <!-- IMPORTANT: This parameter has to be defined and provisioned -->
    <service_account_format>1</service_account_format>

    <!-- Destination Address formatting policy -->
    <!-- Following table shows the permissible values and corresponding formats:

        Value   Format
        =====   ======
        0       MDN
        255     NONE (Note: this parameter not included in activation request)
    -->
    <!-- IMPORTANT: This parameter has to be defined and provisioned -->
    <destination_address_format>0</destination_address_format>

    <!-- FDS-AS3-0112 Client initiated unsubscription from root package policy-->
    <!--<client_initiated_unsub_root_allowed>on</client_initiated_unsub_root_allowed>-->

    <!-- FDS-AS3-#TBD Subscription sync upon launch in unsub state -->
    <subsync_upon_launch_in_unsub_state>true</subsync_upon_launch_in_unsub_state>

    <!-- New in R3.5  -->
    <!--
        MediaFLO supports multiple user profiles on the device. Each
        profile is associated with an ID (MDN for CDMA, IMSI for GSM)
        and contains user specific data including, but not limited to,
        device encryption/decryption keys, subscriber ID, etc.

        The maximum number of user profiles stored on the device is
        controlled by the following parameter. When creating a new
        profile, if the total number of profiles exceeds the maximum,
        the device will delete the excess in a least-recently-used (LRU)
        order.

        Note: The value 0 (zero) indicates infinite number of profiles.
    -->
    <!--<max_user_profile>0</max_user_profile>-->

	<!-- Device profile ID represents the set of capabilities supported by the device.
	This configuration parameter is transmitted from the server to the device -->
    <device_profile_id>2</device_profile_id>
	
	<!-- IMPORTANT: The following 2 parameters have to be defined and provisioned -->
	<init_bcs_class_msg_ver>0</init_bcs_class_msg_ver>
	<init_bcs_config_file_ver>0</init_bcs_config_file_ver>

    <!-- FDS-AS3-#TBD Subscription sync upon launch of SIM enabled device -->
    <!--<subsync_mf_launch_sim>false</subsync_mf_launch_sim>-->
    
    <!-- This provisioned parameter indicates if the following check is
         to be performed or not:
         Check if storage requirement for clipcast services is met when 
         processing subscription request. 
         Default behavior is not to perform this check. -->
    <!-- Allowed values are "on" and "off". -->
    <!--<check_memory_upon_subscription>off</check_memory_upon_subscription>-->
    
</bcs_prov>
