What -is the Packet Context ?

diff -r 48780e181b38 -r 578be2adaf3e Symbian3/PDK/Source/GUID-C2CF49A8-E1AC-565B-8C7F-28C89D59600F.dita --- a/Symbian3/PDK/Source/GUID-C2CF49A8-E1AC-565B-8C7F-28C89D59600F.dita Tue Jul 20 12:00:49 2010 +0100 +++ b/Symbian3/PDK/Source/GUID-C2CF49A8-E1AC-565B-8C7F-28C89D59600F.dita Fri Aug 13 16:47:46 2010 +0100 @@ -1,68 +1,68 @@ - - - - - -What -is the Packet Context ?The packet context encapsulate the functions related to the context -of a packet switched network connection. The context of a connection relates -to factors such as the protocol type, the access point to the network and -the DNS and authentication parameters. -

The context is associated with a particular packet -service.

Contexts for each network type are supported by different member classes -in the RPacketContext:

RPacketContext::TContextConfigGPRS,
RPacketContext::TContextConfigR99_R4 (from -v7.0s onwards)
RPacketContext::TContextConfigCDMA.

Symbian platform provides the authentication parameters to -support CHAP and PAP authentication methods. Previously only PAP authentication -was supported. The CHAP authentication is more secure than the PAP authentication. -The additional functions are:

Point to Point Protocol -(PPP) authentication parameters, that is the CHAP and PAP parameters to support -authentication access with the Gateway GPRS Support Node (GGSN) and Authentication -Authorization and Accounting (AAA) systems. It is up to the client to decide -which mode of authentication to use.
CHAP authentication -can get the Domain Name System (DNS) server name parameters like primary DNS -and secondary DNS. The DNS server name is required in the authentication process. -AAA may deliver DNS IP addresses to the network, so the Packet Data API supports -delivering these addresses to the client. For more information see GSM Standards 09.61 and 24.008.
The authentication can -be used for both the primary and secondary contexts. A primary context configuration -is set without reference to another context. Secondary contexts are created -from an existing context that can be a primary or secondary context.

This API is implemented by RPacketContext.

Packet context -functions

The RPacketContext API -functions enable the clients to do the following:

Obtain a secondary packet -context from an existing packet. The second packet uses the same context information. -The Quality of Service information is not used.
Configure the Quality -of Service specifications of Release99 and Release4 in the packet context.
Modify the negotiated -QoS of an active context.
Add, remove and change -the packet filters in the Traffic Flow template of a context. The clients -can also create and delete the Traffic Flow templates.
Discover context information -for a network interface (NIF) level.
Retrieve the current -packet network release mode to receive roaming notification between the release -modes.