1. Attach Request [TS 23.401] The UE initiates the Attach procedure by the transmission, to the eNodeB, of an Attach Request (IMSI or old GUTI, last visited TAI (if available), UE Core Network Capability, UE Specific DRX parameters, PDN Type, Protocol Configuration Options, Ciphered Options Transfer Flag, Attach Type, KSIASME, NAS sequence number, NAS-MAC, additional GUTI, P-TMSI signature) message together with RRC parameters indicating the Selected Network and the old GUMMEI. If the UE has valid security parameters, the Attach Request message shall be integrity protected by the NAS-MAC in order to allow validation of the UE by the MME. KSIASME, NAS sequence number and NAS-MAC are included if the UE has valid EPS security parameters. NAS sequence number indicates the sequential number of the NAS message. If the UE does not have a valid EPS security association, then the Attach Request message is not integrity protected. In this case the security association is established in step 5a. The UE network capabilities indicate also the supported NAS and AS security algorithms. PDN type indicates the requested IP version (IPv4, IPv4/IPv6, IPv6). Protocol Configuration Options (PCO) are used to transfer parameters between the UE and the PDN GW, and are sent transparently through the MME and the Serving GW. The Protocol Configuration Options may include the Address Allocation Preference indicating that the UE prefers to obtain an IPv4 address only after the default bearer activation by means of DHCPv4. If the UE intends to send PCO which require ciphering (e.g., PAP/CHAP usernames and passwords) or send an APN, or both, the UE shall set the Ciphered Options Transfer Flag and send PCO or APN or both only after authentication and NAS security setup have been completed (see below). If the UE has UTRAN or GERAN capabilities, it should send the NRSU in the PCO to indicate the support of the network requested bearer control in UTRAN/GERAN. Attach Type indicates “Handover” when the UE has already an activated PDN GW/HA due to mobility with non-3GPP accesses. 2. Attach Request [TS 23.401] The eNodeB derives the MME from the RRC parameters carrying the old GUMMEI and the indicated Selected Network. If that MME is not associated with the eNodeB or the old GUMMEI is not available, the eNodeB selects an MME as described in clause 220.127.116.11 on “MME selection function”. The eNodeB forwards the Attach Request message to the new MME contained in a S1-MME control message (Initial UE message) together with the Selected Network and TAI+ECGI of the cell from where it received the message to the new MME. 3. Create Session Request [TS 23.401] If a subscribed PDN address is allocated for the UE for this APN, the PDN subscription context contains the UE’s IPv4 address and/or the IPv6 prefix and optionally the PDN GW identity. In case the PDN subscription context contains a subscribed IPv4 address and/or IPv6 prefix, the MME indicates it in the PDN address. For Attach Type indicating “Initial Attach”, if the UE does not provide an APN, the MME shall use the PDN GW corresponding to the default APN for default bearer activation. If the UE provides an APN, this APN shall be employed for default bearer activation. For Attach type indicating “Handover”, if the UE provides an APN, the MME shall use the PDN GW corresponding to the provided APN for default bearer activation, If the UE does not provide an APN, and the subscription context from HSS contains a PDN GW identity corresponding to the default APN, the MME shall use the PDN GW corresponding to the default APN for default bearer activation. The case where the Attach type indicates “Handover” and the UE does not provide an APN, and the subscription context from HSS does not contain a PDN GW identity corresponding to the default APN constitutes an error case. If the attach type indicates “Initial Attach” and the selected PDN subscription context contains no PDN GW identity the new MME selects a PDN GW as described in clause 18.104.22.168 on PDN GW selection function (3GPP accesses). If the PDN subscription context contains a dynamically allocated PDN GW identity and the Attach Type does not indicate “Handover” the MME may select a new PDN GW as described in clause PDN GW selection function, e.g. to allocate a PDN GW that allows for more efficient routing. The new MME selects a Serving GW as described in clause 22.214.171.124 on Serving GW selection function and allocates an EPS Bearer Identity for the Default Bearer associated with the UE. Then it sends a Create Session Request (IMSI, MSISDN, MME TEID for control plane, PDN GW address, PDN Address, APN, RAT type, Default EPS Bearer QoS, PDN Type, APN-AMBR, EPS Bearer Identity, Protocol Configuration Options, Handover Indication, ME Identity, User Location Information (ECGI), MS Info Change Reporting support indication, Selection Mode, Charging Characteristics, Trace Reference, Trace Type, Trigger Id, OMC Identity, Maximum APN Restriction, Dual Address Bearer Flag, the Protocol Type over S5/S8) message to the selected Serving GW. The RAT type is provided in this message for the later PCC decision. The subscribed APN AMBR for the APN is also provided in this message. The MSISDN is included if provided in the subscription data from the HSS. Handover Indication is included if the Attach type indicates handover. Selection Mode indicates whether a subscribed APN was selected, or a non-subscribed APN sent by the UE was selected.. Charging Characteristics indicates which kind of charging the bearer context is liable for. The MME may change the requested PDN type according to the subscription data for this APN as described in clause 126.96.36.199. The MME shall set the Dual Address Bearer Flag when the PDN type is set to IPv4v6 and all SGSNs which the UE may be handed over to are Release 8 or above supporting dual addressing, which is determined based on node pre-configuration by the operator. The Protocol Type over S5/S8 is provided to Serving GW which protocol should be used over S5/S8 interface. The charging characteristics for the PS subscription and individually subscribed APNs as well as the way of handling Charging Characteristics and whether to send them or not to the P GW is defined in TS 32.251 . The MME shall include Trace Reference, Trace Type, Trigger Id, and OMC Identity if S GW and/or P GW trace is activated. The MME shall copy Trace Reference, Trace Type, and OMC Identity from the trace information received from the HLR or OMC. The Maximum APN Restriction denotes the most stringent restriction as required by any already active bearer context. If there are no already active bearer contexts, this value is set to the least restrictive type (see clause 15.4 of TS 23.060 ). If the P GW receives the Maximum APN Restriction, then the P GW shall check if the Maximum APN Restriction value does not conflict with the APN Restriction value associated with this bearer context request. If there is no conflict the request shall be allowed, otherwise the request shall be rejected with sending an appropriate error cause to the UE. NOTE 7: The Dual Address Bearer Flag is not used when the Protocol Type over S5/S8 is PMIP. 4. Create Session Request [TS 23.401] The Serving GW creates a new entry in its EPS Bearer table and sends a Create Session Request (IMSI, MSISDN, APN, Serving GW Address for the user plane, Serving GW TEID of the user plane, Serving GW TEID of the control plane, RAT type, Default EPS Bearer QoS, PDN Type, PDN Address, subscribed APN-AMBR, EPS Bearer Identity, Protocol Configuration Options, Handover Indication, ME Identity, User Location Information (ECGI), MS Info Change Reporting support indication, Selection Mode, Charging Characteristics, Trace Reference, Trace Type, Trigger Id, OMC Identity, Maximum APN Restriction, Dual Address Bearer Flag) message to the PDN GW indicated by the PDN GW address received in the previous step. After this step, the Serving GW buffers any downlink packets it may receive from the PDN GW without sending a Downlink Data Notification message to the MME until it receives the Modify Bearer Request message in step 23 below. The MSISDN is included if received from the MME. 5. IP-CAN Session Establishment [TS 23.203] – next episode 6. Create Session Response [TS 23.401] The P GW creates a new entry in its EPS bearer context table and generates a Charging Id. The new entry allows the P GW to route user plane PDUs between the S GW and the packet data network, and to start charging. The way the P GW handles Charging Characteristics that it may have received is defined in TS 32.251 . The PDN GW returns a Create Session Response (PDN GW Address for the user plane, PDN GW TEID of the user plane, PDN GW TEID of the control plane, PDN Type, PDN Address, EPS Bearer Identity, EPS Bearer QoS, Protocol Configuration Options, Charging Id, Prohibit Payload Compression, APN Restriction, Cause, MS Info Change Reporting Action (Start) (if the PDN GW decides to receive UE’s location information during the session), APN-AMBR) message to the Serving GW. The PDN GW takes into account the received PDN type, the Dual Address Bearer Flag and the policies of operator when the PDN GW selects the PDN type to be used as follows. If th received PDN type is IPv4v6 and both IPv4 and IPv6 addressing is possible in the PDN but the Dual Address Bearer Flag is not set, or only single IP version addressing for this APN is possible in the PDN, the PDN GW selects a single IP version (either IPv4 or IPv6). If the received PDN type is IPv4 or IPv6, the PDN GW uses the received PDN type if it is supported in the PDN, otherwise an appropriate error cause will be returned. The PDN GW allocates a PDN Address according to the selected PDN type. If the PDN GW has selected a PDN type different from the received PDN Type, the PDN GW indicates together with the PDN type IE a reason cause to the UE why the PDN type has been modified, as described in clause 188.8.131.52. PDN Address may contain an IPv4 address for IPv4 and/or an IPv6 prefix and an Interface Identifier. If the PDN has been configured by the operator so that the PDN addresses for the requested APN shall be allocated by usage of DHCPv4 only, or if the PDN GW allows the UE to use DHCPv4 for address allocation according to the Address Allocation Preference received from the UE, the PDN Address shall be set to 0.0.0.0, indicating that the IPv4 PDN address shall be negotiated by the UE with DHCPv4 after completion of the Default Bearer Activation procedure. In case of external PDN addressing for IPv6, the PDN GW obtains the IPv6 prefix from the external PDN using either RADIUS or Diameter client function. In the PDN Address field of the Create Session Response, the PDN GW includes the Interface Identifier and IPv6 prefix. The PDN GW sends Router Advertisement to the UE after default bearer establishment with the IPv6 prefix information for all cases. If the PDN address is contained in the Create Session Request, the PDN GW shall allocate the IPv4 address and/or IPv6 prefix contained in the PDN address to the UE. The IP address allocation details are described in clause 5.3.1 on “IP Address Allocation”. The PDN GW derives the BCM based on the NRSU and operator policy. Protocol Configuration Options contains the BCM as well as optional PDN parameters that the P GW may transfer to the UE. These optional PDN parameters may be requested by the UE, or may be sent unsolicited by the P GW. Protocol Configuration Options are sent transparently through the MME. 7. Create Session Response [TS 23.401] If the MS Info Change Reporting Action (Start) is received for this bearer context, then the S GW shall store this for the bearer context and the S GW shall report to that P GW whenever a UE’s location change occurs that meets the P GW request, as described in clause 15.1.1a of TS 23.060 . The Serving GW returns a Create Session Response (PDN Type, PDN Address, Serving GW address for User Plane, Serving GW TEID for User Plane, Serving GW TEID for control plane, EPS Bearer Identity, EPS Bearer QoS, PDN GW addresses and TEIDs (GTP-based S5/S8) or GRE keys (PMIP-based S5/S8) at the PDN GW(s) for uplink traffic, Protocol Configuration Options, Charging Id, Prohibit Payload Compression, APN Restriction, Cause, MS Info Change Reporting Action (Start), APN-AMBR) message to the new MME. 8. Initial Context Setup Request/ Attach Accept [TS 23.401] If an APN Restriction is received, then the MME shall store this value for the Bearer Context and the MME shall check this received value with the stored value for the Maximum APN Restriction to ensure there are no conflicts between values. If the Bearer Context is accepted, the MME shall determine a (new) value for the Maximum APN Restriction. If there is no previously stored value for Maximum APN Restriction, then the Maximum APN Restriction shall be set to the value of the received APN Restriction. If the MS Info Change Reporting Action (Start) is received for this bearer context, then the MME shall store this for the bearer context and the MME shall report whenever a UE’s location change occurs that meets the request, as described in clause 15.1.1a of TS 23.060 . The MME determines the UE AMBR to be used by the eNB based on the subscribed UE-AMBR and the APN AMBR for the default APN, see clause 4.7.3. The new MME sends an Attach Accept (APN, GUTI, PDN Type, PDN Address, TAI List, EPS Bearer Identity, Session Management Request, Protocol Configuration Options, KSIASME, NAS sequence number, NAS-MAC, IMS Voice over PS session supported Indication) message to the eNodeB. GUTI is included if the new MME allocates a new GUTI. This message is contained in an S1_MME control message Initial Context Setup Request. This S1 control message also includes the AS security context information for the UE, the Handover Restriction List, the EPS Bearer QoS, the UE-AMBR, EPS Bearer Identity, as well as the TEID at the Serving GW used for user plane and the address of the Serving GW for user plane. In the Attach Accept message, the MME does not include the IPv6 prefix within the PDN Address. The MME includes the EPS Bearer QoS parameter QCI and APN-AMBR into the Session Management Request. Furthermore, if the UE has UTRAN or GERAN capabilities, the MME uses the EPS bearer QoS information to derive the corresponding PDP context parameters QoS Negotiated (R99 QoS profile), Radio Priority, Packet Flow Id and TI and includes them in the Session Management Request. If the UE indicated in the UE Network Capability it does not support BSS packet flow procedures, then the MME shall not include the Packet Flow Id. Handover Restriction List is described in clause 184.108.40.206 “Mobility Restrictions”. The MME sets the IMS Voice over PS session supported Indication as described in clause 220.127.116.11. If the MME or PDN GW has changed the PDN Type, an appropriate reason cause shall be returned to the UE as described in clause 18.104.22.168. 9. RRC Connection Reconfiguration [TS 23.401] The eNodeB sends the RRC Connection Reconfiguration message including the EPS Radio Bearer Identity to the UE, and the Attach Accept message will be sent along to the UE. The UE shall store the QoS Negotiated, Radio Priority, Packet Flow Id and TI, which it received in the Session Management Request, for use when accessing via GERAN or UTRAN. The APN is provided to the UE to notify it of the APN for which the activated default bearer is associated. For further details, see TS 36.331 . The UE may provide EPS Bearer QoS parameters to the application handling the traffic flow(s). The application usage of the EPS Bearer QoS is implementation dependent. The UE shall not reject the RRC Connection Reconfiguration on the basis of the EPS Bearer QoS parameters contained in the Session Management Request. When receiving the Attach Accept message the UE shall set its TIN to “GUTI” as no ISR Activated is indicated. If the UE receives an IPv4 address set to 0.0.0.0, it may negotiate the IPv4 address with DHCPv4 as specified in TS 29.061 . If the UE receives an IPv6 interface identifier, it may wait for the Router Advertisement from the network with the IPv6 prefix information or it may send a Router Solicitation if necessary. NOTE 10: The IP address allocation details are described in clause 5.3.1 on “IP Address Allocation”. 10. RRC Connection Reconfiguration Complete [TS 23.401] The UE sends the RRC Connection Reconfiguration Complete message to the eNodeB. For further details, see TS 36.331 . 11. Initial Context Setup Response [TS 23.401] The eNodeB sends the Initial Context Response message to the new MME. This Initial Context Response message includes the TEID of the eNodeB and the address of the eNodeB used for downlink traffic on the S1_U reference point. 12. Direct Transfer [TS 23.401] The UE sends a Direct Transfer message to the eNodeB, which includes the Attach Complete (EPS Bearer Identity, NAS sequence number, NAS-MAC) message. 13. Attach Complete [TS 23.401]
P-CSCF Discovery - described in TS 23.228: section 5.1.1 Procedures related to Proxy-CSCF discovery and section E.1.1.1 GPRS/EPS procedure for P-CSCF discovery Because the procedure is pretty straight-forward, I will just copy-paste it from the spec above: The Proxy CSCF discovery shall be performed using one of the following mechanisms: - As part of the establishment of connectivity towards the IP-Connectivity Access Network, if the IP-Connectivity Access Network provides such means. - Alternatively, the P CSCF discovery may be performed after the IP connectivity has been established. To enable P CSCF discovery after the establishment of IP connectivity, the IP-Connectivity Access Network shall provide the following P CSCF discovery option to the UE: - Use of DHCP to provide the UE with the domain name and/or IP address of a Proxy CSCF and the address of a Domain Name Server (DNS) that is capable of resolving the Proxy CSCF name, as described below in clause 22.214.171.124. - The UE may be configured (e.g. during initial provisioning or via a 3GPP IMS Management Object (MO), TS 24.167  or in the ISIM, TS 31.103 ) to know the fully qualified domain name (FQDN) of the P CSCF or its IP address. If the domain name is known, DNS resolution is used to obtain the IP address. In the case where UE is aware of more than one P CSCF address, the selection shall be based on home operator configured policy to select the P CSCF. NOTE: Subject to home operator policy, the UE selects the Home P CSCF to be used by either using a pre-configured Home P CSCF FQDN or according to TS 24.167 . This can be done without the UE first performing the local P CSCF discovery (e.g. DHCP). Section 126.96.36.199 describes the DHCP/DNS procedure for P-CSCF discovery: The DHCP relay agent within the IP-Connectivity Access Network relays DHCP messages between UE and the DHCP server.
17. Register message sent from the IMS terminal to the P-CSCF Once the IMS terminal obtains its IP address, it must register to the IMS network. This happens in order for the UE to authenticate and obtain authorization to use the IMS network resources. The IMS registration is accomplished by the SIP REGISTER message – this being also the only SIP message that is authenticated by the network (subsequent SIP messages, like INVITE, 200 OK…and so on, are not being authenticated). First of all, we should know that the IMS-SIP is a SIP (RFC 3261) on steroids (as my SIP colleague use to joke ), because it has a lot of 3GPP enhancements to meet the 3GPP requirements for this type of communication – I won’t get into details right now. One requirement is that, in IMS, unlike in regular SIP, a phone cannot make any call without first being registered to the IMS network. Second of all, let’s establish the meaning of this “register” procedure. What the REGISTER procedure does is bind the public URI of that IMS user to a certain IP address and/or host name. The IP address/host name are the ones given by the IP-CAN Session during attach or later on. It is the means of locating that phone in the network. The point is to let the IMS network know at which actual address (IP/host name) it can find a user it has configured as subscriber. Short note: this public URI thinggie is the identity of the subscriber, something like an e-mail address, only less pretty . It can also contain a bunch of weird parameters that I won’t get into details with right now: examples of SIP URIs: sip:Alice.Smith@domain.com sip:Bob.Brown@example.com sip:email@example.com;transport=tcp SIP URIs with SDP information (SDP – Session Description Protocol) : v=0 o=Bob 234562566 236376607 IN IP4 192.0.0.2 s=Let’s talk about martial arts c=IN IP4 188.8.131.52 t=0 0 m=audio 30000 RTP/AVP 0 a=sendrecv m=video 30002 RTP/AVP 31 a=sendrecv Before actually taking a look at this fancy SIP REGISTER message, let’s present the IMS requirements for SIP Registration: [Bear in mind that many of the information below are inspired/taken from the following book: http://www.amazon.com/3G-IP-Multimedia-Subsystem-IMS/dp/0470871563 The 3G IP Multimedia System: Merging the Internet and the Cellular Worlds by Gonzalo Camarillo and Miguel-Angel Garcia-Martin ] The IMS registration procedure satisfies the following requirements in two round trips: (a) the user binds a Public User Identity to a contact address – this is the main purpose ofa SIP REGISTER request; (b) the home network authenticates the user; (c) the user authenticates the home network; (d) the home network authorizes the SIP registration and the usage of IMS resources; (e) in case the P-CSCF is located in a visited network, the home network verifies that there is an existing roaming agreement between the home and the visited network and authorizes the usage of the P-CSCF; (f) the home network informs the user about other possible identities that the home network operator has allocated exclusively to that user; (g) the IMS terminal and the P-CSCF negotiates the security mechanism that will be in place for subsequent signaling; (h) the P-CSCF and the IMS terminal establish a set of security associations that protect the integrity of SIP messages sent between the P-CSCF and the terminal; (i) both the IMS terminal and the P-CSCF upload to each other the algorithms used for compression of SIP messages. Before creating the SIP Register message, the UE terminal retrieves the Private User Identity from its ISIM card, along with its Public User Identity and its home network domain URI. OK, so let’s take a look at the actual SIP REGISTER message the IMS terminal sends to its P-CSCF, via the 4G Access Network: REGISTER sip:registrar1.home.net SIP/2.0 Via: SIP/2.0/UDP [5555::aaa:bbb:ccc:ddd];comp=sigcomp;branch=z9hG4bK9h9ab Max-Forwards: 70 P-Access-Network-Info: 3GPP-EUTRAN-FDD;eutran-cell-id-3gpp=C359A3913B20E From: <sip:firstname.lastname@example.org>;tag=s8732n To: <sip:email@example.com> Contact: <sip:[5555::aaa:bbb:ccc:ddd];comp=sigcomp>;expires=600000 Call-ID: 23fi57lju Authorization: Digest username=”firstname.lastname@example.org”,realm=”registrar1.home.net”, nonce=”",uri=”sip:registrar1.home.net”, response=”" Security-Client: ipsec-3gpp; alg=hmac-sha-1-96;spi-c=3929102; spi-s=0293020; port-c:3333; port-s=5059 Require: sec-agree Proxy-Require: sec-agree Cseq: 1 REGISTER Supported: path Content-Length: 0 1. The first line identifies the method, which is REGISTER, then it is followed by the Request-URI. This Request-URI identifies the destination domain of the Register request. - this Request-URI has the role of registration URI which identifies the home network or a subdomain of the network 2. The Via header is the IP address ( here: 5555::aaa:bbb:ccc:ddd) given to the UE during the initial attach or bearer activation, statically or dynamically (IP-CAN) assigned. 3. The P-Access-Network-Info represents the access type and information related to the access network, in our case, a 3GPP 4G network – LTE wireless, FDD, with the specified cell id. 4. The To: and From: fields are usually taken from the USIM. These fields have the same value in the Register message, representing the Public User Identity, also called Address-of-Record. This is the identity the other parties know and use to contact this UE. 5. The Contact: header represents the temporary point of presence for this UE. Its value is the most recent IP address the UE has and this address is stored in the S-CSCF. This is the third important parameter about the UE, the Contact Address (the other two being the registration URI and Address-of-Record). 6. The Authorization field caries out authentication information about the terminal. This information is the forth parameter used for registration, having the role of the Private User Identity. This value is the equivalent of the IMSI field in the GSM system and it should not be displayed to the user. It is used by the AKA fields to authenticated the user. This parameter is composed by the private ID and the domain name of the home network where the UE registers. The nonce and response parameters are empty, because this case considers the terminal has just been turned on for the first time, otherwise there should have been some cached information to send here. 7. The Security-Client field lists the algorithms supported by the UE. In this case, the terminal has IPsec capabilities. 8. The client requires the parties to agree on its security parameters and also indicates it supports the Path header.
Ims, at beginning was...
IMSat beginning was…
Agenda• IMS Specification references• IMS IP attach• P-CSCF Discovery• IMS Registration• IMS session set up• IMS adding a media during a session• IMS session terminating Please refer to the notes panel for the explanation of flow
IMS Specifications references (1)• The General aspects:• 3GPP TS 22.228 Service Requirements for the IP Multimedia Core Network (IM CN) Subsystem – Stage 1• 3GPP TS 23.228 IP Multimedia Subsystem (IMS) – Stage 2• Registration:• RFC 3327 SIP “Path” Extension Header Field for Registering Non-Adjacent Contacts• RFC 3608 SIP Extension Header Field for Service Route Discovery during Registration• Diameter:• 3GPP TS 29.109 GAA – Zh and Zn Interfaces based on the Diameter protocol – Stage 3• 3GPP TS 29.229 Cx and Dx interfaces based on the Diameter protocol – Protocol Details• 3GPP TS 29.230 Diameter Applications – 3GPP Specific Codes and Identifiers• 3GPP TS 29.329 Sh Interface based on the Diameter protocol – Protocol Details• 3GPP TS 32.299 Charging Management – Diameter Charging Applications• RFC 3588 Diameter Base Protocol• RFC 3589 Diameter Command Codes for 3GPP Release 5• RFC 4740 Diameter Session Initiation Protocol (SIP) Application• Identification:• 3GPP TS 23.228 IP Multimedia Subsystem (IMS) – Stage 2• 3GPP TS 29.229 Cx and Dx interfaces based on the Diameter protocol – Protocol Details• RFC 4282 The Network Access Identifier
IMS Specifications references (2)• Policy:• 3GPP TS 23.203 Policy and Charging Control Architecture• 3GPP TS 29.207 Policy Control over Go Interface• 3GPP TS 29.208 End-to-end Quality of Service (QoS) Signalling Flows• 3GPP TS 29.209 Policy control over Gq Interface• Charging:• 3GPP TS 22.115 Service Aspects – Charging and Billing• 3GPP TS 32.240 Charging Architecture and Principles• 3GPP TS 32.260 IP Multimedia Subsystem (IMS) Charging• 3GPP TS 23.125 Overall high level functionality and architecture impacts of flow based charging – Stage 2• 3GPP TS 23.203 Policy and Charging Control Architecture• 3GPP TS 29.210 Charging Rule Provisioning over Gx Interface• 3GPP TS 29.211 Rx Interface and Rx/Gx Signalling Flows• 3GPP TS 23.203 Policy and Charging Control Architecture• 3GPP TS 32.295 Charging Data Record (CDR) Transfer• 3GPP TS 32.296 Online Charging System (OCS): Applications and Interfaces• 3GPP TS 32.297 Charging Data Record (CDR) File Format and Transfer• 3GPP TS 32.298 Charging Data Record (CDR) Parameter Description• 3GPP TS 32.299 Diameter Charging Applications• Security:• 3GPP 33-series 3GPP Specifications related to Security
IMS Specifications references (3)• QoS:• 3GPP TS 23.107 Quality of Service (QoS) Concept and Architecture• 3GPP TS 23.207 End-to-end Quality of Service (QoS) Concept and Architecture• 3GPP TS 29.208 End-to-end Quality of Service (QoS) Signalling Flows• OSA:• 3GPP TS 22.127 Service Requirement for the Open Service Access (OSA) – Stage 1• 3GPP TS 23.198 Open Service Access (OSA) – Stage 2• 3GPP TS 29.198 29.198 series: Open Service Access (OSA) API• 3GPP TS 29.199 29.199 series: OSA Parlay X Web Services• CAMEL:• 3GPP TS 22.078 CAMEL – Service description – Stage 1• 3GPP TS 23.078 CAMEL Phase 4 – Stage 2• 3GPP TS 23.278 CAMEL Phase 4 – Stage 2 – IM CN Interworking• 3GPP TS 29.078 CAMEL Phase X – CAMEL Application Part (CAP) specification• 3GPP TS 29.278 CAMEL Phase 4 – CAP specification for IP Multimedia Subsystems (IMS)• 3GPP TS 29.002 Mobile Application Part (MAP) specification• WLAN Access:• 3GPP TS 22.234 Requirements on 3GPP system to Wireless Local Area Network (WLAN) interworking• 3GPP TS 23.234 3GPP System to WLAN Interworking – System Description• 3GPP TS 24.234 WLAN User Equipment (WLAN UE) to Network Protocols – Stage 3• 3GPP TS 29.161 Interworking between the PLMN supporting Packet based Services with WLAN Access and PDNs• 3GPP TS 29.234 3GPP System to WLAN Interworking – Stage 3• 3GPP TS 32.252 WLAN Charging• 3GPP TS 33.234 WLAN Interworking Security
IMS Specifications references (4)• CSICS: Circuit Switched IMS Combinational Services:• 3GPP TS 22.279 Combined CS and IMS Sessions – Stage 1• 3GPP TS 23.279 Combining Circuit Switched (CS) and IMS Services – Stage 2• 3GPP TS 24.279 Combining Circuit Switched (CS) and IMS Services – Stage 3• Presence:• 3GPP TS 22.141 Presence Service – Stage 1 – Requirements• 3GPP TS 23.141 Presence Service – Stage 2 – Architecture and functional description• 3GPP TS 24.141 Presence service using the IP Multimedia (IM) Core Network (CN) subsystem – Stage 3• 3GPP TS 26.141 IMS Messaging and Presence – Media formats and codecs• 3GPP TS 33.141 Presence service – Security OMA Presence Simple OMA Presence Simple V1.0.1 Approved Enabler• PoC: Push-to-talk over Cellular:• 3GPP TR 23.979 Push-to-talk over Cellular (PoC) Services – Stage 2• 3GPP TS 32.272 Push-to-talk over Cellular (PoC) charging
IMS IP attach• the procedure of IP-CAN (Connectivity Access Network) establishment is described in TS 23.203.• IP-CAN is the IP address that the User Equipment gets during Initial Attach or at a Dedicated Bearer creation that connects that UE to the IMS APN.• There are multiple ways of getting this IP address, ways varying from DHCP/DHCPv6, PPP and so on. With regards to IMS, the IP-CAN is given by the PGW, following the PCC rules from its local PCRF.• But, before displaying the actual IP-CAN Session Establishment, let’s take a look at the functional entities and the architectures involved.
P CSCF discoveryThe Proxy CSCF discovery shall be performed using one of the followingmechanisms:- As part of the establishment of connectivity towards the IP-Connectivity Access Network, if the IP-Connectivity Access Networkprovides such means.- Alternatively, the P CSCF discovery may be performed after the IPconnectivity has been established. To enable P CSCF discovery after theestablishment of IP connectivity, the IP-Connectivity Access Network shallprovide the following P CSCF discovery option to the UE:- Use of DHCP to provide the UE with the domain name and/or IPaddress of a Proxy CSCF and the address of a Domain Name Server (DNS)that is capable of resolving the Proxy CSCF name, as described below inclause 184.108.40.206.- The UE may be configured (e.g. during initial provisioning or via a3GPP IMS Management Object (MO), TS 24.167  or in the ISIM, TS 31.103) to know the fully qualified domain name (FQDN) of the P CSCF or its IPaddress. If the domain name is known, DNS resolution is used to obtain the IPaddress.
P CSCF discovery (DHCP)• 1. Establish an IP-Connectivity Access Network bearer if not already available by using the procedures available in the IP-Connectivity Access Network.• 2. The UE requests a DHCP server and additionally requests the domain name and/or IP address of the P‑CSCF and IP addresses of DNS servers. It may require a multiple DHCP Query/Response message exchange to retrieve the requested information.• 3. The UE performs a DNS query to retrieve a list of P‑CSCF(s) IP addresses from which one is selected. If the response does not contain the IP addresses, an additional DNS query is needed to resolve a Fully Qualified Domain Name (FQDN) to an IP address.• After reception of domain name and IP address of a P ‑CSCF the UE may initiate communication towards the IM subsystem. UE IP-CAN DHCP DNS Serv er Serv er 1.IP-CAN Bearer Establ i shment 2. DHCP- Query / 2. DHCP- Response Relay 3. DNS- Query /Response
Thanks• The 3G IP Multimedia System: Merging the Internet and the Cellular Worlds by Gonzalo Camarillo and Miguel-Angel Garcia-Martin http://www.amazon.com/3G-IP-Multimedia- Subsystem-IMS/dp/0470871563• http://www.imacandi.net/windancer/2010/08/29/4 g-to-ims-call-flow-–-register-to-ims-–-part-4.html