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.161  Word version:  17.0.0

Top   Top   Up   Prev   Next
1…   5…   6…   6.2…   6.2.4   6.3…   6.3.2.2…   6.3.3…   6.3.3.2…   6.4…   6.4.2.2…   6.5…   6.5.2…   6.5.3…   6.6…   6.6.1.3…   6.6.2…   6.7…   6.7.2…   6.8… 
6.3 IP flow mobility within a PDN connection  6.3.1 General  6.3.2 Network-initiated IP flow mobility  6.3.2.1 Routing Rules signalled via 3GPP access 
...

 

6.3  IP flow mobility within a PDN connection  p. 28

6.3.1  General  p. 28

6.3.2  Network-initiated IP flow mobility  p. 28

6.3.2.1  Routing Rules signalled via 3GPP access  p. 28

In the case of network-initiated NBIFOM mode, the following procedures are applicable for S2a-SCM, S2a-MCM or S2b when target network is 3GPP access.
In the following signalling flow, the PDN GW moves one or more IP flow(s) by providing a Routing Rule with access type 3GPP. The routing rule is sent via E-UTRAN in this case.
Copy of original 3GPP image for 3GPP TS 23.161, Fig. 6.3.2.1-1: Network-initiated IP flow mobility within a PDN connection via E-UTRAN using GTP
Figure 6.3.2.1-1: Network-initiated IP flow mobility within a PDN connection via E-UTRAN using GTP
(⇒ copy of original 3GPP image)
Up
Step 1.
The UE is connected simultaneously to 3GPP and Trusted/Untrusted WLAN access.
Step 2.
When dynamic PCC is applied for the PDN connection, the H-PCRF determines based on policy information and current UE state that session modification should be initiated to move specific flows. The PCRF provides PCC Rules with access type information to the PDN GW during an IP-CAN session modification procedure. The PDN GW determines that new Routing Rules / Modified Routing Rules need to be sent to the UE based on the received PCC Rules.
When dynamic PCC is not applied, the PDN GW may determine based on local policies that new Routing Rules / Modified Routing Rules need to be sent to the UE.
Step 3.
The PDN GW sends the Created /Modified Routing Rules within Create/Update/Delete Bearer Request to the Serving GW. If bearer resources need to be established or modified due to the PCC rules received in step 2, the bearer operations may be performed in this step
Step 4.
The bearer modification,dedicated bearer activation or dedicated bearer deactivation procedure between the MME and the UE is performed as described in TS 23.401. The UE may accept or reject the Routing Rules. When the UE rejects the Routing Rules, the UE provides a cause value indicating why the request was rejected. This cause value may be used by the network to determine when/if this IP flow mobility operation can be requested again. The UE applies the accepted routing rules and acknowledges the applied rules in the message sent to the MME.
Step 5.
The MME sends Create/Update/Delete Bearer Response indicating the accepted Routing Rules to the PDN GW via the Serving GW.
Step 6.
The PDN GW indicates to the PCRF whether the PCC Rule could be enforced or not. This corresponds to the completion of the PCEF-initiated IP CAN session modification procedure as defined in TS 23.203, proceeding after the completion of IP CAN bearer signalling.
Step 7.
Appropriate S2a/S2b resource release/modification procedures are executed for the resources associated with the flows that were removed from the Trusted or Untrusted WLAN access as described in TS 23.402. For S2a-SCM, dedicated bearer over S2a is not supported when IP flow mobility is used.
Copy of original 3GPP image for 3GPP TS 23.161, Fig. 6.3.2.1-2: Network-initiated IP flow mobility within a PDN connection via GERAN/UTRAN using GTP
Figure 6.3.2.1-2: Network-initiated IP flow mobility within a PDN connection via GERAN/UTRAN using GTP
(⇒ copy of original 3GPP image)
Up
Step 1.
The UE is connected simultaneously to GERAN/UTRAN and Trusted/Untrusted WLAN access.
Step 2.
When dynamic PCC is applied for the PDN connection, the H-PCRF determines based on policy information and current UE state that session modification should be initiated to move specific flows. The PCRF provides PCC Rules with access type information to the PDN GW during an IP-CAN session modification procedure. The PDN GW determines that new Routing Rules / Modified Routing Rules need to be sent to the UE based on the received PCC Rules. When dynamic PCC is not applied, the PDN GW may determine based on local policies that new Routing Rules / Modified Routing Rules need to be sent to the UE.
Step 3.
The PDN GW sends the Created /Modified Routing Rules within Create/Update/Delete Bearer Request to the Serving GW/SGSN. If bearer resources need to be established or modified due to the PCC rules received in step 2, the bearer operations may be performed in this step.
Step 4.
The dedicated bearer activation or bearer modification or dedicated bearer deactivation procedure between the MME and the UE is performed as described in TS 23.060. The UE may accept or reject the Routing Rules. When the UE rejects the Routing Rules, the UE provides a cause value indicating why the request was rejected. This cause value may be used by the network to determine when/if this IP flow mobility operation can be requested again. The UE applies the accepted routing rules and acknowledges the applied rules in the message sent to the SGSN.
Step 5.
The SGSN sends Create/Update/Delete Bearer Response indicating the accepted Routing Rules to the PDN GW via the Serving GW.
Step 6.
The PDN GW indicates to the PCRF whether the PCC Rule could be enforced or not. This corresponds to the completion of the PCEF-initiated IP CAN session modification procedure as defined in TS 23.203, proceeding after the completion of IP CAN bearer signalling.
Step 7.
Appropriate S2a/S2b resource release/modification procedures are executed for the resources associated with the flows that were removed from the Trusted or Untrusted WLAN access as described in TS 23.402. For S2a-SCM, dedicated bearer over S2a is not supported when IP flow mobility is used.
Up

Up   Top   ToC