eMBMS Middleware Provisioning Parameters: Profile Specification Release 3.2

Qualcomm Technologies, Inc.
eMBMS Middleware Provisioning Parameters

Profile Specification Release 3.2
80-B7411-6 Rev. A
April 20, 2015
Confidential and Proprietary – Qualcomm Technologies, Inc.
NO PUBLIC DISCLOSURE PERMITTED: Please report postings of this document on public servers or websites to:
DocCtrlAgent@qualcomm.com.
Restricted Distribution: Not to be distributed to anyone who is not an employee of either Qualcomm Technologies, Inc. or its affiliated
companies without the express approval of Qualcomm Configuration Management.
Not to be used, copied, reproduced, or modified in whole or in part, nor its contents revealed in any manner to others without the express
written permission of Qualcomm Technologies, Inc.
Qualcomm RaptorQ is a product of Qualcomm Technologies, Inc. Other Qualcomm products referenced herein are products of Qualcomm
Technologies, Inc. or its other subsidiaries.
This technical data may be subject to U.S. and international export, re-export, or transfer (“export”) laws. Diversion contrary to U.S. and
international law is strictly prohibited.
© 2015 Qualcomm Technologies, Inc. All rights reserved.

Questions or comments: Questions or comments: https://support.cdmatech.com/
Qualcomm and RaptorQ are trademarks of Qualcomm Incorporated, registered in the United States and other countries. All
Qualcomm Incorporated trademarks are used with permission. Other product and brand names may be trademarks or registered
trademarks of their respective owners.
Qualcomm Technologies, Inc.

5775 Morehouse Drive
San Diego, CA 92121
U.S.A.
Revision history
Revision Date Description
A April 2015 Initial release
80-B7411-6 Rev. A Confidential and Proprietary – Qualcomm Technologies, Inc. 3

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION
Contents
1 Introduction ........................................................................................................................... 6
1.1 Scope.........................................................................................................................................................6
1.2 Document organization ..............................................................................................................................6
1.3 Acronyms ...................................................................................................................................................6
1.4 References ................................................................................................................................................7
2 Middleware Provisioning Parameters .................................................................................. 8

2.1 Introduction ................................................................................................................................................8
2.2 Provisioning parameters ............................................................................................................................9
2.2.1 CarrierNetworkParams ........................................................................................................... 10
2.2.2 OEMParams ........................................................................................................................... 22
A Provisioning XML Schema..................................................................................................28

A.1 Provisioning XML schema ....................................................................................................................... 28
Figures
Figure 2-1 MSDC device parameters .............................................................................................................................8
Figure 2-2 CycleTimes ................................................................................................................................................. 10
Figure 2-3 FECProcessingMaxMemorySize ................................................................................................................ 12
Figure 2-4 FileSystemWriteSpeed ............................................................................................................................... 12
Figure 2-5 MSDCServiceClass .................................................................................................................................... 12
Figure 2-6 ServiceDiscoveryBootstrap ......................................................................................................................... 14
Figure 2-7 ReceptionReportingTemplateURL .............................................................................................................. 15
Figure 2-8 FileRepairTemplateURL ............................................................................................................................. 15
Figure 2-9 ServiceDiscoveryNumberOfRetries ............................................................................................................ 16
Figure 2-10 AccessPointNameMapping ....................................................................................................................... 16
Figure 2-11 NetworkConstraintForADP........................................................................................................................ 17
Figure 2-12 RSSIPollingInterval ................................................................................................................................... 17
Figure 2-13 MaxNumberOfFileDeliveryTables ............................................................................................................. 17
Figure 2-14 MaxReceptionReportingStorageSize ........................................................................................................ 18
Figure 2-15 MaxUnnotifiedFileDownloadQuota ........................................................................................................... 18
Figure 2-16 NumberOfRegistrationWithSameServiceClass ......................................................................................... 19
Figure 2-17 NumberOfConcurrentFileDownload .......................................................................................................... 19
Figure 2-18 NumberOfConcurrentStreaming ............................................................................................................... 20
Figure 2-19 UnicastFetchForDASH.............................................................................................................................. 20
Figure 2-20 Carrier PLMN list....................................................................................................................................... 20
Figure 2-21 StorageFileDelivery................................................................................................................................... 21
Figure 2-22 MaxUnnotifiedFileDownloadQuotaExtension ............................................................................................ 21
Figure 2-23 ScratchSpacePath .................................................................................................................................... 22
Figure 2-24 SuppressReceptionTime........................................................................................................................... 22
Figure 2-25 TMGIActivationTimeout ............................................................................................................................ 22
Figure 2-26 StreamingTMGIActivationRetryTimeOut ................................................................................................... 23

eMBMS Middleware Provisioning Parameters Profile Specification Release 3.2 Contents
Figure 2-27 MSDCSocketInterfacePort ........................................................................................................................ 23

Figure 2-28 DASHStreamingPort ................................................................................................................................. 24
Figure 2-29 TimeShiftBuffer ......................................................................................................................................... 24
Figure 2-30 DeviceType ............................................................................................................................................... 26
Figure 2-31 MSDCUpgradeCheckURI ......................................................................................................................... 26
Figure 2-32 DeviceCapabilities .................................................................................................................................... 26
Figure 2-33 HTTPFileDelivery ...................................................................................................................................... 27
Tables
Table 1-1 Acronyms and abbreviations .........................................................................................................................6
Table 1-2 References....................................................................................................................................................7
Table 2-1 Recommended memory settings for some typical scenarios ...................................................................... 11

1 Introduction
1.1 Scope
This document describes the middleware provisioning parameters. The parameters required by
evolved Multimedia Broadcast/Multicast Service (eMBMS) middleware function correctly on
eMBMS-capable User Equipment (UE). The parameters described use an Extensible Markup
Language (XML) schema. Therefore, the provisioning file is an XML that conforms to the
schema.
Currently, these parameters pre-provision with the eMBMS middleware. In later releases, this
document describes Over-The-Air (OTA) updates of the provisioning parameters.
1.2 Document organization

This document contains the following:
Chapter 1 – Introduction: Provides introductory information including scope, document
organization, acronyms, references, and document revision history.
Chapter 2 – Middleware Provisioning Parameters: Provides overview of the middleware
provisioning parameters.
Appendix A – Provisioning XML Schema: Provides code for the provisioning XML schema.
1.3 Acronyms
Table 1-1 lists the acronyms that appear in the document.
Table 1-1 Acronyms and abbreviations

Term Definition
3G Third Generation
4G Fourth Generation
ADP Associated Delivery Procedure
ADPD Associated Delivery Procedure Description
APN Access Point Name
CPU Central Processing Unit
DASH Dynamic Adaptive Streaming over HTTP
eMBMS evolved Multimedia Broadcast/Multicast Service
FDT File Delivery Table
FEC Forward Error Correction

eMBMS Middleware Provisioning Parameters Profile Specification Release 3.2 Introduction
Term Definition
FLUTE File Delivery over Unidirectional Transport
HTTPS Hypertext Transfer Protocol Secure
LTE Long Term Evolution
MCC Mobile Country Code
MNC Mobile Network Code
MSDC Multicast Service Device Client
OEM Original Equipment Manufacturer
OTA Over-The-Air
PLMN Public Land Mobile Network
RAM Random Access Memory
RSSI Received Signal Strength Indication
TCP Transmission Control Protocol
TMGI Temporary Mobile Group Identity
TSB Time-Shifted Buffer
UE User Equipment
URL Uniform Resource Locator
USD User Service Description
XML Extensible Markup Language
1.4 References
Table 1-2 References
Reference Document number Title
number
Q1 80-B7410-6 eMBMS Middleware Configuration Parameters Profile
Specification Release 3.2
Q2 80-W2333-1 FEC Settings and Behavior for Services Over eMBMS
Q3 80-B7222-1 RaptorQ™ FEC Settings and Behavior for Services Over
eMBMS

2 Middleware Provisioning Parameters
2.1 Introduction
The eMBMS capable UE installs with eMBMS middleware, which is referred to in this document
as Multicast Service Device Client (MSDC). MSDC contains parameters that are relevant for the
behavior of various features within the middleware. These parameters are grouped into two
categories: Configuration parameters (Config Params) and Provisioning parameters (Provisioning
params), shown in Figure 2-1. Configuration parameters are common across different types of UE
for a carrier network and frequently updatable OTA. Whereas values of the provisioning
parameters are device-specific and not expected to be changed OTA. Details of the configuration
parameters, OTA update mechanism, and eMBMS middleware behavior on these updates are
captured in [Q1].
Figure 2-1 MSDC device parameters
The provisioning parameters allow MSDC to function properly on eMBMS-capable UE. This
chapter describes the provisioning parameters in detail. Define the parameters using an XML
schema. Every UE with MSDC installed will have a provisioning XML file that conforms to the
provisioning XML schema described at the end of this document in Appendix A. Preinstall the
provisioning XML file by the Original Equipment Manufacturers (OEMs) on the UE along with
the middleware.

eMBMS Middleware Provisioning Parameters Profile Specification Release 3.2 Middleware Provisioning Parameters
One property of the provisioning parameters is that the values of the parameters may vary from
one type of UE and operator network to another. Different types of UE under the control of a
network operator may have provisioning XML files with different values of the provisioning
parameters depending on the device type. Moreover, the same type of UE may contain different
values of the provisioning parameters for deployment on different network operators.
Section 2.2 provides descriptions of the provisioning parameters. To have flexibility to extend the
schema, design the provisioning XML schema to be backward and forward compatible. Release
the new elements via extension schema(s) under different namespaces and the original schema
will import the extension schema(s). The “any##other” option at the end of the list of elements in
the schema, located in each element allows it to be extendable in the future. Sections 2.2.1 and
2.2.2 provide details about each of the elements in the provisioning XML schema.
2.2 Provisioning parameters

The provisioning XML schema contains a root element called MSDCProvisioningParams.
MSDCProvisioningParams contains an attribute named Version, which denotes the provisioning
schema version number.
The MSDCProvisioningParams consists of two elements, such as CarrierNetworkParams and
OEMParams, shown in Figure 2-1. These elements define two sets of provisioning parameters,
the network-operator specific parameters and the device-specific parameters respectively. The
CarrierNetworkParams elements are set by the network operators and may or may not be
dependent on device types, whereas the OEMParams are set by the OEMs and are specific to the
device types.
The CarrierNetworkParams element contains the following sub-elements:
 CycleTimes
 FECProcessingMaxMemorySize
 FileSystemWriteSpeed
 MSDCServiceClass
 ServiceDiscoveryBootstrap
 ReceptionReportingTemplateURL
 FileRepairTemplateURL
 ServiceDiscoveryNumberOfRetries
 AcessPointNameMapping
 NetworkConstraintForADP
 RSSIPollingInterval
 MaxNumberOfFileDeliveryTables
 MaxReceptionReportingStorageSize
 MaxUnnotifiedFileDownloadQuota
 NumberOfRegistrationWithSameServiceClass
 NumberOfConcurrentFileDownload
 NumberOfConcurrentStreaming

 UnicastFetchForDASH
 PLMN
 CarrierNetworkParamsExtension (with StorageFileDelivery and
CarrierNetworkParamsExtension1)
The OEMParams contains the following sub-elements:
 ScratchSpacePath
 SuppressReceptionTime
 TMGIActivationTimeout
 StreamingTMGIActivationRetryTimeOut
 MSDCSocketInterfacePort
 DASHStreamingPort
 TimeShiftedBuffer
 DeviceType
 MSDCUpgradeCheckURI
 DeviceCapabilities
 OEMParamsExtension (with HTTPFileDelivery)
2.2.1 CarrierNetworkParams
2.2.1.1 CycleTimes parameter

This optional parameter denotes the ratio of the MSDC duty cycle and sleep cycle time, in ms, for
using the Central Processing Unit (CPU). MSDC forces itself to sleep for the sleep cycle time
after running for the duration of the duty cycle time. This parameter ensures that the processing of
the MSDC does not throttle the CPU during CPU-intensive operations. Figure 2-2 shows the
element in detail.
Figure 2-2 CycleTimes

2.2.1.2 FECProcessingMaxMemorySize parameter

This optional parameter denotes the minimum required Random Access Memory (RAM) size that
is allocated at the middleware initialization for Forward Error Correction (FEC) processing of file
objects received via File Delivery over Unidirectional Transport (FLUTE) sessions in UE. This
memory is used for decoding objects received over any FLUTE session including segments for
Dynamic Adaptive Streaming over HTTP (DASH) streaming services and files for file delivery
services.
The middleware will fail its initialization if this amount of memory cannot be allocated. The
middleware may allocate additional memory for FLUTE object decoding at runtime, if necessary.
The value of this parameter is in bytes.
The settings for this parameter should consider the following:
 The number of concurrent streaming sessions
 The data rate of the streaming services
 The segment duration of the streaming services
 The number of concurrent file downloads for file delivery services
 The maximum file size per file delivery service
 FEC type and FEC settings in use
If any of the above factors changes, this parameter value may have to be modified to ensure that
enough memory will be available for FEC processing for all streaming and file download
services.
Table 2-1 lists the recommended parameters for a number of typical settings using either Raptor
or RaptorQ, and using the corresponding recommended FEC settings as captured in in [Q2] and
[Q3] respectively.
Table 2-1 Recommended memory settings for some typical scenarios

2 streams+600 MB 2 streams+1 GB 5 streams+1 GB
Streaming (Average
2 streams file file file
Rate, Segment
Duration) Memory (MB)
800 kbps, 1s 2.04 4.64 6.30 9.36
800 kbps, 2s 2.49 5.09 6.76 10.49
1.5 Mbps, 1s (1.8 Mbps
peak) 2.60 5.20 6.86 10.76
peak) 3.63 6.23 7.90 13.35
800 kbps, 5s 3.88 6.48 8.14 13.96
peak) 3.52 6.12 7.78 13.06

Figure 2-3 shows the FECProcessingMaxMemorySize element in detail.
Figure 2-3 FECProcessingMaxMemorySize
2.2.1.3 FileSystemWriteSpeed parameter (not supported)

This optional parameter denotes the rate, bytes/sec, that the UE is capable of writing received
FLUTE packets in its file system storage. This parameter limits the rate at which the network
operator can transmit data. If the rate of data transmission is more than the designated parameter
the UE may drop the FLUTE packets. Figure 2-4 shows the FileSystemWriteSpeed element in
detail.
NOTE: There is no support for the FileSystemWriteSpeed in the current middleware release.
Figure 2-4 FileSystemWriteSpeed
2.2.1.4 MSDCServiceClass parameter

This optional parameter defines a list of service classes associated with MSDC and the file names
carried in services associated with the service classes. Expand this element to the following
elements and attributes as shown in Figure 2-5. There must be one and only one service defined
for each MSDCServiceClass element definition. Each of the service classes defined in the
provisioning XML file should only refer to one service in the service announcement.
Figure 2-5 MSDCServiceClass
2.2.1.4.1 Name attribute

This attribute denotes the name of the service class defined by this element.

2.2.1.4.2 MSDCFileURIs attribute

This element provides a Uniform Resource Identifiers (URI), for example, a file name for a file to
broadcast on the service that belongs to the service class defined by this element. A wild card “”
(empty string) will be accepted as a file URI to indicate that any file name is acceptable.
2.2.1.4.3 Purpose attribute

This is an attribute of the element – MSDCFileURIs. The attribute denotes the purpose of the file
defined by MSDCFileURI. The defined list of purposes are as follows:
 Configuration
 Service Discovery – not supported
 Service Control – not supported
 Carrier-Specific-Configuration
The following XML snippet illustrates the configuration for the service classes of a configuration
and discovery service. Each file URI has a purpose associated to it. The following snippet also
shows the names of the files that will be broadcast OTA for the services associated with the
service class.
<MSDCServiceClass
Name=“urn:oma:bcast:ext_bsc_3gpp:middleware_configuration:1.0”>
<MSDCFileURIs Purpose=“Configuration”>
http://embmsconfig.qualcomm.com/configuration/msdcconfig.xml
</MSDCFileURIs>
<MSDCFileURIs Purpose=“Carrier-Specific-Configuration”>
https://www.carrier.com/provision/config.xml</MSDCFileURIs>
<MSDCFileURIs Purpose=“Service
Control”>file://servicecontrol.carrier.com/serviceControl.xml</MSDCFileURIs
>
NOTE: The configuration service associated with MSDC is supported when the provisioning file is
missing or the provisioning file does not include the optional parameter MSDCServiceClass. In
this case a specific MSDCFileURI is associated with purpose= “Configuration” with a specific
MSDCServiceClass name as illustrated in the following XML snippet below:
<MSDCServiceClass
Name=“urn:oma:bcast:ext_bsc_3gpp:middleware_configuration:1.0”>
<MSDCFileURIs Purpose=“Configuration”>
http://embmsconfig.qualcomm.com/configuration/msdcconfig.xml</MSDCFileURIs>
</MSDCServiceClass>
2.2.1.5 ServiceDiscoveryBootstrap element

The optional ServiceDiscoveryBootstrap element describes the parameters that need the service
discovery, bootstrap process. Figure 2-6 shows the ServiceDiscoveryBootstrap element in detail.

2.2.1.5.1 BootstrapURI parameter

This optional parameter denotes the Uniform Resource Identifier (URI) from where the
middleware fetches the service definition for the bootstrap service discovery channel. The
BootstrapURI is an important parameter, if it is configured incorrectly it will result in no service
discovery for eMBMS which indirectly results in no eMBMS service. Alternatively, if the
BootstrapURI is not included the MSDC gets the Public Land Mobile Network (PLMN) of the
cell the device is camped on and identifies the values for the Mobile Country Code (MCC) and
the Mobile Network Code (MNC). The Multicast Service Device Client (MSDC) formats the
bootstrap URI using MCC and MNC values (see subsection 5.2.3.1 in TS 26.346):
http://mbmsbs.mnc<MNC>.mcc<MCC>.pub.3gppnetwork.org/bootstrap.multipart
The MCC is always 3 digits long and the MNC may be 2 or 3 digits long .If there are only 2
significant digits in the MNC, one "0" digit shall be inserted at the left side to fill the 3 digits
coding of the MNC value.
2.2.1.5.2 BootstrapAccessPointName parameter

This optional parameter provides the Access Point Name (APN) used during the bootstrap of the
service discovery channel.
2.2.1.5.3 BootstrapRetriesRandomPeriod parameter (not supported)

This optional parameter denotes the time window length over which UE shall calculate a random
time for the bootstrap service discovery unicast fetch. This provides statistically uniform
distribution of any unicast request over a period and balances the network load caused by the
unicast requests from the UE.
NOTE: There is no support for the BootstrapRetriesRandomPeriod parameter in the current middleware
release.
Figure 2-6 ServiceDiscoveryBootstrap

2.2.1.6 ReceptionReportingTemplateURL parameter

The ReceptionReportingTemplateURL is an optional parameter. When included, this parameter
defines a template for the URLs described in the serviceURI in the postReceptionReport element
located in the Associated Delivery Procedure Description (ADPD) of a service. This parameter is
particularly useful to ensure the serviceURI indicates Hypertext Transfer Protocol Secure
(HTTPS) or HTTP URLs. For example, ReceptionReportingTemplateURL can be included as
https://rr*.carrier.com/, therefore MSDC can match https://rrNYC.carrier.com/svc1 but MSDC
cannot match https://rr.carrierXYZ.com/svc1. When ReceptionReportingTemplateURL is
present, MSDC ignores serviceURI in postReceptionReport that do not match
ReceptionReportingTemplateURL. If no serviceURIs match the
ReceptionReportingTemplateURL, then the MSDC disables the reception reporting collection
and upload until an updated ADPD is received with serviceURIs that match the templates. Figure
2-7shows the ReceptionReportingTemplateURL element.
Figure 2-7 ReceptionReportingTemplateURL
2.2.1.7 FileRepairTemplateURL parameter

The FileRepairTemplateURL is an optional parameter. When included, this parameter defines a
template for the URLs described in the serviceURI in the postFileRepair element in ADPD of a
file delivery service. The parameter is particularly useful to ensure that the serviceURI indicates
HTTPS or HTTP URLs. For example, the FileRepairTemplateURL can be included as
https://repair*.carrier.com/, therefore MSDC can match https://repairNYC.carrier.com/script.cgi
but cannot match https://repair.carrierXYZ.com/script.cgi. When FileRepairTemplateURL is
present, MSDC ignores serviceURI in postFileRepair that do not match FileRepairTemplateURL.
If no serviceURIs match the FileRepairTemplateURL, the MSDC disables the file repair until an
updated ADPD is received with serviceURIs that match these templates. Figure 2-8 shows the
FileRepairTemplateURL element.
Figure 2-8 FileRepairTemplateURL

2.2.1.8 ServiceDiscoveryNumberOfRetries parameter

This optional parameter denotes the number of consecutive service announcement receptions, to
perform with no files received on the service discovery FLUTE session before triggering a new
bootstrap procedure to rediscover the service discovery service. Figure 2-9 shows the
ServiceDiscoveryNumberOfRetries element in detail.
Figure 2-9 ServiceDiscoveryNumberOfRetries
2.2.1.9 AccessPointNameMapping parameter

This parameter uses the Android platform to map APN names to network access features.
Figure 2-10 shows the AccessPointNameMapping element in detail. Use the network access
features to cause certain traffic, e.g., file repair or reception reports, to use a specific APN.
2.2.1.9.1 AccessPointName element

This optional element denotes an access point name.
2.2.1.9.2 AccessPointFeature element

This element denotes the access point feature corresponding to the APN in the APName.
If the APN name is present in User Service Description (USD) for the reception reporting or file
repair, but the corresponding name to feature mapping is not present in the provisioning XML the
UE will route the APN traffic through the default APN setting in Android.
If the MSDC finds the appropriate mapping of the APN name and feature from the provisioning
XML, but enabling the APN feature corresponding to an APN name fails in Android, the UE will
block the traffic and abort reception reports or file repair. Therefore, the network operator should
make sure that the same APN name and feature mappings are implemented at the Android
operating system level. If no mappings are established in Android the UE will not be able to route
the data through APN.
Figure 2-10 AccessPointNameMapping

2.2.1.10 NetworkConstraintForADP parameter

This optional parameter denotes the network subtype to use for ADP procedures. The parameter
currently supports the following accepted values: Long Term Evolution (LTE only) and any
Wi-Fi, 3G, or LTE. Figure 2-11 shows the NetworkConstraintForADP element in detail.
Reception reporting and file repair use this parameter value to select the network subtype during
APN-related processing.
Figure 2-11 NetworkConstraintForADP
2.2.1.11 RSSIPollingInterval parameter

This optional parameter determines the time intervals, in seconds, that the MSDC polls the
modem for Received Signal Strength Indication (RSSI)-level strength measurements. The
operator should not set the parameter if there is no need for the RSSI feature. Figure 2-12 shows
the RSSIPollingInterval element in detail.
Figure 2-12 RSSIPollingInterval
2.2.1.12 MaxNumberOfFileDeliveryTables parameter (not supported)

This optional parameter denotes the maximum number of File Delivery Tables (FDTs) MSDC
stores per FLUTE session. The operator should set the value for this parameter equal to the
maximum number of FDTs they want to send when taking into account any FLUTE session.
Figure 2-13 shows the MaxNumberOfFileDeliveryTables element.
NOTE: There is no support for the MaxNumberOfFileDeliveryTables in the current middleware release.
Figure 2-13 MaxNumberOfFileDeliveryTables

2.2.1.13 MaxReceptionReportingStorageSize parameter (not supported)

This optional parameter denotes the maximum amount of storage, in bytes, reserved for the
collection of reception reports by MSDC. The UE stops collecting more reports if the amount is
reached. Figure 2-14 shows the MaxReceptionReportingStorageSize element in detail.
NOTE: There is no support for the MaxReceptionReportingStorageSize parameter in the current

middleware release.
Figure 2-14 MaxReceptionReportingStorageSize
2.2.1.14 MaxUnnotifiedFileDownloadQuota parameter

This optional parameter defines the amount of storage quota, in bytes, for downloaded files of file
delivery services awaiting delivery to applications. Xs:unsignedInt is the type of parameter which
means the maximum amount for storage quota is (2^32)-1= 4 Gbyte. When the size of a received
file is larger than the available space defined by this parameter the middleware discards the
received file. Otherwise, a received file is stored and made available to applications.
Figure 2-15 shows the MaxUnnotifiedFileDownloadQuota element in detail.
If the file system access, for example, file URIs is used to notify applications of downloaded files,
this parameter defines the amount of storage quota for storing downloaded files that were not
accompanied with a notification. If HTTP access is used to notify the application of downloaded
files this parameter defines the amount of storage quota for storing HTTP notified files and
downloaded files without notifications.
NOTE: In the current middleware release, MaxUnnotifiedFileDownloadQuotaExtension overwrites the

value of MaxUnnotifiedFileDownloadQuota.
Figure 2-15 MaxUnnotifiedFileDownloadQuota

2.2.1.15 NumberOfRegistrationWithSameServiceClass parameter (not

supported)
This optional parameter defines a part of extension schema to the initial provisioning parameters.
The parameter denotes the number of applications that allow registration for a particular service
class with the middleware. If an application requests registration with a service class and the
threshold determined by this parameter is reached, the middleware will send a service
registration, error message to the registering application with the appropriate error message.
Figure 2-16 shows the NumberOfRegistrationWithSameServiceClass element in detail.
NOTE: There is no support for the NumberOfRegistrationWithSameServiceClass in the current

middleware release.
Figure 2-16 NumberOfRegistrationWithSameServiceClass
2.2.1.16 NumberOfConcurrentFileDownload parameter (not supported)

This optional parameter defines a part of the extension schema to the initial provisioning
parameters for backward compatibility. The parameter denotes the number of concurrent file
downloads that can be supported by the middleware. When this threshold is reached, the
middleware stops activating file downloads at the FLUTE layer. Figure 2-17 shows the
NumberOfConcurrentFileDownload element in detail.
NOTE: There is no support for the NumberOfConcurrentFileDownload parameter in the current

middleware release.
Figure 2-17 NumberOfConcurrentFileDownload

2.2.1.17 NumberOfConcurrentStreaming parameter

parameters for backward compatibility. This parameter determines the number of streaming
services supported concurrently by the middleware. When it reaches this threshold and an
application activates a streaming service, the middleware sends a service start, error message to
the application. Figure 2-18 shows the NumberOfConcurrentStreaming element in detail.
NOTE: A large NumberOfConcurrentStreaming requires large FECProcessingMaxMemorySize

availability to the middleware.
Figure 2-18 NumberOfConcurrentStreaming
2.2.1.18 UnicastFetchForDASH parameter

parameters for backward compatibility. This parameter indicates the level of support of unicast
fetch of segments for a streaming service. When the value is set to zero the unicast fetch of
segments is disabled. When the value for this parameter is set to one the unicast fetch of segments
enables only for a period of two segment durations after the start of a service. When the
parameter is set to two, the unicast fetch enables for the period of two segments at the beginning
and subsequently for segments that are partially downloaded (incomplete) via broadcasts. Figure
2-19 shows the UnicastFetchForDASH element in detail.
Figure 2-19 UnicastFetchForDASH
2.2.1.19 PLMN parameter

This optional parameter indicates all PLMNs associated with the carrier network where the
middleware operates. A pair of MCC and MNC elements define each PLMN. Figure 2-20 shows
the carrier PLMN list element in detail. MSDC does not accept any parameter under
CarrierNetworkParams if device SIM PLMN is not included in the PLMN list.
Figure 2-20 Carrier PLMN list

2.2.1.20 CarrierNetworkParamsExtension
2.2.1.20.1 StorageFileDelivery parameter

The optional StorageFileDelivery element describes the parameters needed to control the storage
of downloaded files for file delivery services. This parameter defines a part of
CarrierNetworkParamsExtension. Figure 2-21 shows the StorageFileDelivery element in detail.
2.2.1.20.1.1 ExternalPath parameter

This parameter is used to identify a path in an external location to store downloaded files by the
middleware. If the ExternalPath is not included the middleware stores downloaded files in any
internal location.
2.2.1.20.1.2 MaxFileDeliveryTTL parameter (not supported)

This optional parameter is used to identify the maximum time duration to store a downloaded file
in the storage (applies also to file accessible via HTTP) after sending a notification of the file
availability to applications.
NOTE: A small MaxUnnotifiedFileDownloadQuota might require small MaxFileDelivertTTL to remove

notified files as soon as possible by the middleware.
NOTE: There is no support for the MaxFileDeliveryTTL in the current middleware release.
Figure 2-21 StorageFileDelivery
2.2.1.20.2 CarrierNetworkParamsExtension1 parameter

The CarrierNetworkParamsExtension1 element describes an additional parameter needed to
extend the range of the quota for file download storage.
2.2.1.20.2.1 MaxUnnotifiedFileDownloadQuotaExtension parameter

This optional parameter defines the amount of storage quota, in bytes, for downloaded files of file
delivery services awaiting delivery to applications. The behavior of the middleware for this
parameter is identical to MaxUnnotifiedFileDownloadQuota. Xs:unsignedLong is the type of
parameter which means the maximum amount for storage quota is much larger than the 4 Gbyte
limits of the MaxUnnotifiedFileDownloadQuota. Figure 2-22 shows the
MaxUnnotifiedFileDownloadQuotaExtension element.
Figure 2-22 MaxUnnotifiedFileDownloadQuotaExtension

2.2.2 OEMParams
2.2.2.1 ScratchSpacePath parameter

This optional parameter denotes the relative path in the UE file system where received symbols
for downloaded files are stored. Forward Error Correction (FEC) decoding of these received files
is performed on symbols stored in this location. Figure 2-23 shows the ScratchSpacePath element
and its default value.
Figure 2-23 ScratchSpacePath
2.2.2.2 SuppressReceptionTime parameter

The middleware deactivates the Temporary Mobile Group Identity (TMGI) and the FLUTE
session for a service when a file is fully received during the scheduled transmission and when the
start time for the transmission of the next file is in the future by more than the time duration
defined by this element. Figure 2-24 shows the SuppressReceptionTime element in detail.
NOTE: Scheduled transmission is described in fileSchedule of the schedule fragment.
Figure 2-24 SuppressReceptionTime
2.2.2.3 TMGIActivationTimeout parameters

This optional parameter denotes the timeout period, in seconds, at MSDC for receiving a TMGI
activation response from the modem after a TMGI activation request. When a timeout is reached
and MSDC does not get a response from the modem it requests activation again. Figure 2-25
shows the TMGIActivationTimeout element in detail.
Figure 2-25 TMGIActivationTimeout

2.2.2.4 StreamingTMGIActivationRetryTimeOut parameter

This optional parameter denotes the periodic interval (in seconds) at which MSDC reattempts the
TMGI activation for streaming services on activation failures. Figure 2-26 shows the
StreamingTMGIActivationRetryTimeOut element in detail.
Figure 2-26 StreamingTMGIActivationRetryTimeOut
2.2.2.5 MSDCSocketInterfacePort parameter

Use this TCP port to establish a connection between the MSDC java layer and the native layer.
This optional parameter defines two attributes. The starting port number denotes the first port
number the MSDC native layer binds to. In case of conflict (generally due to the fact that the port
is already in use), the MSDC native layer continues to search to bind to a port that is within the
range specified by the portRange attribute. Figure 2-27 shows the MSDCSocketInterfacePort
element in detail.
Figure 2-27 MSDCSocketInterfacePort

2.2.2.6 DASHStreamingPort parameter

This optional parameter denotes the Transmission Control Protocol (TCP) port number for the
local DASH gateway server. Assign this parameter so the TCP port number does not conflict with
other applications running on the UE. This parameter defines two attributes. The starting port
number denotes the first port number DASH gateway binds to. In case of conflict (generally due
to the fact that the port is already in use), the DASH gateway continues to search to connect to a
port that is within the range specified by the portRange attribute. Figure 2-28 shows the
DASHStreamingPort element in detail.
Figure 2-28 DASHStreamingPort
2.2.2.7 TimeShiftBuffer parameter

This parameter contains time-shifted buffer related parameters. Figure 2-29 shows the
TimeShiftBuffer element and its children in detail.
Figure 2-29 TimeShiftBuffer
2.2.2.7.1 MaxTimeShiftBufferDepth parameter

This parameter is the maximum time-shifted buffer depth (TSB) supported for a device type. If
the time shift buffer depth specified in the MPD is greater than this value, then the time shift
buffer depth attribute in the MPD is adjusted to this value.

2.2.2.7.2 TimeShiftBufferMarginSecond parameter

This optional parameter is added to the time shift buffer depth parameter when calculating the
memory required for accommodating the time shift buffer. The additional time covers segment
size overrun beyond the average segment size since the average streaming rate is used for
calculating memory requirements for the time shift buffer. See Section 2.2.2.7.3 for the formula
used by the middleware.
2.2.2.7.3 TimeShiftBufferMarginPercentage parameter

This optional parameter ensures that additional memory is available beyond the memory
calculated for accommodating the time shift buffer for a service.
When a DASH streaming service is started by an application, the middleware compares the
currently available memory in bytes to the value of the following formula:
TSB_Margin_Percentage
AverageRate * (1 + )
100 ∗ (TSB _ Buffer _ Depth + TSB_Margin_Seconds )
8
Where:
 TSB_Margin_Percentage is the parameter described in this section.
 TSB_Margin_Seconds is the provisioning parameter TimeShiftBufferMarginSecond.
 The average rate is the average rate in bits per second of the service as specified in the MPD.
 The TSB_Buffer_Depth is the TSB buffer depth specified in the MPD and capped by both the
MaxTimeShiftBufferDepth provisioning parameter that applies to this device and the
MaxTimeShiftBufferDepth configuration parameter that applies to all the devices in the
network.
If the available memory is less than the above formula the time shift buffer feature is disabled for
the service by setting the time shift buffer attribute in the MPD to zero. The time shift buffer
feature remains disabled for the service until the service is stopped by the application; this
ensures enough memory resources and additional margin is available for the TSB feature.

2.2.2.8 DeviceType parameter

This optional parameter adds a part of extension schema to the initial provisioning parameters for
backward compatibility. When present in the provisioning XML document, this parameter
denotes the device class ID of the device. Later on, this class ID is used by the middleware to
determine the appropriate service discovery-monitoring period in the UE for that class of device.
Figure 2-30 shows the DeviceType element in detail.
Figure 2-30 DeviceType
2.2.2.9 MSDCUpgradeCheckURI parameter(not supported)

This parameter, when present in the provisioning XML document, provides a URI from which the
middleware determines whether an upgrade version of the middleware is available. Figure 2-31
shows the MSDCUpgradeCheckURI element in detail.
NOTE: There is no support for the MSDCUpgradeCheckURI in the current middleware release.
Figure 2-31 MSDCUpgradeCheckURI
2.2.2.10 DeviceCapabilities parameter (not supported)

This parameter, when present in the provisioning XML document, provides a list of features that
the device or middleware supports. The value space for the features defines the 3GPP standard TS
26.346. Figure 2-32 shows the DeviceCapabilities element in detail.
NOTE: The value for the feature element needs to be integer numbers.
NOTE: There is no support for the DeviceCapabilities in the current middleware release.
Figure 2-32 DeviceCapabilities

2.2.2.11 OEMParamsExtension
2.2.2.11.1 HTTPFileDelivery parameter (not supported)

The optional HTTPFileDelivery element describes parameters that control the HTTP server used
for accessing downloaded files of file delivery services. This parameter defines a part of the
OEMParamsExtension. Figure 2-33 shows the HTTPFileDelivery element in detail. The
startingPortNumber and portRange attributes should be used to assign the TCP port number for
the HTTP server. Assign these attributes so the TCP port number does not conflict with other
applications running on the UE. The startingPortNumber denotes the first port number the HTTP
server binds to. In case of a conflict (generally due to the port already being in use), the
middleware continues to search for an available port that is within the range specified by the
portRange attribute.
2.2.2.11.1.1 MaxNumberHTTPConnections parameter (not supported)

This optional parameter defines the maximum number of simultaneous HTTP connections
allowed to the server.
2.2.2.11.1.2 RateHTTPConnection parameter (not supported)

This optional parameter defines the maximum rate of sending data by the HTTP server per
connection.
NOTE: There is no support for the RateHTTPConnection in the current middleware release.
Figure 2-33 HTTPFileDelivery

A Provisioning XML Schema
A.1 Provisioning XML schema

<?xml version="1.0" encoding="UTF-8"?>
<xs:schema xmlns="urn:3gpp:qualcomm:MSDC:ProvisioningFile-1"
xmlns:xs="http://www.w3.org/2001/XMLSchema"
targetNamespace="urn:3gpp:qualcomm:MSDC:ProvisioningFile-1"
elementFormDefault="qualified" attributeFormDefault="unqualified">
<xs:element name="MSDCProvisioningParams">
<xs:annotation>
<xs:documentation>Provisioning schema for MSDC
</xs:documentation>
</xs:annotation>
<xs:complexType>
<xs:sequence>
<xs:element name="CarrierNetworkParams"
minOccurs="0">
<xs:complexType>
<xs:sequence>
<xs:element
name="CycleTimes" type="xs:string" default="980:10" minOccurs="0"/>
<xs:element
name="FECProcessingMaxMemorySize" default="6815744" minOccurs="0">
<xs:simpleType>
<xs:restriction
base="xs:unsignedInt"/>
</xs:simpleType>
</xs:element>
<xs:element
name="FileSystemWriteSpeed" minOccurs="0">
<xs:simpleType>
<xs:restriction

eMBMS Middleware Provisioning Parameters Profile Specification Release 3.2 Provisioning XML Schema
</xs:simpleType>
</xs:element>
<xs:element
name="MSDCServiceClass" minOccurs="0" maxOccurs="unbounded">
<xs:complexType>
<xs:sequence>
<xs:element name="MSDCFileURIs" maxOccurs="unbounded">
<xs:complexType>
<xs:simpleContent>
<xs:extension base="xs:anyURI">
<xs:attribute name="Purpose" type="xs:string" use="required"/>
<xs:anyAttribute processContents="skip"/>
</xs:extension>
</xs:simpleContent>
</xs:complexType>
</xs:element>
<xs:element name="MSDCServiceClassExtension" minOccurs="0">
<xs:complexType>
<xs:sequence>
<xs:any processContents="lax" minOccurs="0"

maxOccurs="unbounded"/>
</xs:sequence>
</xs:complexType>
</xs:element>

</xs:sequence>
<xs:attribute
name="Name" type="xs:string" use="required"/>
</xs:complexType>
</xs:element>
<xs:element
name="ServiceDiscoveryBootstrap" minOccurs="0">
<xs:complexType>
<xs:sequence>
<xs:element name="BootstrapURI" type="xs:anyURI" minOccurs="0"/>
<xs:element name="BootstrapAccessPointName" type="xs:anyURI"

minOccurs="0"/>
<xs:element name="BootstrapRetriesRandomPeriod" default="PT0H"

minOccurs="0">
<xs:simpleType>
<xs:restriction base="xs:duration"/>
</xs:simpleType>
</xs:element>
<xs:element name="ServiceDiscoveryBootstrapExtension" minOccurs="0">
<xs:complexType>
<xs:sequence>

</xs:sequence>
</xs:complexType>

</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element
name="ReceptionReportingTemplateURL" type="xs:string" minOccurs="0"/>
<xs:element
name="FileRepairTemplateURL" type="xs:string" minOccurs="0"/>
<xs:element
name="ServiceDiscoveryNumberOfRetries" default="16" minOccurs="0">
<xs:simpleType>
<xs:restriction
</xs:simpleType>
</xs:element>
<xs:element
name="AccessPointNameMapping" minOccurs="0" maxOccurs="unbounded">
<xs:complexType>
<xs:sequence>
<xs:element name="AccessPointName" type="xs:anyURI" default="default"/>
<xs:element name="AccessPointFeature" type="xs:string"

default="enableHIPRI"/>
<xs:element name="AccessPointNameMappingExtension" minOccurs="0">
<xs:complexType>
<xs:sequence>

</xs:sequence>
</xs:complexType>
</xs:element>

</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element
name="NetworkConstraintForADP" type="xs:string" default="LTE" minOccurs="0"/>
<xs:element
name="RSSIPollingInterval" default="PT2.56S" minOccurs="0">
<xs:simpleType>
<xs:restriction
base="xs:duration"/>
</xs:simpleType>
</xs:element>
<xs:element
name="MaxNumberOfFileDeliveryTables" minOccurs="0">
<xs:simpleType>
<xs:restriction
</xs:simpleType>
</xs:element>
<xs:element
name="MaxReceptionReportingStorageSize" minOccurs="0">
<xs:simpleType>
<xs:restriction
</xs:simpleType>
</xs:element>
<xs:element
name="MaxUnnotifiedFileDownloadQuota" minOccurs="0">
<xs:simpleType>
<xs:restriction
</xs:simpleType>
</xs:element>
<xs:element
name="NumberOfRegistrationWithSameServiceClass" type="xs:unsignedInt" minOccurs="0"/>
<xs:element
name="NumberOfConcurrentFileDownload" type="xs:unsignedInt" minOccurs="0"/>

<xs:element
name="NumberOfConcurrentStreaming" type="xs:unsignedInt" default="20" minOccurs="0"/>
<xs:element
name="UnicastFetchForDASH" type="xs:unsignedInt" minOccurs="0"/>
<xs:element name="PLMN"
minOccurs="0" maxOccurs="unbounded">
<xs:complexType>
<xs:sequence>
<xs:element name="MCC" type="xs:unsignedLong"/>
<xs:element name="MNC" type="xs:unsignedLong"/>

</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element
name="CarrierNetworkParamsExtension" minOccurs="0">
<xs:complexType>
<xs:sequence>
<xs:element name="StorageFileDelivery" minOccurs="0">
<xs:complexType>
<xs:sequence>
<xs:element name="ExternalPath" type="xs:string" minOccurs="0"/>
<xs:element name="MaxFileDeliveryTTL" type="xs:duration"

default="PT2H" minOccurs="0"/>
<xs:element name="StorageFileDeliveryExtension" minOccurs="0">
<xs:complexType>
<xs:sequence>


</xs:sequence>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="CarrierNetworkParamsExtension1" minOccurs="0">
<xs:complexType>
<xs:sequence>
<xs:element name="MaxUnnotifiedFileDownloadQuotaExtension"
type="xs:unsignedLong" default="10737418240" minOccurs="0"/>
<xs:element name="CarrierNetworkParamsExtension2"
minOccurs="0">
<xs:complexType>
<xs:sequence>

</xs:sequence>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:complexType>

</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="OEMParams" minOccurs="0">
<xs:complexType>
<xs:sequence>
<xs:element
name="ScratchSpacePath" type="xs:string" default="sd/scratch1" minOccurs="0"/>
<xs:element
name="SuppressReceptionTime" default="PT5S" minOccurs="0">
<xs:simpleType>
<xs:restriction
</xs:simpleType>
</xs:element>
<xs:element
name="TMGIActivationTimeout" default="PT11S" minOccurs="0">
<xs:simpleType>
<xs:restriction
</xs:simpleType>
</xs:element>
<xs:element
name="StreamingTMGIActivationRetryTimeOut" default="PT1S" minOccurs="0">
<xs:simpleType>
<xs:restriction
</xs:simpleType>
</xs:element>
<xs:element
name="MSDCSocketInterfacePort" minOccurs="0">
<xs:complexType>

<xs:attribute
name="startingPortNumber" type="xs:unsignedInt" default="5008"/>
<xs:attribute
name="PortRange" type="xs:unsignedInt" default="10"/>
</xs:complexType>
</xs:element>
<xs:element
name="DASHStreamingPort" minOccurs="0">
<xs:complexType>
<xs:attribute
name="startingPortNumber" type="xs:unsignedInt" default="4009"/>
<xs:attribute
name="PortRange" type="xs:unsignedInt" default="10"/>
</xs:complexType>
</xs:element>
<xs:element
name="TimeShiftBuffer" minOccurs="0">
<xs:complexType>
<xs:sequence>
<xs:element name="MaxTimeShiftBufferDepth" default="PT4H">
<xs:simpleType>
</xs:simpleType>
</xs:element>
<xs:element name="TimeShiftBufferMarginSecond" default="PT4S"

minOccurs="0">
<xs:simpleType>

</xs:simpleType>
</xs:element>
<xs:element name="TimeShiftBufferMarginPercentage" default="0.2"

minOccurs="0">
<xs:simpleType>
<xs:restriction base="xs:double"/>
</xs:simpleType>
</xs:element>
<xs:element name="TimeShiftBufferExtension" minOccurs="0">
<xs:complexType>
<xs:sequence>

</xs:sequence>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element
name="DeviceType" minOccurs="0">
<xs:complexType>
<xs:sequence>
<xs:element name="DeviceTypeExtension" minOccurs="0">
<xs:complexType>

<xs:sequence>

</xs:sequence>
</xs:complexType>
</xs:element>
</xs:sequence>
<xs:attribute
name="ClassID" type="xs:string" use="required"/>
</xs:complexType>
</xs:element>
<xs:element
name="MSDCUpgradeCheckURI" type="xs:anyURI" minOccurs="0"/>
<xs:element
name="DeviceCapabilities" minOccurs="0">
<xs:complexType>
<xs:sequence>
<xs:element name="Features" maxOccurs="unbounded"/>

</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element
name="OEMParamsExtension" minOccurs="0">
<xs:complexType>
<xs:sequence>
<xs:element name="HTTPFileDelivery" minOccurs="0">
<xs:complexType>
<xs:sequence>

<xs:element name="MaxNumberHTTPConnections"
type="xs:unsignedInt" default="10" minOccurs="0"/>
<xs:element name="RateHTTPConnection" type="xs:unsignedInt"

minOccurs="0"/>
<xs:element name="HTTPFileDeliveryExtension" minOccurs="0">
<xs:complexType>
<xs:sequence>

</xs:sequence>
</xs:complexType>
</xs:element>
</xs:sequence>
<xs:attribute name="startingPortNumber" type="xs:unsignedInt"

default="4600"/>
<xs:attribute name="portRange" type="xs:unsignedInt" default="10"/>
</xs:complexType>
</xs:element>
<xs:element name="OEMParamsExtension1" minOccurs="0">
<xs:complexType>
<xs:sequence>


</xs:sequence>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element
name="MSDCProvisioningParamsExtension" minOccurs="0">
<xs:complexType>
<xs:sequence>
<xs:any processContents="lax"
minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:sequence>
<xs:attribute name="Version" type="xs:string"/>
</xs:complexType>
</xs:element>
</xs:schema>


eMBMS Middleware Provisioning Parameters: Profile Specification Release 3.2

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

eMBMS Middleware Provisioning Parameters: Profile Specification Release 3.2

Uploaded by

Copyright:

Available Formats

Qualcomm Technologies, Inc.

eMBMS Middleware Provisioning Parameters

Confidential and Proprietary – Qualcomm Technologies, Inc.

© 2015 Qualcomm Technologies, Inc. All rights reserved.

Qualcomm Technologies, Inc.

80-B7411-6 Rev. A Confidential and Proprietary – Qualcomm Technologies, Inc. 3

2 Middleware Provisioning Parameters .................................................................................. 8

A Provisioning XML Schema..................................................................................................28

80-B7411-6 Rev. A Confidential and Proprietary – Qualcomm Technologies, Inc. 4

Figure 2-27 MSDCSocketInterfacePort ........................................................................................................................ 23

80-B7411-6 Rev. A Confidential and Proprietary – Qualcomm Technologies, Inc. 5

1.2 Document organization

Table 1-1 Acronyms and abbreviations

80-B7411-6 Rev. A Confidential and Proprietary – Qualcomm Technologies, Inc. 6

80-B7411-6 Rev. A Confidential and Proprietary – Qualcomm Technologies, Inc. 7

Figure 2-1 MSDC device parameters

80-B7411-6 Rev. A Confidential and Proprietary – Qualcomm Technologies, Inc. 8

2.2 Provisioning parameters

80-B7411-6 Rev. A Confidential and Proprietary – Qualcomm Technologies, Inc. 9

2.2.1.1 CycleTimes parameter

Figure 2-2 CycleTimes

80-B7411-6 Rev. A Confidential and Proprietary – Qualcomm Technologies, Inc. 10

2.2.1.2 FECProcessingMaxMemorySize parameter

Table 2-1 Recommended memory settings for some typical scenarios

80-B7411-6 Rev. A Confidential and Proprietary – Qualcomm Technologies, Inc. 11

Figure 2-3 shows the FECProcessingMaxMemorySize element in detail.

Figure 2-3 FECProcessingMaxMemorySize

2.2.1.3 FileSystemWriteSpeed parameter (not supported)

Figure 2-4 FileSystemWriteSpeed

2.2.1.4 MSDCServiceClass parameter

Figure 2-5 MSDCServiceClass

2.2.1.4.1 Name attribute

80-B7411-6 Rev. A Confidential and Proprietary – Qualcomm Technologies, Inc. 12

2.2.1.4.2 MSDCFileURIs attribute

2.2.1.4.3 Purpose attribute

2.2.1.5 ServiceDiscoveryBootstrap element

80-B7411-6 Rev. A Confidential and Proprietary – Qualcomm Technologies, Inc. 13

2.2.1.5.1 BootstrapURI parameter

2.2.1.5.2 BootstrapAccessPointName parameter

2.2.1.5.3 BootstrapRetriesRandomPeriod parameter (not supported)

Figure 2-6 ServiceDiscoveryBootstrap

80-B7411-6 Rev. A Confidential and Proprietary – Qualcomm Technologies, Inc. 14

2.2.1.6 ReceptionReportingTemplateURL parameter

Figure 2-7 ReceptionReportingTemplateURL

2.2.1.7 FileRepairTemplateURL parameter

Figure 2-8 FileRepairTemplateURL

80-B7411-6 Rev. A Confidential and Proprietary – Qualcomm Technologies, Inc. 15

2.2.1.8 ServiceDiscoveryNumberOfRetries parameter

Figure 2-9 ServiceDiscoveryNumberOfRetries

2.2.1.9 AccessPointNameMapping parameter

2.2.1.9.1 AccessPointName element

2.2.1.9.2 AccessPointFeature element

Figure 2-10 AccessPointNameMapping

80-B7411-6 Rev. A Confidential and Proprietary – Qualcomm Technologies, Inc. 16

2.2.1.10 NetworkConstraintForADP parameter

Figure 2-11 NetworkConstraintForADP

2.2.1.11 RSSIPollingInterval parameter

Figure 2-12 RSSIPollingInterval

2.2.1.12 MaxNumberOfFileDeliveryTables parameter (not supported)

Figure 2-13 MaxNumberOfFileDeliveryTables

80-B7411-6 Rev. A Confidential and Proprietary – Qualcomm Technologies, Inc. 17

2.2.1.13 MaxReceptionReportingStorageSize parameter (not supported)

NOTE: There is no support for the MaxReceptionReportingStorageSize parameter in the current