Tech-invite3GPPspaceIETF RFCsSIP
Quick21222324252627282931323334353637384‑5x

Content for  TS 23.203  Word version:  17.2.0

Top   Top   Up   Prev   Next
0…   4…   5…   6…   6.1.4…   6.1.7…   6.1.10…   6.1.17…   6.2…   6.2.2…   6.2.3…   6.3   6.4…   6.8…   7…   7.3…   7.4…   7.7…   7.7.3…   7.8…   A…   A.4…   D…   P…   P.4.2.4…   P.7…   P.7.5…   P.8   Q…   S…   S.7…   S.8.8   T…

 

A.4  3GPP Accesses (GERAN/UTRAN/E-UTRAN) - GTP-based EPC |R8|p. 179

A.4.0  Generalp. 179

For 3GPP Access (GTP-based), architecture details are described in TS 23.401 and in TS 23.060.
Copy of original 3GPP image for 3GPP TS 23.203, Fig. A.4: The 3GPP EPS IP-CAN (GTP-based)
Figure A.4: The 3GPP EPS IP-CAN (GTP-based)
(⇒ copy of original 3GPP image)
Up

A.4.1  High Level Requirementsp. 180

A.4.1.1  Charging related requirementsp. 180

It shall be possible for the charging system to select the applicable rate based on:
  • Location with the granularity as specified for the credit re-authorization trigger Location change in clause A.4.3.1.1;
  • User CSG Information, including CSG ID, access mode and CSG membership indication;
  • RAT type.

A.4.1.2  QoS controlp. 180

For 3GPP Access (GTP based) it shall be possible to apply QoS control at APN-level.
QoS control per APN allows the PCC architecture to control the authorized APN-AMBR to be enforced for the total bandwidth usage of non-GBR QCIs at the PCEF within the same APN.
If there is a QCI assigned to a PCC/QoS rule which is not supported by all RATs of the IP-CAN, the PCRF shall subscribe to the event trigger 'RAT change'. At inter-RAT mobility, the PCRF will be informed and shall then modify those PCC/QoS rules in the PCEF/BBERF to align their QCI values with those supported by the current RAT.
It shall be possible for the PCRF to authorize the QCI and ARP of the default EPS bearer to be enforced by the PCEF immediately and/or at a specific point in time by providing the default EPS bearer related policy information as defined in clause A.4.3.4.
Up

A.4.2  Architectural Model and Reference Pointsp. 180

A.4.2.1  Reference architecturep. 180

In the 3GPP Access (GTP-based) architecture, see TS 23.401 and in TS 23.060,
  • the Policy and Charging Enforcement Function (PCEF) is allocated to the PDN GW;
  • the Bearer Binding and Event Reporting Function (BBERF) does not apply.

A.4.3  Functional Descriptionp. 181

A.4.3.1  Overall descriptionp. 181

A.4.3.1.1  Credit managementp. 181
For EPS the credit re-authorisation triggers in Table A.4.3-1 shall apply in addition to the ones in Table 6.1. They are applicable both in case of PCEF and in case of TDF.
Credit re-authorization trigger Description
SGSN changeThe UE has moved to a new SGSN. (Note 2)
Serving GW changeThe UE has moved to a new Serving GW. (Note 1) (Note 2)
RAT type change.The characteristics of the air interface, communicated as the radio access type, have changed.
Location change (routeing area)The routeing area of the UE has changed. (Note 2)
Location change (tracking area)The tracking area of the UE has changed. (Note 1)
Location change (ECGI)The ECGI of the UE has changed.(Note 1)
Location change (CGI/SAI)The CGI/SAI of the UE has changed.(Note 2)
Location change (eNodeB ID)The eNodeB ID of the UE has changed. (Note 1)
Change of UE presence in Presence Reporting AreaThe UE is entering/leaving a Presence Reporting Area
User CSG Information change in CSG cellUser CSG Information has changed when the UE enters/leaves/accesses via a CSG cell
User CSG Information change in subscribed hybrid cellUser CSG Information has changed when the UE enters/leaves/accesses via a hybrid cell in which the subscriber is a CSG member
User CSG Information change in un-subscribed hybrid cell (see NOTE 3 )User CSG Information has changed when the UE enters/leaves/accesses via a hybrid cell in which the subscriber is not a CSG member
NOTE 1:
These triggers are used for E-UTRAN access.
NOTE 2:
These triggers are used for GERAN/UTRAN accesses.
NOTE 3:
Due to the increased signalling load, such reporting should be applied to a limited number of subscribers only.
If the Location change trigger for GERAN/UTRAN or E-UTRAN is armed, the PDN GW should request the Serving Nodes (then SGSN or MME specifically) to report any changes in location to the level indicated by the trigger according to the procedures described in TS 23.060 or TS 23.401.
The OCS determines at credit management session establishment/modification whether the UE is located in an access type that supports reporting changes of UE presence in Presence Reporting Area. This determination relies on local configuration and may rely on whether the UE is served by a Gn-SGSN (where this reporting is not defined) or by a S4-SGSN. The "SGSN change" trigger and the "Serving GW change" trigger may be used to determine whether the UE is served by a S4-SGSN. If the access type supports it, the OCS may subscribe to Change of UE presence in Presence Reporting Area at any time during the life time of the credit management session.
If the Change of UE Presence in Presence Reporting Area trigger is armed, the PDN GW should request the Serving Nodes (the SGSN or MME) to report any changes in the UE presence in Presence Reporting Area according to the procedures described in TS 23.060 or TS 23.401.
If the User CSG Information change in CSG cell trigger is armed, the PDN GW should request the Serving Nodes (then SGSN or MME specifically) to report any changes in user CSG information when the UE enters/leaves/accesses via a CSG cell.
If the User CSG Information change in subscribed hybrid cell trigger is armed, the PDN GW should request the Serving Nodes (then SGSN or MME specifically) to report any changes in user CSG information when the UE enters/leaves/accesses via a hybrid cell in which the subscriber is a CSG member.
If the User CSG Information change in un-subscribed hybrid cell trigger is armed, the PDN GW should request the Serving Nodes (then SGSN or MME specifically) to report any changes in user CSG information when the UE enters/leaves/accesses via a hybrid cell in which the subscriber is not a CSG member.
If credit re-authorization triggers, event triggers and IP-CAN session related policy information require different levels of reporting of User CSG information for a single IP-CAN session, then the User CSG information to be requested from the Serving Nodes should be changed to the highest level of detail required.
Up
A.4.3.1.2  Event Triggersp. 182
For EPS the event triggers in Table A.4.3-2 shall apply in addition to the ones in Table 6.2 at the PCEF upon the request of the PCRF.
Event trigger Description Reported from Condition for reporting
SGSN changeThe UE has moved to a new SGSN. (Note 2)PCEFPCRF
Serving GW changeThe UE has moved to a new Serving GW. (Note 1) (Note 2)PCEFPCRF
RAT type change.The characteristics of the air interface, communicated as the radio access type, have changed.PCEFPCRF
Location change (routeing area)The routeing area of the UE has changed.PCEFPCRF
Location change (tracking area)The tracking area of the UE has changed. (Note 1)PCEFPCRF
Location change (ECGI)The ECGI of the UE has changed.(Note 1)PCEFPCRF
Location change (CGI/SAI)The CGI/SAI of the UE has changed.(Note 2)PCEFPCRF
Location change (eNodeB ID)The eNodeB ID of the UE has changed. (Note 1)PCEFPCRF
Change of UE presence in Presence Reporting AreaThe UE is entering/leaving a Presence Reporting AreaPCEFPCRF
Subscribed APN-AMBR changeThe subscribed APN-AMBR has changedPCEFAlways set
EPS Subscribed QoS changeThe QoS of the default EPS bearer has changed.PCEFAlways set
User CSG Information change in CSG cellUser CSG Information has changed when the UE enters/leaves/accesses via a CSG cell. (Note 3)PCEFPCRF
User CSG Information change in subscribed hybrid cellUser CSG Information has changed when the UE enters/leaves/accesses via a hybrid cell in which the subscriber is a CSG member. (Note 3)PCEFPCRF
User CSG Information change in un-subscribed hybrid cell (see note)User CSG Information has changed when the UE enters/leaves/accesses via a hybrid cell in which the subscriber is not a CSG member. (Note 3)PCEFPCRF
3GPP PS Data Off status changeThe PCEF reports when the 3GPP PS Data Off status changesPCEFAlways set
NOTE 1:
These triggers are used for E-UTRAN access.
NOTE 2:
These triggers are used for GERAN/UTRAN accesses.
NOTE 3:
Due to the increased signalling load, such reporting should be applied to a limited number of subscribers only.
If the Location change trigger is armed, the PDN GW should request the Serving Nodes (then SGSN or MME specifically) to report any changes in location to the level indicated by the trigger according to the procedures described in TS 23.060 or TS 23.401.
The PCRF determines at IP-CAN session establishment/modification whether the UE is located in an access type that supports reporting changes of UE presence in Presence Reporting Area. This determination relies on local configuration and may rely on whether the UE is served by a Gn-SGSN (where this reporting is not defined) or by a S4-SGSN. The "SGSN change" trigger and the "Serving GW change" trigger may be used to determine whether the UE is served by a S4-SGSN. If the access type supports it, the PCRF may subscribe to Change of UE presence in Presence Reporting Area at any time during the life time of the IP-CAN session.
If the Change of UE Presence in Presence Reporting Area trigger is armed, the PDN GW should request the Serving Nodes (SGSN or MME) to report any changes in the UE presence in Presence Reporting Area according to the procedures described in TS 23.060 or TS 23.401.
The User Location Report in the Access Network Information Reporting contains the ECGI and when the bearer is deactivated, information on when the UE was last known to be in that location.
If the User CSG Information change in CSG cell was provided as event trigger, the PDN GW should request the Serving Nodes to report any changes in user CSG information when the UE enters/leaves/accesses via a CSG cell.
If the User CSG Information change in subscribed hybrid cell was provided as event trigger, the PDN GW should request the Serving Nodes to report any changes in user CSG information when the UE enters/leaves/accesses via a hybrid cell in which the subscriber is a CSG member.
If the User CSG Information change in un-subscribed hybrid cell was provided as event trigger, the PDN GW should request the Serving Nodes to report any changes in user CSG information when the UE enters/leaves/accesses via a hybrid cell in which the subscriber is not a CSG member.
If credit re-authorization triggers, event triggers and IP-CAN session related policy information require different levels of reporting of User CSG information for a single IP-CAN session, then the User CSG information to be requested from the Serving Nodes should be changed to the highest level of detail required.
Up
A.4.3.1.3  Binding mechanismp. 183
As explained in clause 6.1.1, the binding mechanism is performed in three steps: Session Binding, PCC Rule authorization and Bearer Binding.
Session Binding has no 3GPP Access (GTP-based) specifics.
For the authorization of a PCC rule with a GBR QCI the PCRF shall assign a GBR value within the limit supported by the serving network.
For the 3GPP Access (GTP-based) the Bearer Binding is performed by the PCEF. For GERAN/UTRAN in UE-only mode the Bearer Binding mechanism is restricted by the UE provided binding between a SDF and a bearer for UE initiated resource requests.
A PCEF supporting the Bind to Default Bearer PCC rule attribute shall bind a dynamic PCC rule with this attribute to the default bearer instead of using the bearer binding mechanism defined in clause 6.1.1.4 and keep the binding as long as this attribute remains set. When the PCRF removes the Bind to Default Bearer PCC rule attribute, the bearer binding mechanism as defined in clause 6.1.1.4 shall be applied by using the QoS Class Identifier and ARP values of the dynamic PCC rule. The PCEF support for the Bind to Default Bearer PCC rule attribute is optional, and shall be indicated to the PCRF.
The bearer binding mechanism associates the PCC Rule with the EPS bearer to carry the service data flow. The association shall:
  • cause the downlink part of the service data flow to be directed to the EPS bearer in the association; and
  • assume that the UE directs the uplink part of the service data flow to the EPS bearer in the association.
Thus, the detection of the uplink part of a service data flow shall be performed on the EPS bearer over which the downlink packets of the same service data flow is directed to.
When the PDN GW is connected to an SGSN via Gn/Gp (and thus a handover from UTRAN/GERAN to E-UTRAN is possible), the bearer binding in the PCEF shall not combine PCC rules with different ARP values onto the same PDP context. For the UE-only mode (which is based on a UE provided binding) PCC rules with different ARP values shall not be authorized for the same PDP context.
Up
A.4.3.1.4  Policy Controlp. 184
For 3GPP Access (GTP based) the policy control functionalities should include the following functionality for QoS control (in addition to the functionalities listed in clause 6.1.5):
  • Authorization and enforcement of the maximum QoS that is authorized for the total bandwidth usage of non-GBR QCIs at an APN.
  • Authorization and enforcement of the maximum QoS allocated to the Default EPS bearer. The Default EPS bearer shall have a non-GBR QCI as defined in TS 23.401, clause 4.7.2.1.
Up

A.4.3.2  Functional Entitiesp. 184

A.4.3.2.1  Policy Control and Charging Rules Function (PCRF)p. 184
The following information represents 3GPP EPS specific values of the ones listed in clause 6.2.1.1:
  • Subscriber Identifier in the form of IMSI, MSISDN;
  • Type of IP-CAN is set to 3GPP-EPS.
The PCEF may provide the following information (in addition to the information in clause 6.2.1.1):
  • Subscribed APN-AMBR;
  • Default EPS Bearer QoS.
The SPR may provide the following information for a subscriber (in addition to the information in clause 6.2.1.1) connecting to a specific PDN:
  • Authorized APN-AMBR for 3GPP Access;
  • Authorized Default EPS Bearer QoS.
The Authorized APN-AMBR and the Authorized Default EPS Bearer QoS are derived by the PCRF from SPR interaction, according to operator policy.
The PCRF shall upon indication of PCC rule removal due to PS to CS handover notify the AF that the associated flows are no longer served by the PS-domain due to PS to CS handover.
If vSRVCC is supported in the serving network, the PCRF (V-PCRF if roaming) provides an indicator via Gx to the PCEF to indicate that vSRVCC is allowed for the flow corresponding to the video component of the voice/video call.
The PCRF shall provide SDF filters in the PCC rule as received in the packet filter information from the PCEF.
If the PCRF receives a request for addition of service data flow(s) with a reference to existing SDF filter identities (and by that to existing PCC rule(s)), the PCRF shall use the QCI or ARP of the existing PCC rule for the new service data flow(s).
Up
A.4.3.2.2  Policy and Charging Enforcement Function (PCEF)p. 184
In the 3GPP Access (GTP-based) architecture the PCEF enforce QoS Policies as indicated by the PCRF in accordance to what is stated in clause 6.2.2.1 with the following additions:
  • Authorized APN-AMBR enforcement. The PCEF shall enforce the authorized APN-AMBR received via the Gx interface for the total bandwidth usage of non-GBR QCI for the APN.
  • Authorized Default EPS Bearer QoS Enforcement. The PCEF receives the authorized QoS for the default bearer over Gx interface. The PCEF enforces it which may lead to the upgrade or downgrade of the default EPS Bearer QoS. The PCEF shall re-evaluate the bearer binding (as defined in clause 6.1.1.4) taking into account the default bearer QoS change and any PCC Rule operation requested by the PCRF.
When the PDN GW is connected via Gn/Gp (and thus handover from UTRAN/GERAN to E-UTRAN is possible), the PDN-GW shall map QoS parameters of EPS bearers and APN-AMBR (if not received via Gn/Gp) to/from Release 99 and Release 97/Release 98 QoS parameter values of PDP-contexts as specified in Annex E of TS 23.401. The PDN GW shall mediate Gn/Gp procedures so that PCRF experiences no difference compared to S5/S8 procedures.
Only the GBR per bearer is used for resource reservation (e.g. admission control in the RAN).
The MBR (per PCC rule / per bearer) and the authorized APN-AMBR are used for rate policing.
Up
A.4.3.2.3  Application Function (AF) |R9|p. 185
The AF instructions to report loss of transmission resources will result in a notification from the PCRF that may include an indication that the transmission resources are lost due to PS to CS handover.

A.4.3.3Void

A.4.3.4  IP-CAN bearer and IP-CAN session related policy information |R9|p. 185

For EPS the IP-CAN bearer and IP-CAN session related policy information in Table A.4.3.4-1 shall apply in addition to the ones in Table 6.4 and Table A.4.
A Presence Reporting Area may be defined as a short list of TAs or eNBs and/or ECGI for E-UTRAN, a short list of RAs or SAIs or CGIs for UTRAN, and a short list of RAs or CGIs for GERAN.
Attribute Description PCRF permitted to modify the attribute Scope
Authorized default EPS bearer QoSDefines the QCI and ARP of the default EPS bearer.YesIP-CAN session
Subsequent default EPS bearer QoS (NOTE 1)Defines the QCI and ARP of the default EPS bearer to be applied by the PCEF when the default EPS bearer QoS change time is reached.No (NOTE 2)IP-CAN session
Default EPS Bearer QoS change time (NOTE 1)Defines the time at which the PCEF shall apply the subsequent default EPS bearer QoS.No (NOTE 2)IP-CAN session
NOTE 1:
Both parameters shall be provided together. The PCRF may provide up to four instances of them.
NOTE 2:
The PCRF may replace all instances of Subsequent default EPS bearer QoS that have been provided previously with a new instruction. There is no operation to modify a previously provided instance of Subsequent default EPS bearer QoS and/or Default EPS Bearer QoS change time.
The purpose of the default EPS bearer related policy information in Table A.4.3.4-1 is to provide QCI and ARP that is applicable to the default bearer of an IP-CAN session. The PCRF may provide the authorized default EPS bearer QoS in every interaction with the PCEF. The PCEF shall apply the authorized default EPS bearer QoS for the IP-CAN session, including the necessary bearer binding actions.
If dynamic PCC rules are used and the PCEF has indicated that it supports the PCC rule attribute Bind to Default Bearer, the PCRF may provide a subsequent default EPS bearer QoS together with a default EPS bearer QoS change time. When the default EPS bearer QoS change time is reached, the PCEF shall apply the corresponding subsequent default EPS bearer QoS as the new authorized default EPS bearer QoS for the IP-CAN session and perform the necessary bearer binding actions for all of the respective dynamic PCC rules. To keep dynamic PCC rules bound to the default bearer, the PCRF shall include the attribute Bind to Default Bearer in every dynamic PCC rule intended to remain bound to the default bearer.
The PCRF may provide up to four instances of subsequent default EPS bearer QoS.
The PCEF shall discard any previously received subsequent default EPS bearer QoS instances on explicit instruction as well as whenever the PCRF provides a new instruction for one or more subsequent changes to the default EPS bearer QoS or any other subsequent parameter.
Up

A.4.3.5  TDF session related policy information |R12|p. 186

For EPS the TDF session related policy information in Table A.4a shall apply in addition to the ones in Table 6.4a.

A.4.4  PCC Procedures and Flowsp. 186

A.4.4.1  Introductionp. 186

For the 3GPP Access (GTP-based), an IP-CAN session is established by the Create Default Bearer message. The IP-CAN session is terminated when the last EPS bearer of the IP-CAN session is disconnected.
From the network scenarios listed in clause 7.1, the Case 1 (no Gateway Control Session) applies.

A.4.4.2  IP CAN Session Establishmentp. 186

In the case of IP-CAN Session Establishment (described in clause 7.2), the PCEF provides to PCRF (in addition to the parameters described in clause 7.2): the User Location Information, Serving Network, Serving-GW address and RAT type.
The PCEF shall also forward the network capability of reporting of changes in CGI/SAI/RAI to the PCRF.
The PCRF includes, in the IP-CAN Session Establishment Ack, PCC Rules with QCI and ARP matching the Authorized Default EPS Bearer QoS, Authorized APN-AMBR and Authorized Default EPS Bearer QoS. If bearer establishment mode is UE/NW, the PCRF may also include PCC Rules requiring a QCI and ARP different from the Default Bearer QoS and for which NW mode applies.
Up

A.4.4.3  GW (PCEF) initiated IP CAN Session terminationp. 186

The GW (PCEF) initiated IP-CAN Session termination procedure (described in clause 7.3.2) has no 3GPP specific information.

A.4.4.4  IP CAN Session Modificationp. 187

A.4.4.4.1  IP CAN Session Modification; GW (PCEF) initiatedp. 187
For IP-CAN session modification (described in clause 7.4.1) the PCEF includes the modification of any of the 3GPP specific information listed in clause A.4.4.2.
If the PS to CS handover indicator is set for an IP-CAN bearer that is deleted, the PCEF reports termination of transmission resources for associated PCC Rules due to PS to CS handover.
The PCRF may provide the following parameters in the Acknowledgement of the IP-CAN Session Modification to the PDN GW (in addition to the parameters in clause 7.4.1): Authorized APN-AMBR, Authorized Default EPS Bearer QoS.
Up
A.4.4.4.2  IP CAN Session Modification; PCRF initiatedp. 187
The PCRF may provide the following parameters in the Policy and Charging Rule Provision to the PDN GW (in addition to the parameters in clause 7.4.2): Authorized APN-AMBR, Authorized Default EPS Bearer QoS.
Whenever the PCRF modifies the Authorized Default EPS Bearer QoS, the PCRF shall simultaneously modify the QCI and ARP of all PCC Rules that, according to the operator policy, shall have the same QoS as the default bearer.
A modification of the Authorized Default EPS Bearer QoS requires that at least one PCC Rule with a matching QoS can be bound to the default bearer as defined in clause 6.1.1.4.
Up

A.5  3GPP Accesses (GERAN/UTRAN/E-UTRAN) - PMIP-based EPC |R8|p. 187

A.5.0  Generalp. 187

For 3GPP Access (PMIP-based), architecture details are described in TS 23.402.
When PMIP-based S5/S8 has been deployed, the IP-CAN-specific parameter exchange occurs by means of IP-CAN Session Modification messages including the necessary information.

A.5.1  High Level Requirementsp. 187

A.5.1.0  Generalp. 187

The same requirements as in clause A.4.1 apply for 3GPP Access (PMIP-based).

A.5.1.1  QoS controlp. 187

For 3GPP Access (PMIP based) the same requirements as defined in clause A.4.1.2 apply.

A.5.2  Architectural Model and Reference Pointsp. 188

A.5.2.1  Reference architecturep. 188

In the 3GPP Access (PMIP-based) architecture, see TS 23.402,
  • the Policy and Charging Enforcement Function is allocated to the PDN GW;
  • the Bearer Binding and Event Reporting Function (BBERF) is allocated to the Serving GW.
The Gxx applies and corresponds to the Gxc, as defined in TS 23.402. One Gateway Control Session corresponds to one IP-CAN session.

A.5.3  Functional Descriptionp. 188

A.5.3.1  Overall Descriptionp. 188

A.5.3.1.1  Binding mechanismp. 188
The same considerations as in clause A.4.3.1.3 apply with the following modifications:
  • For the 3GPP Access (PMIP-based) the Bearer binding is performed by the BBERF.
A.5.3.1.2  Credit managementp. 188
For 3GPP Access (PMIP-based EPC) the same credit re-authorisation triggers as defined in Table A.4.3-1 apply.
A.5.3.1.3  Event triggersp. 188
For 3GPP Access (PMIP-based EPC) the same event triggers as defined in Table A.4.3-2 apply. However, they apply at the BBERF (and not at the PCEF) upon the request from the PCRF.
Up

A.5.3.2  Functional Entitiesp. 188

A.5.3.2.1  Policy Control and Charging Rules Function (PCRF)p. 188
For 3GPP Access (PMIP based) the same requirements as defined in clause A.4.3.2.1 apply with the following modification:
  • Default EPS Bearer QoS and Subscribed APN-AMBR are provided by the BBERF.
For 3GPP Access (PMIP based), the PCRF receives information about supported bearer establishment modes from the PCEF and provides the bearer establishment mode to be used to the PCEF, i.e. in the same way as for 3GPP Access (GTP based).
Up
A.5.3.2.2  Policy and Charging Enforcement Function (PCEF)p. 188
For 3GPP Access (PMIP based) the same requirements as defined in clause A.4.3.2.2 apply with the following modification:
  • For the 3GPP Access (PMIP-based) the enforcement of the Authorized Default EPS Bearer QoS is not performed by the PCEF.
A.5.3.2.3  Bearer Binding and Event Reporting Function (BBERF)p. 189
In the 3GPP Access (PMIP-based) the BBERF enforces QoS Policies as indicated by the PCRF in accordance to what is stated in clause 6.2.7.3 with the following additions:
  • Authorized Default EPS Bearer QoS Enforcement. The BBERF receives the authorized QoS for the default bearer over Gxx interface. The BBERF enforces it which may lead to the upgrade or downgrade of the default EPS Bearer QoS. The BBERF shall re-evaluate the bearer binding (as defined in clause 6.1.1.4) taking into account the default bearer QoS change and any QoS Rule operation requested by the PCRF.
Up

A.5.3.3Void

A.5.3.4Void

A.5.3.5  IP-CAN bearer and IP-CAN session related policy information |R9|p. 189

For 3GPP Access (PMIP based) the same requirements as defined in clause A.4.3.4 apply.

A.5.3.6  TDF session related policy information |R12|p. 189

For 3GPP Access (PMIP based) the same requirements as defined in clause A.4.3.5 apply.

A.5.4  PCC Procedures and Flowsp. 189

A.5.4.1  Introductionp. 189

For the 3GPP Access (PMIP-based), the IP-CAN session is established by the Proxy Binding Update message to the PDN-GW. The IP-CAN session is terminated when the PMIP session is terminated.
From the network scenarios listed in clause 7.1, the Case 2b applies.

A.5.4.2  Gateway Control Session Establishmentp. 189

For the Gateway Control Session Establishment Procedure (see clause 7.7.1), the Serving GW includes the following additional information in the Gateway Control Session Establishment message (in addition to the parameters described in clause 7.7.1): User Location Information, user GSG information, (if received from the MME), Serving-GW address, Serving Network, RAT Type, Default EPS Bearer QoS and if available the APN-AMBR are provided to the PCRF.
The PCRF includes, in the Acknowledge Gateway Control Session Establishment (in addition to the parameters described in clause 7.7.1): QoS Rules with QCI and ARP matching the Default EPS Bearer QoS. If the bearer establishment mode is UE/NW, the PCRF may also include QoS Rules requiring a QCI and ARP different from the Default EPS Bearer QoS and for which NW mode applies.
In support of PDP Context Activation procedures over S4, the BBERF must indicate various session parameters, e.g. the RAT type, to the PCRF.
The PCRF may provide the following parameters in the Acknowledgement of the Gateway Control Session Establishment to the Serving GW (in addition to the parameters described in clause 7.7.1): Authorized APN-AMBR, Authorized Default EPS Bearer QoS.
If the PS to CS handover indicator is set for an IP-CAN bearer that is deleted, the BBERF reports termination of transmission resources for associated QoS Rules due to PS to CS handover.
Up

A.5.4.3  Gateway Control and QoS Rules Requestp. 190

In the case of Gateway Control and QoS Rules Request (described in clause 7.7.3) the BBERF includes the addition/modification/removal of any the 3GPP specific information listed in clause A.5.4.2.
When a change of RAT without S GW relocation occurs, the BBERF signals the RAT type change as a parameter in an event report sent from the BBERF to the PCRF. An event report is the then sent, indicating the RAT type change, from the PCRF to the PCEF.
When Secondary PDP Context Activation occurs, the S4 SGSN performs a Request Bearer Resource Allocation procedure with the Serving GW. The Serving GW supplies the parameters required by the PCEF to properly handle the allocation of resources. These parameters are sent from the BBERF (Serving GW) to the PCRF for further processing when a PMIP-based S5/S8 is deployed.
The PCRF may provide the following parameters in the Acknowledgement of the Gateway Control and QoS Rules Request to the Serving GW (in addition to the parameters described in clause 7.7.3): Authorized APN AMBR, Authorized Default EPS Bearer QoS.
For the purpose of event reporting to the PCEF the BBERF may generate Event Reports to the PCRF if this has been requested by the PCRF.
Up

A.5.4.4  Gateway Control and QoS Rules Provisioningp. 190

In the case of Gateway Control and QoS Rules Provisioning (described in clause 7.7.4) the PCRF may provide the following parameters (in addition to the parameters described in clause 7.7.4) to the Serving GW: Authorized APN AMBR, Authorized Default EPS Bearer QoS.
Whenever the PCRF modifies the Authorized Default EPS Bearer QoS, the PCRF shall simultaneously modify the QCI and ARP of all QoS Rules that, according to the operator policy, shall have the same QoS as the default bearer.
A modification of the Authorized Default EPS Bearer QoS requires that at least one QoS Rule with a matching QoS can be bound to the default bearer as defined in clause 6.1.1.4.
For the purpose of event reporting to the PCEF the PCRF may request Event Reports from the BBERF. In response to such request the BBERF shall provide the present value(s) of the event parameters.
Up

A.5.4.5  IP CAN Session Establishmentp. 190

The PCRF may provide the following parameters in the Acknowledgement of the IP-CAN Session Establishment to the PDN GW (in addition to the parameters in clause 7.2): Authorized APN AMBR, User Location Information, user GSG information (if received from the BBERF).

A.5.4.6  IP CAN Session Modificationp. 190

A.5.4.6.1  IP CAN Session Modification; GW (PCEF) initiatedp. 190
The PCRF may provide the following parameters in the Acknowledgement of the IP-CAN Session Modification to the PDN GW (in addition to the parameters in clause 7.4.1): Authorized APN AMBR.
A.5.4.6.2  IP CAN Session Modification; PCRF initiatedp. 190
The PCRF may provide the following parameters in the Policy and Charging Rule Provision to the PDN GW (in addition to the parameters in clause 7.4.2): Authorized APN AMBR, User Location Information (if received from the BBERF), user GSG information (if received from the BBERF).
A.5.4.6.3Void

BVoid

CVoid


Up   Top   ToC