Home · All Classes · Grouped Classes · Annotated · Functions

OTA (Network)
Functional Description

OTA Network allows the network provider to send a set of network configuration to a mobile device with no user interaction required to create a working Internet connection. Qtopia processes the network configuration messages and writes the received settings to a file. Two distinct formats of OTA network configuration messages are supported:

1. Nokia's Over the Air Settings Specification 7.0
2. WAP/OMA standards (wap-183-provcont-20010724-a.pdf and OMA-WAP-ProvCont-v1_1-20050428-C.pdf).

New Configuration options are automatically matched against existing configurations and if no existing configuration is available, new Internet/WAP accounts are created. The entire process does not require any interaction with the user, however for security reasons the user can refuse to accept configuration changes. Once the changes are applied, new options are integrated into the Qtopia network configuration and can be used by starting the appropriate accounts.

Features

Network configuration

Qtopia can process OTA network configuration messages and writes the received settings to a file.

The Internet application is responsible the processing of received OTA messages. Depending on the message content it may change Internet, WAP and MMS accounts.

Qtopia supports two distinct formats of OTA network configuration messages:

• Nokia's Over the Air Settings Specification 7.0
• WAP/OMA standards (wap-183-provcont-20010724-a.pdf and OMA-WAP-ProvCont-v1_1-20050428-C.pdf)

The following configuration options are used by Qtopia and its applications:

• ISP name ( the name of the Internet service provider )
• Bearer ( the supported bearer are GSM and GPRS dial-up )
• APN ( access point information - GPRS only )
• GSM dial-up number ( for GSM Dial-up only )
• Authentication name ( the dial-up login name )
• Authentication secret ( the dial-up password )
• Authentication type ( PAP/CHAP authentication )
• WAP gateway address
• WAP gateway port
• WAP username
• WAP password
• WAP service type (e.g. CL-WSP)
• WAP home page
• MMS server address

New options are automatically matched against existing configurations. If there is no existing configuration available, new Internet/!WAP accounts are created. The entire process does not require any interaction with the user. However for security reasons the user can refuse to accept configuration changes. Once the changes are applied new options are integrated into Qtopia's network configuration and can be used by starting the appropriate accounts.

SIM Download

GSM 11.14 specifies a method to download data directly to the SIM, used by operators to modify the user's settings. From section 7.1.1 of GSM 11.14:

If the service "data download via SMS Point-to-point" is allocated and activated in the SIM Service Table (see TS 11.11 [20]), then the ME shall follow the procedure below:

• When the ME receives a Short Message with:
  • protocol identifier = SIM data download, and
  • data coding scheme = class 2 message,
• or when the ME receives a Short Message with:
  • protocol identifier=ANSI-136 R-DATA (see 3G TS 23.040 [30]) and
  • data coding scheme = class 2 message, and the ME chooses not to handle the message ( e.g. MEs not supporting EGPRS over TIA/EIA-136 do not need to handle the message),
• then the ME shall pass the message transparently to the SIM using the ENVELOPE (SMS-PP DOWNLOAD) command as defined below.
• The ME shall not display the message, or alert the user of a short message waiting.

Many modems already do this internally, without notifying Qtopia, so there is nothing to be done to support this on those modems. For modems that don't support SIM download internally, Qtopia passes the download message to the vendor-specific plugin to be handled according to the modem's specific requirements.

OTA Update

Other forms of OTA Update are typically be handled by SMS push services, dispatching on either MIME type or port number. The infrastructure for this is present in the telephony library. Applications in specific functional areas handle the messages in question, dispatched via QDS service messages.