Providing a core infrastructure that can support these services is important.
This is what IMS is all about. There is no argument that TCP/IP can be used today to
deliver multimedia services. Many of us are using these services today through sources
such as AOL and Google. However, how those services are managed, how they are made
secure and how billing is implemented constitute another challenge.
The IMS is not about services. The IMS is about providing access to all services regardless
of the media type, using a common control architecture that works well for all
media. This means that one common control plane is used for video, voice, data, messaging,
and any other media format needed. What??™s even more important is that the control
plane provided through IMS does not need modification to support a new media type.
It does not need a different technology for each media type. Everything is controlled
through one common session control protocol: the Session Initiation Protocol (SIP).
Another fundamental difference with IMS is security. When one looks at today??™s VoIP
implementations, security is sometimes part of the implementation, but it is not very aggressive.
The 3GPP has defined new security functions as a part of the IMS model, and
a base function of the call session control function that establishes the core of the IMS.
The 3GPP has really defined how to approach implementing an all-IP network with
robust security, charging, and session control at the core of the network rather than in
many different boxes, all interconnecting with one another.
Pages:
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38