9.2 Procedures for Fixed Broadband Access network using HeNB – PMIP
23.1393GPP3GPP system - fixed broadband access network interworkingRelease 17Stage 2TS
9.2.1 Initial E-UTRAN Attach with PMIP-based S5/S8
This clause is related to the case when the UE performs initial attachment to the E-UTRAN network via a HeNB. The HeNB is already registered in the network.
The HeNB sends the HeNB local IP address and UDP port if NAT/NAPT is detected to the MME in UE associated S1 signalling (refer to the definition of Initial UE Message in TS 36.413 [29]).
Figure 9.2.1-1 : Initial E-UTRAN attach with PMIP-based S5/S8
This procedure is the same as described in TS 23 402 [3], clause 5.2 with the modification of the existing steps and addition of the new step described below.
1. This step is the same as for attach procedures as in TS 23 402[3], figure 5.2-1, with the exception as defined for the corresponding steps for GTP case, clause 9.1.1.
C.1 The S-GW initiates the Gateway control session establishment procedure with the PCRF, and the following additional information: the HeNB local IP address and the UDP port if NAT/NAPT is detected needs to be forwarded to the PCRF during this procedure.
C.3 The PCRF sends the Gateway Control Session establishment/QoS Rules provisioning message to the BPCF according to TS 23.203 [4]. The message includes the IMSI, HeNB local IP address and UDP port if NAT/NAPT is detected.
Once this procedure completes the PCRF is aware the fact that the UE is connected to the network via the a 3GPP Femto and checks first whether sufficient resources are available in the BBF access before it provisions QoS and PCC rules at the BBER and PCEF, respectively.
9.2.2 Detach for PMIP-based S5/S8
The procedure in this clause provides the PMIPv6-based S5/S8 variants to all E-UTRAN Detach Procedures, including UE, MME or HSS initiated detach procedure (TS 23.401 [2] clause 5.3.8).
Figure 9.2.2-1: E-UTRAN Detach Procedure for PMIP-based S5/S8
This procedure is the same as described in TS 23 402 [3], clause 5.3 with the addition of the new step described below.
A.4. The PCRF initiates the Gateway Control session termination/ QoS Rules Provisioning procedure with BPCF according to TS 23.203 [4].
NOTE: The interaction between the BPCF and the BNG is out of scope.
9.2.3 Dedicated Bearer Procedures for E-UTRAN Access with PMIP-based S5/S8
The dedicated bearer procedure for a PMIP based S5/S8 is based on TS 23 402 [3], clause 5.4.1 It applies to dedicated bearer activation/modification/deactivation procedures.
Figure 9.2.3-1: Dedicated Resource Allocation/Deallocation Procedure, UE in Active Mode
This procedure is the same as described in TS 23 402 [3], clause 5.4.1 with the addition of the new step described below:
A.0 The PCRF initiates the GW Control and QoS Provisioning procedure with the BPCF to request or de-allocate resources in the BBF access network. The message to request resources includes the QoS Information (SDF, QCI, ARP, GBR, MBR) according to TS 23.203 [4].
9.2.4 HSS-Initiated Subscribed QoS Modification
The HSS triggers a change to the default beater QoS attributes that, depending on the decision of the PCRF, may impact the resources allocated in the BBF access.
The HSS Initiated Subscribed QoS Modification for a PMIP-based S5/S8 is depicted in TS 23 402 [3], Figure 5.4.3.2-1.
Figure 9.2.4-1 HSS-initiated Subscribed QoS Modification
This procedure is the same as described in TS 23 402 [3], clause 5.4.3.2 with the addition of the new step described below:
A.2. The PCRF initiates the GW Control and QoS Provisioning procedure with the BPCF to either request allocation/de-allocation of BBF resources. The message includes the QoS Information (QCI, ARP, GBR, MBR) according to TS 23.203 [4].
9.2.5 MME-initiated Dedicated Bearer Deactivation
This clause contains the procedure steps that vary between the GTP and PMIP variant of S5 and S8 for the procedure defined in TS 23.401 [2], clause 5.4.4.2 for -MME initiated dedicated bearer deactivation.
Figure 9.2.5-1: MME-initiated Dedicated Bearer Deactivation
This procedure is the same as described in TS 23 402 [3], clause 5.4.5.3 with the addition of the new step described below:
A.2 The PCRF initiates the GW Control and QoS Provisioning procedure with the BPCF to either request de-allocation of BBF resources for the affected QoS rule(s) according to TS 23.203 [4].
9.2.6 UE-initiated Resource Request and Release
This procedure is executed per TS 23 402 [3], clause 5.5, with modifications, when the PCRF determines that the UE’s request result in allocation/de-allocation of resources in the BBF access.
Figure 9.2.6-1: UE-initiated resource request/release with PMIP-based S5/S8
This procedure is the same as described in TS 23 402 [3], clause 5.5 with the addition of the new step described below.
The UE requests to add, delete or modify filter and may include the QCI and GBR if needed. Depending on the decision of the PCRF new BBF resource may be required. For instance, the PCRF may decide to initiate the activation of a new dedicated bearer.
A.2. The PCRF initiates the GW Control and QoS Provisioning procedure with the BPCF to, depending on the UE’s request, either request allocation/de-allocation of BBF resources. If resources are de-allocated the message includes the QoS rule affected. If additional BBF resources are required then the PCRF includes the QoS rule and QoS Information (SDF, QCI, ARP, GBR, MBR) according to TS 23.203 [4].
NOTE: The interaction between the BPCF and the BNG is out of scope.
9.2.7 UE requested PDN connectivity
The UE requested PDN connectivity procedure for E-UTRAN is depicted in figure 5.6.1-1, TS 23 402 [3]. The procedure allows the UE connected to a HeNB to request for connectivity to an additional PDN over E-UTRAN.
Figure 9.2.7-1: UE requested PDN connectivity with PMIP-based S5 or S8
This procedure is the same as described in TS 23 402 [3], clause 5.6.1 with modification of the existing steps and the addition of the new step described below.
The procedure is executed when the UE requests an additional PDN connection or re-establishes an existing one after a HO.
1. This step is the same as for PDN connectivity procedures as in TS 23.401 [2], figure 5.10.2-1 before step (A), with the exception as defined for the corresponding steps for GTP case, clause 9.1.1.
A.1. The description of this step is the same as step C.1 in clause 9.2.1.
If Alt.A is selected then the PCRF executes step A.4.
A.4. The PCRF initiates the GW Control and QoS Provisioning procedure with the BPCF to modify BBF resources associated with an existing QoS rules or to request new BBF resources. In either case the message includes the QoS Information (SDF, QCI, ARP, GBR, MBR) according to TS 23.203 [4].
If Alt.B is selected then the PCRF executes step B.3.
B.3. The PCRF initiates the GW Control and QoS Provisioning procedure with the BPCF to modify BBF resources associate with an existing QoS rule. The message includes the QoS Information (SDF, QCI, ARP, GBR, MBR) according to TS 23.203 [4].
NOTE: The interaction between the BPCF and the BNG is out of scope.
9.2.8 Service Request and Handover Procedures
This clause specifies the Service Request and Handover Procedures with updating the following information to Fixed Broadband Access network: the HeNB local IP address and the UDP port if NAT/NAPT is detected.
This clause is similar to clause 9.1.5, with the difference that the S5/8 interface is PMIP-based. This following call flow only shows the description on S5/S8 interfaces and Gx/Gxx/S9a interfaces.
Figure 9.2.8-1: Service Request and Handover Procedures-S5/S8 PMIP-based
1. UE initiated Service request procedure, or intra-EUTRAN Handover procedure, or inter-RAT handover is initiated, which can be referred to the corresponding descriptions of clause 9.1.5, Service Request and Handover Procedures (GTP case).
2. The (target) S-GW initiates the Gateway control session establishment (with S-GW relocated) procedure or Gateway Control and QoS Rule Request procedure (without S-GW relocated) with the PCRF, and the following additional information: the HeNB local IP address and the UDP port if NAT/NAPT is detected needs to be forwarded to the PCRF during this procedure.
If the Create Session Request message (with S-GW relocated) or Modify bearer Request message (without S-GW relocated) received by S-GW in step 1 contains none of the additional information: HeNB Local IP address and the UDP port if NAT/NAPT is detected The S-GW determines that the UE leaves femto cell and will inform this event to PCRF.
3. The description of this step is the same as step 5 in clause 9.1.5.
4. This step is the same as the corresponding steps defined in handover procedures for PMIP-based S5/S8 interface clause 5.7, and UE-triggered Service Request for PMIP-based S5/S8, clause 5.9, TS 23 402 [3]. The description of this step is the same as step 7 in clause 9.1.5.
5. This step can refer to the corresponding procedure as in clause 9.1.5.
NOTE: The description is the same as note 2 and note 3 in clause 9.1.5.