1 / 10

AAA in an Mmed All-IP Network

AAA in an Mmed All-IP Network. Henrik Basilier, Ericsson. Multimedia service layer. Multimedia call servers, Gateways etc. Network layer. Access independent functionality For connectivity, routing, mobility, etc. Access layer. Access specific functionality (roughly RAN).

caelan
Download Presentation

AAA in an Mmed All-IP Network

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. AAA in an Mmed All-IP Network Henrik Basilier, Ericsson

  2. Multimedia service layer Multimedia call servers, Gateways etc. Network layer Access independent functionality For connectivity, routing, mobility, etc. Access layer Access specific functionality (roughly RAN) Assumed layering

  3. MSC/VLR MIP Client FAAAN HLR HAAAN BAAA “Access Registration Client” PDSN The starting point Home IP service provider ANSI-41 Visited Access Provider Home Access provider Important to keep the logical separation between home IP network and home access provider !

  4. SIP The client registers with the network (SIP servers), and is also authenticated by the network. These registrations are in important part of the SIP protocol suite. => Should conceptually be supported in the architecture (even if it might be the case that it NOT ALWAYS is needed !

  5. CSCF (serving) CSCF (proxy) ACS SIP Client MIP Client Access Registration Client HAAAN FAAAM HAAAA FAAAA BAAA FAAAN HAAAM PDSN HA AAA Logical Architecture Home Multimedia service provider Home IP service provider Visited Access Provider Home Access provider

  6. CSCF (proxy) ACS MIP Client SIP Client HAAAN HAAAA BAAA Access Registration Client FAAAN FAAAA FAAAM HAAAM PDSN Typical physical architecture AAA AAA Home Access provider Visited Access Provider

  7. CSCF (proxy) ACS MIP Client SIP Client HAAAA Access Registration Client BAAA HAAAN FAAAN FAAAA FAAAM HAAAM PDSN Assume use of same NAI andsame secrets in all layers - NAI - Secret Home access provider Visited Access Provider

  8. What does this scenario tell us? User will never see more than one authentication (one name, one password) in this scenario (but in others, like corporate access) Might be possible to remove steps in the signaling needed in this scenario, if we make use the fact that the same NAI is used and that the same secrets with the home network may be used in all layers.

  9. Other scenarios 1. It is still possible to have a home IP network different from the home IP access, for example corporate netorks or ISPs 2. In the case where there is a separation between MT and TE, it is possible to split the authentication between them: a) Just access layer in MT, network and service layer in TE b) Access and network layer in MT, service layer in TE 3. Wireless access + IP network access provider cooperating with other carrier providing multimedia services ?

  10. Home Subscriber System (HSS) Common functions and databases AAA protocol (e.g DIAMETER) ANSI-41 e.g SIP HAAAN Others HAAAM HAAAA ANSI-41 termination IP MM Control Protocol termination How does it relate to the HSS?

More Related