12.07.2015 Views

ericssonhistory.com

ericssonhistory.com

ericssonhistory.com

SHOW MORE
SHOW LESS
  • No tags were found...

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Figure 9High-availability deployment environment.Figure 10SNF tier view.Data model viewData modeling is an important part of allarchitectural efforts. The SNF data modelview specifies a uniform data model for userandservice-related data and associated provisioningwithin the service network. TheSNF data model has been designed• to support various business and servicelife-cycle models;• to enable designs that distribute userrelateddata throughout the service network;• to support and enable the SNF <strong>com</strong>monprovisioning model;• to support information on how services aredependent on various systems; and• to support extensions that ac<strong>com</strong>modatesolution-specific requirements.Deployment of the data model is generallymade through a directory server (systemtype CDS) within an actual service network.Although the data model can be used toprovide access to all user and servicerelateddata in a service network, it does notnecessarily follow that all data is modeledwithin the data model. Instead, data can bereferenced, which allows for easy integrationof existing, stand-alone data models, calledaffiliate data models. This gives the solutionarchitect room to design service networksusing the main data model and affiliate datamodels.Applied viewThe applied view introduces the SNF blueprint,which provides a reference architecturethat maps SNF system types, their interfaces,and collaborations to a single view.Some typical and important collaborationsdepicted in the SNF blueprint are• the central provisioning entity (CPE),CDS, and system <strong>com</strong>ponent registry(SCR)—to achieve <strong>com</strong>mon provisioningof SNF systems that require provisioning;• the central management entity (CME)collaborating with all other SNF systems—toachieve <strong>com</strong>mon management;• the <strong>com</strong>mon charging entity (CCE) collaboratingwith all other SNF systems—to achieve <strong>com</strong>mon charging; and• the border gateway (BGW), central authenticationentity (CAE), and centralsession entity (CSE)—to achieve singlesign-on for HTTP.SNF rule catalogThe SNF rule catalog is a set of architecturalrules presented along functional and qual-24 Ericsson Review No. 1, 2003

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!