|
|
|
|
MTELRelay to Direct Wireless Broadband1.1 Focus 2016With the introduction of WBB enabled picocells it has always been the intention of the MTEL WBB system to send messages directly from MTELPage to the WBB enabled picocells. This connection would take advantage of the permanently connected infrastructure to reduce the message latency dramatically from the current dial-up systems. This instruction is specific to the MTELRelay 2016 application V1.1 (88) and above. This application now passes messages from MTELPage and relays them directly to the Direct Host which then sends messages to all the WBB enabled picocells. The Direct Host resides in DCS and has redundancy via the remote MTEL Office network using the existing dialup systems. The application will continue to route messages to PagerDEC as in previous versions. There are no changes to this functionality. Hence mobile SMS messages and messages to Hutchison Vodafone will continue to operate. The application also continues to distribute decoded pager data to MTELPage in the reverse direction from the Vodafone Hutchison "3 Paging" network from the PagerDEC server. All MTELRelay's in DCS have the DWBB capability. The Direct Host has the capacity to handle messages from all centres via the Relay simultaneously. The connections to the Direct Host are permanent. The Relays have a virtual pipe across the Direct Host connection. All failures to deliver the message from MTELPage to the WBB Gateway are pushed back to MTELPage and rerouted to the local MTELQue running in the Comms Centres. The diagram below displays the intended final functionality for the system. The DIRECT Host also has OPC connection functionality and mimics a leased line PET connection. This connection has limited capability due to the PET protocol, it is provided to allow ESCAD focused Firecoms to send messages directly the same as MTELPage based messages.
1.2 ConfigurationMTELPage configuration To designate the picocell as a WBB system rather than PSTN or ISDN the picocell pstn data.mdb contains a new site entry where the old site name is appended with _WBB. The dialup parameters are then selected as PSTN and the number is the MTEL WBB access number. This provides two functions, the first is the Queue entry tells MTELPage which route to initially send the message. Second, if the message fails on the R01 route and is sent back to MTELQue, the PSTN information is used by MTELQue to send a message to the new WBB network via the dialup MTEL WBB system. With the release of MTELPage 2016 the Relay will also send messages to virtual picocells. These sites have site name with the name appended with _VPC. These sites are used in conjunction with the MTEL Connect system for user acknowledgement. The virtual picocell performs all the normal paging functionality with user acknowledgement however a message is not generated by the gateway. The message is sent by other methods such as the MDS.
MTELRelay configuration The Relay has two types of outputs, PagerDEC (PDEC) and Direct WBB (DWBB). These routes are solely determined by the name of the network. All _WBB and _VPC messages are sent to the DWBB sockets and all others go to the PDEC socket. Multiple sockets for each output type can be defined. Each can be individually enabled/disabled using the Active field. Clicking on TEST WBB button will send test packets to all DWBB sockets.
1.3 OperationMTELPage sockets The Relay inputs are server sockets and wait for connections from each MTELPage Client in the Comms Centre. The local IP is defined in the Startup table as "MTELPageIP " so that it can be bound to the correct IP stack. MTELPage routing The picocell site records in the MTELPage picocell pstn data.mdb must be changed from Q01 to R01 in the Queue field of the PicocellSites table. This directs MTELPage to route messages to the Relay. Relay Outputs The outputs are clients and require the IP and Port information to define the socket. The Relay checks the name of the network field in the RQST packet from MTELPage and tests for the appended "_WBB" extension to the network name. e.g. Esk_WBB the request packet is
When the packet is relayed to the Direct Host the network name is changed to the WBB name which is in the above case Esk.
The _WBB extension only exists in the MTELPage environment through to the Relay. If MTELPage sends messages to the MTELQue it will recognise all _WBB networks as being the same destination for dial-up purposes. Hence Esk_WBB and Toogoolawah_WBB will be delivered out the same modem connection. The diagram below summaries this operation.
The packet is routed to the DWBB socket as defined in the Output socket configuration. An example is shown below
The DWBB socket is operated on a virtual channel basis. That is all relays are streamed onto the one link from the DirectHost to MConnect. The packet addressing maintains the virtual channel information such that return packets are sent to the originating site correctly. Once the WBB Gateway has processed the message a response is sent back to MTELPage via the Relay to indicate the success of the message. e.g.
Socket Errors: The Direct Host has an activity timer as well and it is longer running at 30 seconds. Normally the Relay will terminate the connection however if the TCP connection fails, both ends will terminate the socket eventually freeing up the socket for the next user. 1.4 Fault Operation and ReportingThere are many point to point connections between MTELPage and the WBB picocell. Each connection could fail for a variety of reasons. Each connection failure is handled and the fall back is to send the message back to the Comms Centre MTELQue to be delivered by dial up systems. This document is specific to connections to MTELPage and the Direct Host. The diagram below shows a simple single packet operation. MTELPage sends a RQST packet to the Relay it forwards the same packet to the Direct Host. The Direct Host then receives reply's from the WBB Gateway and forwards these to the Relay which forwards the packet to MTELPage for final processing. The RESI are intermediate responses and the RESP packet is the final packet completing the message transaction.
If the linkage is broken between these applications then appropriate responses are sent back to MTELPage. The example below the Direct Host has failed to connect to the WBB Gateway. The message is cancelled and rerouted all the way back to MTELQue. The process is very quick typically less than a second.
The same process of rerouting occurs for Direct Host failures.
|
|
|
