Content for TS 23.214 Word version: 18.0.0

1… 4.3… 5… 5.6… 5.10… 6… 6.3… 6.3.1.2 6.3.1.3… 6.3.1.6… 6.3.2… 6.3.3… 6.3.3.4… 6.3.3.7… 6.3.4… 6.3.4.2… 6.3.4.2.2 6.3.4.3 6.4… 7…

6.3.1.3 Procedures with eNB F-TEIDu update 6.3.1.4 Procedures with release of eNB F-TEIDu 6.3.1.5 Procedures when downlink data is buffered in the UP function
...

6.3.1.3 Procedures with eNB F-TEIDu update p. 45

In this clause, interactions between the CP and UP function during the following procedures are considered:

UE triggered Service Request (clause 5.3.4.1 of TS 23.401).
Connection Resume procedure (clause 5.3.5A of TS 23.401).
E-UTRAN initiated E-RAB modification procedure (clause 5.4.7 of TS 23.401).
X2-based handover without Serving GW relocation (clause 5.5.1.1.2 of TS 23.401).
S1-based handover without Serving GW change (clause 5.5.1.2.2 of TS 23.401).

During the above procedures following is the nature of interactions between the CP and UP function:

The SGW-C modifies the Sx session at SGW-U to update the F-TEIDu(s) of the eNB.
Based on the interaction with the PCRF, the PGW-C may modify the PGW-U to update other Sx parameters.

Copy of original 3GPP image for 3GPP TS 23.214, Fig. 6.3.1.3-1: Interaction between CP and UP function during procedures with eNB F-TEIDu update

Figure 6.3.1.3-1: Interaction between CP and UP function during procedures with eNB F-TEIDu update
(⇒ copy of original 3GPP image)

Step 1.

Procedure as listed in this step is initiated as specified in the relevant clauses of this specification. The relevant steps of the procedure as specified in the Figure above are executed.

Step 2.

The SGW-C sends an Sx Session Modification Request to the SGW-U. It shall include the new F-TEIDu of the eNB. Additionally, for the following procedures extra steps may apply:

UE triggered Service Request: If the buffering of the data packets in the idle mode is performed in the SGW-C and if those buffered packets are still valid (e.g. data packets for which the buffering duration hasn't expired yet), then SGW-C shall also provide those data packets to the SGW-U (as specified in clause 5.12) so that it can be sent to the eNB.

Step 3.

The SGW-U sends an Sx Session Modification Response to the SGW-C confirming the successful modification of the Sx session.

Step 4.

The relevant steps of the procedure as specified in the Figure above are executed.

Step 5.

Based on the interaction with the PCRF, the PGW-C may update other Sx parameters for the PDN connection. Correspondingly, the PGW-C sends an Sx Session Modification Request to the PGW-U.

Step 6.

The PGW-U sends an Sx Session Modification Response to the PGW-C confirming the success of the Sx session modification.

Step 7.

The relevant steps of the procedure as specified in the Figure above are executed.

6.3.1.4 Procedures with release of eNB F-TEIDu p. 46

This clause defines interactions between the CP and UP function during the following procedures:

Connection Suspend procedure (clause 5.3.4A of TS 23.401).
S1 release procedure (clause 5.3.5 of TS 23.401).

During the above procedures following is the nature of interactions between the CP and UP function:

The SGW-C modifies the SGW-U to release the eNB F-TEIDu. Additionally, the SGW-C configures the SGW-U so that the downlink data packets can be buffered either in the SGW-C or in the SGW-U.

Copy of original 3GPP image for 3GPP TS 23.214, Fig. 6.3.1.4-1: Interaction between CP and UP function during procedures with release of eNB F-TEIDu

Figure 6.3.1.4-1: Interaction between CP and UP function during procedures with release of eNB F-TEIDu
(⇒ copy of original 3GPP image)

Step 1.

Procedure as listed in this step is initiated as specified in the relevant clauses of this specification. The relevant steps of the procedure as specified in the Figure above are executed.

Step 2.

The SGW-C sends an Sx Session Modification Request to the SGW-U. It shall indicate the SGW-U to release the eNB F-TEIDu. Additionally, the SGW-C decides if the buffering of the downlink data packets shall be done in CP or the UP function, as specified in clause 5.9) and correspondingly informs the SGW-U for as follows:

If the downlink data packets are to be buffered in the SGW-C, the SGW-C shall configure the SGW-U to forward the downlink data packets for all the bearers of the UE to the SGW-C, as specified in clause 5.6.
If the downlink data packets are to be buffered in the SGW-U, the SGW-C shall indicate the same to SGW-U. Additionally, the following applies:
- if the Paging Policy Differentiation feature (as specified in clause 4.9 of TS 23.401) is supported by the SGW-C and SGW-U and based on operator's policy if it is required to be activated for this UE, the SGW-C shall include an indication to provide the DSCP in TOS (IPv4) / TC (IPv6) value from the IP header of the first downlink data packet of each bearer.
- if the PDN GW Pause Charging procedure (as specified in clause 5.3.6A of TS 23.401) is supported by the SGW-C and SGW-U and based on operator's policy if it is required to be activated for this UE, the SGW-C may provide the number/fraction of packets/bytes drop threshold value. When this threshold is reached, the SGW-U is required to provide an indication to the SGW-C.

Step 3.

The SGW-U sends an Sx Session Modification Response to the SGW-C confirming the successful modification of the Sx session.

Step 4.

The relevant steps of the procedure as specified in the Figure above are executed.

6.3.1.5 Procedures when downlink data is buffered in the UP function p. 47

This clause defines interactions between the CP and UP function when then UE is in idle mode and buffering of the downlink data is performed in the UP function, during the following procedures:

Network Triggered Service Request (clause 5.3.4.3 of TS 23.401).
PDN GW Pause of Charging procedure (clause 5.3.6A of TS 23.401).

During the above procedures following is the nature of interactions between the CP and UP function:

The SGW-U notifies the SGW-C that the first downlink data packet was received for a bearer.

NOTE:
A bearer is identified in the SGW-U as a combination of PDR(s) and FAR(s).
The SGW-U notifies the SGW-C that the drop threshold was reached.

Copy of original 3GPP image for 3GPP TS 23.214, Fig. 6.3.1.5-1: Interaction between CP and UP when downlink data is buffered in the UP function

Figure 6.3.1.5-1: Interaction between CP and UP when downlink data is buffered in the UP function
(⇒ copy of original 3GPP image)

Step 1.

Procedure as listed in this step is initiated as specified in the relevant clauses of this specification. The relevant steps of the procedure as specified in the Figure above are executed.

Step 2.

When the downlink data is received, the SGW-U starts buffering it.

On arrival of the first downlink data packet for a bearer, the SGW-U shall send an Sx report message (first packet indication) to the SGW-C. If the Paging Policy Differentiation feature (as specified in clause 4.9 of TS 23.401) is supported by the SGW-U and if it is activated by the SGW-C for this Sx session, the SGW-U shall also include the DSCP in TOS (IPv4) / TC (IPv6) value from the IP header of the downlink data packet.

If the SGW-C has provided the number/fraction of packets/bytes drop threshold value during the procedure with release of eNB F-TEIDu (clause 6.3.1.4), the SGW-U shall monitor that threshold. Once the threshold is reached the SGW-U shall send an Sx report message (drop threshold reached) to the SGW-C.

Step 3.

The relevant steps of the procedure as specified in the Figure above are executed.

Step 4.

The SGW-C sends an Sx report Ack message to the SGW-U. Additionally, for the following procedures the following applies:

Network Triggered Service Request: If DL Buffering Duration time and DL Buffering Suggested Packet Counts were received from the MME/SGSN (refer to step 2 in clause 5.3.4.3 of TS 23.401) by the SGW-C then SGW-C shall include the same in the Sx report Ack message.

Step 5.

The relevant steps of the procedure as specified in the Figure above are executed.