Presentation

11 downloads 71035 Views 90KB Size Report
Raj Pandya. Chairman, ITU-T WP3/11. (Signaling Requirements for Mobility Services). Contributions: GSC(99)-15/RAST(99)-37. GSC5/RAST8, Williamsburg  ...
Progress and Plans for IMT-2000 Standardization in ITU-T Raj Pandya Chairman, ITU-T WP3/11 (Signaling Requirements for Mobility Services)

Contributions: GSC(99)-15/RAST(99)-37

GSC5/RAST8, Williamsburg, August 23-26, 1999

Pandya: ##

IMT-2000: ITU Standardization Activity

IMT-2000 Standardization

Radio Communications

ITU-R

ITU-T

Telecom. Standards Lead SG on IMT-2000

Terrestrial Mobile

IMT-2000 Radio Aspects

SG8

TG8/1 Chairman: M. Callendar

SG11

Signaling & Protocols

WP3/11 IMTT-2000 Signaling Requirements Chairman: R. Pandya

Other IMT-2000 Activities in ITU-T • Services (SG2) • Numbering & Identities (SG2) • OAM (SG4) • Security (SG7) • Interworking (SG13) • Speech & Video coding (SG16)

GSC5/RAST8, Williamsburg, August 23-26, 1999

Pandya: ##

1

ITU-T SG11 Structure forIMT-2000 standards

Study Group11

ITU-R and External fora

IMT-2000 Program Manager

WPs of SG11 and other ITU-T SGs

R. Pandya JQGs*

WP3/11 IMT-2000 Signaling Requirements

IMT-2000 Protocol Choices

Functional Architecture Radio Interface Network Interface

Radio Interface (L2) Service Control Mobility Management Call/Bearer Control

Protocol Groups

Management (with SG4) Security (with SG7)

* JQG: Joint Question Groups

IMT-2000 Interface & Protocol Specifications

GSC5/RAST8, Williamsburg, August 23-26, 1999

Pandya: ##

Recent Developments

Joint Experts Meeting of TG8/1 and SG11 (Beijing) - Agreements • IMT.RSPC to reference 3GPP/SDO Specifications on RTTs • SG11 will develop a common mechanism for IMT-2000 Terminals to recognize radio and network operating environments • SG11 (with SG4 & SG7) will review radio technology independent parts of RTT specifications related to signaling, management, & security. • Request inputs from 3GPPs/SDOs on RTTs requested by September 1 (Annex 1) • Target completion for Common NNI for interworking of family system networks agreed for year-end 2000.

GSC5/RAST8, Williamsburg, August 23-26, 1999

Pandya: ##

2

Key Deliverables - continued Studies/Recommendations targeted for completion in 1999 Review of radio-independent part of RTTs to be included in IMT-RSPC - SG11 - technical assessment of radio-independent aspects of layer 2 and layer 3 RTT specs Common mechanism for a terminal to select radio and/or network environment - SG11 - required terminal capability for roaming across different ‘family member’ networks Q.1721: Information Flows for IMT-2000 (Stage 2 service description)-SG11 - will form the basis for signaling protocols and interface specifications for common NNI - includes IFs, IEs, FEAs etc. for support of Packet data and inter-working with Internet Q.1731-2: Signaling Requirements for Radio Interface - Layer 2 - SG11 - radio-independent services and functions for Layer 2 of the radio interface Q.1741: Functional Specs. and Requirements for IMT-2000 UIM - SG11 - requirements for the design of IMT-2000 UIM and UIM-MT interface GSC5/RAST8, Williamsburg, August 23-26, 1999

Pandya: ##

Key Deliverables - continued Studies/Recommendations targeted for completion in 1999 Review of radio-independent part of RTTs to be included in IMT-RSPC - SG11 - technical assessment of radio-independent aspects of layer 2 and layer 3 RTT specs Common mechanism for a terminal to select radio and/or network environment - SG11 - required terminal capability for roaming across different ‘family member’ networks Q.1721: Information Flows for IMT-2000 (Stage 2 service description)-SG11 - will form the basis for signaling protocols and interface specifications for common NNI - includes IFs, IEs, FEAs etc. for support of Packet data and inter-working with Internet Q.1731-2: Signaling Requirements for Radio Interface - Layer 2 - SG11 - radio-independent services and functions for Layer 2 of the radio interface Q.1741: Functional Specs. and Requirements for IMT-2000 UIM - SG11 - requirements for the design of IMT-2000 UIM and UIM-MT interface GSC5/RAST8, Williamsburg, August 23-26, 1999

Pandya: ##

3

IMT-2000 and Global Roaming: Potential Areas for collaboration

GSC5/RAST8, Williamsburg, August 23-26, 1999

Pandya: ##

IMT-2000: Emerging View

• Multiple Frequency Bands (2G use of IMT-2000 band) • Multiple Radio Technologies (IMT.RSPC - ITU-R) • Multiple Core Networks (Q.1701 - ITU-T)

Multi-band/Multi-mode Terminals roaming between Family Member Networks supporting different access & network protocols GSC5/RAST8, Williamsburg, August 23-26, 1999

Pandya: ##

4

IMT-2000: Global Roaming

Key Requirements • Roaming Terminal should be able to operate in the visited network Need a common mechanism(protocol) to allow the terminal to recognize the Radio and Network environment (of visited system)

• Visited Network should be able to inter-operate with the Home Network Need an interworking mechanism (protocol) for different family system networks to communicate with each other

GSC5/RAST8, Williamsburg, August 23-26, 1999

Pandya: ##

Network Interworking Options

• Interworking using bi-lateral IWFs (3GPPs/SDOs) • Interworking using a Common NNI (ITU-T + 3GPPs/SDOs) • Unified Networks: Single networking prtotocol (ITU-T + ) Unified Networks Common NNI Bilateral IWF

near-term

medium-term

GSC5/RAST8, Williamsburg, August 23-26, 1999

long-term Pandya: ##

5

Network Interworking Option 1 Interworking using bi-lateral IWFs • An ad-hoc solution for early implementation • Inefficien if more than 2 family systems: n(n-1)/2 IWFs required • Change in one NP invokes changes in all interconnected networks

NP-A

A

B

IWF

IWF

NP-C

NP-B

IWF

C

GSC5/RAST8, Williamsburg, August 23-26, 1999

Pandya: ##

Network Interworking Option 2 Interworking using a Common NNI • Family-specific IWFs to Common NNI • Efficient: one IWF design per Family • Change in one NP/IWF does not affect other IWFs • More future-proof (can accomodate new family members)

C

NP-C

IWF

NP-A

A

IWF

GSC5/RAST8, Williamsburg, August 23-26, 1999

Common NNI

IWF

B

NP-B

Pandya: ##

6

Common NNI: Proposed Protocol Suite

Common NNI • Call/Bearer Control- Circuit: N-ISUP/B-ISUP • Bearer/Network Layer - Packet: ATM AAL5/IP • Service Control: ITU-T INAP + mobility extensions - functional commonality with WIN & CAMEL • Mobiliity Management: New Protocol -functional commonality with GSM and IS-41 MAPs - ITU-T TCAP transport GSC5/RAST8, Williamsburg, August 23-26, 1999

Pandya: ##

Global Roaming: Proposed Way Forward

Task

Collaborative Approach

• Mechanism for terminals to recognize operating radio & network environments

• ITU-T/R in close collaboration with 3GPPs and appropriate SDOs

• Interworking between GSM and ANSI-41 networking protocols for early implementations

• Collaboration between 3GPPs and appropriate SDOs

• Common NNI protocol suite for interworking of current and future IMT-2000 family systems

• ITU-T in close collaboration with 3GPPs and appropriate SDOs

• Initial studies towards a ‘Unified Network’ to support evolving telecommunication services

• ITU-T with inputs from 3GPPs and appropriate SDOs

GSC5/RAST8, Williamsburg, August 23-26, 1999

Pandya: ##

7

Future Directions and Plans

- Consolidation of IMT-2000 network-related standardization work in a single group - Maintaining ITU’s role as the pre-eminent forum for international standards - Continued collaboration with relevant external forums to meet industry needs - Increased focus on support of high speed data, Internet and multimedia services - Developing architectures and protocols for unified (wireless/wireline), IP-centric networks;

collaborate! - collaborate! - collaborate! www.itu.int/imt/ GSC5/RAST8, Williamsburg, August 23-26, 1999

Pandya: ##

8