Thread Links | Date Links | ||||
---|---|---|---|---|---|
Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
Hello,
My position is that in the PAR we need
item[s] on structure of data backbone
to support mobillity.
Above includes
- types of nodes [BS(NodeB)-RNC-SGSN-GGSN in
terms of 3GPP]
- layering model of each node and protocols for communication
between nodes [e.g. BS-to-BS communication]
- IP mobility support at the
network [like MoIP &
micro-mobility]
- micro-mobility may include
specification of "L2 triggers"
- AAA elements [nodes responsible for AAA, global
definition of services]
It is very close to Phil's list and to Joey's
comments.
Note that some elements of this stuff are already present in 802.16e doc;
probably we have to remove them to a new document [as suggested also by
DJ].
Development of network specification is critically important for
penetration of 802.16e technology.
It is hard to imagine a network operator buying 802.16e enabled BSs
and SSs without
clear [based on standard] understanding of the structure of land network
for this type
of mobility. Note status of network specifications in 3GPP.
I support DJ's idea of PKMv2 .
I would suggest to have a separated PAR for MIB development. Note that
actual work on MIB for fixed systems
has advanced in WiMax and ETSI [Intel, Alvarion, Airspan, Proxim]. There
is a MIB group in WiMax [chaired by Joey Chou]. There is
a MIB project in HIPERMAN [I am a
Rapporteur]. There is a draft of MIB document that
includes
ASN.1 encoding [IEEE C802.16d-03/76r3 also known as BRAN35d017].
Having this activity tied to developement
of network structure for mobility would be strange and impractical and may
affect synchronization between 802.16
and HIPERMAN MIB documents [HIPERMAN
MIB must be finalized this year].
Vladimir
This mail was sent via mail.alvarion.com ************************************************************************************ This footnote confirms that this email message has been scanned by PineApp Mail-SeCure for the presence of malicious code, vandals & computer viruses. ************************************************************************************ |