13 Detailed operation procedures for GPRS control

29.0783GPPCAMEL Application Part (CAP) specificationCustomised Applications for Mobile network Enhanced Logic (CAMEL) Phase XRelease 17TS

Tools: ARFCN - Frequency Conversion for 5G NR/LTE/UMTS/GSM

NOTE Where a parameter for a GPRS control Operation is marked OPTIONAL in ASN.1, the reader is referred to the conditions for presence for this parameter, specified in the respective Information Flow in 3GPP TS 23.078 [7].

13.1 ActivityTestGPRS procedure

13.1.1 General description

The gsmSCF uses this operation to check for the continued existence of a relationship between the gsmSCF and the gprsSSF. If the relationship is still in existence, then the identified instance of gprsSSF will respond. If the ActivityTestGPRS operation timer expires, then the gsmSCF will assume that the receiving entity has failed in some way and will take appropriate action. This operation opens a new SS7 dialogue between gsmSCF and gprsSSF.

13.1.1.1 Parameters

None.

13.1.2 Responding entity (gprsSSF)

13.1.2.1 Normal procedure

gprsSSF preconditions:

(1) A relationship exists between the gsmSCF and the gprsSSF.

(2) The gprsSSME FSM is in the state "Idle Management".

(3) No active TC dialogue exists at the moment of receiving ActivityTestGPRS.

gprsSSF postconditions:

(1) The gprsSSME FSM transits to the state "Non-call Associated Treatment".

(2) If there is a gprsSSF using the GPRS-Reference Number, then the gprsSSME FSM sends a Return Result "ActivityTestGPRS" to the gsmSCF. The gprsSSME FSM then returns to the state "Idle Management".

If there is no gprsSSF using the GPRS-ReferenceNumber, then the gprsSSME FSM will issue a U‑Abort. The gprsSSME FSM then returns to the state "Idle Management".

(3) The temporary TC dialogue is closed.

If at the time of receiving ActivityTestGPRS there is an active TC dialogue for this GPRS Dialogue, then the gprsSSME FSM issues a U-Abort with Abort reason "overlapping-dialogue".

13.1.2.2 Error handling

Generic error handling for the operation related errors is described in clause 10 and the TC services used for reporting operation errors are described in clause 14.

13.2 ApplyChargingGPRS procedure

13.2.1 General description

The gsmSCF uses this operation for interacting with the gprsSSF function "CSE control of GPRS session or PDP Context duration and volume". The ApplyChargingGPRSReport operation provides the feedback from the gprsSSF to the gsmSCF. The charging scenarios supported by this operation are those given in 3GPP TS 22.078 [3] for "CSE control of GPRS session and PDP Context duration and volume".

If this procedure is used within a PDP Context dialogue, then the charging instruction shall pertain to the PDP Context only. Data volume threshold and duration threshold may be defined separately.

If this procedure is used within a GPRS Session dialogue, then the charging instruction may pertain to the GPRS Session or to a single PDP Context. Charging for a PDP Context may be on duration and/or volume. Charging for a GPRS Session may be on duration only.

NOTE: Charging for a PDP Context on duration and volume requires two ApplyChargingGPRS operations.

13.2.1.1 Parameters

– chargingCharacteristics:
This parameter is a choice between parameters required for "CSE control of a GPRS session or a PDP Context duration or volume":

– maxTransferredVolume:
This parameter specifies the maximum volume that may be transferred before a ApplyChargingReportGPRS shall be sent to the gsmSCF.

– maxElapsedTime:
This parameter specifies the maximum period of time before a ApplyChargingReportGPRS shall be sent to the gsmSCF.

– tariffSwitchInterval:
This parameter indicates the time duration until the next tariff switch. The measurement of the elapsed tariff switch period shall start immediately after successful execution of this operation.

– pDPID:
This parameter identifies the PDP Context, within the GPRS Session dialogue, to which the charging instruction applies.

13.2.2 Responding entity (gprsSSF)

13.2.2.1 Normal procedure

gprsSSF preconditions:

(1) A control relationship exists between the gsmSCF and the GPRS Session or PDP Context to which the operation applies.

(2) The gprsSSF FSM is in one of the following states: "Waiting_for_Instructions" or "Monitoring".

gprsSSF postconditions:

(1) No gprsSSF FSM state transition.

On receipt of this operation, the gprsSSF shall set the charging data using the information elements included in the operation.

13.2.2.2 Error handling

"TaskRefused": In addition to the generic error handling noted below, this error shall be indicated when:

– a previously received GPRS Session or PDP Context period or volume duration is pending;

– a tariffSwitchInterval is indicated when a previously received tariffSwitchInterval is pending;

the gprsSSF has received an ApplyChargingGPRS operation for a PDP Context that is already disconnected;
the gprsSSF has received an ApplyChargingGPRS operation for the GPRS Session when the subscriber is already detached.

Generic error handling for the operation related errors is described in clause 10 and the TC services used for reporting operation errors are described in clause 14.

13.3 ApplyChargingReportGPRS procedure

13.3.1 General description

The gprsSSF uses this operation to report charging related information to the gsmSCF as requested by the gsmSCF using the ApplyChargingGPRS operation.

Timing of duration and measuring of transferred data (if applicable) shall be started when either an Attach, PDP Context Establishment Acknowledgement or an Inter SGSN Routeing Area Update acceptance is detected by the gprsSSF.

A report shall be made when a PDP Context Disconnect, a Detach or a Change in QoS is detected by the gprsSSF or when the gprsSSF detects that the transferred volume or elapsed time duration indicated in the parameter "transferredVolume" or "elapsedTime" (received in ApplyChargingGPRS operation) has been reached.
ApplyChargingReportGPRS shall be sent only on chargeable QoS changes.

13.3.1.1 Parameters

– chargingResult:
This parameter provides the gsmSCF with the charging related information previously requested using the ApplyChargingGPRS operation. The "ChargingResult" is a choice, and can contain either of the following parameters:

– transferredVolume:
This is a choice of the following parameters:

– volumeIfNoTariffSwitch:
This parameter shall be present if no tariff switch has occurred for the PDP Context, otherwise it shall be absent. If present, then the volume transferred since the detection of the event that triggered volume count shall be reported.

– volumeIfTariffSwitch:
This parameter shall be present if a tariff switch has occurred for the PDP Context, otherwise it shall be absent. This parameter may contain the following information:

– volumeSinceLastTariffSwitch:
The volume since the detection of the event that triggered volume count or the last tariffSwitch (whichever of these events was last detected) shall be reported.

– VolumeTariffSwitchInterval:
This parameter shall be present only if a tariff switch was detected after the event that triggered volume count for the PDP Context in the current volume count period. If present, the volume between either the detection the event that triggered volume count or the previous tariff switch (whichever of these events was last detected) and the last tariff switch shall be reported.

– elapsedTime:
This parameter is a choice of the following parameters:

– timeGPRSIfNoTariffSwitch:
This parameter shall be be present if no tariff switch has occurred for the GPRS Session or the PDP Context, otherwise it shall be absent. If present, then the elapsed time since the detection of the event that triggered time count shall be reported.

– timeGPRSIfTariffSwitch:
This parameter shall be present if a tariff switch has occurred for the GPRS Session or the PDP Context, otherwise it shall be absent. TThis parameter may contain the following information:

– timeGPRSSinceLastTariffSwitch:
The time since the event that triggered time count or the last tariffSwitch shall be reported.

– timeGPRSTariffSwitchInterval:
This parameter shall be present only if a tariff switch was detected after the event that triggered time count for the GPRS Session or PDP Context in the current time count period. If present, then the time between either the detection the event that triggered time count or the previous tariff switch (whichever of these events was last detected) and the last tariff switch shall be reported.

– qualityOfService:
This parameter identifies the QoS which was negotiated between the user, the SGSN and the GGSN.
This parameter shall be present only if the sending of the ApplyChargingReportGPRS operation was triggered by a change in Quality of Service. The "negotiated-QoS-Extension" may be present as a supplement to the "negotiated-QoS".

– active:
This parameter indicates whether the GPRS Session or PDP Context is still active

– pDPID:
This parameter identifies the PDP Context, within the GPRS Session dialogue, for which the charging report is valid.

– chargingRollOver:
This parameter indicates possible rollovers of the "ChargingResult" parameter due to the limited value ranges of the associated charging parameters. The "chargingRollOver" parameter is a choice and may contain either of the following parameters:

– transferredVolumeRollOver:
This parameter is a choice of the following parameters:

– rO-VolumeIfNoTariffSwitch:
This parameter indicates how many times the volumeIfNoTariffSwitch parameter of the chargingResult has rolled over. If no rollover has happened, then rO-VolumeIfNoTariffSwitch may be absent.

– rO-VolumeIfTariffSwitch:
This parameter is present if at least one of the parameters below is present. It may contain the following information:

– rO-VolumeSinceLastTariffSwitch:
This parameter indicates how many times the volumeSinceLastTariffSwitch parameter of the chargingResult has rolled over. If no rollover has happened, then rO-VolumeSinceLastTariffSwitch may be absent.

– rO-VolumeTariffSwitchInterval:
This parameter indicates how many times the VolumeTariffSwitchInterval parameter of the chargingResult has rolled over. If no rollover has happened, then rO-VolumeTariffSwitchInterval may be absent.

– elapsedTimeRollOver:
This parameter is a choice of the following parameters:

– rO-TimeGPRSIfNoTariffSwitch:
This parameter indicates how many times the timeGPRSIfNoTariffSwitch parameter of the chargingResult has rolled over. If no rollover has happened, then rO-TimeGPRSIfNoTariffSwitch may be absent.

– rO-TimeGPRSIfTariffSwitch:
This parameter shall be present if at least one of the parameters below is present. If It may contain the following information:

– rO-TimeGPRSSinceLastTariffSwitch:
This parameter indicates how many times the timeGPRSSinceLastTariffSwitch parameter of the chargingResult has rolled over. If no rollover has happened, then rO-TimeGPRSSinceLastTariffSwitch may be absent.

– rO-TimeGPRSTariffSwitchInterval:
This parameter indicates how many times the timeGPRSTariffSwitchInterval parameter of the chargingResult has rolled over. If no rollover has happened, then rO-TimeGPRSTariffSwitchInterval may be absent.

13.3.2 Invoking entity (gprsSSF)

13.3.2.1 Normal procedure

gprsSSF preconditions:

(1) A relationship exists between the gsmSCF and the GPRS Session or PDP Context.

(2) A charging event has been detected that was requested by the gsmSCF via an ApplyChargingGPRS operation.

gprsSSF postconditions:

(1) If termination of the GPRS Session or a PDP Context has occurred, then:

– If the sending of ApplyChargingReportGPRS is directly followed by the reporting of an EDP-R, then the gprsSSF FSM shall transit to the state "Waiting_for_Instructions"; else

– If there are any armed EDPs or pending reports, then the gprsSSF FSM shall remain in the same state; else

– If there are no armed EDPs or pending reports, then the gprsSSF FSM shall transit to the state "Idle".

(2) If the sending of ApplyChargingReportGPRS is due to a timer or counter expiry, then:

– If there are any armed EDPs or pending reports, then the gprsSSF FSM shall remain in the same state; else

– If there are no armed EDPs or pending reports, then the gprsSSF FSM shall transit to the state "Idle".

(3) If the sending of ApplyChargingReportGPRS is due to a change in QoS of a PDP Context, then:

– The gprsSSF FSM shall remain in the same state.

13.3.2.2 Error handling

If the operation timer expires, then the gprsSSF shall abort the TC dialogue, terminate the GPRS dialogue and instruct the SGSN to handle the GPRS session or PDP context in accordance with the default GPRS handling parameter of the valid CSI.

Generic error handling for the operation related errors is described in clause 10 and the TC services used for reporting operation errors are described in clause 14.

13.4 CancelGPRS procedure

13.4.1 General description

The gsmSCF uses this operation to request the gprsSSF to disarm all pending EDPs and to cancel all pending reports for a GPRS Session or for a specific PDP Context. This enables the gprsSSF FSM to transit to the state "Idle".
This procedure can not be used to cancel a previous operation.

13.4.1.1 Parameters

– pDPID:
This parameter identifies the PDP Context, within the GPRS Session dialogue, for which the armed EDPs shall be disarmed and the pending reports shall be cancelled.

13.4.2 Responding entity (gprsSSF)

13.4.2.1 Normal procedure

gprsSSF preconditions:

(1) The gprsSSF FSM is in the state "Waiting_for_Instructions" or in the state "Monitoring".

gprsSSF postconditions:

(1) All pending ApplyChargingReportGPRS are cancelled and all pending EDPs are disarmed. If a PDPID is included in the operation, then the cancelling of the pending reports and the disarming of the armed events applies to the indicated PDP Context only.

(2) If the gprsSSF FSM was in the state "Monitoring" and there are no more armed EDPs or pending ApplyChargingReportsGPRS, then the gprsSSF FSM shall transit to the state "Idle".

If the gprsSSF FSM was in the state "Waiting_for_Instructions", it shall remain in that state. If there are no more armed EDPs or pendingApplyChargingReportsGPRS, then subsequent GPRS Session or PDP Context processing operation will result in the gprsSSF FSM to transit the state "Idle".

The GPRS Session or PDP Context to which the CancelGPRS operation applies, if in active state, shall further be treated by the gprsSSF autonomously as a normal (non-CAMEL) GPRS Session or PDP Context.

13.4.2.2 Error handling

Generic error handling for the operation related errors is described in clause 10 and the TC services which are used for reporting operation errors are described in clause 14.

13.5 ConnectGPRS procedure

13.5.1 General description

The gsmSCF uses this operation to provide an APN to the gprsSSF, to be used for establishing a PDP Context.

13.5.1.1 Parameters

– accessPointName:
This parameter contains the Access Point Name towards which the PDP Context shall be established. Refer to 3GPP TS 29.060 [12] for details on the Access Point Name.

– pDPID:
This parameter identifies the PDP Context, within the GPRS Session dialogue, for which the Access Point Name shall be used.

13.5.2 Responding entity (gprsSSF)

13.5.2.1 Normal procedure

gprsSSF preconditions:

(1) A control relationship exists between the gsmSCF and the PDP Context.

(2) The GPRS PDP Context FSM is supsended at DP PDP_Context_Establishment.

(3) The gprsSSF FSM is in the state "Waiting_for_Instructions".

gprsSSF postconditions:

(1) The gprsSSF performs the actions to establish the PDP Context using the given Access Point Name.

(2) The gprsSSF stops Tssf.

(3) If no EDPs are armed, then the gprsSSF FSM transits to the state "Idle". Otherwise the gprsSSF FSM transits to the state "Monitoring".

The gsmSSF shall not perform any implicit arming or disarming of DPs.

13.5.2.2 Error handling

Generic error handling for the operation related errors is described in clause 10 and the TC services which are used for reporting operation errors are described in clause 14.

13.6 ContinueGPRS procedure

13.6.1 General description

The gsmSCF uses this operation to request the gprsSSF to proceed with GPRS Session or PDP Context processing at the DP at which it previously suspended processing to await gsmSCF instructions. The gprsSSF continues processing without substituting new data from the gsmSCF.

13.6.1.1 Parameters

– pDPID:
This parameter identifies the PDP Context within the control relationship for which the processing shall continue.

13.6.2 Responding entity (gprsSSF)

13.6.2.1 Normal procedure

gprsSSF preconditions:

(1) A control relationship exists between the gsmSCF and the GPRS Session or PDP Context.

(2) The GPRS Session or PDP Context processing has been suspended at any DP.

(3) The gprsSSF FSM is in the state "Waiting_for_Instructions".

gsmSSF postconditions:

(1) GPRS Session or PDP Context processing continues.

(2) The gprsSSF FSM is in one of the following states:

– "Monitoring" because at least one EDP was armed or an ApplyChargingReportGPRS was requested; or

– "Idle" because no EDPs were armed and no ApplyChargingReportGPRS was requested.

13.6.2.2 Error handling

Operation related error handling is not applicable, due to class 4 operation.

13.7 EntityReleasedGPRS procedure

13.7.1 General description

The gprsSSF uses this operation to inform the gsmSCF that the GPRS Session is detached or a PDP Context is disconnected. It shall be used only when the associated event detection point (ie. for GPRS Session Detach: DP "Detach" and for PDP Context Disconnect: DP "PDP Context Disconnection") is at that moment not armed for reporting.

This operation shall be used irrespectively of the functional entity that initiated the Detach or PDP Context Disconnect and irrespectively of the cause for the Detach or PDP Context Disconnect.

When a PDP Context is terminated, then the gprsSSF shall send all pending reports of that PDP Context to the gsmSCF.
When a GPRS Session is terminated, then the gprsSSF shall send all outstanding reports of the GPRS Session to the gsmSCF.

13.7.1.1 Parameters

– gPRSCause:
This parameter gives an indication to the gsmSCF about the reason for discontinuing the PDP Context or GPRS Session. This may be used by gsmSCF if a FurnishChargingInformationGPRS operation needs to be sent to the gprsSSF.

– pDPID:
This parameter identifies the PDP Context within the GPRS Session dialogue, which has terminated.

13.7.2 Invoking entity (gprsSSF)

13.7.2.1 Normal procedure

gprsSSF preconditions:

(1) The gprsSSF FSM is in the state "Waiting_for_Instructions" or in the state "Monitoring".

gprsSSF postconditions:

(1) All armed EDPs for the indicated PDP Context or GPRS Session shall be disarmed. All connections and resources related to the indicated PDP Context or GPRS Session shall be released.
If there are no more armed EDPs or pending reports, then the gprsSSF FSM transits to the state "Idle"; otherwise the gprsSSF FSM remains in the same state.

13.7.2.2 Error handling

Generic error handling for the operation related errors is described in clause 10 and the TC services which are used for reporting operation errors are described in clause 14.

13.8 EventReportGPRS procedure

13.8.1 General description

The gprsSSF uses this operation to notify the gsmSCF of a GPRS Session or PDP Context event previously requested by the gsmSCF in a RequestReportGPRSEvent operation.

13.8.1.1 Parameters

– gPRSEventType:
This parameter specifies the type of event that is reported.

– gPRSEventSpecificInformation:
This parameter indicates the GPRS Session or PDP Context related information specific to the event.

For Change of Position GPRS Session it shall contain the "locationInformationGPRS", if available.

For Change of Position PDP Context it shall contain the "accessPointName", "chargingID", "locationInformationGPRS", "endUserAddress", Quality of Service, "timeAndTimeZone" and "gGSNAddress" and "secondaryPDP-context", if available.

For Detach and PDP Context Disconnect it shall contain the "initiatingEntity" and, conditionally, "routeingAreaUpdate". The "initiatingEntity" indicates the entity that initiated the Detach or PDP Context Disconnect. The "routeingAreaUpdate" indicates that the Detach or PDP Context Disconnect is due to inter-SGSN routeing area update.
In the case of inter-SGSN routeing area update, the gsmSCF may ignore the " initiatingEntity".

For PDP Context Establishment it shall contain the "accessPointName", "endUserAddress", "pDPInitiationType", Quality of Service, "locationInformationGPRS", "timeAndTimeZone" and "secondaryPDP-context", if available.
The Quality of Service shall contain the Requested QoS and the Subscribed QoS. The "requested-QoS-Extension" and the "subscribed-QoS-Extension" may be present as supplements to the "requested-QoS" and the "subscribed-QoS" respectively.

For PDP Context Establishment Acknowledgement it shall contain the "accessPointName", "chargingID" "endUserAddress", Quality of Service, "locationInformationGPRS", "timeAndTimeZone" and "gGSNAddress", if available.
The Quality of Service shall contain the Requested QoS, the Subscribed QoS and the Negotiated QoS. The "requested-QoS-Extension", the "subscribed-QoS-Extension" and the "negotiated-QoS-Extension" may be present as supplements to the "requested-QoS", the "subscribed-QoS" and the "negotiated-QoS" respectively.

All optional gPRSEventSpecificInformation parameters shall be sent in accordance with 3GPP TS 23.078 [7] subclause 6.6.1.4 and 3GPP TS 22.078 [3] annex "GPRS Information provided to the CSE".

– miscGPRSInfo:
This parameter contains DP related information.

– messageType:
This parameter indicates whether the message is a request, i.e. resulting from a RequestReportGPRSEvent with "monitorMode" = "interrupted", or a notification, i.e. resulting from a RequestReportGPRSEvent with "monitorMode" = "notifyAndContinue".

– pDPID:
This parameter identifies the PDP Context, within the GPRS Session dialogue, for which the event is reported.

13.8.2 Invoking entity (gprsSSF)

13.8.2.1 Normal procedure

gprsSSF preconditions:

(1) The gprsSSF FSM is in the state "Monitoring" or in the state "WaitingForInstructions".

(2) The GPRS Session or PDP Context FSM proceeds to an EDP that is armed.

gprsSSF postconditions:

(1) If the message type was notification and there are still armed EDPs that can be met or there any pending reports, then the gprsSSF FSM shall remain in the state "Monitoring".

(2) If the message type was notification and there no more EDPs armed that can be met and there are no pending reports, then the gprsSSF FSM shall transit to the state "Idle".

(3) If the message type was request, then the gprsSSF FSM shall transit to the state "Waiting_for_Instructions". GPRS Session or PDP Context processing is interrupted.

If an EDP-R is met that causes the release of a GPRS Session or PDP Context, then all EDPs related to the GPRS Session or PDP Context shall be disarmed.

13.8.2.2 Error handling

If the message type is "request" and the Tssf timer expires, then the gprsSSF shall abort the TC dialogue and shall instruct the SGSN to treat the GPRS Session or PDP Context in accordance with the default GPRS handling of the valid CSI.

Generic error handling for the operation related errors is described in clause 10 and the TC services which are used for reporting operation errors are described in clause 14.

13.9 FurnishChargingInformationGPRS procedure

13.9.1 General description

The gsmSCF uses this operation to send charging related information to a Logical GPRS record. This Logical GPRS record is CAMEL specific. The first FurnishChargingInformationGPRS operation results in the generation of a Logical GPRS record. Receipt of subsequent FurnishChargingInformationGPRS operations shall overwrite or append the contents of the Logical GPRS record.

13.9.1.1 Parameters

– fCIGPRSBillingChargingCharacteristics:
This parameter contains the following parameters;

– fCIBCCCAMELsequence1:
This parameter contains the following parameters;

– freeFormatData:
This parameter contains free-format billing and/or charging characteristics.

– appendFreeFormatData:
This parameter indicates whether previous FCI free format data is appended or overwritten. Refer to 3GPP TS 23.078 [7] for details of this mechanism.

– pDPID:
This parameter indicates the PDP Context’s Logical GPRS record to which the free format data belongs.

13.9.2 Responding entity (gprsSSF)

13.9.2.1 Normal procedure

gprsSSF preconditions:

(1) The gprsSSF FSM is in the state "Waiting_for_Instructions" or in the state "Monitoring".

gprsSSF postconditions:

(1) No gprsSSF FSM state transition.

On receipt of this operation the gprsSSF performs actions to create the Logical GPRS record, if necessary, and writes the free-format information carried in the operation into the GPRS record. A FurnishChargingInformationGPRS operation will create a Logical GPRS Data Record (CDR) if such a record does not already exist. Subsequent FurnishChargingInformationGPRS operations received, will either overwrite or append the data previously written in the free-format CDR field depending on the presence and value of the parameter "appendFreeFormatData".

The Logical GPRS records will be associated for a given GPRS Session or PDP Context with one or more physical CDRs, as specified in 3GPP TS 32.250 [14] and 3GPP TS 22.115 [4].

13.9.2.2 Error handling

Generic error handling for the operation related errors is described in clause 10 and the TC services which are used for reporting operation errors are described in clause 14.

13.10 InitialDPGPRS procedure

13.10.1 General description

The gprsSSF uses this operation after detection of a TDP-R in the GPRS Session or PDP Context state machine, to request the gsmSCF for instructions to complete the GPRS Session or PDP Context.

For a GPRS Session, the "Attach" and "Change of Position Session" TDPs may result in the InitialDPGPRS Procedure.

For a PDP Context, the "PDP Context Establishment", the "PDP Context Establishment Acknowledgement" and the "Change of Position Context" TDPs may result in the InitialDPGPRS Procedure.

If a PDP Context related TDP is met and there is at that moment a GPRS dialogue for the GPRS Session, then the gprsSSF shall not initiate the InitialDPGPRS Procedure for that PDP Context.

If the "PDP Context Establishment Acknowledgement" event occurs and this event is armed as a TDP, and there is at that moment a GPRS dialogue for the PDP Context, then the gprsSSF shall not initiate a new InitialDPGPRS Procedure for that PDP Context.

13.10.1.1 Parameters

– serviceKey:
This parameter indicates to the gsmSCF the requested IN service. It is used to address the required application/SLP within the gsmSCF; it is not used for SCP addressing.

– gPRSEventType:
This parameter indicates the armed GPRS Attach/Detach FSM or PDP Context FSM DP event, resulting in the InitialDPGPRS operation.

– mSISDN:
This parameter contains the MSISDN of the mobile subscriber for which the CAMEL service is invoked.

– iMSI:
This parameter contains the IMSI of the mobile subscriber for which the CAMEL service is invoked.

– timeAndTimezone:
This parameter contains the time that the gprsSSF is triggered, and the time zone that the invoking gprsSSF resides in.

– gPRSMSClass:
This parameter contains the MS capabilities of the mobile subscriber for which the CAMEL service is invoked.

– endUserAddress:
This parameter identifies the PDP type, PDP type organisation and the actual PDP address.

– qualityOfService:
This parameter contains the Quality of Service.
If the InitialDPGPRS operation is sent as a result of the "PDP Context Establishment" TDP, then the Quality of Service parameter shall contain the Requested QoS and the Subscribed QoS. The "requested-QoS-Extension" and the "subscribed-QoS-Extension" may be present as supplements to the "requested-QoS" and the "subscribed-QoS" respectively.
If the InitialDPGPRS operation is sent as a result of the "PDP Context Establishment Ackonwledgement" TDP or the Change of Position Context TDP, then the Quality of Service parameter shall contain the Requested QoS, the Subscribed QoS and the Negotiated QoS. The "requested-QoS-Extension", the "subscribed-QoS-Extension" and the "negotiated-QoS-Extension" may be present as supplements to the "requested-QoS", the "subscribed-QoS" and the "negotiated-QoS" respectively.

– accessPointName:
This parameter contains the requested address that the MS for which the CAMEL service is invoked for wants to connect to.

– routeingAreaIdentity:
This parameter contains the location information of the MS for which the CAMEL service is invoked.

– chargingID:
This parameter contains the charging ID that, together with the gGSNAddress, uniquely identifies the PDP Context for the MS for which the CAMEL service is invoked.

– sGSNcapabilities:
This parameter specifies the capabilities which the SGSN node can provide for the CAMEL service control.

– locationInformationInSGSN:
This parameter indicates the location of the sending MS.

pDPInitiationType:
This parameter indicates whether a PDP Context was established as a result of a network-initiated request or as a result of a subscriber request.
gGSNAddress:
This parameter refers to the IP address of the GGSN where the PDP Context terminates. It is used together with the chargingID for uniquely identification of the PDP Context for which the CAMEL service is invoked from.
secondaryPDP-context:
This parameter indicates that the PDP Context is requested as a secondary PDP Context.

– iMEI:
This parameter contains the IMEI (with software version) of the mobile subscriber for which the service is invoked.

13.10.2 Invoking entity (gprsSSF)

13.10.2.1 Normal procedure

gprsSSF preconditions:

(1) An event has been met that is armed as TDP.

(2) There is no GPRS dialogue active for that PDP Context or for the GPRS Session.

gprsSSF postconditions:

(1) A control relationship is established between the gsmSCF and the GPRS Session or the PDP Context.

(2) The gprsSSF FSM is in the state "Waiting_for_Instructions".

The address of the gsmSCF that the InitialDPGPRS operation shall be sent to, shall be fetched from the valid CSI. The gprsSSF shall provide all available parameters to the gsmSCF.

The gprsSSF application timer Tssf shall be loaded and started when the gprsSSF sends InitialDPGPRS for requesting instructions from the gsmSCF. It is used to prevent excessive GPRS Session or PDP Context duration or volume usage.

13.10.2.2 Error handling

If the gsmSCF is not accessible, then the gprsSSF instructs the SGSN to handle the GPRS Session or PDP Context in accordance with the Default GPRS Handling parameter of the valid CSI.

If Tssf expires, then the gprsSSF shall abort the interaction with the gsmSCF by means of an abort to TC and shall instruct the SGSN to handle the GPRS Session or PDP Context in accordance with the Default GPRS Handling parameter of the valid CSI.

If the MS abandons the establishment of a GPRS Session or PDP Context after the sending of InitialDPGPRS and before the TC dialogue is established, then the gprsSSF shall abort the interaction with the gsmSCF by means of an abort to TC.

Generic error handling for the operation related errors is described in clause 10 and the TC services which are used for reporting operation errors are described in clause 14.

13.11 ReleaseGPRS procedure

13.11.1 General description

The gsmSCF uses this operation to tear down by the gsmSCF an existing GPRS Session or PDP Context at any phase.

13.11.1.1 Parameters

– gPRSCause:
This parameter gives an indication to the gprsSSF about the reason of releasing the GPRS Session or a specific PDP Context. This may be used by gprsSSF for generating specific indications to the MS or to fill in the "cause" in the release message.

– pDPID:
This parameter identifies the PDP Context, within the GPRS Session dialogue, which shall be released.

13.11.2 Responding entity (gprsSSF)

13.11.2.1 Normal procedure

gprsSSF preconditions:

(1) A control relationship exists between gsmSCF and the GPRS Session or PDP Context. More specifically, in order to tear down an individual PDP Context, an EDP-R must be armed for that PDP Context. In order to make a SCP controlled detach an EDP-R must be armed for the GPRS Session.

(2) The gprsSSF FSM is in the state "Waiting_for_Instructions" or in the state "Monitoring".

gprsSSF postconditions:

(1) All pending reports for the GPRS Session or the PDP Context shall be reported to the gsmSCF.

(2) All connections and resources related to the GPRS Session or the PDP Context shall be released.

(3) All armed EDPs for the GPRS Session or the PDP Context shall be disarmed.

(4) If there are no more pending reports or armed events, then the gprsSSF FSM transits to the state "Idle".

If there are any pending reports or armed events, then the gprsSSF FSM remains in the same state.

13.11.2.2 Error handling

Generic error handling for the operation related errors is described in clause 10 and the TC services which are used for reporting operation errors are described in clause 14.

13.12 RequestReportGPRSEvent procedure

13.12.1 General description

The gsmSCF uses this operation to request the gprsSSF to monitor for a GPRS Session or PDP Context related event (e.g., events such as PDP Context establishment or detach) and to send a notification to the gsmSCF when the event is detected.

The monitoring of more than one event may be requested with a single RequestReportGPRSEvent operation, but each of these requested events will be reported in a separate EventReportGPRS operation.

13.12.1.1 Parameters

– gPRSEvent:
This parameter specifies the event or events of which a report is requested.

– gPRSEventType:
This parameter specifies the type of event of which a report is requested.

– monitorMode:
This parameter indicates how the event shall be reported. If the "monitorMode" is "interrupted", then the event shall be reported as a request; if the "monitorMode" is "notifyAndContinue", then the event shall be reported as a notification; if the "monitorMode" is "transparent", then the event shall not be reported.

– pDPID:
This parameter identifies the PDP Context, within the GPRS Session dialogue, for which the event reporting is requested

13.12.2 Responding entity (gprsSSF)

13.12.2.1 Normal procedure

gprsSSF preconditions:

(1) A control relationship exists between the gsmSCF and the GPRS Session or PDP Context.

(2) The gprsSSF FSM is in the state "Waiting_for_Instructions" or the state "Monitoring".

In the state "monitoring" only requests to disarm detection points (with MonitorMode set to "Transparent") or send notifications of events (with MonitorMode set to "NotifyAndContinue") shall be accepted.

gprsSSF postconditions:

(1) The requested EDPs have been armed or disarmed as indicated.

(2) Previously requested events are monitored until ended by a transparent monitor mode, until the end of the GPRS Session or PDP Context or until the EDPs are detected.

(3) If there sare no armed events or pending reports, then the gsmSSF FSM shall transit to the state "Idle". Otherwise it shall remain in the same state.

13.12.2.2 Error handling

Generic error handling for the operation related errors is described in clause 10 and the TC services which are used for reporting operation errors are described in clause 14.

13.13 ResetTimerGPRS procedure

13.13.1 General description

The gsmSCF uses this operation to refresh the Tssf application timer, in order to avoid the Tssf time-out at the gprsSSF.

13.13.1.1 Parameters

– timerID:
This parameter indicates which timer shall be reset. The only permissable value for this parameter is "Tssf".

– timerValue:
This parameter specifies the value to which the timer shall be set.

13.13.2 Responding entity (gprsSSF)

13.13.2.1 Normal procedure

gprsSSF preconditions:

(1) GPRS Session or PDP Context processing has been suspended at a DP.

(2) The gprsSSF FSM is in the state "Waiting_for_Instructions".

gprsSSF postconditions:

(1) The Tssf timer is loaded with the value received from the gsmSCF and is restarted.

(2) No gprsSSF FSM state transition.

13.13.2.2 Error handling

Generic error handling for the operation related errors is described in clause 10 and the TC services which are used for reporting operation errors are described in clause 14.

13.14 SendChargingInformationGPRS Procedure

13.14.1 General description

The gsmSCF uses this operation to instruct the gprsSSF on the Advice of Charge information to be sent to the MS, provided that the SGSN supports Advice of Charge. The operation may be invoked on multiple occasions.

13.14.1.1 Parameters

– sCIGPRSBillingChargingCharacteristics:
This parameter contains the Advice of Charge information:

– aOCGPRS:
This parameter specifies the Advice of Charge information that shall be sent to the MS. It may contain one or more of the following parameters:

– aOCInitial:
This is a set of Charge Advice Information elements, as defined in 3GPP TS 22.024 [2]. These CAI elements shall be sent by the gprsSSF to the MS when an Activate PDP Context Accept or Attach Accept is sent to MS and a tariff switch has not yet occurred. It may also be sent at any other time e.g. upon change of QoS or RAI.

– aOCSubsequent:
This parameter may contain the following information:

– cAIElements:
This is a set of Charge Advice Information (CAI) elements, as defined in 3GPP TS 22.024 [2]. These CAI elements shall be sent to the MS when an Activate PDP Context Accept or Attach Accept is detected and a tariff switch has occurred previously, or when Activate PDP Context Accept or Attach Accept has previously been detected and a tariff switch occurs.

– tariffSwitchInterval:
This parameter indicates to the gprsSSF the time duration until the next tariff switch. The measurement of the elapsed tariff switch period shall start immediately after successful execution of this operation.

– pDPID:
This parameter identifies the PDP Context, within the GPRS Session dialogue, for which the Advice-of-Charge instruction applies.

13.14.2 Responding Entity (gprsSSF)

13.14.2.1 Normal Procedure

gprsSSF preconditions:

(1) A relationship exists between the gsmSCF and the GPRS Session or PDP Context.

(2) The gprsSSF FSM is in the state "Waiting_for_Instructions" or in the state "Monitoring".

gprsSSF postconditions:

(1) No gprsSSF FSM state transition.

On receipt of this operation, the gprsSSF performs actions to send the Advice of Charge information to the MS, provided that the SGSN supports Advice of Charge.

If Advice of Charge is to be provided to an MS in conjunction with "CSE control of GPRS Session or PDP Context duration or volume", then the following sequence of operations shall be sent from the gsmSCF to the gprsSSF in the following order and in the same TC TC-CONTINUE or TC-BEGIN component:

ApplyChargingGPRS; SendChargingInformationGPRS.

These operations shall be processed sequentially by the gprsSSF, in the order that they are sent by the gsmSCF. In this, case parameter TariffSwitchInterval may be present either in the ApplyChargingGPRS operation or in the SendChargingInformationGPRS operation, but not in both operations. It is recommended that this parameter be transported in the ApplyGPRSCharging operation.

The TariffSwitchInterval information received with either one of these operations shall set the same tariff switch timer in the gprsSSF. This duration timer shall run from the time of successful operation execution.

13.14.2.2 Error handling

"TaskRefused": In addition to the generic error handling noted below, this error shall be indicated when:

– a tariffSwitchInterval is indicated when a previously received tariffSwitchInterval is pending.

Generic error handling for the operation related errors is described in clause 10 and the TC services which are used for reporting operation errors are described in clause 14.