Common IMS Management CIMS-080020 3GPP/3GPP2 Common IMS Workshop Puerto Vallarta, Mexico, 24-25 January 2008 Source: 3GPP2 Document for: Discussion Agenda.

Slides:



Advertisements
Similar presentations
Information Document 18-E ITU-T Study Group 2 May 2002 QUESTION:Q.1/2 SOURCE:TSB TITLE:UNIVERSAL COMMUNICATIONS IDENTIFIER (UCI) (by Mike Pluke, ETSI)
Advertisements

IETF ECRIT SDO Emergency Services Coordination Workshop 5 & 6 Oct 2006 – New York Alain Van Gaever DG Information Society & Media European Commission.
World Class Standards TISPAN NGN OSS Service Interfaces (NOSI) TISPAN WG8 – 3GPP SA#5 Joint meeting Sophia Antipolis, May14th - 15 th Source: Geoff.
Towards a harmonised Tispan Subscription model TISPAN WG8 – 3GPP SA#5 Joint meeting Sophia Antipolis, May14th - 15 th Source: Steve Orobec BT.
1 Analysis of NGMN Requirements REQ 6: Substitution of Monitoring Probes by Infrastructure Inherent Trace Functionality.
Interworking Architecture Between 3GPP and WLAN Systems 張憲忠, 何建民, 黃瑞銘, 紀嘉雄, 李有傑.
22-23 June 2004TISPAN-3GPP Workshop - Sophia-Antipolis 1 Joint 3GPP & TISPAN Workshop on NGN-IMS - NGN-IMS issues handling - Alain Le Roux (France Telecom),
30-31 March 2005 Workshop "IMS over Fixed Access" - Washington 1 TISPAN_NGN Project plan Martin Niekus Alain Sultan
1 TSG-SA WG5 ( Telecom Management) Status Report Agenda Item:7.5 Document for:Information Technical Specification Group Services and System Aspects SP
1 Analysis of NGMN Requirements REQ 10: Automatic Inventory.
Mechanism to support establishment of charging policies Group Name: WG2-ARC Source: InterDigital Meeting Date: TP8 Agenda Item:
1 Nick Yamasaki Chair, TSG-S 04 December 2008 Review of TSG-S Activities in 2008.
3GPP ”All-IP” vision Long and short term What do we want to obtain ? How to get there (phasing) ? What do 3GPP need to do ? Issues to be resolved.
ISSAI 4300 Compliance Audit in the Context of Courts of Accounts 11th Meeting of the INTOSAI Compliance Audit Subcommittee September 2013.
GSC-19 Meeting, July 2015, Geneva 3GPP and The Road to 5G Erik Guttman, 3GPP SA Chairman, Consultant to Samsung Electronics Co., Ltd. Document No:GSC-19_302.
World Class Standards WG8 presentation of current Subscription Management Activities TISPAN WG8 – 3GPP SA#5 Joint meeting Sophia Antipolis, May14th - 15.
World Class Standards Co-op on Information Models- NRM TISPAN WG8 – 3GPP SA#5 Joint meeting Sophia Antipolis, May14th - 15 th Source: Geoff Caryer.
1 An Analysis of 3GPP and 3GPP2 Requirements for Common IMS January 2008 Source:Aleksandar M. Gogic, Chair TSG-S WG-1.
International Telecommunication Union NGN Management Focus Group 13 September 2005 List of Candidate Specifications for NGN Management Dave Sidor NGNMFG.
World Class Standards WG8 Specification Guidelines TISPAN WG8 – 3GPP SA#5 Joint meeting Sophia Antipolis, May14 th - 15 th 2007 Source: Michael Geipl Deutsche.
1 Summary of TSG-S Femto Related Activities Nick Yamasaki (KDDI) - Chair New Orleans, LA, USA March 31, 2009.
TSG-S PMT Work Program & Status 3GPP2 Evolution Workshop Nick Yamasaki, Chair TSG-S June 27-28, 2005.
Presentation Overview
INTRODUCTION. 1.1 Why the Internet Protocol Multimedia Subsystem 1.2 Where did it come from?
Page 1 January 16, 2008 Source: 3GPP2 TSG-S WG4 (Security) Contacts: Anand Palanigounder, Chair, TSG-S WG4 ( Zhibi Wang,
3GPP2 Vision: System Release 6 & 7 Jane Brownley Chair, Vision Ad Hoc 1.
1 17 February 2009 Subject:Draft Presentation for Femto Conference, March 2009 Date: 17 February 2009 Source: Airvana Contact: Doug Knisely
All-IP Access Network Issues 1 TSG-A/3GPP2 All IP Access Network Issues -- TSG-A View -- February
Doc.: IEEE /209r0 Submission 1 March GPP SA2Slide 1 3GPP System – WLAN Interworking Principles and Status From 3GPP SA2 Presented.
3GPP2 Charging Betsy Kidwell Chair, 3GPP2 TSG-X Lucent Technologies OMA-MCC Bangkok, Thailand June 2004.
MCC 3GPP Work program Database Ian Doig, MCC. 3GPP Work program Database Request by Partner Organisations for a common 3G Work program Database. Based.
1 3GPP2 IMS Charging Infrastructure Presented for 3GPP2 TSG-X by Nick Mazzarella of Lucent Technologies September 25, 2004.
NGN Management Focus Group (December 2004) - 0 3GPP TS Flow-based charging requirements Title: 3GPP Overall high level functionality and architecture.
World Class Standards SuM Functional Architecture SuM NGN OSS Service Interfaces (NOSIs) TISPAN WG8 – 3GPP SA#5 Joint meeting Sophia Antipolis, May14th.
3GPP2 Specification Development David Crowe cdma2000 Technology Workshop June 14, 2012 – Guangzhou, China Draft Version 0.1.
Machine-to-Machine(M2M) Communication for cdma2000 Systems Orlett W. Pearson, 3GPP2 Liaison Report to TR-50 August 2012.
ITU-T Workshop “Telecommunication Management and Operations Support Systems“ Beijing, China, May 2006 International Telecommunication Union ITU-T.
Page 1TTT - May 12, GPP IMS Standardization Update Bell Labs Innovations Lucent Technologies Room 9C Lucent Ln. Naperville, IL E Mail.
Diameter SIP Application
3GPP-3GPP2 Workshop CIMS Puerto Vallarta, MEXICO, 24th – 25th January 2008 Source:Motorola Title: Title:Comparison of 3GPP2 SBBC and 3GPP PCC Agenda.
3GPP2 Restructuring Source: TSG-A Chairman; Xiaowu Zhao TSG-C Chairman; Ed Tiedemann TSG-S Chairman; Nick Yamasaki TSG-X Chairman; Marvin Bienn Copyright.
TSG-S Comments to TSG Chairs Regarding Proposed 3GPP2 Restructure Nick Yamasaki Chair, 3GPP2 TSG-S
Public Health Reporting Initiative July 25, 2012.
Plans for Femto Management 3GPP2 TSG-S WG2 Plans for Femto Management Randall J. Scheer (Co-chair)
3GPP2 TSG-SX Structure & Working Procedure Source: TSG-SX Chairman: Xiaowu(Frankle) Zhao TSG-SX Vice-Chair: Yuezhen Wang/Mike Dolan, Copyright Notice 3GPP2.
0 3GPP-3GPP2 Workshop CIMS Puerto Vallarta, MEXICO, 24th – 25th January 2008 Source:3GPP2 Title:Common IMS - Discussion Agenda item:3 Document for:INFORMATION.
1 Subject:Draft Responses to BBF Comments re. cdma2000 MO Preview Date: 25 January 2010 Source: Doug Knisely TSG-X FMOAHG Co-chair, BBF Liaison Contact:
22-23 June 2004TISPAN-3GPP Workshop - Sophia-Antipolis 1 Joint 3GPP & TISPAN Workshop on NGN-IMS - Objectives - Alain Le Roux (France Telecom), TISPAN.
TSG-S OMA (Open Mobile Alliance) Ad-Hoc Report Richard Robinson Chair - 3GPP2 TSG-S SC D.
3GPP TSG RAN WG2 meeting #92 Nanjing, China 23-27, May 2016 R
30-31 March 2005Workshop "IMS over Fixed Access" - Washington 1 Joint 3GPP & TISPAN Workshop on NGN-IMS - Objectives - Alain Le Roux (France Telecom),
Doc.: IEEE /1060r1 Submission September 2013 S. Rayment, Ericsson & S. McCann, BlackBerrySlide 1 3GPP Liaison Report Date: Authors:
BSA 385 Week 4 Individual Assignment Frequent Shopper Program Part 3 For the items specified in the technical architecture document developed for the Frequent.
Kenjiro Arai NTT ITU Workshop on “Voice and Video over LTE” Geneva, Switzerland, 1 December 2015 NNI standards for IMS inter-connection.
ETSI–3GPP NGN ACTIVITIES
ETSI–3GPP NGN ACTIVITIES
3GPP SA5 Inputs for NFV Information Modelling Workshop
3GPP interworking in R3 Group Name: ARC
Teleconference Agenda
ITU-R Ad-Hoc Contact person
Location Based Services support
3GPP Status.
Behavioral goal specialization
Security Working Group
3GPP Update/Status (Release 15 – June 2018)
IMT-2020/5G SC Proposal Date: Authors: July 2016
ETSI–3GPP NGN ACTIVITIES
ESHAC #8 Safety Readiness Review Thomas Hansson, ESH
3GPP Liaison Report Date: Authors: January 2013
Presentation transcript:

Common IMS Management CIMS GPP/3GPP2 Common IMS Workshop Puerto Vallarta, Mexico, January 2008 Source: 3GPP2 Document for: Discussion Agenda Item: 4.4

1 3GPP and 3GPP2 IMS Management Harmonization The management of 3GPP and 3GPP2-based IMS networks are harmonized at two levels: –Interfaces –Models and Network Element Specific Data

2 Interfaces The 3GPP SA5 32-series of specifications are reused in 3GPP2 TSG-S WG5 and 3GPP2 TSG-X WG3 (charging) specifications, whenever appropriate. The concepts of Integration Reference Points (IRPs) and Itf-N interfaces are shared between 3GPP and 3GPP2. –Typically, this means that the management interfaces are common between 3GPP and 3GPP2 (e.g., common alarm interfaces, common provisioning interfaces, common performance management interfaces, common charging interfaces, etc.) –but the network element specific information are not common (e.g., different Network Resource Models (NRMs), different performance measurements, different Call Detail Records (CDRs), etc.). For non-charging management interfaces, the 3GPP2 S.S C (and 3GPP2 S.S D) specifications describe any additions or exclusions from the 3GPP SA5 Release 6 (and Release 7) specifications. For charging, the additions or exclusions are described in the 3GPP2 X.S A and 3GPP2 X.S A specifications

3 Models and Network Element Specific Data For IMS models and network element specific data, much of the data is common between 3GPP and 3GPP2 when there is commonality between the 3GPP and 3GPP2 architectures. –As an example, 3GPP SA5 and 3GPP2 TSG-S WG5 share a common underlying object model (called the Generic NRM, 3GPP R ) that all object models are built upon. In Release 7, 3GPP and 3GPP2 will also share common IMS object model specifications (3GPP R , , and ). These specifications (and the corresponding 3GPP2 specifications), will specify both 3GPP and 3GPP2 shared objects and 3GPP or 3GPP2-specific objects (where there are architecture differences, such as unique interfaces between IMS and the 3GPP and 3GPP2 Radio Access Networks).

4 Management Issues With Moving Toward Common IMS The management issues with moving toward the 3GPP and 3GPP2-based Common IMS networks are relative to: –Architecture Specifications –Management Specifications

5 Architecture Specifications 3GPP architecture needs to clearly designate Common IMS network elements and reference points between Common IMS network elements: –Reference points between Common IMS network elements and 3GPP-specific networks or 3GPP2-specific networks need to be the responsibility of other 3GPP / 3GPP2 specifications (or clearly designated as not part of Common IMS)

6 Management Specifications 3GPP SA5 needs to separate Common IMS performance measurements for interfaces between Common IMS network elements from those on interfaces to non- Common IMS network elements: –Similarly, 3GPP 32.72X series should only reflect Common IMS models and not interfaces between Common IMS network elements and other 3GPP networks (or clearly designate these other modeled interfaces as 3GPP-specific) –3GPP2 TSG-S WG5 will be responsible for modeling interfaces between Common IMS network elements and other 3GPP2 networks, 3GPP SA5 for interfaces to other 3GPP networks. –Similar comments with Common IMS call trace