M2M Cellular Gateway
Its steps are:
Pre‐state: After system booting up, system tries to let the WAN connection be alive.
S 1: When system discovers the WAN connection is failed.
S 2: System starts to re‐connect the WAN connection till connect successfully as same as Pre‐
state.
In the "Dial‐on‐demand" scenario, system will not make the WAN connection until gateway
receives an Internet accessing request from Intranet. And then the connection will keep alive only
when there still is data transfer. If there is no data transfer for a period that is longer than the
Maximum Idle Time, system will disconnect it and let the WAN connection go back to its initial
state –disconnected. The scenario is shown in following diagram.
Its steps are:
Pre‐state: After system booting up, the WAN connection is disconnected.
S 1: When an Internet accessing request is fed into the gateway from the Intranet.
S 2: System starts to make the WAN connection till connect successfully. Keep the connection
alive only when there still is data transfer to the Internet.
S 3: If the WAN connection idles timeout, system will disconnect it and let it go back to Pre‐state.
At last, for "Manually" scenario, system will not make the WAN connection until administrator
click on the "Connect" button on the "Network Status" configuration window. Please refer to
[System]‐[Network Status] section. And then the connection will keep alive only when there still
is data transfer. If there is no data transfer for a period that is longer than the Maximum Idle Time,
system will disconnect it and let the WAN connection go back to its initial state –disconnected.
The scenario is shown in following diagram.
Index skipping is used to reserve slots for new function insertion, when required.
ISP
② Start Connecting
DSLAM
③ Disconnect when
idle timeout
Primary DNS,
Secondary DNS,
DHCP Servers
xDSL Modem
Intranet
Gateway
Dial-on-
demand
① Request Coming
73