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.214  Word version:  18.0.0

Top   Top   Up   Prev   Next
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 Updates to procedures in other specifications  6.3.1 Updates to procedures specified in TS 23.401 [2]  6.3.1.1 Procedures with PDN connection establishment 
...

 

6.3  Updates to procedures in other specifications  p. 38

6.3.1  Updates to procedures specified in TS 23.401 [2]  p. 38

6.3.1.1  Procedures with PDN connection establishment |R16|  p. 38

This clause defines interactions between the CP and UP function during the following procedures:
During the above procedures following is the nature of interactions between the CP and UP function:
  • The new SGW-C selects a new SGW-U and creates an Sx session.
  • The new PGW-C selects a new PGW-U and creates an Sx session.
  • The old SGW-C releases the existing Sx session from the old SGW-U.
  • The old PGW-C releases the existing Sx session from the old PGW-U.
  • The SGW-C modifies the SGW-U to update with the F-TEIDu of the eNodeB and the PGW-U.
Copy of original 3GPP image for 3GPP TS 23.214, Fig. 6.3.1.1-1: Interaction between CP and UP function during PDN connection establishment
Figure 6.3.1.1-1: Interaction between CP and UP function during PDN connection establishment
(⇒ copy of original 3GPP image)
Up
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.
For all the steps below upon receiving a Sx Session Termination Request, the SGW-U or PGW-U releseases all associated resources including the F-TEIDu allocated for the Sx session.
Step 2a.
The SGW-C may send an Sx Session Termination Request to the SGW-U to release the Sx session.
Step 2b.
The SGW-U sends an Sx Session Termination Response to the SGW-C confirming the release of the Sx session.
Step 3a.
The PGW-C may send an Sx Session Termination Request to the PGW-U to release the Sx session.
Step 3b.
The PGW-U sends an Sx Session Termination Response to the PGW-C confirming the release of the Sx session.
Step 4.
The relevant steps of the procedure as specified in the Figure above are executed.
Step 5a.
The SGW-C may send an Sx Session Termination Request to the SGW-U to release the Sx session.
Step 5b.
The SGW-U sends an Sx Session Termination Response to the SGW-C confirming the release of the Sx session.
Step 6a.
The PGW-C may send an Sx Session Termination Request to the PGW-U to release the Sx session.
Step 6b.
The PGW-U sends an Sx Session Termination Response to the PGW-C confirming the release of the Sx session.
Step 7.
The relevant steps of the procedure as specified in the Figure above are executed.
Step 8a.
The SGW-C shall select new SGW-U as specified in clause 5.12. The SGW-C sends an Sx Session Establishment Request to the selected SGW-U for creating an Sx session for the UE.
Step 8b.
The SGW-U allocates F-TEIDu for the default bearer. The SGW-U sends an Sx Session Establishment Response to the SGW-C confirming the successful creation of the Sx session. It includes the F-TEIDu it has allocated.
Step 9.
The relevant steps of the procedure as specified in the Figure above are executed.
Step 10a.
The PGW-C shall select new PGW-U as specified in clause 5.12. The PGW-C sends an Sx Session Establishment Request to the selected PGW-U for creating an Sx session for the UE.
Step 10b.
The PGW-U allocates F-TEIDu for the bearer. The PGW-U sends an Sx Session Establishment Response to the PGW-C confirming the successful creation of the Sx session. It includes the F-TEIDu it has allocated.
Step 11.
The relevant steps of the procedure as specified in the Figure above are executed.
Step 12a.
The SGW-C sends Session Modification Request to the SGW-U. The SGW-C shall include the F-TEIDu of the default bearer received from the PGW.
Step 12b.
The SGW-U sends an Sx Session Modification Response to the SGW-C confirming the success of the Sx session modification.
Step 13.
The relevant steps of the procedure as specified in the Figure above are executed.
Step 14a.
The SGW-C sends an Sx Session Modification Request to the SGW-U. The SGW-C shall include the F-TEIDu of the default bearer received from the eNodeB.
Step 14b.
The SGW-U sends an Sx Session Modification Response to the SGW-C confirming the success of the Sx session modification.
Step 15.
The relevant steps of the procedure as specified in the Figure above are executed.
Step 16a.
If the Handover Indication is included in step 15, the PGW-C updates the old PGW-U session corresponding to the non-3GPP access by sending "Sx session modification request" message to the PGW-U (session ID) and instructs the PGW-U to start routing the downlink packets to the SGW/SGW-U.
Step 16b.
The PGW-U sends "Sx session modification response" message to the PGW-C.
Step 17.
The relevant steps of the procedure as specified in the Figure above are executed.
Up

Up   Top   ToC