Share via

Connection policy configuration

  • Article

Connection policies are used by Connection Manager to identify the correct connection for a connection request. The following example shows an app-based MMS policy configuration. For a more detailed connectivity configuration sample, see Connectivity configuration.

Important  

For dual SIM phones, connection settings must be unique for each SIM. To ensure unique settings, OEMs can use the $(__MVID) macro as part of all connection names.

<Settings Path="Connections">
    <Setting Name="Policies/zzzcontoso_mms_policy $(__MVID)/SID" Value="{5B04B775-356B-4AA0-AAF8-6491FFEA5900}" />
    <Setting Name="Policies/zzzcontoso_mms_policy $(__MVID)/ClientType" Value="app" />
    <Setting Name="Policies/zzzcontoso_mms_policy $(__MVID)/Host" Value="*" />
    <Setting Name="Policies/zzzcontoso_mms_policy $(__MVID)/OrderedConnections" Value="0" />
    <Setting Name="Policies/zzzcontoso_mms_policy $(__MVID)/Conn000/Type" Value="CMST_CONNECTION_NAME" />
    <Setting Name="Policies/zzzcontoso_mms_policy $(__MVID)/Conn000/ConnectionId" Value="zzzcontoso_mms $(__MVID)" />
</Settings>

Important  

All APN, proxy, and policy entries referring to the same connection must be defined within the same <Settings> element in the answer file.

Each policy entry identifies one or more applications in combination with a host pattern. The policy entry is assigned a list of connection details that Connection Manager uses to satisfy connection requests matching the application and host patterns. Multiple policy entries are supported.

Policy Ordering: There is no explicit ordering of policies. The general rule is that the most concrete or specific policy mappings take a higher precedence.

Default Policies: Policies are applied in order of their scope with the most specific policies considered before the more general policies. The phone’s default behavior applies to all applications and all domains and is only used when no other, more specific policy is available. The default policy is to use any available Wi-Fi network first and then any available APN.

Settings

  • policy name
    Defines the name of the policy. In the above example, the policy name is “zzzcontoso_mms_policy $(__MVID)”.

  • SID
    The value of SID depends on the ClientType.

    For application-based mapping policies, SID is the application product ID in GUID format. The curly brackets {} around the GUID are required.

    For host-based mapping policies, SID must be set to *.

  • ClientType
    Specifies the mapping policy type.

    The following list describes the available mapping policy types:

    • Application-based mapping policies are applied to applications. To specify this mapping type, use the value app.

    • Host-based mapping policies are applied to all types of clients requesting connections to specified host(s). To specify this mapping type, use the value *.

  • Host
    Specifies the name of a host pattern. The host name is matched to the connection request to select the right policy to use.

    The host pattern can have two wild cards, "*" and "+". The host pattern is not a URL pattern and there is no concept of transport or paths on the specific host. For example, the host pattern might be "*.host_name.com" to match any prefix to the host_name.com domains. The host pattern will match "www.host_name.com" and "mail.host_name.com", but it will not match "host_name.com".

  • OrderedConnections
    Specifies whether the list of connections is in preference order.

    A value of "0" specifies that the connections are not listed in order of preference. A value of "1" indicates that the listed connections are in order of preference.

  • ConnXXX
    Enumerates the connections associated with the policy. Element names begin with "Conn" followed by three digits which increment starting from "000". For example, a policy which applied to five connections would have element entries named "Conn000", "Conn001", "Conn002", "Conn003", and "Conn004".

  • ConnectionID
    Specifies a unique identifier for a connection within a group of connections. The exact value is based on the Type parameter.

    For CMST_CONNECTION_NAME, specify the connection name. For example, if you have a connection configured from APN configuration, the connection name could be the name of the connection. If you have a NAP configured with the NAPID set to “GPRS1”, the connection name could be “GPRS1@WAP”.

    For CMST_CONNECTION_TYPE, specify the GUID for the desired connection type. The curly brackets {} around the GUID are required. The following connection types are available:

    Connection type GUID

    GSM

    {A05DC613-E393-40ad-AA89-CCCE04277CD9}

    CDMA

    {274AD55A-4A70-4E35-93B3-AE2D2E6727FC}

    Legacy 3GPP

    {6DE4C04B-B74E-47FA-99E5-8F2097C06A92}

    LTE

    {2378E547-8312-46A5-905E-5C581E92693B}

    Wi-Fi

    {8568B401-858E-4B7B-B3DF-0FD4927F131B}

    Wi-Fi hotspot

    {072FC7DC-1D93-40D1-9BB0-2114D7D73434}

     

    For CMST_CONNECTION_NETWORK_TYPE, specify the GUID for the desired network type. The curly brackets {} around the GUID are required. The following network types are available:

    Network type GUID

    GPRS

    {AFB7D659-FC1F-4EA5-BDD0-0FDA62676D96}

    1XRTT

    {B1E700AE-A62F-49FF-9BBE-B880C995F27D}

    EDGE

    {C347F8EC-7095-423D-B838-7C7A7F38CD03}

    WCDMA UMTS

    {A72F04C6-9BE6-4151-B5EF-15A53E12C482}

    WCDMA FOMA

    {B8326098-F845-42F3-804E-8CC3FF7B50B4}

    1XEVDO

    {DD42DF39-EBDF-407C-8146-1685416401B2}

    1XEVDV

    {61BF1BFD-5218-4CD4-949C-241CA3F326F6}

    HSPA HSDPA

    {047F7282-BABD-4893-AA77-B8B312657F8C}

    HSPA HSUPA

    {1536A1C6-A4AF-423C-8884-6BDDA3656F84}

    LTE

    {B41CBF43-6994-46FF-9C2F-D6CA6D45889B}

    EHRPD

    {7CFA04A5-0F3F-445C-88A4-C86ED2AD94EA}

    Ethernet 10Mbps

    {97D3D1B3-854A-4C32-BD1C-C13069078370}

    Ethernet 100Mbps

    {A8F4FE66-8D04-43F5-9DD2-2A85BD21029B}

    Ethernet Gbps

    {556C1E6B-B8D4-448E-836D-9451BA4CCE75}

     

    For CMST_CONNECTION_DEVICE_TYPE, specify the GUID for the desired device type. The curly brackets {} around the GUID are required. The following device types are available:

    Device type GUID

    Cellular device

    {F9A53167-4016-4198-9B41-86D9522DC019}

    Ethernet

    {97844272-00C7-4572-B20A-D8D861C095F2}

    Bluetooth

    {1D793123-701A-4fd0-B6AE-9C3C57E99C2C}

    Virtual

    {EAA02CE5-9C70-4E87-97FE-55C9DEC847D4}

     

  • Type
    Specifies the type of connection being referenced. The following list describes the available connection types:

    • CMST_CONNECTION_NAME – A connection specified by name.

    • CMST_CONNECTION_TYPE – Any connection of a specified type.

    • CMST_CONNECTION_NETWORK_TYPE – Any connection of a specified device type.

    • CMST_CONNECTION_DEVICE_TYPE – Any connection of the specified network type.

Connectivity configuration

APN configuration

Proxy configuration

 

 

Send comments about this topic to Microsoft