Presentation on theme: "22-23 June 2004TISPAN-3GPP Workshop - Sophia-Antipolis 1 TISPAN NGN Architecture Overview Richard Brennan pulver.com, WG2 Chair"— Presentation transcript:
22-23 June 2004TISPAN-3GPP Workshop - Sophia-Antipolis 1 TISPAN NGN Architecture Overview Richard Brennan pulver.com, WG2 Chair firstname.lastname@example.org email@example.com Prepared with Bruno Chatras - France Télécom Leonardo Finizola e Silva - Alcatel Adrianus Van ewijk - Alcatel
30-31 March 2005TISPAN-3GPP Workshop - Washington 2 Agenda 1.Approval of agenda and Documents 2.Workshop objectives 3.NGN (Release 1) Architecture status 4.IMS Architecture and R6 & R7 status 5.Review of the NGN-IMS issues & status 6.Fixed Access to IMS issues/discussion 7.Backbone issues/Interco schemes 8.Session Border Controllers concept 9.Current activities and work plan 10.Next steps/Future cooperation 11.Any other issue 12.Wrap-up/closure
30-31 March 2005TISPAN-3GPP Workshop - Washington 3 Overall Architecture: WI 02007 Service / Transport layer separation in line with ITU-T Y.2011!
30-31 March 2005TISPAN-3GPP Workshop - Washington 4 3GPP R6 and TISPAN R1 NGN: R6 Architectural comparison Network Attachment 3GPP:GPRS entities + HLR (PS part) TISPAN: NASS entities Resource Control 3GPP: PDF and GGSN TISPAN: RACS entities + RCEF and BGF entities MM Session Control 3GPP:IMS (R6) TISPAN (R1)IMS (R6)
30-31 March 2005TISPAN-3GPP Workshop - Washington 5 Architecture Design A sub-system oriented approach, enabling: The addition of new subsystems over the time to cover new demands and service classes. To import (and adapt) subsystems from other standardisation bodies. Flexibility to adjust a subsystem architecture with no or limited impact on other subsystems. IP connectivity is provided using two subsystems: Network Attachment SubSystem (NASS) – WI 02021 Resource and Admission Control Subsystem (RACS) – WI 02020 First service-oriented subsystems include the 3GPP IMS (suitably adapted to the fixed BB access context) – WI 02029 a PSTN/ISDN Emulation Subsystem (PES) – WI 02019 and 02030. Future service-oriented subsystems may include A streaming subsystem A TV Broadcasting subsystem Others as determined DES/02007 has been Working Group approved at TISPAN#5bis
30-31 March 2005TISPAN-3GPP Workshop - Washington 6 TISPAN Architecture – DSL case
30-31 March 2005TISPAN-3GPP Workshop - Washington 7 TISPAN NGN Common Components Roughly equivalent to the HSS (excluding the HLR)
30-31 March 2005TISPAN-3GPP Workshop - Washington 8 Transfer Functions Access NetworkCore Network
30-31 March 2005TISPAN-3GPP Workshop - Washington 9 Focus on the IMS subsystem
30-31 March 2005TISPAN-3GPP Workshop - Washington 10 IMS Architecture in the NGN setting Network Interconnections
30-31 March 2005TISPAN-3GPP Workshop - Washington 11 NGN Impact on IMS Architecture Almost no impact on the IMS functional architecture as such. The IMS architecture is already largely access independent! ETSI TISPAN variant of the IMS is described in WI 02029 Main impacts are on detailed procedures implemented by some of the functional entities (WI 02028), e.g. P-CSCF procedures have to be augmented with ALG-like capabilities for supporting interactions with NAPT-(PT). Location information has to be inserted in SIP messages by the P-CSCF. and on IMS SIP profile (WI 03019). Specific functionalities for supporting IP interconnection are located outside the IMS component.
30-31 March 2005TISPAN-3GPP Workshop - Washington 12 Focus on NASS
30-31 March 2005TISPAN-3GPP Workshop - Washington 13 Network Attachment Subsystem (NASS) - Scope Dynamic provision of IP address and other user equipment configuration parameters (e.g. using DHCP) User authentication, prior or during the IP address allocation procedure Authorization of network access based on user network profile Access network configuration, based on user profile Location management (e.g. for emergency call, …) CPE configuration Support for nomadicity and roaming: NASS can be distributed between a visited and home network
30-31 March 2005TISPAN-3GPP Workshop - Washington 14 NASS architecture Access Management Function (AMF): translates network access signalling between CPE and NACF/UAAF Network Address Configuration Function (NACF): IP address allocation and distribution of other network configuration parameters such as address of DNS server(s), address of signalling proxies for specific protocols Customer Premises Equipment Control Function (CPECF): provides configuration information beyond what is already provided by the NACF. Connectivity Session Location Repository Function (CLF): registers association between the IP configuration, access line specific info and user network profile. Provides mapping info to RACS. Provides location information to TISPAN NGN core subsystems User Access Authorization Function (UAAF): performs user authentication, as well as authorisation checking, based on user profiles, for network access. Profile Database (PDBF): store user network profile TE+CNG = CPE (customer premises equipment)
30-31 March 2005TISPAN-3GPP Workshop - Washington 15 Focus on RACS
30-31 March 2005TISPAN-3GPP Workshop - Washington 16 RACS scope Service Based Local Policy Control: authorisation of QoS requests and definition of the polices to be enforced by the bearer service network elements. Support for Application Function (AF)-initiated AND CPE- initiated resource reservation requests QoS support over multiple access networks (e.g. ADSL and GPRS) and CPE types. Admission Control: Apply admission control to resource reservation requests Based on knowledge of transport resource availability over the “last-mile access” and aggregation segments of the access network NAPT/ Gate Control: controls near-end and far-end NAPT and FW functions, when required, between: two core TISPAN NGN networks or, at the border between core and access TISPAN NGN networks RACS offers services to Application Functions (AF) that may reside in different administrative domains.
30-31 March 2005TISPAN-3GPP Workshop - Washington 17 RACS SPDF - Provides to AF a single point of contact - Authorization decision for QoS resource. BGF - Located at the border of networks (access/core – core/core) - NAPT, Gate Control, packet marking, usage metering, traffic policing RCEF - Located in the access network - gate control, packet marking, policing. A-RACF - Located in the access network - resource reservation and admission control
30-31 March 2005TISPAN-3GPP Workshop - Washington 18 Questions?