We think you have liked this presentation. If you wish to download it, please recommend it to your friends in any social system. Share buttons are a little bit lower. Thank you!
Presentation is loading. Please wait.
Published byBrian Raynor
Modified about 1 year ago
User Data Convergence CT4 specifications Jean-Jacques Trottin October 2009
All Rights Reserved © Alcatel-Lucent 2006, ##### 2 | Presentation Title | Month 2006 From 3GPP Requirements : "The User Data Convergence concept supports a layered architecture, separating the user data storage from the application logic in the 3GPP system, so that user data is stored in a logically unique repository (UDR) allowing access from core and service layer entities, named application front-ends. Network elements and functionalities should be designed to access profile data remotely and without storing them permanently locally, i.e. the front-ends (FEs) shall work in a subscriber dataless configuration." UDC can apply to HLR/HSS Application servers ANDSF ….. User Data Convergence (UDC) Scope
All Rights Reserved © Alcatel-Lucent 2006, ##### 3 | Presentation Title | Month 2006 TS Stage 2 UDC architecture UDC Functional entities UDR : User Data repository Front end (FE): executing the application logic One reference point : Ud between UDR and Front ends e.g. HLR/HSS FE e.g. 3td party application FE e.g. provisioning application FE
All Rights Reserved © Alcatel-Lucent 2006, ##### 4 | Presentation Title | Month 2006 TS Stage 2 User Data Repository main characteristics UDR is a single logical repository from FE perspective a FE has only access to data relevant for it (application data view) UDR may interact with several Application front ends handling the same application logic or different application logics Internal structure of UDR out of standardization scope may be distributed over different locations or centralized, may support geographical redundancy, replication mechanisms and back up functions to secure the storage of data FE (and Ud interface) not aware of this internal structure UDR supports transactions (Database meaning) ACID (atomicity, consistency, isolation, durability) features
All Rights Reserved © Alcatel-Lucent 2006, ##### 5 | Presentation Title | Month 2006 TS Stage 2 Application front-end (FE) main characteristics An Application FE executes an application logic dealing with user data that are stored in the UDR E.g. HLR/ HSS application logic, AS application logic An application front-end interacts with other functional entities of the 3GPP system through existing 3GPP reference points Those existing reference points (C, Cx, Sh, S6a…) shall not be modified by the introduction of the UDC concept An application front-end may belong to a third party: Application FEs which are equivalent may be grouped into a FE Cluster Allowing distribution of requests
All Rights Reserved © Alcatel-Lucent 2006, ##### 6 | Presentation Title | Month 2006 TS Stage 2 UDC information flows Generic information flow: Data access + notification
All Rights Reserved © Alcatel-Lucent 2006, ##### 7 | Presentation Title | Month 2006 TS Stage 2 UDC information flows Ud is a Database access interface Query, Create, Delete, Update procedures Plus Subscription to notifications, notifications Ud Query Procedure Parameters –FE Identifier –user identity (e.g. IMSI, MSISDN, IMPU, IMPI –identification of the data (request) –data value (answer) (according to application data view) 4. Query data answer 1. Query data request UDRFE 2. Perform access control 3. Fetch data value and format it according to the requesting application data view
All Rights Reserved © Alcatel-Lucent 2006, ##### 8 | Presentation Title | Month 2006 TS Stage 2 Access Control Access Control by UDR: it is based on FE identity FE Application type: FE can only access to data associated to a given application (application data view) Type of procedure (Query, Update….) authorized Authentication and Security aspects to be handled with SA3 To be addressed
All Rights Reserved © Alcatel-Lucent 2006, ##### 9 | Presentation Title | Month 2006 TS UDC Stage 3 Working assumption CT4 agreed (at previous CT4) To use LDAP for Ud Query, Create, Delete, Update procedures Ud Query -> LDAP Search Ud Create -> LDAP Add Ud Delete -> LDAP Delete Ud Update -> LDAP Modify Still a debate about Subscription/Notifications between LDAP : that has limitations, so requiring extensions Another protocol: SOAP / XML To be decided in next CT4 (November) Application data view -> LDAP Schema (SA5) LDAP is Directory oriented data architecture –Tree /Subtrees –Naming aspects
All Rights Reserved © Alcatel-Lucent 2006, ##### 10 | Presentation Title | Month 2006 ANDSF case ANDSF (Access Network Discovery and Selection Function) Simple example of an application that needs to read some HSS data Eg list of access networks or their types a user can access Methodology aspect : who is doing what? Definition of the relevant data : SA2, CT1, CT4 Modelling (application data view ) : SA5 Pending points Are these data and associated application data view to be standardised? In rel9, rel10? LS from CT4 to CT1
All Rights Reserved © Alcatel-Lucent 2006, ##### 11 | Presentation Title | Month 2006 Time Schedule CT4 meetings : Nov 9th – 13th Feb 22nd – 27 th Exception procedures for Rel9 up to March 2010 –Mainly on stage 3 – Authentication security aspects
World Class Standards SuM Functional Architecture SuM NGN OSS Service Interfaces (NOSIs) TISPAN WG8 – 3GPP SA#5 Joint meeting Sophia Antipolis, May14th.
World Class Standards WG8 presentation of current Subscription Management Activities TISPAN WG8 – 3GPP SA#5 Joint meeting Sophia Antipolis, May14th - 15.
Page 1TTT - May 12, GPP IMS Standardization Update Bell Labs Innovations Lucent Technologies Room 9C Lucent Ln. Naperville, IL E Mail.
1 3GPP2 GBA Overview Adrian Escott Chair, TSG-S WG4 24 May 2006.
Chapter 5 Introduction to Database Management. Data Vital organizational resource Data resource management is a managerial action that applies technology.
1st Workshop on Intelligent and Knowledge oriented Technologies Universal Semantic Knowledge Middleware Marek Paralič,
Planning an Active Directory Deployment Lesson 1.
2001_03_28 SG A contribution– 1 Dept of State ITAC-T Advisory Committee SG-A Ad Hoc Meeting on ENUM March 28th & 29th, 2001 ENUM CONTRIBUTION TITLE: ENUM.
18 Copyright © 2005, Oracle. All rights reserved. Distributing Modular Applications: Introduction to Web Services.
Database Architecture Introduction to Databases. The Nature of Data Un-structured Semi-structured Structured.
What the $#*! IS my password? Secure Online Password Storage Lon Smith Aaron Gremmert.
Introduction to Core Database Concepts Getting started with Databases and Structure Query Language (SQL)
Relational Database and Data Modeling Lecture 10 (Chapter 4)
Database Design - Lecture 1 Database Concepts. 2 Lecture Objectives Data vs Information Historical Roots of Databases What is a database, what it does,
22-23 June 2004TISPAN-3GPP Workshop - Sophia-Antipolis 1 TISPAN NGN Architecture Overview Richard Brennan pulver.com, WG2 Chair
1 Schema Registries Steven Hughes, Lou Reich, Dan Crichton NASA 21 October 2015.
Distributed Systems Major Design Issues Presented by: Christopher Hector CS8320 – Advanced Operating Systems Spring 2007 – Section 2.6 Presentation Dr.
Framework & Requirements for an Access Node Control Mechanism in Broadband Multi-Service Networks ANCP WG IETF 70 – Vancouver draft-ietf-ancp-framework-04.txt.
SOFTWARE DESIGN AND ARCHITECTURE LECTURE 09. Review Introduction to architectural styles Distributed architectures – Client Server Architecture – Multi-tier.
UNCLASSIFIED Service Oriented Architecture, Information Sharing and the FEA DRM 23 January 2006 Bryan Aucoin DNI CIO Chief Architect
DATABASE MANAGEMENT SYSTEM By: YAMINI TRIPATHI. INTRODUCTION Consists - Collection of interrelated data - Set of programs to access those data Definition.
Chapter 13 Review Questions Give a definition of architecture in an information systems context.
Chapter 10: Designing Databases Chapter 13 Systems Analysis and Design in a Changing World, 3 rd Edition.
All rights reserved © 2005, Alcatel Distributed Storage Networks Dr. Stephan Rupp
Chapter 1 : Introduction §Purpose of Database Systems §View of Data §Data Models §Data Definition Language §Data Manipulation Language §Transaction Management.
1 Communication in Distributed Systems REKs adaptation of Tanenbaums Distributed Systems Chapter 2.
ECS and LDAP Karen Krivaa Product Marketing Manager.
Lecture # 3 & 4 Chapter # 2 Database System Concepts and Architecture Muhammad Emran Database Systems 1.
1 Database Systems: Design, Implementation, and Management CHAPTER 10 Distributed Database Management System.
Tanenbaum & Van Steen, Distributed Systems: Principles and Paradigms, 2e, (c) 2007 Prentice-Hall, Inc. All rights reserved DISTRIBUTED SYSTEMS.
Introduction to UDDI From: OASIS, Introduction to UDDI: Important Features and Functional Concepts.
CP-a Emergency call stage 2 requirements - A presentation of the requirements from 3GPP TS Keith Drage.
Automatic Software Testing Tool for Computer Networks ADD Presentation Dudi Patimer Adi Shachar Yaniv Cohen
1 Active Directory Service in Windows 2000 Li Yang SID: November 2000.
©Silberschatz, Korth and Sudarshan1.1Database System Concepts Chapter 1: Introduction Purpose of Database Systems View of Data Data Models Data Definition.
1 Senn, Information Technology, 3 rd Edition © 2004 Pearson Prentice Hall James A. Senns Information Technology, 3 rd Edition Chapter 7 Enterprise Databases.
Faculty of Information Technology 31242/32549 Advanced Internet Programming Advanced Java Programming Web services Intro.
Presented to: By: Date: Federal Aviation Administration Registry/Repository in a SOA Environment SOA Brown Bag #5 SWIM Team March 9, 2011.
Vikram Thakur Introduction to Active Directory Structure.
Database Management System Lecture 2 Introduction to Database management.
The Directory A distributed database Distributed maintenance.
Przemysław Rek, Mirosław Kopeć, Zofia Gdaniec, Łukasz Popenda, Ryszard W. Adamiak, Marcin Wolski, Marcin Lawenda, Norbert Meyer, Maciej Stroiński.
INTRODUCTION TO DBS Database: a collection of data describing the activities of one or more related organizations DBMS: software designed to assist in.
1 Directory Services What is a Directory Service? Directory Services model Directory Services naming model X.500 and LDAP Implementations of.
Data Manipulation Jonathan Rosenberg dynamicsoft.
Week 1 Lecture MSCD 600 Database Architecture Samuel ConnSamuel Conn, Asst. Professor Suggestions for using the Lecture Slides.
1 Ontolog OOR Use Case Review Todd Schneider 1 April 2010 (v 1.2)
Oracle's Distributed Database Bora Yasa. Definition A Distributed Database is a set of databases stored on multiple computers at different locations and.
© 2004 IBM Corporation WS-ResourceFramework Service Groups Tom Maguire.
© 2017 SlidePlayer.com Inc. All rights reserved.