Longterm All IP Conference and IP2 AdHoc group - PowerPoint PPT Presentation

1 / 13
About This Presentation
Title:

Longterm All IP Conference and IP2 AdHoc group

Description:

6th ASTAP Forum 4-6 June 2002, Phuket, Thailand. 1 ... Seiko Epson Corporation, Sony Corporation, KYOCERA CORPORATION, Mitsubishi Electric Corporation, ... – PowerPoint PPT presentation

Number of Views:34
Avg rating:3.0/5.0
Slides: 14
Provided by: yabusakik
Category:

less

Transcript and Presenter's Notes

Title: Longterm All IP Conference and IP2 AdHoc group


1
Long-term All IP Conference and IP2 Ad-Hoc group
Activity of
Sixth APT Standardization Program (ASTAP)
Forum 4-6 June 2002, Phuket, Thailand
  • ARIB/TTC IP2 Ad-hoc Group

2
Background
  • Rapid growth of IT market in Japan
  • The explosion of IP based data traffic in Mobile
    Communication.
  • Improvement in the cost/performance of IP
    equipments (i.e., Router, Server)
  • Strong drive towards merging mobile systems with
    the Internet

Best solution for handling IP multimedia needed!
3
Objective
  • To clarify Long-term All-IP for beyond IMT-2000
  • Exchange views among ARIB-TTC members
  • Research status/trend of standardization/specific
    ation
  • in relevant global organizations/forums
  • Clarify standardization items from Japanese
    market viewpoint
  • Proposal for the global organizations/forums
    (according to their processes)

4
Scope and Subjects
Study Requirements for IP-based IMT
Platform (IP2)
(1) Analysis of Draft All-IP Related
Standards (2) Service/Platform Capabilities (3)
Architecture (4) Information Flows
5
Study Group Structure
ITU-T SSG
ITU-R WP8F
3GPPs, IETFs, etc.?
Long-term All IP Conference (2-3 times/year)
ARIB (Association of Radio Industries and
Businesses)
TTC (Telecommunication Technology Committee)
  • Reports of study status
  • Presentation of WD
  • Discussion on the way forward

Working Document
IP2 AdHoc (1-2 times/month)
Radio Experts
IT/NW Experts
6
IP2 Ad-hoc Group Members
Chairman Dr. Masami YABUSAKI (NTT
DoCoMo) Vice-chairman Mr. Kazuyoshi SATO
(Mitsubishi) Vice-chairman Dr. Masayoshi OHASHI
(KDDI)
Member Companies
NTT DoCoMo, Inc., KDDI CORPORATION, J-Phone Co.,
Ltd., Nippon Ericsson K.K. FUJITSU
LIMITED, Lucent Technologies Japan Ltd., NEC
Corporation, Nippon Motorola Ltd., NOKIA-JAPAN
CO,. LTD., NTT, OKI Electric Industry Co.,
Ltd., SHARP CORPORATION, Siemens K.K.
Toshiba Corporation, Seiko Epson
Corporation, Sony Corporation, KYOCERA
CORPORATION, Mitsubishi Electric
Corporation, CRL, NTC (NIPPON TELECOMMUNICATIONS
CONSULTING CO.,LTD.) , NTT SOFT, QUALCOMM
JAPAN, DENSO CORPORATION, Hitachi Ltd., NTT
Communication Corporation.
Matsushita Communication Industrial Co., LTD
7
Activity Progress
  • Review of All-IP relevant study and
    standardization
  • e.g. - All IP-NW study in 3G.IP and MWIF
  • - All IP-NW standardization in 3GPPs
  • - European Research Project Brain
  • - IP Mobility, Session Control, VoIP, Security
  • - OSA, Open API(Parlay)
  • (2) Activity to global standardization
  • - Report of ITU-T IMT SSG, ITU-R WP8F, IETF
    Plenaries
  • - Contribution to ITU-T IMT SSG (Rec. on NW
    vision)
  • - Contribution to 3GPP/3GPP2 Harmonization and
    WWRF
  • (3) Technical Discussion
  • - Requirements mainly on Mobility Management,
    Transport,
  • QoS, Service Management, etc.
  • - Working Document Update
  • - Discussion on Architecture started from March,
    2002

8
Annex
  • Contents of
  • Working Document
  • Architecture Document

9
Working Document Contents (1/2)
1. Introduction 2. Service Requirements
(KDDI) 3. Platform Capability Requirements (NTT
DoCoMo) 3.1 General Network Requirements
(NTC) 3.2 General Radio Requirements
(Mitsubishi) 3.3 General Terminal Requirements
(Panasonic) 3.4 Mobility (NEC) 3.5 Transport
(Motorola)
10
Working Document Contents (2/2)
3.6 Service Management (Fujitsu) 3.7 Addressing/Ro
uting (NTT) 3.8 QoS (NOKIA) 3.9 Session
Management (Hitachi) 3.10 Security
(Siemens) 3.11 Accounting/Billing/Charging
(Sharp) 4. Platform Architecture Scenarios
(NTTCom)
11
Architecture Document Contents (1/3)
1. Introduction 1.1 Purpose 1.2 Scope of
Document 1.3 Overview of Document 2. References 3.
Definitions and Abbreviations 4. Framework of
Architecture 4.1 Architecture Objectives 4.2 Guidi
ng Principles 5. Reference Model 5.1 Layered
Model 5.1.1 IP-Based Transport Layer 5.1.2 Control
Layer 5.1.3 Application Layer 5.2 Functional
Components 5.2.1 Basic Functional
Components 5.2.1.1 Mobility Management 5.2.1.2 Ses
sion Management 5.2.1.3 Resource
Management 5.2.1.4 QoS Management 5.2.1.5 Context
Management 5.2.1.6 Authentication and
Authorization 5.2.1.7 Directory
Management 5.2.1.8 Personal Data
Management 5.2.1.9 Media Conversion 5.2.1.10
Charging and Billing
12
Architecture Document Contents (2/3)
5.2.2 Enhanced Functional Components 5.2.2.1 Basic
Signalling Management 5.2.2.2 Contents
Distribution 5.3 Interactions 6. Functional
Distribution and Entities 6.1 Overview of
Functional Distribution 6.2 Description of
Functional Entities in IP-Based Transport
Layer 6.2.1 Router 6.2.2 Access Router
(AR) 6.2.3 Access Point (AP) 6.2.4 Mobile
Node 6.2.5 Anchor Point Router (APR) 6.2.6 Configu
ration Manager 6.2.7 Media Gateway
(MGW) 6.3 Description of Functional Entities in
Control Layer 6.3.1 Entities for Basic Functional
Components 6.3.1.1 Global Mobility Manager
(GMM) 6.3.1.2 Local Mobility Manager
(LMM) 6.3.1.3 Session Manager 6.3.1.4 Radio
Resource Manager (RRM) 6.3.1.5 Network Resource
Map 6.3.1.6 QoS Manager 6.3.1.7 QoS
Broker 6.3.1.8 Context Manager
13
Architecture Document Contents (3/3)
  • 6.3.1.9 Authentication and Authorization (AA)
    Server
  • 6.3.1.10 Directory Manager
  • 6.3.1.11 Profile Database
  • 6.3.1.12 Media Conversion
  • 6.3.1.13 Charging/Billing Manager
  • 6.3.2 Entities for Enhanced Functional
    Components
  • 6.3.2.1 Basic Signalling Manager
  • 6.3.2.2 Multicast Manager
  • Interfaces and Reference Points
  • Appendix (to the IP2 Architecture Working
    Document)
  • A.1 Major open issues
  • A.2 Preliminary draft text on Interfaces and
    reference points
  • A.3 Domain Root Router (DRR) and assumed mobility
    management mechanism
  • A.4 Two possible principles of RRM architecture
    for multi-access
  • A.5 Network resource manager
Write a Comment
User Comments (0)
About PowerShow.com