Question(s): Meeting, date: Study Group: Working Party:

advertisement
Question(s):
Study Group:
2 & 5/19 and 6/13
Meeting, date:
Working Party:
Melbourne, Australia 1 - 3 March 2005
Intended type of document (R-C-D-TD): TD 14r1
Source:
Rapporteur of Q.2/19, Q.6/13 and Editor of Q.5/19
Title:
Meeting Report
Table of Contents
1
Organization of Meeting ............................................................................................... 2
1.1
Meeting Identification and Participation ........................................................ 2
1.2
Terms of Reference ........................................................................................ 2
1.3
Meeting agenda .............................................................................................. 2
2
Key Results ................................................................................................................... 2
2.1
Work Items Progressed .................................................................................. 2
3
Meeting Documentation ............................................................................................... 2
4
Liaison Statements ........................................................................................................ 2
5
Detailed report of discussions....................................................................................... 2
5.1
Review of Meeting Report. ............................................................................ 5
6
Acknowledgements ...................................................................................................... 5
Annex 1 – Meeting agenda ...................................................................................................... 6
Annex 2 – Work Plan............................................................................................................... 7
Annex 3 – List of documents ................................................................................................... 8
Annex 4 – List of Participants ................................................................................................. 9
Annex 5 – TD 12 Discussion Tree Diagram ............................................................................ 10
Attention: This is a document submitted to the work of ITU-T and as such is intended for use by the Member States of ITU, by ITUT Sector Members and Associates, and their respective staff and collaborators in their ITU-related work. It is made publicly available
for information purposes but shall not be redistributed without the prior written consent of ITU. Copyright on this document is owned
by the author, unless otherwise mentioned. This document is not an ITU-T Recommendation, an ITU publication, or part thereof.
-2TD 14r1
1
Organization of Meeting
1.1
Meeting Identification and Participation
This is the report of a meeting of joint Rapporteur meeting of Q.2/19, Q.5/19, and Q.6/13
meeting in Melbourne, Australia 1 - 3 March 2005. The meeting was attended by about 11
delegates from 7 countries.
The list of participants is provided in Annex 4.
1.2
Terms of Reference
The Terms of References for this meeting as agreed in SG 19 and SG 13 closing plenaries in
December 2004:
Progress Mobility Management including in the context of FMC in conjunction with
Q.6/13.
1.3
Meeting agenda
The draft Meeting Agenda was published in Temporary Document 01. It was revised and
approved as TD 01r1 and is reproduced in Annex 1 of this Report.
2
Key Results
2.1
Work Items Progressed

Mobility Management Terms were discussed in details and several Terms were
harmonized across Questions from various ITU-T SGs.
(Additional results are included in the version behind TIES.)
3
Meeting Documentation
Documents considered at this meeting are listed in Annex 3. All documents are available at
http://ties.itu.int/u/tsg19/sg19/xchange/q2/0503Melbourne/.
4
Liaison Statements
The meeting resulted in the preparation and approval of Liaison Statements as summarized in
Table 1.
Table 1 – Outgoing Liaison Statements
Addressee
ITU-T SG13
5
Document
number
TD 13
<body>
Question
Q.2/19,
Q.5/19,
Q.6/13
For
Title/ Subject
information Reply to the LS on Project
coordination and release planning for
NGN
Detailed report of discussions
TDs 06 and 07 are to be kept behind TIES at the authors request.
-3TD 14r1

TD 01 – Agenda and Work Plan.
Approved as TDr1.

TD 02 – Project co-ordination and release planning for NGN
Noted.
SG 13 to manage/coordinate but should take advantage of expertise in all SGs.
Concern with time schedule.
Any release that does not include clear implementation plans (e.g., Stage 3) by
the vendors may not be justified.
We should not duplicate the work of SDOs.
The reply from SG 19 should include our mandate and references to
Q.1741/1742.
Operators are very interested in FMC.
What does “an interactive ITU-T Web site” mean?
An LS reply is drafted in TD 14.

TD 03 - Some relative documents from the latest SG13 and NGN-FG meeting
This is a compilation of MM related documents from SG 13 and NGN-FG. The
group used this TD and relevant contributions and email exchanges to agree on
the following terminologies:
General Mobility: the ability for the user to communicate and access services
irrespective of changes of the location or technical environment such as the
Access Network capabilities, with or without service continuity.
Terminal Mobility: Terminal Mobility is defined as the terminal having the
ability to be moved to different physical locations and provide the user access to
their services.
Personal Mobility: The ability of a user to access services independent of the
terminal or the location of the terminal.
Service Continuity: The ability for a user to maintain an ongoing service during
Generalized Mobility.
Nomadism: The ability of the user to access services when the user moves from
terminal to terminal or the user moves a terminal from one location to another
location and the Network(s) is(are) unable to maintain the user’s service
(session?).
Roaming: The group agreed that this terms does not need to be define or used in
the context of NGN because Nomadicity covers the relevant concept in NGN.

TD 04 - Mobility between H.323 multimedia systems and GPRS/IMT2000 networks
(Rev 2.0)
H.323 acts as an application on the top of SIP in IMS.
The document needs to reflect the access independent nature of IMS.
Mobility Management definitions will be replaced by a pointer to the relevant
documents in ITU-T.
-4TD 14r1
It was not clear if H.323 application requires additional security beyond what is
already available by IMS.

TD 05 - Possible Extensions to Mobility Definitions in H.323 Systems with regard to
NGN and System Convergence
A very useful compilation of MM definitions in various ITU-T documents. This
document was used as one of the inputs to the terminology discussion.

TD 06 - Use of IMS as the Basis for FMC in NGN
(Discussion notes are in the version of this document behind TIES.)

TD 07 - Use of Subscriber Identity Module (SIM) functionality in FMCed NGNs
(Discussion notes are in the version of this document behind TIES.)

TD 08 - RFC 3753 - Mobility Related Terminology
It was noted that the MM terminologies used in IETF is primarily from the IP
point of view and they may have significant differences to those being discussed
in NGN or IMT2000.

TD 09 - Technical Report on NNI Mobility Management Requirements for Systems
Beyond IMT-2000
No contributions to this carry over document so it was not treated.

TD 10 - Mobility Management Framework for Systems Beyond IMT-2000
No contributions to this carry over document so it was not treated.

TD 11 - Baseline Document for 2nd stage deliverable for Q.5/19 on “FMC Network
Architecture and interfaces”
No contributions to this carry over document so it was not treated.

TD 12 - Proposal for review of classification and definition of mobility
A late TD. The group agreed to allow it for inclusion.
TD 12 stimulated a very useful discussion. Points of agreement from the
discussion were:
- Tree Diagrams such as in the current FG NGN documentation and in TD
12 have positive and negative aspects: the discussion noted that trying to
resolve this area through defining or refining such a diagram may not be the
best approach
- An approach using scenarios (e.g., a user walking down the street, a user
driving in a car, a group of users on a train or plane, etc.) should be the
starting point
- Within the scenarios identified, a criterion for further investigation of a
scenario should be whether network actions are required to maintain the
scenario (e.g., when using a given access means, a moving user may require
handover, while a stationary user would not; a stationary user may need to
change access means as a result of a change in the service desired or for
some other reason; etc.)
-5TD 14r1
Although no conclusions were reached, the above points were considered a
suitable methodology to further develop this area. As a stimulus to further
progress in this area and to capture points raised in the discussions, some notes
are attached as Annex 5 to stimulate contributions.

TD 13 - Reply to the LS on Project coordination and release planning for NGN
Drafted during discussion and forwardes to SG 19 Chair for review and approval
by correspondence. Please see TD 02 for additional discussion.
5.1
Review of Meeting Report.
The draft meeting report in TD 14 was reviewed, revised, and approved as TD 14r1.
6
Acknowledgements
The Rapporteur would like to thank Ericsson Australia Pty Ltd. and the Australian
Communications Authority for sponsoring this meeting.
-6TD 14r1
Annex 1 – Meeting agenda
1. Roll call and introductions
2. Agenda
3. Meeting logistics
5. Document allocation
6. Discussion of input documents
7. Revision of output documents
8. Review of draft meeting report
9. Close of meeting
-7TD 14r1
Annex 2 – Work Plan
VOID
-8TD 14r1
Annex 3 – List of documents
Doc. No.
Source
Title
TD 01r1
Rapporteurs
Agenda and Work Plan
TD 02
Study Group 13
Project co-ordination and release planning for NGN
TD 03
Rapporteur
Q.6/13
Some relative documents from the latest SG13 and NGN-FG
meeting
TD 04
Rapporteur
Q.29/16
Mobility between H.323 multimedia systems and
GPRS/IMT2000 networks (Rev 2.0)
TD 05
Rapporteur
Q.29/16
Nokia Corporation
L. M. Ericsson
Nokia Corporation
L. M. Ericsson
Possible Extensions to Mobility Definitions in H.323 Systems
with regard to NGN and System Convergence
TD 08
Rapporteur
Q.2/19
RFC 3753 - Mobility Related Terminology
TD 09
Editors Q.2/19 and Technical Report on NNI Mobility Management Requirements
Q.5/19
for Systems Beyond IMT-2000
TD 10
Editors Q.2/19 and Mobility Management Framework for Systems Beyond IMTQ.5/19
2000
TD 11
Editors Q.5/19 and Baseline Document for 2nd stage deliverable for Q.5/19 on
Q.2/19
“FMC Network Architecture and interfaces”
TD 12
NTT Corporation
Proposal for review of classification and definition of mobility
TD 13
Rapporteur of
Q.2/19
Reply to the LS on Project coordination and release planning
for NGN
TD 14
Rapporteurs
Meeting Report
TD 06
TD 07
Use of IMS as the Basis for FMC in NGN
Use of Subscriber Identity Module (SIM) functionality in
FMCed NGNs
-9TD 14r1
Annex 4 – List of Participants
First Name Last Name Organisation
Country
Patrick
Emery
Australian Communications Authority
Australia
Leslie
Graf
L M Ericsson (Sweden)
Australia
Kevin
Sutherland
Australian Communications Authority
Australia
John
Visser
Nortel
Canada
Jin
Mingye
China Unicom
China
Baofeng
Zhang
Huawei Technologies Co., Ltd.
P.R.China
Kiritkumar
Lathia
SIEMENS MOBILE COMMUNICATIONS SPA Italy
Lehmann
Leo
OFCOM
Switzerland
McFarlane
David
Nokia Corporation (Finland
United Kingdom
Khatibi
Farrokh
QUALCOMM Inc.
USA
Teising
Charles
Lucent Technologies
USA
- 10 TD 14r1
Annex 5 – TD 12 Discussion Tree Diagram
General
Mobility
Terminal
Mobility
Access
Technology
Change
User
Mobility
Network
Mobility
Service
Mobility
Service
Discontinuity
Service
Continuity
Seamless
HO
Movement
Mobility
NonSeamless
HO
Notes:

This is not an agreed Tree Diagram; just another representation. The procedure
described in TD 12 may result in a more appropriate representation.

For simplicity, not all the branches are included in this diagram.
Download