Thread Links Date Links
Thread Prev Thread Next Thread Index Date Prev Date Next Date Index

Requirement Document posted



Title: Message
Hello to all,
 
I am having a couple of comments on the current version of the document as agreed in Portland.
 
Section 2 Definitions
It is a good thing to have introduced a definition for seamless handover!
 
Section 3 Functional Requirements
3.9 and 3.10
Cost and  link utilization are criteria to be taken into account by a handover policy function in order to achieve the handover service according to the requirements. These are NOT requirements by theirselves! Therefore, I am struggling with understanding what is requested there.
 
3.12 Handover Policy

It is said "Terminal Initiated Network assisted handofffs should be given preference since the mobile terminal has knowledge of all the networks an applications running on the device".

 I do not agree here as it can also be argued that Network Initiated terminal assisted mode brings the possibility for the nework to select the best available access network for the terminal according to link utilization and Access Point load information it has and which the terminal doesn't. Just letting the terminal have the final decision could then result in handovers to access network where the user will experience severe service degradation because it had ignored such information.

 

Therefore i will suggest just evocating different possible initiationt/assistance handover modes within the requirements Document without mentioning preference on any of them. This preference should rather be let at the discretion of the hanfover policy function that can reside either on the terminal or the network.

 

 

Section 4 Architecture

4.1 layer 2.5

It is said "The standard shall define SAP(s) for providing layer 1 (PHY), layer 2 (MAC), and layer 2.5 (Mobility Management) information to higher layer entity such as Mobile IP".

Again one of the reason of defining a layer 2.5 model was that it allowed higher layer mobility protocol not to understand each of the underltying layers as all those layers will now interface to the 2.5 layer. So with the use of L2.5, information from PHY and MAC need not anymore be passed directly to higher layer moility protocol as they will be passed to L2.5 wich will present it to unique format upwards!

 

Section 6 Reference Model

 

It is not clear from the document  where an input to any particular layer comes from and which direction (up or down)  the output is directed at

 

 

We can further discuss these points tommorrw during the conf call

 

Eric Njedjou

France Telecom