n IP-CAN session is established after a primary Packet Data Protocol (PDP) context
initiated by the UE is activated.
When a subscriber goes online, the subscribers UE initiates the IP-CAN session establishment flow. Figure 1 shows the message flow of UE-initiated IP-CAN session establishment. Figure 1 Message flow of UE-initiated IP-CAN session establishment http://localhost:7904/pages/CEC1230A/01/CEC1230A/01/resources/upcc/maintenance/ signaling/figure/fig20_d621.png http://localhost:7904/pages/CEC1230A/01/CEC1230A/01/resources/public_sys- resources/icon-note.gif NOTE: The message flow of UE-initiated IP-CAN session establishment in quasi-associated mode is the same as the message flow in direction connection mode. In quasi- associated mode, the policy and charging rules function (PCRF) interworks with the policy and charging enforcement function (PCEF) though the Diameter routing agent (DRA). In direct connection mode, the PCRF connects to the PCEF directly. 1. The UE attaches to the PS network. 2. The UE sends an Activate PDP Context Request message to the serving GPRS support node (SGSN). The Activate PDP Context Request message contains information elements (IEs) such as network service access point identifier (NSAPI), access point name (APN), PDP type, PDP Address, Requested QoS, traffic flow template (TFT) (optional), and protocol configuration option (PCO) (optional). 3. The SGSN validates the IEs such as PDP type (optional), PDP address (optional), and APN (optional) based on the subscription data. If the IEs are valid, the SGSN selects a PCEF based on the APN and sends a Create PDP Context Request message to the selected PCEF. The following IEs may be included in the Create PDP Context Request message: 1. PDP type 2. PDP address 3. APN 4. Requested QoS 5. tunnel endpoint identifier (TEID) 6. NSAPI 7. Mobile Station International ISDN Number (MSISDN) 8. Selection mode 9. Charging characteristics 10. Trace reference 11. Trace type 12. Trigger ID 13. operation and maintenance center (OMC) flag 14. PCO 15. Network indicator 16. Maximum APN 17. international mobile station equipment identity and software version (IMEISV) 18. cell global identity (CGI)/service area identity (SAI) 19. RAT type 20. S-CDR CAMEL information 21. CGI/SAI/routing area identity (RAI) change report indicator 22. NRSN 4. The PCEF validates the Create PDP Context Request message, determines the default charging mode based on charging characteristics, authentication information, or local data configuration, and performs the following operations based on its capability and load: 0. Selects a QoS rule. 1. Generates a charging ID. 2. Sends an authentication request to the authentication, authorization, and accounting (Authentication, Authorization and Accounting (AAA)) server. 3. Assigns an IP address for the UE. If the operations are successful, the PCEF creates a new entry in its PDP context table and IP-CAN session table. If the policy and charging control (PCC) function is enabled for the designated APN, the PCEF selects a PCRF and associates the PCRF with the current IP-CAN session. Then, the PCEF sends a Credit-Control-Request (CCR) message to the selected PCRF, indicating the establishment of the IP-CAN session. The following attribute value pairs (AVPs) may be included in the CCR message: 4. Session-Id 5. CC-Request-Type (INITIAL_REQUEST) 6. CC-Request-Number 7. Bearer-Identifier 8. Bearer-Operation (ESTABLISHMENT) 9. Subscription-Id (international mobile subscriber identity (IMSI)/MSISDN) 10. Framed-IP-Address (UE IP address) 11. IP-CAN-Type (3GPP (0)) 12. 3GPP-RAT-Type 13. User-Equipment-Info (IMEISV) 14. QoS-Information 15. 3GPP-SGSN-MCC-MNC 16. 3GPP-SGSN-Address 17. RAI 18. 3GPP-User-Location-Info 19. Called-Station-ID (APN) 20. Online/Offline (default charging mode) 21. TFT-Packet-Filter-Information (mapped TFT on the Gn interface) 22. Access-Network-Charging-Address (PCEF GPRS Tunneling Protocol- Control plane (GTP-C) address) 23. Access-Network-Charging-Identifier-Gx (GCID) Figure 2 shows a captured CCR message. Figure 2 Captured CCR message http://localhost:7904/pages/CEC1230A/01/CEC1230A/01/resources/upcc/maintena nce/signaling/figure/fig_cn_90_35_0000036_01.png 5. The PCRF makes a multi-dimensional authorization decision for the IP-CAN session based on available information such as subscription information, time, location, service, dynamic AF session. Then, the PCRF sends a Credit-Control- Answer-I (CCA-I) message containing the authorization result to the PCEF. The following AVPs may be included in the CCA-I message: 0. Session-Id (the same as that contained in the CCR-Initial message) 1. Result-Code/Experimental-Result 2. CC-Request-Type/CC-Request-Number (the same as that contained in the CCR-Initial message) 3. Event-Trigger 4. Charging-Rule-Install (At least one Charging-Rule-Install AVP is contained.) 5. Charging-Information (default online charging system (OCS)/offline charging system (OFCS)) 6. Online/Offline (It indicates the default charging mode. If the Online or Offline AVP is contained in the CCA-Initial message sent by the PCRF, the IP-CAN session is charged based on the Online or Offline AVP. If the Online or Offline AVP is not contained in the CCA-Initial message, the charging mode is determined by the configuration on the PCEF.) 7. QoS-Information Figure 3 shows a captured CCA message. Figure 3 Captured CCA message http://localhost:7904/pages/CEC1230A/01/CEC1230A/01/resources/upcc/maintena nce/signaling/figure/fig_cn_90_35_0000037_01.png 6. The PCEF determines whether the authorization is successful based on the value of the Result-Code or Experimental-Result AVP contained in the CCA-Initial message. If the authorization is successful, the PCEF saves the default OCS/OFCS, charging mode, and authorized QoS, generates related policy and control database (PCDB) and charging control database (CCDB), continues all required steps for primary PDP context activation, and sends a Create PDP Context Response message to the SGSN.