Content for TS 23.402 Word version: 18.3.0

0… 4… 4.2… 4.2.2 4.2.3 4.3… 4.4… 4.5… 4.5.7… 4.6… 4.7… 4.7.2… 4.8… 4.8.2a… 4.9… 5… 5.2… 5.4… 5.5 5.6… 5.7… 5.8… 6… 6.2… 6.3 6.4… 6.4.3… 6.5… 6.6… 6.7… 6.8… 6.10… 6.13… 6.15… 7… 7.2… 7.3 7.4… 7.5… 7.6… 7.8… 7.10… 8… 8.2.1.2 8.2.1.3… 8.2.2 8.2.3… 8.2.6… 8.3… 8.4… 8.5… 9… 9.3… 9.4… 10… 13… 16… 16.1.2… 16.1.6… 16.2… 16.2.1a… 16.3… 16.4… 16.7… 16.8… 16.10… 17… A… C… E…

5.8 ME Identity Check Procedures for PMIP-based S5/S8 5.9 UE-triggered Service Request for PMIP-based S5/S8 5.10 PMIP-based S5/S8 procedures for GERAN/UTRAN over S4 5.10.1 General 5.10.2 GPRS procedures that update the PDN-GW 5.10.3 UE allocated resources 5.10.4 Network allocated resources 5.10.5 UE released resources 5.10.6 PDN-GW released resources 5.10.7 Attach 5.10.8 Detach interaction using S4 5.10.9 Interaction with CGI/SAI reporting using S4 5.10.10 RAU Procedure Support 5.11 PDN-GW initiated IPv4 address Delete Procedure 5.12 Location Change Reporting Procedure for PMIP-based S5/S8 5.13 Support for Machine Type Communications (MTC) 5.13.1 General 5.13.2 PDN-GW control of overload 5.13.3 Usage of low access priority indicator
...

5.8 ME Identity Check Procedures for PMIP-based S5/S8 p. 107

ME identity check by the MME in case of PMIP-based S5/S8 is performed as defined for GTP-based S5/S8, see clause 5.3.2.1 (E-UTRAN Initial Attach procedure) of TS 23.401.

No ME identity check support is specified on the S5/S8 reference point.

5.9 UE-triggered Service Request for PMIP-based S5/S8 p. 107

This clause contains the procedure steps that vary between the GTP and PMIP variant of S5 and S8 for the UE-triggered Service Request procedure defined in clause 5.3.4.1 of TS 23.401, for the case where the RAT Type reported in the Service Request has changed compared to the last reported RAT Type.

Copy of original 3GPP image for 3GPP TS 23.402, Fig. 5.9-1: UE-triggered Service Request for PMIP-based S5/S8

Figure 5.9-1: UE-triggered Service Request for PMIP-based S5/S8
(⇒ copy of original 3GPP image)

This procedure concerns both the non-roaming (S5) and roaming case (S8). In the roaming case, the vPCRF in the VPLMN forwards messages between the Serving-GW and the hPCRF in the HPLMN. In the case of Local Breakout, the vPCRF forwards messages sent between the PDN-GW and the hPCRF as well. In the non-roaming case, the vPCRF is not involved at all.

The optional interaction steps between the gateways and the PCRF in the procedures in Figure 5.9-1 only occur if dynamic policy provisioning is deployed. Otherwise policy may be statically configured with the gateway.

A.1)

The Serving-GW informs the PCRF about the change of RAT type, UE Location Information IE and user CSG information (if this has been received from the MME preceding step A) by initiating the Gateway Control and QoS Policy Rules Request Procedure as specified in TS 23.203.

A.2)

The PCRF updates the PCC rules at the PDN-GW by initiating the PCC Rules Provision Procedure as specified in TS 23.203 if the PCC rules have changed based on the RAT type reported by the Serving-GW in step A.1. The UE Location Information IE and user CSG information are also sent to the PDN-GW from the PCRF (if this has been received from the Serving-GW preceding step A.1).

Further, the hPCRF notifies the PDN-GW of the change in RAT.

Step A.2 may be initiated before step A.1 completes: Once the hPCRF receives the event report from the Serving-GW as part of step A.1, the hPCRF may complete step A.1 and initiate step A.2 in any order.

5.10 PMIP-based S5/S8 procedures for GERAN/UTRAN over S4 p. 108

5.10.1 General p. 108

This clause presents the PMIP-based S5/S8 procedures equivalent to the GTP-based procedures presented in TS 23.060 for interworking. The differences required for interpretation of the PMIP-based S5/S8 procedures in other clauses of this specification are clarified below.

If PCC is not deployed, only default bearers may be provided for UE connection to a PDN. This is described fully in the PMIP-based S5/S8 procedures referred to in clause 5.10. Secondary PDP context requests are not supported in this case.

Bearer-specific parameters sent along S4 are not forwarded to the PDN-GW or PCRF in many cases. Bearers terminate in the Serving-GW when PMIP-based S5/S8 has been deployed. Though EPS bearer identifier information is not relevant to the PCRF or PCEF in these cases, some bearer-oriented parameters must be forwarded to the PCRF for authorization and so that the PCRF will generate the correct corresponding PCC rules to send to the PDN-GW for enforcement.

5.10.2 GPRS procedures that update the PDN-GW p. 109

Several procedures employing GTP-based S5/S8 includes a "Modify Bearer" exchange, initiated by the Serving-GW, responded to by the PDN-GW. The equivalent interaction for a PMIP-based S5/S8 is shown in Figure 5.7.2-1.

The following procedures in TS 23.060 will make use of the procedure shown in this specification, clause 5.7.2 to signal RAT change as determined by the SGSN. Aside from the new RAT type, no additional parameter must be sent as an event report by the Serving-GW to the PDN-GW by means of the PCRF (as described in TS 23.203).

The procedure in clause 5.7.2 refers directly to procedures in TS 23.401, while the procedures described here in support of S4 refer to clauses in TS 23.060. The following clarifications to the procedure in clause 5.7.2 must be considered to interpret clause 5.7.2:

6.9.2.2.1a: Serving RNS Relocation Procedure, Combined Hard Handover and SRNS Relocation Procedure, and Combined Cell/URA Update and SRNS Relocation Procedure using S4

Steps A.1 and A.2 of the procedure in clause 5.7.2 occur instead of the steps shown in the box (B1) in clause 6.9.2.2.1a of TS 23.060, Figure 39b. The APN AMBR, RAT Type and other parameters defined in clause 6.9.2.2.1a step B and C are transmitted according to clause 5.7.2, as additional IEs transmitted between the S-GW, PCRF and P-GW. IEs are returned to the S-GW (insofar as step A.2 implies a Gateway Control and QoS Rules Provision procedure as described in TS 23.203).

This procedure applies also to 6.9.2.2.3 Combined Cell / URA Updates and SRNS Relocation Procedure.

6.9.2.2.5A Enhanced Serving RNS Relocation Procedure Using S4

Steps A.1 and A.2 of the procedure in clause 5.7.2 occur instead of the steps shown in the box (step B and C) in Figure 44b1 and steps B and C in Figure 44b2 in clause 6.9.2.2.5A of TS 23.060.

6.12.1A: UE Initiated Service Request Procedure Using S4

Steps A.1 and A.2 of the procedure in clause 5.7.2 occur instead of the steps shown in the box (B1) in clause 6.12.1A of TS 23.060, Figure 50A.

6.13.1.1.2: Iu mode to A/Gb mode Intra-SGSN Change using S4

Steps A.1 and A.2 of the procedure in clause 5.7.2 occur instead of the steps shown in the box (A1) in clause 6.13.1.1.2 of TS 23.060, Figure 52-2.

6.13.1.2.2: A/Gb mode to Iu mode Intra-SGSN Change using S4

Steps A.1 and A.2 of the procedure in clause 5.7.2 occur instead of the steps shown in the box (A1) in clause 6.13.1.2.2 of TS 23.060, Figure 53-2.

6.13.2.1.2: Iu mode to A/Gb mode Inter-SGSN Change using S4

Steps A.1 and A.2 of the procedure in clause 5.7.2 occur instead of the steps shown in the box (B1) in clause 6.13.2.1.2 of TS 23.060, Figure 54-3.

6.13.2.2.2: A/Gb mode to Iu mode Inter-SGSN Change using S4

Steps A.1 and A.2 of the procedure in clause 5.7.2 occur instead of the steps shown in the box (B1) in clause 6.13.2.2.2 of TS 23.060, Figure 55-3.

8.1.4A: Paging response for GPRS Downlink Transfer with no established User plane on S4

Steps A.1 and A.2 of the procedure in clause 5.7.2 occur instead of the steps shown in the box (C) in clause 8.1.4 of TS 23.060, Figure 56b.

5.10.3 UE allocated resources p. 110

The UE (or the SGSN on behalf of the UE) requests resources in several procedures in TS 23.060. The procedure described in clause 5.5 of this specification provides the PMIP-based S5/S8 describes UE-initiated resource request, modification and release. This procedure, with the additional clarification given below, will support the following procedures shown in TS 23.060.

In each case, the SGSN provides a Bearer identifier (the LBI) over S4. The bearer binding performed by the Serving-GW is in this case constrained to either reject or modify (increase or decrease the resource assigned to) the indicated bearer. The Serving-GW shall not provide a different bearer as a result of the PDP Context Activation or Modification procedures.

9.2.2.1A: A PDP Context Activation using S4

Steps A.1 to A.4 of the procedure in clause 5.6.1 occur instead of the steps shown in the box (A1) in clause 9.2.2.1A of TS 23.060, Figure 64a. Step A.1 and A.3a include the RAT Type, Default Bearer QoS and APN-AMBR IEs, and other IEs defined in clause 9.2.2.1A of TS 23.060, step B.

Step A.3b in clause 5.6.1 of this specification (insofar as it implies a Gateway Control and QoS Rules Provision procedure as described in TS 23.203) returns the IEs to the S-GW, including EPS Bearer QoS and other IEs defined in clause 9.2.2.1A of TS 23.060, step C.

If the UE requests a PDP context (effectively an additional PDN connection) for an APN for which the UE already has an active PDN connection, the SGSN shall reject the PDN connectivity request unless it is configured that the Serving-GW supports multiple PDN connections to the same APN.

9.2.2.1.1A Figure 66a: Secondary PDP Context Activation Procedure, PDP Creation Part using S4

Step A.1 of the procedure in clause 5.5 corresponds to the steps described in the box (A1) and (A2) in clause 9.2.2.1.1A of TS 23.060, Figure 66a.

In step A.1, additional IEs are required by the PCRF and PDN-GW in order properly assign QoS rules and prepare the dedicated bearer. The TFT and EPS Bearer QoS (excluding ARP) IEs are received from the SGSN by the S-GW over S4. These parameters are then forward to the PCRF as described in clause 5.5.

9.2.3.3A: MS-Initiated EPS Bearer Modification Procedure using S4, Request Part

The procedure step in clause 9.2.3.3A of TS 23.060, Figure 72c, step B corresponds with step A.1 of Figure 5.5-1 (of this specification).

The Serving-GW provides the same information to the PCRF as the PDN-GW provides according to step B in clause 9.2.3.3A of TS 23.060; this clause defines the IEs included in step A.1 of clause 5.5.

9.2.3.3B: MS-Initiated EPS Bearer Modification Procedure using S4, Execution Part

The procedure step in clause 9.2.3.3B of TS 23.060, Figure 72d, step A corresponds with step A.1 of Figure 5.5-1 (of this specification). The following information elements may be sent, depending on the scenario, see clause 9.2.3.3B of TS 23.060:

9.2.3.3C: MS-Initiated EPS Bearer Modification Procedure using S4, Response Part

The procedure step in clause 9.2.3.3A of TS 23.060, Figure 72c, step C corresponds with step Figure 5.5-1 (of this specification), steps B.1 and B.2, with one difference - before step B.1, step A of the procedure in clause 9.2.3.3C of TS 23.060 occurs. The Serving-GW indicates to the PCRF the result of the resource allocation. This may result in additional interaction with the PDN-GW (see TS 23.203).

5.10.4 Network allocated resources p. 111

Network entities may request resources by means of off-path signalling to support PMIP-based S5/S8. This is defined in clause 5.4.1. All IEs present in messages sent in the replaced 'boxes' in procedures in the following list are sent instead using messages described in this specification. The following procedures in TS 23.060 employ this procedure:

9.2.2.3A: Network Requested PDP Context Activation Procedure using S4

Step A.1 of the procedure in clause 5.4.1 occurs instead of the steps shown in the box (A1) in clause 9.2.2.3A of TS 23.060, Figure 69c. Steps B.1 and B.2 of the procedure in clause 5.4.1 correspond to the box (B1).

9.2.3.1A: SGSN-Initiated EPS Bearer Modification Procedure, Request Part

Step A.1 of clause 5.5 occurs instead of the steps inside box (A1) in clause 9.2.3.1A of TS 23.060, Figure 70c. Figure 5.5-1 refers to TS 23.401 yet the procedure applies to the SGSN-Initiated EPS Bearer Modification Procedure using S4 as well.

9.2.3.1B: SGSN-Initiated EPS Bearer Modification Procedure, Response Part

Steps B.1 and B.2 of clause 5.5 occurs instead of the steps inside box (B1) in clause 9.2.3.1B of TS 23.060, Figure 70d. Figure 5.5-1 refers to TS 23.401 yet the procedure applies to the SGSN-Initiated EPS Bearer Modification Procedure using S4 as well.

9.2.3.2A: PDN-GW-Initiated EPS Bearer Modification Procedure

Step A.1 of the procedure in clause 5.4.1 occurs instead of the steps shown in the box (A1) in clause 9.2.3.2A of TS 23.060, Figure 71c.

Steps B.1 and B.2 of the procedure in clause 5.4.1 correspond to the box (A2). Step B.1 indicates whether the resource allocation was successful. This may result in additional interaction with the PDN-GW (refer to TS 23.203).

5.10.5 UE released resources p. 111

The UE may release dedicated resources by means of off-path signalling to support PMIP-based S5/S8 deployments, as shown in clause 5.5.

9.2.4.1A.1: MS-and SGSN Initiated PDN connection Deactivation Procedure using S4

Steps A.1 to A.4 of the procedure in clause 5.6.2.1 "UE, MME or S-GW initiated PDN Disconnection" occur instead of steps shown in the box (A1) in clause 9.2.4.1A.1 of TS 23.060, Figure 74a.

9.2.4.1A.2: MS- and SGSN Initiated Bearer Deactivation using S4

Steps A.1, B.1 and B.2 of the procedure in clause 5.5 "UE-initiated Resource Request and Release" procedure occur instead of the steps shown in the box (A1) in clause 9.2.4.1A.2 of TS 23.060, Figure 74b.

5.10.6 PDN-GW released resources p. 111

The PDN-GW may release resources by means of off-path signalling to support PMIP-based S5/S8 deployments as shown in clause 5.4.1. The following procedures in TS 23.060 employ this procedure:

9.2.4.3A: PDN-GW-Initiated PDP Context Deactivation Procedure using S4

Step A.1 in clause 5.4.1 corresponds to the steps shown in box (A1) of clause 9.2.4.3A of TS 23.060, Figure 77a.

9.2.4.3B: PDN-GW-Initiated PDP Context Deactivation Procedure using S4

Steps B.1 and B.2 in clause 5.4.1 correspond to the steps in the box (B1) in clause 9.2.4.3B of TS 23.060, Figure 77b.

5.10.7 Attach p. 112

The GPRS Attach Procedure is supported by the following PMIP-based S5/S8 procedures:

Clause 5.3 is employed instead of box (A) in clause 6.5.3A of TS 23.060, Figure 22A. clause 5.3 is also used instead of box (B) in clause 6.5.3B of TS 23.060, Figure 22B.

5.10.8 Detach interaction using S4 p. 112

The MS-, SGSN- and HLR-initiated GPRS detach procedures are supported by the following equivalent PMIP-based S5/S8 procedure:

Clause 5.3 is employed instead of the gray box (A1) in clause 6.6.3 of TS 23.060, Figure 25A.

5.10.9 Interaction with CGI/SAI reporting using S4 p. 112

In the Interaction with CGI / SAI reporting using S4 Procedure as depicted in Figure 15.1.3-3 of TS 23.060, if CGI or SAI changes are considered relevant to charging, a change notification is sent to the PDN-GW. There is no response to this report. This corresponds to a Location change (CGI/SAI) event report provided to the PCRF by means of a Gateway Control and QoS Rules Request, as defined in TS 23.203. This procedure ensures that the event is reported to the PDN-GW as well.

5.10.10 RAU Procedure Support p. 112

RAU procedures in TS 23.060 send messages from the S4 SGSN to the S-GW and thence to P-GW using GTPv2. For PMIP-based S5/S8, these exchanges occur via PCC.

TS 23.203, Figure 7.7.3-1 "Gateway Control and QoS Rules Request", depicts the procedure. The BBERF(S-GW) sends a Gateway Control and QoS Rules Request message to the PCRF including the APN-AMBR. The PCRF sends a PCC Rules Provision message to the PDN-GW including the APN-AMBR. The PDN-GW responds with an Acknowledge Policy and Charging Rules Provisioning message with the APN-AMBR to the PCRF. The PCRF responds to the BBERF(S-GW) with a Gateway Control and QoS Rules Reply message with the APN-AMBR parameter. The response from the PCRF to the BBERF to the initial Gateway Control and QoS Rules Request message must wait (synchronously) for the completion of the PCC Rules Provision exchange between the PCRF and PCEF.

6.9.1.2.2a: Inter SGSN Routeing Area Update and Combined Inter SGSN RA / LA Update using S4

Instead of the steps shown in the box (B1) in clause 6.9.1.2.2a of TS 23.060, Figure 33b, the procedure described above is employed.

6.9.2.1a: Routeing Area Update Procedure using S4

Instead of the steps shown in the box (B1) in clause 6.9.2.1a of TS 23.060, Figure 36b, the procedure described above is employed.

5.11 PDN-GW initiated IPv4 address Delete Procedure p. 112

This procedure is initiated by the PDN-GW when the UE releases the IPv4 address using DHCPv4 procedure or the lease for the IP address has expired. The procedure is used to delete the IPv4 address from the PDN connection context.

Copy of original 3GPP image for 3GPP TS 23.402, Fig. 5.11-1: PDN-GW initiated IPv4 address Delete Procedure

Figure 5.11-1: PDN-GW initiated IPv4 address Delete Procedure
(⇒ copy of original 3GPP image)

This procedure applies to the Non-Roaming (Figure 4.2.1-1), Roaming (Figure 4.2.1-2) and Local Breakout (Figure 4.2.3-4) cases. For the Roaming and Local Breakout cases, the vPCRF forwards messages between the Serving-GW and the hPCRF. In the Local Breakout case, the vPCRF forwards messages between the PDN-GW and the hPCRF.

The optional interaction steps between the gateways and the PCRF in the procedures in Figure 5.11-1 only occur if dynamic policy provisioning is deployed. Otherwise policy may be statically configured with the gateway.

Step 1.

The PCEF initiates the Gateway Control Session Modification Procedure with the PCRF as specified in TS 23.203. The PDN-GW provides the information to enable the PCRF to uniquely identify the IP-CAN session.

Step 2.

In case QoS rules have to be modified, e.g. change of SDF filters, the PCRF initiates a GW Control and QoS rules provision procedure as described in TS 23.203 to inform the S-GW of the updated QoS rules.

Step 3.

The S-GW initiates the "PDN-GW initiated bearer modification without QoS update" as described in clause 5.4.3 of TS 23.401, between steps (A) and (B).

Step 4.

The S-GW informs the PCRF of the success of the QoS rules enforcement, thus ending the GW Control and QoS rules provision procedure described in TS 23.203.

Step 5.

The PDN-GW sends a Binding Revocation Indication (PDN address) message to the Serving-GW to revoke the IPv4 address.

Step 6.

The Serving-GW returns a Binding Revocation Acknowledgement message to the PDN-GW.

5.12 Location Change Reporting Procedure for PMIP-based S5/S8 |R9| p. 114

This clause contains the procedure steps that vary between the GTP and PMIP variant of S5 and S8 for the Location Change Reporting procedure provided in clause 5.9.2 of TS 23.401. If the Serving-GW has received the User Location Information IE and/or user CSG information from MME, this event is reported to the PCRF by means of a Gateway Control and QoS Rules Request, as defined in TS 23.203. This procedure ensures that the event is reported to the PDN-GW as well.

Copy of original 3GPP image for 3GPP TS 23.402, Fig. 5.12-1: Notification of the ECGI/TAI information changes

Figure 5.12-1: Notification of the ECGI/TAI information changes
(⇒ copy of original 3GPP image)

This procedure concerns both the non-roaming (S5) as in Figure 4.2.1-1 and roaming case (S8) as in Figure 4.2.1-2. In the roaming case, the vPCRF in the VPLMN forwards messages between the Serving-GW and the hPCRF in the HPLMN. In the case of Local Breakout as in Figure 4.2.3-4, the vPCRF forwards messages sent between the PDN-GW and the hPCRF as well. In the non-roaming case, the vPCRF is not involved at all.

The optional interaction steps between the gateways and the PCRF in the procedures in Figure 5.12-1 only occur if dynamic policy provisioning is deployed and the MME has been requested to report the User Location Information IE and/or user CSG information changes to the PGW for the UE.

A.1)

The Serving-GW informs the PCRF about the change User Location Information IE and/or user CSG information by initiating the Gateway Control and QoS Policy Rules Request Procedure as specified in TS 23.203.

A.2)

The hPCRF notifies the PDN-GW of the UE Location Information IE and/or user CSG information by initiating the PCC Rules Provision Procedure as specified in TS 23.203.

Step A.2 may be initiated before step A.1 completes.

5.13 Support for Machine Type Communications (MTC) |R10| p. 114

5.13.1 General p. 114

Support for Machine Type Communications (MTC) is described in TS 23.401. The common procedures and functionalities are only captured in TS 23.401.

5.13.2 PDN-GW control of overload p. 115

The PDN-GW may provide mechanisms for avoiding and handling overload situations. These include the rejection of PDN connection requests from UEs.

When PMIP is used for S5/S8 interface, PDN-GW may reject the PDN connection request (i.e. Proxy Binding Update) with indication that the APN is congested. In addition the PDN-GW may indicate a "PDN-GW back-off time" for a specific APN to the MME in the reject message.

Other PDN-GW functionalities and the behaviour of Serving-GW/MME/SGSN upon receiving the reject messages are described in TS 23.401.

5.13.3 Usage of low access priority indicator p. 115

For PDN connection establishment requests, the SGSN/MME includes the low access priority indicator in the request message to the Serving-GW/PDN Gateway. The Serving-GW shall forward the indicator to PDN-GW in Proxy Binding Update message.

Other functions related to indicators are described in TS 23.401.