Standard constructor.

Activates a context that has been previously configured using SetConfig(). Once this function completes, the context will remain in an 'Activating' state until a layer 2 connection (e.g.: PPP or SLIP) has been successfully negotiated between the phone and the packet network gateway. Once the link layer has been negotiated, the context can be considered to be 'Activated'.

This is an asynchronous function.

Use RTelSubSessionBase::CancelAsyncRequest(EPacketContextActivate) to cancel a previously placed asynchronous Activate() request.

Adds a new set of Authorization Token and Flow Identifiers to the packet context object. This asynchronous method may be called by the client application.

This asychronous method may be called by the client application. It sets up a packet filter in the TFT belonging to this context with the ID specified in the packet filter information since version 2 of this API. Supported from v7.0S .

Closes the client's current sub-session with ETel. Any outstanding requests the client may have with ETel (notifications, for example) will be automatically destroyed by ETel.

This function creates an instance of CPacketContextPtrHolder and assigns it to the iEtelPacketContextPtrHolder pointer.

This asynchronous method may be called by the client application. Creates a new Traffic Flow Template.

Deactivates a context previously configured on the phone.

This is an asynchronous function.

Use RTelSubSessionBase::CancelAsyncRequest(EPacketContextDeactivate) to cancel a previously placed asynchronous Deactivate() request.

Deletes a context previously configured on the phone.

This asynchronous function may be called by the client application.

Although the context is deleted from the TSY (and/or ME), the client's RPacketContext/RPacketMbmsContext subsession remains. To remove this, a client must call Close().

This is an asynchronous function.

Use RTelSubSessionBase::CancelAsyncRequest(EPacketContextDelete) to cancel a previously placed asynchronous Delete() request.

This asynchronous method may be called by the client application. Deletes the existing traffic flow template (including all filters) for this context object.

This function deletes and NULLs the iEtelPacketContextPtrHolder pointer.

This asynchronous method may be called by the client application. It returns the number of defined packet filters in the Traffic Flow Template (TFT) associated with this context since version 2 of the API. Supported from v7.0S.

Gets the configuration of the current context.

This is an asynchronous function.

In the case of this function call, the value for each TContextConfigXXX parameter will be input by the TSY.

Use RTelSubSessionBase::CancelAsyncRequest(EPacketContextGetConfig) to cancel a previously placed asynchronous GetConfig() request.

Gets the current connection information.

This is an asynchronous function.

In the case of this function call, the members of class TConnectionInfoV1 or any later derived versions supplied by the client will be returned, eg. TConnectionInfoVx.

Use RTelSubSessionBase::CancelAsyncRequest(EPacketContextGetConnectionInfo) to cancel a previously placed asynchronous GetConnectionInfo() request.

Gets the current connection speed.

This is an asynchronous function.

Use RTelSubSessionBase::CancelAsyncRequest(EPacketContextGetConnectionSpeed) to cancel a previously placed asynchronous GetConnectionSpeed() request.

Allows a client to get details on the current amount of data transmitted and received over the airlink since the context was activated, in version 1 of the API.

This synchronous method may be called by the client application.

Allows a client to get details on the current amount of data transmitted and received over the airlink since the context was activated, for version 2 of this API onwards.

This is an asynchronous function. Note that the synchronous variant of this method is deprecated.

Introduced in v7.0S.

Extracts DNS server names from the context since version 2 of the API.

Supported from v7.0S.

GetDNSInfo() is needed when the client uses dynamic IPv4 PDP addresses. After the context is activated the client needs to know the actual primary and secondary DNS addresses to use when sending packet data. As the network may have supplied these addresses there is a need for an API method to get these addresses from the TSY.

Gets the most recent error to have occurred. This may be used, for instance, to retrieve which error caused PPP to close down prematurely.

This function may be called by the client.

This asynchronous method may be called by the client application. Retrieves information about the packet filter specified by the aIndex parameter since version 2 of this API. It is usual to use this function in conjunction with the EnumeratePacketFilters() method, which returns the current number of defined packet filters in the TFT in its 'aCount' argument.

Supported from v7.0S

Allows a client to retrieve the name of the Quality of Service profile (RPacketQoS) associated with the context.

This is an synchronous function.

Allows a client to get the current status of the context.

This synchronous function may be called by the client application.

Enables asynchronous resource reservation for a new primary or secondary context at the creation phase, since version 2 of the API.

This is an asynchronous function.

Supersedes the LoanCommPort() and RecoverCommPort() methods, which are now deprecated. This new method enables asynchronous resource reservation for a new primary or secondary context at the creation phase.

The InitialiseContext() method still contains the information that was previously in the LoanCommPort() method, i.e. details of the comm port to be used for sending/receiving user data. It however has an additional member which will return any additional information generated by context creation.

Introduced in v7.0S

Provides a client with details of the comm port to be used for sending/receiving user data in version 1 of the API. This comm port is used by Network Interfaces, NIFs, (for example: PPP.NIF) to send and receive data. In a 2-box device this port would generally be the same as that used by the TSY to set up and control the connection. In a 1-box device this port would generally be different to the port used by the TSY to set up and control the connection.

This asynchronous function may be called by the client application.

Use RTelSubSessionBase::CancelAsyncRequest(EPacketContextLoanCommPort) to cancel a previously placed asynchronous LoanCommPort() request.

Superceded in v7.0S

This asynchronous method may be called by the client application. It invokes an MS-initiated modification of an active context in the network since version 2 of the API. The client must previously have altered either the requested QoS profile of the context and/or the TFT whilst the context was active before calling this method.

Supported from v7.0S

Allows a client to be notified whenever a change in the current context is detected and gets the updated configuration.

This is an asynchronous function.

In the case of this function call, the value for each parameter will be input by the TSY.

It should be noted that once the notification completes, the client must then re-post the notification if they wish to continue receiving the notification.

Use RTelSubSessionBase::CancelAsyncRequest(EPacketContextNotifyConfigChanged) to cancel a previously placed asynchronous NotifyConfigChanged() request.

Allows a client to be notified whenever the connection information changes and gets the updated connection information.

This is an asynchronous function.

Once the notification completes, the client must then re-post the notification if they wish to continue receiving further notifications.

Allows a client to be notified whenever the current connection speed changes and gets the current connection speed.

This is an asynchronous function.

Once the notification completes, the client must then re-post the notification if they wish to continue receiving further notifications.

Use RTelSubSessionBase::CancelAsyncRequest(EPacketContextNotifyConnectionSpeedChange) to cancel a previously placed asynchronous NotifyConnectionSpeedChange() request.

Allows a client to be notified of a change in the volume of data transmitted and received over the airlink since the context was activated and gets the new volume.

The notification will only complete when the change in volume increases by a client-specified amount (granularity). The default granularity for each direction (rx/tx) is 4KB.

This is an asynchronous function.

Once the notification completes, the client must then re-post the notification if they wish to continue receiving further notifications.

Use RTelSubSessionBase::CancelAsyncRequest(EPacketContextNotifyDataTransferred) to cancel a previously placed asynchronous NotifyDataTransferred() request.

Allows a client to receive a notification whenever a change in the status of the context is detected and gets the new context status.

This is an asynchronous function.

Once the notification completes, the client must re-post the notification if they wish to continue receiving further status change notifications.

Use RTelSubSessionBase::CancelAsyncRequest(EPacketContextNotifyStatusChange) to cancel a previously placed asynchronous NotifyStatusChange() request.

Opens a handle on an existing context (RPacketContext) object, either primary or secondary, identified by a name.

KErrNotFound is returned if the object does not exist.

An opened RPacketContext must be closed explicitly by calling Close() to prevent a resource (memory) leak.

Creates a primary PDP context (i.e. RPacketContext) on an existing RPacketService connection.

There is a global mutex around this method and the RPacketService::OpenNewSecondaryContext() method. There is a potential problem with an Open function that makes an initial "set-up" function call - another client could also call OpenNewSecondaryContext() or OpenNewContext() at the same time, and the wrong client's OpenNewObjectL() will reach the TSY first. This would mean clients would receive handles to the wrong context! To avoid this, the API code for both OpenNewContext() and OpenNewSecondaryContext() must have a shared global mutex around it, so only one client can call either of these two functions at any one time.

The TSY will return KErrUmtsMaxNumOfContextExceededByPhone if the number of PDP contexts supported by the phone is exceeded. The TSY will return KErrUmtsMaxNumOfContextExceededByNetwork if the number of PDP contexts supported by the network is exceeded.

An opened RPacketContext must be closed explicitly by calling Close() to prevent a resource (memory) leak.

Creates a new secondary context from an existing context (either primary or secondary) since version 2 of the API.

The configuration of the existing context is used by the new one so the client need not call the RPacketContext::SetConfig() method.

Immediately after the creation of the newly created secondary context, a client must - a) ensure that they specify the requested QoS using an RPacketQoS object; b) add a packet filter to the secondary object. This assumes that there already exists a primary or secondary context for this NIF without a TFT. If this is not the case, it is not mandatory that a packet filter is added to this new secondary context before activation. The TSY will return KErrNotSupported if it does not support secondary contexts.

The TSY will return KErrUmtsMaxNumOfContextExceededByPhone if the number of PDP contexts supported by the phone is exceeded. The TSY will return KErrUmtsMaxNumOfContextExceededByNetwork if the number of PDP contexts supported by the network is exceeded.

There is a global mutex around this method and the RPacketService::OpenNewContext() method. There is a potential thread timing issue with an Open function that makes an initial "set-up" function call - another client could also call OpenNewSecondaryContext() or OpenNewContext() at the same time, and the wrong client's OpenNewObjectL() will reach the TSY first. This would mean clients would receive handles to the wrong context! To avoid this, the API code for both OpenNewContext() and OpenNewSecondaryContext() must have a shared global mutex around it, so only one client can call either of these two functions at any one time.

Allows a client, who previously called LoanCommPort(), to inform ETel and hence the TSY that it has finished with the comm port, in version 1 of the API.

This asynchronous function may be called by the client application.

Use RTelSubSessionBase::CancelAsyncRequest(EPacketContextRecoverCommPort) to cancel a previously placed asynchronous RecoverCommPort() request.

Superceded in v7.0S.

Removes the Authorization Token and Flow Identifiers set from the packet context object. This is identified by aAuthorizationToken. This asynchronous method may be called by the client application.

This asynchronous method may be called by the client application. Removes a packet filter from the TFT belonging to this context, since version 2 of the API.

Passes to the TSY all the parameters necessary to configure the particular context. The parameters are passed via a packaged TContextConfigGPRS/ TContextConfigCDMA/TContextConfigR99_R4/RPacketMbmsContextTContextConfigMbmsV1 object depending on the current network mode.

This is an asynchronous function.

In the case of this function call, the value for each TContextConfigXXX parameter will be input by the client and probably obtained from CommDB. To determine how to correctly unpack the descriptor inside the TSY, the TSY must first cast the descriptor to a TPacketDataConfigBase pointer and check whether ExtensionId() returns a KConfigGPRS, KConfigCDMA,KConfigRel99Rel4 or KConfigMBMS. The TSY will then cast the descriptor to the correct TPacketDataConfigBase-derived class.

Use RTelSubSessionBase::CancelAsyncRequest(EPacketContextSetConfig) to cancel a previously placed asynchronous SetConfig() request.

Anonymous access required.

Modes: GRPS, CDMA

Determines which fields in the TConnectionInfoXXX parameter class are valid.

TConnectionInfoV1

Identifiers for the type of data data compression applicable for SNDCP only, as defined in 3GPP TS 44.065, section 6.6.1.1.4. Values listed in the enumeration do not hold same numerical values as those defined in the specifications, as ENoDataComression and EManufacturerDefaultDataComression are introduced in order to be utilised when no compression and device default compression algorithm are needed, respectively.

Maximum length of DNS Fully Qualified Domain Name (RFC 1123)

Identifiers for type of SNDCP & PDCP header compression as defined in 3GPP TS 44.065, section 6.5.1.1.4, Values listed in the enumeration do not hold same numerical values as those defined in the specifications, as ENoHeaderCompression and EManufacturerDefaultHeaderCompression are introduced in order to be utilised when no compression and device default compression algorithm are needed, respectively.

Packet Filter type identifier.

Identifiers for Packet Flow Context. See Table 10.5.161/3GPP TS 24.008.

PCO additional parameter identifiers in MS to network direction, as defined in 3GPP TS 24.008, section 10.5.6.3

PCO additional parameter identifiers in network to MS direction, as defined in 3GPP TS 24.008, section 10.5.6.3

Protocol identifiers, as defined in 24.008, section 10.5.6.3

Defines the protocol used to connect to the packet data gateway.

Modes: GRPS

Service option numbers identify the various packet data services available on the CDMA packet network.

Modes: CDMA 9.5

Buffer for various sorts of authorisation data since version 2 of the API.

Supported from v7.0S.

Data channel package since version 2 of the API.

Supported from v7.0S.

Buffer to hold the GSN address.

KGSNNameLength

Array to hold either IPv4 or IPv6 address or Subnet mask since version 2 of the API.

Supported from v7.0S.

Packaged TPacketFilterV2.

Packaged TPacketFilterV3.

Buffer to hold the protocol address.

KMaxPDPAddressLength

DNS information package since version 2 of the API.

Supported from v7.0S.