Tech-invite  3GPPspace  IETFspace
◀  ▶  21  22  23  24  25  26  27  28  29  31  32  33  34  35  36  37  38  4‑5x

Content for  TS 23.078  Word version:  19.0.0

Top   Top   Up   Prev   Next
1…   4.2…   4.3…   4.4…   4.5…   4.5.2…   4.5.3…   4.5.4…   4.5.5…   4.5.6…   4.5.7…   4.5.8…   4.6…   4.6.2…   4.6.3…   4.6.7…   4.6.13…   5…   6…   6.5…   6.6…   7…   7.5…   8…   9…   10…   11…   12…   A… 
6 GPRS interworking  6.1 Architecture  6.2 Detection Points (DPs)  6.3 Description of CAMEL Subscriber Data  6.4 Description of CAMEL State Models  6.4.1 General Handling  6.4.2 GPRS Attach/Detach State Model  6.4.3 GPRS PDP Context State Model  6.4.4 GPRS CAMEL Scenarios  6.4.5 SGSN Routeing Area Update  6.4.6 Rules for Implicit Disarming of Detection Points 
...

 

6  GPRS interworking  p. 534

6.1  Architecture  p. 534

6.1.1  Functional Entities used for CAMEL  p. 534

This subclause describes the functional architecture needed to support GPRS interworking for CAMEL. Figure 6.1 shows the functional entities involved in a GPRS session requiring CAMEL support. The architecture is applicable to the third phase of CAMEL or higher.
Copy of original 3GPP image for 3GPP TS 23.078, Fig. 6.1: Functional architecture for support of CAMEL
Figure 6.1: Functional architecture for support of CAMEL
(⇒ copy of original 3GPP image)
Up
HLR:
For subscribers requiring CAMEL support, the HLR stores the information relevant to the current subscription GPRS-CSI.
SGSN:
When processing GPRS Attach requests or Inter-SGSN Routeing Area Updates for subscribers requiring CAMEL support, the SGSN receives a GPRS-CSI from the HLR, indicating the SGSN to request instructions from the gprsSSF. The SGSN monitors on request the GPRS events and informs the gprsSSF of these events during processing, enabling the gprsSSF to control the execution of the GPRS session or individual PDP contexts in the SGSN.
gprsSSF:
see subclause 3.1.
gsmSCF:
see subclause 3.1.
Up

6.1.2  Interfaces defined for CAMEL  p. 535

6.1.2.1  SGSN - gprsSSF interface  p. 535

This is an internal interface. The interface is described in the present document to make it easier to understand the handling of DPs (arming/disarming of DPs, DP processing etc.).

6.1.2.2  gprsSSF - gsmSCF interface  p. 535

This interface is used by the gsmSCF to control a GPRS session or individual PDP Context in a certain gprsSSF. GPRS dialogues between the gprsSSF and the gsmSCF on this interface are opened as a result of the gprsSSF sending a request for instructions to the gsmSCF. A GPRS dialogue is composed of a sequence of TC dialogues linked together by the same reference. The GPRS dialogue handler allows the TC dialogue handling.

6.1.2.3  HLR - SGSN interface  p. 535

This interface is used to send CAMEL related subscriber data to a visited GPRS network, e.g. GPRS-CSI.

6.2  Detection Points (DPs)  p. 535

6.2.1  Definition and description  p. 535

GPRS events may be made visible to the gsmSCF. The DPs are the points in association at which these events are detected. The DPs for GPRS Session and PDP Context are described in subclause 6.4.2 and subclause 6.4.3.
A DP can be armed in order to notify the gsmSCF that the GPRS event was encountered, and to allow the gsmSCF to influence subsequent handling of the GPRS Session, or the PDP Context. If the DP is not armed, the processing entity continues the processing without gsmSCF involvement at this DP.
Three different types of DPs are identified:
  • Trigger Detection Point-Request (TDP-R): This detection point is statically armed and may initiate a CAMEL control relationship. This CAMEL control relationship is within a new GPRS dialogue. When the GPRS event is encountered and reported, processing is suspended.
  • Event Detection Point- Request (EDP-R): This detection point is dynamically armed within the context of a CAMEL control relationship. When the GPRS event is encountered, and reported, processing is suspended and the gprsSSF waits for instructions from the gsmSCF.
  • Event Detection Point-Notification (EDP-N): This detection point is dynamically armed within the context of a CAMEL control relationship. When the GPRS event is encountered and reported, processing is not suspended.
Arming/disarming mechanism:
A DP may be statically armed or dynamically armed. The following arming rules apply:
  • DPs for GPRS Session and PDP Context are statically armed as a result of the GPRS-CSI analysis in the SGSN.
  • DPs may be dynamically armed by the gsmSCF within the context of a CAMEL control relationship. In scenario 1 which is described in the subclause 6.4.4.1, PDP context related DPs may be armed as generic DP or as non-generic DP.
The following disarming rules apply:
  • A statically armed DP is disarmed when the GPRS-CSI is withdrawn in the HLR. Only TDP-Rs can be disarmed using this mechanism.
  • If the GPRS Session is released, then all EDPs related to the GPRS Session are disarmed.
  • If a PDP context is released, then all non-generically armed EDPs related to that PDP context are disarmed.
  • If a non-generically armed EDP is met, then EDPs for the GPRS Session or that PDP Context are disarmed, in accordance with the implicit disarming rule (see subclause 6.4.6).
  • Armed EDPs may be explicitly disarmed by the gsmSCF by means of the Request Report BCSM Event information flow.
Up

6.2.2  Relationship, DP processing rules and GPRS dialogue  p. 536

A relationship between the State Models (in the gprsSSF) and the gsmSCF for the purpose of operator specific service processing is considered to be a CAMEL relationship. There are two types of CAMEL relationships: monitor relationship and control relationship.
  • A CAMEL control relationship: the gsmSCF is able to influence the GPRS Session/PDP Context via the relationship for the given state model.
  • A CAMEL monitor relationship: the gsmSCF is not able to influence the GPRS Session/PDP Context via the relationship for the given state model.
A control relationship persists as long as there is one or more EDP-R armed for this instance of the state model, or if the gprsSSF is in the state Waiting For Instruction for this instance of state model.
A control relationship changes to a monitor relationship if the conditions for a control relationship are no longer fulfilled and one or more EDP-N is armed or one or more Apply Charging Report GPRS is outstanding for this instance of the state model. If no EDP-Ns are armed and no Apply Charging Reports GPRS are outstanding for this instance of the state model, the relationship terminates.
A GPRS dialogue exists between gprsSSF and gsmSCF if at least one of the following conditions is fulfilled:
  • There is at least one EDP armed,
  • At least one report is pending,
  • gprsSSF is in state Waiting_For_Instructions.
Up

6.3  Description of CAMEL Subscriber Data  p. 536

6.3.1  GPRS CAMEL Subscription Information (GPRS-CSI)  p. 536

This subclause defines the contents of the GPRS CAMEL Subscription Information.

6.3.1.1  gsmSCF Address  p. 536

Address to be used to access the gsmSCF for a particular subscriber. The address shall be an E.164 number to be used for routeing.

6.3.1.2  Service Key  p. 536

The Service Key identifies to the gsmSCF the service logic that shall apply.

6.3.1.3  Default GPRS Handling  p. 536

The Default GPRS Handling indicates whether the GPRS session or PDP context shall be released or continued as requested in case of error in the gprsSSF to gsmSCF dialogue.

6.3.1.4  TDP List  p. 536

The TDP List indicates on which detection point triggering shall take place.

6.3.1.5  CAMEL Capability Handling  p. 537

CAMEL Capability Handling indicates the phase of CAMEL which is asked by the gsmSCF for the service.

6.3.1.6  CSI state  p. 537

The CSI state indicates whether the GPRS-CSI is active or not.

6.3.1.7  Notification flag  p. 537

The notification flag indicates whether the change of the GPRS-CSI shall trigger Notification on Change of Subscriber Data or not.

6.3.2  gsmSCF address list for CSI |R5|  p. 537

The gsmSCF address list contains a list of gsmSCF addresses to which Notification on Change of Subscriber Data is to be sent. This list is common to all CSI.

6.4  Description of CAMEL State Models  p. 537

GPRS can support multiple PDP contexts simultaneously for an attached subscriber, requiring the behaviour of a GPRS session to be modelled by two state models, one for the attach/detach procedures (GPRS Attach/Detach State Model) and the other for modelling individual PDP Contexts (GPRS PDP Context State Model).

6.4.1  General Handling  p. 537

The GPRS State Model is used to describe the actions in an SGSN during processing of a GPRS session or PDP Contexts.
The GPRS State Model identifies the points in basic GPRS processing when Operator Specific Service (OSS) logic instances (accessed through the gsmSCF) are permitted to interact with basic GPRS control capabilities.
Figure 6.2 shows the components that have been identified to describe a GPRS State Model.
Copy of original 3GPP image for 3GPP TS 23.078, Fig. 6.2: GPRS State Model Components
Figure 6.2: GPRS State Model Components
(⇒ copy of original 3GPP image)
Up

6.4.2  GPRS Attach/Detach State Model  p. 537

The GPRS Attach/Detach State Model is used to model the behaviour of the GPRS attach/detach procedures.
When encountering a DP the Attach/Detach State Model processing is suspended at the DP and the SGSN indicates this to the gprsSSF which determines what action, if any, shall be taken in case the DP is armed.
Copy of original 3GPP image for 3GPP TS 23.078, Fig. 6.3: GPRS Attach/Detach State Model
Figure 6.3: GPRS Attach/Detach State Model
(⇒ copy of original 3GPP image)
Up
CAMEL Detection Point DP Type Description
DP AttachTDP-RA request to attach is received.
DP Change of Position GPRS SessionTDP-R (note 1), EDP-NRouteing Area Update is accepted.
DP DetachEDP-N, EDP-R A detach request is received either from the MS, the SGSN or a 'Cancel Location' received from HLR or Inter SGSN Routeing update occurred in the old SGSN.
NOTE 1:
Change of Position GPRS Session is reported as TDP-R in the case of Inter-SGSN Routeing Area Update (provided that this DP is statically armed in GPRS-CSI).
Change of Position GPRS Session is reported as EDP-N in the case of Intra-SGSN Routeing Area Update (provided that this DP is dynamically armed by the Service Logic).
Up

6.4.2.1  Description of the Attach/Detach model (PIAs)  p. 538

This subclause describes the model for the attach and detach a GPRS session in the SGSN. For each PIA a description can be found of the entry events, actions and exit events.
6.4.2.1.1  Detached  p. 538
Entry events:
  • Detach (user or network initiated) and clearing of a previous GPRS session.
  • Processing of exceptional conditions.
Actions:
  • Interface is idled.
  • Attach request is received from MS containing the IMSI/P-TMSI and the type of attach requested and, the identity of the MS is established (IMSI) (DP Attach), or Inter-SGSN Routeing Area Update Request is accepted (DP Change of Position GPRS Session).
  • Information being analyzed, e.g. GPRS-CSI is analyzed.
Exit events:
  • GPRS-CSI is analyzed (DP Attach or DP Change of Position GPRS Session).
Up
6.4.2.1.2  Attached  p. 539
Entry events:
  • GPRS-CSI is analyzed (DP Attach).
Actions:
  • MM contexts are established at the MS and the SGSN.
Exit events:
  • A GPRS Detach request is received from the MS or from the network (DP Detach).
  • Intra-SGSN Routeing Area Update is accepted (DP Change of Position GPRS Session).
  • An exception is encountered.
The GPRS Attach/Detach State Model shall only have one or more GPRS PDP Context State Models associated with it when in the Attached state. A GPRS PDP Context State Model cannot exist without its associated GPRS Attach/Detach State Model being in the Attached state. Closure of the GPRS Attach/Detach State Model via a detach will result in the idling of all associated GPRS PDP Context State Models and the release of the associated GPRS PDP Contexts.
It shall not be necessary to trigger a relationship from the GPRS Attach/Detach State Model to the gsmSCF in order for triggering to occur in an associated GPRS PDP Context State Model. However, in this latter case a GPRS Attach/Detach State Model shall still exist at the SGSN. This is so that CSE-initiated detach events sent within a given GPRS PDP Context relationship shall result in the GPRS Attach/Detach State Model transiting to the Detached state. As noted above, in this state no PDP Contexts can exist and so all associated GPRS PDP Context State Models will transit to state Idle.
Up

6.4.3  GPRS PDP Context State Model  p. 539

The GPRS PDP Context State Model is used to model the behaviour for the GPRS PDP Context procedures. There is one PDP Context State Model per GPRS PDP context.
When encountering a DP the PDP Context State Model processing is suspended at the DP and the SGSN indicates this to the gprsSSF which determines what action, if any, shall be taken in case the DP is armed.
Copy of original 3GPP image for 3GPP TS 23.078, Fig. 6.4: GPRS PDP Context State Model
Figure 6.4: GPRS PDP Context State Model
(⇒ copy of original 3GPP image)
Up
CAMEL Detection Point DP Type Description
DP PDP Context EstablishmentTDP-R (note 1), EDP-R, EDP-NActivate PDP Context request is received from the MS.
DP PDP Context Establishment AcknowledgementTDP-R (note 2), EDP-R, EDP-NCreate PDP Context response is received from the GGSN.
DP PDP Context DisconnectionEDP-N, EDP-RDeactivate PDP Context Request is received from the MS, Delete PDP Context request is received from the GGSN. Inter SGSN Routeing update occurred in old SGSN.
DP Change of Position ContextTDP-R (note 3), EDP-N, EDP-RRouteing Area Update is accepted.
NOTE 1:
The PDP Context Establishment shall be reported as TDP-R (provided that this DP is statically armed in GPRS-CSI) if there is no relationship with the gsmSCF. If there is a relationship with the gsmSCF it shall be reported as EDP-R or EDP-N if armed so.
NOTE 2:
The PDP Context Establishment Acknowledgement shall be reported as TDP-R (provided that this DP is statically armed in GPRS-CSI) if there is no relationship with gsmSCF. If there is a relationship with the gsmSCF, it shall be reported as EDP-R or EDP-N if armed so.
NOTE 3:
Change of Position Context is reported as TDP-R in the case of Inter-SGSN Routeing Area Update (provided that this DP is statically armed in GPRS-CSI) if there is no relationship with the gsmSCF.
Change of Position Context is reported as EDP-N or EDP-R in the case of Inter-SGSN Routeing Area Update (provided that this DP is armed as generic EDP) if there is a relationship with the gsmSCF.
Change of Position Context is reported as EDP-N in the case of Intra-SGSN Routeing Area Update (provided that this DP is dynamically armed by the Service Logic).
Up

6.4.3.1  Description of the PDP Context model (PIAs)  p. 540

This subclause describes the model for PDP Context State Model in the SGSN. For each PIA a description can be found of the entry events, actions and exit events.
6.4.3.1.1  Idle  p. 541
Entry events:
  • Deactivation (user or network initiated) and clearing of a previous PDP Context.
  • Processing of exceptional conditions.
Actions:
  • Interface is idled.
  • Activate PDP Context request is received from MS (containing NSAPI, PDP Type, PDP Address, Access Point Name, QoS Requested, PDP Configuration Options), or Inter-SGSN Routeing Area Update is accepted (DP Change of Position Context).
  • Information being analyzed, e.g. GPRS-CSI is analyzed.
Exit events:
  • GPRS-CSI is analyzed (DP PDP Context Establishment or DP Change of Position Context, new SGSN).
Up
6.4.3.1.2  PDP Context Setup  p. 541
Entry events:
  • GPRS-CSI is analyzed (DP PDP Context Establishment).
Actions:
  • APN and GGSN selection procedure is performed for a primary PDP context as specified in Annex A of TS 23.060. APN and GGSN selection procedure is not performed for a secondary PDP context.
  • Access Point Name is verified against the subscription. If the gsmSCF has provided an Access Point Name then the Access Point Name provided by the gsmSCF is checked against the subscription. For details refer to TS 23.060 Annex A.
  • The operator determined barring category "Barring of all Packet Oriented Services" is checked and invoked if necessary.
  • The operator determined barring category "Barring of Packet Oriented Services from access points that are within the HPLMN whilst the subscriber is roaming in a VPLMN" is checked and invoked if necessary.
  • The operator determined barring category "Barring of Packet Oriented Services from access points that are within the roamed to VPLMN" is checked and invoked if necessary.
  • The SGSN ensures that an already active PDP context is not reactivated.
  • GGSN address is derived from the Access Point Name by interrogation of a DNS. The Access Point Name consists of a Network Identifier and an Operator Identifier.
  • Create PDP Context Request is sent to the GGSN.
Exit events:
  • Create PDP Context Response is received from the GGSN (DP PDP Context Establishment Acknowledgement).
  • An exception is encountered.
Up
6.4.3.1.3  PDP Context Established  p. 541
Entry events:
  • GPRS-CSI is analyzed (DP PDP Context Establishment Acknowledgement or DP Change of Position Context).
Actions:
  • PDP context is established at the MS and the SGSN.
Exit events:
  • Deactivation of the PDP Context is received from the MS or the GGSN, or is due to an inter SGSN routing area update (DP PDP Context Disconnection, old SGSN).
  • Intra-SGSN Routeing Area Update Request is received from the MS (DP Change of Position Context).
  • Inter-SGSN Routeing Area Update (DP Change of Position Context, new SGSN).
  • An exception is encountered.
Up
6.4.3.1.4  Change of Position Context  p. 542
Entry events:
  • Inter SGSN Routing Area update accepted (new SGSN).
  • Intra SGSN Routeing Area update request received from the MS.
Actions:
  • PDP Context (containing NSAPI, PDP Type, PDP Address, Access Point Name, QoS Requested, PDP Configuration Options) is reestablished in case of Inter-SGSN Routeing Area update accepted (new SGSN).
  • Intra SGSN Routeing Area updated.
Exit events:
  • reestablishement of the PDP context at the new SGSN and return to PDP context established in case of inter SGSN Routeing Area update accepted in new SGSN (PIA PDP context established).
  • Routeing Area update completed in case of intra SGSN Routeing Area update (PIA PDP context established).
Up

6.4.4  GPRS CAMEL Scenarios  p. 542

Two different scenarios are applicable for CAMEL control of GPRS.
Scenario 1:
Scenario 1 allows CAMEL control of the GPRS session and of multiple PDP contexts related to this session within a single GPRS dialogue.
Scenario 2:
Scenario 2 allows CAMEL control of single PDP contexts. Multiple PDP contexts are controlled in this scenario via multiple GPRS dialogues.
Scenario 1 and scenario 2 are mutually exclusive, i.e. it is not possible to use both for one GPRS session at the same time in one SGSN. A GPRS session is involved in GPRS CAMEL at one moment in time either by using scenario 1 or by using possible multiple instances of scenario 2. GPRS sessions in different SGSNs are independent from a CAMEL perspective.
Up

6.4.4.1  GPRS CAMEL Scenario 1  p. 542

Scenario 1 allows CAMEL control of the GPRS session and of multiple PDP contexts related to this session within a single GPRS dialogue (Session dialogue).
Copy of original 3GPP image for 3GPP TS 23.078, Fig. 6.5: GPRS CAMEL Scenario 1
Figure 6.5: GPRS CAMEL Scenario 1
(⇒ copy of original 3GPP image)
Up
A GPRS dialogue in scenario 1 always consists of one GPRS Attach/Detach State Model and optionally of additional multiple GPRS PDP Context State Models related to the Attach/Detach State Model for the GPRS session. There is at most one GPRS Attach/Detach State Model per non idle GPRS session in one SGSN and at most one PDP Context State Model per active GPRS PDP context in one SGSN. The various PDP Context State Models are treated independently of each other.
The GPRS dialogue and the relationship between the GPRS Attach/Detach State Model and the gsmSCF are always initiated using the TDPs of the GPRS Attach/Detach State Model.
The gsmSCf requests further control or monitoring of individual GPRS PDP contexts using the Request Report GPRS Event information flow. To be informed about new individual PDP contexts the gsmSCF arms the DP 'PDP Context Establishment' or the DP 'PDP Context Establishment Acknowledgement' generically, i.e. without a PDP ID, as an EDP. To be informed about the handed over PDP contexts the gsmSCF arms the DP 'Change of Position Context' generically as an EDP-N or EDP-R.
Each GPRS PDP context is identified by a PDP ID. The PDP ID is assigned by the SGSN during PDP context establishment. The PDP ID is unique within one GPRS dialogue. The Request Report GPRS Event information flows to control new or handed over PDP contexts do not include a PDP ID. There is no 'PDP ID' related to the GPRS Attach/Detach State Model.
The PDP Id is reported to the gsmSCF in the first event notification for that PDP context.
Up

6.4.4.2  GPRS CAMEL Scenario 2  p. 543

Scenario 2 allows CAMEL control of single PDP contexts. Multiple PDP contexts are controlled in this scenario via multiple GPRS dialogues (PDP Context dialogues).
Copy of original 3GPP image for 3GPP TS 23.078, Fig. 6.6: GPRS CAMEL Scenario 2
Figure 6.6: GPRS CAMEL Scenario 2
(⇒ copy of original 3GPP image)
Up
A GPRS dialogue in scenario 2 consists of a single GPRS PDP Context State Model. There is no GPRS Attach/Detach State Model involved in this scenario. There is at most one PDP Context State Model per active GPRS PDP context in one SGSN.
There might be multiple GPRS dialogues in scenarios 2 for one GPRS session, each of the dialogues controlling a single GPRS PDP context. The various GPRS dialogues are independent of each other.
The GPRS dialogue and the relationship between the GPRS PDP Context State Model and the gsmSCF are always initiated using the TDPs for the GPRS PDP Context State Model.
Control of further individual GPRS PDP contexts in the same GPRS dialogue as in scenario 1 is not possible. There are no PDP IDs in this scenario.
Up

6.4.5  SGSN Routeing Area Update  p. 544

6.4.5.1  Intra-SGSN Routeing Area Update  p. 544

Intra-SGSN Routeing Area Update will be detected via the DP 'Change of Position GPRS Session' for the session using the GPRS Attach/Detach State Model and via the DPs 'Change of Position Context' for the individual PDP contexts using the GPRS PDP Context State Models.
It will be reported via an EDP-N if the necessary EDP-N is armed.

6.4.5.2  Inter-SGSN Routeing Area Update  p. 544

Inter-SGSN Routeing Area Update from the old SGSN to the new SGSN will be detected via the DP 'Change of Position GPRS Session' for the session using the GPRS Attach/Detach State Model and via the DPs 'Change of Position Context' using the GPRS PDP Context State Models for the individual PDP contexts which have been handed over.
Scenario 1:
Inter-SGSN Routeing Area Update from the old SGSN to the new SGSN will be detected in the new SGSN via the DP 'Change of Position GPRS Session' for the session using the GPRS Attach/Detach State Model and in the new SGSN via the DPs 'Change of Position Context' using the GPRS PDP Context State Models for the individual PDP contexts which have been handed over.
In this scenario the DP 'Change of Position GPRS Session' is armed as a TDP-R. If the Routeing Area Update is accepted the gprsSSF reports this TDP-R to the gsmSCF using the Initial DP GPRS information flow. To be informed about new PDP contexts the gsmSCF arms the DP 'PDP Context Establishment' or the DP 'PDP Context Establishment Acknowledgement' generically as EDP-R or EDP-N. The DPs 'Change of Position Context' for the PDP contexts which have been handed over will be reported with all necessary information to the gsmSCF when the gprsSSF is continued, i.e. it is not longer waiting for instructions. Contexts which are not continued in the new SGSN are not reported. The EDPs for new PDP contexts are reported as usual.
The Detach in the old SGSN is reported to the gsmSCF, provided this event is armed. All outstanding reports in the old SGSN are sent to the gsmSCF and all open CDRs are closed.
Scenario 2:
Inter-SGSN Routeing Area Update from the old SGSN to the new SGSN will be detected in the new SGSN via the DPs 'Change of Position Context' using the GPRS PDP Context State Models for the individual PDP contexts which have been handed over.
In this scenario the DP 'Change of Position Context' is armed as TDP-R. If the Routeing Area Update is accepted the gprsSSF reports these TDP-Rs PDP contexts which have been handed over to the gsmSCF using the Initial DP GPRS information flows in multiple GPRS dialogues.
The PDP Context Disconnection in the old SGSN is reported to the gsmSCF, provided this event is armed. All outstanding reports in the old SGSN are sent to the gsmSCF and the open CDR is closed.
Up

6.4.6  Rules for Implicit Disarming of Detection Points  p. 545

The two Tables below give the rules for implicit disarming of event detection points.
Implicit EDP disarming rules are specified for the Attach/Detach State Model and PDP Context State Model. The Tables specify which EDP's shall be disarmed (i.e. MonitorMode set to Transparent) if/when each EDP is encountered, irrespective of the EDP's MonitorMode (Transparent, NotifyAndContinue, or Request).
EDPs which are armed generically for GPRS PDP Context State Models shall only be implicitly disarmed at the end of the GPRS dialogue. Explicit disarming is possible.
When EDP's are armed with MonitorMode 'Request' (EDP-Rs) are encountered, any implicit EDP disarming shall take place before reporting the EDP and transiting the gprsSSF to the WFI state (if not already suspended in the WFI state).
The Table entry 'X' means that if one DP occurs (independently of arming and reporting to the gsmSCF) the marked one is implicitly disarmed. It shall be possible to rearm explicitly an implicitly disarmed DP.
Encountered DP Implicit disarmed DPs
Change of Position GPRS Session Change of Position Context Detach PDP Context Esta­blishment PDP Context Esta­blishment Acknow­ledgement PDP Context Disconnec­tion
Change of Position GPRS Session
Change of Position Context
DetachXXXXXX
PDP Context Establishment
PDP Context Establishment AcknowledgementX
PDP Context DisconnectionXXX
Encountered DP Implicit disarmed DPs
Change of Position Context PDP Context Establishment Acknowledgement PDP Context Disconnection
PDP Context Establishment AcknowledgementX
PDP Context DisconnectionXXX
Change of Position Context
Up

Up   Top   ToC