See Also
 Important: |
|---|
| This is retired content. This content is outdated and is no longer being maintained. It is provided as a courtesy for individuals who are still using these technologies. This content may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist. |
The CM_MappingsConfiguration Service Provider configures the URL mapping that is used by the ConnMgrMapURLfunction to determine the meta-network where the URL resides.
The meta-network GUID must be provisioned using the CM_Networks Configuration Service Providerbefore provisioning a URL mapping to the meta-network or anything that requires the meta-network GUID.
 Note: |
|---|
| This Configuration Service Provider is managed over the OMA Client Provisioning (formerly WAP Client Provisioning) protocol. To provision devices using the OMA DM protocol, use the ACCESS Configuration Service Providerinstead. Access to this Configuration Service Provider is determined by Security roles. Because OEMs and Mobile Operators can selectively disallow access, ask them about the availability of this Configuration Service Provider. |
The following table shows the default settings. The default security role maps to each subnode unless specific permission is granted to the subnode.
|
Permissions |
Read/Write |
|
Roles allowed to query and update setting |
Manager |
The following image shows the Configuration Service Provider in tree format as used by OMA Client Provisioning.
Characteristics
- <MappingIndex>
-
Specifies settings for the <MappingIndex> parameter. Entries in the mapping table are provisioned and ordered by their MappingIndex value. When mapping URLs, the ConnMgrMapURLsearches the table, starting at the lowest MappingIndex and moving up the list of values from lowest to highest until the first matching pattern is found. Entries with a more specific pattern must be assigned a lower index number than the more general entries. Entries do not need to be contiguous.
The first 500 index numbers (0-500) are reserved for internal use only. User defined exceptions start at 0x01000000 (16777216). By default, the index numbers 0x20000000 (536870912), 0x21000000 (553648128), 0x22000000 (570425344) and 0x23000000 (587202560), are used to map URL strings to the default meta-networks, as shown in the following table.
Parameter pattern value Index Number Network name *://*.*/*
570425344
The Internet
*://*/*
587202560
Work
wsp://*/*
536870912
The WAP Network
wsps://*/*
553648128
Secure WAP Network
Parameters
- Network
-
Used in the <MappingIndex> characteristic to provide the Network GUID where the URL resides.
The following table shows the default settings.
Permissions
Read/Write
Data type
String
Label
Network GUID
Roles allowed to query and update setting
Manager
- Pattern
-
Used in the <MappingIndex> characteristic to provide the URL pattern in a wildcard pattern that is used to match the URL string. The string must be in canonicalized URL format. For example, a blank space in the URL should be converted to the escape sequence %20.
The following table shows the default settings.
Permissions
Read/Write
Data type
String
Label
URL Pattern
Semantic Type
url
Roles allowed to query and update setting
Manager
Microsoft Custom Elements
The following table shows the Microsoft custom elements that this Configuration Service Provider supports for OMA Client Provisioning.
| Elements | Available |
|---|---|
|
noparm |
No |
|
nocharacteristic |
Yes |
|
characteristic-query |
Yes recursive query: Yes |
|
parm-query |
Yes |
Use these elements to build standard OMA Client Provisioning (formerly WAP Client Provisioning) configuration XML. For information about specific elements, see MSPROV DTD Elements. For examples of how to generally use the Microsoft custom elements, see OMA Client Provisioning XML File Examples.
For information about OMA Client Provisioning, see OMA Client Provisioning Files.