Re: [STDS-802-16-MOBILE] Clarification regarding idle mode and paging
Gedon,
I think your question is a very important one and for understanding where
paging as a feature originates from, one needs to understand the
application architecture model. I may not fully address your question but
wanted to share some thoughts.
Here essentially one can simplify the various schemes to two essential
models.
- Global directory
- Local directory
-
And the core application is looking up information about some entity on a
network that could be anywhere. For example, depending on the kinds of
information stored whether it is a IP Address-L2 Address map or IP
Address-User ID map local or global directories could be used. In most
deployments a combination of local and global directories are used.
Now "Paging" as a function is equivalent to requesting a proactive
directory-lookup and response, instead of performing a polled lookup,
which is not as efficient. However Paging has a cost associated with it,
which is broadcast/multicast packets to all the directories that may or
may not hold the information being looked up.
So most commonly it is used for looking local directories, where ones
directory updates could be more frequent and broadcast/multicast does not
prove as costly as the locality is small. Typically for global
directories one would prefer polled lookup (example LDAP style).
So in a 802.16 radio network, the way Paging could be effective is for
the local directory lookup, to understand which BS, the MSS is attached
to at the moment. So the types of applications that take advantage of
paging could be radio networks that automatically update global
directories when the MSS moves within the radio network (BS to BS).
However if one were to deploy SIP based VoIP services, a global directory
lookup makes better sense. Paging can only be useful in this case if the
radio network proactively pages the MSS periodically and then updates the
global directory when it has moved.
Best regards,
jose
________________________________________________________________________________
From: owner-stds-802-16-mobile@LISTSERV.IEEE.ORG
[mailto:owner-stds-802-16-mobile@LISTSERV.IEEE.ORG] On Behalf Of Rosner,
Gedon
Sent: Tuesday, April 20, 2004 6:45 PM
To: STDS-802-16-MOBILE@LISTSERV.IEEE.ORG
Subject: [STDS-802-16-MOBILE] Clarification regarding idle mode and
paging
"Idle Mode is intended as a mechanism to allow MSS to become periodically
available for DL broadcast traffic Messaging ..".
It seems that the ability of an MSS to determine which type of traffic
may generate paging is important on a network supporting a variety of
services - and obviously it is also missing in paging definition.
In a 3GPP network, paging is simple due to limited services that might
use it (dedicated voice calls and SMS) - this service is inherent and
explicit in the network. However, when moving to a shared services
network it is quite desirable to be able to determine which types of
traffic generate paging without requiring specific carrier application to
register and support the paging.
This is especially important on data networks where many protocols send
out periodic messages that the MSS may choose to discard while
maintaining some degree of availability.
It seems that defining optional idle mode service flows (with
classifiers) will provide a simple, flexible and necessary amendment to
the current paging definition.
I'd like to hear your thoughts/inputs on this.
Thanks in advance !
Gedon Rosner
Intel Corporation