1.ims concepts

© Nex-G Exuberant Solutions Pvt. Ltd.Copyright © Nex-G | Skills , NESPL
IMS Concepts

IMS services concepts
• Home-network based services :
Support of CAMEL or IN
Support of OSA
• Support of roaming users :
Architecture shall be based on the principle that the service control for Home
subscribed services for a roaming subscriber is in the Home network, e.g., the Serving-
CSCF is located in the Home network.
There are two possible scenarios to provide services:
- via the service platform in the Home Network
- via an external service platform (e.g. third party or visited network)

An Application Server (AS) offering value added IM services resides either in the user's
home network or in a third party location. The third party could be a network or
simply a stand-alone AS.
The Serving-CSCF to AS interface is used to provide services residing in an AS. Two
cases were identified:
- Serving-CSCF to an AS in Home Network.
- Serving-CSCF to an AS in External Network (e.g., Third Party or Visited)
More specifically the following requirements apply to the IMS Service control interface:
- The ISC interface shall be able to convey charging information .
- The protocol on the ISC interface shall allow the S-CSCF to differentiate between
SIP requests on Mw, Mm and Mg interfaces and SIP Requests on the ISC interface.
HSS to service platform Interface : The Application Server (SIP Application Server
and/or the OSA service capability server and/or IM-SSF) may communicate to the
HSS. The Sh and Si interfaces are used for this purpose.

For the Sh interface, the following shall apply:
- The Sh interface is an intra-operator interface.
- The Sh interface is between the HSS and the "SIP Application Server" and between
the HSS and the "OSA service capability server". The HSS is responsible for policing
what information will be provided to each individual Application Server.
- The Sh interface transports transparent data for e.g. service related data , user
related information, etc.
- The Sh interface also supports mechanisms for transfer of user related data stored
in the HSS (e.g. user service related data, MSISDN, visited network capabilities, user
location (e.g. cell global ID/SAI or the address of the serving network element, etc))
- The Sh interface also supports mechanisms for transfer of standardised data.

• I-CSCF to AS reference point (Ma) : The Ma reference point is between the
Interrogating CSCF and the service platform(s). The Interrogating-CSCF to AS
reference point is used to:
- forward SIP requests destined to a Public Service Identity hosted by an Application
Server directly to the Application Server;
- originate a session on behalf of a user or Public Service Identity, if the AS has no
knowledge of a S CSCF assigned to that user or Public Service Identity.

• The QoS requirements for an IM CN subsystem session
The selection, deployment, initiation and termination of QoS signalling and resource
allocation shall consider the following requirements so as to guarantee the QoS
requirement associated with an IM CN subsystem session :
1. Independence between QoS signalling and Session Control
2. Necessity for End-to-End QoS Signalling and Resource -Allocation
3. Restricted Resource Access at the IP BS Level
4. Restricted Resource Access at the IP-Connectivity Access Network (i.e. layer-2)
Level
5. Co-ordination between Session Control and QoS Signalling/Resource Allocation
6. The Efficiency of QoS Signalling and Resource Allocation
7. Prevention of Theft of Service

• QoS Requirements for IM CN subsystem signalling : Depending on the bearer
establishment mode, the UE shall be able to establish a dedicated signalling for IM
Subsystem related signalling
The use of a dedicated signalling IP-CAN (IP-Connectivity Access Network) bearer
for IM Subsystem related signalling may provide enhanced QoS for signalling traffic.

Naming and addressing concepts
When a UE is registered in the IM CN Subsystem with an IP address, any change to this
IP address that is used to access the IM CN subsystem will result in dropping the
active SIP dialogs, and shall trigger automatic registration.
This automatic registration updates the UE's IP address and security association. To
avoid disruption of ongoing IM CN subsystem services, the UE should not change
the IP address that it uses to access the IM CN subsystem while engaged in active
SIP dialogs (e.g. INVITE or SUBSCRIBE-NOTIFY dialogs).
Identification of users
The various identities that may be associated with a user of IP multimedia services are :
• Private User Identities
• Public User Identities
• Relationship of Private and Public User Identities
• Relationship of Public User Identities, GRUUs, and UEs
• Identification of network nodes
• Public Service Identities

Identification of users can be done by three identities :
Private User Identities
Public User Identities
Globally Routable User Agent URI (GRUU)
• Private User Identities :
Every IM CN subsystem user shall have one or more Private User Identities. The
private identity is assigned by the home network operator, and used, for example, for
Registration, Authorization, Administration, and Accounting purposes.
- The Private User Identity is not used for routing of SIP messages.
- The Private User Identity shall be contained in all Registration requests, (including
Re-registration and De-registration requests) passed from the UE to the home
network.
- The Private User Identity is a unique global identity defined by the Home Network
Operator, which may be used within the home network to identify the user's
subscription

- The Private User Identity shall be permanently allocated to a user's subscription
- The Private User Identity is used to identify the user's information (for example
authentication information)stored within the HSS (for use for example during
Registration).
- The Private User Identity may be present in charging records based on operator
policies.
- The Private User Identity is authenticated only during registration of the user,
(including re-registration and de-registration).
- The HSS needs to store the Private User Identity.

• Public User Identities :
Every IM CN subsystem user shall have one or more Public User Identities.The Public
User Identity is used by any user for requesting communications to other users.
- Both telecom numbering and Internet naming schemes can be used to address users
depending on the Public User identities that the users have.
- A Public User Identity shall be registered either explicitly or implicitly before
originating IMS sessions and originating IMS session unrelated procedures can be
established by a UE using the Public User Identity.
- A Public User Identity shall be registered either explicitly or implicitly before
terminating IMS sessions
- It shall be possible to register globally (i.e. through one single UE request) a user that
has more than one public identity via a mechanism within the IP multimedia CN
subsystem.
- Public User Identities are not authenticated by the network during registration.
- Public User Identities may be used to identify the user's information within the HSS
(for example during mobile terminated session set-up).

• Globally Routable User Agent URI (GRUU) :
A Globally Routable User Agent URI (GRUU) is an identity that identifies a unique
combination of Public User Identity and UE instance that allows a UE to address a
SIP request to a specific Public User Identity UE combination instance.
There are two types of GRUUs; Public GRUUs (P-GRUUs) and Temporary GRUUs (T-
GRUUs).
- P-GRUUs are GRUUs that reveal the Public User Identity of the user and are very
long lived.
- T-GRUUs are GRUUs that contain a URI (Uniform Resource Identifier) that do not
reveal the Public User Identity of the user and are valid until the contact is explicitly
de-registered or the current registration expires.

The CSCF, BGCF and MGCF nodes shall be identifiable using a valid SIP URI
(Uniform Resource Identifier) on those interfaces supporting the SIP protocol, (e.g.
Gm, Mw, Mm, and Mg).
These SIP URIs would be used when identifying these nodes in header fields of SIP
messages.
Identification of network nodes

Mobility related concepts
The following procedures are supported by an UE when accessing IMS:
- Connect to the IP-CAN and acquire the necessary IP address
- Register to the IM subsystem as defined by the IMS registration procedures;
- If an UE explicitly deactivates the IP-CAN bearer that is being used for IMS signalling,
it shall first de-register from the IMS (while there is no IMS session in progress);
- If an UE explicitly deactivates the IP-CAN bearer that is being used for IMS signalling
while an IMS session is in progress, the UE must first release the session and de-
register from the IMS and then deactivate the IP-CAN bearers;
- If an UE changes its IP address according to IP-CAN procedures (e.g. TS 23.221 [7]),
the UE shall re- register in the IMS by executing the IMS registration;

- If an UE acquires an additional IP address due to establishing an additional IP-CAN
bearer through a different access network, the UE may perform an IMS registration
using this IP address as the contact address.
- In order to be able to deliver an incoming IMS session, the IP-CAN bearer that is being
used for IMS signalling need to remain active as long as the UE is registered in the
IM CN subsystem;

1.ims concepts

More Related Content

What's hot

Similar to 1.ims concepts

Recently uploaded

1.ims concepts