hash
stringlengths 32
32
| doc_id
stringlengths 5
12
| section
stringlengths 4
595
| content
stringlengths 0
6.67M
|
|---|---|---|---|
5817f2cb61f7e615e7879961cd761fa6
|
23.203
|
6.12 NBIFOM Routing rule
| |
5817f2cb61f7e615e7879961cd761fa6
|
23.203
|
6.12.1 General
|
The NBIFOM routing rule comprises the information about the UE request to associate an access type to a service data flow filter. The NBIFOM routing rules are provided by the PCEF to the PCRF during IP‑CAN session establishment or modification.
The PCEF derives NBIFOM routing rules based on the Routing Rules received from the UE (when UE-initiated NBIFOM mode applies) or based on requests from the UE to have the network create / modify / delete Routing Rules (when Network-initiated NBIFOM mode applies), as described in TS 23.161 [43].
Table 6.12 lists the information contained in an NBIFOM routing rule, including the information name, the description and whether the PCEF may modify this information in an updated version of the rule. The Category field indicates if a certain piece of information is mandatory or not.
Table 6.12: The NBIFOM routing rule information
Information name
Description
Category
PCEF permitted to modify in an update
Routing Rule identifier
Uniquely identifies the routing rule within an IP‑CAN session.
Mandatory
No
Routing information
This clause defines the method for detecting packets belonging to a flow and the route for the flow.
Routing Rule Priority
Determines the order, in which the routing filters are applied.
Mandatory
Yes
Routing Filter
A packet filter for the detection of IP flows.
Mandatory
Yes
Routing Access Information
The access type that the matching IP flows intend to use.
Mandatory
Yes
The Routing Rule identifier shall be unique for a NBIFOM routing rule within an IP-CAN session. It is set to the Routing Rule identifier assigned by the UE when UE-initiated NBIFOM mode applies as specified in TS 23.161 [43] or by the PCRF when Network-initiated NBIFOM mode applies.
The Routing Rule Priority defines in what order the NBIFOM routing rules are used by the PCRF to determine where to route a service data flow. The Routing Rule Priority is set according to the information provided by the UE as specified in TS 23.161 [43].
The Routing Filter comprises a single packet filter, containing information for matching IP flows. The format of the routing filter is the same as the service data flow filter described in clause 6.2.2.2. The Routing Filter is set according to the information provided by the UE as specified in TS 23.161 [43].
The Routing Access Information indicates the IP-CAN type that the IP flows matching the Routing Filter of this NBIFOM routing rule intend to use.
|
5817f2cb61f7e615e7879961cd761fa6
|
23.203
|
6.12.2 NBIFOM Routing rule operations
|
NBIFOM routing rule operations consist of creation, modification and removal of a NBIFOM routing rule.
At creation of a NBIFOM routing rule, the PCEF provides the NBIFOM routing rule information to the PCRF. The PCRF checks if there is a PCC Rule with a corresponding service data flow template installed in the PCEF. If it is so, the PCRF updates the Allowed Access Type in this PCC Rule according to the Routing Access Information. Otherwise a new PCC Rules is created with a service data flow filter equal to the Routing Filter, a precedence according to the Routing Rule Priority and the Allowed Access Type set to the Routing Access Information and then installed in the PCEF.
NOTE: If the Routing Filter is partially overlapping with a service data flow template of an installed PCC rule, it is up to the operator policy whether to reject the NBIFOM routing rule or whether to create a new PCC rule for this NBIFOM routing rule. In the latter case, this new PCC rule shall have the same parameters (except the rule name and the SDF template) and a higher precedence. The PCRF shall also ensure that relevant PCC rule modifications are applied for both PCC rules.
The PCRF shall store the relation between the Routing Rule identifier and the corresponding PCC rule. The PCRF may also reject a NBIFOM routing rule according to operator policy.
The modification of a NBIFOM routing rule to change the Routing Filter or the Routing Rule Priority triggers the PCRF to modify the service data flow filter or precedence in the corresponding installed PCC Rule accordingly.
The modification of a NBIFOM routing rule to change the Routing Access Information triggers the PCRF to change the Allowed Access Type in the corresponding installed PCC Rule accordingly.
The removal of a NBIFOM routing rule triggers the PCRF to remove the corresponding PCC Rule if the PCC rule creation was triggered by this NBIFOM routing rule. Otherwise, the PCRF removes only the Allowed Access Type in this PCC Rule.
|
5817f2cb61f7e615e7879961cd761fa6
|
23.203
|
7 PCC Procedures and flows
| |
5817f2cb61f7e615e7879961cd761fa6
|
23.203
|
7.1 Introduction
|
The specification of the PCC procedures and flows is valid for the general scenario. Access specific information is included in Annex A, Annex D, Annex H and Annex P.
The description includes procedures for IP‑CAN Session Establishment, Modification and Termination. The IP‑CAN Session modification comprises IP‑CAN bearer establishment, modification, termination, as well as unsolicited PCC decisions.
There are three distinct network scenarios for an IP‑CAN Session:
Case 1: No Gateway Control Session is required, no Gateway Control Establishment occurs at all (e.g. 3GPP Access where GTP-based S5/S8 are employed, as described in TS 23.401 [17] and the IP‑CAN specific Annexes and non-3GPP accesses where GTP-based S2a or GTP-based S2b is employed, as described in TS 23.402 [18]).
Case 2: A Gateway Control Session is required. The BBERF establishes a Gateway Control Session prior to any IP‑CAN session establishment. There are two sub-cases:
2a) The UE acquires a care of address (CoA) that is used for the S2c reference point. The same Gateway Control session applies for all IP‑CAN sessions using that CoA.
2b) A Gateway Control Session is required, as described in TS 23.402 [18] and the IP‑CAN specific Annexes, Gateway Control Session Establishment, as defined in clause 7.7.1.
Each IP‑CAN session is handled in a separate Gateway Control Session.
The PCRF determines at Gx and Gxx session establishment what case applies initially as follows:
1. If the BBERF, at establishment of the Gateway Controls Session, provides an APN, then case 2b applies for the IP‑CAN session.
2. If the BBERF, at establishment of the Gateway Controls Session, does not provide any APN, then case 2a applies for the UE. For this case, the PCRF expects tunnelling header information for each IP‑CAN session to be provided by the applicable PCEF.
3. If there is no Gateway Control Session for the UE with the same IP‑CAN type as indicated over Gx, case 1 applies.
In a handover procedure the applicable case may change for an IP‑CAN session. The PCRF determines the new case in the same manner as described above. Details are defined in each such procedure.
The procedures cover non-roaming, roaming with home routed access and roaming with access to a visited PDN.
For the non-roaming case, the H‑PCRF plays the full role of PCRF. The V‑PCRF is not applicable in this case.
For the roaming case with home routed access, the H‑PCRF interacts with the PCEF and, if the Gxx applies, the V‑PCRF interacts with the BBERF.
For the roaming case with visited access (a.k.a. local breakout in TS 23.401 [17] and TS 23.402 [18]), the V‑PCRF interacts with the PCEF and, if Gxx applies, the BBERF and, if Sd applies, the TDF.
NOTE: The roaming scenario (figure 5.1-4) with visited access is not applicable for traffic steering control.
Procedures defined in this clause cover the traffic cases where the TDF is located on Gi/SGi interface.
Procedures defined in clause 7 cover all the traffic cases where roaming partners both operate PCC. For limited PCC deployment scenarios, Annex K and Annex L specify the impacts to these procedures.
In the text describing the steps in each sequence diagram, the designation PCRF, without specifying V‑ or H‑, refers to the PCRF in non-roaming case and refers to either the V‑PCRF or the H‑PCRF in the roaming cases. The interpretation of the text "PCRF" is thus dependent on the network scenario.
When NBIFOM (defined in TS 23.161 [43]) applies, the description of the flows in this clause 7 is complemented by the description of NBIFOM dedicated behaviours documented in clause 6.1.18.
|
5817f2cb61f7e615e7879961cd761fa6
|
23.203
|
7.2 IP‑CAN Session Establishment
|
This clause describes the signalling flow for IP‑CAN Session establishment as well as network prefix and/or IP address assignment to the UE. The AF is not involved.
Figure 7.2-1: IP‑CAN Session Establishment
This procedure concerns both roaming and non-roaming scenarios. In the roaming case when a Gateway Control Session is used, the V-PCRF should proxy the Gateway Control Session Establishment information between the BBERF in the VPLMN and the H-PCRF over S9 based on PDN-Id and roaming agreements.
For the Local Breakout scenario (Figure 5.1-4) the V-PCRF shall proxy the Indication and Acknowledge of IP‑CAN Session Establishment over S9 between the PCEF in the VPLMN and the H-PCRF. For TDF and solicited application reporting, the V-PCRF shall generate ADC rules from PCC Rules containing application detection and control information as instructed by the H-PCRF over S9. Then, the V-PCRF shall install PCC Rules to the PCEF and ADC Rules to the TDF, if applicable.
In the non-roaming case (Figure 5.1-1) the V-PCRF is not involved.
1. The BBERF initiates a Gateway Control Session Establishment procedure as defined in clause 7.7.1 (applicable to case 2a during initial attach and case 2b, as defined in clause 7.1).
2. The GW (PCEF) receives a request for IP‑CAN Bearer establishment. A PDN Connection Identifier may be included in the request. The GW (PCEF) accepts the request and assigns an IP address and (if requested) network prefix for the user.
3. The PCEF determines that the PCC authorization is required, requests the authorization of allowed service(s) and PCC Rules information. The PCEF includes the following information: UE Identity (e.g. MN NAI), a PDN identifier (e.g. APN), the IP‑CAN type and the IPv4 address and IPv6 network prefix, if available, the PDN Connection Identifier received for IP‑CAN Bearer establishment if multiple PDN connections to the same APN are supported and, if available, the default charging method and the IP‑CAN bearer establishment modes supported and information on whether PCEF is enhanced with ADC. It may also include the TDF IP address, in case of solicited application reporting, if applicable. If the UE has declared support for the extended TFT filter format and the PCEF does not prevent the use thereof, then the PCEF shall indicate that support to the PCRF. The PDN identifier, IP address(es) and UE identity enables identification of the IP‑CAN session. The IP‑CAN Type identifies the type of access from which the IP‑CAN session is established. If the service data flow is tunnelled at the BBERF, the PCEF shall provide information about the mobility protocol tunnelling encapsulation header. The PCEF may also include the Default Bearer QoS and APN-AMBR (applicable to case 1 and case 2a, as defined in clause 7.1). In case 2a the PCEF may also include charging ID information. If the GW/PCEF allocates a shorter IPv6 prefix for use with IPv6 Prefix Delegation, the GW/PCEF provides this shorter prefix as the IPv6 network prefix. If Charging Characteristics were received by GW/PCEF according to TS 23.401 [17] and TS 23.402 [18], the GW/PCEF also forwards Charging Characteristics to the PCRF. Based on local configuration the GW/PCEF may also include the following information: its control plane IPv4 and/or IPv6 address(es), an indication on how the APN was selected, indications on whether IP address(es) where statically or dynamically allocated and the charging identifier of the default bearer to identify different records belonging to the same PDN connection, indication on whether the charging identifier is the only one for the IP‑CAN session. When the PCEF has received the IMEI(SV) in the request for IP‑CAN Bearer establishment received at step 2, the PCEF shall transfer this information to the PCRF.
NOTE 1: In case of TDF and solicited application reporting, either PCEF informs PCRF with TDF IP address, or PCRF has it preconfigured per each one of PCEFs.
4. If the PCRF does not have the subscriber's subscription related information, it sends a request to the SPR in order to receive the information related to the IP‑CAN session. The PCRF provides the subscriber ID and, if applicable, the PDN identifier to the SPR. The PCRF may request notifications from the SPR on changes in the subscription information.
5. The PCRF stores the subscription related information containing the information about the allowed service(s) and PCC Rules information and may include MPS EPS Priority, MPS Priority Level and IMS Signalling Priority for establishing a PS session with priority and may also include user profile configuration indicating whether application detection and control should be enabled for the IP-CAN session.
6. If the PCRF determines that the policy decision depends on the status of the policy counters available at the OCS and such reporting is not established for the subscriber, the PCRF sends an Initial Spending Limit Report Request as defined in clause 7.9.1. If policy counter status reporting is already established for the subscriber and the PCRF determines that the status of additional policy counters are required, the PCRF sends an Intermediate Spending Limit Report Request as defined in clause 7.9.2.
7. The PCRF makes the authorization and policy decision. If MPS EPS Priority, MPS Priority Level and IMS Signalling Priority are present for the user, the PCRF takes the information into account.
8. For the solicited application reporting, the PCRF requests the TDF to establish the relevant session towards PCRF and provides ADC Rules to the TDF, as per user profile configuration, if traffic steering control over Sd applies, ADC Rules may contain traffic steering control information. The PCRF shall include the following information: a PDN identifier (e.g. APN), the IPv4 address and/or IPv6 network prefix, if available and may also include the UE Identity Information and the location/access network information, if available. If Charging Characteristics were received by the PCRF according to step 3 and charging is applicable for the TDF, the PCRF shall also forward received Charging Characteristics to the TDF. Additionally, if received from the PCEF and if charging is applicable for the TDF, the PCRF shall also forward the following parameters to the TDF: the GW/PCEF control plane IPv4 and/or IPv6 address (es), an indication on how the APN was selected, indications on whether IP address (es) where statically or dynamically allocated and the PDN charging identifier of the default bearer. The PCRF may also subscribe to the Event Triggers applicable for the TDF, according to table 6.2.
NOTE 2: If Charging Characteristics are received by the PCRF from the PCEF, PCRF may take them into account when providing Charging information and Default charging method to the TDF.
9. If online charging is applicable for the TDF and at least one ADC rule with charging parameters was activated, the TDF activates the online charging session and provides relevant input information for the OCS decision. Depending on operator configuration, the TDF may request credit from the OCS for each charging key of the activated ADC rules.
10. If online charging is applicable for the TDF, the OCS provides the possible credit information to the TDF and may provide re-authorisation triggers for each of the credits.
11. The TDF sends an Ack (accept or reject of the ADC rule operation(s)) to inform the PCRF about the outcome of the actions related to the decision(s) received in step 8. The Ack also includes the list of Event Triggers to report, including the case when the OCS provides any credit re-authorisation trigger, e.g. PLMN change, Location change (serving CN node), which cannot be monitored at the TDF. The Event Triggers indicate to the PCRF what events to be forwarded from the PCRF to the TDF, once PCRF gets the corresponding Event Report from the PCEF/BBERF.
12. If traffic steering control over St applies, the PCRF determines the traffic steering control information needed for the IP-CAN session; the PCRF provides the UE IPv4 address and/or UE IPv6 prefix and one or more sets of traffic steering control information to the TSSF. The TSSF identifier is pre-configured on the PCRF per e.g. PCEF.
13. The TSSF sends an acknowledgement to the PCRF to inform the PCRF about the outcome of the actions related to the traffic steering control information received in step 12.
14. The PCRF sends the decision(s) including the chosen IP‑CAN bearer establishment mode and indicates whether the use of the extended TFT filter format is allowed in the IP-CAN session, to the PCEF. The GW (PCEF) enforces the decision. The PCRF may provide the default charging method and may include the following information: the PCC Rules to activate and the Event Triggers to report. If PCEF is enhanced with ADC, the applicable PCC rules are provided, according to the user profile configuration, if traffic steering control over Gx applies, PCC Rules may contain traffic steering control information. The Policy and Charging Rules allow the enforcement of policy associated with the IP‑CAN session. The Event Triggers indicate to the PCEF what events must be reported to the PCRF. If the TDF provided a list of Event Triggers to the PCRF in the previous step, the PCRF shall also provide those Event Triggers to the PCEF.
15. If online charging is applicable and at least one PCC rule with charging parameters was activated, the PCEF activates the online charging session and provides relevant input information for the OCS decision. Depending on operator configuration, the PCEF may request credit from the OCS for each charging key of the activated PCC rules.
16. If online charging is applicable, the OCS provides the possible credit information to the PCEF and may provide re-authorisation triggers for each of the credits.
In cases 2a and 2b, if the OCS provides any re-authorisation trigger, which cannot be monitored at the PCEF, the PCEF shall request PCRF to arrange those to be reported by the BBERF via the PCRF.
17. If at least one PCC rule was successfully activated and if online charging is applicable and credit was not denied by the OCS, the GW (PCEF) acknowledges the IP‑CAN Bearer Establishment Request.
18. If network control applies the GW may initiate the establishment of additional IP-‑CAN bearers. See Annex A and Annex D for details.
19. If the PCRF in step 12 has requested an acknowledgement based on PCC rule operations, the GW (PCEF) sends the IP‑CAN Session Establishment Acknowledgement to the PCRF in order to inform the PCRF of the activated PCC rules result.
|
5817f2cb61f7e615e7879961cd761fa6
|
23.203
|
7.3 IP‑CAN Session Termination
| |
5817f2cb61f7e615e7879961cd761fa6
|
23.203
|
7.3.1 UE initiated IP‑CAN Session termination
|
Figure 7.3.1: IP‑CAN Session Termination
This procedure concerns both roaming and non-roaming scenarios. In the roaming case when home routed access is used (figure 5.1-3) or if case 2a applies (as defined in clause 7.1) for Local Breakout (figure 5.1-4), the V‑PCRF should proxy the GW (BBERF) initiated Gateway Control Session Termination or the Gateway Control and QoS Rules Provision between the BBERF in the VPLMN and the H‑PCRF. For those cases it is also the H-PCRF that initiates the PCRF initiated Gateway Control Session Termination procedure or the Gateway Control and QoS Rules Provision procedure and proxy the information over S9 to the BBERF through the V‑PCRF.
For the Local breakout scenario (figure 5.1-4) the V-PCRF shall proxy Indication and Acknowledge of IP‑CAN Session Termination over S9 between the PCEF in the VPLMN and the H‑PCRF. If the AF resides in the VPLMN, the V‑PCRF shall proxy AF session signalling over S9 between the AF and the H‑PCRF.
NOTE 1: The case when the AF resides in the VPLMN is not showed in the figure.
For the same scenario if either case 1 or case 2b applies (as defined in clause 7.1), the V-PCRF may respond to/initiate the Gateway Control Session procedures locally without notifying the H‑PCRF.
In the non-roaming case (figure 5.1-1) the V‑PCRF is not involved at all.
1. If case 2b applies, the GW (BBERF) receives a request to remove the IP‑CAN session. In case 2a, the request goes transparently through the GW (BBERF). In all cases, the GW (PCEF) receives a request to remove the IP‑CAN session.
2. If case 2b applies, the GW (BBERF)-initiated GW Control Session Termination procedure as defined in clause 7.7.2.1 is initiated.
3. The GW (PCEF) indicates that the IP‑CAN Session is being removed and provides relevant information to the PCRF.
NOTE 2: The GW (PCEF) may proceed to step 11 in parallel with the indication of IP‑CAN Session termination.
4. The PCRF finds the PCC Rules that require an AF to be notified and removes PCC Rules for the IP‑CAN session.
5. The GW (PCEF) removes all PCC Rules associated with the IP‑CAN session.
6. The PCRF notifies the AF that there are no transmission resources for the service if this is requested by the AF.
7. The AF acknowledges the notification of the loss of transmission resources.
8. If this is the last IP-CAN session for this subscriber requiring policy counter status reporting, the Final Spending Limit Report Request as defined in clause 7.9.3 is sent. If any existing IP-CAN sessions for this subscriber require policy counter status reporting, the Intermediate Spending Limit Report Request as defined in clause 7.9.2 may be sent to alter the list of subscribed policy counters.
9. If there is an active Sd session between TDF and PCRF, the PCRF terminates it.
10. For the solicited application reporting, the TDF deactivates all the ADC Rules associated with the TDF session. The TDF acknowledges the termination request from the PCRF.
11. If online charging is applicable for the TDF, the TDF issues the final reports and returns the remaining credit to the OCS.
12. The OCS acknowledges the credit report and terminates the online charging session with the TDF.
13. The PCRF removes the information related to the terminated IP‑CAN Session (subscription information etc.) and acknowledges to the GW (PCEF) that the PCRF handling of the IP‑CAN session has terminated. This interaction is the response to the GW (PCEF) request in step 3.
NOTE 3: Step 13 may be initiated any time after step 7.
14. The GW (PCEF) continues the IP‑CAN Session removal procedure.
15. If case 2a applies, the GW Control and QoS Rules Provision procedure as defined in clause 7.7.4 may be initiated to remove the QoS rules associated with the IP‑CAN session being terminated. This applies e.g. in case the Gateway Control Session shall remain to serve other IP‑CAN sessions.
Alternatively, if case 2a applies and the PCRF determines that all QoS rules are to be removed and the Gateway Control Session shall be terminated, the PCRF-initiated GW Control Session Termination procedure as defined in clause 7.7.2.2 is initiated. This applies e.g. in case the UE is detached and the CoA acquired by the UE is not used for any other IP‑CAN session.
16. If online charging is applicable for the PCEF, the PCEF issues the final reports and returns the remaining credit to the OCS.
NOTE 4: Step 16 may be initiated any time after step 13.
17. The OCS acknowledges that credit report and terminates the online charging session with the PCEF.
18. The PCRF sends a cancellation notification request to the SPR if it has subscribed such notification. If all IP-CAN sessions of the user to the same APN are terminated, the PCRF stores the remaining usage allowance in the SPR.
NOTE 5: Step 18 may be initiated any time after step 13.
19. The SPR sends a response to the PCRF.
20. If RUCI reporting from RCAF to PCRF is used, the PCRF sends a Release context request message to the RCAF using the previously stored identity of the RCAF.
21. RCAF acknowledges this by sending the Release context response message to the PCRF. The RCAF releases the context corresponding to the given UE for the given APN, including any reporting restrictions. This also implies that the RCAF does not indicate to the PCRF that the congestion state is over. In case of multiple PCRFs being in simultaneous use for a given UE, a Release context request message from a PCRF applies to the UE context specific to the given Np connection only, identified by the APN. The RCAF can completely release all context information for a given UE when it has released the context for each Np connection of the given UE.
NOTE 6: The IP‑CAN Session removal procedure may proceed in parallel with the indication of IP‑CAN Session termination.
22. If the PCRF has provided traffic steering control information to the TSSF for the IP-CAN session, the PCRF sends a request to the TSSF to remove the traffic steering control information associated to the UE IPv4 address and/or to the UE IPv6 prefix for the terminated IP-CAN session.
NOTE 7: Step 22 may be initiated any time after step 13.
23. The TSSF acknowledges the removal of the traffic steering control information.
|
5817f2cb61f7e615e7879961cd761fa6
|
23.203
|
7.3.2 GW (PCEF) initiated IP‑CAN Session termination
|
Figure 7.3.2: GW (PCEF) Initiated IP‑CAN Session Termination
This procedure concerns both roaming and non-roaming scenarios. In the roaming case when home routed access is used (figure 5.1-3) or if case 2a applies (as defined in clause 7.1) for Local Breakout (figure 5.1-4), the V‑PCRF should proxy the GW (BBERF) initiated Gateway Control Session Termination or the Gateway Control and QoS Rules Provision between the BBERF in the VPLMN and the H‑PCRF. For those cases it is also the H-PCRF that initiates the PCRF initiated Gateway Control Session Termination procedure or the Gateway Control and QoS Rules Provision procedure and proxy the information over S9 to the BBERF through the V‑PCRF.
For the Local breakout scenario (figure 5.1-4) the V-PCRF shall proxy Indication and Acknowledge of IP‑CAN Session Termination over S9 between the PCEF in the VPLMN and the H‑PCRF. If the AF relies in the VPLMN, the V‑PCRF shall proxy AF session signalling over S9 between the AF and the H‑PCRF.
NOTE 1: The case when the AF resides in the VPLMN is not showed in the figure.
For the same scenario if either case 1 or case 2b applies (as defined in clause 7.1), the V‑PCRF may respond to/initiate the Gateway Control Session procedures locally without notifying the H‑PCRF.
In the non-roaming case (figure 5.1-1) the V‑PCRF is not involved at all.
1. The GW (PCEF) detects that IP‑CAN Session termination is required.
2. The GW (PCEF) sends a request to remove the IP‑CAN session.
3. If case 2b applies, the GW (BBERF)-initiated GW Control Session Termination procedure as defined in clause 7.7.2.1 is initiated.
4. The GW (PCEF) receives the response for the IP‑CAN session removal.
5. The GW (PCEF) indicates the IP‑CAN Session termination and provides the relevant information to the PCRF.
6. The PCRF finds the PCC Rules that require an AF to be notified.
7. The PCRF notifies the AF that there are no transmission resources for the service if this is requested by the AF.
8. The AF acknowledges the notification on the loss of transmission resources.
9. If this is the last IP-CAN session for this subscriber requiring policy counter status reporting, the Final Spending Limit Report Request as defined in clause 7.9.3 is sent. If any existing IP-CAN sessions for this subscriber require policy counter status reporting, the Intermediate Spending Limit Report Request as defined in clause 7.9.2 may be sent to alter the list of subscribed policy counters.
10. The GW (PCEF) removes all the PCC Rules associated with the IP‑CAN session.
11. If there is an active Sd session between TDF and PCRF, the PCRF informs TDF about IP-CAN session termination.
12. For the solicited application reporting, the TDF deactivates all the ADC Rules associated with the TDF session. The TDF acknowledges the termination request from the PCRF.
13. If online charging is applicable for the TDF, the TDF issues the final reports and returns the remaining credit to the OCS.
14. The OCS acknowledges the credit report and terminates the online charging session with the TDF.
15. The PCRF removes the information related to the terminated IP‑CAN Session (subscription information etc.) and acknowledges the IP‑CAN Session termination.
NOTE 2: Step 15 may be initiated any time after step 6.
16. If case 2a applies, the GW Control and QoS Rules Provision procedure as defined in clause 7.7.4 may be initiated to remove the QoS rules associated with the IP‑CAN session being terminated. This applies e.g. in case the Gateway Control Session shall remain to serve other IP‑CAN sessions.
Alternatively, if case 2a applies and the PCRF determines that the Gateway Control session shall be terminated, the PCRF-initiated GW Control Session Termination procedure as defined in clause 7.7.2.2 is initiated. This applies e.g. in case the UE is detached and the CoA acquired by the UE is not used for any other IP‑CAN session.
17. If online charging is applicable for the PCEF, the PCEF issues final reports and returns the remaining credit to the OCS.
NOTE 3: Step 17 may be initiated any time after step 15.
18. The OCS acknowledges the credit report and terminates the online charging session.
19. The PCRF sends a cancellation notification request to the SPR if it has subscribed such notification. If all IP-CAN sessions of the user to the same APN are terminated, the PCRF stores the remaining usage allowance in the SPR.
NOTE 4: Step 19 may be initiated any time after step 8.
20. The SPR sends a response to the PCRF.
21. If RUCI reporting from RCAF to PCRF is used, the PCRF sends a Release context request message to the RCAF using the previously stored identity of the RCAF.
22. RCAF acknowledges this by sending the Release context response message to the PCRF. The RCAF releases the context corresponding to the given UE for the given APN, including any reporting restrictions. This also implies that the RCAF does not indicate to the PCRF that the congestion state is over. In case of multiple PCRFs being in simultaneous use for a given UE, a Release context request message from a PCRF applies to the UE context specific to the given Np connection only, identified by the APN. The RCAF can completely release all context information for a given UE when it has released the context for each Np connection of the given UE.
23. If the PCRF has provided traffic steering control information to the TSSF for the IP-CAN session, the PCRF sends a request to the TSSF to remove the traffic steering control information associated to the UE IPv4 address and/or the UE IPv6 prefix for the terminated IP-CAN session.
NOTE 5: Step 23 may be initiated any time after step 6.
24. The TSSF acknowledges the removal of the traffic steering control information.
|
5817f2cb61f7e615e7879961cd761fa6
|
23.203
|
7.4 IP‑CAN Session Modification
| |
5817f2cb61f7e615e7879961cd761fa6
|
23.203
|
7.4.1 IP‑CAN Session Modification; GW (PCEF) initiated
|
This clause describes the signalling flow for the IP‑CAN Session modification initiated by the GW (PCEF). These modifications include IP‑CAN bearer establishment and termination as well as modification if the triggering conditions given to the PCEF are fulfilled.
For the PCEF enhanced with ADC, the reason for such a modification may be that a start or stop of application traffic that matches with one of the activated PCC Rules is detected.
The AF may be involved. An example of the scenario is authorization of a session-based service for which an IP‑CAN Session is also modified.
Figure 7.4: IP‑CAN Session Modification; GW (PCEF) initiated
This procedure concerns both roaming and non-roaming scenarios. In the roaming case when home routed access applies (figure 5.1-3) or if case 2a applies (as defined in clause 7.1) for Local Breakout (figure 5.1-4), when a Gateway Control Session is used, the H‑PCRF may initiate a Gateway Control and QoS Rules Provisioning procedure towards the BBERF and proxy the information through the V‑PCRF over S9.
For case 2b in the Local Breakout scenario (figure 5.1-4) and if the Gateway Control Session is terminated locally at the V‑PCRF, the V‑PCRF shall initiate the Gateway Control and QoS Rules Provisioning procedure locally without notifying the H‑PCRF. For this case the V-PCRF shall proxy the Indication and Acknowledge of IP‑CAN Session Modification over S9 between the PCEF in the VPLMN and the H‑PCRF. If the AF is located in the VPLMN for this scenario, the V‑PCRF shall proxy AF session signalling over S9 between the AF and the H‑PCRF.
NOTE 1: The case when the AF resides in the VPLMN is not shown in the figure.
In the non-roaming case (figure 5.1-1) the V‑PCRF is not involved at all.
1. Optionally, the AF provides/revokes service information to the PCRF due to AF session signalling. The AF may subscribe at this point to notification of bearer level events related to the service information.
NOTE 2: For the PCRF to generate the applicable events, the PCRF instructs the PCEF to report events related to the corresponding PCC rules. Such events are not shown in this sequence diagram.
2. The PCRF stores the service information and responds with the Acknowledgement to the AF.
3. The GW (PCEF) may receive IP‑CAN session signalling for IP‑CAN Session modification. PDN Connection Identifier may be included in the IP‑CAN session signalling.
4. The GW (PCEF) makes a decision to trigger IP‑CAN Session modification either caused by the previous step or based on an internal decision or, e.g. if the GW (PCEF) enhanced with ADC, has detected the start/ stop of application traffic, requested by one of the activated PCC Rules.
5. The GW (PCEF) determines that the PCC interaction is required and sends an Indication of IP‑CAN Session modification (Event Report, affected PCC Rules, if available, the PDN Connection Identifier) to the PCRF together with, if available, User Location Information and/or UE Time Zone and RAN/NAS Release Cause and, if changed, the new IP‑CAN bearer establishment modes supported. If there is a limitation or termination of the transmission resources for a PCC Rule, the GW (PCEF) reports this to the PCRF. If flow mobility applies, the GW (PCEF) may include updated IP flow mobility routing information for any IP flows; the GW (PCEF) also provides an indication if default route for the IP‑CAN session is changed.
6. The PCRF correlates the request for PCC Rules with the IP‑CAN session and service information available at the GW (PCEF).
7. The PCRF may need to report to the AF an event related to the transmission resources if the AF requested it at initial authorisation.
8. The AF acknowledges the event report and/or responds with the requested information.
9. If the PCRF determines a change to policy counter status reporting is required, it may alter the subscribed list of policy counters using the Initial, Intermediate or Final Spending Limit Report Request procedures as defined in clauses 7.9.1, 7.9.2 and 7.9.3.
10. The PCRF makes the authorization and policy decision.
11. For the TDF solicited application reporting, the steps 11-14 take place. The PCRF provides all new ADC decisions to the TDF. This may include ADC Rules activation, deactivation and modification, if traffic steering control over Sd applies, ADC Rules may contain traffic steering control information. This may also include the list of Event triggers and also Event Report for the Event triggers, if reported by the PCEF/BBERF to the PCRF, if the TDF has previously subscribed for such an Event Report. In case of local breakout, the V-PCRF shall provide ADC rules generated from PCC Rules providing application detection and control as instructed by the H‑PCRF over S9.
For unsolicited application reporting and if the PCRF has recorded the release of an IPv4 address in step 5, the PCRF terminates the related Sd session.
12. If online charging is applicable for the TDF, the TDF may request credit for new charging keys from the OCS and/or may inform the OCS about re-authorization trigger if the event occurs and/or may issue final reports and return remaining credit for charging keys no longer active to the OCS.
13. If OCS was contacted by the TDF, the OCS provides the credit information to the TDF and/or acknowledges the credit report.
14. The TDF sends an Ack (accept or reject of the ADC rule operation(s)) to inform the PCRF about the outcome of the actions related to the decision(s) received in step 11. The Ack also includes the list of Event Triggers to report, including the case when the OCS provides any credit re-authorisation trigger, e.g. PLMN change, Location change (serving CN node), which cannot be monitored at the TDF. The Event Triggers indicate to the PCRF what events to be forwarded from the PCRF to the TDF, once PCRF gets the corresponding Event Report from the PCEF/BBERF.
15. If traffic steering control over St applies, the PCRF determines if traffic steering control information needs to be modified/provisioned for the IP-CAN session; the PCRF provides to the TSSF the traffic steering control information associated to the UE IPv4 address and/or to the UE IPv6 prefix.
16. The TSSF sends an acknowledgement to the PCRF to inform the PCRF about the outcome of the actions related to the traffic steering control information received in step 15.
17. The PCRF sends an Acknowledge of IP‑CAN Session modification (PCC Rules, Event Triggers and, if changed, the chosen IP‑CAN bearer establishment mode) to the GW (PCEF). If traffic steering control over Gx applies, PCC Rules may contain traffic steering control information. The GW (PCEF) enforces the decision. If the TDF provided a list of Event Triggers to the PCRF in the previous step, the PCRF shall also provide those Event Triggers to the PCEF.
18. If online charging is applicable for the PCEF, the GW (PCEF) may request credit for new charging keys from the OCS and/or may inform the OCS about re-authorization trigger if the event occurs and/or may issue final reports and return remaining credit for charging keys no longer active to the OCS.
19. If OCS was contacted by the PCEF, the OCS provides the credit information to the GW (PCEF) and/or acknowledges the credit report.
20 The GW (PCEF) acknowledges or rejects any IP‑CAN Session signalling received in step 3.
An IP‑CAN bearer establishment is accepted if at least one PCC rule is active for the IP‑CAN bearer and in case of online charging credit was not denied by the OCS. Otherwise, the IP‑CAN bearer establishment is rejected.
An IP‑CAN bearer termination is always acknowledged by the GW (PCEF).
An IP‑CAN bearer modification not upgrading the QoS and not providing traffic mapping information is always acknowledged by the GW (PCEF). An IP‑CAN bearer modification is accepted if the provided traffic mapping information is accepted by the PCRF. Otherwise, the IP‑CAN bearer modification is rejected.
In case of a GW (PCEF) internal decision the GW (PCEF) initiates any additional IP‑CAN Session signalling required for completion of the IP‑CAN Session modification (applicable to case 1).
In case the IP‑CAN session modification is due to the BBF transitioning from a BBERF in the source access-network to the PCEF, the PCEF initiates IP‑CAN bearer signalling to activate bearers in the target access network (applicable to case 1).
21. The GW (PCEF) receives the response for the IP‑CAN Session signalling request (applicable to case 1).
22. The GW (PCEF) sends a Provision Ack (accept or reject of the PCC rule operation(s)) to inform the PCRF about the outcome of the GW (PCEF) actions related to the decision(s) received in step 15.
NOTE 3: For Cases 2a and 2b, the rejection of PCC rule operation can only occur as a result of online charging interaction.
23. Based on the result of PCC rule operations, the PCRF decides whether to initiate a Gateway Control and QoS Rules provision procedure as defined in clause 7.7.4, if required to keep the PCC and QoS rules aligned (applicable to cases 2a and 2b, as defined in clause 7.1).
If there are multiple BBERFs associated with the IP‑CAN session, this step is performed with all the affected BBERFs.
24. If the AF requested it, the PCRF notifies the AF of related bearer level events (e.g. transmission resources are established/released/lost).
NOTE 4: Based on the outcome reported in this step the AF performs the appropriate action, e.g. starting charging or terminating the AF session.
25. The AF acknowledges the notification from the PCRF.
|
5817f2cb61f7e615e7879961cd761fa6
|
23.203
|
7.4.2 IP‑CAN Session Modification; PCRF initiated
|
This clause describes the signalling flow for the IP‑CAN Session modification initiated by the PCRF. The AF or TDF or the OCS or the TSSF may be involved. An example of PCRF inputs that may trigger the procedure include:
- Initiation and authorization of a session-based service for which an IP‑CAN Session is modified.
- A change in the status of a policy counter.
IP‑CAN Session handling and handling of PCC rules for non-session based services and also general handling of PCC rules that are not subject to AF-interaction or TDF-interaction is also applicable here.
Figure 7.5: IP‑CAN Session Modification; PCRF initiated
This procedure concerns both roaming and non-roaming scenarios. In the roaming case when home routed access applies (figure 5.1-3) or if case 2a applies (as defined in clause 7.1) for Local Breakout (figure 5.1-4), when a Gateway Control Session is used, the V‑PCRF shall proxy Gateway Control and QoS Rules Request between the BBERF in the VPLMN and the H‑PCRF over S9. For this case the H‑PCRF may also initiate a Gateway Control and QoS Rules Provisioning procedure towards the BBERF in the VPLMN and proxy the information via the V‑PCRF over S9.
For case 2b in the Local Breakout scenario (figure 5.1-4) and if the Gateway Control Session is terminated locally at the V‑PCRF, the V-PCRF shall reply to/initiate Gateway Control Session and QoS Rules Request/Provisioning procedures locally without notifying the H‑PCRF. For this case the V‑PCRF shall proxy the Policy and Charging Rules Provisioning and Acknowledge over S9 between the PCEF in the VPLMN and the H‑PCRF. If the AF is located in the VPLMN for this scenario, the V‑PCRF shall proxy AF session signalling over S9 between the AF and the H‑PCRF.
NOTE 1: The case when the AF resides in the VPLMN is not showed in the figure.
In the non-roaming case (figure 5.1-1) the V‑PCRF is not involved at all.
1a. Optionally, the AF provides/revokes service information to the PCRF due to AF session signalling. The AF may subscribe at this point to notification of bearer level events related to the service information. The AF may also provide a reference ID to a transfer policy that the AF previously negotiated with the PCRF (as described in clauses 6.1.16 and 7.11.1).
NOTE 2: For the PCRF to generate the applicable events, the PCRF instructs the PCEF to report events related to the corresponding PCC rules. Such events are not shown in this sequence diagram.
1b. Alternatively, optionally, for TDF, e.g. the TDF detects the start/stop of an application traffic that matches with one of the active ADC Rules.
For solicited application reporting, if the start/stop of application traffic detection Event Trigger was received from the PCRF and the reporting is not muted for the ADC rule, the TDF shall provide application information to the PCRF, including the application identifier, start or stop of application traffic detection event trigger and, for the start of application's traffic detection, the service data flow descriptions, if deducible. Additionally, the application instance identifier should be included in the report both for Start and for Stop of application traffic detection, when the service data flow descriptions are provided.
For unsolicited application reporting, the Sd reports the same application information to the PCRF unconditionally. The TDF establishes a new Sd session if it detects an application for an IPv4 address or IPv6 address for which no corresponding Sd session exists.
1c. Alternatively, optionally, the OCS provides a Spending Limit Report to the PCRF as described in clause 7.9.4.
1d. Alternatively, optionally, the RCAF provides a Congestion Report to the PCRF as described in clause 7.10.1.
NOTE 3: This step is not shown on the diagram.
2a. The PCRF stores the service information if available and responds with the Acknowledgement to the AF. This is applicable to 1a case.
NOTE 4: Without AF interaction, a trigger event in the PCRF may cause the PCRF to determine that the PCC rules require updating at the PCEF, e.g. change to configured policy.
NOTE 5: This procedure could also be triggered by the Gateway Control and QoS Rules Request procedure as described in clause 7.7.3.
3. If the PCRF determines a change to policy counter status reporting is required, it may alter the subscribed list of policy counters using the Initial, Intermediate or Final Spending Limit Report Request procedures as defined in clauses 7.9.1, 7.9.2 and 7.9.3.
4. The PCRF makes the authorization and policy decision. If the AF provided a reference ID to a transfer policy in step 1a, the PCRF shall retrieve the corresponding transfer policy from the SPR before making any decisions.
5. The PCRF may store the application information if provided and responds with an Acknowledgement to the TDF (for unsolicited application reporting) or a Sd session modification (for solicited application reporting). For the TDF solicited application reporting, the PCRF may provide a new ADC decision to the TDF. If the last ADC rule is deactivated, the PCRF requests the TDF to terminate the Sd session towards the PCRF. If there is no active Sd session yet between the TDF and the PCRF, the PCRF requests the TDF to establish the Sd session towards PCRF and provides an ADC decision to the TDF, if traffic steering control over Sd applies, ADC Rules may contain traffic steering control information. In case of local breakout, the V-PCRF shall provide ADC rules generated from PCC Rules providing application detection and control as instructed by the H‑PCRF over S9.
6. If online charging is applicable for the TDF, the TDF may request credit for new charging keys from the OCS and/or may inform the OCS about re-authorization trigger if the event occurs and/or may issue final reports and return remaining credit for charging keys no longer active to the OCS.
7. If OCS was contacted by the TDF, the OCS provides the credit information to the TDF and/or acknowledges the credit report.
8. For the TDF solicited application reporting, in the case of an existing on-going session, if requested by the PCRF the TDF sends a Provision Ack (accept or reject of the ADC Rule operation(s)). For a new session, the TDF sends an Ack. This is to inform the PCRF about the outcome of the actions related to the received ADC decision(s). The Provision Ack / Ack also includes the list of Event Triggers to report, including the case when the OCS provides any credit re-authorisation trigger, e.g. PLMN change, Location change (serving CN node), which cannot be monitored at the TDF. The Event Triggers indicate to the PCRF what events to be forwarded from the PCRF to the TDF, once PCRF gets the corresponding Event Report from the PCEF/BBERF.
9. If traffic steering control over St applies, the PCRF determines if traffic steering control information needs to be modified/provisioned for the IP-CAN session; the PCRF provides to the TSSF the traffic steering control information associated to the UE IPv4 address and/or to the UE IPv6 prefix.
10. The TSSF sends an acknowledgement to the PCRF to inform the PCRF about the outcome of the actions related to the traffic steering control information received in step 9.
11. If there is no Gateway Control and QoS Rules Reply pending and there is a need to provision QoS rules, the PCRF initiates a Gateway Control and QoS Rules Provision Procedure as defined in 7.7.4 (applicable to cases 2a and 2b, as defined in clause 7.1).
If there are multiple BBERFs associated with the IP‑CAN session, Step 9 is performed with the BBERFs that support UE/NW bearer establishment mode.
NOTE 6: If there is a Gateway Control and QoS Rules Reply pending, e.g. this procedure was invoked from the Gateway Control and QoS Rules Request procedure as defined in clause 7.7.3, the PCRF shall use that opportunity for provisioning the applicable QoS rules. If there are multiple BBERFs associated with the IP‑CAN session and the procedure was invoked by a Gateway Control and QoS Rules Request procedure from the primary BBERF, the PCRF may receive a Gateway Control and QoS Rules Request from the non-primary BBERFs.
12. The PCRF sends the Policy and Charging Rules Provision (PCC Rules, Event Trigger, Event Report) to the PCEF. If traffic steering control over Gx applies, the PCC Rules may contain traffic steering control information. If the TDF provided a list of Event Triggers to the PCRF in the previous step, the PCRF shall also provide those Event Triggers to the PCEF.
13. The PCEF enforces the decision.
14. If online charging is applicable for the PCEF, the PCEF may request credit for new charging keys from the OCS and/or may inform the OCS about re-authorization trigger if the event occurs and/or may return the remaining credit for charging keys no longer active to the OCS.
15. If OCS was contacted by the PCEF, the OCS provides the credit information to the PCEF and/or acknowledges the credit report.
16. The GW (PCEF) may send an IP‑CAN Bearer establishment, modification or termination request (applicable to case 1, as defined in clause 7.1).
An IP‑CAN bearer modification is sent by the GW (PCEF) if the QoS of the IP‑CAN bearer exceeds the authorized QoS provided by the PCRF in step 4.
An IP‑CAN bearer termination request is sent by the GW (PCEF) if all PCC rules for an IP‑CAN bearer have been removed.
17. The GW (PCEF) receives the response for the IP‑CAN Bearer modification or termination request (applicable to case 1).
18. The PCEF sends Acknowledge Policy and Charging Rules Provisioning (accept or reject of the PCC rule operation(s)) to the PCRF.
19. If the AF requested it, the PCRF notifies the AF related bearer level events (e.g. transmission resources are established/released/lost).
20. The AF acknowledges the notification from the PCRF.
|
5817f2cb61f7e615e7879961cd761fa6
|
23.203
|
7.4.3 Void
| |
5817f2cb61f7e615e7879961cd761fa6
|
23.203
|
7.5 Update of the subscription information in the PCRF
|
Figure-7.6: Procedure for update of the subscription information in the PCRF
1. The SPR detects that the related subscription profile of an IP‑CAN session has been changed.
2. If requested by the PCRF, the SPR notifies the PCRF on the changed profile.
3. The PCRF responds to the SPR.
4. The PCRF stores the updated profile.
5 If the updated subscriber profile requires the status of new policy counters available at the OCS then an Initial/Intermediate Spending Limit Report Request is sent from PCRF as defined in clauses 7.9.1 and 7.9.2. If the updated subscriber profile implies that no policy counter status is needed an Intermediate Spending Limit Report Request is sent from PCRF, if this is the last policy counter status Final Spending Limit Report Request is sent from PCRF as specified in clause 7.9.3.
6. PCRF makes an authorization and policy decision.
7. The PCRF provides all new PCC decisions to the PCEF and BBERF (if applicable), using the PCRF initiated IP‑CAN session modification procedure in clause 7.4.2. The PCRF also provides all new ADC decisions to the TDF, if applicable.
|
5817f2cb61f7e615e7879961cd761fa6
|
23.203
|
7.6 PCRF Discovery and Selection
| |
5817f2cb61f7e615e7879961cd761fa6
|
23.203
|
7.6.1 General principles
|
This clause describes the underlying principles for PCRF selection and discovery:
- A single logical PCRF entity may be deployed by means of multiple and separately addressable PCRFs.
- The H‑PCRF must be able to correlate the AF service session information received over Rx with the right IP‑CAN session (PCC Session binding).
- The PCRF must be able to associate sessions established over the different reference points (Gx, Rx, S9, Gxa/Gxc, Sd, Np), for the same UE's IP‑CAN session. The actual reference points that need to be correlated depend on the scenario (e.g. roaming, LBO etc.).
- It shall be possible to deploy a network so that a PCRF may serve only specific PDN(s). For example, PCC may be enabled on a per APN basis.
For the case 2a (as defined in clause 7.1), the same PCRF shall support all the PDNs for which PCC is enabled and for which there are potential users accessing by means of case 2a (as defined in clause 7.1).
It shall also be possible to deploy a network so that the same PCRF can be allocated for all PDN connections for a UE.
- A standardized procedure for contacting the PCRF is preferred to ensure interoperability between PCRFs from different vendors. The procedure may be specific for each reference point. The procedure shall enable the PCRF(s) to coordinate Gx, Rx and, when applicable, Gxa/Gxc, S9, Sd and Np interactions.
- It shall allow that entities contacting the PCRF may be able to provide different sets of information about the UE and PDN connections. For example:
- The AF has information about UE IP address and PDN but may not have user identity information.
- The PDN GW has information about user identity (UE NAI), the APN and the UE IP address(es) for a certain PDN connection.
- For case 2b as defined in clause 7.1, the S‑GW and trusted non-3GPP access has information about the user identity (UE NAI) and, the APN(s) but may not know the UE IP address(es).
- For case 2a as defined in clause 7.1, the trusted non-3GPP access has information about the user identity (UE NAI) and the local IP address (CoA) but may not know the APN or UE IP address(es) (HoA).
- The TDF (when the unsolicited application reporting applies) has the information about UE IP address, but may not have the UE identity.
- The RCAF has the information about the user identity (IMSI) and the APN.
- The DRA has information about the user identity (UE NAI), the APN, the UE IP address(es) and the selected PCRF address for a certain IP‑CAN Session.
When the DRA first receives a request for a certain IP‑CAN Session (e.g. from the PDN GW), the DRA selects a suitable PCRF for the IP‑CAN Session and stores the PCRF address. Subsequently, the DRA can retrieve the selected PCRF address according to the information carried by the incoming requests from other entities (e.g. the AF or the BBERF).
When the IP‑CAN Session terminates, the DRA shall remove the information about the IP‑CAN Session. In case of the PCRF realm change, the information about the IP‑CAN session stored in the old DRA shall be removed.
- All PCRFs in a PLMN belong to one or more Diameter realms. Routing of PCC messages for a UE towards the right Diameter realm in a PLMN is based on standard Diameter routing, as specified in RFC 3588, i.e. based on UE-NAI domain part. A Diameter realm shall provide the ability of routing PCC messages for the same UE and PDN connection to the same PCRF based on the available information supplied by the entities contacting the PCRF.
- A PLMN may be separated into multiple Diameter realms based on the PDN ID information or IP address range. In this case, the relevant information (PDN ID, IP address, etc) shall be used to assist routing PCC message to the appropriate Diameter realm.
- Unique identification of an IP‑CAN session in the PCRF shall be possible based on the (UE ID, PDN ID)-tuple , the (UE IP Address(es), PDN ID)-tuple and the (UE ID, UE IP Address(es), PDN ID).
- Standard IETF RFC 3588 mechanisms and components, e.g. Diameter agents, should be applied to deploy a network where the PCRF implementation specifics are invisible for Diameter clients. The use of Diameter agents, including Diameter redirect agents, shall be permitted, but the use of agents in a certain deployment shall be optional.
NOTE: For the use of private UE IPv4 address TS 29.213 [22] provides guidance.
|
5817f2cb61f7e615e7879961cd761fa6
|
23.203
|
7.6.2 Solution Principles
|
In order to ensure that all Diameter sessions for Gx, S9, Gxa/Gxc, Rx, Sd (when the unsolicited application reporting applies) and Np for a certain IP‑CAN session reach the same PCRF when multiple and separately addressable PCRFs have been deployed in a Diameter realm, an optional logical "Diameter Routing Agent (DRA)" function is enabled. This resolution mechanism is not required in networks that utilise a single PCRF per Diameter realm. The DRA has the following roles:
- When deployed, DRA needs to be contacted at first interaction point for a given GW and IP‑CAN session.
NOTE: How subsequent interactions work is described in TS 29.213 [22].
- When deployed, the DRA is on the Diameter routing path when initiating a session with a PCRF over Gx, Rx, Gxa/Gxc, S9 and Sd.
- The DRA is involved at IP‑CAN session establishment by the PDN GW.
- The DRA selects the PCRF at initial attach (IP‑CAN session or Gateway Control session establishment).
- The DRA is involved at Gateway Control session establishment by the S‑GW and trusted non-3GPP access.
- The DRA selects the PCRF at unsolicited service reporting over Sd.
- After IP‑CAN session or Gateway Control Session establishment, the DRA ensures that the same PCRF is contacted for Rx, Gxa/Gxc, Gx, S9, Sd and Np.
- The DRA keeps status of assigned PCRF for a certain UE and IP‑CAN session.
- It is assumed that there is a single logical DRA serving a Diameter realm.
- In roaming scenarios, there is only a single VPCRF for all the PCC sessions (IP‑CAN session, GW control sessions, AF session, etc.) belonging to a single PDN connection of the UE. The VPCRF shall be selected by a DRA in the visited PLMN.
Figure 7.6-1: PCRF selection and discovery using DRA
The DRA functionality should be transparent to the Diameter applications used on the Gx, Gxa/Gxc, S9, Rx, Sd or Np reference points.
In roaming scenario, home routed or local breakout, if the DRA is deployed, the vPCRF is selected by the DRA located in the visited PLMN and the hPCRF is selected by the DRA located in the home PLMN.
The parameters available for the DRA to be able to determine the already allocated PCRF depend on the reference point over which the DRA is contacted, as described in clause 7.6.1.
|
5817f2cb61f7e615e7879961cd761fa6
|
23.203
|
7.7 Gateway Control Session Procedures
| |
5817f2cb61f7e615e7879961cd761fa6
|
23.203
|
7.7.1 Gateway Control Session Establishment
| |
5817f2cb61f7e615e7879961cd761fa6
|
23.203
|
7.7.1.0 General
|
There are two cases considered for Gateway Control Session Establishment:
1. The PCEF establishes the IP‑CAN Session during the Gateway Control session establishment. This happens when the UE attaches to the EPC for the first time and when the UE establishes a new PDN Connection.
2. There exists an established IP‑CAN Session corresponding to the Gateway Control Session being established. This happens when the BBERF changes, i.e. during BBERF relocation and handovers from and to GTP based EPC.
|
5817f2cb61f7e615e7879961cd761fa6
|
23.203
|
7.7.1.1 Gateway Control Session Establishment during Attach
|
Figure 7.7.1.1-1: Gateway Control Session Establishment during Attach
This procedure concerns both roaming and non-roaming scenarios. In the roaming case when a Gateway Control Session is used, the V-PCRF should proxy the Gateway Control Session Establishment between the BBERF in the VPLMN and the H-PCRF over S9 based on PDN-Id and roaming agreements.
In the non-roaming case (Figure 5.1-1) the V-PCRF is not involved.
1. The GW (BBERF) receives an indication that it must establish a Gateway Control Session.
2. The GW (BBERF) sends the PCRF a Gateway Control Session Establishment. The BBERF includes the following information: IP‑CAN Type, UE Identity, PDN Identifier (if known), IP address(es) (if known), an indication that leg linking shall be deferred (applicable for case 2b, as defined in clause 7.1), if available, the PDN Connection Identifier and if available, the IP‑CAN bearer establishment modes supported and the indication of BBERF support for the extended TFT filter format. The IP‑CAN Type identifies the type of access used by the UE. The UE's identity and PDN Identifier requested are used to identify the subscriber and in PCRF selection to locate the PCRF function with the corresponding IP‑CAN session established by the PDN GW. The BBERF may also include the Default Bearer QoS and APN-AMBR (applicable for case 2b, as defined in clause 7.1). An indication that leg linking shall be deferred is included to inform the PCRF that linking the Gateway Control Session to a Gx session shall occur when a matching Gx message is received as described clause 6.2.1.0. Further information is supplied on an access specific basis, as described in the IP‑CAN specific Annexes.
NOTE: The BBERF support is a prerequisite for the PCRF enabling the possibility for usage of the extended TFT filter format in the IP-CAN session(s).
3. For GERAN/UTRAN accesses, if the PCRF is required to interact with the GW (PCEF), the PCRF waits until it gets informed about the establishment of the corresponding IP‑CAN session (step 7 of the IP‑CAN session establishment procedure) and performs a PCRF initiated IP‑CAN session modification procedure with the GW (PCEF).
4. The PCRF sends an Acknowledge Gateway Control Session Establishment to the GW (BBERF). The PCRF may include the following information: the chosen IP‑CAN bearer establishment mode, QoS Rules and Event Triggers. In case 2a a charging ID may be provided together with QoS rules. The QoS policy rules are employed by the GW (BBERF) to perform Bearer Binding. The Event Triggers indicate events that require the GW (BBERF) to report to the PCRF.
5. The QoS Rules and Event Triggers received by the GW (BBERF) are deployed. This will result in bearer binding being performed, according to the rules. This step may trigger IP‑CAN bearer establishment procedures. The details of bearer establishment are IP‑CAN specific.
6. An indication of Gateway Control Session Established is sent to the entity that triggered the initiation of the session.
|
5817f2cb61f7e615e7879961cd761fa6
|
23.203
|
7.7.1.2 Gateway Control Session Establishment during BBERF Relocation
|
Figure 7.7.1.2-1: Gateway Control Session Establishment during BBERF Relocation
This procedure concerns both roaming and non-roaming scenarios. In the roaming case when a Gateway Control Session is used, the V-PCRF should proxy the Gateway Control Session Establishment between the BBERF in the VPLMN and the H-PCRF over S9 based on PDN-Id and roaming agreements.
In the non-roaming case (Figure 5.1-1) the V-PCRF is not involved.
1. The target GW (BBERF) receives an indication that it must establish a Gateway Control Session.
2. The target GW (BBERF) sends the PCRF a Gateway Control Session Establishment. The BBERF includes the following information: IP‑CAN Type, UE Identity, PDN Identifier (if known), IP address(es) (if known), PDN Connection Identifier if available and, if available, the IP‑CAN bearer establishment modes supported. The IP‑CAN Type identifies the type of access used by the UE. The UE's identity and PDN Identifier requested are used to identify the subscriber and in PCRF selection to locate the PCRF function with the corresponding IP‑CAN session established by the PDN GW. The BBERF may also include the Default Bearer QoS and APN-AMBR (applicable for case 2b, as defined in clause 7.1). If the handover state is unknown to the GW (BBERF), as described in TS 23.402 [18], the GW (BBERF) includes an indication to inform the PCRF that linking the Gateway Control Session to a Gx session shall be deferred as described clause 6.2.1.0 (applicable for case 2b, as defined in clause 7.1). Further information is supplied on an access specific basis, as described in the IP‑CAN specific Annexes.
3. If case 2b of clause 7.1 applies and the PCRF correlates the Gateway Control Session with an existing IP‑CAN session, it sends an Acknowledge Gateway Control Session Establishment to the target GW (BBERF). The PCRF may include the following information: QoS Rules and Event Triggers. The QoS policy rules are employed by the GW (BBERF) to perform Bearer Binding. The Event Triggers indicate events that require the GW (BBERF) to report to the PCRF. If the BBERF supports NW/UE bearer establishment mode, the PCRF provides to the new BBERF QoS rules corresponding to existing SDFs. For a change of IP‑CAN type, the QoS parameters of some of the QoS rules may be changed or some QoS rules may not be provided to the new BBERF, e.g. depending of the capability of the target RAT.
If case 2a of clause 7.1 applies, the PCRF sends an Acknowledge Gateway Control Session Establishment to the target GW (BBERF). The PCRF includes packet filters and QoS information for the CoA in order to establish the initial bearer, e.g. for the DSMIPv6 signalling. The PCRF may also include Event Triggers.
NOTE: The packet filters and QoS information provided at this step conceptually are not QoS rules as they are not associated with any IP-CAN session. However, it is a stage 3 issue if the packet filters and QoS information are communicated to the BBERF with the same information elements by which QoS rules are communicated.
4. The QoS Rules and Event Triggers received by the target GW (BBERF) are deployed. This will result in bearer binding being performed, according to the rules. This step may trigger IP‑CAN bearer establishment procedures. The details of bearer establishment are IP‑CAN specific.
5. An indication of Gateway Control Session Established is sent to the entity that triggered the initiation of the session.
6. The target GW (BBERF) initiates the IP‑CAN Bearer signalling if required for the QoS Rules and Event Triggers deployed in step 4.
7. The target GW (BBERF) receives the response for the IP‑CAN Bearer signalling.
8. The target GW (BBERF) sends the result of the QoS rule activation to the PCRF, indicating whether the resources requested have been successfully allocated.
9. If case 2b applies the source GW (BBERF) initiates the Gateway Control Session Termination procedure as defined in clause 7.7.2.1, if appropriate.
10. If the PCC rules previously provided to the GW (PCEF) need to be removed due to the result of the QoS rule activation as received in step 8, the PCRF updates the GW (PCEF). The PCRF first waits for the PCEF initiated IP‑CAN session modification procedure to provide the updates. If the IP‑CAN session modification procedure already occurred, the PCRF performs an IP‑CAN session modification procedure with the GW (PCEF).
11. If case 2a applies the PCRF initiates a Gateway Control and QoS Rules Provision procedure towards the target GW (BBERF) as defined in clause 7.7.4, if appropriate, in order to provide any QoS Rules based on the IP‑CAN session modification of step 10. In case 2a a charging ID may be provided together with QoS rules.
12. If case 2a applies the PCRF initiates a Gateway Control and QoS Rules Provision procedure towards the source GW (BBERF) as defined in clause 7.7.4, if appropriate, in order to remove any QoS Rules affected by the GW (BBERF) re-location. If there is no other IP‑CAN session established at the source GW (BBERF), the PCRF instead initiates the Gateway Control Session Termination procedure as defined in clause 7.7.2.2.
|
5817f2cb61f7e615e7879961cd761fa6
|
23.203
|
7.7.2 Gateway Control Session Termination
| |
5817f2cb61f7e615e7879961cd761fa6
|
23.203
|
7.7.2.1 GW (BBERF)-Initiated Gateway Control Session Termination
|
Figure 7.7.2-1: BBERF-Initiated Gateway Control Session Termination
1. The GW (BBERF) is requested to terminate its Gateway Control Session.
2. The GW (BBERF) initiates a Gateway Control Session Termination towards the H-PCRF. If the GW (BBERF) is deployed in a visited network, this procedure is initiated by the GW (BBERF) to the V-PCRF. The V-PCRF forwards the information to the H-PCRF.
3. The H-PCRF replies to the GW (BBERF) with an Ack Gateway Control Session Termination. If the GW (BBERF) is deployed in a visited network, this information is sent by the H-PCRF to the V-PCRF. The V-PCRF forwards the information to the GW (BBERF).
4. The GW (BBERF) removes the QoS rules and Event triggers associated with the Gateway Control Session. This means the GW (BBERF) ceases its bearer binding and other Gateway Control functions associated with the QoS rules and Event Triggers.
5. The GW (BBERF) has completed terminating the session and can continue with the activity that prompted this procedure.
|
5817f2cb61f7e615e7879961cd761fa6
|
23.203
|
7.7.2.2 PCRF-Initiated Gateway Control Session Termination
|
Figure 7.7.2-2: PCRF-Initiated Gateway Control Session Termination
This procedure concerns both roaming and non-roaming scenarios. In the roaming case when a Gateway Control Session is used, the V-PCRF should proxy the Gateway Control Session Termination between the BBERF in the VPLMN and the H-PCRF over S9 based on PDN-Id and roaming agreements.
In the non-roaming case (Figure 5.1-1) the V-PCRF is not involved.
1. The PCRF is requested to terminate its Gateway Control Session.
2. The PCRF sends a PCRF-Initiated Gateway Control Session Termination to the GW (BBERF).
3. The GW (BBERF) removes the QoS rules and Event triggers associated with the Gateway Control Session. This means the GW (BBERF) ceases its bearer binding and other Gateway Control functions associated with the QoS rules and Event Triggers.
4. If the bearer(s) corresponding to the removed QoS rules are still established, the GW (BBERF) initiates an IP‑CAN specific bearer removal procedure.
5. The GW (BBERF) receives the response for the IP‑CAN specific bearer removal procedure.
6. The GW (BBERF) replies to the PCRF with an PCRF-Initiated Gateway Control Session Termination acknowledgement.
|
5817f2cb61f7e615e7879961cd761fa6
|
23.203
|
7.7.3 Gateway Control and QoS Rules Request
| |
5817f2cb61f7e615e7879961cd761fa6
|
23.203
|
7.7.3.1 General
|
There are two cases considered for a Gateway Control and QoS Rules Request depending on the parameters the GW (BBERF) receives:
Case A: In case the GW (BBERF) action does not depend on the subsequent IP‑CAN session modification, the GW (BBERF) can acknowledge the request after interacting with the PCRF.
NOTE 1: If QoS rules have to be updated due to the event reporting, the PCRF shall use the Gateway Control and QoS Rules Provision procedure.
Case B: The GW (BBERF) is requested to obtain QoS rules for a Gateway Control Session or to deliver IP‑CAN-specific parameters or both.
Figure 7.7.3-1: Gateway Control and QoS Rules Request
NOTE 2: If QoS rules have to be updated for case A, the PCRF shall use the Gateway Control and QoS Rules Provision procedure (clause 7.7.4).
This procedure concerns both roaming and non-roaming scenarios. In the roaming case when a Gateway Control Session is used, the V-PCRF should proxy the Gateway Control and QoS Rules Request between the BBERF in the VPLMN and the H-PCRF over S9 based on PDN-Id and roaming agreements.
In the non-roaming case (Figure 5.1-1) the V-PCRF is not involved.
1. The GW (BBERF) is requested to either report an event or obtain QoS rules or both for a Gateway Control Session.
2. The GW (BBERF) sends a Gateway Control and QoS Rules Request to the PCRF and includes the new IP‑CAN bearer establishment modes if changed. The information sent by the GW (BBERF) to the PCRF includes: a request for resource authorization and/or a report corresponding to a deployed Event Trigger.
3. If the GW (BBERF) is only requested to report an event, the GW (BBERF) acknowledges the step 1 by sending a result to the entity that triggered this procedure.
4. The PCRF initiated IP‑CAN Session Modification Procedure may occur as the result of the Gateway Control and QoS Rules Request procedure, either to forward an Event Report to the GW (PCEF) or to issue new or revised PCC Rules and Event Triggers, or both an Event Report and a PCC Rules and Event Triggers provision.
5. If the GW (BBERF) asked for new QoS rules or IP‑CAN-specific parameters need to be delivered back to the GW (BBERF) or both, the PCRF sends a Gateway Control and QoS Rules Reply to the GW (BBERF). This interaction may include QoS Rules and Event Triggers. In case 2a a charging ID may be provided together with QoS rules.
If there are multiple BBFs associated with the IP‑CAN session and the request in Step 2 is from a non-primary BBERF (see clause 6.2.1.5), only QoS rules corresponding to already activated PCC rules are included in the reply. If a request from a non-primary BBERF results in an authorization of a new QoS rule or to a modification of an existing QoS rules, the PCRF shall reject the request.
6. The QoS Rules and Event Triggers, if any, received by the GW (BBERF) are deployed. This will result in bearer binding being performed, according to the rules. This may result in the binding of additional SDFs or a change in the binding of previously bound SDFs. Subsequent events corresponding to the Event Triggers will cause an Event Report to be delivered to the PCRF by means of a Gateway Control and QoS Rules Request procedure.
7. The GW (BBERF) initiates the IP‑CAN Bearer signalling if required for the QoS Rules and Event Triggers deployed in step 6.
8. The GW (BBERF) receives the response for the IP‑CAN Bearer signalling.
9. If the step 5 contained new and/or modified QoS Rules, the result of the QoS rule activation is returned to the PCRF, indicating whether the resources requested have been successfully allocated.
|
5817f2cb61f7e615e7879961cd761fa6
|
23.203
|
7.7.3.2 Event reporting for PCEF in visited network and locally terminated Gxx interaction
|
This procedure is only used for the event reporting for a PCEF in the visited network and when the Gxx interaction is locally terminated at the V-PCRF.
Figure 7.7.3-2: Event reporting for PCEF in visited network and locally terminated Gxx interaction
1. The GW (BBERF) is requested to report an event for a Gateway Control Session.
2. The GW (BBERF) sends a Gateway Control and QoS Rules Request to the V-PCRF and includes the new IP‑CAN bearer establishment modes if changed. The information sent by the GW (BBERF) to the V-PCRF includes a report corresponding to a deployed Event Trigger.
3. Since the GW (BBERF) is only requested to report an event, the GW (BBERF) acknowledges the message received in step 1 by sending a result message to the entity that triggered this procedure.
4. The V-PCRF forwards the report corresponding to a deployed Event Trigger to the PCEF.
5. A PCEF initiated IP‑CAN Session Modification Procedure may occur as the result of the received report, either to forward the report about the relevant deployed Event Trigger(s) to the H-PCRF or to request new or revised PCC Rules and Event Triggers, or both.
|
5817f2cb61f7e615e7879961cd761fa6
|
23.203
|
7.7.4 Gateway Control and QoS Rules Provision
|
Figure 7.7.4-1: Gateway Control and QoS Rules Provision
This procedure concerns both roaming and non-roaming scenarios. In the roaming case when a Gateway Control Session is used, the V-PCRF should proxy the Gateway Control and QoS Rules Provision between the BBERF in the VPLMN and the H-PCRF over S9 based on PDN-Id and roaming agreements.
In the non-roaming case (Figure 5.1-1) the V-PCRF is not involved.
1. The PCRF is requested to update the QoS Rules and Event triggers for a Gateway Control Session.
2. The PCRF sends a Gateway Control and QoS Rules Provision to the GW (BBERF). It will include QoS Rules and Event Triggers. In case 2a a charging ID may be provided together with QoS rules. If the service data flow is tunnelled at the BBERF, the information about the mobility protocol tunnelling encapsulation header may be included. It is also possible that this interaction includes an Event Report originating from the GW (PCEF) and relayed by the PCRF to the BBERF. This Event Report enables a GW (PCEF)-originating interaction to be sent by way of the PCC infrastructure to the BBERF in situations that communication is needed between the GW (PCEF) and the GW (BBERF) and no interface exists between the GWs.
3. The QoS Rules and Event Triggers received by the GW (BBERF) are deployed. This may result in bearer binding being performed, according to the rules. Subsequent events corresponding to the Event Triggers will cause an Event Report to be delivered to the PCRF by means of a Gateway Control and QoS Rules Request procedure.
4. The GW (BBERF) initiates the IP‑CAN Bearer signalling if required for the QoS Rules and Event Triggers deployed in step 3.
5. The GW (BBERF) receives the response for the IP‑CAN Bearer signalling.
6. The GW (BBERF) sends a Gateway Control and QoS Rules Provision Ack (Result) to the PCRF. The Result information element indicates whether the indicated QoS Rules could be implemented.
7. The PCRF has completed updating the session and can continue with the activity that prompted this procedure.
If there are multiple BBFs associated with the IP‑CAN session (see clause 6.2.1.5), then the processing of the response is as follows depending on whether the BBERF is a primary BBERF or a non-primary BBERF:
- If a primary-BBERF reports failure to install a QoS rule in Step 4, the PCRF also removes the same QoS rule from the non-primary BBERF(s) if any. The PCRF also removes the corresponding PCC rule from the PCEF.
- If a non-primary BBERF reports failure to install a QoS rule, the PCRF updates the enforcement status of the QoS rule for that particular BBERF in its record but does not perform any further action.
|
5817f2cb61f7e615e7879961cd761fa6
|
23.203
|
7.7.5 Void
| |
5817f2cb61f7e615e7879961cd761fa6
|
23.203
|
7.8 Change in subscription for MPS priority services
|
Once the PCRF receives a notification of a change in MPS EPS Priority, MPS Priority Level and/or IMS Signalling Priority from the SPR, the PCRF shall make the corresponding policy decisions (i.e. ARP and/or QCI change) and initiates the necessary IP-CAN session modification procedure(s) to apply the change.
|
5817f2cb61f7e615e7879961cd761fa6
|
23.203
|
7.9 Procedures over Sy reference point
| |
5817f2cb61f7e615e7879961cd761fa6
|
23.203
|
7.9.1 Initial Spending Limit Report Request
|
This clause describes the signalling flow for the H-PCRF to request the status of the policy counters available at the OCS and to subscribe to spending limit reporting (i.e. to notifications of policy counter status changes) by the OCS. If the H-PCRF provides the list of policy counter identifier(s), the OCS returns the policy counter status per policy counter identifier provided by the PCRF. If the H-PCRF does not provide the list of policy counter identifier(s), the OCS returns the policy counter status of all policy counter(s), which are available for this subscriber.
The Initial Spending Limit Report Request includes all subscriber Identifiers associated with the UE available at the PCRF.
NOTE: In case the OCS returns the status of all available policy counters some of these may not be relevant for a policy decision (e.g. those used in a policy decision only when roaming).
Figure 7.9.1: Initial Spending Limit Report Request
1. The H-PCRF retrieves subscription information that indicates that policy decisions depend on the status of policy counter(s) held at the OCS and optionally the list of policy counter identifier(s).
2. The H-PCRF sends an Initial Spending Limit Report Request if this is the first time policy counter status information is requested for the user and the PDN connection. It includes in the request: the subscriber ID (e.g. IMSI) and , optionally, the list of policy counter identifier(s).
3. The OCS sends an Initial Spending Limit Report Response that contains a policy counter status and optionally pending policy counter statuses and their activation times, per required policy counter identifier and stores the H-PCRF's subscription to spending limit reports for these policy counters. If no policy counter identifier(s) was provided the OCS returns the policy counter status, optionally including pending policy counter statuses and their activation times, for all policy counter(s), which are available for this subscriber and stores the H-PCRF's subscription to spending limit reports of all policy counters provided to the H-PCRF. Otherwise, the OCS returns the policy counter status of all policy counter(s), which are available for this subscriber.
|
5817f2cb61f7e615e7879961cd761fa6
|
23.203
|
7.9.2 Intermediate Spending Limit Report Request
|
This clause describes the signalling flow for the H-PCRF to request the status of additional policy counters available at the OCS or to unsubscribe from spending limit reporting. If the H-PCRF provides the list of policy counter identifier(s), the OCS returns the policy counter status per policy counter identifier provided by the PCRF.
NOTE: In case the OCS returns the status of all available policy counters some of these may not be relevant for a policy decision, (e.g. those used in a policy decision only when roaming).
Figure 7.9.2: Intermediate Spending Limit Report Request
1. The H-PCRF determines that policy decisions depend on the status of additional policy counter(s) held at the OCS or that notifications of policy counter status changes for some policy counters are no longer required.
2. The H-PCRF sends an Intermediate Spending Limit Report Request, optionally including in the request an updated list of policy counter identifier(s).
3. The OCS sends the Intermediate Spending Limit Report Response that contains the policy counter status and optionally pending policy counter statuses and their activation times, per required policy counter identifier and stores or removes the H-PCRF's subscription to spending limit reporting by comparing the updated list with the existing H-PCRF subscriptions. If no policy counter identifier(s) was provided, the OCS returns the policy counter status, optionally including pending policy counter statuses and their activation times, for all policy counter(s), which are available for this subscriber and stores the H-PCRF's subscription to spending limit reports of all policy counters provided to the H-PCRF.
|
5817f2cb61f7e615e7879961cd761fa6
|
23.203
|
7.9.3 Final Spending Limit Report Request
|
This clause describes the signalling flow for the H-PCRF to cancel the subscriptions to status changes for the policy counters available at the OCS.
Figure 7.9.3: Final Spending Limit Report Request
1. The H-PCRF decides that notifications of policy counter status changes are no longer needed.
2. The H-PCRF sends a Final Spending Limit Report Request to the OCS to cancel the subscription to notifications of policy counter status changes from the OCS.
3. The OCS removes the H-PCRF's subscription to spending limit reporting and acknowledges the request by sending the Final Spending Limit Report Response to the H-PCRF.
|
5817f2cb61f7e615e7879961cd761fa6
|
23.203
|
7.9.4 Spending Limit Report
|
This clause describes the signalling flow for the OCS to notify the change of the status of the subscribed policy counters available at the OCS for that subscriber. Alternatively, the signalling flow can be used by the OCS to provide one or more pending statuses for a subscribed policy counter together with the time they have to be applied.
Figure 7.9.4: Spending Limit Report
1. The OCS detects that the status of a policy counter(s) has changed and the PCRF subscribed to notifications of changes in the status of this policy counter. Alternatively, the OCS may detect that a policy counter status will change at a future point in time and decides to instruct the PCRF to apply one or more pending statuses for a requested policy counter.
2. The OCS sends the policy counter status and optionally pending policy counter statuses and their activation times, for each policy counter that has changed and for which the H‑PCRF subscribed to spending limit reporting. Alternatively, the OCS sends one or more pending statuses for any of the subscribed policy counters together with the time they have to be applied.
NOTE: The values related to the status of the subscribed counter (e.g. valid, invalid or any other status) are not specified. The interpretation and actions related to the defined values are out of scope of 3GPP.
3. The H-PCRF acknowledges the Spending Limit Report and takes that information into account as input for a policy decision.
|
5817f2cb61f7e615e7879961cd761fa6
|
23.203
|
7.9.5 Sy Session Termination
|
This clause describes the signalling flow for the OCS to terminate the Sy session of a subscriber. This feature is optional.
NOTE 1: When the PCRF supports this procedure and a subscriber is removed from an OCS system, the existing Sy session of the subscriber can be terminated by this procedure.
Figure 7.9.5: Sy Session Termination
1. The OCS decides that the Sy session for a subscriber needs to be terminated.
2. The OCS sends the Sy Session Termination Request to H-PCRF to terminate the Sy session. The H-PCRF removes the Sy session context of the subscriber.
NOTE 2: The termination of the Sy session causes the H-PCRF to make the applicable policy decision and act accordingly, i.e. sessions on other interfaces such as the Rx or Gx interface will remain established, unless the policy decision causes their termination.
3. The H-PCRF acknowledges the termination of the Sy session of the subscriber by sending the Sy Session Termination Response.
|
5817f2cb61f7e615e7879961cd761fa6
|
23.203
|
7.10 Procedures over Np reference point
| |
5817f2cb61f7e615e7879961cd761fa6
|
23.203
|
7.10.1 Report RAN user plane congestion information to PCRF
|
This clause describes the signalling flow for reporting RUCI (RAN User Plane Congestion Information) from the RCAF to the PCRF. Any RUCI changes shall be reported by RCAF unless reporting restrictions apply.
Two types of messages are used on Np for transfer of congestion information from RCAF to PCRF:
- Non-aggregated RUCI report messages, which are sent on a per UE per APN basis using DRA routing. The IMSI and the APN can be used to route messages.
- Aggregated RUCI report messages, which are sent between an RCAF and PCRF and contain congestion information for multiple UEs. A logical PCRF id is allocated for these aggregate messages which determine the destination of the message.
The congestion reporting takes place as shown in Figure 7.10.1 below.
Figure 7.10.1: RUCI reporting from RCAF to PCRF
1. RCAF indicates congestion information for a given UE and APN in a RUCI report message. This message is routed by DRA to the appropriate PCRF based on IMSI and APN.
The RUCI report message includes the RUCI which is defined in clause 6.1.15.1.
Upon receiving the RUCI the PCRF stores the identity of the RCAF for the given UE if the RUCI indicates congestion. The PCRF makes a policy decision.
2. The PCRF allocates a logical PCRF id to identify the PCRF that is the Np destination for the given UE and APN for the RCAF when sending aggregate messages and reports the logical PCRF id in the RUCI acknowledgement.
The RCAF stores the logical PCRF id in the UE context for the given IMSI, APN combination.
3. Subsequent congestion information for the given UE can be sent as part of an Aggregated RUCI report message. Such a message can contain the congestion information for multiple UEs. These UEs can have different congestion levels associated with different eNB identifier or ECGI or SAI, which are indicated in the message. An aggregated RUCI report message is always destined to a single PCRF only and can be routed directly to that PCRF or via the DRA.
NOTE: How the RCAF decides about which information should be contained in a single aggregated RUCI report message out of the UEs with a given logical PCRF id is out of the scope of 3GPP specifications. e.g. the RCAF may aggregate information only for a given cell or eNB into a single message. Alternatively, the RCAF may wait for a configurable period of time to aggregate information from multiple cells or eNBs into a single message. The amount of RUCI updates may be limited by configuring a minimum time between RUCI updates in the RCAF (e.g. when only the identifier of the congested cell serving the UE has changed). This configuration is expected to take both the required accuracy as well as the acceptable signalling amount into account.
4. The Aggregated RUCI is acknowledged.
|
5817f2cb61f7e615e7879961cd761fa6
|
23.203
|
7.10.2 PCRF provided reporting restrictions
|
This clause describes the signalling flow for adding, updating or removing reporting restrictions for a given UE and APN. A pre-condition for this procedure is that the RCAF has already performed RUCI reporting for the given UE and APN. The PCRF stores the RCAF identity for the given UE when the RCAF performs RUCI reporting indicating congestion
This procedure may be triggered by the initial RUCI report message for the given UE at an RCAF, or by other events, e.g. change in the subscription. The procedure is shown in Figure 7.10.2 below.
Figure 7.10.2: PCRF provided reporting restrictions
1. PCRF sends a Modify UE context request to the RCAF of the given UE and APN using the stored identity of the RCAF, specifying the new reporting restrictions or the removal of the reporting restrictions. The RCAF stores the new reporting restrictions or removes the reporting restrictions accordingly.
2. The RCAF sends a Modify UE context response back to the PCRF to notify the PCRF about the success of the change in the reporting restrictions.
3. In case the RCAF already had reporting restrictions for the UE and the APN which are changed in step 2, this may trigger RUCI reporting as specified in clause 7.10.1. This occurs in case of a change from disabled reporting to enabled reporting, or if some reporting restrictions are lifted. The RCAF uses the RUCI report message to report congestion information to the PCRF if it is allowed by the change in the reporting restrictions.
4. The RUCI is acknowledged.
|
5817f2cb61f7e615e7879961cd761fa6
|
23.203
|
7.10.3 UE mobility between RCAFs
|
This clause describes the handling mobility of a UE from one RCAF to a different RCAF. The PCRF applies the rules described in clause 6.1.15.3.
The process is shown in Figure 7.10.3 below for the case when the UE is affected by congestion at RCAF2 after the UE was earlier affected by congestion at RCAF1.
Figure 7.10.3: UE mobility from RCAF1 to RCAF2 in case UE is affected by congestion at RCAF2 after the UE was earlier affected by congestion at RCAF1
1. RCAF1 reports RAN user plane congestion information (RUCI). The PCRF stores the identity of the current RCAF1 for a given UE when it receives the congestion information over Np that is different from no congestion.
2. The RUCI is acknowledged.
3. The UE moves to RCAF2 where it is affected by congestion. RCAF2 reports RAN user plane congestion information (RUCI). The PCRF stores the identity of the current RCAF2 for the given UE when it receives the congestion information over Np that is different from no congestion.
4. The RUCI is acknowledged.
5. Using on the previously stored identity of the old RCAF, the PCRF sends a Release context request message to RCAF1.
6. RCAF1 acknowledges this by sending the Release context response message to the PCRF. The RCAF releases the context corresponding to the given UE and given APN, including any reporting restrictions. This also implies that the RCAF does not indicate to the PCRF that the congestion state is over. In case of multiple PCRFs being in simultaneous use for a given UE, a Release context request message from a PCRF applies to the given Np connection only identified by the APN. The RCAF can completely release all context information for a given UE when it has released the context for each Np connection of the given UE.
|
5817f2cb61f7e615e7879961cd761fa6
|
23.203
|
7.11 Procedures over Nt reference point
| |
5817f2cb61f7e615e7879961cd761fa6
|
23.203
|
7.11.1 Negotiation for future background data transfer
|
This procedure enables the negotiation between the SCEF and the H-PCRF about the time window and the related conditions for future background data transfer (as described in clause 6.1.16). The interaction between the SCEF and the H-PCRF is not related to an IP-CAN session and the H-PCRF associates the information provided by the SCEF to the policies belonging to the ASP and stored in the SPR.
Figure 7.11.1-1: Negotiation for future background data transfer
1. Based on an AF request, the SCEF sends a Background data transfer request to the H-PCRF. The background data transfer request contains ASP identifier, the volume of data to be transferred per UE, the expected amount of UEs, the desired time window and optionally, network area information (e.g. list of cell ids, TAs/RAs).
NOTE 1: The SCEF does not provide any information about the identity of the UEs potentially involved in the future background data transfer.
NOTE 2: A 3rd party application server is typically not able to provide any specific network area information and if so, the AF request is for the whole operator network.
2. The H-PCRF requests from the SPR all existing transfer policies.
3. The SPR provides all existing transfer policies and corresponding network area information to the H-PCRF.
4. The H-PCRF determines, based on information provided by the AF and other available information (see clause 6.1.16) one or more transfer policies. A transfer policy consists of a recommended time window for the background data transfer, a reference to a charging rate for this time window and optionally a maximum aggregated bitrate.
NOTE 3: The maximum aggregated bitrate is not enforced in the network.
5. The H-PCRF sends a Background data transfer response to the SCEF with the possible transfer policies and a reference ID.
NOTE 4: The SCEF forwards the information to the AF. The AF stores the reference ID for the future transfer of AF session information related to this background data transfer via the Rx interface.
6.-7. If the SCEF receives more than one transfer policy, the AF selects one of them and send another Background data transfer request to inform the H-PCRF about the selected transfer policy. The H-PCRF sends a Background data transfer response to the SCEF to acknowledge the selection.
NOTE 5: If the SCEF receives only one transfer policy, the AF is not required to confirm.
8. The H-PCRF stores the reference ID together with the new transfer policy and the corresponding network area information in the SPR.
9. The SPR sends an acknowledgement to the H-PCRF.
|
5817f2cb61f7e615e7879961cd761fa6
|
23.203
|
7.12 Procedures for management of PFDs
| |
5817f2cb61f7e615e7879961cd761fa6
|
23.203
|
7.12.1 PFD Retrieval by the PCEF/TDF ("Pull mode")
|
This procedure enables the PCEF/TDF to retrieve PFDs for an Application Identifier from the PFDF when a PCC/ADC Rule with an Application Identifier is provisioned/activated and PFDs provisioned by the PFDF are not available at the PCEF/TDF.
In addition, this procedure enables the PCEF/TDF to retrieve PFDs from the PFDF when the caching timer for an Application Identifier elapses and a PCC/ADC Rule for this Application Identifier is still active.
The PCEF/TDF may retrieve PFDs for one or more Application Identifiers in the same Request. All PFDs related to an Application Identifier is provided in the response from the PFDF. The signalling flow of PFD Retrieval is depicted in Figure 7.12.1-1 as below.
Figure 7.12.1-1 PFD Retrieval by the PCEF/TDF
1. When one of the above mentioned conditions is met, PCEF/TDF shall fetch from the PFDF the PFDs for the Application Identifier(s) by sending Fetch PFD Request, in which the Application Identifier(s) is included.
2. The PFDF shall response with the list of Application Identifier and all associated PFDs in the Fetch PFD Response message. The PCEF/TDF shall bind the PFDs received from the PFDF to the respective Application Identifier.
|
5817f2cb61f7e615e7879961cd761fa6
|
23.203
|
7.12.2 Management of PFDs in the PCEF/TDF ("push mode")
|
This procedure enables the provisioning, modification or removal of PFDs associated with an application identifier in the PCEF/TDF via PFDF. Either the complete list of all PFDs of all application identifiers, the complete list of all PFDs of one or more application identifiers or a subset of PFDs for individual application identifiers may be managed. Each PFD of an application identifier is associated with a PFD id in case a subset of the PFD(s) associated with an application identifier can be provisioned, updated or removed. In case always the full set of PFD(s) for an application identifier is managed in each transaction, PFD ids do not need to be provided. NOTE 1: The prerequisite to provision or update PFDs is that the application identifier which the external entity provided is mapped into the application identifier that is included in the PCC/ADC Rule as described in TS 23.682 [42]. The interaction between the PFDF and the PCEF/TDF is not related to an IP-CAN session. The PFDF may decide to delay the distribution of PFDs to PCEFs/TDFs for some time to optimize the signalling load over the Gw/Gwn interface. If the PFDF received an Allowed Delay for a PFD, the PFDF shall distribute this PFD within the indicated time interval. Figure 7.12.2-1: Provisioning/update/removal of PFDs in the PCEF/TDF 1. The PFDF may provision, update or remove one, multiple, or all PFDs associated with an application identifier. The PFDF may manage PFDs for more than one application identifier at the same time. Alternatively, the PFDF may provision or remove the list of all PFDs associated with all application identifiers. 2. The PCEF/TDF binds (for provision or update) or unbinds (for removal) the PFDs to the application identifier received from the PFDF. The provisioning of PFDs associates new PFDs to an application identifier. The PFDF may also provide a PFD id for each PFD provided. The update of PFDs modifies existing PFDs associated to an application identifier. Either all PFDs of an application identifier are replaced, or a subset of the PFDs are replaced, where each PFD is identified by a PFD id. Partial modification of a PDF is not supported. The removal of PFDs removes some or all existing PFDs associated to an application identifier. In the case of removal of a subset of the PFD(s), each PFD is identified by a PFD id. The PCEF/TDF acknowledges the reception of the PFDs to the PFDF. Annex A (normative): Access specific aspects (3GPP) A.1 GPRS A.1.0 General The GPRS IP‑CAN employs, for an IP‑CAN session, the concept of PDP contexts in order to provide an information transmission path of defined capacity (QoS). For GPRS, the IP‑CAN bearer is the PDP context. Figure A.1: The GPRS IP‑CAN A.1.1 High level requirements A.1.1.1 General A.1.1.2 Charging related requirements It shall be possible for the charging system to select the applicable rate based on: - SGSN IP address that is used by the GTP control plane for the handling of control messages. - location with the granularity as specified for the credit re-authorization trigger Location change in clause A.1.3.1.3; - User CSG Information, including CSG ID, access mode and CSG membership indication; - RAT type. A.1.1.3 Policy control requirements IP‑CAN Bearer QoS control allows the PCC architecture to control the "Authorized QoS" of a PDP context. Criteria such as the QoS subscription information may be used together with service-based, subscription-based, or a predefined PCRF internal policies to derive the "Authorized QoS" of a PDP context. NOTE: If the PCRF provides authorized QoS for both the IP‑CAN bearer and PCC rule(s), the enforcement of authorized QoS of the individual PCC rules takes place first. A.1.1.4 QoS control For GPRS IP‑CANs it shall be possible to apply QoS control at APN-level. QoS control per APN allows the PCC architecture to control the authorized APN-AMBR to be enforced for the total bandwidth usage of non-GBR QCIs at the PCEF within the same APN. NOTE: For the enforcement of the APN-AMBR for all IP‑CAN sessions to the same APN, the IP‑CAN is required to select the same PCEF for all of them. A.1.2 Architecture model and reference points A.1.2.1 Reference points A.1.2.1.1 Gx reference point The Gx reference point enables the signalling of PCC rules, which govern the PCC behaviour and it supports the following GPRS-specific functions: - Indication of PDP context activation, modification and deactivation. A.1.2.2 Reference architecture In the GPRS IP‑CAN, the Bearer Binding and Event Reporting Function (BBERF) does not apply. A.1.3 Functional description A.1.3.1 Overall description A.1.3.1.1 Binding mechanism A.1.3.1.1.0 General As explained in clause 6.1.1, the binding mechanism is performed in three different steps: session binding, PCC rule authorization and bearer binding. Session binding has no GPRS specifics. For the authorization of a PCC rule with a GBR QCI the PCRF shall assign a GBR value within the limit supported by the serving network. NOTE: For the authorization of PCC Rules with the same QCI the PCRF may also check that aggregated GBR is within the limits supported by the serving network to minimize the risk of rejection of the bearer by the serving network. For the GPRS case bearer binding is performed by: - PCRF, when the selected operation mode is UE-only, see TS 23.060 [12], either due to PCRF decision or network/UE capability; - PCRF and PCEF (i.e. the PCRF performs the binding of the PCC rules for user controlled services while the PCEF performs the binding of the PCC rules for the network controlled services), when the selected operation mode is UE/NW. The bearer binding performed by the PCRF shall bind a PCC rule that is authorized for a TFT packet filter to the PDP context the TFT packet filter has been assigned by the UE if the PCC rule can be authorized for the QCI of the PDP context. If a new PDP context is established, the PCRF can also bind PCC rule(s) to the PDP context if the QCI of the PDP context is different from the QCI, the PCC rule(s) can be authorized for since the PCRF can modify the QCI of the new PDP context. The binding mechanism shall comply with the established traffic flow template (TFT) packet filters (for the whole IP‑CAN session). The bearer binding performed by the PCEF shall compare the PCC rule QoS parameters with the PDP context QoS parameters and bind a PCC rule: - to a candidate PDP context with a matching QoS class and Evolved ARP (if this is supported by the SGSN); - to a candidate PDP context with a matching QoS class and Evolved ARP (if this is supported by the SGSN) that, after modification of the bitrates, fulfils the PCC rule QoS demands; - to a new PDP context with a matching QoS class and Evolved ARP (if this is supported by the SGSN), if there is no suitable candidate PDP context present. The bearer binding mechanism associates the PCC rule with the PDP context to carry the service data flow. The association shall: - cause the downlink part of the service data flow to be directed to the PDP context in the association and - assume that the UE directs the uplink part of the service data flow to the PDP context in the association. Thus, the detection of the uplink part of a service data flow shall be active on the PDP context, which the downlink packets of the same service data flow is directed to. The detection of the uplink part of the service data flow may be active, in parallel, on any number of additional PDP contexts. A.1.3.1.1.1 Bearer binding mechanism allocated to the PCEF When the bearer binding mechanism is allocated to the PCEF, no per bearer information is required to be communicated over the Gx reference point. Once the PCRF has provided the PCC rule decisions at the IP‑CAN session establishment procedure, the PCRF shall provide further PCC rule decisions - using the PCRF initiated IP‑CAN Session Modification procedure; or - in response to an event report from the PCEF (the GW (PCEF) initiated IP‑CAN Session Modification). The bearer binding function shall not combine PCC rules with different ARP values onto the same PDP context. NOTE: If Evolved ARP is not supported by the SGSN then this enables a modification of the PDP context ARP without impacting the bearer binding after relocation to a SGSN that supports Evolved ARP. A.1.3.1.1.2 Bearer binding mechanism allocated to the PCRF If a PDP context is established/modified in order to successfully perform the bearer binding the PCRF will set the PCC rule as binding-pending status until the PCEF reports the establishment or modification of a PDP context that fulfils the PCC rule demands or the PCC rule is removed. The following particularities apply when the bearer binding mechanism is allocated to the PCRF: - The PCEF - shall include a bearer reference in all requests for PCC decisions; - shall report bearer QoS class identifier and the associated bitrates for new/modified PDP contexts; - shall report the TFT filter status for new PDP contexts and for modified TFTs; - shall report the deactivation of a PDP context - The PCRF - shall provide the bearer reference for the binding result when activating a PCC rule; - shall arm the GPRS-specific IP‑CAN event trigger "PDP context activity". - shall arm the event trigger "traffic mapping information change". NOTE: For the above case, the allocation of the bearer binding mechanism to the PCRF facilitates the migration from Rel-6 products to Rel-7 products. The allocation of the binding mechanism may be re-evaluated in future releases. When the PCRF performs the bearer binding the ARP information in the PCC rule shall be ignored unless the SGSN has indicated support for Evolved ARP. A.1.3.1.2 Reporting A container may be closed and a new container opened by the triggering of event triggers. A.1.3.1.3 Credit management For GPRS the PCEF shall initiate one credit management session for each PDP context. For GPRS the credit re-authorisation triggers in table A.1-1 shall apply in addition to the ones in table 6.1. They are applicable both in case of PCEF and in case of TDF. Table A.1-1: GPRS specific credit re-authorization triggers Credit re-authorization trigger Description SGSN change The UE has moved to a new SGSN. RAT type change. The characteristics of the air interface, communicated as the radio access type, have changed. Location change (routeing area) The routeing area of the UE has changed. Location change (CGI/SAI) The CGI/SAI of the UE has changed. User CSG Information change in CSG cell User CSG Information has changed when the UE enters/leaves/accesses via a CSG cell User CSG Information change in subscribed hybrid cell User CSG Information has changed when the UE enters/leaves/accesses via a hybrid cell in which the subscriber is a CSG member User CSG Information change in un-subscribed hybrid cell (see note) User CSG Information has changed when the UE enters/leaves/accesses via a hybrid cell in which the subscriber is not a CSG member NOTE: Due to the increased signalling load, such reporting should be applied for a limited number of subscribers only. If the Location change trigger for CGI / SAI or RAI is armed, the GGSN should request the SGSN to report any changes in location to the level indicated by the trigger according to the procedures described in TS 23.060 [12]. If credit re-authorization triggers and event triggers require different levels of reporting of location change for different PDP contexts for a single IP-CAN session, the SGSN reports location changes to the highest level of detail required. However, the GGSN should not trigger a credit re-authorization if the report received is more detailed than requested by the OCS. If the User CSG Information change in CSG cell trigger is armed, the GGSN should request the SGSN to report any changes in user CSG information when the UE enters/leaves/accesses via a CSG cell. If the User CSG Information change in subscribed hybrid cell trigger is armed, the GGSN should request the SGSN to report any changes in user CSG information when the UE enters/leaves/accesses via a hybrid cell in which the subscriber is a CSG member. If the User CSG Information change in un-subscribed hybrid cell trigger is armed, the GGSN should request the SGSN to report any changes in user CSG information when the UE enters/leaves/accesses via a hybrid cell in which the subscriber is not a CSG member. If credit re-authorization triggers, event triggers and IP-CAN session related policy information require different levels of reporting of User CSG information for a single IP-CAN session, then the User CSG information to be requested from the SGSN should be changed to the highest level of detail required. Change of UE presence in Presence Reporting Area is not applicable for GPRS IP-CAN. A.1.3.1.4 Event Triggers For GPRS the event triggers in table A.2 shall apply in addition to the ones in table 6.2 at the PCEF upon the request of the PCRF. NOTE: The request from the PCRF can be triggered by configured policy, or a request received from the TDF. In case of TDF, this may be a result of credit re-authorization trigger received by the TDF from the OCS. Table A.2: GPRS specific event triggers Event trigger Description SGSN change The UE has moved to a new SGSN. RAT type change. The characteristics of the air interface, communicated as the radio access type, have changed. PDP Context Activity The GGSN has received a request for a PDP context activation, modification or deactivation. Note 1. Location change (routeing area) The routeing area of the UE has changed. Location change (CGI/SAI) The CGI/SAI of the UE has changed. Subscribed APN-AMBR change The subscribed APN-AMBR has changed. User CSG Information change in CSG cell User CSG Information has changed when the UE enters/leaves/accesses via a CSG cell. (Note 2) User CSG Information change in subscribed hybrid cell User CSG Information has changed when the UE enters/leaves/accesses via a hybrid cell in which the subscriber is a CSG member. (Note 2) User CSG Information change in un-subscribed hybrid cell (see note) User CSG Information has changed when the UE enters/leaves/accesses via a hybrid cell in which the subscriber is not a CSG member. (Note 2) 3GPP PS Data Off status change The PCEF reports when the 3GPP PS Data Off status changes. NOTE 1: Available only when the bearer binding mechanism is allocated to the PCRF. NOTE 2: Due to the increased signalling load, such reporting should be applied to a limited number of subscribers only. If the Location change trigger is armed, the GGSN should request the SGSN to report any changes in location to the level indicated by the trigger according to the procedures described in TS 23.060 [12]. If credit-authorization triggers and event triggers require different levels of reporting of location change for different PDP contexts for a single UE, the SGSN reports location changes to the highest level of detail required. However, the GGSN should not trigger a request for PCC rules if the report received is more detailed than requested by the PCRF. For GPRS, the traffic mapping information is represented by the TFT information. For GPRS, the loss/recovery of transmission resources is indicated by a PDP context modification changing the 'Maximum bitrate' UMTS QoS parameter to/from 0 kbit/s (as described in the PDP context preservation procedure in TS 23.060 [12]). The User Location Report in the Access Network Information Reporting contains the CGI/SAI and when the PDP context is deactivated, information on when the UE was last known to be in that location. If the User CSG Information change in CSG cell was provided as event trigger, the GGSN should request the SGSN to report any changes in user CSG information when the UE enters/leaves/accesses via a CSG cell. If the User CSG Information change in subscribed hybrid cell was provided as event trigger, the GGSN should request the SGSN to report any changes in user CSG information when the UE enters/leaves/accesses via a hybrid cell in which the subscriber is a CSG member. If the User CSG Information change in un-subscribed hybrid cell was provided as event trigger, the GGSN should request the SGSN to report any changes in user CSG information when the UE enters/leaves/accesses via a hybrid cell in which the subscriber is not a CSG member. If credit re-authorization triggers, event triggers and IP-CAN session related policy information require different levels of reporting of User CSG information for a single IP-CAN session, then the User CSG information to be requested from the SGSN should be changed to the highest level of detail required. Change of UE presence in Presence Reporting Area is not applicable for GPRS IP-CAN. A.1.3.1.5 Policy Control For GPRS the AF instruction to report changes of the IP‑CAN bearer level information Type of IP‑CAN shall also result in a reporting of RAT type changes, even if the IP‑CAN type is unchanged. A.1.3.2 Functional entities A.1.3.2.1 Policy Control and Charging Rules Function (PCRF) A.1.3.2.1.0 General The PCRF shall upon indication of PCC rule removal due to PS to CS handover notify the AF that the associated flows are no longer served by the PS-domain due to PS to CS handover. A.1.3.2.1.1 Input for PCC decisions The PCRF shall accept any of the following input which the PCEF may provide, specific for GPRS, as a basis for decisions on PCC rule operations. The following information represents GPRS specific values of the ones listed in clause 6.2.1.1: - Subscriber Identifier in the form of IMSI, MSISDN; - A PDN identifier in the form of APN; - A PLMN identifier in the form of SGSN Mobile Country Code and Mobile Network Code; - Type of IP‑CAN set to GPRS; - IP‑CAN bearer attributes in the form of: - Requested QoS, for a PDP context; - TFT, to enable the identification of the corresponding PDP Context; - Location of the subscriber in the form of CGI/SAI or RAI. The following information is in addition to the ones listed in clause 6.2.1.1: - RAT type. - Subscribed APN-AMBR. The SPR may provide the following information for a subscriber (in addition to the information in clause 6.2.1.1) connecting to a specific PDN: - Authorized APN-AMBR. The Authorized APN-AMBR is derived by the PCRF from SPR interaction, according to operator policy. A.1.3.2.2 Policy and Charging Enforcement Function (PCEF) A.1.3.2.2.1 General This functional entity is located in the GGSN. The GGSN provides the GPRS-specific bearer QoS handling. The PCEF shall contact the PCRF based on PCRF address information that shall be configured for the access point name (APN) together with the IMSI or MSISDN (if needed). The PCEF shall maintain a 1:1 mapping from the GPRS QoS Class Identifier to a UMTS QoS profile and vice versa. Each GPRS QoS Class Identifier (QCI) parameter value has a 1:1 mapping to a set of QoS parameters defined for GPRS, TS 23.107 [14]. A recommended mapping is listed in table A.3. Table A.3: Recommended mapping for GPRS QoS Class Identifier to/from Release 99 UMTS QoS parameters GPRS UMTS QoS parameters QoS Class Identifier value Traffic Class THP Signalling Indication Source Statistics Descriptor 1 Conversational n/a n/a speech (NOTE 1) 2 Conversational n/a n/a unknown 3 Streaming n/a n/a speech (NOTE 1) 4 Streaming n/a n/a unknown 5 Interactive 1 Yes n/a 6 Interactive 1 No n/a 7 Interactive 2 No n/a 8 Interactive 3 No n/a 9 Background n/a n/a n/a NOTE 1: The operator's configuration should reserve QCI values that map to "speech" for service data flows consisting of speech (and the associated RTCP) only. NOTE 2: This table defines the mapping for GPRS QCI to/from UMTS QoS parameters for pre-Release 8 GPRS. The characteristics of GPRS QCIs are independent from the standardized QCI characteristics for EPS. The PCEF determines Release 97/Release 98 attributes from Release 99 attributes according to TS 23.107 [14]. The remaining UMTS QoS parameters are subject to operator's policies and either provisioned in the Create PDP Context Request or locally defined in GGSN. NOTE 3: Any change of the ARP parameter by the PCEF may get overwritten by the SGSN due to subscription enforcement unless the SGSN has indicated support for Evolved ARP. For each PDP context, the PCEF shall accept information during bearer establishment and modification relating to: - The user and terminal (e.g. MSISDN, IMEISV); - Bearer characteristics (e.g. QoS negotiated, APN, IM CN Subsystem signalling flag); - Network related information (e.g. MCC and MNC). The PCEF shall use this information in the OCS request/reporting or request for PCC rules. A GGSN may provide more than one APN for access to the same PDN. It should be possible to enable or disable PCC functionality for each APN, independent from the other APNs for access to the same PDN. Once the PCC functionality is disabled, regular GPRS charging and policy methods would be applied, i.e. no PCRF interaction would occur. For each PDP context, there shall be a separate OCS request/OFCS reporting, so this allows the OCS and offline charging system to apply different rating depending on the PDP context. The GGSN shall report the service data flow based charging data on a per PDP context basis. The GGSN shall be able to request the SGSN to provide reports of changes in CGI/SAI/RAI of a UE as directed by the credit re-authorization triggers and/or event triggers. The PCEF enforces QoS Policies as indicated by the PCRF in accordance to what is stated in clause 6.2.2.1 with the following additions: - Authorized APN-AMBR enforcement. The PCEF shall enforce the authorized APN-AMBR received via the Gx interface for the total bandwidth usage of non-GBR QCI for the APN. Only the GBR per bearer is used for resource reservation (e.g. admission control in the RAN). The MBR (per PCC rule / per bearer) and the authorized APN-AMBR are used for rate policing. When the GGSN is connected to a SGSN that does not support the Evolved ARP, the GGSN shall map the Evolved ARP to Rel‑99 ARP parameter value as specified in Annex E of TS 23.401 [17]. A.1.3.2.2.2 Service data flow detection For uplink traffic, in the case of GPRS, all the uplink parts of service data flows templates, which are associated with the PDP context are candidates for matching in the detection process. NOTE: Service data flow templates, which are not associated with the PDP context the packet was received, are not candidates for matching (dashed in the figure). A.1.3.2.2.3 Packet Routeing and Transfer Function The PCEF performs the packet routeing and transfer functions as specified in TS 23.060 [12], with the differences specified in this clause. For the PDP address of an UE, the PCEF routes downlink packets to the different PDP contexts based on the downlink parts of the service data flow templates, in the active PCC rules and their routeing associations to the PDP contexts. The association between an active PCC rule and a PDP context shall correspond to the downlink TFT received from the UE. Each active PCC rule shall have a single routeing association to a PDP context. Upon reception of a packet, the PCEF evaluates the downlink part of the service data flow templates of the PCC rules activated for the PDP address in order of precedence to find a match. When the first match is found, the packet is tunnelled to the SGSN via the PDP context, for which the PCC rule has the routeing association. If no match is found, the PCEF shall silently discard the packet. The UE shall define TFTs that enable successful binding at the PCRF for service data flows requiring a binding to occur. For each uplink packet, the UE should choose the PDP context that is used for the downlink direction of the same service data flow, as declared in the TFT information. The PCEF shall only apply the uplink parts of the service data flow templates of the PCC rules, which are associated with the same PDP context as the uplink packet arrived on. The packet filters, to be applied on dedicated signalling PDP contexts, shall form PCC rules, which shall be granted higher precedence than any other PCC rule and be active on the dedicated signalling context. A.1.3.2.2.4 Measurement The details of measurement are specified in TS 32.251 [9]. A.1.3.2.3 Application Function (AF) For GPRS the AF instruction to report changes of the IP‑CAN bearer level information Type of IP‑CAN will also result in a reporting of RAT type changes, even if the IP‑CAN type is unchanged. The AF instructions to report loss of transmission resources will result in a notification from the PCRF that may include an indication that the transmission resources are lost due to PS to CS handover. NOTE: The AF action up to notification of termination of transmission resources due to PS to CS handover is application specific. IMS interprets that the PS to CS handover notification as SRVCC. A.1.3.3 Policy and charging control rule A.1.3.3.1 General Void. A.1.3.3.2 Policy and charging control rule operations The PCRF associates, at activation, a PCC rule with a PDP context at the PCEF. A.1.3.4 IP‑CAN bearer and IP‑CAN session related policy information For GPRS the IP-CAN bearer and IP-CAN session related policy information in table A.4 shall apply in addition to the ones in table 6.4. Table A.4: PCC related IP-CAN bearer and IP‑CAN session related policy information Attribute Description PCRF permitted to modify the attribute Scope User CSG Information change in CSG cell Defines whether to report User CSG Information change when the UE enters/leaves/accesses via a CSG cell. Yes IP‑CAN session User CSG Information change in subscribed hybrid cell Defines whether to report User CSG Information change when the UE enters/leaves/accesses via a hybrid cell in which the subscriber is a CSG member. Yes IP‑CAN session User CSG Information change in un-subscribed hybrid cell (see note) Defines whether to report User CSG Information change when the UE enters/leaves/accesses via a hybrid cell in which the subscriber is not a CSG member. Yes IP‑CAN session NOTE: Due to the increased signalling load, such reporting should be applied for a limited number of subscribers only. If the User CSG Information change in CSG cell was provided under IP-CAN session related policy information, the GGSN should request the Serving Node to report any changes in user CSG information when the UE enters/leaves/accesses via a CSG cell. If the User CSG Information change in subscribed hybrid cell was provided under IP-CAN session related policy information, the GGSN should request the Serving Node to report any changes in user CSG information when the UE enters/leaves/accesses via a hybrid cell in which the subscriber is a CSG member. If the User CSG Information change in un-subscribed hybrid cell was provided under IP-CAN session related policy information, the GGSN should request the Serving Node to report any changes in user CSG information when the UE enters/leaves/accesses via a hybrid cell in which the subscriber is not a CSG member. If credit re-authorization triggers, event triggers and IP-CAN session related policy information require different levels of reporting of User CSG information for a single IP-CAN session, then the User CSG information to be requested from the Serving Node should be changed to the highest level of detail required. The reporting of User CSG information to the OFCS shall be done on the level of detail as requested by the PCRF within IP-CAN session related policy information and the reporting of User CSG information to the OCS shall be done on the level of detail as requested by the OCS re-authorization triggers. The authorized QoS per bearer (UE-initiated IP‑CAN bearer activation/modification) and the authorized MBR per QCI (network initiated IP‑CAN bearer activation/modification) shall be mapped by the PCEF to the GBR and MBR of the PDP context as described in clause 6.2.2.4. The mapping of the QCI to the UMTS QoS profile parameters is defined in clause A.1.3.2.2.1. A.1.3.4a TDF session related policy information For TDF session related policy information in table A.4a shall apply in addition to the ones in table 6.4a. Table A.4a: TDF session related policy information Attribute Description PCRF permitted to modify the attribute Scope User CSG Information change in CSG cell Defines whether to report User CSG Information change when the UE enters/leaves/accesses via a CSG cell. Yes TDF session User CSG Information change in subscribed hybrid cell Defines whether to report User CSG Information change when the UE enters/leaves/accesses via a hybrid cell in which the subscriber is a CSG member. Yes TDF session User CSG Information change in un-subscribed hybrid cell (see note) Defines whether to report User CSG Information change when the UE enters/leaves/accesses via a hybrid cell in which the subscriber is not a CSG member. Yes TDF session NOTE: Due to the increased signalling load, such reporting should be applied for a limited number of subscribers only. The reporting of User CSG information to the OFCS shall be done on the level of detail as requested by the PCRF within TDF session related policy information and the reporting of User CSG information to the OCS shall be done on the level of detail as requested by the OCS re-authorization triggers. NOTE: PCRF is responsible for setting the event triggers to the highest level of detail required in case different levels of User CSG information reporting to the charging domain are required for a single TDF session. A.1.3.5 Void A.1.4 PCC Procedures and flows A.1.4.1 Introduction For GPRS, the GW (PCEF) is the GGSN. The IP‑CAN bearer is the PDP context and the IP‑CAN Session is established by the Create PDP Context message. The IP‑CAN Session is terminated when the last PDP Context of the specific IP address is deleted and the IP Address is released. A.1.4.2 IP‑CAN Session Establishment The IP‑CAN session establishment procedure (described in clause 7.2) is triggered at the GGSN by receiving a Create PDP Context Request message for the first PDP Context that is created for a new IP Address. The successful procedure results in an establishment of a UE IP Address and a PDP Context for the UE. The Create PDP Context Response message, indicating that a new PDP context is created, is sent to the SGSN. The response may include any changes in QoS according to bearer binding and policy enforcement. During the PDP context activation procedure, it shall be possible to forward the network capability of reporting of changes in CGI/SAI/RAI to the PCRF. The PCRF also includes the Authorized APN-AMBR in the IP‑CAN Session Establishment Ack. A.1.4.3 IP‑CAN Session Termination A.1.4.3.1 UE initiated IP‑CAN Session termination The UE initiated IP‑CAN Session termination procedure (described in clause 7.3.1) is triggered at the GGSN by receiving a Delete PDP Context request message if this is the deletion of the last PDP Context for the IP Address or the Teardown Indicator in the Delete PDP Context Request indicates that all PDP contexts that share the same IP address should be deactivated. All PDP Contexts in the IP‑CAN Session are deleted in the GGSN. The IP Address of the UE is released. The Delete PDP Context Response message, indicating that the PDP context(s) is deleted, is sent to the SGSN. A.1.4.3.2 GW initiated IP‑CAN Session termination The GW initiated IP‑CAN Session termination procedure (described in clause 7.3.2) is triggered if the GGSN detects that the IP‑CAN Session shall be terminated. The Delete PDP Context request message is sent by the GGSN to the SGSN. This may be the deletion of the last PDP Context for the IP Address. If not, the GGSN shall set the Teardown Indicator in the Delete PDP Context Request message to indicate that all PDP contexts that share that same IP address shall also be deactivated. All PDP Contexts in the IP‑CAN Session are deleted. The IP Address of the UE is released. The Delete PDP Context Response, indicating that the PDP context(s) is deleted, is received from the SGSN. A.1.4.4 IP‑CAN Session Modification A.1.4.4.1 IP‑CAN Session Modification; GW (PCEF) initiated The GW (PCEF) initiated IP‑CAN Session modification procedure (described in clause 7.4.1) is triggered at the GGSN by receiving one of the following messages: - Create PDP Context Request message; - Update PDP Context Request message; - Delete PDP Context Request message; - a Change Notification message (indicating the new CGI, SAI or RAI) – see TS 23.060 [12]. In case of a Create PDP Context Request message, the modification of the IP‑CAN Session is the addition of a new PDP Context to the IP‑CAN Session. The new PDP Context is added with specific QoS requirements and traffic mapping information (TFT). A Create PDP Context Response message, indicating that a new PDP context is created, is sent to the SGSN. The response may include any changes in QoS according to bearer binding and policy enforcement. In case of an Update PDP Context Request, a PDP Context in the IP‑CAN Session is modified. The modification may include modifying the QoS and/or the traffic mapping information. The Update PDP Context Response message, indicating that a PDP context is modified, is sent to the SGSN. The response may include any changes in QoS according to bearer binding and policy enforcement. In case of a Delete PDP Context Request message, a PDP Context in the IP‑CAN Session is deleted. The Delete PDP Context Response message, indicating that a PDP context is deleted, is sent to the SGSN. .If the PS to CS handover indicator is set in a Delete PDP context request message , the PCEF reports termination of transmission resources for associated PCC Rules due to PS to CS handover. A Change Notification message indicating a change in CGI / SAI or RAI information is received when there are only changes regarding the current location of the UE. A change in CGI / SAI or RAI may also be notified within other session management messages. The PCRF may provide the Authorized APN-AMBR in the Acknowledgement of the IP‑CAN Session Modification to the GW (in addition to the parameters in clause 7.4.1). Based on operator policy the PCRF may re-authorize MBR/APN-AMBR. A.1.4.4.2 IP‑CAN Session Modification; PCRF initiated The PCRF initiated IP‑CAN Session modification procedure (described in clause 7.4.2) may result in a GGSN initiated PDP Context Modification or Deactivation or a Network Requested secondary PDP Context Activation. If a PDP Context in the IP‑CAN Session needs to be modified, the GGSN sends an Update PDP Context Request message. The modification may include modifying the QoS negotiated, negotiated Evolved ARP or the required CGI/SAI/RAI change reporting. The Update PDP Context Response message, indicating that a PDP context is modified, will be received from the SGSN. If a PDP Context in the IP‑CAN Session needs to be deleted, the GGSN sends a Delete PDP Context Request message. The Delete PDP Context Response message will be received from the SGSN. If the PCEF bearer binding yields that a new PDP context is required, the PCEF shall initiate the Network Requested secondary PDP Context Activation procedure. NOTE: If online charging is applicable, with PCEF bearer binding and a new PDP Context is required, the PCEF may not have all the information (e.g. NSAPI and negotiated QoS) associated with that PDP context for the credit authorisation until the activation procedure is complete and therefore a second credit authorisation may be necessary to provide the remaining information. The PCRF may provide the Authorized APN-AMBR in the Policy and Charging Rule Provision to the GW (in addition to the parameters in clause 7.4.2). A.2 Void A.3 Void A.4 3GPP Accesses (GERAN/UTRAN/E-UTRAN) - GTP-based EPC A.4.0 General For 3GPP Access (GTP-based), architecture details are described in TS 23.401 [17] and in TS 23.060 [12]. Figure A.1: The 3GPP EPS IP‑CAN (GTP-based) A.4.1 High Level Requirements A.4.1.1 Charging related requirements It shall be possible for the charging system to select the applicable rate based on: - Location with the granularity as specified for the credit re-authorization trigger Location change in clause A.4.3.1.1; - User CSG Information, including CSG ID, access mode and CSG membership indication; - RAT type. A.4.1.2 QoS control For 3GPP Access (GTP based) it shall be possible to apply QoS control at APN-level. QoS control per APN allows the PCC architecture to control the authorized APN-AMBR to be enforced for the total bandwidth usage of non-GBR QCIs at the PCEF within the same APN. NOTE 1: For the enforcement of the APN-AMBR for all IP‑CAN sessions to the same APN, the IP‑CAN is required to select the same PCEF for all of them. If there is a QCI assigned to a PCC/QoS rule which is not supported by all RATs of the IP-CAN, the PCRF shall subscribe to the event trigger 'RAT change'. At inter-RAT mobility, the PCRF will be informed and shall then modify those PCC/QoS rules in the PCEF/BBERF to align their QCI values with those supported by the current RAT. NOTE 2: It is assumed that the PCRF is configured with the same mapping rules as the MME. NOTE 3: Subscription to RAT changes ensure that the PCRF is invoked in case the UE moves to a RAT not supporting the assigned QCI in the PCC Rules as well as in case the UE moves back to a RAT supporting the originally assigned QCI. In the latter case, the PCRF can then modify the QCI in the PCC Rules back to the originally assigned value. It shall be possible for the PCRF to authorize the QCI and ARP of the default EPS bearer to be enforced by the PCEF immediately and/or at a specific point in time by providing the default EPS bearer related policy information as defined in clause A.4.3.4. A.4.2 Architectural Model and Reference Points A.4.2.1 Reference architecture In the 3GPP Access (GTP-based) architecture, see TS 23.401 [17] and in TS 23.060 [12], - the Policy and Charging Enforcement Function (PCEF) is allocated to the PDN GW; - the Bearer Binding and Event Reporting Function (BBERF) does not apply. A.4.3 Functional Description A.4.3.1 Overall description A.4.3.1.1 Credit management For EPS the credit re-authorisation triggers in table A.4.3-1 shall apply in addition to the ones in table 6.1. They are applicable both in case of PCEF and in case of TDF. Table A.4.3-1: EPS specific credit re-authorization triggers Credit re-authorization trigger Description SGSN change The UE has moved to a new SGSN. (Note 2) Serving GW change The UE has moved to a new Serving GW. (Note 1) (Note 2) RAT type change. The characteristics of the air interface, communicated as the radio access type, have changed. Location change (routeing area) The routeing area of the UE has changed. (Note 2) Location change (tracking area) The tracking area of the UE has changed. (Note 1) Location change (ECGI) The ECGI of the UE has changed.(Note 1) Location change (CGI/SAI) The CGI/SAI of the UE has changed.(Note 2) Location change (eNodeB ID) The eNodeB ID of the UE has changed. (Note 1) Change of UE presence in Presence Reporting Area The UE is entering/leaving a Presence Reporting Area User CSG Information change in CSG cell User CSG Information has changed when the UE enters/leaves/accesses via a CSG cell User CSG Information change in subscribed hybrid cell User CSG Information has changed when the UE enters/leaves/accesses via a hybrid cell in which the subscriber is a CSG member User CSG Information change in un-subscribed hybrid cell (see NOTE 3 ) User CSG Information has changed when the UE enters/leaves/accesses via a hybrid cell in which the subscriber is not a CSG member NOTE 1: These triggers are used for E‑UTRAN access. NOTE 2: These triggers are used for GERAN/UTRAN accesses. NOTE 3: Due to the increased signalling load, such reporting should be applied to a limited number of subscribers only. If the Location change trigger for GERAN/UTRAN or E‑UTRAN is armed, the PDN GW should request the Serving Nodes (then SGSN or MME specifically) to report any changes in location to the level indicated by the trigger according to the procedures described in TS 23.060 [12] or TS 23.401 [17]. The OCS determines at credit management session establishment/modification whether the UE is located in an access type that supports reporting changes of UE presence in Presence Reporting Area. This determination relies on local configuration and may rely on whether the UE is served by a Gn-SGSN (where this reporting is not defined) or by a S4-SGSN. The "SGSN change" trigger and the "Serving GW change" trigger may be used to determine whether the UE is served by a S4-SGSN. If the access type supports it, the OCS may subscribe to Change of UE presence in Presence Reporting Area at any time during the life time of the credit management session. If the Change of UE Presence in Presence Reporting Area trigger is armed, the PDN GW should request the Serving Nodes (the SGSN or MME) to report any changes in the UE presence in Presence Reporting Area according to the procedures described in TS 23.060 [12] or TS 23.401 [17]. If the User CSG Information change in CSG cell trigger is armed, the PDN GW should request the Serving Nodes (then SGSN or MME specifically) to report any changes in user CSG information when the UE enters/leaves/accesses via a CSG cell. If the User CSG Information change in subscribed hybrid cell trigger is armed, the PDN GW should request the Serving Nodes (then SGSN or MME specifically) to report any changes in user CSG information when the UE enters/leaves/accesses via a hybrid cell in which the subscriber is a CSG member. If the User CSG Information change in un-subscribed hybrid cell trigger is armed, the PDN GW should request the Serving Nodes (then SGSN or MME specifically) to report any changes in user CSG information when the UE enters/leaves/accesses via a hybrid cell in which the subscriber is not a CSG member. If credit re-authorization triggers, event triggers and IP-CAN session related policy information require different levels of reporting of User CSG information for a single IP-CAN session, then the User CSG information to be requested from the Serving Nodes should be changed to the highest level of detail required. A.4.3.1.2 Event Triggers For EPS the event triggers in table A.4.3-2 shall apply in addition to the ones in table 6.2 at the PCEF upon the request of the PCRF. NOTE: The request from the PCRF can be triggered by configured policy, or a request received from the TDF. In case of TDF, this may be a result of credit re-authorization trigger received by the TDF from the OCS. Table A.4.3-2: EPS specific event triggers Event trigger Description Reported from Condition for reporting SGSN change The UE has moved to a new SGSN. (Note 2) PCEF PCRF Serving GW change The UE has moved to a new Serving GW. (Note 1) (Note 2) PCEF PCRF RAT type change. The characteristics of the air interface, communicated as the radio access type, have changed. PCEF PCRF Location change (routeing area) The routeing area of the UE has changed. PCEF PCRF Location change (tracking area) The tracking area of the UE has changed. (Note 1) PCEF PCRF Location change (ECGI) The ECGI of the UE has changed.(Note 1) PCEF PCRF Location change (CGI/SAI) The CGI/SAI of the UE has changed.(Note 2) PCEF PCRF Location change (eNodeB ID) The eNodeB ID of the UE has changed. (Note 1) PCEF PCRF Change of UE presence in Presence Reporting Area The UE is entering/leaving a Presence Reporting Area PCEF PCRF Subscribed APN-AMBR change The subscribed APN-AMBR has changed PCEF Always set EPS Subscribed QoS change The QoS of the default EPS bearer has changed. PCEF Always set User CSG Information change in CSG cell User CSG Information has changed when the UE enters/leaves/accesses via a CSG cell. (Note 3) PCEF PCRF User CSG Information change in subscribed hybrid cell User CSG Information has changed when the UE enters/leaves/accesses via a hybrid cell in which the subscriber is a CSG member. (Note 3) PCEF PCRF User CSG Information change in un-subscribed hybrid cell (see note) User CSG Information has changed when the UE enters/leaves/accesses via a hybrid cell in which the subscriber is not a CSG member. (Note 3) PCEF PCRF 3GPP PS Data Off status change The PCEF reports when the 3GPP PS Data Off status changes PCEF Always set NOTE 1: These triggers are used for E‑UTRAN access. NOTE 2: These triggers are used for GERAN/UTRAN accesses. NOTE 3: Due to the increased signalling load, such reporting should be applied to a limited number of subscribers only. If the Location change trigger is armed, the PDN GW should request the Serving Nodes (then SGSN or MME specifically) to report any changes in location to the level indicated by the trigger according to the procedures described in TS 23.060 [12] or TS 23.401 [17]. The PCRF determines at IP-CAN session establishment/modification whether the UE is located in an access type that supports reporting changes of UE presence in Presence Reporting Area. This determination relies on local configuration and may rely on whether the UE is served by a Gn-SGSN (where this reporting is not defined) or by a S4-SGSN. The "SGSN change" trigger and the "Serving GW change" trigger may be used to determine whether the UE is served by a S4-SGSN. If the access type supports it, the PCRF may subscribe to Change of UE presence in Presence Reporting Area at any time during the life time of the IP-CAN session. If the Change of UE Presence in Presence Reporting Area trigger is armed, the PDN GW should request the Serving Nodes (SGSN or MME) to report any changes in the UE presence in Presence Reporting Area according to the procedures described in TS 23.060 [12] or TS 23.401 [17]. The User Location Report in the Access Network Information Reporting contains the ECGI and when the bearer is deactivated, information on when the UE was last known to be in that location. If the User CSG Information change in CSG cell was provided as event trigger, the PDN GW should request the Serving Nodes to report any changes in user CSG information when the UE enters/leaves/accesses via a CSG cell. If the User CSG Information change in subscribed hybrid cell was provided as event trigger, the PDN GW should request the Serving Nodes to report any changes in user CSG information when the UE enters/leaves/accesses via a hybrid cell in which the subscriber is a CSG member. If the User CSG Information change in un-subscribed hybrid cell was provided as event trigger, the PDN GW should request the Serving Nodes to report any changes in user CSG information when the UE enters/leaves/accesses via a hybrid cell in which the subscriber is not a CSG member. If credit re-authorization triggers, event triggers and IP-CAN session related policy information require different levels of reporting of User CSG information for a single IP-CAN session, then the User CSG information to be requested from the Serving Nodes should be changed to the highest level of detail required. A.4.3.1.3 Binding mechanism As explained in clause 6.1.1, the binding mechanism is performed in three steps: Session Binding, PCC Rule authorization and Bearer Binding. Session Binding has no 3GPP Access (GTP-based) specifics. For the authorization of a PCC rule with a GBR QCI the PCRF shall assign a GBR value within the limit supported by the serving network. NOTE 1: For the authorization of PCC Rules with the same QCI the PCRF may also check that aggregated GBR is within the limits supported by the serving network to minimize the risk of rejection of the bearer by the serving network. For the 3GPP Access (GTP-based) the Bearer Binding is performed by the PCEF. For GERAN/UTRAN in UE-only mode the Bearer Binding mechanism is restricted by the UE provided binding between a SDF and a bearer for UE initiated resource requests. A PCEF supporting the Bind to Default Bearer PCC rule attribute shall bind a dynamic PCC rule with this attribute to the default bearer instead of using the bearer binding mechanism defined in clause 6.1.1.4 and keep the binding as long as this attribute remains set. When the PCRF removes the Bind to Default Bearer PCC rule attribute, the bearer binding mechanism as defined in clause 6.1.1.4 shall be applied by using the QoS Class Identifier and ARP values of the dynamic PCC rule. The PCEF support for the Bind to Default Bearer PCC rule attribute is optional and shall be indicated to the PCRF. The bearer binding mechanism associates the PCC Rule with the EPS bearer to carry the service data flow. The association shall: - cause the downlink part of the service data flow to be directed to the EPS bearer in the association; and - assume that the UE directs the uplink part of the service data flow to the EPS bearer in the association. Thus, the detection of the uplink part of a service data flow shall be performed on the EPS bearer over which the downlink packets of the same service data flow is directed to. NOTE 2: For GERAN/UTRAN in UE-only mode the detection of the uplink part of the service data flow may be active, in parallel, on any number of EPS bearers. When the PDN GW is connected to an SGSN via Gn/Gp (and thus a handover from UTRAN/GERAN to E-UTRAN is possible), the bearer binding in the PCEF shall not combine PCC rules with different ARP values onto the same PDP context. For the UE-only mode (which is based on a UE provided binding) PCC rules with different ARP values shall not be authorized for the same PDP context. NOTE 3: If Evolved ARP is not supported by the SGSN then this enables a modification of the EPS bearer ARP without impacting the service assignment after a handover to E-UTRAN or after relocation to a S4‑SGSN or a Gn/Gp SGSN that supports Evolved ARP. A.4.3.1.4 Policy Control For 3GPP Access (GTP based) the policy control functionalities should include the following functionality for QoS control (in addition to the functionalities listed in clause 6.1.5): - Authorization and enforcement of the maximum QoS that is authorized for the total bandwidth usage of non-GBR QCIs at an APN. - Authorization and enforcement of the maximum QoS allocated to the Default EPS bearer. The Default EPS bearer shall have a non-GBR QCI as defined in clause 4.7.2.1 of TS 23.401 [17]. A.4.3.2 Functional Entities A.4.3.2.1 Policy Control and Charging Rules Function (PCRF) The following information represents 3GPP EPS specific values of the ones listed in clause 6.2.1.1: - Subscriber Identifier in the form of IMSI, MSISDN; - Type of IP‑CAN is set to 3GPP-EPS. The PCEF may provide the following information (in addition to the information in clause 6.2.1.1): - Subscribed APN-AMBR; - Default EPS Bearer QoS. The SPR may provide the following information for a subscriber (in addition to the information in clause 6.2.1.1) connecting to a specific PDN: - Authorized APN-AMBR for 3GPP Access; - Authorized Default EPS Bearer QoS. The Authorized APN-AMBR and the Authorized Default EPS Bearer QoS are derived by the PCRF from SPR interaction, according to operator policy. The PCRF shall upon indication of PCC rule removal due to PS to CS handover notify the AF that the associated flows are no longer served by the PS-domain due to PS to CS handover. If vSRVCC is supported in the serving network, the PCRF (V-PCRF if roaming) provides an indicator via Gx to the PCEF to indicate that vSRVCC is allowed for the flow corresponding to the video component of the voice/video call. The PCRF shall provide SDF filters in the PCC rule as received in the packet filter information from the PCEF. If the PCRF receives a request for addition of service data flow(s) with a reference to existing SDF filter identities (and by that to existing PCC rule(s)), the PCRF shall use the QCI or ARP of the existing PCC rule for the new service data flow(s). NOTE: The reference to existing SDF filter identities informs the PCRF that the request is confined to an existing bearer, having bearer bindings with PCC rules that have the same QCI/ARP combination. Assigning a different QCI or ARP to the new SDFs would cause the procedure to fail, since the PCEF cannot map the new SDFs to another bearer. A.4.3.2.2 Policy and Charging Enforcement Function (PCEF) In the 3GPP Access (GTP-based) architecture the PCEF enforce QoS Policies as indicated by the PCRF in accordance to what is stated in clause 6.2.2.1 with the following additions: - Authorized APN-AMBR enforcement. The PCEF shall enforce the authorized APN-AMBR received via the Gx interface for the total bandwidth usage of non-GBR QCI for the APN. - Authorized Default EPS Bearer QoS Enforcement. The PCEF receives the authorized QoS for the default bearer over Gx interface. The PCEF enforces it which may lead to the upgrade or downgrade of the default EPS Bearer QoS. The PCEF shall re-evaluate the bearer binding (as defined in clause 6.1.1.4) taking into account the default bearer QoS change and any PCC Rule operation requested by the PCRF. When the PDN GW is connected via Gn/Gp (and thus handover from UTRAN/GERAN to E‑UTRAN is possible), the PDN-GW shall map QoS parameters of EPS bearers and APN-AMBR (if not received via Gn/Gp) to/from Release 99 and Release 97/Release 98 QoS parameter values of PDP-contexts as specified in Annex E of TS 23.401 [17]. The PDN GW shall mediate Gn/Gp procedures so that PCRF experiences no difference compared to S5/S8 procedures. Only the GBR per bearer is used for resource reservation (e.g. admission control in the RAN). The MBR (per PCC rule / per bearer) and the authorized APN-AMBR are used for rate policing. A.4.3.2.3 Application Function (AF) The AF instructions to report loss of transmission resources will result in a notification from the PCRF that may include an indication that the transmission resources are lost due to PS to CS handover. NOTE: The AF action up to notification of termination of transmission resources due to PS to CS handover is application specific. IMS interprets that the PS to CS handover notification as SRVCC. A.4.3.3 Void A.4.3.4 IP-CAN bearer and IP-CAN session related policy information For EPS the IP‑CAN bearer and IP‑CAN session related policy information in table A.4.3.4-1 shall apply in addition to the ones in table 6.4 and table A.4. A Presence Reporting Area may be defined as a short list of TAs or eNBs and/or ECGI for E-UTRAN, a short list of RAs or SAIs or CGIs for UTRAN and a short list of RAs or CGIs for GERAN. Table A.4.3.4-1: PCC related IP-CAN bearer and IP‑CAN session related policy information Attribute Description PCRF permitted to modify the attribute Scope Authorized default EPS bearer QoS Defines the QCI and ARP of the default EPS bearer. Yes IP‑CAN session Subsequent default EPS bearer QoS (NOTE 1) Defines the QCI and ARP of the default EPS bearer to be applied by the PCEF when the default EPS bearer QoS change time is reached. No (NOTE 2) IP‑CAN session Default EPS Bearer QoS change time (NOTE 1) Defines the time at which the PCEF shall apply the subsequent default EPS bearer QoS. No (NOTE 2) IP‑CAN session NOTE 1: Both parameters shall be provided together. The PCRF may provide up to four instances of them. NOTE 2: The PCRF may replace all instances of Subsequent default EPS bearer QoS that have been provided previously with a new instruction. There is no operation to modify a previously provided instance of Subsequent default EPS bearer QoS and/or Default EPS Bearer QoS change time. The purpose of the default EPS bearer related policy information in table A.4.3.4-1 is to provide QCI and ARP that is applicable to the default bearer of an IP‑CAN session. The PCRF may provide the authorized default EPS bearer QoS in every interaction with the PCEF. The PCEF shall apply the authorized default EPS bearer QoS for the IP‑CAN session, including the necessary bearer binding actions. If dynamic PCC rules are used and the PCEF has indicated that it supports the PCC rule attribute Bind to Default Bearer, the PCRF may provide a subsequent default EPS bearer QoS together with a default EPS bearer QoS change time. When the default EPS bearer QoS change time is reached, the PCEF shall apply the corresponding subsequent default EPS bearer QoS as the new authorized default EPS bearer QoS for the IP-CAN session and perform the necessary bearer binding actions for all of the respective dynamic PCC rules. To keep dynamic PCC rules bound to the default bearer, the PCRF shall include the attribute Bind to Default Bearer in every dynamic PCC rule intended to remain bound to the default bearer. The PCRF may provide up to four instances of subsequent default EPS bearer QoS. NOTE 1: In order to reduce the risk for signalling overload, the PCRF can spread the provisioning of subsequent default EPS bearer QoS for many UEs over time. NOTE 2: The bearer modification is made in the same way as if the PCRF had modified the authorized default EPS bearer QoS at that point in time. The PCEF shall discard any previously received subsequent default EPS bearer QoS instances on explicit instruction as well as whenever the PCRF provides a new instruction for one or more subsequent changes to the default EPS bearer QoS or any other subsequent parameter. NOTE 3: In order to provide further subsequent default EPS bearer QoS in a timely fashion the PCRF can use its own clock to issue the desired changes or use the Revalidation time limit parameter (clause 6.4) to trigger a PCEF request for a policy decision. NOTE 4: For services that depend on specific APN-AMBR and/or QoS for the default EPS bearer (e.g. MPS session) the PCRF is responsible to ensure that no subsequent APN-AMBR or default EPS bearer QoS interfere with the service, e.g. by removing the subsequent APN-AMBR or default EPS bearer QoS before the respective change time is reached. A.4.3.5 TDF session related policy information For EPS the TDF session related policy information in table A.4a shall apply in addition to the ones in table 6.4a. A.4.4 PCC Procedures and Flows A.4.4.1 Introduction For the 3GPP Access (GTP-based), an IP‑CAN session is established by the Create Default Bearer message. The IP‑CAN session is terminated when the last EPS bearer of the IP‑CAN session is disconnected. From the network scenarios listed in clause 7.1, the Case 1 (no Gateway Control Session) applies. A.4.4.2 IP‑CAN Session Establishment In the case of IP‑CAN Session Establishment (described in clause 7.2), the PCEF provides to PCRF (in addition to the parameters described in clause 7.2): the User Location Information, Serving Network, Serving-GW address and RAT type. The PCEF shall also forward the network capability of reporting of changes in CGI/SAI/RAI to the PCRF. The PCRF includes, in the IP‑CAN Session Establishment Ack, PCC Rules with QCI and ARP matching the Authorized Default EPS Bearer QoS, Authorized APN-AMBR and Authorized Default EPS Bearer QoS. If bearer establishment mode is UE/NW, the PCRF may also include PCC Rules requiring a QCI and ARP different from the Default Bearer QoS and for which NW mode applies. A.4.4.3 GW (PCEF) initiated IP‑CAN Session termination The GW (PCEF) initiated IP‑CAN Session termination procedure (described in clause 7.3.2) has no 3GPP specific information. A.4.4.4 IP‑CAN Session Modification A.4.4.4.1 IP‑CAN Session Modification; GW (PCEF) initiated For IP‑CAN session modification (described in clause 7.4.1) the PCEF includes the modification of any of the 3GPP specific information listed in clause A.4.4.2. If the PS to CS handover indicator is set for an IP-CAN bearer that is deleted, the PCEF reports termination of transmission resources for associated PCC Rules due to PS to CS handover. The PCRF may provide the following parameters in the Acknowledgement of the IP‑CAN Session Modification to the PDN GW (in addition to the parameters in clause 7.4.1): Authorized APN-AMBR, Authorized Default EPS Bearer QoS. A.4.4.4.2 IP‑CAN Session Modification; PCRF initiated The PCRF may provide the following parameters in the Policy and Charging Rule Provision to the PDN GW (in addition to the parameters in clause 7.4.2): Authorized APN-AMBR, Authorized Default EPS Bearer QoS. Whenever the PCRF modifies the Authorized Default EPS Bearer QoS, the PCRF shall simultaneously modify the QCI and ARP of all PCC Rules that, according to the operator policy, shall have the same QoS as the default bearer. A modification of the Authorized Default EPS Bearer QoS requires that at least one PCC Rule with a matching QoS can be bound to the default bearer as defined in clause 6.1.1.4. NOTE: The network configuration can ensure that at least one PCC Rule is bound to the default bearer by applying, either operator policies in the PCRF ensuring that a PCC Rule with matching QoS will be active or in the PCEF ensuring that a predefined PCC Rule not known to the PCRF is bound to the default bearer. A.5 3GPP Accesses (GERAN/UTRAN/E-UTRAN) - PMIP-based EPC A.5.0 General For 3GPP Access (PMIP-based), architecture details are described in TS 23.402 [18]. When PMIP-based S5/S8 has been deployed, the IP‑CAN-specific parameter exchange occurs by means of IP‑CAN Session Modification messages including the necessary information. A.5.1 High Level Requirements A.5.1.0 General The same requirements as in clause A.4.1 apply for 3GPP Access (PMIP-based). A.5.1.1 QoS control For 3GPP Access (PMIP based) the same requirements as defined in clause A.4.1.2 apply. A.5.2 Architectural Model and Reference Points A.5.2.1 Reference architecture In the 3GPP Access (PMIP-based) architecture, see TS 23.402 [18], - the Policy and Charging Enforcement Function is allocated to the PDN GW; - the Bearer Binding and Event Reporting Function (BBERF) is allocated to the Serving GW. The Gxx applies and corresponds to the Gxc, as defined in TS 23.402 [18]. One Gateway Control Session corresponds to one IP‑CAN session. A.5.3 Functional Description A.5.3.1 Overall Description A.5.3.1.1 Binding mechanism The same considerations as in clause A.4.3.1.3 apply with the following modifications: - For the 3GPP Access (PMIP-based) the Bearer binding is performed by the BBERF. A.5.3.1.2 Credit management For 3GPP Access (PMIP-based EPC) the same credit re-authorisation triggers as defined in table A.4.3-1 apply. A.5.3.1.3 Event triggers For 3GPP Access (PMIP-based EPC) the same event triggers as defined in table A.4.3-2 apply. However, they apply at the BBERF (and not at the PCEF) upon the request from the PCRF. NOTE: The request from the PCRF can be triggered by configured policy, a request received from the PCEF or request received from the TDF. For a PCEF or TDF based request, this may be a result of credit re-authorization trigger received by the PCEF or by the TDF from the OCS. A.5.3.2 Functional Entities A.5.3.2.1 Policy Control and Charging Rules Function (PCRF) For 3GPP Access (PMIP based) the same requirements as defined in clause A.4.3.2.1 apply with the following modification: - Default EPS Bearer QoS and Subscribed APN-AMBR are provided by the BBERF. For 3GPP Access (PMIP based), the PCRF receives information about supported bearer establishment modes from the PCEF and provides the bearer establishment mode to be used to the PCEF, i.e. in the same way as for 3GPP Access (GTP based). A.5.3.2.2 Policy and Charging Enforcement Function (PCEF) For 3GPP Access (PMIP based) the same requirements as defined in clause A.4.3.2.2 apply with the following modification: - For the 3GPP Access (PMIP-based) the enforcement of the Authorized Default EPS Bearer QoS is not performed by the PCEF. A.5.3.2.3 Bearer Binding and Event Reporting Function (BBERF) In the 3GPP Access (PMIP-based) the BBERF enforces QoS Policies as indicated by the PCRF in accordance to what is stated in clause 6.2.7.3 with the following additions: - Authorized Default EPS Bearer QoS Enforcement. The BBERF receives the authorized QoS for the default bearer over Gxx interface. The BBERF enforces it which may lead to the upgrade or downgrade of the default EPS Bearer QoS. The BBERF shall re-evaluate the bearer binding (as defined in clause 6.1.1.4) taking into account the default bearer QoS change and any QoS Rule operation requested by the PCRF. A.5.3.3 Void A.5.3.4 Void A.5.3.5 IP-CAN bearer and IP-CAN session related policy information For 3GPP Access (PMIP based) the same requirements as defined in clause A.4.3.4 apply. A.5.3.6 TDF session related policy information For 3GPP Access (PMIP based) the same requirements as defined in clause A.4.3.5 apply. A.5.4 PCC Procedures and Flows A.5.4.1 Introduction For the 3GPP Access (PMIP-based), the IP‑CAN session is established by the Proxy Binding Update message to the PDN-GW. The IP‑CAN session is terminated when the PMIP session is terminated. From the network scenarios listed in clause 7.1, the Case 2b applies. A.5.4.2 Gateway Control Session Establishment For the Gateway Control Session Establishment Procedure (see clause 7.7.1), the Serving GW includes the following additional information in the Gateway Control Session Establishment message (in addition to the parameters described in clause 7.7.1): User Location Information, user GSG information, (if received from the MME), Serving-GW address, Serving Network, RAT Type, Default EPS Bearer QoS and if available the APN-AMBR are provided to the PCRF. The PCRF includes, in the Acknowledge Gateway Control Session Establishment (in addition to the parameters described in clause 7.7.1): QoS Rules with QCI and ARP matching the Default EPS Bearer QoS. If the bearer establishment mode is UE/NW, the PCRF may also include QoS Rules requiring a QCI and ARP different from the Default EPS Bearer QoS and for which NW mode applies. In support of PDP Context Activation procedures over S4, the BBERF must indicate various session parameters, e.g. the RAT type, to the PCRF. The PCRF may provide the following parameters in the Acknowledgement of the Gateway Control Session Establishment to the Serving GW (in addition to the parameters described in clause 7.7.1): Authorized APN-AMBR, Authorized Default EPS Bearer QoS. If the PS to CS handover indicator is set for an IP-CAN bearer that is deleted, the BBERF reports termination of transmission resources for associated QoS Rules due to PS to CS handover. A.5.4.3 Gateway Control and QoS Rules Request In the case of Gateway Control and QoS Rules Request (described in clause 7.7.3) the BBERF includes the addition/modification/removal of any the 3GPP specific information listed in clause A.5.4.2. When a change of RAT without S‑GW relocation occurs, the BBERF signals the RAT type change as a parameter in an event report sent from the BBERF to the PCRF. An event report is the then sent, indicating the RAT type change, from the PCRF to the PCEF. When Secondary PDP Context Activation occurs, the S4 SGSN performs a Request Bearer Resource Allocation procedure with the Serving GW. The Serving GW supplies the parameters required by the PCEF to properly handle the allocation of resources. These parameters are sent from the BBERF (Serving GW) to the PCRF for further processing when a PMIP-based S5/S8 is deployed. The PCRF may provide the following parameters in the Acknowledgement of the Gateway Control and QoS Rules Request to the Serving GW (in addition to the parameters described in clause 7.7.3): Authorized APN‑AMBR, Authorized Default EPS Bearer QoS. For the purpose of event reporting to the PCEF the BBERF may generate Event Reports to the PCRF if this has been requested by the PCRF. A.5.4.4 Gateway Control and QoS Rules Provisioning In the case of Gateway Control and QoS Rules Provisioning (described in clause 7.7.4) the PCRF may provide the following parameters (in addition to the parameters described in clause 7.7.4) to the Serving GW: Authorized APN‑AMBR, Authorized Default EPS Bearer QoS. Whenever the PCRF modifies the Authorized Default EPS Bearer QoS, the PCRF shall simultaneously modify the QCI and ARP of all QoS Rules that, according to the operator policy, shall have the same QoS as the default bearer. A modification of the Authorized Default EPS Bearer QoS requires that at least one QoS Rule with a matching QoS can be bound to the default bearer as defined in clause 6.1.1.4. NOTE: The network configuration can ensure that at least one QoS Rule is bound to the default bearer by applying operator policies in the PCRF ensuring that a QoS Rule with matching QoS will be active. For the purpose of event reporting to the PCEF the PCRF may request Event Reports from the BBERF. In response to such request the BBERF shall provide the present value(s) of the event parameters. A.5.4.5 IP‑CAN Session Establishment The PCRF may provide the following parameters in the Acknowledgement of the IP‑CAN Session Establishment to the PDN GW (in addition to the parameters in clause 7.2): Authorized APN‑AMBR, User Location Information, user GSG information (if received from the BBERF). A.5.4.6 IP‑CAN Session Modification A.5.4.6.1 IP‑CAN Session Modification; GW (PCEF) initiated The PCRF may provide the following parameters in the Acknowledgement of the IP‑CAN Session Modification to the PDN GW (in addition to the parameters in clause 7.4.1): Authorized APN‑AMBR. A.5.4.6.2 IP‑CAN Session Modification; PCRF initiated The PCRF may provide the following parameters in the Policy and Charging Rule Provision to the PDN GW (in addition to the parameters in clause 7.4.2): Authorized APN‑AMBR, User Location Information (if received from the BBERF), user GSG information (if received from the BBERF). A.5.4.6.3 Void Annex B (informative): Void Annex C (informative): Void Annex D (informative): Access specific aspects (Non-3GPP) D.1 DOCSIS IP‑CAN D.1.1 General In the DOCSIS IP‑CAN, each UE is connected to the network via a Cable Modem (CM) which is connected through a Hybrid Fibre Coax (HFC) access network to a Cable Modem Termination System (CMTS). Though the UE and CM may or may not be embedded within the same physical package, they remain separate logical devices. One or more UEs may subtend a single CM. Because the CMTS provides the IP connectivity and traffic scheduling and manages quality of service for the CM and the UEs which subtend it, the CMTS fulfils the role of PCEF for the DOCSIS IP‑CAN. In the DOCSIS IP‑CAN, the Application Manager (AM) and the Policy Server (PS) fulfil the role of the PCRF. When accessing resources via a DOCSIS IP‑CAN, the Rx interface can be used to request resources. The communication between the AM and PS and the PS and CMTS uses the PKT-MM-2 interface which is based on COPS and defined in J.179. The remainder of this clause documents the mapping of PCC terminology to the DOCSIS IP‑CAN and how the DOCSIS IP‑CAN realizes the defined PCC functionality. This clause also establishes the requirements of the Rx interface as it is used for the DOCSIS IP‑CAN. The PKT-MM-2 interface is shown here for information to illustrate the organization of the DOCSIS IP‑CAN. References that specify the PKT-MM-2 interface do not constitute normative requirements for the 3GPP architecture. The DOCSIS IP‑CAN does not intend to pose any new normative requirements for the Gx interface. Figure D.1.1: DOCSIS IP‑CAN D.1.1 High level requirements D.1.1.1 General The DOCSIS IP‑CAN employs for an IP‑CAN session, the concept of a DOCSIS registration. The DOCSIS IP‑CAN employs for an IP‑CAN bearer, the concept of a DOCSIS service flow in order to provide an information path between the UE and the CMTS. Note that DOCSIS service flows are unidirectional, either upstream (toward the CMTS) or downstream (toward the CM). When a CM is registered in the DOCSIS IP‑CAN, it is assigned a unique IP Address and separate primary service flows are created for both the upstream and downstream direction These primary service flows are typically given best effort scheduling and are used to carry all IP traffic through the CM for which a more specific service flow has not been created. When a UE is registered in the DOCSIS IP‑CAN, it is assigned its own IP Address and is identified by its MAC address. A UE does not have a service flow assigned to it as a result of registration; rather it is associated with the primary service flows of the CM through which it is attached to the network. Additional bearers for the UE are created dynamically as required to provide appropriate QoS for service flows. Bearer creation is triggered when media descriptors (Media Type and Format) for the SIP session are sent from the AF to the AM over the Rx interface. The AM translates the media descriptors into a QoS request for a DOCSIS service flow. The AM then forwards the QoS request towards the bearer enforcement point using the PKT-MM-2 interface. The PKT-MM-2 interface is not a 3GPP reference point, Specifications that detail the PKT-MM-2 interface do not impose normative requirements on the 3GPP architecture. The following figure provides a graphical representation of the DOCSIS IP‑CAN and how it maps into the generic PCC terminology. Figure D.1.2: PCC to DOCSIS terminology mapping The DOCSIS IP‑CAN defines an IP-Flow to be a unidirectional sequence of packets identified by OSI Layer 3 and Layer 4 header information. This information includes source/destination IP addresses, source/destination port numbers, protocol ID. Multiple Multimedia streams may be carried in a single IP Flow. In a DOCSIS IP‑CAN, there is no equivalent concept as a service data flow. Further a DOCSIS service flow is uni-directional and each service flow is an aggregation of the QoS needs for all the IP-Flows which make up the service flow. As such, the QoS enforcement is done at the service flow level not at the IP-Flow level. D.1.1.2 Charging related requirements D.1.1.3 Policy control requirements D.1.2 Architecture model and reference points D.1.2.1 Reference points D.1.2.1.1 Rx reference point D.1.2.1.2 Gx reference point D.1.2.1.3 Void D.1.3 Functional description D.1.3.1 Overall description The DOSCIS IP‑CAN employs for an IP‑CAN bearer, the concept of a DOCSIS service flow in order to provide an information path between the UE and the CMTS. When a Cable Modem is registered in the DOCSIS IP‑CAN, primary upstream and downstream service flows are created. When a UE is registered in the DOCSIS IP‑CAN it is associated with the primary service flows of the cable modem through which it is attached to the network. Based on session information provided by the AF using the Rx reference point, the Application Manager will determine QoS requirements for each IP flow. IP flows which do not require special quality of service treatment may be carried over the primary service flows. For other IP flows which require specific QoS treatment, the Policy Server requests the CMTS to admit the flows using the pkt-mm-2 interface providing detailed information of the QoS requirements. Provided that resources are available, the CMTS will create additional bearers dynamically and push the appropriate traffic filters to the cable modem. D.1.3.1.1 Binding mechanism In the DOCSIS IP‑CAN, the binding mechanism is achieved through the use of traffic Classifiers. These Classifiers filter traffic destined to a UE behind a Cable Modem or sourced from a UE behind a Cable Modem, to a particular DOCSIS service flow. DOCSIS Classifiers contain the following attributes which can be used to filter IP traffic: - IP Type of Service – Range and Mask; - IP Protocol; - IP Source Address; - IP Source Mask; - IP Destination Address; - IP Destination Mask; - TCP/UDP Source Port Start; - TCP/UDP Source Port End; - TCP/UDP Destination Port Start; - TCP/UDP Destination Port End. The Classifier(s) which are used for a particular DOCSIS service flow are communicated to the CMTS by the Policy Server (on behalf of the Application Manager) via the pkt-mm-2 interface. The Application Manager will specify the QoS requirements for the IP flow, the direction of the IP flow and the Classifier(s) which are to be used for the DOCSIS service flow serving the IP flow. When a session is no longer in use, the Application Manager communicates to the CMTS to tear down the resources associated with the session. Based on this communication, the CMTS will remove the DOCSIS service flow(s) and any Classifier(s) associated with the service flow(s) and inform the Cable Modem of the removal. Traffic which previously matched the removed Classifier(s) will now be placed on either the upstream or downstream primary DOCSIS service flow, depending on the direction of the traffic. D.1.3.2 Functional entities D.1.3.2.1 Policy Control and Charging Rules Function (PCRF) In the DOCSIS IP‑CAN, the Application Manager (AM) and the Policy Server (PS) fulfil the role of the PCRF. The AM receives media descriptors (Media Type and Format) from the AF for SIP sessions and maps the QoS needs of the session to a FlowSpec, The FlowSpec is a layer 2 independent representation of the bandwidth and QoS requirements for the flow derived from the media descriptors using a well defined algorithm. The AM and PS provide network resource control in the DOCSIS IP‑CAN by managing the CMTS using the PacketCable Multimedia interface pkt-mm-2. The AM and PS map IP flows to DOCSIS service flows in accordance with the operator's policies and based on the media format information provided by the AF. D.1.3.2.1.1 Input for PCC decisions The AM accepts any of the following input as a basis for decisions on PCC rule operations: - Per IP‑CAN session (e.g.: UE IP address); - Requested QoS, media format, priority indicator. The SPR may provide the following information: - Subscribers maximum allowed QoS resources. Subscriber's maximum allowed bit rate for upstream and downstream. D.1.3.2.2 Policy and Charging Enforcement Function (PCEF) The CMTS provides PCEF equivalent functionality within the DOCSIS IP‑CAN. The CMTS creates, modifies and deletes DOCSIS service flows upon request of the Policy Server. The CMTS receives requests from the Policy Server over the pkt-mm-2 interface. D.1.3.2.3 Application Function (AF) D.1.3.3 Policy and charging control rule D.1.3.3.1 General D.1.3.3.2 Policy and charging control rule operations D.2 WiMAX IP‑CAN In the WiMAX IP‑CAN, the UE (also referenced as Mobile Station or MS in IEEE 802.16 standards) connects to the WiMAX Access Service Network (ASN). The ASN logically communicates with a Connectivity Service Network (CSN) which is a collection of core networking functions (e.g. Mobile IP HA, AAA Server, DHCP, DNS etc.). The ASN manages traffic admission and scheduling, enforces QoS for an authorized UE and performs accounting functions for the UE (per session, flow, or UE). WiMAX PCEF is part of WiMAX IP‑CAN and is to be defined by WiMAX Forum [15]. WiMAX PCEF terminates the Gx reference point from the PCRF and may be a distributed enforcement architecture. The PCC functional mapping to WiMAX IP‑CAN is shown in the following figure where PCC Gx and Rx are applied. Figure D.2.1: WiMAX IP‑CAN and 3GPP PCC D.2.1 High level requirements D.2.1.1 General No new requirements have been identified. D.2.1.2 Charging related requirements No new requirements have been identified. D.2.1.3 Policy control requirements No new requirements have been identified. D.2.2 Architecture model and reference points D.2.2.1 Reference points D.2.2.1.1 Rx reference point WiMAX IP‑CAN imposes no new requirements to the Rx reference point. D.2.2.1.2 Gx reference point WiMAX IP‑CAN imposes no new requirements to the Gx reference point other than WiMAX specific values for existing Gx parameters (e.g. RAT type) as described in [15]. D.2.2.1.3 Sp reference point WiMAX IP‑CAN imposes no new requirements to the Sp reference point. D.2.3 Functional description D.2.3.1 Overall description The WiMAX IP‑CAN employs for an IP‑CAN bearer, the concept of a WiMAX service flow, in order to provide a data path between the UE and the WiMAX CSN via the ASN. When a UE is registered in the WiMAX IP‑CAN, it is associated with one or more WiMAX service flows. Based on session information provided by the AF via the Rx reference point, the PCRF determines the QoS requirements for each service by constructing PCC rules. The PCRF requests the WiMAX IP‑CAN via Gx interface to enforce the authorized PCC rules on the WiMAX service flows. The PCEF function in the WiMAX IP‑CAN enforces the PCC rules received from the PCRF. Provided that resources are available, the ASN creates and configures logical bearers and enforces creation of appropriate traffic classes associated with service flows compliant with IEEE 802.16 standards for the air interface and IP‑CAN bearer capabilities in the ASN (e.g. DiffServ). D.2.3.1.1 Binding mechanism D.2.3.1.2 Credit management D.2.3.1.3 Event triggers D.2.3.2 Functional entities D.2.3.2.1 Policy Control and Charging Rules Function (PCRF) The 3GPP PCRF is used for the WiMAX IP‑CAN. The PCRF interacts with WiMAX IP‑CAN using 3GPP Gx reference point. D.2.3.2.2 Policy and Charging Enforcement Function (PCEF) For WiMAX IP‑CAN, PCEF functions may be distributed. It additionally: - Terminates the Gx reference point from PCRF and may act as a proxy for the PCRF. - Handles the enforcement function relocation in WiMAX IP‑CAN in a way that is transparent to the PCRF. D.2.3.2.3 Application Function (AF) WiMAX IP‑CAN imposes no requirements to the AF functionalities. D.2.3.3 Policy and charging control rule D.2.3.3.1 General D.2.3.3.1 Policy and charging control rule operations Annex E (informative): Void Annex F (informative): Void Annex G (informative): PCC rule precedence configuration The precedence information is part of the PCC rule (see clause 6.3.1) and instructs the PCEF in which order the service data flow templates of the active PCC rules needs to be analyzed when an IP packet arrives. This mechanism ensures that the service data flows can be correctly identified even if the service data flow templates contain overlapping service data flow filters. For PCC rules that contain an application identifier (i.e. that refer to an application detection filter), the order and the details of the detection are implementation specific. Once an application has been detected, enforcement and charging shall however be applied under consideration of the PCC rule precedence, i.e. when multiple PCC rules overlap, only the enforcement and charging actions of the PCC rule with the highest precedence shall be applied. NOTE: This ensures that traffic described by service data flow filters can be precluded from the enforcement of application detection filter based PCC rules if this is necessary (e.g. for sponsored data connectivity). Within the PCC framework it is possible to use different types of PCC rules for which the service data flow templates may not always be known by the PCRF. Therefore, the PCC rule precedence information needs to be carefully configured to avoid certain situations e.g. a dynamic PCC rule cannot be applied for service data flow detection due to a predefined PCC rule not known to the PCRF with overlapping filter information and a higher precedence. For example, an operator could structure the value range of the precedence information into separate value ranges (in decreasing order) for the different types of PCC rules as follows: - dynamic PCC rules; - predefined PCC rules known to the PCRF; - predefined PCC rules not known to the PCRF; - dynamic PCC rules for non-operator controlled services, i.e. those which are generated by the PCRF based on the UE provided traffic mapping information (and which take over the UE provided precedence information). Annex H (normative): Access specific aspects (EPC-based Non-3GPP) H.1 General An EPC-based non-3GPP IP‑CAN (TS 23.402 [18]), which requires the Gxa for dynamic QoS control, shall include the BBERF. The allocation of a BBERF to a node within the non-3GPP IP‑CAN is out of 3GPP scope, unless otherwise specified in this Annex. H.2 EPC-based cdma2000 HRPD Access In case of EPC-based cdma2000 HRPD access the BBERF is located in the HRPD Serving Gateway (HSGW) defined in 3GPP2 X.S0057 [20]. The HSGW of an EPC-based cdma2000 HRPD access that supports a Gxa interface shall support all the Gxa procedures defined in this specification. NOTE 1: If the HSGW does not support the Gxa interface, the HSGW performs QoS enforcement in the HRPD access based on subscription-based QoS policies provided by the 3GPP AAA Server/Proxy during access authentication and/or static QoS policies configured in the HSGW. However, this is out of the scope of this specification. The operator may configure an indicator in HSS which is delivered to the BBERF in HSGW within the Charging Characteristics and used by the BBERF to not establish the Gateway Control Session during the IP-CAN session establishment procedure. NOTE 2: The decision to not establish the Gateway Control Session applies for the life time of the IP-CAN session. NOTE 3: The indicator in the HSS is operator specific, therefore it can only be used in non-roaming cases. During the pre-registration phase in case of optimised EUTRAN-to-HRPD handovers, the Serving GW and the HSGW are associated with the IP‑CAN session(s) of the UE in the PCRF. The HSGW is the non-primary BBERF. For each PDN connection, if the UE has acquired an IPv6 prefix via the 3GPP access, the PCRF (H-PCRF in the home-routed case, V-PCRF in the local-breakout case) shall provide the IPv6 prefix of UE to the HSGW during the Gateway Control Session establishment procedure. In order to allow PCRF to link the new Gateway Control session to a Gx session based on the information received in the Gateway Control session establishment message, it is assumed that there is only a single IP-CAN session per PDN ID and IMSI. NOTE 4: The HSGW performs QoS mapping between the QoS parameters exchanged across Gxa interface and the cdma2000 HRPD QoS parameters used within the HRPD access. However, this is out of the scope of this specification. For EPC based cdma2000 HRPD access, the IP-CAN bearer establishment mode for all of the simultaneous IP‑CAN sessions between a UE and a PDN shall have the same value. NOTE 5: The UE is supposed to assign the same BCM value and the PCRF is supposed to keep the value assigned by the UE. H.3 EPC-based Trusted WLAN Access with S2a In an EPC-based trusted WLAN Access with S2a, the PCEF is located in the PDN-GW and the BBERF does not apply. NOTE: Gxa interface is not used for S2a-PMIP in Trusted WLAN within this Release of the specification. From the network scenarios listed in clause 7.1, the Case 1 (no Gateway Control Session) applies. Specific event triggers applicable are listed in table H.3. Table H.3: TWAN access specific event/credit reauthorization triggers Event/Credit reauthorization trigger Description Reported from Condition for reporting RAT type change. The characteristics of the air interface, communicated as the radio access type, have changed. PCEF PCRF/OCS For an IP-CAN session set-up over a Trusted WLAN Access with S2a: - at IP‑CAN Session Establishment the PCEF provides TWAN location information (TWAN ID and/or UE Time Zone as described in clause 16 of TS 23.402 [18]), IP-CAN type , RAT Type, PLMN identifier and an indication that access is trusted to the PCRF (over Gx). The TWAN ID may include the identifier of the operator of the TWAN as defined in clause 16 of TS 23.402 [18]. This occurs at step 3 of Figure 7.2-1 (IP‑CAN Session Establishment). This information is also provided by the PCEF to the charging entities as described in TS 32.251 [9]. - The Access Network Information Report event trigger defined in clause 6.1.4 applies. The user location information within the Access Network Information reporting contains the TWAN ID and/or UE Time Zone as described in clause 16 of TS 23.402 [18]. This information is sent when a bearer over Trusted WLAN access is activated or modified or deactivated and when the IP-CAN session is terminated. When the bearer over Trusted WLAN access is deactivated or the IP-CAN session is terminated the user location information corresponds to the last known UE location. When the IP‑CAN session is terminated a TWAN Release Cause (if available) is also provided to the PCRF. The IP-CAN type change, the PLMN change event triggers defined in clause 6.1.4 and RAT type event trigger applies. The PCEF reports to the PCRF when a Create Session Request is received including information that the UE moved to a trusted WLAN access. This information is also provided by the PCEF to the charging entities as described in TS 32.251 [9]. When the PCRF subscribes to any of the listed above event triggers using the Provision of PCC Rules procedure, the PCEF provides the parameter values in the response back to the PCRF, as defined in clause 6.1.4. It shall be possible for the PCRF to authorize the QCI and ARP of the default EPS bearer to be enforced by the PCEF immediately or at a specific point in time by providing the default EPS bearer related policy information as defined in clause A.4.3.4. H.4 EPC-based untrusted non-3GPP Access In an EPC-based untrusted non 3GPP Access, the BBERF does not apply. Specific event triggers and credit reauthorization triggers are listed in table H.4. Table H.4: Untrusted non-3GPP access specific event/credit reauthorization triggers Event/Credit reauthorization trigger Description Reported from Condition for reporting RAT type change. The characteristics of the air interface, communicated as the radio access type, have changed. PCEF PCRF/OCS For an IP-CAN session set-up over an untrusted non-3GPP access over S2b: - At IP‑CAN Session Establishment the PCEF provides IP-CAN type, indication that it is untrusted RAT type, ePDG IP address and the Serving Network Identifier to the PCRF. This occurs at step 3 of Figure 7.2-1 (IP‑CAN Session Establishment). This information is also provided by the PCEF to the charging entities as described in TS 32.251 [9]. The PCEF provides also the PCRF with User location information it may have received from the ePDG. As defined in TS 23.402 [18], this User location information may contain: ePDG IP address used in IKEv2 tunnel procedures. The local IP address and the UDP or TCP port number (if NAT was detected) detected by the ePDG as the source of the UE traffic over Swu. - WLAN Location Information and the WLAN Location Information Age. The TWAN ID within the WLAN location Information includes the identifier of the operator of the TWAN as defined in clause 16 of TS 23.402 [18]. - The IP-CAN type changes, the PLMN change event trigger defined in clause 6.1.4 and RAT type changes event trigger applies. The PCEF reports to PCRF when a Create Session Request is received including information that the UE moved to an untrusted WLAN access. This information is also provided by the PCEF to the charging entities as described in TS 32.251 [9]. As described for the case of an IP‑CAN Session Establishment, the PCEF provides also the PCRF with location information it may have received from the ePDG and the ePDG IP address used in IKEv2 tunnel procedures. - When the PCRF subscribes to any of the listed above event triggers using the Provision of PCC Rules procedure, the PCEF provides the parameter values in the response back to the PCRF, as defined in clause 6.1.4. - The Access Network Information Report event trigger defined in clause 6.1.4 applies. As defined in TS 23.402 [18], the user location information within the Access Network Information reporting may contain: - The local IP address and the UDP or TCP port number (if NAT was detected) detected by the ePDG as the source of the UE traffic over Swu. - WLAN Location Information and the WLAN Location Information Age. When the Access Network Information reported by the PCRF to the AF corresponds to the local IP address used by the UE to reach the ePDG, this information cannot be considered as reliable. NOTE 1: This is because the UE can spoof its IP address. - When the IP-CAN session is terminated a UWAN Release Cause (if available) is provided to the PCRF. As defined in TS 23.402 [18], the User Location Information within the Access Network Information reporting may contain: - The local IP address and the UDP or TCP port number (if NAT was detected) detected by the ePDG as the source of the UE traffic over Swu. - WLAN Location Information and the WLAN Location Information Age defined in TS 23.402 [18] When the PCEF receives no user location information from the ePDG, it provides at least information on the Serving Network of the ePDG. The PCRF reports the ePDG IP address used in IKEv2 tunnel procedures to the AF (i.e. P-CSCF) at the time the AF instructions as described in clause 6.2.3 are received and the ePDG IP address is available, i.e. at the time the AF session is established and at the time the PCRF reports IP-CAN type change, if the AF (i.e. P-CSCF) subscribes to it. The AF instruction to report changes of the IP‑CAN type is described in clause 6.2.3 including an indication that the access type is untrusted. NOTE 2: In order to provide more detailed information to the AF about the characteristics of the access when the RAT type is unknown, the information on whether the access is untrusted is provided. It shall be possible for the PCRF to authorize the QCI and ARP of the default EPS bearer to be enforced by the PCEF immediately or at a specific point in time by providing the default EPS bearer related policy information as defined in clause A.4.3.4. Annex I (informative): Void Annex J (informative): Standardized QCI characteristics - rationale and principles The following bullets capture design rationale and principles with respect to standardized QCI characteristics: - A key advantage of only signalling a single scalar parameter, the QCI, as a "pointer" to standardized characteristics - as opposed to signalling separate parameters for resource type, priority, delay and loss – is that this simplifies a node implementation. NOTE 1: TS 23.107 [14] permits the definition of more than 1600 valid GPRS QoS profiles (without considering GBR, MBR, ARP and Transfer Delay) and this adds unnecessary complexity. - In general, the rate of congestion related packet drops can not be controlled precisely for Non-GBR traffic. This rate is mainly determined by the current Non-GBR traffic load, the UE's current radio channel quality and the configuration of user plane packet processing functions (e.g. scheduling, queue management and rate shaping). That is the reason why services using a Non-GBR QCI should be prepared to experience congestion related packet drops and/or per packet delays that may exceed a given PDB. The discarding (dropping) of packets is expected to be controlled by a queue management function, e.g. based on pre-configured dropping thresholds and is relevant mainly for Non-GBR QCIs. The discarding (dropping) of packets of an SDF aggregate mapped to a GBR QCI should be considered to be an exception as long as the source sends at a rate smaller than or equal to the SDF aggregate's GBR. Under these exceptional conditions, when required by operator policy, the eNodeB can be configured to also use the bearer's ARP priority level to assess the relative priority of packets belonging to different SDFs in determining whether to discard a packet or not. - An operator would choose GBR QCIs for services where the preferred user experience is "service blocking over service dropping", i.e. rather block a service request than risk degraded performance of an already admitted service request. This may be relevant in scenarios where it may not be possible to meet the demand for those services with the dimensioned capacity (e.g. on "new year's eve"). Whether a service is realized based on GBR QCIs or Non-GBR QCIs is therefore an operator policy decision that to a large extent depends on expected traffic load vs. dimensioned capacity. Assuming sufficiently dimensioned capacity any service, both Real Time (RT) and Non Real Time (NRT), can be realized based only on Non-GBR QCIs. NOTE 2: The TCP's congestion control algorithm becomes increasingly sensitive to non congestion related packet losses (that occur in addition to congestion related packet drops) as the end-to-end bit rate increases. To fully utilise "EUTRA bit rates" TCP bulk data transfers will require a PLR of less than 10-6. Annex K (informative): Limited PCC Deployment Limited support for policy provisioning occurs in certain deployment scenarios. If PCC is deployed in the HPLMN but not the VPLMN, dynamic policy provisioning only occurs in the home routed roaming cases if no BBERF is employed, or in the non-roaming scenarios. In roaming scenarios in which the PCC is deployed in the HPLMN but not the VPLMN and a GW (BBERF) is used: - limited policy control is possible when the UE moves from the HPLMN to the VPLMN. In the VPLMN, the UE receives only service according to static policies or according to static subscriber policies, defined outside the PCC framework delivered as described in TS 23.402 [18]; the dynamically allocated resources associated with specific EPS Bearers no longer apply after this transition. - If a UE moves from the VPLMN to the HPLMN, dedicated resource establishment procedures are used to dynamically allocate the appropriate resources in the HPLMN for EPS bearers. - PCC may still be employed to provision rules to the PCEF/TDF for the purpose of charging on the basis of the IP‑CAN session. When PCC is supported in the VPLMN and not in the HPLMN, dynamic policy may only be provided for the LBO case. As the VPCRF has no access to subscriber policy information from the HPLMN, only static policy will apply. The VPCRF may however interact with the AF in the VPLMN in order to determine dynamic policy operating entirely in the VPLMN. This policy will be enforced either in the PCEF or the BBERF or the TDF to be enforced entirely in the VPLMN. Bearer binding will occur under control of the VPLMN, either in the GW (BBERF) or in the GW (PCEF) (in the case of GTP-based S5/S8 for 3GPP access). Annex L (normative): Limited PCC Deployment In roaming scenarios in which the PCC is deployed in the HPLMN but not the VPLMN and a GW (BBERF) is used: - HPCRF and OCS shall detect based on local configuration according to roaming agreements that the event reporting is restricted. The OCS shall not set re/authorization triggers which would require event reporting that can not be generated. - The H-PCRF shall inform the AF of event triggers that cannot be reported. The H-PCRF shall inform the AF of events that cannot be reported when AF registers event trigger to the H-PCRF. When the H-PCRF detects limited PCC deployment, some event triggers which are dependent upon reporting from the BBERF cannot be reported. The H-PCRF shall inform the AF of events that cannot be reported when the UE is in or after the UE has handed over to an Access Gateway where the BBERF functionality is not deployed. Annex M (informative): Handling of UE or network responsibility for the resource management of services For access networks supporting network initiated resource signalling, the network can take over the responsibility for the resource management for a service. This means the network triggers the request for resources when the service is started or modified and triggers the release of the resources when the service is terminated. The UE remains responsible for starting the service or reacting to an incoming service signalling and needs to decide about how to proceed with the service if the desired resources are not available. As the network initiated resource signalling cannot always be used due to UE, access network, roaming or other restrictions, the default responsibility for the resource management for a service is given to the UE. However, the UE and the PCRF may be configured on a per service basis to make use of the network responsibility for resource management if the current access network allows this, i.e. if network initiated resource signalling is possible. The UE configuration regarding the responsibility for the resource management of a service might be updated by device management. Regarding the PCC functionality, the main difference between the UE and the network responsibility for resource management is in the PCRF behaviour. When the UE is responsible, the PCRF waits with the authorization and installation of PCC rules until an appropriate resource request arrives. The main criteria for authorizing a PCC rule is a match of the service data flow filter information with the UE provided traffic mapping information, i.e. the UE desire to run this service on the requested resource. The QoS requested by the UE is then aligned with the authorized QoS for the PCC rules that are associated with the resource request by the PCRF. When the network is responsible for the resource management, the PCRF authorizes PCC rules immediately, i.e. when the IP‑CAN session is established and when new service information is received from the AF. The authorized PCC rules are installed afterwards. Annex N (informative): PCC usage for sponsored data connectivity N.1 General With sponsored data connectivity, the Sponsor has a business relationship with the operator and the Sponsor reimburses the operator for the user's data connectivity in order to allow the user access to an associated Application Service Provider's (ASP) services. Alternatively, the user pays for the connectivity with a transaction which is separate from the subscriber's charging. It is assumed the user already has a subscription with the operator. A possible deployment configuration for sponsored data connectivity in the non roaming case is illustrated in Figure N.1-1. In the roaming case a S9 reference point is present between the H-PCRF and the V-PCRF. NOTE 1: Sponsored data connectivity is not supported in the roaming with visited access scenario in this Release. Figure N.1-1: Deployment for sponsored data connectivity The relationship between the AF and Sponsor and between the Sponsor and ASP is out of scope of this specification. A single AF can serve multiple ASPs and multiple sponsors. NOTE 2: An ASP can also be a sponsor. The sponsor may choose to supply the PCRF (via the AF) with the usage thresholds that it expects the PCEF/TDF to enforce. Alternatively, the Sponsor can allow the ASP to enforce such control over the sponsored data connectivity. The information required for the detection of sponsored HTTP traffic (i.e. server host name) can be verified with the corresponding server IP address/prefix of the IP packets by the PCEF/TDF. The PCEF/TDF uses implementation specific logic to perform this verification. N.2 Reporting for sponsored data connectivity There are two deployment scenarios for usage reporting for sponsored data connectivity. The Sponsor Identifier and Application Service Provider Identifier are provided for sponsored services to the PCRF from the AF over the Rx interface. In the first scenario the PCRF assigns a service specific Charging Key for a sponsored IP flow. The Charging key is used by the PCEF/TDF to generate separate accounting records for offline charging and and/or usage data records for online charging for the sponsored flows. Correlation of accounting records and usage data records from multiple users per sponsor and/or application service provider is then performed using the charging key. In a second scenario the Sponsor Identifier and Application Service Provider Identity is included in PCC/ADC rules from the PCRF to the PCEF/TDF as defined in clause 6.3.1. For this scenario the same Charging Key may be used both for IP flows that are sponsored and for flows that are not sponsored. Accounting records generated by the PCEF/TDF for offline charging include the Sponsor Identity and the Application Service Provider Identity. Correlation of accounting records from multiple users per sponsor and/or application service provider can then be based on Sponsor Identity and Application Service Provider Identity instead of the Charging Key. Usage reporting for online charging including Sponsor Identity and Application Service Provider Identity has not been specified in this release of the specification. PCC/ADC rules that include a Sponsor Identity and an Application Service Provider Identity should include a Charging Method that indicates offline charging. Annex P (normative): Fixed Broadband Access Interworking with EPC This annex specifies the enhancement to PCC framework for supporting dynamic QoS interworking with Policy Framework defined by Broadband Forum. P.1 Definitions UE local IP address is defined as: either the public IPv4 address and/or IPv6 address/IPv6 network prefix assigned to the UE by the BBF domain in the no-NAT case, or the public IPv4 address assigned by the BBF domain to the NATed RG that is used for this UE. H(e)NB local IP address is defined as: either the public IPv4 address and/or IPv6 address/IPv6 network prefix assigned to the H(e)NB by the BBF domain in the no-NAT case, or the public IPv4 address assigned by the BBF domain to the NATed RG that is used for this H(e)NB. Non-seamless WLAN offload (NSWO) is a capability of routing specific IP flows over the WLAN access without traversing the EPC as defined in clause 4.1.5 of TS 23.402 [18]. EPC-routed: User plane traffic that is routed via a PDN GW in EPC as part of a PDN Connection. EPC-routed applies to non-roaming, roaming with traffic home-routed and roaming with traffic local break-out cases. P.2 Abbreviations The following abbreviations are relevant for this annex only: BBF Broadband Forum BPCF Broadband Policy Control Function NSWO Non-Seamless WLAN offload NSWO-APN Non-Seamless WLAN offload APN P.3 High Level Requirements The same requirements as defined in clause 4 applies with the following exceptions: - no UE initiated resource reservation procedures are supported for EPC-based Fixed Broadband Access. - The support of traffic steering control for the traffic in the (S)Gi-LAN is only applicable to the EPC-routed traffic of Home-routed scenario. In addition, it shall be possible to. - perform resource reservation (e.g. admission control request to the Fixed Broadband Network) based on the bandwidth requirements and the QoS attributes of a service request for EPC-routed traffic in the Fixed Broadband network; - provide information to identify a 3GPP UE in the Fixed Broadband Network. - perform resource reservation (e.g. admission control request to the Fixed Broadband Network) based on the bandwidth requirements and the QoS attributes of a service request for non-seamless WLAN offloaded traffic in the Fixed Broadband network. In this case the non-seamless WLAN offloaded traffic shall be managed by PCRF as an IP-CAN session identified by one IPv4 and/or an IPv6 prefix together with UE identity information and Non-seamless WLAN offload APN. The IP‑CAN session for NSWO exists as long as UE Local IP addresses/prefix is announced to the IP network and authorized by EPC. The NSWO-APN is an APN allowing the BPCF to indicate to PCRF that for subscribers of a certain HPLMN the IP-CAN session is related to NSWO traffic. NOTE 1: The NSWO-APN is not used for the selection of a PDN GW. NOTE 2: Dynamic provisioning from the HPLMN of NSWO-APN to BPCF is out of the scope of this Release. NOTE 3: The naming convention of NSWO-APN is left to operator's implementation decision. P.4 Architecture model and reference points P.4.1 Reference points P.4.1.1 S9a Reference point The S9a reference point resides between: - the PCRF in the PLMN and the BPCF in the Fixed Broadband Access Network (BPCF); - the PCRF in the VPLMN (V PCRF) and the BPCF in the Fixed Broadband Access Network (BPCF). The S9a reference point enables transfer of dynamic QoS control policies from the (V-)PCRF to the BPCF for the purpose of allocation of QoS resources in the Fixed Broadband Access Network for non-seamless WLAN offloaded traffic and for EPC-routed traffic. For scenarios where the traffic is non-seamless WLAN offloaded in the Fixed Broadband Access Network, based on Rx authorizations and event subscriptions, or equivalent information, received by the BPCF from an AF in the Fixed Broadband Access Network, the S9a reference point enables the BPCF to send Rx authorizations and event subscriptions to the PCRF. NOTE: The AF in the Fixed Broadband Access Network and the reference point between the AF in the Fixed Broadband Access Network and the BPCF are out of scope for this specification. P.4.1.2 S15 Reference Point The S15 reference point between the HNB GW and the PCRF and between the HNB GW and the V-PCRF. It enables the transfer of dynamic QoS control policies from the (V-)PCRF to the BPCF for the purpose of allocation of QoS resources in the Fixed Broadband Access Network for HNB CS calls. P.4.1.3 Gxx reference point When this reference point corresponds to the Gxb*, it transports access information for WLAN UEs such as the UE local IP address and the UDP port number. It is used scenarios in which the ePDG provides the access information via Gxb* to trigger the PCRF to initiate the S9a session i.e. S2b-PMIP and untrusted S2c. For the case of H(e)NB with S5/S8 PMIP, this reference point corresponds to Gxc and the requirements in clause 5.2.7 applies. In addition for the purpose of fixed broadband access interworking, Gxc transports the H(e)NB Local IP address and the UDP source port, if available, in the fixed broadband access network where the H(e)NB connects to. P.4.1.4 S9 reference point In addition to the specification of the S9 reference point defined in clause 5.2.6, this reference point is used to trigger the V-PCRF to initiate the Gateway Control Session establishment over S9a. The S9 interface is enhanced to carry from the H-PCRF to the V-PCRF the UE local IP address, the UDP port number, if available, the H(e)NB local IP address and UDP port, if available and the ePDG IP address (for S2b and untrusted S2c access) or the PDN GW IP address (for trusted S2c access), if available. P.4.1.5 Gx reference point In addition to the specification of the Gx reference point defined in clause 5.2.2, this reference point is enhanced as described in the following. The IP-CAN establishment/modification request message, send from PCEF to PCRF, should include: - the UE local IP address and the UDP port number, if available, when WLAN access and GTP is used. - the UE local IP address and the UDP port number, if available, when trusted S2c is used. - the H(e)NB local IP address and the UDP port number, if available, when UE accesses from H(e)NB and GTP S5/S8 is used. P.4.2 Reference architecture P.4.2.0 General The reference architecture described in clause 5.1 is: - extended to include S9a reference point to support fixed broadband access interworking to EPC for the following scenarios: - S9a reference point between PCRF and BPCF in the non-roaming case for traffic that is routed via EPC and for traffic that is non-seamless WLAN offloaded in the fixed broadband access network; and - S9a reference point between the V-PCRF and BPCF for roaming cases with visited access and home routed for traffic that is routed via EPC; and for traffic that is non-seamless WLAN offloaded in the fixed broadband access network; - extended to include the S15 reference point as defined in clause P.4.1.2; - PCEF resides in the PDN GW; - for WLAN access: BBERF resides in the ePDG. The BBERF only applies for cases 2b (i.e. S2b-PMIP, S2c-untrusted); - for H(e)NB access with S5/S8 PMIP: BBERF resides in the Serving GW. The UE may or may not be behind a NAT. The NAT may reside in the BBF access network or in the customer premises network. Policy interworking via S9a for non-seamless WLAN offloaded traffic in this release is supported for scenarios without NAT in the BBF domain. P.4.2.1 Reference architecture – Non-Roaming Figure P.4.2.1-1: PCC Reference architecture for Fixed Broadband Access Interworking P.4.2.2 Reference architecture – Home Routed Figure P.4.2.2-1: PCC Reference architecture for Fixed Broadband Access Interworking (home routed) P.4.2.3 Reference architecture – Visited Access Figure P.4.2.3-1: PCC Reference architecture for Fixed Broadband Access Interworking (visited access) P.4.2.4 Reference architecture - Non-Roaming with non-seamless WLAN offload in Fixed Broadband Access Network; scenario with AF Figure P.4.2.4-1: PCC Reference architecture for Fixed Broadband Access Interworking (non-roaming with non-seamless WLAN offload in Fixed Broadband Access Network) NOTE 1: The architecture also supports scenarios where there is an Application Function in the Fixed Broadband Access Network. The AF in the Fixed Broadband Access Network and the reference point between the AF in the Fixed Broadband Access Network and the BPCF are out of scope for this specification. NOTE 2: The AF in this architecture is used with traffic that is non-seamless WLAN offloaded in the Fixed Broadband Access Network. P.4.2.5 Reference architecture - Roaming with non-seamless WLAN offload in Fixed Broadband Access Network: scenario with AF Figure P.4.2.5-1: PCC Reference architecture for Fixed Broadband Access Interworking (roaming with non-seamless WLAN offload in Fixed Broadband Access Network) NOTE 1: The architecture also supports scenarios where there is an Application Function in the Fixed Broadband Access Network. The AF in the Fixed Broadband Access Network and the reference point between the AF in the Fixed Broadband Access Network and the BPCF are out of scope for this specification. NOTE 2: The AF in this architecture is used with traffic that is non-seamless WLAN offloaded in the Fixed Broadband Access Network. P.4.2.6 Reference architecture - Non-Roaming with non-seamless WLAN offload in Fixed Broadband Access Network: scenario with TDF Figure P.4.2.6-1: PCC Reference architecture for Fixed Broadband Access Interworking (non-roaming with non-seamless WLAN offload in Fixed Broadband Access Network) NOTE 1: The TDF in this architecture is used with traffic that is non-seamless WLAN offloaded in the Fixed Broadband Access Network. NOTE 2: Sd is an intra-operator interface. Scenarios where non-seamless WLAN offloaded traffic is routed via the TDF are therefore limited to the case where the Fixed Broadband Access Network and the PLMN are owned by the same operator. P.4.2.7 Reference architecture - Roaming with non-seamless WLAN offload in Fixed Broadband Access Network: scenario with TDF Figure P.4.2.7-1: PCC Reference architecture for Fixed Broadband Access Interworking (roaming with non-seamless WLAN offload in Fixed Broadband Access Network) NOTE 1: The TDF in this architecture is used with traffic that is non-seamless WLAN offloaded in the Fixed Broadband Access Network. NOTE 2: Sd is an intra-operator interface. Scenarios where non-seamless WLAN offloaded traffic is routed via the TDF are therefore limited to the case where the Fixed Broadband Access Network and the VPLMN are owned by the same operator. P.5 Functional description P.5.1 Overall description For EPC based Fixed Broadband Access Interworking with EPC-routed traffic the credit management, reporting, usage monitoring, termination actions, service data flow prioritization and standardized QoS characteristics as defined in clause 6.1 shall apply. For non-seamless WLAN offloaded traffic service data flow prioritization as defined in clause 6.1 applies. For scenario with TDF, usage monitoring as defined in clause 6.1 applies. For NSWO traffic in other scenarios, without TDF, usage monitoring is out of scope of this specification. For all scenarios, credit management, termination actions and reporting for NSWO traffic are out of scope of this specification. The purpose of policy interworking via S9a for non-seamless WLAN offloaded traffic (PCC Rules provisioned for the UE local IP address) is to enable policy control in the BBF domain in two different ways: - Gate enforcement. The BPCF is expected to provide information over R interface to control whether a service data flow, which is subject to policy control, pass through the BNG if and only if the corresponding gate is open. - QoS enforcement: The BPCF is expected to provide information over R interface to control the authorized QoS of a service data flow according to the QoS information received over S9a interface. The complete specification of the BPCF is defined in BBF TR-134 [31] and BBF TR-203 [30] and BBF TR-291 [33] and it is out of the scope of 3GPP. The information contained in a PCC Rule generated by the PCRF for NSWO traffic includes Service Data Flow Detection and Policy Control information elements specified in table 6.3. The PCC rules for NSWO traffic do not include the Charging and Usage Monitoring Control elements specified in table 6.3. For Fixed Broadband Access the event triggers in table P.5.1-1 shall apply in addition to the ones in table 6.2. Table P.5.1-1: Fixed Broadband specific event triggers Event trigger Description Reported from Conditions for reporting UE local IP address change Either the UE local IP address or the UDP port number or both assigned by Fixed Broadband Access have changed PCEF, BBERF Always set H(e)NB local IP address change Either the H(e)NB IP address or the UDP port number or both assigned by Fixed Broadband Access have changed PCEF, BBERF PCRF P.5.1.1 Binding Mechanism P.5.1.1.1 EPC-routed traffic For EPC routed traffic, binding mechanisms apply as defined in clause 6.1.1 by PCRF, PCEF and BBERF. In addition, the PCC and QoS Rule generation is performed by PCRF as specified in clause 6.1.1, in addition when: - Both a Gx and associated Gateway Control Session exist for the same IP-CAN session; the PCRF shall generate QoS Rules for all the authorized PCC rules in this step. P.5.1.1.2 Non-seamless WLAN offloaded traffic The binding mechanism includes two steps for the non-seamless WLAN offloaded traffic: 1. Session binding. 2. PCC rule authorization. For NSWO traffic, session binding of AF session and TDF session (in unsolicited mode) to an IP-CAN session is performed by the PCRF, as defined in clause 6.1.1, for the purpose of policy control in the BBF domain. The PCRF derives and authorises PCC rules as described in clause 6.1.1. P.5.1.2 S9a, Gx and S15 Session Linking For WLAN, PCRF and BPCF both need to support session linking function. Depending on the deployment there may be one or multiple PCRF that have a Gateway Control Session on S9a for a given UE. The PCRF shall be able to perform the linking between IP-CAN sessions on Gx and the Gateway Control Session on S9a for the same UE based on IMSI and UE local IP address. For H(e)NB scenarios a Gateway Control Session on S9a may be linked to: - IP-CAN Sessions on Gx for all UEs connected to the H(e)NB; - Gateway Control Sessions on S9 and/or IP-CAN Sessions on S9 (in roaming cases); - S15 Session; NOTE 1: There is a single S15 session per HNB for CS calls for all UEs connected to the HNB in order to improve performance. In addition, for CS calls there are no UE specific policies and therefore a single PCRF can handle CS calls for all UEs. When the Gateway Control Session on S9a is initiated by PCRF, BPCF is expected to associate the session on R with the Gateway Control Session on S9a. NOTE 2: How the BPCF performs the association of a Gateway Control Session on S9a and R session is out of the scope of 3GPP. P.6 Functional Entities P.6.1 Policy Control and Charging Rules Function (PCRF) P.6.1.1 General The PCRF functionality defined in clause 6.2.1.0 shall apply. In addition, to support interworking with Fixed Broadband networks, the PCRF shall: - Send the QoS rules to the BPCF over S9a to request admission control in the fixed access. - Send to the BPCF the UE local IP address and UDP port number for the WLAN scenario to allow the Fixed Broadband Access to identify UE traffic. - Send to the BPCF the HeNB Local IP address and UDP port number for the Femto scenario. This allows the Fixed Broadband Access to identify IP flows corresponding to the IPSec tunnel from the HeNB GW to the SeGW which transports H(e)NB UE traffic. - Be able to be configured with the relation of IP address ranges to Fixed Broadband Access, to allow BPCF discovery. - Be able to receive from PDN GW the H(e)NB Local IP address and the UDP source port, if available, in the Fixed Broadband access network at which the H(e)NB is connected. - Be able to receive the UE local IP address and UDP source port from the ePDG (case 2a and case 2b) and PDN GW (case 1). - Be able to receive the HNB local IP address and UDP source port from HNB GW (case 1) for the HNB CS scenario. When PCRF receives the IP-CAN session establishment indication for a PDN connection initiated for a UE connected via Fixed network access, the PCRF determines if a Gateway control session is already present for this IP-CAN session. If Gateway control session is not already established, the PCRF shall trigger Gateway control session establishment procedure from the BPCF. When the UE is connecting via Fixed Broadband access network, no QoS Rules should be sent to the ePDG. The PCRF identifies when the UE is connecting via Fixed Broadband access network from the IP-CAN type. For the purpose of the policy control in the Fixed Broadband Access network for the non-seamless WLAN offloaded traffic, the PCRF shall: - Handle incoming request of IP-CAN session establishment received over S9a. - Perform session binding of the AF session information received via Rx or via S9a with an existing IP-CAN session using the UE local IP address and the IMSI (if available). - Initiate IP-CAN Session Modification and also QoS information provision for Non-seamless WLAN offloaded traffic. - Establish an Sd session with the TDF when an indication of IP-CAN session establishment is received over S9a for the UE local IP address in case of architecture variant C the solicited mode. P.6.1.2 V-PCRF The V‑PCRF functionality defined in clause 6.2.1.3 shall apply. For the purpose of Fixed Access interworking the V‑PCRF functionalities for EPC routed traffic, the following are applicable: - If a BPCF-Initiated Gateway Control Session termination is received over S9a, then the V-PCRF shall terminate a Gateway Control session over S9 with the H-PCRF. - For home routed roaming case, in case 1: - If a Gateway Control Session termination indication is received over S9 from the H-PCRF, then the V-PCRF shall trigger a Gateway Control Session termination to the BPCF. - If a Gateway Control and QoS Rules Request is received over S9 from the H-PCRF, then the V-PCRF shall trigger a Gateway Control and QoS Rules Request to the BPCF. - For both home routed and visited access roaming cases, in case 2b: - If a Gateway Control Session establishment from the BBERF (ePDG) occurs, then the V-PCRF shall establish a Gateway Control Session with the BPCF over S9a and with the H-PCRF over S9. - If the last Gateway Control Session from the BBERF (ePDG) is terminated, then the V-PCRF shall terminate the Gateway Control Session with the BPCF over S9a and with the H-PCRF over S9. - When the last PDN connection over the HNB has been terminated the V-PCRF initiates the GW Control Session Termination to the BPCF if there is no S15 session bound to the Gateway control session over S9a interface session. Otherwise, if there is a S15 session bound to the Gateway control session over S9a interface session the V-PCRF initiates the GW Control QoS rule Provision procedure to the BPCF to release the resources in the fixed broadband network. When the V-PCRF receives the Gateway Control Session establishment indication for a PDN connection initiated for a UE connected via Fixed network access, the V-PCRF determines if a Gateway Control Session is already present for this IP-CAN session. If a Gateway Control Session is not already established, the V-PCRF shall trigger a Gateway Control Session establishment procedure from the BPCF. For the purpose of BBF interworking for NSWO traffic, the V-PCRF functionalities described in the following are applicable: - For roaming scenario, V-PCRF shall handle incoming request of IP‑CAN session establishment received over S9a. - If an IP‑CAN session establishment request is received for a roaming user over the S9a reference point, then the V PCRF shall conclude that the IP‑CAN session is used for NSWO and acts as visited access network as described in clause 6.2.1.3.3. P.6.1.3 H-PCRF The H-PCRF functionality defined in clause 6.2.1.4 shall apply. For the purpose of Fixed Access interworking, the H‑PCRF functionalities defined in the following are applicable to the home routed scenario: - For case 1, if an IP-CAN Session Establishment indication is received over Gx, then if this is the first IP-CAN session for this UE the H-PCRF shall establish a Gateway Control Session to the V-PCRF over S9. - For case 1, if an IP-CAN Session Termination indication is received over Gx then if this is the last IP-CAN session for this UE, the H-PCRF shall terminate the Gateway Control session to the V-PCRF over S9. - If a PCC Rule is generated, the H-PCRF shall send QoS rules to the V-PCRF to request admission control over S9. - If a PCEF-Initiated IP-CAN Session Modification Procedure occurs over Gx to update, for WLAN scenario, the UE local IP Address and UDP port number, or, for the HeNB scenario, the HeNB local IP Address and UDP port number, then the H-PCRF shall send them to the V-PCRF. - For the purpose of BBF interworking for NSWO traffic, in case of roaming, the H-PCRF shall determine PCC rules based on home operator policy for the specific UE when it receives the IP‑CAN session establishment request from V-PCRF. P.6.2 Broadband Policy Control Function (BPCF) The BPCF is the policy Control entity in the Fixed Broadband Access network. The complete specification of the BPCF is defined in BBF TR-134 [31] and BBF TR-203 [30] and it is out of the scope of the 3GPP. For the purpose of interworking with 3GPP network the BPCF is expected to: - Perform admission control in fixed access or delegates admission control decision to other BBF nodes. Based on the admission control, the BPCF accepts or rejects the request received from PCRF over S9a. As with current S9, the BPCF may include the acceptable QoS in the reply if the request is rejected. - Translate the 3GPP QoS rule as received from PCRF over S9a interface into access specific QoS parameters applicable in the Fixed Broadband access network. - Support PCRF-triggered Gateway Control session establishment procedure over S9a. - Support Gateway Control session modification and termination procedures over S9a. The functionality of the BPCF in a roaming scenario is the same as in a non-roaming scenario. For the purpose of the policy control in the BBF domain for the Non-Seamless WLAN offloaded, the BPCF shall: - Support BPCF-initiated IP-CAN Session Establishment procedure over S9a only after successfully checking the local policies indicating that policy control for NSWO is provided. - Support IP-CAN Session Modification procedure over S9a. - Support IP-CAN Session Termination procedure over S9a. - Bind the request received on E/G from AF in the Fixed Broadband access network with an existing IP-CAN session on S9a using the UE local IP address and the IMSI ( if available). P.6.3 Bearer Binding and Event Reporting Function (BBERF) For case 2a and case 2b, the BBERF in the ePDG supports only reporting of the UE's Local IP address and UDP port number to the PCRF. Bearer binding, uplink bearer binding verification functions are not supported. For case 2b, the BBERF in the Serving GW supports those functions specified in clause 6.2.7.1 NOTE: The IP‑CAN-specific parameters provided by BBERF in Serving GW to PCRF includes the H(e)NB's Local IP address and UDP port number. P.6.4 Policy and Charging Enforcement Function (PCEF) PCEF supports those functions specified in clause 6.2.2.1. Case 1 additionally supports the reporting of the UE / H(e)NB Local IP address and the UDP port number, if available, in the Fixed Broadband Access at which the H(e)NB is connected to the PCRF. P.7 PCC Procedures and Flows P.7.1 Introduction From the network scenarios listed in clause 7.1, the Case 1 (no Gateway Control Session over Gxx interface) applies for Fixed Broadband Access for S2a-GTP, S2b-GTP, trusted S2c and H(e)NB scenarios, the Case 2b (a Gateway Control Session over Gxx interface per IP-CAN Session) applies for S2b-PMIP and case 2a (the same Gateway Control Session over Gxx interface for all IP-CAN Sessions) applies for untrusted S2c. In all information flows, the ePDG is present only in untrusted scenario case 2a and case 2b. NOTE: No policy interworking solution based on S9a is defined for Fixed Broadband access interworking via S2a within this release of the specification. P.7.2 IP-CAN Session Establishment P.7.2.0 General This procedure is applicable for WLAN and H(e)NB scenarios for EPC routed traffic and for NSWO traffic. This procedure is the same as described in clause 7.2 with the exceptions described in this clause. NOTE 1: When PCRF receives the IP-CAN session establishment indication over Gx interface, PCRF determines if a Gateway Control session is already present for this IP-CAN session. If a Gateway Control session is not already established, the PCRF shall trigger a Gateway Control session establishment procedure from the BPCF. P.7.2.1 IP-CAN Session Establishment Figure P.7.2.1: IP-CAN Session Establishment for both EPC routed and NSWO traffic This procedure is the same as described in clause 7.2 with the additions described below: 1. The BBF access network may become aware of the IMSI of the 3GPP UE if 3GPP-based access authentication (EAP-AKA/AKA') is performed. The BPCF also becomes aware of the UE local IP address. The steps from 2 to 7 show PCC signalling to provision PCC rules and ADC rules for NSWO traffic. 2. The BPCF Initiates a IP-CAN session establishment over S9a to the PCRF for non-roaming and to the V-PCRF for roaming cases, the information contained in the request message includes IMSI, IP-CAN type, local UE IP address and the NSWO-APN. Triggered by the IP-CAN session establishment over S9 the V-PCRF triggers the S9 session establishment to the H-PCRF. 3-4. The PCRF retrieves user profile from SPR as described in clause 7.2. As part of the user profile, the PCRF may receive an indication on whether policy control for NSWO traffic should be performed for that UE. 5. The PCRF enables policy control for NSWO traffic for that UE based on operator policies and user profile information that may depend on e.g. network where the UE is offloading. The PCRF sends a reply message containing PCC Rules if policy control is enabled . 6. Triggered by the successful establishment of the IP-CAN session for the UE local IP address in step 3, the V‑PCRF (roaming) and the PCRF (non-roaming) may establish a session with the TDF to provision ADC Rules for that UE local IP address (if applicable, when solicited application reporting applies and when policy control for offloaded traffic is to be performed). The PCRF provides the TDF with the UE local IP address, the IMSI, the IP-CAN type and the NSWO-APN. 7. The TDF replies as described in the clause 7.2. The steps from 6 to 10 show PCC signalling to provision policies for EPC routed traffic. 8. IP-CAN session establishment as specified in clause 7.2 is performed, including the establishment of a Gateway Control session (if applicable), as specified below with the following additional information: In case 2a and case 2b, the ePDG (BBERF) initiates a Gateway Control Session Establishment procedure to provide the UE local IP address and UDP port (if available) as defined in clause P.7.5.1. For case 1, step 3 of clause 7.2 for WLAN scenario the PCEF includes the UE local IP address and the UDP port number (if available), while for the H(e)NB scenario the PCEF includes the H(e)NB Local IP address and the UDP port number (if available) in the Fixed Broadband Access at which the H(e)NB is connected to. In case 2b, S-GW (BBERF) initiates a Gateway Control Session Establishment procedure to request QoS Rules for the H(e)NB local IP address as defined in clause P.7.5.1. The PCRF determines, based on information (UE local IP address information or H(e)NB local IP address information) provided in the IP-CAN session establishment indication or Gateway Control Session establishment indication (if applicable), whether or not the user is connecting via a Fixed Broadband Access Network. The steps in (A) show PCC signalling to establish a Gateway Control Session over S9a for EPC routed traffic. A.1. Triggered by the IP-CAN session establishment indication, or triggered by Gateway control session establishment over Gxb*, the PCRF (non-roaming case) or the V-PCRF (visited access roaming case) initiates Gateway Control Session establishment with the BPCF over S9a, if no Gateway Control Session exists for the same IMSI for WLAN scenario. The PCRF includes in the request message to BPCF the IMSI, the UE local IP address and the UDP port number (if available), QoS Rules and the ePDG IP address (for S2b-GTP access) or PDN GW IP address (for trusted S2c access), while for the H(e)NB scenario, the PCRF (Non-roaming case) or the V-PCRF (visited access roaming case) initiates Gateway Control Session establishment with the BPCF over S9a, if no Gateway Control Session exists for the same H(e)NB including the IMSI, H(e)NB Local IP address, the UDP port number (if available) and QoS Rules. For home routed, the H-PCRF initiates a Gateway Control Session over S9 to trigger the V-PCRF to establish a Gateway Control Session over S9a, for visited access, the V-PCRF initiates a Gateway Control Session over S9 to H-PCRF and the Gateway Control Session over S9a to BPCF. A.2. For WLAN scenario the BPCF Initiates the Gateway Control session establishment on S9a including in the request message the IMSI, UE Local IP address and the UDP port (if available), while for the H(e)NB scenario it includes the IMSI, H(e)NB Local IP address and the UDP port number (if available) to the PCRF. A.3. The PCRF reply message contains the result code. The steps in (B) show PCC signalling to provision QoS Rules over S9a for EPC routed traffic. B.1. Triggered by the IP-CAN session establishment indication, or triggered by Gateway control session establishment over Gxb*, the PCRF (non-roaming case) or the V-PCRF (visited access roaming case) initiates Gateway Control and QoS Rule provisioning including QoS Rules and the PDN GW IP address (for trusted S2c access and if this PDN GW IP address has not been provided before), if a Gateway Control Session exists for the same IMSI for WLAN scenario while for the H(e)NB scenario the PCRF (Non-roaming case) or the V-PCRF (visited access roaming case) initiates Gateway Control and QoS Rule provisioning, if Gateway Control Session exists for the same H(e)NB including QoS Rules. B.2. The PCRF reply message contains the result code. 9. Remaining steps of IP-CAN session establishment procedure as defined in clause 7.2 from step 6 onwards. P.7.2.2 Void P.7.3 IP-CAN Session Termination P.7.3.1 Void P.7.3.2 IP-CAN Session Termination Figure P.7.3.2: IP-CAN Session Termination for either EPC routed or NSWO traffic This procedure is applicable for both WLAN and H(e)NB scenario. For WLAN scenarios, this procedure is performed when the PCRF knows that the 3GPP UE released a PDN connection and request the BPCF to remove the PCC/QoS Rules associated to the terminated IP-CAN session or when the last PDN connection for that 3GPP UE is released to terminate the Gateway Control Session over S9a. For H(e)NB scenarios, this procedure is performed when the PCRF knows that the last 3GPP UE connecting to the H(e)NB released its last PDN connection and request the BPCF to release the Gateway Control session over S9a or when a PDN connection is released to request the BPCF to remove the QoS Rules associated with the terminated IP‑CAN session. This procedure is the same as described in clauses 7.3.1 and 7.3.2, with the new steps described below: 1. The PCEF initiates the IP-CAN session termination over Gx, as defined in the clauses 7.3.1 and 7.3.2. 2. This step is triggered by the IP-CAN session termination indication in step 3 in clauses 7.3.1 and 7.3.2, the PCRF (non-roaming case) or the H-PCRF (roaming case) initiates Gateway Control Session Termination over S9a with the BPCF if this is the last IP‑CAN session corresponding to this Gateway Control Session over S9a, or initiates Gateway Control and QoS Rule Provisioning over S9a to remove QoS Rules for the purpose to release resources in the Fixed Broadband Access. NOTE: For case 2b, the description of the Gateway Control Session Termination procedure over Gxb* when triggered by the ePDG (BBERF) is described in clause P.7.5.2 and the description of the Gateway Control and QoS Rule request procedure when triggered by the ePDG (BBERF) is described in clause P.7.5.3. For case 2a, the description of the Gateway Control Session Termination procedure over Gxb* when triggered by the PCRF is described in clause P.7.5.4. 3. The BPCF reply message contains the result code. 4. Remaining steps of IP-CAN session termination as described in clause 7.3 from step 4 onwards, with the additions that in .case 2a and roaming scenario, triggered by step2, the vPCRF initiates the Gateway control session termination with the ePDG over Gxb* if the Gateway control session over S9a bound to that IMSI has been terminated. Steps 5, 6, 7 and 8 are triggered when the BBF access is aware that the UE is detached from BBF access. These steps are not necessarily performed at termination of the IP-CAN session but may occur at a later time. 5. If the BBF access network is aware of the UE is detached from the BBF access network, the BPCF Initiates IP-CAN session termination to the PCRF (non-roaming) and the V-PCRF (for roaming cases). Triggered by the IP-CAN session termination over S9a, the V-PCRF triggers the IP-CAN session termination over S9. 6. The PCRF reply message contains the result code for the IP-CAN session terminated. 7. Triggered by step 6, the PCRF (for non-roaming case) and the V-PCRF (for roaming cases) terminates the TDF session, if exists for the UE local IP address as described in the clause 7.3. 8. The TDF replies as described in the clause 7.3. P.7.4 IP-CAN Session Modification Both the PCRF-initiated IP-CAN Session Modification Procedure and the PCEF-initiated IP-CAN Session Modification Procedures as described in clause 7.4 are applicable for a 3GPP UE that attaches via a Fixed Broadband Access. P.7.4.1 PCEF-Initiated IP-CAN Session Modification Figure P.7.4.1: PCEF-initiated IP-CAN Session Modification This procedure is applicable for WLAN and H(e)NB scenario. This procedure is performed when the UE Local IP address, H(e)NB Local IP address or the UDP port number is changed and/or when a request for PCC Rules is received from the PCEF. This procedure is the same as described in clause 7.4.1 with the additions described below: Step 3 in case 1, the PCEF provides the updated UE local IP address, the updated H(e)NB IP address and/or UDP port number to the PCRF. 1. The PCRF (non-roaming case) initiates Gateway Control and QoS Rule Provisioning with the BPCF to provide either: a. QoS-Rule with the QoS control information (i.e. QCI, GBR, MBR, ARP) and SDF information; and/or b UE local IP address and/or the UDP port number, the H(e)NB Local IP address may be provided in the request; c. Information (e.g. Session ID) that allows the BPCF to associate the request with the existing Gateway Control Session on S9a so that the fixed access can identify the traffic plane resources that are affected. The H-PCRF (home routed roaming case) provisions for WLAN case the UE local IP address and UDP port number (if available) and for H(e)NB case the H(e)NB local IP address and UDP port number (if available) to the V-PCRF to trigger the provisioning over S9a. 2. The BPCF translates the QoS rule as received of the S9a interface (i.e. SDF information, QCI, GBR, MBR and ARP) into access specific QoS parameters applicable in the BBF domain (the details of the mapping from 3GPP QoS parameters on S9a to QoS parameters applicable in the BBF domain is out of 3GPP scope). The BPCF may respond with a "counter-offer" in form of acceptable bandwidth and/or QoS for one or more SDFs if it cannot provide the requested QoS from the PCRF. The BPCF provides the acceptable QoS in the BBF access using 3GPP QoS parameters (i.e. QCI, GBR, MBR and ARP) and SDF information on S9a interface in the reply if the QoS validation for admission control fails. The PCRF may make a new policy decision, e.g. decide to modify or remove the affected QoS rules. NOTE: For H(e)NB PMIP scenario, Gateway Control and QoS Rule Provisioning to the BBERF may be performed as described in clause 7.4.1. P.7.4.2 PCRF-Initiated IP-CAN Session Modification This procedure is initiated by the PCRF (non-roaming) or by the V-PCRF (roaming). The (V-)PCRF requests the BPCF to perform admission control. Steps (A) show how to provision QoS Rules for the UE IP address(es) allocated by EPC and received over Gx and Steps (B) show how to provision PCC Rules to request admission control for the IP-CAN session for the UE local IP address received over S9a. Note that the TDF that is selected for EPC routed and NSWO traffic may or may not be the same TDF. Figure P.7.4.2: PCRF-Initiated IP-CAN Session Modification This procedure is applicable for WLAN and H(e)NB scenario. This procedure is the same as described in clause 7.4.2 with the additions described below: 1a, 2a. 1b. The AF or the TDF provides/revokes service information to the PCRF and detected event triggers if applicable as described in steps 1a, 2a and 1b in clause 7.4.2. For roaming case and for NS-WLAN offloaded traffic, the TDF provides service information and event triggers detected to the V-PCRF. 3. The PCRF for non-roaming cases or the H-PCRF for roaming cases, makes the authorization and policy decision. 4. The PCRF acknowledges to the TDF as described in clause 7.4.2. A: The steps in (A) show PCC signalling to provision QoS Rules for EPC routed traffic. A.1. Triggered by the step 1, the PCRF (non-roaming case) or the v-PCRF (roaming case) initiates Gateway Control and QoS Rule Provisioning to provide: a. QoS-Rule with the QoS control information (QCI, GBR, MBR, ARP) and SDF information. b. Information (e.g. Session ID) that allows the BPCF to associate the request with the existing Gateway Control Session on S9a so that the fixed access can identify the traffic plane resources that are affected. A.2. The BPCF translates the QoS rule as received of the S9a interface (i.e. QCI, MBR, GBR and ARP) into access specific QoS parameters applicable in the BBF domain (the details of the mapping from 3GPP QoS parameters on S9a to QoS parameters applicable in the BBF domain is out of 3GPP scope). The BPCF may respond with a "counter-offer" in form of acceptable bandwidth and/or QoS for one or more SDFs if it cannot provide the requested QoS from the PCRF. The BPCF provides the acceptable QoS in the BBF access using 3GPP QoS parameters on S9a interface (i.e. QCI, GBR) in the reply if the QoS validation for admission control fails. The PCRF may make a new policy decision, e.g. decide to modify or remove the affected QoS rules. A.3. PCC Rules are installed in the PCEF as described in clause 7.4.2 and AF is notified if subscribed to the notification of the resource allocation request/modification. B: The steps in (B) show PCC signalling to provision PCC Rules for NS-WLAN offloaded traffic. B.1. Triggered by the step 3, the PCRF (non-roaming case) or the H-PCRF (roaming case) initiates Policy Rule Provisioning towards the BPCF to provide QoS-Rules for the UE local IP address. B.2. The BPCF translates the PCC rules as received of the S9a interface (i.e. SDF information, QCI, MBR, GBR and ARP) into access specific QoS parameters applicable in the BBF domain as described in A.2. B.3. If the AF requested it, the PCRF notifies the AF (e.g. transmission resources are established/released/lost). B.4. The AF acknowledges the notification from the PCRF. P.7.4.3 BPCF-Initiated IP-CAN Session Modification Figure P.7.4.3: BPCF-Initiated IP-CAN Session Modification The trigger for this procedure is that the BPCF has pre-empted some resources and wants to report a QoS rule failure to the PCRF, or when the BBF network cannot sustain the Bandwidth allocated to a particular traffic class/DSCP aggregate. This procedure is applicable for both WLAN and H(e)NB scenarios. NOTE: Whether additional condition and criteria specific for BBF network and defined by BBF forum are applicable for trigger BPCF-Initiated IP-CAN session modification is out of the scope of 3GPP definition. A: The steps in (A) show PCC signalling to report QoS Rule failure to PCRF for the EPC routed traffic. A.1. The BPCF initiates Gateway Control and QoS Rule Request to report QoS Rule failure to PCRF. The request includes a report identifying the QoS Rules that failed and a reason. A.2. The PCRF acknowledge the request and may initiate PCRF-initiated IP-CAN session modification. Step 5 to 14 is the same as described in clause 7.4.2. A.3. If the AF requested it, the PCRF notifies the AF (e.g. transmission resources are released). A.4. The AF acknowledges the notification from the PCRF. A.5. The PCRF-initiated IP-CAN session modification as described in clause P.7.4.2 may take place. B: The steps in (B) show PCC signalling to report PCC Rule failure to PCRF for NSWO traffic. B.1. The BPCF initiates IP-CAN session modification to report PCC Rule failure to PCRF. A.2. The PCRF acknowledges the request. A.3. If the AF requested it, the PCRF notifies the AF (e.g. transmission resources are released). A.4. The AF acknowledges the notification from the PCRF. P.7.5 Gateway Control Session Procedures P.7.5.1 BBERF-Initiated Gateway Control Session Establishment Figure P.7.5.1: PCRF-triggered Gateway Control Session Establishment for EPC routed traffic This procedure is applicable for both WLAN and H(e)NB PMIP. This procedure is the same as described in clause 7.7.1.1 with the additions described below: 1. For the WLAN case, the ePDG (BBERF) initiates a Gateway Control Session Establishment as defined in clause 7.7.1 with the PCRF (for non-roaming) and with the V-PCRF (for home routed and visited access roaming cases) including the IMSI, APN (if available), the UE Local IP address, the UDP port number if available, while for H(e)NB case the SGW (BBERF) initiates a Gateway Control Session Establishment as defined in clause 7.7.1 with the PCRF (for non-roaming) and with V-PCRF (for home routed and visited access roaming case) including the H(e)NB local IP address and the UDP port number (if available) in the Fixed Broadband Access at which the H(e)NB is connected to. 2. For WLAN case, the PCRF (non-roaming case) or the V-PCRF (home routed and visited access roaming cases) triggers Gateway Control Session establishment with the BPCF over S9a, if this is the first Gateway Control Session for the same IMSI, the PCRF includes in the request message to BPCF the IMSI, the UE local IP address and the UDP port number (if available) and the ePDG IP address (for S2b-PMIP and untrusted S2c access). For the H(e)NB case, the PCRF (non-roaming case) or the V‑PCRF (home routed and visited access roaming cases) triggers Gateway Control Session establishment with the BPCF over S9a, if this is the first Gateway Control Session for the same H(e)NB, the PCRF includes in the request message to BPCF the IMSI, the H(e)NB IP address and the UDP port number (if available). 3. The BPCF Initiates the Gateway Control session establishment to the PCRF (for non-roaming case), to the V-PCRF (for visited access and home routed roaming case) including in the request message the IMSI. Triggered by the BPCF-initiated Gateway Control Session establishment over S9a the V-PCRF sends the Gateway Control Session Establishment over S9. 4. The PCRF in non-roaming and the V-PCRF for roaming cases reply message contains the result code. 5. For H(e)NB case, the PCRF provisions QoS Rules to the BBERF, while for the WLAN case, the PCRF sends a result code in the reply message. No QoS Rules and no event triggers are provided to the BBERF for WLAN scenarios. P.7.5.2 GW (BBERF)-Initiated Gateway Control Session Termination Figure P.7.5.2: Gateway Control Session Termination over S9a This procedure is applicable for both WLAN and H(e)NB scenarios. This procedure is the same as described in clause 7.7.2.1 with the additions described below: 1. For WLAN scenarios, the ePDG (BBERF) initiates a Gateway Control Session Termination with the PCRF (for non-roaming) and with the V-PCRF (for home routed and visited access roaming cases). For H(e)NB scenarios, the SGW (BBERF) initiates a Gateway Control Session Termination as defined with the PCRF (for non-roaming) and with the V-PCRF (for home routed and visited access roaming cases). 2. The PCRF sends a response code. 3. The PCRF (non-roaming case) or the V-PCRF (roaming case) initiates a Gateway Control Session Termination over S9a with the BPCF to terminate the Gateway Control Session with the BPCF if this is the last Gateway Control Session bound to the Gateway Control session over S9a. 4. The BPCF terminates the Gateway Control Session over S9a to the PCRF. In the roaming scenario, V-PCRF (for both home routed and visited access) sends a Gateway Control Session Termination over S9 to the PCRF. 5. The PCRF sends a response code. P.7.5.3 Gateway Control and QoS Rule Request from ePDG/Serving GW Figure P.7.5.3: Gateway Control and QoS Rule Request for EPC Routed Traffic This procedure is applicable for both WLAN and H(e)NB PMIP. This procedure is the same as described in clause 7.7.3.1 with the exceptions described below: In case 2b and case 2a for WLAN scenario, the ePDG (BBERF) may initiate a Gateway Control and QoS Rules Request Procedure to provide the updated UE local IP address and the UDP port number, if available, while for H(e)NB scenario the SGW (BBERF) may initiate a Gateway Control and QoS Rule Procedure to provide the updated H(e)NB local IP address and the UDP port number (if available) in the Fixed Broadband Access at which the H(e)NB is connected to. 1. For the WLAN scenario, triggered by the Gateway Control and QoS Rules Request Procedure in step 2 of clause 7.7.3.1, the PCRF (non-roaming case) or the v-PCRF (roaming case) initiates Gateway Control and QoS Rules Provision Procedure. The updated UE local IP address and/or the UDP port number are provided in the procedure if available, while for H(e)NB scenario the PCRF (non-roaming) or the H-PCRF (for visited access and home routed) may initiate a Gateway Control and QoS Rule Procedure to provide the updated H(e)NB local IP address and the UDP port number (if available) in the Fixed Broadband Access at which the H(e)NB is connected to. For H(e)NB PMIP scenario, the PCRF may provide: a. QoS-Rule with the QoS control information (i.e. QCI, GBR, MBR, ARP) and SDF information. b. Information (e.g. Session ID) that allows the BPCF to associate the request with the existing Gateway Control Session on S9a so that the fixed access can identify the traffic plane resources that are affected. 2. The BPCF replies with a response code, when QoS Rules were provided by the PCRF, the BPCF translates the QoS rule as received of the S9a interface into access specific QoS parameters applicable in the BBF domain . The BPCF may respond with a "counter-offer" in form of acceptable bandwidth and/or QoS for one or more SDFs if it cannot provide the requested QoS from the PCRF. The BPCF provides the acceptable QoS in the BBF access using 3GPP QoS parameters on S9a interface (i.e. QCI, GBR) in the reply if the QoS validation for admission control fails. The PCRF may make a new policy decision, e.g. decide to modify or remove the affected QoS rules. NOTE: For H(e)NB PMIP scenario, Gateway Control and QoS Rule Provisioning to the BBERF may be performed as described in clause 7.4.1. P.7.5.4 PCRF-Initiated Gateway Control Session Termination Figure P.7.5.4: PCRF-Initiated Gateway Control Session Termination This procedure is applicable for WLAN scenario. This procedure is the same as described in clause 7.7.2.2 steps 1 with the additions described below: 1. For the non-roaming and roaming home routed cases, triggered by step 1 in clause 7.7.2.2, the (h)PCRF sends a PCRF-initiated Gateway Control Session termination procedure with BPCF over S9a. For the roaming LBO case, triggered by step 1 in clause 7.7.2.2, the (v)PCRF sends a PCRF-Initiated Gateway control session termination procedure with BPCF over S9a. 2. The BPCF sends PCRF-Initiated Gateway Control Session Termination acknowledgement. 3. Triggered by step 1 in clause 7.7.2.2, the (h)PCRF (for non-roaming case and home routed roaming case) sends a PCRF-initiated Gateway Control Session Termination over Gxb* with the ePDG (BBERF). Triggered by the Gateway Control Session Termination over S9a and S9 with the BPCF, the V-PCRF (roaming LBO case) sends a PCRF-initiated Gateway Control Session Termination over Gxb* with the ePDG (BBERF). 4. The ePDG (BBERF) sends a sends PCRF-Initiated Gateway Control Session Termination acknowledgement. P.7.6 PCRF Discovery and Selection P.7.6.1 PCRF Discovery and Selection by BPCF When the BPCF knows that a 3GPP UE attached via a Fixed Broadband access network and learns the IMSI and the NSWO-APN, the BPCF initiates the IP-CAN session establishment for NSWO offloaded traffic, the BPCF finds the PCRF using the DRA as described in clause 7.6.1. When the BPCF is requested to establish a Gateway Control Session over S9a by PCRF, the BPCF uses the PCRF address provided in the request to establish the Gateway Control Session over S9a. In roaming scenarios, the selected V-PCRF shall belong to the same V-PLMN selected during the 3GPP access authentication procedure. The BPCF uses the VPLMN id to find the V-DRA in the VPLMN. The V-PCRF finds the DRA in the HPLMN based on the IMSI and the APN if available as described in clause 7.6.1. P.7.6.2 PCRF Discovery and Selection by AF/TDF unsolicited application reporting for NS-WLAN offloaded traffic For PCRF discovery and selection by AF/TDF unsolicited application reporting for NS-WLAN offloaded traffic the procedure described in clause 7.6.1 applies. P.7.6.3 PCRF Discovery and Selection by HNB GW When the DRA receives a request for a certain S15 Session establishment from the HNB GW, the DRA selects a suitable PCRF for the S15 Session based on HNB local IP address. When the S15 Session terminates, the DRA shall remove the information about the S15 Session. P.7.7 BPCF Discovery and Selection For PCRF-triggered Gateway Control Session establishment, the PCRF (for non-roaming case) and the V-PCRF (for home routed and visited access roaming cases) is configured with IP address range mappings { (IPx..IPy) ‑> BBF network entry point}. The PCRF (for non-roaming) and the V-PCRF (for roaming cases) selects the correct BBF network entry point based on UE Local IP address for WLAN access and based on H(e)NB Local IP address received from the PCEF/BBERF for H(e)NB case. The implementation of a BBF network entry point is out-of-scope for 3GPP e.g. be a BPCF or a DRA. The H-PCRF sends the H(e)NB/UE local IP address to the V-PCRF over the S9 interface. For WLAN and H(e)NB in Home Routed roaming case, for PCRF-triggered Gateway Control Session establishment, H-PCRF finds V-DRA according to the VPLMN ID if received via Gx session and then discovers V-PCRF by V-DRA. V-PCRF selects the correct BBF network entry point with the given UE local IP address and the H(e)NB Local IP address in the BBF access network at which the H(e)NB is connected to respectively. NOTE: Mobility procedures that implies selection of a new BPCF are not supported in this Release. P.7.8 TDF Discovery and Selection for NS-WLAN offloaded traffic For the solicited application reporting, the TDF address may be preconfigured in the PCRF. Alternatively, the PCRF may receive the TDF address as a part of IP-CAN session signalling for NS-WLAN offloaded traffic over S9a. NOTE: It is assumed that UL and DL traffic are routed via the same TDF. P.8 3GPP HNB Procedures – CS Support P.8.1 S9a CS Session Establishment Figure P.8.1-1: S9a CS Session Establishment This procedure is applicable to HNB for QoS enforcement for CS services. 1) S15 session establishment procedure is performed, which can be referred to step 4-5, clause 9.4.1, TS 23.139 [29]. 2) The (v-)PCRF initiates Gateway Control Session Establishment procedure with BPCF. The description of this step is the same as steps (A) in clause P.7.2.1. P.8.2 PCRF initiated S9a CS Session Modification Figure P.8.2-1: PCRF initiated S9a CS Session Modification This procedure is performed when the first UE or a subsequent UE connected to a HNB requesting a CS call. 1) The HNB GW sends the S15 session modification message to the PCRF, which can be referred to clause 9.4.2, step3 of TS 23.139 [29]. 2) The PCRF (V-PCRF) initiates the Gateway Control and QoS Rules Provisioning procedure to the BPCF as described in step from A.1 to A.2 in clause P.7.4.2. 3) The remaining steps are the same as for clause 9.4.2, steps 5-7 of TS 23.139 [29]. P.8.2A BPCF initiated S9a CS Session Modification Figure P.8.2A-1: BPCF initiated S9a CS Session Modification 1) This step shows PCC signalling to report QoS Rule failure to (v)PCRF for the CS traffic. NOTE: Whether additional condition and criteria specific for BBF network and defined by BBF forum are applicable for trigger BPCF-Initiated S9a CS Session Modification is out of the scope of 3GPP definition. The BPCF initiates Gateway Control and QoS Rule Request to report QoS Rule failure to (v)PCRF. The request includes a report identifying the QoS Rules that failed and a reason. The (v)PCRF acknowledges the request. 2) The (v)PCRF sends the S15 session modification request message to the HNB GW. The (v)PCRF includes the report identifying the QoS Rules that failed and a reason derived from the BPCF. The BPCF response the S15 session modification to the (v)PCRF, which is according to TS 23.139 [29]. P.8.3 S9a CS Session Termination Figure P.8.3-1: S9a CS Session Termination 1) The HNB GW sends a S15 session termination request to the to (v-)PCRF and then the (v-)PCRF acknowledges the request. This can be referred to clause 9.4.3, step 2 of TS 23.139 [29]. 2) The PCRF (V-PCRF) initiated the GW control session termination as defined in steps 2 and 3 in clause P.7.3.2. Annex Q (informative): How to achieve Usage Monitoring via the OCS An alternative to providing the usage monitoring feature described in this technical specification is to re-use the capabilities defined in 3GPP Release 11 for implementation of Policy Control based on Subscriber Spending Limits when online charging is also performed. There are two ways defined in this Annex to achieve usage monitoring via OCS: If PCC/ADC rules that are subject to usage monitoring share the same charging key, the same measurement methods then the Usage Reports over Gy are used for both charging and usage monitoring and in addition: - Policy Counter Status values are associated with the quota allocated with Charging Keys are configured in the OCS. Policy Counter Status (INQUOTA, OUTQUOTA) changes trigger notifications over Sy. - The PCRF is configured with operator policies that associate the policy counter status to a policy decision e.g. block or allow a service to a QoS. If PCC/ADC rules that are subject to usage monitoring have different charging keys and/or different measurement methods then to achieve a common usage report over Gy then: - A common Charging Key is used for all services that are subject to usage monitoring. The charging control information of the PCC/ADC rules includes that online charging applies, the common charging key for the service and service level reporting is activated. In addition, the measurement method is to be set to time/volume. - Policy Counter Status values associated with the quota allocated with Service identifier is configured in the OCS. Policy Counter Status (INQUOTA, OUTQUOTA) changes trigger notifications over Sy. - The PCRF is configured with operator policies that associate the policy counter status to a policy decision e.g. block or allow a service to a QoS. Figure Q.1-1: Deployment for Usage Monitoring via Online Charging System Annex R (informative): Disabling/re-enabling Usage Monitoring for a PCC/ADC rule If usage monitoring for a PCC/ADC rule (belonging to a usage monitoring group) needs to be disabled, one of the two ways below can be chosen to realize this feature: - The PCRF generates a new PCC/ADC rule with the same information (apart from the PCC/ADC Rule identifier) as the existing PCC/ADC rule used to control the same traffic but without the monitoring key. The PCRF provides the new PCC/ADC rule to the PCEF/TDF and removes the existing PCC/ADC rule. NOTE 1: It is assumed that the activation of the new PCC/ADC rule takes place at the same time as the removal of the existing PCC/ADC rule and that no other actions are triggered (e.g. with respect to charging and bearer management) beside the ones related to the disabling of usage monitoring. - The operator selects a specific monitoring key value to be used for all PCC/ADC rules for which usage monitoring is disabled. The PCRF modifies the monitoring key of the corresponding PCC/ADC rule to this specific value. Following the PCRF instruction, the PCEF or TDF updates the monitoring key in the modified PCC/ADC rule and collects the usage information for the specific monitoring key value. The PCEF/TDF usage reports would still be received by the PCRF but could be ignored. NOTE 2: The operator should configure the usage threshold to a sufficiently high value so that frequent usage reports are avoided. If usage monitoring needs to be re-enabled for a PCC/ADC rule (i.e. usage monitoring has been disabled for this PCC/ADC rule before), one of the two ways below can be chosen to realize this feature: - The PCRF generates a new PCC/ADC rule with the same information (apart from the PCC/ADC Rule identifier) as the existing PCC/ADC rule used to control the same traffic and adds the required monitoring key. The PCRF provides the new PCC/ADC rule to the PCEF/TDF and removes the existing PCC/ADC rule without monitoring key. The PCEF/TDF executes the operations in the same way it is described above in Note 1. - The PCRF modifies the monitoring key of the corresponding PCC/ADC rule to the value of the required usage monitoring group (e.g. back to its original value). Annex S (normative): Fixed Broadband Access S.1 General This annex specifies the enhancement to PCC framework for supporting policy and charging control in the fixed broadband access network in the convergent scenario where a single operator is deploying both the fixed broadband access network and the Evolved Packet Core (EPC). The scope of this Annex is to define requirements for the convergent scenario where the PCRF controls directly the network element(s) in the fixed broadband access without the mediation of a different policy server, such as the BPCF defined in Annex P. Policy and charging control is provided for both Non-seamless WLAN offload traffic from a 3GPP UE and fixed devices. The work in this annex takes the fixed broadband accesses as specified by BroadBand Forum in TR-300 [37] as a reference. NOTE 1: This does not preclude the applicability of the solutions described in this Annex to fixed broadband accesses not defined by Broadband Forum. This annex is a realization of the main specification body for the Fixed Broadband Access IP-CAN. It describes only the exceptions and additions in respect to the main specification body, therefore, if not explicitly mentioned, the main specification body is applicable. NOTE 2: Support for MPS Services and IMS Emergency is not specified in this Release. S.2 Definitions The definitions in the following are relevant for this annex only. UE local IP address: Defined as either the public IP address assigned to the UE by the Broadband Forum domain in the no-NAT case, or the public IP address assigned by the Broadband Forum domain to the NATed RG. IP-CAN session: For fixed broadband access, the IP-CAN session can also be identified primarily by an IP address(es). The term UE corresponds to the device that access the services provided by the network (i.e. either RG, or 3GPP UE or fixed end-device), the PDN identifies the IP network where the device gets IP connectivity and the UE identity information may be the IMSI, the user-name or the access line identifier (if available). In a Fixed Broadband Access an IP-CAN session corresponds to a Subscriber IP Session defined in TR-146 [36]. NOTE: The PDN connection concept and APN are not applicable to Subscriber IP session for fixed device. S.3 High Level Requirements S.3.0 General The same requirements as defined in clause 4 4 to support usage monitoring and clause 4.5 to support application detection and control applies. S.3.1 General Requirements The same requirements as defined in clause 4 applies with the following exception and addition: - For Fixed devices the policy and charging control shall be possible only in non- roaming scenario. - For Fixed Broadband Access, PCC decisions shall be based on subscription information for both fixed device and/or fixed access line. - PCRF shall control directly the PCEF in the IP-Edge in the fixed broadband access without the mediation of the BPCF defined in TS 23.139 [29]. NOTE 1: In this Release of the specification, Policy and charging control for layer 2 sessions are out of the scope. - An IP-CAN session shall be established on the IP-Edge per IPv4 address and/or IPv6 address or IPv6 prefix known in the IP-Edge. PCC shall be supported for both the IP-CAN session established for the RG and for each IP-CAN session created for every device (i.e. fixed device or 3GPP UE) behind the RG that is visible in the IP-Edge/PCEF. NOTE 2. In this Release the identification of end-user devices behind a RG configured in routed mode is not supported. NOTE 3: In this Release of the specification, there is no support for IMS-based emergency services. NOTE 4: In this Release of the specification, there is no support for traffic steering control. S.3.2 Charging Related Requirements The same requirements as defined in clauses 4.2.1, 4.2.2 and 4.2.2.a apply, with the exception and addition listed in the following: - The architecture shall provide charging for traffic exchanged by fixed devices and NSWO traffic to/from 3GPP UEs in the following scenarios: - 3GPP IP-Edge based charging with PCEF located in the fixed broadband access network; - Traffic Detection Function (TDF)-based charging; - AAA-based charging, - The requirements for the AAA-based charging solution are described in clause S.8. NOTE 1: The selection of which accounting methods enabled is based on deployment option and there is no dynamic capability negotiation. NOTE 2: The same accounting method is applicable to all devices connected to the same fixed broadband access network. Charging interaction per device (i.e. fixed device or 3GPP UE) is possible only when an IP-CAN session exists for the 3GPP UE or fixed device connected behind a RG. NOTE 3: For a 3GPP UE or a fixed device behind a NATed RG it is not possible to perform charging for that specific device. Inter operator settlements are assumed to ensure support of the case of an UE receiving NSWO over a Fixed Broadband Access (FBA), when the HPLMN and the FBA Service Provider support different charging options. It shall be possible for the charging system to select the applicable rate based on: - home/visited IP‑CAN; - QoS provided for the service; - Time of day; - Location of the subscriber. - Subscriber identifier. Home/visited IP-CAN is not applicable for charging of fixed devices. S.3.3 Policy Control Requirements The same requirements as defined in clause 4.3 applies with the exception and addition listed below: - The PCEF in the IP-Edge shall be able to enforce policies and to perform the appropriate mapping from QoS parameters it receives from the PCRF to Broadband Forum specific parameters. NOTE: How the IP-Edge performs such mapping is out of 3GPP scope. - PCC shall provide QoS control on a service data flow/detected application traffic basis, for IP traffic exchanged by fixed devices and for NSWO traffic exchange by 3GPP UEs in the fixed broadband access. - Requirements for QoS control at IP-CAN bearer level defined in clause 4.3.3.2 are not applicable for Fixed Broadband Access. S.4 Architecture model and reference points S.4.1 Reference architecture S.4.1.1 General The reference architecture described in clause 5.1 and shown in figures S.4.1.2-1 and S.4.1.3-1 applies with the exception and addition listed in the following: - PCEF resides in the IP-Edge in the Broadband Forum access network; - Gxx reference point is not used. NOTE 1: Either SPR or UDR is used in this architecture. NOTE 2: The roaming scenario is not applicable to fixed device and RG. S.4.1.2 Reference architecture - Non-Roaming Figure S.4.1.2-1: PCC Reference architecture for Fixed Broadband Access convergence when SPR is used S.4.1.3 Reference architecture - Roaming Figure S.4.1.3-1: PCC Reference architecture for Fixed Broadband Access convergence (roaming) when SPR is used S.4.2 Reference points S.4.2.1 Gx Reference Point This reference point corresponds to the Gx which resides between the PCEF in the IP-Edge and the PCRF. The same functionality as defined in clause 5.2.2 with the following exceptions: - No provisioning of IP flow mobility routing information from PCEF to PCRF is performed. - Negotiation of IP‑CAN bearer establishment mode (UE-only or UE/NW) does not apply. In addition, for the purpose of convergence between 3GPP access and Broadband Forum access network, the Gx reference point enables the transfer of PCC rules for an IP-CAN session that exists in the PCEF for a fixed device or for a 3GPP UE. S.4.2.2 Sp Reference Point For the purpose of policy and charging control convergence between 3GPP and Broadband Forum access network, the Sp reference point allows the PCRF to request subscription information from the SPR based on a subscriber ID that is defined in clause S.5.2.1. When the subscriber Id is an IMSI, the PDN identifier is the NSWO-APN. When the subscriber Id is used to identify a fixed device no PDN identifier is applicable. NOTE 1: The naming convention of NSWO-APN is left to operator's implementation decision. S.4.2.3 Ud Reference Point For the purpose of convergence between 3GPP access and Broadband Forum access network, the Ud reference point provides the same functionality as the Sp reference point described in clause S.4.2.2. S.4.2.4 Gy/Gz Reference Point These reference points provide the same functionality as defined in the clauses 5.2.4 and 5.2.5 respectively. For the purpose of convergence between 3GPP access and BBF access network, the functions of credit management and reporting is defined in clause S.5.1.6. The Gz and Gy interfaces are specified in TS 32.240 [3] and the functionalities required across the Gz and Gy reference point are defined in TS 32.251 [9]. S.4.2.5 Gyn/Gzn Reference Point These reference points provide the same functionality as defined in the clause 5.2.10 and 5.2.11 respectively. In addition for the purpose of convergence between 3GPP and BBF access network, the functions of credit management and reporting are defined in clause S.5.1.6. The Gzn and Gyn interfaces are specified in TS 32.240 [3] and the functionalities required across the Gzn and Gyn reference point are defined in TS 32.251 [9]. S.4.2.6 Sd Reference Point For the purpose of convergence between 3GPP and Broadband Forum access network, the Sd reference point allows PCRF to have dynamic control over the application detection and control behaviour at a TDF for a fixed device or for a 3GPP UE. The Sd reference point enables the signalling of ADC decision, which governs the ADC behaviour. The Sd reference point provides the same functionality as the Sd described in clause 5.2.8. S.5 Functional description S.5.1 Overall description The purpose of PCC convergence is to enable the policy and charging control for NSWO traffic from 3GPP UE connected to the fixed broadband access network and for the traffic from fixed devices with where the PCRF controls directly the network element(s) in the fixed broadband access without the mediation of a different policy server, such as the BPCF defined in TS 23.139 [29]. In this release, EPC-routed traffic from 3GPP UE connected to connected fixed broadband access network is considered outside the scope. The binding mechanism, credit management, reporting, usage monitoring, termination actions, service data flow prioritization, ADC Rule definition and operations, PCC Rule definition and operations and standardized QoS characteristics as defined in clause 6.1 shall apply. Handling of packet filters provided to the UE by the PCEF as defined in clause 6.1.9 is not applicable for Fixed Broadband Access. S.5.1.1 IP-CAN Session For routed mode RG with NAT, one IP-CAN session shall be established for each corresponding Subscriber IP session on the IP-Edge for the IPv4 address and/or IPv6 address or IPv6 prefix assigned to the RG. In case of routed mode RG when the PPP pass-through feature is enabled (see requirement R-10 in TR‑124 Issue 3 [34b]) an IP-CAN session shall be established for the each single fixed device starting the PPP session. In this case the 3GPP UE does not have Subscriber IP session in IP-Edge. For bridged mode RG, one IP-CAN session shall be established for each corresponding Subscriber IP session on the IP-Edge for each IPv4 address and/or IPv6 address or IPv6 prefix assigned to the fixed device or 3GPP UE which established a Subscriber IP session in fixed broadband network. For routed mode RG with IPv6 when stateless IPv6 address autoconfiguration is used by the end-device behind the RG, one IP-CAN session shall be established for each corresponding Subscriber IP session on the IP-Edge for the IPv6 prefix assigned to the RG. When stateful IPv6 address configuration is used by the end-devices, one IP-CAN session may be established for each end-device. For routed mode RG, the successful completion of 3GPP-based access authentication and assignment of IP address to the 3GPP UE shall not result in any IP-CAN session establishment if the IP address assignment does not result in a new Subscriber IP Session in the IP-Edge. In this case the pre-existent IP-CAN session for the RG is used. A device connected to the RG (e.g. VoIP phones) may also initiate a Subscriber IP session when the RG is configured in bridge mode or when the PPP pass-through feature is enabled on the Routing RG (see requirement R-10 in TR‑124 Issue 3 [34b]). S.5.1.2 Subscriber Identifier The Subscriber ID represents the identity of the User. For the 3GPP UE the Subscriber ID is the IMSI. The Subscriber ID used by fixed device at establishment of Subscriber IP session in fixed broadband access network can be the Access Line Identifier (physical and logical circuit ID) or the username, for example when the Subscriber IP session is a PPP Session. For the RG and fixed device based on Broadband Forum specification, the Subscriber ID is defined in Broadband Forum WT 134 [31] specification. S.5.1.3 Event triggers The fixed broadband access network in the convergent scenario supports the Event triggering mechanisms described in clause 6.1.4. The event triggers applicable are listed in the following: Table S.5.1.3-1: Event triggers Event trigger Description Reported from Condition for reporting QoS change The QoS of the Default Access Profile in AAA has changed PCEF PCRF Out of credit (see note 1) Credit is no longer available. PCEF, TDF PCRF Enforced ADC rule request TDF is performing an ADC rules request as instructed by the PCRF. TDF PCRF Usage report The IP-CAN/TDF session or the Monitoring key specific resources consumed by a UE either reached the threshold or needs to be reported for other reasons. PCEF, TDF PCRF Start of application traffic detection and Stop of application traffic detection (see note 2) The start or the stop of application traffic has been detected. PCEF, TDF PCRF Credit management session failure (see note 1) Transient/Permanent Failure as specified by the OCS PCEF, TDF Always set NOTE 1: This event may apply only when Gy and/or Gyn are deployed. NOTE 2: This event may only be triggered by a PCEF enhanced with ADC. S.5.1.4 Void S.5.1.5 Void S.5.1.6 Credit management For the purpose of credit management of an IP-CAN session for a fixed devices or a 3GPP UE using NSWO, the description in clause 6.1.3 applies with the following exceptions: the subscription identity is provided by PCEF or TDF to the OCS as defined in S.5.1.2 and the applicable credit-reauthorization triggers are defined in the table S.5.1.6-1: Table S.5.1.6-1: Credit re-authorization triggers Credit re-authorization trigger Description Applicable for Credit authorisation lifetime expiry (see note 1) The OCS has limited the validity of the credit to expire at a certain time. PCEF, TDF Idle timeout (see note 1) The service data flow identified by a PCC Rules or the application identified by an ADC Rule has been empty for a certain time. PCEF, TDF QoS changes The QoS of the access network profile has changed. PCEF NOTE 1: This credit reauthorization triggers apply only when Gy and/or Gyn are deployed. S.5.2 Policy and charging Control S.5.2.1 Policy and charging control rule The definition of PCC rule and PCC Rule operations in clauses 6.3.1 and 6.3.2 are applicable, except: - PS to CS session continuity; - User Location Report. NOTE: The procedure for provisioning predefined PCC rules at the IP-Edge is out of 3GPP scope. S.5.2.1a IP‑CAN session related policy information Table 6.4 applies with the following exceptions: - Authorized QoS per bearer and authorized MBR per QCI are not applicable for Fixed Broadband Access. - Charging characteristics profile for 3GPP UE is not available at the PCEF/IP-Edge. - No Charging Characteristics profile is defined for fixed devices. S.5.2.2 Void S.5.3 Void S.5.4 Reflective QoS The Fixed Broadband Network received the PCC rules from Gx reference point and as described in clauses S.3.3 and S.6.1.2 performs the appropriated mapping to Fixed Broadband access parameters. The mapping is outside the scope of 3GPP network and defined in TR-300 [37]. Fixed Broadband Access network currently supports the DSCP marking as specified in BBF TR-092 [40] for BRAS, in BBF TR-101 [35] for Access Nodes and Aggregation Nodes and in BBF TR-124 Issue 3 [34b] for the RG. The solution is based on DSCP marking of packets traversing the Fixed Broadband Access network. The solution assumes functionality in the BBF domain, all these functions are out-of-scope for 3GPP; also, these functions may or may not be implemented depending on the agreement between 3GPP and Fixed Broadband Access operator, these functions are described for information only. The downlink QoS treatment of the traffic in the PCEF is defined in clause S.6.1.2 and in TR-300 [37]. For the QoS treatment of the IP flow traffic from the UE to the IP-Edge, DSCP marking may be performed by the 3GPP UE by means of reflective QoS as defined in TS 23.139 [29], in particular: - How to inform the UE, as part of 3GPP access authentication signalling, that reflective QoS shall be applied on all the traffic in the attached network as defined in clause 6.3.1 of TS 23.139 [29]. - How the UE creates a 5-tuple rule for uplink traffic as defined in clause 6.3.3 of TS 23.139 [29]. How the RG or the IP-Edge may implement protective measurements (e.g. per UE-bandwidth limitations in the RG or in the IP-Edge) as defined in clause 6.3.1 of TS 23.139 [29]. NOTE: The UE supporting reflective QoS always send this indication during the Access authentication procedure. S.5.5 Policy Control Policy control functionalities listed in clause 6.1.5: binding, gating control, event reporting, QoS control and Redirection are applicable for Fixed Broadband Access. There is no support for NW initiated or UE initiated bearer establishment procedures; policy control is performed locally at the PCEF or at the TDF. If the PCRF provides authorized QoS for both, the IP‑CAN session and PCC rule(s), the enforcement of authorized QoS of the individual PCC rules shall take place first. S.5.5.1 Default QoS Control The BBF AAA may provide a default Access Profile QoS for the IP-CAN session that may contain QoS information. The PCRF may provide dynamically the default QoS for the IP-CAN session to the PCEF over Gx or alternatively may provide a default QoS profile name for those cases when the default QoS profile is provisioned in the IP-Edge/PCEF. The PCEF enforces the default QoS or the default QoS profile for the IP-CAN session provisions over Gx. The PCEF does not enforce the default Access Profile QoS provided by BBF AAA for the IP-CAN session if PCRF is deployed. The default QoS consists of a QCI and MBR. The IP-Edge/PCEF shall be able to convert default QoS into Fixed Broadband Access QoS attribute values. In the IP-Edge, the QCI and optionally the ARP priority level is used to determine the DSCP code value or other transport specific information element and the MBR is used for bandwidth limitation for the DSCP code value. The PCEF/IP-Edge shall enforce first the QoS for the packets that matches a service data flow template in an installed PCC Rule for which specific QoS enforcement actions are provided then the IP-Edge/PCEF shall enforce the default QoS for all downlink and uplink traffic for the IP-CAN session. S.6 Functional Entities The functional entities listed in clause 6.2 apply, except BBERF. Those functional entities that have specific values or specific functionality for Fixed Broadband Access are described in this clause. NOTE: Support for MPS Services and IMS Emergency is not specified in this Release. S.6.1 Policy Control and Charging Rules Function (PCRF) S.6.1.1 General The PCRF functionality defined in clause 6.2.1.0 shall apply, with the following exceptions: - No negotiation of IP-CAN bearer establishment mode applies. - No subscription to changes of IP-CAN type, RAT type or Access Network Information applies to the PCEF. - No event triggers that the TDF can subscribe to need to be monitored by the PCRF. - Usage Monitoring Control as defined in clause 6.6 applies with the following exceptions: - In the routed RG with NAT mode, the IP-CAN session is per RG in the PCEF/IP-Edge, the PCRF retrieves the usage monitoring related information from the SPR using the subscriber-id provided over Gx. The PCRF decides how to allocate a usage threshold to each existing IP-CAN session and/or MK. - In the bridge RG mode and in routed RG mode without NAT there may be a separate fixed subscriber session (i.e. IP-CAN session) for the each device behind the RG. The PCRF retrieves usage monitoring related information from the SPR using the subscriber-id and, if the request is for a 3GPP UE, the NSWO APN provided over Gx. The PCRF decides how to allocate a usage threshold to each existing IP-CAN session and/or Monitoring Key. S.6.1.1.1 Input for PCC decisions The PCEF may provide a subset of the information listed in clause 6.2.1.1 with the following fixed broadband specific values: - Subscriber Identifier in the form of an IMSI, MSISDN for a 3GPP UE or in the form of a user-name or Access Line Identifier (physical and logical circuit ID) for fixed device or RG; - Location of the subscriber; that may include Access line id (physical and logical circuit ID), SSID of the AP, BSSID of the AP; NOTE: How the location information becomes available to the PCEF/IPEdge is out of the scope of 3GPP. - PLMN id of the PCEF located in the IPEdge, if available; - IPv4/IPv6 address or IPv6 prefix of the UE; - Type of IP‑CAN (i.e. Fixed Broadband Access); - A PDN ID in the form of the NSWO-APN for a 3GPP UE. The SPR may provide the information listed in clause 6.2.1.1 for a UE and optionally for NSWO-APN. The OCS may provide the information listed in clause 6.2.1.1 for a UE. The TDF may provide the information listed in clause 6.2.1.1 for a UE and optionally for NSWO-APN. The AF, if involved, may provide the information listed in clause 6.2.1.1 with the following Fixed Broadband Access Specific values: - Subscriber Identifier; - IPv4/IPv6 address or IPv6 prefix of the UE. S.6.1.2 Policy and Charging Enforcement Function (PCEF) The PCC requirements for the PCEF is located in the Fixed Broadband Access are defined in TR-300 [37]. The PCEF performs the following Fixed Broadband specific functions: QoS enforcement: - The PCEF shall be able to convert a QoS parameters sent from PCRF to Fixed Broadband Access to specific QoS attribute and determine the QoS parameters sent to PCRF from the PCEF from a set of Fixed Broadband Access specific QoS attribute. Application Detection: - The support of Application Detection functionality is considered a network operator choice in Fixed Broadband Access. If supported, the functionality defined in clause 6.2.2.5 applies. In addition, the following functions are not supported: - No UE and/or NW initiated bearer procedures and no enforcement of the authorized QoS for an IP-CAN bearer is supported for Fixed Broadband Access. S.6.1.3 Application Function (AF) The AF functionality defined in clause 6.2.3 shall apply, except for the following functionality: - No subscription to changes of IP-CAN type, RAT type or Access Network Information applies. S.6.1.4 Subscriber Profile Repository (SPR) The SPR functionality defined in clause 6.2.4 shall apply. For Fixed Broadband Access the SPR may provide the subscription profile information per subscriber and PDN in case of a 3GPP UE or per subscriber in case of a fixed device or RG: - Subscriber Identifier in the form of an IMSI, MSISDN for a 3GPP UE or in the form of a user-name or Access Line Identifier (physical and logical circuit ID) for fixed device or RG; - A PDN ID in the form of the NSWO-APN. S.6.1.5 Online Charging System (OCS) The OCS functionality defined in clause 6.2.5 shall apply. For Fixed Broadband Access the PCEF provides the Subscriber Identifier that may be e.g. IMSI for a 3GPP UE or a user name or Access line identifier for a fixed devices or RG to the OCS. The PCEF or TDF also sends Access line id (physical and logical circuit ID) to the OCS when the subscriber ID identifies a 3GPP UE or a fixed device behind the RG. NOTE: An operator may also apply this solution with both PCEF and TDF performing enforcement and charging for a single IP-CAN session as long as the network is configured in such a way that the traffic charged and enforced in the PCEF does not overlap with the traffic charged and enforced by the TDF. S.6.1.6 Offline Charging System (OFCS) The OCS functionality defined in clause 6.2.6 shall apply. For Fixed Broadband Access the PCEF provides the Subscriber Identifier that may be e.g. IMSI for a 3GPP UE or a user name or Access line identifier for a fixed devices or RG to the OFCS. The PCEF or TDF also sends Access line id (physical and logical circuit ID) to the OFCS when the subscriber ID identifies a 3GPP UE or a fixed device behind the RG. NOTE: An operator may also apply this solution with both PCEF and TDF performing enforcement and charging for a single IP-CAN session as long as the network is configured in such a way that the traffic charged and enforced in the PCEF does not overlap with the traffic charged and enforced by the TDF. S.6.1.7 User Data Repository (UDR) The SPR data listed in clause 6.2.3 are stored in the UDR, the subscriber identifier and the PDN ID defined in S.6.1.4 applies. S.6.1.8 Traffic Detection Function (TDF) The TDF functionality defined in clause 6.2.9 shall apply. For Fixed Broadband Access, the TDF does not subscribe to event triggers indication from the PCRF at any IP-CAN session procedure. S.7 PCC Procedures and Flows S.7.1 Introduction A "Fixed Broadband Access IP-CAN" is a fixed access broadband network that provides IP connectivity to a UE. The Fixed Broadband Access IP-CAN reuses the definition of an IP-CAN session in this specification. The AF can provide the NATed IP address and ports used by the UE (for IMS, according to TS 23.228 [39]). NOTE: When the above condition is not met, there are no standardized means as for now to identify a UE behind a NATed-RG. The Fixed Broadband Access network does not support the concept of a bearer and multiple bearers as defined in TS 23.401 [17]. However, DSCP marking provides QoS support on transport network layer so that QoS and charging policies can be applied per SDF. Case 1, no Gateway Control Session applies for Fixed Broadband Access. The procedures cover both non-roaming and roaming with access to NSWO APN for a 3GPP UE. For the roaming case with access to NSWO APN, the V PCRF interacts with the IP-Edge PCEF and, if Sd applies, with the TDF. S.7.2 IP-CAN Session Establishment The PCEF located in the IP-Edge initiates the Gx IP‑CAN Session establishment as defined in clause 7.2. The session is initiated after that the IP-Edge becomes aware of an IPv4 address and/or an IPv6 prefix has been assigned to the fixed device and/or 3GPP UE. In route mode configuration with NATed RG, the session is initiated after the RG has been connected to the network and has been assigned an IPv4 address and/or IPv6 Prefix. The IPv4 address and/or IPv6 Prefix are assigned as per Broadband Forum specifications and it is out of scope of 3GPP. In bridge mode, the session is initiated after the device has been authenticated has been assigned an IPv4 address and/or IPv6 address or IPv6 Prefix by the Fixed Broadband access. Operator policies in the PCEF indicate if dynamic policy control is provided. In addition, the NSWO-APN is also configured for subscribers on a PLMN basis. The PCEF located in the IP-Edge includes in the IP‑CAN Session establishment message the Subscriber-Id, NSWO-APN if available, IP-CAN type, the Default QoS if available, the PLMN id if available and the location information as defined in S.6.1.1.1. The IP-Edge maps the Default-Access-Profile QoS to Default-QoS as defined in clause S.5.5.1. The PCRF may provision a Default QoS or a Default QoS profile, PCC Rules to activate and Events Triggers to report. S.7.3 IP-CAN Session Termination This procedure is in accordance with clause 7.3.2 with the exceptions listed in this Annex. The UE-initiated IP-CAN session termination is not to applicable to Fixed Broadband Access. The IP-CAN session termination is triggered by PCEF when Subscriber IP session is terminated. The trigger to terminate the Subscriber IP session may be HSS/AAA request to detach the UE or may be Broadband Forum specific (e.g. RG switch off, loss of transmission, IP address lease expiration PPPoE session termination, etc) and out of the scope of 3GPP. In routed mode configuration with NAT this procedure is applicable only when IP session from RG is terminated, e.g. when RG switches off or when public IP address assigned to the RG is released, etc. NOTE: In routed mode with NAT, the termination of connection from a device in LAN, e.g. when device releases the local IP address or it disconnects from WLAN does not trigger the IP-CAN session termination for IP session from RG. S.7.4 IP-CAN Session Modification S.7.4.1 PCEF-Initiated IP-CAN Session Modification This clause is related to IP-CAN session modification initiated by IP-Edge/PCEF for IP session. This procedure is in accordance with clause 7.4.1 with the exceptions listed in this Annex. In routed mode with NAT, this procedure can be triggered when new device connects to the RG, for example when UE requests a local IP address to the RG or when a UE disconnects from WLAN. The IP-Edge reports that an Event was met, including the Event Trigger and the affected PCC Rule. If TDF applies, the PCRF may provide ADC Rules and Event Triggers to the TDF and may provide PCC Rule, Event Triggers and a Default QoS or a Default QoS profile to PCEF. S.7.4.2 PCRF-Initiated IP-CAN Session Modification This procedure is in accordance with clause 7.4.2 with the exceptions listed in this Annex. The PCRF may also provide a Default QoS or a Default QoS profile to PCEF. S.7.5 Update of the subscription information in the PCRF This procedure is in accordance with clause 7.5.when the UE's (i.e. RG, fixed device or 3GPP UE) profile changes. S.7.6 PCRF Discovery and selection PCRF discovery and selection follows the principles defined in clause 7.6 with the following modification: - The Subscriber ID specified in clause S.5.1.2 is used as user identity. - For a 3GPP UE, the NSWO-APN is also available. - The IPv6 address may be included in the IP-CAN session establishment in the case of bridge-mode RG. S.8 Charging using AAA signalling The architecture shall provide charging for traffic exchanged by fixed devices and NSWO traffic to/from 3GPP UEs using AAA signalling. In this release in case of AAA-based charging the BBF AAA server is used for performing accounting of fixed device as defined by BBF specifications TR-101 [35] and TR-146 [36]. NOTE: The AAA-based accounting for fixed device is not applicable in roaming scenario. For the charging session over Gya and Gza, the user identifier is the same that is issued over the Gx session S.8.1 Reference architecture - Non-Roaming Figure S.8.1: PCC Reference architecture for Fixed Broadband Access convergence when AAA-based accounting is used S.8.2 Reference architecture - Roaming Figure S.8.2: PCC Reference architecture for Fixed Broadband Access convergence (roaming) when AAA-based accounting is used S.8.3 Gza Reference Point To transport charging information about 3GPP UE, the Gza reference point is located between Accounting Interworking function in the BBF defined network and the 3GPP offline charging system OFCS located in the VPLMN (roaming scenario) or in the HPLMN (non-roaming scenario). To transport charging information about fixed devices, the Gza reference point is located between the Accounting Interworking function in the BBF defined network and the 3GPP offline charging system located in the HPLMN (only non-roaming scenario). NOTE: The detailed definition of Gza reference point and diagram flows for supporting AAA-based charging is outside the scope of this specification. See SA WG5 specifications for further details. S.8.4 Gya Reference Point The Gya reference point is located between the Accounting Interworking function in the BBF defined Access Network and the 3GPP online charging system OCS located in the HPLMN and it transports charging information for 3GPP UE. The Gya reference point is located between the Accounting Interworking function in the BBF defined Access Network and the 3GPP online charging system located in the HPLMN and it transports charging information for fixed device. NOTE: The definition of Gya reference point and diagram flows for supporting AAA-based charging is outside the scope of this specification. See SA WG5 specifications for further details. S.8.5 B Reference Point This reference point is defined in BBF TR-300 [37]. NOTE: The definition of this reference point is out of the scope of 3GPP. S.8.6 AAA based charging The charging support for NSWO traffic for 3GPP UE and fixed devices can be provided when the BBF network reports per-user accounting data via B and Gya/Gza reference points. Offline and online charging may be supported by the 3GPP and BBF domain. In this Release, in case of AAA-based charging, the Online charging is supported based on existing capability supported by B reference point and IP-Edge with limitation based on AAA RADIUS/Diameter accounting in the BBF network (e.g. BNG capability, usage of RADIUS over B reference point). For RG in routed mode configuration with NAT, the single devices (i.e. fixed device and 3GPP UE) connected behind a RG can not be recognised, so the accounting is performed only for the RG. In case of RG bridge mode configuration and in routed mode configuration without NAT the AAA based charging is performed per single devices having a Subscriber IP session. In order to allow performing charging for fixed devices, the following assumptions are made about functionality in the Fixed Broadband Network: - The BBF network is able to collect per user accounting data for fixed devices and periodically report this data via the B reference point. S.8.7 Accounting Interworking Function The Accounting Interworking Function that performs translation of the accounting signalling and parameters that are understood by the IP-Edge into the credit management signalling and parameters that are understood by the OCS and the OFCS is defined in BBF TR-300 [37]. S.8.8 Procedures AAA based charging using accounting signalling S.8.8.0 General This clause describes the AAA-based charging. The basic assumption is that B interface is not modified. S.8.8.1 Charging Session Initiation This procedure is performed for initiation of charging session Figure S.8.8.1: AAA-based Charging Session Initiation The steps included in Block A and B are mutually exclusive. 1. The 3GPP UE EAP-based authentication or BBF Fixed device authentication is performed. NOTE 1: Authentication for fixed device is out of the scope of 3GPP specifications. A.1 If AAA-based accounting applies, the 3GPP UE/BBF device is successfully authenticated and this triggers the interaction with the OCS system. This step is outside the 3GPP scope. A.2. The Accounting Interworking Function that will activate the online-charging session and provide relevant input information for the OCS decision. i.e. subscriber identifier and charging keys obtained in step A.1. A.3. If online charging is applicable, the OCS provides the possible credit information to the Accounting Interworking Function and may provide re-authorisation triggers for each of the credits. NOTE 2: The Only Credit Reauthorization triggers that can be reported are "Credit Reauthorization time expired". 2. If PCC is supported, the IP-CAN session establishment procedure may be established as define in clause S.7.2. The steps from 1 to 14 defined in clause 7.2 are performed with the following exception: - Steps 9 - 10 are performed only if TDF based accounting is supported and AAA-based accounting is not supported. - Steps 13 - 14 are performed only if PCEF accounting is supported and AAA-based accounting is not supported. B.1. If AAA-based accounting applies, the start of accounting session is triggered in BBF AAA. This step is out of the scope of 3GPP specifications. NOTE 3: This step may occur anytime in parallel to steps from 1 to 14 of clause 7.2 B.2. The same step as step A.1 B.3. The same step as step A.2 3 The IP-CAN session establishment as defined in clause 7.2 steps from 15 to 17 are performed. S.8.8.2 Charging Session Modification This procedure is performed for updating the charging information, such as the available quota. Figure S.8.8.2: AAA-based Charging Session modification 1. The BNG can sent a RADIUS-Start accounting message or a RADIUS-Intermediate-Accounting message. 2 When the Accounting Interworking Function receives the message, it determines if it is required to update the accounting information which triggers an interaction with the OCS. 3. The Accounting Interworking Function may contact the OCS to request credit for new charging keys and/or to issue final report and return remaining credit for charging keys no longer active, i.e. when the accounting session is terminated. 4. The OCS may instruct the Accounting Interworking Function on the further handling of the session (terminate, continue, etc), provide credit information (possibly with re-authorisation trigger) and/or acknowledge the credit report. S.8.8.3 Charging Session Termination S.8.8.3.1 Charging Session Termination BNG-initiated This procedure is performed when BNG send a stop accounting message to the Accounting Interworking Function, for example the IP-CAN session termination procedure is initiated by PCRF or when Subscriber IP session terminated (for example when the 3GPP UE disassociates from the fixed broadband network, the RG is switched off, etc.). Figure S.8.8.3.1-1: AAA-based Charging Session Termination 1. The BNG determines that the Subscriber IP session is terminated (e.g. the device has left the fixed broadband network) and consequently a PCEF-Initiated IP-CAN session termination is initiated or it shall be terminated, when PCRF-Initiated IP-CAN session termination procedure is performed. 2. The BNG send a RADIUS-Stop-accounting message to the ACC_If. This step is outside the scope of 3GPP specifications. 3 The Accounting Interworking Function determines that the Accounting Session shall be terminated. 4. The Accounting Interworking Function shall issue the final reports and return the remaining credit to the OCS. 5. The OCS acknowledges the credit report and terminates the online charging session. Annex T (informative): How to accumulate PCC/ADC Rule usage in multiple monitoring groups If usage for a PCC/ADC rule is accumulated in multiple Monitoring Groups, the following solution re-uses the capabilities defined in the main body of this specification, the steps are described below: 1. The PCRF retrieves the total group allowance for the Monitoring Group and the set of services belonging to the Monitoring Group from the SPR. 2. For dynamic PCC/ADC Rules, the PCRF selects a Monitoring Key for those services that belongs to more than one Monitoring Group but does not have an individual Monitoring Key assigned. 3. For pre-configured PCC/ADC Rules the PCRF selects the PCC/ADC Rules for each of the services that belong to the monitoring group. For pre-configured PCC/ADC Rules, the PCEF is configured with an individual Monitoring Key that monitors the usage. 4. The PCRF calculates a usage threshold for each of these Monitoring Keys taking into account the minimum of the individual service allowance and the monitoring group allowance(s) the service belongs to. 5. The PCRF installs or activates the PCC/ADC Rule. The PCRF provides a usage threshold for each Monitoring Key. 6. When the PCRF receives a usage report for a Monitoring Key from the requested node (PCEF or TDF), the PCRF shall deduct the value from the corresponding group allowances and from the individual allowance if needed. 7. As long as all group usage allowances are not reached, the PCRF calculates a new usage threshold for the Monitoring Key based on the corresponding group allowances the service belongs to. Annex U (normative): Policy and charging control in the downlink direction for traffic marked with DSCP by the TDF In order to provide policy and charging control (e.g. QoS enforcement) in the downlink direction for applications with non-deducible service data flows detected by the TDF, in addition to the solution described in clause 4.5, the following solution is defined: The TDF shall be able to mark detected downlink application traffic with a DSCP value received within an installed ADC Rule matching this traffic. NOTE 1: Unless a class of applications matches the definition of a DSCP value standardised by IETF, DSCP values with no standardised meaning in IETF are used. DSCP values in ranges reserved by IANA for "experimental or Local Use" are suitable. NOTE 2: Using DSCP values with no standardised meaning in IETF prevents any IP router between TDF and PCEF to perform differentiated service scheduling for related IP packets unless it is updated or configured to support those DSCP values. This implies that sufficient network capacity must be guaranteed along the path between the TDF and PCEF so that the disabling of DiffServ packet forwarding has no detrimental impact on the end-to-end QoS. NOTE 3: Marking of DSCP bits for this purpose can interfere with appropriate traffic handling in some operator transport networks. The DSCP marking may also get remarked by routing entities within the operator networks. NOTE 4: If the application sets DSCP marking that is used for policy and charging control in the PCEF, either no ADC Rule is installed in the TDF matching this application traffic or if an ADC Rule is installed, then DSCP marking is not enabled. When TDF sets DSCP to values used for policy and charging control, network configuration needs to prevent an untrusted source from getting unplanned QoS and charging and also prevent remapping of this traffic between the application and the TDF. To ensure that the DSCP value used for service data flow detection is not visible to the operator's transport network, based on operator configuration, a tunnelling protocol may be used between TDF and PCEF. In case tunnelling is used then the DSCP value used for service data flow detection shall be carried in the inner IP header. The DSCP marking used in the operator's transport network is carried in the outer IP header of the tunnel. NOTE 5: The tunnel connections are preconfigured in the IP infrastructure connecting the TDF and the PCEF. The operator needs to ensure the same tunnel configuration is used for the TDF and for the PCEF. The tunnel protocol can be any applicable IP-based tunnel depending on operator´s choice. In order to support policy and charging control in the downlink direction by the PCEF/BBERF for an application detected by the TDF (typically for services with non -deducible service data flows), the PCRF shall either install a dynamic PCC/QoS Rule or activate a pre-defined PCC rule, which identifies traffic based on the corresponding DSCP value (provided by the ToS/Traffic Class mask field within the service data flow filter). In case tunnelling is used, the PCEF shall use the inner header's DSCP for the service data flow detection defined in clause 6.2.2.2. NOTE 6: This solution is particularly useful for QoS enforcement in the downlink direction procedures performed by the PCEF/BBERF. The TDF may still perform application detection and control as per received ADC Rules, including application detection reporting to the PCRF, enforcement control, usage monitoring control and charging, while applying DSCP marking. The PCEF/BBERF may also perform then policy and charging control in the downlink direction. Annex V (informative): Policy Control for Remote UEs behind a ProSe UE-to-Network Relay UE With the Proximity-based services, in accordance with TS 23.303 [44], a UE acting as a Remote UE can connect to a PDN via a ProSe UE-to-Network Relay UE, using an IP-CAN session that the Relay UE has established. The Relay UE is assigned an IPv6 prefix that is shorter than /64. The PCRF does not get any Remote UE identity and is not required to be aware of the Remote UE but is expected to validate Remote UE related service information from the AF and generate any necessary PCC rules according to standard procedures already defined. PCC rule authorizations may be static (e.g. predefined PCC rules) or rely on AF provided service information. An AF serving a remote UE reaches the appropriate PCRF based on the IPv6 prefix that the UE-to-Network Relay UE has assigned to the remote UE. The AF reaches the appropriate PCRF by performing a PLMN lookup for the IPv6 prefix and using the Network Realm/Domain, as defined in TS 23.003 [16], associated with the PLMN. In order to make a PCC rule specific for a certain Remote UE, the SDF filters used for traffic detection need to include the attribute Local Address and Mask with a value that corresponds to the Remote UE only. The value is normally an IPv6 prefix that is longer than the prefix assigned for the IP-CAN session (i.e. for the ProSe UE-to-Network Relay UE). Annex W (informative): Void Annex X (informative): Encrypted traffic detection by using domain name matching For the cases when it is required to detect and enforce/charge sponsored services within encrypted traffic and those sponsored services are uniquely identifiable by a list of {IP address ranges, domain name matching strings, match type (absolute/suffix)} set, while either element in the pair of {IP address ranges, domain name matching strings} can be "any", as applicable, but not both elements simultaneously, the domain name matching solution described below may be used. NOTE 1: L3 information (IP address ranges) is visible even if traffic is encrypted. The following assumptions apply for the solution: - There exists an agreement between the operator and sponsored data connectivity content provider. - Content provider uses HTTPS as a transport mechanism, using Web Public Key Infrastructure (PKI). The set of information {IP address ranges, domain name matching strings, match type (absolute/suffix)} required to identify encrypted traffic is defined in the PCEF/TDF either by using pre-defined PCC/ADC Rules or by using dynamic PCC/ADC Rules that include Application Identifiers, as applicable. The detection logic to which Application Identifier in the PCEF/TDF refers to, is extended to cover ({IP address ranges, domain name matching strings, match type (absolute/suffix)} information. If such a pre-defined or dynamic PCC/ADC Rule is active for an IP-CAN/TDF session, the PCEF/TDF shall check IP address ranges and, in case of compliancy with the received/preconfigured value (see note 2), match domain name strings, either absolutely or by suffix, against the following fields in the initial HTTPS handshake: - TLS Server Name Indication (SNI) extension, when available (see [47]); or, if not available. - Server certificate's Subject Alternative Name x.509 extension DNS name, when available. All relevant values shall be examined for matching; or if not available or no match was found. - Server certificate's Subject Common Name (CN). NOTE 2: If the IP address ranges equals "Any", then any traffic is said to be compliant. The information required for the detection of sponsored HTTPS (i.e. defined in Annex X to be pre-configured in the PCEF/TDF and either the TLS SNI extension or the Server certificate´s Subject Alternative Name x.509 DNS name or Server certificate´s Subject CN) is verified with the corresponding server IP address/prefix of the IP packets by the PCEF/TDF. The PCEF/TDF uses implementation specific logic to perform this verification. Annex Y (informative): Change history Change history Date Meeting TDoc CR Rev Cat Subject/Comment New version 2014-06 SP-64 SP-140273 0885 5 B PCC Rules sharing resources 13.0.0 2014-06 SP-64 SP-140383 0885 6 B PCC Rules sharing resources MCC Update to use correct approved revision of the Rel-13 CR. 13.0.1 2014-09 SP-65 SP-140428 0896 2 B Addition of RAN user plane congestion handling feature into the specification 13.1.0 2014-09 SP-65 SP-140428 0897 2 B Np reporting restrictions 13.1.0 2014-09 SP-65 SP-140428 0899 2 B Aggregation of Np messages 13.1.0 2014-09 SP-65 SP-140421 0907 2 A Clarifications for PRA reporting 13.1.0 2014-09 SP-65 SP-140431 0908 2 F Clarification of resource sharing for different Rx sessions 13.1.0 2014-09 SP-65 SP-140441 0914 - A QCI values for Public Safety services 13.1.0 2014-12 SP-66 SP-140674 0904 3 A Clarifications for TFT handling 13.2.0 2014-12 SP-66 SP-140689 0915 - C Applicability of congestion information reporting for certain APNs only 13.2.0 2014-12 SP-66 SP-140689 0916 2 F Clarifying details of deferred services 13.2.0 2014-12 SP-66 SP-140671 0920 2 A Support for IPv6 prefix retrieve by the HSGW during the eHRPD pre-registration procedure 13.2.0 2014-12 SP-66 SP-140694 0921 3 B Introducing the feature of excluding Usage of a Service/Application from IP-CAN session/TDF session Usage into the specification 13.2.0 2014-12 SP-66 SP-140690 0922 2 B Indication to share resources in the UL or DL or both directions 13.2.0 2014-12 SP-66 SP-140685 0924 4 A Charging correlation identifier for the IP-CAN session 13.2.0 2014-12 SP-66 SP-140694 0925 1 D New Annex: Monitor service usage in multiple groups 13.2.0 2014-12 SP-66 SP-140689 0926 3 C Np mobility handling 13.2.0 2014-12 SP-66 SP-140689 0927 - C Resolution of Editor's note on bandwidth limitation. 13.2.0 2014-12 SP-66 SP-140678 0930 2 A QoS handling at inter-RAT mobility 13.2.0 2014-12 SP-66 SP-140668 0939 1 A Correct Reference to 3GPP2 X.S0057 13.2.0 2014-12 SP-66 SP-140678 0946 2 A Correction to Delay Budget for first packets in a data burst 13.2.0 2014-12 SP-66 SP-140689 0950 2 F Transfer of location information on Np 13.2.0 2014-12 SP-66 SP-140689 0952 - F Removal of Editor Note on logical PCRF id 13.2.0 2014-12 SP-66 SP-140693 0953 3 C TDF support for downlink's bearer selection and bearer binding procedures 13.2.0 2014-12 SP-66 SP-140686 0955 2 A Proposal to solve the discussion on how QoS change of default bearer affects PCC Rules bound to the default bearer 13.2.0 2014-12 SP-66 SP-140693 0958 3 B Activate PCC function per UE based on subscription information 13.2.0 2014-12 SP-66 SP-140689 0961 2 F Clarifying reporting of no congestion state 13.2.0 2014-12 SP-66 SP-140693 0963 2 B TWAN release cause for Trusted WLAN 13.2.0 2014-12 SP-66 SP-140679 0964 - F Stage 3 alignment for Fixed Broadband Access 13.2.0 2015-03 SP-67 SP-150027 0966 3 B Removing restrictions to report RAT type to the AF 13.3.0 2015-03 SP-67 SP-150027 0968 1 B Activate PCC function per UE based on subscription information when BBERF is deployed 13.3.0 2015-03 SP-67 SP-150109 0971 1 A Correction to support of I-WLAN in TS 23.203 13.3.0 2015-06 SP-68 SP-150230 0905 6 A Priority of Default Bearer 13.4.0 2015-06 SP-68 SP-150230 0941 5 A Clarifications for QoS change of default bearer 13.4.0 2015-06 SP-68 SP-150235 0975 2 B Resource management for background data transfer via Rx 13.4.0 2015-06 SP-68 SP-150232 0976 3 F Configuring AF application identifier value in PCRF to avoid SRVCC 13.4.0 2015-06 SP-68 SP-150239 0977 1 F Session/bearer release cause over S2b 13.4.0 2015-06 SP-68 SP-150231 0978 2 F Alignment of RUCI reporting restrictions' basis for UPCON 13.4.0 2015-09 SP-69 SP-150492 0980 3 B Introduction of Flexible Mobile Service Steering feature into PCC architecture 13.5.0 2015-09 SP-69 SP-150498 0981 1 F Adding Nt reference point to architecture 13.5.0 2015-09 SP-69 SP-150503 0985 2 B Location to Support Emergency services over WLAN access to EPC 13.5.0 2015-09 SP-69 SP-150497 0986 3 B PCC Support of NBIFOM 13.5.0 2015-09 SP-69 SP-150491 0988 1 A Clarifications for PCC rule actions 13.5.0 2015-09 SP-69 SP-150492 0989 3 B Update the architecture to support the FMSS for EPC-routed scenario 13.5.0 2015-09 SP-69 SP-150492 0990 4 B Definition of Traffic Steering Control Information 13.5.0 2015-09 SP-69 SP-150505 0991 2 F Removal of OCS proxy in LBO roaming scenario 13.5.0 2015-09 SP-69 SP-150492 0992 3 B High level requirement and function description of FMSS 13.5.0 2015-09 SP-69 SP-150500 0994 1 F Addition of resource sharing indication 13.5.0 2015-09 SP-69 SP-150492 0995 3 B PCC architecture enhancement for traffic steering using St and TSSF 13.5.0 2015-09 SP-69 SP-150550 0983 4 B PCC Procedures and Flows including Traffic Steering 13.5.0 2015-09 - - - - - MCC correction to implementation of CR0986R3 13.5.1 2015-12 SP-70 SP-150604 1000 3 B Policy Control for remote UE behind relay UE 13.6.0 2015-12 SP-70 SP-150607 1002 3 F Bearer binding, usage monitoring and other impacts due to NBIFOM 13.6.0 2015-12 SP-70 SP-150608 1004 1 F Clarify Nt Reference Point 13.6.0 2015-12 SP-70 SP-150614 1006 1 F Update of the PCC rules during the addition of an access procedure 13.6.0 2015-12 SP-70 SP-150617 1007 1 F Conveying to the EPC the IMEI of devices accessing a trusted or untrusted WLAN 13.6.0 2015-12 SP-70 SP-150613 1008 1 F Transfer of User Location Information at Create Session Request over S2b 13.6.0 2015-12 SP-70 SP-150600 1012 - A Correction of definition of QCI 65, 66, 69 and 70 13.6.0 2016-03 SP-71 SP-160162 1009 7 B APN AMBR change at a certain time on Gx 13.7.0 2016-03 SP-71 SP-160162 1018 2 F Bitrate variations 13.7.0 2016-06 SP-72 SP-160298 1013 7 C Priority sharing for concurrent sessions 13.8.0 2016-06 SP-72 SP-160294 1021 1 F Clarification of the decision of NBIFOM mode 13.8.0 2016-06 SP-72 SP-160291 1023 1 F Transfer of traffic steering policy control information for TSSF 13.8.0 2016-06 SP-72 SP-160291 1026 - F Corrections to FMSS related descriptions 13.8.0 2016-06 SP-72 SP-160287 1029 2 B Update of 23.203 for CIoT 13.8.0 2016-06 SP-72 SP-160294 1030 2 F Clarifications and Corrections for NBIFOM 13.8.0 2016-06 SP-72 SP-160304 1022 2 B Subscription to notification of PLMN id change over Rx 14.0.0 2016-09 SP-73 SP-160653 1025 3 B Reporting entering or leaving a set of PRAs 14.1.0 2016-09 SP-73 SP-160653 1031 9 B Support of Multiple PRAs 14.1.0 2016-09 SP-73 SP-160655 1032 - C Support of sponsored data connectivity for TDF 14.1.0 2016-09 SP-73 SP-160655 1033 5 B Encrypted traffic detection by using domain name matching 14.1.0 2016-09 SP-73 SP-160645 1034 4 C Support of traffic steering control for 3rd party service function 14.1.0 2016-09 SP-73 SP-160651 1035 3 B Provision of EPC-level identities for IMS emergency sessions over Rx 14.1.0 2016-09 SP-73 SP-160655 1036 7 B Management of PFDs to PCEF/TDF 14.1.0 2016-09 SP-73 SP-160644 1037 1 A Provisioning of the Source port and ePDG IP address 14.1.0 2016-09 SP-73 SP-160641 1039 1 A Setting the RR identifier alignment with stage 3 14.1.0 2016-09 SP-73 SP-160655 1041 3 B Architecture enhancement to support SDCI 14.1.0 2016-09 SP-73 SP-160655 1043 6 B PFD retrieval and the procedures for sponsored data connectivity enhancement 14.1.0 2016-09 SP-73 SP-160641 1045 3 A Details of PCEF Routing Rule operations 14.1.0 2016-09 SP-73 SP-160638 1050 2 A Extending the IE for application detection within the ADC Rules 14.1.0 2016-09 SP-73 SP-160655 1051 3 B Sponsored HTTP traffic detection by using domain name matching 14.1.0 2016-09 SP-73 SP-160658 1052 1 B Adding ENODEB_CHANGE event trigger 14.1.0 2016-09 SP-73 SP-160655 1053 3 B Rx enhancement for SDCI 14.1.0 2016-09 SP-73 SP-160646 1058 2 B New QCI values for V2X services 14.1.0 2016-09 SP-73 SP-160658 1060 2 B Predictable pre-emption of media flows 14.1.0 2016-09 SP-73 SP-160638 1066 2 A Overlapping IP Addresses with FMSS 14.1.0 2016-12 SP-74 SP-160812 1070 1 A Remove "same media type" requirement for Priority Sharing 14.2.0 2016-12 SP-74 SP-160818 1071 3 F Modification of PRA information over Gx reference point 14.2.0 2016-12 SP-74 SP-160826 1076 4 B Introduction of 3GPP PS Data Off 14.2.0 2016-12 SP-74 SP-160818 1077 3 F Corrections on the usage of set of PRA 14.2.0 2016-12 SP-74 SP-160818 1079 1 F Configuration of multiple PRAs 14.2.0 2016-12 SP-74 SP-160908 1073 3 C Service input for the setting of the ARP-PCI and ARP-PVI 14.2.0 2016-12 SP-74 SP-160921 1068 5 C Deferred default EPS bearer QCI and ARP change 14.2.0 2017-03 SP-75 SP-170052 1081 1 C TS 23.203 support for transport level packet marking 14.3.0 2017-06 SP-76 SP-170370 1082 3 F Updating the description of 3GPP PS Data Off feature 14.4.0 2017-06 SP-76 SP-170368 1086 7 F Clarification of caching time 14.4.0 2017-06 SP-76 SP-170368 1090 2 F Corrections to handling of partial and full updates 14.4.0 2017-09 SP-77 SP-170719 1093 1 F Correction to event trigger Data Off Change 14.5.0 2017-09 SP-77 SP-170720 1094 2 F Corrections to PFD removal 14.5.0 2017-09 SP-77 SP-170732 1092 2 C Enhancement on Sy reference point 15.0.0 2017-09 SP-77 SP-170729 1099 2 C 23.203 PCEF Support for Data Off phase 2 15.0.0 2017-12 SP-78 SP-170921 1106 3 C Support for Unsynchronized lists 15.1.0 2017-12 SP-78 SP-170926 1107 5 B Enhanced VoLTE performance CR for TS 23.203 15.1.0 2017-12 SP-78 SP-170924 1110 3 C Use of ARP priority level in addition to QCI for packet handling 15.1.0 2017-12 SP-78 SP-170929 1111 2 C Extension on QCI for MC Video 15.1.0 2017-12 SP-78 SP-170920 1112 4 B Introduction of new QCIs for low latency with normal reliability requirements 15.1.0 2017-12 SP-78 SP-170924 1113 2 F Clarify MBMS and other use of PCC/QoS specification 15.1.0 2018-03 SP-79 SP-180110 1116 1 C QCIs for URLLC 15.2.0 2018-06 SP-80 SP-180472 1119 4 A Application detection report when the PFDs are removed 15.3.0 2018-06 SP-80 SP-180496 1120 5 F Policy update when UE is suspended 15.3.0 2018-06 SP-80 SP-180494 1121 - F Updates to URLLC QCIs to align with SA1's updated requirements 15.3.0 2018-09 SP-81 SP-180726 1122 1 F Corrections for low latency QCIs 15.4.0 2018-09 SP-81 SP-180729 1123 1 F Removal of incorrect definition of WB-E-UTRAN 15.4.0 2019-03 SP-83 SP-190175 1124 3 C New QCIs for Enhanced Framework for Uplink Streaming 16.0.0 2019-03 SP-83 SP-190163 1125 2 B Support for Restricted Local Operator Services in 23.203 16.0.0 2019-06 SP-84 SP-190404 1127 2 A Multiple PFD filters, alignment with stage 3 16.1.0 2019-12 SP-86 SP-191089 1130 1 F Aligning TS 23.203 with the CHEM feature of SA4 16.2.0 2021-03 SP-91E SP-210085 1133 1 B Multimedia Priority Service (MPS) Phase 2 support for Data Transport Service 17.0.0 2021-06 SP-92E SP-210361 1134 1 F Multimedia Priority Service (MPS) Phase 2 support for Data Transport Service 17.1.0 2021-06 SP-92E SP-210361 1135 1 B Additional authorization functionality in support of MPS for Data Transport Service 17.1.0 2021-12 SP-94E SP-211284 1136 2 B Support policy and QoS control for satellite access 17.2.0 2021-12 SP-94E SP-211279 1138 1 A Access network information request without PCC rules 17.2.0 2024-03 - - - - - Update to Rel-18 version (MCC) 18.0.0 2024-09 SP-105 SP-241266 1139 2 B Support of MPS priority for Messaging 19.0.0 2024-12 SP-106 SP-241490 1141 2 F Support of MPS priority for Messaging 19.1.0
|
b57c39c719229455cea55c4a75308a42
|
23.204
|
1 Scope
|
The present document specifies the new capabilities and enhancements needed to support SMS over a generic IP Connectivity Access Network (IP-CAN) using IMS capabilities (TS 23.228 [9]). These include (but are not limited) to:
1 Enhancements to the HSS;
2 Communication between the SMS-GMSC/SMS-IWMSC and the HSS;
3 Authentication of service usage and registration;
4 Transfer of UE Terminated SMS, UE Originated SMS, and Delivery reports;
5 Mechanisms to handle SMS when there is more than one IP connection active with the UE, etc.
6 Mechanisms to handle MT-SMS without MSISDN to IMS UE, and SMS between IMS UEs that support MSISDN-less SMS operation.
The document also specifies the capabilities and enhancements needed to support the service level interworking for the Short Message service as defined in the TS 23.040 [2] and in this specification and the Instant Messaging service as defined in OMA-TS-SIMPLE_IM-V1_0 [12]. The features supported from the IM specification are limited to the exchange of short or large immediate messages in pager mode.
NOTE: The page-mode immediate message as defined in TS 24.247[14] is considered as a subset of OMA-TS-SIMPLE-IM-V1_0 [12].
The document also specifies the capabilities and enhancements needed to support service level interworking for the Short Message service, as defined in the TS 23.040 [2] and in this specification and the OMA CPM service as defined in OMA-TS-CPM_Conv_Fnct-V1_0 [17]. The features supported from the CPM specification are the exchange of short or large immediate messages in pager mode, as well as session-based messaging.
The service requirements are described in TS 22.340 [18].
|
b57c39c719229455cea55c4a75308a42
|
23.204
|
2 References
|
The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
- References are either specific (identified by date of publication, edition number, version number, etc.) or non‑specific.
- For a specific reference, subsequent revisions do not apply.
- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.
[1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
[2] 3GPP TS 23.040: "Technical realization of the Short Message Service (SMS) Point to Point (PP)".
[3] Void.
[4] Void.
[5] Void.
[6] 3GPP TS 29.002: "Mobile Application Part (MAP) specification".
[7] Void.
[8] Void.
[9] 3GPP TS 23.228: "IP Multimedia Subsystem (IMS); Stage 2".
[10] Void.
[11] Void.
[12] OMA-TS-SIMPLE_IM-V1_0: "Instant Messaging using SIMPLE", http://www.openmobilealliance.org/.
[13] IETF RFC 5438: "Instant Message Disposition Notification", February, 2009.
[14] 3GPP TS 24.247: "Messaging service using the IP Multimedia (IM) Core Network (CN) subsystem; Stage 3".
[15] OMA-RD-CPM-V1_0: "CPM Requirements", http://www.openmobilealliance.org/.
[16] OMA-AD-CPM-V1_0: "CPM Architecture", http://www.openmobilealliance.org/.
[17] OMA-TS-CPM_Conv_Fnct-V1_0: "CPM Conversation Functions", http://www.openmobilealliance.org/.
[18] 3GPP TS 22.340: "IP Multimedia System (IMS) messaging; Stage 1".
[19] IETF RFC 4975: "The Message Session Relay Protocol (MSRP)", September 2007.
[20] 3GPP TS 23.682: "Architecture enhancements to facilitate communications with packet data networks and applications".
[21] 3GPP TS 23.060: "General Packet Radio Service (GPRS); Service description; Stage 2".
[22] 3GPP TS 23.272: "Circuit Switched (CS) fallback in Evolved Packet System (EPS); Stage 2".
[23] 3GPP TS 23.501: "System Architecture for the 5G System; Stage 2".
[24] 3GPP TS 23.502: "Procedures for the 5G System; Stage 2".
[25] 3GPP TS 23.401: "General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access".
|
b57c39c719229455cea55c4a75308a42
|
23.204
|
3 Definitions and abbreviations
| |
b57c39c719229455cea55c4a75308a42
|
23.204
|
3.1 Definitions
|
For the purposes of the present document, the terms and definitions given in TR 21.905 [1] and the following definitions apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [1]:
Converged IP Messaging: as defined in OMA-RD-CPM-V1_0 [15]. Converged IP Messaging supports one-to-one, one-to-many personal communications, and also communication with Applications.
CPM Message: as defined in OMA-RD-CPM-V1_0 [15]: Information that is sent to one or more recipients. A CPM Message can contain several discrete Media (e.g. text, images, audio-clips, video-clips).
CPM AS: An application server supporting the functionality of a CPM Participating Function and/or a CPM Controlling Function as defined in OMA-RD-CPM-V1_0 [15].
IM origination: origination of an Instant Message by an IMS UE.
IM termination: termination of an Instant Message by an IMS UE.
IMS core: refers to the core session control elements of the IM CN Subsystem, i.e. the CSCFs, and the IBCF.
Instant Message: an Instant Message as defined in the OMA-TS-SIMPLE_IM-V1_0 [12] and TS 24.247 [14]. The term Instant Message is also used to designate a CPM Message.
Interworking Selection Function: as defined in OMA-AD-CPM-V1_0 [16]. The Interworking Selection Function selects an Interworking Function that should perform the actual interworking between CPM and SMS.
MSISDN-less SMS operation: operation to support SMS communication without the need of MSISDN in the UE's IMS subscription profile.
MSISDN-less Correlation ID: information element which consists of Receiver Identity (i.e. SIP-URI of B party), Sender Identity (i.e. SIP-URI of A party), and HLR Identity (i.e., HLR that serves the B party).
Non-supporting MSISDN-less SMS UE: a UE which does not support MSISDN-less SMS operation as defined in this specification.
SIMPLE IM service: the Instant Messaging Service as defined in the OMA-TS-SIMPLE_IM-V1_0 [12].
SM origination: origination of a Short Message (including SMS over IP) by an SMS capable UE, as defined in TS 23.040 [2] and this specification.
SM termination: termination of a Short Message (including SMS over IP) by an SMS capable UE, as defined in TS 23.040 [2] and this specification.
SMS: the Short Message Service as defined in the TS 23.040 [2].
SMSF: the SMS Function as defined in TS 23.501 [23].
SMSIP MESSAGE: an immediate message as defined in TS 23.228 [9], which encapsulates a SM in its text body.
SMSIP UE: a UE which supports SMSIP MESSAGE.
|
b57c39c719229455cea55c4a75308a42
|
23.204
|
3.2 Abbreviations
|
For the purposes of the present document, the abbreviations given in TR 21.905 [1] and the following apply:
CPM Converged IP Messaging
IM Instant Message
IMDN Instant Message Disposition Notification
IP‑SM‑GW IP-Short-Message-Gateway
ISF Interworking Selection Function
SM Short Message
|
b57c39c719229455cea55c4a75308a42
|
23.204
|
4 Void
|
4a Architecture Requirements
4a.1 General
The SMS-IP architecture supports the following:
- Notification shall be sent to the HSS that a previously unreachable UE is now reachable.
- Functionality is required to be able to select the domain for message delivery between IMS and CS/PS, and to have the message delivered to the selected domain.
- Functionality is required to determine whether to transform the message format or not, and to perform the transformation of the message format when determined.
- The interworking function shall generate the appropriate charging-related information and provide the appropriate online charging mechanism (if it is applied for the Short Message Service and/or SIMPLE IM services and/or CPM based services) for the interworking services.
4a.2 Transport-level interworking
For transport-level interworking , the architecture allows for the following:
- A registration and de-registration mechanism shall be supported where UEs are required to explicitly indicate their ability to send and receive encapsulated Short Messages.
- It shall provide for the transport of Short Message Service TP layer PDUs (TS 23.040 [2]) and associated RP layer information.
4a.3 Service-level interworking
For service-level interworking, the architecture allows for the following:
- The service-level interworking is a value added service which requires service subscription. In addition, it shall also take the operator's policy, if available, into account, e.g. checking on the barring setting of the subscriber to determine whether to provide this interworking or not, so the service authorisation shall be supported before the interworking is executed.
- The service-level interworking applies as a fallback only if the users cannot communicate with each other using their chosen messaging service according to the user preference and operator policy. The location of the interworking service can be in the originating network and in the terminating network.
- The service-level interworking shall support interworking between OMA SIMPLE IM service as defined in OMA-TS-SIMPLE_IM-V1_0 [12] and Short Message Service, as defined in the TS 23.040 [2] and in the current specification.
- The service-level interworking shall support interworking between OMA CPM service as defined in OMA-TS-CPM_Conv_Fnct-V1_0 [17] and Short Message Service, as defined in the TS 23.040 [2] and in the current specification.
- The service-level interworking shall take the capability of the terminating UE into account when possible.
- The service level interworking shall be transparent to the end user.
- The service-level interworking shall minimize the impact on the IMS architecture.
- The service-level interworking shall not impact existing functionality of the Short Message Service as described in TS 23.040 [2] or of the SIMPLE IM service enabler as described in OMA-TS-SIMPLE_IM-V1_0 [12] or of the CPM service enabler as described in OMA TS CPM_Conv_Fnct-V1_0 [17]. Existing security mechanisms for the SIMPLE IM service, the Converged IP Messaging service and the Short Message Service shall be reused.
- The interworking function shall be aware if the message should be interworked or not, e.g. specific types of Short Messages such as an over the air configuration message, shall not be interworked at service-level, but shall be instead transported as a Short Message via IMS, CS or PS.
- If an SMS user requests an SMS status report that the message was delivered to the recipient, then an SMS status report shall be generated when the message is delivered using Instant Message.
- If an IMS user requests a notification that the message was delivered to the recipient and the Instant Message is interworked to Short Message on the originating side, an SMS status report shall be interworked to a delivery notification when the message is delivered.
- The interworking functionality shall be executed in the following cases:
- Originating network:
- The sender is an IM user or a CPM user who has subscribed to the interworking function and the recipient is not routable in IMS;
- The operator policy on the originating side has been set to send the Instant Messages via Short Message Service.
- Terminating network:
- The user preferences and/or the operator policy of the recipient have been set to receive the incoming Instant Messages via Short Message Service;
- The received message is a Short Message and the recipient is an IM user or a CPM user and has subscribed to the interworking service.
NOTE: For ensuring the integrity of the response messages from the IM UE or the CPM UE, it is strongly recommended that in networks where the IP-SM-GW is deployed, no intermediate nodes modify or terminate the message between the IP-SM-GW and the terminating IM UE or CPM UE. If intermediate nodes are deployed, they can send response messages that do not reflect the final response from the IM UE or CPM UE. Final responses from the IM UE or CPM UE are necessary to ensure correct charging and delivery reports on the Short Message Service side.
4a.4 SMS without MSISDN
For SMS without MSISDN interworking, the architecture allows for the following in addition to clause 4a.2:
- It shall provide for the transport of Mobile Terminating Short Message Service to UE without the need of MSISDN in the UE's IMS subscription profile.
- It shall provide for the transport of Mobile Originating Short Message Service from IMS UE that supports MSISDN-less SMS operation to other IMS UE.
4a.5 SMS without MSISDN interworking with Non-supporting MSISDN-less SMS UE
This version of the specification does not require the support of SMS communication between IMS UE that supports MSISDN-less SMS operation as defined in this specification and non-supporting MSISDN-less SMS UE.
NOTE: It is up to implementation on the IMS network that supports the MSISDN-less SMS operation to determine how to interwork with non-supporting MSISDN-less SMS UE if required.
|
b57c39c719229455cea55c4a75308a42
|
23.204
|
5 Architecture model and reference points
| |
b57c39c719229455cea55c4a75308a42
|
23.204
|
5.1 Reference architecture
|
Figure 5.1 below shows the overall architecture for providing SMS over a generic IP CAN.
Figure 5.1: Architecture for providing SMS over a generic IP-CAN
NOTE: Nodes specific to the CPM functions such as ISF are either collocated with the IP-SM-GW or else are not shown.
|
b57c39c719229455cea55c4a75308a42
|
23.204
|
5.2 Reference points
| |
b57c39c719229455cea55c4a75308a42
|
23.204
|
5.2.1 General
|
The clauses below describe the needed enhancements and specific considerations to existing interfaces in order to support SMS over a generic IP-CAN.
|
b57c39c719229455cea55c4a75308a42
|
23.204
|
5.2.2 C/S6c interface
|
The C or S6c interface allows the SMS-GMSC, using MAP or a Diameter based protocol, to obtain the address of the IP-Message-GW via mechanisms described in clause 5.3.
|
b57c39c719229455cea55c4a75308a42
|
23.204
|
5.2.3 Interface between the IP-SM-GW and the HLR/HSS
|
The interface(s) between the IP-SM-GW and the HLR/HSS is used for:
- Supporting the registration and de-registration from the IP-SM-GW to the HLR/HSS for SMS delivery.
- Forwarding of the Send Routeing Information for Short Message requests from HLR/HSS to IP-SM-GW in order to return the address where the SM should be forwarded.
- Interrogating the HLR/HSS using Send Routeing Information for Short Message to retrieve the IMSI and the current MSC, SGSN, MME and/or SMSF addresses.
- Informing the HLR/HSS when a memory capacity exceeded condition ceases.
- Retrieving SMS related data from the HLR/HSS: subscriber data of the short message service similar to the data for the current CS/PS domain and additional service data on the service authorisation of the encapsulated short message delivery via IMS, SC address for service-level interworking from Instant Message to Short Message if the SC address is stored in the HLR/HSS.
Both a Sh interface and either a J or S6c interface can be deployed between the IP-SM-GW and the HLR/HSS. During the functional allocation the change on existing MAP functions, when used, should be minimized. The deployment of the J or S6c interface is mandatory, since it is used for forwarding the SRI for SM message.
|
b57c39c719229455cea55c4a75308a42
|
23.204
|
5.2.4 E/Gd/Gdd/SGd interface
|
The E/Gd/Gdd/SGd interface allows the IP-SM-GW to connect to the SMS‑GMSC, appearing to the SMS‑GMSC as an MSC, SGSN, MME or SMSF.
For interworking with SMS in MME as defined in TS 23.272 [22], Annex C, an IWF may be used as described in that clause.
For interworking with an SGSN supporting the Gdd interface, an IWF may be used as described in TS 23.060 [21].
|
b57c39c719229455cea55c4a75308a42
|
23.204
|
5.2.5 ISC interface
|
The ISC interface allows the IP-SM-GW to forward the receiving message to the SIP based UE via IMS core.
|
b57c39c719229455cea55c4a75308a42
|
23.204
|
5.2.6 Void
| |
b57c39c719229455cea55c4a75308a42
|
23.204
|
5.3 Functional entities
| |
b57c39c719229455cea55c4a75308a42
|
23.204
|
5.3.1 IP-Short-Message-Gateway (IP-SM-GW)
| |
b57c39c719229455cea55c4a75308a42
|
23.204
|
5.3.1.1 General
|
The IP-SM-GW shall provide the protocol interworking for delivery of the short message between the IP-based UE and the SMS-SC. The message is routed to the SMS-SC for delivery to the SMS-based user or the message is received from the SMS-SC of an SMS-based UE for delivery to an IP-based UE.
The general functions of the IP-SM-GW are:
- to determine the domain (CS/PS or IMS) for delivery of a Short Message;
- to connect to the SMS‑GMSC using established MAP or Diameter based protocols, appearing to the SMS‑GMSC as an MSC, SGSN, MME or SMSF using the E, Gd/Gdd or SGd interfaces;
- to respond to Send Routeing Information for Short Message requests made by the SMS-GMSC, and forwarded from the HSS, with its own address;
- to connect to the SMS-IWMSC using established MAP or Diameter based protocols, appearing to the SMS-IWMSC as an MSC, SGSN, MME or SMSF using the E, Gd/Gdd or SGd interfaces;
- to connect to the HSS using established MAP or Diameter based protocols, to obtain the address of MSC/SGSN/MME/SMSF address(es) for SM termination in CS/PS;
NOTE: The IP-SM-GW need not support all of the functionality defined in MAP in TS 29.002 [6].
- to acquire and maintain knowledge of the association between the MSISDN, IMSI and the address of the S‑CSCF serving of the user;
- to check that it has a valid address in SMS for the sender as well as the recipient when receiving an IMS message for an SMS user. The IP-SM-GW shall obtain a valid address for both from the SIP headers of the IMS message (e.g. the sender would be identified in the asserted id in form of TEL URI);
- for terminating procedures:
- if TEL URI is available, it maps the recipient's address from an MSISDN/IMSI to TEL URI format when receiving an SMS for an IP-based UE, and then it is the responsibility of the IMS core to perform any further mapping towards a SIP URI as required;
- if TEL URI is not available, it maps the recipient's address from an IMSI to SIP URI format when receiving an SMS for an IP-based UE.
- to act as an Application Server towards the IMS core;
- to perform domain selection to choose the appropriate domain to deliver a message to a recipient and to obtain the MSC, SGSN, MME and/or SMSF addresses from the HSS; and
- to manage flags indicating user availability for SMS termination in the HSS and in IP-SM-GW.
- for MSISDN-less SMS operation:
- if the recipient is not addressed with MSISDN but with SIP-URI, the originating IP-SM-GW sends the SM toward to the target IMS network,
- if delivery to target UE failed, the terminating IP-SM-GW returns MSISDN-less correlation ID to allow the originating IMS network to retry later,
- if originating IP-SM-GW receives temporary delivery failure with MSISDN-less correlation ID from target IMS network, it forwards the SM along with the MSISDN-less correlation ID to SMSC for store and forwarding.
- to handle Resource-Priority information, including setting the transport priority of an outgoing Short Message.
|
b57c39c719229455cea55c4a75308a42
|
23.204
|
5.3.1.2 Transport-level interworking
|
The additional functions of the IP-SM-GW when interworking is done by carrying encapsulated Short Messages in IMS messages are:
- to communicate with the UE using IMS messaging as transport while maintaining the format and functionality of the Short Message;
- to carry the SMS status messages as encapsulated bodies of IMS messages;
- to store the subscriber data of the short message service similar to the data for the current CS/PS domain and to perform the short message authorization as performed by the MSC/SGSN/MME/SMSF, as well as to store additional service data on the service authorisation of the encapsulated Short Message delivery via IMS and to perform the service authorization.
NOTE 1: The short message subscriber data of the CS/PS domain and additional service data on the authorisation of encapsulated Short Message delivery via IMS are retrieved from the HLR/HSS via third party registration procedure as specified in the clause 6.1. The IP‑SM‑GW can request the HSS to send a notification whenever the subscriber data and/or additional service data is updated, which the IP‑SM‑GW can then retrieve.
NOTE 2: The mechanism for prioritizing whether the short message is delivered via a GSM/UMTS or other IP‑CAN connection when the terminal is simultaneously connected to both access networks is outside the scope of this specification.
|
b57c39c719229455cea55c4a75308a42
|
23.204
|
5.3.1.3 Service-level interworking
|
The additional functions of the IP-SM-GW when service-level interworking is done between Short Messages and Instant Messages in IMS are:
- to determine whether to transform the message format or not, and to perform the transformation of the message format when determined.
- to use the SC address retrieved either as part of the subscriber data from the HSS at registration or as provisioned by configuration, when transforming the Instant Message into Short Message.
- to perform the authorization for service-level interworking.
The additional functions of the IP-SM-GW when service-level interworking is done between Short Messages and CPM Messages in IMS are the same as functions performed for Instant Messages in IMS and additionally:
- to translate a chat session invitation to a short message including instructions for the SMS user how to react (accept/reject) the chat session invitation, if operator policy mandates the consent of the SMS user. Otherwise the IP-SM-GW shall respond a chat session invitation on behalf of the SMS user (accept/reject), according to operator policy;
- to translate the SMS user's answer to a chat session invitation to a proper response for the chat session invitation request;
- to inform SMS user about the changes of group chat session parameters;
- to translate a chat session teardown request to a short message, if operator policy mandates it; and
- to translate the SMS user's request to leave a chat session to a proper CPM request.
|
b57c39c719229455cea55c4a75308a42
|
23.204
|
5.3.2 HSS/UDM
|
In order to support SMS over generic IP access, the HSS/UDM shall support the following functions:
- storing the pre-configured address of the IP-SM-GW on a subscriber basis;
NOTE: If all subscribers are assigned to a single IP‑SM‑GW address, the IP‑SM‑GW address does not need to be pre-configured in the HSS.
- handling an indication that the terminal is registered with an IP-SM-GW for delivery of SMS;
- storing the SMSF address when the SMSF registers with the UDM as specified in TS 23.502 [24];
- responding to the "send routing information for short message" query from IP‑SM‑GW with the address of the MSC/SGSN/MME/SMSF;
- forwarding the Send Routeing Information for Short Message, from an SMS-GMSC, towards the IP-SM-GW and forwarding any responses to the originator of the Send Routeing Information for Short Message;
- returning the IMSI and the MSC, SGSN, MME and/or SMSF addresses as a response to Send Routeing Information for Short Message required from IP-SM-GW;
- alerting the SCs stored in the message waiting data when the terminal is registered with an IP‑SM‑GW for delivery of short message;
- reporting notification to the IP-SM-GW of the reachability of a UE at the transport layer after a delivery failure;
- accepting delivery status reports from IP-SM-GWs instead of SMS-GMSC.
- storing the MPS for Messaging indication, as specified in TS 23.401 [25] and TS 23.501 [23].
- setting the transport priority for all messages related to MPS for Messaging.
|
b57c39c719229455cea55c4a75308a42
|
23.204
|
6 Procedures
| |
b57c39c719229455cea55c4a75308a42
|
23.204
|
6.0 General
|
The clause describes the procedures for the support of transport-level interworking between Short Message service and encapsulated Short Message via IP service, for the support of the service-level interworking for the Short Message service and Instant Messaging service as defined in OMA-TS-SIMPLE_IM-V1_0 [12], for the support of the service-level interworking for the Short Message service and Converged IP Messaging service as defined in OMA-TS-CPM_Conv_Fnct-V1_0 [17] and for the support of receiving MT-SMS to a UE without MSISDN. Clauses only applying to either transport-level interworking or service-level interworking are indicated as such.
NOTE: In the procedures in the following clauses, the I‑CSCF, P‑CSCF and ASs such as IM AS, as well as nodes specific to CPM functions such as ISF, are not shown in the figures.
6.0a SMS without MSISDN in IMS
6.0a.1 MO-SMS without MSISDN in IMS
For MO-SMS without MSISDN, the IP-SM-GW of the originating side fills the RP-OA field with a value that indicates UE is MSISDN-less to satisfy the protocol requirement. If the originating UE does not have MSISDN or the recipient UE is addressed with SIP-URI (i.e., recipient is not addressed with MSISDN) then IP-SM-GW first tries to deliver the SMS directly to the terminating IMS network. If the terminating IMS network does not accept SMS delivery without MSISDN and responds with a permanent error indication, then IP-SM-GW shall abort any further re-attempt and responds back to sender that SMS delivery has failed.
If the terminating IMS network indicates the SMS delivery failed due to temporary reasons (e.g, UE is not reachable) and the response has included the MSISDN-less correlation ID for the recipient then IP-SM-GW forwards both the SM and MSISDN-less correlation ID to the SMSC for storage and for subsequent retries.
6.0a.2 MT-SMS without MSISDN in IMS
For device triggering, the selection of IMS to deliver MT-SMS without MSISDN is defined in TS 23.682 [20].
For SMS between IMS UEs without MSISDN, the delivery of MT-SMS to the recipient is based on the identity from the SIP MESSAGE received from the originating IMS network or retrieved using the MSISDN-less correlation ID from the Forward-Short-Message received from SMSC.
This clause describes the additional functionality required for the delivery of MT-SMS toward a UE in IMS without MSISDN.
During UE IMS registration procedure, the serving IP‑SM‑GW obtains IMSI of the UE from the S-CSCF and the serving IP-SM-GW address is indicated to HSS as defined in clause 6.1 and HSS stores this IP-SM-GW address. IP‑SM‑GW subscribes to event registration package to receive UE's IMPU (i.e. SIP URI). UE which does not have MSISDN will have at least one SIP-URI as IMPU. When IP-SM-GW receives SM from SMSC with IMSI as the recipient address (i.e. device triggering as defined in TS 23.682 [20]), IP‑SM‑GW shall try to deliver the MT-SMS via IMS without retrying to other domain.
When IP-SM-GW receives a SM from originating IMS network via SIP MESSAGE and IP-SM-GW failed to deliver the SM to the recipient and future retry is allowed and possible, then IP-SM-GW shall return a MSISDN-less correlation ID along with an indication of temporary error pointing to unsuccessful delivery attempt to the originating IMS network. This MSISDN-less Correlation ID includes sender's SIP URI, recipient's SIP URI, and HLR-Id which identifies receiver's HLR.
|
b57c39c719229455cea55c4a75308a42
|
23.204
|
6.1 Registration procedure
|
Figure 6.1: Registration procedure
1) The UE establishes IP connection.
2) At any time after the establishment of the IP connection, the UE registers at the S-CSCF according to the IMS registration procedures.
NOTE 1: For simplicity, not all messages between UE and S-CSCF and between S-CSCF and HSS are shown in detail.
3) S-CSCF checks the initial filter criteria retrieved from the HSS during the IMS registration procedure.
4) After successful IMS registration and based on the retrieved initial filter criteria, the S-CSCF informs the IP-SM-GW (AS) about the registration of the user. IMSI is informed to the IP‑SM‑GW (AS) when there is no MSISDN in the UE's IMS subscription profile.
5) The IP-SM-GW (AS) returns OK to the S-CSCF.
6) The IP-SM-GW (AS) sends IP-SM-GW Register Req to the HSS.
7) The HSS stores the received IP-SM-GW address if necessary or for MT-SMS without MSISDN (see clause 6.0a.2), uses it as an indication that the UE is available to be accessed via the IMS to trigger an Alert service centre message if the message waiting flag is set, and responses to the IP-SM-GW (AS) with IP‑SM‑GW Register Res. IP‑SM‑GW gets the IMPU (SIP URI) for SMS delivery without TEL-URI from registration event package.
NOTE 2: IP-SM-GW Register Res can include the SC address to be used for this user in the subscriber data (see also clause 6.7).
NOTE 3: If the IP‑SM‑GW address stored in the HSS via registration procedure is not the same as the preconfigured IP‑SM‑GW address (if any), then the short message delivery attempted during registration can be unnecessarily delayed.
8) After successful registration of the IP‑SM‑GW address at the HSS the HSS checks whether message waiting data are stored and alerts all SCs using procedures described in TS 23.040 [2] (see also clause 6.5b).
|
b57c39c719229455cea55c4a75308a42
|
23.204
|
6.2 De-registration procedure
| |
b57c39c719229455cea55c4a75308a42
|
23.204
|
6.2.1 UE initiated
|
Figure 6.2: UE initiated de-registration procedure
1) At any time after the registration procedure, the UE may initiate a de-registration procedure. The UE sends a De-Register request (Register request with Expires header having value 0) to the S-CSCF.
2) S-CSCF responds to the UE with OK.
3) S-CSCF checks the initial filter criteria retrieved from the HSS during the IMS registration procedure.
4) Based on initial filter criteria the S-CSCF informs the IP-SM-GW (AS) about the de-registration of the user.
5) The IP-SM-GW (AS) returns OK to the S-CSCF.
6) The IP-SM-GW (AS) de-registers the UE at the HSS sending a De-register Req.
7) The HSS de-registers the UE and responds to the IP-SM-GW (AS) with De-register Res.
NOTE: The pre-configured IP‑SM‑GW address in the HSS, if any, is not removed, as it is used for subsequent SM termination.
|
b57c39c719229455cea55c4a75308a42
|
23.204
|
6.2.2 Network initiated
|
Figure 6.2a: Network initiated de-registration procedure
1) After receiving a trigger (e.g. De-Register message from the S‑CSCF), the IP‑SM‑GW shall de-register the IP‑SM‑GW of a subscriber from the HSS sending a De-Register Req.
2) The HSS de-registers the UE and responds to the IP‑SM‑GW (AS) with De‑register Res.
|
b57c39c719229455cea55c4a75308a42
|
23.204
|
6.3 Transport-level interworking: Successful encapsulated Short Message origination procedure with MSISDN
|
Figure 6.3: Successful encapsulated Short Message origination procedure
1) The UE registers to S-CSCF according the IMS registration procedure. Note that I-CSCF and P-CSCF are not shown in this figure.
2) UE submits the encapsulated Short Message (SMS-SUBMIT, SC Address) to the S-CSCF using an appropriate SIP method.
3) S-CSCF forwards the encapsulated Short Message (SMS- SUBMIT, SC Address) to IP-SM-GW (AS) based on stored iFC.
4) IP-SM-GW (AS) acknowledges the SIP message.
5) SIP message acknowledge is forwarded by S-CSCF to UE.
6) The IP-SM-GW performs service authorization based on the stored subscriber data as described in the clause 6.1. The IP‑SM‑GW shall check whether the subscriber is authorised to use the short message service (e.g. Operator Determined Barring settings), similar to the authorization performed by MSC/SGSN in case the Short Message is delivered via CS or PS domain. In addition, the IP-SM-GW shall also check whether the user is authorised to use the encapsulated Short Message delivery via IMS. If the result of service authorization is negative, the IP-SM-GW shall not forward the message, and shall return the appropriate error information to the UE in a failure report. Otherwise, the IP-SM-GW (AS) extracts the Short Message (SMS- SUBMIT) and forwards it towards the SMS-SC (SC Address) via the SMS-IWMSC using standard MAP or Diameter based (SGd/Gdd) signalling (as described in TS 23.040 [2]).
7) The SMS-IWMSC forwards the Short Message (SMS-SUBMIT) to the SMS-SC (see TS 23.040 [2]).
8) SMS-SC sends a Submit report (SMS-SUBMIT‑REPORT) to SMS-IWMSC (see TS 23.040 [2]).
9) SMS-IWMSC sends the Submit report to IP-SM-GW (AS) (see TS 23.040 [2]).
10) IP-SM-GW (AS) sends the Submit report to S-CSCF, encapsulated in an appropriate SIP request.
11) The S-CSCF sends the Submit report to the UE.
12) The UE acknowledges the SIP request.
13) The S-CSCF forwards the acknowledgement of the SIP request to IP-SM-GW (AS).
6.3a Transport-level interworking: Short Message origination procedure without MSISDN
6.3a.1 Initial delivery of SMS without MSISDN
Figure 6.3a.1 shows the initial SM delivery by IP-SM-GW during MO-SMS operation without MSISDN.
Figure 6.3a.1: Short Message origination procedure for MSISDN-less operation
1) The UE-A registers to S-CSCF according the IMS registration procedure. Note that I-CSCF and P-CSCF are not shown in this figure.
2) UE-A submits the encapsulated Short Message (SMS-SUBMIT, SC Address) to the S-CSCF using an appropriate SIP method. Since recipient does not have MSISDN, the UE-A fills the TP-DA field with value that indicates recipient UE is addressed without MSISDN, and indicates recipient's SIP URI in SIP MESSAGE (e.g. UE-A sets the R-URI to PSI (SMSC address) and the To header with recipient's SIP URI in the MESSAGE). Based on the existing procedure, P-CSCF fills the UE-A's default URI to p-asserted-identity before sending the MESSAGE to S-CSCF.
NOTE: It is up to stage 3 to define how recipient's SIP URI is to be indicated in the protocol level.
3) S-CSCF forwards the encapsulated Short Message (SMS-SUBMIT, SC Address) to IP-SM-GW (AS) based on stored iFC.
4) IP-SM-GW (AS) acknowledges the SIP message.
5) SIP message acknowledge is forwarded by S-CSCF to UE-A.
6) The IP-SM-GW performs service authorization based on the stored subscriber data as described in the clause 6.1. The IP SM GW shall check whether the subscriber is authorised to use the short message service (e.g. Operator Determined Barring settings), similar to the authorization performed by MSC/SGSN in case the Short Message is delivered via CS or PS domain. In addition, the IP-SM-GW shall also check whether the user is authorised to use the encapsulated Short Message delivery via IMS. If the result of service authorization is negative, the IP-SM-GW shall not forward the message, and shall return the appropriate error information to the UE in a failure report. Otherwise, the IP-SM-GW (AS) extracts the Short Message (SMS-SUBMIT) and constructs the SMS-DELIVER and sends it towards the terminating IMS network.
7) The terminating IMS network tries to deliver the SM toward the designated recipient (see clause 6.4a).
8) Terminating IMS network response with one of the following:
8a) Terminating IMS network refuses or does not allow SMS delivery with MSISDN-less operation by sending back a permanent error.
8b) Terminating IMS network is not able to deliver the SM to designated recipient and returns a MSISDN-less correlation ID to allow retries at a later time. IP-SM-GW then forwards the SM to SMSC for storage and forward operation (see clause 6.3a.2).
8c) Terminating IMS network is successfully deliver the SM toward the designated recipient.
9) Proper response as determined in step 8a, 8b, or 8c is returned back to UE-A. For 8a, the response indicates to the UE-A that SMS to this recipient is failed permanently. For 8b, the response is the Submit report received from the SMSC. For 8c, the response indicates a successful delivery of the SM to the recipient.
6.3a.2 Subsequent re-delivery of SMS without MSISDN
When the initial delivery attempt failed and retry is possible (see Figure 6.3a.1 step 8b), the IP-SM-GW forwards the SM to SMS-SC for storage and forwarding operation. Figure 6.3a.2 shows the subsequent re-delivery attempt of SM by SMS-SC.
Figure 6.3a.2: Redelivery attempt of SM without MSISDN
1) IP-SM-GW forwards the SM along with the MSISDN-less correlation ID received in step 8b of figure 6.3a.1 to SMS-SC/SMS-IWMSC.
2a) SMS-SC/SMS-GMSC receives a trigger to re-deliver the SMS from HSS (see clause 6.5b) and queries the HSS for serving node information using the recipient's SIP URI and HLR-id from the MSISDN-less correlation ID.
2b) SMS-GMSC forwards the SM along with the MSISDN-less correlation ID to the IP-SM-GW using the address (i.e. IP-SM-GW of UE-B) received from HSS in step 2a.
3) IP-SM-GW (terminating) delivers SM to UE-B via the SIP MESSAGE.
|
b57c39c719229455cea55c4a75308a42
|
23.204
|
6.4 Transport-level interworking: Successful encapsulated Short Message termination procedure from SMS-GMSC
|
Figure 6.4: Successful encapsulated Short Message termination procedure
1) The UE registers to the S-CSCF according to the IMS registration procedure.
2) The SMS-SC forwards the Short Message (SMS‑DELIVER) to the SMS-GMSC.
3) Steps 3a to 3c are performed if SMS GMSC interrogates the HSS with MSISDN. For MT-SMS without MSISDN as defined in clause 6.0a, step 3d is performed if an IP-SM-GW address is available and need not be retrieved, and steps 3e to 3f are performed if an IP-SM-GW address needs to be retrieved.
3a) The SMS‑GMSC interrogates the HSS (using MSISDN) to retrieve routeing information. Based on the pre-configured IP-SM-GW address for the user, the HSS forwards the request to the corresponding IP-SM-GW.
NOTE 1: The Send Routeing Info for SM request is not forwarded if it has been sent originally from the IP‑SM‑GW.
NOTE 2: If there is only a single IP‑SM‑GW address, the IP‑SM‑GW address does not need to be pre-configured in the HSS, the Send Routeing Info for SM request can be forwarded on the STP level.
3b) The HLR/HSS returns the addresses of the current MSC, SGSN, MME or SMSF to the IP‑SM‑GW for delivery of the Short Message in CS/PS domain. The HLR/HSS also returns the IMSI, for the IP‑SM‑GW to correlate the receipt of Short Message from the MT Correlation ID within the IMSI field of the Forward Short Message.
3c) The IP SM GW creates a MT Correlation ID as per TS 23.040 [2] which associates the Send Routeing Info for SM with the subsequent Forward Short Message messages(s), and stores this along with the IMSI of the receiving subscriber. The IP-SM-GW returns only one address, which is of itself, along with the MT Correlation ID as routeing information to the SMS-GMSC.
NOTE 3: For the case where the IP‑SM‑GW address is not pre-configured in the HSS, the Send Routeing Info for SM request will be forwarded on the STP level, the IP-SM-GW returns the address of itself as routeing information to SMS-GMSC upon receipt of the forwarded Send Routeing info for SM request.
3d) Interrogation is skipped in the context of T4 device triggering if an up to date IP-SM-GW address is already available at the SMS-SC/SMS-GMSC.
3e) The SMS GMSC interrogates the HSS (using IMSI) to retrieve routeing information.
3f) HLR/HSS returns the addresses of IP-SM-GW, MSC (MME), SGSN and/or SMSF. If IMS is to be used for MT-SMS then continue with step 4.
4) If steps 3a to 3c have been taken, SMS-GMSC delivers the Short Message (SMS‑DELIVER) to IP-SM-GW (AS) including the MT Correlation ID received from the IP‑SM‑GW, in the same manner that it delivers the Short Message to an MSC, SGSN, MME or SMSF. Otherwise, SMS-GMSC delivers the Short Message (SMS DELIVER) to IP-SM-GW (AS) including the IMSI.
5) The IP‑SM‑GW performs service authorization based on the stored subscriber data described in the clause 6.1. The IP‑SM‑GW shall check whether the subscriber is authorised to use the short message service (e.g. Operator Determined Barring settings), similar to the authorization performed by MSC/SGSN/MME/SMSF in case the Short Message is delivered via CS or PS domain. In addition, the IP‑SM‑GW shall also check whether the subscriber is authorised to use the encapsulated Short Message delivery via IMS. If the result of service authorization is negative, the IP‑SM‑GW shall not forward the message, and shall return the appropriate error information to the SMS-SC in a failure report. Domain selection function is not performed for MT-SMS without MSISDN (i.e. when IMSI is received in step 4) and IMS is used for delivery. Otherwise (i.e. when a MT Correlation ID is received in step 4), the IP-SM-GW performs domain selection function to determine the preferred domain for delivering the message according to operator policy and user preferences. The logic for selecting preferred route for message delivery is a matter of implementation.
6) If the preferred domain is IMS, the IP-SM-GW (AS) uses the TEL-URI associated with the IMSI of the message received for the target UE to send the Short Message (SMS‑DELIVER, SC Address) encapsulated in the appropriate SIP method towards the S-CSCF. If TEL URI is not available, SIP URI is used.
7) S-CSCF forwards the encapsulated Short Message (SMS-DELIVER, SC Address) to the UE.
8) The UE acknowledges the SIP request.
NOTE 4: This is not yet the Delivery report.
9) The S-CSCF forwards the acknowledgement of the SIP request to the IP-SM-GW (AS).
6.4a Transport-level interworking: Short Message termination procedure without MSISDN from IMS network
Figure 6.4a: Short Message termination procedure without MSISDN
1) The UE-B registers to the S-CSCF according to the IMS registration procedure.
2) The originating IMS network which received the SM from the UE-A forwards the Short Message (SMS-DELIVER) to the terminating IMS network. It reaches the IP-SM-GW responsible for UE-B. For brevity, the intermediate IMS nodes interactions prior to reaching IP-SM-GW are not shown.
3) If local policy allows MSISDN-less SMS operation, IP-SM-GW tries to deliver the SM to UE-B.
4a-4b) SM is successfully delivered to UE-B. A success Delivery report is sent to the originating IMS network.
5a) If IP-SM-GW tried to deliver the SM but encountered some error (e.g. UE is memory full, UE not reachable, etc) then:
5b) IP-SM-GW returns a MSISDN-less Correlation ID to originating IMS network along with an indication of temporary failure.
6a-6b) if the IP-SM-GW refuses the MSISDN-less SMS operation due to local policy or other permanent errors (e.g. protocol error), IP-SM-GW returns a permanent error indication to the originating IMS network.
|
b57c39c719229455cea55c4a75308a42
|
23.204
|
6.5 Transport-level interworking: Delivery Report procedure
|
Figure 6.5: Delivery report procedure
1) The UE has received the Short Message as described in clause 6.4 or clause 6.4a.
2) The UE sends a Delivery report (SMS‑DELIVER‑REPORT) to the S-CSCF, including either a positive or a negative acknowledgement to the Short Message received in step 1.
3) The S-CSCF forwards the Delivery report to the IP-SM-GW (AS). It shall be ensured that the Delivery report reaches the same IP-SM-GW that forwarded the Short Message in step 1.
4) IP-SM-GW (AS) acknowledges, at the SIP level, the Delivery report to S-CSCF.
NOTE: This is the acknowledgement to the Forward Short Message in the SM termination procedure.
5) S-CSCF forwards the SIP acknowledgement to the Delivery report to the UE.
6) The IP-SM-GW (AS) sends a Delivery report to the SMS-GMSC or to originating IMS network for MSISDN-less SMS operation.
7) The IP-SM-GW may send a Report SM Delivery Status to the HSS. This may trigger the Alert service centre procedure or an update of the message waiting data in the HSS as described in TS 23.040 [2], if necessary.
8) The SMS-GMSC may send a Report SM Delivery Status to the HSS. The HSS shall ignore the information provided in this report.
6.5a Unsuccessful SM termination procedure
When a Short Message fails to reach the UE via the selected domain, a failure delivery report is returned to the IP‑SM‑GW. The IP‑SM‑GW takes responsibility to re-attempt the delivery of the message in another domain which is listed in the sequence of the priority in the IP‑SM‑GW while the domain selection is performed during the SM termination procedure. If the message successfully reaches the UE after re-delivery, the IP‑SM‑GW forwards the received successful Delivery report to the SMS‑GMSC. Otherwise, if the message still fails after the IP‑SM‑GW has tried all selectable domains, the IP-SM-GW forwards the received unsuccessful Delivery report to the SMS‑GMSC and sends Report SM Delivery Status message to the HLR/HSS. The HLR/HSS then records the corresponding Messages Waiting Data (MWD), and an Alert service centre procedure may be initiated as described in clause 6.5b or 6.6. The IP-SM-GW sets UE-Not-Reachable-for-IP (UNRI) locally as defined in TS 23.040 [2].
The order in which domains are selected for message delivery by the IP‑SM‑GW is subject to operator policy and/or user preferences and any known or assumed timer values in the SMS-GMSC for the Forward Short Message message (see NOTE 1).
The following flow shows only an example order of selected domains, i.e. the IMS is the preferred domain, followed by the PS domain, and finally the CS domain.
NOTE 1: If the timer at the SMS-GMSC has been configured to a short value (near to the minimum value), the IP‑SM‑GW may not have sufficient time to try the message delivery in all three domains. This problem can be resolved by several implementation solutions, e.g. re-configuring the SMS-GMSC timer to be longer, enhancing the IP-SM-GW to try the delivery only in two or one domain(s).
Figure 6.5a: Unsuccessful SM termination procedure
1) As described in clause 6.4, the Short Message is routed to the UE via S‑CSCF after the domain selection is performed in the IP‑SM‑GW and all the available domains have been listed in the sequence of the priority in the IP‑SM‑GW. The message fails to reach the UE, e.g. due to the UE not being reachable in IMS, or exceeded memory capacity of the UE.
2) The S‑CSCF sends an appropriate failure message according to normal IMS procedure as defined in TS 23.228 [9], and sends it to the IP‑SM‑GW (AS) including an appropriate error value. This Delivery report is an acknowledgement to the Short Message received by the S-CSCF in step 1.
NOTE 2: When the failure message is sent from the UE, e.g. the UE notifies the network that the UE has been unable to accept a Short Message because its memory capacity has been exceeded, the S‑CSCF forwards the failure message to the IP‑SM‑GW (AS).
3) IP‑SM‑GW (AS) acknowledges the failure message to S‑CSCF.
4) The IP‑SM‑GW verifies the error cause of the failure delivery report. If the error is due to exceeded memory capacity of the UE, the IP‑SM‑GW forwards the Delivery report (SMS‑DELIVER‑REPORT) back to the SMS-GMSC and the procedure continues as described in step 16. Otherwise, the IP‑SM‑GW forwards the Short Message to the domain which is listed in the second place in its priority list. It is supposed that the SGSN is selected.
5) The SGSN delivers the message to the UE but the message fails to reach the UE, e.g. the UE is not reachable in PS domain.
NOTE 3: If the delivery succeeds in the PS domain at this point, the procedure for successful message delivery over PS domain is described in clause 6.4.
6) The SGSN generates a Delivery report (SMS‑DELIVER‑REPORT) and sends it to the IP‑SM‑GW, including an appropriate error value. This Delivery report is an acknowledgement to the Short Message received by the SGSN in step 5.
7) The IP-SM-GW forwards the Short Message to the domain which is listed in the third place in its priority list. It is supposed that the MSC is selected.
8) The MSC delivers the message to the UE but the message fails to reach the UE, e.g. the UE is not reachable in CS domain.
NOTE 4: If the delivery succeeds in the CS domain at this point, the procedure for successful message delivery over CS domain is described in clause 6.4.
9) The MSC generates a Delivery report (SMS‑DELIVER‑REPORT) and sends it to the IP‑SM‑GW, including an appropriate error value. This Delivery report is an acknowledgement to the Short Message received by the MSC in step 8.
10) The IP-SM-GW forwards the Short Message to the domain which is listed in the forth place in its priority list. It is supposed that the MME is selected.
11) The MME delivers the message to the UE but the message fails to reach the UE, e.g., the UE is not reachable in PS domain.
12) The MME generates a Delivery report (SMS-DELIVER-REPORT) and sends it to the IP-SM-GW, including an appropriate error value. This Delivery report is an acknowledgement to the Short Message received by the MME in step 11.
13) The IP-SM-GW forwards the Short Message to the domain which is listed in the fifth place in its priority list. It is supposed that the SMSF is selected.
NOTE 5: If the IP-SM-GW acquires two SMSF addresses from the HSS, the IP-SM-GW tries to deliver the message one by one.
14) The SMSF delivers the message to the UE but the message fails to reach the UE, e.g. the UE is not reachable in PS domain.
15) The SMSF generates a Delivery report (SMS-DELIVER-REPORT) and sends it to the IP-SM-GW, including an appropriate error value. This Delivery report is an acknowledgement to the Short Message received by the SMSF in step 14.
16) The IP‑SM‑GW sends a Delivery report to the SMS‑GMSC.
NOTE 6: The SMS-GMSC is aware of the availability of the UE on only one domain (see clause 6.4), and so will not attempt redelivery to another domain after receiving a failure report.
17) The IP-SM-GW sends a Report SM Delivery Status to the HSS with accurate results from different domains. The HSS records the corresponding MWD, i.e. the SMS‑SC address which stores the un-delivered message and the failure reason which indicates that the message failed to be sent by IP‑SM‑GW due to the UE not being available or the memory capacity of the UE being exceeded. The IP-SM-GW sets UNRI locally.
18) The IP-SM-GW subscribes to the HSS for a one-time notification of the UE being reachable again. The HSS records the subscription and instructs the transport layer to report when the UE is reachable.
19) The SMS-GMSC sends a Report SM Delivery Status to the HSS. The HSS shall ignore the information provided in this report.
6.5b Alert Service Centre procedure when UE is available
When a Short Message is received in the IP-SM-GW for delivery to an IMS subscriber, the IP-SM-GW shall verify the registration status of the UE. If the UE is not registered in IMS, or is registered in IMS but does not advertise the Converged IP Messaging, SIMPLE IM or SMSIP capability, the Short Message shall not be interworked; neither at service level nor at transport level. Based on operator policy and user preferences, either the message is sent over CS/PS or an error indication is sent back to the SMS-SC. In the latter case, when the UE registers in IMS advertising the Converged IP Messaging, SIMPLE IM and/or the SMSIP capability at a later time, this information is sent to the SMS-SC and the delivery is attempted at that time, as an Instant Message or an encapsulated Short Message as appropriate.
NOTE: The service level or transport level interworking of a message is prohibited as identified in the above scenario in order to prevent the possibility of the message being deferred in the terminating network.
If the IP-SM-GW detects the UE is reachable for SMS over IP and the UE is registered with support of Converged IP Messaging, SIMPLE IM or SMSIP capability, the IP-SM-GW clears local UNRI and informs HLR/HSS that the UE is available again.
If the HLR/HSS has recorded the MWD with a failure reason that the message failed to be sent by IP‑SM‑GW due to the UE not being available, once the HLR/HSS receives a message from any of the domains indicating that the UE is available again, e.g. IMSI attached, or IMS registered, the HLR/HSS initiates an Alert service centre procedure to request the SMS-SC to re-send the stored message.
The following figure shows an example of how a deferred message is re-transmitted to an IMS UE upon the UE availability.
Figure 6.5b: Alert service centre procedure when UE is available
1) The message is transmitted from SMS‑SC to IP‑SM‑GW for delivery to the subscriber, possibly after transport-level and/or service-level interworking. Prior to this interworking, the IP‑SM‑GW shall check for UE availability. If the UE is not registered in IMS, and delivery over CS/PS is unsuccessful (see clause 6.5a), the IP‑SM‑GW returns an appropriate error response to SMS‑SC. The SMS-SC then informs the HSS/HLR about the unavailability of the UE. After an unsuccessful SM termination procedure due to the UE being unavailable, the HSS records the MWD i.e. the SMS‑SC address which stores the un-delivered message and the failure reason which indicates that the message failed to be sent by IP‑SM‑GW due to the UE not being available, for a subsequent Alert service centre procedure.
At any time after the unsuccessful SM termination procedure, the UE may attach in the PS and or CS domain again, in which case a Ready for SM message from the SGSN, MSC, MME or SMSF is sent to the HLR/HSS as described in TS 23.040 [2]. The HLR/HSS initiates an Alert service centre procedure to the SM‑IWMSC when the user's MWD is not NULL, and the procedure continues as described in step 3.
2) At any time after the unsuccessful SM termination procedure, the status of the UE may indicate that the UE is available due to, e.g. registration in IMS (step 2a). At that point UE-Not-Reachable-for-IP (UNRI) is updated in HLR/HSS, as described in TS 23.040 [2]. After the IMS registration is finished, the procedure continues as described in step 3.
At any time after the unsuccessful SM termination procedure, the HSS can receive a notification from the transport layer e.g. MME that the UE is reachable again (step 2b). As the IP-SM-GW has subscribed to the event as described in clause 6.5a, the HSS shall notify the IP-SM-GW of the UE being reachable again (step 2c). If the UE is already registered in IMS, the IP-SM-GW shall then send a Ready for SM message to the HLR/HSS (step 2d) and the procedure continues as described in step 3. Otherwise, the IP-SM-GW discards the notification message. The procedure will resume when one of the conditions described in steps 1 and 2 is fulfilled.
3) The HLR/HSS checks the user's MWD. If MWD is not Null, the HLR/HSS initiates an Alert service centre message to the SMS‑IWMSC.
4) The SMS‑IWMSC forwards the Alert service centre procedure to the responding SMS‑SC.
5) Upon receipt of the Alert service centre message, the SMS‑SC re-attempts to send the stored Short Message. The message is transmitted to IP-SM-GW and thereafter to the UE after appropriate interworking (transport-level and/or service-level interworking) is performed. The UE acknowledges the reception of the message.
|
b57c39c719229455cea55c4a75308a42
|
23.204
|
6.6 Transport-level interworking: Alert service centre procedure when memory capacity is available
|
If the HLR/HSS has recorded the MWD with a failure reason that the message failed to be sent by IP‑SM‑GW due to the memory capacity of the UE is exceeded, once the HLR/HSS receives a message from any of the domain indicating that the memory capacity of the UE is available again, e.g. form the IMS, PS or CS domain, the HLR/HSS initiates a Alert service centre procedure to request the SMSC to re-send the stored message.
The following figure only shows an example where the HLR/HSS invokes the Alert service centre procedure when the memory capacity available message is received from IMS.
Figure 6.6: Alert service centre procedure when memory capacity is available
1) If SM termination attempts (via IP-SM-GW) failed because the UE's Memory Capacity Exceeded, the message to be transferred to IP Based UE is queued in the SMS-SC.
2) UE sends a message to IP-SM-GW indicating that the UE has memory available to receive one or more Short Messages.
3) IP-SM-GW notifies the HLR/HSS of memory being available in the UE.
4) If the HLR/HSS receives the indication that the UE has memory available to receive one or more Short Messages, it initiates a Alert service centre procedure with the SC address and the MSIsdn‑Alert to SMS‑IWMSC as described in TS 23.040 [2].
5) The SMS‑IWMSC forwards the Alert service centre message to the SMS-SC whose address was provided by the HLR/HSS in step 4.
|
b57c39c719229455cea55c4a75308a42
|
23.204
|
6.7 Service-level Interworking: IM or CPM capable UE sends an Instant Message to an SMS user
|
Figure 6.7: Successful IM origination to SMS procedure
1) The UE registers to S-CSCF according the IMS registration procedure.
2) UE submits the Instant Message to the S-CSCF using an appropriate SIP method. The UE may request to hide its Public User Identity from the recipient within the Instant Message, as described in OMA‑TS‑SIMPLE_IM‑V1_0 [12] or in OMA-TS-CPM_Conv_Fnct-V1_0 [17]. If the P-CSCF (not shown in the figure) has received an indication from the S-CSCF that MPS for Messaging is set (enabled) for the UE in the HSS (see TS 23.228 [9]), the P-CSCF sets the Resource-Priority information on the Instant Message to a value appropriate for MPS, sets the transport priority of the Instant Message to a value appropriate for MPS and handles the Instant Message with priority.
3) S-CSCF forwards the Instant Message to IP-SM-GW based on stored iFC.
NOTE 1: Subscribers with no subscription for service level interworking will not be provided with the relevant iFCs.
4) The IP-SM-GW shall decide whether to perform service-level interworking depending on SIP request header (e.g. Request-URI), operator policy, when the Instant Message is not routable in the IMS. If an ISF is deployed in the network, the ISF may take the decision to interwork using SMS and sends the message to the IP-SM-GW to perform the interworking. If IP-SM-GW decided to perform service-level interworking, the IP-SM-GW performs service authorization based on the stored subscriber data retrieved from the HLR/HSS at the time of the registration procedure as specified in clause 6.1. The IP-SM-GW shall check whether the originating subscriber is authorised to use the interworking service. If the result of service authorization is negative, the IP-SM-GW shall not forward the message, and shall return the appropriate error information to the UE in a failure report. Otherwise, the IP-SM-GW shall use the SC Address in the subscriber data retrieved from the HSS at registration or provisioned by configuration and translates the Instant Message to a Short Message (SMS- SUBMIT) carrying SC Address, then forwards it towards SMS-SC (SC Address) via the SMS-IWMSC (as described in TS 23.040 [2]). If the size of the content of the Instant Message is larger than the size of the content that one Short Message could transfer, the IP-SM-GW shall split the content of the Instant Message into several parts, translate them to concatenated Short Messages, and forward the concatenated Short Messages to the SMS-SC as described in TS 23.040 [2]. If the sender of the Instant Message requests to hide its Public User Identity from the recipient and operator policy allows for this, the IP-SM-GW shall anonymize the identity of the user to the recipient. Otherwise, if operator policy prohibits this, the IP SM GW shall return an appropriate error to the user.
If the Resource-Priority information on the Instant Message has a value appropriate for MPS, the IP-SM-GW sets the transport priority of the outgoing Short Message to a value appropriate for MPS and handles the Short Message with priority.
5) If service authorization is successful, the IP-SM-GW acknowledges the Instant Message.
6) Instant Message acknowledgement is forwarded by S-CSCF to UE.
NOTE 2: Steps 5 and 6 can occur anytime after the subscriber authorization check has been performed by the IP‑SM‑GW.
7) The SMS-IWMSC forwards the Short Message (SMS- SUBMIT) to the SMS-SC (see TS 23.040 [2]).
8) The SMS-SC sends a Submit report (SMS-SUBMIT REPORT) to the SMS-IWMSC (see TS 23.040 [2]).
9) SMS-IWMSC sends a Submit report to IP-SM-GW (see TS 23.040 [2]).
NOTE 3: The procedure can end in step 9. Steps 10 to 13 occur only if the IM user requested a processing notification in the Instant Message sent in step 2, as described in IETF IMDN RFC 5438 [13].
10) IP-SM-GW translates the received Submit report to an appropriate Instant Message, and forwards it to the S‑CSCF. If the IP‑SM‑GW sent concatenated Short Messages to SMS-SC in step 4, the IP‑SM‑GW should wait for the last Submit report, and translate the last Submit report to an appropriate Instant Message, and forward it to the S‑CSCF.
11) S-CSCF sends the translated Instant Message to the UE.
12) UE acknowledges the translated Instant Message.
13) Acknowledgement of the translated Instant Message is forwarded by S-CSCF to IP-SM-GW.
|
b57c39c719229455cea55c4a75308a42
|
23.204
|
6.8 Interaction between transport-level and service-level Interworking
| |
b57c39c719229455cea55c4a75308a42
|
23.204
|
6.8.1 General
|
The interaction between transport-level interworking (between SMS over CS/PS and SMS over IMS) and service-level interworking (between Instant Messaging and SMS) depends on the user subscription and authorisation, on the UE capabilities, and on operator policy.
If a user is only subscribed to either transport-level interworking or service-level interworking, only procedures defined for the subscribed interworking may be performed.
If a user is subscribed to both transport-level interworking and service-level interworking, but the user is only authorised for one of the interworking when the message is processed, only the authorised interworking may be performed.
If a user is subscribed to both transport-level interworking and service-level interworking, and is authorised for both, the behaviour of the IP-SM-GW depends on the specific scenario, on the registered capabilities of the UE, and finally is defined by operator policy and user preferences.
For a user subscribed to service-level interworking, two Application Servers in the network are normally called upon to handle an Instant Message:
- the IM AS, defined in OMA-TS-SIMPLE_IM-V1_0 [12] or the CPM AS, defined in OMA-TS-CPM_Conv_Fnct-V1_0 [17].
- the IP-SM-GW.
The following clauses describe the different interaction scenarios.
|
b57c39c719229455cea55c4a75308a42
|
23.204
|
6.8.2 IMS Originating
|
In the originating network, a UE sends a SIP MESSAGE (Encapsulated Short Message or Instant Message). The originating S‑CSCF forwards the SIP MESSAGE to the IP-SM-GW based on the iFC. The subscription of the transport level interworking and the service level interworking applies for different iFC. However, the SIP MESSAGE is forwarded to the IP-SM-GW if the user subscribes to one of the interworking services. If there is no subscription for the interworking service, the S‑CSCF continues with the subsequent iFC check. After all the originating iFC triggers have been handled, the S‑CSCF attempts to route the message to the terminating IMS network. If it fails, an error is returned to the sender.
NOTE 1: if an IM AS or a CPM AS is present in the network, Instant Messages are routed to it before going to the IP-SM-GW.
NOTE 2: An encapsulated Short Message uses the PSI of the SC as the Request-URI. If the user is not subscribed to transport-level interworking and the IP-SM-GW is not invoked, the ENUM query fails, and an error is returned to the sender.
When the IP-SM-GW receives the SIP MESSAGE, it shall decide which interworking should be performed based on the content of the received SIP MESSAGE, as the IP-SM-GW can distinguish between an encapsulated Short Message and an Instant Message. If an encapsulated Short Message is received and if the subscriber is authorised for the service, the IP-SM-GW maps the encapsulated Short Message to a Short Message. Similarly, when an Instant Message is received, the IP-SM-GW considers performing the service-level interworking if the service is authorized: the IP‑SM‑GW shall decide whether to send the SIP MESSAGE via interworking service based on SIP request header (e.g., R‑URI), operator policy, when the Instant Message is not routeable in the IMS or when the IP-SM-GW is selected to handle the message.
Figure 6.8.2.1: Performing interworking service on originating side
|
b57c39c719229455cea55c4a75308a42
|
23.204
|
6.8.3 IMS Terminating
|
When the IP-SM-GW receives a Short Message from the legacy network on the terminating side, it performs the domain selection to determine the preferred domain to transfer the short message. If the selected network is IMS, the IP-SM-GW will determine whether the transport level interworking or the service level interworking is to be preformed based on the users' subscription and authorisation, and on the UE capability as indicated during IMS registration. If the user has subscribed to both services, is authorised for both and the UE has indicated its capability to receive both encapsulated Short Messages and Instant messages, the priority between the transport-level interworking and the service-level interworking is based on operator policy and user preferences.
NOTE 1: If the incoming Short Message is interworked to an Instant Message, the resulting Instant Message could be routed to the IM AS or CPM AS before being sent to the UE.
Figure 6.8.3.1: Performing interworking service on terminating side for an incoming Short Message
When the IP-SM-GW receives an Instant Message, based on user subscription and authorisation for service-level interworking, on operator policy and user preferences, and on UE capability indicated during IMS registration, the IP‑SM‑GW may perform service-level interworking to transform the message format to SMS and deliver the message to the UE. If the user is subscribed and authorised for transport-level interworking, and based on UE capability indicated during IMS registration, and on operator policy and user preferences, the message may be delivered as an encapsulated Short Message to the UE over IMS. Otherwise, the Short Message is delivered over CS/PS.
|
b57c39c719229455cea55c4a75308a42
|
23.204
|
6.9 Service-level Interworking: Concatenated Short Messages delivered as a large Instant Message
|
An IMS registered user with IM service or CPM service receives a concatenated short message delivered as two or more short messages. The information below describes the behaviour when the received concatenated Short Message exceeds the maximum payload size of an Instant Message.
Figure 6.9: Concatenated Short Messages delivered as an IM large message
1) The UE registers to the S-CSCF according to the IMS registration procedure.
2) The SMS-SC forwards a Short Message that is part of a concatenation of two or more Short Messages to the SMS-GMSC.
3a) The SMS GMSC interrogates the HSS to retrieve routeing information. Based on the pre-configured IP-SM-GW address for the user, the HSS forwards the request to the corresponding IP-SM-GW.
3b) The HLR/HSS returns the IMSI and the address(es) of the current MSC, SGSN, MME and/or SMSF to the IP-SM-GW for delivery of the SMS SM in CS/PS domain.
3c) The IP-SM-GW creates a MT Correlation ID as per TS 23.040 [2], which associates the Routeing Info retrieval with the subsequent Forward Short Message messages(s), and stores this along with the IMSI of the receiving subscriber. The IP-SM-GW returns to the SMS-GMSC the address of itself, along with the MT Correlation ID in the IMSI field, as routeing information. Alternatively, the IP-SM-GW may return the address(es) of the current MSC, SGSN, MME and/or SMSF, in which case, the subsequent procedure to forward the message is the same as defined in TS 23.040 [2].
4) The SMS-GMSC delivers the Short Message to the IP-SM-GW in the same manner that it delivers the Short Message to an MSC, SGSN, MME or SMSF, including the MT Correlation ID received from the IP-SM-GW, in place of the IMSI.
5) The IP-SM-GW checks whether the recipient is authorized for the interworking service. If the user is authorized, the IP-SM-GW recognizes that the received message is part of a concatenated Short Message and stores the received message.
NOTE 1: The IP-SM-GW needs to have access to a persistent storage in order to aggregate all the Short Message parts.
6) The IP-SM-GW acknowledges the Forward Short Message to the SMS-GMSC.
7) The SMS-GMSC may send a Report SM Delivery Status to the HSS. The HSS shall ignore the information provided in this report.
8) The SMS-GMSC sends a Delivery report (SMS-DELIVER-REPORT) to the SMS-SC.
9) The SMS-SC forwards the next Short Message that is part of a concatenation of two or more Short Messages to the SMS-GMSC.
NOTE 2: If this is not the last Short Message of the concatenation, then processing continues at step 4.
10) If this is the last Short Message of the concatenation, then the SMS GMSC delivers the Short Message to the IP-SM-GW in the same manner that it delivers the Short Message to an MSC, SGSN, MME or SMSF, including the MT Correlation ID received from the IP-SM-GW, in place of the IMSI.
11) The IP-SM-GW checks whether the recipient is authorized for the interworking service. If the user is authorized, the IP-SM-GW recognizes that the received message is part of a concatenated Short Message and stores it.
12-13) Once all the segments have been received, the IP-SM-GW establishes an MSRP session with the recipient's UE to deliver the message. The session invitation is sent to the recipient UE.
NOTE 3: As a matter of implementation efficiency, the IP-SM-GW may initiate the connection towards the recipient after receiving the first Forward Short Message and passing a service authorization check. This may help prevent timeouts at the SMS GMSC (while it waits for the final Delivery report) but may also result in unnecessary session initiation signalling if there is a failure in a service check for subsequently received Short Messages.
14) The IP-SM-GW delivers the message in one or more MSRP SEND requests to the recipient UE.
15) -16) The IP-SM-GW closes the session after message delivery is complete.
17) The IP-SM-GW acknowledges the Forward Short Message to the SMS-GMSC.
18) The IP-SM-GW may send a Report SM Delivery Status to the HLR/HSS for either of the following cases:
- setting of the Message Waiting flags when the Forward Short Message was unsuccessful;
- clearing of the Message Waiting flags in HLR/HSS when the Forward Short Message was successful, but had previously failed.
NOTE 4: See TS 23.040 [2] for a full explanation of when the Message Waiting flags are set and unset.
19) The SMS-GMSC may send a Report SM Delivery Status to the HSS. The HSS shall ignore the information provided in this report.
20) The SMS-GMSC sends a Delivery report (SMS-DELIVER-REPORT) to the SMS-SC.
|
b57c39c719229455cea55c4a75308a42
|
23.204
|
6.10 Service-level interworking: Status Report procedure for Instant Message to Short Message interworking
|
Figure 6.10: Status report procedure for Instant Message to Short Message interworking
1) An Instant Message from the UE is successfully delivered to the SMS user after service-level interworking. The original Instant Message requested a Disposition Notification.
NOTE 1: A Disposition Notification can be requested in the message sent by the UE in step 1 as described in IETF IMDN draft-ietf-simple-imdn [13]. If the requested Disposition Notification by the IM user is a request for a read notification, the IP-SM-GW ignores the request.
2) The SMS-SC sends a Status report to the SMS-GMSC.
NOTE 2: The Status report will, from the SMS-GMSC's point of view be treated as any SM termination.
NOTE 3: The Status report is an optional message.
3a) The SMS GMSC interrogates the HLR/HSS to retrieve routeing information. Based on the pre-configured IP-SM-GW address for the user, the HLR/HSS forwards the request to the corresponding IP-SM-GW.
3b) The HLR/HSS returns the IMSI and the address(es) of the current MSC, SGSN, MME and/or SMSF to the IP-SM-GW for delivery of the Short Message in CS/PS domain.
3c) The IP-SM-GW creates a MT Correlation ID as per TS 23.040 [2], which associates the Routing Info retrieval with the subsequent Forward Short Message messages(s), and stores this along with the IMSI of the receiving subscriber. The IP-SM-GW returns to the SMS-GMSC the address of itself, along with the MT Correlation ID in the IMSI field, as routeing information. Alternatively, the IP-SM-GW may return the address(es) of the current MSC, SGSN, MME and/or SMSF, in which case, the subsequent procedure to forward the message is the same as defined in TS 23.040 [2].
4) The SMS-GMSC sends the status report in the Forward Short Message to the IP-SM-GW.
NOTE 4: Steps 5 to 11 only occur if the original IM requested a delivery notification in the Disposition Notification.
5) The IP-SM-GW translates and maps the Status report in the Forward Short Message into an Instant Message carrying a Delivery Notification as described in the IETF IMDN draft-ietf-simple-imdn [13]. The IP‑SM‑GW should keep the message id for a message for which IMDN was requested so it can send the message id to the UE in the IMDN.
6-7) The IP-SM-GW sends a Delivery Notification within an Instant Message to the S-CSCF, which sends the Instant Message to the UE.
8-9) The UE acknowledges receipt of the Instant Message containing the Delivery Notification to the S-CSCF. The S‑CSCF sends the acknowledgment to the IP-SM-GW.
10) The IP-SM-GW sends a Delivery report (SMS-DELIVER-REPORT) to the SMS-GMSC.
11) The SMS-GMSC sends an acknowledgement back to the SMS-SC.
|
b57c39c719229455cea55c4a75308a42
|
23.204
|
6.11 IM or CPM user sends an Instant Message to an SMSIP UE
|
An IMS registered user with SIMPLE IM service or CPM service sends an Instant Message via service-level interworking as an encapsulated Short Message to an SMSIP UE, which did not indicate support for SIMPLE IM or CPM when registering to IMS.
NOTE 1: Based upon user subscription and depending on network deployment, other Application Servers could be processing the incoming Instant Message before the IP-SM-GW. The behaviour of the IM AS is described in OMA-TS-SIMPLE_IM-V1_0 [12]. The behaviour of the CPM AS is described in OMA-TS-CPM_Conv_Fnct-V1_0 [17].
Figure 6.11: Successful UE termination Instant Message to encapsulated Short Message procedure
1) IM or CPM UE sends an Instant Message to the S-CSCF#1. The UE may request to hide its Public User Identity from the recipient within the Instant Message, as described in OMA‑TS‑SIMPLE_IM‑V1_0 [12] and in OMA-TS-CPM_Conv_Fnct-V1_0 [17].
2) The S-CSCF#1 forwards the Instant Message to the S-CSCF#2.
3) The S-CSCF#2 forwards the Instant Message to the IP-SM-GW based on iFC.
4) Based on user subscription and authorisation for service-level interworking, on operator policy and user preferences, and on UE capability indicated during IMS registration, the IP-SM-GW shall decide whether to perform service-level interworking. If the user is subscribed and authorised for transport-level interworking, and based on UE capability indicated during IMS registration, and on operator policy and user preferences, the message may be delivered as an encapsulated Short Message to the UE over IMS. Otherwise, the Short Message is delivered over CS/PS, as described in clause 6.13. If the sender of the Instant Message requests to hide its Public User Identity from the recipient and operator policy allows for this, the IP‑SM‑GW shall anonymise the identity of the user to the recipient. Otherwise, if operator policy prohibits this, the IP‑SM‑GW shall return an appropriate error to the user.
NOTE 2: If a delivery notification was requested in the message sent by the UE in step 1 as described in IETF IMDN RFC 5438 [13], the procedure for delivery report described in clause 6.12 applies. Otherwise IP-SM-GW will just acknowledge, at the SIP level, the Delivery report received from the SMSIP UE.
5) The IP-SM-GW forwards the encapsulated Short Message to the S-CSCF#2.
6) The S-CSCF#2 forwards the encapsulated Short Message to the SMSIP UE.
7) The SMSIP UE acknowledges the translated encapsulated Short Message.
8) The S-CSCF forwards the acknowledgement of the translated encapsulated Short Message to the IP-SM-GW.
9-11) The IP-SM-GW forwards the acknowledgement of the translated encapsulated Short Message to the originating IM UE or CPM UE.
|
b57c39c719229455cea55c4a75308a42
|
23.204
|
6.12 Delivery report for an Instant Message delivered as encapsulated Short Message
|
This procedure follows the procedure described in clause 6.11, when the original Instant Message included a delivery notification request.
Figure 6.12: Delivery report after a successful Instant Message to encapsulated Short Message procedure
NOTE: An encapsulated Short Message has been sent successfully according to the procedure described in clause 6.11 before the procedure below can be performed.
1-2) The SMSIP UE has received the Short Message as described in clause 6.11 and sends a Delivery report (SMS-DELIVER-REPORT) to the IP-SM-GW via the S-CSCF.
3-4) The IP-SM-GW acknowledges, at the SIP level, the Delivery report to the SMSIP UE via the S-CSCF.
5-7) The IP-SM-GW sends a Delivery Notification to the IM UE or CPM UE.
8-10) The IM UE or CPM UE acknowledges the reception of the Delivery Notification.
|
b57c39c719229455cea55c4a75308a42
|
23.204
|
6.13 Service-level interworking: IM or CPM capable UE sends an Instant Message to an SMS user with Interworking in the terminating side
|
This procedure describes the delivery of an Instant Message to a registered or an un-registered IMS subscriber. For the unregistered case, the S‑CSCF forwards the Instant Message to the IP‑SM‑GW based on the unregistered iFC of the subscriber.
Figure 6.13: Successful IM terminating to SMS procedure with Interworking in the Terminating Side
1) UE submits an Instant Message, destined to another IM user or CPM user in another IMS domain, using an appropriate SIP method. The UE may request to hide its Public User Identity from the recipient within the Instant Message, as described in OMA‑TS‑SIMPLE_IM‑V1_0 [12] and in OMA-TS-CPM_Conv_Fnct-V1_0 [17]. If the P-CSCF (not shown in the figure) has received an indication from the S‑CSCF that MPS for Messaging is enabled for the originating UE in the HSS (see TS 23.228 [9]), the P‑CSCF sets the Resource-Priority information on the Instant Message to a value appropriate for MPS, sets the transport priority of the outgoing Instant Message to a value appropriate for MPS and handles the Instant Message with priority.
2) The S-CSCF resolves the destination domain and routes the message towards the S-CSCF in the terminating network ("Terminating S-CSCF").
3) The terminating S-CSCF forwards the Instant Message to the IM AS ("Terminating IM AS") or to the CPM AS ("Terminating CPM AS") based on stored iFC.
NOTE: Depending on iFC configuration, it is possible that the IM AS or CPM AS is not triggered for the unregistered subscribers.
4) The terminating IM AS or CPM AS invokes terminating IM or CPM services as applicable for the destination IM or CPM user.
5a) The IM AS or CPM AS can forward the Instant Message back to the terminating S-CSCF, e.g. the terminating IM user is offline or the CPM user has no terminating interworking user preferences.
5b) In the case of the CPM AS, if terminating interworking user preferences are set, the Instant Message is routed directly to the IP-SM-GW in which case the procedure continues with step 7.
6) The terminating S-CSCF forwards the Instant Message to the IP-SM-GW, e.g. based on stored iFC.
7) If the user is authorized, the IP-SM-GW performs service-level interworking by converting the Instant Message to Short Message. The IP-SM-GW shall obtain the routeing information for the UE from the HLR/HSS and deliver the message to the UE. If the sender of the Instant Message requests to hide its Public User Identity from the recipient and operator policy allows for this, the IP‑SM‑GW shall anonymise the identity of the user to the recipient. Otherwise, if operator policy prohibits this, the IP‑SM‑GW shall return an appropriate error to the user.
8) The IP-SM-GW obtains the routeing information for the destination UE from the HLR/HSS. The HLR/HSS also returns the indication whether MPS for Messaging is enabled for the UE in the HSS (see TS 23.228 [9]) and if the MPS for Messaging is enabled for the UE, the HLR/HSS sets the transport priority of the message to a value appropriate for MPS and handles the message with priority.
9) The IP-SM-GW sends the Forward Short Message message to the target MSC/SGSN/MME/SMSF. If the Resource-Priority information on the Instant Message is a value appropriate for MPS, the IP-SM-GW sets the transport priority of the outgoing Short Message to a value appropriate for MPS and handles the Short Message with priority.
10) The MSC/SGSN/MME/SMSF sends the Short Message to the UE.
11) The UE acknowledges the receipt of the Short Message.
12) The MSC/SGSN/MME/SMSF sends a Delivery report (SMS-DELIVER-REPORT) to the IP-SM-GW.
13) The IP-SM-GW sends OK response to the terminating S-CSCF.
14) The S-CSCF forwards the OK to the terminating IM AS or CPM AS.
15) The terminating IM AS or CPM AS forwards the OK response back to the terminating S-CSCF.
16) The terminating S-CSCF forwards the OK back towards the originating S-CSCF.
17) The originating S-CSCF forwards the OK to the originating UE.
|
b57c39c719229455cea55c4a75308a42
|
23.204
|
6.14 Service-level interworking: IM or CPM user receives Short Message from an SMS user
|
An IMS registered user with SIMPLE IM or CPM service receives a Short Message formatted via service-level interworking to an Instant Message.
Figure 6.14: Successful IM termination after service-level interworking
1) The UE registers to the S-CSCF according to the IMS registration procedure.
2) The SMS-SC forwards a Short Message to the SMS-GMSC.
3a) The SMS-GMSC interrogates the HLR/HSS to retrieve routeing information. Based on the pre-configured IP-SM-GW address for the user, the HLR/HSS forwards the request to the corresponding IP-SM-GW. The SMS GMSC also interrogates the HLR/HSS to check whether MPS for Messaging is enabled for the UE (see TS 23.228 [9]). If the MPS for Messaging is set (enabled) for the UE (see TS 23.228 [9]), the HLR/HSS sets the transport priority of the message to a value appropriate for MPS and handles the message with priority.
3b) The HLR/HSS returns the IMSI and the address(es) of the current MSC, SGSN, MME and/or SMSF to the IP-SM-GW for delivery of the SM in CS/PS domain. The HLR/HSS also returns the indication whether MPS for Messaging is set (enabled) for the UE (see TS 23.228 [9]), sets the transport priority of the message to a value appropriate for MPS and handles the message with priority.
3c) The IP-SM-GW creates an MT Correlation ID as per TS 23.040 [2], which associates the Routing Info retrieval with the subsequent Forward Short Message messages(s), and stores this along with the IMSI of the receiving subscriber. The IP-SM-GW returns to the SMS-GMSC the address of itself, along with the MT Correlation ID in the IMSI field, as routeing information. The IP SM GW returns the indication whether MPS for Messaging is set (enabled) for the UE in the HLR/HSS (see TS 23.228 [9]). If MPS for Messaging is enabled for the UE, the IP-SM-GW sets the transport priority of the message to a value appropriate for MPS and handles the message with priority.
4) The SMS-GMSC delivers the Short Message to the IP-SM-GW in the same manner that it delivers the Short Message to an MSC, SGSN, MME or SMSF, including the MT Correlation ID received from the IP-SM-GW, in place of the IMSI. If MPS for Messaging is enabled for the UE in the HLR/HSS (see TS 23.228 [9]), the SMS-GMSC sets the transport priority of the message to a value appropriate for MPS and handles the Short Message with priority.
5) The IP-SM-GW checks whether the recipient is authorized for the interworking service.
NOTE: The IP-SM-GW will determine whether the transport-level interworking or the service-level interworking is to be performed according to clause 6.8.3.
6) If the user is authorized for service-level interworking, the IP-SM-GW converts the Short Message to an Instant Message. It sends the Instant Message using the appropriate SIP method towards the S-CSCF. If the MPS for Messaging indication for the UE is activated, the IP-SM-GW applies an MPS appropriate Resource-Priority information to the SIP message, sets the transport priority of the message to a value appropriate for MPS and handles the message with priority.
7) The S-CSCF forwards the Instant Message to the UE.
The mechanism defined in clause 5.3.4.3 of TS 23.401 [25] and clause 4.2.3.3 of TS 23.502 [24] ensures that if the UE needs to be paged, the MME/AMF pages the UE with priority.
8) The UE acknowledges the SIP request to the S-CSCF.
9) The S-CSCF forwards the acknowledgement of the SIP request to the IP-SM-GW.
10) The IP-SM-GW acknowledges the Forward Short Message to the SMS-GMSC.
11) The SMS-GMSC sends a Delivery report (SMS‑DELIVER‑REPORT) to the SMS‑SC.
12) The IP‑SM‑GW may send a Report SM Delivery Status to the HLR/HSS.
13) The SMS-GMSC may send a Report SM Delivery Status to the HSS. The HSS shall ignore the information provided in this report.
|
b57c39c719229455cea55c4a75308a42
|
23.204
|
6.15 Service-level Interworking: CPM capable UE sends a Chat session invitation to an SMS user
| |
b57c39c719229455cea55c4a75308a42
|
23.204
|
6.15.1 IP-SM-GW in the originating network
|
Figure 6.15.1: Chat session invitation to SMS user and Message data exchange (IP-SM-GW in originating network)
1) The UE registers to S-CSCF according to the IMS registration procedure.
2) The UE sends a session invitation request for a chat session to the S-CSCF, using the appropriate SIP method. The UE may request to hide its Public User Identity from the recipient within the session invitation.
3) S-CSCF forwards the session invitation to the IP-SM-GW based on stored iFC.
NOTE 1: Subscribers with no subscription for service level interworking will not be provided with the relevant iFCs.
4) The IP-SM-GW performs service authorization based on the stored subscriber data retrieved from the HLR/HSS at the time of the registration procedure as specified in clause 6.1. The IP-SM-GW shall check whether the originating subscriber is authorised to use the interworking service. If the result of service authorization is negative, the IP-SM-GW shall not forward the message, and shall return the appropriate error information to the UE in a failure report. If the sender of the session invitation asks to hide its Public User Identity from the recipient and operator policy allows for this, the IP-SM-GW shall anonymize the identity of the user in all messages it sends to the recipient. If operator policy prohibits anonymity, the IP-SM-GW shall not perform interworking and shall send back an appropriate response.
NOTE 2: Steps 5 to 7 are only executed if the operator policy is to check back with the SMS user before accepting the invitation on behalf of the SMS user. Otherwise, the process continues with step 8, as if the SMS user has responded with an acceptance of the chat session invitation.
5) Otherwise, the IP-SM-GW correlates an MSISDN to this chat session. Any SMS sent from the SMS user to this MSISDN should be interworked into the chat session with which this MSISDN is correlated. The IP-SM-GW shall use the SC Address in the subscriber data retrieved from the HSS at registration or provisioned by configuration and translates the chat session invitation request to a Short Message (SMS- SUBMIT) carrying an SC Address, then forwards it towards the SMS-SC (SC Address) via the SMS-IWMSC (as described in TS 23.040 [2]). The text in the Short Message is defined by the operator and should convey information to the SMS user that he is invited to send and receive messages in the context of a chat session, and include instructions on how to accept, reject and end the session. If no response is received in time, the IP-SM-GW will consider the session rejected and send an appropriate response to the session invitation.
NOTE 3: The MSISDN used as the sender of the Short Message is either the MSISDN of the CPM user or one that is assigned by the IP-SM-GW, depending on operator configuration.
6) The SMS-IWMSC forwards the Short Message (SMS- SUBMIT) to the SMS-SC and the SMS is delivered to the SMS user using standard SMS procedures (see TS 23.040 [2]).
7) A Short Message is sent by the SMS user via the SMS-GMSC to the IP-SM-GW in accordance to steps 2 to 4 and steps 10 to 13 from clause 6.14.
8) If the answer is positive, the IP-SM-GW acknowledges the session invitation. Otherwise the IP-SM-GW will consider the session rejected and send back an appropriate response.
9) Session invitation acknowledgement is forwarded by S-CSCF to the CPM UE.
NOTE 4: The following steps are executed only if an SMS with a positive answer is received from the SMS user or if the operator policy indicated that the session is accepted without SMS user interaction. If a negative response to the invitation is received or if no response from the SMS user is received within an operator defined time, the IP-SM-GW will send a negative response to the chat invitation.
NOTE 5: Steps 10 to 12 are repeated for each message sent from the CPM user towards the SMS user, and steps 13 to 14 are repeated for each message sent from the SMS user towards the CPM user.
10) The CPM user sends a message within the chat session containing data to the recipient SMS user.
11) The IP-SM-GW transforms the received message into a Short Message and sends a Short Message (SMS- SUBMIT) carrying the SC Address, then forwards it towards the SMS-SC (SC Address) via the SMS-IWMSC (as described in TS 23.040 [2]). According to operator policy, each SMS generated for the SMS user may include text instructions on how to leave the chat session.
12) The SMS-IWMSC forwards the Short Message (SMS- SUBMIT) to the SMS-SC and the SMS is delivered to the SMS user using standard SMS procedures (see TS 23.040 [2]).
13) A Short Message is sent by the SMS user via the SMS-GMSC to the IP-SM-GW in accordance to steps 2 to 13 from clause 6.14.
NOTE 6: Step 5 of the flow in clause 6.14 becomes this: The IP-SM-GW identifies that a session exists between the SMS user and the CPM user.
|
b57c39c719229455cea55c4a75308a42
|
23.204
|
6.15.2 IP-SM-GW in the terminating network
|
The SMS user (SMS UE B) in this flow is a CPM user (CPM user B) whose preferences are set in his home network to receive his incoming chat sessions as Short Messages.
Figure 6.15.2: Chat session invitation to SMS user and message data exchange (IP-SM-GW in terminating network)
1) The originating network for CPM user A sends a session invitation request for a chat session to a CPM user (CPM user B) in another IMS domain, using the appropriate SIP method. The UE may request to hide its Public User Identity from the recipient within the session invitation. The originating S-CSCF (not shown) resolves the destination domain and routes the session invitation towards the S-CSCF in the terminating network ("terminating S-CSCF").
2) The terminating S-CSCF forwards the session invitation to the IP-SM-GW based on stored iFC.
NOTE 1: Subscribers with no subscription for service level interworking will not be provided with the relevant iFCs.
3) Authorization to continue is checked. If the sender of the session invitation asks to hide its Public User Identity from the recipient and operator policy allows for this, the IP SM GW shall anonymize the identity of the user in all messages it sends to the recipient. If operator policy prohibits anonymity, or if the IP-SM-GW cannot identify the sending party and the operator prohibits session invitations from unidentified users, the IP SM GW shall not perform interworking and send back an appropriate response.
NOTE 2: Steps 5 to 7 are only executed if the operator policy is to check back with the SMS user before accepting the invitation on behalf of the SMS user. Otherwise, the process continues with step 8, as if the SMS user has responded with an acceptance of the chat session invitation.
4) The IP-SM-GW performs service-level interworking by converting the chat session invitation request to a Short Message. The IP-SM-GW obtains the routeing information for the destination UE from the HLR/HSS.
5) The IP-SM-GW sends the Forward Short Message message to the target MSC. The IP-SM-GW assigns an MSISDN representing the chat session to ensure that the reply to this SMS is sent back to this particular IP-SM-GW. Any SMS sent from the SMS user to this MSISDN should be interworked into the chat session with which this MSISDN is correlated. The text in the Short Message is defined by the operator and should convey information to the SMS user that he is invited to send and receive messages in the context of a chat session, and include instructions on how to accept, reject and end the session. The identity of the original sender (CPM user or group) is included as part of the operator provided invitation text. If no response is received in time, the IP-SM-GW will consider the session rejected and send an appropriate response to the session invitation.
6) The MSC/SGSN/MME/SMSF sends the Short Message to the SMS user.
7) A Short Message is received via the SMS-GMSC from the SMS user by the IP-SM-GW, in accordance to steps 2 to 4 and steps 10 to 13 of clause 6.14, indicating the response to the chat session invitation. The message is targeted to the MSISDN representing the chat session which was assigned in step 5.
8) If the answer is positive, the IP-SM-GW acknowledges the session invitation. Otherwise the IP-SM-GW will consider the session rejected and send back an appropriate response.
9) The session invitation acknowledgement is forwarded by S-CSCF to the CPM UE.
NOTE 3: The following steps are executed only if an SMS with a positive answer is received from the SMS user or if the operator policy indicated that the session is accepted without SMS user interaction. In case a negative response to the invitation is received or if no response from the SMS user is received within an operator defined time, the IP-SM-GW will send a negative response to the chat invitation.
NOTE 4: Steps 10 to 13 are repeated for each message sent from the CPM user towards the SMS user, and step 14 is repeated for each message sent from the SMS user towards the CPM user.
10) The CPM user sends a message within the chat session containing data to the recipient SMS user.
11) The IP-SM-GW transforms the received message into a Short Message and obtains the routeing information for the destination UE from the HLR/HSS.
12) The IP-SM-GW sends a Short Message (SMS- DELIVER) towards the MSC/SGSN/MME/SMSF, as described in TS 23.040 [2]. The IP-SM-GW inserts the MSISDN representing the chat session as the sender of the message, to ensure that the reply to this SMS is sent back to it.
13) The MSC/SGSN/MME/SMSF forwards the Short Message (SMS- DELIVER) to the SMS user, and the SMS is delivered to the SMS user using standard SMS procedures as described in TS 23.040 [2]).
14) A Short Message is received via the SMS-GMSC from the SMS user by the IP-SM-GW, in accordance to steps 2 to 13 from clause 6.14. The message is targeted to the MSISDN representing the chat session which was assigned in step 5.
NOTE 5: Step 5 of the flow in clause 6.14 becomes this: "The IP-SM-GW identifies that a session exists between the SMS user and the CPM user".
|
b57c39c719229455cea55c4a75308a42
|
23.204
|
6.16 Service-level Interworking: CPM capable UE tearing down a Chat session between a CPM user and an SMS user
| |
b57c39c719229455cea55c4a75308a42
|
23.204
|
6.16.1 IP-SM-GW in the originating network
|
Figure 6.16.1: Chat session teardown request to SMS (IP-SM-GW in originating network)
1) The CPM UE sends a SIP BYE for an ongoing session to the S-CSCF.
2) S-CSCF forwards the session teardown request to the IP-SM-GW. The IP-SM-GW performs service-level interworking by converting the session teardown request to a Short Message (SMS-SUBMIT) carrying the SC Address and including operator provided teardown text. The IP-SM-GW uses the SC Address in the subscriber data retrieved from the HSS at registration or provisioned by configuration.
3) The IP-SM-GW forwards the Short Message towards the SMS-SC (SC Address) via the SMS-IWMSC (as described in TS 23.040 [2]). The text in the Short Message is defined by the operator and should convey information to the SMS user that the chat session is ending.
NOTE 1: The MSISDN used as the sender of the Short Message is either the MSISDN of the CPM user or one that was assigned by the IP-SM-GW at session establishment, depending on operator configuration.
4) The SMS-IWMSC forwards the Short Message (SMS- SUBMIT) to the SMS-SC (see TS 23.040 [2]).
NOTE 2: Steps 3 to 4 are only executed if the operator policy requires that the SMS user be told the session is being torn down. Otherwise, the process continues with step 5.
5) The IP-SM-GW acknowledges the session teardown request and tears down the associated resources.
6) The session teardown acknowledgement is forwarded by the S-CSCF to the CPM UE.
|
b57c39c719229455cea55c4a75308a42
|
23.204
|
6.16.2 IP-SM-GW in the terminating network
|
The SMS user (SMS user B) in this flow is a CPM user (CPM user B) who has set his preferences in his home network to receive his incoming chat sessions as Short Messages.
Figure 6.16.2: Chat session teardown request to SMS (IP-SM-GW in terminating network)
1) The CPM user's originating network sends a session teardown request for an ongoing chat session to the terminating S-CSCF.
2) The terminating S-CSCF forwards the session teardown request to the IP-SM-GW serving the SMS user. The IP-SM-GW performs service-level interworking by converting the session teardown request to a Short Message including operator provided teardown text.
3) The IP-SM-GW obtains the routeing information for the destination UE from the HLR/HSS.
4) The IP-SM-GW sends the Forward Short Message to the target MSC/SGSN/MME/SMSF. The IP-SM-GW inserts the MSISDN it had previously assigned to represent this chat session as the sender of the message.
NOTE: Steps 3 to 5 are only executed if the operator policy requires that the SMS user be told the session is being torn down. Otherwise, the process continues with step 6.
5) The MSC/SGSN/MME/SMSF sends the Short Message to the SMS user.
6) The IP-SM-GW acknowledges the session teardown request and tears down the associated resources.
7) The session teardown acknowledgement is forwarded by S-CSCF towards the CPM user's originating network.
|
b57c39c719229455cea55c4a75308a42
|
23.204
|
6.17 Service-level Interworking: SMS user requesting the IP-SM-GW to tear down the Chat session between a CPM user and an SMS user
| |
b57c39c719229455cea55c4a75308a42
|
23.204
|
6.17.1 IP-SM-GW in the originating network
|
Figure 6.17.1: Chat session teardown request to CPM UE (IP-SM-GW in originating network)
1) A message is received from the SMS user via the SMS-GMSC by the IP-SM-GW, in accordance to steps 2 to 4 and steps 10 to 13 of clause 6.14, with the operator defined Short Message indicating the SMS user wants to leave the chat session.
2) The IP-SM-GW performs service-level interworking by recognizing that the Short Message corresponds to the operator defined teardown text indicating the SMS user wants to leave the chat session, so the IP-SM-GW sends a chat session teardown request.
3) The session teardown request is forwarded by S-CSCF to the CPM UE.
4) The CPM UE acknowledges the session teardown request.
5) The acknowledgement is forwarded by the S-CSCF to the IP-SM-GW.
|
b57c39c719229455cea55c4a75308a42
|
23.204
|
6.17.2 IP-SM-GW in the terminating network
|
The SMS user in this flow is a CPM user who has set his preferences in his home network to receive his incoming chat sessions as Short Messages.
Figure 6.17.2: Chat session teardown request to CPM UE (IP-SM-GW in terminating network)
1) A message is received from the SMS user via the SMS-GMSC by the IP-SM-GW, in accordance to steps 2 to 4 and steps 10 to 13 of clause 6.14, with the operator provided teardown text indicating the SMS user wants to leave the chat session.
2) The IP-SM-GW performs service-level interworking by recognizing that the Short Message corresponds to the operator provided teardown text indicating the SMS user wants to leave the chat session, so the IP-SM-GW sends a chat session teardown request.
3) The session teardown request is forwarded by the S-CSCF towards the CPM user's originating network.
4) The CPM user's originating network acknowledges the session teardown request and tears down the associated resources.
5) The acknowledgement is forwarded by the S-CSCF to the IP-SM-GW.
|
b57c39c719229455cea55c4a75308a42
|
23.204
|
6.18 Service-level interworking: Status Report procedure for chat session message to Short Message interworking
|
Figure 6.18: Status report procedure for chat session message to Short Message interworking 1) A chat session message from the UE is successfully delivered to the SMS user after service-level interworking according to clause 6.15. The chat session message requested a success or failure delivery report. NOTE 1: A Request for success or failure delivery report can be requested in a chat session message sent by the UE as described in IETF RFC 4975 [19]. 2) The SMS-SC sends a Status report to the SMS-GMSC. NOTE 2: The Status report, from the SMS-GMSC's point of view, will be treated as any SM termination. NOTE 3: The Status report is an optional message. 3a) The SMS GMSC interrogates the HLR/HSS to retrieve routeing information. Based on the pre-configured IP-SM-GW address for the user, the HLR/HSS forwards the request to the corresponding IP-SM-GW. 3b) The HLR/HSS returns the IMSI and the address(es) of the current MSC, SGSN, MME and/or SMSF to the IP-SM-GW for delivery of the Short Message in CS/PS domain. 3c) The IP-SM-GW creates a MT Correlation ID as per TS 23.040 [2], which associates the Routing Info retrieval with the subsequent Forward Short Message messages(s), and stores this along with the IMSI of the receiving subscriber. The IP-SM-GW returns to the SMS-GMSC the address of itself, along with the MT Correlation ID in the IMSI field, as routeing information. Alternatively, the IP-SM-GW may return the address(es) of the current MSC, SGSN, MME and/or SMSF, in which case, the subsequent procedure to forward the message is the same as defined in TS 23.040 [2]. 4) The SMS-GMSC sends the status report in the Forward Short Message to the IP-SM-GW. 5) The IP-SM-GW translates and maps the Status report in the Forward Short Message into a report request as described in MSRP IETF RFC 4975 [19]. 6) The IP-SM-GW sends a Delivery report (SMS-DELIVER-REPORT) to the SMS-GMSC. 7) The SMS-GMSC sends an acknowledgement back to the SMS-SC. 8-9) The IP-SM-GW sends a success of failure report based on the value in the status report. NOTE 4: Step 6 and 8 can happen independently of each other. Annex A (informative): Service-level interworking: IM or CPM user sends an Instant Message to a group list including SMS users Figure A.1: IM user sends an Instant Message to a group list via service-level interworking 1) The UE registers to S-CSCF according the IMS registration procedure. 2) UE generates Instant Message which includes group information, e.g. Group identifier in the Request-URI and/or recipient list in the body of the Instant Message. UE submits the Instant Message to the S-CSCF using an appropriate SIP method. 3) Based on the stored iFC, S-CSCF forwards the Instant Message to an AS in charge of the group delivery, e.g., the controlling function server defined in OMA-TS-SIMPLE_IM-V1_0 [12] or the controlling function server defined in OMA-TS-CPM_Conv_Fnct-V1_0 [17]. 4) The group delivery AS replicates per Instant Message for per recipient according to the group information it obtains acting as a B2BUA. See detail in OMA-TS-SIMPLE_IM-V1_0 [12] or in OMA-TS-CPM_Conv_Fnct-V1_0 [17]. 5) The group delivery AS sends the generated multiple Instant Messages to S-CSCF (e.g., the Instant Messages can be delivered as what the list server does defined in the TS 24.247 [14]). 6) The S-CSCF forwards the Instant Messages to the IP-SM-GW based on the stored iFC. 7) The IP-SM-GW shall decide whether to perform service-level interworking depending on SIP request header (e.g. Request-URI), operator policy, when the Instant Message is not routeable in the IMS. If IP-SM-GW decided to perform service-level interworking, the IP-SM-GW performs service authorization based on the stored subscriber data retrieved from the HLR/HSS at the time of the third party registration procedure as described in the clause 6.1. The IP-SM-GW shall check whether the originating subscriber is authorised to use the interworking service .If the result of service authorization is negative, the IP-SM-GW shall not forward the message, and shall return the appropriate error information to the UE in a failure report. Otherwise, the IP-SM-GW shall translate the IMS message to a Short Message (SMS- SUBMIT) and forwards it towards the SMS-SC (SC Address) via the SMS-IWMSC (as described in TS 23.040 [2]). 8) If service authorization is successful, the IP-SM-GW acknowledges the Instant Messages. 9-11) Instant Message acknowledgement is forwarded by S-CSCF to UE. 12) The SMS-IWMSC forwards the Short Messages (SMS- SUBMIT) to the SMS-SC (see TS 23.040 [2]). 13) The SMS-SC sends multiple Submit reports (SMS-SUBMIT REPORT) to SMS-IWMSC (see TS 23.040 [2]). 14) SMS-IWMSC sends the Submit reports to IP-SM-GW (see TS 23.040 [2]). 15) IP-SM-GW translates the received Submit reports to appropriate IMS delivery notifications defined in RFC 5438 [13], and forwards the IMS delivery notifications to the S-CSCF. 16) The S-CSCF forwards the IMS delivery notifications to the group delivery AS. 17) The group delivery AS aggregates the delivery notifications of the same type from different recipients into a single delivery notification. 18) The group delivery AS sends the delivery notification to the S‑CSCF. 19) The S-CSCF forwards the delivery notification to the UE. 20-23) Acknowledgement of the delivery notification is forwarded by S-CSCF to IP-SM-GW. Annex B (informative): Group chat sessions B.1 Service-level interworking: IM or CPM user initiates a group chat and sends an Instant Message to a group list including SMS users The flow in this clause is the same as that described in clause 6.15.1 with the difference that it is required that the IP-SM-GW assign an MSISDN for this group chat session so that it is clear for the SMS user that any message sent to the assigned MSISDN will be delivered to the group chat session participants, not just to the CPM UE that invited the SMS user. In this flow, the IP-SM-GW is in the PLMN of the CPM UE, but it could also be in the PLMN of the SMS user if that user was also a CPM user and had terminating user preferences to deliver the session invitation via SMS. Figure B.1: CPM user initiates a group chat and messages are exchanged within the group chat via service-level interworking 1) The UE registers to S-CSCF according the IMS registration procedure. 2) The UE generates a chat session invitation which includes group information, e.g. Group identifier in the Request-URI and/or recipient list in the body of the chat session invitation. UE submits the Instant Message to the S-CSCF using an appropriate SIP method. 3) Based on the stored iFC, S-CSCF forwards the session invitation to an AS in charge of handling group chat requests, e.g., the controlling function server defined in OMA-TS-SIMPLE_IM-V1_0 [12] or the controlling function server defined in OMA-TS-CPM_Conv_Fnct-V1_0 [17]. 4) The group chat AS replicates a session invitation per recipient according to the group information it obtains acting as a B2BUA. See details in OMA-TS-SIMPLE_IM-V1_0 [12] or in OMA-TS-CPM_Conv_Fnct-V1_0 [17]. 5) The group chat AS sends the generated multiple session invitations to the S-CSCF. 6) The group chat AS forwards one of the chat session invitations to the IP-SM-GW according to normal routing procedures (e.g., via S-CSCF). NOTE 1: Nodes specific to the CPM functions such as ISF are either collocated with the IP-SM-GW or else are not shown. 7) The IP-SM-GW translates the chat session invitation request to a Short Message (SMS- SUBMIT) and forwards it towards the group chat SMS-SC (SC Address) via the SMS-IWMSC (as described in TS 23.040 [2]). The IP-SM-GW assigns an MSISDN representing the group chat session to ensure that the reply to this SMS is sent back to this particular IP-SM-GW. Any SMS sent from the SMS user to this MSISDN will be interworked into the group chat session with which this MSISDN is correlated. The text in the Short Message is defined by the operator and conveys information to the SMS user that he is invited to send and receive messages in the context of a group chat session, and includes instructions on how to accept, reject and end the session. The identity of the original sender (CPM user or group) is included as part of the operator provided invitation text. 8) The SMS-IWMSC forwards the Short Messages (SMS- SUBMIT) to the group chat SMS-SC and the SMS is delivered to the SMS user using standard SMS procedures (see TS 23.040 [2]). 9) A Short Message is received from the SMS user via the SMS-GMSC by the IP-SM-GW, in accordance to steps 2 to 4 and steps 10 to 13 from clause 6.14, indicating the response to the group chat session invitation. The message is targeted to the MSISDN representing the group chat session which was assigned in step 7. 10) If the answer is positive or if operator policy is to accept the session invitation on behalf of the SMS user, the IP-SM-GW acknowledges the session invitation. Otherwise the IP-SM-GW will consider the session rejected and send back an appropriate response. 11) The session invitation acknowledgement is forwarded by S-CSCF to the group chat AS. 12-13) The group chat AS responds back to the group chat session initiator once the first user joins the group chat session. NOTE 2: The following steps are executed only if an SMS with a positive answer is received from the SMS user or if the operator policy indicated that the session is accepted without SMS user interaction. In case a negative response to the invitation is received or if no response from the SMS user is received within an operator defined time, the IP-SM-GW shall send a negative response to the chat invitation. 14-17) The IP-SM-GW subscribes to the participant information changes. NOTE 3: Steps 18 to 21 are repeated for each message sent from any group chat session participant towards the SMS user, and steps 22 to 24 are repeated for each message sent from the SMS user towards the group chat session participants. 18) The CPM UE (or any group chat session participant) sends a message containing data to the group chat AS. 19) For the group chat session participant who is an SMS user, the message is routed towards the IP-SM-GW. 20) The IP-SM-GW identifies that a session exists between the SMS user and group chat AS and transforms the received message into a Short Message and sends a Short Message (SMS- SUBMIT) carrying the SC Address, then forwards it towards the group chat SMS-SC (SC Address) via the SMS-IWMSC (as described in TS 23.040 [2]). The IP-SM-GW inserts the address representing the group chat session as the sender of the message to ensure that the reply to this SMS is sent back to this particular IP-SM-GW. 21) The SMS-IWMSC forwards the Short Message (SMS- SUBMIT) to the group chat SMS-SC and the SMS is delivered to the SMS user using standard SMS procedures (see TS 23.040 [2]). 22) A Short Message is received from the SMS user via the SMS-GMSC by the IP-SM-GW, in accordance to steps 2 to 13 from clause 6.14. The message is targeted to the MSISDN representing the group chat session which was assigned in step 7. NOTE 4: Step 5 of the flow in clause 6.14 becomes this: The IP-SM-GW identifies that a session exists between the SMS user and the CPM user. Steps 6 and 7 of the flow in clause 6.14 are replaced by steps 23 and 24 in this flow. 23) The IP-SM-GW identifies that a session exists between the SMS user and the group chat AS and transforms the received message into message data and sends it within the session towards the group chat AS. 24) The group chat AS forwards the message to all group chat participants. B.2 Service-level interworking: CPM user extends a one-to-one chat session into a group chat session This flow is the same as that described in clause 6.15.1 with the difference that it is required that the IP-SM-GW assign an MSISDN when this group chat session starts if one was not assigned before, so that it is clear for the SMS user that any message sent to the assigned MSISDN will be delivered to the group chat session participants, not just to the CPM UE that invited the SMS user. In this flow, the IP-SM-GW is in the PLMN of the CPM UE, but it could also be in the PLMN of the SMS user if that user was also a CPM user and had terminating user preferences to deliver the session invitation via SMS. Figure B.2: CPM user modifies a one-to-one chat session into a group chat session 1) A one-to-one chat session is established between the CPM user and the SMS user. 2) The UE generates a chat session invitation which includes a recipient list in the body of the chat session invitation. The original SMS user who is part of the one-to-one chat session is included in that list An indication is added for the original SMS user in the list that the existing one-to-one session is to be replaced by the new session. The UE submits the chat session invitation to the S-CSCF. 3) Based on the stored iFC, S-CSCF forwards the session invitation to an AS in charge of handling group chat requests, e.g., the controlling function server defined in OMA-TS-SIMPLE_IM-V1_0 [12] or the controlling function server defined in OMA-TS-CPM_Conv_Fnct-V1_0 [17]. 4) The group chat AS replicates a session invitation per recipient according to the group information it obtains acting as a B2BUA. See details in OMA-TS-SIMPLE_IM-V1_0 [12] or in OMA-TS-CPM_Conv_Fnct-V1_0 [17]. 5) The group chat AS sends the generated multiple session invitations to the S-CSCF. 6) The group chat AS sends one of the chat session invitations to the IP-SM-GW according to normal routing procedures (e.g., via S-CSCF). The chat session invitation will indicate that the existing session is to be replaced with a new session. 7) The IP-SM-GW translates the chat session invitation request to a Short Message (SMS- SUBMIT) and forwards it towards the group chat SMS-SC (SC Address) via the SMS-IWMSC (as described in TS 23.040 [2]). The IP-SM-GW assigns an MSISDN representing the group chat session, if one was not assigned for the one-to-one chat session, to ensure that the reply to this SMS is sent back to this particular IP-SM-GW. Any SMS sent from the SMS user to this MSISDN will be interworked into the group chat session with which this MSISDN is correlated. The text in the Short Message is defined by the operator and conveys information to the SMS user that the one-to-one session has been transformed into a group session and that he is invited to send and receive messages in the context of a group chat session, and includes instructions on how to accept, reject and end the session. The identity of the original sender (CPM user or group) is included as part of the operator provided invitation text. 8) The SMS-IWMSC forwards the Short Messages (SMS- SUBMIT) to the group chat SMS-SC and the SMS is delivered to the SMS user using standard SMS procedures (see TS 23.040 [2]). 9) A Short Message is received from the SMS user via the SMS-GMSC by the IP-SM-GW, in accordance to steps 2 to 4 and steps 10 to 13 from clause 6.14, indicating the response to the group chat session invitation. The message is targeted to the MSISDN representing the group chat session which was assigned in step 7. 10) If the answer is positive or if operator policy is to accept the session invitation on behalf of the SMS user, the IP-SM-GW acknowledges the session invitation. Otherwise the IP-SM-GW will consider the session rejected and sends back an appropriate response. 11) The session invitation acknowledgement is forwarded by S-CSCF to the group chat AS. 12-13) The group chat AS responds back to the group chat session initiator once the first user joins the group chat session. B.3 Service-level interworking: IP-SM-GW informs SMS users about group chat participant changes In this flow, the IP-SM-GW is in the PLMN of the CPM UE, but it could also be in the PLMN of the SMS user if that user was also a CPM user and had terminating user preferences to deliver the session invitation via SMS. Figure B.3: Sending participant information changes to an SMS user in a group chat session 1) A group chat session including SMS user(s) set up by an IM or CPM user as described in clause B.1 steps 1-17. 2) The group chat AS detects change in participants of the group chat session (e.g. participant added or left the group chat session, that event is not shown in the flow). 3-4) As the IP-SM-GW has subscribed to participant information changes, the group chat AS notifies the IP-SM-GW about the participant change through the S-CSCF using an appropriate SIP method. 5-6) The IP-SM-GW acknowledges the notification. 7) According to operator policy, the IP-SM-GW translates the participant change notification to a Short Message (SMS- SUBMIT) and forwards it towards the group chat SMS-SC (SC Address) via the SMS-IWMSC (as described in TS 23.040 [2]). The text in the Short Message is defined by the operator and conveys appropriate information to the SMS user. 8) The SMS-IWMSC forwards the Short Messages (SMS- SUBMIT) to the group chat SMS-SC and the SMS is delivered to the SMS user using standard SMS procedures (see TS 23.040 [2]). Annex C (informative): Change History Change history Date Meeting TDoc CR Rev Cat Subject/Comment New version 2007-12 SP-38 SP-070898 0036 1 B New Annex: IM user sends an Instant Message to a group list including SMS users 8.0.0 2007-12 SP-38 SP-070898 0037 3 B IM capable UE sends an Instant Message to an SMS user 8.0.0 2007-12 SP-38 SP-070898 0038 4 B Relationship between SMSIP and Service level interworking 8.0.0 2007-12 SP-38 SP-070898 0039 4 B Definition, Symbol, Abbreviation Clauses 8.0.0 2007-12 SP-38 SP-070898 0041 5 B Status Report for IM to SMS IW 8.0.0 2007-12 SP-38 SP-070898 0043 2 B Updating the scope for TS 23.204 8.0.0 2007-12 SP-38 SP-070898 0044 2 B Concatenated Short Messages delivered as an large Instant Message 8.0.0 2007-12 SP-38 SP-070898 0045 2 B IP-SM-GW Additional Features 8.0.0 2008-03 SP-39 SP-080109 0047 2 C SC address retrieval for IM MO 8.1.0 2008-03 SP-39 SP-080108 0050 2 A Correction to Reference 8.1.0 2008-03 SP-39 SP-080109 0053 - D Implementing the documentation guidance from SA#38 8.1.0 2008-03 SP-39 SP-080109 0056 - F IM to SM interworking procedure corrections 8.1.0 2008-03 SP-39 SP-080109 0058 2 B Procedures when disposition notification is requested by IMS UE 8.1.0 2008-03 SP-39 SP-080109 0059 3 C Adding architecture requirement for service level interworking 8.1.0 2008-03 SP-39 SP-080109 0060 2 C Implementing the functionality for SC address retrieval 8.1.0 2008-03 SP-39 SP-080109 0061 1 F General cleanup of the specification 8.1.0 2008-03 SP-39 SP-080109 0062 3 C General cleanup of new clauses agreed in SA2#62 8.1.0 2008-03 SP-39 SP-080109 0063 3 C Correctly adding SMS to IM interworking procedures and clean up 8.1.0 2008-06 SP-40 SP-080368 0064 1 C Adding privacy functionality to the service level interworking 8.2.0 2008-06 SP-40 SP-080368 0065 2 C IM delivery to unregistered IMS subscriber 8.2.0 2008-06 SP-40 SP-080368 0066 1 F General Cleanup (cont'd) 8.2.0 2008-06 SP-40 SP-080368 0067 4 F Deferred message when SMS is transport or service level interworked 8.2.0 2008-06 SP-40 SP-080368 0068 1 F Corrections for IM termination call flow 8.2.0 2008-06 SP-40 SP-080368 0070 1 F Architectural requirement corrections 8.2.0 2008-06 SP-40 SP-080368 0072 - F SMS delivery correction 8.2.0 2008-09 SP-41 SP-080585 0074 3 B Update of TS 23.204 for SMS over IP procedures for E-UTRAN 8.3.0 2009-03 SP-43 SP-090111 0077 4 A Correction of procedure for SM termination through the home network 8.4.0 2009-03 SP-43 SP-090106 0078 1 F Reduction of unnecessary signalling 8.4.0 2009-12 SP-46 - - - - Update to Rel-9 version (MCC) 9.0.0 2010-03 SP-47 SP-100157 0085 - B IP-SM-GW enhancements for interworking with OMA CPM (Rel-9 CR0087 not included as instructed on the Rel-9 CR) 10.0.0 2010-06 SP-48 SP-100336 0088 - F Scope and References Corrections of CPM-SMS IW 10.1.0 2010-06 SP-48 SP-100336 0089 - F Clarify routing of messages for processing in the IP-SM-GW 10.1.0 2010-09 SP-49 SP-100557 0090 1 F NOTE corrections 10.2.0 2011-06 SP-52 SP-110343 0091 - F IP-SM-GW address handling clarification 11.0.0 2011-09 SP-53 SP-110469 0092 - F MCC Implementation correction to CR0091 11.1.0 2012-06 SP-56 SP-120240 0093 5 B Server to MSISDN-less IMS UE direction in IMS 11.2.0 2012-12 SP-58 SP-120717 0095 2 F Nokia Siemens Networks, LG Electronics 11.3.0 2012-12 SP-58 SP-120727 0096 2 B SMS for IMS UE to IMS UE without MSISDN 12.0.0 2013-03 SP-59 SP-130091 0097 1 F Clarification on MSISDN-less SMS operation 12.1.0 2013-06 SP-60 SP-130322 0101 2 A Adding the interface between IP-SM-GW and MME 12.2.0 2013-09 SP-61 SP-130370 0103 1 A IP-SM-GW with Diameter interfaces for SMS in MME 12.3.0 2013-12 SP-62 SP-130535 0104 - B IP-SM-GW and Gdd interface 12.4.0 2015-12 - - - - - Update to Rel-13 version (MCC) 13.0.0 2016-06 SP-72 SP-160284 0108 - A SMS w/o MSISDN with removal of Sh interaction 13.1.0 2017-03 - - - - - Update to Rel-14 version (MCC) 14.0.0 2018-03 SP-79 SP-180094 0109 1 F MT SMS domain selection by IP-SM-GW 15.0.0 2018-03 SP-79 SP-180094 0110 2 F Addition of description on SMSF address 15.0.0 2019-12 SP-86 SP-191089 0119 1 F Alignment to 23.040 on UE reachability notification from IP-SM-GW 16.0.0 2022-03 SP-95E - - - - Update to Rel-17 version (MCC) 17.0.0 2024-03 - - - - - Update to Rel-18 version (MCC) 18.0.0 2024-09 SP-105 SP-241266 0120 3 B Support of MPS priority for SMS over IP 19.0.0 2024-12 SP-106 SP-241490 0121 2 F MPS transport priority clarification for SMS over IP 19.1.0
|
654592d6e30fb2596cb6e134b557471f
|
23.222
|
1 Scope
|
The present document specifies the architecture, procedures and information flows necessary for the CAPIF. The aspects of this specification include identifying architecture requirements for the CAPIF (e.g. registration, discovery, identity management) that are applicable to any service APIs when used by northbound entities, as well as any interactions between the CAPIF and the service APIs themselves. The common API framework applies to both EPS and 5GS, can be hosted within a PLMN or SNPN, and is independent of the underlying 3GPP access (e.g. E-UTRA, NR).
|
654592d6e30fb2596cb6e134b557471f
|
23.222
|
2 References
|
The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
- References are either specific (identified by date of publication, edition number, version number, etc.) or non‑specific.
- For a specific reference, subsequent revisions do not apply.
- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.
[1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
[2] 3GPP TS 23.682: "Architecture enhancements to facilitate communications
with packet data networks and applications".
[3] 3GPP TS 23.501: "System Architecture for the 5G System; Stage 2".
[4] 3GPP TS 23.502: "Procedures for the 5G System; Stage 2".
[5] 3GPP TR 26.981: "MBMS Extensions for Provisioning and Content Ingestion".
[6] 3GPP TS 32.240: "Telecommunication management; Charging management; Charging architecture and principles".
[7] ETSI GS MEC 011 (V1.1.1): "Mobile Edge Computing (MEC); Mobile Edge Platform Application Enablement".
[8] ETSI GS MEC 009 (V1.1.1): "Mobile Edge Computing (MEC); General Principles for Mobile Edge Service APIs".
[9] OMA-ER_Autho4API-V1_0-20141209-A: "Authorization Framework for Network APIs".
[10] OMA-TS-REST_NetAPI_Common-V1_0-20180116-A: "Common definitions for RESTful Network APIs".
[11] OMA-TS-NGSI_Registration_and_Discovery-V1_0-20120529-A: "NGSI Registration and Discovery".
[12] 3GPP TS 33.122: "Security Aspects of Common API Framework for 3GPP Northbound APIs".
[13] 3GPP TS 23.435: "Procedures for Network Slice Capability Exposure for Application Layer Enablement Service".
[14] IETF RFC 6749 (October 2012): "The OAuth 2.0 Authorization Framework".
[15] 3GPP TS 23.434: "Service Enabler Architecture Layer for Verticals (SEAL); Functional architecture and information flows".
[16] 3GPP TS 33.501: "Security architecture and procedures for 5G System".
[17] 3GPP TS 28.541: "Management and orchestration; 5G Network Resource Model (NRM); Stage 2 and stage 3".
[18] 3GPP TS 28.532: "Management and orchestration; Generic management services".
[19] 3GPP TS 28.538: "Management and orchestration; Edge Computing Management".
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.