Quote:
Originally Posted by jopfer
|
From the above document:
B.1.2 Recommended 802.11 AP Capabilities
1. Beacon: The AP should transmit periodic beacons, at least every 100 ms.
2. Authentication: The AP should support WEP and WPA with PSK. It could optionally support 802.1X authentication for
large enterprise environments.
3. Encryption: The AP should support WEP (RC4) and WPA (TKIP) encryption, including 802.1X Key Management
(802.1X/EAPOL-Key functions). It could optionally support WPA/802.11i (AES) encryption
4. Roaming: The AP could optionally support IAPP or similar vendor-specific inter-AP protocol to speed up context
transfer for a roaming MS (Phone).
5. Delay: The AP (if it can discern voice packets, say using 802.1p tags or IP TOS/DS markings) should internally
prioritize voice packets ahead of any other data packets that are to be transmitted. The AP should support 802.11e
EDCA (or WME) to allow prioritized access for voice packets to the medium. It can also “simulate” this behavior by
using a smaller contention window and inter-frame spacing for voice packets, relative to other data packet.
6. Network QoS: The AP should honour 802.1p tags and IP TOS/DS byte markings, to provide relative prioritization for
voice packets on the LAN uplink.
7. Power save/sleep mode: The AP should support MS that want to use power-save mode. Specifically, it should
recognize the Power Management bit in the frame header, and if an MS indicates it is going to enter PS-mode, the AP
should buffer any incoming traffic for that MS and indicate that via a Traffic Indication Map (TIM) or DTIM. The AP
should support Power-Save Polling by the MS.
D.1.1 Hibernation Mode
The GSM RR entity in MS enters hibernation mode when the MS switches from GSM mode to UMA mode.
In this mode, the GSM RR entity shuts off the GSM radio in order to extend battery life in UMA mode. Before going into
hibernation mode:
1. If there is a GSM camping cell available, the GSM RR keeps a copy of the most recent system information of the
camping cell, and then shuts down layer 1 and powers down the GSM radio.
2. If there is no cell available, the GSM RR immediately stops layer 1 and shuts off the GSM radio.
3. If PLMN search is in progress, it continues until either a camping cell is selected or when it is concluded that no
cell is available for the moment. It then proceeds according to step 1 or step 2 above.
The GSM RR entity exits out of hibernation mode under the following conditions:
1. When MS changes AP it is attached to, as a result of intra-UMA roving or handover;
2. When MS detects unlicensed radio link has dropped below certain threshold that triggers rove-out or handover-out
(or some time prior to this event);
3. When unlicensed radio link is lost altogether.
Upon exiting hibernation mode, and with the stored copy of the system information, the GSM RR entity can perform instant
wakeup instead of going through either normal cell selection procedure or stored list cell selection procedure (See §6.2/6.3
of 3GPP TS 45.008). To do so, the mobile tunes onto the ARFCN of the target cell and searches for the FCCH. Once it
captures the synchronization to the FCCH/SCH of the target cell, it restores all BCCH data from previously stored snapshot
and assumes the BCCH data is up to date. If the target cell is not found within two FCCH cycles (about 92ms), or if
snapshot BCCH data is not available, the mobile shall go through the normal cell selection procedure or stored list cell
selection procedure.
After that, the GSM RR entity moves into the “detached cell reselection” mode (see next section).
If the MS is still in UMA mode (i.e. due to intra-UMA roving or handover), then the GSM RR entity can re-enter hibernate
mode.
If the MS switches to GSM mode (i.e. due to UMA-to-GERAN roving or handover), then the GSM RR entity will become
active and attached to the NAS layer (and UMA RR entity will detach from the NAS layer).
It also says elsewhere that UMA establishes a secure tunnel. The WRT54GX2 reviews give it a TERRIBLE reputation for tunneling and VPN performance!
I am trying playing with UDP ports 4500 and 500 which TMO says are the ports