Document type: PowerPoint file Meeting name: The 15th CJK NGN WG meeting SDO name: CCSA Author name: Hui Min E-mail: huimin@chinamobile.com Telephone number: 13910633714

Status of Multi-connection (Q9)

3

Content

Q9 scope Work plan of Q9 Planned contributions in next meeting Members and Observers Open issues for discussion

Scope

Tasks include, but are not limited to: Identify and study enhancements to existing Recommendations related to

service requirements for the harmonization of multiple connections for multiple access technologies.

Develop high-level network architecture enhancements to support the harmonization of multiple connections for multiple access technologies.

Develop information flow between different layers needed to be delivered to meet the requirements of multiple connections to support its services in the realm of heterogeneous accesses.

Some key issues of multi-connection

Multi-connection means UE keeps more than one network connections simultaneously. Different types of network connections may provide users with different user experiences, such as broad bandwidth, low time delay, and high security. The main purpose of multi-connection is to federate all means of access technologies in order to access the network ubiquitously (from everywhere and at any time), benefit from different advantages of multiple access technologies, and help us to provide better user experience.

5

Content

Q9 scope Work plan of Q9 Planned contributions in next meeting Members and Observers Open issues for discussion

Work plan

Doc No%

CompleteTarget

dateEditors

Y.MC-SCEN 20 2009-09 Qin Wu (Huawei, China)Hui Min (China Mobile, China)Yong-Geun Hong (ETRI, Korea)

Y.MC-REQ 20 2010-01 Hui Min (China Mobile, China)

Y.MC-ARCH

10 2010-09 Hui Min (China Mobile, China)

Introduction of current documents

Y.MC-SCEN This Supplement describes the scenarios of multi-connections architecture for NGN,

which deals with the multi-connection use cases and considerations within different layers in the NGN.

This Supplement addresses routing consideration, service division and combination consideration, QoS consideration and security consideration for multi-connection together with cross layer interaction consideration between different layers to better user experience and facilitate utilization of network resource, load balance and reliability of connections.

Y.MC-REQ This Recommendation provides brief descriptions of Requirement of Multi-

connection in terms of the overall requirements and a high-level overview of the functional features to be addressed. The descriptions are from the aspects of service requirement, capabilities requirement, functional requirement, and other technology requirement.

To describe multi-connection requirements in terms of the overall requirements and a high-level overview of the functional features

To list key technology issues relevant to multi-connection Y.MC-ARCH

This Recommendation describes the architecture of multi-connection in terms of the overall functional requirements and a high-level overview of multi-connection framework to be addressed.

To develop the architecture and definition of functional entities (FEs) and allocation of functional capabilities to FEs

To address the relationship between multi-connection architecture and NGN FRA

8

Content

Q9 scope Work plan of Q9 Planned contributions in next meeting Members and Observers Open issues for discussion

Planned contributions in Y.MC-SCEN

Draft Supplement “Multi-Connection Scenario in NGN” 6 Generic Scenarios of Multi-

connection Detailed description

7 Multi-connection use cases To be extended and modified

Planned contributions in Y.MC-REQ

Draft Recommendation “Multi-connection Requirement in NGN” 6 Multi-connection requirement

6.1 Application layer requirement Access selection function for the application

6.2 Session control layer requirement 6.3 Access control layer requirement

Routing filter function 6.4 Access layer requirement 6.5 Technology requirement

To be extended

Y.MC-ARCH Draft Recommendation “Multi-

connection Architecture in NGN” 6 Multi-connection architecture

6.1 Overall architecture 6.2 Access network 6.3 Access control 6.4 Session control 6.5 Application layer

7 Mapping to NGN To be improved in the future meeting

12

Content

Q9 scope Work plan of Q9 Planned contributions in next meeting Members and Observers Open issues for discussion

Members and observers

China Mobile Huawei ZTE ETRI Alcatel Shanghai Bell

14

Content

Q9 scope Work plan of Q9 Planned contributions in next meeting Members and Observers Open issues for discussion

The evolution of network model

GW 1

LAN

INTERNET

GW 2

GW

INTERNET

Server

The initial internet is designed for one interface of each host

In the current multi-connection environment, the old internet model is not suitable anymore.

1. The host with multiple network interfaces should be capable to connect with different networks simultaneously.

2. The policies to assign different flows to the appropriate interface are required, and how to apply the policies to the host need to be considered as well.

3. Network side should be capable of distributing the IP flow according to some parameters, such as IP address prefix, network type and so on.

Requirements

Specific Scenario

GW

INTERNET

INTRANET

Operator Network

GW

GW

GW

Corporation Email

P2P download

Video communication

Ether

net

WiFi

3GPP Access

Interaction among different networks

terminal Access network Access control & session control

application

MME

SGW

PDN GW

GWAP

eNode B

Application Server

Service Platform

GGSNSGSNNodeB RNC Service Platform

eNode BeNode B

3G

LTE

WiF

i

AP

AP

Thanks！